Can't get rid of helo-laravel...

HELO works great for emails that my code sends - really awesome. Since I added it in the middle of a project, I didn't notice that it totally bombs out when using Laravel created authentication messages (see issue #1 ). I need to test some things that area, so I am trying to get past HELO. I changed my .env file back to my MailTrap settings, and the mail message I generate now go there, but the Laravel created emails still generate the
Argument 1 passed to Illuminate\Notifications\Channels\MailChannel::__construct() must implement interface Illuminate\Contracts\Mail\Factory, instance of BeyondCode\HeloLaravel\Mailer given

error. Any idea how I can get around this?
Thanks!!

It looks like you have installed the (this) optional helper package. You don't need it for using the HELO app. So if you remove it from your composer.json file and run composer update you should be good to go.
So if you remove the helper package, you can use HELO again and shouldn't have any issues.

@sschlein Perfect - thanks!! Now I'm not clear why I installed this in the first place....


Building and installing the library

Hi,
I tried building and installing the library, but it seems that there are a bunch of dependencies that are required in order to build the library. On Fedora 40 I had to install these:
google-benchmark-devel
gtest-devel
asio-devel

And even after installing asio-devel, there was some find_package() call in CMakeLists.cmake which failed because it couldn't find asio-config.cmake or asioConfig.cmake. I couldn't find a Fedora package that provides either of these files, so I just gave up on trying to build the test/benchmark stuff and just commented out the following lines in CMakeLists.cmake
# add_subdirectory(bench)
# add_subdirectory(tests)
# add_subdirectory(tests/autobahn)
# add_subdirectory(examples)

After that the project built successfully (which is not surprising given that it seems to be a header-only library).
It probably makes sense to add CMake options that would allow excluding these four directories by default and only building them if the user explicitly requests that.
Also another issue arises from the following defines
WS_CLIENT_USE_SIMD_UTF8
WS_CLIENT_USE_ZLIB_NG

Initially I thought that they are CMake options and should be specified as
cmake ... -DWS_CLIENT_USE_SIMD_UTF8 -DWS_CLIENT_USE_ZLIB_NG

But obviously that is not the case. So obviously they are C++ defines and the next question is whether they should be defined during the building of the library or during the building of the user's application that uses the library. Given that it seems to be a header-only library, the defines probably should be added to the client applications's CMakeLists.txt
So all these things should probably be added to the readme file.

Hi,

It probably makes sense to add CMake options that would allow excluding these four directories by default and only building them if the user explicitly requests that.

Yes, the bench/tests/examples should be optional, I'll introduce CMake options for them.

WS_CLIENT_USE_SIMD_UTF8
WS_CLIENT_USE_ZLIB_NG

Indeed, those are compile time definitions, see examples:
target_compile_definitions(ex_echo_sync PRIVATE
    WS_CLIENT_USE_ZLIB_NG=1 # Use zlib-ng instead of zlib
    WS_CLIENT_USE_SIMD_UTF8=1 # Use simdutf for utf-8 validation
)

I agree that it's not obvious from the README and should be clarified.
Will look into it next week when I have more time at hand.

OK, thank you for the clarification. Also I installed the library via
cmake -B build
cmake --install build

After that it these two directories to /usr/local/include/, more specifically
/usr/local/include/coroio/
/usr/local/include/ws_client/

The second one, ws_client, contains .hpp files, but the first one, coroio, contains both .hpp files and .cpp files.
root@fedora:~# ls -la /usr/local/include/coroio/
total 116
drwxr-xr-x   2 root root  4096 Jul 23 04:58 .
drwxr-xr-x. 11 root root  4096 Jul 23 04:58 ..
-rw-r--r--   1 root root   745 Jul 23 01:35 all.hpp
-rw-r--r--   1 root root  1658 Jul 23 01:35 base.hpp
-rw-r--r--   1 root root  2771 Jul 23 01:35 corochain.hpp
-rw-r--r--   1 root root  4009 Jul 23 01:35 epoll.cpp
-rw-r--r--   1 root root   497 Jul 23 01:35 epoll.hpp
-rw-r--r--   1 root root  3046 Jul 23 01:35 kqueue.cpp
-rw-r--r--   1 root root   516 Jul 23 01:35 kqueue.hpp
-rw-r--r--   1 root root   422 Jul 23 01:35 loop.hpp
-rw-r--r--   1 root root  2662 Jul 23 01:35 poll.cpp
-rw-r--r--   1 root root  3889 Jul 23 01:35 poller.hpp
-rw-r--r--   1 root root   439 Jul 23 01:35 poll.hpp
-rw-r--r--   1 root root  1319 Jul 23 01:35 promises.hpp
-rw-r--r--   1 root root 10952 Jul 23 01:35 resolver.cpp
-rw-r--r--   1 root root  2814 Jul 23 01:35 resolver.hpp
-rw-r--r--   1 root root  1885 Jul 23 01:35 select.cpp
-rw-r--r--   1 root root   606 Jul 23 01:35 select.hpp
-rw-r--r--   1 root root  5664 Jul 23 01:35 socket.cpp
-rw-r--r--   1 root root  7975 Jul 23 01:35 socket.hpp
-rw-r--r--   1 root root  2544 Jul 23 01:35 sockutils.cpp
-rw-r--r--   1 root root  3815 Jul 23 01:35 sockutils.hpp
-rw-r--r--   1 root root  2389 Jul 23 01:35 ssl.cpp
-rw-r--r--   1 root root  7537 Jul 23 01:35 ssl.hpp
root@fedora:~#

What is the purpose of the .cpp files in that directory? Are they to be compiled in some way by the client application? It seems to me that they should actually be compiled during the library build and then installed as libcoroio.a or libcoroio.so. Or am I missing something about this installation?

You can ignore coroio / remove it. That's an alternative to ASIO, which is also optional. Maybe I should remove it or make a CMake option.

coroio has been moved out of the include directory and is optional.
The README has been updated with

new CMake options WS_CLIENT_BUILD_EXAMPLES, WS_CLIENT_BUILD_TESTS and WS_CLIENT_BUILD_BENCH
compile-time definitions are documented

If something else is worth clarifying or documenting, please let me know or submit a pull request. Thanks.


Adds courserun importing from edX (like sync_courserun, but moreso)

Pre-Flight checklist

[X] Testing

[X] Code is tested
[X] Changes have been manually tested

What are the relevant tickets?
No ticket for this but was inspired by #1235
What's this PR do?
Adds a management command, import_courserun, that will create course runs in MITx Online and import the relevant data from edX in one fell swoop. Optionally, it will create CMS pages for courses that don't exist. Also optionally, it will walk a program and attempt to find all the courses in edX that exist for a given run tag and set them all up at once (so if you create a chunk of courses for a new semester, you can just tell the command the program and the new semester run tag and it'll take care of the rest).
How should this be manually tested?

Create some courses in your local devstack instance that don't have corresponding courseruns in MITx Online. Ideally, make some that are in a program and some that are outside that program so you can test individual run generation as well as whole program generation.
For the individual courserun, run manage.py import_courseware --courserun <course run ID>. The course run should be created and its information should match the course on edX.
For the program, run manage.py import_courseware --program <program> --run-tag <run tag>. It should attempt to find all the courses that are in the program on edX and, if it finds them, then attempt to create courseruns for them. Depending on how your devstack instance is set up, you may get a bunch of errors here due to courses not existing in devstack.
Apply the --live flag and make sure the course runs are marked as live.
Attempt to sync a courserun for a course that doesn't have a CMS page, and specify --create-cms-page. The command should create a CMS page for you.
The command should fail gracefully if:
7. The course run(s) already exist
8. The course doesn't exist
9. The CMS page for the course already exists
(i.e. you should be able to re-run this for a program and have it add new things but not touch things that were already extant)

Codecov Report

Merging #1256 (673434f) into main (c15b8e0) will decrease coverage by 2.06%.
The diff coverage is n/a.

:exclamation: Current head 673434f differs from pull request most recent head 16a8b3a. Consider uploading reports for the commit 16a8b3a to get more accurate results

@@            Coverage Diff             @@
##             main    #1256      +/-   ##
==========================================
- Coverage   83.18%   81.12%   -2.07%
==========================================
  Files         297      151     -146
  Lines       11957     7846    -4111
  Branches      815      815
==========================================
- Hits         9947     6365    -3582
+ Misses       1783     1255     -528
+ Partials      227      226       -1

Impacted Files
Coverage Δ

ecommerce/models.py
85.83% <0.00%> (ø)

frontend/public/src/components/Expandable.js

frontend/public/src/lib/queries/courseRuns.js

...ontainers/pages/register/RegisterEmailPage_test.js

.../src/containers/pages/login/LoginEmailPage_test.js

...d/public/src/components/forms/ProfileFormFields.js

...end/public/src/components/ReceiptPageDetailCard.js

frontend/public/src/lib/notificationsApi.js

.../src/containers/pages/checkout/OrderReceiptPage.js

frontend/public/src/tests_init.js

... and 138 more

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

I could use this right away to help with https://odl.zendesk.com/agent/tickets/141442

Does this address step 7 & 10 in https://github.com/mitodl/hq/discussions/306 ? Is it possible to include any others?

It can take care of the product creation.. that should be pretty simple to add so will do that today.

Product creation added in https://github.com/mitodl/mitxonline/pull/1256/commits/62a9685d9327818077af1ae88657f1bc8cbd6c73

Updates in https://github.com/mitodl/mitxonline/pull/1256/commits/e4f82bfe2db26e18d1510a30e6b05f14e4e0055b include fixing the bug with CMS pages (live should reflect whether or not you pass --live; it was always "draft" before) and updating the single courserun code to create the course if it also doesn't exist.
For the course creation - you can now specify --courserun and --program together; in this case, the program is the program that the new course should be added to. Don't specify --run-tag here - it'll be ignored. The run tags is part of the courserun readable ID so it'll get the run tag from that.


Add support for GCI webhooks

See webhooks in https://developers.google.com/open-source/gci/resources/downloads/TaskAPISpec.pdf
difficulty/high
Opened by @jayvdb at gitter/coala/gci

@jayvdb How do you intend to use the webhook in corobo?


Do not update the version to dev during release

Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Release:
-----------------------------------------------------------------
--------------------- Release configuration ---------------------
-----------------------------------------------------------------
Git URL 		 -> git@github.com:elyra-ai/pipeline-editor.git
Git reference 		 -> HEAD
Git user 		 -> Luciano Resende
Git user email 		 -><EMAIL_ADDRESS>Work dir 		 -> /Users/lresende/opensource/elyra/pipeline-editor/build/release
Source dir 		 -> /Users/lresende/opensource/elyra/pipeline-editor/build/release/pipeline-editor
Current Version 	 -> 0.4.0-dev
New Version 		 -> 0.4.0
Release Tag 		 -> v0.4.0
-----------------------------------------------------------------

