Support configuration changes

Implement cluster configuration changes, i.e. adding and removing servers.

Defined in the Raft paper chapter 6.


KeyCharPrimitive() loses window scroll position

In any game (but for instance my first game http://iplayif.com/?story=http://hlabrande.fr/if/games/espions.z5), when KeyCharPrimitive (in I6) or "wait for any key" (in I7) is used, Parchment loses the position to where the window had been scrolled and send you back to the beginning, instead of staying around the same position.
If a game has a ton of text then a "press any key" and no "clearscreen" instruction, you have to scroll again all the way down to go back to where you were. If the game uses this effect a lot, for example to pace cutscenes, you have to scroll down dozens of time and it's really annoying, borderline unplayable.
(This shows up in games in French, more than in games in English, because the francophone scene uses this effect a lot historically.)
Parchment could either stay at the same position and have the player scroll down a bit to see the text that just popped up, or scroll down automatically as desktop interpreters do.
Thanks! :)

I think this is fixed now. Let me know if you have more troubles.


netstandard2.0;net4xx support possible?

Hi,
Is there some technical reason why all these tasks are net6.0 only? If you could add at least .netstandard2.0 support it would make the migration from old tasks to these the much easier. Of course if possible add net4 Framework support too.

Hello, these are tasks specifically created for newer Frends versions. There are no plans to make this net standard 2.0 compatible or framework compatible.
For .NET Standard 2.0 and Framework 4.7.1 tasks use Frends.File tasks here - https://github.com/FrendsPlatform/Frends.File.


searching nintendo does not bring up all results

Searching for "nintendo" does not bring up lbry://re2-lA-q8DMm5r8#8e1e8b42451a0c0dc3db4e8b4f645f2ad802e665 which has "Nintendo Hardware and Revisitation - Rerez Talks" as the title.

Will take a look at this as soon as possible,
Dev instance i have seems to return different results will take a look at implementation.

This has been corrected with the latest release of chain query
The following search will return it as the #1 result.
https://lighthouse.lbry.io/search?s=Nintendo Hardware and Revisitation


HTTP import log file not working with special characters

When using special characters in a password in the form of:
<EMAIL_ADDRESS>It cannot be handled and a vfs2.FileSystemException is trown saying: Port number is missing from URI

Apache VFS2 is not able to parse URL. You can try to escape special characters:
<EMAIL_ADDRESS>
Are you asked about user/password if you try to open?
http(s)://server.com/logs/debug.log
<EMAIL_ADDRESS>

I'll try masking the special characters but I'm not asked for any password at all.


[Feature] Number of moles of substance & number of electron , proton and neutron calculator.

Description

Input: The user inputs the mass of the substance and its molar mass (in grams per mole).

Calculate Moles: The calculator calculates the number of moles of the substance.

Calculate Number of Electrons, Protons, and Neutrons: This part depends on the substance. If the substance is an atom (not an ion), you can determine the number of electrons, protons, and neutrons based on its atomic number (Z) and mass number (A).

Number of protons (Z) = atomic number (provided for each element)
Number of electrons (Z) = number of protons (for a neutral atom)
Number of neutrons (N) = mass number (A) - number of protons (Z)

Output : The calculator displays the number of moles of the substance, as well as the number of electrons, protons, and neutrons.

Optional Features:

Error Handling: Ensure the user inputs valid values and handle any potential errors gracefully.
Support for Ions: Extend the calculator to handle ions by allowing the user to input the charge, which would affect the number of electrons.
Interactive Interface: Develop a user-friendly interface that guides the user through the process step by step.

Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[ ] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[ ] I am a SWOC'24 contributor.

Code of Conduct

[X] I agree to follow this project's "Code of Conduct".

Can you assign this issue to me ?

Can you pls tell the proper name for your calculator @govinddwivedi-git

"Atomic Composition Calculator" @Rakesh9100

Proceed @govinddwivedi-git

Pls provide your PR @govinddwivedi-git

Go ahead @debangi29

Pls provide your PR @debangi29

Hello @Rakesh9100, please assign me the issue I can work on this.

Go ahead @bharat-c27

Pls provide your PR @bharat-c27

Sure, I am working on it.
I will provide you tomorrow


Sema: Narrow down the derivation of == for RawRepresentable enums to non-resilient modules

This change was originally introduced in https://github.com/apple/swift/pull/36752.
The problem occurs in the following scenario:

New compiler with this change is used to build a dylib and swiftinterface
file for module A, which defines a RawRepresentable enum type E.

Module B imports module A and references == on two E instances.

The module B is run against a dylib of module A built with the old compiler.

At this point, module B will not link (or run) because the symbol for E.==
is not present in the old dylib for A.
The only real solution here is to disable this new optimization when
building a module for -enable-library-evolution, unfortunately.
In the future, we could make the derived E.== symbol @_alwaysEmitIntoClient.
However today, synthesized declarations cannot be @_alwaysEmitIntoClient
because they do not have source text that can be emitted into the
swiftinterface file. One day, we might gain the ability to print Exprs as
source text that parses back in, at which point we could allow synthesized
declarations to be @_alwaysEmitIntoClient.
Fixes rdar://problem/84912735 and rdar://problem/82919247.

@swift-ci Please smoke test

@swift-ci Please smoke test Linux Platform


Options become invisible when rendered inside a parent with overflow scroll or hidden

Reproduction Link
https://codesandbox.io/s/vuemultiselect-issue-txjr4
When vue-multiselect component is rendered inside a parent or ancestor element with overflow property set to scroll or hidden and when dropdown options are rendered above position then part of the options become invisible.
I've actually figured out where the problem is but haven't had a chance to prepare a pull-request. The problem is that vue-multiselect is making calculations based on the position of it on the screen (via getBoundingClientRect). Instead it should find the first ancestor with overflow property that is not visible and use that as reference.

Have you made a fix for this issue, if so, can you please share?

Has a PR been opened for this? We are experiencing this as all.

Bump

Are there any updates here?


requireLineBreakAfterVariableAssignment: allow exception for init part o...

...f for loop
Fixes #1157.
Returns if node.parentNode.type === 'ForStatement'

Oh looks like I need ForStatement, ForInStatement, and ForOfStatement?

Coverage increased (+0.0%) to 97.7% when pulling a6944b48e32a51723e1eec50a85e47087bb7e038 on hzoo:require-line-break-exception into 038e20ff262cea691e513c9439b948bbbd80c151 on jscs-dev:master.

Coverage increased (+0.0%) to 97.7% when pulling 07aa5cc1cfcc4d0cde2c76b50c795d821a4af36d on hzoo:require-line-break-exception into 038e20ff262cea691e513c9439b948bbbd80c151 on jscs-dev:master.

Nice work @hzoo.


fix(remix-cloudflare-pages): don't clone request

Closes: #2195
#- [X] Docs
#- [X] Tests

Not quite sure this will work. Instead, I think we should add .clone() here and here. It looks like it was just missed off by accident in those couple of places. The other handlers in that file look to correctly clone the request.

Looks like it was intentionally removed by @jacob-ebey quite recently to fix some other bug that I don't know enough about.

@GregBrimble You mentioned the other PR. Does that also fix the problem you wanted to solve with this PR?
If so, please close this PR & #2195.

@MichaelDeBoey , no. @jacob-ebey's commit introduced the bug #2195. But I don't know enough about why that work was done to know how to fix it.
Happy to put up a PR to re-add the .clone(), but I imagine y'all probably want some other solution?

Hi, thankfully just found this issue/PR after having thought this was an error on my side. May I ask if there are any updates on this? I'm forced to use javascript-only Forms in my Remix+CF Pages project as a workaround now, which isn't ideal really.

@stepri Is this PR ready for review?

@stepri Mind addressing @jacob-ebey's feedback? We can get this merged after that's done.


Transciever doesn't read QUERY_SM_RESP

According to SMPP v3.4 specification a Transciever has to be able to receive QUERY_SM_RESP pdu, but returns SmppPduErr instead

PR: #22


Rename variants to pseudos

Variants currently provide the ability to create pseudo classes (just hover and focus are supported at this time). The name "variants" does not convey this.
"pseudos" makes more sense than explicitly using "pseudo classes" since in the future, this system should also support pseudo elements like ::before and ::after.

This is done in the next branch (yet to be documented,  it supports any pseudo using the pseudo key).


Create a built with gulp.js badge

Grunt has such a badge:
An intermediate solution (until a nice badge will be created) can use shields.io badge service and may look like this:

+!

https://github.com/gulpjs/artwork/pull/4#issuecomment-66841297

This is the closest I got to it with the shields.io site:

or some of these:

You're more than welcome to use any of them (or replace the words with whatever you want)


[HOLD] [HOLD  rn-onyx PR 572] Update node version for QSP

Update the node version to 20.15.1
Part of https://github.com/Expensify/Expensify/issues/416221

We also need to bump react-native-onyx version once https://github.com/Expensify/react-native-onyx/pull/572 is merged and version is bumped


luci-app-noddos 2 need to fix

Thanks to the author, great app! but..

Link together with the word:

Maybe just IP-addresses :):

If you need help let me know:)
I could prepare and make corrections myself, but maybe you have responsibilities, and my intervention will break them. Thank you!

You will most likely need to fix this file: https://github.com/openwrt/luci/blob/master/applications/luci-app-noddos/po/ru/noddos.po and then create a Pull Request to have the correct version merged.

There are to issues:

The space between localizable resource and the programmatic output is part of the localizable resource. If it's moved out of it, that should fix the problem.
IPv4 used as a header for the table where IPv6 addresses also present.

@feckert -- I can fix this if you want me to.

Upstream project is dead, this should be closed - https://github.com/noddos/noddos/issues/55#issuecomment-747105165

The package is to be removed.


hardened_malloc has MTE support now

Pixel 8 and Pixel 8 Pro were launched with MTE support and it's deployed in the latest release of GrapheneOS as an opt-in option in user facing security settings rather than hidden in developer options. It will be enabled by default for the base OS including system apps along with user installed apps without their own native libraries. It will be opt-in for apps with their own native libraries along with executables separate from their app processes.

