Add OnRejected callback to Request Queuing middleware to allow user code to handle rejections

Epic #10702
Right now, when a request is rejected by the queuing middleware, we just 503. We should provide a user callback to allow user code to handle it specially.

Done in https://github.com/aspnet/AspNetCore/pull/10817 !


Migration 0002 negative unit tests

Description
Migration 0002 negative unit tests
Type of change

Unit tests (no changes in the code)

Testing steps
Done on CI
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
Base: 67.20% // Head: 67.20% // No change to project coverage :thumbsup:

Coverage data is based on head (ee40e88) compared to base (5fcc6d3).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #338   +/-   ##
=======================================
  Coverage   67.20%   67.20%
=======================================
  Files          14       14
  Lines        1177     1177
=======================================
  Hits          791      791
  Misses        364      364
  Partials       22       22

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

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


Application Optimizations

Overview

Limit the number of times the api reloads the data

load only when a sufficient distance change has occurred

Done When

The result set from a yelp API call has been cached for a client.
The results cache is refreshed with an API call if the distance from the original location exceeds 25% of the client's desired search radius.

From "lunch meeting":

Cache the data from the given location
refresh results when user travels 25% away from the initial location

Note: this will be hard to test on an emulator since the location is fixed.


Fix <= parsing

As of v0.1.7, parse_op2 parses < before <=, which implies the term (<= 1 2) doesn't parse correctly -- this fails with thread 'main' panicked at 'No parse.' because it thinks it's a < operator followed by something it didn't expect).
I just changed the order of Oper::Ltn and Oper::Lte to fix this :)

Thanks!


why im getting this?

Downloading...
From: https://drive.google.com/uc?id=1TINXq-us2aUC5d1lCXGITP4yjzmA-IHY
To: /content/10_Mate.zip
100% 3.19M/3.19M [00:00<00:00, 205MB/s]
unzip:  cannot find or open /content/zipfile.zip, /content/zipfile.zip.zip or /content/zipfile.zip.ZIP.

FileNotFoundError                         Traceback (most recent call last)
 in
37 if not zipfile_url.startswith("/content"):
38   get_ipython().system('unzip -j -o "{root_dir}/{zipfile_name}" -d "{unzip_to}"')
---> 39   os.remove(f"{root_dir}/{zipfile_name}")
40
41 files_to_move = ("meta_cap.json", \
FileNotFoundError: [Errno 2] No such file or directory: '/content/zipfile.zip'

Yep ok so just go to your file listing on the side - and rename the zip file to zipfile.zip - its' annoying but it WORKS trust me XD

Hi, may i know which notebook is this?


Broken after some update

I use latest docker container. Watchtower autoupdate my containers. So not sure when it broke, but now after login i see
Forbidden (403)
CSRF verification failed. Request aborted.
More information is available with DEBUG=True.
Login page work, I enter account, but after login it not work.

I found your doc about CSRF problem. Now work. Thanks.


other record of customized domain fixed

For example we customize *.3osmp.mongodb.net:A:<IP_ADDRESS> -u <IP_ADDRESS>.
App must just customize A query of this domains but current app answer all queries with this response
IN A <IP_ADDRESS>

I fixed this bug.

@arturoarevalo
Waiting for accept... :))


Async components do not render loading component

Version
3.4.3
Reproduction link
https://codesandbox.io/s/lucid-haze-mr425
Steps to reproduce
https://vuejs.org/v2/guide/components-dynamic-async.html#Handling-Loading-State

Create a route with an Async component as showed in the documentation.

const AsyncComponent = () => ({
  // The component to load (should be a Promise)
  component: import('./MyComponent.vue'),
  // A component to use while the async component is loading
  loading: LoadingComponent,
  // A component to use if the load fails
  error: ErrorComponent,
  // Delay before showing the loading component. Default: 200ms.
  delay: 200,
  // The error component will be displayed if a timeout is
  // provided and exceeded. Default: Infinity.
  timeout: 3000
})

Reload page.

Loading component is never rendered.

What is expected?
Loading component should load while chunk is being fetched
What is actually happening?
Loading component does not render

This functionality is needed for the initial render of the app when using code splitting. Otherwise there is a blank screen while the partial downloads. I tried putting a loader behind the Vue app, but as soon as the app renders the router the page blanks out again so I'd like to have a loader for the actual route itself.

See https://github.com/vuejs/vue-router/pull/2140
The problem with async components like those is that they need to be loaded in order to check existing navigation guards to confirm the navigation and actually display the component. At which time, it's already loaded, so it never displays in its loading state


Local Storage  - Security Issue

Hi Team,
In AngularJS, as part of moving data between controllers we used the local Storage concept and it works well and holds the data even we refresh the page. but my team says, there is lot of hacks that exploit HTML local storage and we cannot persist protected data on end point/client system.
Could you please help me in understanding the security concerns involved in localStorage or is it safe to store in local storage ? let me know any other best options for this issue.
Thanks,
SateeshKumar. B

Hi, there are two problems with this issue

This is a question that should be directed to a support forum, as this is not an issue
This is not related to Angular at all, at least not without a relatively big explanation that it is missing


FieldArray: new values update only after input blur, but should after each change

Are you submitting a bug report or a feature request?
bug report
What is the current behavior?
http://www.webpackbin.com/N1djS5vOz
props in FieldArray component update only after input blur
Steps: 1) click "Add person" 2) type something inside input (list should update immediately) 3) make blur (list updates, but should at step 2)
What is the expected behavior?
they should update after every input change
One possible workaround is to connect some selector to People component and pass it as a prop to FieldArray

Seems like it fixed, I'll check it soon.

I think that fix is merged but not released.  I'm still seeing the same sort of issue: implausibly I have an error about an empty field array but in the syncErrors in the store but... at the same time, the field is not empty.  ¯_(ツ)/¯

Fixed now in v6.6.2

No, it isn't fixed. It just became harder to reproduce. I get very strange behaviour, I'll create a bin to reproduce it later.

Yes, it's fixed, but now there is another problem with FieldArray https://github.com/erikras/redux-form/pull/2465#issuecomment-293481665


ELECTRA: Pre-training Text Encoders as Discriminators Rather Than Generators

https://docs.google.com/presentation/d/1ZLnQnhfmqPwwhoIw8uZn7qUtLxvRmW3jRZoN2Oqfnjo/edit?usp=sharing


[Refactor] Refactor RewriteTask and support bottomup task

What type of PR is this：

[ ] bug
[ ] feature
[ ] enhancement
[x] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

[FE PR Coverage Check]
:disappointed: fail : 52 / 72 (72.22%)
file detail

path
covered line
new line
coverage
not covered line detail

:large_blue_circle:
com/starrocks/sql/optimizer/task/BottomUpRewriteTask.java
0
16
00.00%
[14, 15, 16, 20, 21, 22, 26, 27, 28, 33, 34, 36, 37, 38, 39, 41]

:large_blue_circle:
com/starrocks/sql/optimizer/Optimizer.java
10
12
83.33%
[360, 361]

:large_blue_circle:
com/starrocks/sql/optimizer/task/RewriteTask.java
37
39
94.87%
[37, 82]

:large_blue_circle:
com/starrocks/sql/optimizer/task/TopDownRewriteTask.java
5
5
100.00%
[]


Deleting Center/Starting/Ending Point does not delete properly (ArcMap)

Procedure:
Enter 1 1 in Circle tab - Center Point
Select text in Center Point text box
Press Delete
Result:
Text is replaced by 1.0 1.0
Result expected:
Box should be cleared

PR: https://github.com/Esri/distance-direction-addin-dotnet/pull/332

@rjones0 @kgonzago I tested ArcMap adding build 23 Feb 2017 13:08 which I believe should have this change however I'm able to reproduce the issue. For me after I entered "1 1" into the Center Point textbox and then selected the text and pressed Delete the center point textbox was populated with "111325.1 111319.5"

@rjones0 @kgonzago Same issue for Lines, Ellipse, and Rings. Also same issue in ArcGIS Pro; I'll open a separate issue for Pro.
What's happening is that when you click Delete, the addin is re-displaying the coordinate that the user entered converted into the selected "Display Coordinate" property set on the "Edit Properties" dialog.

Pro issue is #334

I got this one.

Functionality appears to be working properly now.  I am able to delete the Center Point input without any issues.


[BUG] :The Navbar for various features in the website are different.

Description
Hi @akshitagupta15june Mam ,
The Navbar for various features on the website is different. To improve user experience and enhance the overall UI, we should make the Navbar across all the features same, making it easier for users to navigate the site.
Screenshots
Augmented Reality Meditation:

Connect with Iskcon Events:

Divine Activities for All Generation:

Pomodoro Spiritual Break:

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Go for it! but keep the index page intact, same as it is and you can change the other navbars similar to peach colour


Error: pq: syntax error at or near "-" when deleting redshift DB

I've been trying to destroy a redshift DB and getting this error, not too sure if this is a bug or if we're running into something else here.
The only way we can get round it is to either delete it manually.
Terraform will perform the following actions:

  # redshift_database.db will be destroyed
  - resource "redshift_database" "db" {
      - connection_limit = -1 -> null
      - id               = "27376203" -> null
      - name             = "database-prd" -> null
      - owner            = (sensitive) -> null
    }

Plan: 0 to add, 0 to change, 1 to destroy.
redshift_database.db: Destroying... [id=27376203]
╷
│ Error: pq: syntax error at or near "-"
│
│
╵
Problem applying destroying terraform environment

