Missing ["diagnosis"] key in the crash report information

Describe the bug
Previously before the version rc-2, most of the crashes captured, will have diagnosis info on what is going on and what are the exceptions, however after upgrading to rc-2, the whole structure changed and the framework did not capture anything useful from crash occured. After upgrading to rc-2, there are some API breaking changes and I managed to migrate to the new version.
Is there anything I missed out?
Currently it is hard to identify what are the changes from each version as there is no changelogs. Can anyone please help?
Version
KSCrash pod 'KSCrash', '2.0.0-rc.2'
XCode 16
macOS Sequioa 15.1
Code snippets

        // AppDelegate.swift
        let kCrashInstallation = KSCrash.shared
        let config = KSCrashConfiguration()
        config.deadlockWatchdogInterval = 0
        config.reportStoreConfiguration.maxReportCount = 5
        config.monitors = [.all]

        do {
            try kCrashInstallation.install(with: config)
        }
        catch {}

        // Other file
        var allCrashReports = [CrashReportDictionary]()
        let kCrashInstallation = KSCrash.shared
        let crashReportFilterJSONEncode = CrashReportFilterJSONEncode()

        if let unsentReports = kCrashInstallation.reportStore?.reportIDs {
            if unsentReports.count > 0 {
                for reportID in unsentReports {
                    if let dictionaryReport = kCrashInstallation.reportStore?.report(for: reportID.int64Value) {
                        allCrashReports.append(dictionaryReport)
                    }
                }
            }
            crashReportFilterJSONEncode.filterReports(allCrashReports) { filteredReports, error in
                if filteredReports != nil {
                    for case let (index,  report as CrashReportData) in filteredReports!.enumerated() {
                        if report.isKind(of: CrashReportData.self) {
                            do {
                                let json = try JSONSerialization.jsonObject(with: report.value, options: [])
                                if let jsonObject = json as? NSDictionary {
                                    if let crashObject = jsonObject["crash"] as? NSDictionary {
                                        if let crashDiagnosis = crashObject["diagnosis"] {
                                            crashInfo = "\(crashDiagnosis)\n"
                                        }
                                        else {
                                            if let exceptionName = (crashObject as NSDictionary).value(forKeyPath: "error.mach.exception_name") {
                                                crashInfo = "Exception name - \(exceptionName)\n"
                                            }
                                        }
                                    }
                                    if let systemObject = jsonObject["system"] as? NSDictionary {
                                        appVersion = "App Version \(systemObject["CFBundleShortVersionString"] ?? "UNAVAILABLE")(\(systemObject["CFBundleVersion"] ?? "UNAVAILABLE")) \n"
                                        buildVersion += "OS \(systemObject["system_version"] ?? "UNAVAILABLE")"
                                    }
                                }
                            }
                            catch {
                                logger.error("KCrash JSONSerialization failed")
                            }
                        }
                    }
                }
            }
        }

Steps to reproduce

Just trigger any crash

Crash report or stack trace
No response
KSCrash version
rc-2
Operating System
iOS
OS version
iOS 17 - 18
Device model
No response
Xcode version
16.1
Additional context
No response

Hi @avjiang!
Thanks for the details. Here is the main suggestion to help address your issue:
Diagnosis Missing: The missing diagnosis information is likely due to configuration changes. The KSCrashReportFilterDoctor is now a filter that needs to be explicitly applied. To include diagnosis information, make sure to use it like any other filter. You can check the logic for the diagnosis filter here.
Here are some additional recommendations:

Release Version: You're currently using rc-2, which might be causing some issues. I suggest trying the latest version rc-7, which can be found here. The newer release may contain fixes for the problems you're experiencing with diagnosis data not being captured.

Changelog: You mentioned having trouble identifying changes between versions. There is a changelog available on the releases page, which should help clarify what has changed and guide your migration.

Migration Guide: It sounds like you're having trouble with the API changes after upgrading to rc-2. The report structure itself hasn't changed much, with only some new fields being added. The breaking changes are mainly in the API, and you can find more details in the migration guide here. Reviewing this guide should help ensure you've accounted for all necessary changes.

Field Names: To avoid any typos or issues with renamed fields, I recommend referring to the field names in the header file KSCrashReportFields.h. This will help maintain consistency in your crash report handling.

Let me know if these suggestions help resolve your issue, or if you need more detailed assistance with the migration.

hi @GLinnik21 !
Thank you so much for the information! Really appreciate it. I will try to adjust the things following what you have mentioned. Will temporarily close this issue for now.
Cheers!


Allow player to restart with space instead of refreshing the page

@sdegueldre looks goode to me! :+1: Thank you for your contribution!


not work in almalinux 9.5

i get this error:
warning: Signature not supported. Hash algorithm SHA1 not available.
error: https://repo.almalinux.org/almalinux/RPM-GPG-KEY-AlmaLinux: key 1 import failed.
No match for argument: kmod-wireguard
No match for argument: wireguard-tools
No match for argument: qrencode
No packages marked for removal.
Dependencies resolved.
Nothing to do.

I think this is because AlmaLinux 9.5 is too new, I haven't test it myself but will test is in VM next.
You can play with https://github.com/xiahualiu/wg_gaming_installer/blob/main/install.sh#L107-L112 and see if anything wrong with it. I don't know but it seems the OS is too new so many packages are missing now.

I have made a fix for this issue. Can you try #31 branch to see if it works?
git clone https://github.com/xiahualiu/wg_gaming_installer.git
cd ./wg_gaming_installer
git switch issue_30
./install.sh

Thank you for your fix.
installed without problem.


Setting to Restore Earlier Display of Journal Notes in Tree View

Please select if your request is either something new or an enhancement

[X] Enhancement of an existing Feature.
[ ] Request of a new feature.

Please select the area your request applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[ ] Workspace - VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup - Dendron's Lookup Command
[X] Views - Dendron Preview, Tree View, Side Panels in the UI
[ ] Schema - Dendron Schemas
[ ] Pod - Data import from / export to Dendron
[ ] Publish - External Site Publish
[ ] Markdown - Markdown features, such as syntax support and features

Is your feature request related to a problem? Please describe
As of Dendron 0.90, the presentation of journal notes in the Tree View as changed. Prior to this version, only the "day" portion of the note's title was displayed in the Tree View. For a note with the title frontmatter field of "2022-04-12", this would render in the Tree View as:
>2022
  >04
    12

As of Dendron 0.90, the full title is displayed:
>2022
  >04
    2022-04-12

While displaying the full title in the Tree View makes sense for most notes, for journal notes specifically, the information is superfluous, as the year and month is already presented in the above hierarchical levels.
Describe the solution you'd like
That there be an option to change the way journal notes are displayed in the Tree View to only show the day portion of the note's title, and to hide the year and month.
Describe alternatives you've considered
Do not think there is a real alternative here. There is the option for the very dedicated user to go through all of their journal notes and manually change the title frontmatter field, but for anyone with a journal spanning multiple years worth of entries, they would have to be quite the dedicated user indeed.

To be clear, I am not against the note titles being used in the Tree View instead of the file names. I am in agreement that for most cases, the note title is probably more descriptive.
My issue is—as stated above—that in the case of journal notes specifically, the information is superfluous. The year and month are now displayed twice, first as part of the hierarchy and again as part of the note title.
Looking at your suggestions above, @aleksey-rowan, it occurs to me that option 3:
"an additional metadata item in notes (something like label) that would control what is displayed in the tree view; if label is not set, it could default to either file name or title"
Might already have been met without the need for introducing a new frontmatter field. Is this something that can be tied to Note Traits?
Every journal note already has the traitID journalNote associated with it. I do not want to ask for the impossible if such a thing cannot be done, but if it is possible to influence the behavior of the Tree View via note frontmatter, then tying the setting to Note Traits seems more straightforward. That way all notes of a certain category would behave as desired, as opposed to working through notes individually to add an additional frontmatter field.

hey @micharris42 thank for the report.
As @aleksey-rowan pointed out, V1 (used to) labeled the tree items derived from the file name and V2 explicitly labeled them with the note titles.
This caused confusion with V1, because tree items were sorted with title, but labeled with file name. (specifically, because uppercase alphabets came before underscore, but you would imagine that prepending an underscore would bubble up the item to the top), so V1's labelling has been changed to be with titles as well.
The problem described here also comes from the fact that creating a journal note now will apply the journal note trait, and will add the full yyyy-mm-dd timestamp as a title, whereas in the past, it would have set the title as simply dd.
We are currently fixing various issues and polishing up V1 in preparation of deprecating treeview V2, so this enhancement makes sense. Though, in the spirit of iteration, we would probably start by associating the tree view labeling to the trait, and not make the labelling configurable for now.
@jonathanyeung At first glance labeling tree item differently for notes with journal trait seems trivial. Is there anything else I'm blanking here that I should be aware of?

@micharris42 I'm also not note title being used in the tree--they are great and I agree that they are preferable in most cases.
I wanted to point out that Dendron heavily relies on file names for lookup and all other note manipulations, and replacing file name with titles in the tree will obscure these file names; also, since this change affects not only journal notes, we should think how non-journal notes will be affected.
@hikchoi Would labeling notes with based on traits expandable to other traits (and maybe customizable by the users)? If note traits are used to specify how the note should render in the tree, then maybe a generic render-as-file-name-in-tree trait is needed that can be applied to any note, not only a journal one.
What if instead of relying on note traits, this label behaviour (title or file name) is specified in the schema for that hierarchy? Placing that bit of configuration there would be consistent with schemas defying note hierarchies.

