Add "Not" Condition Function

As I understand it should be quite straightforward to add such a feature because there are already great analogues. If you don't mind I would to open PR and suggest to do it myself, although I'm totally newbie in Haskell world and if you give me some contribution guide, I will do my best to extend stratosphere functionality :) The main question for me: what is the workflow to contribute, for example is there CI tests or run its locally is enough?
Thank you!

Hey @Znack! Sure, I can help you contribute.
First, you should go to the file for Stratosphere.Values. Here it is on Github: https://github.com/frontrowed/stratosphere/blob/master/library/Stratosphere/Values.hs
What we want to do is add the Not function to the Val a type. Here is the definition of that: https://github.com/frontrowed/stratosphere/blob/a91f4251437b13e067883270e01aa6830a45c8ee/library/Stratosphere/Values.hs#L39-L52
See how all of the intrinsic functions are defined here? We just need to add a constructor for Not. I'm pretty sure it would look like:
Not (Val Bool)

A good place to put it is probably near the other bool functions, like right after Or.
Now we need to tell stratosphere how to serialize this to JSON. We do that by editing the definition of the ToJSON (Val a) and FromJSON (Val a) type classes.
https://github.com/frontrowed/stratosphere/blob/a91f4251437b13e067883270e01aa6830a45c8ee/library/Stratosphere/Values.hs#L61-L76
https://github.com/frontrowed/stratosphere/blob/a91f4251437b13e067883270e01aa6830a45c8ee/library/Stratosphere/Values.hs#L91-L114
Look at how some of the other intrinsic functions are defined to get a sense of what is required there.

We have a build set up with CircleCI, so don't worry about breaking anything :smile:  I will also review the PR you make of course, and I can provide any guidance you need there too. Let me know if you need more help!

Hello, thanks for such detailed answer, I have cloned repo, now everything looks quite clear, and I will start my first attempts to make things working shortly :)

@jdreaver if you want the GADT version to work, we could maybe convert between an untyped representation and a typed GADT version like here: http://augustss.blogspot.ie/2009/06/more-llvm-recently-someone-asked-me-on.html
The untyped version is easier to (de)serialize, but then you need a separate "type checking" phase from UntypedVal -> Maybe (TypedVal a) and a "type erasing" phase from TypedVal a -> UntypedVal.
May not be worth the trouble though. I am a little surprised Equals has the type it does. Do we use that anywhere at FR?

Ahh, darn. Sorry about this, you are right @Znack.
You've correctly identified the root issue here. The type of Equals is
Equals :: Val a -> Val a -> Val a

but we want
Equals :: Val a -> Val a -> Val Bool

Indeed, we don't usually use these comparison functions at Front Row because we are already in Haskell, so we just do any computation like this in Haskell. Supporting them is definitely important though. I'll try to take a stab at fixing this today.

 I'm going to see if your solution can work. As long as it is ergonomic to users (i.e. they shouldn't have to care what goes on under the hood), I'm not too worried about how hairy it is to implement.
I wonder if there is a short-term, lower-cost solution like adding some way to coerce Val a -> Val b. Then we could keep everything else as-is and just ask folks to coerce their Val values. We already have Val constructors that are essentially pluck the a in Val a out of thin air, like Ref Text and GetAtt Text Text.
Also, the only reason I have FromJSON is to help with testing, and for the goal of being able to use stratosphere to validate or lint CloudFormation templates. In reality, I don't think the latter is that useful, but having FromJSON around for testing is pretty neat. I'm wondering if we could just do without all the FromJSON instances and use the GADT without needing any special machinery to implement FromJSON.
Lastly, we could just get rid of any Bool types in Val a since they aren't quite accurate anyway. That means changing
And :: Val Bool -> Val Bool -> Val a
Or :: Val Bool -> Val Bool -> Val a

to
And :: Val a -> Val a -> Val a
Or :: Val a -> Val a -> Val a

That still doesn't fix when we expect a Bool though (although this wouldn't even work currently if we need a Val Bool AFIACT because of the dependence on the a type parameter).
Ah, decisions decisions :smile:

Yeah, it is looking like I encountered much deeper problem than I expected with Not :)
I've read those article (although it is still quite complicated for me and I'm not sure I understood all nuances there). I have also learned much deeper GADTs itself and made some experiments to understand the problem itself. And now I have few stupid questions :)
The main problem with GADTs and FromJSON instances is requirement that parseJSON have to return Parser (Val a) but with GADTs in some cases we will return more specific Parser (Val Bool) and it is unacceptable? I tried to do it and exactly got the compile-time error:
• Couldn't match type ‘a’ with ‘Bool’
      ‘a’ is a rigid type variable bound by
        the instance declaration
        at /Users/sergey/projects/delivery/deploy-bot/TypedWithGADTOnly.hs:32:10-25
      Expected type: Parser (Val a)
        Actual type: Parser (Val Bool)

