text:
Problem with HeaterCooler

Today I tried the new HeaterCooler service but I have a problem:
When I change the temperature or the Mode(s)/State, everything works fine. But changes are not reflected in the Apple Home App. For example, the temperature is always 0. I checked the MQTT topic and the values but everything seems fine.
Before HeaterCooler I used a Thermostat to control my AirCondition. This is still working without any problems (like > 40 other devices I use via HomeKit2Mqtt).
Any help or hint is appreciated.
Viele Grüße
Christoph

Just a first guess... could you try to delete line 44 in services/HeaterCooler.js https://github.com/hobbyquaker/homekit2mqtt/blob/master/services/HeaterCooler.js#L44 and restart homekit2mqtt to see if it works then?

could you pls show the log output (-v debug) when publishing a message on the temperature topic?

I found out that the temperature topic is not in the log file.
This ist my config:
 "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2":
  {
    "id": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2",
    "name": "EwWohnzimmer/Klimaanlage2",
    "manufacturer": "HCS",
    "model": "EwWohnzimmer/Klimaanlage2",
    "services":
    [
      {
        "service": "HeaterCooler",
        "name": "EwWohnzimmer/Klimaanlage2",
        "topic":
        {
          "setActive": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/setActive",
          "setTargetHeaterCoolerState": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/setTargetHeaterCoolerState",
          "setCoolingThresholdTemperature": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/setCoolingThresholdTemperature",
          "setHeatingThresholdTemperature": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/setHeatingThresholdTemperature",
          "setRotationSpeed": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/setRotationSpeed",
          "setSwingMode": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/setSwingMode",
          "statusActive": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusActive",
          "statusCurrentTemperature": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusCurrentTemperature",
          "statusCurrentHeaterCoolerState": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusCurrentHeaterCoolerState",
          "statusTargetHeaterCoolerState": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusTargetHeaterCoolerState",
          "statusSwingMode": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusSwingMode",
          "statusRotationSpeed": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusRotationSpeed",
          "statusCoolingThresholdTemperature": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusCoolingThresholdTemperature",
          "statusHeatingThresholdTemperature": "Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusHeatingThresholdTemperature"
        },
        "payload":
        {
          "identify": "select"
        },
        "config":
        {
          "TemperatureDisplayUnits": 0
        }
      }
    ]
  },

The log:
0|index    | 2018-08-13 21:41:19.953 <debug> < mqtt Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusCoolingThresholdTemperature 23 23
0|index    | 2018-08-13 21:41:19.954 <debug> > hap update EwWohnzimmer/Klimaanlage2 CoolingThresholdTemperature 23
0|index    | 2018-08-13 21:41:19.955 <debug> < mqtt Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusHeatingThresholdTemperature 23 23
0|index    | 2018-08-13 21:41:19.955 <debug> > hap update EwWohnzimmer/Klimaanlage2 HeatingThresholdTemperature 23
0|index    | 2018-08-13 21:41:19.956 <debug> < mqtt Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusCurrentHeaterCoolerState 0 0
0|index    | 2018-08-13 21:41:19.956 <debug> > hap update EwWohnzimmer/Klimaanlage2 CurrentHeaterCoolerState 0
0|index    | 2018-08-13 21:41:19.956 <debug> < mqtt Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusRotationSpeed 25 25
0|index    | 2018-08-13 21:41:19.956 <debug> > hap update EwWohnzimmer/Klimaanlage2 RotationSpeed 25
0|index    | 2018-08-13 21:41:19.956 <debug> < mqtt Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusSwingMode 0 0
0|index    | 2018-08-13 21:41:19.957 <debug> > hap update EwWohnzimmer/Klimaanlage2 SwingMode 0

I checked the topic publication with MQTTBox and it looks ok:
26
qos : 0, retain : false, cmd : publish, dup : false, topic : Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusCurrentTemperature, messageId : , length : 75, Raw payload : 5054

Thanks,
Christoph

Ok, found the error. Will fix it asap.

Thank you very much! It's working now!
Christoph

Hmm, it looks like changes to the CurrentHeaterCoolerState is not update in the Home App. It shows up in the log with the value 3 (Cooling) but the Home app shows "Aus". Also, TargetHeaterCoolerState is 2 (Cool).
0|index    | 2018-08-17 23:32:11.105 <debug> < mqtt Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusCurrentHeaterCoolerState 3 3
0|index    | 2018-08-17 23:32:11.105 <debug> > hap update EwWohnzimmer/Klimaanlage2 CurrentHeaterCoolerState 3
0|index    | 2018-08-17 23:32:11.106 <debug> < mqtt Hcs/Programs/EwWohnzimmer/HomeKit/Klimaanlage2/statusTargetHeaterCoolerState 2 2
0|index    | 2018-08-17 23:32:11.106 <debug> > hap update EwWohnzimmer/Klimaanlage2 TargetHeaterCoolerState 2

I tried the Eve app. But changes to the CurrentHeaterCoolerState are also not reflected. So the behavior is the same as in the Apple Home App.


text:
actually display claim values

Right now we are only displaying what the claim properties are, but not the actuall values :grimacing:

To make this better testable right a larger number of entities probably need to be added to the intermediate handpicked version (maybe all entities mentioned in Q1-100).
Oh yeah, and it should be mentioned that currently only the first claim for each property is displayed.

More detailed progress on the implementation of different data types is tracked at #9

source: gharchive/issue

repo: hobofan/ipfs-wikidata-ui

license: MIT

license_type: permissive

license_source: github-api


text:
Implement the search for international results

Reason (Why?)
The usefulness of einander-helfen.org depends on the versatility of the results. We want to be able to offer international, as well as national, results.
Solution (What?)
The user should be able to switch between national and international search. They should be able to search for countries and/or continents, as well as do a full-text search of the international posts, either within a selected country/continent or without selecting one to show all international results relevant to their search term.
Out of scope
The search for the national results stays as is. The international search is merely an extension to that.
Layout/UI will be done in another (frontend) issue.
Relation to other Issues
#224
#244 has to be done before implementing this issue.
Acceptance criteria
When international search ("Weltweit" in the dropdown next to the location search bar) is selected and the user starts typing in the location search bar, autocomplete should offer countries or continents instead of postal code and place. Any given search results in "international mode" should be international posts only, located anywhere but in Germany.
Searching for a country or continent returns posts located in that country/continent. Full-text search without selecting a country/continent returns all fitting international results. Full-text search with a country/continent selected returns all fitting results in the respective country/continent.

Correct select size in tablet view
Edit smartphone header
Don't use radius in interntaional search

Correct select size in tablet view
Edit smartphone header
Don't use radius in interntaional search

authors: DianaPankratz LeDrieHda

repo: hochschule-darmstadt/einander-helfen


text:
HS512 broken?

Hi,
Is HS512 broken or am I missing something? I'm using 0.4.1 from NPM.
> var jwt = require('jwt-simple');
undefined
> var payload = {x: 'y'};
undefined
> var token = jwt.encode(payload, 'pass', 'HS512');
undefined
> jwt.decode(token, 'whatever', 'HS512');
{ x: 'y' }
> jwt.decode(token, 'so decrypted', 'HS512');
{ x: 'y' }

The jwt.decode's third argument is noVerify.
jwt_decode(token, key, noVerify, algorithm)

Document is not enough...
Usually, you don't need to specify a algorithm because it is included in token.
> var jwt = require('jwt-simple')
undefined
> jwt.version
'0.4.1'
> var payload = {x: 'y'};
undefined
> var token = jwt.encode(payload, 'pass', 'HS512');
undefined
> jwt.decode(token, 'pass');
{ x: 'y' }
> jwt.decode(token, 'whatever');
Error: Signature verification failed
...

If you need to specify it, you can write as below.
jwt.decode(token, 'pass', true, 'HS512');

would you like some PR documenting the new params in decode?

@bjrmatos Yes, sounds good!

Hi @bjrmatos Can I close this issue ?

@alexjab sure!

authors: alexjab bjrmatos hokaccha markohaapala

repo: hokaccha/node-jwt-simple

license: mit

license_source: bigquery


text:
23:28:26 NoSuchMethodError: com.r4intellij.lang.parser.GrammarParserUtil.enter_section_(Lcom/intellij/lang/PsiBuilder;IILcom/intellij/psi/tree/IElementType;Ljava/lang/String;)Lcom/intellij/lang/PsiBuilder$Marker;

