Create extra values field in kluster secret

We need a way to customize the helm-chart values without exposing everything into the API.
This adds a field into the kluster secret to hold a map of extra values which get deep merged into
the helm values used to render to helm.
This lets us customize resources and additional flags on the apiserver, controller-manager, scheduler etc. without exposing them via the API.

Ok this looks good but I think what is still missing is actually calling MergeMaps in KlusterToHelmValues no?


the future of npm tooling in nixpkgs (yarn2nix)

In my opinion nixpkgs needs to have some tooling to fetch dependencies from npm.
In the past there was yarn2nix, which was removed, but not quite, because riot-desktop still has it's own version of it in the tree.
In my custom packages I have been using the out-of-tree solution https://github.com/moretea/yarn2nix with little hassle, but it has a few problems when used in nixpkgs:

The lack of recursive nix or IFD in Hydra requires the yarn.nix file to be manually generated and added to nixpkgs which makes packages hard to maintain and bloats nixpkgs with unnecessary data
The hashes for git dependencies are not contained in yarn.lock, which yarn2nix works around by using the builtin fetchGit function, which is not an option in nixpkgs since it is not available in Hydra
It has been discussed in the past if the yarn2nix project should be part of nixpkgs, since it has a relatively large, active code base, and nixpkgs was not keeping up with upstream development.

Possible solution for 1. and 2.: Download the dependencies during build in a fixed-output derivation like buildRustPackage does it. The requirement is that yarn is reproducible, and it has been discouraged by some folks to use fixed-output derivation like this, because it might mask impurity introduced by the tool, in this case yarn.
Possible solution for 3.: Split yarn2nix into two parts, like bundix and bundlerEnv. The js part generating yarn.nix from yarn.lock is maintained outside nixpkgs, the nix part using yarn.nix to build a node_modules directory is maintained in nixpkgs, so that other packages in nixpkgs can use it.

Now if you ask me, yarn2nix is a well-built tool like it is, and I would opt for solving 3. like mentioned above and adding it to nixpkgs again. This could be improved upon once the general underlying problem of 1. and 2. is solved in general, since the same problem applies to bundix and bundlerEnv.

A competent npm tooling is a requirement for #60788

Another approach which is interesting is @nmattia's https://github.com/nmattia/napalm which doesn't try to place files on disk but instead spawns a fake NPM registry. It only works for NPM but I assume that it could be adapted for yarn as well. The advantage is that it requires much less nix code and we don't have to depend on undocumented disk locations.

note: I axed the NPM registry, I'm now putting the packages directly in npm's cacache

With yarn2nix-moretea added back to nixpkgs this issue is solved for me.
This time I hope it will stay up-to-date and it will not be necessary to remove it again.
The generate.sh script provided will make it very easy to pull new changes from upstream.


Parameter to make apoc.periodic.iterate() raise an error when any batch fails

Feature description (Mandatory)
I'm using apoc.periodic.iterate() to iterate nodes and perform actions on each node. Sometimes, some of the actions would fail. However, when any action fails, the call to apoc.periodic.iterate() is still successful. Therefore, the queries following the call will still be executed. I find it inconvenient because I don't want the following queries to be executed when the call to apoc.periodic.iterate() fails. In addition to that, I'm using cypher-shell command to execute by queries, and I want cypher-shell to exit with a non-zero status code if any of the action fails in the call to apoc.periodic.iterate().
My proposal is to add a parameter (e.g. raiseErrorWhenAnyBatchFail) to apoc.periodic.iterate(), so I can config it to raise an error when any batch fails. That way, it can prevent the following queries to be executed and make cypher-shell exit with a non-zero status code when error occurs.
Considered alternatives
I know that I can check the output parameters failedOperations and failedBatches that returned from the call to apoc.periodic.iterate() to know if the call has failed or not, but I didn't find any way to raise an error with the help of these 2 output parameters.
How this feature can improve the project?
I guess it's a feature request that other people would find helpful.

Hi. Thank you for adding this. We will look into it and come back to you.

Thank you!

The issue has been fixed by @johnlinp in this pull request https://github.com/neo4j/apoc/pull/304. Thank you so much for your contribution!

@AzuObs Excuse me, this issue has nothing to do with the PR #304. Please reopen this issue. Thank you.

Oops, you are right. Apologies for that.

Hi @johnlinp. I will close this issue since we currently do not extend APOC core. Feel free to open a new github issue for apoc extended if you think this functionality would fit in there.

I just reported at https://github.com/neo4j-contrib/neo4j-apoc-procedures/issues/3547.


Interface & Visualization

So I was trying to follow along with the interface README. When I ran yarn start, it returned this error: Command failed with exit code 127. After some Googling, apparently just yarn needs to be run first, and then yarn start worked. So that should be added to the README.
This is how the first page looks for me:

@dlebauer or @Chris-Schnaufer would you be able to confirm your review so that this PR can be merged?

This PR is now complete in itself, please have a final review and then merge it.
@Chris-Schnaufer @KristinaRiemer @dlebauer @saurabh1969

This PR is now complete in itself, please have a final review and then merge it.
@Chris-Schnaufer @KristinaRiemer @dlebauer @saurabh1969

Due to a lot of lines of code in this PR, it might be challenging to review the work done in recent commits so to make this easier, I have opened issues(regarding the recent commits) that are implemented in this PR.

Visualize the shapefiles
Added a Success Page
Added an Error Page
Added requests file to hit YABA app client routes
Created a validation/review page


issue with reading data from Excel XLSX

Hi,
I am trying to read a column from an Excel file and then use it in Dymola. Could you please tell me what is the procedure? I am using the ExternData.Types.ExternXLSXFile.constructor function with as input the filename of the excel file, but I get the error:
Error: The class ExternData.Types.ExternXLSXFile is not a package since it contains the
non-constant component id. Lookup in non-package is restricted to
encapsulated elements, but search found the function constructor.
You can turn off this check by setting Advanced.CheckPackageRestriction:=false;
Component context: ExternData.Types.ExternXLSXFile.id
Component declared as Integer id
File: C:/Program Files (x86)/Dymola 2016 FD01/Modelica/ExternalObject.mo, line 2
Must translate function ExternData.Types.ExternXLSXFile.constructor.
Error: The class ExternData.Types.ExternXLSXFile is not a package since it contains the
non-constant component id. Lookup in non-package is restricted to
encapsulated elements, but search found the function constructor.
You can turn off this check by setting Advanced.CheckPackageRestriction:=false;
Component context: ExternData.Types.ExternXLSXFile.id
Component declared as Integer id
File: C:/Program Files (x86)/Dymola 2016 FD01/Modelica/ExternalObject.mo, line 2
Failed
Failed to expand ExternData.Types.ExternXLSXFile.constructor("...path...").
After that, I guess I have to use the function ExternData.Functions.XLSX.getReal. Am I correct?
Thanks

Do you use the current master or the last release v1.1.0 of the package? The reason I ask is the currently commented example models in the master head. See https://github.com/tbeu/ExternData/blob/master/ExternData/package.mo#L457-L468 for a commented example which should work in Dymola. Can you please confirm (since I have no Dymola running at the moment)?
If you want to read a column from an Excel sheet you need to call getReal in a loop and assign the values to a Real vector (either in an initial equation or with parameter binding).
P.S. The example models will be commented in again for v2.0.0 once they are restructured.

Hi,
I have tried to run the example ExternData.Examples.XLSTest1, but Dymola crashes.
Any idea about what the reason could be?
Thanks

Which version of the package do you use? Which version of Dymola do you use? Which OS do you use Dyomola on? Which compiler do you use (MSVC, MinGW or GCC on Linux)?

I can now confirm that XLSXTest1 crashes on Dymola 2016 32-bit on Win. Will fix it.


Handle local filesystem debuginfo discovery relative path case

I recently came across a case where I originally thought it was an issue with the project, but it turns out to be a case where Parca Agent doesn't handle a specific case of debuginfo discovery on a local filesystem.
In this particular case it was about discovering the locally available libc debuginfo from Redpanda. When reading the .gnu_debuglink it returned this:
$ readelf --hex-dump=.gnu_debuglink /proc/25357/root/opt/redpanda/lib/libc.so.6

Hex dump of section '.gnu_debuglink':
  0x00000000 37623936 64666238 33663062 64636236 7b96dfb83f0bdcb6
  0x00000010 61343130 34363962 38326638 36343135 a410469b82f86415
  0x00000020 65356164 61332e64 65627567 00000000 e5ada3.debug....
  0x00000030 21c5dc99                            !...

It says 7b96dfb83f0bdcb6a410469b82f86415e5ada3.debug, which seemed inconsistent with the Build ID of the shared library:
$ readelf --hex-dump=.note.gnu.build-id /proc/25357/root/opt/redpanda/lib/libc.so.6

Hex dump of section '.note.gnu.build-id':
  0x000003a0 04000000 14000000 03000000 474e5500 ............GNU.
  0x000003b0 6e7b96df b83f0bdc b6a41046 9b82f864 n{...?.....F...d
  0x000003c0 15e5ada3                            ....

Which says 6e7b96dfb83f0bdcb6a410469b82f86415e5ada3.
I thought this was incorrect, but it turns out .gnu_debuglink can also be meant as a relative path. Meaning it was trying to tell us to search for the file 7b96dfb83f0bdcb6a410469b82f86415e5ada3.debug. And we should have known the 6e prefix directory from the Build ID.

Isn't it this case?
https://github.com/parca-dev/parca-agent/blob/68ecbac6dc8d30f3e59df93d8c1f27c1ef2b0a7f/pkg/debuginfo/find.go#L222

The current implementation should have covered the relative path. I wonder what I've missed 🤔 ?

Can we write a test for the exact setup? During testing it definitely did not work. Also while that case may be able to find it, it does not actually use whatever the .gnu_debuglink contains, it just does what we think it should contain.


Update containerd to 1.6.12 or above

@h0x0er this is needed since containerd has a vulnerability. It does not affect us, but we should still upgrade. Can you please update it on go.sum/ go.mod and create PR in the int branch?

This is done


Image diff (subtraction) support

I'd love to see a histogram! Them I wouldn't have to load up DaVinci Resolve or Premiere Pro just to see one :).

I'd love to see a histogram! Then I wouldn't have to load up DaVinci Resolve or Premiere Pro just to see one :).


spatial/{r2,r3}: fix/clarify doc comments

Please take a look.

Codecov Report

Merging #1680 (444396d) into master (d920954) will decrease coverage by 0.06%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1680      +/-   ##
==========================================
- Coverage   73.27%   73.21%   -0.07%
==========================================
  Files         507      502       -5
  Lines       60004    59721     -283
==========================================
- Hits        43970    43722     -248
+ Misses      13553    13536      -17
+ Partials     2481     2463      -18