There are few ways to solve this problem, one is looking like a dirty hack and I  wonder, is it really inappropriate? The method makes us to create data Hide f = forall a. Hide (f a) structure that will hide our own Val and than create instance of FromJSON for its: instance FromJSON (Hide Val) where ... . I tried to implement this one, although I was unable to extract the result from Hide after encoding :( Here is my attempt if you are curious (I've just updated gist of @cdparks adding Hide class + its instances and updated the main):
data Hide f =
  forall a. (Show a) =>
            Hide (f a)

class HideFromJSON f where
  hideParseJSON :: Value -> Parser (Hide f)

instance HideFromJSON Val where
  hideParseJSON (Object o) =
    case HashMap.toList o of
      [] -> fail "Empty object as val"
      [("If", o')] -> do
        Hide (If cond t f) <- parseJSON o' :: Parser (Hide (Val))
        pure $ Hide $ If cond t f
      [("And", o')] -> do
        Hide (And x y) <- parseJSON o' :: Parser (Hide (Val))
        pure $ Hide $ And x y
      -- ...

instance HideFromJSON f => FromJSON (Hide f) where
  parseJSON = hideParseJSON

main = do
  putStrLn $ "Typed     | " ++ show typed
  putStrLn $ "Encoded   | " ++ show encoded
  putStrLn $ "Decoded   | " ++ show decoded
  where
    typed =
      List
        [ And (Not (Equals (Int 1) (Int 2))) (Equals (Bool True) (Bool False))
        , Bool False
        ]
    encoded = encode typed
    Just (Hide decoded) = decode encoded :: Maybe (Hide Val)
--             ^ here I've got compile-time error

The error itself:
• Couldn't match expected type ‘p’ with actual type ‘Val a’
        because type variable ‘a’ would escape its scope
      This (rigid, skolem) type variable is bound by
        a pattern with constructor:
          Hide :: forall (f :: * -> *) a. Show a => f a -> Hide f

Anyway there is the second way with converting between an untyped representation and a typed GADT and this will help because now FromJSON can simply always return Untyped and there can not be any confusion for the compiler. Although with this method we have to write converter like typecheck.
All this stuff looking extremely interesting for me and I would be glad to assist you to make this done or anyway to follow the PR to learn a lot of useful things about Haskell :) If I can be useful, can you please guide me where to go and which way is more appropriate for Stratosphere?

Hey @Znack, thanks for all the research on this!
I think we have a few options here:

Use a GADT for Val a and use one of the methods outlined by you and @cdparks to convert between the untyped and typed representations in FromJSON (Val a)
Add some way to coerce Val a -> Val b
Use a GADT but add some "escape hatch" when reading Val a to just stuff anything not extremely simple in a ValJson Value or something. That is, we almost ignore trying to parse stuff like Equals that changes the type of a.
Use a GADT and also just remove FromJSON from stratosphere since we don't really need it and I don't know anyone that uses it. This might also decrease compile times, which are pretty high. I had some pipe dreams of building a library/executable on top of stratosphere to do linting on CloudFormation templates, but I don't have any plans to actually execute on that.

We've decided to let this issue stew for a bit and not make too hasty of a decision. I hesitate to make the "wrong" decision, make a backwards incompatible change that breaks peoples' code, and then have to fix it with another backwards incompatible change.

@MichaelXavier do you have any opinions on this? Do you use any of the boolean intrinsic functions, like And, Equal, Or, etc? Have you had issues with their poor types? We don't use them at Front Row so we've never encountered issues here.

Thanks for explanations @jdreaver, it is useful for me to understand the possible approaches here :)
Of course, I understand that such a decision should be considered with a lot of attention and there should be some time to gather a feedback. I will follow the issue and learn the accompanying topics, today I read a lot of articles about the GADTs and hope eventually understand it quite well 😄
Our use case is quite simple: we use not for SnapshotARN parameter of the RDS and if it is not empty use it. And while the issue is still under development I have already prepare the workaround, I just use plain Aeson Value:
accompanying


ENH: Update RTK for future proofing.

Using explicit typecasts for future-proofing
enums.  RTK treats enum values as integers and
enumerations interchangeably for pushing onto
a stack of integers.  Using explicit static_casts
makes code future proof when enum class is used.

Thanks @hjmjohnson. It was my intention to update it before the new ITK release candidate. If this is still planned for tomorrow, then I'll finish a few things today and suggest a newer RTK tag tomorrow morning if all nightly builds went fine.

@SimonRit This small change is needed for the updates to enumerations.  I'm going to merge this version to remove one complication in expanded testing.  A new PR with even newer RTK should be considered as a separate issue.


Fix GDExtension library resolution logic

Added x86, arm64-v8a and armeabi-v7a to the list of supported archs in the gdextension_export_plugin#_export_file(...) logic. These values are included in the set of p_features passed to the method, which caused them to be lumped in the features_wo_arch set.
When trying to find the library path, we use a predicate with the following logic:
[features_wo_arch, arch_tag](String p_feature) { return features_wo_arch.has(p_feature) || (p_feature == arch_tag); }

For a gdextension config file like the one below, this causes the first android entry (android.armeabi-v7a = ...) to always be returned regardless of archs since it always satisfies the predicate.
[configuration]

entry_symbol = "example_library_init"
compatibility_minimum = 4.1

[libraries]
linux.x86_64 = "res://libgdexample.so"

android.armeabi-v7a = "res://libgdexample.android.template_release.armeabi-v7a.so"
android.arm32 = "res://libgdexample.android.template_release.armeabi-v7a.so"
android.x86 = "res://x86/libgdexample.android.template_release.x86.so"
android.x86_32 = "res://x86/libgdexample.android.template_release.x86.so"
android.x86_64 = "res://libgdexample.android.template_release.x86_64.so"
android.arm64-v8a = "res://libgdexample.android.template_release.arm64-v8a.so"
android.arm64 = "res://libgdexample.android.template_release.arm64-v8a.so"

Fixes https://github.com/godotengine/godot/issues/82727

These architectures/feature tags are meant to be the Godot-specific ones (arm32, arm64, x86_32, x86_64).
I'm not sure we should start adding all the architectures identifiers which may be used on specific platforms there, keeping it standardized would be good. Maybe we just shouldn't add Android-specific arch identifiers as feature tags?

For a gdextension config file like the one below, this causes the first android entry (android.armeabi-v7a = ...) to always be returned regardless of archs since it always satisfies the predicate.

I would add a separate list of invalid architectures and skip ("unknown architecture" with error message) armeabi-v7a and arm64-v8a altogether. For consistency with other platforms (since everything else in Godot expect arm32 and arm64 instead).

Or maybe we should require to always specify architecture, currently it's not the case for macOS and iOS (since binary can be universal), but we can require to specify universal as architecture for these case and consider all entries without arch as invalid.

These architectures/feature tags are meant to be the Godot-specific ones (arm32, arm64, x86_32, x86_64).
I'm not sure we should start adding all the architectures identifiers which may be used on specific platforms there (e.g. aarch64 on Linux, x86-64 on macOS, x64 on Windows, etc.). Keeping it standardized would be good. Maybe we just shouldn't add Android-specific arch identifiers as feature tags?

That could be the approach; we add the Android specific ones automatically in the feature list when the Godot specific arch is selected, so we can either disable that logic or provide an error message to indicate to the user they can't be used in the gdextension config.

For a gdextension config file like the one below, this causes the first android entry (android.armeabi-v7a = ...) to always be returned regardless of archs since it always satisfies the predicate.

I would add a separate list of invalid architectures and skip ("unknown architecture" with error message) armeabi-v7a and arm64-v8a altogether. For consistency with other platforms (since everything else in Godot expect arm32 and arm64 instead).

To @akien-mga's point, the list would need to include the invalid architectures for all supported platforms to be consistent.

I've updated the fix to remove the Android specific abis from the feature list.

Thanks!


Swift Package

I'd like to use this in my apps but a Swift Package is missing

I'm going to add support of SwiftUI and then I will add Swift Package for you.
Thanks, Rony!

It was not easy to support UIHostingController and I found a global issue. List highlights the issue.

Now It fully supports SwiftUI cause you can use.puller modifier from SwiftUI's code. But It has an issue of UIHostingController similar like https://forums.swift.org/t/uihostingcontroller-inside-uiview-bug-when-moving/55061

The puller is ready to use, @ronyfadel 🎉


Where can I try out the latest features that haven't been merged into the LFE develop branch?

The LFE project tends to have a backlog of unmerged PRs, since the core contributors have many other responsibilities. However, a bleeding-edge branch is maintained, which includes all PRs that 1) seem sane, and 2) pass the LFE build and test suite in TravisCI.
That branch is currently maintained here:

https://github.com/lfe/lfe/tree/bleeding-edge

Any issues you uncover, please report to the appropriate PR -- thanks!
Enjoy :-)

We will have to work out how to manage the LFE repo. There are a number of things I have to try and merge in. I haven't had much time to work on it lately, but I will try and better myself.


Add a test for sentence-bert based answer correctness metrics

Hi @matanor , I thought that tetst_metrics.py should be fixed. Is this PR in reference to issue https://github.com/IBM/unitxt/issues/1136 that I assigned to you (because your name shows in gitlens..)?

Hi @matanor , I thought that tetst_metrics.py should be fixed. Is this PR in reference to issue #1136 that I assigned to you (because your name shows in gitlens.. as the one who moved the tests from prepare to test_metrics)?

hi @dafnapension ! you mean we should first fix the above issue, before considering this PR ? (though the issue is on context_correctness, here its about new tests for answer_correctness)

I must admit that I am less familiar with the exact inference power of the different models, I participate in unitxt more on the level of "pattern recognition" of code issues: if I see a problem (like this issue), or asked to help with some specific pieces of code.
I only have my own Win10 machine (running on Dell), no access to any GPU.
So in these terms (of סדר וניקיון) I bumped into this issue, and looked in gitlens to see who can understand what is going on, and found your name in gitlens.
Now you explained in the PR (that made your name show in gitlens) that you see value in moving tests from prepare to test_metrics.
So now, in terms of סדר וניקיון, even before the correctness of the scores..  I am puzzled about two issues:
(1) why heavy tests again in prepare, and not in test_metrics,
(2) what about this "def text_context_correctness(self):"  (note the  text_...   which prevents this method from being tested at all) that I had the impression that is related to your current PR.

Hi @matanor , this is how I manage to run your prepare/metrics/rag_answer_correctness.py  on my little Dell:

@dafnapension same question as here .. is it ok to merge?
the error in Test Catalog Preparation seemd unrelated?

Yes yes, from my perspective. I suspect, though that the 'merge' button is not applicable without passing all automatic tests.


Bug: Twitter-like 140 character truncation is erratic in timeline script

Workaround in a5ff6a9, but not great.

Fixed in 8907b1d6872e6d15bbd197771c1f57d2eed925a3 .


Publish scala-native snapshot to maven center

I got errors when resolving the dependencies.
[error]   not found: https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/org.scala-native/sbt-scala-native/scala_2.12/sbt_1.0/0.5.0-SNAPSHOT/ivys/ivy.xml
[error]   not found: https://repo.typesafe.com/typesafe/ivy-releases/org.scala-native/sbt-scala-native/scala_2.12/sbt_1.0/0.5.0-SNAPSHOT/ivys/ivy.xml
[warn] Project loading failed: (r)etry, (q)uit, (l)ast, or (i)gnore? (default: r)

Yes, unfortunately scala native 0.5 is not yet out, so the current way to set it up for gears is to locally publish it. I wrote some guides in CONTRIBUTING.md; but the tl;dr is if you're on Unix a git submodule update followed by dependencies/publish-deps.sh should prepare all the dependencies for you.

Scala Native 0.5.0 snapshots are available if you configure the snapshot resolver.
https://oss.sonatype.org/content/repositories/snapshots/org/scala-native/nativelib_native0.5.0-SNAPSHOT_3/

[error] (rootNative / update) sbt.librarymanagement.ResolveException: Error downloading org.scalameta:munit_native0.5.0-SNAPSHOT_3:1.0.0-M10+16-4e2ab919-SNAPSHOT
[error]   Not found
[error]   Not found
[error]   not found: C:\Users\hepin\.ivy2\local\org.scalameta\munit_native0.5.0-SNAPSHOT_3\1.0.0-M10+16-4e2ab919-SNAPSHOT\ivys\ivy.xml
[error]   not found: https://repo1.maven.org/maven2/org/scalameta/munit_native0.5.0-SNAPSHOT_3/1.0.0-M10+16-4e2ab919-SNAPSHOT/munit_native0.5.0-SNAPSHOT_3-1.0.0-M10+16-4e2ab919-SNAPSHOT.pom
[error]   not found: https://oss.sonatype.org/content/repositories/snapshots/org/scalameta/munit_native0.5.0-SNAPSHOT_3/1.0.0-M10+16-4e2ab919-SNAPSHOT/munit_native0.5.0-SNAPSHOT_3-1.0.0-M10+16-4e2ab919-SNAPSHOT.pom
[error] Total time: 20 s, completed 2024年1月24日 22:23:48

@armanbilge Munit is not published.
ThisBuild / resolvers += "Sonatype OSS Snapshots" at "https://oss.sonatype.org/content/repositories/snapshots/"

I plan to release 0.2 alongside SN 0.5.0 when the latter is available.

building the dependencies locally worked for me, thanks!  One issue I had was with the nix flake when running nix develop - I'm not sure why, but the SBT override wasn't being picked up.
Explicitly setting the JDK as a dependency for the dev shell solved this for me - e.g:
 devShells.default = pkgs.mkShell {
          buildInputs = with pkgs; [
            jdk21
            # Scala deps
            (sbt.override { jre = jdk21; })
            ....
            etc

It's published ;)


Questions

Hi, any questions
Why BaseEntity contains property Key? Where is used?
Your application contains SPA and mobile applications (React and react-native), why use cookies? And token auth ? mobile application use cookie too?
Nice project, thanks

Thank for your interest. ASP core project is on developing. Nowadays I'm little busy with react-social-network to move to next version and support AWS, Firebase, Azure, Other back-ends. On the whole of course I will use JWT. This project is not opinionated and it's not only used for react-social-network so I support some others security stuff too. If you have any further question don't hesitate to ask.


tox checks should not apply to test files

I made a project using this template
When I ran tox it "corrected" a bunch of OWL files in my tests/input folder. I don't want these corrected. By all means we should fix the ontologies upstream but in general I don't want test files touched!

The tox.ini should have --skip param to take care of it since this may be project specific?

Are you back? :-)
I think we want to err on the side of standardization and gently
encouraging the same dir layouts etc. Make tests/input the standard for
test data, tests/output for outputs. People can always tweak after the fact.
On Mon, Jan 29, 2024 at 12:28 PM Harshad @.***> wrote:

The tox.ini should have --skip param to take care of it since this may be
project specific?
—
Reply to this email directly, view it on GitHub
https://github.com/monarch-initiative/monarch-project-template/issues/24#issuecomment-1915507995,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAMMOIVBA3GM4XFBQE4YADYRABAJAVCNFSM6AAAAABCQA63ROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJVGUYDOOJZGU
.
You are receiving this because you authored the thread.Message ID:
@.***
com>


Procmon 3.61 not working in Win7 dev VM - Unable to load Process Monitor Device Driver

Sorry if this is wrong place to report issues, it's just easier to report in GH and seems like tool bugs reported here before have been addressed.
To reproduce:
IE 8 Win7 VM (https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/) in Virtualbox
Procmon <IP_ADDRESS> (latest)
Download and run (I had to download Firefox from ftp.mozilla.org to even have a working browser to download procmon, you can try testing on IE11 VM for modern browser).
Unable to load Process Monitor Device Driver

Thanks,

Windows 7 is not supported anymore - check with Windows. I'll have a look here, but no promises.

Windows 7 is not supported anymore - check with Windows. I'll have a look here, but no promises.

@foxmsft I don't think that is the reason why process monitor does not run, unless it has to do with driver signing expiration.
If that is the case and it is actually no longer supported, then these docs should be updated because they currently say Windows Vista and higher
https://github.com/MicrosoftDocs/sysinternals/blob/master/sysinternals/downloads/procmon.md#download
But again I don't think that is the issue here
Please reopen this issue.
Thanks,

Hi @wesinator, tracking this one internally and I'll try to solve it for the next ProcMon release, in the next couple of months.

Around some point, Microsoft enabled a dual-signature policy (i.e., the program adds both sha1 and sha256 digital signatures for staging).
Then, as of Process Monitor 3.53, Microsoft removed the sha1 signature (only the sha256 signature was retained).
The default unanswered Win7 does not support sha2 signatures, so Process Monitor prompts for an error that does not load the driver (embedded driver file: procmon .sys).
So there are two workarounds (Win7):
a. Use of lower versions such as 3.52;
b. Update patches (KB3033929);
大概从某个时间开始，微软启用了双签名策略（即程序同时添加sha1和sha256数字签名，过渡用）。
然后，自 Process Monitor 3.53 起，微软删除了sha1签名（只保留sha256签名）。
而默认的未更新补丁的Win7并不支持sha2签名，所以Process Monitor会提示无法加载驱动（嵌入的驱动文件：procmon.sys）的错误。
所以有两种解决方法（Win7）：
a.使用低版本如3.52；
b.更新补丁（KB3033929）；
ps，防火墙实在太讨厌了，传个图片文件累死。

You know, it would be nice if Procmon bothered to bubble the actual error up to the user!

You know, it would be nice if Procmon bothered to bubble the actual error up to the user! Telling me it can't load the device driver is pretty useless.

@ariccio it's a missing system feature update. the program doesn't know this.
you need to install these:
https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/3033929?redirectedfrom=MSDN
https://support.microsoft.com/en-us/topic/sha-2-code-signing-support-update-for-windows-server-2008-r2-windows-7-and-windows-server-2008-september-23-2019-84a8aad5-d8d9-2d5c-6d78-34f9aa5f8339
Hope this helps,

JFYI, procmon is broken again with the same popup on Win7...   (And the mentioned patches for signing do not help.)  Yeah, yeah, I know that it's not supported...

can confirm, the patch is already installed, still getting the error message

The latest version of procmon that works for me on Windows 7 x64 SP1 is v3.86.
You must install KB4474419 and KB4490628.
For downloading the KB update use: https://www.catalog.update.microsoft.com/
For more info about the SHA2 updates: https://support.microsoft.com/en-us/topic/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus-64d1c82d-31ee-c273-3930-69a4cde8e64f

We're in fact using the driver kit for Windows 8, so I would be surprised if it worked with 7 at all.

We're in fact using the driver kit for Windows 8, so I would be surprised if it worked with 7 at all.

Actually, on Windows 7 SP1 x86, even the current version of procmon (v3.93) works fine.

As the time of writing this comment, the latest version of Procmon (<IP_ADDRESS>) works on Windows 7 SP1 64-bit with the following patches installed:
Kernel-Mode Driver Framework v1.11 (KB2685811)
User-Mode Driver Framework v1.11 (KB2685813)
Security Update for Microsoft Windows (KB4474419)
Update for Microsoft Windows (KB4490628)
The last one (KB4490628) is NOT optional. Without it, Windows 7 is able verify SHA-2 certificates (with KB4474419 installed) but Procmon wouldn't run. I originally skipped it since it's titled "Servicing Stack Update for Windows 7 for x64-based Systems" and I wasn't planning to use Windows Update, however Procmon wouldn't run without it installed (not sure why though, other applications I use which uses SHA-2 drivers like npcap runs just fine)

After installing KB4474419 and KB4490628 on my Windows 7, I still received the "Unable to load Process Monitor Device Driver" error. However, after running procmon 3.86 once, the subsequent version, procmon 3.91, was able to run without issues. I'm not sure if this information is helpful for you.


Extend/Change public client registration properties

We have to add and change some properties for public client registration.

[x] add blog_uri
[ ] use blog title and blog description of config/settings
[ ] change clientName to name
[ ] add update client function in passport-ghost
[ ] use the new updateClient function in passport-ghost (be able to update any client property)

@cobbspur is it possible to change the blog_uri?

changed the issue title and added more TODO's

Closed by #7690


document the host parameter on port-forwards

Hello @maiamcc, @ellenkorbes,
Please review the following commits I made in branch nicks/portforward:
78fe764de51f21de9f2783d4b1a4b747e7761794 (2020-12-02 11:27:12 -0500)
document the host parameter on port-forwards
Code review reminders, by giving a LGTM you attest that:

Commits are adequately tested
Code is easy to understand and conforms to style guides
Incomplete code is marked with TODOs
Code is suitably instrumented with logging and metrics

@maiamcc haha, ya, that occurred to me too when i was adding this! ya, let's do it


Add the 2-factor authentication screen back in

With the rewrite to react the 2-factor authentication is missing in the front-end after login. This means that users will not be able to log in if they have 2-factor enabled.
The 2-factor screen needs to be added in the authentication flow in the front-end again.

The needed changes in the API have been merged into the code base in https://github.com/pledger-io/rest-application/pull/24


How can the "Fulfilling" section code work?

function* demo() {
  var res = yield 10;
  assert(res === 32);
  return 42;
}

var d = demo();
var resA = d.next();
// => {value: 10, done: false}
var resB = d.next(32);
// => {value: 42, done: true}
//if we call d.next() again it throws an error

demo takes no arguments, and doesn't assign any values out of arguments so how could the second call to demo.next() possibly pass the assert(res === 32); line?

The * after function indicates that demo is a generator function.  What that means is that calling demo doesn't actually evaluate the function, it just sets up a new context for the function.  When you first call d.next() it actually begins executing the function, but pauses when it gets to the first yield keyword.  The second call, d.next(32) passes 32 in as the result of the yield expression.  This causes the assertion to pass and the demo function to continue the rest of its execution.  It's this ability to pause execution of the function that makes generator so powerful.


Typescript deploy to lambda

Desktop (please complete the following information):

OS: Mac Catalina 10.15.07
VS Code version: .54.3

Commit: 2b9aebd5354a3629c3aba0a5f5df49f43d6689f8
Date: 2021-03-15T11:57:12.728Z (2 wks ago)
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 19.6.0

Alexa Skill Toolkit extension version: v2.5.0

Question
I migrated my skill to Typescript. I have trouble updating the location of index.handler using the Alexa Skills Toolkit. I am using the Alexa Console built-in repository, lambda function, and cloud watch.
My code looks very similar to this sample skill. But they are not using the Alexa Skills Toolkit, so I am not sure how to integrate Typescript using the Toolkit.
My folder structure looks like follows:

.ask

.vscode

lambda

dist

src

index.js
index.js.map

node_modules

src

utils

types

data

index.ts
package.json
tsconfig.json

skill-package

assets

interactionModels

skill.json

.gitignore

Package.json currently points to "main": "dist/index.js",. When I upload the project to Alexa Console using the vs code plugin, the code viewer shows me the following code structure:

Skill Code

lambda

dist

index.ts
package.json
tsconfig.json

src

I receive the following error on Cloud Watch when I try to call my skill
{
    "errorType": "Runtime.HandlerNotFound",
    "errorMessage": "index.handler is undefined or not exported",
    "stack": [
        "Runtime.HandlerNotFound: index.handler is undefined or not exported",
        "    at Object.module.exports.load (/var/runtime/UserFunction.js:144:11)",
        "    at Object.<anonymous> (/var/runtime/index.js:45:30)",
        "    at Module._compile (internal/modules/cjs/loader.js:778:30)",
        "    at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)",
        "    at Module.load (internal/modules/cjs/loader.js:653:32)",
        "    at tryModuleLoad (internal/modules/cjs/loader.js:593:12)",
        "    at Function.Module._load (internal/modules/cjs/loader.js:585:3)",
        "    at Function.Module.runMain (internal/modules/cjs/loader.js:831:12)",
        "    at startup (internal/bootstrap/node.js:283:19)",
        "    at bootstrapNodeJSCore (internal/bootstrap/node.js:623:3)"
    ]
}

Do I need to even add dist/ to the lambda or should I add it to .gitignore?
What's the best way to solve this issue using not aws commands but the plugin or the ask-cli. I am not hosting the lambda on my own and I am also not zipping the code but I deploy it using the Alexa Skills Toolkit. I could migrate to custom lambda and write myself a custom zip command but I would rather stick to the vs code plugin. Unsure how to proceed.
Thanks for your help!

I was able to make it work now.

I added the dist folder to git and deploy it to lambda using Alexa Skills Toolkit
I added a index.js inside lambda/ which just looks like follows:

const handler = require('./dist/index')

exports.handler = handler

Is this how TypeScript is supposed to work with Alexa Skills Toolkit or is there a better way to configure it?

Hey @andrelandgraf , sorry for the late response. So as you may already know, the Alexa Console built-in repository is just the normal AWS Lambda function over an AWS CodeCommit repository for the skill, handled by the Hosted skills service. AWS Lambda doesn't currently support Typescript out of the box, and the developers are expected to build the .ts files to .js files before uploading to the service. This is the reason why you would still need to upload the dist directory containing the js files.
Additionally, the default handler location for the AWS Lambda function for the hosted skills service is index.handler and at the moment, that service doesn't provide a way to configure this handler through the tools. This is the reason why you would have to re-import the handler from dist/index and export it back again, in your workaround. You can also configure your tsconfig.json to output the built files to the same lambda folder, and hence not do such workarounds. However, that would add both js and ts files in the same folder, leading to confusion and maintainability issues. I think your workaround is a good one, until the hosted skill service provides a way to configure the handler location.
As for the sample skill, it seems to have been built on the ask cli v1 structure. If so, skill devs can use this migration guide, to convert it to the ask cli v2 structure, which is compatible with the ASK Toolkit vscode extension. Hope this helps.
I am going ahead and closing this issue, considering you are unblocked at the moment. Please create an issue in case you have further questions or have any feedback on the extension. Thanks.

Thanks @nikhilym for the in-depth explanations! This cleared up a lot of assumptions I made. Great to hear that you recommend my workaround for now.


RenderDoc fails to open multiple Vulkan captures with out of device memory errors

Description
With RenderDoc I often want to compare 2 different frames at the same time, a good frame a bad frame, to see what inputs went wrong and where, in order to track down rendering issues. However in Vulkan, it's almost impossible to open 2 captures at the same time, as RenderDoc always throws this out of device memory error on opening the second capture:

With 0 captures open:

With 1 capture open:

Once loaded, it seems to only take up ~1.5GB with plenty to spare, but then attempting to load any other capture and it will throw out of device memory.
Also, if I run my application and then try to load a RenderDoc capture while my app is open, RenderDoc will also throw this error. If I reverse the order and load the RenderDoc capture first, and then my application, both work perfectly fine with low GPU memory utilisation. It seems RenderDoc just doesn't like when another Vulkan application is running on the system, including itself.
Steps to reproduce
Here are 2 small and simple captures which trigger the issue for me: https://cdn.discordapp.com/attachments/942442841408434186/1153640179513434112/deko_texture_example.7z
Open one of the captures, and then open the other so that a second RenderDoc instance opens. The second capture should throw an out of device memory error.
These were captured on an nVidia Titan X, using Vulkan 1.3. The build process is a bit of a pain, so I'm hoping you can open these. Let me know if not though.
Environment
Windows 10, and all RenderDoc versions I've used experience this issue, currently on v1.29 https://github.com/baldurk/renderdoc/commit/815c88b932245826c30dba1a8309ee9ae3eadb78

I'm not able to reproduce this. I can open both captures fine (though I did have to patch them to open on my 4090 as the memory types were not compatible with a titan X). I'm on the exact same driver 536.99 so I don't think it's a driver version thing.
Does this only happen with your program? Or can you repro this with e.g. vkcube or Sascha Willems' demos? Do you have a different machine or GPU you can test with?
Realistically I'm not sure why this would happen only for you unless it was an NV/driver issue, but it doesn't make a lot of sense to me either why it would report an out of memory error.

I cannot reproduce this with vkcube or Sascha's demos, I can open multiple of those, so it may be my app only. We have an OpenGL backend and I can open multiple OpenGL captures without issue. We don't have a DirectX backend so I can't test that, but after capturing some other random DX apps, multiples there are also ok. So it seems like it is specific to my app, and is Vulkan-only.
I'll try to build RenderDoc from source and do a little debugging to see if I can get some information about the allocations.

Ahh, yes that make sense - also makes sense why I didn't reproduce it when I hacked the capture to remap the memory allocations.
In the general case RenderDoc needs to preserve the memory types for correctness, otherwise there could be a cascading effect with the resources bound not being available to bind to other memory types, availability for host writes, etc. Newer features like buffer device address put a nail in the coffin of the idea of remapping memory types. I do have a local hack that will reallocate memory for resources but it doesn't work in all cases and right now doubles the amount of memory used in a capture.
Presumably that also means that if you run two instances of your application it will break? Indeed the only thing I can suggest is what you will have already thought of - being more careful with how much PCI-E window memory you use.


new build-args-file parameter which allows to pass build arguments to

buildah task
KONFLUX-268
Before you complete this pull request ...
Look for any open pull requests in the repository with the title "e2e-tests update" and
see if there are recent e2e-tests updates that will be applicable to your change.

I've changed it to "        BUILDAH_ARGS+=("--build-arg-file=${SOURCE_CODE_DIR}/${BUILD_ARGS_FILE}")
because that is what I wanted initially do
and it is up to users, if they will provide builargs from the root of the repo "./args.conf", or from context "./context/args.conf"
anyway it is "full" path within repo which will be provided in the --build-arg-file

/retest


fix: Bowser.getParser empty string UserAgent error

Description
It turns out that Bower doesn't allow any forms of empty UserAgent in getParser function https://github.com/lancedikson/bowser/blob/41bbfc1600fc38d3ea5f49dcfba5bc28cd7357aa/src/parser.js#L24.
Motivation and Context
Making it works for React Native app.
Types of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] I have added tests to cover my changes.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] My code follows the code style of this project.
[x] My commits and the title of this PR follow the Conventional Commits Specification.
[x] I have read the contributing guidelines.

