Feedback form not works

Please update it. composer update

i updated composer but not works.

tested and works. but can be shown an success message after feedback send event.


VNI Selection improvement for interdomain

Signed-off-by: Artem Belov<EMAIL_ADDRESS>Description
Keep original src ip and external dst ip to compare ip addresses properly
Enable TestInterdomainVPNFirewallRemote which was broken because of VNI selection issue
Motivation and Context
#1695, #1354
How Has This Been Tested?

[ ] Covered by existing integration testing
[x] Added integration testing to cover
[ ] Tested locally
[ ] Have not tested

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

You had mentioned some corner case concerns... do you want to bring them up here?

@edwarnicke  This pull request already contains some corrections from me.

Ah... I see now :)


support link DO NOT WORK

[Enter feedback here]
theis is the essage you got when trying to reactivate a subscription that was accidentally canceled:
Account management has moved to Azure portal
This portal has been retired. We have migrated all the functionality including managing payment methods, downloading invoices, usage & costs and viewing your subscriptions to the Azure portal.
Azure portal offers a richer unified experience for cost management & billing and resource management. Learn more about account management in Azure portal.

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

ID: 0bffdd7e-ea18-32e8-6aa3-1f24e531414f
Version Independent ID: 053c490b-4078-a18c-cc22-38e8e3329dc1
Content: Reactivate a disabled Azure subscription
Content Source: articles/cost-management-billing/manage/subscription-disabled.md
Service: cost-management-billing
Sub-service: billing
GitHub Login: @bandersmsft
Microsoft Alias: banders

@The-algar Thank you for your post. We will look into this issue and get back to you soon.

please call me now
We need to reactivate our VPS on azure subscription iD  f7062012-6dd8-4663-a21d-890d87522e1b NOW!

De : SadiqhAhmed-MSFT @.>
Envoyé : lundi 28 mars 2022 11:57
À : MicrosoftDocs/azure-docs @.>
Cc : Eric M. Clermontet @.>; Mention @.>
Objet : Re: [MicrosoftDocs/azure-docs] support link DO NOT WORK (Issue #90586)
@The-algarhttps://github.com/The-algar Thank you for your post. We will look into this issue and get back to you soon.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/90586#issuecomment-1080445557, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH7Y6OP6RGW3YWJS62Q6QCTVCF7B3ANCNFSM5R2Q4M7Q.
You are receiving this because you were mentioned.Message ID: @.***>

@The-algar Can you share the link you are using to re-activate your subscription?
Ideally, you should be able to re-activate the subscription from Azure portal - http://portal.azure.com/

If you are unable to activate your subscription, you can contact Azure subscription management team by raising a support request.
The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.
Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.
FYI: Azure Billing and Subscription Management support is included in the Basic Support Plan without any charge.
https://azure.microsoft.com/en-us/support/plans/

@The-algar Checking in to see if the above answer helped. Let us know if there are still any additional issues we can help with.

@The-algar We haven't heard back from you, so we will now close this issue. If this remains an issue, please reply and we will gladly continue the discussion.

Hello
forget about it
the Azure team solved it
best regards

De : SadiqhAhmed-MSFT @.>
Envoyé : lundi 28 mars 2022 16:13
À : MicrosoftDocs/azure-docs @.>
Cc : Eric M. Clermontet @.>; Mention @.>
Objet : Re: [MicrosoftDocs/azure-docs] support link DO NOT WORK (Issue #90586)
@The-algarhttps://github.com/The-algar Can you share the link you are using to re-activate your subscription?
Ideally, you should be able to re-activate the subscription from Azure portal - http://portal.azure.com/
[image]https://user-images.githubusercontent.com/44458118/160417198-e5bc906f-3052-4f7b-831b-a6eea50ae1cd.png
If you are unable to activate your subscription, you can contact Azure subscription management team by raising a support request.
The ticket enables you to work closely with the support engineers and get a quick resolution to your issue.
Here is the link - https://docs.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request to create support case.
FYI: Azure Billing and Subscription Management support is included in the Basic Support Plan without any charge.
https://azure.microsoft.com/en-us/support/plans/
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/90586#issuecomment-1080706469, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH7Y6ONJTOZRMKRQZZ2BY3LVCG47PANCNFSM5R2Q4M7Q.
You are receiving this because you were mentioned.Message ID: @.***>

Hi,
I would rather you look into the ticket I opened about reactivatiing a subscription was accidentally canceled.
All our clients services are on that subscription and we need it restored asap
please advise

De : SadiqhAhmed-MSFT @.>
Envoyé : lundi 28 mars 2022 11:57
À : MicrosoftDocs/azure-docs @.>
Cc : Eric M. Clermontet @.>; Mention @.>
Objet : Re: [MicrosoftDocs/azure-docs] support link DO NOT WORK (Issue #90586)
@The-algarhttps://github.com/The-algar Thank you for your post. We will look into this issue and get back to you soon.
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/90586#issuecomment-1080445557, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AH7Y6OP6RGW3YWJS62Q6QCTVCF7B3ANCNFSM5R2Q4M7Q.
You are receiving this because you were mentioned.Message ID: @.***>


DOMAIN_LIST is outdated

wuuvo.com, kzccv.com, qiott.com don't work anymore

I appreciate you letting me know about this issue! I’m working on updating the domain list right now and I’ll get back to you as soon as it’s done. Thanks for your cooperation and support! <3


yuyi

This is an  tag
This is an  tag
This is an  tag
Keep in mind that Atom is highly customizable in a number of ways and we strongly prefer that you consider these options before filing this issue:

https://flight-manual.atom.io/using-atom/sections/basic-customization/: tweak Atom's configuration, styles, and keybindings.
https://flight-manual.atom.io/using-atom/sections/atom-packages/: install a community package.
https://flight-manual.atom.io/hacking-atom/: use the Atom API in your init script, to create a package, or to enhance an existing package.

If you're convinced that none of these options are appropriate for the feature you want, please explain why that's the case by completely filling out the issue template below.
Also note that the Atom team has finite resources so it's unlikely that we'll work on feature requests. If we're interested in a particular feature however, we'll follow up and ask you to submit an RFC to talk about it in more detail.
-->
Summary
One paragraph explanation of the feature.
Motivation
Why are we doing this? What use cases does it support? What is the expected outcome?
Describe alternatives you've considered
A clear and concise description of the alternative solutions you've considered. Be sure to explain why Atom's existing customizability isn't suitable for this feature.
Additional context
Add any other context or screenshots about the feature request here.

Thanks for reaching out!
We require the template to be filled out on all new issues and pull requests. We do this so that we can be certain we have all the information we need to address your submission efficiently. This allows the maintainers to spend more time fixing bugs, implementing enhancements, and reviewing and merging pull requests.
Thanks for understanding and meeting us halfway :grinning:


Add support for Yarn workspaces

This package assumes yarn.lock is in cwd folder, which is not always the case for Yarn workspaces, and result will depend on how you run the command:

yarn workspace my-package xyz => hasYarn=true
cd packages/my-package && yarn xyz => hasYarn=false

I suggest to also look for a Yarn workspace in parent folders, and look for a lock file there too

This is especially true for Yarn 3 where there is only a single yarn.lock file at the root of the monorepo.


On open of the exported html, the initial camera position is far away from the point cloud

On opening of the exported html, the initial camera position is far from the point cloud  and have to zoom in a lot, inorder to get to the point cloud. Need a way such that the exported html also captures the camera selection from the Poses, eg: camera_0 or camera_1 etc.. whichever pose is chosen, should also get captured in the exported html and it will open as the pose in the exported html

Yes we'll do this ASAP!

Done in #314, to be released soon.


I want to receive notifications that are relevant to me. (US 9.0)

I want to be notified of any changes in my account that may be relevant to me.
Acceptance Criteria

[ ] Requires a notification button that indicates when there are new notifications
[ ] Notification button should show most recent notifications when clicked
[ ] Requires a button to see all notifications
[ ] Clicking on the button to see all notifications should bring up a page showing all notifications, from most recent to least recent
[ ] A notification should be added to the list of notifications whenever there are changes in account status, project status, or someone replied to one of their comments

Original acceptance criteria

Requires a notification button that indicates when there are new notifications
Notification button should show most recent notifications when clicked
Requires a button to see all notifications
Clicking on the button to see all notifications should bring up a page showing all notifications, from most recent to least recent
A notification should be added to the list of notifications whenever there are changes in account status, project status, or someone replied to one of their comments

Comments
Would requires rework of the database. If notification is really necessary, sending an email would suffice.


Expose wait_for_steady_state and deployment_circuit_breaker

And also improve the readability of the container definition (see commit messages for more details).

Had to bump dependencies (primarily terratest) in order to fix the e2e tests, all working now but the PR needs another approve before I can merge this 👍


[STAN-171] UI: align updated info to the right

Before:

After:

Additionally, I've tried to remove margin at the bottom of each listing, to try and match with what we have in the prototype. It's a first pass and (as with everything, really) can be modified based on whatever @karypun thinks

@roc this looks great, thank you :-)


nixos/acme: execute a single lego command

Motivation for this change
See #86184.
This implementation follows the workaround indicated https://github.com/go-acme/lego/issues/693#issuecomment-438639428.
Things done

[x] Tested using NixOps
Built on platform(s)

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

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

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

cc @maralorn

Overall this change looks great. Thank you very much!

I must say though that I am not a fan of my own work here.
We are introducing new dependencies on openssl and perl to fix a little something that should logically be done in lego (#216, #290, #693). 4 years and 3 issues later, that does not seem to be a priority for lego to fix this.
@m1cr0man: you introduced the change to Lego. Was Lego the only choice for what we need in NixOS?

I think this PR is an improvement as well - let's merge it :+1:

The acme update mentioned is here https://github.com/NixOS/nixpkgs/pull/91121.

Is it good to merge then?

Yeah go for it! :)

Yeah go for it! :)

I believe I do not have such permission on this repo.

Yeah go for it! :)

I believe I do not have such permission on this repo.

Ah, yes :sweat_smile: someone should be able to do it today for you.

@GrahamcOfBorg test acme

Merging entirely based on discussion.


Remove Entity and update some SideBar related classes

Closes #431
Closes #370
Closes #362
Closes #419
Closes #427
Closes #363
Closes #425

@UFOMelkor Addressed all of your comments. I hadn't actually planned to update Settings, I only made it compile and cleaned up a bit. But seeing from your comments that there wasn't much that was missing, I also addressed those comments to update Settings and added it to the list of issues that will be closed when this is merged.


Capture rationale and impact for using the debug images

In a recent pull request to zipkin, @devinsba noticed we are using the debug distroless image. We should be aware if this is adding heft to our based image which has grown substantially since moving off JDK 1.8
In other repos, we are starting to add RATIONALE.md, and this could be a good thing to start with.

We are about to cut a new zipkin version, but for starters here's where we are > 250MiB. The last version prior to distroless (2.12.3) was < 150MiB.
openzipkin/zipkin                  2.12.3              69d91daa0839        6 months ago        147MB
openzipkin/zipkin                  2.16.2              b4a4e6e796ee        10 days ago         253MB

