CORE-5402 Trusted Root Certificates - Retrieve certificates and pass to verification library

Retrieve packaging verification library trusted certificates from DB

Can we please also remove corda-runtime-os\components\chunking\chunk-db-write-impl\src\main\resources\cordadevcodesignpublic.pem. It was just part of the stub which is replaced by actual cert fetching.

Can we please also remove corda-runtime-os\components\chunking\chunk-db-write-impl\src\main\resources\cordadevcodesignpublic.pem. It was just part of the stub which is replaced by actual cert fetching.

removed


Synthesis failed for Google.Cloud.SecurityCenter.V1P1Beta1

Hello! Autosynth couldn't regenerate Google.Cloud.SecurityCenter.V1P1Beta1. :broken_heart:
Please investigate and fix this issue within 5 business days.  While it remains broken,
this library cannot be updated with changes to the Google.Cloud.SecurityCenter.V1P1Beta1 API, and the library grows
stale.
See https://github.com/googleapis/synthtool/blob/master/autosynth/TroubleShooting.md
for trouble shooting tips.
Here's the output from running synth.py:
2021-03-19 22:45:48,389 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/Google.Cloud.SecurityCenter.V1P1Beta1
2021-03-19 22:45:48,877 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2021-03-19 22:45:48,881 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2021-03-19 22:45:48,885 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2021-03-19 22:45:48,888 autosynth [DEBUG] > Running: git config push.default simple
2021-03-19 22:45:48,892 autosynth [DEBUG] > Running: git branch -f autosynth-Google.Cloud.SecurityCenter.V1P1Beta1
2021-03-19 22:45:48,896 autosynth [DEBUG] > Running: git checkout autosynth-Google.Cloud.SecurityCenter.V1P1Beta1
Switched to branch 'autosynth-Google.Cloud.SecurityCenter.V1P1Beta1'
2021-03-19 22:45:49,102 autosynth [DEBUG] > Running: git rev-parse --show-toplevel
2021-03-19 22:45:49,109 autosynth [DEBUG] > Running: git log -1 --pretty=%H
2021-03-19 22:45:49,113 autosynth [DEBUG] > Running: git remote get-url origin
2021-03-19 22:45:49,148 synthtool [ERROR] > Failed executing git checkout master:

error: Your local changes to the following files would be overwritten by checkout:
	google/cloud/dialogflow/v2/answer_record.proto
	google/cloud/dialogflow/v2/conversation.proto
	google/cloud/dialogflow/v2/conversation_profile.proto
	google/cloud/dialogflow/v2/participant.proto
