Eclipse won't stop building workspace

I configured Jaxb2 Plugin as follows in a project, and now Eclipse is in loop, always rebuilding the project over and over. Am I doing anything wrong? This seemed like a common way to generate resources from WSDL.
<build>
	<plugins>
		<plugin>
			<groupId>org.jvnet.jaxb2.maven2</groupId>
			<artifactId>maven-jaxb2-plugin</artifactId>
			<version>0.13.1</version>
			<executions>
				<execution>
					<goals>
						<goal>generate</goal>
					</goals>
				</execution>
			</executions>
			<configuration>
				<schemaLanguage>WSDL</schemaLanguage>
				<generatePackage>br.com.itau</generatePackage>
				<schemas>
					<schema>
						<url>https://ww2.itau.com.br/2viabloq/2ViaXMLWebSvc.asmx?WSDL</url>
					</schema>
				</schemas>
			</configuration>
		</plugin>
	</plugins>
</build>

Please send me a PR with a sample project in https://github.com/highsource/maven-jaxb2-plugin-support under 2/2viabloq. I'll take a look.

I've sent the PR with the project, but there's something specific on it that causes the problem. Newer projects with the same POM structure doesn't loop in Eclipse. However, i've not been able to trace it.

Thank you for the PR.
There are two parts of the problem.
One is why maven-jaxb2-plugin regenerates the code. This is due to the fact that you compile an online resource and the server does not provide the Last-Modified header. Here's a snippet from the logs:
5/18/18, 9:37:47 PM GMT+2: [WARN] The URI [https://ww2.itau.com.br/2viabloq/2ViaXMLWebSvc.asmx?WSDL] seems to represent an absolute HTTP or HTTPS URL. Getting the last modification timestamp is only possible if the URL is accessible and if the server returns the [Last-Modified] header correctly. This method is not reliable and is likely to fail. In this case the last modification timestamp will be assumed to be unknown.
5/18/18, 9:37:48 PM GMT+2: [ERROR] Could not retrieve the last modification timestamp for the URI [https://ww2.itau.com.br/2viabloq/2ViaXMLWebSvc.asmx?WSDL] from the HTTP URL connection. The [Last-Modified] header was probably not set correctly.
5/18/18, 9:37:48 PM GMT+2: [WARN] Last modification of the URI [https://ww2.itau.com.br/2viabloq/2ViaXMLWebSvc.asmx?WSDL] is not known.
5/18/18, 9:37:48 PM GMT+2: [INFO] Sources are not up-to-date, XJC will be executed.

To work around this, create a local copy of the WSDL and use a catalog file to rewrite URLs. I explicitly do not recommend building online resources. It breaks reproducible builds.
Next problem is why Eclipse keeps rebuilding. I honestly don't know. Probably Eclipse detects that new files were generated (i.e. that something is changed in sources) and rebuilds the whole project. Who knows.
I also prefer to consider IDE integration to be out of the scope of the maven-jaxb2-plugin.

Ok, thanks for the feedback!


fixed make test failure in osx 10.10.5 - see https://github.com/docker/hyperkit/issues/52

make test was failing due to the mktemp variation in osx 10.10.5

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "mktemp-fix" git@github.com:ashee/hyperkit.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.


[Addition]:

Hotspot b58 Addresses
112nUUzgHQ5aNLAyrD2SULndRvffTSt3ymNne1zPDb7K5hW1dgBZ
Discord Handle
Zakzouk
Reason(s)
Relayed and very high earning
unusual activities
very far away witnessing
in the same wallet 2 miners  exact the same behaviours
wallet 13FDESFPFhQ2LMVupawvFg4jdy3nWwAaG6HgiT48mFupx7qbmVd

We have taken into account this addition request in the next iteration of the denylist. Some or all of the Hotspots listed may be added to the denylist. This is an automated comment due to the volume of addition and removal requests. A future tool is in the works to provide more insight into the analysis approach made by the Helium team and community members that maintain this list.


Allow get local ip to work without internet

get_local_ip would fail if there was no internet connection. Now it is defaulting to <IP_ADDRESS>.
This allows using the HTTP component without an internet connection.

This error only occurs when you turn off all network interfaces. In that case you only have access to loopback


Fixing nit comments from previous DW mutation support prs.

Why make this change?
Fixing nit comments from earlier pr: https://github.com/Azure/data-api-builder/pull/1978
What is this change?
There were some nit comments to fix while adding implementation for mutation support for DW.
How was this tested?
Existing tests should cover as this pr only handles nit fixes.

/azp run

/azp run


Upgrading to 7.0.0 ends up with dummyQuery, dummyMutation and dummySubscription placeholders only in the Schema

Hello, after upgrading to 7.0.0 (from 6.2.3) the thing stops working and I only get those dummy placeholders. I don't use any integration with frameworks, however I am using Slim Framework to provide middleware functionality "above" the GraphQL (e.g. for processing authentication headers) and GraphQLite is the handler of the Slims middleware stack.
The only BC break mentioned in docs is SchemaFactory::setClassNameMapper being renamed to SchemaFactory::setFinder. I don't call SchemaFactory::setClassNameMapper anywhere so I don't think I sould be affected.
I also noticed slight change in documentation example where ->addControllerNamespace('App\\Controllers\\') is replace with ->addControllerNamespace('App\\Controllers'). I checked and I am using it without the trailing backslash. Schema and type namespaces are same in my case.
This is my code dumbed down to a minimal version that works in 6.2.3 and doesn't work in 7.0.0:
        $schemaFactory = (new \TheCodingMachine\GraphQLite\SchemaFactory(
            $cache,
            $container,
        ))
            ->addControllerNamespace("MyApp\\Graph\\Schema")
            ->addTypeNamespace("MyApp\\Graph\\Schema");

        $graphQlServer = new \GraphQL\Server\StandardServer([
            'schema' => $schemaFactory->createSchema(),
            'context' => new \TheCodingMachine\GraphQLite\Context\Context(),
        ]);

        $requestHandler = new class($graphQlServer) implements \Psr\Http\Server\RequestHandlerInterface {
            public function __construct(
                private readonly \GraphQL\Server\StandardServer $server
            ) {
            }

            public function handle(
                \Psr\Http\Message\ServerRequestInterface $request
            ): \Psr\Http\Message\ResponseInterface {
                $result = $this->server
                    ->processPsrRequest(
                        $request,
                        (new \Slim\Psr7\Factory\ResponseFactory())->createResponse(),
                        new \Slim\Psr7\Stream(\Safe\fopen('php://temp', 'w'))
                    );

                if ($result instanceof \Psr\Http\Message\ResponseInterface) {
                    return $result;
                }

                throw new \LogicException('Unexpected result of GraphQL server encountered: `' . get_class($result) . '`');
            }
        };

        $middlewareDispatcher = new \Slim\MiddlewareDispatcher(
            $requestHandler
        );

        $middlewareDispatcher
            ->addMiddleware(new \Slim\Middleware\BodyParsingMiddleware())
        ;

        (new \Slim\ResponseEmitter())->emit(
            $middlewareDispatcher
                ->handle(
                    \Slim\Factory\ServerRequestCreatorFactory::create()->createServerRequestFromGlobals()
                )
        );

This is the full log from composer update:
- Removing thecodingmachine/class-explorer (v1.1.0)
   - Removing mouf/classname-mapper (v1.0.2)
   - Upgrading symfony/cache (v6.4.10 => v7.1.3): Extracting archive
   - Upgrading symfony/expression-language (v6.4.8 => v7.1.1): Extracting archive
   - Installing kcs/class-finder (0.4.0): Extracting archive
   - Upgrading thecodingmachine/graphqlite (v6.2.3 => v7.0.0): Extracting archive
My PSR Container is very thin custom adapter for Nette\DI\Container that is in production for years in many projects.
My PSR Cache is also very thin adapter for Nette\Caching\Cache. There used to be problems in history but more with performance and I don't think this might be the case. I also purged the cache 😉.
What might be wrong? Any help appreciated ♥.

Well, clearly there is some class mapping issues going on.  By default, the new class mapper uses the Composer autoload.  Is your namespace autoloaded by Composer?  If not, add it to your composer.json, or use the SchemaFactory::setFinder method to set a Finder instance that correctly loads the classes.
If that's handled correctly, you're going to need to manually debug the class loading to find out what's being loaded.  Ultimately though, the new class-finder isn't finding your namespace it seems.
Also, if this is the case, we should probably add a validation check to see if the namespace exists.  I think it'd probably be okay to throw an exception if a namespace provided doesn't have any classes found.  I'm guessing this is quietly ignored currently.

Please, don't close it yet. I have the debugging in my TODO. Indeed all my classes are autoloaded by Composer (PSR-4). I want to Xdebug it but didn't have time.

Feel free to reply back with details and we can reopen it.

So it turned out that the bundled class-finder doesn't look into composers fallback directories.
The obvious solution was to change:
  "autoload": {
    "psr-4": {
      "": "src/",
      "SomeNamespace\\": "packages/"
    }
  },

to
  "autoload": {
    "psr-4": {
      "": "src/",
      "MyApp\\Graph\\Schema": "src/MyApp/Graph/Schema",
      "SomeNamespace\\": "packages/"
    }
  },

Maybe it could be mentioned in the docs (unless the https://github.com/alekitto/class-finder/issues/22 is fixed).
I realize there is this:
  "autoload": {
    "psr-4": {
      "App\\": "src/"
    }
  }

But I humbly believe it is not obvious enough. Looks almost exactly like:
  "autoload": {
    "psr-4": {
      "": "src/"
    }
  }

and obviously APP is only an example.
Thanks. Problem solved on my end. Have a nice day :-)

GraphQLite's classfinder now uses Composer's autoload.  So yea, whatever you define in your Composer config is going to be what's available to GraphQLite.  I don't think there is much more to explain here.  But if you'd like to improve the docs, a PR would be welcomed and appreciated.  IMO, Composer's autoload functionality should be pretty straightforward and understood by most developers.  And GraphQLite leveraging that autoload, and not trying to handle it some other way, is ideal.

Oh no, my classes ARE autoloaded by Composer. They are, however autoloaded by method, that is not implemented by class-finder. Fallback PSR4 directory.

Looks like class-finder has been fixed already 😅.
https://github.com/alekitto/class-finder/issues/22

Oh, I see.  Please submit a PR after testing to bump the class-finder package version.

Wow, during testing the fix for class-finder I found out that the class-finder includes all the files in the directories. This is crazy side effect to say at least.
I understand that mixing php scripts and classes is a bad practice. I have sort of a template written in php somewhere in the app and its contents started appearing in all the API responses 😆.
The problem didn't show up until the composer fallback directory got implemented.

Finally I decided to implement my own finder since there are problems with Kcs (sorry) and there is straightforward way for me in my application.
But man, the Filter interface of the SchemaFactory::setFinder's parameter is complicated 👀 !
And you only use the iterator and inNamespace feature (which is hardly useful in custom finder as it can be easily managed there) 😭 .
Not to mention that it is from third party's package I did not explicitly install. I believe you should make your own simpler interface. What happens if you decide to replace Kcs for some reason?
You should maybe think about a feature where user would simply pass the list of classes to the schema and that's it.
namespace TheCodingMachine\GraphQLite;

interface Finder {
  public function getClasses(): iterable;
}

PS: I plan to use Nette\RobotLoader to find classes. Maybe you should take a look too 😉.

Finally I decided to implement my own finder since there are problems with Kcs and there is straightforward way for me in my application.
But man, the Filter interface of the SchemaFactory::setFinder's parameter is complicated 👀 !
And you only use the iterator and inNamespace feature (which is hardly useful in custom finder as it can be easily managed there) 😭 .
Not to mention that it is from third party package I did not explicitly install. What happens if you decide to replace Kcs for some reason?
This should be pretty much it:
namespace TheCodingMachine\GraphQLite;

interface Finder {
  public function getClasses(): iterable;
}

PS: I plan to use Nette\RobotLoader to find classes. Maybe you should take a look too 😉.

Oh, I see. Please submit a PR after testing to bump the class-finder package version.

I don't think class-finder needs bumping. The fix has been released in 0.5.4. GraphQLite requires ^0.5.1 which will install the fixed version.
People for whom the version 0.5.1 works will continue with no change, new installs will have 0.5.4.

@josefsabl adding the setFinder is a new feature that was added to allow for customization of Kcs mostly.  It wasn't really fully intended to support other class finder implementations.  However, from a design perspective, it probably should have been.  If you'd like to improve on this with a managed interface and adapter for Kcs, that'd be something we can consider merging.  It'd obviously be a BC break at this point, but I think that's fine - most people will be using the default finder implementation, and this is a newer addition as well.


libicns: 0.8.1 → 0.8.1-unstable-2022-04-10

Description of changes
Update libicns from 0.8.1 (2012-06-14, yes, thirteen years ago) to the current Git commit. This is also the commit packaged in Debian as <IP_ADDRESS>.g921f972-0.1, and fixes many issues.
https://github.com/GerHobbelt/libicns/compare/0.8.1...921f972c461c505e5ac981aaddbdfdde97e8bb2b
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041512
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.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.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2656

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2744

Hmm, someone else did this upgrade in #252255 without checking existing PRs.

#252255

Then there should have been a merge conflict, right? But I don't remember GitHub showing that to me. Maybe I overlooked it.
Why does the other PR have an additional zlib argument in buildInputs?


got-10k dataset link

hi, i have requested the link for dataset multiple times, but i havent recieved it yet. can anyone please forward it to me at<EMAIL_ADDRESS>

This bug was fixed. Please try again, thanks.

I have this problem as well. Any updates?


Are you guys using the variable "key" in yield return?

https://github.com/Microsoft/BotBuilder/blob/e927e34aab62c2fd199b6ac7921a37d4d3aa9a66/CSharp/Library/Microsoft.Bot.Builder/Dialogs/LuisDialog.cs#L409
Can you guys use the variable key in yield return in the statement below?

Hi kiranchand,
Thanks for pointing this out. Seems that the key variable was created for it to be later returned in this case. I will review and get back to you.
Francisco


[Bug]: Theme collection

What happened?
Hello,
I think, we got a regression.
On class Themes, the collection definition is Name=>class
        $this->collection = collect([
            DefaultTheme::getName() => DefaultTheme::class,
            Nord::getName() => Nord::class,
            Sunset::getName() => Sunset::class,
        ]);

but make is returning "default". By the way, this collection is key=>class. No need to first, but a simple get().
Or need to reverse the collection key/value.
    public function make(string $theme): Theme
    {
        $name = $this->collection->get($theme);
        if ($name) {
            return new $name;
        }
    }

Between the __construct & make, the collection changed :
Illuminate\Support\Collection {#1478 ▼ // vendor\hasnayeen\themes\src\Themes.php:42
  #items: array:3 [▼
    "default" => "default"
    "nord" => "nord"
    "sunset" => "sunset"
  ]
  #escapeWhenCastingToString: false
}

How to reproduce the bug
Install
Package Version
v3.0.10
PHP Version
8.2.4
Laravel Version
v3.0.39
Notes
No response

A fix has been pushed 04a7476, should be ok now


'GoogleUtilities/GULKeychainStorage.h' file not found

Having this issue when uses the latest Firebase iOS SDK

This issue is still there. Please provide a valid solution


Godrays

Could you add the ability to enable and control volumetric lighting in the next update :)

Hi, I made a separate mod during 5.9.0-dev for controlling the volumetric lighting: Volumetric Lighting.


Refactor Tetris client code & fix React unique key warnings

TBS-71

Move WebSocket management to the parent page component, which allows passing the game state to other components other than the Tetris game

TBS-72

Update the level & score fields on the client using the game state data

TBS-74

Assign unique keys to children in a list (see React’s Keys)

:rocket:


Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

🐛 Description
When upgrading from magic-sdk v6.2.1 to magic-sdk v8.1.0 within a perfectly working VueJS3 project, I am getting this warning when serving my app (yarn serve):
 WARNING  Compiled with 1 warning
 warning  in ./node_modules/magic-sdk/dist/es/index.js
Critical dependency: require function is used in a way in which dependencies cannot be statically extracted

🌎 Environment

Software
Version(s)

magic-sdk
8.1.0

Browser
Chrome

yarn
1.22.17

Operating System
Windows

Please provide a reproducible example and we'll take a look.

Please provide a reproducible example and we'll take a look.

I just created a Nuxt project with TailwindCSS preset and installed Moralis with dependencies and I get this error

Please provide a reproducible example and we'll take a look.

Same issue breaking our build using Magic-SDK 8.1.0 at Blocknative

Clone https://github.com/blocknative/react-demo
Switch to develop branch
run rm yarn.lock && yarn install --network-concurrency 1
run yarn build
see errors

Critical dependency: require function is used in a way in which dependencies cannot be statically extracted```

+1

Please provide a reproducible example and we'll take a look.

This is pretty reproducible in like 5 minutes, depending on how much you want to develop your library. Again, creating a Nuxt project with TailwindCSS preset and installing Moralis dependencies makes this error show up on my screen.

Please provide a reproducible example and we'll take a look.
@smithki
We have customers sending us this issue trying to make Magic available to their customers and their build breaking.
Please update us on the progress of this so we can pass along

Thank you for the code sample @Adamj1232. I'm off-the-clock this week but will make time for this early next week.

After digging into this issue a bit, the warning appears to be related to this code being inlined into magic-sdk's ESM output:
var __require = /* @__PURE__ */ ((x) => typeof require !== "undefined" ? require : typeof Proxy !== "undefined" ? new Proxy(x, {
  get: (a, b) => (typeof require !== "undefined" ? require : a)[b]
}) : x)(function(x) {
  if (typeof require !== "undefined")
    return require.apply(this, arguments);
  throw new Error('Dynamic require of "' + x + '" is not supported');
});

This could either be resolved at the ESBuild layer, but can be worked around for your individual purpose by adjusting your bundler config to resolve magic-sdk to its CommonJS entrypoint (magic-sdk/dist/cjs/index.js), which won't manifest this warning. It is also valid to ignore this warning using whatever API/plugin your bundler provides to silence noisy logs. This warning in context of magic-sdk will not manifest any bugs at runtime.

Wonderfull, thanks @smithki

@smithki can you give an idea of what this bundler config would look like to resolve to CommonJS entrypoint? We have multiple customers asking for examples

@Adamj1232 that would really depend on your bundler. I suggest looking for docs specific to your tooling. Unfortunately, there is no "conventional wisdom" to share.

@Adamj1232 that would really depend on your bundler. I suggest looking for docs specific to your tooling. Unfortunately, there is no "conventional wisdom" to share.

Do you have examples for webpack and rollup? Those are the most common for our users

I can point you to these resources, but have not yet attempted to write a working example:

Webpack resolve.alias
Rollup @rollup/plugin-alias

For the record, I don't work at Magic anymore. All I can provide is limited "free" support like this. If you are looking for extra help, I suggest you reach out to Magic's support team directly, or try StackOverflow.

Thx @smithki, I'll take it from here.
Though I'm not an expert on ESbuild, I will start to check the demo in the thread. @Adamj1232 Feel free to ping me for any more context you have.

@Ethella I have a fix for react using CRACO
const path = require("path");

module.exports = {
  reactScriptsVersion: "react-scripts" /* (default value) */,

  webpack: {
    alias: {
      "magic-sdk": path.resolve(
        __dirname,
        "node_modules/magic-sdk/dist/cjs/index.js"
      ),
    },
  },
};

For pure webpack I believe alias is nested with resolve ... resolve.alias...
These would be helpful to add to your documentation

I was about to say I found no issues reported during the build because you already fixed it 🚀.
I'll update our doc to reflect your suggestion. Thx a lot!

Hey, @Adamj1232  how to do the same for node.js? I can't upload my backend to Heroku because of this same problem. I could solve it for the frontend using your suggestion, but how about node.js? Thank you a lot.

@andreisucman you would have to look into the documentation for the compiler you are using.

@Adamj1232 . I'm using webpack. Here is my config. How can I modify it?
module.exports = {
mode: 'production',
entry: './lib/engine.mjs',
output: {
library: 'js-chess-engine',
libraryTarget: 'umd',
globalObject: 'this',
umdNamedDefine: true,
filename: 'engine.js',
},
}

I think it would be something like this but you would have to do some testing to confirm.
Official docs for webpack - https://webpack.js.org/configuration/resolve/#resolvealias
module.exports = {
    mode: 'production',
    entry: './lib/engine.mjs',
    output: {
        library: 'js-chess-engine',
        libraryTarget: 'umd',
        globalObject: 'this',
        umdNamedDefine: true,
        filename: 'engine.js',
    },
  resolve: {
    alias: {
        "magic-sdk": path.resolve(__dirname, "node_modules/magic-sdk/dist/cjs/index.js"),
    }
  }
}

Thank you @Adamj1232. I'll test and write.

@Adamj1232 It worked! Thanks again. Here is the full snippet for node js using webpack (make sure to update mode, entry, and output per your project).
const path = require("path");

module.exports = {
  mode: "production",
  entry: "./lib/engine.mjs",
  output: {
    library: "engine",
    libraryTarget: "umd",
    globalObject: "this",
    umdNamedDefine: true,
    filename: "engine.js",
  },
  resolve: {
    alias: {
      "magic-sdk": path.resolve(
        __dirname,
        "node_modules/magic-sdk/dist/cjs/index.js"
      ),
    },
  },
};

Possible resolution on livetime on nextjs:
next.config.js
/** @type {import('next').NextConfig} */
const nextConfig = {

    webpack: (config, {buildId, dev, isServer, defaultLoaders, webpack}) => {
        config.externals.push({
            '@aws-sdk/signature-v4-multi-region': 'commonjs @aws-sdk/signature-v4-multi-region',
        })

        return config
    },
}

module.exports = nextConfig


Log files are automatically deleted now

Description
As of change 31b7c35bae6ee5aefaa539feefb4ac172dde77ff, it doesn't seem to be possible to retain logs from renderdoccmd. We used this in automated tests trying to replay a bunch of .rdc files as part of a regression test. We'd call renderdoccmd replay <trace.rdc> and set RENDERDOC_DEBUG_LOG_FILE=/path/to/log.txt and would store the log.txt file produced in test artifacts, so when replay fails, we'd know exactly what happened on RenderDoc side. Now the file is deleted and we no longer have this information to go by. What is the recommended way of collecting replay logs?
Steps to reproduce
RENDERDOC_DEBUG_LOG_FILE=/path/to/log.txt renderdoccmd replay sample.rdc

The produced log file is deleted when renderdoccmd quits and it is not possible to get debug log messages that might point to the reason why replay failed (like specific driver compatibility issues)
Environment

RenderDoc version: 11719a2588544a12947f809a384c4cfe57a1e03e
Operating System: Linux
Graphics API: Vulkan

renderdoccmd and RENDERDOC_DEBUG_LOG_FILE are internal implementation details and are not user facing, you should not be referencing these directly yourself. What you're describing is not a bug, you were relying on broken behaviour which has now been fixed.
If you use the renderdoc replay API e.g. with a python script you can obtain the log path with renderdoc.GetLogFile() and read the file contents to store them, as happens in the functional tests.


[Event Request] table 472 "Job Queue Entry" - OnCleanupAfterExecutionOnAfterDeleteJQEntry

Can we please get the following event?
local procedure CleanupAfterExecution()
var
    JobQueueDispatcher: Codeunit "Job Queue Dispatcher";
    SessionId: Integer;
begin
    if "Notify On Success" then
        if Session.StartSession(SessionId, Codeunit::"Job Queue - Send Notification", CurrentCompany(), Rec) then;

    if "Recurring Job" then begin
        ClearServiceValues();
        if Status = Status::"On Hold with Inactivity Timeout" then
            "Earliest Start Date/Time" := JobQueueDispatcher.CalcNextRunTimeHoldDuetoInactivityJob(Rec, CurrentDateTime)
        else
            "Earliest Start Date/Time" := JobQueueDispatcher.CalcNextRunTimeForRecurringJob(Rec, CurrentDateTime);
        EnqueueTask();
//+Change
//-    end else
//-        Rec.Delete();
    end else begin
        Rec.Delete();
        OnCleanupAfterExecutionOnAfterDeleteJQEntry(Rec);
    end;
//-Change
end;

[IntegrationEvent(false, false)]
local procedure OnCleanupAfterExecutionOnAfterDeleteJQEntry(JobQueueEntry: Record "Job Queue Entry")
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Page 70 - 'docker build -f Dockerfile.test -t <IP_ADDRESS>:5000/books-ms-tests .' fails

<EMAIL_ADDRESS>node_modules/gulp-yuidoc
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>events.js:85
throw er; // Unhandled 'error' event
^
Error: ENOENT, rename '/tmp/053eb721967ff1d04dee652255581f3b/bower/deacf902f90ca6d3b27910fca875e706-71-NmJB8X/archive.tar.gz.1261675549'
at Error (native)
The command '/bin/sh -c cd /source/client && npm install && bower install --allow-root --config.interactive=false -s' returned a non-zero code: 1
vagrant@cd:~/books-ms$

I just rerun the commands from the "Implementation of the Deployment Pipeline: Initial Stages" chapter and could not reproduce the problem you are facing. The image was built without any error.
The issue you reported might be a temporary glitch in npm that was resolved in the mean time. Can you please re-run it again and check whether it still fails. If it is still not working, it is probably somehow related to your laptop, network, or something else specific to your environment. In that case, maybe we can have a chat on Skype or HangOuts and share your screen. That way I might be able to find out what the problem is.

Issue is reproducible.  Agree that it is likely related to my environment.

Running by hand as described in that chapter consistently results in the aforementioned error.  However, it builds correctly when executed by Jenkins as described in the 'Clustering and Scaling Services' chapter.  Go figure.

The difference is that the command you executed manually runs in a loop
with the idea to test any change to FE while you're developing. Even though
tests are temporarily disabled, the loop is still there and needs to be
stopped with ctrl+c. The tests in Jenkins are one-off thing. They run once.
On Tue, Dec 6, 2016 at 10:34 AM Michael Estrin<EMAIL_ADDRESS>wrote:

Running by hand as described in that chapter consistently results in the
aforementioned error. However, it builds correctly when executed by Jenkins
as described in the 'Clustering and Scaling Services' chapter. Go figure.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/vfarcic/ms-lifecycle/issues/24#issuecomment-265232798,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFc5A7ROxbnj2ykUgme2jnDuhI2lEo7Fks5rFarNgaJpZM4LElKw
.


microservice jar file size

Hi,
I use vertx to create microservices running on openshift.
But now I figured out that if I include this modues as dependency my fat jars get a file size of > 50mb.
Is there a possibility to keep my jars small? IMHO having microservice jars that big is not the idea behind microservices?!
regards, Marco

can you list your actual dependencies with size ?

can we close this issue ?

if you are ok with a file size > 26MB by default then yes

hum that seems to be an hazelcast issue

doesn't hazelcast provide a stripped down version ?

have you looked at the other cluster manager ?

The Hazelcast distribution jar for the latest stable version (3.8.6) is ~8MB (http://search.maven.org/#artifactdetails|com.hazelcast|hazelcast|3.8.6|jar). Which hazelcast artifacts are you including in your microservice fat-jar?

Hi @MarWestermann
As @vbekiaris pointed out, the Vert.x Hazelcast cluster manager depends on a single Hazelcast JAR file. This JAR file is rather small considering the features brought in.
I'm not sure why you need Fabric8 Kubernetes API model and the rest, but it's definitely not an Hazelcast cluster manager issue.

Hi @vbekiaris @tsegismont
Hi don't directly include any hazelcast deps into my jar.. just the vertx-hazelcast:3.4.2 jar.
I just did another test:
create maven bundle by archetype: org.jetbrains.kotlin:kotlin-archetype-jvm:1.1.51
add the fabric8-vertx-plugin to build:
            <plugin>                 <groupId>io.fabric8</groupId>                 <artifactId>vertx-maven-plugin</artifactId>                 <version>1.0.8</version>                 <executions>                     <execution>                         <id>vmp</id>                         <goals>                             <goal>initialize</goal>                             <goal>package</goal>                         </goals>                     </execution>                 </executions>                 <configuration>                     <redeploy>true</redeploy>                     <verticle>${main.verticle}</verticle>                 </configuration>             </plugin>
Add vertx-core:3.4.2 as dependency
Package with mvn clean compile vertx:package
Result: 6,7 MB
Add vertx-hazelcast:3.4.2 dependency
package again
Result: 14 MB
Add vertx-config-kubernetes-configmap:3.4.2
package again
Result: 21,5 MB


Fix daily unused deps check failing without mold

https://github.com/fedimint/fedimint/runs/8255591793?check_suite_focus=true#step:6:285

Codecov Report

Merging #531 (a0f7712) into master (be13df1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #531   +/-   ##
=======================================
  Coverage   72.68%   72.68%
=======================================
  Files          83       83
  Lines       10974    10974
=======================================
  Hits         7977     7977
  Misses       2997     2997

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


FIX No longer train batch-norm layer during pretraining

Fix the issue that the gradient of the batch norm layer was still incorrectly updated during pretraining. On some rare occasions (i.e. some random initializations), this led to the issue that the covariate-informed dimension did not capture the covariate-associated gene expression anymore.
Updated

Freeze batch norm layer during pretraining
Updated unit tests. Unit tests now capture this unwanted behavior

Failed test due to failed HTTP request for test_data (non-essential)

Error in test_data - Remote dataset cannot be downloaded (non-essential) HTTP Error 403: Forbidden


Add capability of plotting mesh

Awesome!
Is there any chance you could do the same additions to the Lua-wrapper? We would like to keep the Python and Lua versions in sync (we are looking into a more sustainable solution in which the Lua-wrapper calls the Python wrapper, making development and maintenance easier).
Also, could you please update the README.md with this new feature?

Maybe it takes a little time to write the lua code for me, because I've never tried that.


One more little fix for %like% search

Changes Unknown when pulling 142fca245ae3bbe238b2494be28cea11bec80282 on one_more_like_search_fix into ** on master**.

Changes Unknown when pulling 95b752517400c430e208634b207f672bca4a5659 on one_more_like_search_fix into ** on master**.


Add Low Trust User messages

Description
Continuation of https://github.com/Chatterino/chatterino2/pull/3502, just that some of the code I made long ago is not on this one. Meaning that there's no background color and there's no resizing SVG.
However, if anyone wants to change it, feel free to. But this is a working functioning version that shows you restricted low trust user messages.
It DOES NOT show "Monitoring" messages, because it would be sending two messages.
Here's an example on how it looks like right now:

Additionally this pull request includes some other changes with the resources generator, but it's all issue free, or should be. As I put a duplicate checker there. So it won't mess up with same named .png and .svg files.

@Mm2PL the checks failed
uhhh and my repo is not so clean uhhh
can someone just take the files from "Add low trust user messages", it has all the changes needed for this to work
and idk

Your checks failed... yes and what should i do about that

this bot has something against _ underscores

Your checks failed... yes and what should i do about that

idk if it's even an issue, the only check it failed is not even important, just code style

idk if it's even an issue, the only check it failed is not even important, just formatting

if the formatting check fails, maybe... fix your formatting?
Also, you haven't added a changelog entry, so that check obviously fails as well, that has nothing to do with the checkbox in the PR template.

These icons look identical to the ones used in ~Twilight~ webchat. Where did you get them from? Please include a license for them if possible. We cannot copy the ones from webchat because we do not have the right to use them in the project.

oh, it's from Twitch
idk what Twilight is

idk if it's even an issue, the only check it failed is not even important, just formatting

if the formatting check fails, maybe... fix your formatting?
Also, you haven't added a changelog entry, so that check obviously fails as well, that has nothing to do with the checkbox in the PR template.

yeah the checkbox wasn't in the PR template, like it used to be
so I thought that this fell off or something

These icons look identical to the ones used in ~Twilight~ webchat. Where did you get them from? Please include a license for them if possible. We cannot copy the ones from webchat because we do not have the right to use them in the project.

oh, it's from Twitch idk what Twilight is
if that's an issue, it can be changed

Here's one for the eye hidden one for example
https://fonts.google.com/icons?selected=Material+Icons:visibility_off:

I tried to commit the requested changes in one uhhh change thingy so the changes can be seen all at once

oh, it's from Twitch idk what Twilight is

I just meant the Twitch's web app.

if that's an issue, it can be changed

Source of icons does matter, please change them to ones we can use. Material icons are ok, fluenticons are preferable since we already use them in the app and won't need to add a license for them. It's better to not get in trouble for copyright issues.

oh, it's from Twitch idk what Twilight is

I just meant the Twitch's web app.

if that's an issue, it can be changed

Source of icons does matter, please change them to ones we can use. Material icons are ok, fluenticons are preferable since we already use them in the app and won't need to add a license for them. It's better to not get in trouble for copyright issues.

what about fonts'google.com?

3 cze 2023 13:52:48 karl-police @.***>:

oh, it's from Twitch idk what Twilight is
I just meant the Twitch's web app.
if that's an issue, it can be changed
Source of icons does matter, please change them to ones we can use. Material icons are ok, fluenticons[https://fluenticons.co/] are preferable since we already use them in the app and won't need to add a license for them. It's better to not get in trouble for copyright issues.
what about fonts'google.com?
—
Reply to this email directly, view it on GitHub[https://github.com/Chatterino/chatterino2/pull/4642#issuecomment-1574889990], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AF62MIUWMT6JILB2EIEJ2U3XJMQQBANCNFSM6AAAAAAYEFVJQE].
You are receiving this because you were mentioned.[Obrazek śledzący][https://github.com/notifications/beacon/AF62MIT65MTLS4CZJULCR4TXJMQQBA5CNFSM6AAAAAAYEFVJQGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS533VAM.gif]Message ID: @.***>

As long as they permit redistribution in an app like ours its fine. Modification would also be nice if they don't have dark/light variation.

3 cze 2023 13:52:48 karl-police @.>:
oh, it's from Twitch idk what Twilight is I just meant the Twitch's web app. if that's an issue, it can be changed Source of icons does matter, please change them to ones we can use. Material icons are ok, fluenticons[https://fluenticons.co/] are preferable since we already use them in the app and won't need to add a license for them. It's better to not get in trouble for copyright issues. what about fonts'google.com? — Reply to this email directly, view it on GitHub[#4642 (comment)], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AF62MIUWMT6JILB2EIEJ2U3XJMQQBANCNFSM6AAAAAAYEFVJQE]. You are receiving this because you were mentioned.[Obrazek śledzący][https://github.com/notifications/beacon/AF62MIT65MTLS4CZJULCR4TXJMQQBA5CNFSM6AAAAAAYEFVJQGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTS533VAM.gif]Message ID: @.>
As long as they permit redistribution in an app like ours its fine. Modification would also be nice if they don't have dark/light variation.

but do we have to add a license credit somewhere for fonts.google.com ?

We would need to do that, if we used their stuff. Paste the license into resources/licenses/google-fonts.txt and add a bit of code to the About settings page (somewhere in widgets/settingspages/) near other licenses.

Added these:
eye, hidden, flag - from https://fluenticons.co/outlined
since these matched more to the Twitch one
these don't really match, but from fluenticons anyways
safetyShieldAlert
those that aren't even used don't even need a replacement

how tf do I revert CHANGELOG conflict bullshit that merged entire master branch?

Superseded by #5056


SIMSBIOHUB-442: Add support for hiding/showing table columns for Obserations and Telemetry

Links to Jira Tickets

https://apps.nrs.gov.bc.ca/int/jira/browse/SIMSBIOHUB-442

Description of Changes

Add support for hiding/showing table columns for Obserations and Telemetry
Added sessionStorage call in order to cache column visibility across app reloads
Renamed ObservationComponent and ManualTelemetryComponent to ObservationsTableContainer and ManualTelemetryTableContainer

Testing Notes

Visit the Manage Observations or Manage Telemetry page
Click the cog icon
You should be able to:

[ ] Show/hide all columns
[ ] Show/hide additional columns

Show/hide some or all columns, then refresh the page. You should:

[ ] See that the visiblity state has persisted across refreshes

Noticed a few things (not sure if these were there before or not):
On the Manage Observations page

Click Add Record
Leave some or all fields empty
Click Save
Validation banner is displayed
Click Discard Changes
Validation banner is still displayed

On the Manage Observations page

Click Add Record
Leave some or all fields empty
Click Save
Validation banner is displayed
Hide one of the columns that is marked as in error
Click the Prev or Next buttons on the validation banner.
Error is thrown when it tries to navigate to one of the hidden columns

visibleColumns[params.colIndex] is undefined

There are also a couple of react errors in the console:

When I first click Add Record.
When I first enter data in the Date column.


add workers - hanging tests

What does this PR do?
seems some tests are failing because of too many workers
Before submitting

[ ] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[ ] Did you read the contributor guideline, Pull Request section?
[ ] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes?
[ ] Did you write any new necessary tests? [not needed for typos/docs]
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] If you made a notable change (that affects users), did you update the CHANGELOG?

PR review

[ ] Is this pull request ready for review? (if not, please submit in draft mode)

Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

Hello @Borda! Thanks for opening this PR.

In the file tests/models/self_supervised/test_scripts.py:

Line 15:36: E231 missing whitespace after ','
Line 34:27: E231 missing whitespace after ','
Line 50:35: E231 missing whitespace after ','
Line 87:20: E231 missing whitespace after ','

Do see the Hitchhiker's guide to code style

Hello @Borda! Thanks for opening this PR.

In the file tests/models/self_supervised/test_scripts.py:

Line 15:36: E231 missing whitespace after ','
Line 34:27: E231 missing whitespace after ','
Line 50:35: E231 missing whitespace after ','
Line 87:20: E231 missing whitespace after ','

Do see the Hitchhiker's guide to code style


Problem with gcode

Hello, I have a older problem with a gcodefile where Bart give me before a reply but after a computer crash i do not find the solution any more. Is it possible to point me back on the rails. i remember i must modify some file before compiling the hole thing.
Gcode file:
disk.txt
Sreenshot:

Thank you in advance

You should ask questions about Grbl_ESP32 on that repo.
https://github.com/bdring/Grbl_Esp32
You can send $e=33 to find out what error 33 is. It is an invalid target for an arc. This means you are telling Grbl to go from an existing location to a new location via a specific arc move. When Grbl calculates that arc move it does not get exactly to that target.
This could be due to the fact that your gcode is not very accurate with only 2 decimal places. You should try to get your CAM program to generate more accuracy. This will insure the best accuracy.
Another way is to allow more tolerance in Grbl. Arc tolerance is set via the $GCode/ArcTolerance setting. The default is 0.002mm. You can see it is very likely that 2 decimal places will produce an error. I would think that $GCode/ArcTolerance=0.03 would work.


Change Log tab missing in device component detail views

Environment

Nautobot version (Docker tag too if applicable): 1.4.2b1
Python version:
Database platform, version: MySQL
Middleware(s): n/a

Steps to Reproduce

Create a device with components (interfaces, power ports, console ports, etc - all components appear to be affected)
Navigate to the device detail view, then to the appropriate device component list view (interfaces, power ports, etc.), then click on an individual component (interface, power port, etc.) in the table, e.g. http://localhost:8080/dcim/console-ports/8b5d0e98-8ed9-4d93-8451-68202fc8253a/

Expected Behavior
"Change Log" tab to be included in the page.

Observed Behavior
"Change Log" tab is missing, however the changelog view does exist as you can manually enter the URL such as http://localhost:8080/dcim/console-ports/8b5d0e98-8ed9-4d93-8451-68202fc8253a/changelog/ in order to view it.
This is probably because the various device component models do not actually inherit from the base ChangeLoggedModel mixin class at present, and so are lacking an instance.get_changelog_url method.

May be a regression resulting from #2049. See also #1424.

Let's bite the bullet and turn these into proper change-logged models. For the migrations to do that, let's set the timestamps of the component's device timestamp. In this context, it is less confusing than using the timestamp of when the migration is run.


PopupMenu Overlay should follow target when resizing window

The overlay generated by clicking the PopupMenuButton seems to be positioned relative to the window and hence moves when the window is resized.
Expected: Overlay should follow the target renderbox, in this case the Container.
created in DartPad
Center(
   child: PopupMenuButton(
          itemBuilder: (context) => ["apple", "orange"]
              .map((e) => PopupMenuItem(
                    child:  Text(e),
                  ))
              .toList(),
          child: Container(
            height: 200,
            width: 300,
            color: Colors.green,
          ),
        ),
    );

Verified this using latest stable on web and desktop.

Web:

https://user-images.githubusercontent.com/67046386/110903162-08d6e480-832d-11eb-88cc-be47eebdb232.mov

Desktop:

flutter doctor -v
[✓] Flutter (Channel stable, 2.0.1, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-GB)
    • Flutter version 2.0.1 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision c5a4b4029c (8 days ago), 2021-03-04 09:47:48 -0800
    • Engine revision 40441def69
    • Dart version 2.12.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

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

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

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

[✓] Connected device (4 available)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.2
    • 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 89.0.4389.82

! Doctor found issues in 1 category.

@shihaohong Hey, Have you started work on this yet? 😄

Hi, I haven't. Let me unassign myself for now. Did you want to give it a try? :P

Just take a look at this, seems a bit tricky, I can try it and probably need your help. : )

Reopening after revert in https://github.com/flutter/flutter/pull/80831

Put relevant discussion information here for the reference of those who are interested in it in the future.
https://github.com/flutter/flutter/pull/80420#discussion_r613813178
https://github.com/flutter/flutter/pull/80831#issue-619763743
https://github.com/flutter/flutter/pull/80831#issuecomment-824164974
CC @HansMuller @shihaohong

I am able to reproduce this issue on the latest stable and master channels.
  flutter doctor -v
[✓] Flutter (Channel master, 3.11.0-2.0.pre.55, on macOS 13.3 22E252 darwin-arm64, locale en-NG)
    • Flutter version 3.11.0-2.0.pre.55 on channel master at /Users/dammya/fvm/versions/master
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 835b892d7f (9 days ago), 2023-05-07 01:30:22 +0530
    • Engine revision 23f730efbf
    • Dart version 3.1.0 (build 3.1.0-83.0.dev)
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /Users/dammya/Library/Android/sdk
    • Platform android-33, build-tools 32.1.0-rc1
    • ANDROID_HOME = /Users/dammya/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

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

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2022.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

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

[✓] VS Code (version 1.78.0)
    • VS Code at /Users/dammya/.Trash/Visual Studio Code 20.07.05.app/Contents
    • Flutter extension version 3.50.0

[✓] Connected device (3 available)
    • Damilola’s iPhone (mobile) • 71c843fa5f3dec767999f36224653c0faa78660e • ios            • iOS 16.4 20E247
    • macOS (desktop)            • macos                                    • darwin-arm64   • macOS 13.3 22E252 darwin-arm64
    • Chrome (web)               • chrome                                   • web-javascript • Google Chrome 113.0.5672.92

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[✓] Flutter (Channel stable, 3.10.0, on macOS 13.3 22E252 darwin-arm64, locale
    en-NG)
    • Flutter version 3.10.0 on channel stable at /Users/dammya/sdks/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 84a1e904f4 (6 days ago), 2023-05-09 07:41:44 -0700
    • Engine revision d44b5a94c9
    • Dart version 3.0.0
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version
    32.1.0-rc1)
    • Android SDK at /Users/dammya/Library/Android/sdk
    • Platform android-33, build-tools 32.1.0-rc1
    • ANDROID_HOME = /Users/dammya/Library/Android/sdk
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      11.0.12+0-b1504.28-7817840)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

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

[✓] Android Studio (version 2021.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      11.0.12+0-b1504.28-7817840)

[✓] IntelliJ IDEA Community Edition (version 2022.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

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

[✓] VS Code (version 1.78.0)
    • VS Code at /Users/dammya/.Trash/Visual Studio Code 20.07.05.app/Contents
    • Flutter extension version 3.50.0

[✓] Connected device (3 available)
    • Damilola’s iPhone (mobile) • 71c843fa5f3dec767999f36224653c0faa78660e •
      ios            • iOS 16.4 20E247
    • macOS (desktop)            • macos                                    •
      darwin-arm64   • macOS 13.3 22E252 darwin-arm64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 113.0.5672.92

[✓] Network resources
    • All expected network resources are available.

• No issues found!


Nullable C# types aren't always correctly mapped to Typescript

Some nullable types on the C# side aren't correctly mapped to nullable types on the Typescript side.  Examples include:

List<T>? becomes T[ ] rather than T[ ] | null
List<T?> becomes T[ ] rather than (T | null)[ ]
List<T?>? becomes T[ ] rather than (T | null)[ ] | null

I suspect this is a problem unique to IEnumerables due to how they need to end with square brackets in Typescript, opposed to any other type which can be handled "normally".
I have found a workaround for the first case, which for me was all I needed...
bool IsNullable(Property p){
    return p.Type.FullName.EndsWith("?");
}

But I'm unsure if that's as easy for the other two cases, or god forbid, lists of lists, which I bet also suffer from this.
Might look into this later if I have time.

AGHHJDSsabamhndjhkmads

Dude, there's literally a property on Typewriter.CodeModels.Type called IsNullable and it even works correctly, there is no excuse for this to not be working top-level.

hi man - it is not an excuse - I just do not have so much time as before as I am maintaining much more software that you can imagine

hi man - it is not an excuse - I just do not have so much time as before as I am maintaining much more software that you can imagine

My bad.  I could have phrased that more nicely.  Completely valid excuse too, if you don't have time, you don't have time.  I appreciate you spending any on this fork at all.
I wish I had the sort of experience you do so I could just PR a fix for this and not take up your time ._. 👉👈

Thanks Adasko.


cmd/go: 'go get -d' in a lazy module should promote transitive imports of the named package(s) to roots

(This is a pre-release cleanup needed for #36460, noticed during testing.)
In go 1.17 modules, we maintain the invariant that the modules providing all packages transitively imported by the main module are listed explicitly in its go.mod file.
go get currently adds a requirement on the module(s) providing the package(s) requested on the command line, but not their transitive imports. (This matches the behavior of go get in pre-1.17 modules.)
However, I expect that most users who run go get on a package will intend to actually import that package. If that is the case, then if they are in the default -mod=readonly mode their builds involving that package will fail until they run go mod tidy.
I would rather that go get make the requested package importable right away, with go mod tidy only needed to clean up any extraneous dependencies afterward. To make that work for go 1.17 modules, go get should be changed to add explicit requirements for all of the indirectly-imported packages too.
CC @jayconrod @matloob

@bcmills Checking in from a release meeting as this a release blocking issue,  are there updates on this? Thanks.

I'm still planning to do this. Honestly, I'm not sure that it even needs to block the beta — go get doesn't get a whole lot of user testing anyway, and following it with go mod tidy is fine as a workaround.

go get in a go 1.17 module now pulls in the transitive dependencies of its arguments, but perhaps it should also fix up the direct/indirect split as well. (Currently it marks even its arguments as indirect, which puts the new dependencies in a separate section due to #45965.) Leaving open for now while we (actively) consider what that behavior should be.

On further consideration: it's easy to promote an indirect dependency to direct, by invoking go get -d or similar on the package that imports it. So, for example:
go get -d -t ./...

will remove the // indirect markings from all dependencies that are actually direct.
On the other hand, it's difficult to demote a direct dependency to // indirect. Only go mod tidy and go mod vendor do that, and they're both rather large hammers.
So let's keep the default at // indirect, because it's not obvious that one is a better default than the other and starting as indirect is less disruptive for users to fix.

Given the above reasoning, I'm calling this issue fixed.


"Scene" is not defined

Manim sideview works well, but I can't use autocompletion, classes and functions are underlined as error

Hey,
That is because your VSCode is not configured to the python environment with manim installed. You can bring up the configuration menu by clicking the second to right-most icon with 'python' in its name.

where is the menú? i can´t see the icon with python's name

Can you please show me a screenshot of your bottom bar?


corrected Konflict to conflict

Hi Christian, there are many more typos, can you correct them and then resubmit the pull request?

Hi Adam, I corrected more typos.
Thank you,
Christian

Nice work! I'm going to close this PR so other's can complete the assignment.


Adjust layout for consistency when building visualizations

Addresses #924
The layout takes into account these notes from the 04/11/2022 UX meeting. The build progression looks as follows on a 1280x900 resolution, simulated via Firefox's dev tools:

New visualization with no selections. Of note, the VariableCoverageTable is not yet rendered.

Select x and y variables

Select an overlay

Select a facet

The UI looks pretty good, but I would suggest making the legend use the width available from its container, and remove the top/bottom margin from the right side.
Before

After

Could you talk with @moontrip if he's available and talk about widening the legend to the standard 400px width that the variable coverage table and birds eye are using?

We were having this discussion earlier with @bobular and he spoke with @danicahelb about it. She suggested we not deal with the legend width until b58. Is the final verdict to wait until b58 or to sneak it in now?

We could sneak it in if it's not likely to break anything.  The 400px wide legend with labels cut off less than half-way across will look sillier than the narrow legend IMO.  I'm just looking to see where it's done.  I don't think web-component's PlotlyPlot.tsx handles this any more.

I think we should wait. It's a minor bother to me, but it sounds like there are a host of other related issues that might arise.

I had a look at web-components' PlotLegend.tsx and I don't think we should rush this.
Ideally that component should have a width prop, from which the ellipsis threshold is calculated (I know this is not an exact science).  So let's punt on this now and save it for https://github.com/VEuPathDB/web-components/issues/344 in 58

I had a look at web-components' PlotLegend.tsx and I don't think we should rush this. Ideally that component should have a width prop, from which the ellipsis threshold is calculated (I know this is not an exact science). So let's punt on this now and save it for VEuPathDB/web-components#344 in 58

Now that this is being rendered as HTML, rather than SVG, we should be able to use the CSS text-overflow: ellipsis rule to automatically truncate based on available space, rather than truncating the text in JavaScript. This will allow things to be more responsive. I will update the issue linked above.


Sign in with Verify: Users are put off by having to remember another password

Impact: Users may abandon Verify at this point.
Evidence: “Don’t tend to remember passwords.”
“Makes me think ‘oh no, not another password’.
“Might have a go if I could remember my password – I’d hope it had a reminder.”

See also #602 #588


[BUG] animationConfig broken using reanimated v3

When using react-native-notificated with react-native-reanimated v3 (in my case ~3.3.0) when using AnimationBuilder or importing any animation config such as ZoomInDownZoomOutUp results in the below error:
ReanimatedError: Trying to access property `transitionInStyles` of an object which cannot be sent to the UI runtime., js engine: reanimated

UPDATE
After further digging I think the problem is AnimationBuilder and passing classes vs objects over to the native renanimated JS runtime - for example, if I pass an animation config object to animationConfig then it seems to work but typescript will not like the type.

Hi @erickreutz , thanks for bringing it up. I'll take a look at this bug.
Meanwhile, can you give me more details about your project package setup? I want to recreate the bug with almost the same setup as yours.  Just packages like React Native, TS, gesture handler, etc.

Sure thing! Here is the package.json of my test app that crashed.
{
  "name": "my-test-app",
  "version": "1.0.0",
  "main": "node_modules/expo/AppEntry.js",
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "web": "expo start --web"
  },
  "dependencies": {
    "expo": "~49.0.15",
    "expo-status-bar": "~1.6.0",
    "react": "18.2.0",
    "react-native": "0.72.6",
    "react-native-gesture-handler": "~2.12.0",
    "react-native-notificated": "^0.1.2",
    "react-native-reanimated": "^3.5.4"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0"
  },
  "private": true
}

Hi @erickreutz, thank you so much for your contribution to the project - the precise description helped me very much; and sorry that the fix took so long (unfortunately OSS is done in spare time ⏳). The bug is tricky; long story short: reanimated v3 checks the content of its hook useAnimationStyles - and the class can't be destructured to variables inside it. You can go ahead with our library in v0.1.4, which solves this issue.  I wish you good coding time :)


Explanation for Flowable vs Observable?

Hi There, So I was using this to create a retrofit service and I ran into this problem. I noticed that when I am using the RxJava2CallAdapter, it doesn't seem to support Flowable. For example, I tried the following:
@GET("/services/rest/?method=flickr.photos.getRecent")
    Flowable<PhotoSearchResult> getRecentPhotos(@Nullable @Query("extras") String extras,
                                            @Query("per_page") int perPage,
                                            @Query("page") int page);

That never actually triggers my onNext(), onCompleted(), etc...
Maybe I'm missing something, but ideally for a network call, I read up on RxJava2, it advises us to use something like Flowable. However, when I try Flowable, it never triggers the onNext() call in my .subscribe() function.
It will work correctly if I instead make my Service interface return an Observable. Can someone help explain this to me. I feel as if I'm totally missing something here...

There are tests for Flowable which show that it behaves the same way as Observable: https://github.com/JakeWharton/retrofit2-rxjava2-adapter/blob/master/src/test/java/com/jakewharton/retrofit2/adapter/rxjava2/FlowableTest.java. Can you express your difficulties in the form of a failing test?

So I tried the following:
@GET("/services/rest/?method=flickr.photos.getRecent")
    Maybe<PhotoSearchResult> getRecentPhotos(@Nullable @Query("extras") String extras,
                                            @Query("per_page") int perPage,
                                            @Query("page") int page);```
and then I did this and it seems to be working just fine:

@Override
public void getRecentPhotos(final @Nullable String extras, final int itemsPerPage,
final int pageNumber,
final @NonNull FetchImageListener fetchListener) {
flickrService.getRecentPhotos(extras, itemsPerPage, pageNumber)
.subscribeOn(Schedulers.io())
.observeOn(AndroidSchedulers.mainThread())
.cache()
.subscribe(new MaybeObserver() {
@Override
public void onSubscribe(Disposable s) {
Timber.i("Started flickr.photos.recent, with extras=%s, itemsPerPage=%d, pageNumber=%d", extras, itemsPerPage, pageNumber);
}
            @Override
            public void onSuccess(PhotoSearchResult photoResults) {
                fetchListener.onImagesFetchSuccess(photoResults.photoResults.photos);
            }

            @Override
            public void onError(Throwable t) {
                Timber.e(t);
                fetchListener.onImagesFetchError(t.getMessage());
            }

            @Override
            public void onComplete() {
                Timber.i("Finished flickr.photos.recent, with extras=%s, itemsPerPage=%d, pageNumber=%d", extras, itemsPerPage, pageNumber);
            }
        });
}```.

However, if I convert the above to the following:
@GET("/services/rest/?method=flickr.photos.getRecent")
    Flowable<PhotoSearchResult> getRecentPhotos(@Nullable @Query("extras") String extras,
                                            @Query("per_page") int perPage,
                                            @Query("page") int page);

, and my flowable handling to the following:
flickrService.getRecentPhotos(extras, itemsPerPage, pageNumber)
            .subscribeOn(Schedulers.io())
            .observeOn(AndroidSchedulers.mainThread())
            .subscribe(new Subscriber<PhotoSearchResult>() {
                @Override
                public void onSubscribe(Subscription s) {
                    Timber.i("Started flickr.photos.recent, with extras=%s, itemsPerPage=%d, pageNumber=%d", extras, itemsPerPage, pageNumber);
                }

                @Override
                public void onNext(PhotoSearchResult photoResults) {
                    Timber.i("Next data flickr.photos.recent, with extras=%s, itemsPerPage=%d, pageNumber=%d", extras, itemsPerPage, pageNumber);
                    fetchListener.onImagesFetchSuccess(photoResults.photoResults.photos);
                }

                @Override
                public void onError(Throwable t) {
                    Timber.e(t);
                    fetchListener.onImagesFetchError(t.getMessage());
                }

                @Override
                public void onComplete() {
                    Timber.i("Finished flickr.photos.recent, with extras=%s, itemsPerPage=%d, pageNumber=%d", extras, itemsPerPage, pageNumber);
                }
            });```
I am never able to reach my onNext(), onError(), or onComplete(). However, it enters onSubscribe() as expected.

public void onSubscribe(Subscription s) {
//add this
s.request(128);
Timber.i("Started flickr.photos.recent, with extras=%s, itemsPerPage=%d, pageNumber=%d", extras, itemsPerPage, pageNumber);
}

@zoomself . That makes sense. I was using the flowable wrong. I believe I needed to add that s.request.


Installer gives error when trying to install to a non-default location

To "Program files" for instance. It probably needs administrative rights for that.
More info and screens: 149104

looks like one can only ask for the admin permissions before starting installation. therefore we cannot try install as regular user first, then as admin. admin users should rather use the enterprise installer.


creating multisig transactions possible?

I am attempting to build a multisig transaction using libwally-swift with a p2wsh input/output but getting stuck when specifying the Witness type for my input as it seems to be limited to p2wpkh and p2sh-p2wpkh e.g. single sig types only.
Is there something I am missing? Is it just a limitation of libwally-swift at the moment that only single sig transactions can be created?
Thanks,
Fontaine

@Fonta1n3 I haven't tested this flow, because for my own purpose (unrelated to Blockchain) I rely on PSBT generated by Specter Desktop. Afaik the Blockchain wallet doesn't use PSBT at all.
I'm happy to review a change that supports it though, just make sure there's good test coverage.


Introduce BuildSrcProjectConfigurationAction

This new extension point allows any module in the classpath to
contribute configuration actions targeting specifically at the buildSrc
root project.
The motivating use-case is allowing gradle-script-kotlin to contribute
tasks and source-sets to the buildSrc project without introducing
a hard-coded dependency (see gradle/gradle-script-kotlin#230).
As a bonus, the Groovy buildSrc configuration was extracted to its own
configuration action class and moved closer to GroovyPlugin so it
could be applied by type instead of id.

Blocks gradle/gradle-script-kotlin#232.


Fix adding or editing person with student id or email that exists in list

I'm not too sure what the PR title is about. What is the (previously) incorrect behaviour that this PR is trying to fix? What should the correct behaviour be?

In the previous version, if Person with StudentId A0123456X and Email<EMAIL_ADDRESS>is in the list, it is possible to add a Person with the same StudentId A0123456X and different Email<EMAIL_ADDRESS>The current version will not allow adding or editing to a Person with StudentId or Email that is already in the list, not necessarily both.


hipFreeAsync hangs

Hi, I'm experiencing hangs with hipFreeAsync and was wondering what could potentially cause that.
From my perspective it looks like some kind of racing condition.
It consistently happens at the end of the test suite when we start to release memory of the device arrays used in the process in AMDGPU.jl which provides AMD GPU programming interface in Julia language.
Just to note, that memory free happens a lot during tests, it just that it hangs at the end.
I made sure that we do not destroy streams or respective context.
Also, freeing arrays uses NULL stream, but for other operations we use other streams.
I started seeing this issues with ROCm 5.6-5.7.1 and using RX7900XT.
Here's gdb output of the process when it hangs:

On ROCm 5.4 it was not observed and the whole test suite ran fine.
If you need any additional info, I'm happy to provide.

I also ran tests using debug Julia & HIP build and besides hitting this assert (which I commented out) there were no other issues.

Hi @pxl-th can you please attach a reproducer for the issue. Can you reproduce the hang in C++ as well?

Unfortunately, I was unable to create a MWE as it is unclear to me what causes it.
Running the tests one-by-one does not reproduce it, only when running them all.
I tried running them on multiple workers and on just a single thread and in all cases it hangs.
But the place where it hangs might change from run to run.
When running tests I get a lot of page faults in dmesg as described here.
Although I'm not sure if this is critical enough to cause hangs.
Also, reproducing the tests with C++ is not easy, because we have almost 13k tests.
So the best I can suggest is to try running AMDGPU tests yourself, which is quite easy:

Download & unpack Julia 1.10: https://julialang-s3.julialang.org/bin/linux/x64/1.10/julia-1.10.0-rc1-linux-x86_64.tar.gz
Launch Julia REPL with <julia-dir>/bin/julia --threads=auto
Enter package mode with ] key
Add AMDGPU.jl package: add AMDGPU#master
Run AMDGPU tests with test AMDGPU

At some point, test workers will become idle and inspecting them with gdb will show this hang.
I'm also not sure if this is an issue with Julia or AMDGPU.jl package, we've been successfully running CI on RX6700XT for several months now without issues using ROCm 5.4 - 5.6 and tried other GPUs like MI200 without these issues.

Also, on Windows there are no issues at all with RX7900XT, it passes all AMDGPU.jl tests without hanging.

@iassiour, not sure if this is expected, but I noticed that async malloc/free vs non-async is ~300x slower.
MWE (allocates in total ~400 KiB across 100k iterations):
#include <hip/hip_runtime.h>
#include <iostream>

using namespace std;

void check(int res) {
    if (res != 0) {
        std::cerr << "Fail" << std::endl;
    }
}

int main(int argc, char* argv[]) {
    hipStream_t s;
    check(hipStreamCreateWithPriority(&s, 0, 0));

    /*
    std::cout << "Regular" << std::endl;
    for (int i = 1; i < 100000; i++) {
        float *x;
        check(hipMalloc((void**)&x, 4));
        check(hipFree(x));
    }
    */

    std::cout << "Async" << std::endl;
    for (int i = 1; i < 100000; i++) {
        float *x;
        check(hipMallocAsync((void**)&x, 4, s));
        check(hipFreeAsync(x, s));
    }

    return 0;
}

pxl-th@Leleka:~/code$ time ./a.out
Regular

real	0m0,256s
user	0m0,206s
sys	0m0,033s

pxl-th@Leleka:~/code$ time ./a.out
Async

real	1m15,237s
user	1m47,751s
sys	0m0,828s

Hi @pxl-th I think the slowness in async malloc/free is caused by a bug triggered by small (<8 byte) allocations.
I will create a PR internally to fix this. Thank you for reporting this.

Hi @pxl-th the fix for < 8-byte allocations has been merged in develop https://github.com/ROCm/clr/commit/2ede1c9adb76e04627fea8126f9cea9c03740574  and it should appear in future release.
Regarding the 16-byte allocations timing test:
There is an extra bookkeeping overhead associated with the memory pool APIs. While this overhead is quite small, the small memory allocations are also generally fast. In addition, this latency can be hidden if the application takes full advantage of the async API. In this particular example there is no computation done to overlap with the allocation overhead and hence the latency is not hidden.
Additionally please note that this API is currently in Beta state so it is subject to ongoing changes which might improve/impact the performance as we polish our implementation.
Regarding the hang in hipFreeAsync mentioned in the original post, I could not immediately reproduce the issue with 5.7.1 ubuntu 22.04 but with a RX7900XTX. Is there a specific subtest that the workers become idle or it happens in the end of the process? If possible can please attach the logs up to the hanging point.

Thank you for the fix!
Regarding hipFreeAsync and hangs, I recently upgraded to ROCm 6 and when running AMDGPU.jl tests it reported some page faults (and errored instead of hanged), so I was able to fix those (rocBLAS related).
Now I'm able to successfully run the test suite, however, it still hangs randomly when running tests and doing some graphics stuff at the same time.
Here's the hang from yesterday CI run: link.
I was screencasting at the same time as running tests, but just re-running tests without it worked fine (see CI run just below the failed one).
I still see some page-faults occasionally as described here, but I'm not sure if they are related to hangs.

Is there a specific subtest that the workers become idle or it happens in the end of the process?

Usually it hangs at some internal synchronization point.
gdb backtrace is either the same as in the original post or similar but in hipMemcpyDtoH waiting for all streams.
So besides suggesting to run the tests and do some graphics related stuff at the same time I'm not sure how else to reproduce it... But at least now CI passes with Navi 3, so that's an improvement :)
We still have some tests that fail on Navi 3, so I'll investigate those and update here if they are related.

