availability sets example

the doc says:
'Let’s consider a typical VM-based solution where you might have four front-end web servers and use 2 back-end VMs that host a database.'
Do these two VMs host a single database or two separate databases?
In case of a single database, what is the way to synchronize data between these two VMs?
In case of two separate databases, created availability set doesn't help me when one of the two VMs has issues, because the remaining VM hosts database which data is not the same as of database on VM with issues.
Pls. clarify what do you mean here.
In case of four web-servers, each running on its own VM, availability set does the job since web-servers usually don't keep data and shouldn't be in sync.

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

ID: a57ffc39-d1a4-77f7-d78a-415db2deeae7
Version Independent ID: 7ec4a1b0-6545-97e5-449c-f5e72df0242e
Content: Tutorial - High availability for Windows VMs in Azure
Content Source: articles/virtual-machines/windows/tutorial-availability-sets.md
Service: virtual-machines-windows
GitHub Login: @cynthn
Microsoft Alias: cynthn

Thanks for the question! We are currently investigating and will update you shortly.

@alexeyshishkin01 From my understanding, the example implies - two VMs host a single database.
For the question, how to sync two VMs, here is a thread that talks about the options: https://stackoverflow.com/questions/25533053/possible-to-keep-two-vhds-in-sync-on-azure-vms
Here is the document on Azure File service : https://docs.microsoft.com/en-us/azure/storage/files/storage-how-to-create-file-share
@cynthn Can you please confirm on the example in the document.

my question was about two VMs that host a single database.
your example is about web application, which is different from database.
it means, your example doesn't relate to my question at all.
pls. note I'm not talking about specific OS - it can be either Linux (most probably) or Windows.

@alexeyshishkin01 It was just an example of when you might want to use availability sets. I'll remove the reference from the doc. Thank you!

#please-close

I have to reopen it, because the doc made me confused about availability set usage.
The doc should be clear enough in order not to spend the time re-asking about the content.
What I'd like you to do is:

make clear enough that in the example four VMs running web-servers are independent from each other and their VM data doesn't have to be in sync
two VMs running single database have to have sync data, but in this case there's immediate question - how to do it?
provide an example or link of (a)synchronous replication between two databases, say MS SQL Server
the other immediate questions - how web servers connect to database? which VM? load-balancing or virtual private address? etc.
pls. don't mention file share to use with databases - it simply doesn't work with databases

@alexeyshishkin01 thanks for the feedback. The article is only meant as a very brief introduction to the availability set feature. The "example" as it was written was just to give some context around one application for availability sets. I realized that this was getting a bit to specific, so I took out the reference to databases and left it with just a generic "back-end". For more detailed information on production deployments, I would suggest looking into the docs for the specific database implementation. Unfortunately, database syncing is way outside the scope for this doc :)


Refactor module deprovisioning in btp-manager

Currently the deprovisioning process in btp-manager relies on the GroupVersionKinds found in the chart:
https://github.com/kyma-project/btp-manager/blob/main/controllers/btpoperator_controller.go#L768
We can refactor it to delete applied resources from module-resources/apply

PR: https://github.com/kyma-project/btp-manager/pull/193

PR with addition of the outdated resources deprovisioning: https://github.com/kyma-project/btp-manager/pull/201


feature: provide hdfs yaml configuration file

What's changed and what's your intention?
In the previous PR, we support the hdfs as storage in the operator. But at that time, because there are some bugs in opendal in the kernel. We only add the HDFS feature in the operator, but cannot provide an example. Recently, the kernel fix the problem, so this PR update the hdfs example yaml file.
Checklist

[ ] I have written the necessary docs and comments
[ ] I have added necessary unit tests and integration tests

Refer to a related PR or issue link (optional)

@arkbriar I just updated it and used the multi-arch image.


Section 2: Description of the data

You are allowed to select any dataset you want for this project, as long as you have the license to use it publicly. Warning: finding a good data set can take a lot of time and effort. We therefore recommend that you select one that you have worked with in a previous lab in MDS and that you are already familiar with (for example the Gapminder, movie, or the dataset you use for your project 522).

Task completed.


Tooltip not showing on the popup view on firefox browser

Describe the bug
Tooltip not showing on the popup view on firefox browser
To Reproduce
Steps to reproduce the behavior:

Open the extension (popup view)
Check tooltip when hover:

Show/hide balance icon
? icon in Send Fund screen
Transaction history
...

Actual: Tooltip not showing
Expected behavior: Show tooltip

@Quangdm-cdm check tooltip on Expand view (All Browser) when hover Show/Hide balance after fix issue: #168


Disable Hardware Acceleration

Actually I want to disable the Hardware Acceleration in VS Code is there any to disable this one.

@saileshkush95 code --disable-gpu from the command line?

Related to this - I've just discovered that launching Code (insiders) with the --disable-gpu flag, on Windows 10 (running in a VMWare VM) improvs performance TREMENDOUSLY. Scrolling, syntax highlighting, etc is MUCH faster.


Add config & train the 6.8B model

closes #214
Trained model and results are available here.
Runtime estimates are here.

Is the plan that we will add new configs each time and keep them in this code base, or should we just have a template config as an example which we edit but don't commit? I don't mind either way, but the config record will be saved on wandb anyway during the training run, so it isn't strictly necessary to add it to the code base I guess?

I like having one recommended configuration for each size similar to how Pythia did it so a new model trainer can just grab the most appropriate configuration straight away without doing a lot of the tweaking to find optimal batch sizes, DeepSpeed stage version, etc. But I'd say there's no need to commit a 6.9B_v1, 6.9B_v2, 6.9B_v3, etc. What do you think?


Windows & maximum number of host aliases per line

Hi!
It looks like Windows support only up to 9 aliases per line.
More info on this here.
My VVV tries to fit in there around 70 😄
Anyway we can have goodhosts break them down to multiple lines?

This is a bug for the cli tool, the plugin is just a wrapper around it.
Can you open a ticket here -> https://github.com/goodhosts/cli


Billing - STRIPE - Payment method - Billing_details

payment failure events (from STRIPE) dumps additional information like the billing_details:
Let's try to populate this information when creating the payment method.
I'm not sure if this should be done server-side (or client-side).
As of today, the name shown below as been set client side !

payment failure events (from STRIPE) dumps additional information like the billing_details:
Let's try to populate this information when creating the payment method.
I'm not sure if this should be done server-side (or client-side).
As of today, the name shown below as been set client side !

Is this related to the user created in Stripe by e-Mobility?
In that case you should provide the user's address in e-Mobility to Stripe (even make it mandatory to the users when the billing is active.)
And when you create a payment method and use it, I would expect the user's address to be provided in the billing_details property, right?

payment failure events (from STRIPE) dumps additional information like the billing_details:
Let's try to populate this information when creating the payment method.
I'm not sure if this should be done server-side (or client-side).
As of today, the name shown below as been set client side !

Is this related to the user created in Stripe by e-Mobility?
In that case you should provide the user's address in e-Mobility to Stripe (even make it mandatory to the users when the billing is active.)
And when you create a payment method and use it, I would expect the user's address to be provided in the billing_details property, right?

needs some investigation ... sounds like stripe gets the information from the "payment_method" itself, not from the user?!??!?

FYI: The country information in stripe has to be a two-character string: FR, US, etc ...
When a string such as 'France' is used some of their endpoints trigger exceptions.
We need to find a way to convert the country string to a consistent country code ...
Strange enough but a wrong value is not refused when populating the customer address!!! - to be clarified!

This issue has been solved backend side when synchronizing user/customer data and when creating a new payment method.
c.f.: PR: https://github.com/sap-labs-france/ev-server/issues/2466
I'm closing this one


[ENH] Describe arbitrary units in Common Principles

Closes #580. Although I considered adding something to Appendix 5 (Units), it didn't seem to fit well with the contents of the Appendix, so I've limited this change to a single list item in Common Principles#Units.
Changes proposed:

Add an item to the additional rules list in Common Principes#Units describing how arbitrary units/unitless data should be handled.

@tsalo thanks for the PR. Can you go one more step (two actually :wink: ) and check that this new BIDS definition is observed in BEP009 and BEP001?

@sappelhoff There's a call this week for BEP001 where I plan to bring this up. I will also comment on BEP009 directly.


#pragma once is not optimized on GCC

Your stuff might want to mention this long-standing GCC bug:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58770
On a big tree it is certainly slower than internal #ifndef guards.

Thank you for pointing this out! I didn't know about this issue and it didn't show in these tests presumably because I still have a very low number of unique header files.  I've made a comment in this repo https://github.com/IncludeGuardian/multiple-inclusion-optimization-tests/commit/709d48d59f22d30a96f7c01d6d0d38e52124e734 to mention this issue.
I will try and take a look to see if I can submit a fix for GCC and then update the article that corresponds to the finding in this repo.


fix(fromEvent): pass options in unsubscribe

Description:
This PR includes the same fix as #3350, but targets the stable branch.
The PR cherry picks a commit from #3350 (that adds an expectation to a fromEvent test) and changes FromEventObservable so that the test passes.
The fix in #3350 was rebased to account for refactorings that were made to fromEvent after the PR was opened. I guess the issue is something that ought to be fixed in stable, too.
Related issue (if exists): #3349

Coverage remained the same at 97.4% when pulling f0d6024a3cb4a851d60c4e9debb61a1c67c72e1c on cartant:issue-3349-stable into e2cd3a2b3115de5b038380288a7dcbfe2a7f9c4d on ReactiveX:stable.


Is there an example of VSS.getServiceContribution()?

I have a question, but no answer, no sample reference, can you help me?
const contributionId: string = "ms.vss-work-web.fields-allowed-values-provider";
VSS.getServiceContribution(contributionId).then((serviceContribution: IServiceContribution) => {
	const context: WebContext = VSS.getWebContext();
	serviceContribution.getInstance(serviceContribution.id, context).then(instance => {
		//TODO: instance is null

		//do something...
	})
});

