Add RCA documentation

Future outages should be documented and their root cause analyzed.  This proposes a framework for RCA reports and a place to house them.
Fixes BonnyCI/projman#188
Signed-off-by: matthew wagoner<EMAIL_ADDRESS>

this is a stripped down version of a document I found here: http://www.projectmanagementdocs.com/project-controlling-templates/root-cause-analysis.html#axzz4fwQLZNMC
I am not sure if they need to be credited any further.

Awesome, thanks!
One question for clarification: should outage reports be added and updated here in real-time, or should we wait until after finishing the RCA process before proposing a new past report?

I would think we would do as we have so far: start a projman issue to keep track of the outage in real time.  We can then propose reports as PRs to the bonnyci.org repo and discuss at the outage callout meeting.


#3 adding in the onbuild trigger so we upgrade the openjdk on each it…

…eration of downstream child images

LGTM - maybe a variable to define the update in one place...

LGTM


do bucketing support variable length input for  bidirectional lstm?

It seems to use 0 padding to get fixed length in every bucket.
But bi-lstm needs 2 direction to input, could mxnet know the difference ?

@sbodenstein
I think the masking and reverse layers does it

@piiswrong Thanks a lot for your fast reply. I'll check it.

This issue is closed due to lack of activity in the last 90 days. Feel free to reopen if this is still an active issue. Thanks!


demo on cpu

Hi, the demo works excellent on gpu. But on cpu i set device="cpu" and disable all cuda related commands(torch.cuda.synchronize) but still there is no prediction. I get skip loading parameter warnings, but no detection. It is as if model is not loaded properly. Thanks

There was a difference in my conf file as compared to training. Solved. Thanks

There was a difference in my conf file as compared to training. Solved. Thanks

Hello, I have the same problem with you, could you please tell me how you solve it, thank you very much.


Latest update to serenity via NuGet

[Failure] Could not find a part of the path 'C:\xxx.Web\Scripts\typings\rsvp\rsvp.d.ts'.
[Failure] Could not find file 'C:\xxx.Web\Scripts\serenity\Serenity.CoreLib.d.ts'.
[Failure] Could not find file 'C:\xxx.Web\Scripts\serenity\Serenity.Externals.d.ts'.
[Failure] Could not find file 'C:\xxx.Web\Scripts\serenity\Serenity.Externals.Slick.d.ts'.
[Failure] Could not find a part of the path 'C:\xxx.Web\Scripts\typings\jqueryui\jqueryui.d.ts'.
Will fix this manually but might need a quick check in the package.

I couldn't understand what you mean here

Do you have any spaces in your projects name?

Nope no spaces.
It's all working, seemed more like a warning than an error.

Same "issue" here upgrading from 2.1.2 to 2.1.8...

Uhm slickgrid.d.ts is an empty file (0 byte) both in my "upgraded" project and in a brand new one...

Yep it's empty, not a problem

Ok no problem then!
Btw in the upgrade process from nuget I get this:
[Failure] Could not find file 'C:\......xyz.Web\Scripts\typings\slickgrid\slickgrid.d.ts'.
[Failure] Could not find a part of the path 'C:\......xyz.Web\Scripts\typings\rsvp\rsvp.d.ts'.
[Failure] Could not find a part of the path 'C:\......xyz.Web\Scripts\serenity\Serenity.CoreLib.d.ts'.

The application seems to be working fine, but just to share this warning with you...needless to say, the previous upgrade (I mean before 2.1.2) did not report this failure message...
Thanks
Bye

The errors you get are from TypeScript language service, they are intellisense errors, while NuGet is removing and re-adding package contents to your project. So this is not a problem at all, especially with Serenity packages.


Add People picker control using SPFx extension on list view command set bar

Below is the scenario on which I want to work on.
Select the document,
Click on command button from command bar
Open popup Add 3 people picker control on the same which will fetch the data from the list person/group column Update the values in people picker.
Any inputs on this?
I want to use pnp/spfx-property-controls in .ts file of command set extension.
On click of command, popup should get opened and in that popup , i want to display this people picker control. I do not want to use react component.
I have referred the url https://sharepoint.github.io/sp-dev-fx-property-controls/controls/PropertyFieldPeoplePicker/, and tried to add that code in .ts file but it is giving an error on "this.onPropertyPaneFieldChanged,"
Let me know how to accommodate this code in .ts file.

Hi @Sampadaak2613,
Property Controls are developed to be used in SPFx Web Part Property Pane only.
There is another repo for web parts and extensions - Reusable React Controls
You have to be familiar with React development to use these components in your command set customizer.
In few words,
You'll need to install the module in your project as mentioned in the documentation linked above.
Then, you'll need to create you "Popup" component. I would recommend to create it in a separate .tsx file that allows combined markup and TypeScript code.
In this file you'll need to import needed component - in your case PeoplePicker.
And then, in render method you'll be able to use it just like <PeoplePicker ... />
Let me know if it makes sense.


Build.BuildNumber is unclear

It appears that the discussion behind where Build.BuildNumber is set is inaccurate. I see nothing in ADO Pipeline options to set this. However it appears that it can be set with a top-level 'name' property in the pipeline YAML. There is discussion about this in the 'Run number' page. However it also confusing to have 'Run number' and 'Build number' which are both the same thing. Let's just refer to 'Build number' please (since the Builds list has a 'Build #' column).

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

ID: 9ffebdc8-521c-44b5-cde4-4abdc1bd6f18
Version Independent ID: dc0effda-6d93-62aa-64c5-4e6f283b0826
Content: Predefined variables - Azure Pipelines
Content Source: docs/pipelines/build/variables.md
Product: devops
Technology: devops-cicd
GitHub Login: @steved0x
Microsoft Alias: sdanie

In Microsoft Team Foundation Server (TFS) 2018 and previous versions, runs are called builds. We've added clarification of this as part of #5726 and that update will be live soon.


feat: Resolved Dark Mode Persistance Issue After refreshing

Hi @apu52,
Title : Dark mode gets turned off on refeshing a page
Issue Close #732
Description
I have resolved the issue to persist the dark mode preference across page refreshes using localStorage.
The changes ensure that the user's selected mode (dark or light) is maintained even after the page is refreshed.
Please take a look and review it.
Changes made :

To make the dark mode preference persist across page refreshes, used "localStorage" to save the user's preference.
Then Saved the theme preference in localStorage whenever the theme is toggled.
and then Checked the saved theme preference when the page loads and apply it accordingly.

Video/Screenshots (mandatory)
https://github.com/apu52/Travel_Website/assets/131389695/8a466c0e-1ac4-48fa-8408-a028b67f4988
Type of PR

[x] Bug fix
[x] Feature enhancement

Checklist:

[x] I have performed a self-review of my code.
[ ] 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

##Are you contributing under any Open-source programme?
GSSOC'24
Could you please review and also give required labels?

@apu52 i resolved the issue. It is working fine now. Please take a look

Hi @apu52,
Could you Please take a look. also add required labels.

@apu52

@apu52, I just checked it and it's working fine.
Please take a look -
https://github.com/apu52/Travel_Website/assets/131389695/3e11ad2b-4c0b-4de2-a2ef-fe67ccf3a076

@apu52, I just checked it and it's working fine.
Please take a look -
TravelWebsite.Issue.mp4

yes .now its working fine


Feature: Add support for NeoTree

Thanks for your amazing plugin!
I see support for NvimTree but it would be very nice if you could support neo-tree as well.
The highlight group names can be found here:
https://github.com/nvim-neo-tree/neo-tree.nvim/blob/230ff118613fa07138ba579b89d13ec2201530b9/doc/neo-tree.txt#L1298-L1346
Related: https://github.com/Mofiqul/vscode.nvim/issues/147
Thanks in advance ;)

+1


Service account management

Rancher API and UI provide no means for managing k8s service accounts, which are crucial to deploying many catalog items/helm charts/workloads.
We should add this ability

It would help if we could, for example, deploy a single service account to all downstream clusters.  In this use case, we are working on ServiceNOW integration with downstream clusters and would like to create the same service account on every downstream clusters automatically.


[BUG] 2022.2.0.dev20220109

On the newest devs of HA the integration isnt't loading anymore. The same happened to the node-red integration. Also it cant be found anymore in the store of Hacs when searching for it.

This is a HACS issue, see #261. Please close this issue if updating HACS fix the issue.

Yup that did it. Sorry about that!


Added fields for webconsole URL and API URL to certificate creation

Set API URL and Web Console URL fields for the new certificate requests. These added fields will allow us to check the certificates installed on the cluster and the certificates from the secret stored on Hive cluster with greater ease. Also fixed bug in Sync Certificate Request function in Reconcile loop to ensure that Current CR Spec is set to the value of the Desired CR Spec.

/lgtm


block sometimes needs an initial refresh to get most recent information

Sometimes edits to blocks made in the Notion web UI are not immediately available through the API.
For example, create a sample script test.py like:
client = NotionClient("[TOKEN]", monitor=False)
page = client.get_block("[PAGE URL]")
print(page.title)
page.refresh()
print(page.title)

Create new page with title "A" and run the script on it. It will output
A
A

Edit the title to "B" in the web UI and re-run. It will output
A
B

I would expect it to output
B
B

If you set monitor=False, it will not be monitoring for changes and auto-update. Try with monitor=True.

In the example above, each run of test.py is independent. Monitoring should not be necessary, unless you're saying that there's a cache of some sort shared between multiple runs?

There's a cache of some sort shared between multiple runs. :)

But given monitoring can be turned off (and is currently broken), I think the cache should be re-thought a bit...

the cache sounds useful, but I would expect it to be opt-in and off by default

Sounds good. The main place it's essential is the combination of monitoring + callbacks + app restarts.  I'll think that through when I get monitoring going again.

As of 0.0.25 (just released) it's now disabled by default, and can be enabled with NotionClient(..., enable_caching=True).


API method to retrieve running Chroma version

Useful to make sure that a remote Chroma is as expected or whether a new feature is available yet.

im taking care of this in a small PR

I think we have version which is fine for now?

@HammadB yep! that's what im using ;)


Should we remove prove_and_verify from the CLI commands?

## Observation
This method seems to only be useful for running tests, because the prover will likely not create a proof and then verify it in one go, unless they are debugging something. The workflow is usually, one entity creates the proof and another verifies the proof.
I don't think there is a meaningful discrepancy between using prove_and_verify versus using prove and `verify. Though if its only used for tests/debugging, it makes sense to discuss testing the end to end tests using the actual workflow.

This has been fixed, circuit building at prove time was running different code branches to building the vk