Find the smallest test case, and dump the AMD_LOG_LEVEL=4 for it.

There are tests that reliably trigger the hang.
In Julia we use Task-Local State (TLS) as opposed to Thread-Local State.
And each Task in Julia has its own HIP stream, that's how users are advised to use multiple gpus at the same time.
For this we have tests that check that TLS is working properly, where we create streams with different priorities and check that TLS is updated accordingly (that are then destroyed one GC collects them).
When running these tests (among other tests) with 2+ workers it causes the hang.
By default those tests are disabled for Navi 3, so I've uncommented them inpxl-th/tls branch for AMDGPU.jl.
Just in case, AMDGPU.jl for this branch can be installed with ]add AMDGPU#pxl-th/tls command.

AMD_LOG_LEVEL=4 logs: logs.txt
gdb on the hanged process (I'm currenlty using release build, but it can be roughly inferred to the internal synchronization caused by hipFree):

Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
0x00007f2cf0708c9b in sched_yield () at ../sysdeps/unix/syscall-template.S:120
120	../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) bt
#0  0x00007f2cf0708c9b in sched_yield () at ../sysdeps/unix/syscall-template.S:120
#1  0x00007f2c8b0fe9e5 in ?? () from /opt/rocm-6.0.0/lib/libamdhip64.so
#2  0x00007f2c8b102d42 in ?? () from /opt/rocm-6.0.0/lib/libamdhip64.so
#3  0x00007f2c8b0447fe in ?? () from /opt/rocm-6.0.0/lib/libamdhip64.so
#4  0x00007f2c8af5f52c in ?? () from /opt/rocm-6.0.0/lib/libamdhip64.so
#5  0x00007f2c8af659c3 in hipFree () from /opt/rocm-6.0.0/lib/libamdhip64.so
#6  0x00007f2cef3f05f0 in ?? ()
#7  0x0000000000000004 in ?? ()
#8  0x00007f2c973fe620 in ?? ()
#9  0x00007f2b28f80110 in ?? ()
#10 0x00007f2c973fe600 in ?? ()
#11 0x00007f2cef3407e0 in ?? ()
#12 0x00007f2b28f80450 in ?? ()
#13 0x00007f2c973fe710 in ?? ()
#14 0x00007f2cef3f09d7 in ?? ()
#15 0x0000002000000202 in ?? ()
#16 0x000000200000010f in ?? ()
#17 0x00007f2c90f7e1f0 in ?? ()
#18 0x0000000000000003 in ?? ()
#19 0x0000000000000010 in ?? ()
#20 0x00007f2c973fe740 in ?? ()
#21 0x00007f2ce54990c0 in ?? ()
#22 0x00007f2ce54990c0 in ?? ()
#23 0x00007f2ce54990c0 in ?? ()
#24 0x00007f2b28f80450 in ?? ()
#25 0x0000000000000000 in ?? ()
(gdb)