Part of v2.6.2


remove graph from search

no more graph biz (was fun while it lasted)

Should sigma also be removed from package.json?

yes, good catch, just removed it on this branch


Nodes cannot pull image from docker registry

Hey, I have an issue that don't know how to investigate further and how to solve it. I tried it a few times by removing all VPS and started again but every time I end up with the same error.
I am trying to set up my cluster on Scaleway. I follow instructions one by one, and I am at the point where I installed wave as CNI, and I've got:
kube-system   weave-net-dtwbj                2/2     Running                 1          9d
kube-system   weave-net-kmxq7                0/2     Init:ImagePullBackOff   0          9d
kube-system   weave-net-pzfcj                0/2     Init:ImagePullBackOff   0          9d

So my issue is on my nodes but not on master.
I found this #74 and this time I applied these suggestions, but the output is the same.
UFW / Firewall
I skip the part with firewall, on every VPS I've got:
> ufw status
Status: inactive

In scaleway config all my VPS have the same security policy applied. Only outbound traffic on ports [25, 465, 587] is dropping.
Internet connection
On both my nodes I've issue to download images from docker's registry and I believe that this is the real issue here
> docker pull hello-world
Using default tag: latest
Error response from daemon: Get https://registry-1.docker.io/v2/: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

On master hello-world was pulled successfully.
Nodes have internet connection outside:
--- google.com ping statistics ---
9 packets transmitted, 9 received, 0% packet loss, time 8011ms
rtt min/avg/max/mdev = 1.008/1.139/1.258/0.073 ms