It currently uses random tags with a reserved free tag and tags of adjacent allocations within the slab excluded. It relies on the existing enabled by default guard slab feature for protection between slabs (in the default configuration, a guard slab is left protected between each slab). It's not currently used for large (by default, larger than 128k) allocations which have randomly sized guard regions (at least 1 page) and a virtual memory quarantine (replaced by new PROT_NONE allocation on free and kept quarantined via FIFO queue and random array, similar to slab allocation quarantine in hardened_malloc).

It currently uses random tags with a reserved free tag and tags of adjacent allocations within the slab excluded. It relies on the existing enabled by default guard slab feature for protection between slabs (in the default configuration, a guard slab is left protected between each slab). It's not currently used for large (by default, larger than 128k) allocations which have randomly sized guard regions (at least 1 page) and a virtual memory quarantine (replaced by new PROT_NONE allocation on free and kept quarantined via FIFO queue and random array, similar to slab allocation quarantine in hardened_malloc).
The planned approach of incrementing through tags for each allocation/free after an initial random tag is chosen is not implemented yet and is still being thought over.


❓plugin question

I have a question about this

We’re working to refactor the Microsoft Graph Developer Proxy to make it more modular. This will not only make it easier to maintain the different features in the future but will also give you the opportunity to build plugins to support scenarios specific to your organization.

... I was wondering if you are considering giving a possibility to provide a plugin which will allow to mock responses for any API request (not only MS Graph)? I know, probably out of scope 😉, but just wondering 🙂.
BTW
Sorry I didn't find time to test it out sooner. Congrats on the awesome Hackathon result 🤩 You all rock and I hope to use msgraph developer proxy as an example to organize this kind of hackathon where I work 😉

Hey @Adam-it! Thank you for the kind words! As for your suggestion, you should be able to do this with the functionality we have available today. If you look at the sample responses.json in the project's root folder (not the repo root), you'll find that mocks are based on absolute URLs so you should be able to mock any request. Out of curiosity, would you mind sharing what you're thinking about mocking?

aaa of course it will work 🤩. I even looked at this part of the code (when checking a potential bug, in different issue) but didn't think of trying it out 😁, sorry for a stupid question 👍.
My scenario is to mock responses also for our internal Web API's.
The case I am trying to accomplish is to develop UI-automated tests of desktops applications (WPF based) that use many different API's (Graph, SharePoint, Azure, internal) and in an environment were the UI test may test the desktop app fully without relying on the availability of MS Graph (tenant) or our internal servers (internal Web APIs, also dev). So lets say 'almost' offline state 😉, where I test the app mocking any response from any API for UI tests done by TestStack.White

@waldekmastykarz yep it works 👍. Besides adding the mocked response to my custom API I also had to extend the graph-dev-proxy appsetting.json with additional urlsToWatch for my API 😉 Cool 🤩
I think this completes my PoC 👍 of a UI automated integration test of a desktop app mocking APIs response using graph-dev-proxy as a support tool. Thank you for your answer and help. You rock 🤩

Closing the issue as I got my answer 👍

Awesome! Thank you for sharing the additional information. Is this something that you could (and be willing to) possibly share on a community call? I bet many folks would find this invaluable.
/cc: @gavinbarron @garrytrinder @sebastienlevert

Sure. Today I presented the PoC internally, how it may be used to improve the quality of our UI tests. I still will need to work a bit on the PoC and add a couple of slides. I will try to finish it during the next weekend and will contact @garrytrinder to help me out set up a slot on a community call 👍

Awesome! Thank you so much and looking forward to it


GetPage returns a page when I think it should return nil

I understand that .GetPage on both Page and Site have some fuzziness when finding a page, but I was surprised by this.
content/
├── p1/
│   ├── index.md
│   └── p1.xyz
└── _index.md

layouts/_default/home.html
{{ with .Page.GetPage "p1.xyz" }}
  {{ .RelPermalink }}
{{ end }}

{{ with .Site.GetPage "p1.xyz" }}
  {{ .RelPermalink }}
{{ end }}

public/index.html
/p1/

/p1/

I would expect both methods to return nil because p1.xyz is a page resource, not a page.

It looks like .Page.GetPage is working as I would like with https://github.com/gohugoio/hugo/pull/11830, while .Site.GetPage still returns p1.

I have rewritten all of this, but I will put this test case on my "to check list".

This is fixed in my wip branch, but I have added a test for it.


Lumen support?

Hi,
I loved using this with Laravel and would like to continue using this on Lumen. I tried the following:

Registered the service provider on bookstrap/app.php with $app->register('Jenssegers\Mongodb\MongodbServiceProvider');
Since Lumen does not have config/database, I had to edit vendor\laravel\lumen-framework\config\database.php to add MongoDB configuration.

But when I actually try to do something, I get:
InvalidArgumentException: Unsupported driver [mongodb]
So I guess even though I register the service provider, it does not create the necessary database connector for MongoDB? I know this Lumen is not officially supported, but is there any chance to get this working?

Did you uncommented the $app->withEloquent() call in your bootstrap/app.php file?

Sorry I forgot to mention that. But yes I did. I just tried migrations and seeding first.

Having the same issue here, albeit I'm not trying migrations & seeding, just attempting to pull from an existing MongoDb database.
As Lumen is just using the Illuminate\Database component I'm sure it's going to be fairly simple to get this all hooked up, but it's Friday afternoon and I'm having too much trouble concentrating to figure it out at the moment :)

I created simple config/database.php to override vendor/laravel/lumen/config/database.php.
<?php

return [

    'default' => 'mongodb',

    'connections' => [

        'mongodb' => array(
            'driver'   => 'mongodb',
            'host'     => 'localhost',
            'port'     => 27017,
            'username' => '',
            'password' => '',
            'database' => 'test_db'
        ),

    ],

];

It's works.

@yohang88 did you make any other changes than adding the service provider to the boostrap/app.php?
I've also created the config file and i get the same "Unsupported driver" error.
How does your model look like?

Also having trouble with this, same error

@alex-LE
This is my bootstrap/app.php
<?php

require_once __DIR__.'/../vendor/autoload.php';

// Dotenv::load(__DIR__.'/../');

/*
|--------------------------------------------------------------------------
| Create The Application
|--------------------------------------------------------------------------
|
| Here we will load the environment and create the application instance
| that servers as the central piece of the framework. We'll use this
| application as an "IoC" container and router for this framework.
|
*/

$app = new Laravel\Lumen\Application;

// $app->withFacades();

// $app->withEloquent();

/*
|--------------------------------------------------------------------------
| Register Container Bindings
|--------------------------------------------------------------------------
|
| Now we will register a few bindings in the service container. We will
| register the exception handler and the console kernel. You may add
| your own bindings here if you like or you can make another file.
|
*/

$app->singleton(
    'Illuminate\Contracts\Debug\ExceptionHandler',
    'App\Exceptions\Handler'
);

$app->singleton(
    'Illuminate\Contracts\Console\Kernel',
    'App\Console\Kernel'
);

/*
|--------------------------------------------------------------------------
| Register Middleware
|--------------------------------------------------------------------------
|
| Next, we will register the middleware with the application. These can
| be global middleware that run before and after each request into a
| route or middleware that'll be assigned to some specific routes.
|
*/

// $app->middleware([
//     // 'Illuminate\Cookie\Middleware\EncryptCookies',
//     // 'Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse',
//     // 'Illuminate\Session\Middleware\StartSession',
//     // 'Illuminate\View\Middleware\ShareErrorsFromSession',
//     // 'Laravel\Lumen\Http\Middleware\VerifyCsrfToken',
// ]);

// $app->routeMiddleware([

// ]);

/*
|--------------------------------------------------------------------------
| Register Service Providers
|--------------------------------------------------------------------------
|
| Here we will register all of the application's service providers which
| are used to bind services into the container. Service providers are
| totally optional, so you are not required to uncomment this line.
|
*/

// $app->register('App\Providers\AppServiceProvider');
$app->register('Jenssegers\Mongodb\MongodbServiceProvider');

/*
|--------------------------------------------------------------------------
| Load The Application Routes
|--------------------------------------------------------------------------
|
| Next we will include the routes file so that they can all be added to
| the application. This will provide all of the URLs the application
| can respond to, as well as the controllers that may handle them.
|
*/

require __DIR__.'/../app/Http/routes.php';

return $app;

Maybe the tricky setting is $app->withEloquent(); . I'm uncommented that line, and get Unsuporrted Driver also.
This is my Model file User.php
<?php namespace App;

use Jenssegers\Mongodb\Model as Eloquent;

class User extends Eloquent {

    protected $collection = 'users';

}

This is my routes.php for test purpose:

$app->get('/', function() use ($app) {

    $users = App\User::all()->toJson();

    echo $users;

});

Response:
[{"_id":"5533b08eb8b200865f64f21f","nama":"Yoga Hanggara"},{"_id":"5533b0c9b8b200865f64f220","nama":"Handoko"}]

@yohang88 thanks!
I've disabled $app->withEloquent(); and now it works.
It might be a problem as i'm unable to use Eloquent now, but in my case i don't need it.

Disabling $app->withEloquent() works, but I consider this a workaround.

Just realized that registering Jenssegers\Mongodb\MongodbServiceProvider after make db via App::withEloquent() will throw Unsupported driver [mongodb].
// bootstrap/app.php

// $app->withFacades();

$app->withEloquent();

$app->register('Jenssegers\Mongodb\MongodbServiceProvider');

But if you register after withEloquent() line, it will be OK.
// bootstrap/app.php

// $app->withFacades();

$app->register('Jenssegers\Mongodb\MongodbServiceProvider');

$app->withEloquent();

:+1:  @krisanalfa

You may want to use The Capsule Manager and then creating your own mongodb config at project root
https://github.com/illuminate/database/blob/master/README.md
It's more portable I think.
Take advantage by using the middleware to configure mongodb:
<?php
			namespace App\Http\Middleware;
			use Closure;
			use Illuminate\Database\Capsule\Manager as Capsule;
			use Illuminate\Events\Dispatcher;
			use Illuminate\Container\Container;

			class ExampleMiddleware {

			    public function handle($request, Closure $next)
			    {
					$capsule = new Capsule;
                                           //Configure config file config/defaultmongodb.php
					\App::configure('defaultmongodb');
					$capsule->addConnection(config('defaultmongodb'));

					// Set the event dispatcher used by Eloquent models... (optional)
					$capsule->setEventDispatcher(new Dispatcher(new Container));

					// Make this Capsule instance available globally via static methods... (optional)
					$capsule->setAsGlobal();

					// Setup the Eloquent ORM... (optional; unless you've used setEventDispatcher())
					$capsule->bootEloquent();

					$capsule->getDatabaseManager()->extend('mongodb', function($config){
					    return new \Jenssegers\Mongodb\Connection($config);
					});

			        return $next($request);
			    }
			}