dmesg at the time of hang:

[16837.325405] amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:153 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[16837.325418] amdgpu 0000:2f:00.0: amdgpu:   in page starting at address 0x0000000000001000 from client 10
[16837.325424] amdgpu 0000:2f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000B32
[16837.325428] amdgpu 0000:2f:00.0: amdgpu: 	Faulty UTCL2 client ID: CPC (0x5)
[16837.325432] amdgpu 0000:2f:00.0: amdgpu: 	MORE_FAULTS: 0x0
[16837.325435] amdgpu 0000:2f:00.0: amdgpu: 	WALKER_ERROR: 0x1
[16837.325439] amdgpu 0000:2f:00.0: amdgpu: 	PERMISSION_FAULTS: 0x3
[16837.325442] amdgpu 0000:2f:00.0: amdgpu: 	MAPPING_ERROR: 0x1
[16837.325445] amdgpu 0000:2f:00.0: amdgpu: 	RW: 0x0
[16882.774186] amdgpu 0000:2f:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001c address=0xdb1b2000 flags=0x0020]
[16882.880711] gmc_v11_0_process_interrupt: 4 callbacks suppressed
[16882.880716] amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:153 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[16882.880721] amdgpu 0000:2f:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001c address=0xdb1b2000 flags=0x0000]
[16882.880728] amdgpu 0000:2f:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
[16882.880733] amdgpu 0000:2f:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001c address=0xdb1b2000 flags=0x0020]
[16882.880734] amdgpu 0000:2f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000B32
[16882.880737] amdgpu 0000:2f:00.0: amdgpu: 	Faulty UTCL2 client ID: CPC (0x5)
[16882.880741] amdgpu 0000:2f:00.0: amdgpu: 	MORE_FAULTS: 0x0
[16882.880744] amdgpu 0000:2f:00.0: amdgpu: 	WALKER_ERROR: 0x1
[16882.880748] amdgpu 0000:2f:00.0: amdgpu: 	PERMISSION_FAULTS: 0x3
[16882.880751] amdgpu 0000:2f:00.0: amdgpu: 	MAPPING_ERROR: 0x1
[16882.880754] amdgpu 0000:2f:00.0: amdgpu: 	RW: 0x0
[16882.907117] amdgpu 0000:2f:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001c address=0xdb1b2000 flags=0x0020]
[16894.050735] amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:153 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[16894.050740] amdgpu 0000:2f:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001c address=0xdb1b2000 flags=0x0000]
[16894.050748] amdgpu 0000:2f:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
[16894.050754] amdgpu 0000:2f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000B32
[16894.050758] amdgpu 0000:2f:00.0: amdgpu: 	Faulty UTCL2 client ID: CPC (0x5)
[16894.050763] amdgpu 0000:2f:00.0: amdgpu: 	MORE_FAULTS: 0x0
[16894.050766] amdgpu 0000:2f:00.0: amdgpu: 	WALKER_ERROR: 0x1
[16894.050770] amdgpu 0000:2f:00.0: amdgpu: 	PERMISSION_FAULTS: 0x3
[16894.050771] amdgpu 0000:2f:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001c address=0xdb1b2000 flags=0x0020]
[16894.050775] amdgpu 0000:2f:00.0: amdgpu: 	MAPPING_ERROR: 0x1
[16894.050778] amdgpu 0000:2f:00.0: amdgpu: 	RW: 0x0
[16902.616293] amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:153 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[16902.616299] amdgpu 0000:2f:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
[16902.616302] amdgpu 0000:2f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000B32
[16902.616304] amdgpu 0000:2f:00.0: amdgpu: 	Faulty UTCL2 client ID: CPC (0x5)
[16902.616306] amdgpu 0000:2f:00.0: amdgpu: 	MORE_FAULTS: 0x0
[16902.616307] amdgpu 0000:2f:00.0: amdgpu: 	WALKER_ERROR: 0x1
[16902.616309] amdgpu 0000:2f:00.0: amdgpu: 	PERMISSION_FAULTS: 0x3
[16902.616310] amdgpu 0000:2f:00.0: amdgpu: 	MAPPING_ERROR: 0x1
[16902.616312] amdgpu 0000:2f:00.0: amdgpu: 	RW: 0x0
[16902.616313] amdgpu 0000:2f:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001c address=0xdb1b2000 flags=0x0000]
[16902.631525] amdgpu 0000:2f:00.0: amdgpu: [gfxhub] page fault (src_id:0 ring:153 vmid:0 pasid:0, for process  pid 0 thread  pid 0)
[16902.631530] amdgpu 0000:2f:00.0: amdgpu:   in page starting at address 0x0000000000000000 from client 10
[16902.631533] amdgpu 0000:2f:00.0: amdgpu: GCVM_L2_PROTECTION_FAULT_STATUS:0x00000B32
[16902.631534] amdgpu 0000:2f:00.0: amdgpu: 	Faulty UTCL2 client ID: CPC (0x5)
[16902.631536] amdgpu 0000:2f:00.0: amdgpu: 	MORE_FAULTS: 0x0
[16902.631538] amdgpu 0000:2f:00.0: amdgpu: 	WALKER_ERROR: 0x1
[16902.631539] amdgpu 0000:2f:00.0: amdgpu: 	PERMISSION_FAULTS: 0x3
[16902.631541] amdgpu 0000:2f:00.0: amdgpu: 	MAPPING_ERROR: 0x1
[16902.631542] amdgpu 0000:2f:00.0: amdgpu: 	RW: 0x0
[16902.631543] amdgpu 0000:2f:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x001c address=0xdb1b2000 flags=0x0000]