Impacted Files
Coverage Δ

spatial/r2/vector.go
96.66% <ø> (ø)

spatial/r3/vector.go
97.50% <ø> (ø)

lapack/gonum/dlaqr1.go
40.62% <0.00%> (-15.63%)
:arrow_down:

graph/iterator/nodes_map_safe.go

graph/internal/set/same_appengine.go

mat/offset_appengine.go

...sp/fourier/internal/fftpack/array_bounds_checks.go

mat/index_bound_checks.go

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 d920954...444396d. Read the comment docs.

Disregard the previous comment, I was using a shared home computer and didn't notice a different user was logged into Windows.


Installing Default Dynamic through Marketplace with Beautiful Lyrics crashes Spotify

Describe the bug
When Default Dynamic is installed through the Marketplace with Beautiful Lyrics installed too, Spotify will loop reload a few times before crashing/closing. Happens most of the time when opening Spotify but not every time. This has been an issue for a while now. Installing Default Dynamic through the PowerShell script does not have this issue which makes me believe this is a bug with Default Dynamic when installed through the Marketplace but please tell me if I'm wrong. for some reason quickly clicking the Light/Dark mode button prevents this from happening.
To Reproduce
Steps to reproduce the behavior:

Install Default Dynamic through Marketplace
Install Beautiful Lyrics through Marketplace
Close and reopen or Refresh Spotify

Screenshots
https://github.com/JulienMaille/spicetify-dynamic-theme/assets/141533012/ce5c12a3-e4ad-411b-86e1-2f472a2c6af9
Desktop Setup

Operating System: Windows 11
Spotify: <IP_ADDRESS>8.g0ea3f38b
Spicetify: 2.36.12
Theme: 4.9

Logs

I have no idea how to solve that, have you also contacted the team behind Beautiful Lyrics and the Marketplace?

am also facing the same issue its crashing when devtools is enabled


getFormMeta returning empty object for Form fields with display: none

Are you submitting a bug report or a feature request?
Bug report
What is the current behavior?
In my Redux Form, I have an onChanged handler added to the form, which triggers an action for some tracking purpose as shown below
@reduxForm({
  form: FORM_NAME,
  touchOnBlur: false,
  onChange: autoSaveAndTrackChanges,
})

In the autoSaveAndTrackChanges method, I am calling getFormMeta method, to find the field which has { active: true } just to find which field was changed.
It works fine for all the fields, except for one of my custom Checkbox component which has the actual <input> element hidden with styling { display: none } because it shows a fancy checkbox instead of the regular one. getFormMeta returns an empty object when this checkbox is checked.
However, when I remove display: none from the <input> element, getFormMeta works fine and returns the actual object with all the required meta values.
What is the expected behaviour?
getFormMeta should work fine even if the form field is hidden with display: none
What's your environment?
"redux-form": "7.2.3"

That's probably not a redux-form issue.
Hidden elements can't be focused -- you didn't show your field implementation, but from your question I assume you must be spreading the input props on that hidden input.


support Redis cluster as cache storage

Is your feature request related to a problem? Please describe.
Support Redis cluster as cache storage.
Describe the solution you'd like
Connect to a Redis cluster by using redis+cluster:// schema.
Additional context

UniversalClient is useful for connecting Redis cluster and Redis single node in one implementation.
A parser is needed for parsing Redis cluster schema.
Tests could be added in compatibility tests. (Setup a Redis cluster by services)

This appears to have regressed.
redis+cluster schema is no longer supported


jsonify does not accept strings

If I try to feed a string into jsonify, I get the following error:
ValueError: dictionary update sequence element #0 has length 1; 2 is required
I imagine this is intentional... perhaps it's related to the same problem described in issue #170 ?

#1703


Syntax examples

Hi! I think an examples folder with one or more syntax example would help. The rust docs indicate that most functionality is based on the Core struct. It links to the Core C++ docs. When I try to run methods from that page, like GetAvailableDevices(), or get_available_devices() from the Python API, the method is unrecognized. How should you, for example, list available devices in the Rust bindings? Thank you!

I agree. I might even prefer them as doc tests; I've done this before (e.g., here) but more examples would be helpful. Are you interested in helping out with this?
Re: your GetAvailableDevices() question, I think that is a slightly different matter: the Rust bindings are incomplete in the sense that they don't implement every possible function from OpenVINO's C API. I only initially added the functions I needed, but I am open to PRs adding more. Do you want to take a stab at it? It looks like we would need to call ie_core_get_available_devices and then read the returned ie_available_devices struct into a Vec<String>.

I have a fork and am ready to get cranking. Example to start: I'd like to implement these:
use openvino::runtime::{ie_api::Model, AsyncInferQueue, Core, PartialShape};

Would I need to edit openvino-sys directly, or just openvino? I'm guessing both, since I can't find these other than Core in the openveino-sys docs.

Cool! I think there are a couple of things to note here:

the openvino-sys crate is generated from OpenVINO's upstream C API; you can see how this is done in the codegen.rs task. All of the functions you need should be in the generated folder.
if the functions you are looking for are not there, it's probably because OpenVINO is in the process of switching to a new API, "API 2.0," which we haven't yet moved to in these bindings but you may be using in C/C++/Python. In other words, we need to shift these Rust bindings from ie_* to ov_*; you can see more of the differences between the current API and API 2.0 here.

Can you give me an idea of whether the APIs you are looking to add are available now or only in API 2.0? If they're available now, you should be good to go to add new Rust functionality; if they're only available in API 2.0, it might be a bit of a heavy lift for you to refactor everything to use the API 2.0 and then add the functionality you want. If it's that latter case, I do plan to get to the "API 2.0 refactor" but it might not happen immediately; I'm available on Zulip if you want to chat about all this.

Great! I'm using the OpenVINO face recognition demo.
Well, a heavily modified version of it, but the OpenVINO calls are the same. So, this should be the latest API, since I'm running OpenVINO 2023.1.0.
So, it sounds like this rust binding isn't ready for the current OpenVINO API, as the root cause perhaps.

I wonder if it would be possible to use bindgen to wrap the C OpenVINO directly, without having to manually implement things. I've done that before, eg with CMSIS-DSP. But I don't know how well it would work for stuff that h as an allocator and/or C++ features. You can then wrap the results in a more rust-friendly way, like replacing pointers with refs, or just leave it.

That's essentially how these crates work: openvino-sys contains the bindgen-generated C API and then openvino wraps up those unsafe calls in Rust-friendly syntax. I'll revive this issue once I get to refactoring these crates to use "API 2.0."

@David-OConnor, it's been a while since this issue was opened; should I close it or are you still considering adding some examples?

You can close it; I've moved on; thx!


Console commands, after interacting with the user, the code is incorrectly encoded.

Laravel Version: 8.20.1
PHP Version: 7.4.11
Database Driver & Version: Mysql

Description:
In console commands, after interacting with the user, the code is incorrectly encoded.
As can be seen in the image below, with a very simple example, a message with special characters is displayed, just to show that it works, after that, we ask any question (confirmation fails too), and after that the encoding is lost. The console's answers come with the wrong encoding, but that wouldn't be a problem, the problem is that after the question, a database import is performed, and the imported data is scrambled.
I know its a windows problem, because on linux this error doesnt happend.
as a standard shell application, I'm using git bash, but I've already tested with windows cmd and power shell

Might be something related to Mingw64, Laragon, Visual Studio Code terminal emulation or Windows.
I just tested in Linux and it works as expected.
Test code:
<?php // ./routes/console.php

use Illuminate\Support\Facades\Artisan;

Artisan::command('app:test', function () {
    $user = $this->ask('áêìöu');
    $this->info($user);
    $this->info('áêìöu');
    dd('áêìöu');
});

Output:
$ php artisan app:test

 áêìöu:
 > áêìöu

áêìöu
áêìöu
"áêìöu"

Might be something related to Mingw64, Laragon, Visual Studio Code terminal emulation or Windows.
I just tested in Linux and it works as expected.
Test code:
<?php // ./routes/console.php

use Illuminate\Support\Facades\Artisan;

Artisan::command('app:test', function () {
    $user = $this->ask('áêìöu');
    $this->info($user);
    $this->info('áêìöu');
    dd('áêìöu');
});

Output:
$ php artisan app:test

 áêìöu:
 > áêìöu

áêìöu
áêìöu
"áêìöu"

I know It Works on Linux, but its Common issue i think.., many people uses laravel on windows

I know It Works on Linux, but its Common issue i think.., many people uses laravel on windows

But did you try directly on the windows terminal (Command Prompt/PowerShell), not inside a virtual environment such as Laragon or Mingwin?
Install PHP directly on windows and test with a clean installation to see if the error happens outside of these emulation layers. If you want to emulate a *nix environment try using WSL2.
At least, did you test on an official Laravel developement environment, such as Homestead?
It would be hard to support every development or deployment environment combination when multiple configuration factors can interfere in the outcome.

But did you try directly on the windows terminal (Command Prompt/PowerShell), not inside a virtual environment such as Laragon or Mingwin?
Install PHP directly on windows and test with a clean installation to see if the error happens outside of these emulation layers. If you want to emulate a *nix environment try using WSL2.
At least, did you test on an official Laravel developement environment, such as Homestead?
It would be hard to support every development or deployment environment combination when multiple configuration factors can interfere in the outcome.

I did some testing on a virtual machine I have with windows and it fails.
To fix it you can set your php.ini's output_encoding variable to "UTF-8". By default it is empty.
output_encoding = "UTF-8"

Before setting output_encoding variable:

After setting output_encoding variable:

To find where your php.ini file is located run this command:
php -i | findstr "Configuration"

And check the path in the Loaded Configuration File line.
If you can't change the php.ini file, you can set at runtime by calling ini_set(...)
ini_set('output_encoding', 'UTF-8');

For example, in my sample command, it would become:
<?php // ./routes/console.php

use Illuminate\Support\Facades\Artisan;

Artisan::command('app:test', function () {
    ini_set('output_encoding', 'UTF-8');

    $user = $this->ask('áêìöu');
    $this->info($user);
    $this->info('áêìöu');
    dd('áêìöu');
});

If you want this to be run for every file you can add it to your AppServiceProvider file inside its boot(...) method.
Hope this helps.

I did some testing on a virtual machine I have with windows and it fails.
To fix it you can set your php.ini's output_encoding variable to "UTF-8". By default it is empty.
output_encoding = "UTF-8"

Before setting output_encoding variable:

After setting output_encoding variable:

To find where your php.ini file is located run this command:
php -i | findstr "Configuration"

And check the path in the Loaded Configuration File line.
If you can't change the php.ini file, you can set at runtime by calling ini_set(...)
ini_set('output_encoding', 'UTF-8');

For example, in my sample command, it would become:
<?php // ./routes/console.php