thx :) @krisanalfa

@askmatey Keep rock, bro!
@guns28 Anytime :smile:

Thank you so much @krisanalfa

Could someone add this as a PR to the documentation?

When I try to install the package it show the following errprs.
Problem 1
- jenssegers/mongodb v3.0.0 requires mongodb/mongodb ^1.0.0 -> satisfiable by mongodb/mongodb[1.0.0, 1.0.1, 1.0.2].
- jenssegers/mongodb v3.0.1 requires mongodb/mongodb ^1.0.0 -> satisfiable by mongodb/mongodb[1.0.0, 1.0.1, 1.0.2].
- jenssegers/mongodb v3.0.2 requires mongodb/mongodb ^1.0.0 -> satisfiable by mongodb/mongodb[1.0.0, 1.0.1, 1.0.2].
- mongodb/mongodb 1.0.2 requires ext-mongodb ^1.1.0 -> the requested PHP extension mongodb is missing from your system.
- mongodb/mongodb 1.0.1 requires ext-mongodb ^1.1.0 -> the requested PHP extension mongodb is missing from your system.
- mongodb/mongodb 1.0.0 requires ext-mongodb ^1.1.0 -> the requested PHP extension mongodb is missing from your system.
- Installation request for jenssegers/mongodb ^3.0 -> satisfiable by jenssegers/mongodb[v3.0.0, v3.0.1, v3.0.2].

@zahiruldu You have to install PHP MongoDB first. You can do it via PECL installation.
pecl install mongodb

I'm using Laravel Framework version 5.2.35 and the code is kind of different.
Can't use $app->withEloquent() this doesn't exist on laravel's Illuminate
Any update for this version?
`<?php
/*
|--------------------------------------------------------------------------

Create The Application

The first thing we will do is create a new Laravel application instance

which serves as the "glue" for all the components of Laravel, and is

the IoC container for the system binding all of the various parts.

*/

$app = new Illuminate\Foundation\Application(
realpath(DIR.'/../')
);
/*
|--------------------------------------------------------------------------

Bind Important Interfaces

Next, we need to bind some important interfaces into the container so

we will be able to resolve them when needed. The kernels serve the

incoming requests to this application from both the web and CLI.

*/

$app->singleton(
Illuminate\Contracts\Http\Kernel::class,
App\Http\Kernel::class
);`

Looks like you're using Laravel full, this issue is about Lumen. The instructions for the full framework should still work on 5.2.35.

@yohang88 solution is working.
My config/database.php looks like:
<?php
    return [
        'default' => 'mongodb',
        'connections' => [
            'mongodb' => [
                'driver'   => 'mongodb',
                'host'     => env('DB_HOST', 'localhost'),
                'port'     => env('DB_PORT', 27017),
                'database' => env('DB_DATABASE'),
                'username' => env('DB_USERNAME'),
                'password' => env('DB_PASSWORD'),
                'options'  => [
                    'database' => 'admin' // sets the authentication database required by mongo 3
                ]
            ],
        ],
        'migrations' => 'migrations',
    ];

hi guys
(my english is so bad and  excuse me for this format)
after a lot of search into the net,finally figure out how to use 2 different databases (Mongodb and mysql) in LUMEN.

