text:
🛑 Auth-Bridge - Test 1 is down

In e550d88, Auth-Bridge - Test 1 ($AUTH_BRIDGE_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Auth-Bridge - Test 1 is back up in 9867940.


text:
🛑 Software Center - Test 1 is down

In 29d14ee, Software Center - Test 1 ($SOFTWARECENTER_TEST_1) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Software Center - Test 1 is back up in 1d81e2f.

source: gharchive/issue

repo: herrphon/upptime

license: MIT

license_type: permissive

license_source: github-api


text:
feat: add Fresh use to auto refresh expiration time

What type of PR is this?
feat

What this PR does / why we need it (English/Chinese):
en: add Fresh use to auto refresh expiration time
Example:
var once sync.Once

func main() {
	h := server.New(server.WithHostPorts(":8000"))
	store := cookie.NewStore([]byte("secret"))
	store.Options(sessions.Options{MaxAge: 10})
	h.Use(sessions.New("mysession", store))

	h.GET("/login", func(ctx context.Context, c *app.RequestContext) {
		s := sessions.Default(c)
		once.Do(func() {
			s.Set("key", "value")
			s.Options(sessions.Options{MaxAge: -1})
			s.Save()
		})
		i := s.Get("key")
		c.JSON(200, utils.H{
			"key": i,
		})
	}, sessions.Refresh(store))
	h.Spin()
}

Which issue(s) this PR fixes:
https://github.com/hertz-contrib/sessions/issues/7

为什么 Run go vet -stdmethods=false $(go list ./...) 没执行结束就停止了, licence 根本没有改动为什么错误了

这个有关联的 issue 吗？ 是遇到什么需求了吗？

模板有, kinggo 提的, 我无所谓

source: gharchive/pull-request

authors: Duslia Skyenought

repo: hertz-contrib/sessions


text:
Pile of misc stuff

Broken out by commit

Thanks for the updates!

Just FYI I'm very interested in getting some nice resources for interacting with Vault added.  We'll see how much time I have in the next month or so.

repo: hexedpackets/chef-vault

license: mit

license_source: bigquery


text:
Ignore images within 'do not render' class

img tags which has class="do-not-render" attribute would be ignored by the parser in case one would like to exclude particular images from Fancybox.

Do we have better solution for this feature?

Hi @tomap, done.

See #181

authors: Xuanwo changyuheng tomap

repo: hexojs/hexo-theme-landscape


text:
Update German VAT Rate with temporary reduction until the end of 2020

Closes #637

@rposborne We're not too far from the end of the year, but given the way things are, I wouldn't be surprised to see this reduction extended, so maybe it still makes sense to merge this?

Apparently the lower rate has not been extended: https://www.avalara.com/vatlive/en/vat-news/german-vat-rate-returns-to-19--1-jan-2021.html so I guess we can abandon this ^^

Apparently the lower rate has not been extended: https://www.avalara.com/vatlive/en/vat-news/german-vat-rate-returns-to-19--1-jan-2021.html so I guess we can abandon this ^^

Closing since this is no longer applicable.

Closing since this is no longer applicable.

authors: jarthod pmor

repo: hexorx/countries


text:
Unable to create build with flavor for iOS simulator

It is not possible to pass flavor name for iOS simulator build.
See lines 249-251 of file tasks/build/index.js.
Flavour arg is pushed only for !simulator condition.

Hi,
You are the first person to ever open an issue for Simulator 😄
There were multiple reasons of it not being there, First being the original author made it that way in 2020 and simulators aren't used heavily on Azure Pipelines and nor they can generate '.ipa' (at least to my knowledge). Also, is flavor even supported on simulator?
Solution
You can pass the --flavor your_flavor or try --flavor=your_flavor to the extraArgs and by pass this restriction easily. You can refer to readme.
I added extraArgs just for these edge cases and if Flutter team adds any new functionality.
Try extraArgs if in case for some reason it doesn't work. Feel free to re-open this issue.

I just came across this bug. The simulator build should not prevent setting a flavor. You may want to produce a simulator build in your pipeline as an artifact for QA to test with. You could have several flavors you are interested in testing with a simulator.

authors: SBerenda guulp hey24sheep


text:
Update README.md

Description
Give a description of what the changes are and what you have done with the things that you are commiting
Type of change

[] Bug Fix
[] New Feature
[X] Documentation
[] Enhancements

How has this been tested?
Where was this tested and what were the results of the test?
Ensure that you add some proof that this was tested and is functioning as expected
Checklist

[X] My code follows the style and contributing guidelines of this repo
[X] My code has been tested and will not break anything that is existing

Testing the template. This is what it looks like Odai, lmk if you want it to be changed at all thanks

It auto populates every time you make a PR, so...

Take another look at the notebook @heyodai


text:
滚动位置缓存问题

请问滚动位置缓存是必须依赖 cube-scroll 吗?
https://github.com/hezhongfeng/vue-page-stack-example/blob/master/src/views/main/MainList.vue

把以上文件中的 cube-scroll 换成普通滚动，返回时就无法记住滚动位置了。
<template>

    <stack-header :title="$t('home')"></stack-header>

</template>

这个插件不是独立存在的，是依赖于vue和vue-router的，所以很多行为是与vue和vue-router一致的。
你反应的这个问题属于Vue的自身特性
回归到你的问题本身，做出如下改动：

然后手动访问http://localhost:1234/main
这其中的变化就是涉及到整个页面滚动还是局部滚动，使用better-scroll恰巧解决了vue的这个问题，下面是我新搭建的非常干净的初始项目，你可以下载下来替换成keep-alive自行研究。
scroll-demo.zip

authors: hezhongfeng ipumpkinbomb

repo: hezhongfeng/vue-page-stack


text:
添加审批流按权限组独自发送钉钉通知的功能

审批流能按当前的审批权限组发送指定钉钉通知

你好，我理解工单审批的流程通知是通知到固定的一个目标。 实际上审批流可能会涉及不同的部门、小组。 如提交工单后，先由开发组leader审批， 然后再由系统运维组审批。  两个审批环节分属不同小组，单个审批环节的通知能支持通知到不同小组会更加友好

authors: cppmajor hjweddie

repo: hhyo/Archery


text:
Allow clearing all ClassDetails members

For complete XML mappings we need the ability to clear all members of a ClassDetails.
Might be ok/better to clear just "persistable" members (fields, getters and setters)

Ultimately this is probably better handled from ORM as the ability to add @Transient to all persistable members and removing them as we see an attribute mapping.

Closing in favor of https://github.com/hibernate/hibernate-models/issues/88 and https://github.com/hibernate/hibernate-models/issues/89

repo: hibernate/hibernate-models


text:
Backport of HHH-18675 to 6.6 branch

Cherry picked changes from main branch into 6.6 branch.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license
and can be relicensed under the terms of the LGPL v2.1 license in the future at the maintainers' discretion.
For more information on licensing, please check here.

https://hibernate.atlassian.net/browse/HHH-18675

Thanks

authors: beikov leonschenk

repo: hibernate/hibernate-orm


text:
HSEARCH-2108 Elasticsearch analyzers v2

https://github.com/hibernate/hibernate-search/pull/1017 Follows up
https://hibernate.atlassian.net/browse/HSEARCH-2108
I've tried to follow @gunnarmorling suggestion, this patch will add a new AnalyzerReference class to keep track of analyzers, locals or remotes. A remote analyzer is represented using the class RemoteAnalyzer.
It seems to work with custom-analyzers defined on Elasticsearch and the built-in one.

interface AnalyzerReference {
String getName(); // if that's needed here at all?
void close();
}

Analyzers can be lazy initialized, at the moment this is done using the DelegateNamedAnalyzer.
My plan was to assume that a reference to an analyzer can be lazy and therefore remove the need for DelegateNamedAnalyzer and therefore an additional wrapper.
As for the other remarks, I'll try to apply them.

repo: hibernate/hibernate-search


text:
🛑 kiwifarms.st is down

In 840946d, kiwifarms.st (https://kiwifarms.st) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kiwifarms.st is back up in 6fe366b after 29 minutes.

repo: hickoryhouse/kf


text:
🛑 kiwifarms.st is down

In a859eaf, kiwifarms.st (https://kiwifarms.st) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kiwifarms.st is back up in dd2a493 after 5 minutes.


text:
🛑 kiwifarms.st is down

In 6cce8e6, kiwifarms.st (https://kiwifarms.st) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kiwifarms.st is back up in c12fea0 after 12 minutes.


text:
Refactored to use FlatList in place of deprecated ListView

This is an improved version of the pull request created by @rollymaduk at #14. Changes:

Removed the .idea folder
Fixed an issue where the scope of this.renderList() function is gone due to its assignment in the expression (renderList || this.renderList)
Resolve conflicts in index.js
Adding SafeAreaView to KeyboardAvoidingView - otherwise on iPhone X the textbox will be pushed up too high and covered by the "notch"

This PR addresses issue #8
@hiddentao do let me know if any updates is needed. Looking forward to having it merged because otherwise the component breaks in RN 0.60. Thank you!

Great work! I see you're still adding commits though. I shall wait until you feel it's complete.

@hiddentao it should be completed now. Let me know if you identify anything that needs to be changed or fixed!

@hiddentao and thank you for reviewing!

@ryanphung Looks good, just one small fix left.

@hiddentao Fixed in latest commits.

authors: hiddentao ryanphung


text:
🛑 EarthquakeEarlyWarningPlus is down

In 7b1f75c, EarthquakeEarlyWarningPlus (https://discord-status-api.glitch.me/api/v1/status/460323119651880960?token=$API_TOKEN) was down:

HTTP code: 418
Response time: 13636 ms

Resolved: EarthquakeEarlyWarningPlus is back up in fb7c6f0.


text:
Error with Object.Freeze() in IE 11

Hi, Thanks for the plugin!
When my site is run in IE 11 there is an error with the "object.freeze()". Do you know a workaround I can put in? Thanks!

If I float a fix are you capable of building a new distributable locally to test?
I’m guessing this is the issue:
https://github.com/datorama/akita/pull/95/commits/8a6306542595a8e2230b09299cff4be35fd3af7b
https://github.com/brandonroberts/ngrx-store-freeze/issues/7
Technically we don’t support IE11 any more but my intention was to try and not break it until 10.0 and then officially end support, which is likely the next release.

Sure I can give it a shot! Thanks!
Thanks,
Christopher

On Dec 11, 2019, at 6:52 PM, Josh Goebel notifications@github.com wrote:

If I float a fix are you capable of building a new distributable locally to test?
I’m guessing this is the issue:
datorama/akita@8a63065
brandonroberts/ngrx-store-freeze#7
Technically we don’t support IE11 any more but my intention was to try and not break it until 10.0 and then officially end support, which is likely the next release.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Build a new version against https://github.com/highlightjs/highlight.js/pull/2319 and test please.

Thanks, I built and tested, but still get the same error. I think the function Object.freeze(o); just doesn't exist in IE 11.

If this section of the code is removed it still works well (not sure what else is affected!) but in my app its cool.. maybe performance is slightly affected? I'm using highlight.js for a handful of  sql code blocks.
If you have another idea I'd appreciate it! - otherwise I can use the code w/ this block commented out. (lines 1130 - 1151 in src/highlight.js)

Freeze exists. The error is telling you that.
Could you add some logging and console.log both the object and property right before freeze is called and let me know which item or property it’s blowing up on?
Commenting it out will probably work as a quick fix. This code prevents language plugins from corrupting the parser itself by modifying the shared regexes - which it turns out our own languages were doing in the past (by accident).

Good point 👍
Yes - here's a few few pics. It seems to be because the first object is a string, not an "object" -

To test out, I changed the order of the object array to put one of the "objects" first to see if the function would successfully complete. It fails in my console.log at the freeze check with the object error, but should not hit this at runtime because the first conditions are true.

Here is  rerun with the console.log removed from that section:
Now it works until it gets to a string in the array.

What do you think?

btw, I apologize for using ie 11 😭 my personal feeling is that IE does not qualify as a browser 😄

In ES5, if the argument to this method is not an object (a primitive), then it will cause a TypeError. In ES2015, a non-object argument will be treated as if it were a frozen ordinary object, and be simply returned.

Ah.  Can you try the PR again?  I modified it so we don't try to freeze any of the strings.

btw, I apologize for using ie 11

No problem.  I appreciate your reporting this.  My intention was always for 9.x to be a stable release series that people could continue to use for a while if they needed support for IE11 and older browsers while 10.0 moves on to newer things.  So I'd def like to see this fixed if we can. :)
But we don't actively test new changes in IE11.

Thanks, that works very well. I appreciate it!

Releasing 9.17.1 with the fix.


text:
enh(scala) fix triple quoted string

Resolves #2986

Checklist

[x] Added markup tests, or they don't apply here because...
[x] Updated the changelog at CHANGES.md
[x] Added myself to AUTHORS.txt, under Contributors

I'd add another test of multi line string:
val multiLineString =
  """aaa
    |ddd
    |sdfa""".stripMargin

should produce:
aaa
ddd
sdfa

and:

val multiLineString =
"""aaa
|ddd
|sdfa"""

should produce:

aaa
|ddd
|sdfa

Code run at [Scastie](https://scastie.scala-lang.org/N2V8tPHcQguXehJyhxD4pA).

If you wanted to contribute additional tests to the project (expanding on strings.txt) that'd be great... long-term it'd be nice to test all the different types of strings, escaping of special chars, etc...

I'd add another test of multi line string:

Of course our parsing engine doesn't care about the how the string is interpreted, we just highlight it. So your last two examples are irrelevant in our context - as far as I can tell. The highlighted is the same in both cases, regardless of what the end result it inside the runtime.

authors: joshgoebel toshetah


text:
Update README.md

fixed a typo

Changes

Checklist

[ ] Added markup tests, or they don't apply here because...
[ ] Updated the changelog at CHANGES.md

Thanks!

authors: Mellaoui joshgoebel


text:
Started a pull request template

Started creating a pull request template. Suggestions for what it should include are welcome.

Uglify -> tensor change is there so that the tests pass.
I added your other changes.

In the Description section, perhaps it is useful to ask for a link to a Github issue or Slack discussion related to the PR and what it addresses?
Good idea. Not sure how we can link to a Slack discussion but an issue would be helpful.

repo: higlass/higlass


text:
Questions about two stage training in PETR

Thank you for sharing the code! I notice that, PETR is set to be two-stage in the code, i.e., top K proposals from encoder output are selected as the query embedding as well as the  initial reference point in the decoder. This is also very similar to the two-stage version of Deformable-DETR.
However, in section 3.3 of the paper, the authors mentioned that the query embeddings are randomly initialized and learnt, which is not a two-stage way. I wonder if the reported results are from two-stage models or one-stage ones. Besides, how much improvement can the two-stage variant bring?

In PETR, they used randomly initialized queries without query positional encoding from reference points. So, section 3.3 seems correct with the code of this repo.

while two-stage deformable DETR embedded their queries with their initial bboxes.

In PETR, they used randomly initialized queries without query positional encoding from reference points. So, section 3.3 seems correct with the code of this repo.

Thank you for your answer! I check the code and i think that, the two-stage mode (default setting in the code) denotes that the initial reference points for the decoder are initialized from the top 100 proposals, while the query embedding vectors are still randomly initialized.
I check the code in opera/models/utils/transformer.py, line 856-908, encoder features with high confidence are selected as proposals, and K keypoint coordinates are predicted. The keypoints are used as initial reference points in the decoder (Note that the deformable cross-attention use 17 reference points). Hence, i think there are still some difference between section 3.3, where the locations of initial reference points are randomly initialized and learnt. I am a little curious here how much improvement this modification can bring. Actually, such setting is quite reasonable.
This setting is very close to the recent DINO, where they only use positional information from encoder proposals and use randomly initialized content vectors for query. DINO says this will yield better performance.

Hence, I think there is still some difference between section 3.3, where the locations of initial reference points are randomly initialized and learned.
-> could you let me know where is that comment in the paper? It is written that _"Concretely, given K randomly initialized joint queries Qjoint ∈ RK×D, the joint decoder takes the joint locations of each full-body pose predicted by preceding pose decoder as their initial reference points and then further reﬁne the joint locations."
This setting is very close to the recent DINO, where they only use positional information from encoder proposals and use randomly initialized content vectors for queries. DINO says this will yield better performance.
-> The DINO uses mixed query selection that set initial reference point as content query and randomly initialized positional encoding while this repo set randomly initialized value as content query also.
Thank you for your feedback :)

I check the code and I think that the two-stage mode (default setting in the code) denotes that the initial reference points for the decoder are initialized from the top 100 proposals, while the query embedding vectors are still randomly initialized.
-> Yes, I think so too!

The DINO uses mixed query selection that set initial reference points as content queries and uses randomly initialized positional encoding while this repo set randomly initialized values as content queries also.
-> I have not finished reading DINO's code. But I think the idea of only passing position information of proposals are quite similar here.  Thank you very much!

authors: dae-sun flyinglynx

repo: hikvision-research/opera


text:
[question] Custom callback for logging action, observation, reward, info and done at each timestep

Hello,
I'd like to log the value of the following variables at each timesteps during training: action, observation, reward, info and done (for debugging an environment). I understand these values can be accessed with a custom callback. I had a look at the examples provided in the documentation but I couldn't adapt them to my problem. Here is a minimal example:
from stable_baselines.common.callbacks import BaseCallback
from stable_baselines import PPO2

class LoggingCallback(BaseCallback):

    def __init__(self, verbose=0):
        super(LoggingCallback, self).__init__(verbose)

    def _on_step(self) -> bool:
        """
        How to print action, observation, reward, done and info from env.step() ?
        """
        return True

model = PPO2('MlpPolicy', 'Pendulum-v0', verbose=1)
model.learn(5000, callback=LoggingCallback())

I know that you don't do consulting but if you could point me in the right direction, that would be very appreciated. Is this the right approach? Are you aware of someone else who attempted something similar? Thanks.

Hello,
the information you are looking for is normally available in self.locals of the callback.
Anyway, I would recommend you to use Stable-Baselines3 which has a cleaner code (and easier to tweak ;) ).

Thanks I'll have a look at your suggestions.

authors: PierreExeter araffin

repo: hill-a/stable-baselines


text:
What exactly does the output printed to the standard output mean when verbose=1 in DQN?

When verbose== 1 in DQN, what exactly does the produced output represent? I haven't yet looked at the source code, and, of course, the answer lies there. The documentation for verbose only says

verbose – (int) the verbosity level: 0 none, 1 training information, 2 tensorflow debug

Anyway, sometimes it produces some output like this
--------------------------------------
| % time spent exploring  | 2        |
| episodes                | 100      |
| mean 100 episode reward | -59.7    |
| steps                   | 1841     |
--------------------------------------
--------------------------------------
| % time spent exploring  | 2        |
| episodes                | 200      |
| mean 100 episode reward | -15.3    |
| steps                   | 2452     |
--------------------------------------
--------------------------------------
| % time spent exploring  | 2        |
| episodes                | 300      |
| mean 100 episode reward | -15.2    |
| steps                   | 3058     |
--------------------------------------
...

and sometimes it doesn't produce anything. I think this also depends on the number of training time steps. So, what exatly do these values mean? What does episodes represent? Is it the number of episodes passed until that point? If yes, does mean 100 episode reward mean the average of the returns obtained in all the last 100 episodes? What does % time spent exploring exactly mean? It's always 2 (apparently).
I was trying to compare this output with the output that is produced by the SB's monitor, but they are different, as SB's monitor writes the sum of rewards obtained in an episode, for all episodes.

What does episodes represent?
Is it the number of episodes passed until that point?

Yes, total number of episode down so far.

If yes, does mean 100 episode reward mean the average of the returns obtained in all the last 100 episodes?

yes

What does % time spent exploring exactly mean? It's always 2 (apparently).

this is the epsilon of the epsilon-greedy exploration used by DQN (percentage of random action taken). Please read more about RL and DQN if this is unclear to you.

as SB's monitor writes the sum of rewards obtained in an episode, for all episodes.

You can easily recompute mean 100 episode reward using the Monitor file.
In fact, for other algorithms, ep_rew_mean is computed using the Monitor and is the mean over the last 100 episodes.
If you want more consistent logging, please take a look at Stable-Baselines3 ;)
(and please read the DQN section in the migration guide too).

closing in favor of https://github.com/DLR-RM/stable-baselines3/pull/803

authors: araffin nbro


text:
🛑 DSM is down

In 8352079, DSM (https://dsmcf.klib.cn) was down:

HTTP code: 520
Response time: 10906 ms

Resolved: DSM is back up in a980ea2 after 8 minutes.


text:
Bump react-docgen-typescript dependency to 2.0.0

Hi,
Is it possible to bump react-docgen-typescript dependency's version to 2.0.0?
Context
It seems that there's an issue fixed inside react-docgen-typescript dependency when using typescript version 4.3
TypeError: (tag.text || "").trim is not a function.
code fix : https://github.com/styleguidist/react-docgen-typescript/issues/356
new version on npm : https://www.npmjs.com/package/react-docgen-typescript
Thanks 🙂

I will file a PR for this change!

There is an PR on this https://github.com/hipstersmoothie/react-docgen-typescript-plugin/issues/42 but not merged yet, unfortunately.

authors: michelengelen ptrhck yanckst


text:
feat: add segment for user tracking

Try out this version of the Hiro Wallet - download extension builds.

Add most events in the wallet
Events implemented

Generate new Secret Key: When user generates new Secret Key
Copy Secret Key to clipboard: When user selects option to copy Secret Key to clipboard
Copy address to clipboard: When user selects option to copy address to clipboard
Choose to create account: When user chooses to create new account from app menu
Choose to change network: When user chooses to change network from app menu
Change network: When user selects network
Add network: When user submits new network
Lock session: When user locks session manually
Sign out: When user signs out manually
View transaction: When user selects transaction for view in Explorer
Broadcast transaction: When user submits transaction for broadcast
Submit invalid Secret Key
Submit valid password:
Select asset for send

All events include :

Anonymous ID for user by account
User agent (string)
Version (string)
Timestamp
Selected network (string: mainnet, testnet, devnet or other)

@kyranjamie We can do this.
const { onCopy, hasCopied } = useClipboard(secretKey || '');
const onCopyTracked = useAnalyticsWrapper('Copy to Clipboard')(onCopy)
const toaster = useToaster();
const onCopyToClipboard = useCallback(() => {
 onCopyTracked();
 toaster('Some message');
}, []);

@kyranjamie I would like get this ready for QA but I need to set the secrets env SEGMENT_WRITE_KEY just like SENTRY_DSN. Shall I contact devops for this ? We need to set a different KEY for the PR build (staging KEY) than the production one.

@markmhx's document say underscore case, not kebab

@kyranjamie FYI I will squash all the commits at the end into one clean commit for the SEM release.

@kyranjamie FYI I will squash all the commits at the end into one clean commit for the SEM release.

I wouldn't recommend this. What if we need to revert one commit? Also makes history less useful. You could drop all the semantic release dev commits if you really want, but wouldn't squash everything.

@kyranjamie Yes I meant just the commits of this PR only.

This is looking better since I see the consent prompt now upon first installing the extension:

However, can we get this content embedded into the normal page structure instead of showing it as a modal on top of an empty page?
This is how it's currently integrated for the desktop wallet upon installation:

This format seems more appropriate given the context, and it prevents users from clicking to dismiss (and implicitly deny) around the content area (as I did accidentally while testing).

Note as well that the copy needs to be updated generally to match that shown above in the desktop wallet.

@markmhx Sure I will update it to look like the desktop wallet.

We don't appear to be changing the page route or path between page states, nor changing the page title, which appears to make it impossible to distinguish between various page views e.g. landing on the index upon installation, then proceeding to the "View Secret Key" screen then "Set password", etc.:

Would it be possible update how we handling routing here so that the path does reflect the current state? Or somehow provide a simulated distinct route to Segment for each view regardless so it knows how to differentiate?

@markmhx Yes ideally it should work, but in the wallet we have a pretty weird implementation of the router: the view does not match the route. Since we don't have many 'pages', I think for the time (until we refactor this router) we can just trigger the event for each view in the code. wdyt ?

Yep let's go with whatever instrumentation-based customizations are needed here so the data is reported to Segment as if the router kept the route in sync with the view. 👍

Looking good otherwise in Mixpanel:

For the "broadcast_transaction" event, let's include property "type" with "transfer", "deploy" and "execute" as possible values so we can distinguish types?

Separately, it appears that we aren't firing for "Transaction state change" events yet, which is the only other one we'll need for this particular release:

I'm also noticing we'll need to report the "network" property a bit differently to protect possible PII with custom URLs.
Current:

Proposed:

Would also be useful to have using_default_hiro_api: boolean

@kyranjamie Note that this is not ready for review.

Would also be useful to have using_default_hiro_api: boolean
Done

Thanks @kyranjamie for your yesterday's review, I made the changes.  It's ready again for review.

I tested tracking for transaction state changes today and got partial results:

No event seen in Segment for the initial change to "submitted"
Event seen for change to "pending" but no "time_since_last_state" attribute compared to "submitted" state
No event seen for "microblocks" (though it transitioned through one fairly quickly)
Event seen for "success_anchor_block" but only after I revisited the wallet's full-page tab hours later and with a corresponding (later) timestamp instead of time it was included. Can we not trigger events if tabs aren't in view / active?

Thanks @markmhx for the feedback, I will check it out and fix it.

How complicated would it be to add time_since_broadcast as an attribute for all transaction_state_change events as well? That way we can measure total time to anchor block inclusion not just since last state.
Separately, we should update the name for transaction_state_change to change_transaction_state (imperative verb) in light of our naming standards.

@markmhx It's not difficult to add time_since_broadcast, but we should be aware that the time diff might be slightly off, because for broadcast (submitted) we use local time (user machine time) while the other datetime are based on the api/nodes. We could improve this measurement later by adding some clock synchronisation.

@markmhx When you say 'Event seen for "success_anchor_block" but only after I revisited the wallet's full-page tab hours later and with a corresponding (later) timestamp instead of time it was included. Can we not trigger events if tabs aren't in view / active?'
Do you mean that we should not trigger those events while the tab with the wallet is still open but the user is not on the tab currently and we should trigger those only if he click on the tab again ?

We want to trigger these events regardless of whether the tab is currently active. In my testing it appeared as though they were not triggered when the tab was inactive.

authors: beguene kyranjamie markmhx zone117x

repo: hirosystems/stacks-wallet-web


text:
feat: bitcoin fees query

Try out this version of the Hiro Wallet - download extension builds.

This PR adds the bitcoin fee estimates query as a precursor to reworking the existing fees component for the new send form.
Using endpoint: https://github.com/Blockstream/esplora/blob/master/API.md#fee-estimates
This endpoint returns fee rates that we use * tx byte length to get the fees we will suggest to the user. We need to decide what block confirmations we want to target to suggest a low, middle, and high fee.

We can merge this as a first step, but I'm having to make some more changes to get the different blockchain fee estimate types to work together. I have another working branch off this one.

Hoping I am leaving this in a place it can be merged and worked with if needed for the fees component.

@kyranjamie is this ok to merge now?


text:
usage is having a problem

slack-history-export -t my_oatuh_token -u my_username -f output.json
gives this output:
workingError: missing_scope
    at Users.BaseClass.throwError (/usr/local/lib/node_modules/slack-history-export/node_modules/slack-api-client/lib/api/common/base_class.js:15:14)
    at /usr/local/lib/node_modules/slack-history-export/node_modules/slack-api-client/lib/api/common/base_class.js:44:37
    at Request.callback (/usr/local/lib/node_modules/slack-history-export/node_modules/superagent/lib/node/index.js:691:12)
    at Stream.<anonymous> (/usr/local/lib/node_modules/slack-history-export/node_modules/superagent/lib/node/index.js:922:12)
    at emitNone (events.js:91:20)
    at Stream.emit (events.js:185:7)
    at Unzip.<anonymous> (/usr/local/lib/node_modules/slack-history-export/node_modules/superagent/lib/node/utils.js:108:12)
    at emitNone (events.js:91:20)
    at Unzip.emit (events.js:185:7)
    at endReadableNT (_stream_readable.js:974:12)```

did I not specify the correct flags on my Slack app to gain access to private messages? or is there something else I need to do first?

same here

It works if you use legacy tokens (generated here) instead of the new Slack app tokens.

@17cliu's approach works for me, I think it should be mentioned in README file.
(And @17cliu's headpic is super cool btw 😄 )

Thanks @ajhsu! :D

repo: hisabimbola/slack-history-export


text:
web_demo文件缺失，train_web并不是web_demo的内容

web_demo文件缺失，train_web并不是web_demo的内容

https://github.com/hiyouga/ChatGLM-Efficient-Tuning/issues/289

authors: couldn hiyouga

repo: hiyouga/ChatGLM-Efficient-Tuning


text:
Why modifying down_proj in llama?

Hello,
Thank you very much for this implementation.
In the Llama implementation, I wonder why and how you choose to edit the down_proj layer instead of gate_proj or up_proj in the MLP module? Thank you very much!
Best,
Wenyue

I also have the same question.

authors: Wenyueh loganvaz

repo: hiyouga/FastEdit


text:
4张M40 配置，使用accelerate启动训练，出现TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'

我在5天前更新的Factory代码。今晚启用accelerate  想进行多GPU训练。查阅以前版本的readme.
先执行了accelerate config
我的配置图下:
compute_environment: LOCAL_MACHINE
debug: true
deepspeed_config:
  deepspeed_config_file: /Micla/Project/LLaMA-Factory/config/ds_config.json
  zero3_init_flag: true
distributed_type: DEEPSPEED
downcast_bf16: 'no'
dynamo_config:
  dynamo_backend: INDUCTOR
  dynamo_mode: default
  dynamo_use_dynamic: false
  dynamo_use_fullgraph: true
enable_cpu_affinity: false
machine_rank: 0
main_training_function: main
num_machines: 1
num_processes: 4
rdzv_backend: static
same_network: true
tpu_env: []
tpu_use_cluster: false
tpu_use_sudo: false
use_cpu: false

deepspeed_config_file:内容如下:
{
  "train_batch_size": 32,
  "gradient_accumulation_steps": 8,
  "steps_per_print": 2000,
  "zero_optimization": {
    "stage": 3,
    "allgather_partitions": true,
    "allgather_bucket_size": 5e8,
    "overlap_comm": true,
    "reduce_scatter": true,
    "reduce_bucket_size": 5e8,
    "contiguous_gradients": true
  },
  "fp16": {
    "enabled": true
  }
}

这是我的启动命令：  （我是用一遍webui训练界面自动获取相关命令后再修改前缀）
accelerate launch /Micla/Project/LLaMA-Factory/src/train.py \
    --stage sft \
    --do_train True \
    --model_name_or_path THUDM/glm-4-9b \
    --preprocessing_num_workers 16 \
    --finetuning_type lora \
    --template default \
    --flash_attn auto \
    --dataset_dir data \
    --dataset identity,wikipedia_zh \
    --cutoff_len 1024 \
    --learning_rate 5e-05 \
    --num_train_epochs 3.0 \
    --max_samples 100000 \
    --per_device_train_batch_size 4 \
    --gradient_accumulation_steps 8 \
    --lr_scheduler_type cosine \
    --max_grad_norm 1.0 \
    --logging_steps 5 \
    --save_steps 100 \
    --warmup_steps 0 \
    --optim adamw_torch \
    --packing False \
    --report_to none \
    --output_dir saves/GLM-4-9B/lora/train_2024-07-01-02-00-52 \
    --fp16 True \
    --plot_loss True \
    --ddp_timeout 180000000 \
    --include_num_input_tokens_seen True \
    --deepspeed /Micla/Project/LLaMA-Factory/config/ds_config.json \
    --lora_rank 8 \
    --lora_alpha 16 \
    --lora_dropout 0 \
    --lora_target all

出现的错误：
[rank3]:   File "/home/micla/.conda/envs/llama_factory/lib/python3.11/site-packages/accelerate/accelerator.py", line 1618, in _prepare_deepspeed
[rank3]:     "train_batch_size": batch_size_per_device
[rank3]:                         ^^^^^^^^^^^^^^^^^^^^^
[rank3]: TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'

我觉得应该是配置上有点问题，但是我发现不了，想请求帮助。 我的机器是M40*4 ，询问了GPT4告诉我是不支持bf16，上述问题也先在GPT询问，但是它一直让我修改配置，错误还是持续，所以想在这问问

使用：https://github.com/hiyouga/LLaMA-Factory/blob/main/examples/deepspeed/ds_z3_config.json

使用：https://github.com/hiyouga/LLaMA-Factory/blob/main/examples/deepspeed/ds_z3_config.json

谢谢，晚点我会试试

使用：https://github.com/hiyouga/LLaMA-Factory/blob/main/examples/deepspeed/ds_z3_config.json

我使用了这份json, 目前的错误还是一样：TypeError: unsupported operand type(s) for *: 'NoneType' and 'int'

我昨天使用了这配置，（去除了fp16   机器不支持）运行后它提示我显存不足，我依照GPT的命令修改了配置batch size 和其他参数，报错了，请问有什么参数是不允许被修改的吗
命令如下：
accelerate launch /Micla/Project/LLaMA-Factory/src/train.py     --stage sft     --do_train True     --model_name_or_path THUDM/glm-4-9b     --preprocessing_num_workers 16     --finetuning_type lora     --template default     --flash_attn auto     --dataset_dir data     --dataset identity,wikipedia_zh     --cutoff_len 1024     --learning_rate 5e-05     --num_train_epochs 3.0     --max_samples 50000     --per_device_train_batch_size 2     --gradient_accumulation_steps 4     --lr_scheduler_type cosine     --max_grad_norm 1.0     --logging_steps 5     --save_steps 100     --warmup_steps 0     --optim adamw_torch     --packing False     --report_to none     --output_dir saves/GLM-4-9B/lora/train_2024-07-01-02-00-52     --fp16 True     --plot_loss True     --ddp_timeout 180000000     --include_num_input_tokens_seen True     --deepspeed /Micla/Project/LLaMA-Factory/config/ds_z3_config.json     --lora_rank 4     --lora_alpha 8     --lora_dropout 0     --lora_target all

authors: Micla-SHL hiyouga

repo: hiyouga/LLaMA-Factory


text:
FEAT: add HF tags for models that have been trained with llama-factory

Hi @hiyouga !
Great work on the Llama-Factory library ! 🚀
I would like to propose a new feature request: model tagging
With transformers 4.37.0 we added model tagging support by automatically tagging models on the Hub. That way you could sort models that have a specific tag, e.g. it you want to filter models that have the tag trl you could use think link: https://huggingface.co/models?other=trl / so for llama-factory: https://huggingface.co/models?other=llama-factory
I see it is already done in the get_modelcard_args method but add_model_tags enables you to push that tag even if you don't call trainer.push_to_hub and simply calling model.push_to_hub() will automatically push the model + the llama-factory tag
Let me know if this PR makes sense, otherwise we can also close it as technically the tags are already pushed, this PR would just cover the case where users use your trainer without pushing the trainer itself but the model.

Hi @younesbelkada ! Thanks for adding this patch, we are willing to utilize the new feature in transformers 4.37.0.
However, we found the implementation of push_to_hub in the Hugging Face's Trainer a bit strange: [1]

"model_tags" would be only appended when the users pass the "tags" argument to push_to_hub.
It would result in duplicate tags if there is an overlap between "model_tags" and "tags".

I am curious about the reason behind this design. Looking forward to hearing back from you.
[1] https://github.com/huggingface/transformers/blob/v4.37.2/src/transformers/trainer.py#L3737-L3747

Hi @hiyouga
Thanks!
I had a look at your comment, I think that I did a mistake when designing that logic, indeed we should always push the tag if model.add_model_tags() is called. I made https://github.com/huggingface/transformers/pull/29009 which should solve this unintended behaviour
Regarding your second point, there shouldn't be any duplicated tag I think, the block:
                if model_tag not in kwargs["tags"]:
                    kwargs["tags"].append(model_tag)

Circumvents that + even if multiple duplicated tags exists on the model card (which is less likely to happen give that guard + https://github.com/huggingface/transformers/blob/main/src/transformers/utils/hub.py#L1142 ) on the frontend they'll be always displayed a as a single tag. See: https://huggingface.co/ybelkada/test-bert-tags/commit/631bcabcc22cf313dd63441a85b122317fce6680
Let me know what do you think !

@younesbelkada Thanks! I think the above modification is fine, and this PR could now be safely merged.

authors: hiyouga younesbelkada


text:
🛑 Griffo is down

In 6e87b89, Griffo (https://www.griffo.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Griffo is back up in 699ee84 after 16 minutes.

repo: hjstrauss/MonitorMySites


text:
🛑 LM Bogen WSV is down

In 9484548, LM Bogen WSV (https://www.lmbogenwsv.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LM Bogen WSV is back up in 7cfd6c6 after 7 minutes.


text:
🛑 Griffo is down

In 21cf9fa, Griffo (https://www.griffo.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Griffo is back up in 3a63671 after 8 minutes.


text:
🛑 HJStrauss is down

In a281ac3, HJStrauss (https://www.hjstrauss.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: HJStrauss is back up in b1a31b4 after 33 minutes.


text:
🛑 LM Bogen WSV is down

In af23a49, LM Bogen WSV (https://www.lmbogenwsv.de) was down:

HTTP code: 0
Response time: 0 ms

Resolved: LM Bogen WSV is back up in 21d67f5 after 7 minutes.


text:
Dummy PR for DDD diffs

This is to allow people to leave comments on the diffs.

We should bring these proposals and openssl/openssl#17184 together. That PR suggests some things which have an overlap with what is proposed here. It also proposes new APIs that will be needed for the future (not necessarily for MVP). We should figure out how your suggestions and that PR fit together.

authors: hlandau mattcaswell

repo: hlandau/openssl


text:
An upstream regression pulled in d6c5d18

What actually happened?
When #+SETUPFILE: keyword is present in an org-mode buffer, the buffer's fontification is screwed up.
See explanation in https://github.com/hlissner/doom-emacs/issues/2775#issuecomment-620311173
This bug was introduced upstream. Doom pulls the regression in d6c5d18.

I can confirm! What should one do?

Looking at org-mode upstream repo commit log, it may have been fixed by 80865bab64.
If you can't afford to wait, use (package ... :pin ...) as described in Pinning packages to specific commits
;; file: packages.el
(package! org-mode :pin "80865bab64")

or (unpin! ...) org-mode completely and use always latest commit
;; file: packages.el
(unpin! org-mode)

I've bumped org in d34633c, so this issue should be resolved. Let me know if that isn't the case and I'll reopen it. Thanks for bringing it to my attention!

Thank you!

Works! Thanks!

authors: AloisJanicek guraltsev hlissner myshevchuk

repo: hlissner/doom-emacs


text:
Pin Agda packages to latest stable release

Describe your request
The main method of installing Agda is to build it from the source releases posted on Hackage, using either Cabal or Stack. However, the nightly build is not released on Hackage.
Currently, the packages in :lang agda track the master branch of the Agda repository, resulting in a version mismatch between agda-mode and the installed version of Agda unless you either install the nightly version of Agda or manually pin the agda-mode packages.
Thus it seems like for almost all usecases of the :lang agda module one would have to pin the packages. I think this means it would be better to pin the package in Doom Emacs itself to the latest stable release.
Briefly explain its use-case

Install Agda from Hackage
Add :lang agda to config and run doom sync
Versions match and agda-mode just works

I'd be glad to do so, but as I don't know anything about Agda, and there isn't enough information here for me to act on. What is "stable"? On agda/agda see a stable-2.5 branch, the latest tag is 2.6.2, and the latest announcement on the wiki that looks remotely relevant says (2021-02-07) Agda 2.6.1.3 is now available. Is there a particular branch we can track?
In any case, the :lang agda module has a +local flag, which stops it from installing anything -- leaving it entirely to the user to supply them and add them to your load-path (or write your own local package! for it).

I have to admit that I don't know a lot about Agda myself (yet?), I just encountered this while trying to set up my development environment. It does seem to be a bit of a mess to pin to a particular commit or branch. My apologies for making a pretty misinformed feature request.
I didn't know about the +local flag, it seems like a more elegant solution considering the way Agda versions work.
Maybe just adding the details about having to either pin the packages or use the +local flag to the documentation for the :lang agda module would be a good enough solution.

authors: hlissner theOperand


text:
lang/python: add additional checks

Related: #2180, #2193
A few questions and a comment:

Should line 8 be an assertion? Is python not being installed a blocker?
I realize these doctor checks are all checking for global installations of various packages. How does this conflict with the various virtualenv solutions people are using?
How do you determine where to put intermixed dependencies? For example, should the editor module also check if python is enabled and warn about black?
Finally, I settled on using the format of "couldn't find $executable. $feature will not work". Doom seems to be a little bit inconsistent here, but this format seemed to be most common.

1. Should line 8 be an assertion? Is `python` not being installed a blocker?

It probably should be, yeah.

2. I realize these doctor checks are all checking for global installations of various packages. How does this conflict with the various virtualenv solutions people are using?

I'm afraid there is no simple solution to this problem. We can only check for global installs and rely on heuristics. User's can ignore its warnings if they know better. I'm open to suggestions.

3. How do you determine where to put intermixed dependencies? For example, should the `editor` module also check if `python` is enabled and warn about `black`?

Good question. The provider should do the checks, rather than the consumer. i.e. It should be checked for in the :editor format module, wrapped in (when (featurep! :lang python) ...). I've put it in the python module because :editor format is overdue a rewrite (possibly with the reformatter.el package instead).

4. Finally, I settled on using the format of "couldn't find $executable. $feature will not work". Doom seems to be a little bit inconsistent here, but this format seemed to be most common.

Very true. I have a rewrite of the doctor system in the works to standardize these checks (and make following up on specific warnings/errors easier, through a doom doctor --describe ERRCODE command or similar). In any case, this is just fine for the time being.

Sorry for the late response. This looks good to me. Thanks for your help!

authors: danlamanna hlissner


text:
Bump lsp-mode

Contains a fix for signature help disappearing
https://github.com/emacs-lsp/lsp-mode/commit/7f68f9231f248ec613afe4d15cd69c8f37f27059 bump is to a commit after this

Done

Great! Thanks for the help!

authors: chbatey hlissner


text:
Bootstrap trampolines to prevent doom build hang

This is a workaround for doom build hanging on native-comp Emacs when run with an empty cache.  We're effectively automating the process of killing doom build and trying again.
Re: #3655
Re: #3983

Very cool. Thanks!

authors: flatwhatson hlissner


text:
Double quote doom binary location

This allows 'make quickstart' to work on Windows when using GNU make (appreciate Windows isn't officially supported)

I don't mind accepting this PR, but I use GNU make on Linux and MacOS, and it has never complained about DOOM not being quoted. Does GNU make on Windows behave differently?

Yes, this is what I get when not quoted and running make quickstart from within .emacs.d:
'bin' is not recognized as an internal or external command, operable program or batch file. make: *** [quickstart] Error 1
Which is making it difficult to script as part of an automated installation.

Understood. Thanks for this!

authors: hlissner xeijin


text:
Fix additional troublesome Windows characters

I found some additional files that are troublesome for Windows and have made the fixes.

Excellent, thanks!

authors: allforabit hlissner

repo: hlissner/emacs-snippets


text:
Plugin link

Prerequisites
Expected behaviour
Detailed parameter to use the plugin "link" to use the function "openlink" in the editor.
Environment
Shopware 5.8.4 and your plugin "Erweiterter TinyMCE"

https://www.tiny.cloud/docs-3x/reference/TinyMCE3x@Plugins/
There is no plugin "link"

authors: hlohaus tee-le-shop

repo: hlohaus/SheAdvancedTinyMce


text:
Set up read.me

It is good to get the site's important links in there:

the .page
the .live
the original site
any special instructions or call outs
a pre-made Sidekick link is nice too

Please add links to these pages as ones we plan to build out in Franklin:
https://www.freseniusmedicalcare.com/en/home
https://www.freseniusmedicalcare.com/en/patients-families-overview
https://www.freseniusmedicalcare.com/en/dialysis-options

newbie here, i want to contribute. Can you tell me what exactly to add?

I am taking this one, newbie here LOL.

authors: SpaciousCoder78 Toto-Tuo helms-charity

repo: hlxsites/fresenius


text:
Implement Application Note resource page

Examples:

https://www.moleculardevices.com/en/assets/app-note/br/assess-virus-neutralization-with-rapid-hts-friendly-assay
https://main--moleculardevices--hlxsites.hlx.page/en/assets/app-note/br/assess-virus-neutralization-with-rapid-hts-friendly-assay

Tasks:

[ ] Overall content styling (might be mostly ok already)
[ ] PDF button styles incl. icon
[ ] Image alignment, width, margins
[ ] Image caption styling

WIP in https://github.com/hlxsites/moleculardevices/tree/application_node_page

authors: lydiapuric mhaack

repo: hlxsites/moleculardevices


text:
CIV-6994 relist hearing notice

https://tools.hmcts.net/jira/browse/CIV-6994
new event to retrigger/relist hearing notice by changing state back to case progression
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ x] No

Overriding branch protections as the issue is general for civil-ccd-definition at the moment. This PR was actually green.

repo: hmcts/civil-ccd-definition


text:
Bug/civ 2649 tem issue second defendant

LRvLR: 1v2 different sol - Camunda changes.
template issue for second defendant
JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/CIV-2649
Change description
LRvLR: 1v2 different sol - Camunda changes.
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ x] No

This PR can be closed

repo: hmcts/civil-service


text:
PRO-3179: Amend Grant Details

Change description

Required spreadsheet: CCD_Probate_V01.10-Dev.xlsx, https://github.com/hmcts/Probate-CCD-Import-Spreadsheets/blob/master/spreadsheet/back-office/CCD_Probate_V02.02-Dev.xlsx
Added fields for amending grant
Also included fix for docker compose (to all cases to be created locally)

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

Good work Dhruv!

repo: hmcts/probate-sol-ccd-services


text:
RDCC-2262 - removed log to check the time taken for executing methods

JIRA link
https://tools.hmcts.net/jira/browse/RDCC-2262
Change description
CRD - Remove the log added for time taken for executing methods and code for handling formula cell type
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[ X ] No

It is just minor code smell only but it is good to address this https://sonarcloud.io/project/issues?id=uk.gov.hmcts.reform%3Areform%3A%3Ard-caseworker-ref-api&pullRequest=347&resolved=false&types=CODE_SMELL

merging the code.

repo: hmcts/rd-caseworker-ref-api


text:
Undefined reference to _d_arraybounds_index

Trying to to use LWDR for the psvita using vitasdk:
c:/msys64/usr/local/vitasdk/bin/../lib/gcc/arm-vita-eabi/10.3.0/../../../../arm-vita-eabi/bin/ld.exe: C:/msys64/usr/local/dlibs/\libtest.a(util.o): in function _D4util17stringCmpInternalFNeMxAaMxQeZi': C:\/Users\Marcelo\AppData\Local\dub\packages\lwdr-0.3.0\lwdr\source/util.d:6: undefined reference to _d_arraybounds_index'
c:/msys64/usr/local/vitasdk/bin/../lib/gcc/arm-vita-eabi/10.3.0/../../../../arm-vita-eabi/bin/ld.exe: C:/Users\Marcelo\AppData\Local\dub\packages\lwdr-0.3.0\lwdr\source/util.d:6: undefined reference to _d_arraybounds_index' c:/msys64/usr/local/vitasdk/bin/../lib/gcc/arm-vita-eabi/10.3.0/../../../../arm-vita-eabi/bin/ld.exe: C:\/Users\Marcelo\AppData\Local\dub\packages\lwdr-0.3.0\lwdr\source/util.d:6: undefined reference to _d_arraybounds_index'
c:/msys64/usr/local/vitasdk/bin/../lib/gcc/arm-vita-eabi/10.3.0/../../../../arm-vita-eabi/bin/ld.exe: C:/Users\Marcelo\AppData\Local\dub\packages\lwdr-0.3.0\lwdr\source/util.d:6: undefined reference to `_d_arraybounds_index'
collect2.exe: error: ld returned 1 exit status
This is my dub:
"dflags": [
		"-mtriple=armv7a-unknown-unknown",
		"-mcpu=cortex-a9",
		"-g",
		"-float-abi=hard",
		"-O0",
		"-fthread-model=local-exec"
	],
	"targetType": "staticLibrary",

My D source:
class Test
{
	immutable(char*) getStringFromD()
	{
		return "Hello World from D! Simple Test".ptr;
	}
}

class UltraTest : Test
{
	override immutable(char*) getStringFromD()
	{
		return "Hello World from D!!! Ultra Test!".ptr;
	}
}

extern(C) immutable(char*) getStringFromD()
{
	return new UltraTest().getStringFromD;
}

Which compiler (and version) are you using?

This was fixed with the MoonlightSentinel PR

authors: MrcSnm hmmdyl

repo: hmmdyl/LWDR


text:
[MTDSA-573] Fix flaky tests by increasing the default timeout duration for Future.

Override defaultTimeout in UnitSpec to 30 seconds, up from 5.
Change default timeout duration to 30 seconds in the Http class.

Factored it out in to a val.

repo: hmrc/self-assessment-api


text:
Add new GitHub actions

This new GitHub action will check to ensure that all commits in a pull request follow the required format, and if not, will fail to indicate to the user what the issue is.

I dont think my overall review comment got addressed or responded to, also looks like another commit got added that does not fall in the scope of the PR title.

PR title changed. Regex now includes a comment


text:
Feat: added get deleted newsletter emails

Description
This pull request introduces a new API endpoint to retrieve soft-deleted newsletters.
Key Features

Endpoint: GET /api/v1/newsletter-subscription/deleted
Functionality: Retrieves newsletters that have been soft-deleted.
Authentication: Requires a valid JWT token for access.
Authorization: Only users with the SuperAdmin role can access this endpoint.

Acceptance Criteria

The endpoint should accept HTTP GET requests.
The request must include a valid authentication token in the Authorization header.
The response should return a list of newsletters that have been marked as soft-deleted.

Authorization Header:
{
    "Authorization": "Bearer <token>"
}

Related Issue
This pull request addresses Issue 288.
How Has This Been Tested?
The changes have been tested with the following methods:

Integration Tests:

Verified successful retrieval of soft-deleted newsletters by an authorized SuperAdmin user.
Tested unauthorized access attempts with an invalid token.
Handled cases where a regular user attempts to access the endpoint without sufficient permissions.

Screenshots (if appropriate - Postman, etc.)

Types of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[x] My code follows the code style of this project.
[x] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

please remove comments

done


text:
Should have a way to filter things out of the logs.  Poses a security issue as it stands.

I think there needs to be a way to create a "safe" list so that certain things are scrubbed from the logs
For instance
Params: map[username:Altonymous password:1234 confirm_password:1234  handle:Altonymous]
Should be:
Params: map[username:Altonymous password: confirm_password: handle:Altonymous]

Hi @Altonymous and @hoisie - I've done a slight modification to server.go to provide a config attribute called OmitPostParams, which if set to true does NOT omit any POST parameters.
Is there interest in this getting patched in? If so I'll submit a pull request.
Usage is pretty simple:
web.Config.OmitPostParams = true
Results in output like:
2016/02/19 14:56:26 1.2.3.4 -  POST /saml_consume - 27.903774ms

Thanks for posting this issue. I agree it's a security concern and needs to be fixed. I like the idea of having a way to disable param logging, but I think that could be achieved more effectively using log levels.
I was thinking of introducing a config option like Config.FilterParams which could be a list of sensitive param names. For example, if you'd like to filter out password and password_confirm, you could just use: Config.FilterParams = []string{"password", "password_confirm"}

Great idea :)

Great idea!

Just created https://github.com/hoisie/web/pull/208. Config.FilterParams is a list of regular expression strings. I think that's a little more flexible than just hardcoding param names. Anyone want to take a look at that?

authors: Altonymous cfrichot hoisie xntrik

repo: hoisie/web


text:
Definir el código a usar para cada Provincia

Siendo que el módulo aún no está siendo usado, ¿deberíamos quizás cambiar el código del módulo para que use ISO-3166-2 y así integrarse mejor con módulos de logística?

Siendo que sólo tuvo 3 instalaciones (de prueba) quizás es un buen momento para hacer el fork y cambiar los códigos y ya generar la versión 1.1.0 (¿o la 1.0.1?)

¿Que clase de fork? ¿No se deberia cambiar en este mismo repo? En cuanto a la version, creo que es un cambio un poco mas grande que un fix, asi que 1.1.0 es mas acertado.

Según hemos definido, es vía fork: https://www.mugar.io/como-contribuir-con-los-modulos/
Estoy de acuerdo con lo de la versión.

authors: barbanet manuelcanepa

repo: holamugar/module-argentinaregions


text:
conversion: add various marshalling methods

This PR adds some more marshalling methods. If we want to replace big.Int and hexutil.Big with uint256.Int in go-ethereum, these methods are needed.
Benchmark_EncodeHex/large/uint256-6             10843225                97.2 ns/op            80 B/op          1 allocs/op
Benchmark_EncodeHex/large/big-6                  6547092               190 ns/op             139 B/op          2 allocs/op
Benchmark_DecodeHex/large/uint256-6              9983671               118 ns/op              32 B/op          1 allocs/op
Benchmark_DecodeHex/large/big-6                 10242964               128 ns/op              32 B/op          1 allocs/op

cc @fjl PTAL

Codecov Report

Merging #79 into master will decrease coverage by 0.19%.
The diff coverage is 97.22%.

@@             Coverage Diff             @@
##            master      #79      +/-   ##
===========================================
- Coverage   100.00%   99.80%   -0.20%
===========================================
  Files            3        3
  Lines          958     1030      +72
===========================================
+ Hits           958     1028      +70
- Misses           0        1       +1
- Partials         0        1       +1

authors: codecov-commenter holiman


text:
Add new variable 'last' using middleware parameter ?from=now

Adding a RESSOURCE with parameter ?from=now
to get last value from middleware
add self.last to output the new value

I added paramaters to 'from' and 'to' to the middleware url.
The default is not touched, if from or to is not set
But you can configure the 'from' and 'to'
Add self.last using tuples.


text:
[0.80.0] apple_tv_scan unable to find AppleTV devices

Home Assistant release with the issue:
0.80.0
Last working Home Assistant release (if known):
N/A
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
https://www.home-assistant.io/components/apple_tv/
Description of problem:
Recently installed HomeAssistant 0.80.0 and attempted to use the Apple TV component. Following the initial steps, HomeAssistant is unable to find any device using the 'apple_tv.apple_tv_scan' service. No errors found in the Home Assistant logs.
Home Sharing is enabled on the Apple TV and rebooted the Apple TV multiple times. Home Sharing works from my Apple Devices with the Apple TV. Both the Apple TV and the HomeAssistant Container are on the same (physical) network/subnet.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
discovery:
  enable:
    - homekit

ios:
apple_tv:

Additional information:
Currently running tvOS12

having the same issue, how are you starting your docker container? the cmd line

I was having the same issue on 0.80.3, but it appears to be fixed in 0.81.0.
Output from home-assistant.log:
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.components.discovery] Found new service: apple_tv {'host': '192.168.1.28', 'port': 3689, 'hostname': 'Game-Room.local.', 'properties': {'DFID': '4', 'EiTS': '1', 'mV': '131082', 'aV': '196620', 'hG': '00000000-06b2-c289-794b-f60944fc4dcd', 'fs': '2', 'Name': 'Game Room', 'atSV': '65539', 'Ver': '131075'}, 'name': 'Game Room'}
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.components.discovery] Found new service: apple_tv {'host': '192.168.1.31', 'port': 3689, 'hostname': 'Living-Room.local.', 'properties': {'DFID': '3', 'EiTS': '1', 'mV': '131082', 'aV': '196620', 'hG': '00000000-06b2-c289-794b-f60944fc4dcd', 'fs': '2', 'Name': 'Living Room', 'atSV': '65539', 'Ver': '131075'}, 'name': 'Living Room'}
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.loader] Loaded apple_tv from homeassistant.components.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.setup] Setting up apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.setup] Setup of domain apple_tv took 0.0 seconds.
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.loader] Loaded remote from homeassistant.components.remote
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.loader] Loaded media_player.apple_tv from homeassistant.components.media_player.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.setup] Setting up remote
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.setup] Setup of domain remote took 0.0 seconds.
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.components.media_player] Setting up media_player.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.loader] Loaded remote.apple_tv from homeassistant.components.remote.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new media_player.apple_tv entity: media_player.game_room_4
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new media_player.apple_tv entity: media_player.living_room_4
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.components.remote] Setting up remote.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.components.remote] Setting up remote.apple_tv
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new remote.apple_tv entity: remote.game_room_4
Oct 28 18:13:18 nuc hass[26345]: 2018-10-28 18:13:18 INFO (MainThread) [homeassistant.helpers.entity_registry] Registered new remote.apple_tv entity: remote.living_room_4