Reviving this as I have a faily small MWE that consistently reproduces the issue.
On ROCm 6.0.2 and RX7900 XTX.
Again in Julia as it is much easier to set up the code.
MWE:
using AMDGPU
function main()
    data = rand(Float64, 1024, 1024)
    Threads.@threads for i in 1:1000
        sum(ROCArray(data))
    end
end
main()

starts multiple threads (2 is enough but more threads trigger this more reliably)
in each thread copies the data from the host to the device (hipMallocAsync, hipMemcpyHtoDAsync)
computes the sum of the array (hipModuleLaunchKernel)
frees the arrays (hipFreeAsync)

And at some point during execution it hangs.
Output of kill -USR1 PID for each Julia thread (two of them).
Notice that one thread hangs at hipModuleLaunchKernel and another at hipFreeAsync.
This is with debug HIP build.
cmd: /home/pxl-th/bin/julia-1.10.1/bin/julia 55042 running 2 of 2

# Thread 1

unknown function (ip: 0x7f8322c91115)
unknown function (ip: 0x7f8322c9cc77)
wait at /home/pxl-th/code/clr/rocclr/thread/semaphore.cpp:96
finishLock at /home/pxl-th/code/clr/rocclr/thread/monitor.cpp:121
lock at /home/pxl-th/code/clr/rocclr/thread/monitor.hpp:207
ScopedLock at /home/pxl-th/code/clr/rocclr/thread/monitor.hpp:163
isValid at /home/pxl-th/code/clr/hipamd/src/hip_stream.cpp:98
hipModuleLaunchKernel at /home/pxl-th/code/clr/hipamd/src/hip_module.cpp:440
macro expansion at /home/pxl-th/.julia/dev/AMDGPU/src/hip/call.jl:38 [inlined]
hipModuleLaunchKernel at /home/pxl-th/.julia/dev/AMDGPU/src/hip/libhip.jl:282
#24 at /home/pxl-th/.julia/dev/AMDGPU/src/runtime/hip-execution.jl:123 [inlined]
macro expansion at /home/pxl-th/.julia/dev/AMDGPU/src/runtime/hip-execution.jl:110 [inlined]
macro expansion at ./none:0 [inlined]
pack_arguments at ./none:0
#launch#23 at /home/pxl-th/.julia/dev/AMDGPU/src/runtime/hip-execution.jl:122 [inlined]
launch at /home/pxl-th/.julia/dev/AMDGPU/src/runtime/hip-execution.jl:116 [inlined]
#18 at /home/pxl-th/.julia/dev/AMDGPU/src/runtime/hip-execution.jl:85 [inlined]
macro expansion at /home/pxl-th/.julia/dev/AMDGPU/src/runtime/hip-execution.jl:78 [inlined]
macro expansion at ./none:0 [inlined]
convert_arguments at ./none:0 [inlined]
#roccall#17 at /home/pxl-th/.julia/dev/AMDGPU/src/runtime/hip-execution.jl:86 [inlined]
roccall at /home/pxl-th/.julia/dev/AMDGPU/src/runtime/hip-execution.jl:84 [inlined]
macro expansion at /home/pxl-th/.julia/dev/AMDGPU/src/runtime/hip-execution.jl:50 [inlined]
macro expansion at ./none:0 [inlined]
#call#1 at ./none:0
unknown function (ip: 0x7f83219799ed)
_jl_invoke at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/gf.c:3076
call at ./none:0 [inlined]
#_#15 at /home/pxl-th/.julia/dev/AMDGPU/src/runtime/hip-execution.jl:59
HIPKernel at /home/pxl-th/.julia/dev/AMDGPU/src/runtime/hip-execution.jl:54
unknown function (ip: 0x7f8321979415)
_jl_invoke at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/gf.c:3076
macro expansion at /home/pxl-th/.julia/dev/AMDGPU/src/highlevel.jl:175 [inlined]
#mapreducedim!#59 at /home/pxl-th/.julia/dev/AMDGPU/src/kernels/mapreduce.jl:155
mapreducedim! at /home/pxl-th/.julia/dev/AMDGPU/src/kernels/mapreduce.jl:86
unknown function (ip: 0x7f8321977230)
#mapreducedim!#59 at /home/pxl-th/.julia/dev/AMDGPU/src/kernels/mapreduce.jl:167
mapreducedim! at /home/pxl-th/.julia/dev/AMDGPU/src/kernels/mapreduce.jl:86 [inlined]
#mapreducedim!#59 at /home/pxl-th/.julia/dev/AMDGPU/src/kernels/mapreduce.jl:167
mapreducedim! at /home/pxl-th/.julia/dev/AMDGPU/src/kernels/mapreduce.jl:86 [inlined]
#_mapreduce#43 at /home/pxl-th/.julia/packages/GPUArrays/Hd5Sk/src/host/mapreduce.jl:67
_mapreduce at /home/pxl-th/.julia/packages/GPUArrays/Hd5Sk/src/host/mapreduce.jl:33 [inlined]
#mapreduce#41 at /home/pxl-th/.julia/packages/GPUArrays/Hd5Sk/src/host/mapreduce.jl:28 [inlined]
mapreduce at /home/pxl-th/.julia/packages/GPUArrays/Hd5Sk/src/host/mapreduce.jl:28 [inlined]
#_sum#831 at ./reducedim.jl:1015 [inlined]
_sum at ./reducedim.jl:1015 [inlined]
#_sum#830 at ./reducedim.jl:1014 [inlined]
_sum at ./reducedim.jl:1014 [inlined]
#sum#828 at ./reducedim.jl:1010 [inlined]
sum at ./reducedim.jl:1010 [inlined]
macro expansion at /home/pxl-th/.julia/dev/t.jl:26 [inlined]
#39#threadsfor_fun#7 at ./threadingconstructs.jl:215
#39#threadsfor_fun at ./threadingconstructs.jl:182 [inlined]
#1 at ./threadingconstructs.jl:154
unknown function (ip: 0x7f83218af892)
_jl_invoke at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/gf.c:3076
jl_apply at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/julia.h:1982 [inlined]
start_task at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/task.c:1238
unknown function (ip: (nil))