slog-term works only on stable.

Because of nightly/beta regression: https://github.com/rust-lang/rust/issues/40011

Rust issue is closed

All right. Thanks!


Impossible to load photos from gallery if "Optimize iPhone Storage" is selected

Hi and thanks for sharing this beautiful picker.
In my iPhone i have this: Settings->Photos & Camera->Optimise iPhone Storage
Lot of my photos are in low res loaded in iCloud, and with the standard picker they are downloaded from iCloud when selected.
With Fusuma picker if I pick up a photo from my gallery (and if the photo is a low res photo loaded in iCloud) the photo is not displayed.

Ok, i fixed it.
Just insert :
let options = PHImageRequestOptions()
options.networkAccessAllowed = true
just before each imageManager.requestImageForAsset call.

Michele


deps: update to zeebe-node@2

Bumps to zeebe-node@2 (builds on top of https://github.com/camunda/camunda-modeler/pull/2797).
Reduces the modeler distribution size from 130 MB to 100 MB (Linux).
Speeds up the build process significantly.
Works on

[x] Linux (zeebe 1.3) @nikku
[ ] Windows
[ ] MacOS

Build artifacts (available soon)
(https://github.com/camunda/camunda-modeler/actions/runs/1922103601)

https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/update-zeebe-node/camunda-modeler-update-zeebe-node-linux-x64.tar.gz
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/update-zeebe-node/camunda-modeler-update-zeebe-node-mac.dmg
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/update-zeebe-node/camunda-modeler-update-zeebe-node-mac.zip
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/update-zeebe-node/camunda-modeler-update-zeebe-node-win-ia32.zip
https://camunda-modeler-on-demand.s3.eu-central-1.amazonaws.com/update-zeebe-node/camunda-modeler-update-zeebe-node-win-x64.zip

Closes #2783

Once again I need your help on integration testing against Windows / MacOS @Skaiir @smbea .

From ~20 minutes to ~7 minutes of build time. I am looking forward to merging this :)

@Skaiir @smbea please have a look.

Works on MacOS 👍

Works on Windows as well 👍


[TikTok] Interaction Stickers

DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

[X] I understand that I will be blocked if I remove or skip any mandatory* field

Checklist

[X] I'm requesting a site-specific feature
[X] I've verified that I'm running yt-dlp version 2022.09.01 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue
[ ] I've read about sharing account credentials and I'm willing to share it if required

Region
USA
Example URLs
https://www.tiktok.com/t/ZTRmCRKfv/
https://www.tiktok.com/t/ZTRmCRjNF/
https://www.tiktok.com/t/ZTRmCYwgH/
https://www.tiktok.com/t/ZTRmCN3uG/
https://www.tiktok.com/@newlinersseries/video/7148181531603897643?_r=1&u_code=e26e3635964a9j&preview_pb=0&language=en&_d=e2dmmdf2jd7k6j&share_item_id=7148181531603897643&source=h5_m&timestamp=1664588428&ug_btm=b8727,b2878&sec_user_id=MS4wLjABAAAAWRTxa9TmYNrI8T-5s9uJDRAEjUK47kceEtCRyFUIEsMang6XJwIvZMYGqCObcv8g&utm_source=copy&utm_campaign=client_share&utm_medium=ios&tt_from=copy&user_id=7106641030017270830&share_link_id=143EF17A-B3EB-4233-820F-4CDC664C3DFC&share_app_id=1233
Provide a description that is worded well enough to be understood
Please add support for interaction stickers on TikTok. I need them personally for future searching and upscaling, but there are many other applications available for this data as well. I seen the code, and it seems like you tried to implement it as a subtitle format. You can either put it in the .info.json or make a new subtitle format called the .interaction_stickers.json .
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
Documents]$ yt-dlp -vU https://www.tiktok.com/
n 1 (char 0). Retrying... (attempt 1 of 5)
[TikTok]<PHONE_NUMBER>746532654: Downloading video
 details
WARNING: [TikTok] Expecting value: line 1 colum
n 1 (char 0). Retrying... (attempt 2 of 5)
[TikTok]<PHONE_NUMBER>746532654: Downloading video
 details
WARNING: [TikTok] Expecting value: line 1 colum
n 1 (char 0). Retrying... (attempt 3 of 5)
[TikTok]<PHONE_NUMBER>746532654: Downloading video
 details
WARNING: [TikTok] Expecting value: line 1 colum
n 1 (char 0). Retrying... (attempt 4 of 5)
[TikTok]<PHONE_NUMBER>746532654: Downloading video
 details
WARNING: [TikTok]<PHONE_NUMBER>746532654: Failed t
o parse JSON; trying feed workaround
[TikTok]<PHONE_NUMBER>746532654: Downloading video
 feed
[debug] Sort order given by extractor: quality,
 codec, size, br
[debug] Formats sorted by: hasvid, ie_pref, qua
lity, vcodec, acodec, filesize, fs_approx, tbr,
 vbr, abr, lang, res, fps, hdr:12(7), channels,
 asr, proto, vext, aext, hasaud, source, id
7147358339746532654 has no subtitles

You'll need to first explain to me what "interaction stickers" even are

You need yt-dlp to do what with the stickers? Also I don't visually see them on the 1st nor 2nd video

Download them to the info json or a caption json
On Saturday, October 1, 2022, MinePlayersPE - notifications at github.com <
@.***> wrote:

You need yt-dlp to do what with the stickers? Also I don't visually see
them on the 1st nor 2nd video
—
Reply to this email directly, view it on GitHub
https://github.com/yt-dlp/yt-dlp/issues/5093#issuecomment-1264279245,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3B3Y2UJMI4JSNJKIQM6HVTWA7TWJANCNFSM6AAAAAAQ2HMOZM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Interaction Stickers are a field in the TikTok api json that has all the information about the stickers, including contents and timeframe. This includes text people put on TikTok, reply stickers, image stickers, and more. My use case is to archive TikTok videos and be able to search them easier with the text info, however you can upscale videos or interact with the videos (like supporting a nonprofit or viewing a reply)

I don't see any timed text/images in the webpage of the example URLs you have given

I don't see any timed text/images in the webpage of the example URLs you have given

https://media.discordapp.net/attachments/1010778636976144394/1026178944682176582/RPReplay_Final1664730424.mp4
These stickers aren’t always interactive, most of the time, the text is static, however replies are in that coffee table video. They look static to desktop browsers and they are. It’s handy for interacting with replies and other interaction stickers, or searching text content of TikTok videos

Interaction Stickers are a field in the TikTok api json that has all the
information about the stickers, including contents and timeframe. This
includes text people put on TikTok, reply stickers, image stickers, and
more. My use case is to archive TikTok videos and be able to search them
easier with the text info, however you can upscale videos or interact with
the videos (like supporting a nonprofit or viewing a reply)
On Friday, September 30, 2022, pukkandan - notifications at github.com <
@.***> wrote:

You'll need to first explain to me what "interaction stickers" even are
—
Reply to this email directly, view it on GitHub
https://github.com/yt-dlp/yt-dlp/issues/5093#issuecomment-1264253255,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A3B3Y2XEVY4AU6GQYNSHQ7LWA7FV3ANCNFSM6AAAAAAQ2HMOZM
.
You are receiving this because you authored the thread.Message ID:
@.***>


Added Vulture dead code checker

What does this PR do?
Solves #5649
I have integrated Vulture to CI for dead code checking.
Before submitting

[x] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[ ] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[ ] Add labels and milestones (and optionally projects) to the PR so it can be classified
[ ] Check that target branch and milestone match!

Did you have fun?
Make sure you had fun coding 🙃

@aniketmaurya thx for the quick PR, mind rebase it on feat 1.2

@aniketmaurya thx for the quick PR, mind rebase it on feat 1.2

does it report any issue now?

Hi @Borda, You mean in the GitHub actions? Yes, there are few dead code blocks detected by it.

does it report any issue now?

Hi @Borda, You mean in the GitHub actions? Yes, there are few dead code blocks detected by it.

does it report any issue now?

Hi @Borda, You mean in the GitHub actions? Yes, there are few dead code blocks detected by it.

ok, soo it shall be fixed within the PR :]
but fist can you rebase it in release/1.2-dev?

does it report any issue now?

Hi @Borda, You mean in the GitHub actions? Yes, there are few dead code blocks detected by it.

ok, soo it shall be fixed within the PR :]
but fist can you rebase it in release/1.2-dev?

does it report any issue now?

Hi @Borda, You mean in the GitHub actions? Yes, there are few dead code blocks detected by it.

ok, soo it shall be fixed within the PR :]
but fist can you rebase it in release/1.2-dev?

@Borda  I think I messed up something during hard reset to 1.2 :(

does it report any issue now?

Hi @Borda, You mean in the GitHub actions? Yes, there are few dead code blocks detected by it.

ok, soo it shall be fixed within the PR :]
but fist can you rebase it in release/1.2-dev?

@Borda  I think I messed up something during hard reset to 1.2 :(

@aniketmaurya fixed :]

@aniketmaurya fixed :]

@aniketmaurya fixed :] can you fix the code so the check pass :]

@aniketmaurya fixed :] can you fix the code so the check pass :]

There are a total of 37 unused variables detected in different modules. Should I check and remove them or add them to whitelist? I am not familiar with all of the modules.

@aniketmaurya fixed :] can you fix the code so the check pass :]

@aniketmaurya fixed :] can you fix the code so the check pass :]

There are a total of 37 unused variables detected in different modules. Should I check and remove them or add them to whitelist? I am not familiar with all of the modules.

Hi @RJ722, mind review the vulture workflow CI here?

I think that all these ignores are just temporary hacks and all shall be resolved properly

and will there be ugly # vulture: ignore in the code base as we are forced to do sometimes like #type ignore for mypy?

I think that all these ignores are just temporary hacks and all shall be resolved properly

@aniketmaurya how is it going here? :]

@aniketmaurya how is it going here? :]

@aniketmaurya how is it going here? :]

I'll push the changes by either by today evening or tomorrow morning.

@aniketmaurya how is it going here? :]

I'll push the changes by either by today evening or tomorrow morning.

Hi @Borda, I have renamed the unused variables to _ and in case of multiple unused args in the same function replaced with __

Hi @Borda, I have renamed the unused variables to _ and in case of multiple unused args in the same function replaced with __

Hi @Borda, I have added ignore_names to pyproject.toml and the vulture check has passed. But I don't understand why import formatting test is failing. On my forked repo is has passed https://github.com/aniketmaurya/pytorch-lightning/runs/1823785683

