[WIP] Fix staging configuration for Apple Sign-In

Details
The redirect URI for Apple Sign-In was not correctly set in staging. This uses NEW_EXPENSIFY_URL env value via CONFIG, which is how the domain is set in the staging environment.
Fixed Issues

$ https://github.com/Expensify/App/issues/23288
PROPOSAL: https://github.com/Expensify/App/issues/23288#issuecomment-1644262505
Tests

Add a NEW_EXPENSIFY_URL value to a local .env file
Add a console.log to inspect the redirect URI value at https://github.com/Expensify/App/pull/23290/files#diff-0e1ba41abd8481f21d5431f400cc5ebbff622599be5d757ee5f78820174759e6R43 when the app loads, ensure it matches <YOUR DOMAIN>/appleauth

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

Offline tests

n/a
QA Steps

This fixes issues with the Apple Sign-In, no new 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 / Chrome
[x] iOS / native
[x] iOS / 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 a new component is created I verified that:

[x] A similar component doesn't exist in the codebase
[x] All props are defined accurately and each prop has a /** comment above it */
[x] The file is named correctly
[x] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[x] The only data being stored in the state is data necessary for rendering and nothing else
[x] If we are not using the full Onyx data that we loaded, I've added the proper selector in order to ensure the component only re-renders when the data it is using changes
[x] 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)
[x] 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)
[x] All JSX used for rendering exists in the render method
[x] 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