Instance is null !!! What do I seem to have missed?
I'm sure this contribution exists.

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

ID: f699a190-5e7e-1103-8d9d-c3d58e698e3a
Version Independent ID: 1e54fe20-7e4d-d5ff-1682-8659f7a8fba8
Content: Core Client SDK - Azure DevOps
Content Source: docs/extend/reference/client/core-sdk.md
Product: devops
Technology: devops-ecosystem
GitHub Login: @chcomley
Microsoft Alias: chcomley

@VAllens  Thank you for the feedback, please see if this example helps.
I can assign this to the author, though please note this forum is for documentation only.
For any help related to support requests, please refer to either:

Visual Studio community
Visual Studio on Stack Overflow

Hi @VAllens, please let me know whether @msebolt's example worked for you.

I saw this in VSS.SDK.js:
    /**
    * Get a contributed service from the parent host.
    *
    * @param contributionId Full Id of the service contribution to get the instance of
    * @param context Optional context information to use when obtaining the service instance
    */
    function getService(contributionId, context) {
        if (!context) {
            context = {};
        }
        if (!context["webContext"]) {
            context["webContext"] = getWebContext();
        }
        if (!context["extensionContext"]) {
            context["extensionContext"] = getExtensionContext();
        }
        return getServiceContribution(contributionId).then(function (serviceContribution) {
            return serviceContribution.getInstance(serviceContribution.id, context);
        });
    }
    VSS.getService = getService;

Thank all, especially @msebolt .


VMWare Workstation/Fusion collocation

https://github.com/ObrienlabsDev/blog/wiki/Developer-Guide#vmware

side channel mitigation off https://knowledge.broadcom.com/external/article?legacyId=79832

On m1max install 24.01 arm without options - do these post install
VMWare Fusion 13.5.2

enable ssh on ubuntu VM


Categories Scroll Column

I figure there must be a better way to do them. I have seen it done better on other websites, so it should be made to look better

completed this with w3-CSS


Clarify "word" character class in 'isk' documentation.

If you do :h 'iskeyword' there will be a phrase:
For '@' characters above 255 check the "word" character class.

The question is what is this "word" character class?
Currently if I have привет мир unicode text in a buffer, I can match a letter with /\k but not with a /\w which I thought is the "word" character class...

If you do :h 'iskeyword' there will be a phrase:
For '@' characters above 255 check the "word" character class.

The question is what is this "word" character class?
Currently if I have привет мир unicode text in a buffer, I can match
a letter with /\k but not with a /\w which I thought is the "word"
character class...

Hmm, I don't think this is clearly specified in the help.  The < and >
regexp items mention start and end of word, which does use a similar
rule.
Best I can think of is "any character that is not white space or punctuation".
--
hundred-and-one symptoms of being an internet addict:
187. You promise yourself that you'll only stay online for another
15 minutes...at least once every hour.
/// Bram Moolenaar --<EMAIL_ADDRESS>-- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

Possibly fixed by https://github.com/vim/vim/commit/4c295027a426986566cd7a76c47a6d3a529727e7
The help at :h 'isk' now says:

For '@' characters above 255 check the "word" character class (any character
that is not white space or punctuation).

Yes, thank you.
I am still a bit confused by a "word" character class mention there as it doesn't match to what is defined for a regex word character class. Or maybe quotes in "word" means it is different?

I don't know.  Maybe "word" character class refers to [[:keyword:]]?  If so, the definition might be circular, because the latter is already defined via 'iskeyword'.
Maybe we could say this instead:

'@' characters above 255 match [^[:space:][:punct:]] (any character
that is not white space or punctuation).

diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 84969b23f..0ed431e9a 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -4563,9 +4563,9 @@ A jump table for the options with a short description can be found at |Q_op|.
 			local to buffer
 	Keywords are used in searching and recognizing with many commands:
 	"w", "*", "[i", etc.  It is also used for "\k" in a |pattern|.  See
-	'isfname' for a description of the format of this option.  For '@'
-	characters above 255 check the "word" character class (any character
-	that is not white space or punctuation).
+	'isfname' for a description of the format of this option.  '@'
+	characters above 255 match `[^[:space:][:punct:]]` (any character that
+	is not white space or punctuation).
 	For C programs you could use "a-z,A-Z,48-57,_,.,-,>".
 	For a help file it is set to all non-blank printable characters except
 	'*', '"' and '|' (so that CTRL-] on a command finds the help for that


Windows Compression Support

There is disabled windows compression due the issue with loading speed. Contact @fcolarich to revalidate a new solution
It's discovered that a compress operation on the same image takes ~x10 time more (200-300 ms vs 2500-3500 ms) in our solution than Compressonator GUI. Seems like we are missing some skew flag in CMP's method call. As an option to fast fix is to integrated CLI tool and pass images via disk and it still will be faster. Another option to try is to tweak NumThreads to 32 in FuseNode
Log in CLI
Processing: hrm
compressonatorcli.exe C:/Users/Fran/Downloads/hrm.png C:/Users/Fran/Downloads/results/hrm.DDS -fd BC7 -NumThreads 32
Processing destination: C:/Users/Fran/Downloads/results/hrm.DDS
Source data size = 4194304 Bytes, width = 1024 px height = 1024 px
Destination data size = 1048576 Bytes Resulting compression ratio = 4.00:1
Compressed to BC7 with 1 iteration(s) in 0.230 seconds
Total time taken (includes file I/O): 0.230 seconds
Done Processing
Processed in 0.24 seconds
====== Compress: 1 succeeded, 0 failed ======