com.r4intellij.lang.parser.GrammarParserUtil.enter_section_(Lcom/intellij/lang/PsiBuilder;IILcom/intellij/psi/tree/IElementType;Ljava/lang/String;)Lcom/intellij/lang/PsiBuilder$Marker;
com.r4intellij.lang.parser.GrammarParserUtil.enter_section_(Lcom/intellij/lang/PsiBuilder;IILcom/intellij/psi/tree/IElementType;Ljava/lang/String;)Lcom/intellij/lang/PsiBuilder$Marker;
java.lang.NoSuchMethodError: com.r4intellij.lang.parser.GrammarParserUtil.enter_section_(Lcom/intellij/lang/PsiBuilder;IILcom/intellij/psi/tree/IElementType;Ljava/lang/String;)Lcom/intellij/lang/PsiBuilder$Marker;
at com.r4intellij.lang.parser.RParser.document(RParser.java:148)
at com.r4intellij.lang.parser.RParser.parse_root_(RParser.java:74)
at com.r4intellij.lang.parser.RParser.parseLight(RParser.java:67)
at com.r4intellij.lang.parser.RParser.parse(RParser.java:23)
at com.intellij.psi.tree.ILazyParseableElementType.doParseContents(ILazyParseableElementType.java:64)
at com.intellij.psi.tree.IFileElementType.parseContents(IFileElementType.java:43)
at com.intellij.psi.impl.source.tree.LazyParseableElement.f(LazyParseableElement.java:172)
at com.intellij.psi.impl.source.tree.LazyParseableElement.getFirstChildNode(LazyParseableElement.java:212)
at com.intellij.psi.impl.source.tree.LazyParseableElement.getFirstChildNode(LazyParseableElement.java:36)
at com.intellij.psi.impl.source.tree.SharedImplUtil.getFirstChild(SharedImplUtil.java:52)
at com.intellij.psi.impl.source.PsiFileImpl.getFirstChild(PsiFileImpl.java:763)
at com.r4intellij.editor.RFoldingBuilder.touchTree(RFoldingBuilder.java:85)
at com.r4intellij.editor.RFoldingBuilder.buildFoldRegions(RFoldingBuilder.java:73)
at com.intellij.lang.folding.LanguageFolding.buildFoldingDescriptors(LanguageFolding.java:90)
at com.intellij.codeInsight.folding.impl.FoldingUpdate.a(FoldingUpdate.java:265)
at com.intellij.codeInsight.folding.impl.FoldingUpdate.getFoldingsFor(FoldingUpdate.java:250)
at com.intellij.codeInsight.folding.impl.CodeFoldingManagerImpl.buildInitialFoldings(CodeFoldingManagerImpl.java:239)
at com.intellij.openapi.fileEditor.impl.text.PsiAwareTextEditorProvider.createEditorAsync(PsiAwareTextEditorProvider.java:61)
at com.intellij.openapi.fileEditor.impl.FileEditorManagerImpl.openFileImpl4(FileEditorManagerImpl.java:780)
at com.intellij.openapi.fileEditor.impl.FileEditorManagerImpl.openFileImpl3(FileEditorManagerImpl.java:738)
at com.intellij.openapi.fileEditor.impl.FileEditorManagerImpl$8.run(FileEditorManagerImpl.java:718)
at com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:117)
at com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:99)
at com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:85)
at com.intellij.openapi.fileEditor.impl.FileEditorManagerImpl.openFileImpl2(FileEditorManagerImpl.java:715)
at com.intellij.openapi.fileEditor.impl.FileEditorManagerImpl.openFileWithProviders(FileEditorManagerImpl.java:656)
at com.intellij.openapi.fileEditor.ex.FileEditorManagerEx.openFile(FileEditorManagerEx.java:146)
at com.intellij.openapi.fileEditor.impl.FileEditorManagerImpl$14.run(FileEditorManagerImpl.java:1076)
at com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:124)
at com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:99)
at com.intellij.openapi.command.impl.CoreCommandProcessor.executeCommand(CoreCommandProcessor.java:85)
at com.intellij.openapi.fileEditor.impl.FileEditorManagerImpl.openEditor(FileEditorManagerImpl.java:1072)
at com.intellij.openapi.fileEditor.OpenFileDescriptor.navigateInAnyFileEditor(OpenFileDescriptor.java:152)
at com.intellij.openapi.fileEditor.OpenFileDescriptor.navigateInEditor(OpenFileDescriptor.java:138)
at com.intellij.openapi.fileEditor.OpenFileDescriptor.navigateInEditorOrNativeApp(OpenFileDescriptor.java:134)
at com.intellij.openapi.fileEditor.OpenFileDescriptor.navigate(OpenFileDescriptor.java:121)
at com.intellij.openapi.fileEditor.impl.text.FileDropHandler.a(FileDropHandler.java:75)
at com.intellij.openapi.fileEditor.impl.text.FileDropHandler.handleDrop(FileDropHandler.java:57)
at com.intellij.openapi.fileEditor.impl.EditorsSplitters$MyTransferHandler.importData(EditorsSplitters.java:777)
at javax.swing.TransferHandler.importData(TransferHandler.java:827)
at javax.swing.TransferHandler$DropHandler.drop(TransferHandler.java:1544)
at java.awt.dnd.DropTarget.drop(DropTarget.java:455)
at javax.swing.TransferHandler$SwingDropTarget.drop(TransferHandler.java:1282)
at sun.awt.dnd.SunDropTargetContextPeer.processDropMessage(SunDropTargetContextPeer.java:545)
at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchDropEvent(SunDropTargetContextPeer.java:859)
at sun.awt.dnd.SunDropTargetContextPeer$EventDispatcher.dispatchEvent(SunDropTargetContextPeer.java:783)
at sun.awt.dnd.SunDropTargetEvent.dispatch(SunDropTargetEvent.java:48)
at java.awt.Component.dispatchEventImpl(Component.java:4736)
at java.awt.Container.dispatchEventImpl(Container.java:2292)
at java.awt.Component.dispatchEvent(Component.java:4703)
at java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4898)
at java.awt.LightweightDispatcher.processDropTargetEvent(Container.java:4611)
at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4457)
at java.awt.Container.dispatchEventImpl(Container.java:2278)
at java.awt.Window.dispatchEventImpl(Window.java:2739)
at java.awt.Component.dispatchEvent(Component.java:4703)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:746)
at java.awt.EventQueue.access$400(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:697)
at java.awt.EventQueue$3.run(EventQueue.java:691)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:75)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:86)
at java.awt.EventQueue$4.run(EventQueue.java:719)
at java.awt.EventQueue$4.run(EventQueue.java:717)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionDomain.java:75)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:716)
at com.intellij.ide.IdeEventQueue.e(IdeEventQueue.java:748)
at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.java:573)
at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.java:384)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)

win7 intellj14.0.3 java version "1.8.0_31"

Oh cool a parser bug ;-). Unfortunately there's little we can do about it unless you would be willing to share a (cut-down to the relevant bits) code sample that would allow us to reproduce this error. Would this be possible for you?
If you don't want to post it publicly you could also sent it to me via email.

platform:
R x64 3.3.3
win7
java version "1.8.0_31"
IDE:pycharm 4.5.3 or intellj idea 14.0.3
the error log I package send to you,
At 2017-04-25 23:49:54, "Holger Brandl" notifications@github.com wrote:
Oh cool a parser bug ;-). Unfortunately there's little we can do about it unless you would be willing to share a (cut-down to the relevant bits) code sample that would allow us to reproduce this error. Would this be possible for you?
If you don't want to post it publicly you could also sent it to me via email.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

pycharm2016 is ok.
At 2017-04-25 23:49:54, "Holger Brandl" notifications@github.com wrote:
Oh cool a parser bug ;-). Unfortunately there's little we can do about it unless you would be willing to share a (cut-down to the relevant bits) code sample that would allow us to reproduce this error. Would this be possible for you?
If you don't want to post it publicly you could also sent it to me via email.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

The plugin does not support versions before 2016.3. Sorry for inconvenience.
Do you know @ktisha what since-build value would need to be used in the plugin.xml to prevent users with older version from installing the plugin?

authors: holgerbrandl jackwwv


text:
conversion: revert json-marshalling change in #144, marshal hex-format

This undoes the change in json-marshalling, making it so that we (again) marshal uint256.Int in hex-format. This is more widely useful in go-ethereum.
I originally intended to let it be this way, but I changed my mind due to this comment: https://github.com/holiman/uint256/pull/144#discussion_r1405828059.
This would be an alternative to https://github.com/ethereum/go-ethereum/pull/28628
cc @fjl @karalabe

But why?
On Thu, 30 Nov 2023 at 21:46, codecov[bot] @.***> wrote:

Codecov
https://app.codecov.io/gh/holiman/uint256/pull/145?src=pr&el=h1&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Martin+Holst+Swende
Report
Merging #145
https://app.codecov.io/gh/holiman/uint256/pull/145?src=pr&el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Martin+Holst+Swende
(add7529
https://github.com/holiman/uint256/commit/add7529b4048cc245cf5ada7df33efcf24678c15)
into master
https://app.codecov.io/gh/holiman/uint256/commit/f24ed59bea89c23941cf073aeb3f702514f3b371?el=desc&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=Martin+Holst+Swende
(f24ed59
https://github.com/holiman/uint256/commit/f24ed59bea89c23941cf073aeb3f702514f3b371)
will not change coverage.
The diff coverage is 100.00%.
Additional details and impacted files
@@            Coverage Diff            @@##            master      #145   +/-   ##
Coverage   100.00%   100.00%
Files            5         5
Lines         1643      1643
Hits          1643      1643
—
Reply to this email directly, view it on GitHub
https://github.com/holiman/uint256/pull/145#issuecomment-1834442515, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAA7UGLCAG2FEIQHLR452ADYHDPBXAVCNFSM6AAAAABABXLKW2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZUGQ2DENJRGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

As @fjl noted:

However, let me just say I find the upstream change is not the best. We always want hex output in go-ethereum. So now we need to add a conversion every time just like for big.Int. I thought uint256 is purpose built for our use, why would we make it harder for ourselves?

What is the status here? will this change from hex to decimal format be reverted or not? Having decimal marshaling is kind of annoying in the ethereum context and would require a proxy type as hexutil.Big everywhere.

We discussed this, and agreed to not revert it. I implemented a hexutil.U256 type in go-ethereum, and closed this PR.

Okay. Just out of curiosity, what is the reason for changing this in the first place?
To give some more context: My lib is effected by this breaking change (I presume it will be relatively easy to fix though). But still, this package has hundreds of direct dependents which code might break or act unexpected. This should be a v2 release IMO or kept as is.

Okay. Just out of curiosity, what is the reason for changing this in the first place?

To be more like big.Int. Or exactly which of the changes are you referring to?

To give some more context: My lib is effected by this breaking change (I presume it will be relatively easy to fix though). But still, this package has hundreds of direct dependents which code might break or act unexpected. This should be a v2 release IMO or kept as is.

Well, depends on how you see it. It doesn't break the programing API, but yes, it does break some places where marshalling is concerned. But many places where you would unmarshal a hex-string, would also accept an int-string.
Anyway, go-ethereum is the main driver for this library.

source: gharchive/pull-request

authors: holiman karalabe lmittmann


text:
increase numbers of label

Currently, I think the number of label is limited to 20 (in helper.swift) is it?
I tested it out with yolo9000 and it still limit only to above 20 array. How to increase the number of label to more than 20?

The version used in this app is trained on the PASCAL VOC dataset, which only has 20 classes. I think there is also a version trained on COCO that has more classes.

Thank you, I am able to generate it now. It take a while from basic of knowing nothing to get to know  yolo.

repo: hollance/YOLO-CoreML-MPSNNGraph


text:
Access to Link for checkpoint

Hi, thank you for sharing such a great work. I want to reproduce the results about the models using the checkpoint link. However, The link needs a permission for the access. So Please allow access to checkpoint link.

Sorry for the late reply, I have opened up access to everyone.

thank you


text:
Merge tombstone pr

PR summary
This PR manually merges the api and implementation features on cas and eavs introduced by https://github.com/holochain/holochain-rust/pull/1363/files.
Review checklist

[ ] The story has unit or integration tests
[ ] No new bugs, and any tech-debt is identified and justified
[ ] There is enough API documentation (how to use)
[ ] There is enough code documentation (how the code works)

This looks good to me!

authors: AshantiMutinta struktured


text:
Make subscription attribute update handler Thread safe

The attribute update callback of subscription is called from the Matter SDK Thread directly. Most handling needs to run in the event loop Thread. Do a few quick checks, and then call the rest of the handler in the event loop Thread.
This also gets rid of a couple of loop.create_task() calls from the Matter SDK thread. loop.create_task() is not Thread safe.

Instead of calling a routine on the event loop thread, we could also call a co-routine directly using asyncio.run_coroutine_threadsafe. Then we might also be able to remove some of the create_task calls and just await those calls. But this could affect timing etc. In a first step, I'd like to just make this Thread safe while leaving things mostly as is.


text:
Add commandclass version attribute

Add attribute for the CommandClass Version.
This is key in order to solve the targetValue issue with dimmers.

depends on https://github.com/zwave-js/zwave-js-server/pull/62 and bump of server version afterwards

depends on https://github.com/zwave-js/zwave-js-server/pull/62 and bump of server version afterwards

Z-Wave JS Server Alpha 4 has been released with the server PR included https://github.com/zwave-js/zwave-js-server/releases/tag/1.0.0-alpha.4

Z-Wave JS Server Alpha 4 has been released with the server PR included https://github.com/zwave-js/zwave-js-server/releases/tag/1.0.0-alpha.4

authors: balloob marcelveldt


text:
Punctuation should be ignored in wildcards

"is {name} in {zone}" where {zone} is a wildcard will match is Alice in New York?, but the {zone} slot will incorrectly hold the value New York? with the question mark.
Punctuation should be ignored from wildcard matching.

This feature has been merged into main

authors: synesthesiam tetele

repo: home-assistant/hassil


text:
Remove leftover antl4r and dataclasses-json references

The dependency on those libraries was removed in the 1.0 release.

Thanks!

authors: mweinelt synesthesiam


text:
Chromecast not detected in certain conditions

Home Assistant release (hass --version):
Hassbian 1.31 with HASS 0.60.0
Python release (python3 --version):
3.5.3
Component/platform:
Cast
Description of problem:
Chromecasts (and similar) are no longer detected/usable when not using discovery or when running on a non-flat network.
Expected:
Chromecasts, Google Homes, Chromecast Audios should appear as media_player devices.
Additional info:
Google recently removed an API from Chromecasts (fw 1.28.x+) that was used by pychromecast to access information normally obtained from device discovery (See: https://github.com/balloob/pychromecast/issues/195)
For those of us that run non-flat networks (i.e. HASS on different subnet) discovery is not an option, and so explicit declaration of CC addresses usually allows pychromecast to obtain the information for the device from the API that has been removed.
The result of this break is that anyone not using discovery, or not using a flat network, no longer has any media_player devices detected for their Cast devices.
pychromecast fixed this issue in 1.0.3, by obtaining the required information from an alternative API in the Cast devices on newer firmwares and I have experimentally confirmed the fix.
https://github.com/home-assistant/home-assistant/issues/10964#issuecomment-351847395
However, updating the version of pychromecast to 1.0.3 within my HASS venv still does not allow cast devices to be detected using the explicitly set URL in the config.
For completeness, the configuration previously worked, no configs have changed, the CCs only broke when the CC firmwares updated themselves, while I was still running 0.59.2, 0.60.0 still still doesn't work, and updating to pychromecast 1.0.3 does not work, although testing pychromecast in a Python shell on the command line does work as expected.

It seems I had mis-understood how depencies work in HASS. Upgrading to 1.0.3 manually caused it to be downgraded again on restart, however, changing the requirement in cast.py to 1.0.3 upgraded it properly and my CCs are working again.
TL;DR Upgrading to pychromecast 1.0.3 solves this issue.

For awareness: 1.0.2 broke other devices:
https://github.com/home-assistant/home-assistant/issues/10926

how can I solve the problem on hassio?

changing the requirement in cast.py to 1.0.3 upgraded it properly

@hamid-elaosta Are you able to walk me through this? It seems like there's a file I can edit to make this change, is that correct?

@rufusmccoot Of course;
Stop home assistant;
systemctl stop home-assistant@homeassistant.service
Edit this file;
/srv/homeassistant/lib/python3.5/site-packages/homeassistant/components/media_player/cast.py
and change this line
REQUIREMENTS = ['pychromecast==0.8.2']
to
REQUIREMENTS = ['pychromecast==1.0.3']
Save and start home assistant, and your Chromecast should work again hopefully (as mine do).

@sardauker I have no clue how hassio works, nor have I ever used it, hopefully one of the HASS guys can help you.

@hamid-elaosta Thanks. I'm actually doing it on hass.io too and can't find that file. I'll keeping looking around though. Thanks again.

Idem. Hassio has not a full working system interface, just a busybox.

for hassio it is pretty much the same but you copy the cast.py file in as a custom_component and change the value there.
BEWARE: DO NOT FORGET that you've done this as you may see issues later as the custom component overrides the hassio

authors: hamid-elaosta rufusmccoot ryanm101 sardauker

repo: home-assistant/home-assistant


text:
Cannot use auth_providers

After add on both 0.74 and 0.74.1
homeassistant:
  auth_providers:
   - type: homeassistant
   # Uncomment next line if you want to enable legacy API password support
   - type: legacy_api_password

I cannot enter ha at all. Everything load completed but I cannot access ha from browser at all. In log file show
2018-07-24 19:54:39 WARNING (MainThread) [homeassistant.components.http] Experimental auth api enabled and legacy_api_password support enabled. Please use access_token instead api_password, although you can still use legacy api_password

#15659

Confirmed in forum, duplicated #15659

authors: SamuiSmartHome awarecan


text:
Problem with Plex

Home Assistant release with the issue: 0.84.3

Operating environment: Hass.io on Raspberry Pi 3 and Plex Server on Windows 10

Component/platform: https://www.home-assistant.io/components/media_player.plex/

Description of problem:
Hi all,
I’m trying to configure Home Assistant to interact with my Plex Media Server.
First, I followed this procedure and I had no issues: I rebooted HA and all seems ok with no errors in the log.
Then, as I first test, I tried to play a song in one of my GoogleMini speaker, so I created a trigger with this action:
action:
  service: media_player.play_media
    data:
      entity_id: media_player.GoogleMiniSpeaker1
      media_content_id: { \“library_name\” : \“Music\”, \“artist_name\” : \“Muse\”, \“album_name\” : \“Black Holes and Revelations\”, \“track_name\” : \“Starlight\”, \“shuffle\”: \“0\” }
      media_content_type: MUSIC

But when I activate the trigger nothing happened, and I have this error in the log:
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/service.py", line 277, in _handle_service_platform_call
    await getattr(entity, func)(**data)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/switch/template.py", line 154, in async_turn_on
    await self._on_script.async_run(context=self._context)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/script.py", line 130, in async_run
    await self._handle_action(action, variables, context)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/script.py", line 172, in _handle_action
    action, variables, context)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/script.py", line 261, in _async_call_service
    context=context
  File "/usr/local/lib/python3.6/site-packages/homeassistant/helpers/service.py", line 81, in async_call_from_config
    domain, service_name, service_data, blocking=blocking, context=context)
  File "/usr/local/lib/python3.6/site-packages/homeassistant/core.py", line 1101, in async_call
    processed_data = handler.schema(service_data)
  File "/usr/local/lib/python3.6/site-packages/voluptuous/schema_builder.py", line 267, in __call__
    return self._compiled([], data)
  File "/usr/local/lib/python3.6/site-packages/voluptuous/schema_builder.py", line 589, in validate_dict
    return base_validate(path, iteritems(data), out)
  File "/usr/local/lib/python3.6/site-packages/voluptuous/schema_builder.py", line 427, in validate_mapping
    raise er.MultipleInvalid(errors)
voluptuous.error.MultipleInvalid: value should be a string for dictionary value @ data['media_content_id']

What's wrong?
Thank you in advance
Riky
Problem-relevant configuration.yaml entries:
media_player:
  - platform: plex

Problem-relevant plex.conf entries:
{
    "192.168.0.90:32400": {
        "ssl": false,
        "token": "---MYTOKEN---",
        "verify": false
    }
}

Your quotes looks off at first glance. Also, you need to quote the whole entry.

Hi @fabaff , I change the code in this way:
action:
  service: media_player.play_media
    data:
      entity_id: media_player.GoogleMiniSpeaker1
      media_content_id: "{ \“library_name\” : \“Music\”, \“artist_name\” : \“Muse\”, \“album_name\” : \“Black Holes and Revelations\”, \“track_name\” : \“Starlight\”, \“shuffle\”: \“0\” }"
      media_content_type: MUSIC

but I get an error immediately from the compiler
unknown escape sequence at line 9, column 33:
              media_content_id: "{ \“library_name\” : \“Music\”, \“a ...
                                    ^

I would also like to apologize to everyone if my questions are very banal, but I'm just a beginner and I couldn't find anywhere a simple example how to properly use the syntax.

I changed the code again in this way
(quotation marks " everywhere, and not “ ” as suggested in the component page example ):
action:
  service: media_player.play_media
    data:
      "entity_id": "media_player.GoogleMiniSpeaker1"
      "media_content_id": "{ \"library_name\" : \"Music\", \"artist_name\" : \"Muse\", \"album_name\" : \"Black Holes and Revelations\", \"track_name\" : \"Starlight\", \"shuffle\": \"0\" }"
      "media_content_type": "MUSIC"

Now I get no errors in the log and hear the "pling" sound of the google mini speaker activation, but the song is not played.
Any idea of what I'm still doing wrong?
May I take this opportunity to wish you all a Happy Christmas!

Unfortunately the issue still persists.
I have not understood yet which is the correct syntax.

authors: RikyUnreal fabaff


text:
MQTT Sensor: state is not updated when data is too big

Problem:
A sensor state is never updated if the message received via MQTT is big.
Steps to reproduce:
1 - Create a sensor getting data from a topic
2 - Send data that is to big (I tried 326 and wans't received).

Please add more details:

which MQTT broker do you use
which MQTT client sends the data
have you verified, with another MQTT client, that the data is received

@emontnemery

I have indeed tested with another client and it received the data.
I have tested the packet being sent from two different clients (ESP and a MQTT Windows Client).
The problem is not with the broker since Home Assistant is a client and doesn't not know the brokers code.
I have checked with Wireshark and confirmed the packet is sent to Home Assistant.

I am pretty sure the steps above will reproduce the problem.
Any questions, just ask.
Best Regards.

The maximum length of the data stored in an entity's state is 255 characters.

The maximum length of the data stored in an entity's state is 255 characters.

I understand it is right now, but that is very limiting. For instance, I have a device that was placed on my door, and, everytime somebody rings the bell it takes a picture and makes it available throught MQTT. The message is compressed, but still doesn't work.

Agree, I also tried using it for compressed images and couldn't make them small enough :(

We should not store compressed images in the state machine. That's not what the state machine is for. You can use the MQTT camera platform for images.

authors: Alv3s Swiftnesses balloob emontnemery tdejneka


text:
update insteon client

Description:
Update client library
Related issue (if applicable): fixes #6842
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:

[ ] 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.

Have you tested the updated version locally yourself with real devices?

I think these changes have been included in my PR here #10137 and I have tested those with my local real devices.

New client was tested on Insteon 2-wire dimmers. Closing this PR though since the change is included in #10137

authors: armills camrun91 wardcraigj


text:
Google assistant sync

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:

[ ] The code change is tested and works locally.

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:

[ ] 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.

This is my code and it's not ready yet.


text:
bump python-ecobee-api version to 0.0.18

Description:
Bump python-ecobee-api version to 0.0.18
This resolved an issue caused by a Typo that prevented Ecobee from utilizing nextTransition when setting a hold mode or temperature.
Related issue (if applicable): fixes #
https://github.com/nkgilley/python-ecobee-api/pull/33
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:

[x] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass

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:

[ ] 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:

[ ] Tests have been added to verify that the new code works.

Please read the PR template and fill it in

Thanks! 🐬

authors: balloob geekofweek


text:
Update REST Sensors to allow json_attributes_template for state attributes (MQTT style)

Description:

Add json_attributes and  force_update options to the rest platform's binary_sensor platform (already exist in sensor)
Update the rest sensor and binary_sensor devices to allow MQTT-style json_attribute_template options to break out the JSON response into state attributes.  Currently only first-level JSON dict values can be handled as device state attributes, this allows you to add a nested JSON response object as state values and then (coupled with json_attributes) filter that object further. MQTT Documentation for reference.

Pull request with documentation for home-assistant.io (if applicable): home-assistant/home-assistant.io#9722
Example entry for configuration.yaml (if applicable):
binary_sensor:
  - platform: rest
    scan_interval: 600
    resource: !secret resource_url
    name: VPN
    device_class: connectivity
    value_template: "{{ value_json['user']['connected'] }}"
    headers:
      User-Agent: Home Assistant
      Content-Type: application/json
    json_attributes_template: "{{ value_json.connection | tojson }}"
    json_attributes:
      - device_description
      - vpn_ip
      - connected_since_date

Checklist:

[X] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.
[X] I have followed the [development checklist][dev-checklist]

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

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

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

[N/A] [The manifest file][manifest-docs] has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[N/A] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[N/A] Untested files have been added to .coveragerc.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

Why can't the actual json_attributes be a list of templates? That would make the sensor much more flexible (since the desired attributes might not be nested in the same object).

@ronmichel you could in theory, but I was trying to stay within the established architecture by mimicking what the MQTT sensor has already.

We should not have Jinja2 templates be used to generate JSON values.

@balloob it's what MQTT also does, but yeah it's strange. We should handle that for that kind of integration same over the place.

Would it be better to just allow a list of JSON paths (including any nested objects) in the config and return those directly?
Like @pvizeli said, I was just extending something already used in MQTT which works and had a similar need for me with REST.
Do you want me to open an architecture issue for this if you're wanting to be consistent across the board? (I can't think of any other 'generic' integrations that might need this besides MQTT, REST, and maybe command line?).

We have complex template rendering. So we could do something like this:
attributes:
  something: {{ json_value.bla }}
  hello: {{ json_value.yo }}

I updated the code to allow the use of complex templates, but I don't see a method for complex templates "with possible json values" -- I have to convert the JSON to a dict and pass that to the render_complex function.  It works, however, you end up with "{{ connection.bytes_read }}" instead of "{{ value_json.connection.bytes_read }}".  Am I missing that function somewhere?

Is it possible to update homeassistant.helpers.template Line 69 from:
    return value.async_render(variables)

to:
    return value.async_render_with_possible_json_value(variables)

Or duplicate this function to render_complex_with_possible_json_value?

Please rebase on latest dev branch.

@shbatm please run black from the project root.
black --fast homeassistant tests

@balloob can you continue the review?

Months have passed since last update on this PR, so it is running stale. I'm going to close the PR for now.
Feel free to re-open the PR when you are ready to work on it again 👍

authors: MartinHjelmare balloob frenck pvizeli ronmichel shbatm


text:
Bump env_canada to 0.0.27

Description:
Bumps env_canada library to 0.0.27. Resolves issue with HTTPS certificate failures noted at https://community.home-assistant.io/t/support-for-environment-canada-platforms/126241/73.
Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.
[x] I have followed the [development checklist][dev-checklist]

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

[x] [The manifest file][manifest-docs] has all fields filled out correctly. Update and include derived files by running python3 -m script.hassfest.
[x] New or updated dependencies have been added to requirements_all.txt by running python3 -m script.gen_requirements_all.
[x] Untested files have been added to .coveragerc.

This PR should have been merged into dev branch and not the rc branch.

I've made the label red to make sure it's more clear next time

authors: balloob michaeldavie


text:
Workaround to allow multiple recipients separated by a comma in smtp …

Description:
Related issue (if applicable): fixes #2093
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#
Example entry for configuration.yaml (if applicable):

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

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

If code communicates with devices, web services, or a:

[ ] 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.

…emails (#2093)

It seems that this change would allow entry for recipients in the configuration.yaml files which looks like this:
notify:
  - platform: smtp
    ...
    recipient: recipient1@smtp.ch, recipient2@smtp.ch

I guess that would work but YAML is using a different format for listing entries.
    recipient:
      - recipient1@smtp.ch
      - recipient2@smtp.ch
    ...
    recipient: [recipient1@smtp.ch, recipient2@smtp.ch] # inline

This change would also require an update of the documentation.

It's a quick fix until someone is willing to do an overhaul on the module to support a list, rename it to "recipients" (plural), add support for cc, and more things, etc.  the comma separated string is the best I could come up with that would be backwards compatible with previous versions of config files without a doc change necessarily needed

Please make sure that you fill out the template for the pull request. Just adding a title is not enough.
Closing this as the functionality is already supported by providing a list like @fabaff said.
notify:
  - platform: smtp
    ...
    recipient:
      - recipient1@smtp.ch
      - recipient2@smtp.ch

As far as I can tell, that's incorrect - multiple recipients is NOT currently supported for the reason that the message expects a comma separated string:
msg['To'] = self.recipient
(here self.recipient must be of the form "recipient1@smtp.ch,recipient2@smtp.ch"
but the library expects a python list:
mail.sendmail(self._sender, self.recipient,
(here self.recipient must be of the form [ 'recipient1@smtp.ch' , 'recipient2@smtp.ch' ] )
Please consider reopening.

By using the configuration that I provided, you are specifying a list in YAML which will be passed as a list to the SMTP notify platform.

Actually @jwater7 has a point. Passing a list to the MIMEText object produces an AttributeError when the as_string method is called:
In [1]: from email.mime.text import MIMEText
In [2]: msg = MIMEText('testbody')
In [3]: msg['To'] = to
In [4]: print(msg.as_string())
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
...
AttributeError: 'list' object has no attribute 'encode'

I think we can fix this better without having to change how things are configured by joining the list into a comma separated string, before passing it into the MIME object.
In [23]: msg = MIMEText('testbody')
In [24]: msg['To'] = ', '.join(to)
In [25]: print(msg.as_string())
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
To: email1@test.com, email2@test.com

testbody

I'm very confused as @jwater7 patch does exactly the opposite: it takes a comma delimited string and convert it to a list.
If a comma separated list is what is expected, that would also work today as one can just specify that, right?

The problem is that we need to provide recipients at two places. The first one is to the MIME object. There we have to enter a string. A comma separated string if more than one email. The other place is as an argument to the mail.sendmail method. There we have to enter a list of strings or a string. The current implementation passes the recipient variable as is to both places. Hence, it will break if we pass a list to the MIME object.
I don't think this PR should be merged as is, but could be modified to instead pass recipients correctly into the MIME object. The call to sendmail method should work as it is today. See my example above, and in that case we also need coercing the recipients variable into a list.

authors: MartinHjelmare balloob fabaff jwater7


text:
Question for using Roborock App

Hi,
thanks for this plugin!! I have get today the Roborock S6 maxV.
I have a question to this part:
Fully automatic
This feature seems to be working on models that support naming the rooms in the Xiaomi / Roborock App. This is known to include the Roborock S6 as well as the S4 with firmware version 3.5.8_0358 or newer.
Even if you have one of these models but you haven't named the Rooms in your App yet, this function will not work! Thanks @domeOo
How can I get the token in Mi Home and using the Roborock App? Is this possible?

Hi @Kohle81,
Other folks are trying to make it work with the Roborock App but they haven't found out how to do so yet: https://github.com/homebridge-xiaomi-roborock-vacuum/homebridge-xiaomi-roborock-vacuum/issues/104
Apparently the Roborock App has a different way to authenticate the robot, and it invalidates the token every time you use the app 🤷


text:
Sort on children column

Hi,
First of all, TreeGrid is a POWERFUL datatable plugin with a simple approach (children)
There is however a small lack for me. When a column is sorted, the column of the child branch is not sorted.
If that had been possible, it would be great !
Best
Frédérik

Thanks for the suggestion, I'll check and update it once I'm free.
Best
Homfen


text:
Crash during torus eversion

torus_eversion_actions.txt
Crash I experienced while trying to simplify one of the proof steps in an attempt to build the torus eversion.

Thanks Calin and Wilf. Calin what was the issue here?

It was trying to do an anticontraction but it couldn't do the factorization so it panicked. Now if that happens, it just does a bubbling (which has always been our fallback).

authors: calintat jamievicary wilfofford

repo: homotopy-io/homotopy-rs


text:
combining multiple TIFF's into a single TIFFImageryProvider

I have a set of 57 RGB TIF's which cover  all of Austria, each about 10GB
Do you see a way to combine those into a single TIFFImageryProvider, similar to a GDAL VRT?
or do I need to add each one separately and select the right one?
thanks in advance,
Michael
ps: works great for me - congratulations!

Hello, thank you for your support and encouragement.
This library currently only supports rendering a single TIFF file. Each TIFF file corresponds to a TIFFImageryProvider. If you have multiple TIFF files, you should group them together as a dataset.
When you need to load a specific file, you can create a TIFFImageryProvider and display it on the Cesium globe.
The dataset can be formatted as a simple array, similar to the following format, which can be easily implemented in a frontend project:
type Layer = {
  id: string;
  name: string;
  url: string;
};

type DataSet = {
  id: string;
  name: string;
  layers: Layer[];
}

Nevertheless, loading 57 COG TIFF files of 10GB each onto Cesium puts a significant strain on performance.
If you could test and implement this loading scenario in a similar js library like OpenLayers, please let me know, and I will try to address this performance issue.

@hongfaqiu thanks for the quick reply!
I'll explore your suggestion
I'll also give gdal_merge  a try - probably pushing the envelope at 500GB ;)
appreciated - thanks!
Michael

500GB! That's a tremendous amount, and if GDAL slices are too large, it poses a significant performance challenge for the frontend.
Wishing you good luck!

what do you think about a tiled approach like so:

create a GDAL VRT of the GeoTIFF's
run titiler
massage TIFFImageryProvider to deal with tiled GeoTIFF's

stupid idea or doable?

@mhaberler In fact, I have a classmate whose thesis is about researching how to manage multiple TIFF files and dynamically split them into tiles in real-time.
I presented these ideas to him about half a year ago, but I am unsure if he has continued researching them. 😂

what do you think about a tiled approach like so:

create a GDAL VRT of the GeoTIFF's
run titiler on the VRT
massage TIFFImageryProvider to deal with tiled GeoTIFF's

stupid idea or doable?
edit: it seems this project uses titiler-generated tiles - in this case PNG's but not far off
the titiler documentation says it can generate GTIFF's

I believe your idea is entirely feasible. It only requires a simple modification by transforming the TIFFImageryProvider into a class similar to UrlTemplateImageryProvider.
This modified class can load and render pre-split TIFF tiles using a URL template format like /cog/tiles/{z}/{x}/{y}.tiff.
However, it would be necessary to provide the band information and spatial extent of the TIFF in advance.

authors: hongfaqiu mhaberler

repo: hongfaqiu/TIFFImageryProvider


text:
功能建议：在浏览器缩小的时候，侧边栏收进去

在浏览器缩小的时候，侧边栏收进去，而不是手动去点

这个需要适配移动端，后面再考虑吧 #87

authors: TheBlindM honghuangdc

repo: honghuangdc/soybean-admin


text:
beta1.0版本登录成功后notification框持续时间过长

在登录成功后会弹出一个欢迎回来的notification框，但是它没有设置自动关闭时间，这就导致了每次重新登录都需要额外的点击关闭一次这个提示性的框框，对于某些登录态不能长时间保存的应用来说，用户体验也许会更糟糕，可否考虑增加一个持续时间？

naiveUI版本是在antd版本的基础上迁移的，antd-vue的notification组件默认不传递是会默认关闭掉的，加个延迟时间就行


text:
Can the program be trained using the GPU

Can the program be trained using the GPU? I used the GPU. As a result, each agent needs to allocate memory. The result shows that the GPU memory is insufficient. Can anyone help me? Thank you
2019-07-30 03:35:51.118858: W tensorflow/core/common_runtime/bfc_allocator.cc:271] *********************************************xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2019-07-30 03:35:51.119107: E tensorflow/stream_executor/cuda/cuda_driver.cc:806] failed to allocate 6.38G (6854984448 bytes) from device: CUDA_ERROR_OUT_OF_MEMORY: out of memory
2019-07-30 03:35:51.119149: W tensorflow/core/common_runtime/bfc_allocator.cc:267] Allocator (GPU_0_bfc) ran out of memory trying to allocate 16.0KiB.  Current allocation summary follows.
2019-07-30 03:35:51.119173: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (256): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119191: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (512): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119208: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (1024): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119227: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (2048): 	Total Chunks: 1, Chunks in use: 1. 2.2KiB allocated for chunks. 2.2KiB in use in bin. 1.0KiB client-requested in use in bin.
2019-07-30 03:35:51.119246: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (4096): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119262: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (8192): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119279: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (16384): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119296: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (32768): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119314: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (65536): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119330: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (131072): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119347: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (262144): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119364: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (524288): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119381: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (1048576): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119398: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (2097152): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119415: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (4194304): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119432: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (8388608): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119449: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (16777216): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119466: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (33554432): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119485: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (67108864): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119502: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (134217728): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119519: I tensorflow/core/common_runtime/bfc_allocator.cc:597] Bin (268435456): 	Total Chunks: 0, Chunks in use: 0. 0B allocated for chunks. 0B in use in bin. 0B client-requested in use in bin.
2019-07-30 03:35:51.119537: I tensorflow/core/common_runtime/bfc_allocator.cc:613] Bin for 16.0KiB was 16.0KiB, Chunk State:
2019-07-30 03:35:51.119553: I tensorflow/core/common_runtime/bfc_allocator.cc:632] Chunk at 0x7fcc33000000 of size 2304
2019-07-30 03:35:51.119568: I tensorflow/core/common_runtime/bfc_allocator.cc:638]      Summary of in-use Chunks by size:
2019-07-30 03:35:51.119584: I tensorflow/core/common_runtime/bfc_allocator.cc:641] 1 Chunks of size 2304 totalling 2.2KiB
2019-07-30 03:35:51.119600: I tensorflow/core/common_runtime/bfc_allocator.cc:645] Sum Total of in-use chunks: 2.2KiB
2019-07-30 03:35:51.119618: I tensorflow/core/common_runtime/bfc_allocator.cc:647] Stats:
Limit:                  6854986957
InUse:                        2304
MaxInUse:                     2304
NumAllocs:                       1
MaxAllocSize:                 2304

