The app closes randomly.

Description
Even when I'm doing nothing, the app closes with no apparent reason.
Windows event viewer:
Faulting application name: files.exe, version: <IP_ADDRESS>, time stamp: 0x6147ad85
Faulting module name: Windows.UI.Xaml.dll, version: 10.0.22000.132, time stamp: 0xdab57acf
Exception code: 0xc000027b
Fault offset: 0x0000000000834110
Faulting process id: 0x34e4
Faulting application start time: 0x01d7bec3bb67f691
Faulting application path: C:\Program Files\WindowsApps\49306atecsolution.FilesUWP_<IP_ADDRESS>_x64__et10x9a9vyk8t\files.exe
Faulting module path: C:\Windows\System32\Windows.UI.Xaml.dll
Report Id: 96111dde-74c4-4234-a4f3-5b378db881e9
Faulting package full name: 49306atecsolution.FilesUWP_<IP_ADDRESS>_x64__et10x9a9vyk8t
Faulting package-relative application ID: App
Steps To Reproduce
No response
Expected behavior
No random crashes.
Files Version
V2
Windows Version
Windows 11 (22000.194)
Relevant Assets
No response

System.Exception: Unspecified error very clear log xD
Do you have some steps to reproduce this?
Does it close after being minimized for a while? Or also while being open but not interacted with? Or while you're using it?


Unexpected key(s) in state_dict

After training my model, i'm having trouble testing my model on images. I'm getting this error message
RuntimeError: Error(s) in loading state_dict for DataParallel:
Missing key(s) in state_dict: "module.Prediction.attention_cell.i2h.weight", "module.Prediction.attention_cell.h2h.weight", "module.Prediction.attention_cell.h2h.bias", "module.Prediction.attention_cell.score.weight", "module.Prediction.attention_cell.rnn.weight_ih", "module.Prediction.attention_cell.rnn.weight_hh", "module.Prediction.attention_cell.rnn.bias_ih", "module.Prediction.attention_cell.rnn.bias_hh", "module.Prediction.generator.weight", "module.Prediction.generator.bias".
Unexpected key(s) in state_dict: "module.Prediction.weight", "module.Prediction.bias".
any advice on this would be helpful

@MattHuntebrinker If your model trained with 'CTC' Prediction, then in testing stage, Prediction should be 'CTC' and make sure not 'Attn'.  Hope is helps.

I think the comment of @bityigoss would solve this issue, thanks!


Make pillow a full dependency

Issue:
Pillow is listed as a package.extra, even though it seems to be explicitly depended upon even when passing images as base64 instead of PIL images.
This seems to happen because the functions that support image formats other than PIL still convert the other formats to PIL during the process (_convert_to_parts, _load_image_from_gcs, etc)
Proposal:
Convert pillow to a full dependency.
Relevant lines:
https://github.com/langchain-ai/langchain-google/blob/main/libs/genai/langchain_google_genai/chat_models.py#L209-L261
Error message:
File "/usr/local/lib/python3.12/site-packages/langchain_google_genai/chat_models.py", line 234, in _url_to_pil
  raise ImportError(
ImportError: PIL is required to load images. Please install it with `pip install pillow`

I'm not sure we want to keep PIL as a required dependency.
Have you tried to install the package with pip install langchain-google-genai[images]?
P.S. We should probably adjust the error message though. Would you be open to send a PR for that, please?

/gcbrun

Yes, I think we should keep PIL as an optional dependency. It is a big package and can result in unnecessarily large file sizes.
The error message should be improved though

it looks to be stale, closing


Unable to log into tenant after migrating from wso2am 3.1.0/3.2.0 to 4.0.0

Description
Unable to log into tenant after migrating from wso2am 3.1.0 or 3.2.0 to 4.0.0 when IS configured as the resident key manager, but able to log into super tenant and any tenant thats created after migration.
Steps to Reproduce
Configure wso2 apim 3.2.0 with IS as resident KM
Migrate 3.2.0 to 4.0.0.
Affected Component
APIM
Version
4.0.0
Environment Details (with versions)
No response
Relevant Log Output
[2022-08-26 11:02:32,706] [cafd7e5f-52c9-480a-a228-ac1c432a703a] ERROR {org.wso2.carbon.core.services.authentication.AuthenticationAdmin} - System error while Authenticating/Authorizing User : Error when handling event : PRE_AUTHENTICATION

Related Issues
No response
Suggested Labels
No response

Could not recreate this issue in 3.2.0-4.0.0 migrated setup.


Instagram API Changes

Used this Git a while back with no issues, however, have you accommodated Instagrams latest API changes to make sure this is still working?

My various sites' went down as well. This no longer works bc of the api changes. /users/self/feed isn't an endpoint now. Perhaps public_content or some such thing?
And ten of you only get up to 20 imgs at once at most in sandbox mode.

It works for me in sandbox mode. But you must now add extra credentials, something like:
var feed = new Instafeed({
  get: 'tagged',
  tagName: 'mytagname',
  clientId: 'xxxxxxxxxxxxxxxxxxxxxx',
  accessToken: 'xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
});
feed.run();

This is for the case where you are just loading content that is in any case public. I've not yet tried the case where the content is private. In this case, the client-side method is probably not a good idea.
Getting the credentials is a slightly annoying process, but followinging this slightly out of date guide should help:
https://github.com/adrianengine/jquery-spectragram/wiki/How-to-get-Instagram-API-access-token-and-fix-your-broken-feed
Notes to the guide above:

You don't need to set up a LAMP as it suggests it not really required and because...
Instagram will not longer accept the localhost:3000 as your redirect URI anymore anyway.
3: Just use your website as the redirect URI and than as the last step it will redirect to your website and you will see something like:
http://mywebsite.com/#access_token=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
You can now just copy your access_token out of the URI.

As far as  I know in sandbox mode you're limited to the latest 20 user posts (not 20 per request, only 20 latest). Did any one figure out how to deal with that? I want to show all posts of an account I own.

@NewDimension I believe you can get "unlimited" access if you've applied and been approved for an app by the Insta team.  That means that you have to have a privacy page, stream (video of what you'll be doing) and I think an https redirect...

Just want to confirm that you now have to have the access token of the user´s images you want to show.
I have no idea whether one can still show images from multiple accounts. Seems like, no, on first glance.

I have read a lot about it today, I wonder why I have not heard about this before, but the instagram API no longer allows any kind of "one-off" projects.
These are the guidelines for what will be approved:
https://www.instagram.com/developer/authorization/


Feature request: add a LICENSE

Hello @mattiasgeniar
Not that I really wanted to resurrect this old repo,
but can I ask you to add a LICENSE to it?
Possibly an open one, like MIT.
I wanted to use it for some tests and since http://infinite-download.ma.ttias.be/ seems always out of bandwith, I would love to self-host it.
Still, I'm a little scared of your full team of lawyers so..

Haha :-)
Sure thing, I added the MIT license in 2fc6779.
Mattias


Change "kevinb7" to "kevinbarabash"

Hi Kevin,
This is a trivial change that simply changes "kevinb7" to "kevinbarabash" in links that point to GitHub.
Commits have been squashed, but I did not build, as I didn't see it necessary with this change.
~ Brynden "Gigabyte Giant" Bielefeld<EMAIL_ADDRESS>

Thanks.  I didn't realize how much of a pain changing user names would be.

No problem. GitHub doesn't really make switching usernames easy. It's kind of one of those "once you pick it you're stuck with it for life" situations, but oh well.

FYI: There is still a mention of the old username in the LICENSE file

Copyright (c) 2014 kevinb7

Also I suspect the date should be changed to (c) 2014-2016 to reflect the continued development?


intergration with vllm and unsloth in webui and/or cli

Reminder

[X] I have read the README and searched the existing issues.

System Info
python 3.10
vllm:latest
Reproduction
do you have any guide or documentation on how to incoporate vllm and unsloth into llamafactory webui and/or cli?
Thanks for your help.
Expected behavior
No response
Others
No response

see https://github.com/hiyouga/LLaMA-Factory?tab=readme-ov-file#deploy-with-openai-style-api-and-vllm
and use llamafactory-cli train -h for documents


data-role="carousel"

Hi Olton!
A little help/hint!
Regardless of the video resolution (ex. 1680x1050 or 1920x1080 or 3840x2160), I would like to display various images (old arcade screen shoots) in the center of the screen with the object data-role="carousel". All screen shoots have a fixed width (640px) and variable height. I use

but the image is displayed full screen.
Is there a way to center in X and Y without resizing them?
Thank you!

You can set a fixed width for the carousel via the data-width = "640" attribute.

This are 2 sample images (same width, different height)

but nothing is changed!

640 without px

Sorry for the "px", but I tried both with and without and nothing has changed.

Fixed in 4.4.1

[x] Carousel: fixed usage attribute data-width, now this attribute applied to max-width css property for carousel

In the current version, slides fill the entire carousel according to its width and the rule for height. You can set the width for the carousel (already fixed). or put the image inside the slide.

I'm added in 4.4.1 new component ImageBox - https://codepen.io/olton/pen/GRqZBVN

Thank you very much!


Embed Youtube Videos