# Thread 2

unknown function (ip: 0x7f8322c91115)
unknown function (ip: 0x7f8322c9cc77)
wait at /home/pxl-th/code/clr/rocclr/thread/semaphore.cpp:96
finishLock at /home/pxl-th/code/clr/rocclr/thread/monitor.cpp:121
lock at /home/pxl-th/code/clr/rocclr/thread/monitor.hpp:207
ScopedLock at /home/pxl-th/code/clr/rocclr/thread/monitor.hpp:163
FreeMemory at /home/pxl-th/code/clr/hipamd/src/hip_device.cpp:90
submit at /home/pxl-th/code/clr/hipamd/src/hip_mempool.cpp:112
enqueue at /home/pxl-th/code/clr/rocclr/platform/command.cpp:391
hipFreeAsync at /home/pxl-th/code/clr/hipamd/src/hip_mempool.cpp:137
macro expansion at /home/pxl-th/.julia/dev/AMDGPU/src/hip/call.jl:38 [inlined]
hipFreeAsync at /home/pxl-th/.julia/dev/AMDGPU/src/hip/libhip.jl:174 [inlined]
#free#9 at /home/pxl-th/.julia/dev/AMDGPU/src/runtime/memory/hip.jl:134
free at /home/pxl-th/.julia/dev/AMDGPU/src/runtime/memory/hip.jl:129 [inlined]
#43 at /home/pxl-th/.julia/dev/AMDGPU/src/array.jl:30 [inlined]
context! at /home/pxl-th/.julia/dev/AMDGPU/src/tls.jl:131
_free_buf at /home/pxl-th/.julia/dev/AMDGPU/src/array.jl:28
unknown function (ip: 0x7f83219788cc)
_jl_invoke at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/gf.c:3076
release at /home/pxl-th/.julia/packages/GPUArrays/Hd5Sk/src/host/abstractarray.jl:42
unsafe_free! at /home/pxl-th/.julia/packages/GPUArrays/Hd5Sk/src/host/abstractarray.jl:91 [inlined]
unsafe_free! at /home/pxl-th/.julia/dev/AMDGPU/src/array.jl:34 [inlined]
#mapreducedim!#59 at /home/pxl-th/.julia/dev/AMDGPU/src/kernels/mapreduce.jl:168
mapreducedim! at /home/pxl-th/.julia/dev/AMDGPU/src/kernels/mapreduce.jl:86 [inlined]
#mapreducedim!#59 at /home/pxl-th/.julia/dev/AMDGPU/src/kernels/mapreduce.jl:167
mapreducedim! at /home/pxl-th/.julia/dev/AMDGPU/src/kernels/mapreduce.jl:86 [inlined]
#_mapreduce#43 at /home/pxl-th/.julia/packages/GPUArrays/Hd5Sk/src/host/mapreduce.jl:67
_mapreduce at /home/pxl-th/.julia/packages/GPUArrays/Hd5Sk/src/host/mapreduce.jl:33 [inlined]
#mapreduce#41 at /home/pxl-th/.julia/packages/GPUArrays/Hd5Sk/src/host/mapreduce.jl:28 [inlined]
mapreduce at /home/pxl-th/.julia/packages/GPUArrays/Hd5Sk/src/host/mapreduce.jl:28 [inlined]
#_sum#831 at ./reducedim.jl:1015 [inlined]
_sum at ./reducedim.jl:1015 [inlined]
#_sum#830 at ./reducedim.jl:1014 [inlined]
_sum at ./reducedim.jl:1014 [inlined]
#sum#828 at ./reducedim.jl:1010 [inlined]
sum at ./reducedim.jl:1010 [inlined]
macro expansion at /home/pxl-th/.julia/dev/t.jl:26 [inlined]
#39#threadsfor_fun#7 at ./threadingconstructs.jl:215
#39#threadsfor_fun at ./threadingconstructs.jl:182 [inlined]
#1 at ./threadingconstructs.jl:154
unknown function (ip: 0x7f83218af892)
_jl_invoke at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/gf.c:2894 [inlined]
ijl_apply_generic at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/gf.c:3076
jl_apply at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/julia.h:1982 [inlined]
start_task at /cache/build/default-maughin-0/julialang/julia-release-1-dot-10/src/task.c:1238
unknown function (ip: (nil))