You can run it on just CPU to get started. Add
import os
os.environ['CUDA_VISIBLE_DEVICES'] = ''

on top of the python script to bypass Nvidia GPUs.

You can run it on just CPU to get started. Add
import os
os.environ['CUDA_VISIBLE_DEVICES'] = ''

on top of the python script to bypass Nvidia GPUs.

Does the CPU and GPU training time have a big difference? How long does it take to train if you use a CPU?

https://github.com/hongzimao/pensieve/issues/82 The speed depends on your hardware. Since the model is not too large, CPU and GPU performed similarly in our experiment.

repo: hongzimao/pensieve


text:
Too many subrequests.

Hi,
on a blockchain, I'm trying to get the information that the transaction has been approved.
const confirmation = await connection.confirmTransaction({
        signature,
        blockhash,
        lastValidBlockHeight,
    },
    "finalized"
);

The confirmTransaction function assigns multiple get requests in the background to verify whether the transaction has been confirmed or not.
in this case "error: Too many sub-requests. Thus, employees can submit up to 50 sub-requests per request."
the error returns. I don't get errors when I do the same with Expressjs.
What am I doing wrong?

Hi @tolgaand !
Which platform do you run on? I think it's not Hono matter but the platform matter.

Hi @yusukebe , thanks for your comment.
For two days I thought it wasn't about hono.
But then I realized that when I try with frontend(next) and backend(express), there is no problem.
The code of the confirmTransaction function is here