@aniketmaurya mind resolving conflicts?

 Is it because we are moving to torchmetrics?
cc: @Borda

lots of dead code is being detected in pytorch_lightning/metrics module. Is it because we are moving to torchmetrics?
cc: @Borda

yes, pls ignore all inside metrics :]

@aniketmaurya mind resolving conflicts?

Done @edenlightning !

I'm not sure we should integrate this checker into Lightning, considering we have a lot of dynamism in the way we call hooks so this checker will often produce false positives.
The number of items you already had to whitelist makes me think this is not that useful for this project.

I agree with @carmocca, seems there are a lot of false positives (and a long whitelist) so I'm not sure there is much benefit to adding this.

I do not have any preference on used tool, but still thinking that we shall address dead code in our codebase...


Initial Conditions

https://github.com/Hickles02/FYP478/blob/77396aace18d3152b7a4fe47f8b567958ceb13d6/MATLAB/main_system.m#L33-L35
@tmlouw
Marlin specifies the initial molar holdup on each tray as one but says nothing regarding the mole fractions. Do you agree that they should all be 0?

I would rather set them equal to 0.5 initially. Funny things can happen close to zero...


[SPARK-46446][SQL][Followup] Fix sql tests for subqueries with correlated OFFSET

What changes were proposed in this pull request?
Follow-up PR for https://github.com/apache/spark/pull/44401, I had some small test fixes that didn't get included in that PR.
Why are the changes needed?
Fix tests
Does this PR introduce any user-facing change?
No
How was this patch tested?
Tests themselves
Was this patch authored or co-authored using generative AI tooling?
No

@cloud-fan
Test fails look unrelated

the test failure is unrelated, thanks, merging to master!


Activate extension on startup finished

Changes
Changed extension's activation event to onStartupFinished, so it can handle whatever it needs to right away.
Checklist

[x] have tested my change
[x] for feature PRs: PR only includes one feature enhancement.

@sebjulliand I do know that in recent VS Code releases we no longer need the command activations, but do you think it's okay that we remove the onView?

@sebjulliand I do know that in recent VS Code releases we no longer need the command activations, but do you think it's okay that we remove the onView?

@worksofliam I think so...onStartupFinished seems to be the earliest yet safest stage to activae the extension without issue.


Fix Crossref API deprecation and building on win32

Hi Alex. Maybe I posted this PR too early. This was in response to our whatsapp group.
I have a parser failure (Crossref) when the word "AND" is in a query.bibliographic, causing the program to loop the failed request as depicted here.
Not sure when I'll try to implement a workaround. If so, i'll update this PR.

As explained in the commit I just lowered everything, as the query parser fails on few all caps keywords for now.

Awesome work! I'ill generate a release from the new version.


Fix critical bug when updating Objects

During the implementation of a system using CWS to store data, a bug was discovered. It seems that when the content of an existing object is replaced, there is a problem with the padding, during decryption.
It should be noted, that the code has been tested quite thoroughly, so the discovery of the bug is surprising! As it is concsidered a critical (show-stopper) bug, it will also be made in the 1.1 branch and will result in a new 1.1.1 release.

Last commit fixed the issue. The error was a wrong flag in the Data Entity, which prevented updating the IV. Why the internal testing didn't catch this issue is left as a problem between H2/Hibernate, since the flag was ignored. The external testing demonstrated the problem, and the cleaner code made it easier to fix.


Do not compile sources associated with disabled Goost classes

With #54, solves #49.
Allows to optimize the resulting binary for size while compiling the engine, so it's not only about run-time behavior now.
Some hacks are removed, but some added. Using injection mechanism in add_source_files to override the default behavior so that we can filter out Goost-specific classes compiled in the module, without having to modify the rest of SCSub, making it highly compatible with Godot development.
This kind of approach is important if we'd like some features in Goost to be upstreamed to Godot without much hassle in the future.
Some sources need to be renamed to match the snake_case version of class names, as the mechanism relies on PascalCase to snake_case string conversion.
That said, I think this PR pretty much makes the dependency system in Goost more or less feature-complete. It means that more classes can be added in Goost without fearing the bloat, because each and every class can be possibly disabled now in Goost.
If there are link/compilation errors that you stumble upon while disabling classes (and those are not coming from dependency errors), then feel free to open a bug report.
Should also write some documentation for this... But not 100% sure about the best API/implementation yet.

May be worth to update implementation with godotengine/godot#53860.


There is no ng2-dnd/ng2-dnd

I'm submitting a ...
[x] bug report
[ ] feature request
[ ] question about the decisions made in the repository

Do you want to request a feature or report a bug?

What is the current behavior?
I imported the latest ng2-dnd, version 4.2.0. I followed the example "Retreiving files in a drop zone".  The first import doesn't work:
import { DND_PROVIDERS, DND_DIRECTIVES } from 'ng2-dnd/ng2-dnd';

I checked my node_modules\ng2-dnd folder. There is no ng2-dnd file or directory.
I'm using Angular 2 version 4.0.3.

You have to put DndModule in the import instead of DND_PROVIDERS, in the bootstrap method DndModule.forRoot(), and 'ng2-dnd' instead of 'ng2-dnd/ng2-dnd'


Common classes

Hi,
I have a question why we are duplicating work?
There seems to be a few 'common' classes in the solution where they are duplicated in both projects. e.g. encryption. Why do we not have a 'Common' Project with these classes in that the other projects just reference?

I want the client to have no dependencies except the default ones from the .net framework.

Why can't we have a dependency on our own controlled, small library? I'm just thinking it would help out with the project structure and maintainability.

@MaxXor I think you may have misunderstood @tidusjar
If I am understanding correctly, tidusjar is suggesting that we move code that is the same for the server and the client (for example: protobuf) to another project and have the server and use the same project so we don't have to make a change to the server or client, then reflect the change to the other project. Doing this would mean we only have to change one and it would be unnecessary to require a duplicate change in the other project.

@yankejustin Correct. We would then only make the change in one location and it would be consistent across the server and client. But it would require 1 more .DLL

@tidusjar and I don't allow this one more DLL, sorry.

@MaxXor i think this is feasible.we can use ilmerge to combine the protobuf dll , encryption dll and client.exe after compiling them. simply search in google for ilmerge.exe.

we can merge mono.cecil with xrat.exe


Admin tasks

Version bump
Updated CHANGELOG
Ran cargo fix --edition

Fixes #37

Coverage remained the same at 96.773% when pulling afa5ea4c214bedd3adef3035aa3d819aa1b386e9 on dev into c808e70a2a2fc57895f5a8f2238761b24b57572f on master.

Coverage remained the same at 96.773% when pulling afa5ea4c214bedd3adef3035aa3d819aa1b386e9 on dev into c808e70a2a2fc57895f5a8f2238761b24b57572f on master.

Coverage remained the same at 96.773% when pulling afa5ea4c214bedd3adef3035aa3d819aa1b386e9 on dev into c808e70a2a2fc57895f5a8f2238761b24b57572f on master.

@rphmeier Do I need to add edition = "2018" to Cargo.toml for the Rust 2018 edition conversion?

@rphmeier Do I need to add edition = "2018" to Cargo.toml for the Rust 2018 edition conversion?

Ah, yes, I think you do.


vagrant: Add installation support for MacOS 10.15.6.

There are file sharing issues with the mac version 10.15.6 and
vagrant. Using parallels as a provider for vagrant fixes the issue.

@timabbott should we advertise this in the docs? Since parallels is paid and not an OSS, I am less inclined to do so.

Do you have more details on these file sharing issues?

Yes, the problem was that var/remote_cache_prefix was an empty file when using VirtualBox and Docker on macOS.

Let's try to debug that macOS issue.

Tim and I decided to revert this (18dcb86de53e452045f3693c8680a04f53d09758, f869701d15a53aa56c0b8511f5652dd6c25c33d2). Feel free to put them in a new PR and wait for review.

Okay! Sorry for the trouble.

Let's try to debug that macOS issue.

I tried to debug it last week, but I am not sure if this is something we can fix from our side. I can give it another try when someone reports facing the same issue.


[shared_preferences] Add iOS stub to shared_preferences_windows

Description
shared_preferences supports versions older than 1.18, so this plugin
needs the iOS stub to prevent breaking iOS projects via transitive
dependencies when shared_prefences endorses the Windows implementation.
Related Issues
flutter/flutter#41719
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[x] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
[x] I updated CHANGELOG.md to add a description of the change.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

I managed to forget this in the initial version of all three plugins :P


Update versions for Release 6.13.0

Merging the 6.13.0 release into master

#4320 should fix the test failure


Update trees_2.13 to 4.8.8

About this PR
📦 Updates org.scalameta:trees_2.13 from 4.8.7 to 4.8.8
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

🔍 Files still referring to the old version number
The following files still refer to the old version number (4.8.7).
You might want to review and update them manually.
website/docs/release_notes.md

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "trees_2.13" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scalameta", artifactId = "trees_2.13" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:semver-spec, old-version-remains, commit-count:1

Superseded by #2369.


ArangoDB Single Instance as a Docker Container Randomly Crashing

My Environment

ArangoDB Version:  3.5.2
Storage Engine: RocksDB
Deployment Mode:  Single Server
Deployment Strategy: Manual Start in Docker
Configuration:
Infrastructure: AWS t3a.small Machine
Operating System: Ubuntu 16.04
Total RAM in your machine: 2GB. However, the container's limit is 1.2GB
Disks in use: SSD
Used Package:  Docker

Component, Query & Data
Affected feature: Docker Container crashes and restarts at random intervals

AQL query (if applicable):
AQL explain (if applicable):

Dataset:

Size of your Dataset on disk: A few megabytes. The database is used for testing purposes

Replication Factor & Number of Shards (Cluster only):

Steps to reproduce

On an AWS t3a.small machine, Docker version 19.03.5, build 633a0ea838, Run ArangoDB using the following docker command:

docker run -d --name test -v /mnt/test:/var/lib/arangodb3 --restart always --memory="1200m" --cpus="1.5" -p 8529:8529 --log-driver="awslogs" --log-opt awslogs-region="eu-west-1" --log-opt awslogs-group="/docker/test" -e ARANGO_RANDOM_ROOT_PASSWORD=1 -e ARANGO_STORAGE_ENGINE=rocksdb arangodb/arangodb:3.5.2 --log.level queries=warn --log.level performance=warn

The average number of concurrent connections does not exceed 10.

