Figure out how to get .m4b to save processing time

I've been looking into this but haven't found an API yet.
The iOS app seems to not use it either (confirmed via Proxyman)
When using the web UI, there is a button to download it which then redirects to the correct signed asset request. However I have not figured out whether the API can do that too.
PS: Current version of the API seems to be v10

Yeah, i poked around on web for awhile but the signed assets would be difficult to handle without API support. Poking through the android app doesn't show any API support for .m4b at all.

PS: Current version of the API seems to be v10

let me make an issue to unify the endpoints. I grabbed them off some other libro fm code or issues.


More Fishing

Can you add fishing for the fishrod and the item received is customizable?

I didn't quite understand your suggestion. Do you want me to add the functionality to be able to fish? Or that the API method returns a customizable item?


Suggestions to speed up pytest-spark tests

The spark session created by pytest-spark is not so optimized for small unit tests that only work with small dataframes.
pytest-spark seems to rely on whatever are Spark's default settings:
https://github.com/malexer/pytest-spark/blob/0152b555eb532710fd5bd212bd95134f9342e22f/pytest_spark/__init__.py#L101
Those defaults are aimed at working with some bigger data sets. IMHO it would make more sense to optimize the speed for smaller datasets.
We initially used pytest-spark (thanks for that!), but recently changed to create the spark session fixture with our own code (kudos to @artem-garmash!).
    """
    Parameters to reduce parallelism to make it run faster with test data
    """
    spark = SparkSession.builder \
        .config('spark.sql.shuffle.partitions', 1) \
        .config('spark.default.parallelism', 1) \
        .config('spark.rdd.compress', False) \
        .config('spark.shuffle.compress', False) \
        .enableHiveSupport() \
        .getOrCreate()

In our case the total test duration went from 7m:38s down to 3m:03s thanks to this change.

Also relates to https://github.com/malexer/pytest-spark/issues/8. To me it seems that ideally pytest-spark could offer defaults that are optimized for small datasets and then also somehow allow customizing any values of spark config.

Added in version 0.5.1, already on Pypi

I came here from google, trying to speed up our pytest tests in github actions, and it was a fruitful day. We used those spark defaults  https://pypi.org/project/pytest-spark/ and reduced time from 6 minutes to 3 minutes.
Then tweaked more

Added pytest-parallel plugin and passed --workers=2 - 10 seconds faster
To utilise it fully .set("spark.executor.cores", 2) - so 2 cores would handle 2 threads - 10 seconds faster


Allow transform non-2xx request to 2xx request in simple mode.

Used in transform 304 response to 200 response with local cache.

That is a very good idea!
This would mean the transform function would just change the statusCode and the response would be "reresolved" accordingly.
function (body, response, resolveWithFullResponse) {
    // Get data from the cache etc.
    response.statusCode = 200
    return response
}

However, this solution doesn't go with resolveWithFullResponse = false yet...

If resolveWithFullResponse = false set, it usually means the status code (also headers etc) are not important to the coder. So I think just retain the status code when resolveWithFullResponse = false is OK

Just to make sure I really understand you correctly:

You do a request with option simple = true
The server sends a 304 response
You apply the transform that shall be able to change the statusCode to 200
request-promise does not return the response to .catch(...) anymore
Instead, request-promise returns the response to .then(...)

Correct? Or are you working with simple = false to begin with and are not worried about getting the response returned to .catch(...) anyway?

Yep this is my opinion.
I tried to working with simple = false, but I also need others rejections
like 404.
Transform non-304 into rejection under simple = false makes my code even
more complicated...
Sincerely
George Chung
2016-09-28 1:35 GMT+08:00 Nicolai Kamenzky<EMAIL_ADDRESS>
Just to make sure I really understand you correctly:

You do a request with option simple = true
The server sends a 304 response
You apply the transform that shall be able to change the statusCode
to 200
request-promise does not return the response to .catch(...) anymore
Instead, request-promise returns the response to .then(...)

Correct? Or are you working with simple = false to begin with and are not
worried about getting the response returned to .catch(...) anyway?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/request/promise-core/issues/2#issuecomment-249938821,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACYml2U8EOgGVU_f3YeSTBP1m6cHAd0lks5quVP1gaJpZM4KCnAF
.


[3742] Implement api endpoint for provider courses#show

Context

https://trello.com/c/ekPzeeJr/3742-s-implement-api-endpoint-api-v3-recruitmentcycles-year-providers-providercode-courses-coursecode
Adds public/v1 api endpoint for providers courses#show

Changes proposed in this pull request

Add RecruitmentCycle serialiser
Add endpoint for courses on providers for public API

Guidance to review

Should be able to fetch a course via endpoint
Should be able to specify includes for endpoint and they should be returned in the response

Checklist

[x] Make sure all information from the Trello card is in here
[x] Attach to Trello card
[x] Rebased master
[x] Cleaned commit history
[x] Tested by running locally

 [S] Implement API endpoint - /api/v3/recruitment_cycles/:year/providers/:provider_code/courses/:course_code


Array parameters changed from foo[]=1&foo[]=2 to foo=1&foo=2

After a recent update of master, I find that array parameters are passed through differently (see title). This broke querying with array parameters for my Rails-based API.
I suspect that 33ba3149bbe0e112a764213ef9aa9b969af4da82 is the culprit, with url.format using querystring to create the query string, instead of passing through the path as composed by qs (I guess here).

thanks for reporting this! can you give some quick example code of how you were running into this issue? (is it in a controller or?)

I guess this would help - #423

Good news, bad news on this.. i can pretty easily get it to output ?q[0]=1&q[1]=3 but not ?q[]=1&q[]=3 - and i'm pretty sure things like rails doesn't like the index to be there.  The reason why it currently outputs ?q=1&q=3 is
qs is setup to be able to parse either option, but i think it only ever outputs with index.  Would having the index in the array be a deal breaker for you?  I'm having problems finding anything in node that formats it with []'s.