Please commit your changes or stash them before you switch branches.
Aborting

Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 312, in _inner_main
    git_source.enumerate_versions(sources, pathlib.Path(temp_dir))
  File "/tmpfs/src/github/synthtool/autosynth/git_source.py", line 202, in enumerate_versions
    source_versions = enumerate_versions_for_source(git_source, temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/git_source.py", line 166, in enumerate_versions_for_source
    local_repo_dir = str(synthtool_git.clone(remote))
  File "/tmpfs/src/github/synthtool/synthtool/sources/git.py", line 85, in clone
    shell.run(["git", "checkout", "master"], cwd=str(dest), check=True)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['git', 'checkout', 'master']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


[$1000] IOU - IOU preview amount is displayed in recipient's Report currency when Send 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:
Prerequisites on Olddot:
Set Account A Report Currency USD
Set Account B Report Currency SGD (or any different from USD)

Go to https://staging.new.expensify.com/
and login with account A
Send $100 from A to B
On account B - Check the currency displayed in the IOU

Expected Result:
IOU preview under account A should be in USD in USD, as Report currency is USD and user is sending USD
Actual Result:
IOU preview under account A is displayed in SGD (or any other currency that was set in OldDot for account B)
Workaround:
Unknown
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: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: Yes
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://user-images.githubusercontent.com/93399543/225104735-c4e56882-f074-4b14-99c9-f3dd9ad53ec8.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~0157937139cce1cc56
Upwork Job ID:<PHONE_NUMBER>410894848
Last Price Increase: 2023-04-13

Triggered auto assignment to @johncschuster (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

@johncschuster Eep! 4 days overdue now. Issues have feelings too...

@johncschuster 8 days overdue is a lot. Should this be a Weekly issue? If so, feel free to change it!

@johncschuster this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

@johncschuster 12 days overdue. Walking. Toward. The. Light...

This issue has not been updated in over 14 days. @johncschuster eroding to Weekly issue.

@johncschuster this issue is now 3 weeks old. There is one more week left before this issue breaks WAQ. What needs to happen to get a PR in review this week? Please create a thread in #expensify-open-source to discuss. Thanks!

@johncschuster Whoops! This issue is 2 days overdue. Let's get this updated quick!

@johncschuster this issue is now 4 weeks old and preventing us from maintaining WAQ. This should now be your highest priority. Please post below what your plan is to get a PR in review ASAP. Thanks!

Job added to Upwork: https://www.upwork.com/jobs/~0157937139cce1cc56

Triggered auto assignment to Contributor Plus for review of internal employee PR - @Santhosh-Sellavel (Internal)

@johncschuster, @Santhosh-Sellavel 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

Triggered auto assignment to @strepanier03 (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

John is OOO, reassigning so this gets actioned. thanks!

Working on this now.

I can recreate this without issue, here are my testing notes:
Account A =<EMAIL_ADDRESS>set to USD
Account B =<EMAIL_ADDRESS>set to CHF
Account A sent account B $100 USD. The IOU is in CFH for both account A and account B.

@Santhosh-Sellavel - I just triaged this and am ready to move it forward. It has the internal label now, but that's because of the length of time this went without an update.
I think this should be an external issue but when I relabel it I don't know if another C+ is going to be assigned. If that happens I will remove their assignment so you can still have this job and let them know what happened.
If you disagree with this being external, let me know and we can chat about it and change it.

Current assignee @strepanier03 is eligible for the External assigner, not assigning anyone new.

Current assignee @Santhosh-Sellavel is eligible for the External assigner, not assigning anyone new.

Triggered auto assignment to @stitesExpensify (External), see https://stackoverflow.com/c/expensify/questions/7972 for more details.

I think this could be internal as it seems like a backend issue to me!

Okay @Santhosh-Sellavel - you are definitely better equipped to help make that call and I'll send this back internal. Thank you.

Current assignee @Santhosh-Sellavel is eligible for the Internal assigner, not assigning anyone new.

Applied the Help Wanted label for added traction.

I'll post in Slack and see if there are any takers.

@strepanier03, @stitesExpensify, @Santhosh-Sellavel Whoops! This issue is 2 days overdue. Let's get this updated quick!

Still waiting for some takers

Brandon is working on this so I removed the help wanted label.

I am going to be OoO from April 26-May 3. I plan to leave this assigned to me during my out-of-office as it likely won't need my action before I return.
If something changes and action is needed from the BugZero team, please reach out in #expensify-open-source to request help from another team member.
Thanks, chat with you when I get back!

@strepanier03, @stitesExpensify, @Santhosh-Sellavel 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

@strepanier03, @stitesExpensify, @Santhosh-Sellavel 6 days overdue. This is scarier than being forced to listen to Vogon poetry!

@stitesExpensify - Is Daily still the right label for this? Just checking in for an update.

@strepanier03 yep, this should remain Daily and we need to prioritize it. @stitesExpensify any update on this one?

Thank you @michaelhaxhiu - I'll continue following along until my action is needed.

Update from @stitesExpensify in Slack:

I was hard focused on threads for the previous 2 weeks, and then was OOO for a week. I'll be sure to work on it this week

@stitesExpensify - Any update that we can share here?

Brandon updated in the weekly OS resync that they wouldn't have bandwidth until next week at the earliest. If something changes and you'd like me to try to find another engineer to help move this forward please let me know @stitesExpensify otherwise I'll continue to monitor and help however you need.

I think that this was actually fixed with the switch to threads. At the high level it shows how much I owe in my currency, and then if I go into the thread, then it shows the original currency. IMO that is the correct functionality


Doc lgcm

Started the documentation for LGCM and renamed the Arguments with underscores to go with the other Taxon-Arguments.
non_linear_function argument now requires a vector of slopes.
closes #55

Working on a new lgcm version (as a lot was missing from the old one in my opinion), which makes this branch obsolete


Support using a customer service account to run Cloud Build triggers in the cicd recipe

The work needs to be done are roughly

Follow this and add necessary resources to our cicd recipe, which includes a new logging bucket, an optional service account (either passed in or created in our recipe, toggled by an input param). The service account will later be used in google_cloudbuild_trigger resources.

The feature to use a custom SA in cloud build triggers are still in beta, and Terraform's google beta provider does not seem to support that yet. See pending issue. The code to support that likely should be added here. We can help implement that. Terraform provider has a weekly release schedule. Once the change is approved and merged, it might take 1-2 weeks for it to be available, so need to plan accordingly.

Note: the cloud build's doc suggests that feature is still in beta, but in that issue in terraform provider repo, someone suggests that it's already GA. This is something to look into a bit more and verify.

Change the google_cloudbuild_trigger resources in cicd recipe to use the service account. If need to switch to beta provider, we should add google-beta in the resource's provider field. The cloudbuild yaml file should be modified to use the custom logging bucket as well.

Test, add docs for upgrade instructions, etc.

PR #5237 for adding the service_account field to google_cloudbuild_trigger in the provider merged.

#1034


suggestion: add DO NOT EDIT comment to generated bindings files

Generated bindings files should indicate that they are generated with an auto-generated DO NOT EDIT comment at top of the file. This is not needed for Rust, but any language like c where the bindings are part of the project should have this comment.
// Code generated by wit-bindgen DO NOT EDIT.
// Version:
// Revision:
// Build Date:
// Built By:

Many editors recognize this string and warn when editing the file. Many tools include build-level information for triage. This might be especially useful for wit-bindgen while breaking changes are still frequent.

:+1:  to adding comments to the generated bindings.
I'm curious about the need ffor Version/Revision/Build Date/Built By fields. At first glance, it seems like version-control systems do a good job of tracking this information already.

I included this snippet from what I've seen when the generator is a CLI and not managed as a dependency, e.g. not in go.mod/go.sum, Cargo.toml, etc.
go-enum is an example: https://github.com/abice/go-enum/blob/8268238fd705b39d430e7d8682b527af8452b6ab/generator/enum.tmpl#L1-L6
So if wit-bindgen were run as a CLI because it was provided as a globally installed tool in a build container, the version used might not be captured in git.
To be honest, most of those fields seemed redundant to me, but I figured I'd drop the superset of what I've seen and we can pick from that.

This has been fixed by #490; it appears GitHub didn't auto-close this issue.


Stream/IR/test:timepoint_folding.mlir.test is timeout after integrates

The test will be disabled in https://github.com/iree-org/iree/pull/11245

@benvanik Doing a Github clean up scrub again.. Any priority / status here?


Milestones should not have a due date field.

    const milestonesJSON = await danger.github.api.issues.listMilestonesForRepo({
        owner: danger.github.thisPR.owner,
        repo: danger.github.thisPR.repo,
    });
    console.log(JSON.stringify(milestonesJSON, null, 4));

:tada: This issue has been resolved in version 2.0.0 :tada:
The release is available on:

2.0.0
GitHub release

Your semantic-release bot :package::rocket:


Step 7: Upload the artifacts into staging repository for release vote

After all the artifacts are packaged in Step 6, we need to upload them to the staging repo for the community to vote, with a release name as an input.
We can definitely use the same tools in Step 6, to push the artifacts upstream.
I have created a folder called openwhisk: https://dist.apache.org/repos/dist/dev/incubator/openwhisk/, under the apache dev/incubator, as the dir for us to stage.

This issue can be closed for now, because the code structure to upload the artifacts into the staging url is up and ready. The source code artifacts are able to be uploaded. For further binaries and docker images, they can easily be ported to re-use the same code structure.


[Feature]: Add new selected state colour on DS repo

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
https://www.notion.so/appsmith/Unified-add-panel-18a94e51a498410aa5503379babb6ef0?p=cce00a1ac41146d1b7385735420376b9&pm=s
Why should this be worked on?
part of unified add panel

@hetunandu The icon active colour doesn’t seem to be a darker shade of grey as suggested in design
DP:

Design:


argocd-dex-server Deployment's init container does not use image variable

When specifying an image in the ArgoCD resource as documented here, the init container copyutil of the argocd-dex-server deployment does not use the specified image (contrary to all the other deployments).

Hello, thanks for the report, can you confirm which version of the operator, and how you're configuring the image?

Sorry, could've said that from the beginning. It's the ArgoCD operator 0.0.14 installed via OLM on OpenShift 4.6 and my configuration is looking like this:
apiVersion: argoproj.io/v1alpha1
kind: ArgoCD
metadata:
  name: my-argo-cd
spec:
  dex:
    openShiftOAuth: true
  image: redacted.company.docker.mirror/argoproj/argocd
  rbac:
    policy: |
      g, cluster-admin, role:admin
  redis:
    image: redacted.company.docker.mirror/redis
  server:
    autoscale:
      enabled: true
    ha:
      enable: true
    host: my-argocd.apps.my-ocp-cluster.my-company.com
    ingress:
      enabled: false
    insecure: true
    route:
      enabled: true
  usersAnonymousEnabled: false

I have already seen that the dex section of the CR has an image field for the dex image itself, but this obviously doesn't have anything to do with the init container.

Hi, I've had a look, and the init-container is not using the Dex image.
The container that is executed is doing the equivalent of:
$ cp /usr/local/bin/argocd-util /shared so, it's using the image from the top-level image declaration
https://argocd-operator.readthedocs.io/en/latest/reference/argocd/#image-example and not the dex image.

Hi, yes I know. What I wanted to say is: in my case every component of ArgoCD (server, application-controller, and so on) is correctly using the image redacted.company.docker.mirror/argoproj/argocd I declared in the top-level declaration but the init container of dex is still using argoproj/argocd (so using the cluster's default registry) instead redacted.company.docker.mirror/argoproj/argocd

Hi @Obirah Sorry, I've had a look, and there was a bug in v0.0.14 which I'm just about to open a PR for, while it is using the ArgoCD spec.image, it doesn't update the init-container's image if you change after it was initially created.
You can try deleting the dex Deployment object, and it should be recreated with the correct init-container image from spec.image.

Awesome, deleting the Deployment worked as predicted. I'll leave this issue open though so that other people can find it in the meantime and you can link the PR.


Problem With Permission

It keeps saying this when I try applying any changes in the bloxstrap menu:
System.Net.Http.HttpRequestException: An attempt was made to access a socket in a way forbidden by its access permissions. (clientsettingscdn.roblox.com:443)
===== Inner Exception =====
System.Net.Sockets.SocketException: An attempt was made to access a socket in a way forbidden by its access permissions.
here is the log btw
Bloxstrap_20230727T122938Z.log

Do you have anything on your computer that could be blocking Bloxstrap from connecting to the internet?

Could a vpn be doing it?

Probaby. Try disabling that and see if anything changes.

wait, my vpn isn't on, so what should i do?

I just don't really know how to or where i could find something blocking my internet for the app.

Antivirus, maybe?

that's what im looking at

right now

yep my antivirus was being goofy, thanks for putting up with my dumbness


Update plugin to escape path to bin/man.fish

Previously an error would throw if the path to /bin/man.fish involved spaces or other special characters. This commit escapes the string before having Vim parse it.
Resolves https://github.com/dag/vim-fish/issues/36#issuecomment-254576309

This PR addresses the same issue as https://github.com/dag/vim-fish/pull/32 but in a slightly different way. Will let the maintainer decide which is the best solution and merge.

@dag Can we get this merged? Thanks!

It appears this is an abandoned repo.

Oops. Yours is probably the better fix, but since you closed this I missed it and merged the other one. Maybe I'll fix it manually, but feel free to open a new PR because I might not get to it.

Reopened @dag. Thanks! I appreciate this plugin. Thanks for looking at this.


Add TreemapContext to Treemap

Add TreemapContext to Treemap.
This allows children of Treemap to reference some information

order
position
direction of next element

This allows users to customize Treemap more easily and clearly

Codecov Report
Attention: Patch coverage is 0% with 46 lines in your changes are missing coverage. Please review.

Project coverage is 67.22%. Comparing base (fc3afc0) to head (9c25e48).

Files
Patch %
Lines

packages/treemap/src/treemap.tsx
0.00%
46 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #343      +/-   ##
==========================================
- Coverage   68.99%   67.22%   -1.78%
==========================================
  Files          39       39
  Lines        1329     1364      +35
  Branches      241      251      +10
==========================================
  Hits          917      917
- Misses        412      447      +35

Flag
Coverage Δ

unittests
67.22% <0.00%> (-1.78%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


(Bug)Text fixes and Jest tests fixes

Description
@johnsmith-gooddollar

Fixes text formatting
Fixes Jest tests
Adds catalog.js files to .gitignore

@alecsantos96
Please perform global search on:
showDialog(
showErrorDialog(
You will find a lot of places you've forgot to localize. Fix them, don't forget to re-generate translation files and update tests/snapshots
Please work from the latest master https://github.com/GoodDollar/GoodDAPP/commit/41243ac9e76c33aeab1ec427721b5b23495fd1e5


Remove CDS_ASG_SHIFT_TRAFFIC_STEP_NG from docs

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screenshot.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://660b4cb4a1f59b446d29235f--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://660ba9ddfe5563881288d231--harness-developer.netlify.app


Critical issue using EF Core on UWP (unable to open database file)

Steps to reproduce
Follow this simple tutorial.
The issue
Start the app either in Debug or Release.
An exception occurs with db.Database.Migrate();.
Exception thrown: 'Microsoft.Data.Sqlite.SqliteException' in Microsoft.Data.Sqlite.dll. Additional information: SQLite Error 14: 'unable to open database file'.
This is the very first step, Migrate() method should create the database if there is not any yet (it also fails with db.Database.EnsureCreated()).
Further technical details
EF Core Tools version: 1.0.0-preview2-final
EF Core Sqlite version: 1.0.0
UniversalWindowsPlatform version: 5.2.2
Operating system: Windows 10 (UWP)
Visual Studio version: VS 2015 Update 3

@bbougot can you zip up and share a project that reproduces the issue?

WindowsApp1.zip
Simply tick every thing in Exception Window and launch in Release using .NET Native Toolchain.

I believe this is a duplicate of https://github.com/aspnet/EntityFramework/issues/5386#issuecomment-220089390. @bbougot although the exception is thrown, it doesn't actually represent a bug as EF Core handles this and continues execution normally.

Yes this is exactly the same issue. Although it does not crash the app, it's a weird issue, which leads to a misinterpretation (the database is created anyway).

Closing as a duplicate of #5386


Add dynamically created ForagePINEditText to catalog

What

Why

Test Plan

✅ | ❌ I've added unit tests for this change.
✅ | ❌ The reviewer should manually test the changes in this PR.

Demo

How

#277  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @devinmorgan and the rest of your teammates on  Graphite


Add support to execute same request with multiple parameters.

there are scenarios where user want to invoke requests with different payload and run tests.
supporting this will help testers.

refer: https://stackoverflow.com/questions/78279438/postman-how-to-iterate-over-query-parameters-and-save-the-responses-into-a-sing


solved -- Error: 'Emulation.resetViewport' wasn't found

looks like screenshotMultipleSelectors() may be broken?
$ node -v
v8.1.0
error:
~/Desktop/backstop test @gshipon-mn1(gshipon)
$ node chromyTest
error caught > Error: 'Emulation.resetViewport' wasn't found

script:
chromy
  .chain()
  .console(function (text, consoleObj) {
    if (console[consoleObj.level]) {
      console[consoleObj.level]((consoleObj.level).toUpperCase() + ' > ', text);
    }
  })
  .goto('examples/featureTests/index.html')
  .wait(1)
  .screenshotMultipleSelectors(
    ["body", "h1", "h2"],
    handlescreenshots,
    {useQuerySelectorAll: true}
  )
  .end()
  .then(_ => {
    chromy.close()
    console.log('success');
  })
  .catch(e => {
    chromy.close()
    console.log('error caught > ' + e);
  });

function handlescreenshots(error, png, index, selectors, sub){
  console.log('>>>',error, selectors[index], sub);
  fs.writeFileSync(`./screens/${selectors[index]}_${sub}.png`, png);
}

I have tried chromy 0.3.1,  0.3.2, 0.3.3 all return the same response. 😔

@dotneet  Found the issue!  Chrome Canary was throwing the error.  v61.0.3155.0
Don't know if that command was deprecated.  Thought you'd want to know.

Thanks. I confirmed that that command will remove in future and discover alternative way.
I'll support both versions canary and stable.

@garris
I opened the issue that related to this problem at chromium 3 days ago.
https://bugs.chromium.org/p/chromium/issues/detail?id=741969
I've published new version of chromy that supports chrome61, but chrome's bug was fixed yesterday.
So maybe you need to update chrome canary.

will do.  thanks!


Incident: OpenAI

The service "OpenAI" has been down since 24                 nov.                 2024                 03h29                 (Downtime: 60.071 seconds).

Investigating - We are aware of an issue which has resulted in TEST being unavailable. We are currently investigating and working to restore functionality as soon as possible.

test

Identified - We have identified the root cause of this issue, and are currently working to implement a fix.

Update - We are continuing to work on the fix for our issue. Thank you for your patience.

Monitoring - A fix has been implemented and we are monitoring results. Most users should already see access to TEST restored.

Resolved - This issue has now been resolved. Between 4:06pm and 4:30pm PT, TEST was unavailable to all users. Access was restored to most users by 4:34, with a small number of customers still experiencing issues until 5pm.


Updating ball holding rules for 2022 and modifying tests accordingly

Changes are as follows:

Duration allowed before ballholding has been extended from 1 to 5 seconds.
Maximal distance at which ballholding can occur has been divided by 2

This implied changing time indications and position of robots on a few tests.
The part C of the ball_holding/multi_robot_kid test has also been fixed (it
was not testing what the README pretended to test).

This also includes the fixes from #300


Detection rule new detection ux

Description
Replaced the detection code editor in Detection rule creation form to use UI components. It simplifies entering detection and also allows user to enter values for a field by uploading text or csv files.

Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #575 (ec9d6a7) into main (0e38a1b) will decrease coverage by 0.73%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #575      +/-   ##
==========================================
- Coverage   32.49%   31.76%   -0.73%
==========================================
  Files         136      138       +2
  Lines        4084     4228     +144
  Branches      666      687      +21
==========================================
+ Hits         1327     1343      +16
- Misses       2617     2746     +129
+ Partials      140      139       -1

see 17 files with indirect coverage changes


Not able to create ZoneAuth

When I tried to create ZoneAuth, it seems that the fqdn set for the ZoneAuth instance is not being passed into the post request:
1.9.3-p448 :001 > require 'infoblox'
 => true
1.9.3-p448 :002 > ENV["WAPI_VERSION"]='1.2'
 => "1.2"
1.9.3-p448 :003 > connection = Infoblox::Connection.new(username: 'username', password: 'password', host: 'host')
 => #<Infoblox::Connection:70211723145900 @host="host">
1.9.3-p448 :004 > zone_auth = Infoblox::ZoneAuth.new(:connection => connection)
 => #<Infoblox::ZoneAuth:0x007fb6e1a1c558 @connection=#<Infoblox::Connection:70211723145900 @host="host">>
1.9.3-p448 :005 > zone_auth.fqdn = 'zone1.com'
 => "zone1.com"
1.9.3-p448 :006 > zone_auth.post
Infoblox::Error: Error: 400 { "Error": "AdmConProtoError: field for create missing: fqdn",
  "code": "Client.Ibap.Proto",
  "text": "field for create missing: fqdn"
}

It would be greatly appreciated if you could take a look. Thank you for all the great work.

Hello - I pushed out gem version 0.5.1 with a fix for this.  Let me know if that works for you!

The fix works for me. Thanks a lot for the quick fix.


drag and drop doesn't work in cell outputs

playing around with react-chessboard — in a regular React app, this code
import { Chessboard } from "react-chessboard";

<div style={{ width: "400px" }}>
  <Chessboard />
</div>;

produces

but in vitale it produces

maybe something to do with how cell output frames are overlaid on the notebook?

drag and drop works fine with tldraw, both in cell outputs and in a separate view. There must be something particular about react-chessboard.


Remove security prompt

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

Coverage data is based on head (3cb0049) compared to base (ec6e4ee).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff            @@
##           develop       #4   +/-   ##
========================================
  Coverage    63.83%   63.83%
========================================
  Files           13       13
  Lines          777      777
========================================
  Hits           496      496
  Misses         281      281

Flag
Coverage Δ

unittests
63.83% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Errors in some case

Info:

OS: Archlinux up to date

Logseq ver: logseq-desktop-wayland-bin 0.9.19

Plugin ver: 2.4.0

Theme name: catppuccin mocha

[ x ] ⚠ Do i have issue with DISABLED my custom.css?
custom.css is empty

Description:
With the plugin enabled i get an error while navigating most recent pages, tried to understand what is the trigger but didn't manage to find it. Disabling the plugin, relaunching logseq and re-enabling it makes it work for sometime but errors will come back. Keeping the plugin disabled solve the error.
To Reproduce:
Create a new page and navigate to it.
Expected behavior:
Entering the page
Screenshots

Attach files
Can't find logs or whatever usefull on the system, if anything is needed i'm happy to help

I have the same issue!

I can confirm this issue, too.

logseq <IP_ADDRESS>
Awesome UI 2.4.0
logseq-dev-theme 1.26.17

Error Message in popup after any click on an link while Awesome UI is enabled:

Error caught by UI!
NotFoundError: Failed to execute 'insertBefore' on 'Node': The node before which the new node is to be inserted is not a child of this node.

Update:
Tried out for a couple of days now, after an update to catppuccin theme seems like the problem did fix himself.
Hoping this is solved for everyone

I am getting this same error. I do not have a custom css and am using default theme. I have rebuilt search index, cleared the cache and disabled all other plugins and still get the error.

Still getting this error, on both windows and ubuntu

Linux Mint user here, having this problem as well


Unexpected throttling during deployment from UpdateRolesWithIDPFunction

Amplify CLI Version
12.10.1
Question
amplify push fails as we create new environments.
We examine our cloud formation logs see the UpdateRolesWithIDPFunctionOutputs lambda function for amplify environment is the source of the error. We visit the cloudwatch logs and find this error.
Previously we used amplify v9.2.1 and deployed environments without issue, however after upgrading to v12.10.1 we are seeing this issue. This appears to occur intermittently as we have deployed some environments successfully.
Error in cloud watch:
{
    "Status": "FAILED",
    "Reason": "See the details in CloudWatch Log Stream: 2024/04/01/[$LATEST]80d0d2816e064b43824d00206af9b1b7",
    "PhysicalResourceId": "2024/04/01/[$LATEST]80d0d2816e064b43824d00206af9b1b7",
    "StackId": "arn:aws:cloudformation:us-west-2:370837355406:stack/amplify-www-lemona-140512/88476010-f06b-11ee-b2a3-02b61020254d",
    "RequestId": "c5c4f4fe-99b3-45eb-9d8f-d88fe8582fd0",
    "LogicalResourceId": "UpdateRolesWithIDPFunctionOutputs",
    "NoEcho": false,
    "Data": {
        "Error": {
            "name": "Throttling",
            "$fault": "client",
            "$metadata": {
                "httpStatusCode": 400,
                "requestId": "63175dcc-b2a1-4a43-85e3-806b74e7a9cd",
                "attempts": 3,
                "totalRetryDelay": 134
            },
            "Type": "Sender",
            "Code": "Throttling",
            "message": "Rate exceeded"
        }
    }
}

error.stack
2024-04-01T21:23:29.839Z	101336b9-30e1-45d2-84f6-68ca61681f54	INFO	Throttling: Rate exceeded
    at throwDefaultError (/var/runtime/node_modules/@aws-sdk/node_modules/@smithy/smithy-client/dist-cjs/index.js:838:20)
    at /var/runtime/node_modules/@aws-sdk/node_modules/@smithy/smithy-client/dist-cjs/index.js:847:5
    at de_CommandError (/var/runtime/node_modules/@aws-sdk/client-iam/dist-cjs/index.js:4635:14)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async /var/runtime/node_modules/@aws-sdk/node_modules/@smithy/middleware-serde/dist-cjs/index.js:35:20
    at async /var/runtime/node_modules/@aws-sdk/node_modules/@smithy/core/dist-cjs/index.js:165:18
    at async /var/runtime/node_modules/@aws-sdk/node_modules/@smithy/middleware-retry/dist-cjs/index.js:320:38
    at async /var/runtime/node_modules/@aws-sdk/middleware-logger/dist-cjs/index.js:33:22
    at async Promise.all (index 0)
    at async handleEvent (/var/task/index.js:62:25)

Lambda source
const response = require('cfn-response');
const { IAMClient, GetRoleCommand, UpdateAssumeRolePolicyCommand } = require('@aws-sdk/client-iam');
exports.handler = function(event, context) {
    // Don't return promise, response.send() marks context as done internally
    const ignoredPromise = handleEvent(event, context)
};
async function handleEvent(event, context) {
    try {
        let authRoleName = event.ResourceProperties.authRoleName;
        let unauthRoleName = event.ResourceProperties.unauthRoleName;
        let idpId = event.ResourceProperties.idpId;
        let authParamsJson = {
            'Version': '2012-10-17',
            'Statement': [{
                'Effect': 'Allow',
                'Principal': {'Federated': 'cognito-identity.amazonaws.com'},
                'Action': 'sts:AssumeRoleWithWebIdentity',
                'Condition': {
                    'StringEquals': {'cognito-identity.amazonaws.com:aud': idpId},
                    'ForAnyValue:StringLike': {'cognito-identity.amazonaws.com:amr': 'authenticated'}
                }
            }]
        };
        let unauthParamsJson = {
            'Version': '2012-10-17',
            'Statement': [{
                'Effect': 'Allow',
                'Principal': {'Federated': 'cognito-identity.amazonaws.com'},
                'Action': 'sts:AssumeRoleWithWebIdentity',
                'Condition': {
                    'StringEquals': {'cognito-identity.amazonaws.com:aud': idpId},
                    'ForAnyValue:StringLike': {'cognito-identity.amazonaws.com:amr': 'unauthenticated'}
                }
            }]
        };
        if (event.RequestType === 'Delete') {
            try {
                delete authParamsJson.Statement[0].Condition;
                delete unauthParamsJson.Statement[0].Condition;
                authParamsJson.Statement[0].Effect = 'Deny'
                unauthParamsJson.Statement[0].Effect = 'Deny'
                let authParams = {PolicyDocument: JSON.stringify(authParamsJson), RoleName: authRoleName};
                let unauthParams = {PolicyDocument: JSON.stringify(unauthParamsJson), RoleName: unauthRoleName};
                const iam = new IAMClient({region: event.ResourceProperties.region});
                let res = await Promise.all([
                    iam.send(new GetRoleCommand({RoleName: authParams.RoleName})),
                    iam.send(new GetRoleCommand({RoleName: unauthParams.RoleName}))
                ]);
                res = await Promise.all([
                    iam.send(new UpdateAssumeRolePolicyCommand(authParams)),
                    iam.send(new UpdateAssumeRolePolicyCommand(unauthParams))
                ]);
                response.send(event, context, response.SUCCESS, {});
            } catch (err) {
                console.log(err.stack);
                response.send(event, context, response.SUCCESS, {Error: err});
            }
        } else if (event.RequestType === 'Update' || event.RequestType === 'Create') {
            const iam = new IAMClient({region: event.ResourceProperties.region});
            let authParams = {PolicyDocument: JSON.stringify(authParamsJson), RoleName: authRoleName};
            let unauthParams = {PolicyDocument: JSON.stringify(unauthParamsJson), RoleName: unauthRoleName};
            const res = await Promise.all([
                iam.send(new UpdateAssumeRolePolicyCommand(authParams)),
                iam.send(new UpdateAssumeRolePolicyCommand(unauthParams))
            ]);
            response.send(event, context, response.SUCCESS, {});
        }
    } catch (err) {
        console.log(err.stack);
        response.send(event, context, response.FAILED, {Error: err});
    }
};

Hey @NickDario, thank you for reaching out. Could you let us know the number of resource the new environment is currently creating. Does waiting for a couple of minutes and running push mitigate the issue?

Currently we are creating about 1-200 IAM roles per environment. During our amplify cli upgrade we needed to create about half a dozen new environments, We deployed 2 before encountering this issue.
After the two were deployed we were unable to create any more for about 24 hours, and then we were only able to deploy one before encountering this issue again.
We verified we are not hitting any IAM quota limits as well.
What is unclear to me why this lambda is throwing. it seems to only update two policies, the auth and unauth roles. it consistently was this lamdba that threw the throttling error.

@NickDario apologies on the delay and thank you for the information. The issues seems to be occurring on the AWS SDK call UpdateAssumeRolePolicyCommand .
Marking this as bug for improvements to implement a backoff and retry strategy on the calls.


refactor: adjust LSP7 storage layout like LSP8

What does this PR introduce?
♻ Refactor
Minor change to adjust the storage layout of the token contracts so that they look similar between LSP7 and LSP8.

PR Checklist

[x] Wrote Tests
[x] Wrote & Generated Documentation (readme/natspec/dodoc)
[x] Ran npm run lint && npm run lint:solidity (solhint)
[x] Ran npm run format (prettier)
[x] Ran npm run build
[x] Ran npm run test

Task linked: DEV-5249 [Investigation] Test different storage layouts for LSP7/8 and see gas difference


Bug: Selecting a line containing decorator node in the beginning and pressing → arrow key moves selection to the decorator node

Lexical version: 0.14.5
Steps To Reproduce (See screencast)

On a new line, add an inline decorator node (e.g. Equation) and add some text after it.
Set the selection right at the end of the node.
Attempt to select the current line (using keyboard shortcut Cmd + Shift  + ← on Mac)
Attempt to go to the end of line (using keyboard shortcut →)

Expected behavior
Selection should move to the end of the line.
Actual behavior
Selection moves to the decorator node.
https://github.com/facebook/lexical/assets/35807215/43a9da24-0e05-4f19-872a-ca5cf9cd9333

Can still reproduce this one


implementing Centerpoint on KITTI dataset

Hello, I have tried to implement Centerpoint on kitti dataset and the results are shown below:

As you can see, it has reached reasonable results on most of the evaluation metrics except AOS. My first concern is that if it is related to the fact that the KITTI lidar frame is 90 degrees rotated from nuScenes lidar frame? If it is, what should I do to revise this error? Second, Centerpoint is a two-stage detector and I do not know if current reimplementation has achieved this?
Below is my config borrowed from SECOND and CENTERPOINT. In the meanwhile, I removed the velocity params in the model setting.
voxel_size = [0.05, 0.05, 0.1]
point_cloud_range=[0, -40, -3, 70.4, 40, 1]
# point_cloud_range = [0, -39.68, -3, 69.12, 39.68, 1]
model = dict(
    type='CenterPoint',
    pts_voxel_layer=dict(
        max_num_points=5, voxel_size=voxel_size, max_voxels=(16000, 40000),point_cloud_range=point_cloud_range),
    pts_voxel_encoder=dict(type='HardSimpleVFE', num_features=4),  ##Voxel feature encoder [voxel_num, num_per_v, num_features]->[voxel_num, num_features]
    pts_middle_encoder=dict(
        type='SparseEncoder',
        in_channels=4,
        sparse_shape=[41, 1600, 1408],
        output_channels=128,
        order=('conv', 'norm', 'act'),
        encoder_channels=((16, 16, 32), (32, 32, 64), (64, 64, 128), (128,
                                                                      128)),
        encoder_paddings=((0, 0, 1), (0, 0, 1), (0, 0, [0, 1, 1]), (0, 0)),
        block_type='basicblock'), ### return [N, C * D, H, W]
    pts_backbone=dict(
        type='SECOND',
        in_channels=256,
        out_channels=[128, 256],
        layer_nums=[5, 5],
        layer_strides=[1, 2],
        norm_cfg=dict(type='BN', eps=1e-3, momentum=0.01),
        conv_cfg=dict(type='Conv2d', bias=False)),
    pts_neck=dict(
        type='SECONDFPN',
        in_channels=[128, 256],
        out_channels=[256, 256],
        upsample_strides=[1, 2],
        norm_cfg=dict(type='BN', eps=1e-3, momentum=0.01),
        upsample_cfg=dict(type='deconv', bias=False),
        use_conv_for_no_stride=True),
    pts_bbox_head=dict(
        type='CenterHead',
        in_channels=sum([256, 256]),
        tasks=[
            dict(num_class=1, class_names=['Car']),
            dict(num_class=1, class_names=['Pedestrian']),
            dict(num_class=1, class_names=['Cyclist']),
        ],
        common_heads=dict(
            reg=(2, 2), height=(1, 2), dim=(3, 2), rot=(2, 2)),
        share_conv_channel=64,
        bbox_coder=dict(
            type='CenterPointBBoxCoder',
            post_center_range=point_cloud_range,
            max_num=100,
            score_threshold=0.1,
            out_size_factor=8,
            voxel_size=voxel_size[:2],
            code_size=7,
			pc_range=point_cloud_range[:2],
            ),
        separate_head=dict(
            type='SeparateHead', init_bias=-2.19, final_kernel=3),
        loss_cls=dict(type='GaussianFocalLoss', reduction='mean'),
        loss_bbox=dict(type='L1Loss', reduction='mean', loss_weight=0.25),
        norm_bbox=True),
    # model training and testing settings
    train_cfg=dict(

        pts=dict(
			point_cloud_range=point_cloud_range,
            grid_size=[1408, 1600, 40],
            voxel_size=voxel_size,
            out_size_factor=8,
            dense_reg=1,
            gaussian_overlap=0.1,
            max_objs=500,
            min_radius=2,
            code_weights=[1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0, 1.0])),
    test_cfg=dict(
        pts=dict(
			point_cloud_range=point_cloud_range,
            post_center_limit_range=point_cloud_range,
            max_per_img=500,
            max_pool_nms=False,
            min_radius=[4, 12, 10, 1, 0.85, 0.175],
            score_threshold=0.1,
            out_size_factor=4,
            voxel_size=voxel_size[:2],
            nms_type='rotate',
            pre_max_size=4096,
            post_max_size=512,
            nms_thr=0.2)))

dataset_type = 'KittiDataset'
data_root = 'data/kitti/'
class_names = ['Pedestrian','Cyclist','Car']

input_modality = dict(use_lidar=True, use_camera=False)
db_sampler = dict(
    data_root=data_root,
    info_path=data_root + 'kitti_dbinfos_train.pkl',
    rate=1.0,
    prepare=dict(
        filter_by_difficulty=[-1],
        filter_by_min_points=dict(Car=5, Pedestrian=10, Cyclist=10)),
    classes=class_names,
    sample_groups=dict(Car=12, Pedestrian=10, Cyclist=10))

file_client_args = dict(backend='disk')
train_pipeline = [
    dict(
        type='LoadPointsFromFile',
        coord_type='LIDAR',
        load_dim=4,
        use_dim=4,
        file_client_args=file_client_args),
    dict(
        type='LoadAnnotations3D',
        with_bbox_3d=True,
        with_label_3d=True,
        file_client_args=file_client_args),
    dict(type='ObjectSample', db_sampler=db_sampler),
    dict(
        type='ObjectNoise',
        num_try=100,
        translation_std=[1.0, 1.0, 0.5],
        global_rot_range=[0.0, 0.0],
        rot_range=[-0.78539816, 0.78539816]),
    dict(type='RandomFlip3D', flip_ratio_bev_horizontal=0.5),
    dict(
        type='GlobalRotScaleTrans',
        rot_range=[-0.78539816, 0.78539816],
        scale_ratio_range=[0.95, 1.05]),
    dict(type='PointsRangeFilter', point_cloud_range=point_cloud_range),
    dict(type='ObjectRangeFilter', point_cloud_range=point_cloud_range),
    dict(type='PointShuffle'),
    dict(type='DefaultFormatBundle3D', class_names=class_names),
    dict(type='Collect3D', keys=['points', 'gt_bboxes_3d', 'gt_labels_3d'])
]
test_pipeline = [
    dict(
        type='LoadPointsFromFile',
        coord_type='LIDAR',
        load_dim=4,
        use_dim=4,
        file_client_args=file_client_args),
    dict(
        type='MultiScaleFlipAug3D',
        img_scale=(1333, 800),
        pts_scale_ratio=1,
        flip=False,
        transforms=[
            dict(
                type='GlobalRotScaleTrans',
                rot_range=[0, 0],
                scale_ratio_range=[1., 1.],
                translation_std=[0, 0, 0]),
            dict(type='RandomFlip3D'),
            dict(
                type='PointsRangeFilter', point_cloud_range=point_cloud_range),
            dict(
                type='DefaultFormatBundle3D',
                class_names=class_names,
                with_label=False),
            dict(type='Collect3D', keys=['points'])
        ])
]
# construct a pipeline for data and gt loading in show function
# please keep its loading function consistent with test_pipeline (e.g. client)
eval_pipeline = [
    dict(
        type='LoadPointsFromFile',
        coord_type='LIDAR',
        load_dim=4,
        use_dim=4,
        file_client_args=file_client_args),
    dict(
        type='DefaultFormatBundle3D',
        class_names=class_names,
        with_label=False),
    dict(type='Collect3D', keys=['points'])
]

data = dict(
    samples_per_gpu=8,
    workers_per_gpu=4,
    train=dict(
        type='RepeatDataset',
        times=1,
        dataset=dict(
            type=dataset_type,
            data_root=data_root,
            ann_file=data_root + 'kitti_infos_train.pkl',
            split='training',
            pts_prefix='velodyne_reduced',
            pipeline=train_pipeline,
            modality=input_modality,
            classes=class_names,
            test_mode=False,
            # we use box_type_3d='LiDAR' in kitti and nuscenes dataset
            # and box_type_3d='Depth' in sunrgbd and scannet dataset.
            box_type_3d='LiDAR')),
    val=dict(
        type=dataset_type,
        data_root=data_root,
        ann_file=data_root + 'kitti_infos_val.pkl',
        split='training',
        pts_prefix='velodyne_reduced',
        pipeline=test_pipeline,
        modality=input_modality,
        classes=class_names,
        test_mode=True,
        box_type_3d='LiDAR'),
    test=dict(
        type=dataset_type,
        data_root=data_root,
        ann_file=data_root + 'kitti_infos_val.pkl',
        split='training',
        pts_prefix='velodyne_reduced',
        pipeline=test_pipeline,
        modality=input_modality,
        classes=class_names,
        test_mode=True,
        box_type_3d='LiDAR'))

evaluation = dict(interval=1, pipeline=eval_pipeline)

optimizer = dict(type='AdamW', lr=0.001, betas=(0.95, 0.99), weight_decay=0.01)
# optimizer = dict(type='Adam', lr=0.0002, betas=(0.9, 0.99), weight_decay=0.0001)
optimizer_config = dict(grad_clip=dict(max_norm=35, norm_type=2))

lr_config = dict(
    policy='cyclic',
    target_ratio=(10, 0.0001),
    cyclic_times=1,
    step_ratio_up=0.4)

momentum_config = dict(
    policy='cyclic',
    target_ratio=(0.8947368421052632, 1),
    cyclic_times=1,
    step_ratio_up=0.4)
runner = dict(type='EpochBasedRunner', max_epochs=80)

checkpoint_config = dict(interval=1)
log_config = dict(
    interval=50,
    hooks=[dict(type='TextLoggerHook'),
           dict(type='TensorboardLoggerHook')])
dist_params = dict(backend='nccl')
log_level = 'INFO'
work_dir = './work_dirs/centerpoint_kitti'
load_from = None
resume_from = None
workflow = [('train', 1)]
gpu_ids = range(0, 1)

Also, I am eager for your official implementation.

As your detection performance is reasonable, I guess there are some problems with the direction class setting, i.e., only the direction class is incorrect in your case. The overall performance is almost good enough. According to the implementation provided by the CenterPoint's authors, the one-stage CenterPoint should achieve the similar result with SECOND. You can refer to this repo.

Adding to the point, I think there are something different in mmdet3d's implementation and the aos will be better if you apply some transform to the rotation output (add 90 degree or sth, I don't remember exactly). Additionally, you can just ignore the aos number and only care about ap.
regarding two stage, you can see my comments here https://github.com/tianweiy/CenterPoint-KITTI/issues/20

I have meet same things before when I try to training centerpoint in KITTI dataset, and I find the roty of KITTI dataloader is different from centerpoint_head . You can just add pi in centerpoint_head.py file and aos will be fine.

Close due to inactivity. Feel free to reopen it if you have any further questions.

Traceback (most recent call last):
File "train.py", line 202, in
main()
File "train.py", line 116, in main
model = build_network(model_cfg=cfg.MODEL, num_class=len(cfg.CLASS_NAMES), dataset=train_set)
File "../pcdet/models/init.py", line 18, in build_network
model_cfg=model_cfg, num_class=num_class, dataset=dataset
File "../pcdet/models/detectors/init.py", line 30, in build_detector
model_cfg=model_cfg, num_class=num_class, dataset=dataset
File "../pcdet/models/detectors/centerpoint.py", line 7, in init
self.module_list = self.build_networks()
File "../pcdet/models/detectors/detector3d_template.py", line 47, in build_networks
model_info_dict=model_info_dict
File "../pcdet/models/detectors/detector3d_template.py", line 136, in build_dense_head
voxel_size=model_info_dict.get('voxel_size', False)
File "../pcdet/models/dense_heads/center_head.py", line 66, in init
[self.class_names.index(x) for x in cur_class_names if x in class_names]
RuntimeError: CUDA error: out of memory
Hello，I tried to use it on openpcdet, but I encountered an error. Can you give me some suggestions
base on GTX3070 cuda11.1 pytorch1.8.2


Run calico cni on docker desktop kubernetes

In order to explore network policies I require a CNI within kubernetes that runs on docker desktop.
I have tried to install calico through the following command:
kubectl apply -f https://docs.projectcalico.org/manifests/calico.yaml
Expected Behavior

Calico up and running, able to apply network policies.
Current Behavior

I get the error:
Error: failed to start container "mount-bpffs": Error response from daemon: path /sys/fs is mounted on /sys but it is not a shared mount
Your Environment

Calico version: 3.26.1
Orchestrator version (e.g. kubernetes, mesos, rkt): docker desktop kubernetes windows v4.23.0
Operating System and version: Windows 11 Enterprise    Version	10.0.22621 Build 22621

I'm not too surprised it's not working on Docker desktop, as it's not a platform we test on or expect to be used in production. You'll need to make sure the correct kernel, mounts, etc are in use. Docker desktop isn't one of our supported platforms so I'm afraid we can't provide too much help here, other than suggesting to investigate how to configure the necessary mounts in a Docker Desktop environment - ultimately Docker Desktop is using a VM under the covers, to ensuring that VM meets Calico's requirements is necessary.


Request: Do not overwrite existing files unless explicitly allowed.

Currently, if a duplicate file already exists for a download requested by Mist, the download will start and the duplicate file will be deleted/overwritten when the download is complete.
Since overwriting files without warning is not generally the expected behavior on macOS, I think it would make sense for Mist to check if any duplicate files exist (other than temporary files which should be deleted without warning), and exit with an error before starting a download.
For the user to explicitly allow overwriting existing files, a -f, --force argument could be added which would allow Mist to delete and overwrite any and all necessary files to get the requested job done.

I agree it would improve the experience if users can optionally overwrite generated file(s), with mist defaulting to failing / exiting if an existing file is found and the --force flag is not supplied.


[SPARK-22291][SQL] Conversion error when transforming array types of uuid, inet and cidr to StingType in PostgreSQL

What changes were proposed in this pull request?
This PR fixes the conversion error when transforming array types of uuid, inet and cidr to StingType in PostgreSQL.
How was this patch tested?
Added test in PostgresIntegrationSuite.

cc @cloud-fan, the follow-up PR for 2.2, thanks!

Test build #83200 has started for PR 19604 at commit 549cb81.

Test build #83201 has started for PR 19604 at commit 995e38e.

I found in this branch the Docker-based integration will fail due to can not pull the image wnameless/oracle-xe-11g:14.04.4, should we move on to wnameless/oracle-xe-11g?
Error response from daemon: manifest for wnameless/oracle-xe-11g:14.04.4 not found

Ah, let's remove [FOLLOWUP] or replace it to something like [BRANCH-2.2] in the PR title.

Test build #83200 has finished for PR 19604 at commit 549cb81.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83200/
Test PASSed.

Test build #83201 has finished for PR 19604 at commit 995e38e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

LGTM

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83201/
Test PASSed.

Merged build finished. Test PASSed.

thanks, merging to 2.2!

can you close it? PR merged to non-master branch will not be closed automatically. thanks

Sure, I'll close it and thank you and @viirya.


Correct attributes for spells not being assigned for display

When assigning attributes there seem to be two places the values can be set. in FUItem.system.accuracy.attributes.(primary|secondary), and also in FuItem.system.rollInfo.attributes.(primary|secondary).
The value from the dropdown selection correctly is assigned to the rollInfo, so the spell works while rolling. But the values in accuracy don't seem to be properly set, so the display of what attributes are selected is incorrect in the character info.
I don't know why there are two places it can be found, but I assume if you just change attackAttributes in getSpellDisplayData to use the data from rollInfo it will be solved?

My bad,
Spells uses
check.primary = item.system.rollInfo.attributes.primary.value;
check.secondary = item.system.rollInfo.attributes.secondary.value;
Weapons uses
check.primary = item.system.attributes.primary.value;
check.secondary = item.system.attributes.secondary.value;
Fixed the display issue, it should roll and display the correct die in the next alpha release

thank you!


[bug] Screen Recording randomly stops working

describe the bug
Screenpipe Screen Recording status is stale, hasn't updated in over a day.
to reproduce

Open the app
Red status light
Stale screen recording status

expected behavior
It shouldnt be stale
system info

os: macos 14.6
screenpipe version: latest

additional context
Audio and UI monitoring is green
I've tried the troubleshoot options

can you share logs?

@louis030195 Nothing noteworthy in the logs.

When I open the recorder logs, again, nothing noteworthy.
I've restarted the app, installed updates, restarted my computer.

@louis030195 Screenpipe is basically completely unusable for me at this point since recording is still not working since the 14th. I've tried quitting all my apps and background apps, but still no luck.

2024-11-18T13:18:32.769646Z  INFO screenpipe_server::resource_monitor: Runtime: 10s, Total Memory: 0% (0 GB / 131 GB), Total CPU: 0%, NPU: N/A
2024-11-18T13:18:37.606470Z  INFO screenpipe_audio::core: device: "MacBook Pro Microphone (input)"
2024-11-18T13:18:37.698534Z  INFO screenpipe_audio::core: starting continuous recording for MacBook Pro Microphone (input) (30s segments)
2024-11-18T13:18:42.855219Z  INFO screenpipe_server::resource_monitor: Runtime: 20s, Total Memory: 0% (0 GB / 131 GB), Total CPU: 2%, NPU: N/A
2024-11-18T13:18:52.946539Z  INFO screenpipe_server::resource_monitor: Runtime: 30s, Total Memory: 0% (0 GB / 131 GB), Total CPU: 3%, NPU: N/A
2024-11-18T13:19:03.036477Z  INFO screenpipe_server::resource_monitor: Runtime: 40s, Total Memory: 0% (0 GB / 131 GB), Total CPU: 3%, NPU: N/A
2024-11-18T13:19:07.713514Z  INFO screenpipe_audio::stt: device: MacBook Pro Microphone (input), resampling from 48000 Hz to 16000 Hz
2024-11-18T13:19:07.780833Z  INFO screenpipe_audio::stt: device: MacBook Pro Microphone (input), total audio frames processed: 300, frames that include speech: 0, speech duration: 0ms, speech ratio: 0.00, min required ratio: 0.20
2024-11-18T13:19:07.834361Z  INFO screenpipe_server::core: device MacBook Pro Microphone (input) received transcription Some("")
2024-11-18T13:19:07.834409Z  INFO screenpipe_server::core: device MacBook Pro Microphone (input) inserting audio chunk: ""
2024-11-18T13:19:13.126756Z  INFO screenpipe_server::resource_monitor: Runtime: 50s, Total Memory: 0% (0 GB / 131 GB), Total CPU: 4%, NPU: N/A
2024-11-18T16:34:23.110085Z  INFO screenpipe_server::resource_monitor: Runtime: 10s, Total Memory: 0% (0 GB / 131 GB), Total CPU: 0%, NPU: N/A
2024-11-18T16:34:27.955876Z  INFO screenpipe_audio::core: device: "MacBook Pro Microphone (input)"
2024-11-18T16:34:28.044708Z  INFO screenpipe_audio::core: starting continuous recording for MacBook Pro Microphone (input) (30s segments)
2024-11-18T16:34:33.201779Z  INFO screenpipe_server::resource_monitor: Runtime: 20s, Total Memory: 0% (0 GB / 131 GB), Total CPU: 2%, NPU: N/A
2024-11-18T16:34:43.291469Z  INFO screenpipe_server::resource_monitor: Runtime: 30s, Total Memory: 0% (0 GB / 131 GB), Total CPU: 3%, NPU: N/A
2024-11-18T16:34:53.380466Z  INFO screenpipe_server::resource_monitor: Runtime: 40s, Total Memory: 0% (0 GB / 131 GB), Total CPU: 3%, NPU: N/A
2024-11-18T16:34:58.051242Z  INFO screenpipe_audio::stt: device: MacBook Pro Microphone (input), resampling from 48000 Hz to 16000 Hz
2024-11-18T16:34:58.108263Z  INFO screenpipe_audio::stt: device: MacBook Pro Microphone (input), total audio frames processed: 300, frames that include speech: 0, speech duration: 0ms, speech ratio: 0.00, min required ratio: 0.20
2024-11-18T16:34:58.196852Z  INFO screenpipe_server::core: device MacBook Pro Microphone (input) received transcription Some("")
2024-11-18T16:34:58.196894Z  INFO screenpipe_server::core: device MacBook Pro Microphone (input) inserting audio chunk: ""
2024-11-18T17:59:42.015046Z  INFO screenpipe_server::resource_monitor: Runtime: 4856s, Total Memory: 1% (1 GB / 131 GB), Total CPU: 4%, NPU: N/A

Restarted server and got these logs:
2024-11-18T18:00:49.177097Z  INFO screenpipe_server::resource_monitor: Runtime: 10s, Total Memory: 0% (0 GB / 131 GB), Total CPU: 0%, NPU: N/A
2024-11-18T18:00:55.027343Z  INFO screenpipe: screenpipe already in PATH at: /opt/homebrew/bin/screenpipe
2024-11-18T18:00:55.027372Z  INFO screenpipe: screenpipe is available and properly set in the PATH
                                        _

__________________  ___  ____     ____  (_____  ___
/ / / / _ / _ / __ \   / __ / / __ / _
(  / // /  /  __/  __/ / / /  / // / / // /  __/
//___//   _/_// //  / .// ./__/
//     //
build ai apps that have the full context
open source | runs locally | developer friendly
┌─────────────────────┬────────────────────────────────────┐
│ setting             │ value                              │
├─────────────────────┼────────────────────────────────────┤
│ fps                 │ 0.2                                │
│ audio chunk duration│ 30 seconds                         │
│ video chunk duration│ 60 seconds                         │
│ port                │ 3030                               │
│ audio disabled      │ false                              │
│ vision disabled     │ false                              │
│ save text files     │ false                              │
│ audio engine        │ WhisperDistilLargeV3               │
│ ocr engine          │ AppleNative                        │
│ vad engine          │ Silero                             │
│ vad sensitivity     │ High                               │
│ data directory      │ /Users/davidmcgregor/.screenpipe   │
│ debug mode          │ false                              │
│ telemetry           │ true                               │
│ local llm           │ false                              │
│ use pii removal     │ false                              │
│ ignored windows     │ ["bit", ".env", "Item-0", "App ... │
│ included windows    │ []                                 │
│ friend wearable uid │ not set                            │
│ ui monitoring       │ true                               │
│ frame cache         │ true                               │
├─────────────────────┼────────────────────────────────────┤
│ languages           │                                    │
│                     │ all languages                      │
├─────────────────────┼────────────────────────────────────┤
│ monitors            │                                    │
│                     │ id: 1                              │
├─────────────────────┼────────────────────────────────────┤
│ audio devices       │                                    │
│                     │ MacBook Pro Microphone (input)     │
├─────────────────────┼────────────────────────────────────┤
│ pipes               │                                    │
│                     │ no pipes available                 │
└─────────────────────┴────────────────────────────────────┘
you are using local processing. all your data stays on your computer.
warning: telemetry is enabled. only error-level data will be sent to highlight.io.
to disable, use the --disable-telemetry flag.
2024-11-18T18:00:55.327072Z  INFO screenpipe: watching pid 12010 for auto-destruction
2024-11-18T18:00:55.327223Z ERROR screenpipe_vision::core: Failed to get monitor with id: 1. Exiting continuous_capture.
2024-11-18T18:00:55.327379Z  INFO screenpipe_server::server: Server starting on <IP_ADDRESS>:3030
2024-11-18T18:00:55.327484Z  INFO screenpipe_vision::run_ui_monitoring_macos: starting ui monitoring...
2024-11-18T18:00:55.334903Z  INFO screenpipe_audio::whisper: device = Metal(MetalDevice(DeviceId(1)))
2024-11-18T18:00:55.637380Z  INFO screenpipe_audio::vad_engine: Initializing SileroVad...
2024-11-18T18:00:55.637451Z  INFO screenpipe_audio::vad_engine: SileroVad Model downloaded to: "/Users/davidmcgregor/Library/Caches/screenpipe/vad/silero_vad.onnx"
2024-11-18T18:00:55.637830Z  WARN screenpipe_vision::run_ui_monitoring_macos: ui monitoring error: /var/folders/b6/wfw4c_8j50q6h2_9z7j4xlqw0000gn/T/ui_monitoring_macos.swift:548:13: warning: will never be executed
2024-11-18T18:00:55.637840Z  WARN screenpipe_vision::run_ui_monitoring_macos: ui monitoring error:             if hasRelevantValue {
2024-11-18T18:00:55.637865Z  WARN screenpipe_vision::run_ui_monitoring_macos: ui monitoring error:             ^
2024-11-18T18:00:58.108667Z  INFO screenpipe_server::server: streaming frames from 2024-11-18 05:01:00 UTC to 2024-11-18 17:58:39.059 UTC
2024-11-18T18:01:05.462662Z  INFO

@louis030195  looks like it was the ui monitoring that was breaking things. I thought I turned it off, but I guess I needed to click the save and restart button.

@louis030195
It still happens randomly. Today it turned off a few times.  UI monitoring was off the whole time.


Add farsi translation package

Please insert your language in the alphabetical order of language lists.

@fzaninotto Done.

Thanks!


Airco fan mode doesn't show auto but diffuse

As can be seen in below screenshot the option for auto mode (which is currently selected in the app) is shown as "diffuse" in Home assistant. I guess this is some sort of mis-mapping of status.

Also in the App I can only select low, medium and high speed. So not sure what LOW_MID and MID_HIGH will do.

Diffuse is mapped to the mode Nature returned by device, the scope is to differentiate from the mode Auto returned by other devices. Because LG provide both mode in the list (auto and diffuse) I need to map the 2 modes in different mode. The other to modes are also returned by API, if they do nothing just ignore them.


Return 500 on error for create project

Wrap call-sql "create_project" in a try/catch
Return error and 500 if error in create_project

If ok I'll proceed with the other handlers.


register functionality for local user

node_modules ??

Reply to this email directly, view it on GitHub
https://github.com/xoperations/api/pull/9, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAh0xzq5eyx8W3FKtX-gGlQr28E7vbFvks5sDmyugaJpZM4N4VGO
.

Hi Gayantha
node_modules folder should be in the git-ignore list.As  the modules were
already in the branch i added the new npm modules for that as well.
i understand there is no need for that as they are defined in the
package.json .
On Tue, Jun 13, 2017 at 4:51 PM, Gayantha<EMAIL_ADDRESS>wrote:

node_modules ??

Reply to this email directly, view it on GitHub
https://github.com/xoperations/api/pull/9, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAh0xzq5eyx8W3FKtX-
gGlQr28E7vbFvks5sDmyugaJpZM4N4VGO>
.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/xoperations/api/pull/9#issuecomment-308085631, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ANeN78M3XVWU0mpCUhh9aKwsjFAXs1Zxks5sDnC7gaJpZM4N4VGO
.


Query over two time windows does not work as expected

From @salsh  on Jan 23, 2018
If a query is made over two time windows, it does not always work as expected. The expected result should be processing through both time windows one after the other if the necessary BGP data are available, right?
The following query works as expected:
bgpreader -t updates -p ris -c rrc00 -w<PHONE_NUMBER>,1502352100 -w<PHONE_NUMBER>,1502353100
The following query ends after the first time window although there are BGP data for the second time window:
bgpreader -t updates -p ris -c rrc00 -w<PHONE_NUMBER>,1502340100 -w<PHONE_NUMBER>,1502350100
I hope the potential bug only applies to this version. I am very much looking forward to the next release.
Copied from original issue: CAIDA/bgpstream#57

This issue still exist in the current build.
Two windows -w<PHONE_NUMBER>,1502340100 -w<PHONE_NUMBER>,1502350100 output ends at the end of the first window (reversing the windows order gets you the same output).
vagrant@ubuntu-xenial:~/libbgpstream/tools$ ./bgpreader -t updates -p ris -c rrc00 -w<PHONE_NUMBER>,1502340100 -w<PHONE_NUMBER>,1502350100|tail
U|A|1502340100.000000|ris|rrc00|||8758|2001:8e0:0:ffff::9|2804:2e78::/32|2001:8e0:0:ffff::9|8758 8220 6939 28329 28213|28213|8220:65030 8220:65401 8758:110 8758:300||
U|A|1502340100.000000|ris|rrc00|||8758|2001:8e0:0:ffff::9|2a04:c45::/32|2001:8e0:0:ffff::9|8758 8220 8447 61098|61098|8220:65090 8220:65401 8758:110 8758:300||
U|A|1502340100.000000|ris|rrc00|||8758|2001:8e0:0:ffff::9|2804:7d0::/32|2001:8e0:0:ffff::9|8758 8220 6939 28329 262324|262324|8220:65030 8220:65401 8758:110 8758:300||
U|A|1502340100.000000|ris|rrc00|||8758|2001:8e0:0:ffff::9|2804:ee4::/32|2001:8e0:0:ffff::9|8758 8220 6939 28329 263557|263557|8220:65030 8220:65401 8758:110 8758:300||
U|A|1502340100.000000|ris|rrc00|||8758|2001:8e0:0:ffff::9|2804:2cc::/32|2001:8e0:0:ffff::9|8758 8220 6939 28329 262839|262839|8220:65030 8220:65401 8758:110 8758:300||
U|A|1502340100.000000|ris|rrc00|||8758|2001:8e0:0:ffff::9|2804:167c::/32|2001:8e0:0:ffff::9|8758 8220 6939 28329 263288|263288|8220:65030 8220:65401 8758:110 8758:300||
U|A|1502340100.000000|ris|rrc00|||8758|<IP_ADDRESS>|<IP_ADDRESS>/23|<IP_ADDRESS>|8758 8220 6939 16735 263629|263629|8220:65110 8220:65401 8758:110 8758:300||
U|A|1502340100.000000|ris|rrc00|||8758|<IP_ADDRESS>|<IP_ADDRESS>/22|<IP_ADDRESS>|8758 6830 16735 263629|263629|6830:16000 6830:16236 6830:23001 6830:35307 16735:6061 16735:7000 16735:7001 8758:110 8758:300||
U|A|1502340100.000000|ris|rrc00|||1836|2a01:2a8::3|2804:21c4::/32|2a01:2a8::3|1836 6939 16735<PHONE_NUMBER>72|264572|1836:120 1836:3100 1836:3110||
U|A|1502340100.000000|ris|rrc00|||1836|2a01:2a8::3|2804:104c::/32|2a01:2a8::3|1836 6939 16735 263629|263629|1836:120 1836:3100 1836:3110||

@digizeph did we remove multi-interval support?

@alistairking yes, we removed it in PR #47 .

thanks. i’ll close this then.


(local) ISDF module in PySCF

Local Interpolative separable density fitting module for PBC in PySCF together with an experimental module for THC-post-HF methods.
Supporting robust fitting, k-point, MPI.
Add new files in pyscf/lib/pbc to support ISDF
Changes on pyscf/lib/numpy_helper.py to remove unnecessary copy when doing dgemm.
Changes on pyscf/scf/hf.py to support occ-RI-K.

Exciting!!!!
I wonder what can be done about the fact that the Apache 2.0 and GPL 3.0 licenses are incompatible. That may lead to a license problem when making FFTW a required dependency, because then pyscf binaries cannot be distributed. So maybe an FFT wrapper is needed?
Some options:

Intel MKL has an FFTW3 interface.
Use pocketfft like SciPy. PocketFFT has both C and C++ versions. Do they have the same performance?

Hi @NingZhang1 , these PRs should probably be staying in a local fork for now while you're still developing ISDF. If there are features that are finished and ready to merge, they can be separated into a standalone PR so that we don't have to review 450 commits and 150+ files changed. And if the features are very new, we may ask that the PR first go to pyscf-forge for testing before being incorporated into the main pyscf distribution.

Hi Timothy,
Sorry for updating such a large PR. Thanks for suggestions. I am preparing
a more clean branch for update, which will contain the most stable features
that have been fully tested (by myself) and ready to merge. I agree that it
is better to first merge it into pyscf-forge beforeing incorportated into
the main pyscf distribution.
Best wishes,
Ning
Timothy Berkelbach @.***> 于2024年7月25日周四 10:19写道：

Hi @NingZhang1 https://github.com/NingZhang1 , these PRs should
probably be staying in a local fork for now while you're still developing
ISDF. If there are features that are finished and ready to merge, they can
be separated into a standalone PR so that we don't have to review 450
commits and 150+ files changed. And if the features are very new, we may
ask that the PR first go to pyscf-forge for testing before being
incorporated into the main pyscf distribution.
—
Reply to this email directly, view it on GitHub
https://github.com/pyscf/pyscf/pull/2314#issuecomment-2251020486, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AHJIAW7OVZM5OOPTMY2BOCLZOEXRHAVCNFSM6AAAAABKX3RZEGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJRGAZDANBYGY
.
You are receiving this because you were mentioned.Message ID:
@.***>


[BUGFIX] Fix wrong TYPO3 version

The Problem/Issue/Bug:
  [InvalidArgumentException]   Could not find package typo3/cms-base-distribution with version 9.
How this PR Solves The Problem:
Manual Testing Instructions:
Automated Testing Overview:

Related Issue Link(s):
Release/Deployment notes:

Hmm, the ^9 still comes directly from https://composer.typo3.org/
And I still had no trouble with it at all, maybe you can explain the actual problem. Was this perhaps a temporary issue with upstream packaging?
$ ddev composer create typo3/cms-base-distribution ^9 --no-interaction --prefer-dist
Building ddev-ssh-agent
Recreating ddev-ssh-agent ... done

ssh-agent container is running: If you want to add authentication to the ssh-agent container, run 'ddev auth ssh' to enable your keys.
Building db
Building web
Creating ddev-junk-db ... done
Creating ddev-junk-web ... done
Creating ddev-junk-dba ... done

Recreating ddev-router ... done

Warning: ALL EXISTING CONTENT of the project root (/Users/rfay/workspace/junk) will be deleted
Would you like to continue? [Y/n] (yes):
Removing any existing files in project root
Executing composer command: composer create-project typo3/cms-base-distribution /var/www/html/.tmp_ddev_composer_create_wBBKTv ^9 --no-interaction --prefer-dist

Installing typo3/cms-base-distribution (v9.5.0)
  - Installing typo3/cms-base-distribution (v9.5.0): Loading from cache
Created project in /var/www/html/.tmp_ddev_composer_create_wBBKTv
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 74 installs, 0 updates, 0 removals
  - Installing typo3/cms-composer-installers (v2.2.2): Loading from cache
  - Installing typo3/class-alias-loader (1.0.1): Loading from cache
  - Installing helhum/typo3-console-plugin (v2.0.5): Loading from cache
  - Installing typo3fluid/fluid (2.6.2): Downloading (100%)
  - Installing typo3/phar-stream-wrapper (v3.1.2): Loading from cache
  - Installing typo3/cms-cli (2.0.0): Loading from cache
  - Installing symfony/polyfill-ctype (v1.12.0): Loading from cache
  - Installing symfony/yaml (v4.3.4): Downloading (100%)
  - Installing symfony/routing (v4.3.4): Downloading (100%)
  - Installing symfony/polyfill-mbstring (v1.12.0): Loading from cache
  - Installing symfony/polyfill-php72 (v1.12.0): Loading from cache
  - Installing symfony/polyfill-intl-idn (v1.12.0): Loading from cache
  - Installing symfony/intl (v4.3.4): Downloading (100%)
  - Installing symfony/polyfill-intl-icu (v1.12.0): Loading from cache
  - Installing symfony/finder (v4.3.4): Loading from cache
  - Installing psr/container (1.0.0): Loading from cache
  - Installing symfony/service-contracts (v1.1.6): Loading from cache
  - Installing psr/cache (1.0.1): Loading from cache
  - Installing symfony/var-exporter (v4.3.4): Downloading (100%)
  - Installing symfony/cache-contracts (v1.1.5): Loading from cache
  - Installing psr/log (1.0.2): Loading from cache
  - Installing symfony/cache (v4.3.4): Downloading (100%)
  - Installing symfony/expression-language (v4.3.4):Downloading (100%)         )
  - Installing symfony/polyfill-php73 (v1.12.0): Loading from cache
  - Installing symfony/console (v4.3.4): Downloading (100%)
  - Installing swiftmailer/swiftmailer (v5.4.12): Loading from cache
  - Installing psr/http-message (1.0.1): Loading from cache
  - Installing psr/http-server-handler (1.0.1): Loading from cache
  - Installing psr/http-server-middleware (1.0.1): Loading from cache
  - Installing nikic/php-parser (v4.2.4): Downloading (100%)
  - Installing guzzlehttp/promises (v1.3.1): Loading from cache
  - Installing ralouphie/getallheaders (3.0.3): Loading from cache
  - Installing guzzlehttp/psr7 (1.6.1): Loading from cache
  - Installing guzzlehttp/guzzle (6.3.3): Loading from cache
  - Installing doctrine/lexer (1.1.0): Loading from cache
  - Installing doctrine/instantiator (1.2.0): Loading from cache
  - Installing doctrine/event-manager (v1.0.0): Loading from cache
  - Installing doctrine/cache (v1.8.0): Loading from cache
  - Installing doctrine/dbal (v2.9.2): Loading from cache
  - Installing doctrine/annotations (v1.7.0): Loading from cache
  - Installing cogpowered/finediff (0.3.1): Loading from cache
  - Installing algo26-matthias/idna-convert (v1.1.0): Loading from cache
  - Installing typo3/cms-core (v9.5.9): Loading from cache
  - Installing typo3/cms-recordlist (v9.5.9): Loading from cache
  - Installing typo3/cms-extbase (v9.5.9): Loading from cache
  - Installing typo3/cms-fluid (v9.5.9): Loading from cache
  - Installing typo3/cms-install (v9.5.9): Loading from cache
  - Installing typo3/cms-frontend (v9.5.9): Loading from cache
  - Installing typo3/cms-filelist (v9.5.9): Loading from cache
  - Installing typo3/cms-extensionmanager (v9.5.9): Loading from cache
  - Installing typo3/cms-backend (v9.5.9): Loading from cache
  - Installing typo3/minimal (v9.5.0)
  - Installing helhum/config-loader (v0.12.2): Loading from cache
  - Installing symfony/process (v4.3.4): Downloading (100%)
  - Installing typo3/cms-scheduler (v9.5.9): Loading from cache
  - Installing helhum/typo3-console (v5.7.2): Loading from cache
  - Installing typo3/cms-about (v9.5.9): Loading from cache
  - Installing typo3/cms-viewpage (v9.5.9): Loading from cache
  - Installing typo3/cms-tstemplate (v9.5.9): Loading from cache
  - Installing typo3/cms-t3editor (v9.5.9): Loading from cache
  - Installing typo3/cms-sys-note (v9.5.9): Loading from cache
  - Installing typo3/cms-seo (v9.5.9): Loading from cache
  - Installing typo3/cms-setup (v9.5.9): Loading from cache
  - Installing typo3/cms-rte-ckeditor (v9.5.9): Loading from cache
  - Installing typo3/cms-reports (v9.5.9): Loading from cache
  - Installing typo3/cms-redirects (v9.5.9): Loading from cache
  - Installing typo3/cms-info (v9.5.9): Loading from cache
  - Installing typo3/cms-impexp (v9.5.9): Loading from cache
  - Installing typo3/cms-form (v9.5.9): Loading from cache
  - Installing typo3/cms-fluid-styled-content (v9.5.9): Loading from cache
  - Installing typo3/cms-felogin (v9.5.9): Loading from cache
  - Installing typo3/cms-beuser (v9.5.9): Loading from cache
  - Installing typo3/cms-belog (v9.5.9): Loading from cache
  - Installing typo3/cms-adminpanel (v9.5.9): Loading from cache
symfony/routing suggests installing symfony/http-foundation (For using a Symfony Request object)
symfony/routing suggests installing symfony/config (For using the all-in-one router or any loader)
symfony/service-contracts suggests installing symfony/service-implementation
symfony/console suggests installing symfony/event-dispatcher
symfony/console suggests installing symfony/lock
guzzlehttp/psr7 suggests installing zendframework/zend-httphandlerrunner (Emit PSR-7 responses)
doctrine/cache suggests installing alcaeus/mongo-php-adapter (Required to use legacy MongoDB driver)
helhum/config-loader suggests installing ext-yaml (For improved performance when parsing yaml files you should use the PECL YAML Parser php extension)
Writing lock file
Generating autoload files
> typo3cms install:fixfolderstructure
> typo3cms install:generatepackagestates
Generating class alias map file
Inserting class alias loader into main autoload.php file
The following directory structure has been fixed:
Directory /typo3temp successfully created.
Fixed permission on /typo3temp.
File /typo3temp/index.html successfully created.
Set content to /typo3temp/index.html
Fixed permission on /typo3temp/index.html.
Directory /typo3temp/assets successfully created.
Fixed permission on /typo3temp/assets.
Directory /typo3temp/assets/compressed successfully created.
Fixed permission on /typo3temp/assets/compressed.
Directory /typo3temp/assets/css successfully created.
Fixed permission on /typo3temp/assets/css.
Directory /typo3temp/assets/js successfully created.
Fixed permission on /typo3temp/assets/js.
Directory /typo3temp/assets/images successfully created.
Fixed permission on /typo3temp/assets/images.
Directory /typo3temp/assets/_processed_ successfully created.
Fixed permission on /typo3temp/assets/_processed_.
Directory /typo3temp/var successfully created.
Fixed permission on /typo3temp/var.
File /typo3temp/var/.htaccess successfully created.
Set content to /typo3temp/var/.htaccess
Fixed permission on /typo3temp/var/.htaccess.
Directory /typo3temp/var/charset successfully created.
Fixed permission on /typo3temp/var/charset.
Directory /typo3temp/var/cache successfully created.
Fixed permission on /typo3temp/var/cache.
Directory /typo3temp/var/lock successfully created.
Fixed permission on /typo3temp/var/lock.
Directory /typo3conf successfully created.
Fixed permission on /typo3conf.
Directory /typo3conf/ext successfully created.
Fixed permission on /typo3conf/ext.
Directory /typo3conf/l10n successfully created.
Fixed permission on /typo3conf/l10n.
Directory /fileadmin successfully created.
Fixed permission on /fileadmin.
Directory /fileadmin/_temp_ successfully created.
Fixed permission on /fileadmin/_temp_.
File /fileadmin/_temp_/.htaccess successfully created.
Set content to /fileadmin/_temp_/.htaccess
Fixed permission on /fileadmin/_temp_/.htaccess.
File /fileadmin/_temp_/index.html successfully created.
Set content to /fileadmin/_temp_/index.html
Fixed permission on /fileadmin/_temp_/index.html.
Directory /fileadmin/user_upload successfully created.
Fixed permission on /fileadmin/user_upload.
Directory /fileadmin/user_upload/_temp_ successfully created.
Fixed permission on /fileadmin/user_upload/_temp_.
File /fileadmin/user_upload/_temp_/index.html successfully created.
Set content to /fileadmin/user_upload/_temp_/index.html
Fixed permission on /fileadmin/user_upload/_temp_/index.html.
Directory /fileadmin/user_upload/_temp_/importexport successfully created.
Fixed permission on /fileadmin/user_upload/_temp_/importexport.
File /fileadmin/user_upload/_temp_/importexport/.htaccess successfully created.
Set content to /fileadmin/user_upload/_temp_/importexport/.htaccess
Fixed permission on /fileadmin/user_upload/_temp_/importexport/.htaccess.
File /fileadmin/user_upload/_temp_/importexport/index.html successfully created.
Set content to /fileadmin/user_upload/_temp_/importexport/index.html
Fixed permission on /fileadmin/user_upload/_temp_/importexport/index.html.
File /fileadmin/user_upload/index.html successfully created.
Set content to /fileadmin/user_upload/index.html
Fixed permission on /fileadmin/user_upload/index.html.
The following extensions have been added to the generated PackageStates.php file: core, scheduler, extbase, fluid, frontend, fluid_styled_content, filelist, impexp, form, install, recordlist, backend, reports, setup, rte_ckeditor, about, adminpanel, belog, beuser, extensionmanager, felogin, info, redirects, seo, sys_note, t3editor, tstemplate, viewpage
Moving installation to project root

I did the same PR for the base dist see https://github.com/TYPO3/TYPO3.CMS.BaseDistribution/pull/19 and https://github.com/TYPO3/TYPO3.CMS.BaseDistribution/issues/10
The problem seems to be related to Windows and DDEV in normal Windows shell, I was able to reproduce the exception here.
Will talk to Helmut about this issue...

I'd say this can be closed: https://github.com/TYPO3/TYPO3.CMS.BaseDistribution/pull/19#issuecomment-530409648

Ah, I've never tried it except in git bash. Interesting.

I just tested ddev composer create typo3/cms-base-distribution "^9" --no-interaction --prefer-dist which works fine in a Windows shel. Git Bash and Power SHel don't have this issue on Windows

Other solution could be ddev composer create typo3/cms-base-distribution ^^9 --no-interaction --prefer-dist
Currently searching for an official docu of Microsoft without success. This I have found on excaping: https://www.robvanderwoude.com/escapechars.php

I made minor changes here to make it work best with current ddev, and offer the quotes where a ^ is involved. Would appreciate your review @gilbertsoft


[patch] fix lint in master

LGTM as a fix, though the code likely should be able to handle this case (e.g. for fresh builds).


Setting to return rows as dictionaries

Useful for some when returning values directly as JSON

Should this be a flag that causes all fetch calls to return dictionaries or a separate set of functions?

In my opion it would be undesirable to return real dictionaries because it doubles the code paths in pyodbc.  Would it not make more sense to extend pyODBC row functionality to support getitem['fieldname'] in addition to getitem[columno] and then provide a custom JSON encoder like below.

import json
class pyODBCEncoder(json.JSONEncoder):
...     def default(self, obj):
...         if isinstance(obj, pyodbc.Row):
...             return obj.to_json()
...         # Let the base class default method raise the TypeError
...         return json.JSONEncoder.default(self, obj)
...
dumps(myPyODBCRow, cls=pyODBCEncoder)

@Lexcon Good point, but Rows already support getitem.  Unfortunately that isn't enough to make the JSON encoder turn it into a JSON object.
This was a suggestion via email.  I wish I'd asked them to open the issue so they'd be in the conversation.
Another simple option, however, is for user's to wrap them.  I often do this for logging or debug purposes.  By wrapping the cursor from my db.connect() function (usually I have a db module in each project to consolidate connection handling).
I'll look at the JSON code again to see if there is something else that it might recognize that wouldn't double the code.  Also, Rows are somewhat optimized for space.

Hi guys,
I am creating dict like below.
result = []         column_names = [column[0] for column in cursor.description]         for row in data:             result.append(dict(zip(column_names, row)))
I am not 100% sure whether columns order is always same in both cursor.description and row.

yes, this would be a nice addition. (hello, I'm a pymssql refugee)

is there any progress with this?

Yep it would be nice to have this feature

I am facing a similar problem in one of my projects, I need to send the Nested JSON generated from the SQL Server database (using the FOR JSON Clause) via an API. Again since Row object is not JSON serializable, I need to convert it into Dict or List which ends up double encoding the JSON. Please let me know if you find a fix to this
But for simply converting the TSQL query output to JSON, the following code works just fine
columns = [column[0] for column in cursor.description] results = [] #Created a dictionary as it is JSON Serializable  for row in cursor.fetchall():    result = dict(zip(columns, row))    results.append(result)

This would be very handy. Consider a generic Flask route that should return a record fetched from pyodbc. Flask will automatically convert a returned dict to JSON, so it would be nice and clean to do something such as:
@app.route('/record/<key>')
def record_by_key(key):
    cx = pyodbc.connect('DSN=MYDSN')
    cursor = cx.cursor()

    #the odbc driver I use is obscure and has bugs with parameterized queries so using ? doesn't work reliably
    sql = """
        select * from my_table where key='{0}'
    """.format(key)

    cursor.execute(sql)

    row = cursor.fetchone(as_dict=True)

    return row

Checking to see if there's been any progress on this. I'm also migrating from pymssql, which has this feature.

Yes please. Rows as dictionaries. 👍


Navigating to http://localhost// causes a security exception

Originally from: https://github.com/reactjs/react-router/issues/3168
When attempting to set pathname to "//" you will receive a security error similar to the following:
Uncaught SecurityError: Failed to execute 'replaceState' on 'History': A history state object with URL 'http:' cannot be created in a document with origin 'http://localhost'.
This is because it attempts to push // onto the history, which is interpreted as a scheme-relative URL.

We should probably handle this on our side to keep consistent behavior between what happens with the History API and what happens when using the full refresh fallback.

So close this issue and reopen https://github.com/reactjs/react-router/issues/3168 ?

No – it still needs to be handled on the history side. Among other things, this limitation only arises with browser history (or other histories that use the HTML5 history API). It won't arise with hash history or memory history.
Among other things, history.push doesn't even go through any code in the router.

All I'm saying is we should probably just throw here if you try and push a path like that. So it's either we throw or the browser does.

Via an invariant, of course, so we can have an error message that gets stripped out for production builds :grinning:

I decided to handle this via a warning instead. We already warn about paths with protocols and/or domains attached. Protocol-relative URLs are just another case of the same problem.

The drawback with only warning is that it doesn't account for weird URLs linking to your app or site. So we've had to patch this issue in our wrapper around history.

@necolas What does your patch do? Do you try to guess the right URL and redirect?

This is what we do:
import { useRouterHistory } from 'react-router';
import createBrowserHistory from 'history/lib/createBrowserHistory';
import useScroll from '../scroll-behavior';

const REGEX_LEADING_SLASHES = /^\/\/+/;
/**
 * Fixes relative paths with multiple leading slashes
 */
export const fixProtocolRelativeUrls = (history, location) => {
  const { pathname, search, hash } = location;
  if (pathname && REGEX_LEADING_SLASHES.test(pathname)) {
    const normalizedPathname = pathname.replace(leadingSlashes, '/');
    const newPath = normalizedPathname + search + hash;
    history.replace(newPath);
  }
};

let history;
const _createBrowserHistory = () => {
  if (!history) {
    history = useScroll(useRouterHistory(createBrowserHistory));
    fixProtocolRelativeUrls(history, window.location);
  }
  return history;
};

export default _createBrowserHistory();


Wallet address, hovering it, should show the address

You should also be able to click it to copy?


SAK-32044 - Problems posting message in forums

From what I can tell with this code. The old pattern was to return (with the selectedForum) if the selectedForum was set at all.
However it's better if you give it a chance to try to look it up, and if it fails looking it up then return with the previous selected forum. This mostly retains the old logic that was there (and keeps forums from breaking) and also seems to give it a chance to update the breadcrumbs correctly as well.

LGTM


fix(#419) preserve body padding-right in removeScroll

#419
🍁🚬

Whoops I forgot to take into account the scrollbar being on the left.


Create documentation of KPOps components

Closes #76
Closes #120

I've split pipeline.yaml into components and found how to embed an external file into a page. Although automation is not an option right now, the files can be checked by the CI against the schema and updated manually if necessary.

that's an excellent point! Could you create a followup issue for the CI addition?

that's an excellent point! Could you create a followup issue for the CI addition?

Already did in #123, added a reference here now.


Set Sensitivity Fail

Description of the issue
Hello, I have several Xiaomi vibration sensors, but they all give error when I try to set the sensitivity
Addon version
V 1.26.0-1
Platform
OS: 8.2
Core : 2022.6.7
Supervisor : 2022.6.2
Coordinator : zStack3x0
Firmware : 20220219
Logs of the issue (if applicable)
2022-07-06 16:58:35Publish 'set' 'sensitivity' to 'Vibrazione_Tapparella_Porta_Finestra_Sala' failed: 'Error: Write 0x00158d0003d23063/1 genBasic({"65293":{"value":11,"type":32}}, {"sendWhen":"immediate","timeout":35000,"disableResponse":false,"disableRecovery":false,"disableDefaultResponse":true,"direction":0,"srcEndpoint":null,"reservedBits":0,"manufacturerCode":4447,"transactionSequenceNumber":null,"writeUndiv":false}) failed (Timeout - 8668 - 1 - 7 - 0 - 4 after 35000ms)'

Make sure to wake them up right before sending the command (press a button on the sensors)

Make sure to wake them up right before sending the command (press a button on the sensors)

Hello, I tried both to press the button (it is detected by the interface) and then change the sensitivity, and change the sensitivity and then press the button ... the error remains ... other ideas ?

Then it may be that the router it is connected to doesn't relay the message correctly. Repair the device very close to the coordinator such that it has a direct connection with it and try again.

Then it may be that the router it is connected to doesn't relay the message correctly. Repair the device very close to the coordinator such that it has a direct connection with it and try again.

Ok, turning off the repeaters and pressing the button about 3/4 times (with 1 second of scrap) they took the configuration...thank you


Does unilm/e5 support deepspeed or other accelerator?

Describe
Model I am using (UniLM, MiniLM, LayoutLM ...):e5
Can I use deepspeed for evaluating beir benchmark? Or does it support other strategies?
Can I use fp16? Would it impact results?

Hi @mengyao00 ,

Can I use deepspeed for evaluating beir benchmark?

Currently we do not support using DeepSpeed for inference. I think the main advantage of DeepSpeed is about reducing training GPU memory usage. For inference, traditional data parallel is enough.

Can I use fp16? Would it impact results?

Yes, in fact, our evaluation results are all based on fp16.