create config directory in root and create new php file into config directory, named database.php (this is so important that name of php file  must to be database.php )
here is my database config file:
`<?php
return [
'default' => 'mongodb',
'connections' => [
 'mongodb' => [
     'driver' => 'mongodb',
     'host' => 'localhost',
     'port' => 27017 ,
     'database' => 'appstore',
     'username' => 'farzan',
     'password' => '1234admin',
     'options' => [
         'database' => 'admin' // sets the authentication database required by mongo 3
     ]
 ],

 'mysql' => [
     'driver' => 'mysql',
     'host' => 'localhost',
     'database' => 'lumen',
     'username' => 'root',
     'password' => null ,
     'charset'   => 'utf8',
     'collation' => 'utf8_unicode_ci',
 ],

]
];

as you see, my default db is mongodb, but you can switch between databases easily when you create a  Model class. for example if you want to work with mysql db you have to write:
protected $connection = 'mysql';
this line of  code change the default db in database.php
here is my model class
`<?php
namespace App\models;
use Illuminate\Database\Eloquent\Model;
class Car extends Model
{
protected $connection = 'mysql';
protected $fillable = [
'name', 'model' , 'created_at' , 'updated_at',
];
}and my controller class <?php
namespace App\Http\Controllers;
use App\models\Car;
class CarController extends Controller
{
public function showCars()
{
   $cars = Car::all();
    return response()->json($cars);
}

public function showCar($id)
{
    $cars = Car::find($id);
    return response()->json($cars);
}

}`
enjoy it:))))

I am trying to install plugin "composer require jenssegers/mongodb" on my lumen project but it is not instlling. It give me given below error
composer require jenssegers/mongodb
PHP Warning:  PHP Startup: Unable to load dynamic library 'mongo.so' (tried: /usr/lib/php/20190902/mongo.so (/usr/lib/php/20190902/mongo.so: cannot open shared object file: No such file or directory), /usr/lib/php/20190902/mongo.so.so (/usr/lib/php/20190902/mongo.so.so: cannot open shared object file: No such file or directory)) in Unknown on line 0
Cannot create cache directory /home/mayank/.composer/cache/repo/https---packagist.org/, or directory is not writable. Proceeding without cache
Cannot create cache directory /home/mayank/.composer/cache/files/, or directory is not writable. Proceeding without cache
Using version ^3.6 for jenssegers/mongodb
./composer.json has been updated
Cannot create cache directory /home/mayank/.composer/cache/repo/https---packagist.org/, or directory is not writable. Proceeding without cache
Cannot create cache directory /home/mayank/.composer/cache/files/, or directory is not writable. Proceeding without cache
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Conclusion: don't install jenssegers/mongodb v3.6.3
- Conclusion: don't install jenssegers/mongodb v3.6.2
- Conclusion: don't install jenssegers/mongodb v3.6.1
- Conclusion: remove illuminate/container v7.4.0
- Installation request for jenssegers/mongodb ^3.6 -> satisfiable by jenssegers/mongodb[v3.6.0, v3.6.1, v3.6.2, v3.6.3].
- Conclusion: don't install illuminate/container v7.4.0
- jenssegers/mongodb v3.6.0 requires illuminate/container ^5.8|^6.0 -> satisfiable by illuminate/container[5.8.x-dev, 6.x-dev, v5.8.0, v5.8.11, v5.8.12, v5.8.14, v5.8.15, v5.8.17, v5.8.18, v5.8.19, v5.8.2, v5.8.20, v5.8.22, v5.8.24, v5.8.27, v5.8.28, v5.8.29, v5.8.3, v5.8.30, v5.8.31, v5.8.32, v5.8.33, v5.8.34, v5.8.35, v5.8.36, v5.8.4, v5.8.8, v5.8.9, v6.0.0, v6.0.1, v6.0.2, v6.0.3, v6.0.4, v6.1.0, v6.10.0, v6.11.0, v6.12.0, v6.13.0, v6.13.1, v6.14.0, v6.15.0, v6.15.1, v6.16.0, v6.17.0, v6.17.1, v6.18.0, v6.18.1, v6.18.2, v6.18.3, v6.2.0, v6.3.0, v6.4.1, v6.5.0, v6.5.1, v6.5.2, v6.6.0, v6.6.1, v6.6.2, v6.7.0, v6.8.0].
- Can only install one of: illuminate/container[5.8.x-dev, v7.4.0].
- Can only install one of: illuminate/container[6.x-dev, v7.4.0].
- Can only install one of: illuminate/container[v5.8.0, v7.4.0].
- Can only install one of: illuminate/container[v5.8.11, v7.4.0].
- Can only install one of: illuminate/container[v5.8.12, v7.4.0].
- Can only install one of: illuminate/container[v5.8.14, v7.4.0].
- Can only install one of: illuminate/container[v5.8.15, v7.4.0].
- Can only install one of: illuminate/container[v5.8.17, v7.4.0].
- Can only install one of: illuminate/container[v5.8.18, v7.4.0].
- Can only install one of: illuminate/container[v5.8.19, v7.4.0].
- Can only install one of: illuminate/container[v5.8.2, v7.4.0].
- Can only install one of: illuminate/container[v5.8.20, v7.4.0].
- Can only install one of: illuminate/container[v5.8.22, v7.4.0].
- Can only install one of: illuminate/container[v5.8.24, v7.4.0].
- Can only install one of: illuminate/container[v5.8.27, v7.4.0].
- Can only install one of: illuminate/container[v5.8.28, v7.4.0].
- Can only install one of: illuminate/container[v5.8.29, v7.4.0].
- Can only install one of: illuminate/container[v5.8.3, v7.4.0].
- Can only install one of: illuminate/container[v5.8.30, v7.4.0].
- Can only install one of: illuminate/container[v5.8.31, v7.4.0].
- Can only install one of: illuminate/container[v5.8.32, v7.4.0].
- Can only install one of: illuminate/container[v5.8.33, v7.4.0].
- Can only install one of: illuminate/container[v5.8.34, v7.4.0].
- Can only install one of: illuminate/container[v5.8.35, v7.4.0].
- Can only install one of: illuminate/container[v5.8.36, v7.4.0].
- Can only install one of: illuminate/container[v5.8.4, v7.4.0].
- Can only install one of: illuminate/container[v5.8.8, v7.4.0].
- Can only install one of: illuminate/container[v5.8.9, v7.4.0].
- Can only install one of: illuminate/container[v6.0.0, v7.4.0].
- Can only install one of: illuminate/container[v6.0.1, v7.4.0].
- Can only install one of: illuminate/container[v6.0.2, v7.4.0].
- Can only install one of: illuminate/container[v6.0.3, v7.4.0].
- Can only install one of: illuminate/container[v6.0.4, v7.4.0].
- Can only install one of: illuminate/container[v6.1.0, v7.4.0].
- Can only install one of: illuminate/container[v6.10.0, v7.4.0].
- Can only install one of: illuminate/container[v6.11.0, v7.4.0].
- Can only install one of: illuminate/container[v6.12.0, v7.4.0].
- Can only install one of: illuminate/container[v6.13.0, v7.4.0].
- Can only install one of: illuminate/container[v6.13.1, v7.4.0].
- Can only install one of: illuminate/container[v6.14.0, v7.4.0].
- Can only install one of: illuminate/container[v6.15.0, v7.4.0].
- Can only install one of: illuminate/container[v6.15.1, v7.4.0].
- Can only install one of: illuminate/container[v6.16.0, v7.4.0].
- Can only install one of: illuminate/container[v6.17.0, v7.4.0].
- Can only install one of: illuminate/container[v6.17.1, v7.4.0].
- Can only install one of: illuminate/container[v6.18.0, v7.4.0].
- Can only install one of: illuminate/container[v6.18.1, v7.4.0].
- Can only install one of: illuminate/container[v6.18.2, v7.4.0].
- Can only install one of: illuminate/container[v6.18.3, v7.4.0].
- Can only install one of: illuminate/container[v6.2.0, v7.4.0].
- Can only install one of: illuminate/container[v6.3.0, v7.4.0].
- Can only install one of: illuminate/container[v6.4.1, v7.4.0].
- Can only install one of: illuminate/container[v6.5.0, v7.4.0].
- Can only install one of: illuminate/container[v6.5.1, v7.4.0].
- Can only install one of: illuminate/container[v6.5.2, v7.4.0].
- Can only install one of: illuminate/container[v6.6.0, v7.4.0].
- Can only install one of: illuminate/container[v6.6.1, v7.4.0].
- Can only install one of: illuminate/container[v6.6.2, v7.4.0].
- Can only install one of: illuminate/container[v6.7.0, v7.4.0].
- Can only install one of: illuminate/container[v6.8.0, v7.4.0].
- Installation request for illuminate/container (locked at v7.4.0) -> satisfiable by illuminate/container[v7.4.0].
Installation failed, reverting ./composer.json to its original content.
pleses help me


Fix DHCP option order not being preserved

Fixes #75 by introducing a data-structure that will preserve insertion order.

To be clear, removing the manual insert of End fixes your issue where the encoder did not produce a valid message right? It is just not going to be byte-by-byte the same.

Sorry for the delay on this. I'm unsure why this would break backwards compatibility. Users don't particular interact with the internal Options object.
It's giving 100% test passing on my machine, it looked like last time was a serde issue, so hopefully by explicitly enabling the serde feature of IndexMap this won't be a problem.
Also imo I think that a protocol encoding library should be byte-by-byte accurate between runs.

On Wed, Oct 09, 2024 at 09:58:54PM -0700, f3rn0s wrote:

Also imo I think that a protocol encoding library
should be byte-by-byte accurate between runs.

I think that it is good thing if server replies to options in the same
order as original requested by the client. ( In other words: Do not
assume that both ends can deal with a reshuffled option order. )
Groeten
Geert Stappers
Silence is hard to parse

@f3rn0s the iterator type makes it into the public API in IntoIter, that's the spot I'm concerned about the breaking change
Have either of you seen anything in RFC's which implied an option order?
I lean more towards btreemap because it's in the standard lib, requires no dependencies, and satisfies your concern of producing the same byte-by-byte output.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

2 of 3 (66.67%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.1%) to 52.428%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/v4/options.rs
2
3
66.67%

Files with Coverage Reduction
New Missed Lines
%

src/v6/options.rs
1
54.78%

Totals

Change from base Build<PHONE_NUMBER>:
-0.1%

Covered Lines:
1598

Relevant Lines:
3048

💛  - Coveralls

@leshow I opted for IndexMap since that preserves insertion order over just a consistent, but not necessarily visible/modifiable, order.
There was no reference to ordering in RFC 2131 or 2132, but it would be nice to have granular control in case we came across a server or client implementation that has weird requirements.


Cross compile prebuild libraries

The libraries are complicated to build, so they should be prebuilt. Install all toolchains and build them. Both debug and release for all platforms that godot can export to.
ETA: 8h

Tried the IOS cross compilation from the docs. It is just madness. Trying the godotengine/build-containers instead. It looks promising. If it works, I will put a submodule to the repo. I could then create a new SConstruct (or shell script) and put the library in files directory and then run the scons command in the docker images.

The library is buildable for IOS and probably OSX. It can be built only in a docker container. The container can be found in a fork of godotengine/build-containers. I will add it in this repo. The rust wrapper now uses a solana-sdk that is buildable for mac. https://github.com/Virus-Axel/solana-apple. It turns out I needed to fork solana repo as well. The libraries have been built at least and I will update the scons to utilize the podman containers.


Consolidate the various platform Xcode projects into a single one

This addresses a long-standing pain point in the way AudioKit platforms have been managed, by unifying all three platform-specific projects within a single AudioKit.xcodeproj.
There are six targets in that project (2 per platform, AudioKit and AudioKitUI). The end usage is not very different from before (mostly have to check you're using the target for the right platform), and the changes to the scripts were minimal.
As a result a number of files have been relocated and some duplicates were removed. This will make it easier to add new cross-platform features from now on, as including new files in an OS target is now just a matter of checking the box for the target in Xcode.

Killer


Implement HTTP plugin missing options

Related to #7

I will add documentation when #13 is merged.


Pfsense+ support

Hi!
Thanks for keeping up the work on a project. Been using a CE edition for while and now planning to switch to Pfsense plus (because of the customer)
Is this edition (pfSense plus) supported as well?
Id like to use the API for this device:
https://shop.netgate.com/products/1100-pfsense
Thanks for answering! :)

Sorry, just noticed that there are related issues here.
Maybe updating the READMe with the informations would be plus (pun intended).


Modify output for table_info command in rel table

Currently, we need to run 3 CALL statements to retrieve the primary key info from the node tables so that we know how to construct the correct export query for the rel table.
CALL table_info(Node1)
RETURN *;

CALL table_info(Node2)
RETURN *;

CALL table_info(Rel)
RETURN *;

The first two show us the primary keys for the node tables. Simply exporting the rel table with all properties of the node table (or skipping the node tables entirely) isn't useful.
Current
When we output the table info for a rel table, it only outputs the relationship properties, but no node primary key info (which would be helpful to output the rel table).
kuzu> CALL table_info("Rel") RETURN *;
--------------------------------------------
| property id | name           | type      |
--------------------------------------------
| 1           | id | INT64     |
--------------------------------------------
| 2           | example_prop     | STRING     |
--------------------------------------------

Desired
We could output the src and dest primary keys from the underlying rel table information.
kuzu> CALL table_info("Rel") RETURN *;
--------------------------------------------
| property id | name           | type      |
--------------------------------------------
| 1           | id | INT64     |
--------------------------------------------
| 2           | example_prop     | STRING     |
--------------------------------------------

src: Node1, primary_key: id
dest: Node2, primary_ley: id

This would allow the user to obtain just enough information via a single CALL statement to output the rel table with the node primary keys via a subsequent COPY TO command.

Consider assigning this to @manh9203 @mxwli or @MSebanc as well during times they need an issue to take care of.


Feature/test no pandas

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (092b6ae) 69.72% compared to head (a25fa67) 90.40%.

Additional details and impacted files
@@               Coverage Diff                @@
##           development      #89       +/-   ##
================================================
+ Coverage        69.72%   90.40%   +20.67%
================================================
  Files               40        9       -31
  Lines             2269      896     -1373
================================================
- Hits              1582      810      -772
+ Misses             687       86      -601

Flag
Coverage Δ

processing-tests
85.34% <ø> (?)

table-tests
94.16% <ø> (?)

unit-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@hugolarzabal can you review it one last time?


write_to_tmp_storage() for import_action()

Created a separate function to handle writing imported data to tmp_storage to improve readability and testability.
Tests passed, 3 skipped. Follows PEP-8.
I didn't write new tests but I'd be happy to, if they are needed.

Coverage increased (+0.009%) to 91.943% when pulling 02767f333edeb6a7a3f5db5560d66c764809f303 on toivomattila:write_to_tmp_storage into 65416fbcefd4b3203a498020ac007b18c00b12a3 on django-import-export:master.

Coverage increased (+0.009%) to 91.943% when pulling 02767f333edeb6a7a3f5db5560d66c764809f303 on toivomattila:write_to_tmp_storage into 65416fbcefd4b3203a498020ac007b18c00b12a3 on django-import-export:master.

thanks @toivomattila


typeToString for type alias defined in different file does not use the type alias name

TypeScript Version:  nightly (2.5.0-dev.20170712)
Code
a.ts
import { f } from "./b";
f({ x: 1 });

b.ts
export type X = { x: number };
export function f(x: X): void {}

Hover over f.
Expected behavior:
(alias) f(x: X): void
Actual behavior:
(alias) f(x: {
    x: number;
}): void

We should also just put a limit on how much we're willing to write. I noticed a long pause when hovering over Diagnostics in our codebase, which is a huge object literal, with an equally large inferred type.


WASM

WASM

very simple js with an import image, a bunch of input parameters (cutoff, order etc.) and applying SF.


make isLockingOptimistic a store feature

addressed PR feedback on adding isLockingOptimistic to store features

I removed all the unrelated changes in this new PR and made the changes you suggested. Any updates?

Is there a need to update Chapter 12 of the documents to explain how this is defaulted and configured now ?

There may be. I will investigate.

this is synced off an old branch. will create a new PR off titan11.


Enable LTO and Upgrade to binutils 2.36.0

Nice work @fjtrujy !
A little background on the LTO feature:
I've tested compiling everything with LTO. It's a very interesting feature I didn't know much about. Thanks to @leidav for pointing this out in #7 . Compiling newlib, ps2sdk, ps2sdk-ports, etc... with this option is possible, but requires little changes everywhere:

add -flto flag when compiling and linking
link using gcc (of gcc-ld). Linking with ld alone will not work.

Currently compiling everything like this will result in link errors, but at least with this feature enabled everyone can use it in their own projects, and perhaps we can slowly start enabling the flag in other projects as well.


Metal setup merge

Merging back the result of merging main into metal-setup.

🙏

Looks like there's an issue with depth between extrusion and symbols here.


SDWebImage error

/MWPhotoBrowser/MWPhotoBrowser/Classes/MWPhoto.m:162:63: Incompatible block pointer types sending 'void (^)(NSUInteger, long long)' to parameter of type 'SDWebImageDownloaderProgressBlock' (aka 'void (^)(NSInteger, NSInteger)')

solved? how?

my project imports MWPhotoBrowser，has error.solved by changing block pointer types "void (^)(NSUInteger, long long)" to "void (^)(NSInteger, NSInteger)".

my english is poor ,hope u could understood what i say

Thank you. Totally understand.

See MediaBrowser I made this library to Swift3 using latest SDWebImage

@zhangkuo921112   I Sove it，
typedef void(^SDWebImageDownloaderProgressBlock)(NSInteger receivedSize, NSInteger expectedSize);

![image](https://user-images.githubusercontent.com/8489350/31599034-45438ec8-b216-11e7-9e82-6eb3184f2f95.png)


Update main.nf

Modified the help message to display an example on how to run the pipeline

This should be tested first and possibly with a small (test) dataset

For this PR, I only updated the help message.
I tested it, and it works.


refactor the opt

Description of your changes

Fixes #
I have:

[ ] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

Though you want to pass parameters via options, the fields in the StepGeneratorOptions are still exported to users. It seems useless since the options do not limit the usage of the field in the struct.

changed to lower case

or we can split the types file into multi files


add span_snapshot to session-end.json

Goal

Testing

Release Notes

WHAT:
WHY:
WHO:

#614  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @nelsitoPuglisi and the rest of your teammates on  Graphite


Register in VPN process as well

Task/Issue URL: https://app.asana.com/0/488551667048375/1207294405155930
Description
Add native crash handling for VPN process now that we also have it for the main process
Steps to test this PR
Test native crash handing

[ ] apply the patch from this Asana task to this PR
[ ] build and install and launch app
[ ] verify Native crash handler init pixel sent appears in logcat
[ ] verify Native crash handler successfully initialized. apperas in logcat
[ ] verify VPN crashes and Native crash pixel sent appears in logcat
[ ] In kibana, verify pixels appear when applying this filter pixel:m.app*.native.crash.*
[ ] pixels have the right params, vpn process name, right appVersion and right customTab true/false value

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#4519  👈
#4517
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @aitorvs and the rest of your teammates on  Graphite

Verifying expectations on this... i do see the pixel however the app doesn't crash. Instead, the VPN process dies; I assume this is what is expected and the testing step is wrong.
Yeah, copy/paste error, fixed.

What i'm not sure about is how the reporting and retry mechanism go together; I see the VPN continually turn off and on again and native crash pixels fire over and over. Obviously it's crashing here because of the patch, but if it were a real crash are you worried about sending the same crash pixel repeatedly if it tries and fails to establish the VPN connection? I saw > 30 pixels generated before I realised what was happening.
Approving the PR on the assumption the above is all in line with your expectations on how that should work; let me know if not.
Yeah, the VPN coming back right after a crash is a "feature" of the VPN. We bind to the process and try to recreate it if it crashes for unexpected reasons.
The addition here is the pixel we'll send. Granted it can end up in spikes, tbh I don't know how often that (vpn crash loop) happens in production

Maybe I add a different kill switch for VPN process registration in case we need to disable due to spamming pixels?

Maybe I add a different kill switch for VPN process registration in case we need to disable due to spamming pixels?

@aitorvs good idea


mini.align: accept optional line count prefix

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md

Module(s)
mini.align
Description
It would be nice if mini.align's ga and gA maps accepted an optional count that was interpreted as the number of lines to operate on.
For example, in order to =-align the 5 lines counting from the current one, currently this is done via ga4j=. I am proposing to also allow 5ga=. Note this saves a keystroke.

Thanks for the suggestion!
This indeed sounds interesting. Yet I don't think it is enough to justify added complexity (both in code and mental). Right now ga and gA are regular operators (same as built-in d, c, etc.) and always expect textobject/motion after it. Having a different fixed linewise behavior for when v:count is supplied seems to be going against all established operators logic.
Closing as not planned.


[Bugfix] run apiPackageModify after setup venv

Background
When RackHD and on-http both in interpendent PRs, we consider the swagger-ui-api packages on-http-api1.1 on-http-api2.0 on-http-redfish-1.0 may be changed, so they must be uninstalled->rebuild->installed again. Function apiPackageModify is for this.
setup virtualenv used to be done out of  test.sh, so  apiPackageModify will be applied in new venv.
but recent changes setup venv after  apiPackageModify, this make apiPackageModify invalid.
Solution
add apiPackageModify to the last step of  setupVirtualEnv
@panpan0000 @PengTian0

:+1:


Input and AssetTypes missing in the doc

Hello, I was following this doc. I noticed Input and AssetTypes wasn't imported.
So I went to see the .md file corresponding to this doc. I found it here.
It seems the code comes from this notebook. Only this code is taken :
# Training MLTable defined locally, with local data to be uploaded
my_training_data_input = Input(type=AssetTypes.MLTABLE, path=training_mltable_path)

# Validation MLTable defined locally, with local data to be uploaded
my_validation_data_input = Input(type=AssetTypes.MLTABLE, path=validation_mltable_path)

# WITH REMOTE PATH: If available already in the cloud/workspace-blob-store
# my_training_data_input = Input(type=AssetTypes.MLTABLE, path="azureml://datastores/workspaceblobstore/paths/vision-classification/train")
# my_validation_data_input = Input(type=AssetTypes.MLTABLE, path="azureml://datastores/workspaceblobstore/paths/vision-classification/vali

Hence we don't see the imports.
I think we should add the imports because it can be confusing while reading the doc.

I created a Pull Request. So it should be ok.

@LucasColas thanks for noticing and fixing this.  Changes have merged and should appear later today in our documents.
#please-close


If destination directory doesn't exist, Copy-FileToNavContainer fails

The Move-Item command doesn't create the destination directory first if it doesn't exist. Unlike Copy-Item -Force which creates directories, Move-Item -Force doesn't seem to and instead fails the command.

If the ... directory (or any other element of the destination path) does not exist, the command fails. The missing directory is not created for you, even if you use the Force parameter. (source)

https://github.com/microsoft/navcontainerhelper/blob/4bf885d513a1bdaf59af2a0113cee3ad428f9c21/Misc/Copy-FileToNavContainer.ps1#L40
Perhaps it could be preceded by something like this? New-Item -Force does create subdirectories if they don't exist.
if( -Not (Test-Path $containerPath))
{
    New-Item -Path $containerPath -ItemType Directory -Force | Out-Null
}

I did this by putting a Invoke-ScriptInNavContainer with the above beforehand, but it just seems more neat if the Copy could handle it.

For the ease of using the function, I agree with you.

Shipped in <IP_ADDRESS>


Add in places in UI for the new system labels that have been introduced

Based on the labels docs, some of these need to be incorporated into the UI so that if you clone a service, it will clone the behavior. Due to the fact system labels are not copied (https://github.com/rancher/rancher/issues/2342), it needs to be added in the UI so that clone would work.
http://docs.rancher.com/rancher/labels/
Labels to add into the UI include:
io.rancher.container.dns
io.rancher.container.hostname_override
io.rancher.container.start_once
io.rancher.container.pull_image
io.rancher.container.requested_ip

+1 for at least start_once to be a UI checkbox.

:+1:

DNS is on by default and doesn't have a false value so it doesn't make sense to show.  The others are fine.

DNS: Available only if managed network, off by default
Hostname: Available only on service, radio to select "container name" or custom string
Start once: Available only on service
Requested IP: Available only if managed network
Pull: Enabled by default because it seems like what people want

DNS: This only works for Host networking so should hide for bridge/none. @vincent99
Pull: It's not enabled by default. Did we want to?
I have not tested on containers, just services.

(in master/after rc3)

DNS Changed to only networkMode=host
DNS changed to actually work when set
Pull on by default

Tested and entered separate bugs against issues.


Registration error in Windows version

Getting error "Email and password didn't match." when trying to register with existing email
There is an error in server response:
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'my-email' for key 'users_email_unique' (SQL: insert into `users` (`name`, `email`, `password`, `id`, `updated_at`, `created_at`) values (my-login, my-email, some-password-hash, some-id, 2017-12-27 00:11:15, 2017-12-27 00:11:15))"

(some values are replaced)
I think it should show something like "User already exists. Forgot password?"

Yes, I was plan this on future release, notifications detail such as success and fail request for registration and login, thank you.
I will close this, and move it to #2. And if you want to help me with a PR I will take a look. 👍


Fix stale injection config

Signed-off-by: yeya24<EMAIL_ADDRESS>What problem does this PR solve?
Fixes #547

Codecov Report

Merging #548 into master will decrease coverage by 5.30%.
The diff coverage is 39.44%.

@@            Coverage Diff             @@
##           master     #548      +/-   ##
==========================================
- Coverage   61.39%   56.08%   -5.31%
==========================================
  Files          64       66       +2
  Lines        4069     4256     +187
==========================================
- Hits         2498     2387     -111
- Misses       1383     1699     +316
+ Partials      188      170      -18

Impacted Files
Coverage Δ

api/v1alpha1/kernelchaos_types.go
13.84% <0.00%> (+9.40%)
:arrow_up:

api/v1alpha1/timechaos_types.go
17.14% <0.00%> (+7.14%)
:arrow_up:

controllers/kernelchaos_controller.go
0.00% <0.00%> (ø)

controllers/podchaos/types.go
65.95% <0.00%> (ø)

controllers/stresschaos_controller.go
0.00% <0.00%> (ø)

pkg/chaosdaemon/netem_linux.go
26.66% <0.00%> (ø)

pkg/chaosdaemon/netlink_linux.go
0.00% <ø> (ø)

pkg/chaosdaemon/stress_server_linux.go
0.00% <0.00%> (ø)

pkg/utils/chaosdaemon.go
51.21% <ø> (ø)

pkg/webhook/config/config.go
17.14% <ø> (-72.86%)
:arrow_down:

... and 47 more

Continue to review full report at Codecov.

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

/merge


Action Hub Auth State returned to looker is saved successfully by Looker but Looker GUI does not recognize this and ends up in an infinite loop of Auth.

Trying to create a Custom Action.
Trying to integrate the Google Workspace / Google OAuth / IDP to authenticate.
Can successfully get the OAuth window and Auth in successfully.
The oAuthFetchInfo also successfully gets the state and Looker has the state saved. However, the GUI is not recognizing the event of a successful state / saved state.
This results in the Auth to be stuck in a loop keep asking to Auth in even after a successful Auth.
However, after successful auth, when the GUI asks to auth again immediately if chosen cancel this works as expected and the custom action can be used.
The challenge is if the state expired and requires to auth again hitting cancel causes confusion.
Workaround:
After a successful auth when the GUI shows the window to auth again hit cancel, and refresh the page.

Using a custom Action Server
Create a simple Google IDP Authentication
In version 23.6 the Auth gets successful token and the token is sent to Looker and Looker is saving the state (Proven by working action if the user was to hit cancel on the subsequent Auth Prompt).
The auth will keep on going on a loop, asking use to keep logging in.

Hi @kosalangoogle
I believe the way that this is intended to work is that the action logic should tell Looker whether to present the auth button or not, based on looking at the content of the received state.
Are you able to share a sample request your action is receiving and the associated response you are sending back?
Thanks!

Same issue. Looker UI should refresh the form when we click on Verify credentials, but instead it just reverts to the original Login form.


Httpweb

I think you guys are good at rust.  Here is a plugin that serves web pages with login and logout.  Could you please do a code review?
1> check for rust code
2> are there any ticks that would make the code better?
3> could I use ACL and/or http-auth, or something similar.
4> what config parameters could I add

very good!

Implement your business first, code and compile it, then there is no problem. As for code quality and performance optimization; if it is not a high-concurrency scenario, you can postpone it for later consideration.
Built-in AUTH/ACL and HTTP AUTH/ACL are for MQTT, not suitable for HTTP permission control.
Add configuration items according to your business needs.

I can compile and run the plugin you implemented, looking forward to your continued improvement of it!
---- Replied Message ----
| From | Shaun @.> |
| Date | 07/11/2023 14:46 |
| To | @.> |
| Cc | @.***> |
| Subject | [rmqtt/rmqtt] Httpweb (PR #28) |
I think you guys are good at rust. Here is a plugin that serves web pages with login and logout. Could you please do a code review?
1> check for rust code
2> are there any ticks that would make the code better?
3> could I use ACL and/or http-auth, or something similar.
4> what config parameters could I add
You can view, comment on, or merge this pull request online at:
https://github.com/rmqtt/rmqtt/pull/28
Commit Summary
3a6836a http-web and logging
1d49283 fixed build
bc6aee6 added tls
File Changes
(8 files)
MCargo.toml (4)
Adist/index.html (1)
Mrmqtt-bin/Cargo.toml (2)
Armqtt-plugins/rmqtt-http-web.toml (15)
Armqtt-plugins/rmqtt-http-web/Cargo.toml (19)
Armqtt-plugins/rmqtt-http-web/src/config.rs (84)
Armqtt-plugins/rmqtt-http-web/src/lib.rs (323)
Mrmqtt.toml (3)
Patch Links:
https://github.com/rmqtt/rmqtt/pull/28.patch
https://github.com/rmqtt/rmqtt/pull/28.diff
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


How to make from_index() faster?

Hello.
I have the index saved to disk (4 json.gz files, and one embeddings_0.pt file).
from_index() takes anywhere between 15-30 seconds, which seems like a long time, given that the index is saved to disk.
I have verbosity set to 1, and it seems to me that the Loading checkpoint shards part is taking majority of that time.
What can be done to make it faster?

Hey, thank you for flagging!
Loading checkpoint shards is not actually part of the indexing, but it's the usual huggingface transformers message while it's loading the model (so you can properly embed the queries).
Loading big models' shards is often quite slow. If this is problematic, you could try looking at how people have tried to optimise it in the past (e.g. https://github.com/huggingface/safetensors/issues/333)


Improving clarity demo

todo:

[x] Add support for mermaid graphs

mgaitan/sphinxcontrib-mermaid

See also: maksimdrachov/opencyphal-tutorial

I would like to add the following mermaid diagrams to improve clarity:
---
title: Legend
---
flowchart TB
    id1[/Message-publisher\]
    id2[\Message-subscriber/]
    id3{{Service}}
    id4[subject_or_service_id:type]

---
title: demo_app.py
---
flowchart TB
    subgraph 42:org.opencyphal.pycyphal.demo.demo_app
        direction TB
        subgraph heartbeat_publisher
            direction TB
            heartbeat_publisher_1[/uavcan.node.Heartbeat.1.0\]
        end
        heartbeat_publisher --> uavcan.node.heartbeat
        subgraph temperature_setpoint
            direction TB
            temperature_setpoint_1[\uavcan.si.unit.temperature.Scalar_1/]
        end
        2345:uavcan.si.sample.temperature.Scalar --> temperature_setpoint
        subgraph temperature_measurement
            direction TB
            temperature_measurement_1[\uavcan.si.sample.temperature.Scalar_1/]

        end
        2346:uavcan.si.unit.voltage.Scalar --> temperature_measurement
        subgraph heater_voltage
            direction TB
            heater_voltage_1[/uavcan.si.unit.voltage.Scalar_1\]
        end
        heater_voltage --> 2347:uavcan.si.unit.voltage.Scalar
        subgraph least_squares
            direction TB
            least_squares_1{{arasaka_corp.PerformLinearLeastSquaresFit_1}}
        end
        123:arasaka_corp.PerformLinearLeastSquaresFit_1.Request --> least_squares
        least_squares --> 123:arasaka_corp.PerformLinearLeastSquaresFit_1.Response
    end

---
title: plant.py
---
flowchart TB
    subgraph 43:org.opencyphal.pycyphal.demo.plant
        direction TB
        subgraph heartbeat_publisher
            direction TB
            heartbeat_publisher_1[/uavcan.node.Heartbeat.1.0\]
        end
        heartbeat_publisher --> uavcan.node.heartbeat
        subgraph temperature
            direction TB
            temperature_publisher_1[/uavcan.si.sample.temperature.Scalar_1\]
        end
        temperature --> 2346:uavcan.si.sample.temperature.Scalar
        subgraph voltage
            direction TB
            voltage_1[\uavcan.si.unit.voltage.Scalar_1/]

        end
        2347:uavcan.si.unit.voltage.Scalar --> voltage
    end

The last one is a useless change, but:

(Feel free to roll back)

This issue:

I've added sphinxcontrib.contentui in order to allow toggling the view of "Graph explanation" (see docs/pages/demo.rst). I think it's a bit clearer if the reader can toggle certain parts of the explanation that might be useful upon the first read, but migh otherwise be a bit too long to include in the default view of the page.
So that leaves 2 options:

remove this extension
circumvent this check

@maksimdrachov nudge

Feel free to merge, or keep open (since I might want to change some other small stuff around as well)

I might want to change some other small stuff around as well

That's fine, let's take these changes in as they come in separate PRs.


Album cover folder as a volume

The album folder is not marked as a volume, so it's lost when container is destroyed. I'll make a PR soon in order to fix it.

See #11


feat: add plugin migrate subspace

Basic Checks
Have you run rush change for this change?

[x] Yes
[ ] No

If No, please run rush change before, this is necessary.
If adding a new feature, the PR's description includes:

[x] Reason for adding this feature
[x] How to use
[x] A basic example

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
Summary
Rush plugin to migrate an existing project into a subspace.
Detail
The rush subspace is a new feature that intends to move common projects into 1 workspace. Teams that want to take advantage of this feature need to manually migrate these projects. This script automates most of these required steps to speed up the migration process.
How to test it
rush migrate-subspace

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.pedro.gomes seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Update GitLab to version 8.13.0

Update GitLab to 8.13.0, released on Oct 22nd
This update brings improved root_squash support in the case of users setting up NFS on the hostmounts.

cc\ @ssk2
Tested on DC/OS 1.8.6
Tested an upgrade on a single-node pinned instance, and tested install of both CE and EE image

Thanks @twk3!


Weird text being rendered in vim with airline enabled?

[x] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: MacOS Sierra 10.12.6
Hyper.app version: 2.1.1
Link of a Gist with the contents of your .hyper.js: https://gist.github.com/JesseLeite/0a595fb0b41d5a5895814f7f971ee92b
Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere):
The issue is reproducible in vanilla Hyper.app:

Issue

I'm not sure if this is a Hyper issue, or a Vim (or Vim plugin) issue... but I think it's related to all three.  It seems when I open some files like my .vimrc in Vim in Hyper, I get these weird characters rendering at bottom, which are not actually in my .vimrc file.  It seems to be related to the vim-airline plugin, because disabling that plugin fixes the glitchy characters.  However, if I leave the vim-airline plugin enabled and try in Terminal.app, I can't reproduce the issue in those terminals.  Could it be something to do with vim-airline in combination with Hyper?
With vim-airline installed in vim in hyper:

Without vim-airline installed in vim in hyper:

Updated to vim 8.x, it's fixed!


Participant Self-Description

What this PR changes/adds
Generate a Gaia-X Self-Description based on a template for each participant and inject it into the associated Identity Hub.
Why it does that
Each dataspace participant should have its own Self-Description.
Linked Issue(s)
#186
Checklist

[ ] added appropriate tests?
[ ] performed checkstyle check locally?
[ ] added/updated copyright headers?
[ ] documented public classes/methods?
[ ] added/updated relevant documentation?
[ ] added relevant details to the changelog? (skip with label no-changelog)
[ ] formatted title correctly?

Codecov Report

Merging #272 (d648bd2) into feature/186-participant_self_description_ (8e1c880) will not change coverage.
The diff coverage is n/a.

@@                             Coverage Diff                              @@
##             feature/186-participant_self_description_     #272   +/-   ##
============================================================================
  Coverage                                        78.78%   78.78%
  Complexity                                          20       20
============================================================================
  Files                                                5        5
  Lines                                               66       66
  Branches                                             5        5
============================================================================
  Hits                                                52       52
  Misses                                              14       14

Impacted Files
Coverage Δ

...spaceconnector/mvd/FederatedCacheNodeResolver.java
100.00% <ø> (ø)

...onnector/mvd/RegistrationServiceNodeDirectory.java
90.00% <ø> (ø)

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


fixed events

Fixes #232
Description: The events were not visible in the admin area. this pr is a minute change to fix that.
Checklist

[x] I've followed the Contributing guidelines provided in the repository.
[x] I've made the changes which were demanded in the linked issue.
[x] I've tested my code on a Chromium based browser.
[x] I've tested my code on Mozilla Firefox.
[x] My code gave a clean console on debugging. (no warnings/errors)

Testimonial
N.A

@ankiiitraj i request you to review this pr, since hg is currently working on admin consoles in general, and can refactor the hg's website console once its working and we see any issues with its current working.


i18n(es): Updating Firebase Realtime Database

Description (required)

Related issues & labels (optional)

Closes #
Suggested label:

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File
Note
Locale

src/content/docs/es/guides/backend/google-firebase.mdx
Localization changed, will be marked as complete.
es

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


reduce memory usage of concourse-lite vagrant box

Would it be possible to reduce the amount of memory used by the vagrant box to something more reasonable like 2 GB instead of 6 GB?

I strongly second. 6GB may be reasonable if you have 16 or 32 gigs, but I have but 8, and as soon as I started running my first build, my entire system became unresponsive
at least a default like min(33% of RAM, 6GB) would make a much better first impression for people in my situation
(or if 6 is really necessary, bail with an error in the vagrantfile )
I discovered the VM_MEMORY env var but in a reload (to test caching behavior) I forgot to include it on a vagrant up and again totally jammed my system for several minutes until I managed to turn the vm off without having to hard reset my computer (as I did the first time)

See the related issue at https://github.com/starkandwayne/concourse-tutorial/issues/46.
This is definitely a huge problem, and it's discouraging to hear concourse-lite might be designed with these defaults. I'm not sure who has 6GB spare memory sitting around on their computers, but so far this issue took down my Mac four times before I found this issue.
Attempting to use VM_MEMORY=2048 vagrant up) caused VBoxHeadless to immediately eat up 5GB+ (instead of the previous behavior I'd seen where it would start with ~2.35 and increase to >5 only as I used Concourse).
I seem to finally have gotten it under control with the standard Vagrant memory controls:
config.vm.provider "virtualbox" do |vb|
  vb.memory = 2048
  vb.cpus = 2
end

But there really should either be better defaults, or a clear warning that concourse-lite won't run on many systems without these settings being tweaked.

a PR for this would be nice; that number has just stuck around since we based this on BOSH lite.

fixed by #12


mkvtoolnix: 7.8.0 -> 7.9.0

Added support for the new qt5 gui
@Fuuzetsu @k0ral

Cool. Can we make wxWidgets off by default or even gone all together?

The QT5 interface still has some minor bugs that need to be fixed, they will probably be fixed by the next 8.0.0 release(such as can't disable/enable steams individually).  The biggest issue is the Rakefile doesn't install the icons and desktop entries when wxwidgets is disabled(this was probably originally a way to detect if the GUI was enabled).  I would consider this to be a transitional release so I have added support for both and the necessary fixes so that once everything works we can disable or remove wxwidgets.

Could you please add legacyGUI = false to the mkvtoolnix-cli override (in all-packages.nix) ?
I think this is needed so the assert legacyGUI -> withGUI && wxGTK != null; works correctly.

It doesn't need to be added to all-packages.nix, the assert will work correctly as is, it enforces that for legacyGUI to be enabled that withGUI must be enabled and wxGTK must not be null.  It only matters that mkvtoolnix-cli must override/disable withGUI in all-packages.nix.  If withGUI is disabled, then the if statement in configureFlags will never pass the legacyGUI flag regardless of whether it is enabled or not.
As far as disabling  legacyGUI by default, it can't be done cleanly yet, there are upstream fixes needed to the build system that I previously described.

As a matter of fact, the assertion currently fails:
> nix-build -A mkvtoolnix-cli
error: assertion failed at "/home/koral/nixpkgs/pkgs/applications/video/mkvtoolnix/default.nix":15:1

legacyGUI is true by default, thus it requires withGUI to be true as well, which doesn't hold for mkvtoolnix-cli.

Yeah, your right, I wasn't paying attention there, I should sleep.

@k0ral
OK, now it should work.  This way should allow you to enable one or the other or both now too.
@k0ral @Fuuzetsu
Just to avoid confusion from anyone that uses to package in the meantime, I disabled the newer qt5 GUI until the next release when some issues with it can be resolved.  The current GUI I left titled as legacy so that it is easy to switch back to the QT interface once 8.0.0 is released and hopefully it will be usable at that point.

What concerns me sligthly is that anyone who had withGUI = false now gets wxWidgets GUI. Feels like legacyGUI should be set to false when withGUI is but that's difficult to put in.
What I would do instead is keep wxWidgets as withGUI so that it remains the default for this release and expose the QT5 GUI under a new option. Then in next release we can just make QT5 the default and deal with wxWidgets separately. This means that only people likely to use the recent package are going to be bitten by change of attributes (easily fixable) rather than suddenly getting wxWidgets which with its dependencies is too heavy to just be pulled in randomly. Consider mkvtoolnix being used on a server, with this change suddenly we're pulling in wxWidgets…

I do agree, but to note that we also already have both mkvtoolnix(gui) & mkvtoolnix-cli that should handle this for anyone that uses the package.

Ah, you're correct.


Handle Too many requests

Hi,
When adding a lot of env variables, I get rate limited by Vercel. However, it is currently not detected and eventually the command fails. Maybe detect & sleep for x seconds? Thanks!
Added Environment Variable NUXT_ENV_RECAPTCHA_KEY to Project umsfront [2s]
Error! Too many requests - try again in 46 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 46 seconds (more than 120, code: "api-projects"). (429)
/bin/sh: -c: line 1: syntax error: unexpected end of file
/bin/sh: -c: line 0: `echo -n (xxxxx) | vercel env add NUXT_ENV_HOME_LEGAL production'
Error! Too many requests - try again in 46 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 45 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 46 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 46 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 45 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 45 seconds (more than 120, code: "api-projects"). (429)
/bin/sh: more!: command not found
Vercel CLI 19.1.1
Error! Too many requests - try again in 44 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 43 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
/bin/sh: more!: command not found
Vercel CLI 19.1.1
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 41 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 39 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 38 seconds (more than 120, code: "api-projects"). (429)
/bin/sh: More!: command not found
Vercel CLI 19.1.1
Error! Too many requests - try again in 38 seconds (more than 120, code: "api-projects"). (429)
groups.: No such file or directory
Vercel CLI 19.1.1
Error! Too many requests - try again in 38 seconds (more than 120, code: "api-projects"). (429)
Error! Too many requests - try again in 38 seconds (more than 120, code: "api-projects"). (429)