Thanks for looking into this!
I've tested Ruby on Rails 4.1.6 and that doesn't accept arrays indexed with numbers :( And I'm probably not the only one using Rails. I see a couple of options:

Fix qs (e.g. when option indices is set to 'empty' output with ?q[]=1&q[]=3)
Use querystring like before (though it's been a while since its last update)
Use qs2
Document how to handle this server-side

It seems this has the attention of upstream :) See https://github.com/hapijs/qs/issues/46 and https://github.com/hapijs/qs/pull/65

thanks for all the info on this! just opened up a PR for it.

Thank you, it works! And I guess after arrayFormat has been implemented, we might be able to use qs again.


Add furniture/amenities icons

Related to #1453, #1454 and #1461.
wardrobe/cabinet-filing alts:

@danielbayley Usecase is not clear to me for:
desk-lamp, pillow and rocking-chair.

This PR is merged to the lab branch. This PR does not match our PR template, which requires valid use cases. To move on we merged this PR to the lab branch, which will be moved to a separate repo in the future.


move deployment info to fh-deploy

This PR removes most deployment info from the docs which is added to fh-deloy in this PR.
Note: I didn't remove the deployment info in the e2e tutorial as it would have ruined the flow of the tutorial.

Thanks! I'll just delete this nb and link from the docs to the deploy project


ui: Settings screen according to figma

Adapt Settings screen according to Figma.
Differences:

"Log out" is in section "Wallet" instead of "Settings"

Question:

Should the "Create new wallet" button be removed? Personally, leaning towards "Yes". (related https://github.com/joinmarket-webui/joinmarket-webui/issues/228)

📸 Before

📸 After

the Logout is for the whole app, not on wallet level. it should go over Wallet category please :)

maybe even "Log out from Jam"

Hmm.. I am not sure I know what this means.
Currently "logging out" is just forgetting the session key. What should happen, when someone "logs out"?

its should bring you to "login page" https://www.figma.com/file/kfejZJFlwBywvLEnPEmJo1/?node-id=3994%3A73345
but I think we do not have that yet

the Logout is for the whole app, not on wallet level.

I think these are equivalent things at this time (as @theborakompanioni mentioned) right?

I think that "log out" from Wallet, because its now underneath is misleading.
logout should be only used when the user logged in somewhere, if that's not the case, we need to rethink what's actually happening.
I would move logout back up again and hide it as long as we don't have login implemented. why would a user logout aka "lock" the wallet and not just close the window?

I would move logout back up again and hide it as long as we don't have login implemented.

Removed it for now.

why would a user logout aka "lock" the wallet and not just close the window?

You are right, the (now removed) "Log out" action, by forgetting the auth token, would have been the same as closing the window.
However, I can relate to some uneasiness when closing a tab with an "unlocked" wallet. A dedicated button would "feel" a little better, albeit there is no difference in what actually happens.

what happens when we just close the window?

The auth token is removed (as sessionStorage cleared when the page session ends).

~
so we have:
* **create wallet**: creating new wallets, not possible while another wallet is still used and unlocked

* **unlock wallet**: wallet is _inactive_, **needs password** to be active

* **open wallet**: entering, using, wallet is _active_

* **lock wallet**: deactivate wallet, wallet is now _inactive_

* **Logout** wallet (misunderstanding): wallet stays active in the background, **needs password** to be opened/ entered again

Maybe something like "Leave wallet", "Exit wallet" or "Close wallet" (although the term "Closing" might be confused by "Locking")?
In any case, I have just removed it for now and will support anything that you think makes most sense from an UI/UX perspective.
Do you think these changes can be merged?

Removing seems like n acceptable solution for now. 👍  All the nuances are way to complicated, we really need to figure out a good concept for this.

A little padding for the buttons on mobile would be great.

A little padding for the buttons on mobile would be great.

Yeah, did not change that, as I supposed it was intentional. Any improvements are very welcome! Feel free to just push to this branch!

Yeah, did not change that

Good point! :D Will push an update.

@theborakompanioni, I was taking inspiration for ConfirmModal use case and found out that this feature doesn't work here. If you want I can work on it?

@theborakompanioni, I was taking inspiration for ConfirmModal use case and found out that this feature doesn't work here. If you want I can work on it?

I am not quite sure what you are referring to.. can you elaborate?

Confirm modal wants you to confirm that you really want to do this.
But there's no modal opening up here.

@theborakompanioni let's discuss this in tomorrow's meeting.
If there's no meeting, we'll discuss this in one-on-one call.


specify edge ids in protos - avoid id clashes with nodes

nodes and edges have the same id namespace - to ensure we don't
accidentally assign an id to an edge that was supposed to be used by a
node later on, we're now storing the edge ids as well
this change is backwards compatible, but all frontends need to be
updated for this to have any effect

nodes and edges have the same id namespace

actually, that's not true! let's hold back on this


godot 3.1 beta 9 does not save last opening scence and last opening script

Godot version:

v3.1 beta 9
OS/device including version:

windows 10 Pro, GTX 1060 6GB
Issue description:

Godot 3.1 beta 9 does not save last opening scence and last opening script. This issue makes me quite alot time to come back last place to working.
I try at v3.1 beta 8, is is still ok.
Steps to reproduce:

open some scene and some script.
restart godot.

Minimal reproduction project:

Indeed, that's #26359 which has been fixed since then. I'll add it to the beta 9 blog post.


KAFKA-4818: Exactly once transactional clients

Thanks for the review @ijuma!
For some context. The main changes for the producer are in Sender and in TransactionState. The TransactionState class has nearly all the code for handling transactions.
Essentially, the producer continues to have a single background thread it uses to send requests. The main difference is that transactional RPCs have the highest priority: if there is any such request waiting to be sent or in flight, no ProduceRequests are sent.
The TransactionState maintains a queue of Transactional requests, ordered by priority. Some requests like FindCoordinator must always be sent first. Also EndTxn must always go last, etc. This class also manages chaining requests: so if we need to send to a coordinator, but don't have a coordinator yet, it will put the FindCoordinator request at the head of the queue.
The TransactionsTest has all the tests for the new flows.
On the consumer side, things are much simpler. All the main logic is in the Fetcher  in the PartitionRecords sub class. Here we, we decide to drop batches based on the contents of the abort index received in the fetch request.
The FetcherTest has new test cases for the consumer side fetcher changes.

Also, there is a merge conflict due to https://github.com/apache/kafka/commit/17ce2a7307222d7476eb60318fab2e672eebe559

I fixed the correctness comments and fixed the merge conflicts after rebasing onto trunk.

@hachikuji, I took care of all the major comments, and most of the minor ones. Main changes  include:

Introduced more formal states to TransactionState and made the state transition checks more formal.
Stopped throwing exceptions from completion handlers.
If the Transaction is in ERROR state, the next transactional method will fail.
The transaction can be in error state if any transactional request or produce request within the transaction had a fatal error.

The only thing remaining is to cache errors from background requests like AddPartitions and FindCoordinator and propagate those on the next user-facing method. Currently we just log these errors. But that should be a minor change relatively speaking, so this is ready for review.

System test run: http://jenkins.confluent.io/job/system-test-kafka-branch-builder/857/

Rebased onto trunk and kicked off a new system test build with the latest changes: http://jenkins.confluent.io/job/system-test-kafka-branch-builder/860/

System tests passed..

Merging to trunk.


[Question]

Please follow the general troubleshooting steps first:

[x] I've Read the official README v1 or README v2?
[x] I've Read the official API reference?

Question related to which version: 2.0.0-nullsafety.2
Description
Is there any method that returns the remaining time to the next prayer? Looking at the documentation, I only see that I can get the current date but nothing else.

Assalamualaikum,
Brother you can just easily calculate  remaining time yourself in Dart.
final remainingTimeDifference = DateTime.now().difference(prayerTimes.fajr)

Thanks.


Rspec unable to test #call method's receive count.

Subject of the issue

Your environment

Ruby version: 2.3
rspec-mocks version: 3.2

Steps to reproduce
try to test a method is invoked with .call
it "should receive first method", :te=>true do
a = [1,2]
m = a.method(:first)
expect(a).to receive(:first)
m.call
end
Expected behavior
expect to receive 1 time
Actual behavior
receive only 0 time
How can I test this use case?

m = a.method(:first) binds m to the current implementation of first.  Later, when m is called, it does not send the :first message.
expect(a).to receive(:first) expects that a receives the :first message.  It replaces the implementation of the first method with one that tracks whether or not it has received the message.  Since m was bound before the expectation was set, calling m runs the original logic and not the replaced implementation that rspec-mocks has set up.  So the spec doesn't work like how you want.
You can make it work by binding m to a callable that sends the first message:
  it "should receive first method", :te=>true do
    a = [1,2]
    m = -> { a.send(:first) }
    expect(a).to receive(:first)
    m.call
  end

...or by binding m to the first method after setting up the expectation:
  it "should receive first method", :te=>true do
    a = [1,2]
    expect(a).to receive(:first)
    m = a.method(:first)
    m.call
  end


refactor: add eslint, change to travis and add some sample files

:tada: This PR is included in version 1.4.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Promise.all should accept any iterable, not just Array

According to the MDN, Promise.all should accept any iterable, not just Array.

Perhaps this could be as simple as wrapping the value Promise.all() receives in Array.from, if it exists.

Ya, totally agree and it is planned to add this support.


Integration test log compiler

This patch series adds infrastructure that creates a private simulator and tabrmd instance for each integration test before the test is executed. This allows us to add all of the integration tests to the test harness and run them as we do all the unit tests: make -j$(nproc) check.

this resolves #75

Cleaned up the script a bit. Had some debug stuff left in it.


spirv-fuzz: Edit TransformationLoad structure to supporting OpLoad and OpAtomicLoad together.

This RR is just to support the "TransformationLoad" new structure.
Part of #4324.

@afd  ping.
when you accept changes I will merge this branch with the main branch I worked on it. What do you think?


list: showing v1.33.0-dev as latest version

google.golang.org/grpc: v1.30.0 [latest v1.33.0-dev]

perhaps versions with metadata should be skipped.

skipping pre-release versions blocks all pre-v1 versions from showing up.

I've added a opt-in -pre flag to both the get and list subcommands which enable using pre-release versions. v0 pre-release versions are allowed no-matter what.


Write mini.resize

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.resize
Description
A sub-plugin like smart-splits.nvim helps people easily resize their windows.
Neovim isn't a gui software thus resizing the windows is troublesome. This feature is simple but useful.
Expected behaviors (like smart-splits.nvim):

Normally it doesn't map any key to resize since people generally don't need to resize the windows.
It creates the resize-mode which allows us to resize the windows by h/j/k/l.

I can help you implement this sub-plugin if you want it in mini.nvim. Of course, it is totally ok if you want to implement it by yourself.

Interestingly enough, it was already suggested in #12. Using Alt + hjkl is in somewhat of a "mode" in itself as Alt can be pressed. And creating splits seems not that inconvenient with built-in <C-w> + sv.
What exactly do you feel is troublesome in Neovim with resizing windows?

Well, it does like a duplicated issue. Thanks for your reply.


reduce strategy weight cost and also scale by weight

This should handle the issue of low weights not firing because it scales the relative weights.

Still need test and deployment, also one other issue is that we might to take into consideration the amount being added/deducted, since if it's a huge amount, then putting into the lower weight strategy might not make sense, and this can be done with just another add and parameter pass.

@crazybuster The effect of this change is that super low values for the "percent" allocated to the strategy no longer "cap" the amount of funds moved to the strategy? If so, can't we work around this for now by just using big numbers for our "percentages"? Or is there some other issue?

@crazybuster The effect of this change is that super low values for the "percent" allocated to the strategy no longer "cap" the amount of funds moved to the strategy? If so, can't we work around this for now by just using big numbers for our "percentages"? Or is there some other issue?

Yes, we can work around this(and we do currently) if our relative strategies have similar weight amounts.


Cant break Mechanical Placer and miner on server

https://s1.sunekaer.com/i/07-08-2021_21-46-06_%25pn.gif
https://paste.sunekaer.com/forumibuge.md

fixed in dev


add proposal timestamp migration

Codecov Report

Merging #417 (b58a921) into jchalam/proposalModulePrefix2 (9d813e7) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@                        Coverage Diff                        @@
##           jchalam/proposalModulePrefix2     #417      +/-   ##
=================================================================
+ Coverage                          95.58%   95.60%   +0.02%
=================================================================
  Files                                 33       33
  Lines                               5026     5051      +25
=================================================================
+ Hits                                4804     4829      +25
  Misses                               222      222

Impacted Files
Coverage Δ

contracts/cw-proposal-single/src/contract.rs
92.60% <100.00%> (+0.59%)
:arrow_up:

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


main branch

Let's get a main branch going if we could. this takes 2 minutes
https://www.hanselman.com/blog/EasilyRenameYourGitDefaultBranchFromMasterToMain.aspx

And this manual will update all forks, local clones, scripts on the CI/CD servers and other related stuff in the some miracle way?

No not at all, just thought it would be great to get the convo started.
I was going to use my existing pre commit hooks to catch such wording with this tool.. then I also realized I'm referencing the master branch in my pre commit hooks.
I'm certainly not saying to blow away master and break everything so I apologize for being so vague initially


Package request: nak

Project description
a command line tool for doing all things nostr
Metadata

homepage URL: https://github.com/fiatjaf/nak
source URL: https://github.com/fiatjaf/nak
license: mit
platforms: darwin, freebsd, darwin

Add a :+1: reaction to issues you find important.

The flake I wrote is here.
https://github.com/comamoca/flake-nak


Add dumb and manual theme caching systems to Window

A continuation of https://github.com/godotengine/godot/pull/65156, but for Window and its derivatives this time. I've also added the dumb caching system previously introduced for controls in https://github.com/godotengine/godot/pull/64314, because that's only reasonable.
In relation to windows there is one thing that I didn't touch here, but that needs some rework later on. When a Viewport is handling its subwindows, all drawing code is in the Viewport class, which makes it very inconvenient to introduce the cache, and it also moves responsibilities to outside of Window, and spreads the string usage beyond where we can control it. Juan wasn't against me reworking this bit to organize the code a bit better and encapsulate some of the Viewport::_sub_window_* methods' logic inside of Window. But I'll look into it at a later date.
I also want to bring back WindowDialog removed during the multiwindow/viewport refactoring. Currently the base "dialog" node is AcceptDialog, which has extra stuff like buttons. IMO a more basic class is needed, and since we used to have it in WindowDialog, it's sensible to me to bring it back. This should also clean up the styles for dialogs, as currently all the base styles are defined in AcceptDialog (and before this PR there was a mystical Dialogs theme type which was manually polled for items, instead of using inheritance like we do elsewhere).
Other than that, this is a straightforward version of https://github.com/godotengine/godot/pull/65156 for Windows. It's also independent, so if the general concept is approved and the code is good it can be merged before the other one.

Thanks!


NavigationAgents - schedule pathfinds to prevent performance blips

Adds a simple method to limit pathfinds per physics tick.
Pathfinds in the navigation server are currently synchronous, and can cause performance blips and dropped frames if several agents do a pathfind simultaneously. This PR enables simply limiting the number of pathfinds per physics tick.
Notes

Adds a project setting navigation/common/pathfinding/paths_per_tick. This can either be positive, 0 (unlimited), or negative, indicating a single pathfind every nth tick.
Overall it is usually better (especially with large navmeshes) to distribute single pathfinds over several frames. But this would require major changes to the current design, so this PR is a reasonable compromise to get started managing performance.
Duplicates some code in 2D and 3D versions. Could be moved out into a separate class if desired, am initially following the preference for local solutions (even if duplication occurs). See https://docs.godotengine.org/en/stable/community/contributing/best_practices_for_engine_contributors.html#prefer-local-solutions
Also relevant to 4.x.

CC @smix8 @Scony @AndreaCatania

I like the overall idea, but I don't like the implementation:

project setting navigation/common/pathfinding/paths_per_tick aggregates 2 features - one for positive values with zero and another one for negative values. IMO that should be split into 2
code is  duplicated across 2D and 3D
the setting is static - cannot be manipulated at runtime

IMO, the much better way would be to implement the solution within the navigation server (something like async map_get_path). Moving the setting there as well would make it possible to manipulate it in the runtime. Moreover, having the entire knowledge of path calculation requests (FIFO queue) in one place would make it very easy to introduce more sophisticated algorithms on how to distribute requests among frames. Not to mention such a solution could be exposed to the user. There are plenty of use cases in games where AI must recalculate the path from time to time while it's not time-critical. It would be nice if there was an API that allows user to request path calculation "somewhere in the future when the load is not that big".

project setting navigation/common/pathfinding/paths_per_tick aggregates 2 features - one for positive values with zero and another one for negative values. IMO that should be split into 2
code is duplicated across 2D and 3D
the setting is static - cannot be manipulated at runtime

All these are easy to change.

IMO, the much better way would be to implement the solution within the navigation server (something like async map_get_path).

Yes, as I said here in the notes:

Overall it is usually better (especially with large navmeshes) to distribute single pathfinds over several frames. But this would require major changes to the current design, so this PR is a reasonable compromise to get started managing performance.

Writing async version will probably require some major rework from the navigation maintainers to get working without causing stalls (if anyone wants to volunteer for this? :grin: ). In the meantime, although 4.x is in beta, 3.x is expected to be used in production, and imo it is better to have a stop gap solution that works than nothing at all, so people can continue to ship games.
Essentially, 3.5 stable is right around the corner so if possible it would be good to clear up the major problems with the navigation asap (robustness and performance), and have a usable solution - bearing in mind we don't have time for another long series of betas for async pathfinding.

IMO it will not.

Then maybe you can add it? :+1:

Once users start using above implementation it will be much harder to push for the proper one.

In terms of project setting we could probably just have a toggle for deferred_pathfinding, and reuse this for async at a later date. In terms of feature implementation, async pathfinding is pretty much standard for AI, I don't think anyone will be holding back the development.

Actually, I'm busy rewriting the entire navigation system using Recast/Detour/Crowd as a plugin/module :)
Nevertheless, having a feature switch deferred_pathfinding - off by default - would make this implementation acceptable IMO. Whoever would need it would use it and yet It would be much less harmful to the average user if we replace it later.
I'd just call to split navigation/common/pathfinding/paths_per_tick and duplicate the code in that case.
Ofc. Feel free to disagree :) Maybe @smix8 can give some thoughts as well.