@aleksey-rowan
Thank you for the insights. There are a lot of ways to approach this, and we would need some time to have it specced out.
The main concern I have is that what we use to sort and what we use to label may not match when this is configurable. Locking a display method to the a sort method would alleviate that, but would also feel restricting for some. Ideally we would come up with an intuitive presentation of both sorting method and labelling method so that it doesn't create false expectations.

Yes, I didn't even think about the sorting and how it will be affected by the different labels shown in the tree view. That's a whole new can of worms and I do agree that this needs to be well specked out and maybe you might want to consider reversing the change while this is happening. It is a big change after all, without an option to get the old behaviour back.
I was also thinking about possible sorting options and I realized that I want a custom sort most of all. Yes, sorting by date and title/file name is a great feature, but I also want to arrange my hierarchies in the order I want without having to prepend them with number or other characters. I feel like most note-taking apps will let you order your notes in whatever way you want (I only checked OneNote, Notion, Evernote and Obsidian) and usually they let you override it and re-sort notes (date, name, etc.) at a single level.
In essence, I only want automatic sort for journal/meeting notes and for everything else I either don't care about the order or custom order is what I want.
The above should be a separate issue in itself. Apologies for rambling.
@hikchoi @micharris42
As for the issue at hand, maybe instead of messing with Tree View nodes and how they are rendered, it will be easier to allow customization of the title metadata value of journal notes in dendron.yml. It's already possible to customize the filename of the journal notes through the dateFormat: y.MM.dd config option. So, adding another option (titleFormat) to template the title shouldn't be something unimaginable. But then again, you can't add a config option to every single thing :/
Then I thought that I should be able to just use the journalNote trait to modify the note's title on creation to use the old dd, but it looks like it's a special trait and cannot be modified or overwritten right now:

https://github.com/dendronhq/dendron/issues/1911
https://github.com/dendronhq/dendron/issues/2211

These last two options seem to me the easiest I have, with the journal trait being more generic.

It seems there is quite a bit more breadth to this issue then I realized when I initially opened it.
Reading through the comments, it looks to me as though part of the trouble is deciding whether this should be a setting that affects notes en masse (either by Note Traits, Schemas, or some other alternative), or whether this should be a setting implemented per note. My preference is for the former, but I am sure there are plenty of users who would rather have a more granular level of control.
Ideally both methods could be implemented, and users could tweak the behavior of their notes however they like, but I do recognize that having two methods to achieve one goal is—arguably—introducing unnecessary complexity.
I think @hikchoi  had the right of it when they initially suggested the labeling not be made configurable for now. If journal notes are adjusted behind the scenes to be displayed in the Tree View as they were prior to Dendron 0.90, then the change is purely visual and should not require any change in how the notes actually work.
As the Note Traits feature (and Dendron itself) matures,  this could be made a configurable setting when a more intuitive method is possible, with the ultimate goal being @aleksey-rowan's request for a fully customizable sorting.

A little update on this issue.
To preserve the old behavior of labeling tree items with the note's filename, we decided to add a toggle button, and a configuration in dendron.yml that would set a default value that could switch between title labels and filename labels.
To avoid confusion with sorting, the label that is used to present the tree items will also be what the items will be sorted by.
We are ironing out the last bit of details, but this should go out within a week if no issues come up. I'll let you guys know when it gets released.

This has been released with a toggle menu that persist the setting across sessions. I'll close this issue.
Please let us know here or with a separate issue if you have any outstanding concerns.

@hikchoi, possibly I need to open a separate issue?
To be clear, I actually prefer the note titles being used in the Tree View instead of the file names. For most cases, the note title is probably more descriptive. If I have a note like scratch.my_imp_note, I think the Tree View displaying My Important Note is much more useful than my_imp_note.
I specifically singled out Journal Notes in this issue because I find them to be the one case where the note title is actually less useful. By default, Journal Notes are created with title frontmatter of year-month-day. As consequence, the year and month are displayed twice in the Tree View, first as part of the hierarchy and again as part of the note title. This is repetitive and even looks out of place.
Compare:
>2022
  >06
    08

To:
>2022
  >06
    2022-06-08

My preference would be that most notes in a Dendron vault be displayed via note title, but with Journal Notes in particular truncated to only display the day, instead of year-month-day. As of Dendron 0.98.0, this does not seem to be possible.
Should this issue be reopened, or should I create a separate issue?
Thank you.

Hey @micharris42, thank you for the clarification.
It seems like then your concerns are more related to how journal note traits are setting the note titles than what the tree view is displaying. I imagine it would make more sense to make the journal note title behavior customizable rather than make the tree view handle it.
Since this issue has all the necessary context for your problem, I'll go ahead and reopen this issue. No need to create a separate one.
@jonathanyeung I think this can be resolved if we expose the journal note trait to an actual file that the user can customize. Do you think that makes sense? The alternative would be adding a config that would toggle the behavior but I think that's a bit of a roundabout way of handling it when we are already utilizing note traits.


Automated Package Upgrade

:tada: This PR is included in version 7.0.84 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[gettext] Fix building for android

Taken from https://github.com/navit-gps/navit/pull/1087/files
Describe the pull request

What does your PR fix?
Fixes building gettext for android

Which triplets are supported/not supported? Have you updated the CI baseline?
+android, No

Does your PR follow the maintainer guide?

Yes

I don't understand how this affects libtasn builds on windows

@m-kuhn Not related to your PR, and I've fixed it.

Thanks @JackBoosY

Cool, thanks @m-kuhn :)


Automatic return to checkpoint

For some training it'd be helpful to be able to just quikly, automatically return to checkpoint every n seconds or on some kind of event. Like when you touched the ball, hit the ground, wall, ceiling, hit hyperspeed.

Thanks for the suggestion.  A couple potential complications I could see are: the UI to configure this would be complex/large with so many different choices of things to reset on, and when the checkpoint is restored, you'll be holding down buttons already, so it will immediately resume, which often will ruin the shot.
For the former point, there are several events I can think that would be most common: goal scored, {ball,car} touches {ground,wall,ceiling}.  This is 7 already, and multiple would want to be active at the same time.
For the latter, it might be feasible to suppress resuming from the checkpoint until after all inputs are released and then one is pressed again.

For the latter, it might be feasible to suppress resuming from the checkpoint until after all inputs are released and then one is pressed again.

In fact, this should probably be the behavior even when pressing the button to restore a checkpoint.  I've had times where I reset before fully releasing the controls, and the checkpoint resumes instantly, ruining the shot.

This is implemented with 0a5d5543baa257b7e93343efe303b3445ea77389.  I'll make a preview release in a minute if you want to test it out.

If you don't mind testing it out, you can download the preview version here: https://github.com/NitrOP7674/FreeplayCheckpoint/releases/download/v1.2.0-pre/CheckpointPlugin-v1.2.0-pre.zip
Just unzip into your bakkesmod directory (C:\Users\%username%\AppData\Roaming\bakkesmod\bakkesmod).
I'll submit the new version to bakkesplugins.com after using it for awhile to make sure there are no more bugs, and then it takes a few weeks for them to update it on their site.


⚠ Erroring on update: Git

I'm rewriting the git history to remove the assets/ folder, which contained a nontrivially-sized video and GIFs. The fix should simply to delete the plugin folder and install again; nothing should break if you do that :)
If you have a fork of this for some reason, you should not have any trouble rebasing. I've only rewritten the history for assets/.
TL;DR: delete and reinstall, and it'll work (and be faster now)