Problem:
The Docker container unexpectedly restarts at random intervals, and all the connected clients get disconnected. We are unable to find out why the container is restarting and what is causing it. The memory and CPU of the underlying machine are low, and do not have any alarming values. We would like help on what is going on, or at least how to debug further
EDIT:
After further investigation, we found that Docker container running Arango is reaching the memory allocated to it fully. The memory gets filled incrementally ever since the container starts running and it never goes down, until it is filled and the container restarts.
EDIT #2:
I ran the container with the following command, but it still crashed and caused a socket hangup error on the clients:
docker run -d --name test -v /mnt/test:/var/lib/arangodb3 --restart always --memory="1200m" --cpus="1.5" -p 8529:8529 --log-driver="awslogs" --log-opt awslogs-region="eu-west-1" --log-opt awslogs-group="/docker/test" -e ARANGO_RANDOM_ROOT_PASSWORD=1 -e ARANGO_STORAGE_ENGINE=rocksdb arangodb/arangodb:3.5.2 --log.level queries=warn --log.level performance=warn --rocksdb.block-cache-size 256MiB --rocksdb.enforce-block-cache-size-limit true --rocksdb.total-write-buffer-size 256MiB --cache.size 256MiB

Why does the memory keeps increasing and does not go down, especially when it is not being used?
Expected result:

Hi @nicolaselkhoury,
can you provide any logs that can help us to understand the issue better?
Also note that 256MB for cache, write buffers etc. is not a lot. If statistics are enabled in the server, then it's not uncommon that memory usage increases over time. Please take a look here for some options to decreasing memory usage: https://www.arangodb.com/docs/stable/tutorials-reduce-memory-footprint.html

Hi,
Thank you for answering me. Unfortunately, there exists no logs before Arango crashing. I monitored the container's memory consumption using the ATOP tool. While monitoring, I could see the memory consumed by the container incrementally increasing, until the container finally crashes and restarts, and then the memory decreases.
I understand that if statistics are enabled, then the memory usage will increase over time, but I would like to limit the memory consumption somehow and forbid Arango from continuously eating up memory. How can I do that?
Moreover, why do these commands, which I use when starting the Arango process not work?
--rocksdb.block-cache-size 256MiB --rocksdb.enforce-block-cache-size-limit true --rocksdb.total-write-buffer-size 256MiB --cache.size 256MiB