I think the idea of this pr to slice the updates over multiple frames is good but I think we should implement this differently.
Navigation timeslice as a feature is needed, no doubt. The current NavigationAgent navigation leads to frame spikes that could be easily avoided if not all NavigationAgents node would call for updates in the same frame. I think that change is not time critical for Godot 3.5. In my tests performance is not really worse than old navigation in <3.5 before the NavigationServer backports. We can give us some time to figure things out properly for something that works in both Godot 4.0 and 3.5.1 or 3.6.
I think this should be implemented in Godot 4.0 first and later backported. With the many recent updates and backports for Godot 3.5 we have near identical navigation code in 3.5 and 4.0 now. This was a struggle to achieve. Every addition, if not very specific for Godot 3.5 codebase, should be made for Godot 4.0 first and then backported to Godot 3.5, if it works.
I think navigation features like timeslicing path queries here should not be made NavigationAgent node exclusive. Navigation features should work with pure NavigationServer API use first and then be added to any node that uses said API functions cause not everyone wants to and should use the NavigationAgent node as it is very restricting. This means this feature needs to be added on the NavigationServer and not on the NavigationAgent node, e.g. with a queue on the NavigationServer like Scony suggested.
Async/Deferred/WhateverMode path queries should never be a bool toggle for the entire project. Some actors are just more important than others and some situations need instant updates while others are more performance aware. So this should be a parameter on the actual path query. Could still add a funnel on the node like in this pr but the time slice should be in the hands of the NavigationServer and not some random node. My prefered way to add a "deferred" parameter for path queries would be with the NavigationPathQueryParameters3D objects from pr #62429. Could easily add a property like NavigationPathQueryParameters3D.path_callback = "method_name" to it. When a callback is available the NavigationServer will process the path query not immediately but only when it has time. I would prefer shifting to such Parameter objects like physics does as it makes it so much easier to add / rework features in the backend without breaking compatibility and add class documentation.
I think settings like those discussed should be part of the NavigationServer and changeable at any time from scripts not a "hardcoded" projectsetting that is only updated at the start. In general I prefer to move navigation related properties/settings to the NavigationServer for those that depend on a Godot navigation build anyway. My pr #62601 for navigation debug already tried to clean the SceneTree from as much navigation stuff as possible and move it to the NavigationServer so everything navigation related is in one place.
@Scony If you manage to integrate Detour/Crowd in Godot with the current NavigationServer that would be definitly a feature for a core module in my opinion as it would solve some annoying limitations with the current navigation system. Let me know if you make it available for testing e.g. with a branch.

Closing as stale.


Provide mock IOpipe for user function tests

Users developing with IOpipe will find that calls to context.iopipe.* will fail without a good mock. We should provide a reasonable mock for those users so they do not need to build this themselves.

@ewindisch Can you provide an example of where context.iopipe.* fails? Just so I understand the use case.

Closing s related to #285.


Allow setting custom FREETYPE_LIBRARY/FREETYPE_INCLUDE_DIRS through CMake

I have just upgraded to our latest internal conda environment and noticed that the conda FreeType library has an additional dependency on libXau which apparently is not correctly captured by CMake's FindFreetype. So I need to manually specify the dependency by setting
-D FREETYPE_LIBRARY="$CONDA_PREFIX/lib64/lib/libfreetype.so;/lib64/libXau.so" \
-D FREETYPE_INCLUDE_DIRS=$CONDA_PREFIX/include/freetype2 \

However, for this to work I had to replace the Freetype::Freetype IMPORTED target with the standard pair of FREETYPE_INCLUDE_DIRS/FREETYPE_LIBRARIES vars (thus consolidating the mechanism that was already used my emscripten builds).

@ptosco :what's your take on how I should tag this (bug/enhancement) and which milestone I should assign it to?
Is this a bug fix for 2022.09.2 or something for 2023.03?

@greglandrum I would consider it a bug fix for 2022.09.2 - the way it previously worked prevented setting an explicit path to FreeType library and headers, which can be considered a bug given that's usually possible for most if not all libraries.


Request for the FID Evaluation Code in MAISI

I am currently developing a CT image generation algorithm and would like to compare its performance with the results reported in your work, MAISI. However, we have observed a significant discrepancy between the FID values calculated using our code and those reported in your paper.
To ensure fairness in the comparison, I would like to kindly request the code or implementation details used in MAISI for calculating the FID between generated and real images. This would greatly help in maintaining consistency and accuracy in our evaluations.

Which part of body your algorithm generate?


Failed to build Havit.Blazor locally

I want to propose a few PRs with new components and improvements but can't build the Havit solution locally. My problems:

During the build I get the next error:

Looks like it's some CI artifacts, but I am pretty sure that it's shouldn't be in common code. Is it possible to move it to CI processes or provide a solution on how to disable it locally?

Problem with BootstrapIcon. In remarks for I found the solution how to solve it:

	/// - Update wwwroot\fonts\bootstrap-icons.woff
	/// - Update wwwroot\fonts\bootstrap-icons.woff2
	/// - Update wwwroot\bootstrap-icons.css
	/// - Update bootstrap-icons.json in this folder.

but looks like it does not work for me. Is it possible to provide Powershell (and bash for macOS/Linux) to trigger update these files to automate regeneration of these properties?

There is a SourceLink issue related to the fact we are deploying the project from Azure DevOps. Making the SourceLink conditional should resolve the issue. Will push the fix today.
I believe the fix will also resolve your issue 2).

@sshulik, pull the latest version from master and restart Visual Studio. The build should succeed now.
(fixed with 445c740483703b1040793743b0ddb70116f477f9)


Add Python unittest

Is it worth encouraging unittest now instead of the CW testing framework (and/or deprecating the latter)?

Is it worth encouraging unittest now instead of the CW testing framework (and/or deprecating the latter)?

After people fixed thousands upon thousands Python kata for the last framework, modules, and Python 3.10, I'm not sure if deprecating any of that will go over well.

Also, I notice many testing frameworks are missing guides. I can add these pretty easily from Qualified's docs, but maybe I should defer to someone more familiar with the platform?

but maybe I should defer to someone more familiar with the platform?

No, we can review them and suggest changes if it's awkward in Codewars context. PRs welcomed.

@ggorlen Please open separate PRs, so it's easier to review and merge individually.


pull request for e2e test at 12/11/2016 10:15:03

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Updating concurrent tests count for vsphere e2e tests

Description of changes:
Updating concurrent tests count for vsphere e2e tests
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm

/approve

/cherry-pick release-0.18


Remove ARM64 statement in apt install

The deb package does not support ARM64. Skipping step 3 on Ubuntu will install an old azure-cli package that is not maintained by Azure CLI team in the Microsoft repository. It's old (2.0.81) and many commands are broken. Before any support or test is done in ARM64, let's remove the related statement first.

Docs Build status updates of commit addcd83:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/includes/cli-install-linux-apt.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Perhaps we can explicitly call out that ARM is not supported? So that users won't assume we do have ARM support.

Docs Build status updates of commit f4d00a4:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/includes/cli-install-linux-apt.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Make IHttpRequestStreamReaderFactory public

