Show an error when a media path does not exist

Testing #122275
In the example below the media path does not exist. There is an exception shown in the console.

It could be helpful to make the error more obvious, e.g. by rendering it into the page.
		"walkthroughs": [
			{
				"id": "exampleProject",
				"title": "Turn Markdown into HTML",
				"description": "Use this sample project to learn how to convert Markdown to HTML!",
				"primary": true,
				"steps": [
					{
						"id": "md-to-html.openExample",
						"title": "Open an example folder",
						"description": "To start, **try** opening [link](http://www.eclipse.org) an ``code`` example folder that has been preconfigured for this tutorial. **This is optional**, but helps for following along!\n[Open Example](command:md-to-html.openExample)",
						"media": {
							"path": "media/example1.md"
						}
					}
				]
			}
		],

I hit the same issue -- took me a bit to realize the path was wrong.

This works for markdown, but not images


question about distributed_utils.all_gather_list

In function distributed_utils.all_gather_list(data, group, max_size) , why assert max_size < 255*256 ？
If this is necessary, is there any way for me to use a larger size of logging_output ?

Interestingly enough someone just submitted a change that generalizes this :) It should be merged soon.

@myleott  any link of this submitted change?
By the way，Is it possible to use BLEU as the validation metric in the future?

https://github.com/pytorch/fairseq/pull/1499/files#diff-cc468b704bc1fc2e0ae7ee926e2c289b

Merged here: https://github.com/pytorch/fairseq/commit/29d7182447c4120057c116eb22c06d1d909eb3a1

thanks.


URL for QLeverUI with particular query

There is currently a mechanism that produces a unique URL after a query has been executed so that that URL leads to the UI with that query already entered. For example: http://qlever.informatik.uni-freiburg.de/Wikidata_Full/KyZa6C
However, there is no mechanism (or not that I know of) for linking to the site with a query that has not yet been entered. A natural URL would be (PREFIXes ommitted for brevity) http://qlever.informatik.uni-freiburg.de/Wikidata_Full/query=SELECT+?x+WHERE+{+?x+wdt:P31+wd:Q5+} or something like that. It would also be good if this were possible both with a GET and a POST request. In the case of a POST request, it would be natural to turn the URL into one of the kind described in the first paragraph.
As an aside, are the URLs described in the first paragraph persistent? That is, do they survive any restarts and updates of the QLever UI as long as the sqlite3 database is preserved? They should!

Yes, these URLs are stored in the sqlite3 database. They can, however, be deleted by clicking "Resources > Clear History" (I might rename that to something more understandable like "Delete URLs for executed queries")

Does the 'Clear History' delete only the queries I created myself or does it globally delete every query currently in the database?

I added a share button next to the download button in the latest commit.

89caea7b2865af178daa05a6a105522c4dc5a137

Yes, these URLs are stored in the sqlite3 database. They can, however, be deleted by clicking "Resources > Clear History" (I might rename that to something more understandable like "Delete URLs for executed queries")

Does the 'Clear History' delete only the queries I created myself or does it globally delete every query currently in the database?

Yes, it will delete every query in the database. Also, as of 9a9314b46f3a33eb24ec9b376603e7e536aa6b06, this button is only available for project admins, a.k.a. people who have the credentials to login to /admin

I regularly run a query on the web UI, then close my browser (current Firefox version), take a break of about a week, open my browser, click on 'Restore Previous Session' (which gets me back all the browser tabs that were open when I closed the browser window) and then want to look at the query I ran last time. Usually, even though the URL is correct (and has a unique part at the end), the query text box is empty and the result table doesn't show. I don't see any way of getting back my query in this situation.
Does this really only happen when an admin clicks on 'Clear History' between me closing and opening the browser window? If so, why is it apparently clicked at least once a week?
I realize I can click on 'Share' and save the GET query instead of the POST query as a workaround. I'm just wondering why I have to.

I did some changes in 20479f0b9f44731e4531963286c5f6824d2a8192 that would prevent possible "unintetional" deletions of the stored links. If this didn't fix your issue, I'm not sure I'll have another clue on why the links "get lost" like this.


Add the Zephyr model?

Hello everybody,
I have noticed there is no Zephyr model implementation. Here is a link to the HF model hard: zephyr-7b.
Is there a plan to add this model? Thanks!

Oh, ok. Thanks!

Also just to mention that zephyr is already supported specifically in the quantized example, see here.


Thread::fShouldExit should of type std::atomic

AFAIK the C++ keyword volatile has to do with compiler optimization (especially ordering). (it was a little different in C)
std::atomic  guarantees "undefined behaviour"-free code, when multiple threads access a std::atomic<trivialtype> variable concurrently like it is possible in Thread through internal running Thread and concurrent other threads through the public Thread::signalThreadShouldExit.

C++98 does not have std::atomic, which DPF still targets as minimum requirement.
I do not want to introduce new C++ requirements until very strictly necessary.
The volatile there is meant more as an indication that it should never be optimized away, as a precaution more than reassurance.


Recon backend

Allows the choice of backend in child classes of recon
Implements FBP with choice of backend
closes #1164

the ASTRA FBP doesn't have the correct weighting for the astra backprojector. It needs some investigation to find how the projectors are weighted.
In the mean time we could split this in to two. However adding the backend functionality works, but does not have a use case until either ASTRA FBP or LS+TC recons are implemented.
I'd suggest not merging until we have the use case implemented too.


Big delay with no feedback when a message is first kicked off

@thedadams brought this up in standup and i am seeing it as well.
It takes several seconds before we even give any feedback to a user after they send a message.
We think this is because the context now takes longer to generate because of the call to knowledge.

https://github.com/gptscript-ai/desktop/pull/428

Tested with electron build -  9d3d776c3
We are presented with "Waiting for model response.." message as soon as we send any chat message now.
But this fix seems to have introduced the following 2 issues which were not seen before:
https://github.com/gptscript-ai/desktop/issues/437
https://github.com/gptscript-ai/desktop/issues/438


Add ability to insert custom etl_config files into the etl config

The design is to have an external directory that can contain multiple extension files and do the merge in memory every time etk runs

@lastmansleeping please document the design in the description, ie, where the files will be stored.

What is the status of this task?

Will push the code soon and create a pull request.

great, thx
p

On Oct 16, 2017, at 10:26 PM, Ashish Bharadwaj Srinivasa<EMAIL_ADDRESS>wrote:
Will push the code soon and create a pull request.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/usc-isi-i2/dig-etl-engine/issues/30#issuecomment-337121475, or mute the thread https://github.com/notifications/unsubscribe-auth/ABBlp8cbNn_R4v_X7Ylv8c0nOGpi06faks5stDptgaJpZM4P3ot7.

Commit on my fork. Will create a pull request once I sync up with @saggu. @GreatYYX will handle the functionality at the dig-etl-engine end. Still keeping the issue "In Progress".


<IP_ADDRESS>:6697: Operation not permitted.

Using the command:
docker run --name ircd -p 6667:6667 inspircd/inspircd-docker

I get:
Warning! Some of your listener failed to bind:
<IP_ADDRESS>:6697: Operation not permitted.
Created from <bind> tag at /inspircd/conf/inspircd.conf:140
<IP_ADDRESS>:6667: Operation not permitted.
Created from <bind> tag at /inspircd/conf/inspircd.conf:206
<IP_ADDRESS>:7000: Operation not permitted.
Created from <bind> tag at /inspircd/conf/inspircd.conf:227
<IP_ADDRESS>:7001: Operation not permitted.
Created from <bind> tag at /inspircd/conf/inspircd.conf:228

Closing this as based on your Anope docker issue you seem to have fixed it. :)

I did indeed fix it but forgot to close this issue, thanks for closing it


[bulk] validation: fix disallowed html

This PR fixes 10 disallowed HTML issues.

Docs Build status updates of commit 8916534:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:warning:Warning

Details

Skype/SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md
:warning:Warning

Details

Skype/SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'DeviceClippingEventRatio element (QualityPropertiesType complexType)' is duplicated in: 'SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(2,8), SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(2,8)'. Titles must be unique within a docset.
Line 13, Column 1: [Warning: duplicate-h1s - See documentation] H1 'DeviceClippingEventRatio element' is duplicated with other articles: 'SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(13,1), SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(13,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'DeviceClippingEventRatio element (QualityPropertiesType complexType)' is duplicated in: 'SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(2,8), SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(2,8)'. Titles must be unique within a docset.
Line 13, Column 1: [Warning: duplicate-h1s - See documentation] H1 'DeviceClippingEventRatio element' is duplicated with other articles: 'SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(13,1), SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(13,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Global effort to fix build validation errors
@lindalu-MSFT
The Content & Learning team is fixing build validation errors on docs.microsoft.com for the rest of H2. This will eliminate potential accessibility, security, and usability issues. This PR includes only build validation fixes and does not change other content. Please review within five business days and merge or comment in the PR with any changes you'd like to see. Thank you!

Docs Build status updates of commit 93b7890:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Skype/SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md
:warning:Warning

Details

Skype/SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md
:warning:Warning

Details

Skype/SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'DeviceClippingEventRatio element (QualityPropertiesType complexType)' is duplicated in: 'SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(2,8), SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(2,8)'. Titles must be unique within a docset.
Line 13, Column 1: [Warning: duplicate-h1s - See documentation] H1 'DeviceClippingEventRatio element' is duplicated with other articles: 'SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(13,1), SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(13,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

Skype/SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md

Line 2, Column 8: [Warning: duplicate-titles - See documentation] Title 'DeviceClippingEventRatio element (QualityPropertiesType complexType)' is duplicated in: 'SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(2,8), SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(2,8)'. Titles must be unique within a docset.
Line 13, Column 1: [Warning: duplicate-h1s - See documentation] H1 'DeviceClippingEventRatio element' is duplicated with other articles: 'SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-c.md(13,1), SDN/articles/deviceclippingeventratio-element-qualitypropertiestype-complextype-skype-sdn-2-2-d.md(13,1)'. First level headings must be unique within a docset.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Add PermissionGrid Options for Polls

In a future release, we would want to create some PermissionGrid options for polls so that the Administrator has control of what groups can view or actions they can perform.
Read
View polls (maybe?)
View poll results
Create
Start a poll
Participate
Allow poll voting
Allow self-poll editing
Moderate
Delete polls
Edit polls
If you have any suggestions on what names we should use or what permissions I missed, please discuss here.

The Delete polls and Edit polls permission are added for the new version


[modify] gws/monitor enhancement