(oh yeah, forgot to link in first post, was motivated from here: https://www.reddit.com/r/neovim/comments/wsg5yx/attention_to_all_plugin_authors_newcomers_careful/)

It's definitely a bit annoying to deal with, but the fix isn't too bad, so I do hope this has a net benefit overall for everyone using iswap.nvim.
Thanks for understanding!


Add test for correct referrer header

The current version of Turbo contains a bug in which the referer header is not correctly set for requests (see #332 and https://github.com/hotwired/turbo-rails/issues/211) This potentially breaks a lot of functionality in Rails apps. I noticed there is no test assuring the header is set correctly, so I added one.
Like stated in #332, the bug is introduced with the changes in #306 by @kirillplatonov and @dhh. When you change fetch_requests.ts:82 back to to old version, the test is green.
// await this.allowRequestToBeIntercepted(fetchOptions)
dispatch("turbo:before-fetch-request", { detail: { fetchOptions } })

I'm not familiar enough with the internals of Turbo to understand why the header changes, so any help to actually fix the issue is welcome!

@edwinv thank you for adding the test. I will take a look at this issue with Pausable API.

https://github.com/hotwired/turbo/pull/345

Perfect! Closing this PR in favor of #345, because it contains both the tests and the fix.


Bug: Cannot deselect selected playground content when selection includes a table and some other content

Lexical version: current playground version
Steps To Reproduce

Start with the Lexical playground
Add a table
Click and drag a selection that includes both some part of the table, or even all of it, and some other text content on the page as well.

The current behavior
A mouse click anywhere does not automatically deselect the selection.
The expected behavior
A mouse click anywhere should deselect the selection, as it does in all other playground contexts.

https://user-images.githubusercontent.com/16598249/215102352-58e94db9-bc54-43fe-832c-d67001ae4c73.mp4
This is a video demonstrating the issue.


Collaborate?

Hi @archit-p , I just wanted you to know that I'm enjoying the table feature you've built for React. I'm hacking away in a fork, trying to get it to a point where it can be easily installed into an existing React project via npm module. That's my main need right now, because I would hope to use it in a few internal projects for our Mumbai-based company.
Take a look and let me know if you'd be interested in trying to work out a way to merge these together before I deviate from your code base too much. If so, I'd like to hear specifically what it would take in your view to remain compatible with however you're already using it.
https://github.com/koyal-tech/editable-react-table
Warm regards,
Jeff

Hi Jeff,
Thank you for your kind words. I'm happy that you're enjoying this project and would like to extend it.
As the code is currently, I believe the Table component can be published as a module and re used in other projects. There are a few things to be mindful of when making this change:

State management is completely outside the Table component and currently uses useReducer. All the code is written with this in mind, so you might need to make changes if you wish to use a different state management tool and/or move state management inside the Table component itself. I see that you've chosen to introduce the TableWrapper component and bring state management into the module itself.
The project uses an older version of Vite and so build is done using Rollup. Vite has since moved to using Esbuild which is faster, so that is something to be explored.
There are no provisions to change the styling. All styles are written using plain CSS, so this might become an issue when integrating within a larger project with its own style system.
Finally, there are no tests in the project. This is an area I'm unfamiliar with, however I strongly believe tests would be required for robustness.

I'll be happy to discuss these issues further and to integrate these changes into the project. Feel free to create a PR/more issues with ideas and questions!

Thanks, this is helpful and mostly inline with how I felt after reading the code base. We have a pretty strong unit testing practice at Koyal Tech, and will endeavor to contribute some basics in that regard. 👍
Just so you're aware, I did an MVP to get it modularized and able to import, but I know further enhancements will be required before it is useful enough to merge back in.
https://github.com/koyal-tech/editable-react-table
(PR 1 might be of interest at a quick glance.. https://github.com/koyal-tech/editable-react-table/pull/1 )
https://www.npmjs.com/package/@koyal-tech/editable-react-table

I have to thank you for your work. This repo inspire me to create a plugin in [Obsidian.md|https://obsidian.md], and I shared this repo link inside the readme.md as source.
If I achieve another kind of cell (calendar, image...) I will share it here too!
https://github.com/RafaelGB/obsidian-db-folder

As I promise, I dev the Calendar column type using react-calendar npm dependency feel free to check it =)

Thanks for the feedback @jeff-r-koyaltech @RafaelGB @joseph-vedadi ! Will be using #13 to track creating a package.


Unable to use with RN 0.44

Thanks for your issue.
I fixed it and I will release new version soon.


Typo in https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/docs/extensibility/how-to-provide-a-service.md

Hello,
I'm trying to understand how to write a service and I've found a potential typo here:
https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/docs/extensibility/how-to-provide-a-service.md
Could you please double check this code:

private object CreateService(IServiceContainer container, Type serviceType)
{
if (typeof(SMyService) == serviceType)
return new SMyService(this);
return null;
}

Shouldn't this code be "return new MyService(this)" and not a "return new SMyService(this)"?

@maxperga thanks, we'll take a look.

@maxperga Thanks for pointing this out. You are correct and we will update the code snippet shortly.


Updated docs/Resources.md with gitter channel info.

@ErikSchierboom Changes in resources.md to add gitter channel information.

Great, thanks!


Add hot deployment

We should be able to deploy and start using a project without the need to restart the server.

This already works as expected and for some reason I thought it does not 😑
Hence closing!


Evaluate multiple providers

Created a extensible script which evaluates multiple providers
Invoked gemini and openai
Easily extensible for additional providers like hugging face, cohere, jinai etc


SAK-44383 samigo > provide return link on DD UI for URL delivered quizzes

https://jira.sakaiproject.org/browse/SAK-44383
Usage of samigo has increased drastically due to the pandemic. As an extension, more instructors are delivering quizzes using the published assessment URL. Due to other issues, it can be quite easy for students to get click happy and/or become impatient and refresh the page before it finishes loading. The result is that the students are taken to the "Data Discrepancy" page.
In a normal situation, this Data Discrepancy page provides the user with a button to return to the samigo landing page (quiz listing UI). However, in the case of a quiz delivered by published URL, this button does not appear (nor should it in this case, the instructor intended for the user to take a specific quiz, not give them the option to take other quizzes in the site as well, plus the tool itself may be intentionally hidden by the instructor).
So in the case of a quiz delivered by URL, upon reaching the Data Discrepancy page there is no way for the user to return to the quiz (unless they're critical thinkers and paste in the published assessment URL again into their URL bar). This has lead to a lot of complaints and support calls at our institution, which is becoming burdensome.
One way to address this (for quizzes delivered by URL) is to present the user with a link to take them back to the "Continue Assessment" page, so they're easily and quickly able to resume their quiz attempt without intervention or support.
Additional mitigation (blocking them from getting click happy) is handled in another ticket: SAK-44248.

I would have preferred to use the JSF 2 <h:button> or even <h:link>, but for whatever reason samigo blows up trying to render these.... I thought we were on JSF 2 now?
Anyway, falling back to JSF 1 workaround of using an <h:outputLink>...

I also had no luck with the new JSF 2 <h:link>


Update front page

Needs to include a brief summary of what the package is and does, along with references to appropriate papers.

Need to double-check appropriate refs, as well as add a modifications page to the docs.

Closed with merge of #56.


initdb configmap name

The name is mismatched between the creation and referencing. It seemed easiest to just hard-code the name to avoid having to run values through tpl, but not entirely sure if there is something that makes this undesirable, so leaving it as a PR until something is decided.

Closing this after https://github.com/CloudVE/galaxy-kubernetes/commit/d282e8e599b3b0cfaf433a612ef4a0e46cbab771


Add method to generate JWK from EncodingKey

Awesome, thanks! FWIW I intend to look into getting similar public key parameters in ring after this, and I'll make another MR. It should be simple enough seeing how simple the workaround is, unlike with Ed25519.

Ah, mis-targeted it...

Redoing the merge here: https://github.com/andrewbaxter/fork-jsonwebtoken/pull/5


Install fails on Windows

running choco install ngrok results in
Attempt to get headers for https://bin.equinox.io/a/c4Cafbnz7jm/ngrok-v3-3.14.1-windows-amd64.zip failed.
  The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://bin.equinox.io/a/c4Cafbnz7jm/ngrok-v3-3.14.1-windows-amd64.zip'. Exception calling "GetResponse" with "0" argument(s): "The underlying connection was closed: An unexpected error occurred on a send."
Downloading ngrok 64 bit
  from 'https://bin.equinox.io/a/c4Cafbnz7jm/ngrok-v3-3.14.1-windows-amd64.zip'
ERROR: The remote file either doesn't exist, is unauthorized, or is forbidden for url 'https://bin.equinox.io/a/c4Cafbnz7jm/ngrok-v3-3.14.1-windows-amd64.zip'. Exception calling "GetResponse" with "0" argument(s): "The underlying connection was closed: An unexpected error occurred on a send."
This package is likely not broken for licensed users - see https://docs.chocolatey.org/en-us/features/private-cdn.
The install of ngrok was NOT successful.
Error while running 'C:\ProgramData\chocolatey\lib\ngrok\tools\chocolateyinstall.ps1'.
 See log for details.

Visiting the link below to manually to download from getting started results in an error The connection for this site is not securebin.equinox.io sent an invalid response. ERR_SSL_PROTOCOL_ERROR
(https://bin.equinox.io/c/bNyj1mQVY4c/ngrok-v3-stable-windows-amd64.zip)

@Nicolis1 thank you for the issue. we are investigating now.

We are currently working with Chocolately to get our latest binary unblocked and released: https://community.chocolatey.org/packages/ngrok/3.16.0


Add note in README that django_zappa needs to be added to INSTALLED_APPS

This is included in this PR: https://github.com/Miserlou/django-zappa/pull/16


Update version in version.py

The last release was 0.6.3, but version.py has: version = "0.6.2".

The validation is complete. The Connected PR fulfills requirements of all connected issues. The new workflows added work fine and now automatically updates the version.  Issue is clear from QA Validation.


Should the scheduler concept require get_completion_scheduler of the scheduler's sender?

Perhaps add:
  requires (S&& s) {
    { get_completion_scheduler<set_value_t>(schedule(s)) } -> same_as<S>;
  }

?

@lewissbaker, thoughts?


loot-links

Link
https://loot-links.com/s?fk9o
Version
Manifest-v3
What browser(s) are you using?
Chrome browsers (includes brave, edge, opera, etc)
What platform are you using?
Computer (Windows, Linux, MacOS)
(Optional) Anything else?
It should be really easy to make a bypass for it. Here's a part of its source code:

THIS IS A FAST BYPASS
open console and type "PUBLISHER_LINK"

Deobfuscator used: https://deobfuscate.relative.im/
I did some processing on one of the scripts (it creates the PUBLISHER_LINK variable in the window), and here's the result:
https://gist.github.com/RealPacket/ddfbf2126dcea0274b6040b867219f67

works! right now: https://loot-links.com/s?fIjL -> https://www.mediafire.com/file/u09lk2fa7vtirdc/Codex_new_one.apk/file

I'm going to try and make a PR to fix loot links support.

I'm going to try and make a PR to fix loot links support.

I'm late... https://github.com/FastForwardTeam/FastForward/pull/1333

Fixed by #1333


refactor(stitcher): optimize to be more memory efficient

Signed-off-by: Phil Kuang<EMAIL_ADDRESS>Issue
The backend node process runs into heap out of memory crashes when processing entities with large number of relations. For us, we have a scenario that runs into this where we have some Group entities whose members include all of our User entities. This is sourced from our GitHub instance that have "master teams" that include every user in our enterprise server (~6k hasMember relations).
Fix
Optimize the Stitcher code to not expand queried DB rows by avoiding join queries with the relations table. This can be fetched separately instead to avoid duplicate row data being loaded into memory. Applying this small optimization allowed us to fully process our entities within the default node memory limit.
Alternative Workaround
Bump the default node memory limit via NODE_OPTIONS=--max-old-space-size=<new-limit>. For our use case this required bumping up to 8gb to successfully process our entities.
Diagnosis
Please let me know if I might've misunderstood anything in my diagnosis below 🙏
We encountered the out of memory issue when updating to the latest release (v1.8). We determined the cause was due to this change which modified the behavior of the GithubMultiOrgProcessor which we use. Previously this processor only defined spec.memberOf relations on individual User entities but with this change, spec.members relations are also now defined for Group entities.
The following describes my understanding of the behavior of the stitching process before and after this change and how it highlighted the memory inefficiency:
Before GithubMultiOrgProcessor Refactors

Groups are emitted first and are processed & stitched without issue since they have no defined relations (yet)
Each user are emitted with the memberOf relation so relations originate from User entities only
As each user is processed and stitched, it causes the "master" group to be restitched to include the new user in its relations

The DB query in the Stitcher code loads a low number of rows into memory for

The User since a user won't have many memberOf relations
The "master" Group since the number of member relations are only as many as the number of User entities processed so far in the pipeline

After GithubMultiOrgProcessor Refactors

Both Group and User entities emit membership relations
Groups are emitted first and processed & stitched with all relations inserted into the relations table

Stitching pulls all DB rows into memory which is ok if this is the only thing being stitched

As each User is processed, this causes the "master" Group to be re-stitched which results in:

All DB rows being fetched into memory again each time the "master" Group is re-stitched
Multiple User entities may be processed in parallel which mean the "master" Group is re-stitched for every user
Eventually node will run out of memory and result in a heap dump when too many parallel iterations of the Group is stitched at the same time

Below is a snapshot of the heap profile taken right before the out of memory crash which confirms the behavior described above:

The Array allocations (in red) correspond to multiple parallel executions of the Stitcher fetching DB rows into memory
The inspection of the contents of the elements of these arrays (in blue) confirms that these are the rows that are the result of "join expansion" with the relations table. Each row is nearly identical loading redundant data aside from the relation properties
The memory consumption of the processedEntity property (in yellow) shows that this stringified representation of the entity definition consumes the majority of the memory allocation and is the key culprit of the inefficient memory usage

Additional Notes
This should only occur the first time users are ingested since there is logic that prevents stitching of previously processed relations (though it does not detect duplicate relations that originate from another entity, ie. it doesn't stop a User from re-triggering the stitching of the Group even if their relation (that originated from the Group) has already been stitched, this seems to be caught later on). However we ran into this as a side effect of the recent bugs introduced
in GithubMultiOrgProcessor (see fix for more info) that corrupted the old relations and triggered everything to be re-stitched. Those bugs ended up as a blessing in disguise as this inefficiency probably would've continued to go unnoticed without them 😅
Applicable to https://github.com/backstage/backstage/issues/14574 under performance issues.
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Hi!
Regarding "hotspot" re-stitching - yes, that's definitely unfortunate. For a long time now, I've been wanting to change the stitcher such that it runs entirely standalone. It would be preferable if there was just a "refresh_state.needs_stitching" column basically, and then the stitcher could go grab things that are on todo in any way that it sees fit. There would be a chance, then, for rolling up multiple stitch triggers into just one actual piece of work, if there's some debouncing / delay.
Regarding both Group and User having their spec filled with membership: It would actually be kind of nice if only users had those, since it's likely that users in general are part of fewer groups, than groups have members. Duplicating the information is just wasteful as well; it'll generate duplicate relations that need to be deduped during stitching, for no gain.
I can totally understand that this big join got problematic in these corner cases you mention. The full entity body JSON ended up being cloned in every single result row. Main concern here is losing some atomicity when splitting into two queries, since I very intentionally made it a single expression for that reason. I'll have a look.

@freben @Rugvip thanks for the feedback! I totally didn't consider the risk of breaking atomicity, will definitely keep that mind when I consider making DB changes in the future. I'm glad the risk here is minimal and updated the change to perform parallel queries (thanks for the tip!).


disable tab navigation while loading is showing

It would be great if you can capture the tab key so the user cannot go to some inputs or links with the tab key while the loading is enabled

I tried various solution but none of worked.
I gone through packages like https://github.com/theKashey/vue-focus-lock
but their solution is not clean and a bit hacky.
I have also gone through bootstrap model component, because it is already doing the same. But could not figure out how they are doing.

@empresarrollo
I have made this feature, i haven't released it, need more testing.
See the commit https://github.com/ankurk91/vue-loading-overlay/commit/063cceee1d4800ea986b2e845fdb85263cff2d29
Will invest more time this weekend.

Released v2.2.0


Add Python 3.12 to CI.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (7e95fc6) 87.21% compared to head (e195e46) 87.21%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #166   +/-   ##
=======================================
  Coverage   87.21%   87.21%
=======================================
  Files          29       29
  Lines         837      837
=======================================
  Hits          730      730
  Misses        107      107

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


Update Cosmos to v0.38.3

Yesterday AIB shared with the cosmos community the recent discover of a high-severity security vulnerability that impacts all versions of Tendermint.
To fix this issue, they will release a new version of tendermint and cosmos sdk today at 14:00 UTC.
We need to upgrade to this version in order to fix this security problem.

What should be done is start from the current 0.3.0 release, update the Tendermint version there with the most recent one, and then release a 0.3.1 if possible.
Then all the nodes should upgrade as soon as possible.

Closes with #123


Accept file::// urls

Is your feature request related to a problem? Please describe.
For the product I am working on, I am now using a custom build of capacitor-community/electron as we need the filesystem aspect to be able to accept file:// urls. Currently it works by not passing in a directory at all, which triggers my code to check if there is a valid URL and whether the protocol is file://. Is this something useful for the main project? I have tested my code for file and directory reading but it probably needs some more testing around some other areas of filesystem.ts, e.g. mkdir etc. I can try to get around to finding some time to do that! Let me know if you want a PR for what I have.

Can you describe the use case more?
I don't understand where you would need to use a file directory URL rather than just reading the file on the system via the Electrons API.

So we're using deep linking within our electron app and as part of that a file url can be passed in via the query. I did at first just try removing the file protocol and accessing the directory path but the current API only allows directories to be Documents or 'DRIVE_ROOT' - neither of which worked well for us (access denied errors and having to do string manipulation to try to find the correct place and drive, which wasn't reliable - Node seems to default to the drive that node is running on), the file:// url seemed to offer is the most consistent and reliable way of doing this and works consistently across platforms. It is also fully supported by NodeFS so it's nice to be able to have this as an option in Electron.

Have you tried to load the file via the electron API directly rather than plugins?
You could even make your own electron platform plugin that would do what you need too.

I'll have a play. I did try it via the electron API, but because that uses the HTML5 Web API, I was then getting security issues using the file:// urls (even though we're on https). I will have a play with perhaps doing a plugin if I can find time around the day job :)
For now we'll probably keep using the custom version of community electron that I have and I'll just keep my fork up to date with yours.


⚠ Orpheus has degraded performance

In f48f8db, Orpheus ($OPS) experienced degraded performance:

HTTP code: 200
Response time: 7665 ms

Resolved: Orpheus performance has improved in 7a1ea81 after 5 minutes.


Q telomere capping (GO:0016233)

Should telomere capping be an activity, rather than a process?
The process is
GO:0031848 | protection from non-homologous end joining at telomere

I also see
GO:0048239   negative regulation of DNA recombination at telomere
but this is really the same as
GO:0031848 | protection from non-homologous end joining at telomere
The end protection prevents recombination AND non-homologous end joining

Should telomere capping be an activity, rather than a process?

Here's the definition: "A process in which telomeres are protected from degradation and fusion, thereby ensuring chromosome stability by protecting the ends from both degradation and from being recognized as damaged DNA. May be mediated by specific single- or double-stranded telomeric DNA binding proteins."
That sounds like capping comprises one or more binding events. If these can be captured and individuated then it's a process. To the extent that binding is out of scope for GO (because of the issue of figuring out what gene product enables it), tallying the events and gene products is harder.

I was wondering what the molecular function of "shelterin" would be , other than "telomere binding"

see
https://github.com/geneontology/go-ontology/issues/23997
which is closely related.


No way to set ranges for fitting parameters in Optimize functions

The optimize functions do not have any way to set parameter limits, for example stating p[0]>=0 to prevent the fitting from attempting negative values. This SEVERALLY limits the usefulness of the package as a whole, as there is no way to prevent the optimization from sliding into unacceptable or non-physical areas. Many unacceptable fit parameters are easily avoidable if the package simply were able to be told not to proceed into certain areas, but instead the algorithms can fall into extant but known unacceptable minima very easily.
There is no simple and universally applicable method for preventing this from being an issue, as often in these cases the functional form may not be known or may not be defined in the forbidden region and thus there is no truly safe way to alter the functional output such that the fit returns to the safe region if it wanders out. This is the single largest and most troublesome problem in the entire package for myself and many other scientists, and it is a glaring omission in this otherwise extremely proficient MATLAB replacement.

This work by @nmayorov may be of interest here: https://github.com/scipy/scipy/pull/5019.

An implementation of nonlinear LSQ has landed in gh-5044, yay! I wonder if this issue should be closed now.

Indeed it is possible, even without needing to use limfit package!
e.g. if you are using lasts method, you can define your condition in your model, so that the residual becomes very large when one the parameter values fall outside of the desire interval. Here is an example, in which I require my parameter theta say in a range where cos(theta) is always positive.
model function for the direction reconstruction
#----------------------------------------
def model(r, par):
'''
r = delta_r [x, y, 0]
'''
# direction of the pulse
theta = par[0]
phi = par[1]
s = [np.sin(theta) * np.cos(phi), np.sin(theta) * np.sin(phi), np.cos(theta)]
if np.cos(theta) < 0:
return 1e16
return -np.dot(r, s)
residual function for direction reconstruction
#----------------------------------------
def chisq(par, t, r):
return t - model(r, par)
whatever main program
#----------------------------------------
initial values for the fit
init_vals = np.array([-0.05, -0.6], dtype=float)
fit the function
s, flag = leastsq(chisq, init_vals, args = (t, r))


Release

Release multiple-sequence EID

Codecov Report
Base: 66.32% // Head: 66.72% // Increases project coverage by +0.40% :tada:

Coverage data is based on head (3bb04fa) compared to base (32c329d).
Patch coverage: 89.63% of modified lines in pull request are covered.

:exclamation: Current head 3bb04fa differs from pull request most recent head c5f8ed7. Consider uploading reports for the commit c5f8ed7 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #297      +/-   ##
==========================================
+ Coverage   66.32%   66.72%   +0.40%
==========================================
  Files          67       67
  Lines        5137     5154      +17
==========================================
+ Hits         3407     3439      +32
+ Misses       1730     1715      -15

Impacted Files
Coverage Δ

api/utils/extensions.py
20.00% <0.00%> (ø)

db/python/connect.py
55.14% <ø> (ø)

db/python/tables/sample.py
27.31% <0.00%> (-4.98%)
:arrow_down:

api/routes/sequence.py
46.37% <46.66%> (+3.51%)
:arrow_up:

db/python/layers/sequence.py
77.38% <69.23%> (+10.15%)
:arrow_up:

db/python/layers/sample.py
52.67% <80.00%> (+0.34%)
:arrow_up:

db/python/tables/sequence.py
82.10% <83.63%> (+13.23%)
:arrow_up:

db/python/utils.py
73.33% <100.00%> (+1.24%)
:arrow_up:

models/models/analysis.py
100.00% <100.00%> (ø)

models/models/sequence.py
90.00% <100.00%> (-3.11%)
:arrow_down:

... and 20 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Allowing for Multiple Parents

Forgive me if this is already possible, but one main thing holding me back from even trying Dendron is that it seems to limit your notes to a strict folder-like hierarchy. I agree that a hierarchy-less system, such as with using only tags or standard links, is limiting, but a strict hierarchy is equally limiting. What we need is to allow for a file to be in multiple hierarchies at the same time.
I realize that this probably goes against the core function/philosophy of Dendron, but I'd rather have zero defined parents than only one, in which case I'm likely to use another tool where I'm not fighting the design.
I suspect this functionality will never happen, but I really like a lot of what Dendron has so I'm wondering if there is a workaround - is it possible to use Dendron without the "."-delimited hierarchies (everything in one folder/vault) but the front matter allows for multiple parents to be listed, which can be used in your neat graph modes and some other features?

While you can't have multiple parents (Dendron's a tad opinionated that way) you CAN use backlinks to the "multiple parents to be listed". See this for more details on backlinks: https://youtu.be/vrhBNGMJQwE?t=398.
I myself have a many pages that are under the "projects" directory but also map to an area so use this feature extensively.

just to elaborate on this a bit more, while we don't plan on supporting multiple parents, we are considering adding support for note aliases which will allow you to take the same note and have it aliased under multiple hierarchies. would this be good for your use case?
https://github.com/dendronhq/dendron/issues/128

I don't think aliases will work for me, its an entirely different thing. What I'm talking about would be a fundamentally different framework - a network diagram rather than a hierarchical one. If interested, you can check out The Brain to see the best implementation of this way of organizing and thinking.

A little late to the game on this one, but in case it helps @nixsee or anyone else out there...

Dendron does not enforce a "strict hierarchy". It supports hierarchy, and very flexibly in my opinion, but you can just as easily keep all your notes "at the top level", i.e. no hierarchy at all
between links+backlinks (as @kpathakota mentions) and tagging (now natively supported), Dendron does support multiple hierarchies pretty well. The hopefully-forthcoming aliasing that @kevinslin mentioned could help too.


Optimize startup on versionLessThan function

Hi, how are you? I've been using the lib for a few months now, but I notice a slowdown when trying to start, and when analyzing and testing I realized that most of it is because of the versionLessThan function, so I redid it in bash script, did some tests and everything worked fine.

Wtf error?

I had gotten a weird Docker error, so I just added a space to run it again and it worked, I changed it to the version variable to check

From my tests on my dedicated device, before the change, the startup message took around 17 seconds to arrive, after the change it dropped to 7 seconds

This number may not be the same for everyone, some will feel the changes more and others less depending on the CPU and especially the speed of the ra memory.

But everything is ok now I believe


Save button state with form validation

Save button state with form validation
I found an issue which comes from interaction of page edit form validation and save button state.
Affected Version
silverstripe/framework - 4.6.0
Description
Save button state is incorrect after form submission when a validation error occurs.
Steps to Reproduce

Navigate to page edit form

Make edits in the form - make sure that a form validation is in place (for example a required field).

Save the form.

Expected result
Save button is green, it indicates unsaved changes. It should be the same as before the form submission as the change were not saved due to the validation error.
Actual result
Save button is transparent with green border, it indicates save changes.

Duplicate of https://github.com/silverstripe/silverstripe-admin/issues/1110


defineProps with external Props give a "Cannot read properties of undefined (reading 'sys')"

Environment
Ubuntu
Node 18
Nuxt 3.5.3 (same on 3.5.1 or 3.5.2)
Vue 3.3.4 (same on 3.3.3, 3.3.2, 3.3.1)
Nitro Version: 2.4.1
Reproduction
https://stackblitz.com/edit/nuxt-props-ts-issue?file=tailwind.config.js,components%2FAHeader%2FAHeader.vue,components%2FALogoTest%2FALogoTest.vue
Describe the bug
When I import types from an external file into a component and I want to use these types in defineProps, I get the following error on the reproduction link :

Additional context
No response
Logs
No response

Let's track in https://github.com/nuxt/nuxt/issues/20936


Change LuaRocks spec url to https

Hi
I'm working behind a corporate firewall which restricts SSH traffic. Therefore
luarocks install --server=https://luarocks.org/dev paths

fails at git clone. I guess, it would be easy fixable by changing the git url to https. I believe that drawbacks of doing so would be neglectable, but people like me would greatly benefit from it.
I tried to run LuaRocks against a local spec file using https. git clone succeeded, but LuaRocks failed afterwards. Thus, I'm not sure whether it can really that easily be changed. Maybe it can't or maybe LuaRocks behaves slightly different with local spec files as opposed to "official ones" on the internet

Continues to fail ever since this issue was created.
Seems I won't be able to fix a project.


Fix occupational frameworks count

Asana ticket:
This allows  OccupationStandard.by_national_standard_type to receive a single value as a symbol and work as expected. Previously it only worked with the value as string, since it is the format we search from the query form checkbox
This is how is called from home.html.erb, which display an incorrect result:
 <p class="font-bold text-accent-100">
   <%= OccupationStandard.by_national_standard_type(:occupational_framework).count %> Apprenticeships
 </p>

Eventually we should move these to get all records from ES so we have consistent data.

@littleforest I would keep them in PG


Statistics in JSON format

Hi, do you think it would be possible to output the staticstics in JSON or any other format, that is more modern then ancient XML?

It is possible. XML just simplier to output, no need to watch over commas and brackets.

So, could you please add JSON support? XML may be easier to generate, but it is outdated and noone really uses it anymore...

It's not outdated. Java, Tomcat, OO, LiO, MSO and many others using it. And nginx-rtmp too.
As for request - I want make any promises.

IMHO it is, but hey, I don't want to argue... And if you find a while to add the JSON support, it would be really appreciated (not just by me)...

I have a converter written by myself, it works like proxy and returns JSON,
it's in PHP. Anyone interested?
22 sie 2015 16:19 "Jacob Sycha"<EMAIL_ADDRESS>napisał(a):

IMHO it is, but hey, I don't want to argue... And if you find a while to
add the JSON support, it would be really appreciated (not just by me)...
—
Reply to this email directly or view it on GitHub
https://github.com/arut/nginx-rtmp-module/issues/669#issuecomment-133708321
.

Not easy, as you can see on:
https://github.com/arut/nginx-rtmp-module/blob/master/ngx_rtmp_stat_module.c#L436
XML format is "hardcoded" every where in the file, it's not a conversion (with libxml2 for instance).
If you use Php, convert XML to JSON is as simple as:
        $xml = simplexml_load_file('http://<IP_ADDRESS>/stat');

        $json   = json_encode($xml);

Isn’t hardcoding in API a bit contraproductive?
From: Thomas Decaux<EMAIL_ADDRESS>Sent: Wednesday, September 2, 2015 10:21 AM
To: arut/nginx-rtmp-module
Cc: Jacob Sycha
Subject: Re: [nginx-rtmp-module] Statistics in JSON format (#669)
Not easy, as you can see on:
https://github.com/arut/nginx-rtmp-module/blob/master/ngx_rtmp_stat_module.c#L436
XML format is "hardcoded" every where in the file, it's not a conversion (with libxml2 for instance).
If you use Php, convert XML to JSON is as simple as:
    $xml = simplexml_load_file('http://<IP_ADDRESS>/stat');

    $json   = json_encode($xml);

—
Reply to this email directly or view it on GitHub https://github.com/arut/nginx-rtmp-module/issues/669#issuecomment-136974050 .  https://github.com/notifications/beacon/ABdnmFDiPR59MHaTihNvHmZnxy_6EOdAks5otqjvgaJpZM4FudZ8.gif

I just got PHP script which handles xml->json for me making all arrays looks good. I tried 2-codelines-solution but it returned ugly JSON sometimes.

@JacobCZ if you want JSON then you're more than welcome to submit a PR. Asking the devs to do it and telling them that their coding style isn't great isn't the best way to get things done :-)

I’m not telling them such thing, I’m just noting, that XML might not be the best way to go theese days ;) Unfortunatelly, I don’t do C, so PR is not an option for me... But I found a XML to JSON library for PHP, so it’s not such a problem for me...
From: Chris Wiggins<EMAIL_ADDRESS>Sent: Tuesday, September 8, 2015 9:29 AM
To: arut/nginx-rtmp-module
Cc: Jacob Sycha
Subject: Re: [nginx-rtmp-module] Statistics in JSON format (#669)
@JacobCZ https://github.com/JacobCZ  if you want JSON then you're more than welcome to submit a PR. Asking the devs to do it and telling them that their coding style isn't great isn't the best way to get things done :-)
—
Reply to this email directly or view it on GitHub https://github.com/arut/nginx-rtmp-module/issues/669#issuecomment-138460579 .  https://github.com/notifications/beacon/ABdnmMOxV_aHHuKejDu5DzrW1c1UW1-Bks5ovoXZgaJpZM4FudZ8.gif

@misiek08 can you share you "bridge" please? :)

    $xml = simplexml_load_file('http://<IP_ADDRESS>/stat');

    $json   = json_encode($xml);

$xml = simplexml_load_file('http://<IP_ADDRESS>/stat');
$xmlj = json_encode($xml);
$data = json_decode($xmlj, true);

JSON is modern data format, maybe u can try srs, all api data are in JSON.

@winlin +1
po 21. 9. 2015 v 8:52 odesílatel winlin<EMAIL_ADDRESS>napsal:

JSON is modern data format, maybe u can try srs, all api data are in JSON.
—
Reply to this email directly or view it on GitHub
https://github.com/arut/nginx-rtmp-module/issues/669#issuecomment-141892854
.

@JacobCZ You can migrate from nginx-rtmp to SRS https://github.com/simple-rtmp-server/srs

@winlinvip looks cool, but advertising in other repo?

@JacobCZ SRS is open-source project, SRS1 copy lots of codes from nginx-rtmp, so I think SRS can be a fork project of nginx-rtmp. The difference is SRS base on ST, while nginx-rtmp base on nginx. Whatever, the RTMP and stream process of SRS, for example, the exec, the forward, the transcode, hls, hds, is build from nginx-rtmp. So, need more explains?

In a word, welcome to migrate from greate nginx-rtmp to great SRS~
:)

Advertising in other repo just IS bad. It doesn’t matter that it’s opensource or even based on te original project…
From: winlin<EMAIL_ADDRESS>Sent: Tuesday, September 22, 2015 9:20 AM
To: arut/nginx-rtmp-module<EMAIL_ADDRESS>Cc: Jacob Sycha<EMAIL_ADDRESS>Subject: Re: [nginx-rtmp-module] Statistics in JSON format (#669)
In a word, welcome to migrate from greate nginx-rtmp to great SRS~
:)
—
Reply to this email directly or view it on GitHub https://github.com/arut/nginx-rtmp-module/issues/669#issuecomment-142200622 .  https://github.com/notifications/beacon/ABdnmLflcuEkzwnLburOSWXKyZrBVJoiks5o0PiCgaJpZM4FudZ8.gif

@JacobCZ Why bad?

anyway, I dont understand chinese ^^

Anyway, please love what you love~
原来非中国人也一样愚钝不化、胶柱鼓瑟、冥顽不灵、门户之见、一叶蔽目、先入为主、舍本逐末，谁的代码不是用英文写的？谁的wiki不是提供英文版？谁分发的RTMP、HLS、HDS、DASH只能中国人看得懂？

@winlin if you need to spam, at least spam in english...
On Sun, 4 Oct 2015 02:01 winlin<EMAIL_ADDRESS>wrote:

Anyway, please love what you love~
原来非中国人也一样愚钝不化、胶柱鼓瑟、冥顽不灵、门户之见、一叶蔽目、先入为主、舍本逐末，谁的代码不是用英文写的？谁的wiki不是提供英文版？谁分发的RTMP、HLS、HDS、DASH只能中国人看得懂？
—
Reply to this email directly or view it on GitHub
https://github.com/arut/nginx-rtmp-module/issues/669#issuecomment-145300019
.

Sorry, I say nothing.

I solved this server side using the nginx XSLT module  and a xml2json stylesheet i found here.
The see how, check out this commit: https://github.com/espizo/simple-nginx-rtmp/commit/d4705612500368fb77cff0cb7d6584d64ce7e03f

i've added json support for the stat page https://github.com/arut/nginx-rtmp-module/pull/815
please test & give feedback. forgive me if the source sucks, have not coded C in a while ;)