use Illuminate\Support\Facades\Artisan;

Artisan::command('app:test', function () {
    ini_set('output_encoding', 'UTF-8');

    $user = $this->ask('áêìöu');
    $this->info($user);
    $this->info('áêìöu');
    dd('áêìöu');
});

If you want this to be run for every file you can add it to your AppServiceProvider file inside its boot(...) method.
Hope this helps.

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


warn_error_options, warn_error mutual exclusivity with click

resolves #6579

Description

Checklist

[ ] I have read the contributing guide and understand what's expected of me
[ ] I have signed the CLA
[ ] I have run this code in development and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
[ ] I have run changie new to create a changelog entry

closing in favor of: https://github.com/dbt-labs/dbt-core/pull/6771


Lack of Corgi block and all hints are wrong on tutorial Simple Extensions in Chinese

Describe the bug
Lack of Corgi block and all hints are wrong on tutorial Simple Extensions in Chinese
Steps to reproduce the behavior
1.Navigate to https://arcade.makecode.com/beta#
2.Switch to Chinese language
3.Tutorials---->Simple Extensions---->Start Tutorial
4.Click the hint
Expect behavior
There should add the Corgi block and all hints are right.
Actual behavior
Lack of Corgi block and all hints are wrong on tutorial Simple Extensions in Chinese

Additional context
1.OS: Windows(rs6)
2.arcade version: 0.18.7
3.Microsoft MakeCode version: 6.1.22

fixed in translation: https://crowdin.com/translate/kindscript/3803/en-zhcn


Feature request: CRT GEOM OpenGL shader

As GDash supports OpenGL shaders, one of the best shaders for CRT simulation called CRT GEOM (deluxe) would be nice to have as an additional shader effect. Would perfectly fit for retro C64 game!
Tried this one:
https://github.com/libretro/glsl-shaders/blob/master/crt/shaders/crt-geom.glsl
Is shown in the options after renaming to .shader but does not do anything.

Looks like that GDash only supports XML shaders:
https://docs.libretro.com/development/shader/xml-shaders/
I'm not sure how to convert the *.glsl format to XML, if this is possible at all.
So I tried to hack the GDash code to load a GLSL shader. I could manage to load everything without error, but I don't see an effect... As I have no experience with shaders, I guess there is something missing.
So far I did:

Add code from this example: https://moderncprogramming.com/loading-a-glsl-shader-from-file-in-opengl-using-pure-c/
Modify crt-geom.glsl:

Comment #pragma's, otherwise syntax error
Split into two parts (vertex/fragment) and load separetely
Rename lum to lum1 in saturation(), otherwise syntax error

So probably this ends with "help wanted"...

New approach: I found a XML version of the shader here:
https://github.com/alunbestor/Boxer/blob/master/Resources/Shaders/crt-geom-interlaced-curved.shader
Modified for GDash: add version, disable CURVATURE, add interlace_detect
Start GDash with -v so that you can see why a shader does not get compiled.
If you need more shader log info I could add it, but the additional output is just "compile failed" or "main() not found".
(This requires to add glGetProgramInfoLog, glGetShaderiv and glGetProgramiv)
Please tell me if this does the job, so I can close the issue.

I found shaders that are working with GDash, too:
https://github.com/guestrr/FS-UAE-Shaders/tree/master
Not all are working but these are (and have nice effects):
crt-caligari
crt-cgwg
crt-trinitron
crt-trinitron2
xbrz4x
xbrz6x

Is this already modified for GDash or do you still have to do that?

It's already modified, although the original file already worked. I guess, I'll revert to the original. Maybe then it's easier to import a new version of the shader.


Slate state when HttpClient reconnects

When a connection is interrupted, the ping thread marks the RedisHost as unavailable. But, when the connection is restored, it does not update the Available property. It seems that the AsyncTcpClient recovers itself, marking the client as Connected, but the Available property is not updated.
Note that the TcpClient will have the IsConnected property as true, but the Available property will remain as false
https://github.com/beetlex-io/BeetleX.Redis/blob/df7fcaff52a012b783f6583327ab788af27e2756/src/RedisHost.cs#L94-L126
Steps to reproduce:

Host a local redis server
Make a call (in my case, from an asp.net core controller), e.g. INFO. Everything works as expected.
Now, shutdown the Redis instance
Make the call again. It should throw an exception and the host marked as Available = false
Start the Redis server again.
Make the same call (aspnet server should not be rebooted).
Exception is thrown as redis server is not available

The AsyncTcpClient changes to a Connected state, but the Available property is still false.
Changing the property before returning solved the issue for me:
this.Available = true;
return new Result { ResultType = ResultType.Simple, Messge = "Connected" };

I think the cause is the parallel Ping from ReadHosts and WriteHosts.
Both will call Connect method, but one that fails may flag the mConnected field as false, while the second thread has set as true.
https://github.com/beetlex-io/BeetleX/blob/ce6f9d91394dbed5f28a66b9efbd9a87f9d32e23/src/BeetleX/Clients/Clients.cs#L1019-L1105

thanks


Failed to parse response body.

I have the same problem.  Nothing helps. I've tried to set all the cookies instead of the "_U" cookie in the settings.js, doesn't help. All worked well 3-4 days ago, but now I always get this error. Can someone give any advice please?

if you are Chinese
you can try to
删掉BingAIClient.js 中的 'x-forwarded-for' 部分或将这一行注释
然后配置好代理

So it seems like /turing/conversation/create doesn't work anymore. What's also weird is /turing/conversation/create is to create a new conversation and I get this error on existing conversations.

I would suggest either removing the config cookies key/value entirely or set your entire cookies string, not just the _U cookie. If your IP isn't blocked by Bing, that should resolve this issue.

I did that, same issue. The issue is that turing/conversation/create is no longer a valid path. Please update the code.

I was wrong! I was able to modify the code and use cookies instead of just a token and it worked!

You don't need to modify the code. It supports setting your cookies instead of just a token already.

I was wrong! I was able to modify the code and use cookies instead of just a token and it worked!

How did you do that? I think I've done it from the very beginning, but it didn't help.
So I take all the cookies here

Add it to my  settings.js

And I get this error on my server:

And this one as a response to my request:
{"error":"Cannot convert argument to a ByteString because the character at index 2667 has a value of 1042 which is greater than 255."}

I am using chatgpt-clone which uses this as a dependency. So I am not sure how to do it for yours.

And I get this error on my server:
@gengituser you probably copy-pasted it manually by selecting the text right? You need to right-click and select the Copy option from the menu instead, as the visible text is truncated in the middle using a special "..." unicode character.

And I get this error on my server:

@gengituser you probably copy-pasted it manually by selecting the text right? You need to right-click and select the Copy option from the menu instead, as the visible text is truncated in the middle using a special "..." unicode character.

I just found a solution thanks to another discussion here: https://github.com/waylaidwanderer/node-chatgpt-api/issues/302
The issue was that I'm not from the English speaking country and my name contains non-English characters. That's why within my cookies there were non-English characters. I just went into my Microsoft account settings and rewrote my name in English. Then I re-logged into Bing search and copied the new cookies. After that, everything worked! )


Investigate modifying ethereum-js/monorepo into a bedrock client

This would be tough.  Better path is wasmify opreth


MAINTAINER deprecated

The MAINTAINER instruction is deprecated:

https://docs.docker.com/engine/reference/builder/#/maintainer-deprecated

Consider implementing a warning with suggestion to replace with LABEL maintainer.

Looks like this was solved in #69

@jadametz
Confirmed - just ran whatever the latest is:
Line 4: MAINTAINER<EMAIL_ADDRESS>Issue  Category      Title                 Description
    1  Deprecation   Deprecated as of      This INSTRUCTION is deprecated as of Docker 1.13
                     Docker 1.13

This can be closed.

Thanks everyone! Not sure why this was left open, closing now.

I added a MAINTAINER line to the www.fromlatest.io example and it didn't complain


Trying to add a disposable to a DisposableStore that has already been disposed of. The added object will be leaked!

lifecycle.js:319 Error: Trying to add a disposable to a DisposableStore that has already been disposed of. The added object will be leaked!
    at DisposableStore.add (lifecycle.js:319:30)
    at EditorHoverStatusBar._register (lifecycle.js:382:28)
    at EditorHoverStatusBar.addAction (contentHoverStatusBar.js:40:14)
    at markerHoverParticipant.js:213:35

/duplicate
https://github.com/microsoft/vscode/issues/221455


lp error message when the configured default printer isn't available could be clearer

As highlighted by martin in https://bugs.debian.org/870463 where the default printer as configured in ~/.cups/lpoptions was not available anymore; they were getting:

lp: Error - no default destination available.

but the error message could be improved to read:

Invalid default destination specified in config file: mfc9465cdn

or something along these lines.

I don't know how far we want to go with this, but holding for 2.3.x.

