Filenames are too long

For example, this filepath is 201 characters.
tests/general/phase0/bls/sign_msg/small/sign_msg_0x263dbd792f5b1be47ed85f8938c0f29586af0d3ac7b977f21c278fe1462040e3_0x0000000000000000000000000000000000000000000000000000000000000000_0x0100000000000000

Linux has a maximum filename length of 255 characters for most filesystems. When we ultilize caching in our continuous integration or even locally, the base path may be more than 54 characters.
Please reduce the filename length for these tests.

Example full local directory with caching enabled ends up being 309 characters.
/home/preston/.cache/bazel/_bazel_preston/6e220e5720b8243fd605645eb29a29ba/external/eth2_spec_tests_general/tests/general/phase0/bls/sign_msg/small/sign_msg_0x263dbd792f5b1be47ed85f8938c0f29586af0d3ac7b977f21c278fe1462040e3_0x0000000000000000000000000000000000000000000000000000000000000000_0x0100000000000000

For now, we're forking the tar.gz and renaming all of these long directories so we can update to 0.8.3.

Sorry, was a bit careless with those names. Will change it after interop, fully prioritizing bugs + interop over formatting now.

Discussed offline that the culprit seems to be ecryptfs. Nonetheless, a shorter filename would be appreciated.

Yes, so on unix you have 2 constants, one for max filename at 255 characters usually and one for max total path at 4096 characters.
Ecryptfs adds metadata or random hashes of about 100 characters to each file stored in an encrypted partition.

See https://github.com/ethereum/eth2.0-specs/pull/1405

Thanks @protolambda. This is effectively resolved for the next version so i'll close this.


Libupnp error with Gerbera/DD-WRT/Entware