@fraserc182 as a workaround until the fix gets merged you can manually run DROP DATABASE "database-prd";

@mtesch-um yup can do. Thanks for working on this.


Add updateMoneyRequestCategory command

Details
Adds a new UpdateMoneyRequestCategory command in place of the broad EditMoneyRequest command for editing money request category
Fixed Issues
$ https://github.com/Expensify/App/issues/32313
PROPOSAL: N/A
Tests

Log into an account on New Expensify that is the employee on workspace
Navigate to the Workspace chat and press + > Request Money
Add an amount and merchant and save the request
Click on the details for the request and add a category
Edit the category to be another category
Confirm in both cases that the category has updated successfully
Reload the app and confirm the category is still successfully updated.

[x] Verify that no errors appear in the JS console

Offline tests

Log into an account on New Expensify that is the employee on workspace
Navigate to the Workspace chat and press + > Request Money
Add an amount and merchant and save the request
Click on the details for the request and add a category
Go offline
Edit the category to be another category
Confirm you see the pending category change

Go back online and confirm the category change is persisted.

QA Steps
Same as  Tests steps

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari
https://github.com/Expensify/App/assets/16747822/fdb07321-50ad-4144-847f-6c84a8e094aa

MacOS: Desktop
https://github.com/Expensify/App/assets/16747822/d3edfe3c-f291-40f8-950b-1b47fd1de5cd

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

@NikkiWines Looks good! Just missing native/mWeb screenshots :bow:

Ah yeah, I've been having troubles with my iOS and Android emulators lately, hence the lack of videos. I'll try to get those sorted today but otherwise since this doesn't actually impact the UI it should be consistent across all platforms and I think we can merge.

@NikkiWines Ah no worries, I'll just approve then!

@MonilBhavsar thanks for the review, updated!

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to production by https://github.com/thienlnam in version: 1.4.31-7 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅


ERROR RUNNING BACKEND: fast_composite_scaled_bilinear_sse2_x888_8888_normal_SRC ("InferModules__Die.InferInternalError

Running infer on Firefox code generated the following backtrace:

ERROR RUNNING BACKEND: fast_composite_scaled_bilinear_sse2_x888_8888_normal_SRC ("InferModules__Die.InferInternalError
(\"Unexpected call expression null\")")

BACK TRACE
Raised at file "base/Die.ml" (inlined), line 27, characters 6-36
Called from file "base/Logging.ml", line 284, characters 58-80
Called from file "IR/HilInstr.ml", line 113, characters 12-84
Called from file "absint/LowerHil.ml", line 53, characters 6-96
Called from file "absint/AbstractInterpreter.ml", line 70, characters 19-72
Called from file "list.ml", line 96, characters 24-34
Called from file "list.ml" (inlined), line 96, characters 12-36
Called from file "list.ml" (inlined), line 96, characters 12-36
Called from file "src/list0.ml" (inlined), line 24, characters 40-81
Called from file "absint/AbstractInterpreter.ml", line 80, characters 38-94
Called from file "absint/AbstractInterpreter.ml", line 137, characters 14-76
Called from file "absint/AbstractInterpreter.ml" (inlined), line 152, characters 4-59
Called from file "absint/AbstractInterpreter.ml" (inlined), line 163, characters 18-56
Called from file "absint/LowerHil.ml" (inlined), line 99, characters 22-89
Called from file "concurrency/RacerD.ml", line 993, characters 10-50
Called from file "list.ml", line 96, characters 24-34
Called from file "backend/ondemand.ml", line 152, characters 51-92

I think I see the problem, but would you mind sharing a repro of the command you're running in Firefox so I can be sure?


update instructions for codeless connector

Update instruction for codeless connector validation since the DataConnector_API_CCP_template.json won't work out of the box until you reduce it to just the connectorUiConfig collection.
Tested each template with the validation tool, and only the CCP template fails. Determined the template will validate when reducing to just the connectorUiConfig collection.
Reason to change - I want to be able to point to this validation tool from the codeless connector learn/docs page.

Hi @v-vdixit, please provide your feedback. Thanks

Hi @austinmccollum we are looking into this, thanks!

Hi @austinmccollum we are still working on this, thanks!


rac-261 stream monitor base matcher logic.

This story was pre-dojo and is way too long. It is a good checkpoint of the asynch matching engine to date, however!
Primary feature chunks in here:

Added the stream-monitor base plugin. This is the classes that specific stream monitors will be based on.
Added a matcher engine (stream_matchers_base.py)
** ordered and unordered groups of matchers, along with a root group. The groups are the entry point for processing "events" and do a lot of the common logic.
** a StreamMatchBase that protocol-specific matchers will subclass to implement their special sauce. Handles a lot of common logic, leaving as little as possible to be done in the subclass. Mostly implementing '_match' to try and see if an event matches or not.
** a match-batch class to tie events to the results of various matchers in the groups
Added various matched-types in stream_matchers_results
** MatcherResult (base class)
** MatcherUnderMatch -- indicates a match fail because not enough matches were seen on the given matcher
** MatcherOverMatch -- indicaes a match fail because too many matches were seen on the given matcher
** MatcherCleanHitResult -- indicates success. Yay!
** MatcherOrderedMissMatch -- indicates out-of-order seen in an ordered group
Created a selftest stream-monitor with a simple exact string match matcher and injector
And since this IS TDD, there is a test_matchers.py plugin tester.

The bigger pieces of "todo" left are:

make it possible to do the injections from a different greenlet to actually simulate async
add a "wait_for" type operation (right now there is a "finish" call that just examines already injected events)

However, I want to get this in and start doing much smaller stories for the pieces. Also, the next step is to add the AMQP stream watcher, which pretty much means those two "todos" happen in that sequence of stories.
Note: also modified "mkcheck.sh" to pass on arguments the flake8 to allow testing of a specific file (or in this case, subdirectory)
One thing to remember is that this is the engine bits. The dev-facing "api" is very open to amendment in the next stories.
@hohene @diontje @gpaulos @RackHD/corecommitters

BUILD RackHD #1375 : FAILURE

** BUILD SmokeTest-FIT  #645: FAILURE
** BUILD Install-Ubuntu-14-04  #608: SUCCESS
** BUILD SmokeTest-CIT  #839: SUCCESS
** BUILD Install-CentOs-6.5  #630: SUCCESS

test this please


📚Update README with SYSL_PLANTUML env description

Fixes # 148.
Changes proposed in this pull request:

Update README with SYSL_PLANTUML env description

@anz-bank/sysl-developers

@juliaogris thank you for following this up! not a tricky one but improves usability for new devs.

@anz-rfc , @anzdaddy - updated, please have another look.


Improve chat_view.xml layout preview

Jira issue:

no ticket -

What was solved?
These changes were made specifically to preview chat_view.xml. Here are some key points:

AppBarView and its sub-views were throwing NullPointException because of Dependencies.localeProvider
Added dummy content for the GvaChipGroup view

Release notes:

[ ] Feature
[x] Ignore: no effect for client
[ ] Release notes (Is it clear from the description here?)
[ ] Migration guide (If changes are needed for integrator already using the SDK - what needs to be communicated? Add underneath please)

Additional info:

[ ] Is the feature sufficiently tested? All tests fixed? Necessary unit, acceptance, snapshots added? Check that at least new public classes & methods are covered with unit tests
[ ] Did you add logging beneficial for troubleshooting of customer issues?
[ ] Did you add new logging? We would like the logging between platforms to be similar. Refer to Logging from Android SDKs → Things to consider for newly added logs in Confluence for more information.

Screenshots:
Before

After

Good Idea! 👍

Added new commit to fix issues with locales in paparazzi


Notifications

A way needs to be created that allows us to create notifications in a easy way using the Spectre toasts component.
Ideally would a function/object be added to the Vue instance.
A notification could be a warning/success/error.
Example
new Vue({
  mounted: function() {
    this.$notification.success('Vue is mounted!')
    this.$notification.error('Something went terribly wrong')
  }
})

Does user needs to allow notifications in browser?

No a notification is a small popup in the bottom right corner


For testing it would be nice to have set_data method in RequestExt

How do people do write unit tests against handler that use Routerify's request data?

@ry
The RequestExt.data() method facilitates data and app state sharing across route handlers, middleware, and the error handler in Routerify. For further information, please refer to the documentation here.
Currently, there is no public API available to directly test the handler with Routerify's request data. To address this, we can propose two possible approaches:
Approach 1: Expose SharedDataMap and DataMap internal types as follows:
#[tokio::test]
async fn test_router_handler() {
    struct Data(u64);

    // A handler for "/" page.
    async fn home_handler(req: Request<Body>) -> Result<Response<Body>, Infallible> {
        // Access the app state.
        let data = req.data::<Data>().unwrap();

        Ok(Response::new(Body::from(data.0.to_string())))
    }

    let mut req = Request::builder()
        .method("GET")
        .uri("http://localhost/example")
        .body(Body::empty())
        .unwrap();

    // Prepare data.
    let mut data_map = DataMap::new();
    data_map.insert(Data(100));
    let shared_data_maps = vec![SharedDataMap::new(Arc::new(data_map))];

    // Inject the data to Request's extensions..
    let ext = req.extensions_mut();
    ext.insert(shared_data_maps);

    let resp = home_handler(req).await.unwrap();

    let resp = into_text(resp.into_body()).await;
    assert_eq!(resp, "100");
}

Approach 2: Introduce a separate method called set_data_test() in RequestExt for modifying shared data in the test environment:
#[tokio::test]
async fn test_router_handler() {
    struct Data(u64);

    // A handler for "/" page.
    async fn home_handler(req: Request<Body>) -> Result<Response<Body>, Infallible> {
        // Access the app state.
        let data = req.data::<Data>().unwrap();

        Ok(Response::new(Body::from(data.0.to_string())))
    }

    let mut req = Request::builder()
        .method("GET")
        .uri("http://localhost/example")
        .body(Body::empty())
        .unwrap();

    // Update the shared data only for this request.
    req.set_data_test(Data(100));

    let resp = home_handler(req).await.unwrap();

    let resp = into_text(resp.into_body()).await;
    assert_eq!(resp, "100");
}

IMO, We should go for Approach 2 and expose the set_data_test method only for test environment.

@rousan I concur.

You can always set your data container as something like Arc<RwLock<T>> then you can just update inside of it as *r.data().unwrap().write() =
this would be a solution to what you are asking for.
Also you can use Any type and downcast it safely to any value this is another solution to your particular problem.
In either case this is a niche problem and I dont think this should be supported in routerify itself since it can cause more problems then it solves. As I demonstrated above routerify doesnt really prevent you from doing this by yourself but this is an app specific issue rather than being a general issue in the domain what routerify tries to solve

@ta3pks,
this is a good solution, but you need to write a router builder and then setup a mock server and send a mock request to the server to unit-test a handler.
@ry is trying to unit-test the handler directly by passing the req as an argument.

Oh i see I got it wrong then. But in this case I dont think he should be involving routerify in his unit tests since he is not testing routerify but his own application logic. I still believe this is not a case routerify should try to solve this seems a design issue with the app that utilizes routerify


Optional CPU limit in while: True loops

As vidgear uses several, non-limited while True loops, I can see 100% CPU usage per core, most notably in Netgear.recv(). Includes fans going at 100%.
Detailed Description

While I'm sure there are many dependencies and special cases I'm ignoring, my fork currently uses a simple sleep(0.02) as such: https://github.com/otter-in-a-suit/vidgear/commit/a8534de14f0977d5e507d7a7afdf1f0d877751ab
I'm not sure if there is a better, synchronized way, but any form of limiter would be amazing.
Context

I am using Vidgear for a network-driven security camera: https://github.com/otter-in-a-suit/scarecrow
Running vanilla vidgear causes 100% CPU usage on all cores used by the API.
Your Environment

VidGear version: 0.1.6 (fork)
Branch: Development
Python version: 3.7.3
pip version: 18.1
Operating System and version: Linux pop-os 5.3.0-7625-generic #27~1576774560~19.04~f432cd8-Ubuntu SMP Fri Jan 10 16:25:52 UTC  x86_64 x86_64 x86_64 GNU/Linux

Any Other Important Information

With 0.02s sleep:

Without:

Both on an empty receive, i.e. with no active sender.

@otter-in-a-suit Why not add time.sleep(0.02) in your script code rather in vidgear code? Isn't it will be more convenient? It will have the same effect.

Please correct me if i read the code wrong, but from what I can tell, self.terminate in the Neatgear.recv() method evaluates to a while True, as without incoming data (which is a use case, I believe), it waits forever on data and hence, never sets the self.terminate flag.

self.terminate in the Neatgear.recv() method evaluates to a while True, as without incoming data (which is a use case, I believe), it waits forever on data and hence, never sets the self.terminate flag.

Not exactly, self.terminate flag depends on two factors in receive mode(i.e receive_mode = True):

terminate_flag received from the server to which it is connected:

Makes self.terminate =True. See here:
https://github.com/abhiTronix/vidgear/blob/8357aa5d6df59df45bd21a7c23c0950c6b152f59/vidgear/gears/netgear.py#L554-L576

User clicks CTRL+C keyboard Interrupt on the keyboard:

This will force terminates the loop by making self.terminate =True. See here:
https://github.com/abhiTronix/vidgear/blob/8357aa5d6df59df45bd21a7c23c0950c6b152f59/vidgear/gears/netgear.py#L745-L760

@otter-in-a-suit The termination based on Server response has both pros and cons. But you can yourself add a timer in your script to tackle this so that it self-terminates after a fixed amount of time if no response is received from the server.

Thanks for the explanation!
In the use case I am referring to, the server might no exists (yet). This could happen in a couple of scenarios, I believe. For instance, if the device sending the stream is not available, busy, has bad network connection, or simply does not send data continuously. An example for the latter could be a doorbell-camera, which would only send data upon somebody pressing it. In these cases, I would still want my server to be listening, but not at 100% CPU capacity.
If I add a thread that waits for X seconds on a response, I am still wasting a lot of CPU cycles for the thread, the server will run on 100% CPU on one core while waiting during that time, I add artificial delay in the times I'm not actively listening, and I am forced to re-start the receiver after a while, as I do expect a response eventually. In this scenario, there also won't be any user input, as it's running headless, for instance via a systemd service.

but not at 100% CPU capacity.

@otter-in-a-suit Something is wrong here. Can you share your script code that you're using to access NetGear API?

Here's a minimal example that I stripped from here: https://github.com/otter-in-a-suit/scarecrow/blob/master/server/receiver.py#L56
from vidgear.gears import NetGear
import logging
import cv2

logger = logging.getLogger()
client = NetGear(address='<IP_ADDRESS>', port=str(5454), protocol='tcp',
                     pattern=1, receive_mode=True, logging=True)

while True:
    # receive frames from network
    frame = client.recv()
    logger.debug('Image received')
    #image_np = np.copy(frame)
    # check if frame is None
    if frame is None:
        logger.error('No frame available')
        break

    key = cv2.waitKey(1) & 0xFF
    # check for 'q' key-press
    if key == ord("q"):
        # if 'q' key-pressed break out
        break

Please notice how there is no sender active, for the use case I've outline above.
Without 0.02 sleep:

With:

See how one core is at 100%. The fans on my System76 Gazelle are also going crazy due to that.
Hope this helps!

address='<IP_ADDRESS>'

@otter-in-a-suit This means you're running your both server & client on your local machine, and both are sharing the same resources, thereby 100% CPU is obvious and is certainly not the correct way to benchmark it. But yeah, NetGear is surely using a lot of resources(not 100%) but more then it is intended to, and also ZMQ internals are also responsible for the same.
No doubt, Adding time.sleep() is suspending CPU for a short duration, but it is just a dirty fix but not an ideal solution for doing the same, you're also delaying your output on a faster connection. The correct solution that I'm planning to incorporate asyncio with vidgear for a long time and I think it is the future for this library. Ascynio has many inbuilt functions that can quadruple performance while using minimum system resources in NetGear. I'm postponing this feature for the future since I'm super busy with other projects but when I'll push PR related to it you'll be informed first. So stay tuned.

The same thing happens over the network. But as stated in the original post, yes, sleep is a really bad workaround.
Thanks for your explanation - looking forward to any improvements! :)

Hey @otter-in-a-suit, Thanks for your patience, Kindly reinstall the new NetGear_Async API PR(#114) as follows:
git clone https://github.com/abhiTronix/vidgear.git
cd vidgear
git checkout development
sudo pip3 install .
cd

and test the usage examples from its wiki and see if it solves memory problem? and then revert here!

@otter-in-a-suit Closed and marked solved for now. Kindly share your results when you're ready. Good luck!

Overall
Thank you for this change! it will take me a while to update my code to use asyncio, but I have run several preliminary tests with the new branch.
I haven't pushed my changes to my own project just yet.
Test approach:

Updated https://github.com/otter-in-a-suit/vidgear/tree/development from master repo
Updated https://github.com/otter-in-a-suit/scarecrow/blob/development/sbin/install_vidgear.sh
Ran ./sbin/install_vidgear.sh
Check

(env) christian @ pop-os ➜  scarecrow git:(testing) ✗  pip3 list | grep vidgear
vidgear              0.1.7.dev1

Added asyncio to requirements.txt / setup.py
Updated sender, receiver to new async code

Problems & Resolutions
Dependencies
Issue:

E   ModuleNotFoundError: No module named 'starlette'
E   ModuleNotFoundError: No module named 'aiofiles'
E   ModuleNotFoundError: No module named 'aiohttp'
...

Background:
You are using pip3 install .[asyncio], which references your setup.py.
Resolution:
As this contains these dependencies, I've added the line to my sbin script. Maybe update the docs?
Issue:
NetGear_Async :: ERROR :: 'NetGear_Async' object has no attribute '_NetGear_Async__address'
Traceback (most recent call last):
  File "/home/christian/workspace/scarecrow/env/lib/python3.7/site-packages/vidgear/gears/asyncio/netgear_async.py", line 304, in __server_handler
    self.__protocol + "://" + str(self.__address) + ":" + str(self.__port)

Background:
If receive_mode is set to False, __address is not set. This is an oversight in the else clause.
Resolution:
Pull request: https://github.com/abhiTronix/vidgear/pull/118
Issue:
NetGear_Async :: WARNING :: Invalid pattern. Defaulting to `zmq.PAIR`!
Background:
Your example in the docs does not show all kwargs. When updating from legacy to 0.1.7.dev1, old code breaks. This should return the invalid pattern.
Resolution:
Pull request: https://github.com/abhiTronix/vidgear/pull/118
Issue:
On any of the above failures, the thread does not complete and deadlocks.
Background:
I am not familiar with asyncio (yet :)). Probably an issue on my end.
Resolution:
N/A

Dependencies
Issue:
E ModuleNotFoundError: No module named 'starlette'
E ModuleNotFoundError: No module named 'aiofiles'
E ModuleNotFoundError: No module named 'aiohttp'
...

Background:
You are using pip3 install .[asyncio], which references your setup.py.
Resolution:
As this contains these dependencies, I've added the line to my sbin script. Maybe update the docs?

@otter-in-a-suit Sorry I didn't added line pip3 install .[asyncio] above. But you can already find correct way to install dependencies in its wiki

Issue:
NetGear_Async :: WARNING :: Invalid pattern. Defaulting to zmq.PAIR!
Background:
Your example in the docs does not show all kwargs. When updating from legacy to 0.1.7.dev1, old code breaks. This should return the invalid pattern.
Resolution:
Pull request: #118
Let's work on this issue on other issue you created more recently.

@otter-in-a-suit adding small sleep command does helps in reducing load. I'll add this fix in next PR.

Successfully resolved and merged in commit 8f8d951


Parse hsl/hsla colors

#15128 has caused a regression of #10195
Although HSL is relatively rare some Mapbox styles e.g. https://github.com/OrdnanceSurvey/OS-Open-Zoomstack-Stylesheets/blob/master/Vector Tiles/Mapbox GL Styles/OS Open Zoomstack - Outdoor.json use it heavily, so it would now be more efficient to parse instead of reverting to using getComputedStyle.  The algorithm is based on the older longer version in https://stackoverflow.com/questions/36721830/convert-hsl-to-rgb-and-hex which gives the same result as getComputedStyle in Chrome, which the new shorter version does not.

Thanks, @mike-000.  We should have requested a test in #10195.  Without one, we can expect more regressions in the future (anything that is not tested should not really be trusted).


fix: signature_validation_credential_id not persisted in create api

@bzwei can you redo this PR with the other changes from credential-spike @hsong-rh has fixed all the test failures


Accept Sensitive for CID

We pull the Value for CID from our Secret-Vault, as we consider CID as worthy of Protection.  Our Secret-Vault yields Sensitive[String].  In my Opinion Writers of Profile-Modules should not be bothered with handling Values of Type Sensitive.  Passing them over to the Component-Modules, (like “falcon”) should “just work”.

let init.pp accept CID of Datatype Sensitive[String]
do the Unwrap at the latest possible Location

@cocker-cc sorry for the delay - I will review this soon. Thanks for your patience and contribution!

@cocker-cc thanks for your PR v0.8.0 has been released with this change


Drop multi_json dependency

As discussed in https://github.com/oauth-xx/oauth2/issues/579#issuecomment-1084174454, the Ruby JSON stdlib module should be good enough.
Closes #579

Codecov Report

Merging #590 (08f7c75) into master (7e5cd6c) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #590      +/-   ##
==========================================
+ Coverage   89.66%   89.70%   +0.04%
==========================================
  Files          15       15
  Lines         445      447       +2
==========================================
+ Hits          399      401       +2
  Misses         46       46

Impacted Files
Coverage Δ

lib/oauth2/response.rb
100.00% <100.00%> (ø)

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more

Code coverage failure: SimpleCov failed with exit 2 due to a coverage related error
Rubocop failure: Will be fixed in 16345ec1e12c348fc752b851173c22a8c7b68a8f via https://github.com/oauth-xx/oauth2/pull/589


Exception: Incorrect parameter. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))