WireGuard
By the output of wg show I assume that VPN between my VPS is set up correctly
peer: 3
  endpoint: 3-priv IP:51820
  allowed ips: <IP_ADDRESS>/32
  latest handshake: 1 minute, 17 seconds ago
  transfer: 7.50 GiB received, 6.50 GiB sent

peer: 2
  endpoint: 2-priv IP:51820
  allowed ips: <IP_ADDRESS>/32
  latest handshake: 1 minute, 41 seconds ago
  transfer: 4.96 GiB received, 6.11 GiB sent

Could anybody help me track the issue down and help me to fix it? I can provide any kinds of logs you wish just tell me how I can get it

It's difficult to debug this without further context. I found this: https://forums.docker.com/t/docker-pull-results-in-request-canceled-while-waiting-for-connection-client-timeout-exceeded-while-awaiting-headers/73064/10

I‘ll try to have a look at the suggestions made in #74, but I’m really busy at the moment.

Thank you, no pressure. Once more I decided to remove all my VPS and try again but with this error in mind. I installed docker firstly and then follow this guide. After each bigger step I run docker pull image where image was every time different (PHP, nginx etc.) to be sure that it has to download it from registry and will not use any cache. After this process I find out that wireguard cause the issue.
My VPS's config looked like this:
1 VPS with public IP
2 VPS without public IP
And the one with public IP worked well, and two others didn't, so I added at Scalaway public IP's, and it starts working (docker pull). Unfortunately I as well didn't have enough time to try the rest of the guide. Hopefully in this weekend I will try and let you know.
I don't understand why VPS worked well without WG and public IP and after setting up WG I suddenly need public IP. If you have any idea let me know.
Right now treat this as on hold I will leave here information if adding public IP's solves my problems :)

Hey I managed to set up cluster :) Not adding IP addresses to all my nodes was a mistake. But I still don't understand why setting up WireGuard messed networking on VPS. I followed additional instructions from #74 and didn't have to do any ip route from guide and anything connected to that so if you will find any spare time maybe it's worth your attention, and if it doesn't break anything else, IMO it will be good to mention it in guide as second option :)
Thank you very much for this guide it is very useful


[language, move] Introduce public key validation

TL;DR: Introduce a native function for public key validation, and use it in TR key rotation.
This solves the problem that any 32-byte value would be accepted as a public key in the stdlib contracts, despite the length check being insufficient to protect against invalid point attacks, small subgroup attacks, and typos.
In the last case, before this PR, a user would typically rotate their key to an invalid public key unwittingly, and then fail to produce signatures against that new key, losing the balance of their account in the process losing the ability to demonstrate the legality of their transactions. We'd rather have early failure.
This introduces a native function for checking the validity of this public key, and uses it upon rotation. It would probably be useful to call this public key validation function in a few more places - in fact, anywhere externally-controlled key material is registered on-chain. I have not looked beyond the key rotation contracts — Edit : and publication — for now.
A further step would be an opt-in proof of ownership (TBD).

I confirm that the latest commit (f1aeaab) (with modifying prelude.bpl) passed the Prover test in CI (https://github.com/mimoo/mirai-bot/runs/668772188?check_suite_focus=true#step:7:1). Miraibot is silent when it finds no errors.

Thanks for tackling this important endeavor!

@bors-libra r=sblackshear

:pushpin: Commit 6a751d1 has been approved by sblackshear

:hourglass: Testing commit 6a751d14810a505dd9cfdcdb0f722a18965aaa76 with merge a8cd371857f70541f2fd49239c0b02059c54d726...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: sblackshear
Pushing a8cd371857f70541f2fd49239c0b02059c54d726 to master...


Archival: Internal Blob Store Implementation for Archival Interface

Task 3 of https://github.com/uber/cadence/issues/2082

Move this

Moved.


Investigate if model_without_ddp is needed

🐛 Describe the bug
Investigate if we need model_without_ddp in the training script. https://github.com/pytorch/vision/blob/12fd3a625a044a454cca3dbb2187e78efe1b4596/references/classification/train.py#L201
Versions
N/A
cc @datumbox

While running a fairly limited training experiment for https://github.com/pytorch/vision/pull/4381, it was observed that model worked without any issue instead of model_without_ddp. Hence, it may be worth investigating if we need model_without_ddp at all.

@fmassa Prabhat did investigations where he used the model instead of model_without_ddp on the checkpoint mechanism and it seems that the loading/saving/resuming worked fine. Could you please provide some additional information on why using the non-parallelized version was needed in the first place? What is it expected to fail if we use the model instead of model_without_ddp? It might be the case that whatever limitation used to exist, is no longer an issue.

Hi,
The reason why we have model_without_ddp was to be able to serialize the model weights without the module. prefix that gets attached to DDP models. Otherwise, you wouldn't be able to load the checkpoints from the trained model on the CPU or on a model without DDP, or would have to perform checkpoint renaming to manually remove the prefix. The easiest thing to do was to keep around a version of the model that didn't have DDP, so that we don't have to deal with this.

@fmassa Thanks for the info.
Prabhat found that using model instead of model_without_ddp on the following snippet works fine for EMA. He was able to save/load checkpoints without a problem:
https://github.com/pytorch/vision/blob/12fd3a625a044a454cca3dbb2187e78efe1b4596/references/classification/train.py#L208
We did end up changing it to model_without_ddp just to be safe but I wonder if the limitation that existed int the past is no longer there and we can replace model_without_ddp with model everywhere. Thoughts?

I ran training on resnet18 for 100 epochs, where I cancelled the training around epoch 34 and resumed it again, with and without model_without_ddp(I just do model_without_ddp = model after the if block).
Here is the diff:
diff --git a/references/classification/train.py b/references/classification/train.py
index a3e4c9ad..d49dba56 100644
--- a/references/classification/train.py
+++ b/references/classification/train.py
@@ -201,6 +201,7 @@ def main(args):
     if args.distributed:
         model = torch.nn.parallel.DistributedDataParallel(model, device_ids=[args.gpu])
         model_without_ddp = model.module
+    model_without_ddp = model

     model_ema = None
     if args.model_ema:

I didn't see any significant difference in the result.
training_with_changes1.txt
training_with_changes2.txt
training_with_no_changes1.txt
training_with_no_changes2.txt

@prabhat00155 what you would have needed would be to try to load the serialized checkpoint from a model that hasn't been wrapped up in DDP yet.
Something as simple as
model = torchvision.models.resnet50()
model.load_state_dict(path_to_checkpoint)

would fail due to the added module. that gets appended due to DDP, so you would need to use tools like torch.nn.modules.utils.consume_prefix_in_state_dict_if_present, which are pretty new and was added to PyTorch less than 6 months ago https://github.com/pytorch/pytorch/pull/53224
I would be ok removing the current model_without_ddp in torchvision if we use a newer and better way that is provided by PyTorch, but I'm not sure that the current torch.nn.modules.utils.consume_prefix_in_state_dict_if_present is enough for that (at least it would need some thinking to be able to make sure all cases are handled properly)

@fmassa Thanks for providing background on why this was added.
So basically, this workaround increases user-friendliness on how the weights are handled after the training is completed (hence outside of the train.py script).
Two thoughts on eliminating the non-parallelized version:

For the users of our library that just take the pre-trained weights this has no effect. It's us the contributors who train the models, prepare them (verify, produce hashes, load on S3 etc) and make them available. So we could easily adjust our process to do the extra step of removing .module without real issues.
For the users of the references, this could potentially become a source of frustration as users would have to take the checkpoints, remove .module with the aforementioned method and then use the weights.

I don't have a very strong opinion over this, but I'm leaning towards keeping it for the time being. Yes it's a bit annoying to keep the non-parallelized version around but it does eliminate potential frustration for new users of the library. Thoughts?

Thanks @fmassa and @datumbox! I think it makes sense to keep it then. I'll close this issue.

I don't have a very strong opinion over this, but I'm leaning towards keeping it for the time being. Yes it's a bit annoying to keep the non-parallelized version around but it does eliminate potential frustration for new users of the library. Thoughts?

Yes, that's the main reason why I'd lean on keeping it. The use-case I had was indeed for a user to run evaluation on a checkpoint in a different machine with a single GPU (or without GPUs), and the current setup allows them to get this seamlessly.


Where to find "generic.bin"?

Hey everyone,
i tried to flash the code onto a NodeMCU. When I executed the flash.bat and chose option 1 nothing happend. So i looked into the flash.bat and found it is supposed to upload "generic.bin" via esptool.
The Problem: I can't find a generic.bin in the entire ZIP-folder.
Any ideas what i'm missing?
Thanks in advance.

You seem to have downloaded the source code. Please use the releases. See https://github.com/esprfid/esp-rfid#software
If it is the first time for you to flash esp-rfid, then please use the latest release of version 1 : https://github.com/esprfid/esp-rfid/releases/tag/1.0.2

Thanks a lot, it worked.


Add widget buttons not working

Dev Home version
<IP_ADDRESS>
Windows build number
10.0.22623.1245
Other software
OS Build Version: 10.0.22623.1245.amd64fre.ni_release.220506-1250
.NET Version: .NET 6.0.16
Steps to reproduce the bug
I just installed devhome, I connected my Github account and when I press any add widget button it just doesn't do anything, in fact I pressed it so many times that the app closed
Expected result
A new screen is expected to appear with the available widgets
Actual result
I press any add widget button it just doesn't do anything, in fact I pressed it so many times that the app closed
Included System Information
CPU: Intel(R) Core(TM) i5-10300H CPU @ 2.50GHz
Physical Memory: 15.84GB (8.9GB free)
Processor Architecture: x64
Included Extensions Information
Extensions:
Microsoft.Windows.DevHome_<IP_ADDRESS>_x64__8wekyb3d8bbwe
Microsoft.Windows.DevHomeGitHubExtension_<IP_ADDRESS>_x64__8wekyb3d8bbwe

Duplicate of #866


PointOperation adds list-annotation feature / Fix bugs / ViewOperation feature extensions

:tada: This PR is included in version 1.0.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Add wallpapers for different resolutions

Currently the wallpaper included is 1680x1050. It would be good to find the wallpaper in different resolutions for people looking to get the exact same look as the screenshot.
Unfortunalty I can't seem to find the same wallpaper in any other resolution.
If anyone has any other wallpapers that look similar, or would be a good fit for the theme, let me know!

Hey. There is just Something missing in the Theme.config
Please add this in the Banner Option.
banner_scale fillscreen
It fixes this issue :)
Sources refind.config or http://www.rodsbooks.com/refind/themes.html
Maybe u should update your source :) By the Way very Nice theme!!!

