modify document

Signed-off-by: chentanjun<EMAIL_ADDRESS>Ⅰ. Describe what this PR did
modify document
Ⅱ. Does this pull request fix one issue?
None
Ⅲ. Why don't you add test cases (unit test/integration test)? (你真的觉得不需要加测试吗？)
No Need
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #920 into master will increase coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #920      +/-   ##
==========================================
+ Coverage   46.57%   46.58%   +0.01%
==========================================
  Files         111      111
  Lines        6611     6611
==========================================
+ Hits         3079     3080       +1
  Misses       3287     3287
+ Partials      245      244       -1

Impacted Files
Coverage Δ

supernode/store/errors.go
73.33% <ø> (ø)
:arrow_up:

supernode/server/result_info.go
0% <ø> (ø)
:arrow_up:

supernode/store/store_mgr.go
43.75% <ø> (ø)
:arrow_up:

supernode/plugins/plugin_manager.go
91.42% <ø> (ø)
:arrow_up:

supernode/daemon/mgr/progress/progress_util.go
21.42% <ø> (ø)
:arrow_up:

supernode/daemon/mgr/peer/manager.go
78.65% <ø> (ø)
:arrow_up:

supernode/store/store.go
59.09% <ø> (ø)
:arrow_up:

supernode/store/local_storage.go
68.58% <ø> (ø)
:arrow_up:

supernode/plugins/plugins.go
100% <ø> (ø)
:arrow_up:

supernode/daemon/mgr/scheduler/manager.go
22.6% <0%> (+0.68%)
:arrow_up:

Continue to review full report at Codecov.

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

LGTM. Thanks for your good job. 👍


You can add the same server multiple times

Either adding it via discovery and then adding it manually, running discovery more than once (say if you add a new server and want to discover that, it will duplicate the original server).
We really need to check to see if a server is present before we go and add it to the list.

Probably obvious, but machineIdentifier is the attribute that unique distinguishes servers.

We don't actually store that in the registry, Elan (we're limited on space we can store for config data). But I just added a simple duplicate check for name / address.

We don't actually store that in the registry, Elan (we're limited on space we can store for config data). But I just added a simple duplicate check for name / address.


shell: "select" command suddenly gone

Following up on the quick discussion on IRC.
So, a user which used both old and new shell would immediately notice the lack of "select" command in the new one. On IRC, I was told that it's not needed, and one can access all commands directly.  I don't what was meant by that, but my interpretation is obvious - it would mean that knowing that there's "stats" command in "net" shell module, I can type "stats" and it would get executed.
Of course, it cannot work like that, because there could be "bt stats", etc. commands. So, I proceeded to check, and of course, "stats" doesn't work:
uart:~$ stats
stats: command not found

Instead, I need to type:
uart:~$ net stats

Interface 0x00424a20 (Ethernet) [0]
===================================

Of course, it's alleviated by completion, but:

Completion was there in the old shell too.
It was possible to use "net stats" in the old shell too.
But besides that, there was also "select <module>" command which allowed get rid of typing "net" altogether!

Of course, with possibility no.3 provided, users enjoyed it. And of course, they noticed the regression with the new shell, and submit tickets asking what's up.

@carlescufi @nashif @pfalcon
New shell has different architecture comparing to the old one. It was highlighted since the very beginning that it will not have namespaces. Of course it would be feasable to implement select command but in my opinion it will have follwoing drawbacks:

it will not bring realy new functionality
it will be extra code that must be maintained
memory footprint will increase
it might confuse the user when subcommand and namespace have the same syntax - what shall be in fact selected?

I am not 100% against but at least I would like to have fair discussion about that. New shell is widely announced hence I expect user are aware about possible changes and losing backward compatibility.

So, unlike some other things (e.g. https://github.com/zephyrproject-rtos/zephyr/issues/10766) I also not 100% "want it back". I'm just taking a role of an end user (and I am such regarding the use of the shell), and trying to understand how it happened that new, improved shell was designed in a way to not support previous shell features. And then to collect feedback from other people whether they miss it. If I'm the only one, well, I guess I can re-learn.

IMHO we do not need select command, personally I never used it earlier anyway.

personally I never used it earlier anyway.

But people apparently did, see e.g. https://github.com/zephyrproject-rtos/zephyr/commit/0b8fde39e4b7b4ab81c763cda7daf0a3cee8cc56 . Quoting the commit message:
This driver has been tested with stm32l4 disco iot board
(disco_l475_iot1) and the wifi sample:

$ select wifi
$ scan
$ connect "CISCO" 5 password
$ select net
$ tcp connect <IP_ADDRESS> 4242
$ tcp send HelloWorld!

This is no regression, when you completely change how the subsystem works, to the better, it happens. I have not seen anyone complaining about this being missing or being broken because of that. Very nice to be speaking for the "users", but I did not hear any users complaining about that. This will will need to be documented in the release notes and should be enough IMO. Let's move on.
If there is a real bug here, please open one with specific details.

Fyi, during hackathon @jarz-nordic was playing around making select command which goes one step into command tree. The trick there was that when you are switching to commands 'branch' you don't have unselect command. For that he used metakey ctrl+x. Such approach emulates starting an application and quitting it. Not sure where that ends and if he plans to do PR since it's rather nice to have feature.

@nashif: This ticket is open for community discussion. Please don't close it single-headedly, unless you want to make (repeated) precedents of how tickets are handled in Zephyr projects.
Otherwise, thanks for your opinion. I fully agree that this matter should be finalized until 1.14 release, so it's useful to keep it open until then.

during hackathon @jarz-nordic was playing around making select command which goes one step into command tree

I do hope that nobody spends implementation effort on this ticket until it's proven as required. I also do hope that it remains a place of discussion, and ultimately, an exercise of change control for all of us.

@pfalcon then please remove the "Regression" from the title. This is not a regression.

@pfalcon

Please don't close it single-headedly

I still need to find the button that supports multi-headed closing.

@pfalcon : I am working on select command. I have following assumptions in my mind:

It is allowed to select a command that:

is static (syntax/handler cannot change in runtime)
has subcommands

You can always select command that is deeper in commands tree if it fulfills 1)

When command is successfully selected, prompt will change to selected command syntax + $ or > (TBD).