🤯 I haven't personally tested deploying that many environment variables.
I will look into solutions to this.

This tool is very useful.
It's not a radical measure, but could we have, for example, a configurable option to have the interval of an API call?
Or can't we have the option to just do the writing without deleting env variable?


Typo? s/menvcfg/henvcfg/

" When the hypervisor extension is implemented, if menvcfg.HADE is 1, hardware updating of PTE A/D bits is enabled during G-stage address translation."
I believe that should be if henvcfg.HADE is 1.

Nevermind. I think confused myself.


vite: add option to set dev load context within Cloudflare preset

TODO

[x] tests
[ ] changeset (?)
[x] docs

superceded by https://github.com/remix-run/remix/pull/8649


[Draft] Migration to NeonDB

@Swiizyy what do we do with this PR? its super out of date, lets create a new pr with just the migration commits added

Ah we have this already in the #562 PR ^^ I will close this


MDK tutorials - updated with latest changes

MDK tutorials - updated with latest changes

@MichaelCzcz thanks for reviewing, updated with proposed changes.

@jitendrakansal You have missed one requested change.

@MichaelCzcz Please check now
missed  "Now, we deploy" part


Add support to set capabilities on Solr cloud container's security context

Hi Team,
Currently It is possible to set capabilities for initContainers and sidecarContainers, Eg:
securityContext:
  capabilities:
    drop:
      - ALL