Thanks @T0m93.
I think I'm going to keep the banner_scale option left to it's default value for now and leave it up to the user to enable this. I think an upscaled image is worse than a native one, so I'd rather not upscale by default :-)

Ok. But there are 3 possibilities.
1.The picture is too big ---> doesnt look as nice as it does normally ---> banner_scale fillscreen---> fits and no quality loss
2. Picture fits--> no changes
3. picture too small  --> looks weird. upscaling would fix that ---> Quality loss, but at least it fits the screen and doesnt look weird :) and if it sucks just replace the background.png with whatever you like^^
But yout theme, your rules :) By the way it looks really awesome on my Mac, just added some text on it (by the way use Calibre for Text. matches perfect the theme).
Maybe u should fix/change the win8 icon. Because it uses the default blue one (i just replaced the default win8 icon with your win icon and renamed it).
Have a nice day :)

Thanks for the feedback again @T0m93!
Yeah that's true. But I think I'd rather leave that decision up to the user. I'd rather them get an obvious bad experience (image too small / large) and then either replace the image, or settle with using banner_scale, than simply add that option and then have the user scratching their head as to why the background looks fuzzy.

But yout theme, your rules :)

Thanks again man I really appreciate it! :-)
I fixed the windows issue in aa27619. Thanks for letting me know!

I was looking for similar wallpapers on deviantART and actually found the original, in higher quality (2560x1600).
http://leonardoalanb.deviantart.com/art/Minimalist-wallpaper-295519786

That's it! Thank you very much @theRealPadster :100:

You don't want to replace the version in use with the higher-quality one?

I think I'd like for the user to select a background image that is the right size for them. I have 1920x1080 monitors, so I will leave it at that as the default. But I did put a section into the readme about selecting a wallpaper size.

banner_scale fillscreen ? Why not now? Would fix everything. With 2560x1600 wallpaper there shouldn't be any upscaling issues.

Yeah, could the 2560x1600 version be included and banner_scale fillscreen be set as default? The pattern doesn't have any details that would be lost if it just centred the image, as it's just a gradient for the most part. For 1080p screens it would fill it (with some cut off around the edges), and on bigger screens, like 1440p, it would still look good, without stretching.


Temporarily pin autograd < 1.6, fix builds

Description
Adds an upper-bound constraint to autograd's version, in order to fix builds for Windows and ARM M-series macOS, for more details see https://github.com/HIPS/autograd/issues/601
Update: fixed after a 1.6.1 patch release
Fixes # (issue)
Type of change
Please add a line in the relevant section of CHANGELOG.md to document the change (include PR #) - note reverse order of PR #s. If necessary, also add to the list of breaking changes.

[ ] New feature (non-breaking change which adds functionality)
[ ] Optimization (back-end change that speeds up the code)
[ ] Bug fix (non-breaking change which fixes an issue)

Key checklist:

[ ] No style issues: $ pre-commit run (see CONTRIBUTING.md for how to set this up to run automatically when committing locally, in just two lines of code)
[ ] All tests pass: $ python run-tests.py --all
[ ] The documentation builds: $ python run-tests.py --doctest

You can run unit and doctests together at once, using $ python run-tests.py --quick.
Further checks:

[ ] Code is commented, particularly in hard-to-understand areas
[ ] Tests added that prove fix is effective or that feature works

We can probably just remove autograd as a dependency, we don't use it anywhere (only in one test specifically just for autograd)

Good idea, since we can fall back to using derivative instead of autograd when differentiating. Do you want me to try doing this in a further PR?

The only place where we use it is here:

Yes please. I don't think the fall back to derivative will work, that is specifically for interpolants. But we never need the fallback in practice

The only place where we use it is here:
https://github.com/pybamm-team/PyBaMM/blob/bf8581174460005f4d4ecb1a0b56cbf665cd59ce/pybamm/expression_tree/functions.py#L94-L122

@tinosulzer I thought of some more discussion before I start doing it concretely. Using "derivative" instead of "autograd" did not work, as you said above. Five tests from test_expression_tree.test_functions fail locally when I remove autograd as an option, and it is the error that comes up when len(children) > 1:
ValueError: differentiation using '.derivative()' not implemented for functions with more than one child

should I remove those tests? Debugging this could be slightly outside my forte

I see, let's keep this as is then, and just make autograd an optional dependency as is already being done in #3044

Sure, closing this since the build issue was resolved with autograd 1.6.2


Redirected to auth/login with 404 after install, nginx

I tried to install cockpit on my nginx server and ran into the same issue #686.
Did you find a solution for this issue on nginx ?

Found the solution 🎉
It was already discussed about the issue on #19. Also, there is a link to the nginx server config which worked for me (hence the try_files $uri $uri/ /cockpit/index.php?$args;)


Add transformer implementation of relevance task

This PR adds transformer implementation and distilbert base model for the relevance task. These notebooks will enable us to experiment with sparse models.
Reference Issues:
Closes #221
Addresses #184

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign erikerlandson for approval by writing /assign @erikerlandson in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

/approve

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Shreyanand
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Shreyanand]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Strings for server connections limited to 64 characters

The plugin limits the character strings to 64 characters in length, this causes issues when trying to connect to a kdb instance managed by Amazon FinSpace with Managed kdb Insights. The strings for serverName is over 64 characters, and the password is a very long signed URL

Thanks for the feedback, we have raised a ticket internally to implement this

@vsaulys  Raised the limit to 1024 characters. Will this be enough?

Will need 2048.
The signed connection string can be up to 2048 as per docs:
https://docs.aws.amazon.com/finspace/latest/management-api/API_GetKxConnectionString.html￼
Vincent Saulys
@.***

On Mar 11, 2024, at 6:41 AM, Ecmel Ercan @.***> wrote:
@vsaulys https://github.com/vsaulys Raised the limit to 1024 characters. Will this be enough?
—
Reply to this email directly, view it on GitHub https://github.com/KxSystems/kx-vscode/issues/257#issuecomment-1988130186, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATBT3QSMVSTHPNVT4YIEVTYXWC5VAVCNFSM6AAAAABEJP4Y3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBYGEZTAMJYGY.
You are receiving this because you were mentioned.

Increased to 2048

This will be in release 1.4 hopefully this week.

@vsaulys  This is available in version 1.4 from marketplace.

Excellent!
Thanks for the update
Vincent Saulys
@.***

On Mar 13, 2024, at 1:41 PM, Ecmel Ercan @.***> wrote:
@vsaulys https://github.com/vsaulys This is available in version 1.4 from marketplace.
—
Reply to this email directly, view it on GitHub https://github.com/KxSystems/kx-vscode/issues/257#issuecomment-1995135483, or unsubscribe https://github.com/notifications/unsubscribe-auth/AATBT3UJUUIP6OSXZ6EXOWTYYCFT7AVCNFSM6AAAAABEJP4Y3CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJVGEZTKNBYGM.
You are receiving this because you were mentioned.


[Feature Request] Dependency Status Tab on Azure Dev Ops

Hi there,
i'm using DependencyCheck on Azure DevOps and it seems a quite powerful tool, compliment for that.
I've installed the extension and configured the Dependecy, and everything is working fine, I can download test results from artifacts, I've also configured a Publish Dependency Check Test Results Task so i got i nice view of the tests result.
It would be nice to add a Dependency Status Tab where to show the report directly in Azure Dev Ops in addition to download it as artifact
All the best.

@gsantopaolo I didn't know about this Azure Devops extension, but a bit of googling led me to https://github.com/dependency-check/azuredevops
That looks like the spot to file your Feature Request. The Azure DevOps integration (a wrapper around the CLI tool of this project) is not managed by this DependencyCheck project, but appears to be managed in that azuredevops dependency-check github project.
The merging of PRs by @ejohn20 matches with the contributors mentioned at the marketplace as well as the comments in its Q&A section where an issue in that github project is referenced.

