id
stringlengths 4
10
| text
stringlengths 4
2.14M
| source
stringclasses 2
values | created
timestamp[s]date 2001-05-16 21:05:09
2025-01-01 03:38:30
| added
stringdate 2025-04-01 04:05:38
2025-04-01 07:14:06
| metadata
dict |
|---|---|---|---|---|---|
472752030 | HHH-13511 Remove interning of aliases in org.hibernate.loader.Default…
…EntityAliases
Being discussed with @dreab8 and @gsmet
fixed and merged
| gharchive/pull-request | 2019-07-25T09:10:12 | 2025-04-01T06:38:56.820455 | {
"authors": [
"Sanne"
],
"repo": "hibernate/hibernate-orm",
"url": "https://github.com/hibernate/hibernate-orm/pull/2954",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
525243943 | HHH-13355 : StaleStateException for updates to optional secondary table using saveOrUpdate
https://hibernate.atlassian.net/browse/HHH-13355
rebased and applied upstream
thanks @gbadner
| gharchive/pull-request | 2019-11-19T20:21:15 | 2025-04-01T06:38:56.822078 | {
"authors": [
"dreab8",
"gbadner"
],
"repo": "hibernate/hibernate-orm",
"url": "https://github.com/hibernate/hibernate-orm/pull/3106",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1113337365 | Fix race condition that allowed Component.getType() to return null
This fix prevents an NPE in org.hibernate.mapping.SimpleValue.isValid() and likely elsewhere
Thanks for the fix!
| gharchive/pull-request | 2022-01-25T02:03:37 | 2025-04-01T06:38:56.822903 | {
"authors": [
"TheCodePope",
"beikov"
],
"repo": "hibernate/hibernate-orm",
"url": "https://github.com/hibernate/hibernate-orm/pull/4700",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1449462878 | HSEARCH-4722 Fix postgresql container start timing out on CI
https://hibernate.atlassian.net/browse/HSEARCH-4722
Backported to 6.1 and 6.0.
| gharchive/pull-request | 2022-11-15T09:34:24 | 2025-04-01T06:38:56.823967 | {
"authors": [
"marko-bekhta",
"yrodiere"
],
"repo": "hibernate/hibernate-search",
"url": "https://github.com/hibernate/hibernate-search/pull/3308",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1615258687 | HSEARCH-2366 Add an Elasticsearch mapping export tool
https://hibernate.atlassian.net/browse/HSEARCH-2366
Should we add some options parameter into the export method even if it'll be empty for now or contain some setting to export mappings (what it's doing now) so that in the future we won't break the API or ... as it's incubating - don't bother with it now and later we'll just break the API? 😄
Then there also was a mention of a CLI ... is that what we need or that was just a thought?
[ERROR] --[ Constraint Violation ]-----------------------------------------
[ERROR] Constraint: hsearch:TypesExtendingTypeFromAnotherModuleMustHaveModuleSpecificKeywordInName
[ERROR] Severity: MAJOR
[ERROR] Number of rows: 2
[ERROR] Main (non-test) types extending/implementing a Hibernate Search type from another module must have a module-specific keyword in their name,
[ERROR] either at the very start or just after "Abstract".
[ERROR] This allows to more easily understand which module a given type comes from.
[ERROR] Exceptions are allowed when:
[ERROR] - the misnamed type is an anonymous type or a generated type;
[ERROR] - or the misnamed type is deprecated;
[ERROR] - or the implemented type is deprecated;
[ERROR] - or the implementing type is an inner/nested type;
[ERROR] and its surrounding type does use the module-specific keyword;
[ERROR] - or the implemented type is in a util module,
[ERROR] in which case the implemented interface may just be a detail.
[ERROR]
[ERROR] misnamedTypeArtifact.moduleSpecificKeyword=Pojo, misnamedType=org.hibernate.search.mapper.pojo.schema.management.impl.FileSearchSchemaCollector, externalParentType=org.hibernate.search.engine.backend.schema.management.IndexSchemaCollector
[ERROR] misnamedTypeArtifact.moduleSpecificKeyword=Pojo, misnamedType=org.hibernate.search.mapper.pojo.schema.management.SearchSchemaCollector, externalParentType=org.hibernate.search.engine.backend.schema.management.IndexSchemaCollector
[ERROR] -------------------------------------------------------------------
[ERROR]
I cannot say that I like the idea of naming these PojoSearchSchemaCollector and PojoFileSearchSchemaCollector / PojoSearchSchemaCollectorToFiles ... 🥲
I cannot say that I like the idea of naming these PojoSearchSchemaCollector and PojoFileSearchSchemaCollector / PojoSearchSchemaCollectorToFiles ...
The one about FileSearchSchemaCollector will disappear once we solve the problem for SearchSchemaCollector, I think.
Two solutions:
Add an exception to the JQAssistant rule...
Use composition instead of inheritance. I.e. make IndexSchemaCollector SPI, don't extend it in SearchSchemaCollector, declare an exportExpectedSchema method in SearchSchemaCollector, and in org.hibernate.search.mapper.pojo.schema.management.impl.PojoScopeSchemaManagerImpl#exportExpectedSchema(org.hibernate.search.mapper.pojo.schema.management.SearchSchemaCollector) create an instance of IndexSchemaCollector that delegates to the SearchSchemaCollector.
Your choice!
| gharchive/pull-request | 2023-03-08T13:17:38 | 2025-04-01T06:38:56.828614 | {
"authors": [
"marko-bekhta",
"yrodiere"
],
"repo": "hibernate/hibernate-search",
"url": "https://github.com/hibernate/hibernate-search/pull/3437",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
617341658 | HV-1775 Rename CDI extension service file for new jakarta package
Signed-off-by: Gaurav Gupta gaurav.gupta@payara.fish
Can one of the admins add this person to the trusted builders? (reply with: "add to whitelist" or "ok to test")
ok to test
@jGauravGupta thanks! Unfortunately, I wasn't able to test the CDI extension back in the time because I had no CDI implementation available.
I amended your commit to include a JIRA issue number.
Do you have more fixes coming or should I release an Alpha2?
OK, I was able to restore the CDI extension tests as Weld has made progress on their side.
Following your PR, all the tests pass so I'm releasing 7.0.0.Alpha2. It should synced to Central sometime tomorrow.
@jGauravGupta Alpha2 is now available on Central.
Thanks @gsmet
| gharchive/pull-request | 2020-05-13T10:42:17 | 2025-04-01T06:38:56.832040 | {
"authors": [
"Hibernate-CI",
"gsmet",
"jGauravGupta"
],
"repo": "hibernate/hibernate-validator",
"url": "https://github.com/hibernate/hibernate-validator/pull/1095",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
1555549891 | 🛑 Kiwi Farms Forum is down
In b288de8, Kiwi Farms Forum (https://kiwifarms.net) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Kiwi Farms Forum is back up in 7dae57b.
| gharchive/issue | 2023-01-24T19:30:58 | 2025-04-01T06:38:56.846393 | {
"authors": [
"hickoryhouse"
],
"repo": "hickoryhouse/kf",
"url": "https://github.com/hickoryhouse/kf/issues/122",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2053087506 | 🛑 Kiwi Farms Forum is down
In 413fd28, Kiwi Farms Forum (https://kiwifarms.net) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Kiwi Farms Forum is back up in e775532 after 5 minutes.
| gharchive/issue | 2023-12-21T21:38:08 | 2025-04-01T06:38:56.848999 | {
"authors": [
"hickoryhouse"
],
"repo": "hickoryhouse/kf",
"url": "https://github.com/hickoryhouse/kf/issues/1460",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1565066001 | 🛑 Kiwi Farms Forum is down
In bed5e56, Kiwi Farms Forum (https://kiwifarms.net) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Kiwi Farms Forum is back up in c55c6eb.
| gharchive/issue | 2023-01-31T22:04:12 | 2025-04-01T06:38:56.851298 | {
"authors": [
"hickoryhouse"
],
"repo": "hickoryhouse/kf",
"url": "https://github.com/hickoryhouse/kf/issues/147",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2055776991 | 🛑 kiwifarms.st is down
In e8acb74, kiwifarms.st (https://kiwifarms.st) was down:
HTTP code: 0
Response time: 0 ms
Resolved: kiwifarms.st is back up in 2544295 after 15 minutes.
| gharchive/issue | 2023-12-25T16:40:09 | 2025-04-01T06:38:56.854446 | {
"authors": [
"hickoryhouse"
],
"repo": "hickoryhouse/kf",
"url": "https://github.com/hickoryhouse/kf/issues/1907",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2070637459 | 🛑 kiwifarms.st is down
In 0b13013, kiwifarms.st (https://kiwifarms.st) was down:
HTTP code: 0
Response time: 0 ms
Resolved: kiwifarms.st is back up in 750bf35 after 13 minutes.
| gharchive/issue | 2024-01-08T15:01:08 | 2025-04-01T06:38:56.857419 | {
"authors": [
"hickoryhouse"
],
"repo": "hickoryhouse/kf",
"url": "https://github.com/hickoryhouse/kf/issues/2970",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2071680697 | 🛑 kiwifarms.st is down
In 3e4a39d, kiwifarms.st (https://kiwifarms.st) was down:
HTTP code: 0
Response time: 0 ms
Resolved: kiwifarms.st is back up in 5cd1be3 after 14 minutes.
| gharchive/issue | 2024-01-09T05:57:43 | 2025-04-01T06:38:56.860657 | {
"authors": [
"hickoryhouse"
],
"repo": "hickoryhouse/kf",
"url": "https://github.com/hickoryhouse/kf/issues/3018",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1759693018 | Descriptor protocall
This PR introduces descriptor protocol for constrained class fields, so one doesn't have to test (mostly) for the constraints on the arguments in the init method.
@landreman
This is ready for review
| gharchive/pull-request | 2023-06-16T00:03:50 | 2025-04-01T06:38:56.881281 | {
"authors": [
"mbkumar"
],
"repo": "hiddenSymmetries/simsopt",
"url": "https://github.com/hiddenSymmetries/simsopt/pull/326",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
361904747 | Function missing return statement
Hi,
First, thanks for the lib! It has helped me immensely get the DAC working with zero effort :)
However, there is just one issue reported by the compiler, which would be nice if it were fixed:
MCP4728.h: In member function 'uint8_t MCP4728::analogWrite(MCP4728::DAC_CH, uint16_t, bool)':
MCP4728.h:44:5: warning: no return statement in function returning non-void [-Wreturn-type]
The warning is pretty self-explanatory, literally just the return keyword is missing in the method implementation: https://github.com/hideakitai/MCP4728/blob/master/MCP4728.h#L43
Thanks,
Doug.
Hi, thank you for using and reporting issue!
I've fixed it in b2462e0e867b733ec51de99e3ff040c22e86780d, so check it out and let me know if you have another problem :) Thanks!
| gharchive/issue | 2018-09-19T19:59:36 | 2025-04-01T06:38:56.884064 | {
"authors": [
"LouDou",
"hideakitai"
],
"repo": "hideakitai/MCP4728",
"url": "https://github.com/hideakitai/MCP4728/issues/1",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1290248044 | 🛑 Misskey (隠れ家) is down
In fae050f, Misskey (隠れ家) (https://misskey.yukineko.me) was down:
HTTP code: 403
Response time: 264 ms
Resolved: Misskey (隠れ家) is back up in b324456.
| gharchive/issue | 2022-06-30T14:48:46 | 2025-04-01T06:38:56.889091 | {
"authors": [
"hideki0403"
],
"repo": "hideki0403/status.yukineko.me",
"url": "https://github.com/hideki0403/status.yukineko.me/issues/392",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1555751039 | 🛑 SSH Singapore 3 is down
In 09c3392, SSH Singapore 3 (http://sg3.hidesvr.xyz:3128) was down:
HTTP code: 0
Response time: 0 ms
Resolved: SSH Singapore 3 is back up in a882902.
| gharchive/issue | 2023-01-24T22:13:05 | 2025-04-01T06:38:56.891500 | {
"authors": [
"hidessh99"
],
"repo": "hidessh99/up-ssh",
"url": "https://github.com/hidessh99/up-ssh/issues/114",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1013585151 | Implement GuildJoinEvent
Summary
Separate the guild join event from the guild available event since apparently, new guilds won't have the unavailable field present.
Checklist
[x] I have run nox and all the pipelines have passed.
[ ] I have made unittests according to the code I have added/modified/deleted.
Will the fragment go under feature or breaking?
Will the fragment go under feature or breaking?
likely breaking.
One test case missing, but LGTM
Is it related to guild available event?
Is it related to guild available event?
Amazingly GitHub didn't post my comment with it. Thanks GitHub.
The test case is to check what event gets deserialized based on whether unavailable is there or not
Is it related to guild available event?
Amazingly GitHub didn't post my comment with it. Thanks GitHub.
The test case is to check what event gets deserialized based on whether unavailable is there or not
Happens I guess. I see, I'll get into it today.
Added more test cases on 41ce43c4260cd566c6ef94fdf70839787508ddca. It's mostly copy-pasted because the only difference was the event type. Should I parametrize this?
| gharchive/pull-request | 2021-10-01T17:14:52 | 2025-04-01T06:38:56.977358 | {
"authors": [
"Jonxslays",
"davfsa",
"norinorin"
],
"repo": "hikari-py/hikari",
"url": "https://github.com/hikari-py/hikari/pull/809",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
58091926 | Still having odd display issue
After implementing the CSS fix from issue #72, we're still seeing odd display flickers and artifacts. To make sure it was not just our instance, I pulled up the countdown homepage and was able to duplicate the problem there (see attached).
Sometimes it is a relatively small line like this:
Sometimes it is significantly larger:
Anyone have thoughts as to what would be causing that? We're seeing it on a number of displays, cards, and OSes, so it doesn't seem to be specific to the hardware or the OS. It does, however, seem to be more common in Chrome than any other browser.
Thank you for your feedback, but this problem seems to be caused by hardware acceleration, dunno if there is a way around by css/html.
I never saw this bug on my computer though, and I use Chrome has my main browser, I think we need to investigate the real cause of this issue.
This happens on Chrome and Opera if I recall correctly. On FF there is no such bug, so it's definitely a rendering issue.
Is it specific to the "flip" clock implementation? I have used the clock
without the flip animation and never had issues. So I'm wondering if it's
something in that specific use case.
For me it happened only with the flip clock. From what I can tell other people only have the issue with the flip clock as well.
Guys, it's an issue with the CSS of the flip clock, I really don't have much experience with 3d animations and hardware acceleration at CSS level. Do you guys can guess where we begin to solve this problem?
The issue seems to go away when the perspective value for .main-example .time is under 480px. When I set it to 479px everything is displayed perfectly, but when I increase it to 480px the artifacts come back. This is very weird but seems to work for me.
For me it goes away when I put perspective to 0px;
The problem is not the script itself, but the machine hardware
acceleration! The output will dependent on your computer
Em sex, 27 de mar de 2015 06:04, dingo-d notifications@github.com
escreveu:
For me it goes away when I put perspective to 0px;
—
Reply to this email directly or view it on GitHub
https://github.com/hilios/jQuery.countdown/issues/100#issuecomment-86873713
.
Yeah, I think it also depends on the browser, because if I recall correctly, on firefox the issue didn't exist. And ff is known to handle css3 transformations better than chrome (or webkit based browsers).
Another thing I noticed that at transform: rotateX(90deg) the card is still visible. It seems that the transformation origin is not aligned properly.
| gharchive/issue | 2015-02-18T16:36:37 | 2025-04-01T06:38:56.990323 | {
"authors": [
"MichaelTurk",
"dingo-d",
"hilios",
"vilius-g"
],
"repo": "hilios/jQuery.countdown",
"url": "https://github.com/hilios/jQuery.countdown/issues/100",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
925583910 | Installation Error: Stable_baselines
Hey guys! Basically I was just trying to install stable_baselines on Mac m1
Here is the code:
pip install stable-baselines
stable_baselines_error.txt
I got nothing. Please help me!!!!!
Looks like either Numpy or OpenCV could not be installed. I would recommend checking their communities for help on this.
PS: stable-baselines3 is more actively maintained, so you might want to try if it works :)
Looks like either Numpy or OpenCV could not be installed. I would recommend checking their communities for help on this.
PS: stable-baselines3 is more actively maintained, so you might want to try if it works :)
Thank You for your advice. I did try stable-baselines3 then I got:
stable_baselines3_error.txt
Then back to stable_baselines, I thought I should fix the opencv problem first, so I try to install OpenCV, then I got:
opencv_error.txt
I think there is a link.
Yeah indeed these are numpy and OpenCV errors. Looks like the older versions of these libraries do not work.
Try installing stable-baselines3 with only pip install stable-baselines3 (without the [extra]). That skips OpenCV installation but it is only used for some rendering purposes (visualizing envs etc).
pip_install_stable-baselines3.txt
I used pip install stable-baselines3 still got error. This sucks :(
I just realized we had same problem here: https://github.com/DLR-RM/stable-baselines3/issues/360
Try using conda to install libraries instead of pip.
Last login: Mon Jun 21 10:24:42 on ttys001
(base) zhangjing@zhangjingdeMacBook-Pro ~ % conda activate tf_m1
(tf_m1) zhangjing@zhangjingdeMacBook-Pro ~ % conda install -c conda-forge stable-baselines3 -y
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: |
Found conflicts! Looking for incompatible packages.
This can take several minutes. Press CTRL-C to abort.
failed
UnsatisfiableError: The following specifications were found to be incompatible with each other:
Output in format: Requested package -> Available versions
(tf_m1) zhangjing@zhangjingdeMacBook-Pro ~ % conda install stable-baselines
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
PackagesNotFoundError: The following packages are not available from current channels:
- stable-baselines
Current channels:
- https://repo.anaconda.com/pkgs/main/osx-arm64
- https://repo.anaconda.com/pkgs/main/noarch
- https://repo.anaconda.com/pkgs/r/osx-arm64
- https://repo.anaconda.com/pkgs/r/noarch
- https://conda.anaconda.org/conda-forge/osx-arm64
- https://conda.anaconda.org/conda-forge/noarch
To search for alternate channels that may provide the conda package you're
looking for, navigate to
https://anaconda.org
and use the search bar at the top of the page.
(tf_m1) zhangjing@zhangjingdeMacBook-Pro ~ % conda install stable-baselines3
Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: failed with repodata from current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Solving environment: -
Found conflicts! Looking for incompatible packages.
This can take several minutes. Press CTRL-C to abort.
failed
UnsatisfiableError: The following specifications were found to be incompatible with each other:
Output in format: Requested package -> Available versions
Still nothing 0.0
stable-baselines is not in conda repositories... Please look at the link I gave you.
I am not able to give further technical support on this as the issue lies in the dependencies of stable-baselines, not the stable-baselines itself, and close this issue as "no tech support".
| gharchive/issue | 2021-06-20T12:03:27 | 2025-04-01T06:38:56.999871 | {
"authors": [
"JingZhang918",
"Miffyli"
],
"repo": "hill-a/stable-baselines",
"url": "https://github.com/hill-a/stable-baselines/issues/1124",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
193408190 | 游戏超时判断如何实现
应用场景：游戏倒计时30s结束给出游戏结果，在游戏中用户可能会切换到其他页面再回到游戏页面，不知道具体的实现步骤是怎样的，希望指点一下
开始时保存下结束时间new Date().getTime() + 3000;，然后定时器里判断当前时间和结束时间的对比
可以看这个demo： http://runjs.cn/detail/lvjkgzrw
thanks, the best wishes
@06wj 应用时textAlign和textVAlign不生效
@06wj 看源码知道还需要初始一下宽高就能正常使用textAlign和textVAlign了，这个建议落实到文档提醒下开发者
new Hilo.Text({
font: "bold 43px arial,sans-serif",
textAlign:'right',
textVAlign:'middle',
width: 720,
height: 1080,
text:'30s'
}).addTo(stage);
好 因为canvas本身没这个属性，是用过js根据width,height设置位置实现的，我加到文档里
@jingchaofang http://hiloteam.github.io/Hilo/docs/api-zh/symbols/Text.html#textAlign 已加
建议提供自动计算文字大小的功能。这个并不难。
我之前写的一个 Canvas的Label组件里有类似这样的代码：
if (this._autoSizeWithText && this.textHolder) {
if (this.textHolder.needToCompute) {
this.textHolder.computeSize();
this.computeSizeWithText();
}
}
当没有给Label组件设置大小的时候，则采用『文本内容多大，Label组件就多大』的方案。
宽度用 context.measureText 计算。
高度可以用一个专门计算高度的临时canvas来做，提前计算好。 字体，字号和 高度的映射关系。
（一个游戏里的字体和字号是有限的，不可能想做字处理软件一样无法确定用户到底要用什么字体什么字号）
宽高计算好之后要记得 加上 描边、阴影一类的大小。
自动计算文字大小功能有的，只是textAlign和textVAlign需要手动提供对象的宽高才能实现啊
@06wj ， 哦 明白了， 他说的这个 textAlign 是 label 内的 对齐方式， 不是label容器的。我理解错了
| gharchive/issue | 2016-12-05T04:14:11 | 2025-04-01T06:38:57.006068 | {
"authors": [
"06wj",
"finscn",
"jingchaofang"
],
"repo": "hiloteam/Hilo",
"url": "https://github.com/hiloteam/Hilo/issues/62",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1067233829 | Visualization part
Hi,
Great work and thanks for sharing the code. Could ask how did you visualize the result? Could you share the scripts?
Best,
Wei
Hi Wei,
Once you trained the model, you can use test.py script to generate predictions and these predictions will be saved as MRI volumes. You can use MRI/CT viewing application to view those predictions. For example, I use Mango Software: https://en.wikipedia.org/wiki/Mango_(software) . There is an option to get snapshots of the slices that you want to save as images.
Best Regards,
Himashi
| gharchive/issue | 2021-11-30T13:23:54 | 2025-04-01T06:38:57.008964 | {
"authors": [
"himashi92",
"xiaoiker"
],
"repo": "himashi92/VT-UNet",
"url": "https://github.com/himashi92/VT-UNet/issues/1",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1238224179 | 大文字やんけ
https://github.com/hiraginoyuki/webpack.15-puzzle.app/blob/master/src/app/app.tsx#L14
わろた
なぜ抜けた
わろた
| gharchive/issue | 2022-05-17T07:52:16 | 2025-04-01T06:38:57.042673 | {
"authors": [
"Mogyuchi",
"hiraginoyuki"
],
"repo": "hiraginoyuki/webpack.15-puzzle.app",
"url": "https://github.com/hiraginoyuki/webpack.15-puzzle.app/issues/46",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
187069380 | i am getting this error, only in devices: Crashed: swift.imageloader.queues.io
UIImageView+ImageLoader.swift line 29
specialized UIImageView.(url.getter).(closure #1)
Thank you for the issue.
I fix by #95
I released 0.12.0.
| gharchive/issue | 2016-11-03T14:07:33 | 2025-04-01T06:38:57.044364 | {
"authors": [
"hirohisa",
"lalmachado"
],
"repo": "hirohisa/ImageLoaderSwift",
"url": "https://github.com/hirohisa/ImageLoaderSwift/issues/94",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1922135625 | Broken link -- Page not found --using clarity values --> "response value utilization"
Link to "response value utilization much simpler" sends to a 'page not found'
Hi @losatnick !
The mentioned link seems to be working properly. Can we close this issue?
The link still isn't working for me - I've attached a screenshot of the section im referencing
Are you following this link? https://docs.hiro.so/get-started/stacks-blockchain-api#using-clarity-values
Ah yeah - the second link is the one that I was viewing and discovered the broken link
All the docs im reviewing I'm getting to from hiro.so --> docs
Fixed by https://github.com/hirosystems/stacks-blockchain-api/pull/1726
| gharchive/issue | 2023-10-02T15:22:51 | 2025-04-01T06:38:57.048630 | {
"authors": [
"MicaiahReid",
"csgui",
"losatnick"
],
"repo": "hirosystems/docs",
"url": "https://github.com/hirosystems/docs/issues/486",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
592920619 | Registering the service one should provide absolute path, otherwise exception is thrown
When registering service via services.AddJsonLocalization, if the path is not an absolute one it will throw the following exception when resolving the files by IStringLocalizer
// this will cause an error when _localizer["Hello"] is called later on
services.AddJsonLocalization(options => options.ResourcesPath = "Resources");
it should be changed to
var directory = Path.Combine(Directory.GetCurrentDirectory(), "Resources");
services.AddJsonLocalization(options => options.ResourcesPath = directory);
the latter will work perfect.
I think that extra line can be moved to the library itself.
System.ArgumentException: The path must be absolute. (Parameter 'root')
at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root, ExclusionFilters filters)
at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root)
at Microsoft.Extensions.Configuration.FileConfigurationExtensions.SetBasePath(IConfigurationBuilder builder, String basePath)
at My.Extensions.Localization.Json.JsonStringLocalizer.<>c__DisplayClass17_0.<BuildResourcesCache>b__0(String _)
at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
at My.Extensions.Localization.Json.JsonStringLocalizer.BuildResourcesCache(String culture)
at My.Extensions.Localization.Json.JsonStringLocalizer.GetStringSafely(String name)
at My.Extensions.Localization.Json.JsonStringLocalizer.get_Item(String name)
at My.Extensions.Localization.Json.Internal.StringLocalizer.get_Item(String name)
HEADERS
=======
Accept-Language: fr-FR
Thanks for reporting this, but did you try to run the sample, it should work as expected
Dear @hishamco, thanks for the prompt reply, yes I ran the sample with a controller trying to use IStringLocalizer
@shahabganji let me try your scenario to make sure that I can reproduce the bug, if you think your fix is a real bug, you could send a PR if you want ..
Thanks
@hishamco The PR created, hope it helps
I need to check the sample with your changes first before I review the PR
Thanks
@shahabganji I think there's some confusion here you 're using IStringLocalizer instead of IStringlocalizer<T> which is may causes a strange behavior
Please refer to my new added sample here
Hope it clarifies what's the preferred localizer you should use as well as resource name conventions
Merged into dev
@hishamco
I still get the same error, even with IStringLocalizer<HomeController>; besides using IStringLocalizer<T> only loads messages from T.{culture}.json file, right? however, using non-generic IStringLocalizer will load messages which are not only for a specific class/controller, like some global shared messages.
I added the following to resolve problem in Startup -> ConfigureServices
services.AddJsonLocalization(
options => options.ResourcesPath = Path.Combine(
Directory.GetCurrentDirectory(), "Resources"));
without that it is like :
note that the response is 500 Internal Server Error
and this is the log :
Microsoft.AspNetCore.Server.Kestrel: Error: Connection id "0HLUNLKCTNMP6", Request id "0HLUNLKCTNMP6:00000001": An unhandled exception was thrown by the application.
System.ArgumentException: The path must be absolute. (Parameter 'root')
at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root, ExclusionFilters filters)
at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root)
at Microsoft.Extensions.Configuration.FileConfigurationExtensions.SetBasePath(IConfigurationBuilder builder, String basePath)
at My.Extensions.Localization.Json.JsonStringLocalizer.<>c__DisplayClass16_0.<BuildResourcesCache>b__0(String _) in /Users/shahab/dev/playground/My.Extensions.Localization.Json/src/My.Extensions.Localization.Json/JsonStringLocalizer.cs:line 173
at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
at My.Extensions.Localization.Json.JsonStringLocalizer.BuildResourcesCache(String culture) in /Users/shahab/dev/playground/My.Extensions.Localization.Json/src/My.Extensions.Localization.Json/JsonStringLocalizer.cs:line 162
at My.Extensions.Localization.Json.JsonStringLocalizer.GetStringSafely(String name) in /Users/shahab/dev/playground/My.Extensions.Localization.Json/src/My.Extensions.Localization.Json/JsonStringLocalizer.cs:line 101
at My.Extensions.Localization.Json.JsonStringLocalizer.get_Item(String name) in /Users/shahab/dev/playground/My.Extensions.Localization.Json/src/My.Extensions.Localization.Json/JsonStringLocalizer.cs:line 42
at Microsoft.Extensions.Localization.StringLocalizer`1.get_Item(String name)
at LocalizationSample.Mvc.Controllers.HomeController.Index() in /Users/shahab/dev/playground/My.Extensions.Localization.Json/samples/LocalizationSample.Mvc/Controllers/HomeController.cs:line 19
at lambda_method(Closure , Object , Object[] )
at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target, Object[] parameters)
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncObjectResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeFilterPipelineAsync>g__Awaited|19_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)
That means the error occurs when you are using IStringLocalizer alone or beside IStringLocalizer<T> right?
I just checked out the project and run the new sample as dotnet project. I have the same error no matter which type of usage, IStringLocalizer<T> alone also produces the error. using both together also produces error.
my current controller :
using System;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Extensions.Localization;
namespace LocalizationSample.Mvc.Controllers
{
[Route("")]
public class HomeController : Controller
{
private readonly IStringLocalizer<HomeController> _localizer;
public HomeController(IStringLocalizer<HomeController> localizer)
{
_localizer = localizer ?? throw new ArgumentNullException(nameof(localizer));
}
public string Index()
{
var result = _localizer["Hello"].Value;
return result;
}
}
}
and Startup.cs
using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Hosting;
using Microsoft.Extensions.DependencyInjection;
using Microsoft.Extensions.Hosting;
namespace LocalizationSample.Mvc
{
public class Startup
{
public void ConfigureServices(IServiceCollection services)
{
services.AddControllers();
services.AddJsonLocalization(options => options.ResourcesPath = "Resources");
}
public void Configure(IApplicationBuilder app, IWebHostEnvironment env)
{
app.UseRequestLocalization("en-US", "fr-FR");
if (env.IsDevelopment())
{
app.UseDeveloperExceptionPage();
}
app.UseRouting();
app.UseEndpoints(endpoints => endpoints.MapControllers());
}
}
}
I have two resource files, HomeController.fr-FR.json and fr-FR.json
changed the line to services.AddJsonLocalization( options => options.ResourcesPath = Path.Combine(Directory.GetCurrentDirectory(), "Resources")); and it works like a charm.
Also changing Line 174 to
.SetBasePath(Path.Combine(Directory.GetCurrentDirectory() ,_resourcesPath))
solved the issue.
I did few updates after I support JsonHtmlLocalizer, I will try to use IStringLocalizer alongside with IStringLocalizer to reproduce the error
you mean IStringLocalizer alongside with IStringLocalizer<T>? but in this case IStringLocalizer<T> also throws an exception. Anyway thanks for the follow ups.
Seems I confused, could please try the latest sample LocalizationSample.Mvc and let me know what are the required changes to raise the error
I exactly did that. please check here and here
I just checked out the project and run the new sample as dotnet project. I have the same error no matter which type of usage, IStringLocalizer alone also produces the error. using both together also produces error.
Seems you didn't fetch the latest bits ;) I just merged a new commits anyhow I don't have such T.{culture}.json file, furthermore there's no error occurs on IStringLocalizer<HomeController> at all
This is a French version of how Privacy page is look like at my end
By T I meant HomeController, I pulled the latest version, however, the problem still exist.
URL: https://localhost:8001/Home/Privacy/?culture-fr-FR&ui-culture=fr-FR
error the same as before:
Microsoft.AspNetCore.Server.Kestrel: Error: Connection id "0HLUNMASR1PM7", Request id "0HLUNMASR1PM7:00000001": An unhandled exception was thrown by the application.
System.ArgumentException: The path must be absolute. (Parameter 'root')
at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root, ExclusionFilters filters)
at Microsoft.Extensions.FileProviders.PhysicalFileProvider..ctor(String root)
at Microsoft.Extensions.Configuration.FileConfigurationExtensions.SetBasePath(IConfigurationBuilder builder, String basePath)
at My.Extensions.Localization.Json.JsonStringLocalizer.<>c__DisplayClass16_0.<BuildResourcesCache>b__0(String _) in /Users/shahab/dev/playground/My.Extensions.Localization.Json/src/My.Extensions.Localization.Json/JsonStringLocalizer.cs:line 173
at System.Collections.Concurrent.ConcurrentDictionary`2.GetOrAdd(TKey key, Func`2 valueFactory)
at My.Extensions.Localization.Json.JsonStringLocalizer.BuildResourcesCache(String culture) in /Users/shahab/dev/playground/My.Extensions.Localization.Json/src/My.Extensions.Localization.Json/JsonStringLocalizer.cs:line 162
at My.Extensions.Localization.Json.JsonStringLocalizer.GetStringSafely(String name) in /Users/shahab/dev/playground/My.Extensions.Localization.Json/src/My.Extensions.Localization.Json/JsonStringLocalizer.cs:line 101
at My.Extensions.Localization.Json.JsonStringLocalizer.get_Item(String name) in /Users/shahab/dev/playground/My.Extensions.Localization.Json/src/My.Extensions.Localization.Json/JsonStringLocalizer.cs:line 42
at Microsoft.Extensions.Localization.StringLocalizer`1.get_Item(String name)
at LocalizationSample.Mvc.Controllers.HomeController.Privacy() in /Users/shahab/dev/playground/My.Extensions.Localization.Json/samples/LocalizationSample.Mvc/Controllers/HomeController.cs:line 22
at lambda_method(Closure , Object , Object[] )
at Microsoft.Extensions.Internal.ObjectMethodExecutor.Execute(Object target, Object[] parameters)
at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextResourceFilter>g__Awaited|24_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Rethrow(ResourceExecutedContextSealed context)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.InvokeFilterPipelineAsync()
--- End of stack trace from previous location where exception was thrown ---
at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeAsync>g__Awaited|17_0(ResourceInvoker invoker, Task task, IDisposable scope)
at Microsoft.AspNetCore.Routing.EndpointMiddleware.<Invoke>g__AwaitRequestTask|6_0(Endpoint endpoint, Task requestTask, ILogger logger)
at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.Server.Kestrel.Core.Internal.Http.HttpProtocol.ProcessRequests[TContext](IHttpApplication`1 application)
I did the same thing to solve the problem and it worked.
I don't know whether the OS matters or not, mine is Mac OS X
I see, I don't now you are running on Mac OS, so I need to create a functional test, so AzurePipeline should fail if there's issue
I will try create it ASAP
Thanks again
Also I will try your change to check if it's work with me too on Windows
If you wish to create a functional test that runs the LocalizationSample.Mvc that I created in you PR it will be very good to make sure that your changes works on ever OS
No problem I'll put a time on that.
I request few changes on your PR, please fix them and let me know if you need help on creating a functional test
Sure, just give me some time till evening, currently at the middle of some important stuff, is that okay?
Take your time .. I will try to fix and improve something else meanwhile
Dear @hishamco, check PR #44 . I've added a functional test for one of the samples, LocalizationSample, do we need another one for LocalizationSample.Mvc?
I will have a look ...
Thanks
@hishamco Please also update the nuget feed. thanks 🙏
Do you mean upload a NuGet package?
Yes.
Am 03.04.2020 um 20:19 schrieb Hisham Bin Ateya notifications@github.com:
Do you mean upload a NuGet package?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
I need to add some new features, then I will release 2.1.0 hope this will not take more than few days
| gharchive/issue | 2020-04-02T21:16:23 | 2025-04-01T06:38:57.090378 | {
"authors": [
"hishamco",
"shahabganji"
],
"repo": "hishamco/My.Extensions.Localization.Json",
"url": "https://github.com/hishamco/My.Extensions.Localization.Json/issues/43",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2114262547 | NuxtIcon not rendered in Histoire
Describe the bug
After having a lot of trouble trying to get Storybook running in my nuxt project, I figured I give histoire a try.
But unfortunately I'm running in a lot of problems as well.
One of them is the <NuxtIcon /> is just not rendered at all, but working fine in the nuxt app.
Reproduction
https://github.com/lud-hu/nuxt-histoire-reproduction
System Info
System:
OS: macOS 14.0
CPU: (8) arm64 Apple M1
Memory: 68.38 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 18.19.0 - /opt/homebrew/opt/node@18/bin/node
Yarn: 1.22.19 - /opt/homebrew/bin/yarn
npm: 10.2.3 - /opt/homebrew/opt/node@18/bin/npm
pnpm: 8.15.1 - /opt/homebrew/bin/pnpm
Browsers:
Chrome: 121.0.6167.139
Edge: 121.0.2277.98
Safari: 17.0
npmPackages:
@histoire/plugin-nuxt: ^0.17.9 => 0.17.9
@histoire/plugin-vue: ^0.17.9 => 0.17.9
histoire: ^0.17.9 => 0.17.9
Used Package Manager
yarn
Validations
[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion.
[X] The provided reproduction is a minimal reproducible example of the bug.
Same here. I found two issues.
Problem 1: NuxtIcon is an async component, so Wrap NuxtIcon with Suspense.
Problem 2: NuxtIcon is accessing the vueApp.component that is stubbed out.
My workaround was to add a stub of the vueApp.component in the useNuxtApp composable stub of histoire. Or add guard code for vueApp.component access from NuxtIcon Side.
If we could override useNuxtApp stub, it would be nice for these problems
Thanks for the fix, @Akryum!
Do you publish new versions of histoire to npmjs regularly? The 0.17.11 that contains this fix is marked as a release here at github but not yet published to npmjs. Thx!
Thanks for the fix, @Akryum! Do you publish new versions of histoire to npmjs regularly? The 0.17.11 that contains this fix is marked as a release here at github but not yet published to npmjs. Thx!
It's published in "@histoire/plugin-vue": "^0.17.11".
My workaround was to add a stub of the vueApp.component in the useNuxtApp composable stub of histoire.
@positiveprogrammer Can you elaborate on how you did that?
You can find stub of composables in histoire/plugin-nuxt/runtime/composables.mjs
You could change the stub like the one below. Just skip the exception
export const useNuxtApp = () => ({ runWithContext: async (fn) => await fn(), vueApp: { components: [] } })
Hi all, thanks for the great lib.
But how was the issue described fix? How can NuxtIcon be used in stories? @positiveprogrammer as I understood, you have found the solution, correct?
@MaksymOsovitnii I found 2 issues; the first one was already fixed by the Histoire team, and the second issue is a little bit ambiguous since NuxtIcon tries to access vueApp to add NuxtIcon as a global component, but Histoire stub useNuxtApp composable, so NuxtIcon throw an exception.
You can take a look at nuxt-icon/dist/runtime/Icon.Vue
When you use nuxt-icon in your story, the highlighted code will throw an exception. So I proposed a workaround to add vueApp and composable in histoire stub manually.
@positiveprogrammer , thank you! Now it's clear to me.
MIght be releated: https://github.com/histoire-dev/histoire/issues/746
a potential hacky solution 👉 https://github.com/histoire-dev/histoire/discussions/773
| gharchive/issue | 2024-02-02T07:10:15 | 2025-04-01T06:38:57.108963 | {
"authors": [
"MaksymOsovitnii",
"awacode21",
"did",
"its-lewin",
"lud-hu",
"positiveprogrammer"
],
"repo": "histoire-dev/histoire",
"url": "https://github.com/histoire-dev/histoire/issues/668",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1677801343 | Dataset doesn't exist.
FileNotFoundError: Couldn't find a dataset script at
/content/JosephusCheung/GuanacoDataset/GuanacoDataset.py or any data file in the
same directory. Couldn't find 'JosephusCheung/GuanacoDataset' on the Hugging
Face Hub either: FileNotFoundError: Dataset 'JosephusCheung/GuanacoDataset'
doesn't exist on the Hub. If the repo is private or gated, make sure to log in
with `huggingface-cli login`.
We reproduced this problem by running the following script:
CUDA_VISIBLE_DEVICES=0 python src/finetune.py \
--do_train \
--dataset guanaco \
--finetuning_type lora \
--output_dir test \
--overwrite_cache \
--overwrite_output_dir \
--per_device_train_batch_size 4 \
--gradient_accumulation_steps 4 \
--lr_scheduler_type cosine \
--logging_steps 10 \
--save_steps 1000 \
--max_train_samples 10000 \
--learning_rate 1e-4 \
--num_train_epochs 1.0 \
--fp16
And everything seems good. Please check your internet connection, or log in with huggingface-cli login.
We strongly recommend logging in with your HuggingFace account since this dataset requires confirmation before using it.
| gharchive/issue | 2023-04-21T04:52:54 | 2025-04-01T06:38:57.148513 | {
"authors": [
"hiyouga",
"michaeloo0"
],
"repo": "hiyouga/ChatGLM-Efficient-Tuning",
"url": "https://github.com/hiyouga/ChatGLM-Efficient-Tuning/issues/18",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1815014397 | 请问全量调参为什么没有pytorch_model.bin
我用accelerate启动，deepspeed配置stage2
在checkpoint下面没有看到pytorch_model.bin文件，但看到adapter_model.bin文件。
推理的时候，是不是把adapter_model.bin修改成pytorch_model.bin
全量调参：把adapter_model.bin修改成pytorch_model.bin后，推理的结果很乱，不符合预期。
lora调参的效果就很好。
不知道 问题在哪？ 不能直接把adapter_model.bin修改成pytorch_model.bin?
现在全量微调肯定会生成 pytorch_model.bin，如果没有请更新代码
没更新代码，怎么使用，假如只有adapter_model.bin
| gharchive/issue | 2023-07-21T01:16:43 | 2025-04-01T06:38:57.150865 | {
"authors": [
"chenglu66",
"eight-corner",
"hiyouga"
],
"repo": "hiyouga/LLaMA-Efficient-Tuning",
"url": "https://github.com/hiyouga/LLaMA-Efficient-Tuning/issues/214",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2342711873 | 情感分类微调：测试输出出现大量positive和negative。
Reminder
[X] I have read the README and searched the existing issues.
System Info
linux
Reproduction
instruction = f'Judge whether the movie review is positive or negative.'
fine_tune_data = [{
'instruction': instruction,
'input': data['text'],
'output': 'positive' if data['label'] == 1 else 'negative'
} for data in train_data]
json.dump(fine_tune_data, open('LLaMA-Factory/data/imdb.json', 'w'), indent=2)
模型的输出有大量的negative和positive，并且lora合并之后，推理速度明显下降。
Expected behavior
仅输出一个positive或negative
Others
No response
llama3 非 instruct 模型请用 template: default 微调
感谢大佬！
请问你微调分类任务有改动默认参数吗，为什么我微调后测试的时候发现有些答案不固定呢
| gharchive/issue | 2024-06-10T02:38:59 | 2025-04-01T06:38:57.154005 | {
"authors": [
"hiyouga",
"nvliajia",
"un0o7"
],
"repo": "hiyouga/LLaMA-Factory",
"url": "https://github.com/hiyouga/LLaMA-Factory/issues/4183",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2254537345 | 🛑 Griffo is down
In fc6c093, Griffo (https://www.griffo.de) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Griffo is back up in 9d6ba3d after 9 minutes.
| gharchive/issue | 2024-04-20T12:47:24 | 2025-04-01T06:38:57.167314 | {
"authors": [
"hjstrauss"
],
"repo": "hjstrauss/MonitorMySites",
"url": "https://github.com/hjstrauss/MonitorMySites/issues/2060",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2593516460 | 🛑 Opa Hansi is down
In 599f96c, Opa Hansi (https://www.opahansi.de) was down:
HTTP code: 0
Response time: 0 ms
Resolved: Opa Hansi is back up in 42cadf0 after 10 minutes.
| gharchive/issue | 2024-10-17T03:36:43 | 2025-04-01T06:38:57.169783 | {
"authors": [
"hjstrauss"
],
"repo": "hjstrauss/MonitorMySites",
"url": "https://github.com/hjstrauss/MonitorMySites/issues/9292",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
268977490 | [用户管理]用户名长度限定
如果用户名比较长，例如ORPOM-USER2，界面上名字特别长且自动换行，导致user2落在下区，看不清也不太合理。
增加长度校验，最长8个字符。
| gharchive/issue | 2017-10-27T03:28:05 | 2025-04-01T06:38:57.170597 | {
"authors": [
"chenyork"
],
"repo": "hjyk/tbsui",
"url": "https://github.com/hjyk/tbsui/issues/5",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1381678217 | Update purenail mods
DarknessRandomizer: Fix a bunch of logic, UI overhaul for 4th lantern shard
MoreDoors: Inaugural beta release
SpoilerViewerMod: Fix bugs, integrate with MoreDoors
Did you want to bump the modlinks version number for Darkness?
Did you want to bump the modlinks version number for Darkness?
Yes, thanks.
| gharchive/pull-request | 2022-09-22T01:06:11 | 2025-04-01T06:38:57.172115 | {
"authors": [
"dplochcoder",
"flibber-hk"
],
"repo": "hk-modding/modlinks",
"url": "https://github.com/hk-modding/modlinks/pull/648",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
782697631 | [Feature Request]Scanned manga problem.
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. E.g. I'm always frustrated when [...]
I have a lots of scanned manga. it have 2page in one single image. So it need to be split into 2 page.
Describe the solution you'd like
A clear and concise description of what you want to happen.
The image ratio check and split. I think its best option.
Describe a small use-case for this feature request
How would you imagine this to be used? What would be the advantage of this for the users of the application?
Scanned manga have the issue like my case.
Additional context
Add any other context or screenshots about the feature request here.
Hi, thanks for the feature requests!
The image ratio check and split. I think its best option.
This might not work in some cases. Sometimes you get a few wide pages in a chapter (see the screenshot below), and if we do the ratio check and split, the wide pages would be wrongly split. I think the easiest solution for you would be to use the paged reader.
Hi, thanks for the feature requests!
The image ratio check and split. I think its best option.
This might not work in some cases. Sometimes you get a few wide pages in a chapter (see the screenshot below), and if we do the ratio check and split, the wide pages would be wrongly split. I think the easiest solution for you would be to use the paged reader.
As you can see this manga have perfect ratio. how can i split the manga?
As you can see this manga have perfect ratio. how can i split the manga?
What I was saying is that I agree it would be a useful feature, but I can't think of a user-friendly way to do this. If we just split all wide pages, some pages would be incorrectly split (as in my screenshot). We could add a double-page reading mode, where we split all pages regardless of their width/height ratios, but then the server would have to do the heavy image processing on the fly. I need to think about it and see what we can do, but of course, any suggestions are welcome.
In your screenshot, you are using the continuous mode. Perhaps you can give the paged mode a try as a workaround. The double-page images should look better in the paged mode.
What I was saying is that I agree it would be a useful feature, but I can't think of a user-friendly way to do this. If we just split all wide pages, some pages would be incorrectly split (as in my screenshot). We could add a double-page reading mode, where we split all pages regardless of their width/height ratios, but then the server would have to do the heavy image processing on the fly. I need to think about it and see what we can do, but of course, any suggestions are welcome.
In your screenshot, you are using the continuous mode. Perhaps you can give the paged mode a try as a workaround. The double-page images should look better in the paged mode.
Thanks for reply my submission. I really hope add the 2page mode in to the Mango. I will wait until get upgrade! TNX!
Thanks for reply my submission. I really hope add the 2page mode in to the Mango. I will wait until get upgrade! TNX!
| gharchive/issue | 2021-01-09T22:32:44 | 2025-04-01T06:38:57.180824 | {
"authors": [
"Dobob1022",
"hkalexling"
],
"repo": "hkalexling/Mango",
"url": "https://github.com/hkalexling/Mango/issues/140",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1236215469 | Support unzipped entry
Resolve #215
What I did
Change the Entry class to abstract class,
Implement DirectoryEntry, which treats unzipped images in a directory as an entry
the rule is described at here
Scan DirectoryEntry when Title#new and Title#examine are called.
Fix caching policy after some tests
Result and test
Here is an test library environment.
.:
info.json nested-folder/ 'THE iDOLM@STER Your Mess@ge 3rd stage.zip' 'THE iDOLM@STER Your Mess@ge 4th stage.zip' unzipped-files/
./nested-folder:
10.jpg 12.jpg 14.jpg 16.jpg 18.jpg 1.jpg 21.jpg 23.jpg 25.jpg 2.jpg 4.jpg 6.jpg 8.jpg info.json 'THE iDOLM@STER Your Mess@ge 1st stage.zip'
11.jpg 13.jpg 15.jpg 17.jpg 19.jpg 20.jpg 22.jpg 24.jpg 26.jpg 3.jpg 5.jpg 7.jpg 9.jpg nested-unziped-file/ 'THE iDOLM@STER Your Mess@ge 2nd stage.zip'
./nested-folder/nested-unziped-file:
10.jpg 11.jpg 12.jpg 13.jpg 14.jpg 15.jpg 16.jpg 17.jpg 18.jpg 19.jpg 1.jpg 20.jpg 21.jpg 22.jpg 23.jpg 24.jpg 25.jpg 26.jpg 2.jpg 3.jpg 4.jpg 5.jpg 6.jpg 7.jpg 8.jpg 9.jpg
./unzipped-files:
10.jpg 11.jpg 12.jpg 13.jpg 14.jpg 15.jpg 16.jpg 17.jpg 18.jpg 19.jpg 1.jpg 20.jpg 21.jpg 22.jpg 23.jpg 24.jpg 25.jpg 26.jpg 2.jpg 3.jpg 4.jpg 5.jpg 6.jpg 7.jpg 8.jpg 9.jpg
In tree view,
root (unzipped, have 4 entries, one title)
├ nested-folder (would be an entry and a title, have 3 entries)
│ ├ 1.jpg ~ 26.jpg
│ ├ nested-unziped-file (would be an entry)
│ │ └ 1.jpg ~ 26.jpg
│ ├ THE iDOLM@STER Your Mess@ge 1st stage.zip
│ └ THE iDOLM@STER Your Mess@ge 2nd stage.zip
├ unzipped-files (would be an entry)
│ └ 1.jpg ~ 26.jpg
├ THE iDOLM@STER Your Mess@ge 3rd stage.zip
└ THE iDOLM@STER Your Mess@ge 4th stage.zip
Result
The directories appeared as entries and titles
What I tested
remove an image file from directory
rename an image file in a directory
add new folder to scan
About class name
ZippedEntry -> ArchiveEntry
DirectoryEntry -> ?
I can't come up with good names...
I found that there's a bug after rename a directory entry and scan.
@tr7zw Hi!
you mean that the nested-folder in the sample would be a problem, and it shouldn't be treated as an entry because it has another titles and zipped entries though it has image files, right?
I think the responsibility of configuring a library is up to the library owners. If they don't want this, they would remove those files.
Huh I guess never mind? I still had in mind that if you have a folder "Manga" and in that folder a folder "One Piece" with the chapters inside, I think in the past it treated the "Manga" folder as something containing Chapters. But apparently this was already fixed, now it shows Titles/Entries.
Still a really neat pr, since using directories as chapters allows some more flexibility, and with the new abstract Entry class it could allow some nice new features(other compressed files than .zip, dynamically loading chapters from urls/network shares).
Thanks @Leeingnyo! I fixed the linter warnings and took a quick look, and it looks good overall! I think it's a nice application of abstract classes.
Re class names, yeah I think ArchiveEntry is more appropriate than ZippedEntry because we also support RAR/CBR files. I think DirectoryEntry looks fine. We could also use DirEntry to make it shorter but I have no strong feelings.
Also I think it makes more sense to break the classes into individual files, e.g., entry.cr, zipped_entry.cr, and directory_entry.cr. What do you think?
I will do a full review and some testings later this week :+1:
Hey @Leeingnyo sorry for the delay. I made quite some changes to the PR. Can you take a quick look when you have the time to make sure I didn't accidentally fuck up anything? Thanks!
@hkalexling sorry I pushed errors occurred version... wait for a moment
@hkalexling it looks great. I like the method that you did to recover entry instances :)
Since @page was added to Entry, it caused an error to recover old library.yml.zip file. But, I don't mind of this. fine!
Thanks @Leeingnyo! Sorry the comments above was just for my own reference and I accidentally published them ;-P
Since @page was added to Entry, it caused an error to recover old library.yml.zip file.
Could you elaborate a bit on this? I tried the following steps but didn't see the error.
Remove library.yml.gz
Build and run from the master branch to regenerate the library.yml.gz file
Build and run from this branch and there's no error
Oh that's the difference. I built it from the dev branch. but I had the same error when I tried from the master branch.
[ERROR] 2022/06/05 15:02:04 | Missing YAML attribute: path at line 14, column 7
because my ubuntu snap upgrades a Crystal implicitly, I use a Crystal 1.4.1... this would be a matter. :p
Ah sorry my bad. It does happen on master on Crystal 1.0.0 as well, but it's a minor issue and will only happen once so I think we are fine.
Thanks <3
| gharchive/pull-request | 2022-05-15T07:53:35 | 2025-04-01T06:38:57.194909 | {
"authors": [
"Leeingnyo",
"hkalexling",
"tr7zw"
],
"repo": "hkalexling/Mango",
"url": "https://github.com/hkalexling/Mango/pull/305",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1709048128 | [Feature] Interactive Kanban - Drag, Drop
The ability to drag and drop cards is a big deal for me; IMO it's the whole reason to Kanban!
Our upstream dependency react-kanban supports interactive boards[^1], but we'll have to add code that will modify the LogSeq graph according to actions taken by the user.
[^1]: though it should be acknowledged that the package is abandoned
I am attempting to implement this feature on my own, but I'd be happy for any tips or discussion here. I'll open a draft PR if I have any kind of progress so that other interested parties can collaborate on the feature.
I'm using the react-kanban demo as a guide.
I've made an initial attempt that matches the react-kanban demo but the event handler doesn't get triggered on drag. I've deleted the default logseq event handlers via the developer tools as a test but it had no effect.
The https://github.com/cannibalox/logtools project, when installed, enables showing a block as a set of kanban columns using CSS trickery. It has the added benefit of not requiring additional graph editing. It doesn't look as good, but it works.
I'd prefer to use this plugin but I think I'd need some help getting the modifications working. The current state of my attempt is here: https://github.com/isosphere/logseq-kanban-plugin/tree/drag-drop
second this
I suppose the plugin should have a disclaimer that you won't be able to move cards, which is mostly the point in having a kanban board itself.
For this function, you may like to use the logseq-plugin-kanban-board.
| gharchive/issue | 2023-05-14T19:26:17 | 2025-04-01T06:38:57.200100 | {
"authors": [
"hkgnp",
"isosphere",
"stan-voo"
],
"repo": "hkgnp/logseq-kanban-plugin",
"url": "https://github.com/hkgnp/logseq-kanban-plugin/issues/31",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1310725853 | Improve compatibility when sending codes in Python
For an example, the following function definition will break as an inpur to the REPL window;
def generate_messages(since, until):
def daterange(start_date, end_date):
for n in range(int((end_date - start_date).days)):
yield start_date + timedelta(n)
start_date = date(since)
end_date = date(until)
for single_date in daterange(start_date, end_date):
print(single_date.strftime("%Y-%m-%d"))
because the ipython kernel will regard the empty line as the end of the function definition, thus causing an error. But, simply deleting the new line is also a good idea, because the following code;
class NoInputFileError(Exception):
pass
class InputFileError(Exception):
pass
will break if you remove the line between class definitions.
So is there a way to improve compatibility when sending codes to the ipython kernel?
That's may be the IPython issue, so close it.
| gharchive/issue | 2022-07-20T09:18:18 | 2025-04-01T06:38:57.244869 | {
"authors": [
"tristone13th"
],
"repo": "hkupty/iron.nvim",
"url": "https://github.com/hkupty/iron.nvim/issues/277",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
725609992 | Scala lsp format on save
Hello!
What did you expect to happen?
For scala +lsp I would expect that format +onsave would pick the lsp format capability.
What actually happened?
It's using the CLI scalafmt tool.
If I do SPC c f it works as expected.
Additional details:
https://github.com/regadas/doom.d/
Thanks for this awesome project!
I just noticed this #4120 It might be related.
Yeah, that PR was meant to solve this issue.
Also, this may be a duplicate of #3626
#4120 was merged. Please update and let me know if that has resolved your issue.
Hi @hlissner that fixed it! Thanks
@systemctl603 Thanks as well for the PR!
| gharchive/issue | 2020-10-20T13:48:58 | 2025-04-01T06:38:57.256583 | {
"authors": [
"hlissner",
"regadas",
"systemctl603"
],
"repo": "hlissner/doom-emacs",
"url": "https://github.com/hlissner/doom-emacs/issues/4121",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
742671461 | Conflicting bindings
There are two elements with the same keybindings:
modules/editor/evil/config.el has
(map! :textobj "c" #'evilnc-inner-comment #'evilnc-outer-commenter)
and .local/straight/repos/evil-tex/evil-tex.el has
(define-key outer-map "c" 'evil-tex-a-command) and similar to inner.
So when working in TeX files, which one will be active is random. Sometimes visual-inner-c selects inside commands and sometimes inside comments (it is the same for the whole session, which one will be bound is defined when the buffer loads, but non-deterministically, so sometimes I get one and sometimes the other).
Since the tex one comes from a plugin, I would recommend changing the module one (comment) to capital c.
System information:
```
SYSTEM type darwin
config x86_64-apple-darwin18.7.0
shell /usr/local/bin/fish
uname Darwin 19.6.0 Darwin Kernel Version 19.6.0: Thu Oct 29 22:56:45 PDT 2020; root:xnu-6153.141.2.2~1/RELEASE_X86_64 x86_64
path (/usr/local/opt/openjdk/bin ~/.gem/ruby/2.6.0/bin ~/.npm-global/bin ~/.emacs.d/bin /usr/local/opt/qt/bin ~/.gocode/bin ~/Documents/MATLAB/mosek/tools/platform/osx64x86/bin ~/.cargo/bin ~/bin/flutter/bin ~/.config/yarn/global/node_modules/.bin ~/Library/Android/sdk/tools ~/Library/Android/sdk/platform-tools ~/bin/netbunch ~/bin /Library/TeX/texbin /Library/Frameworks/Mono.framework/Versions/Current/Commands /Applications/VMware Fusion.app/Contents/Public /Library/Apple/usr/bin /opt/X11/bin /usr/local/bin /usr/bin /usr/local/sbin /usr/sbin /sbin /bin /Applications/Emacs.app/Contents/MacOS/libexec /Applications/Emacs.app/Contents/MacOS/bin)
EMACS dir ~/.emacs.d/
version 27.1
build Aug 16, 2020
buildopts --with-mac --enable-mac-app=/Users/travis/build/railwaycat/homebrew-emacsmacport/build-scripts/emacs-source/tmproot --prefix=/Users/travis/build/railwaycat/homebrew-emacsmacport/build-scripts/emacs-source/tmproot --enable-mac-self-contained --with-modules
features NOTIFY KQUEUE ACL GNUTLS LIBXML2 ZLIB TOOLKIT_SCROLL_BARS MODULES THREADS JSON PDUMPER LCMS2 GMP
traits (batch server-running envvar-file)
DOOM dir ~/.doom.d/
version 2.0.9
build HEAD -> develop f7293fb67 2020-11-11 20:33:27 -0500
elc-files 0
modules (:completion company (ivy +icons +prescient) :ui doom doom-dashboard doom-quit fill-column hl-todo modeline neotree ophints (popup +defaults) tabs treemacs unicode vc-gutter vi-tilde-fringe window-select workspaces :editor (evil +everywhere) file-templates fold (format +onsave) multiple-cursors snippets word-wrap :emacs (dired +icons) electric (ibuffer +icons) undo vc :checkers syntax grammar :tools ein (eval +overlay) gist lookup lsp magit make pdf rgb tmux :os macos :lang (cc +lsp) (clojure +lsp) common-lisp (csharp +lsp +unity) data (dart +flutter +lsp) (elixir +lsp) (elm +lsp) emacs-lisp (erlang +lsp) (fsharp +lsp) (go +lsp) (haskell +dante +lsp) (json +lsp) (java +meghanada) (javascript +lsp) (julia +lsp) (kotlin +lsp) (latex +lsp +latexmk) (lua +lsp +moonscript) (markdown +grip) nim nix ocaml (org +dragndrop +journal +hugo +pretty) (python +lsp +cython +pyright) qt (ruby +lsp +rails) (rust +lsp) (scala +lsp) (sh +fish +lsp) (swift +lsp) web (yaml +lsp) :app calendar :config (default +bindings +smartparens))
packages ((tide) (vue-mode) (zig-mode) (alert) (lsp-julia :recipe (:host github :repo non-jedi/lsp-julia)) (julia-formatter :recipe (:host github :repo ki-chi/julia-formatter :files (julia-formatter.el scripts/server.el))))
unpin (n/a)
elpa (n/a)
```
Their code is already bound to mode keymaps. This has been bothering me for some time, but being random it is quite hard to pin down what is triggering it. I'll keep an eye open and see if I can find any pattern or anything that may help. You can close the issue if you want, I'll reopen it or fill a new one if I find out what is wrong.
| gharchive/issue | 2020-11-13T18:11:29 | 2025-04-01T06:38:57.260210 | {
"authors": [
"acristoffers"
],
"repo": "hlissner/doom-emacs",
"url": "https://github.com/hlissner/doom-emacs/issues/4265",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1871887439 | Sub-Header
Article Pages:
Mobile
Desktop
Search Results Page:
Mobile:
Desktop:
Originally posted by @amol-anand in https://github.com/hlxsites/accenture-newsroom/issues/2#issuecomment-1671255194
closing because duplicate
| gharchive/issue | 2023-08-29T15:11:51 | 2025-04-01T06:38:57.313349 | {
"authors": [
"amol-anand"
],
"repo": "hlxsites/accenture-newsroom",
"url": "https://github.com/hlxsites/accenture-newsroom/issues/20",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1918791887 | Family Pack
https://main--bitdefender--hlxsites.hlx.live/solutions/family-pack#overview
In the section Compare Bitdefender Products, the TS button redirects to the cart, instead of PP as IS.
authoring issues. Added the correct link to TS button.
| gharchive/issue | 2023-09-29T08:03:56 | 2025-04-01T06:38:57.314595 | {
"authors": [
"andreibogdan"
],
"repo": "hlxsites/bitdefender",
"url": "https://github.com/hlxsites/bitdefender/issues/372",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1811747434 | Firefox issue
When in Firefox, the nav fails to display.
It seems that the CSS pseudo-class has is not supported in FF: https://caniuse.com/css-has
| gharchive/issue | 2023-07-19T11:28:35 | 2025-04-01T06:38:57.315930 | {
"authors": [
"krizel4",
"solaris007"
],
"repo": "hlxsites/mammotome",
"url": "https://github.com/hlxsites/mammotome/issues/499",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1727726017 | Missing wave
Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix #420
Test URLs:
Before: https://main--moleculardevices--hlxsites.hlx.page/en/assets/tutorials-videos/br/automated-plate-loading
After: https://missing-wave--moleculardevices--hlxsites.hlx.page/en/assets/tutorials-videos/br/automated-plate-loading
AND
Before: https://main--moleculardevices--hlxsites.hlx.page/en/assets/tutorials-videos/br/how-to-set-up-elisa-assay-and-basic-analysis-using-softmax-pro
After: https://missing-wave--moleculardevices--hlxsites.hlx.page/en/assets/tutorials-videos/br/how-to-set-up-elisa-assay-and-basic-analysis-using-softmax-pro
AND
Before: https://main--moleculardevices--hlxsites.hlx.page/resources/citations/axon
After: https://missing-wave--moleculardevices--hlxsites.hlx.page/resources/citations/axon
Note: I added also 2 additional styles for videos-and-webinars theme to make sure there is some space between hero and some space to wave
| gharchive/pull-request | 2023-05-26T14:19:36 | 2025-04-01T06:38:57.320937 | {
"authors": [
"lydiapuric"
],
"repo": "hlxsites/moleculardevices",
"url": "https://github.com/hlxsites/moleculardevices/pull/445",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
439125059 | Validate NOT and OR syntax on Definition store to allow user to import definition file
https://tools.hmcts.net/jira/browse/RDM-4635
Include validation in definition store to allow definition (excel) file with NOT and OR show condition syntax
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ X] No
Added tests.
| gharchive/pull-request | 2019-05-01T10:33:19 | 2025-04-01T06:38:57.420273 | {
"authors": [
"ganganna-peddapothu"
],
"repo": "hmcts/ccd-definition-store-api",
"url": "https://github.com/hmcts/ccd-definition-store-api/pull/393",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2176111545 | CIV-12777 Part Admit Claimant Dashboard
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-12777
Change description
Added:
Handler for claimant response (claimant)
Script for Part admit Accepted claimant response
Method to return ordinal formatted date
Unit and integration test
Modified:
I have extracted the utils ClaimantResponseUtils.java
from civil/service/docmosis/utils to civil/utils because it is generally used. Consequently some imports have been modified
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ x ] No
Open for review before the end of the sprint
Open to get reviews
| gharchive/pull-request | 2024-03-08T14:05:45 | 2025-04-01T06:38:57.426321 | {
"authors": [
"miguelMolina3691"
],
"repo": "hmcts/civil-service",
"url": "https://github.com/hmcts/civil-service/pull/4178",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2691069767 | Updating Postgres checks, attempting to use pipeline variables to send messages to threads with each loops in pipeline
Change description
Updating Postgres checks
Attempting to use pipeline variables to send messages to threads with each loops in pipeline.
The first loop sets the header, subsequent loops should send to the thread of the same header
example thread:
| gharchive/pull-request | 2024-11-25T15:00:11 | 2025-04-01T06:38:57.441963 | {
"authors": [
"MartyFox"
],
"repo": "hmcts/dtspo-daily-monitoring",
"url": "https://github.com/hmcts/dtspo-daily-monitoring/pull/95",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2761185479 | [ALS-7200]
Switch to async upload
Allows for 5G+ uploads to S3
async not needed.
| gharchive/pull-request | 2024-12-27T18:56:59 | 2025-04-01T06:38:57.483863 | {
"authors": [
"Luke-Sikina"
],
"repo": "hms-dbmi/pic-sure-services",
"url": "https://github.com/hms-dbmi/pic-sure-services/pull/46",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1438855313 | Update scala3-library to 3.2.1
Updates org.scala-lang:scala3-library from 3.2.0 to 3.2.1.
GitHub Release Notes - Version Diff - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!
Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala3-library" } ]
Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
pullRequests = { frequency = "@monthly" },
dependency = { groupId = "org.scala-lang", artifactId = "scala3-library" }
}]
labels: library-update, early-semver-patch, semver-spec-patch, commit-count:n:2
Superseded by #56.
| gharchive/pull-request | 2022-11-07T19:20:20 | 2025-04-01T06:38:57.487930 | {
"authors": [
"hnaderi"
],
"repo": "hnaderi/lepus",
"url": "https://github.com/hnaderi/lepus/pull/38",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
633593613 | Intern Selection Process
We should start with the grouping so we can know who and who are working together
Please what's supposed to go on here?
What I would mention here is that the leaders of the group should give room for at least 50% newbies to learn from the experienced.
hi, what is the selection process?, what anbout mobile development beginners?, or any beginner?
There should be a mode for selection
Check the slack channel the selection process is already stated there
Really?
| gharchive/issue | 2020-06-07T17:20:49 | 2025-04-01T06:38:57.490249 | {
"authors": [
"Idadelveloper",
"Idss15",
"Oluwatobiloba98",
"Technelly",
"adekniyi",
"dnor-dev"
],
"repo": "hng-teamfury/stage2",
"url": "https://github.com/hng-teamfury/stage2/issues/6",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2421363973 | Squeeze page
Contributions
Description
Developed the API endpoint for the Squeeze Page to handle POST requests, collect user information, and send an email template to the user.
Endpoints
Created Endpoint: POST /api/v1/squeeze
Type of Change
[x] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
Implementation Details
Created Endpoint: Implemented the POST /api/v1/squeeze endpoint to handle form submissions.
Data Validation: Added validation for incoming data to ensure required fields are provided and the email format is correct.
Response Handling: Implemented appropriate responses for both success and error scenarios:
Success Response:{
"message": "Your request has been received. You will get a template shortly."
}
Error Response:{
"message": "Failed to submit your request",
"status_code": 400
}
Database Storage: Saved user information securely in the database.
Testing
Unit Tests: Written unit tests for backend validation and data handling.
Testing Scenarios: Tested various scenarios for form submissions including successful, invalid data, and server errors.
Challenges and Issues
Database Table Issue:
Problem: The database table provided by the DB maintainers lacked an email field when I forked and cloned the repo.
Solution: Updated the table and migrations on my separate branch to include the necessary email field.
Note: This issue should be addressed and noted during testing.
Email Template Sending Bottleneck:
Problem: The task required sending email templates to the user's email address, but emails could not be sent immediately after the POST request. This necessitated asynchronous processing.
Solution: Utilized Laravel's job queue system to handle email sending asynchronously. However, the existing jobs table in the database was already configured for different purposes, such as job type, job name, and organization details.
Issue: The email functionality does not work due to the jobs table configuration conflicting with the intended use for email queue processing.
Checklist
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
You have merge conflicts and it doesn't link to your issue
You have merge conflicts and it doesn't link to your issue
I did not even touch that, maybe it's because i did not pull before pushing
I worked on my create branch all through
| gharchive/pull-request | 2024-07-21T11:47:11 | 2025-04-01T06:38:57.503117 | {
"authors": [
"NgBlaze",
"Ruthiejayjay"
],
"repo": "hngprojects/hng_boilerplate_php_laravel_web",
"url": "https://github.com/hngprojects/hng_boilerplate_php_laravel_web/pull/67",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
529594309 | Admin UI sometimes won't save Scenario step edits
Not really sure how to reporduce at this time, the behavior seems to be that after some time of using the UI to edit scenario steps, it stops saving them. The green confirmation message won't show up after you click save and when you go back to the scenario later the changes are missing
How long of time are we talking? The JWT token expires after a day.
Check the response to the PUT requests in the network tab of your browser; like so:
in the span of 10s of minutes, definitely not a day
Its also intermittent, some moments later the save action will work again
I haven't been able to reproduce this behavior. Can you post some more details about which versions of gargantua and admin-ui you're using and the environment in which you installed the app? Also post the HTTP response to a failed request and/or the corresponding logs when the edit fails to save.
after further debugging, I suspect it might be because of latin charset in my scenario steps...specifically curly quotes vs straight. The error messages can be seen on the JS console, but the UI doesn't report the error, just silently fails.
Closing in favor of #25
| gharchive/issue | 2019-11-27T22:11:11 | 2025-04-01T06:38:57.509325 | {
"authors": [
"ebauman",
"hall",
"wjimenez5271"
],
"repo": "hobbyfarm/admin-ui",
"url": "https://github.com/hobbyfarm/admin-ui/issues/24",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
274691554 | Add log and env_log packages, resolves #20
Description
This PR introduces the log and env_logger packages to handle logging for the source code. These packages adds several useful macros such as info!, debug!, err! etc which can be used for logging of different kinds. To view the logs one must run test or the main program with the RUST_LOG flag set to the appropriate level, for instance RUST_LOG=gemini=info cargo run.
Alternate Designs
N/A
Benefits
Allows logging for debug etc without disturbing the user.
Possible Drawbacks
N/A
Applicable Issues
#20
Codecov Report
Merging #21 into master will decrease coverage by 3.08%.
The diff coverage is 50%.
@@ Coverage Diff @@
## master #21 +/- ##
==========================================
- Coverage 98.87% 95.78% -3.09%
==========================================
Files 3 3
Lines 89 95 +6
==========================================
+ Hits 88 91 +3
- Misses 1 4 +3
Impacted Files
Coverage Δ
src/main.rs
100% <ø> (ø)
:arrow_up:
src/resources.rs
100% <100%> (ø)
:arrow_up:
src/generators/names.rs
94.66% <40%> (-3.91%)
:arrow_down:
Continue to review full report at Codecov.
Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 29f1ec8...14af326. Read the comment docs.
| gharchive/pull-request | 2017-11-16T22:48:43 | 2025-04-01T06:38:57.571094 | {
"authors": [
"codecov-io",
"holmgr"
],
"repo": "holmgr/gemini",
"url": "https://github.com/holmgr/gemini/pull/21",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1754530146 | HoloViz Roadmap 2023
This issue is meant to be commented by the HoloViz contributors, maintainers and steering committee members.
In order to define the HoloViz roadmap for the next 6-12 months we would like to collect what would be your personal roadmap, i.e. what you think should be the most important goals for HoloViz and what you would like to work on?
Please insert only 1 comment (edit it later if you need to) before the 3rd of July 2023.
No matter which website or repo a user has landed on, guide them quickly and easily to the right tool for their job, i.e. the right library and the right API for that library.
Will be discussed July 3rd
Put HoloViz more to the front: making it clear on each project website that they are part of HoloViz, linking more to holoviz.org, improving the holoviz.org story of what can be done with the intersection of the HoloViz packages (panel+hvplot/geo/holoviews+datashader(+bokeh)), improving the interoperability between the HoloViz packages (aka viz dashboards made easy).
Following the work on Panel, keeping on improving the docs by completing Panel's work (API docs) and proceeding to hvPlot's overhaul
On a personal level, I'd like to spend a lot more time maintaining hvPlot (which fits with 1. and 2.)
Improve the structure of Panel's technical reference material (primarily the API reference and component gallery sections-#4305)
Improve guidance on tool selection as part of the getting started experience on HoloViz.org (#351)
Reduce energy barriers to first-time contributions. For instance, improving/coordinating contributor guides or getting the complete docs build time down to seconds. IMO, dramatically prioritizing this point would benefit all aspects of HoloViz.
Start applying the Panel docs format to hvPlot and HoloViews
Datashader:
Complete the matrix of support for all Reduction classes and as many of the following as make sense: work on GPU, work using Dask, antialiasing, contained within a by reduction, contained within a where reduction. Ref https://datashader.org/api.html#reductions
Simplify the Reduction code which currently has many very similar functions in append and combine functions. This should reduce the code complexity and the number of numba functions. May be able to cache the numba functions.
Improve the documentation is line with recent changes to Panel, in particular by adding smaller How To Guides for specific tasks.
HoloViews:
Code: Keep on improving the code. I would like to look at the code in-depth and make plans to remove some part that is not tested or is no longer used.
Test: Update the test to use pytest with fixtures, not unittest.TestCase.
Test: Support running the tests in random order so it is possible to parallelize the tests.
Test: To improve or at least better understand how to change the plotting backend in the test suite. It could be related to the previous point.
Type hints: Begin adding type hints to HoloViews.
DEV: Update development infrastructure to use Hatch. I want to begin this transition as soon as possible.
DEV: Look into CI's build, docs, and tests concerning the warnings emitted but often ignored.
So, in general, improvements behind the scene.
I have been following HoloViz and its component libraries for several years and was originally drawn back to use it, specifically because of the Panel Tabulator component.
I need a FREE OSS highly-functional, high-performance Python-interactive table widget for Pandas to replace QGrid. I liked Qgrid because it was highly functional, fast & big data scalable for 1M+ rows, preserved state after user interaction, was fully addressable as a Python object and many other features (sort columns, filters, groupby and many other Pandas). Qgrid code ran in Flask, Jupyter Notebook and Django and other Python full-stack web frameworks. QGrid was developed by Quantopian on top of SlickGrid. However, Quantopian ran out of money and closed down; eventually Quantopian followers gave up maintaining Qgrid. The R community has had HTMLtable for many years, offering high-quality, high-functionality table widgets "that just work".
Aggrid is a popular proprietary commercial alternative to Qgrid that is being heavily promoted by Streamlit (now a Snowflake property). Streamlit is freemium software. Aggrid is expensive (Starting at...$$$999 Per Developer). Aggrid is still not very mature v0. for the open-source version. Aggrid is a Javascript / Angular framework, very functional. Many features have not been surfaced to Python. The most important Aggrid features (row selection, groupby, and others) are locked to monthly or enterprise subscriptions. The Streamlit community promotes Aggrid heavily through YouTube demos.
You can see more about the JavaScript hacks required to add free functionality to aggrid here: Streamlit Ag-Grid
"Since AgGrid is a JavaScript-based grid, the background properties of columns or cells can be changed by adding JavaScript code to the Python code. I am adding the JsCode library to be able to use JS code in the Grid."
If Panel Tabulator offers a FOSS full-function alternative to Aggrid, it will lead to much greater adoption of the rest of Holoviz.
My vote is to focus on enhancing Tabulator to be a good strong FREE alternative ("competitor") to aggrid, and get fully functional as a simple-to-use component in Jupyter Notebook, Flask, Django and other tools.
With demos like PyGWalker from Kanaries. PyGWalker is pretty cool. Tabulator with other Holoviz widgets could equal or surpass PyGWalker.
I am willing to help with applications of Tabulator, but we have to get it wrapped into a Streamlit component to jump on the Streamlit bandwagon. I found a Chinese port of Streamlit Component wrapper for Tabulator but it does not work completely. I will post a link to it as soon as I re-find it.
For me the most important is removing the friction of getting started with Panel, hvPlot, param, HoloViews, ... in that order.
It is primarily about improving
Documentation
Fixing bugs
Support on Discourse and Discord
Communication on social media.
Speed/ Performance
| gharchive/issue | 2023-06-13T10:12:09 | 2025-04-01T06:38:57.597527 | {
"authors": [
"Hoxbro",
"MarcSkovMadsen",
"droumis",
"ianthomas23",
"jbednar",
"maximlt",
"richlysakowski"
],
"repo": "holoviz/holoviz",
"url": "https://github.com/holoviz/holoviz/issues/366",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
1727992227 | Grouped/dodged bar charts not working as documented
ALL software version info
MacOS Big Sur, M1
Python 3.10.10
JupyterLab v3.5.2
hvplot 0.8.3
bokeh 3.1.1
Description of expected behavior and the observed behavior
I'm trying to make a dodged bar chart like the one in https://hvplot.holoviz.org/reference/pandas/bar.html#basic-bar-plots but the output is always stacked, never dodged
Complete, minimal, self-contained example code that reproduces the issue
I just downloaded this notebook https://hvplot.holoviz.org/reference/pandas/bar.html#basic-bar-plots and did run-all:
No errors in the console.
Indeed, seems to be a regression in Bokeh 3.x. See also https://github.com/holoviz/holoviews/issues/5726
| gharchive/issue | 2023-05-26T17:28:42 | 2025-04-01T06:38:57.601551 | {
"authors": [
"nicolaskruchten",
"philippjfr"
],
"repo": "holoviz/hvplot",
"url": "https://github.com/holoviz/hvplot/issues/1072",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
2074554277 | Unknown state
Hi there,
I've also discovered that my BEKO B5WFU78435WB (7002340002) it has one new task that HomeWhiz doesn't not recognize. Right now the washing machine is "washing" but Home Assistant shows "unknown" task
How can I get the "tasks" from HomeWhiz phone app and see what's wrong?
Hi 👋,
could you share some debug logs?
Thanks!
Hi there,
Yes, here we go: homewhizz.log
Pretty much something isn't right in my washer_substate too. I've got washer-dryer and old versions of your Addon worked fine (before the breaking change).
Version 0.6 randomly was changing washer_substate but mainly stayed in "remove the laundry".
The latest version is constantly stuck on "washing finished, remove laundry" while all other options and sensors are flawless. See the screenshot
F999 9226 1840 7970 4793 37
It works correctly if I unplug the washing machine from the mains and plug it in again. For the following washing then the substate is reported fine, another washing after this fine and then after a day I do another washing and the substate is always "remove laundry".
I haven't used the app for a year and I am unable to test if the app reads the same status as.. For some reasons the app doesn't let you see the progress of washing unless you chose "download program". It used to do it before, I'm sure.
@cnecrea I decoded all the messages from your logs.
State: None
Substate: None
State: program_wool_handwash
Substate: None
State: program_mix
Substate: None
State: program_mix
Substate: None
State: program_drum_clean
Substate: None
State: program_drum_clean
Substate: washer_substate_program_started
State: program_drum_clean
Substate: washer_substate_program_started
State: program_drum_clean
Substate: washer_substate_washing
State: program_drum_clean
Substate: washer_substate_washing
State: program_drum_clean
Substate: washer_substate_washing
State: program_drum_clean
Substate: washer_substate_prewash
State: program_drum_clean
Substate: washer_substate_prewash
State: program_drum_clean
Substate: washer_substate_prewash
State: program_drum_clean
Substate: washer_substate_prewash
State: program_drum_clean
Substate: None
State: program_drum_clean
Substate: None
State: program_drum_clean
Substate: None
State: program_drum_clean
Substate: None
State: program_drum_clean
Substate: None
State: program_drum_clean
Substate: washer_substate_paused
State: program_delicates
Substate: None
State: program_wool_handwash
Substate: None
State: program_eco_40_60
Substate: None
State: program_cottons
Substate: None
State: None
Substate: None
The only "None" states, which should translate to unknown in Home assistant, are at the beginning and at the end. And those should be, according to the app, washing?
I'll close this issue for now as there haven't been any updates in some time.
| gharchive/issue | 2024-01-10T14:56:48 | 2025-04-01T06:38:57.618812 | {
"authors": [
"Mikescotland",
"TechHummel",
"cnecrea"
],
"repo": "home-assistant-HomeWhiz/home-assistant-HomeWhiz",
"url": "https://github.com/home-assistant-HomeWhiz/home-assistant-HomeWhiz/issues/185",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
822792199 | Switch order of ValueNotification and Value update so that the notification includes the latest value
In #154 the order of operations for creating the ValueNotification was wrong and led to the value that came in the notification being returned as the value that we was previously in the state (see https://github.com/home-assistant/core/issues/47432). This fixes the order of operations.
I could use some help writing some good test cases for this one, I don't think we have enough given all the issues that have occurred as we try to fix this
@kpine can you take a look at this and see if it makes sense since you spotted this immediately?
I was wondering, why is value modified at all? Isn't it needed just to get the metadata? These notifications are supposed to be events or stateless values, not value updates.
To test this I'd create a Value instance on the node and then create an event coming in with new data. The ValueNotification data should then be created with the Value instance data as base but be updated with the new data from the event. So we need to make sure that we can assert that difference when creating the initial Value and event data
I was wondering, why is value modified at all? Isn't it needed just to get the metadata? These notifications are supposed to be events or stateless values, not value updates.
Yes, it doesn't sound like the Value state should be updated when reading the docs about ValueNotification event:
https://zwave-js.github.io/node-zwave-js/#/api/node?id=quotvalue-notificationquot
Is there any pre-existing method to do this?
value_notification.update(value.metadata)
I imagine value.metadata doesn't exist yet...
ah, perhaps it does...
so maybe this value_notification.metadata.update(value.metadata)
value_notification.metadata.update(value.metadata.data)
Just tested on my prod setup, this works, and resolves https://github.com/home-assistant/core/issues/47432
value_notification.metadata.update(value.metadata.data)
To test this I'd create a Value instance on the node and then create an event coming in with new data, that should trigger a ValueNotification event. The ValueNotification data should then be created with the Value instance data as base but be updated with the new data from the event. So we need to make sure that we can assert that difference when creating the initial Value and event data
So it looks like my tests are missing a value in the args part of the value notification event, and I don't test the value explicitly. If I were to add it with a different value from the Values value, and then check it, would that be sufficient?
To test this I'd create a Value instance on the node and then create an event coming in with new data, that should trigger a ValueNotification event. The ValueNotification data should then be created with the Value instance data as base but be updated with the new data from the event. So we need to make sure that we can assert that difference when creating the initial Value and event data
So it looks like my tests are missing a value in the args part of the value notification event, and I don't test the value explicitly. If I were to add it with a different value from the Values value, and then check it, would that be sufficient?
actually, the Value in my test data doesn't even have a value, so if I add a value to the notification, we can guarantee it's coming from the notification event if the ValueNotification has a value
value_notification.metadata.update(value.metadata.data)
The problem with this approach is that ValueNotification.endpoint is None. There are two ways to solve this:
Update the entire value_notification.data. This may have unintended side effects but not sure.
Update the endpoint property to return 0 by default. I think this is safe because every value has to be on an endpoint, doesn't it?
I think the endpoint is not included from the ValueNotification, so the endpoint shouldn't be included in the HA event?
I think the endpoint is not included from the ValueNotification, so the endpoint shouldn't be included in the HA event?
The notification is for a value that does have an endpoint. There's a third option, see my upcoming commit
Looks good!
FYI, my scene activation and basic set events do include endpoint from the server.
| gharchive/pull-request | 2021-03-05T06:31:35 | 2025-04-01T06:38:57.636267 | {
"authors": [
"MartinHjelmare",
"jcam",
"kpine",
"raman325"
],
"repo": "home-assistant-libs/zwave-js-server-python",
"url": "https://github.com/home-assistant-libs/zwave-js-server-python/pull/156",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
269067873 | Adding support for deployment_key for git_pull addon
The main idea is to allow the user to provide a private key which will be used typically as "deployment_key".
The json will be something like:
{ (...)
"deployment_key": [
"-----BEGIN RSA PRIVATE KEY-----",
"MIIEpAIBAAKCAQEArNTRDaU1nQ/Fcb5VttyxTuEEpf+W3tNe6QMVswAXAirDh4Do",
"WTC1/IFae89jId5FckmFOszskAqoCLjI6ZrnxP3ZLW7yVsDn7TkI0iR21DdJ/fSU",
(...)
"-----END RSA PRIVATE KEY-----"
],
"deployment_key_protocol": "rsa"
}
The multiline is a bit messy, but seems the more comfortable way to make copy&paste. The alternative is to add \n for each line and remove the lines and the json becomes unreadable.
Note that deployment_key_protocol is optional and defaults to rsa. The idea is to allow the user to allow any of the typically supported ssh protocols for identities, which are:
dsa
ecdsa
ed25519
rsa
I don't consider the ~/.ssh/identity, which appears in the man pages, but I have never seen it nowadays. I assume most people will do ssh-keygen and just forget about the protocol (rsa seems to be the default in all the ssh packages I have ever used). All the aforementioned protocols are suffix to ~/.ssh/id_<suffix> so that is simply used as the file name.
If this PR sounds good, I am ready to add the documentation for it.
We can also use /share/keys if you think that make more sense and add a options to set the name, like we use on google_assistant or snips?
I didn't like the idea to require Samba in order to use that. Because that is the only method I have seen that can be used in order to upload a file like a key. But if you think is better I can change.
The deployment key doesn't change (typically is set and forgotten) so a bit messy initial setting may not be so bad.
For me, it dosn't matter. It should be user friendly as it is possible. So if you prefere this, it is okay.
You can also use scp/sftp with ssh add-on to access to share. If you know a nice webinterface for data handling (like file station from synology) we can add it as add-on.
Anyway, you are free to handle that as file or as options. For me is both okay :+1:
Do we neef also the openssh client?
I think that the current workaround for multiline-private-key-into-config-json is good enough. It should be enough for my scenario, and I assume that it will be a common case for people having private repos somewhere (either cloud or "in premises").
Last two commits should address your comments.
Please update also the website
"repository": "match((?:git|ssh|https?|git@[-\\w.]+):(\/\/)?(.*?)(\\.git)(\/?|\\#[-\\d\\w._]+?))",
This needs to improve, because some of us aren't using github, for instance mine is gitlab@git.domain.com:group/repo.git
I'd suggest a regexp which can match anything word before @.
@jonkristian I think that you meant to comment on home-assistant/hassio-addons#198
Because that line that you are quoting is from that PR, not this one. I was very confused at first...
@alexbarcelo So sorry about the confusion. Should I move my comment?
| gharchive/pull-request | 2017-10-27T10:58:35 | 2025-04-01T06:38:58.017586 | {
"authors": [
"alexbarcelo",
"jonkristian",
"pvizeli"
],
"repo": "home-assistant/hassio-addons",
"url": "https://github.com/home-assistant/hassio-addons/pull/196",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
261209404 | Fix typo: BUILT_TYPE -> BUILD_TYPE
Sidenote: have issues been disabled intentionally for this repo?
I build a new release in 10min
| gharchive/pull-request | 2017-09-28T06:44:50 | 2025-04-01T06:38:58.019056 | {
"authors": [
"pschmitt",
"pvizeli"
],
"repo": "home-assistant/hassio-build",
"url": "https://github.com/home-assistant/hassio-build/pull/37",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
532338231 | Alert window doesn't has correct title or button
When the frontend uses the JavaScript alert(), it shows an alert to the user with the wrong title and a missing caption for the OK button (button does work).
@gmatyszczak does this also fix the %s or should I open a new issue for that?
I couldn't reproduce the issue with %s. Could you provide steps? Or retest it on your side?
Cannot reproduce either anymore. Perfect !
| gharchive/issue | 2019-12-03T23:31:44 | 2025-04-01T06:38:58.021086 | {
"authors": [
"balloob",
"gmatyszczak"
],
"repo": "home-assistant/home-assistant-android",
"url": "https://github.com/home-assistant/home-assistant-android/issues/90",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
309690484 | Cast groups unavailable
Home Assistant release with the issue:
0.66.0.beta1
Last working Home Assistant release (if known):
0.65.6
Operating environment (Hass.io/Docker/Windows/etc.):
Raspbian GNU/Linux 9 (stretch)
Component/platform:
media_player.cast
Description of problem:
Since update to the latest beta version, my cast groups are unavailable now and then. However, the single devices of the groups can be controlled, but not the groups itself. I encountered this issues typically in the morning. When restarting HASS, all cast devices and groups are available, again.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
discovery:
media_player:
- platform: cast
Traceback (if applicable):
Additional information:
Hmmm, thanks for reporting this 👍
Seems a lot like https://github.com/home-assistant/home-assistant/issues/13483 and probably due to the groups changing their "elected leader". Could you also enable debug logs as mentioned in the comment in there? It would really help.
Maybe back to the original elected leader? :)
Hmmm, that might be it, but I have not idea how that could affect the socket client. Oh gosh, this is getting interesting... 😂
@dshokouhi The problem is that not only the host (or IP address) of the device that is the "elected leader" or the device that accepts all commands changes, but also the port number. And that dynamically, so there's no way that a user can list the cast members in their configuration.
btw, from what I know now, the issue is not related to the discovery aspect of the cast integration. In fact, we discover elected leader changes just fine. The issue seems to be somewhere in the disconnect from old leader + connect to new leader code.
Oh wow nice to hear you guys seem to have pinned down the issue :) if you need any help testing I am sure myself and others would be glad to help.
I'm still trying to find out what exactly caused this, but If you'd like to help 😬, it would be good to know whether with the following configuration the issue still happens (with discovery: disabled).
media_player:
- platform: cast
scan_interval: 1234567890
I personally am not seeing the issue with my setup with that config, but it would be good to get some data from others too. This configuration should not really affect anything and the cast integration should still work (without the new semi-polling mode I introduced in the linked PR). If the error doesn't appear with that configuration, it would mean that we know the code change that caused this, but I still have no idea why the connections drop.
Ok I have disabled discovery for google_cast, and applied the same config for the media_player component. Will reply back if I notice the issue.
@OttoWinter the issue came back overnight, one of my groups is currently unavailable and the other one went unavailable over night and became available again.
@dshokouhi Ok. At least that rules out one possible explanation... Thanks very much!
I'd be happy to help test as well if there's are any new updates,
I just closed my issue after troubleshooting and determining that cast groups are causing my problems, and that this issue probably relates to mine.
If I include cast groups in global or cast discovery, then I lose the ability to cast to all but a few of my cast-enabled devices when Home Assistant starts up. If I explicitly define just the individual devices and exclude cast groups, then everything works fine. As a point of clarification, when I say "lose the ability to cast", I mean that when I hit the cast icon in Pandora, Spotify, or Google Play Music, I only get the devices with very old firmwares as options (Sony Speaker with Chromecast Built-In and an Insignia Alarm Clock with Chromecast Built-in). None of the Chromecast Audios, Google Homes, Nvidia Shields, nor any of the associated groups show up.
I've attached a log.
home-assistant test2.log
I'm also seeing this behaviour today, running Home Assistant 0.67.1:
The more-info dialog shows the details of the bottom group, but the state of the top group is identical. I also have the individual Chromecast Audio units in my Home Assistant setup and it seems one of them (Garoeda I) was unavailable for about half a minute. This caused the two groups (that include that specific Chromecast Audio) to become and remain unavailable.
This is what syslog logged on my Raspberry Pi 3:
pi@Ra:~ $ cat /var/log/syslog | grep unavailable
Apr 22 17:13:41 Ra hass[13460]: #033[32m2018-04-22 17:13:41 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.garoeda_i, old_state=<state media_player.garoeda_i=off; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-22T04:38:21.736327+02:00>, new_state=<state media_player.garoeda_i=unavailable; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-22T17:13:41.211439+02:00>>#033[0m
Apr 22 17:13:42 Ra hass[13460]: #033[32m2018-04-22 17:13:42 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio, old_state=<state media_player.home_audio=off; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T04:38:21.754878+02:00>, new_state=<state media_player.home_audio=unavailable; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T17:13:42.196000+02:00>>#033[0m
Apr 22 17:13:47 Ra hass[13460]: #033[32m2018-04-22 17:13:47 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio_with_bathroom, old_state=<state media_player.home_audio_with_bathroom=unavailable; friendly_name=Home Audio with bathroom, supported_features=21437 @ 2018-04-22T15:47:52.989243+02:00>, new_state=<state media_player.home_audio_with_bathroom=off; friendly_name=Home Audio with bathroom, supported_features=21437 @ 2018-04-22T17:13:47.477800+02:00>>#033[0m
Apr 22 17:13:47 Ra hass[13460]: #033[32m2018-04-22 17:13:47 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio, old_state=<state media_player.home_audio=unavailable; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T17:13:42.196000+02:00>, new_state=<state media_player.home_audio=off; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T17:13:47.500569+02:00>>#033[0m
Apr 22 17:14:16 Ra hass[13460]: #033[32m2018-04-22 17:14:16 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.garoeda_i, old_state=<state media_player.garoeda_i=unavailable; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-22T17:13:41.211439+02:00>, new_state=<state media_player.garoeda_i=off; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-22T17:14:16.308174+02:00>>#033[0m
Apr 22 17:14:16 Ra hass[13460]: #033[32m2018-04-22 17:14:16 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio_with_bathroom, old_state=<state media_player.home_audio_with_bathroom=off; friendly_name=Home Audio with bathroom, supported_features=21437 @ 2018-04-22T17:13:47.477800+02:00>, new_state=<state media_player.home_audio_with_bathroom=unavailable; friendly_name=Home Audio with bathroom, supported_features=21437 @ 2018-04-22T17:14:16.640050+02:00>>#033[0m
Apr 22 17:14:16 Ra hass[13460]: #033[32m2018-04-22 17:14:16 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio, old_state=<state media_player.home_audio=off; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T17:13:47.500569+02:00>, new_state=<state media_player.home_audio=unavailable; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T17:14:16.659293+02:00>>#033[0m
And this is what happened according to Home Assistant:
2018-04-22 17:13:41 WARNING (Thread-6) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-04-22 17:13:42 WARNING (Thread-8) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-04-22 17:13:51 ERROR (Thread-10) [pychromecast.socket_client] Failed to connect. No retries.
2018-04-22 17:14:11 ERROR (Thread-6) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-04-22 17:14:12 ERROR (Thread-8) [pychromecast.socket_client] Failed to connect: timed out. aborting due to stop signal.
2018-04-22 17:14:16 ERROR (Thread-11) [pychromecast.socket_client] Error reading from socket.
2018-04-22 17:14:16 ERROR (Thread-12) [pychromecast.socket_client] Error reading from socket.
2018-04-22 17:14:16 WARNING (Thread-11) [pychromecast.socket_client] Error communicating with socket, resetting connection
2018-04-22 17:14:16 WARNING (Thread-12) [pychromecast.socket_client] Error communicating with socket, resetting connection
2018-04-22 17:14:16 ERROR (Thread-11) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-04-22 17:14:16 ERROR (Thread-12) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
My configuration for the Cast component is basic:
- platform: cast
Did some further testing today and have included the logs and some screenshots. The first screenshot is my casting choices when cast groups are turned off in Home Assistant, but all other cast devices are turned on (meaning I'm selecting them individually with their host ip address). Everything shows up, including the groups.
The "home assistant log test6" is when I turned groups on by:
platform: cast
While Home Assistant was running, I also restarted the router and then restarted every single cast device individually. All that should be evident in the log. None of that worked as you can see in screenshot 2, which is my list of casting choices. The Sony speaker and the Insignia Alarm clock, both running much older versions of chromecast software are the only devices present. The groups you see are groups that contain one or both of those two devices.
I then commented out platform: cast to remove the groups, but kept my individual selections by host, ie:
###platform: cast
platform: cast
host: 192.168.85.141
name: Living Room
Just like screenshot 1, all my device and groups now show up as cast targets. I included "home assistant log test7" with these conditions to compare against test6.
home-assistant test6.log
home-assistant test7.log
Can you cast to your devices from, say, your phone, when they show as unavailable in Home Assistant? While I didn't post any screenshots, I too am seeing devices and groups become unavailable. I've always assumed the two issues were related. However, if you're still able to cast to a device / group that's unavailable in Home Assistant, then I agree I may have a different issue.
I will have to test that when my Cast groups are unavailable the next time, as they have suddenly gone back to their off state almost 2 hours ago:
Syslog:
pi@Ra:~ $ cat /var/log/syslog | grep unavailable
Apr 23 02:17:23 Ra hass[13460]: #033[32m2018-04-23 02:17:23 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio, old_state=<state media_player.home_audio=unavailable; friendly_name=Home Audio, supported_features=21437 @ 2018-04-22T17:14:16.659293+02:00>, new_state=<state media_player.home_audio=off; friendly_name=Home Audio, supported_features=21437 @ 2018-04-23T02:17:23.181650+02:00>>#033[0m
Apr 23 02:17:23 Ra hass[13460]: #033[32m2018-04-23 02:17:23 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home_audio_with_bathroom, old_state=<state media_player.home_audio_with_bathroom=unavailable; friendly_name=Home Audio with bathroom, supported_features=21437 @ 2018-04-22T17:14:16.640050+02:00>, new_state=<state media_player.home_audio_with_bathroom=off; friendly_name=Home Audio with bathroom, supported_features=21437 @ 2018-04-23T02:17:23.219506+02:00>>#033[0m
Apr 23 02:17:43 Ra hass[13460]: #033[32m2018-04-23 02:17:43 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.garoeda_i, old_state=<state media_player.garoeda_i=off; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-22T17:14:16.308174+02:00>, new_state=<state media_player.garoeda_i=unavailable; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-23T02:17:43.591443+02:00>>#033[0m
Apr 23 02:17:59 Ra hass[13460]: #033[32m2018-04-23 02:17:59 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.garoeda_i, old_state=<state media_player.garoeda_i=unavailable; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-23T02:17:43.591443+02:00>, new_state=<state media_player.garoeda_i=off; friendly_name=Garoeda I, supported_features=21437 @ 2018-04-23T02:17:59.393369+02:00>>#033[0m
Home Assistant log:
2018-04-23 02:17:43 WARNING (Thread-6) [pychromecast.socket_client] Heartbeat timeout, resetting connection
Please test to see if they are available as cast targets regardless of status. What I've found is that whether they are "off" or "unavailable", they will not show up as available to cast to from Pandora, Google Play Music, or any other app that has cast capability. I'd love to have validation of that behavior.
Please test to see if they are available as cast targets regardless of status. What I've found is that whether they are "off" or "unavailable", they will not show up as available to cast to from Pandora, Google Play Music, or any other app that has cast capability. I'd love to have validation of that behavior.
It's very weird. Regardless of the media player status within Home Assistant, I can tell a Google Home to play a song on any of the individual Chromecast Audios or Google Homes and it will do so. If I try tell it to play to a cast group, however, only one set of speakers will play, which I assume is the leader of the group. And if I open Pandora or Google Play Music and hit the Cast icon, none of the individual devices or groups show up as options (except - as noted in an earlier comment - the older firmware devices with Chromecast built-in from Sony and Insignia. Those are solid).
As a reminder, this behavior is only when I have Home Assistant running with platform: cast discovering the groups. If I allow it to only discover the individual cast players, then everything works fine both in Home Assistant and in Pandora, Google Home, etc.
In addition to unavailable I just noticed unknown as well.
@dshokouhi Are you using cast groups in Home Assistant? I've found if I remove them, then the unavailable issue goes away (unfortunately, so too does a bunch of functionality). Could you test by removing cast groups and see if you get to:
@benjamin1492 this bug is only about cast groups so removing them to test is not an option. They need to work which is why we are troubleshooting this.
Understood. I'll wait on the resolution to this one, and if it doesn't fix my problem, I'll reopen my other case. For now, I'll leave ya'll alone to get the cast groups fixed.
I am having an issue where none of my cast components show up in home assistant anymore even if I use discovery.
So my problem is definitely different. Running the beta, I was able to get all the devices to A) show as available in Hass, and B) show as cast targets. But that only lasted for about 15 minutes before I was back to A) only the leader playing when cast group selected, and B) having no cast targets for GPM or Pandora. The 15 minutes to failure is an improvement...used to be instantaneous as soon as I started Hass.
@benjamin1492 have you tried removing/unplugging devices one by one to see if one of them is a factor?
Just chiming in because I'm seeing the same thing. My group will randomly go "unavailable" a few times a day, and then a few hours later it goes back to available again. I only have two devices in the group, so it seems plausible that when the leader selection is changed, it toggles between the two devices. At this moment, it's showing as unavailable in HA, but I'm able to use the group with Pandora
Hi, so I had another look at this problem today to see what could be causing this. One potential problem is that the disconnection logic is currently not perfect and we don't wait until the previous socket has truly disconnected when re-establishing a connection. This doesn't seem like something that could cause this error to me but I'm running out of potential causes.
I've update the cast integration a bit to resolve above issue. If someone wants to help, copy this file to <config_dir>/custom_components/media_player/cast.py. I'm not sure if it would solve the issue but it would at least be worth a try.
I've been running that 4/28 version for about a day and it hasn't solved the problem, but subjectively, I think it may a little different. It went unavailable three times today, but both were only for a minute or so (rather than hours like I think it was before)
@psfales Thanks for testing! I think 30 seconds to 60 seconds are more or less expected and there's not much we can do to cut this time down:
It takes 10-15 seconds until we receive the mDNS message with the new host.
Then we need to disconnect from the old chromecast. Can take up to 5-10 seconds depending on the amount of data waiting to be transferred and so on.
Finally, we need to connect to the new host. Can take 10+ seconds. Especially while the new host is still setting up to receive connections.
Unfortunately, it hasn't stayed so good. It went unavailable at 5:30 this morning and stayed unavailable for 2.5 hours until I rebooted
Oh noes :/ Reopening then...
Unfortunately, I won't be able to work on this for the next week and a half though because I'm in the process of studying for my final exams 📚
Certainly understand about your schedule. When you have time, I'm curious.... Is it possible to tell when the elected leaders changes, or which device it is at any given time? I think it would be interesting to confirm that the group going unvailable (or return to available) is correlated with a leader change.
There's no real visual way to see that from the front-end. But if you have debug logs enabled you can see a Disconnecting from previous chromecast message in there when a leader change is detected.
I experience this problem I'm pretty new to Homeassistant but am a developer. Let me know if you need anything!
I also have this problem. Not a developer but happy to test/help where I can.
I just realized that I have another chromecast devices (not group) that became unavailable prior to the chromecast group, 3 mins after the single device became available again, the group went unavailable.
The kitchen devices unavailablitiy is not restricted to chromecast, when it's unavailable in chromecast, it's not reachable from any other apps either. "All"s problems is howeber only limited to chromecast. Let me know if I can helt in any way :)
Same goes for me and the time a group takes to become unavailable seems totally random. I went away for a week so no music was played via other devices and on my return all groups were available. Unsure if a total fluke or due to not casting from other devices there was no need to elect a new group "leader". I presume Home Assistant was casting TTS weather alerts etc because i forgot to switch them off.
@JIOB, did you check your history? i'd be really curious to kno if not
interacting with it caused it to hold stable
On Fri, May 18, 2018 at 5:15 AM JIOB notifications@github.com wrote:
Same goes for me and the time a group takes to become unavailable seems
totally random. I went away for a week so no music was played via other
devices and on my return all groups were available. Unsure if a total fluke
or due to not casting from other devices there was no need to elect a new
group "leader". I presume Home Assistant was casting TTS weather alerts etc
because i forgot to switch them off.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/13530#issuecomment-390188171,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEuJQHrfPVcCjQ3uWSxKLDI_pSNvpWk1ks5tzrtNgaJpZM4TADhw
.
I didn't check at the time and its since been overwritten. If the same situation occurs again prior to a fix ill ensure i've got a log to share.
Not my proudest work, but I just did this as a cludge:
- alias: 'All unavailable for 3 minutes'
trigger:
platform: state
entity_id: media_player.all
to: 'unavailable'
for:
minutes: 15
action:
service: homeassistant.restart
homeassistant reboots whenever the group is unavialable for more than 15 minutes. I have a feeling this will come back and bite me in the ass...
I am actually wondering if maybe the cast platform can create a service call that allows us to basically "reload" the groups like what happens during a home assistant restart. A hass restart is the only way to bring the groups back maybe there is a way to trigger the rediscovery of just the cast groups when they become unavailable? I think I saw some platforms use unloading like hue maybe something similar can be triggered here? Sorry if I am shooting in the dark just trying to help offer ideas/suggestions :)
I have been thinking the same, but not sure if it has to be a service, it should just do it if the groups lose connection in that case.
It's because of mess with configuration.
I had same problem, I checked all my configuration an there was some parts that I correct them. Then I removed the database and restart the machine. It's been about 10 days that I don't have that problem anymore.
I agree with @dshokouhi and @kristoffernolgren it would be nice if some logic could be built in to restart the service when a group/groups become unavailable.
@aliaghil which parts of your configuration did you correct? My configuration now only contains..
- platform: cast
In my configuration I had this code in sensors:
`
sensor:
platform: systemmonitor
resources:
type: since_last_boot
type: processor_use
type: memory_free
type: disk_free
arg: /
platform: template
sensors:
time_template:
friendly_name: Time
value_template: '{{ as_timestamp(now()) | timestamp_custom("%d/%m %H:%M", True) }}'
since_last_boot_template:
friendly_name: Up Time
value_template: >
{%- set s = states.sensor.since_last_boot.state.split('.')[0] -%}
{{ s }}
platform: version
name: version
and I changed it to:
sensor:
platform: systemmonitor
resources:
type: since_last_boot
type: processor_use
type: memory_free
type: disk_free
arg: /
platform: template
sensors:
time_template:
friendly_name: "Time"
value_template: '{{ as_timestamp(now()) | timestamp_custom("%d/%m %H:%M", True) }}'
since_last_boot_template:
friendly_name: "Up Time"
value_template: >
{%- set s = states.sensor.since_last_boot.state.split('.')[0] -%}
{{ s }}
platform: version
name: "Version"
`
In my sensors wherever there was friendly_name: I used quotation mark for it.
After version 0.60 developers add cloud component, and I add it to my configuration, but didn't use it, even I didn't login to it. I think the problem was because of this, after I confined it, and logged in to it, the problem gone.
in configuration.yaml i had this:
`
homeassistant:
customize_glob: !include config/customize_glob.yaml
packages: !include_dir_named config/packages/
frontend:
extra_html_url:
/local/custom_ui/state-card-custom-ui.html
I disabled that two.
homeassistant:
customize_glob: !include config/customize_glob.yaml
packages: !include_dir_named config/packages/
frontend:
extra_html_url:
- /local/custom_ui/state-card-custom-ui.html
`
I was using separated config
I found it out, these files shouldn't go in the config folder config/config
automations.yaml
entity_registry.yaml
known_devices.yaml
scripts.yaml
secrets.yaml
I bring them back to root config folder config
the last one
I update all my automation with Automation editor.
@aliaghil are you saying that those steps have permanently fixed your instance of the cast component?
@JIOB yes. I update hassio to 0.71.0 and unfortunately the problem come back again :(
I'm going to downgrade it to v0.70.1 and see what's going on...
Just updated HomeAssistant to 0.72.0 and it forced me to reconfigure my Google cast devices. Anybody know if the change has the ability to fix this issue? Will post back if i find anything.
I also updated to 0.72.0 and got the dialog about forcing me to reconfigure
Google Cast. But I don't understand what this means. It apparently
created a file in the config directory called ".config_entries.json" which
has an entry for "Google Cast." But other than that one-time interaction
I don't see any change in behavior. "Google Cast" does not appear anywhere
in the UI and all the Chromecast, Chromecast Audio, and audio groups that
were there before are still lthere.
On Sun, Jun 24, 2018 at 6:28 AM, JIOB notifications@github.com wrote:
Just updated HomeAssistant to 0.72.0 and it forced me to reconfigure my
Google cast devices. Anybody know if the change has the ability to fix this
issue? Will post back if i find anything.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/13530#issuecomment-399749490,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKyoCsrJK8dEx3GKnh19WWJhmAk19vjBks5t_3fbgaJpZM4TADhw
.
After updating to 0.72.0 and using the new UI config method, I am still experiencing this issue. So it doesn't look like the new config method fixed the issue.
I am having the same issue here with 0.72.
Individual devices work, by group gets dropped. I do not recall having this issue before
The HA log shows the issue happening first two nights ago @2:38am, which seems to somehow recovered (stopped reporting errors in the log) , and similar errors last nigh @2:27am , which have not recovered yet
2018-07-05 02:38:17 ERROR (Thread-10) [pychromecast.socket_client] Error reading from socket.
2018-07-05 02:38:17 WARNING (Thread-10) [pychromecast.socket_client] Error communicating with socket, resetting connection
2018-07-05 02:38:17 ERROR (Thread-10) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-05 02:38:22 ERROR (Thread-10) [pychromecast.socket_client] Failed to connect. No retries.
2018-07-05 02:38:39 WARNING (Thread-8) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-05 02:38:54 ERROR (Thread-8) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-05 02:41:58 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-05 02:42:05 ERROR (Thread-9) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-05 03:05:35 WARNING (Thread-7) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-05 03:05:38 ERROR (Thread-7) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-05 03:29:43 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
2018-07-06 02:27:17 ERROR (Thread-191485) [pychromecast.socket_client] Error reading from socket.
2018-07-06 02:27:17 WARNING (Thread-191485) [pychromecast.socket_client] Error communicating with socket, resetting connection
2018-07-06 02:27:17 ERROR (Thread-191485) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-06 02:27:22 ERROR (Thread-191485) [pychromecast.socket_client] Failed to connect. No retries.
2018-07-06 02:27:45 WARNING (Thread-8) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-06 02:27:52 ERROR (Thread-8) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-06 02:51:57 WARNING (Thread-7) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-06 02:52:04 ERROR (Thread-7) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-06 02:52:15 ERROR (Thread-481327) [pychromecast.socket_client] Error reading from socket.
2018-07-06 02:52:15 WARNING (Thread-481327) [pychromecast.socket_client] Error communicating with socket, resetting connection
2018-07-06 02:52:15 ERROR (Thread-481327) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-06 04:35:58 WARNING (Thread-9) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-06 04:36:01 ERROR (Thread-9) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-06 07:41:15 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
I use Chromecast Audio groups extensively and use playing/off state changes to trigger many automations. (volume setting, turning off and on connected amps etc).
Here's a log from last night, which shows the groups becoming unavailable at 22:36, coming back 61s later, then going unavailable again 1s later. The groups recover during the night.
There are two groups, "All" and "Downstairs". "sony" is the A/V receiver with cast built in. 'sony_2' is the songpal component of same device. I doubt that's relevant, other than to show that songpal and pychromecast both report unavailable at roughly the same times.
Casting GPM to the CCA 'bedroom' begins at 22:23 and ends at 23:22.
2018-07-11 22:23:36 INFO bedroom -> 'idle'
2018-07-11 22:23:36 INFO (MainThread) [homeassistant.core] Bus:Handling <Event call_service[L]: service_data=entity_id=media_player.bedroom, volume_level=0.15, service_call_id=1975828368-6972, service=volume_set, domain=media_player>
2018-07-11 22:23:36 INFO (Thread-21) [pychromecast.controllers] Receiver:setting volume to 0.1
2018-07-11 22:23:36 INFO bedroom -> 'playing'
...
2018-07-11 22:34:33 INFO bedroom -> 'playing'
2018-07-11 22:36:01 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.60', port=8009, uuid='afb73d06-77f7-39df-d206-0b98b58be99d', model_name='STR-DN860', friendly_name='Sony')
2018-07-11 22:36:04 WARNING (Thread-53) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-11 22:36:06 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.60', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 22:36:06 DEBUG (Thread-53) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-11 22:36:06 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.60', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 22:36:06 WARNING (Thread-52) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-11 22:36:06 DEBUG (Thread-52) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-11 22:36:06 INFO downstairs -> 'unavailable'
2018-07-11 22:36:06 INFO all -> 'unavailable'
2018-07-11 22:36:11 WARNING (Thread-24) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-11 22:36:11 DEBUG (Thread-24) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-11 22:36:11 INFO sony -> 'unavailable'
2018-07-11 22:36:36 ERROR (Thread-53) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-11 22:36:36 ERROR (Thread-52) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-11 22:36:41 ERROR (Thread-24) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-11 22:37:19 INFO sony_2 -> 'unavailable'
2018-07-11 22:37:55 INFO sony_2 -> 'off'
2018-07-11 22:37:55 DEBUG (Thread-52) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-11 22:37:55 INFO all -> 'off'
2018-07-11 22:37:55 DEBUG (Thread-24) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-11 22:37:55 DEBUG (Thread-53) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-11 22:37:55 INFO sony -> 'off'
2018-07-11 22:37:55 INFO downstairs -> 'off'
2018-07-11 22:37:56 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.60', port=8009, uuid='afb73d06-77f7-39df-d206-0b98b58be99d', model_name='STR-DN860', friendly_name='Sony')
2018-07-11 22:37:56 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered chromecast ChromecastInfo(host='10.100.39.92', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 22:37:56 DEBUG (MainThread) [homeassistant.components.media_player.cast] Discovered chromecast with same UUID: ChromecastInfo(host='10.100.39.92', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 22:37:56 DEBUG (MainThread) [homeassistant.components.media_player.cast] Disconnecting from chromecast socket.
2018-07-11 22:37:56 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered chromecast ChromecastInfo(host='10.100.39.92', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 22:37:56 INFO all -> 'unavailable'
2018-07-11 22:37:56 DEBUG (MainThread) [homeassistant.components.media_player.cast] Discovered chromecast with same UUID: ChromecastInfo(host='10.100.39.92', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 22:37:56 DEBUG (MainThread) [homeassistant.components.media_player.cast] Disconnecting from chromecast socket.
2018-07-11 22:37:56 INFO downstairs -> 'unavailable'
2018-07-11 22:38:01 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connecting to cast device ChromecastInfo(host='10.100.39.92', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 22:38:01 INFO (Thread-20) [pychromecast] Querying device status
2018-07-11 22:38:01 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connecting to cast device ChromecastInfo(host='10.100.39.92', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 22:38:01 ERROR (Thread-20) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-11 22:38:01 INFO (Thread-6) [pychromecast] Querying device status
2018-07-11 22:38:01 ERROR (Thread-6) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-11 22:39:20 INFO bedroom -> 'idle'
2018-07-11 22:39:20 INFO bedroom -> 'playing'
...
2018-07-11 23:22:37 INFO bedroom -> 'playing'
2018-07-11 23:22:51 INFO (Thread-11) [pychromecast] Quiting current app
2018-07-11 23:22:51 INFO (Thread-11) [pychromecast.controllers] Receiver:Stopping current app '2872939A'
2018-07-11 23:22:51 INFO bedroom -> 'off'
2018-07-11 23:37:14 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered chromecast ChromecastInfo(host='10.100.39.60', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 23:37:14 DEBUG (MainThread) [homeassistant.components.media_player.cast] Discovered chromecast with same UUID: ChromecastInfo(host='10.100.39.60', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 23:37:14 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connecting to cast device ChromecastInfo(host='10.100.39.60', port=42904, uuid='02005ffe-7f5c-4512-b118-50e1d4f87cdc', model_name='Google Cast Group', friendly_name='All')
2018-07-11 23:37:14 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered chromecast ChromecastInfo(host='10.100.39.60', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 23:37:14 INFO (Thread-3) [pychromecast] Querying device status
2018-07-11 23:37:14 DEBUG (MainThread) [homeassistant.components.media_player.cast] Discovered chromecast with same UUID: ChromecastInfo(host='10.100.39.60', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 23:37:14 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connecting to cast device ChromecastInfo(host='10.100.39.60', port=42760, uuid='c790e2bc-dae8-439b-8ab9-408266d10422', model_name='Google Cast Group', friendly_name='Downstairs')
2018-07-11 23:37:14 INFO (Thread-4) [pychromecast] Querying device status
2018-07-11 23:37:15 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connection successful!
2018-07-11 23:37:15 INFO all -> 'off'
2018-07-11 23:37:15 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connection successful!
2018-07-11 23:37:15 INFO downstairs -> 'off'
2018-07-12 02:23:21 WARNING (Thread-30) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 02:23:21 DEBUG (Thread-30) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 02:23:21 INFO lounge_mini -> 'unavailable'
2018-07-12 02:23:36 DEBUG (Thread-30) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-12 02:23:36 INFO lounge_mini -> 'off'
2018-07-12 02:23:38 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.89', port=8009, uuid='e957ad8e-8b83-0f38-97ae-89c501ce6e34', model_name='Google Home Mini', friendly_name='Lounge Mini')
2018-07-12 02:45:48 WARNING (Thread-29) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 02:45:48 DEBUG (Thread-29) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 02:45:48 INFO office -> 'unavailable'
2018-07-12 02:45:55 ERROR (Thread-29) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-12 02:46:00 DEBUG (Thread-29) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-12 02:46:00 INFO office -> 'off'
2018-07-12 02:46:03 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.94', port=8009, uuid='a0721def-786f-a924-c5cd-75cd5a7f569d', model_name='Chromecast Audio', friendly_name='Office')
2018-07-12 03:15:51 WARNING (Thread-28) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 03:15:51 WARNING (Thread-27) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 03:15:51 DEBUG (Thread-28) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 03:15:51 DEBUG (Thread-27) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 03:15:51 INFO chromecast_lounge -> 'unavailable'
2018-07-12 03:16:07 DEBUG (Thread-28) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-12 03:16:07 INFO chromecast_lounge -> 'off'
2018-07-12 03:16:10 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.91', port=8009, uuid='dd9ff914-24cf-86ad-5ed1-85ce9ac1af8e', model_name='Chromecast', friendly_name='Chromecast Lounge')
2018-07-12 04:05:28 WARNING (Thread-26) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 04:05:28 DEBUG (Thread-26) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 04:05:28 INFO bedroom_home -> 'unavailable'
2018-07-12 04:05:35 ERROR (Thread-26) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-12 04:05:41 DEBUG (Thread-26) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-12 04:05:41 INFO bedroom_home -> 'off'
2018-07-12 04:05:42 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.90', port=8009, uuid='5e2fc371-10e9-ea49-23b4-216a51072fc7', model_name='Google Home', friendly_name='Bedroom Home')
2018-07-12 04:51:47 WARNING (Thread-32) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 04:51:47 DEBUG (Thread-32) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 04:51:47 INFO bedroom -> 'unavailable'
2018-07-12 04:51:55 ERROR (Thread-32) [pychromecast.socket_client] Failed to connect, retrying in 5.0s
2018-07-12 04:52:00 DEBUG (Thread-32) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-12 04:52:00 INFO bedroom -> 'off'
2018-07-12 04:52:04 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.93', port=8009, uuid='b5fda076-4ba4-1565-9f3d-8f98ddfcb78c', model_name='Chromecast Audio', friendly_name='Bedroom')
2018-07-12 04:56:25 WARNING (Thread-25) [pychromecast.socket_client] Heartbeat timeout, resetting connection
2018-07-12 04:56:25 DEBUG (Thread-25) [homeassistant.components.media_player.cast] Cast device availability changed: LOST
2018-07-12 04:56:25 INFO kitchen -> 'unavailable'
2018-07-12 04:56:39 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered previous chromecast ChromecastInfo(host='10.100.39.92', port=8009, uuid='24ddbab5-3d2c-aebf-805c-e866fa3c2458', model_name='Chromecast Audio', friendly_name='Kitchen')
2018-07-12 04:56:41 DEBUG (Thread-25) [homeassistant.components.media_player.cast] Cast device availability changed: CONNECTED
2018-07-12 04:56:41 INFO kitchen -> 'off'
Since switching to hassio I have the problem too:
Any news on this issue?
Still not working for me with the latest version :(
@OttoWinter @balloob - Is anyone actively working on this issue? This has been broken for months. I used to have automations to play music and announcements to certain groups. But casting to groups is anything but reliable. My logs are full of pychromecast failure to connect errors. What can we do to help test/debug?
Yeah, absolutely nothing has changed since this was first reported (neither better nor worse). :(
I have a far from ideal workaround for triggering automations while casting to speaker groups. I'm using the Unifi WAP component to monitor the bytes flowing to Chromecast Audio's. If one spikes above 20000, then the amp supplying power to the speakers it feeds turns on. There's usually a delay of 5-20 seconds given the polling frequency, but it's otherwise tolerable. Also, if there are no spikes on any of the Chromecasts for 10 minutes, then the corresponding amp is (hopefully) turned off. This is only for cast groups...casting to individual Chromecast Audio's is much more straightforward. Also, to make this work, I had to convert all of the Chromecast Audio's from wired to wireless because the Unifi controller doesn't track bytes for wired devices. I haven't noticed any issues going to wireless, but I'd really prefer to keep them wired.
While this is a passable work around, it is only about 60% effective. The speakers always turn on, but only turn off after 10 minutes about half the time. I haven't figured out why yet, so I have an automation that turns off all the amps at midnight.
Thanks, I'll check that out then. I like the idea of the broadcast not killing any music that was playing.
As since cast groups stopped working, I just listed out my cast devices within my script/automation as a work around for now.
alias: TTS Test
sequence:
data:
entity_id: media_player.basement_speakers, media_player.basement_assistant,
media_player.garage_assistant, media_player.pole_barn_assistant
volume_level: 0.6
service: media_player.volume_set
data:
entity_id: media_player.basement_speakers, media_player.basement_assistant,
media_player.garage_assistant, media_player.pole_barn_assistant
message: This is a test message. Is the volume loud enough?
service: tts.google_say
I too would like to know where things are at with this issue. I used to have automations fire when certain groups were playing etc. They've been useless for months.
Agree this is still an issue. Now I am even starting to get this with certain cast devices.
I have the same problem
Wish there was a way to vote on issues, this is such a pain, having to reboot HA nightly to keep Chromecast groups somewhat operational.
My server shuts down over night and starts up the next morning. The groups
are often already non-functional by the time I get home from work!
On Thu, Sep 20, 2018 at 11:01 AM joydashy notifications@github.com wrote:
Wish there was a way to vote on issues, this is such a pain, having to
reboot HA nightly to keep Chromecast groups somewhat operational.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/issues/13530#issuecomment-423102075,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AQNwbRzGtM6FyPjMn9UnszZ3-4qDxLq0ks5uc1l1gaJpZM4TADhw
.
My server shuts down over night and starts up the next morning. The groups are often already non-functional by the time I get home from work!
…
On Thu, Sep 20, 2018 at 11:01 AM joydashy @.***> wrote: Wish there was a way to vote on issues, this is such a pain, having to reboot HA nightly to keep Chromecast groups somewhat operational. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#13530 (comment)>, or mute the thread https://github.com/notifications/unsubscribe-auth/AQNwbRzGtM6FyPjMn9UnszZ3-4qDxLq0ks5uc1l1gaJpZM4TADhw .
My HA also reboots when it needs to use Chromecast groups and detects they are Unavailable. This of course introduces a delay in the functionality. It's a sucky workaround!
Give 0.78.1 a try
Give 0.78.1 a try
Looks promising! Will update soon.
already on 0.78.1 and looks like it fixed my issue. got instances of unavailable issues on my 3 cast groups and they went from off to unavailable to off in seconds.
Updated to 0.78.1 yesterday evening. This morning woke up to 2 of my 4 groups Unavailable... and one of my individual chromecast audios, as well. Had to restart HA to re-connect to them.
I also still have the issues with 0.78.1.
Also still having the same problem with 0.78.1
@awarecan
Thanks for your help with this. If you need anything in addition to what I've attached, please let me know. I'd be glad to help any way I can in getting this resolved.
Here's my config:
# Chromecast Audios
- platform: cast
name: Den
host: 192.168.85.130
- platform: cast
name: Kitchen
host: 192.168.85.145
- platform: cast
name: Dining Room
host: 192.168.85.146
- platform: cast
name: Living Room
host: 192.168.85.144
- platform: cast
name: Patio
host: 192.168.85.173
- platform: cast
name: Master Bedroom
host: 192.168.85.142
- platform: cast
name: Master Bathroom
host: 192.168.85.149
- platform: cast
name: Master Closet
host: 192.168.85.147
- platform: cast
name: Playroom
host: 192.168.85.141
- platform: cast
name: Office
host: 192.168.85.143
- platform: cast
name: "Sloane's Speaker"
host: 192.168.85.125
- platform: cast
#Google Home
- platform: cast
name: Office Home
host: 192.168.85.160
- platform: cast
name: Master Bedroom Home
host: 192.168.85.115
- platform: cast
name: "Sloane's Alarm Clock"
host: 192.168.85.205
- platform: cast
name: Kitchen Home
host: 192.168.85.118
- platform: cast
name: Den Home
host: 192.168.85.128
#Chromecast Videos
- platform: cast
name: Den Chromecast
host: 192.168.85.100
- platform: cast
name: Den Shield
host: 192.168.85.204
- platform: cast
name: Playroom Shield
host: 192.168.85.203
And here's the output from logger with focus on logger:
home-assistant.log
I can also confirm that https://github.com/home-assistant/home-assistant/pull/16732 has not fixed this.
Which makes sense, as that fix refers to it being a problem for 15 days, but I have had this problem for much longer. Current issue is also much older.
@benjamin1492, 0.78.1 would not resolve your issue since you are configuring host IP address manually.
However, the #16786 may help to fix your problem, I rewrote the device connection logic for your case.
78.1 did not help me either. It lasted about a day, but now I have both my group and my cast devices showing as unavailable.
I created a new PR #16804, not sure if it will help, but you can try.
#16786 caused more problem than fixed, I closed it.
0.78.3 - same problem - group unavailable
Running 0.78.3 this is my log when the cast group 'Home' got unavailable. The cast devices are setup by the discover feature, no IP component configuration:
018-09-24 13:00:48 DEBUG (zeroconf-ServiceBrowser__googlecast._tcp.local.) [homeassistant.components.media_player.cast] Discovered chromecast ChromecastInfo(host='192.168.178.39', port=42673, uuid='a1883456-632f-4b0b-a2c6-fa6a246f1010', manufacturer='', model_name='Google Cast Group', friendly_name='Home') 2018-09-24 13:00:48 DEBUG (MainThread) [homeassistant.components.media_player.cast] Discovered chromecast with same UUID: ChromecastInfo(host='192.168.178.39', port=42673, uuid='a1883456-632f-4b0b-a2c6-fa6a246f1010', manufacturer='', model_name='Google Cast Group', friendly_name='Home') 2018-09-24 13:00:48 DEBUG (MainThread) [homeassistant.components.media_player.cast] Disconnecting from chromecast socket. 2018-09-24 13:00:48 INFO (MainThread) [homeassistant.core] Bus:Handling <Event state_changed[L]: entity_id=media_player.home, old_state=<state media_player.home=off; friendly_name=Home, supported_features=21437 @ 2018-09-24T08:56:49.289521+02:00>, new_state=<state media_player.home=unavailable; friendly_name=Home, supported_features=21437 @ 2018-09-24T13:00:48.276523+02:00>> 2018-09-24 13:00:49 DEBUG (Thread-15) [pychromecast.socket_client] Sending: Message urn:x-cast:com.google.cast.tp.connection from sender-0 to receiver-0: {'type': 'CLOSE', 'origin': {}} 2018-09-24 13:00:49 DEBUG (Thread-15) [pychromecast.socket_client] connection listener: 70432210 (CastStatusListener) 2018-09-24 13:00:49 DEBUG (Thread-15) [homeassistant.components.media_player.cast] Received cast device connection status: DISCONNECTED 2018-09-24 13:00:49 DEBUG (MainThread) [homeassistant.components.media_player.cast] Connecting to cast device ChromecastInfo(host='192.168.178.39', port=42673, uuid='a1883456-632f-4b0b-a2c6-fa6a246f1010', manufacturer='', model_name='Google Cast Group', friendly_name='Home')
@awarecan under new PR #16804 the groups still don't come back as per this issue.
Confirmed here, as well.
Since #16804 only addressed issue of start up hanging in manual configure scenario, rest logic reverted back to 0.77. So if you have group unavailable issue before, you still have it now.
I don't have "group" myself, so I won't be able to reproduce or debug that issue, so I am afraid I won't be able to help much.
@awarecan this is where you suggest people to buy you two Google Homes so you can create a group 👍
If a donation towards a Ghome Mini or so would help get this bug fixed, I'm in. This is by far my biggest issue with HA right now.
If a donation towards a Ghome Mini or so would help get this bug fixed, I'm in. This is by far my biggest issue with HA right now.
I would be in as well.
I'm in as well, but want to add my two cents on how to proceed. As background, I have a very robust Google cast implementation: 10 Chromacast Audios, 4 Google Homes, an Insignia alarm clock, and a Sony speaker with Chromecast built-in. Ever since Google updated the firmware in Nov-17, this has been a problem. However, none of the Chromecast Built-in devices that remain on old firmware such as the Sony speaker or Insignia alarm clock are impacted. My suggestion is that each of us willing to send equipment to awarecan for this project send something different: a full size Google Home, a Google Home Mini, a Chromecast Audio, and at least 2 Chromecast built-in devices. This would allow awarecan to build a variety of different groups to test the code - group of all built-ins, group of Google devices, and a mixed group.
This integration has been a graveyard for many a capable Home Assistant developer just because of it's overall complexity. This approach will give us the best shot at finally getting this thing resolved. I'd even be willing to throw a $100 bounty out there for a final fix, in addition in addition to a Google Home.
Awarecan: You mission should you choose to accept it is to fix the Cast platform for good. Shoot me an address and I'll get a Home en route.
I have only one google home mini and it regularly (after a few hours) goes to unabailable until I restart HA. Is this the same issue or is this fixed with #16804?
Still having this issue on Home Assistant 0.79.3
@awarecan Is there anything we can do to help? Donations, devices, etc? I agree with most people here this desperately needs to be corrected once and for all and I know many of us are willing to help in anyway we can.
Dear, someone working on this problem ???
Same problem in Home Assistant 0.80.2
Yeah still experiencing this on 0.80.2
Has no one tried reverting whatever component changed back in March? Nothing has been fixed regarding this issue since it cropped up back then.
@j0barr this issue has nothing to do with any changes. The issue has been present since day 1 of Google Cast Groups being available and integrated into HA. It has to do with how the leader of the group (which is comprised of all the devices in the group) is elected. If the leader changes (happens relatively frequent), the group goes unavailable. You can see this with netdisco. More than likely a dev will have to do a big rewrite in order to address this issue.
That's odd if nothing has changed because I swear it was working for me back with version 65.
You can easily revert back to that version and test. Or set up a dev environment and only add the cast devices. You will see that the groups go unavailable. Trust me, I've been involved in this issue since day 1.
Issue goes back way further than that. https://github.com/home-assistant/home-assistant/issues/7782 is when I first started tracking the problem.
Looked into this for a bit, going to see if the latest version of zeroconf would fix this. Zeroconf is used for pychromecast which is used for the Cast component.
Two fixes from their changelog interest me:
Switched from netifaces to ifaddr (pure Python)
ServiceBrowser entries are being refreshed when 'stale' now
https://github.com/jstasiak/python-zeroconf/blob/master/README.rst
The current version used by pychromecast is 0.17.7
@bryanyork Nope, that is unrelated. The issue is that when the cast group changes its elected leader we are currently not re-connecting to the new elected leader in the way the chromecast expects. We do get the callback from zeroconf that it has changed the leader. And we currently do try to disconnect from the old leader and re-connect to the new one. However, something in that process is behaving in a way that the chromecast doesn't expect, and though many hours of debugging I haven't been able to resolve the problem yet. This issue is particularly hard to diagnose because it just happens randomly every few hours, so if you test something you always have to wait that amount of time for the change to trigger again.
I've noticed that restarting HA always fixes this problem. What is it about restarting HA that causes this to be fixed, at least temporarily?
Is it possible we could make the software mimic whatever a reboot does to get around the issue?
I'd tried adding an automation to reboot if cast groups become unavailable but that became unreliable too as sometimes HA wouldn't come back,
I've noticed that restarting HA always fixes this problem. What is it about restarting HA that causes this to be fixed, at least temporarily?
I'm with Shadex12, a restart will fix it. I was using cast groups as a alarm warning, but with them disappearing (going unavailable) I have temporaily reverted to a single speaker.
Can't add much to the discussion except to add my encouragement for a fix.
I am on Hassio 0.82.1 and my groups were also "unavailable" after some time in the middle of the night.
I have two groups. Each of them were "off" from 22:47 to 02:19. (2018.12.04)
Then they were "unavailable" from 02:19 to 03:08. (2018.12.05)
Then again they went to status "off" from 03:08 to 04.57. (2018.12.05)
Then they went unavailable until now: 04:57 to 22:04.
Logs on hassio:
https://paste.ubuntu.com/p/J6Nt3pSzH9/
If I can help in any way let me known.
Same issue here on HA 0.84.2.
Groups change to unavailable every other day and refuses to come back, restarting HA always does the trick.
Non here either (0.86.2)
I'm affected by the issue as well.
I'm looking for a workaround until the issue is resolved.
I've seen that restarting Home Assistant does solve the issue, so something is capable of healing this 'unavailable' status in HA.
Does anyone know how to reproduce this without a complete restart ?
My idea would be to create an automation which does something like:
If
no cast devices are running
and
at least 1 cast group is 'unavailable'
then
reload the chomecast integration (-> heal)
Any idea on which service/function to use ?
This should be fixed in beta 0.88.0b0
Please give it a try!
To provoke errors, try restarting casts that are members of an audio group, either through the Google Home app or by simply power cycling.
Note: It's normal that the group goes offline and comes back a few times as group leadership may be handed over several times if the restarted unit is the preferred group leader.
In case it's still not working, a complete HA log - from starting HA until group is no longer - is needed for debugging.
Logger options in configuration.yaml
logger:
default: info
logs:
homeassistant.components.cast: debug
homeassistant.components.cast.media_player: debug
pychromecast: debug
pychromecast.discovery: debug
pychromecast.socket_client: debug
zeroconf: debug
Hi,
I pulled Home assistant Dev 0.89 in a docker container (fresh config, host networking) and used discovery to autoconfigure my chromecasts and groups.
They are discovered but all 'unavailable'.
The attached log shows "Failed to connect" errors.
https://paste.ubuntu.com/p/4BRQ3hhQBC/
@masterz666 That should be fixed in beta 0.88.0b2
@emontnemery I'm on 0.88.0b0 since Thursday and didn't had this issue since then. Seems like it really fixed it (at least for me) 🎉
Thanks for you work! 👍
on 0.88b2 I sometime have this in the log. is this expected ?
[Chromecast salon:8009] Heartbeat timeout, resetting connection
I don't want to jump the gun but I think the new pychromecast update may have solved this issue! And mainly due to a experimental commit. https://github.com/balloob/pychromecast/pull/268. Crossing fingers but this is very promising!
@edif30, @soldag Thanks for the feedback! balloob/pychromecast#268 is included in HA 0.88 via #21097 so I'll go ahead and close this issue.
@masterz666 The print means HA lost the connection to a chromecast. At least for me, chromecasts are not extremely stable and reboot now and then, so yes, I'd say its expected.
Does anyone on this thread have a Sony or Insignia speaker with Chromecast Built-in? If so, have you noticed them causing any issues after updating to the new pychromecast? The new version still isn't working for me, which I think makes me the exception based on the recent feedback. I'm now trying to troubleshoot my cast install, and starting with the less common devices.
semi-unrelated:
@ttaidapos can you post your yaml for those media player cards that you posted pics of?
Thanks.
For what it's worth. I'm on 88.2 and the group casting still going strong! Still have a plethora of errors though.
Line 718: 2019-03-03 04:58:09 WARNING (Thread-12) [pychromecast.socket_client] [Baby display:8009] Heartbeat timeout, resetting connection Line 1807: 2019-03-04 02:01:09 WARNING (Thread-2) [pychromecast.socket_client] [Living Room Speaker:8009] Heartbeat timeout, resetting connection Line 1828: 2019-03-04 02:22:58 WARNING (Thread-7) [pychromecast.socket_client] [Office display:8009] Heartbeat timeout, resetting connection Line 1829: 2019-03-04 02:28:16 WARNING (Thread-9) [pychromecast.socket_client] [Kitchen Speaker:8009] Heartbeat timeout, resetting connection Line 1830: 2019-03-04 02:28:23 WARNING (Thread-6) [pychromecast.socket_client] [Bedroom Speaker:8009] Heartbeat timeout, resetting connection Line 1836: 2019-03-04 02:34:31 WARNING (Thread-15) [pychromecast.socket_client] [Bathroom Speaker:8009] Heartbeat timeout, resetting connection Line 1873: 2019-03-04 03:17:51 WARNING (Thread-12) [pychromecast.socket_client] [Baby display:8009] Heartbeat timeout, resetting connection Line 1894: 2019-03-04 03:42:43 WARNING (Thread-5) [pychromecast.socket_client] [Soundbar Speaker:8009] Heartbeat timeout, resetting connection Line 1944: 2019-03-04 04:36:27 WARNING (Thread-10) [pychromecast.socket_client] [Dining Room Speaker:8009] Heartbeat timeout, resetting connection Line 1988: 2019-03-04 05:26:33 WARNING (Thread-14) [pychromecast.socket_client] [Kitchen display:8009] Heartbeat timeout, resetting connection
semi-unrelated:
@ttaidapos can you post your yaml for those media player cards that you posted pics of?
Thanks.
It's a lot and I take no credit for it. I have modified it the yaml a lot. here it is and best of luck!
https://pastebin.com/RbWJVNhH
I lose cast groups still with 0.97.2...
| gharchive/issue | 2018-03-29T09:51:05 | 2025-04-01T06:38:58.179756 | {
"authors": [
"JIOB",
"OttoWinter",
"Roemer",
"Shadex12",
"Spartan-II-117",
"Wonkavator",
"accelle17",
"ajfriesen",
"aliaghil",
"allmoney",
"awarecan",
"backcountrymountains",
"balloob",
"benjamin1492",
"bryanyork",
"darylsargent",
"dshokouhi",
"e1miran",
"edif30",
"eeepsylon",
"emontnemery",
"fanaticDavid",
"fillwe",
"frankhommers",
"gezonthenet",
"grangemd",
"harry19023",
"iorifly",
"j0barr",
"josephkiser04",
"joydashy",
"kalkih",
"kdjordjev",
"kristoffernolgren",
"masterz666",
"psfales",
"rgruebel",
"smoke007",
"soldag",
"ttaidapos"
],
"repo": "home-assistant/home-assistant",
"url": "https://github.com/home-assistant/home-assistant/issues/13530",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
314006938 | 0.67.0b1 - BT mac addresses get prefixed with double underscore in known_devices.yaml
Home Assistant release with the issue:
0.67.0b1
Last working Home Assistant release (if known):
Unknown
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
Bluetooth device tracker
Description of problem:
BT devices are getting a double underscore in the mac address in known_devices.yaml
mac: BT__00:11:22:AA:BB:CC
This causes an error as it thinks that the second underscore is part of the mac address
Correct mac address...
mac: BT_00:11:22:AA:BB:CC
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
Traceback (if applicable):
Additional information:
When removing the rogue underscore, or making any other changes in known_devices.yaml the device is rediscovered again, with a double underscore again
Confirming the same behaviour running 0.67b1 in hassio. When a device is added as a new one, it shows up in known_devices.yaml as:
my_iphone:
hide_if_away: false
icon:
mac: BT__40:xx:xx:xx:xx:DB
name: my iPhone
picture:
track: true
If I change my existing device but suffix BT with an extra _ the bluetooth device tracker gives the following error:
[homeassistant.components.device_tracker.bluetooth_tracker] Error looking up Bluetooth device
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/homeassistant/components/device_tracker/bluetooth_tracker.py", line 92, in update_bluetooth
result = bluetooth.lookup_name(mac, timeout=5)
File "/usr/lib/python3.6/site-packages/bluetooth/bluez.py", line 59, in lookup_name
raise BluetoothError ("%s is not a valid Bluetooth address" % address)
bluetooth.btcommon.BluetoothError: _40:xx:xx:xx:xx:DB is not a valid Bluetooth address
Can, however confirm, that bluetooth tracker works if you delete your previously added BT-devices and let it recreate them in known_devices.yaml.
This issue is directly related to this PR: https://github.com/home-assistant/home-assistant/pull/12458
Appears to be working correctly again in 0.67.0
| gharchive/issue | 2018-04-13T08:03:34 | 2025-04-01T06:38:58.192616 | {
"authors": [
"elbogi",
"jimbob1001"
],
"repo": "home-assistant/home-assistant",
"url": "https://github.com/home-assistant/home-assistant/issues/13846",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
366487676 | Tap on slider on mobile triggers two state changes/events/messages
Home Assistant release with the issue:
v 0.78.3
Description of problem:
When using home assistant on a mobile (probably also on a tablet) tapping a slider, for example for brightness, triggers two times the same state change/event/message.
In my specific case I'm using MQTT and it results in 2x the same MQTT message being published.
When moving the slider and then releasing it only a single state change/event/message is created/sent.
This sounds like a frontend issue.
/move to home-assistant/home-assistant-polymer
| gharchive/issue | 2018-10-03T19:16:39 | 2025-04-01T06:38:58.194919 | {
"authors": [
"fabaff",
"simonvanderveldt"
],
"repo": "home-assistant/home-assistant",
"url": "https://github.com/home-assistant/home-assistant/issues/17112",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
489597139 | Entity property configuration: The following attributes are already set in customize.yaml
Home Assistant release with the issue
0.98.2
Last working Home Assistant release (if known):
unknown
Operating environment (Hass.io/Docker/Windows/etc.):
Docker on Debian Busterb
Component/platform:
Entity configuration in "Settings -> Configuration"
Description of problem:
See https://community.home-assistant.io/t/entity-property-configuration-the-following-attributes-are-already-set-in-customize-yaml/135444
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
See the linked forum thread above, i have provided some snippets there.
Traceback (if applicable):
not applicable
Anyone? This is still a problem on 0.100 for me.
Is this still an issue?
I have read through your forum thread and would suggest that you try out the given solution:
homeassistant:
customize: !include customize.yaml
You may be right about YAML indentation, however I would always follow the official documentation.
In this case: customize entities
I have solved it by moving the "customize" dictionary key to the beginning of the dict. It's strange since yaml dicts shouldn't be ordered, but it works for me now.
Oh okay that is great to hear 👍
Please mark this issue as solved :)
| gharchive/issue | 2019-09-05T08:13:26 | 2025-04-01T06:38:58.200878 | {
"authors": [
"simonszu",
"springstan"
],
"repo": "home-assistant/home-assistant",
"url": "https://github.com/home-assistant/home-assistant/issues/26445",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
211563790 | hass becomes unresponsive after a few hours
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.39.2
Python release (python3 --version):
3.5.3
Component/platform:
HASS Docker image
Description of problem:
after a few hours, the docker container and hass are unresponsive. The front end shows disconnected. the log no longer reports anything. The log is full of errors like this:
17-03-02 02:27:39 ERROR (Thread-3) [homeassistant.components.sensor.command_line] Timeout for command: python3 /config/sensor/getBIProfile.py
17-03-02 02:27:39 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-02 02:27:44 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-02 02:27:48 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-02 02:27:52 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-02 02:28:05 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-02 02:28:11 ERROR (MainThread) [homeassistant.core] Timer got out of sync. Resetting
17-03-02 02:28:32 WARNING (Thread-13) [pychromecast.socket_client] Heartbeat timeout, resetting connection
17-03-02 02:28:50 WARNING (Thread-17) [pychromecast.socket_client] Error communicating with socket, resetting connection
Full log here: https://hastebin.com/gabikeyayo.sql
Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:
Traceback (if applicable):
Additional info:
Also noticed this running on Docker as well.
Think it is related to #6253 with too many events causing things to slow down to a crawl, and eventually unresponsive.
This has nothing to do with too many events. I think that something is causing high CPU usage, not sure what it could be.
@balloob When #6369 goes live, are there any specific logs/experiments you'd like if I can replicate?
I'm not using the Z-wave component... so it can't be that for me.
I am using nmap device tracker and/or asus router device tracker. I've tried using only one or the other and the issue persists. Could it be either of those? Anything you want to know from my setup or anything you want me to do?
I turned off both nmap and Asus device trackers and I haven't seen the timer out of sync error in a while.
I spoke too soon. It crashed overnight :(
Same issue. Previously running 0.35.3 which was solid. Reverting now to 0.39.2 to reproduce.
Reproduced within hours. Back to 0.38.4.
@markferry did you use pip to downgrade?
Nope, setup.py. Working from git.
In gdb: #0 0x76f51b30 in __pthread_cond_timedwait (cond=0x3c3f68, mutex=0x3c3f98, abstime=0x7ef0d4a4) at pthread_cond_timedwait.c:199
which I'll admit is not exactly surprising.
Backtrace for all threads:
bt.txt
Almost all waiting on OpenZWave.
0.37.0dev0 lasted longer but still died. Should probably also drop my DB tables before the next run.
Back to 0.36.0dev0 (64800fd).
Died again. Bisected back to 0.36.0.dev0 (c14a5fa) now. If this proves fruitless there's also bisecting the config. What joy.
I'm getting the same issue in a docker as well! It is driving me nuts!
These issues have been resolved. Don't want to create a catch all issue so closing this.
| gharchive/issue | 2017-03-03T00:49:12 | 2025-04-01T06:38:58.213980 | {
"authors": [
"370gt",
"KptnKMan",
"balloob",
"iambdud",
"markferry",
"philhawthorne"
],
"repo": "home-assistant/home-assistant",
"url": "https://github.com/home-assistant/home-assistant/issues/6366",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
243352611 | Flux LED - Scene with multiple platforms cannot be called while Flux controller is powered off
Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.49.0
Python release (python3 --version):
3.5.2
Component/platform:
Flux LED
Description of problem:
When HA starts and the Flux LED device controller is powered off, the error:
ERROR (Thread-1) [homeassistant.components.light.flux_led] Failed to connect to bulb 192.168.0.15, TV LEDs
is shown in the info panel and the light entity is not created.
If this entity is part of a HA Scene with other platforms/entities the scene can no longer be called.
WARNING (MainThread) [homeassistant.helpers.state] reproduce_state: Unable to find entity light.tv_leds ERROR (MainThread) [homeassistant.core] Invalid service data for light.turn_on: two or more values in the same group of exclusion 'Color descriptors' @ data[<Color descriptors>]. Got None
In my configuration the scene in question contains a Hue bulb and a Flux LED strip.
Expected:
The Hue bulb to respond to the scene call while the Flux LED controller is powered off.
Problem-relevant configuration.yaml entries and steps to reproduce:
- platform: hue
host: 192.168.0.150
allow_unreachable: true
- platform: flux_led
devices:
192.168.0.15:
name: TV LEDs
scene.yaml
- name: Warm
entities:
light.lamp:
state: on
brightness: 223
color_temp: 443
xy_color: [ 0.5015, 0.4153 ]
light.tv_leds:
state: on
brightness: 60
rgb_color: [ 255, 123, 9 ]
Start/restart HA with the Flux LED controller powered off.
Call the scene "Warm" either from an automation or the web interface.
Traceback (if applicable):
Additional info:
Prior to version 0.44.0 (approx) the Scene worked as expected with the Flux LED controller powered off.
The Yeelight platform creates the light entity with a state of "unavailable" if HA is started while the controller is powered off. This allows scenes containing other platforms to be successfully used.
You can no longer have color_temp and xy_color in the same setting so try removing one of them from light.lamp.
I removed color_temp which allows the scene to work. Not quite what I expected because my original config above works when the Flux LED controller is powered on and available in HA.
That does sound unexpected. Would you mind double-checking that the color_temp/ xy_color combination really does work in that scenario (with a current HA)? If so, I will try replicating your configuration.
I just double checked and I can confirm that when HA starts with the Flux LED Controller powered off, the Scene with both color_temp and xy_color does not work. When HA starts with the Flux LED Controller powered on the the Scene does work with both keys. By removing either of the keys the Scene works with the Flux LED Controller powered off.
I have tried your scene now, it always fails for me (as expected). However, I only have LIFX to test with.
As I cannot reproduce the inconsistent behavior, I will not try fixing it :)
| gharchive/issue | 2017-07-17T10:26:46 | 2025-04-01T06:38:58.222963 | {
"authors": [
"amelchio",
"rossffs"
],
"repo": "home-assistant/home-assistant",
"url": "https://github.com/home-assistant/home-assistant/issues/8520",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
267808589 | Added website authentication
Description:
Added website authentication so you can also scrape data which is behind a login.
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
- platform: scrape
resource: http://example.com
name: Website-auth-scrape
username: user
password: password
authentication: basic
select: 'h1'
Checklist:
If user exposed functionality or configuration variables are added/changed:
[x ] Documentation added/updated in home-assistant.github.io
If the code communicates with devices, web services, or third-party tools:
[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.
If the code does not interact with devices:
[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.
Hi @ufulu,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!
Isn't this a duplicate of #10079 ?
Duplicate of #10079.
To avoid exactly this, did I link the Pull Request in the forum thread.
| gharchive/pull-request | 2017-10-23T20:35:51 | 2025-04-01T06:38:58.231507 | {
"authors": [
"fabaff",
"fanaticDavid",
"homeassistant",
"ufulu"
],
"repo": "home-assistant/home-assistant",
"url": "https://github.com/home-assistant/home-assistant/pull/10092",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
275252577 | Cast return values and add unit tests.
Description:
Cast return values according to their type returned from yahoo.
Add unit test for yahoo weather component.
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
Checklist:
If user exposed functionality or configuration variables are added/changed:
[ ] Documentation added/updated in home-assistant.github.io
If the code communicates with devices, web services, or third-party tools:
[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.
If the code does not interact with devices:
[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.
Could you write the tests in a way that mocks out the library instead of mocking out the network response and using the library?
@andrey-git I can give it a try. What would be the benefit of that?
Everyone who runs test won't need to install the library. Also the tests will be more hermetic - if library implementation would change without changing the providing API - the tests won't break.
I think you no longer need the json file and can just return whatever values needed in the mock.
@pvizeli maybe the lib should return numeric values in the first place?
@andrey-git what is wrong with have a whole set of data is a separate file instead of small chunks of data inline? Is there a special reason? The json could eventually be reused for testing the yahoo weather sensor component.
I don't feel strongly about this. Lets's wait for @pvizeli as lib author
@fabaff ?
@pvizeli Are you talking about the lib returning numeric values rather than strings?
I added a temporary fix to work around the yahoo weather API issue (#10640).
| gharchive/pull-request | 2017-11-20T06:48:15 | 2025-04-01T06:38:58.240988 | {
"authors": [
"andrey-git",
"cgtobi",
"pvizeli"
],
"repo": "home-assistant/home-assistant",
"url": "https://github.com/home-assistant/home-assistant/pull/10699",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
203874203 | Restore input_* states on startup
Description:
This PR enables HASS to restore the last state of an input_boolean, an input_slider and an input_select on a restart.
This is pretty useful if you have e.g. input booleans or sliders for dynamic settings on your HASS.
Example:
Let's say you have an alarm clock setup with hass. The target time ist set by an input_slider and will now survive a reboot.
The feature is optional and can be set by restore: startup for each entity of the named domains above.
I have chosen 'restore' as the attribute, because you could re-use it for further functionalities/implementations later on (e.g. "reset value after 24hours")
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#1911
Example entry for configuration.yaml (if applicable):
input_boolean:
is_home:
name: 'Is Home'
initial: on
nightmode:
name: 'Alarm Clock enabled'
initial: off
restore: startup
input_select:
radio_channel:
name: 'Radio Channel'
options:
- 'a'
- 'b'
initial: 'a'
icon: 'mdi:import'
restore: startup
input_slider:
alarm_hour:
name: 'Alarm Hour'
icon: 'mdi:timer'
initial: 8
min: 0
max: 23
step: 1
restore: startup
Checklist:
If user exposed functionality or configuration variables are added/changed:
[x] Documentation added/updated in home-assistant.github.io
If the code communicates with devices, web services, or third-party tools:
[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.
If the code does not interact with devices:
[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.
Hi @FREImedia,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!
Duplicate of https://github.com/home-assistant/home-assistant/pull/4614
Hey, sorry the CLA link was wrong, it's now been fixed. Please sign the CLA here.
I am closing this in favor of #4614
| gharchive/pull-request | 2017-01-29T14:51:36 | 2025-04-01T06:38:58.251373 | {
"authors": [
"Danielhiversen",
"FREImedia",
"homeassistant",
"robbiet480"
],
"repo": "home-assistant/home-assistant",
"url": "https://github.com/home-assistant/home-assistant/pull/5622",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
207231759 | Add 'entity_picture' property to DarkSkySensor component
Description:
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):
Checklist:
If user exposed functionality or configuration variables are added/changed:
[ ] Documentation added/updated in home-assistant.github.io
If the code communicates with devices, web services, or third-party tools:
[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.
If the code does not interact with devices:
[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.
Hi @aronsky,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!
I attempted to run tox tests, and had one failure (in the test_darksky.py module, suspicious!) - but this failure seems to happen prior to my changes, as well. Looks like something about a mock load_fixture, which has nothing to do with the changes in this pull request.
I don't think that is a good idea to add base64 icons to code. But I can also not say what the alternative sultion is. I'm not a frontend developer. CC @balloob
@pvizeli I agree that it's not perfect, far from it. I just wanted it to be both self-contained, and not dependent on 3-rd party repositories, which might change and/or disappear at any moment, breaking the module.
I looked around on the Dark Sky website, hoping to find some sort of permalinks to the icons, but their official icons are dynamic and use Javascript - I don't know how to cleanly integrate those into Home Assistant.
If there's a more elegant solution, I'll be happy to do it.
One idea of the weather component was to be able to display the conditions in a visual way. Unfortunately the frontend part is not done yet.
@aronsky Could you use the Skycons library? It's self contained JS, public domain and created for DarkSky. Plus the icons are animated.
https://github.com/darkskyapp/skycons
@rpitera - yep, I saw those icons. They definitely look cool - but integrating them requires changes in the front-end, and without that - I have no idea how a specific module can influence the front-end extensively (and this is required, since the front-end doesn't currently support Javascript-based icons)
I'm btw a big fan of the skycons. We should consider adding those to the frontend.
OK. So, updating the frontend proved to be more complicated than I thought. I have, in fact, made a small patch to the frontend, that would show the state's icon property (instead of the currently used entity_picture). But this behavior is only desirable for weather forecast sensors. Unfortunately, by the time the state arrives to the frontend, there's nothing to differentiate it from other sensors, even other monitored conditions from the weather sensor (such as the temperature, which should display the value, not the icon). As a temporary hack, I enabled this only for sensors that have an icon containing the word weather, but obviously it's not a proper solution.
I ended up doing what @balloob suggested for now, and will try to come up with a more robust solution to the frontend in the future.
Speaking of the frontend, what are the guidelines to making changes to that component, since it compiles into files that are part of this repo? Do I make a pull request in the frontend's repository, and once it is accepted, compile and make a pull request here?
You just make PRs against the frontend repo. I add new builds from frontend to this repo.
Please add your images in a subfolder under images.
Also a heads up that this is the last change that we will allow for the darksky sensor. Future efforts will have to be focussed on the weather component. This sensor will be removed in a future release.
I had no idea there's a weather component in the works - I didn't see anything in the documentation. I'll look into it (it does make sense to have those unified somehow, as opposed to different sensors with different images and weather states).
I'll move the images to a subfolder.
And finally, regarding the frontend repo. I understand that this might be a headache to keep track of, but any chance you can tag frontend commits with versions matching the home-assistant tags that use those commits? It's a lot less clear on which version to work on in that repo.
Every Home Assistant commit already contains a version of Home Assistant Polymer via a submodule: https://github.com/home-assistant/home-assistant/tree/dev/homeassistant/components/frontend/www_static
That being said, you still always have to work on the latest version no matter what commit it is based off.
Can you remove the png versions since they are not being used ?
You also broke the tests.
Hello @aronsky,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:
01f346ccee1f62f354b0ee239ee9c42c38a43437 - No email found attached to the commit.
b2cbde31945d9bf0e9ccc87c3e9259da781cde1a - No email found attached to the commit.
Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:
If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.
If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.
If you only made a single commit you should be able to rungit commit --amend --author="Author Name <email@address.com>"
(substituting Author Name and email@address.com for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:
You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.
Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.
We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:
Hello @aronsky,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:
01f346ccee1f62f354b0ee239ee9c42c38a43437 - No email found attached to the commit.
b2cbde31945d9bf0e9ccc87c3e9259da781cde1a - No email found attached to the commit.
Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:
If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.
If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.
If you only made a single commit you should be able to rungit commit --amend --author="Author Name <email@address.com>"
(substituting Author Name and email@address.com for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:
You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.
Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.
We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:
I'm not sure what broke the build... Any chance it has been broken in the dev branch that I merged into my code? It seems like it, because that's the first commit that seems to break the build. I merged the current dev branch, and hopefully it'll work - I'm not on my work computer, and can't run tox from here. If it still fails, it'll have to wait until tomorrow.
P.S. Sorry for the mess with the commits without e-mail addresses, I haven't used my home computer for development before, and didn't notice that git hasn't had an e-mail set up.
Seeing that this is using a subfolder of SVG icons, would this support putting in your own SVG icons as long as the naming matched the DarkSky naming conventions? Also, if you replaced them, would they get overwritten on subsequent HA updates? I'm assuming no, since this will be the final update (barring hot-fixes of course) allowed for this platform.
@rpitera yes, if this pull request is accepted, you'll be able to switch to your own SVGs, as long as you replace the files (i.e., the names match). Your assumption about the subsequent updates sounds correct to me, but your guess is as good as mine in that regard.
Thanks!
It seems that you have added some commits to your branch unrelated to this change. Please clean it up.
Hi @balloob, I'm not sure which commits you're referring to. There were a couple of commits I've pushed without properly signing them with my email, and I had to do some git history rewriting to fix that. Other than that, there are only commits relevant to the change, and the merges from dev I did from time to time to stay up to date with the code. If that's not something I should've done, I'll avoid it in the future, but at this point I don't know how to unravel those merges - and not sure how critical it is, since those are all commits accepted into the dev branch, anyway.
Do you prefer that I redo my changes in a separate, clean pull request, and abandon this one?
Have a look at commits or files changed to see what I mean:
Yup, that's the mess with the authoring I referred to previously, sorry about that. I'm not sure how to fix that properly - if I start afresh, rebase my dev branch on the original commit where it diverged from the upstream repo, cherry-pick the commits with my changes, and then push - will it clean everything up and avoid the need for a new pull request?
Again, sorry about the mess.
Yes, that will work. You will have to force-push to overwrite the bad commits in your current branch.
To be safe, you can also create a new branch that branches off latest dev and cherry-pick your changes.
That sounds like the best idea. Will there be an option to update this pull request to point to the new branch, or do I check its correctness and then force-push it onto the current branch in question?
Can't change the source branch. It will be easiest to just close this PR and open a new one.
I'll do that. Once again, sorry about the mess with the branches and stuff. The new pull request, #6141, is just one clean commit :)
| gharchive/pull-request | 2017-02-13T14:22:19 | 2025-04-01T06:38:58.288355 | {
"authors": [
"aronsky",
"balloob",
"fabaff",
"homeassistant",
"pvizeli",
"rpitera"
],
"repo": "home-assistant/home-assistant",
"url": "https://github.com/home-assistant/home-assistant/pull/5948",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
233001470 | Updated pyhomematic
Description:
Updating pyhomematic dependency to fix wired devices.
Related issue (if applicable): fixes #7708
@danielperna84 you are allowed to merge dependency upgrade PRs yourself 👍
| gharchive/pull-request | 2017-06-01T20:31:46 | 2025-04-01T06:38:58.291219 | {
"authors": [
"balloob",
"danielperna84"
],
"repo": "home-assistant/home-assistant",
"url": "https://github.com/home-assistant/home-assistant/pull/7861",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2443320405 | Add some more light control sentences
Fix #2319
Summary by CodeRabbit
New Features
Introduced new commands for controlling lights, allowing users to specify actions like turning lights off or on in designated areas, as well as flexible phrasing without area specifications.
Tests
Added test cases to ensure the system recognizes new phrases for turning lights off and on, enhancing the robustness of the natural language processing for lighting commands.
Looks good
| gharchive/pull-request | 2024-08-01T20:09:00 | 2025-04-01T06:38:58.293601 | {
"authors": [
"TheFes",
"tetele"
],
"repo": "home-assistant/intents",
"url": "https://github.com/home-assistant/intents/pull/2362",
"license": "CC-BY-4.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1275431083 | Compile a fast LP solver to Wasm
The best LP solvers such as CBC or Highs are written in C/C++. So if we want to use them in our project (#508), we need to compile them in Wasm using emscripten. Nick made some progress on this.
This is great. Has it improved the performance of the layout algorithm?
To be determined, there are some issues to address with layout tests that currently depend on minilp to address before we can move to good_lp+highs.
Thanks Chiara. So is this new solver currently being used in the production
layout code?
On Fri, 29 Jul 2022, 14:38 Chiara Sarti, @.***> wrote:
To be determined, there are some issues to address with layout tests that
currently depend on minilp to address before we can move to good_lp+highs.
—
Reply to this email directly, view it on GitHub
https://github.com/homotopy-io/homotopy-rs/issues/509#issuecomment-1199297520,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACQ4OHUO6U3OZYEJLXGFCMTVWPNFTANCNFSM5ZDK2OMQ
.
You are receiving this because you commented.Message ID:
@.***>
Not yet, but the idea is to either use this solver only for production or to just bin the tests altogether.
I think @calintat is the best position to figure out what to do on this front, but once that is sorted moving to highs should be relatively straightforward.
| gharchive/issue | 2022-06-17T20:31:21 | 2025-04-01T06:38:58.345769 | {
"authors": [
"calintat",
"jamievicary",
"regular-citizen"
],
"repo": "homotopy-io/homotopy-rs",
"url": "https://github.com/homotopy-io/homotopy-rs/issues/509",
"license": "BSD-3-Clause",
"license_type": "permissive",
"license_source": "github-api"
} |
961332621 | Flutter run error: Could not complete submission of dSYM
I meet this issue when I am trying running the code to deploy in my iPhone.
Here is the detail info:
Project /Users/dadachen/workspace/FEhViewer built and packaged successfully.
Uploading dsym file
error: Could not complete submission of dSYM at
/Users/dadachen/workspace/FEhViewer/build/ios/Debug-iphoneos/fehviewer.app.d
SYM: Error Domain=com.crashlytics.mac.error-domain.process-dsym Code=2 "File
no longer exists at (null)" UserInfo={NSLocalizedFailureReason=File no
longer exists at (null)}
Command PhaseScriptExecution failed with a nonzero exit code
note: Using new build system
note: Building targets in parallel
note: Planning build
note: Analyzing workspace
note: Constructing build description
note: Build preparation complete
Could not build the precompiled application for the device.
I do not have any ideas of that. Could you give me a help?
I have replaced the google firebase plist with mine. So can I do something to solve this?
You can try to configure Runner.xcodeproj in xcode. left click on TARGETS, Runner, right select Build Phases ,
expand Run Script,
comment out this line
"${PODS_ROOT}/FirebaseCrashlytics/upload-symbols" -gsp ${GOOGLESERVICE_INFO_LOCATION} -p ios "${DWARF_DSYM_FOLDER_PATH}/${DWARF_DSYM_ FILE_NAME}"
There may be something wrong with this script, I'll try to fix it
It works for me. Thank you so much! ☺️
| gharchive/issue | 2021-08-05T01:49:44 | 2025-04-01T06:38:58.356593 | {
"authors": [
"coda1997",
"honjow"
],
"repo": "honjow/FEhViewer",
"url": "https://github.com/honjow/FEhViewer/issues/7",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
2381775463 | Add documentation on how to use HonoX outside of Cloudflare
What is the feature you are proposing?
Projects created by selecting x-basic with npm create hono@latest support Cloudflare Workers & Pages, but it would be beneficial to have documentation on how to adapt the code to run on other platforms.
I don't think this is currently possible as the Vite plugin built into HonoX is only adapted for Cloudflare Pages.
There was some discussion on this in #42 where someone built their own plugin. If not, I'm not sure if it would be helpful, but Cloudflare have open-sourced the runtime for their Workers (https://github.com/cloudflare/workerd) so if you're looking to self-host, that might be helpful.
Hi.
You can run the HonoX app on other runtimes like Node.js and Bun instead of Cloudflare/workerd. To do it, you must build your app with the proper Vite settings. It would be good if the setting were written in the README.
| gharchive/issue | 2024-06-29T14:16:12 | 2025-04-01T06:38:58.359265 | {
"authors": [
"3w36zj6",
"chrisyalamov",
"yusukebe"
],
"repo": "honojs/honox",
"url": "https://github.com/honojs/honox/issues/197",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
824270323 | 多个主机名相同时设置解析
在DNS服务器中为同一个主机记录配置多个IP地址，在应答DNS查询时，所有IP地址按照预先设置的权重进行返回不同的解析结果，将解析流量分配到不同的服务器上，从而达到负载均衡的目的。
那么如何指定修改某个记录的IP呢
not a DDNS designed usage?
| gharchive/issue | 2021-03-08T07:31:55 | 2025-04-01T06:38:58.360742 | {
"authors": [
"Dreamupers",
"honwen"
],
"repo": "honwen/aliyun-ddns-cli",
"url": "https://github.com/honwen/aliyun-ddns-cli/issues/46",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
906692824 | Bug: lualine goes blank after calling NvimTreeToggle
Self Checks
[X] I'm using the latest lualine and neovim nightly.
[X] I didn't find the issue in exsisting issues or prs.
How to reproduce the problem
install both nvim-tree and lualine plugins.
open a file in nvim.
call :NvimTreeToggle.
lualine gets into the tree buffer.
call :NvimTreeToggle again.
lualine shows blank in current buffer.
Actual behaviour
lualine goes blank.
Expected behaviour
lualine should appears again after toggle nvimtree.
Aditional information
Minimal config to reproduce the issue
Config
This happens if any buffer where lualine is deactivated is focused and gets closed while focused.
@dragondove Which colorscheme are you using?
@dragondove Which colorscheme are you using?
I'm using zephyr . Does it relate to this issue? The config of lualine I used is from evil_lualine.
what's most likely happening is the active status isn't being enabled due to none of the event we look for being triggured
We probably need aditional event to catch this case here:
https://github.com/hoob3rt/lualine.nvim/blob/9726824f1dcc8907632bc7c32f9882f26340f815/lua/lualine/init.lua#L173
@dragondove evil_lualine doesn't configure inactive_status that's why you're probably seeing lualine disapear . Does leaving the window and entering it again bring back lualine ?
what's most likely happening is the active status isn't being enabled due to none of the event we look for being triggured
We probably need aditional event to catch this case here:
https://github.com/hoob3rt/lualine.nvim/blob/9726824f1dcc8907632bc7c32f9882f26340f815/lua/lualine/init.lua#L173
@dragondove evil_lualine doesn't configure inactive_status that's why you're probably seeing lualine disapear . Does leaving the window and entering it again bring back lualine ?
yes, If I firstly switch to the editing buffer(By C-w w), lualine will be there.
It seems this bug disapears, but I don't know why, maybe it is caused by a specific version of neovim. Anyway, it works fine now.
| gharchive/issue | 2021-05-30T09:20:22 | 2025-04-01T06:38:58.368405 | {
"authors": [
"dragondove",
"ful1e5",
"oblitum",
"shadmansaleh"
],
"repo": "hoob3rt/lualine.nvim",
"url": "https://github.com/hoob3rt/lualine.nvim/issues/268",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2443886172 | 🛑 FWAw is down
In 5b3d6b9, FWAw ($FWA_SITE) was down:
HTTP code: 0
Response time: 0 ms
Resolved: FWAw is back up in d51ca66 after 24 minutes.
| gharchive/issue | 2024-08-02T02:52:21 | 2025-04-01T06:38:58.392707 | {
"authors": [
"hoopybe"
],
"repo": "hoopybe/uptime",
"url": "https://github.com/hoopybe/uptime/issues/1363",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1344613152 | 뷰어 페이지에 파일 상세정보 표시하는 옵션 추가
왼쪽 상단이나 뭐 그런 곳?
[ ] 이미지가 해당 위치까지 침범할 경우 자동숨김 (마우스 커서를 움직이면 표시)
[ ] 투명도 조절
취소 ㅜ.ㅜ
| gharchive/issue | 2022-08-19T15:50:08 | 2025-04-01T06:38:58.403715 | {
"authors": [
"hoppang"
],
"repo": "hoppang/purpleeye",
"url": "https://github.com/hoppang/purpleeye/issues/44",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
377958740 | [HOPS-808] Fix performance degradation due to safemode and enable nam…
…enode resource monitoring
Make sure there is no duplicate PR for this issue
Please check if the PR fulfills these requirements
[ ] Tests for the changes have been added and passed (for bug fixes / features)
[x] HOPS JIRA issue has been opened for this PR
[x] All commits have been squashed down to a single commit
[x] The commit message has the following format: [HOPS-XXX] message
Post a link to the associated JIRA issue
https://hopshadoop.atlassian.net/browse/HOPS-808
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information:
https://github.com/hopshadoop/hops-metadata-dal/pull/137
https://github.com/hopshadoop/hops-metadata-dal-impl-ndb/pull/170
Can one of the admins verify this patch?
@berthoug i was benchmarking hopsFS with 4 namenodes and i found that my solution for avoiding reading the safemode variable from the database at every request only works for one namenode. So i fixed this one, and pushed it.
There is some errors in this pull request (ex: "<<<<HEAD" ;) ) and I think I identified some potential bugs. I fixed them in the following pull request #580.
| gharchive/pull-request | 2018-11-06T17:39:38 | 2025-04-01T06:38:58.431489 | {
"authors": [
"HopsworksJenkins",
"berthoug",
"maismail"
],
"repo": "hopshadoop/hops",
"url": "https://github.com/hopshadoop/hops/pull/568",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
695915734 | Removed isEqualNode comparison
Proposal to fix https://github.com/hopsoft/cable_ready/issues/70
I think we should retain the isEqualNode check for performance reasons; however, I'd be ok to skip this check for SELECT and OPTION elements. @adank92 Do you think this compromise would address the problems you faced in #70?
That is a clever suggestion, if the issue is restricted to just select/option.
@hopsoft @leastbad that would work for the first issue, but for the second one we would also need to skip INPUT
Talk to me like I'm distracted and less confident... what is it about form elements that they need special care? Is it because the user can change their state?
Should TEXTAREA be added to the list?
Are there others we're not thinking about because "nobody" ever uses them?
What are the gotchas? eg. what about the input type="numeric" that is forced to display the value abc, putting it in violation of the half-baked pattern validation built into some elements? is "equal but not valid" something that matters in this context? I'm just trying to brainstorm and still feeling haunted by the abstract thinking required to get to an outcome on https://github.com/patrick-steele-idem/morphdom/pull/206
Talk to me like I'm distracted and less confident... what is it about form elements that they need special care? Is it because the user can change their state?
SELECT elements need to have one option with the selected attribute set in order for morphdom to work as expected. The library will ensure this by running code to sync the attribute (syncBooleanAttrProp(fromEl, toEl, "selected");). Using isEqualNode prevents this from happening. This is explained more in detail in the original issue #70
INPUT elements do not update their value attribute in the HTML definition when users type in it. If the page is loaded with an empty input, the user types in something, and then the backend returns an empty input again, ìsEqualNode will always return true because both HTML elements are still the same.
Should TEXTAREA be added to the list?
Yes, TEXTAREA has the same issue as INPUT. If we want to retain isEqualNode, it should be skipped too.
Are there others we're not thinking about because "nobody" ever uses them?
There might be others but I can only confirm these 3 elements. I don't think the other form elements in this list would have issues https://www.w3schools.com/html/html_form_elements.asp. But then again, there's a reason why morphdom doesn't use isEqualNode.
What are the gotchas? eg. what about the input type="numeric" that is forced to display the value abc, putting it in violation of the half-baked pattern validation built into some elements? is "equal but not valid" something that matters in this context? I'm just trying to brainstorm and still feeling haunted by the abstract thinking required to get to an outcome on patrick-steele-idem/morphdom#206
Numeric inputs suffer from the same issue, their values are not updated if changed in the backend. I've tested it without isEqualNode and it works fine. If the backend clears the value, the UI clears it. If the backend changes the number, the UI changes it. And if the backend changes the value to a string, the UI just clears the value out.
Interestingly, in my testing with a draft PR that doesn't use isEqualNode if the tagName is an input/select/textarea...
I am finding that it's not select that is the problem, but option. So far as I can tell, @adank92's first MCVE works fine if I filter for option but still breaks if I filter for select.
Does that make sense to you, Adan?
Works:
if (fromEl.tagName != 'OPTION' && fromEl.isEqualNode(toEl)) return false
Doesn't work:
if (fromEl.tagName != 'SELECT' && fromEl.isEqualNode(toEl)) return false
I was/am worried that this bug will impact DATALIST elements as well, but if indeed it's the OPTION that is relevant, this could kill two birds with one stone.
Yes, you are right. select itself is not a problem, it's option. Since morphdom can't find an option with a selected attribute, it ends up resetting the select.
Thanks for taking care of it in a new PR.
| gharchive/pull-request | 2020-09-08T14:21:25 | 2025-04-01T06:38:58.444030 | {
"authors": [
"adank92",
"hopsoft",
"leastbad"
],
"repo": "hopsoft/cable_ready",
"url": "https://github.com/hopsoft/cable_ready/pull/71",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1068483091 | CB-15245:Fix NPE in create-aws-cluster when encryption type set to null
Master PR: https://github.com/hortonworks/cloudbreak/pull/11840/files
2.49 PR: https://github.com/hortonworks/cloudbreak/pull/11841
I think this PR should be closed, and so should #11841. The right solution is to
Repurpose #11840 for CB-2.49.0 (rebase the branch, force push, then change the target branch with the Edit button).
Once #11840 gets merged, open a merge PR for CB-2.49.0 -> CB-2.50.0.
Once the latter PR is merged, open another merge PR for CB-2.50.0 -> master (2.51).
Please follow the merge process mentioned (here)[https://github.com/hortonworks/cloudbreak/pull/11809#pullrequestreview-814882747] and here.
I think this PR should be closed, and so should #11841. The right solution is to
Repurpose CB-15245:Fix NPE in create-aws-cluster when encryption type set to null #11840 for CB-2.49.0 (rebase the branch, force push, then change the target branch with the Edit button).
Once CB-15245:Fix NPE in create-aws-cluster when encryption type set to null #11840 gets merged, open a merge PR for CB-2.49.0 -> CB-2.50.0, using a feature branch based off CB-2.50.0.
Once the latter PR is merged, open another merge PR for CB-2.50.0 -> master (2.51), using a feature branch based off master.
Please follow the merge process mentioned here and here.
Changed the target branch for master PR to CB-2.50.0, and we are skipping the merge to 2.49 as discussed in https://jira.cloudera.com/browse/CB-15245?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel. Once the 2.50 PR is merged , will port that change to master.
| gharchive/pull-request | 2021-12-01T14:35:51 | 2025-04-01T06:38:58.467999 | {
"authors": [
"lajosrodek",
"satyabollineni"
],
"repo": "hortonworks/cloudbreak",
"url": "https://github.com/hortonworks/cloudbreak/pull/11842",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
1176970855 | CB-16388 RDSConfig calculation take long time, refactor the RdsConfig select by clusterId
The rds config fetch is too expensive because the hibernate fetch all of the attached clusters as references.
This is a backport from 2.55.0
@topolyai5 can you check why CI jobs seem stucked?
@lajosrodek @topolyai5 what's the status of this PR? is this still targeted to 2.54? if yes, please either resolve comments or modify the change accordingly
| gharchive/pull-request | 2022-03-22T15:37:16 | 2025-04-01T06:38:58.469772 | {
"authors": [
"horadla23",
"topolyai5"
],
"repo": "hortonworks/cloudbreak",
"url": "https://github.com/hortonworks/cloudbreak/pull/12476",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
621255694 | DISTX-421 DISTX-427 Recommendation for host groups' scalability
Added recommendations for auto-scalability and manual scalability.
Implemented both CM service based recommendations and fallback recommendations.
./gradlew build
ping @keyki
Thanks @bergerdenes for taking a look. I have addressed those comments.
@bergerdenes could you please merge this?
Merged
| gharchive/pull-request | 2020-05-19T20:14:36 | 2025-04-01T06:38:58.471837 | {
"authors": [
"bergerdenes",
"cegganesh84"
],
"repo": "hortonworks/cloudbreak",
"url": "https://github.com/hortonworks/cloudbreak/pull/8100",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
159141961 | Permission with fragment @NeedsPermission method never called
Hello,
I have a very simple application using the PermissionsDispatcher. The main activity contains a fragment annotated with @RuntimePermissions.
When I run the application on the emulator, the dialog are displayed but my method is never called.
The project has the following configurations:
minSdkVersion: 16
targetSdkVersion: 23
The generated code look like that:
final class MessageListPermissionsDispatcher {
private static final int REQUEST_ONSTARTLOADERLIST = 0;
private static final String[] PERMISSION_ONSTARTLOADERLIST = new String[] {"android.permission.READ_SMS","android.permission.READ_CONTACTS","android.permission.RECEIVE_SMS","android.permission.BROADCAST_SMS"};
private static GrantableRequest PENDING_ONSTARTLOADERLIST;
private MessageListPermissionsDispatcher() {
}
static void onStartLoaderListWithCheck(MessageList target, View view, Bundle savedInstanceState) {
if (PermissionUtils.hasSelfPermissions(target.getActivity(), PERMISSION_ONSTARTLOADERLIST)) {
target.onStartLoaderList(view, savedInstanceState);
} else {
PENDING_ONSTARTLOADERLIST = new OnStartLoaderListPermissionRequest(target, view, savedInstanceState);
if (PermissionUtils.shouldShowRequestPermissionRationale(target.getActivity(), PERMISSION_ONSTARTLOADERLIST)) {
target.showRationaleList(PENDING_ONSTARTLOADERLIST);
} else {
target.requestPermissions(PERMISSION_ONSTARTLOADERLIST, REQUEST_ONSTARTLOADERLIST);
}
}
}
static void onRequestPermissionsResult(MessageList target, int requestCode, int[] grantResults) {
switch (requestCode) {
case REQUEST_ONSTARTLOADERLIST:
if (PermissionUtils.getTargetSdkVersion(target.getActivity()) < 23 && !PermissionUtils.hasSelfPermissions(target.getActivity(), PERMISSION_ONSTARTLOADERLIST)) {
target.showDeniedForList();
return;
}
if (PermissionUtils.verifyPermissions(grantResults)) {
if (PENDING_ONSTARTLOADERLIST != null) {
PENDING_ONSTARTLOADERLIST.grant();
}
} else {
if (!PermissionUtils.shouldShowRequestPermissionRationale(target.getActivity(), PERMISSION_ONSTARTLOADERLIST)) {
target.showNeverAskForList();
} else {
target.showDeniedForList();
}
}
PENDING_ONSTARTLOADERLIST = null;
break;
default:
break;
}
}
private static final class OnStartLoaderListPermissionRequest implements GrantableRequest {
private final WeakReference<MessageList> weakTarget;
private final View view;
private final Bundle savedInstanceState;
private OnStartLoaderListPermissionRequest(MessageList target, View view, Bundle savedInstanceState) {
this.weakTarget = new WeakReference<>(target);
this.view = view;
this.savedInstanceState = savedInstanceState;
}
@Override
public void proceed() {
MessageList target = weakTarget.get();
if (target == null) return;
target.requestPermissions(PERMISSION_ONSTARTLOADERLIST, REQUEST_ONSTARTLOADERLIST);
}
@Override
public void cancel() {
MessageList target = weakTarget.get();
if (target == null) return;
target.showDeniedForList();
}
@Override
public void grant() {
MessageList target = weakTarget.get();
if (target == null) return;
target.onStartLoaderList(view, savedInstanceState);
}
}
}
Could you give us a sample prj?
The sample is compiled with android studio.
MyApplication3.zip
You miss implmenting onRequestPermissionsResult
@Override
public void onRequestPermissionsResult(int requestCode, String[] permissions, int[] grantResults) {
super.onRequestPermissionsResult(requestCode, permissions, grantResults);
MessageListPermissionsDispatcher.onRequestPermissionsResult(this, requestCode, grantResults);
}
https://github.com/hotchemi/PermissionsDispatcher#2-delegate-to-generated-class
BTW, you don't need to do following
if (android.os.Build.VERSION.SDK_INT >= Build.VERSION_CODES.M) {
MessageListPermissionsDispatcher.onStartLoaderListWithCheck(this, view, savedInstanceState);
} else {
onStartLoaderList(view, savedInstanceState);
}
just call withCheck method.
@Nullable
@Override
public View onCreateView(final LayoutInflater inflater, final ViewGroup container, final Bundle savedInstanceState) {
View view = inflater.inflate(R.layout.fragment_layout, container, false);
MessageListPermissionsDispatcher.onStartLoaderListWithCheck(this, view, savedInstanceState);
return view;
}
https://github.com/hotchemi/PermissionsDispatcher/issues/157#issuecomment-224774837
| gharchive/issue | 2016-06-08T11:33:50 | 2025-04-01T06:38:58.494821 | {
"authors": [
"Bathilde",
"hotchemi",
"shiraji"
],
"repo": "hotchemi/PermissionsDispatcher",
"url": "https://github.com/hotchemi/PermissionsDispatcher/issues/157",
"license": "apache-2.0",
"license_type": "permissive",
"license_source": "bigquery"
} |
2183665664 | Pick and Save Not Enabled & Order Items Invisible
Current behavior
Currently, there are two critical issues affecting our system:
Pick and Save Buttons Not Enabled: The Pick and Save buttons are not enabled in the app.
Order Items Invisible in Fulfilment App: Additionally, the order items are not visible in the fulfilment application. As a result, we are unable to fulfill orders promptly.
We tested this issue for order ID : SVC13094 in adoc-sv-oms
Expected behavior
The Pick and Save buttons should be enabled, allowing our team to efficiently manage orders.
Order items should be visible within the fulfilment application to facilitate accurate order processing.
This issues is due the dependency on OMS. The recent changes related to internationalInvoiceUrl (Custom document generation) were part of OMS 5.5.1 release. So in order to get it fix on adoc-sv-oms, need to be upgraded to 5.5.1.
| gharchive/issue | 2024-03-13T10:40:03 | 2025-04-01T06:38:58.502174 | {
"authors": [
"khushalidube-hwsys",
"ravilodhi"
],
"repo": "hotwax/fulfillment-pwa",
"url": "https://github.com/hotwax/fulfillment-pwa/issues/454",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
775150352 | Make Autoloading more robust
Duplicate of #3
Modifies the stimulus/loaders/autoloader module to account for module
importing in 4 different scenarios:
Immediately when parsed
Whenever elements that declare [data-controller] are added,
deleted, or modified (via a MutationObserver)
Whenever the DOMContentLoaded event fires (for applications that
don't depend on turbo
Whenever the turbo:load event fires (for applications that do
depend on turbo
In addition to autoloading in more scenarios, this commit also changes
the autoloader to read controller tokens in a spacing-agnostic manner,
and to transform dasherized controller names (like
message-rendering) to underscored file names (like
message_rendering_controller.js).
The changes made to test/dummy were done so manually, and are being
checked into version control. In an ideal set up, the generator would be
run for every System Test, and then reverted.
Testing
Add System Test level coverage to ensure that the configurations,
helpers, and autoloading work together in concert to dynamically load
Stimulus Controllers.
To do so, add a Gemfile-level dependency on capybara, webdrivers,
and selenium-webdrivers.
Co-authored-by: Justin Malčić j.malcic@me.com
Thanks for the review @MarkoZabcic! I've added you as a co-author to the commit.
Thanks for the review @MarkoZabcic! I've added you as a co-author to the commit.
Plan is still to extract the bulk of this into stimulus, but at least we're not broken in the meanwhile!
Plan is still to extract the bulk of this into stimulus, but at least we're not broken in the meanwhile!
| gharchive/pull-request | 2020-12-28T01:56:22 | 2025-04-01T06:38:58.509239 | {
"authors": [
"dhh",
"seanpdoyle"
],
"repo": "hotwired/stimulus-rails",
"url": "https://github.com/hotwired/stimulus-rails/pull/11",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2313333700 | Upgrade the croc version
croc is not compatible with older versions after upgrading to version 10.0
v9.6.16 was a breaking change so I have re-released it as v10.0.0 to signal that. clients must be >=v9.6.16 or >=v10 to be compatible.
I updated it. Usually takes a week to show up in fdroid.
Can a standalone apk file be provided?
I added an APK to the release.
| gharchive/issue | 2024-05-23T16:15:10 | 2025-04-01T06:38:58.520079 | {
"authors": [
"TJNOV",
"howeyc"
],
"repo": "howeyc/crocgui",
"url": "https://github.com/howeyc/crocgui/issues/46",
"license": "ISC",
"license_type": "permissive",
"license_source": "github-api"
} |
394422581 | 建议取消页面转码的注释，并添加ignore，忽略非法字符
gb2312 编码的网页会存在问题
#request.py
import chardet
#line 121
#res_data = await resp.text()
content = await resp.read()
charset = chardet.detect(content)
res_data = content.decode(charset['encoding'], 'ignore')
@sugarguo
你好，为什么取消是因为这是一个轻量的框架，不想过多依赖第三方库，对于编码问题，你可以:
利用read()方法获取字节进行解码
或者我另外开一个关于编码的ruia插件 ruia-cchardet
我这边提供一个编码参数，你那边使用的时候，比如gb2312，直接传encoding = gb2312，这边帮你解码
你觉得哪种方案比较好
| gharchive/issue | 2018-12-27T15:29:06 | 2025-04-01T06:38:58.522018 | {
"authors": [
"howie6879",
"sugarguo"
],
"repo": "howie6879/ruia",
"url": "https://github.com/howie6879/ruia/issues/10",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
704791241 | 关于onebot生态应用案例的补充
这是我写的一个基于Nonebot的QQ群机器人，它叫FG，最具特色的功能是使用机器学习算法提取聊天关键词。目前有两个分支，一个是主分支，只有提取关键词功能，另外一个分支是为某科幻群定制的版本，这个版本功能更加丰富，可以欢迎新人，微软小冰（支持文字/图片）智能聊天引擎的接入等～目前正考虑将微软小冰的特性接入主分支。
目前在Github获得17个star，望能补充进应用案例模块～
项目主页：https://github.com/mgsky1/FG
主分支：https://github.com/mgsky1/FG/tree/mirai
某科幻群的定制分支：https://github.com/mgsky1/FG/tree/hhx_mirai
效果图：
直接按原格式提个 pull request 吧
直接按原格式提个 pull request 吧
已提交PR
| gharchive/issue | 2020-09-19T03:26:39 | 2025-04-01T06:38:58.526166 | {
"authors": [
"mgsky1",
"richardchien"
],
"repo": "howmanybots/onebot",
"url": "https://github.com/howmanybots/onebot/issues/22",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
344427786 | add count of pending users
Issue #335
Description
Add a scope for pending users in model
Add the counter in view
Testing steps
Explain how to test your PR manually
Step 1
Step 2
Step 3
Features PR URL
PR #ID
Checklist
Make sure that all steps a checked before the merge
[ ] RSpec tests are passing on CI
[ ] Cucumber features are passing localy
[ ] bin/cop -a does not return any warnings
[ ] Tested manually
Screenshots
Provide screenshots of implemented functionality
Что здесь можно тестровать? Вьюху? Или скоуп?
@Mehonoshin Можно проверять. Да, своего скоупа не нужно, в модели уже был нужный метод.
билд упал, надо фичи поправить
| gharchive/pull-request | 2018-07-25T12:44:24 | 2025-04-01T06:38:58.530481 | {
"authors": [
"Hunk13",
"Mehonoshin"
],
"repo": "howtohireme/give-me-poc",
"url": "https://github.com/howtohireme/give-me-poc/pull/339",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
1879769273 | [BUG]: pretraining llama-2-70b get unknowen error
🐛 Describe the bug
我按照教程做llama-2-70的预训练，修改了gemini.sh，运行出现了下面的错误
self.layers = nn.ModuleList([LlamaDecoderLayer(config) for _ in range(config.num_hidden_layers)])
File "/usr/local/anaconda/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 380, in __init__
self.self_attn = LlamaAttention(config=config)
File "/usr/local/anaconda/lib/python3.10/site-packages/transformers/models/llama/modeling_llama.py", line 255, in __init__
self.q_proj = nn.Linear(self.hidden_size, self.num_heads * self.head_dim, bias=False)
File "/usr/local/anaconda/lib/python3.10/site-packages/torch/nn/modules/linear.py", line 101, in __init__
self.reset_parameters()
File "/usr/local/anaconda/lib/python3.10/site-packages/torch/nn/modules/linear.py", line 107, in reset_parameters
init.kaiming_uniform_(self.weight, a=math.sqrt(5))
File "/usr/local/anaconda/lib/python3.10/site-packages/torch/nn/init.py", line 396, in kaiming_uniform_
return torch.overrides.handle_torch_function(
File "/usr/local/anaconda/lib/python3.10/site-packages/torch/overrides.py", line 1551, in handle_torch_function
result = torch_func_method(public_api, types, args, kwargs)
File "/usr/local/anaconda/lib/python3.10/site-packages/colossalai/lazy/lazy_init.py", line 324, in __torch_function__
o = func(*tree_map(unwrap, args), **tree_map(unwrap, kwargs))
File "/usr/local/anaconda/lib/python3.10/site-packages/torch/nn/init.py", line 396, in kaiming_uniform_
return torch.overrides.handle_torch_function(
File "/usr/local/anaconda/lib/python3.10/site-packages/torch/overrides.py", line 1551, in handle_torch_function
result = torch_func_method(public_api, types, args, kwargs)
File "/usr/local/anaconda/lib/python3.10/site-packages/torch/_tensor.py", line 1295, in __torch_function__
ret = func(*args, **kwargs)
File "/usr/local/anaconda/lib/python3.10/site-packages/torch/nn/init.py", line 412, in kaiming_uniform_
return tensor.uniform_(-bound, bound)
File "/usr/local/anaconda/lib/python3.10/site-packages/colossalai/_analyzer/_subclasses/meta_tensor.py", line 113, in __torch_dispatch__
ret = func(*args, **kwargs)
File "/usr/local/anaconda/lib/python3.10/site-packages/torch/_ops.py", line 287, in __call__
return self._op(*args, **kwargs or {})
File "/usr/local/anaconda/lib/python3.10/site-packages/torch/_decomp/decompositions.py", line 1958, in uniform_
return self.copy_((high - low) * torch.rand_like(self) + low)
File "/usr/local/anaconda/lib/python3.10/site-packages/colossalai/lazy/lazy_init.py", line 476, in wrapper
return self.tensor_cls(orig_target, *args[1:], device=orig_t.device, dtype=orig_t.dtype, **kwargs)
File "/usr/local/anaconda/lib/python3.10/site-packages/colossalai/lazy/lazy_init.py", line 163, in __new__
elem = func(*args, **{**kwargs, 'device': 'meta'})
Environment
python3.10
torch2.0
cuda11.2
运行脚本
colossalai run --nproc_per_node 8 pretrain.py -c 70b -g -x fp16 -b 2 -d /path/to/RedPajama-Data-1T-Sample
您好，请问有完整的报错信息吗，traceback的报错好像缺了最后的部分？
我搜了issue，是因为不支持torch2.0
所以我降级到了pytorch 1.13.1+cu117，但是仍然跑不起来，这次是因为OOM
我是单机8卡跑的，A100 40G
运行脚本
colossalai run --nproc_per_node 8 pretrain.py -a -c 70b -g -x fp16 -p gemini_auto -b 1 -d RedPajama-Data-1T-Sample
adjust the batch size or model configuration to fit within the memory constraints
TypeError File "/usr/local/lib/python3.10/dist-packages/colossalai/lazy/lazy_init.py", line 163, in new
: rand() received an invalid combination of arguments - got (dtype=torch.dtype, device=str, ), but expected one of:
(tuple of ints size, *, torch.Generator generator, tuple of names names, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)
(tuple of ints size, *, torch.Generator generator, Tensor out, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)
(tuple of ints size, *, Tensor out, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)
(tuple of ints size, *, tuple of names names, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)
elem = func(*args, **{**kwargs, 'device': 'meta'})
TypeError: rand() received an invalid combination of arguments - got (dtype=torch.dtype, device=str, ), but expected one of:
(tuple of ints size, *, torch.Generator generator, tuple of names names, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)
(tuple of ints size, *, torch.Generator generator, Tensor out, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)
(tuple of ints size, *, Tensor out, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)
(tuple of ints size, *, tuple of names names, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)
sure, batch size now is set to 1, can't be small
| gharchive/issue | 2023-09-04T08:24:54 | 2025-04-01T06:38:58.541177 | {
"authors": [
"Fridge003",
"frankmara",
"lvbu12",
"yoosan"
],
"repo": "hpcaitech/ColossalAI",
"url": "https://github.com/hpcaitech/ColossalAI/issues/4607",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
1815058057 | [pipeline] add pipeline support for T5Stack/T5EncoderModel
📌 Checklist before creating the PR
[x] I have created an issue for this PR for traceability
[x] The title follows the standard format: [doc/gemini/tensor/...]: A concise description
[x] I have added relevant tags if possible for us to better distinguish different PRs
🚨 Issue number
Link this PR to your issue with words like fixed to automatically close the linked issue upon merge
e.g. fixed #1234, closed #1234, resolved #1234
#4247
📝 What does this PR do?
Summarize your work here.
if you have any plots/diagrams/screenshots/tables, please attach them here.
Design special algorithm for distributing layers to pipeline stages, since the structure of T5(Encoder/Decoder) is more complex than other transformer models.
Modify the logic of forward for T5Stack/T5EncoderModel, so that pipeline parallel can be smoothly run.
Add relevant tests for layer distribution & pipeline forward.
💥 Checklist before requesting a review
[x] I have linked my PR to an issue (instruction)
[x] My issue clearly describes the problem/feature/proposal, with diagrams/charts/table/code if possible
[x] I have performed a self-review of my code
[x] I have added thorough tests.
[x] I have added docstrings for all the functions/methods I implemented
⭐️ Do you enjoy contributing to Colossal-AI?
[x] 🌝 Yes, I do.
[ ] 🌚 No, I don't.
Tell us more if you don't enjoy contributing to Colossal-AI.
| gharchive/pull-request | 2023-07-21T02:27:46 | 2025-04-01T06:38:58.547349 | {
"authors": [
"Fridge003"
],
"repo": "hpcaitech/ColossalAI",
"url": "https://github.com/hpcaitech/ColossalAI/pull/4300",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
600991294 | Implemented generic os event driven mechanism to update HPENodeInfo object if there is any change in object attributes detected .
Issue:
CON-882 (Continuously monitor worker node network configuration)
Implementations:
Implemented a generic polling mechanism that accepts anonymous function and polling interval as arguments.
It has two functions
1.obj:=InitTask(...)
This is basically used to initialize the task object which registers the anonymous function that needs to be polled along with poll frequency. Also, it invokes a separate thread to monitor the OS signals e.g SIGTERM, SIGHUP for the graceful exit of the polling task.
2.obj.start()
This is basically to kick starts the polling in a loop unit os signal is received. It periodically polls the registered anonymous fn. This should be invoked as a separate goroutine.
Created an anonymous wrapper function around getNodeInfo() that is passed to InitTask() with default 30 Minutes polling frequency.
Testing:
I have tested the code by manually deleting the cluster worker node's one of the data network interfaces and have validated that the network changes are dynamically picked by Node Server and also HPENodeInfo is updated.
Hi,
I'm not sure how to get these email to stop. Can you please remove me from
your mailing list?
-Shiva
On Mon, Apr 27, 2020, 8:36 AM Shiva Krishna Merla notifications@github.com
wrote:
@shivamerla approved this pull request.
looks good..
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hpe-storage/csi-driver/pull/145#pullrequestreview-401074021,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAB2ZBZRZRNVFF3UUBKPH3ROWRAFANCNFSM4MJSNJDQ
.
Hi, I'm not sure how to get these email to stop. Can you please remove me from your mailing list?
…
-Shiva
I guess you need to Unsubscribe notification. That should stop. Since I haven't made any user-specific configuration it was the default.
Hi, I'm not sure how to get these email to stop. Can you please remove me from your mailing list?
…
-Shiva
I guess you need to Unsubscribe notification. That should stop. Since I haven't made any user-specific configuration it was the default.
@shiva Looks like folks have been tagging you instead of me by mistake. My GitHub ID is @shivamerla. I am not sure how i can control it. Can you unsubscribe from notifications on this repo?
Will try. Thanks for your responses.
-Shiva
On Mon, Apr 27, 2020, 9:49 PM Shiva Krishna Merla notifications@github.com
wrote:
Hi, I'm not sure how to get these email to stop. Can you please remove me
from your mailing list?
… <#m_2134139001607331619_>
-Shiva
I guess you need to Unsubscribe notification. That should stop. Since I
haven't made any user-specific configuration it was the default.
@shiva https://github.com/shiva Looks like folks have been tagging you
instead of me by mistake. My GitHub ID is @shivamerla
https://github.com/shivamerla. I am not sure how i can control it. Can
you unsubscribe from notifications on this repo?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hpe-storage/csi-driver/pull/145#issuecomment-620378754,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAB2ZEG5Z26UNSZAROD6T3ROZN6LANCNFSM4MJSNJDQ
.
| gharchive/pull-request | 2020-04-16T12:03:29 | 2025-04-01T06:38:58.776898 | {
"authors": [
"shiva",
"shivamerla",
"vidhutsingh"
],
"repo": "hpe-storage/csi-driver",
"url": "https://github.com/hpe-storage/csi-driver/pull/145",
"license": "Apache-2.0",
"license_type": "permissive",
"license_source": "github-api"
} |
188584403 | US_4.3: Email to participants
As organizer I want to send a bulk mail to all participants of an event in order to avoid coping the email addresses.
Dependency: Event, Role Organizer, Role Pupil
Additional details: The sender of the Email can be a single person (e.g. tobias.duerschmid@student.hpi.de) or a mailing list (e.g. mintcamp2016@hpi.de). Please ensure, that this will not lead to access violation and discuss your solution with the HPI admins and my team.
| gharchive/issue | 2016-11-10T18:34:17 | 2025-04-01T06:38:58.782787 | {
"authors": [
"tobiduer"
],
"repo": "hpi-swt2/workshop-portal",
"url": "https://github.com/hpi-swt2/workshop-portal/issues/35",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
191464406 | Missing information in seeds.rb
As @radscheit already pointed out, db/seeds.rb is missing information to seed the database. Please add at least the required fields for a profile (:first_name, :last_name, :gender, :birth_date, :email, :school, :street_name, :zip_code, :city, :state, :country)
/cc @hefowe @cmfcmf @Philipp-Bode
Maybe there could be a test that makes sure that db/seeds.rb can be loaded?
| gharchive/issue | 2016-11-24T08:57:51 | 2025-04-01T06:38:58.784345 | {
"authors": [
"bjrne",
"chrisma"
],
"repo": "hpi-swt2/workshop-portal",
"url": "https://github.com/hpi-swt2/workshop-portal/issues/63",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
192225321 | composer.json是否有误？
"require": {
"php": ">=5.3.0",
"hprose/hprose": ">=2.0.9",
"ext-swoole": ">=1.8.8"
},
应为 "hprose/hprose-php":">=2.0.9"
并没有错，hprose/hprose-php 这个包不是官方的，是一个 hprose 用户在很久之前 fork 了一份发布到 packagist 上面的一个包，这个版本是很旧的。
hprose/hprose 这个包才是对应的官方的 hprose/hprose-php 项目的。
| gharchive/issue | 2016-11-29T09:08:44 | 2025-04-01T06:38:58.796125 | {
"authors": [
"andot",
"geekchu"
],
"repo": "hprose/hprose-swoole",
"url": "https://github.com/hprose/hprose-swoole/issues/2",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
1173759910 | Update readme with typedarray source
Here's a small change to the README, with information on using a Uint8Array for the source, which I forgot to add in my previous PR.
Thanks!
| gharchive/pull-request | 2022-03-18T16:06:37 | 2025-04-01T06:38:58.877323 | {
"authors": [
"hrynko",
"p3v9d5ui"
],
"repo": "hrynko/vue-pdf-embed",
"url": "https://github.com/hrynko/vue-pdf-embed/pull/17",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
2622642517 | JobDetails unit test fails
Failed test output:
tests/components/Job/JobDetails.test.tsx > JobDetails > renders JobDetails
TypeError: Cannot read properties of undefined (reading 'join')
Added a conditional statement to check if the requiredSkills array existed before attempting to call join on it. Bug fixed!
| gharchive/issue | 2024-10-30T01:30:56 | 2025-04-01T06:38:58.889637 | {
"authors": [
"vuvuong003"
],
"repo": "hsalway1/WolfJobs",
"url": "https://github.com/hsalway1/WolfJobs/issues/8",
"license": "MIT",
"license_type": "permissive",
"license_source": "github-api"
} |
613724456 | new(vx-demo): convert Brush to codesandbox
:memo: Documentation
:house: Internal
TODO
[ ] fix initialBrushPosition in sandbox
Part of #624, re-writes the Brush demo to link out to code-sandbox.
Link (update branch to master upon merge).
@kristw @hshoff
I'm just gonna merge this and continue to debug the initialBrushPosition separately
| gharchive/pull-request | 2020-05-07T02:15:32 | 2025-04-01T06:38:58.894061 | {
"authors": [
"williaster"
],
"repo": "hshoff/vx",
"url": "https://github.com/hshoff/vx/pull/678",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
64905202 | Fix #23 decrease horizontal width of badges
Fix #23 decrease horizontal width of badges
Closing to squash.
| gharchive/pull-request | 2015-03-28T06:06:07 | 2025-04-01T06:38:58.904287 | {
"authors": [
"brettwooldridge"
],
"repo": "hstove/issue_stats",
"url": "https://github.com/hstove/issue_stats/pull/25",
"license": "mit",
"license_type": "permissive",
"license_source": "bigquery"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.