But, there is no way to set capabilities on Solr cloud container's security context, can you please help in adding support for it?

@HoustonPutman is support for setting capabilities on the pod security context confirmed to be added eventually (and if it is, is there already an indication on when)? Or is this only under consideration and might be not added at all?

@ollixy you cannot set capabilities on the podSecurityContext, cf. https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.26/#podsecuritycontext-v1-core. What we need is a separate option to specify the securityContext of each container in the pod.
@HoustonPutman +1 for this issue, since solr is incompatible when using sokme restricted PSS and enforcing these with keyverno (for example).
I'll try to file an PR, but my knowledge about operators is quite limited.

@mmoscher @HoustonPutman any news on this one?

Any news on this one?

Hi all! a new version was recently released (April 12, 2024, Apache Solr Operator™ v0.8.1 available, there is no solution to our problem) is there any news on our problem?

Hi all! a new version was recently released (April 12, 2024, Apache Solr Operator™ v0.8.1 available, there is no solution to our problem) is there any news on our problem?

@ollixy , @pareekdevanshu, @mmoscher, @aaronsuns , @AyzekTime
This is an open source project, and we rely on contributions. If your day-job has a need for this and are willing to sponsor such a feature, then the best way forward is to arrange so that you can contribute a PR directly, and we'll help get it in to the next version.