Is your feature request related to a problem?
Would like to be able to embed youtube videos & twitter post to memos post
Describe the solution you'd like
Would like to be able to embed youtube videos & twitter post to memos post
Additional context
No response

That would be a great feature!

I've been working on preview cards for links so let's hope it gets accepted
Only works with twitter/x and youtube video/shorts (but only .com domains)

solid dot - yt video
outlined dot - yt shorts

Hello @saitauthao & @AxelRHD,
I am working on something like this so let's hope it gets accepted.

Warning: Only available for Twitter.com (not X) and Youtube.com (with video and shorts)


Recover from [AggregateError: All promises were rejected] Error: Want for xyz aborted

One of my peers is crashing. When this happens the sending peer is crashing also. I assume because it cannot sync with the crashed other peer anymore. I get:

node:internal/process/promises:289
triggerUncaughtException(err, true /* fromPromise */);
^
[AggregateError: All promises were rejected] {
[errors]: [
Error: Want for bafyreifolbhkz5za75dw5b7tgq45vlc23fwsk3ujxlc6qhv4aft3tuzbhy aborted
at EventTarget. (file:///home/test/orbitdb/src/node_modules/@helia/block-brokers/node_modules/ipfs-bitswap/dist/src/notifications.js:56:24)
at [nodejs.internal.kHybridDispatch] (node:internal/event_target:826:20)
at EventTarget.dispatchEvent (node:internal/event_target:761:26)
at abortSignal (node:internal/abort_controller:371:10)
at AbortController.abort (node:internal/abort_controller:393:5)
at EventTarget.onAbort (file:///home/test/orbitdb/src/node_modules/any-signal/dist/src/index.js:8:20)
at [nodejs.internal.kHybridDispatch] (node:internal/event_target:826:20)
at EventTarget.dispatchEvent (node:internal/event_target:761:26)
at abortSignal (node:internal/abort_controller:371:10)
at AbortController.abort (node:internal/abort_controller:393:5)
]
}

Then the peer is also crashed. To error causing this in the other peer is:

/home/test/orbitdb/src/node_modules/abstract-level/abstract-level.js:133
callback(new ModuleError('Database is not open', {
^
ModuleError: Database is not open
at maybeOpened (/home/test/orbitdb/src/node_modules/abstract-level/abstract-level.js:133:18)
at /home/test/orbitdb/src/node_modules/abstract-level/abstract-level.js:160:13
at process.processTicksAndRejections (node:internal/process/task_queues:77:11) {
code: 'LEVEL_DATABASE_NOT_OPEN',
cause: [Error: IO error: lock orbitdb/1/orbitdb/zdpuAvRjoqLMMnyAdoXD2fZN4Hoz9Q1YXVsYX532ArbT2AwNB/log/_heads//LOCK: already held by process] {
code: 'LEVEL_LOCKED'
}
}

I don't know why the database is locked, maybe because of a previous crash, but I would not assume that a different peer is also crashing when this happens. The LOCK file is still in the directory, maybe it has to be removed?
Can I catch the error somehow in the other client and recover? I cannot find a stack trace from my code, this is all buried by the asynchronous magic of JavaScript.

Wrap the offending lines of code (I.e. the ones throwing the errors) in a try...catch block. The first error looks like a timeout error when retrieving a block from the other peer. The second error is the underlying LevelDB still being locked when you attempt to reopen it. You would need to explicitly close it before attempting to re-open it.
The culprit is likely a communication issue between IPFS peers (hence the ipfs bitswap error).

Wrap the offending lines of code (I.e. the ones throwing the errors) in a try...catch block.

That's the problem. At least in the first case this is not directly executed by my code and the stack trace does not show any of my code. It is happening asynchronously and my code is It seems that the complete DB, orbitdb, IPFS has crashed, i.e. I have to restart the whole program since I cannot add any try ... catch

Can you replicate the issue and post some kind of reproducible code snippet?

Closing with no response. Please feel free if you are able to provide some kind of working example.


Bugzilla query for untriaged Core: General bugs should use the Severity field instead of Priority

From the latest email "[autonag] Bugs to triage for the 2020-05-08" for the Core: General component, the Bugzilla query is still using the Priority field to identify untriaged bugs.
We should update the query to use the Severity field instead so we comply with the current Firefox Bug Triage Process.

The fix for that is being worked on in #953.


Write mode filter :: (overwrite + append) !== (any)

When selecting both "Overwrite" and "Append" options the filter behaves as if none was selected.
Use case
On the Data Sources page, select both write mode options to filter out all sources that were never modified.

Existing Consumer API version 0.7 only accepts a single value filter append: boolean. So I'm moving the ticket to the next major release.


Question. Frame Number?

Im using version 5.1.6 because this is the highest version I am able to use with Expo SDK 49. Everything works fine however, I would like to know is there a way to get the current frame of the LottieView? I tried searching through the values that come from the ref to the LottieView, but I can't find any Animated Values or frame numbers there. I using the play and pause through the ref to the LottieView.

Hi @oiver555,
No, Neither we, nor the native dependencies (as far as I know) have any such method. Can I ask why you need this? Maybe I can recommend an alternative for achieving your goal

Hi @oiver555
It is not exactly the current frame, but you can get the current progress position if you use the AnimatedLottieView show in te example here: https://github.com/lottie-react-native/lottie-react-native?tab=readme-ov-file#usage

Hi @oiver555 It is not exactly the current frame, but you can get the current progress position if you use the AnimatedLottieView show in te example here: https://github.com/lottie-react-native/lottie-react-native?tab=readme-ov-file#usage

Slight clarification, you can set the progress with that prop and have fine-grained control over it, but it won't give you the progress. That one you need to have somewhere separately. You can read more here

Wow thanks much, I eventually found a way around my issue but I'll be sure to remember your comment

Sounds good. Best of luck to you.


Document new reserved keywords

Adding a reserved keyword is a backwards-incompatible change, so as a part of our upgrade documentation and release notes we need to inform our users about any new reserved words in (this list).
For 1.1 there is one new reserved word, current_schema.

Thanks for calling this out, @bdarnell. I have an issue to document this, but it looks like we already regenerated the full grammar for 1.1 and so it's listed already. Did we call this out as a backwards-incompatible change in the 1.1 alpha that introduced it?

We called it out as a new feature in the 20170720 release notes, but not that it was a new reserved word.


Combine names when combining different images into one.

When more than one image is used to build a texture (for example, metal + rough as separate images), the names of the source images need to be combined.
The exporter was doing this until recently when a refactor dropped the feature.  My reimplementation here is a bit more complex, unfortunately, but it tries to "do the right thing" on a bunch of edge cases.
Time permitting, I may try to add tests for this behavior, so it can be called out if it breaks again.

The latest commit to this branch includes the first few entries in a whole new section of the test suite.  Prior to this, the tests just confirm that valid glTFs are being produced, but this change introduces a new section of tests where we start to inspect certain aspects of the results.  This allows the tests to determine if filenames are being combined correctly, and ORM images are being assembled correctly.
There's tons of room to build additional specific tests, but for this PR I'll pause here and see if this new pattern of testing is acceptable to folks here.

Just to make sure I understand the principle: it checks the resulting texture files and their content, but doesn't try to do any validation of the json content?

Wow.  Spent more than a day trying to get those image tests done, and when they finally worked I got excited and totally forgot to check the JSON output.
In my latest commit I'm using JSON.parse on the exported content, and then expecting certain values to be set correctly within that content.
As always, the glTF Validator also runs on the files, as part of the existing test suite, but you knew that.

Cool, LGTM
Maybe we can discuss some general solution to do comparison of JSON content (in separate issue or slack or something).
Btw. looks like Circle has changed something, I can't see uploaded test results or artifacts anymore

Yes, the requirement to be logged into CircleCI in order to see artifacts threw me for a loop last week.

Tests failed when I merged this, but it looks like the failure was during the "download Blender 2.80" step.  Hopefully that's just transient, maybe there's a corrupt bzip file on the server today...

From the logs transfer was interrupted after 22M. Trying same URL from here completes just fine, so maybe just some network glitch. If you have access to retry the build, that may fix things. And once Blender 2.80 goes final we should do a docker image with blender already installed and use that for tests :)

Yes.  It looks to me like Blender 2.79b is also being downloaded each time.  Would love to get that fixed too, but I'd have a lot of reading to do before I tried it myself.

Yeah I ended up making the build script download every time as I don't have access to setup Khronos properly in docker hub, and there didn't seem to be others that had or knew how to do. If someone has the rights I'll be happy to assist in setting it up. I originally had it (with our fork) so that it would trigger new build on docker hub on every push to master. In that way the build script would have the Blender 2.80 version from last push.


Create new labelled data set

Overview
We'll need a high quality labelled data set for ongoing training & evaluation.
Requirements

[x] Sample a larger set of YouTube videos - Ed has done this
[x] Design a richer prompt - Cam has done this
[x] Create a spreadsheet of extracted claims to be labelled - Cam & Ed are doing this
[x] Pass to the health fact checking teanm to annotate - David will do this

Done! (Just waiting for the annotators to annotate.)


Support for version 5.15.8

Hi,
Thanks for this amazing software. It is so much better than what Qt is able to provide :)
Is your feature request related to a problem? Please describe.
I am currently trying to develop an app for android using pyqtdeploy which supports only qt 5. Unfortunately, there is a bug that prevents running on android in 5.15.2 (https://bugreports.qt.io/browse/QTBUG-71590?focusedCommentId=687317).
Describe the solution you'd like
Could it be possible to add support for Qt 5.15.8?
Describe alternatives you've considered
I tried to use Qt 6 but unfortunately pyqtdeploy is not compatible.

Could it be possible to add support for Qt 5.15.8?

Unfortunately not. Qt 5.15.3 - 5.15.8 are paid software, and binaries are not available from the repositories that aqtinstall uses at https://download.qt.io/online/qtsdkrepository/ . If you wish to build from source, the source code for these versions is available at https://download.qt.io/official_releases/qt/5.15/ , but aqtinstall cannot help you do that.
If you need more recent bug fixes than 5.15.2, you could try using 5.12.12. Qt 5.12 is past end-of-life, but the most recent bugfix is dated November 2021 (5.15.2 was released in November 2020).
Good luck with Python Qt development for Android. I know very little about the subject, but it sounds quite difficult.

Thanks a lot for the information. It is a shame that Qt does not provide a better support to the open source community.
Riverbank has done a good job on enabling PyQt for android but unfortunately it seems that they lack some man power to make it easy. Anyway, I will move another project to C++, it will be more easy.
Thanks a lot again for your software, I will clearly continue to use it :)
Best regards,


Open Calendar in Day View instead of Month View

Whenever, I click the calendar button once opening Calendr, it opens the Apple Calendar in Month view. Is there a way to set it to open the Day View of Apple Calendar?

You can double click the dates. It will open in day view on that date.


Faster download link for the driver

The link I provided in Baidu Tieba is hosted on Baidu Net Disk, and it does "takes forever to download there without membership". I did provided more links that hosted on different cloud disk provider, however I can't provide these links on Tieba because they will simply delete my post.
For foreign users that need my modified driver, here is a a link hosted on huang1111 Cloud Disk, based on OneDrive for Business, which should provide faster download speed.
https://pan.huang1111.cn/s/7GqEHg

哇哦~参拜大佬~谢谢大佬给我们写的驱动——

嘿嘿~顺便说下，雨科的官网上有全部的网盘链接。
http://raincandy.1337.moe/nvcmpgpu/


bug fix: SLR CIS map layer redraw

Fixes a couple bugs relating to the Map data layers:

when navigating to a new route/page in the website from the SLR CIS tool the requested page would not load
when navigating back to the SLR CIS tool from another page the map layers would not draw

 Bug: On DEV/BETA SLR-CIS tool has top menu issue


Compiling multiple files in one js

@paparga Thanks for contribution! Gratz on being first pull request :tada:


MAINT: signal: fixed build warning (sprintf) on MacOS

Reference issue

Closes #22086
What does this implement/fix?

Used snprintf instead of sprintf

snprintf requires an argument: number of bytes that will be written to the buffer. The buffer was already initialized with enough size. So just passed the length of the mystr to snprintf

Additional information

Thanks for your first contribution! There are lots of other good first issues at the moment if you're interested

Thank you 😊 I will look into it.


Fortify SSC Credential Management

Storing and encrypting the Fortify SSC credentials, either on the CLI or in a config file.

This functionality was added in #42


tpc-ds qeury82 shuffle data size is abnormal [QST]

when I test tpc-ds query-82, cpu shuffle write data size is 105GB+, while shuffle read data size is 3GB+,
GPU rapids shuffle write and read data size is both 80GB+ , so I compared tow dag  is below :
cpu:

gpu:

I have 2 questions ,

in general , shuffle write data size is equal shuffle write data size , but query-82 shuffle read data is less than write ,why ? what it happend ?
can rapids add this feature to reduce shuffle read data size to improve performance ?

I would have to look at what in the query is reading the shuffle data.  Spark has some operators that stop processing early if they can tell that they don't need to process any more data.  In some cases they can even avoid running entire tasks.  We recently hit one of theses issues with #900. I don't think this is the same issue because query 82 has an order by before the limit, which usually will translate into a TakeOrderedAndProject instead of a regular Limit, but I would have to look into the details of the plan to be sure.

Closing this old issue.  Please reopen if still relevant.


Italian Characters:  ì ù è à ò  cause Segmentation Fault

Hi Ross,
I found an issue on how a4 process Italian character that cause a segmentation fault when it is pressed (è,ì,ù,à or ò) :

$
Program received signal SIGSEGV, Segmentation fault.
__stack_chk_fail () at src/env/__stack_chk_fail.c:17
17      src/env/__stack_chk_fail.c: No such file or directory.
(gdb) bt
#0  __stack_chk_fail () at src/env/__stack_chk_fail.c:17
#1  0x000055555556b4df in render_termwin ()
#2  0x00007ffff7f2b086 in tickit_bindings_run_event () from /lib/libtickit.so.3
#3  0x00007ffff7f391ab in ?? () from /lib/libtickit.so.3
#4  0x00007ffff7f39211 in ?? () from /lib/libtickit.so.3
#5  0x00007ffff7f39211 in ?? () from /lib/libtickit.so.3
#6  0x00007ffff7f39211 in ?? () from /lib/libtickit.so.3
#7  0x00007ffff7f3aee1 in tickit_window_flush () from /lib/libtickit.so.3
#8  0x00007ffff7f3b08c in ?? () from /lib/libtickit.so.3
#9  0x00007ffff7f382d2 in tickit_evloop_invoke_timers () from /lib/libtickit.so.3
#10 0x00007ffff7f2c065 in ?? () from /lib/libtickit.so.3
#11 0x000055555556c855 in main ()

a4-keycodes run outside a4 show the character correctly:

but if I run a4-keycode from a4 terminal the Italian ( ì ù à ò è ) character pressed is not showed at all.

can you help me to solve the segmentation fault and correctly show the Italian characters ?
Many thanks
Max

Thanks for the detailed report. I can reproduce this and will dig in this weekend.

It's all extended ascii chars, so ascii 128-255. a4 can display them, but strips them out when entered in. So, you can open a file with those characters in it and they'll display, but you can't type them in. Working on it.

@littlewing7 what is your LANG setting?

$ echo $LANG
en_US.UTF-8
on the system suffering segFault

I tried to install a4 on VOID for ARM64 (musl)  and here there aren't SEG-FAULT, but the Italian Char are displayed as

I've made debugging progress and am still working on this.

Please try the attached patch. The problem was much larger than I at first thought, so thank you for reporting this! Basically, only ASCII characters could be input, no other Unicode at all. The libtickit procedure that reads keyboard input is converting the Unicode code point to UTF-8 encoding, and then that is sent to the libvterm processor, which expects a code point so attempts to again convert its input to UTF-8 encoding, which of course doesn't work. This patch decodes the UTF-8 encoding for Unicode keyboard input before sending it to libvterm for processing. I will look at making this more efficient later, if this tests OK for you.
$ patch <patch_utf8.txt
patch_utf8.txt

Hi Ross,
patch tested and work fine

great work!
Max

Closing with tag v0.2.2.


Improvements to CSS workflow

Hi! First of all, thanks for the amazing plugin to make reveal.js slides within the Sphinx. I am very happy to found it recently and already used for my last slides.
In total it was very smooth experience, but I'd like to discuss some possible modifications to CSS workflow, while working with sphinx-revealjs.
Custom CSS configuration
revealjs_style_theme allows to use custom reveal.js theme, basic (black, white, etc) or custom. In most cases, this might be enough. For my slides I copied default white theme and provide some updates (mostly for fonts).
While this is OK for one slides, it might be very time-consuming, if I'd like to change the default theme to use somewhen later.
With that in mind about to provide advanced ability to supply custom CSS rules via some extra revealjs_custom_styles config instead?
In that case configuration below allows user to easily switch between reveal.js themes, but do not lose any custom modifications,
revealjs_style_theme = "white"
revealjs_custom_styles = """
.mt-5 {
  margin-top: 3rem !important;
}

.text-muted {
  color: grey !important;
}
"""

Emtpy sections with background
I have a slide with backround,
notitle
-------

.. revealjs_section::
    :data-background-image: _static/lvivpy-9/github-actions.png
    :data-background-size: contain

In that slide I don't want to have notitle header rendered at all. As of now I'm able to do this by using CSS rule,
section[data-background-image="_static/lvivpy-9/github-actions.png"] h3 {
  display: none;
}

But in reality I would like to have some "magic" way to do this without any extra CSS. I don't have an idea now, how it might look, but it widely common pattern to have slides only with background image, but without any text above it.
Fonts improvements
sphinx-revealjs allows to setup custom generic font, as well as include it from Google Fonts. However, I find those features a bit buggy.

v1 of Google Fonts used, while it might be useful to migrate to latest v2
Custom generic font applied only to body, while in reality it should be applied to .reveal class instead
As headers and monospace fonts configured via .reveal h1, .reveal h2, ... & .reveal pre, .reveal code rules, it might be useful to allow setup revealjs_header_font & revealjs_monospace_font as well

With that in mind, I'd like to once again thank you on your work and if you'll be OK with some CSS improvements, I noted above, I would be glad to help with the implementation.

Thank you for using and feedback!
> Custom CSS configuration

With that in mind about to provide advanced ability to supply custom CSS rules via some extra revealjs_custom_styles config instead?

Yes, I plan adding confg for stylesheets to include other css files similar html_css_files .
If you want to customize style in current version, it mabye usefule html_css_files option as workaround (this option work revealjs builder).

Emtpy sections with background

If you want h3 level no-title section, please try to use revealjs_break directive.
example:
some section
------

.. revealjs_break::
   :notitle:
   :data-background-image: _static/lvivpy-9/github-actions.png
   :data-background-size: contain

@attakei
Thanks for your comments.
Was not aware of html_css_files, will try to use it instead of overwriting reveal.js theme.
As well as will try to use your workaround for sections with empty header. Maybe it is good idea to put this case to example slides?

Tried write empty header section demo using revealjs_break that is like your presentation, and I think that it is worked well-done.

Page: https://attakei.github.io/sphinx-revealjs/example-background-only-section.html
Source: https://github.com/attakei/sphinx-revealjs/blob/master/demo/example-background-only-section.rst

In your case,  try replace like following:
(before)
notitle
-------

.. revealjs_section::
    :data-background-image: _static/lvivpy-9/github-actions.png
    :data-background-size: contain

(after)
.. revealjs_break::
    :notitle:
    :data-background-image: _static/lvivpy-9/github-actions.png
    :data-background-size: contain

I read your reST source from https://igordavydenko.com/slides/_sources/lvivpy-9.rst.txt

Hi @attakei,
Yeah,
.. revealjs_break::
    :notitle:
    :data-background-image: _static/lvivpy-9/github-actions.png
    :data-background-size: contain

works as expected. Thanks a lot!

As I started to move my changes to reveal.js theme into separate CSS file, I also remembered another improvement I had in mind.
My slides use tomorrow-night highlight.js theme, while by default zenburn theme loaded. Maybe, it is reasonable to disable loading default highlight.js theme for reveal.js, when it is not expected to be used?

Yes, your thinking are right.
Template includes zenbun.css from first release , beacause I have used higithlght.js already any presentations with reveal.js.
sphinx-revealjs should have used any css explicitly (it would been better to use explicitly than using implicitly)

On current version(>= 0.12.0), set only reveal.css as stylesheet file in sphinx-revealjs.
If you want other theme of highlight.js, insert into it revealjs_css_files (with managing file at your repo).


Add fastv

fastv: an ultra-fast tool to detect viral sequence from sequencing data for detection of viral infectious diseases, like COVID-19

@sfchen
Read the contribution guidelines please.


Tests to ensure content generated by Identity scaffolder is in sync with content in Identity UI package

If we end up with a mismatch, the generated content will not behave the same as intended.

cc @Eilon

This should be a priority as the Identity RCL is not the same as the generated code. See #937

@HaoK - I am going to close this issue since you own both these contents (scaffolding & project creation).


Release new version to fix >8.1 notices

Hi,
Currently we have a working dev-master. Would it be possible to release a new version with these fixes compared to 2.1.2?

Hi @PatrickHuiskens,
give me a day or two. I will check this and try to release the new version soon.

Closing this as v2.2.0 with the PHP8 support has been released.

Hi, sorry never checked this.
It was already in your branch but not released. Thanks!


Shutters and Blinds are not correctly supported

Describe the bug
A Tasmota device that is configured as shutter, will expose:
20:36:13.528 MQT: stat/TM_Shutter/RESULT = {"Shutter1":{"Position":56,"Direction":0,"Target":56,"Tilt":0}}

This is translated / concatenated in the adapter to:

Setting, e.g., Shutter1_Position leads to

sonoff.0
2022-08-27 20:51:06.701
debug
Client [TM_Shutter] pingreq

sonoff.0
2022-08-27 20:50:36.732
debug
[TM_Shutter] Received: stat/TM_Shutter/RESULT = {"Command":"Unknown"}

sonoff.0
2022-08-27 20:50:36.540
debug
Send to "TM_Shutter": cmnd/TM_Shutter/Shutter1_Position = 49

sonoff.0
2022-08-27 20:50:36.540
debug
onStateChange  sonoff.0.TM_Shutter.Shutter1_Position:  {"val":49,"ack":false,"ts":1661626236539,"q":0,"from":"system.adapter.jarvis.0","user":"system.user.admin","lc":1661626236539}

sonoff.0
2022-08-27 20:50:36.540
debug
stateChange  sonoff.0.TM_Shutter.Shutter1_Position:  {"val":49,"ack":false,"ts":1661626236539,"q":0,"from":"system.adapter.jarvis.0","user":"system.user.admin","lc":1661626236539}

The correct command to be send would have been cmnd/TM_Shutter/ShutterPosition1 = 49
Versions:

Adapter version: 2.5.1

Additional context
The issue / bug template here relates to some Amazon adapter

Further issue:
Shutter1_Direction and Shutter1_Target are never updated, although the status information are recieved:

.
.
.
.

sonoff.0
2022-08-27 21:27:09.331
debug
Client [TM_JamieBlind] pingreq

sonoff.0
2022-08-27 21:27:00.068
debug
stateChange  sonoff.0.TM_JamieBlind.SHUTTER1:  {"val":0,"ack":true,"ts":1661628420067,"q":0,"from":"system.adapter.sonoff.0","user":"system.user.admin","lc":1661628420067}

sonoff.0
2022-08-27 21:27:00.066
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":0,"Direction":0,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:27:00.066
debug
process  task:  {"type":"addObject","id":"sonoff.0.TM_JamieBlind.SHUTTER1","data":{"_id":"sonoff.0.TM_JamieBlind.SHUTTER1","common":{"type":"number","role":"state","read":true,"write":false,"name":"TM_JamieBlind  SHUTTER1"},"native":{},"type":"state"}}

sonoff.0
2022-08-27 21:27:00.066
debug
updateState sonoff.0.TM_JamieBlind.SHUTTER1 - 1

sonoff.0
2022-08-27 21:27:00.066
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/SHUTTER1 = 0

sonoff.0
2022-08-27 21:26:59.560
debug
stateChange  sonoff.0.TM_JamieBlind.POWER1:  {"val":"OFF","ack":true,"ts":1661628419559,"q":0,"from":"system.adapter.sonoff.0","user":"system.user.admin","lc":1661628419558}

sonoff.0
2022-08-27 21:26:59.559
debug
stateChange  sonoff.0.TM_JamieBlind.POWER1:  {"val":"OFF","ack":true,"ts":1661628419558,"q":0,"from":"system.adapter.sonoff.0","user":"system.user.admin","lc":1661628419558}

sonoff.0
2022-08-27 21:26:59.558
debug
process  task:  {"type":"addObject","id":"sonoff.0.TM_JamieBlind.POWER1","data":{"_id":"sonoff.0.TM_JamieBlind.POWER1","common":{"type":"string","role":"switch","read":true,"write":true,"storeMap":true,"name":"TM_JamieBlind  POWER1"},"native":{},"type":"state"}}

sonoff.0
2022-08-27 21:26:59.556
debug
updateState sonoff.0.TM_JamieBlind.POWER1 - 2

sonoff.0
2022-08-27 21:26:59.556
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/POWER1 = OFF

sonoff.0
2022-08-27 21:26:59.556
debug
Set State after task: sonoff.0.TM_JamieBlind.POWER1

sonoff.0
2022-08-27 21:26:59.556
debug
process  task:  {"type":"addObject","id":"sonoff.0.TM_JamieBlind.POWER1","data":{"_id":"sonoff.0.TM_JamieBlind.POWER1","common":{"type":"string","role":"switch","read":true,"write":true,"name":"TM_JamieBlind   POWER1"},"native":{},"type":"state"},"cbArg":"OFF"}

sonoff.0
2022-08-27 21:26:59.556
debug
updateState sonoff.0.TM_JamieBlind.POWER1 - 1

sonoff.0
2022-08-27 21:26:59.556
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"POWER1":"OFF"}

sonoff.0
2022-08-27 21:26:58.701
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":4,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:57.697
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":9,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:56.720
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":14,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:55.724
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":19,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:54.696
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":24,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:53.690
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":29,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:52.688
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":34,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:51.725
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":39,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:50.724
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":44,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:49.706
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":49,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:48.714
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":54,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:47.704
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":59,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:46.728
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":64,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:45.726
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":69,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:44.716
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":74,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:43.705
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":79,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:42.794
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":84,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:41.708
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":89,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:40.705
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":94,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:39.704
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":99,"Direction":1,"Target":0,"Tilt":0}}

sonoff.0
2022-08-27 21:26:39.547
debug
[TM_JamieBlind] Received: stat/TM_JamieBlind/RESULT = {"Shutter1":{"Position":100,"Direction":1,"Target":0,"Tilt":0}}

+1 having the same problem...

+1 same problem

@bug84 me too posts helop noone ... Thumbs up in fortst post is only think that is visible


Fixes typo

Hi @victorsolis, this does not appear to be a typo.  JWT's type field is referred to as typ: https://jwt.io/introduction


[FeatureRequest] Display episodes aired today

As far as I understand from the code
		if config.Get().ShowUnairedEpisodes == false {
			if episode.AirDate == "" {
				continue
			}
			firstAired, _ := time.Parse("2006-01-02", episode.AirDate)
			if firstAired.After(now) || firstAired.Equal(now) {
				continue
			}
		}

Elementum gets the current date in UTC (and the time is always 00:00), then tries to convert the air date to UTC as well (without a TimeZone and the time is always 00:00).
This leads to the problem like it isn't possible to watch the episode on the air date and a little bit on the next day (given I live in UTC +2 I can see the episode only after 2am the next day).
Release groups are working really fast nowadays, especially when series are released on the streaming service first.
So would it be possible to add an additional configuration where a user could avoid  "firstAired.Equal(now)" comparison?
Or maybe instead of UTC use system's timezone everywhere.

Hi @Virusmater
I don't think that this code is causing your issue.
I read the code and this is what i can see (unless i missed something):

about time - https://golang.org/pkg/time/
a. Now returns the current local time.
b. UTC returns t with the location set to UTC.

So it will just "standardize" your local time. And then as you noticed, elementum will strip out time from it to get a "standardize" date.
https://github.com/elgatito/elementum/blob/46204e32f7923dad475adc8c7347cb08769f184e/util/time.go#L29-L32
you can run this snippet on your machine to test this "standardization" https://play.golang.org/p/PaPYxkQAbS4

Depending on your settings (i mean Use Trakt information in Trakt lists option) elementum will use tmdb (default) or trakt for air dates.

a. tmdb uses only date and this date looks like a local date for the show's origin country (e.g. for USA show it will use air date for USA time zone). So no UTC there - meaning that date is not "standardize".
for some cases this might lead to a confusion because you might perceive that episode was released yesterday (for your time zone) when it was actually released today or even just will be released today (b/c their time zone is far behind).
on a separate note: for things like anime that are released in a country which TZ is far ahead of your TZ you will see date in future, which maybe is your case.
b. trakt uses already normalized time - i mean converted to UTC. and then elementum strip out time of it.
on a web site trakt uses your TZ (e.g. adds some hours to this UTC time). So you will see real release time for your TZ.
Important note: elementum does not do any time conversion here (and as i mentioned tmbd, for instance, does not provide time at all). It just take provided date and set time to 00:00 UTC (so it can compare 2 days w/o TZ tricks).
This basically means that elementum compares start of the day of the release with start of the user's day.
For USA show and with source of info set to
a. tmdb - for TZ that is far ahead of USA TZ it will actually give you episodes that are not released yet about a day before.
b. trakt - will give you episodes only a few hours before they was really released.
as an example:
reference date - https://www.adultswim.com/videos/final-space/change-is-gonna-come
Saturdays at 10:30p (USA time)
e.g. April 24 2021 22:30.
https://trakt.tv/shows/final-space/seasons/3/episodes/6
$ curl -H @trakt-headers.txt https://api.trakt.tv/shows/final-space/seasons/3?extended=full
"first_aired": "2021-04-25T03:30:00.000Z", <--- they added 5h difference with UTC
so if your TZ is UTC+2 and your date is 25th and your time is more than 02:00 - elementum will compare 25 with 25 and will give you episode. this is quite correct behaviour. the only thing is that episode will be released only at 05:30 your time.
https://www.themoviedb.org/tv/74387-final-space/season/3/episode/6
$ curl -s https://api.themoviedb.org/3/tv/74387/season/3/episode/6?api_key=xxx
"air_date": "2021-04-24", <--- they just use date
so if your TZ is UTC+2 and your date is 24th and your time is more than 02:00 - elementum will compare 24 with 24 and will give you episode. this is kind of correct behaviour. the drawback is that episode will be released only on 25th at 05:30 your time.
But anyway, this means that for USA tv shows, for instance, in elementum you will always see episodes before they actually were released.
So if you are talking about USA shows, then my guess is that either you ran into situation when tmdb/trakt has wrong release date (or episode was leaked) or when release date was changed and your local cache still has old (later) date:
https://github.com/elgatito/elementum/blob/4cfb76705389bbda44af657a76524fa6071a0e2f/cache/types.go#L40
https://github.com/elgatito/elementum/blob/4cfb76705389bbda44af657a76524fa6071a0e2f/cache/types.go#L8
If you are talking about  Asia-Pacific shows, then if episode was released in their morning (so for you it will be evening of the previous day) - then yes, with tmdb you will have to wait for a new day in terms of UTC (02:00 for you) because tmdb does not have time and has a "local" date (i am not sure about local date - it just looks like it. i checked on some popular anime show but  i suggest you to check it for your show).
Since we can't do anything about tmdb - solution for you will be to use info from trakt - enable Use Trakt information in Trakt lists option. Since thakt uses UTC time - elemetum can properly understand the release day. In this case you will see episodes slightly before they actually were released (because we remove time).
As a side note: another notable option here is to "show unaired episodes" which can help with leaked episodes (it smart enough so it will not affect "my progress", only list of episodes inside season).
@elgatito knows more and can correct me if i am wrong.

Anyway, If you can provide real example (with links to tmdb/trakt/offcial release time) then it will be easier to understand why it happens to you.

@Virusmater There is nothing to change in the code. You can disable option to hide unaired episodes.
TMDB does not store time or release, only day. That means that in 1AM you will see all the items for that day.
That is why we check if now is the next day after release date.

Just an example that will work only now and today:
https://trakt.tv/shows/the-handmaid-s-tale/seasons/4/episodes/1
Elementum hides that episode in my timezone (CET) right now, but according to trakt it was released "April 28, 2021 9:00 AM"
I tried both with and without "Use Trakt information in Trakt lists" option.
My problem that I see items only the next day after 2AM, not the same day after 2AM.
Will come back with an output of golang snippet on my machine.

@Virusmater Elementum is using TMDB for that information, not Trakt.

I understand the problem with TMDB has no information about timezone, so Elementum treats Air Date (firstAired) as 28-04-2021 00:00:00 UTC and current datetime (now) as 28-04-2021 00:00:00 UTC.
But I find it really strange when current date is 28-04-2021, Kodi shows air date as 28-04-2021, everywhere around the globe now 28-04-2021 or 29-04-2021 already, but Elementum still hides the season/episode.
I still don't understand why

we check if now is the next day after release date.
wouldn't it be better to check if now (in UTC) is the day of the release or after (in UTC)?

Even if we will take an ideal situation when the user lives in UTC timezone and the episode was aired at the midnight of UTC timezone - the user still will not see the aired episode on the same day. The user will have to wait till the next day because firstAired.Equal(now) will return true.
In case of Episodes released in Japan see even bigger problem:
Let's say right now:

My time right now: 22:30 28 April 2021 (CEST)
Episode was just released in Japan: 05:30 29 April 2021 (GMT+9)
Elementum translates my current time (now) to 00:00 28 April 2021 (UTC)
Elementum translates air date (firstAired) to 00:00 29 April 2021 (UTC)
Elementum checks if the episode should be showed if firstAired.After(now) || firstAired.Equal(now)
firstAired.After(now) == True

That means that Elementum doesn't show the Episode as aired yet. Okay, not much we can do there, let's wait till tomorrow
Then tomorrow:

My time tomorrow: 22:30 29 April 2021 (CEST)
Episode was released already more than 24 hour ago in Japan: 05:30 29 April 2021 (GMT+9)
Elementum translates my current time (now) to 00:00 29 April 2021 (UTC)
Elementum translates air date (firstAired) to 00:00 29 April 2021 (UTC)
Elementum checks if the episode should be showed if firstAired.After(now) || firstAired.Equal(now)
firstAired.After(now) == False
firstAired.Equal(now) == True

That means that Elementum still doesn't show the episode that was aired more than 24 hours ago. Isn't it an issue?
Is my logic is wrong somewhere?
In my situation I would rather see that an episode was aired today, but no torrents are available than no episodes are available at all.
That's why I was saying about the configurable option in Elementum.

so i missed that aired.Equal(now) will trigger continue/return depending on the case.
maybe we really should remove aired.Equal(now)?
also for "my progress" "Use Trakt information in Trakt lists"  will be used. and at least for "user lists". but look like it is not used for just browsing trakt.
anyway with aired.Equal(now) even trakt also will not work for Asian-Pacific.
as a temporary solution - for "my progress" there is "Hide unaired episodes" setting and for browsing - "show unaired episodes".

i mean it works for majority of people because they watch USA tv shows and they usually released in the evening, so for us it a next day and tmdb gives the previous day. but if USA show will be released in the morning - we also will not see it on the same day, since for us it also will be the same day and aired.Equal(now) will screw the logic.

I'm using an integration with Kodi library and don't really use Trakt. If I will check "Show unaired episodes" - then they all will be immediately added to the library and there is no notification or way to know right away when an actual episode will be aired.

we can just introduce the logic that will suppress aired.Equal(now) or we can remove it completely.

either of those will work for me beautifully for me.
actually I'm really surprised that this issue wasn't discussed before.

actually I'm really surprised that this issue wasn't discussed before.

i think that

it works for majority of people because they watch USA tv shows and they usually released in the evening

and i guess that only not very popular Japan's show air in the morning (since the morning is not a time for something popular in general :-) )
so i think current logic works for the majority of the people. and other people probably just ignore this issue :-|

Just decided to check if that logic really works for majority of people living in Europe based on most popular series right now (based on trakt trending).
Current logic works okay with (released late evening in USA and TMDB will show it as yesterday):

The Curse of Oak Island
Supergirl
New Amsterdam
The Blacklist

Current logic will show the episode only the next day (released early morning in USA):

The Handmaid's Tale
Shadow and Bone
For All Mankind
Line of Duty
The Falcon and the Winter Soldier

So yeah, I would rather see those episodes added a bit early to Kodi library than not see them at all and have to go to the torrent search manually. I'm all in to make it configurable or remove aired.Equal(now) for everybody.

If I remember correctly, TMDB does NOT have timezones within air dates.
TMDB is filled by people, who just write in a date in a text field.
That means you get same air date for shows from Japan / US / UK.
And same date, no matter where you live.
Elementum is checking to avoid showing Today premieres. If you want to bypass that check - enable in settings to show unaired episodes.

If I remember correctly, TMDB does NOT have timezones within air dates.
TMDB is filled by people, who just write in a date in a text field.
That means you get same air date for shows from Japan / US / UK.
And same date, no matter where you live.

I fully understand it.
the part I don't understand is why

Elementum is checking to avoid showing Today premieres

I don't want to see all unaired episodes, but I want to see episodes that were aired today. And, if possible, to do it configurable. If the team is strongly against it for some reason - that's fine, you can close this issue.

I think we can do this as a configurable option, that is disabled by default.
"Hide unaired episodes" and "Show unaired episodes" are useful when you need to see leaked episodes, but for this case - not really, since it will "clutter up" your progress, for example.


Wp events

Show events data from a WordPress site, on basic pages (if the option is set to true)
FRONTEND (Gatsby):

gatsby-config.js - added styled components and graphql source plugins
gatsby-node.js - updated schema for show events field
src/components/events.js - new component
src/templates/basic-page.js - show events data

BACKEND (Drupal): multidev

added checkbox field to basic page to show events data (https://wp-events-chug.pantheonsite.io/). Field will be added to other multidevs after PR review

TESTING:
The backend is at https://wp-events-chug.pantheonsite.io/ so you will need to update the ENV variable when running gatsby develop. The page "TEST - New International Students" will show the events at the top of the page. Other pages don't have the field set, so shouldn't show the events.

@abanuog Please create a preview site for this feature branch on Gatsby Cloud as per https://dev.azure.com/uoguelph/CCS/_wiki/wikis/WCM Content Hub Wiki/1395/Previewing-changes-on-Gatsby-Cloud?anchor=using-gatsby-cloud-to-preview-a-multidev-and-feature-branch
See https://www.gatsbyjs.com/dashboard/2e86c058-a370-4898-ae51-9698cd178e8d/sites/e1480ab1-9d0f-4dcb-9fda-75347c74c1c9 and https://www.gatsbyjs.com/dashboard/2e86c058-a370-4898-ae51-9698cd178e8d/sites/4d03c6f6-9271-4faf-8419-e36460e489d7/deploys for examples

Preview site is now available at https://guswpevents.gatsbyjs.io/

Not mergeable due to conflicts


Add core features documentation as includes

Depends on spring-cloud/spring-cloud-dataflow#684

includes new structure
includes stream category with relevant reordered sections
includes task category
includes dashboard category

(once we finalize structure/content, we can then repeat this across other server implementations for consistency)

Its also not rendering correctly.  I'm not seeing anything below:
7.1 Streams
7.1.1 Introduction
I ran the following command :  ./mvnw clean package -DskipTests -P full -am -pl spring-cloud-dataflow-server-cloudfoundry

Actually, I don't understand the include directive with #s

@cppwfs / @ericbottard:
Submitted: spring-cloud/spring-cloud-dataflow#689
With suggestions in the PR above, I'll directly include streams.adoc and dashboard.adoc as includes directly. YARN and K8S implementations would include tasks.adoc as well.

Changes are submitted; however, this PR requires spring-cloud/spring-cloud-dataflow#869, as a prerequisite.

Images are not showing up.  i.e.
images/dataflow-dashboard-about.png
images/dataflow-available-apps-list.png
They may have to be copied from the host project. :-(

Thanks for catching that!
I changed all the /images link to absolute path (in the core docs), so we can then include images in  server specific docs without having to copy them over and maintain as dups. The fix will be addressed in spring-cloud/spring-cloud-dataflow#683.

LGTM

squashed merged


Style/ParallelAssignment for array swapping

I have code like this. I just need to swap two elements in array
array = [1, 2, 3, 4]
array[0], array[1] = array[1], array[0]
p array

rubocop game me this offence:
test.rb:2:1: C: Style/ParallelAssignment: Do not use parallel assignment.
array[0], array[1] = array[1], array[0]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

By documentation of Style/ParallelAssignment cop I cannot understand that is wrong with my code.
Is this a bug in cop, or there is better way to swap elements in my array?
I use
rubocop 0.35.1 (using Parser <IP_ADDRESS>, running on ruby 2.1.6 x86_64-linux)

Is this a bug in cop

Yes. It's a bug.
This cop tries to find an ordering of assignments which doesn't change the meaning of the code. If it can't find one, it's not supposed to issue a warning.

Just a clarification, Rubocop has the same bug for swapping values of hash or object attributes:
All these result in Style/ParallelAssignment offences:
array[0], array[1] = array[1], array[0]
hash[:a], hash[:b] = hash[:b], hash[:a]
point.x, point.y = point.y, point.x

I think the issue stems from the cop seeing these as method calls instead of as assignments. I will try to dig into this cop to fix it.

@alexdowad I may need some help with this one. There was a change in the code to start using NodePattern to check find_valid_order. I am not too familiar with NodePattern. I am sure I could figure it out, but you can probably fix the bug faster than I can. My first thought was to reintroduce the swapping_variables? which was replaced by find_valid_order.

@rrosenblum, no problem. I am just going for dinner now, but will look at it later.

My first thought was to reintroduce the swapping_variables? which was replaced by find_valid_order

swapping_variables? was replaced for good reason. It was only able to identify very basic cases where parallel assignment cannot validly be replaced. find_valid_order is far more robust. It just needs to be updated to handle aref assignments and attribute assignments.

find_valid_order is far more robust. It just needs to be updated to handle aref assignments and attribute assignments.

After looking at the cop, that is what I was thinking. I had some guesses with how it would need to be modified, but I would need to play with it to really figure out how it needs to be changed.

Hey @rrosenblum... just opened a PR which fixes this one.
If you are interested, try reading the comments at the top of node_pattern.rb. The intention is that other developers should be able to pick up the "node pattern" language within 10 minutes -- but if there's anything which is hard to grasp, I will try to make the docs clearer.

I just read over the docs at the top of node_pattern.rb, they seem detailed enough to me. The idea behind NodePattern makes sense to me. I will need to play around with it before I am completely comfortable with it.


Add missing ICreateOptions

Codecov Report

Merging #107 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #107   +/-   ##
=======================================
  Coverage   96.46%   96.46%
=======================================
  Files          99       99
  Lines         904      904
  Branches      120      120
=======================================
  Hits          872      872
  Misses         11       11
  Partials       21       21

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 0cfcdd7...341b6d0. Read the comment docs.

I'm trying to run my project pointing to the github repository but it doesn't seem to build the code when installing. How can I install the package from my branch ?

hey thanks for contributing!
So you want to npm install path/to/github/repo, right?
You could create another branch which includes the compiled files and install this branch. The master only consists of *.ts files.

@RobinBuschmann Thank you for this awesome project!
I just migrated our code base from Model<Instance<T>, T> => Model<T>. At first I was confused, I thought I had to use the sequelize packages types. Then I realized that I can use directly the sequelize-typescript Model typings :).
Yep, I want to do that. I guess I can wait for a little. Any release coming soon ?

Thank you.
I'm planing to release a beta version next weekend.


docs: Improve readability of useRefreshOnFocus

It was not obvious what useRefreshOnFocus hook does at first glance. This PR refactors it to use a firstTimeRef ref to make it clear that we are skipping the first time useFocusEffect is called.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 4.0.0-beta.4 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Unable to connect with SSO to AWS Kubernetes cluster

Describe the bug
When connecting to an algorithm, the following error appears
To Reproduce
Steps to reproduce the behavior:

Go to monokle
try to add a cluster
get the error

Expected behavior
Monokle should be able to connect to the cluster
Screenshots

Desktop (please complete the following information):
(base)  ~/Repos/MT2/MT2-infra/terraform/ [dev] kubectl config view --minify | sed -e 's/(.:) (.)/\1 **************/'
apiVersion: **************
clusters:

cluster:
server: **************
name: **************
contexts:
context:
cluster: **************
namespace: **************
user: **************
name: **************
current-context: **************
kind: **************
preferences: **************
users:
name: **************
user:
auth-provider:
config:
client-id: **************
client-secret: **************
id-token: **************
idp-certificate-authority-data: **************
idp-issuer-url: **************
refresh-token: **************
name: **************
I am using SSO. (edited)

Additional context
Add any other context about the problem here.

Lens and kubectl work without any issue

Not the same issue, but it might be related: https://github.com/kubeshop/monokle/issues/1855.
Can you ask more details about the cloud provider, cluster type (GKE, Kubesprayed, ..), what sort of SSO, etc? These issues are quite hard to resolve without being able to reproduce it.

Hey guys,
Hey @chargio,
Is there any chance to get it fixed anytime soon? :)
It still doesn't work. Got updated today hoping that it's fixed already. :)
But it is not, unfortunately.
I feel like the connection is a basic feature.
Would be nice to get it prioritized a little bit. :)
@olensmar , just FYI ^^

