Ignition | neat micro CMS in under 300kb of PHP | Content Management System library

I just wanted to use Mailgun to send E-mail from my Laravel project and followed this steps from official document: https://laravel.com/docs/9.x/mail#mailgun-driver

composer require symfony/mailgun-mailer symfony/http-client

When I try to send password reset e-mail to test it, it throws an excepiton:

Class "Symfony\Component\Mailer\Bridge\Mailgun\Transport\MailgunTransportFactory" not found

Here is the full stack trace: https://flareapp.io/share/oPRKqyZ7#share

I don't know but maybe it's because this project started as a Laravel 8 project and I updated it to Laravel 9 one week ago. Is it trying to find something comes with Laravel 9 into app directory or something but my project doesn't have that? I didn't understand.

By the way if it helps; this project uses Jetstream with Inertia.js and Vue.js. So the composer.json looks like this now:

Apache ignite .net core server node fails to start with the below error, any idea what could be the reason?

I'm using Spring and Ignite Spring to run a pretty simple cluster consisting of one server node and multiple client nodes with varying domain logic.

Ignite configuration:

• All nodes connect via TcpCommuncationSpi, TcpDiscoverySpi and TcpDiscoveryVmIpFinder. TcpDiscoveryVmIpFinder.setAddresses only contain the server node.
• The server node has serveral CacheJdbcPojoStore configured, the database data is loaded after calling Ignition.start(cfg) using ignite.cache("mycachename").loadCache(null).

After a client node is connected to the server node, it does some domain specific checks to verify data integrity. This works very well if I first start the server node, wait for all data to be loaded and then start the client nodes.

My problem: if I first start the client nodes, they can't connect to the server node as it is not yet started. They patiently wait for the server node to come up. If I now start the server node, the client nodes connect directly after Ignition.start(cfg) is done on the server node, but BEFORE the CacheJdbcPojoStores are done loading their data. Thus the domain specific integrity checks do fail as there is no data present in the caches yet.

My goal: I need a way to ensure the client nodes are only able to connect to the server node AFTER all data is loaded in the server node. This would simply the deployment process as well as local development a lot, as there would be no strict ordering of starting the nodes.

What I tried so far: Fiddling around with ignite.cluster().state(ClusterState.INACTIVE) as well as setting up a manually controlled BaselineTopology. Sadly, both methods simple declare the cluster as not being ready yet and thus I can't even create the caches, let alone load data.

My question: Is there any way to achieve either:

1. hook up into the the startup process of the server node so I can load the data in BEFORE it joins the cluster
2. Declare the server node "not yet ready" until the data is loaded.

When I run any PHP artisant command I got this Error

I try to upgrade my laravel 8 as I read here https://laravel.com/docs/9.x/upgrade

But after I applyid some changes in composer.json I got error :

I try to remove some data using the thin client data streamer (.NET apache ignite) but i end up with an exception:

DataStreamer can't remove data when AllowOverwrite is false.

My problem is when i try to change AllowOverwrite to true it is not respected.

I'm using Apache.Ignite NET 2.12.0.

I tried several approaches to allow two Ignite clusters to be run separately on the machine:

1. Approach described here. I specified DiscoverySPI and CommunicationSPI port for each instance of server(I use client-server model) to isolate them, but the server failed to run with this warning:

[05:03:01,968][WARNING][main][TcpDiscoverySpi] Failed to connect to any address from IP finder (make sure IP finder addresses are correct and firewalls are disabled on all host machines): [/127.0.0.1:47501, /127.0.0.1:47502]

In that case, the execution enters Ignition.Start and don't leave it.

1. I tried to provide IgniteConfiguration.SslContextFactory with different certificates to avoid the different clusters seeing each other, but in that case - they see each other, but the clusters fail to join each other, which prevents them from working.

Is there some easy way to do this?

AFAIK, there are roughly two kinds of code objects in V8. One is javascript bytecode interpreted by Ignition, and the other is machine code which is compiled & optimized by Turbofan. According to the execution/frames.h, V8 constructs a different stackframe for each kind of code object. It means V8 should know the kind of the callee before it executes.

When unoptimized code(JS Bytecode) calls the optimized one, I guess that Ignition could handle the case properly to build a new stackframe for an optimized one. However, when the optimized code(machine code) calls the unoptimized one, I'm curious about how V8 determines whether callee is unoptimized or not. If the machine code is run directly on the processor, nothing can help V8 determine the kind of callee.

Also, in my understanding, V8 should detect whether some code dependency is compromised to mark or deoptimize the invalidated code objects. It also seems infeasible if V8 doesn't monitor the execution of machine code.

So my question is:

1. Does V8 monitor the execution of (optimized) machine code? If so, how does it happen?

2. If 1 is false, then how does V8 check the invalidation of code dependency or detect whether the callee is compiled or not?

I have a Java server technology (Ignition by Inductive Automation specifically) that calls a batch file that is meant to use WinSCP to transfer some text files overnight to our customer. It is not working and I am not sure why.

Here is the batch file – actual information has been changed so any typos are not representative of actual batch file. Note that