I'm running into this issue on EKS.
@janhoy / @HoustonPutman Are these extra capabilties/privs ever actually needed? If not, we can likely hardcode in the changes made in this comment:
https://github.com/apache/solr-operator/issues/671#issuecomment-1875441585
Here is an example of a values.yaml I'm trying to use for a Solr Cluster:
securityContext: &securityContext
  allowPrivilegeEscalation: false
  capabilities:
    drop: ["ALL"]
  runAsNonRoot: true
  seccompProfile:
    type: RuntimeDefault
  allowPrivilegeEscalation: false

podOptions:
  labels:
    sidecar.istio.io/inject: 'false'
  podSecurityContext:
    <<: *securityContext
zk:
  provided:
    zookeeperPodPolicy:
      securityContext:
        <<: *securityContext
      labels:
        sidecar.istio.io/inject: 'false'

To the maintainers: Is there a particular reason you specify your own fields in podOptions.podSecurityContext instead of just accepting a k8s podSecurityContext API type? Using the upstream k8s type would mean that no-one would manually have to add fields available in the k8s type to the securityContext objects in this CRD, right? I'm definitely no expert, but I've seen this done in other operators.


Talos Linux support

Talos Linux does not have modprobe, which leads to the install-cni.sh script not working correctly, which prevents the installation of CNI, although the necessary module is already built directly into the kernel.
At the same time, CAP_SYS_MODULE is blocked in Talos Linux, which also makes it impossible to install CNI in the standard configuration.
Also, due to the fact that the file system in Talos Linux is read-only, installing the binary files required in the install-cni.sh script into the system is impossible.
Is it possible to solve this problem?