The StackOverflow answer is about a configuration file parsing issue (#5414) which was fixed in 3.3/3.4, so it should not matter here. But it could still be worth to check whether the options you specified are actually handed through correctly: https://www.arangodb.com/docs/stable/administration-configuration.html#fetch-current-configuration-options
You say the container RAM limit is 1.2GB. Block cache + write buffers + cache alone make up least 768MiB. But the server executable, data files etc. are also resident in memory, so it could well be that arangod honors the memory limiting options, but because of other things that are loaded into memory you might exceed the RAM limit very quickly. Keep in mind that intermediate and final query results require memory. You might want to set a memory limit for queries: --query.memory-limit
There are also other options which you are not using so far (see https://www.arangodb.com/docs/stable/tutorials-reduce-memory-footprint.html), for example:
--rocksdb.max-total-wal-size
--rocksdb.dynamic-level-bytes
You may also try to disable statistics to see how that changes the observed memory usage.
Make sure overcommit_memory is not set to 2 in your environment, or the server may get OOM killed way before memory is actually running out.

Hi @nicolaselkhoury,
Did you have a chance to read Simran's reply?
Was it helpful?

Hi @nicolaselkhoury,
Since we have not heard back from you recently, I am closing this issue for now.
Feel free to reopen this ticket if needed.


Fix formatting ActionController::Parameters

Add an extra check for unpermitted Rails paramters
that will report they they respond to :to_hash
but raise an error.
Fixes #17

OK, I had to run bundle exec appraisal rails-6.0 rspec to reproduce this new failure locally. It appears that with Ruby 2.7 and ActiveRecord 6.0.3 things have changed a bit. I have to see what's the best approach to handle this.


Does default request method change depending on the env?

I noticed something odd while trying to write a cron script.
Executing http "https://httpbin.org/anything" in our CLI does a GET request, while if I run that same command in a cron script, it becomes a POST request. Is this intentional?
( this can be replicated via sending a similar request to a path in https://requestb.in )
I noticed this on v0.9.4, then upgraded to v0.9.9 and the issue is still there.

You might need to use --ignore-stdin when invoking HTTPie from a cron job. Please see the docs for more details — https://httpie.org/doc#scripting.


Support for Polkadot v0.8.28

This PR adds support for two changes introduced in v0.8.28 (https://github.com/paritytech/polkadot/releases/tag/v0.8.28):

New MultiAddress enum (https://github.com/paritytech/substrate/pull/7380, https://github.com/paritytech/polkadot/pull/2126)
New 'providers' reference counter in the account store (https://github.com/paritytech/substrate/pull/7363, https://github.com/paritytech/polkadot/pull/2152)

A new MultiAddress class that takes the place and wraps the original Address is introduced. The BalanceTransfer and Extrinsic classes now contain a reference to a MultiAddress, and for backward compatibility, we keep setters that accept a plain Address instance.

Codecov Report

Merging #50 (5d09ba6) into master (b2d8775) will increase coverage by 0.13%.
The diff coverage is 94.44%.

@@             Coverage Diff              @@
##             master      #50      +/-   ##
============================================
+ Coverage     86.91%   87.04%   +0.13%
- Complexity      892      911      +19
============================================
  Files           115      118       +3
  Lines          2973     3034      +61
  Branches        430      438       +8
============================================
+ Hits           2584     2641      +57
  Misses          278      278
- Partials        111      115       +4

Impacted Files
Coverage Δ
Complexity Δ

.../io/emeraldpay/polkaj/scaletypes/MultiAddress.java
87.50% <87.50%> (ø)
2.00 <2.00> (?)

...in/java/io/emeraldpay/polkaj/scale/UnionValue.java
94.44% <87.50%> (-5.56%)
12.00 <7.00> (+7.00)
:arrow_down:

...a/io/emeraldpay/polkaj/scaletypes/AccountInfo.java
100.00% <100.00%> (ø)
17.00 <5.00> (+3.00)

...meraldpay/polkaj/scaletypes/AccountInfoReader.java
100.00% <100.00%> (ø)
2.00 <0.00> (ø)

.../emeraldpay/polkaj/scaletypes/BalanceTransfer.java
74.07% <100.00%> (+2.07%)
15.00 <1.00> (+1.00)

...ldpay/polkaj/scaletypes/BalanceTransferReader.java
100.00% <100.00%> (ø)
2.00 <0.00> (ø)

...ldpay/polkaj/scaletypes/BalanceTransferWriter.java
100.00% <100.00%> (ø)
3.00 <1.00> (+1.00)

...ava/io/emeraldpay/polkaj/scaletypes/Extrinsic.java
93.75% <100.00%> (+0.20%)
11.00 <0.00> (ø)

.../emeraldpay/polkaj/scaletypes/ExtrinsicReader.java
84.37% <100.00%> (ø)
2.00 <0.00> (ø)

.../emeraldpay/polkaj/scaletypes/ExtrinsicWriter.java
100.00% <100.00%> (ø)
3.00 <0.00> (ø)

... and 5 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b2d8775...5d09ba6. Read the comment docs.

@pablojorge sorry, totally missed the Pull Request. Just checked it, everything looks good, and I'm going to merge it now. Thank you!


The default project icon has ugly corners

Tested versions

System information

Issue description
The SVG looks fine, i think it's the editor doing some funny stuff to it.

Steps to reproduce

Minimal reproduction project (MRP)

Seems to be a problem with Godot.
Blazium left, Godot Right.

https://github.com/blazium-engine/blazium/pull/85 closed this issue


chore: release main

:robot: I have created a release beep boop
cache: 0.3.1
0.3.1 (2023-08-08)
Bug Fixes

tests: fix hanging test (#246) (b60c7f2)

codegen: 0.6.0
0.6.0 (2023-08-08)
Features

codegen: derive Block macro adds required trait bounds by default (#249) (892bef5)
codegen: insert appropriate bounds in Io, SchematicType, LayoutType proc macros (#251) (33dcc79)
macros: refactor macro reexports (#250) (a332717)

Dependencies

The following workspace dependencies were updated

dependencies

examples bumped from 0.2.0 to 0.3.0
type_dispatch bumped from 0.2.0 to 0.3.0

dev-dependencies

substrate bumped from <=0.5.0 to <=0.6.0
sky130pdk bumped from <=0.5.0 to <=0.6.0
spectre bumped from <=0.5.0 to <=0.6.0

config: 0.2.3
Dependencies

The following workspace dependencies were updated

dependencies

cache bumped from 0.3.0 to 0.3.1

diagnostics: 0.3.0
0.3.0 (2023-08-08)
Features

validation: create type for unvalidated SCIR library (#252) (1550a22)

examples: 0.3.0
0.3.0 (2023-08-08)
Features

codegen: insert appropriate bounds in Io, SchematicType, LayoutType proc macros (#251) (33dcc79)
macros: refactor macro reexports (#250) (a332717)

Dependencies

The following workspace dependencies were updated

dev-dependencies

substrate bumped from <=0.5.0 to <=0.6.0
sky130pdk bumped from <=0.5.0 to <=0.6.0
spectre bumped from <=0.5.0 to <=0.6.0

geometry: 0.4.0
0.4.0 (2023-08-08)
Features

macros: refactor macro reexports (#250) (a332717)

Dependencies

The following workspace dependencies were updated

dependencies

geometry_macros bumped from 0.0.0 to 0.0.1

geometry_macros: 0.0.1
Dependencies

The following workspace dependencies were updated

dependencies

type_dispatch bumped from 0.2.0 to 0.3.0

scir: 0.5.0
0.5.0 (2023-08-08)
Features

slices: use SliceOne instead of Slice where possible (#253) (8eba8ed)
validation: create type for unvalidated SCIR library (#252) (1550a22)

Dependencies

The following workspace dependencies were updated

dependencies

diagnostics bumped from 0.2.0 to 0.3.0

sky130pdk: 0.6.0
0.6.0 (2023-08-08)
Features

macros: refactor macro reexports (#250) (a332717)

Dependencies

The following workspace dependencies were updated

dependencies

substrate bumped from 0.5.0 to 0.6.0
spectre bumped from 0.5.0 to 0.6.0

spectre: 0.6.0
0.6.0 (2023-08-08)
Features

macros: refactor macro reexports (#250) (a332717)
slices: use SliceOne instead of Slice where possible (#253) (8eba8ed)

Dependencies

The following workspace dependencies were updated

dependencies

cache bumped from 0.3.0 to 0.3.1
scir bumped from 0.4.0 to 0.5.0
substrate bumped from 0.5.0 to 0.6.0

spice: 0.4.0
0.4.0 (2023-08-08)
Features

slices: use SliceOne instead of Slice where possible (#253) (8eba8ed)
validation: create type for unvalidated SCIR library (#252) (1550a22)

Dependencies

The following workspace dependencies were updated

dependencies

scir bumped from 0.4.0 to 0.5.0

spice_rawfile: 0.1.0
0.1.0 (2023-08-08)
Features

spice-rawfile: add SPICE rawfile parser (#254) (f42d45b)

substrate: 0.6.0
0.6.0 (2023-08-08)
Features

codegen: derive Block macro adds required trait bounds by default (#249) (892bef5)
codegen: insert appropriate bounds in Io, SchematicType, LayoutType proc macros (#251) (33dcc79)
macros: refactor macro reexports (#250) (a332717)
slices: use SliceOne instead of Slice where possible (#253) (8eba8ed)
testing: add test for terminal path API (#245) (de55691)
validation: create type for unvalidated SCIR library (#252) (1550a22)

Dependencies

The following workspace dependencies were updated

dependencies

config bumped from 0.2.2 to 0.2.3
examples bumped from 0.2.0 to 0.3.0
cache bumped from 0.3.0 to 0.3.1
codegen bumped from 0.5.0 to 0.6.0
geometry bumped from 0.3.0 to 0.4.0
scir bumped from 0.4.0 to 0.5.0
spice bumped from 0.3.0 to 0.4.0
type_dispatch bumped from 0.2.0 to 0.3.0

dev-dependencies

sky130pdk bumped from <=0.5.0 to <=0.6.0
spectre bumped from <=0.5.0 to <=0.6.0

tests: 0.0.0
Dependencies

The following workspace dependencies were updated

dependencies

geometry bumped from 0.3.0 to 0.4.0
substrate bumped from 0.5.0 to 0.6.0
scir bumped from 0.4.0 to 0.5.0
cache bumped from 0.3.0 to 0.3.1
spice bumped from 0.3.0 to 0.4.0
spectre bumped from 0.5.0 to 0.6.0
sky130pdk bumped from 0.5.0 to 0.6.0

type_dispatch: 0.3.0
0.3.0 (2023-08-08)
Features

codegen: insert appropriate bounds in Io, SchematicType, LayoutType proc macros (#251) (33dcc79)
macros: refactor macro reexports (#250) (a332717)

Dependencies

The following workspace dependencies were updated

dependencies

type_dispatch_macros bumped from 0.2.0 to 0.3.0

type_dispatch_macros: 0.3.0
0.3.0 (2023-08-08)
Features

macros: refactor macro reexports (#250) (a332717)

Dependencies

The following workspace dependencies were updated

dev-dependencies

type_dispatch bumped from <=0.2.0 to <=0.3.0

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/codegen-v0.6.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/config-v0.2.3 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/cache-v0.3.1 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/geometry-v0.4.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/scir-v0.5.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/spice-v0.4.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/spice_rawfile-v0.1.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/type_dispatch-v0.3.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/type_dispatch_macros-v0.3.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/sky130pdk-v0.6.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/substrate-v0.6.0 :sunflower:

:robot: Release is at https://github.com/substrate-labs/substrate2/releases/tag/spectre-v0.6.0 :sunflower:


ApiException only generated for the first *.json OpenApiReference

When NSwag.ApiDescription.Client generates the client .cs files it only generates the ApiException partial classes for the first of these.
Example of the CsProj file:
<ItemGroup>

    <OpenApiReference Include="Api1.OpenApi.json" Namespace="Project.Api1Client" />

    <OpenApiReference Include="Api2.OpenApi.json" Namespace="Project.Api2Client" />

    <OpenApiReference Include="Api3.OpenApi.json" Namespace="Project.Api3Client" />

  </ItemGroup>

Both ApiException and ApiException are only generated in Api1.OpenApiClient.cs withing the Project.Api1Client namespace. Both Api2.OpenApiClient.cs and Api3.OpenApiClient.cs do not have ApiException and ApiException in their respective namespaces

Potentially a wider .Net issue: here

The work around posted here: https://github.com/dotnet/aspnetcore/issues/18204#issuecomment-606281714 works.
This problem still happens in VS2022, hoping for a fix some day.


Remove some bootstrap css.

Next we can remove close class too after a bit of cleanup in another PR. Also,  it's prime time to work on #26990 and then we can soon delete the file.

Merged, thanks @amanagr!


DSD: Add Focus Managment On MultiSelect component

Fixes JIRA ticket 1289 and 1290
This PR does the following:

Adds focus management for after Apply or Close button is pressed in the Dialog MultiSelect
Adds focus management for after the count button is pressed on the MultiSelectMenuButton
Adds test for the new functionality
Fixes a style bug on MultiSelectGroup mobile

How has this been tested?

Accessibility concerns or updates

This PR should address the accessibility issue of focus loss after the MultiSelect component closes or the count button has been clicked. Now the focus should return to the MultiSelectMenuButton after any of these actions have been performed.

Checklist:

[ ] I have updated the Storybook documentation accordingly.
[ ] I have added relevant accessibility documentation for this pull request.
[x] All new and existing tests passed.

Front End Review:

[ ] Review the Vercel preview deployment once it is ready.

Good catch on the focus logic @EdwinGuzman! I decided on a check for the previous isOpen value to catch the first render. Since the onApply is not connected to the MenuButton logic I think this is the easiest way to get it to work when the "Apply" button is clicked.

Great!

@isastettler
Before this is merged into development, let me have Clare do an a11y review in the Vercel preview.  I'll let you know how it goes.

@isastettler
Before this is merged into development, let me have Clare do an a11y review in the Vercel preview. I'll let you know how it goes.

@isastettler
Clare also gives a 👍 on the updates.  Please go ahead and merge this PR into development.


soft-serve: 0.7.4 -> 0.7.6

Fixes #272128
Description of changes
https://github.com/charmbracelet/soft-serve/releases/tag/v0.7.5
https://github.com/charmbracelet/soft-serve/releases/tag/v0.7.6
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] 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/)
24.11 Release Notes (or backporting 23.11 and 24.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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This fixes CVE-2024−41956 which is a remote code execution vulnerability.


Trigger events on filled out input field

Some sites disable the submit button and check the username and password field to be modified. The input field checks need a "change" event to be triggered.

This is great, thanks @mintao !


Jupiter NoteBook

please make a jupiter notebook ... i have tried to get it working unsucessfully ... problem when loading the model .... the first parameter is :
merged_talk_heads=merged_talk_heads,
perhaps i have not correctly patch the transformers ?

hello

so bad :(


This only needs to be done once

when doing the manual, non root method to give permissions through adb, when it says it only needs to be done once, does this mean it needs to be done once but if the phone is restarted, or goes to the lockscreen, it kills it and needs to be done again the next time you use the app?
or is it persistent and doesn't need a connection to adb ever again, and can just read logs straight off the device?
(non root, android 10)

The adb permission granting does not work on newer androids. Or is there a way to enable this without rooting the phone?

adb permission is only once needed, it will stay until you take it away with adb.
And @muziker this works for me up to Android 12 with adb. Lowest was Android 7 where i did it with adb.
Enable USB debugging, type the adb command, open the app to confirm it works, disable USB debugging and enjoy.


TS import

When using:
import EventEmitter = require("wolfy87-eventemitter");

with:
{
  "compilerOptions": {
    "module": "commonjs",
    "target": "es6",
  }
}

I get
2 import EventEmitter = require("wolfy87-eventemitter");
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

src/bla.ts(2,1): error TS1202: Import assignment cannot be used when targeting ECMAScript 2015 modules. Consider using 'import * as ns from "mod"', 'import {a} from "mod"', 'import d from "mod"', or another module format instead.

2 import EventEmitter = require("wolfy87-eventemitter");

Unfortunately when doing:
import * as EventEmitter from "wolfy87-eventemitter";

I get
/Users/joscha/dev/xhr-mocklet/node_modules/ts-node/src/index.ts:307
        throw new TSError(formatDiagnostics(diagnosticList, cwd, ts, lineOffset))
              ^
TSError: ⨯ Unable to compile TypeScript
src/MockXMLHttpRequestUpload.ts (1,31): Module '"/Users/joscha/dev/xhr-mocklet/node_modules/wolfy87-eventemitter/EventEmitter"' resolves to a non-module entity and cannot be imported using this construct. (2497)
    at getOutput (/Users/joscha/dev/xhr-mocklet/node_modules/ts-node/src/index.ts:307:15)
    at /Users/joscha/dev/xhr-mocklet/node_modules/ts-node/src/index.ts:336:16
    at Object.compile (/Users/joscha/dev/xhr-mocklet/node_modules/ts-node/src/index.ts:498:11)
    at Module.m._compile (/Users/joscha/dev/xhr-mocklet/node_modules/ts-node/src/index.ts:392:43)

I am not 100% sure, but I think the types might not be defined in a compatible way to be used with the tsconfig options above - any ideas?

I'm afraid I've never seen that import / require syntax before and I don't know what the error means. I didn't add the TS definitions to this repository myself since I don't use it or intend to use it. Can you see anything wrong with the .ts file?
I won't be of much help here since I know far less about it than you do. Hopefully someone who knows more about TS can help us out if you're not sure.

Without further information, I don't think I can help here I'm afraid. Maybe try the version from Definitely Typed? (I think that's what it's called?...)


Example grammar proto3 does not accept enum fields starting from zero

Issue with proto3 example: Can not parse this simple proto-file
syntax = "proto3";

enum Error {
    hello = 0;
}

Reason: int_lit does not allow for a single zero, which is understandable for field numbers in messages, but field numbers in enum start at zero.
struct dec_lit : seq< range< '1', '9' >, star< digit > >  {};
struct int_lit : sor< hex_lit, oct_lit, dec_lit > {};
struct enum_field : ... ident, sps, equ, sps, int_lit, ...

A possible solution is to introduce enum_number that allows zero.
Ref: There must be a zero value, so that we can use 0 as a numeric default value
https://developers.google.com/protocol-buffers/docs/proto3#enum

I know that the grammar suffers from same issue.

So there was a bug in the original grammar that I copied into the PEGTL grammar. I'll change enum_field to use a new rule enum_int that uses enum_dec aka. plus< digit > instead of dec_lit.


How can I make my barcode have a transparent background?

you can do it like this: JsBarcode(image, { background: "" })


Minor update to implementors.md

Very low-priority, minor pull request that updates the "Implementing the OpenTracing APIs" page text a bit.  The changes are:
Split the text into two sections with headings. The rationale here was I initially clicked on the link to find information how to implement the OpenTracing APIs -- but then found text on why it's a good idea to do so. Both pieces of information are good and necessary, but I think the headings help as people may come to the page primarily for one purpose or the other.
Directly include a link to the GitHub repo. I assume this is the de-facto place to get information on the reference implementations :)
...and also I added some word-smithing that I think makes the content a little more clear (hopefully the improvement here isn't entirely subjective!).

thanks -- LG aside from the reference impl pointer.


MINOR: Remove TLS renegotiation code

This has been disabled since the start and since
it's removed in TLS 1.3, there are no plans to
ever support it.

Thoughts @rajinisivaram?

Merging to trunk.


fix(suggestion): correct regex construction

Very rookie mistake, oversaw a reFindAllSubmatches causing it to error out with certain prefixes.
Status

[x] Code changes have been tested on an instance of YAGPDB, or there are no code changes
[x] I have read and followed the contribution guide

Thanks again!

Thanks again!

No problem, my mistake!

No problem, my mistake!


Evaluate enforceGUIDInFileName for EmbeddedRootSource

Fixes #9665 #9738
Status
Tested, but limited to one TC and one SC workflow. Needs a more rigorous set of testes before merge.
Description
Enable enforceGUIDInFileName for supported releases of CMMSSW when EmbeddedRootSource is used. This fixes #9665.
Also, clean up logic for enabling the parameter for primary input data by doing a regex check of the first input file. Should prevent the parameter from being enabled for any workflow that uses a non-GUID compliant file name (we have seen this on StoreResults/StepChain). This part fixes #9738.
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
#9660 and #9468
External dependencies / deployment changes
Nope

So the cmsRun1 part worked, but when I looked for cmsRun2 logs I noticed the first step errors with:
2020-06-10 23:23:19,856:CRITICAL:CMSSW:Error running cmsRun
{'arguments': ['/bin/bash', '/srv/job/WMTaskSpace/cmsRun1/cmsRun1-main.sh', '', u'slc7_amd64_gcc820', 'scramv1', 'CMSSW', 'CMSSW_11_1_0_pre7', 'FrameworkJobReport.xml', 'cmsRun', 'PSet.py', '', '', '']}
Linux Return code: 137

2020-06-10 23:23:19,923:CRITICAL:CMSSW:Error message: None

Will need some further investigation.

Yep, tasks and steps are confusing, especially because there is an overloading of the step definition as well. Every single workflow has tasks and steps (objects), however, in a StepChain, the task is also called a (high level) step. Hopefully I didn't make it worse ;)
So, TaskChain does not have cmsRun2 step, thus I guess you're saying that your test workflow actually failed in the second Task. Can you please point me to the workflow name and where it has been injected?

Thanks for the explanation! I ran this workflow a couple times. On the second I decreased LumisPerJob to see if it would run any faster.
https://esg-dmwm-dev1.cern.ch/reqmgr2/fetch?rid=egough_TC_RelVal_PU_11_1_0pre7_reqmgr2_200610_164551_2076
https://esg-dmwm-dev1.cern.ch/reqmgr2/fetch?rid=egough_TC_RelVal_PU_11_1_0pre7_reqmgr2_200611_201738_4598
It looks like the vast majority of the jobs are successful. Currently only a 2% failure rate for one and 0% for the other. So I don't think there is an issue with the workflow or my changes overall.

@goughes Erik, are you going to seek the other approach (based on file name patterns) you suggested yesterday? Or would you like to have this PR reviewed and merged before you investigate the filename pattern?

@amaltaro My thinking now is that most of the code here would need to stay since I need a way to pass inputTypeAttrib from the pileup setup to handleEnforceGUIDInFilename. L655 will be the line that will change with my new filename pattern matching updates.

My changes broke a couple PSet unit tests which I will need to fix.

test this please

@amaltaro Fixed the unit tests, but I'm open to suggestions if you feel there is another way. Want to take another look here?

test this please


How to use cpu kernel of an operator (which provides only cpu implementation) in gpu context?

If a custom operator (written in c++) only provides cpu implementation, can it be used in gpu context where all other operators have gpu kernel? In Caffe this is straightforward, because when you call Blob's cpu_data() and mutable_cpu_data() it automatically syncs with gpu data.
Thank you.

How are the operator's forward and backward kernels implemented? By kernel, I mean the function block that does parallel computation such as this. In MXNet, most of the simple operators shares the same kernels between CPU and GPU. That's why there is a template argument called xpu in Forward and Backward function as this. If your cpu kernel also works for gpu and you defined Forward and Backward functions using xpu template argument, what you need to do is register the operator in a .cu file as this.
Sometimes, complicated operators do not share the same kernels for cpu and gpu as they have different parallelization approaches and each kernel has to be optimized against its own device.

@reminisce The cpu kernel is a complex algorithm that needs direct access to the raw cpu memory. Only cpu kernel is provided and I intend to use the cpu kernel in gpu context (like caffe, which uses cpu kernel when no gpu kernel is provided, and cpu_data() can automatically sync with gpu data).

This issue is closed due to lack of activity in the last 90 days. Feel free to ping me to reopen if this is still an active issue. Thanks!
Also, do please check out our forum (and Chinese version) for general "how-to" questions.


(*BatchVerifier).Add arguments are the opposite of Verify

Verify(publicKey ed25519.PublicKey, message, sig []byte) bool
(v *BatchVerifier) Add(publicKey ed25519.PublicKey, sig, message []byte) bool

Note how Verify takes first the message and then the signature, while Add does the other way around.
This looks extremely error prone.
Indeed, BenchmarkVerifyBatch itself is using the function wrong, but still passes because it does not check the return value of Add. This also means that all benchmarks are testing a batch size of 0.
v.Add(pub, msg, ed25519.Sign(priv, msg))

As an API safety note, I think Verify should be documented to return false on a batch of size zero. Also, Add should return an error value to give a chance to errcheck-like linters to catch the fact that the error is not handled. Actually, it should not return anything and defer all results to Verify, so that if invalid inputs are inserted in the batch, Verify will fail. This is too big of a footgun, and if people want to optimize for malformed signatures they can just implement the length check themselves.
Since swapping the arguments is not going to break the API, I would recommend intentionally introducing a backwards-incompatible change, so that there aren't two compatible versions that work very differently. For example you could rename VerifyBatch to Verify, since BatchVerifier.VerifyBatch is redundant anyway.
P.S. I don't think Verify should purge the batch. There is no expensive resource to reuse, it's not documented, and it's a footgun: I would expect two sequential Verify operations to return the same value.
	// purge BatchVerifier for reuse
	v.entries = []ks{}

Thanks for flagging this! It sounds like the best thing would be to:

[ ] fix the order of arguments in Add;
[ ] made Add infallible, deferring failures to the batch verification;
[ ] rename BatchVerifier.VerifyBatch to BatchVerifier.Verify;
[ ] make Verify idempotent.


Feature routing

Hi @gulsher7, thanks for your contribution.
I have reviewed your code, and you did a great job 👍🏼
However, I get two errors on the animateToRoute function (see attached image)
I fixed them by changing the animation declaration to this:
let animation: MapCameraAnimation = MapCameraAnimationFactory.createAnimation(
            from: update,
            duration: TimeInterval(1),
            easingFunction: EasingFunction.inCubic)

Please change it on your side and let me know if it works.
another thing is that I want you to format the code using the shortcut ctrl*i on xcode, just to have a unified formatting of the code :)
And as we discussed, I'll work on the Android side and publish a new version soon.
Thank you for your time and efforts :)

@gulsher7 and about your concern for the performance implications of calling updateFeature on every didSet of the Routing component. I also agree that it could affect the performance, but not calling it Makes the Routing component not respond to changes on the JS side. on android there is a function called onAfterUpdateTransaction that I use to wait until all the props are updated then call updateFeature, but I'm not sure if there's a similar function on iOS

Hi @gulsher7, thanks for your contribution. I have reviewed your code, and you did a great job 👍🏼
However, I get two errors on the animateToRoute function (see attached image) I fixed them by changing the animation declaration to this:
let animation: MapCameraAnimation = MapCameraAnimationFactory.createAnimation(
            from: update,
            duration: TimeInterval(1),
            easingFunction: EasingFunction.inCubic)

Please change it on your side and let me know if it works. another thing is that I want you to format the code using the shortcut ctrl*i on xcode, just to have a unified formatting of the code :)
And as we discussed, I'll work on the Android side and publish a new version soon.
Thank you for your time and efforts :)

Hey, i'm not getting this error at my side, could yo please verify the here map sdk version i'm using <IP_ADDRESS>.103798-release version

I'm using HERE navigate version <IP_ADDRESS>.105808-release:
sdk version==>> SDKVersion(productVariant: "explore", versionName: "<IP_ADDRESS>.105808-release", versionGeneration: 4, versionMajor: 18, versionMinor: 2, versionPatch: 0, versionBuild: 105808, versionTag: "release", backendConfig: "PRD")

I guess the error above is due to a version mismatch. If I use the code you provided, it gives me a deprecated warning

i'm using explore sdk

Yes, your right. I cleared the Pod file and re-instantiated it, and it now works.


[struct_pack] struct_pack::deserialize_to args order

Search before asking

[ ] I searched the issues and found no similar issues.

What happened + What you expected to happen
The example shows:
person p3;
auto buffer = struct_pack::serialize(p.age, p2.name);
[[maybe_unused]] auto result =
    struct_pack::deserialize_to(p3.age, buffer, p3.name);

Why not struct_pack::deserialize_to(buffer, p3.age, p3.name)?
Reproduction way
Anything else
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Well, The old version of struct_pack don't support template variadic parameter.
Normally, the first parameter is target, and the second parameter is source.
struct_pack::deserialize_to(target /*object*/, source /*data*/);

However, when we try to support variadic parameters, we found some problem. If you want to deduce variadic template automatically, the  variadic parameters should be the last parameter. That's why we use such strange args order.

Well, The old version of struct_pack don't support template variadic parameter. Normally, the first parameter is target, and the second parameter is source.
struct_pack::deserialize_to(target /*object*/, source /*data*/);

However, when we try to support variadic parameters, we found some problem. If you want to deduce variadic template automatically, the variadic parameters should be the last parameter. That's why we use such strange args order.

Thanks for the explanation.


Missing AMDX info for Defender/PUAProtection

Defender/PUAProtection information does not include ADMX settings, however the AMDX templates suggest that an equivalent configuration item exists that has matching options/values...
AMDX.xml
<policy name="Root_PUAProtection" class="Machine" displayName="$(string.Root_PUAProtection)" explainText="$(string.Root_PUAProtection_Explain)" key="Software\Policies\Microsoft\Windows Defender" valueName="PUAProtection" presentation="$(presentation.Root_PUAProtection)">
    <parentCategory ref="AntiSpywareDefender" />
    <supportedOn ref="windows:SUPPORTED_Windows_10_0_RS1" />
    <elements>
        <enum id="Root_PUAProtection" valueName="PUAProtection" required="true">
            <item displayName="$(string.ExploitGuard_ControlledFolderAccess_EnableControlledFolderAccess_Disable)">
                <value>
                    <decimal value="0" />
                </value>
            </item>
            <item displayName="$(string.ExploitGuard_ControlledFolderAccess_EnableControlledFolderAccess_Block)">
                <value>
                    <decimal value="1" />
                </value>
            </item>
            <item displayName="$(string.ExploitGuard_ControlledFolderAccess_EnableControlledFolderAccess_Audit)">
                <value>
                    <decimal value="2" />
                </value>
            </item>
        </enum>
    </elements>
</policy>

AMDL.xml
<string id="Root_PUAProtection">Configure detection for potentially unwanted applications</string>
<string id="Root_PUAProtection_Explain">
        Enable or disable detection for potentially unwanted applications. You can choose to block, audit, or allow when potentially unwanted software is being downloaded or attempts to install itself on your computer.

        Enabled:
        Specify the mode in the Options section:
        -Block: Potentially unwanted software will be blocked.
        -Audit Mode: Potentially unwanted software will not be blocked, however if this feature would have blocked access if it were set to Block, then a record of the event will be in the event logs.

        Disabled:
        Potentially unwanted software will not be blocked.

        Not configured:
        Same as Disabled.
</string>

Policy CSP - Defender - Windows Client Management
Defender/PUAProtection

Added in Windows 10, version 1607. Specifies the level of detection for potentially unwanted applications (PUAs). Windows Defender alerts you when potentially unwanted software is being downloaded or attempts to install itself on your computer.

The following list shows the supported values:

0 (default) – PUA Protection off. Windows Defender will not protect against potentially unwanted applications.
1 – PUA Protection on. Detected items are blocked. They will show in history along with other threats.
2 – Audit mode. Windows Defender will detect potentially unwanted applications, but take no action. You can review information about the applications Windows Defender would have taken action against by searching for events created by Windows Defender in the Event Viewer.

Documentation should include the following for Defender/PUAProtection...

ADMX Info:

GP English name: Configure detection for potentially unwanted applications
GP name: Root_PUAProtection
GP element: Root_PUAProtection
GP path: Windows Components/Microsoft Defender Antivirus
GP ADMX file name: WindowsDefender.admx

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

ID: 66b1ab2e-1964-5580-7c99-4bd4cd480075
Version Independent ID: f7b5da46-04cb-3501-65fa-870a3c6f09b8
Content: Policy CSP - Defender - Windows Client Management
Content Source: windows/client-management/mdm/policy-csp-defender.md
Product: w10
Technology: windows
GitHub Login: @ManikaDhiman
Microsoft Alias: dansimp

@maxaxaxaxGit , Thanks for pointingout the missing information.
Now i am going to add the missing information to this article

(ref. PR #8744 )

Closing via #8744
Thank you

Closing via #8744
Thank you


maxxViT onnx export problem

Hi,
Have anybody encountered problem with exporting maxxViT model to onnx?
Model: maxxvit_rmlp_small_rw_256
Export code:
model = timm.create_model('maxxvit_rmlp_small_rw_256', pretrained = True, num_classes = 2)
state = torch.load('model_001.pth')]
model.load_state_dict(state['model'])
model.eval()

import torch.onnx
torch.onnx.export(model,
                 torch.rand(1, 3, 256, 256, requires_grad=True),
                 f"out_model.onnx",
                 export_params=True,
                 opset_version=10,
                 do_constant_folding=True,
                 input_names=['input'],
                 output_names=['output'],
                 dynamic_axes={'input': {0 : 'batch_size'}, 'output': {0 : 'batch_size'}})

Encountered error:
[/usr/local/lib/python3.7/dist-packages/torch/onnx/symbolic_helper.py](https://localhost:8080/#) in _onnx_unsupported(op_name)
    455         "Unsupported: ONNX export of operator {}. "
    456         "Please feel free to request support or submit a pull request on PyTorch GitHub.".format(
--> 457             op_name
    458         )
    459     )

RuntimeError: Unsupported: ONNX export of operator prim::ConstantChunk, unknown dimension size. Please feel free to request support or submit a pull request on PyTorch GitHub.

Modules:
timm: 0.7.0dev0
pytorch: 1.12.1+cu113

@rkinas can you try all opset ver supported in pt 1.12 and report if it's supported in newer ones, 10 is rather old.

Using the default opset version (13 I think) in pytorch 1.12 works fine, so try commenting the opset_version arg out in your export.... not sure what the lowest is, likely 11 or 12 as I think they made changes to chunking there...

Hi Ross,
Thank you for prompt answer. You are right - works great!


Heading (compass) calculation error or non-existing in Y-forward-X-up configuration

In our vehicle we need to place the BeagleBoard Blue in a configuration where forward is in the Y-direction and up is in the X-direction.
The MPU-library does not seem to support this configuration and it therefore fails to calculate the heading and compensate correctly for both roll, pitch and yaw.
I am using the newest image for the BeagleBone Blue along with the newest version (from git) of librobotcontrol.
Would there be any chance that you could update the libraries to support this, or provide us with instructions how to and then we could submit a PR?
Additionally we have observed at many occasions during the last year or so that the heading starts drifting (continuing going in circles) all of a sudden, and then needs a hard reboot to reset the IMU.
Is it possible to avoid or circumvent this when it happens?

I think the orientation you are looking for is the third option, X-UP. You are however right that the magnetometer orientation change was wrong, I fixed that just now in a03bf544d26f74836d8bac78e0d7aa0d3cfde807
I'd love to know more info on the drifting issue, random bugs are hard to track down and this isn't something I've been able to replicate myself.

@StrawsonDesign that was also how I fixed it. And then to use it as compass with Y-forward you futhermore have to multiply with -1 and subtract -90 deg from the result, such that heading becomes Wrap360(-1*data.compass_heading*Rad2Deg-90).
For roll and pitch you then have to grab data.fused_TaitBryan[TB_ROLL_Y]*Rad2Deg and data.fused_TaitBryan[TB_PITCH_X]*Rad2Deg, respectfully.
For heading, roll and pitch rate you have to grab -1*data.gyro[TB_YAW_Z], data.gyro[TB_ROLL_Y] and data.gyro[TB_PITCH_X].
Just clarifying for anyone else who might end up in this configuration (orientation of BB board).
In regards to the heading drift, this is something I have seen previously in Sparkfun 9-axis IMUs, which I guess is pretty much the same as the one in the robotics cape. From debugging then, it seemed that if the software utilising the IMU would be restarted several times and thereby re-initiating the IMU several times, the IMU would go crazy. Only fix I could come up with back then was to hard reboot the IMU. But this was only applied after I would have recognized the heading drift.

If they ever found a fix to detect this prior to catastrophic failure and then do a reboot by software, please let me know and share their experiences.
Thanks,
Jesper


Version 2.11 compatibility

phonebox_plugin fails to migrate to Netbox version 2.11.0.

Applying database migrations (python3 netbox/manage.py migrate)...
Traceback (most recent call last):
File "netbox/manage.py", line 10, in
execute_from_command_line(sys.argv)
File "/opt/netbox-2.11.0/venv/lib/python3.7/site-packages/django/core/management/init.py", line 419, in execute_from_command_line
utility.execute()
File "/opt/netbox-2.11.0/venv/lib/python3.7/site-packages/django/core/management/init.py", line 395, in execute
django.setup()
File "/opt/netbox-2.11.0/venv/lib/python3.7/site-packages/django/init.py", line 24, in setup
apps.populate(settings.INSTALLED_APPS)
File "/opt/netbox-2.11.0/venv/lib/python3.7/site-packages/django/apps/registry.py", line 114, in populate
app_config.import_models()
File "/opt/netbox-2.11.0/venv/lib/python3.7/site-packages/django/apps/config.py", line 301, in import_models
self.models_module = import_module(models_module_name)
File "/usr/lib/python3.7/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1006, in _gcd_import
File "", line 983, in _find_and_load
File "", line 967, in _find_and_load_unlocked
File "", line 677, in _load_unlocked
File "", line 728, in exec_module
File "", line 219, in _call_with_frames_removed
File "/opt/netbox-2.11.0/venv/lib/python3.7/site-packages/phonebox_plugin/models.py", line 2, in
from extras.models import ChangeLoggedModel, TaggedItem
ImportError: cannot import name 'ChangeLoggedModel' from 'extras.models' (/opt/netbox-2.11.0/netbox/extras/models/init.py)

I have the same issue after installing Netbox v2.11.
Unable to run these commands:
(venv) $ python3 manage.py migrate
(venv) $ python3 manage.py collectstatic
and I have to comment the plugin part in configuration.py otherwise nginx does not launch the Netbox web page

Thank you for your feedback and interest to the plugin.
I've just published a new release allow the plugin for NetBox 2.11+.
In my test NB 2.11.2 environment, all general test cases work without crashes.
Please try to upgrade the plugin. I will leave the issue opened for additional feedback for a while.

Can you please share the link of the updated plugin ?
Thank you
Regards
Téléchargez Outlook pour iOShttps://aka.ms/o0ukef

De : iDebugAll @.>
Envoyé : Wednesday, May 5, 2021 9:18:00 PM
À : iDebugAll/phonebox_plugin @.>
Cc : uc33260 @.>; Manual @.>
Objet : Re: [iDebugAll/phonebox_plugin] Version 2.11 compatibility (#3)
Thank you for your feedback and interest to the plugin.
I've just published a new release allow the plugin for NetBox 2.11+.
In my test NB 2.11.2 environment, all general test cases work without crashes.
Please try to upgrade the plugin. I will leave the issue opened for additional feedback for a while.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/iDebugAll/phonebox_plugin/issues/3#issuecomment-832944876, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AT6XQI7V7MSZ25JNAUWON2DTMGKWRANCNFSM43GB2P6Q.

@uc33260
This is already merged into the main branch here and published on PyPi.
Usual upgrade and install guidelines are relevant.

I upgraded to the new release, that's working fine now !
Thank you.
Does new features are scheduled for this plugin ? two features will be helpful to add:
Bulk add like for IP Address
Appearance in Tenant "Stats" dashboard to visualize the number of DID/internal numbers added for a tenant.

@uc33260

Does new features are scheduled for this plugin ?

Yes, I'm planning some enhancements for the plugin, including some relations between Numbers, Devices, and Voice Circuits.
Probably some IPAM Prefix analog for Numbers would also be helpful.
Feel free to open the issue marked as [Feature Request] if you have some ideas and use cases that might be interesting to the community.

Bulk add like for IP Address

This is already implemented. There is an 'Import' button in the right top corner of the Numbers page.
It leads to /plugins/phonebox/import_numbers/ page with a CSV bulk import form of a similar format.

Appearance in Tenant "Stats" dashboard to visualize the number of DID/internal numbers added for a tenant.

This ability might be limited from the plugins code. They do allow to extend some of the NetBox sections, but I should check if you can do this for Tenants.

Got that at migrate
Traceback (most recent call last):   File "manage.py", line 10, in <module>     execute_from_command_line(sys.argv)   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 419, in execute_from_command_line     utility.execute()   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/core/management/__init__.py", line 413, in execute     self.fetch_command(subcommand).run_from_argv(self.argv)   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/core/management/base.py", line 354, in run_from_argv     self.execute(*args, **cmd_options)   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/core/management/base.py", line 398, in execute     output = self.handle(*args, **options)   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/core/management/base.py", line 89, in wrapped     res = handle_func(*args, **kwargs)   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/core/management/commands/migrate.py", line 75, in handle     self.check(databases=[database])   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/core/management/base.py", line 423, in check     databases=databases,   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/core/checks/registry.py", line 76, in run_checks     new_errors = check(app_configs=app_configs, databases=databases)   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/core/checks/urls.py", line 13, in check_url_config     return check_resolver(resolver)   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/core/checks/urls.py", line 23, in check_resolver     return check_method()   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/urls/resolvers.py", line 412, in check     for pattern in self.url_patterns:   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/utils/functional.py", line 48, in __get__     res = instance.__dict__[self.name] = self.func(instance)   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/urls/resolvers.py", line 598, in url_patterns     patterns = getattr(self.urlconf_module, "urlpatterns", self.urlconf_module)   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/utils/functional.py", line 48, in __get__     res = instance.__dict__[self.name] = self.func(instance)   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/django/urls/resolvers.py", line 591, in urlconf_module     return import_module(self.urlconf_name)   File "/usr/lib/python3.7/importlib/__init__.py", line 127, in import_module     return _bootstrap._gcd_import(name[level:], package, level)   File "<frozen importlib._bootstrap>", line 1006, in _gcd_import   File "<frozen importlib._bootstrap>", line 983, in _find_and_load   File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked   File "<frozen importlib._bootstrap>", line 677, in _load_unlocked   File "<frozen importlib._bootstrap_external>", line 728, in exec_module   File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed   File "/opt/netbox-2.11.4/netbox/netbox/urls.py", line 8, in <module>     from extras.plugins.urls import plugin_admin_patterns, plugin_patterns, plugin_api_patterns   File "/opt/netbox-2.11.4/netbox/extras/plugins/urls.py", line 28, in <module>     urlpatterns = import_object(f"{plugin_path}.urls.urlpatterns")   File "/opt/netbox-2.11.4/netbox/extras/plugins/utils.py", line 31, in import_object     spec.loader.exec_module(module)   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/phonebox_plugin/urls.py", line 2, in <module>     from . import views   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/phonebox_plugin/views.py", line 5, in <module>     from . import filters   File "/opt/netbox-2.11.4/venv/lib/python3.7/site-packages/phonebox_plugin/filters.py", line 2, in <module>     from utilities.filters import BaseFilterSet, TagFilter ImportError: cannot import name 'BaseFilterSet' from 'utilities.filters' (/opt/netbox-2.11.4/netbox/utilities/filters.py)
Python version: 3.7.3
NetBox version: 2.11.4


agent v0.1.4 release + better defaults

There are some failed tests, though. ImgPullBackoff... probably wrong image

There are some failed tests, though. ImgPullBackoff... probably wrong image

looks like in the tests here, we never actually tested kedify images but it was still on kedacore...


Running pully giving Error: Cannot find module 'm3u8stream/lib/parse-time' error

Just freshly installed pully and seeing this error:
$ pully
internal/modules/cjs/loader.js:957
    throw err;
    ^

Error: Cannot find module 'm3u8stream/lib/parse-time'
Require stack:
- /usr/local/lib/node_modules/pully/node_modules/ytdl-core/lib/index.js
- /usr/local/lib/node_modules/pully/node_modules/pully-core/dist/index.js
- /usr/local/lib/node_modules/pully/dist/index.js
- /usr/local/lib/node_modules/pully/dist/bin/pully.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:954:17)
    at Function.Module._load (internal/modules/cjs/loader.js:847:27)
    at Module.require (internal/modules/cjs/loader.js:1016:19)
    at require (internal/modules/cjs/helpers.js:69:18)
    at Object.<anonymous> (/usr/local/lib/node_modules/pully/node_modules/ytdl-core/lib/index.js:7:21)
    at Module._compile (internal/modules/cjs/loader.js:1121:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1160:10)
    at Module.load (internal/modules/cjs/loader.js:976:32)
    at Function.Module._load (internal/modules/cjs/loader.js:884:14)
    at Module.require (internal/modules/cjs/loader.js:1016:19) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/usr/local/lib/node_modules/pully/node_modules/ytdl-core/lib/index.js',
    '/usr/local/lib/node_modules/pully/node_modules/pully-core/dist/index.js',
    '/usr/local/lib/node_modules/pully/dist/index.js',
    '/usr/local/lib/node_modules/pully/dist/bin/pully.js'
  ]
}

Any suggestions on how to fix?
macOS 10.15.2
npm 6.13.4
node 13.2.0

My guess is that's an error in ytdl-core. @fent Do you have any insight on this?

this was an error in ytdl-core <= v1.0.0, it was fixed in v1.0.1

$ ytdl --version
1.1.0

I've also tried running:
$ npm install -g ytdl-core@latest

+<EMAIL_ADDRESS>updated 1 package in 0.441s

I'm still getting the same error though. How can I ensure I'm using the fixed version of ytdl-core?

Feel free to make a PR updating pully. I can test it later today and release it to npm.

@ACyphus Just a guess, but try navigating to your global node_modules directory and find pully. Within there try running npm i ytdl-core@latest. Then run the pully command.

Feel free to make a PR updating pully. I can test it later today and release it to npm.

I'm not super familiar with node. I'm presuming this requires updating the ytdl-core dependency in pully-core? https://github.com/jimbuck/pully-core/blob/master/package.json#L38

@ACyphus Just a guess, but try navigating to your global node_modules directory and find pully. Within there try running npm i ytdl-core@latest. Then run the pully command.

$ npm i ytdl-core@latest
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@ffmpeg-installer/linux-arm):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"linux","arch":"arm"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@ffmpeg-installer/linux-arm64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"linux","arch":"arm64"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@ffmpeg-installer/linux-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"linux","arch":"ia32"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@ffmpeg-installer/linux-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"linux","arch":"x64"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@ffmpeg-installer/win32-ia32):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"win32","arch":"ia32"} (current: {"os":"darwin","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/@ffmpeg-installer/win32-x64):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"win32","arch":"x64"} (current: {"os":"darwin","arch":"x64"})

+<EMAIL_ADDRESS>updated 1 package and audited 192 packages in 3.03s
found 0 vulnerabilities

I still get the same error when running pully though.

@ACyphus Thanks for trying that. I should have some time tonight (6'ish hours from now) to update the references on everything and test it all. I'll post any updates here.

Thanks @jimbuck ✨ absolutely no rush from my side by the way

Just FYI, this is still on my mind, I will take a stab at it tonight.

pully-core is now updated. Working on updating pully next.

er I don't even know what pully is but I have a browser extension that uses ytdl-core and apparently updating to the latest version (which is a new major) solved the issue for me

I still have the same error, tried installing the latest ytdl but this gave me the same warning messages as @ACyphus.

$ ytdl --version
1.1.0

I've also tried running:
$ npm install -g ytdl-core@latest

+<EMAIL_ADDRESS>updated 1 package in 0.441s

I'm still getting the same error though. How can I ensure I'm using the fixed version of ytdl-core?

don't install a node library globally. node will prioritize local modules over global ones.
if you want to debug this more, look at your package-lock.json file and see any entries for ytdl-core and what is requiring an older version, if anything.

Temporary fix.
cp -r ./node_modules/m3u8stream/dist ./node_modules/m3u8stream/lib

if you want to debug this more, look at your package-lock.json file and see any entries for ytdl-core and what is requiring an older version, if anything.

running with npx, how do fix this

in /node_modules/ytdl-core/lib/index.js change 'm3u8stream/lib/parse-time to 'm3u8stream/dist/parse-time

I think the latest tag reference a version that depends on the 0.7.2 release of pully-core which depends on the 0.28.0 release of ytdl-core, which incorrectly references m3u8stream/lib/parse-time instead of m3u8stream/dist/parse-time.
Could this mean that anyone who installs pully using npm i pully will get a broken version? That's what happened to me, but I don't know for sure.
Is the solution to create a new tag that references a version of pully that has the up to date dependencies?


PLA or ASA

Hi there,
willing to print but concerned about temperatures.
Some of my device get quite hot and I don't think PLA will hold it.
Anyone printing this in ASA?
Any major hints to consider?

I've got a set of four Minisforum MS-01's in a customized build printed entirely in PLA. The metal cases get a little warm, but not heat bed warm, so I'm worried about that. The one concern I have is the CPU fan exhaust, but so far it doesn't seem to be an issue. Granted these machines aren't under load that often.
We'll see how it holds up, but right now I have no concerns with PLA for these machines.

I've been using PLA and PETG with excellent results. Also, given the addition of the 120mm fan trays for additional cooling power, you may not need to worry about thermal thresholds as much anymore.


[HBASE-28142] Region Server Logs getting spammed with warning when st…

…orefile has no reader : Changing warn level log to debug level in HStore

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 19s
Docker mode activated.

Thank you @anchal246 for raising your first PR in Apache HBase. Welcome to the team :)
Will merge this to brnach-2.6+ by EOD.