@tolgaand
I've investigated. If you are running on Cloudflare Workers, then you can only make up to 50 external fetch sub-requests in the free plan.
https://developers.cloudflare.com/workers/platform/limits/
Maybe this is the issue.

@yusukebe thanks for your comment.
The '@honojs/node-server' library worked.
One last question; where can I deploy my project using this library?

The @honojs/node-server library worked.

Good!

One last question; where can I deploy my project using this library?

You can deploy it anywhere Node.js works. Version 16.x or 18.x would be good. If you like "serverless", maybe it will work on AWS lambda or Google Cloud Functions. Or you can make it runs on VPS or containers...

Hi, thank you for creating Hono,
do you have any example of how to use "@honojs/node-server" with AWS lambda (serverless)?

Hi @KailasMahavarkar !

do you have any example of how to use "@honojs/node-server" with AWS lambda (serverless)?

Not yet. I have never heard about Hono running on AWS. Let me know if you get it to work :)

authors: KailasMahavarkar tolgaand yusukebe

repo: honojs/hono


text:
🛑 TPB is down

In 71913e3, TPB ($TPB_SITE) was down:

HTTP code: 0
Response time: 0 ms

Resolved: TPB is back up in 2442be6 after 17 minutes.

repo: hoopybe/uptime


text:
Merged in DWX permissions