I'm using the extension for the first time in a my solution, with the new Visual Studio 2019.
I have some solution folders where there are some document files (release_notes.txt & c).
Seems that TSVN is not able to manage these files, every time, for every command, raise the exception (exception translated from the Italian language, I'm not sure that the exception description is exactly that):
Incorrect parameter. (Exception from HRESULT: 0x80070057 (E_INVALIDARG))
All these 'solution folder' are present also on disk inside the working copy root!

Did you install TortoiseSVN with the client tools?
https://github.com/sboulema/TSVN/wiki/Menu-items-not-working#tortoisesvn

Yes, I have checked today again the installation and the client tools are installed!
In the normal files, stored inside a project, the TSVN extension works fine, the problem seems only for the files, inside the solution folder (that, I repeat, are not real folders, probably this is the problem).

I find out that I get this Exception only if I have the Manage NuGet Packages window open. Pershaps this helps. If I close the window all works fine again.

In my case it was the "Publish" Website window.
Works fine when I close it, when the window is open Commit or update do not work.


Fix typo: AesCrytpServiceProvider -> AesCryptoServiceProvider

Corrects this document's filename and text.

@chlowell,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

Thanks for catching that. I fixed all the migration guides, and another crypto typo in the app configuration docs.


allow better subclassing of Connection

allow subclassing Connection without having to instantiate abstract constants in an abstract subclass
aka Connection > SqlConnection > UserConnection (don't require SqlConnection to have to instantiate TNode)
Also make TNode abstract type enforceable

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Kyle Brenneman seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


[Accessibility] Duplicate IDs are present in Input and Textarea components

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
An expected behavior for a standard Input (with an associated Label) is to have a unique ID for each pairing.
Current Behavior
The current Input and Textarea components are providing a defaultProp for ID using the getBuiId utility. Since defaultProps is a static method and it isn't called on instances of the class, the ID is being duplicated across all usages.
Example of htmlFor duplication in Label:

Storybook a11y failures:

Context
I'm not too familiar with the layout of this repo, but I have a simple commit (https://github.com/austin94/baseui/commit/c39199a8745065d796eb8643de3333a8d071abcf) that includes some fixes for this issue.
It includes:

Remove ID defaultProp from all components
Generate a unique ID for each instance, similar to the Popover implementation

Not applied to BaseInput and TextArea since there are no associated Labels that require it

Update snapshots and add htmlFor assertion

If any of this seems reasonable I can open a PR if wanted. Thanks 👋!
Your Environment

Tech
Version

Base UI
master

React
^16.4.0

browser
Chrome

node.js
v9.11.1

Steps to Reproduce
https://baseui.netlify.com/?selectedKind=Input&selectedStory=Controlled and uncontrolled input&full=0&addons=1&stories=1&panelRight=0&addonPanel=REACT_STORYBOOK%2Freadme%2Fpanel

thanks a lot for reporting it @austin94 - can you open a pull request with your changes?

can you open a pull request with your changes

Will do.


Fix some several easy-to-fix issues.

Fix issues:

#189
#219
#206

Thanks for that suggestion! I had no idea mixing could be "batched". And, as a bonus, that also removes 3 other unneeded files, and makes this work with any farmland that uses the c:farmland tag. I just implemented it myself, as it was easier.

Hmm, I'm new to mixins and only do simple ones, but, I'm afraid, your comment went over my head.  I'm not sure what you mean by I'm not changing the return value, as it would normally return FALSE if it  was not minecraft:farmland and now returns FALSE if it is not #c:farmland.

In addition to canceling when your mixin does change the return value (when the block is not minecraft:farmland but it is in the c:farmland tag), it also cancels in all other cases.  Because of how simple the target method is, this is not a huge deal, but it is better to avoid canceling in the other cases.  For example:
    @Inject(at = @At("TAIL"), method = "canPlantOnTop", cancellable = true)
    private void plantBlocksCanPlantOnTopOfRichSoil(BlockState floor, BlockView world, BlockPos pos, CallbackInfoReturnable<Boolean> cir) {
        if (!cir.getReturnValue() && floor.isIn(TagsRegistry.FARMLAND)) {
            cir.setReturnValue(true);
        }
    }

Also, if you think I should just check if it's fd:rich_soil_farmland just not to mess up other mods I'll do that.

It's what I would do, but both of these are more "best practices" things.

Okay, now I see. I had thought that injecting into the method auto-canceled it, even when your return was false. I will do what you said. Now I understand why this method did it in an if statement.

Should I remove the FARMLAND tagkey and the new method I added?

Should I remove the FARMLAND tagkey and the new method I added?

Probably, since they're no longer used.  This does look pretty good to me now.  Bear in mind, though, I am not a maintainer of Farmer's Delight so they might have some other request.


direct link to .egg package

I'm packaging a python egg file for a linux distribution and it requires me to specify a directly link to a file. Currently, it is possible to request for it via API, however this feature not available for me.
The closest what I found is the following URL:
https://pypi.org/simple/
So if I need to get a link for frida-12.0.3-py3.6-linux-x86_64.egg file for example, I need to visit
the URL https://pypi.org/simple/frida/, search for this filename and copy the link.
However, I cannot automate it. It would be more useful if you could redirect the following URL (in my example): https://pypi.org/simple/frida/frida-12.0.3-py3.6-linux-x86_64.egg to the direct link.
Thank you in advance.

@blshkv see https://warehouse.readthedocs.io/api-reference/integration-guide/#querying-pypi-for-package-urls for more information on how you might obtain the direct link.
The URL you want a redirect for would be:
https://files.pythonhosted.org/packages/3.6/f/frida/frida-12.0.3-py3.6-linux-x86_64.egg
This will return an HTTP redirect to https://files.pythonhosted.org/packages/73/d8/ffeed9316a2e73ec1920c02bb1bfb37db62c6b56e83b5d3d0e6c17ae63b2/frida-12.0.3-py3.6-linux-x86_64.egg

Perfect, thank you for pointing that out!

Hi, can you help me find a similar link for .whl  https://pypi.org/simple/orjson/ please?
I tried few schemes and unable to figure it out :\

As explained in https://warehouse.readthedocs.io/api-reference/json.html, you can load https://pypi.org/pypi/orjson/json. You'll find the link in the payload, depending on if you want a stable or cutting edge version, a wheel or a tar.gz etc.

that doesn't work well for me, unfortunately. I'm trying to package a package for Gentoo, and need a universal URL, similar to the one which you provided before: https://files.pythonhosted.org/packages/3.6/f/frida/frida-12.0.3-py3.6-linux-x86_64.egg which would redirect to a next location. If not, I would need to write a separate eclass to extract it, but parsing JSON in bash might not be that easy.

parsing JSON in bash might not be that easy

If you can use jq, it's usually not that bad.
Otherwise, I note that it's quite rare for a project in 2021 to still expose egg files, the standard is wheel.
The URL you're looking for is something around:
https://files.pythonhosted.org/packages/cp36/o/orjson/orjson-3.5.4-cp36-cp36m-macosx_10_9_x86_64.macosx_11_0_arm64.macosx_10_9_universal2.whl
The part you had wrong was probably the "python version". One way to find the information that it needs to be cp36 and not 3.6 or something: starting from @ewdurbin 's advice that it was using the conveyor service, search for its code source: https://github.com/pypa/conveyor/blob/master/conveyor/views.py and see that it looks for the matching python_version field in the JSON API, so looking at the JSON API, orjson's python_version fields looks like cp36 and the rest is following the doc :)

That works. Thanks a lot!

hm.. what would be the url for https://pypi.org/pypi/semgrep/json please?

I've outlined the exact method for figuring it out above.
https://files.pythonhosted.org/packages/cp36.cp37.cp38.cp39.py36.py37.py38.py39/s/semgrep/semgrep-0.57.0-cp36.cp37.cp38.cp39.py36.py37.py38.py39-none-any.whl
You're welcome to request help again if you find a package for which the method above doesn't work, but if it does, please follow it. Otherwise, I might not be a very reliable human API (my SLA are probably aweful).

Didn't expect it that long, but I figured it out at the end. Thanks a lot!


First Pass at Bootstrap Process

I've added a few structural things here to try and start addressing the meta process questions raised in #2 – let me know what you think.

I took a first pass at adding some basic process, context setting, and expectations for Bootstrap in the project's main README.
I've made dedicated, slightly more fleshed out documents for:
Foundation Expectations (seeded with @bnb and @hackygolucky's content PR'd in #4 and #6)
CPC Expectations (With context setting at the top, and a bit 'ol TODO:)
C3 Expectations (With context setting at the top, and a bit 'ol TODO:)
Inside of /projects I've added a structured RFC process for proposing new governance features along with a proposal for an RFC template.
I've added an empty /governance folder where I'm envisioning that, after an RFC proposal has been accepted, more refined copy can be placed (see description in the RFC process README). I'm picturing these will be like the documents present in the CNCF TOC's /process and /workinggroups directories

Huh, Github did something weird since I branched off of Tierney's branch, but PR'd against master. All well. Diff still looks correct.

I agree with @rubys that the sticky notes should be captured as initial brainstorming since not everybody could be in the sessions and we need to follow the same process for all input.  Using the RFC process makes sure we have a level playing feed.
This does mean that we'll need champions to submit RFCs for the initial input from the brainstorming to make it into the final result, but that seems like the right way to go to me.

Good work!
Before landing this, I would ask all the leadership of the JSF projects if they want to be involved. We should track the answers.

Updated with the typo fixes mentioned above. I see three (3) things that need to happen before merging – hopefully we can converge on these in the meeting today!

[ ] Reconcile the README with @jasnell's version in #9
[ ] Determine who chairs this group and by what process they are picked
[ ] Discuss what deliverable are for charter work

Also, for the sake of issue cross reference, breakout session takeaways have been documented in #11 and #16

@rubys

What would complete that for me is a description of the relationship between the sticky notes and the RFCs. I would be happiest if the sticky notes were described something along the lines of brainstorming which will inform us as to which RFCs need to be written, but ultimately the RFCs are the concrete actions that either are taken or dropped.

I've clarified this a little bit in #11 as:

Programs that emerged from the session were grouped by the Foundation Value they most support. Programs would be administered by one or both of the Top Level Councils (CPC or C3). Each actionable program can conceivably go through the Program RFC Process defined in /programs currently proposed in PR #7.

Ideally, I'd love to see every program (read: governance document that is not a charter) go through the RFC process. Every program identified in #11 could be championed through the RFCs.

Since there has not yet been an update to this PR should we remove it from tomorrow's agenda?

@MylesBorins, finally digging into breaking this out into the appropriate relevant PRs as agreed, but I think the best way forward may be to simply close this and allow the other threads of conversation move forward naturally.
A lot has changed since this was drafted and much of its concerns are captured elsewhere. I've left comments on the other PRs in the few places where there is content missing – small points on #23 / #32, and some content missing from #6. Will leave it up to you to close if you agree 👍

See #40

Also, https://github.com/nodejs/bootstrap/pull/42


:bug: Only remove stop words

Also, move pre-processor scripts into their own directory.
Note: would be good to write tests for the pre-processing code but given the switch away from MongoDB it is probably not worth it a t this stage.

:rocket: deployment of profiles-db succeeded (http://profiles-db-pr-56.dev.beta.nhschoices.net)


Update tracking.md

Per MS style guide

Avoid future tense
drop () from methods

Use bigger ideas, fewer words : Our modern design hinges on crisp minimalism. Shorter is always better.
Short sentences and fragments are easier to scan and read. Prune every excess word.
Contributes to https://github.com/dotnet/AspNetCore.Docs/issues/23572

PR not passing checks.

Nothing to do with my changes
Error: entity-framework/core/querying/tracking.md:82:1 MD004/ul-style Unordered list style [Expected: asterisk; Actual: dash]
I'll fix these.


Crash  on Socket.close()

First, thank you for developing this fantastic lightweight server!
We've encountered a recurring crash, primarily when the iOS app is running in the background. The crash log is as follows:
Crashed: com.apple.root.user-initiated-qos.cooperative
0  libsystem_kernel.dylib         0x1e64 close + 8
1  App                          0x71c300 Socket.close() +<PHONE_NUMBER>
2  App                          0x6f7eb8 HTTPServer.start() +<PHONE_NUMBER>
3  libswift_Concurrency.dylib     0x41948 swift::runJobInEstablishedExecutorContext(swift::Job*) + 416
4  libswift_Concurrency.dylib     0x42868 swift_job_runImpl(swift::Job*, swift::ExecutorRef) + 72
5  libdispatch.dylib              0x15944 _dispatch_root_queue_drain + 396
6  libdispatch.dylib              0x16158 _dispatch_worker_thread2 + 164
7  libsystem_pthread.dylib        0xda0 _pthread_wqthread + 228
8  libsystem_pthread.dylib        0xb7c start_wqthread + 8

To provide further context, here are relevant code snippets related to how we start and stop the server:
 func start() {
        Task {
            do {
                if await !server.isListening {
                    try await server.start()
                }
            } catch (_ as CancellationError) {
                print("Task cancelled")
            } catch {
                logger.error("Error local server: \(error.localizedDescription)")
            }
        }
    }

    func stop() {
        let task = Task {
            await server.stop()
        }
        task.cancel()
    }

Thanks!

Thank you for reporting this issue 🙏🏻
Please let me know if https://github.com/swhitty/FlyingFox/issues/66 fixes the issue for you.

Thanks a lot the crash is fixed!


Phase 1: recursively parse include statements and generate a final augmented yaml file

Fixed by PR https://github.com/WLCG-Lightweight-Sites/simple_grid_yaml_compiler/pull/5


Improve security

Update the bicep files from the AZD source repo

Please can you rebase so we can do the security tests again


Support ellipse selections

Oops, the first commit belongs to the other PR and shouldn't be here... If needed I can clean this up.

Interesting, I'm not sure if this has a wide enough use case but going to try it out and see what it looks like cause I'm curious!

Cool!
The use case for us is that we allow users to select circular avatars. So to be honest we also only care about the circular use case (which can be easily enforced by specifying a fixed aspect ratio of 1.0), but for flexibility I implemented it as generic ellipses.

@arendjr, I am using this library for circular avatars as well. I am very happy with rectangle crop area and separate preview, which renders image with border-radius 50%.

Yes, that would be another work-around :)
But then don't you like the prospect of being able to select the circle right away and not needing a separate preview anymore?

@arendjr, not only circular thing is previewed but also crop and scale, so I am very happy with it :)


Caught egl initial wrong when use multiprocessing

I'm new in mujoco. And I'm using mujoco for reinforcement research. I have designed an environmnet using mujoco which needs render to get version data. I use ssh connect with my server whose operator system is ubuntu 20.04 and use egl as my render backend. At the beginning, it runs with any problem. To accelerate the data collection process, I try to use multi-processing. I use python(py3.8 and mujoco python bindings is 2.3 which is the latest version) and once I run multi-process, I caught
AttributeError: 'GLContext' object has no attribute '_context'.
I'm sure there is no problem with my code because it works well in another computer whose os is windows.

Please post a full stack trace.

Exception ignored in: <function GLContext.del at 0x7f465c83ae50>
Traceback (most recent call last):
File "/home/liuzekun/anaconda3/envs/robot/lib/python3.8/site-packages/mujoco/egl/init.py", line 130, in del
self.free()
File "/home/liuzekun/anaconda3/envs/robot/lib/python3.8/site-packages/mujoco/egl/init.py", line 120, in free
if self._context:
AttributeError: 'GLContext' object has no attribute '_context'
When I run 20 process paralley of mujoco to collect trainning data，every process caught this problem. But if I run process one by one, it runs collectedly.
Interesting, I ran a single process yesterday, and it works correctly till now. But when I try to reproduct the bug, the process also caught GLContext error.

Same problem! Is there any progress?

It's strange that I change the method to create mujoco process from multiprocessing.Process to multiprocessing.Pool, it runs successfully. Anyway, this issue can be closed.

I have tried for long time. When I run my program in m1 chip macOS, it runs successfully, but it occur "egl init wrong" on x86 chip ubuntu.

Hi @TypeFloat, can you check if the latest release (3.1.0) fixes your issue? We've added a close method that you should call to free up resources associated with the renderer object. You can use it as follows:
# Option 1.
renderer = Renderer(...)
# Use renderer.
renderer.close()

# Option 2.
with Renderer(...) as renderer:
# Use renderer.

I appreciate your attention, but unfortunately, the close function doesn't work. My requirement was to enable multiple renderers at the same time(because I use multiprocessing), not turn them on and off in sequence, so freeing resources didn't work. Below is a simple example I implemented, reproducing my problem on my server (ubuntu20.04 OS, python=3.9, mujoco=3.1.0).
import mujoco
def para_func():
xml_path = "assets/robot-0.xml"
model = mujoco.MjModel.from_xml_path(xml_path)
data = mujoco.MjData(model)
with mujoco.Renderer(model, 960, 1280) as r:
r.update_scene(data)
r.render()
if name == "main":
import multiprocessing
with multiprocessing.Pool(3) as pool:
    for i in range(3):
        pool.apply_async(para_func, error_callback=print)
    pool.close()
    pool.join()

Traceback is below:
Traceback (most recent call last):
File "/home/*/miniconda3/envs/mujoco/lib/python3.9/site-packages/mujoco/egl/init.py", line 130, in del
self.free()

File "/home//miniconda3/envs/mujoco/lib/python3.9/site-packages/mujoco/egl/init.py", line 120, in free
if self._context:
AttributeError: 'GLContext' object has no attribute '_context'
Exception ignored in: <function Renderer.del at 0x7f6f90215790>
Traceback (most recent call last):
File "/home//miniconda3/envs/mujoco/lib/python3.9/site-packages/mujoco/renderer.py", line 327, in del
self.close()
File "/home/*/miniconda3/envs/mujoco/lib/python3.9/site-packages/mujoco/renderer.py", line 315, in close
if self._gl_context:
AttributeError: 'Renderer' object has no attribute '_gl_context'

Hi @TypeFloat, can you try adding multiprocessing.set_start_method('spawn') right after the import? It solves my multiprocessing issue.

@kevinzakka Amazing, thanks for you helping! The code works well on ubuntu.


"Feedly" stays highlighted even after canceling prompt for sign-in

iOS
Version: 5.0.1 (41)

Go to NNW's Settings, then tap "Add Account". You see the list of On My Phone, Feedbin, Feedly.
Tap "Feedly".
You get a prompt "NetNewsWire wants to use 'feedly.com' to sign in". Tap Cancel.

Expected: You got back to the normal list of On My Phone, Feedbin, Feedly, with none of them highlighted.
Actual: "Feedly" remains the highlighted selection.

Fixed and coming in the next release.


fixing parameter regex to actually capture entire parameter value

It looks like the Segment route does not properly create the param value matching regex, which resulted in parameters with more than one letter in value not matching the route.
This fixes it, although the regex might be too permissive. Please verify and if you approve send Matthew a PR :)

BTW the fix is a simple change to one line - rest of changes are my IDE removing trailing spaces and you can safely ignore them :)

$regex .= '(?<' . $part[1] . '>[^/]+)';

i think its hardcode... maybe I want to use [^-] or other delimiter for 'ending parameter'...
But this is a very simple solution... :)

