THE ONE PROBE missing mods?

Hello,
I was trying out this mod and minecraft told me this, The One Probe is missing mods it depends on. Include the following mods or remove The One Probe. Compatlayer 0.1.6 or above.
Thanks

yes, you need compatlayer. Did you install that?


completing-read's initial field is off by one when using selectrum

Will try and get to writing a PR but here is the repro for safe keeping and maybe someone beats me to it,
(completing-read "Test: " '("0123456789" "0123456") nil nil '("0123456789" . 4))

It is expected, based on non-selectrum behavior, that the cursor would be positioned over the 4 (zero-indexed) but with selectrum it is positioned over the 3. That is the 4th character but the index is 3.

Ah, the problem is passing initial-input to read-from-minibuffer inside of selectrum--read. the completing-read docs explicitly say that the initial-input argument is different from the read-from-minibuffer in that the former is 0-indexed, and the latter is 1-indexed. It also says that initial-value is deprecated but the alternative behavior is kinda bogus anyways requiring a yank with M-n...

Thanks, I wasn't even aware of that "feature", where is it used? We could simply insert the string manually of course but maybe this can wait as we might change the internal approach and wrapping default completion instead, see #481

Should be fixed by #530

Thank you! I'll give it a shot.

This thread is being closed automatically by Tidier because it is labeled with "waiting on response" and has not seen any activity for 90 days. But don't worry—if you have any information that might advance the discussion, leave a comment and I will be happy to reopen the thread :)


Add known arguments to avatar filter

Ticket: #
Reviewer: @
Issue
Known arguments for avatar (size, default) are not passed to the filter, so they are missed by the functions hooked into the filter (for example, returning an image of the wrong size).
Solution
Add known args  to filter method.
Impact
Small, and bringing behaviour up to expectation.

Coverage increased (+0.002%) to 93.41% when pulling 1961d026e2d92c2efee0c2c95cf5b3eb49318cad on xavivars:patch-3 into ba10f09a3cccb38619da2012bd9d88bb724bcb2f on timber:master.

Lookin' good, thanks @xavivars !


Implementation of Context-Level Type Inference

Details
Key points od Context-Level Inference

View type inference as a problem-solving process, incrementally increasing information in the context.
Represents context as an ordered list of type varaible declarations and definitions.
Unification maintains context while solving type equations.
Uses '#' separators to mark "local" sections in the context for handling let-polymorphism.
"Optimist's Lemma" to decompose and sequentially solve sub-problems

Formal Representation

Unification ($\alpha$ and $\beta$ are type variables, $\tau$ is a type):
$\alpha \equiv \beta \quad|\quad \alpha \equiv \tau$

Type Inference rule ($\lambda$-abstraction):
$\frac{\Gamma, x:\alpha \vdash t : \beta}{\Gamma \vdash \lambda x.t : \alpha \rightarrow \beta}$

Let-polymorphism
$\frac{\Gamma \vdash t : \sigma \quad \Gamma, x:\sigma \vdash u : \tau}{\Gamma \vdash \text{let } x = t \text{ in } u : \tau}$

Examples
package main

import "fmt"

// Type inference in variable declaration
var x = 42 // inferred as int

// Function with type inference
func add(a, b int) int {
    return a + b
}

// Polymorphism using interfaces
type Printable interface {
    Print()
}

type MyType struct {
    value string
}

func (m MyType) Print() {
    fmt.Println(m.value)
}

func main() {
    // Type inference in slice initialization
    numbers := []int{1, 2, 3, 4, 5}

    // Type inference in range-based loop
    for i, v := range numbers {
        fmt.Printf("Index: %d, Value: %d\n", i, v)
    }

    // Polymorphism through interfaces
    var p Printable = MyType{"Hello, World!"}
    p.Print()
}

not needed.

reopeded due to the inferring an params type


Error messages from cmd after compiling?

Hi Michael,
After a successful compiling (with -static and -march=native added) under WIN with just two warnings, a first test from cmd
shows nearly two thousands of error lines about invalid attack tables for Bishop and Rook.
After this MisterQueen can still be started with the uci command and reacts to 'go infinite' with b1c3 (no pv, no info though)
Haven't tried yet if it might play a game under a GUI despite the error messages in the beginning.
Any idea?
debug info from a logging tool
0.000: - Starting server: MisterQueen.exe
0.031: - Priority class set to normal
0.031: - Thread priority set to normal
0.046: < ERROR: invalid ATTACK_BISHOP table
...
0.280: < ERROR: invalid ATTACK_BISHOP table
0.280: < ERROR: invalid ATTACK_ROOK table
...
0.670: < ERROR: invalid ATTACK_ROOK table
2.449: > uci
2.449: < id name Mister Queen
2.449: < id author Michael Fogleman
2.449: < uciok
5.460: > ucinewgame
7.004: > isready
7.004: < readyok
11.247: > go infinite
12.246: < bestmove b1c3

$ make
Creating directories
Beginning release build
Compiling: src/bb.c -> build/release/bb.o
Compiling: src/bk.c -> build/release/bk.o
Compiling: src/board.c -> build/release/board.o
src/board.c: In function 'board_print':
src/board.c:234:19: warning: 'c' may be used uninitialized in this function [-Wmaybe-uninitialized]
  234 |                 c |= 0x20;
      |                 ~~^~~~~~~
Compiling: src/book.c -> build/release/book.o
Compiling: src/deps/tinycthread/tinycthread.c -> build/release/deps/tinycthread/tinycthread.o
Compiling: src/eval.c -> build/release/eval.o
Compiling: src/gen.c -> build/release/gen.o
Compiling: src/main.c -> build/release/main.o
Compiling: src/move.c -> build/release/move.o
src/move.c: In function 'score_move':
src/move.c:162:9: warning: variable 'piece_material' set but not used [-Wunused-but-set-variable]
  162 |     int piece_material = 0;
      |         ^~~~~~~~~~~~~~
Compiling: src/opening.c -> build/release/opening.o
Compiling: src/perft.c -> build/release/perft.o
Compiling: src/search.c -> build/release/search.o
Compiling: src/table.c -> build/release/table.o
Compiling: src/uci.c -> build/release/uci.o
Compiling: src/util.c -> build/release/util.o
Linking: bin/release/main
Making symlink: main -> bin/release/main

Guenther (maintainer of the RWBC XB/UCI chronology)

This might be your problem:
https://twitter.com/WEREMSOFT/status/1286317465941823488

Ok, the problem was that wasm has diferent sizes for data types. There was an overflow issue. The solution was to change the following line 4 in bb.h:
#define BIT(sq) (1L << (sq))
to
#define BIT(sq) (1LL << (sq))

Hooray! Thanks for the quick hint.
Finally I can add MisterQueen to the XB/UCI chronology, except you won't like to be there?
https://rwbc-chess.de/
https://docs.google.com/spreadsheets/d/1GXoy3lGhdKPJbatdw2_2dhWT3TkpthPcNtHs51MQydM
BTW it would be nice if a version number would exist. Ofc I can still add the last commit date to the binary.
 :)

Limitations
Unaware of draw by repetition.

[Event "CuteChess 1.20 dev"]
[Site "RWBC-CAPPUCCINO"]
[Date "2020.10.10"]
[Round "1"]
[White "MisterQueen_2020-04-08"]
[Black "Stash_122-64"]
[Result "1/2-1/2"]
[ECO "B30"]
[GameDuration "00:03:30"]
[GameEndTime "2020-10-10T22:53:38.155 Mitteleuropäische Sommerzeit"]
[GameStartTime "2020-10-10T22:50:08.019 Mitteleuropäische Sommerzeit"]
[Opening "Sicilian defense"]
[PlyCount "64"]
[TimeControl "40/120"]

1. e4 {book} c5 {book}
2. Nf3 {book} Nc6 {book}
3. Be2 {book} g6 {book}
4. Bb5 {+0.75/10 4.01} Nd4 {-0.21/10 3.23}
5. Nxd4 {+0.65/10 4.01} cxd4 {-0.17/10 3.23}
6. O-O {+0.65/10 4.00} a6 {-0.08/10 3.23}
7. Ba4 {+0.75/11 4.01} e5 {-0.01/10 3.24}
8. d3 {+0.65/10 4.00} Nf6 {-0.03/9 3.23}
9. f4 {+0.85/10 4.01} Bd6 {-0.22/11 3.23}
10. Nd2 {+0.90/10 4.00} b5 {-0.40/11 3.23}
11. Bb3 {+0.90/10 4.00} exf4 {-0.35/10 3.23}
12. Nf3 {+0.90/9 4.00} Bc5 {-0.31/9 3.23}
13. Bxf4 {+1.10/9 4.00} d6 {-0.28/8 3.24}
14. Nh4 {+1.60/8 4.00} Bg4 {-0.98/8 3.24}
15. Qc1 {+1.80/9 4.00} Nd7 {-1.76/10 3.24}
16. Bxf7+ {+2.75/10 4.00} Kxf7 {-5.11/12 3.23}
17. Bg5+ {+4.10/11 4.00} Kg7 {-5.73/12 3.23}
18. Bxd8 {+4.05/10 4.01} Rhxd8 {-5.86/11 3.24}
19. Qg5 {+4.00/10 4.00} Ne5 {-6.02/11 3.24}
20. h3 {+4.00/9 4.06} Bd7 {-5.98/11 3.23}
21. Nf3 {+4.00/9 4.00} Nc6 {-5.43/9 3.23}
22. Qd5 {+4.10/9 4.01} h6 {-4.70/8 3.24}
23. Rae1 {+4.15/8 4.00} a5 {-4.71/9 3.25}
24. a3 {+4.15/9 4.03} Rac8 {-4.83/9 3.23}
25. Rd1 {+4.10/9 4.01} Ne7 {-4.80/10 3.24}
26. Qb7 {+4.05/10 4.00} Ra8 {-3.77/10 3.24}
27. Qc7 {+4.10/8 4.01} Nc6 {-2.97/11 3.25}
28. b4 {+2.45/10 4.01} Rac8 {-2.92/12 3.24}
29. Qb7 {+2.90/12 4.00} Rb8 {-2.93/13 3.24}
30. Qc7 {+2.90/12 4.00} Rbc8 {-2.90/12 3.25}
31. Qb7 {+2.90/12 4.00} Rb8 {-2.92/13 3.25}
32. Qc7 {+2.90/12 4.01} Rbc8 {0.00/15 3.24}
{Draw by 3-fold repetition}
1/2-1/2


Eol certificates (EXPOSUREAPP-14790)

Subtask

A wish from my personal site: The PRs opened in the Android repo tend to only include a link to a JIRA ticket, which is not accessible by the community.
As we already discussed way back in https://github.com/corona-warn-app/cwa-documentation/issues/402, this is not optimal for an Open-Source project.
So my wish: Please continue to provide descriptions for PRs, as there are still people reading here who don't have access to JIRA.
cc @dsarkar

A wish from my personal site: The PRs opened in the Android repo tend to only include a link to a JIRA ticket, which is not accessible by the community. As we already discussed way back in corona-warn-app/cwa-documentation#402, this is not optimal for an Open-Source project. So my wish: Please continue to provide descriptions for PRs, as there are still people reading here who don't have access to JIRA.
cc @dsarkar

@Ein-Tim
EOL stands for End of Life.
The App will simply disable some features at EOL and some feature will continue to work after EOL (Date). When you see EOL - feature name in a PR it means that this PR is bring is applying a flag on this feature which will take effect at EOL


Migrate NUnit3 project to support .NET Core

Migrated the NUnit3 project to .NET Standard. We depend on different NUnit versions for different frameworks:

3.0.1 for .NET Framework 4.5
3.7.0 for .NET Standard 1.5