We definitely grew otherwise, some of it I aim to cleanup in the next release or so. Ex 2.16.2 is dramatically larger than 2.12.3: however it isn't a hundred megs larger.
zipkin-server-2.12.3-exec.jar                     2019-03-01 16:06  39726640
zipkin-server-2.16.2-exec.jar                     2019-08-24 15:08  56548977

I tried to build w/o the -debug and it seems busybox isn't there.. No idea the space saving if we were able to avoid it.
Step 11/17 : RUN ["/busybox/sh", "-c", "adduser -g '' -h /zipkin -D zipkin"]
 ---> Running in e50ea9179b1f
OCI runtime create failed: container_linux.go:345: starting container process caused "exec: \"/busybox/sh\": stat /busybox/sh: no such file or directory": unknown

Can get the numbers into a RATIONALE next week. The debug image just adds BusyBox which was just a couple megabytes or so and is definitely good to keep. Looks like the Java image is getting larger by adding dependencies for swing type libraries, which I remember our old image was explicitly deleting since we don't have a gui. We'll probably need to go back to manual trimming in a base image to get those bytes back.


Missing Dash in PowerShell Sample Causing Command Failure in 'Create the VPN Gateway' Section

I noticed a minor problem with one of the examples on this page. In the section titled 'Create the VPN gateway,' the PowerShell sample is missing a dash in the parameter for 'GatewaySku,' which is causing the command to fail. My feedback here is to add the dash ('-') to correct the example.

Reference: https://learn.microsoft.com/en-us/azure/vpn-gateway/create-routebased-vpn-gateway-powershell#CreateGateway

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

ID: e43f17b9-b2e3-95c7-061a-235692e51b71
Version Independent ID: d3ff45e3-c540-4ff2-d38f-74679c7a153a
Content: Create a route-based virtual network gateway: PowerShell - Azure VPN Gateway
Content Source: articles/vpn-gateway/create-routebased-vpn-gateway-powershell.md
Service: vpn-gateway
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

@zacha0dev
Thank you for your feedback! We will review and update as appropriate.


License

Would you be willing to add a license file to the project?
Example: MIT License :)
https://opensource.org/licenses/MIT

Hey @josephlimb my apologies, I only just noticed this comment. I turned off GH notifications completely for a while when during a period when I was a member of several hundred repos.
I've added the MIT License to this project. Thanks for the bump.


Handle requests.exceptions.ConnectionError

Description
No response

This issue was migrated from an old repository: https://github.com/CiscoDevNet/catalystwan/issues/187


Timezone issues

All the date we receive from our server are UTC,
and DatePickerDialog.mCalendar is final and private,
so I can not override the current timezone of the calendar.
adding accessors for mCalendar would solve this issue.
e.g : I receive from the server "31/10/2016"
I expect to see the picker dialog on the 31th but it is showing on the 30th (time difference between utc and device local time)

The dialog is behaving as expected: render a given date in the timezone of the current device.
If you really need to treat some date timezone independent, you'll have to do the timezone conversion up front, before initializing the dialog


Resolve rendering issue where screen turns white after first frame

I don't know how common or widespread this issue is; I found out about it via a SO question. But, it can be duplicated on my own hardware, so I fixed it.
The color mask (1, 1, 1, 0) seems to be the source of the issue, but I don't particularly understand why. Simply removing the color mask seems to have no ill effect, so that's all this pull request does.
This pull request also includes an example file which reproduces the effect, and which works properly after applying the change.

It is so stupid idea to remove one string code and don't check all tests
gl.colorMask(1, 1, 1, 0); - works good for colored primitives with alpha channel and removes images
gl.colorMask(1, 1, 1, 1); - works good for images and broken alpha channel for primitives


Visualization of segmentation results for Shapenet Part

I used the code you provided to conduct the experiment on the Shapenet Part dataset and could get the MIOU value, but I could not get the visualization result. So I would like to ask you how to do it.
Looking forward to your reply. Thank you

You can use MeshLab or Cloudcompare for visualization. Both of them are very easy to use.