@d3vzer0 could you try on 0.81.0 and see if that fixes it?

Unfortunately still have the same issue. I have home-sharing enabled but HomeAssistant think's otherways:
2018-11-11 02:35:38 DEBUG (zeroconf-ServiceBrowser__touch-able._tcp.local.) [pyatv] Auto-discovered service LulzSec TV at 192.168.1.57 (no home sharing)

Thanks for the replies!
Unfortunately still have the same issue. I updated to HomeAssistant 0.82 (Docker). I have home-sharing enabled but HomeAssistant still thinks other-ways:
2018-11-11 02:35:38 DEBUG (zeroconf-ServiceBrowser__touch-able._tcp.local.) [pyatv] Auto-discovered service AppleTV at 192.168.1.10 (no home sharing)

I'm having a similar issue, but perhaps my specific setup might provide a few more clues. I've got two apple tvs, one an aTV4, the other an aTV4K. I have absolutely no issues with the the aTV4, but the 4K has been a consistent and baffling problem.
I can pair the 4K by disabling home sharing, rebooting, then re-enabling home sharing, as support threads on the home assistant forums have suggested, but this only lasts for a day or two at most before  home assistant loses a connection and begins spamming the logs with:
2018-11-13` 19:43:11 WARNING (MainThread) [homeassistant.components.media_player.apple_tv] A <class 'aiohttp.client_exceptions.ClientConnectorError'> error occurred: Cannot connect to host 192.168.0.117:3689 ssl:None [Host is unreachable]
Just in case it's relevant, I use a Netgear Orbi as a wifi AP, and the aTV4 is wifi, while the aTV 4K is connected via ethernet to the Orbing satellite. I've tried the 4K wifi only, and it hasn't made a difference.
Running the latest hassio docker setup (0.82.0) on a generic linux server (Ubuntu bionic).

authors: d3vzer0 lukiffer meekaah setlursh

repo: home-assistant/home-assistant


text:
launch_library error on start "Error on device update!"

Home Assistant release with the issue:
0.83.3
Last working Home Assistant release (if known):
None
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
launch_library (Space launch sensor)
Description of problem:
This sensor doesn't start on 0.83.3 docker, gives the error below.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
- platform: launch_library

Traceback (if applicable):
2018-12-05 19:11:30 ERROR (MainThread) [homeassistant.components.sensor] launch_library: Error on device update!
Traceback (most recent call last):
File "/usr/local/lib/python3.6/site-packages/pylaunches/common.py", line 29, in api_call
response = await self.session.get(endpoint, headers=HEADERS)
File "/usr/local/lib/python3.6/site-packages/aiohttp/client.py", line 370, in _request
timeout=timeout
File "/usr/local/lib/python3.6/site-packages/aiohttp/connector.py", line 445, in connect
proto = await self._create_connection(req, traces, timeout)
File "/usr/local/lib/python3.6/site-packages/aiohttp/connector.py", line 757, in _create_connection
req, traces, timeout)
File "/usr/local/lib/python3.6/site-packages/aiohttp/connector.py", line 843, in _create_direct_connection
traces=traces), loop=self._loop)
concurrent.futures._base.CancelledError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/src/app/homeassistant/helpers/entity_platform.py", line 248, in _async_add_entity
await entity.async_device_update(warning=False)
File "/usr/src/app/homeassistant/helpers/entity.py", line 347, in async_device_update
await self.async_update()
File "/usr/src/app/homeassistant/components/sensor/launch_library.py", line 58, in async_update
await self.launches.get_launches()
File "/usr/local/lib/python3.6/site-packages/pylaunches/api.py", line 26, in get_launches
data = await common.api_call(BASE_URL)
File "/usr/local/lib/python3.6/site-packages/pylaunches/common.py", line 30, in api_call
data = await response.json()
File "/usr/local/lib/python3.6/site-packages/async_timeout/__init__.py", line 55, in __aexit__
self._do_exit(exc_type)
File "/usr/local/lib/python3.6/site-packages/async_timeout/__init__.py", line 92, in _do_exit
raise asyncio.TimeoutError
concurrent.futures._base.TimeoutError

Additional information:

Ive tried for a few days with no luck. I am also having issues with the seventeentrack sensor.. I wonder if my installation has trouble getting to the internet. Except I have the darksky component working fine.

That is just weird...
Can you try this inside the container:
time curl -sSL https://launchlibrary.net/1.4/launch/next/1

Here's the output:
time curl -sSL https://launchlibrary.net/1.4/launch/next/1
{"launches":[{"id":1500,"name":"Falcon 9 Block 5 | SpX CRS-16","windowstart":"December 5, 2018 18:16:16 UTC","windowend":"December 5, 2018 18:16:16 UTC","net":"December 5, 2018 18:16:16 UTC","wsstamp":1544033776,"westamp":1544033776,"netstamp":1544033776,"isostart":"20181205T181616Z","isoend":"20181205T181616Z","isonet":"20181205T181616Z","status":1,"inhold":0,"tbdtime":0,"vidURLs":["https:\/\/www.youtube.com\/watch?v=Esh1jHT9oTA","https:\/\/www.youtube.com\/watch?v=wwMDvPCGeE0"],"vidURL":null,"infoURLs":[],"infoURL":null,"holdreason":null,"failreason":null,"tbddate":0,"probability":90,"hashtag":null,"changed":"2018-10-31 15:12:52","location":{"pads":[{"id":84,"name":"Space Launch Complex 40, Cape Canaveral, FL","infoURL":"","wikiURL":"https:\/\/en.wikipedia.org\/wiki\/Cape_Canaveral_Air_Force_Station_Space_Launch_Complex_40","mapURL":"http:\/\/maps.google.com\/maps?q=28.56194122,-80.57735736","latitude":28.56194122,"longitude":-80.57735736,"agencies":[{"id":121,"name":"SpaceX","abbrev":"SpX","countryCode":"USA","type":3,"infoURL":null,"wikiURL":"http:\/\/en.wikipedia.org\/wiki\/SpaceX","changed":"2017-02-21 00:00:00","infoURLs":["http:\/\/www.spacex.com\/","https:\/\/twitter.com\/SpaceX","https:\/\/www.facebook.com\/SpaceX","https:\/\/www.youtube.com\/channel\/UCtI0Hodo5o5dUb67FeUjDeA"]}]}],"id":16,"name":"Cape Canaveral, FL, USA","infoURL":"","wikiURL":"","countryCode":"USA"},"rocket":{"id":188,"name":"Falcon 9 Block 5","configuration":"9 Block 5","familyname":"Falcon","agencies":[{"id":121,"name":"SpaceX","abbrev":"SpX","countryCode":"USA","type":3,"infoURL":null,"wikiURL":"http:\/\/en.wikipedia.org\/wiki\/SpaceX","changed":"2017-02-21 00:00:00","infoURLs":["http:\/\/www.spacex.com\/","https:\/\/twitter.com\/SpaceX","https:\/\/www.facebook.com\/SpaceX","https:\/\/www.youtube.com\/channel\/UCtI0Hodo5o5dUb67FeUjDeA"]}],"wikiURL":"https:\/\/en.wikipedia.org\/wiki\/Falcon_9_Full_Thrust#Block_5","infoURLs":["http:\/\/www.spacex.com\/falcon9"],"infoURL":"http:\/\/www.spacex.com\/falcon9","imageSizes":[320,480,640,720,768,800,960,1024,1080,1280,1440,1920],"imageURL":"https:\/\/s3.amazonaws.com\/launchlibrary\/RocketImages\/Falcon9Block5.jpg_1920.jpg"},"missions":[{"id":888,"name":"SpX CRS-16","description":"SpaceX will launch the Dragon spacecraft on their 15th operational cargo delivery mission to the International Space Station. The flight is being conducted under the Commercial Resupply Services contract with NASA.","type":11,"wikiURL":"","typeName":"Resupply","agencies":[{"id":44,"name":"National Aeronautics and Space Administration","abbrev":"NASA","countryCode":"USA","type":1,"infoURL":null,"wikiURL":"http:\/\/en.wikipedia.org\/wiki\/National_Aeronautics_and_Space_Administration","changed":"2017-02-21 00:00:00","infoURLs":["http:\/\/www.nasa.gov","https:\/\/www.youtube.com\/channel\/UCLA_DiR1FfKNvjuUpBHmylQ","https:\/\/twitter.com\/nasa","https:\/\/www.facebook.com\/nasa"]}],"payloads":[]}],"lsp":{"id":121,"name":"SpaceX","abbrev":"SpX","countryCode":"USA","type":3,"infoURL":null,"wikiURL":"http:\/\/en.wikipedia.org\/wiki\/SpaceX","changed":"2017-02-21 00:00:00","infoURLs":["http:\/\/www.spacex.com\/","https:\/\/twitter.com\/SpaceX","https:\/\/www.facebook.com\/SpaceX","https:\/\/www.youtube.com\/channel\/UCtI0Hodo5o5dUb67FeUjDeA"]}}],"total":181,"offset":0,"count":1}
real	0m6.368s
user	0m0.014s
sys	0m0.008s

Anything > 5s will trigger timeout.

This was caused by a delay in the server resolving addresses. I haven't fixed the cause but it's not related to the component.

authors: IVData ludeeus


text:
Yeelight Lamp and Bulb errors when send any commands

Home Assistant release with the issue:

observed from version 0.95 to 0.96.5 current version
Last working Home Assistant release (if known):
unknown
Operating environment (Hass.io/Docker/Windows/etc.):

hass.io / docker / linux
Component/platform:

Yeelight Wifi Bulb
Description of problem:
Every time a command is sent to BSLamp model bslamp1 MJCTD01YL and WiFi Light bulb RGBW MJDP02YL I get an error in log. Commands work and the device performs what I tell it to do.
errors look like this:
2019-07-27 22:34:50 ERROR (SyncWorker_0) [homeassistant.components.yeelight.light] Error when calling <function YeelightGenericLight.set_default at 0x7f6aaf78c560>: {'code': -5000, 'message': 'general error'}
2019-07-27 22:34:52 ERROR (SyncWorker_29) [homeassistant.components.yeelight.light] Error when calling <function YeelightGenericLight.set_default at 0x7f6aaf78c560>: {'code': -5000, 'message': 'general error'}
2019-07-27 22:34:56 ERROR (SyncWorker_17) [homeassistant.components.yeelight.light] Error when calling <function YeelightGenericLight.set_default at 0x7f6aaf78c560>: {'code': -5000, 'message': 'general error'}
2019-07-27 22:34:59 ERROR (SyncWorker_30) [homeassistant.components.yeelight.light] Error when calling <function YeelightGenericLight.set_default at 0x7f6aaf78c560>: {'code': -5000, 'message': 'general error'}
2019-07-27 22:35:07 ERROR (SyncWorker_23) [homeassistant.components.yeelight.light] Error when calling <function YeelightGenericLight.set_default at 0x7f6aaf78c560>: {'code': -5000, 'message': 'general error'}
2019-07-27 22:35:12 ERROR (SyncWorker_5) [homeassistant.components.yeelight.light] Error when calling <function YeelightGenericLight.set_default at 0x7f6aaf78c560>: {'code': -5000, 'message': 'general error'}
2019-07-27 22:45:00 ERROR (SyncWorker_19) [homeassistant.components.yeelight.light] Error when calling <function YeelightGenericLight.set_default at 0x7f6aaf78c560>: {'code': -5000, 'message': 'general error'}
2019-07-27 22:45:04 ERROR (SyncWorker_1) [homeassistant.components.yeelight.light] Error when calling <function YeelightGenericLight.set_default at 0x7f6aaf78c560>: {'code': -5000, 'message': 'general error'}
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
# Yeelight (Xiaomi)
yeelight:
  devices:
    192.168.1.40:
      name: yeelight_bslamp1
      save_on_change: true
      model: bslamp1
    192.168.1.45:
      name: yelight_bulb1
      save_on_change: true
      model: RGBW

Traceback (if applicable):

Additional information:
#for the bulb i also tried this config that gives the same errors
yeelight:
  devices:
    192.168.1.45:
      name: yelight_bulb1
      save_on_change: true
      model: color1

Looks like those devices do not support setting the default, so you can change save_on_change to false (which is the default) and you should not see those errors anymore.

Idd changeing save_on_change to false solves the problem, tbh i always had it like this but only recently saw this probelm. Thanks.

Maybe there could be a map of devices which support the commands and which do not (ping @zewelor), but I feel this is not a priority. Shall we close this for now @hellcry37?

Yes, I think issue can be closed, seem that issue is resolved if I disabled that option. Thank you very much!


text:
Can't use a discovered sensor in a template

Home Assistant release with the issue:
0.101.3
Last working Home Assistant release (if known):
N/A, never tried it before
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Integration:
MQTT Sensor (MQTT Discovery)
Description of problem:
Can't use a sensor added via integration discovery in a template, works fine with other sensors manually added in configuration.yaml. The sensor is a Xiaomi tempeature sensor added via zigbee2mqtt discovery
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
{{ as_timestamp(states.sensor.0x00123456789_temperature.last_changed) }}

Traceback (if applicable):
Error rendering template: TemplateSyntaxError: expected token ',', got '0x00123456789_temperature'

Additional information:

This is due to entities that start with a number https://www.home-assistant.io/docs/configuration/templating/#entity_id-that-begins-with-a-number


text:
Bump pylutron to 0.2.5

Description:
New version is much more robust against disconnections, fixes a string formatting exception, and adds better logging when uncaught exceptions are thrown.
Related issue (if applicable): fixes #20348
Pull request with documentation for home-assistant.io (if applicable): N/A
Example entry for configuration.yaml (if applicable): N/A
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

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

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

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

[ ] The manifest file 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.
[ ] Untested files have been added to .coveragerc.

If the code does not interact with devices:

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

@cdheiser @JonGilmore FYI


text:
Bump aioesphomeapi to 2.4.1

Description:
See also https://github.com/esphome/aioesphomeapi/compare/v2.4.0...v2.4.1
Related issue (if applicable): fixes https://github.com/home-assistant/home-assistant/issues/28157
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

A PR to fix the formatting has been merged. Try rebasing on latest dev branch to let the build pass.

authors: OttoWinter cgtobi


text:
Use voluptuous for Octoprint

Description:
Migration of the configuration check to voluptuous.
Related issue (if applicable): fixes 127528299
Example entry for configuration.yaml (if applicable):
octoprint:
  host: YOUR_OCTOPRINT_HOST
  api_key: YOUR_API_KEY

binary_sensor:
  platform: octoprint
  monitored_conditions:
    - Printing
    - Printing Error

@w1ll1am23, would be nice if you could take a look at the changes and run a quick test. Thanks.

Ran a quick test and it seems to work. I did notice I had to change my config form
host: http://192.168.x.x

to
host: 192.168.x.x

When using the http:// the logs said it was failing when trying to connect to host 'http' any idea what that is about?

Yes, I changed that to be more aligned with the configuration of the other platforms/components. This will be mentioned in the release note for 0.28.

:+1:


text:
Add parse_time method for templates.

Description:
Frequent interest is shown in Gitter/forums for a method that parses strings to produce a datetime object.
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>
Checklist:
If user exposed functionality or configuration variables are added/changed:

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

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.

Sadly this causes TypeError: can't subtract offset-naive and offset-aware datetimes when used with relative_time and no timezone.

There is another time parsing function in homeassistant.util.dt named parse_datetime. Having two different datetime parsers may lead to confusion (why does this parse here and not there, etc).
Any reason the existing one wouldn't suffice here?

@jaharkes hmm, I need something a little more flexible than that - test_parse_datetime_converts_correctly also only tests for 1986-07-09T12:00:00Z which is a little sad. I could replace that method with a call to dateutil.parser.parse and the test would most likely pass, but I'm not sure if that will suffice as a test in changing the functionality.

@balloob introduced homeassistant.util.dt.parse_datetime in commit 68d92c31. Looking at that commit I think it intentionally only parses ISO dates and probably should not be replaced with a more flexible parser.

@jaharkes is correct. Iso8601 for the win.

Agreed, ISO8601 is the only acceptable date format, and I don't want the
extra delivery for such a small feature. However, short of writing a parser
as flexible as the one provided in the tried-and-tested dateutil, I'm not
sure if we have anything to satisfy it. Any ideas? Your advice on direction
is welcome.
On Wed, 19 Oct 2016, 8:04 pm Paulus Schoutsen, notifications@github.com
wrote:

@jaharkes https://github.com/jaharkes is correct. Iso8601 for the win.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3950#issuecomment-254909911,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1TOyfy9UnSGDsEfi61rxCNYk2rPj9Mks5q1mnAgaJpZM4KbMA-
.

We have a parse_time method in dt_util. I don't see too many use cases for parsing a date, as that's that would have to be updated all the time.

Your example also doesn't make sense, why get the current date time as a datetime object, convert it to string, then convert it again to a datetime object ?

Doesn't look like GitHub processed my email;
Replace using now() with a timestamp.
The two use cases I'm aware of;

Receiving a string timestamp and trying to calculate the relative time.

Receiving a second duration and trying to calculate the relative time of it.

@dale3h may have more.

I think a good first step here would be to add support for strptime as @dale3h suggests.

I've updated the example.

unfortunately @dale3h's workaround doesn't work for states.sun.sun.attributes.next_rising  because this comes back as an isoformat string which can't be be used with relative_time (TypeError: can't compare offset-naive and offset-aware datetimes) this was reason for the attempt at #4036 ... which additionally needed delta in get_age to be replaced with delta = now() - date if now() > date else date - now() to make relative_time(states.sun.sun.attributes.next_setting) possible

I have a solution in the form of a custom component, which uses dateutil.
Should I close this PR or just alter the commit to use the existing method
to parse ISO8061 dates - atleast providing a way for people to get a
datetime object from a string?
On Fri, 21 Oct 2016, 6:24 am Paulus Schoutsen, notifications@github.com
wrote:

We have a parse_time method in dt_util. I don't see too many use cases
for parsing a date, as that's that would have to be updated all the time.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3950#issuecomment-255296453,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1TO8lRRoCDQmNU3mG-rfKLGFN15wZ9ks5q2EyagaJpZM4KbMA-
.

@lwis that in itself won't be enough to get realtive_time to work unless some timezone offset is either added to the string value or implied on the parsing.

Replace using now() with a timestamp.
The two use cases I'm aware of;

Receiving a string timestamp and trying to calculate the relative time.

Receiving a second duration and trying to calculate the relative time of
it.

@dale3h may have more.
On Fri, 21 Oct 2016, 6:54 am Paulus Schoutsen, notifications@github.com
wrote:

Your example also doesn't make sense, why get the current date time as a
datetime object, convert it to string, then convert it again to a datetime
object ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3950#issuecomment-255299914,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1TO4IL5P6OWCuH4LHjS9FlapiWzf6uks5q2FOOgaJpZM4KbMA-
.

Haha, brilliant!
On Fri, 21 Oct 2016, 7:03 pm Dale Higgs, notifications@github.com wrote:

@lwis https://github.com/lwis For what it's worth, I was able to figure
out a work-around for your issue the other day. It came to me after writing
my previous comment:
{{ relative_time(now().strptime((as_timestamp(now()) -
61)|timestamp_custom('%Y-%m-%d %H:%M:%S%z'), '%Y-%m-%d %H:%M:%S%z')) }} ago
@balloob https://github.com/balloob Yeah, that's a bit ridiculous and
way too complicated...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3950#issuecomment-255434718,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1TO-2d8Rivuzsc614MvfPQrlj7idAaks5q2P5fgaJpZM4KbMA-
.

Good idea, I can't see an issue with exposing strptime, and it avoids an
extra dep. I'll update the PR soon.
On Fri, 21 Oct 2016, 6:13 pm Dale Higgs, notifications@github.com wrote:

I was offering assistance the other day and could not find a way to
convert a string to a timestamp inside of a template. Even a strict-format
string -> datetime object would be better than what we (don't) have
available to templates currently.
The only use-cases that comes to mind for needing a loose parser would
be for human input, i.e. Alexa, Telegram bot, MQTT, etc.
For now, I would even be happy with having direct access to strptime.
What I have in mind right now is:
{{ 'Apr 14 2013 15:32:09'|strptime('%b %d %Y %H:%M:%S') }}
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3950#issuecomment-255428238,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1TO51qbZg94ISV4REoLtPsza-un9cEks5q2PK3gaJpZM4KbMA-
.

@jumpkick I'm still trying to decide if setting the users timezone by
default would work, or simply UTC.
On Tue, 25 Oct 2016, 7:20 pm jumpkick, notifications@github.com wrote:

@lwis https://github.com/lwis that in itself won't be enough to get
realtive_time to work unless some timezone offset is either added to the
string value or implied on the parsing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/home-assistant/home-assistant/pull/3950#issuecomment-256121061,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1TO37aqGlLahSSZttDG5Lai9s6RkwZks5q3khigaJpZM4KbMA-
.

"The datetime module has support for output to a string of dates and times in ISO 8601 format ("2012-09-09T18:00:00-07:00"), with the object method "isoformat([sep])".  But there's no support for parsing such strings.  A string to datetime class method should be provided, one capable of parsing at least the RFC 3339 subset of ISO 8601." - http://bugs.python.org/issue15873
So... it looks like the only way around it is this monstrosity...
{{ relative_time(now().strptime((states.sun.sun.attributes.next_rising[:-6].replace('T',' ')+states.sun.sun.attributes.next_rising[-6:].replace(':',''))|timestamp_custom('%Y-%m-%d %H:%M:%S%z'), '%Y-%m-%d %H:%M:%S%z')) }} ago

Now we just need to get get_age patched so that it handles negative deltas as per above

Ok to merge when conflicts resolved.

authors: balloob jaharkes jumpkick lwis


text:
Only report slowness warning once per entity

Description:
Only report slowness warning once per entity.
Related issue (if applicable): fixes #4936

👍

authors: balloob pvizeli