This is a duplicate of this issue: https://github.com/dependency-check/azuredevops/issues/3

Closing this issue as it will be handled in the azuredevops repo.


The side_panel example doesn't exit successfully on Windows (must use Ctrl + C to exit)

The side_panel example doesn't exit successfully when closed with the icon menu at the top left of the window or by clicking the X at the top right of the window. The console sits and waits until I press Ctrl + C.
Run with: cargo run --example side_panel
Environment:

Windows 10

Edition: Windows 10 Pro
Version: 21H2
OS build: 19044.1826
Experience: Windows Feature Experience Pack 120.2212.4180.0

Rust

rustc 1.62.1 (e092d0b6b 2022-07-16)

Bevy v0.8
bevy_egui v0.15

It's a bug in Bevy 0.8 caused by power-saving settings. I forgot to remove them from that particular example. Fixed in 5e31c9e584a7470b940ec45a136dddedf7e930b6, thanks!


Update OGC-API-Coverages-SWG-Charter.adoc

I made a number of grammatical edits to the document. No technical changes. My only suggestion is that you reach out to the coverage experts in the OGC. Many members that work in the satellite or related sensor technology domains are not represented in the list of charter members.
Any questions on my suggested edits, please let me know!
Cheers

Thanks for the review. We will discuss the charter at the WCS SWG session tomorrow of the upcoming TC meeting.


reuse_port on freebsd

Why isn't reuse_port working on FreeBSD ?
FreeBSD already has SO_REUSEPORT and SO_REUSEADDR support @ kernel.
Please, implement.

http://hg.nginx.org/nginx/rev/4f6efabcb09b
maybe someone can help?
https://github.com/alibaba/tengine/blob/master/auto/os/freebsd
huh.

cc @zhuzhaoyuan

Any news ?

Try fix one?

@Onepamopa You can try tengine-2.2.0 , If it's have any qusetion PLZ tell me.  Thx.


Documents won't generate with versions after 1.9.1

Describe the bug
Hi,
This is a continuation of issue #3282 but this issue is related to documents. The attached package can generate with 1.9.1 but not with 1.10.x, 1.11.x, nor 1.12.x.
graphql-codegen-bug-reproduce-documents.tar.gz
To Reproduce
Steps to reproduce the behavior:
tar xvf graphql-codegen-bug-reproduce.tar.gz
cd graphql-codegen-bug-reproduce
npm i
npm run build # works
sed -i "s|1.9.1|1.11.2|g" package.json
npm i
npm run build

My GraphQL schema:

Attached in package.

My GraphQL operations:

Attached in package.

My codegen.yml config file:

Attached in package.
Expected behavior
Generates file in src/types.ts
Environment:

OS: Linux & Mac
@graphql-codegen/...: 1.9.1-1.12.1
NodeJS: 10

@ardatan can you please take a look?

@SoyYoRafa You're using old version in that reproduction. Could you please try with the latest version 1.12.2 without ~? And next time please use codesandbox or GitHub instead of tar.gz. Thanks!

Hi, this still occurs in 1.12.2.

So as I said above please provide codesandbox reproduction.

Hi,
I have uploaded the files codesandbox: https://codesandbox.io/s/graphql-codegen-issue3457-hrs0w

And next time please

This I understood to be a future issue, not this one.

@ardatan you still waiting on something from me? I want to make sure the codesandbox has everything you need.

@SoyYoRafa Sorry for the late reply.
It seems like there is some kind of a conflict in deps, caused by graphql-config that requires @graphql-toolkit/schema-merging.
In your example, removing the explicit dependency for @graphql-toolkit/..., updating to latest codegen and add Yarn resolution seems to solve it:
  "resolutions": {
    "@graphql-toolkit/schema-merging": "0.9.9"
  }

We are working on a fix for that :)

We managed to reproduce this in: https://github.com/ardatan/graphql-toolkit/pull/548 , thanks @SoyYoRafa

@SoyYoRafa I can confirm that the fix in graphql-toolkit fixed that issue.
It will be shipped with the next codegen version.
If you wish to workaround that, you can use Yarn resolutions:
  "resolutions": {
    "@graphql-toolkit/core": "0.10.3-alpha-afd5e20.8",
    "@graphql-toolkit/apollo-engine-loader": "0.10.3-alpha-afd5e20.8",
    "@graphql-toolkit/code-file-loader": "0.10.3-alpha-afd5e20.8",
    "@graphql-toolkit/common": "0.10.3-alpha-afd5e20.8",
    "@graphql-toolkit/git-loader": "0.10.3-alpha-afd5e20.8",
    "@graphql-toolkit/github-loader": "0.10.3-alpha-afd5e20.8",
    "@graphql-toolkit/graphql-file-loader": "0.10.3-alpha-afd5e20.8",
    "@graphql-toolkit/graphql-tag-pluck": "0.10.3-alpha-afd5e20.8",
    "@graphql-toolkit/json-file-loader": "0.10.3-alpha-afd5e20.8",
    "@graphql-toolkit/prisma-loader": "0.10.3-alpha-afd5e20.8",
    "@graphql-toolkit/relay-operation-optimizer": "0.10.3-alpha-afd5e20.8",
    "@graphql-toolkit/schema-merging": "0.10.3-alpha-afd5e20.8",
    "@graphql-toolkit/url-loader": "0.10.3-alpha-afd5e20.8"
  }

Fixed in v1.13.2


Bad state: Cannot add event while adding a stream

I was trying to follow the example's structure for setting up an observable in order to have a listener for a status change in order to call a function but keep getting the error "Bad state: Cannot add event while adding a stream".
I was not sure if it was actually necessary, but I created a standalone AuthStatusController and an RxStatus which was similar to the RxUser() in the example:
enum AuthStatus { signIn, signedIn, signOut, signedOut, notVerified, verified }

class RxStatus{
  final status = AuthStatus.signedOut.obs;
}

class AuthStatusController extends RxController{
  static AuthStatusController get to => Get.find();
  final rx = RxStatus();
  AuthStatus get status => rx.status.value;

  void setStatus(AuthStatus value) {
    rx.status.value = value;
  }

  set status(AuthStatus value) {
    rx.status.value = value;
  }
}

I was using the Event package before and setup my listener within initState() of the class in which I wanted to use it, so I had just replaced the old listener with the new one, but that is when I got the error.
This is what I was attempting to use

  @override
  void initState() {
    super.initState();

    ...
    ...
    AuthStatusController.to.rx.status.listen((status) {
      if (status == AuthStatus.notVerified) Future.microtask(() => _switchAuthMode(verify: true));
    });
  }

I didn't think it would make much difference, but I figured it was worth a try, so I attempted this, but it made no difference.
  addListener() async {
    await AuthStatusController.to.rx.status.listen((status) {
      if (status == AuthStatus.notVerified) Future.microtask(() => _switchAuthMode(verify: true));
    });
  }

  @override
  void initState() {
    super.initState();

    ...
    ...
    addListener();
  }

I am guessing that it must be something that I am doing incorrectly, but I am not quite sure what. I usually spend time searching and going through other people's projects/repos and looking for similar setups to try and spot what I am doing differently, but I am finding it a bit difficult to find any, unfortunately.
Thanks,
-MH
Versions
Flutter: (Channel master, 1.19.0-4.0.pre.81, on Microsoft Windows [Version 10.0.19041.264], locale en-US)
get: ^2.11.1

I think what you want to do is use ever. It is more appropriate for this situation, listen only takes effect after the first change, ever is perfect for what you are trying to do. Read a little bit about Workers before you go into that.
Do you really need an initState and a StatefulWidget?
I would use ever() (Worker) to listen to this event, preferably within a Controller class in his onInit.
Listen only delivers changes, and it cannot be placed before the start of the stream that will give this error, for that there is the subject.stream.listen that is able to hear everyone, but I think your project would be much more organized if you remove all that for your controller and use ever instead of listening to a stream.
class AuthStatusController extends RxController{
  static AuthStatusController get to => Get.find();
  final rx = RxStatus();
  @override
  onInit(){
  ever(rx, (status){
 if (status == AuthStatus.notVerified) Future.microtask(() => _switchAuthMode(verify: true));
 })
  }
  AuthStatus get status => rx.status.value;

  void setStatus(AuthStatus value) {
    rx.status.value = value;
  }

  set status(AuthStatus value) {
    rx.status.value = value;
  }
}

My apologies, I should have clarified. The controller and such in the top section of code I shared are completely separate. The initState(), listener, and _switchAuthMode() are in my UI code to trigger a sequence of animations that change the login form to an email verification form once Firebase reports back if their account is verified or not.
I will give the 'ever' function and try and see if that does the trick.
Thanks,
-MH

There are a few other small adjustments I need to make on my end to utilize things properly in a few more places, but the flow of user creation and login, as well as the rest of my application, are now using 100% Get and things seem to be working well.
I definitely plan on seeing what else the package offers that I might be able to make use of, but for the bulk of things, looks like I am good to go. 👍
Thanks a lot, man. I appreciate it!
-MH

No problem. Closing this issue, if you face problems you can open another issue. If you still have doubts you can comment right here and I will answer.


Display notification banner if no changes made

What does this pull request do?
Shows info banner when no changes are made when amending outcomes
What is the intent behind these changes?
If nothing has changed on desired outcomes and the user goes to save changes an error shouldn’t throw on reason for changing
design: https://www.figma.com/file/UPHNDGeHMPKM6hZcAvZjk2/Working---Master-Design?node-id=7340%3A75906

 8.7 Amend desired outcomes

Looks good except one clarification


Networking API

Implementing https://partner.steamgames.com/doc/features/multiplayer/networking for multiplayer games would be a huge W for this repo. Any plans to add it?
I'm surprised that Greenworks doesn't already have this either. There is a networking API here already, but pointed out by another issue, it uses an outdated API.

ISteamNetworkingMessages specifically


import snippets from registry to development server

https://github.com/user-attachments/assets/0d5c5192-9087-434a-beb2-de3f2a798ecb
/claim #174
/closes #174

cannot find axios? But it worked on my machine

@seveibar I went to add your snippet and it was worth it, I found a bug where I imported duplicate snippets. Fixed now


Trying to use Fedora container KO

Hi,
I try to use Fedora container in Dockerfile and it is executed by Github Actions in Github Pages.  It's because architecture is amd64 ?

CheerpX only support the 32-bit x86 instruction set. Amd64 will be supported in the future.


prefer https

Using https will help keep user information confidential from any prying eyes, which is especially important on a site like this. If there are any other places in the repo that link back to the site and specify the protocol, please let me know and I'll add it to this pull request.
In addition, please make sure to use the https link when linking to the site elsewhere. If the protocol is not specify, GitHub will default to https, so this only matters if you are typing out the full URI.

Will https remain when we point the domain to cleanslate.com