This interface is currently pub-internal. An implementation is necessary when creating BodyModelBinderProvider or BodyModelBinder instances. This is necessary in user code when creating resource filters that parse the request body. For example, ASP.NET Core WebHooks does this in a few places e.g. https://github.com/aspnet/WebHooks/blob/be8571953a0124c0877f777e8fb5bb17329204ab/src/Microsoft.AspNetCore.WebHooks.Receivers.Stripe/Filters/StripeVerifyNotificationIdFilter.cs.
For reference: https://github.com/aspnet/Mvc/blob/760c8f38678118734399c58c2dac981ea6e47046/src/Microsoft.AspNetCore.Mvc.Core/Internal/IHttpRequestStreamReaderFactory.cs

We should do this in 2.1 - that doesn't immediately help webhooks, but will help it remain stable in the future.


Documentation Chaos:📝[DOCS] adding Stargazers and Forkers section to readme.md

Describe the Documentation Update
Issue Description
adding Stargazers and Forkers section to readme.md
Suggested Change
we can add Stargazers and Forkers section to readme.md
Stargazers
Use Case:

Bookmarking Projects
Discovering Popularity

Benefits:

Visibility
Feedback Indicator
Community Engagement

Forkers
Use Case:

Creating Personal Copies
Contributing Back

Benefits:

Encouraging Innovation
Easy Collaboration
Building Ownership

ADD LABELS HACKTOBERFEST AND GSSOC EXT 24 AND LEVEL 2 OR LEVEL 3
ASSIGN ME THE WORK
THANK YOU @vansh-codes !
Add References or Examples

Confirm

[X] I understand that my update will add to the chaos and I'm okay with it
[X] I agree to follow this project's Code of Conduct
[X] I want to work on this documentation update
[X] I'm GSSOC'24 Extd registered Contributor
[X] I'm Hacktoberfest registered Contributor

Go ahead!


devbox: strange sirepo db structure

run$ pwd
/home/vagrant/src/radiasoft/sirepo/run/run/run

That is the directory structure that is created after running sirepo service http and trying to use sirepo.

I'm not seeing this on my devbox.

A pip install -e . of Sirepo fixed it.


Edit colors of selected element

When the user changes the stroke or shape background color and they have an element selected, they could expect to modify the color of that element instead of having to delete it and draw it again.

I select my element and then change the fill and stroke colors. The change doesn't affect the currently selected element

The change is applied in the next shape I create
I can work on implementing that feature if we think it'd be nice to have.

@paulomenezes is working on this here https://github.com/excalidraw/excalidraw/pull/179

And it got merged 🎉 I'm closing this one. Thank you!


My Excel Files are not showing up /dating up

Describe the bug
When creating a new Excel-Form in OneDrive it does not appear in the Graph Explorer properly.
To Reproduce
Steps to reproduce the behavior:

Create a new Excel File Form
Search in Graph Explorer (My Files, Recent, Search Items...)

Expected behavior
I wanted to see the files and copy its File-ID.
AB#8607

Hello @paulbijancoch!
You can try this:

Get the list of items in your OneDrive using this query https://graph.microsoft.com/v1.0/me/drive/root/children
You should find your document there unless it is in a folder
If your file is in a folder, you get the id of the item and use this query. Replace item-id with the id you have picked up. `https://graph.microsoft.com/v1.0/me/drive/items/{item-id}/children


Updates for pre-auth - multiple keys from the same account

1. Fixes https://github.com/onflow/flow-js-sdk/issues/459.
For example, in the case that user requires authorization from 2 accounts ["account1", "account2"] and account1 requires 2 keys ["account1|0", "account1|2"], authorizers are mapped from
["zxxsf8uvs7", "mf0v3p6t2c"]

->
["CURRENT_USER", "mf0v3p6t2c"]

->
[ ["0xd5f1a3954f06b231|0", "0xd5f1a3954f06b231|2"], "mf0v3p6t2c"]

->
["0xd5f1a3954f06b231|0", "0xd5f1a3954f06b231|2", "mf0v3p6t2c"]

2. Add in #455
Mutate key ID with the key ID from signature response.

@orodio Let me know if you have questions or concerns, thanks.

Makes sense, as always thanks for your effort

Will get this into a beta release


Most of the STM's have a RTC-ISR register that can be checked if the RTC is running.
A simple check in the RTC_API.c does work, I have been using it for some time now:
if(RTC->ISR == 7) {     // RTC initialization and status register (RTC_ISR), cold start (with no backup domain power) RTC reset value
Bypass the RTC initialise in this case that stops the register being reset.
I believe Martin did merge a PR from me a few weeks back for the F7 but that seems not to have happened.

@bcostm @adustm

OK I take this in charge for all STM32 series.

We think it's better to use the flag INITS instead. To check if the RTC was initialized.
Is it fine for you?

Which ever you think will the best option, using RTC->ISR is mentioned in the manual as a way to check the state of the RTC, has been working as I mentioned above.

Hello @star297 ,
Is it ok for you now ? Could we close this issue  ?
Cheers

@adustm
@0xc0170
No I'm afraid you can't.
I have loaded Mbed_dev rev: 58, it is not correct and will not work.
This part has to be changed/ included:
int rtc_isenabled(void)
{
if ((RTC->ISR & RTC_ISR_INITS) ==  RTC_ISR_INITS){
return 1;
} else {
return 0;
}
}
All the "rtc_inited" code needs to be removed, it's no longer required and has no use here.
I have this implemented on several targets L476, L152, F4xx, F746 and is working correctly.
If you prefer I will send an individual PR with the working code for each of the targets I have fully tested.
Each target that uses the same embedded peripheral RTC in the Mbed line up will need this change to work properly. Some of the other 'low end' targets do not have the RTC->ISR register so must not be changed.
Paul

@star297 please do, at least one, so we can test it


[2.0-wip] Shorter class names for table, form, label, alert, etc. options

Isn't it possible to shorten the class names that are used for table, form, label, alert, etc. options?
For example:

could be simplified to:

Which means:

Code that is easier to write
Code that is easier to read
Resulting HTML (and possibly CSS)  would be a little smaller (to save bytes here and there - for faster page load times)

Currenty a similar class name convention is used for icon options:

and it works great.
As long as related class names (like .table or .form) is scoped, everything should work fine.

Form options
Button options
Label options
Alert options

could benefit from such shorter class names as options.

See #1281, I brought this up a few days ago.

yep - duplicate: https://github.com/twitter/bootstrap/issues/1281


Add explanation on how to run this in development mode

A suggestion from badpotato in this post.

Done 0d5c646d66c05013fa5d2866b788032e232c461c


Update Puppeteer to v13

This PR updates Puppeteer to fix CVE-2022-0235.

Published as<EMAIL_ADDRESS>


[ABW-3579] Align depositors/resources icon section

Description
Align depositors/resources icon sections on tx preview screen.
How to test

Preview tx that changes both resource rule and depositor and verify icons are centered.

Screenshot

PR submission checklist

[x] I have tested account deposit settings preview

@jakub-rdx Should we be able to click on the item when it is a specific resource, or not?

@jakub-rdx Should we be able to click on the item when it is a specific resource, or not?

@micbakos-rdx To open asset details? I think at the time of development, the answer was no, and it is not clickable on iOS.


[Docs] Add doc for basic C API design choices

Closes #293. A sketch was proposed in #310. This PR extracts the markdown portion of that sketch as a document that
contributers can review to understand our C API strategy.
The markdown doc in #310 has been reworded a little, and the Opaque handles section has been expanded to list alternative schemes.

The only thought could be to remove some of the talk of alternatives

To be honest, I initially forgot that this was a "contributing" doc rather than a psuedo-DR so went and added more alternatives.
Regardless, I was reluctant to remove alternatives, since I'm not 100% certain we won't want to reconsider the alternatives as we do more C API work.
How about if we change the "Alternatives" subtitle to "Rejected alternatives" or "Other alternatives considered" or move to an "Appendix" section?
I also assume that this will be a living doc, to be updated as we do more work on the C API (e.g. ownership/memory management).

@feltech I was about to merge, as I think it's fine as is but be good to ponder Nick's update here.

Do you want to rebase and merge @feltech


Indexer incorrectly claims a user command is part of a block

Our tests assert that mainnet-220897-3NL4HLb7MQrxmAqVw8D4vEXCj2tdT8zgP9DFWGRoDxP72b4wxyUw.json contains a user command whose recipient is B62qkCALyHkUGBTvLSc35GTmF5wzYEiXGLMDA2rBMDH2AruHxgcxSjg.
This assertion is coded into our tests here: https://github.com/Granola-Team/mina-indexer/blob/bbb4872b69509871dcac28a2d62d57eb202ab7bc/rust/tests/command/store.rs#L82
log out the Vec from the assertion and you will find that the indexer_store includes an extra user command that the block does not include.

@n1tranquilla Good find. Are you working on a fix, too? Should you be assigned this issue?

not an issue on main


Update port position when state changes

Update the position when the port is first mounted (this can happen
when the port "type" is changed e.g. from "bottom" to "right").
Also update the position when the number of ports on the port's side
changes.
Both of these updates are necessary to ensure that the links between
nodes start and end in the correct positions after an update to the
chart state.

Merge please 👍

@MrBlenny I really need this too!


Fix recent issues with release 1.2.1

Revert "Allow the pages directory to be in node_modules (#318)"
This reverts commit a13c6ccb1182af32923e587a0d86f2eacac0e022.
Fixes this issue:

I assume a13c6ccb1182af32923e587a0d86f2eacac0e022 will ask babel to lookup the code inside node_modules or something similar.

Coverage remained the same at 37.259% when pulling 4d21dece745a71666e30e7b0b6a27a6fed23c2e1 on arunoda:fix-1.2.1-issue into 39ba1a0110d5ee42711da799f7b07e90e522251a on zeit:master.


How to select and install webdrivers

I'd expect the README to explain how to select which driver to use and how to get it installed.

Hi @aceofspades, I am in the process of updating the README to get ready for the v3.7.2 release. Here is the draft - https://github.com/kapoorlakshya/webdrivers/blob/release_3_7_2/README.md
Let me know if you would like to see any other information in there.

@kapoorlakshya I think my particular problem was due to the latest version of the Chrome Browser not having a corresponding version of the Chromedriver. It wasn't clear what was going on until I dug in via the console and even then I only not HTTP errors until I figured out how to turn on verbose mode. So hopefully a future version can display better errors. To me it seems safe for any downloads to be logged without requiring verbose mode.

I agree - we'll improve the logging in the future versions. For now, I have updated the README with as much user relevant information I can think of.


Query about the new --float --double --longdouble options

I had a query about the new --float --double --longdouble options in 0.4 - specifically is there a way to sub the correctly represented float values back into the result?
I've had problems in the past where the rounding error when going from some any-precision-float -> float for the higher order terms of polynomials throws out the overall ULP of the result, and in the past I've had to then manually re-encode the correctly represented float values back into the original remez run so that the next term in the polynomial is aware of the precision loss of the preceding terms.
Thanks!

I’m afraid right now LolRemez ignores the fact that truncating to e.g. float creates a suboptimal solution.
Implementing this would requires several additional full Remez runs (using the same technique as in this section of the tutorial), but it does make sense to make it automatic, yes.

Ok - thanks for the quick response! I'll just run do some scripting in a loop for now as an interim solution.


Attempt to fix issue #608,  parsing non-param args in sensible way

Attempt to fix issue #608 :
If [^a-z]units\.[a-z]+ regex is found in a value being parsed, try to parse as a Pint quantity (possibly with errors via uncertainties). If that fails, or if that string wasn't found, parse as a literal value (i.e., NOT as a Pint quantity).

Tested the PR on a stage I was developing. All seems to work as intended. :)


OnClick on Pin marker

I want to handle the onClick on the pin, how is this possible without using MotionEvent?

I'm sorry I can't provide help with this sort of question, but there are examples of drawing pins and adding custom event handling in the sample library and that should be enough to provide the answer. If not, please try asking questions on StackOverflow.


[9.x] Support --ssl-ca on schema load and dump

When using SSL with MySql php artisan migrate will fail with
In Process.php line 272:

  [Symfony\Component\Process\Exception\ProcessFailedException]
  The command "mysql  --user="${:LARAVEL_LOAD_USER}" --password="${:LARAVEL_L
  OAD_PASSWORD}" --host="${:LARAVEL_LOAD_HOST}" --port="${:LARAVEL_LOAD_PORT}
  " --database="${:LARAVEL_LOAD_DATABASE}" < "${:LARAVEL_LOAD_PATH}"" failed.

  Exit Code: 5(Unknown error)

Draft pr's aren't reviewed. Please mark as ready if you want a review, thanks.

It doesn't complain if you pass an empty string?

It doesn't complain if you pass an empty string?

not with the mysql version I am using locally ....

It doesn't complain if you pass an empty string?

It does: https://github.com/laravel/framework/issues/41300


[for discussion] izettle-java: Duplicate project for compatibility

izettle-java-compat is intended for the clients that cannot use source/target level higher than java 1.6.
The current izettle-java will roll forward source/target to java 1.8
Note: The code is just copied directly from current izettle-java as-is. Only change is the package name (to not get class conflicts in depending repositories).
Thoughts on this, @staffanjonsson @oskarwiksten and @softarn for example? Is there a cleaner way forward?

Who will use this apart from Android then?

Well, no one really. But to not drag along any java8 dependencies to android, izettle-reader-library would also have to use this one as well instead of the java8 one.

Solved in other ways. Closing.


Obtrusive logging of item_discard_skipped event

Expected Behavior
Only log item_discard_skipped after having spun a pokestop.
Actual Behavior
Obtrusive logging of item_discard_skipped.
2016-08-10 18:04:48,609 [MoveToMapPokemon] [INFO] [move_to_map_pokemon_move_towards] Moving towards Voltorb, 0.11km, left (6 minutes, 54 seconds)
2016-08-10 18:04:50,520 [RecycleItems] [INFO] [item_discard_skipped] Skipping Recycling of Items. 75 space left in bag.
2016-08-10 18:04:50,533 [MoveToMapPokemon] [INFO] [move_to_map_pokemon_move_towards] Moving towards Voltorb, 0.10km, left (6 minutes, 52 seconds)
2016-08-10 18:04:52,116 [RecycleItems] [INFO] [item_discard_skipped] Skipping Recycling of Items. 75 space left in bag.
2016-08-10 18:04:52,128 [MoveToMapPokemon] [INFO] [move_to_map_pokemon_move_towards] Moving towards Voltorb, 0.10km, left (6 minutes, 50 seconds)
2016-08-10 18:04:53,853 [RecycleItems] [INFO] [item_discard_skipped] Skipping Recycling of Items. 75 space left in bag.
2016-08-10 18:04:53,865 [MoveToMapPokemon] [INFO] [move_to_map_pokemon_move_towards] Moving towards Voltorb, 0.09km, left (6 minutes, 49 seconds)
2016-08-10 18:04:55,390 [RecycleItems] [INFO] [item_discard_skipped] Skipping Recycling of Items. 75 space left in bag.
2016-08-10 18:04:55,401 [MoveToMapPokemon] [INFO] [move_to_map_pokemon_move_towards] Moving towards Voltorb, 0.08km, left (6 minutes, 47 seconds)
2016-08-10 18:04:56,949 [RecycleItems] [INFO] [item_discard_skipped] Skipping Recycling of Items. 75 space left in bag.
2016-08-10 18:04:56,961 [MoveToMapPokemon] [INFO] [move_to_map_pokemon_move_towards] Moving towards Voltorb, 0.07km, left (6 minutes, 46 seconds)
2016-08-10 18:04:58,749 [RecycleItems] [INFO] [item_discard_skipped] Skipping Recycling of Items. 75 space left in bag.
2016-08-10 18:04:58,761 [MoveToMapPokemon] [INFO] [move_to_map_pokemon_move_towards] Moving towards Voltorb, 0.07km, left (6 minutes, 44 seconds)
2016-08-10 18:05:00,530 [RecycleItems] [INFO] [item_discard_skipped] Skipping Recycling of Items. 75 space left in bag.
2016-08-10 18:05:00,636 [MoveToMapPokemon] [INFO] [move_to_map_pokemon_move_towards] Moving towards Voltorb, 0.06km, left (6 minutes, 42 seconds)
2016-08-10 18:05:02,292 [RecycleItems] [INFO] [item_discard_skipped] Skipping Recycling of Items. 75 space left in bag.

Steps to Reproduce
Run the bot.
Other Information
Maybe use formatted only after a spin for item_discard_spinning event?
Git Commit: 63f777bac0c8cdc75d07f9ef491ca8b900c0148a

#3279


Status Code 2 return

I tried using your lint on my Proto3 file however it failed.   Not sure what the issue could be
C:\main\dlmu\cadaemon-0339.1\include\cagrpc>protoc --lint_out=. CAService.proto
--lint_out: protoc-gen-lint: Plugin failed with status code 2.
I am using the latest x64 protoc using the master branch.  My protoc files are used for gRPC. It would be really useful if there was some descriptive text indicating what Status code 2 means

Are you able to post your .proto file?

I think there is a problem with the binary, firstly it has no extension for
the win32 executable.  After renaming it I received the following popup -
also not sure but I think I may be forced to specify the '-I .' in order
for the default usage to find the proto files
I'll try again as soon as you have a newer version
John
[image: Inline image 1]
On Sun, Apr 24, 2016 at 4:22 PM, Clifton Kaznocha<EMAIL_ADDRESS>wrote:

Closed #2 https://github.com/ckaznocha/protoc-gen-lint/issues/2 via
10e721b
https://github.com/ckaznocha/protoc-gen-lint/commit/10e721be48e6e1143c3246ac78df391024631050
.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/ckaznocha/protoc-gen-lint/issues/2#event-639178469

Something went wrong with the travis cross compilation. I've just manually regenerated the binaries. Let me know if you still have an issue getting it to run.

Thanks for the update, I'm not sure how to tell if the linter plugin is
working, if I run it against my proto file I get nothing out, either it
only complains when things are not valid or its doing nothing?  Also my
antivirus flagged it - but I guess thats because its a new executable.
John
On Sun, Apr 24, 2016 at 7:43 PM, Clifton Kaznocha<EMAIL_ADDRESS>wrote:

Something went wrong with the travis cross compilation. I've just manually
regenerated the binaries. Let me know if you still have an issue getting it
to run.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/ckaznocha/protoc-gen-lint/issues/2#issuecomment-214067066

An exit code of 0 and no output means it found are no issues with your file. If the linter isn't working protoc should give you some error.

BTW just to try to violate the google protoc style guide, I changed one of
my message names to have a lower case and the linter flagged nothing., I'm
not sure if the executable is doing anything.  It is in my path.  Hopefully
its not a virus :)
i.e.
// individual fault state
message FaultValue {
oneof oneof_type {
string name = 1;
int32 index = 2;
}
bool value = 3;}
was changed to
// individual fault state
message faultValue {
oneof oneof_type {
string name = 1;
int32 index = 2;
}
bool value = 3;}
On Sun, Apr 24, 2016 at 7:43 PM, Clifton Kaznocha<EMAIL_ADDRESS>wrote:

Something went wrong with the travis cross compilation. I've just manually
regenerated the binaries. Let me know if you still have an issue getting it
to run.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/ckaznocha/protoc-gen-lint/issues/2#issuecomment-214067066

Clifton, I tried the test.proto and successfully got 15 errors - I made the
similar violations in my proto file (the one I sent you on friday) however
the linter fails to perform any linting on the proto file.  Try changing
the camel case of any of my messages or enums, you will see no lint
warnings. I'm guessing the imports are confusing the linter.
John
On Sun, Apr 24, 2016 at 10:45 PM, Clifton Kaznocha<EMAIL_ADDRESS>
wrote:

An exit code of 0 and no output means it found are no issues with your
file. If the linter isn't working protoc should give you some error.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/ckaznocha/protoc-gen-lint/issues/2#issuecomment-214099357

Confirmed your findings, I've just push the fix and will make the release now. Thanks for bearing with me!

OK, the new release is here: v0.1.2
Everything should work for you, please let me know it it doesn't.

No thank you
All the best and thanks for the linter!
John
On Mon, Apr 25, 2016 at 12:00 AM, Clifton Kaznocha<EMAIL_ADDRESS>
wrote:

Confirmed your findings, I've just push the fix and will make the release
now. Thanks for bearing with me!
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/ckaznocha/protoc-gen-lint/issues/2#issuecomment-214119159

Clifton,
Thanks that works great!  Nice work
John
On Mon, Apr 25, 2016 at 12:10 AM, Clifton Kaznocha<EMAIL_ADDRESS>
wrote:

OK, the new release is here: v0.1.2
https://github.com/ckaznocha/protoc-gen-lint/releases/tag/v0.1.2
Everything should work for you, please let me know it it doesn't.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/ckaznocha/protoc-gen-lint/issues/2#issuecomment-214120644


Working version following testing & feedback with Ops Eng team.

A reference to the issue / Description of it
This PR is the result of the work undertaken for issue https://github.com/ministryofjustice/modernisation-platform/issues/7047
How does this PR fix the problem?
It adds the following resources:
A github workflow that runs on the first day of each month and which triggers:
i. A script that gets a json list of environments to check based on the first commit date of the environments/.json file.
ii. A second script that generates a github issue for the review of the owner details and which calls a python script that sends an email to the owner via Gov.UK Notify.
A Gov.UK Notify email template that accepts the following parameters from the above script - the environment name, the owner's email address and the URL of the github issue.
How has this been tested?
Please describe the tests that you ran and provide instructions to reproduce.
These resources were tested as follows:
Generating issue & email for sprinkler only
With @connormaglynn & the operations-engineering environment.
Deployment Plan / Instructions
Will this deployment impact the platform and / or services on it?
The workflow & scripts will deploy on merge of this PR. The Gov.UK Notify template was created manually and is not managed in code.
Updates to the userguide and workflow lists will be done once the changes have been merged.
Checklist (check x in [ ] of list items)

[x] I have performed a self-review of my own code
[x] All checks have passed
[ ] I have made corresponding changes to the documentation
[ ] Plan and discussed how it should be deployed to PROD (If needed)

Additional comments (if any)
{Please write here}

Here are a few comments:

When you check out the repository, there’s no need to specify the ref tag, it will default to the main branch.
Instead of declaring the environment variables for each step individually, you can declare them globally.
There's no need to change directories or give execute permissions to the script, as the runner will already be in the checked-out repository by default.


[msbuild]DLLs aren't copied to output folder for MSIX packaged app

Describe the bug
When using vcpkg with msbuild, DLLs are copied to only the project output folder but not the MSIX packaging project output folder.
Environment

OS: Windows
Compiler: revision

To Reproduce
Steps to reproduce the behavior:

Create a sample console application project in visual studio and use any package that produces DLL for the application.
Create a MSIX packaging project and add the previous console app as reference to "Applications" node.
Deploy the MSIX packaged app and run the app.
See the error.

Expected behavior
DLLs should be copied to MSIX package like before (recent changes are causing this behavior).
Failure logs

Error when using "fmt"
Additional context
This is probably happening due to recent changes in vcpkg as it didn't happen before.

Duplicated to https://github.com/microsoft/vcpkg/issues/16184


SPORK_8 doesn't do what it should do

So prior to <IP_ADDRESS> we had
"SPORK_8_MASTERNODE_PAYMENT_ENFORCEMENT": true,
I disabled it in <IP_ADDRESS> because:
If an incorrect  blocks get generated without the masternode payment enforcement in place, the network SHOULD reject these and orphan, them, but it doesn't.
What actually seems to happen is that the voting MNs self partition off with an invalid chain.  The correctly reject the block as per
https://github.com/MattF42/PePe-core/blob/6decb6e1879ffa939a421ac15e5cc9b3de1f3685/src/masternode-payments.cpp#L202-L205
But then spiral off into a death spiral of InvalidChainFound,  Invalid masternode payment detected and fairly quickly stop syncing.
I think this happens because only the voting MNs participate in in the IsTransactionValid() / IsBlockPayeeValid() checks, but honestly I'm rather out of my depth here.....
So, we shouldn't get MNs sulking and stopping getting paid (hurrah) - but we CAN have invalid blocks (with not MN reward) which the network will not correctly reject :(
Can someone please take a look and work out how we can re-enable SPORK8 without causing MN breakage?
Block 483396 was an example of such a block:
~/bin/PEPEPOW-cli getrawtransaction a133ae7f74523db8cd389196f8eb6480990a233eff694b96b44cf7db5fedb6f7 1
{
"hex": "02000000010000000000000000000000000000000000000000000000000000000000000000ffffffff1f0344600704b896ff64088100d3b9030304027a657267706f6f6c2e636f6d00000000000100a89c13460200001976a9140ddc16715823d16442abc7bf0538c2cd46ea2c1988ac00000000",
"txid": "a133ae7f74523db8cd389196f8eb6480990a233eff694b96b44cf7db5fedb6f7",
"size": 116,
"version": 2,
"locktime": 0,
"vin": [
{
"coinbase": "0344600704b896ff64088100d3b9030304027a657267706f6f6c2e636f6d00",
"sequence": 0
}
],
"vout": [
{
"value": 25000.00000000,
"valueSat":<PHONE_NUMBER>000,
"n": 0,
"scriptPubKey": {
"asm": "OP_DUP OP_HASH160 0ddc16715823d16442abc7bf0538c2cd46ea2c19 OP_EQUALVERIFY OP_CHECKSIG",
"hex": "76a9140ddc16715823d16442abc7bf0538c2cd46ea2c1988ac",
"reqSigs": 1,
"type": "pubkeyhash",
"addresses": [
"P9rTbRfgkXLmvquRHRKY5Nq7ewA1bFoUZv"
]
}
}
],
"blockhash": "00000000001ccca9511293f1cd73be38089b36b6e6b5a74c9a8709e92d220559",
"height": 483396,
"confirmations": 36166,
"time":<PHONE_NUMBER>,
"blocktime":<PHONE_NUMBER>
}

Hopefully this is fixed by c6366d58f60aa0ac4ab9efd8d694079263be4e43 leaving open until confirmed


add auth.moduleaccounts to the stargate whitelist

Closes: #6585
What is the purpose of the change
this PR will enable smart contracts to fetch osmosis's module accounts.
Testing and Verifying
This change is a trivial rework / code cleanup without any test coverage.

that said, let us know if this code change is not considered trivial *

Documentation and Release Note

[ ] Does this pull request introduce a new feature or user-facing behavior changes?
[ ] Changelog entry added to Unreleased section of CHANGELOG.md?

Where is the change documented?

[ ] Specification (x/{module}/README.md)
[ ] Osmosis documentation site
[ ] Code comments?
[ x] N/A

devbot help

Hi! I'm DevBot, a bot that helps with common tasks in the development process. Commands:

devbot fix: Fix basic errors in the PR. (e.g. imports, changelog conflicts, go mod conflicts)
devbot merge base: Merge the base branch into the PR branch.
devbot add changelog [misc/feat/bug/api/sec] [message]: Add a changelog entry to the PR. (e.g. devbot add changelog feat Added a new feature)

If message is blank, defaults to PR title.

devbot re-pr: Re-PR the PR, useful for external contributors where we have no edit perms.

devbot add changelog misc add (x/auth) ModuleAccounts query to stargate whitelist

devbot add changelog misc add x/auth: ModuleAccounts query to stargate whitelist

@ibjc Would you be able to add a changelog for this? Thanks!

@ibjc Would you be able to add a changelog for this? Thanks!

oh sure thing, will do


Add opening settings after geolocation start

Description:
Resolved #772.
How to test:

Set "Never" for location tracking in the app settings;
Open the app;
Go to the dashboard;
Click to "Location Inactive";
Should be redirect to the app settings;

Closing due to inactivity


operators [N] [CI] nfs-provisioner-operator (0.0.2)

Signed-off-by: Jooho Lee<EMAIL_ADDRESS>New Submissions

[V] Are you familiar with our contribution guidelines?
[V] Have you packaged and deployed your Operator for Operator Framework?

[V] Is your submission signed?
[V] Is operator icon set?

Updates to existing Operators

[] Did you create a ci.yaml file according to the update instructions?
[] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[V] Modify more than one operator
[V] Modify an Operator you don't own
[V] Rename an operator - please remove and add with a different name instead
[V] Modify any files outside the above mentioned folders
[V] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[V] Description about the managed Application and where to find more information
[V] Features and capabilities of your Operator and how to use it
[V] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[V] Human readable name and 1-liner description about your Operator
[V] Valid category name1
[V] One of the pre-defined capability levels2
[V] Links to the maintainer, source code and documentation
[V] Example templates for all Custom Resource Definitions intended to be used
[V] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/test 4.6-deploy-operator-on-openshift

@mvalarh I commited 2778705 without signoff so I tried to recommit it with sign but still DCO failed. Could you guide me how to fix this ?

/test 4.7-deploy-operator-on-openshift

/merge possible


Raise percentage of mutation score indicator

Q
A

Is bugfix?
❌

New feature?
❌

Breaks BC?
❌

Fixed issues
-

👍


Categorise high level layers for display

There are currently a concrete number of subclasses of the base highlevelgraph.Layer. Some of these have specific contexts or collection linkage (array Vs dataframe), others do not. For the sake of the work being done by @freyam , it would be nice to create some categories for the purpose of being shown in .visualize().
Layers allow for attaching attributes at instantiation. I suggests there might also be class attributes giving information about the layer type, which will be true for all instances.
Example: DataFrameIOLayer is IO by operation type and dataframe by collection.  It would be reasonable for these to be among the default annotations of all instances.

cc @GenevieveBuckley

This is amazing! I will get started on finding more about this and share my findings here! :rocket:

I suggest starting with a concrete list of the current known implementations of Layer.

List of Layers
class Layer(collections.abc.Mapping)
High level graph layer
class MaterializedLayer(Layer)
Fully materialized layer of Layer
class Blockwise(Layer)
Tensor Operation
Array Layers
class BlockwiseCreateArray(Blockwise)
Specialized Blockwise Layer for array creation routines
class ArrayOverlapLayer(Layer)
Simple HighLevelGraph array overlap layer
Dataframe Layers
class DataFrameLayer(Layer)
DataFrame-based HighLevelGraph Layer
class SimpleShuffleLayer(DataFrameLayer)
High-level graph layer for a simple shuffle operation in which each output partition depends on all input partitions
class ShuffleLayer(SimpleShuffleLayer)
High-level graph layer corresponding to a single stage of a multi-stage inter-partition shuffle operation.
class BroadcastJoinLayer(DataFrameLayer)
High-level graph layer for a join operation requiring the smaller collection to be broadcasted to every partition of the larger collection.
class DataFrameIOLayer(Blockwise, DataFrameLayer)
DataFrame-based Blockwise Layer with IO

Copying over my comment from the Slack thread earlier today:

I think figuring out what categories should be included will be the tricky thing, and trying to make those categories be something users will care about. It seems like it'd be more useful if we can use them to highlight bottlenecks. I assume that's why you suggest IO and shuffle. We seem a bit vague on things beyond that though, I don't know that "all other CPU computations" is likely to be very useful to display (and will probably be most cases)

So I think I'm more advocating that the Layer classes have some default annotations - and that's all. That way, we only need to look at these annotations, we don't need to do any isinstance checks. Of course, we still might want to look into the layer contents, to make the difference between GPU/CPU.
Totally agree that "CPU" should not have any associated decoration, as it will be the default, most common box.

@martindurant
What would the default annotations be for all the layers? I can think of layer_id.
Meanwhile, I have come up with the visualization for the HLGs!
Design
Group the listed layer_types into 4 categories
IO (DataFrame)

DataFrameIOLayer

Shuffle (DataFrame)

SimpleShuffleLayer
ShuffleLayer

Blockwise (Array mostly + DataFrame)

Blockwise
BlockwiseCreateArray

Materialized (Array  + DataFrame)

MaterializedLayer

The remaining layers:

ArrayOverlapLayer
DataFrameLayer
BroadcastJoinLayer
can be just left as it is.

Visualization
Graphviz (Layer.dask.visualize())
We can show the different groups with different colors.

HTML Repr (Layer.dask)
Using the same colors used in the Graphviz, we change the tiny circles next to each layer to reflect its layer_type.

(I have also modified the MaterializedLayer's existing color to be a little lighter. I feel it looks nicer and easier on the eyes)
It might seem too colorful, but that's because I am showing all the different types of layers at the same time. This is highly unlikely to been observed in real Dask Graphs.
/cc @jacobtomlinson I would love to hear your opinion as well on the colors. You have done an amazing job adding all the existing colors :sparkles:

What would the default annotations be for all the layers

Empty? If we can't think of anything useful, it's better not to complicate the visuals.

/cc @mrocklin What do you think about the use of colors?
(colors are open for discussion)

I hadn't thought of changing the colours in the dots next to the layer titles in the HTML representation, that's a nice touch.
Personally, I'm not sure we're gaining much by having multiple shades of green/blue/etc. for different types of layers in the same larger category. I think that adds more confusion.
We'll need some effort spent on:

Explaining what information the user should gain from this (eg: shuffles are inefficient so you don't want to see too many of them, blockwise layers are likely to be nicely parallelized, etc.). You'll need to be able to explain this very clearly for all of them.
How we are going to communicate that information to the user (a legend for graphviz? added information in the docs? something in the HTML repr?)

Personally, I'm not sure we're gaining much by having multiple shades of green/blue/etc. for different types of layers in the same larger category. I think that adds more confusion.

 This looks even cleaner :sparkles:
I have also added a Legend below so users have a good idea of what the colors mean.

and

Note: The colors used in Layer 2, 5, and 6 are supposed to be Green (Blockwise) as well, but I have used different ones to show all of the colors

Explaining what information the user should gain from this (eg: shuffles are inefficient so you don't want to see too many of them, blockwise layers are likely to be nicely parallelized, etc.). You'll need to be able to explain this very clearly for all of them.

I'm unfamiliar with this section of the code. So I'm not sure which layers are more difficult for users and which are simple (quick?).
If I have more context about the different layers and what makes them slower than the rest, I can perhaps do something more with those layers' nodes.
For example, I can add a little node form note to all of the Shuffle and DataFrameIO layers. This could imply that this is an area worth investigating.

How does this sound?

For example, I can add a little node form note to all of the Shuffle and DataFrameIO layers.

I'm sorry, what does this mean?

I think it means that the outline box is not just a rectangle, but has a little fold in the corner. Pretty subtle.
On July 26, 2021 10:28:04 PM EDT, Genevieve Buckley @.***> wrote:

For example, I can add a little node form note to all of the
Shuffle and DataFrameIO layers.

I'm sorry, what does this mean?
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/dask/dask/issues/7919#issuecomment-887159227

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

@GenevieveBuckley Yes, Martin is correct.
So, in essence, the current node shape is "box." Another node shape is "note," which resembles a paper fold from the corner.
Normally, people fold a page to bookmark it so that it can be easily found later. In this case, the fold would indicate that this area warrants further investigation.

/cc @jacobtomlinson I would love to hear your opinion as well on the colors. You have done an amazing job adding all the existing colors ✨

Thanks @freyam but all the colour design was done by an external designer. See dask/community#135. I've added another comment to that issue to see if we can get the designer involved in choosing the more colours.

I've added another comment to that issue to see if we can get the designer involved in choosing the more colours.

That's amazing! :rocket:

So, in essence, the current node shape is "box." Another node shape is "note," which resembles a paper fold from the corner.

I think that the difference is too subtle to see in your examples, and the meaning of the different shapes will not be obvious to users.

Just wanna confirm:
Shuffle and DataFrameIO layers are the 2 specific layers you want to highlight differently to point at the potential source of inefficiency?

I have opened a Draft PR where I will be working along with this discussion.
#7974


About the data format.

Could you provide some short example data for reasoning, or provide more detailed infomation about the format of the input data?
Thanks.

Sorry for the late reply. I noticed you have applied the dataset and the download link is sent to you. You can find specific data formats in that.


gnss-sdr: 0.0.9 -> 0.0.10 (wip)

Motivation for this change
https://gnss-sdr.org/gnss-sdr-v0010-released/
Things done

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

[x] NixOS

rebuilding again to be sure, FWIW

[ ] macOS
[ ] other Linux distributions

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

Whoops, guess i put this in the wrong stack of commits haha.  Even with these deps, fails late in build--probably not hard to fix, but not ready yet sorry!


CFPB color palette overhaul

Overhauled color palette in CFPB's brand-palette.less variables file.
:warning: WARNING: This is a breaking change for CFPB projects that use this file. Please heed the instructions given at the bottom of the file for updating your project's color variables when implementing the updated palette.
Review:

@jimmynotjim
@designlanguage

@Scotchester - The values look good, thanks!

Small comment but :+1:

Updated! Mergin' time.


[10.x] Make canCreate at QueryDataTable accept QueryBuilder only

canCreate function at QueryDataTable should accept QueryBuilder only but it accepts EloquentBuilder  aslo because EloquentBuilder contract extends QueryBuilder

Released on https://github.com/yajra/laravel-datatables/releases/tag/v10.0.8 Thanks!


Change variable names to make code clearer and more understandable

https://github.com/debrayc/genereight/pull/7/commits/e50949d85bf83beca7b9ce77b74e4d159a08fd34


HOW DO I FIX THIS??

Describe your problem here.

Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
no

change the song's bpm

change the song's bpm

WORSE than before

WORSE than before

if you've decreased the bpm, increase it, and viceversa, until it seems editable

WORSE than before

if you've decreased the bpm, increase it, or viceversa, until it seems editable

By some reason, it stills happends the same
By the other hand, it's the only chart that looks like that (uneditable), it might be 'cause it's from one of the first psych engine updates charts.

Clear section.


[FEATURE] Add type definitions

I use typescript for my projects and it would be really great if there is a type definitions defined directly in the project.
It would make much better development experience as it would reduce the amount of going back and forth looking at the documentation if the descriptions and types were to show up in the IDE.

Added by #166

Hi @dpa99c @dakotaJang, actually I inserted a
declare const FirebasePlugin: FirebasePlugin;
at top of my Angular Service, but I have the following error:
'FirebasePlugin' refers to a value, but is being used as a type here.
How can I use the types in may Ionic project?
Thanks,
--Luca


Time picker feature

Love the library!
We have started transitioning all our implementations of date pickers to use this library. However, we have a few places where we also need to be able to change the time of day, together with choosing a specific date. See screenshot for our current implementation with our old custom date-picker:

Is this something you could consider implementing? Or is it out of scope for this library?

Maybe I could implement it.  Do you have any suggestions about what the design would look like?

Initially I was picturing something like this, where you just type in the time manually (or with a stepper or similar):

However, I'm not sure if that's the best for mobile devices for instance. Perhaps clicking the time should open some kind of popup/dropdown, where it's easier to choose a time, even on mobile devices? Like the Material UI time picker: https://material-ui.com/components/pickers/#material-ui-pickers

That's really amazing idea , really amazing :)!!!

+1 @tobiasf

Is this in the pipeline already?

Is this in the pipeline already?


Update

@Nitin-2001
Most you have fixed are code style. For example, we prefer separate the import section such as 3rd party, internal, public by empty line.
https://github.com/kakao/buffalo/pull/32/commits/27e717d0debf261fc643a29f9bf1df8175d31c2f#diff-f67ab7e3398f27879fd773eb052f6ebdeee2d95d5aeb422ccf8a30161776fe67L4


Wiki Pages

As ML and AI algorithms are being included in this repository, I think it is better to have our own Wiki for this repository. Also, @aashutoshrathi has suggested about an extra application field, we could add application of algorithms there. What are your views @aviaryan @singhpratyush @Monal5031 @yashLadha ?

Since the algorithms implemented are not industry standard, they will not be used by anyone. They are present here just to test the proof of concept. I think that just the comments in the implementation will do the job.

@Prakash2403 yes it seems a good idea to have that but in a little different way according to me.
We can create our own questions and add it there along with the dependent algorithm.
We can also use it for uploading questions for any future contests in our college and uploading answers there only along with used algo/DS.

@singhpratyush There are multiple things which are too big to be explained in comments. For example, Average case time complexity of quick sort is O(nlogn). Proof using probability requires a wiki page. Similarly, when A* search algorithm will be added, then heuristic function and conditions required (admissibility and consistency) will require a wiki page.
Although, these things can found on Internet, but it will be nice if we just give a brief summary here.
@Monal5031 Nice idea. But I think we should make a different repository dedicated to it.
What are your views @singhpratyush @aviaryan @yashLadha @aashutoshrathi @harishkrupo ?

@Prakash2403: That is true. But this repository is to show the implementations. Things like consistency check, proof of complexity, etc. can be referenced from other destinations on the Internet.
But if the contributor really wants to give his words on the implementation, he may add a README.md in docs/ directory of the repository.
@aashutoshrathi @aviaryan @Monal5031: What do you guys think of this?

@singhpratyush Yes sir it seems a nice idea, with the new contributors joining in it'd be good if that person explains their implementation if they did in a different manner. With the explanation being available on the algo/DS this repo would be more useful for people who are trying to learn new concepts.
Also sir we can use github pages to publish the explanations, like the main page could list all the algo/DS which has the explanations and others with the actual explanation. Views? @aviaryan @Prakash2403 @yashLadha @aashutoshrathi @mohitkyadav

I agree. But if we are going to do this, we must do it asap, as this repository is growing bigger day by day.


fix: merge duplicate chunks

What kind of change does this PR introduce?
fixes https://github.com/webpack/webpack/issues/18898
Did you add tests for your changes?
WIP
Does this PR introduce a breaking change?
No
What needs to be documented once your changes are merged?
Now we export the plugin MergeDuplicateChunksPlugin, so developers can now use it with any stage and merge chunks after https://webpack.js.org/plugins/split-chunks-plugin/.
There is only one option - stage.

@SkReD It seems there is no ideal behavior for everyone, so I want to return the original logic, and give the ability to specify the stage, and if the developer wants he can apply the plugin twice

@SkReD It seems there is no perfect solution to this problem, some want to do it only before the splitting, some even after, so I decided to return the previous behavior (I got a little more reports personally), and export the plugin, so if someone needs it, he can run it with another stage


av pr create fails if the parent branch is merged and not synced

It's better to detect this and explain that rather than saying "Head sha can't be blank, Base sha can't be blank, No commits between buildkite_pipeline_config_api and buildkite_api_token, Base ref must be a branch"

I have a question about this issue.
Do you suggest handling the error messages from the API (GraphQL Error message) in more detail? Or do you have any other ideas?

Let's first try checking if the parent is merged by checking MergeCommit in the branch metadata.


Init and constructor block not highlighted

They are not highlighted at all, i can send you a pr with a fix if you want to

He’s Dead Jim, class and lateinit aren't either.

data class .
the word 'data' is highlighted but class is not.
This syntax highlighting very POOR and could make your code even more confusing.


React

Can somebody help me implement this in react?

Smartcrop is library for finding crops of images. React is a library for building user interfaces.
I'm really not sure what you mean by "implementing" a library for finding crops for images "in" a library for building user interfaces.
What exactly are you trying to accomplish?

I'm trying to let my users upload a image with react dropzone and then crop
it. The problem is react has a virtual dom so I can't get you the image
element (or not without hacking react), what I can get though is the actual
file data in base 64.
On Fri, 03 Nov 2017, 00:42 Jonas Wagner<EMAIL_ADDRESS>wrote:

Smartcrop is library for finding crops of images. React is a library for
building user interfaces.
I'm really not sure what you mean by "implementing" a library for finding
crops for images "in" a library for building user interfaces.
What exactly are you trying to accomplish?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jwagner/smartcrop.js/issues/64#issuecomment-341579647,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABwqZQ9dSrDFGkn6d2sjdJ15JrKvdpuOks5sykVsgaJpZM4P6-nM
.

You should be able to access an image element in your virtual dom via a [ref](https://reactjs.org/docs/refs-and-the-dom.html], without any nasty hacks.

Yes I can access it, but it doesn't exist as it's a file that is uploaded.
So I'd need to now go and display it (without crop) for a few milliseconds
and then access it in ref and crop it, which results in a flashing effect.
If smart crop could read the base64 image instead of a element, I could
crop it before I display it
On Sat, 04 Nov 2017, 16:46 Jonas Wagner<EMAIL_ADDRESS>wrote:

You should be able to access an image element in your virtual dom via a
[ref](https://reactjs.org/docs/refs-and-the-dom.html], without any nasty
hacks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jwagner/smartcrop.js/issues/64#issuecomment-341902219,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABwqZb5-dIHnENPqXAY0HsBwAwNsRoPSks5szHjQgaJpZM4P6-nM
.

Just set visibility to hidden (or display: none) until you have all the information you need to display it properly?


Entity Framework Core

Install the package

@feliperamoss could you do me the favor and review the PR for that. Thx :)


discrepancy searches (exclude ebsco)

Differences in volumes between results app in prod and app in dev.
searchterm <- "gluten AND intolerance"

is this one done? I have tested against old tool without ebsco

I think they are not really comparable anymore anyway cause I fixed a couple errors and filters and dates on the other ones. What was the result of the test?

I ran them at the stage that everything had been refactored and it was all good - will do again now to capture changes

Oh yes now I remember the results you sent. My apologies.


Port from C# to ghūl

Re-implemented in ghūl
Renamed main pipe class from Pipe`1 to Pipe
Moved the Pipe class into a new Ghul.Pipes namespace