[master d6db9ea1d] The lp and lpr commands now provide better error messages when the default printer cannot be found (Issue #5096)


chore(protocol): update Alpha-3 protocol configurations

Questions to discuss:

[x] What average block time will we use / assume for A3? (3 seconds?) => 3s seems to be reasonable
[x] Shall we change minEthDepositAmount to 0.1 ETHs?  (some concerns here) => should be fine
[x] Do we need to increase the cooldown period for A3 network? (proofCooldownPeriod + systemProofCooldownPeriod) => if Sepolia generally work well and we're confident we can get these overwrite transactions in fast enough then seems ok.
[x] Do we need to change realProofSkipSize? (i think it depends on the avg block time that we predict) => start with realProofSkipSize: 10 for the initial wave, we can reconsider afterwards
[x] What treasury address will we use? => 0xdf09A0afD09a63fb04ab3573922437e1e637dE8b
[x] What INITIAL_PROOF_TIME_TARGET will we use? (in current internal devnet, avg proof submission time is ~80s, so shall we use 120s? if we use 120s, then initProofTimeIssued will be 49883) => 2 * 80 (avg proof submission time) = 160
[x] What param1559.gasIssuedPerSecond will we use? (i think it depends on the avg block time that we predict) => param1559.gasIssuedPerSecond := 2,000,000 gas/s == 4 L2 blocks of 6M gas/L1 block
[x] Shall we change param1559.yscale / param1559.xscale / param1559.gasExcess? => lets calculate them in TaikoL2's init() function
[x] Shall we make sure state.blockFee always >=1? (to prevent proposing becomes "totally free"?) => If the proposing EIP-1559 parameters are set well, seems this will be unnecessary (could be a big IF)

Maybe we should do minEthDepositsPerBlock: 1? Feels like that could be a big UX improvement.
I think smart to start with  realProofSkipSize: 10 for the initial wave, we can reconsider afterwards.
Regardless of the value of minEthDepositAmount, I think there's definitely spam risk on this queue. Anybody with a lot of ETH can make the queue extremely long and we can only process a couple/block, so users may have to wait a long time to get their ETH deposit if abused.
INITIAL_PROOF_TIME_TARGET = 80s * 2
prover fee adjustmentQuotient = TBD
param1559.gasIssuedPerSecond := 2,000,000 gas/s == 4 L2 blocks of 6M gas/L1 block. Seems reasonable to me and is the proposed 3s block times. Other values:

struct EIP1559Params {
        basefee = ? (could just be 0 to start);
        gasIssuedPerSecond = 2000000;
        gasExcessMax = ?;
        gasTarget = 2000000 * 12;
        ratio2x1x = 11250;
    }

Unfortunately not so easy to find all the correct values here. Something like https://github.com/taikoxyz/taiko-mono/blob/main/packages/protocol/script/DetermineNewProofTimeIssued.s.sol + some input parameter simplification https://github.com/taikoxyz/taiko-mono/issues/13556 like with the proving fee would certainly help to make this easier to configure!

Update the configs based on PR feedbacks: https://github.com/taikoxyz/taiko-mono/pull/13806/commits/1f6eed59db8e90e4554c539c5cb9a727b4453bc3 , plz review

Have we seen the proposal basefee work within reasonable ranges on our internal testnet?

In current internal devnet, all provers will at least wait proofTargetTime before submission, but right now the baseFee is still 0, and i think @adaki2004 is working on tuning the parameters.

Ah yeah I heard about that!
It looks like how I name things is a bit confusing, what about the L2 basefee that the proposer pays on L2? That one also depends on proposing blocks at fixed intervals (same as with the proofs) to keep the basefee steady. So was wondering if the behavior there was as expected and we can for sure push that L2 basefee pretty high in a small amount of time (we need that high L2 basefee to prevent spam).

@davidtaikocha @Brechtpd @adaki2004 Do you think we should get onto a call to quickly resolve this issue?

@davidtaikocha @Brechtpd @adaki2004 Do you think we should get onto a call to quickly resolve this issue?

after upgrade the proxy implementation and use Dani's new params:
ProofTimeTarget: 150
ProofTimeIssued: 162263074
BlockFee: 1e8 ( 1 TKO was set so far so i guess we stick to it.. if you disagree i need to recalculate the proofTimeIssued)
AdjustmentQuotient: 32000

seems the fee backs to stable again. and before that, our client sometimes will submit the proofs asap, and zkpool's client also always submits proof asap, i think this is also part of the reason.

@davidtaikocha @Brechtpd @adaki2004 Do you think we should get onto a call to quickly resolve this issue?

And im ok for a call to the final overall checking of this PR.

#13483

Duplicate of #

update-alpha-3-configs


Saving GDF with columnar metadata

columnar metadata is critical for keeping track of things like units, sources, timestamp exc..
Is there a GDF.write method that supports writing/reading of table metadata?

At the moment no. Afaik GDAL doesn't have a concept of columnar metadata and the only (geo)spatial format that does is Arrow. Even then, with metadata you might be restricted to Strings only.
In Julia we have columnar metadata support on DataFrames and we could make a geospatial vector type that also stores it.

we could make a geospatial vector type

Is this a big lift and how would it work?

Depends on how much functionality we put in. Think of it as a wrapper, or a wrapper with a spatial index a la geoacceleratedarrays. It seems less work than a GeoDataFrame type.


Possibility to link to a specific shade

Would be very helpful to be able to link to a specific shade "setup". Just need 4 parameters really: The color, the two steps, and the name of the color.
Something like this:
https://www.tailwindshades.com/?color=4B207F&up=15&down=5&name=foobar

Would be really nice when collaborating with others, as well as for documenting where the shade "setup" came from so it's possible to go back and re-adjust.

That's a nice idea! Let me see if we can constantly change the URL parameters as we move the sliders, without any unintended consequences. Otherwise, a button to copy this "share" link can be added

A share link is probably good to have either way. I've experienced some issues with the typescript playground "auto url" not always being up-to-date, which is kind of annoying, so having an explicit "give me a URL for the current state"-button is great.
If you do make the URL parameters change, maybe you can use replace rather than push, to not create a browser history horribly long. Or maybe a combination somehow. Not sure what's best. Should most definitely be debounced/throttled somehow though.

Yes from a very short research I found that a hashtag replace might work better but will stick to the button if it becomes too involved, I mean the upside of being able to copy the URL at anytime is small to begin with.

Simple is usually good. Easier to maintain, easier to deal with. 👍

Just tested out, and it works great! 🙏


Get Aaron, Gill, Johannes, (Alex?) to label set independently

Write a guidelines document and have a standardized dataset, truly random subset- of all sentences which have a G or P
Update mindtagger first to have "interesting", "association", "causal" tags

Pay attention here: The Gene-Pheno extractor still only takes canonical gene names! Before we pull out a random subset from genepheno_relations, maybe update to ALL possible gene names (canonical, noncanonical, RefSeq and Ensembl if I remember correctly)


Right click not working (v1.8)

After installing shell (v1.8) , I have to restart the File Explorer process for right click to work . Also , in this new version how to remove the shadow animation.

To disable  shadow, go to theme section in shell.nss file and write the following code
shadow.enabled=false

save file, hold shift+right-click to reload or restart explorer.

1.8 seems to be broken on Windows 10.  As detailed here
"Open /imports/terminal.nss file in Shell folder, then replace the title property value from title.terminal to id.terminal.title, save the file and restart file explorer".
I also adjusted the Windows Terminal line
from:
item(where=sys.ver.major >= 10 title=title.Windows_Terminal admin=key.shift() image='@package.path("WindowsTerminal")\WindowsTerminal.exe' cmd='wt.exe' arg='-d<EMAIL_ADDRESS>to:
item(where=sys.ver.major >= 10 title='@appx.name("WindowsTerminal")@elevated' admin=key.shift() image='@package.path("WindowsTerminal")\WindowsTerminal.exe' cmd='wt.exe' arg='-d<EMAIL_ADDRESS>

@Aman1337g I had the same problem, and I think it had to do with several instances of Shell being installed and conflicting with each other.
I originally installed it via the installer; one day I updated via winget. I think that's when the problem you describe began for me. I tried uninstalling with the Windows Uninstall feature in the Control Panel as well as the uninstaller it comes with. The problem persisted.
What I did is a search of all related files on my system and deleted  them all. No trace of Shell left. Reinstalled it, rebooted the system and the right-click is back to functional right away without the need of restarting the explorer.

@Aman1337g I had the same problem, and I think it had to do with several instances of Shell being installed and conflicting with each other.
I originally installed it via the installer; one day I updated via winget. I think that's when the problem you describe began for me. I tried uninstalling with the Windows Uninstall feature in the Control Panel as well as the uninstaller it comes with. The problem persisted.
What I did is a search of all related files on my system and deleted them all. No trace of Shell left. Reinstalled it, rebooted the system and the right-click is back to functional right away without the need of restarting the explorer.

Thanks @r-katabasis the problem is now fixed.


Error running "npm install && npm run test  "

What happened:
Trying to install module and run tests:
npm install && npm run test

up to date, audited 154 packages in 512ms

found 0 vulnerabilities

><EMAIL_ADDRESS>test
> npm run tsc && jasmine --config=./spec/support/jasmine.json

><EMAIL_ADDRESS>tsc
> tsc

src/model/workflow.ts:27:23 - error TS2307: Cannot find module '../../../sdk-ts-generator/src/workflow' or its corresponding type declarations.

27 import {Crondef} from '../../../sdk-ts-generator/src/workflow';
                         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Found 1 error.

npm ERR! code 2
npm ERR! path /Users/tsurdilovic/devel/serverlessworkflow/sdk-typescript
npm ERR! command failed
npm ERR! command sh -c tsc

npm ERR!      /Users/tsurdilovic/.npm/_logs/2021-04-24T15_11_47_758Z-debug.log
npm ERR! code 2
npm ERR! path /Users/tsurdilovic/devel/serverlessworkflow/sdk-typescript
npm ERR! command failed
npm ERR! command sh -c npm run tsc && jasmine --config=./spec/support/jasmine.json

npm ERR!      /Users/tsurdilovic/.npm/_logs/2021-04-24T15_11_47_800Z-debug.log

What you expected to happen:
tests run ok
How to reproduce it:
clone the project as shown in readme
execute
npm install && npm run test
Anything else we need to know?:
Environment:

npm version 7.6.3

@antmendoza probably related to https://github.com/serverlessworkflow/sdk-typescript/pull/50 :)
we need to merge that

yes @tsurdilo  my mistake, sorry. This import was there from the beginning.


firefly-iii: fixes creation of vendor directory

This allows the package to work properly. Also partially fixes https://github.com/NixOS/nixpkgs/issues/342285
Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Way ahead of you :) https://github.com/NixOS/nixpkgs/pull/342556

Fixed by https://github.com/NixOS/nixpkgs/pull/343900


PBID-102: Default to filtering (prevent activation) when timezone cannot be determined and a config is defined

This PR just adds a test to verify that the existing implementation behaves as we thought it should.

@victorigualada this seems to be failing with browserstack.  Any idea why?

@victorigualada this seems to be failing with browserstack. Any idea why?

I think that the project is not activated in CircleCI so it can't run the tests at all.


Clean up some more Python 2-isms

Reword and simplify a few docstrings.
Add back a test for 2-arg super() in property() definitions that
was (accidentally?) dropped in #936.

Thanks, that super thing was pyupgrade. Fortunately the other super call is also in test_slots that I've blocked in pre-commit.


[Event Request] Codeunit 90 new event on procedure InsertReceiptLine

Hi,
I requested the adding of a publisher in the InsertReceiptLine function (issue 17885).
The publisher has been added in the BaseApp version 20.1.39764.41543 but the parameter PurchRcptLine is missing  :
        IsHandled := false;
        OnInsertReceiptLineOnBeforeProcessWhseShptRcpt(PurchLine, IsHandled, CostBaseAmount, PurchRcptLine);
        if not IsHandled then
            if (PurchLine.Type = PurchLine.Type::Item) and (PurchLine."Qty. to Receive" <> 0) then begin
                ShouldGetWhseRcptLine := WhseReceive and PurchLine.IsInventoriableItem();
                >
                OnInsertReceiptLineOnAfterCalcShouldGetWhseRcptLine(PurchRcptHeader, PurchLine, PostedWhseRcptHeader, WhseRcptHeader, CostBaseAmount, WhseReceive, WhseShip, ShouldGetWhseRcptLine);
                <
                if ShouldGetWhseRcptLine then

Could you add this parameter ?

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


Exception while running workitem

@adamenagy  {"The server returned the non-success status code 403 (Forbidden).\nMore error details:\n"User= cannot access a resource owned by Owner=AdamNagy."."}
How to resolve this?

I added a new environment variable for FORGE_NICKNAME that you'll have to set. More info in the readme:
https://github.com/adamenagy/QuickerAssemblerDA#running


How could I use this linter with golangci-lint?

I can't find this project by name in the golangci linter list: https://golangci-lint.run/usage/linters/.
But in the commit message, I found upgrade information about supports golangci-lint.
Could you tell me how to use this linter? Thank you.

Hi!
There is a make target to install the linter as a plugin, as this linter is not (yet) integrated in golangci-lint.
When you've installed the plugin you can add it to your .golangci.yml
linters-settings:
 custom:
   proto-golint:
     path: /Users/iwittkau/go/bin/proto-golint-plugin.so
     description: report direct access to proto message fields when getters can be used
     original-url: github.com/iwittkau/proto-golint
linters:
  enable:
    - proto-golint

… adapt it with the path to the plugin on your machine. The make target will put out the path where the plugin was copied to ($GOPATH/bin/proto-golint-plugin.so).
The reason why I need to update the dependencies regularly is due to the fact that this linter is compiled outside of golangci-lint and not imported by their code directly. The versions of the shared dependencies must exactly match those also imported by golangci-lint.

I successfully used this tool in my project. It's very cool. Thanks for your guidance!


bootstrap-calendar not working in a flask project

It is not an issue but a question. I am trying to use this calendar into my flask application, however the html file is running fine in isolation, but when I try to call this file from flask app it is not working. I cannot see the calendar. I can only see the bootstrap buttons of year month day and next previous etc. I also tried to call the java-script files according to flask's way of calling static files, but it also did not work. Any suggestions would be very appreciated.

I will tell you from my experience, because you have to figure out how the calendar works. Don't know anything about flask, but know that you must have mixed the order of the js files loading. They must be in order

****

Not sure if you've included bootstrap.js file, which basically is not included in the basic docs of this repository. At least that helped me.

Hi dandruff, thank you for your reply. As far as I understood, From somewhere inside the calendar code it is calling files from tmpls and it is requesting for a wrong path. For example Flask only allow you to get files from a static folder if a request comes for another folder Flask does not allow accessing that file. Now what is happening all the files (js) files have been loaded but from somewhere inside the code it is requesting for tmpls 'month.html' file. I am getting the following error in my console of browser
jquery.min.js:4GET http://<IP_ADDRESS>:5000/verifyDomain/tmpls/month.html?_=1463436714276 404 (NOT FOUND)
Actually my static path is
http://<IP_ADDRESS>:5000/pdf/tmpls/month.html
Now I do not know how to change the tmpls path as the second one. If you have any idea of the code. Please tell me so.
As far as bootstrap is concerned I can see bootstrap styles in the form of buttons into my html. So I believe it is loading the bootstrap.

So in the beginning you set the default options for the calendar. They are often as follows:
var options = {
        events_source: '/events', //in this case url, but can put array or object for test cases
        view: 'month',
        tmpl_path: 'tmpls/',
        tmpl_cache: false,
        day: '2016-05-18'
        ....
}

Try to play with  tmpl_path variable. Depending on the framework and language you use the application searches for the templates, sending also the timestamp in microseconds for the moment of the request (in your case<PHONE_NUMBER>276 / delete 276 and you get 05/16/2016 10:11pm (UTC)). I had to put tmpls folder in the root folder, some software would look in the folder where calendar.js is placed, rarely where your framework or language would search for. Also, try using Firefox instead of Chrome, which will allow your local files to load. Once on a server browsers will work the same way.
These are just some suggestions that you can try. Bootstrap JS (not CSS) has little or nothing to do with you buttons by the way, but is used for the calendar.

You need to set tmpl_path: '/pdf/tmpls/'

Hi guys,
thank you so much I am able to use this calendar with your help in flask. I changed tmpl_path: '/pdf/tmpls/'  in calendar.js and app.js file. Also I set  events_source: '/pdf/events.json.php', in app.js file. My html file looks as follow for someone else trying to use flask.
<link rel="stylesheet" href="/pdf/components/bootstrap2/css/bootstrap.css">
	<link rel="stylesheet" href="/pdf/components/bootstrap2/css/bootstrap-responsive.css">
	<link rel="stylesheet" href="/pdf/css/calendar.css">

				<button class="btn btn-primary" data-calendar-nav="prev"><< Prev</button>
				<button class="btn" data-calendar-nav="today">Today</button>
				<button class="btn btn-primary" data-calendar-nav="next">Next >></button>

				<button class="btn btn-warning" data-calendar-view="year">Year</button>
				<button class="btn btn-warning active" data-calendar-view="month">Month</button>
				<button class="btn btn-warning" data-calendar-view="week">Week</button>
				<button class="btn btn-warning" data-calendar-view="day">Day</button>


Split "mentat transaction" logic into its own crate

Splitting some more "pre" work from #563.
Paraphrased from the discussion in that PR:
Splitting high level metadata logic away from the top level is needed in some form to enable nicer patterns for the internal consumers (well, just tolstoy for now). Further refactoring of this logic should be easier from this point on, and the consumers building on top of the transaction crate won't be affected significantly - likely just a few import changes.
As it stands, transaction right now is a thin layer on top of db, doing some bookkeeping one layer above it. I'm not a fan of having Store and Conn at the top level, either - it makes writing tests that want to use a real Conn awkward, forcing them to be at the top level, away from the functionality that's being tested. The TestConn surrogate is a smell of that. So, there's like more re-shuffling to be done! My hope is that little steps like this will help inform us what the "ideal" world might look like.

Carrying over r+ from @ncalexan in #563.


Update *.domain.tld as well as @.domain.tld

Gandi supports wildcard * subdomains, but they should be updated as well as the @. I hacked the script to achieve that for me, but a clean implementation should be devised…
Given that the configuration form in DSM validates the hostname a little strictly, and that there is no other setting (I wouldn't abuse the username field for that), maybe make two versions of the script?

You can make a PR as is and we discuss it as a review.

Thanks for the RP. Do you have a link to the documentation related to *. TO me it unclear what it actually does. and what is the difference to @.

Here's a passage in the docs: https://docs.gandi.net/en/domain_names/faq/record_types/a_record.html#what-are-wildcard-a-records. So @ means no subdomain, and * means any subdomain. Reading this, I realize that I don't rely on dynamic subdomains other than by laziness, so I'll probably/eventually set up a proper zone update script for when I add/remove a vhost…

Ok, obviously '@' and '*' are different usecases. Thus the proposed change is wrong.
Is the handling onf wildcard records makes sense is a different question.

New version, untested because I currently don't have access to my NAS.
The idea is either you use it as previously by giving foo.example.tld in DSM, or just example.tld in which case the @.example.tld. A record will be updated.
Or, by writing a wrapper script that passes additional arguments at the end, you can update explicit hosts, including the special @ and *:
/bin/bash
./livedns.py "$@" foo bar @ '*'

What do you think?


Can we assume all manifests and indexes are always pushed using the /manifests API in case of multiarch images?

Assuming we have a "root" index containing multiple manifest references (of media type manifest, in a more practical example a multi-arch image).
What is the proper way to upload the image metadata?
A) All the files containing manifests are pushed using the /manifests API, and the index is pushed afterwards using the same API.
B) Just the "root" index is pushed using the /manifests API, after all the other files have been pushed using the /blobs API.
In both cases the "root" index would be valid, because all references have previously been pushed, and can be identified server-side using their respective digests regardless of which API was used to push.
There are implications in following calls to pull or delete manifests, if for example the manifest was pushed using the /blobs API, not the /manifests API, the server is not aware that file is a manifest, so it can't be exposed to be downloaded/deleted using the /manifests API. They would only be available through the /blobs API.
On server side implementation, can we assume all the clients use either A) or B)?