Changes Unknown when pulling 2301041e37d885ba1a3cebc89b1172e6294d7c73 on sunny4381:features/gws-monitor-enhancement into ** on shirasagi:master**.

Changes Unknown when pulling 0475a72a2890112e7a32db53a34b2b6979a8f342 on sunny4381:features/gws-monitor-enhancement into ** on shirasagi:master**.

Changes Unknown when pulling 0475a72a2890112e7a32db53a34b2b6979a8f342 on sunny4381:features/gws-monitor-enhancement into ** on shirasagi:master**.

Changes Unknown when pulling 011f424dfb87c6ffbc966a81cc6702f0a4b86747 on sunny4381:features/gws-monitor-enhancement into ** on shirasagi:master**.

Changes Unknown when pulling c6ef17cdeaf9d1e6ac6160ee91b34d9d082156d6 on sunny4381:features/gws-monitor-enhancement into ** on shirasagi:master**.

Changes Unknown when pulling c6ef17cdeaf9d1e6ac6160ee91b34d9d082156d6 on sunny4381:features/gws-monitor-enhancement into ** on shirasagi:master**.

Coverage decreased (-0.2%) to 80.037% when pulling ddb91975cc63741f3f3105cb23947d67aba34ed5 on sunny4381:features/gws-monitor-enhancement into 30219c2889442c9e918358540d2670165bc2b562 on shirasagi:master.


Build:  use partial clone for Builds (Reduces checkout duration)

A partail cone with  fetch with tree:0 is around 3 seconds. For a whole checkout it can be sometimes be minutes.
For example a linux build an checkout on linux can be 54 seconds to 6m 14 seconds
Theory behind it.
https://github.blog/2020-12-21-get-up-to-speed-with-partial-clone-and-shallow-clone/

You tried this before and then reverted it for some reason. Why is the situation different now?

filter: tree:0 was introduced with checkout@v4 and is the newer method for git to minmally clone.
The main difference is that fetch-depth:1 has only one version while  filter: tree:0  keeps the history but all not needed history is not fetched. and this reduces the clone speed drastically while not beeing so much slower.

Wow, advanced stuff. I know very little about this, thanks for the lesson.


Gaps in the data?

The animation seems to stop from time to time, e.g. at April 10 2013, 08:40 in the highest altitude or at the very beginning of the migration event in the low altitude.
Are these gaps in the data or is this due to the 0 migration values?

Any need to fix this?

I don't think we should fix gaps in data.  But it's always nice to have a distinction between a gap in the data (no data) and a zero value (measured but no migration). If I understand correctly currently we have put zeros where there are gaps. I think that is incorrect.  Would it be possible to have an n/a or something similar? Question is how to visualize if at all, could be a small dot, or for a zero small dot and when no data, then blank screen.

This gaps are caused by #55. Fix is described in #105. Closing.


JsValue::from_serde is very slow compare to pass string from WASM to js and then using JSON.parse to parse data

Summary
JsValue::from_serde is very slow compare to pass string from WASM to js and then using JSON.parse to parse data.
Additional Details
I tried to use 'wasm-bindgen' to test performance of a general senario: request data from server at WASM and then pass data to JS, and find that the JsValue::from_serde is very slow.
And then I change to just pass response text to JS instead, and then using JSON.parse to parse text to json data, which compare to 'from_serde' is way better performance.
So I wanna ask if there's anything I can do to improve from_serde perfroamce?
The perfomrance profile (need to remove extra extension 'txt')
Profile-from_serde_vs_json_parse.json.txt
The performance screenshot

And the demo repo to reproduce this issue: https://github.com/maple-leaf/rust-wasm-playgroud

It generally depends on where the time is being spent. If the time is being spent copying the data into wasm's linear memory, that's unfortunately pretty difficult. If the time is spent in JSON parsing itself then you could consider parsing in JS and then passing pieces to wasm so you don't copy all of the data. Unfortunately though I don't have time myself to dig into this and provide more help at this time.

You might want to use serde-wasm-bindgen instead which avoids JSON parsing / serialization. Also see tracking issue and previous discussion in https://github.com/rustwasm/wasm-bindgen/issues/1258.


Removes OpenSSL.

Not so much time ago, Apple updated CommonCrypto and now it includes AES256GCM and secp256r1 algorithms. From now on we can stop to use OpenSSL as our encryption dependency.
This will give to us next advantages:

Size of our SDK will be smaller.
We can distribute our SDK as sources (before this PR, with cocoapods, our SDK was distributed as compiled framework, and after some changes in our sources we should recompile our framework and push it to our VCS, from now on we will not do that). And I think that its very important for Swift libraries because Swift don't have ABI compatibility yet (framework compiled with 3.0 will not work with project that compiled with swift 3.1).
Much-much easier to debug our SDK in real project.

👍 👍 👍 👍 👍


Microphone recording doesn't work on Linux with official builds

Godot version: Git https://github.com/godotengine/godot/commit/924db5fa58ab28912857029ec8dd34fbde771550
OS/device including version: Fedora 30, PulseAudio
Issue description: Microphone recording doesn't seem to work on Linux, even though Godot appears as a capture device when running the Mic Record Demo:

Saving the file after recording a few seconds will write a WAV file that contains only a few seconds of silence. I made sure the microphone is not muted by recording a sample in Audacity beforehand (where it works correctly).
Steps to reproduce: Use the "Mic Record Demo" from godot-demo-projects. Click the Record button, say something, then press Stop. Save the audio to a WAV file then inspect it using a media player.

See also https://github.com/godotengine/godot-demo-projects/issues/359. This issue has been confirmed by @CombustibleLemonade in https://github.com/godotengine/godot-demo-projects/issues/359#issuecomment-547962679, so I'll add the confirmed label right away.
Edit: This issue is not exclusive to Linux and has been occurring on Windows and macOS too (both x86 and ARM).

Confirmed Linux Mint 19.2 Cinnamon, x64 Kernel 5.0.0-31-generic, Lenovo Laptop.

Confirmed on Ubuntu 18.04.3 on a Lenovo Thinkpad T420.

Confirmed on up-to-date NixOS unstable with KDE, PulseAudio.

Can this get added to 3.2 milestone, and how can we help troubleshoot the problem?

@FeralBytes Which Godot versions can you reproduce this on? Microphone support was added in 3.1.

I can reproduce this with 3.1.2

@Calinou 3.2 beta 4 is broken, also 3.1.1 is broken Also 3.1 Stable does not work. A what stage of 3.1 was it added at Alpha?  Ah 3.1 Alpha1 works. I then tested Beta 1 and it was broken. I then worked backwards and found that even 3.1. Alpha2 was broken.
So a change between 3.1 Alpha1 and 3.1Alpha2 broke mic recording for many versions of Linux.

@FeralBytes the change might be in the fa26a551. After reverting that in Master the recording started working for me. The changes look pretty innocent and I cannot tell just by looking what is the problem. Any thoughts @marcelofg55.

I can confirm @Zolzak's finding about the print_verbose().
Neither local builds of the  master nor the 3.2.2-stable

This was confirmed to also occur on Windows and macOS in https://github.com/godotengine/godot-demo-projects/issues/572.

This was confirmed to also occur on Windows and macOS in https://github.com/godotengine/godot-demo-projects/issues/572.

This was confirmed to also occur on Windows and macOS in godotengine/godot-demo-projects#572.