Output of gdb -p PID for one thread:
(gdb) bt
#0  __futex_abstimed_wait_common64 (private=<optimized out>, cancel=true, abstime=0x0, op=393, expected=0, futex_word=0xde5448)
    at ./nptl/futex-internal.c:57
#1  __futex_abstimed_wait_common (cancel=true, private=<optimized out>, abstime=0x0, clockid=0, expected=0, futex_word=0xde5448)
    at ./nptl/futex-internal.c:87
#2  __GI___futex_abstimed_wait_cancelable64 (futex_word=futex_word@entry=0xde5448, expected=expected@entry=0,
    clockid=clockid@entry=0, abstime=abstime@entry=0x0, private=<optimized out>) at ./nptl/futex-internal.c:139
#3  0x00007ff13e29cbdf in do_futex_wait (sem=sem@entry=0xde5448, abstime=0x0, clockid=0) at ./nptl/sem_waitcommon.c:111
#4  0x00007ff13e29cc78 in __new_sem_wait_slow64 (sem=0xde5448, abstime=0x0, clockid=0) at ./nptl/sem_waitcommon.c:183
#5  0x00007ff06957fffe in amd::Semaphore::wait (this=0xde5440) at /home/pxl-th/code/clr/rocclr/thread/semaphore.cpp:96
#6  0x00007ff06957f43d in amd::Monitor::finishLock (this=0x7ff06ab140c0 <streamSetLock>)
    at /home/pxl-th/code/clr/rocclr/thread/monitor.cpp:121
