Can we use regular nox (and not the special native-venv nox fork?)

How would this feature be useful?

If we switched to regular nox (and not @cs01's) fork we could normalize our flow and take advantage of nox development and bug fixes.
Describe the solution you'd like

The comment in noxfile.py says to use @cs01's fork of nox...
# until this is fixed in nox. See
# https://github.com/theacodes/nox/issues/199

Currently nox theacodes/nox#199 is closed, and a patch (theacodes/nox#231) merged.  nox has option @nox.session(venv_backend='venv') that can allow the use of a venv backend.
Can we switch to this now?  Is there any reason to keep using the special fork of nox?
Describe alternatives you've considered

Alternative would be to keep doing what we're doing.  However I'm starting to wonder how stale the special fork of nox is getting.

Is the venv-virtualenv distinction actually relevant now? virtualenv now uses the same mechanism as venv on Python 3.

I just tried plain nox with venv_backend='venv' and at least that works fine.
I'm waiting for #509 to land before doing more testing.

Ok, also plain nox and no special venv_backend works.  (Meaning virtualenv works as @uranusjr suggested).  I disabled the assert_not_in_virtualenv() helper to test this.
@cs01 what used to break in the tests with virtualenv?  Would it be obvious (like tests failing) or was it something more subtle to look out for?

The issue was that from within a nox task, virtual environments were not able to be created. This is a corner case for nox usage that obviously pipx exploits heavily.
IIRC it had to do primarily with the python path resolution. If it works on vanilla nox now, that is great. I have been stressing about my custom nox branch for a while, so I am happy to delete it if things are working now.

The assert_not_in_virtualenv() wasn't a venv vs virtualenv thing, it was just that creating a virtual environment from within one was failing (I think).


Update Composer dependencies (2022-09-21-00-04)

Visual regression test passed!
View the visual regression test report


made UI changes on campground page

📋 Description
I have made the UI changes as suggested where I have changes the layout of the buttons, changed the color scheme of the buttons suggested and also added hover effect on the buttons.

✅ Checklist
Before submitting the PR, please make sure you have completed the following:

[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] I have made corresponding changes to the documentation (if applicable).
[x] My changes generate no new warnings.
[x] I have tested it locally and it works fine.
[x] Any dependent changes have been merged and published in downstream modules.

🏷 Types of Changes
What type of changes does your code introduce? (Check all that apply)

[ ] Bug fix (non-breaking change which fixes an issue) 🐛

[ ] New feature (non-breaking change which adds functionality) ✨

[x] UI enhancement (non-breaking change which enhances UI) 🎨

[ ] Documentation update 📚

Fixes #218

Reminder:
Please ensure your pull request is made to the test branch, not main.
Thank you for contributing to VigneshDevHub! We look forward to reviewing your PR and getting it merged!

Hey @anishka25 , can you please make sure the other two buttons have the same background color as the sort button? Thanks!

did the changes @Vignesh025

Thankyou for Contributing!


CoreML wakeword detection

Based on @kwylez's port of spokestack-android's tensorflow-lite model-based wakeword detector. There is a default model and configuration included, and an example usage for testing.

 Spokestack iOS integrate CoreML-based wakeword

There is a heap overflow memory bug in WitVAD but otherwise, this implementation is working. We will port WebRTC's VAD in a future PR and use that instead.


Can I export the actual sensor data of ego veicle? The same as it in HUD, e.g. speed, compass

Hi,
Can I export the actual sensor data of ego veicle? The same as it in HUD, e.g. speed, compass etc. And then I want it to show in a another window.
Could someone give me a advice? Thanks!
Anna

@bernatx could you follow up with this please?


web xml rundeck version logic

https://github.com/Webtrends/rundeck/commit/bf808ce99a1343ec5b2ca86d9bd98804a70bbaad prevents rundeck 2.7.0

I think this can be solved by reading the version into rubygems version parsing
https://ruby-doc.org/stdlib-2.1.0/libdoc/rubygems/rdoc/Gem/Requirement.html

@atheiman https://github.com/Webtrends/rundeck/pull/153 contains the implementation you mentioned

Closing this issue as was resolved in #153 and there is now conditional logic on rundeck version in the relevant templates


Avoid loading topography for calculating bandwidth

For this I need an enhancement on PyCo's side. Opened an issue for that: https://github.com/pastewka/PyCo/issues/263

This has been fixed in #758


MSID: 103425 Version: 1 DOI: 10.1101/2<IP_ADDRESS>2176

MSID: 103425
Version: 1
Preprint DOI: https://doi.org/10.1101/2<IP_ADDRESS>2176
Step 1. Awaiting reviews
Editorial to post reviews via hypothesis
Useful links:

DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=103425
New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
Reviews on sciety: https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>2176

For trouble shooting (e.g. no Docmaps available):

DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint
Production QC content ahead of publication
Instructions:

QC preview: https://prod--epp.elifesciences.org/previews/103425v1
Update ticket with any problems (add blocked label)
When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
Move card to next column
(At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

Preprint DOI :  https://doi.org/10.1101/2<IP_ADDRESS>2176
Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/103425/v1/reviews
To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex
This step adds the reviewed preprint to the homepage: https://elifesciences.org
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Useful links:

Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested
Waiting for PDF to be generated
Useful links:

PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo
Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/
Step 6: Done!

[ ] Kettle is on!

OK to proceed


Add an option to override showHideValidationErrorForField

Hi I had to override how classes are added to the controls. I did expose this function in the Sync library so it can be overridden. It may be useful for others to.
https://github.com/eriksimonic/FormEditor/blob/master/Source/Umbraco/JS/FormEditor/FormEditorSync.js
Regards
Erik

Hey @eriksimonic,
Nice. I'll test it out as soon as I can and merge it :)
Thanks!


Replace mustache and fmt::format with std::format.

Mustache fails to test at compile time and could easily be replaced with std::format. Additionally, we are using fmt::format which can be replaced with std::format.
Moving to std::format can only be resolved when we switch to a C++20 minimum compiler spec.
If we'd like to remove Mustache before C++20, we can use fmt::format inseat od std::format and write and additional issue to update to std::format later.

One option is to make the format code look like this:
constexpr std::string_view add_contract_template = {
   "file(GLOB {}-source ${CMAKE_CURRENT_SOURCE_DIR}/../../../apps/{}/*{})\n" // target name, object name, source extension
   "add_contract({} {} ${{}-source})\n\n"};                                  // object name, target name, target name

constexpr std::string_view add_library_template = {
   "file(GLOB {}-source ${CMAKE_CURRENT_SOURCE_DIR}/../../../libs/{}/*{})\n\n" // target name, object name, source extension
   "add_library({} ${{}-source})\n\n"};                                        // target name, target name

Another is to make it look like something like this:
constexpr std::string set_vals = {
   "set(APJ_TARGET_NAME \"{}\")\n"
   "set(APJ_OBJECT_NAME \"{}\")\n"
   "set(APJ_EXT \"{}\")\n"};

constexpr std::string_view add_contract_template = {
   "file(GLOB ${APJ_TARGET_NAME}-source ${CMAKE_CURRENT_SOURCE_DIR}/../../../apps/${APJ_OBJECT_NAME}/*${APJ_EXT})\n"
   "add_contract(${APJ_OBJECT_NAME} ${APJ_TARGET_NAME} ${${APJ_TARGET_NAME}-source})\n\n"};

constexpr std::string_view add_library_template = {
   "file(GLOB ${APJ_TARGET_NAME}-source ${CMAKE_CURRENT_SOURCE_DIR}/../../../libs/${APJ_OBJECT_NAME}/*${APJ_EXT})\n\n"
   "add_library(${APJ_TARGET_NAME} ${${APJ_TARGET_NAME}-source})\n\n"};

@larryk85 There are two additional issues beyond compile time checking making std::format preferable to Mustache.
The first is that Mustache is a non-standard library that essentially duplicates the functionality of a standard one.
The second issue is it's lack of escape mechanism for braces in the source requiring some workaround for use with cmake files.
Given that we are committed to standard libraries and are already using format, it seems like a no brainer to switch away from Mustache.
I wouldn't bet money on it, but I think the number of lines of code (number of characters even) should be about the same between the two solutions; however, the format code should be more familiar to most of us. Of course, removing the Mustache repo reduces the number of lines of code.
I think this is a positive maintenance improvement.

In fact, here's some sample code, untested but you get the idea.
            // as is with workaround
            s << temp.render(datum{"obj_name", obj.name()}
                                  ("target_name", target_name(obj))
                                  ("source_ext", system::extension(obj.language()))
                                  ("dollar_brace", "${")); // dollar_brace must be "${" to work around Mustache issue

            // first example above
            std::format_to(std::ostream_iterator<char>(s), temp,
                           target_name(obj), obj.name(), system::extension(obj.language()),
                           obj.name(), target_name(obj), target_name(obj));

            // second example above
            std::format_to(std::ostream_iterator<char>(s), set_vals, target_name(obj), obj.name(), system::extension(obj.language()));
            s << temp;

Here's the proposed code (#41):
            km::mustache cmake::add_contract_template = {
               "file(GLOB {{target_name}}-source ${CMAKE_CURRENT_SOURCE_DIR}/../../../apps/{{obj_name}}/*{{source_ext}})\n"
               "add_contract({{obj_name}} {{target_name}} {{dollar_brace}}{{target_name}}-source})\n\n"};

            km::mustache cmake::add_library_template = {
               "file(GLOB {{target_name}}-source ${CMAKE_CURRENT_SOURCE_DIR}/../../../libs/{{obj_name}}/*{{source_ext}})\n\n"
               "add_library({{target_name}} {{dollar_brace}}{{target_name}}-source})\n\n"};

            s << temp.render(datum{"obj_name", obj.name()}
                                  ("target_name", target_name(obj))
                                  ("source_ext", system::extension(obj.language()))
                                  ("dollar_brace", "${")); // dollar_brace must be "${" to work around Mustache issue

Here's the same code with fmt::format or std::format:
           constexpr std::string_view add_contract_template = {      // 0: object name, 1: target name, 2: source extension
               "file(GLOB {1}-source ${CMAKE_CURRENT_SOURCE_DIR}/../../../apps/{0}/*{2})\n"
               "add_contract({0} {1} ${{1}-source})\n\n"};

            constexpr std::string_view add_library_template = {       // 0: object name, 1: target name, 2: source extension
               "file(GLOB {1}-source ${CMAKE_CURRENT_SOURCE_DIR}/../../../libs/{0}/*{2})\n\n"
               "add_library({0} ${{1}-source})\n\n"};

            std::format_to(std::ostream_iterator<char>(s), temp,
                  target_name(obj),
                  obj.name(),
                  system::extension(obj.language()));

Really not that much different.

@larryk85 There are two additional issues beyond compile time checking making std::format preferable to Mustache.
The first is that Mustache is a non-standard library that essentially duplicates the functionality of a standard one.
The second issue is it's lack of escape mechanism for braces in the source requiring some workaround for use with cmake files.
Given that we are committed to standard libraries and are already using format, it seems like a no brainer to switch away from Mustache.
I wouldn't bet money on it, but I think the number of lines of code (number of characters even) should be about the same between the two solutions; however, the format code should be more familiar to most of us. Of course, removing the Mustache repo reduces the number of lines of code.
I think this is a positive maintenance improvement.

I'm not sure what you mean by "mustache is not standard", mustache is a standard for templating. https://github.com/mustache/spec/tree/master/specs.
I'm fine with the removal, but I still don't see the big advantage.  Mustache also has far more functionality than fmt. Albeit, we aren't currently using that functionality, it's not a 1-1 replacement per se.

Re standard: https://isocpp.org/
I agree, this is not a 1:1 replacement. And the advantage is minor: one less dependency and one less hackey workaround. (Unless there was an escape mechanism I didn't see. But since no one raised their hand to point to it...)
This was closed in #41.


Sentry 404ing in stand-alone Bucket Brigade

Sentry should probably not be enabled for standalone bucket brigade at all, but as it is it is not configured correctly.  Every time there is an error I get something like:
GET<EMAIL_ADDRESS>-> 404
POST https://o490365.ingest.sentry.io/api/5554165/store/?sentry_key=d88678349f5d4e20b707882f78f2f78e&sentry_version=7 -> 200

It is possible that this would not happen for someone else, and only started happening to me after I was hit by https://github.com/gwillen/solstice-audio-test/issues/116, which caused my browser to send a ridiculous number of requests to Sentry?
This crashes the browser if I run into an error that is at all frequent.
My preference would be to remove Sentry, but if whoever added it wants to keep it perhaps we need rate limiting?

Removed a while ago


Update Lenovo.ThinInstaller.locale.en-US.yaml

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Pull request contains merge conflicts.

Make sure to pull the latest changes from the upstream's master branch and do your changes in separate branch which is always synced up with the master branch.


Graphql support

Hi, thanks for the work on this very useful library.
This pull request adds some information on how to easily use this library on a Graphql setup.
Had to change some bits in the interceptor class to make it easier to extend into.

First of all thanks for coming with this idea. However, I couldn't make it work by just doing simple usage. Can you share an example repo that works with this forked version? I couldn't receive requests and responses on rate-limiter side.  If you show me how you do that point then I can make some optimizations there.

@Jylth  First of all thanks for coming with this idea. However, I couldn't make it work by just doing simple usage. Can you share an example repo that works with this forked version? I couldn't receive requests and responses on rate-limiter side. If you show me how you do that point then I can make some optimizations there.

Hello @ozkanonur, pleasure to help.
What do you mean exactly by simple usage?
I tested the following use cases and i didn't notice any issues with them:
GraphQL Query using a custom extended RateLimiterInterceptor like explained in the modified section of the README

Using express
Using fastify
As a class and method level interceptor through UseInterceptors
As a global interceptor through APP_INTERCEPTOR provider
With RateLimiter decorator

I also tested traditional controller endpoints with the initial RateLimiterInterceptor in the same use cases as above to see if i didn't break anything but those were also working correctly.
Also if you don't mind, i will add some unit tests for the behaviors listed above in a different pull request.

Hello @ozkanonur, pleasure to help.
What do you mean exactly by simple usage?
I tested the following use cases and i didn't notice any issues with them:
GraphQL Query using a custom extended RateLimiterInterceptor like explained in the modified section of the README

Using express
Using fastify
As a class and method level interceptor through UseInterceptors
As a global interceptor through APP_INTERCEPTOR provider
With RateLimiter decorator

I also tested traditional controller endpoints with the initial RateLimiterInterceptor in the same use cases as above to see if i didn't break anything but those were also working correctly.
Also if you don't mind, i will add some unit tests for the behaviors listed above in a different pull request.

It just doesn't work whenever I try. Response is always coming as undefined. I created another branch and then added Graphql (currently only for express based ones) support. There is also a TODO list at end of the documentation, if you want you can help me about them, I am pretty busy with a lot of repositories these days so I am pretty slow to react issues or features on this repository I am sorry about that. And thanks again to make me remember about Graphql support !

To support fastify you will need to pass the context option to the apollo server configuration passing down the correct request/reply object. Like below. So for this lib there is not much you could do about it, just write it in the docs.
example below:
GraphQLModule.forRoot({
  context: ({ request, reply }) => {
    // assigning request to reply.res will make it work with your current implementation.
    reply.req = request
    return { req: request, res: reply }
   }
})

To support fastify you will need to pass the context option to the apollo server configuration passing down the correct request/reply object. Like below. So for this lib there is not much you could do about it, just write it in the docs.
example below:
GraphQLModule.forRoot({
  context: ({ request, reply }) => {
    // assigning request to reply.res will make it work with your current implementation.
    reply.req = request
    return { req: request, res: reply }
   }
})

I am glad that you explain that. Now with version 2.3.0 this library also supports Fastify based Graphql server.


Create subgraph index feedback part3

Feedback from Charles to standardize terms
Additional details for resource quota trouble-shooting

Docs Build status updates of commit 658c807:
:warning: Validation status: warnings

File
Status
Preview URL
Details

academic-services/knowledge-exploration-service/how-to-create-index-from-mag.md
:warning:Warning

Details

academic-services/knowledge-exploration-service/resources-troubleshoot-guide.md
:white_check_mark:Succeeded

academic-services/knowledge-exploration-service/how-to-create-index-from-mag.md

Line 99: [Warning] Cannot find bookmark '#Azure-login-failure-due-to-multiple-subscriptions-or-multiple-tenants-being-tied-to-a-single-Azure-account' in 'knowledge-exploration-service/resources-troubleshoot-guide.md', did you mean '#azure-login-failure-due-to-multiple-subscriptions-or-multiple-tenants-being-tied-to-a-single-azure-account'?
Line 102: [Warning] Cannot find bookmark '#Azure-Batch-service-not-registered' in 'knowledge-exploration-service/resources-troubleshoot-guide.md', did you mean '#azure-batch-service-not-registered'?
Line 125: [Warning] Cannot find bookmark '#Azure-login-failure-due-to-multiple-subscriptions-or-multiple-tenants-being-tied-to-a-single-Azure-account' in 'knowledge-exploration-service/resources-troubleshoot-guide.md', did you mean '#azure-login-failure-due-to-multiple-subscriptions-or-multiple-tenants-being-tied-to-a-single-azure-account'?
Line 135: [Warning] Cannot find bookmark '#Azure-Subscription-quota-limit-reached' in 'knowledge-exploration-service/resources-troubleshoot-guide.md', did you mean '#azure-subscription-quota-limit-reached'?

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

ms.date: 2020-04-15

Update date.

Refers to: academic-services/knowledge-exploration-service/how-to-create-index-from-mag.md:5 in 658c807. [](commit_id = 658c8074cba6176aead96829cd9ecdbe14e2546e, deletion_comment = False)

ms.date: 2020-04-15

Update date.

Refers to: academic-services/knowledge-exploration-service/resources-troubleshoot-guide.md:5 in 658c807. [](commit_id = 658c8074cba6176aead96829cd9ecdbe14e2546e, deletion_comment = False)


App asks for Accessibility Access each time app starts though I deny each time.

Before opening the issue, have you...?

[X] Searched for existing issues
[X] Looked through the wiki
[x] Updated MonitorControl to the latest version (if applicable)

Describe the bug
Each time when booting the app, which is now every time my computer boots, MonitorControl asks for the Accessibility permissions which enable the keyboard brightness controls.
While this is a nice feature, I personally don't feel comfortable giving this app so much power, and would rather use it without this feature.
That being said, I cannot find a way to disable this annoying and repetetive "request" for permission. This app works great, but I might uninstall it if I can't get it to stop harassing me every time I boot up.
Steps to reproduce

Install App
Configure to start at bootup
Boot up computer
Deny Accessibility Permissions
Reboot Computer
Bug happens where it keeps annoying asking for the permissions over and over.

Expected behavior
There is a "Don't Ask Again" checkbox which allows me to permanantly silence the permission request.
Anything else?
Thank you so much for making this awesome app.
Environment Information (please complete the following information)
- macOS version: Monterey 12.0.1
- Mac model: M1 Air
- MonitorControl version: 4.0.2 Build 6965
- Monitor(s): Builtin; 2nd Gen Ipad Pro 12.9"
- Apple Silicon/M1 (yes or no): YES

Hi @fieryWaters, the app should ask for the permissions only if you enable media keys either for volume or brightness control - this permission is required for these functions. If you disable these, then the prompts should stop.


[HOLD] Revert "Theme switching: Going Live! (Add preferences menu entry for ThemePage)"

Reverts Expensify/App#21669

We're not reverting this


#333 corrected text overlap on login page

Related Issue
Text overlap in Login Buttons and changed icons size to match the text
Closes: https://github.com/AKD-01/blogweet/issues/333
Description of Changes
changed the line height in components/loginButtons/index.css, added a font size property in index.js
Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[ ] I have included comments in areas that may be difficult to understand.
[ ] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots

Original
Updated

@AKD-01 can you please review the PR


[WIP] AAF Reader: Reading in markers

This is code implemented by Shahbaz Khan to read in markers from an AAF file -> into an OTIO file.
Co-authored-by: Shahbaz Khan<EMAIL_ADDRESS>

Any known problems with this PR? I have just implemented it on a small scale at the facility and cannot find any as yet

Codecov Report

Merging #479 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #479   +/-   ##
=======================================
  Coverage   81.28%   81.28%
=======================================
  Files          72       72
  Lines        2731     2731
=======================================
  Hits         2220     2220
  Misses        511      511

Flag
Coverage Δ

#py27
81.29% <ø> (ø)
:arrow_up:

#py36
?

#py37
81.29% <ø> (ø)
:arrow_up:

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 1407f4a...254b612. Read the comment docs.


MINOR: [C++][CI] Try to workaround bug in conda-forge benchmark package

Rationale for this change
Work around bug in version 1.8.4 of the benchmark package: https://github.com/conda-forge/benchmark-feedstock/issues/36
Are these changes tested?
By regular CI jobs.
Are there any user-facing changes?
No.

@github-actions crossbow submit -g cpp

@github-actions crossbow submit test-conda-*

@kou @assignUser @raulcd It would be nice to review this quickly as it fixes a couple CI jobs.


Pattern for making make_compact safe

Hi @LukasKalbertodt, I saw your badge for this crate when I was reading the reddit post and thought I'd take a look. I noticed how the make_compact functions break the guarantee of stable indexes, so thought I'd try and see if there was a way to use the borrow checker to keep you from calling make_compact if you were still holding on to an index.
This is the pattern I came up with. There's a new Index<'a> type, which is just a newtyped usize with a lifetime parameter. To do any operations that produce or use an Index, you have to call them on a JailedStableVec<'a>, which you can get by calling .jail() on a normal StableVec. The call to .jail() borrows the StableVec, as do any indexes returned by the methods on the JailedStableVec, and you can't call make_compact until all of the borrows have ended. This way all indexes will be valid. (For the most part. See the end of my doc comment on the jailed module for details of where it falls apart.)
Anyway, this makes things more complicated to use, and for all I know, make_compact may not cause that many bugs, so I can understand if you don't want to incorporate this into the library. I just thought it was a cool pattern, and wanted to share :smiley:

What a nice idea! I love using the borrow checker to catch certain bugs at compile time, especially the kinds of bugs the borrow checker was never designed to catch ;-)
I think I will close this PR, for the reasons you mentioned: it's probably not worth it to add another complex API to catch a few of those bugs. And anyway, the new API doesn't catch all index invalidation bugs, as you already mentioned, too.
So I hope you don't mind me closing this. But thanks again for this experiment ^_^

@LukasKalbertodt Have you read @Gankro's thesis? It has some interesting stuff about using lifetimes to force array indexes to be valid in section 6.3. I was reading it today, and apparently you can force two things to have the same lifetime by using PhantomData<Cell<&'a mut ()>>. I'm not exactly sure how it works, but I managed to use it here.
RFC 1951 (which links to the above paper) mentions "generative existential types" in its unresolved questions section. It sounds like if they are introduced to the language at some point, they could be used to provide a better API with safe indexes here.

@mikeyhew Actually, I have read that thesis! But I might have only skimmed it, because I cannot remember the PhantomData<Cell<...>> trick. That sounds really awesome! I guess it work because Cell (or rather the underlying UnsafeCell) is invariant in regards to T (although I'm far from completely understanding variance in Rust :P).
I did a similar experiment last year; I wrote a blog post about it. Please note that the post still contains some mistakes and there are a lot of possible improvements; I never really came around to fix those. Anyway, the PhantonData<Cell<...>> trick could also really help there! Maybe I'll try it sometime.
And wow, I haven't read the "unresolved questions" you linked. Super interesting stuff!


Create mailing list for core working group

@lgierth or @diasdavid could you make a<EMAIL_ADDRESS>mailing list and add these people to it?

@jbenet
@diasdavid
@whyrusleeping
@flyingzumwalt
@lgierth

Notes:

The actual definition of the core WG and its membership is not fully settled. See https://github.com/ipfs/rfcs/pull/2 -- but we need this mailing list in order to coordinate the work that will finish at RFC so we can formally create WGs.
The contents of this list will probably be made publicly viewable, but in the meantime we need a way to flag conversations for this group.

moved to https://github.com/protocol/it/issues/6


Add examples for encrypted keyfiles

In the case that the private keyfile is encrypted, the CLI tools fail to connect unless the password is passed in via the environment file.  I added some examples in the documentation for this (probably unusual) scenario.
Note that it appears that only SERVER_ADDITIONAL_ERL_ARGS is necessary for rabbitmqctl and others to connect, but I added examples for RABBITMQ_CTL_ERL_ARGS also.

@arch273 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

Thank you! It's a great addition to have 👍


File logging log rotation is broken.

Tested versions
v4.3.stable.arch_linux
v4.2.2.stable.official [15073afe3]
System information
Godot v4.3.stable unknown - Arch Linux #1 SMP PREEMPT_DYNAMIC Thu, 12 Sep 2024 17:21:02 +0000 - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3090 (nvidia; 560.35.03) - AMD Ryzen 7 5800X 8-Core Processor (16 Threads)
Issue description
When file debug/file_logging/enable_file_logging is enabled and debug/file_logging/max_log_files is > 1, files should be logged to the set directory (default "user://logs/godot.log") starting with godot.log (most recent run) and keeping previous runs as godot{datetimestamp}.log. Previously this would correctly maintain the most recent logs but since ~4.3 it has stopped working. Now once the first debug/file_logging/max_log_files have been generated, only the newest (godot.log) gets correctly replaced and the oldest n-1 files are kept forever.
Steps to reproduce
Enable file logging add some print statements and run the game 6 times.
Minimal reproduction project (MRP)
N/A

@Jack-023 Can you try following the same steps on 4.3 dev/beta/RCs to determine when the regression started? You can download them here.

@Calinou just tried Godot_v4.3-beta2_linux.x86_64 and the bug exists there.

Actually just tested in v4.2.2.stable.official [15073afe3] in an older project and it's not working there either so it has been around longer than I thought.
Only godot.log gets overwritten, log files from months ago never change.
I increased the file count from 5 -> 6 and ran a few more times. On the first run, godot.log was renamed with the correct datetime in the name and a new godot.log was created with the newest run. Second run none of the (now 5) files with a datetime in the name were updated/removed and godot.log was overwritten with the latest runs logs.

@pafuent thanks for your work on fixing this! I just ran into this bug myself wondering what was happening for a while; hopefully this'll get merged for 4.4 soon 😊

Could this bug be added back as a release blocker?  The patch looks good from a cursory look (it even adds tests to avoid further regressions!), but it has not been reviewed, approved or merged, and removing the labels here makes the impression that the priority of this bug decreased, which in my opinion, it has not - the file logging feature has been unusable for 2 releases now - which we also found out the "hard way".


Microsoft repository https://packages.microsoft.com/rhel/8/prod/ has invalid repodata

Issue description:
It is not possible sync repository https://packages.microsoft.com/rhel/8/prod/ because there are differences in sha256 checksums.
Repository URL: https://packages.microsoft.com/rhel/8/prod/
Example of affected package:      adutil-preview-0.7.022-1.x86_64.rpm
[MIRROR] adutil-preview-0.7.022-1.x86_64.rpm: Downloading successful, but checksum doesn't match. Calculated: 7450321d76c36418ecee48545724bb98161cb9b14e51a4c5d2a2d5637595b107(sha256)  Expected: 061d903499bbbacdbcc643eab29746a01a267b9aeacb4d10d96a4af957326925(sha256)
[FAILED] adutil-preview-0.7.022-1.x86_64.rpm: No more mirrors to try - All mirrors were already tried without success
## Package adutil-preview-0.7.022-1.x86_64.rpm sha256 checksum verification
7450321d76c36418ecee48545724bb98161cb9b14e51a4c5d2a2d5637595b107  adutil-preview-0.7.022-1.x86_64.rpm
## Information from repodata for package adutil-preview-0.7.022-1.x86_64.rpm
checksum type="sha256" pkgid="YES">061d903499bbbacdbcc643eab29746a01a267b9aeacb4d10d96a4af957326925
location href="adutil-preview-0.7.022-1.x86_64.rpm"
## sha256 checksum differences:
package: 7450321d76c36418ecee48545724bb98161cb9b14e51a4c5d2a2d5637595b107
repodata: 061d903499bbbacdbcc643eab29746a01a267b9aeacb4d10d96a4af957326925
Please verify packages and if necessary regenerate repodata. Thanks

@konstruktoid : Would you be able to verify the claim above from @libor-p ?

There is multiple issues with that repository.
Running sudo rpm -Uvh https://packages.microsoft.com/config/rhel/8/packages-microsoft-prod.rpm as instructed on https://docs.microsoft.com/en-us/windows-server/administration/linux-package-repository-for-microsoft-software fetches the correct RPM but the repo baseurl is incorrect, rhel/8.0/prod should be rhel/8/prod.
[packages-microsoft-com-prod]
name=packages-microsoft-com-prod
baseurl=https://packages.microsoft.com/**rhel/8.0/prod**
enabled=1
gpgcheck=1
gpgkey=https://packages.microsoft.com/keys/microsoft.asc
sslverify=1

$ curl https://packages.microsoft.com/**rhel/8.0/prod**/repodata/repomd.xml

<title>404 Not Found</title>

404 Not Found

nginx/1.16.1

$ curl -s https://packages.microsoft.com/**rhel/8/prod**/repodata/repomd.xml | head -n3
<?xml version="1.0" encoding="UTF-8"?>
<repomd xmlns="http://linux.duke.edu/metadata/repo" xmlns:rpm="http://linux.duke.edu/metadata/rpm">
  <revision>1605745291</revision>

I can however install adutil-preview, except answer the EULA question...
$ sudo dnf install adutil-preview
Last metadata expiration check: 0:02:36 ago on Mon 23 Nov 2020 09:36:41 PM UTC.
Dependencies resolved.
[...]
Install  4 Packages

Total download size: 7.5 M
Installed size: 17 M
Is this ok [y/N]: y
Downloading Packages:
(1/4): krb5-workstation-1.17-18.el8.x86_64.rpm                                                                                601 kB/s | 940 kB     00:01
(2/4): libkadm5-1.17-18.el8.x86_64.rpm                                                                                97 kB/s | 185 kB     00:01
(3/4): realmd-0.16.3-18.el8.x86_64.rpm                                                                                122 kB/s | 233 kB     00:01
(4/4): adutil-preview-0.7.029-1.x86_64.rpm                                                                                2.7 MB/s | 6.1 MB     00:02
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Total                                                                                1.7 MB/s | 7.5 MB     00:04
warning: /var/cache/dnf/packages-microsoft-com-prod-37360e73ce94b4be/packages/adutil-preview-0.7.029-1.x86_64.rpm: Header V4 RSA/SHA256 Signature, key ID be1229cf: NOKEY
packages-microsoft-com-prod                                                                                2.6 kB/s | 983  B     00:00
Importing GPG key 0xBE1229CF:
 Userid     : "Microsoft (Release signing<EMAIL_ADDRESS> Fingerprint: BC52 8686 B50D 79E3 39D3 721C EB3E 94AD BE12 29CF
 From       : https://packages.microsoft.com/keys/microsoft.asc
Is this ok [y/N]: y
Key imported successfully
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                1/1
  Installing       : realmd-0.16.3-18.el8.x86_64                                                                                1/4
  Installing       : libkadm5-1.17-18.el8.x86_64                                                                                2/4
  Installing       : krb5-workstation-1.17-18.el8.x86_64                                                                                3/4
  Installing       : adutil-preview-0.7.029-1.x86_64                                                                                4/4
  Running scriptlet: adutil-preview-0.7.029-1.x86_64                                                                                4/4

Use of adutil requires acceptance of the adutil EULA.
Do you accept the terms of the EULA for adutil as specified at /usr/share/adutil/microsoft_adutil_pre-release_license.md y/N?
Cannot proceed with install since EULA was NOT accepted.
warning: %post(adutil-preview-0.7.029-1.x86_64) scriptlet failed, exit status 1

Error in POSTIN scriptlet in rpm package adutil-preview
  Verifying        : krb5-workstation-1.17-18.el8.x86_6
Error in POSTIN scriptlet in rpm package adutil-preview
  Verifying        : krb5-workstation-1.17-18.el8.x86_64                                                                                1/4
  Verifying        : libkadm5-1.17-18.el8.x86_64                                                                                2/4
  Verifying        : realmd-0.16.3-18.el8.x86_64                                                                                3/4
  Verifying        : adutil-preview-0.7.029-1.x86_64                                                                                4/4

Installed:
  adutil-preview-0.7.029-1.x86_64                    krb5-workstation-1.17-18.el8.x86_64                    libkadm5-1.17-18.el8.x86_64                    realmd-0.16.3-18.el8.x86_64

Complete!
$ sudo dnf install adutil-preview
Last metadata expiration check: 0:00:19 ago on Mon 23 Nov 2020 09:40:36 PM UTC.
Package adutil-preview-0.7.029-1.x86_64 is already installed.
Dependencies resolved.
Nothing to do.
Complete!
$ wget https://packages.microsoft.com/rhel/8/prod/adutil-preview-0.7.029-1.x86_64.rpm
[...]
$ rpm --checksig -v adutil-preview-0.7.029-1.x86_64.rpm
adutil-preview-0.7.029-1.x86_64.rpm:
    Header V4 RSA/SHA256 Signature, key ID be1229cf: OK
    Header SHA1 digest: OK
    V4 RSA/SHA256 Signature, key ID be1229cf: OK
    MD5 digest: OK

$ curl -sSL https://packages.microsoft.com/keys/microsoft.asc > ./microsoft.asc
$ sudo rpm --import ./microsoft.asc
$ rpm --checksig -v adutil-preview-0.7.029-1.x86_64.rpm
adutil-preview-0.7.029-1.x86_64.rpm:
    Header V4 RSA/SHA256 Signature, key ID be1229cf: OK
    Header SHA1 digest: OK
    V4 RSA/SHA256 Signature, key ID be1229cf: OK
    MD5 digest: OK
$ sha256sum adutil-preview-0.7.029-1.x86_64.rpm
acdf7aff04ac72c136e7c009784a0dc33d7aa8ff4af13c4a00239bfc43976a6e  adutil-preview-0.7.029-1.x86_64.rpm
$ grep acdf7aff04ac72c136e7c009784a0dc33d7aa8ff4af13c4a00239bfc43976a6e a7828bf004485feff5b6003f5440fee5f13e1c2cd7247e7dc8ab97039b85eabc-filelists.xml
<package pkgid="acdf7aff04ac72c136e7c009784a0dc33d7aa8ff4af13c4a00239bfc43976a6e" name="adutil-preview" arch="x86_64">

Thanks a lot. That makes it much easier to find out if we are dealing with a documentation repo issue or a software package repo issue.
Looking up rhel/8.0/prod via a web search, there appears to be other tickets for this already here on GitHub, but they are all closed:

https://github.com/Azure/azure-storage-fuse/issues/381
https://github.com/Azure/azure-storage-fuse/issues/396
https://github.com/dotnet/core/issues/4919

There is also a related post in git memory: https://www.gitmemory.com/issue/Azure/azure-storage-fuse/396/686815499
Not quite sure exactly what to make of this, but my most immediate thought is that this might not be fixable by a direct document edit, unless I have missed something obvious.

I'm using repository config file from  https://packages.microsoft.com/config/rhel/8/prod.repo . Content of the file is:
[packages-microsoft-com-prod]
name=packages-microsoft-com-prod
baseurl=https://packages.microsoft.com/rhel/8/prod/
enabled=1
gpgcheck=1
gpgkey=https://packages.microsoft.com/keys/microsoft.asc
This is valid configuration. But issue is with repodata which are not aligned with packages. From my point of view, for example package adutil-preview-0.7.022-1.x86_64.rpm has been updated, but repodata were not re-generated after the change. It is reason why sha256 checksum for repodata and package is different.
Repodata re-generation of https://packages.microsoft.com/rhel/8/prod/ should fix the issue.

Yeah, this isn't a documentation issue, but there doesn't seem to be any other smooth way to report issues like this.
@libor-p, you're correct as well. A repodata re-generation and a verification of packages-microsoft-prod.rpm should be done.

Any word on this?  I'm setting up Foreman/Katello and adding the Microsoft Repos and the sync is failing checksum "A file failed validation due to checksum."
Upstream URLs I'm using are
https://packages.microsoft.com/rhel/7/prod/
and
https://packages.microsoft.com/rhel/8/prod/

Wish there were some form of "Feedback Hub" link to use for that repo or related page for Q&A, but I don't know the topic or subject well enough. @konstruktoid : Any updated further thoughts on this issue? 🙂

I sent an email to<EMAIL_ADDRESS>to see if they have any leads to help.  3 months to have a broken repo doesn't seem right.

Hi my team manages the repos at packages.microsoft.com, this issue was forwared to us. I checked on our side and it looks like the latest version of the adutil-preview package wasn't copied onto the mirrors properly. I manually pushed the package to the rhel 8 repo, could you try refreshing and installing the package again?
For the rhel 7 repo, is it failing on installing the adutil-preview package?

I wish I could say.  I'm trying to sync the repo's in Foreman Katello.  The RHEL 8 repo isn't giving a checksum error anymore, but the CentOS 7 repo still does.
But I still can't get the RHEL 8 repo to sync successfully.  It's not giving any sort of good error, no description:
   "  File \"/usr/lib64/python3.6/json/encoder.py\", line 202, in encode\n" +
   "    return ''.join(chunks)\n",
  "description"=>""},

Microsoft's repos are the only ones that fail.

I reached out to the owners of the package, they have republished the package from the rhel 8 repo. Could you try syncing from there again?

@inbuckle, I can confirm that sync from "https://packages.microsoft.com/rhel/8/prod/" is working again. But please can you also ask for republishing of "https://packages.microsoft.com/rhel/7/prod/"? Sync is still not possible because of different repodata/package sha256 checksum.
Example:
omi-1.6.4-0.ssl_100.ulinux.x64.rpm: Downloading successful, but checksum doesn't match. Calculated: 33d64c8269e16daf7c2ed432fb7881976205d291bb38879fcf40cf6197bc7688(sha256)  Expected: aeb801a2e2155848cdd07f44f9077b920e57ea04f1b550dc1070a07f0f53a106(sha256)

@inbuckle also the sync from https://packages.microsoft.com/sles/12/prod/ and https://packages.microsoft.com/sles/15/prod/ for adutil-preview-0.7.022-1.x86_64.rpm didn't work.
Example:

Microsoft SLES 12 (https://packages.microsoft.com/sles/12/prod/):

E 'adutil-preview-0.7.022-1.x86_64.rpm': Checksum mismatch' ('11e8f178475f38d3c08f592162deb93b6e3b431e34c5dca5219b8f5f42fde9d3' vs '52fa0be87ab10a07ae00313ed819664a93e99c7087a4cd8c3cdd70dd53e55679')

Microsoft SLES 15 (https://packages.microsoft.com/sles/15/prod/):

E 'adutil-preview-0.7.022-1.x86_64.rpm': Checksum mismatch' ('11e8f178475f38d3c08f592162deb93b6e3b431e34c5dca5219b8f5f42fde9d3' vs '52fa0be87ab10a07ae00313ed819664a93e99c7087a4cd8c3cdd70dd53e55679')

Hi,
problem still exist on RHEL7/Centos7, I'm trying setup Foreman with packages-microsoft-com-prod repo and I'm constantly getting checksum error.
Can you people from Microsoft please fix that repo to?
Thanks

As is already mentioned, sync of https://packages.microsoft.com/rhel/7/prod is not possible because of sha256 differences between package and repodata.
Sync repository microsoft-rhel7-prod (https://packages.microsoft.com/rhel/7/prod/) Error:
[MIRROR] omi-1.6.6-0.ssl_100.ulinux.x64.rpm: Downloading successful, but checksum doesn't match. Calculated: e8333668d222facfb7512f508b466514fcf99ce83a8afb39659a2eec836d5efb(sha256)  Expected: 75bec1b40b8a6a21096f27bf9b0514bb1c237af8122096afb8b45e99e4a4cf70(sha256) ",
"[MIRROR] omi-1.6.6-0.ssl_100.ulinux.x64.rpm: Downloading successful, but checksum doesn't match. Calculated: e8333668d222facfb7512f508b466514fcf99ce83a8afb39659a2eec836d5efb(sha256)  Expected: 75bec1b40b8a6a21096f27bf9b0514bb1c237af8122096afb8b45e99e4a4cf70(sha256) ",
"[MIRROR] omi-1.6.6-0.ssl_100.ulinux.x64.rpm: Downloading successful, but checksum doesn't match. Calculated: e8333668d222facfb7512f508b466514fcf99ce83a8afb39659a2eec836d5efb(sha256)  Expected: 75bec1b40b8a6a21096f27bf9b0514bb1c237af8122096afb8b45e99e4a4cf70(sha256) ",
"[MIRROR] omi-1.6.6-0.ssl_100.ulinux.x64.rpm: Downloading successful, but checksum doesn't match. Calculated: e8333668d222facfb7512f508b466514fcf99ce83a8afb39659a2eec836d5efb(sha256)  Expected: 75bec1b40b8a6a21096f27bf9b0514bb1c237af8122096afb8b45e99e4a4cf70(sha256) ",
"[FAILED] omi-1.6.6-0.ssl_100.ulinux.x64.rpm: No more mirrors to try - All mirrors were already tried without success"
Package URL: https://packages.microsoft.com/rhel/7/prod/omi-1.6.6-0.ssl_100.ulinux.x64.rpm
sha256sum omi-1.6.6-0.ssl_100.ulinux.x64.rpm
e8333668d222facfb7512f508b466514fcf99ce83a8afb39659a2eec836d5efb  omi-1.6.6-0.ssl_100.ulinux.x64.rpm
Information from repository metadata for the package:

omi
x86_64

75bec1b40b8a6a21096f27bf9b0514bb1c237af8122096afb8b45e99e4a4cf70
Open Management Infrastructure
omi server

Error confirmation
Package sha256:             e8333668d222facfb7512f508b466514fcf99ce83a8afb39659a2eec836d5efb
Package repodata sha256:    75bec1b40b8a6a21096f27bf9b0514bb1c237af8122096afb8b45e99e4a4cf70
Please regenerate repodata for rhel/7/prod repository. Thanks

https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb seems to be broken as well at the moment. @inbuckle may I ask you to step in again?

@inbuckle If you can, please also look at the RHEL7 and RHEL8 repos. I'm seeing the same checksum errors mentioned above by libor-p on both of them.
http://packages.microsoft.com/rhel/7/prod/
http://packages.microsoft.com/rhel/8/prod/

I'm following the documentation https://docs.microsoft.com/en-us/dotnet/core/install/linux-centos and I'm having an error installing on Cent OS 7.
There is indeed a problem with this walkthrough.

Hi @rsg-roberth, is there an issue with the documentation (https://docs.microsoft.com/en-us/dotnet/core/install/linux-centos)  or does the repository fail?

@konstruktoid Following Documents I can't check the final installation. I believe there are problems with repositories.
Reason: it's been a while (about 8 months), I managed to follow this step-by-step installation of version 3.1

@konstruktoid Following Documents I can't check the final installation. I believe there are problems with repositories.
Reason: it's been a while (about 8 months), I managed to follow this step-by-step installation of version 3.1

I have no issues installing 3.1 or 5.0 on CentOS 7.
$ cat /etc/centos-release
CentOS Linux release 7.9.2009 (Core)
$ sudo yum install dotnet-sdk-5.0
[...]
Installed:
  dotnet-sdk-5.0.x86_64 0:5.0.302-1
$ dotnet --list-sdks
5.0.302 [/usr/share/dotnet/sdk]
$ sudo yum install dotnet-sdk-3.1
[...]
Installed:
  dotnet-sdk-3.1.x86_64 0:3.1.411-1
$ dotnet --list-sdks
3.1.411 [/usr/share/dotnet/sdk]
5.0.302 [/usr/share/dotnet/sdk]

@konstruktoid  I'm on version 7.6.1810, but I don't think that's the problem.
What am I doing:
rpm -Uvh https://packages.microsoft.com/config/centos/7/packages-microsoft-prod.rpm
sudo yum install aspnetcore-runtime-5.0
I believe the problem is with the certificate. What should not happen, because step by step this command is intended to solve: rpm -Uvh https://packages.microsoft.com/config/centos/7/packages-microsoft-prod.rpm

I didn't try to install the runtime packages, can test later.
Are you having the same issues with the SDK?

@konstruktoid Yes, the same certificate error occurs.

According to the image you got issues connecting to the official CentOS repos as well, are you perhaps behind a proxy and can you download the packages manually?

@konstruktoid It is a network that has no restrictions unless there is something on the part of the internet provider.

Well, since you couldn't retrieve the repolist there's more issues than just the Microsoft one.
Can you download a .rpm from a repository manually using curl or wget without any issues?

@konstruktoid I changed the /etc/yum.repos.d/microsoft-prod.repo file
changing the https for http and also changed the /etc/resolv.conf adding in addition to the google ddns the machine's own ip.
I'm going to redo the machine and see what actually solved the problem.
Thank you very much for the guidance.

The problem was in the machine/structure.
I had to change the ddns pointing to google and also to the machine's local ip.
I also changed the links from /etc/yum.repos.d/microsoft-prod.repo replacing https with http.
@konstruktoid  thank you very much.

Glad I could be of assistance @rsg-roberth


Update svgs

Updates the home page svgs.
Most of the changes shown in index are just from running prettier
Updates
Step 2 of How It Works is now the inside image.

Separated phone screens into separate images, so they stack on mobile.

Issues
Can't get the about->healthy communities image to not show the weird vector graphics
Still see a small white stripe at the bottom of the peaking woman image, maybe it hasn't been updated?

The stripe at the bottom of the phones is not correctly placed.  The Figma design has it slightly hidden behind the phones.  I had a hard time doing this, which is why I used a single svg instead of four.  Feel free to go that direction if you can't figure out making look like the below (staging env with 1 svg)

Also, the woman exercising still has those lines on her pants!  Does it not for you locally??

Ah I see, I'll try and get that blue stripe a little further up.
Woman exercising still has lines for me too, I couldn't figure that one out.


new platform: Excalibur

launchpool date TBD
DD reviewed by @sircryptomaxi
https://docs.google.com/document/d/1M9hmCupPtyVQrHMXG5m8-1PSkTwLKcb1Ask1U4VVwB4/edit

pending final check

pending final check


Inappropriate "usage of catch-all clauses" message

Whenever I do something like this:
catch (Exception e) when (e is SomeException || e is SomeOtherException)
Exceptional gives me the message: "Usage of catch-all clauses is not recommended."
Unless I'm seriously misunderstanding the purpose of this suggestion, I don't think it's appropriate here.  It's not a catch-all clause - it's only catching certain Exception types.

Also, I just noticed that the autofix "disable" message doesn't seem to actually disable the message.  I've tried both "Disable once with comment" and "Disable in file with comment"; they do add in lines that look like I imagine they should look:
// ReSharper disable once CatchAllClause
and
// ReSharper disable CatchAllClause
respectively, but the "Usage of catch-all clauses is not recommended" message shows up regardless.


Request for Python 3.8 Support

Hello,
I'm writing to request support for Python 3.8 in your Lightweight Charts Python project.
I have been using your project and find it very useful. However, I would like to use it along with QuantConnect, which currently only supports Python 3.8.
I have done some preliminary testing on my local environment, and it seems that the library functions well with Python 3.8. This preliminary testing was not exhaustive though, so it would be great if you could confirm this compatibility.
I believe Python 3.8 support would make your project even more helpful to a broader audience, and I am eager to hear your thoughts on this.
Thank you for your consideration and for all your work on this project.
Best regards

Hi!
The library should work on 3.8; I had a look through the breaking changes and there doesn't seem to be anything obvious which would prevent it from working.
I'll take a closer look and get back to you, in the mean time if you find any bugs let me know.
Louis

Hey,
After some tests it appears the library runs fine on 3.8, so I have updated the package to reflect this.
Louis


提示错误

UnboundLocalError                         Traceback (most recent call last)
 in <cell line: 101>()
99   return fragments_translated
100
--> 101 fragments_translated = translate_fragments(new_fragments, count_of_sentence_send_once_limit)
102
103 # Save translation as json file
1 frames
 in translate_by_chatgpt(sentences, max_retry_times, deployment_id, model_name, temperature)
73       print(f"==Tranlate Retry with {current_retry_times} times")
74       continue
---> 75   return sentences_translated
76
77 def translate_fragments(fragments, sentence_send_limit=5):
UnboundLocalError: local variable 'sentences_translated' referenced before assignment

Fixed in PR https://github.com/lewangdev/autotranslate/pull/5


Update the PolymerPass to support Polymer 2 in ADVANCED mode.

Provides full support for Polymer 2 class based and hybrid elements. By setting the new --polymer_version=2 flag, the behavior is changed to support both Polymer 2 class based elements as well as better renaming. In particular:

Declared properties are now renamable (except for those marked readonly).
Both declared and standard properties follow the ALL_UNQUOTED policy.
Designed for new type inference only. Type names are no longer forced into the global scope.
Adds an @polymerElement annotation for Polymer 2 classes so the compiler can recognize elements which do not directly extend Polymer.Element.
@polymerElement and @polymerBehavior annotations are now printed out when --preserve_type_annotations is enabled.
Auto-injects an object reflection primitive to support consistently renaming Polymer property configuration literals with the object.

Requires #2337 to prevent the compiler from creating invalid property names.
We can either land #2277 first and then I'll rebase these changes, or it can be closed and this PR can be merged in it's stead as it includes those changes.
I've tested this code on my project with the --polymer_version flag at both 1 and 2.
cc @MatrixFrog, @justinfagnani

Updated to support the change from static get config() {} to static get properties() {}

And now updated to use Polymer.ElementProperties as the return type for the properties getter.

Further testing revealed that declared properties with reflectToAttribute: true should not be renamed. PR updated to account for this.

@ChadKillingsworth there has been some renaming of the jsdoc tags:
@polymerElement -> @polymer and @customElement
@polymerMixin -> @polymer and @mixinFunction
@polymerBehavior is unchanged.

@azakus I was just working on this today

This has been rebased onto the top of the tree. It now implements the new annotations from Polymer/polymer-analyzer/issues/605 - except for @appliesMixin functionName.
It didn't make sense to handle the @appliesMixin annotation as we don't have a way to keep the functionName reference updated with renaming. It's not a typename.

Can we get another rebase?

@justinfagnani Done. This is going to get very difficult to keep in sync as the compiler is seeing a lot of changes this summer to support Es6 syntax without transpilation.

Yeah, @azakus and I are tying to get this LGTM'ed asap. Dan wanted to try it out locally. Thanks for your patience!

I got this error:
[11:32:47] gulp-google-closure-compiler: java.lang.RuntimeException: INTERNAL COMPILER ERROR.
Please report this problem.

An enclosing scope is required for change reports but node null doesn't have one.
  Node(CLASS): polymer.html_script_32.js:27:2
  class DomIf extends Polymer.Element {
  Parent(BLOCK): polymer.html_script_32.js:3:12
(function() {

	at com.google.javascript.jscomp.Compiler.getChangeScopeForNode(Compiler.java:2614)
	at com.google.javascript.jscomp.Compiler.reportChangeToEnclosingScope(Compiler.java:2678)
	at com.google.javascript.jscomp.PolymerClassRewriter.addInterfaceExterns(PolymerClassRewriter.java:593)
	at com.google.javascript.jscomp.PolymerClassRewriter.rewritePolymerClassDeclaration(PolymerClassRewriter.java:220)
	at com.google.javascript.jscomp.PolymerPass.rewritePolymer2ClassDefinition(PolymerPass.java:152)
	at com.google.javascript.jscomp.PolymerPass.visit(PolymerPass.java:116)
	at com.google.javascript.jscomp.NodeTraversal.traverseBranch(NodeTraversal.java:685)
	at com.google.javascript.jscomp.NodeTraversal.traverseChildren(NodeTraversal.java:757)
	at com.google.javascript.jscomp.NodeTraversal.traverseBlockScope(NodeTraversal.java:772)
	at com.google.javascript.jscomp.NodeTraversal.traverseBranch(NodeTraversal.java:679)
	at com.google.javascript.jscomp.NodeTraversal.traverseFunction(NodeTraversal.java:716)
	at com.google.javascript.jscomp.NodeTraversal.handleFunction(NodeTraversal.java:647)
	at com.google.javascript.jscomp.NodeTraversal.traverseBranch(NodeTraversal.java:663)
	at com.google.javascript.jscomp.NodeTraversal.traverseChildren(NodeTraversal.java:757)
	at com.google.javascript.jscomp.NodeTraversal.traverseBranch(NodeTraversal.java:681)
	at com.google.javascript.jscomp.NodeTraversal.traverseChildren(NodeTraversal.java:757)
	at com.google.javascript.jscomp.NodeTraversal.traverseBranch(NodeTraversal.java:681)
	at com.google.javascript.jscomp.NodeTraversal.traverseChildren(NodeTraversal.java:757)
	at com.google.javascript.jscomp.NodeTraversal.handleScript(NodeTraversal.java:635)
	at com.google.javascript.jscomp.NodeTraversal.traverseBranch(NodeTraversal.java:660)
	at com.google.javascript.jscomp.NodeTraversal.traverseChildren(NodeTraversal.java:757)
	at com.google.javascript.jscomp.NodeTraversal.traverseBranch(NodeTraversal.java:681)
	at com.google.javascript.jscomp.NodeTraversal.traverse(NodeTraversal.java:306)
	at com.google.javascript.jscomp.NodeTraversal.traverseEs6(NodeTraversal.java:602)
	at com.google.javascript.jscomp.PolymerPass.hotSwapScript(PolymerPass.java:98)
	at com.google.javascript.jscomp.PolymerPass.process(PolymerPass.java:93)
	at com.google.javascript.jscomp.PhaseOptimizer$NamedPass.process(PhaseOptimizer.java:305)
	at com.google.javascript.jscomp.PhaseOptimizer.process(PhaseOptimizer.java:231)
	at com.google.javascript.jscomp.Compiler.check(Compiler.java:1110)
	at com.google.javascript.jscomp.Compiler.performChecksAndTranspilation(Compiler.java:910)
	at com.google.javascript.jscomp.Compiler.access$000(Compiler.java:101)
	at com.google.javascript.jscomp.Compiler$3.call(Compiler.java:844)
	at com.google.javascript.jscomp.Compiler$3.call(Compiler.java:841)
	at com.google.javascript.jscomp.CompilerExecutor$2.call(CompilerExecutor.java:93)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
	at java.lang.Thread.run(Thread.java:748)
Caused by: java.lang.IllegalStateException: An enclosing scope is required for change reports but node null doesn't have one.
	... 38 more

events.js:182
      throw er; // Unhandled 'error' event
      ^
Error: Compilation error

You can test with https://github.com/Polymer/polymer/pull/4684 and run gulp closure

Just recreated. It's an easy fix - I'll get to it this weekend.

@azakus Fixes pushed. I now get the same 33 warnings as I get from the released version of the compiler.

One note, Polymer code like this will break with the --polymer_version=2 flag:
class FooElement extends Polymer.Element {
  static get is() { return 'foo-element'; }
  static get properties() {
    return {
      bar: {
        type: String,
        observer: 'barChanged_' // this won't be renamed properly
      }
    };
  }
  _barChanged() { console.log(this.bar); }
}

There are several strategies to handle this:

Quote _barChanged
Have the class implement an external interface to block renaming
Add property reflection calls to the observer string. It's possible for the compiler to auto-add these if it's a string literal. Though that's a bit harder for complex observers.
Address https://github.com/Polymer/polymer/issues/4543

@ChadKillingsworth Hmm, I'm a bit confused. I had hoped that any property returned by the properties getter would be counted as a property that exists on the class, but I'm still seeing stuff like WARNING - Property indexAs never defined on this of type DomRepeat. Is there anything that polymer pass can do for this?

@azakus It should be recognizing those. The pass specifically adds stub definitions. It's either not recognizing the class as a Polymer class or adding the stub incorrectly.
How can I reproduce this?

@justinfagnani suggested I make a small repo that should make it easier to identify, I'll go ahead and do that and let you know.

In addition to the repro for this potential issue, it seems like it'd be nice to have a polymer+closure sample repo both as a starting point for interested users and for us all to contribute to and check to make sure the whole pipeline is working.

That would be awesome. In addition it would be great to be able to show different compilation levels and I would love to demonstrate polymer-rename usage to forward renaming to templates.

@ChadKillingsworth I've added you to https://github.com/PolymerLabs/polymer-closure-sample. So far, it looks like extending Polymer.Element works, but not anything more exotic with the /** @polymerElement */ annotation.

@ChadKillingsworth nvm, I forgot we changed @polymerElement to @polymer. That does seem to work correctly.

@azakus Do I need to add back in support for @polymerElement as well?

@ChadKillingsworth oh no, I just needed to update all of Polymer. All forward on the new thing!

@ChadKillingsworth https://github.com/PolymerLabs/polymer-closure-sample/commit/fbb91de13c441b2768bbc20fbf7aa83e6c9b1379 shows an interesting bug with readonly props:
app.html_script_14.js:24: WARNING - property _setReadOnlyProp not defined on any supertype of XFoo
              readOnlyProp: {
              ^^^^^^^^^^^^

@azakus Looks like I missed marking the class as implementing the interface that got created. Fixed that and added a test. One less warning now.

@MatrixFrog this PR feels ready for integration as a first pass.
I'd like to see simple property observers avoid dead code elimination
class XFoo {
  static get properties() {
    return { foo: { observer: 'fooChanged' } };
  }
  fooChanged(newFooValue, oldFooValue) {
  }
}

but I'm totally fine with that coming later 👍

Having some issues with our import script. Stand by.

@MatrixFrog Want me to squash? I merged in master this morning.

It couldn't hurt.

Done

Got it. After this lands, can you update https://github.com/google/closure-compiler/wiki/Annotating-JavaScript-for-the-Closure-Compiler with an indication of what @polymer and @polymerBehavior mean?

Yup. https://github.com/google/closure-compiler/wiki/Polymer-Pass too

Added the new annotations. I'm going to have to work a bit to rewrite the Polymer Pass documentation - but I'll get that this week.


Create a documentation page for logging vm messages using Beacon.

Since we can access VM log messages from the image we should have a page in the doc about documenting how to do it.


182346339 remove blueprint

I'm not sure how to definitively check to make sure this didn't cause any unwanted changes. It would probably be good to get some QA from someone who knows the look of CLUE well to make sure nothing broke. Here are notes that might be helpful when looking over the PR:

Seems like blueprintjs was barely being used in the project, but blueprint.css was being imported in index.tsx so it's very possible its affects were far reaching.
The .bp3-button class in clue-app-header.sass seemed to be duplicating something from blueprintjs rather than referencing something from blueprintjs. It also seemed to be unused.
I couldn't figure out the rule that outline: none !important was overriding in geometry-tool.sass, and I couldn't see any difference when I removed it.
blueprint.css defined rules for small and strong. small never seems to be used in the project. strong is used widely. The rule set the font-weight of strong to 600 rather than the default 700, which might explain why bold text wasn't showing up as bold as desired.
A couple of font families were being downloaded in blueprint-icons.css: Icons16 and Icons20. I couldn't find any references to either one (except a body wide font-family definition in blueprint.css which I copied over but ended up commenting out). However, I really don't know how to check to make sure these fonts aren't being used.

@tealefristoe I mentioned this in the meeting today, but you should measure the sizes on before/after builds to see how much effect removing blueprint had.


Progressive scan creates distorted image for widths 180 and 360

This is a great library! I found an issue when providing images with a width of 360 or 180 when progressive_scan is set to true. Issue goes away when progressive_scan is set to false.
Input is RGB and encoder quality is set to 85.
Image from Big Buck Bunny showing the distortion.

It looks like Chrome doesn't display the image. Click on the invisible link to get the URL of the image.

This is most likely a problem with subsampling. I've created #3 this should fix this problems.
Would be nice if you can test if this PR fixes the Problem for your test image, too.

It's fixed. Thank you!


ADBDEV-5259: Ensure sscanf function does not overwrite buffer.

Ensure sscanf function does not overwrite buffer.
The sscanf function is not safe in the sense that it can read data into the
buffer without relying on its size. To prevent buffer overflows, this patch adds
an explicit maximum read size.

Allure report https://allure.adsw.io/launch/67799

Failed job Resource group isolation tests on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1222397

Failed job Resource group isolation tests on ppc64le: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1222398

Failed job Regression tests with ORCA on x86_64: https://gitlab.adsw.io/arenadata/github_mirroring/gpdb/-/jobs/1222391

failed known flaky dispatch test

I guess "Ensure sscanf function not overwrite buffer." should be changed to "Ensure sscanf function does not overwrite buffer". That seems more correct.

should be changed to "Ensure sscanf function does not overwrite buffer".

updated


Update config_template.txt

Lemme fix this, all I did was update the top part, I didn't touch the multiadmin stuff.


Nullable properties NullReferenceException not thrown.

I encountered a small 'bug' on C# while trying to build a search method using the stringVar.Contains in a predicate.
At first It worked fine for every Model I used it on, but if that Model had a null value in some of its properties no error is thrown but the search failed and returned no data.
It took me a while to find where the problem was, and that's where I tried checking the values in my Model and found that some were null, usually we'd use the null-conditional operator stringVar?.Contains to check if the variable is null before using a method on it but we can't do that with expression trees (You'd get the following error An expression tree lambda cannot contain conditional access expressions).
So my fix was to check if the property is not null and then call the string method.
private static bool Contains(PropertyInfo prop, T x, string searchValue)
    {
        return prop.GetValue(x) != null && prop.GetValue(x).ToString().ToLower().Contains(searchValue);
    }

And then called it in the predicate:
predicate.Or(x => Contains(prop, x, searchValue));

But I was wondering why the error was not thrown and if it was caught why does the predicate fail?
P.S: Might be the same problem here #62

If you are building predicate for EF you are doing this in wrong way. PredicateBuilder will not help here.
Create question on StackOverflow with detailed description what you ate trying to achieve.

@sdanyliv I am indeed doing that, I followed the demo you had in the Readme calling AsExpandable() and using predicate.Compile() everything seems to be working fine I don't see what's wrong with that? It's just this single problem that was stopping it from working on some cases because no error was thrown.
Meanwhile I am building a demo project that I'll try to link here when I am done.

@elf-is You are referring to DataTableService.SearchAColumn? I believe, that you misunderstand the behaviour of EF Core and your Database here, and there isn't a lot LINQKit can do about this. It may also be, that you would need to push for a C# Language specification change.
So first, what does EF Core do with Expressions?

EF Core tries to translate C#-function-calls into SQL
It seems you are using Pomelo.EntityFrameworkCore.MySql as database provider, that documents that stringValue.Contains(value) is translated into expr LIKE pat [ESCAPE 'escape_char'] or LOCATE(substr,str). See https://github.com/PomeloFoundation/Pomelo.EntityFrameworkCore.MySql/wiki/Translations#string-functions
MySQL states for both, that if any argument is NULL, the result is NULL. There is no exception/error here and NULL for most aspects behaves like false in boolean-context

Second, if you intend to use the predicate outside EF Core you basically hit the limits of the C# compiler/C# Language specification. For all I know you can only use the expressions present in .NET 3.5 directly in source code and have it translated for you into an Expression tree, see also https://learn.microsoft.com/en-us/dotnet/csharp/advanced-topics/expression-trees/#limitations . What you can do right now, is to write your own helper like
    public class CoalescingTests
    {

        [Theory]
        [InlineData(null, false)]
        [InlineData("x", true)]
        [InlineData("y", false)]
        public void NullCoalesce(string value, bool expectation)
        {
            Expression<Func<string, bool>> expression = s => s.IfNotNull(str => str.Contains("x"), () => false);
            Assert.Equal(expectation, expression.Invoke(value));

            var expanded = expression.Expand();
            Assert.DoesNotContain("IfNotNull", expanded.ToString());
            Assert.Equal(expectation, expanded.Invoke(value));
        }
    }

    public static class CoalescingExtensions
    {
        [Expandable(nameof(IfNotNullWithDefault))]
        public static TResult IfNotNull<TIn, TResult>(this TIn value, Expression<Func<TIn, TResult>> then, Expression<Func<TResult>> @else)
            where TIn : class
        {
            if (value != null)
                return then.Invoke(value);
            return @else.Invoke();
        }

        static Expression<Func<TIn, Expression<Func<TIn, TResult>>, Expression<Func<TResult>>, TResult>> IfNotNullWithDefault<TIn, TResult>()
            where TIn : class
        {
            var value = Expression.Parameter(typeof(TIn));
            var then = Expression.Parameter(typeof(Expression<Func<TIn, TResult>>));
            var @else = Expression.Parameter(typeof(Expression<Func<TResult>>));
            return Expression.Lambda<Func<TIn, Expression<Func<TIn, TResult>>, Expression<Func<TResult>>, TResult>>(
                Expression.Condition(
                    Expression.NotEqual(value, Expression.Constant(null, typeof(TIn))),
                    Expression.Invoke(then, value),
                    Expression.Invoke(@else)),
                value, then, @else
                );
        }
    }

Calling Expand() results in s => IIF((s != null), s.Contains("x"), False). This differs from ?. in that it does not define a variable for the checked s. If s actually is a computed property, you may want to modify the expansion, to first assign the value to a local variable, as otherwise expanding will spread the property access to all places. Given that you build your predicate it may however be better memory-wise to create the temporary variable once and use it in all predicates.
This would be an expansion with local variable:
        static Expression<Func<TIn, Expression<Func<TIn, TResult>>, Expression<Func<TResult>>, TResult>> IfNotNullWithDefault<TIn, TResult>()
            where TIn : class
        {
            var valueParameter = Expression.Parameter(typeof(TIn));
            var value = Expression.Parameter(typeof(TIn));
            var then = Expression.Parameter(typeof(Expression<Func<TIn, TResult>>));
            var @else = Expression.Parameter(typeof(Expression<Func<TResult>>));
            return Expression.Lambda<Func<TIn, Expression<Func<TIn, TResult>>, Expression<Func<TResult>>, TResult>>(
                Expression.Block(
                    new[] {value},
                    Expression.Assign(value, valueParameter),
                    Expression.Condition(
                        Expression.NotEqual(value, Expression.Constant(null, typeof(TIn))),
                        Expression.Invoke(then, value),
                        Expression.Invoke(@else))),
                valueParameter, then, @else
            );
        }


Novel View Render

Dose render a image mush be use gt_depth as arg? how can I render a image with Novel View?

You can pass all zero values for gt_depth and the function will operate assuming there are no depth values available. However, note that for training and optimization, our method heavily relies on depth values and cannot be trained properly without them.


Using reactStrictMode  results in the error: "It looks like you've created a new nodeTypes or edgeTypes object"

Describe the Bug
using reactStrictMode results in the error:

It looks like you've created a new nodeTypes or edgeTypes object

I'm aware that reactStrictMode renders the component twice and for several debugging reasons. Therefore, shouldn't this be properly handled from the ReactFlow context?
Your Example Website or App
reproduced here
Steps to Reproduce the Bug or Issue

npx create-next-app@latest
set reactStrictMode to true
paste the example:

const initialNodes = [
  { id: '1', position: { x: 0, y: 0 }, data: { label: '1' } },
  { id: '2', position: { x: 0, y: 100 }, data: { label: '2' } },
];
const initialEdges = [{ id: 'e1-2', source: '1', target: '2' }];

export default function Home() {
  return (

    <div style={{ width: '100vw', height: '100vh' }}>
      <ReactFlow nodes={initialNodes} edges={initialEdges} />
    </div>
  );
}

run the app

Expected behavior
No Warnings to Appear when using reactStrictMode
Screenshots or Videos
No response
Platform

OS: Window
Browser: Edge
Version: 120.0.2210.144

Additional context
No response

Hi there @alikleit! This has been fixed in our v12 beta (confirmed by taking your reproduction and swapping out reactflow for @xyflow/react): the issue I think stems from a fairly naive approach we were taking to tracking this particular warning. I think there's some interplay with next as well, because we can't reproduce the error in other examples even with <React.StrictMode />.
You can safely (although annoyingly) ignore this while you're on v11 and using next :)


#Feature-Request: Dark Light mode toggle

I would like to suggest adding a dark/light mode toggle to the website. This feature would provide users with the option to switch between dark and light themes, making the website more accessible and user-friendly in different lighting conditions.

It already has that feature. I have chosen to disable it because of personal preferences. Thank you for opening the issue.


Directive isn't updated when new data comes in if called from another directive

I have started to use directives with ui-router:
$stateProvider
  .state('book', {
    abstract: true,
    url: '/:book',
    template: '<book-tabs />'
  })
  .state('book.about', {
    url: '',
    template: '<book-about />'
  })
  .state('book.stats', {
    url: '/statistics',
    template: '<book-stats />'
  });

Here is one of the directives:
  export default function(app) {
    app.directive('bookStats', function() {
      return {
        restrict: 'E',
        controllerAs: 'statsTab',
        templateUrl: 'book-stats.tpl.html',
        controller: 'BookStatsCtrl'
      };
    });
  };

Inside of book-stats directive I want to call stats-list directive and pass book object, that is empty at first, but has data after HTTP request is fulfilled:
var vm = this;
vm.book = {};
Book.get.single({bookId: id}).then(function(res) {
    vm.book= res; // there is data
    return res;
});

In template:
<stats-list book="statsTab.book"></stats-list>

And here is stats-list directive:
export default function(app) {
  app.directive('statsList', function() {
    return {
      restrict: 'E',
      scope: {
        book: '='
      },
      templateUrl: 'stats-list.tpl.html',
      controller: 'CircleRankListCtrl'
    };
  });
};

When initialized, stats-list directive is called with a empty book object as a parameter, and when HTTP request is fulfilled and book object gets some data, stats-list directive doesn't update.
When I tried to call $scope.$apply inside of a callback I got $digest already in progress error.
I used Angular 1.4.7 but I also tried to changed it all to Angular 1.5 components.

@Vayvala, this sounds like a general support question. Please, use one of the appropriate support channels for these types of questions.
GitHub issues are reserved for bug reports and feature requests.
Thx !
--
If you think you have found a bug with Angular itself, it would be very helpful if you could create a minimal live reproduction (e.g. using CodePen, Plnkr etc).


Support for Nextera and other library preparations

While discussing preparation sheets, @AmandaBirmingham @charles-cowart and I realized that the present shotgun library preparation page only allows for Kapa Hyper Plus:

I spoke with @ghsmu414 and he confirmed that, while the majority of preparations are Kapa Hyper Plus, we do still use Nextera. In addition, library preparations beyond Nextera and Kapa Hyper Plus may be used in the future.
It would be beneficial to allow for specifying Nextera kits. But a more general interface here, which allows the user to create a new kit type, may be the most ideal.

https://github.com/jdereus/labman/blob/677f696334fa2fdf2b6a9b084ec9c812fbcd8ae1/labcontrol/db/process.py#L4117

Tentatively assigning to full launch.

for specifying Nextera kits. But a more general interface here, which allows the user to create a new kit type, may be the most ideal.

After a little bit of thought, it might be better to make the creation of a new kit type a separate interface in the Admin section. Granted everyone is currently an admin, but I think it's prudent to prevent casual creation of new kit types.

Note that it won't be enough to add an interface to allow admins to create new kit types ... we will also need to change the shotgun library prep interface--AND, more thornily, the underlying db and object structure--to allow user to specify the kit type as well as the kit id.  Right now, all the way down to the db level, LabControl expects ALL shotgun library prep to be done with a kappa hyper plus kit:

That does sound like it goes deep; I'll ask Greg if this is needed before launch, we can prioritize it behind the other deliverables.


Update APK on Github

Thanks for offering this great app for free – and even having the .apk available at Github! However, I've noticed that file is from June, while the latest release was in November. Could you make an update available here as well? Best place of course would be with the releases/ page, see Creating Releases ;)

I just created a release for the v1.0.5 update which should be live on the Play Store now.
From now on, I will create new releases for each update and make sure to keep the .apk up-to-date.

Thanks a lot! In that case, folks without Playstore can use the F-Droid client to install/update from here :smiley_cat: Updates are usually available within 24h of your releasing them here at Github. People using the repo will then get notified automatically when their F-Droid client next updates its package lists.


Error AADSTS50076

Is it possible to authenticate with the oauth 2.0 protocol with the grant_type password for a user with MFA enabled?

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

ID: 2870d4a9-e204-023a-56a8-c34e56347b43
Version Independent ID: 846fe3ae-21cb-e030-f68f-db73acef0c74
Content: Understand the OAuth 2.0 authorization code flow in Azure AD
Content Source: articles/active-directory/develop/v1-protocols-oauth-code.md
Service: active-directory
Sub-service: develop
GitHub Login: @rwike77
Microsoft Alias: ryanwi

Hi @martininvillia ,
From what I understand they will be blocked if they try to use MFA.  This has been answered here. https://stackoverflow.com/questions/54215795/authenticate-and-get-azure-ad-token-in-net-core-web-api-with-grant-type-as-pass

@rwike77

If you have further questions feel free to tag me in the comments and I will gladly continue the discussion.


Overlapping fieldsets

I had some calls from customers that they can not change the status of an order.
After checking the issue I have seen that there are overlapping fieldsets. This issue is based on the concrete5 dashboard-theme.
I opened an issue here: https://github.com/concrete5/concrete5/issues/7020
Sceenshot on community store 1.4beta and concrete5 8.4.2:

I've pushed up a fix for this - just the removal of those fieldsets.
I'd like to re-organise this page a bit, since there are some further features I'd like to add.
I'm thinking maybe some tabs or similar so the page isn't so long.


fix(docs): Updated the permissions doc examples with clearer scope assignment inputs.

Why:
Closes: #22769

What's being changed (if available, include any code snippets, screenshots, or gifs):
Updated the permission documentation to correctly reflect the scope assignment in the usage.

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline.

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

I couldn't make the change.
Sent from Yahoo Mail on Android
On Wed, Oct 4, 2023 at 10:12 PM, Sarah @.***> wrote:
#28864 was added to the merge queue.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Unable to read gef file

Hello,
I have been trying to read a gef file using the following code:
from pygef import Cpt

Cpt(r"..\GO\46358_10.GEF")

Unfortunately I get an error:
thread '<unnamed>' panicked at 'python apply failed: Any(InvalidOperation("abs not supportedd for series of type Float64"))', src\lazy\apply.rs:35:19
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Traceback (most recent call last):
  File "C:\Users\921479\Desktop\GEO\Z002\notebooks\test_gef.py", line 5, in <module>
    Cpt(r"..\GO\46358_10.GEF")
  File "C:\Users\921479\Desktop\GEO\Z002\notebooks\.venv\lib\site-packages\pygef\cpt.py", line 159, in __init__
    parsed = _GefCpt(path)
  File "C:\Users\921479\Desktop\GEO\Z002\notebooks\.venv\lib\site-packages\pygef\gef.py", line 276, in __init__
    self.parse_data(self._headers, self._data, column_names)
  File "C:\Users\921479\Desktop\GEO\Z002\notebooks\.venv\lib\site-packages\polars\lazy\frame.py", line 299, in collect
    return pl.eager.frame.wrap_df(ldf.collect())
pyo3_runtime.PanicException: python apply failed: Any(InvalidOperation("abs not supportedd for series of type Float64"))

I think there is a problem in the .collect() statement when the cpt data is converted to a DataFrame. Has anyone come across this issue before? Does there exist a workaround? Thanks for your consideration.

See #121
Update polars: pip install polars==0.10.21

Thanks that worked.


Fuzzer: Support User-Defined Types (Opaque types)

Description
We'd like to allow Velox fuzzers to test UDFs that take Opaque-typed inputs or generate Opaque-typed output.

Will be solve with the framework we design for #3159

@kagamiori Wei, do we need the same for aggregation fuzzer?

@kagamiori Wei, do we need the same for aggregation fuzzer?

That would make sense. I've updated the title.


Celeryd-multi can't start with eventlet pool

Create simple test task:
import eventlet
from celery.task import task
eventlet.monkey_patch()
@task
def add(x,y):
return x+y
Then start celeryd-multi with 2 queues( one with Eventlet, one usual):
celeryd-multi start 2
-Q:1 starters    -c:1 5
-Q:2  parsers -P:2 eventlet -c2:5
--logfile=celer.${USER}%n.log
--loglevel=INFO
--verbose  --time-limit=60 --purge
In celer.log.2.log last line is<EMAIL_ADDRESS>has started.", but in celer.log.1log - last lines are
[2012-02-23 20:20:35,215: INFO/PoolWorker-4] child process calling self.run()
[2012-02-23 20:20:35,217: INFO/PoolWorker-5] child process calling self.run()
and agents never accept tasks.
Remarks:
If i make both queues as eventlet by adding "-P:1 eventlet" - celeryd-multi starts without any problems.
If i remove "eventlet.monkey_patch()" from test task - celeryd-multi  also starts without any problems.

celeryd-multi seems not to play a role. Problem seems to be like this - if i call eventlet.monkey_patch() inside multiprocessing pool - celery hangs, if pool is Eventlet - everething is OK.
How is it possible to determine which pool is used by celery and decide - whether to call for monkey_patch or not?


Configuring client with hazelcast_client.xml

Is there a way to configure the C++ client using client xml file like we do with java client? If application has both java and C++ code that connects to hazelcast, do we have to parse the configuration file ourselves on the C++ side? Thanks

Hello,
No, we do not have the XML config feature for C++, but it is in our road map. You can see the comparison of features implemented per language here: https://hazelcast.org/clients-languages/

@aparnam-asg, thanks for your question! This is something we would like to add in the first part of this year. Stay tuned!


Refactor minutes, adjust nav and member listing slightly

Overview
This continues the template upgrade to bootstrap 5, this time for the minutes listing page. Some highlights:

the names of the meetings are now visible on all screen sizes (as opposed to only desktop)
a conditional to show a message for no results has been added
the nav in the base template has been adjusted to make sure the nav-items stay to the right
the horizontal padding in the board members' listing page has been adjusted (felt there was a little too much)

Connects #969
Closes #997
Demo

Testing Instructions

Check the minutes listing page against its live version on desktop and mobile window sizes
Confirm that

it looks presentable/similar to the original
the functionality still works (date search, show all/fewer button, etc)

Ah didn't notice that, ty! Got that in as well as the drop shadow from the live site.


pydantic version update

pydantic update to 2.*
template update

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.085%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
252

Relevant Lines:
307

💛  - Coveralls


feat: Add module & jsnext:main entries

This PR reduces the bundle size

This does not "reduce the bundle size", it causes Webpack to consume a different target, the es target, which most consumers do not want to do.
We provide the es target for consumers who specifically want to consume esnext code, and are fine with handling their own browser targeting/transpilation.
Feel free to use the es target if you want - no code changes necessary! The current state of JavaScript modules, especially with Webpack and Babel, is a bit messy. We'd rather keep it such that all tooling will use the cjs target by default.

which most consumers do not want to do

Why? Just wondering.
IMHO given that this package is a Next.js plugin and not a standalone thing makes ES target the only necessary one at all. The decision to support this or that browser is made at the app level, not at the Next.js plugin level. That's the only way to achieve proper tree-shaking and polyfilling that does not produce duplicate code.

@kachkaev Unless you're transpiling your node_modules, that is unfortunately not the case.  Again, this is an ongoing discussion in the JavaScript world, but not something we'll get into here.
Just trying to make the package make the most sense for the most users.

Ha, Ok, got your point, your es target is not only es modules but all the code is es.
I think that this is wrong approach to a plugin, I think that the es version should only not transpile the import / export syntax.
Checkout how react-semantic-ui are doing it: https://github.com/Semantic-Org/Semantic-UI-React/blob/master/.babel-preset.js#L64
Check how i18next are doing it: https://github.com/i18next/i18next/blob/master/rollup.config.js#L29
WDYT?

@isaachinman ping?

@felixmosh Regarding your comments: there is no need to repeat yourself across multiple issues/PRs.
The fact that we're exporting a esnext version of our source has nothing to do with alignment with the community in regards to tree shaking. It's there so that consumers who wish to transpile their deps to their own target may do so. This is, I believe, the future of JavaScript dependency management.
The fact that the current standard is to distribute packages with es modules and also transpile to some arbitrary browser target is indicative of how troubled the current state of JavaScript modules is.
As a package author, I do not care about consumers' individual browser targeting needs based on their own particular use cases and business requirements. The distribution of source code and the eventual transpilation to an end user's unique target should be distinct build steps.
The commonjs target works relatively nicely, because we can reuse the next/babel preset for most of the heavy lifting. Because this is a NextJs plugin, it is absolutely critical that we have the same target. If you can figure out how to replicate the cjs Babel target within our babelrc to export es modules in a target called esm while still consuming the next/babel preset, I'd accept a PR for that.

OK,
I didn't want to upset you, looked like you didn't get a notification for this comment.
Thanx for the time, I will investigate your suggestion.

No problem. The relevant preset can be found here.

BTW, why do you think that next-i18next is transpiled by next's babel config?

The point is that we need to support targets like IE11. If you'd like to use modern ES and benefit from tree shaking, you can certainly import from the appropriate directory. Is that not working?

@isaachinman It doesn't work in case for shared code server and client


2490 Sketch of a Graal feature to support automated resource loading based on the Typesafe config

Closing for now, keeping the branch for future reference.


Abandoned?

People are using their time to create free tools and you can't even write a message to ask properly if the project is discontinued

People are using their time to create free tools and you can't even write a message to ask properly if the project is discontinued

Dont cry


Pip package don't have dependency on requests but use it

Hello.
requests package not installed with this package after installation using pip.
pip show camunda-external-task-client-python3
Name: camunda-external-task-client-python3
Version: 3.0.0
Summary: Camunda External Task Client for Python 3
Home-page: https://github.com/trustfactors/camunda-external-task-client-python3
Author: Deserve Labs
Author-email<EMAIL_ADDRESS>License: LICENSE.txt
Location: c:\users\aaksarin\virtualenvs\crm2camunda\lib\site-packages
Requires:
Required-by:

But in engine_client.py there is requests import.

@aaksarin
Thank you for reporting the issue. I have reached 3.2.0 version that now mentions the requests module under Requires:
https://pypi.org/project/camunda-external-task-client-python3/
pip show camunda-external-task-client-python3
Name: camunda-external-task-client-python3
Version: 3.2.0
Summary: Camunda External Task Client for Python 3
Home-page: https://github.com/trustfactors/camunda-external-task-client-python3
Author: Deserve Labs
Author-email<EMAIL_ADDRESS>License: LICENSE.txt
Location: /Users/yogeshnaik/.pyenv/versions/3.7.5/envs/camunda_pkg_install_example/lib/python3.7/site-packages
Requires: requests
Required-by:


BoringSSL: Switch SecureSocket implementation from NSS to BoringSSL

We are switching the Dart standalone executable "dart" and the dart:io library to use the BoringSSL library (https://boringssl.googlesource.com/boringssl/)
instead of the Mozilla NSS library.
This will simplify the API for importing certificates and keys, simplify the build process and decrease the executable size, and switch to a simpler, smaller SSL library that is maintained by Google with outdated code removed and new TLS features added quickly.

[x] Merge in BoringSSL branch
[x] Support onBadCert arg: #23561
[ ] Add change log entry
[x] Update documentation
[x] Blog post
[x] Report errors from multithreaded encrypting: #24185

This master bug (issue) will be used to track requests, and be marked as blocked on all the bugs tracking individual feature implementations. @mit-mit: edited this to fit other meta issues.

Looking forward to this, a nice change!

@whesse, I updated this to follow the meta bug style. Can you complete the list I started for things that need to happen in 1.13? Thanks!

This is now complete.  Filing a separate bug for the changelog entry.


Hotfix cache queries for performance

Used Threads Library to off load hashing of cache keys.
Added cache for count and results of projects filters queries.
Moved main filters query to projectRepository (this is because queries share state, so instantiating different query builders avoid wrong results when using cache).

Still work in progress, I am rewriting a little the queries, but the cache broke the tests.

To debug you can add DEBUG=threads:* to any command like npm start or npm run test

Made this improvement PR
We have a build issue with typescript v3.
https://github.com/andywer/threads.js/issues/359#issuecomment-831966607
So we are blocked by other dependency upgrade PR

Merged https://github.com/Giveth/impact-graph/pull/810 as tests passed.
The major idea behind improvements:

Merging reaction complexity improved, from O(n^2) to O(n)
Relay on json-stable-stringify, since it support nested object sorting. object-hash does only first level key sorting

Hey Amin for staging I think the default values are enough.