[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(themeColors.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 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.
[x] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

LGTM, I wonder if we need to update the variable also here for Android?

Not for Android. For Android, the only requirement is that it matches a value set in the Apple developer console for the given Service ID.
The redirect URI isn't actually used on Android, as there's no domain name there to compare it to, so there's no point of failure. (It works by the library using a webview to intercept the POST that Apple makes in the redirect flow).

Ah yeah, good catch, that's expecting a full route. Maybe the full URI should go in CONFIG 🤔 bit unusual, but it can't go in CONST because that would be a reference cycle

Alternatively, I think we can move APPLE_SIGN_IN_REDIRECT_ROUTE to ROUTES to avoid the reference cycle?

Should be fixed for Android as well, but building and testing now.

Alternatively, I think we can move APPLE_SIGN_IN_REDIRECT_ROUTE to ROUTES to avoid the reference cycle?

We can if it feels better, but I think it's valuable to keep the two pieces of Apple Sign-In config (service ID and redirect URI) together since they're always used together

Alright, I tested Android and it's working, so I think we're good to go on this

Given there was another regression, we're going to revert and incorporate this change into a new PR.


add lakeland community college

@ProgrammingPete I have to close this request without merging, because you requested to add a non-existent domain to this repository: Host mail.lakelandc.edu not found: 3(NXDOMAIN) Please ensure that you are familiar with this repository rules located at the bottom of this page and submit a new request with the correct information. Thank you for your understanding!


Add stable release policy

Description
This is the proposed stable release policy
closes: #671

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

[x] Targeted PR against correct branch (see CONTRIBUTING.md)
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[x] Code follows the module structure standards.
[x] Wrote unit and integration tests
[x] Updated relevant documentation (docs/) or specification (x/<module>/spec/)
[x] Added relevant godoc comments.
[x] Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
[x] Re-reviewed Files changed in the Github PR explorer
[x] Review Codecov Report in the comment section below once CI passes

Should we also explicitly say that we will not make patch releases that exclusively bump up the Cosmos SDK or Tendermint?

I guess it is just unclear when we make a patch release, not what is in the patch release. Maybe it is best to just state it is up to our discretion? I think it is impossible to predict an appropriate cadence for patch releases

And if we have a fix to release, then we can bump the versions of those 2 dependencies as well (if there's a new version). Do you have any idea if not making releases with the newer versions of the dependencies could have an impact on the developers? Like a chain moving to 0.45 but still using ibc-go v1.2.x with 0.44.

I'm fairly certain chains/apps can overwrite the SDK version we use with a repalace in the go.mod

I guess it is just unclear when we make a patch release, not what is in the patch release. Maybe it is best to just state it is up to our discretion? I think it is impossible to predict an appropriate cadence for patch releases

For me it would be fine if we say that we would create patch releases when there's a new version of the SDK or Tendermint, just maybe to give some reassurance to the developers (assuming this is something they value). Otherwise, stating that it's up to our discretion is also fine.

For me it would be fine if we say that we would create patch releases when there's a new version of the SDK or Tendermint, just maybe to give some reassurance to the developers (assuming this is something they value). Otherwise, stating that it's up to our discretion is also fine.

Most SDK and Tendermint patch releases should fall under the category of allowed pr's for stable patch-releases. I think it is probably fine to leave as is?

@crodriguezvega feel free to push any changes directly


<mask> area doesn't get expanded beyond object's bounding box

It appears <mask> area doesn't get expanded beyond the bounding box of the object it is applied to:

mask-0.svg, mask-1.svg, mask-2.svg

It could "shrink" inside the object's bounding box, though.  The most apparent effect is that a stroke that goes beyond the object's bounding box gets clipped from view.
mask-0.svg
    <mask id="aperture" maskUnits="userSpaceOnUse"
        x="0" y="0" width="500" height="500">

Actual
Expected

mask-1.svg
    <mask id="aperture" maskUnits="userSpaceOnUse"
        x="50" y="50" width="450" height="450">

Actual
Expected

mask-2.svg
    <mask id="aperture" maskUnits="userSpaceOnUse"
        x="60" y="60" width="440" height="440">

Actual
Expected

Initially found in https://github.com/weisJ/jsvg/issues/64#issuecomment-1974806550

This should be fixed in the latest snapshot

Trying out current 1.5.0-SNAPSHOT (gradlew --refresh-dependencies → 1.5.0-20240304.002615-19) – the outer stroke is now fully visible but a different defect appears.  Looks like the overall mask is scaled (enlarged):

mask-0
mask-1
mask-2

Notice the circular hole is bigger than the debug overlay that uses the same path as for the mask.

This is related to #66. I have a fix locally, will push once #67 is resolved. I noticed that the library I am using to compare images in tests doesn’t handle transparent pixels and thus multiple tests have failed silently for the past few versions. I need to catch up with those before work on subpixel alignment can be continued.

Just tried with a current 1.5.0-SNAPSHOT – it now (currently) appears just right.


Quivers do not go into armory cabinet

When automating storage for a mob farm, quivers, despite being non-stackable, are not accepted into the cabinet. (from supplementaries)
also Armory cabinet doesnt link to controller but that may be as intended?
functionalstorage-1.18.2-1.0.7.jar

Quivers also doesnt render in normal drawers


ES updates

add nullish coallescing (??) and exponentiation (**) binary_ops by default (fixes #268)
add logical assignment operators ||= &&= ??= (es2021)
add license file to build output (fixes #267)
add docs for standard JS literals (fixes #255)
remove node 16, add node 22 to test builds
(also upgraded eslint rules and docco to pass tests)

NOTE: will trigger a minor release ... I debated if the new binary ops should trigger a major or not, but let me know if you'd like me to change the commit message

The Exponentiation ** operator?
Yeah, I'm in doubt as well, technically, it could be alternate some logic for a very low percentage of users, which would advise for major. But I'm fine with minor as well.


Single Cell RNA-seq reveals ectopic and aberrant lung resident cell populations in Idiopathic Pulmonary Fibrosis

Project short name:
lungPopulationsIPF
Primary Wrangler:
All wranglers.
Metadata lead: Irene
Data lead: Enrique
Secondary Wrangler:

Associated files

Google Drive: https://drive.google.com/drive/folders/1rYux17a7JCPbnajxGaGlAIylTKkrG2qm?usp=sharing
Ingest: https://contribute.data.humancellatlas.org/projects/detail?uuid=c16a754f-5da3-46ed-8c1e-6426af2ef625

Published study links

Paper: https://www.science.org/doi/10.1126/sciadv.aba1983

Accessioned data: https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSE136831

Key Events

[x] Convert published metadata to HCA spreadsheet
[x] Manually curate dataset to meet HCA metadata standard
[x] Collect any matrix and cell-type annotation files
[x] Upload sheet to validate metadata
[x] Check linking using ingest graph validator
[x] Transfer raw files to ingest to validate data files
[x] Ask the Secondary Wrangler for an end-to-end review of the project. Ask the Expertise Wrangler to review specific tabs if needed
[x] Submit dataset to Production
[ ] Complete the Export SOP
[ ] Convert project data to SCEA format following the SCEA conversion SOP if appropriate

We started wrangling this dataset as part of the "Wrangler workshop - remove obstacles in the flow"

@ipediez to finish wrangling the metadata and inform the secondary wrangler about which fields/tabs were not reviewed during the workshop
@ESapenaVentura to wrangle the available data
@idazucchi or @Wkt8 to secondary wrangle the information that wasn't filled in during the workshop

hca-util area: eaf44850-d35f-4ab0-a53e-f81c5f236289

@Wkt8 to secondary review this.

Looks great to me! Fixed a small typo with contributor names in Ingest. Apart from that, it looks great!

R16 ReExport Successful

@idazucchi to look today
@ESapenaVentura: LGTM

After Dave's request in #1270 I am re-opening the current ticket to add fastq files that are now available in GSE136831.
hca-util upload area already contains the analysis files, and fastqs have been uploaded there as well.
Discussing with @ESapenaVentura how to proceed with the update, while keeping the same uuids for all other entities.
I downloaded the spreadsheet from ingest's submission, and added the Sequence file tab, and wrangled them. I filled the uuids for the references of the seq file tab as well (cell suspension, library preparation protocol, sequencing protocol).
spreadsheet \w seq files here: 1da128e6-c525-42c0-be81-384998f93781_20240620-155943.xlsx

Graph valid & exporting

Verified in browser.


kube-up.sh support scaleout

What type of PR is this?

/kind feature

What this PR does / why we need it:
kube-up.sh support scale-out cluster
1TP1RP verified
2TP2RP verified
Which issue(s) this PR fixes:

Fixes #1036
Special notes for your reviewer:
Example commands to start Kube-up:
export SCALEOUT_CLUSTER=true NUM_NODES=2 SCALEOUT_TP_COUNT=1 SCALEOUT_RP_COUNT=1 RUN_PREFIX=example-111621-1x1x100
export MASTER_DISK_SIZE=500GB MASTER_ROOT_DISK_SIZE=500GB KUBE_GCE_ZONE=us-west2-b MASTER_SIZE=n1-highmem-32 NODE_SIZE=n1-highmem-16 NODE_DISK_SIZE=500GB GOPATH=$HOME/go KUBE_GCE_ENABLE_IP_ALIASES=true KUBE_GCE_PRIVATE_CLUSTER=true CREATE_CUSTOM_NETWORK=true KUBE_GCE_INSTANCE_PREFIX=${RUN_PREFIX} KUBE_GCE_NETWORK=${RUN_PREFIX} ENABLE_KCM_LEADER_ELECT=false ENABLE_SCHEDULER_LEADER_ELECT=false ETCD_QUOTA_BACKEND_BYTES=8589934592 SHARE_PARTITIONSERVER=false LOGROTATE_FILES_MAX_COUNT=200 LOGROTATE_MAX_SIZE=200M KUBE_ENABLE_APISERVER_INSECURE_PORT=true KUBE_ENABLE_PROMETHEUS_DEBUG=true KUBE_ENABLE_PPROF_DEBUG=true TEST_CLUSTER_LOG_LEVEL=--v=2 HOLLOW_KUBELET_TEST_LOG_LEVEL=--v=2 GCE_REGION=us-west2-b
./cluster/kube-up.sh

Verify scale out cluster:
kubectl --kubeconfig=/home/sonyali/go/src/k8s.io/arktos/cluster/kubeconfig-proxy get nodes
kubectl --kubeconfig=/home/sonyali/go/src/k8s.io/arktos/cluster/kubeconfig.rp-1 get nodes
kubectl --kubeconfig=/home/sonyali/go/src/k8s.io/arktos/cluster/kubeconfig.tp-1 get nodes

Does this PR introduce a user-facing change?:

have we started a kubemark test env with this approach ? for example a 100 node kubemark perf run? the kubemark functionality should be still there.

have we started a kubemark test env with this approach ? for example a 100 node kubemark perf run? the kubemark functionality should be still there.

Not yet, as we talked in yesterday's meeting, this version is focus on kube-up.sh to unblock mizar integration.


[BUG] <any_changed doesn't capture changes due to renaming files>

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug?
I would expect any_changed to be true when there is a renamed file. It looks like any changed doesn't take renamed files into account.
To Reproduce
Rename a file in the specified directory and then check the any_changed flag.

For the specific case when I came across this, the file was renamed (moved from a directory outside the one specified into the specified AutomatedTests directory) but also had additional changes. It only showed up in the renamed files list.
What OS are you seeing the problem on?
ubuntu-latest or ubuntu-20.04
Expected behavior?
If there is anything listed for "All changed files" that the any_changed flag would be true.
Relevant log output
Checking for file changes: "AutomatedTests"...
  Added files:
  Copied files:
  Deleted files:
  Modified files:
  Renamed files: AutomatedTests/DownloadDatabaseTestCase.swift
  Type Changed files:
  Unmerged files:
  Unknown files:
  All changed files: AutomatedTests/DownloadDatabaseTestCase.swift
  All modified files:
  Input files: AutomatedTests
  Matching modified files:

Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

@linnea-foreflight This should be resolved in the latest release


[$1000] Inconsistent "To" label for participant selector in case of split bill and send/request money.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Click on the Fab button in the LHN
Click on the split bill button.
Enter the amount and click next.
Notice that before the text input, there is a label called "To" at the top.
Close this modal.
Go back to LHN and click on the Fab again
Click on either send money or request money button.
Enter the amount and click next.
Notice that before the text input, there is no label like "To".

Expected Result:
Remove the To label from all areas of the UI. The behavior should be consistent.
Actual Result:
The To label is shown in participant selection component in case of "Split bill" but not in case of "Send/Request money".
Workaround:
Can the user still use Expensify without this being fixed? Have you informed them of the workaround?
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android / native
[x] Android / Chrome
[x] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] MacOS / Desktop

Version Number: 1.3.16-3
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/43996225/d74f6563-6676-404b-9baa-e76c9604f4da
https://github.com/Expensify/App/assets/43996225/8e7a916f-3860-453e-bbe9-2f84168c4f3e
Expensify/Expensify Issue URL:
Issue reported by: @Nikhil-Vats
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1684262848278309
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~010aadb10658e3788e
Upwork Job ID:<PHONE_NUMBER>238852608
Last Price Increase: 2023-05-30

Proposal by @Nikhil-Vats
Proposal
Please re-state the problem that we are trying to solve in this issue.
Inconsistent label for participant selector in case of split bill and send/request money.
What is the root cause of that problem?
In MoneyRequestParticipantsPage, if the prop hasMultipleParticipants is true then we render MoneyRequestParticipantsSplitSelector (Split bill) otherwise we render MoneyRequestParticipantsSelector (Send/Request money).
The MoneyRequestParticipantsSplitSelector component uses Text for showing the label "To" before OptionSelector -
https://github.com/Expensify/App/blob/05f5b06e37dafdeff5a86441c615557a6e735c3c/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSplitSelector.js#L215-L218
However, there is no use of Text in MoneyRequestParticipantsSelector, it directly returns OptionSelector -
https://github.com/Expensify/App/blob/05f5b06e37dafdeff5a86441c615557a6e735c3c/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSelector.js#L156-L159
What changes do you think we should make in order to solve the problem?
We should use View as a wrapper in MoneyRequestParticipantsSelector which is shown in case of Send/Request money and use Text to show the correct label for this case. This will make the behaviour consistent across all IOU request types (split, send, request).
What alternative solutions did you explore? (Optional)
NA

@kavimuru Thanks for posting my proposal. I would like to point out that this is a discrepancy on other pages/modals also -
Without label -

NewChatPage (Click on FAB then click on New Chat)
SearchPage (Click on the search icon in the header in LHN)
YearPickerPage (Go to settings, then your profile, click on personal details, Date of birth and then year)
IOUCurrencySelection (Change currency in any type of IOU request)
MoneyRequestParticipantsSelector (The one this issue is regarding - Send/Request money)
TimezoneSelectPage (Settings > Profile > Timezone)
TaskAssigneeSelectorModal (Click on FAB then assign task, enter a title and click next and click assignee)
TaskShareDestinationSelectorModal (Click on FAB then assign task, enter a title and click next and click share somewhere)
WorkspaceInvitePage (Settings > Workspaces > Any workspace > Manage members > Invite)

With label -

MoneyRequestParticipantsSplitSelector (The one mentioned in the issue - Split bill) - Shows a label "To".
PronounsPage (Go to settings then profile) - It shows not a label but a description - "Your pronouns are shown on your profile.".

Now, some of the components without label don't need a label such as SearchPage, YearPickerPage, IOUCurrencySelection, etc. but between similar pages like Request Money, Send Money, Split bill, etc. and also the Task assignee, share destination modals it would be nice to have consistency.
We can have labels for these components as I have mentioned in the solution section of my proposal or we can remove labels to keep consistency between similar components.

I agree this is inconsistent and worth fixing.

Good question, I am not sure yet. I want to figure out when we added the To field and the intentions behind adding it. Then it'll be easier to decide this more clearly!

We need to find a consensus on the thread in slack. Then we can re-apply Help Wanted and proceed. I could see us removing the To field but I'm just 1 vote here. There's a chance that we added it for good reason and keep it, perhaps even adding it to all the UI components where you select a person (e.g. from the FAB flows)

No updates, waiting on Shawn to come back to get his input

We discussed further and @shawnborton weighed in. We agree that it's wise to kill the To: field in all areas of the UI.

Updated the GH body, expected result, and title to be inline with our expectations.
@Nikhil-Vats since you already kicked off a proposal, just wanna nudge you in case you need to adjust/adapt that proposal to fit the latest agreed-upon plan.

Proposal
Please re-state the problem that we are trying to solve in this issue.
Inconsistent "To" label for participant selector in case of split bill and send/request money. The label "To" in split bill participant selector is unnecessary since the UI is self explanatory.
What is the root cause of that problem?
In MoneyRequestParticipantsPage, if the prop hasMultipleParticipants is true then we render MoneyRequestParticipantsSplitSelector (Split bill) otherwise we render MoneyRequestParticipantsSelector (Send/Request money).
The MoneyRequestParticipantsSplitSelector component uses Text for showing the label "To" before OptionSelector -
https://github.com/Expensify/App/blob/05f5b06e37dafdeff5a86441c615557a6e735c3c/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSplitSelector.js#L215-L218
However, these is no use of Text in MoneyRequestParticipantsSelector, it directly returns OptionSelector -
https://github.com/Expensify/App/blob/05f5b06e37dafdeff5a86441c615557a6e735c3c/src/pages/iou/steps/MoneyRequstParticipantsPage/MoneyRequestParticipantsSelector.js#L156-L159
What changes do you think we should make in order to solve the problem?
We should remove line 217 (see below) from MoneyRequestParticipantsSplitSelector to remove the To label since the UI is self explanatory.
<Text style={[styles.textLabelSupporting, styles.pt3, styles.ph5]}>{this.props.translate('common.to')}</Text>

We cannot remove the view wrapper because it is used for safe area padding (near the next button).

See screenshot.

### What alternative solutions did you explore? (Optional)
NA

Thanks @aimane-chnaif

Thanks for assigning me this issue. I have applied to the job on Upwork and I will raise the PR within a few hours.

Hey @aimane-chnaif @michaelhaxhiu I have raised the PR. You can review and test it. Some of the platform videos (test proofs) are pending, I will add them by EOD today.

Hey all 👋, I have added the videos for all platforms now. All wrapped up from my end. You can review and test.

Invited yall to the job. We'll sort out final payout amounts after 7 days passes.
So far though, the 50% bonus is obviously in play

I agree w/ that take

all paid. thanks to all! 😎 till next time, folks.


Add simpler examples

Current examples have many options, including which env to solve. That might be helpful to tackle a new environment, where you will have to tune hyper parameters, but as examples to new users, I feel they are too complicated. I think it is better to add simpler examples that only solves a single predefined env.

In particular, do you have a good set of parameters for using ACER in ALE?
I've been running your example train_acer_ale.py with the default options, but it only gives me reduced sample efficiency compared to A3C (while taking noticeably longer).
Could be I've just been using the wrong games. Wang, et. al. unhelpfully only give an aggregate graph which doesn't give any information about, in which specific environments ACER is supposed to have improved sample efficiency.

Interesting. Which game did you try? When I tuned train_acer_ale.py, I found it is much more sample-efficient than A3C on Breakout with the default parameters.

@muupan Breakout, Beam Rider, Pong and Qbert. I guess if you did have better efficiency with Breakout, there must be something wrong with my setup - though I still get good results from A3C.


Any plans to upgrade to Angular 13+?

Do you have plans to upgrade to Angular 13+?

Fixed in 3.0.0


Make HathiTrust button admin configurable

The current HathiTrust behavior is configured in app properties.
The next step is enabling admins to manage the configuration through the UI.

After reviewing this, it turns out we were able to implement the Hathi Trust button purely in client side javascript within libcat and there's already configuration properties available there that can be modified by the appropriate admins, so there's no further work to be done on this.


Unable to run leap after manual DLL install

I used the manual install method (i.e. copying the libleapct.dll file instead of compiling the source) as instructed in the manual_install.py. I am unable to run any of the demo scripts after manual installation. I have confirmed that the files, leapctype.py, leaptorch.py, leap_filter_sequence.py, leap_preprocessing_algorithms.py, and libleapct.dll are properly copied to my Python's virtual environment path after running the  manual_install.py script:
System info:
Windows 10 x64
Python 3.11.9
Below are my steps to repeat:
PS C:\test_LEAP_issue\LEAP-1.14> python .\manual_install.py
Copying LEAP-CT files to: C:\temp_python_venv\venv_test_leap\Lib\site-packages

PS C:\test_LEAP_issue\LEAP-1.14> ls "C:\temp_python_venv\venv_test_leap\Lib\site-packages"

    Directory: C:\temp_python_venv\venv_test_leap\Lib\site-packages

Mode                 LastWriteTime         Length Name
----                 -------------         ------ ----
d-----         6/17/2024  10:34 AM                pip
d-----         6/17/2024  10:32 AM                pip-24.0.dist-info
d-----         6/17/2024  10:32 AM                pkg_resources
d-----         6/17/2024  10:32 AM                wheel
d-----         6/17/2024  10:32 AM                wheel-0.43.0.dist-info
d-----         6/17/2024  10:33 AM                _distutils_hack
d-----         6/17/2024  10:33 AM                __pycache__
-a----         6/17/2024  10:39 AM         298374 leapctype.py
-a----         6/17/2024  10:39 AM          20989 leaptorch.py
-a----         6/17/2024  10:39 AM          28282 leap_filter_sequence.py
-a----         6/17/2024  10:39 AM          26081 leap_preprocessing_algorithms.py
-a----         6/17/2024  10:39 AM        9271808 libleapct.dll
-a----         6/17/2024  10:32 AM              0 pip-24.0.virtualenv
-a----         6/17/2024  10:32 AM              0 setuptools-69.5.1.virtualenv
-a----         6/17/2024  10:32 AM             18 _virtualenv.pth
-a----         6/17/2024  10:32 AM           4546 _virtualenv.py

PS C:\test_LEAP_issue\LEAP-1.14> pip list
Package    Version
---------- -------
pip        24.0
setuptools 69.5.1
wheel      0.43.0

PS C:\test_LEAP_issue\LEAP-1.14\demo_leapctype> python .\d01_standard_geometries.py
  File "C:\temp_python_venv\venv_test_leap\Lib\site-packages\leapctype.py", line 124, in __init__
    self.libprojectors = windll.LoadLibrary(fullPath)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\username\AppData\Local\Programs\Python\Python311\Lib\ctypes\__init__.py", line 454, in LoadLibrary
    return self._dlltype(name)
           ^^^^^^^^^^^^^^^^^^^
  File "C:\Users\username\AppData\Local\Programs\Python\Python311\Lib\ctypes\__init__.py", line 376, in __init__
    self._handle = _dlopen(self._name, mode)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: Could not find module 'C:\temp_python_venv\venv_test_leap\Lib\site-packages\libleapct.dll' (or one of its dependencies). Try using the full path with constructor syntax.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "C:\test_LEAP_issue\LEAP-1.14\demo_leapctype\d01_standard_geometries.py", line 6, in <module>
    leapct = tomographicModels()
             ^^^^^^^^^^^^^^^^^^^
  File "C:\temp_python_venv\venv_test_leap\Lib\site-packages\leapctype.py", line 126, in __init__
    self.libprojectors = ctypes.CDLL(fullPath, winmode=0)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "C:\Users\username\AppData\Local\Programs\Python\Python311\Lib\ctypes\__init__.py", line 376, in __init__
    self._handle = _dlopen(self._name, mode)
                   ^^^^^^^^^^^^^^^^^^^^^^^^^
FileNotFoundError: Could not find module 'C:\temp_python_venv\venv_test_leap\Lib\site-packages\libleapct.dll' (or one of its dependencies). Try using the full path with constructor syntax.

Have you installed the CUDA toolkit?

Have you installed the CUDA toolkit?
No, my PC doesn't have NVIDA CPU. Doesn't the DLL support CPU only?

Ahh, yes, there is the problem.  The precompiled dll that I post requires the cuda libraries.  Can you compile the code yourself?  The instructions are here.
If you cannot compile this yourself, I could build you a library that does not require cuda, but you'll have to wait for me to do this until the weekend.  Compiling yourself is pretty easy.

I am not sure how to build without GPU. The instructions says:All you need to do here is swap the CMake file. Rename cpu_CMakeLists.txt to CMakeLists.txt. . But there is no cpu_CMakeLists.txt file in the repo.

It’s in the src folder.

Did you see the file in the src folder?  Were you able to compile?

Did you see the file in the src folder? Were you able to compile?

Yes, I see it in src folder. I haven’t built yet. Will report back once I try.

I was able to build without GPU and got the demo scripts to work. It would be great if the releases included pre-built DLL for use without GPU. Or the existing built DLL handled situations where a user does not have a GPU.

Glad it worked!
We are definitely interested in making the build process easier, but this type of thing is not really in my skill set.  I am hoping someone from the LEAP user community will step up and help us out with this.
I am going to close this issue, but feel free to open another one if you have further issues.


Difference between serial and parallel scf energy

Hi,
(Sorry for crossposting. I wasn't sure if it was better to post mpi4pyscf issues here for visibility)
I noticed a difference in the RHF energy when running with FFTDF in parallel. The difference is quite small (~0.6 mHa / Cell) but it only appears to happen for larger, or potentially just the gth-cc-XZVP basis sets for X > D. I've pasted the scf script below and attached the output files for both serial and parallel (srun -n 8) calculations.
I'm using mpi4pyscf master and pyscf v1.6.6. The difference only seems to appear for gth-cc-TZVP and gth-cc-QZVP, gth-cc-DZVP (which I think is the same as gth-DZVP) seems fine.
If it's any help the initial energy seems slightly different too.

#!/usr/bin/env python

import numpy
from functools import reduce
from pyscf.pbc import gto, scf
from pyscf import scf as mol_scf
from mpi4pyscf.pbc import df as mpidf

alat0 = 3.6

cell = gto.Cell()
cell.a = (numpy.ones((3,3))-numpy.eye(3))*alat0/2.0
cell.atom = (('C',0,0,0),('C',numpy.array([0.25,0.25,0.25])*alat0))
cell.basis = 'gth-cctzvp'
cell.pseudo = 'gth-pade'
cell.mesh = [33]*3
cell.rcut = 38
cell.verbose = 5
cell.build()

nk = [2,2,2]
kpts = cell.make_kpts(nk)

cutoff = 1e-14
mf = scf.KRHF(cell,kpts)
# mf = mol_scf.addons.remove_linear_dep_(mf,threshold=cutoff,lindep=cutoff)
mf.with_df = mpidf.FFTDF(cell,kpts)
mf.chkfile = 'scf.dump'
mf.conv_tol = 1e-9
ehf = mf.kernel()

serial.txt
mpi.txt

It is presumably something to do with the fact that the overlap matrix is
nearly singular (condition number = 10^11). With double precision, the
different roundoff due to multiple MPI processes will then be magnified by
this condition number to give a visible difference.
On Fri, Mar 13, 2020 at 6:37 PM Fionn Malone<EMAIL_ADDRESS>wrote:

Hi,
(Sorry for crossposting. I wasn't sure if it was better to post mpi4pyscf
issues here for visibility)
I noticed a difference in the RHF energy when running with FFTDF in
parallel. The difference is quite small (~0.6 mHa / Cell) but it only
appears to happen for larger, or potentially just the gth-cc-XZVP basis
sets for X > D. I've pasted the scf script below and attached the output
files for both serial and parallel (srun -n 8) calculations.
I'm using mpi4pyscf master and pyscf v1.6.6. The difference only seems to
appear for gth-cc-TZVP and gth-cc-QZVP, gth-cc-DZVP (which I think is the
same as gth-DZVP) seems fine.
If it's any help the initial energy seems slightly different too.
#!/usr/bin/env python
import numpyfrom functools import reducefrom pyscf.pbc import gto, scffrom pyscf import scf as mol_scffrom mpi4pyscf.pbc import df as mpidf
alat0 = 3.6
cell = gto.Cell()
cell.a = (numpy.ones((3,3))-numpy.eye(3))*alat0/2.0
cell.atom = (('C',0,0,0),('C',numpy.array([0.25,0.25,0.25])*alat0))
cell.basis = 'gth-cctzvp'
cell.pseudo = 'gth-pade'
cell.mesh = [33]*3
cell.rcut = 38
cell.verbose = 5
cell.build()
nk = [2,2,2]
kpts = cell.make_kpts(nk)
cutoff = 1e-14
mf = scf.KRHF(cell,kpts)# mf = mol_scf.addons.remove_linear_dep_(mf,threshold=cutoff,lindep=cutoff)
mf.with_df = mpidf.FFTDF(cell,kpts)
mf.chkfile = 'scf.dump'
mf.conv_tol = 1e-9
ehf = mf.kernel()
serial.txt https://github.com/pyscf/pyscf/files/4332165/serial.txt
mpi.txt https://github.com/pyscf/pyscf/files/4332164/mpi.txt
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pyscf/pyscf/issues/557, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN5NRDSI7OJZWI3P5AR5DDRHLNUBANCNFSM4LH24XYQ
.

Thanks for the hint. I'll try dropping smaller exponents to see if it reduces the magnitude of the error. It should also get worse with increasing MPI process count presumably.

Some settings in cutoff and threshold might be changed during the development stage from 1.6 to 1.7. I just updated the mpi4pyscf library to sync to the latest pyscf-1.7. The latest version of mpi4pyscf should be able to give consistent results.

Thanks, I updated to the newest version of mip4pyscf and pyscf. The differences still persist. What's confusing is that the overlap matrix for gth-tzvp has a roughly similar condition number but seems much less sensitive to how many MPI processes I use. If I start dropping exponents in the gth-cc-tzvp basis set, so that now the condition number is ~ 10^2 , the results still seem to depend on the order of 1e-3 Ha/Cell depending on how I run the job.


An introduction to using var name = new var(); is missing.

@Frederisk commented on Mon Jul 01 2019
The explanation for using in code like the following is missing.
*using* var decryptStream = new MemoryStream();
*using* var decrypt = new CryptoStream(decryptStream, decryptTransform, CryptoStreamMode.Write);
decrypt.Write(encryptBytes, 0, encryptBytes.Length);
var decryptBytes = decryptStream.ToArray();
var decryptedString = Encoding.UTF8.GetString(decryptBytes, 0, decryptBytes.Length);
return decryptedString;

I hope it can be added.

文件詳細資料
⚠ 請勿編輯此區段。 這是 docs.microsoft.com ➟ GitHub 問題連結的必要項。

ID: 042902cc-1598-5df1-34cc-caa0fad63e02
Version Independent ID: e186d0c4-523e-38f7-2cde-d00109ea784b
Content: using 陳述式 - C# 參考
Content Source: docs/csharp/language-reference/keywords/using-statement.md
Product: dotnet-csharp
GitHub Login: @BillWagner
Microsoft Alias: wiwagn

Hi team,
I'm moving this here since the user is making a suggestion to the original documentation
kind regards

Thanks @CeciAc
This is in our roadmap for adding before .NET Core 3.0 ships.

@BillWagner .NET Core 3.0 has shipped...


handling of DOIs in Scopus metadata import: use dc.identifier.doi instead of dc.identifier

Describe the bug
DOIs of items that are imported via Scopus metadata import are stored in (the generic identifier) metadata field dc.identifier instead of dc.identifier.doi.
This change was introduced 2 years ago by this commit: https://github.com/DSpace/DSpace/commit/8ffb4dd6c60c6c7b8799fccd07cf13c02dbe471b#diff-a3dd3c9dee8a3c386c19d4a96c79e287696e8124a8a729d71fa292c73957a998R133
We propose that DOIs are stored in dc.identifier.doi.

Please consider also #5565 and associated PRs.  There is a long-standing question about where identifiers from different sources should be stored, particularly to distinguish those that DSpace controls from those assigned by others.


Update micromamba docker image and setup-micromamba action

Overview

Update the setup-micromamba action to v2
Update the micromamba docker image to use the recently released 1.5.10 tag

Testing
How did you make sure this worked? How can a reviewer verify this?
# To-do list
- [ ] If updating analyses or data processing functions: make sure to update or write data validation tests (e.g. `test_minmax_rows()`).
- [ ] Run `make pytest-coverage` locally to ensure that the merge queue will accept your PR.
- [ ] Review the PR yourself and call out any questions or issues you have.
- [ ] For minor ETL changes or data additions, once `make pytest-coverage` passes, make sure you have a fresh full PUDL DB downloaded locally, materialize new/changed assets and all their downstream assets and [run relevant data validation tests](https://catalystcoop-pudl.readthedocs.io/en/nightly/dev/testing.html#data-validation) using `pytest` and `--live-dbs`.
- [ ] For bigger ETL or data changes run the full ETL locally and then [run the data validations](https://catalystcoop-pudl.readthedocs.io/en/nightly/dev/testing.html#data-validation) using `make pytest-validate`.
- [ ] Alternatively, run the `build-deploy-pudl` GitHub Action manually.

See this pytest action run for confirmation that the integration tests work without the big runner.


Problem with the "Load OSM file" tool

Hello,
When I try to use the "Load OSM file" tool, I receive an error message when trying to loading the data into a feature class game so I ticked the geoprocessing option "Replace results of geoprocessing operations". By the way, the tool works very well when the feature class set does not exist.
Error encountered: "Incompatible version of OSM extension detected (Detected 1, 2 expected).".

Hello Tony - I was able to replicate the behavior here. I'll continue to look at it tomorrow and see why it's happening.

I think this is a bug - or if its working as designed, then tool documentation should be updated.  Steps to replicate:

Manually create a feature dataset in ArcCatalog, with the following feature classes: 1) a point feature class with the name [nameOfFeatureDataset]_osm_pt, 2) a line feature class with the name [nameOfFeatureDataset]_osm_ln, and a polygon feature class with the name [nameOfFeatureDataset]_osm_ply. Accept the defaults in the wizard for creating the new feature classes.
Launch the Load OSM File tool, and attempt to populate the tool such that the .osm file target feature class is this new empty one you've created.
You will get the error described above in the user interface  "Incompatible version of OSM extension detected (Detected 1, 2 expected).", and won't be able to run the tool.

Further question here - is there a workflow where this issue is critical, versus just being annoying that you have to use the tool to create the feature dataset rather than creating it in advance? If so, will you please describe that workflow? e.g., script or process? Thanks!

In fact, when I launch the tool alone or in a model builder, it's the same result.
The problem is that I need to relaunch OSM data to have the lastest version of the features. First I tried with the diff OSM Load tool but, even with a small data set, it runs during 2 or 3 days without downloading data.
So I have created a model builder witch use xapi dowload tool, load osm data tool and attribute tool for every data set I need (highway, landuse, leisure, natural, waterway, ...)
And then I made some very beautiful city map with ArcGIS...

Another problem with this tool.
I made a model builder with this tool and export il in python. When I run the Python script, I get the following error :
Traceback (most recent call last):
File "V:_FMW\Voirie\4-ChargementGDB.py", line 30, in
arcpy.OSMGPFileLoader_osmtools(voies_osm, "CONSERVE_MEMORY", "ALL", voies, OSM_Points, OSM_Lines, OSM_Polygons)
AttributeError: 'module' object has no attribute 'OSMGPFileLoader_osmtools'

Hello, could you tell me if you have found any solution with my problem.
The fact is that I have to show this toolbox in the next ESRI France Forum in september but if it doesn't works, I prefer not to show it.

Tony,
if you generate your own toolbox then the name/reference of the loader tool will change. 'arcpy.OSMGPFileLoader_osmtools' is referring to the tool in our toolbox. The nomenclature is name_of_tool__toolbox_alias. If your toolbox uses a different alias then you need to adjust the name accordingly. Also, if your script is running stand-alone, you might need to load the OpenStreetMap toolbox explicitly. For more information take a look at the arcpy help at http://desktop.arcgis.com/en/desktop/latest/analyze/python/adding-and-removing-toolboxes.htm

Thank you for the answer.
Have you any solution for the first problem witch was :
Incompatible OSM extension version detected. (Detected 1, expected 2)

That is pretty much expected behavior and a design choice we made for this release.
The reasoning was the following:

We are no longer adding the OSM custom object behavior by default. The custom behavior is the magic that makes the wonderful OSM editor work but only if you are intending to edit the OSM data. Based on the feedback we received only very few people are actually editing the data so it was more of a nuisance than anything else and hence we removed it. You can still enable the behavior (and you have to for editing) but it is now the additional step of enabling the OSM extension and the "Download, Extract, and Symbolize" model shows you how to do that.
We used the OSM extension information to tell what version of the OSM download we are dealing with. A couple releases ago we had a breaking schema change that causes this ripple effect. Now with the extension gone we don't know and decided to show the error you are encountering.
The solution is however fairly simple. Delete the feature dataset (because the tool would do exactly the same thing) and then load the osm file into a feature dataset which happens to have the same name you just deleted.

Hello everybody,
I'm sorry but I still have problems with my python script.
This is the script (I put "print" to see where the problems come from) :
print('0.0 Lancement du script de chargement du fichier osm dans la GDB')
print('1.1 Import du module arcpy')
import arcpy
print('1.3 Modules importés')
print('2.1 Définition des arguments ')
file_osm = "V:\_PROJETS\_CCPRO_OSM\OSMFiles\voies.osm"
Add_OSM_tag_keys_to_schema = "ALL"
layer = "V:\_GDB\OSM_CCPRO.gdb\voies2"
print('2.2 Arguments définis')
print('3.1 Définition des variables ')
layer_osm_pt = file_osm
layer_osm_ln = file_osm
layer_osm_ply = file_osm
print('3.2 Variables définies')
print('4.1 Lancement du process 3LoadFile_One')
arcpy.OSMGPFileLoader_osmtools(file_osm, "CONSERVE_MEMORY", Add_OSM_tag_keys_to_schema, layer, layer_osm_pt, layer_osm_ln, layer_osm_ply)
print('99. script 3LoadFile_One achevé')

And this is the result :
0.0 Lancement du script de chargement du fichier osm dans la GDB
1.1 Import du module arcpy
Warning (from warnings module):
File "C:\Program Files (x86)\ArcGIS\Desktop10.3\ArcPy\arcpy_init_.py", line 157
warnings.warn("Failed importing {0}".format(filename))
UserWarning: Failed importing c:\program files (x86)\arcgis\desktop10.3\ArcToolbox\Toolboxes\ccpro_download_using_xapi.py
0.0 Lancement du script DownloadOSMFiles
1.1 Import des modules arcpy, sys, urllib, urllib2
1.2 Import du module local
1.3 Import des modules arcpy.ImportToolbox
Warning (from warnings module):
File "C:\Program Files (x86)\ArcGIS\Desktop10.3\ArcPy\arcpy_init_.py", line 157
warnings.warn("Failed importing {0}".format(filename))
UserWarning: Failed importing c:\program files (x86)\arcgis\desktop10.3\ArcToolbox\Toolboxes\DownloadOSMFiles.py
Warning (from warnings module):
File "C:\Program Files (x86)\ArcGIS\Desktop10.3\ArcPy\arcpy_init_.py", line 157
warnings.warn("Failed importing {0}".format(filename))
UserWarning: Failed importing c:\program files (x86)\arcgis\desktop10.3\ArcToolbox\Toolboxes\download_using_xapi.py
Warning (from warnings module):
File "C:\Program Files (x86)\ArcGIS\Desktop10.3\ArcPy\arcpy_init_.py", line 157
warnings.warn("Failed importing {0}".format(filename))
UserWarning: Failed importing c:\program files (x86)\arcgis\desktop10.3\ArcToolbox\Toolboxes\LoadFiles.py
1.3 Modules importÃ©s
2.1 DÃ©finition des arguments
2.2 Arguments dÃ©finis
3.1 DÃ©finition des variables
3.2 Variables dÃ©finies
4.1 Lancement du process 3LoadFile_One
Traceback (most recent call last):
File "V:_ARCGIS\3LoadFile_One.py", line 34, in
arcpy.OSMGPFileLoader_osmtools(file_osm, "CONSERVE_MEMORY", Add_OSM_tag_keys_to_schema, layer, layer_osm_pt, layer_osm_ln, layer_osm_ply)
AttributeError: 'module' object has no attribute 'OSMGPFileLoader_osmtools'

I see where is the problem. It's the UTF-8 encoding option of Python Shell...


mediapipe android customize output packets

    Hello, i would like to create my own output stream from graph ("merged_landmarks" for ex.). How will I able to initialize this in addpacketcallback because it seems it is not yet defined somewhere in the mediapipe workspace aside from the graph. thank you very much.

Here is my modified holistic_tracking_to_render_data.pbtxt with the "merged_landmarks" output stream in middle part

### The code snippet

### The error
2022-11-12 12:02:45.067 28089-28166/com.lite.holistic_tracking E/native: E20221112 12:02:45.067229 28166 graph.cc:474] ; Input Stream "landmarks_merged" for node with sorted index 2 name callback_calculator_that_collects_stream_landmarks_merged does not have a corresponding output stream.
2022-11-12 12:02:45.068 28089-28166/com.lite.holistic_tracking D/GlThread: Stopping GL thread ExternalTextureConverter
2022-11-12 12:02:45.069 28089-28166/com.lite.holistic_tracking E/AndroidRuntime: FATAL EXCEPTION: ExternalTextureConverter
Process: com.lite.holistic_tracking, PID: 28089
com.google.mediapipe.framework.MediaPipeException: unknown: ; Input Stream "landmarks_merged" for node with sorted index 2 name callback_calculator_that_collects_stream_landmarks_merged does not have a corresponding output stream.
at com.google.mediapipe.framework.Graph.nativeStartRunningGraph(Native Method)
at com.google.mediapipe.framework.Graph.startRunningGraph(Graph.java:336)
at com.google.mediapipe.components.FrameProcessor.startGraph(FrameProcessor.java:553)
at com.google.mediapipe.components.FrameProcessor.maybeAcceptNewFrame(FrameProcessor.java:421)
at com.google.mediapipe.components.FrameProcessor.onNewFrame(FrameProcessor.java:439)
at com.google.mediapipe.components.ExternalTextureConverter$RenderThread.renderNext(ExternalTextureConverter.java:485)
at com.google.mediapipe.components.ExternalTextureConverter$RenderThread.lambda$onFrameAvailable$0$ExternalTextureConverter$RenderThread(ExternalTextureConverter.java:413)
at com.google.mediapipe.components.-$$Lambda$ExternalTextureConverter$RenderThread$IXJjtE68JMV2CMJNQcFYhTUqhj8.run(Unknown Source:4)
at android.os.Handler.handleCallback(Handler.java:938)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loopOnce(Looper.java:210)
at android.os.Looper.loop(Looper.java:299)
at com.google.mediapipe.glutil.GlThread.run(GlThread.java:141)
Originally posted by @QuiLevitin in https://github.com/google/mediapipe/issues/2317#issuecomment-1311487215

I just want to close this problem because I forgot to update the binarypb from Android Studio which solves the issue. Thank you and happy Coding!


fix(isNumeric): handle numeric string case

Description:
Added a string check before , to eliminate numeric string cases.
Related issue (if exists):
#3699

Coverage decreased (-0.02%) to 96.884% when pulling d221f8ddc7e3e6d57b7a945d4f0354b3b36e87da on akoserwal:fix-isNumeric-num-string into bc49e40a887d2b1946bf5294b4027369f0b753c3 on ReactiveX:master.

Hi, @akoserwal! This is an api for internal use only. Is there something breaking in the external API that this is fixing?

@benlesh: It is not fixing anything in the external API. I find many people are using this internal API and discussing about this particular case which I had covered here.

@benlesh : In that case, I can close this PR. Although it is meant to be used internally. I have seen some discussion where it is been used as external consumption by some other projects. It's optional, if we want to handle string input.


Limits issue?

Currently, it seems memory for the VM is created via the 'spec.domain.resources.requests' field. The limit for the virt-launcher pod seems to come from the namespace default (kubectl get limits default). If the default limits are lower than the requests, the virt-launcher pod does not create.
Reproduce: "kubectl edit limits default", set memory to 128Mi, then try to create a VM with 1Gi of memory.
I propose that the virt-launcher pod's 'spec.domain.resources.limits.memory' be set to the request field. It seems the VM is already slightly less than the request, so hopefully there's enough buffer in the pod for running bash or whatever else might be needed, but there may need to be additional buffer accounted for in this number.
Alternatively, change the memory field to come from the limit rather than the request, in which case kubernetes will automatically populate the request field to match.
Likewise, it seems like setting CPU via spec.domain.cpu.cores does not change the virt-launcher's CPU request/limit beyond the namespace default. This may be by design, for example one could create an 8 core VM that is throttled down to 100m CPU time, but I'm not sure.

Likewise, it seems like setting CPU via spec.domain.cpu.cores does not change the virt-launcher's CPU request/limit beyond the namespace default. This may be by design, for example one could create an 8 core VM that is throttled down to 100m CPU time, but I'm not sure.

Hi,
Yes, absolutely. The spec.domain.cpu.cores setting only controls the cpu topology of the vm, as it will be seen by the guest OS. Currently, we are only presenting 1 socket with X cores and 1 thread.
Please see [1]
The number of physical CPUs that the VM will run on can be requested using the spec.domain.resources.requests.cpu as in [2]

Currently, it seems memory for the VM is created via the 'spec.domain.resources.requests' field. The limit for the virt-launcher pod seems to come from the namespace default (kubectl get limits default). If the default limits are lower than the requests, the virt-launcher pod does not create.

Thanks, I wasn't aware of this, let me look into it.
On the other hand, memory limits can set using the  spec.domain.resources.limits.memory as in [2], does it solve the problem?

It seems the VM is already slightly less than the request, so hopefully there's enough buffer in the pod for running bash or whatever else might be needed, but there may need to be additional buffer accounted for in this number.

We are accounting a memory overhead, please see [3] and [4]. There is an ongoing effort to improve this and suggestions are welcome :)
I think the reason for less memory being presented in the guest OS is because of the kernel memory reservations.
[1] http://www.kubevirt.io/user-guide/#/workloads/virtual-machines/virtualized-hardware-configuration?id=cpu
[2] http://www.kubevirt.io/user-guide/#/workloads/virtual-machines/virtualized-hardware-configuration?id=resources-requests-and-limits
[3] http://www.kubevirt.io/user-guide/#/workloads/virtual-machines/virtualized-hardware-configuration?id=memory-overhead
[4] https://github.com/kubevirt/kubevirt/blob/master/pkg/virt-controller/services/template.go#L255

Yes, explicitly setting a limit works, and should be fine if there's overhead built-in. This means users who have low defaults have to always specify both memory requests and memory limits to the same value (or limit higher than requests). It works but is a bit unintuitive to users who are simply thinking in terms of "how do I set the VM's RAM".
On the one hand I could see kubevirt ensuring the memory limit is at least the request for virt-launcher pod, to avoid failures that might not be easy for the end user to figure out.  I can also see the limit and request being used to set initial and max RAM for a VM with memory ballooning, but I guess that's not really in conflict with ensuring that limit is >= request.

@mlsorensen great that you brought that up.

Yes, explicitly setting a limit works, and should be fine if there's overhead built-in. This means users who have low defaults have to always specify both memory requests and memory limits to the same value (or limit higher than requests). It works but is a bit unintuitive to users who are simply thinking in terms of "how do I set the VM's RAM".

I agree. I would even formulate it as a hard requirement that users can simply think about  "how do I set the VM's RAM". Our overhead should not be of interest to them.
In my opinion the main issue is that we even allow posting VMs which are invalid when considering the default limits. We now have the possibility to reject vms, because of the validating webhook. I think the webhook should take the overhead into account and simply reject the vm with something like:
invalid: spec.resources.requests: Invalid value: "610554432":
        must be less than or equal to memory limit

A few more things to make it less confusing for people:

Add the allowed maximum to the error message.
Let a modifying webhook set the maximum based on the pod default limits (this one is not yet there, but we will need it for all modifications which happend because of defaulting and presets anyway).

So step one would be adding validation with the default limits in mind, the second step would be the modifying webhook.

I can also see the limit and request being used to set initial and max RAM for a VM with memory ballooning, but I guess that's not really in conflict with ensuring that limit is >= request.

Yes that is one of the goals to use it for ballooning too.

Looks like "limits" aren't pulled in from VM presets, so with presets at least it can't override a low default limit.

@mlsorensen maybe my comment was confusing. Nothing of what I describe above is currently happening, just in case it sounded like the presets should take the limits into account already.

Oh no, I wasn't getting that from your comment. Just that I thought maybe this could be worked around for users via presets, adding a 'limits' in addition to the 'requests' in the preset would mean that  individual VMs would not need to specify both.
As it stands, if I have a 'foo' preset that 'requests' 1Gi of RAM, as a user if my default limits are small I have to still specify a 'limits' value in my VM even when using 'foo' preset. Trying to add a 'limits' to the preset to get around this does nothing. I think that's a bug, perhaps a separate issue should be created to apply limits via preset?

@mlsorensen I'm wondering whether are working on this already? I'd like to start a PR, just don't to get in your way if you are planning too. :)

@fabiand we marked it for 1.1, let us know if you disagree

Another aspect to this is that the cluster defaults are not visible in the VM spec i.e. if as in the example the limits are set, the limits will not turn up on the vm spec, only on the vmpod.
We could however also respect those limits with kubevirt and add them to the VM spec in order to make this at least visible (that defaults were applied).


[WAX615] Cannot add the integration: Username, Password, or Address is wrong.

Version of the custom_component
0.1.4
Device information
Netgear WAX615
Firmware version: V<IP_ADDRESS>
Configuration
logger:
  default: info
  logs:
    custom_components.netgear_wax: debug

Nothing else related to this component is included in configuration.yaml.
Describe the bug
Upon trying to add the integration, the following error is displayed:
Username, Password, or Address is wrong.
I have triple checked that fields are correct.
Debug log

Pasting the relevant log lines found in home-assistant.log after enabling debug logs for custom_components.netgear_wax:
2023-08-24 16:43:54.135 DEBUG (MainThread) [custom_components.netgear_wax] Creating client with username admin
2023-08-24 16:43:55.092 DEBUG (MainThread) [custom_components.netgear_wax] Logging in with username admin
2023-08-24 16:43:56.590 DEBUG (MainThread) [custom_components.netgear_wax] login security token response={ "status": 401 }
2023-08-24 16:43:56.591 ERROR (MainThread) [custom_components.netgear_wax] Failed: Could not get security token: { "status": 401 }
Traceback (most recent call last):
  File "/config/custom_components/netgear_wax/config_flow.py", line 87, in _test_credentials
    state = await client.async_get_state()
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/netgear_wax/client_wax.py", line 93, in async_get_state
    result = await self.async_post(request_data)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/netgear_wax/client_wax.py", line 199, in async_post
    await self.async_login()
  File "/config/custom_components/netgear_wax/client_wax.py", line 57, in async_login
    raise Exception("Could not get security token: " + text)
Exception: Could not get security token: { "status": 401 }

Looking forward to getting some feedback. Thanks!

Thanks. I will close this and use https://github.com/rroller/netgear/issues/18 to track this issue. I see what's wrong now

This should be fixed in the latest version of the plugin, please try that.

Now it’s working. Thanks!


Check error comparability for avoiding panic

To fix #22

Codecov Report

Merging #26 into master will increase coverage by 0.1%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master      #26     +/-   ##
=========================================
+ Coverage   96.15%   96.25%   +0.1%
=========================================
  Files           5        5
  Lines         182      187      +5
=========================================
+ Hits          175      180      +5
  Misses          4        4
  Partials        3        3

Impacted Files
Coverage Δ

pkgerrors.go
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

https://github.com/srvc/fail/pull/26/commits/4dc2444760cf27e435c692cb158ffd17ba314a84
-		} else if reflect.DeepEqual(rootErr, err) {
+		} else {

err == nil ⇒ rootErr == nil
err != nil ⇒ rootErr != nil ∧ ( rootErr == err ∨ rootErr != err )

なのでこの比較は不要。

Any plan to release this?

@qnighy Sorry!... Here's the new version:
https://github.com/srvc/fail/releases/tag/v4.1.0


Fix sideload text track issues on iOS

This PR is designed to fix #1155.
While investigating this, I discovered the code would cause text tracks to be displayed even if the type was set to "disabled". I've refactored the code so that we only look for text tracks matching the device language if the type is "system".

@ashnfb I can't figure out how to make it so all text tracks get disabled. The code to loop through all the tracks and update the enabled status works fine as long as we enable at least one track. But if I setEnabled:NO for all of them, the text for the most recently selected track gets stuck on the screen and never disappears. Any ideas how we can tackle this? I've looked all over Stack Overflow and can't find anything.
Here's the relevant code:
  for (int i = firstTextIndex; i < _player.currentItem.tracks.count; ++i) {
    BOOL isEnabled = NO;
    if (selectedTrackIndex != RCTVideoUnset) {
      isEnabled = i == selectedTrackIndex + firstTextIndex;
    }
    [_player.currentItem.tracks[i] setEnabled:isEnabled];
  }

@ashnfb Ok, thanks man. I've asked a friend who's pretty familiar with AVPlayer how to tackle this, but I haven't heard back from him yet.

@cobarx Does someone looking at this issue? i can help you if you tell me where to start from


how to handle network request failed error?

I have a form and want to send it to a server and get a response so I wrote this:
submitForm = async () => {
  fetch("www.somewhere.com", {
    method: 'POST',
    headers: {
      'Content-Type': 'application/json',
    },
    body: JSON.stringify(some_data)
  })
  .then((response) => response.json())
  .then((responseJson) => {
     // do something
  })
  .catch((error) => {
      this.setState({server_error: "request failed try again."});
  });
};

But It seems that my catch doesn't work correctly because if the request fails I get an error from react native like this:

TypeError: Network request failed
at XMLHttpRequest.xhr.onerror (C:\Archive\code\current\native\melcom\node_modules\react-native\Libraries\vendor\core\whatwg-fetch.js:504)

Note that I'm not struggling with http or https, I just want to provide a nice error to the user if the request fails due to the internet connection, wrong API, etc. instead of getting react native error.

Did you find a solution?

I am having deep trouble with these errors. I can't query data with React Native from Backend (in Heroku) using mLab.
Error: Network error: Network request failed
at new ApolloError (blob:http://localhost:8081/288f46c3-20cd-40df-9227-3cba3c633362:126473:28)
at ObservableQuery.getCurrentResult (blob:http://localhost:8081/288f46c3-20cd-40df-9227-3cba3c633362:126583:20)
at ObservableQuery.currentResult (blob:http://localhost:8081/288f46c3-20cd-40df-9227-3cba3c633362:126557:27)
at Query._this.getQueryResult (blob:http://localhost:8081/288f46c3-20cd-40df-9227-3cba3c633362:115908:53)
at finish (blob:http://localhost:8081/288f46c3-20cd-40df-9227-3cba3c633362:116089:43)
at Query.render (blob:http://localhost:8081/288f46c3-20cd-40df-9227-3cba3c633362:116096:14)
at finishClassComponent (blob:http://localhost:8081/288f46c3-20cd-40df-9227-3cba3c633362:15468:37)
at updateClassComponent (blob:http://localhost:8081/288f46c3-20cd-40df-9227-3cba3c633362:15431:30)
at beginWork (blob:http://localhost:8081/288f46c3-20cd-40df-9227-3cba3c633362:16117:22)
at performUnitOfWork (blob:http://localhost:8081/288f46c3-20cd-40df-9227-3cba3c633362:18744:18)

I have this error while want to get node server data inside react native app I tried by removing localhost with ip address of the machine.
TypeError: Network request failed
at XMLHttpRequest.xhr.onerror (C:\Users\usman\Desktop\Native-charts\ChartApp\node_modules\react-native\Libraries\Renderer\oss\ReactNativeRenderer-dev.js:4424)
at XMLHttpRequest.dispatchEvent (C:\Users\usman\Desktop\Native-charts\ChartApp\node_modules\react-native\Libraries\Renderer\oss\ReactNativeRenderer-dev.js:10894)
at XMLHttpRequest.setReadyState (C:\Users\usman\Desktop\Native-charts\ChartApp\node_modules\react-native\Libraries\Renderer\oss\ReactNativeRenderer-dev.js:10602)
at XMLHttpRequest.__didCompleteResponse (C:\Users\usman\Desktop\Native-charts\ChartApp\node_modules\react-native\Libraries\Renderer\oss\ReactNativeRenderer-dev.js:10435)
at C:\Users\usman\Desktop\Native-charts\ChartApp\node_modules\react-native\Libraries\Renderer\oss\ReactNativeRenderer-dev.js:10541
at RCTDeviceEventEmitter.emit (C:\Users\usman\Desktop\Native-charts\ChartApp\node_modules\react-native\Libraries\Components\DrawerAndroid\DrawerLayoutAndroid.android.js:240)
at MessageQueue.__callFunction (blob:http://localhost:8081/c3345fde-73f7-4e22-9b43-24b8d9f444ea:4614)
at C:\Users\usman\Desktop\Native-charts\ChartApp\node_modules\react-native\Libraries\ART\ReactNativeART.js:213
at MessageQueue.__guard (C:\Users\usman\Desktop\Native-charts\ChartApp\node_modules\react-native\Libraries\ART\ReactNativeART.js:387)
at MessageQueue.callFunctionReturnFlushedQueue (C:\Users\usman\Desktop\Native-charts\ChartApp\node_modules\react-native\Libraries\ART\ReactNativeART.js:212)

Is there anyone cleared this..

Have you found a solution for this? I am having the same error.

Use error.message
As state
this.state.error: error.message
On Sun 14 Apr, 2019, 5:02 PM Sathish<EMAIL_ADDRESS>wrote:

Have you found a solution for this? I am having the same error.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/23403#issuecomment-482953304,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AinTOf3Ek1SWT9FmYXD3qu_vA5UOyUMFks5vgxHggaJpZM4a20x-
.

error.message
this.state.error:error.message

Hi @Dina07 , Always fetch throwing error. throwing Network request failed. How to solve this issue.

Remove console.log(error);
Or
Show me your code
On Mon 15 Apr, 2019, 10:19 AM Sathish<EMAIL_ADDRESS>wrote:

Hi @Dina07 https://github.com/Dina07 , Always fetch throwing error.
throwing Network request failed. How to solve this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/23403#issuecomment-483106005,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AinTOZbXPgnDJxqBnmhLHWB-XEV8Ifpaks5vhATQgaJpZM4a20x-
.

Any updates? Still impossible to catch network errors?

put error.message
On Tue, Jun 4, 2019 at 12:34 AM MIkhail Kozlov<EMAIL_ADDRESS>wrote:

Any updates? Still impossible to catch network errors?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/23403?email_source=notifications&email_token=AIU5GOMQIWK36RQUUNKOW33PYVTKHA5CNFSM4GW3JR7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW2LW7Q#issuecomment-498383742,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIU5GOMO3IID6IBGL66JZQDPYVTKHANCNFSM4GW3JR7A
.

--
With Regards:
D.DHINAGARAN
Contact Number:+91-9597193436

Grant permission for network
On Tue, Jun 4, 2019 at 10:21 AM DINAGARAN<EMAIL_ADDRESS>wrote:

put error.message
On Tue, Jun 4, 2019 at 12:34 AM MIkhail Kozlov<EMAIL_ADDRESS>wrote:

Any updates? Still impossible to catch network errors?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/23403?email_source=notifications&email_token=AIU5GOMQIWK36RQUUNKOW33PYVTKHA5CNFSM4GW3JR7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW2LW7Q#issuecomment-498383742,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIU5GOMO3IID6IBGL66JZQDPYVTKHANCNFSM4GW3JR7A
.

--
With Regards:
D.DHINAGARAN
Contact Number:+91-9597193436

--
With Regards:
D.DHINAGARAN
Contact Number:+91-9597193436

@jordimuntada Did you fix your problem? I am having the same issue with Android throwing a Network Request Failed error when trying to call a Heroku-hosted API.

@jordimuntada Did you fix your problem? I am having the same issue with Android throwing a Network Request Failed error when trying to call a Heroku-hosted API.

put error.message in console

Any solution for this issue?

@jordimuntada Did you fix your problem? I am having the same issue with Android throwing a Network Request Failed error when trying to call a Heroku-hosted API.

I can't remember what I did to correct this error.
Do you still have that same error? Let me take a look into it.

put error.message
…
On Tue, Jun 4, 2019 at 12:34 AM MIkhail Kozlov @.***> wrote: Any updates? Still impossible to catch network errors? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#23403?email_source=notifications&email_token=AIU5GOMQIWK36RQUUNKOW33PYVTKHA5CNFSM4GW3JR7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW2LW7Q#issuecomment-498383742>, or mute the thread https://github.com/notifications/unsubscribe-auth/AIU5GOMO3IID6IBGL66JZQDPYVTKHANCNFSM4GW3JR7A .
-- With Regards: D.DHINAGARAN Contact Number:+91-9597193436

Is there any way to get the corresponding error code for 'Network request failed' ?


Experimental features

This won't probably be merged, just to try out some feature

[x] Litestream
[x] Granian

To generate a project using this branch
falco start-project my_awesome_project -c experimental

Another branch with https://github.com/orm011/pgserver and granian

add this to gitignore
db.sqlite3-wal
db.sqlite3-shm


How do I use object detection on a video ?

I have a video of couple of objects and I would like to know how do I use object detection on a video.
Now I am using object detection model ResNet-18 with c920 logitech camera.

 The code below is for using the C920 web cam:
import cv2
import jetson.utils
import jetson.inference

model = jetson.inference.detectNet()
width = 640
height = 320

cam = cv2.VideoCapture('/dev/video1')
cam.set(cv2.CAP_PROP_FRAME_WIDTH, width )
cam.set(cv2.CAP_PROP_FRAME_HEIGHT, height )

# Opening the camera
while cam.isOpened():

    ret, frame = cam.read()
    frame = cv2.flip(frame, 1)
    frame_rgba = cv2.cvtColor(frame, cv2.COLOR_BGR2RGBA).astype(np.float32)

    img = jetson.utils.cudaFromNumpy(frame_rgba)

    detections = model.Detect(img, width, height, "box,labels,conf")
    conv1 = jetson.utils.cudaToNumpy(img, width, height, 4)
    conv2 = cv2.cvtColor(conv1, cv2.COLOR_RGBA2RGB).astype(np.uint8)
    conv3 = cv2.cvtColor(conv2, cv2.COLOR_RGB2BGR)

    if cv2.waitKey(1) & 0xFF == ord('q'):
        break

cam.release()
cv2.destroyAllWindows()

If you want to use the image without bounding boxes you use frame variable, but if you want the image with it you will use conv3.
if you want to load a video that you already have just put the link in cv2.VideoCapture('LINK HERE')

I am using pre recorded video from the camera

I just tried this code leandrovrabelo and this is not working because you are using np.uint8
this kinda of variable is not in the program so how it should run ?
the error is np is not defined

I found out that there is 1 line missing for some reason should be import numpy as np :)
by the way can i see live object detection on a video ?
when i will run a program the program will open a window that i can see live object detection from the video ?

The code above works with the web cam.
use the details below instead of inserting the video link:
cam = cv2.VideoCapture('/dev/video1')
to confirm which device you should use open a terminal and paste the following code:
v4l2-ctl --list-devices
It will show the available cameras.

I used your code as it is and I get this error : np is not defined

I used your code as it is and I get this error : np is not defined
perhaps you need to:
import numpy as np

Thanks @leandrovrabelo finally something that works :)

If you update or re-clone your repo from the latest master and re-run make and sudo make install, support for video playback/recording was also added earlier this summer.
You should now be able to do something like:
$ detectnet my_video_input.mp4 my_video_output.mp4


Enable ES Module usage

As noted in #80, es module imports are currently broken on the 2.1.0 release.
According to the node docs, the package.json module field is ignored. Instead, an ES module can be signified using "type": "module".
In this PR:

[x] Bump to 2.1.1
[x] Add "type": "module"

@jhurliman It looks like we'll need a similar change to just-performance too. Did you want me to go ahead and update that too?

@benschwarz
Adding "type": "module" makes this module not importable by other commonjs modules, as I tested locally.
The change to remove "type": "module" is introduced in #79 .
I think the real problem is that the module is not built properly to support esm and cjs at the same time.


Add Cuda and CuDNN version

Hey Andrea,
Great work on the bindings, they work very well. Would it be possible to add the version of Cuda and CuDNN that you used in the readme. It seems to be Cuda 8 + CuDNN 5.1 currently.
Due to how Cuda/CuDNN depreciation works, deprecated or WIP procs temporarily get a version number like this one:
https://github.com/unicredit/nimcuda/blob/4bf458d13fe98380aa7241b891c1e850393ae57f/nimcuda/cudnn.nim#L275-L279
Those are then removed for ever (deprecated) or replace a "normal core" proc.
So between CuDNN v5.1 and CuDNN v7, some procs may have the same name but different arguments due to having been replaced, or others will have disappeared altogether.

It is in fact CUDA 8 + CuDNN 5.1, I will add this


RooParametricShapeBinPdf allow functional parameters

Hi,
This PR generalizes RooParametricShapeBinPdf to allow the function to have parameters that are themselves functions (RooAbsReal). Our previous implementation only allowed parameters to be variables (RooRealVar) due to the use of RooAbsReal::asTF (https://root.cern.ch/doc/master/RooAbsReal_8cxx_source.html#l04104), which enforces that.
As a reminder, this binned PDF is intended to act as wrapper to a continuous/analytical PDF, forcing RooFit to correctly calculate the integrals under the curve. This is used in several dijet analyses (and may be used in the combined all-hadronic diboson analysis), where the variable-width bins are very coarse.
Here is a simple script to test the new PR and show the bias introduced by fitting with the usual method: https://gist.github.com/jmduarte/c616c486d4532cdd5a56150c1ccc42d5
Thanks,
Javier

I added a small fix 62c2d99 to re-define the ranges for each bin at evaluation time in case they don't exist.
This is needed for cases when workspaces are combined (and the variable is imported from a different workspace, which doesn't have the ranges defined in that one!).

Hi @jmduarte
I think this modification deserves some additional text in this section of the docs: https://cms-hcomb.gitbooks.io/combine/content/part2/settinguptheanalysis.html#caveat-on-using-parametric-pdfs-with-binned-datasets which advertises that the user can use functions.
Can you propose some text?

I would propose text as follows:
2. Another solution (currently implemented for 1-dimensional histograms only) is to use a custom pdf which wraps the original pdf and performs the correct integrals internally as in RooParametricShapeBinPdf.

Note version 2 of this pdf class now allows parameters that are themselves RooAbsReal objects (i.e. functions of other variables). The integrals are handled internally by calling the underlying pdf’s createIntegral() method with named ranges created for each of the bins. This means that if the analytical integrals for the underlying pdf are available, they will be used.

Perfect, thanks!


UI: Implement upload, fetch and paste input methods for data input

From @andrewthecoder on February 3, 2015 14:55
Multiple data file input methods sought, including drag-and-drop text files, copy-pasting and possibly file fetching with CORS (and accompanied help guide) as an optional task.
Copied from original issue: HeriotWattMEng2015/ShExDemo#2

From @skhutan on February 22, 2015 12:48
drag-and-drop and copy-paste data input implemented, CORS data fetching + help guide to be completed as an optional feature


Where is pyrealsense2.py after compilation?

Required Info

Camera Model
D400

Firmware Version
SDK 2.0

Operating System & Version
Windows 10

Kernel Version (Linux Only)

I would like to use the Python wrapper and I think that I managed to compile it (what I did was run Cmake_gui which created a c:\realsense\librealsense-master\build\wrappers\python\RealsensePythonWrappers.sln solution file that I promptly opened and built without errors).
But where is pyrealsense2.py, the creation of which I had assumed was the point of the whole compilation procedure? I cannot find any .py files un the whole build directory.
Am I missing something really obvious? Please pardon my utter noobishness.

Open librealsense2.sln under build directory, build pyrealsense2 project under Wrappers solution-folder, pyrealsense2.pyd will be under build\Release\pyrealsense2.pyd or build\Debug\pyrealsense2.pyd.
Let us know if this helps

You can also use pre-compiled pyrealsense2.pyd provided with the installer.

So, in the meantime I figured out that there is no .py file but rather the .pyd file is the one to work with. I haven't found the pre-compiled one but the one I compiled works fine. Many thanks for getting back to me.


Update elasticsearch to match docs

r? @muffinresearch?

@muffinresearch Thanks. I notice in the .travis.yml that this gets auto deployed to pypi, which is so cool. What does one do after a pip update to make this rebuild the container?

fig build elasticsearch should do it.


Add API key and token variables for AI services

I wanted to specify the API key or Token for the AI service when starting LibreChat, so I added variables.

cool, thanks!


Add unsafeExtendSafeZone footgun

The wallet requested this functionality, see its docstring for more details. We
begrudgingly provide this footgun and take no responsibility for any bugs caused
by it.

bors merge


Name of top function is misleading

Quote from the docs:

*fn top(&self) -> mut u8
Returns the top of the stack. On all modern architectures, the stack grows downwards, so this is the highest address.

If the stack grows downwards, then the top of the stack is at the lowest address. Presumably this function actually gets the base of the stack.

okay we can rename this, will do


Adds signature verification on proxy messages

 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.giogio21 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.

@giogio21 I let you fix comments from Emilien before doing my review.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 148 (0.0%)  changed or added relevant lines in 2 files are covered.
14 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-1.4%) to 53.344%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

contracts/evoting/controller/handlers.go
0
58
0.0%

contracts/evoting/controller/action.go
0
90
0.0%

Files with Coverage Reduction
New Missed Lines
%

contracts/evoting/controller/handlers.go
1
0%

services/dkg/pedersen/handler.go
13
84.89%

Totals

Change from base Build<PHONE_NUMBER>:
-1.4%

Covered Lines:
2991

Relevant Lines:
5607

💛  - Coveralls


Review cookie-Cutter

I forked the imswitch cookie-cutter into this repository. Nothing has changed as the hooks remain the same. I updated the README.md. Are there points we would need to review? @jacopoabramo

Done!


feat(select): add prop popperFitSelectWidth

Description
add prop popperFitSelectWidth default is false
basic use:

popperFitSelectWidth === true

the popper width will equal select width

popperFitSelectWidth === false

just like the original

popperFitSelectWidth === number

set the popper width

Linked Issues

Additional Context

I think this prop name is too long. Better to fit-popper.


Remove heuristics for finding Python and NumPy in favor of baseline find_package

The basic CMake FindPython functionality works well in modern enough versions. The heuristics may have predated the ability to specify find_package(Python ... COMPONENTS ... NumPy).
FindPython docs for reference: https://cmake.org/cmake/help/latest/module/FindPython.html
Additions
N/A
Removals
N/A
Changes

Rely on CMake to pick up the active python installation (system or virtual environment) found by find_package(Python ...)
Update the minimum version of CMake to ensure that will work

Testing

Manual testing on my system with a mix of conformations of virtual environments and packages installed in the system environment

Screenshots
N/A
Notes

Developers on other teams may need to be informed that they'll need to activate their virtual environment before configuring with cmake, rather than just having ngen/venv present

Todos

[ ] Update documentation accordingly

Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[x] Code follows project standards (link if applicable)
[x] Passes all existing automated tests
[x] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[x] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)
[x] Reviewers requested with the Reviewers tool :arrow_right:

Target Environment support

[x] Linux
[x] macOS

Draft mode until I go over the documentation and update it to match.

General comment, we do still require the NumPy headers (or pybind11 does, I think)... so what's the thought behind removing the documentation of the necessity of installing that?

They're part of the pip package, and picked up by CMake without additional guidance:
$ find test-venv/lib/python3.11/site-packages/numpy/ | grep '.h$'
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/ndarrayobject.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/utils.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/__multiarray_api.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/npy_1_7_deprecated_api.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/oldnumeric.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/experimental_dtype_api.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/libdivide/libdivide.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/old_defines.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/ufuncobject.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/npy_common.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/npy_cpu.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/ndarraytypes.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/npy_no_deprecated_api.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/npy_3kcompat.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/npy_os.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/npy_endian.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/npy_interrupt.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/_numpyconfig.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/_neighborhood_iterator_imp.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/numpyconfig.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/__ufunc_api.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/arrayscalars.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/random/distributions.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/random/bitgen.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/npy_math.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/halffloat.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/arrayobject.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/_dtype_api.h
test-venv/lib/python3.11/site-packages/numpy//core/include/numpy/noprefix.h
test-venv/lib/python3.11/site-packages/numpy//f2py/src/fortranobject.h

(venv) Phils-Mac-mini:ngen phil$ cmake -B test-numpy -S<EMAIL_ADDRESS>-- The C compiler identification is AppleClang <IP_ADDRESS>00029
-- The CXX compiler identification is AppleClang <IP_ADDRESS>00029
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /Library/Developer/CommandLineTools/usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /Library/Developer/CommandLineTools/usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Compiler: /Library/Developer/CommandLineTools/usr/bin/cc
-- Compiler: /Library/Developer/CommandLineTools/usr/bin/c++
-- No Boost root:
-- Found Boost<EMAIL_ADDRESS>(found suitable version "1.76.0", minimum required is "1.72.0")
INFO UDUNITS_ACTIVE not defined
Looking for UDUNITS-2...
-- Could NOT find UDUNITS2 (missing: UDUNITS2_LIBRARY UDUNITS2_INCLUDE)
-- Updating submodule /Users/phil/Code/noaa/ngen/extern/UDUNITS-2
INFO - Linking libudunits2 to path "/Users/phil/Code/noaa/ngen/test-numpy/UDUNITS-2/build/lib/libudunits2.dylib"
INFO NGEN_ACTIVATE_PYTHON set to 'true' by default
-- Found Python: /Users/phil/Code/noaa/ngen/venv/bin/python3.11 (found suitable version "3.11.4", minimum required is "3.6.8") found components: Interpreter Development NumPy Development.Module Development.Embed
Python_NumPy_INCLUDE_DIRS = /Users/phil/Code/noaa/ngen/venv/lib/python3.11/site-packages/numpy/core/include
-- pybind11 v2.10.1
-- Performing Test HAS_FLTO
-- Performing Test HAS_FLTO - Success
-- Performing Test HAS_FLTO_THIN
-- Performing Test HAS_FLTO_THIN - Success
-- Found Boost<EMAIL_ADDRESS>(found version "1.76.0")
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD
-- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Success
-- Found Threads: TRUE
-- Found Python: /Users/phil/Code/noaa/ngen/venv/bin/python3.11 (found version "3.11.4") found components: Interpreter
-- Configuring done (1.6s)
-- Generating done (0.1s)
-- Build files have been written to: /Users/phil/Code/noaa/ngen/test-numpy

(I added the print of Python_NumPy_INCLUDE_DIRS to demonstrate that it worked)

They're part of the pip package, and picked up by CMake without additional guidance...

Interesting. This probably makes sense but I wonder about the plethora of Python setups... we should probably check this out with a conda env before merging at a minimum, and maybe with OS-installed numpy package (e.g. Debian-style). But yes it will probably work fine.

For posterity, @mattw-nws @robertbartel and I discussed this, and decided to go ahead with the build system change here, and to separately consider the runtime behaviors that this brings into consideration.

Belated note, yes I did have to do this in Visual Studio Code (VSCode) via .vscode/settings.json after this PR, to get the IDE's cmake integration to find a virtual environment it was finding automatically before:
{
    "cmake.environment": {
        "VIRTUAL_ENV":"/path/to/.venv",
        // ...
    }
}

I think the 'right' thing to do would rather be to define Python_ROOT_DIR in a CMake user presets file. So, don't pretend that all the other stuff the venv drops in the environment is also set, just point CMake at the installation and let it do its thing.

https://cmake.org/cmake/help/latest/manual/cmake-presets.7.html


parameters of render  z_far and z_near

Hi, I noticed that the z_far and z_near is 5 and 15 in the pytorch version.However, the near_clip is 0.01 and far_clip is  50.0 in the tensorflow version.  I wonder why  there is such a difference？

The original wider range is unnecessary in our case where faces are located with a distance of 10 to the camera, so we change them to 5 and 15 respectively.


Dask support

Should we add Dask as a supported library that we wrap? See https://github.com/dask/dask/pull/8750#issuecomment-1438365157. CC @tomwhite @jakirkham

That probably makes sense to do. And in principle I think that this package can add support for any widely used array library.

I probably won't prioritize work on this myself for now unless some downstream consumer library expresses a desire for Dask support here. But if you want to submit a pull request adding it I will be happy to review and merge it.
The primary purpose of this library is to wrap existing libraries so that they more closely match the array API. This is preferable to using a separate namespace in the library itself because end-users can continue to use the existing array objects, and only the corresponding consumer library (like scipy or scikit-learn) would need to use this compat layer to make use of the uniform array API on it.

For the record, as discussed in other PRs, I started experimenting with what would imply supporting dask in scikit-learn via the Array API spec.
array-api-compat support for dask would indeed simplify those experiments and make it possible for early adopters to try it before numpy and dask mains API are fully aligned with the Array API spec by default.
See the discussion in: https://github.com/scikit-learn/scikit-learn/issues/26724

BTW I'll be running a sprint on the array API next week at the SciPy conference sprints. If any of you will be present this could be a thing to sprint on.

@asmeurer let me know if you give it a shot. It should be quite easy to adapt scikit-learn tests to also add dask.array to the the list of namespaces to test against:
https://github.com/scikit-learn/scikit-learn/blob/83a8015702213b39510a0f4898bc6879bcdf3ac2/sklearn/utils/_array_api.py#L13-L50
Then it's a matter of running:
pytest -k array_api sklearn/

I'm not sure when I'll be able to work on this issue, but if someone else wants to work on implementing it I'll be happy to review/help with questions.

cc @jrbourbeau (for awareness)

Dask support has been merged. Quite a lot of functionality is skipped in the tests, which maybe could be improved with further wrappers, though most of it will either need to be fixed upstream, or can never be supported in Dask. People should open new issues if they run into any missing or broken behavior with Dask.


feat: add syntax highlighting

change pyyaml version to 3.1.3 to avoid this error: https://github.com/yaml/pyyaml/issues/152

I think you need to add a value for highlight to the default CONFIG; otherwise this looks great!

Ah, actually I think you need to add dependencies to setup.py as well

@benwr done.


Casecmp autocorrect to .zero? can fail is the & operator is used

value&.casecmp('true') == 0
will get corrected to
value&.casecmp('true').zero?
This can fail if value is nil. .zero?
Expected behavior
value&.casecmp('true') == 0
should become
value&.casecmp('true')&.zero?
Actual behavior
Becomes value&.casecmp('true').zero?
Steps to reproduce the problem
Autocorrect value&.casecmp('true') == 0
RuboCop version
$ rubocop -V
0.42.0

The same happens for Array.index, which can return int or nil
Use path.index(url).zero? instead of path.index(url) == 0.

The same happens for Array#index, which can return int or nil.

The purpose of using #zero? is to protect you from methods with "broken" signatures, like this one. 😀 It is likely that this cop (or at least the auto-correction) will be made disabled by default in #3398, as people seem to rely on the fact that you can also send #== to nil (even though I would argue you shouldn't. :wink: )

The cop will be marked unsafe in #5978


Add support for backing up mysql database

Code that works with mysql is on this branch: https://github.com/jchonig/docker-mmonit/tree/backup.  It is also built on docker hub with tag backup-4.2.2
It needs testing on sqlite3 to ensure it still works.
@sseide do you use the backup functionality?

Currently i am using external backup for my mysql data.
But i can try your solution later this week.

hi - looking at the script i found some issues and things to impprove. I created an PR with the updates. Feel free to either accept or cherry-pick from it.

@sseide lots of good stuff in there.
I upgraded the branch to 3.19 and will integrate and test your changes there.
Would someone actually access mysql via a socket from within a container?

Would someone actually access mysql via a socket from within a container?

At least i do :-)
Having one central database to tune and take care of, running locally on docker host. This has no other network connection. Only socket is mounted into all containers needing a database.
Every docker container bringing its own DBMS nowadays is to much work to tune and secure everything. Every db needs its own backup setup and software updates to watch and apply... much easier having one system only to focus on.

@sseide I refactored the changes init initialization, which run in the s6 service init-mmont and the actual backup in /etc/periodic/hourly/mmonit_backup.
I think I have all your changes included.  Could you please take a look.
Thanks
Jeff


License question

Thanks for your help with holes, it seems everything works when vertices are unique.
Could you please write what is the license for your library?

In the README it says: License : MIT.


Prop name wrong?

[Vue tip]: Prop "iconpath" is passed to component , but the declared prop name is "iconPath". Note that HTML attributes are case-insensitive and camelCased props need to use their kebab-case equivalents when using in-DOM templates. You should probably use "icon-path" instead of "iconPath".

Can you copy your code here? You should use it like this, not in your component prop.
import VueFlags from "@growthbunker/vueflags";

Vue.use(VueFlags, {
  // Specify the path of the folder where the flags are stored.
  iconPath: '/images/vueflags/flags/',
});

The documentation is available here: https://www.growthbunker.dev/vueflags/

I'm including it via