That's a different issue though. The issue on Linux is specific to official builds, mic input works fine on local builds with a recent PulseAudio.
Separate issues should be opened for Windows or macOS issues, which are likely all separate bugs (mic input is implemented in the audio drivers so it's platform-specific).

The problem is this:
The sample rate for you mic on your Mac and the Godot project need to match:

this still happens with 3.4.stable on linux ubuntu 21.10

Happens on Ubuntu 20.04.1 LTS with Godot_v3.4-stable_x11.64
The audiomixer shows that the microphone Godot is using does work but the data Godot records is silence

@enorrmann @mgschwan Can you reproduce this if you change the microphone's sample rate in the PulseAudio configurati

@enorrmann @mgschwan Can you reproduce this if you change the microphone's sample rate in the PulseAudio configuration files, then log out and back in again? This is apparently how you workaround the issue on macOS at least.

my samplerate is 44100,
with godot 3.2, in the sound panel, a new godot recording source appears and the app works ok
with godot 3.4.stable, nothing appears in the recording panel, and the app "hangs" when I hit play, then the console shows
1
44100
True
[0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0[...]

Its still happening in Godot 3.5 in Mac OS monterey.
M1 Pro - Macbook Pro

Its still happening in Godot 3.5 in Mac OS monterey. M1 Pro - Macbook Pro

Please open a separate issue to track the root cause on macOS, as it's likely different.

i get no audio from anything recorded on windows.

@idg32 this is a Linux specific issue, please open another one for Windows

In https://github.com/V-Sekai/godot-speech we added code from libsamplerate to resample audio arbitrarily to 48000hz.
@enorrmann has a sample conversion problem and this relates to that.

Not sure if this is the right place for that, but I have the same problem on FreeBSD
(13.1 with Godot 3.4.2 installed via pkg). pavucontrol (pulseaudio mixer) doesn't
show anything in its 'Recording'-tab when Godot is ostensibly recording, tho.
Playback works fine, recording just yields a completely silent audio stream, no errors.
Tested with own code as well as the mic recording demo.

Over 3 years later and this is still happening on Godot 4.01 stable. Recorded audio is silent every time. The length of the recording is accurate but the data is all 0s. You can clearly hear yourself with the Record bus unmuted, so imo the issue lies somewhere within the set_recording_active() and/or get_recording() functions. I tried to figure it out but I am not equipped enough to figure it out. Please help anyone :'(

This issue is still present, for me as well.
I can hear the feedback through the "Record" bus when unmuted, but the audio is being recorded.
On Arch Linux, kernel 6.2.9-zen1-1-zen
Godot v4.0.2.stable.flathub [7a0977ce2]

I was looking closely at the code and I'm no expert at C++ or threaded stuff. When set_recording_active is set to false, it never waits for the thread to finish. The code inside the thread _io_thread_process does know when to stop processing, but it seems like that function is still being called since the thread never finishes.
Also _io_thread_process really just calls _update_buffer. Though what's strange is that another function called _update also calls _update_buffer as well. I'm not sure where _update gets called from but it never checks if the recording has stopped.
Maybe I can try to clone the repo and test to see if there is any issues there.

I'm not getting any results so far except that PulseAudio sometimes exit badly when I stop hitting record. There is also sometimes where audio crackles though closing and opening the game fixes it. (aka when i keep the audio bus unmuted)
Data seems to be zero from the recording_data itself.
Note I'm using the mic_record demo from the godot projects demo repository as testing.
I added the ensure_thread_stopped function to when the set_recording_active is set to false and break early when the loop needs to stop, though that also didn't change anything. I'm not sure where the actual microphone input data is coming from.
Is AudioEffectRecord really the right thing to use here? The documentation says to use AudioEffectCapture to capture the voice and mentions nothing about AudioEffectRecord.
Looking it up more, it seems like AudioEffectRecord is meant only for recording your voice to a file and AudioEffectCapture is used for processing your voice in real time. https://github.com/godotengine/godot/pull/52441
Though I'm not sure why AudioEffectCapture can't just be used instead to save to a file if that's what the user is going to do?
Does AudioEffectCapture work here? I haven't seen anyone mention it yet so I guess I will test it out.

I had this issue with earlier betas on arch Linux, but since the release it works perfectly for me. Not sure if that means it's an issue with how it works or not, maybe some sort of driver difference? Idk

Does AudioEffectCapture work here? I haven't seen anyone mention it yet so I guess I will test it out.

What were your findings, @Nukiloco ?
@andersmmg: What did you use to record? AudioEffectRecord? Or AudioEffectCapture, like the docs say?

It works for me using the official audio record demo, which looks like it's using AudioEffectRecord

Does AudioEffectCapture work here? I haven't seen anyone mention it yet so I guess I will test it out.

What were your findings, @Nukiloco ?
@andersmmg: What did you use to record? AudioEffectRecord? Or AudioEffectCapture, like the docs say?

I haven't tested it out yet since I been busy doing other things currently.

Using git bisect between (working) 4.0.3-stable and (not working) 4.1.1-stable and the power of the following Nix expression
nix build --impure --expr '(builtins.getFlake "github:nixos/nixpkgs/nixos-unstable").legacyPackages.x86_64-linux.godot_4.overrideAttrs { src = ./.; }' -L
I have determined that the breaking change was at:
https://github.com/godotengine/godot/commit/98c655ec8db17e50afa58284b1dcad754034db4b
Unfortunately this commit doesn't look suspicious at all.  Further investigation is necessary.

I have definitely confirmed that this is the breaking commit, from two subsequent checkins in this list from around May 10
https://github.com/godotengine/godot/commits/master?after=c80a2b4fe99dcd0bba6fc24ed2748b1474b24448+1&branch=master&qualified_name=refs%2Fheads%2Fmaster

It's a very large commit, none of which appears to relate the the audio system, so I have no idea what's happened.
https://github.com/godotengine/godot/pull/75901/commits/98c655ec8db17e50afa58284b1dcad754034db4b

That's a different issue from this one which was reported in 2019 then, and seemed specific to build environments / runtime environments. Could you open a new issue about the 4.1 regression with those details?

More testing, i was reading through the source code and wanted to get more details. I run the test project in verbose mode, and all of the sudden, it starts to work.
For some unknown reason, verbose mode, fixes the issue?
And running without verbose mode, brings the issue back.
All I can assume here and what I'm guessing, is that the verbose printing is delaying something long enough for it to work?


The program runs fine, but some of the code on the display is white, no color

VSCode Version: 1.26.1
OS Version: MacOS
Steps to Reproduce:

Open a .tsx file
The program runs fine, but some of the code on the display is white, no color

Does this issue occur when all extensions are disabled?: Yes
This is all my code,I confirmed the file suffix ".tsx" and selected the language mode as "TyPeScript React".
import * as React from 'react';
import * as CSSModules from 'react-css-modules';
import { connect } from 'react-redux';
import { bindActionCreators } from 'redux';

import { WechatAccountHeader } from '../../../components/header';
import { WechatAccountInput } from '../../../components/input';
import { WechatAccountBigButton } from '../../../components/big_button';
import { check_phone_number } from 'src/utils/base';
import { Toast } from 'src/components/toast';
import { Link, browserHistory } from 'react-router';
import * as weui from 'weui.js';
import 'weui';

const style = require('./index.scss');

type WechatProps = {};
type WechatState = {
  is_next_active:boolean,
  mobile_input:string,
  toast_content:string,
  toast_is_show:boolean,
};

@CSSModules(style, { allowMultiple: true })
export class Component extends React.Component<WechatProps, WechatState> {
  constructor(props:any, context:any) {
    super(props, context);
    this.state = {
      is_next_active: false,
      mobile_input: '',
      toast_content: '',
      toast_is_show: false,
    };
  }
  go_next = () => {
    const mobile = this.state.mobile_input;
    if (check_phone_number(mobile)) {
      browserHistory.push(`/wechat_account/captcha/${mobile}?aim=reset`);
    } else {
      Toast.show('手机号输入不正确');
    }
  }
  mobile_input_change = (e) => {
    const { value } = e.target;
    this.setState({
      mobile_input: value,
    });
    this.setState({
      is_next_active: /\S+/.test(value),
    });
  }
  handle_no_bind = () => {
    weui.dialog({
      title: '手机号未绑定/不可用',
      content: '已购买过课程客户，请联系 “班主任” 处理。未购买过课程客户，请联系客服：400-8353-800 转 “ 1 ” 处理。',
      buttons: [{
        label: '取消',
        type: 'default',
      }, {
        label: '联系客服',
        type: 'primary',
        onClick: () => {
          location.href = 'tel:400-8353-800';
        },
      }],
    });
  }
  render() {
    const { state } = this;
    return (

        <WechatAccountHeader title="重置密码" is_show_logo={false}></WechatAccountHeader>
        <WechatAccountInput placeholder="输入手机号码" onChange={this.mobile_input_change}
          max_len={11}></WechatAccountInput>

          手机号未绑定/不可用？

          <WechatAccountBigButton text="下一步" is_active={state.is_next_active}
            handleClick={this.go_next}></WechatAccountBigButton>

        登录注册即表示你已阅读，并同意《用户注册协议》

    );
  }
}

const map_state_to_props = (state:any) => {
  return {};
};

const map_dispatch_to_props = (dispatch:any) => {
  return bindActionCreators(
    {},
    dispatch,
  );
};

export let ComponentContainer = connect(
  map_state_to_props,
  map_dispatch_to_props,
)(Component);

Is this a bug, or where did I make a mistake? However, I found this situation in several other files. I tried to restart it but it didn't solve it. Although it didn't affect the running of the program, there were suddenly a few pieces of color in the code that were not rendered. It was still a little uncomfortable.


WW does not deserialize strings with newline characters properly with Koalas dataframes

If I have a string column in a dataframe that contains newline characters and serialize and deserialize the dataframe, the deserialized dataframe is not recreated properly.
Code Sample, a copy-pastable example to reproduce your bug.
>>> import pandas as pd
>>> import databricks.koalas as ks
>>> import woodwork as ww
>>> from woodwork.deserialize import read_woodwork_table
>>> df = pd.DataFrame({
...     'id': [0, 1, 2, 3],
...     'comments': [
...         '\ncomment1\n',
...         '\nleading newline',
...         'trailing\n',
...         'in the \n middle'
...     ]
... })
>>> ks_df = ks.from_pandas(df)
>>> ks_df.ww.init()
>>> ks_df.ww.to_disk('.')
>>> new_df = read_woodwork_table('.')
>>> new_df
    id         comments
0  3.0          in the
1  NaN             <NA>
2  1.0  leading newline
3  2.0         trailing
4  0.0         comment1

Note - I did not investigate this thoroughly with pandas or Dask input, but it seems to be working as expected based on limited testing. That should be investigated more thoroughly.

We can escape the new line characters by encoding to unicode_escape then decoding to utf-8. I'm not sure how general this can apply to different use cases. I'll go through a quick example.
import pandas as pd
import databricks.koalas as ks
import woodwork as ww
from woodwork.deserialize import read_woodwork_table

df = pd.DataFrame({
    'id': [0, 1, 2, 3],
    'comments': [
        '\ncomment1\n',
        '\nleading newline',
        'trailing\n',
        'in the \n middle',
    ]
})

This is how we can escape newline characters in pandas.
encode = df.comments.str.encode('unicode_escape')
df['comments'] = encode.str.decode('utf-8')
df

   id           comments
0   0       \ncomment1\n
1   1  \nleading newline
2   2         trailing\n
3   3   in the \n middle

We can see that the new line characters were escaped by looking at the actual string values.
df.comments.values

array(['\\ncomment1\\n', '\\nleading newline', 'trailing\\n',
       'in the \\n middle'], dtype=object)

Now, serialization in koalas should work from here.
kdf = ks.from_pandas(df)
kdf.ww.init()
kdf.ww.to_disk('test')
new_df = read_woodwork_table('test')
new_df

   id           comments
0   1  \nleading newline
1   3   in the \n middle
2   0       \ncomment1\n
3   2         trailing\n

Koalas does not currently support unicode_escape.
ks.from_pandas(df.comments).str.encode('unicode_escape')

/usr/local/Caskroom/miniconda/base/envs/woodwork/lib/python3.8/site-packages/databricks/koalas/strings.py in encode(self, encoding, errors)
    995         Not supported.
    996         """
--> 997         raise NotImplementedError()
    998
    999     def extract(self, pat, flags=0, expand=True) -> "ks.Series":

NotImplementedError:

An alternative approach can be applying the escape to each element.
escape = lambda string: string.encode('unicode_escape').decode('utf-8')
df['comments'] = df.comments.apply(escape)

@jeff-hernandez Featuretools was able to serialize and deserialize this type of data without issue (at least I think so). You also might want to take a look to see if there is anything different between the serialization methods that might explain why it worked for Featuretools, but not for WW.
This came up when trying to serialize/deserialize the featuretools ecommerce entityset with Woodwork.
I guess it's possible that this wasn't working right in Featuretools and we never caught it...not sure...

It's also an issue in Featuretools. In a koalas entity set, the data before serializing does not match the data after deserializing.
import featuretools as ft

es = ft.EntitySet()
es.entity_from_dataframe(
    entity_id='comments',
    dataframe=ks.from_pandas(df),
    variable_types={
        'comments': ft.variable_types.NaturalLanguage,
    },
    index='id',
)

es.to_csv('data')
es2 = ft.read_entityset('data')
es2['comments'].df

   id          comments
0   3  in the \n middle
1   1   leading newline
2   2          trailing
3   0          comment1

This can also be resolved by escaping the newline characters as shown previously.

After some additional investigation, this behavior seems to be related to the default spark settings. By default spark strips leading and trailing whitespace characters and does not read/write data in a multi-line format during serialization. By passing additional parameters, this can be resolved:
import pandas as pd
import databricks.koalas as ks

df = pd.DataFrame({
     'id': [0, 1, 2, 3],
     'comments': [
         '\ncomment1\n',
         '\nleading newline',
         'trailing\n',
         'in the \n middle'
     ]
})
ks_df = ks.from_pandas(df)

Original DF:
   id           comments
0   0       \ncomment1\n
1   1  \nleading newline
2   2         trailing\n
3   3   in the \n middle

Serialization with default parameters:
ks_df.to_csv('test1')
new_df1 = ks.read_csv('test1')

         id         comments
0         3          in the
1   middle"             None
2         1  leading newline
3         2         trailing
4         0         comment1

Serialization with updated parameters:
ks_df.to_csv('test2', multiline=True, ignoreLeadingWhitespace=False, ignoreTrailingWhitespace=False)
new_df2 = ks.read_csv('test2', multiline=True, ignoreLeadingWhitespace=False, ignoreTrailingWhitespace=False)

   id           comments
0   1  \nleading newline
1   3   in the \n middle
2   0       \ncomment1\n
3   2         trailing\n


Fix highlight for identifiers starting with 'function'

In current yats.vim, identifier starting with 'function', like 'functionName', breaks highlighting
when placed in parentheses (i.e. not in top level).

This PR fixes the problem by modifying start condition of 'typescriptFuncImpl' syntax.
I'm not certain that this is the best way to do because I'm not familiar to vimscript nor its highlighting system though...

Thanks!


Setup production

Create deploy/prod.properties. In that file:

app-name=eauser-geomapper-dev
set the app-port to 8050 and the xcc-port to 8051
leave password blank: password=

Bootstrap and deploy to prod.

Should app-name=eauser-geomapper-prod instead?

that was a typo -- you can leave app-name out of prod.properties all together and rely on the default value instead. I'll fix that in the description.


Release v4.0.0

From 3.0.0 straight to 4.0.0.

Looks great; merge on test results.

@nathanielmanistaatgoogle thanks


Support for default value assignment will be added for values that are not found.

{
  title: { initial: "initial value" }
}

Closes: https://github.com/aykutkardas/muninn/commit/54de81a64f80b310b6a26b35ab95770b8444668c


rust config? I also have a rust config, maybe can make it better to use, maybe not. :)

also a basic config...
;; need cargo
;; cargo install racer
;; cargo install rustfmt

(when (maybe-require-package 'rust-mode)
  ;;(maybe-require-package 'cargo-mode)
  (maybe-require-package 'toml-mode)
  (maybe-require-package 'racer)

  (after-load 'rust-mode
    (add-hook 'rust-mode-hook #'racer-mode)
    (add-hook 'racer-mode-hook #'eldoc-mode)
    (add-hook 'racer-mode-hook #'company-mode)
    ;;(define-key rust-mode-map (kbd "TAB") #'company-indent-or-complete-common)
    (setq company-tooltip-align-annotations t)
    (setq rust-format-on-save t)
    )
  )

(add-to-list 'auto-mode-alist '("\\.rs\\'" . rust-mode))

(provide 'init-rust)

Thanks! I've just enabled company-tooltip-align-annotations by default. The rest, I think, is already covered elsewhere in my config (e.g. toml-mode, company-mode). rust-mode already adds the auto-mode-alist entry, and I'm not sure I want to enable rust-format-on-save by default, because I think it will break when users haven't installed rustfmt.


Component re-architecture

Allow for a simple API to add Palladio components to a web page.

[x] timespan
[x] map
[x] facet
[x] table
[x] graph
[ ] timeline
[ ] gallery

This was started and is now merged into master. We have an initial take on timespan, facet, map, and table components.

Still todo:

[x] timespan
[x] map
[x] facet
[x] table
[ ] graph
[ ] timeline
[ ] gallery

Need timeline for 1.1

Timeline is now a component.

Re-assigning milestone to 'Next'. The components we wanted for 1.1 are complete.


[Sema] Fix spurious use_local_before_declaration errors.

The current implementation of type checker is overly strict for use_local_before_declaration cases.
When performing name lookup for UnresolvedDeclRefExpr, if a local declaration after use is detected, an error is raised immediately, without checking outer results where legal candidates may occur.
This PR adds relevant checking to see if we can find better matching candidates from outer results before raising a use_local_before_declaration error.

Resolves SR-7660.

I think it would make more sense if name lookup was driven by a source location and didn’t find declarations before their definition at all.

@DougGregor is probably the best person to review this and give guidance.

@swift-ci please smoke test

Thanks for the comments and review.

@swift-ci please smoke test


Middleware on a Per-Route Basis

After looking at the project's documentation, and poking around with sunder for a bit, I was wondering if functionality exists to allow multiple middleware per route, say similar to koa-router.
If not, is that within the scope of any potential future work?
In any case, super awesome tool I'd love to use in the future!

After messing around a bit more, was able to come up with a potentially simple-enough solution that allows for a variable number of middlewares on a given route declaration. With some cursory testing it appears to work without issue.
Usage:
router.get('/my/api/path', withMiddlewares(middlewareOne, middlewareTwo, myHandler))```

### Declaration:
```typescript
import { apply, Context, Handler } from 'sunder';
import { Env } from 'my/package/env';
import { PathParams } from 'sunder/middleware/router';

export const withMiddlewares = <T extends PathParams<any>, U>(...middlewares: Handler<Env, T, U>[]) => {
    return async (ctx: Context<Env, T>) => {
        try {
            await apply(middlewares, ctx);
        } catch (e) {
            console.error(e);
            throw e;
        }
    };
}```

Ah! I think I just found provided solution using compose:
import { Router, compose } from 'sunder'
import { Env } from './bindings'
import { handleBar } from './handlers'
import { withFoo } from './middleware'

export function registerRoutes(router: Router<Env, any>) {
  router.get('/', compose([withSentry, handleDebug]))
}

Hth!

I think compose is the best answer here :). We could in the future allow multiple arguments instead (and if there are multiple, we call compose internally).


Switch to kubelet plugin watcher mode

KubeletPluginWatcher is enabled by default in kube-1.12.0;
This commit switches registration of Device Plugin to watcher
mode instead of explicitly calling Register in Device Plugin.
This also means Device Plugin will only work with
KubeletPluginWatcher featureGate enabled.

Change the commit title to "Introduce kubelet plugin watcher model " and updated another version;
tested with kube-1.12.0; device plugin can be re-registered when kubelet gets restarted.

Deprecating this PR ( it is outdated and was created against master branch ) and creating a new one to add plugin watch support in release-v1 branch.


First DataBinder integration

First ServiceX DataBinder integration
Only for Python transformer for this PR

I see that you have write permission to this repo. Instead of a fork, your could move your changes to a branch of this repo so I can also push commits to it.


Help with : LoRA issue in distributed setting

System Info
Hello there, i'm trying to follow this tuto from the documentation in order to finetune a model in a distributed setting (currently testing with a 7B model), I'm doing the training in huggingface's spaces using a Jupyter docker image with 4 L4 GPUs (using terminal not notebook)

The error is simpy ModuleNotFoundError: No module named 'torch._six'
Who can help?
@pacman100 and @stevhliu
Information

[X] The official example scripts
[ ] My own modified scripts

Tasks

[X] An officially supported task in the examples folder
[ ] My own task or dataset (give details below)

Reproduction
My script so far :
git clone https://github.com/huggingface/peft.git
cd peft

# trying to make sure everything is installed
pip install -r requirements.txt
pip install -r examples/sft/requirements_colab.txt
pip install -r examples/sft/requirements.txt

accelerate config --config_file deepspeed_config.yaml

accelerate launch --config_file "deepspeed_config.yaml"  examples/sft/train.py \
--seed 100 \
--model_name_or_path "meta-llama/Llama-2-7b-hf" \
--dataset_name "AbderrahmanSkiredj1/moroccan_darija_wikipedia_dataset" \
--chat_template_format "none" \
--add_special_tokens False \
--append_concat_token False \
--splits "train,test" \
--max_seq_len 2048 \
--num_train_epochs 1 \
--logging_steps 5 \
--log_level "info" \
--logging_strategy "steps" \
--evaluation_strategy "epoch" \
--save_strategy "epoch" \
--push_to_hub \
--hub_private_repo True \
--hub_strategy "every_save" \
--bf16 True \
--packing True \
--learning_rate 1e-4 \
--lr_scheduler_type "cosine" \
--weight_decay 1e-4 \
--warmup_ratio 0.0 \
--max_grad_norm 1.0 \
--output_dir "llama2-7b-wiki-ary-sft-lora-deepspeed" \
--per_device_train_batch_size 8 \
--per_device_eval_batch_size 8 \
--gradient_accumulation_steps 4 \
--gradient_checkpointing True \
--use_reentrant False \
--dataset_text_field "content" \
--use_flash_attn True \
--use_peft_lora True \
--lora_r 8 \
--lora_alpha 16 \
--lora_dropout 0.1 \
--lora_target_modules "all-linear" \
--use_4bit_quantization False

Expected behavior
to finish training and push the adapter to the hub !?

Based on the error message, it's almost certainly not a PEFT issue, the same would happen if you did not use PEFT. Instead, it seems that your deepspeed version and PyTorch versions don't match. In this order, try upgrading the following packages and check if this solves the problem:

deepspeed
torch
accelerate

Oh, and a tip for the future, don't post screenshots, paste the text instead when writing an issue.

Thanks dear @BenjaminBossan 🤗


Use global instead of constant stdin, stdout and stderr

This makes it possible to use http://ruby-doc.org/stdlib-2.0.0/libdoc/minitest/rdoc/MiniTest/Assertions.html#method-i-capture_io to capture the output of byebug in tests (more context: https://github.com/deivid-rodriguez/pry-byebug/pull/90)

@bouk It seems that you managed to solve this issue with testing pry-byebug through other mechanism, so since this part of the code is very likely to change in the near future (to fix #229), I'll close this.
I'll get to your PR in pry-byebug soon.
Sounds good?

@bouk I'm doing some work for #229 and I think this is a good easy way to get it tested. Could you rebase this so I can merge it?

Thank you! :)


Fixed invalid RT_GROUP_ICON when adding icons directly from the Writer class

Resource type RT_GROUP_ICON weren't written properly when calling the AddWin32Icon methods on the Writer class, the ID of each GRPICONDIRENTRY were written as an INT instead of a USHORT.

Wow! How did you ever find this? Thanks so much!

That's exactly what I told myself when I found it hehe.  I was trying to find a method to make ILMerge use a different icon for the output file that the source or the attribute assemblies.  So after experimenting with the AddWin32Icon method of the Writer class, I couldn't get it to work (the generated exe only contained the first icon size, and the rest were missing). I then tried loading the that generated exe in a win32 resource viewer, and I had the same problem (only the first icon size was showing).
I ended up writing a test .net app that would parse all the icons from the Win32 resources, and only after that I noticed that all GRPICONDIRENTRY icon structures were there, but only the first one had correct values, all subsequent structures values were invalid.  I then came to the conclusion that ILMerge must not be writing them properly, debugged it and found it.
I assume that it was never reported as this method is not really exposed as an option in the ILMerge.exe, I just stumbled on it because I ended up calling it.
Glad I could help.

Very impressive! Congrats!


[cli][tf] bug fix for custom event patterns + cleanup

to: @ryandeivert
cc: @airbnb/streamalert-maintainers
size: small
Background
Bug fix for supporting cross-account IDs in custom CloudWatch event patterns
Changes

Bug fix on custom event patterns - It wasn't properly handling custom JSON input
Small code cleanup

Testing
Deployed in test account

Coverage remained the same at 95.35% when pulling 2b5ad0667fe2601e84462a8e88725cc9de60faf2 on jacknaglieri-cloudtrail-event-patterns-fix into 1c0006010d61459d714f0daf158680f8ad4bf77a on master.


Maintainer Nomination: Brandon Lum

Maintainer Nomination: Brandon Lum

GitHub handle: @lumjjb
Note: This nomination is part of the initial community bootstrap.
Sponsoring Maintainers
A community member may also be accepted as nominee if sponsored by a commitee of
maintainers. Please refer to GOVERNANCE.md for details about
the nomination by commitee process.

@puerco
@luhring

💬 Discussion Start Date:
A decision on the nomination shall be discussed for no longer than 30 days after
the discussion start date. After the the discussion period is over, the vote
tally will be computed and the nomination will be accepted or rejected.
Start Date: 2023-01-21
🗳 Voting Results
Final Enhancement Vote Tally:
👍 : X Votes
👎 : X Votes
Result: APPROVED | REJECTED
ℹ Voting Instructions:
To vote for this nomination, maintainers should add a comment with a 👍 emoji
to show support or 👎 to reject the enhancement.  After voting is over (usually
after 30 days), votes will be computed by the project's mantainers and
registered in this issue. Refer to  GOVERNANCE.md for details
on how many votes are required to approve and when voting ends.

We have the thumbs up from all the initial roster of maintainers, therefore @lumjjb is now formally accepted to the OpenVEX team. Welcome on board Brandon! :tada:


Are custom single.html or list.html layouts possible with this Theme?

Is it possible to have custom layouts for certain types of content when using this theme?
This is how my content structure looks like. Practice tests display content from /content/questions

Now I wanted to create a custom layout /layouts/questions/single.html but then it shows 404 Page Not Found.
So are custom layouts possible whilst keeping the side navbar and other components and just changing the inner content display?

not sure, if this is true also for single.html. to define a custom layout, you need to populate the archetype metadata variable in each document like archetype: question (YAML header). additionally your custom template should be in a folder <customtheme>/layouts/partials/archetypes/question/, and you would need to specify this "custom theme" in your Hugo config like
theme:
  - "customtheme"
  - "hugo-theme-relearn"

At the moment I must confess it's overcomplicated and too difficult to do such modifications.
So before ripping everything apart, what kind of modification do you want to achieve?

Leaving the menu and only customize the content area of a post?
Completly change the whole page including menu, topbar, search, etc.?

I wanted to modify the content (or "article") part and @cagix lead me to the archetypes which worked fine for me here
I am quite new to Hugo and I guess it was confusing to me that "archetype" was somehow connected to what layout will be picked.
I thought of archetypes as predefined content pages but what layout would be picked is not based on the frontmatter but the section in which the content page resides. So in my case I thought I would need to create /layouts/questions/single.html
This can be closed


Issue labels and management

We currently have very few issue labels, and few ways to sort issues. I think this could be improved to make it easier for both users and maintainers to work on this. The main goal of this issue is to start a discussion. All ideas presented here are debatable, so feel free to chip in!
Priority
Personally, I would like to have a way to assign priority to issues, to help focus development:

Priority: high
Priority: medium
Priority: low

Alternatively, P: high.
Instead of priority, bugs could instead be labeled 'Severity'. If something is truly blocking users, this could then be looked at first.
Difficulty
Second, attributing approximate difficulty to issues would also help (especially for newcomers):

Difficulty: high
Difficulty: low

Alternatively: D: high or to mimic the Rust project: E: high with E standing for Experience.
Combined with the Priority/Severity label, this could help in deciding on what to work: a high priority, low complexity task is basically a low-hanging fruit and could even be worked on by external occasional contributors. We could keep good first issue and ħelp wanted as they seem to complement this nicely.
Component
I don't think any of us is an expert on the whole codebase. Categorizing issues based on what code is impacted would really help developers focus on their own area of expertise. Deciding what is or is not a component in swhkd may not be straightforward and may need some discussion. Here are some ideas:

Component: swhks
Component: parser
Component: daemon

Again, this could be shortened to C: swhks for instance.
If possible, I think all these should be assignable by maintainers only (especially for priority or difficulty).

Is shorthand ideal here? (for example D: high or E: high)
That might be confusing for new contributors. I'm all for Difficulty/Experience/Component.

You're right, I think the shorthand version is a bit confusing.
If we find the longer version too verbose at some point, we can always change to the shorthand.

Yep that works! I'll go ahead and make the labels and we can slowly start to triage issues as we start working on them.

I've created the labels. I'll go ahead and close this issue and slowly start triaging all reports.
Note: all the labels apart from bug are gated to maintainers.


Fix up mixup of age/height

We currently use age/height as identifiers for values related to CLTV and CSV. However we get them mixed up in the function call to from_txdata. Do a few improvements to fix the mixup and improve the overall situation.

Patch 2 is a breaking change, changes a public method name.
Patch 1 an 4 are bug fixes.

(This description and PR are totally re-written, the comment directly below is now stale.)

Are we actually using age and height to classify things? I would expect two classifications - height vs time and relative vs absolute ... where I would expect age to be a synonym for relative.

Done reviewing 3d76d02ba95c1372d7126c08e7a1f47fc0743fb9.
I'm still confused by the logic in the last commit ... it seems like we are using "height" vs "age", which as I've mentioned in my first comment, seems like a wrong way to classify. But maybe this should be fixed in a later PR? This PR is definitely an improvement.

I'm trying to detangle things here in rust-miniscript while simultaneously creating the new 'timelocks' API in rust-bitcoin. I'm held back by the fact that I keep getting confused, for the last two weeks I thought 'age' went with CLTV, only after your original comment on this PR did I realize the mix ups we had.

I'm still confused by the logic in the last commit ... it seems like we are using "height" vs "age"

I thought I was in line with your original comment, the last commit fixes the fact that we pass the wrong value to evaluate_older and evaluate_after. It also removes the usage of 'age' in relation to CLTV but keeps the usage of 'age' for CSV.
I'm taking baby steps, mainly focusing on CLTV. The weakness in this approach is I'm not 100% across all the intricacies of CSV right at this minute so this might mean some churn when I move onto that part of the timelocks.

evaluate_after should take an absolute timelock while evaluate_older should take a relative one. Height versus time is a different classification.

evaluate_after should take an absolute timelock while evaluate_older should take a relative one. Height versus time is a different classification.

I think we are on the same page, I believe the PR is correct, and believe that patch 1 and 4 are rectifying real bugs.

I pushed an additional patch that removes height in favour of lock_time. I left it separate because I think its better to see each tiny change as a separate patch even though they are all interdependent. Can squash the whole thing into a single patch once you are convinced the changes are correct also.


Pandas library version.

Is pandas library latest version going to work with the code?

Pandas version I have on my machine where I made the tests is pandas 1.0.1. The latest version is 1.0.4 and I don't believe there are lots of differences in the main functionalities.


Create a guide for porting WAMR to a new architecture

Such a document should be helpful for the commuity contributors porting WAMR for new architectures.

https://github.com/bytecodealliance/wasm-micro-runtime/blob/main/doc/port_wamr.md


chore(docs): should be LiveScript not typescript in CHANGELOG.md

Back to b6df2cf there was a confusion between LiveScript and typescript.

Thanks! Merged as 31b7bf44babf64f5e2f21bc08d0032384b5cc96c


[CI/Tooling] Remove hardened_runtime argument for the agent.omnibus-build invoke task

What does this PR do?
This PR removes the hardened_runtimes flag in the agent.omnibus-build invoke task.

Motivation
According to the comments it was used to build the Agent on MacOS < 10.13.6. According to the Agent Installation Instructions:  Agent v7.38 is the last release to support macOS 10.13. (we're in 7.50 rn).

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

The MacOS build job will fail because the --hardened-runtime is used there.


Add filtering information to processing docs

Closes #18. In this PR, I'm adding in the section about how we created the filtered counts matrix post processing with Alevin-fry. I added in a brief paragraph about using DropletUtils::emptyDrops() including a sentence about what it does, our choice of lower=200, and then how we actually filtered on the FDR <= 0.01. Please let me know if the explanation is at the right level of detail or not.
Another thing I wanted to note here is that we haven't yet mentioned the actual file types that we are working with or that we have both an unfiltered and filtered output. I was wondering if we should include that here somewhere or have a separate section describing what files are included for each sample (Maybe this is a good candidate for a FAQ)?
Also in this PR I removed the headers for bulk RNA seq and spatial since that will not be part of MVP I thought it made sense to remove for now and then we can add it in when we set up the workflow for those.

Another thing I wanted to note here is that we haven't yet mentioned the actual file types that we are working with or that we have both an unfiltered and filtered output. I was wondering if we should include that here somewhere or have a separate section describing what files are included for each sample (Maybe this is a good candidate for a FAQ)?

This is tracked in #6 so if you have thoughts after writing this, you can jot them down there!

@jashapiro I changed the intro section to combine what I had with what you had suggested. Let me know what you think!


Not working website: https://node-projects.github.io/web-component-designer-demo/index.html

I've a complex website wich is a designer application for HTML. (https://node-projects.github.io/web-component-designer-demo/index.html)
It did not work in old Ladybird, and does not in current.
But with the version from today, it intially loads (great progress)

It uses many new webstandards (shadow dom, adopted stylesheets, ...)
at the moment it prints out many fixmes:

What it should look like:

Since new version, every fixme is printed twice:

The layout actually looks much better on master:

From Shannon's screenshot it looks like this issue is resolved (besides the problem in #1082). I'll close this as resolved for now, but if you can put together any reduced test cases of issues you're seeing, please do post them as new issues so they can get fixed. :^)

@AtkinsSJ
what means resolved? The website shows, but it does not work.

I've create sub issues:
https://github.com/LadybirdBrowser/ladybird/issues/356
https://github.com/LadybirdBrowser/ladybird/issues/1037
If they are resolved, I'll look what next is missing, but the site is not workin yet, so this issue should be left open


How can I make Oura use the configs from daemon.toml?

How can I make the dump command (e.g.: oura dump relays-new.cardano-mainnet.iohk.io:3001 --bearer tcp --since 63064696,1d9c6ddfe10bb15081f30bd26d26560b6d3d2a7d3eff8174e5f255b81424af36) "see" the configurations I set in the daemon.toml file? In the Mapper Options page it only mentions the options themselves, but not where the daemon.toml file should be.
I am running it on OSX, in case it makes any difference.

@pedromtcosta there should be a flag --config which then takes a path to the daemon.toml file. If it's missing from that subcommand specifically, we should be able to add it.

I think dump is missing the --config flag indeed. I get this error when trying: oura dump relays-new.cardano-mainnet.iohk.io:3001 --bearer tcp --since 63064696,1d9c6ddfe10bb15081f30bd26d26560b6d3d2a7d3eff8174e5f255b81424af36 --config /Users/me/_source/github/txpipe/oura/daemon.toml
error: Found argument '--config' which wasn't expected, or isn't valid in this context

	If you tried to supply `--config` as a value rather than a flag, use `-- --config`

USAGE:
    oura dump --bearer <bearer> --since <since> <socket>

For more information try --help

hi @pedromtcosta. The daemon.toml file is meant to be used with the oura daemon command. The daemon command allows you to do anything that the other commands provide.
The dump and watch commands are just shortcuts to hardcoded pipeline configurations to avoid writing the same daemon.toml file for common use-cases.
In fact, trying to incorporate a custom config file into the watch / dump commands would generate some weird conflicts (for example, using a webhook sink configuration on a watch command doesn't make much sense).
To accomplish what you need, I suggest running oura daemon --config ./daemon.toml directly with a config that matches what the dump command does. The toml file would look something like this:
[source]
type = "N2N"
address = ["Tcp", "relays-new.cardano-mainnet.iohk.io:3001"]
magic = "mainnet"

[source.intersect]
type = "Point"
value = [63064696, "1d9c6ddfe10bb15081f30bd26d26560b6d3d2a7d3eff8174e5f255b81424af36"]

[sink]
type = "Stdout"
format = "JSONL"

@scarmuega good point, adding a config flag to dump or watch would  indeed cause conflicts. I hadn't thought of that.

Thanks, @scarmuega! That's indeed what I need. May I ask what is the difference between the --since flag from dump and the --cursor flag from daemon? The only issue I have with the solution is that I can't use the --since flag anymore, but it seems the --cursor flag does the same thing, is this correct?

@pedromtcosta the since flag is equivalent to the [source.intersect] section, it allows you to define from which point in the chain you intend to crawl. You can find more info here: https://txpipe.github.io/oura/advanced/intersect_options.html
The cursor flag is meant to be a workaround to deal with restarts of the process. When running Oura for long periods of time, it is probable that an unexpected restart will occur. In that scenario, we want to keep going from the last point seen (as opposed to start all over again). Passing the cursor flag to the daemon command will effectively bypass the configured intersect point.

@scarmuega I understood --since is equivalent to [source.intersect], but my problem with using [source.intersect] in this case is that I'd need to create several daemon.toml files (I am spawning multiple oura processes in parallel). Effectively, what's the difference in the output when using [source.intersect] as opposed to --cursor? It seems to me that both do the same thing

@pedromtcosta intersect is for initial start in which case a cursor file doesn't exist yet. If you want a cursor, it'll make one for you and use it to track progress. Otherwise on restart oura would start from the intersect once again instead of the cursor.
intersect -> on start
cursor -> on restart
On restart, if cursor exists override intersect as the starting point.

Closing this as the answers solved my problem. Thank you @rvcas and @scarmuega!


Upgraded to SKY UX 2 beta; renamed SKY Pages to SKY UX Builder

Current coverage is 100% (diff: 100%)

Merging #35 into master will not change coverage

@@           master   #35   diff @@
===================================
  Files          21    21
  Lines         439   436     -3
  Methods        53    53
  Messages        0     0
  Branches       45    45
===================================
- Hits          439   436     -3
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update 5370845...5b62f9f

In the interest of not ripping up too much stuff I left any internal variables, file names, etc. that reference SKY Pages as-is.  I think we can continue to use skyux as the config property name since it'll match the repo name.


User should be able to change its avatar

We cannot identify a user just by looking at its avatar. Tinygraphs are great but for placeholders.

Improve profile view by adding UI to upload a picture (need to add a bucket to Google Cloud Platform)
Add new property to User entity to store avatar's URL
Handle new property in the app (if NULL we display the Tinygraph)

We should do the same for Team and Tournament


[FEATURE] Update README.md  -> Adds list of algorithms separated by topic and in increasing difficulty

Detailed Description
It could be useful improve the content of the README.md file adding:

Logo and a link to the forum room of the community.
List of all the algorithms shown in different tables, according to the topic, for example:

Sorting

Algorithm 1

Algorithm 2

Searching

Algorithm 1

Algorithm 2

Context

Listing all the algorithms in increasing difficulty order will be helpful for students and beginners

Great point. Please check the new documentation website:
https://thealgorithms.github.io/C-Plus-Plus
and its "Files" tab.
Would that address the above concerns?

Feel free to reopen the issue if you think this is not addressed and any suggestions as to why you think it is not fixed would be helpful.


trace orchestration -s failed

add trace to troubleshooting the kcp-cli "orchestration <orch_id> operations" failed to filter using "--state failed"

@lauraanddolay is this issue still exists? is there an issue in the github for that? can you test it as your separate KEB instance on DEV (you can contact me how to do that)

/uncc

/uncc @wozniakjan

/uncc @wozniakjan

/uncc


color_threshold missing since v2.1.2

Checklist

[x] I updated the card to the latest version available
[x] I cleared the cache of my browser
[x] I verified that I'm really running the lastest version in my browser console
[x] I checked if there is another issue opened with the same problem

Describe the bug
Experimental color_threshold is not being rendered, graphs just come out grey.
Version of the card
Version: 2.1.2
To Reproduce
This is the configuration I used:
type: custom:apexcharts-card
experimental:
  color_threshold: true
header:
  show: true
  title: Next agile rates
stacked: false
graph_span: 23h
span:
  start: day
  offset: +24h
series:
  - entity: event.octopus_energy_electricity_REDACTED_next_day_rates
    type: column
    curve: stepline
    name: p/kWh
    group_by:
      func: first
      duration: 5m
    extend_to: false
    stroke_width: 3
    show:
      extremas: time
    color_threshold:
      - value: -100
        color: cyan
      - value: 0
        color: green
      - value: 20
        color: orange
      - value: 30
        color: red
      - value: 40
        color: purple
    data_generator: |
      return entity.attributes.rates.map((entry) => {
         return [new Date(entry.start), entry.value_inc_vat*100];
       });

Screenshots

Expected behavior
Until this week, when I upgraded to HA 2024.7.2 and apexcharts v2.1.2 the columns were coloured according to the thresholds, now they are all grey.
Desktop (please complete the following information):

Browser Firefox (Linux)
Version 127

Smartphone (please complete the following information):

Device: Samsung
OS: Android 14
Browser Firefox
Version 128

Additional context
The headers appear to be coloured correctly as the entity state changes over the day, but the chart remains grey.

I must be doing something wrong... color seems to be ignored even without color_threshold

Again, the header has the right colours, but the chart does its own thing

Disregard the comment from 5 minutes ago... A browser cache clear fixed that, but color_threshold is still not working for me.

Same here, adding another screenshot, sorry I'm on mobile.

And just to confirm, reverting to version v2.0.4 fixes the issue and colours are shown according to the thresholds again. v2.1.0 and (unsurprisingly) v2.1.1 both have the bug. I've looked at the changelog for v2.1.0 and can't see any obvious commits that would be worth me looking more closely at.
Sorry I'm not a js person so that's the extent of my debugging ability!

btw: only column-charts are affected. When you use "type: line" color_threshold is working.

+1 on this issue for bar charts.

+1

same issue here
according to this comment on the HA forum it seems that a gray border has been added to the bars and covers the original color.

I've got a possible solution for myself and may provide a temporary resolution for others whilst whatever has happened in the background is fixed  (unless I misunderstand the situation and they way stroke_width was being used by myself and others).
So on to the solution I've found, there's a relationship between the following CSS styles being applied to columns which you can view in developer tools and the issues we're seeing in the way that the columns are being generated:
path[Attributes Style] {
    d: path("M 367.934 280.641 L 367.934 91.2086 L 368.515 91.2086 L 368.515 280.641 Z");
    fill: rgb(255, 0, 0);
    fill-opacity: 1;
    stroke: rgb(168, 168, 168);
    stroke-opacity: 1;
    stroke-linecap: butt;
    stroke-width: 5;
    stroke-dasharray: 0;
    clip-path: url(#gridRectMask6mmoop78i);
}

The giveaway is the following value: stroke: rgb(168, 168, 168);  this results in the grey colour we're witnessing.  i.e.

Setting the value of stroke_width to 0 correctly formats the columns that were previously being filled grey.

+1 on this one. Might be something else as well in my case, but at least the color_threshold is not right. I am trying to get the most out of the space in the card, and using the top line with a bit of a trick to display electricity price "level" with mostly colors.
In version 2.0.4:

In version 2.1.x: (sample 2.1.2)

My Yaml for the left graph is:
type: custom:apexcharts-card
card_mod:
  style:
    .: |
      ha-card {
        transform: translate(0,-7px);
        padding-top: 0px;
      }
      div#header__states {
        padding-top: 213px;
      }
      div#state__value {
      }
      div#state__name {
        transform: translate(0px,-8px);
      }
experimental:
  color_threshold: true
cache: true
graph_span: 24h
show:
  loading: false
update_delay: 30s
span:
  end: hour
apex_config:
  chart:
    height: 245px
  yaxis:
    - id: left
      show: true
      opposite: false
      decimalsInFloat: 0
      labels:
        formatter: |
          EVAL:function (value) {
            return value+" L";
          }
    - id: right
      show: true
      opposite: true
      decimalsInFloat: 0
      tickAmount: 5
      labels:
        formatter: |
          EVAL:function (value) {
            return value+" W";
          }
    - id: elpris
      show: false
      min: -200
      max: 1
      opposite: true
      decimalsInFloat: 2
hours_12: false
header:
  show: true
  floating: true
  colorize_states: true
  title: ' '
  show_states: true
series:
  - entity: sensor.water_usage_hourly
    type: area
    name: Vatten
    color: '#8ab4f8'
    stroke_width: 1
    yaxis_id: left
    group_by:
      func: max
      fill: last
      duration: 1h
    show:
      legend_value: false
      in_header: false
      in_chart: true
  - entity: sensor.energy_5min_period
    color: '#ff0000'
    yaxis_id: right
    stroke_width: 1
    curve: smooth
    name: Energi
    unit: W
    extend_to: false
    transform: return x>0 ? x*1000*60/5:null;
    show:
      legend_value: false
      in_header: false
      in_chart: true
  - entity: sensor.nordpool
    name: Spot
    stroke_width: 12.8
    yaxis_id: elpris
    type: column
    time_delta: +1h
    group_by:
      func: last
      duration: 1h
    show:
      header_color_threshold: true
      in_header: false
    float_precision: 3
    unit: c/kWh
    transform: return (x*100);
    opacity: 1
    color_threshold:
      - value: -100
        color: blue
      - value: 5.88372
        color: green
      - value: 8.38372
        color: lightgreen
      - value: 10.88372
        color: yellow
      - value: 13.38372
        color: orange
      - value: 15.88372
        color: orangered
      - value: 18.38372
        color: red
      - value: 20.88372
        color: darkred
  - entity: sensor.phyn_pp1_daily_water_usage
    yaxis_id: left
    name: Vatten
    color: '#3498db'
    show:
      in_header: true
      legend_value: false
      in_chart: false
  - entity: sensor.energy_cost_today_v10
    yaxis_id: elpris
    color: '#ff0000'
    name: El idag
    float_precision: 2
    transform: return Number(x).toFixed(2).toString();
    show:
      in_header: true
      legend_value: false
      in_chart: false

..and for the right graph:
type: custom:apexcharts-card
card_mod:
  style:
    .: |
      ha-card {
        transform: translate(0,-7px);
        padding-top: 0px;
      }
      div#header__states {
        padding-top: 213px;
      }
      div#state__value {
      }
      div#state__name {
        transform: translate(0px,-8px);
      }
hours_12: false
cache: true
experimental:
  color_threshold: true
  disable_config_validation: false
graph_span: 36h
span:
  offset: +12h
now:
  show: true
show:
  loading: false
update_delay: 30s
header:
  show: true
  floating: true
  colorize_states: true
  title: ' '
  show_states: true
apex_config:
  chart:
    height: 246px
yaxis:
  - id: left
    show: true
    opposite: false
    max: 5
    apex_config:
      decimalsInFloat: 1
      tickAmount: 5
      labels:
        formatter: |
          EVAL:function (value) {
            return value.toFixed(1)+" mm";
          }
  - id: right
    show: true
    opposite: true
    apex_config:
      tickAmount: 5
      decimalsInFloat: 1
      labels:
        formatter: |
          EVAL:function (value) {
            return value.toFixed(1)+" °C";
          }
  - id: elpris
    show: false
    min: -2000
    max: 1
    opposite: true
    apex_config:
      tickAmount: 5
      decimalsInFloat: 3
series:
  - entity: sensor.nordpool
    stroke_width: 12
    name: ' '
    color: '#1d1d1d'
    yaxis_id: elpris
    type: column
    time_delta: +1h
    group_by:
      func: last
      duration: 1h
    show:
      header_color_threshold: true
      in_header: false
      legend_value: false
    float_precision: 3
    unit: c/kWh
    transform: return (x*100);
    opacity: 1
    color_threshold:
      - value: -100
        color: blue
      - value: -100
        color: blue
      - value: 5.88372
        color: green
      - value: 8.38372
        color: lightgreen
      - value: 10.88372
        color: yellow
      - value: 13.38372
        color: orange
      - value: 15.88372
        color: orangered
      - value: 18.38372
        color: red
      - value: 20.88372
        color: darkred
  - entity: sensor.ring_i_torvmossvagen_temp_avg
    extend_to: now
    yaxis_id: right
    color: '#e74c3c'
    name: Ute temp
    stroke_width: 2
    show:
      in_header: false
      legend_value: false
  - entity: sensor.ring_i_torvmossvagen_regn_houly
    yaxis_id: left
    type: column
    color: '#3498db'
    name: Regn
    stroke_width: 3.8
    transform: 'return x>0 ? x : null;'
    show:
      in_header: false
      legend_value: false
  - entity: sensor.laajalahti_hourly
    yaxis_id: right
    name: '  Prognos'
    color: '#9b59b6'
    unit: °C
    stroke_width: 2
    show:
      in_header: false
      legend_value: false
    data_generator: |
      return entity.attributes.forecast.map((entry) => {
        return [new Date(entry.datetime).getTime(), entry.temperature];
      });
  - entity: sensor.laajalahti_hourly
    yaxis_id: left
    name: ' '
    unit: mm
    stroke_width: 2
    type: column
    color: '#1448ab'
    show:
      in_header: false
      legend_value: false
    data_generator: |
      return entity.attributes.forecast.map((entry) => {
        return [new Date(entry.datetime).getTime(), entry.precipitation];
      });
  - entity: sensor.nordpool
    name: ' '
    color: '#1d1d1d'
    stroke_width: 10
    type: column
    time_delta: +1h
    yaxis_id: elpris
    group_by:
      duration: 1h
    show:
      in_header: false
      legend_value: false
      header_color_threshold: true
      extremas: true
    float_precision: 1
    unit: c/kWh
    data_generator: >
      const data = []; for(let i = 0; i <= entity.attributes.raw_today.length-1;
      i++) {
        if (new Date(entity.attributes.raw_today[i]["start"]).getTime()>=(new Date).getTime()) {
          data.push([new Date(entity.attributes.raw_today[i]["start"]).getTime(), entity.attributes.raw_today[i]["value"]*100])
        }
      } if (entity.attributes.tomorrow_valid) for(let i = 0; i <=
      entity.attributes.raw_tomorrow.length-1; i++) {
          data.push([new Date(entity.attributes.raw_tomorrow[i]["start"]).getTime(), entity.attributes.raw_tomorrow[i]["value"]*100])
      } return data;
    opacity: 1
    color_threshold:
      - value: -100
        color: blue
      - value: -100
        color: blue
      - value: 5.88372
        color: green
      - value: 8.38372
        color: lightgreen
      - value: 10.88372
        color: yellow
      - value: 13.38372
        color: orange
      - value: 15.88372
        color: orangered
      - value: 18.38372
        color: red
      - value: 20.88372
        color: darkred
  - entity: sensor.ring_i_torvmossvagen_regn_idag
    yaxis_id: left
    name: Regn idag
    color: '#3498db'
    show:
      in_header: true
      legend_value: false
      in_chart: false
  - entity: sensor.ring_i_torvmossvagen_temp
    yaxis_id: right
    color: '#e74c3c'
    name: Ute temp
    show:
      in_header: true
      legend_value: false
      in_chart: false

It looks like updating to HACS v2 now prevents you from reverting to 2.0.4, so I'm stuck with grey bars until this is fixed. Or revert HACS as well I guess.

It looks like updating to HACS v2 now prevents you from reverting to 2.0.4, so I'm stuck with grey bars until this is fixed. Or revert HACS as well I guess.

In HACS, click on the apex charts card project, then the three dots menu and choose redownload, from there you can choose a version (although it says it's not recommended I don't know what that means)

the three dots menu

Ah I'd stopped using that method and switched to the service call (not action) some time ago when that message started displaying. The service call fails, but this method works, thanks.

Any update on this issue? Still using the v2.0.4 version in stead of v2.1.2 because of this. Last release has been a while. Did not see a solution yet. Issue is just flagged stale, how to remove this stale label?

I have found the culprit in my configuration: removing the     stroke_width: from my chart did solve my threshold issue.
Hope it helps


[map] zoom in on map

-added ability to zoom and pan. To zoom in and out, can use buttons or mouse wheel
dev updated (http://dev.datacommons.org/tools/map#%26sv%3DCumulativeCount_MedicalConditionIncident_COVID_19_PatientDeceased%26pc%3D1)

very very cool!
i think the changes aren't on dev anymore, but looking at the video - would be nice if hover is disabled during the zoom transitions.

Thanks! I will try to disable hover during zoom transitions in a separate pr


All the time get error with restart of HA [Bug]

The problem
@Vaskivskyi every time I restart HA I get the following error message in my logs
This error originated from a custom integration.
Logger: homeassistant
Source: custom_components/asusrouter/config_flow.py:548
Integration: AsusRouter (documentation, issues)
First occurred: 10:07:36 (1 occurrences)
Last logged: 10:07:36
Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/discovery_flow.py", line 71, in async_start
await gather_with_concurrency(
File "/usr/src/homeassistant/homeassistant/util/async.py", line 201, in gather_with_concurrency
return await gather(
File "/usr/src/homeassistant/homeassistant/util/async_.py", line 199, in sem_task
return await task
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 798, in async_init
flow, result = await task
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 826, in _async_init
result = await self._async_handle_step(flow, flow.init_step, data)
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 335, in _async_handle_step
result: FlowResult = await getattr(flow, method)(user_input)
File "/config/custom_components/asusrouter/config_flow.py", line 548, in async_step_ssdp
discovery_info.upnp[ssdp.ATTR_UPNP_MODEL_DESCRIPTION]
KeyError: 'modelDescription'
Your device model
ASUS XT-12
Firmware type
Stock
Firmware version
<IP_ADDRESS>.388_22127
Integration version with the issue
since 0.21.0 now am on 0.21.1
Method of the integration installation
HACS
What version and type of Home Assistant installation do you use
2023.2.5
Is there anything useful in the logs?
This error originated from a custom integration.

Logger: homeassistant
Source: custom_components/asusrouter/config_flow.py:548
Integration: AsusRouter (documentation, issues)
First occurred: 10:07:36 (1 occurrences)
Last logged: 10:07:36

Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/discovery_flow.py", line 71, in _async_start
    await gather_with_concurrency(
  File "/usr/src/homeassistant/homeassistant/util/async_.py", line 201, in gather_with_concurrency
    return await gather(
  File "/usr/src/homeassistant/homeassistant/util/async_.py", line 199, in sem_task
    return await task
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 798, in async_init
    flow, result = await task
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 826, in _async_init
    result = await self._async_handle_step(flow, flow.init_step, data)
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 335, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
  File "/config/custom_components/asusrouter/config_flow.py", line 548, in async_step_ssdp
    discovery_info.upnp[ssdp.ATTR_UPNP_MODEL_DESCRIPTION]
KeyError: 'modelDescription'

Diagnostics information
Can not attach from mobile phone
Additional information
None

Hello, @smarthomefamilyverrips,
Sorry to hear, you are experiencing issues with AsusRouter
From the log error I see, that your device is not reporting the model name in the network discovery (which was added in 0.21.0)
The fix will be available as soon as possible. I will let you know

@Vaskivskyi, OK happy you see the problem, will await for your fix, Thanks! 👍🏻

Hey. The issue will be fixed in the next AsusRouter update

@Vaskivskyi Great thanks! 👍🏻

Hello. The issue should be fixed in 0.22.0, which is already available via HACS

@Vaskivskyi did fix it for me! 👍🏻


Look, if you really want to hack a io game that bad just make it yourself. Stop complaing about lack of udpates or many issues for something you get free.
Some of the people here spent hours infront of a computer screen to code all of this and trust me it wasn't easy
You should be thankful that these people took the time to do those hacks and released it free.
Also you can just get good like seriously it isn't that hard
Making complaining threads about something that is obvious also doesn't help. If you think you're the first person who made a thread about "freezing pls fix" change your mind.
 Life doesn't work that way
And finally if you REALLY wanted to get rid of that freezing issue you COULD consider LEARNING how to script YOURSELF to HELP out
Also just imagine...if you worked hundred of hours to make a game that you hoped people would like and then some of those people decided to abuse the system of your game.
I̶ ̶g̶u̶e̶s̶s̶ ̶m̶y̶ ̶t̶h̶r̶e̶a̶d̶ ̶w̶a̶s̶ ̶p̶o̶i̶n̶t̶l̶e̶s̶s̶ ̶t̶o̶o̶ ̶a̶n̶d̶ ̶t̶h̶a̶t̶ ̶i̶t̶'̶s̶ ̶g̶o̶i̶n̶g̶ ̶t̶o̶ ̶b̶e̶ ̶c̶l̶o̶s̶e̶d̶.̶

Truth

I'm assuming the last part was the "truth" :laughing:

I just WON with no HACK, it isn't that HARD

It really isn't. I play without hacks. But sometimes people just want to make it easier.

are you his lawyer or bodyguard ? no ? f*** off then.
for the creators:
thank you for all your hard work. i think you should make this private and start charging for it, i will be your first customer.

@DreamC***oz And what would be your price hmm ?
I'm just pointing out the obvious things going on here like the whole drama about the freezing going on and edgy kids crying cuz they can't use hack.

I mean I use a cheat that cost $1 for surviv. It's pretty good and doesn't crash. Even blissin is in the discord for it.   Hacks could boost that 7 kills to 22 easily.  He has 200 subs

I mean I use a cheat that cost $1 for surviv. It's pretty good and doesn't crash. Even blissin is in the discord for it. If you want I can send you the link to it

can you send me a link ? thx

I mean I use a cheat that cost $1 for surviv. It's pretty good and doesn't crash. Even blissin is in the discord for it.  Hacks could boost that 7 kills to 22 easily. Want a link?

Hacks and cheats are itself illegal which mean you aren't really well placed to talk.

I mean I use a cheat that cost $1 for surviv. It's pretty good and doesn't crash. Even blissin is in the discord for it. If you want I can send you the link to it

No thanks I don't participate much in hacking activities paying would be a waste.

lmao @TheSatanicAngeI you suck btw, saiga and 7 kills and IHASYOU name

Yea sure I suck, what you think I'd take my time to get the best game I could out of sheer luck and skills ? Just for you guys ? Nah you aren't worth it.  I use random names that are popular by now. It's easier than trying to came up with a new name that I won't really use anyways.

 He has 200 subs

Assuming things is commonly known as an insult for lower IQ beings like you.   It is literally meaningless. Also it may looks like this to a lower-intelligent being like you but I'm not actually taking his defense. Sure I favorise his situation but it's my own selfish situation that I want to change. I mean maybe I shouldn't have let notifications on after all. Every time someone made a thread I was just looking it up to see if anything new was brought up and I end up with all the times people complaining about things not working rather than helping or trying to change things. It is frustrating.
Last words
I am very happy to see that I am capable of offending so many people with my meaningless existence, thank you guys so much to for caring, it really means a lot to me.

 Meaningless existence Keep you meaningless existence to yourself then goddamn

I am very happy to see that I am capable of offending so many people with my meaningless existence, thank you guys so much to for caring, it really means a lot to me. Meaningless existence Keep your meaningless existence to yourself then goddamn

Yeah what he said

I am very happy to see that I am capable of offending so many people with my meaningless existence, thank you guys so much to for caring, it really means a lot to me.
Congratulation! I can now see that you're all teaming as fake friends to have some kind of superiority that you can't get alone.


Begin refactoring of Stats to store all results

This is the initial implementation of #5 which will ensure better consistency and accuracy inside the statistics gathering - it also has the knock-on effect of improving the accuracy of the hook system notifications in general.
This PR introduces the new for option with stat: Cachex.stats(:my_cache, for: :get). This allows the retrieval of extremely raw values on an action level. The default is to still provide what we do now.
Naturally there's a bigger memory overhead to this because we're storing more data, and the retrieval will take a little bit longer if you're grabbing the current implementation (because it's calculated on-demand). I think these are perfectly fine and expected.

Coverage increased (+0.4%) to 100.0% when pulling 6c69239e9dcd14c4d1011d39e2745c8976a97da7 on issue-5 into 545daf389938a70ace6cd2f5f066445752c8aac8 on master.

Coverage increased (+0.4%) to 100.0% when pulling 3fa15c0dda2bbc1c22eb94623ca2c49963779858 on issue-5 into 545daf389938a70ace6cd2f5f066445752c8aac8 on master.

Coverage increased (+0.4%) to 100.0% when pulling 95d9167bf8ee332fa98dadd36ee177d94c91c204 on issue-5 into 545daf389938a70ace6cd2f5f066445752c8aac8 on master.

Coverage increased (+0.4%) to 100.0% when pulling 30e09b27994a0fd5a76d4e142eb8d74fc23ffe89 on issue-5 into 545daf389938a70ace6cd2f5f066445752c8aac8 on master.

Coverage increased (+0.2%) to 99.794% when pulling 6605318d892c08cd1c5bfb62bea1f950d09f909a on issue-5 into 545daf389938a70ace6cd2f5f066445752c8aac8 on master.

Coverage increased (+0.4%) to 100.0% when pulling f369d165d1c17d4de872c1389d3ee8df9a70c2a3 on issue-5 into 545daf389938a70ace6cd2f5f066445752c8aac8 on master.

Ok, this is good to go. Some additional improvements will be filed separately to avoid too big a divergence.
Closes #2 and #5.


Enhanced documentation

Fixed the typos and added content for a better understanding. Kindly review the changes.

Fixed the spelling mistakes for 'scrape' and it's various forms
Enhanced the introduction by elaborating on it

Also removed an extra '.git' extension in the clone command.

I have made the necessary changes in the readme file, sir. Are there any more changes required?

Sir, I can't merge it, as I don't have the write access.


[MBL-1575] Add estimated shipping costs for rewards and add-ons

📲 What
A description of the change.
🤔 Why
Some background context on why the change is needed.
🛠 How
More in-depth discussion of the change or implementation.
👀 See
Trello, screenshots, external resources?

Before 🐛
After 🦋

📋 QA
Instructions for anyone to be able to QA this work.
Story 📖
[Name of Trello Story](Trello link)

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
Attention: Patch coverage is 23.52941% with 52 lines in your changes missing coverage. Please review.

Project coverage is 67.50%. Comparing base (d32fa71) to head (e3eb3ff).

Files
Patch %
Lines

...java/com/kickstarter/libs/utils/RewardViewUtils.kt
0.00%
21 Missing :warning:

.../activities/compose/projectpage/AddOnsContainer.kt
0.00%
15 Missing :warning:

...arter/services/transformers/GraphQLTransformers.kt
0.00%
5 Missing :warning:

...c/main/java/com/kickstarter/models/ShippingRule.kt
75.00%
4 Missing :warning:

.../ui/activities/compose/projectpage/AddOnsScreen.kt
0.00%
4 Missing :warning:

...vities/compose/projectpage/RewardCarouselScreen.kt
0.00%
3 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@                         Coverage Diff                         @@
##             feature/pledge-redemption-ml1    #2090      +/-   ##
===================================================================
- Coverage                            67.57%   67.50%   -0.07%
  Complexity                            2130     2130
===================================================================
  Files                                  365      365
  Lines                                22205    22242      +37
  Branches                              3132     3140       +8
===================================================================
+ Hits                                 15005    15015      +10
- Misses                                5543     5570      +27
  Partials                              1657     1657

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Explore idea of having native in-app shopping for Particle hardware

https://help.shopify.com/api/sdks/mobile-buy-sdk/android

Belongs in the app repo


Running on Linux with Mono

Might be in over my head here, but has anyone used this library on a linux box with Mono?
I was able to get the sample project to compile and run on Linux, but it would error out trying to find the device by the PID and VID. I'm assuming the WinUSB driver is what is missing on my Linux machine, any idea if there's a way around that?

Never thought anyone would actually try to run this on Linux, because Linux is one of the first platforms that supported iBeacons with the Bluez stack. If there really is a need to run this on Linux, I think we need to add an additional transport which uses RAW BT sockets on Linux instead of WinUSB.

I probably have an odd use case...I'm deploying code to a fleet of Raspberry Pis and my main machine is running Windows 7. Was hoping to sync up my development environment with what would be running on each Pi. This would also have the added benefit of developing in Visual Studio.


fix: Missing button text for PostScript

This fixes #6900 by avoiding any Postscript file in the list of built URL for a document,

Note: I was unable to fully test it as my docker environment does not have the full archived drafts, but add empty draft-ietf-tsvwg-quickstart-07.ps/txt/pdf locally and it works (i.e., txt/pdf buttons are displayed and nothing for ps)