Will https remain when we point the domain to cleanslate.com

No, you will not be able to support HTTPS with a custom domain hosted on GitHub Pages, unless you add CloudFlare (or something) in front of it to do the HTTPS termination there -- with the understanding that even that wouldn't be encrypted all the way back.

...I was just responding with a link to that post, @konklone! The CloudFlare workaround is much, much better than nothing in this case, and we can work on setting that up once the project switches over to the custom domain.

so @stvnrlly . The plan was to buy the domain "cleanslate.com" and then point it to the github. Thoughts on how we can maintain "https." And if we cannot? How bad would that be? We strongly prefer to be able to have the cleanslate link used. Thoughts?

ok great!!!!

On Jul 14, 2015, at 4:06 PM, stvnrlly<EMAIL_ADDRESS>wrote:
...I was just responding with a link to that post, @konklone https://github.com/konklone! The CloudFlare workaround is much, much better than nothing in this case, and we can work on setting that up once the project switches over to the custom domain.
—
Reply to this email directly or view it on GitHub https://github.com/codefordc/clean-slate/pull/95#issuecomment-121366532.

@stvnrlly. My goal is to secure the domain by Friday/Saturday for our launch on Monday. So its fine if we  set up the Cloudflare after the launch. Or does it need to be done before?

It can be done any time after you buy the domain name.


Fluentbit always read all log files from the beginning

Describe the bug

Whenever fluentbit is restarted (reloaded config) it rereads all logs files form the beginning
Steps to reproduce the issue:

Delete the deaemonset for fluentbit
Expected behavior

continue reading where it left off
Either have a hostPath or a pvc to save the DB from the fluentbit Input Plugin
Screenshots

Additional context

We will add options to enable hostPath, PVC for fluent-bit and set position file accordingly thanks for reporting it.


Syntax colorization for Python is incorrect in Notebookcells

Latest Insiders
Pylance 2021.11.2

See below (latest insiders): (this used to work in Insiders, see screenshots here https://github.com/microsoft/vscode-jupyter/issues/8374)

Here's a screenshot from the stable version (hence a regression):

This works fine for me.

Can you set this?
    "notebook-intellisense.trace.server.verbosity": "Verbose",
    "notebook-intellisense.logLevel": "Trace",

And then copy the output of the pylance logging for the matching kernel?

Closing as per discussion

I can repro this if there's no folder open (or no active interpreter set)


Dos larave-ide-helper support method autocomplete?

Versions:

ide-helper Version: current

Laravel Version: 9

PHP Version: 8

Question:
Dos larave-ide-helper support method autocompleat?

as you can see, am in phpstome 2022, and it can not autocomplete validate!
Please advice

Hi @beshoo  - The reason you're not getting autocomplete here is that the Request class is not known to PHPStorm at the time of your code writing.
This is shown bu the yellow background on the classname in the arguments list.
If you bring up the context menu for the Request - it should give you the chance to import it - at which time PHPStorm will be able to complete it.


Document not found when removing records

My Environment

ArangoDB Version:        3.3.14
Storage Engine:             MMFile
Deployment Mode:       Single Server
Configuration:               -
Infrastructure:               -
Operating System:        Debian 8
Used Package:              Debian or Ubuntu .deb

Component, Query & Data
Affected feature:
AQL
AQL query (if applicable):
FOR rec IN vTest
    FILTER rec._ci == 'id'
    REMOVE rec IN vTest

AQL explain (if applicable):
 FOR rec IN vTest FILTER rec._ci == 'id' REMOVE rec IN vTest

Execution plan:
 Id   NodeType        Est.   Comment
  1   SingletonNode      1   * ROOT
  6   IndexNode          1     - FOR rec IN vTest   /* skiplist index scan */
  5   RemoveNode         0       - REMOVE rec IN vTest

Indexes used:
 By   Type       Collection   Unique   Sparse   Selectivity   Fields                           Ranges
  6   skiplist   vTest        false    false            n/a   [ `_ci`, `ipList[*].netLong` ]   (rec.`_ci` == "id")

Optimization rules applied:
 Id   RuleName
  1   remove-data-modification-out-variables
  2   use-indexes
  3   remove-filter-covered-by-index
  4   remove-unnecessary-calculations-2

Write query options:
 Option                   Value
 ignoreErrors             false
 waitForSync              false
 nullMeansRemove          false
 mergeObjects             true
 ignoreDocumentNotFound   false
 readCompleteInput        true
 useIsRestore             false
 consultAqlWriteFilter    false
 ignoreRevs               true

Dataset:

only vTest collection with one skiplist index - field: "_ci, ipList[*].netLong"
only one record in vTest:

  "_ci": "id",
  "ipList": [
    {
      "netLong": 180906496
    },
    {
      "netLong": 168430080
    }
  ]
}

Steps to reproduce

Create vTest collection
Add a new record (above)
Execute the query

Problem:
Query: AQL: document not found (while executing)
The cause of this seems to be the applied index which seems to create _id duplicates during the query execution:
FOR rec IN vTest
    FILTER rec._ci == 'id'
    COLLECT id = rec._id WITH COUNT INTO c
    RETURN {id, count: c}

Expected result:
...

I can reproduce this fairly easy, we will have a look and fix it. For reference:
db._create('vTest');
db.test.save({"_ci": "id","ipList": [{"netLong": 180906496},{"netLong": 168430080}]});
db.vTest.ensureIndex({type:'skiplist', fields:["_ci", "ipList[*].netLong"]});
db._query("FOR rec IN vTest FILTER rec._ci == 'id' REMOVE rec IN vTest");

fixed in https://github.com/arangodb/arangodb/pull/6510

Fixed for 3.3.16

Thanks for the fix. Do you have any estimate when 3.3.16 could be released? This bug is quite a blocker for us.

It's always hard to provide an estimate for release dates, as the effective release dates are determined by what issues are reported and fixed in total, and by how quick the QA can be completed.
If you are happy with a preview release of 3.3.16 for a specific platform, I think we can provide it rather quickly. Is that an option?

We discussed this internally and decided that the suggested preview release is not needed at the very moment. However things change and I might come begging for it in the future :).

Hi @gurisko
ArangoDB version 3.3.16 has been officially released - I am going ahead and close this ticket now.
Tickets can be re-opened at any time by adding a new comment.
Best,
Omar Ayoubi

That was quick! Thanks!


Update of WebDriver to Selenium 4.10.0

One of the libraries fails to download, @rbourga please check it out


Exclude unstable Loom tests