[composer] device invite flow succeeds, but requires app refresh to load

Seems like some errors are getting thrown after the Device Invite flow that crashes Composer. All seems to work after cmd-R.
Repros:

Invite another device
Watch it hang when it succeeds

#4847


[TEST] Unit test code coverage improvement

What's the test to develop? Please describe
For the purpose of system stability, we should have a plan to increase unit test case coverage especially for longhorn-manager part. And there is also includes to add e2e test cases to decrease manual test effort.
Additional context
Add any other context or screenshots about the test request here.

This will be beyond the release scope, so it should be a continuous effort.
cc @longhorn/dev

@weizhe0422 For automating manual regression test cases, should have another ticket EPIC to track instead of using this ticket. This ticket will only focus on unit testing of primary components, especially longhorn-manager.
cc @longhorn/qa

@weizhe0422 Converted this to EPIC, so you can add more tickets later to correlate to this when you are working on each sub-coverage.


all-cabal-hashes: Update from Hackage at 2018-10-29T21:01:27Z

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

/cc @basvandijk

Outdated by f648605b4e521667baeeda71d8bf5573100bdb7b


Error when executing uds server using apache wsgi

Hi,
I'm trying to execute openuds as an apache wsgi module:
[root@server1 conf.modules.d]# cat 10-wsgi-python3.conf
# NOTE: mod_wsgi_python3 can not coexist in the same apache process as
# mod_wsgi (python2).  Only load if mod_wsgi is not already loaded.