Release Candidate:
-----------------------------------------------------------------
--------------------- Release configuration ---------------------
-----------------------------------------------------------------
Git URL 		 -> git@github.com:elyra-ai/pipeline-editor.git
Git reference 		 -> HEAD
Git user 		 -> Luciano Resende
Git user email 		 -><EMAIL_ADDRESS>Work dir 		 -> /Users/lresende/opensource/elyra/pipeline-editor/build/release
Source dir 		 -> /Users/lresende/opensource/elyra/pipeline-editor/build/release/pipeline-editor
Current Version 	 -> 0.4.0-dev
New Version 		 -> 0.4.0-rc.0
RC number 		 -> 0
Release Tag 		 -> v0.4.0rc0
-----------------------------------------------------------------


Oklcha with_ methods are inconsistent with other color spaces

Bevy version
main
What you did
Try to swap some code using Hsla to Oklcha.
What went wrong
Expected with_hue calls to continue working, because Oklcha also has hue.
But for this color space, they are with_h, with_l, and with_c.
Additional information
I think that Oklcha is the odd one out and that all other spaces use full names, but we should check them all and make them consistent.
Also, maybe this is intentional. I don't know much about Oklch. Are the lch strictly "lightless" "chroma" and "hue"?.
Oklaba also has "short with_ methods" but if you expanded them, I assume they would end up like lightness, a, b.

Yeah, we should expand these all out. Oklaba's extended form is lightness + 'a' + 'b' as you say.


Netatmo failing on startup

