text:
no popups on

Disabled buttons don't seem to be able to have popups, which would be nice for explaining why the button is disabled. https://codesandbox.io/s/v-tooltip-disabled-button-fj0oj

The same goes for <input type="text" disabled="disabled">
Did you find a solution to this?

Found this as a workaround: https://github.com/Akryum/v-tooltip/issues/125

Duplicate of #125

source: gharchive/issue

authors: Akryum p0psicles reed-jones

repo: Akryum/v-tooltip

license: MIT

license_type: permissive

license_source: github-api


text:
Status eines Schalters auslesen möglich?

Hallo,
gibt es eine Möglichkeit den Status eines Schalters auszulesen?
Erkannt wird er ja korrekt aber leider sieht man nur den Zustand der Batterie, den Zeitstempel der letzten Aktion, Name und den "Alive" Status.

Leider nein. Der Adapter kann nur anzeigen, was das Gateway an Infos bereit stellt. Der Schalterstatus gehört leider nicht dazu.


text:
[2.3.2.1.3] Refine User Interface Requirements

Issue Details
Description
Refine the User Interface Requirements based on the feedback given.
Success or Completion Criteria
A table showcasing the changes made to our User Interface Requirements.
Allocated Time
3 Days
Start Date: 16/10/23, 0900
End Date: 18/10/23, 2359

