further cleanup of make_bcs utility and CatchmentCN routines

An inconsistency in NLv5 Catchment model parameters was discovered that impacts 6 tiles (out of ~1.6 million) on the EASEv2 M09 grid.   The 6 tiles in question end up with some PEATCLSM parameters (incl. porosity=0.93), even though they (probably) should have mineral soil properties (which is still reflected in some parameters associated with the 0-30 cm soil layer).  An investigation is ongoing.
During this investigation, a few minor problems with the make_bcs script were discovered and fixed in the branch associated with this PR.  More fixes might be needed.
The PR will be zero-diff for all model runs.  It is not yet clear how the inconsistency in the Catchment model parameters will be resolved.  We will probably need to introduce a new bcs version to fix the parameter inconsistency, which probably means that will the PR will also be zero-diff for the make_bcs package.
cc: @rdkoster @gmao-jkolassa @biljanaorescanin @weiyuan-jiang @gmao-qliu

UPDATE (5/5/22):
The subroutines dealing with HWSD/PEATMAP processing and the Woesten soil parameters were partially cleaned up and some documentation was added.  The changes are not meant to be final.  The latest commit ef69e84 successfully tested 0-diff for the generation of NLv4 and NLv5 bcs in EASEv2_M09 resolution.  Additional tests for other bcs versions and resolutions will be needed.
It remains unclear how the tiles identified by Sebastian end up with peat as profile soil class.  The attached pdf and xls files provide additional information.
SMAP_L4_Meeting_20220504_NLv5_bcs_only.pdf
soilparam_peat_tiles_rr_20220504.xlsx
cc: @rdkoster @gmao-jkolassa @biljanaorescanin @weiyuan-jiang @gmao-qliu

UPDATE (23 May 2022):
Additional cleanup was merged from the following supporting PRs:
remove generation of obsolete bcs file CLM4.5_veg_typs_fracs #586
cleanup of incomplete CatchCN albedo scaling #589
#589 touches the CatchmentCN GridComp and requires 0-diff verification of the GEOSldas CatchmentCN tests.
Also, make_bcs requires testing to see if the branch successfully reproduces the existing sets of bcs (keeping in mind that the obsolete bcs file CLM4.5_veg_typs_fracs is no longer generated and a couple of IDL plots were renamed).
Since the (standard) Catchment model was not touched, the PR is trivially 0-diff for all GCM tests and most GEOSldas tests (except those involving CatchmentCN as noted above).
In its current form, this PR does not address the inconsistent soil parameters identified by Sebastian.  This is left for future work, provided someone can figure out the logic of subroutine soil_para_hwsd() and how we end up with the inconsistent parameters.
@biljanaorescanin, please test this PR as outlined above and report the results here.  If the tests pass, remove the "contingent" label and convert from "draft" to "ready for review" to indicate that the PR is ready to be merged into develop.
cc: @rdkoster @gmao-jkolassa @weiyuan-jiang @gmao-qliu @sdrabenh

All Nightly tests passed.
I've run one bcs test (EASE M09), files are same as from run when using develop branch with exception to file we removed (file was obsolete), some wording changes in README file and out log file and some plots that visualized information in removed file were removed as well.

I've run one bcs test (EASE M09)

Thanks, @biljanaorescanin.  Which bcs version did you run?  Given the extent of the changes in this PR, we need to run multiple versions at multiple resolutions.  At the very least, we need to run NLv4 and NLv5 on M09 and M36, and we need to run NLv3 at c720, c360, c180 and c90.

@gmao-rreichle I did NLv3. Sure, I will run other cases and add a comment once I am done.

@gmao-rreichle @weiyuan-jiang I've added last commit so we don't have warning messages in catchcn_params.nc4 and catch_param.nc4 . I am testing it now to confirm.

I added the "contingent" label again.  Not sure why this was removed.  We are not quite done with this PR.  Hopefully final touches and testing underway now.

The previous two commits fix a netcdf dimension error that had been present for a long time in the catch_params.nc4 and catchcn_params.nc4 files generated by make_bcs.  The data in the files was successfully verified 0-diff after the commits.
Owing to the bug in the old version of these nc4 files, nccmp and cdo do not work properly for comparing the catch_params.nc4 files before and after the dimensions bug fix.  I verified 0-diff for data across the old and new nc4 files using matlab.
@biljanaorescanin successfully completed final developer tests today (GEOSldas runs that use bcs generated with the branch associated with this PR).

PR is ready for final verification and merging by GCM gatekeeper.
PR only touches make_bcs and CatchmentCN and is trivially 0-diff for all GCM tests.
Suggested log entry:
make_bcs and CatchmentCN cleanup:
- removed generation of unused/obsolete bcs file CLM4.5_veg_typs_fracs
- cleanup of incomplete CatchCN albedo scaling
- partial cleanup and improved documentation of subroutines dealing with HWSD/PEATMAP processing and Woesten soil parameters

We may have to examine why it checks table 2 of pix2 but use table 1 of pix1

Thanks, @weiyuan-jiang, for the sleuthing.  I've never looked at this program and cannot quickly make sense of what's going on here.  I'm still unclear what happens when we run the (usual) build with optimization, and what a fix would look like.  If we also get Pix1=-999 with the optimized build, then lines 344-347 should result in garbage, which is concerning.  @atrayano, are you familiar with the code in question?  [In brief, when we run this code for make_bcs using a debug build, the run stops with an error message that an index value is negative.  No such stop and error message is produced when we run the (usual) optimized build.  See previous comment by @weiyuan-jiang.]
cc: @biljanaorescanin @rdkoster

@gmao-rreichle Yes, I am familiar with this code , it was written by Max Suarez many years ago. I have seen the negative (-999) Pix error once in a while, and usually this is a result of the rasterization process not covering completely the Earth

The good news is I only saw one bad pix. Maybe we can throw away that one ? @gmao-rreichle @biljanaorescanin @atrayano

@weiyuan-jiang Unfortunately, we cannot throw away the "bad" Pix. My first impulse is to write a piece of code to check the raster(s) for -999 and possibly do something to re-assign a "good" value (for example, assign the value from a neighbor)

@sdrabenh I made an issue for things we didn't address  https://github.com/GEOS-ESM/GEOSgcm_GridComp/issues/596, we are ready to proceed with this PR as it is.


Unable to import in 2.4.15

Since the last update for GSE retail I am unable to import any macros. No error just does nothing when you click the import button

Is this just one class of all classes?
TimothyLuke

On 1 Sep 2019, at 9:22 am, Elfyau<EMAIL_ADDRESS>wrote:
Since the last update for GSE retail I am unable to import any macros. No error just does nothing when you click the import button
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

All classes all macro's some other people are having a similar issue as well

I just did a clean install on a Mac with just GSE and imported https://wowlazymacros.com/t/decent-starter-bm-macro/8410 on a low level hunter without issue.
Need more information on what is occurring.
TimothyLuke

On 1 Sep 2019, at 12:32 pm, Elfyau<EMAIL_ADDRESS>wrote:
All classes all macro's some other people are having a similar issue as well
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Hey - can you go into the mods options and turn on the mods debug mode (as opposed to the sequence debug mode) and select storage as the module.  There will be some display and capture options - these also need to be turned on.  There will be a ton of stuff sent to your chat log.  Can you send me the lot or screenshot the last lot of messages?
TimothyLuke

On 1 Sep 2019, at 12:32 pm, Elfyau<EMAIL_ADDRESS>wrote:
All classes all macro's some other people are having a similar issue as well
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

https://imgur.com/a/xStQH81
From Cloudy
TimothyLuke

On 1 Sep 2019, at 1:57 pm, Timothy Minahan<EMAIL_ADDRESS>wrote:
Hey - can you go into the mods options and turn on the mods debug mode (as opposed to the sequence debug mode) and select storage as the module.  There will be some display and capture options - these also need to be turned on.  There will be a ton of stuff sent to your chat log.  Can you send me the lot or screenshot the last lot of messages?
TimothyLuke

On 1 Sep 2019, at 12:32 pm, Elfyau<EMAIL_ADDRESS>wrote:
All classes all macro's some other people are having a similar issue as well
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

so now i use the released version 2.4.15 without -gxxxxxxx https://imgur.com/a/NM5rVC8
still the same and also i turn on the debug mode this is what it say after i import the code on my chat
the code that i using is for resto shaman
https://wowlazymacros.com/t/elfyaus-8-2-resto-shammy-dps-heals-macro-update-18-aug-19/7921
Transmission:  Data Finalised
Transmission:  Decomsuccess: true
Transmission:  tablerows: 2 type cell1 string cell2 table
Storage:  sequenceIndex: SAM_ELEMENTAL
Storage:  No Macro Found, Possibly different spec for Sequence SAM_ELEMENTAL
Storage:  sequenceIndex: SAM_ENHANCEMENT
Storage:  No Macro Found, Possibly different spec for Sequence SAM_ENHANCEMENT

Cheers - what are you trying to import?
Can you copy the import string please
TimothyLuke

On 1 Sep 2019, at 2:25 pm, CloudySummer<EMAIL_ADDRESS>wrote:
so now i use the released version 2.4.15 without -gxxxxxxx https://imgur.com/a/NM5rVC8
still the same and also i turn on the debug mode this is what it say after i import the code on my chat
the code that i using is for resto shaman
https://wowlazymacros.com/t/elfyaus-8-2-resto-shammy-dps-heals-macro-update-18-aug-19/7921
Transmission: Data Finalised
Transmission: Decomsuccess: true
Transmission: tablerows: 2 type cell1 string cell2 table
Storage: sequenceIndex: SAM_ELEMENTAL
Storage: No Macro Found, Possibly different spec for Sequence SAM_ELEMENTAL
Storage: sequenceIndex: SAM_ENHANCEMENT
Storage: No Macro Found, Possibly different spec for Sequence SAM_ENHANCEMENT
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