I think we can take care of this by adding the right configuration options to the Helm chart. I see that Talos has installation instructions for Cilium, which includes the correct Helm values to provide: https://www.talos.dev/v1.5/kubernetes-guides/network/deploying-cilium/
2 things I am not sure about:

CNI binary installation: there is no way around it actually, the CNI binary must be copied to the host file system (/opt/cni/bin). This is the case for all K8s CNI plugins. Are you sure that Talos doesn't make an exception for this directory?
Antrea Agent runs in privileged mode. Would that be a problem for Talos?

/opt/cni/bin maybe is writable, cause it's mentioned in docs. But there're other pathes in install script and maybe one of them would fail.
CAP_SYS_MODULE is restricted by Talos (https://www.talos.dev/v1.5/learn-more/process-capabilities/) and currently helm chart have no option to disabling it - https://github.com/antrea-io/antrea/blob/main/build/charts/antrea/templates/agent/daemonset.yaml#L100
Running pod in privileged mod is not a problem
But modpeprobe in install script is a problem - https://github.com/antrea-io/antrea/blob/main/build/images/scripts/install_cni#L58 , cause Talos doesn't include it as far as I understood. But needed kernel modules should be already builtin to kernel - https://github.com/siderolabs/pkgs/blob/252a59ffe374ce98c71b0c9b959e691addd38919/kernel/build/config-amd64#L1687-L1690 . So it's needed to somehome bypass modprobe

An update on this:

we have merged #5718 which lets users adjust the securityContext for Antrea containers, and in particular drop capabilities
we still need a way to skip loading kernel modules in both the install-cni initContainer and the antrea-ovs container (the OVS start script will try to do modprobe openvswitch as well)

when running Talos in Docker (for dev only), modprobe will always fail [^1]
even when running Talos using VMs (qemu in my case), modprobe is failing even though this comes as a surprise to me. The /lib/modules/$(uname -r)/modules.builtin file seems correct, and modprobe should not try to load modules listed in this file (and hence should not fail). I have opened an issue for this: https://github.com/siderolabs/talos/issues/7980

[^1]: This is the reason for Docker:
In a Talos Node, modules information is in /lib/modules/6.1.61-talos/ (kernel version will change based on the Talos version), but uname reports the kernel version from the host (in my case 6.4.16-linuxkit given that I am using Docker Desktop). Tools will usually check for built-in modules or available modules under /lib/modules/$(uname -r), which in this case won’t work given the kernel mismatch.


Add Linux support

Fixes #2

Thanks for the PR.
This makes sense to me, however, we'd need to update the release workflow, as it currently does not use build.sh and only runs on mac-os image.
Could you please help us with this?


Wrong now day

Hello, thank you for great package, but I saw 2 issues, first of all I run example and start date is 28 Tuesday, but today is 27 Tuesday(see screenshots). Second: how can I set start week from Monday ?

Hi man. Thank you for the issue. I will verify it.

@Sergionius thanks for your feedback, We've updated this lib to allow you to change the default start day of the week. We'll be working on the bug you reported and ASAP, we will release the bux fix with both corrections.

@Sergionius new version 0.1.1 start the week on Monday and fix the bug the order day. The new versions will parameterize. Thanks for the feedback.


add spread attributes

if we won't get rid of the wrapper (#5), let's at least make it more flexible.
This PR allows the wrapper to receive more attributes, like extra classes, in order to avoid breaking compatibility with pre defined element structures

I think I did something wrong here... I was using an old version somehow.


intersection type: T & { … } not fully documented

Search terms
intersection type
( I searched for "intersection type" before opening this issue; I found https://github.com/TypeStrong/typedoc/issues/1519 but that was closed as completed )
Expected Behavior
I would expect intersection types to be documented as well (their fields), i.e. the right-hand-side of typical intersections such as A & { … }.
Actual Behavior
Intersection type is not fully documented.
Steps to reproduce the bug

Install typedoc v0.24.7
Generate documentation for following snippet

export = project;

declare namespace project {
  /**
   * Options abc.
   */
  export type Options = {
    /**
     * My Flag
     */
    flag?: boolean
  }

  export type OtherOptions = Options & {
    /**
     * other flag
     */
    flag2: string | 'f' | 'g'
  }
}

Open documentation. You will see:
Options:

OtherOptions:

Environment

Typedoc version: 0.24.7
TypeScript version: Version 5.0.4
Node.js version: v18.16.0
OS: macOS 13.3.1

This is working as designed right now -- TypeDoc only recurses to show properties if the root type is an object type. The relevant code is in member.declaration.tsx.
I'm not sure what the right solution for this is yet. It certainly doesn't make sense to recursively show properties for every object type within an arbitrary type e.g. type Foo<T> = T extends { a: string } ? Something<{ b: string }> : never, but this case as well as a recent SO question are both simple enough that they probably ought to be recursed into and rendered.
It seems like it would be confusing to me to recurse if:

There are more than one object types to display
The object type isn't "roughly top level" Record<X, {}> yes, {}[] yes, T & {} yes, T | {} maybe? T extends {} no, SomeRandomGeneric<{}> maybe?

Hi,
from my TS-noob perspective, I thought that even for something like { a: String } | { b: String } both sides would be rendered, i.e. all anonymous structures would be documented. And for Type | { … }, Type would be a link and the right-hand-side would be documented inline as well.
Of course, I don't know all the edge cases and I'm by far not experienced enough in TypeScript to say which way would be better.
But from a user's perspective (i.e. the one reading the documentation), I think it's strange to see a type whose properties are not documented in the rendered HTML. Would it be feasible to render the anonymous structure's properties if there is only one such occurrence? Or to render all, but add headings such as 1. Block to separate different properties of the same name? (e.g. { a: String } | { a: Integer })
My use case is:
type Config = { … }
type SubConfig = Config | { … }

Regards,
Andre

Generally, if that much description of a type is necessary, I'd look at splitting it up - it's probably too complex of a type. TypeDoc's CommentDisplayPart type is an example of this, before it was split up it looked like this:
export type CommentDisplayPart =
    | { kind: "text"; text: string }
    | { kind: "code"; text: string }
    | { kind: "inline-tag";  tag: `@${string}`; text: string; target?: string | number | ReflectionSymbolId; };

Rendering all of the properties for this type twice would get really messy.. (potentially more than twice since the heading would probably have to render the type to indicate what object it's associated with)
There might be a good way to do this that I'm not seeing, UI design isn't my strong point, I tend to prefer just looking at declaration files for library documentation rather than looking at HTML rendered docs (at least for TypeScript, browsing header files is much worse than cppreference)

I see. Personally, I'd rather see it all duplicated. After all, it's what the developer wrote. If developers want fewer details on a page, they should split it up (as proposed by you). In my case it's only a few properties that are disjunct. At the moment, I use interfaces for documentation, because there all properties are rendered with their description. I only use TypeDoc for documentation, so it's not an issue for me, but I thought types would fit better. :-)

If someone wants to give implementing a implementing deeply nested rendering for object literals a shot, I'd be happy to take a look at it, but given my expertise lies far outside UI design, and I'm not seeing an obvious way to do this in a non-terrible way, for now I'm just going to go with:
{props.type?.visit<JSX.Children>({
    reflection: renderTypeDeclaration,
    array: (arr) => arr.elementType.visit(visitor),
    intersection: (int) => int.types.map((t) => t.visit(visitor)),
    union: (union) => union.types.map((t) => t.visit(visitor)),
    reference: (ref) => ref.typeArguments?.map((t) => t.visit(visitor)),
    tuple: (ref) => ref.elements.map((t) => t.visit(visitor)),
})}

(that is, render the properties of objects at the top level, or one level deep for arrays/intersections/unions/references/tuples)

@Gerrit0 you may want to investigate piggybacking off of however vscode does its tooltip rendering, if that's possible.  It deeply renders the type (often when you don't want it to!).  Also, the current TypeDoc renderer seems to do deep rendering by default in type parameter constraint blocks, of all things...
In general I think exposing some level of user control over this is one of the main ways TypeDoc could be improved.  I may start looking at PRing some improvements of my own in this direction - I think @expand or @noexpand tags could be very helpful here.


Release v50.1.0

[ ] The purpose of this PR is explained in this or a referenced issue.
[ ] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] Apache v2 license headers are included in each file.

/azp run

/azp run

/azp run check-enforcer

/azp run check-enforcer


Meta QA probabilities

What does this PR do?
This PR returns probabilities for MetaQA.
Other minor changes:
Code reformatting

Looks good to me! Solves #450


Get rid of 'six' usage

Getting rid of 'six' usage which leads to stop compatibility with py2

recheck


Implement API Endpoints for Fetching and Updating Object Data

The backend lacks specific API endpoints to fetch properties using projectId and to update specific objects (sites, buildings, apartments, garages).

The Property Endpoint returns a JSON object with an empty Property list, indicating a bug in the implementation.

@HassanAlhawari1998 Are you sure you have already created a property?
If not, this behavior is fine for me since total and size are 0.

@astanik there are issues with PropertyItemJSON not being nullable and with RepositoryProperty not returning correct results in findPropertyByProjectId. The getEntityManager.createNamedQuery always returns an empty list, but the query works correctly when called directly without using createNamedQuery.

@HassanAlhawari1998 I found an error with the total value being returned. Your problem seems to be the offset you are passing as a query parameter. For an offset of 10 you would expect objects from 10 to 19.


templates/image-builder: add CHANNEL as parameter so it get's filled

CHANNEL has to be specified as parameter to get filled
otherwise it's literally ${CHANNEL} :-|
followup of #1299

Sidenote: it was pretty hard to find as it's badly documented and I hope that's the correct implementation but considering this wide pattern it's really ok to explicitly set the filename
https://github.com/codecov/uploader/blob/main/src/helpers/files.ts#L161