Everything went smoothly and no important changes are present. Most of the changes are related to changing our build scripts to run NUnit3 tests using dotnet test and later uploading the results to AppVeyor. Also I deleted NUnit.Console v3 runner from the repository as we don't longer use it.
@moodmosaic @adamchester Looking forward to your review. That is the last important migration to .NET Standard (we have only Idioms and F# projects left and they are blocked by dependencies). Hope that will cheer you if you are tired from such PRs 😃

@moodmosaic If you have time in upcoming days, could you please review this one? Changes are really minor (don't scary 35 changed files - about 30 of them are removal of NUnit3 console runner) and that is the last major library we need .NET Core support for. I want to make a tweet that we almost fully support .Net Core in the private feed (so people could try and early use), however need this one to proceed further..

@moodmosaic Thank you! 🥇


Unable to Save Some Category in Magento2

When I am trying to save some category then getting this error and category is not being saved..
For example we are trying to save Anchor to Yes/No.
Warning: ltrim() expects parameter 1 to be string, array given in /var/www/html/eoutlet/public_html/app/code/Magento/Catalog/Model/Category/FileInfo.php on line 102
My Magento Version : 2.2.5
If anyone also faced this issues, then please revert me?
Thanks

i am facing same issue can anyone help me


The side navbar with a normal top navbar interfere when collapsing and expanding

When the screen is small enough for the button to collapse or uncollapse to become available, clicking on the uncollapse button for the side navbar (which is now at the top) also uncollapses the original top navbar. But uncollapsing the top navbar does not uncollapse the side navbar.

I don't understand what you mean, sorry. Do you have two navbars?

Yeah, i have the normal top sidebar that is from bootstrap itself (link ) and then for certain pages i want your side navbar. But when both are in use and the width of the device is small, pressing the uncollapse button of your side navbar, also uncollapses the normal sidebar. I hope this made clear what i meant?

It's not designed to work with a second navbar. They'll end up both collapsing to the top. I would guess start by trying to change the data-target ID though.

Fiddling around with the data-target fixed it indeed, thanks for pointing me in the direction i needed to look :)


TBB path issue on Windows

Since the last release my CI tests for nutpie fail on windows. If my remote debugging is right, this is due to the changes introduced in #118. This adds some code that is executed in __init__, ie right at import time, where it calls os.add_dll_directory with contents of the ~/.bridgestan directory. But if this runs on a fresh install, where stan was not downloaded already, this fails with a FileNotFound error.
Some logs from the CI:
https://github.com/pymc-devs/nutpie/actions/runs/5419095619/jobs/9851843966#step:8:335
If my interpretation of this is correct, this could be fixed by delaying the call to _windows_path_setup until after bridgestan is downloaded, ie by setting a flag to False at import time, and checking that flag each time a model is compiled. (strictly speaking it would be enough to check when a shared lib is loaded, but if, say, someone would want to load the library using a different interface, that interface would then have to do that...)

I believe your diagnosis is correct. I have two thoughts:

Can we think of a reasonable way to test this behavior (it didn’t show up in our CI since we set $BRIDGESTAN, and I think we have to do that since the code will drift from the released versions)
I think adding it at load time is the more correct thing to do, since a model will (presumably) be loaded more times than it is compiled. If you compile, close python, re open, and then load, that needs to work.

On:

but if, say, someone would want to load the library using a different interface, that interface would then have to do that...

I believe that the dll_load_path is specific to Python as an additional security feature. To my knowledge $PATH is used elsewhere, so I don’t believe this would be an issue?

I believe that the dll_load_path is specific to Python as an additional security feature. To my knowledge $PATH is used elsewhere, so I don’t believe this would be an issue?

I'll try with the branch from the PR. If this is in fact an issue, I guess we could also expose the function? ie as a verify_library_path or so, that only does something on windows?.


Missing next & previous icons in contents view

In Volto contents view, with a big list of items (to force pagination), you can see 'next' and 'previous' icons to move through pages, but icons are not displayed/loading  :(

@robdayz Just noticed that, maybe semantic-ui icons are not loading inside the Menu. We can render using our Icon component.

@robdayz see #1693

Merged! Thanks @nileshgulia1


Improvement - Documentation for Transport

The documentation for Transport could be clarified a bit.  It's not immediately clear what the difference between schedule() and scheduleOnce() is other than scheduleOnce() will remove the scheduled event from the timeline after it is fired.
Also, I was a bit confused about the time argument.  I had tried using a future time that would have been a small bit of time away from the current time (e.g. current transport time was 12.5 and I scheduled an event for 13.0), but the event didn't fire until many seconds after it was expected.  However, when I used a now-relative time (+0.5) the event fired when I expected.  I was under the assumption that an event could be scheduled for a specific time in seconds.

Thanks for the comment. Timing in Tone is still a little complicated. There are two clock sources to manage, the Transport clock, (which is seekable, pausable, restartable and which the docs usually refer to as the "timeline"), and the Web Audio clock (which counts up from 0 and doesn't stop). This is definitely confusing and could use some more documentation, so i appreciate the issue.
Maybe the docs should refer to one as Time and the other as TimelineTime or something like that to clarify when one is used over the other. I think updating the Transport and Event Classes wikis to make this clear would be a good thing too.
It's possible that your issue is that the Web Audio clock was at 12.5, but the Transport's timeline was at 0. And since schedule is relative to the Transport's clock, if you put in a value of 13 and then started the Transport, it would take 13 seconds before the event was fired.
As far as schedule vs scheduleOnce, they are pretty much identical, except that, as you said, scheduleOnce will be removed after it's invoked. so it might be useful for events which you don't want to repeat or be recorded along the Transport's timeline. schedule is much more useful than scheduleOnce


Scala Native support

Experimental Scala Native support requires Scala 2.11; sn has no sbt tests support, here is provided a workaround.

[x] fix commented out test cases
[x] ci

Blocked by https://github.com/scala-native/scala-native/issues/571

Project is no longer maintained.


Incorrect/unhelpful "error parsing lakefile" from print-paths

In a file I get
`/home/sebastian/.elan/toolchains/leanprover--lean4---nightly-2022-08-10/bin/lake print-paths Init` failed:

stderr:
Error parsing '././lakefile.lean'.  Please restart the lean server after fixing the Lake configuration file.

but going back to the lakefile, it's clear that the file itself parses and processes just fine. The real error is revealed only on lake build
error: no such file or directory (error code: 2)
  file: ./https://github.com/JLimperg/aesop/lakefile.lean

at which point I realize I wrote
require aesop from "https://github.com/JLimperg/aesop"

I would expect print-paths to show the precise error from above as well.

This is actually as intended as part of @gebner's #52. Note this statement from the PR: "In this fallback mode, all files except lakefile.lean immediately fail with an error to remind the user that lake serve must be restarted after fixing lakefile.lean."

@Kha I agree that the message can be confusing. However, as @gebner was responsible for this behavior (and seems to have specifically intended it), I want to hear his input before touching it.

I certainly have no objections to changing the error message.

should we store the lakefile loading error in LAKE_INVALID_CONFIG so that we can show it instead of this generic message?

:+1:

For the latter part, should we store the lakefile loading error in LAKE_INVALID_CONFIG so that we can show it instead of this generic message?

What error are we talking about here? It does not seem feasible to store the entire stderr of either the configuration file elaboration or Lake itself in the environment variable.

I just ran into this again.

It does not seem feasible to store the entire stderr of either the configuration file elaboration or Lake itself in the environment variable.

On Windows the limit is 32K, on Linux you can store several megabytes in an environment variable.  Passing (the last couple lines of) the error message should be easily possible.

@gebner

Passing (the last couple lines of) the error message should be easily possible.

Yeah, this seems reasonable. The only problem right now is that logs are currently printed directly to stderr and not stored, so printPaths does not currently have a way to retrieve the log lines and store them in the variable.

Just linking to another appearance of this issue: https://leanprover.zulipchat.com/#narrow/stream/287929-mathlib4/topic/how.20to.20include.20mathlib4.20in.20the.20lakefile.3F/near/306763490


CircuitBreaker in EventHub sdk consumer ?

Query/Question
I would like to implement CircuitBreaker pattern in EventHub consumer. Does the current SKD supports this functionality implicitly ? For example, consumer consumes messages and sends data to external API, if the external API server is down, consumer has to stop consuming messages. Is there any Listener or Flag mechanism which indirectly informs the consumer to halt consuming messages until further notice (CircuitBreaker is CLOSED) .
Why is this not a Bug or a feature Request?
This is a common scenario, i believe Azure development team would have thought about it and implemented it in SKD.
Setup (please complete the following information if applicable):

OS: Windows10
IDE : IntelliJ
Version of the Library used

        <dependency>
            <groupId>com.microsoft.azure</groupId>
            <artifactId>azure-eventhubs</artifactId>
            <version>2.2.0</version>
        </dependency>
        <dependency>
            <groupId>com.microsoft.azure</groupId>
            <artifactId>azure-eventhubs-eph</artifactId>
            <version>2.4.0</version>
        </dependency>

Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Query Added
[x] Setup information Added

@serkantkaraca or @JamesBirdsall - could you please provide any insights into how this can be accomplished in Event Hubs SDK 2.2.0?

If you're using Event Processor Host, then don't return from onEvents until the downstream dependency is back and you are able to finish processing the batch. If you do return, then EPH will move on to the next batch for that partition and there's no way to prevent that. The only thing that can happen while waiting is that the owning host might lose the lease on the partition -- and since you haven't checkpointed yet, the new owning host will get the same batch of messages again, encounter the same problem with the downstream dependency, and go into the same wait state in your code.

@kumarrajnumber Does this answer your question?

Yes, thanks, please close this issue.


cannot import name 'KumexBaseRestApi'

Installed using pip, then ran this code:
from kucoin_futures.client import Market
client = Market(url='https://api-futures.kucoin.io')
klines = client.get_ticker("XBTUSDM")
print(klines)
Then encountered this error:
Traceback (most recent call last):
File "futures.py", line 1, in
from kucoin_futures.client import Market
File "/usr/local/lib/python3.6/dist-packages/kucoin_futures/client.py", line 4, in
from kucoin_futures.ws_token.token import GetToken
File "/usr/local/lib/python3.6/dist-packages/kucoin_futures/ws_token/token.py", line 1, in
from kucoin_futures.base_request.base_request import KumexBaseRestApi
ImportError: cannot import name 'KumexBaseRestApi'

problem was in token.py

hello,please try again. I find the issue is fixed.

problem was in token.py

issue is fixed.


add ldap ping feature

Coverage decreased (-0.7%) to 50.674% when pulling<PHONE_NUMBER>23f3321f0835e0efb7a03e90b09f9e on yhua123:configuration into ce0a44010ddf02aebcb7078d89d1b57b6e547baa on vmware:configuration.

Would be better if we can also verify other options in this api?

Thanks for your suggestion.
For my design, this feature take minimum options, focus on verify LDAP service on server side.
Other parameters configured by customer, plan implement in new feature-search.
Reason: 1) goldap.search need these parameters
2) reuse code for verify
From: Daniel Jiang<EMAIL_ADDRESS>Sent: Monday, January 09, 2017 11:06 PM
To: vmware/harbor
Cc: Yong Hua (c); Author
Subject: Re: [vmware/harbor] add ldap ping feature (#1299)
Would be better if we can also verify other options in this api?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_vmware_harbor_pull_1299-23issuecomment-2D271307058&d=DwMCaQ&c=uilaK90D4TOVoH58JNXRgQ&r=mf9f1i0xfA5UE1sFgGnwrA&m=vA_MoBh2WAP4kNPEefzOEJE2ocHijui8CpzbfM09gvU&s=ALtbXyDF8rd0A50DhK8y6PrUbDx6-_xyU6WE_8qY9dM&e=, or mute the threadhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ASRzrVaLZQe9ZjhwdECv4dZTuE8-5FQqMeks5rQkzagaJpZM4LeHkS&d=DwMCaQ&c=uilaK90D4TOVoH58JNXRgQ&r=mf9f1i0xfA5UE1sFgGnwrA&m=vA_MoBh2WAP4kNPEefzOEJE2ocHijui8CpzbfM09gvU&s=Lyzd7my5CUUfA5UHFNXl45zHMKENklZ9t8W_bUMUVzE&e=.

Coverage decreased (-0.7%) to 50.674% when pulling 996c4163c21c22566a417ba418fa811c8721c450 on yhua123:configuration into ce0a44010ddf02aebcb7078d89d1b57b6e547baa on vmware:configuration.

Coverage decreased (-0.7%) to 50.674% when pulling cb4e6f217becef29570dcce5630c32a613f24b0a on yhua123:configuration into ce0a44010ddf02aebcb7078d89d1b57b6e547baa on vmware:configuration.

Coverage decreased (-0.7%) to 50.674% when pulling<PHONE_NUMBER>8f4c8bb7ed3e2789fd4ef081a36107 on yhua123:configuration into ce0a44010ddf02aebcb7078d89d1b57b6e547baa on vmware:configuration.

@yhua123, I think that makes sense, but as per our experience, users often make mistake setting up the scope and other parms, IMO the "test connection" should verify as much as possible to help user avoid such cases.

Coverage decreased (-0.7%) to 50.653% when pulling ae6027531e708da66fbdc889b6b0e754ed9670f1 on yhua123:configuration into ce0a44010ddf02aebcb7078d89d1b57b6e547baa on vmware:configuration.

Coverage decreased (-0.7%) to 50.653% when pulling 7fbe811394c3fcdc2fdf2f3d37a3c75a018cb039 on yhua123:configuration into ce0a44010ddf02aebcb7078d89d1b57b6e547baa on vmware:configuration.


openjdk.mk: make MEMORY_SIZE computation portable

Fixes non-portable (bash specific) code causing errors in log on some systems (ubuntu):
...
18:43:25  /bin/sh: 1: [[: not found
18:43:25  /bin/sh: 1: [[: not found
18:43:25  expr: syntax error: unexpected argument '1024'
18:43:25  /bin/sh: 1: [: Illegal number:
18:43:25  expr: syntax error: unexpected argument '2048'
18:43:25  expr: syntax error: missing argument after '>'
...

testing:
linux_x86-64 OK

sparcv9_solaris JDK 8: https://ci.adoptium.net/job/Grinder/10132
x86-64_windows JDK 21: https://ci.adoptium.net/job/Grinder/10133
Also check a couple other platforms that often have different versions of tools installed ( make / bash )

testing:
linux_x86-64 OK

This is the same one with the error message and use the branch openjdk-hotspot-test, not the openjdk-memsize-fix

testing:
linux_x86-64 OK

This is the same one with the error message and use the branch openjdk-hotspot-test, not the openjdk-memsize-fix

Oh, you are right, I have accidentally used link to to grinder run with error twice.
Testing supposed to link this one:
https://ci.adoptium.net/view/Test_grinder/job/Grinder/10097/
I will update description

sparcv9_solaris JDK 8: https://ci.adoptium.net/job/Grinder/10132 x86-64_windows JDK 21: https://ci.adoptium.net/job/Grinder/10133
Also check a couple other platforms that often have different versions of tools installed ( make / bash )

I have only ran linux since modified code is in:
ifeq ($(OS),Linux)
...
endif

but probably better to test other systems anyway


[RFC]: Add @stdlib/iter/until-each

Description
This RFC proposes adding an iterator utility to invoke a function for each iterated value until a predicate function returns true.
This is the iterator equivalent of @stdlib/utils/until-each.
Package: @stdlib/iter/until-each
Alias: iterUntilEach
Related Issues
None.
Questions
No.
Other
No.
Checklist

[X] I have read and understood the Code of Conduct.
[X] Searched for existing issues and pull requests.
[X] The issue name begins with RFC:.

@kgryte @Planeshifter I'd like to work on this issue, can you please assign it to me ?

Thanks for your interest in working on this package, @JawHawk. Just assigned you. Looking forward to your contribution to stdlib! :rocket:


Feature/graceful shutdown

Description of the Change
Adds graceful shutdown for iroha daemon.

Benefits

Better shutdown management: closing grpc connections, database connections and so on.
Possible Drawbacks

None.

At the moment shutdown() itself does not unblock waiting because signal handler works in the same thread as wait(). Your approach will work after https://github.com/hyperledger/iroha/pull/981 will be merged.

Sorry for wrong merge, this pr is still open.


Video Reality – started

Worked with @jv776 @DaoGatech to get video reality on web browsers

Okay that actually makes a lot of sense. I'm not sure why I thought an iframe was necessary

The detectrtc.js library you found seems to be a bit heavy for our use case. Perhaps it's as simple as checking for the existence of navigator.mediaDevices.getUserMedia. That should work, right?

You're right, I can add a check that the document actually exists. I was thinking it might also be good to check if the DOM exists before registering the LiveVideoRealityLoader (that way Argon won't even try to use the LiveVideoRealityLoader in non-DOM environments).

I was thinking it might also be good to check if the DOM exists before registering the LiveVideoRealityLoader (that way Argon won't even try to use the LiveVideoRealityLoader in non-DOM environments).

No, don't do that. The LIveVideoRealityLoader is used in argon-app, which is a non-DOM environment.

No, don't do that. The LIveVideoRealityLoader is used in argon-app, which is a non-DOM environment.

Okay. I'll just add the check to the constructor.

The detectrtc.js library you found seems to be a bit heavy for our use case. Perhaps it's as simple as checking for the existence of navigator.mediaDevices.getUserMedia. That should work, right?

I agree the DetectRTC library is pretty heavy and I'm not sure that I want to use it. The issue with testing the existence of getUserMedia is that it might exist but not actually provide any useful functionality. For example, on my desktop the function exists, but since there are no webcams or microphones on my desktop I can't get any useful MediaStream objects from it.
So really there are two different things we need to test for: does the browser provide an implementation of getUserMedia, and, if it does, does the hardware actually have any cameras available. The first one is easy to test but the second one seems a little more complicated. There's also the issue that even if a webcam exists, the user might not give the app permission to use it, so getUserMedia will not return a useful MediaStream in that case either.

Why was this jspmPackage flag removed?

I think I updated my jspm installation at some point during development, which might explain why the entire file was overwritten. I can add the flag back in


Add support for "collectionType" in redis-sink

As a developer, I'd like to port collectionType support from XD to redis-sink. This capability allows pinning the collection type to a variety of data structures and not just List, which is the default.

Name of the sink is redis-pubsub should change to just redis

This issue was moved to spring-cloud-stream-app-starters/app-starters-release#37


Issues with File Upload and Saving in AnyField with Link::class Relation

Description:
I am experiencing difficulties with uploading and saving files using the AnyField configured for a relation with Link::class. When attempting to upload a file through this field, I consistently receive the error message: "key for class 'SilverStripe\AnyField\Extensions\ModalController' is required". Additionally, when I select a file from existing files and then close the modal or save the overarching DataObject, the file fails to be saved. This issue persistently prevents the proper use of this feature.
Question:
Is this behavior indicative of a bug in the module, or could it be a result of some oversight in my configuration? Do you need further information in reproducing this?
Here is a part of my current code:
class HeroSlide extends DataObject
{

    private static $db = [
        'SortOrder' => 'Int',
        'Title' => 'Text',
    ];

    private static $has_one = [
        'PrimaryButton' => Link::class,
        'SecondaryButton' => Link::class,
    ];

    public function getCMSFields()
    {
        $fields = parent::getCMSFields();

        $fields->removeByName([
            'PrimaryButtonID',
            'SecondaryButtonID',
        ]);
        $fields->addFieldsToTab('Root.Main', [
            TextField::create('Title', 'Titel'),
            AnyField::create('PrimaryButton', 'Primärer Button'),
            AnyField::create('SecondaryButton', 'Sekundärer Button')
        ]);

        return $fields;
    }
}

Pretty sure that's a bug with AnyField. I suspected this scenario would fall flat on its face.
If the object you want to manage with AnyField has an UploadField it will likely not work.
I'll try to have a glance, but it will likely not be this week.

Got a PR which I think addresses the problem. Still needs to look at the CI.
https://github.com/maxime-rainville/silverstripe-anyfield/pull/35

Related PR merged


Export CHALICE_DEV_URL= ?

From the readme:

Additionally, the API Gateway endpoints will be shortened to https://endpoint/dev/ for brevity. Be sure to substitute https://endpoint/dev/ for the actual endpoint that the chalice CLI displays when you deploy your API (it will look something like https://abcdefg.execute-api.us-west-2.amazonaws.com/dev/.

Why not let the chalice  command-line export/set the URL as an environment variable? It should make scripting a lot easier (right now it would probably be possible to |tail -1 |read URL - but being able to check the exit-code of chalice, and then know that that one can go on with testing  http ${CHALICE_DEV_URL} or equivalent might make things even easier?

Giving this a bit more consideration, perhaps it would be even better to write the url to a file, like .endpoint.dev - or both. Might make it easier to keep abstractions working well cross-platform (perhaps with a sub-command: calice url that simply output the current url end-point?

I think this would be helpful.  I think I'll need to rework the .chalice structure internals.  I think in general I would like to have some file that tracks all the resources we create for you (in addition to the rest api id and stage so we can return the url to you).  That will also help facilitate other commands such as chalice delete (#40) and chalice resources (#11), which I'd like to add.

This has been resolved in https://github.com/awslabs/chalice/pull/169, which adds a chalice url command that prints the deployed URL to stdout.


Does numba's implementation of np.diff have a bug?

I'm having this problem where the numba implementation of np.diff does not work on a slice of a matrix. Is this a bug or am I doing something wrong?

    import numpy as np
    from numba import njit
    v = np.ones((2,2))

    np.diff(v[:,0])

array([0.])

    @njit
    def numbadiff(x):
        return np.diff(x)

    numbadiff(v[:,0])

---------------------------------------------------------------------------
TypingError                               Traceback (most recent call last)
<ipython-input-6-1838803668db> in <module>
----> 1 numbadiff(v[:,0])

~\Anaconda3\lib\site-packages\numba\dispatcher.py in _compile_for_args(self, *args, **kws)
    399                 e.patch_message(msg)
    400
--> 401             error_rewrite(e, 'typing')
    402         except errors.UnsupportedError as e:
    403             # Something unsupported is present in the user code, add help info

~\Anaconda3\lib\site-packages\numba\dispatcher.py in error_rewrite(e, issue_type)
    342                 raise e
    343             else:
--> 344                 reraise(type(e), e, None)
    345
    346         argtypes = []

~\Anaconda3\lib\site-packages\numba\six.py in reraise(tp, value, tb)
    666             value = tp()
    667         if value.__traceback__ is not tb:
--> 668             raise value.with_traceback(tb)
    669         raise value
    670

TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Invalid use of Function(<function diff at 0x000001AD488E8E58>) with argument(s) of type(s): (array(float64, 1d, A))
 * parameterized
In definition 0:
    TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Internal error at <numba.typeinfer.CallConstraint object at 0x000001AD4B281608>.
reshape() supports contiguous array only
[1] During: resolving callee type: BoundFunction(array.reshape for array(float64, 1d, A))
[2] During: typing of call at C:\Users\alujan\Anaconda3\lib\site-packages\numba\targets\arraymath.py (3227)

Enable logging at debug level for details.

File "..\..\..\..\Anaconda3\lib\site-packages\numba\targets\arraymath.py", line 3227:
    def diff_impl(a, n=1):
        <source elided>
        # To make things easier, normalize input and output into 2d arrays
        a2 = a.reshape((-1, size))
        ^

    raised from C:\Users\alujan\Anaconda3\lib\site-packages\numba\typeinfer.py:951
In definition 1:
    TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Internal error at <numba.typeinfer.CallConstraint object at 0x000001AD4B281608>.
reshape() supports contiguous array only
[1] During: resolving callee type: BoundFunction(array.reshape for array(float64, 1d, A))
[2] During: typing of call at C:\Users\alujan\Anaconda3\lib\site-packages\numba\targets\arraymath.py (3227)

Enable logging at debug level for details.

File "..\..\..\..\Anaconda3\lib\site-packages\numba\targets\arraymath.py", line 3227:
    def diff_impl(a, n=1):
        <source elided>
        # To make things easier, normalize input and output into 2d arrays
        a2 = a.reshape((-1, size))
        ^

    raised from C:\Users\alujan\Anaconda3\lib\site-packages\numba\typeinfer.py:951
This error is usually caused by passing an argument of a type that is unsupported by the named function.
[1] During: resolving callee type: Function(<function diff at 0x000001AD488E8E58>)
[2] During: typing of call at <ipython-input-5-8138554adfcb> (3)

File "<ipython-input-5-8138554adfcb>", line 3:
def numbadiff(x):
    return np.diff(x)
    ^

This is not usually a problem with Numba itself but instead often caused by
the use of unsupported features or an issue in resolving types.

To see Python/NumPy features supported by the latest release of Numba visit:
http://numba.pydata.org/numba-doc/latest/reference/pysupported.html
and
http://numba.pydata.org/numba-doc/latest/reference/numpysupported.html

For more information about typing errors and how to debug them visit:
http://numba.pydata.org/numba-doc/latest/user/troubleshoot.html#my-code-doesn-t-compile

If you think your code should work with Numba, please report the error message
and traceback, along with a minimal reproducer at:
https://github.com/numba/numba/issues/new

Thanks for the report. The issue you are seeing is because there's no support for .reshape() (as used by np.diff) on non-contiguous arrays, which is what the input is by virtue of taking a column out of a 2D C ordered array.

what is the solution or alternative of using  .reshape()


x/build: difference between post-submit builder and gomote makes repros less likely

What version of Go are you using (go version)?

$ go version
go version devel +594b4a3bfe Wed Nov 4 16:54:48 2020 +0000 linux/amd64

Does this issue reproduce with the latest release?
Bug under investigation not in latest releast
What operating system and processor architecture are you using (go env)?
openbsd-amd64-62 builder
What did you do?
Attempt to reproduce failures from #42237. These failures are occurring on nearly 100% of post-submit openbsd-amd64-62 builds on build.golang.org.
My attempt to repro (run from /src):
$ gomote create openbsd-amd64-62
user-mpratt-openbsd-amd64-62-0
$ GOROOT=$(readlink -f $(pwd)/../) gomote push user-mpratt-openbsd-amd64-62-0
2020/11/04 13:54:40 installing go1.4
2020/11/04 13:54:46 Remote doesn't have "src/cmd/go/testdata/script/test_benchmark_labels.txt"
2020/11/04 13:54:46 Remote doesn't have "src/runtime/debug/stack.go"
2020/11/04 13:54:46 Remote doesn't have "test/dwarf/dwarf.dir/z6.go"
2020/11/04 13:54:46 Remote doesn't have "test/fixedbugs/bug322.go"
2020/11/04 13:54:46 Remote doesn't have "src/cmd/vendor/golang.org/x/sys/unix/syscall_unix_gc.go"
2020/11/04 13:54:46 Remote doesn't have 9344 files (only showed 5).
2020/11/04 13:54:46 Remote lacks a VERSION file; sending a fake one
2020/11/04 13:54:49 Uploading 9345 new/changed files; 23218856 byte .tar.gz
$ gomote run user-mpratt-openbsd-amd64-62-0 ./go/src/all.bash
Building Go cmd/dist using /tmp/workdir/go1.4. (go1.12 openbsd/amd64)
Building Go toolchain1 using /tmp/workdir/go1.4.

Building Go toolchain2 using go_bootstrap and Go toolchain1.
Building Go toolchain3 using go_bootstrap and Go toolchain2.
Building packages and commands for openbsd/amd64.

##### Testing packages.

... 20 minutes later ...
ALL TESTS PASSED

What did you expect to see?
Test failures similar to the post-submit builders in almost all runs.
What did you see instead?
Failures almost never occur. Running all.bash takes ~20min, so I haven't run it tons of times, but I'd say I've probably gotten 1 or 2 failures out of around 10 runs. I've managed to get a few more repros running go test runtime, but I'm not sure the failure rate is any higher; that test just runs faster.

One other thing I've noticed which may be related is that it seems like the openbsd-amd64-62 gomote is significantly slower than the openbsd-amd64-62 builder.
e.g., compare this post-submit run to my gomote run:
Test Output
##### Testing packages.
ok      archive/tar     0.132s
ok      archive/zip     0.849s
ok      bufio   0.342s
ok      bytes   2.026s
ok      compress/bzip2  0.112s
ok      compress/flate  4.316s
ok      compress/gzip   0.657s
ok      compress/lzw    0.244s
ok      compress/zlib   1.988s
ok      container/heap  0.023s
ok      container/list  0.017s
ok      container/ring  0.016s
ok      context 0.153s
ok      crypto  0.023s
ok      crypto/aes      0.078s
ok      crypto/cipher   0.038s
ok      crypto/des      0.044s
ok      crypto/dsa      0.031s
ok      crypto/ecdsa    0.346s
ok      crypto/ed25519  0.111s
ok      crypto/elliptic 0.079s
ok      crypto/hmac     0.024s
ok      crypto/internal/subtle  0.020s
ok      crypto/md5      0.020s
ok      crypto/rand     0.127s
ok      crypto/rc4      0.055s
ok      crypto/rsa      0.233s
ok      crypto/sha1     0.015s
ok      crypto/sha256   0.016s
ok      crypto/sha512   0.024s
ok      crypto/subtle   0.022s
ok      crypto/tls      2.721s
ok      crypto/x509     1.747s
ok      database/sql    1.046s
ok      database/sql/driver     0.027s
ok      debug/dwarf     0.045s
ok      debug/elf       0.066s
ok      debug/gosym     0.057s
ok      debug/macho     0.027s
ok      debug/pe        0.037s
ok      debug/plan9obj  0.028s
ok      embed/internal/embedtest        0.033s
ok      encoding/ascii85        0.058s
ok      encoding/asn1   0.033s
ok      encoding/base32 0.130s
ok      encoding/base64 0.029s
ok      encoding/binary 0.038s
ok      encoding/csv    0.029s
ok      encoding/gob    0.067s
ok      encoding/hex    0.084s
ok      encoding/json   0.687s
ok      encoding/pem    0.048s
ok      encoding/xml    0.111s
ok      errors  0.055s
ok      expvar  0.043s
ok      flag    0.124s
ok      fmt     0.171s
ok      go/ast  0.045s
ok      go/build        2.028s
ok      go/constant     0.020s
ok      go/doc  0.233s
ok      go/format       0.039s
ok      go/importer     0.516s
ok      go/internal/gccgoimporter       0.052s
ok      go/internal/gcimporter  10.296s
ok      go/internal/srcimporter 9.709s
ok      go/parser       0.071s
ok      go/printer      0.698s
ok      go/scanner      0.035s
ok      go/token        0.059s
ok      go/types        4.011s
ok      hash    0.019s
ok      hash/adler32    0.040s
ok      hash/crc32      0.021s
ok      hash/crc64      0.022s
ok      hash/fnv        0.121s
ok      hash/maphash    0.254s
ok      html    0.025s
ok      html/template   0.481s
ok      image   0.192s
ok      image/color     0.042s
ok      image/draw      0.193s
ok      image/gif       3.448s
ok      image/jpeg      0.388s
ok      image/png       0.177s
ok      index/suffixarray       0.325s
ok      internal/cpu    0.040s
ok      internal/fmtsort        0.030s
ok      internal/poll   0.132s
ok      internal/profile        0.015s
ok      internal/reflectlite    0.249s
ok      internal/singleflight   0.028s
ok      internal/trace  0.207s
ok      internal/unsafeheader   0.018s
ok      internal/xcoff  0.038s
ok      io      0.359s
ok      io/fs   0.025s
ok      io/ioutil       0.030s
ok      log     0.040s
ok      log/syslog      1.411s
ok      math    0.052s
ok      math/big        2.772s
ok      math/bits       0.034s
ok      math/cmplx      0.020s
ok      math/rand       0.566s
ok      mime    0.055s
ok      mime/multipart  0.411s
ok      mime/quotedprintable    0.057s
ok      net     29.665s
ok      net/http        23.805s
ok      net/http/cgi    1.256s
ok      net/http/cookiejar      0.112s
ok      net/http/fcgi   0.040s
ok      net/http/httptest       0.132s
ok      net/http/httptrace      0.028s
ok      net/http/httputil       0.195s
ok      net/http/internal       0.020s
ok      net/http/pprof  4.234s
ok      net/internal/socktest   0.015s
ok      net/mail        0.029s
ok      net/rpc 0.068s
ok      net/rpc/jsonrpc 0.031s
ok      net/smtp        0.074s
ok      net/textproto   0.044s
ok      net/url 0.046s
ok      os      1.398s
ok      os/exec 1.937s
ok      os/signal       2.588s
ok      os/user 0.026s
ok      path    0.016s
ok      path/filepath   0.133s
ok      plugin  0.019s
ok      reflect 2.786s
ok      regexp  0.226s
ok      regexp/syntax   0.577s

Almost every big test takes 50-100%+ longer than the post-submit version. bytes 1.2s vs 2s, compress/zlip 1.5s vs 2s, reflect 1s vs 2.7s.
This is a very empirical observation, and I haven't seen the post-submit results from a passing run (since the logs are immediately deleted), so perhaps there is nothing there, but this makes me wonder if the gomote is on a smaller instance or something.

Thanks for reporting. Also CC @golang/release for awareness.
The openbsd-amd64-62 builder is a normal (not a "longtest" or "race" or otherwise semi-special builder), so running all.bash in a gomote session should be equivalent in spirit of what the builder is meant to test.
One of the most important differences that comes to mind is that when you have a gomote session running all.bash, all execution happens sequentially. The post-submit builder differs in that it's configured to shard test execution across multiple builder instances of that type:
$ goexec 'dashboard.Builders["openbsd-amd64-62"].SplitMakeRun()'
(bool)(true)

(See coordinator.go#L2003-L2007 and BuildConfig.SplitMakeRun.)
Which should explain the timing difference you've observed above.
I've only had a chance to look briefly so far, I'll see if I can look more later on.

I haven't seen the post-submit results from a passing run

I've looked up the logs for some passing post-submit builder runs, for reference:

https://build.golang.org/log/048aa4dea5849c147970cc9112d8aaf85c91337d
https://build.golang.org/log/2dde3efaca68a3d3df0bedb61f4bcc3fb4fe7006
https://build.golang.org/log/1426acabc5dc4bbf653877fa341fe90814f9442b

They all look similar, like so:
[...]
ok  	regexp/syntax	0.270s
ok  	runtime	72.720s
ok  	runtime/debug	0.112s
ok  	runtime/internal/atomic	0.073s
ok  	runtime/internal/math	0.010s
ok  	runtime/internal/sys	0.046s
ok  	runtime/metrics	0.009s
ok  	runtime/pprof	6.015s
ok  	runtime/race	0.386s
ok  	runtime/trace	1.521s
ok  	sort	0.062s
[...]

I've investigated this and I believe I'm able to reproduce the problem of #42237 on the openbsd-amd64-62 builder via gomote.
Investigation Log
I limited my scope to the openbsd-amd64-62 builder, which fails very often on build.golang.org. All of the failures have this shape:
panic: test timed out after 3m0s
[...]
FAIL	runtime	180.092s
FAIL

In other words, the runtime test is failing because it is taking more than 3 minutes to run, which is the default timeout for most package tests (see here) and the builder doesn't override it via GO_TEST_TIMEOUT_SCALE.
Here's an relevant bit from an event log of a recent failed build (full log here):
 2020-11-04T23:36:25Z run_tests_multi <IP_ADDRESS>:80: [go_test:regexp go_test:regexp/syntax]
  2020-11-04T23:36:30Z finish_run_tests_multi after 4.58s; <IP_ADDRESS>:80: [go_test:regexp go_test:regexp/syntax]
  2020-11-04T23:36:30Z run_test:go_test:runtime <IP_ADDRESS>:80
  2020-11-04T23:37:00Z still_waiting_on_test go_test:runtime
  2020-11-04T23:37:30Z still_waiting_on_test go_test:runtime
  2020-11-04T23:38:00Z still_waiting_on_test go_test:runtime
  2020-11-04T23:38:30Z still_waiting_on_test go_test:runtime
  2020-11-04T23:39:00Z still_waiting_on_test go_test:runtime
  2020-11-04T23:39:30Z still_waiting_on_test go_test:runtime
  2020-11-04T23:39:55Z finish_run_test:go_test:runtime after 3m25.3s; <IP_ADDRESS>:80
  2020-11-04T23:39:55Z run_tests_multi <IP_ADDRESS>:80: [go_test:runtime/debug go_test:runtime/internal/atomic go_test:runtime/internal/math]
  2020-11-04T23:39:55Z finish_make_and_test after 14m36.5s
  2020-11-04T23:39:55Z done with test failures
  2020-11-04T23:39:55Z finish_run_tests_multi after 74.7ms; err=buildlet: Client closed; <IP_ADDRESS>:80: [go_test:runtime/debug go_test:runtime/internal/atomic go_test:runtime/internal/math]
  2020-11-04T23:39:55Z main_buildlet_broken <IP_ADDRESS>:80

Notably, it tells me the runtime package tests were sharded and run individually (compare with regexp and regexp/syntax package tests above it, which were grouped together in a single runTestsOnBuildlet call).
This gave me the idea to try reproducing the failure by doing just go test -short runtime on a gomote session. Fortunately, I was able to reproduce the problem by doing that and didn't need to do anything more.
Reproduction Steps

Build Go at parent commit of CL 232298 (commit b3f7f60129b822978115717912f4d477a46e8467) in a openbsd-amd64-62 gomote session.

Run go test -count=1 -short runtime repeatedly. Observe success, all around 1~ minute completion time:
gotip $ git checkout 8fdc79e18a9704185bd6471b592db1e8004bd993~
[...]
HEAD is now at b3f7f60129 cmd/dist: fix build failure of misc/cgo/test on arm64
gotip $ export MOTE=$(gomote create openbsd-amd64-62)
gotip $ gomote push $MOTE
[...]
2020/11/04 18:29:24 Uploading 411 new/changed files; 2728173 byte .tar.gz
gotip $ gomote run $MOTE go/src/make.bash
Building Go cmd/dist using /tmp/workdir/go1.4. (go1.12 openbsd/amd64)
[...]
gotip $ gomote run $MOTE go/bin/go test -count=1 -short runtime
ok  	runtime	88.095s
gotip $ gomote run $MOTE go/bin/go test -count=1 -short runtime
ok  	runtime	46.000s
gotip $ gomote run $MOTE go/bin/go test -count=1 -short runtime
ok  	runtime	85.341s
gotip $ gomote run $MOTE go/bin/go test -count=1 -short runtime
ok  	runtime	43.466s
gotip $ gomote run $MOTE go/bin/go test -count=1 -short runtime
ok  	runtime	52.164s
gotip $ gomote run $MOTE go/bin/go test -count=1 -short runtime
ok  	runtime	55.943s
gotip $ gomote run $MOTE go/bin/go test -count=1 -short runtime
ok  	runtime	56.088s

Build Go at CL 232298 (commit 8fdc79e18a9704185bd6471b592db1e8004bd993) in a openbsd-amd64-62 gomote session.

Also run go test -count=1 -short runtime repeatedly. Now, observe success but many instances exceed the 180 second timeout:
gotip $ git checkout 8fdc79e18a9704185bd6471b592db1e8004bd993
HEAD is now at 8fdc79e18a runtime: reduce timer latency
gotip $ gomote push $MOTE
[...]
2020/11/04 18:44:32 Uploading 3 new/changed files; 61629 byte .tar.gz
gotip $ gomote run $MOTE go/src/make.bash
Building Go cmd/dist using /tmp/workdir/go1.4. (go1.12 openbsd/amd64)
[...]
Installed commands in /tmp/workdir/go/bin
gotip $ gomote run $MOTE go/bin/go test -count=1 -short runtime
ok      runtime 295.983s
gotip $ gomote run $MOTE go/bin/go test -count=1 -short runtime
ok      runtime 168.566s
gotip $ gomote run $MOTE go/bin/go test -count=1 -short runtime
ok      runtime 290.109s
gotip $ gomote run $MOTE go/bin/go test -count=1 -short runtime
ok      runtime 308.163s
gotip $ gomote run user-dmitshur-openbsd-amd64-62-0 go/bin/go test -count=1 -short runtime
ok      runtime 405.817s

Intermittent Slow Tests
I added -v to see what tests were slow. I found a few tests were sometimes slow (but not other times):
[...]
=== RUN   TestShrinkStackDuringBlockedSend
--- PASS: TestShrinkStackDuringBlockedSend (0.23s)
=== RUN   TestNoShrinkStackWhileParking
--- PASS: TestNoShrinkStackWhileParking (6.62s)
=== RUN   TestSelectDuplicateChannel
(a wait time of 2 minutes here) <------------------ !!!
--- PASS: TestSelectDuplicateChannel (120.02s)
=== RUN   TestSelectStackAdjust
--- PASS: TestSelectStackAdjust (0.08s)
=== RUN   TestChanSendSelectBarrier
--- PASS: TestChanSendSelectBarrier (0.05s)
[...]
PASS
ok  	runtime	199.880s

[...]
--- PASS: TestPseudoRandomSend (0.00s)
=== RUN   TestMultiConsumer
--- PASS: TestMultiConsumer (0.28s)
=== RUN   TestShrinkStackDuringBlockedSend
--- PASS: TestShrinkStackDuringBlockedSend (0.23s)
=== RUN   TestNoShrinkStackWhileParking
(a wait time of 2 minutes here) <------------------ !!!
--- PASS: TestNoShrinkStackWhileParking (126.49s)
=== RUN   TestSelectDuplicateChannel
(a wait time of 2 minutes here) <------------------ !!!
--- PASS: TestSelectDuplicateChannel (120.02s)
=== RUN   TestSelectStackAdjust
--- PASS: TestSelectStackAdjust (0.08s)
=== RUN   TestChanSendSelectBarrier
--- PASS: TestChanSendSelectBarrier (0.03s)
[...]
PASS
ok  	runtime	295.983s

Running just those tests individually didn't reproduce the problem:

gotip $ gomote run $MOTE go/bin/go test -count=1 -v -run=TestSelectDuplicateChannel -short runtime
=== RUN   TestSelectDuplicateChannel
--- PASS: TestSelectDuplicateChannel (0.03s)
PASS
ok  	runtime	0.046s
gotip $ gomote run $MOTE go/bin/go test -count=1 -v -run=TestSelectDuplicateChannel -short runtime
=== RUN   TestSelectDuplicateChannel
--- PASS: TestSelectDuplicateChannel (0.03s)
PASS
ok  	runtime	0.041s
gotip $ gomote run $MOTE go/bin/go test -count=1 -v -run=TestSelectDuplicateChannel -short runtime
=== RUN   TestSelectDuplicateChannel
--- PASS: TestSelectDuplicateChannel (0.03s)
PASS
ok  	runtime	0.039s
gotip $ gomote run $MOTE go/bin/go test -count=1 -v -run=TestSelectDuplicateChannel -short runtime
=== RUN   TestSelectDuplicateChannel
--- PASS: TestSelectDuplicateChannel (0.03s)
PASS
ok  	runtime	0.045s
gotip $ gomote run $MOTE go/bin/go test -count=1 -v -run=TestSelectDuplicateChannel -short runtime
=== RUN   TestSelectDuplicateChannel
--- PASS: TestSelectDuplicateChannel (0.03s)
PASS
ok  	runtime	0.045s

So it seems there's some sort of interaction between all the runtime tests when run one after another.
I hope this helps @prattmic be able to also reproduce the problem and use it to investigate #42237 more easily. Please let me know if it still doesn't reproduce for you for some reason.

As far as I can tell, the root cause here turned out to be that the problem was reproducible only when running go test -short runtime individually, but not as part of all.bash. I'll close this since I don't see anything more to do here. Please comment if I missed something.


Network watcher: Bug fix: packet capture error + descriptions

This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information

[x] The title of the PR is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For information on cleaning up the commits in your pull request, see this page.
[x] Except for special cases involving multiple contributors, the PR is started from a fork of the main repository, not a branch.
[x] If applicable, the PR references the bug/issue that it fixes.
[x] Swagger files are correctly named (e.g. the api-version in the path should match the api-version in the spec).

Quality of Swagger

[x] I have read the contribution guidelines.
[x] My spec meets the review criteria:

[x] The spec conforms to the Swagger 2.0 specification.
[x] Validation errors from the Linter extension for VS Code have all been fixed for this spec. (Note: for large, previously checked in specs, there will likely be many errors shown. Please contact our team so we can set a timeframe for fixing these errors if your PR is not going to address them).
[x] The spec follows the patterns described in the Swagger good patterns document unless the service API makes this impossible.

Hi @irrogozh, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (irrogozh). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

Good to merge.  This PR fixes the bug in Autorest.

No modification for NodeJS

 https://github.com/Azure/azure-sdk-for-ruby/pull/689

 https://github.com/Azure/azure-sdk-for-python/pull/994


Rename lock_expiry to timeout

lock_expiry is not correctly named, and give incorrect indication about the behaviour.
I could not found documentation about this on azure but my experiences show that it represents the time after which the http connection send 204 empty response if no message is available
When using a timeout of 100s I get the following debug log from hyper (reqwest)
2024-04-26T15:17:20.027847Z DEBUG app::worker: Fetching message from queue
  at src/worker/mod.rs:46

2024-04-26T15:17:20.028454Z DEBUG hyper::client::connect::dns: resolving host="name.servicebus.windows.net"
  at /Users/baptiste/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/client/connect/dns.rs:122

2024-04-26T15:17:20.075441Z DEBUG hyper::client::connect::http: connecting to <IP_ADDRESS>:443
  at /Users/baptiste/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/client/connect/http.rs:542

2024-04-26T15:17:20.108438Z DEBUG hyper::client::connect::http: connected to <IP_ADDRESS>:443
  at /Users/baptiste/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/client/connect/http.rs:545

2024-04-26T15:17:20.181322Z DEBUG hyper::proto::h1::io: flushed 356 bytes
  at /Users/baptiste/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/proto/h1/io.rs:340

// Waiting 100s

2024-04-26T15:19:00.302686Z DEBUG hyper::proto::h1::io: parsed 5 headers
  at /Users/baptiste/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/proto/h1/io.rs:208

2024-04-26T15:19:00.302737Z DEBUG hyper::proto::h1::conn: incoming body is empty
  at /Users/baptiste/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/proto/h1/conn.rs:224

2024-04-26T15:19:00.302921Z DEBUG hyper::client::pool: pooling idle connection for ("https", name.servicebus.windows.net)
  at /Users/baptiste/.cargo/registry/src/index.crates.io-6f17d22bba15001f/hyper-0.14.28/src/client/pool.rs:380

2024-04-26T15:19:00.303130Z DEBUG app::worker: No Message in Queue
  at src/worker/mod.rs:50

On this api doc 204 response is described as No messages available within the specified timeout period.

I agree timeout is not a perfect name but lock_expiry is just incorrect. I tried to find the same implementation in other SDK (go, js or java) but they I think they all use the amqp api not the http api so it's difficult to compare


Internal assets aren't being found even that they exist

I have an umbrella app which has many web apps of different domains. However, I would like to extract common components and styles to a separate application called :design_system.
To correctly forward and handle different paths request I also have a :proxy_web app that forwards to the respective endpoint based on the conn.path_info pattern.
Here's the ProxyWeb main part, the router:
defmodule ProxyWeb.Router do
  @behaviour Plug

  def init(opts), do: opts

  def call(conn, _opts) do
    endpoint = forward_conn(conn.path_info)
    endpoint.call(conn, [])
  end

  defp forward_conn(["api" | _]), do: PlataformaDigitalAPI.Endpoint
  defp forward_conn(["design-system" | _]), do: DesignSystem.Endpoint
  defp forward_conn(_), do: PlataformaDigital.Endpoint
end

Thats works fine, but phoenix_storybook has a strange behaviour.
In my :design_system app I define the router as:
defmodule DesignSystem.Router do
  use Phoenix.Router, helpers: false

  import PhoenixStorybook.Router

  scope "/" do
    storybook_assets("/design-system/storybook/assets")

    live_storybook("/design-system/storybook",
      backend_module: DesignSystem.Storybook,
      assets_path: "/design-system/storybook/assets"
    )
  end
end

So now I'm able to reach /design-system/storybook/assets/css/app.css for example, in the browser!
However, when I reach to /design-system/storybook the page reloads infinitely because the conn is halted on the AssetNotFoundController of phoenix_storybook
The partial log is
[debug] compiling storybook file: typography.story.exs
[debug] Processing with PhoenixStorybook.AssetNotFoundController.asset/2
  Parameters: %{"asset" => ["css", "fonts.css"]}
  Pipelines: [:storybook_assets]
[debug] Phoenix.Router halted in :storybook_assets/2
[debug] Processing with PhoenixStorybook.AssetNotFoundController.asset/2
  Parameters: %{"asset" => ["css", "app.css"]}
  Pipelines: [:storybook_assets]
[debug] Processing with PhoenixStorybook.AssetNotFoundController.asset/2
  Parameters: %{"asset" => ["js", "app.js"]}
  Pipelines: [:storybook_assets]
[debug] Phoenix.Router halted in :storybook_assets/2
[debug] Phoenix.Router halted in :storybook_assets/2

Sample Video
https://github.com/phenixdigital/phoenix_storybook/assets/44469426/e7669a9e-4e71-415a-b11c-3a5ef8f94d6d
The complete source code can be found at https://github.com/peapescarte/pescarte-plataforma/tree/feat/design-system-app

hey Zoey, sorry I hadn't much time lately to work on the storybook, but I'm now tackling all open issues.
Is your issue still relevant? If so, I can help this week

yes, it is!

Ok, I’ll try to reproduce your error tomorrow!

Hey Zoey, it took me a couple of hours to dig down to the issue, but the problem was you are not providing the storybook a LiveView endpoint.
I fixed it with:
diff --git a/apps/design_system/lib/design_system/endpoint.ex b/apps/design_system/lib/design_system/endpoint.ex
index 07356ee..62a1513 100644
--- a/apps/design_system/lib/design_system/endpoint.ex
+++ b/apps/design_system/lib/design_system/endpoint.ex
@@ -12,5 +12,7 @@ defmodule DesignSystem.Endpoint do
     key: "_design_system_key",
     signing_salt: "OBcQb8Zm"

+  socket("/design-system/live", Phoenix.LiveView.Socket)
+
   plug DesignSystem.Router
 end
diff --git a/apps/design_system/lib/design_system/router.ex b/apps/design_system/lib/design_system/router.ex
index 7bcca04..f404532 100644
--- a/apps/design_system/lib/design_system/router.ex
+++ b/apps/design_system/lib/design_system/router.ex
@@ -8,7 +8,8 @@ defmodule DesignSystem.Router do

     live_storybook("/design-system/storybook",
       backend_module: DesignSystem.Storybook,
-      assets_path: "/design-system/storybook/assets"
+      assets_path: "/design-system/storybook/assets",
+      live_socket_path: "/design-system/live"
     )
   end
 end

Let me know if it's working for you!

I'm closing, feel free to re-open if you are still stuck with this issue.


Responsive page

How to make responsive and adjustable page for desktop app??
when i expand and maximize the page, all the container overlaps each other.
How to overcome that issue?

Can you provide some sample code please?


No mocks (or documentation) for testing batch requests.

The API Client library allows us to mock out most requests pretty easily for testing as explained in the docs.  Unfortunately, there is no easy way to mock batch requests as far as I can tell.  For applications that make heavy use of batch requests, testing can become pretty cumbersome quite quickly.

Mocking out the calls so that it correctly calls the right callbacks is pretty complex when trying to do it with vanilla unittest.mock.
Formatting the requests/responses can also be a bit tricky when using the regular HttpMock class and I can't find it documented anywhere.

I'm not saying this is a great solution, but I've managed to get it working with the code below.  Maybe it will seed some ideas about how this can be accomplished in a more manageable way:
import collections
import itertools
class MockBatchHttpRequest(object):
    """An object that represents an HTTP request from the batch api."""
    def __init__(self, callback=None):
        self._callback = callback
        self._callbacks = collections.OrderedDict()
        self._counter = itertools.count()
        self._request_list = []

    def _new_id(self):
        """Generate a new id."""
        return next(self._counter)

    def add(self, request, callback=None, request_id=None):
        """Add a request to be executed as part of the batch."""
        request_id = request_id or self._new_id()
        self._callbacks[request_id] = callback
        self._request_list.append(request)

    def execute(self, http=None):
        """Execute the request."""
        for request, request_id in zip(self._request_list, self._callbacks):

            response = request.execute(http=http)
            callback = self._callbacks.get(request_id)
            if callback:
                # I'm currently being lazy and didn't test the exception case, so I didn't add handle that here either... :-)
                callback(request_id, response, None)
            if self._callback:
                self._callback(request_id, response, None)

so long as I monkey patched the Resource that I'm working with:
service = googleapiclient.discovery.build(*args, **kwargs)
service.new_batch_http_request = MockBatchHttpRequest

From here, I can use a regular HttpMockSequence to register the responses that I am expecting.

@mgilson - Thanks for the solution -- saved me some time :)
Made a couple small changes for exception handling:
    def execute(self, http=None):
        """Execute the request."""
        for request, request_id in zip(self._request_list, self._callbacks):
            response, exception = None, None
            try:
                response = request.execute(http=http)
            except Exception as e:
                exception = e

            callback = self._callbacks.get(request_id)
            if callback:
                callback(request_id, response, exception)
            if self._callback:
                self._callback(request_id, response, exception)

I'm happy to review any PRs to add this mocking functionality to http_mock.

I'm opting to close this as it's unlikely we will implement it in the future.

These client libraries are officially supported by Google. However, the libraries are considered complete and are in maintenance mode. This means that we will address critical bugs and security issues but will not add any new features.

thanks for your code. would be great if someone could write a few tests for it and post it as a pip lib


[Locomotion]: Implement walking with touchpad

Ability to move the play area using the touchpad and always walk forward in the direction the headset is facing.

Branch demoing solution: https://github.com/thestonefox/SteamVR_Unity_Toolkit/tree/feat/touchpad-walking

I could see a use in some of my projects where you want to initially orient the game experience to your physical space. So moving, rotating the play area until aligned with a spatial marker. Then locking it off could be interesting.
Imagine one controller would be used as a marker to place on a table or chair, and the other controller would move/rotate you until the controller aligns/sits on the virtual surface.

@bcoyle I've seen blogs about that sort of thing, where you can position things in the real world then tag them with the controller current position (or something) then those objects can be created in the game world. So you know where tables are to put the controllers.
Would be cool to implement something like that.

This isn't working in Unity 5.4 beta due to the way the headset is located.

Related to this issue: https://github.com/thestonefox/SteamVR_Unity_Toolkit/issues/62

The latest version of this branch:
https://github.com/thestonefox/SteamVR_Unity_Toolkit/tree/feat/touchpad-walking
Has a fix for unity 5.4 so should be working.

New version of this branch is now live. Resolves the unity 5.4 issue also tracks the person collider to where the headset it and also allows for crouching.

Need to prevent being able to stand up in areas where you're not allowed to stand up otherwise it goes crazy trying to resolve the rigid body.
One way to resolve would be to track the highest height that the headset has been at, then track the position of the play area whilst it was at that highest point.
Then on conflict just move the play area back to the last good known position.

Yup that's what they do in Budget Cuts. Thankfully upon standing we fade to black so that's on the player.

Yeah I think if the player is going to do something unnatural in game, then it's fair to resolve it with an unnatural response (i.e. fade to black and teleport to last good location)

Yup we're clearly on the same page here (see #65 hehe)

Another post about trackpad movement, https://www.reddit.com/r/Vive/comments/4k7an5/something_changed_im_now_ok_with_trackpad/

@bcoyle I'm working on the touchpad movement script right now!
Just got the collision resolution working, hopefully should be pushing the branch soon!

Ok new branch for people to try:
https://github.com/thestonefox/SteamVR_Unity_Toolkit/commits/feat/touchpad-walking
It now supports collision reset, so if you crouch and walk under something then try stand up, you just get put back to your last good standing position.
There is also a collider offset you can apply to make it lower than touching the headset to prevent grabbing objects hitting the collider (you could also toggle this offset via script at point of grab as it's public).

First version completed with: 3582c87173378ef8c1169d4d0ce63c42a9c0965b


BZ-1255695 - kie-deployment-descriptor.xml Source tab doesn't have XM…

…L syntax highlighting
(cherry picked from commit 121213b54bfeb23c1986e2a63c62f774fb7a0f4a)

+1 to merge (assuming tests pass)


leak memory

I just started the server from under "valgrind" and sent a few requests using tests/basic/test_ws_crash.py
Result:
LEAK SUMMARY:
    definitely lost: 448 bytes in 4 blocks
    indirectly lost: 2,208 bytes in 28 blocks
      possibly lost: 80,740 bytes in 49 blocks
    still reachable: 289,495 bytes in 1,869 blocks
         suppressed: 0 bytes in 0 blocks
ERROR SUMMARY: 42 errors from 42 contexts (suppressed: 0 from 0)

Attached full logs:
server.log
valgrind.log

Basically problem in wrapper or in mysql driver, also problem can be in wrong code which use QMySQL driver.

main target solution: replace wrapper by Qt and use original code for working with mysql database

https://stackoverflow.com/questions/5134891/how-do-i-use-valgrind-to-find-memory-leaks

Runned new test:
$ valgrind --leak-check=full \
    --show-leak-kinds=all \
    --track-origins=yes \
    --verbose \
    --log-file=valgrind-out.txt \
    ./fhq-server -wd ../ci/travis/data

valgrind:
==7435== LEAK SUMMARY:
==7435==    definitely lost: 11,296 bytes in 84 blocks
==7435==    indirectly lost: 135,164 bytes in 1,310 blocks
==7435==      possibly lost: 592,608 bytes in 1,610 blocks
==7435==    still reachable: 1,056,532 bytes in 11,688 blocks
==7435==         suppressed: 0 bytes in 0 blocks
==7435==
==7435== ERROR SUMMARY: 340 errors from 340 contexts (suppressed: 0 from 0)
==7435== HEAP SUMMARY:
==7435==     in use at exit: 1,795,600 bytes in 14,692 blocks
==7435==   total heap usage: 125,078 allocs, 110,386 frees, 21,563,189 bytes allocated

==7435== LEAK SUMMARY:
==7435==    definitely lost: 11,296 bytes in 84 blocks
==7435==    indirectly lost: 135,164 bytes in 1,310 blocks
==7435==      possibly lost: 592,608 bytes in 1,610 blocks
==7435==    still reachable: 1,056,532 bytes in 11,688 blocks
==7435==         suppressed: 0 bytes in 0 blocks
==7435==
==7435== ERROR SUMMARY: 340 errors from 340 contexts (suppressed: 0 from 0)


correct padding on how-to post view

The padding of the step Heading is not conform to mockups, child of #420

merged


Reloading - Reloading page

Make a page where reloading data are shown for "while reloading" process.

Done, when a shell lot is asigned, you can click one the "magic" icon to see reload data. Nothing fancy, just a simple page to display data.


Bump libtorch version to 1.1.0

Fix #103
I had to remove some JIT functionalities (which was actually not used) and fix some types in the data loader on the C++ side.

DOne in #131 based on this PR


[Help Needed] Animation speed

Hello! There is a way to adjust texture animation speed via properties?
Something like:
speed=10
speed=0

Not really, no.


Typo 'is reset' to 'resets'

Typo 'is reset' to 'resets' in working_with_rnns.py

Thanks for the PR -- "is reset" is actually what's intended in this context (passive voice).


Feature request: hide tooltip

I'd would like to be able to hide the tooltip as only find it annoying.
E.g. if I accidentally move my cursor to the top center where the title of the current active window is, it will change to 'waybar'. This new title is too short to be under the cursor, thus it becomes inactive and focus switches to my previous window. Now the focus of my cursor is the title of waybar again, and it will switch back to 'waybar'. This creates a rapid back-and-forth in active window state, which manifests itself as a flickering screen.

#172 duplicate?

Done in 83a6475510df2c3db325c6ba24b377858b487ca5
Just set in each module "tooltip": false


html code div

If you put the following into StackEdit things break in preview:
### I'm an inline html

hello from StackEdit Inline HTML

But if you add a space in front of the closing
 things work just fine:
### I'm an inline html

hello from StackEdit Inline HTML

This bit of code fixes this weird behavior for me:
        editor.getConverter().hooks.chain("preConversion", function(text) {

			text = text.replace(/^\<\/div\>/gm,
                function (wholeMatch) {
                    return "
";
                }
            );
			return text;
        });

Probably there's a better solution diving into the code.
Regards.
uh

Fixed in the v5 (https://stackedit.io/app).


Simplify UI

This new UI aims to be more intuitive while also reducing buttons and number of clicks required to do common actions. It's also a tiny bit more expressive. You can now edit the game clock outside of a ref timeout.

Clicking score takes user to edit-score dialog
Clicking clock takes user to edit-time dialog
Clicking new SCORE button takes user to new confirm-score dialog
Clicking TIMEOUT changes the the button to RESUME and vice versa
Gong button removed

Current coverage is 83.16% (diff: 81.11%)

Merging #17 into master will decrease coverage by 2.51%

@@             master        #17   diff @@
==========================================
  Files             3          3
  Lines           405        398     -7
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits            347        331    -16
- Misses           58         67     +9
  Partials          0          0

Powered by Codecov. Last update 74352f1...3d82074


create a dark mode buttton and make a dark mode

Description
i will make a "darkmode" option avilable for this website.The darkmode will be with hover ,box-shadow effect.
Screenshots

Checklist

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[X] I'm a GSSoC'24-Extd contributor
[ ] I'm a Hacktoberfest'24 contributor
[X] I am willing to work on this issue (optional)

@Arisha2902 thankyou for raising this issue But for now this feature is not required will let u know if required in future and make sure to star our Repo.


Failure to generate correct intersection between polygon and vertical line

When intersecting a perfectly vertical line with a simple bounding box, an empty geometry is returned instead of the expected linear intersection.
Steps to reproduce the problem.
In this example, line1 shows the expected behavior:
>>> import shapely.wkt as sw
>>> bbox = sw.loads('POLYGON ((0 0, 0 342, 576 342, 576 0, 0 0))')
>>> line1 = sw.loads('LINESTRING<PHONE_NUMBER>056567<PHONE_NUMBER>243917,<PHONE_NUMBER>261437<PHONE_NUMBER>625572)')
>>> line1.length
16.213595703233356

>>> print(line1.intersection(bbox))
LINESTRING<PHONE_NUMBER>056567<PHONE_NUMBER>243917,<PHONE_NUMBER>261437<PHONE_NUMBER>625572)

A similar line with perfectly aligned x-coordinates results in an empty intersection:
>>> line2 = sw.loads('LINESTRING<PHONE_NUMBER>056567<PHONE_NUMBER>325304,<PHONE_NUMBER>056567<PHONE_NUMBER>243917)')
>>> line2.length
8.56227320813872

>>> print(line2.intersection(bbox))
LINESTRING EMPTY

If we remove a few digits of precision from the first coordinate, the intersection is correct again:
>>> line2b = sw.loads('LINESTRING (346.819<PHONE_NUMBER>325304,<PHONE_NUMBER>056567<PHONE_NUMBER>243917)')
>>> line2b.length
8.562273214633842

>>> print(line2b.intersection(bbox))
LINESTRING (346.819<PHONE_NUMBER>325304,<PHONE_NUMBER>056567<PHONE_NUMBER>243917)

Operating system
Mac OS X 10.14.6 (18G103).
Shapely version and provenance
Shapely 1.7.1 installed via Pip.

This is a workaround I’ve been using:
def line_inside_polygon(line, polygon):
    ''' Return the portion of a line inside a polygon
    '''
    if not line.relate_pattern(polygon, '**1******'):
        # GEOS has trouble with vertical lines contained within polygons,
        # so just return the line itself if no part of it pokes outside.
        return line

    return line.intersection(polygon)

def line_outside_polygon(line, polygon):
    ''' Return the portion of a line outside a polygon
    '''
    if not line.relate_pattern(polygon, '**1******'):
        # GEOS has trouble with vertical lines contained within polygons,
        # so just return an empty geometry if no part of it pokes outside.
        return shapely.geometry.GeometryCollection()

    return line.difference(polygon)

Very interesting. Thanks for the report @migurski!
I can't reproduce it on Ubuntu 20.04 with shapely 1.7.1 and GEOS 3.8.0-CAPI-1.13.1.

reproduce.py
"""
For reproducing https://github.com/Toblerity/Shapely/issues/1088
"""
import shapely.wkt as sw

# ---------------------------------------------------
# In this example, line1 shows the expected behavior:
bbox = sw.loads('POLYGON ((0 0, 0 342, 576 342, 576 0, 0 0))')
line1 = sw.loads('LINESTRING<PHONE_NUMBER>056567<PHONE_NUMBER>243917,<PHONE_NUMBER>261437<PHONE_NUMBER>625572)')
print(line1.length)
# 16.213595703233356

print(line1.intersection(bbox))
# LINESTRING<PHONE_NUMBER>056567<PHONE_NUMBER>243917,<PHONE_NUMBER>261437<PHONE_NUMBER>625572)

# -------------------------------------------------------------------------------------
# A similar line with perfectly aligned x-coordinates results in an empty intersection:
line2 = sw.loads('LINESTRING<PHONE_NUMBER>056567<PHONE_NUMBER>325304,<PHONE_NUMBER>056567<PHONE_NUMBER>243917)')
print(line2.length)
# 8.56227320813872

print(line2.intersection(bbox))
# LINESTRING EMPTY

# ----------------------------------------------------------------------------------------------------
# If we remove a few digits of precision from the first coordinate, the intersection is correct again:
line2b = sw.loads('LINESTRING (346.819<PHONE_NUMBER>325304,<PHONE_NUMBER>056567<PHONE_NUMBER>243917)')
print(line2b.length)
# 8.562273214633842

print(line2b.intersection(bbox))
# LINESTRING (346.819<PHONE_NUMBER>325304,<PHONE_NUMBER>056567<PHONE_NUMBER>243917)

On my machine the script gives the following output:
16.213595703233356
LINESTRING<PHONE_NUMBER>056567<PHONE_NUMBER>243917,<PHONE_NUMBER>261437<PHONE_NUMBER>625572)
8.56227320813872
LINESTRING<PHONE_NUMBER>056567<PHONE_NUMBER>325304,<PHONE_NUMBER>056567<PHONE_NUMBER>243917)
8.562273214633842
LINESTRING (346.819<PHONE_NUMBER>325304,<PHONE_NUMBER>056567<PHONE_NUMBER>243917)

But on your machine I believe the output would be:
16.213595703233356
LINESTRING<PHONE_NUMBER>056567<PHONE_NUMBER>243917,<PHONE_NUMBER>261437<PHONE_NUMBER>625572)
8.56227320813872
LINESTRING EMPTY
8.562273214633842
LINESTRING (346.819<PHONE_NUMBER>325304,<PHONE_NUMBER>056567<PHONE_NUMBER>243917)

I'd be curious what your GEOS version is. You can get the version string like this:
python -c "import shapely.geos; print(shapely.geos.geos_version_string)"
# 3.8.0-CAPI-1.13.1

Hi @migurski this is an unfortunate upstream bug with GEOS 3.9.0 (see https://github.com/libgeos/geos/issues/408), which has recently been fixed.
Update to GEOS 3.9.1 (or downgrade to GEOS 3.8.1) to resolve this issue.

Thanks @mwtoews!


[FLINK-4384] [rpc] Add "scheduleRunAsync()" to the RpcEndpoint

NOTE: This builds on top of #2357 - only the second commit belongs actually to this pull request is relevant.
Use this view to look at the diff: https://github.com/apache/flink/pull/2360/commits/7b9eb2f3de23a7bee28346664ff39e0c28235a6e
Add a scheduleRunAsync() method to the RpcEndpoint. It behaves like runAsync() but delays the call by a given number of milliseconds. The delay does not happen by a thread sleep, but by scheduling the message that triggers the Runnable it into the future of the message dispatcher.
This also adds tests for the runAsync(), scheduleRunAsync(), and callAsync() that validate that all these calls actually run in the same thread (the RPC endpoint's main thread).

Great addition @StephanEwen. +1 for merging.
Things are getting in shape :-)

Will address the comments and merge this.

Manually merged into the flip-6 branch in f74f44bb56e50d1714e935df2980a6c8213faf89


How to make a sequence of http requests on a widget before build method

I have 3 classes: Users, Posts and Comments. User has many Posts and
Posts has many Comments.
I want that all data has been fetched before the widget's build method is called.
I tryed to use initState() to do this:
class FetchDataExample extends StatefulWidget {
  final User _user;

  FetchDataExample(this._user);

  @override
  _State createState() => _State(_user);
}

class _State extends State<FetchDataExample> {
  final User _user;

  _State(this._user);

  @override
  void initState() {
    _user.setPosts();
    super.initState();
  }

  @override
  Widget build(BuildContext context) {
    print(this._user.posts[0]);

    return Container(

    );
  }
}

In User class  I have:
void setPosts() async {

    String url = 'https://jsonplaceholder.typicode.com/posts?userId=' + this.id.toString();
    var request = Requester.get(url); // Returns a Future<Response>

    await request.then((value) => this.posts = Post.jsonToPosts(json.decode(value.body)));

    this.posts.forEach((post) => post.setComments());

    print(this.posts[0]);
}

The 'setComments()' has the same logic.
I have two prints:

Inside build that returns null;
Inside setPosts the returns Instance of 'Post';

So, by the time that Build method is called in the widget, the initState has not finished yet.
I need it be finished, does anyone know how can I do that?

Rewrite setposts as a future, then use it as part of a futurebuilder
so
future<posts>setPosts() async {  ...your code... return posts[0]
in you widget build method
return futurebuilder(future: _user.setPosts, builder: ...the widget that uses the data goes here
Recommend reading the docs here for more details, https://api.flutter.dev/flutter/widgets/FutureBuilder-class.html

You can use FutureBuilder
Follow this link
https://api.flutter.dev/flutter/widgets/FutureBuilder-class.html

@kenwen on my App, I need to do about 4-5 different requests that uses previous requests values.
The only way I can do that is nesting FutureBuilders?

@bernardohrl recommend reading the docs and SO, but off the top of my head you could use .then to chain all your futures together into one future


new version load fail

Traceback (most recent call last):
File "D:\ai\ComfyUI-aki-v1.1\nodes.py", line 1864, in load_custom_node
module_spec.loader.exec_module(module)
File "", line 883, in exec_module
File "", line 241, in call_with_frames_removed
File "D:\ai\ComfyUI-aki-v1.1\custom_nodes\ComfyUI-IF_AI_tools_init.py", line 10, in
from .IFDreamTalkNode import IFDreamTalk
File "D:\ai\ComfyUI-aki-v1.1\custom_nodes\ComfyUI-IF_AI_tools\IFDreamTalkNode.py", line 20, in
from .dreamtalk.core.utils import (
File "D:\ai\ComfyUI-aki-v1.1\custom_nodes\ComfyUI-IF_AI_tools\dreamtalk\core\utils.py", line 13, in
from configs.default import get_cfg_defaults
File "D:\ai\ComfyUI-aki-v1.1\custom_nodes\ComfyUI-IF_AI_tools\dreamtalk\configs\default.py", line 15, in
comfy_dir = find_comfy_dir(script_path)
File "D:\ai\ComfyUI-aki-v1.1\custom_nodes\ComfyUI-IF_AI_tools\dreamtalk\configs\default.py", line 12, in find_comfy_dir
return find_comfy_dir(parent_path)
File "D:\ai\ComfyUI-aki-v1.1\custom_nodes\ComfyUI-IF_AI_tools\dreamtalk\configs\default.py", line 12, in find_comfy_dir
return find_comfy_dir(parent_path)
File "D:\ai\ComfyUI-aki-v1.1\custom_nodes\ComfyUI-IF_AI_tools\dreamtalk\configs\default.py", line 12, in find_comfy_dir
return find_comfy_dir(parent_path)
[Previous line repeated 4 more times]
File "D:\ai\ComfyUI-aki-v1.1\custom_nodes\ComfyUI-IF_AI_tools\dreamtalk\configs\default.py", line 11, in find_comfy_dir
raise Exception("ComfyUI directory not found")
Exception: ComfyUI directory not found

is expecting ComfyUI-aki-v1.1 to be ComfyUI I am sorry I dont think I can change that in the code for now


MacroShader regex error

Using ColorMatrixFilter gives a strange error, like in ( https://github.com/fponticelli/thx.core/issues/50 ) :
/usr/share/haxe/std/neko/_std/EReg.hx
Error:(33, 11) Unsupported escaped char 's'
Error:(22, -1) Called from
/home/er453r/haxelib/openfl/3,4,0/openfl/_internal/macros/MacroShader.hx
Error:(29, 27) Called from

Just checked - it compiles on windows x64, the problem exists only on linux x64

it is a haxe issue, not openfls


MAINT: optimize: improve linprog error message for sparse input with method 'simplex'/'revised simplex'

Reference issue
Closes gh-13559
What does this implement/fix?
When a constraint matrix is sparse, scipy.optimize.linprog with method "simplex" or "revised simplex" fails with an error message that is difficult to trace. This PR adds a more explicit error message.
Additional Information
Previous error message: see gh-13559
New error message:
ValueError: Method 'revised simplex' does not support sparse constraint matrices. Please consider using one of {'highs', 'highs-ipm', 'highs-ds'}.

These changes LGTM, merging.  Thanks @mdhaber !


feat: Create Authorized Discord IDs

Description

Related Issue

Fixes #(issue number)

Types of changes

[ ] Bug fix (non-breaking change that solves an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (corrections, enhancements, or additions to documentation)
[ ] Other (please describe):

use it on this function:
https://github.com/kehiy/RoboPac/blob/02e015a2c88cec56d31fc6df033e4adf2790cc3b/engine/engine.go#L408
make sure you add it to .env.example.

Don't forget to sync your fork.

done


These dependencies were not found: with the nodemailer

I got this message when I tried to include nodemailer
  child_process in ./node_modules/nodemailer/lib/sendmail-transport/index.js
I already installed nodemailer using npm
npm install nodemailer --save
and I include it to my component
impor nodemailer from 'nodemailer'
and I user require too
const nodemailer =require('nodemailer) ;

This question is available on Nuxt.js community (#c6980)

Could you provide a snippet of the code you are using. Also, where are you including nodemailer?

Getting a similar issue after installing nodemailer and nodemailer-ses
$ npm run dev

...

These dependencies were not found:

* child_process in ./node_modules/nodemailer/lib/sendmail-transport/index.js
* dns in ./node_modules/nodemailer/lib/mailer/index.js
* fs in ./node_modules/nodemailer/lib/dkim/index.js, ./node_modules/nodemailer/lib/mime-node/index.js and 1 other
* net in ./node_modules/nodemailer/lib/mailer/index.js, ./node_modules/nodemailer/lib/smtp-connection/http-proxy-client.js and 1 other
* tls in ./node_modules/nodemailer/lib/smtp-connection/http-proxy-client.js, ./node_modules/nodemailer/lib/smtp-connection/index.js

To install them, you can run: npm install --save child_process dns fs net tls

Even after running that install command, I get the following:
$ npm install --save child_process dns fs net tls

...

+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>+<EMAIL_ADDRESS>added 187 packages from 83 contributors in 27.081s
[!] 80 vulnerabilities found [9019 packages audited]
    Severity: 22 Low | 40 Moderate | 18 High
    Run `npm audit` for more detail

Previously this was 10 Moderate and all node-sass related

$ npm run dev

...

 ERROR  Failed to compile with 8 errors                                                                                12:43:25

These dependencies were not found:

* child_process in ./node_modules/nodemailer/lib/sendmail-transport/index.js
* dgram in ./node_modules/native-dns-cache/lookup.js, ./node_modules/native-dns/lib/server.js and 1 other
* fs in ./node_modules/native-dns/lib/platform.js, ./node_modules/nodemailer/lib/dkim/index.js and 2 others

To install them, you can run: npm install --save child_process dgram fs

Seems like a vicious circle. Any help appreciated
Environment
$ node -v
v9.7.0

$ npm -v
6.0.1

^ including nodemailer within nuxt.config.js as serverMiddleware:
nuxt.config.js
module.exports = {
  // ...
  serverMiddleware: [
    { path: '/api/mailer', handler: '~/api/report-mailer.js' },
  ]
}

api/report-mailer.js
const app = require('express')();
const nodemailer = require('nodemailer')
const aws = require('aws-sdk')

aws.config.loadFromPath('config/aws.json')

let transporter = nodemailer.createTransport({
  SES: new aws.SES({ apiVersion: '2010-12-01' })
})

module.exports = { path: '/api', handler: app }

app.post('/mailer', (req, res) => {
  const options = {
    from<EMAIL_ADDRESS>    to: 'User<EMAIL_ADDRESS>    subject: 'Your attachment',
    text: 'Your attachment',
    html: '
Your attachment is attached
',
    attachments: [
      {
        filename: 'attachment.pdf',
        path: 'https://domain.com/path/to/file.pdf'
      }
    ]
  }

  transporter.sendMail(options, (err, info) => {
    if (info) console.log(info)
    if (error) console.log(error)
  })
})

component.vue
axios.post('/api/mailer', this.pdfUrlPath)
  .then(data => { })
  .catch(error => { })

And as soon as I post all of that, turns out the build was failing as I was also including nodemailer and nodemailer-ses within my component.vue file - build now successful
😄

Hello, @carmat, it's nice you've resolve this problem.
I don't understood what you did in this last post. Could you explain better? Sadly I still got this error.


Create playback button

This PR adds a new control for the playback rate and play/pause functionality, as well as the ability to go forward and backwards. It is rather specific to the case of logarithmically spaced bins symmetric around the 0, but can also be generalized if we want.
On a big (>600px) screen it appears as a floating dialog

on smaller screens it goes inline

and on 370px and smaller, there is a simplified interface

Hey @johnarban, sorry it took me so long to get back to you about this. I like this new interface a whole lot!!! I think it's intuitive and looks very nice.
I would suggest that you deploy it on a non-main branch so that Alyssa, Anna, Sue, and Mary would be able to access it and ask them to give comments about the UI on both desktop and mobile.
@Carifio24, please share your thoughts as well!
I have some suggestions here, roughly in order of how strongly I feel about them.
Mobile:

[ ] I don't think you need to hide the new time control box on xsmall mobile. If the user popped it open, you could lay it down right over the main controls that I circled in purple. Everything you need to manage time is in the new control box, so I don't think you need to also be able to access the main time controls. It just needs to be clear how to make it go away if you want to. Maybe an x in the corner?

Desktop:

[ ] The "Reverse" button should change to "Forward" if the user is already running time in reverse, to indicate that pressing the button will move time forward again.

[ ] The tooltip for the "Forward" (>>) button should change to "Faster" if you already moving forward. If you are moving forward or paused, the tooltip for the << button should say "Reverse".

[ ] Similarly, the tooltip for the "Reverse" button (the << on the main interface) should change to "Faster" if you are already moving in reverse. If you are moving in reverse or paused, the tooltip for the >> button should say "Forward".

[ ] Can you try the gauge or gauge-high icons and see if the dots appear clearly? The gauge-simple-high is so minimalist that I'm not sure someone would know what that is if they didn't already know that was a time control.

[ ] I think the tooltips want to be in front of the time controls box?

[ ] When we slow down time in the vicinity of totality, if this wouldn't be too much of a pain to implement - if the user explicitly uses the time controls to go faster, I think we should let them.

[ ] I might make the markers for the 1x, 10x, 100x on the time control slider be vertical line ticks rather than dots, but that's not at all a strong preference.

Super awesome work on this, @johnarban!!! 🌟

Those are good comments @Carifio24

[ ] I will make it more obvious that you tap the icon again (I can turn it into an 'x') to close the control on mobile
[ ] Push the tooltips below the buttons is smart.

And I think just forward is good. Most people will use the scrubber anyway.


leafletDataHelper.getLayers returning old data

From @rikbosch on March 31, 2015 11:52
I'm trying to adjust the map's bounds to the bounds of a featureGroup.
However, when retrieving the bounds of the group, it contains no marker layers.
I'm calling the following function after setting the markers in the $scope object:
 $scope.layers = {
    baselayers: {},
    overlays: {
        primary: {
            type: 'featureGroup',
            name: 'Primary Lines',
            visible: true
        },

        secundary: {
            type: 'featureGroup',
            name: 'secundary',
            visible: false
        }
    }
};

$scope.markers = {};

myApiService.getMarkerData()
    .then(function(data) {
        $scope.markers = mapMarkers(data.lines);
        fitToLayer('primary');
    });

function fitToLayer(name) {
    leafletData.getMap()
        .then(function(map) {
            leafletData.getLayers()
                .then(function(layers) {
                    var layer = layers.overlays[name]; //<== layer has no markers defined
                    map.fitBounds(layer.getBounds()); //<==throws error 'lat' undefined
                });
        });
}

function mapMarkers(lines) {
    return lines.map(function(line) {
        return {
            layer: 'primary',
            lat: line.x,
            lng: line.y,
            key: line.id
        };
    });
}

the full error:
TypeError: Cannot read property 'lat' of undefined
    at Object.L.LatLngBounds.getNorth (leaflet-src.js:1336)
    at Object.L.LatLngBounds.getNorthWest (leaflet-src.js:1316)
    at L.Map.L.Class.extend.getBoundsZoom (leaflet-src.js:1887)
    at L.Map.L.Class.extend.fitBounds (leaflet-src.js:1635)
    at main.controller.js:95
    at processQueue (angular.js:13248)
    at angular.js:13264
    at Scope.$get.Scope.$eval (angular.js:14466)
    at Scope.$get.Scope.$digest (angular.js:14282)
    at Scope.$get.Scope.$apply (angular.js:14571)

Copied from original issue: tombatossals/angular-leaflet-directive#668

From @jessertaylor on March 31, 2015 12:0
have you tried dumping layer.getBounds()?

Was there ever a solution to this issue? Believe I'm seeing the same error.

I am interesting to can access also to layer data.
How can i used the leafletData tool ?
In fact i would like to can acces to 'eachLayer' method of my gesojson layer to can modify my marker on a external action.
as here : http://gis.stackexchange.com/a/133325


Add Web APIs section with examples

Summary
This pull request adds a new section titled "Web APIs" to the Learn JavaScript project. This section covers various Web APIs that are essential for modern JavaScript development.
Changes Made

Added a new section in the table of contents.
Created subsections for DOM Manipulation, Fetch API, Geolocation API, Canvas API, Storage API, and Notification API.
Included practical code examples for each Web API.

Benefits

Provides practical examples of using Web APIs.
Enhances learners' understanding of how to interact with the browser and web server.
Makes the curriculum more comprehensive and up-to-date with current JavaScript practices.

I look forward to feedback and suggestions. Thank you for reviewing my contribution.

Nice work @srishti-coder 👏 .

Fixes #213 .


Add new own tab function to the TableTools

I find that the tab-button is generated by action-script code. That's not a problem. But can I create new tab-button for my own functionality? How to link the action then? Thanks in advance

Hi Alkasih,
The DataTables forums is the place for questions like this, you're more likely to get help there. This Github is used for tracking bugs.

Yes, you can use the fnClick option of the buttons to perform whatever custom action you want. This is in the documentation here: http://datatables.net/extensions/tabletools/button_options#fnClick .


Move validation from controllers to pkg/backup, pkg/restore

Fixes #131
Moves the validation to the first thing we do in Backup() and Restore().
Signed-off-by: Nikhita Raghunath<EMAIL_ADDRESS>/cc @ncdc @skriss

Thanks for the PR @nikhita! We're on holiday until after the new year, so I wanted to let you know it'll be a few days before we start reviewing this. Also, I will have an answer for you about how to deal with the controller issue. Stay tuned!

@nikhita hi, are you still interested in continuing with this?

@nikhita hi, are you still interested in continuing with this?

Interested? Yes. :)
But I don't have the bandwidth right now (at least the next couple of weeks). If anyone wants to work on it till then, please have a go at it!

Is this still needed? I'll have some cycles to work on it.

Yes, we still need this before we get to 1.0. We need to move defaulting and validation out of the controllers and into pkg/backup and pkg/restore.

I am going to close this because I'm not sure if I'll have time in the next few weeks to work on it and it's been open for a while. Sorry for the trouble!


Master

@all-contributors please add @wilderPariona for code

@all-contributors please add @wilderPariona for code