This PR added DWX required permissions to the AWS policy JSON file.

@akanto @prasanthj Can you please review this PR?
Thx.

Let's give this some more time for testing. Found some permissions are lacking few days back.

@prasanthj Just slack me your findings and missing permissions and I will add them to the merged file before we pull it in....

authors: odraese prasanthj

repo: hortonworks/cloudbreak


text:
CB-8663 Deploy IdBroker across multiple nodes

This change add in a new table for IdBroker's certs that will be used to
sync IdBroker nodes together.  It includes it's own master secret and
changes to the Knox IdBroker config provider.  This also includes the
necessary salt changes to have these files set and generated for just
IdBroker nodes.
Testing Done:
Brought 2 IdBroker nodes up with no issue.  If settings are incorrect
they fail to start.  Had member of IdBroker team confirm configuration
looks good and nodes respond correctly.
Brought up 1 IdBroker with no issue.
Brought up 1 IdBroker node, then upgraded to this fix and resumed it
with no issue.

This is the same as https://github.com/hortonworks/cloudbreak/pull/8929

LGTM. Feel free to merge when the checks have passed.

authors: keyki orngejaket


text:
ENGESC-6437. Use forceMetricsFetch for decommision data nodes ambari …

…request -> use the original requests in case of empty response
See detailed description in the commit message.

retest this please

with my change:
http://ci-cloudbreak.eng.hortonworks.com/job/cloudbreak-pull-request-builder-integration-test/16193/
failures:
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidAmbariBaseUrl
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidAmbariGpgKeyUrl
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidMpackUrl
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidRepoConfigsAll
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidStackBaseUrl
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidUtilBaseUrl
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidVersionDefFileUrl

without my change:
http://ci-cloudbreak.eng.hortonworks.com/job/cloudbreak-pull-request-builder-integration-test/16191/
failures:
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidAmbariBaseUrl
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidAmbariGpgKeyUrl
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidMpackUrl
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidRepoConfigsAll
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidStackBaseUrl
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidUtilBaseUrl
com.sequenceiq.it.cloudbreak.RepositoryConfigsTests.testValidVersionDefFileUrl

seems like that's exactly the same