Issue Comments
Description
Based on the Feedback given to our team, we made changes to most of the UIRs as they did not meet the 7 requirements.
Changes to success or completion criteria? y/n (if y, describe
No Changes, Criteria Completed!
Start Date: 16/10/23, 0900
End Date: 18/10/23, 2359


text:
M1 Reflection - Yue Qian

What are the great things that your team is doing?
Effective communication, working together and improving our work as we learn along the weeks
Are there anything in the team that wish could be changed?
Delegation
Do you have ideas that could improve the current situation of your team?
More regular and meaningful team meetings to stay updated on the group progress


text:
Assign Objects to Domains: Shortcomings

The current implementation has a few shortcomings that need to be addressed:

There's no batching support ("If the count of requested objects is lesser than 1000, then it runs synchronously, otherwise asynchronously."): Clarify/discuss whether batching support is required.
"For recursive additions, the request allows a maximum of 99 objects at a time." => currently there's no logic around this requirement mentioned on the dev portal.
Different return types for sync and async responses. They should be both based on the JobDetails data class.

For the last point ("Different return types for sync and async responses"), code adjustments will be made as part of #32

repo: Alation/Allie-SDK


text:
about particles

Dear author，i have a question.
What does the color of the particles represent
speed? direction? or？
could u explain it to me？

The color represents the speed.
------------------ 原始邮件 ------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com>;
发送时间: 2020年10月8日(星期四) 上午8:55
收件人: "AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com>;
抄送: "Subscribed"<subscribed@noreply.github.com>;
主题: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
Dear author，i have a question.
What does the color of the particles represent
speed? direction? or？
could u explain it to me？
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Thank you very much for your generous answer.
Another question,when the earth is operated , the wind field will be redrawn. How to cancel this?
------------------ 原始邮件 ------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com>;
发送时间: 2020年10月9日(星期五) 中午11:08
收件人: "AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com>;
抄送: "啥也不会的小菜鸟"<984281379@qq.com>;"Author"<author@noreply.github.com>;
主题: Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
The color represents the speed.
------------------ 原始邮件 ------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com>;
发送时间: 2020年10月8日(星期四) 上午8:55
收件人: "AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com>;
抄送: "Subscribed"<subscribed@noreply.github.com>;
主题: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
Dear author，i have a question.
What does the color of the particles represent
speed? direction? or？
could u explain it to me？
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

In my opinion, it cannot be cancelled. Every time I operate the earth, I need to update the current viewport parameters, including the camera angle of view, the latitude and longitude range of the visible area, etc. At the same time, because it is based on webgl, I need to clear the frame buffer and the particle texture of the last time for each operation and recreate it. If you cancel these operations, the visualization will be messy, and the last wind field traceand the current tracewill overlap.
------------------ 原始邮件 ------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com>;
发送时间: 2020年10月9日(星期五) 下午5:02
收件人: "AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com>;
抄送: "Albert.Ejiestein"<1510342484@qq.com>;"Comment"<comment@noreply.github.com>;
主题: Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
Thank you very much for your generous answer.
Another question,when the earth is operated , the wind field will be redrawn. How to cancel this?
------------------ 原始邮件 ------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com>;
发送时间: 2020年10月9日(星期五) 中午11:08
收件人: "AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com>;
抄送: "啥也不会的小菜鸟"<984281379@qq.com>;"Author"<author@noreply.github.com>;
主题: Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
The color represents the speed.
------------------&nbsp;原始邮件&nbsp;------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com&gt;;
发送时间:&nbsp;2020年10月8日(星期四) 上午8:55
收件人:&nbsp;"AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com&gt;;
抄送:&nbsp;"Subscribed"<subscribed@noreply.github.com&gt;;
主题:&nbsp;[AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
Dear author，i have a question.
What does the color of the particles represent
speed? direction? or？
could u explain it to me？
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Is there any way to solve this problem?
------------------ 原始邮件 ------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com>;
发送时间: 2020年10月9日(星期五) 下午5:19
收件人: "AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com>;
抄送: "啥也不会的小菜鸟"<984281379@qq.com>;"Author"<author@noreply.github.com>;
主题: Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
In my opinion, it cannot be cancelled. Every time I operate the earth, I need to update the current viewport parameters, including the camera angle of view, the latitude and longitude range of the visible area, etc. At the same time, because it is based on webgl, I need to clear the frame buffer and the particle texture of the last time for each operation and recreate it. If you cancel these operations, the visualization will be messy, and the last wind field traceand the current tracewill overlap.
------------------ 原始邮件 ------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com>;
发送时间: 2020年10月9日(星期五) 下午5:02
收件人: "AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com>;
抄送: "Albert.Ejiestein"<1510342484@qq.com>;"Comment"<comment@noreply.github.com>;
主题: Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
Thank you very much for your generous answer.
Another question,when the earth is operated , the wind field will be redrawn. How to cancel this?
------------------&nbsp;原始邮件&nbsp;------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com&gt;;
发送时间:&nbsp;2020年10月9日(星期五) 中午11:08
收件人:&nbsp;"AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com&gt;;
抄送:&nbsp;"啥也不会的小菜鸟"<984281379@qq.com&gt;;"Author"<author@noreply.github.com&gt;;
主题:&nbsp;Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
The color represents the speed.
------------------&amp;nbsp;原始邮件&amp;nbsp;------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com&amp;gt;;
发送时间:&amp;nbsp;2020年10月8日(星期四) 上午8:55
收件人:&amp;nbsp;"AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com&amp;gt;;
抄送:&amp;nbsp;"Subscribed"<subscribed@noreply.github.com&amp;gt;;
主题:&amp;nbsp;[AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
Dear author，i have a question.
What does the color of the particles represent
speed? direction? or？
could u explain it to me？
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

In this project, the effect you want cannot be achieved.
------------------ 原始邮件 ------------------
发件人: "Rookiemin"<notifications@github.com>;
发送时间: 2020年10月10日(星期六) 下午3:02
收件人: "AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com>;
抄送: "Albert.Ejiestein"<1510342484@qq.com>; "Comment"<comment@noreply.github.com>;
主题: Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
Is there any way to solve this problem?
------------------ 原始邮件 ------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com>;
发送时间: 2020年10月9日(星期五) 下午5:19
收件人: "AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com>;
抄送: "啥也不会的小菜鸟"<984281379@qq.com>;"Author"<author@noreply.github.com>;
主题: Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
In my opinion, it cannot be cancelled. Every time I operate the earth, I need to update the current viewport parameters, including the camera angle of view, the latitude and longitude range of the visible area, etc. At the same time, because it is based on webgl, I need to clear the frame buffer and the particle texture of the last time for each operation and recreate it. If you cancel these operations, the visualization will be messy, and the last wind field traceand the current tracewill overlap.
------------------&nbsp;原始邮件&nbsp;------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com&gt;;
发送时间:&nbsp;2020年10月9日(星期五) 下午5:02
收件人:&nbsp;"AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com&gt;;
抄送:&nbsp;"Albert.Ejiestein"<1510342484@qq.com&gt;;"Comment"<comment@noreply.github.com&gt;;
主题:&nbsp;Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
Thank you very much for your generous answer.
Another question,when the earth is operated , the wind field will be redrawn. How to cancel this?
------------------&amp;nbsp;原始邮件&amp;nbsp;------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com&amp;gt;;
发送时间:&amp;nbsp;2020年10月9日(星期五) 中午11:08
收件人:&amp;nbsp;"AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com&amp;gt;;
抄送:&amp;nbsp;"啥也不会的小菜鸟"<984281379@qq.com&amp;gt;;"Author"<author@noreply.github.com&amp;gt;;
主题:&amp;nbsp;Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
The color represents the speed.

------------------&amp;amp;amp;nbsp;原始邮件&amp;amp;amp;nbsp;------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com&amp;amp;amp;gt;;
发送时间:&amp;amp;amp;nbsp;2020年10月8日(星期四) 上午8:55
收件人:&amp;amp;amp;nbsp;"AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com&amp;amp;amp;gt;;
抄送:&amp;amp;amp;nbsp;"Subscribed"<subscribed@noreply.github.com&amp;amp;amp;gt;;
主题:&amp;amp;amp;nbsp;[AlbertEjiestein/Wind-Field-Cesium] about particles (#5)

Dear author，i have a question.
 What does the color of the particles represent
 speed? direction? or？
 could u explain it to me？

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

okey！  I get it.
Thank you very much for your generous answer.
------------------ 原始邮件 ------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com>;
发送时间: 2020年10月10日(星期六) 下午3:06
收件人: "AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com>;
抄送: "啥也不会的小菜鸟"<984281379@qq.com>;"Author"<author@noreply.github.com>;
主题: Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
In this project, the effect you want cannot be achieved.
------------------ 原始邮件 ------------------
发件人: "Rookiemin"<notifications@github.com>;
发送时间: 2020年10月10日(星期六) 下午3:02
收件人: "AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com>;
抄送: "Albert.Ejiestein"<1510342484@qq.com>; "Comment"<comment@noreply.github.com>;
主题: Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
Is there any way to solve this problem?
------------------&nbsp;原始邮件&nbsp;------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com&gt;;
发送时间:&nbsp;2020年10月9日(星期五) 下午5:19
收件人:&nbsp;"AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com&gt;;
抄送:&nbsp;"啥也不会的小菜鸟"<984281379@qq.com&gt;;"Author"<author@noreply.github.com&gt;;
主题:&nbsp;Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
In my opinion, it cannot be cancelled. Every time I operate the earth, I need to update the current viewport parameters, including the camera angle of view, the latitude and longitude range of the visible area, etc. At the same time, because it is based on webgl, I need to clear the frame buffer and the particle texture of the last time for each operation and recreate it. If you cancel these operations, the visualization will be messy, and the last wind field traceand the current tracewill overlap.
------------------&amp;nbsp;原始邮件&amp;nbsp;------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com&amp;gt;;
发送时间:&amp;nbsp;2020年10月9日(星期五) 下午5:02
收件人:&amp;nbsp;"AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com&amp;gt;;
抄送:&amp;nbsp;"Albert.Ejiestein"<1510342484@qq.com&amp;gt;;"Comment"<comment@noreply.github.com&amp;gt;;
主题:&amp;nbsp;Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)
Thank you very much for your generous answer.
Another question,when the earth is operated , the wind field will be redrawn. How to cancel this?

------------------&amp;amp;amp;nbsp;原始邮件&amp;amp;amp;nbsp;------------------
发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com&amp;amp;amp;gt;;
发送时间:&amp;amp;amp;nbsp;2020年10月9日(星期五) 中午11:08
收件人:&amp;amp;amp;nbsp;"AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com&amp;amp;amp;gt;;
抄送:&amp;amp;amp;nbsp;"啥也不会的小菜鸟"<984281379@qq.com&amp;amp;amp;gt;;"Author"<author@noreply.github.com&amp;amp;amp;gt;;
主题:&amp;amp;amp;nbsp;Re: [AlbertEjiestein/Wind-Field-Cesium] about particles (#5)

 The color represents the speed.

 ------------------&amp;amp;amp;amp;nbsp;原始邮件&amp;amp;amp;amp;nbsp;------------------
 发件人:                                                                                "AlbertEjiestein/Wind-Field-Cesium"                                                                                <notifications@github.com&amp;amp;amp;amp;gt;;
 发送时间:&amp;amp;amp;amp;nbsp;2020年10月8日(星期四) 上午8:55
 收件人:&amp;amp;amp;amp;nbsp;"AlbertEjiestein/Wind-Field-Cesium"<Wind-Field-Cesium@noreply.github.com&amp;amp;amp;amp;gt;;
 抄送:&amp;amp;amp;amp;nbsp;"Subscribed"<subscribed@noreply.github.com&amp;amp;amp;amp;gt;;
 主题:&amp;amp;amp;amp;nbsp;[AlbertEjiestein/Wind-Field-Cesium] about particles (#5)

 Dear author，i have a question.
  What does the color of the particles represent
  speed? direction? or？
  could u explain it to me？

 —
 You are receiving this because you are subscribed to this thread.
 Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

authors: AlbertEjiestein Rookiemin

repo: AlbertEjiestein/Wind-Field-Cesium


text:
Demo is broken!

At the moment this link from the README 404s:
https://albertlucianto.github.io/vue-text-highlight

Hi @samtstern, thanks for reporting! It's fixed now.

authors: AlbertLucianto samtstern

repo: AlbertLucianto/vue-text-highlight


text:
实现硬编码版本的地图显示食堂位置

效果
图片

为什么不用 Xml 布局？
高德给的接口不够，得用程序式生成布局。
为什么返回按钮在上面？
试了很多方法也没办法搞到下面。高德的地图组件不是很配合
为什么硬编码？
因为食堂标签本身是硬编码的，所以这个地图显示也只能用硬编码了。得等到食堂标签页面修改完之后，采取软编码，本功能才能跟着修改。

可以，很酷

source: gharchive/pull-request

repo: AlearXS/SmartCanteenApp


text:
ChatGLM

"Can the author add a call to ChatGLM? It is not only free to use now, but the translation effect is also very good."

Hi. I can take a look when I have time. Weren't there already nodes on ChatGLM? https://github.com/smthemex/ComfyUI_ChatGLM_API

"Thank you very much! However, if it's integrated into your plugin, it would be even more powerful and convenient, as I'd immediately think of using your plugin when I need translation."

Hi. You still need a key, even though chatglm4-flash is free (https://bigmodel.cn/). You will need to get a ZHIPUAI API key to use the model.

"Thank you very much! However, if it's integrated into your plugin, it would be even more powerful and convenient, as I'd immediately think of using your plugin when I need translation."

https://github.com/AlekPet/ComfyUI_Custom_Nodes_AlekPet/tree/master/ChatGLMNode#chatglm-nodes-for-comfyui


text:
Limit for One functions?

tail needed for WHERE or LIMIT part of query. But function, whitch return just one struct need auto add limit 1 automatically.

FindOneFrom and FindOneTo already use LIMIT 1. It is not possible to add it to tail automatically for SelectOneFrom and SelectOneTo. For example, consider tails LIMIT 1 OFFSET 10 and WHERE name = 'LIMIT 1'. To figure out that LIMIT 1 can be added to the second query, but not to the first, reform have to parse it, and I don't plan to add parser.

authors: AlekSi EagleMoor

repo: AlekSi/reform

license: mit

license_source: bigquery


text:
New Features

Hello, here some suggestions of features which can make our favorite browser Thorium Browser even more faster and more efficient, maybe it will be a good idea to add options in the settings to activate/deactivate them quickly with one click, I ask this because I tried to activate some of these flags but it doesn't work :(
secret flag apparently not documented reserved to chrome os:
--enable-native-gpu-memory-buffers
disable complete prefetch to save data date battery:
Back forward cache
Closed Tab Cache
Persistent client hints
option to enable low mode for weak notebook
--enable-low-end-device-mode
increase buffer or media source extension (MSE):
--mse-video-buffer-size-limit-mb=300 --mse-audio-buffer-size-limit-mb=300
increase cache size beyond limit 1.8Gb
--disk-cache-size=5147483647
increase media cache beyond limit 1.8Gb
--media-cache-size=3147483647
disable completely disk cache and memory cache because the flag
--disk-cache-size=0
do not work !
Thanks a lot !

@trimechee --enable-native-gpu-memory-buffers is available for all OSes. I will make a chrome://flag to turn this on/off in the UI
Back forward cache is enabled by default as of M108.
Closed tab cache is probably not something you want.
Low end device mode should only be used on chromeos with less than 4GB RAM
Disk cache should not be messed with.
The media cache flags, I do not have experience with. You can experiment with them and see what works for you.

I have made many many experiments with media cache , nothing change, but with palemoon browser, i can full buffer full video in sibnet streaming platform ans uqload platform and many others streaming platform,  but in chromium browsers, only little amount of video is buffered, in this site voiranime, the first player "mytv", there a litte mount of buffer video, but in the second player "moon", i can buffer many minutes of video, i think video platforms decide how much mount of video will be buffered  :
https://v3.voiranime.com/anime/dragon-ball-z-vf/dragon-ball-z-139-vf/
https://video.sibnet.ru/video5128213-Dead_Mount_Death_Play_01_VF/?utm_source=player&utm_medium=video&utm_campaign=EMBED


text:
add shop page

fixed contact  and added a shop page

done


text:
Add multi protocol versions support

We'd like to provide support for multiple binary protocols in order to cover older as well as newer Apache Cassandra versions.

[ ] version 3 is also used by ScyllaDB #138 (not implemented in CDRS)

[x] version 4 is actually implemented in CDRS

[ ] version 5

Version 3 - PR submitted #145

repo: AlexPikalov/cdrs


text:
Strange behaviour

I am getting strange behaviour with this integration and the related frontend card.
Everytime i try to open and view the dashboard with this integration i am forced to delete cache… only after 2 or 3 times i clear the cache the page shows itself, otherwise i have only a blank page.
Any other has the same behaviour?

Im closing this, as nobody had this too. It looks like it is something with A frontend. It is not related to this integration


text:
Interpreting signature probabilities for each mutation/variant in a VCF

Follow up on a previous issue since I'd like to be able to categorize each mutation in a VCF sample by its assigned signature.
I took at look at the output files there but still have the same questions as above. Could you confirm that SigProfiler algorithm simply calls the SBS with the highest probability or it's more complicated? I do notice that the results here tend to skew way more toward a dominant SBS compare to the previous path:
6.040989045139073e-05	0.0	0.0	0.7239713074945375	0.14000906911576955	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.013243712486085144	0.0	0.0	0.0	0.03891348241870776	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.08380201859444865	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0
but there are still variants where it can be quite close, e.g. between two signatures:
0.0001331437736342248	0.0	0.0	0.015046617411096077	0.4462584121397326	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.04714382614493876	0.0	0.0	0.0	0.114888454105007	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.3765295464255912	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0
or even three signatures:
0.0004209922073199189	0.0	0.0	0.09195513113684133	0.2659303843753061	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.08492596007440775	0.0	0.0	0.0	0.23650530304941902	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.32026222915670594	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0	0.0
Originally posted by @lntran26 in https://github.com/AlexandrovLab/SigProfilerAssignment/issues/148#issuecomment-2480338360

Dear @lntran26,
I hope you are doing well, and sorry for the delayed response. Regarding your question, SigProfilerAssignment does not assign an individual mutational signature to each individual somatic mutation. Instead, as you can see in the output matrix, SigProfilerAssignment provides a probability for each mutational signature to be causing each individual somatic mutation. We actually do not provide the one-to-one assignment per individual mutation as this is a probabilistic result.
Considering this, it's then a user's choice how to proceed further. For example, you can use a maximum likelihood approach, where you always take the signature with the highest probability, or make some filters, only allowing cases where a specific signature has a probability of causing an individual mutation above a certain threshold.
I strongly suggest you to check the methods of topography-associated studies (Otlu et al. 2023 Cell Reports and Morganella et al. 2016 Nature Communications), which have used these approaches in the past, and reach out by email in case you have further questions.
I hope this helps, and thanks so much for your interest in our tools!

repo: AlexandrovLab/SigProfilerAssignment


text:
cursor css not working

i tried setting the css for hovering on workspaces to have the cursor become a pointer, but it spits out this error [2023-09-21 18:49:22.932] [error] style.css:37:10'cursor' is not a valid property name, not sure if this is a missing feature or an issue. thanks for any help you can give

I do not think that this is a bug since cursor is not a supported property of gtk3

is there a way to change the it in gtk css?

Sorry until GTK support this, it'll not be possible.

authors: Alexays exoess mutoroglin

repo: Alexays/Waybar


text:
Segmentation fault after resume

Version: 0.10.3
Environment: x86_64, GNU/Linux (Arch), sway 1.9.
This happened when docking a suspended laptop and then resuming. Suspend was triggered by taking the laptop out of its dock while the lid was closed. Resume was triggered by opening the lid.
Program terminated with signal SIGSEGV, Segmentation fault.
[Current thread is 1 (Thread 0x7b7c8292fa00 (LWP 2154699))]
#0  std::__detail::_List_node_base::_M_hook (this=this@entry=0x5d945462ef30, __position=__position@entry=0x5d9454477d88) at /usr/src/debug/gcc/gcc/libstdc++-v3/src/c++98/list.cc:134
#1  0x00007b7c85933b91 in std::__cxx11::list<sigc::slot_base, std::allocator<sigc::slot_base> >::emplace<sigc::slot_base> (__position=Python Exception <class 'gdb.error'>: value has been optimized out
, this=0x5d9454477d88) at /usr/include/c++/13.2.1/bits/stl_list.h:268
        __tmp = 0x5d945462ef30
        __tmp = <optimized out>
#2  std::__cxx11::list<sigc::slot_base, std::allocator<sigc::slot_base> >::insert (__x=..., __position=Python Exception <class 'gdb.error'>: value has been optimized out
, this=0x5d9454477d88) at /usr/include/c++/13.2.1/bits/stl_list.h:1403
#3  sigc::internal::temp_slot_list::temp_slot_list (slots=std::__cxx11::list = {...}, this=<synthetic pointer>) at /usr/include/sigc++-2.0/sigc++/signal_base.h:223
#4  sigc::internal::signal_emit0<void, sigc::nil>::emit (impl=0x5d9454477d80) at /usr/include/sigc++-2.0/sigc++/signal.h:788
        exec = {sig_ = <optimized out>}
        slots = Python Exception <class 'gdb.error'>: value has been optimized out
{slots_ = <optimized out>, placeholder = }
        exec = {sig_ = <optimized out>}
        slots = Python Exception <class 'gdb.error'>: value has been optimized out
{slots_ = <optimized out>, placeholder = }
        slot = <optimized out>
        __for_range = <optimized out>
        __for_begin = Python Exception <class 'gdb.error'>: value has been optimized out

        __for_end = Python Exception <class 'gdb.error'>: value has been optimized out

#5  sigc::signal0<void, sigc::nil>::emit (this=<optimized out>) at /usr/include/sigc++-2.0/sigc++/signal.h:2805
#6  sigc::signal0<void, sigc::nil>::operator() (this=<optimized out>) at /usr/include/sigc++-2.0/sigc++/signal.h:2821
#7  Glib::DispatchNotifier::pipe_io_handler (this=<optimized out>) at ../glibmm/glib/glibmm/dispatcher.cc:486
        data = {dispatcher = 0x5d94543a7218, notifier = 0x5d9453ecfd80}
        n_read = <optimized out>
        drop_message = <optimized out>
        __PRETTY_FUNCTION__ = {<optimized out> <repeats 64 times>}
#8  0x00007b7c85933f60 in sigc::slot1<bool, Glib::IOCondition>::operator() (_A_a1=@0x7ffdc9566e64: Glib::IO_IN, this=<optimized out>) at /usr/include/sigc++-2.0/sigc++/functors/slot.h:675
#9  Glib::IOSource::dispatch (this=<optimized out>, slot=<optimized out>) at ../glibmm/glib/glibmm/main.cc:1377
#10 0x00007b7c85934daf in Glib::Source::dispatch_vfunc (callback=<optimized out>, user_data=<optimized out>) at ../glibmm/glib/glibmm/main.cc:131
        self = <optimized out>
        callback_data = <optimized out>
        __PRETTY_FUNCTION__ = {<optimized out> <repeats 75 times>}
#11 0x00007b7c85a13199 in g_main_dispatch (context=0x5d9453e66450) at ../glib/glib/gmain.c:3344
        dispatch = 0x7b7c85934d60 <Glib::Source::dispatch_vfunc(_GSource*, int (*)(void*), void*)>
        prev_source = 0x0
        begin_time_nsec = 279270673315849
        was_in_call = 0
        user_data = 0x5d9453ec2480
        callback = 0x7b7c859340a0 <(anonymous namespace)::glibmm_dummy_source_callback(void*)>
        cb_funcs = 0x7b7c85b04380 <g_source_callback_funcs>
        cb_data = 0x5d9453f8d1d0
        need_destroy = <optimized out>
        source = 0x5d9453ecfea0
        current = 0x5d9453e66690
        i = 0
        __func__ = "g_main_dispatch"
#12 0x00007b7c85a723bf in g_main_context_dispatch_unlocked (context=0x5d9453e66450) at ../glib/glib/gmain.c:4152
#13 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x5d9453e66450, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../glib/glib/gmain.c:4217
        max_priority = 2147483647
        timeout = -1
        some_ready = 1
        nfds = 4
        allocated_nfds = 5
        fds = 0x5d9453f264d0
        begin_time_nsec = 279270673291279
#14 0x00007b7c85a12712 in g_main_context_iteration (context=context@entry=0x5d9453e66450, may_block=may_block@entry=1) at ../glib/glib/gmain.c:4282
        retval = <optimized out>
#15 0x00007b7c857e6ed6 in g_application_run (application=0x5d9453e546d0, argc=<optimized out>, argv=0x7ffdc9567db8) at ../glib/gio/gapplication.c:2712
        arguments = 0x5d9453f74370
        status = 0
        context = 0x5d9453e66450
        acquired_context = <optimized out>
        __func__ = "g_application_run"
#16 0x00005d94536b98bc in ??? ()
#17 0x00005d94536b7ed6 in main ()

Can you build a debug version of Waybar and try to reproduce it again, because currently the gdb backtrace doesn't show much. Also include the trace logs by running with -l trace.

Does it also happen if you suspend/resume without the dock connected?

Can you share your Waybar config? I'll try to reproduce it locally.

I can't reproduce it by suspending/resuming with your groups/group-upower config. Can you try reproducing it with a very minimal config?

I still can't reproduce it with your minimal config. I'm on Hyprland, though, I'm not sure if that makes a difference.
@LukashonakV merged a UPower rework into master yesterday, can you try again with the latest master?

Hi @hrdl-github , let me check
I'm not familiar with the dock station. When you connect laptop to it is dock station became as a main battery in the system ?
Please provide battery list from the system when dock station is connected
Thanks

I've been using the reworked upower module since #3223 (comment). Is there any chance that this is due to leftover callbacks to UPower::deviceNotify_cb after UPower::~UPower gets called when an output gets destroyed?

Impossible. Once destructor is called dispatcher instances with the UPower client, devices are destructed

@hrdl-github  is it possible if I create the patch for you to check, whether it solves an issue ? I'll provide it there in the conversation.
Looks I found it. But I cannot reproduce this issue so need a help to check

Hi @hrdl-github ,
Please apply provided patch into yours master branch, run make and then please test waybar. Due to github limitation I added txt file extension . Remove txt and apply upower.patch
upower.patch.txt

Hi @hrdl-github , please check master release. This patch is merged, If its Ok, please close this issue. Thanks

authors: LukashonakV hrdl-github zjeffer


text:
[sway/window] Add app_id to usable fields in title

I know it's a pretty naive implementation but I hope:

It will work
It will be retro-compatible with existing configuration file

I have to confess I'm not a C++ developer (far from it).
Closes #1000

Thanks!

authors: Alexays max-k


text:
Compiling on Linux

In order to compile the library on linux, you need to

Fix a file sources/mfoGlobals.h. Replace d_mfoglobaldefineextern enum StencilScheme just to a enum StencilScheme, because C++ standard does not allow enum to be extern. This gives an error.
Replace common to Common in Makefile

Also, there is a warning about overflow:
../sources/MagFieldOps.cpp: In function ‘void _proceedGlobals(bool)’:
../sources/MagFieldOps.cpp:137:63: warning: overflow in conversion from ‘long int’ to ‘int’ changes value from ‘10000000000’ to ‘1410065408’ [-Woverflow]
  137 |     mapIntproceed   (bGet, "step_max", WiegelmannProcStepMax, 10000000000); // max. aval. step
      |                                                               ^~~~~~~~~~~

Thanks, will be done.

Changes are committed, please check.

It compiles now.
You can fix some warnings as well:
../Common/BasePhysics/agpWiegelmannPar.cpp: In member function «double CagpWiegelmann::step(int, int)»:
../Common/BasePhysics/agpWiegelmannPar.cpp:202:11: предупреждение: ISO C++ запрещает преобразование строковой константы в «char*» [-Wwrite-strings]
  202 |     o.out("vB", vB);
      |           ^~~~
../Common/BasePhysics/agpWiegelmannPar.cpp:207:11: предупреждение: ISO C++ запрещает преобразование строковой константы в «char*» [-Wwrite-strings]
  207 |     o.out("B2", B2);
      |           ^~~~
../Common/BasePhysics/agpWiegelmannPar.cpp:208:11: предупреждение: ISO C++ запрещает преобразование строковой константы в «char*» [-Wwrite-strings]
  208 |     o.out("invB", s);
      |           ^~~~~~
../Common/BasePhysics/agpWiegelmannPar.cpp:209:11: предупреждение: ISO C++ запрещает преобразование строковой константы в «char*» [-Wwrite-strings]
  209 |     o.out("rotB", rotB);
      |           ^~~~~~
../Common/BasePhysics/agpWiegelmannPar.cpp:210:11: предупреждение: ISO C++ запрещает преобразование строковой константы в «char*» [-Wwrite-strings]
  210 |     o.out("Wa", Wa);
      |           ^~~~
../Common/BasePhysics/agpWiegelmannPar.cpp:211:11: предупреждение: ISO C++ запрещает преобразование строковой константы в «char*» [-Wwrite-strings]
  211 |     o.out("divB", divB);
      |           ^~~~~~
../Common/BasePhysics/agpWiegelmannPar.cpp:212:11: предупреждение: ISO C++ запрещает преобразование строковой константы в «char*» [-Wwrite-strings]
  212 |     o.out("Wb", Wb);
      |           ^~~~
../Common/BasePhysics/agpWiegelmannPar.cpp:213:11: предупреждение: ISO C++ запрещает преобразование строковой константы в «char*» [-Wwrite-strings]
  213 |     o.out("WaxB", WaxB);
      |           ^~~~~~
../Common/BasePhysics/agpWiegelmannPar.cpp:214:11: предупреждение: ISO C++ запрещает преобразование строковой константы в «char*» [-Wwrite-strings]
  214 |     o.out("WbxB", WbxB);
      |           ^~~~~~
../Common/BasePhysics/agpWiegelmannPar.cpp:223:11: предупреждение: ISO C++ запрещает преобразование строковой константы в «char*» [-Wwrite-strings]
  223 |     o.out("vF", (CagmVectorField *)vF);

and
../sources/WiegelmannProcedure.cpp:254:8: предупреждение: лишние токены в конце директивы #endif [-Wendif-labels]
  254 | #endif _WINDOWS
      |        ^~~~~~~~

These are non-critical, but you can fix them as well to avoid confusion with errors

In new update there's compilation error
../sources/WiegelmannProcedure.cpp: In function «uint32_t mfoWiegelmannProcedureCore(CagmVectorField*, CagmScalarField*, CagmVectorField*, CagmVectorField*, CagmVectorField*, CagmVectorField*, CagmScalarField*, CagmScalarField*, CagmScalarField*, CagmScalarField*, CagmScalarField*, CagmScalarField*, CagmScalarField*, CagmScalarField*, CagmScalarField*, double*, int, PROTO_mfoWiegelmannCallback, double*)»:
../sources/WiegelmannProcedure.cpp:144:11: ошибка: «class CagpWiegelmann» не содержит элемента с именем «step_failed»
  144 |     proc->step_failed[0] = 0;
      |           ^~~~~~~~~~~
../sources/WiegelmannProcedure.cpp:170:20: ошибка: «class CagpWiegelmann» не содержит элемента с именем «step_failed»
  170 |             (proc->step_failed[0])++;
      |                    ^~~~~~~~~~~
../sources/WiegelmannProcedure.cpp:196:19: ошибка: «class CagpWiegelmann» не содержит элемента с именем «step_failed»
  196 |             proc->step_failed[0] = 0;
      |                   ^~~~~~~~~~~
make: *** [<встроенное>: ../sources/WiegelmannProcedure.o] Ошибка 1

It seems submodule 'Common' was not automatically updated, please look.

Finally compilation works. Now we need to try setting up .so compilation within pip install.

repo: Alexey-Stupishin/AMaFiL


text:
Segematation fault (core dumped) and Cannot load image ""

![screenshot from 2018-05-17 23-53-25](https://user-images.githubusercontent.com/33179551/40188973-c57b677c-5a2d-11e8-86ba-e430f98ba30d.png
Can anyone help here? Pretty sure have done the training part OK (only 1 class). I am only using 6 images to begin with and when running I get the error shown in the screenshot attached.
Thanks

Can you show your obj.data and train.txt files?
Check that relative (or absolute) path is correct in the train.txt.

authors: AlexeyAB Moorditj

license: Unlicense


text:
HA 2024, не получает из УДЯ данные от яндекс розетки, voltage,  power, amperage

После обновления на HA 2024 больше не получаю данных по напряжению и току с яндекс розетки.
Использовал такой конфиг для получения данных:
    sensors:
      rozetka_voltage:
        friendly_name: "Напряжение"
        unit_of_measurement: V
        value_template: "{{ state_attr('switch.rozetka','voltage')}}"
      rozetka_power:
        friendly_name: "Мощность"
        unit_of_measurement: W
        value_template: "{{ state_attr('switch.rozetka','power')}}"
      rozetka_amperage:
        friendly_name: "Ток"
        unit_of_measurement: A
        value_template: "{{ state_attr('switch.rozetka','amperage')}}"

Формат поддержки изменился. Теперь нужно вручную в конфиге указать, какие сенсоры вам нужны.
Если скачаете диагностику устройства розетки из ХА - смогу добавить проброс всех сенсоров подобных устройств без дополнительной настройки.

Огромное спасибо за Ваш труд! Моё знакомство с HA произошло благодаря этой интеграции. Купил игрушку (колонку) яндекса ребёнку в подарок, и мне вдруг на просторах нета попалась эта интеграция на глаза.. В результате установил HA, купил ещё Я (и не только) устройств и колонок
А данные то передаются...
Вот кусок диаг. от розетки:
"properties": [
{
"type": "devices.properties.float",
"retrievable": true,
"reportable": true,
"parameters": {
"instance": "voltage",
"name": "\u0442\u0435\u043a\u0443\u0449\u0435\u0435 \u043d\u0430\u043f\u0440\u044f\u0436\u0435\u043d\u0438\u0435",
"unit": "unit.volt"
},
"state": {
"percent": null,
"status": null,
"value": 227
},
"state_changed_at": "2024-01-14T12:08:46Z",
"last_updated": "2024-01-14T12:09:44Z"
},
{
"type": "devices.properties.float",
"retrievable": true,
"reportable": true,
"parameters": {
"instance": "power",
"name": "\u043f\u043e\u0442\u0440\u0435\u0431\u043b\u044f\u0435\u043c\u0430\u044f \u043c\u043e\u0449\u043d\u043e\u0441\u0442\u044c",
"unit": "unit.watt"
},
"state": {
"percent": null,
"status": null,
"value": 0
},
"state_changed_at": "2024-01-11T05:00:58Z",
"last_updated": "2024-01-14T12:09:44Z"
},
{
"type": "devices.properties.float",
"retrievable": true,
"reportable": true,
"parameters": {
"instance": "amperage",
"name": "\u043f\u043e\u0442\u0440\u0435\u0431\u043b\u0435\u043d\u0438\u0435 \u0442\u043e\u043a\u0430",
"unit": "unit.ampere"
},
"state": {
"percent": null,
"status": null,
"value": 0
},
"state_changed_at": "2024-01-11T05:00:58Z",
"last_updated": "2024-01-14T12:09:44Z"
}
],
"item_type": "device",
"skill_id": "T",
"room_name": "\u0414\u0435\u0442\u0441\u043a\u0430\u044f",
"state": "online",
"render_info": {
"icon": {
"id": "yandex.socket"
}
},
"created": "2022-11-16T18:08:19Z",
"parameters": {
"device_info": {
"manufacturer": "Yandex",
"model": "YNDX-0007",
"hw_version": "1.0",
"sw_version": "1.0.4"
}

Куска мало. Нужно с начала, где есть тип и capabilities. Идентификаторы можно пропустить

"data": {
"device": {
"id": "........-....-....-....-............",
"name": "\u0411\u0435\u043b\u0430\u044f \u0440\u043e\u0437\u0435\u0442\u043a\u0430",
"type": "devices.types.socket",
"icon_url": "https://avatars.mds.yandex.net/get-iot/icons-devices-devices.types.socket.svg/orig",
"capabilities": [
{
"reportable": true,
"retrievable": true,
"type": "devices.capabilities.on_off",
"state": {
"instance": "on",
"value": true
},
"parameters": {
"split": false
}
}
],
"properties": [
{
"type": "devices.properties.float",
"retrievable": true,
"reportable": true,
"parameters": {
"instance": "voltage",
"name": "\u0442\u0435\u043a\u0443\u0449\u0435\u0435 \u043d\u0430\u043f\u0440\u044f\u0436\u0435\u043d\u0438\u0435",
"unit": "unit.volt"
},
"state": {
"percent": null,
"status": null,
"value": 227
},
"state_changed_at": "2024-01-14T12:08:46Z",
"last_updated": "2024-01-14T12:09:44Z"
},
{
"type": "devices.properties.float",
"retrievable": true,
"reportable": true,
"parameters": {
"instance": "power",
"name": "\u043f\u043e\u0442\u0440\u0435\u0431\u043b\u044f\u0435\u043c\u0430\u044f \u043c\u043e\u0449\u043d\u043e\u0441\u0442\u044c",
"unit": "unit.watt"
},
"state": {
"percent": null,
"status": null,
"value": 0
},
"state_changed_at": "2024-01-11T05:00:58Z",
"last_updated": "2024-01-14T12:09:44Z"
},
{
"type": "devices.properties.float",
"retrievable": true,
"reportable": true,
"parameters": {
"instance": "amperage",
"name": "\u043f\u043e\u0442\u0440\u0435\u0431\u043b\u0435\u043d\u0438\u0435 \u0442\u043e\u043a\u0430",
"unit": "unit.ampere"
},
"state": {
"percent": null,
"status": null,
"value": 0
},
"state_changed_at": "2024-01-11T05:00:58Z",
"last_updated": "2024-01-14T12:09:44Z"
}
],
"item_type": "device",
"skill_id": "T",
"room_name": "\u0414\u0435\u0442\u0441\u043a\u0430\u044f",
"state": "online",
"render_info": {
"icon": {
"id": "yandex.socket"
}
},
"created": "2022-11-16T18:08:19Z",
"parameters": {
"device_info": {
"manufacturer": "Yandex",
"model": "YNDX-0007",
"hw_version": "1.0",
"sw_version": "1.0.4"
}
}
}
}

В следующем релизе для этих розеток все сенсоры будут добавляться автоматически

https://github.com/AlexxIT/YandexStation/releases/tag/v3.13.1

А можно ещё одну просьбу по улучшению?  (^_^)
Если тип розетки в УДЯ выбран "освещение", то в HA данные по току напряжению не передаются. В УДЯ эти параметры у лампочки присутствуют

Вы можете добавить любые сенсоры любых устройств. Почитайте документацию последней версии.
Просто именно для розетки все её сенсоры пробрасываются автоматически.

Да, Спасибо! В документации всё написано.
Для таких же не опытных как я:
В документации "Управление умным домом.."
В конфиге
yandex_station:
include:

Белая розетка
name: Полки
properties: [ "amperage", "power", "voltage" ]

authors: AlexxIT MikhailTeddy

repo: AlexxIT/YandexStation


text:
Optionally generated functions

I think one of the nicest things about this package is that it naturally gives access to the comptime and runtime versions without the user needing to repeat themselves. Therefore, I think it makes a lot of sense for this to create optionally generated functions by default rather than plain generated functions.
This PR makes the @ct_enable macro create optionally generated functions by default which fall back on the runtime definition at the compiler's discretion.
IMO this is a better default than non-optionally generated functions because it can save a lot of useless compile times in dynamic circumstances, and we can let users opt out by writing things like
@ct_enable optional=false function ...

This is just a suggestion as to how I'd approach it, but feel free to request that the default be non-optional and force users to opt into the optionally generated functions.

Bump @olynch

Oh shoot! I totally didn't see this @MasonProtter. I will look at it now.

OK, I understand what this is doing now. I have to integrate it a little with some unpushed work, but hopefully I can merge this today. Sorry, I almost never check my github notifications, and I wasn't expecting anyone to send me a PR. In the future, definitely bug me on zulip if I'm not merging something.

@MasonProtter I'm so sorry this took so long; thank you for the PR! I should be more responsive now; I was finishing my thesis May-July, and I've now started working fulltime on Julia stuff.

No problem! I know how these things go.

authors: MasonProtter olynch


text:
Principal Component Analysis - Base

Task: Set up the basic Principal Component Analysis code functionality that works
Level-3 : 25 Points

I want to contribute to this issue as GSSoC'21 participant.

@Rutikab12  You have been assigned the task to setup the base for Principal Component Analysis .
Try to submit a PR in 5 days.

Okay.

@Rutikab12 Yeah,It's expected to write a small example to show that your code works and it does what it's supposed to do.

Hey @ashwani-rathee can I work on this one as well ?

@Bayesian4042 I have two days left for PR. I i am unable to complete it, then you can go for it.

@ashwani-rathee my code is ok , is it? . I only have to pull it in .py extension, right?. I have closed my PR , which was pulled yesterday.

I'll try to get it merged today,if it's working fine.I have got to check the algorithm though,on it.

@Rutikab12 #74 is not yet ready
What is your progress on this?Any issues?How can I help?
2days to a PR
#64 #11 #44 are good examples of proper implementation by your fellow participants

Yeah my new PR will be ready by today. One more thing, I was suppose to write the PCA module python code instead of importing it from sklearn , right?. @ashwani-rathee

I would like to work on this issue. I am a gssoc participant. Please assign it to me.

@ashwani-rathee  I would like to work on this project can you assign this to me

Needs to be reassigned

@Sibasish-Padhy want to take it up?

hey can I work on this issue . I am a GSSOC21' participant . @ashwani-rathee

@ashwani-rathee
Hi, if this issue is still unassigned can I take it up?
Thank you.

@ashwani-rathee
I am a participant GSSOC'21
I would like to contribute to this

@ELITA04 Would you like to take this up and continue on the work?

@ashwani-rathee, Yes I'd like to.

@ELITA04 Go ahead

repo: Algo-Phantoms/Algo-ScriptML


text:
converted integer to a binary string

Fixes #301

@vabhv1903
Add some context about the algorithm above the code as comments.
Also, add the complexities too.

repo: Algo-Phantoms/Algo-Tree


text:
no way to use Tab & TabLink with NavLink from 'react-router'

<Tab>
  <TabLink>Name</TabLink>
</Tab>

will generate:

  Name

But, NavLink from react-router can only add className to itself, if it's active.
<NavLink to="/path" activeClassName="is-active" >Title</NavLink>

if we're in /path url, it will generate:
Title

So, even if we compose NavLink & TabLink, there's still no way to use bulma's style with it. Because, we can't add className to Tab when NavLink is active.

@MunifTanjim , you're right, there is no way to use NavLink, but remember that you have Link and you can use it like this example. This example is based on React Router custom link example.
Since Bulma use this kind of classes for tabs, we're unable to change the behavior. I've been really busy but I want to change this kind of stuff (since Bulma is not intended for React while Bloomer is
) and make Bloomer React friendly with other famous libraries, styled-components is going to help us to achieve this.
Ps: I'm going to close this issue, but you're welcome to open it if this doesn't help you.

Thanks for the response. :smiley: Actually I solved it earlier (and forgot about this issue). I'll leave my solution here:
import React from 'react'
import { Route, NavLink } from 'react-router-dom'
import { Tab, TabLink } from 'bloomer'

const NavBarTab = ({ to, exact, ...rest }) => (
  <Route
    path={to}
    exact={exact}
    children={({ match }) => (
      <Tab isActive={match}>
        <TabLink render={() => <NavLink to={to} exact={exact} {...rest} />} />
      </Tab>
    )}
  />
)

export default NavBarTab

@MunifTanjim lol, actually my first tough was to reply you about the render method that most of anchors have in bloomer. These were tough for this situation when I was facing so many troubles (well, more code) writing the documentation.
Thanks for your solution posted here. I'll leave a code in my comment so we can have both solutions.

I know it is poor form to comment on a closed ticket, but this is almost exactly like what I'm seeing. Let me know if you want a new ticket.

For styling purposes, I'd like to use <NavbarItem href={'/todos'}>Todos
But react-router generates a full page reload for that, because Bloomer generates an
I could instead do <NavbarItem onClick={() => history.push('/todos')}> but that messes up the styling
 has the correct routing behavior, but wrong styling

If this is confusing, I can do a gist.

@pauleveritt a gist would be really helpful :)

Here you go: https://gist.github.com/pauleveritt/c5bc6d6f317daede74b97216294bb87f
I suspect the gist will be insufficient as well, as this is an interaction with react-router 4.

@pauleveritt yeah, it would be better if you create a small repo... or a http://codesandbox.io example with the minimal stuff you want to do. If that's possible, that would be really helpful.
I believe that you would need the render prop on NavBarItem but let's see your example.

I'll investigate your suggestion first. I'd prefer not to clutter up this ticket with a side issue. Thanks for the fast responses.

authors: AlgusDark MunifTanjim pauleveritt

repo: AlgusDark/bloomer


text:
Omniparser inference

Hi,
Do you provide pretrained models for inference in Omniparser? I couldn't find the inference and pretrained models.

same issue, I can't find

the swin_base_patch4_window7_224_22k.pth from Swin-Transformer
really annoying.

same issue, anyone who solved this issue?

authors: aneeqahsan01 jiaoqianji youseon-jang


text:
The train data of BIRD-SQL is uncompressed failed.

I try to uncompress the zip package of train data in BIRD-SQL，but got the follow error message:
unzip train.zip
Archive:  train.zip
creating: train/
inflating: __MACOSX/.train
inflating: train/.DS_Store
inflating: __MACOSX/train/..DS_Store
inflating: train/train_databases.zip
error:  invalid compressed data to inflate
bad CRC b09490af  (should be 2eea441e)
inflating: __MACOSX/train/._train_databases.zip
inflating: train/train.json
inflating: __MACOSX/train/._train.json
inflating: train/train_gold.sql
inflating: __MACOSX/train/._train_gold.sql

This looks like the zip file was damaged due to incomplete download, can it be reproduced by re-downloading it again?

Hi
I have downloaded the train.zip file three times from the given link, but I always get the error "error: invalid zip file with overlapped components (possible zip bomb)" while unzipping it. If I continue unzipping by setting UNZIP_DISABLE_ZIPBOMB_DETECTION=TRUE, about 30 databases turn up empty.
Is it possible to provide the dataset elsewhere? Thanks

authors: MaveriQ eric-doug huybery

repo: AlibabaResearch/DAMO-ConvAI


text:
update the news page in JPN and ENG

NEWS page

JPN
ENG

Thank you, I will cherry-picked it to https://github.com/AlisProject/welcome/pull/182

repo: AlisProject/welcome


text:
Added Feedback Section

Have done changes in the main html file along with an inline script and also added some css into the global.css file

@Alitindrawan24 please look into the PR #160 and kindly merge it if no prob


text:
Fix issue #5070: [Bug]: lint-fix workflow is failing

This pull request fixes #5070.
The issue has been successfully resolved because:

The root cause was clearly identified - the workflow was failing due to using mutually exclusive flags --all-files and --files in the pre-commit command
The fix was straightforward - removing the --all-files flag while keeping the --files flag with the specified file patterns
The solution is appropriate since:

Having --files with specified patterns (openhands//* evaluation//* tests/**/*) already covers the necessary files to check
The flags were mutually exclusive according to the pre-commit help output shown in the error message
No additional workflow or code changes were needed beyond this configuration fix

Since this was purely a CI workflow configuration issue, no application code changes or tests were required

The PR can be summarized for reviewers as:
"Fixed the lint-fix workflow by removing the redundant and conflicting --all-files flag from the pre-commit command, while maintaining the file pattern specifications with --files. This resolves the argument conflict that was causing the workflow to fail."
Automatic fix generated by OpenHands 🙌

To run this PR locally, use the following command:
docker run -it --rm   -p 3000:3000   -v /var/run/docker.sock:/var/run/docker.sock   --add-host host.docker.internal:host-gateway   -e SANDBOX_RUNTIME_CONTAINER_IMAGE=docker.all-hands.dev/all-hands-ai/runtime:6dc76df-nikolaik   --name openhands-app-6dc76df   docker.all-hands.dev/all-hands-ai/openhands:6dc76df

Looks ok!

authors: enyst openhands-agent

repo: All-Hands-AI/OpenHands


text:
fix: ts 7016

import piniaPersist from 'pinia-plugin-persist-uni';
Could not find a declaration file for module 'pinia-plugin-persist-uni'. 'node_modules/pinia-plugin-persist-uni/dist/pinia-persist-uni.es.js' implicitly has an 'any' type.
  There are types at 'node_modules/pinia-plugin-persist-uni/dist/index.d.ts', but this result could not be resolved when respecting package.json "exports". The 'pinia-plugin-persist-uni' library may need to update its package.json or typings.
ts(7016)

感谢分享，不知道我的理解是否有误，package.json中exports的作用是设置引用包里面不同类型资源时的默认指向，而此插件的依赖应该不需要引用，只需要被ts解析才对，是否有尝试按照README中配置 tsconfig.json呢

有添加，但是没效果，我之前用另一个插件 https://github.com/prazdevs/pinia-plugin-persistedstate 不需要改 tsconfig。
https://stackoverflow.com/a/76212193/10188914
https://stackoverflow.com/a/77685338/10188914

了解了，看起来和项目中使用的ts的版本有关，将会合并发布

已发布 v1.3.1


text:
Compensate for zooming in/out

When you zoom in or out mouse movements do not scale respectively.

It should be fixed now.

authors: AllenDang adsick


text:
Warnings for manually calling a React.PropTypes validation functions

Hi,
First I have to say that react-bootstrap-table is fantastic. It is a pleasure to work with. I'm getting a few warning messages when I add New, Delete and Search.
I'm running
react-bootstrap-table@2.5.5
and
├── react@0.14.8
└─┬ react-bootstrap-table@2.5.5
  └─┬ react-toastr@2.8.1
    └── react@15.3.2

I get the following warning message:
Warning: You are manually calling a React.PropTypes validation function for the **toastTypeprop onToastContainer**. This is deprecated and will not work in the next major version. You may be seeing this warning due to a third-party PropTypes library. See https://fb.me/react-warning-dont-call-proptypes for details.
I get the same warning message for the props below.
**`id` prop on `ToastContainer`
`toastMessageFactory` prop on `ToastContainer`
`preventDuplicates` prop on `ToastContainer`
`newestOnTop` prop on `ToastContainer`
`onClick` prop on `ToastContainer`**

Not sure if it is a version issue or something else.

I think this is the same issue as [(https://github.com/tomchentw/react-toastr/issues/75)] which it looks like it hasn't been fixed yet.

@g3blv, good finding, hope there's someone can fix it in react-toastr. I'll close this issue. BTW, maybe you can open a PR to ```react-toastr``. Thanks you :)

@AllenFang I've checked with the author of react-toastr issue #75. He no longer sees the issue while I do. Could the issue be somewhere else in react-boostrap-table?

@g3blv, I've no idea about this issue, because the warning message is all about the react-toastr.  But i'll spend some time to check this out.

+1

authors: AllenFang g3blv stavlevy

repo: AllenFang/react-bootstrap-table


text:
Add method to search for data assets

Acceptance criteria:

[ ] get_data_assets
[ ] a method called search_data_assets
[ ] exposes all parameters of the data asset API
[ ] if start and limit are passed, return the requested number of assets
[ ] if start and limit are not passed, return all matching assets (make multiple requests)

[ ] Create a separate method called search_data_assets

[ ]  Create a separate method called search_data_assets

Updated the acceptance criteria, thanks.

Acceptance criteria:

[ ]  ~get_data_assets~
[ ]  a method called search_data_assets
[ ]  exposes all parameters of the data asset API
[ ]  if start and limit are passed, return the requested number of assets
[ ]  if start and limit are not passed, return all matching assets (make multiple requests)

^ @dyf I think we should use the default behavior provided by codeocean if start and limit are not passed

Acceptance criteria:

[ ]   ~get_data_assets~
[ ]   a method called search_data_assets
[ ]   exposes all parameters of the data asset API
[ ]   if start and limit are passed, return the requested number of assets
[ ]   if start and limit are not passed, return all matching assets (make multiple requests)

^ @dyf I think we should use the default behavior provided by codeocean if start and limit are not passed

We can make it a separate ticket if you want, but I this is functionality I would like.

Acceptance criteria:

[ ]    ~get_data_assets~
[ ]    a method called search_data_assets
[ ]    exposes all parameters of the data asset API
[ ]    if start and limit are passed, return the requested number of assets
[ ]    if start and limit are not passed, return all matching assets (make multiple requests)

^ @dyf I think we should use the default behavior provided by codeocean if start and limit are not passed

We can make it a separate ticket if you want, but this is functionality I would like.

I put this as a separate ticket.

authors: dana-rocha dyf jtyoung84

repo: AllenNeuralDynamics/aind-codeocean-api


text:
duplicate records for same prefix

Describe the bug
I found two records that represent the same prefix.
To Reproduce
Steps to reproduce the behavior:
filter = {"name": { "$regex": "^single-plane.*" }, "subject.subject_id": "631479" }
records = list(
    doc_db_client.collection.find(filter=filter)#, projection=projection)
)

for r in records:
    print(r["_id"], r["name"], r["location"])

prints
5a5c2cff-272c-44da-b75a-e7f5b668f01e single-plane-ophys_631479_2023-03-21_12-00-00 s3://aind-ophys-data/single-plane-ophys_631479_2023-03-21_12-00-00
aab2b12d-5b9f-40da-ac53-9d455d6fe1fc single-plane-ophys_631479_2023-03-23_12-00-00 s3://aind-ophys-data/single-plane-ophys_631479_2023-03-23_12-00-00

oops


text:
Ephys rig camera assembly require filter which is optional

UPDATE:
The form is rendered directly from schemas, and is therefore requiring sub-fields, even though the main field is optional. Write a work around within the app that will convert required sub-fields to optional
Describe the bug
The filter is optional in the schema but the entry form requires it.
Additional context
Relaying info from Anna Lakunina

To fix this, I'll either have to write a workaround in the app that edits the schema, or do something in aind-data-schema

authors: mekhlakapoor saskiad


text:
Alluxio and K8s have different interpretation of size

Alluxio Version:
2.4
Describe the bug
In K8s context, g or GB means 1000^3 and gi or GiB means 1024^3.
https://stackoverflow.com/questions/50804915/kubernetes-size-definitions-whats-the-difference-of-gi-and-g
In Alluxio context, g or GB means 1024^3.
https://github.com/Alluxio/alluxio/blob/a5265484f6f0cfcb7745dec31e61030056b49240/core/base/src/main/java/alluxio/Constants.java#L23
So when we use g and pass the quota to Alluxio and K8s, K8s grants 1000^3 but Alluxio tries to utilize 1024^3. For example if it is an emptyDir, then the pod using the emptyDir will be killed for overusing resources.
To Reproduce
Steps to reproduce the behavior (as minimally and precisely as possible)
Expected behavior
Alluxio and K8s should have consistent understanding about sizes, especially they are parsing the same piece of configuration field.
Urgency
Describe the impact and urgency of the bug.
Additional context
Add any other context about the problem here.

There are a few options:

Workaround: Use bytes all across the helm chart configuration to avoid conversion. This can only be a workaround as users will face the issue when they use expressions like 4G.

Change Alluxio conversion to be G = 1000^3 and Gi = 1024^3. This breaks the backward compatibility but will guarantee consistent (and correct?) behavior.

Change Alluxio conversion to be G = Gi = 1024 ^ 3. This gives backward compatibility but might be a confusing fix.

@madanadit What do you think about this?

@jiacheliu3 I would suggest:

Alluxio helm chart uses the K8s convention (G = 1000^3) (for comformity)
We do not change the convention for Alluxio servers either (for backwards compatibility)
When we set a helm config to X G, we transform the value to bytes and set Alluxio config in B. Similar for other units as well.

@jiacheliu3 I would suggest:

Alluxio helm chart uses the K8s convention (G = 1000^3) (for comformity)
We do not change the convention for Alluxio servers either (for backwards compatibility)
When we set a helm config in G or Gi, we transform the value to bytes and set Alluxio config in B. Similar for other units as well.

This will only work for helm chart right? When the user tries to use kubectl and manually give G to both K8s and Alluxio, there will still be a confusing resource mismatch.

@madanadit @jiacheliu3 Since this issue seems to be popping up again and again, let's revive this discussion.
As Jiacheng mentioned there will be no way to ensure correct behaviour across all k8s tools (present and future) unless this is addressed properly. If we are not willing to break backwards compatibility in Alluxio (which is understandable), we can make it an opt-in rolling upgrade to enable the distinction in Alluxio between Gi and G and at some point in the future (e.g 3.0.0) we make it a fully committed change.
If this solution is undesirable then the only option we are left with is to concede that K8s and Alluxio have mismatching interpretations of G and document this extensively with corresponding workarounds.

1 GiB ~= 1.074 GB, or conversely 0.931 GiB <= 1 GB
Therefore we document that any Alluxio worker cache capacity backed by a k8s volume specified using GB require a high watermark <= 0.931

Discussed wth @madanadit, here's a compromise that should be minimally impactful:

Add the KiB/MiB/GiB/TiB suffix to Alluxio's parsing and map them to be identical to the existing KB/MB/GB/TB mappings.
Specify that all users of the Alluxio in a K8s environment (Helm or otherwise) should use the 2-bit based notation for any storage sizes, as this is the only interpretation Alluxio supports.

This requires zero end-user changes for normal Alluxio deployments, and a small change to our Helm chart & corresponding documentation. Otherwise, if end users attempt to use the base-10 notation in k8s with Alluxio it is at their own risk.

In the meantime, this error and its observed symptom(s) should be added to the troubleshooting section of the Alluxio K8s doc page
Ex:
tmpfs is smaller than the configured size: tmpfs size: 500002816, configured size: 524288000

This occurs because the K8s interprets the sizeLimit: 5G of the emptyDir volume as 51000^3 bytes whereas the binary tool tmpfs used in the alluxio-mount.sh interprets G as Gi => 51024^3 bytes.
There is currently no workaround for this.

authors: ZhuTopher jiacheliu3 madanadit

repo: Alluxio/alluxio


text:
Alluxio didn't cache data in remote worker when read them from UFS with Spark

Alluxio Version:
2.4.1
Describe the bug
Under these cases data can be cached in worker RAM automaticly(working as expected):

alluxio fs load
Short circuit read(aka read from local worker)

But when read from UFS with Spark, data can not be cached in remote worker RAM automaticly, not working as expected.
Some configurations might be related:
alluxio.user.file.readtype.default=CACHE
alluxio.user.file.passive.cache.enabled=true

To Reproduce

Deployed by helm on Kubernetes, set MEM to level 0 and no other customization.
No local worker, only remote workers.

Expected behavior
Data can be cached in worker RAM automaticly when read form remote worker.

@suninuni this is expected if you are running alluxio fs load /file as by default it will load data only to the current node running this command, with a single thread.
You may want to try   alluxio fs distributedLoad /file which will cache files distributedly.

@apc999 actually when use alluxio fs load or Filesystem API to read files, it will cache files distributedly in remote workers. But my problem is Alluxio can't cache files as expected when use Spark to query data through it.
Here is configs for Spark:
configs.put("spark.scheduler.mode", "FAIR");
configs.put("fs.alluxio.impl", "alluxio.hadoop.FileSystem");
configs.put("hive.metastore.uris", "thrift://bigdata-hive-metastore:9083");
configs.put("spark.sql.warehouse.dir", "alluxio://alluxio-master-0:19998;alluxio-master-1:19998;alluxio-master-2:19998/");
configs.put("spark.sql.catalogImplementation", "hive");


text:
Fix NPE in UfsDirectoryStatus

In some UFSes like S3, directories will have a null lastModifiedTimeMs indicating the timestamp is not available. We used long as constructor parameter type which will throw when null is passed in for a S3 directory.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/6760/
Test PASSed.

alluxio-bot, merge this please.

alluxio-bot, cherry-pick this to branch-2.1 please.


text:
Support getting real content hash from hdfs when using getFileStatus

What changes are proposed in this pull request?
Support getting real content hash from hdfs
Why are the changes needed?
for data integrity
Does this PR introduce any user facing changes?
na

Check here also please https://github.com/Alluxio/alluxio/blob/master/underfs/hdfs/src/main/java/alluxio/underfs/hdfs/HdfsUnderFileOutputStream.java#L93

Check here also please https://github.com/Alluxio/alluxio/blob/master/underfs/hdfs/src/main/java/alluxio/underfs/hdfs/HdfsUnderFileOutputStream.java#L93

for this PR, it's specific to getFileStatus from ufs.

alluxio-bot, merge this please.

alluxio-bot, merge this please.

alluxio-bot, merge this please.

alluxio-bot, cherry-pick this to dora, please

alluxio-bot, cherry-pick this to dora please

authors: beinan jja725 tcrain


text:
[ALLUXIO-628] Fixed Style checker failed to find an indent problem

https://alluxio.atlassian.net/browse/ALLUXIO-628
This one prepares the change in the configuration in Checkstyle.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9511/
Test FAILed.

authors: AmplabJenkins HorizonNet


text:
Volatility hint for Tokenscript engine optimisation

Compare:
<ts:ethereum function="balanceOf" contract="dai" as="uint">
vs
<ts:ethereum function="getStreet" contract="EntryToken" as="utf8">
The balanceOf is expected to be more volatile than the getStreet value. Adding a volatile attribute will help to give a hint for wallet run speed optimisation.
This would be a good start:
<ts:ethereum function="balanceOf" contract="dai" as="uint" volatile="true">
or
<ts:ethereum function="balanceOf" contract="dai" as="uint" volatility="high">
<ts:ethereum function="getStreet" contract="EntryToken" as="utf8" volatility="low">

Ok we have refined this down to two values to begin with:
<ts:ethereum function="balanceOf" contract="dai" as="uint" volatility="immediate">
and
<ts:ethereum function="getStreet" contract="EntryToken" as="utf8" volatility="default">
The second default volatility is handled by the client as appropriate. The immediate flag indicates that the value should be fetched before usage.

repo: AlphaWallet/TokenScript


text:
Update Binance and xDai RPC server nodes to recommended ones

Based on:

https://docs.binance.org/smart-chain/developer/rpc.html
https://www.xdaichain.com/for-developers/developer-resources

Tested on iOS :p

repo: AlphaWallet/alpha-wallet-android


text:
SystemTime arbitrary implementation is not arbitrary

The SystemTime impl for Arbitrary should be an arbitrary SystemTime with shrinking toward the epoch.  Right now it always returns the current time.

For example: https://github.com/BurntSushi/quickcheck/blob/4986e26c773503a9147256afb1c735bb3980e3ff/src/arbitrary.rs#L924-L944

repo: AltSysrq/proptest


text:
Move all Altinn 3 related tests in altinn-access-management-frontend repo in Github

[x] Move all Altinn 3 related which are API-delegering, IdPorten test in altinn-access-management-frontend repo
[ ] Configure github action so all tests will start running after every deploy

For running the E2E cypress tests from GitHub actions the runner needs to be able to connect to endpoints at{21-24}.altinn.cloud. for the time being, these endpoints are not opened on the internet, Hence, the Github action will fail. This issue is blocked until the endpoints are opened or we have custom self-hosted github runner.

Closing this task since we have got access running cypress e2e tests from github action and @andreasisnes has configured it to run from github action for which other tasks are created which can be followed.

authors: acn-Sneha andreasisnes


text:
Authorized Parties (formerly known as ReporteeList)

New API under Access-Management for getting all Authorized Parties (formerly known as reporteelist), where the authenticated user have any authorized access, either directly or through organizations where the user have a key-role.
Description

New AuthorizedParties controller and endpoint
Updated with use Altinn2 AuthorizedParties retrieval including roles pr. reportee party (optional URL-parameter: includeAltinn2)
New DelegationMetadataRepository Query for getting all direct and inherited App and Resource delegations in Altinn 3
New AuthorizedParties service implementation to get all relevant data and build the complete AuthorizedParties hierarchy list

Related Issue(s)

#563

Developer/Reviewer Checklist

[x] Your code builds clean without any errors or warnings
[x] No changes to config/appsettings or environment variables created in separate linked PR
[x] Manual testing done (required)
[x] Relevant integration test added (required for functional changes)
[ ] Relevant automated test added (required for functional changes)
[x] All integration tests run green

Documentation

[ ] User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

reading the changes are a bit difficult in the files where it was changed from namespace {} to namespace; Might be because that all lines in that file got indent one step back? Not quite sure.. However, should create a PR where we rewrite all the namespace ...{} to namespace ...; ?

there are some sonarqube complaints, I agree with the complexity of some of the functions, hard to read and grasp with actually going in the methods. Also, TheoryData can and should be used with Theory. You can see an example of the usage here https://github.com/Altinn/altinn-access-management/blob/5c4ba7f3ed2f7dd4a6ad25ff0fc082c4341a0838/test/Altinn.AccessManagement.Tests/Controllers/Altinn2DelegationControllerTest.cs#L75, it basically does the same as the old way, but with TheoryData you will get a build error if the TheoryData generic signature don't match with the arguments of the test.

authors: andreasisnes jonkjetiloye

repo: Altinn/altinn-access-management


text:
Multiple Select component

Description
Multiple select component described in Figma should be implemented. This component has partially been implemented in app-frontend repo in the PR https://github.com/Altinn/app-frontend-react/pull/505. Some code might be reused.

Additional Information
Once the component has been implemented, we should replace existing implementation in app-frontend. See issue https://github.com/Altinn/app-frontend-react/issues/510
Tasks

[ ] Implement
[ ] Design review

Acceptance Criterias

Multiple select is implemented
...

Waiting for Figma tokens in order to continue working on this.

Closing this as I have created new issues for the remaining tasks:

#201
#202

repo: Altinn/altinn-design-system


text:
Move Altinn.Common.EFormidlingClient

Description
We should take over Altinn.Common.EFormidlingClient and either

Merge it into Altinn.App.Core
Maintain it as a separate library in app-lib

Preferentially the first option, if it is doable without making breaking changes
Additional Information
No response
Tasks
No response
Acceptance Criterias
No response

Duplicate of https://github.com/Altinn/app-lib-dotnet/issues/131

repo: Altinn/app-lib-dotnet


text:
Using Dark or Mosaic theme, the message box to type in is white

On its own, this is jarring and an odd stylistic choice, but the most annoying part is how the text seems to have been recolored to white and so it's practically invisible: http://i.imgur.com/8RDiw1r.png
It's slightly better with the Mosaic theme, but still.
I'm on Windows 10 (anniversary update) using v1.4.3

Still true for me as well, many months after the problem first arose.
Regardless though, the issue was fixed in a fork by Sytten (thank you so much dude!)

Thankfully I found it was fixed in the new beta release. http://i.imgur.com/gONeehQ.png

Yea just use the latest beta :P

authors: Koolstr Sytten revalationist

repo: Aluxian/Facebook-Messenger-Desktop


text:
Live Quiz

Erase existing environment (screen capture)
Setup our working environment (git clone's)

1 erase enviorment

Clone Repo

activate tools setup

default:~$ bundle -v
Bundler version 2.5.18
default:~$ ruby -v
ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux-gnu]
default:~$ python --version
Python 3.10.12
default:~$ jupyter -v

scripts /venv.sh
404.html     images	LICENSE     _posts	      _sass
assets	     _includes	Makefile    README4YML.md     scripts
_config.yml  index.md	navigation  README.md	      venv
Gemfile      _layouts	_notebooks  requirements.txt
This command creates my virtual environment

'' markdown
Summary- we redownloaded  the gems and other installations like ruby and python. We cloned our repositories in github. Then we could change the directories with the command cd. We went into Visual Studio code and typed make. Then we got a server address which took us into  a browser and we saw the site we made on github there. We also made the directory Nighthawk with the command Mkdir. We typed in scripts/venv.sh which created our virtual environment. We checked if bundle and other installations were properly installed.
'' markdown

0.9
0.9
1.8/2


text:
Add contributors badges to website, from README.md

At present the contributors badge are being fetched from CONTRIBUTORS.md
README.md has action implemented that will automatically update the contributors badge
The badges in the the README shall reflect in website under contributors section as well

Hi @AmanSarraf
can i take this issue too?

hey @sleekyom , do we have any update

hi @AmanSarraf please review my PR again, I updated the styling :)

authors: AmanSarraf SWELLZ sleekyom

repo: AmanSarraf/Opensource-Buddy


text:
你好，可以发一下后续的作业吗

你好，可以发一下后续的作业吗

这里有全部的https://github.com/Huan0414/Motion-Planning


text:
Add a license to the repository

I recently came across your project quantumRepeatersAndStuff and I noticed that the repository github.com/Ampersand00/quantumRepeatersAndStuff currently does not have a license specified.
Why Adding a License is Important?
As GitHub documents

Public repositories on GitHub are often used to share open source software. For your repository to truly be open source, you'll need to license it so that others are free to use, change, and distribute the software.

Would be possible to add a valid license to this repository? Probably something really OpenSource such as the Apache 2.0 license would fit really well.
Thanks!

Of course! It was really a surprise that someone is interested in this project.

Thank you!


text:
Load error?

https://amsterdammusiclab.nl doesn’t load, but https://www.amsterdammusiclab.nl does.
N.B. Might have reported this earlier as well.

www.amsterdammusiclab.nl seems to have an A record that points to an IP owned by the UvA and a CNAME that points to  illc-aml.science.uva.nl.: DNS Checker <www.amsterdammusiclab.nl>
However, amsterdammusiclab.nl does not seem to have these records but instead have a NS record (that eventually also points to an IP owned by UvA): DNS Checker <amsterdammusiclab.nl>.
So probably it's just configuring the DNS correctly to fix this inconsistent behavior.

We'll switch to a new server before long, where we can correct the behaviour. NB this is an issue for the amsterdam-music-lab repo (relating to the blog), so I moved the issue there: https://github.com/Amsterdam-Music-Lab/amsterdam-music-lab/issues/11

authors: BeritJanssen drikusroor hhoning

repo: Amsterdam-Music-Lab/MUSCLE


text:
CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_66cunxm_et/clone/recipe/meta.yaml:20: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_66cunxm_et/clone/recipe/meta.yaml:27: missing_pip_check: For pypi packages, pip check should be present in the test commands
WARNING: /tmp/abs_66cunxm_et/clone/recipe/meta.yaml:35: missing_description: The recipe is missing a description
ERROR: /tmp/abs_66cunxm_et/clone/recipe/meta.yaml:35: missing_documentation: The recipe is missing a doc_url or doc_source_url
Errors were found

authors: anaconda-pkg-build bkreider

repo: AnacondaRecipes/awacs-feedstock


text:
CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_e6sma_iiaa/clone/recipe/meta.yaml:27: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_e6sma_iiaa/clone/recipe/meta.yaml:27: patch_must_be_in_build: patch must be in build when source/patches is set.
ERROR: /tmp/abs_e6sma_iiaa/clone/recipe/meta.yaml:30: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_e6sma_iiaa/clone/recipe/meta.yaml:50: missing_pip_check: For pypi packages, pip check should be present in the test commands
ERROR: /tmp/abs_e6sma_iiaa/clone/recipe/meta.yaml:58: missing_license_family: The recipe is missing the about/license_family key.
WARNING: /tmp/abs_e6sma_iiaa/clone/recipe/meta.yaml:58: missing_description: The recipe is missing a description
Errors were found


text:
Build v 0.3.0:

Upstream: https://github.com/plotly/dash-cytoscape/tree/v0.3.0
Jira: PKG-2625

Required by interpret*
Added a patch to point to the correct package.json file location in setup.py.
noarch removed, script command updated and deps updated as required.

some extra deps are used in examples, so maybe consider putting them in run_constrains, otherwise LGTM

I don't think that is necessary or wanted.

some more requierements are needed, see https://github.com/plotly/dash-cytoscape/blob/v0.3.0/requirements.txt ?
biopython>=1.77
gunicorn
plotly
colour==0.1.5
?

Those are dev dependencies


text:
Mode modifiers not being stripped from pcre

It looks like you are not pulling out mode modifiers from pcre.  When converting to (at least) a javascript regex, they are not valid and should be stripped. https://www.regular-expressions.info/refmodifiers.html
var a = "((?i)\b\d{5}(?:[-\s]\d{4})?\b)|(\b([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9][A-Za-z]?))))\s?[0-9][A-Za-z]{2}))|(\b[A-Za-z]\d[A-Za-z][ -]?\d[A-Za-z]\d\b)"
RegexTranslator.getRegexStringFromMediaryString(RegexTranslator.getMediaryStringFromRegexString(a, "pcre"), "ecma")
Output:
'((?i)\bd{5}(?:[-s]d{4})?\b)|(\b([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9][A-Za-z]?))))s?[0-9][A-Za-z]{2}))|(\b[A-Za-z]d[A-Za-z][ -]?d[A-Za-z]d\b)'
Expected output:
'(\bd{5}(?:[-s]d{4})?\b)|(\b([Gg][Ii][Rr] 0[Aa]{2})|((([A-Za-z][0-9]{1,2})|(([A-Za-z][A-Ha-hJ-Yj-y][0-9]{1,2})|(([A-Za-z][0-9][A-Za-z])|([A-Za-z][A-Ha-hJ-Yj-y][0-9][A-Za-z]?))))s?[0-9][A-Za-z]{2}))|(\b[A-Za-z]d[A-Za-z][ -]?d[A-Za-z]d\b)'

Thank you for bringing this to my attention; I'll take a look as soon as I'm able.

Any updates?

@ericraio I had actually been working on a massive overhaul of regex-translator that would've included modifiers and just about every other possible regex feature but my lack of experience writing actually parsers and creating abstract syntax trees, as opposed to the simple textual transformation regex-translator currently does, things, unsurprisingly, got complicated and I kind of burned myself out for quite a while.

authors: Anadian ericraio garrettrowe

repo: Anadian/regex-translator


text:
Missing Textures Fix

This is a fix for #3730, though technically it is also a fix for #2997. It seems like #3730 was actually caused by #3011 breaking the resizing behavior of the TextureAtlas.
I included the contents of the TextureAtlas in the top left corner of the screenshots here to illustrate the failures.
The symptom of #2997 was the first letter disappearing.

The cause of this issue was actually the creation of the initial texture in the constructor. The font-size in the reported issue is important to note, because if the image being added was larger than the initial texture, it was re-generated and everything was fine.
#3011 fixed this, but caused issues when textures needed to be resized.
The resize failure can be seen below.
Before resize:

After resize:

I suspect the underlying cause is something to do with the state when the constructor is called. This can be resolved by creating the initial texture when the first image is added.
Here are the examples shown with the fix applied:

Thanks for looking into this, @lasalvavida.
Update CHANGES.md.
Also add a unit test if a reasonable one can be written for this.
@bagnell please review and merge when you are available.

@lasalvavida Are you seeing any test failures?

@bagnell, yes I am. Since the TextureAtlas doesn't rely on a shader + draw command anymore some of the color tests are failing and initial size is only respected when it is greater than the first image added with border, so some of those hard-coded size tests are failing. I'll update the tests.

@bagnell Whenever you get a chance, this is ready for a look

@lasalvavida can you merge in master and fix the conflicts (it's probably just changes.md)
@bagnell it would be nice to get this into the next release.  Can you take a quick look when it's ready?

Merged changes.md

I still see 19 test failures in Chrome 50 that don't occur in master.

@bagnell, test failures should be fixed, and #3730 should no longer be present in @TomPed's example code

The second screenshot is from this CZML example which also seems to behave correctly.

@bagnell The standalone test that I had put together no longer breaks in chrome. I reverted my changes to Texture.js as this no longer appears to be an issue.
The changes to TextureAtlas are still needed to fix #3730

@lasalvavida This looks good. Resolve the conflict with master and I'll merge this.

@bagnell Updated

authors: bagnell lasalvavida mramato pjcozzi

repo: AnalyticalGraphicsInc/cesium


text:
Fix pickPosition accuracy when depthTestAgainstTerrain is false

Fixes https://github.com/AnalyticalGraphicsInc/cesium/issues/8179. Merge https://github.com/AnalyticalGraphicsInc/cesium/pull/8205 first.
Local sandcastle for testing
This builds on top of https://github.com/AnalyticalGraphicsInc/cesium/pull/8205 by using the "everything-else" color texture to determine whether the pick depth should take the scene's depth value or the globe's depth value for a given pixel. If a pixel in the color texture is opaque it writes the scene depth, otherwise it writes the globe depth.
The one downside I noticed so far is that is breaks scene.pickTranslucentDepth since those commands are depth-only and the color texture can't be relied on. I tried a few ideas like writing color in that pass but it exposes a different bug that is very similar to https://github.com/AnalyticalGraphicsInc/cesium/issues/7429 (because my testing Sandcastle happens to use EDL). I have an idea for doing this whole PR differently by rendering a stencil bit for the depth plane and doing a two-pass copy. I'll see how that goes and then bump this PR for review.

Thanks for the pull request @lilleyse!

:heavy_check_mark: Signed CLA found.
:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

@lilleyse the only change in this PR is to CHANGES.md, did you PR into the right branch?

@mramato looks like I accidentally pushed these same changes to the target branch. Should be fixed now.

Need to check if this fixes https://github.com/AnalyticalGraphicsInc/cesium/issues/4368

Decided to go with a different approach. See https://github.com/AnalyticalGraphicsInc/cesium/issues/8179#issuecomment-544529884.

authors: cesium-concierge lilleyse mramato


text:
Use Cesium sun as lightsource for material

When converting Collada models to glTF via the web service you provide and then displaying the model in Cesium makes the model unaffected by the lighting direction of the sun. I saw that the obj2gltf library added a --cesium flag to address this issue. Would it be possible for the web service to provide a similar feature?
As a side note, it is not possible for us to use obj2gltf because of limitations in storing model hierarchies in the obj format, which are needed for rotating parts of the models we use.

@laurensdijkstra I moved this to https://github.com/AnalyticalGraphicsInc/cesium/issues/4207 since this repo is just example code, not the actual model converter used on cesiumjs.org.

Thanks! I was already wondering if this was the right repo because I didn't see any updates since a long time yet online al kinds of new features were added.

authors: laurensdijkstra pjcozzi


text:
关于监督方式

您好，我想请问您这篇工作是有监督还是无监督还是半监督的呢？在论文中我没有看到相关的说明，我看到论文中一方面说没有gt的反射率，一边说使用正常光的反射率，正常光在低光照增强领域一般应该代表标签吧，所以我有些困惑，希望您能给出解答

Hi, 这篇文章使用的是有监督方式的训练，监督标签是用正常光照的图像经过分解之后得到的（伪标签）。关于这个细节的描述可以参考Methods(Initialize Module)

您好，感谢您的回复，最近准备引用您的这篇论文，由于时间有限，想问下您这个模型的参数量和计算量（3×400×600作为输入尺寸）

您好，感谢您的回复，最近准备引用您的这篇论文，由于时间有限，想问下您这个模型的参数量和计算量（3×400×600作为输入尺寸）

authors: AndersonYong szxmachinelearning

repo: AndersonYong/URetinex-Net


text:
Documentation of PartialRenaming

In 03-holes/Main.hs, we have the following lines of code:
-- partial renaming from Γ to Δ
data PartialRenaming = PRen {
    dom :: Lvl                -- size of Γ
  , cod :: Lvl                -- size of Δ
  , ren :: IM.IntMap Lvl }    -- mapping from Δ vars to Γ vars

I don't get why the first comment says that the renaming is from "Γ to Δ", while the last comment says that it's from "Δ vars to Γ vars". Is this a typo?

It's not a typo. A renaming from Gamma to Delta can be represented as a function from Delta vars to Gamma vars. This flipping is a fairly common thing in type theory literature.
For an illustration, assume Gamma = (a : A, b : B) and Delta = (c : C, d : D). Then, in many semantics of a type theory, a renaming from Gamma to Delta is a function of the form \(a, b, c) -> (t1, t2) where t1 and t2 must be variables. However, every such function is determined by a mapping (c |-> t1, d |-> t2) where t1 and t2 are variables. So, a renaming in the forward direction, from Gamma to Delta, is also representable as a function from variables to variables in the backwards direction.

Why \(a, b, c) -> (t1, t2) and not \(a, b) -> (t1, t2)?

Well, that was a typo, edited.

Okay, so PartialRenaming represents a function of the form \(a, b) -> (t1, t2) in the example you've suggested, but is implemented (by the ren field) in the backwards direction (c |-> t1, d |-> t2)?

Yes. It's only "morally" a function \(a, b) -> (t1, t2), not literally. The point is, the direction of the arrow in "renaming from Gamma to Delta" is more useful than the other way around, because it's way more common to have that direction in semantics.

Sweet, thank you for your explanation.

I also have a few questions about the function invert that generates PartialRenaming.
First, I see this comment:
--  invert : (Γ : Cxt) → (spine : Sub Δ Γ) → PRen Γ Δ

But 1) the first parameter is of type Lvl, not Cxt, 2) I don't see Sub Δ Γ defined anywhere in the file, not sure what that means, and 3) spine is not one of the function parameters, invert actually accepts sp.
Next, in the implementation of invert, we construct pure $ PRen dom gamma ren, where dom is the length of the spine, and gamma is the first parameter of invert. But, looking at the docs:
-- partial renaming from Γ to Δ
data PartialRenaming = PRen {
    dom :: Lvl                -- size of Γ
  , cod :: Lvl                -- size of Δ
  , ren :: IM.IntMap Lvl }    -- mapping from Δ vars to Γ vars

dom is actually the "size of Γ" and cod is the "size of Δ", so I am a bit confused why PRen is constructed the other way round in invert.

The definition of `invert`
--  invert : (Γ : Cxt) → (spine : Sub Δ Γ) → PRen Γ Δ
invert :: Lvl -> Spine -> IO PartialRenaming
invert gamma sp = do

  let go :: Spine -> IO (Lvl, IM.IntMap Lvl)
      go []        = pure (0, mempty)
      go (sp :> t) = do
        (dom, ren) <- go sp
        case force t of
          VVar (Lvl x) | IM.notMember x ren -> pure (dom + 1, IM.insert x dom ren)
          _                                 -> throwIO UnifyError

  (dom, ren) <- go sp
  pure $ PRen dom gamma ren

A Sub Gamma Delta is a parallel substitution. A renaming is a special case of a substitution which maps vars to vars. A substitution maps vars to arbitrary values.
Here (spine : Sub Gamma Delta) means that spine is a sequence of values, one value for each variables in Delta, such that each value can depend on variables from Gamma. A spine here is just a list of arguments that a meta is applied to, so it happens to be the same thing as a Sub (both are lists of values). sp is the abbreviation of spine.
Gamma and Delta in PRen Gamma Delta and Sub Gamma Delta are just arbitrary variable names. I can alpha-rename abstracted variables however I like.
In a formalization, we'd write Gamma for a context, but in the implementation the only computationally relevant information is just the length of the context. So in the Haskell code a context becomes a Lvl. If instead of De Bruijn levels and indices, we used non-shadowing names, we would need to pass a list of names instead of a Lvl. But this is mostly an implementation detail, the main idea is to pass enough information about a typing context so that we can create a variable that's fresh in that context.

Maybe you meant Sub Delta Gamma instead of Sub Gamma Delta? Because the code says Sub Δ Γ.
Also, I don't understand why we do IM.insert x dom ren, i.e., associating a gamma-variable x with a delta-variable dom, while PartialRenaming says that ren maps delta-variables to gamma-variables.

The choice of gamma and delta is completely arbitrary and you can consistently rename them in any context. When I talk about functions from A to B the names "A" and "B" have no importance at all. Same with gamma and delta.

Interesting. I think I've understood the Haskell implementation itself, but the comment introduce so much confusion to me. Perhaps they'd be more clear considering the formalism...
Anyhow, thank you for the help!

authors: AndrasKovacs Hirrolot

repo: AndrasKovacs/elaboration-zoo