If you want something more flexible I think you should use the Regex router

It's fixed in the master now, with a much better approach. Will write about it soon. Basically, default delimiter is a slash "/" now, but you can specifiy other/multiple delimiters like this:
/foo/:bar{-/}[-baz]/bat


Add a quick reference menu item

It should pull quick references from the database based on a key, so can do quick refs for artccs, airports, etc. Put a type on the quick ref for future use as well (airport, artcc, etc.)

All wired up. Error handling isn't good though, need to figure out what to do with that.


Committing modified files -- formatting changes.

Reformatted the classes in the "storage/sis-storage/src/main/java/org/apache/sis/index/tree/" directory to use 4-space indentations instead of 2-space indentations.

Merged, thanks! I have also cherry-picked this commit to the geoapi-4.0 branch, which is the current development branch.


Leaflet options are not valid

MapBox API layers are 410 (Gone) and should be removed from leaflet options:
https://github.com/Project-OSRM/osrm-frontend/blob/7466ebadef54a45d01a8e64944d757bc62646284/src/leaflet_options.js#L5-L21
Also, would be nice to have hiking and biking options instead of geofabrik small components which is not available either.

Fixed by #331

Really dont know what is fixed. But it still show
GET https://api.mapbox.com/v4/mapbox.streets/13/2344/3132@2x.png?access_token=pk.eyJ1IjoibXNsZWUiLCJhIjoiclpiTWV5SSJ9.P_h8r37vD8jpIH1A6i1VRg 410 (Gone)