text:
Fixed: Infinite scroll with searchbar and loading bug(#289)

Related Issues

https://github.com/hotwax/dxp-components/issues/289
Short Description and Why It's Useful
Removed the logic to re-render the infinite-scroll on queryString check that has been added in the previous PR.
Added a variable to check whether the scrolling can be enabled or not whenever users lands on the list page. For this, we have determined the height of the content part scroll and infiniteScroll component and if the height is less than 0 then only enabling the infinite-scroll component
Removed disabled as once the infiniteScroll is disabled it does not gets enabled again, hence removed the disabled property and instead used v-show to enable/disable infinite scroll.
Screenshots of Visual Changes before/after (If There Are Any)

Contribution and Currently Important Rules Acceptance

[x] I read and followed contribution rules

Verified and working fine in release v1.6.1.
https://jam.dev/c/7ce45f60-d381-416c-8f6b-125161e1dd90

repo: hotwax/facilities


text:
invalid JSON is being produced once formatted

Here is a content that is wrongly formatted
This is the content of a markdown file

```json
{
        "foo": "bar",
        "user_id": "2313",
        "scope": ["internal"]
}
```

This is the content of a markdown file

```json
{
  "foo": "bar",
  "user_id": "2313",
  "scope": ["internal"],
}
```

The extra comma at the end of the list lead to an invalid json
Here is my mdsf.json
{
  "$schema": "https://raw.githubusercontent.com/hougesen/mdsf/main/schemas/v0.0.2/mdsf.schema.json",
  "json": {
    "enabled": true,
    "formatter": [
      [
        "prettier"
      ]
    ]
  }
}

prettier 3.2.5 is installed and work well.

The point I raised in #146 is interesting here as I have no way to know what formatter is being applied.

It seems to me you are using jsonc format which supports comments and extra trailing comma
These two formats should be handled separately.
```json
{
        "foo": "bar",
        "user_id": "2313",
        "scope": ["internal"]
}
```

```jsonc
{
        "foo": "bar",
        "user_id": "2313",
        "scope": ["internal"] // some comment
}
```

it might be related to this https://github.com/prettier/prettier/issues/15956

The reason json is formatted as jsonc is because people often have comments in their json codeblocks, which isn't part of the specification.
But I just did a quick test and it seems that both prettier and deno supports formatting json files with comments. Sadly Biome does not expose the argument for allowing comments (https://github.com/biomejs/biome/blob/a6f5f0e8187912b389bf88ece65a51f1e02027a6/crates/biome_service/src/configuration/json.rs#L31).
I was already planning on introducing language “flavors” (css -> css, scss, sass, less, json -> json, jsonc, json5, sh -> sh, zsh, bash), which should fix the issue.

authors: ccoVeille hougesen

repo: hougesen/mdsf


text:
按照教程启动之后无法收到回信

背景: 在Telegram机器人中使用chatgpt

按照教程申请了一个Telegram机器人，并执行了如下流程的操作：

配置文件中编写了Telegram的token
配置文件中编写了自己chatgpt的token
配置文件中去掉了wechat 这行

go build之后运行，给自己的Telegram机器人发送信息没有回复，求解

按照教程docker启动后Exit

@sivanWu0222  麻烦把镜像删除之后重新运行试试
https://github.com/houko/wechatgpt/releases/tag/v2.9.3

拉取源码编译后台运行就ok了

repo: houko/wechatgpt


text:
OpenShift server failed

pi@raspberrypi:~ $ bypy info
<D> [04:24:06] Using requests.packages.urllib3 to disable warnings
Refreshing, please be patient, it may take upto None seconds...
Authorizing/refreshing with the OpenShift server ...
<E> [04:24:09] Exception:
<type 'exceptions.ValueError'> - No JSON object could be decoded
Stack:
  File "/usr/local/bin/bypy", line 11, in <module>
    sys.exit(main())
  File "/usr/local/lib/python2.7/dist-packages/bypy/bypy.py", line 3253, in main
    result = getattr(by, args.command[0])(*uargs)
  File "/usr/local/lib/python2.7/dist-packages/bypy/bypy.py", line 937, in info
    return self.quota()
  File "/usr/local/lib/python2.7/dist-packages/bypy/bypy.py", line 943, in quota
    return self.__get(pcsurl + 'quota', pars, self.__quota_act)
  File "/usr/local/lib/python2.7/dist-packages/bypy/bypy.py", line 690, in __get
    return self.__request(url, pars, act, 'GET', actargs, retry, addtoken, dumpex, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/bypy/bypy.py", line 668, in __request
    result = self.__request_work(url, pars, act, method, actargs, addtoken, dumpex, **kwnew)
  File "/usr/local/lib/python2.7/dist-packages/bypy/bypy.py", line 536, in __request_work
    if const.ENoError == self.__refresh_token(): # refresh the token and re-request
  File "/usr/local/lib/python2.7/dist-packages/bypy/bypy.py", line 889, in __refresh_token
    result = self.__get(url, pars, self.__refresh_token_act, retry = retry, addtoken = False)
  File "/usr/local/lib/python2.7/dist-packages/bypy/bypy.py", line 690, in __get
    return self.__request(url, pars, act, 'GET', actargs, retry, addtoken, dumpex, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/bypy/bypy.py", line 668, in __request
    result = self.__request_work(url, pars, act, method, actargs, addtoken, dumpex, **kwnew)
  File "/usr/local/lib/python2.7/dist-packages/bypy/bypy.py", line 518, in __request_work
    perr(formatex(ex))
  File "/usr/local/lib/python2.7/dist-packages/bypy/util.py", line 70, in formatex
    type(ex), ex, ''.join(traceback.format_stack()))

<E> [04:24:09] Maximum number (1) of tries failed.
OpenShift server failed, authorizing/refreshing with the Heroku server ...

不能用了吗？

I have the same problem....
the error informations were just the same.
 [04:24:09] Maximum number (1) of tries failed.
OpenShift server failed, authorizing/refreshing with the Heroku server ...

感谢反馈。
这个错误不要紧的，只是说OpenShift的授权服务器出错（后面还有一个heroku的，应该是通过了），而且只在第一次授权的时候出现。为了避免更多人把这个当做严重错误，我改了一下，现在只要最后授权成功就不报错了。

authors: TshineZheng dragon9001 houtianze

repo: houtianze/bypy


text:
Reduce go module changes

What
Redo the dependencies just adding the tink dependency only, reverting any other go module changes.
Why
It looks like there are other changes not required being made to the Go modules in stellar/go#2692.

Curious what procedure you ran to slim this down? Why go mod tidy can't result in the same outcome? Are all the tests still passing? It's hard to tell here.

All tests should pass, I think I ran it local. Merge it to your branch and CI will run. All I did was go get tink, then ran go mod tidy. Your go.mod changes look like you also upgraded some other dependencies.

Interesting. All I did was go get tink and go mod tidy as well. https://github.com/stellar/go/pull/2692/commits/7b68fda4ad233511211acff9f0f9072846cf79d7

authors: howardtw leighmcculloch

repo: howardtw/go


text:
NEXT RELEASE

Includes:

Rebranded Webex bots (renamed from Cisco Spark)
Google Hangouts connector
Reorganized tests

The tests look tight. Nice job.

authors: amplicity benbrown

repo: howdyai/botkit


text:
node are not labeled in output directed_graph

Hello,
Thank you for the putting together this package. I am testing it out and it is very fast.
My question is about the data input. I tried inputting a dataframe from panda and the algorithm runs fine with the GaussianPC function. However, I get a directed_graph with no node names. The output of directed_graph.nodes() is a series of numbers equal to the number of culumns in my input. Do the column names in the input correspond directly with the node numbers in the directed_graph?
Thank you

You are right, we omit node names, and use the columns' indexes (zero-indexed) instead. Hence, the node numbers in the directed_graph correspond to the column names in the order provided as data input.

Thank you for the clarification

Another question. The resultant network from running GaussianPC is a directed graph. but even though I provide a correlation matrix as part of the input, it is unweighted. Is there a way to generate a weighted graph? Or is acceptable to assign the correlation values as weights manually? Finally, is there a way to export the graph to be used as a weighted directed graph that can be edited/previewed/analyzed in cytoscape?

Thanks very much for the information and guidance.

repo: hpi-epic/gpucsl


text:
Any pre-built dynamic library or executable file for andriod?

Hi, Dear HPI team,
Thanks for the wonderful project. I'm conducting some network binrarization research and want to compare the speed of binray network versus its FP32 counterpart on cellphone. This repository might provide a convienent framework for testing. However, it is a long way to build the OpenBlas and the amalgamation module for ARM platforms. I've tried so for a long time but ony got a lot of errors.
I wonder if you have already compiled some library to run on Android platform. For example, the  jni_libmxnet_predict.so mentioned in the project, by which I could call for speedup testing.
Thanks very much.

Hi, I've successfully built the OpenBlas, however the amalgamation submodule seemed not to be built.
A lot of header files were not found...

Closing this, since we only support the new version from now on: https://github.com/hpi-xnor/BMXNet-v2

authors: Jopyth blueardour

repo: hpi-xnor/BMXNet


text:
Plugin Request: cmp-treesitter

Similar to https://github.com/hrsh7th/nvim-compe/tree/master/lua/compe_treesitter

Sorry. I have no plan to create treesitter source.
i hope someone do it.


text:
org/http4s/blaze/util/package.class is present twice in the classpath

org/http4s/blaze/util/package.class is present twice in the classpath
JarClassLoader: Warning: org/http4s/blaze/util/package$.class in lib/http4s-blaze-core_2.12-0.17.0-RC1.jar is hidden by lib/blaze-core_2.12-0.12.6.jar (with different bytecode)
JarClassLoader: Warning: org/http4s/blaze/util/package.class in lib/http4s-blaze-core_2.12-0.17.0-RC1.jar is hidden by lib/blaze-core_2.12-0.12.6.jar (with different bytecode)

So that depending on the final classpath order one might get in runtime:
java.lang.NoSuchMethodError: org.http4s.blaze.util.package$.End()Lscala/util/Right;

This package object is new in 0.17, so it doesn't affect 0.16.
The problem is that http4s-blaze-core (from the http4s project) and blaze-core (from the blaze project) are both in the same namespace.  We should move all the classes in http4s-blaze-core to a different package.

Even though we haven't caused a clash in 0.16, we probably ought to do the renaming in 0.16 and bubble it up, just to avoid any future problem.  The split package problem has existed for a long time.

This is fixed now, right?

Yes.

authors: Unisay aeons rossabaker


text:
Exposing extended information for a backend

#2696 introduces EmberClient, which exposes state on top of Client via subtyping.  Today on Gitter, a similar request of blaze-client was expressed by a user.  This is something we need a pattern for.
We agreed to merge #2696 as is, but we should pick a pattern and introduce it where applicable.
Options surfaced so far:

Subtyping (like #2696).  Makes FP people squeamish, and gets lost in middleware.
Pass extended state (e.g., pool) as argument to builder.  This is somewhat attractive, but the builders already have several options that go into making the pool.
Have (alternate?) builder methods that return some pair (Client, ExtendedState).

the EmberClient subtype has fought us on binary compatibility.
async-http-client effectively does option 2


text:
KeepAliveSuite.Keep-Alive flake Scala 3

==> X org.http4s.headers.KeepAliveSuite.Keep-Alive: header.parse(a.value) == right(a)"  0.085s munit.FailException: Failing seed: 1VE4-Kn23Ku3oLhvMg2G7YDpGmZxPwlxVDvK_x7wW_C=
You can reproduce this failure by adding the following override to your suite:
override val scalaCheckInitialSeed = "1VE4-Kn23Ku3oLhvMg2G7YDpGmZxPwlxVDvK_x7wW_C="
Exception raised on property evaluation.

Exception: org.http4s.ParseFailure: Invalid Keep-Alive header: Reserved token of list List(token, max) was found in the extensions.
at munit.ScalaCheckSuite.propToTry(ScalaCheckSuite.scala:98)
Caused by: org.http4s.ParseFailure: Invalid Keep-Alive header: Reserved token of list List(token, max) was found in the extensions.

Different test, same exception:
==> X org.http4s.headers.KeepAliveSuite.Keep-Alive: header.renderString == "name: value"  0.042s munit.FailException: Failing seed: mL7Ax3Y2spY7TC0xRCvVrn004HEAGoFRRtJaWoxiXTM=
You can reproduce this failure by adding the following override to your suite:

  override val scalaCheckInitialSeed = "mL7Ax3Y2spY7TC0xRCvVrn004HEAGoFRRtJaWoxiXTM="

Exception raised on property evaluation.
> Exception: org.http4s.ParseFailure: Invalid Keep-Alive header: Reserved token of list List(token, max) was found in the extensions.
    at munit.ScalaCheckSuite.propToTry(ScalaCheckSuite.scala:98)
Caused by: org.http4s.ParseFailure: Invalid Keep-Alive header: Reserved token of list List(token, max) was found in the extensions.

authors: hamnis rossabaker


text:
Don't depend on third-party APIs in our tuts

We keep failing intermittently in Travis due to third-party APIs:
[tut] *** Error reported at /home/travis/build/http4s/http4s/docs/src/main/tut/json.md:177
// <console>:49: warning: method run in class Task is deprecated: use unsafePerformSync
//        http4s.map(_.map(_.stargazers_count).mkString("\n")).run
//                                                             ^
// org.http4s.client.UnexpectedStatus: unexpected HTTP status: 403 Forbidden

This is the GitHub API rate limiting us.  We need something more predictable for our example to get more predictable builds.

I didn't realize we had tests using github.com too (#909).  Those don't 403, but they do cost us control of our own destiny.
We could dogfood our own server in the tests, though we might just as well justify dogfooding our client in server tests.  There is an embedded, zero-dependency server that we could use as well, if we're not allergic to com.sun in a test.


text:
404 Not Found

Hello,
I have a task of "reviving" someone else iOS app which uses your (Swifter) library.
I've encountered quite weird problem:
Here is the setup:

application has files in some location (lets say /serve on the phone (there is a folder called webapp and inside is index.html and folder res with some css files)
application creates server

server["/:path"] = shareFilesFromDirectory(servePath)
# servePath = "...serve/"

application presents webview pointing request to http://localhost:8080/webapp/index.html

Main problem is that I get Status code: 404
Here are my findings:

files are there - I'm listing whole folder tree and printing content of index.html
swifter (and webview) works
I replace

server["/:path"] = shareFilesFromDirectory(servePath)

with
server["/webapp/index.html"] = { .ok(.htmlBody("You asked for \($0)"))  }

and I get You ask for... in webview

if I add servePath /webapp and the end and remove it from webview request (making it http://localhost:8080/index.html) - webpage loads with out no style. I then went in with inspector and saw that all other files get 404 (so for example http://localhost:8080/src/main.css)]

Is there something with directories that is blocking (permissions or sth)?
Thx for the help

I'm having the same issue. I'm trying to serve local files and open them in a webview in the same app.  Like above, I can confim that files are there (e.g. I can open the files in webview directly with webView.loadFileURL) and I can confirm that Swifter is working by getting a reponse from it. But I get a 404 when trying to serve the local files via Swifter.
Please let me know if anyone has been able to find a workaround, or can recommend an alternative solution (library) for this problem).

authors: ajitam janek

repo: httpswift/swifter


text:
Questions about the object masks

Hi! This is an amazing work in image inpainting, and I'm really interesting the method to generate masks described in your paper. The problem is that when generating masks, object masks are first sampled. However, this repo only provides 4 object masks. Could you provide more samples and the method to construct the object masks? Thank you!

Thank you for your interest in our work! We used the ProFill (ECCV'20) object mask dataset to generate the random object mask. The entire object mask dataset can be downloaded here https://zengxianyu.github.io/iic/#object-masks

Thanks for your reply! It helps me a lot!

repo: htzheng/CM-GAN-Inpainting


text:
feat:新增主从模式和哨兵模式配置

新增主从模式和哨兵模式配置

well done

repo: huashijun/redis


text:
🛑 [PROD] Site e Loja is down

In dd5a384, [PROD] Site e Loja (https://testfy.com.br/) was down:

HTTP code: 500
Response time: 3129 ms

Resolved: [PROD] Site e Loja is back up in d59338c.

repo: hub-xp/testfy-status


text:
Deprecate show_profile

Remove deprecated show_profile from example schedule

Thanks for catching that.

authors: basepi whackyhack

repo: hubblestack/hubble


text:
开发模式下，不能直接访问在public下的静态文件

生产模式下 可以，
是不是webpack 需要加什么配置

config.default.js
  exports.static = {
    prefix: '/public/',
    dir: path.join(app.baseDir, 'public')
  }

应该是少这个配置吧

@DragWeb  不少这个，
如果少这个，生产环境也应该访问不了才对

确实有这个现象，http://localhost:7001/public/html/home/index.html 这个静态页面也访问不了，还有.ttf和.woff等字体文件   /public/client/font/.ttf    /public/client/font/.woff   @hubcarl

端口是9000   访问静态console信息：net::ERR_CONNECTION_REFUSED

@ZQun  你是用最新master代码嘛？如果是最新的，是可以直接访问的。如果egg-webpack 是旧版本，本地开发模式只能通过 http://localhost:9000/public/html/home/index.html

建议看一下egg＋webpakc构建流程：http://hubcarl.github.io/easywebpack/vue/dev

@hubcarl   谢谢，刚刚用了最新master没有问题！我之前用的旧版

authors: ChitaGideon DragWeb ZQun hubcarl

repo: hubcarl/egg-vue-webpack-boilerplate


text:
Allow decoding in sub-batches

This allows decoding in sub-batches for processing large batches such as videos:

If am understanding this correctly, we are trying to reduce vram consumption by dividing tasks into sub-batches?

Yeah, we have such nodes for normal encoding/decoding already, the VRAM spike otherwise can be huge with large batches common with videos.

I am still undecided if this is really necessary to be added to the decode node. If other parts of the pipeline are handling the full batch, why the decode unet need to make compromise and perform decode in smaller batch.
I wonder if there are existing nodes to split large video (image seq) down to small batches?

I am still undecided if this is really necessary to be added to the decode node. If other parts of the pipeline are handling the full batch, why the decode unet need to make compromise and perform decode in smaller batch.
I wonder if there are existing nodes to split large video (image seq) down to small batches?

Because it's not possible to decode a large batch at once. It will OOM, and we can't use other decoders as this node is only one with the compatible decoder. With AnimateDiff we have to use complete batches and it can't be split up, as it uses sliding context windows to handle large batches.
It could just as well be a separate too in this repo. As far as I know I can't import the VAE used here to my custom node for example, and as this node loads the VAE directly I'd have to add all that as well, hence the PR.

authors: huchenlei kijai

repo: huchenlei/ComfyUI-layerdiffusion


text:
config.yaml new loaction

Hey there,
config.yaml file is no longer under $HOME/.hueristiq/xurlfind3r/config.yaml , it's currently under /$HOME/.config/xurlfind3r/config.yaml , please update it in the readme file

Seems like there is another issue with intel x
[ERR] intelx: unexpected status code 400 received from https://2.intelx.io/phonebook/search/result?k=key&id=00000000-0000-0000-0000-000000000000&limit=10000
in the ID value it doesn't generate an actual search id , instead, it uses 00000000-0000-0000-0000-000000000000 which causes the call to crash

Hey there,
config.yaml file is no longer under $HOME/.hueristiq/xurlfind3r/config.yaml , it's currently under /$HOME/.config/xurlfind3r/config.yaml , please update it in the readme file

Ooh! yeah!

Let me check on the issues

authors: Hacktus enenumxela


text:
🛑 VGMdb API is down

In 5f82d8a, VGMdb API (https://vgmdb.info) was down:

HTTP code: 502
Response time: 356 ms

Resolved: VGMdb API is back up in e14e966 after 33 minutes.

repo: hufman/upptime


text:
Unrecognized arguments when using text-classification --train

The command:
autotrain text-classification --train --project_name test-autotrain
Results in:
[2023-10-25 15:31:31,073] [INFO] [real_accelerator.py:158:get_accelerator] Setting ds_accelerator to cuda (auto detect)
usage: autotrain <command> [<args>]
AutoTrain advanced CLI: error: unrecognized arguments: --project_name test-autotrain

The same command (with the rest of the arguments of course), but with autotrain llm works as expected and trains the model. Unsure why the argument is not being recognized.  Not passing --project_name of course results in the error "Project name must be specified" from run_text_classification.py line 281. Passing other arguments (that worked fine with autotrain llm) also doesn't work with text-classification, I just get an unrecognized arguments error. Other tried arguments include --use_peft, --use_int4, --learning_rate 5.5e-5.
autotrain version - 0.6.40
Updating to 0.6.41 still results in the same problem.

Upon further inspection with autotrain text-classification --help, it appears that many of the arguments for text-classification slightly differ from llm. Instead of --project_name as with llm, text-classification uses --project-name. text-classification also doesn't use peft or 4 bit quantization as --use_peft and --use_int4 are not options and there are no similar options displayed with --help. --learning_rate is also lr. I'm surprised that the passed arguments differ in name instead of using the same name, but, perhaps there is something going on with the multiple layers of ArgumentParser that I do not understand.

repo: huggingface/autotrain-advanced


text:
Translated the whole Chapter 3 to Thai

Hi, I have finished translating the whole Chapter 3 into Thai.
Please check and let me know if there's any corrections needed.
Cheers,
#64

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

authors: HuggingFaceDocBuilderDev a-krirk

repo: huggingface/course


text:
Allow to use service nodeport

More info here : https://github.com/huggingface/private-hub-package/issues/24

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Icon is to removing the warning on helm lint ;)

authors: HuggingFaceDocBuilder rtrompier

repo: huggingface/datasets-server


text:
add yahoo_answers_topics

This PR adds yahoo answers topic classification dataset.
More info:
https://github.com/LC-John/Yahoo-Answers-Topic-Classification-Dataset
cc @joeddav, @yjernite

feel free to merge/ping me to merge if there're no more changes to do

authors: lhoestq patil-suraj

repo: huggingface/datasets


text:
add W&I + LOCNESS dataset (BEA-2019 workshop shared task on GEC)

Name: W&I + LOCNESS dataset (from the BEA-2019 workshop shared task on GEC)
Description: https://www.cl.cam.ac.uk/research/nl/bea2019st/#data
Paper: https://www.aclweb.org/anthology/W19-4406/
Motivation: This is a recent dataset (actually two in one) for grammatical error correction and is used for benchmarking in this field of NLP.

Checkbox

[x] Create the dataset script /datasets/my_dataset/my_dataset.py using the template
[x] Fill the _DESCRIPTION and _CITATION variables
[x] Implement _infos(), _split_generators() and _generate_examples()
[x] Make sure that the BUILDER_CONFIGS class attribute is filled with the different configurations of the dataset and that the BUILDER_CONFIG_CLASS is specified if there is a custom config class.
[x] Generate the metadata file dataset_infos.json for all configurations
[x] Generate the dummy data dummy_data.zip files to have the dataset script tested and that they don't weigh too much (<50KB)
[x] Add the dataset card README.md using the template : fill the tags and the various paragraphs
[x] Both tests for the real data and the dummy data pass.

I created a clean PR where I also incorporated the suggested changes here: https://github.com/huggingface/datasets/pull/1449


text:
Pin rouge_score test dependency

Temporarily pin rouge_score (to avoid latest version 0.7.0) until the issue is fixed.
Fix #4734

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


text:
Update stackexchange license

The correct license of the stackexchange subset of the Pile is cc-by-sa-4.0, as can for example be seen here: https://stackoverflow.com/help/licensing

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

authors: HuggingFaceDocBuilderDev cakiki