#7  0x00007ff069243506 in amd::Monitor::lock (this=0x7ff06ab140c0 <streamSetLock>)
    at /home/pxl-th/code/clr/rocclr/thread/monitor.hpp:207
#8  0x00007ff069243318 in amd::ScopedLock::ScopedLock (this=0x7fef5d5fd810, lock=...)
    at /home/pxl-th/code/clr/rocclr/thread/monitor.hpp:163
#9  0x00007ff06945d5cc in iHipWaitActiveStreams (blocking_stream=0x1885a00, wait_null_stream=true)
    at /home/pxl-th/code/clr/hipamd/src/hip_stream.cpp:204
#10 0x00007ff069251f31 in hip::getStream (stream=0x1885a00, wait=true) at /home/pxl-th/code/clr/hipamd/src/hip_context.cpp:99
#11 0x00007ff069293448 in hip::Event::addMarker (this=0x19ae190, stream=0x1885a00, command=0x0, record=true)
    at /home/pxl-th/code/clr/hipamd/src/hip_event.cpp:251
#12 0x00007ff0693fc532 in hip::MemoryPool::FreeMemory (this=0x15acb70, memory=0x1c6da90, stream=0x1885a00)
    at /home/pxl-th/code/clr/hipamd/src/hip_mempool_impl.cpp:249