I am used to see A), but apparently B) also exists... Therefore I would tend to consider A) the proper way.

I wonder if there is a reason why manifests cannot be handled as blobs at will. That way A), B) and even a combination of both would be possible.
Is it the root of the artifact? Then handle it as a manifest and manage it with the /manifests endpoints.
It isn't? Then handle it as a blob and manage it with the /blobs endpoints.
Manifests uploaded over the /blobs endpoints can be promoted anytime to /manifests.
That way you would not need to differentiate between A and B.

I think this might be one of those cases where the spec talks about/implies garbage collection slash the DAG, but doesn't explicitly say it.  Without having an unambiguous way to identify "an object that might have children" it's hard to implement validation or garbage collection in a sane way that doesn't involve heuristics.

I suspect, given the way content addressable stores work, that some registries may allow a manifest to be pulled as a blob. However, the reverse would be less likely since registries track manifests for GC and media type headers.
My individual opinion is that manifests and blobs may be treated separately by registries, and every entry in an index should be a manifest that is only accessed via the manifest API. While some tools could be written that understand their content is accessed using the blob API, that would break more generic tooling that inspects, ingests, scans, and transports the content. Also a manifest listed in an index may be its own independent object, pulled directly, without going through the index, or it may be listed in multiple indexes, so I have a hard time calling any one index or image manifest the "root".
I am aware that exceptions to this that have occurred in the past, but I consider that a bug. Support for a buggy implementation is a decision for the individual registries and tooling, and not something OCI should be pushing. E.g. I wouldn't want an OCI conformance test to check if a registry allows an index containing references to content pushed to the blob API.

I believe everyone agreed on A). Do we need a spec update? I am ok with closing this issue.

Do we need a spec update?

I believe since image-spec says that the entries must be a manifest, and distribution-spec only specifies a single way to push manifests, we're okay without a spec change (at least we leaned on that when this issue came up in the past). If there's misleading wording, or a clarifying statement that you want to fix, feel free to raise a PR and we'll review it.

I am ok with closing this issue.

Thanks. I was leaving it open in case you didn't feel it was answered or there were other maintainers that wanted to weigh in. I'll close this out but feel free to keep the conversation going here.


Latest Vision API throws MissingMethodException  for all calls.