actually i try to use every rshaman import string and all of them doesnt work
this is the one that i trying to use
Elfyau’s 8.2 Resto Shammy DPS/Heals Macro UPDATE(18/Aug/19)
d0dmgaWsOiVLeVwjYYKuZev5WuMTe3LKUPsv)ssUnv15bYovP9ISBI9R4Naf6Vaf8BiduPYqvcdwQHdWbHcDAqhdqhhOulek1sPkzXkjTCQ8qLu9uv9yuEoPMiuWuvktgvY0fDrLexfvQEgQQ6DafTrLu2kQkTzQITRe1hHIAwqjFgQ(oQugjQkwhqfJwftJQuNeOQUoQ4Aav6Eav5YcBdvv(eqjtaPn6cKEVw53aJGbmShZ0TM2OFVXCi(gonejAAJUaPn6cK(kMPZPvee7yIefOGRo9AfZpM(pi2s0TM(kMPZPvee7yIefOGRonpBzBAS540jD5p9vmtNtR4J4cC0hONeRPfe7yIefOGRo96hdktZdIFsbk4G508G4NuGc(0yJkjD9M(kMPZPvee7yIefOGRonpBzBAS540jDbx6RyMoNwzhGIbkCQkcIDmrIcuWvN2liGeYvqx(rFfZ0PoaBoHWIPv2bOyGcNQIGyhtKOafC1PDHosWJH8x1YPNM7sjm9zAEqpbwtZNWkqbF6pDH5p9gkdF65Hqa4b9Hj9aPFbsN7nMdrB0fi9vmtNtRii2XejkqbxDAmQtNvM(pqpjDRPVIz6CAfbXoMirbk4yXq(RAP60paOdMCZklfoWspnMDglOKEmfGw4cTM2Olq6RsZHhziHpOPve0XC(QuspMcqEfLW0bTrj9lCXEJ5q0gDbsFfZ050k7aumqHtD6pcUMg5z6vqI5OBn9vmtNtRSdqXafoSMwqSJjsuGcU60RBamgmrUP3qz4tj9FgawJJWsisOFHdICWeeL0TM2Olq6RyMoNwrqSJjsuGcU60Rvm)y6)Gylr3A6RyMoNwrqSJjsuGcU608SLTPXMJtN0L)0xXmDoTIpIlWrFGEsSMwqSJjsuGcU60RFmOmnpi(jfOGdMtZdIFsbk4tJnQK01B6RyMoNwrqSJjsuGcU608SLTPXMJtN0fCPVIz6CALDEqmoAvfbXoMirbk4Qt7feqc5kOl)OVIz6uhGnNqyX0k7aumqHtvrqSJjsuGcU60Uqhj4Xq(RA50tZDPeM(mnpONaRP5tyfOGp9NUW8NEdLHp98qia8G(WKEG0VaPZ9gZHOn6cK(kMPZPvee7yIefOGRong1PZkt)hONKU10xXmDoTIGyhtKOafCSyi)vTuD6ha0btUzLLchyPNgZoJfuspMcqlCHwtB0fi9vP5WJmKWh00kc6yoFvkP)ZaWACewcrc9lCqKdMGOFHl2BmhI2Olq6RyMoNwzNheJJwD6pcUMg5z6vqI5OBn9vmtNtRSdqXafoSMwqSJjsuGcU60RBamgmrUP3qz4tj9yka5vucth0gLusj9BwjKutp)bwxxdSM(vepihlwh5dWsBvybMGiSPhJCYdYrp3lgxrM7wZH0PpIJtc63dkpqgDRPFpO8azlkC00TMEm)RW3WPHiH(AVb6n97nHJvaFjd3YHKqKqytpg4i4bsOBn9EzqUOBn9yi8yCkjDbs)diyGpgOBn)8ME(eoeKr3A6XOleJU10Vb9dUzLLGcoDRPFbFxq3AkPKia

actually everycode that was made for rshaman bfa all of them doesnt work idk if this happen on other class as well

I was also having this problem I was trying to import this - https://wowlazymacros.com/t/elfyaus-8-2-one-button-marksman/7791 on the release version and my fresh install of WoW.
I just reverted to 2.4.14 and it worked 1st time.
Not sure if that helps you.

oh yeah it works using 2.4.14 version

I just tried this and was able to import RESTO_DMG and REST_HEAL without issue.
I'm using the latest alphas: 2.4.15-5-g08e8531 and 2.4.15-6-gb7daa08
Going to push this version as 2.4.16 to fix a latent bug with #580 and #582

@Elfyau @CloudySummer @JustPete93 Was this fixed with the last release?

I will check it after work today.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Timothy Minahan<EMAIL_ADDRESS>Sent: Tuesday, September 3, 2019 12:52:47 AM
To: TimothyLuke/GnomeSequencer-Enhanced<EMAIL_ADDRESS>Cc: Pete<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [TimothyLuke/GnomeSequencer-Enhanced] Unable to import in 2.4.15 (#584)
@Elfyauhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FElfyau&data=02|01||ecd1413c7d1441e68c6d08d72ff847bb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637030615706125033&sdata=wj%2BaQDzij1UZYOm4vdQ3UJxeEj05R0B4926ic%2BIgw5A%3D&reserved=0 @CloudySummerhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FCloudySummer&data=02|01||ecd1413c7d1441e68c6d08d72ff847bb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637030615706135044&sdata=jeCCUet3aETfDJvtIZAUK%2Bb8asKWn3f%2BURB0FIpa2Vc%3D&reserved=0 @JustPete93https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJustPete93&data=02|01||ecd1413c7d1441e68c6d08d72ff847bb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637030615706145043&sdata=kqDiqSA8MUO4og90C6mXSqEUB46mBj%2B9nX5bJZqIhEM%3D&reserved=0 Was this fixed with the last release?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTimothyLuke%2FGnomeSequencer-Enhanced%2Fissues%2F584%3Femail_source%3Dnotifications%26email_token%3DADJORAL7CKWSDWS72XDNVG3QHWKL7A5CNFSM4ISVDCE2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5WUFEA%23issuecomment-527254160&data=02|01||ecd1413c7d1441e68c6d08d72ff847bb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637030615706155054&sdata=slWtAq1I0AMWyyPRJQWBkjP1OUh14Z3xYp49FHlem1k%3D&reserved=0, or mute the threadhttps://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FADJORAPPMORF7YZITZHZ3N3QHWKL7ANCNFSM4ISVDCEQ&data=02|01||ecd1413c7d1441e68c6d08d72ff847bb|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637030615706165060&sdata=U2iGiscJ7%2FmF039MKHnYqzGR8FHmQ%2BPgNvHXL6Su8YI%3D&reserved=0.

Closing this out as fixed.  I havent had any reports for 2.4.16 or 2.4.17 of this occuring.


[Icon] - Some icons are not found within the font files.

Steps to Reproduce
Create a "address card icon".
Expected
Should show the icon font, as it uses the correct "content-code".
Result
The included font does not support this content code.
Temporary fix: downloading font-awesome instead of using the included font file from semantic

Hi @Leaninsider, the icon in question seems to be working fine:
https://github.com/Semantic-Org/Semantic-UI/blob/796d2f66e26ae5bb76c604fe6a36914ad3d2fe2a/src/themes/default/elements/icon.overrides#L110
Here’s a test case: https://jsfiddle.net/fjjhpckb/


Panic while transcribing audio.wav

thread 'main' panicked at 'slice index starts at 172409 but ends at 168511',
/tmp/whisper-burn/src/transcribe.rs:101:22

https://github.com/Gadersd/whisper-burn/blob/3757c15fd18fe2ec2c398cb6a4697e108442ff3a/src/transcribe.rs#L95
Here waveform.len() could be less than n_samples_per_tensor, which results in iter_len to be extremely large:
[src/transcribe.rs:97] n_samples_per_tensor = 238559
[src/transcribe.rs:97] waveform.len() = 168511
[src/transcribe.rs:97] waveform.len() - n_samples_per_tensor =<PHONE_NUMBER>3709481568

Replacing subtraction with saturating_sub fixes the issue.

Nice catch! I just pushed your correction.


Q: Links to PDF pages

Hi!
First of all, thanks for an -incredible- plugin! It's truly changed my workflow with Zotero!
One issue (or question) with templating: I have tried editing the default single annotation template to include a link to the page in the PDF document (reading the property on 'it'), but I can't seem to get it right.
Any chance I could get it to work? This feature is super important to me, as I have quite long PDF's and annotations, so I usually need to see some more context when copying from them.
Thank you again!

Hi!
First of all, thanks for an -incredible- plugin! It's truly changed my workflow with Zotero!
One issue (or question) with templating: I have tried editing the default single annotation template to include a link to the page in the PDF document (reading the property on 'it'), but I can't seem to get it right.

In zt-annots.eta add
[<%= annot.pageLabel %>](<%= annot.backlink %>)

this opens the Zotero PDF reader at the given page.


Chip 0455 Animation Request

Chip ID
0455
Sample

Additional information
Add any other information here.

Animation has been pushed.


fix: correct lint

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Smart Attachments event conflict

Smart Attachments 2.5.3 captures the keyboard event for "c" while labels are being edited. No current known workaround.

Only other plugin can fix this.


vak train requires regularization and crashes like #99

In the attached .toml file the setting is:
normalize_spectrograms = true
If I run vak train with the 'false' setting it crushes.
vak train should be able to run without normalization.
When set to  normalize_spectrograms = true
vak train crashes like #99 with the following message:
File "C:\Anaconda3\envs\tweetyenv_alpha\Scripts\vak-script.py", line 11, in
load_entry_point('vak', 'console_scripts', 'vak')()
File "c:\users\yarden cohen\repos\vak\src\vak_main_.py", line 43, in main
config_file=args.configfile)
File "c:\users\yarden cohen\repos\vak\src\vak\cli\cli.py", line 21, in cli
train(toml_path=config_file)
File "c:\users\yarden cohen\repos\vak\src\vak\cli\train.py", line 115, in train
transform = transforms.Compose(
File "c:\users\yarden cohen\repos\vak\src\vak\datasets\window_dataset.py", line 255, in from_csv
target_transform
File "c:\users\yarden cohen\repos\vak\src\vak\datasets\window_dataset.py", line 98, in init
one_x, _ = self.getitem(tmp_x_ind)
File "c:\users\yarden cohen\repos\vak\src\vak\datasets\window_dataset.py", line 147, in getitem
window, labelvec = self.__get_window_labelvec(idx)
File "c:\users\yarden cohen\repos\vak\src\vak\datasets\window_dataset.py", line 132, in __get_window_labelvec
lbls_int = [self.labelmap[lbl] for lbl in annot.seq.labels]
AttributeError: 'list' object has no attribute 'seq'
config-llb3-04232019.zip

Maybe the standardization can be solved by setting the transform to an identity in line 86 in train.py:
e.g.
standardize = lambda *args: args

Oops, closed automagically because I mentioned in a pull request


The Percent Response graph on UI shows unusual

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ *] Question or discussion
[ ] Bug
[ ] Requirement
[ ] Feature or performance improvement

Question

What do you want to know?
I'm not sure it's a bug or  data not right,what situation show the p95 and p99 smaller than the p90

Bug

Which version of SkyWalking, OS and JRE?
Skywalking version :6.3

Which company or project?

What happen?
If possible, provide a way for reproducing the error. e.g. demo application, component version.

Requirement or improvement

Please describe about your requirements or improve
ment suggestions.

Can’t see your image.


Update Array.adoc

Seems like Array size is missing from docs even though it works in code?
so I've been testing with the following code if (Array.filter(adjList, func (rv : VertexNode) { rv.name != v.name }).size() > 0)
and it seems to be working. Not sure I got that function definition right but it will be great if you can add the correct version.
Thanks,
Gabriel

Hi Gabriel, and thanks for your contribution!
Confusingly, size is not a function in the Array module, but it’s a “virtual member” of each array type (e.g. of [Bool]). You can tell since you can write a.size() and not Array.size(a).
Therefore, it should be documented in the language guide. Oddlly, I don't find it listed in the table “Special member access” https://sdk.dfinity.org/docs/language-guide/language-manual.html#exp-dot – @crusso, is that intentional?
Other places where it maybe should be mentioned could be https://sdk.dfinity.org/docs/language-guide/mutable-state.html#immutable-arrays. And maybe the Array documentation should also point to these place, or mention the special members, so I’ll leave this open for my colleages to chime in as well.

Ok great, thanks for the info.
It seems Array.size(a) does not exist yet as I'm getting field size does not exist in type   module {append : <A>([A], [A]) -> [A]; chain : <A, B>([A], A -> [B]) ->  am I missing something?
It would be great if we had that. Thanks again.

That’s what I mean: size is not a member of the Array module, but you can simply write xs.size() whenever xs : [t]; no need to import a libray for that.

That’s what I mean: size is not a member of the Array module, but you can simply write xs.size() whenever xs : [t]; no need to import a libray for that.

Oh I see what you meant. Got it now, thank you very much for the swift reply .

Come on!

Is it possible to document the "virtual members" of each type? Spent too much time trying to find out how to get the length of an array

Is it possible to document the "virtual members" of each type? Spent too much time trying to find out how to get the length of an array

It always takes me a while to find it, but you can find this in
https://sdk.dfinity.org/docs/language-guide/language-manual.html#exp-dot

Therefore, it should be documented in the language guide. Oddlly, I don't find it listed in the table “Special member access” https://sdk.dfinity.org/docs/language-guide/language-manual.html#exp-dot – @crusso, is that intentional?

That was an oversight, thanks for fixing it @nomeata. (It may take a while for the fix to reach the public web site.)

Fixed in the Language Manual. Thanks!


Revert "Make snippets/dependencyManagement/customizingResolution-attributeSubstitutionRule..."

So the fix can be used as a demo during the hackathon kick-off.
This reverts commit a68732516493941d2f30ecd4e64af44a9cb5b575.

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle help

Currently, the following commands are supported:
@bot-gradle test <BuildTrigger1> <BuildTrigger2> ... <BuildTriggerN>

A trigger is a special build for this PR on TeamCity, common triggers are:

SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/PullRequestFeedback/ReadyForNightly/ReadyForRelease
Shortcuts: SC/CA/QFL/QF/PRF/RFN/RFR
Specific builds:

BD: BuildDistributions/BuildDocs so that you can preview the generated docs/distribution.
PT: PerformanceTest, all performance tests for Ready For Nightly stage.
APT: AllPerformanceTest, all performance tests, including slow performance tests.
AST: AllSmokeTestsPullRequestFeedback
AFT: AllFunctionalTestsPullRequestFeedback
ASB: AllSpecificBuildsPullRequestFeedback
ACC: AllConfigCacheTestsPullRequestFeedback
ACT: AllCrossVersionTestsReadyForNightly
AFTN: AllFunctionalTestsReadyForNightly
ACTR: AllCrossVersionTestsReadyForRelease
AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle test and merge

queues this PR for testing and merges if all tests pass by:

Creating a merge commit from your PR branch HEAD and the target branch
Running a ReadyForNightly build against the merge commit
When it passes, fast-forward the target branch to this merge commit (i.e. merge the PR)

The merge commit is called a pre-tested commit, which means that it fully tests the integration
of your branch HEAD and latest master, instead of only testing your branch HEAD.
@bot-gradle cancel

cancel a running pre-tested commit build or remove it from queue

@bot-gradle clean

clear the conversation history

@bot-gradle help

display this message

To run a command, simply submit a comment.  For detailed instructions see here.

@bot-gradle clean

@bot-gradle test this

@bot-gradle test and merge

No milestone for this PR. Please set a milestone and retry.

Hm, looks like it hadn't landed before the kickoff. Does it make sense to land it now, @bamboo?

No, it doesn't. We should just make sure we keep the solutions consistent.


[HUDI-6119] Add testcase for timeline timezone UTC

Change Logs
Create instant time after setCommitTimezone if table exists, or after initTable if no table exists.
Impact
When hoodie.table.timeline.timezone is UTC in not UTC LOCAL timezone, timeline action does not progress.
Risk level (write none, low medium or high below)
none
Documentation Update
[HUDI-6119] Add testcase for timeline timezone UTC
@yihua following comment, added testcase
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@nicholas-fwang The PR seem causing the Java CI to fail continously, can you check the test failures and fire a fix again?

@danny0405 okay I will check it


Added Ultimate ChatGPT.

Ultimate ChatGPT is an advanced conversational chatbot powered by OpenAI's gpt-3.5-turbo & gpt-4, offering exceptional language understanding and generation capabilities for a wide range of conversational applications.

@imabutahersiddik I apologize for the inconvenience. The README is automatically generated by the program, and I am only able to manually add the URL you provided. As a result, I will not be able to merge this PR. Thank you for your understanding.


Twin Example for Drone

📝 Description of the feature
Many request are coming to us for Drone Digital Twin
💡 Steps for implementing the feature
No example
🔗 Useful links and references
Create n example, I can help on this

hi @nitinbanait , thanks for opening this issue. Would you be able to describe the exact need in more details with a possible illustration of the example you have in mind ? Is there anything new on the pytwin library that would need to be considered for that particular example ?
If that's a possibility for you, you might want to go ahead and start working on a new branch with the implementation you have in mind. We could certainly assist and review the work as it progresses.

Simple Drone Drop Test using PyAnsys, a good example to start with.


Custom notification with a component with dependencies doesn't work

Overview of the problem
Oruga version: [0.4.X]
Vuejs version: [2.X.X]
OS/Browser: All
Description
If you instantiate a component that customizes notifications, it doesn't load all dependencies (ie $i18n)
Steps to reproduce

Customize a notification with a component that has dependencies
Fire notification programmatically

Expected behavior
Custom notification doesn't throw errors
Actual behavior
Custom notification throws errors (can't find dependencies)

It works, only missing parent: this in the example


File upload could not be processed.

I am suddenly getting "file upload could not be processed" for ANY pdf file I try to upload, even those that worked fine before.  This happened after I attempted to upgrade, but now happens both with the old and the new versions.  I have tried to reinstall, to no avail.  It is also possible that there has been a Java upgrade since the last time I used tabula (not sure on the exact timing).
I have attached the portion of the log I suspect is relevant.  The error happens after the file is selected, it shows "waiting to be processed," and then it raises a series of exceptions.

WF economic-forecast.pdf

Any clues would be appreciated.

As another clue, github will not upload the pdf file, either, so attaching it to the issue report did not work.

i am also facing same problem.
Windows 10.
tabula: 1.1.1

I am still facing this problem, after multiple attempts at reinstalling.  Any hints?

@gunnarblix looks like Tabula's workspace file got corrupted. Try finding the Tabula folder in Window's APPDATA directory and delete it. It usually is at C:\Users\<your_username>\Appdata.

That was it - thank you!!
For reference, the directory was C:\Users<username>\AppData\Roaming\Tabula.
I suspect it got corrupted when I upgraded the last time.  (Lesson: never upgrade :-)


FeatureRequest: PowerToys Run - font-family, font-size, resizing and transparency ability.

📝 PowerToys Run - font-family, font-size, resizing and transparency ability.
The size of the run tab seems quite small, it would be quite awesome if there could be configuration over the UI of this search-bar.

If you'd like to see this feature implemented, add a 👍 reaction to this post.

Duplicate of https://github.com/microsoft/PowerToys/issues/4794

Duplicate of https://github.com/microsoft/PowerToys/issues/4794


export control

In doing some header cleanup I'm realizing that we do nothing to control the export of symbols from either of our libraries. Thus every globally visible symbol is exported and we're exposing a pile of utility functions that aren't part of the TSS2 API. The "right thing to do" here is to specifically limit the symbols we expose using the various methods available through the compiler and linker. There may be portability issues so we'll have to do some homework here.
https://www.akkadia.org/drepper/dsohowto.pdf

Made a pile of progress on this. The 'simulator' global variable has been factored out of the socket TCTI. The global debug print function pointer has been factored out of the device TCTI as well. The only (I think) remaining undefined reference in one of our libraries is the printf function pointer in the socket TCTI.

The device TCTI is ready to have a map file applied. The socket TCTI still has unresolved symbols caused by global data but that's being tracked in #126. The SAPI library hasn't yet been looked at and I imagine that will be the most difficult as it exports a large number of symbols. Likely this issue should be broken out into distinct issues for tracking.

#184 resolves this and is out for review


Watch for updates

Hello everyone, nice project you created here!
Is it planned to provide a watcher-like functionality? For my package dwm-status I build a watcher based on dbus events, maybe you are interested in adding a similar API method.

Hey, @Gerschtli!
There are no plans to make anything like this right now, as there is no such a notification mechanism for all platforms currently supported (note that Linux implementation is using sysfs instead of uevent+dbus).
It is possible to make this "watcher" in a polling manner and just re-read all data each n time, but it looks like a easy task to implement by yourself (Manager::refresh could help with that).

Ah okay, the polling way is not an acceptable way for my project because of its ineffeciency and inaccuracy. But thank you for your quick response!


feat(drawer): add new types to the Drawer

TOP-1329
Description
We have to have all existing in Base UI version of Drawer: 'narrow', 'regular', 'medium', 'wide', 'ultra-wide'
⚠ BREAKING CHANGE ⚠: Now, regular type is a narrow, wide -> regular
Screenshots

Review

[ ] Read CONTRIBUTING.md and Component API principles
[ ] Annotate all props in component with documentation
[ ] Create examples for component
[ ] Ensure that deployed demo has expected results and good examples
[ ] Ensure that tests pass by running yarn test
[ ] Ensure that visuals tests pass by running yarn test:visual. If not - check the documentation how to fix visual tests
[ ] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.

PR commands

List of available commands:

@toptal-bot run all - Run whole pipeline
@toptal-bot run build - Check build
@toptal-bot run visual - Run visual tests
@toptal-bot run deploy:documentation - Deploy documentation
@toptal-bot run package:alpha-release - Release alpha version

@toptal-bot run visual


Bug: Cursor does not always flash

When the text cursor is enabled, if it is positioned on-screen above an area that is not using either the current foreground or background colour then it will not be visible, and will not flash
this is because the current cursor uses canvas->swapRectangle to be drawn, which swaps the current "pen" and "brush" coloured pixels in a given area, equating to the currently selected FG and BG colours
Now that the graphics system supports EOR operations drawing a rectangle using the EOR paint mode may be a better option

as of VDP 2.7.0, cursor is now plotted using XOR, thus fixing this issue


Forward auth token for logger APIs from controller to other controllers and brokers

When auth is enabled, the controller logger API cannot directly access controller/broker/minion logger APIs.
Fixed this by forwarding the auth token in request header.

Codecov Report

Merging #10590 (28d69a4) into master (fe7a72b) will decrease coverage by 55.06%.
The diff coverage is 0.00%.

@@              Coverage Diff              @@
##             master   #10590       +/-   ##
=============================================
- Coverage     68.96%   13.90%   -55.06%
+ Complexity     6495      439     -6056
=============================================
  Files          2106     2052       -54
  Lines        112992   110510     -2482
  Branches      17019    16724      -295
=============================================
- Hits          77921    15364    -62557
- Misses        29590    93891    +64301
+ Partials       5481     1255     -4226

Flag
Coverage Δ

integration2
?

unittests1
?

unittests2
13.90% <0.00%> (+0.02%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...ontroller/api/resources/PinotControllerLogger.java
0.00% <0.00%> (ø)

... and 1633 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


CEO-393 Fix the positioning of Project Stats (Dec testing bug fix)

Purpose
Moves the Project Stats section underneath the new location of the info icon.
Related Issues
Closes CEO-393
Submission Checklist

[x] Included Jira issue in the PR title (e.g. CEO-### <title>)
[x] Code passes linter rules (npm run eslint/clj-kondo --lint src)

Screenshots

I dont think you need left and margin.  does left: 1rem not do the same?


Archive page subtitles be surrounded by  mistakenly

I used the latest release version to generate my blog, and use year-archive.html in your repo's gh-pages branch to generate my /archive page.
It is supposed that the subtitle of year, such as 2016 should be like the appearance in your website archive by year, but when I jekyll s it locally, it is surrounded by  tag mistakenly. And the only thing I did is rename the year-archive.html to year-archive.md, I am wondering if there is some modifications in the latest release version that influence the generation of this page. I also tried tag-archive.html and category-archive.html in _pages folder, but it runs normally without the  tag surrounded.
Picture shows below.

Best.

What's going on is when you changed the page from .html to.md it's telling Jekyll to process the page as Markdown.
Since there is an indent in the code around the subtitle it's being converted into a  block. If you remove the indents it should process correctly.
{% include base_path %}
{% capture written_year %}'None'{% endcapture %}
{% for post in site.posts %}
{% capture year %}{{ post.date | date: '%Y' }}{% endcapture %}
{% if year != written_year %}

{{ year }}

{% capture written_year %}{{ year }}{% endcapture %}
{% endif %}
{% include archive-single.html %}
{% endfor %}


generator: use rundir as apply start marker

Fixes https://github.com/coreos/torcx/issues/50

/cc @squeed


Use R code fences, closes #10

@kfl

Eh. I'm not sure how this closes my PR #10. Is it because you prefer the
````

syntax over the
~~~

syntax? (I thought that bike-shedding was discouraged :wink:) I personally prefer the later, but it is not big deal to me.

I misred the e-mail from GitHub.


problem with movement of ur robot with urscript

Hi, I published URScript command movep[(q,)] using /ur_driver/URScript topic by senting a string message. I can see the publisher publising the msg and urscript subscribed to it. But I am unable to move the robot . Please suggest me what would be the problem.

Since this may is related to the communication between ROS and UR, can you post information about your versions?
I run into a similar problem with kinetic and UR 3.5.2 on my UR5 (see: https://github.com/Zagitta/ur_modern_driver/issues/18). It was fixed by adding a terminal symbol to the string. I suggest you try the fork of @Zagitta found here:  https://github.com/Zagitta/ur_modern_driver
For debugging purposes you can use a script to test, if the errors is in the ROS-interface.
bypass_ur_script.txt
I also recommend to first test with a Virtual Machine from UR found here: https://www.universal-robots.com/download/?option=37648#section16597

I have only tested this with @Zagitta's fork anyway, so I don't know if there's an issue in this repository that prevents this from working. And +1 to @SteveGrehl 's suggestions of adding extra info/context.

I am using ROS Kinetic with UR Controller version 3.5.1. I used the code talker directly to publish command on /urscript topic without using socket communication. I am able to move robot arm but same as expected and there is delay in the program.I will try your method using socket programming.

I am using ROS Kinetic with UR Controller version 3.5.1. I used the code talker directly to publish command on /urscript topic without using socket communication. I am able to move robot arm but same as expected and there is delay in the program.I will try your method using socket programming.

I am able to move robot arm
well, that's good 👍

[..] but same as expected
I don't understand what you mean.

I mean I am directly publishing movep() command on /URScript topic and giving displacement along y-direction. I checked the motion before sending the command the robot y displacement towards front direction but robot displaces downwards. And when run the command rosrun the robot doesnt move . Robot stands still and when I click on keyboard interrupt ctrl+c it moves. And for code the attached by @SteveGrehl uses a subscriber while there exists two subscribers and no publisher. I tried defining publisher but still I am unable move the robot arm according to @SteveGrehl code.

Kindly please find the attached text code.
talker.txt
nvidia@tegra-ubuntu:~/catkin_ws$ rostopic list
/attached_collision_object
/clicked_point
/collision_object
/execute_trajectory/cancel
/execute_trajectory/feedback
/execute_trajectory/goal
/execute_trajectory/result
/execute_trajectory/status
/follow_joint_trajectory/cancel
/follow_joint_trajectory/feedback
/follow_joint_trajectory/goal
/follow_joint_trajectory/result
/follow_joint_trajectory/status
/initialpose
/joint_states
/joint_temperature
/move_base_simple/goal
/move_group/cancel
/move_group/display_contacts
/move_group/display_planned_path
/move_group/feedback
/move_group/goal
/move_group/monitored_planning_scene
/move_group/ompl/parameter_descriptions
/move_group/ompl/parameter_updates
/move_group/plan_execution/parameter_descriptions
/move_group/plan_execution/parameter_updates
/move_group/planning_scene_monitor/parameter_descriptions
/move_group/planning_scene_monitor/parameter_updates
/move_group/result
/move_group/sense_for_plan/parameter_descriptions
/move_group/sense_for_plan/parameter_updates
/move_group/status
/move_group/trajectory_execution/parameter_descriptions
/move_group/trajectory_execution/parameter_updates
/pickup/cancel
/pickup/feedback
/pickup/goal
/pickup/result
/pickup/status
/place/cancel
/place/feedback
/place/goal
/place/result
/place/status
/planning_scene
/planning_scene_world
/recognized_object_array
/rosout
/rosout_agg
/rviz_moveit_motion_planning_display/robot_interaction_interactive_marker_topic/feedback
/rviz_moveit_motion_planning_display/robot_interaction_interactive_marker_topic/update
/rviz_moveit_motion_planning_display/robot_interaction_interactive_marker_topic/update_full
/rviz_tegra_ubuntu_25076_3945433862842214962/motionplanning_planning_scene_monitor/parameter_descriptions
/rviz_tegra_ubuntu_25076_3945433862842214962/motionplanning_planning_scene_monitor/parameter_updates
/tf
/tf_static
/tool_velocity
/trajectory_execution_event
/ur_driver/URScript
/ur_driver/io_states
/ur_driver/robot_status
/wrench
I meant the robot should be in motion immediately I publish commands and stop when I press keyboard interrupt. But the robot executes after some time after rosrun is executed and contiunes even when I press keyboard interrupt ctrl+C. Sometimes code start executing  even after I press ctrl+C.  As seen in the code I am displacing arm only y-direction with respect to the first point but the robot moves in other direction

I executed a program using movep() on teach pendent I dont get error and it executes properly while program the same code using /URScript by publishing commands it keeping showing circle radius is too small or invalid joints . Can I know what is the problem and How can I proceed further?

Is this still an issue for your @lakshmip001 ?
The URScript topic can be a bit difficult, and I'm not sure using it for motions is the best thing to do.
One thing I can suggest is to wrap all statements in a program (so def myProg: ... end) instead of sending single lines. That tends to work better.

I'm going to close this issue, but if it's still a problem then please feel free to re-open @lakshmip001.


Updated file size limits

In March, the max size of uploaded files was increased from 100GB to 250GB.
https://www.microsoft.com/en-us/microsoft-365/roadmap?filters=&searchterms=70558

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 905e2c09-ef3e-07cc-0809-6ff171157c47
Version Independent ID: c0d33162-183d-fff8-32e9-a999f391ea51
Content: Limits and specifications for Microsoft Teams - Microsoft Teams
Content Source: Teams/limits-specifications-teams.md
Service: msteams
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

@khilker15 Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

@scanum this can be closed thank you.


segment Leaderboards kom_type element always returns "kom"

Caling a Segment Leaderboard, the kom_type seems to be always "kom", at least for me, also in running segments.
Example:
Segment 17261611 is a running segment.
Calling strava.segments.listLeaderboard({ "access_token": accessToken, id: id, "page": 1, "context_entries": 1, "per_page": 1} results in:
{"effort_count":12, "entry_count":12, "kom_type":"kom", "entries":[{"athlete_name":"Maarten H.", "elapsed_time":164, "moving_time":164, "start_date":"2011-04-23T06:02:42Z", "start_date_local":"2011-04-23T08:02:42Z", "rank":1}, {"athlete_name":"Felix K.", "elapsed_time":194, "moving_time":146, "start_date":"2018-03-30T15:44:32Z", "start_date_local":"2018-03-30T17:44:32Z", "rank":2}, {"athlete_name":"Dirk K.", "elapsed_time":205, "moving_time":157, "start_date":"2019-07-19T19:10:55Z", "start_date_local":"2019-07-19T21:10:55Z", "rank":3}, {"athlete_name":"Michael U.", "elapsed_time":208, "moving_time":208, "start_date":"2019-03-07T19:14:40Z", "start_date_local":"2019-03-07T20:14:40Z", "rank":4}, {"athlete_name":"Stefan E.", "elapsed_time":244, "moving_time":244, "start_date":"2019-02-07T07:04:46Z", "start_date_local":"2019-02-07T08:04:46Z", "rank":5}]}

Patch welcome.
On Fri, Jul 19, 2019 at 6:52 PM Dirk<EMAIL_ADDRESS>wrote:

Caling a Segment Leaderboard, the kom_type seems to be always "kom", at
least for me, also in running segments.
Example:
Segment 17261611 is a running segment.
Calling strava.segments.listLeaderboard({ "access_token": accessToken,
id: id, "page": 1, "context_entries": 1, "per_page": 1} results in:
{"effort_count":12, "entry_count":12, "kom_type":"kom",
"entries":[{"athlete_name":"Maarten H.", "elapsed_time":164,
"moving_time":164, "start_date":"2011-04-23T06:02:42Z",
"start_date_local":"2011-04-23T08:02:42Z", "rank":1},
{"athlete_name":"Felix K.", "elapsed_time":194, "moving_time":146,
"start_date":"2018-03-30T15:44:32Z",
"start_date_local":"2018-03-30T17:44:32Z", "rank":2}, {"athlete_name":"Dirk
K.", "elapsed_time":205, "moving_time":157,
"start_date":"2019-07-19T19:10:55Z",
"start_date_local":"2019-07-19T21:10:55Z", "rank":3},
{"athlete_name":"Michael U.", "elapsed_time":208, "moving_time":208,
"start_date":"2019-03-07T19:14:40Z",
"start_date_local":"2019-03-07T20:14:40Z", "rank":4},
{"athlete_name":"Stefan E.", "elapsed_time":244, "moving_time":244,
"start_date":"2019-02-07T07:04:46Z",
"start_date_local":"2019-02-07T08:04:46Z", "rank":5}]}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/UnbounDev/node-strava-v3/issues/76?email_source=notifications&email_token=AAAGJZNRWUM2ZG7OJZAUM3LQAJASBA5CNFSM4IFMZ3NKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HAMYPUQ,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAGJZIRNK6JMHKZOVLSZXTQAJASBANCNFSM4IFMZ3NA
.

--
Mark Stosberg
Director of Systems and Security
RideAmigos

Can you confirm that the mistake is in this repository and not in the original Strava API?
Because I can't find any routine here dedicating a kom type to a segment leaderboard.

I don't have time, but you are welcome to make direct REST Calls to the Strava API and compare those results to calling the APIs through this module.

After checking on the swagger platform I can confirm that this is an issue created by the API. It can't be resolved by this module, but for my application I was able to solve it another way. I'll close this for now.


Unable to get any stock price data - JSONDecodeError: Expecting value: line 1 column 1 (char 0)

import yfinance as yf
apple = yf.Ticker("AMZN")
hist = apple.history(period="max", start="2021-05-20", end="2021-06-04")

It was working fine, but now just gives the JSON Decode Error.

Looks like I am getting the same error.
Seems like a server may be down? Not really sure.
This is the line I am running:
return yf.download(tickers = ticker, period = "5d", group_by = 'ticker', threads = False)
This is the error I am getting:
simplejson.errors.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

Solution:
pip3 install yfinance --upgrade --no-cache-dir
or use pip if you are not using pip3

It worked for me in PyCharm, but is still not working in my Conda environment even after running those pip commands.

Yup same issue!

Thank you also for building this scraper. It is awesome.

pip3 install yfinance --upgrade --no-cache-dir solved it for me too!

yeah, just works for me by simply upgrading it.

I'm having the same issue and upgrading the package did not appear to fix it.

The upgrade did it for me. Thanks!


Develop

Prepare for a simpler repository setup.
Going forward, we'll be developing on master, i.e., PRs no longer target develop but master directly. The master branch is protected and can only be modified through PRs.
I am going to activate release-drafter for the master branch such that we automatically collect the changes for the next release.
Furthermore, a Github Action is going to build the platform-specific bundles of the launcher and attach them to any new release automatically.

Previously, the master branch was only updated infrequently, whenever we did a release. At these points we would reset the master branch to point to the latest version of develop (git merge --ff-only).
Thus, master is essentially the same as develop, except being outdated in-between.
As we are not doing any release management for the launcher in the sense of supporting and patching old versions, having rolling releases directly from master should simplify the overall process.
New releases are simply marked by git tags.

Hooray Jenkins reported success with all tests good!


Add TSlint + Prettier linter

What problem does this feature solve?
TSlint works well with Prettier thanks to tslint-config-prettier. It would be great to have such a feature in Vue CLI.
What does the proposed API look like?
TSlint   Prettier selection on the linter selection step.

Let's close this issue, I have a better idea described here: https://github.com/vuejs/vue-cli/issues/2462


Be able to read version 4 replays

Version 4 replays are no longer readable bc they have less features.
We need to add a way to convert the old array size to the new array size.

Automatically checks for version and adapts if v4. The boolean bOnGround isnt precisely though, the bSupersonic is


Fix #1051, use OSAL time conversion/access methods

Describe the contribution
Instead of accessing OS_time_t values directly, use the OSAL-provided conversion and access methods.  This provides
independence/abstraction from the specific `OS_time_t definition and allows OSAL to transition to a 64 bit value.
Fixes #1051
Testing performed
Build and run unit tests, sanity check CFE
Expected behavior changes
None (but see notes)
System(s) tested on
Ubuntu 20.04 (native)
RTEMS 4.11 + pc686 (qemu)
Additional context
By using the OSAL implementation of subsecond/microsecond conversion, this will correct some minor inaccuracies in the CFE TIME conversions that were never noticed before.
Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.

CCB 2021-01-06 APPROVED

Fixes broken Micro2SubSec and SubSec2Micro functions that were returning innacurate values
Removes the need for some test cases because OSAL now performs those

Needs https://github.com/nasa/osal/pull/723

CCB 2021-01-06 APPROVED

Fixes broken Micro2SubSec and SubSec2Micro functions that were returning innacurate values
Removes the need for some test cases because OSAL now performs those

Needs https://github.com/nasa/osal/pull/723


[License] Add a NOTICE file to apply the LICENSE to our work

Description
Hypercrx is taking part in 2022年中国开源创新大赛 and the competition requires a LICENSE and a NOTICE. So I have (re)learned something about Licenses.
According to the APPENDIX of the Apache License 2.0, a explicit NOTICE file is great(for Apache projects it is a MUST, for others optional) to apply the license to the work.
And I also read How to apply the Apache 2.0 License to your Open Source software project and visited apache/echarts then got a conclusion that we can also have a NOTICE file in the root directory.
I suppose a possible NOTICE file looks like this:
Copyright 2020-2023, Frank Zhao and the Hypercrx contributors
SPDX-License-Identifier: Apache-2.0

Hi @frank-zsy, do you have any knowledge on this?

/self-assign


[WIP]增加双向认证支持

Codecov Report

Merging #24 (b3578dd) into master (924160e) will decrease coverage by 0.74%.
The diff coverage is 26.66%.

:exclamation: Current head b3578dd differs from pull request most recent head 0f3629c. Consider uploading reports for the commit 0f3629c to get more accurate results

@@             Coverage Diff              @@
##             master      #24      +/-   ##
============================================
- Coverage     76.35%   75.61%   -0.74%
+ Complexity      310      309       -1
============================================
  Files            39       39
  Lines          1607     1620      +13
  Branches        113      118       +5
============================================
- Hits           1227     1225       -2
- Misses          334      344      +10
- Partials         46       51       +5

Flag
Coverage Δ

java
75.61% <26.66%> (-0.74%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...aliyun/gmsse/protocol/ClientConnectionContext.java
73.36% <21.42%> (-6.21%)
:arrow_down:

src/main/java/com/aliyun/gmsse/ClientAuthType.java
100.00% <100.00%> (ø)


MAINT: fix lobpcg performance regression

Closes https://github.com/scipy/scipy/issues/4506
On the other hand, I think lobpcg is broken (https://github.com/scipy/scipy/issues/4174).
before:
               lobpcg benchmark sakurai et al.
==============================================================
      shape      | blocksize |    operation   |   time
                                              | (seconds)
--------------------------------------------------------------
        (50, 50) |     3     |     lobpcg     |   0.99
        (50, 50) |     3     |       eigh     |   0.01
      (400, 400) |     3     |     lobpcg     |   9.98
      (400, 400) |     3     |       eigh     |   0.10
    (2400, 2400) |     3     |     lobpcg     |  18.56
    (2400, 2400) |     3     |       eigh     |  14.83

after:
                 lobpcg benchmark sakurai et al.
==============================================================
      shape      | blocksize |    operation   |   time
                                              | (seconds)
--------------------------------------------------------------
        (50, 50) |     3     |     lobpcg     |   0.42
        (50, 50) |     3     |       eigh     |   0.01
      (400, 400) |     3     |     lobpcg     |   3.04
      (400, 400) |     3     |       eigh     |   0.09
    (2400, 2400) |     3     |     lobpcg     |   9.52
    (2400, 2400) |     3     |       eigh     |  14.45

Thanks


Heavy Adornment Memory Optimizations

Theres some memory consumption problem with the Explorer, that happens when multiple objects are being created and destroyed during each frame. This has been a problem for several months now, but it has become more notable with this plugin, due to the CoreGui suddenly becoming visible in the Explorer.
I updated parts of the Adornment module to utilize a smart object pooling system, so that objects don't have to get cleared and regenerated during each frame. As a side effect, this actually makes the tool faster than it was before, and it can handle large parts without the framerate panicking too much.

Bump.

Sorry, been super busy. I'll try to take a look at this today.


Support for hvyor talk comments

Hvyor Talk is a privacy-focused, fully-featured commenting platform for blogs and news sites. I am using it on my personal blog, so I thought to open a PR if other people might be interested in using it.

Looks good, thank you!

I tested it a bit, their styles require unsafe-inline in the CSP, I opened a report about it: https://community.talk.hyvor.com/submissions/64dec56e8b15fc2614ac224b
Additionally, when I enabled Hyvor for abridge I was getting a bit of (Flash of inAccurate coloR Theme)[https://css-tricks.com/flash-of-inaccurate-color-theme-fart/]
I tried changing the scripts from async to defer, but it did not help. The flash of inaccurate color may have been caused by the shadow dom that hyvor uses for styling, but i am honestly not sure, but once I disabled hyvor by default the flash of inaccurate color was gone.
The easiest way to reproduce this issue is by clicking into articles then using the browser back button. My default is a dark theme, and when I would hit the back button I was often getting a very small flash of white background, its very fast, and some people may not even notice, but it was there. Additionally it seemed to only be an issue in Firefox, Chrome did not display the issue...
For now I disabled hyvor in the demo because I want it working perfectly in both firefox and chrome.

Sure. I personally use Firefox as well.
I am using hyvor because I do not want to use Disqus, and commento has not been updated since 2021 (at least the GitHub version). I also do not want to host comments myself since I am not a devops or backend person.
I did not notice those issues because, well, comments are pretty much an afterthought right now and only experimental on my blog. I might end up removing them if they don't serve much purpose.
Anyway, thanks for all your work. I love this theme.

@Ayush1325 If you are looking for an alternative maybe check out Cactus Comments which is matrix based and can work even if you don’t host your own matrix homeserver.
https://cactus.chat/


Qwen2Tokenizer does not work with SFTDataset

Need to add a __call__ method.

@RdoubleA this can be closed yes?

Completed by #1347


Added options to enable media player for activity groups

Added 2 options (enabled by default) to have :
1/ One global media player entity (as today)
2/ One media player entities per activity group

Hi, I don't understand your comment :
currently you have one media player for ALL activities, right ? I added an option (enabled by default) to enable or disable this
I added another option to enable one media player for each activity group
So if you enable option 1 : you will have one media player for sure (for all activities) like today
If you enable option 2 : you will have one media player for each activity group
If you enable both : you will have 1 + n media players where n = number of activity groups

Not quite following, but it sounds like we agree. Just include those files back in a commit so they are available for easier development while relevant.

Hi again Jack,
I have just committed another proposition to handle :
1/ The source selection for a media player entity (for media streamers like Apple TV or Android TV it will be the app like netflix..., for a TV it will be HDMI1, 2..., for a STB it will be the TV channel and so on) => this is important to keep it here I think as this is a must have to handle those commands when you don't have the remote next to you
2/ The media entity selection that you put in the source list : first I removed duplicates, also I moved it and enable the sound mode selection as the list of media entity selection
3/ In the media entity list : when user select an entity, you cannot unselect it to move to automatic selection, so I added an automatic selection entry in the drop down to get batck to automatic mode
4/ Not sure about that : I removed the condition you apply on the user media entity selected when it is off or not playing. There some situations where it is not playing but active, or where it is off and you want to put it back on (when something wrong happened)
As an idea, because sound mode is not ideal to select media player entities : building a sub menu in the source list where you would have :

Media player entity -> selection causes to create a new source list built from entities list
 source 1
source 2
...


Fix issue that does not save selection data when configuration changed.

Fix issue that does not save selection data when configuration changed.

Resolved: https://github.com/Park-SM/ParkDateTimePicker/pull/15


Timeout of a requested domain or tcp port

Hi. If I create a port 80 forwarded subdomain or tcp address and then stop the session. After few seconds if If I create the tunnel using the same port or subdomain, then will I'll be assigned the same port or subdomain or something else?

You should be assigned the same domain but this all depends on how timeouts are handled. The readme outlines specifics on ping client interval and idle timings.


Adding sshTest to verify a cluster comes back up active after rebooting node

Issue:

645
Problem

We currently do not have an automated test where we reboot a node and check to see if the cluster comes back up Active. We should do the following to rectify that:

Create a 1 node, all roles RKE1 cluster, reboot the cluster and validate that the cluster and nodes are Active
Create a 1 node, all roles RKE2 cluster, reboot the cluster and validate that the cluster and nodes are Active
Create a 1 node, all roles K3s cluster, reboot the cluster and validate that the cluster and nodes are Active

Solution

Adding an ssh test to the automation framework to reboot a node and verify the cluster comes up active.
Testing

Engineering Testing
Manual Testing

Manual steps taken:

Provision a 1 node all role rke1/rke2/k3s cluster
ssh into the node
run sudo reboot
Verify cluster goes into Updating state and the node status is in reconciling
Verify the node reboots successfully
Verify the cluster comes back up active

Automated Testing

Test types added/modified:

Unit
Integration (Go Framework)
Integration (v2prov Framework)
Validation (Go Framework)
Other - Explain: EXPLAIN
None
REMOVE NOT APPLICABLE BULLET POINTS ABOVE

If "None" - Reason: EXPLAIN THE REASON

If "None" - GH Issue/PR: LINK TO GH ISSUE/PR TO ADD TESTS
Jenkins test available upon request

QA Testing Considerations

This automation is in order to cover more testcases for QA
Regressions Considerations

There aren't any regressions as the reboot command is already a built-in function of linux and we are just verifying the status changes of the node and cluster.
Existing / newly added automated tests that provide evidence there are no regressions:
Jenkins test available upon request

@thaneunsoo I have also left comments on https://github.com/rancher/rancher/pull/42706 which has merged, can you address the feedback in this PR?


Unable to Deploy or Retrieve on Debian all of a sudden

Summary
This might be related to the fact that after successfully authorizing the org, the cli has started to create .sfdx/ and .sf/ directories in my home directory (~/) I don't think it was like that before. Now it gives me the error org not found or can not decipher.
Steps To Reproduce:

Authorize an org in Debian
Try to retrieve after authorizing
Get the error that org can not be found.

Expected result
Should have been able to successfully retrieve it
Actual result
Got errors org can not be found instead
System Information

Which shell/terminal are you using? VSCode terminal

If you are using sfdx

{
  "cliVersion": "sfdx-cli/7.188.1",
  "architecture": "linux-x64",
  "nodeVersion": "node-v16.15.1",
  "pluginVersions": [
    "@oclif/plugin-autocomplete 1.4.5 (core)",
    "@oclif/plugin-commands 2.2.7 (core)",
    "@oclif/plugin-help 5.2.4 (core)",
    "@oclif/plugin-not-found 2.3.18 (core)",
    "@oclif/plugin-plugins 2.3.0 (core)",
    "@oclif/plugin-search 0.0.13 (core)",
    "@oclif/plugin-update 3.1.3 (core)",
    "@oclif/plugin-version 1.2.1 (core)",
    "@oclif/plugin-warn-if-update-available 2.0.26 (core)",
    "@oclif/plugin-which 2.2.14 (core)",
    "@salesforce/lwc-dev-server 2.11.0 (user)",
    "alias 2.2.1 (core)",
    "apex 1.5.1 (core)",
    "auth 2.4.2 (core)",
    "community 2.2.1 (core)",
    "config 1.5.1 (core)",
    "custom-metadata 2.1.1 (core)",
    "data 2.2.1 (core)",
    "generator 2.0.17 (core)",
    "info 2.4.2 (core)",
    "limits 2.3.3 (core)",
    "org 2.3.2 (core)",
    "packaging 1.14.3 (core)",
    "schema 2.3.1 (core)",
    "signups 1.4.0 (core)",
    "source 2.5.1 (core)",
    "telemetry 2.1.1 (core)",
    "templates 55.4.1 (core)",
    "trust 2.4.1 (core)",
    "user 2.3.2 (core)",
    "@salesforce/sfdx-plugin-lwc-test 1.0.1 (core)",
    "salesforce-alm 54.8.5 (core)"
  ],
  "osVersion": "Linux 5.10.0-15-amd64",
  "shell": "bash",
  "rootPath": "/home/amana/.npm_packages/lib/node_modules/sfdx-cli"
}

I don't know what I did exactly, but I do remember installing the normal sfdx-cli (without npm) using the standard procedure with the install script, and updating it, and it worked after that I guess.

This issue flickers, sometimes it arises and sometimes it doesn't...

Hey @prateekamana have you been seeing this happening with the new sf v2 CLI?


Fix issue #358

Coverage remained the same at 100.0% when pulling d72090f8d20eb0c12fd4377a3cb3801f4c68b4ee on issue_358 into a6a24091d7fb3d70a581130e301a7297d6aea068 on master.


[CAMEL-8349] Context should be started with defined TCCL

https://issues.apache.org/jira/browse/CAMEL-8349

needs more work


dnsmonster: init at 0.9.3

Description of changes
Passive DNS Capture and Monitoring Toolkit
https://github.com/mosajjal/dnsmonster
Related to #81418

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 178068 run on x86_64-linux 1

1 package built:

dnsmonster

Can you mark it broken for darwin? I am not sure why the test fails.


如何更新KEY？

chatgpt-dingtalk-bot version:
Python version:
Operating System:

Description
Describe what you were trying to get done.
Tell us what happened, what went wrong, and what you expected to happen.
What I Did
Paste the command(s) you ran and the output.
If there was a crash, please include the traceback here.

是 openai 的 api_key么？ 可以通过环境变量来设置

0.6.0已经支持了


Adding assertions for AddChange test scenario for ResultV2 Test

The updated test accounts for much needed assertions for AddChange scenario in Result V2 test:
This code snippet initializes an expectedFileChanges variable, which is a map containing expected changes. Each file is associated with a set of object changes represented by the ObjectChanges type. Within each file's changes, specific objects are associated with an array of Change structs, where each struct represents a change in values. The g.Expect(result.FileChanges) statement asserts that the FileChanges field of the result variable matches the expected changes defined.

Hi @souleb hope you are doing well, I made the necessary changes recommended here: https://github.com/fluxcd/image-automation-controller/pull/682#issuecomment-2122409405

@souleb hey can you take a look at these changes  please


allDayAccessor is not enough to stop rendering events in all day section

Hi,
In the TimeGrid component, when determining if an event is an all day event, even though my allDayAccessor returns always false since I don't want to display events in that section, there is another condition that includes the events as all day events that can't be controlled via props:
(dates.isJustDate(eStart) && dates.isJustDate(eEnd))
Could this be modified in order to get the result of the allDayAccessor function passed to the component?
https://github.com/intljusticemission/react-big-calendar/blob/6c517dd41ca2ac0266d2b3a3d5f56affb356975d/src/TimeGrid.js#L167
Thanks.

There are a few past issues that cover why this is and how you can handle it, please see them thanka


Laravel v10 support

🧰 Changes
This PR adds support for Laravel 10.
I ran the tests before upgrading, when PayloadTest::testCreate() failed because of timezone difference. I updated the regex to cover timestamps with and without "Z", and optional defined timezone, to make sure all tests pass.
Examples:

2022-08-17T17:12:13
2022-08-17T17:12:13Z
2023-02-17T09:47:14+01:00

Please check if that is the right approach. If not, then the underlying function needs to be updated to only report UTC timestamps.
After upgrading the Laravel version to 10 I ran the tests again and all still passed.
🧬 QA & Testing
Run the tests before and after the version switch. Make sure Laravel was upgraded when running composer update.

ping @kanadgupta @erunion

Hey! Thanks so much for this, I'm gunna run through this tomorrow and if all looks good i'll get a new release out for you. Thanks for your patience.

Thanks for this. This repo is actually a mirror of https://github.com/readmeio/metrics-sdks and I've got a similar PR for this over at https://github.com/readmeio/metrics-sdks/pull/743 so I'm going to close this out.
I'm working today on getting that PR of mine working and out the door so there'll be a release supporting Laravel 10 in the next couple days.

I've just released v11 which adds support for Laravel 10 and PHP 8.2. I've also dropped support for Laravel 8 in this one as it was EOL'd last month.


Tracing wrong step

recursiveAsyncDone should pass 'trace' instead of 'nextStep' to buildTarget. If passed a target, it's the same trace step and not a different one.

fixed in v0.2.0


Windows ?

https://github.com/tigrisdata/tigris/blob/main/scripts/install_build_deps.sh seems to not support windows.
is that because foundation db just does not run on windows ?

You are right, install_build_deps.sh needs to be fixed to support Windows.
But most of the development flows don't require FoundationDB clients on the host.
So if you disable platform check in the script and install the rest of the tools, you
would be able to run:

make test which would execute the tests in the docker container.
make generate to generate the code, so all symbols are resolved in the IDE.
make run to bring up a Tigris instance on localhost:8081, so you can issue manual requests.

I did simple manual tests on Windows in the past, but it could be broken since then.
We would greatly appreciate the contributions.


feat: Enhancing About Section

Title and Issue number

Title: Enhancing About Section
Issue No. : #1084
Code Stack : CSS
Close #1084

Description

Made Changes to the ABOUT section of the website so as to make it more attractive.
Video/Screenshots (mandatory)

Type of PR

[ ] Bug fix
[X] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Checklist:

[X] I have performed a self-review of my code.
[X] I have commented my code, particularly in hard-to-understand areas.
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have gone through the  contributing.md file before contributing

Additional context:

##Are you contributing under any Open-source programme?

[X] I am contributing under GSSOC'24
[ ] I am contributing under VSOC'24

Hey @AshmitaBarthwal, the sections looks good. Your PR will be merged soon.

@itsekta thankyou. Could you mark my LEVEL of contirbution label to it ??

@apu52 I made the necessary changes. Shall I create a new pull request for this ???

@apu52 MARK THE LEVEL OF CONTRIBUTION LABEL UNDER GSSOC

@apu52 Please review my Pull Request.

@itsekta Please review my updated Pull Request.

it is not the authentic color of the text font of the website in the dark mode .please change it to the custom . U can get the color codes from the original repo .please check that

I Have made the necessary changes And i am creating a new pull request to void any confusion @apu52

Hey @AshmitaBarthwal, please create a new PR. I'm closing this one because it includes changes to the Google logo CSS and other elements. Please address one issue at a time. For the About Us section, ensure that the color combination matches the current UI, as the colors you used are not suitable.

@itsekta YES I have created a new pull request.


test: portability.posix.env.newlib/portability.posix.common.newlib Fatal error on nsim

Describe the bug
Tests:
tests/posix/env/portability.posix.env.newlib
and
tests/posix/common/portability.posix.common.newlib
end with error.
I think these are similar problems.
To Reproduce
twister -p nsim_em -s tests/posix/env/portability.posix.env.newlib
twister -p nsim_em -s tests/posix/common/portability.posix.common.newlib
Logs and console output
tests/posix/env/portability.posix.env.newlib:
*** Booting Zephyr OS build v3.7.0-3583-g0a20f24d7090 ***
Running TESTSUITE env
===================================================================
START - test_getenv
 PASS - test_getenv in 0.001 seconds
===================================================================
START - test_getenv_r
 PASS - test_getenv_r in 0.002 seconds
===================================================================
START - test_setenv
 PASS - test_setenv in 0.001 seconds
===================================================================
START - test_unsetenv
 PASS - test_unsetenv in 0.002 seconds
===================================================================
START - test_watertight
E: ***** Exception vector: 0x6, cause code: 0x1, parameter 0x2
E: Address 0x80000b40
E: EV_ProtV
E: Memory read protection violation (stack checking scheme)
E:  r0: 0x80000b44  r1: 0x0  r2: 0x8000009c  r3: 0x80000b47
E:  r4: 0x80808080  r5: 0x3d3d3d3d  r6: 0x3d6f7869  r7: 0x0
E:  r8: 0x1010101  r9: 0x0 r10: 0x80002cd0 r11: 0x80808080
E: r12: 0x3 r13: 0x0  pc: 0x7ae0
E:  blink: 0x14c status32: 0x80086a06
E: lp_end: 0x7bea lp_start: 0x7bdc lp_count: 0x0
E: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
E: Current thread: 0x8000009c (test_watertight)
E: Halting system
Console now belongs to simulator.

tests/posix/common/portability.posix.common.newlib:
*** Booting Zephyr OS build v3.7.0-3583-g0a20f24d7090 ***
Running TESTSUITE barrier
===================================================================
START - test_barrier
 PASS - test_barrier in 0.001 seconds
===================================================================
TESTSUITE barrier succeeded
Running TESTSUITE clock
===================================================================
START - test_clock_getcpuclockid
 PASS - test_clock_getcpuclockid in 0.001 seconds
===================================================================
START - test_clock_getres
 PASS - test_clock_getres in 0.001 seconds
===================================================================
START - test_clock_gettime
 PASS - test_clock_gettime in 0.001 seconds
===================================================================
START - test_clock_settime
 PASS - test_clock_settime in 0.001 seconds
===================================================================
START - test_gettimeofday
 PASS - test_gettimeofday in 0.001 seconds
===================================================================
START - test_realtime
I: n: 20, sleep: 100, margin: 10, lo: 110, avg: 110, hi: 110
 PASS - test_realtime in 2.199 seconds
===================================================================
TESTSUITE clock succeeded
Running TESTSUITE cond
===================================================================
START - test_cond_resource_exhausted
 PASS - test_cond_resource_exhausted in 0.001 seconds
===================================================================
START - test_cond_resource_leak
 PASS - test_cond_resource_leak in 0.002 seconds
===================================================================
START - test_pthread_condattr
 PASS - test_pthread_condattr in 0.001 seconds
===================================================================
TESTSUITE cond succeeded
Running TESTSUITE confstr
===================================================================
START - test_confstr
 PASS - test_confstr in 0.001 seconds
===================================================================
TESTSUITE confstr succeeded
Running TESTSUITE fnmatch
===================================================================
START - test_fnmatch
 PASS - test_fnmatch in 0.003 seconds
===================================================================
TESTSUITE fnmatch succeeded
Running TESTSUITE grp
===================================================================
START - test_grp_stubs
 PASS - test_grp_stubs in 0.001 seconds
===================================================================
TESTSUITE grp succeeded
Running TESTSUITE key
===================================================================
START - test_correct_key_is_deleted
 PASS - test_correct_key_is_deleted in 0.001 seconds
===================================================================
START - test_key_1toN_thread
 PASS - test_key_1toN_thread in 0.003 seconds
===================================================================
START - test_key_Nto1_thread
 PASS - test_key_Nto1_thread in 0.002 seconds
===================================================================
START - test_key_resource_leak
 PASS - test_key_resource_leak in 0.001 seconds
===================================================================
TESTSUITE key succeeded
Running TESTSUITE mqueue
===================================================================
START - test_mqueue
 PASS - test_mqueue in 0.023 seconds
===================================================================
START - test_mqueue_notify_basic
 PASS - test_mqueue_notify_basic in 0.002 seconds
===================================================================
START - test_mqueue_notify_errors
 PASS - test_mqueue_notify_errors in 0.002 seconds
===================================================================
START - test_mqueue_notify_non_empty_queue
 PASS - test_mqueue_notify_non_empty_queue in 0.002 seconds
===================================================================
START - test_mqueue_notify_thread
 PASS - test_mqueue_notify_thread in 0.104 seconds
===================================================================
TESTSUITE mqueue succeeded
Running TESTSUITE mutex
===================================================================
START - test_mutex_normal
mutex lock is taken
 PASS - test_mutex_normal in 0.105 seconds
===================================================================
START - test_mutex_prioceiling_stubs
 PASS - test_mutex_prioceiling_stubs in 0.001 seconds
===================================================================
START - test_mutex_recursive
recursive mutex lock is taken
 PASS - test_mutex_recursive in 0.105 seconds
===================================================================
START - test_mutex_resource_exhausted
 PASS - test_mutex_resource_exhausted in 0.001 seconds
===================================================================
START - test_mutex_resource_leak
 PASS - test_mutex_resource_leak in 0.002 seconds
===================================================================
START - test_mutex_timedlock
Expecting timedlock with timeout of 200 ms to fail
Expecting timedlock with timeout of 200 ms to succeed after 100ms
 PASS - test_mutex_timedlock in 0.320 seconds
===================================================================
TESTSUITE mutex succeeded
Running TESTSUITE mutex_attr
===================================================================
START - test_pthread_mutexattr_destroy
 PASS - test_pthread_mutexattr_destroy in 0.001 seconds
===================================================================
START - test_pthread_mutexattr_gettype
 PASS - test_pthread_mutexattr_gettype in 0.001 seconds
===================================================================
START - test_pthread_mutexattr_init
 PASS - test_pthread_mutexattr_init in 0.001 seconds
===================================================================
START - test_pthread_mutexattr_settype
 PASS - test_pthread_mutexattr_settype in 0.001 seconds
===================================================================
TESTSUITE mutex_attr succeeded
Running TESTSUITE nanosleep
===================================================================
START - test_clock_nanosleep_errors_errno
 PASS - test_clock_nanosleep_errors_errno in 0.001 seconds
===================================================================
START - test_clock_nanosleep_execution
 PASS - test_clock_nanosleep_execution in 3.015 seconds
===================================================================
START - test_nanosleep_errors_errno
 PASS - test_nanosleep_errors_errno in 2.028 seconds
===================================================================
START - test_nanosleep_execution
 PASS - test_nanosleep_execution in 3.538 seconds
===================================================================
TESTSUITE nanosleep succeeded
Running TESTSUITE posix_apis
===================================================================
START - test_fdtable_init
 PASS - test_fdtable_init in 0.001 seconds
===================================================================
START - test_posix_sysconf
 PASS - test_posix_sysconf in 0.001 seconds
===================================================================
TESTSUITE posix_apis succeeded
Running TESTSUITE pthread
===================================================================
START - test_pthread_cleanup
 PASS - test_pthread_cleanup in 0.001 seconds
===================================================================
START - test_pthread_descriptor_leak
 PASS - test_pthread_descriptor_leak in 0.006 seconds
===================================================================
START - test_pthread_equal
 PASS - test_pthread_equal in 0.001 seconds
===================================================================
START - test_pthread_execution
Thread 0 starting with scheduling policy 1 & priority 0
Thread 1 starting with scheduling policy 1 & priority 0
Thread 2 starting with scheduling policy 1 & priority 0
Bounce test OK
Barrier test OK
 PASS - test_pthread_execution in 4.987 seconds
===================================================================
START - test_pthread_priority_conversion
 PASS - test_pthread_priority_conversion in 0.001 seconds
===================================================================
START - test_pthread_set_get_concurrency
 PASS - test_pthread_set_get_concurrency in 0.001 seconds
===================================================================
START - test_pthread_setschedprio
 PASS - test_pthread_setschedprio in 0.001 seconds
===================================================================
START - test_pthread_termination
Thread 0 starting with a priority of 4
Cancelling thread 0
Thread 0 could not be cancelled
Thread 1 starting with a priority of 3
Cancelling thread 1
Thread 1 could not be cancelled
Thread 2 starting with a priority of 2
Cancelling thread 2
Thread 2 could not be cancelled
Thread 3 starting with a priority of 1
Cancelling thread 3
Thread 3 could not be cancelled
 PASS - test_pthread_termination in 1.012 seconds
===================================================================
START - test_pthread_testcancel
 PASS - test_pthread_testcancel in 0.001 seconds
===================================================================
START - test_sched_getparam
 PASS - test_sched_getparam in 0.001 seconds
===================================================================
START - test_sched_getscheduler
 PASS - test_sched_getscheduler in 0.001 seconds
===================================================================
START - test_sched_rr_get_interval
 PASS - test_sched_rr_get_interval in 0.001 seconds
===================================================================
START - test_sched_setparam
 PASS - test_sched_setparam in 0.001 seconds
===================================================================
START - test_sched_setscheduler
 PASS - test_sched_setscheduler in 0.001 seconds
===================================================================
TESTSUITE pthread succeeded
Running TESTSUITE pthread_attr
===================================================================
START - test_null_attr
 PASS - test_null_attr in 0.001 seconds
===================================================================
START - test_pthread_attr_getdetachstate
 PASS - test_pthread_attr_getdetachstate in 0.001 seconds
===================================================================
START - test_pthread_attr_getguardsize
 PASS - test_pthread_attr_getguardsize in 0.001 seconds
===================================================================
START - test_pthread_attr_getinheritsched
 PASS - test_pthread_attr_getinheritsched in 0.001 seconds
===================================================================
START - test_pthread_attr_getschedparam
 PASS - test_pthread_attr_getschedparam in 0.001 seconds
===================================================================
START - test_pthread_attr_getschedpolicy
 PASS - test_pthread_attr_getschedpolicy in 0.001 seconds
===================================================================
START - test_pthread_attr_getscope
 PASS - test_pthread_attr_getscope in 0.001 seconds
===================================================================
START - test_pthread_attr_getstack
 PASS - test_pthread_attr_getstack in 0.001 seconds
===================================================================
START - test_pthread_attr_getstacksize
 PASS - test_pthread_attr_getstacksize in 0.001 seconds
===================================================================
START - test_pthread_attr_init_destroy
 PASS - test_pthread_attr_init_destroy in 0.002 seconds
===================================================================
START - test_pthread_attr_large_stacksize
Unable to allocate large stack of size 8388608 (skipping)
 SKIP - test_pthread_attr_large_stacksize in 0.002 seconds
===================================================================
START - test_pthread_attr_policy_and_priority_limits
 PASS - test_pthread_attr_policy_and_priority_limits in 0.004 seconds
===================================================================
START - test_pthread_attr_setdetachstate
 PASS - test_pthread_attr_setdetachstate in 0.202 seconds
===================================================================
START - test_pthread_attr_setguardsize
 PASS - test_pthread_attr_setguardsize in 0.001 seconds
===================================================================
START - test_pthread_attr_setinheritsched
 PASS - test_pthread_attr_setinheritsched in 0.002 seconds
===================================================================
START - test_pthread_attr_setschedparam
 PASS - test_pthread_attr_setschedparam in 0.001 seconds
===================================================================
START - test_pthread_attr_setschedpolicy
 PASS - test_pthread_attr_setschedpolicy in 0.001 seconds
===================================================================
START - test_pthread_attr_setscope
 PASS - test_pthread_attr_setscope in 0.001 seconds
===================================================================
START - test_pthread_attr_setstack
 PASS - test_pthread_attr_setstack in 0.002 seconds
===================================================================
START - test_pthread_attr_setstacksize
 PASS - test_pthread_attr_setstacksize in 0.002 seconds
===================================================================
START - test_pthread_attr_static_corner_cases
 SKIP - test_pthread_attr_static_corner_cases in 0.001 seconds
===================================================================
TESTSUITE pthread_attr succeeded
Running TESTSUITE pwd
===================================================================
START - test_pwd_stubs
 PASS - test_pwd_stubs in 0.001 seconds
===================================================================
TESTSUITE pwd succeeded
Running TESTSUITE rwlock
===================================================================
START - test_pthread_rwlockattr_getpshared
 PASS - test_pthread_rwlockattr_getpshared in 0.001 seconds
===================================================================
START - test_pthread_rwlockattr_setpshared
 PASS - test_pthread_rwlockattr_setpshared in 0.001 seconds
===================================================================
START - test_rw_lock
 PASS - test_rw_lock in 0.133 seconds
===================================================================
TESTSUITE rwlock succeeded
Running TESTSUITE semaphore
===================================================================
START - test_named_semaphore
 PASS - test_named_semaphore in 5.695 seconds
===================================================================
START - test_semaphore
 PASS - test_semaphore in 5.008 seconds
===================================================================
TESTSUITE semaphore succeeded
Running TESTSUITE signal
===================================================================
START - test_pthread_sigmask
 PASS - test_pthread_sigmask in 0.002 seconds
===================================================================
START - test_sigaddset
 PASS - test_sigaddset in 0.001 seconds
===================================================================
START - test_sigaddset_oor
 PASS - test_sigaddset_oor in 0.001 seconds
===================================================================
START - test_sigdelset
 PASS - test_sigdelset in 0.001 seconds
===================================================================
START - test_sigdelset_oor
 PASS - test_sigdelset_oor in 0.001 seconds
===================================================================
START - test_sigemptyset
 PASS - test_sigemptyset in 0.001 seconds
===================================================================
START - test_sigfillset
 PASS - test_sigfillset in 0.001 seconds
===================================================================
START - test_sigismember
 PASS - test_sigismember in 0.001 seconds
===================================================================
START - test_sigismember_oor
 PASS - test_sigismember_oor in 0.001 seconds
===================================================================
START - test_signal_strsignal
E: ***** Exception vector: 0x6, cause code: 0x1, parameter 0x2
E: Address 0x800041b0
E: EV_ProtV
E: Memory read protection violation (stack checking scheme)
E:  r0: 0x800041b4  r1: 0x800040f0  r2: 0x800016e0  r3: 0x800041b7
E:  r4: 0x1010101  r5: 0xb  r6: 0x1  r7: 0x1010101
E:  r8: 0x8000412c  r9: 0x0 r10: 0x0 r11: 0x0
E: r12: 0xa r13: 0x27394 pc: 0x186fc
E:  blink: 0x776e status32: 0x80086a06
E: lp_end: 0x1c3cc lp_start: 0x1c3c4 lp_count: 0x0
E: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
E: Current thread: 0x800012c4 (test_signal_strsignal)
E: Halting system
Console now belongs to simulator.

Expected behavior
Tests passed
Environment:

Linux Ubuntu 22.04
Toolchain: Zephyr SDK 16.8
Zephyr version: v3.7.0-3583-g0a20f24d7090

Observed also on nsim/nsim_hs/mpuv6.
nsim/nsim_hs/mpuv6        tests/posix/common/portability.posix.common.newlib FAILED Timeout (nsim 2.060s)
twister-out/nsim_nsim_hs_mpuv6/tests/posix/common/portability.posix.common.newlib/handler.log
...
===================================================================
START - test_sigismember_oor
 PASS - test_sigismember_oor in 0.001 seconds
===================================================================
START - test_signal_strsignal
E: ***** Exception vector: 0x6, cause code: 0x1, parameter 0x2
E: Address 0x80003da0
E: EV_ProtV
E: Memory read protection violation (stack checking scheme)
E:  r0: 0x80003da4  r1: 0x80003ce0  r2: 0x800016cc  r3: 0x80003da7
E:  r4: 0xb  r5: 0x1  r6: 0x2e  r7: 0x0
E:  r8: 0x0  r9: 0x0 r10: 0x0 r11: 0x2a1bd
E: r12: 0xa r13: 0x2758c  pc: 0x16fb4
E:  blink: 0x76ba status32: 0x80086a02
E: lp_end: 0x1a9ac lp_start: 0x1a9a4 lp_count: 0x0
E: >>> ZEPHYR FATAL ERROR 2: Stack overflow on CPU 0
E: Current thread: 0x800012b4 (test_s)
E: Halting system

Looks like a problem with the 'optimized' newlib strlen implementation that compares words instead of bytes.
These instructions trigger the problem:
strlen       or           %r3,%r0,7
strlen+0x04  ld           %r2,[%r3,-7]

ARC hardware stack bounds checking not only ensures the stack stays within bounds but also raises an exception on non-sp based memory references to the unallocated stack (between stack_top and sp).
The word alignment (or 7) and correction (-7 offset) points to a valid address (4 byte buf), but r3 points to the unallocated stack.
Not sure yet who's to blame and where to fix: compiler, newlib (or even hardware to not check the base but base+offset...)?

This sounds like a newlib problem

@keith-packard This looks like a similar problem as fixed in https://github.com/picolibc/picolibc/pull/508
Any suggestions? I like the notion of "PICOLIBC_NO_OUT_OF_BOUNDS_READS". Here, the trigger is hardware stack protection, but it could have been any protection (e.g. mem domains).

The only reason we aren't hitting this with picolibc is because the SDK only includes -Os versions, which don't use the arc assembly code...
I'm a bit confused though -- is the stack not 8-byte aligned in both base and size? If it were, how could these accesses be out-of-bounds? Or is the issue that SP is actually 0x80003da4 and we're reading below that address?
I assume that switching to the C versions would solve this problem? That code never reads before the string and only reads long values on long-aligned addresses -- it will read bytes past the end of the string, but never past the longword containing the end of the string. If so, fixing the newlib build to skip the arc assembly code would be fairly easy. We'll want to also make the same changes in picolibc. Alternatively, some brave volunteer could offer to fix the arc assembly code, once we understand the cause.

Correct, this is not about stack allocation/alignment, it is about the value of the stack pointer + ARC hardware stack checks. Non-SP based accesses to the 'unallocated' stack (a better description would be the unused part of the total allocated stack) trigger an exception.
It sounds like the "PICOLIBC_NO_OUT_OF_BOUNDS_READS" was added for a different problem (stack alignment).
I agree that switching to the C version may be the better solution. I'm not sure both C implementations (the performance optimized one, as well as the simple per byte loop) would work. The "-Os" flag I assume picks the byte loop one? That should always work, but misses the optimization when ARC hardware stack checking is not configured in the hardware or not enabled.

Reading the ARC asm code, it sure looks like the issue should only occur when the buffer is not 8-byte aligned and sits at the same address as SP. If that's true, then the C version should work fine -- it aligns the source address by doing byte-by-byte compares, then performs long-at-a-time compares for the remainder of the string. As long as the stack is allocated on long-aligned boundaries, then it will not access any out-of-bounds addresses.
Performance will be reduced as the C code operates on longs while the asm code operates on pairs of 4-byte values, and the asm code takes advantage of additional instructions which the C code does not.
I suggest testing using picolibc as a module and configuring the build to optimize for speed instead of size. I'm unable to test this myself as I don't have access to 'nsim'.

Thanks @keith-packard, this looks like a problem for the assembly optimized code only. The standard C version doesn't trigger the problem (neither the speed or size optimized variant). But currently only when size optimization is chosen the C version is used. The assembly code and C code have similar optimizations, but the C version doesn't seem to do out of bound reads (as you explained, that may only happen with unaligned pointers). I guess we should either have a new 'no out of bounds' config option that doesn't pick the assembly version when set, or completely drop the ARC assembly versions of strlen in favor of the standard C version (I didn't compare the compiler generated vs assembly variants).

I can easily disable the assembly versions in picolibc; it looks like there would be only a modest performance improvement when using them. Does someone want to make the equivalent changes in newlib? Or should we disable newlib as an option on arc targets?

I can easily disable the assembly versions in picolibc; it looks like there would be only a modest performance improvement when using them. Does someone want to make the equivalent changes in newlib? Or should we disable newlib as an option on arc targets?

I guess that was already done here https://github.com/picolibc/picolibc/pull/889, right?

I guess that was already done here picolibc/picolibc#889, right?

Yup.


[Documentation] Document beartype-specific typing cause protocol

In companion issue #116, resident nptyping guru and animalish mad lad @ramonhagenaars wisely proposes @beartype codify a protocol for use by third-party type hint APIs. This protocol would enable these APIs to describe to interested runtime type checkers (chiefly, @beartype) the exact cause of a runtime type-checking failure. This is really needful for third-party type hints describing opaque data structures. (See: "What is a tensor? No, seriously.")
Currently, @beartype only emits coarse-grained exception messages for third-party type hint APIs. These messages fail to describe the exact cause of type-checking failures. Real-world nptyping example or it didn't happen, so:
>>> from beartype import beartype
>>> from nptyping import NDArray, Shape
>>> import numpy as np
>>> @beartype
... def fun(_: NDArray[Shape[
...     '*, [a, b, c], 2, BareNecessities, 5 bananas'], Float]) -> None:
...     ...
>>> fun(np.array())
@beartyped fun() parameter _="array([<some big array>])" violates type hint NDArray[Shape['2, 2'], Float], as "array([<some big array>])" not instance of <protocol "nptyping.ndarray.NDArray">

Clearly, @beartype's claim that the passed NumPy array is, in fact, not a NumPy array is fallacious. That's bad. The passed NumPy array obviously is a NumPy array; it just happens to violate the expected shape required by the third-party type hint.
Once we resolve issue #116, let's publicly (and prominently) document the get_cause() protocol. Doing so enables other third-party type hint APIs that are not nptyping to publish similar descriptive causes for consumption by @beartype.
Thus spake the grizzled bear. :bearded_person:

Aaaaaaaaand... it kinda seems doubtful anybody still wants this. Let's quietly close this out to make @beartype look better. :hand_over_mouth:


Hangs without feedback upon creating spreadsheet

After creating the spreadsheet, I don't see feedback to indicate that the operation was successful. The app is still processing, but I can only tell by hovering my mouse over the menu bar and seeing the waiting icon. If I clicking out of the window and go do something else (like edit the spreadsheet), it finishes running and displays properly after a while.

I have the same problem (under Linux / JRE 8, Update 121).

Same problem there too