@taras-klym we are working actively on it. Are you in our discord so we can ask you the questions we need to move it forward? We are having problems to replicate the bug to solve it.

Hi @chargio ,
No, I am not. Please send me the link to the discussion.
Or ask what kind of information do you need so that I could provide it here.

Hi @taras-klym We have send you an email to set a quick call. Let us know when you are available

Hi Sergio,
Sure, I will schedule the call via the link you have provided. A bit busy with work-related stuff right now.
Taras Klym
DevOps III (Europe based)
McKinsey & Company
From: Sergio Ocón-Cárdenas @.>
Date: Monday, 21 November 2022, 12:20
To: kubeshop/monokle @.>
Cc: Taras Klym @.>, Mention @.>
Subject: [EXT]Re: [kubeshop/monokle] Unable to connect with SSO to AWS Kubernetes cluster (Issue #2203)
Hi @taras-klymhttps://urldefense.com/v3/__https:/github.com/taras-klym__;!!EIXh2HjOrYMV!aKx7PKzW1h-oUfx9KmaIQHFigMZtekR0qIP0YaOqVlUeS-bCfIIOKJdB56D8BHyu_BeL36brnFGIckLiPUREcXGj0d8HmlzKbTY$ We have send you an email to set a quick call. Let us know when you are available
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https:/github.com/kubeshop/monokle/issues/2203*issuecomment-1321824395__;Iw!!EIXh2HjOrYMV!aKx7PKzW1h-oUfx9KmaIQHFigMZtekR0qIP0YaOqVlUeS-bCfIIOKJdB56D8BHyu_BeL36brnFGIckLiPUREcXGj0d8H6kWdh8o$, or unsubscribehttps://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/AXZOPBUHQIYRF5WOT26PIT3WJNEHTANCNFSM56ATHTKA__;!!EIXh2HjOrYMV!aKx7PKzW1h-oUfx9KmaIQHFigMZtekR0qIP0YaOqVlUeS-bCfIIOKJdB56D8BHyu_BeL36brnFGIckLiPUREcXGj0d8HOae_o0M$.
You are receiving this because you were mentioned.Message ID: @.***>
+=============================================================+
This email is confidential and may be privileged. If you have received
it in error, please notify us immediately, delete the email, and do not
copy it, disclose its contents or use it for any purpose.
+=============================================================+

Can you schedule another meeting using the same link?
Thanks a lot for your help

Workaround:

Open the Kubectl proxy manually, and connect to the proxy with a different kubectl file.
Add it to documentation

Hi @taras-klym We think we have a solution for you. Can you test it?

Hi @taras-klym We think we have a solution for you. Can you test it?

Hi @chargio ,
Have just tried and here what I am seeing while kubectl CLI works.

Regards,
Taras.

Hi @taras-klym We think we have a solution for you. Can you test it?

Hi @chargio , Have just tried and here what I am seeing while kubectl CLI works.
Regards, Taras.

And yeah. I have just updated Monokle to the latest version.

Or it just hangs and all I am seeing is this:

Hi @taras-klym ,
I wanted to reach out and let you know that we've released version 1.13.3, which includes a solution that may help you resolve your issue.
I noticed from the Github issue related to your problem that you've already tried the new version, but I wanted to make sure you were aware of the new Proxy feature that we've added.
This feature is not enabled by default, but it should be able to bypass the authentication and allow you to connect to the cluster.
I've included a link to our documentation below, which provides instructions on how to enable the Proxy feature within Monokle or how to accomplish the same thing manually using the kubectl command.
https://kubeshop.github.io/monokle/cluster-issues/
Let us know if this fixes your issue!

Do we have confirmation that this is working? Did it fix the problem?

Do we have confirmation that this is working? Did it fix the problem?

Hi @chargio ,
I have tried the "enable proxy" trigger in Monokle's settings. It doesn't work. I didn't try the manual method as I don't find it convenient. I have multiple kubeconfigs and changing them manually back and force is not a working solution for me.
About the first (UI based) approach. I think I got the error saying why it doesn't work. Due to sha256 is not supported in Monokle probably.
Here is the message I got while trying to authorize using proxy enabled:

Thanks for your patience, we were expecting the updates to fix it. We are looking for next actions and will come back to you shortly.
It is great that you are willing to help

We have been looking further on the problem and trying to find alternative solutions. We believe it will be easier for us to identify the problems when the new version is delivered in a few weeks, so I am moving this to 2.1.
It is still a high priority for us, and we will continue investigating meanwhile of alternative solutions to the proxy problem we found.

Talk to John to see if we can get more information from his setup (Kubefirst)

We rewrote the connection and it should be working now

Hi @taras-klym - the latest 2.0.10 release should fix the timestamp-related warnings you are getting - still working on the cluster reconnect..

Closing this issue, I created a separate one for the refreshing of oauth2 tokens


Z-Wave lock status is not updated when locked/unlocked by HomeAssitant (i.e. RF operation of the Lock)

Home Assistant release (hass --0.43.2):
Component/platform:
Z-Wave lock model: Schlage BE469NXCEN
Description of problem:
The lock works fine and operates manually as well as via HomeAssistant (RF/Z-Wave operation).  And the lock sensors work fine when operating the lock manually by thumbturn, keypad, key, etc.  However, the status sensors are not updated at all when operated by HomeAssistant via RF/Z-Wave lock/unlock commands.
For example, if I manually unlock the lock with the thumbturn at the lock, I can clearly see the state change in home assistant and the 'alarm-type' sensor (i.e. sensor.schlage_be469nxcen_touchscreen_deadbolt_alarm_type_15_0) updates to a value of 22, which denotes that the lock was "manually unlocked".
In addition, the hidden lock attribute "lock_status" updates to say "Manually Unlocked".
However, if I then proceed to use Home Assistant to re-lock the lock, neither of the two states are updated.  The 'alarm_type' sensor will continue to have the old value of 22, and the 'lock_status' attribute of the lock will continue to say "Manually Unlocked".  Even though the actual state of the lock does change to "locked".  None of the other corresponding sensors or lock_status are updated when operated over Z-Wave/RF network from HomeAssistant.
So the result is that there is no way to know when the lock is operated by HomeAssistant vs physically operated at the lock by a user.
Expected:
When Home Assistant operates the lock via Z-Wave/RF the lock sensors should update to reflect that he lock state has changed.  All sensors, and the 'lock_status' attribute should all be updated to the correct status that reflects the new state based on the Z-Wave/RF operation.
For example, if locked by HomeAssistant the sensors should be updated to the correct numerical value for being locked by RF/Z-Wave, and the 'lock_status' attribute of the lock should say "locked by z-wave command' (or something similar).
And the same should be true for when unlocked by RF/Z-Wave with commensurate status values and message.
Problem-relevant configuration.yaml entries and steps to reproduce:
Simple UI yaml to trigger lock/unlock the Lock via Z-Wave/RF from HomeAssistant:
groups:
  locks:
    name: Locks
    view: yes
    entities:
      - lock.schlage_be469nxcen_touchscreen_deadbolt_locked_15_0

The following values don't change -- from the last values set when the lock is manually/physically operated -- no matter how many lock/unlock commands are sent from HomeAssistant using the loc switch:
DEV Template for Testing:
'lock_status' attribute = {{ states.lock.schlage_be469nxcen_touchscreen_deadbolt_locked_15_0.attributes.lock_status }}

'alarm_type' sensor value = {{ states('sensor.schlage_be469nxcen_touchscreen_deadbolt_alarm_type_15_0') }}

Did the behaviour change in a recent Home Assistant version or was it always this way?
Assuming it was always this way, could you try to reproduce this in ozwcp?
Regardless of ozwcp, when you enter the "bad state", try to run zwave.refresh_node service. Does this bring Hom Assistant to a correct state?

Hi. I am using this lock:

state shows this in dev-states:

But in fact the door is opened .

I also have a polylock (it sucks). Even when the lock was dead for days ozw would still display it as alive.
The RTT times are huge. Could it be that the lock is just not communicating with HA at all?

On the positive side for this lock(poly), I have it working perfectly.  But I had to add a repeater that supported forwarding encrypted packets between the controller and lock who are only placed 10 meters apart.

My lock is maybe 1.5 meters away from the controller . It must be an issue with hass as it worked in 0.41 ...well.. each time I manually had to lock. Then hass would get the right state. When is restart hass sometimes the lock locks itself which is good ..sometimes not. Anyway it is absolutely unstable und unreliable ATM . Is there a way to debug and fix this issue?

@andrey-git
Thanks for the troubleshooting tips.  Here's my findings...
The behavior is wrong even in OZWCP from my testing.  Even in OZWCP, the lock state does not update to reflect the latest when it is operated via Z-Wave/ RF -- it keeps the prior value from when it was last operated via the lock directly/physically (e.g. manually locked, manually unlocked, keypad locked, keypad unlocked).
Here's a screenshot of the OZWCP panel in an invalid state.  I manually locked the lock, hence you see Alarm type 21 value, then I triggered unlock via OZWCP, and the lock physically unlocked, the On/Off updated correctly, but the Alarm Type value still says 21 meaning it was "locked manually".  So the state in this screenshot is invalid because of course now the lock is unlocked.

Per your second question:  every time I try "refresh node" all of the "Alarm Type" and "Alarm Level" values are zeroed out or reset to defaults, and are not updated...  until I manually operate the lock again, in which case the new values are finally refreshed.  This seems to be the same in both OZWCP as well as HomeAssistant.
Thanks!

This sounds familiar to an issue I've got with a Yale YRD220. Certain states (Auto relock for one) don't update the lock status in Hass. I assume it has something to do with this comment and I've looked around in the zwave lock component but don't have a good solution that doesn't just add another exception like the polylock.

@raerae1616 Wanna share your sensor config?

@roflmao sure thing....
Sensor I'm using for the "Office/Back Door" above in the screenshot:
sensor: !include_dir_merge_list sensors/

###Security Locks Sensors.yaml file

- platform: template
   sensors:

     office_door_lock_status:
       entity_id: lock.schlage_be469nxcen_touchscreen_deadbolt_locked_15_0
       value_template: >-
           {% set lock_status = states.lock.schlage_be469nxcen_touchscreen_deadbolt_locked_15_0.attributes.lock_status %}
           {% set lock_status = lock_status|replace('user 1', 'Mickey Mouse') %}
           {% set lock_status = lock_status|replace('user 2', 'Minnie Mouse') %}
           {{ lock_status }}

Locks Group to generate the above screenshot in the UI:
groups:
  locks:
    name: Locks
    entities:
      - sensor.office_door_lock_status
      - lock.schlage_be469nxcen_touchscreen_deadbolt_locked_15_0

I'm having slightly different state issues with my YRD210, where the alarm type is correct and the lock status text is always accurate, but the Lock / Unlock status is never updated.
Why is this line a workaround instead of the default?  I'm pretty sure that would fix my issue.

My experience is different from @droberts84.  The Alarm Type only updates when lock state changes are initiated directly from teh physical lock.  Anytime I use the lock/unlock service in Home Assistant the Alarm type status (and therefore the 'lock_status' attribute) are never updated.
I have created a franken-workaround using a combination of Template Switch, and Input Select to store my custom state (e.g. locked_by_hass, unlocked_by_hass), and an automation to keep things in sync (e.g. reset the InputSelect value when state changes form the physical lock), and finally a custom sensor to aggregate these states into a working LockStatus sensor result.  But, this has to be done for each and every lock -- I may port this into an AppDaemon if/when I get some time to tinker more with it.
Here's the Sensor config that uses the state of the InputSelect, and the Lock itself (supported by the TemplateSwitch, and Lock Automation):
     office_door_lock_state:
        #NOTE: To ensure consistent updates, we link to the update of the zwave entity id, and not the lock!
        entity_id:
          - sensor.schlage_be469nxcen_touchscreen_deadbolt_alarm_type_23_0
          - input_select.lock_hass_status_for_office_back_door_lock
          - zwave.schlage_be469nxcen_touchscreen_deadbolt_23
        value_template: >-
            {% set alarm_type = states('sensor.schlage_be469nxcen_touchscreen_deadbolt_alarm_type_23_0') %}
            {% set alarm_level = states('sensor.schlage_be469nxcen_touchscreen_deadbolt_alarm_level_23_1') %}
            {% set hass_state = states('input_select.lock_hass_status_for_office_back_door_lock') %}

            {#- Z-Wave/RF Lock: Alarm State 0x01 (???) -#}
            {%- if hass_state == 'locked_by_hass' -%}
                {{ 'locked with Home Assistant' }}

            {#- Z-Wave/RF Unlock: Alarm State 0x01 (???) -#}
            {%- elif hass_state == 'unlocked_by_hass' -%}
                {{ 'unlocked with Home Assistant' }}

            {# Manually Locked: Alarm State 0x15 (21) #}
            {% elif alarm_type == '21' %}
                {{ 'locked manually with key cylinder or inside thumb turn' }}

            {#- Manual Unlock: Alarm State 0x16 (22) -#}
            {%- elif alarm_type == '22' -%}
                {{ 'unlocked manually with key cylinder or inside thumb turn' }}

            {#- Keypad Lock by keypad touch (lock & leave): Alarm State 0x12 (18) -#}
            {%- elif alarm_type ==  '18' -%}
                {{ 'locked with keypad' }}

            {#- Keypad Unlock: Alarm State 0x13 (19) -#}
            {%- elif alarm_type == '19' -%}
                {{ 'unlocked with keypad by user ' ~ alarm_level }}

            {%- else -%}
                {#- The lock status is sometimes unknown when HASS boots and Z-Wave is initialized.  In this case
                    we want to use the last state reported by the lock itself (physically) if possible, otherwise
                    we return 'unknown' -#}
                {# {{ 'unknown' }} #}
                {% set state = states.lock.schlage_be469nxcen_touchscreen_deadbolt_locked_23_0 %}
                {% set status = (state.attributes.lock_status if state else '')|trim() %}
                {% set result = status if status != '' else 'unknown' %}
                {{ result|lower() }}
            {%- endif -%}

Bummer that this was closed... this is definitely a bug, somwhere in the machine . . . .


Update configure-endpoints-gp.md

updated policy location

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/5327

@mjcaparas Please merge this PR. Thanks


Removes older version of JDK

I was updating a RedHat server and the latest JDK7 updated as expected, set itself as latest and default (as expected since I set that flag). However, it removed the existing JDK version. It still works for what I need it to do but I expected the new JDK would be set as latest and the old version would remain.
Thanks for all the hard work. Steve

@staylorx for Debian-based systems I believe the packaging is done differently so I can have 2 versions and the default makes sense.
on RedHat systems I'm installing a RPM so installing a newer version will replace the older one.
I'd need to use a tarball and make some extra configs to support multiple versions.

I think I went down a path with the set-default flag thinking that might keep the older one. But I get it now. Thanks for jumping on this so quickly. Amazing.

It's a valid point and I'll keep the issue open.
I'll probably release a v5 version of this role that just uses tarball and installer (which means it would work for all platforns, even Mac).
Problem is time to do it :)
On Mar 1, 2016 7:08 PM, Steve Taylor<EMAIL_ADDRESS>wrote:I think I went down a path with the set-default flag thinking that might keep the older one. But I get it now. Thanks for jumping on this so quickly. Amazing.
—Reply to this email directly or view it on GitHub.

Will you (did you) keep a flag if you actually want it to remove older versions?

No.
I believe it requires a new implementation of this role that doesn't use a debian package to install JDK and it's not a priority for me.
Feel free to make a pull request and I'll check it out.
On May 21, 2016 3:58 PM, Philip Morrison<EMAIL_ADDRESS>wrote:Will you (did you) keep a flag if you actually want it to remove older versions?
—You are receiving this because you were assigned.Reply to this email directly or view it on GitHub


The anchor links are still broken

To test go to your own repo page:
https://github.com/Kir-Antipov/GitHub-Defreshed

Then hover over one of the headers and click on the anchor

It refreshes the page inline and does not link to the anchor

Originally posted by @ccampbell in https://github.com/Kir-Antipov/GitHub-Defreshed/issues/5#issuecomment-652629659

Fixed in v1.3.5


device_type="gpu" loses determinism for randomness

Fixing seeds in LGBM Regressor does not work as soon as device_type='gpu' is activated. The results vary randomly despite fixing seeds.
(Tested with Python lightgbm 2.3.0)

I think we don't provide the fixed seed for GPU version now.
ping @huanzhang12

@Gerenuk Have you tried to set gpu_use_dp parameter?
https://lightgbm.readthedocs.io/en/latest/Parameters.html#gpu_use_dp

@StrikerRUS
With gpu_use_dp=True it becomes reproducible again.
Btw, I'm using the "nomkl" setup if that matters.
I'm working on my data and not sure how to create a minimal example :/

@Gerenuk
Great! Then it's expected behaviour and no repro is needed.
https://lightgbm.readthedocs.io/en/latest/FAQ.html#when-using-lightgbm-gpu-i-cannot-reproduce-results-over-several-runs