Hi,
I am refering to this bug:
https://sourceforge.net/p/pupnp/bugs/138/
I also found the bug meanwhile (at least it works for me).
See upnpapi.c at line 3574:
/* Cycle through the list of interfaces looking for IP addresses.  */
	for (i = (size_t)0; i < (size_t)ifConf.ifc_len;) {
		struct ifreq *pifReq =
		    (struct ifreq *)((caddr_t) ifConf.ifc_req + i);
//		i += sizeof *pifReq; <<<<<<< removed
		i += sizeof ifConf.ifc_req; <<< insert
		/* See if this is the sort of interface we want to deal with. */
		memset(ifReq.ifr_name, 0, sizeof(ifReq.ifr_name));
		strncpy(ifReq.ifr_name, pifReq->ifr_name,

As I am not familar with patch and so on I hope it is understandable. Could someone change this in source with next commit?
Thanks.

Hi robolaf,
I did a small change in master today in these lines, but your change does not seem to be correct.
sizeof *pifReq == sizeof struct ifreq
sizeof ifConf.ifc_req == sizeof struct ifreq *
You have changed the increment to the size of a pointer. Since the variable i is a char index into the buffer (ifc_len is in bytes), that does not seem to be what we want.
Regards,
Marcelo.

Hi Marcelo,
Thanks for the quick reply and cleaning up the code… You are right, of course. This was the wrong increment…
So, I digged into it a little bit more and found the following on my system:

the returned ifConf.ifc_len is 72
I looked at all 72 bytes in the buffer and there are two interfaces: starting at byte 0:lo and at 36:br0
=> that means the correct increment of i for my system needs to be 36 here:

   /* Cycle through the list of interfaces looking for IP addresses.  */
   for (i = 0; i < ifConf.ifc_len; i +=  36) {     //(int)(sizeof (struct ifreq))) {

I have no glue whether this is the same on other systems or whether ioctl sends back wrong data in my case.
I hope you have the possibility to check this out… and fix it accordingly.
Thanks and regards.

@robolaf Did you have success with @mrjimenez's patch? => https://github.com/mrjimenez/pupnp/commit/0fbbe083474221ef3c4484b33ecfe62a3faabba5

@v00d00 No, as said. The patch helps to better read the code, however it did not help to solve the issue.

Seeing the same issue on Gentoo, using version 1.10.1.
By default, Gerbera/libupnp binds to this local interface:
8: bridge0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 3a:54:61:0d:f4:75 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global dynamic bridge0
       valid_lft 301sec preferred_lft 301sec
    inet6 fe80::3854:61ff:fe0d:f475/64 scope link
       valid_lft forever preferred_lft forever

But as soon as I try to bind it to the following interface, I'll end up with LibUPnP error code: -121:
10: wg-sae13: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000
    link/none
    inet <IP_ADDRESS>/24 brd <IP_ADDRESS> scope global wg-sae13
       valid_lft forever preferred_lft forever

Is there anything I could provide to debug this further?

Hi Elias,
The return code -121 is UPNP_E_INVALID_INTERFACE. If you search for this, you will see that this is only returned in function UpnpGetIfInfo() in upnpapi.c. This function is called from UpnpInit2(). That means that UpnpGetIfInfo() could not find the interface name you requested or that it does not have an IP address bound to it.
I would suggest that you put some printf's in UpnpGetIfInfo() to find out what is going on.
Regards,
Marcelo.

@eliasp Is this still an issue or is it gone with the (few) releases since then?


Problem with evaluation abstractions

This is needed by @ryantrinkle.
https://github.com/jwiegley/hnix/blob/master/Nix/Eval.hs#L193

Progress report: I've been working on this for a few weeks.
The core idea is to change NVFunction to
NVFunction (Params (ValueSet m -> m r)) (ValueSet m -> m r)

This allows to pass the argumentset to itself at application time, to evaluate default values.
The current status is that is works when evaluated in Identity, but freezes (maybe with an infinite loop?) in IO. I still have to trace stuff to figure out what's happening here.
If anybody's curious, the WIP code is here: https://github.com/jwiegley/hnix/compare/master...madjar:fix-recursive-argument-set

@madjar Which test are you using to reproduce the freeze?

@jwiegley I added a small reproducing example (in the middle in Eval.hs, to make debugging easier :))
expr = let Success x = parseNixString "({ x ? 1, y ? x * 3 }: y - x) {}"
       in x
goeval :: MonadFix m => m (NValue m)
goeval = evalExpr expr mempty

goevalIO = goeval @ IO
goevalId = goeval @ Identity

goevalId returns (NVConstant (NInt 2))), goevalIO freezes.

@madjar I've looked at this with @ryantrinkle, and it looks like we're running into a problem with laziness.  It works with Identity, because nothing is getting forced, and it just so happens then that Nix's laziness gets implemented by Haskell's own laziness.
In IO, however, there are strict evaluation boundaries, which violate Nix's laziness, results in cycles that can't be broken, hence the bad MVar dependency.
I think the fix is to reify the concept of laziness and make it concept, using a new NVThunk data type, with the same semantics as Haskell/Nix. Thus, buildArgument would just stick the pending evaluation into an NVThunk, but wouldn't force it until it's actually used.  For Identity this will likely require using IORef and unsafePerformIO to allow fixing the thunk contents to avoid re-evaluation.
Does this sound like anything you'd be interested in tackling?

@jwiegley I've reached a similar conclusion (though not as articulate, as you can see here: https://github.com/jwiegley/hnix/issues/67#issuecomment-369343772).
I guess I started working on something along the lines of what you describe, replacing ValueSet with type Environment m = Text -> m (Maybe (NValue m)) (which is equivalent to Map Text (m (NValue m)), except you can't list keys ; see note [1]). But I'm not sure this is what you are suggesting.
Anyway, I'm definitely interested, but I feel I am not understanding everything here. Could you write a little bit more about your idea of NVThunk to get me started?
Note [1]: On top of the recursiveness of buildArgument, there is one more problem: in evalBinds, the keys of the set can be dynamic and depend on the set itself, which makes it impossible to list the keys without evaluation the whole set (thus making Map not usable).

Could we interleave the Monad into the value type, and then do pure . unsafePerformIO in the IO case to continue leveraging built-in laziness in all cases?
(On can also manually write something like pure . unsafePerformIO but duplicating the state token instead of magicking a new one which might help maintain the order of effects.)

I think that might be very hard to extend to other monads (e.g.
transformers over io)
On Tue, Mar 13, 2018, 00:04 John Ericson<EMAIL_ADDRESS>wrote:

Could we interleave the Monad into the value type, and then do pure .
unsafePerformIO in the IO case to continue leveraging built-in laziness
in all cases?
(On can also manually write something like pure . unsafePerformIO but
duplicating the state token instead of magicking a new one which might help
maintain the order of effects.)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jwiegley/hnix/issues/75#issuecomment-372540152, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABGlYOptGLBKmTdbx5bi_wYgncPsrIZkks5td0VZgaJpZM4Rqgsm
.

Progress report: I tried going with the NVThunk idea, but I kind of reached a wall. I'm not sure I quite groked it, and I'd love some hints on where NVThunk would actually fit.

I'll need to carve some time to check this out. Basically we want to do a sort of Löb transform: instead of seeing attribute sets as mappings of the type Map Key Value, they are really mappings from keys to functions, of type Map Key (Map Key Value -> Value).  If NVThunk were a kind of Value, then we'd be building a thunk that references the parent map, allowing us to return back to Map Key Value, where now some of the values are effectively deferred functions of type Map Key Value -> Value.  Part of the complexity in our case comes from the presence of a monad during evaluation, such that m needs to be added in all the necessary places above.

OK! This is finally fixed, and in the right way (not by avoiding IO, since that made supporting import in a principled way unpleasant).
The crux of the problem we were having can be demonstrated by this test case:
module Bug where

import           Control.Monad.Fix
import qualified Data.Map.Lazy as Map
import           Data.Maybe
import           Debug.Trace

loebM :: (MonadFix m, Traversable t) => t (t a -> m a) -> m (t a)
loebM f = mfix $ \a -> trace "mapM" $ mapM (trace "$ a" . ($ a)) f

main :: IO ()
main = do
    xs <- loebM $ Map.fromList
        [ (0, const (pure (2 :: Int)))
        , (1, \l ->
                  trace ("before: l = " ++ show (Map.keys l))
                    $ pure (fromJust
                            (trace
                                ("after: l = " ++ show (Map.keys l))
                                  $ Map.lookup 0 l) + 3)) ]
    traceM "loebM completed"
    print xs

If you remove the "before" trace, it works; if you leave it in, it dies. The reason here is what we had suspected before: monadic binds introduce sequence points. In order for loebM to do its job that way we want, the call to mapM has to be completed before we make any references to the members of the map. Otherwise, the env argument doesn't exist yet.
The answer for hnix is to add one more layer of indirection. ValueSet has changed from:
type ValueSet m = Map.Map Text (NValue m)

to:
type ValueSet m = Map.Map Text (m (NValue m))

This injection of an m layer allows us to defer monadic evaluation of the members of the map until after all the wiring has been done by loeb (we can now use regular loeb instead of loebM, since we don't want the effects processed during construction of the self-referential map).
Another change I made to show why this monadic layering is useful is a new MonadNix type class:
class MonadFix m => MonadNix m where
    currentScope :: m (ValueSet m)
    newScope :: ValueSet m -> m r -> m r
    importFile :: NValue m -> m (NValue m)

This basically represents all of the effects that occur during evaluation of a Nix expression: defining and referencing dynamic attribute scopes, and importing files. I'm sure more will be added in future.
This type class also simplified a lot of the code, because now instead of building lambdas everywhere, we can just use currentScope and newScope, which have much clearer meaning in the contexts where they are used.
Here's the IO definition of MonadFix. Note the use of a helper type called Cyclic to represent the fact that our monadic effects might occur anywhere throughout the evaluation tree:
newtype Cyclic m a = Cyclic { runCyclic :: StateT (ValueSet (Cyclic m)) m a }
    deriving (Functor, Applicative, Monad, MonadFix)

instance MonadNix (Cyclic IO) where
    currentScope = Cyclic get
    newScope s k = Cyclic $ put s >> runCyclic k
    importFile path = Cyclic $ case path of
        Fix (NVLiteralPath path) -> do
            eres <- parseNixFile path
            case eres of
                Failure err  -> error $ "Parse failed: " ++ show err
                Success expr -> runCyclic $ evalExpr expr
        _ -> error $ "Unexpected argument to import: " ++ show path

And last but not least, I added a helper function which came up during ICFP 2017, and which Conal Elliott (@conal) helped me to finally defined: adiM. This implements abstract definitional interpreters for catamorphisms over functor fixed points. The basic result is that, in the same way that recursion schemes let us arbitrarily layer in new data (such as parsing annotations), abstract definitional interpreters let us layer in new behavior on top of existing evaluators. This made it trivial to create a new tracing evaluator, which the tests use so that can see where evaluation went wrong:
tracingExprEval :: MonadNix m => NExpr -> IO (m (NValue m))
tracingExprEval =
    fmap (runIdentity . snd) . adiM @() (pure <$> eval) psi
  where
    psi k v@(Fix x) = do
        putStrLn $ "Evaluating: " ++ show x
        k v

Ping @ryantrinkle: You should be unblocked now, and have a way to play with imports as you wish!

Note that this exact same issue is currently plaguing all the other uses of rec in Eval.hs too, which can probably be resolved in a similar way. This is causing, for example, this test to fail:
git submodule update --init
cp ./data/nix/tests/lang/lib.nix .
./dist/build/hnix/hnix --debug --eval -f /Users/johnw/src/hnix/data/nix/tests/lang/eval-okay-list.nix

OK, that last problem should be sorted now as well, by the same approach.

I was able to remove the need for MonadFix entirely, using just loeb when recursive references are desired, and I've deferred management of the "scope stack" to the MonadNix instances, rather than dealing with it explicitly in the evaluator. At the moment it's implementing just by merging maps, but we should move to a more efficiently method since the depth will never be all that large, but the number of attributes will be.


Vagrant isn't being installed

I think something is wrong with the code that detects if an app exists. Vagrant is definitely in the apps list but doesn't get installed.

probably because it is installed as vagrant.pkg instead of .app.

Can this be easily fixed?

yes

closed by f80afa7241c6c3a405403511194a3f86adc8dd02


希望本软件能新增插件功能

浏览器插件, 代替浏览器默认下载吗?

抱歉，你想的有点过分了。。。。。

From: maxioptty<EMAIL_ADDRESS>Sent: Monday, April 13, 2020 12:17:57 PM
To: agalwood/Motrix<EMAIL_ADDRESS>Cc: ScottLiu2019<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [agalwood/Motrix] 希望本软件能新增插件功能 (#582)
浏览器插件, 代替浏览器默认下载吗?
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/agalwood/Motrix/issues/582#issuecomment-612742443, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AN3EBU7U54HGKYCDH6QSQ7DRMKG7LANCNFSM4LVBXHSQ.


Deprecation warning: Support for defaultProps will be removed from function components

Bug Report Description
Running the application shows the following warning in the javascript console:
react-dom.development.js:86 Warning: SubmitButton: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.
    at SubmitButton (http://localhost:5173/src/components/forms/SubmitButton.tsx:20:29)
    at form
    at http://localhost:5173/node_modules/.vite/deps/chunk-OQXAPCKX.js?v=d6448a19:1701:50
    at Grid2 (http://localhost:5173/node_modules/.vite/deps/chunk-LILNPRW7.js?v=d6448a19:2717:24)
    at SignInForm (http://localhost:5173/src/views/SignIn/SignIn.tsx:69:102)
    at div
    at http://localhost:5173/node_modules/.vite/deps/chunk-OQXAPCKX.js?v=d6448a19:1701:50
    at Box3 (http://localhost:5173/node_modules/.vite/deps/chunk-LILNPRW7.js?v=d6448a19:533:19)
    at http://localhost:5173/node_modules/.vite/deps/chunk-OQXAPCKX.js?v=d6448a19:1701:50
    at div
    at http://localhost:5173/node_modules/.vite/deps/chunk-OQXAPCKX.js?v=d6448a19:1701:50
    at Box3 (http://localhost:5173/node_modules/.vite/deps/chunk-LILNPRW7.js?v=d6448a19:533:19)
    at http://localhost:5173/node_modules/.vite/deps/chunk-OQXAPCKX.js?v=d6448a19:1701:50
    at div
    at http://localhost:5173/node_modules/.vite/deps/chunk-OQXAPCKX.js?v=d6448a19:1701:50
    at Box3 (http://localhost:5173/node_modules/.vite/deps/chunk-LILNPRW7.js?v=d6448a19:533:19)
    at http://localhost:5173/node_modules/.vite/deps/chunk-OQXAPCKX.js?v=d6448a19:1701:50
    at div
    at http://localhost:5173/node_modules/.vite/deps/chunk-OQXAPCKX.js?v=d6448a19:1701:50
    at Box3 (http://localhost:5173/node_modules/.vite/deps/chunk-LILNPRW7.js?v=d6448a19:533:19)
    at http://localhost:5173/node_modules/.vite/deps/chunk-OQXAPCKX.js?v=d6448a19:1701:50
    at SignIn (http://localhost:5173/src/views/SignIn/SignIn.tsx:175:29)
    at RenderedRoute (http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=6f24415e:3653:5)
    at RenderErrorBoundary (http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=6f24415e:3613:5)
    at RenderedRoute (http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=6f24415e:3653:5)
    at RenderErrorBoundary (http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=6f24415e:3613:5)
    at Outlet (http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=6f24415e:4024:26)
    at DialogProvider (http://localhost:5173/src/hooks/useDialog.tsx:21:27)
    at AlertProvider (http://localhost:5173/src/hooks/useAlert.tsx:27:33)
    at AuthProvider (http://localhost:5173/src/store/auth/AuthProvider.tsx:27:29)
    at RtlProvider (http://localhost:5173/node_modules/.vite/deps/chunk-LILNPRW7.js?v=d6448a19:910:5)
    at ThemeProvider (http://localhost:5173/node_modules/.vite/deps/chunk-LILNPRW7.js?v=d6448a19:859:5)
    at ThemeProvider2 (http://localhost:5173/node_modules/.vite/deps/chunk-LILNPRW7.js?v=d6448a19:949:5)
    at ThemeProvider (http://localhost:5173/node_modules/.vite/deps/chunk-2NI66VHR.js?v=d6448a19:296:12)
    at Root
    at RenderedRoute (http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=6f24415e:3653:5)
    at RenderErrorBoundary (http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=6f24415e:3613:5)
    at DataRoutes (http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=6f24415e:4766:5)
    at Router (http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=6f24415e:4031:15)
    at RouterProvider (http://localhost:5173/node_modules/.vite/deps/react-router-dom.js?v=6f24415e:4583:5)

What is the current behavior?
How can this issue be reproduced?

start the application with yarn dev
navigate to the app at http://localhost:5173 and open the developer console
observe the deprecation warning

What is the expected behavior?

there is no warning in the dev console

What is the motivation / use case for changing the behavior?

make the application ready for future versions of react

Please tell us about your environment:

n/a

Other information:

n/a

@ATNoblis FYI you will also run into this issue when using the template. We'll need to figure out where all the occurrences of this are so that we can fix it systematically.


Adds back the lost Clappy Bird images

This PR adds the deleted images from #663

Thank you! Apologies for messing this up in the first place!


Navbar_Added

navbar added A Bootstrap one as you have asked.

@Mainakroy050 just push your changes no need to close the PR

I have made another pull request, please close this one,
there is a problem from my end . So please do consider it. & I am extremely sorry for that.


Allow --no-part to work for fragmented downloads

Checklist

[X] I'm reporting a feature request
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2022.02.04. (update instructions)
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
In my format selection I look for [vcodec=vp9] and sometimes I get a "regular" download and other times I get a fragmented download. My commandline includes --no-part to force the download to write directly to the output file.
The problem is the fragmented download doesn't respect this --no-part option and creates a ytdl file and then a sequentially numbered frag file for each fragment it downloads. Because I don't keep fragments, it is downladed, merged and deleted immediately before the next fragment file is created.
My request is for --no-part to work with fragmented downloads and write fragments directly to the output file instead of to a separate file and then merging them.

PS: we need to write fragment files anyway when using -N since holding multiple fragments in memory is a bad idea

Thanks for that. I hadn't considered the possibility of losing a fragment which would be much harder to resume than a sequential download.

@pukkandan
As of now, is there any yt-dlp option to mitigate this?
It takes twice as much writes to disk to download fragmented video. First it writes a fragment, then appends it to the output file. So if I download a 10GB YouTube video I have to write 20GB of data (plus another 10GB to merge the formats). This trashes the drive.
Generally I'd do --downloader dash:ffmpeg because ffmpeg uses a single file but then I don't get the whole benefit of speed / sig calculation.

As of now, is there any yt-dlp option to mitigate this?

No


pack command should log destination path

Currently pack command is not logging the final path of the package

Fixed by #86


Automatic test update

By https://github.com/foolip/bikeshed-tests

I'm going to switch to using @autofoolip to create these PRs, so closing this one to see that work.


Bug on superscript

"x^{2}" - works as expected but reversing it "^{2}x" would result in the whole string being superscripted. A work-around is adding a space in front of the string " ^{2}x" and the result is ok but needles to say it is a useless drag removing the space from a NSMutableAttributedString.
Thank you

Hi @EmyXOR, thank you for reporting this error and sorry for answering so late.
I just checked this by adding the following lines to the UsageExamples.playground file:
"^{2}x^{3}".superscripted(font: .systemFont(ofSize: 12))
"^{2}x".superscripted(font: .systemFont(ofSize: 12))

These were the results, so it seems everything worked as expected:

What version of HandyUIKit are you using and what version of Xcode & Swift are you using? Also, what is your deployment target and platform?

Closing this due to irreproducability & inactivity.


Feature request: convert region Reason to ReScript

The playground has a hidden feature that converts reason to rescript.  (the settings, toggle RE/RES).  Whatever is doing this, I'm assuming it could be incorporated into this plugin.
Highlight a Region
Command Pallet -> Convert highlighted Reason to ReScript
Command Pallet -> Convert highlighted Rescript to Reason
I would find this VERY helpful as I'm learning rescript and often have to look at reason resources.  It could also be very useful for cut-n-paste programming

Unfortunatel,y this is not something we're going to actively pursue given we're phasing out Reason syntax and have a very limited workforce working on the editor tooling.


Not all information are passed in JSON

Hi guys, until now we used Azure Table to store the info about Lead, now we adopted Dynamics 365 and see that not all fields are transferred in JSON. For example "ProductId" is missing. This is essential, because we do not know what product our customer actually installed. Would it be possible to add at least "ProductId" to the JSON.  Thank you.

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

ID: 44a7d6f7-7f55-fe1b-f84d-ebcf4fc580b5
Version Independent ID: 316b0913-f7e4-2dfe-6d21-549ce69dcda3
Content: HTTPS Endpoint
Content Source: articles/marketplace/cloud-partner-portal-orig/cloud-partner-portal-lead-management-instructions-https.md
Service: marketplace
GitHub Login: @dan-wesley
Microsoft Alias: pabutler

Thanks for your comment. We are actively investigating and will get back to you shortly. Thanks for your patience.

Apologies for the delay. Please share this feedback directly with the feature owner via our public feedback channel. This allows other users to comment and vote on your feedback to helps prioritize the request against our backlog. Thanks again for the feedback.
@qianw211  - FYI


Change set_github_release to use FL_CHANGELOG context value if present

FL_CHANGELOG is a lane context value set by the changelog_from_git_commits action. This changes the set_github_release action to use that value as the default value for the release :description

Looks great, thanks @mfurtak :+1:


Island Utils 1.6.2 Incompatible with 1.20.1

The Island Utils mod, when in 1.6.1 and on 1.20.1, recommends I update it to 1.6.2, which is supposedly available for 1.20.2 and 1.20.1, but the 1.6.2 update is incompatible with 1.20.1, as it requires the most recent version of Noxesium, 1.0.5, which is only compatible with Minecraft version 1.20.2.

https://media.essential.gg/8efd83a2-b7ce-469c-3c95-8a2f82575a00

The one linked by the updater is the 1.20.2 build, are you downloading the build for 1.20.1? (https://modrinth.com/mod/island-utils/version/nKoBFdbG)


(experimental) tests: check priority order in txgen

Error: root: failed to run scenario: root: panic caught running scenario: priority correct 3: goroutine 1 [running]:

which is to say in the txgen test, stuff worked out with the transactions in order

let's go with #748


support uialertcontroller？

I want to know how to use PasswordTextField in uialertcontroller.

That's not supported at the moment. PRs are very welcome.


overlay-layout.scss affecting global styles

What is actually happening?
The overlay-layout.scss file is being applied globally throughout the project during development. If not disabled or managed properly during development, it causes unwanted global styles to be included in the final build, leading to potential style conflicts and layout issues across different components.
What is expected?
The overlay-layout.scss file should be scoped or conditionally included, so it doesn't affect the entire project globally, especially in the final production build. It should only be applied when necessary and not interfere with the styles of other components.
Reproduction steps:

Include overlay-layout.scss in the project globally.
Observe the global impact on all pages and components during development.
Build the project for production.
Check the output CSS file to see that the styles from overlay-layout.scss are still included, affecting the entire application.

Hi @NolaZheng, thank you for bringing up this issue.
The fix has been released in v1.2.2. If you encounter any further issues or have any questions, feel free to reach out.
Thanks again!

Hi @motea927, thank you for fixing the issue! I tested the new version and found that css is all fine now.
I also found that adding an additional zIndex in layoutPreview is required for new version to work properly.
 OverlayLayout({
        /* options */
        layoutPreview: {
          style: {
            position: 'absolute',
            margin: 'auto',
            inset: '0',
            width: '16.2rem',
            height: '6.6rem',
            zIndex: 999, // <--- this
          },
        },
      }),

Perhaps it would be worth considering an update to the documentation or include the CSS separately. Thanks again!

Hi @NolaZheng,
After merging PR #13, the layout preview lost its default styles. This issue has been addressed in PR #16 and is included in the latest release: v1.2.3.
Thanks for your feedback!


Add IDToken for Azure provider

Description
This adds the IDToken to the session for the Azure provider.
Motivation and Context
This allows it to be passed as a bearer token in the Authorization header to an upstream such as the Kubernetes dashboard. It solves the issue in https://github.com/pusher/oauth2_proxy/issues/131

How Has This Been Tested?
This has been tested against Azure AD to check that it returns the IDToken. It was tested with nginx in auth proxy mode to check that this token could be used to authenticate to the kubernetes dashboard.
As a result of the change the cookie being returned is larger and has to be split. This can cause an issue if using nginx to proxy requiring proxy buffer size be increased (see https://andrewlock.net/fixing-nginx-upstream-sent-too-big-header-error-when-running-an-ingress-controller-in-kubernetes/). I'm not sure therefore if something should be noted in the changelog regarding this.

Checklist:

[x] My change requires a change to the documentation or CHANGELOG.
[x] I have updated the documentation/CHANGELOG accordingly.
[X] I have created a feature (non-master) branch for my PR.

I've added a note to both the documentation and the changelog

We just tested this branch and ran into an issue with
[2019/10/03 06:23:31] [oauthproxy.go:745] Error loading cookied session: Cookie "_oa
uth2_proxy" not present
As you say in the conversation/documentation the cookie has been split into _oauth2_proxy_0, _oauth2_proxy_1, _oauth2_proxy_2. We are using the auth-request mode which seems to be the most common.
Nginx has been configured with increased proxy buffer size. Where do we need to make changes now to make this work?
This is how we configure our ingress:
nginx.ingress.kubernetes.io/auth-signin: https://$host/oauth2/start?rd=$request_uri
nginx.ingress.kubernetes.io/auth-url: https://$host/oauth2/auth

@iremmats What do the logs for the ingress controller say? The log from oauth2-proxy says it's not getting the cookie and the reason for that lies somewhere in nginx so those logs should hold the answer.

@iremmats Split cookies with auth request mode can cause issues. Ensuring Nginx properly copies the set-cookie headers across has had many different solutions posted in issues on this repo for a while but it has not really been solved.
Instead, the recommendation is to use redis for session storage, which solves the problem of large cookies by just issuing a session ticket rather than the full session, meaning no more split cookies

Any idea when this will be merged? I'm looking forward to testing it out! Thanks.

If we can get the conflicts resolved I think this will be good to go.

@syscll I've resolved the conflicts if you're able to review it once more. Thanks.


Nightly Deployment Automation

Finish Nightly deployment work SUPER FEATURE UMBRELLA TICKET.

@hargitayjpl I think we can mark this as "Done".  Let's discuss more, next meeting


Implement the BallerinaTupleTypeBuilder in Types API

Description:
$title
Describe your task(s)
- TupleTypeBuilder withMemberType(TypeSymbol mType)
- TupleTypeBuilder withRestType(TypeSymbol rType)
- TupleTypeSymbol build()

Related Issues (optional):
Subtask of #35415

Completed by #35873


Space Ninjas auto-toggle internals after spawning

About the PR
Space ninja masks automatically toggle internals on at roundstart (technically, when they are first equipped. Thus, space ninja masks spawned with F5 will do this the first time they are worn)
Technical details
When an entitiy with BreathToolComponent.AutomaticActivation = true is equipped, it schedules the werarer's internals to be toggled on the next tick. (The delay is to ensure that the ninja's gear finished spawning and thus there is an air tank to work with)
Currently, this field is then set to false, so this only happens the first time when such a mask is equipped.
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl: Errant

tweak: Space Ninjas now automatically turn their internals on when they spawn.

Pretty good quality of life change, other than that one nitpick it looks good to me!

Thinking about it this really just seems like hacks around implementing startinggear ordering if it's just going to activate it the next 'tick'. There's no design reason for this to even exist besides "I'm not sure on entity spawning" which we can guarantee for anything that currently cares about this.

I removed the whole delay thing and introduced a new bool to the class used to get an entity's inventory slots. When this flag is set on the request, "mask" is moved to the end of the list of slots (if present)
This works for the current scenario, and is technically "done".
But is that enough? This is a very specific transformation with no future potential.
Should I replace it with a more complex functionality that can take some sort of rule list/template for future uses, and pass such a rule from the gear spawning code, rather than the current book?

I have big brained a solution but will fix this when I get time.


Model Summary option

It would be nice if we can get a summary of our model:
let us suppose our data model contains:
model sample{
   role: String
   salary: Int
}

Suppose syntax could be:
ctx.prisma.sample.summary()

Output :-
[    {
          "role":["user",["user","admin"],1669],
   },
  {
          "salary":["73333",[1....100000],1669],
   },
]

OR
Overall output
like by using ctx.prisma.sample.summary().preetify()
SAMPLE
--------------------------------------------------------------
values     FREQUENT             UNIQUE      COUNTS
--------------------------------------------------------------
role          user            [user,admin]    1669
salary        73333          [1....100000]     1669

It could be similar like python pandas describe function.

I am marking this as a feature. Not sure it will be in the core but you can implement a Prisma middleware to convert json into that pretty format.
https://www.prisma.io/docs/reference/tools-and-interfaces/prisma-client/middleware
Also, I have a side project which can generate a summary of your mode. Maybe you are interested in checking it out: https://github.com/pantharshit00/prisma-docs-generator


Ship docker-compose or rancher-compose with rancher-os

docker-compose (or rancher-compose) is great often used when you have to deployed services involving many containers. It would be nice to have it natively supported by rancher-os

rancher-compose is what powers services on RancherOS. Perhaps we should also expose it as a command line tool.

it make sense to me to have it under a ros sub-command

/cc @ibuildthecloud

Will rancher-compose as sub-command of ros also usable for user-docker or only with system-docker?

+1

The problem with shipping docker-compose is that it will increase the distribution size by about 9 mb.  Rancher-compose could be included as its go, but it seemed self serving to bundle it.
I have this other tool I've fooled with for awhile but have not released called "wonka".  Essentially it makes it look like you are running a local CLI but in fact it's wrapped in a docker container.  I think this is the correct route to bundling more great tools like docker compose.

Essentially it makes it look like you are running a local CLI but in fact it's wrapped in a docker container.

Would be a great feature / tool!!!

@ibuildthecloud I look forward to it

is there a preferenced way or documentation on how to add docker-compose yourself?

my bad, just found https://github.com/rancher/os/issues/128

@ibuildthecloud will be good have more info about how to use wonka it's really hard to start working with RancherOS and make it your default OS to work daily

Using a custom container and docker network, I can achieve the same thing as docker-compose. would be nice though from an automation/scripting point of view to simply just have docker-compose :)

I was also looking for docker-compose.
I did
sudo ros console switch debian
sudo apt-get install wget
wget https://github.com/docker/compose/releases/download/1.16.1/run.sh
chmod +x run.sh
mkdir ~/bin
mv run.sh ~/bin/docker-compose
export PATH=$PATH:~/bin

I put a docker-compose.yml in a directory and run it using:
docker-compose up -d

But having docker-compose directly could be a nice feature

Not any official comments about this yet?

Another simple way to do this an keep it on each reboot, add this to your cloud-config.yml:
runcmd:
    - wget https://github.com/docker/compose/releases/download/1.21.2/docker-compose-$(uname -s)-$(uname -m) -O /usr/bin/docker-compose
    - chmod +x /usr/bin/docker-compose

@netroller
So it will BE downloaded every reboot? Maybe it's better to download it to a persistent directory and symlink if needed?
Sometimes I use docker-compose inside of a docker container (bash script or alias) 😁

This issue is open since 3 years. Is anyone actually using RancherOS, and if so, how is it being used if there is no way to orchestrate a bunch of services? The cloud-config.yml has a grave issue that it does not allow you to preload data before starting the services, with the worst side-effect being that non-existent files bind-mounted to volumes will be created as directories, making the affected container completely unusable (restarting the container with a directory mount replaced by a correct file mount will just show an error).
I've been trying to use ROS since several weeks now and whichever way I go, something unexpected and completely blocking stops any progress; after giving up trying to use cloud-config->rancher->services, I got stuck by the lack of a *-compose tool. The next option I'm trying is to use docker-compose via a docker image, which feels like a ridiculous hack.

I am installing docker-compose manually for a 2 years now via a simple script.
write_files:
  - path: /etc/setup.sh
    permissions: "0755"
    owner: root
    content: |
      #!/bin/bash
      if [ $(/usr/bin/id -u) -ne 0 ]; then
          echo "Not running as root"
          exit
      fi

      mkdir -p /opt/bin
      COMPOSE_VERSION=`curl -s https://api.github.com/repos/docker/compose/releases/latest | grep 'tag_name' | cut -d\" -f4`
      sh -c "curl -L https://github.com/docker/compose/releases/download/${COMPOSE_VERSION}/docker-compose-`uname -s`-`uname -m` > /opt/bin/docker-compose"
      chmod +x /opt/bin/docker-compose
      sh -c "curl -L https://raw.githubusercontent.com/docker/compose/${COMPOSE_VERSION}/contrib/completion/bash/docker-compose > /etc/bash_completion.d/docker-compose"

Would be nice if there is something build in.

An official answer here could be to show how to install rancher-compose in RancherOS and to show what it can be used in a quite similar manner than docker-compose

@scls19fr ros service command means rancher-compose. https://rancher.com/docs/os/v1.x/en/installation/system-services/custom-system-services/
Also you can download the rancher-compose CLI, https://github.com/rancher/rancher-compose/releases


can't update neither patch

Hi there, since las updat I get this error... any help? thankyou!
Traceback (most recent call last):
File "C:\GitHub\SuperSD\extensions\sd-webui-comfyui\lib_comfyui\custom_extension_injector.py", line 87, in patch_prompt_server_add_routes
add_routes_ast_function.body[2].value.args[0].elts[0:0] = [extra_line_of_code.body[0].value]
AttributeError: 'For' object has no attribute 'value'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "C:\GitHub\SuperSD\extensions\sd-webui-comfyui\lib_comfyui\comfyui\pre_main.py", line 98, in
main()
File "C:\GitHub\SuperSD\extensions\sd-webui-comfyui\lib_comfyui\ipc_init_.py", line 41, in wrapper
return function(*args, **kwargs)
File "C:\GitHub\SuperSD\extensions\sd-webui-comfyui\lib_comfyui\comfyui\pre_main.py", line 43, in main
patch_comfyui()
File "C:\GitHub\SuperSD\extensions\sd-webui-comfyui\lib_comfyui\ipc_init_.py", line 41, in wrapper
return function(*args, **kwargs)
File "C:\GitHub\SuperSD\extensions\sd-webui-comfyui\lib_comfyui\comfyui\pre_main.py", line 85, in patch_comfyui
custom_extension_injector.register_webui_extensions()
File "C:\GitHub\SuperSD\extensions\sd-webui-comfyui\lib_comfyui\custom_extension_injector.py", line 14, in register_webui_extensions
register_custom_scripts(script_paths)
File "C:\GitHub\SuperSD\extensions\sd-webui-comfyui\lib_comfyui\ipc_init_.py", line 41, in wrapper
return function(*args, **kwargs)
File "C:\GitHub\SuperSD\extensions\sd-webui-comfyui\lib_comfyui\custom_extension_injector.py", line 33, in register_custom_scripts
patch_prompt_server_add_routes(parsed_class, custom_scripts_path_list)
File "C:\GitHub\SuperSD\extensions\sd-webui-comfyui\lib_comfyui\custom_extension_injector.py", line 89, in patch_prompt_server_add_routes
raise RuntimeError("Cannot patch comfyui as it is not up to date")
RuntimeError: Cannot patch comfyui as it is not up to date

After uninstalling and reinstalling the plugin in an attempt to get it to see torch (see my previous issue) I get this same error. I have tried setting the ICS to file system as suggested elsewhere - but that didn't seem to make a difference either.

Same issue... I met the issue too today...And I am sure it is up to date... I don't know why....

Spent 4H in this issue but I cannot find a solution....exhaust...

As much as I don't want to - I may have to setup a standalone and link it - I was hoping to keep it all in the same automatic folder family, but oh well. 🙃

Just to cIarify, @jayododds I don't think this is the same issue as you had in #198.

Okay, should be fixed. They added a for loop in the middle of the function, so we were patching the wrong thing. I also updated the error message so that people don't spend 4h trying to fix a non-fixable issue.

right now it works for me. The only thing was the comfyui manager were not there. I'm reinstalling sd-webui-conmfyui. it might be there if I'm not wrong.. if not I'll try to do it manually (I'm noob). I'll let you know about the reinstalling. Good job!

right now it works for me. The only thing was the comfyui manager were not there. I'm reinstalling sd-webui-conmfyui. it might be there if I'm not wrong.. if not I'll try to do it manully (I'm noob)

Everything ok!

The update got it running but now I'm onto the white screen in tab issue :) Getting closer!

I updated the new version, but a new issue come up....
[ComfyUI] To see the GUI go to: http://<IP_ADDRESS>:8189
Exception in thread Thread-8 ():
Traceback (most recent call last):
File "E:\Stable diffusion\sd-webui-aki-v4.5\python\lib\site-packages\aiohttp\connector.py", line 1152, in _create_direct_connection
hosts = await asyncio.shield(host_resolved)
File "E:\Stable diffusion\sd-webui-aki-v4.5\python\lib\site-packages\aiohttp\connector.py", line 874, in _resolve_host
addrs = await self._resolver.resolve(host, port, family=self._family)
File "E:\Stable diffusion\sd-webui-aki-v4.5\python\lib\site-packages\aiohttp\resolver.py", line 33, in resolve
infos = await self._loop.getaddrinfo(
File "asyncio\base_events.py", line 863, in getaddrinfo
File "concurrent\futures\thread.py", line 58, in run
File "socket.py", line 955, in getaddrinfo
socket.gaierror: [Errno 11004] getaddrinfo failed
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "threading.py", line 1016, in bootstrap_inner
File "threading.py", line 953, in run
File "E:\Stable diffusion\sd-webui-aki-v4.5\extensions\sd-webui-comfyui\ComfyUI\custom_nodes\ComfyUI-Manager_init.py", line 2240, in
threading.Thread(target=lambda: asyncio.run(default_cache_update())).start()
File "asyncio\runners.py", line 44, in run
File "asyncio\base_events.py", line 649, in run_until_complete
File "E:\Stable diffusion\sd-webui-aki-v4.5\extensions\sd-webui-comfyui\ComfyUI\custom_nodes\ComfyUI-Manager_init_.py", line 2238, in default_cache_update
await asyncio.gather(a, b, c, d)
File "E:\Stable diffusion\sd-webui-aki-v4.5\extensions\sd-webui-comfyui\ComfyUI\custom_nodes\ComfyUI-Manager_init_.py", line 2226, in get_cache
json_obj = await get_data(uri)
File "E:\Stable diffusion\sd-webui-aki-v4.5\extensions\sd-webui-comfyui\ComfyUI\custom_nodes\ComfyUI-Manager_init_.py", line 516, in get_data
async with session.get(uri) as resp:
File "E:\Stable diffusion\sd-webui-aki-v4.5\python\lib\site-packages\aiohttp\client.py", line 1141, in aenter
self._resp = await self._coro
File "E:\Stable diffusion\sd-webui-aki-v4.5\python\lib\site-packages\aiohttp\client.py", line 536, in _request
conn = await self._connector.connect(
File "E:\Stable diffusion\sd-webui-aki-v4.5\python\lib\site-packages\aiohttp\connector.py", line 540, in connect
proto = await self._create_connection(req, traces, timeout)
File "E:\Stable diffusion\sd-webui-aki-v4.5\python\lib\site-packages\aiohttp\connector.py", line 901, in _create_connection
_, proto = await self._create_direct_connection(req, traces, timeout)
File "E:\Stable diffusion\sd-webui-aki-v4.5\python\lib\site-packages\aiohttp\connector.py", line 1166, in _create_direct_connection
raise ClientConnectorError(req.connection_key, exc) from exc
aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host raw.githubusercontent.com:443 ssl:default [getaddrinfo failed]

@WhiteKnight666 Are you using 2 different venvs for your Webui and ComfyUI installation? I could be wrong but I feel like some ComfyUI code leads to an error in the venv of your A1111 install.


Add collaborators to this repo

Comment below to be added as a collaborator
We will all be using this repository today. Even though it's public right now, you will not be able to make changes until you're given the correct permissions. We've automated this process via the GitHub API. Once you comment, we will add you as a collaborator.
You'll start to receive a lot of emails. (❗) You can slow these down immediately by clicking the Unwatch button at the top of the page and selecting either the Participating and @mentions or Ignore option.

Leave a comment here!
italics
bold

this
is
a
list

Leaving a comment to be added as a collaborator

Leaving comment to be added as collaborator

This is a comment for the gitHub class

Hello..please add me as collaborator

Hello, please add me as collaborator.

Hello..please add me as collaborator

Hello .. Please add me a collaborator.

Leaving a comment

Hello

Hello,   Please add me as a collabrator

Hello, Please add me as a collabrator

Hello!

Hi,
Get it.

Hi

Got it
On Tue, Aug 20, 2024 at 10:16 AM rjiang13 @.***> wrote:

Hi,
Get it.
—
Reply to this email directly, view it on GitHub
https://github.com/Coveros-GitHub-Training/smbc-class-2/issues/1#issuecomment-2298975373,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKU7QZUHX22WT2K7ZVWIZFTZSNFVJAVCNFSM6AAAAABMY75TPWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJYHE3TKMZXGM
.
You are receiving this because you commented.Message ID:
@.***>

--
Regards
Sharan Matte


TypeError: Cannot read property 'getContext' of undefined

Hello am trying to retrieve one record from the database am getting this error "TypeError: Cannot read property 'getContext' of undefined". What could be the issue?
Below is my code in an entity repository that's being called in a service in Nest Js Framework
async validateUserPassword(signInCredentialsDto: SignInCredentialsDto): Promise<LoginUsers | null> {         const { email, password } = signInCredentialsDto;         const user = await this.em.findOne(LoginUsers, { email: email })         console.log(user)         if(user && await user.validatePassword(password)){             return user;         }else{             return null;         }     }

Please provide executable reproduction. There is no way anybody can help based on just error message (not even full stack trace).
Will close this, issues should follow the issue template and need to be verifiable - will be happy to reopen if you can provide something I can actually try.

Please provide executable reproduction. There is no way anybody can help based on just error message (not even full stack trace).
Will close this, issues should follow the issue template and need to be verifiable - will be happy to reopen if you can provide something I can actually try.

Okay let me try to give you a proper picture of what am doing, am working on graphql api using nest js framework, am trying to login a person, so at the resolver level i have this code running
import { AuthService } from "../services/auth.service"; @Resolver(of => LoginUsers) export class AuthResolver { @Mutation(returns => AccessToken)     signInLoginUser(         @Args("signInCredentials") signInCredentialsDto: SignInCredentialsDto,     ) {         return this.authService.signIn(signInCredentialsDto);     } }
the above code calls the authService, the authService executes this code
`
import { LoginUsersRepository } from 'src/users/repositories/loginusers.repository';
@Injectable()
export class AuthService {
constructor(
private loginUsersRepository: LoginUsersRepository,
){}
async signIn(signInCredentialsDto: SignInCredentialsDto ): Promise{
const user: LoginUsers = await this.loginUsersRepository.validateUserPassword(signInCredentialsDto)
if(!user){
throw new UnauthorizedException('Invalid Credentials');
}
    const roleName = await user.getUserRole()
    const { email, roleId } = user;

    const payload: JwtPayload = { email, roleId, roleName };
    const accesstoken = new AccessToken();
    accesstoken.accessToken = await this.jwtService.sign(payload)
    return accesstoken;
}

}
`
the authService then calls the loginUsersRepository which has this code running
`
import { LoginUsers } from "../entities/loginusers.entity";
import { EntityRepository } from "@mikro-orm/mongodb";
import { Repository } from "@mikro-orm/core";
@Repository(LoginUsers)
export class LoginUsersRepository extends EntityRepository {
//....
async validateUserPassword(signInCredentialsDto: SignInCredentialsDto): Promise<LoginUsers | null> {
const { email, password } = signInCredentialsDto;
const user = await this.em.findOne(LoginUsers, { email: email })
console.log(user)
if(user && await user.validatePassword(password)){
return user;
}else{
return null;
}
}
}
 so when this codeconst user = await this.em.findOne(LoginUsers, { email: email })in the loginUsersRepository, i get this error on the terminal
TypeError: Cannot read property 'getContext' of undefined
at LoginUsersRepository.get em [as em] (/Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/node_modules/@mikro-orm/mongodb/MongoEntityRepository.js:18:25)
at LoginUsersRepository.validateUserPassword (/Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/dist/users/repositories/loginusers.repository.js:86:33)
at AuthService.signIn (/Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/dist/auth/services/auth.service.js:73:54)
at AuthResolver.signInLoginUser (/Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/dist/auth/resolvers/auth.resolver.js:30:33)
at /Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/node_modules/@nestjs/core/helpers/external-context-creator.js:69:33
at processTicksAndRejections (node:internal/process/task_queues:93:5)
at async target (/Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/node_modules/@nestjs/core/helpers/external-context-creator.js:76:28)
at async /Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/node_modules/@nestjs/core/helpers/external-proxy.js:9:24
`
am wondering what have i done wrong?
The code for the LoginUsers entity is this
`
import { Field, ObjectType, ID } from "@nestjs/graphql";
import { Roles } from "./roles.entity";
import * as bcrypt from 'bcrypt';
import { SubRoles } from "./subrole.entity";
import { ObjectId } from "@mikro-orm/mongodb";
import { Entity, EntityRepositoryType, ManyToOne, PrimaryKey, Property } from "@mikro-orm/core";
import { LoginUsersRepository } from "../repositories/loginusers.repository";
@ObjectType()
@Entity({ tableName: 'loginusers' })
export class LoginUsers {
[EntityRepositoryType]?: LoginUsersRepository;
@Field(() => ID)
@PrimaryKey()
public _id!: ObjectId
@Field()
@Property({ persist: true })
public email: string;
// @OneToOne({ inversedBy: 'distributor', orphanRemoval: true, type: AuthenticationSubInstance })
// public subInstance!: AuthenticationSubInstance;
@Field(type => SubRoles, { name: "subrole", nullable: true })
@ManyToOne({ persist: false, mapToPk: true, nullable: true })
public subRoleId?: SubRoles;
@Field(type => Roles, { name: "role", nullable: true })
@ManyToOne({ persist: false, mapToPk: true, nullable: true })
public roleId?: Roles;
@Field({ name: "roleName" })
public role: string
@Field({ nullable: true })
@Property({ persist: true })
public firstName: string;
@Field({ nullable: true })
@Property({ persist: true })
public lastName: string;
@Property({ persist: true })
public password: string;
@Property({ persist: true })
public salt: string;
@Field({ nullable: true })
@Property({ onCreate: () => new Date(), persist: true })
public createdAt: Date;
@Field({ nullable: true })
@Property({ onUpdate: () => new Date(), onCreate: () => new Date(), persist: true })
public updatedAt: Date;
async getUserRole(): Promise {
if (this.roleId != null) {
// console.log(this.roleId)
// const role = await getModelForClass(Roles).findOne({ _id: this.roleId }).exec()
return "Trial";
} else {
return null
}
}
async validatePassword(password: string): Promise {
console.log(this.password)
const hash = await bcrypt.hash(password, this.salt);
return hash === this.password;
}
}
`
and the configs for the MikroORM configs are these
`
import { MikroOrmModuleOptions } from '@mikro-orm/nestjs'
import * as config from 'config';
import { AuthenticationInstance } from 'src/users/entities/authentication-instance.entity';
import { AuthenticationSubInstance } from 'src/users/entities/authentication-subinstance.entity';
import { LoginUserRolePivotTable } from 'src/users/entities/loginuser-role.pivottable.entity';
import { LoginUserSubRolePivotTable } from 'src/users/entities/loginuser-subrole.pivottable.entity';
import { LoginUsers } from 'src/users/entities/loginusers.entity';
import { RolesPermissions } from 'src/users/entities/roles-permissions.pivottable.entity';
import { Roles } from 'src/users/entities/roles.entity';
import { SubRolePermissions } from 'src/users/entities/subrole-permissions.pivottable.entity';
import { SubRoles } from 'src/users/entities/subrole.entity';
import { Permissions } from 'src/users/entities/permissions.entity';
const { type, host, port, username, password, database, authSource } = config.get('db');
export const mikroOrmConfig: MikroOrmModuleOptions = {
type: 'mongo',
dbName: database,
debug: true,
entities: [
LoginUsers,
Roles,
AuthenticationInstance,
AuthenticationSubInstance,
LoginUserRolePivotTable,
LoginUserSubRolePivotTable,
Permissions,
RolesPermissions,
SubRolePermissions,
SubRoles,
],
baseDir: __dirname,
clientUrl: type + "://" + username + ":" + password + "@" + host + ":" + port + "/?" + authSource + "=admin&readPreference=primary&appname=MongoDB%20Compass&ssl=false",
}
`
What is it am i doing wrong? Please help

Okay let me try to give you a proper picture of what am doing, am working on graphql api using nest js framework, am trying to login a person, so at the resolver level i have this code running
import { AuthService } from "../services/auth.service"; @Resolver(of => LoginUsers) export class AuthResolver { @Mutation(returns => AccessToken)     signInLoginUser(         @Args("signInCredentials") signInCredentialsDto: SignInCredentialsDto,     ) {         return this.authService.signIn(signInCredentialsDto);     } }
the above code calls the authService, the authService executes this code
`
import { LoginUsersRepository } from 'src/users/repositories/loginusers.repository';
@Injectable()
export class AuthService {
constructor(
private loginUsersRepository: LoginUsersRepository,
){}
async signIn(signInCredentialsDto: SignInCredentialsDto ): Promise{
const user: LoginUsers = await this.loginUsersRepository.validateUserPassword(signInCredentialsDto)
if(!user){
throw new UnauthorizedException('Invalid Credentials');
}
    const roleName = await user.getUserRole()
    const { email, roleId } = user;

    const payload: JwtPayload = { email, roleId, roleName };
    const accesstoken = new AccessToken();
    accesstoken.accessToken = await this.jwtService.sign(payload)
    return accesstoken;
}

}
`
the authService then calls the loginUsersRepository which has this code running
`
import { LoginUsers } from "../entities/loginusers.entity";
import { EntityRepository } from "@mikro-orm/mongodb";
import { Repository } from "@mikro-orm/core";
@Repository(LoginUsers)
export class LoginUsersRepository extends EntityRepository {
//....
async validateUserPassword(signInCredentialsDto: SignInCredentialsDto): Promise<LoginUsers | null> {
const { email, password } = signInCredentialsDto;
const user = await this.em.findOne(LoginUsers, { email: email })
console.log(user)
if(user && await user.validatePassword(password)){
return user;
}else{
return null;
}
}
}
 so when this codeconst user = await this.em.findOne(LoginUsers, { email: email })in the loginUsersRepository, i get this error on the terminal
TypeError: Cannot read property 'getContext' of undefined
at LoginUsersRepository.get em [as em] (/Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/node_modules/@mikro-orm/mongodb/MongoEntityRepository.js:18:25)
at LoginUsersRepository.validateUserPassword (/Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/dist/users/repositories/loginusers.repository.js:86:33)
at AuthService.signIn (/Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/dist/auth/services/auth.service.js:73:54)
at AuthResolver.signInLoginUser (/Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/dist/auth/resolvers/auth.resolver.js:30:33)
at /Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/node_modules/@nestjs/core/helpers/external-context-creator.js:69:33
at processTicksAndRejections (node:internal/process/task_queues:93:5)
at async target (/Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/node_modules/@nestjs/core/helpers/external-context-creator.js:76:28)
at async /Users/leon/Documents/code/node/nest/mikroORM/graphql-users-service-mikroORM/node_modules/@nestjs/core/helpers/external-proxy.js:9:24
`
am wondering what have i done wrong?
The code for the LoginUsers entity is this
`
import { Field, ObjectType, ID } from "@nestjs/graphql";
import { Roles } from "./roles.entity";
import * as bcrypt from 'bcrypt';
import { SubRoles } from "./subrole.entity";
import { ObjectId } from "@mikro-orm/mongodb";
import { Entity, EntityRepositoryType, ManyToOne, PrimaryKey, Property } from "@mikro-orm/core";
import { LoginUsersRepository } from "../repositories/loginusers.repository";
@ObjectType()
@Entity({ tableName: 'loginusers' })
export class LoginUsers {
[EntityRepositoryType]?: LoginUsersRepository;
@Field(() => ID)
@PrimaryKey()
public _id!: ObjectId
@Field()
@Property({ persist: true })
public email: string;
// @OneToOne({ inversedBy: 'distributor', orphanRemoval: true, type: AuthenticationSubInstance })
// public subInstance!: AuthenticationSubInstance;
@Field(type => SubRoles, { name: "subrole", nullable: true })
@ManyToOne({ persist: false, mapToPk: true, nullable: true })
public subRoleId?: SubRoles;
@Field(type => Roles, { name: "role", nullable: true })
@ManyToOne({ persist: false, mapToPk: true, nullable: true })
public roleId?: Roles;
@Field({ name: "roleName" })
public role: string
@Field({ nullable: true })
@Property({ persist: true })
public firstName: string;
@Field({ nullable: true })
@Property({ persist: true })
public lastName: string;
@Property({ persist: true })
public password: string;
@Property({ persist: true })
public salt: string;
@Field({ nullable: true })
@Property({ onCreate: () => new Date(), persist: true })
public createdAt: Date;
@Field({ nullable: true })
@Property({ onUpdate: () => new Date(), onCreate: () => new Date(), persist: true })
public updatedAt: Date;
async getUserRole(): Promise {
if (this.roleId != null) {
// console.log(this.roleId)
// const role = await getModelForClass(Roles).findOne({ _id: this.roleId }).exec()
return "Trial";
} else {
return null
}
}
async validatePassword(password: string): Promise {
console.log(this.password)
const hash = await bcrypt.hash(password, this.salt);
return hash === this.password;
}
}
`
and the configs for the MikroORM configs are these
`
import { MikroOrmModuleOptions } from '@mikro-orm/nestjs'
import * as config from 'config';
import { AuthenticationInstance } from 'src/users/entities/authentication-instance.entity';
import { AuthenticationSubInstance } from 'src/users/entities/authentication-subinstance.entity';
import { LoginUserRolePivotTable } from 'src/users/entities/loginuser-role.pivottable.entity';
import { LoginUserSubRolePivotTable } from 'src/users/entities/loginuser-subrole.pivottable.entity';
import { LoginUsers } from 'src/users/entities/loginusers.entity';
import { RolesPermissions } from 'src/users/entities/roles-permissions.pivottable.entity';
import { Roles } from 'src/users/entities/roles.entity';
import { SubRolePermissions } from 'src/users/entities/subrole-permissions.pivottable.entity';
import { SubRoles } from 'src/users/entities/subrole.entity';
import { Permissions } from 'src/users/entities/permissions.entity';
const { type, host, port, username, password, database, authSource } = config.get('db');
export const mikroOrmConfig: MikroOrmModuleOptions = {
type: 'mongo',
dbName: database,
debug: true,
entities: [
LoginUsers,
Roles,
AuthenticationInstance,
AuthenticationSubInstance,
LoginUserRolePivotTable,
LoginUserSubRolePivotTable,
Permissions,
RolesPermissions,
SubRolePermissions,
SubRoles,
],
baseDir: __dirname,
clientUrl: type + "://" + username + ":" + password + "@" + host + ":" + port + "/?" + authSource + "=admin&readPreference=primary&appname=MongoDB%20Compass&ssl=false",
}
`
What is it am i doing wrong? Please help

This is close to being unreadable, please learn how to format code properly :] Anyway, I was asking for executable repro, not for snippets of your code.
Looking at this, I can already see you have some entity definitions wrong (e.g. using mapToPk means the type is the PK type, not the entity). But that won't be the problem here.
You have something wrong in the Nest DI part, as apparently it won't pass the EM instance to the repository automatically.
Try looking at the existing example repositories.

This is close to being unreadable, please learn how to format code properly :] Anyway, I was asking for executable repro, not for snippets of your code.
Looking at this, I can already see you have some entity definitions wrong (e.g. using mapToPk means the type is the PK type, not the entity). But that won't be the problem here.
You have something wrong in the Nest DI part, as apparently it won't pass the EM instance to the repository automatically.
Try looking at the existing example repositories.

I had the same problem, in my case I was declaring my custom repository as a provider and also importing it in the module configuration. Removing the repository from the providers array solved it.

maybe what is missing here is the @InjectRepository(FooRepository) decorator before argument declaration

Here is an example on how to get this error.
If you have a module of an entity Foo and also have a repository for Foo, you would have something like this
@Entity()
export class Foo {
  [EntityRepositoryType]?: FooRepository

  // other fields ...
}

@Repository(Foo)
export class FooRepository extends EntityRepository<Foo> {}

And in the module you would need to use MikroOrmModule.forFeature to register the entity and repository (using EntityRepositoryType in the entity), which would look something like:
@Module({
  imports: [MikroOrmModule.forFeature({ entities: [Foo] })],
  providers: [ /* foo services or providers */ ],
  controllers: [ /* foo controllers */ ]
})
export class FooModule {}

Later you think something like "I want to use this repository in other module, so I will export it" and you will do:
@Module({
  imports: [MikroOrmModule.forFeature({ entities: [Foo] })],
  providers: [ /* foo services or providers */, FooRepository], // repository added to providers
  exports: [FooRepository],
  controllers: [ /* foo controllers */ ]
})
export class FooModule {}

and in another module you would import FooModule and add to the constructor of your service FooRepository.
@Module({
  imports: [FooModule, /* bar module imports*/ ],
  providers: [ /* bar services or providers */ ],
  controllers: [ /* bar controllers */ ]
})
export class BarModule {}

@Injectable()
export class BarService {
  constructor(public readonly fooRepository: FooRepository, /* other things injected*/) {}
}

And this is what will cause the error when trying to use the repositories in difference places.
I'm not sure if this is intentional or if it's a bug/something not possible to do (Maybe @B4nan could say something about it).
To solve this you need to remove the FooRepository from providers and exports from the FooModule and to use it in the BarModule you must use MikroOrmModule.forFeature to register Foo entity and it's repository.
@Module({
  imports: [
    MikroOrmModule.forFeature({
      entities: [FooEntity, BarEntity, /* other entities */],
    }),
  ],
  providers: [ /* bar services or providers */ ],
  controllers: [ /* bar controllers */ ]
})
export class BarModule {}

This worked for me and hope this comment is good for people in the future.

I believe you should not export the repository like that, you should call the forFeature in the other module instead to have it available. Having it in the providers seems wrong too, the forFeature call is what registers the provider for giver repositories.

You haven't added
@Entity({ customRepository: () => UsersRepository })
in your entity declaration

I just ran into this same issue, It would be helpful if the Documentation for MikroORM with NestJS went over this sort of thing.


Generic MSM implementation

implements blst teams pippenger generically via traits.

[x] Cleanup commit messages
[x] Find out why blst c-kzg-4844 binding C# test failing
[x] Rebase on main (missing latest zkcrypto teams changes)
[x] Fix run-benchmarks.sh (zkcrypto team accidentally removed us)
[x] Add arkmsm feature flag (default: pippenger, if arkmsm flag - sequential version use arkmsm)

Merged into integration branch.


Could not compile asyncio

OS: centos7
[weiby@login async_server]$ cargo --version
cargo 1.34.0-nightly (b33ce7fc9 2019-02-19)
[weiby@login async_server]$ rustc --version
rustc 1.34.0-nightly (e1c6d0057 2019-02-22)

[weiby@login async-io-demo]$ cargo run --example async-echo
   Compiling asyncio v0.1.0 (/share/home/weiby/code/rust/async-io-demo)
error[E0432]: unresolved imports `std::task::LocalWaker`, `std::task::UnsafeWake`
  --> src/executor.rs:12:23
   |
12 | use std::task::{self, LocalWaker, UnsafeWake, Waker};
   |                       ^^^^^^^^^^  ^^^^^^^^^^ no `UnsafeWake` in `task`
   |                       |
   |                       no `LocalWaker` in `task`

error[E0432]: unresolved import `std::task::LocalWaker`
  --> src/fs_future.rs:10:23
   |
10 | use std::task::{self, LocalWaker};
   |                       ^^^^^^^^^^ no `LocalWaker` in `task`

warning: unused import: `Cell`
 --> src/executor.rs:5:17
  |
5 | use std::cell::{Cell, RefCell};
  |                 ^^^^
  |
  = note: #[warn(unused_imports)] on by default

error: aborting due to 2 previous errors

For more information about this error, try `rustc --explain E0432`.
error: Could not compile `asyncio`.

To learn more, run the command again with --verbose.

There are many alterations in std::lib about rust asynchronous abstraction recently, this repo does not support rust-1.34. You can compile the branch master or 1.33 in rust-1.33-nightly, you can also compile the branch 1.32 in rust-1.32-nightly.

OK, thanks!


33 create backdrop component from modal

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Imgur upload

I wanted to ask how much is expiration date IMGBB upload ?

The code for upload expiration time is set to 10 minutes (I've tested this, and it does delete after 10 minutes)

fetch(`https://api.imgbb.com/1/upload?expiration=600&key=${IMGBB_TOKEN}

When editing in Photopea it seems to upload an image with a 1 minute expiration (I think this is meant as a temporary measure in order to upload it to that website though, so I don't think this one matters)

fetch(`https://api.imgbb.com/1/upload?expiration=60&key=${IMGBB_TOKEN}

Is it private when it's uploaded to IMGBB? Sorry for lot of questions

Is it private when it's uploaded to IMGBB? Sorry for lot of questions


Remove commented out code

Just general code hygiene since you're already using a VCS to keep code around.

Good. Thanks for the fix


trafficmanager.net (Azure) giving false positives

So far all the Azure takeovers i've found that resolve to *.trafficmanager.net seem to be FP
thanks

Thank you @AnotherWayIn I started noticing this a while back.
I haven't found a proper way to remediate this issue, it seems the only way to rule out a false positive would be to attempt a takeover.

@haccer if it resolves to an IP it's taken the only other way i know is to to use the Azure CLI as it requires auth to check if the subdomain is available.


Could libm be removed ?

It seems that no_std could works well without libm. I want to know ther reason about import it? For performance?

My gut feeling is "no" but I forgot why. :upside_down_face:
In the past we used libm because the Rust standard library did not support the required floating point instructions under certain circumstances such as compilation to WebAssembly in no_std mode.
I don't know if this is still the case ...
Importants links:

https://github.com/rust-lang/libm
https://github.com/paritytech/wasmi/issues/240
https://github.com/paritytech/wasmi/pull/241

We indeed need libm since some f32 and f64 methods such as fract and trunc are not available in Rust's core library unfortunately. This may change in the future though since some people are working on that.
Compare the following docs for f32:

std: https://doc.rust-lang.org/std/primitive.f32.html
core: https://doc.rust-lang.org/core/primitive.f32.html


Leverages ES6 for chp06/NOC02

Leverages ES6

Uses classes
Scope variables

Thank you so much for this! I'm finally getting to review this and would like to port everything over to ES6 like in #71. While const may be more "correct" I'm thinking I might like to leave all the variables as let to be more beginner friendly, what do you think?


CSLC-S1 Final SAS Acceptance Test

Ticket to track acceptance testing for the CSLC-S1 SAS Final delivery.
The container tarball for the delivery can be found in Artifactory-FN under the path general/gov/nasa/jpl/opera/adt/cslc_s1/r6/final/dockerimg_cslc_s1_final_0.5.0.tar, test inputs and expected outputs can be found under general/gov/nasa/jpl/opera/adt/cslc_s1/r6/final/delivery_cslc_s1_final_0.5.0.zip. Documentation for the delivery is under general/gov/nasa/jpl/opera/adt/cslc_s1/r6/final/documents/
A new wiki page needs to be created to capture the Acceptance Testing procedure for the Final delivery. The procedure for the previous CalVal delivery may be used as a starting point.

Acceptance testing was completed without issue. Wiki page is available here: https://github.com/nasa/opera-sds-pge/wiki/CSLC-S1-Final-Acceptance-Testing-Instructions


Apply tips to reduce the filesize of generated notebooks

https://fredrikekre.github.io/Literate.jl/v2/tips/#notebook-filesize

dup of https://github.com/JuliaReach/ReachabilityAnalysis.jl/issues/428

Reopening since #428 got closed. Especially the DisplayAs should help a lot.


BigDecimal.Precision have no effect

I testet you example code. There I have only changed a "." to an "," , because in europe point and comma are switched.
Without changing point to comma, the error looks like

But the precision of the number is a higher precision then yours. Seems to be 372 instead of the setted 200, because the Mantisse is 372 characters long.

Set the static member:
BigDecimal.AlwaysTruncate = true;
This will constrain the number of digits to the right of the decimal separator to the value specified in BigDecimal.Precision. Well, to within +/- 1 digit of the precision, anyways.
With BigDecimal.AlwaysTruncate set to true, it will truncate the BigDecimal after every arithmetic operation.
With BigDecimal.AlwaysTruncate set to false, it will never truncate the numbers on its own. The user is in control of when, if ever, the number should be truncated, by calling the Truncate method manually; Usually after a series of operations, but before returning/presenting the final result would be a common place to do so
With BigDecimal.AlwaysTruncate set to false, any newly constructed BigDecimal begins its life with up to Precision digits in length (if needed. 1/4 is still going to be just 0.25), and any arithmetic operations that results in a longer decimal representation (e.g. multiplication) will  result in a longer decimal representation.
The default value for BigDecimal.AlwaysTruncate is false.
I figured its better to keep the trailing digits by default, requiring the behavior that throws them away be set explicitly,
than to toss away digits of precision to peoples' calculations by default, requiring that keeping the full precision be made explicit.
This all should be reflected in the readme. If its not, I will add it at once.
I should also probably state this in the readme, if it isn't already:
Setting BigDecimal.AlwaysTruncate = true; may significantly boost performance.
If you are finding your calculations are taking a long time to return, and you find that your intermediate values have decimal representations that have grown obscenely long, setting BigDecimal.AlwaysTruncate = true; should see immediate gains in speed at the cost of a little precision.

I perhaps misunderstood what you were saying.
You also seem to be saying that parsing numbers is failing, if you use a comma as a decimal separator.
All you have to do to make that work is set the CurrentCulture to your current culture, or any culture who has the same number formatting rules as yours. Argentina , for example, also uses commas as decimal separators, and periods to group digits to the left of the decimal separator, into groups of three, so we will use that as an example:
CultureInfo argentina = CultureInfo.GetCultureInfoByIetfLanguageTag("es-AR");
CultureInfo.CurrentCulture = argentina ;

When parsing, the library uses the properties of CultureInfo.CurrentCulture.NumberFormat to parse a string into a BigDecimal, so it should do the right thing if you just set CultureInfo.CurrentCulture.
This affects only the thread that runs such a statement. If your application is multi-threaded, consider setting DefaultThreadCurrentCulture instead.

Set the static member: BigDecimal.AlwaysTruncate = true;

Ok. I have added the line to the top of your example.
Now it is less precision then before, but the result is still different to your output:

You also seem to be saying that parsing numbers is failing, if you use a comma as a decimal separator.
All you have to do to make that work is set the CurrentCulture to your current culture,

I am not sure, if it is better, that every program which using BigDecimal, integrating the part with CurrentCulture or if it is better, if BigDecimal itself includes the part with "CurrentCulture", so that a string with decimal-point can everytime in every country direct converted to a BigDecimal.
Currently in Windows it is so, that in cultures, which using a comma in Floating point numbers, the point (".") will be used in programs for numbers and the comma (",") is in numbers, that are outputted to command line.
And for example in the Powershell ist is so, that I input
14.8 + 17.4
and it outputs
32,2
Thats the Microsoft-way.
Java and Python don't using comma. They input and output numbers with point.

but the result is still different to your output:

I'm not understanding the issue here...
Is it that the the second time it displays that long number, it doesn't have a decimal point in it?
e.g. "64079000015605783843835009599722600 ..." ?
If so, well that's because its literally displaying the Mantissa and the exponent:
Console.WriteLine($"{almostInteger.Mantissa}");
//<PHONE_NUMBER>5605783843835009599722600391518338454771405992063505171997949372951472701529422358634915404757740005027416333594519349348824890921372720968246769717009339797514969003242216358994087504831741
Console.WriteLine($"{almostInteger.Exponent}");
// -193

If you were expecting each line to be output twice, that's not necessarily what its doing or meant to happen.
The code comments are supposed to reflect what's output by the console. But the code comments themselves don't print out to the console, so they are tough to compare. But they were not designed to compare. The code in the readme wasn't meant to be a test; it was meant to give people an example of what using the library would look like, and give them an idea what the output would look like.
You could use it for a test. If you wrap every code comment with a Console.WriteLine call, you do see two identical lines of output for calculated object:
Console.WriteLine($"{BigDecimal.Precision}");
Console.WriteLine($"5000");
BigDecimal.Precision = 200; // Tone down the precision for this demo.
Console.WriteLine($"{BigDecimal.Precision}");
Console.WriteLine($"200");

BigDecimal goldenRatio = BigDecimal.Divide(BigDecimal.Add(BigDecimal.One, BigDecimal.Pow(5d, 0.5d)), BigDecimal.Parse("2"));
BigDecimal almostInteger = BigDecimal.Pow(goldenRatio, 23);
Console.WriteLine($"{almostInteger}");
Console.WriteLine($"64079.000015605783843835009599722600391518338454771405992063505171997949372951472701529422358634915404757740005027416333594519349348824890921372720968246769717009339797514969003242216358994087504831741");

Console.WriteLine($"{almostInteger.Mantissa}");
Console.WriteLine($"64079000015605783843835009599722600391518338454771405992063505171997949372951472701529422358634915404757740005027416333594519349348824890921372720968246769717009339797514969003242216358994087504831741");
Console.WriteLine($"{almostInteger.Exponent}");
Console.WriteLine($"-193");

BigDecimal X = BigDecimal.Parse("0.000551876379690949227373068432671081677704194260485651214128035320088300220750");
Console.WriteLine($"{X}");
Console.WriteLine($"0.00055187637969094922737306843267108167770419426048565121412803532008830022075");

BigDecimal result = BigDecimal.Divide(BigDecimal.One, X);
Console.WriteLine($"{result}");
Console.WriteLine("1812.000000000000000000000000000000000000000000000000000000000000000000000001");

If you want tests, there is a whole test project with 135 tests.

If you were expecting each line to be output twice, that's not necessarily what its doing or meant to happen. The code comments are supposed to reflect what's output by the console.

I know it.
But the result is different to that what you have written in the comments.
And here the output of your now published program:

-368 ist NOT the same like -193.
And the number "1812,000000000000000000000000000000000000000000000000000000000000000000000001812000000000000000000000000000000000000000000000000000000000000000000000001812000000000000000000000000000000000000000000000000000000000000000000000001"
have NOT the same precision like
"1812.000000000000000000000000000000000000000000000000000000000000000000000001"

Oh, and here, where I added a BigDecimal.AlwaysTruncate = true; at the top of your program.

But again,
-200 ist NOT the same like -193.
And
"1812,000000000000000000000000000000000000000000000000000000000000000000000001812000000000000000000000000000000000000000000000000000000000000000000000001812"
have not the same precision like
"1812.000000000000000000000000000000000000000000000000000000000000000000000001"

-368 ist NOT the same like -193

Fair enough. Ill update the Readme to reflect the true, correct value.

It it so.


Scheduler ,Controller has only one replica ,when Node out of service ,Hwameistor will does not work

from zhenguang:
Scheduler ,Controller has only one replica ,when Node out of service ,Hwameistor will does not work

Kubernetes has its own scheduler and controller, however, Hwameistor can also provide HA provisioning.

HwameiStor currently support HA provisioning.  number of replicas can be configured with helm value.


reduce button height

How can I reduce the button height? I tried isDense = true , padding: EdgeInsets.all(0), and customButton to reduce the height, but none of them worked for my case. I still can see the dropdownButton is larger than my customButton.
DropdownButtonHideUnderline(
              child: DropdownButtonFormField2(
            isDense: true,
            buttonStyleData: ButtonStyleData(padding: EdgeInsets.all(0)),
            menuItemStyleData: MenuItemStyleData(padding: EdgeInsets.all(0)),
            dropdownStyleData: DropdownStyleData(padding: EdgeInsets.all(0)),
            customButton: Container(
              height: 30,
              color: Colors.pink,
              child: Text(
                widget.model.type,
                style: TextStyle(
                  color: Colors.black,
                ),
              ),
            ),

Please upgrade to latest version and test this again.
Feel free to ask for re-open if it is not solved yet.


Missing instructions on how to upload to the App Folder

Hello, thanks for the tool.
I followed the instructions on the README, giving permission only to the App Folder. Any command that I issue gets me an access denied message, for instance:
% onedrive-uploader ls /
Could not list: received unexpected status code 403: Access denied (accessDenied)

I suppose I should point to the App Folder, but I don't know what that is and couldn't find instructions about this. In my OneDrive, an Apps (actually Aplicativos because it's in Brazilian Portuguese) folder was created automatically, but there's nothing inside it. I tried creating an onedrive-uploader folder inside it to access that, but still access denied. I tried mkdir and upload but they all get status code 403.
The documentation from Microsoft mentions a special folder namespace, but that doesn't work either (I guess it works only if used in the REST API calls within onedrive-uploader)...
If it helps to know, in the onedrive-uploader config process, I chose options:
Available scopes:
1) Default (Files.Read, Files.ReadWrite, Files.Read.All, Files.ReadWrite.All, offline_access)
2) App Root (Files.ReadWrite.AppFolder, offline_access)
3) Custom
Select Scopes [1]: 2
Available Drive Roots:
1) Default (/drive/root)
2) App Root (/drive/special/approot)
3) Custom
Select Drive Root [1]: 2

Appreciate if you could help me with this. Thanks!

Update: I was trying the upload on my work Microsoft account (managed by my university). I performed the login on my personal Microsoft account and it worked. The Apps/onedrive-uploader folder was created and I was able to upload a file. There's probably some constraint on my work account that prevents it from working.
Anyways, I'll close the issue as there is no need for instructions on how to upload to the App folder. It sets it as root internally.


Update Dockerfile to build an image

Update Dockerfile to install on local environment.
civitaspo/redash-qr dose not exist on dockerhub. So I need to build a docker image.

Run an instruction on README on Dockerfile.
Remove "does something useful" from spec/redash/query/replace_spec.rb.

I'm sorry for quite slow replay. Dockerfile was updated to remove ARG and 'ENV'.  --env-file option should be used.  @civitaspo

Maybe we doesn't need Use Docker section. Because I removed ARG and ENV from Dockerfile.

thx


Update threat-intelligence-integration.md

cc: @yelevin

@rijutakapoor2 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@batamig: I'm sorry - only the author of this article, @yelevin, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

#label:"aq-pr-triaged"

We'll make that correction later. It's not a blocker.
#sign-off

@ktoliver : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@yelevin I incorporated your requested revision. Merging now.

@ktoliver Thanks Kristine!


bug(body):Modify the type of Body to io.io.ReadCloser

Hi Yuedong, could you please remove the comment lines that are not be used anymore. Thanks.


fix broken link and move links to bottom

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @curiousjazz77 isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards,
CLA GitHub bot

Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement.
After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.

User @curiousjazz77 isn't covered by a CLA. They will need to complete the form at https://identity.linuxfoundation.org/projects/cncf

Regards, CLA GitHub bot

Hi I submitted the CLA ~30 minutes ago.


Create static obstacles to the map

The obstacles should be stationary on the map created in #3 .

I'll work on this next. I'll be implementing the Box2D physics engine to handle collisions.

Done #20


Add a search module bar to the landscape screen

Prerequisite

[ ] Add a button to hide the properties form component (needed on small device screens)
[ ] Memorize in local storage the hide/show preference options selected by the user from the minimap/presetConfiguration/propertiesForm components. This will avoid the annoying situation of having to hide or show components every time they press F5 or access JHipster Lite. ComponentsVisibilityRepository-> LocalStorageComponentsVisibilityRepository
[ ] Use an icon on the minimap instead of the large OPEN MINIMAP button to optimize screen space

TODO

[ ] (work in progress...)

Demo of the prototype to show the viability of this feature
The recorded video missed some frames and is lagging, but it's super smooth to use. Please ignore the search button, as it wasn't needed.
https://github.com/user-attachments/assets/d3ab75c1-0138-4628-a67e-d769ba6be938

Thanks @renanfranca  but for the 1st version, keep it simple plz:

search module bar
highlight the modules related to the input text
it should be closed to your video

No need local storage, no need minimap, no need to hide properties, etc...
At least for a 1st version. The other points can be discussed further, after some 1st feedbacks

I updated the TODO in the description to focus on small steps and quick delivery. I removed the Prerequisites.

TODO (edited: 20241012)
[ ] Implement a search functionality in the modules bar that identifies the module/feature by name as each letter is typed.
[ ] Highlight the first module/feature that matches the typed letters in the search bar.
[ ] Scroll the screen to the highlighted module if it is not visible in the current viewport.
[ ] Reset the screen position to the initial landscape layout when the search bar is cleared.
[ ] Remove the hilight when the search bar is cleared.
[ ] Hide the search bar on devices with screens smaller than or equal to 1024px, as it becomes impractical to use without the option to hide other components.

Thanks for the feedback, @pascalgrimaud, and for bringing me back down to earth, haha. I was so confident that it was a killer feature that I was trying to make the most of it. But it's better to collect other opinions.

Adding a bounty for the amount of work and this really nice feature.
Thanks for your hard work @renanfranca

Thank you very much @pascalgrimaud! I am looking forward to the feedback from everyone who can try it; I am all ears ;)
I am going to share the demonstration video here too:
https://github.com/user-attachments/assets/b09eede8-6a7e-4f8d-bf18-4523f123915a

@pascalgrimaud: Bounty Claimed  https://opencollective.com/generator-jhipster/expenses/226386. Thanks 💙😄

@renanfranca : approved


Feature Request: add method to convert Request to RFC 2616 Format

Ever since I ran into https://marketplace.visualstudio.com/items?itemName=humao.rest-client I have grown attached to writing HTTP requests like this:
POST https://example.com/comments HTTP/1.1
content-type: application/json

{
    "name": "sample",
    "time": "Wed, 21 Oct 2015 18:27:50 GMT"
}

From this format these requests can be easily executed in a dedicated REST client and converted into, e.g., curl command lines etc.
I'd love to see, e.g., a def .toRfc2616 (or a catchier name) def in Request so one can convert a request into this format for easier debugging and experimenting with HTTP requests.

Sounds cool, shouldn't be a problem as we already has toCurl converter :)

@phdoerfler, do you need support for ByteArrayBody, ByteBufferBody, InputStreamBody or StreamBody? If not, examples like that POST above should be ok for now.

@rojekp @adamw thanks 🙂


Fix create election bugs

[x] The export JSON function correctly checks the marshaled data instead of the newly typed configuration.
[x] Fixes the condition where MaxN should be less or equal to Choices length in selects (MaxN > Choices.length and not MaxN >= Choices.length)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3004

Relevant Lines:
5487

💛  - Coveralls


Add CITATION.cff

Description of new feature
GitHub has just added support for CITATION.cfffiles
I assume that we might already have a citation in mind, so I thought I'd bring it to our collective attention.

In fact, I have a browser tab open to https://citation-file-format.github.io/ The citation is in the Zenodo badge. A CITATION.cff file would bring more attention to it.

Thanks for the reminder, it didn't occur to me to check the badges for a DOI. It looks like we'd be duplicating some of our auto-generated content like contributor information etc. I wonder if there is an easy tool to integrate that, or whether we need to add something to the release process to generate a new CITATION.cff.

Looking at the structure of a CITATION.cff, I think it could be hand-written. The DOI doesn't change: I have the badge linked to the versionless DOI, which always points to the latest version. I think it's actually a problem that Zenodo defines the authors to be the set of contributors to the repository, in part because some people contribute a lot more than others (the variance is huge), but also because some people contributed to scikit-hep/awkward-0.x and not scikit-hep/awkward-1.0 (different repos). The contributors to scikit-hep/awkward-0.x are in the allcontributors list because I put them in there manually.
But if we want a shorter list for CITATION.cff, where do we draw the cut-off? I suppose this is why you were considering auto-generating the CITATION.cff, to include new authors as they appear, though the cut-off of people who made substantial contributions would be difficult to automate (number of lines changes?). Also, even though a lot of people made significant contributions, adding a big block of names in the references section of a paper only increases page count, and some journals include the references section in the page count that limits the lengths of articles.
For these practical reasons, perhaps it should be just "Jim Pivarski et al"? (With a strong emphasis on the "et al".) This way, it doesn't get too big in references sections and the link back here has pictures of everybody who contributed—something people find if they click through the link, which is to say, if they're interested. For years, ROOT was cited with just two names (Rene and Fons), although the Zenodo link has 30 names (still much less than the number of people who have contributed to ROOT, 282). I think those 30 names are people who are now or have been on the ROOT Team page, but Awkward Array doesn't have a well-defined team.
Actually, let me put a bit more thought into this. Some people have been funded to work on Awkward Array. They are:

@jpivarski / Jim Pivarski, Princeton
@ianna / Ianna Osborne, Princeton
@henryiii / Henry Schreiner, Princeton
@ioanaif / Ioana Ifrim, Princeton
@trickarcher / Anish Biswas, Manipal Institute of Technology (as GSoC and IRIS-HEP Fellow)
@reikdas / Pratyush Das,, Institute Of Engineering and Management, Kolkata (at that time, now Purdue, as an IRIS-HEP Fellow)
@EscottC / Charles Escott, Sacred Heart University (at that time, now Columbia, as a GSoC student)
@Jayd-1234 / Jaydeep Nandi, National Institute of Technology, Silchar (as a GSoC student, though his involvement was at the very beginning of when it was called "Awkward Array")

But using that to define the list wouldn't count people who made substantial contributions, like @nsmith-, @drahnreb, @veprbl, @chrisburr, and you.
Now that you're all linked into this thread, maybe you have opinions/preferences? Am I worrying too much about making the reference a big block of names by including everybody? (27 people in .all-contributorsrc, which is less than ROOT's curated list of 30 names.)

My personal take is favouring simplicity over adding infrastructure to keep track of a citation file, but I'm perhaps a bit blasé when it comes to the premise in the first place. So, at least for my name, +0 on including in a CITATION.cff file, and +1 on keeping it simple with Jim Pivarski et al.

+1 on keeping it simple with Jim Pivarski et al.

+1

One irritating thing is it seems the CITATION file has the version number in it - having another place (sometimes the only place) to change a version number is really a step backward for some projects. "Last GitHub release" would be really nice instead. :)
For names, I tend to prefer keeping a full author list then using a rule to truncate all of them (X names et. al. after a limit of Y names), but for software, this likely is hard to keep up (if all-contributors adds support, that might be really nice). Maybe the top X(=3?) contributors on GitHub (they are sorted in the GH UI), or anyone who has contributors more than X% (%10?), etc. I think the rule proposed above could be "list of people who have creative control over the software, et al". I'm mostly looking for a way to make this a suggestion that can apply to other projects. Some projects have more than one core developer; boost-histogram would likely need to be @HDembinski and me at the least. It would be nice to adopt a community guideline. (@danielskatz might have suggestions or input here?) - I'd be happy to propose a page to scikit-hep.org/developer .

It would be more effective to open an issue in https://github.com/citation-file-format/citation-file-format for feature requests or format changes that to just comment about them here :)

perhaps a feature request to all-contributors too?

For Parsl, we decided that all repo contributors with non-trivial/typo changes would be added as authors, in addition to other non-repo contributors

It would be more effective to open an issue

I haven't even set this up in a single repo yet, so probably not quite ready for that, but yes, I will if it's a problem. I first might just see what it does if you leave that blank, for example.

:wave: Joining this Issue's discussion given thoughts / rough edges in https://github.com/scikit-hep/pyhf/issues/1541. I think one of the problems is that GitHub isn't being very clear on what parts of the CFF spec they support, as it clearly isn't all of it, but only GitHub can answer that so we'll need to open an Issue.

During the release of pyhf v0.6.3 we noticed some unexpected issues with CITATION.cff that we didn't have with .zenodo.json (c.f. https://github.com/scikit-hep/pyhf/issues/1541#issuecomment-913992537).

Closed by #1257


Add Postman to windows workstation

for API calls to Vault.  Should also create a desktop shortcut for this.

This is fixed in the latest workstation image.