It seems that -NumThreads 32 makes the difference (but why when it's on GPU?)

Relates to https://github.com/decentraland/unity-explorer/issues/2740


Avatar position in hover could be moved downward

Is it possible to move the position of the avatar downward, so that the height of the box is not too high. I feel like there is a gap underneath the avatar that is wasted.

Unfortunately GitLens can't control that positioning. All I can do it affect the size of the avatar. Which you can change by changing the gitlens.hovers.avatarSize setting. Sorry. 😢


chore: update documentation for ainit_document_table function

In this commit we update the documentation for the ainit_document_table function. Previously the documentation said the argument metadata_columns was a list of SQLAlchemy columns. This is incorrect, as we have defined our own Column type.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

/gcbrun


search page can set bigger or  loading more

https://icon-sets.iconify.design/?query=sync

This is changed in new version of website (not published yet). It loads all available results, has dynamic pagination based on current browser window and it can be scrolled.


suggestion: make select/copy-paste a bit easier

thanks again for creating such a useful resource!
i did find copy/pasting a bit finicky so was wondering if you'd considered using github pages to render the docs and customizing a little?
by way of example, i did a quick patch that renders using a tweaked layout and adds a little javascript hack to auto-highlight a complete code block when you click anywhere on it.
the auto-generated site at https://petermd.github.io/kubernetes-the-hard-way/ shows how it would look

This is pretty nice, but I won't have the time to actively maintain this. I'm opening to you hosting such a site.

Sorry Kelsey, hope you don't think I was trying to make more work for you!
Making the /docs tree render as a site is just a github setting, the only change I made is to tweak the default layout and include the "auto-select" javascript.


Support for complex-values problems

It seems that the present version does not support complex-valued problem. Let nlprob be a NonlinearProblem with uType Vector{ComplexF64}. Then
solve(nlprob, NewtonRaphson(), abstol = 1e-9)
yields ArgumentError: Cannot create a dual over scalar type ComplexF64. If the type behaves as a scalar, define ForwardDiff.can_dual(::Type{ComplexF64}) = true.
Is there a way around this?

The default used to be ForwardDiff.jl but now we can do things smarter and chose the AD or Finite Diff based on the problem type. So this shouldn't be an issue!

This can be closed!


Initial cli commands for stack API

This PR adds initial CLI commands for stacks API.
This also fixes a deploy revision related regression and now separates the deployment revision from the service version. Naturally there can be multiple deployments (re-balancing, interval deploy etc.) for a given service version and thus we need to separate these concepts.
We need to further work on the versioning when we actually enable the capability to deploy older version of service/stack.

rebased and cleaned

I will still work on the service_rev vs. deploy_rev thingy before merging this


Upgrade client-go to v6.0.0

Maya should upgrade the client-go to use version 6.0.0

Please go through the following below link so as to solve this issue
https://github.com/kubernetes/client-go/releases/tag/v6.0.0

Please go through the below code so as to solve this problem
client-go-6.0.0.zip

Please find the link https://github.com/kubernetes/kubernetes/issues/57330

@Apollo9999 For this to be considered for the hackfest, can you please fork the repo and raise a Pull Request making the necessary changes required for the upgrade. Once your PR is reviewed and merged you will be eligible for hackfest goodies.

@yudaykiran Please be informed as per your suggestion I made fork of openebs/maya  but system not allowing me to create a PR kindly look in to this issue and  resolve as soon as possible

I would like to work on this @NisantaSahoo will this be OK?

Yes, @Satvik08 please go ahead !

https://github.com/openebs/maya/pull/437 upgrades to v8.0.0


Add page url to the payload of "register" message

Hi @tuvistavie,
I'm the author of Atomic Chrome for Emacs. It's an Emacs clone of Atomic Chrome which allows you to use Emacs as a editor of Atomic Chrome instead of Atom.
Some users want to automatically select editing mode depending on website (e.g. markdown mode for GitHub pages) like Edit with Emacs can do. It requires that the Chrome extension sends the page URL to the editor. Could you consider merging this patch to do that?

Hi @alpha22jp,
Thanks for the PR! I will publish a new version of the Chrome plugin with this addition.

Hi @tuvistavie,
Thanks for your understanding!

@alpha22jp I just published version 0.2.8 with your patch, it should be available within a few hours.


Gracefully handle terminal resize and font resize

Describe the bug
Resizing my terminal's font or resizing the window breaks the presentation. It seems to me these are common enough adjustments for warranting an issue.
Steps to reproduce the bug
Steps used to install present:

pip install present

Steps to reproduce the behavior:

Create a basic slide
Open it with present
Resize your font using terminal emulator shortcuts, or resize the window
Aaaand it's broken :(

Expected behavior

Resizing the window or changing the font size triggers a repaint in Present, and the slides automatically adjusts.

Slides
(not relevant)
Screenshots

Resizing demo
Changing font size

Environment

OS: Linux (5.8.7-arch1-1 #1 SMP PREEMPT Sat, 05 Sep 2020 12:31:32 +0000 x86_64 GNU/Linux)
Terminal emulator: Kitty
Python version: 3.8.5
present version: 0.5.1 (btw, would be nice to be able to do present --version

Additional context
/
:v:

Thanks for the detailed bug report! I'm not sure how to go about handle resizing right now, will have to look into how to do it in asciimatics. But I'll document this behavior in the docs till it gets fixed.


Add status file

Pull Request Test Coverage Report for Build 13

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

Totals

Change from base Build 11:
0.0%

Covered Lines:
0

Relevant Lines:
12

💛  - Coveralls


Sidr broke when upgrading jquery jquery.1.11.1

When I switched to jquery.1.11.1 Sidr broke.

With which version of  jquery does it work?

It should work with jQuery >=1.4.3.
I tried with 1.11.1 and it works, please give me more info or a sample website where it fails.


Multiple pages of records?

I noticed the player profile page only has one page of records, the last X games. Is there a data storage reason for that? Or could that be a potential future feature?

I know bulma already has pageation and stuff. I was thinking of taking a
crack at a PR. Think I mostly got it running locally last night. Just
wanted to check there wasn’t some technical issue preventing the feature
that I was missing.
I’m not super experienced with Rust, so I might crash and burn. But I
thought it could be fun!
On Tue, Jun 21, 2022 at 7:31 AM halvnykterist @.***>
wrote:

The primary reason for that is to speed up rendering the page (and to not
make it too long.) Having multiple pages of records is definitely something
I've got as an idea, but haven't implemented yet.
A temporary workaround is to add /history?game_count=9999 to the URL to
get an extended unstyled view..
—
Reply to this email directly, view it on GitHub
https://github.com/halvnykterist/rating-update/issues/26#issuecomment-1161622019,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB56ACZOORPZ4NMWK4LDJNDVQGRXZANCNFSM5ZJEMQ6A
.
You are receiving this because you authored the thread.Message ID:
@.***>


feature(layout-grid): add new component

First pull request here, hope this is okay.
I am using some of the other components already in a new project and want to move away from https://github.com/materialr as it is a bit hard to maintain as one person with a job :)
Just unsure about the screenshots Docker image. My assumption is that that only gets pushed once a PR is accepted and merged?

Codecov Report

Merging #351 into master will increase coverage by 0.03%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #351      +/-   ##
==========================================
+ Coverage   97.25%   97.28%   +0.03%
==========================================
  Files          36       39       +3
  Lines        1491     1509      +18
  Branches      164      164
==========================================
+ Hits         1450     1468      +18
  Misses         41       41

Impacted Files
Coverage Δ

packages/layout-grid/Cell.js
100% <100%> (ø)

packages/layout-grid/Row.js
100% <100%> (ø)

packages/layout-grid/Grid.js
100% <100%> (ø)

Continue to review full report at Codecov.

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

@hvolschenk thanks for opening this PR...we will take a look and discuss among the team. RE Screenshot tests - I think we have an issue accepting outside contributors without the key. You are able to download and run tests locally (if you have docker installed), but cannot push up. Once we arrive to a final design I can add the screenshot test.

@moog16 Sweet, sorted the comments, just added a question of my own.

can you please sign this PR? Just comment "I signed it"

#358 passing tests - so we can merge!


MINOR: Add @Timeout annotation to consumer integration tests

In this buid, the following test hang forever.
Gradle Test Run :core:test > Gradle Test Executor 93 > PlaintextConsumerTest > testSeek(String, String) > testSeek(String, String).quorum=kraft+kip848.groupProtocol=consumer STARTED

As the new consumer is not extremely stable yet, we should add a Timeout to all those integration tests to ensure that builds are not blocked unnecessarily.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Hmmm -- are we concerned with introducing these new test failures? I agree a timeout is good, but I'm wondering if there is a way we could suppress these failures for PR builds.

I've also been seeing more failed builds --
* What went wrong:

Execution failed for task ':streams:upgrade-system-tests-25:test'.

> Process 'Gradle Test Executor 9' finished with non-zero exit value 1

  This problem might be caused by incorrect test process configuration.

From this PR -- is it possible the new consumer could be throwing errors that cause test issues like this? I know it should be on the test to handle errors in a way that doesn't kill the build, but I have been seeing many failed builds due to these issues or GC/OOM issues.


refactor: rely on Onboard for provider watching

Known bugs that resulted in reopening

[x] Multiple GA event tracking: one is occuring per provider action and when switching network it sometimes tracks incorrectly.
[x] ENS name is not resolving correctly, as explained here.
[x] Disconnecting and refreshing reconnects the user automatically.
[x] No network switch prompt when connecting.

May likely fix

Avalanche network switching message: https://github.com/gnosis/safe-react/issues/3285
Did fix: ~Wallet Connect Infura errors: https://github.com/gnosis/safe-react/issues/2093~
Fixed a separate PR: ~Wallet Connect not working on Gnosis Chain: https://github.com/gnosis/safe-react/issues/3372~

What it solves
The removal of an unnecessary interval and, in turn, numerous requests. Also, a reduction of ENS errors in the console.
How this PR fixes it
In researching how to reduce ENS console errors from our provider watcher, it became apparent that we were relying on a legacy method of 'watching' the Onboard provider. Onboard, however, has built-in subscriptions that are a better alternative than the interval we were using. (One of which resolves ENS domains on wallet connection).
Instead of using an interval that polls every few seconds, this PR migrates to using the wallet, address, network and ens subscriptions from ENS, responsible for:

Wallet changes
Account changes
Network changes
ENS resolutions (when the above three change)

The legacy watcher interval has been removed, as well as the associated reducer/middleware adjusted. The reducer handles the subscriptions based on updates instead and wallet disconnection is now handled internally via Onboard, removing reliance on a provider removal method. Logic that was previously required in the middleware: instantiating contracts and saving the current provider for re-connection is now also handled by Onboard.
The notification system has been moved from provider 'fetching' (which was previously happening every time per interval) to the middleware, which is also subscription-based.
A few unnecessary utility functions have also be replaced or substituted for their Onboard counterparts.
How to test it
Nothing should change on a UI/UX level. Connection may seem a bit quicker. Areas to check are the following (cross-wallet):

Wallet connection should correctly update the providers store data correctly, i.e. EOA details, ENS domain, hardware/smart contract wallet flags, etc.
Disconnection should clear the providers store.
Provider-related notifications should work as before.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

35 of 81 (43.21%)  changed or added relevant lines in 10 files are covered.
32 unchanged lines in 3 files lost coverage.
Overall coverage remained the same at 32.378%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/components/AppLayout/Header/index.tsx
0
1
0.0%

src/logic/wallets/utils/network.ts
1
2
50.0%

src/logic/wallets/store/selectors/index.ts
9
12
75.0%

src/logic/wallets/store/reducer/index.ts
4
11
36.36%

src/logic/wallets/store/middleware/index.ts
12
26
46.15%

src/logic/wallets/onboard.ts
5
25
20.0%

Files with Coverage Reduction
New Missed Lines
%

src/logic/wallets/onboard.ts
3
10.71%

src/components/AppLayout/Header/index.tsx
14
0%

src/logic/wallets/getWeb3.ts
15
71.62%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3172

Relevant Lines:
8708

💛  - Coveralls

I am not sure I have enough understanding of all the underlying problems to say it's ready for QA.

What problems did you find?

Tested on Rinkeby with

[ ] Ledger nano X - works both signing and execution
[ ] Trezor T - only signing works. Execution is not available with trezor T

Issue with WC connection. Tried in dev and prod and it doesn't happen there
https://github.com/gnosis/safe-react/issues/3528

The trezor causes 2 calls to GA when connecting it, one when the modal open to select an account from the dropdown and one when you actually confirm it. This also happens in dev, but given the 1st checkbox in the description of this ticket I wanted to know if this ticket is supposed to fix these repeated calls to GA or not.

Tested in Rinkeby so far. Signing tx with MM chrome extension, WC with MM phone app, trezor one and ledger nano S worked fine. Also safe creation
I'll give it a try to other networks tomorrow

Issue with WC connection. Tried in dev and prod and it doesn't happen there #3528

I'm a bit confused as you're following comment:

Tested in Rinkeby so far. Signing tx with MM chrome extension, WC with MM phone app, trezor one and ledger nano S worked fine.

suggests it works? Can you provide any more details?

I wanted to know if this ticket is supposed to fix these repeated calls to GA or not

Not here. I am working on the Analytics epic where it will be sorted.

Let me summarize my comments:

2 issues I found recently: #3528 and #3529. The "dev" comment is that I always check dev (and sometimes prod) to see if the issue are happening there as well, but in this case both of those issues only happen in this PR.
Lili seems to have issues with the "Trezor T" to sign txs
I made a comment regarding GA in trezor, but you are saying that is not expected to be fixed here, so I'll ignore it
Despite the issues Lili and I found, on my side I had no problem creating safes, signing and executing tx with the MM extension, WC with the MM phone app and the devices I have: a trezor one and a ledger nano S.

* 2 issues I found recently: [Onboard refactor: Safe not loading when WC is used to connect to the safe. #3528](https://github.com/gnosis/safe-react/issues/3528) and [Onboard refactor: Console warnings when opening the safe list on the sidebar #3529](https://github.com/gnosis/safe-react/issues/3529). The "dev" comment is that I always check dev (and sometimes prod) to see if the issue are happening there as well, but in this case both of those issues only happen in this PR.

Just confirmed with @francovenica that these were solved by merging dev into this branch (https://github.com/gnosis/safe-react/pull/3364/commits/649cfd0ff2ad496cf453b0c323f87b13251abc11)

* Lili seems to have issues with the "Trezor T" to sign txs

Awaiting confirmation on whether this is related to an older ticket.
Looks like we can merge this soon 👀


Updating API module

Adding ScriptingError error
Throw errors instead of prints when failing
special treatment of stopTime for API.simulate
More documentation

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


Send Confirmation says Money Sent! when transferring assets

The Send Confirmation dialog say Money Sent! when transferring assets and should say Asset sent!.


Add "conflictsWith" functionality to Filterer library

What does this PR do?
This pull request adds the confictsWith filter option which allows a user to specify that the given filtered value conflicts with one or more filtered values. If multiple conflicting values are present a FilterException is raised.
Checklist

[  ] Pull request contains a clear definition of changes
[  ] Tests (either unit, integration, or acceptance) written and passing
[  ] Relevant documentation produced and/or updated

Coverage remained the same at 100.0% when pulling 7a02dd4931dc6bfadee7c3fb7727c9b3ec498544 on chadicus:fea/conflicts-with into a8dec173063ee2444ec297f065f64496b7d21590 on traderinteractive:master.

Coverage remained the same at 100.0% when pulling 7a02dd4931dc6bfadee7c3fb7727c9b3ec498544 on chadicus:fea/conflicts-with into a8dec173063ee2444ec297f065f64496b7d21590 on traderinteractive:master.


max_grad_norm is ignored in FP16 training

I am currently fighting with a dynamic loss scale that is constantly decreasing due to gradient overflows. Setting max_grad_norm in the JSON config has no effect since it is overidden in deepspeed_light.py https://github.com/microsoft/DeepSpeed/blob/13fd3dca2abb6d6a6af62d46457fff8a1a678a4a/deepspeed/pt/deepspeed_light.py#L407-L408:
I think this modification should be removed.
Kind regards

I just saw that there is a "gradient_clipping" option in the config. However, setting it to 1.0, does not eliminate the gradient overflow messages. Is this expected?

Gradient overflow messages, typically at the beginning of training, are not surprising. But this should eventually stop once the dynamic loss scale has decreased to a point that allows training stability.
Are you not seeing the overflow messages stop?

Regarding to the orignal question, what's the purpose to disable 'max_grad_norm' for fp16?
if self.fp16_enabled() and 'max_grad_norm' in optimizer_parameters.keys():
optimizer_parameters['max_grad_norm'] = 0.0

The rationale for this was to support both the old  and new ways of specifying gradient clipping. The difference is that in the old way, gradient clipping is specified as max_grad_norm parameter of the fp32 optimizer, while in the new (and more intuitive way IMHO) gradient clipping is handled in the fp16 wrapper optimizer, such as here. In summary, this logic allows the fp16 optimizers in DeepSpeed to handle both old and new gradient clipping styles.
All that said, we are thinking of ways to improve the interface and avoid this confusion, and we certainly appreciate your input on that.


Some small fixes for tree display

Partial fix for #327

Current coverage is 91.43%

Merging #329 into master will not affect coverage as of 801fb00

@@            master    #329   diff @@
======================================
  Files           41      41
  Stmts         2079    2079
  Branches         0       0
  Methods          0       0
======================================
  Hit           1901    1901
  Partial          0       0
  Missed         178     178

Review entire Coverage Diff as of 801fb00

Powered by Codecov. Updated on successful CI builds.


Ant species data source

This is an authoritative data source for ~25,000 ant names. It is maintained by Steve Shattuck. It would be nice to have it available at some point.
https://www.antwiki.org/wiki/Downloadable_Data

@whitfarnum thanks for the suggestion . So far, the Antwiki data is looking nicely organized and accessible. Perhaps @myrmoteras is also interested in getting the Antwiki taxonomic list incorporated into Nomer, and perhaps even explicitly linked to related taxonomic treatments.

fyi @seltmann - perhaps another example of a well used taxonomic resources like DiscoverLife. Neat to see how Antwiki is a little easier to access.


Objects

made a User.java and udpated Recipe.java to include a description
updated UserPage.html and NewRecipeServlet.java to have the description implementation


chore: bump up version to v1.13.0

关联的Issues (Related Issues)

改动 (Proposed Changes)

附注 (Additional Info)

自查清单 (Checklist)
在你认为本 PR 满足被审阅的标准之前，需要确保 / Before you mark the PR ready for review, please make sure that:

[ ] 符合Venus项目管理规范中关于PR的相关标准 / The PR follows the PR standards set out in the Venus project management guidelines
[ ] 具有清晰明确的commit message / All commits have a clear commit message.
[ ] 包含相关的的测试用例或者不需要新增测试用例 / This PR has tests for new functionality or change in behaviour or not need to add new tests.
[ ] 包含相关的的指南以及文档或者不需要新增文档 / This PR has updated usage guidelines and documentation or not need
[ ] 通过必要的检查项 / All checks are green

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/v1.13@486746f). Click here to learn what that means.
The diff coverage is n/a.

Additional details and impacted files

@@               Coverage Diff                @@
##             release/v1.13     #156   +/-   ##
================================================
  Coverage                 ?   34.46%
================================================
  Files                    ?       41
  Lines                    ?     2591
  Branches                 ?        0
================================================
  Hits                     ?      893
  Misses                   ?     1542
  Partials                 ?      156

Flag
Coverage Δ

unittests
34.46% <0.00%> (?)

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


date is not selected in Chrome Version 62.0.3202.62 (Official Build) (64-bit)

Description
When using Chrome Version 62.0.3202.62 (Official Build) (64-bit), the calendar opens but after a date is selected and the calendar closes, the date is not updated in the input box.
Expected outcome
The date should be updated.
Actual outcome
The input box remains blank (or unchanged if a value is set).
Live Demo
https://www.webcomponents.org/element/vaadin/vaadin-date-picker
Steps to reproduce
Go here https://www.webcomponents.org/element/vaadin/vaadin-date-picker
Use the noted version of Chrome and click on the calendar icon of the "Pick a date" labeled vaadin-date-picker component.
Select a date
The calendar closed and the date is not updated.
Browsers Affected

[ X] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge
[ ] IE 11
[ ] iOS Safari
[ ] Android Chrome

Fixed in v2.0.6, thank for reporting!

The same fix for 1.x: v1.2.4

Excellent, thank you for the fix.


fsspec access from Synapse to abfs fails with idna codec error

I am following this tutorial, however when accessing a file via abfs protocol in the linked account this error occurs:
UnicodeError: encoding with 'idna' codec failed (UnicodeError: label empty or too long)
fsspec.version = 0.8.4
I am 'Storage Blob Data Contributor' on that linked account.
Thank you and best regards, Robert
[Enter feedback here]

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

ID: 9de691e6-672e-1c04-e484-dc60ad6c0d10
Version Independent ID: fdcf2021-710c-5380-591c-6b74c4e0b4f6
Content: Tutorial: Use FSSPEC to read/write ADLS data in Synapse Analytics spark pool - Azure Synapse Analytics
Content Source: articles/synapse-analytics/machine-learning/tutorial-spark-pool-filesystem-spec.md
Service: synapse-analytics
Sub-service: machine-learning
GitHub Login: @AjAgr
Microsoft Alias: ajagarw

I tried some more tests:
access with key, data directly in container: ok!
fsspec.open('abfs://synapse/sales_data.csv', account_name=adls_account_name, account_key=adls_account_key).open()
access with key, data in subfolder: fails with 'file not found' (Files is present of course)
fsspec.open('abfs://synapse/aml/sales_data.csv', account_name=adls_account_name, account_key=adls_account_key).open()
access with sas (subfolder or directly) fails
...fails with: UnicodeError: encoding with 'idna' codec failed (UnicodeError: label empty or too long)

@gantonius I'm able use FSSPEC to read/write ADLS data in Synapse Analytics spark pool without any issues.

Read data using linked service:

Write data using linked service:

Data is written to ADLS gen2 account.

Hope this helps.

That's promising :)
Could you please share your versions of
fsspec and adlfs
On Wednesday, September 15, 2021, CHEEKATLAPRADEEP-MSFT <
@.***> wrote:

@gantonius https://github.com/gantonius I'm able use FSSPEC to
read/write ADLS data in Synapse Analytics spark pool without any issues.

Read data using linked service:

[image: image]
https://user-images.githubusercontent.com/79183421/133425959-9124ffb3-b815-4f3d-8433-9e16c2cb5a49.png

Write data using linked service:

[image: image]
https://user-images.githubusercontent.com/79183421/133426063-8763184f-3417-4229-af0c-5c98f6a06be5.png
Data is written to ADLS gen2 account.
[image: image]
https://user-images.githubusercontent.com/79183421/133426154-9b94f733-3b71-4318-a4dc-6d7b43f8c1cd.png
Hope this helps.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/81100#issuecomment-919940024,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMXJSSX5XGVAISNQO7FNQ3UCCAILANCNFSM5ECETCOA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@CHEEKATLAPRADEEP-MSFT  I am using the same code, but still getting errors.
According to your screenshots, even subfolders work for you.
Could you therefore please share your versions:
import fsspec; fsspec.version
import adlfs; adlfs.version
Thank you and best regards,
Robert

@robert4os I had tested on both the Supported Azure Synapse runtime.

Azure Synapse Runtime for Apache Spark 2.4:

fsspec 0.8.4
adlfs 0.5.5

Azure Synapse Runtime for Apache Spark 3.0

adlfs 0.7.7
fsspec 2021.6.1

@CHEEKATLAPRADEEP-MSFT -- I have just created a new synapse workspace and tried the above with the described error.

For Spark 3, I have got it to work, changing the parameter in the fsspec.open method to 'adls_account_name' from 'account_name' (as given in the tutorial).
fsspec_handle = fsspec.open('abfs://..../sub/fsspec.yml', adls_account_name = adls_account_name, sas_token=sas_key)
So the tutorial in the docs is out dated for sure (at least regarding spark3).
--
For Spark 2 I have not found a solution to the error above. Absolutely reproducible, even using a totally fresh Synapse workspace. I have opened a ticket.

With the help of support I realized that storage accounts that are linked (via KEY) work, but others (via SP or MSI) do not!
Either

the tutorial mentions that ONLY linked storage (via KEY) is supported (for spark 2)
AND for spark 3 it mentions the different parameters needed (i.e.  'adls_account_name' from 'account_name')
Or preferably all permutations of spark2/3 and linked via KEY/SP/MSI get supported :)

@robert4os Thanks for the sharing your findings.
We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Update optioncodes.md

Code	Category	Description
AF02	Air Filter	HEPA Filter
APFB	Autopilot Firmware	Standard Autopilot Firmware
APH4	Drivers Assistance Package	Autopilot 3.0 Hardware
AU01	Sound Studio Package	Sound Studio Package
BP02	Battery Performance	Uncorked Non-Performance Acceleration
BR00	Battery Range	NO Battery Range
BS00	Blind Spot Sensor Package	No Blind Spot Sensor Package
BTXA	Battery	18650J2 Battery Cell
CDM0	CHADEMO	CHAdeMO no
CF00	Charger Firmware Limit	No Charger Firmware Limit
CH09	Chargers	Tesla Standard Charging System
CONL	Country Description	Netherlands
CPF1	CONNECTIVITY_FIRMWARE_OPTION	Premium Connectivity Enabled
CW02	Weather Package	Cold Weather Package
DCF2	Front Console	Inductive Phone Charger
DRLH	Drive Orientation	Left Hand Drive
DSHG	Dashboard	Dash with Graphite trim
DV4W	Motor	Dual Motor
EUSB	Safety	Safety EU Black
FBBB	Front Brake Assembly	Front Brake Brembo Black
FDU2	Front Drive Unit	Raven Front Drive Unit
FG02	Fog Lamps	Fog Lamps
FMP6	Firmware Performance	Firmware Performance - 2017.26
FR05	Front Row Seat	Ventilated Front Seats
GLTL	Assembly	Tilburg Assembly
HP00	High Power Wall Connector	No High Power Connector
IDBA	Interior Decor	Black Ash interior décor
LLP2	License Plate Liftgate Type	EU Liftgate
LP01	Lighting Package	Lighting Package
LT5W	Lower Trim	Black PUR lower with White interior
MDLS	Manufacturing Model	Model S Standard
ME02	Seat Memory	Seat Memory LHD Driver
MI04	Project/Program Code	Pedestrian Protection
PBSB	Exterior Color	Solid Black Paint
PF00	Performance	No Performance
PK00	Parking Sensors	No Parking Sensors
PP01	Pedestrian Protection	Ped Pro R127 Compliant
PS01	Parcel Shelf	Parcel Shelf
PWS0
RBMB	Rear Brakes Assembly	Rear Brake Mando Black
RDU4	Rear Drive Unit	Rear small drive unit with electric oil pump
REEU	Region	Region European Union
RFFR	Roof	Fixed Glass Roof (roof rack compatible)
S42W	Seat	White Plenum M3 Seats
SC04	Supercharge Hardware	Pay as you go Supercharging
SP01	Security Package	Security Package
SR07	Second Row Seat	Second Row Seats with Comfort Improvements
ST01	Steering Wheel	non-heated steering wheel
SU03	Suspension	Adaptive Air Suspension
TD00	Tear Down	NON-GLIDER
TIM9	Tires	Michelin Pilot Sport 4
TM00	Model Trim	Model S
TR00	Rear Facing Seats	No Rear Facing Seats
UTSB	Upper Trim	Black Ultra-suede Headliner
WR02	WRAP	Wrap 2 (Tilburg bound)
WTAS	Wheels	19” Aero wheel (Silver)
X001	Teck Package - Liftgate	Override: Power Liftgate
X003	Teck Package - Navigation	Override: Navigation YES
X007	Teck Package - Exterior Lights	Override: Premium exterior lighting YES
X011	Teck Package - Homelink	Override: Homelink YES
X014	Satellite Radio	Override Satellite Radio NO
X021	Rear Spoiler	No Rear Carbon Fiber Spoiler
X025	Performance Powertrain	Override Performance Powertrain NO
X027	Door handle	Light handle
X028	Normal Badging	Normal Badging
X031	Passive Entry Pkg	Yes Passive Entry Pkg
X037	Tech Package - Mirror -YES	Power Folding Mirror
X039	HD Radio	DAB Radio
X043	Phone Dock Kit	YES Phone Dock Kit
YFCC	Yatcht Floor	Front Console, Décor Matched

Thanks!


Use Lit Robot's info as the global name and email for git operations during releases.

This PR sets the global git email and name to those of our robot account so that it doesn't have to be set in each individual repo before committing.

Cool! Maybe this will fix https://github.com/lit/lit/issues/2502

This is draft... is it intended for review?

Cool! Maybe this will fix #2502

Huh, maybe!

This is draft... is it intended for review?

I didn't mark it as ready since it's based on #2496, which is still pending, but I certainly won't stop you if you want to look it over early

Actually no... I'd rather see that other PR work without changing the existing git setup.

Closing: this was added as part of #2540.


publish<EMAIL_ADDRESS>

Requested by: @billyvg
Merge target: sentry-v2
Quick links:

View changes
View check runs

Assign the accepted label to this issue to approve the release.
Leave a comment containing #retract under this issue to retract the release (original issuer only).
Targets

[ ] github
[ ] npm

Targets marked with a checkbox have already been executed.  Administrators can manually tick a checkbox to force craft to skip it.

I checked CI and it was green over there.


sudo support for ssh commands

My master VM template doesn't have a root password that I can use via SSH - but there's a local user that can run password-less 'sudo' commands. I created this PR to enable the local non-root user to provision Chef / vSphere VMs.
This implements the machine_options 'sudo' key used by chef-provisioning-fog and chef-provisioning-aws - and therefore maintains compatibility in case the driver is swapped out from underneath configurations of vSphere, AWS, or Fog platforms.

This is great. Thanks so much!

Thank you! Any idea when the next minor version will be released?

released 0.7.0 just now. Thanks again.


CB-11412 Update templates to designate template source dir

Is there a standard format for this style of template?
I think we should use the folder name template instead of template_src.

Nope, I just made those changes according to how templates are implemented in cordova create.
We should definitely talk about what the default files/folders should look like (+ create a guide to creating templates), but some things will be project specific, like package.json and config.xml.
For now, package.json and config.xml within template_src will be copied and then package.json (name and version) and config.xml (name, id, and version) are updated to match the created project. If no config.xml is included in the template, we grab the one from cordova-app-hello-world. If no package.json is included in the template, nothing happens.

I personally wouldn't bother with template vs template_src. It can be named whatever as long as dirname in index.js points to it.

So I could change it in my templates if I wanted. And a different template author could use something else?

@devgeeks yup. Cordova doesn't care what you call the subdirectory.

Thanks for the clarification @carynbear!
I'd like to see all PhoneGap projects use template/ and not template_src/. Underscores are not very common in node projects - I'm not sure why Cordova picked up using them. In directory structure, usually a dash - is used in place of a space and in syntax, it's camelCase.

@mwbrooks
Sorry I put this on the back burner while waiting for people to review it. I chose that naming convention mainly because node_modules/ has the same naming convention
I made some additions to docs on the topic of template usage and creation. Definitely not perfect, but I what I wrote is a little bit easier to digest if I use template_src to indicate the location of the template's contents and template to refer to the entire package. That can be revised so please review it with the naming conventions in mind.

I'm closing this since it's been sitting for a week.
@mwbrooks in package.json my_app is now MyApp


Add support for other FOV algorithms + symmetric shadowcasting

Related: #198, #192, #75
This is my attempt to introduce support for multiple field of view algorithms to the library. It also adds a symmetric version of the shadowcasting algorithm. Having said that, I realize that the old algorithm, being preferable due to better performance, might be adapted to include a symmetry switch. However, the point for supporting different algorithms remains.
If you'd prefer factoring the new algorithm out of this PR, just let me know :)
Summary of proposed changes:

flesh out field_of_view as a proper (private) module of bracket-pathfinding, and convert the current upstream FOV algorithm into its submodule, recursive_shadowcasting.
in field_of_view, introduce enum FieldOfViewAlg with the methods field_of_view_set() and field_of_view(), akin to DistanceAlg with distance2d() and distance3d() in bracket_geometry. The variants of this enum represent the different algorithms.
move existing FOV tests to field_of_view in order to accommodate DRYer testing of new algorithms
include both the new FieldOfViewAlg as well as the old FOV functions (of the old algorithm) in bracket_pathfinding::prelude, to maintain backwards compatibility.
add a symmetric shadowcasting algorithm, described in #198.

:tada:

I put this through a lot of tests, and it looks really good - thank you.


[Feature Request]: Pointer movement is not professional

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
i will make pointer movement as professional. So this is good for your website that enhance professional software development
Use Case
Existing pointer movement is really agains with professional software development process.
Benefits
Make website as professional website.
Add ScreenShots/Videos

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 Extended contributor
[X] I'm a Hacktoberfest'24  contributor
[X] I have starred the repository

@skanarul8002 what kind of Cursor movement UI u want to add like can u give any example like with maybe some prototypes

Ok sure @apu52. Basically standard Web applications follows a normal pointer movement there are no back dot blinking, no any things. That exists pointer movement is really different from other applications but your Web is good so need to make professional.
Also you see a snapshot, is this right? I think 🤔 this not good for applications.
So I want to make normal standard pointer that fit in your application.

Actually @skanarul8002 I understand your recommendations as a Cursor basic style , But as it's a totally open source project , i want to make it interactive & really don't want to make it a the basic cursor again.
So if u may have some other recommendations regarding this u can generally tell here

@apu52 , if you will accept this task then i will give my best design and also look professional, design also.

please mentor @apu52 , mention required levelno also.
Thanks for accepting this issue.

@skanarul8002 I will add labels after reviewing your PR , don't worry about that , go ahead with the PR


url should be part of every source

Unless I'm missing something, the source specification is useless without URL. I suggest to add "url" to this check:
https://github.com/osbuild/osbuild-composer/blob/05fd221bd4763040afd9a17b8c6567dc9ef97409/internal/weldr/api.go#L596
Related: https://github.com/weldr/lorax/issues/1066

This sounds reasonable. How would this affect lorax compatibility?

It shouldn't have any effect. url is assumed to be present. it's useless without it.


Rename common orchestration workflow parameters

What this PR does / why we need it:
This PR rename orchestration workflow parameters that specify details of OpenSDS instance. This will make Dashboard integration consistant.

Codecov Report

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

@@          Coverage Diff           @@
##           master     #26   +/-   ##
======================================
  Coverage    42.5%   42.5%
======================================
  Files          13      13
  Lines         614     614
  Branches       65      65
======================================
  Hits          261     261
  Misses        343     343
  Partials       10      10


teuthology-describe-tests: add --summary command

Add --summary argument to teuthology-describe-tests for estimating run capacity, printing descriptions, dumping matrix,  yaml fragments.

@gregsfortytwo any idea what happens on jenkins?

@gregsfortytwo Probably something wrong with jenkins environment or master branch is broken.
The only suspect thing I can see in the log is:
  /home/jenkins-build/build/workspace/teuthology-pull-requests$ /home/jenkins-build/build/workspace/teuthology-pull-requests/.tox/flake8/bin/flake8 --select=F,E9 teuthology scripts
teuthology/suite/run.py:139:16: F632 use ==/!= to compare str, bytes, and int literals
teuthology/suite/test/test_build_matrix.py:624:16: F632 use ==/!= to compare str, bytes, and int literals
teuthology/suite/test/test_build_matrix.py:626:16: F632 use ==/!= to compare str, bytes, and int literals
teuthology/suite/test/test_build_matrix.py:629:16: F632 use ==/!= to compare str, bytes, and int literals
teuthology/suite/test/test_build_matrix.py:631:16: F632 use ==/!= to compare str, bytes, and int literals
teuthology/task/lockfile.py:228:12: F632 use ==/!= to compare str, bytes, and int literals
ERROR: InvocationError for command '/home/jenkins-build/build/workspace/teuthology-pull-requests/.tox/flake8/bin/flake8 --select=F,E9 teuthology scripts' (exited with code 1)```

But other PR has the same error message, for example:
https://jenkins.ceph.com/job/teuthology-pull-requests/1411/

jenkins retest this please

So the jenkins failure are not related to the PR.

@jdurgin @gregsfortytwo @vasukulkarni are we good with this PR?

Going back to my last review, looks like the seed thing is still messed up. And a test to validate it against dry-run output would still be good!

Anything automated will do, but yeah I would probably start with some grep'ing, sort'ing, and diff'ing.

Anything automated will do, but yeah I would probably start with some grep'ing, sort'ing, and diff'ing.

It will be equivalent to fix --dry-run so it can be executed without special production environment, because as I said earlier you can just run teuthology-suite --dry-run without special environment. This would be an overkill.

@gregsfortytwo There is no sense in making test comparing --dry-run and --inspect in sense of seed, because using of seed is different by design for both, by default --dry-run should generate random seed for randomized suite generation, for the latter it should not be random.
We could try and run both for different same seed values. However it will not be unit test, it is system test because it requires specific test environment, if the --inspect can be run just from source code directory, the --dry-run requires more fixes, not related to this PR. Since this PR is not changing any functionality, I would like to merge it, and suggest to create another PR for testing --dry-run, anyways I do not see a benefit in this test.

Trying to match up this output with that of dry-run isn't to test dry-run, it's to validate that --inspect is doing what we expect. It would be VERY BAD if somebody ran inspect and somehow got different results than were to come out of the normal suite execution engine!
That doesn't mean we need to execute a test on every install, but we can make it part of the teuthology self-tests that run in Jenkins: do the setup necessary to invoke dry-run, grab its output, and compare it to the output of --inspect.
(I think the seed is a red herring; it only applies when you're doing a subset with the magic $ (random) input. So for a full suite run it won't apply? Or if it does, we can force the same seed value in for both.)

Trying to match up this output with that of dry-run isn't to test dry-run, it's to validate that --inspect is doing what we expect. It would be VERY BAD if somebody ran inspect and somehow got different results than were to come out of the normal suite execution engine!

But we will need to run both.
Well the inspect is using same API as dry-run, correspondingly it should generate same facet set. I ran manually a comparison test on suites from ceph repo. But if you want to run it for each commit on each PR it will require checkout whole ceph repo each time. Or we will need to have some test hierarchy of empty files, and we are not safe that 'dry-run' won't fail while trying to detect some git repo stuff by this path.
I also don't seed  a sense in this test, because later one can decide to remove test description from the log of dry-run.
If we really want to test --inspect, not 'dry-run' there is no sense to compare it with dry-run at all, because dry-run also requires to be tested that it is doing what we expect, and we are not testing this now.
So in ideal world we need to have test subtree in teuthology source tree to play role as test vectors for inspect. Btw, the matrix tests are using dummy in memory fs, which can not be used on cli level.

That doesn't mean we need to execute a test on every install, but we can make it part of the teuthology self-tests that run in Jenkins: do the setup necessary to invoke dry-run, grab its output, and compare it to the output of --inspect.
(I think the seed is a red herring; it only applies when you're doing a subset with the magic $ (random) input. So for a full suite run it won't apply? Or if it does, we can force the same seed value in for both.)

Right, the seed make sense only when 'subset' option is used, otherwise it is just ignored.

Trying to match up this output with that of dry-run isn't to test dry-run, it's to validate that --inspect is doing what we expect. It would be VERY BAD if somebody ran inspect and somehow got different results than were to come out of the normal suite execution engine!

But we will need to run both.
Well the inspect is using same API as dry-run, correspondingly it should generate same facet set.

Hmm, the implementation is mostly in build_matrix, but I'm worried about some subtle difference creeping in as part of the filtering since that's duplicated. I guess if that were factored out and the same code used we wouldn't need an extra test here.

I just spoke to @kshtsk and did a little bit of digging re: how to test this. What I'm thinking the right thing to do would be to take a look at the build_matrix tests - specifically things similar to this. The use of mock to create a fake 'suite' has been effective, and it seems like it would work fell for this feature.
I'd also argue that it doesn't need to e.g. verify all possible flag combinations, and that testing that the proper args are passed to build_matrix, trusting that those tests do their job.

Yeah that would be fine; like I said it's the re-implementation of filtering that concerns me at this point.

Oh, sure - good point. I agree that it'd be worth attempting to reuse that code.

@jdurgin @gregsfortytwo
The functionality moved to teuthology-describe-tests, the teuthology-suite --inspect reincarnated as teuthology-describe-tests --summary. The code is now using same execution path as teuthology.suite.run Run.collect_jobs for filters. Also teuthology-describe-tests fixed to use --filter --filter-out and --filter-all in same manner as in teuthology-suite, as well as --seed and new option --filter-fragments.

Also I suggest to rename teuthology-describe-tests to shorter name teuthology-describe, what do you think about it?

@susebot run deploy

Also I suggest to rename teuthology-describe-tests to shorter name teuthology-describe, what do you think about it?

sounds good to me


Invalid local primary storage can be created

ISSUE TYPE

Bug Report

COMPONENT NAME

UI, API, Local storage,KVM

CLOUDSTACK VERSION

4.19.1

CONFIGURATION

Cloudstack 4.19.1
KVM Rocky8
OS / ENVIRONMENT

SUMMARY

Cloudstack allows adding an invalid local primary storage on KVM. It throws an error that the path is invalid i.e the directory does not exist but the primary storage is added.
STEPS TO REPRODUCE

1. Enable the 'Enable local storage for User Instances' on the zone
2. Add primary storage using UI with scope 'host' and protocol 'filesystem'.
3. Input a path that is not present in the KVM host
4. Add primary storage

EXPECTED RESULTS

The primary storage doesn't get added.

ACTUAL RESULTS

The primary storage gets added.

@rajujith , I don't think this is a bug. It is operator responsibility to make sure the path is there and they may plan their order of actions at will. Restricting this seems excessive  control to me.

@DaanHoogland  I agree with you that it is the operator's responsiblity. Still, it's good to improve this area and not allow invalid paths in the future and throw an error stating the same.

ok, I see the point, but am worried that we are over-controlling the backend system. We can implement a check that a file path exists, is a directory and is writable, but no further. A mount may not be performed for instance. and the mount point may not have space. These issues should at least for now be out of scope.
Another issue is that on different hypervisortyoes the check may need different implementations.
What do you think @rajujith ?

ok, I see the point, but am worried that we are over-controlling the backend system. We can implement a check that a file path exists, is a directory and is writable, but no further. A mount may not be performed for instance. and the mount point may not have space. These issues should at least for now be out of scope. Another issue is that on different hypervisortyoes the check may need different implementations. What do you think @rajujith ?

Agreed.


[Add] Rounded Animated Pulse Button

Details
I would like to propose the addition of a "Rounded Pulse Button" to our website.
The key feature of the Rounded Pulse Button is its subtle animation effect. When users hover over the button, it will pulse gently, expanding and contracting in a smooth and eye-catching manner. This pulsating animation will create a sense of interactivity and engagement, encouraging users to interact with the button.
Screenshots
No response
Type of Contribution

[ ] Update to an existing Animated Button
[X] Adding a new Button
[ ] Resolving a bug
[X] Proposal to the Repository
[ ] Changes related to documentation or README.md
[ ] Other Changes

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I am willing to work on this issue
[X] I am a GSSoC'23 contributor

🎉 The GSSOC'23 program has reached its conclusion, prompting us to officially close all pull requests (PRs) and issues. We extend a heartfelt thank you for your amazing contributions! 🙌 Keep the coding spirit alive with the same enthusiasm, and may luck 🍀 favor you in all your future coding adventures!


update sbt-unidoc 0.3.2 => 0.4.0

Problem
sbt-unidoc 0.3.2 is not autoplugin but, 0.4.0 is autoplugin
Solution
update sbt-unidoc
Solution
We can use sbt-unidoc as autoplugin
https://github.com/sbt/sbt-unidoc/releases/tag/v0.4.0

Codecov Report

Merging #405 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #405   +/-   ##
========================================
  Coverage    94.26%   94.26%
========================================
  Files          224      224
  Lines         3314     3314
  Branches       263      263
========================================
  Hits          3124     3124
  Misses         190      190

Continue to review full report at Codecov.

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

@matsu-chara lgtm, thank you!

@matsu-chara thanks, I'm going to merge this one shortly.

@matsu-chara , thank you, this one merged in 3f7192d815e18dfee72069baabe59b8968947ab3.


React 15.5.4 - Warning: Accessing PropTypes via the main React package is deprecated.

Can you resolve the warining adding prop-types package dependency?
warning.js:36 Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead.

Best Regards.

a PR https://github.com/qimingweng/react-modal-dialog/pull/49 is already waiting to fix that

Is there anything holding up merging it? It would be nice to get rid of these errors


Allow mount_path to be specified when defining volumes.

The previous implementation of this feature, would result in the host_path and the mount_path to be the same with not option to make a custom mount path.

Ah I can see why this would be needed. Say I need to include data from $HOME/.config/mydata, and since the home directory will be different paths for the host and mount, then you want to be able to mount this to the same logical point in the container? The logic has changed significantly in our code, so this will likely need a fresh PR, but I'm not opposed to this on principal.

Actually closing since you can do this via DOCKER_OPTS, and for very esoteric behavior like this that would require much more than "zero" setup, since it is almost certainly host-specific, you can always provide it via another config option, and isn't a valid path which is what we planned to support.


overflow at WriteMatrix() in cmstypes.c

https://github.com/mm2/Little-CMS/blob/65c63bf549d78253c14b30b3d62cb668bbbe612c/src/cmstypes.c#L2551
If the actual length of the double array is less than 9, then the arrry access will be out of bounds.

Fixed by 9632a058a0c617a6461a1c32bc437fef87b3de9c
Many thanks for reporting


Update wrong comment

Hey, I saw that the comment for the cron job said every Monday, but your bot doesnt reflect the comment. So I updated it :)

Hey thanks for the interest in my project, nice catch!
Although the comment states something wrong I think your correction might still not be what the cronjob states. The Gihub action actually runs every hour on the 22th minute, not every 22 minutes!
Nuce try though, better luck next time babygirl!


There were some breaking changes on this new version of Webpack.
Just to explain my changes on the code:

Webpack Config files must now specify their build environment as production or development
Extract-text-webpack-plugin doesn't support the new plugin system, and the maintainers decided to deprecate it. See webpack-contrib/extract-text-webpack-plugin#701. It is now replaced by mini-css-extract-plugin
NoEmitOnErrorsPlugin is used by default, so there is no need to specify it anymore.

Resolves #544.

Thanks @lgaitan I'll review it this weekend :)


Add Makefile targets for some common/useful development tasks:

Development Make Targets
This adds several new Makefile targets to help streamline local development.
One decision I made on this was to use the docker-compose postgres rather than assuming a locally-hosted Postgres. Might not be everyone's choice.
dev setup tasks:

.venv
/git/hooks/pre-commit
.env

db tasks: reuses the docker db container rather than hosting postgres locally:

startdb
stopdb
migrations

active development tasks:

server
stator

Usage/Example
$ make pydev
python3 -m venv .venv
. .venv/bin/activate
python3 -m pip install -r requirements-dev.txt
[snip install stuff...]
Successfully installed Jinja2-3.1.2 MarkupSafe-2.1.1 Pygments...
[snip install stuff...]
python3 -m pre_commit install
pre-commit installed at .git/hooks/pre-commit

make server
docker compose -f docker/docker-compose.yml up db -d
[+] Running 1/0
 ⠿ Container docker-db-1  Running                                                                                0.0s
python3 -m manage runserver
Watching for file changes with StatReloader
Performing system checks...

System check identified no issues (0 silenced).
January 05, 2023 - 16:33:20
Django version 4.1.5, using settings 'takahe.settings'
Starting development server at http://<IP_ADDRESS>:8000

Closes #357

Thanks for these - do you want to take a stab at writing the documentation for this as well?

Sure, in contributing.md?

No, in docs/contributing.rst if you could - that's where our detailed docs for local dev live.

Yeah that's what I meant, was writing from (bad) memory.


[Run][Calculator Plugin] Support Hexadecimal calculations

Summary of the new feature/enhancement
It would be awesome if I could use PowerToys Run to do quick hexadecimal calculations.
Example input:

0xF + 0x1

Example output:

16
0x10

With the implementation of this groundbreaking new feature, the common error of 0xG could be avoided.
Proposed technical implementation details (optional)
Utilize the Busy Wait Algorithm (BWA) so the user gets the feeling that the computer is thinking very hard.
Bounty
I will post one smiley face emoji upon completion of this task.

I did not find this issue when creating my own. Still in my issue there were other features discussed (binary & conversion in particular), so I would suggest keeping the issue in mind when thinking about implementing this https://github.com/microsoft/PowerToys/issues/4690#issue-649753186
Summary of the new feature/enhancement
PT Run is already my goto way for doing small calculations. However I quite often need to do calculations, as well as conversions with different positional systems (mainly hex and binary).
It would be great if the built in calculator would support hex numbers by using the 0xHH notations and binary numbers by using the 0bXX notation. The result could be presented in the same system that is used in the calculation. If the calculation is mixing systems (for example hex and decimal), the result might default to decimal instead.
A conversion could also be implemented by using a notation similar to python-like casts: hex(some_numer), bin(some_number), dec(some_number).
Some possible calculation examples using the proposed system:
0xff + 0b100000000 -> 511
hex(0xff + 0b100000000) -> 0x1ff
bin(0xac) -> 0b10101100
hex(674) -> 0x2a2

I also like the feature that Keypirinha has, that if I type some calculation I get multiple results with different formats:
> floor(16.5 * 1024) gives the result list:
             16407
            0x4017
0b0100000000010111

this work item may solve this: https://github.com/microsoft/PowerToys/issues/2265 which will encompass https://github.com/microsoft/calculator/issues/526
Need to validate what items it will enable.

PT Run can do this now.  verified under 0.69.1

Would be nice if there was also hex output in a second row to choose from, especially when calculating multiple memory offsets or similar stuff I want to stay in hex for most calculations.

😀

encountered some problem when using hexademical calculation
#29632
It would be great if someone can check what's going on.🌷

Also see #12571 and #27760, making PowerToys Run support programmer conversions would let me stop needing the Windows Calculator app. I regularly convert between binary, decimal, and hexadecimal for my work with Siemens and Rockwell PLCs for industrial automation (factory manufacturing). Bonus points if the common PLC number notations were also supported, e.g. 2#1111_1111 for binary, 8#7777_7777 for octal, and 16#FFFF_FFFF for hex. Lastly it would be nice if this were more clearly documented in PowerToys; I had no clue the Run dialog supported hex until I searched the Github and found this issue. I did try entering 16#80A4 into the run dialog but nothing happened, so I assumed there wasn't any support. Here are some representative calculations I currently do with Windows calculator and sites like https://www.rapidtables.com/convert/number/hex-to-decimal.html?x=80A4
Convert 1310 from decimal to binary for setting DIP switches for a Siemens F-Address:
1310 → 2#0101_0001_1110
Convert binary error code from raw device output into decimal for lookup in device manufacturer's error manual:
2#1101_1110 → 222 Atlas Copco Henrob "Die Check Camera: Ref. Image Does not Exist"
Convert unsigned decimal error code from raw device output into hexadecimal for lookup in device manufacturer's error manual:
32932 → 16#80A4 Siemens "The CPU does not support this function"
Convert signed decimal error code from raw device output into hexadecimal for lookup in device manufacturer's error manual:
-32604 → 16#80A4 Siemens  "The CPU does not support this function"

Any update on being able to convert bases? i.e. like what @dnlmlr said:

hex(674) -> 0x2a2


[Java] JDBC Adapter Build Issue

Rationale for this change
Compiling JDBC Adapter module fails when running from a time zone which is not UTC. The tests assume the set time zone is UTC. Since running from a location where the timezone is not UTC, the error documented in https://github.com/apache/arrow/issues/40619 occurs.
What changes are included in this PR?
Adding the time zone as a property to maven profile.
Are these changes tested?
These changes have been tested locally in a non-UTC timezone (+0530).
Are there any user-facing changes?
No

@github-actions crossbow submit verify-rc-source-java-linux-almalinux-8-amd64

@github-actions crossbow submit java

@github-actions crossbow submit verify-rc-source-java

@github-actions crossbow submit java

It seems like this PR is not breaking any CIs.
Except for the known and documented issues:

Issue in CI -> Documented
Issue in CI -> Documented

Probably better to wait until the issues which are unrelated to this modification though validates it.

@github-actions crossbow submit -g java


Support other regex dialects than JavaScript

Fix #193
Changes

Support other regex dialects than JavaScript

Codecov Report

Merging #378 (7b93eb2) into main (6246719) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 7b93eb2 differs from pull request most recent head eed206d. Consider uploading reports for the commit eed206d to get more accurate results

@@            Coverage Diff             @@
##              main      #378    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           66        56    -10
  Lines         2666      1848   -818
  Branches       241        88   -153
==========================================
- Hits          2666      1848   -818

Impacted Files
Coverage Δ

packages/recheck/src/lib/worker-pool.ts

packages/recheck/src/lib/exe.ts

packages/recheck/src/lib/env.ts

...ges/eslint-plugin-redos/src/rules/no-vulnerable.ts

packages/recheck/src/lib/java.ts

packages/recheck/src/lib/agent.ts

packages/recheck/src/lib/native.ts

packages/recheck/src/browser.ts

packages/recheck/src/lib/pure.ts

packages/recheck/src/main.ts

Continue to review full report at Codecov.

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

Good work! At least I need supports for atomic groups and possessive quantifiers.

Hey @makenowjust! Awesome work here. What do you need to push this?


{testsdk} Initialize random config dir in setUp

Fix #28848
Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

testsdk


Reimplement GCV microservices

The GCV services API was previously implemented as microservices. For various reasons, these microservices never made it into production. Since then, the services API has changed and so has the tech stack. Reimplement the microservices to conform to the updated API using the new stack.

The genes microservice was implemented in commit 60a953a910545b607266b02e36c33de45e74a1a9.

The chromosome microservice was implemented in commit 400a43de6aed274918a9b51fab2e0339ab6afbec.

The micro-synteny search microservice was implemented in commit a9b359141f1731c4fff0dfceeda25829552f46ac.

The macro-synteny microservices were implemented in commit 6029ad393796da5bd9616f4cd02ac29b047b9fed. There's one service that general macro-synteny requests (e.g. wildcards that match all chromosomes in the database) are sent to and another service that that service sends pairwise macro-synteny requests to, i.e. the query chromosome compared to one other.
The latter takes less than 1 second to compute blocks between two chromosomes, but enough requests are sent that computing all pairwise blocks between the query chromosome and all chromosomes in the database takes several seconds, e.g. ~6 seconds for Glycine max chromosome 15. The bottleneck by a factor of 1 is loading all the genes for the target chromosome from the database. This performance could be improved by updating the database request to be asynchronous (see issue #13) and/or updating the Redis schema to store each chromosome's ordered list of gene families in a Redis list, rather than using RediSearch to exact match the genes' chromosome name and then ordering by the index. Alternatively (or additionally), multiple instances of the pairwise service could be run so the load can be balanced across them (this can be achieved as part of issue #11).

Commit 30c7bef46a3190f688813ca4233b5a273f1bea9a removed the previous microservice implementations that didn't conform to the version 1 or 2 services APIs and were replaced by the microservices documented in this issue. Closing.

Commit f8a155435647c19c35e491e1e2d6921049bd1fc4 removed the core Python module that the deprecated microservice implementations were built on.


[TESTING/WIP] deps: Bump com_google_protobuf + friends

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

cc @adisuissa as discussed/expected this is a very failing attempt to update protobuf
some things in this PR are defo useful - the patch, the sha updates, date updates etc - the updated protoc in the PR works
the core problem i hit is that protobuf expects more depedencies, and i think due to the way we load in api_build_system we dont get/load them
i worked around those to the point of  not getting upstream errors - and instead this:

ERROR: /build/tmp/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/external/com_google_protobuf/python/BUILD.bazel:54:20: in internal_copy_files_impl rule @com_google_protobuf//python:copied_wkt_proto_files:
Traceback (most recent call last):
	File "/build/tmp/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/external/com_google_protobuf/python/internal.bzl", line 11, column 17, in _internal_copy_files_impl
		fail("Source does not start with %s: %s" %
Error in fail: Source does not start with src/: ../com_google_protobuf/src/google/protobuf/any.proto
ERROR: /build/tmp/_bazel_envoybuild/b570b5ccd0454dc9af9f65ab1833764d/external/com_google_protobuf/python/BUILD.bazel:54:20: Analysis of target '@com_google_protobuf//python:copied_wkt_proto_files' failed

anyhow - feel free to fork this or lmk if you want me to update/pursue it


Update API so uploading an image doesn't cause the thumbnail to resize 3 times

This GH is being created as the counterpart to this E/app github, per @chiragsalian's request:

can you create an issue and assign it to me so that i can make the API changes.

Action Performed:

Open any chat
Upload a larger file to share

Expected Result:
The API should support thumbnail should load once uploaded, or if it's a large file it should display a spinner until it's uploaded. We need to update the API to return the dimensions of the image upload.
Actual Result:
If you share an image, the uploading thumbnail resizes 3 times. Then it finalizes the upload.
Workaround:

Can the user still use Expensify without this being fixed? Have you informed them of the workaround?

No
Platform:

Where is this issue occurring?

Web

Let me know if it's ok to keep this in the E/App repository @chiragsalian (I can make it under E/E if that's better)?

I think its fine as is. I've just put the PR for review.

weeeeee

This went to prod last week. Closing issue.


feat: encoder runtime arguments check

Description
Fixes #1227
Checklist:

[ ] I have reviewed my diff in github, line by line.
[ ] Every change is related to the PR description.
[ ] I have linked this pull request to the issue(s) that it resolves.
[ ] There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
[ ] The branch has been merged or rebased against the head of its merge target.
[ ] I'm happy for the PR to be merged at the reviewer's next convenience.

Hopefully your next commit avoids the spot instance issues


Getting no registered kernels ConfigureDistributedTPU for 'meta_pseudo_labels'

Traceback (most recent call last):
File "meta_pseudo_labels/main.py", line 463, in main
train_tpu(params, should_eval=should_eval)
File "meta_pseudo_labels/main.py", line 237, in train_tpu
set_tpu_info(params)
File "meta_pseudo_labels/main.py", line 68, in set_tpu_info
topology_proto = sess.run(tpu_init)
File "/usr/local/lib/python3.7/dist-packages/tensorflow_core/python/client/session.py", line 956, in run
run_metadata_ptr)
File "/usr/local/lib/python3.7/dist-packages/tensorflow_core/python/client/session.py", line 1180, in _run
feed_dict_tensor, options, run_metadata)
File "/usr/local/lib/python3.7/dist-packages/tensorflow_core/python/client/session.py", line 1359, in _do_run
run_metadata)
File "/usr/local/lib/python3.7/dist-packages/tensorflow_core/python/client/session.py", line 1384, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: No OpKernel was registered to support Op 'ConfigureDistributedTPU' used by node ConfigureDistributedTPU (defined at /usr/local/lib/p
ython3.7/dist-packages/tensorflow_core/python/framework/ops.py:1748) with these attrs: [tpu_embedding_config="", is_global_init=false, embedding_config=""]
Registered devices: [CPU, XLA_CPU]
Registered kernels:

[[ConfigureDistributedTPU]]
I0322 13:53:47.967103<PHONE_NUMBER>98304 main.py:470] Failed 50 times. Retry!

i have the same problem. And i summarize some corresponding questions in mpl code.
(btw, i use colab-tpu to run this work.)
question 1: i can not find the parameter 'num_cores_per_replica' in main.py(line 71). And the paremeter is not defined in flag_utils.py.
question 2: i donot know which tpu_lib  is imported in main.py(line 66).
thank you very much!

Traceback (most recent call last): File "meta_pseudo_labels/main.py", line 463, in main train_tpu(params, should_eval=should_eval) File "meta_pseudo_labels/main.py", line 237, in train_tpu set_tpu_info(params) File "meta_pseudo_labels/main.py", line 68, in set_tpu_info topology_proto = sess.run(tpu_init) File "/usr/local/lib/python3.7/dist-packages/tensorflow_core/python/client/session.py", line 956, in run run_metadata_ptr) File "/usr/local/lib/python3.7/dist-packages/tensorflow_core/python/client/session.py", line 1180, in _run feed_dict_tensor, options, run_metadata) File "/usr/local/lib/python3.7/dist-packages/tensorflow_core/python/client/session.py", line 1359, in _do_run run_metadata) File "/usr/local/lib/python3.7/dist-packages/tensorflow_core/python/client/session.py", line 1384, in _do_call raise type(e)(node_def, op, message) tensorflow.python.framework.errors_impl.InvalidArgumentError: No OpKernel was registered to support Op 'ConfigureDistributedTPU' used by node ConfigureDistributedTPU (defined at /usr/local/lib/p ython3.7/dist-packages/tensorflow_core/python/framework/ops.py:1748) with these attrs: [tpu_embedding_config="", is_global_init=false, embedding_config=""] Registered devices: [CPU, XLA_CPU] Registered kernels: [[ConfigureDistributedTPU]] I0322 13:53:47.967103<PHONE_NUMBER>98304 main.py:470] Failed 50 times. Retry!

Hi, have u solved this problem?

In first thread, the code can initial the model successful. But in the second thread, 'ConfigureDistributedTPU' can not find ‘TPU’?


Creating virtual monitors/displays

Hey, i'm a linux user who travels a lot and works remotely, and what i carry on my travel is my laptop and a pair of vr googles,
What i do in in x11 right now is making the system believe there are occupied existing inputs when they are not occupied but the inputs do exist, is very clunky and messy because the method changes whether you use nvidia, intel or radeon and is really inconsistent.
with those existing inputs i can see them through the vr googles with something like immersed and then work with 3 or 4 giant displays easily instead of the 1 small display that my laptop has, i would really like if in hyprland you could create virtual displays.
i have read the wiki and did not found something useful in order to do so, if i'm wrong, and there is a way to do this, please, tell me.

no clue about your usecase but hyprctl output: https://wiki.hyprland.org/Configuring/Using-hyprctl/#output

all config


test: add angular distribution tests from pycompwa

First test is ported from pycompwa, together with some fixture code.
I also made a small change to the variable names, as they were not consistent.
The second one I will tackle tomorrow. But this will serve as the baseline for all other distribution test.
@redeboer @Leongrim @sebastianJaeger , take a look if you like the test setup. Ideally I would like you to possibly extend this with your channels.
Closes #181
TODOs:

[x] add second pycompwa distribution check
[x] add scipy as a test dependency
[ ] Test channels of @Leongrim @sebastianJaeger

I would just keep this PR as it is and @Leongrim  and @sebastianJaeger  can add their channels in follow up PRs. It also reflects the title this way.

I would just keep this PR as it is and @Leongrim  and @sebastianJaeger  can add their channels in follow up PRs. It also reflects the title this way.