#13 0x00007ff06927f94f in hip::Device::FreeMemory (this=0xef7400, memory=0x1c6da90, stream=0x1885a00)
    at /home/pxl-th/code/clr/hipamd/src/hip_device.cpp:93
#14 0x00007ff0693f8792 in FreeAsyncCommand::submit (this=0x1c6e860, device=...)
    at /home/pxl-th/code/clr/hipamd/src/hip_mempool.cpp:112
#15 0x00007ff069546692 in amd::Command::enqueue (this=0x1c6e860) at /home/pxl-th/code/clr/rocclr/platform/command.cpp:391
#16 0x00007ff0693e9dd0 in hipFreeAsync (dev_ptr=0x7fef3c220000, stream=0x1885a00)
    at /home/pxl-th/code/clr/hipamd/src/hip_mempool.cpp:137
#17 0x00007ff13cfe8cd3 in ?? ()
#18 0x000000000000000c in ?? ()

CC @saleelk @iassiour

Mixing default and non-default streams in hip*Async functions seems to cause hangs.
Here's C++ reproducer:
#include <hip/hip_runtime.h>
#include <iostream>
#include <thread>

__global__
void vectorAdd(int *a, int *b, int numElements) {
    int i = hipBlockIdx_x * hipBlockDim_x + hipThreadIdx_x;
    if (i < numElements)
        b[i] += a[i];
}

void fn() {
    hipStream_t stream;
    hipStreamCreate(&stream);

    int n_elements = 1024 * 1024;
    int size = n_elements * sizeof(int);

    int *a = new int[n_elements];
    int *b = new int[n_elements];
    for (int i = 0; i < n_elements; ++i) {
        a[i] = 1;
        b[i] = 1;
    }

    int *da, *db;
    hipMallocAsync(&da, size, stream);
    hipMallocAsync(&db, size, stream);

    hipMemcpyHtoDAsync(da, a, size, stream);
    hipMemcpyHtoDAsync(db, a, size, stream);

    hipLaunchKernelGGL(
        vectorAdd, dim3((n_elements + 255) / 256), dim3(256),
        0, stream, da, db, n_elements);

    /* hipFreeAsync(da, stream); */
    hipFreeAsync(da, nullptr); // <--- Mixing default stream with non-default causes hangs!
    hipFreeAsync(db, stream);

    hipStreamDestroy(stream);

    delete[] a;
    delete[] b;
}

void thread_fn() {
    for (int i = 0; i < 1000; i++) {
        fn();
    }
}

int main() {
    std::thread t1(thread_fn);
    std::thread t2(thread_fn);
    std::thread t3(thread_fn);
    std::thread t4(thread_fn);

    t1.join();
    t2.join();
    t3.join();
    t4.join();
    return 0;
}

Kind ping, to see if someone can take a look at the issue.

Testing on ROCm 6.1 with RX 7800 XT, the Julia MWE does no longer hang. However, the C++ reproducer cannot complete.

This might be related to this issue: https://github.com/ROCm/hipFFT/issues/91

@torrance thanks for the update! This should significantly help with CI in AMDGPU.jl

Indeed - thanks!

@luraess It's fixed in future release of ROCm 6.1.2 Thanks!

Hi @pxl-th,
I tested the C++ reproducer code on the latest version of ROCm (6.2.2) and can confirm that the issue appears to be fixed. Please give it a try on the latest version and let me know if the issue persists. Thanks!