chore: update nodejs version

Fixes #16613

The CI matrix in workflows/build-test.yml still runs v12.

I removed the v12 from the build matrix.
@legobeat @adonesky1  Currently, the extension is using Node v16, and we might want to update it soon to the latest LTS (v18): do you think it would make more sense to update this package to v16 or directly to v18?


Obsoletion request: GO:0061778 intracellular chloride channel activity and child GO:0005229 intracellular calcium activated chloride channel activity

GO:0061778 intracellular chloride channel activity
and child GO:0005229 intracellular calcium activated chloride channel activity
The reason for obsoletion is that these represent a mix of a MF + a CC.
Replace by parent: GO:0005254 chloride channel activity
Thanks, Pascale

@pgaudet Do you not agree that intracellular calcium activated chloride channel activity and it's regulations should be kept?  Thanks.

Hi @raymond91125
The regulation terms need to go for sure, because for the BO refactor we want to obsolete all children of 'regulation of MF'.
I need to look more into the term' intracellular chloride channel activity', it seems we are mixing a MF and a CC.

I need to look more into the term' intracellular chloride channel activity', it seems we are mixing a MF and a CC.

I agree. I moved intracellular calcium activated chloride channel activity from under 'intracellular chloride channel activity'. 'intracellular calcium activated chloride channel activity' is about plasma membrane Cl- channels that have an intracellular Ca2+-binding site. Thus I would keep the term 'intracellular calcium activated chloride channel activity'.

intracellular calcium activated chloride channel activity' is about plasma membrane Cl- channels that have an intracellular Ca2+-binding site.

Oh - I was capturing these as 'intracellularly gated' - is that what you mean here?

Oh - I was capturing these as 'intracellularly gated' - is that what you mean here?

That's right. I regard activated and gated synonymous.

OK sounds good - can you rename 'intracellular calcium activated chloride channel activity' to the same pattern as the siblings, ie 'intracellularly calcium-gated chloride channel activity'?
Thanks, Pascale


Preventing inappropriate role binding deletion

This change prevents role bindings from being inappropriately deleted
when the logic to clean up PSPT related role bindings run.  Right now all existing role bindings are deleted, now only role bindings marked with a PSP annotation will be deleted.
Also cleaned up some bad annotation names.
Issue:
https://github.com/rancher/rancher/issues/12872

LGTM


Add ability to put spesos into cargo console

I thought we had it already but maybe it was an unfinished pr or something.
:cl:

add: Added ability to put spesos directly into cargo request consoles.

THANK YOU


"Switch Network" button throws an error for chainId

Context: An unsupported network is currently selected.
Actions: The "switch network" button is clicked.
Error: "Expected 0x-prefixed, unpadded, non-zero hexadecimal string 'chainId'. Received: 1"

@dmosites is this still an issue? I'm not seeing it on my end. In the ChainSelector branch I saw this issue a lot and was able to fix it. If it's no longer an issue we can close this ticket