<IfModule !wsgi_module>
    LoadModule wsgi_module modules/mod_wsgi_python3.so
</IfModule>

WSGIPythonPath /opt/openuds/server/src
WSGIDaemonProcess uds user=apache group=apache threads=25 python-path=/opt/openuds/server/src
WSGIProcessGroup uds
WSGIScriptAlias / /opt/openuds/server/src/server/wsgi.py
WSGIPythonOptimize 2
WSGILazyInitialization off
WSGIApplicationGroup %{GLOBAL}

<Directory /opt/openuds/server/src/server/>
  <Files wsgi.py>
    Require all granted
  </Files>
</Directory>

Alias /static/ /opt/openuds/server/src/static/

<Directory /opt/openuds/server/src/static>
    Require all granted
</Directory>

[root@server1 conf.modules.d]#
But I get a Error 500:
[root@server1 httpd]# cat error_log
[Wed Jan 13 02:42:19.483940 2021] [suexec:notice] [pid 161:tid<PHONE_NUMBER>02016] AH01232: suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed Jan 13 02:42:19.507220 2021] [lbmethod_heartbeat:notice] [pid 161:tid<PHONE_NUMBER>02016] AH02282: No slotmem from mod_heartmonitor
[Wed Jan 13 02:42:19.507939 2021] [http2:warn] [pid 161:tid<PHONE_NUMBER>02016] AH02951: mod_ssl does not seem to be enabled
[Wed Jan 13 02:42:19.576354 2021] [mpm_event:notice] [pid 161:tid<PHONE_NUMBER>02016] AH00489: Apache/2.4.37 (Oracle Linux) mod_wsgi/4.6.4 Python/3.6 configured -- resuming normal operations
[Wed Jan 13 02:42:19.576397 2021] [core:notice] [pid 161:tid<PHONE_NUMBER>02016] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[Wed Jan 13 02:43:44.963357 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877] mod_wsgi (pid=163): Failed to exec Python script file '/opt/openuds/server/src/server/wsgi.py'.
[Wed Jan 13 02:43:44.963422 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877] mod_wsgi (pid=163): Exception occurred processing WSGI script '/opt/openuds/server/src/server/wsgi.py'.
[Wed Jan 13 02:43:44.965262 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877] Traceback (most recent call last):
[Wed Jan 13 02:43:44.965322 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/opt/openuds/server/src/server/wsgi.py", line 34, in <module>
[Wed Jan 13 02:43:44.965331 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     application = get_wsgi_application()
[Wed Jan 13 02:43:44.965339 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/usr/local/lib/python3.6/site-packages/django/core/wsgi.py", line 12, in get_wsgi_application
[Wed Jan 13 02:43:44.965345 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     django.setup(set_prefix=False)
[Wed Jan 13 02:43:44.965355 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/usr/local/lib/python3.6/site-packages/django/__init__.py", line 24, in setup
[Wed Jan 13 02:43:44.965361 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     apps.populate(settings.INSTALLED_APPS)
[Wed Jan 13 02:43:44.965369 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/usr/local/lib/python3.6/site-packages/django/apps/registry.py", line 122, in populate
[Wed Jan 13 02:43:44.965374 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     app_config.ready()
[Wed Jan 13 02:43:44.965382 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/opt/openuds/server/src/uds/__init__.py", line 78, in ready
[Wed Jan 13 02:43:44.965387 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     from . import REST  # To make sure REST initializes all what it needs
[Wed Jan 13 02:43:44.965395 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/opt/openuds/server/src/uds/REST/__init__.py", line 220, in <module>
[Wed Jan 13 02:43:44.965400 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     Dispatcher.initialize()
[Wed Jan 13 02:43:44.965407 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/opt/openuds/server/src/uds/REST/__init__.py", line 213, in initialize
[Wed Jan 13 02:43:44.965413 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     importlib.import_module( __name__ + '.' + package + '.' + name)  # import module
[Wed Jan 13 02:43:44.965420 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/usr/lib64/python3.6/importlib/__init__.py", line 126, in import_module
[Wed Jan 13 02:43:44.965425 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     return _bootstrap._gcd_import(name[level:], package, level)
[Wed Jan 13 02:43:44.965433 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/opt/openuds/server/src/uds/REST/methods/reports.py", line 39, in <module>
[Wed Jan 13 02:43:44.965448 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     from uds import reports
[Wed Jan 13 02:43:44.965456 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/opt/openuds/server/src/uds/reports/__init__.py", line 49, in <module>
[Wed Jan 13 02:43:44.965462 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     from uds.core import reports
[Wed Jan 13 02:43:44.965469 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/opt/openuds/server/src/uds/core/reports/__init__.py", line 33, in <module>
[Wed Jan 13 02:43:44.965475 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     from .report import Report
[Wed Jan 13 02:43:44.965482 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/opt/openuds/server/src/uds/core/reports/report.py", line 37, in <module>
[Wed Jan 13 02:43:44.965487 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     from weasyprint import HTML, CSS, default_url_fetcher
[Wed Jan 13 02:43:44.965495 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/usr/local/lib/python3.6/site-packages/weasyprint/__init__.py", line 473, in <module>
[Wed Jan 13 02:43:44.965500 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     from .document import Document, Page  # noqa isort:skip
[Wed Jan 13 02:43:44.965507 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/usr/local/lib/python3.6/site-packages/weasyprint/document.py", line 23, in <module>
[Wed Jan 13 02:43:44.965513 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     from .draw import draw_page, stacked
[Wed Jan 13 02:43:44.965520 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/usr/local/lib/python3.6/site-packages/weasyprint/draw.py", line 16, in <module>
[Wed Jan 13 02:43:44.965525 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     from .images import SVGImage
[Wed Jan 13 02:43:44.965533 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/usr/local/lib/python3.6/site-packages/weasyprint/images.py", line 14, in <module>
[Wed Jan 13 02:43:44.965538 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     import cairosvg.parser
[Wed Jan 13 02:43:44.965545 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/usr/local/lib/python3.6/site-packages/cairosvg/__init__.py", line 99, in <module>
[Wed Jan 13 02:43:44.965550 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     svg2svg.__doc__ = surface.Surface.convert.__doc__.replace(
[Wed Jan 13 02:43:44.965569 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877] AttributeError: 'NoneType' object has no attribute 'replace'
[Wed Jan 13 02:43:45.206417 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>52448] [remote <IP_ADDRESS>:59878] mod_wsgi (pid=163): Failed to exec Python script file '/opt/openuds/server/src/server/wsgi.py'.
[Wed Jan 13 02:43:45.206500 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>52448] [remote <IP_ADDRESS>:59878] mod_wsgi (pid=163): Exception occurred processing WSGI script '/opt/openuds/server/src/server/wsgi.py'.
[Wed Jan 13 02:43:45.206628 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>52448] [remote <IP_ADDRESS>:59878] Traceback (most recent call last):
[Wed Jan 13 02:43:45.206666 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>52448] [remote <IP_ADDRESS>:59878]   File "/opt/openuds/server/src/server/wsgi.py", line 34, in <module>
[Wed Jan 13 02:43:45.206673 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>52448] [remote <IP_ADDRESS>:59878]     application = get_wsgi_application()
[Wed Jan 13 02:43:45.206681 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>52448] [remote <IP_ADDRESS>:59878]   File "/usr/local/lib/python3.6/site-packages/django/core/wsgi.py", line 12, in get_wsgi_application
[Wed Jan 13 02:43:45.206686 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>52448] [remote <IP_ADDRESS>:59878]     django.setup(set_prefix=False)
[Wed Jan 13 02:43:45.206702 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>52448] [remote <IP_ADDRESS>:59878]   File "/usr/local/lib/python3.6/site-packages/django/__init__.py", line 24, in setup
[Wed Jan 13 02:43:45.206707 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>52448] [remote <IP_ADDRESS>:59878]     apps.populate(settings.INSTALLED_APPS)
[Wed Jan 13 02:43:45.206729 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>52448] [remote <IP_ADDRESS>:59878]   File "/usr/local/lib/python3.6/site-packages/django/apps/registry.py", line 83, in populate
[Wed Jan 13 02:43:45.206745 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>52448] [remote <IP_ADDRESS>:59878]     raise RuntimeError("populate() isn't reentrant")
[Wed Jan 13 02:43:45.206776 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>52448] [remote <IP_ADDRESS>:59878] RuntimeError: populate() isn't reentrant

Nothing appear in uds.log file.
Thanks a lot in advance.

Hi,
your problem seems to come from "cairo.parser", from here exactly:
[Wed Jan 13 02:43:44.965533 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/usr/local/lib/python3.6/site-packages/weasyprint/images.py", line 14, in
[Wed Jan 13 02:43:44.965538 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     import cairosvg.parser
[Wed Jan 13 02:43:44.965545 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/usr/local/lib/python3.6/site-packages/cairosvg/init.py", line 99, in
[Wed Jan 13 02:43:44.965550 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     svg2svg.doc = surface.Surface.convert.doc.replace(
Seems that something is missing on your cairo installation, and as soon as weasyprint tries to load it, it fails...
Hope this helps :).
Note: try an "import cairo.parser" from ipython for example, to try to get something more. Weasyprint tries to load it, but it cannot... May some library is missing in your platform?

Hi,
your problem seems to come from "cairo.parser", from here exactly:
[Wed Jan 13 02:43:44.965533 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/usr/local/lib/python3.6/site-packages/weasyprint/images.py", line 14, in
[Wed Jan 13 02:43:44.965538 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     import cairosvg.parser
[Wed Jan 13 02:43:44.965545 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]   File "/usr/local/lib/python3.6/site-packages/cairosvg/init.py", line 99, in
[Wed Jan 13 02:43:44.965550 2021] [wsgi:error] [pid 163:tid<PHONE_NUMBER>59744] [remote <IP_ADDRESS>:59877]     svg2svg.doc = surface.Surface.convert.doc.replace(
Seems that something is missing on your cairo installation, and as soon as weasyprint tries to load it, it fails...
Hope this helps :).
Note: try an "import cairo.parser" from ipython for example, to try to get something more. Weasyprint tries to load it, but it cannot... May some library is missing in your platform?

I have checked cairo and looks it is correctly installed.
There are some differences between the requirements published in

I have checked cairo and looks it is correctly installed.
There are some differences between the requirements published in

Hi,
I have checked cairo and cairosvg and looks they are correctly installed.
[root@server1]# python3
Python 3.6.8 (default, Nov  5 2020, 18:03:20)
[GCC 8.3.1 20191121 (Red Hat 8.3.1-5.0.1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import cairo
>>> import cairo.parser
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'cairo.parser'
>>> cairo.version
'1.16.3'
>>> import cairosvg
>>> import cairosvg.parser
>>> from cairosvg import svg2svg
>>> svg2svg.__doc__="hola"
>>>

>>>

[root@server1]# python3
Python 3.6.8 (default, Nov 5 2020, 18:03:20)
[GCC 8.3.1 20191121 (Red Hat 8.3.1-5.0.1)] on linux
Type "help", "copyright", "credits" or "license" for more information.

from cairosvg import surface
from cairosvg import svg2svg
svg2svg.doc=surface.Surface.convert.doc.replace('the format for this class', 'SVG')
print(svg2svg.doc)
Convert an SVG document to SVG.

    Specify the input by passing one of these:

    :param bytestring: The SVG source as a byte-string.
    :param file_obj: A file-like object.
    :param url: A filename.

    Give some options:

    :param dpi: The ratio between 1 inch and 1 pixel.
    :param parent_width: The width of the parent container in pixels.
    :param parent_height: The height of the parent container in pixels.
    :param scale: The ouptut scaling factor.
    :param unsafe: A boolean allowing XML entities and very large files
                   (WARNING: vulnerable to XXE attacks and various DoS).

    Specifiy the output with:

    :param write_to: The filename of file-like object where to write the
                     output. If None or not provided, return a byte string.

    Only ``bytestring`` can be passed as a positional argument, other
    parameters are keyword-only.

The packages installed are slightly different thant the listed in the requirements document:
[root@server1]# pip3 list
Package                 Version
----------------------- ---------
asgiref                 3.3.1
bcrypt                  3.2.0
bitarray                1.6.1
cairocffi               1.2.0
CairoSVG                2.5.1
certifi                 2020.12.5
cffi                    1.14.4
chardet                 4.0.0
cryptography            2.9.2
cssselect2              0.4.1
cycler                  0.10.0
defusedxml              0.6.0
Django                  3.1.5
dnspython               2.1.0
gpg                     1.13.1
html5lib                1.1
idna                    2.10
kiwisolver              1.3.1
lxml                    4.6.2
matplotlib              3.3.3
mod-wsgi                4.6.4
mysqlclient             2.0.3
numpy                   1.19.5
ovirt-engine-sdk-python 4.4.9
paramiko                2.7.2
Pillow                  8.1.0
pip                     20.3.3
ply                     3.9
pyasn1                  0.3.7
pyasn1-modules          0.1.5
pycairo                 1.16.3
pycparser               2.14
pycrypto                2.6.1
pycurl                  <IP_ADDRESS>
PyNaCl                  1.4.0
pyOpenSSL               19.1.0
pyparsing               2.4.7
Pyphen                  0.10.0
python-dateutil         2.6.1
python-ldap             3.1.0
python-memcached        1.58
pytz                    2020.5
requests                2.25.1
rpm                     4.14.3
setuptools              39.2.0
six                     1.11.0
sqlparse                0.4.1
tinycss2                1.1.0
urllib3                 1.26.2
WeasyPrint              52.2
webencodings            0.5.1
xml-marshaller          1.0.2

Any help will be welcome.
Thansk a lot in advance
Ó

Hi,
I have checked cairo and cairosvg and looks they are correctly installed.
[root@server1]# python3
Python 3.6.8 (default, Nov  5 2020, 18:03:20)
[GCC 8.3.1 20191121 (Red Hat 8.3.1-5.0.1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import cairo
>>> import cairo.parser
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ModuleNotFoundError: No module named 'cairo.parser'
>>> cairo.version
'1.16.3'
>>> import cairosvg
>>> import cairosvg.parser
>>> from cairosvg import svg2svg
>>> svg2svg.__doc__="hola"
>>>

>>>

[root@server1]# python3
Python 3.6.8 (default, Nov 5 2020, 18:03:20)
[GCC 8.3.1 20191121 (Red Hat 8.3.1-5.0.1)] on linux
Type "help", "copyright", "credits" or "license" for more information.

from cairosvg import surface
from cairosvg import svg2svg
svg2svg.doc=surface.Surface.convert.doc.replace('the format for this class', 'SVG')
print(svg2svg.doc)
Convert an SVG document to SVG.

    Specify the input by passing one of these:

    :param bytestring: The SVG source as a byte-string.
    :param file_obj: A file-like object.
    :param url: A filename.

    Give some options:

    :param dpi: The ratio between 1 inch and 1 pixel.
    :param parent_width: The width of the parent container in pixels.
    :param parent_height: The height of the parent container in pixels.
    :param scale: The ouptut scaling factor.
    :param unsafe: A boolean allowing XML entities and very large files
                   (WARNING: vulnerable to XXE attacks and various DoS).

    Specifiy the output with:

    :param write_to: The filename of file-like object where to write the
                     output. If None or not provided, return a byte string.

    Only ``bytestring`` can be passed as a positional argument, other
    parameters are keyword-only.

The packages installed are slightly different thant the listed in the requirements document:
[root@server1]# pip3 list
Package                 Version
----------------------- ---------
asgiref                 3.3.1
bcrypt                  3.2.0
bitarray                1.6.1
cairocffi               1.2.0
CairoSVG                2.5.1
certifi                 2020.12.5
cffi                    1.14.4
chardet                 4.0.0
cryptography            2.9.2
cssselect2              0.4.1
cycler                  0.10.0
defusedxml              0.6.0
Django                  3.1.5
dnspython               2.1.0
gpg                     1.13.1
html5lib                1.1
idna                    2.10
kiwisolver              1.3.1
lxml                    4.6.2
matplotlib              3.3.3
mod-wsgi                4.6.4
mysqlclient             2.0.3
numpy                   1.19.5
ovirt-engine-sdk-python 4.4.9
paramiko                2.7.2
Pillow                  8.1.0
pip                     20.3.3
ply                     3.9
pyasn1                  0.3.7
pyasn1-modules          0.1.5
pycairo                 1.16.3
pycparser               2.14
pycrypto                2.6.1
pycurl                  <IP_ADDRESS>
PyNaCl                  1.4.0
pyOpenSSL               19.1.0
pyparsing               2.4.7
Pyphen                  0.10.0
python-dateutil         2.6.1
python-ldap             3.1.0
python-memcached        1.58
pytz                    2020.5
requests                2.25.1
rpm                     4.14.3
setuptools              39.2.0
six                     1.11.0
sqlparse                0.4.1
tinycss2                1.1.0
urllib3                 1.26.2
WeasyPrint              52.2
webencodings            0.5.1
xml-marshaller          1.0.2

Any help will be welcome.
Thansk a lot in advance
Ó

I'ts strange,
Some advices:
1.- We use python 3.7 for all our tests, not python 3.6 (i think there should be no problem with 3.6 anyway, just a comment)
2.- Have you tried to run "python3 manage.py runserver 0:8000" for example, to see if it starts without wsgi?
3.- Do not use "master". Master, as noticed on main page "readme", is always under heavy development, and it's not normally functional. Use the 3.0 branch instead.
4.- I have not tried apache on new 3.x branches, so my help is very limited, sorry :(,

I'ts strange,
Some advices:
1.- We use python 3.7 for all our tests, not python 3.6 (i think there should be no problem with 3.6 anyway, just a comment)
2.- Have you tried to run "python3 manage.py runserver 0:8000" for example, to see if it starts without wsgi?
3.- Do not use "master". Master, as noticed on main page "readme", is always under heavy development, and it's not normally functional. Use the 3.0 branch instead.
4.- I have not tried apache on new 3.x branches, so my help is very limited, sorry :(,


Joey dev

Finish week 2 tutorial

I add the link to my deployed site~ Feel free to leave a message there XD


(PUP-10677) use puppet ruby in puppet_gem provider

Before this commit, on Windows, puppet_gem provider
was relying on puppet-agent to set puppet bin first
in PATH. With the changes in https://github.com/puppetlabs/puppet-agent/pull/1973
puppet bin is now appended in PATH so we need to explicitly
set the full path to gemcommand.

depends on: https://github.com/puppetlabs/puppet-agent/pull/1973

CLA signed by all contributors.

I've looked into adding an acceptance to this, especially for windows but because we don't have system ruby installed on Windows, that would make a very slow test.

tests/provider/package/puppet_gem.rb passed in 37.01 seconds
      Test Suite: tests @ 2020-09-21 14:26:56 +0300

      - Host Configuration Summary -

              - Test Case Summary for suite 'tests' -
       Total Suite Time: 37.01 seconds
      Average Test Time: 37.01 seconds
              Attempted: 1
                 Passed: 1
                 Failed: 0
                Errored: 0
                Skipped: 0
                Pending: 0
                  Total: 1

      - Specific Test Case Status -

Becase INSTALLDIR/puppet/bin is added to path, gem provider installs gem into Puppet's if system ruby in not available. Need to see if removing puppet/bin from path breaks anything


Testing new leaflet 1.8.0-beta.0 with markerCluster

[x] I'm reporting a bug, not asking for help
[x] I'm sure this is a Leaflet.MarkerCluster code issue, not an issue with my own code nor with the framework I'm using (Cordova, Ionic, Angular, React…)
[x] I've searched through the issues to make sure it's not yet reported

I'm testing a new leaflet version.
How to reproduce

Leaflet version I'm using: 1.8.0-beta.0
Leaflet.MarkerCluster version I'm using: 1.5.4
Browser (with version) I'm using: All ;)
OS/Platform (with version) I'm using: Windows 10

Minimal example reproducing the issue
let markers = L.markerClusterGroup();

for (let i = 0; i < points.length; i++) {
  const [lat, lng, title] = points[i];
  let marker = L.marker(new L.LatLng(lat, lng));
  marker.bindPopup(title);
  markers.addLayer(marker);
}

map.addLayer(markers);

The error that appears is:
Point.js:67 Uncaught TypeError: Cannot read properties of undefined (reading 'x')
    at p._subtract (Point.js:67:19)
    at p.subtract (Point.js:63:23)
    at i._panOnFocus (Marker.js:397:29)
    at HTMLDivElement.o (DomEvent.js:108:13)

This seems to be related: https://github.com/Leaflet/Leaflet/discussions/8044#discussioncomment-2426002
Fix got merged into Leaflet:main https://github.com/Leaflet/Leaflet/pull/8084

Thanks for the information, in this case I am closing the issue


Package Request: Rainmeter

Package Requested

[x] I would like someone else to build the manifest.
[x] I would like help so I can submit the manifest.
[x] I have performed a search and couldn't find this package.
[ ] I think there is a new version available and I have provided the URL.

Manifest:
Fill out as much of the manifest metadata you can:
PackageIdentifier:   # Rainmeter.Rainmeter
PackageVersion:      # <IP_ADDRESS>21
PackageLocale:       # meta-data locale (example: "en-US")
Publisher:           # Rainmeter
PackageName:         # Rainmeter
License:             # GNU GPL v2
ShortDescription:    # desktop customization tool
Installers:
 - Architecture:     # Neutral
   InstallerType:    # EXE
   InstallerUrl:     # https://github.com/rainmeter/rainmeter/releases/download/v<IP_ADDRESS>21/Rainmeter-4.3.1.exe
   InstallerSha256:  # EB8F0390F4919C5A2A16B0FF9D5C181DED835ACBEC12E60984BC9BBC3A1F2EF9
ManifestType: singleton
ManifestVersion: 1.0.0

https://github.com/microsoft/winget-pkgs/pull/868
https://github.com/microsoft/winget-pkgs/pull/14043
https://github.com/microsoft/winget-pkgs/pull/15086
https://github.com/microsoft/winget-pkgs/pull/15156
https://github.com/microsoft/winget-pkgs/pull/16145

This application does not support silent installation.


Completely fails when any part of wildcard has "__"

while trying to test some LoRAs, one of them had __ as part of the name, ie: LoRA:artist__style:1 which broke the extension. is there a setting or way to just have the extension ignore a line featuring an odd number of __s instead of failing completely?

You can change the wildcard wrap syntax: https://github.com/adieyal/sd-dynamic-prompts?tab=readme-ov-file#changing-syntax

@akx I see, that's another solution, thanks.