just pulled the latest and am getting the following error on start up, i thought i should add that my Netatmo was working before this pull request, thanks
[Netatmo Weather] Initializing Netatmo platform...
==> /var/log/homebridge.err <==
/opt/homebridge/platforms/Netatmo.js:124
that.api.getStationsData(function(err, devices) {
^
TypeError: undefined is not a function
at Object.NetAtmoRepository.refresh (/opt/homebridge/platforms/Netatmo.js:124:14)
at /opt/homebridge/platforms/Netatmo.js:151:16
at NodeCache.module.exports.NodeCache.get (/opt/homebridge/node_modules/node-cache/lib/node_cache.js:64:11)
at NodeCache.get (/opt/homebridge/node_modules/node-cache/lib/node_cache.js:3:59)
at Object.NetAtmoRepository.load (/opt/homebridge/platforms/Netatmo.js:148:16)
at Object.NetatmoPlatform.accessories (/opt/homebridge/platforms/Netatmo.js:179:21)
at loadPlatformAccessories (/opt/homebridge/app.js:122:20)
at loadPlatforms (/opt/homebridge/app.js:116:9)
at startup (/opt/homebridge/app.js:59:27)
at Object. (/opt/homebridge/app.js:223:1)

Hi,
the new netatmo is working with an updated version of the netatmo api provided by patricks.
(Please check: https://github.com/nfarina/homebridge/issues/326)
This version does nolonger use an outdated and deprecated API call
For me a "npm install" fixed this, since the netatmo lib was updated.
Kind regards
planetK

perfect, working now, thanks so much, maybe i should remember to do this after every update?


Sanitize SW_REGISTER logs

This PR is adding a way to sanitize sensitive logs. I realized that my logs were containing sensitive information (AKA. user passwords from the RW_REGISTER call) and that was not acceptable. This is a opt-in setting, so "old" code should be working the same way it was.

ping

Closed in favor of #37


Add electron-store JSON schema for the app settings

Adds a JSON schema for electron-store.
re #663

@sindresorhus how can I snag the issuehunt deposit for completing this issue?

@blakedietz Done now. Rewarding is done manually.

@sindresorhus thank you!


Log to file

simple_logger doesn't seem to allow logging to a file. Currently, we can run teos like:
teosd >> teos.log
And that would do, but it may be nice to have this out of the box. Find a simple and lightweight replacement for simple_logger that allows this and do the proper changes.

In defense of simple_logger since it's indeed a very simple, lightweight crate:
This might be a fairly simple feature to add.

Looks like this may be harder than it looks, but it has been requested as a feature, but the issue was closed :( https://github.com/borntyping/rust-simple_logger/issues/21
The general solution is redirecting on cmd https://github.com/borntyping/rust-simple_logger/issues/16

I'm also going to link #176 since this is somewhat of a solution for it

I think we should keep this, but maybe remove the good first issue tag and tag it as docs or something.
There is currently a solution for this for Linux via systemd and you can also go the teosd >> teos.log route.
Thoughts @mariocynicys?

To me, this would only make sense if the tower can be ran as a detached daemon.
It's cleaner to start teosd in:
teosd --daemon --logfile FILE fashion (and actually have daemon and logfile specified in the config instead) than teosd --daemon >> FILE.
But since I start my tower like teosd >> FILE & anyway, where the log file is specified isn't an issue in that regard since I have to write that trailing ampersand.
This might be a bit of a biased opinion tbh.
side note: sorry I don't like systemd services :p


Aligning widgets

According to https://ipywidgets.readthedocs.io/en/latest/examples/Widget Styling.html

Most widgets have a description attribute, which allows a label for the widget to be defined. The label of the widget has a fixed minimum width. The text of the label is always right aligned and the widget is left aligned:
If a label is longer than the minimum width, the widget is shifted to the right:

How can I change the minimum width?  My widgets have descriptions with various lengths, and I can't get any of them to line up!

Here's an example of the output we currently get when stacking a bunch of ipywidgets in a VBox:

or a Box:

From the documentation, I can't figure out what options there are for aligning either the descriptions, the left edge of the widget, or the right edge of the widget, and for the results to look at all sensible we'd want to align all three of those values.  From the code, I can see lots of different settings, but nothing that I can see how to change...

@jbednar which version of ipywidgets are you using?

The situation should be better with ipywidgets 5.x, which you can install with
conda install -c conda-forge ipywidgets

ipywidgets 4.1.1, the latest available on the main anaconda channel.  I'll try the conda-forge version.

You should get 5.1.4.

Thanks for the suggestion!  After
conda install -c conda-forge ipywidgets
jupyter nbextension enable --py --sys-prefix widgetsnbextension

and restarting the notebook server, I get ipywidgets 5.1.4 and the following output (after disabling selection boxes, which seemed to have changed syntax or requirements):

I guess that's an improvement. :-)  But I still have the same problem: How can I increase the description width, which is woefully short?  Breaking it across lines like that isn't something I'd want to happen except for extremely long names.  How can I make the various widgets (sliders, different types of text boxes, etc.) be the same width?  How can I make a boolean's label show up on the same side of the widget as for all the other widgets, so that it lines up the same?  Is there a magic web page or even code file somewhere that explains all this? :-)

At the moment, you cannot change the description width from a Python API.
However, you can add a css class to the widget and inject css through the %%css magic.

Thanks! Is there a web page or notebook with an example of how to do that?

This is not something we really support because it is exposing the DOM structure of the widget, which we don't want to make part of the API.
Regarding layouts, I recommend you take a look at the FlexBox Layout example notebook.

I had previously run across the FlexBox eample and tried to run it, but thought that it required a development version because it wouldn't work with my 4.x installation.  I'll try again with 5.x!
I don't want to mess with CSS either, but I would think that widget widths are something that many users will need to control, from Python.

BTW, I'll ask for ipywidgets to be updated on the main conda channel, which should happen quickly because I'm at Continuum using it for a Continuum-sponsored project. :-)  Thanks for releasing such a fabulous package for everyone to use!

👍 thanks @jbednar

Unless there's any chance a release is imminent that would add control over the description width, in which case I'd hold off on updating the main conda channel until the release is ready?

I don't think there is any reason to hold off. We are making releases all the time since 5.x, and it should not be an issue for anaconda folks to bump version numbers.

Ok, request submitted.

Just to update, after fixing a problem with the traitlets version, dropdowns work again, so I can show what all the widgets look like now:

As you can see, the dropdowns have yet another width and a different left edge, making the property sheet display like this be even more jumbled.

I also tried all the options in Flexbox Layout.ipynb, but all I managed to achieve was drawing a box around the entire set of widgets or to try to cram them on one line; I couldn't see any way to affect how the description field is formatted or how to change the widths of any of the widgets.

Correction: I can make the widths worse, I just can't improve them. :-)  If I passwidth=20% to all of the widgets, the FloatText widget gets cropped off at a narrow width, and if I pass  width=10px so does the SelectMultiple widget.  But I can't make any of them stretch to match the larger size of the other widgets, nor can I reduce the size of the larger ones to match, only reduce the size of already small ones.  Surely I'm missing something obvious about how to control all this?

@jbednar I meant that instead of using the description you can use Label widgets and lay them out with the FlexBox widgets.

Ah, I'll try that, thanks!

Well, that does improve things somewhat.  I couldn't get the Label widget to enforce a minimum width to make anything line up, but I was able to use an HTML widget with a fixed width:

So this takes care of lining up the descriptions, and it also puts the checkbox on the same side of its label as all the other widgets do.  However, SelectMultiple is still formatted incorrectly -- why is it offset slightly to the right?  It just always is, and I can't see how to affect that in any way.  Plus it might be nice to make the FloatText widget match the others in length, but I can't see how to stretch it out.

I just fixed the offset to the right, it will be in the next minor release.
I am preparing a better example notebook on widget styling and layout to
settle all of this.
FYI there ia a readout_format attribute for the slider. You may be
interested in this.
On May 20, 2016 2:07 PM, "James A. Bednar"<EMAIL_ADDRESS>wrote:

Well, that does improve things somewhat. I couldn't get the Label widget
to enforce a minimum width to make anything line up, but I was able to use
an HTML widget with a fixed width:
[image: image]
https://cloud.githubusercontent.com/assets/1695496/15437160/d3f6ab0e-1ec5-11e6-8a17-8c3040eac419.png
So this takes care of lining up the descriptions, and it also puts the
checkbox on the same side of its label as all the other widgets do.
However, SelectMultiple is still formatted incorrectly -- why is it offset
slightly to the right? It just always is, and I can't see how to affect
that in any way. Plus it might be nice to make the FloatText widget match
the others in length, but I can't see how to stretch it out.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/ipython/ipywidgets/issues/589#issuecomment-220677975

Thanks for the fix!  I think this will be usable for our purposes now, though it's definitely tricky to figure out how to format anything.  Hopefully the notebook will help enlighten us. :-)  I wasn't able to use readout_format to eliminate the strange gap after the slider, but maybe there's a way...


Cannot import into common source set

I have successfully pulled the jitpack.io dependency into my project, but release 0.8 seems to have no linkable source?

See the above for the successful gradle import.  I have no org.komputing package or files though?

I am having the same problem on Android when adding the following to my gradle file
implementation "com.github.komputing:KHash:0.8"

Furthermore it may be helpful to have an example in the README how to import only some modules.

thanks for the report - I guess this has to do with the multi-platform changes and you need to add a jvm - hope @RiccardoM can have a look here

Hi @steve-the-edwards and @MariusBoepple, thanks for opening this issue.
Currently, I'm working on making this project fully multiplatform compliant, but I need some of the other PRs to be merged first on other projects:

KBigNumbers: https://github.com/komputing/KBigNumbers/pull/4
KHex: https://github.com/komputing/KHex/pull/3

Once those projects have been made available for multiplatform, I will make this project multiplatform compliant too.
It should be a matter of days now. Sorry for the inconvenience.

but as far as I see they do not need multiplatform - just JVM

really confused now - your PR https://github.com/komputing/KHash/pull/7 introduced multiplatform and I think also introduced the problem with JVM the reporters have

@ligi You're write, I've misread the posts.
Having a look inside the Jitpack build.log for version 0.8 it seems that everything has worked fine.
Probably, the problem is that they are trying to use the repository as follows
implementation "com.github.komputing:KHash:0.8"

while it should be
implementation "com.github.komputing:Khash:0.8"

(Note the lowerchase h on KHash instead of it being uppercase).
This is due to Jitpack being case-sensitive

@RiccardoM thanks for looking into this. I would expect another failure for the case sensitivity (artifact not found) - but perhaps this is really the issue - waiting for the reporters to deny or confirm.
I can also look into the problem later this week as I also need to migrate from walleth/sha3 to komputing/KHash - just did not come around to it and it has no priority for me as there are no content changes for me between these versions.

I can also look into the problem later this week as I also need to migrate from walleth/sha3 to komputing/KHash - just did not come around to it and it has no priority for me as there are no content changes for me between these versions.

@ligi please see https://github.com/komputing/KEthereum/pull/66

@mirceanis thanks - looking at it currently - looks good - just need to test it a bit - but this means you could use KHash 0.8 in a JVM context?

@ligi yes.
It is used by a JVM lib trat passes tests and that lib is used in an android context which also passes tests.
I had to exclude the old walleth maven coordinates though, otherwise there are duplicate class errors in the android build:
implementation("com.github.komputing:KHash:$khash_version") {
        exclude group: "com.github.walleth"
    }

With implementation "com.github.komputing:Khash:0.8" I'm still just getting

They both look similar:
https://jitpack.io/com/github/komputing/Khash/0.8/
https://jitpack.io/com/github/komputing/KHash/0.8/

@MariusBoepple I see the same thing in AndroidStudio but I am able to CMD+click(CTRL+click) on a call to calculateSHA3() in my code and see the implementation.

but it seems jitpack only picks up the sha3 module:
https://jitpack.io/com/github/komputing/KhasH/0.8/build.log

but it seems jitpack only picks up the sha3 module:
https://jitpack.io/com/github/komputing/KhasH/0.8/build.log

I just assumed that was the only one available in 0.8. I didn't follow the history of this repo too closely

ah - yes you are right - 0.8 only contains SHA3


this is wrong, no longer applicable

this is wrong, no longer applicable

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

ID: 6ca858db-d7bf-c894-af0a-eb1ba07c29ea
Version Independent ID: 330f9197-38cd-73b7-c2cc-5d032a3bdc33
Content: Python in Visual Studio tutorial step 5, install packages
Content Source: docs/python/tutorial-working-with-python-in-visual-studio-step-05-installing-packages.md
Product: visual-studio-windows
Technology: vs-python
GitHub Login: @cwebster-99
Microsoft Alias: cowebster

@worldor -- thank you for your feedback.  Please clarify the inapplicable aspects of this article.  In addition, consider these resources:

Ask a question or find an answer on the Microsoft Q&A page for Visual Studio.
Check the Visual Studio MSDN Forum.
Stack Overflow
Reddit


Repository headline renders extremely thin

Gogs Version
Gogs: Go Git Service <IP_ADDRESS>5 Beta
Browser
Firefox 43.0a2 (2015-10-29) on Ubuntu 15.04
Problem description

As you can see the headline renders extremely thin. This happens because of the font-weight: 300; which is set on that element and the fact that I have the Lato font family (with its different weights) installed on my system. Rather than using the normal Lato font Firefox chooses “Lato Hairline” as it considers it to be more fitting for that weight.
After changing
.repository .head .ui.huge.breadcrumb {
    font-size: 1.7rem;
    font-weight: 300;
}

to
.repository .head .ui.huge.breadcrumb {
    font-size: 1.7rem;
    font-weight: 400;
}

it looks fine on my system:

Please try out develop branch or https://try.gogs.io


Duplicate method vector_apply_quaternion_rotation and quaternion_rotate?

I think we have two functions (see title) that do the same thing. If this is true, which one shall we keep?

Can you make the decision?

@Korijn Of course. I would keep vector_apply_quaternion_rotation (perhaps drop the _rotation bit). It follows the logic of vector_apply_matrix in that you take a vector, operate on it, and output a vector.

Sounds good to me.


Expose error codes in exceptions (502 Bad Gateway)

Right now there doesn't appear to be a good way to tell specifically what error code Telegram returns in the case of an error, other than looking at the string coming from Telegram::Bot::Exceptions::ResponseError. This approach seems kind of fragile. It would be nice it exposed the numeric code.
My use case for this is that once in a while the Telegram API returns a 502, which is just some temporary gateway error. I'd like my bot to restart itself in this case, but not if the error is a 4xx as it indicates the bot did something wrong and should stop.
I can submit a pull request that implements this, but I was wondering what the best way of doing this is. I could:

Expose the data method that is currently private. This would allow objects to inspect the actual response and take actions based on it. This might have design implications.
Expose a new method, error_code that contains only the error code.
Raise a specific error type for each known Telegram response (one for 409, one for 502, etc). It'd be a lot of new classes.
Code the bot by default to keep trying in case of 502 or even 5xx errors, instead of throwing an exception. This is what the Golang telegram bindings do.

I'm curious to what your thoughts are on this. Like I said, I'm happy to take this and work on it, just want to make sure I'm going in the right direction.

@oslerw to be honest, you can access error code through response attribute (which is an instance of HTTParty::Response). But it smells bad (as end user shouldn't care about gem internals) and we definitely need to expose code as attribute. So, second option is a way to go.

Fixed in 3f566b8


num_epochs vs iters?

Why are only 3 epochs run on windows (cuda) while 1000 iters are run on mlx?

ah thanks for that! the 3 epochs were definitely left there for testing. feel free to tune it higher!

Thanks, i did but ran out of memory. I think the CUDA implementation needs some memory management tweaking.


icao window wrong icon color on default dark theme

almost impossible to see it.

must be something on the css, will check.

Fixed in v1.1.1 - https://github.com/jflores82/simchecklists/commit/9b9992637d738a00f001a63cf1512d40638d16ed
it was on the element itself with a wrong css call.


Shortcut for install/update the last available version with Gradle Wrapper

It would be nice if I could tell Gradle to use the last available stable version with gradle wrapper task. For example with
gradle wrapper --gradle-version=last

Now I have to look at the web and copy the version number to the command line.

Thanks for the proposal. To be honest, I'm not sure such an option would see much usage.
@gradle/developer-experience WDYT?

@marcphilipp as a data point, in nearly every repo we have we have added extra wrapper tasks to update to a nightly/RC/GA.  I think the only contentious point is whether or not we want to treat the services.gradle.org JSON endpoint as a public API. I'll grant you that we upgrade Gradle more than most people would.

I think this is such a good idea that I wrote a spec for this roughly 2 years ago :)
I'm going to give my 👍 here but admit that this isn't the first issue I would personally pick up. I would be happy for us to entertain PRs here.


notif: Require sender_id, server, and realm_uri, rejecting ancient servers' data

These fields are all present since Zulip Server 1.9, and two of them even since 1.8, so it's long past time we should be able to not worry about servers that don't send them. Having them always present will be helpful for the work @AkashDhiman is doing on our Android notification UI, as discussed here:
https://github.com/zulip/zulip-mobile/pull/4842#discussion_r685546372

This PR is a draft because before we start ignoring these notifications from old (pre-1.9) servers, I'd like to set things up so that we log warnings to Sentry when we do so. There's a couple of commits at the start of this branch aimed at doing that, but then I realized that they can't possibly work yet because the Sentry destination (aka "DSN" or "client key") lives only in the JS code, at src/sentryConfig.js, and without that there's no way that the native-Android Sentry SDK can know where a Sentry event should go. So I'll see about fixing that and getting Sentry reporting working from the native Android side, and then this can go atop that.
(Sentry reporting from the native iOS side would be great too -- not so much for our own code, because we don't have much there, but because hopefully it can let us know if there are crashes happening there. That's also another benefit of getting it set up on Android.)
In the meantime, I think all the commits reflect what I'd want to merge once that preparatory work is in.

This PR is a draft because before we start ignoring these notifications from old (pre-1.9) servers, I'd like to set things up so that we log warnings to Sentry when we do so.

Sent that as #4996. Once that's merged, I'll rebase this and mark as ready.

OK, we now have Sentry reporting in our Android-native code, and this PR is ready!

Thanks for the review! Merged.


kinsing malware container

Source ->
https://blog.aquasec.com/threat-alert-kinsing-malware-container-vulnerability
IoC ->
www.traffclick.ru
www.mechta-dachnika-tut.ru
www.rus-wintrillions-com.ru
rus-wintrillions-com.ru
stroitelnye-jekologicheskie-materialy2016.ru

These domains in not registered now:
mechta-dachnika-tut.ru
rus-wintrillions-com.ru
stroitelnye-jekologicheskie-materialy2016.ru
You can check this via official WHOIS here:
https://cctld.ru/en/service/

Thanks Lorenzo, I've added www.traffclick.ru.  Thanks @ammnt  for the assist.
Closing.


ouset:0.1.0

I am submitting

[ ] a new package
[x] an update for a package

I have read and followed the submission guidelines and, in particular, I

[x] selected a name in conformance with the guidelines
[x] added a typst.toml file with all required keys
[x] added a README.md with documentation for my package
[x] have chosen a license and added a LICENSE file or linked one in my README.md
[x] ensured that my submission does not infringe upon the rights of a third party
[x] tested my package locally on my system and it worked
[x] named this PR as name:version of the submitted package
[x] agree that my package will not be removed without good reason

Description: I made some tweaks to the existing package with the same version:

changed the layout mechanism with minor tweaks, which can be regarded as bug fixing
added a new function on top of the other functions, for easier usage
old functions gained a named argument, which gives control over alignment functionality

I have not yet announced this package anywhere, so I guess this fix can still be included in 0.1.0. However, I can also package this as a newer version.

As there are actual behavioural changes and not just docs fixes, this would require a new version of the package, either 0.1.1 or 0.2.0 depending on whether it contains breaking changes.


[Floating Issue] dotnet build runs too long

Description
dotnet build operation runs too long (floating problem), agent fails with one of the next errors:
We stopped hearing from agent Azure Pipelines 2. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error. For more information, see: https://go.microsoft.com/fwlink/?linkid=846610
Child node "2" exited prematurely. Shutting down. Diagnostic information may be found in files in "C:\Users\VssAdministrator\AppData\Local\Temp\" and will be named MSBuild_*.failure.txt. This location can be changed by setting the MSBUILDDEBUGPATH environment variable to a different directory.
Error: The process 'C:\Program Files\dotnet\dotnet.exe' failed with exit code<PHONE_NUMBER>
The same code can be build in range 8-30 minutes. The issue occurs since middle of June.
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions

Virtual environments affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 10.15
[ ] macOS 11
[ ] macOS 12
[ ] Windows Server 2019
[X] Windows Server 2022

Image version and build link
20220710.1
Is it regression?
20220607.3
Expected behavior
dotnet build runs stable
Actual behavior
dotnet build runs non stable
Repro steps
dotnet build -c Release
main .csproj file
<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    <RootNamespace>...</RootNamespace>
  </PropertyGroup>

  <PropertyGroup>
    <!-- This group contains project properties for RazorLight on .NET Core -->
    <PreserveCompilationReferences>true</PreserveCompilationReferences>
    <PreserveCompilationContext>true</PreserveCompilationContext>
  </PropertyGroup>

  ...

</Project>

Hi @flopik3-5, thank you for reporting this one. We will take a look.

Description
dotnet build operation runs too long (floating problem), agent fails with one of the next errors:
We stopped hearing from agent Azure Pipelines 2. Verify the agent machine is running and has a healthy network connection. Anything that terminates an agent process, starves it for CPU, or blocks its network access can cause this error. For more information, see: https://go.microsoft.com/fwlink/?linkid=846610
Child node "2" exited prematurely. Shutting down. Diagnostic information may be found in files in "C:\Users\VssAdministrator\AppData\Local\Temp\" and will be named MSBuild_*.failure.txt. This location can be changed by setting the MSBUILDDEBUGPATH environment variable to a different directory.
Error: The process 'C:\Program Files\dotnet\dotnet.exe' failed with exit code<PHONE_NUMBER>
The same code can be build in range 8-30 minutes. The issue occurs since middle of June.
Platforms affected

[x]  Azure DevOps
[ ]  GitHub Actions

Virtual environments affected

[ ]  Ubuntu 18.04
[ ]  Ubuntu 20.04
[ ]  Ubuntu 22.04
[ ]  macOS 10.15
[ ]  macOS 11
[ ]  macOS 12
[ ]  Windows Server 2019
[x]  Windows Server 2022

Image version and build link
20220710.1
Is it regression?
20220607.3
Expected behavior
dotnet build runs stable
Actual behavior
dotnet build runs non stable
Repro steps
dotnet build -c Release
main .csproj file
<Project Sdk="Microsoft.NET.Sdk.Web">

  <PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    <RootNamespace>...</RootNamespace>
  </PropertyGroup>

  <PropertyGroup>
    <!-- This group contains project properties for RazorLight on .NET Core -->
    <PreserveCompilationReferences>true</PreserveCompilationReferences>
    <PreserveCompilationContext>true</PreserveCompilationContext>
  </PropertyGroup>

  ...

</Project>
```<Project Sdk="Microsoft.NET.Sdk.Web">

net6.0
...

true
true

...

net6.0
...

true
true

...

```

net6.0
...

true
true

...

Hello @flopik3-5. Thank you for your report. Could you please provide a public repository to reproduce the issue.

Hello @flopik3-5, just a gentle ping

Hello @dmitry-shibanov, unfortunately no.

@flopik3-5, we cannot do something without repro. I'm going to close this issue, feel free to reopen it if you can provide it.


Primitive integer not validated correctly

Thanks for this great module! I have started using it, and there are just a few little issues I found.
I've recreated this in your test suite - it is failing but I think should be passing?

see https://github.com/rwalle61/swagger-model-validator/commit/2d27d3aece65a7b2be7a1d1fde83419ff952c1f1
The tests in that file all test that you correctly validate object properties that should be integers, but not whether a primitive integer itself is correctly validated.
I believe this is the cause:
if(targetType !== "object" && targetType !== modelType) {
        return createReturnObject(new Error('Unable to validate a model with a type: ' + targetType + ', expected: ' + modelType));
    }

https://github.com/swagger-model-validator/swagger-model-validator/blob/master/lib/modelValidator.js#L89
When target is an integer, typeof target is 'number', so targetType is 'number' but modelType is integer, so we throw this error

This is not really designed to validate a single primitive.  It is intended to handle more complex json bodies than a single primitive type.
A single primitive type can be more easily validated in your code and doesn't really require swagger awareness.  This is more for the troublesome problems with an entire object being passed in.

I agree single primitive types are pretty easy to validate manually, and so a user wanting to validate their data could just do that.
However, your package is also useful for validating one's OpenAPI spec in automated tests. If I have an OpenAPI spec with this schema:
schemas:
    ProjectID:
        type: integer

Then the test above tests whether I have defined ProjectID correctly.
This may seem a trivial test, because this ProjectID schema seems so easy to write, but this functionality would:

reduce confusion - a ProjectID schema with type: number passes but one with type: integer fails, which made me think for a moment that OpenAPI 3 did not support type: integer.
enable TDD of one's OpenAPI schema definitions. I could write my tests first, then make my OpenAPI docs match them, and then forever my tests and OpenAPI docs would be in sync.
make this package's validation API more complete and consistent, allowing others to build on top of it more easily. I'm developing a Chai plugin and want to let my users validate their data against schema objects easily in Chai. I want to satisfy points 1 and 2 above for them. That will require validator.validate(123, { type: integer }) succeeding, and resolving issues https://github.com/swagger-model-validator/swagger-model-validator/issues/121 and https://github.com/swagger-model-validator/swagger-model-validator/issues/122 (which are about "the troublesome problems with an entire object being passed in")

What do you think?

I managed to fix this test by changing var targetType = typeof target to var targetType = typeOf(target), typeOf being:
function typeOf(variable) {
    if (Number.isInteger(variable)) {
        return 'integer';
    }
    return typeof variable;
}

But then that broke the hasNumberRefTest in testRefModels1.js. I was able to fix it by changing type: number to type: integer, but I think type: number ought to be passing if you supply an integer (OpenAPI docs: "Note that integer as a type is also supported and is defined as a JSON number without a fraction or exponent part.")

I've looked into this and it is caused by a basic check at the top of the stack that assumes all types are objects at first and have properties that may be primitives or objects.
I'v made a change that will treat the root as a primitive or an object based on the model definition.


Fix separators moving when multiple filters deleted - Fix #9887

[x] Redmine Issue: https://redmine.pfsense.org/issues/9887
[x] Ready for review

$ridx was being subtracted as each filter was deleted resulting in separators becoming logically under subsequent filters.
I can not see why this subtraction was required since adding a filter does not require an increase of $ridx.
History likely dictates why it was required so strike this pull request if I am way off the mark.
Local testing has identified no ill effects from this change.

Hold off on this. I've come across another condition where there is still an issue.

Both #6801 and #9887 now work as expected.

Fixed for both Firewall and NAT.


Claim list - has source / has no source

Similar to claim search, claim list should have these filters.

Also need https://github.com/lbryio/lbry-sdk/issues/2942 looked into with this. @jessopb and i always run into this once you have more than 1 claim in mempool


Add storage class support for notebook PVCs

Description

This PR adds support for setting the default storage class for the jupyter tile.
Key changes:

Added storageClassName field to NotebookData type in both frontend and backend.
fix test mocks that where creating a new type

How Has This Been Tested?

enable storage class feature flag
set storage class in dashboard config
spawn a notebook in jupyter tile
check that notebook created is using the storage class in the dashboard config
remove the storage class from the dashboard config
spawn it again and check that it uses the default set in the storage class admin page
turn off the feature flag
spawn it again, check that it uses the default openshift storage class

Test Impact

updated test mocks and added test to make sure default storage class was passed to the backend
Request review criteria:

Self checklist (all need to be checked):

[x] The developer has manually tested the changes and verified that the changes work
[x] Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
[x] The developer has added tests or explained why testing cannot be added (unit or cypress tests for related changes)

If you have UI changes:

[ ] Included any necessary screenshots or gifs if it was a UI change.
[ ] Included tags to the UX team if it was a UI/UX change.

After the PR is posted & before it merges:

[ ] The developer has tested their solution on a cluster by using the image produced by the PR to main

had to fix test @DaoDaoNoCode

Ok i think this is a bit more complicated then it could be. The tables data fetching hook can return a refresh function which only refreshes the recurring run data and not all data. and it will still not force update the whole thing
this is the old (in main now)
https://github.com/user-attachments/assets/19c0c008-a7ab-4c75-884c-ad6c857bc1ee
This is the new
https://github.com/user-attachments/assets/9d93494d-2fdb-4ce1-8455-5e527ff85b60
diff --git a/frontend/src/concepts/pipelines/content/tables/pipelineRecurringRun/PipelineRecurringRunTable.tsx b/frontend/src/concepts/pipelines/content/tables/pipelineRecurringRun/PipelineRecurringRunTable.tsx
index d8fc9e75c..50036f023 100644
--- a/frontend/src/concepts/pipelines/content/tables/pipelineRecurringRun/PipelineRecurringRunTable.tsx
+++ b/frontend/src/concepts/pipelines/content/tables/pipelineRecurringRun/PipelineRecurringRunTable.tsx
@@ -18,7 +18,7 @@ import PipelineRecurringRunTableToolbar from './PipelineRecurringRunTableToolbar

 type PipelineRecurringRunTableProps = {
   recurringRuns: PipelineRecurringRunKFv2[];
-  refreshSingleRecurringRun: (recurringRun: PipelineRecurringRunKFv2) => void;
+  refresh: () => void;
   loading?: boolean;
   totalSize: number;
   page: number;
@@ -34,7 +34,7 @@ type PipelineRecurringRunTableProps = {

 const PipelineRecurringRunTable: React.FC<PipelineRecurringRunTableProps> = ({
   recurringRuns,
-  refreshSingleRecurringRun,
+  refresh,
   loading,
   totalSize,
   page,
@@ -124,7 +124,7 @@ const PipelineRecurringRunTable: React.FC<PipelineRecurringRunTableProps> = ({
         rowRenderer={(recurringRun) => (
           <PipelineRecurringRunTableRow
             key={recurringRun.recurring_run_id}
-            refreshSingleRecurringRun={refreshSingleRecurringRun}
+            refresh={refresh}
             isChecked={isSelected(recurringRun.recurring_run_id)}
             onToggleCheck={() => toggleSelection(recurringRun.recurring_run_id)}
             onDelete={() => setDeleteResources([recurringRun])}
diff --git a/frontend/src/concepts/pipelines/content/tables/pipelineRecurringRun/PipelineRecurringRunTableRow.tsx b/frontend/src/concepts/pipelines/content/tables/pipelineRecurringRun/PipelineRecurringRunTableRow.tsx
index 1787dbecc..c08e61c50 100644
--- a/frontend/src/concepts/pipelines/content/tables/pipelineRecurringRun/PipelineRecurringRunTableRow.tsx
+++ b/frontend/src/concepts/pipelines/content/tables/pipelineRecurringRun/PipelineRecurringRunTableRow.tsx
@@ -19,7 +19,7 @@ import useExperimentById from '~/concepts/pipelines/apiHooks/useExperimentById';

 type PipelineRecurringRunTableRowProps = {
   isChecked: boolean;
-  refreshSingleRecurringRun: (recurringRun: PipelineRecurringRunKFv2) => void;
+  refresh: () => void;
   onToggleCheck: () => void;
   onDelete: () => void;
   recurringRun: PipelineRecurringRunKFv2;
@@ -27,7 +27,7 @@ type PipelineRecurringRunTableRowProps = {

 const PipelineRecurringRunTableRow: React.FC<PipelineRecurringRunTableRowProps> = ({
   isChecked,
-  refreshSingleRecurringRun,
+  refresh,
   onToggleCheck,
   onDelete,
   recurringRun,
@@ -100,7 +100,7 @@ const PipelineRecurringRunTableRow: React.FC<PipelineRecurringRunTableRowProps>
           onToggle={(checked) =>
             api
               .updatePipelineRecurringRun({}, recurringRun.recurring_run_id, checked)
-              .then(() => refreshSingleRecurringRun(recurringRun))
+              .then(() => refresh())
           }
         />
       </Td>
diff --git a/frontend/src/pages/pipelines/global/runs/ScheduledRuns.tsx b/frontend/src/pages/pipelines/global/runs/ScheduledRuns.tsx
index 2639db627..350416ae4 100644
--- a/frontend/src/pages/pipelines/global/runs/ScheduledRuns.tsx
+++ b/frontend/src/pages/pipelines/global/runs/ScheduledRuns.tsx
@@ -16,32 +16,15 @@ import CreateScheduleButton from '~/pages/pipelines/global/runs/CreateScheduleBu
 import { useContextExperimentArchived as useIsExperimentArchived } from '~/pages/pipelines/global/experiments/ExperimentContext';
 import { usePipelineRecurringRunsTable } from '~/concepts/pipelines/content/tables/pipelineRecurringRun/usePipelineRecurringRunTable';
 import PipelineRecurringRunTable from '~/concepts/pipelines/content/tables/pipelineRecurringRun/PipelineRecurringRunTable';
-import { PipelineRecurringRunKFv2 } from '~/concepts/pipelines/kfTypes';
-import { usePipelinesAPI } from '~/concepts/pipelines/context';

 const ScheduledRuns: React.FC = () => {
   const { experimentId, pipelineVersionId } = useParams();
-  const [[{ items: recurringRuns, totalSize }, loaded, error], { initialLoaded, ...tableProps }] =
-    usePipelineRecurringRunsTable({ experimentId, pipelineVersionId });
+  const [
+    [{ items: recurringRuns, totalSize }, loaded, error, refresh],
+    { initialLoaded, ...tableProps },
+  ] = usePipelineRecurringRunsTable({ experimentId, pipelineVersionId });
   const isExperimentArchived = useIsExperimentArchived();

-  const { api } = usePipelinesAPI();
-  const [updatedRecurringRuns, setUpdatedRecurringRuns] = React.useState<
-    PipelineRecurringRunKFv2[]
-  >([]);
-
-  React.useEffect(() => setUpdatedRecurringRuns(recurringRuns), [recurringRuns]);
-
-  const refreshSingleRecurringRun = (recurringRun: PipelineRecurringRunKFv2) => {
-    api.getPipelineRecurringRun({}, recurringRun.recurring_run_id).then((newState) => {
-      setUpdatedRecurringRuns((prevState) =>
-        prevState.map((run) =>
-          run.recurring_run_id === recurringRun.recurring_run_id ? newState : run,
-        ),
-      );
-    });
-  };
-
   if (error) {
     return (
       <Bullseye>
@@ -92,8 +75,8 @@ const ScheduledRuns: React.FC = () => {

   return (
     <PipelineRecurringRunTable
-      refreshSingleRecurringRun={refreshSingleRecurringRun}
-      recurringRuns={updatedRecurringRuns}
+      refresh={refresh}
+      recurringRuns={recurringRuns}
       loading={!loaded}
       totalSize={totalSize}
       {...tableProps}

/retest

/retest

@Gkrumbach07 Can you rebase your PR with main? That should fix the test.

/approve


Update WikiLink syntax to unencoded and fix heading bug

Markdown Link title and WikiLink without URI encoding
Markdown Links (which include the obsidian:// URL scheme) keep the URI encoding for the file path while also using the unencoded version for the Display. WikiLinks do not need to be URI encoded at all.
This change will ensure that WikiLinks are thus created in the unencoded form and that this will also be used for the displayed text in Markdown Links. I acknowledge there might have been a design decision to use URI encoding both for the displayed title as well as the file in the Obsidian URI – if this is the case happy to discuss and understand.
The linkt to a file named My Fabulous Obsidian File.md in Obsidian is currently rendered as follows (Markdown link and WikiLink, respectively):
[My%20Fabulous%20Obsidian%20File](obsidian://advanced-uri?vault=VAULT&file=My%20Fabulous%20Obsidian%20File.md)
[[My%20Fabulous%20Obsidian%20File]]

Whereas with the change, it will be
[My Fabulous Obsidian File](obsidian://advanced-uri?vault=VAULT&file=My%20Fabulous%20Obsidian%20File.md)
[[My Fabulous Obsidian File]]

Fix for a "heading" bug
I always get the #heading version, even if no heading is selected in Alfred. When debugging the script, I saw it processed a string value of undefined on my Systems. This contains an attempt to fix this by testing for "heading" and its value instead of testing for an empty / non empty variable. This was with newer versions of macOS Sonoma, and the newest Alfred Version.

This change will ensure that WikiLinks are thus created in the unencoded form and that this will also be used for the displayed text in Markdown Links. I acknowledge there might have been a design decision to use URI encoding both for the displayed title as well as the file in the Obsidian URI

Actually, it wasn't. So appreciate the fix!


"helm dep build" fails if requirements.yaml contains local dependencies and remote one

Hello
I have a chart that contains two dependencies, one is located in our internal helm registry, one is copied into the charts sub-directory. I can either use "helm dep build" with only the one from the registry or the local one, but not in combination:
$ tree .
|-- Chart.yaml
|-- README.md
|-- charts
|   `-- oraclepdb
|       |-- Chart.yaml
|       `-- templates
|           `-- oraclepdb.yaml
|-- requirements.yaml
|-- templates
|   |-- _helpers.tpl
|   |-- deployment.yaml
|   |-- ingress.yaml
|   |-- secrets.yaml
|   `-- svc.yaml
`-- values.yaml

The helm registry is added:
$ helm repo list
NAME    URL
stable  https://kubernetes-charts.storage.googleapis.com
local   http://<IP_ADDRESS>:8879/charts
mobi    https://git.bitbucket.server/projects/K8S/repos/charts/raw

Using this requirements yaml:
$ more requirements.yaml
dependencies:
  - name: mobi-postgresql
    version: 1.0.1
    repository: "@mobi"
    alias: postgresql
  - name: oraclepdb
    version: 0.0.1

and then "helm dep list"
NAME            VERSION REPOSITORY      STATUS
mobi-postgresql 1.0.1   @mobi           missing
oraclepdb       0.0.1                   unpacked

then trying "helm dep update" fails:
Error: no repository definition for . Please add them via 'helm repo add'
Note that repositories must be URLs or aliases. For example, to refer to the stable
repository, use "https://kubernetes-charts.storage.googleapis.com/" or "@stable" instead of
"stable". Don't forget to add the repo, too ('helm repo add').

for some reason the sub-chart in charts is no longer a local one.
Just using this requirements.yaml and running "helm dep update" works:
dependencies:
  - name: mobi-postgresql
    version: 1.0.1
    repository: "@mobi"
    alias: postgresql

It also works if both sub-charts are copied and extracted already.
I tried pointing to the file using this requirements.yaml:
dependencies:
  - name: mobi-postgresql
    version: 1.0.1
    repository: "@mobi"
    alias: postgresql
  - name: oraclepdb
    version: 0.0.1
    repository: "file://./charts/"

$ helm dep list
NAME            VERSION REPOSITORY              STATUS
mobi-postgresql 1.0.1   @mobi                   missing
oraclepdb       0.0.1   file://./charts/        unpacked

$ helm dep build
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "mobi" chart repository
...Successfully got an update from the "stable" chart repository
...Unable to get an update from the "local" chart repository (http://<IP_ADDRESS>:8879/charts):
        Get http://<IP_ADDRESS>:8879/charts/index.yaml: dial tcp <IP_ADDRESS>:8879: connectex: No connection could be made because the target machine actively refused it.
Update Complete. ⎈Happy Helming!⎈
Saving 2 charts
Downloading mobi-postgresql from repo https://git.mobi.mobicorp.ch/projects/K8S/repos/charts/raw
Save error occurred:  chart metadata (Chart.yaml) missing
Deleting newly downloaded charts, restoring pre-update state
Error: chart metadata (Chart.yaml) missing

this does not download the mobi-postgresql file anymore.
So currently I can only use remote charts or both within the charts sub-directory. But mixing them havong one from remote and one unpacked (in case some chart does not yet offer some values, so we temporarly copy them) does somehow not work.
using helm 2.8.2 on windows.
Is there a workaround?

I am seeing similar issue with helm dependency update - trying to use requirements.yaml to alias and conditionally include local subcharts + pull in remote dependencies.  'helm dependency update' requires a repository path be provided for all entries in requirements.yaml so I added file://./charts/mychart for local subchart.   The dependency update fails with : 'Save error occurred:  directory ../charts/mychart not found' even though the path listed exists.
Commenting out local subcharts when running 'helm dependency update' and then uncommenting before install to get around issue temporarily.

I've been looking into this and have reached some confusing dead ends.
This os.Stat() call in this func https://github.com/kubernetes/helm/blob/master/pkg/resolver/resolver.go#L132 is behaving as if the path does not exist. I copied that function identically to do a smoke test and with identical inputs, the smoke test can find the file path and the func in resolver.godoes not.
I'm not very experienced with go, but I cannot understand how the same os.Stat() call will return different results.

Also experiencing this on mac !

The only workaround that I found for this is to place all the sub charts into a subchart folder and have the requirements.yaml like this (with your example)
dependencies:
  - name: mobi-postgresql
    version: 1.0.1
    repository: "@mobi"
    alias: postgresql
  - name: oraclepdb
    version: 0.0.1
    repository: "file://subcharts/oraclepdb"

But this is kind of ugly in my opinion.
I really would like to have this bug fixed.

@ejether, I am also looking at the helm code and I think I found the reason why the os.Stat() fails to find the folder.
This is because the calling function downloadAll ( https://github.com/kubernetes/helm/blob/b6335b7dfeb0e68952ee914877fe456ecd257779/pkg/downloader/manager.go#L212 ) is renaming the charts folder to "tmpcharts" during the update thus making our unpacked chart not foundable for that duration.

I'll propose a PR to fix this soon. I made it work locally but I need some more testing and unfortunatly there are no tests for that daowloadAll method and I am a Go rooky for writing it from scratch.

Thanks for working on it.

Any progress on this?

I have the same problem

+1

Still seeing the problem

Same problem was also described in issue 5531 - now closed as duplicate.
Two pull requests are opened at the moment: 3987 and 3422.
A workaround is described in above comment.

Experiencing this as well.

Still present in helm 3 Chart.yaml v2

Am I making the correct assumption that if you remove the repository option, it would automatically check in the charts folder?
https://github.com/helm/helm/blob/985827d09a0456551e116805a7c41c32800c85c0/pkg/downloader/manager.go#L219
Seems to be working for me, unless I'm missing something vital.

closing as inactive. Please re-open if this continues to show itself in more recent versions of Helm 3. Thanks.

This issue still persists in Helm 3.3.0.


Update bicep-functions-string.md

Fist example (concatOutput) does not have the word And in it.

@mumian - can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

@felixtsem5 - thank you for your contribution.
#sign-off


Collapse: disable animation

Hi,
it would be useful to be able to disable animation in the "collapse" component as in "modal" (for example via class or data attribute).
Thanks

I think a simple class to the element is enough for the purpose:
.collapse-noanimation {     transition: none; }
So we can close this.
Thanks


Valid for pie charts?

Hi, it is possible to use this plug in for pie charts?
If just possible for bar, where should I copy the plug in inside Chartist folder structure?
Thanks in advance.

Hi @Aldegunde , for using chartist plugings see https://gionkunz.github.io/chartist-js/plugins.html#whats-a-plugin
It really doesn't matter where you place it, as long as you load it in your page ;-) And define it in the plugins array of your chart as described in the above mentioned page.
Will it work for pie's? just try, I didn't write it for that, and it has been some time, But i guess it will at least render something.


Flatten config structures and remove namespace package

Merging this for now. We can work out the details as keep iterating on the new api. LGTM.


fix(DataStore): model reconciliation queue publisher

Pushing this out, prior to being ready to push into mainline ( need to update the rest of the unit tests), becuase there is a slight difference from the suggested approach listed here:
https://github.com/aws-amplify/amplify-ios/issues/755
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

This PR appears to be causing a crash in one of our environments. We're still trying to pinpoint the details of the crash. Will add a bug when we've figured out what's happening

We've released the fix for the regression in 1.3.1.


Improve zsh startup time

My zsh startup time has gone up quite substantially as a result of adding so many plugins. The code being executed should be profiled and pruned accordingly.

It appears that the two biggest timesinks are actually just
source ~/.antigen-repo/antigen.zsh

and
antigen use oh-my-zsh

I'm not sure what we can do about this.

To address the problem of Antigen being slow, we could consider switching to one of these projects:

https://github.com/Tarrasch/antigen-hs
https://github.com/tarjoilija/zgen

To address the problem of Oh-My-Zsh being slow, we could copy the functionality required by our plugins out of Oh-My-Zsh and into .zshrc. This would require some considerable time and effort, though.

I've experienced problems with Antigen not updating its cache properly, and antigen cache-reset sometimes being necessary to get it to realize that the bundle list has changed. Therefore, swapping out Antigen for antigen-hs or zgen would be ideal.

Apparently there are quite a few alternatives to Antigen! See https://github.com/unixorn/awesome-zsh-plugins#frameworks.

We are switched to zplug, and since this will break backwards compatibility I am also refactoring the rest of .zshrc. Progress is on the zplug branch.

Resolved in df4a24e7d49cc01816d3f750826e988c72a05219.


Fix GitHub Pages build error + updates to release docs

Fixed by only having current version listed on site.
Also added gradle task publishSite to update version and javadocs of site.

Codecov Report

Merging #580 into master will decrease coverage by 1.34%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #580      +/-   ##
============================================
- Coverage      59.2%   57.86%   -1.35%
+ Complexity     1230     1220      -10
============================================
  Files           104      104
  Lines          4763     4763
  Branches        706      706
============================================
- Hits           2820     2756      -64
- Misses         1789     1861      +72
+ Partials        154      146       -8

Flag
Coverage Δ
Complexity Δ

#livelocal
20.32% <ø> (-2.19%)
351 <ø> (-25)

#unit
55.02% <ø> (-0.07%)
1170 <ø> (-1)

Impacted Files
Coverage Δ
Complexity Δ

...xenon/adaptors/schedulers/local/CommandRunner.java
0% <0%> (-51.07%)
0% <0%> (-5%)

...on/adaptors/filesystems/local/LocalFileSystem.java
55.47% <0%> (-20.55%)
24% <0%> (-5%)

...tors/schedulers/local/LocalInteractiveProcess.java
53.65% <0%> (-17.08%)
5% <0%> (ø)

...ciencecenter/xenon/utils/LocalFileSystemUtils.java
81.03% <0%> (-1.73%)
59% <0%> (-1%)

...l/esciencecenter/xenon/filesystems/FileSystem.java
73.74% <0%> (-0.8%)
99% <0%> (ø)

...ecenter/xenon/adaptors/schedulers/JobExecutor.java
72.53% <0%> (+0.7%)
36% <0%> (+1%)
:arrow_up:

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 4228f9f...73ce507. Read the comment docs.


Any maven property starting with prefix flyway causing migration to fail

What version of Flyway are you using?
5.0.2
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin, SBT plugin, ANT tasks)
Maven 3.3
What database are you using (type & version)?
Irrelevant
What operating system are you using?
Windows
What did you do?
<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>org.flywaydb-bug</groupId>
    <artifactId>flyway-skip</artifactId>
    <version>5.0.2</version>
    <packaging>jar</packaging>
    <properties>
       <flyway.driver>org.h2.Driver</flyway.driver>
       <flyway.user>sa</flyway.user>
       <flyway.password></flyway.password>
       <flyway.h2.param>MODE=ORACLE</flyway.h2.param>
       <flyway.url>jdbc:h2:./target/test-db;${flyway.h2.param}</flyway.url>
    </properties>
    <build>
        <plugins>
            <plugin>
                <groupId>org.flywaydb</groupId>
                <artifactId>flyway-maven-plugin</artifactId>
                <version>5.0.2</version>
                <executions>
                    <execution>
                        <id>test</id>
                        <goals>
                            <goal>migrate</goal>
                        </goals>
                    </execution>
                </executions>
                <dependencies>
                    <dependency>
                        <groupId>com.h2database</groupId>
                        <artifactId>h2</artifactId>
                        <version>1.4.196</version>
                    </dependency>
                </dependencies>
            </plugin>
        </plugins>
    </build>
</project>

What did you expect to see?
Flyway should run normally, ignoring any project properties that are not supported by plugin and not passed to its configuration.
What did you see instead?
Failed to execute goal org.flywaydb:flyway-maven-plugin:5.0.2:migrate (test) on project flyway-skip:
org.flywaydb.core.api.FlywayException: Unknown configuration property: flyway.h2.param

This works as designed. This feature ensures that typos in important property names are caught early, avoiding potentially disastrous scenarios.
If you really want to use a flyway prefix, just use flyway- instead of flyway..

Looks like a bad design. If you want to "ensures that typos in important property names are caught early" shows it as a warning in the log. Anyway, there is maybe a property that will turn off this check. I have the <flayway.ver> property defined in the root project, and now have to change due to this issue.


Free RAM shows always 0%

Hi BenRoe,
I have installed your Module for the MagicMirror, and after some startinng problems depending on the missing "request-module" it now works fine. The only Problem I have is that "Free RAM" always shows 0%.
I run MagicMirror on a Raspberry Pi 3 B+. The version of MagicMirror is 2.19.0.
Thanks for your advise. :-)
xIExodusIx

Have installed MagicMirror from scratch with all updates and upgrades I could find, now "Free RAM" shows different values.
This Issue can be closed.
Thanks


Missing OpenSSL license phrase in a Huawei project

Hello
A Huawei project use OpenSSL here
But it does not have license phrase in its Readme and doc that are used for advertising.
According to the OpenSSL License, Point 3,

All advertising materials mentioning features or use of this
software must display the following acknowledgment:
"This product includes software developed by the OpenSSL Project
for use in the OpenSSL Toolkit. (http://www.openssl.org/)"

Why are they advertising material?
in the README, Huawei uses its brand name "Huawei" for advertising the project, and mentioning its features of the Huawei product.
in the doc, Huawei invites outside developers to join in, in order to promote its product, and include a complete SDK.

Basically a duplicate of #5404.  Closing.


Cancel request for authenticated session

FBSDKLog: There is already a request for authenticated session. Cancelling active SFAuthenticationSession before starting the new one.
Future<User> signInWithFacebook() async {
    final FacebookLogin facebookLogin = FacebookLogin();
    final FacebookLoginResult result = await facebookLogin.logInWithReadPermissions(['email']);
    if (result.accessToken != null) {
      final AuthResult authResult = await _firebaseAuth.signInWithCredential(
        FacebookAuthProvider.getCredential(accessToken: result.accessToken.token),
      );
      return _userFromFirebase(authResult.user);
    } else {
      throw PlatformException(code: 'ERROR_ABORTED_BY_USER', message: 'Sign in aborted by user');
    }
  }

Getting same error
FBSDKLog: There is already a request for authenticated session. Cancelling active SFAuthenticationSession before starting the new one.
what is the solution to this


fix a duplicated source file: i18n/en.i18n.json

please check this out :)

Oh, good catch, but that code is changing anyway. To avoid submitting PRs on old code please always make them to the devel branch :)


Font size of Open Exchange App Description page is too big

The title "HL7 and SMS Interoperability Demo" is unnecessarily big. And this affects the mobile view of it as well.

done


Support for Note attribute

I see in the swagger documentation that there is support for a longer note (something different than the summary) as part of the Route attribute.
WebAPI Route does not support this, but I dont see that swashbuckle has implemented something for
[Route("/hello", Summary = @"Default hello service.",
Notes = "Longer description for hello service.")]
Is there already support for this in swashbuckle? I can't seem to find it.

just saw in the swaggerconfig
apisingleversion("","").description("")..


Rename 'Material Icons' to 'Google Material Icons'

Adds clutter, and the author is already clear from the license info popover. Won't fix.


SW-3493 Fix duplicate single quotes in notifications

The MessageFormat class, which is used to format localized messages that contain
placeholders, requires single quote characters to be escaped. By default, Spring
only uses MessageFormat if there are actually placeholders. Unfortunately, that
means the escaping rule for single quote characters depends on whether or not the
string happens to have placeholders.
This was causing the added-to-organization notification to have an English title
of, You''ve been added to a new organization! (note the two single quote
characters).
Make the escaping behavior consistent by configuring the resource bundle to always
use MessageFormat even if there are no placeholders.

Current dependencies on/for this PR:

main

PR #1093   👈

This comment was auto-generated by Graphite.


fix(image-with-caption): revert caption requirement

This reverts commit 335a02bd06652e7acadd6a6ff6579a05b210a4a3.
Related Ticket(s)
#6871
#7257
related Slack thread https://cognitive-app.slack.com/archives/C2PLX8GQ6/p1638980498318300
Description
This PR removes the default value and reverts the required caption in the image with caption component
Changelog
New

{{new thing}}

Changed

heading requirement in ImageWithCaption

Removed

default image-with-caption heading value

Thanks, waiting for it to build to double check preview.
BTW, Functional spec is correct. I think the previous issue was referencing an outdated func spec.

@emyarod noticed that this particular test has been flakey on WC. I tried adding the mock for Kaltura but that didn't seem to help, we might need to update the test to accommodate for this so it isn't sporadically failing:


Blinds motor not recognized as such

It is one more of the big family of TS0601 devices.
Would it be possible to introduce an easy way to edit/update these signatures?
At the moment I can't find a way to access these files with hassio and portainer is no longer available.
I'll try custom folder.
Here is my device signature - "YIDI" branded inside-the-blind-tube + battery + rf433 + zigbee motor.
{
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4098, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0051",
"in_clusters": [
"0x0000",
"0x0004",
"0x0005",
"0xef00"
],
"out_clusters": [
"0x000a",
"0x0019"
]
}
},
"manufacturer": "_TZE200_zuz7f94z",
"model": "TS0601",
"class": "zigpy.device.Device"
}

It shows no controls when added.

This needs a quirk I guess seeing as device_type 0x0051 is a SMART_PLUG. You could try to create a quirk yourself and in replacements use zha.DeviceType.WINDOW_COVERING_DEVICE

Thank you - that is interesting.
I have a hassio version. any guidance how to test the quirk without having
RW access to the host?
I tried this below (from here
https://github.com/zigpy/zha-device-handlers/discussions/693)  but it does
not seem to pick up the files from there.
zha:
custom_quirks_path: /config/custom_zha_quirks/
On Mon, Jan 10, 2022 at 10:51 AM Schwick @.***> wrote:

This needs a quirk I guess seeing as device_type 0x0051 is a SMART_PLUG.
You could try to create a quirk yourself and in replacements use
zha.DeviceType.WINDOW_COVERING_DEVICE
—
Reply to this email directly, view it on GitHub
https://github.com/zigpy/zha-device-handlers/issues/1267#issuecomment-1009241737,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATJNEU7TRNIGLFJOYZSDCB3UVMTENANCNFSM5LQ6YXYQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Thanks,
Igor Skobkarev,
@.***

so, after going around it a bit,
I've added a quirk based on tuya_moes window covering (TuyaMoesCover0601)
which had the same input/output clusters and device type, and injected  via
custom_quirks_path config directive.
It is being identified and applied:
2022-01-23 14:29:34 DEBUG (MainThread) [zigpy.quirks.registry] Considering
<class 'tuya_ts0601_cover.TuyaYIDICover0601'>
2022-01-23 14:29:34 DEBUG (MainThread) [zigpy.quirks.registry] Found custom
device replacement for cc:86:ec:ff:fe:b8:b2:41: <class
'tuya_ts0601_cover.TuyaYIDICover0601'>
However when I click the up/down in the Lovelace it goes:
2022-01-23 14:40:00 DEBUG (MainThread) [zhaquirks.tuya]
cc:86:ec:ff:fe:b8:b2:41 Sending Tuya Cluster Command.. Manufacturer is
_TZE200_zuz7f94z Cluster Command is 0x0002, Arguments are ()
2022-01-23 14:40:00 ERROR (MainThread)
[homeassistant.components.websocket_api.http.connection] [2967549456]
'_TZE200_zuz7f94z'
KeyError: '_TZE200_zuz7f94z'
The profile now looks like this:
{
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>,
complex_descriptor_available=0, user_descriptor_available=0, reserved=0,
aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>,
mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice:
142>, manufacturer_code=4098, maximum_buffer_size=82,
maximum_incoming_transfer_size=82, server_mask=11264,
maximum_outgoing_transfer_size=82,
descriptor_capability_field=<DescriptorCapability.NONE: 0>,
*allocate_address=True, *is_alternate_pan_coordinator=False,
*is_coordinator=False, *is_end_device=False, *is_full_function_device=True,
*is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True,
*is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0202",
"in_clusters": [
"0x0000",
"0x0004",
"0x0005",
"0x0102",
"0xef00"
],
"out_clusters": [
"0x000a",
"0x0019"
]
}
},
"manufacturer": "_TZE200_zuz7f94z",
"model": "TS0601",
"class": "tuya_ts0601_cover.TuyaYIDICover0601"
}
The quirk is attached and any suggestions are appreciated.
Thanks
Igor
On Mon, Jan 10, 2022 at 11:12 AM Igor Skobkarev @.***>
wrote:

Thank you - that is interesting.
I have a hassio version. any guidance how to test the quirk without having
RW access to the host?
I tried this below (from here
https://github.com/zigpy/zha-device-handlers/discussions/693)  but it
does not seem to pick up the files from there.
zha:
custom_quirks_path: /config/custom_zha_quirks/
On Mon, Jan 10, 2022 at 10:51 AM Schwick @.***> wrote:

This needs a quirk I guess seeing as device_type 0x0051 is a SMART_PLUG.
You could try to create a quirk yourself and in replacements use
zha.DeviceType.WINDOW_COVERING_DEVICE
—
Reply to this email directly, view it on GitHub
https://github.com/zigpy/zha-device-handlers/issues/1267#issuecomment-1009241737,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATJNEU7TRNIGLFJOYZSDCB3UVMTENANCNFSM5LQ6YXYQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Thanks,
Igor Skobkarev,
@.***

--
Thanks,
Igor Skobkarev,
@.***
"""Tuya based cover and blinds."""
from zigpy.profiles import zha
from zigpy.zcl.clusters.general import Basic, Groups, Identify, OnOff, Ota, Scenes, Time
from zhaquirks.const import (
DEVICE_TYPE,
ENDPOINTS,
INPUT_CLUSTERS,
MODELS_INFO,
OUTPUT_CLUSTERS,
PROFILE_ID,
)
from zhaquirks.tuya import (
TuyaManufacturerWindowCover,
TuyaManufCluster,
TuyaWindowCover,
TuyaWindowCoverControl,
)
class TuyaYIDICover0601(TuyaWindowCover):
"""Tuya blind controller device."""
signature = {
    # "node_descriptor": "NodeDescriptor(byte1=2, byte2=64, mac_capability_flags=128, manufacturer_code=4098,
    #                    maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264,
    #                    maximum_outgoing_transfer_size=82, descriptor_capability_field=0)",
    # "endpoints": {
    # "1": { "profile_id": 260, "device_type": "0x0051", "in_clusters": [ "0x0000", "0x0004","0x0005","0xef00"], "out_clusters": ["0x000a","0x0019"] }
    # },
    # "manufacturer": "_TZE200_zah67ekd",
    # "model": "TS0601",
    # "class": "zigpy.device.Device"
    # }
    MODELS_INFO: [("_TZE200_zuz7f94z", "TS0601")],
    ENDPOINTS: {
        1: {
            PROFILE_ID: zha.PROFILE_ID,
            DEVICE_TYPE: zha.DeviceType.SMART_PLUG,
            INPUT_CLUSTERS: [
                Basic.cluster_id,
                Groups.cluster_id,
                Scenes.cluster_id,
                TuyaManufCluster.cluster_id,
            ],
            OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
        }
    },
}

replacement = {
    ENDPOINTS: {
        1: {
            DEVICE_TYPE: zha.DeviceType.WINDOW_COVERING_DEVICE,
            INPUT_CLUSTERS: [
                Basic.cluster_id,
                Groups.cluster_id,
                Scenes.cluster_id,
                TuyaManufacturerWindowCover,
                TuyaWindowCoverControl,
            ],
            OUTPUT_CLUSTERS: [Time.cluster_id, Ota.cluster_id],
        }
    }
}

The remova/join generates one odd message:
2022-01-23 14:54:55 DEBUG (MainThread) [bellows.zigbee.application]
Received incomingMessageHandler frame with
[<EmberIncomingMessageType.INCOMING_UNICAST: 0>,
EmberApsFrame(profileId=260, clusterId=0, sourceEndpoint=1,
destinationEndpoint=1,
options=<EmberApsOption.APS_OPTION_ENABLE_ROUTE_DISCOVERY: 256>, groupId=0,
sequence=18), 255, -69, 0xeb8a, 255, 255,
b'\x18\xda\x01\x04\x00\x00B\x10_TZE200_zuz7f94z\x05\x00\x00B\x06TS0601']
2022-01-23 14:54:55 INFO (MainThread) [zigpy.device] [0xeb8a] Read model
'TS0601' and manufacturer '_TZE200_zuz7f94z' from <Endpoint id=1
in=[basic:0x0000, groups:0x0004, scenes:0x0005, None:0xEF00]
out=[ota:0x0019, time:0x000A] status=<Status.ZDO_INIT: 1>>
2022-01-23 14:54:55 INFO (MainThread) [zigpy.device] [0xeb8a] Discovered
basic device information for
2022-01-23 14:54:55 DEBUG (MainThread) [zigpy.application] Device is
initialized
2022-01-23 14:54:55 DEBUG (MainThread) [zigpy.quirks.registry] Checking
quirks for _TZE200_zuz7f94z TS0601 (cc:86:ec:ff:fe:b8:b2:41)
2022-01-23 14:54:55 DEBUG (MainThread) [zigpy.appdb] Error handling
'_save_attribute' event with (cc:86:ec:ff:fe:b8:b2:41, 1, 0, 4,
'_TZE200_zuz7f94z') params: FOREIGN KEY constraint failed
On Sun, Jan 23, 2022 at 2:44 PM Igor Skobkarev @.***> wrote:

so, after going around it a bit,
I've added a quirk based on tuya_moes window covering (TuyaMoesCover0601)
which had the same input/output clusters and device type, and injected  via
custom_quirks_path config directive.
It is being identified and applied:
2022-01-23 14:29:34 DEBUG (MainThread) [zigpy.quirks.registry] Considering
<class 'tuya_ts0601_cover.TuyaYIDICover0601'>
2022-01-23 14:29:34 DEBUG (MainThread) [zigpy.quirks.registry] Found
custom device replacement for cc:86:ec:ff:fe:b8:b2:41: <class
'tuya_ts0601_cover.TuyaYIDICover0601'>
However when I click the up/down in the Lovelace it goes:
2022-01-23 14:40:00 DEBUG (MainThread) [zhaquirks.tuya]
cc:86:ec:ff:fe:b8:b2:41 Sending Tuya Cluster Command.. Manufacturer is
_TZE200_zuz7f94z Cluster Command is 0x0002, Arguments are ()
2022-01-23 14:40:00 ERROR (MainThread)
[homeassistant.components.websocket_api.http.connection] [2967549456]
'_TZE200_zuz7f94z'
KeyError: '_TZE200_zuz7f94z'
The profile now looks like this:
{
"node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>,
complex_descriptor_available=0, user_descriptor_available=0, reserved=0,
aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>,
mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice:
142>, manufacturer_code=4098, maximum_buffer_size=82,
maximum_incoming_transfer_size=82, server_mask=11264,
maximum_outgoing_transfer_size=82,
descriptor_capability_field=<DescriptorCapability.NONE: 0>,
*allocate_address=True, *is_alternate_pan_coordinator=False,
*is_coordinator=False, *is_end_device=False, *is_full_function_device=True,
*is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True,
*is_security_capable=False)",
"endpoints": {
"1": {
"profile_id": 260,
"device_type": "0x0202",
"in_clusters": [
"0x0000",
"0x0004",
"0x0005",
"0x0102",
"0xef00"
],
"out_clusters": [
"0x000a",
"0x0019"
]
}
},
"manufacturer": "_TZE200_zuz7f94z",
"model": "TS0601",
"class": "tuya_ts0601_cover.TuyaYIDICover0601"
}
The quirk is attached and any suggestions are appreciated.
Thanks
Igor
On Mon, Jan 10, 2022 at 11:12 AM Igor Skobkarev @.***>
wrote:

Thank you - that is interesting.
I have a hassio version. any guidance how to test the quirk without
having RW access to the host?
I tried this below (from here
https://github.com/zigpy/zha-device-handlers/discussions/693)  but it
does not seem to pick up the files from there.
zha:
custom_quirks_path: /config/custom_zha_quirks/
On Mon, Jan 10, 2022 at 10:51 AM Schwick @.***>
wrote:

This needs a quirk I guess seeing as device_type 0x0051 is a SMART_PLUG.
You could try to create a quirk yourself and in replacements use
zha.DeviceType.WINDOW_COVERING_DEVICE
—
Reply to this email directly, view it on GitHub
https://github.com/zigpy/zha-device-handlers/issues/1267#issuecomment-1009241737,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ATJNEU7TRNIGLFJOYZSDCB3UVMTENANCNFSM5LQ6YXYQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Thanks,
Igor Skobkarev,
@.***

--
Thanks,
Igor Skobkarev,
@.***

--
Thanks,
Igor Skobkarev,
@.***

You need to add the command to this file: https://github.com/zigpy/zha-device-handlers/blob/16f298e9ce293d241592f86573e909f9c32809d0/zhaquirks/tuya/init.py#L104-L123
Possibly see some of my comments here for some instructions: https://github.com/zigpy/zha-device-handlers/issues/1294
If you get the custom quirk working, please PR the changes or send the quirk, so that it can be merged into Home Assistant.


Metrics agent ConfigMap should use cluster name override

When creating a cluster with a name override:
apiVersion: k8ssandra.io/v1alpha1
kind: K8ssandraCluster
metadata:
  namespace: test
  name: demo
spec:
  cassandra:
    serverVersion: 4.1.0
    clusterName: override # <<< name override here
    datacenters:
      - metadata:
          name: dc1
        size: 1
        racks:
          - name: rack1
        storageConfig:
          cassandraDataVolumeClaimSpec:
            storageClassName: standard
            accessModes:
              - ReadWriteOnce
            resources:
              requests:
                storage: 100Mi

The metrics agent ConfigMap is named demo-dc1-metrics-agent-config.
This is inconsistent with other Kubernetes resources (pods, etc) which are named after the override.
This line should use c.Kluster.SanitizedName(). Additionally, it should check that the concatenated name doesn't have more than 253 characters.
We should also audit other generated names to make sure that those rules are consistently applied.

Note: this ticket used to cover invalid DC names too, but that is a more widespread issue so I moved it to a dedicated ticket: #1141.


undefined method `to_i' for date in jekyll 4.0

I updated to the latest Jekyll (or) if on GitHub Pages to the latest github-pages
I ran jekyll doctor to check my configuration
I read the contributing document at https://jekyllrb.com/docs/contributing/

My Environment

Software
Version(s)

Operating System
openSUSE Tumbleweed

jekyll
4.0.0

github-pages
No

Expected Behaviour
Should compile
Current Behavior
Compile error:
Configuration file: /home/guo/git/suse/jekyll-theme/_config.yml
            Source: /home/guo/git/suse/jekyll-theme
       Destination: /home/guo/git/suse/jekyll-theme/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
Traceback (most recent call last):
        33: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/bin/jekyll:23:in `<main>'
        32: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/bin/jekyll:23:in `load'
        31: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/exe/jekyll:15:in `<top (required)>'
        30: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/mercenary-0.3.6/lib/mercenary.rb:19:in `program'
        29: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/mercenary-0.3.6/lib/mercenary/program.rb:42:in `go'
        28: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `execute'
        27: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `each'
        26: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/mercenary-0.3.6/lib/mercenary/command.rb:220:in `block in execute'
        25: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/commands/build.rb:18:in `block (2 levels) in init_with_program'
        24: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/command.rb:89:in `process_with_graceful_fail'
        23: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/command.rb:89:in `each'
        22: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/command.rb:89:in `block in process_with_graceful_fail'
        21: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/commands/build.rb:36:in `process'
        20: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/commands/build.rb:65:in `build'
        19: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/command.rb:28:in `process_site'
        18: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:76:in `process'
        17: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:202:in `render'
        16: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:515:in `render_pages'
        15: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:515:in `each'
        14: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:516:in `block in render_pages'
        13: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/site.rb:523:in `render_regenerated'
        12: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/renderer.rb:61:in `run'
        11: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/page.rb:179:in `trigger_hooks'
        10: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/hooks.rb:101:in `trigger'
         9: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/hooks.rb:101:in `each'
         8: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/hooks.rb:102:in `block in trigger'
         7: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/bundler/gems/jekyll-locale-dc5c46cadd09/lib/jekyll-locale.rb:45:in `block in <top (required)>'
         6: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/bundler/gems/jekyll-locale-dc5c46cadd09/lib/jekyll/locale/mixins/support.rb:16:in `hreflangs'
         5: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/bundler/gems/jekyll-locale-dc5c46cadd09/lib/jekyll/locale/mixins/support.rb:30:in `sibling_data'
         4: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/bundler/gems/jekyll-locale-dc5c46cadd09/lib/jekyll/locale/mixins/support.rb:30:in `map'
         3: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/bundler/gems/jekyll-locale-dc5c46cadd09/lib/jekyll/locale/mixins/support.rb:31:in `block in sibling_data'
         2: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/bundler/gems/jekyll-locale-dc5c46cadd09/lib/jekyll/locale/mixins/support.rb:24:in `publish?'
         1: from /home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/publisher.rb:10:in `publish?'
/home/guo/git/suse/jekyll-theme/vendor/bundle/ruby/2.6.0/gems/jekyll-4.0.0/lib/jekyll/publisher.rb:14:in `hidden_in_the_future?': undefined method `to_i' for #<Date: 2018-01-01 ((2458120j,0s,0n),+0s,2299161j)> (NoMethodError)
Did you mean?  to_s

Code Sample
I am working on this branch https://github.com/openSUSE/jekyll-theme/tree/l10n-feat
bundle exec jekyll serve --trace

Turning off year, month and day archives solved the issue:
jekyll-archives:
  enabled:
    - tags
    - categories
``

At first glance, this issue seems to occur only when you use jekyll-archives and jekyll-locale plugins together. (Let us know if otherwise)..
Regardless, the cause would be because of:
https://github.com/jekyll/jekyll-archives/blob/5ae016be5defc2838d0297c28e3c24cb303bea1d/lib/jekyll-archives/archive.rb#L101-L104
Jekyll's documents tend to have an instance of Time as their date attributes.
The fix for this would be to use Time.new(*args) in the code above.


Traccar Server Webpage Breaks When Zoom is 0

Describe the bug
When server's zoom setting is set to 0, this breaks the react app and causes the page to go "blank" and unable to use. The page initially loads fine, displaying the navigation bar, the devices, the map, etc., but after about 1 second the page "updates" the map and it errors out.

All contents of the app are removed and the user is unable to do anything and must reload the page.
Setting the zoom to a number > 0, fixes the issue.
To Reproduce
Steps to reproduce the behavior:

Go to 'https://{server}:{port}/modern/settings/server'
Within the 'Preferences' find the 'Zoom' setting
Set 'Zoom' to 0
Save Settings
Go to start page at 'https://{server}:{port}/modern'
See blank page after error occurs

Expected behavior
Zoom is 0, so the map view should be fully zoomed out, without error.
Screenshots
Broken page

Console Errors

Desktop (please complete the following information):

OS: Windows 10
Browser: Firefox
Version 101

Additional context
When zoom is set to 0, Traccar Manager also breaks on mobile (Android). Displays a blank white page once error occurs as well. Setting the zoom to a number > 0, fixes the issue.

What version of Traccar?

https://{server}:{port}/api/server says Version 5.0

This issue has already been fixed. Please upgrade.

Next time before filing a bug please make sure you test it on the latest release first.

My apologies! Thank you.


Can you add the list of dependencies( e.g., requirements.txt)?

Hi,
Thank you for publishing the code.
But I couldn't quite make it work without knowing the versions of the libraries used in the code.
so that I'd like you to add the list of dependencies, such as requirements.txt.
Could you please add the list of dependencies when you have time?
Best

Sorry, I could make it work!
Thank you.


Disabling or working around Same-Origin-Policy

<EMAIL_ADDRESS>commented:

It would be great to be able to operate on pages embedding (i)frames which contents are loaded from another domain, eg.:
<!-- location: http://foo.bar/ -->
<frameset>
<!-- ... -->
<frame src="http://baz.bar/" />
</frameset>
Following the standard cross-domain-policy behavior of the browser, it's impossible to retrieve the DOM contents of the frame using JavaScript, so it would be cool to be able to disable this behavior (eg. with some configuration flasg), or at least to access the (i)frame DOM contents.
Discussion: https://groups.google.com/d/topic/phantomjs/sMH7W_5V8wE/discussion

Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #213.
:star2:   3 people had starred this issue at the time of migration.

Disabling web security is a big command-line hammer, and it might actually break webpages that are relying on the silent-failure behavior of cross-domain scripting.  I don't know if this is even possible with the Qt/Webkit API, but something like the Firefox Add-On SDK's notion of "content scripts" [ https://developer.mozilla.org/en-US/Add-ons/SDK/Guides/Content_Scripts ], which run in the context of a webpage and have an intermediate level of privilege between regular page JS and extension JS, might address this and a number of other problems (e.g. #10203).

Due to our very limited maintenance capacity (see #14541 for more details), we need to prioritize our development focus on other tasks. Therefore, this issue will be closed. In the future, if we see the need to attend to this issue again, then it will be reopened.
Thank you for your contribution!