Received, thank you
---Original---
From: "Yongcheng @.>
Date: Mon, Feb 14, 2022 17:01 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [Yochengliu/Relation-Shape-CNN] Visualization of segmentationresults for Shapenet Part (#43)
You can use MeshLab or Cloudcompare for visualization. Both of them are very easy to use.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you authored the thread.Message ID: @.***>


Removed from the playstore

Hello, loafwallet is removed from the playstore once again (like many apps)
this is a real bummer.
Please consider f-droid and/or apks on github.
Regards

Maybe because of the SMS change they made,nothing major imo

Maybe because of the SMS change they made,nothing major imo

Google currently removes a lot of apps paid or free apps - for several reasons.
Not only due to the sms-changes.

See also here:
https://old.reddit.com/r/litecoin/comments/b6ki32/what_the_heck_happen_to_loafwallet/

It's fixed. But we are working to add Loaf to the fdroid store.


Migrate to pnpm, publish via GitHub Actions with provenance

A nice to have, see the discussion as well as the blog post on npm package provenance.

As a note, the "publish package" steps in our processes are becoming a significant pain point

It took a handful of commits, but my fork now has an automated Actions workflow that publishes a package to npm with provenance (scroll to the bottom of the linked page) and releases to GitHub.
It uses changesets and works like so:

Every commit to main will trigger the changeset action to look at the changesets since the last release
It will aggregate these changesets and decide on the next appropriate version (e.g. if there was a few patches, then patch; if a minor then minor, etc.)
It will create a PR
If we don't want to release, then we just don't merge the PR and it hangs around, getting updated automatically on each main push
If we do merge, then it releases to npm and GitHub

Other notes:

I needed to add a repository url to package.json
I chose changeset as the release flow option because we use changesets in other repos and so it seemed like the better option than trying to change behavior and force folks to use conventional commit messages, which is necessary for other release workflows
I replaced yarn with pnpm

Thoughts @andreogle @bbenligiray ? Shall I create a PR?

I can see a few cases that this doesn't support. For example, if we have a major and a minor change lined up on main and we want to release only the minor change, the automatic PR will want us to release the major change as well. Also, it doesn't seem to support patching previous major/minor versions. I guess to be able to support these, minor-specific release branches as in Airnode (https://github.com/api3dao/airnode/tree/v0.3, https://github.com/api3dao/airnode/tree/v0.4, etc.) are needed. That being said, I think OIS releases have been exclusively linear so this workflow would work here in practice.
Is it possible to require a number of approvals on the release PR?
@hiletmis can you check the provenance part out? The point is that the releases that do it has a green tick.

Would provenance also work here?

@bbenligiray tried on logos.
I will do the necessary changes on the other repos as well
thanks @dcroote for the feature

For example, if we have a major and a minor change lined up on main and we want to release only the minor change, the automatic PR will want us to release the major change as well.

Correct, though I've struggled to think of when we'd have both merged to main but then not want to release the major. Did you have a situation in mind?

Also, it doesn't seem to support patching previous major/minor versions

As you suggest, I would create a branch (if one didn't already exist), but then add the branch to the workflow trigger here so that changesets releases the appropriate version against that branch containing the patch. The fallback could always be manual release.

Would provenance also work here?

Quite possibly. The Airnode docker build steps are a bit complicated, but the api3-dao-dashboard already uses the docker/build-push-action GitHub Action that automatically adds provenance attestations

Is it possible to require a number of approvals on the release PR?

I'm not sure this can be done based on GitHub's branch protection rules. The number of reviewer approvals can be set, but only at the branch level. Right now this repo requires: PRs to merge, 1 approval, and status checks before merging. There is the option of "Require review from Code Owners" that might get at what you want.

thanks @dcroote for the feature

Sure, and @hiletmis if you want the PRs and commits to have the release version see this step and how it's incorporated.

Correct, though I've struggled to think of when we'd have both merged to main but then not want to release the major. Did you have a situation in mind?

It's common to bundle breaking changes together to reduce the number of major releases. Breaking changes also typically take a longer time to implement. Of multiple breaking changes, one will hit main first, and in the case that we want to bundle all breaking changes together, we would have to wait until all breaking changes are completed before being able to make a new release, which would potentially take a long time. Again though, I'm thinking generally, OIS may not be affected by this in practice.

As you suggest, I would create a branch (if one didn't already exist), but then add the branch to the workflow trigger here so that changesets releases the appropriate version against that branch containing the patch. The fallback could always be manual release.

We probably wouldn't need manual release at all in this case. This may be overkill for something like OIS that historically had a linear release path (no backporting) though.

Quite possibly. The Airnode docker build steps are a bit complicated, but the api3-dao-dashboard already uses the docker/build-push-action GitHub Action that automatically adds provenance attestations

Documented in https://github.com/api3dao/airnode/issues/1956

I'm not sure this can be done based on GitHub's branch protection rules. The number of reviewer approvals can be set, but only at the branch level. Right now this repo requires: PRs to merge, 1 approval, and status checks before merging. There is the option of "Require review from Code Owners" that might get at what you want.

It looks like we can require an arbitrary number of approvals or approval of code owners, but this may be annoying on main. Having a special release branch (or multiple for different versions) would allow stricter requirements to be practical.

OK- after a bunch of exploration the following can work, which I believe satisfies everything. Note it is slightly more laborious because of the multiple PRs, but I think that is inescapable if we want stricter release protections.

We have a release branch with stricter branch protection rules (required PR before merging, number of reviewers, a code owner). This is nice because we don't have to enforce stricter branch protections on main and main development can continue in parallel with a release.
When we decide to make a release: we open a PR from main to release. In my fork: https://github.com/dcroote/ois/pull/8
Since the PR is against release it requires the aforementioned approvals
The PR is merged, which triggers the changeset release Actions workflow which runs on push to release.
The Actions workflow sees changesets and creates a release PR against the release branch. https://github.com/dcroote/ois/pull/9
Since the PR is against release it requires the aforementioned approvals
The PR is merged, which publishes to npm with provenance and to GitHub Releases
A PR from release to main is created and merged. https://github.com/dcroote/ois/pull/10
Repeat

What is nice is while the release process is occurring, development can continue on main without issue (I tested by pushing a commit to main after publishing but before merging release back to main).
Note that I believe merging of PRs to and from release should be done with "Create a merge commit" to preserve the commit history, which is particularly important for preserving the tagged release commit. I think the Actions PR itself can be squashed or rebased to avoid one extra merge commit.

Sounds simple enough to me.

Sounds good, this is mostly what we're doing atm with the data feed operations (except the release branch isn't protected yet)

A PR from release to main is created and merged. https://github.com/dcroote/ois/pull/10

I assume you opened this PR manually. I wonder if it can be opened automatically after the release.

I assume you opened this PR manually. I wonder if it can be opened automatically after the release.

Indeed it can be, good thought.

@hiletmis see above. We tend to merge production back to main manually, it would be nice if a PR that does this opened automatically after production publishes


Expm typo fix add log

fixed a typo and added a logger.info to log more info.
Description

Motivation and Context

How Has This Been Tested?

[ ] Pass the test by running: pytest qlib/tests/test_all_pipeline.py under upper directory of qlib.
[ ] If you are adding a new feature, test on your own test scripts.

Screenshots of Test Results (if appropriate):

Pipeline test:
Your own tests:

Types of changes

[ ] Fix bugs
[ ] Add new feature
[ ] Update documentation

Thanks!
It looks great now!


Creation of py.typed is not detected

Port of https://github.com/microsoft/pyright/issues/7479, but as a request to the Pylance team.
# Install pipx
python -m pip install --user pipx
python -m pipx ensurepath

# Install Poetry
pipx install poetry

# Create a new src-layout project
poetry new pytyped-repro-dir --src

# Enter the environment
cd pytyped-repro-dir
poetry install
poetry shell

# Turn on strict type-checking for Pyright and *disable extra path lookups*.
printf "\n\n[tool.pyright]\n\ntypeCheckingMode = \"strict\"\nextraPaths = []" >> pyproject.toml

# Define a function in the package, and import it from the tests.
printf "def foo():\n    return 'hi'\n" > src/pytyped_repro_dir/__init__.py
printf "from pytyped_repro_dir import foo\n\nfoo()" > tests/__init__.py

In a separate terminal, run the following in pytyped-repro-dir
poetry shell
npm init --yes
npm install pyright
npx pyright --watch

Pyright issues the following error:
.../pytyped-repro-dir/tests/__init__.py
  .../pytyped-repro-dir/tests/__init__.py:1:6 - error: Import "pytyped_repro_dir" could not be resolved (reportMissingImports)
  .../pytyped-repro-dir/tests/__init__.py:1:31 - error: Type of "foo" is unknown (reportUnknownVariableType)

In the original terminal, create a py.typed file:
touch src/pytyped_repro_dir/py.typed

Notice file watching doesn't pick up any change. The error persists, but goes away if you restart Pyright or the language service.

I'll note that file watching has historically been a major source of bugs and regressions in pyright due to the complications of inconsistent behaviors and file system limitations across various platforms and configurations. Our current file watching implementation has been working stably for some time, so if you decide to pursue this feature request, please do so carefully to avoid unintended consequences. As I said in the pyright thread, I think this feature request will impact very few users, but a regression in the file-watching code will have widespread (negative) impact.


xaxis unreadable when too many items

Hello,
on Line Chart i want to show history (month to month) from past 10 years. however their is too much label to write them all on the xaxis :( how to hide some label to show only few label who can be draw on the xaxis without overflowding their neighbor label ?
screenshoot:
https://docs.google.com/file/d/0BwX45JL_Li5FWHRjRnVmblFkX00/edit?usp=drivesdk

and the scale numbers are cut off on the left side. I've also noticed that on a few charts.

@HaraldWalker  You can see how I resolved this problem at #715

One possible solution is to print blank spaces for some of the labels.  For instance, let's say you want to only have 10 X labels:
//assuming labelData is your current array of labels
var labels = [];
var labelsToShow = Math.floor(labelData .length / 10);
for (var f = 0; f < chartData.length; f++) {
if (f % labelsToShow == 0) {
labels .push(f);
} else {
labels .push("");
}
}

This is a use case for the chart type I'm proposing in https://github.com/nnnick/Chart.js/issues/1059. Maybe you are interested in helping developing this?

Huzzah! The first alpha of Chart.js 2.0 has landed and should fix this issue. Check out the release and try it out! We've got a lot of momentum right now, so please help us test so we can launch 2.0 Gold by the end of the month.
https://github.com/nnnick/Chart.js/releases/tag/v2.0-alpha
I'm closing this issue for now, but if you have implementation questions or find bugs, please create a jsfiddle and post the link here and we'll reopen this issue and get it fixed.


Set Daily to stream raw tracks

closed by https://github.com/Watts-Lab/deliberation-empirica/pull/316


Javascript functions extension

Extension for Javascript functions like alert,confirm and prompt

Refer to PR #570

if you want something that is just alert/confirm/prompt then we can talk about that...

Not eval and other dangerous stuff

more like alert,confirm and other safe javascript functions like fetch but fetch already has it's own extension

if eval gets added make it very sandboxed like you need to enable it and stuff can just not work if it is a computer virus waiting to happen

I now have v0.1 done (alert only)

Lily's Toolbox have it

Imma add some more blocks


Add parameter to use external cache dir for SBRP and previously-source-built tarballs

These files can unpredictably take a very long time to download, which is particularly bad in source-build since we need to do fresh builds all the time. It would speed up local builds quite significantly to have an easy way to cache the files in a directory that won't be wiped by git clean -xdf or similar commands.
We might just need to:

Change the download to skip if the file exists.
Make sure the download writes the stream to a temp file, not the final (to avoid cancellation problems).

Ideally we'd also have a checksum, but we don't have a reasonable way to check these in with auto-updates AFAIK. 😕

Make sure overriding the shared definition of ExternalTarballsDir works.
Provide a shortcut to override ExternalTarballsDir with, say, $HOME/.dotnet-source-build/external-tarballs/?

SBRP is now built as part of source-build.  Prep.sh also provides a means for devs to cache the previously-source-built artifacts locally.

Closing per my previous comment.


Minor update to Installation Guide

For the pip installation on Windows, the command box needs to be running as admin for the installation to complete; this isn't mentioned in the docs (just says "open a command prompt").

If you installed python to your program files directory, then yes, admin permission are required. A note about this in the docs would be helpful. I'll make a doc update later today.

Updated the install guide with commit 0092acd11068ff6f74577d739eb5e8fed391e08a


subsample used? 200 m to 1 m frames

Based on the Google's post, it use 200m frames. I wonder what kind of subsample methods are used to keep only 1m frames? Thank you.

@weiguowilliam Hello, thank you for the issue! Google's dataset is consisting of 200M frames per seed on each game. The 200M frames of the data are divided into 20 chunks of 1M frames. So, in this library, one of the chunks is loaded to make up the dataset with 1M frames. Although mixing up frames in different epochs needs more memory space and time to process, we can add that feature.

Thank you! 1m frames should be enough:)


Replace tabs with spaces

Replace tabs with two spaces.

Thanks a lot! I've been meaning to do this, but I haven't had the time :)


[OAuth 2.0] "invalid_request" for changing outlook incoming server authentication to OAuth 2.0

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
6.904
Where did you get the app from?
F-Droid
Android version
OneUI 4.1 (Android 12)
Device model
Samsung M51
Steps to reproduce
Context: Got a microsoft email that older sign-in methods will be disabled soon. Switching to OAuth 2,0 in thunderbird desktop was easy (sending a test email triggered OAuth sign-in). Then logged in to my account settings through browser and cleared all app passwords. This caused K-9 mail on my phone to show 'Authentication failed' notification. Tapping on it led to the 'Inoming Server Settings' page of that outlook account.
Steps performed then:

Changed Authentication from 'Normal Password' to 'OAuth 2.0'.
Clicked next, it prompted me to Sign in (We'll redirect you to your email provider to sign in. You need to grant the app access to your email account).
Tapping on the link opened my browser (Tried a bunch: Firefox, Fennec, Chrome, Cromite, even copied URL to desktop and tried in Firefox desktop. Same error).
The page that opens throws an error.

Expected behavior
The website should prompt to sign in and allow adding k-9 as an email client.
Actual behavior
The page shows an error instead:
We're unable to complete your request
invalid_request: The provided value for the input parameter 'redirect_uri' is not valid. The expected value is a URI which matches a redirect URI registered for this client application
I have tried manually capturing the url and manually pasting (just in case) but it always errors out. Also it doesn't matter if that account is already logged into the browser, it never detects it.
Logs

This is going to become a real problem for K9.
Support for modern authentication is becoming mandatory.

And I changed IMAP server from imap-mail.outlook.com to outlook.office365.com according to microsoft docs.
Don't know if it matters or not.

@nICEnnnnnnnLee Thanks for the hint, I downgraded back to the 6.804 (fdroid) version to test and while it still failed the first time when I re-imported my backup and tried to reauthenticate, changing my default browser to another browser somehow fixed it.
This was weird so to try again, I added a completely new account, and this time even the old browser started loading the OAuth sign-in page correctly. I guess K-9 mail was generating the correct URL but the browser (whichever was the default) was receiving a broken one and thus the 'invalid_request' error.
Unfortunately I can't reproduce it now to confirm. but it's fixed and I've successfully converted all outlook accounts to OAuth 2.0.
Thank you, I guess I should close the issue.
Regards,
Gravemind2015


[fix](mark join) mark join column should be nullable

Proposed changes
pick #24910 into branch-2.0
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 51.04 seconds
stream load tsv:          555 seconds loaded<PHONE_NUMBER>9 Bytes, about 128 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          32 seconds loaded 861443392 Bytes, about 25 MB/s
insert into select:          29.6 seconds inserted 10000000 Rows, about 337K ops/s
storage size:<PHONE_NUMBER>1 Bytes

there is a bug, wait for next pr


whether we can define a global receiver to just send  warning notifications for a whole K8S cluster?

I have try below config, but still can receive many warning alerts.

@wanjunlei Any thoughts on this? As I can understand the router and alertselector in receiver is duplicated, we can keep one of them

@cao99 check if there any other receivers send to the wechat user CaoYY.
And the WeChat in Router will be the low case, it should be wechat.

@cao99 check if there any other receivers send to the wechat user CaoYY.
And the WeChat in Router will be the low case, it should be wechat.

Just one receiver to the wechat user CaoYY.
I will try to change to the low case: wecat

I delete all routers, and just config alertSelector in the global receiver. Now can't receiver any new notifications even warning alerts.

change the log level to debug, check if any alerts are received
https://github.com/kubesphere/notification-manager/blob/master/docs/crds/notification-manager.md#args

@wanjunlei  below are logs

From the log, the alerts were filtered out in the filter stage, you can create a global receiver without alertSelector to check that alerts with the error or critical severity have been received.

If remove alertSelector from receiver,  we can receive  warning error critical severity  alerts.

a spelling error, the serverity should be severity.

Tks a lot, working now.  Copy  config from here,  the spelling error need to update also.
https://github.com/kubesphere/notification-manager/blob/master/docs/crds/receiver.md


Support for global Extensions, Environment

Is your feature request related to a problem? Please describe.
No.
Describe the solution you'd like
We define a lot of extensions, which we use in many of our stacks, an example would be for logging:
x-influxlog: &influxlog
  logging:
    driver: syslog
    options:
      syslog-address: "udp://localhost:514"
      tag: "{{.ImageName}}"

We would like to share these extensions so that like Docker Configs & Secrets, they can be referenced in newly created stacks without explicitly implementing them again.
Another thing that would benefit from such a mechanic is global environment variables. Maybe these can be shown as an immutable list when creating a new stack and edited somewhere else. But that's a lower priority.
Describe alternatives you've considered
AFAIK, there are none, at least not for extensions. Right now we just past them into each new stack.

@turbo On the global environment variables that sounds like something we have implemented (see issue 2411 https://github.com/portainer/portainer/issues/2411) to pull values out from a data source (currently an Excel spredsheet although we were thinking of extending it to be via ODBC). I'm planning on getting the changes up into my public repository shortly.
Is that the sort of thing you have in mind?

@turbo on swarm mode Portainer currenlyt uses docker stack deploy command for deploying stacks so it have same limitations than Docker it selves have so to get feature like that it would need to be added to Docker first.
But if you have access to Docker nodes you can set default logging settings on there: https://docs.docker.com/config/containers/logging/configure/


prefer-for-of false positive

The following pattern causes prefer-for-of to trip even though it's impossible to turn the for into a for-of.
const a = { b: 5 };
const b = { c: 5 };

for (const key in a)
	if (!(key in b))
		b[key] = a[key];

I'm sure there might be a better way of performing this pattern without the for (maybe Object.assign?), but just letting you know.

Oh, I see, it wants me to use Object.keys rather than "in". My bad. The error msg should probably reflect that, though.


Experimenting w/ Datasets - Purpose of Exp.

Objective:

[x] Define objective of engaging with dress-up games
[x] Write about what research gaps this research addresses
[ ]

Completed! I will be editing the .md file just so everything is properly formatted and stuff


Verify machine-controller CRDs before deleting workers

What this PR does / why we need it:
This PR fixes a bug and brings an improvement:

kubeone reset will not wait for workers to be deleted if CRDs are not deployed
kubeone reset will now explicitly check are CRDs deployed instead of trying to delete a CR

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #681
Does this PR introduce a user-facing change?:
kubeone reset doesn't wait for workers to be deleted if machine-controller CRDs are not deployed

/assign @kron4eg

/retest

pkg/installer/installation/reset.go:208:26: defaultRetryBackoff - retries always receives 3 (unparam)
func defaultRetryBackoff(retries int) wait.Backoff {
^
make: *** [Makefile:70: lint] Error 1

Should we ignore this error, disable unparam or something else?

@kron4eg I ignored the lint error, so CI passes. PTAL.

/lgtm

/retest


[FR] Give buttons for previous and next notes

Thank you for this great plugin. I has helped me in decreasing clutter of navigation from my notes. It would be great if the Navbar could have dedicated button for previous and next daily notes. I have a streak of 13 years in journals which I have imported into Obsidian and am missing this feature.

For now I have implemented this functionality in my setup using the Quick Explore + Commander plugin

Good idea. I don't want to clutter the navbar by default, I could make the buttons toggleable or just create Obsidian commands, or both. What do you think?

Hi, I don't think I want to add this to this plugin, as I want this plugin to focus on the navbar.
You can add it yourself by using Commander and Periodic Notes

They also have commands for weeks, months and years


SAPUI5 Version conflicts (1.123 and 1.124)

Hello there,
I've recently noticed that the cap-js/attachments plugin is incompatible with the SAPUI5 version 1.123 and 1.124 (1.125 works fine).
Specifically there seems to be an issue with missing ui5 functions, which leads to the app not loading:

Sometimes also an duplicate id error is thrown:

Since I've only been able to find a reference that UI5 version 1.121.0 or higher (^1.121.0) is required, this version incompatibility should probably be documented somewhere.
Versions:
@cap-js/attachments: 1.0.2
@cap-js/cds-types: 0.2.0
@sap/cds: 7.9.2
@sap/cds-compiler: 4.9.4
@sap/cds-dk: 7.6.0
@sap/cds-dk (global): 7.9.3
@sap/cds-fiori: 1.2.3
Best regards
Timo

Hi @Rediate15,
Yes, the Attachments table doesn't work with the UI5 versions 1.123 and 1.124, thank you for pointing this out. We will update the readme for the same.
Best Regards,
Muskan


Re-designing the profile page.

There is mess on profile page design, the profile page should be redesigned in a aesthetic way.

I am requesting You to permit me to work on this issue, and to inform you I am GSSOC-2021 participant.

I am the participant of Gssoc 21 , I would like to work on this , Will you assignee me

@VarunMore Assigned.
@Furquan712 FCFS rule :p

Sir, Do I need to follow any pattern or any set of rule while or I should do it by my and then push the code for the review?

hey @yash982000 I have done the changes and  now wants to place a pull request so that you can review it and merge it, can you help me to place a pull request, I tried to push the code to the repo but its showing some  error--(remote: Permission to ChetnaNSharma/Alumni-Connect.git denied to VarunMore.
fatal: unable to access 'https://github.com/ChetnaNSharma/Alumni-Connect.git/': The requested URL returned error: 403
).
please help.

Can I work on this issue?

@VarunMore Please update your status fast.
If not, @srishtij2000 feel free to work on it. If I am unable to reply fast, drop me a WhatsApp DM on<PHONE_NUMBER>

Okay I will be start working on this . Kindly  assign this to me

wait @srishtij2000  i am waiting for review,
I'm already working .

@srishtij2000 Feel free to hop on some other issue

I am requesting You to permit me to work on this issue.


HTTPS Setup Documentation

Hi @marcosnils , do you guys have documentation on how to properly setup SSL (https) for Play With Docker?  Similar to this website  play-with-docker.com --> https://labs.play-with-docker.com/

PWD supports let's encrypt by default. We don't have any instructions or provide any support about how to set it up but following the code should be straightforward
https://github.com/play-with-docker/play-with-docker/blob/b363a35a61f60f7908b8a31e8c3dcaba54183f61/handlers/bootstrap.go#L132


Vega year update

Added vega logic to relevant plots which colors the background of the plots by year.

Can you add a picture of the change?

Group Stack Plot:

Location Date Plot:

great, thanks!


autoUpdater.quitAndInstall() doesn't relaunch app

When I call autoUpdater.quitAndInstall(), the app quits to install the update, but it doesn't start afterwards; when I start it manually, I can see that the update was applied successfully. This must have been broken in the last two or three releases of Electron, as I remember it was restarting the app correctly on 0.36.4.
Currenty: Electron 0.36.7 on OSX 10.11.

There was no changes to OS X's autoUpdater in 0.35.x and 0.36.x, it could be caused by other things. I suggest reporting this to https://github.com/Squirrel/Squirrel.Mac instead, which is the auto updating library used by Electron. I'm closing this since we are not able to solve this on our side.


deptry 0.17.0 does not recurse into subdirectories on Windows

Describe the bug
deptry does not seem to recurse into subdirectories, incontrast to the documentation's "Dependency issues are detected by scanning for imported modules within all Python files in a directory and its subdirectories,"
To Reproduce
On Windows 10, I installed deptry into the virtual environment used by the project by
poetry add --group dev deptry

and run it on our project, which has the following structure
$ROOT
 +--src
 |   `--<packagename>
 |       +--[subdirs with python files in it]
 |        `--main.py
 `--pyproject.toml

From $ROOT

deptry . does not scan any files.
deptry src does not scan any files
deptry src\<packagename> scans main.py, but does not scan those in the subdirs

=> deptry does not seem to recurse into subdirectories, at least on Windows.
Expected behavior
Scan all files, as described in the documentation
System [please complete the following information]:

OS: Windows 10
Language Version: Python 3.10.11
Poetry version: Poetry 1.8.2

I've tried on my side on Windows with the structure you shared and was not able to reproduce, as files are correctly found.
Could you maybe add --verbose flag when running deptry and share the output (make sure to redact data you think is sensitive), or create a minimal git repository that reproduces the issue? That would help trying to reproduce the issue.

Going to close this one since I was not able to reproduce, and we don't have any feedback. If you are still affected and are able to give more details, feel free to add a comment, or create a new issue.


All items disappeared

I use the mod on the version 1.12.2 and have not had any problems until now. In addition, I use the Mod Ultimate Remote.
So, I've built, keep accessing the ME system and then, all of a sudden, all the items are supposed to be gone. Even if I put a NEW item in the system, the interface remains empty. A hard disk is full, and remove the hard disks and reinvent again has brought nothing. Even if I insert an empty disk, the problem persists.
I use the normal 64k hard drives.

Just got this issue myself...It occured to me while is making gold ingots form nuggets and the storage was saying i had 31k odd nuggets when in fact i only had 3


Add TIMER to the compilationType enum of the HostEnsureCanCompileStri…

…ngs hook.
The HTML spec redefines it in a way that accepts a "TIMER" compilation type, used by setTimeout and setInterval [1] [2] [3].
[1] https://html.spec.whatwg.org/multipage/webappapis.html#hostensurecancompilestrings(realm,-parameterstrings,-bodystring,-codestring,-compilationtype,-parameterargs,-bodyarg)
[2] https://w3c.github.io/webappsec-csp/#can-compile-strings
[3] https://html.spec.whatwg.org/multipage/timers-and-user-prompts.html#timer-initialisation-steps

cc @koto @lukewarlow

(I'm not quite sure in which spec this value should be defined)

Having this in ECMA-262 is very weird, given that ECMA-262 doesn't use it at all.
Ideally, the HostEnsureCanCompileStrings signature should not be updated, and its implementation in web specs should be changed to
HostEnsureCanCompileStrings(...args)
1. Perform EnsureCanCompileStrings(...args)

where EnsureCanCompileStrings is defined in the relevant web spec. Then, setTimeout should call EnsureCanCompileStrings directly (and not HostEnsureCanCompileStrings, which is meant to be called by ECMA-262 to ask for info to web specs), and only EnsureCanCompileStrings needs to accept extra parameters or enum values.

Oh I see that the above is already happening, with EnsureCSPDoesNotBlockStringCompilation. Then I don't understand why we need this change, given that HostEnsureCanCompileStrings is never called with a TIMER value.

Mmh, you are right the "timer initialization steps" above directly calls EnsureCSPDoesNotBlockStringCompilation with the timer value, not HostEnsureCanCompileStrings.
That said, I see that

https://tc39.es/proposal-dynamic-code-brand-checks/#sec-hostensurecancompilestrings uses an enum values DIRECT-EVAL, INDIRECT-EVAL, FUNCTION.
https://w3c.github.io/webappsec-csp/#can-compile-strings uses a quoted uppercase names "TIMER" and "FUNCTION".
https://html.spec.whatwg.org/multipage/timers-and-user-prompts.html#timer-initialisation-steps uses unquoted lowercase timer.

which I guess is understandable but I'm sure is quite right. Or maybe I'm missing something?
Maybe we should be:

change https://html.spec.whatwg.org/multipage/webappapis.html#hostensurecancompilestrings(realm,-parameterstrings,-bodystring,-codestring,-compilationtype,-parameterargs,-bodyarg) to remap the enum values to quoted uppercase names.
change https://html.spec.whatwg.org/multipage/timers-and-user-prompts.html#timer-initialisation-steps to pass "TIMER" as an argument

but indeed no need to change the HostEnsureCanCompileStrings definition here.

* change https://html.spec.whatwg.org/multipage/webappapis.html#hostensurecancompilestrings(realm,-parameterstrings,-bodystring,-codestring,-compilationtype,-parameterargs,-bodyarg) to remap the enum values to quoted uppercase names.

maybe even map DIRECT-EVAL and INDIRECT-EVAL to a single "EVAL" value, since EnsureCSPDoesNotBlockStringCompilation treats them the same.

Closing this issue per discussion above.


large file out of memory

cosole error in chrome:
Cannot enlarge memory arrays. Either (1) compile with  -s TOTAL_MEMORY=X  with X higher than the current value 16777216, (2) compile with  -s ALLOW_MEMORY_GROWTH=1  which adjusts the size at runtime but prevents some optimizations, (3) set Module.TOTAL_MEMORY to a higher value before the program runs, or if you want malloc to return NULL (0) instead of this abort, compile with  -s ABORTING_MALLOC=0
Then,I try to add this code before Viz.js

<script>
        var Module = {
             TOTAL_MEMORY: [537395200]
        }
   </script>

but it can't works

The Module variable this refers to is hidden inside a closure. If you really want to do this, I would try one of the following:

Build Viz.js with a modified src/pre.js.
Edit the Viz.js release. You can find the closure and the Emscripten Module variable at the beginning of the file.

set default value of TOTAL_MEMORY ,like this:
ma=e.TOTAL_MEMORY||537395200

Viz.js now supports the totalMemory option:
Viz(src, { totalMemory: 537395200 });

This option doesn't seem to work in 2.1.2 when viz.js is loaded in Node using require('viz.js/full.render.js').
A usable workaround is as follows:
const viz = new Viz({Module: () => Module({TOTAL_MEMORY: 1<<25}), render});


Omnisharp 1.12.0 on MacOS does not start. Complains of missing file: mcs.exe

Environment data
dotnet --info output:
.NET Command Line Tools (1.0.4)
Product Information:
Version:            1.0.4
Commit SHA-1 hash:  af1e6684fd
Runtime Environment:
OS Name:     Mac OS X
OS Version:  10.12
OS Platform: Darwin
RID:         osx.10.12-x64
Base Path:   /usr/local/share/dotnet/sdk/1.0.4
VS Code version: 1.15.0
C# Extension version: 1.12.0
Steps to reproduce
Open a .cs file
Expected  behavior
Omnisharp starts working
Actual behavior
Omnisharp keeps showing "Running" in the bottom right corner and does not work.
The output of OmniSharp Log is:
Starting OmniSharp server at 8/11/2017, 3:05:53 PM
    Target: /Users/perbnielsen/Documents/state-machine-unity/Unity/Unity.sln

OmniSharp server started wth Mono
    Path: /Users/perbnielsen/.vscode/extensions/ms-vscode.csharp-1.12.0/.omnisharp/run
    PID: 29831

OmniSharp: -s /Users/perbnielsen/Documents/state-machine-unity/Unity/Unity.sln --hostPID 29793 --stdio DotNet:enablePackageRestore=false --encoding utf-8 --loglevel information formattingOptions:useTabs=false formattingOptions:tabSize=4 formattingOptions:indentationSize=4
{"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Startup","Message":"Omnisharp server running using Stdio at location '/Users/perbnielsen/Documents/state-machine-unity/Unity' on host 29793."},"Seq":1,"Type":"event"}
[info]: OmniSharp.DotNet.DotNetProjectSystem
        Initializing in /Users/perbnielsen/Documents/state-machine-unity/Unity
[info]: OmniSharp.DotNet.DotNetProjectSystem
        Auto package restore: False
[info]: OmniSharp.DotNet.DotNetProjectSystem
        Update workspace context
[info]: OmniSharp.DotNet.DotNetProjectSystem
        Resolving projects references
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        OmniSharp initialized with Mono MSBuild.
    MSBUILD_EXE_PATH: /Library/Frameworks/Mono.framework/Versions/4.8.0/lib/mono/msbuild/15.0/bin/MSBuild.dll
    MSBuildExtensionsPath: /Library/Frameworks/Mono.framework/Versions/4.8.0/lib/mono/xbuild
    TargetFrameworkRootPath: /Library/Frameworks/Mono.framework/Versions/4.8.0/lib/mono/xbuild-frameworks
    RoslynTargetsPath: /Users/perbnielsen/.vscode/extensions/ms-vscode.csharp-1.12.0/.omnisharp/omnisharp/msbuild/Roslyn
    CscToolPath: /Users/perbnielsen/.vscode/extensions/ms-vscode.csharp-1.12.0/.omnisharp/omnisharp/msbuild/Roslyn

[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Detecting projects in '/Users/perbnielsen/Documents/state-machine-unity/Unity/Unity.sln'.
[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Loading project: /Users/perbnielsen/Documents/state-machine-unity/Unity/Assembly-CSharp.csproj
[fail]: OmniSharp.MSBuild.ProjectFile.ProjectFileInfo
        The specified task executable location "/Users/perbnielsen/.vscode/extensions/ms-vscode.csharp-1.12.0/.omnisharp/omnisharp/msbuild/Roslyn/mcs.exe" is invalid.
[warn]: OmniSharp.MSBuild.MSBuildProjectSystem
        Failed to load project file '/Users/perbnielsen/Documents/state-machine-unity/Unity/Assembly-CSharp.csproj'.
/Users/perbnielsen/Documents/state-machine-unity/Unity/Assembly-CSharp.csproj

[info]: OmniSharp.MSBuild.MSBuildProjectSystem
        Loading project: /Users/perbnielsen/Documents/state-machine-unity/Unity/Assembly-CSharp-Editor.csproj
[fail]: OmniSharp.MSBuild.ProjectFile.ProjectFileInfo
        The specified task executable location "/Users/perbnielsen/.vscode/extensions/ms-vscode.csharp-1.12.0/.omnisharp/omnisharp/msbuild/Roslyn/mcs.exe" is invalid.
[warn]: OmniSharp.MSBuild.MSBuildProjectSystem
        Failed to load project file '/Users/perbnielsen/Documents/state-machine-unity/Unity/Assembly-CSharp-Editor.csproj'.
/Users/perbnielsen/Documents/state-machine-unity/Unity/Assembly-CSharp-Editor.csproj

[info]: OmniSharp.Script.ScriptProjectSystem
        Detecting CSX files in '/Users/perbnielsen/Documents/state-machine-unity/Unity'.
[info]: OmniSharp.Script.ScriptProjectSystem
        Could not find any CSX files
[info]: OmniSharp.Services.WorkspaceHelper
        Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpWorkspaceOptionsProvider
[info]: OmniSharp.Startup
        Configuration finished.

This looks like a duplicate of https://github.com/OmniSharp/omnisharp-vscode/issues/1704. The solution is to update to the latest stable Mono version (5.0.1).

Also reported here: https://github.com/OmniSharp/omnisharp-vscode/issues/1699.

Do let me know if this doesn't fix the issue for you.

That did indeed fix it. Thank you.

Glad to hear it. Thanks!


[Improvement] - Add Continuous Integration

There is no CI Automatic Build and Test.
I think it would be very useful to add a CI service such as Travis-CI or Circle-CI which will make it possible to test the code after every push and each pull request.

Could this be added as a google code in task?

This would require login permission to the CI server. So I don't think we'll be able to provide credentials to students.


cell killing vs cell death

@pgaudet  Should these be related in GO?

I dont think so - killing a cell means killing another cell, and is typically a defense reponse (that bit needs to be improved, I think it's missing from the ontology), cell death is often an internal cellular program. I am not sure how we mode when a cell induces apoptosis in another cell ?

OK, I think it has probably been used incorrectly. I can see that immune cell mediated cell killing belongs under here, but a lot of the co-annotations are to
for instance,
GO:0150064 vertebrate eye-specific patterning
GO:0036257 multivesicular body organization
GO:0008584  male gonad development
GO:0051402 neuron apoptotic process
GO:0008340   determination of adult lifespan
GO:0007431 salivary gland development
GO:0008285 negative regulation of cell population proliferation
Should the definition really be more specific  in the context of defense?

Looks like these are developmental ?

Yep. It seems that apoptosis in the context of development should. be excluded from cell killing?

Definitely!
Although in this case I wonder, looking at the first one GO:0150064 vertebrate eye-specific patterning - there are 3 EXP annotations, including 2 to complement system proteins, which are likely killing as a defense response in some pathway independent of eye patterning.

The third being integrin, also involved in immune processe

complement-mediated synapse pruning

I suspect you are getting these co-annotations from children of cell killing
'complement-dependent cytotoxicity'
'leukocyte mediated cytotoxicity'
'microglial cell mediated cytotoxicity'
'natural killer cell mediated cytotoxicity'
'neutrophil mediated cytotoxicity'
'T cell mediated cytotoxicity'
which as far as I remember could not be moved under 'killing of cells of another organism' because they also serve to eliminate tumor cells ('GO:0002420 natural killer cell mediated cytotoxicity directed against tumor cell target'
'GO:0002419 T cell mediated cytotoxicity directed against tumor cell target') (and now I see, during development).  The tumor cell process could probably be moved out.
For the developmental processes ideally we'd have a new branch under developmental process. I am not sure how people annotate tumor cell elimination (and where these annotations shoul.

There are ~400 annotation to both
GO:0001906 cell killing
GO:0012501 programmed cell death
with regulates closure


Test report publishing fails following v3.3.0 release

Hi, I have been using your test report publishing scripts in several projects. Today you released a new version and since then the publishing fails.

It seems to have something to do with the summary input, but this input is described as optional in the documentation.

@bogdanbranisteanu thank you for the report. Are you using the specific version @v3.3.0 or the higher level tag @v3?
Could be related to: https://github.com/mikepenz/action-junit-report/blob/main/src/annotator.ts#L140-L143
But the summary was already in use on v3.1.0 too https://github.com/mikepenz/action-junit-report/blob/v3.1.0/src/main.ts#L181 🤔
Is this on an open source repo? E.g. GitHub Cloud or enterprise server?

Tried with both @v3.3.0 and @v3 and it was failing. Now changed to @v3.2.0 and it works just fine. The projects are on an enterprise server.

@v3 is tagged now on the same level as @v3.3.0 (always verifying this though)
Wonder if it may be due to the upgrade to<EMAIL_ADDRESS>

I've recompiled v3.3.0 with the previous<EMAIL_ADDRESS>version here: https://github.com/mikepenz/action-junit-report/commit/c3ef56bd1c1d7f5a1e8ee7e561369b24efed4ed8
Would you please be so kind to test if that is the cause of the problem.
mikepenz/action-junit-report@c3ef56bd1c1d7f5a1e8ee7e561369b24efed4ed8

(generally speaking commit hash pinning is from a security perspective advised - https://docs.github.com/en/actions/security-guides/security-hardening-for-github-actions#using-third-party-actions)

It's still failing.

@bogdanbranisteanu thank you for trying this variant.
What seems strange, it should fail also on v3.2.0 given that it also posts a job summary.
I am sorry that I have to rely on you testing this - Really appreciate your help.
Prepared a new commit which allows to disable the publishing of the job summary at the end:
https://github.com/mikepenz/action-junit-report/commit/2e7e69d112175cca18d6fa2b53566862c24a9f20
mikepenz/action-junit-report@2e7e69d112175cca18d6fa2b53566862c24a9f20

      - uses: mikepenz/action-junit-report@2e7e69d112175cca18d6fa2b53566862c24a9f20
        with:
          job_summary: false

This one works fine.

Published v3.3.1 which offers the APi to disable job_summary's.

I can confirm that all projects can now successfully publish the test reports. Thanks a lot for the cooperation and quick fix!


Error http response at 400 or 500 lvl

Error: Http response at 400 or 500 level The above error occurred in task getBalance created by openWalletFromMnemonic created by takeEvery(wallet/openWalletFromMnemonic, openWalletFromMnemonic) created by rootWalletSaga Tasks cancelled due to error: takeEvery(wallet/openWalletFromMnemonic, openWalletFromMnemonic) takeEvery(wallet/openWalletFromPrivateKey, openWalletFromPrivateKey) takeEvery(wallet/openWalletsFromLedger, openWalletsFromLedger) takeEvery(wallet/addWallet, addWallet) reloadBalanceOnTransaction takeEvery(wallet/fetchWallet, loadWallet) takeLatest(wallet/selectWallet, selectWallet) takeEvery(wallet/closeWallet, closeWallet) Error: Http response at 400 or 500 level at new E (https://wallet.oasisprotocol.org/static/js/2.4b9d1ee8.chunk.js:94905:13) at Y (https://wallet.oasisprotocol.org/static/js/2.4b9d1ee8.chunk.js:96430:33) at oc. (https://wallet.oasisprotocol.org/static/js/2.4b9d1ee8.chunk.js:96404:25) at Ib (https://wallet.oasisprotocol.org/static/js/2.4b9d1ee8.chunk.js:95551:22) at O (https://wallet.oasisprotocol.org/static/js/2.4b9d1ee8.chunk.js:95537:3) at wc (https://wallet.oasisprotocol.org/static/js/2.4b9d1ee8.chunk.js:96058:21) at yc (https://wallet.oasisprotocol.org/static/js/2.4b9d1ee8.chunk.js:96125:9) at oc.push.n.W (https://wallet.oasisprotocol.org/static/js/2.4b9d1ee8.chunk.js:96070:3) at oc.push.n.R (https://wallet.oasisprotocol.org/static/js/2.4b9d1ee8.chunk.js:96066:59)

Thank you for reporting this issue. We have updated our Oasis Wallet with bug fixes and new features which should also solve mentioned issue above.
If you still encounter same or similar issue, please check our FAQ or send an email to our support team at<EMAIL_ADDRESS>


Issue using make install

I've got an ubuntu v18 running in a VM.  When tying to "make install" the chantools I get the following error
$ sudo make install
 Installing chantools.
GO111MODULE=on go install -v -ldflags "-X main.Commit=v0.5.0" ./...
github.com/guggero/chantools/lnd
github.com/chantools/lnd
# github.com/guggero/chantools/lnd
/usr/lib/go-1.10/src/github.com/guggero/chantools/lnd/channel.go:76:14: cannot use ourSig (type []byte) as type input.Signature in argument to input.SpendMultiSig:
	[]byte does not implement input.Signature (missing Serialize method)
/usr/lib/go-1.10/src/github.com/guggero/chantools/lnd/channel.go:76:14: cannot use theirSig (type []byte) as type input.Signature in argument to input.SpendMultiSig:
	[]byte does not implement input.Signature (missing Serialize method)
# github.com/chantools/lnd
/usr/lib/go-1.10/src/github.com/chantools/lnd/channel.go:76:14: cannot use ourSig (type []byte) as type input.Signature in argument to input.SpendMultiSig:
	[]byte does not implement input.Signature (missing Serialize method)
/usr/lib/go-1.10/src/github.com/chantools/lnd/channel.go:76:14: cannot use theirSig (type []byte) as type input.Signature in argument to input.SpendMultiSig:
	[]byte does not implement input.Signature (missing Serialize method)
Makefile:69: recipe for target 'install' failed
make: *** [install] Error 2

Any ideas?

As the README states:

make sure you have go 1.13.x (or later) installed

From your logs it looks like you're using go 1.10.


[#496] New package suffix for the app builds

Created new gradle.properties attribute
Improved app/build.gradle to support the attribute
Let Manifest file work with the new placeholder app name field
Added new app name to strings.xml

The solution doesn't change the string/app_name usage in the rest of the code (i.e. screens), although I had a solution with new getAppName() extension function in Spackle lib. But it'd probably require to embed the dev information in to the BuildConfig and add names for both regular and dev builds to spackle/res/strings too.
Closes https://github.com/zcash/secant-android-wallet/issues/496.
This code review checklist is intended to serve as a starting point for the author and reviewer, although it may not be appropriate for all types of changes (e.g. fixing a spelling typo in documentation).  For more in-depth discussion of how we think about code review, please see Code Review Guidelines.
Author

[x] Self-review: Did you review your own code in GitHub's web interface? Code often looks different when reviewing the diff in a browser, making it easier to spot potential bugs.
[ ] Automated tests: Did you add appropriate automated tests for any code changes?
[ ] Manual tests: Did you update the manual tests as appropriate? While we aim for automated testing of the application, some aspects require manual testing. If you had to manually test something during development of this pull request, write those steps down.
[ ] Code coverage: Did you check the code coverage report for the automated tests?  While we are not looking for perfect coverage, the tool can point out potential cases that have been missed. Code coverage can be generated with: ./gradlew check for Kotlin modules and ./gradlew connectedCheck -PIS_ANDROID_INSTRUMENTATION_TEST_COVERAGE_ENABLED=true for Android modules.
[ ] Documentation: Did you update documentation as appropriate? (e.g README.md, etc.)
[x] Run the app: Did you run the app and try the changes?
[ ] Screenshots: Did you provide before and after UI screenshots in the description of this pull request?  This is only applicable for changes that modify the UI.
[x] Rebase and squash: Did you pull in the latest changes from the main branch and squash your commits before assigning a reviewer? Having your code up to date and squashed will make it easier for others to review. Use best judgement when squashing commits, as some changes (such as refactoring) might be easier to review as a separate commit.

Reviewer

[x] Checklist review: Did you go through the code with the Code Review Guidelines checklist?
[x] Ad hoc review: Did you perform an ad hoc review?  In addition to a first pass using the code review guidelines, do a second pass using your best judgement and experience which may identify additional questions or comments. Research shows that code review is most effective when done in multiple passes, where reviewers look for different things through each pass.
[ ] Automated tests: Did you review the automated tests?
[ ] Manual tests: Did you review the manual tests?
[ ] How is code coverage affected? We encourage you to compare coverage before and after changes and when possible, leaving it in a better place.
[x] Documentation: Did you review Docs, README.md, and Architecture.md as appropriate?
[ ] Run the app: Did you run the app and try the changes? While the CI server runs the app to look for build failures or crashes, humans running the app are more likely to notice unexpected log messages, UI inconsistencies, or bad output data. Perform this step last, after verifying the code changes are safe to run locally.

I pushed some changes to allow hiding the debug suffix for our screenshot tests, since eventually I think we'll use those for marketing/or app store display.  I'm waiting for the CI job to run, to make sure I got the suffix cleared properly for CI jobs.


Verify parity of data-path configuration attribute

Both dlme-airflow and dlme-transform rely on the data-path value to match in their individual configurations.
For example: https://github.com/sul-dlss/dlme-airflow/blob/main/catalogs/penn.yaml#L8 must match https://github.com/sul-dlss/dlme-transform/blob/main/config/metadata_mapping.json#L1494 as dlme-airflow uses this for the export path and dlme-transform uses it for the import path.

Closed by #177
Differences between airflow and transform have been discussed and will be ticketed separately.


Bad timezone DST related handling

Somewhere in the bowels of PhantomJS there's a bug with handling timezone DST changes.
To see it use the following configuration:

use the moment library (saw it with version 2.10.3)
set your local timezone to 'America/Edmonton' (possibly by setting TZ='America/Edmonton' on the command-line before running PhantomJS
run the following code:

for (var i = 1; i < 11; ++i) {
    console.log('hour ' + i + ':', moment('2016-03-13').hour(i));
}

there was a 2 --> 3 DST change in that time-zone on that day, so when you run something like this in node.js or Firefox, you get the following results:

i --> hour
1 --> 1
2 --> 3 (the only one changed!)
3 --> 3
4 --> 4

however, under PhantomJS you get results like these:

i --> hour
1 --> 1
2 --> 3 (changed!)
3 --> 4 (changed!)
4 --> 5 (changed!)
5 --> 6 (changed!)
6 --> 7 (changed!)
7 --> 8 (changed!)
8 --> 9 (changed!)
9 --> 9
10 --> 10

Now I have not taken the time to research this further, and in theory it could be something that moment is doing internally that is interacting badly with PhantomJS code, but it's strange that this happens only with PhantomJS while not with any other browser I've tested or with node.js.
Hope this helps.
[I hoped to find the time to research this a bit more and find out exactly which native Date operations get performed by moment in those .hour() calls, but unfortunately have not found it yet. However, if anyone does want to take a look, I don't expect that part to be difficult.]

I have also come across a similar DST issue but in native JavaScript code.  I have seen it with the Date constructor as in the following example.  I have also seen it when used with Date#setFullYear on dates that on not in DST but the new year is in DST.
Let TZ=America/Denver.
var dst, std;
dst = new Date(2008, 2, 9, 3);
if (/central/i.test(dst.toString())) {
  // The following fails in PhantomJS 2.1.1.
  expect(dst.getTimezoneOffset()).toBe(300);
  expect(dst.toISOString()).toBe('2008-03-09T08:00:00.000Z');
  expect(dst.getTime()).toBe(1205049600000);
}
else if (/mountain/i.test(dst.toString())) {
  // The following fails in PhantomJS 2.1.1.
  expect(dst.getTimezoneOffset()).toBe(360);
  expect(dst.toISOString()).toBe('2008-03-09T09:00:00.000Z');
  expect(dst.getTime()).toBe(1205053200000);
}
...
dst = new Date(2008, 2, 9, 8);
console.log(dst.toString());
if (/central/i.test(dst.toString())) {
  // The following fails in PhantomJS 2.1.1.
  expect(dst.getTimezoneOffset()).toBe(300);
  expect(dst.toISOString()).toBe('2008-03-09T13:00:00.000Z');
  expect(dst.getTime()).toBe(1205067600000);
}
else if (/mountain/i.test(dst.toString())) {
  // The following fails in PhantomJS 2.1.1.
  expect(dst.getTimezoneOffset()).toBe(360);
  expect(dst.toISOString()).toBe('2008-03-09T14:00:00.000Z');
  expect(dst.getTime()).toBe(1205071200000);
}

dst = new Date(2008, 2, 9, 9);
console.log(dst.toString());
if (/central/i.test(dst.toString())) {
  // The following does NOT fail in PhantomJS 2.1.1.
  expect(dst.getTimezoneOffset()).toBe(300);
  expect(dst.toISOString()).toBe('2008-03-09T14:00:00.000Z');
  expect(dst.getTime()).toBe(1205071200000);
}
else if (/mountain/i.test(dst.toString())) {
  // The following fails in PhantomJS 2.1.1.
  expect(dst.getTimezoneOffset()).toBe(360);
  expect(dst.toISOString()).toBe('2008-03-09T15:00:00.000Z');
  expect(dst.getTime()).toBe(1205074800000);
}

Study the example above and you may notice a pattern.  The further the offset of the timezone is from UTC, the more dates are incorrect.  Notice that central does NOT fail for new Date(2008, 2, 9, 9).

Reproduced this with code:
phantomjs> var p3 = new Date(1427590740000);
undefined
phantomjs> p3
"2015-03-29T00:59:00.000Z"
phantomjs> p3.getSeconds();
0
phantomjs> p3.setSeconds(1);
1427587141000
phantomjs> p3
"2015-03-28T23:59:01.000Z"
phantomjs>
So just using setSeconds throws hours to previous day.


add basics one

Created python directory and added a hello world statement for basics one

Well-done LeoMcBills


Support for resolving latest.release of artifacts

Before moving to Coursier for resolving dependencies it was possibly to e.g.
import $ivy.`group-id:artifact-id:latest.integration`

to fetch the latest version. This has now gone. Please bring it back once https://github.com/coursier/coursier/issues/209 is resolved.

The issue you referred to has been solved. Ammonite 1.6.9 supports latest.integration and latest.release. This issue can be closed.


User - be provided with translation - write comments in prefer language and easily read more comments

As a user, I want the app to provide a translation function so that I can write my comments in the language I want and easily read more comments written in different languages.

Estimate: 8 Hours
Acceptance Criteria:

[x] A translation option is available below each comment and topic content.
[x] Once click the translation option, the original text will be replaced by translated one, and an optional for displaying the original text will replace the translation option.

commit ae67805af0d09eaffeed1dd5dfcfd10c0eb56157


Server becomes unresponsive because max_connections is reached during read

Question
When I run a couple of select queries that try to find rare terms on column indexed by tokenbf, I see server readiness probe start to fail on kubernetes because a lot of sockets are opened on the server side for rpc calls. Server also becomes unresponsive to all tcp calls.

After a few minutes, they mostly recover. Breakdown of the sockets for server-0 for example:
1318 byconity-vw-vw-def
697 10-64-116-211.byco
180 ip-10-64-66-224.u
142 ip-10-64-231-57.u
77 ip-10-64-166-98.u
73 s3-us-west-2-r-w.
34 ip-10-64-231-57.us
28 ip-10-64-66-224.us
22 ip-10-64-166-98.us
so a lot of sockets opened to the read workers on servers. Is there a way to limit this to leave server functional? What causes new sockets to be opened for read workers?

Hi @ozcelgozde, thank you for report this issue. Let us investigate this

Hi @jenrryyou , please help to see why there are too many number of brpc connection open?

Hi @ozcelgozde , our developer are not sure where is those high number of rpc come from. We think that it is not come from brpc. To monitor the number of rpc_socket_count we can scrape it from url http://pod_ip:rpc_port/vars or http://pod_ip:rpc_port/brpc_metrics for Prometheus. Can you make a graph and see if the rpc really cause by brpc

Actually what u said looks to be correct, the problem seems to be coming from the tcp connections and not the rcp connections.

Let me dig deeper

I notice a lot of http requests:

And this causes Poco to throw Got exception while starting thread for connection.No thread available. From what I can trace thru the code, this is set to 16 by default and I couldnt find a way to change it do you have an idea?

A few samples:
2024.03.08 15:22:21.065071 [ 11817 ] {}  Catalog: Finish set commit time for txn<PHONE_NUMBER>70231913, elapsed 8 ms.
Got exception while starting thread for connection. Error code: 0, message: 'No thread available'
2024.03.08 15:22:21.173052 [ 7038 ] {}  CnchLock: acquire 1 locks in 2 ms
Got exception while starting thread for connection. Error code: 0, message: 'No thread available'
As you can see it blocks everything :)

A few samples: 2024.03.08 15:22:21.065071 [ 11817 ] {} Catalog: Finish set commit time for txn<PHONE_NUMBER>70231913, elapsed 8 ms. Got exception while starting thread for connection. Error code: 0, message: 'No thread available'
2024.03.08 15:22:21.173052 [ 7038 ] {} CnchLock: acquire 1 locks in 2 ms Got exception while starting thread for connection. Error code: 0, message: 'No thread available'
As you can see it blocks everything :)

Hi @ozcelgozde , thank you for your cooperation. There should be no interaction between workers and servers via http. I wonder if the http connections come from liveness check or metrics scraping like Prometheus

And may I know in which place you see that it is set to 16?

And could you tell how do you find out large number of connection is http? I think maybe the way you did may have a mistake

mentioned in #1153

I traced 16 from contrib/pocpFoundation/src/ThreadPool.cpp
PooledThread* ThreadPool::getThread()
{
	FastMutex::ScopedLock lock(_mutex);

	if (++_age == 32)
		housekeep();

	PooledThread* pThread = 0;
	for (ThreadVec::iterator it = _threads.begin(); !pThread && it != _threads.end(); ++it)
	{
		if ((*it)->idle())
			pThread = *it;
	}
	if (!pThread)
	{
		if (_threads.size() < _maxCapacity)
		{
			pThread = createThread();
			try
			{
				pThread->start();
				_threads.push_back(pThread);
			} catch (...)
			{
				delete pThread;
				throw;
			}
		}
		else
			throw NoThreadAvailableException();
	}
	pThread->activate();
	return pThread;
}

I couldnt find anywhere we set the max capacity and default is 16 so I assumed

cnch_current_metrics_http_connection

I did not find this metrics name in ByConity source code. btw, are your cluster using S3 storage. Then I think the number of http connection may related to S3 storage

yes, I'm using S3

yes, I'm using S3

The S3 should not related here because the the S3 client will send http request from workers only. I think if you encounter the issue again, could you help to execute the command netstat on the server to see the source of the connection and its corresponding port. That should be the way to identify if the connection is HTTP or not. Maybe you can post the output of netstat command here so we could analyse together

Here is some of the command I use with netstat to quickly count the number of http request
$ netstat --tcp | grep "ESTABLISHED" | grep "18685"
tcp6       0      0 localhost:18685         localhost:31556         ESTABLISHED
tcp6       0      0 localhost:31556         localhost:18685         ESTABLISHED

My http port is 18685, and you can see there are 2 sockets because i connect to the server from local

I was finally able to reproduce it reliably when I send a lot of queries over clickhouse client at once.  This, as expected, makes transaction and tcp socket count spike. netstat also reflects a lot of tcp connections. A few errors I can see from read and server replicas are:
Failed to query, err: couldn't query clickhouse, query id: 30c83f8c-e23b-11ee-892c-02c7f6dbdbda, got err: "code: 2010, message: Query [30c83f8c-e23b-11ee-892c-02c7f6dbdbda] failed with RootCause: SegmentId: 0, ErrorCode:2010, Message: Fail to call DB.Protos.RegistryService.registry, error code: 2001, msg: [E2001][<IP_ADDRESS>:123456789]Create stream ExchangeDataKey[448383008663142595_1_0_18446744073709551615] for query 30c83f8c-e23b-11ee-892c-02c7f6dbdbda failed by exception: Code: 2010, e.displayText() = DB::Exception: Interrput accept for ExchangeDataKey[448383008663142595_1_0_18446744073709551615] SQLSTATE: HY000 (version <IP_ADDRESS>); \n AdditionalErrors: SegmentId: 1, ErrorCode:2010, Message: Worker host:<IP_ADDRESS>:8124, exception:Code: 2010, e.displayText() = DB::Exception: Fail to call DB.Protos.RegistryService.registry, error code: 1008, msg: [E1008]Reached timeout=10000ms @<IP_ADDRESS>:8124 SQLSTATE: HY000 (version <IP_ADDRESS>)  SQLSTATE: HY000"

Failed to query, err: couldn't query clickhouse, query id: 30c81674-e23b-11ee-8918-02c7f6dbdbda, got err: "read: read tcp <IP_ADDRESS>:59968-><IP_ADDRESS>:9000: i/o timeout"

Failed to query, err: couldn't query clickhouse, query id: a55e6764-e23a-11ee-b252-02c7f6dbdbda, got err: "read: EOF"

Is there a way to know what is my simultaneous query limits over tcp?

I was finally able to reproduce it reliably when I send a lot of queries over clickhouse client at once.  This, as expected, makes transaction and tcp socket count spike. netstat also reflects a lot of tcp connections. A few errors I can see from read and server replicas are:
Failed to query, err: couldn't query clickhouse, query id: 30c83f8c-e23b-11ee-892c-02c7f6dbdbda, got err: "code: 2010, message: Query [30c83f8c-e23b-11ee-892c-02c7f6dbdbda] failed with RootCause: SegmentId: 0, ErrorCode:2010, Message: Fail to call DB.Protos.RegistryService.registry, error code: 2001, msg: [E2001][<IP_ADDRESS>:123456789]Create stream ExchangeDataKey[448383008663142595_1_0_18446744073709551615] for query 30c83f8c-e23b-11ee-892c-02c7f6dbdbda failed by exception: Code: 2010, e.displayText() = DB::Exception: Interrput accept for ExchangeDataKey[448383008663142595_1_0_18446744073709551615] SQLSTATE: HY000 (version <IP_ADDRESS>); \n AdditionalErrors: SegmentId: 1, ErrorCode:2010, Message: Worker host:<IP_ADDRESS>:8124, exception:Code: 2010, e.displayText() = DB::Exception: Fail to call DB.Protos.RegistryService.registry, error code: 1008, msg: [E1008]Reached timeout=10000ms @<IP_ADDRESS>:8124 SQLSTATE: HY000 (version <IP_ADDRESS>)  SQLSTATE: HY000"

Failed to query, err: couldn't query clickhouse, query id: 30c81674-e23b-11ee-8918-02c7f6dbdbda, got err: "read: read tcp <IP_ADDRESS>:59968-><IP_ADDRESS>:9000: i/o timeout"

Failed to query, err: couldn't query clickhouse, query id: a55e6764-e23a-11ee-b252-02c7f6dbdbda, got err: "read: EOF"

Is there a way to know what is my simultaneous query limits over tcp?

We have settings to limit the number of query like max_concurrent_queries_for_all_users, but the capacity is depend on the implementation. But the issue of sending too many queries is different from the issue you tell from the start. Like we are interest where are so many HTTP connections come from?

A lot of HTTP connections come from HTTP insert. We have ingestion over http, which on peak times causes the same effect I would think.

A lot of HTTP connections come from HTTP insert. We have ingestion over http, which on peak times causes the same effect I would think.

I see, I've tried to send many queries to reproduce and also encounter the resource issue that thread can't be created. We are going to merge some MR to improve the QPS but I'm not sure if it gonna change much.

Thank you @dmthuc for your help and interest!


Desktop or embedded?

Desktop or embedded?

Please elaborate your question. What is your actual use case?

This crate is meant to be used on embedded devices to implement a CDC serial port. If you want to access such a port from a normal computer, you can use e.g. https://crates.io/crates/serialport

Thanks! I'm looking for such crate for hours!


Someone donated? Who?

Looks like there has been a regression with the webhook/slack integration.

Previously these people were named in the Slackbot message.

Thanks @ghuntley we'll look into it.


BigInt needs to implement num and operate on num

I was looking at converting the test tests/kernel/unsorted/loop_test.dart to the new 64-bit limit on integer literal.
fact(n) {
  var f = 1;
  while (n > 0) {
    f *= n;
    --n;
  }
  return f;
}

...

  Expect
      .isTrue(fact(42) ==<PHONE_NUMBER>752879898543142606244511569936384000000000);

I'd like to update this test to the 64-bit overflow semantics, and to preserve the original BigInt test, that is:
  Expect.isTrue(fact(new BigInt.from(42)) ==
      BigInt.parse("1405006117752879898543142606244511569936384000000000"));
  Expect.isTrue(fact(3.14159) == 1.0874982674320444);

Unfortunately, this doesn't work because BigInt.> doesn't accept a num (and throws when compared to 0).
This leads me to conclude that updating existing code to work with BigInt is going to be really hard unless BigInt is modified to implement num.

I'm marking this as P1 as I believe this issue needs to be resolved before shipping Dart 2.0. Otherwise, please just close it.

@floitschG @lrhn

It is quite inconvenient. I decided not to try and support BigInt in Intl at the moment. It works fine with num, Int64, and MicroMoney, but those support operations like dividing by num.

I would love to get this into Dart2. It makes working with BigInt much more easy and removes a lot of code fuzz

@alexmarkov
Please re-evaluate this and do one of the following:

Add it to a milestone if it is still P1
Change priority label and add milestone if no longer P1
Close, if this issue is no longer needed

FWIW I think this is nice to have, but it is not P1.
This improvement falls into the core library area, so I'll defer to @lrhn or @leafpetersen .

We don't have any current plans to make BigInt implement num.
Implementing num is not without cost. For example, compiling to JavaScript can assume that any num is a JavaScript number and treat it more efficiently. If a num can also be a BigInt, then every num + num  operation in JavaScript would potentially have to check both operands for being BigInt before taking the efficient path.
We would also have to specify what BigInt + double and BigInt + int (and vice versa) evaluates to. Likely double for BigInt + double and BigInt for BigInt + int, but in JavaScript, integers are also doubles, so that could easily introduce subtle errors.
So, no current plan, not expecting this to happen unless something changes (like JavaScript getting both efficient integers and big integers)


[FLINK-19758][filesystem] Implement a new unified file sink based on the new sink API

What is the purpose of the change
This pull requests implementations a new File sink based on the new sink API.
Brief change log
af69ad89405936040b55d54acb0ef18e6141e5ad implements the sink.
Verifying this change
This change added tests and can be verified as follows:

Unit tests for each components for the new sink.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): yes
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
The S3 file system connector:  no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? not applicable

@flinkbot run azure

Merged!


Flex box grid does not support offsets

As per the float based grid - we need the ability to offset columns to position content on the grid

Sounds like it would be useful. We'll tag it as a feature for a upcoming release.

Flexbox uses SIZE-order-N classes. Is that what you're after?

@ivanjaros no - offsetting the columns as per this example
@rafibomb all you need to add is this to get it back. I found the mixin architecture a bit baffling or I would have added myself and made a PR :)
`/* offsets */
.large-offset-1, .medium-offset-1, .small-offset-1 {
margin-left: 8.333%; }
.large-offset-2, .medium-offset-2, .small-offset-2 {
margin-left: 16.667%; }
.large-offset-3, .medium-offset-3, .small-offset-3 {
margin-left: 25%; }
.large-offset-4, .medium-offset-4, .small-offset-4 {
margin-left: 33.333%; }
.large-offset-5, .medium-offset-5, .small-offset-5 {
margin-left: 41.667%; }
.large-offset-6, .medium-offset-6, .small-offset-6 {
margin-left: 50%; }
.large-offset-7, .medium-offset-7, .small-offset-7 {
margin-left: 50%; }
.large-offset-8, .medium-offset-8, .small-offset-8 {
margin-left: 66.667%; }
.large-offset-9, .medium-offset-9, .small-offset-9 {
margin-left: 75%; }
.large-offset-10, .medium-offset-10, .small-offset-10 {
margin-left: 83.333%; }
.large-offset-11, .medium-offset-11, .small-offset-11 {
margin-left: 91.667%; }`

While we may need to add them we saw the spacing options as a pretty good replacement since thats how we tended to use offsets. We're discussing adding it back for simple feature parody.

Please add it back. It doesn't appear possible to achieve some layouts using spacing instead of offsets.
For example, the following layout on a medium screen places all the inputs on a single line and on a small screen positions inputs 'two' and 'three' nicely aligned under input 'one':

                       label text

                        <input name="one/>

                        <input name="two"/>
                        <input name="three"/>

Done! I think eventually I'll find a way to reuse that code between the two grids, so it's not just being copied and pasted.

If you want to use it as a mixin: @include grid-column-offset($o);


(cargo-release) version 0.4.0

Motivation

Future Work

Codecov Report

Merging #230 (d51a8de) into main (4c3adae) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #230   +/-   ##
=======================================
  Coverage   89.90%   89.90%
=======================================
  Files          43       43
  Lines        3634     3634
=======================================
  Hits         3267     3267
  Misses        367      367

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


right table location is not getting updated with arguments db-prefix and db-rename

Hi David,
We have been testing db-prefix and db-rename options and right table location do not have the new db name.
our sample command is
hms-mirror -cfg uat-dev.yaml -d SQL -db phoenix_raw -tf fx_house_rates --db-rename 'uat_phoenix_raw' -o /tmp/hms-mirror-dist-latest/working-dir/sql_real_test1/ -slc -sql
hms-mirror -cfg uat-dev.yaml -d SQL -db phoenix_raw -tf fx_house_rates --db-prefix 'uat_' -o /tmp/hms-mirror-dist-latest/working-dir/sql_real_test/ -slc -sql
Can we get this fixed ?

In each of these cases, the database new is created with the appropriate 'new/altered' name.  I think you're referring to the location element of the table create.
hms-mirror uses a literal translation (minus the namespace) when doing the transfers.  And since we can't rely on the 'db' name in the path being accurate, we can't make a assumption to make an adjustment here.
But there is an option.  Use the -rdl|--reset-default-location along with -ewd|--external-warehouse-directory and -wd|--warehouse-directory settings to control where the new data goes.
For example:
hms-mirror -cfg uat-dev.yaml -d SQL -db phoenix_raw -tf fx_house_rates --db-prefix 'uat_' -o /tmp/hms-mirror-dist-latest/working-dir/sql_real_test/ -slc -rdl -wd hdfs://new_namespace/new_root_mngd_location -ewd hdfs://new_namespace/new_root_ext_location
Note: The -sql option has been deprecated.


Regex cleanup

Change unnecessary regex capturing groups to non-capturing groups, so only the desired value is captured. This also eliminates the need to specify an index because 're.findall' no longer returns a list.

looks great


Folder structure

Refactored folder structure to be able to include angular stuff

Also added .bowerrc to redirect Angular dependencies under the "public" folder


Is it possible to publish longer prediction?

I believe this was already asked, I was wondering if this has changed at all? As I would like obviously publish a longer prediction with some methods I had in mind.
Thank you,
Montana.

I think projections more than a few weeks out become fairly noisy, and so we want to avoid making projections if we do not feel confident enough in our results. With school reopenings and the start of flu season in October, it is fairly difficult to estimate where things will be, and for that reason we are currently not extending our forecasts beyond November 1. Thanks for understanding!

Makes sense, thank you for the response @youyanggu!


Refactor migrations and add missing fields (first name and last name)

When you ran october:down, it was left fields first name and last name in the table. Now it's fixed + refactored.

Thank you!


Vector2 and Vector2IO have duplicate toStateObject and fromStateObject methods

Vector2 and Vecto2IO both have the same lines of code, we probably don't want that logic in both places, but it is hard to tell the usages of  Vector2.toStateObject.

They also have duplicate fromStateObject methods.

From https://github.com/phetsims/graphing-quadratics/issues/38#issuecomment-426442151:
That looks good. I think that the level of verbosity is appropriate. We often to refer to these types of objects as "value types", but I think data structure is good too.
@samreid why are toStateObject and fromStateObject directly on the types for Vector2 and Quadratic. That feels like an antipattern to me, could we use phetsims/phet-io#1373 to make things more consistent?
Like vector2.phetioType.toStateObject()

Defining toStateObject and fromStateObject directly on the wrapped type (e.g. Vector2, Color, Quadratic) is far from an anti pattern.  It's the pattern called encapsulation.  Rather, putting them on the IO type (e.g. Vector2IO, ColorIO, QuadraticIO) is the anti pattern; it requires exposing implementation details of the wrapper type to the IO type, duplication documentation, information spread out across multiple files,... and an implementation that is inherently more problematic to maintain.

For Vector2 I agree it makes the most sense to move these methods from Vector2IO to Vector2.  Leaving assigned to @zepumph for review/discussion.  Anything else to do here?

That looks good for Vector2. I wonder if we may use this same approach in the future for other value types like RangeIO or Bounds2IO.

We don't have a need for that now though, closing.


fix: Improve enclave and userop error messages

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR focuses on improving error messages throughout the thirdweb package, specifically in various enclave actions and test files. It enhances clarity by including status codes and messages in the error handling.
Detailed summary

Improved error messages in:

sign-message.enclave.ts
generate-wallet.enclave.ts
sign-typed-data.enclave.ts
sign-transaction.enclave.ts
userop.ts

Changed chain definition from defineChain(531050104) to arbitrumSepolia in smart-wallet-dev.test.ts.
Updated test cases to remove .skip from some tests and added logging for signatures.
Commented out the setThirdwebDomains function in tests.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

#5653  👈 (View in Graphite)
main

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


Correlation function measurement

Hello,
I recently used this package to calculate a Hubbard model's ground state. I tried to measure the correlation function just as the tutorial did, then the error comes out that the function "analysed_energy" is not in "pauxy.analysis.correlation". I checked the source function and there is indeed no function as "analysed_energy“ there. Could anyone check this problem? Maybe the current version of pauxy in the source code is not the same as the one used in the tutorial? Thank you!

Hi Pauxy is deprecated in favour of ipie. This code is no longer maintained.