Skynet: timeout due to perf (https://github.com/eclipse-openj9/openj9/issues/16728)
TimedGet: failure on mac-x86 (https://github.com/eclipse-openj9/openj9/issues/16729)

Signed-off-by: Jack Lu<EMAIL_ADDRESS>

The Skynet exclude is not working. Probably you need to exclude java/lang/Thread/virtual/stress/Skynet.java#id0
https://openj9-jenkins.osuosl.org/job/Test_openjdk19_j9_sanity.openjdk_aarch64_linux_Nightly/118/

@fengxue-IS pls go through the jdk20 exclude list as well. Looks like there are things unexcluded for 19 that were not unexcluded for 20.


Dev json schema

Allow pipestat output_schemas to exist as a true JSON schema while still offering backwards compatibility

Will also assist with:
https://github.com/databio/bbconf/issues/20


Do not trigger Azure CI on optimum changes

Merging to test functionality. Only affects Azure Linux CI.


Likely spelling mistake in README.md: "which uses Java Service Provider Inteface (SPI)" (missing 'r')

At 6d4fe9592677a9530f07be302b4b77c860360ddd dated 2022-02-07.

Thanks!! This issue was closed by #1668


Disable print if we are in 3D mode

This came up in https://github.com/GeoNode/geonode-client/issues/171

Coverage increased (+0.005%) to 70.72% when pulling 8ed0684b5bc840b9f03fa0d0cd1290471d058b9f on disable-print-3d into 951407fe3940ae0bd360fb4bdaef4fb3dd43c2e6 on master.

Coverage increased (+0.1%) to 70.855% when pulling daf4f06ab22f661eebb282c85f7959c05487d0ed on disable-print-3d into 951407fe3940ae0bd360fb4bdaef4fb3dd43c2e6 on master.


Failure on mapIntermediaryJar

When I try to run gradlew yarn it always give a error at :mapIntermediaryJar
:mapping minecraft to intermediary

> Task :mapIntermediaryJar FAILED

FAILURE: Build failed with an exception.

* Where:
Build file 'D:\ADM\Desktop\Codes\MCP\yarn-1.15.2\build.gradle' line: 628

* What went wrong:
Execution failed for task ':mapIntermediaryJar'.
> Failed to remap jar

I already tried to redownload the source folder.

Having the same issue:
> Task :downloadIntermediary
Unable to get progress logger. Download progress will not be displayed.

> Task :downloadVersionsManifest
:downloading minecraft versions manifest

> Task :downloadMcLibs
:downloading minecraft libraries

> Task :downloadMcJars
:downloading minecraft jars
:downloading minecraft client
:downloading minecraft server

> Task :mapIntermediaryJar FAILED
:mapping minecraft to intermediary

FAILURE: Build failed with an exception.

* Where:
Build file '/home/ej/Documents/Tools/Yarn1_15/build.gradle' line: 628

* What went wrong:
Execution failed for task ':mapIntermediaryJar'.
> Failed to remap jar

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 23s

I've seen that to

For now, guys, change the + in https://github.com/FabricMC/yarn/blob/e7852f3aa99b729af90e0f998193fb557b8f52aa/build.gradle#L15
to <IP_ADDRESS>, like
classpath 'net.fabricmc:tiny-remapper:<IP_ADDRESS>'

tiny remapper updated asm, and apparently the old asm brought by other parts of the buildscript dislikes that.

That fix pr is merged. Pull from origin (or whatever the remote this repo is on your git local repo)'s 1.15.2 branch and build again.


Game update/dlc

Describe the bug
A clear and concise description of what the bug is.
when mod is installed then boot the game the initial load screen gets stuck. All other mods are removed aside from this mod and those associated with it IE Isekai mod, expanded content 2022 etc
To Reproduce
Steps to reproduce the behavior:

install mod via unity mod manager latest version and dependencies (TT base and core)
launch game
game attempts its initial load and remains at 2/3rds complete

System OS is windows 11, core i5 9400f, 2070 super, 32gb ram

well i feel dumb you were on top of it i missed the update by a few minutes works now thank you for the great work


upstream-community-operators storageos (2.4.1)

Update to existing Operators

[x] Is your new CSV pointing to the previous version with the replaces property?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

/merge possible

/merge possible


Add Python 3.9/3.10 suport

I'd like to be able to use the armada client in projects that use more recent versions of python.
Looking at the dependencies and the git history it wasn't immediately obvious to me why the upper bound constraint on the version of python was added.
Is there a reason why not?
I think we could just remove it?

Hello @damelLP!  Welcome to the armada project.
I think we pinned python version due to airflow.  Maybe 6 months ago we had issues with 3.9.  We can test and get it working now.
For python client I think there is no issue.

We pushed a new release to PyPi so you should be good to work with it now!
https://pypi.org/project/armada-client/


Highlight memory usage in the README

I notice that mpi_soap.py uses ~5GB memory per MPI process.  So if you do something like mpiexec -np 12 on a machine with 64GB of memory, you'll just get a cryptic error like this.
mpiexec noticed that process rank 0 with PID 0 on node blah exited on signal 9 (Killed).
It might be good to point this out in the README.

Thanks for pointing that out! Yes I should add some pointers for typical issues that may arise in the README - will include that along with a quick code update later this week.

Took a little longer than I intended because GPFlow had updated, but I've updated the code for SOAP-GP as well as the readme now :)


Deadlock while sending keep alive

Describe the bug
App crashes with the deadlock on SignalR.hubconnection.queue while sending keepAlive token
Expected behavior
No crashes occur
Enable logging at the debug level and attach/past to the issue
Crashed: SignalR.hubconnection.queue
0  libdispatch.dylib              0x1277c __DISPATCH_WAIT_FOR_QUEUE__ + 468
1  libdispatch.dylib              0x122b0 _dispatch_sync_f_slow + 148
2  SwiftSignalRClient             0x15c50 $s18SwiftSignalRClient13HubConnectionC14resetKeepAlive33_BCC7D37BC150A1E312A2AFABE4B9B5C6LLyyF + 444
3  SwiftSignalRClient             0x1640c $s18SwiftSignalRClient13HubConnectionC17sendKeepAlivePing33_BCC7D37BC150A1E312A2AFABE4B9B5C6LLyyFys5Error_pSgcfU_ + 204
4  SwiftSignalRClient             0x2d6f0 $s18SwiftSignalRClient23ReconnectableConnectionC4send4data0F11DidCompletey10Foundation4DataV_ys5Error_pSgctF + 356
5  SwiftSignalRClient             0x302b4 $s18SwiftSignalRClient23ReconnectableConnectionCAA0E0A2aDP4send4data0F11DidCompletey10Foundation4DataV_ys5Error_pSgctFTW + 20
6  SwiftSignalRClient             0x16278 $s18SwiftSignalRClient13HubConnectionC17sendKeepAlivePing33_BCC7D37BC150A1E312A2AFABE4B9B5C6LLyyF + 652
7  SwiftSignalRClient             0xcc84 $sIeg_IeyB_TR + 28
8  libdispatch.dylib              0x11fb8 _dispatch_block_async_invoke2 + 148
9  libdispatch.dylib              0x3db0 _dispatch_client_callout + 20
10 libdispatch.dylib              0x712c _dispatch_continuation_pop + 416
11 libdispatch.dylib              0x18c08 _dispatch_source_invoke + 1260
12 libdispatch.dylib              0xafd8 _dispatch_lane_serial_drain + 272
13 libdispatch.dylib              0xbc5c _dispatch_lane_invoke + 408
14 libdispatch.dylib              0x15d78 _dispatch_workloop_worker_thread + 708
15 libsystem_pthread.dylib        0x3814 _pthread_wqthread + 276
16 libsystem_pthread.dylib        0xa76c start_wqthread + 8

Thanks for the report. It looks like a duplicate of #264 which was already fixed but not yet released to Cocoapods

@moozzyk  when do you plan to make it available from Cocoapods?

I should be able to get to this in a few weeks. If you need it sooner, please consider: https://github.com/sponsors/moozzyk?frequency=one-time&sponsor=moozzyk

I pushed version 0.9.2 to Cocoapods.


feat(generic): add Range

What?
add Range
Why?
It's on the todo list
How?
preallocate the slice and go through each index and set the value to index+min

Codecov Report
Base: 97.78% // Head: 97.79% // Increases project coverage by +0.01% :tada:

Coverage data is based on head (8ea6609) compared to base (0713311).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #59      +/-   ##
==========================================
+ Coverage   97.78%   97.79%   +0.01%
==========================================
  Files           8        8
  Lines         901      907       +6
==========================================
+ Hits          881      887       +6
  Misses         14       14
  Partials        6        6

Impacted Files
Coverage Δ

generic.go
100.00% <100.00%> (ø)

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


open url in new tab on button click

🐛 Bug Report
A clear and concise way is to open the URL is to the new tab, not the same tap.
WRONG

Onclick open in new tap CORRECT WAY

I would like to work on this issue under LGMSOC, please assign me!

I would like to work on this bug. I have experience with the mentioned feature as I have implemented the required feature in my portfolio website.  Please assign this issue to me under LGM-SoC.

Is it necessary @nilisha-jais ?

Is it necessary @nilisha-jais ?

I guess opening in new tab on clicking, might be a convenient way.

we have an option of back button I guess we don't need it

we have an option of back button I guess we don't need it

@nilisha-jais Okay!


.stop() sometimes hangs indefinitely

Version:
1.8.1

Subsystem:
@libp2p/websocket , connection manager, components

Severity:
High
Description:
Steps to reproduce the error:
I have a test scenario with a few nodes that I connect to each other and send some data
Sometimes when terminating a node it endlessly waits for the Websocket transport to shutdown. This is because there are connections that does close (?) and in the it-ws library there are no calls to server.closeAllConnections() before close.
I have managed to make the shutdown work better if  modify https://github.com/libp2p/js-libp2p/blob/73f2b6b6d767492f8f1d740fac382a2d22c3fca1/packages/libp2p/src/components.ts#L72 to terminate the components in the reverse order in sequentially... so I suspect there is some kind of race condition going on or leak of some sort
Also no issues if I use Tcp transport instead.
This is not a good description on how to reproduce the issue, because it is a bit random when it occurs. But wanted to create this issue if others have the same problem and will update the description if I have a isolated a good test

When the stop timeouts, I one connection left with 0 streams,
remoteAddr: '/ip6/::ffff:7f00:1/tcp/56327/p2p/12D3KooWApN6mEB5666wTpqpzkgcKXC7kgMxmm7CAWRiD3WAg4Yv'
direction:  'inbound'
encryption: '/noise'
multiplexer: '/yamux/1.0.0'
transient: false

Closing the connectionManager component seems also to fix the issue

in the it-ws library there are no calls to server.closeAllConnections() before close.

I may be missing something but where is the closeAllConnections method defined?  The it-ws module stores a reference to a http/https net.Server which has no such method.

no issues if I use Tcp transport

Looking at the code, the TCP listener aborts each connection on close whereas the WebSocket transport tries to close them gracefully.
Do you still see the issue if the transport aborts the connections instead of closing them on close?

http.Server and https.Server has that method  since NodeJs 18.2.0
/// it-ws/server.ts

 async close (): Promise<void> {
    await new Promise<void>((resolve, reject) => {
      this.server.closeAllConnections()
      this.server.close((err) => {
        if (err != null) {
          reject(err); return
        }

        resolve()
      })
    })
  }

Actually the closeAllConnections trick does work since the connection is a tcp one (?)
The close connection manager first trick seems to always work.
Also adding like a 5s delay before stopping also seems to work

http.Server and https.Server has that method since NodeJs 18.2.0

Aha, that's interesting, nice find.
The docs do say though:

This does not destroy sockets upgraded to a different protocol, such as WebSocket or HTTP/2

...so I wonder if there's something else going on here?

Ye the whole thing about aborting Websocket connections before closing does not seem to have an impact. Only the two things I mentioned in my last comment did mitigate the problem for me

Looking at the code, the TCP listener aborts each connection on close whereas the WebSocket transport tries to close them gracefully.

That would explain something!


fix(lspinfo): respect custom PATH when checking whether cmd is executable

Super hacky, but this was the easiest, least intrusive, improvement I could think of.

I assume this has to do with nvim-lsp-installer. But it would be nice with some context.

I assume this has to do with nvim-lsp-installer. But it would be nice with some context.

Yeah I'd wager >99% of the cases where servers are set up with a modified PATH would be via nvim-lsp-installer. The motivation behind this is to improve the troubleshooting experience when using nvim-lsp-installer. This error will be displayed all of the time (unless the user has the server installed on PATH) should a server fail to start for some reason, even if the LSP client was able to locate the executable. It has led to people (rightfully) assuming that something is broken with the server installation via nvim-lsp-installer, when that is not the case.
I think it'd be nice if the client interface were to expose any errors it encounters, currently I believe it always returns nil if something goes wrong, for example:

https://github.com/williamboman/neovim/blob/fa35548343afe09c969574e58a50a31b8d14c57b/runtime/lua/vim/lsp.lua#L865-L864
https://github.com/williamboman/neovim/blob/fa35548343afe09c969574e58a50a31b8d14c57b/runtime/lua/vim/lsp/rpc.lua#L336

I wouldn't mind if this is declined btw, it's really hacky. Other terrible ideas I had include:

actually attempt to spawn (via libuv, same as rpc client) the server process and immediately kill it
spawning an ephemeral headless nvim instance with a modified path and capture its output (nvim --headless -c "echo executable(%q)")

I'll try to hack this into lsp installer instead

For reference: https://github.com/williamboman/nvim-lsp-installer/pull/691


ICES rectangles being calculated incorrectly

Describe the bug
ICES rectangles being calculated incorrectly:

The automation of ICES Rectangle from Lat/Long info seems partially broken. While some squares were calculated accurately, other inputs generated results such as ‘49E10’ & ‘49E11’, which simply don’t exist in the ICES system. (These did not correspond with information for ‘49F0’ or ‘49F1’, as might be expected, but for Lat/Longs within ‘49E9’.)

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Correct ICES rectangles should be calculated
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):

Device: [e.g. Samsung Galaxy S9]
Android version: [e.g. 8.1]
App version [e.g. 0.2]

Additional context
See CatchLocation.getIcesRectangle()

Could only reproduce by supplying minute values > 60. Have added UI restrictions to stop user entering minute values greater than 60, added code to change values greater than 60 that make it through to 59.


Add William Schwab to Contributors list

@wschwab, I'm quite elated about your PR. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a PR and learned that I merged it?

It's a really good feeling. I mean, contributing to open source, especially
for a newcomer to the coding community, involves taking the plunge into
doing work that others will be able to see and review. To have it broken
down in a way that's easy to follow, and then to be able to succeed, is
great. It makes contributing look more accessible.
Your links at the bottom are also really informative. I've been poking
around over there, seeing if there's something I can handle. Thanks for
taking the time to set all of that up!
On Tue, Sep 5, 2017 at 7:44 AM, Roshan Jossey<EMAIL_ADDRESS>wrote:

Merged #441 https://github.com/Roshanjossey/first-contributions/pull/441
.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Roshanjossey/first-contributions/pull/441#event-1234177001,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeIR4ySmbg3izPeaV6hPMl03NMV-sK4Iks5sfNHGgaJpZM4PLtJ0
.

@wschwab, I’d urge you to continue contributing to other open source projects.
We also have a slack team to help/mentor people trying to contribute to open source projects.
You can join the team by going to https://firstcontributions.herokuapp.com