Nested*Depth Rules (#248)

Add rules for checking the depth of if, for, try, and when blocks/expressions. I think the speks are relatively thorough, but I'm certainly open to being convinced otherwise.
Probably very open for debate is the default thresholds for each rule. I went for thresholds of 2 for if and for, and 1 for try and when. My rationale is that if and for are generally more constrained than the others in the complexity/number of their possible outcomes. For example, if is a "this or that" proposition, but when has a more arbitrary number of outcomes.

This is a really nice first-time contribution. I really appreciate this. Big thanks!
Appropriate testing can either be done with this script or manually over the mentioned projects in this script. These test projects are usually a good indicator how stable a rule is.

@bobisageek I'll happily review your code soon.

@bobisageek any update on this PR? Do you need assistance?

No updates, I just had the holidays and then work has sort of picked up, so I've had to shelve the side projects for a little while. Since I'm sure there will be a bunch of updates and large re-writes for the shared mutable state, I'll just close this and open a clean new one if/when I can get to the rewrite.


refactor(jest-environment)!: remove unnecessary defensive code

Summary
This PR removes unnecessary defensive code which was planned (mostly) to be removed in Jest 30.
Test plan
Green CI.

https://github.com/jestjs/jest/releases/tag/v30.0.0-alpha.4


Harmonize wording

What this PR does / why we need it:
This PR aims to unify the terminology we use in our documentation.
Which issue this PR fixes
This PR closes #609
Public facing documentation PR
N/A
Special notes for reviewer:
N/A
Add a screenshot or an example to illustrate the proposed solution:
N/A
Checklist:

[ ] Added relevant notes to WIP-CHANGELOG.md
[ ] Proper commit message prefix on all commits
[X] Updated the public facing documentation
Is this changeset backwards compatible for existing clusters? Applying:

[X] is completely transparent, will not impact the workload in any way.
[ ] requires running a migration script.
[ ] will create noticeable cluster degradation.
E.g. logs or metrics are not being collected or Kubernetes API server
will not be responding while upgrading.
[ ] requires draining and/or replacing nodes.
[ ] will change any APIs.
E.g. removes or changes any CK8S config options or Kubernetes APIs.
[ ] will break the cluster.
I.e. full cluster migration is required.

Chart checklist (pick exactly one):

[X] I upgraded no Chart.
[ ] I upgraded a Chart and determined that no migration steps are needed.
[ ] I upgraded a Chart and added migration steps.

Pipeline config
N/A

FYI, the term customer in the following figures is not changed to application developer:

docs/img/ck8s-c4model-level3-auth.drawio.svg
docs/img/ck8s-c4model-level3-logs.drawio.svg
docs/img/ck8s-c4model-level3-metrics.drawio.svg
docs/img/ck8s-c4model-level3.drawio.svg
docs/user-guide/img/user-guide.drawio.svg

And in all documents the term compliant kubernetes administrator didn't changed to platform administrator.

Thanks for the feedback @cristiklein !

Thanks @salehsedghpour !
Few comments:

FYI, the term customer in the following figures is not changed to application developer:

docs/img/ck8s-c4model-level3-auth.drawio.svg
docs/img/ck8s-c4model-level3-logs.drawio.svg
docs/img/ck8s-c4model-level3-metrics.drawio.svg
docs/img/ck8s-c4model-level3.drawio.svg
docs/user-guide/img/user-guide.drawio.svg

And in all documents the term compliant kubernetes administrator didn't changed to platform administrator.

[ ]  I'm a bit confused by the passive voice. Why didn't you make these changes? Was it because we didn't make it clear enough if these should be changed too? Or did you simply decide to leave these for a later PR?
[ ]  According to our glossary, we want to capitalize terms, e.g., Management Cluster, not management cluster. Can you update your PR for that?
[ ]  @lucianvlad This PR touches ADRs and arch diagrams, for which you are the owner. Looks okay, as far as I can tell, but please approve.

Regarding those images that I listed, the main reason that I didn't changed them was that it really didn't make sense. For instance, the last image already has the application developer and at the same time it also has the super user. To this end I decided to leave them for a future PR after some discussion!
I'll update the PR with Management Cluster.


How can I mock BlobServiceClient for unit tests when using dependency injection?

The documentation here shows the default constructor BlobServiceClient() with the description "Initializes a new instance of the BlobServiceClient class for mocking."
How can I mock a BlobServiceClient for unit testing? More precisely, I would like to provide fake blob streams (e.g. from MemoryStream) and fake BlobProperties for my unit tests.
Please add some documentation how to achieve that.
I've also cross-posted this issue here.

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

ID: d0e2a2da-cb07-a454-dbfa-7349007812a2
Version Independent ID: 2cbfee72-6851-6224-fd83-1819515926a9
Content: Dependency injection with the Azure SDK for .NET
Content Source: docs/azure/sdk/dependency-injection.md
Product: dotnet-azure
GitHub Login: @pakrym
Microsoft Alias: pakrym

@pakrym can you help with this question?

Duplicate of https://github.com/Azure/azure-sdk-for-net/issues/25836


Changed relative paths .csproj and pcc name in yml, updated gitignore

Most significant change was to Gemfire4.csproj, the relative paths were going too far up, they only needed to go up one on my machine to get to the bin. I am working on VmWare Fusion, but don't think this would make a difference on other machines.
Changed the name of the pcc service due to blog I am writing.
FolderProfile now reflecting recommended relative path bin\Debug\net461\win10-x64\publish
Git ignored Gemfire package as it must be purchased.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: everythingeverywhere sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks Ivan!


ParallelTestExecution with Sorted output and Tags sometimes skips tests

Hi,
This follows from https://github.com/maiflai/gradle-scalatest/issues/25.
import org.scalatest.tagobjects.{CPU, Network}
import org.scalatest.{FlatSpec, ParallelTestExecution}

class MySpec extends FlatSpec with ParallelTestExecution {
  it should "network" taggedAs Network in {
    fail("doesn't")
  }
  it should "cpu" taggedAs CPU in {
    fail("doesn't")
  }
}

java org.scalatest.tools.Runner -oF -PS4 -R build/classes/test -n org.scalatest.tags.CPU

Discovery starting.
Discovery completed in 94 milliseconds.
Run starting. Expected test count is: 1
Run completed in 202 milliseconds.
Total number of tests run: 0
Suites: completed 1, aborted 0
Tests: succeeded 0, failed 0, canceled 0, ignored 0, pending 0
No tests were executed.

It correctly discovers that one test should be run, but then appears not to run it. As you can see from the test code, running the test should fail.
Changing -PS4 to -P4 always runs the expected test and fails the build.
Removing -n org.scalatest.tags.CPU detects and runs two tests. Both fail.
Replacing -n org.scalatest.tags.CPU with -l org.scalatest.tags.CPU should run the other test, but actually gives the same No tests were executed.
I've tried picking through Runner.scala but got somewhat lost in the middle. Is this a recognised issue that has a known workaround please?
Thanks,
Stu

We're hitting this problem. When we use -l to exclude our slow tests, it skips running tests that aren't marked slow when -PS is used. If just -P is used, all tests run. This is a problem in 3.1.1, 3.1.2, and 3.2.0. For us, we have 32 "fast" tests in one of our projects and get this output:
Discovery starting. Discovery completed in 3 seconds, 483 milliseconds. Run starting. Expected test count is: 32 Run completed in 4 seconds, 518 milliseconds. Total number of tests run: 17 Suites: completed 9, aborted 0 Tests: succeeded 17, failed 0, canceled 0, ignored 0, pending 0
Only 17 run, though 32 were actually expected.
Simply changing from -PS12 to -P12 we get:
Discovery starting. Discovery completed in 3 seconds, 524 milliseconds. Run starting. Expected test count is: 32 Run completed in 4 seconds, 507 milliseconds. Total number of tests run: 32 Suites: completed 16, aborted 0 Tests: succeeded 32, failed 0, canceled 0, ignored 1, pending 0
We're stuck with -PS, so any help would be appreciated greatly. Thanks!

Adding -Dorg.scalatest.tools.Runner.forever=true seems to trigger the example test above to actually run and fail (infinitely).
I'll keep digging.

Thanks for looking @maiflai. FWIW, I added a 5-second sleep to one of our tests that isn't running on my machine and then all of the tests got executed. However, when I instead added a 5-second sleep to one of the tests that were already running (one of the 17), then no change in the number of tests executed (and it took 5 seconds longer). It doesn't seem to be dependent on the test itself, as a co-worker has a different set of the 32 tests that get executed than mine (and it is only 10).

@maiflai @jeksmith @bvenners I submitted the following PR attempting to fix this:
https://github.com/scalatest/scalatest/pull/1838

that's great, thanks very much.
the patch appearedfixed the issue when I applied it locally.

@cheeseng Unfortunately the patch didn't work for my case. Perhaps it is different when using -l alone instead of -n alone? I verified I am using your change. I'm not sure how to boil down my suite of tests to a small example that exposes the problem. Any ideas of what I should look for in naming or otherwise?
Thanks for your help with this!

@jeksmith I afraid I am not sure how I can help you in your case, a small example project to reproduce the problem will be really helpful, the above fix was identified with @maiflai 's example.  It could be a separate problem for your case, and it will be really hard to tackle your problem without a consistent way to reproduce it, so hopefully you can somehow get a boil down version that reproduce your problem and I'll be happy to look into it.  :)

@cheeseng Ok, I found the test class that causes trouble for the PR. It is an AsyncFunSpec. I've boiled it down to the following. When running with @maiflai 's class and excluding Slow, it doesn't run any test about 50% of the time.
import org.scalatest.funspec.AsyncFunSpec
import org.scalatest.tagobjects.Slow
import scala.concurrent.Future

class MyAsyncSpec extends AsyncFunSpec {
  describe("when run in parallel with other tests") {
    it("should not affect their execution", Slow) {
      Future { assert(false) }
    }
  }
}

Use -l  org.scalatest.tags.Slow (and not -n).
For my actual test, it doesn't work 100% of the time. For this test, like I said, it doesn't work about 50% of the time. By doesn't work, I mean when you run it with the MySpec class above, the CPU and Network tests are not executed as they should be since they are NOT Slow tests.