Notes:

Will require an update to the ghūl compiler to reference the new Ghul.Pipes.Pipe type before the | operator can be used with this version. (And actually, I'll probably take the opportunity to roll this functionality into the main ghūl runtime library package)

Bumps #major version

Closing and moving to ghul-runtime, to avoid having to bootstrap over two changes at once.


v1.23.0

Fixed

"Above the Rain" releases all resources when stopped

Changed

Update Patron list

Added

New piece: "Beneath Waves"

Verified on stanging


Authentication

Created simple registration form and firebase registration function

Added login screen for existing users, along with ability to switch between login/register

Added logged in user stream builder to main.dart to redirect to home page when login/registration is complete. Temporary log out button on home screen.


Drop support for Tracker

Some things to remove

[ ] https://github.com/TuringLang/docs/issues/521
[ ] Any other reference to Tracker in the docs
[x] export of AutoTracker.
[x] some tests still cover Tracker. Could leave them though if they are fast and harmless, maybe leave comments saying that if they ever need fixing, they should rather be deleted.
[ ] something else? Please add.

Replacing Tracker with Mooncake in docs is blocked, because that depends on Turing 0.35, and it's not possible right now to get a fully compiling Julia environment for the docs. (essentially, we need to bump DPPL and Turing to run with<EMAIL_ADDRESS>https://github.com/TuringLang/docs/issues/541
That said, I think the remaining issues are to do with docs, rather than the Turing library. Besides, I've already been keeping track of these on the issue above. So I think it's safe to close this in favour of the docs issue.


[ISSUE #9064]Optimize the way to determine whether RMQ_SYS_TRANS-HALFTOPIC is in RMQ_SSYS_TRANS-OP_ALF_TOPIC in transaction messages

Which Issue(s) This PR Fixes
fixes #9064
Brief Description
事务消息， 回查判断RMQ_SYS_TRANS_HALF_TOPIC消息是否在RMQ_SYS_TRANS_OP_HALF_TOPIC 中，优化判断方式。之前代码是先判断Map.containsKey，然后进行removeKey，新的方式是直接removeKey ！= null。之前如果Map.containsKey为真，还需要进行额外的一步removeKey操作，新的方式removeKey！= null，即判断了Map是否存在key，又移出了对应的key，提升了一点点性能。

Transactional messages: The process involves checking whether messages in RMQ_SYS_TRANS_HALF_TOPIC exist in RMQ_SYS_TRANS_OP_HALF_TOPIC, with an optimized approach for verification. Previously, the code first used Map.containsKey to check existence and then performed removeKey. The new approach directly uses removeKey != null.
In the previous method, if Map.containsKey returned true, an additional removeKey operation was required. In contrast, the new approach both checks if the key exists in the Map and removes the corresponding key in one step, offering a slight performance improvement.
How Did You Test This Change?
经过多轮测试，在Map.containsKey 为true为false概率各为50%的情况，第二种方案明显优于第一种方案。而实际生产环境中，事务回查状态为Unknown的场景应该小于50%，在高并发大数据量场景下，个人认为这个小改动对性能还是有一些提升。
After multiple rounds of testing, when the probabilities of Map.containsKey being true or false are both 50%, the second approach consistently outperforms the first. In actual production environments, the probability of transactional checks being in an “Unknown” state should be less than 50%. Therefore, I believe this small adjustment provides a minor but meaningful performance improvement.

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

Project coverage is 47.85%. Comparing base (93e2689) to head (f13c93e).
Report is 1 commits behind head on develop.

Files with missing lines
Patch %
Lines

...saction/queue/TransactionalMessageServiceImpl.java
0.00%
1 Missing and 1 partial :warning:

Additional details and impacted files
@@              Coverage Diff              @@
##             develop    #9062      +/-   ##
=============================================
- Coverage      47.97%   47.85%   -0.13%
+ Complexity     11904    11869      -35
=============================================
  Files           1312     1312
  Lines          91735    91733       -2
  Branches       11751    11751
=============================================
- Hits           44014    43898     -116
- Misses         42312    42414     +102
- Partials        5409     5421      +12

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


Add support for duplicating a deployed stack

Portainer recently added support for a stack migration, which moves a stack from one cluster to another; but we should also have a stack duplicate function, which is where a copy of the stack is deployed on another (user selected) cluster, but leaving the current stack running. This is a nice way to ensure consistency across endpoints/clusters.

I was thinking of how to implement this, and I think the right approach is this:
With the migration button there will also be a duplication button:

Clicking on it will create a new stack with the same config as the current stack in the new endpoint.
Should we allow to create the new stack on the same endpoint? Is that even possible?

Can, but must have a new name... in fact any duplicate function must force a new name.
Rgds,
Neil Cresswell
On 14/09/2018, at 2:30 AM, Chaim Lev-Ari <notifications<EMAIL_ADDRESS>wrote:
I was thinking of how to implement this, and I think the right approach is this:
With the migration button there will also be a duplication button:
[ui]https://urldefense.proofpoint.com/v2/url?u=https-3A__user-2Dimages.githubusercontent.com_1381655_45494717-2D5a14b600-2Db77a-2D11e8-2D9168-2D451ca1fe4baf.png&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=HkfKwn7qnGtycq-Z-WIE-yUd4By4j-XH5yXZxh5w6Pg&s=knsTbhBKlL3Wg7DopgZ8pQwZAkJsMkBWYg0A0F8olq4&e=
Clicking on it will create a new stack with the same config as the current stack in the new endpoint.
Should we allow to create the new stack on the same endpoint? Is that even possible?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_portainer_portainer_issues_2234-23issuecomment-2D421027727&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=HkfKwn7qnGtycq-Z-WIE-yUd4By4j-XH5yXZxh5w6Pg&s=UpclOpb9rdAvQEM6_ux9e8UaEV0K0uT2hqTu6wsCiSo&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_AWGrlbjVLJF-2DPplsOTWj6xREwKmbMpLgks5uamwZgaJpZM4WXAIc&d=DwMFaQ&c=euGZstcaTDllvimEN8b7jXrwqOf-v5A_CdpgnVfiiMM&r=0fx0h4vB56iTLpw2McH1ZD6TqG_QGpbggVOB-PfMJpM&m=HkfKwn7qnGtycq-Z-WIE-yUd4By4j-XH5yXZxh5w6Pg&s=93_PkfaXPYYAcSs9HRYi3OshDNAe3xnxMi1JeUCGN58&e=.


Calculator for set operations

Fixed #32
As per the question I made four functions of Union , Intersection , Complement , Difference of the sets. I used the "useState" hook of ReactJs to set the state of the application after implementing the specific function as per the demand of the user.
REMEMBER: Digits entered in the sets should be separated by the "commas" (the same has been mentioned as the placeholder also)
Screenshots(Attach 2 screenshots of your own input and output) -

By raising this PR I affirm that -

[x] My code follows the guidelines of this project.

[x] I have performed a self-review of my own code.

[x] I have commented my code.

[x] My code gives the correct output.

[x] I affirm that I strictly follow contributing guidelines and code of conduct.

Congratulations 🎉 @Satvik-Garg on your contribution.

Hey 👋, may you also encourage us by clicking the star icon on the repository main page. ⭐