In my code that calls the Vision API, I upgraded the Vision API version number from 1.4 to 1.5:
https://github.com/GoogleCloudPlatform/dotnet-docs-samples/pull/839/files
And now all the API calls fail with the same mysterious exception:
[xUnit.net 00:00:01.81]       System.TypeInitializationException : The type initializer for 'Google.Cloud.Vision.V1.ImageAnnotator' threw an exception.
[xUnit.net 00:00:01.81]       ---- System.TypeInitializationException : The type initializer for 'Google.Cloud.Vision.V1.BatchAnnotateFilesRequest' threw an exception.
[xUnit.net 00:00:01.81]       -------- System.TypeInitializationException : The type initializer for 'Google.Cloud.Vision.V1.AnnotateFileRequest' threw an exception.
[xUnit.net 00:00:01.81]       ------------ System.MissingMethodException : Method not found: 'Google.Protobuf.FieldCodec`1<Int32> Google.Protobuf.FieldCodec.ForInt32(UInt32)'.
[xUnit.net 00:00:01.81]       Stack Trace:
[xUnit.net 00:00:01.81]         T:\src\github\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Vision.V1\Google.Cloud.Vision.V1\ImageAnnotatorGrpc.cs(190,0): at Google.Cloud.Vision.V1.ImageAnnotator.ImageAnnotatorClient.BatchAnnotateImages(BatchAnnotateImagesRequest request, CallOptions options)
[xUnit.net 00:00:01.81]         T:\src\github\gax-dotnet\releasebuild\Google.Api.Gax.Grpc\ApiCall.cs(92,0): at Google.Api.Gax.Grpc.ApiCall.GrpcCallAdapter`2.CallSync(TRequest request, CallSettings callSettings)
[xUnit.net 00:00:01.81]         T:\src\github\gax-dotnet\releasebuild\Google.Api.Gax.Grpc\ApiCallRetryExtensions.cs(84,0): at Google.Api.Gax.Grpc.ApiCallRetryExtensions.<>c__DisplayClass1_0`2.<WithRetry>b__0(TRequest request, CallSettings callSettings)
[xUnit.net 00:00:01.81]         T:\src\github\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Vision.V1\Google.Cloud.Vision.V1\ImageAnnotatorClientPartial.cs(446,0): at Google.Cloud.Vision.V1.ImageAnnotatorClient.Annotate(AnnotateImageRequest request, CallSettings settings)
[xUnit.net 00:00:01.81]         T:\src\github\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Vision.V1\Google.Cloud.Vision.V1\ImageAnnotatorClientPartial.cs(504,0): at Google.Cloud.Vision.V1.ImageAnnotatorClient.AnnotateSingleFeatureType[T](Type featureType, Func`2 annotationExtractor, Image image, ImageContext context, Int32 maxResults, CallSettings callSettings)
[xUnit.net 00:00:01.81]         T:\src\github\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Vision.V1\Google.Cloud.Vision.V1\ImageAnnotatorClientPartial.cs(43,0): at Google.Cloud.Vision.V1.ImageAnnotatorClient.DetectFaces(Image image, ImageContext context, Int32 maxResults, CallSettings callSettings)
[xUnit.net 00:00:01.81]         C:\Users\rennie\gitrepos\dotnet-docs-samples\vision\api\DetectFaces\DetectFaces.cs(44,0): at GoogleCloudSamples.DetectFaces.Main(String[] args)
[xUnit.net 00:00:01.81]         C:\Users\rennie\gitrepos\dotnet-docs-samples\testutil\TestUtil.cs(137,0): at GoogleCloudSamples.CommandLineRunner.Run(String[] arguments)
[xUnit.net 00:00:01.81]         C:\Users\rennie\gitrepos\dotnet-docs-samples\vision\api\VisionTest\VisionTest.cs(60,0): at GoogleCloudSamples.TutorialTests.TestFacesWithFace()
[xUnit.net 00:00:01.81]         ----- Inner Stack Trace -----
[xUnit.net 00:00:01.81]         T:\src\github\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Vision.V1\Google.Cloud.Vision.V1\ImageAnnotator.cs(6270,0): at Google.Cloud.Vision.V1.BatchAnnotateFilesRequest.get_Parser()
[xUnit.net 00:00:01.81]         T:\src\github\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Vision.V1\Google.Cloud.Vision.V1\ImageAnnotatorGrpc.cs(38,0): at Google.Cloud.Vision.V1.ImageAnnotator..cctor()
[xUnit.net 00:00:01.81]         ----- Inner Stack Trace -----
[xUnit.net 00:00:01.81]         T:\src\github\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Vision.V1\Google.Cloud.Vision.V1\ImageAnnotator.cs(6032,0): at Google.Cloud.Vision.V1.AnnotateFileRequest.get_Parser()
[xUnit.net 00:00:01.81]         T:\src\github\google-cloud-dotnet\releasebuild\apis\Google.Cloud.Vision.V1\Google.Cloud.Vision.V1\ImageAnnotator.cs(6302,0): at Google.Cloud.Vision.V1.BatchAnnotateFilesRequest..cctor()
[xUnit.net 00:00:01.81]         ----- Inner Stack Trace -----
[xUnit.net 00:00:01.81]            at Google.Cloud.Vision.V1.AnnotateFileRequest..cctor()
[xUnit.net 00:00:01.82]   Finished:    VisionTest
----- Test Execution Summary -----

Ouch. That sounds like Google.Protobuf made an incompatible change :( Will investigate ASAP

Okay, there was definitely a breaking change in Google.Protobuf, as I've reported here: https://github.com/protocolbuffers/protobuf/issues/6379
But that doesn't fully explain what's going on, as Vision 1.5.0 should have been compiled against the new version of protobuf too.
Marking this as p1 as it may well affect all the APIs I released earlier in the week. Will first try to reproduce in your repo.

Okay, I've reproduced it in the dotnet-docs-samples repo. The integration tests in google-cloud-dotnet pass though, so I suspect it's some sort of version mismatch. Continuing to investigate.

Okay, I've figured out the problem. It turns out the bug is in Google.Protobuf 3.9.0, which was just released yesterday. Our APIs depend on 3.8.0 or earlier - but some of the projects in dotnet-docs-samples have explicit dependencies on Google.Protobuf, and they're being upgraded by the gardener.
For the moment, the solutions to fix dotnet-docs-samples are:

Pin Google.Protobuf to 3.8.0
Remove the explicit Google.Protobuf dependencies entirely

(These solutions apply to the Detect and ProductSearch projects - but there may well be other projects in the repo with the same issue.)
This is being addressed in Google.Protobuf as well, but if I were to update our dependency to Google.Protobuf 3.9.0 and recompile and rerelease everything, that would probably work too. I'll discuss it with @chrisdunelm on Monday, but at least we have a handle on what's going on, and advice for the moment: avoid Google.Protobuf 3.9.0.

Leaving this open for the moment, but there's almost certainly nothing we want to do here except not depend on Google.Protobuf 3.9.0, which we may even want to delist. I'm hoping there'll be a bugfix release (of Google.Protobuf) out soon.

Thank you for the investigation, jskeet.  I'll modify dotnet-docs-samples.

Google.Protobuf 3.9.0 is delisted, so I believe we don't need to be particularly careful here any more - closing.


Lcalization for Azeri language

Checklist for this pull request
Before submitting a pull request, please make sure to follow these rules:

Your code should contain tests relevant for the problem you are solving.
Your commits messages format should follow the jQuery git commit message format (http://contribute.jquery.org/commits-and-pull-requests/#commit-guidelines).
The pull request should reference existing issues or link to a reproducible demo.
Please review the guidelines for contributing (CONTRIBUTING.md) to this repository for more information.

Description
Please describe your pull request.
Thank you!
I hope that more and more Azeri developers will get benefits from it.

thx


Creating an Org-Wide team as an unlicensed Global Admin

Many orgs don't have licenses on their Global Admin accounts, so it would be good to manage the creation of these in this situation.

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

ID: 76309c0b-2a9c-36a8-d7c7-f7d6f311d39b
Version Independent ID: bc69c0e3-0fa7-c86e-5e8c-067c8811e9bf
Content: Create an org-wide team in Microsoft Teams - Microsoft Teams
Content Source: Teams/create-an-org-wide-team.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@Lewis-Barry
thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


Move monitor.go into a package?

Currently monitor.go is in an odd spot. Perhaps we should create a new folder monitor and move it under there
.
├── api
│   └── server.go
├── builder
│   ├── client.go
│   └── client_test.go
├── consensus
│   ├── client.go
│   └── clock.go
├── monitor.go
└── types
    └── types.go

👇🏼
├── api
│   └── server.go
├── builder
│   ├── client.go
│   └── client_test.go
├── consensus
│   ├── client.go
│   └── clock.go
├── monitor
│   └── service.go
└── types
    └── types.go

Hello Sir, I'm new to open-source, would you mind if I takeover this issue?
I can move the monitor.go to a new package and refactor the project :)

Hello Sir, I'm new to open-source, would you mind if I takeover this issue?
I can move the monitor.go to a new package and refactor the project :)

Sounds good. Thanks!

Hello Sir,
I've created a draft commit https://github.com/CypherpunkSamurai/relay-monitor/commit/93744b1b171ca59fb3b342db9a1a32b99ee03c16. Please review changes :

sorry to move ahead of this issue, but I have refactored some of the code in #22 and this is no longer relevant


Remote-controlled valves for tube furnaces gas

Hardware installation is finished, but the software has not been fully implemented yet (not integrated to alab_one).


The installation goes wrong when setup.py install is called from other directory

python ./some_package/setup.py install

malfunctions: it takes the content of the current directory as the package. Instead it should take the content of the dir where setup.py is situated.
I know I shouldn't install packages this way and should use pip install ./some_package instead, but there may be no pip, no wheel and no setuptools installed at all, so to install them one has to use this command.

If setuptools is not installed, then this won't work anyway.
On Python 3, you can use python3 -m ensurepip to get pip installed. On Python 2, use the get_pip bootstrapping script.
As for this bug, it's legitimate of reproducible, though very easy to work around and apparently only affects an unsupported workflow. Is it possible that the packages you are installing are using find_packages, possibly with a relative path as the argument? I think in that case this would be the expected behaviour.


Create "subscribe" mode, that displays first name and last name field after email field, instead of feedback message.

Fixed. $.dingdongShow('subscribeOnly')


[Core] Windows2019_NET60_PackageRef_Debug failing in nightly runs

Core nightly test runs are failing with:

Error message
[error]The job running on agent azsdk-pool-mms-win-2019-general 33 ran longer than the maximum time of 60 minutes. For more information, see https://go.microsoft.com/fwlink/?linkid=2077134

For more details check here:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1630457&view=results

@jsquire for notification.

Label prediction was below confidence level 0.6 for Model:ServiceLabels: 'Azure.Core:0.5457191,Storage:0.072572485,KeyVault:0.046368074'

Closing, as this pipeline is no longer included in the Core standard pipelines.


initdb fails on macos

On Mac we are seeing
2024-06-24 09:49:14.845 AEST [24328] FATAL:  could not create shared memory segment: No space left on device
2024-06-24 09:49:14.845 AEST [24328] DETAIL:  Failed system call was shmget(key=128053537, size=56, 03600).
2024-06-24 09:49:14.845 AEST [24328] HINT:  This error does *not* mean that you have run out of disk space.  It occurs either if all available shared memory IDs have been taken, in which case you need to raise the SHMMNI parameter in your kernel, or because the system's overall limit for shared memory has been reached.
        The PostgreSQL documentation contains more information about shared memory configuration.
child process exited with exit code 1
initdb: removing contents of data directory "/Users/xxxx/projects/xxx/tmp_pg/cRwAExKc"

The fix appears to be to increase kern.sysv.shmmax and maybe kern.sysv.shmall also.
Possibly we can workaround this by adding params to the initdb invocation to indicate that a less production-like setup is acceptable.

Sorry, I'm not quite following the scope here (and I have no Apple hardware to try it out). This is occurring intermittently? Or on all Macs all of the time? Or one Mac all of the time?
Is this specific to the way Butane is invoking Postgres in some way, or does a manual invocation of Postgres initdb hit the same problem on this system?

I've got a rarely used Mac Intel, so might be able to reproduce it in order to get more specifics.
I'm told it is a permanent problem until those kern params are set.  Very likely the same error would occur if initdb was invoked the same way on the command line.

I remember having this problem years ago setting up my Django dev environment on a Mac and fixing it as explained above. It's however a "problem" between Apple security restrictions for "regular" users and how you run PostgreSQL on an Apple system (usually, as your own user with the PostgreSQL app).
I'd expect similar behavior on modern Linux distros if you set up and run PostgreSQL as a regular user.


Nothing happens after installation

The programm doesn't start at least nothing appears on my screen.
I installed https://flickrdownloadr.com/installer/windows/flickrdownloadr-<IP_ADDRESS>-windows-installer.exe
Anything else I need to do?

Thank you for reporting this - are you trying this from a Windows machine?

Thank you for reporting this - are you trying this from a Windows machine?


Close connection

This context menu should likely appear when we have an active live connection, otherwise, it should not do anything.

We have a way of closing the connection from Sessions, so removing the milestone from now.


FSM graphs and process pseudocode

This closes #29 and #28.
The graph representation for the e finite state machines
as described in players.py.
Also for representing the process two pieces of pseudocode.
One for the data collection and one for the moran process.
The pseudocodes are in a tex file.
Update gitignore to ignore pdf of tex files.
Ashlock's fortress strategies for comparison are also included
Will also close PR #22.

Thanks @Nikoleta-v3, I'm going to merge this and include in to #30.


windows aarch64 in tagged releases:

Just had a look at the latest release and did not see windows arm64. also called aarch64 I believe.
https://github.com/vlcn-io/cr-sqlite/releases/tag/v0.16.3
Windows arm hardware is really taking off, now that Qualcomm are producing hardware for Windows
Is Rust able to built for this ?
Here is just a copy / paste of the tagged release :)

[crsqlite-aarch64-linux-android.zip](https://github.com/vlcn-io/cr-sqlite/releases/download/v0.16.3/crsqlite-aarch64-linux-android.zip)
463 KB
Jan 18
[crsqlite-darwin-aarch64.zip](https://github.com/vlcn-io/cr-sqlite/releases/download/v0.16.3/crsqlite-darwin-aarch64.zip)
396 KB
Jan 18
[crsqlite-darwin-x86_64.zip](https://github.com/vlcn-io/cr-sqlite/releases/download/v0.16.3/crsqlite-darwin-x86_64.zip)
381 KB
Jan 18
[crsqlite-ios-dylib.xcframework.tar.gz](https://github.com/vlcn-io/cr-sqlite/releases/download/v0.16.3/crsqlite-ios-dylib.xcframework.tar.gz)
1.13 MB
Jan 18
[crsqlite-linux-aarch64.zip](https://github.com/vlcn-io/cr-sqlite/releases/download/v0.16.3/crsqlite-linux-aarch64.zip)
671 KB
Jan 18
[crsqlite-linux-x86_64.zip](https://github.com/vlcn-io/cr-sqlite/releases/download/v0.16.3/crsqlite-linux-x86_64.zip)
628 KB
Jan 18
[crsqlite-win-i686.zip](https://github.com/vlcn-io/cr-sqlite/releases/download/v0.16.3/crsqlite-win-i686.zip)
446 KB
Jan 18
[crsqlite-win-x86_64.zip](https://github.com/vlcn-io/cr-sqlite/releases/download/v0.16.3/crsqlite-win-x86_64.zip)

Also I am wondering why there is no WASM for the Browser ?
I would have thought that those todo examples use wasm as the service worker to do their thing...


Re-check show popup Back-up your seed-pharse on Android

Describe the bug
Re-check show popup Backup your seed phrase on Android
To reproduce the bug
Steps:

Perform upgrade version 1.1.22(283)b-v8  to 1.1.22(284)b-v8 successfully
Re-open app and observe the displayed screen

Actual: Show popup backup

Expect: Do not show popup

I've prevented showing this popup on Android. This bug doesn't often occur, so I'll recheck the code, and we'll keep following this issue for a while.

@ThaoNguyen998 This could be occurred after change web runner online to offline or downgrade web runner version. If you haven't seen any case of losing data after a month, i prefer close this issue. Thanks!

@ThaoNguyen998 close this issue because we use Marketing Campaign to show Backup seed phrase now!!!


Feat/kpcovr fitted regressor

Addresses #112. It's a little messier to use pre-fitted regressors with KPCovR because of all the extra kernel arguments, but I think it's worth it to ensure that X, K, Y, and Yhat are always consistent.
The wrinkle is how to pass the kernel arguments cleanly. The way I have it set up right now is that all of the kernel arguments come in through the regressor, pre-fitted or not. This means when instantiating the class you don't have to specify kernel parameters for both the regressor and for KPCovR. However, it also means that if you want to use non-default kernel parameters for mixing = 1, you still have to import and pass a KernelRidge instance, which seems a bit silly.
On the other hand, we could have both KPCovR and the regressor accept kernel arguments, and have one set override the other depending on the particular situation. The kernel parameters associated with a pre-fitted regressor would override the ones passed directly to KPCovR (since they need to be consistent), and maybe in the case of a non-fitted regressor the opposite would be true. The downside is that this clutters up the __init__ call. Thoughts?

However, it also means that if you want to use non-default kernel parameters for mixing = 1, you still have to import and pass a KernelRidge instance, which seems a bit silly.

I see that its conceptually more nice to separate the regressor and the kernel parameters, but it seems to be more complicated in terms of the amount of code to write to cover the different cases, when one wants to also allow prefitted regressors, and also more complicated for the user to differ the cases for the different input parameters. So I think it is fine for me. If it is written in the doc that the kernel parameters from the regressor are used, I would be okay as a user.
I really think you should change the default arguments to None and do a checker as it is sklearn style. Something could be happen, when two instances of PCovR are used, since you consider prefitted regressors. I know it is a bit constructed, but still something which could happen
class Regressor:
    def __init__(self):
        self.fitted = False

    def fit(self, X):
        self.fitted=True

class PCovR:
    def __init__(self, regressor=Regressor()):
        self.regressor = regressor

    def fit(self, X):
        self.regressor.fit(X)

a = PCovR()
print("a.regressor.fitted", a.regressor.fitted)
a.fit(None)
print("a.regressor.fitted", a.regressor.fitted)

b = PCovR()
print("b.regressor.fitted", b.regressor.fitted)

Output:
a.regressor.fitted False
a.regressor.fitted True
b.regressor.fitted True

regressor in b was not intentionally prefitted

That is some interesting behavior. My intuition would be that the instantiation of b would use a fresh instance of Regressor given the __init__ call of PCovR, but apparently not!
Either way, would it not be enough to just deepcopy or clone self.regressor during the fit? For instance,
class PCovR:
    def __init__(self, regressor=Regressor()):
        self.regressor = regressor

    def fit(self, X):
        self.regressor_ = deepcopy(self.regressor)
        self.regressor_.fit(X)

This is what I have currently done through check_krr_fit (and check_lr_fit in PCovR) -- if the regressor is unfitted, it is cloned (https://scikit-learn.org/stable/modules/generated/sklearn.base.clone.html), and if it is fitted, a full deepcopy is made.
If I understand correctly, clone-ing estimators during the fit is how sklearn tends to handle estimators-containing-estimators like TransformedTargetRegressor, OneVsRestClassifier, ColumnTransformer, Pipeline with caching, etc.

Yes deepcopy should prevent this to happening when the user uses only the public function interface of the PCovR class, but the user could just access them. They are not even marked as private.
a = PCovR()
print("a.regressor.alpha", a.regressor.alpha)
# want to update only one parameter instead of defining the whole KernelRidge
a.regressor.alpha = 0.5
print("a.regressor.alpha", a.regressor.alpha)

b = PCovR()
print("b.regressor.alpha", b.regressor.alpha)

a.regressor.alpha 0.8
a.regressor.alpha 0.5
b.regressor.alpha 0.5

That is some interesting behavior. My intuition would be that the instantiation of b would use a fresh instance of Regressor given the init call of PCovR, but apparently not!

That's an issue with using mutable instances as default values. The regressor is created when parsing code, and stored within the class; and then the same instance is used for all new instances of PCovR. Usually you want to avoid mutable values as default parameters. Something like this should work fine:
class PCovR:
    def __init__(self, regressor=None):
        if regressor is None:
            regressor = Regressor()

        self.regressor = regressor

    def fit(self, X):
        self.regressor_.fit(X)

Using a deep copy could also work, although I think it makes the code more complex.

I think we should use None as default argument and deepcopy in the fit function, it is very close what sklearn does
https://github.com/scikit-learn/scikit-learn/blob/15a949460/sklearn/compose/_target.py#L128-L140
We don't use clone because we allow also prefitted regressor


Bootstrap v4 stability

I am fully aware that is too generic and this may not be the convenient place to ask and I apologize for that. Is Bootstrap v4 current state (i.e. alpha 3) is stable enough to start a production project? Since there is no roadmap for the final stable version, I can't understand how stable the current version is. I would deeply like to get rid of Bootstrap v3 and start using v4. The first alpha has been there for a year now. So I need to know from contributors or developers how they really feel about the current state of stability for a production project. Thank you for your patience!

I use alpha 2 on my website with no issues. That being said, if something were to go wrong, you would have to explain to your client that you used a technology labelled as being in 'alpha' on their website. I'm not sure how that would go down.

@eronaeon alpha doesn't necessarily mean unstable. I have been using alpha.2 in production since January with very limited problems. Really the only thing to keep in mind is when upgrading that things  tend to change pretty radically while in alpha stage. Perfect example is when we upgraded from alpha.2 to alpha.3, we had to change all of our labels to tags and figure out why all of the stuff that used to be centered, wasn't anymore. But other than that, it was fine.
Finally, an issue ticket is not the best place to discuss this type of thing. I recommend you close this issue and move this conversation to Stack Overflow.

I believe this is partly why Bootstrap adheres to the Semantic Versioning methodology. Any changes that are backwards-compatible (and don't require any inspection on your part) would be a PATCH, aka __.__.XX
Semantic versioning helps users/clients of Bootstrap know how the changes will affect their workflow. It seems the Bootstrap team have chosen to use pre-release notation specifically because there is NO GUARANTEE about any sort of compatibility. Indeed, looking at the SemVer Specs reveals the following about pre-release versions:

A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version.

We're in alpha. Make of that what you will. 😄
Feel free to continue discussing here with your fellow community members.
But since this isn't a bug or feature request, I'm marking it as closed to keep the issue tracker tidy.


[Firewall] az network firewall policy rule-collection-group collection: support to configure --terminate-tls and --target-urls while creating a rule

Close Azure/azure-cli#15377
It's part 2/3 of Azure/azure-cli#15377

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your PR is merged into master branch, a new PR will be created to update src/index.json automatically.
The precondition is to put your code inside this repo and upgrade the version in the PR but do not modify src/index.json.

Firewall


Remove unused monkey patch

This file containing an extension to QME::QualityReport is not being used in the source code and is causing issues with the new version of bundler (due to issues with load paths).
This should resolve issue #47.  I'm proposing we delete the file since it isn't being used within the code.  If we decide this functionality is needed and the file restored, we will need to fix the order of these paths being loaded.

Looks good.


[Feature Request] New MODAL Command: Show/Hide ALL information from a Note

Hello @tadashi-aikawa !!!!
As we already know, an AQS Modal have all this information about a Note
→ Alias
→ Tags
→ Backlinks
→ Frontmatter items
→ Headers
Based on this information, I would like to share an idea with you.
My Workflow
Due to all of this rich information that I wrote above, Many times I use AQS to see all of the information that a specific note have instead filter for a unique value.
This way, my FR is about a new Modal command that let the user SHOW/HIDE all information from a note that AQS have (Alias, Tags, Backlinks, Frontmatter items and Headers)
📸 This is a real example of this FR → AQS Modal for the note 003.md

As you can see from the image above, this real note has all items
I had to type the letter a to trigger all times that contains the letter a
I have more items that does not have letter a that I want to see :)
This is extreme powerful because I can just open the modal, select a note or a subset of notes and than look at this content without open the note !!!! than I close the AQS modal and continue to work on the active note.
MY FR
This way, my FR is a new command that will Show/Hide all information that AQS has about the note that IS SELECTED/FOCUSED in the modal.
This way, we can have access to all data and decide what to do
If possible 🙏 → if the user type something while this mode is ON it will automatically came back to standard mode and filter the modal based on the query (exactly the way that works today)

Thanks for reading this !!!!! I hope you like my suggestion 🙏 🙏 🙏
Let me know if you need more information !!!
Have a great day 🌞

Hi @FelipeRearden :)
Adding "Show xxx" options like the "Show frontmatter" would be possible. However, it concerns that the feature makes AQS more complicated. So let me set the status of this issue "gathering interest" 🙏

Adding "Show xxx" options like the "Show frontmatter" would be possible. However, it concerns that the feature makes AQS more complicated. So let me set the status of this issue "gathering interest" 🙏

Hello @tadashi-aikawa !!!
100% understood! Let's see if we get more interest in this type of feature 🙏
Just a few comments about this idea for the audience:
→ It's a new command that will be triggered by a hotkey. This way, the default behavior of AQS will be a preserved. Only power users will look for information about this feature in documentation and decide if fits the user workflow.
→ This command is ALL ON /ALL OFF. By this I mean that it will show all items. The idea is to NOT have a single command for each item (backlink, frontmatter, headers and alias) but a command for ALL.
Thanks for reading this 🙏


check whether we're writing too big a blob

cross https://github.com/dimagi/commcare/pull/162

Fix a bug where we were weren't able to write a fixture > 1MB in size to the SQLite DB but would fail silently until the point that the user tried to use this fixture. Instead, fail during restore and give output
Not terribly happy with this fix, but think its a reasonable holdover until we can actually fix the underlying issue (we should be storing fixtures >1mb in files and saving the reference in the DB).
The strangest part is that Android seems to think everything has gone fine with the DB write until the moment you try to read it (IE there wasn't any exception at write time). So possible solutions were trying to read the object immediately after writing and erroring if that failed, or just testing the blob length (as I did) and reporting a failure if that blob exceeded the size.

Should be targetting commcare_2.23

:+1:  @ctsims want to take a quick pass at it?


Add analyzer to expect public properties for component parameters.

If we find a parameter that is non-public we will create a warning for that situation and notify the user.
Updated the naming of existing properties and classes that referred to public/private required properties to be specific to those properties setters (that's what they verified before these changes).
Updated test expectations and names.
Changed the code fix provider to no longer worry about the property setters and instead inspect the properties declared accessibility. Did not re-add the property setter code fix provider because these code fix providers do nothing in practice (Razor light bulbs aren't enabled in the editor).
Added new tests.

Addresses #8825

Addresses #8825

Addresses part of #8825

Addresses part of #8825

Yes, the main other thing is warning if people try to set these properties elsewhere.
@NTaylorMullen Do you think that's something we're likely to do in time for inclusion in 3.0? I'd be very keen to do that with more or less the same timing as we make this change that forces people to use publics.

Do you think that's something we're likely to do in time for inclusion in 3.0?

Yes, this is part of the work item for this milestone.

@NTaylorMullen Do you think that's something we're likely to do in time for inclusion in 3.0? I'd be very keen to do that with more or less the same timing as we make this change that forces people to use publics.

Yup, just doing this in pieces so they all can land reasonably.


More accurate cgroup error messages

- What I did
Added, "or the cgroup is not mounted" for all the cgroup error messages.
- How I did it
- How to verify it
umount a cgroup (e.g. cpusets), and then create a container using that one. You'll see a more helpful warning message.
- Description for the changelog

A kernel may support any of these, but an admin may have unmounted
certain cgroups, so let's include that possibility in the error so
as to avoid users thinking they have a kernel issue.
Signed-off-by: Christy Perez<EMAIL_ADDRESS>

Thanks! Some questions, but overall looks good

@clnperez oh, we have this PR as well, which will conflict with yours https://github.com/docker/docker/pull/24502

@thaJeztah Heh, nice. Great minds? ;) . #24502 fixed some of the same grammatical issues I did, so :clap:
I can wait until that one's in and then rebase this one.

@clnperez yes, that'd be great. We just discussed these and we want to wait until 1.12 GA, so that we don't run into difficult cherry-picks for PR's that are needed for 1.12; These improvements will make it into 1.13.

@clnperez the other PR is merged, can you rebase?

@thaJeztah Done! Thanks for the heads up.

LGTM 🐸

LGTM, thanks!


Can't save

I don't see my saves for multiplayer.  I can only see save replay by the way.

A replay is a save in MP, just host that replay from the Multiplayer menu?

I tried but I can't see anything on the host tab in the menu. It's just blank.On Mar 28, 2019 11:09 AM, Alex Hughes<EMAIL_ADDRESS>wrote:A replay is a save in MP, just host that replay from the Multiplayer menu?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.

Can you post screenshots please

I waited for about 5 minutes to see if anything would load up. Not sure what is exactly wrong.

ok well are you trying to load a singleplayer save? if so go to singleplayer load up your save then hit esc, and host server or host multiplayer dont remember what it says then when that is loaded up and done hosting then save replay and you should find it in your host tab on the main menu.


Alert color variables missing

Beta-1 seems to be missing the alert color values from Alpha.6; was there any particular reason they were removed? How do we now control the background colors and borders for alerts?

#23750 issue and others are talking about the same subject.
Color variables are now on the theme map here:
https://github.com/twbs/bootstrap/blob/v4-dev/scss/_variables.scss#L64-L74

What about the new alert changes in beta:
// Alternate styles
//
// Generate contextual modifier classes for colorizing the alert.

@each $color, $value in $theme-colors {
  .alert-#{$color} {
    @include alert-variant(theme-color-level($color, -10), theme-color-level($color, -9), theme-color-level($color, 6));
  }
}

It looks like "($color, -10)" the -10 is changing the color for alert. That is not variable related...

Closing as we don't have alert vars anymore.

can anyone explain how it's getting the background color? I want to understand how it takes the $color and what it's doing to make it 'lighter'. It doesn't appear to be a simple 'lighten' color function.

@cholybran
Its frustrating right? Almost like it has a mind of its own... o.O


Add a ConsentToShare field to the participant table

Add a ConsentToShare field to the participant table
This will default to true
Add this as an option to the edit user on the admin dashboard.

TET participant #5209 has requested that their data NOT be shared with NDA. When this ConsentToShare field is created, change #5209's status to false.


Create utility functions signatures

Create a set of initial and mandatory utility methods with a signature, specifying at least input parameters

I think it doesn't make much sense to have this as a separate task. After all, utility functions are created once they're actually needed; of course we don't know the implementation details of the code we'll be writing in advance, so we don't know which utility functions we need yet.

I totally agree, I was thinking that could help you but I'm seeing that you are learning very fast the AR ecosystem :) closing this!


Fix as_compatible_shape for transposed auxcoords

A minor fix for as_compatible_shape.
Sometimes Cube dimensions are transposed by the operation.  If an AuxCoord spans these dimensions, we need to either transpose the AuxCoord's points or rearrange its associated dims.  I went for the latter, making it consistent with the cube.transpose() treatment.

this seems like a sensible addition
many thanks @rcomer


Build(deps-dev): Bump moment-timezone-data-webpack-plugin from 1.5.0 to 1.5.1 (#3919)

Pull request opened by the merge tool on behalf of #3919

Merged in 298114f1ab152a6a1ab3979d110dfeda6cdd0ab7


Hotfix: IA-3609,  IA-3607

Explain what problem this PR is resolving
Related JIRA tickets : IA-3609,  IA-3607
Self proofreading checklist

[ ] Did I use eslint and black formatters
[ ] Is my code clear enough and well documented
[ ] Are my typescript files well typed
[ ] New translations have been added or updated if new strings have been introduced in the frontend
[ ] My migrations file are included
[ ] Are there enough tests
[ ] Documentation has been included (for new feature)

Doc

Tell us where the doc can be found (docs folder, wiki, in the code...)

Changes

add changes from https://github.com/BLSQ/iaso/pull/1761
set PaymentLot task to None after bulkupdate
front-end always show all tasks but disable buttons and add row color if task active for Payment Lot

How to test
Go to  page wit payment lots:

open a payment lot and bulk update it
Try playing with the other buttons

Print screen / video
Upload here print screens or videos showing the changes
Notes
forked from v1.246b. New tag: v1.246g. (v1.246c is playground only, d to f still had bugs)

closing as changes will be ported to main through other PRs