I think that AsyncTestSuite has special behaviour for two mixins (org.scalatest.AsyncTestSuite#parallelAsyncTestExecution)?
class MyAsyncSpec extends AsyncFunSpec with ParallelTestExecution seems to work reliably.
class MyAsyncSpec extends AsyncFunSpec with RandomTestOrder does not.

@maiflai @jeksmith Fyi @johnduffell has a more complete fix here for 3.2 and 3.0:
https://github.com/scalatest/scalatest/pull/1842
https://github.com/scalatest/scalatest/pull/1841
I have pushed similar changes to my current PR for 3.1.x:
https://github.com/scalatest/scalatest/pull/1838
Do you mind to test again and see if the changes fix your problem now?
Thanks.

Yes, that seems to work, and I agree those are the uses of that constructor in 3.2
Thanks very much!
Stu

@cheeseng Excellent! Works in my test environment and with my dev project. All tests are executed as expected for both '-n' and '-l' cases. Many thanks!!!!
-John

@cheeseng Hi. Any chance you know when the fix may get into a Scalatest release? Thanks.


Node ids of dependency graph may not be unique

The node identifiers in the dependency graph are created from the action's name and actual parameters.
Therefore, if there are multiple instances of the same action with the same parameters in the plan those would appear only once in the dependency graph.

An attempt was made in #8 to handle this problem. Instead of separate attributes, I have tried to compile the action instance into executable action representation. Eventually, each node is expected to have its own representation.
But the problem in dependency graph may be due to the node name produced when translating plans.

But the problem in dependency graph may be due to the node name produced when translating plans.

Yes, indeed I think the problem is the node name. We should add a unique id, .e.g, the position  of the action in the plan.


Feat/industries db

update seed files to seed organizations, industries, and organization industries.
add api route for api/industries
Directory component to fetch industries list from db
dbOperations to get industries list, organization Industry mappings (1871 has Tech and Venture Capital), and massage organizations to add industry data.

Just starting to review this but this stood out to me first. We should have a single JS file that seeds the entire database and it can call these other seed functions for us.
I'll take a further look at this one and #29 sometime this weekend. Everything looks pretty straightforward, but I want to run things locally to really kick the tires.

@rogeruiz pushed up some changes. Please take a look and lemme know if it looks good to you! Should be ready for your feature.

🙏🏼🙏🏼 🚀
Jorge Viramontes
jorgeviramontes.com http://www.jorgeviramontes.com/
On Sat, Nov 9, 2024 at 11:54 AM Roger Steve Ruiz @.***>
wrote:

@.**** commented on this pull request.
In drizzle/schema.ts
https://github.com/Alacran-Studio/lpdd/pull/30#discussion_r1835479494:

photos: text("photos").default("[]"),

videos: text("videos").default("[]"),

Sure thing. I do still think we’ll need to revisit this to store metadata
and not just the strings. But I’ll write up the ticket for that and we can
tackle it sometime in the future after 1.0.
—
Reply to this email directly, view it on GitHub
https://github.com/Alacran-Studio/lpdd/pull/30#discussion_r1835479494,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAS4NRYLFXU3XBMEW7HNRWTZ7ZD5HAVCNFSM6AAAAABQ27HRICVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDIMRVGUZDONBXGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Code for script.js

This is the code for script.js

@YashAryanTheCoder Any more updates?

No this was final. Kindly merge my pull request

Thank you @Astrodevil


Asymetrical Subject - Feature suggestion

I am working on a Redis Pub/Sub implementation at my job, where instead of calling SUBSCRIBE, UNSUBSCRIBE, and PUBLISH directly, this will be handled using a Subject.
This is a rough implementation:

class RedisSubjects {

    Subject<RedisValue> GetChannel(RedisChannel channel) {
        var subject = new Subject<RedisValue>();
        ISubscriber subscriber = redis.GetSubscriber();

        // When a message is received on the channel, alert subscribers to the subject
        subscriber.Subscribe(channel, (redisChannel, redisValue)=>{
            subject.OnNext(redisValue);
        });

        // ...... In the real implementation, UNSUBSCRIBE is handled by Dispose();

        // This is the tricky part:
        subscription.Subscribe((value)=>{
              // This implementation will cause an endless loop,
              // as the message published to Redis, will eventually come back
              // through to this code path.
              subscriber.Publish(channel, value);
        });
    }

}

What would be ideal, is to have a single Subject, which circumvents this looping problem. The ideal design would be to have two Subjects under the hood, which appear as a single Subject to the outside world. When the outside world calls OnNext on this Asymetrical subject, which internal Subject receives the message, would be able to be configured.
Subject A (Is a subject in its own right)
===#====

Subject B (Is a subject in its own right)
=#====#=

// External callers see only:

AsymetricalSubject
=#=#==#=

// The creator of the Asymetrical Subject, configures Subject A to be the external "inlet"

// This code is called:
AsymetricalSubject.OnNext(@)

// Results in:
Subject A
===#====@
Asymetrical Subject
=#=#==#=@

Would this sort of feature have any value to anyone else? Or am I approaching this problem poorly?

I think this is too peculiar for your case and can be achieved with existing Rx building blocks.


App goes to background

Bug
App stops (goes to backgroud) without exception or crash message.
Version Number of Plugin: 2.6.0
Device Tested On: Android 6.0.1
When I try to open more tha 10 images consequently with PickPhotoAsync, the Xamarin Android app goes to background without exception or message.
This is the code snippet.
     ` var imageFile = await CrossMedia.Current.PickPhotoAsync();
        if (imageFile == null)
        {
            return;
        }

        var pinImageDTO = new PinImageDTO()
        {
            MediaFile = imageFile,
            ImageSource = ImageSource.FromStream(() =>
            {
                var stream = imageFile.GetStream();
                return stream;
            }),
            Id = Guid.NewGuid().ToString()
        };`

Update to 2.6.2 or latest beta for enhance memory management

@jamesmontemagno I've already updated it to the latest beta and still not working. Do you have any other solutions?

Hi @jamesmontemagno  i am facing same problem can you please suggest ...


Cache return value of VendorAPI::SingleApplicationPresenter#as_json

Context
Multiple requests to GET /api/v1/applications will typically return JSON objects which haven't change much over time. This endpoint could be more performant with the use of some basic caching.

Changes proposed in this pull request
We can rely on ApplicationChoice#updated_at as an indication of change to an application so cache the output of SingleApplicationPresenter#as_json calls using a compound key containing this timestamp.

Guidance to review
I've arbitrarily passed expires_in: 30.minutes as a caching arg, should we make this longer?

Link to Trello card
https://trello.com/c/yzKDiTtI/4037-spike-investigate-performance-issues-with-get-applications-endpoint

Things to check

[x] This code does not rely on migrations in the same Pull Request
[x] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[x] API release notes have been updated if necessary
[x] Required environment variables have been updated added to the Azure KeyVault

@cwrw We now configure production envs to use RedisCacheStore https://github.com/DFE-Digital/apply-for-teacher-training/blob/main/config/environments/production.rb#L24


Update label-automerge.yml

🗣 Description

Fix incorrect permissions for auto-merge labeler workflow.
💭 Motivation and context

It was broken by the hardening.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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 15.141%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
115

Relevant Lines:
609

💛  - Coveralls


Uninstalling toltec, ddvk package crashed and soft bricked RM2

Describe the issue
I uninstalled Toltec using "toltecctl uninstall" and that caused my RM2 to be stuck on the is starting screen.
To Reproduce
Steps to reproduce the behaviour:

ssh into device
run  toltecctl uninstall
running the command will disconnect from ssh
rm2 is stuck on is starting screen

Expected behaviour
Be able to start my device and use it in the pre-installed way
Screenshots
If applicable, add screenshots to help explain your problem.
Device information (please complete the following information):

Device: reMarkable 2
OS version: <IP_ADDRESS>9

Additional context
Eeems was able to help me fix this issue and said that ddvk must have crashed while reverting. running "ls -l /usr/bin/xochitl" gave me this output "-rwxr-xr-x    1 root     root             0 Jan 16 14:47 /usr/bin/xochitl" and running this command "file /usr/bin/xochitl" gave me "/usr/bin/xochitl: empty".

Another user had reported that they had the device crash while uninstalling, and it crashed at removing libatomic.

We had another user have the device crash part way through an update/upgrade and then lost SSH access. I have copies of the root partitions that we can investigate to see what happened.


added flavor keys

addressed #73 by making icecream flavor assignment a separate field in the json file.

I cleaned up a little bit, and removed an unused variable. Now I just have to remove the seed assignment flavor key from the preprocessing config file


remove useless doc

This doc is not needed anymore, so remove it.
Fix #944

@reasonerjt  PTAL.  Thanks!

Coverage remained the same at 50.256% when pulling 714543238defa1782941ab3d1f10dc0b58fce9cf on supereagle:dev into aea99d49b496a466fc92709f43cb25d4bf1e143d on vmware:dev.

Thanks!


printing

hi,
i have this question. i tried to print in my new trueos. it works very well. but, i do have virtualbox now and i would like to print also from windows7 from virtualbox. can you help me how to do it? when i install the printer i checked "share this printer". and than i cannot find it or install this printer in windows in virtualbox. is here way to make it works?
thank you

This would be a problem with your VirtualBox configuration rather than Lumina.
If the printer is directly attached to the system (with a USB cable for instance), then you will probably need to setup the USB device passthrough for the virtual machine to be able to "see" it.
If it is a network printer, then you will need to make sure that your virtual machine can properly access the local network (network device passthrough?).