To unselect command you can either type select with no arguments or `select

Unselect will always bring you to command's ROOT_LEVEL (you cannot recursively unselect).

@jarz-nordic

I am working on select command.

@jarz-nordic: Thanks for bringing this up. I actually wanted to post my impressions of "3 months without select". In short, I still miss it, even if mostly subconsciously. If I don't use the shell for 3-4, next session I either start with automatically typing "select", or with typing "iface", "ping", etc., and getting error.
Now after posting that, my intention was to close this ticket, because it didn't generate much interest, and as I told a few times, while I consider such matters to be a topic for discussion, I don't consider that someone should spend effort on such obviously subjective matters only because I want.
So, please think again if it's good investment of your time. If you implement it, I will use and will appreciate it. The way I would image it to be implement is to store select's argument in some buffer, then prepended to each command typed later (max line length should be taken into account). Except of course not everything can be an arg of "select", but a "subcategory command" like "net".
All in all, the above is pretty trivial, and you would certainly know better. But surely let's make it KISS.

When command is successfully selected, prompt will change to selected command syntax + $ or > (TBD).

I like this. All other points also makes sense.
Thanks.

@pfalcon : I am quite close to PR so please expect it shortly.

According to comments in #13425 this issue can be closed.


Log Failed Videos

This commit implements the following:

The feature request from issue #15 is now functional. To support it, a new CLI argument, --failed-videos-page, has been added to specify the page name. The page must already exist within the Hydrus client at the time the program is run, and it must be a file search page. If there is more than one page with the same name, one of the pages will be chosen pseudo-randomly. If no valid page can be found, it fails gracefully while allowing the program to continue.
Additionally, all phashing failures with video-specific information are now simultaneously logged to a .txt file for easier info collection (file stored in the same directory as the database files)
The --job-count parameter can now be set via environment variable
An additional comment has been added with a specific link for checking the status of 'unordered-generator' on joblib's GH

Thanks for the work. This is a very cool feature.
I will take another look at this after the refactor, as discussed. I don't expect you to rewrite any of this afterwards due to refactor changes so I will see what I can do.

Thanks for the work. This is a very cool feature.
I will take another look at this after the refactor, as discussed. I don't expect you to rewrite any of this afterwards due to refactor changes so I will see what I can do.

Closing this out as you've got it in there! 🎉


Test run enhancements

I think this should be added to the test run function, too.
The test run kills the command after 10 seconds but it can have undesirable results when performing local or remote operations (git push/pull, sendmail, cp, brew upgrade) when testing a command.
Some operations can stall and have no output for more than 10 seconds but still be active.

Current architecture is pretty simple and it doesn't monitor user commands - everything is executing in a "run-and-forget" manner.
Test run is different, though. Since we can't really understand whether the command hanged or just doing some work, i decided that it's not that common for a shortcut command to do something more than 10 seconds.
I guess the right solution here is to allow user to abort test run any time he want by pressing a button or something. I'll think about it later, 1.1 release is a priority now.

Just to add that if the test run window presented the command output in realtime (scrolling window like in the default terminal), then it would just need a Cancel button. Or, as an alternative, a button to run the test in the default terminal (to avoid complicating the code). Just an idea for a new issue.

I'll leave it all as one issue since it's easier to work on one particular part of functionality. Could be done for 1.2 or later.

No silly timeouts anymore, added the abort button (works like that). Realtime output won't make it to the next version though, so I'll leave it open.

This is more complicated than i originally anticipated, going to postpone it again.

Since I have very little time to continue the development of this project, I decided to cancel some of the planned features, otherwise the new release will never be a thing. Test run will stay at it is, I think it's good enough anyway.


[sysrst_ctrl] added the markdown file

Signed-off-by: Eric Shiu<EMAIL_ADDRESS>

Okay. rebase and push the branch.


test-branch/execute-job/wrong-commit-sha-on-pr/48763c41-7a9d-4e24-8efb-315e2c81d4bd

PR for testing f461d30829b247a149a440e8021cc510781469e0

/canonical/self-hosted-runners/run-workflows 931ad21dd9ace68aaa0a7d341e94de96ad93fa6b


Use start script

The canonical default executable is start script in the package.json file, that by default is server.js file, not bin entry since you can define several binaries in a single package.

That is, you'd like to just run pkg without specifying a filename? An interesting idea. The problem with start is that it's an arbitrary shell command, not a JavaScript entry point. The main entry point could perhaps be more appropriate since it does point to a JavaScript file.

Or some property in the package.pkg config object, like "entrypoint".

You can always specify entry point javascript file explicitly in CLI instead of passing path to package.json.

Thoughts on using the main field?
I know it's primarily used in libraries, but it would be a good fit for pkg as well.

I would still go for the start script entry, also if it's supposed to be a
shell command, because people usually just define an executable there or if
not an ad-hoc executable script can be created. If not, I would add a new
field, but I'm a bit against this idea having currently valid alternatives.
El 2/5/2017 6:28, "Jim Buck"<EMAIL_ADDRESS>escribió:

Thoughts on using the main
https://docs.npmjs.com/files/package.json#main field?
I know it's primarily used in libraries, but it would be a good fit for
pkg as well.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zeit/pkg/issues/43#issuecomment-298494658, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvsB_MGKMUwiZ6AhEUOJ6pv42_jKBks5r1rD-gaJpZM4NMhwZ
.

Sorry, i can not get why you don't like bin field. Pkg's purpose i to (mostly) preserve npm i something -g tool installation and usage scenario. Since globally installed tool uses bin field, the idea behind pkg was to use bin field as well.

And yeah, you can specify several subfields in bin field. Pkg will use one that's name matches with name field of package.json.

@igorklopov Ahhh I did not realize that the bin entry was already supported. I see now that it's also documented in the README.
I'm closing since I don't think it makes sense to duplicate functionality when there is already a mechanism to specify entry point in the package.json. Thank you for the suggestion though!

Please open this again, the problem is not the lack of functionality but
the fact it's not standard compliant, as start script is. Please read npm
package.json documentation and fix that, bin field is not designed to be
used that way and it's a bug.
El 2/5/2017 7:45, "Nathan Rajlich"<EMAIL_ADDRESS>escribió:

@igorklopov https://github.com/igorklopov Ahhh I did not realize that
the bin entry was already supported. I see now that it's also documented
in the README https://github.com/zeit/pkg#usage.
I'm closing since I don't think it makes sense to duplicate functionality
when there is already a mechanism to specify entry point in the
package.json. Thank you for the suggestion though!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zeit/pkg/issues/43#issuecomment-298502596, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAgfvkGT919cBfMrlEPWDRJr_PNwiksUks5r1sMVgaJpZM4NMhwZ
.

@piranna The "start" script is used for starting servers, not CLI applications. The bin field is absolutely used for CLI applications, and npm encourages this with the --global flag installing into your $PATH.
pkg mapping to bin is perfect.

npm start is also used to start cli applications too, I have seen using server.js just for this everywhere. Also, since several years ago usage of --global and globally installed modules are absolutely deprecated, so that's not the point. You can use bin, but that's a mapping of the executables that offer that module, that can be several of them, and there's no requeriment that any of them has the same name of the current module, so blindly trust on that field is a bad usage and a bug according to the spec. As I said before, better alternatives are to use standard start script, or if not following standard practices, add a new custom field on package.json file just for this.

Great idea with npm start 👍
Implementing that allows us easily pack micro-services to single executable.


Update analyze_logs.py

Thank you very much for bringing great help to my research. I encountered a small problem in the process of using it, and I have already proposed the bug and my solution in issue 5396. I was told that I could create a PR to fix that, so I give it a try by creating this PR.
Describe the bug
When using the plot_curve function tools/analysis_tools/analyze_logs.py to plot the curve of loss-iteration, loss values with a large number of iterations will be misplaced in front of the loss with a small number of iterations. Therefore, some details of the loss-iteration curve are disorderly.

There could be some problems with the setting of abscissa(iters). I checked the plot_curve fucntion in tools/analysis_tools/analyze_logs.py and found that num_iters_per_epoch could not return the right value. It returns the iter of mode:val instead of the last/biggest number of mode:train in log.json file.
Reproduction
Using python tools/analysis_tools/analyze_logs.py plot_curve log.json --keys loss_cls --legend loss_cls to plot curve.
Here's my log and log.json file.
logandlogjason20210619_165226.zip
Bug fix
I tried a method that can solve my problem, but it may not work for all related problems.
ln line 68 of tools/analysis_tools/analyze_logs.py, I changed num_iters_per_epoch = log_dict[epochs[0]]['iter'][-1] to num_iters_per_epoch = log_dict[epochs[0]]['iter'][-2]. After the change, num_iters_per_epoch could return the last value of mode:train instead of the value of mode:val.

The solution only works when there is only one value of mode:val.
Thanks again.
PS
I do NOT check the potential influence on downstream projects, please pay attention.

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

Hi @Y-M-Y ！First of all, we want to express our gratitude for your significant PR in the mmdetection project. Your contribution is highly appreciated, and we are grateful for your efforts in helping improve this open-source project during your personal time. We believe that many developers will benefit from your PR.
We would also like to invite you to join our Special Interest Group (SIG) private channel on Discord, where you can share your experiences, ideas, and build connections with like-minded peers. To join the SIG channel, simply message moderator— OpenMMLab on Discord or briefly share your open-source contributions in the #introductions channel and we will assist you. Look forward to seeing you there! Join us ：https://discord.gg/raweFPmdzG
If you have WeChat，welcome to join our community on WeChat. You can add our assistant ：openmmlabwx. Please add "mmsig + Github ID" as a remark when adding friends：）
Thank you again for your contribution❤


Fix NullPointerException due to missing schema

Seems to fix #639

Thanks @fmjaeschke - would it be possible to add a test?

Thanks @fmjaeschke - would it be possible to add a test?

Currently I don't know how to test the DevServicesArtemisProcessor. Even checked the existing tests for AmqpDevServicesProcessor in smallrye-reactive-messaging-amqp extension which is very similar to DevServicesArtemisProcessor.

Anything holding us back to merge this?

@all-contributors please add @fmjaeschke  for bug and code


Fix Hot/Cold Nardah Genie Cave tile

Title
Fixes #4238

The screenshots in #4238 seem to indicate that a working tile is exactly 7 tiles north of the existing world point. Have you checked the world point in this PR using the dev tools to ensure it is correct?

IIRC all hot/cold clues have a 3X3 area that you can dig in successfully. I did use the dev tools to double check this.
I used the orb, got the message of directly under me and took a screen shot of the coordinate layout:
https://i.imgur.com/hNwpT1D.png


isValid() should follow RFC-952

The current implementation is too naive.
  The syntax of a legal Internet host name was specified in RFC-952
  [DNS:4].  One aspect of host name syntax is hereby changed: the
  restriction on the first character is relaxed to allow either a
  letter or a digit.  Host software MUST support this more liberal
  syntax.

  Host software MUST handle host names of up to 63 characters and
  SHOULD handle host names of up to 255 characters.

  Whenever a user inputs the identity of an Internet host, it SHOULD
  be possible to enter either (1) a host domain name or (2) an IP
  address in dotted-decimal ("#.#.#.#") form.  The host SHOULD check
  the string syntactically for a dotted-decimal number before
  looking it up in the Domain Name System.

  DISCUSSION:
       This last requirement is not intended to specify the complete
       syntactic form for entering a dotted-decimal host number;
       that is considered to be a user-interface issue.  For
       example, a dotted-decimal number must be enclosed within
       "[ ]" brackets for SMTP mail (see Section 5.2.17).  This
       notation could be made universal within a host system,
       simplifying the syntactic checking for a dotted-decimal
       number.

       If a dotted-decimal number can be entered without such
       identifying delimiters, then a full syntactic check must be
       made, because a segment of a host domain name is now allowed
       to begin with a digit and could legally be entirely numeric
       (see Section <IP_ADDRESS>).  However, a valid host name can never
       have the dotted-decimal form #.#.#.#, since at least the
       highest-level component label will be alphabetic.

Cf https://www.ietf.org/rfc/rfc952.txt and https://www.ietf.org/rfc/rfc1123.txt.
Could/should possibly be made available as a separate module.
closes #58

I close this issue since #100 added a RFC compliant implementation of isValid.


[CI][C++] Add nightly job to test offline build

See discussion on https://github.com/apache/arrow/pull/9803
Reporter: Neal Richardson / @nealrichardson
Note: This issue was originally created as ARROW-12095. Please see the migration documentation for further details.

Issue resolved by pull request 44721
https://github.com/apache/arrow/pull/44721


Add support for pointer function format

Following discussion with grevy It should be possible to:

define pointer function format object
declare variable and input variable of those objects
being able to call variable function with specified parameters

feature partially implemented on branch multi_precision
See unit_test function_ptr.py for an example:
metalibm_function/unit_tests/function_ptr.py

Features has been merged into master.


[Bug] Guidelines not rendering in correct positions

Reproducible in vscode.dev or in VS Code Desktop?

[X] Not reproducible in vscode.dev or VS Code Desktop

Reproducible in the monaco editor playground?

[X] Not reproducible in the monaco editor playground

Monaco Editor Playground Link
No response
Monaco Editor Playground Code
No response
Reproduction Steps

Get the latest source from the repository. The follwing will download the package as a .tgz file into your working directory and extract it:

npm pack monaco-editor
tar xvf monaco-editor-0.52.0.tgz

Paste the code below into an index.html file in the same directory where you downloaded the code to:

<!DOCTYPE html>

    <title>Monaco Test</title>
    <link rel="stylesheet" type="text/css" data-name="vs/editor/editor.main" href="package/min/vs/editor/editor.main.css">

Open the index.html file using VSCode LiveServer.
Then the problem should already be appearent.

Actual (Problematic) Behavior
The guideline is drawn in the wrong spot:

Expected Behavior
The guideline should be drawn like this:

Additional Context
No response

I have already looked into this and I think the problem is the way the character widths in charWidthReader.ts are calculated.
The DomCharWidthReader uses the _createDomElements Method to create some test elements. It creates three div-elements (one for each font-style: bold, italic and normal), which then are filled with a bunch of span-elements that each contain a different character of which the width is to be measured. The configured font-style (fontFamily, fontSize, etc.) is applied to the three div-elements, which are then all wrapped into another div and appended to the body.
The created test element (stored in this._container) looks something like this:

        iiiiiiiiiiiiiiiiiiiiii

        |||||||||||||||||||||||

        |||||||||||||||||||

You will notice that the three div-elements have the styles applied, which the span-elements in them should inherit. And here is the problem: When somebody uses the * CSS-Selector to apply global styles it takes precedence to the inherited style of the parent. This means that even though the div-elements have the correct styles applied, the span-elements, which are actually used to measure the characters, don't inherit them.
This is also visible in the DevTools of the browser when you select one of the span-elements:
.
Potential Solutions

The first one would be to just apply the styles to the span elements (this would mean calling applyFontInfo for each span-element created.)
The second possibility would be to set the all font properties to inherit: testElement.style.font = 'inherit'. This would mean that the span-elements would explicitly inherit their styles directly from their parents which would override the global *-style.

I am very open to a discussion and am also very motivated to implement the change.
Thanks for reading :)


Ignore Namespace Field of Contour When GatewayClassRef is Set

Please describe the problem you have
Currently, the contour.spec.namespace.name must match gateway.namespace. Instead, ignore the field since an instance of Contour should be deployed to the namespace of the associated Gateway.

Removing milestone until the community achieves a consensus on the Gateway API implementation plan.


Change speedbonus to be adjustable

Credits to vun for modelling, base value needs to further tested before commit.

kinda messed it up lol whoops


[demo - prize draw] move the confirmation message down the screen

On the demo, on the prize draw part, the feedback message confirming that the participation has been recorded

is at the top of the screen and is non visible if the screen is scrolled down, can lead the user wondering if the button has been clicked correctly, if the the form has been submitted correctly
The confirmation message should be at the bottom of the screen under the buttons so the user can see right away that the entry is submitted without having to scroll up

Done

Thanks works well


test: use new auth API and js-auth helpers

Closes #459

What I did

How to test

Checklist

[x] Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests).
[x] Make sure to add/update documentation regarding your changes.
[x] You are NOT deprecating/removing a feature.

:tada: This PR is included in version 4.9.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


PAYDAY 2 few patches ago everything was fine

Software information
PAYDAY 2, High settings.
System information

GPU: NVIDIA GeForce RTX 3060
Driver: 517.48
Win version: 10 x64 Home Edition
DXVK version: 1.10.3

Log files

d3d9.log: payday2_win32_release_d3d9.log
crash.txt: crash.txt

Try uninstalling RivaTuner Statistics Server and MSI Afterburner. Those are known to break Vulkan applications.


Fix #1570: use overflow-immune algorithm in hypot()

This has the side effect of slowing down math.hypot() by 2x, and speeding up np.hypot() by 30%

I think the only way to get the speed back would be to insert a branch that tests whether both x and y are less than half of the max float size, and then use the simple algorithm in that case.

Actually, doing some additional research, I think both the original and new implementation are wrong.  Apparently IEEE-754 actually specifies how this function must be done in order to achieve correct precision:
http://www.netlib.org/fdlibm/e_hypot.c
I am now sufficiently spooked to wonder why we aren't calling the system libm for this.   Is hypot not present on some platforms?

I am now sufficiently spooked to wonder why we aren't calling the system libm for this.

I think the assumption was that inlining the naive version could make it faster. Which is still true even with the current version, actually (vs. Numpy).

Is hypot not present on some platforms?

According to the man pages here, it's C99 not C89. I don't know if Windows has it...

If we can use the platform hypot, I would prefer to do that, otherwise we are taking responsibility for meeting the precision requirement in our inlineable version of the algorithm.

Ok, so hypot() is always available on Windows but, before VS2013, hypotf() is only available on Itanium systems...

When we come back to fix this, I think we need to use the platform hypot() and hypotf() where available.  If hypotf() is not available, cast up to double, use hypot() and cast back.

This was superseded by #1934.


fastlane-match 0.0.2

New Pull Request Checklist
Please mark the points which you did / accept.

[x] I read the Step Development Guideline
[ ] I have a test for my Step, which can be run with bitrise run test (in the step's repository)
[x] I did run bitrise run audit-this-step (in the step's repository - note, if you don't have this workflow in your bitrise.yml, you can copy it from the step template.)
[x] I read and accept the Abandoned Step policy

Hi @blackjid ,
Thanks for the PR! We will check it ASAP.

Hi @blackjid ,
thanks for the step PR, i really like this step! Both the step.yml and the step repo looks great!
You may update later the step's descriptions, since the match docs moved to: https://docs.fastlane.tools/actions/match/.


Windows 7 notifications

This is the implementation of desktop notifications for Windows 7.
Resolves electron #8384

@electron/maintainers Looking for reviewers for this. Thanks

:bow: Thank you so much for this mountain of work. Tons of people will be very happy - I'll try to take a quick look on Monday.

Does the code under browser/win/win32_desktop_notifications come from an existing library? It seems that the implementation is glueing an library instead of writing everything from scratch.

No, it's 100% new code. That part under the subdirectory is functionally independent, that's maybe why it looks like a separate library - it's structured that way.

This looks 👏 really good. As discussed in person, I'm so very happy we have this PR. Thank you so much! I have only three requests:
:one: As mentioned by @poiru, snake_case would be a good change.
:two: We frequently fail to send notifications using the native ToastNotifier in Windows 8, 8.1, and 10. I would love an option to use this notification object even from versions newer than Windows 7.
:three: I'd love to be able to configure the background color.
Both 2 and 3 could easily be another PR in the future.

I will post an update with snake casing later. I also have a fix for a small DPI related bug that I discovered, but I still need to test it in a multi-monitor setup.
We should think more about the right approach for explicitly selecting the type of notification from the calling code. First thing that comes to mind is consistency across non-Windows OSes. But I do support the general idea.
The color is now derived from the one which the user has selected for windows in the Control Panel. I see some value in being able to change it (e.g. to add category classification). Still, we should give it a bit more thought to make sure the feature doesn't make the user's desktop a playground for every app developer's creativity.
Which brings me to an issue which should be addressed as well at some point - this currently doesn't consider a scenario where multiple Electron apps generate notifications at the same time. Right now these would simply overlap each other.

https://github.com/electron/brightray/pull/285 has been merged which enables cpplint on CI builds so if you rebase/merge master it should pull in those changes.

Any progress on this @alespergl 🤗

Thanks!

Hello @alespergl,
Thanks for the great work on this feature.
Could this part of code ported to a single module that can be used in C#?
I'm working on another project in windows forms, which needs to send a notification on windows 7. And I found your solution is the greatest one.
Could you give me some guides/tips to do that?
Thank you very much!


link against pthread when available

Fixes ament/ament_index#8.
http://ci.ros2.org/job/ros2_batch_ci_linux/538/ (using ros2/ros2#138 to not have the libgtest-dev Debian package installed)
http://ci.ros2.org/job/ros2_batch_ci_osx/408/
http://ci.ros2.org/job/ros2_batch_ci_windows/562/

This introduces one warning from gtest.h in gcc: http://ci.ros2.org/job/ros2_batch_ci_linux/538/warnings17Result/
Do we need -Wmissing-field-initializers? Warnings from within gtest seem like unnecessary noise.
Besides that, lgtm.

I reproduced the problem in ament/ament_index#8 (after uninstalling libgtest-dev) with master and can confirm that this patch fixes it. +1

The warning is always shown. I tried to disable it with the extra compiler flags. It was supposed to be -Wno-missing-field-initializers in the first place: http://ci.ros2.org/job/ros2_batch_ci_linux/539/


How to make off-canvas visible by default?

Hey! I'm setting show prop to the true by default, but offcanavas still hidden, so I need to call toggle function twice (show => false, show => true) to show it again. Is it a bug or expected behavior?

Hi, are you trying to load the page with the offcanvas already displayed?

Yes
On Sat, 30 Jun 2018, 14:02 Miljan<EMAIL_ADDRESS>wrote:

Hi, are you trying to load the page with the offcanvas already displayed?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vuikit/vuikit/issues/108#issuecomment-401533971, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEJuNolWgKj8oZ9iHqI4KgCb_iTGQmLxks5uB1q8gaJpZM4U966z
.

Its a missing feature. Will be considered on future versions.


Waiting for socket connections on port 11411 waiting for socket connection

Hi ! I have followed the tutorial and did everything according to it, but after running:
rosrun rosserial_python serial_node.py tcp 11411
it stays stuck on :  Waiting for socket connections on port 11411
waiting for socket connection
I can't seem to find out where the error is, can you please guide me? thanks in advance.

The issue has been solved , thank you so much for this awesome repo.

Can you please elaborate how you solved the issue?

@Shihab-Haque Do you remember what was the solution?


Fix: Shop Screen UI

Fixed CSS of ESIM Item card
Fixed Tab Bar Styles
Refactored code
Add lodash/types dev dep. for Lint issue


Ignore currently unsupported regex operators

This PR ignores currently unsupported operators in parseOperator.
genji> SELECT 0 !~ 1;
found !~, expected ; at line 1, char 10
genji> SELECT 0 1;
found 1, expected ; at line 1, char 10

Closes #252

Codecov Report

Merging #274 into master will decrease coverage by 0.06%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master     #274      +/-   ##
==========================================
- Coverage   61.35%   61.29%   -0.07%
==========================================
  Files          68       68
  Lines        6345     6348       +3
==========================================
- Hits         3893     3891       -2
- Misses       1936     1940       +4
- Partials      516      517       +1

Impacted Files
Coverage Δ

sql/parser/expr.go
77.12% <0.00%> (-0.69%)
:arrow_down:

engine/memoryengine/store.go
91.96% <0.00%> (-1.79%)
:arrow_down:

Continue to review full report at Codecov.

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


Deploy error after changing role name

Hello, I had standard configuration which was working fine. Then I wanted to change the role to match it's meaning from web to api
primary_role: api
servers:
  api:
    - x.x.x.x

It wasn't production server, so I removed also app, old containers and start deploy again. Then I have got error at the end.
  ERROR (SSHKit::Command::Failed): Exception while executing on host x.x.x.x: docker exit status: 1
docker stdout: Nothing written
docker stderr: Error: host settings conflict with another service

Kamal: 2.2.2
Rails 7.2
Ruby 3.3.5

I think you'd need to run kamal app remove with the old config, then change it and then run kamal deploy. Is that would you did?

After those issues I have also removed app kamal app remove and remove all unused containers: docker ps -a, docker rm xxx. And then kamal deploy -d staging. At the end of the build process, I have got mentioned error.

I'm not sure why this is happening then.
The error suggests that kamal-proxy still has a deployment registered under the old role. You should be able to remove it manually with:
docker exec kamal-proxy kamal-proxy ls

This should report the service name. Then you can remove it with
docker exec kamal-proxy kamal-proxy remove <service>

I'm totally stuck on this. I changed the host settings so that I can redirect to www. No I can't get past "docker stderr: Error: host settings conflict with another service" – Kamal is awesome when it works. Very frustrating to hit dead ends like this on pretty common situations (like changing the subdomain).

I renamed my config file from .config/deploy.abc.yml to .config/deploy.xyz.yml and faced this error. @djmb's commands above resolved the issue.

After those issues I have also removed app kamal app remove and remove all unused containers: docker ps -a, docker rm xxx. And then kamal deploy -d staging. At the end of the build process, I have got mentioned error.
When I changed that role back to web, everything is working fine. But for clarity I would like to keep it with name api.

this worked for me as well

Landed here after changing the default role name and no longer having the original default role name present, similar to OP.

I tried kamal all remove locally, but it didn't seem to do the trick.
I also didn't want to revert to the default role name, as my role names are now dynamically generated in ERB.

To fix, per the above comment, running the following on the remote servers in question resolved the issue, but note that it will obviously cause some downtime without working around it, if that will affect you:

docker exec kamal-proxy kamal-proxy ls

This should report the service name. Then you can remove it with
docker exec kamal-proxy kamal-proxy remove <service>


Remove font-awesome-sass

As Rails 7.0 now provides several options to handle CSS assets, we should avoid specifying specific solution for gem users.

But if you do this, many icons won't work.
Do you have an alternative ?

Ahh I found that this gem actually adds nothing in Ruby but just provides assets. So if people want to use Webpacker or esbuild, they could just ignore gem and add npm package directly. Closing this. Thanks!


No docstrings

Comparing this repository to PlaNet, I noticed all the docstrings have been removed in this one. Why is that?

Mostly because it's faster to develop without docstrings.


Improve simplified closeAndRelease task

As suggested in #38:

depend on all closeAndRelease*StagingRepository tasks

As a bonus:

display release task descriptions on gw tasks

Closes #38.

E2E fails with timeout on a repo initialization.
> Task :initializeSonatypeStagingRepository
Caching disabled for task ':initializeSonatypeStagingRepository' because:
  Build cache is disabled
Task ':initializeSonatypeStagingRepository' is not up-to-date because:
  Task has not declared any outputs despite executing actions.
Creating staging repository for sonatype at https://oss.sonatype.org/service/local/, stagingProfileId '248647f1a45ed6'
<=======------> 58% EXECUTING [12m 31s]
> :initializeSonatypeStagingRepository
...

Locally over 10 minutes is not enough. I will try it again later. Looking at the Nexus stats, there is ongoing outbreak (yet):

I wonder, if 45 minutes is somehow bound to some Gradle limit (here locally):
> Task :initializeSonatypeStagingRepository FAILED
:initializeSonatypeStagingRepository (Thread[Execution worker for ':',5,main]) completed. Took 45 mins 23.116 secs.

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':initializeSonatypeStagingRepository'.
> java.net.SocketTimeoutException: Connect timed out

The next time it finished after 1 hours :).
> Task :initializeSonatypeStagingRepository
Caching disabled for task ':initializeSonatypeStagingRepository' because:
  Build cache is disabled
Task ':initializeSonatypeStagingRepository' is not up-to-date because:
  Task has not declared any outputs despite executing actions.
Creating staging repository for sonatype at https://oss.sonatype.org/service/local/, stagingProfileId '248647f1a45ed6'
Created staging repository 'iogithubgradle-nexus-e2e-1507' at https://oss.sonatype.org/service/local/repositories/iogithubgradle-nexus-e2e-1507/content/
:initializeSonatypeStagingRepository (Thread[Execution worker for ':',5,main]) completed. Took 1 hrs 0 mins 22.088 secs.
:publishMavenJavaPublicationToSonatypeRepository (Thread[Execution worker for ':',5,main]) started.

I will report it to Sonatype. It's quite strange.
Btw, on CI it fails with timeout after ~90 seonds (by default timeout is set to 1 minute). Not respecting timeout might be related to my system, VPN or something...


I have the latest Power BI Desktop Version but I cannot see the Azure Cost Management Connector

Thanks for your comment, @HaoZhang615 . This looks like a support request or product question rather than documentation feedback. You might find a solution in the Power BI Community, at https://community.powerbi.com. If not, you can get support by going to https://support.powerbi.com.

Thanks for your comment, @HaoZhang615 . This looks like a support request or product question rather than documentation feedback. You might find a solution in the Power BI Community, at https://community.powerbi.com. If not, you can get support by going to https://support.powerbi.com.


fix: remove cosign layer since main upstream provides cosign in RPM

Despite my constant complaining about RPMs I understand a good portion of our userbase likes the ability to use existing tooling. It might even be worth it just for the changelogs with the version bump being in the right list.
You win this one. 😄

To add insult to injury the wolfi toolbox is broken too? 😄

Despite my constant complaining about RPMs I understand a good portion of our userbase likes the ability to use existing tooling.

It's sigstore's fault. if they didn't ship an RPM, we'd have probably added the cosign layer to main upstream of bluefin instead of the RPM. :-)


Niche optimization in JsValue

Motivation
I have a bunch of code using Option<SomeJsBindgenType>, e.g. Option<JsValue>, Option<Node>. These types are represented as a JsValue under-the-hood, which is declared as
pub struct JsValue {
    idx: u32,
    _marker: marker::PhantomData<*mut u8>, // not at all threadsafe
}

Would it be possible to include a niche-optimization here, e.g. by using idx: NonZeroU32, so that the above Option types have size 4 instead of size 8? It seems some indices are already reserved for values in "stack space", so could we free one additional index to serve as a niche for optimizing Option<JsValue>?
Additional Context
NonZeroU32

Yeah, it should be pretty easy to reduce the stack size by 1 and make index 0 into a niche. I think this makes sense to do.


process and flow categorization

Updated categorization and flow names to match upstream models for issues #70  #71

When I tested your commit it only added Technosphere Flows/ for the electricity flows, but not the upstream flows (coal, gas, etc), which is why I added the same in upstream_dict.py @WesIngwersen


Error detected while processing /root/.vim/bundle/nerdtree/lib/nerdtree/tree_dir_node.vim:

Hi guys
I have been struggling get the nerdtree plugin working on my vim
I am getting below error
[root@dctxvm201 ~]# vim
Error detected while processing /root/.vim/bundle/nerdtree/lib/nerdtree/tree_dir_node.vim:
line  326:
E475: Invalid argument: 117
My scriptname output is below
1: /etc/vimrc
2: /usr/share/vim/vim70/syntax/syntax.vim
3: /usr/share/vim/vim70/syntax/synload.vim
4: /usr/share/vim/vim70/syntax/syncolor.vim
5: /usr/share/vim/vim70/filetype.vim
6: /root/.vimrc
7: /root/.vim/autoload/pathogen.vim
8: /usr/share/vim/vim70/ftoff.vim
9: /usr/share/vim/vim70/syntax/nosyntax.vim
10: /usr/share/vim/vim70/ftplugin.vim
11: /usr/share/vim/vim70/indent.vim
12: /root/.vim/bundle/nerdtree/plugin/NERD_tree.vim
13: /root/.vim/bundle/nerdtree/autoload/nerdtree.vim
14: /root/.vim/bundle/nerdtree/lib/nerdtree/path.vim
15: /root/.vim/bundle/nerdtree/lib/nerdtree/menu_controller.vim
16: /root/.vim/bundle/nerdtree/lib/nerdtree/menu_item.vim
17: /root/.vim/bundle/nerdtree/lib/nerdtree/key_map.vim
18: /root/.vim/bundle/nerdtree/lib/nerdtree/bookmark.vim
19: /root/.vim/bundle/nerdtree/lib/nerdtree/tree_file_node.vim
20: /root/.vim/bundle/nerdtree/lib/nerdtree/tree_dir_node.vim
21: /root/.vim/bundle/nerdtree/lib/nerdtree/opener.vim
22: /root/.vim/bundle/nerdtree/lib/nerdtree/creator.vim
23: /root/.vim/bundle/nerdtree/lib/nerdtree/flag_set.vim
24: /root/.vim/bundle/nerdtree/lib/nerdtree/nerdtree.vim
25: /root/.vim/bundle/nerdtree/lib/nerdtree/ui.vim
26: /root/.vim/bundle/nerdtree/lib/nerdtree/event.vim
27: /root/.vim/bundle/nerdtree/lib/nerdtree/notifier.vim
28: /root/.vim/bundle/nerdtree/autoload/nerdtree/ui_glue.vim
29: /root/.vim/bundle/nerdtree/nerdtree_plugin/exec_menuitem.vim
30: /root/.vim/bundle/nerdtree/nerdtree_plugin/fs_menu.vim
31: /usr/share/vim/vim70/plugin/getscript.vim
32: /usr/share/vim/vim70/plugin/gzip.vim
33: /usr/share/vim/vim70/plugin/matchparen.vim
34: /usr/share/vim/vim70/plugin/netrwPlugin.vim
35: /usr/share/vim/vim70/plugin/rrhelper.vim
36: /usr/share/vim/vim70/plugin/spellfile.vim
37: /usr/share/vim/vim70/plugin/tarPlugin.vim
38: /usr/share/vim/vim70/plugin/tohtml.vim
39: /usr/share/vim/vim70/plugin/vimballPlugin.vim
40: /usr/share/vim/vim70/plugin/zipPlugin.vim
============================================================
and run time path is
runtimepath=~/.vim,~/.vim/bundle/nerdtree,/usr/share/vim/vimfiles,/usr/share/vim/vim70,/usr/share/vim/vimfiles/after,~/.vim/after
Let me know what could be the issue?

I resolved this issuse.
Some files were missing when i copied the nerd-tree plugin to bundle folder.


【小程序】增加上传代码、绑定体验者、开放平台相关API

文档参见微信开放平台 > 资源中心 > 第三方平台 > 代小程序实现业务部分，
因为微信没有提供文档永久链接，所以 docstring 里面就不放文档地址了...
:)

Codecov Report

Merging #242 into master will decrease coverage by 0.14%.
The diff coverage is 50%.

@@            Coverage Diff             @@
##           master     #242      +/-   ##
==========================================
- Coverage   76.64%   76.49%   -0.15%
==========================================
  Files          72       72
  Lines        2937     2953      +16
==========================================
+ Hits         2251     2259       +8
- Misses        686      694       +8

Impacted Files
Coverage Δ

wechatpy/client/api/wxa.py
56.66% <50%> (-7.62%)
:arrow_down:

Continue to review full report at Codecov.

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

Pre-released in v1.5.0.dev0


fix(util): error when filetype is nil

Hi, on latest nvim v0.11.0-dev-1190+gc12be1249f this PR fixes the following issue, preventing Copilot to work
Error executing vim.schedule lua callback: ...e/.local/share/nvim/dev/copilot.lua/lua/copilot/util.lua:143: bad argument #1 to 'gsub' (string expected, got
nil)
stack traceback:
        [C]: in function 'gsub'
        ...e/.local/share/nvim/dev/copilot.lua/lua/copilot/util.lua:143: in function 'get_language_id'
        /usr/share/nvim/runtime/lua/vim/lsp/client.lua:1030: in function '_text_document_did_open_handler'
        /usr/share/nvim/runtime/lua/vim/lsp/client.lua:1049: in function '_on_attach'
        /usr/share/nvim/runtime/lua/vim/lsp/client.lua:631: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

closing, dup zbirenbaum/copilot.lua/pull/340

Has been fixed in core in the meantime, so should be ok with tonight's nightly


JavaTurboModule/LongLivedObject cleanup

Summary:

Don't iterate over JSI Value to get args, convert each of the args individually instead
Make LongLivedObjectCollection constructor private
allowRelease does not need to be virtual
Move away from const-ness as a thread-safety indicator

Changelog: [Internal]
Differential Revision: D43354535

Can you fix the failed checks?


DataBase config + data structure designs (Employees)

Design and implement Data Class (Bean) for employees
Create corresponding database 'bgc' and datatable for employees
Create method to determine ramp-up time in employee class

Giving ramp-up period its own issue


Create grpc health probes for k8s deployments

Add grpc health probe to the server so k8s can check how it is doing.
https://github.com/grpc-ecosystem/grpc-health-probe

Example app: https://github.com/americanexpress/grpc-k8s-health-check

https://github.com/grpc/grpc/blob/master/doc/health-checking.md

https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/#define-a-grpc-liveness-probe

Now that grpc is officially  supporting grpc health probe and k8s can launch probe to the master server, I think the pr in the scoretrak apis is the best way to go about this.


Travis changes

Enables caching, however saves less speed than I was hoping for
Added a directive which will be required in a forthcoming travis update
Travis configuration now installs optional dependencies defined in setup.py, rather than listing requirements again.

Codecov Report

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

@@           Coverage Diff           @@
##           master      #30   +/-   ##
=======================================
  Coverage   99.62%   99.62%
=======================================
  Files           7        7
  Lines         537      537
=======================================
  Hits          535      535
  Misses          2        2

Continue to review full report at Codecov.

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


Move mill.BuildInfo tomill.main.BuildInfo

We currently encourage import mill._, which causes problems when people want to also import mill.contrib.buildinfo.BuildInfo. There's a workaround to import mill.{BuildInfo => MillBuildInfo, _}, which we do in several places in our own codebase, but it's a pain in the neck and an unnecessary hurdle for users to cross. The majority of users would not need to access mill.BuildInfo at all, so putting it in the default namespace just adds clutter.
The mill.BuildInfo is used throughout mill.scalalib and mill.scalajslib and so on, but is not used in main/, so I put it in as downstream a module as possible which turns out to be mill.main.BuildInfo

Sounds good. I'll merge this first, and open a follow up to possibly rename BuildInfo


Add light mode to the app

Issue number #20 is now fixed.
preview-
https://github.com/singodiyashubham87/ScrapeIt/assets/126085856/8856a855-0c4d-4853-91e3-712436841a52
I am contributing under Kharagpur Winter Of Code.

@ayann07 This is not the expected behaviour, The UI does not look appealing at all, don't make it exactly white and this project uses TailwindCSS for styling and not vanilla CSS.


Improve CLI error messages

Fixes #17
Closes #36 (by documenting that toMatchTypeOf ~= toExtend)
Closes #37 (by documenting that helper types are not part of the API surface)
Closes #32
Closes #4
Closes #6 (by documenting that you can't use .not.toBeCallableWith(...))
Closes #38
Use generics to give better error messages than "Arguments for the rest parameter 'MISMATCH' were not provided" for most toEqualTypeOf cases and many toMatchTypeOf cases. This trades off some implementation complexity for better end-user error messages. Essentially, write a special <Expected extends ...> constraint for each overload of each method, which does some crazy conditional logic, which boil down to:

<Expected extends Actual> for toEqualTypeOf (when we aren't in a .not context)
<Expected extends Satisfies<Actual>> for toMatchTypeOf

Anyone interested, have a look at the snapshot updates in errors.test.ts.snap to see what the real world difference is.
Each of these constraints apply only when we know it's going to "fail" - i.e. Satisfies<...> is a fairly meaningless helper type that is used to try to show errors at the type-constraint level rather than the ...MISMATCH: MismatchArgs<...> level which won't give good error messages.
When using .not, the constraint just becomes extends unknown, and you'll have to squint as before.
See also: #14 for the better long-term solution, if the TypeScript team decide to merge the throw types PR.
See also: #13 for a hopefully-complementary improvement to the information on hover, which will improve the cases this doesn't cover.
TODO:

[x] See if the expectTypeOf({a: 1}).toMatchTypeOf({a: 'one'}) case can also be improved.
[x] Document. The constraints are a bit different to what most users would be used to, so it's worth highlighting the best way to read error messages and clarify when they might default to "Arguments for the rest parameter 'MISMATCH' were not provided"

Note: I have publish v0.17.0-1 based on this PR and will hopefully be able to use that version in vitest as a test before merging.

Nice! Happy to have some better error messages in the command line.
I'll take a closer look tomorrow.

Update: looks like it's possible to get rid of ...MISMATCH completely. But some more tests/handling of edge cases around never/any are needed. Might also want to automatically snapshot test all the // @ts-expect-error cases in the main test file. Will push commits for that soon.

Here's something kind of weird...
With these changes in the dx-generics branch, both the following compile:
  expectTypeOf({a: 1}).toMatchTypeOf<{a: number; b?: string}>()
  expectTypeOf({a: 1}).not.toMatchTypeOf<{a: number; b?: string}>()

In main, only the former compiles.

Here's something kind of weird...
With these changes in the dx-generics branch, both the following compile:
  expectTypeOf({a: 1}).toMatchTypeOf<{a: number; b?: string}>()
  expectTypeOf({a: 1}).not.toMatchTypeOf<{a: number; b?: string}>()

In main, only the former compiles.

Good catch, thank you. I've converted this to a branch since there are a few things up in the air and it isn't ready to go in.

Spent some time talking about this with @shicks and @12wrigja and we came up with some good ideas for some more dx.
Succinctly, it's a change like this:
const error = Symbol('error')

type ExpectedToBeNull<T> = {[error]: T}
type ExpectedNotToBeNull<T> = {[error]: T}

type IsASuperTypeOf<T> = {[error]: T}
type IsNotASuperTypeOf<T> = {[error]: T}

export type ExpectTypeOf<Actual, B extends boolean> = {
  toBeNull:
     Extends<Actual, null> extends B ?
         () => true :
         B extends true ? ExpectedToBeNull<Actual> : ExpectedToNotBeNull<Actual>

  toMatchTypeOf: {
    <Expected extends (
      B extends true ?
        (Extends<Actual, Expected> extends true ? unknown : IsASuperTypeOf<Actual>) :
        (Extends<Actual, Expected> extends false ? unknown : IsNotASuperTypeOf<Actual>)
    )>(): true
    <Expected extends (
      B extends true ?
          (Extends<Actual, Expected> extends true ? unknown : IsASuperTypeOf<Actual>) :
          (Extends<Actual, Expected> extends false ? unknown : IsNotASuperTypeOf<Actual>)
     )>(
      expected: Expected,
    ): true
  }

For toBeNull, you get errors like:
test/usage.test.ts:97:19 - error TS2349: This expression is not callable.
  Type 'ExpectedToBeNull<number>' has no call signatures.

97   expectTypeOf(1).toBeNull()
                     ~~~~~~~~

test/usage.test.ts:96:26 - error TS2349: This expression is not callable.
  Type 'ExpectedNotToBeNull<null>' has no call signatures.

96   expectTypeOf(null).not.toBeNull()
                            ~~~~~~~~

For toMatchTypeOf, you get an error message like:
test/usage.test.ts:27:49 - error TS2344: Type '{ a: string | number; }' does not satisfy the constraint 'IsNotASuperTypeOf<{ a: number; }>'.
  Property '[error]' is missing in type '{ a: string | number; }' but required in type 'IsNotASuperTypeOf<{ a: number; }>'.

27   expectTypeOf<{a: number}>().not.toMatchTypeOf<{a: number|string}>()
                                                   ~~~~~~~~~~~~~~~~~~

  src/index.ts:108:30
    108 type IsNotASuperTypeOf<T> = {[error]: T}
                                     ~~~~~~~
    '[error]' is declared here.

This loses tsc telling you specifically what wasn't matching between expected and actual as having the previous comparison be backwards was a bit misleading but it does print out the types so you're aware of what types you were dealing with. Unfortunately, the only useful bit is the very first line of the error. Everything else is noise.

Hello, I didn't really look well at the PR, but just wanted to mention that I've noticed that the message that appears when hovering on an IDE can change significantly between TS versions. In particular, the expansions of generic expressions. Some versions may show Foo<Bar> while others may show things like { resultOfExpandingFoo: Bar }. Especially with complex types (with many layers of generics). Sometimes, the result of expanding the expression was very simple, but still TS would show things like X extends infer Y ? NonNullable<DeepPartial<Y>> : Something<X> instead of resolving into { a: 1 }. Just a reminder that this may happen. Maybe you put lots of effort in giving users good messages on hovering, but then a new TS version comes (every month!) and it could break...

Seems like the easy solution here is to just make sure any possible expansion is readable.  In particular,
type IsASupertypeOf<T> = {[error]: T};

is not particularly readable if it's expanded, but if the internal symbol were instead
type IsASupertypeOf<T> = {[isASuperTypeOf]: T};

then it shouldn't really matter whether it's expanded or not - I can't imagine any reasonable way TypeScript could format that badly.

Spent some time talking about this with @shicks and @12wrigja and we came up with some good ideas for some more dx.
Succinctly, it's a change like this:
const error = Symbol('error')

type ExpectedToBeNull<T> = {[error]: T}
type ExpectedNotToBeNull<T> = {[error]: T}

type IsASuperTypeOf<T> = {[error]: T}
type IsNotASuperTypeOf<T> = {[error]: T}

export type ExpectTypeOf<Actual, B extends boolean> = {
  toBeNull:
     Extends<Actual, null> extends B ?
         () => true :
         B extends true ? ExpectedToBeNull<Actual> : ExpectedToNotBeNull<Actual>

  toMatchTypeOf: {
    <Expected extends (
      B extends true ?
        (Extends<Actual, Expected> extends true ? unknown : IsASuperTypeOf<Actual>) :
        (Extends<Actual, Expected> extends false ? unknown : IsNotASuperTypeOf<Actual>)
    )>(): true
    <Expected extends (
      B extends true ?
          (Extends<Actual, Expected> extends true ? unknown : IsASuperTypeOf<Actual>) :
          (Extends<Actual, Expected> extends false ? unknown : IsNotASuperTypeOf<Actual>)
     )>(
      expected: Expected,
    ): true
  }

For toBeNull, you get errors like:
test/usage.test.ts:97:19 - error TS2349: This expression is not callable.
  Type 'ExpectedToBeNull<number>' has no call signatures.

97   expectTypeOf(1).toBeNull()
                     ~~~~~~~~

test/usage.test.ts:96:26 - error TS2349: This expression is not callable.
  Type 'ExpectedNotToBeNull<null>' has no call signatures.

96   expectTypeOf(null).not.toBeNull()
                            ~~~~~~~~

For toMatchTypeOf, you get an error message like:
test/usage.test.ts:119:54 - error TS2344: Type '{ a: string; }' does not satisfy the constraint 'IsASuperTypeOf<{ a: string | number; }>'.
  Property '[error]' is missing in type '{ a: string; }' but required in type 'IsASuperTypeOf<{ a: string | number; }>'.

119   expectTypeOf<{a: string | number}>().toMatchTypeOf<{a: string}>()
                                                         ~~~~~~~~~~~

  src/index.ts:108:27
    108 type IsASuperTypeOf<T> = {[error]: T}
                                  ~~~~~~~
    '[error]' is declared here.

and for .not:
test/usage.test.ts:27:49 - error TS2344: Type '{ a: string | number; }' does not satisfy the constraint 'IsNotASuperTypeOf<{ a: number; }>'.
  Property '[error]' is missing in type '{ a: string | number; }' but required in type 'IsNotASuperTypeOf<{ a: number; }>'.

27   expectTypeOf<{a: number}>().not.toMatchTypeOf<{a: number|string}>()
                                                   ~~~~~~~~~~~~~~~~~~

  src/index.ts:108:30
    108 type IsNotASuperTypeOf<T> = {[error]: T}
                                     ~~~~~~~
    '[error]' is declared here.

This loses tsc telling you specifically what wasn't matching between expected and actual as having the previous comparison be backwards was a bit misleading but it does print out the types so you're aware of what types you were dealing with. Unfortunately, there's quite a bit of noise in these.
I recognize that this snippet doesn't handle unknown and never correctly like it did before so you'd probably want to adjust for that as well.

@trevorade @shicks @12wrigja I did something like this and I think it's a big improvement! I ended up doing lots of refactoring, including separating out positive from negative assertions. Would you like to take a look?

I'm merging this and will release as v0.17.0 soon.


Facet error when using a cursor to change rendered component

I Have a component that conditionally renders <Login /> or <Ok /> depending on a value on a Baobab tree:
var Main = React.createClass({
  mixins: [branch],
  cursors: {
    userCursor: ['user']
  },

  render() {
    if(this.state.userCursor.id === ''){
      return <Login />;
    } else {
      return <Ok />;
    }
  }
})

But as soon as the tree is updated and an user object is set, I get an "Cannot convert undefinded or null to object", on facet.js.
On facet.js, if I add a check before self.cursors everything works, but this is obviously not a permanent solution:
 this.updateHandler = function(e) {
    if(!self.cursors) return;
    var paths = Object.keys(self.cursors).map(function(k) {
      return self.cursors[k].solvedPath;
    })

Hello @cassiozen, I'll investigate this issue asap. In the meantime, could you show me what your app's state looks like, please?

Sure:
var Baobab = require('baobab');

var tree = new Baobab({
  user: {
    id: '',
    username: '',
    firstname: '',
    lastname: '',
    email: '',
    avatar: ''
  },
  viewStates: {
    login: {
      invalidLogin: false,
      loading: false
    }
  }
});

module.exports = tree;

Ok @cassiozen, I traced the bug (a very nasty one I must say) and it seems the event emitter is the culprit here. I need to investigate some things and hopefully fix this.

Well it seems that emmett's behaviour is consistent with node's emitter (see this).
I therefore need to add a killed flag in the facet to avoid those kind of things.

Ok, tested this just now. This should be fixed as per last commit.

Nice! this was affecting me too.


version 0.0.6 update broke google-colab today

I'm getting this error:
AttributeError: module 'jaxlib.xla_extension' has no attribute 'PmapFunction'

Thanks for the report, the version of JAX in Colab is quite old (5 releases behind!). I'll chat with the Colab+JAX teams to see if we can get it updated.
For now you will need to manually upgrade the version of JAX that is installed in your Colab. Here is an example: https://colab.research.google.com/gist/tomhennigan/d3114f83c64a6a79374589a96cf2eb5a/upgrade-jax-in-colab.ipynb . The important part is:
!pip install --upgrade pip
!pip install --upgrade "jax[cuda]" -f https://storage.googleapis.com/jax-releases/jax_releases.html

The JAX version in Colab is now 0.3.4 which should be sufficient for the latest Haiku :).


[Docs] Support for dynamic names in property mediator

@sajithaliyanage commented on Tue Apr 07 2020
Description:
Updating the documentation related to $subject. We need to update the property mediator configuration section at[1] with the following new feature.
From the PR https://github.com/wso2/wso2-synapse/pull/1510, we have added the dynamic name support for the property mediator. Now users can add dynamic property names within the { and } brackets inside the name attribute. Some examples can find below.
Examples:
<property name="{get-property('propertyName')}" expression="$ctx:propertyValue" />
<property name="{$ctx:propertyName}" expression="$ctx:propertyValue" />
<property name="{json-eval({$ctx:propertyName})}" expression="$ctx:propertyValue" />

Note:
The property mediator can not have a static name like {name} further since above fix uses the same logic used in defining the sequence mediator key attribute.
Suggested Labels:
Type/Documentation
Affected Product Version:
MI 1.2.0
[1] - https://ei.docs.wso2.com/en/latest/micro-integrator/references/mediators/property-Mediator/

Fixed with https://github.com/wso2/docs-ei/pull/1624


Reshape layer drops mask from previous layers

System information.

Have I written custom code (as opposed to using a stock example script provided in Keras): Yes, very basic code
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):  Ran it on google colab notebook (https://colab.research.google.com/) as well as CentOS 7
TensorFlow installed from (source or binary): Binary / however it is installed in colab
TensorFlow version (use command below): v2.6.0-0-g919f693420e 2.6.0
Python version: 3.7
Bazel version (if compiling from source): N/A
GPU model and memory: N/A
Exact command to reproduce:

import tensorflow as tf
import numpy as np

num = 10

embedding_size = 5
window_size = 2

emb = tf.keras.layers.Embedding(
    num, embedding_size, input_length=1, mask_zero=True
)

td = tf.keras.layers.TimeDistributed(emb)

inp = tf.constant(
    np.array([
              [0,1],[3,0],[4,0]
    ])
)

inp = tf.keras.layers.Reshape((window_size, 1))(inp)
print(inp)

out = td(inp)
print(out.shape,out._keras_mask)

out2 = tf.keras.layers.Reshape((window_size,embedding_size ))(out)
print(out2.shape)

#The following throws an error, because Reshape dropped the mask from the previous tensor:
print(out2._keras_mask)

Error from last line:

AttributeError: 'tensorflow.python.framework.ops.EagerTensor' object has no attribute '_keras_mask'

Describe the problem.
Applying the Reshape layer to a tensor that has a mask (e.g., from the Embedding Layer) gets rid of the mask, instead of reshaping it.
This is a problem because in order to re-use an Embedding Layer for different outputs, I need to apply reshape after certain transformations, before passing to other layers (e.g., LSTM), but instead of also reshaping the mask of the tensor (as a user would expect), Reshape apparently discards the mask entirely, so I cannot use it.
To resolve this I would have to write a custom version of the Reshape layer to replace it.
Describe the current behavior.
Reshape layer applied to a tensor with a mask discards the mask instead of reshaping it.
Describe the expected behavior.
Reshape layer should not discard the mask of a tensor when reshaping it, but instead should correspondingly reshape the mask as well (so the mask now correctly applies to the reshaped tensor and can be passed to subsequent layers like LSTM).
I.e., in the code snippet above, for 'out', I have a tensor with shape (3, 2, 1, 5) and mask =
tf.Tensor(
[[[False]
  [ True]]

 [[ True]
  [False]]

 [[ True]
  [False]]], shape=(3, 2, 1), dtype=bool)

After the Reshape application above, the output is shape (3,2,5) - I would expect the mask to be correspondingly reshaped like:
new_mask = tf.keras.layers.Reshape((window_size,))(out._keras_mask)
So that the new mask is now shape (3,2) =
<tf.Tensor: shape=(3, 2), dtype=bool, numpy=
array([[False,  True],
       [ True, False],
       [ True, False]])>

Contributing.

Do you want to contribute a PR? (yes/no): no

Standalone code to reproduce the issue.
See the code block at the beginning.
Source code / logs.
N/A

issue reproducible at colab

@brian36 ,
Can you please take a look at this issue with similar error.It helps.Thanks

@brian36 ,
Can you please take a look at this issue with similar error.It helps.Thanks

This other issue is unrelated.
The issue here is, there is no keras mask when there should be one, after passing a tensor with a mask through reshape.
This is not a support issue or question about implementation, but in my opinion a bug with the Reshape layer implementation.  At the very least it should give the option of keeping the underlying mask when passing through the Reshape layer, and it definitely should warn the user it's dropping the underlying mask / mention this in the documentation if nothing else.  Instead it does neither.

@jvishnuvardhan I Was able to reproduce the issue in TF v2.6 and TF-nightly please find the gist .Thanks!

We don't believe the reshape layer supports masking at this time, though it could be added. We are happy to accept contributions that add it as a feature
(Separately, we should consider raising an error when passing a tensor with a mask to a layer that does not support masking, rather than silently dropping the mask)

@tomerk Can I work on this if no one else is?


access log support smooth upgrade

close #4505

done https://github.com/juicedata/juicefs/pull/4524


chore(updatecli): replace title by name in terraform-providers

This PR aligns manifest syntax with other manifests like https://github.com/jenkins-infra/digitalocean/blob/main/updatecli/updatecli.d/hashicorp-tools.yml or (more exactly) https://github.com/jenkins-infra/azure/blob/main/updatecli/updatecli.d/terraform-providers.yaml
Note: no title in the action section is needed here as there is no variable in it, thus the name will be used as PR title.
Follow-up of https://github.com/jenkins-infra/digitalocean/pull/122#discussion_r1239756668

Doing so triggers the following JSON schema error:
Missing property "name".yaml-schema: Updatecli

I gues our other manifest need an update, but it means we have to check carefully the JSOn schema when changing updatecli files

I see this error on the main branch currently but not in this PR, which adds this name property instead of a global title.


How to fill a 4DTensor?

Hi, There only 3 dim(arm_compute::Window::DimX, arm_compute::Window::DimY, arm_compute::Window::DimZ), so , how can I fill a 4DTensor with a ptr?

Hi @qfmy ,
You can have a look at the documentation here on how to work with Tensors. For accessing 4th dimension you can use id[3].

Closing issue! Reopen if needed.


Multiple input

Whats the solution if we have multiple paired fastq files which we want to run fastp on them. suppose 120 files named like (s_1_1_qseq.fq  to  s_1_120_qseq.fq)  and their pairs are (s_2_1_qseq.fq to s_2_120_qseq.fq).
how is it possible to do that at once?

You can use some script languages, like shell or python to make a loop, and run fastp one by one.

can you suggest an example ? it will be useful for non-programmers like me

It would be grealy appreciated it you could! Thanks for this awesome tool!

In case someone ever needs this, here is a simple Python script I used for to run fastp one by one. Simply change the input and output directory path in the script and run the script:
import os
import subprocess
Set input and output dirs
input_dir = "INPUT/DIRECTORY"
output_dir = "OUTPUT/DIRECTORY"
os.makedirs(output_dir, exist_ok=True)
Loop over all input files
for filename in os.listdir(input_dir):
if "R1" in filename and filename.endswith(".fastq"):
in1 = os.path.join(input_dir, filename)
out1 = os.path.join(output_dir, filename)
in2 = in1.replace("R1", "R2")
out2 = out1.replace("R1", "R2")
    # Now run fastp command
    if os.path.exists(in2):
        command = f"fastp --in1 {in1} --out1 {out1} --in2 {in2} --out2 {out2} -w 10"
        print(f"Running command: {command}")
        subprocess.run(command, shell=True)
    else:
        print(f"Matching _R2_ file not found for {in1}")
else:
    print(f"{filename} does not include '_R1_' or is not a fastq file")


Fixed numerous broken links

#MMS2019Docathon

@ChrisKibble : Thanks for your contribution! The author, @, has been notified to review your proposed change.

Tagging @aczechowski as pages have no author.

Docs Build status updates of commit 1df2cb3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/1710_Release_Notes.md
:white_check_mark:Succeeded

docs-conceptual/1802_Release_Notes.md
:white_check_mark:Succeeded

sccm-ps/ConfigurationManager/ConfigurationManager.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.

Thanks @ChrisKibble for the contribution! I'll review after the end of the contest.
#hold-off
(reviewers, please don't edit - I'll take care of it.)

@ChrisKibble : Thanks for your contribution! The author, @, has been notified to review your proposed change.

Docs Build status updates of commit 8e1de4f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/1710_Release_Notes.md
:white_check_mark:Succeeded

docs-conceptual/1802_Release_Notes.md
:white_check_mark:Succeeded

sccm-ps/ConfigurationManager/ConfigurationManager.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.

@ChrisKibble : Thanks for your contribution! The author, @, has been notified to review your proposed change.

@aczechowski : Thanks for your contribution! The author, @, has been notified to review your proposed change.

Docs Build status updates of commit 0a1b013:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/1710_Release_Notes.md
:white_check_mark:Succeeded

docs-conceptual/1802_Release_Notes.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.


When can this lib support AC1018?

Recently, I have try to transform the high dwg version to autocad2000, but it seems this lib has some bugs.  Such as some layers' geometries losed or exists bugs when opencadfile().
Is it because the geometrytype is not enough for versions after transform. Can you continue to update the lib??Thank you.

I am thinking about rewriting this library completely to make it more Modern C++ as it stands now, and since it has pretty bad design choices (which leads to memory-leaks, hard error-handling, etc). It's hard to estimate how much will it take since this is not my main project at the moment, and it seems that it won't be.
In near future I will start to commit again into dev branch, it won't be stable of course, but after I will make global refactoring I will also try to extend possible formats with 1 new version of DWG.
Thanks for your interest.

Hi @sandyre,
Is there any progress on adding support of more recent AC file versions?

Hello @rudolfninja . No, unfortunately there is none.
I would like to say that there is https://github.com/nextgis-borsch/lib_opencad repository with latest patches taken from GDAL project trunk, so it should be better t o use instead. API is the same.
Best regards,
sandyre

Thanks. I'll take a look on it


[1Password] ...quick access to main fields: name, password, on-time passwd

Extension
https://www.raycast.com/khasbilegt/1password
Description
A quick way to find and paste username and password
Current behavior:
The main (quick) action ⏎ will open the selected entry in 1Password. Other actions can be viewed by pressing ⌘K:

⇧⌘C Copy Username
⌥⌘C Copy Password
^⌘C Copy One-time Password

Sugested behavior

have custom (quick) actions for the main functions, inline with those in 1Password's Quick Access

⌘⏎  Paste username
⇧⏎ Paste password
⌥⏎ Paste One-time password

have the custom (quick) actions previewed when the modification-key is pressed, as shown in the mockups:
(the mochups should display "Paste" iso "Copy")

default

[⌘] held down

[⇧]  held down

[⌥] held down
Who will benefit from this feature?
All 1Password users that use raycast as interface to access their login credentials.
Anything else?

Check 1Password "Quick Access"
Check Alfred implementation

@raycastbot reopen this issue
Hey, are you aware that you are able to set the primary (return) and secondary(cmd+return) commands as you prefer?
Right now that are no "paste" functions, which you could create an issue to be implemented.


Mismatch of class name in source code and example codes

Hi please help to check！

lin_stack ，or libusb_stack


RPC handler error

The script has an issue when ran with Python 2.7.13
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/local/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/usr/local/lib/python2.7/threading.py", line 754, in run
    self.__target(*self.__args, **self.__kwargs)
  File "nightminer.py", line 648, in _handle_incoming_rpc
    output += '\n  ' + e.reply
TypeError: cannot concatenate 'str' and 'dict' objects

+1

output += '\n  ' + str(e.reply)

Scrypt does not work.
{'params': ['NightMiner/0.1'], 'method': 'mining.subscribe', 'id': 1}   {u'jsonrpc': u'2.0', u'id': 1, u'error': {u'message': u'Procedure not found.', u'code': -32601}}

Sorry, I haven't really paid attention to this in quite some time. Did the stratum protocol change?

Yes, the protocol has changed, now you need to log in and get a job
{"jsonrpc": "2.0", "id": 1, "method": "login", "params": {"login": "", "pass": "", "agent": "NightMiner/0.1"}}
response
{"jsonrpc":"2.0","result":{"job":{"blob":"060681eff5cd05345337affbe243531444b4c9a39f4f3f9f78ec40df35f07191b2d0dc4654b44f000000000e5f94b68a6ac56a5ff1d6b715795a72be98685800c18283264591416e6aa63501","target":"e4a63d00","job_id":"c8b5ea1d-ad7d-4e6a-9241-22c7033a35ba","time_to_live":5},"status":"OK","id":"a010b632-b750-4362-9053-0f69b5e2f84e"},"id":1,"error":null}


RemovedInDjango40Warning: ugettext_lazy() is deprecated

I am getting the following warning for each use of _(...) when used with Django 3.1.3, wagtail 2.11:
RemovedInDjango40Warning: django.utils.translation.ugettext_lazy() is deprecated in favor of django.utils.translation.gettext_lazy()
An easy and obvious fix, PR incoming shortly.

This  is becoming more urgent since wagtailmenus now doesn't work with the latest setup of wagtail 2.16 (using Django 4 by default)

Agreeing with @Crocmagnon.  I tried this package in a project and ended up not making use of it.  When I tried to remove the package form the venv and from INSTALLED_APPS, I got an error that one of the project's migrations is dependent on one of the wagtailmenus migrations (0022).  Since I can't remove wagtailmenus from INSTALLED_APPS because of this migrations dependency, I now have to (artificially) constrain this project to Django 3 when I would otherwise have just upgraded it to 4.

Yes, still very relevant - I see this was fixed in master branch already, would be great to see it in the release.

This was solved on version 3.1.3, thanks for everybody's help!


Support for Azure TLS 1.0/1.1 ends on 31 Octber 2024, Any action required?

Support for Azure TLS 1.0/1.1 ends on 31 Octber 2024.
The storage account of our Company Communicator requires   minimum TLS version  1.0.
Do I need to update the storage account  to be  minimum TLS version 1.2 ?

Hi @ATshirai ,
Thanks for raising the query. We will check and do the needful. No action is needed from your until further notice.


Allow reader/writer endpoints for pools

Experimenting with Reader/Writer endpoints
With this PR, connecting with postgres://sharding_user:sharding_user@localhost:6432/sharded/writer is equivalent to connecting to postgres://sharding_user:sharding_user@localhost:6432/sharded and then setting role to primary before each query.
Connecting with postgres://sharding_user:sharding_user@localhost:6432/sharded/reader is equivalent to connecting to postgres://sharding_user:sharding_user@localhost:6432/sharded and then setting role to replica before each query.
This is useful for clients that maintain their own primary/replica pools but do not have ability ban bad replicas or load balance (e.g. a vanilla Rails 6 app).

Hey,
Try playing with this setting  instead: no code changes required I think.

@levkk What I want to do here is to run a single Pgcat process in front of one primary and N replicas and do special routing using the database string. This would make the switch to Pgcat transparent to the client as it will not need to do any SET role calls after connecting, it will only want to change its connection string.
Setting default_role would work only if I have a dedicated process for each role or if I set default_role to replica and make client changes for the primary role to send SET role to primary after connecting.

Hey,
If you're planning on using the database name to route to different databases, you don't need to make any changes to PgCat. Simply configure the primary as pools.primary and replicas as pools.replicas and route your queries as before. The pools.primary will have one primary configured and the pools.replicas will have several replicas configured which PgCat will load balance queries against. By setting default_role = "replica" on the pools.replicas pool, you'll be able to avoid any confusion regarding routing logic inside the configured pool, but even if you don't I think by default PgCat will load balance across all databases in the configured pool.

I see what mean!.
That's a good idea, sounds like it should work now that we support multi-db.
Also, I was worried about overlaps, like when we have an instance address appear under multiple pools but I think Pgcat only enforces this uniqueness within individual shards  so we should be okay to have one instance appear in two different pools.


[Question] Any plans to port to PyTorch ?

Hi, I was just wondering whether you have some plans to provide a similar library for PyTorch ?
Thanks

Hey, thanks for reaching out! Unfortunately the short answer is no 😞
We put quite a bit of thought into the question of which framework we should build Larq on and decided to go with TensorFlow / Keras over PyTorch.. One of our main goals when choosing a high level abstraction was that we don't want to reinvent the wheel by building our own, but rather want to integrate really well into the code people are already using. We really like the Keras API for its simplicity, but it is still very flexible if you want to build complex architectures or custom training loops. Especially with TensorFlow 2.0 on the horizon, we feel that building Larq on tf.keras will allow us to integrate really well into the TensorFlow ecosystem. Especially using https://www.tensorflow.org/datasets/datasets for reproducibility has been really great for us in the past. We plan to release pretrained and finetunable models in the near future and for us that seemed to be a great fit for Keras.
I know everybody prefers a different framework, but for the moment we try to focus on making Larq work really well with the TensorFlow ecosystem and won't try to make it framework agnostic.
Luckily, it's becoming much easier to move between frameworks these days: https://twitter.com/fchollet/status/1052228463300493312 😉
Larq is currently in its very early stages and we're trying to gather as much feedback from the community as possible. We plan on releasing stable version mid of July. There's a lot of great stuff coming in the next few weeks. What features are you currently missing, or what would help you to adopt Larq for your own work (apart from Larq being written in TensorFlow)?

@lgeiger thanks for the answer ! I see your points and I understand the reasoning.
As far as I understand the features of Larq are those new quantized layers and optimizers which are tested and hopefully will become stable very soon. I thought, maybe, the same work can be rather quickly generalized to pytorch and its ecosystem, to cover other users.
Anyway, I was also wondering what binarization could perform for semantic segmentation tasks etc.

Thanks for the comments

I thought, maybe, the same work can be rather quickly generalized to pytorch and its ecosystem, to cover other users.

I agree, the layers and quantizers can possibly be generalized to pytorch rather quickly. Though our main goal at the moment is to grow the ecosystem around binarized (and extremely quantized) neural networks by also providing pretrained models and "official" implementations of popular papers as well as adding more insights and relevant training metrics. We also plan on developing optimized GPU kernels for faster training. Therefore we are focusing our resources on TensorFlow.

Anyway, I was also wondering what binarization could perform for semantic segmentation tasks etc.

Oh yes, using binarization for segmentation is an interesting field to explore further


Exclude Cache for querystring

What value do I pass excludeCacheFor so that if the language is detected through querystring it's not stored as a cookie? I only see cimode as an example in the docs. Would be nice to expand on this so it's more clear on how to utilize this feature :)

it's to exclude languages not detection modes - that's why the sample has cimode as language -> as you probably do not want to cache that...

Is there a way to exclude caching if it's a querystring value?

no, sorry at time of caching we have no idea what source was used to detect...you would need to write a own override for the cookie detector not doing set cookie if value is in querystring:
https://github.com/i18next/i18next-browser-languageDetector/blob/master/src/browserLookups/cookie.js#L44
adding using: https://github.com/i18next/i18next-browser-languageDetector/blob/master/src/index.js#L43


[Feat]: Workflow for Closing Old Issues

This feature aims to automate the process of managing old issues, ensuring that the repository remains organized and focused on relevant tasks. By automatically closing old issues, it reduces manual overhead for repository maintainers and helps keep the issue tracker tidy and up-to-date.

@Swarnendu0123 please assign me this issue under gssoc

We don't need this.


docs: fix google analytics config and docs

This pull request includes updates to the configuration files for Google Analytics integration. The changes streamline the configuration by removing redundancy and ensuring consistency between documentation and default settings.
Configuration updates:

docs/advanced/html.md: Removed the analytics directive to simplify the configuration for Google Analytics.
jupyter_book/default_config.yml: Moved google_analytics_id out of the analytics section to the main html section for better clarity and consistency.

According to @MortenHannemose, the one in Configuration defaults docs section is correct.
fix jupyter-book/jupyter-book#2194

I don't think we want to change the location of this configuration key, so I'll close this one. I believe that #2194 is now resolved because we've made a new release that unifies the documentation with the actual implementation. Thanks for looking into this and making the PR to try and improve the project 👍


Gtk mac and Linux

For applications that include Gtk and need to run on linux and mac the following .travis.yml code works for me:
    apt:
        packages:
            - xvfb
            - xauth
            - libgtk-3-0
script:
  - if [[ -a .git/shallow ]]; then git fetch --unshallow; fi
  - if [[ `uname` = "Linux" ]]; then TESTCMD="xvfb-run julia"; else TESTCMD="julia"; fi
  - $TESTCMD -e 'Pkg.clone(pwd()); using BinDeps; println(BinDeps.debug("Package")); Pkg.build("Package"); Pkg.test("Package"; coverage=true)'

Maybe you could work that into your package somehow?

This is definitely too specific to find its way into all generated Travis configs, but maybe it could be inserted if the template's requirements contain Gtk. I'll think about that, thanks!

Yea, that's what I mean: if and only if the package requires Gtk and linux then do all that .travis.yml stuff.

I'm not sure if this still applies on 1.0, but looking back on it, it's sufficiently specific that I don't really think it belongs in this package.


GDPR deletion request

As the issue I previously created (#1593) has been ignored, meaning that I still cannot login to delete my account and am still being sent unwanted emails frequently, I am hereby requesting immediate erasure of personal data concerning me according to Article 17 of the GDPR.
My account on CodeTriage is still using my old GitHub username: @jooles. Please delete the entire account and all associated data
I am of the opinion that the requirements set forth in Article 17(1) GDPR are fulfilled. You cannot claim an exception based on Article 17(3) GDPR either, particularly as I am not a public figure.
If I have given consent to the processing of my personal data (e.g. according to Article 6(1) or Article 9(2) GDPR), I am hereby withdrawing said consent for the entire process.
In addition, I am objecting to the processing of personal data concerning me (which includes profiling), according to Article 21 GDPR. I request that you restrict the processing of the data concerning me pending the verification whether your legitimate grounds override mine, pursuant to Art. 18(1)(d) GDPR.
If you have made the aforementioned data public, you are obliged pursuant to Article 17(2) GDPR to take all reasonable steps to inform other controllers, including search engine operators, who process the personal data listed above, that I have requested the erasure of all links, copies or replications. This applies not only to exact copies of the data concerned, but also to those from which information contained in the data concerned can be derived.
In case you have disclosed the affected personal data to third parties, you have to communicate my request for erasure of the affected personal data, as well as any references to it, to each recipient as laid down in Article 19 GDPR. Please also inform me about those recipients.
If you object to the requested erasure, you have to justify that to me.
My request explicitly includes any other services and companies for which you are the controller as defined by Article 4(7) GDPR.
As laid down in Article 12(3) GDPR, you have to confirm the erasure to me without undue delay and in any event within one month of receipt of the request.
Thank you in advance.

I'm unable to find jooles but I did find a Jooles I can't confirm that's you from public information (it's not tied to your github) so i'll send you an email shortly. Reply to that and I can delete your account.

Email replied to and I've been assured that the data has been deleted (which is good enough for me 🙂)


Modal lookup for class function

Hi Team,
How can we do a modal lookup for a stub function defined within a class?
I am referring to your HuggingFace batch inference example - https://modal.com/docs/guide/ex/batch_inference_using_huggingface
Any help is appreciated.
Thanks!

I believe you can look it up using ClassName.function_name

Thanks @erikbern this works!


[HCIBox] Resource bridge fails to deploy

Resource bridge fails with a timeout error when generating the kubeconfig file for the arcappliance.
Arcappliance logs indicate a timeout generating the kubeconfig

I'm stuck with this issue over multiple deployment attempts.  Do you need any data / logs?
ERROR: [Errno 2] No such file or directory: 'C:\Users\Administrator.jumpstart\.kube\config'


Update tests deps to latest versions and unpin deps

#110 shows that there are some old dependencies, so the idea is:

Update all tests dependencies (pytest and others) to the latest versions
Unpin all the versions (since not updated libraries are prone to security vulnerabilities)

Done in https://github.com/scrapinghub/python-scrapinghub/pull/166.


Add classifiers to setup.py

Without language classifiers in setup.py this project gets marked as not supporting Python 3 when using a tool like caniusepython3.com to check Python 3 compatibility. I've added the basic classifiers, the most important ones being the language ones.

Coverage remained the same at 100.0% when pulling fd01b1f7b6bcea88967ef3d6890d7967032a9d0a on dsanders11:patch-1 into 3d8792e4a9d4ef29eec316e33a35af02b932f167 on glyph:master.

Thanks for noticing this oversight; looking forward to updating this in the next release.


fix(web): use abort controller to cancel API requests on timeout

Describe your changes
Replace the utils "timeout" code with more robust timeout that cancels the underlying request:
https://pins-ds.atlassian.net/browse/APPLICS-1068
Best reviewed with the "hide whitespace" option, as there is a shift of nesting.
Useful information to review or test

Type of change 🧩

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please explain in the description section above)

Checklist before requesting a review

[ ] I have performed a self-review of my own code
[ ] I have double checked this work does not include any hardcoded secrets or passwords
[ ] I have made corresponding changes to the documentation
[ ] I have provided details on how I have tested my code
[ ] I have referenced the ticket number above
[ ] I have provided a description of the ticket
[ ] I have included unit tests to cover any testable code changes

:tada: This PR is included in version 2.39.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.33.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Downloads wrong title

Sometimes the wrong titles are downloaded. Example: If you try to download
Deine Freunde - Mecker it downloades actually Deine Freunde - keine Märchen.
Not such a big deal as these songs both belong to the same album. It is a kids album. BUT the same happens for songs with explicit content which is not so nice if you try to download songs for kids.

I think this happens because Spotify Downloader runs the following search query on YouTube:
https://www.youtube.com/results?search_query=Deine+Freunde+-+Mecker+lyrics
And as you can see, the song "Mecker" isn't the top result. You could consider specifying the argument -m (or --manual). Then Spotify Downloader will show you a list of matching videos and allows you to choose the correct one.


Fix horizontal scroll issue

Description

I noticed a horizontal scroll on the webpage (caused by the "search/register/manage" selector).
Using the selector creates an empty body on the right, causing horizontal scroll (see screenshot, changed bg to red).
Not a big deal ofc, but the fix improves ux.

Screenshots

Hi thanks for your submission, going to close this as I can not reproduce now. Feel free to re-open if it's still an issue and we'll investigate further.


Logo Does Not Redirect to Home Page

Describe the bug
The logo on the website does not redirect to the home page when clicked. Typically, clicking on a website’s logo should lead the user back to the homepage, but this feature is missing or not functioning properly on this site.
To Reproduce
Steps to reproduce the behavior:

Go to any page other than the home page.
Click on the logo in the header.
Observe that the logo does not redirect to the homepage as expected.

Expected behavior
Clicking the logo should redirect the user to the homepage from any other page on the website.
Screenshots
https://github.com/user-attachments/assets/33ad2207-c169-4e0b-98bc-7914d857e61c
Additional context
I would like to fix this issue to improve the user experience. Please assign this issue to me, and add the labels: hacktoberfest-accepted, gssoc-ext. Thank you!

there is only an issue for the changing the logo it doesn't mention that it will fix this bug.

@ANSHIKA-26 I can do that logo-->home page, please assign me


feat: Add support for Base.iterate and Base.startswith.

Fix #35

Is that an error that my PR added?

Looks like not --- the nightly failures seem unrelated and are also failing in integration in  https://github.com/tshort/StaticCompiler.jl/pull/95 and https://github.com/tshort/StaticCompiler.jl/pull/96
The one thing I wasn't sure about is the mac failure on 1.8, but pretty sure that's unrelated too


Review technologies cheatsheet

Description of the task:
Review the technologies cheatsheet before it is shared with the blood bionetwork
Deadline: Friday 17th of February?
cheatsheet
Acceptance criteria for the task:

[ ] check existing technologies

[x] CITE-seq
[x] DroNc-seq
[ ] MARS-seq
[ ] inDrop
[ ] Drop-seq
[ ] Fluidigm C1
[ ] sci-CAR
[ ] GexScope

[x] add smart-seq3

Wranglers to check technologies if capacity allows - Please check the boxes after checking

This is not important to do right now! Closing.