LPush Array

I want to push an array (string or int) to a key.... The problem is that tell that implement a marshal.
I implement but insert all in a single object, my idea is to read every of that array and insert with multiple calls to LPUSH

Done, just adding ... solve the problem


fatal error: could not build module 'Firebase'

Hi.  We started experiencing build errors for iOS related to Firebase and this plugin out of the blue recently (May 24th).  Are you aware of anything external that might of changed that would have triggered this?
While building module 'Firebase' imported from Plugins/cordova-plugin-firebase-config/FirebaseConfigPlugin.h:2:
In file included from <module-includes>:1:
ios/platforms/ios/Pods/Firebase/CoreOnly/Sources/Firebase.h:1:9: fatal error: 'FirebaseCore/FirebaseCore.h' file not found
#import <FirebaseCore/FirebaseCore.h>
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
In file included from /Plugins/cordova-plugin-firebase-config/FirebaseConfigPlugin.m:1:
Plugins/cordova-plugin-firebase-config/FirebaseConfigPlugin.h:2:9: fatal error: could not build module 'Firebase'
@import Firebase;
 ~~~~~~~^~~~~~~~
2 errors generated.
** BUILD FAILED **

Version 1.2.1.

I've forced cordova >= 9.0.0 in v2.0.4


Bug? Using .AddAutoNumber extension throws a scoping exception (aspnet core 3.1)

Hi there,
Thanks so much for doing all the heavy lifting with this! 👍
This is what I have tested it on

Visual Studio for Windows 16.5.x
Project is an ASP.NET Core 3.1 Azure Functions (runtime v~3)

Unfortunately I can't get it to work using the services.AddAutoNumber() extension (as described in your blog), it throws the following exception:
[23/04/2020 03:13:24]
Microsoft.Azure.WebJobs.Script.WebHost: Dependency AutoNumber.Interfaces.IOptimisticDataStore {ReturnDefault} as parameter "optimisticDataStore" reuse CurrentScopeReuse {Lifespan=100} lifespan shorter than its parent's: singleton AutoNumber.UniqueIdGenerator: AutoNumber.Interfaces.IUniqueIdGenerator {ReturnDefault}
[23/04/2020 03:13:24]   from ambiently scoped container with {no name, Parent={no name, Parent={no name}}}
[23/04/2020 03:13:24] To turn Off this error, specify the rule with new Container(rules => rules.WithoutThrowIfDependencyHasShorterReuseLifespan()).

It appears as tho making a singleton rely on an (effectively transient) dependency makes it barf. Perhaps it's aspnet core 3.x, I'm not sure, but the error does make sense. Here's a link which describes roughly what it is going on, in case other people are having a problem with it too:
https://blog.markvincze.com/two-gotchas-with-scoped-and-singleton-dependencies-in-asp-net-core/
I was able to resolve it by manually building the dependency chain (I just made everything singletons because that's what suits my purpose for my solution, but ymmv). It looks pretty much like this now:
// earlier on in another part of town (I had to fully qualify it coz
// I am using other Azure Storage libs)
using MWAS = Microsoft.WindowsAzure.Storage;

...

// set up the DI chain for the auto-incrementing numeric-code generation.
// it needs a CloudStorageAccount pre-registered with DI,
// has to be the MS.WindowsAzure.Storage.blah type tho, it it won't work

services.AddSingleton<MWAS.CloudStorageAccount, MWAS.CloudStorageAccount> ((svcs) =>
{
    var config = svcs.GetService<IConfiguration>();
    var connectionString = config[BlobStorageConstants.BlobStorageConnectionString];
    var cloudStorageCount = MWAS.CloudStorageAccount.Parse(connectionString);
    return cloudStorageCount;
});

services.AddOptions<AutoNumberOptions>().Configure<IConfiguration>
(
    (settings, configuration) =>
    {
        configuration.GetSection("AutoNumber").Bind((object) settings);
    }
);

// this makes it barf too, so I switched to using a singleton, below
//services.AddScoped<IOptimisticDataStore, BlobOptimisticDataStore>();
services.AddSingleton<IOptimisticDataStore, BlobOptimisticDataStore>(x =>
{
    var autoNumberOptions = x.GetService<IOptions<AutoNumberOptions>>();
    var storageAccount = x.GetService<MWAS.CloudStorageAccount>();
    var optimisticBlobStore = new BlobOptimisticDataStore(storageAccount, autoNumberOptions);
    return optimisticBlobStore;
});

services.AddSingleton<IUniqueIdGenerator, UniqueIdGenerator>(x =>
{
    var optimisticStore = x.GetService<IOptimisticDataStore>();
    var uniqueIdGenerator = new UniqueIdGenerator(optimisticStore);
    return uniqueIdGenerator;
});

It's a bit more complex, because I kind of had to force it to use specific constructors for all the entities, but the end result works perfectly. So, thanks again for building and publishing this! 👍

@wislon  Such a detailed issue. I really appreciate that. I will take a look and see what else we can do about it.

It's a bit more complex, because I kind of had to force it to use specific constructors for all the entities, but the end result works perfectly. So, thanks again for building and publishing this! 👍

Honestly, I just ported the library to .NET Core and updated everything. All credits go to the  Tatham Oddie.

Cheers @0x414c49, no problem, happy to help :). There's not much worse than coming across a problem like this and knowing there must be a way to solve it, but literally not having the time to do so. So hopefully my 'solution' (such as it is) can help someone else, even if it's copypasta and some renaming ;) .
I suspect that if you just set the IOptimisticDataStore and CloudStorageAccount deps to be singletons as well, then that'll be fine for most peoples' cases; it's not like they're massive resource pigs. I guess the gatekeeper over the whole thing is the aspnet core DI framework itself, so we don't get much say in it... and I was reluctant to set up the container to allow it to turn the error message off (as suggested in the exception).

I'm now investing some-time on the project and I think you are totally correct about making BlobOptimisticDataStore singleton. It's a dependency of UniqueIdGenerator (which is already singleton) so that doesn't make sense to make BlobOptimisticDataStore  Scoped.
I'm gonna make some changes on the DI part, especially provide more generic ways to add this project to the IoC.

@wislon I fixed this issue and created an options builder during registering the service. Can you check the PR here #2?


e2e: retry on "transport: missing content-type field" error

The e2e sometimes fail getting objects like PVCs from the Kubernetes API
server, and log the following error:
Error getting pvc "rbd-6940" in namespace "rbd-694": rpc error: code = Unknown desc = OK: HTTP status code 200; transport: missing content-type field

By checking the error message, and initiating a retry on this failure,
CI jobs should fail less regulary.
See-also: https://github.com/ceph/ceph-csi/pull/2622#issuecomment-972600735

Show available bot commands
These commands are normally not required, but in case of issues, leave any of
the following bot commands in an otherwise empty comment in this PR:

/retest ci/centos/<job-name>: retest the <job-name> after unrelated
failure (please report the failure too!)
/retest all: run this in case the CentOS CI failed to start/report any test
progress or results

/retest ci/centos/upgrade-tests-cephfs

/retest ci/centos/upgrade-tests-cephfs

Failed with #2264 (logs)

/retest ci/centos/upgrade-tests-cephfs

/retest ci/centos/upgrade-tests-cephfs

This did not get picked up the 1st time :thinking:

@mergifyio rebase

added DNM since https://github.com/ceph/ceph-csi/pull/2658 needs to be merged first for the ci to work
@mergifyio refresh

@mergifyio rebase

@mergifyio rebase


multibootusb: /bin/sh: parted: command not found

Describe the bug
multibootusb pkg expects the parted to be available in the path.
To Reproduce
Steps to reproduce the behavior:

Using NixOS 20.03 stable (system-wide)
Run nix-shell -p multibootusb
Run sudo multibootusb and you should see the following:

Extracting syslinux 64 bit...
Extracting syslinux modules to multibootusb directory...
Using pyudev for detecting USB drives...
	/dev/sdc
	/dev/sdc1
Selected device /dev/sdc
/bin/sh: parted: command not found
Traceback (most recent call last):
  File "/nix/store/gg68mc7bjm2g4g6sp9037h5wv90lvgnl-multibootusb-9.2.0/lib/python3.6/site-packages/scripts/mbusb_gui.py", line 162, in onComboChange
    usb.gpt_device(config.usb_disk)
  File "/nix/store/gg68mc7bjm2g4g6sp9037h5wv90lvgnl-multibootusb-9.2.0/lib/python3.6/site-packages/scripts/usb.py", line 403, in gpt_device
    _cmd_out = subprocess.check_output("parted  " + dev_name + " print", shell=True)
  File "/nix/store/b44iazh7w9iflqlyl1l2hrgmr5hd2znq-python3-3.6.10/lib/python3.6/subprocess.py", line 356, in check_output
    **kwargs).stdout
  File "/nix/store/b44iazh7w9iflqlyl1l2hrgmr5hd2znq-python3-3.6.10/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command 'parted  /dev/sdc print' returned non-zero exit status 127.
Aborted

Expected behavior
It to work correctly without having to manually add any additional packages
Screenshots
N/A
Additional context
You can work around the issue by manually installing the parted pkg
$ nix-shell -p multibootusb -p parted

Notify maintainers
@jD91mZM2 @bjornfor
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 5.4.39, NixOS, 19.09.2145.c2c5dcc00b0 (Markhor)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.3.4`
 - channels(root): `"nixos-20.03.1822.5adf2a6c116"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
  multibootusb
# a list of nixos modules affected by the problem
module:

Multibootusb will be dropped: https://github.com/NixOS/nixpkgs/pull/172383, since it had been broken for long and didn't have any maintainer left.


Create ClusterProfile first, CAPI Cluster later. Add-ons are not deployed

Problem Description
In this sequence:

create ClusterProfile instance
create Cluster instance with labels matching ClusterProfile

no add-ons are deployed. Essentially Sveltos never recognizes cluster is a match for the ClusterProfile instance (proof of that, ClusterSummary is never created)

Issue fixed https://github.com/projectsveltos/sveltos-manager/pull/144

Issue is seen again in v0.8.0


Use of native gen_random_uuid() since PG 13

Hi!
As documented, the uuid-ossp extension is required and (as far I looked up) there are a few test files using dedicated uuid_generate_v4() method.
Since PostgreSQL v13, a native method has been added gen_random_uuid() and could be used in place to reduce dependancies.
What do you think about?
Regards, Florent

thanks @fljdin !!
Actually, realizing the tests were just ast deparsing, the lib wasn't even necessary! thanks! it's been removed https://github.com/pyramation/postgres-ast-deparser/commit/d652b311074aaa9271fd9e0c4d0951e207c6369d
Let me know if I missed anything, cheers!


New export function to write graph as OSM XML-formatted file

per #257

I tested this on a network for Piedmont, CA and validated the output by using Osmosis to convert the output to .pbf without errors. Is there a better way to validate? Open to suggestions here.
The hackiest part of this code is here. As best I can tell, osmnx does not currently obtain or preserve these element attributes when querying the Overpass API. Osmosis, however, requires these attributes to be present when it does it's thing and will error out otherwise. Very much open to suggestions here for better ways to handle this.
The other iffy part of the code is here. In the OSM XML format it seems that certain tags are stored as element attributes, while others are stored as sub-elements of their own. I account for this by explicitly specifying which is which in the osmnx settings here. This is all fine except in the case that any of these attributes and tags don't also appear in the useful_tags_node and useful_tags_path settings. They all need to be in one of those lists of useful tags in order to be retained during creation of the graph. Perhaps the more elegant solution would be to include the osm tag and attribute lists in the get_node() and get_path() commands, since that's where the actual filtering of tags takes place, but it seemed like it involved fewer changes to the code to just force the osm tags and attributes into the "useful tags" lists whenever ox.config() gets called. That being said, it does force those default fields into the "useful tags" lists and that's probably not ideal either. Open to suggestions here as well.

Those are the main pitfalls I see with this PR, but I may be overlooking some stuff so please let me know.

Coverage decreased (-1.6%) to 91.963% when pulling d9dea78275d83b63c5b18f3d744af45040223289 on mxndrwgrdnr:master into bd407efce46ea83dc48036ae940cfe1de4161332 on gboeing:master.

Two other comments:

Because the ox.save_graph_osm() function has to iterate over every node and every id in order to parse into XML, the runtimes can be pretty severe. I clocked ~30 min to export a network with ~600k nodes and ~1.6M edges. When I was running this myself I was using a tqdm wrapper around the iterator to track progress as it went so that I wouldn't freak out and think it had stalled. I didn't want to further bog down the requirements.txt file though so I didn't include that functionality in the PR although I think it made it much nicer.
On the topic of runtimes, one future improvement might be to skip the graph_to_gdfs() conversion and parse the graph object itself directly into XML. Pandas makes life easier for the person writing the code but it definitely slows things down having to iterate over huge dataframes.

@gboeing

Because the ox.save_graph_osm() function has to iterate over every node and every id in order to parse into XML, the runtimes can be pretty severe.

It might be useful to add a comment that this can be time-intensive into the docstring.

On the topic of runtimes, one future improvement might be to skip the graph_to_gdfs() conversion and parse the graph object itself directly into XML.

This would also be more memory efficient.

I tested this on a network for Piedmont, CA and validated the output by using Osmosis to convert the output to .pbf without errors. Is there a better way to validate?

That seems reasonable. Would you also add a new test to tests/test_osmnx.py to test this function for CI, using a small graph for relatively quick runtime?

@gboeing travis is failing trying to create the TESTENV but the only change I made to requirements.txt was to remove lxml. Have you seen this before?

travis is failing trying to create the TESTENV but the only change I made to requirements.txt was to remove lxml. Have you seen this before?

@mxndrwgrdnr I think this is happening because of recent changes in how conda and conda-forge handle channel priority. I've updated the travis config in the master branch and the tests are working again there. It should fix it here if you rebase your PR from master to incorporate those changes.

@gboeing we good.

Thanks!


[Discussion] Private Genesis State

Description
As a user of unrestricted privacy, I want to be able to specify the initial genesis state for private transactions.
There are a couple of options on how to implement this:

separate private genesis config e.g private-genesis.json

add an option into genesis.config e.g

"alloc": {
  "0x0ffd23af8eebc60b3cfdeed6f814988757237314": {
    "private": true,
    "code": "0x6080...",
  }
}

There are also question about how much to implement as a first version. Perhaps a good start would be to use the same public genesis on the private state? This would cater for many scenarios.

I think there might be a pitfall to be avoided where transaction participants can have divergent private states

I think there might be a pitfall to be avoided where transaction participants can have divergent private states

Yeah, could be an issue but don't think there would be much gain in the world of private transactions. Another option would be to make it part of the createPrivacyGroup transaction (this would only work for onchain privacy groups) so that you have the initial members and the genesis as part of the first private transaction.

The other option is to go down the plugin/factory approach where the user can apply whatever transactions they want to a group before it becomes 'active'. The tradeoff is that everything who's using privacy groups on that network must have the same plugin in installed. But, the same would be true for with config file.

That sounds interesting. There is no spec for genesis files, I’d be very interested if we can land something here and port it to EEA tests.

I didn't realise there wasn't anything in place! The first implementor wins I guess :smile:

Agreed!

@antonydenyer I believe this discussion continued in another ticket? maybe I'm misremembering

It did https://github.com/hyperledger/besu/pull/2509
I guess there are a couple of things to consider.

what we do from a besu point of view
what should the standard look like

Personally, I think @pinges is right. Besu should implement it using a plugin architecture. Then from a standards point of view, we can provide an off the shelf plugin that implements/adheres to the standard.

Discussed and merged in #2509


update border color

Fixes 107 .

Changes proposed in this Pull Request:

fix mat expansion header border

Screenshots:

Showcase demo:

To Test:
Angular-design-pattern

/lists/status-list
/lists/inline-local-actions

Angular showcase demo:
/templates/dashboard

https://github.com/brightlayer-ui/angular-showcase-demo/blob/dev/src/app/pages/templates/dashboard/dashboard.component.html#L169 need to remove this line to fix double border (this issue is only in showcase demo).

The changes work, but since we've already defined this color in both palettes, we can use the palette here instead.  Also can you update the changelog?


About getting the Pseudolabel

Hi ouyang,
Good job! I have some problems about getting the pseudolabel as follow:
1、I can't understand the way of randomly select when from pseudolabel candidates to pseudolabel, according the pixel of pseudolabel candidataes or others?

2、What's the detail of pseudolabel candidates? How many classes of seudolabel candidates? 400? Each pixel instand of one class?
Thank you very much!  best!

Hi, thanks for your interest.
Pseudolabels are stored with label values 0 (background), 1, 2, 3,.... . Different values are used to differentiate each individual pseudolabel.
In each training iteration, a random pseudolabel is selected according to the label value. The task shown to the network is to segment this specific psedulabel label against everything else (i.e., essentially a FG-BG segmentation problem).
Please also see the pseudolabel generation Jupiter notebook for more details.
Cheng

@gaowq2017 Hello. May I just kindly ask if you eventually get this code working? Thanks. Please let me know if you have any questions.

@gaowq2017 Hello. May I just kindly ask if you eventually get this code working? Thanks. Please let me know if you have any questions.

Hi ouyang:
Thank you very much! I can use this code but i use not pseudolabel as the label. Because i don't known how to get the pseudolabel in ourself dataset from superpixels to pseudolabel as follow:

Thanks for your reply. You can look into ./data/pseudolabel_gen.ipynb which generates pseudolabel step by step. You might want to change configuration like image paths/ namings according to your own dataset.


Updates Codecov ignore list to correctly ignore items.  Updates documentation release process.

Linked Issue:

Checklist:

[ ] Is the linter reporting 0 errors?
[ ] Did you comply with our styleguide?
[ ] Is there adequate test coverage for your new code?
[ ] Does the CI pipeline pass?
[ ] Did you update the documentation?
[ ] Did you update the sample app?
[ ] Do we need to increment the minor/major version?
[ ] Did you change the public API?
[ ] Have you done everything you can to make sure that errors that can occur are compile-time errors, and if they have to be runtime do you have adequate tests and documentation around those runtime errors? For more details.

If Applicable:

[ ] Did you test when the first item is skipped?
[ ] Did you test when the last item is skipped?
[ ] Did you test when middle items are skipped?
[ ] Did you test when incorrect data is passed forward?
[ ] Did you test proceeding backwards?

If Public API Has Changed:

[ ] Did you deprecate (rather than remove) any old methods/variables/etc? Our philosophy for deprecation.
[ ] Have you done the best that you can to make sure that the compiler guides people to changing to the new API? (Example: the renamed attribute)
[ ] If necessary, have you tested the upgrade path for at least N-1 versions? For example, if data persists between v1 and v2 then that upgrade should be tested and as easy as we can make it.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@29e6a99). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #54   +/-   ##
=======================================
  Coverage        ?   98.20%
=======================================
  Files           ?       71
  Lines           ?     4615
  Branches        ?        0
=======================================
  Hits            ?     4532
  Misses          ?       83
  Partials        ?        0

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 29e6a99...2869ee6. Read the comment docs.

Approvals met and checks passed.  Merging into main.


FIDO2 breaking change

The latest version of the fido2 library changes the get_assertion function which breaks MFA.
https://github.com/Yubico/python-fido2/releases/tag/0.8.1
Expected Behavior
webauthn/U2F tokens should work
Current Behavior
TypeError: get_assertion() takes 2 positional arguments but 4 were given
Possible Solution
Update the code to work with latest version of python-fido2, or lock to fido2==0.7.3
Steps to Reproduce (for bugs)

Use webauthn MFA

Your Environment

App Version used: 2.1.3
Environment name and version: Python 3.7.3
Operating System and version: macOS 10.14.6

Breaking change in a minor release, eh?  Bad fido, bad.
We'll lock it for now.

Added to release 2.2.0.  Thanks!


ZTE ZXR10 VSC (Virtual Switch Cluster)

Issue type: feature request
Since we are using this switches in our datacenter, i would like to add the stacking ports. They use a 40GB MiniSAS cable and the ports are shown as "xlgei" ("gei" for 1GB ports, "xgei" for 10GB ports).
ZTE calls the stacking technology VSC (Virtual Switch Cluster).
Is it possible to add this kind of ports as MiniSAS or under the Stacking group?
Thanks!

Can you provide a link to documentation of the interface specification? I can't seem to find anything.

I have only offline documentation available, i have attached the pages related to the stacking expansion module with the 40GB ports (ZTE_59_2L_SK.pdf) and VSC configuration (ZTE_VSC.pdf), let me know if you need further informations.

Given that these use a standard mini-SAS form factor, we probably don't want to define it as something specific to ZTE. But we also don't currently define storage interfaces. I'll leave this open for comment for now.

Maybe just adding the interface type like Juniper VCP would be enough?

My point is that (as far as I can tell) this isn't a ZTE-proprietary form factor: it's a standard mini-SAS form factor. We don't want to add it as a ZTE-specific stacking form factor since it might be in use by other vendors for the same purpose.

It feels like we're starting to abuse the concept of network interface with regard to stacking interfaces. These are really proprietary connections that should be treated a bit differently from normal interfaces. I'm going to hold off on adding any more stacking types until we at least have a better idea where #99 is headed.


add first implementation of augmentedNN to predict selectivity

I add first implementation of augmentedNN to predict selectivity for range predicates, taking lstm.cpp and LSTM.py as a reference.
Test cases for the model are also added. The test cases include a uniform distribution dataset and a skewed distribution dataset.
Hyperparameters, especially number of training epochs, need to be discussed based on real system experiments.

Coverage decreased (-0.2%) to 76.303% when pulling 15cf3d138f1a4f961093cc5117f6ed9e288f73c4 on yetiancn:master into 1de89798f271804f8be38a71219a20e761a1b4b6 on cmu-db:master.


Character preview

What feature do you want to get added on the base engine?
This feature will add a character preview of bf variants skin or even opponents that can be play-able just like from the dave and bambi, whatever song you'd choose it will take you to the character preview!
To test your sight, and reliability, please select the option of what should NOT be requested.
A good idea

i mean you can technically do that in the character editor? just press through the animations


On how to enable users to use TF32 in CuPy

TensorCore, special hardware units executing matrix multiply operations, has been enhanced in the A100 GPU. One of the enhancements is the TF32 compute mode, in which inputs and outputs are still in F32 data type, but are internally converted to proprietary 19-bit floating point for fast matrix multiply. The results in TF32 compute mode are not exactly the same as the results in FP32, but it is much faster.
The CUDA11 libraries support the TF32 compute mode; for example, cublasGemmEx, one of the matrix multiply subroutines in cuBLAS, uses the TF32 compute mode when the parameter computeType is CUBLAS_COMPUTE_32F_FAST_TF32.
We would like to make this TF32 compute mode available in CuPy as well, so I hope we can discuss here specifically how we can make TF32 compute mode available to users.
We believe there are three levels of CUDA library use in CuPy.

directly call the thin wrapper of the C/C++ API of the CUDA libraries (e.g., cupy_backends.cuda.libs.cublas.gemmEx).
call a python routine that abstracts the C/C++ API of the CUDA libraries (e.g., cupy.cutensor.contraction).
use from Numpy/Scipy compatible subroutines (e.g., cupy.matmul, cupy.einsum).

As for 1., I don't think there is any need to discuss on it, as we just need to make it available in Cupy, TF32 compute mode related data types defined in each CUDA library.
As for 2., for example, in cupy.cutensor.contraction, you use numpy dtype to allow you to specify the compute mode, there is no TF32 in numpy dtype, so you need to do something about it.
As for 3., for example, you may call a subroutine of cuBLAS library in cupy.matmul, so you need to be able to specify in some way whether you want to use the TF32 compute mode there.
I think we should decide on a general policy before we start implementation.
What would you think on this?

Hi @anaruse, any chance you could comment on #3370? Someone suggested that TensorCores might help speed up complex32 computations.

We discussed in the team:

Adding new dtype like cupy.tf32 sounds inappropriate as the acutal array data format on memory is exactly the same as cupy.float32.
Adding new keyword arguments to each routine (e.g, cupy.matmul) is a burden and should be avoided also in terms of compatibility with NumPy.
We think the relationship between "float32" and "tf32" is similar to that of "cudnn disabled" and "cudnn enabled" in Chainer, so it is better to make it a configuration that users can opt-in, like environment variable CUPY_TF32=1.

Adding new dtype like cupy.tf32 sounds inappropriate as the acutal array data format on memory is exactly the same as cupy.float32.

Why? Do I miss something? It doesn't look like so to me:
https://blogs.nvidia.com/wp-content/uploads/2020/05/tf32-Mantissa-chart-hi-res-FINAL.png

https://blogs.nvidia.com/blog/2020/05/14/tensorfloat-32-precision-format/

TF32 Tensor Cores operate on FP32 inputs and produce results in FP32.

I guess naruse-san intended to use this?

Ah I see, thanks @kmaehashi!

TF32 implemented via #3810. Thanks @anaruse!


feat(blobs): revert to constant roots of unity rather than unconstrained

Due to https://github.com/noir-lang/noir/issues/6457, having a huge constants file with the roots of unity is slowing down noir/proving/simulating in the blobs PR (#9302). With this slowdown, proving 3 blobs per block instead of 1 won't run, but 1 isn't enough to contain the fields we expect.
For now, we are calculating the roots of unity in an unconstrained function and using those to move to 3 blobs. This means we are not constraining that we have correctly constructed a blob containing the tx effects of the block, so it's horribly insecure.
Once the above issues are resolve, go back to using the large constants file in noir-projects/noir-protocol-circuits/crates/blob/src/config.nr and delete noir-projects/noir-protocol-circuits/crates/blob/src/unconstrained_config.nr.

The linked issue has been closed, is this still a problem today?


NodeStage Volume request.PublishContext doesn't contain key wwn/wwnkey value is empty

Error snippet:
func (d *nodeService) NodeStageVolume(ctx context.Context, req *csi.NodeStageVolumeRequest) (*csi.NodeStageVolumeResponse, error) {
    ....
    ....

    wwn, ok := req.PublishContext[WWNKey]
	if !ok || wwn == "" {
		return nil, status.Error(codes.InvalidArgument, "WWN ID is not provided or empty")
	}
    ...
    ...
}

Error logs:
GRPC error: rpc error: code = InvalidArgument desc = WWN ID is not provided or empty

Exploring the node plugin.
The NodeStage volume method is called by kublet.
Need to analyse why it is not passing wwn id.

/assign

WWN Key value is empty in req.PublishContext:
I1207 05:04:52.856589       1 node.go:90] NodeStageVolume: called with args {VolumeId:f22eba03-4b9f-4dd2-9d37-d57aa563c39f PublishContext:map[wwn:] StagingTargetPath:/var/lib/kubelet/plugins/kubernetes.io/csi/pv/pvc-9ca714b7-50d5-483c-8685-e9063fca28ac/globalmount VolumeCapability:mount:<fs_type:"xfs" > access_mode:<mode:SINGLE_NODE_WRITER >  Secrets:map[] VolumeContext:map[storage.kubernetes.io/csiProvisionerIdentity:1638852069180-8081-powervs.csi.ibm.com] XXX_NoUnkeyedLiteral:{} XXX_unrecognized:[] XXX_sizecache:0}
I1207 05:04:52.856697       1 node.go:134] NodeStageVolume: wwnkey: wwn, req.PublishContext: map[wwn:]

Volume details from IBM Cloud returning empty string for wwn sometimes and taking time to return the actual wwn.
Adding a temporary wait loop in controllerPublishVolume solves the issue.
         for i:=0;i<10;i++{
               disk, err := d.cloud.GetDiskByID(volumeID)
               klog.V(5).Infof("ControllerPublishVolume: disk details/%s : %+v", volumeID, disk)
               if err != nil {
                     if err == cloud.ErrNotFound {
                             return nil, status.Error(codes.NotFound, "Volume not found")
                     }
                     return nil, status.Errorf(codes.Internal, "Could not get volume with ID %q: %v", volumeID, err)
              }

              if disk.WWN == ""{
                 klog.V(5).Infof("ControllerPublishVolume: WWN is empty SLEEP 5s")
                  time.Sleep(5 * time.Second)
              }else{
                  break
              }
         }

         disk, err := d.cloud.GetDiskByID(volumeID)
        klog.V(5).Infof("ControllerPublishVolume: disk details/%s : %+v", volumeID, disk)

Need to add a standard wait loop utility method and use it in controller.

Need to add a standard wait loop utility method and use it in controller.

There is a standard wait function present in the k8s here - https://github.com/kubernetes/apimachinery/blob/5f072755815add51938b52f806c555ed8c86a1ce/pkg/util/wait/wait.go#L511, my fav one is PollImmediate, you can use one of them.

and also we need to understand when this happening and see if we can create an issue with PowerVS team for this one.

Wait loop for disk creation is currently not implemented in the cloud library.
The following justifies: https://github.com/ppc64le-cloud/powervs-csi-driver/issues/38


Prevent rendering

Hey guys,
Is there currently any way to prevent rendering ?
I would need such a feature to optimize my server side rendering, let me explain how it works:
1/ I'm rendering my app in order to feed the stores (API call...)
2/ When all the stores are ready, I'm rendering my app a second time in order to get the final html
3/ I'm sending the html
With this feature I would be able to prevent the components rendering in the part 1/ for performance improvements ! : )
Do you think we could implement this feature ? I guess we may only have to add a condition in the shouldComponentUpdate lifecycle method ?
Thanks

Sounds to me like a simple if statement in some root component that prevents children from being rendered until a certain condition is met? Or you can event postpone the SSR React.render in the first place until your stores are ready?

Thanks for your help @mweststrate 😃
I have to render my whole component three to let the components initialize and call the necessary store's methods.
I guess I could use shouldComponentUpdate in all my "smart components" using the @observer but I don't even think that mobx-react check the component shouldComponentUpdate result before doing his own business. (Am I right?)
Having a way to enable/disable the @observer rendering would be a cool feature though, SSR would be easier, less extra code.

We could call shouldComponentUpdate if it exists here https://github.com/mobxjs/mobx-react/blob/master/index.js#L53 and skip forceUpdate if it returns false.

@andykog good point, that might make sense anyways. Or it might be confusing :) not entirely sure. Implementing should be pretty straight forward, although the original shouldComponentUpdate should be used, as mobx replaces it with its own implementation

@mweststrate voting for keeping shouldComponentUpdate with it's original functionality (or at least providing an observer that respects manually written ones).

Investigated this issue. shouldComponentUpdate is respected, but only for setState or newly passed in props. It is not respected when observables used in render are changed. This breaks fundamentally with the philosophy of MobX that derivations and state should be kept consistent with the state at all times.
If you don't want components to be rerendered, this should be expressed in the state and addressed by using for example computed or other observables that are only updated once in a while.
I hope that helps!

@thunderkid I think the discussion is about shouldComponentUpdate, not render. Not entirely sure since this thread is 1.5 years old and closed ;-)

Or we could implement componentWillReact return true/false to render or not ?


Toolbarc

@linuxgurugamer we now have a way to do this directly without a throw-away PR:

https://github.com/KSP-CKAN/NetKAN/actions/workflows/manual_inflate.yml

See KSP-CKAN/NetKAN#8262.

I think this would've also been inflated via the webhook, or the 30 minute bot run at the latest.


Why not use conv3D  instead of sparse conv3D?

Hi,
As we know, sparse conv3d is popular in the 3D detection pipeline, such as CenterPoint, PV-RCNN, and so on.
Why do we use  normal conv3D   instead of sparse conv3d.

Hi @rockywind ,
I agree that sparse 3d convolutions are better for 3d object detection as they require much less memory and time. However, for multi-view 3d detection we first need to aggregate the representations from multiple RGB images. In our case this aggregation ends with a dense (nos sparse) voxel volume representation. Consequently we process this volume with dense (not sparse) 3d convolutions.
You can feel free to share the ideas how to make the 3d voxel volume representation sparse. However I think if you have a really good one it can be a great idea for your next paper :)

Yes, I see.
Thank you for your help!


Warn users about using provided/optional/implementation for annotation deps, especially with @Implies

I wrote something about those scopes for Guava users in https://github.com/google/guava/wiki/UseGuavaInYourBuild#what-about-guavas-own-dependencies, but here we'd be writing primarily to other library authors who are making their own decisions about what scope to use.
We'll hopefully be defining annotations such that those scopes can't cause "Cannot find annotation method 'value()'" problems, but I don't know that we'll be able to prevent all runtime problems. And @Implies is going to be a whole additional problem (somewhat similar to @Inherited) about which I'll file an issue shortly.
Some other links:

https://issues.apache.org/jira/browse/MNG-2205?focusedCommentId=16267311&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16267311
https://github.com/google/auto/pull/765#discussion_r332220988
https://github.com/google/auto/pull/765#discussion_r335545477

(In our docs, we can mention that JSpecify is a small library (and, given our rate of progress, is going to stay that way ;)).)

I think you were summarizing this issue in #295 like this:

When developers declare a dependency on a library of annotations (like JSpecify), they sometimes choose to declare the dependency in a way that tells tools: "When someone depends on my library, don't include that annotation library on that user's classpath, either at build time or at runtime." I think this is a bad idea in general (and so I want to discourage it).

So unless we reverse course on "bad idea", we should continue this evangelism, and strongly advise tool owners that they should issue loud warnings when they spot an annotation they know nothing about. And maybe even add a javadoc blurb to @Implies in particular about it.

See also #389.

Continuing to dump links without thinking deeply: As long as nullness checkers contain code like this that introspects on annotation declarations, we will have another reason to worry about building without those annotations on the classpath.

This is written in the docs-1.0 branch, which we'll merge into main soon.


Fail to install pycdec

I find most of the command about installing pycdec is  python setup.py install
BUT, I just find the setup.py.in file and there is no setup.py file
when I type python setup.py.in install
I encountered with an error

`../utils/fast_sparse_vector.h: In member function 'size_t FastSparseVector<T, LOCAL_MAX>::size() const [with T = double; unsigned int LOCAL_MAX = 7u; size_t = long unsigned int]':
../utils/fast_sparse_vector.h:280:3: warning: control reaches end of non-void function [-Wreturn-type]
   }
   ^
In file included from cdec/_cdec.cpp:264:0:
../decoder/kbest.h: In member function 'bool KBest::FilterUnique::operator()(const std::vector<int>&)':
../decoder/kbest.h:34:5: warning: control reaches end of non-void function [-Wreturn-type]
     }
     ^
In file included from ../utils/fdict.h:11:0,
                 from ../utils/fast_sparse_vector.h:25,
                 from ../utils/sparse_vector.h:4,
                 from ../utils/weights.h:6,
                 from cdec/_cdec.cpp:238:
../utils/dict.h: In member function 'WordID Dict::Convert(const string&, bool)':
../utils/dict.h:60:3: warning: control reaches end of non-void function [-Wreturn-type]
   }
   ^
In file included from ../utils/dict.h:11:0,
                 from ../utils/fdict.h:11,
                 from ../utils/fast_sparse_vector.h:25,
                 from ../utils/sparse_vector.h:4,
                 from ../utils/weights.h:6,
                 from cdec/_cdec.cpp:238:
../utils/wordid.h: At global scope:
../utils/wordid.h:9:21: warning: 'null_wordid' defined but not used [-Wunused-variable]
 static const WordID null_wordid=std::numeric_limits<WordID>::max();
                     ^

error: command 'gcc' failed with exit status 1`

Could anyone help me ?
thanks!

Can we get a fix on this issue? I am facing the exact same error.


glfwWaitEvents not waiting

glfwwaitevents() does not seem to be working in the latest version of glfw3 as compare to it's previous versions.
I have been trying to run or debug the example of rotating triangle with glfwWaitEvents() command, but the triangle keeps rotating along with flickering rather that just supposed to stay stationary with no input via keyboard or mouse.

Which version of what OS are you using?

windows 8.1

windows 8.1 with visual studio 2015

Unable to reproduce using Windows 8.1, MSVC 2015 (update 1), and current glfw master.

Unable to reproduce.

Unable to reproduce using Windows 10, MSVC 2015 (update 1) with either current glfw master or 3.1.2 NuGet package
@waqasm86 Post your code

Still unable to reproduce.

@dougbinks I'm not opposed to that if people find it sufficiently useful.

Unless this can be reproduced, I suggest this issue be closed. IMO the most likely cause is a third-party piece of software sending unwanted messages to the window (could be anything from a screen recorder to a Windows misfeature). We could maybe create an enhancement issue to discuss designing something to filter these out as dougbinks suggests, probably targeting 3.4.

I can reproduce this on some machines, and I've been intending to look into this but just haven't had the time yet given that I think it's relatively low priority.

@dougbinks Are you able to reproduce with any of the glfw test/example programs, or maybe a very simple program that I can copy? I will try again to reproduce and debug now that I'm on Windows 10.

This happens on any program using glfwWaitEvents() - any message sent to a window will cause the glfwWaitEvents() to return since the underlying message procedure handles the message.
However outside of user input this only happens on some machines. I don't have the ones which do this in front of me right now and don't recall the message being processed, but you could create a program which sends a message to your glfw program using SendNotifyMessage  to test if you need.


KAFKA-6554; Missing lastOffsetDelta validation before log append

Add validation checks that the offset range is valid and aligned with the batch count prior to appending to the log. I've added several unit tests to verify the various invalid cases.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

cc @rajinisivaram

@hachikuji Thanks for the updates, LGTM. Merging to trunk and 1.1.


[infra-proxy-service] Auto populate terraform deployed chef servers.

:nut_and_bolt: Description: What code changed, and why?

Add function configure_automate_infra_views.
if enable_chef_server is enabled the add entry in servers using infra-proxy-service.

:chains: Related Resources
Fixes https://github.com/chef/automate/issues/3585
:+1: Definition of Done

dev and acceptance environments have the pre-populated entry of terraform locally deployed chef servers.

:athletic_shoe: How to Build and Test the Change
:white_check_mark: Checklist

[x] I have read the CONTRIBUTING document.
[ ] Tests added/updated?
[ ] Docs added/updated?
[x] All commits have been signed-off for the Developer Certification of Origin.

:camera: Screenshots, if applicable
Signed-off-by: Vivek Singh<EMAIL_ADDRESS>

@jeremiahsnapp thankyou so much for insights!
At present, if configure_automate_infra_views run multiple times it will raise the error record AlreadyExists. Surely, that will get logged somewhere and not a valid case.
Will add the checks to ignore if the record already exists and update you soon
Thanks!


ci: whitenoise broken

===========> Running lint.whitenoise ...
tools/bin/whitenoise
fatal: ambiguous argument 'main': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git  [...] -- [...]'
https://github.com/envoyproxy/gateway/actions/runs/3926974423/jobs/6713175184

dup of https://github.com/envoyproxy/gateway/issues/523


FIX: Upgraded docker dependencies

There were security issues reported in several components in the
Dockerfile. This PR fixes them. It should not introduce any
breaking changes, but this container does now run as a 'gitleaks'
user.
Issues reported:

3 Vulnerabilities in Openssh v8.1_p1-r0
1 Vulnerability in busybox v 1.31.1-r9
1 Vulnerability in apk-tools v2.10.5-r0
1 CIS best practices issue - Container did not run as non-root

Additional fixes/changes

Refactored Dockerfile to allow easier upgrades in the future
through ARGuments.
Refactored makefile to support additional arguments
Refactored makefile with an IMAGE_PATH to make future container
tests easier
Downgraded to openssh-client instead of openssh*. Having the
openssh server in the container is a bad practice.
Did not version pin the APKs as that is against Alpine guidance

Fixes #562
NOTE: I was not able to scan using the proprietary twistlock tool.
Description:
Explain the purpose of the PR.
Checklist:

[X] Does your PR pass tests?
[ ] Have you written new tests for your changes?

Closing this in favor of https://github.com/zricethezav/gitleaks/pull/615, I will still give you a shout out in the next release

Sounds good! Thanks for patching it. :)


compiler: Implement graceful lowering of derivatives (aka "unexpansion")

With the option
Operation(..., {'expand': False})

derivatives are now synthesized as loops over FD coefficients, rather than through unrolling. This required non-negligible additions and changes to the compiler, among which the enhancement of so called StencilDimensions, which were until now utilized in tests only and the generalization of several compiler passes (among which Cluster fusion).
The PR is equipped with lots of new tests.
However, the machinery introduced here is mainly exploited in PRO, where >100 tests stressing the new compilation engine have been added.
There still are 3 TODOs left here, which I count to address between this week and next, but they shouldn't change the PR content meaningfully
This stuff is mandatory for Rice; hence we should aim to merge it ASAP. Apologies for the little pressure, I did my best to file it ASAP, but despite working on it full-time since December, it is only now that it's reached a decent stage)
This PR should also more neatly achieve what https://github.com/devitocodes/devito/pull/2014 (@georgebisbas ) has tried to do

An important issue of this PR I forgot to mention. Code generation times do increase. Between 15% and 40% I'd say, but only noticeable with complex physics and high order discretizations. Cost increase is due to more sophisticated and in particular more accurate data dependence analysis.
@ggorman and I discussed at length about this and in particular what to do. We propose to park it until after Rice, or at least until the stuff for Rice is ready, then sprint on it altogether to improve the situation.
This time we want to use Numba

Numba might be a good idea yeah, and for other part of the compiler as well.


General code clean-up and refactoring

This is an open call for implementing better programming practices (e.g. DRY) to any areas of the codebase that are lacking. Any help is welcome.

Hi, I'd like to participate in refactoring this code.


feat(core): Add add_zeros_like function

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

Project coverage is 80.15%. Comparing base (1ff095c) to head (344330c).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #51      +/-   ##
==========================================
+ Coverage   79.48%   80.15%   +0.66%
==========================================
  Files           9        9
  Lines         780      796      +16
  Branches      214      220       +6
==========================================
+ Hits          620      638      +18
+ Misses        131      130       -1
+ Partials       29       28       -1

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


Health Check

Hello,
why there isn't any documentation regarding the usage of the health_checks that are already being supported (and used by this module!) by the aws_lb resource?

Well, there are examples which partially substitute documentation. Have you checked them?
https://github.com/terraform-aws-modules/terraform-aws-alb/blob/06706ac43dadf995ffd6572a9337b1f762e9e7d8/examples/complete-alb/main.tf#L185-L195

This can also help
https://www.terraform.io/docs/providers/aws/r/lb_target_group.html#health_check


[Event Request] CU 13637 OIOUBL-Export Sales Cr. Memo

Requesting a new event in CreateXml to allow editing the xml Document before it’s written to stream.
We would like to fill some optional tags in the document, like embed pdf and add more information on lines.

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. We will update this issue with information about availability.


git patch apply no such file or directory when creating a PR

I'm running Gogs  <IP_ADDRESS>2 Beta and have an organizational repo with a forked repo of that  under my own account in Gogs.
When trying to submit a PR from my forked branch to the same branch in the organization repo, I am met with a 500 page.  The gogs.log shows the following:
2015/11/18 10:40:02 [...routers/repo/pull.go:642 CompareAndPullRequestPost()] [E] NewPullRequest: testPatch: git apply --check: exit status 1 - error: path/to/valid/file.txt: No such file or directory
However, on the PR creation page, the diff shows up correctly, and I can see that the file exists in the matching branch of both repos.
Setting the run mode to test and dev did not produce any other helpful information.

@ryanb-hc
Can you try to reproduce this on https://try.gogs.io
maybe your bug is related to this one: #1931

I've tried it out on https://try.gogs.io and was unable to reproduce the problem.  Reading through that issue it looks like it could be similar.
It appears that your issue has been fixed on gogs/master as of 3 days ago, I'll update my server and test it out there again.

@ryanb-hc you need to update your Gogs.

Upgraded our local gogs server from source just now.  PRs worked exactly as expected.
@stonerl Thanks for the quick response and direction
@Unknwon Thank you for all your time and dedication to making such a wonderful piece of software!

:tada:


Dash vertical align

Em dash and en dash (and possibly others) are centred on the zero digit. But these symbols are appropriate for use with lowercase text in a vertical position similar to the hyphen.

Thanks for reporting this and for the screenshot.

FWIW this is still an issue. The dashes sit way too high compared to the letters, and it's especially noticeable in titles.


Question on how to realm - Ensure that realm-related code runs on same background thread with runloop

This is a question on how to use realm
Goals
Ensure that realm-related code runs on same background thread with runloop
Expected Results

I am using realm in an iOS app.
I am calling realm methods in a background thread. Realm objects can be used only in the thread where it was created.
This means that I have to ensure that all the code related to accessing realm objects happen on the same thread. This question has been answered here-  How to ensure to run some code on same background thread?
The background thread has no runloop and hence realm objects do not get refreshed automatically.
Can any one point out how to create a background thread with a runloop so that the code blocks can be executed on the same background thread with runloop?

The answer from clemens which creates a NSThread and uses performBlock to enqueue work on that thread's RunLooop is what you have to do. Manually implementing an event loop using a semaphore and work queue means that Realm doesn't know how to enqueue work on the queue, and trying to mix the two will just end in pain.


Remove system-owned runtime image configurations

Elyra currently pre-installs a set of runtime image configurations. There are several issues:

these configurations  cannot be removed by users
the referenced container images don't work on Red Hat Openshift
the referenced container images are maintained and hosted by third-parties and might be impacted by the recent Docker decision to sunset free team organizations

This PR removes these runtime configurations from the Elyra installation. Migration instructions will be included in the Elyra release notes. A draft version can be found here https://github.com/elyra-ai/elyra/discussions/3120. Note that documentation links in this document will yield a 404 until Elyra 3.15.0 was published.
Considerations:

No impact on existing pipeline files because the image name is persisted, not the runtime configuration name.
Existing installations of Elyra continue to include these runtime image configurations, even after Elyra was upgraded using pip install ... --upgrade. The removal only impacts new installations in a clean environment or upgrades that are performed by running pip uninstall ... followed by pip install ....
Container-based Elyra deployments can be extended to use the elyra-metadata install command to create the desired default runtime image configuration entries.
Custom builds of Elyra can still take advantage of system-owned runtime image configurations because this PR does not remove the relevant code. For example, a custom build might add one or more metadata files to the etc/config/metadata/runtime_images directory.

What changes were proposed in this pull request?

Remove runtime configurations
Add runtime configurations as test resources
Update tests to use test resources

How was this pull request tested?

Launch JupyterLab/Elyra and verify that nothing is broken
test-server and test-integration Makefile targets complete successfully

Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Existing installations of Elyra continue to include these runtime image configurations, even after Elyra was upgraded. The removal only impacts new installations.

This is really a function of how the user chooses to "upgrade" the application.  If they treat the upgrade as "uninstall/install", then the files in {sys.prefix}/share/jupyter/metdata/runtime-images will be removed during the uninstall.   Using pip install --upgrade elyra will "preserve" the location.

Container-based Elyra deployments can be extended to use the elyra-metadata install command

We should probably document equivalent elyra-metadata install runtime-images commands for users to produce this.  Also, with this approach, users would be able to modify these instances since they will not be considered "system-owned" - which is a good thing. :smile:

Existing installations of Elyra continue to include these runtime image configurations, even after Elyra was upgraded. The removal only impacts new installations.

This is really a function of how the user chooses to "upgrade" the application. If they treat the upgrade as "uninstall/install", then the files in {sys.prefix}/share/jupyter/metdata/runtime-images will be removed during the uninstall. Using pip install --upgrade elyra will "preserve" the location.

Great point! I've updated the PR description accordingly.

I don't think we should remove these runtime images as these will make the pipelines unusable out of the box.

Pipelines are already unusable out of the box for KFP and Airflow because users need to create a runtime configuration first, which is a non-trivial task. That local executions currently require a container image to be as associated even though it is never used is a design issue, which should be fixable.

Yes, we make this on purpose to make sure validation was considering the pipeline ready for real business which is run in a runtime which requires associated runtime-images.
As the elyra maintainers, we cannot guess what the configuration required to connect to a runtime deployed on the user environment, so unfortunately we cannot provide a sample runtime configuration. But we can guess some widely used runtime-images that can be useful for users and allow them to use elyra out of the box, even if they only want to run local pipelines.
The thing here is probably that we do this every day, so we know what and where to do it with our eyes closed. New users will be overwhelmed with the required steps to run a pipeline, our sample pipelines will not work as there is not going to be any runtime-image to use, etc and they will just give up.

I find the requirement of a docker image for all generic nodes knowing I want to run the pipeline locally to be my number one pet peeve about Elyra!  I really wish this requirement could be relaxed until the time of submission when the actual runtime is determined.  Or perhaps we could relax the requirement if Generic Pipeline is selected since those can only use generic components.  We really need a runtime configuration meta-property like "require-images-on-generic-components", then, by promoting Local to its own runtime (here we are again!) we could make the proper enforcement.  (This would also argue for some client-side validation to improve UX.)
If we could relax the runtime-image requirement on generic nodes so that its enforcement is a function of runtime selection, then I think this would allow a generic pipeline to be run out-of-the-box.

Regarding the removal of the system-owned runtime-image metadata instances, I think providing a table of parameters for CLI elyra-metadata install runtime-image commands for each of the previous system-owned images would be sufficient - especially given users will typically want to use their own images and many of these will likely cease to be available due to the Docker policy changes.
I think we're going to run into issues with these anyway once jupyter_core changes the default to prefer the platform directories (i.e., {sys.prefix}/share/jupyter/metadata/runtime-images) - which will occur in its 6.0 release but can be used now.  When platform directories are preferred, I believe users will be able to update "system-owned" metadata instances in place since we rely on the ordering of directories - so these "system-owned" instances are a hack at best (and always have been since directory preference orders are already configurable).

I find the requirement of a docker image for all generic nodes knowing I want to run the pipeline locally to be my number one pet peeve about Elyra! I really wish this requirement could be relaxed until the time of submission when the actual runtime is determined.

I am ok with this, the issue is that we have the "as you build" checks that mark nodes as red when they are not ready for submission, more like a compilation check before you run, to avoid only seeing 10 issues when you run and we will lose that.


[#13322] Deprecate ModuleCommandExtensions

Closes #13322

I wondered the same thing, but until we have #13247 in 16.0 it's not actually possible to migrate, so I was thinking we would document this as part of the 16.0 migration guide.


'NoneType' object has no attribute 'attrs'

I'm trying import-export on Django 3, python 3.8, on a fairly large site with lots of models, but I encounter this on the first class inspected in this code, which is import_export.resources.Resource.
    from import_export import resources
  File "/usr/lib/python3.8/site-packages/import_export/resources.py", line 234, in <module>
    class Resource(metaclass=DeclarativeMetaclass):
  File "/usr/lib/python3.8/site-packages/import_export/resources.py", line 202, in __new__
    setattr(meta, option, getattr(options, option))
AttributeError: 'NoneType' object has no attribute 'attrs'

When I add code to avoid that (if options:), I then encounter
    from import_export import resources
  File "/usr/lib/python3.8/site-packages/import_export/resources.py", line 986, in <module>
    class ModelResource(Resource, metaclass=ModelDeclarativeMetaclass):
  File "/usr/lib/python3.8/site-packages/import_export/resources.py", line 914, in __new__
    new_class = super().__new__(cls, name, bases, attrs)
  File "/usr/lib/python3.8/site-packages/import_export/resources.py", line 183, in __new__
    setattr(meta, option, getattr(options, option))
AttributeError: 'NoneType' object has no attribute 'attrs'

Again a guard if options: around that code helps.

Django Import Export: 2.0.2, 2.3.0, master
Python 3.8
Django 3.0.8

Odd packages which might be related are django-compat-patcher, and forbiddenfruit.

Interesting. Do you think you can create a reproducible example? Im wondering if its a django-import-export issue, or maybe as you point out, a conflict with another package.

We also found this problem, in our case the conflicting module was definitely forbiddenfruit, just importing it shows the problem, we added if options and meta: like @jayvdb and it worked trough eventually we did a change to forbiddenfruit since we have it vendored.

@juanjux , is your forbiddenfruit modification public?  Seeing it might highlight, or at least help narrow down, the cause.

On forbiddenfruit.py we replaced:
calling_frame = inspect.currentframe().f_back
return sorted(calling_frame.f_locals.keys())

with:
return  __builtin__.dir(obj)

So it's doing a dir(None) but that's ok for our use case of the module.

It's easy to reproduce when testing django-import-export

pip install forbiddenfruit
in test_resources.py, add import forbiddenfruit
Run tests

tests will crash with the error message.

Fixed in #1325


[audio] tag not working when there are spaces in the filename

From @jeroenpraat on December 27, 2014 15:54
When an audio tag and audio file name is formatted like this: [audio]Artist - Song.mp3[/audio] the html5 audio player is not displayed (Firefox) or empty (Chromium). When you replace the spaces manually with %20 it works.  [audio]Artist%20-%20Song.mp3[/audio].
Copied from original issue: friendica/red#774

From @pafcu on December 28, 2014 10:23
Spaces are technically not allowed in urls, which is probably why it's not working. Since it's so common to have spaces in names, and there's not really any risk for error, I made spaces work too now.

Thanks for this @pafcu !


Ensure corrected p-values are always <= 1.0

Reference issue
Fixes GH-7354.
What does this implement/fix?
Clips p-values produced by Bonferroni correction at 1.0

Whoops. There's a bug and the change breaks another test locally. Will look into it.

Ok so the new test function test_bonferroni_pval_clip(), which checks if the p-vals don't exceed 1, is implicitly also included in the modified test_multi_pval_correction() function (line 34). So there is a little "test redundancy" here now; however I propose to keep test_bonferroni_pval_clip() as it's a very straightforward function and not as convoluted as test_multi_pval_correction(). WDYT?

Thanks @hoechenberger


feat(providers): Update providers to return list of services for a service account

Please describe the motivation for this PR and provide enough
information so that others can review it.
Providers should return all associated services for a service account, not just 1.
Please mark with X for applicable areas.

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Control Plane          [X]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests / CI System      [ ]
Other                  [ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?
No

Codecov Report

Merging #1586 into main will increase coverage by 10.15%.
The diff coverage is 64.92%.

@@             Coverage Diff             @@
##             main    #1586       +/-   ##
===========================================
+ Coverage   44.39%   54.54%   +10.15%
===========================================
  Files         111      113        +2
  Lines        4690     4818      +128
===========================================
+ Hits         2082     2628      +546
+ Misses       2608     2188      -420
- Partials        0        2        +2

Impacted Files
Coverage Δ

cmd/cli/dashboard.go
0.00% <ø> (ø)

cmd/cli/env.go
0.00% <0.00%> (ø)

cmd/cli/mesh.go
0.00% <0.00%> (ø)

cmd/cli/mesh_delete.go
40.00% <0.00%> (ø)

cmd/cli/namespace.go
0.00% <0.00%> (ø)

cmd/cli/namespace_list.go
37.50% <0.00%> (ø)

cmd/cli/osm.go
0.00% <ø> (ø)

cmd/cli/version.go
0.00% <0.00%> (ø)

cmd/osm-controller/validate.go
0.00% <0.00%> (ø)

pkg/catalog/catalog.go
100.00% <ø> (+5.55%)
:arrow_up:

... and 65 more

Continue to review full report at Codecov.

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


auth:setup doesn't provides user hook

Hello, just played with auth and noticed a lack of User Hook, for encripting password.
If it's not there passwords are saved without hasing.. and when trying to validate it gives an error.
I havent found how to disable these, so i think it would be better to provide user hook with user model on auth:setup

@muxahuk Nice catch.


[FR] Deduplicate vendored dependencies

What's the problem this feature will solve?
Currently, pkg_resources, setuptools and setuptools._distutils all have their own _vendor directories. In many cases, the vendored packages overlap — especially packaging is now vendored 3 times. Besides potential version mismatches such as #4323, it also increases the disk space use and wheel size. From a quick and dirty deduplication attempt, compressed wheel goes down from 920 KiB to 710 KiB, and the install from 3.5 MiB to 2.7 MiB.
Describe the solution you'd like
I think it would make sense to establish some kind of reuse hierarchy, and e.g. given that setuptools imports stuff from pkg_resources anyway, make them reuse the vendored packages from pkg_resources as well, and only vendor these that aren't common to both.
Alternative Solutions
No response
Additional context
No response
Code of Conduct

[X] I agree to follow the PSF Code of Conduct

Thanks for the suggestion.
Since pkg_resources and distutils is deprecated, I'd like to keep these concerns separate.
Distutils needs its own vendored dependencies because it's still tested independently in pypa/distutils.
I'm trying to make setuptools not depend at all on pkg_resources. The long-term strategy is to stop vendoring packages altogether, or at least declare the dependencies normally and only provide vendored copies as a fallback. Here's how I'm thinking that would work:

vendored dependencies would only be supported when installed on the file system (limited or no support for zip-based or other alternative installs).
vendored dependencies would be stored unaltered to a directory or set of directories that would be added to the end of sys.path when necessary (bootstrapping), but naturally installed dependencies would be preferred.
These vendored dependencies might be provided in a top-level package that could be shared between pkg_resources and setuptools (_setuptools_vendored?).

This approach would make setuptools largely behave as a naturally-installed package (no vendoring), but provide the dependencies for bootstrapping purposes (maybe only opt-in).
Let's focus on those efforts and set aside 1MiB of overhead until we've tackled these other concerns.

Sure, that would work as well. In fact, I think it would make devendoring much easier than it is now.


separate server-side code

it will help to separate the front-end and back-end code, by creating a new script for the server-side functions that is then sourced at the top of app.R.

Thanks @juniperlsimonis, Covered in c30fd80d9af1fe9a741355297c1635506ad55d9f


feat: ldv sales from reassessments - 1636

feat: adds beginning of service for adjusting credits based on reassessment, LDV sales from reassessments are now being written to the organizationLdvSales table and are displayed on the organization page and should be pulled into future model year reports

Removed consider_supplemental flag from get_ldv_sales function so that lists not containing the consider_supplemental? parameter will still grab reassessment data if the reassessment exists in an approved state and contains ldv sales data.


[@angular-devkit/schematics] Getting package manager info from @angular/cli

🚀 Feature request
Command (mark with an x)

[x] new
[ ] build
[ ] serve
[ ] test
[ ] e2e
[x] generate
[x] add
[x] update
[ ] lint
[ ] extract-i18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Description
I'm currently developing a schematics that needs to know which package manager the user is using for its project. I found that the logic of detection the package manager already exists within the ng cli (reading from angular.json config or heuristic from workspace), but does not seem to be exposed to the schematics context or options (AFAIK).
Describe the solution you'd like
I would like a way to get the package manager information when the schematics is running in an ng cli context without having to duplicate all the the logic in the schematics itself.
Describe alternatives you've considered
Not sure what would be the best option here: pass on the packageManager info as a schematics option directly, or expose the package manager detection tools directly as an import'able package in your schematics, or something else.
 Have you considered any alternative solutions or workarounds?

I am curios to know what is the use-case that you need to know package manager.

I'm currently building a tool to generate devcontainers configuration for JS projects (incl. Angular with ng add), and to properly set up the container I need to know which package manager the user would like to use.
Currently I've implemented my own logic for that especially as I also would like to support pnpm outside Angular projects, so consider this request as nice-to-have. I made the Angular logic a bit simpler than what's currently implemented in ng CLI, here's my code for anyone's interested:
export function getPackageManager(tree: Tree): string {
  let packageManager = getPackageManagerFromConfig(tree);
  if (packageManager) {
    return packageManager;
  }

  const hasYarnLock = tree.exists('yarn.lock');
  const hasNpmLock = tree.exists('package-lock.json');

  packageManager = hasYarnLock && !hasNpmLock ? 'yarn' : 'npm';
  return packageManager;
}

function getPackageManagerFromConfig(tree: Tree): string | null {
  const config = tree.read('angular.json');
  if (!config) {
    return null;
  }

  const angularJson = JSON.parse(config.toString()) as Record<string, any>;
  return (angularJson.cli?.packageManager as string) ?? null;
}


TestCloseHangingIntegration bug

Approximately 1/3 tries of running TestCloseHangingIntegration does not end at all. That's because program gets stuck in this for loop:
func (c *Conn) sendController() {
	for {
		if size := c.Waiting(); size < targetWaiting {
			break
		}
		time.Sleep(50 * time.Millisecond)
	}
}

Where size = max uint
That's because metrics.InQueue decreases when it is equal to 0.
Interestingly enough, I cannot observe such behavior when I comment out this line in TestCloseHangingIntegration:
h.exec("DROP KEYSPACE mykeyspace")

That's because we decrement  inQueue while receiving closeRequest connWriter::loop(), which is fatal!
r := <-c.requestCh
c.metrics.InQueue.Dec()
if r == _connCloseRequest {
    return
}

Let's decrement after checking closeRequest.

Nevertheless, I don't see why such behavior is observed only when we drop keyspace.
My guess is that executing extra query before closing connection gives enough time for all the other request to finish, so that inQueue is equal to 0 and it overflows while decrementing.


sorry for being the first

Hey, glad I found this! All I'm getting is a black screen, I've set it up exactly how it should be with no errors on start up. .xauthority is all good too, i just had to chmod it.  I'm on an s22 android 14. Gotta be something easy. Please let me know if you need more info or any advice for someone who tends to complicate things for no reason. Thanks and looking forward to using this! 😀

Same ^^


Change MongoController to MongoService

Minor change, just for better naming conventions we have decided to convert MongoController to MongoService as we want controllers to be specific to endpoint logic and endpoints in general.

Maybe rename it to MongoRepository

Maybe rename it to MongoRepository

@Evanlab02 Can discuss whenever we get a chance to chat again 😄
Not really critical and should be a quick change that we can do together :)


stages/ostree.deploy.container: allow deploying from container

The ostree.deploy stage now accepts either a ostree input:
      - type: org.osbuild.ostree.deploy
        options:
          osname: fedora-coreos
          remote: fedora
          mounts:
            - /boot
            - /boot/efi
          kernel_opts:
            - rw
            - console=tty0
            - console=ttyS0
            - ignition.platform.id=qemu
            - '$ignition_firstboot'
        inputs:
          commits:
            type: org.osbuild.ostree
            origin: org.osbuild.source
            mpp-resolve-ostree-commits:
              commits:
                - ref: fedora/x86_64/coreos/stable
                  remote:
                    url: https://kojipkgs.fedoraproject.org/ostree/repo/

or a containers input:
      - type: org.osbuild.ostree.deploy.container
        options:
          osname: fedora-coreos
          target_imgref: ostree-remote-registry:fedora:quay.io/fedora/fedora-coreos:stable
          mounts:
            - /boot
            - /boot/efi
          kernel_opts:
            - rw
            - console=tty0
            - console=ttyS0
            - ignition.platform.id=qemu
            - '$ignition_firstboot'
        inputs:
          images:
            type: org.osbuild.containers
            origin: org.osbuild.source
            mpp-resolve-images:
              images:
                - source: registry.gitlab.com/redhat/services/products/image-builder/ci/images/fedora-coreos
                  tag: stable

In the containers input case we will run ostree container image deploy wheras for ostree commits input we will continue to execute ostree admin deploy.
Co-authored-by: Dusty Mabe<EMAIL_ADDRESS>and Luke Yang @lukewarmtemp

Marking as draft since this builds on top of https://github.com/osbuild/osbuild/pull/1399

One thing we will lose vs current FCOS-and-derivatives is https://github.com/coreos/fedora-coreos-tracker/blob/main/internals/README-internals.md#aleph-version right?
We are actually planning potentially grow at least test-level dependencies on this for OCP as part of bootimage update work.  (A while ago I did https://github.com/openshift/machine-config-operator/pull/2994 which is currently just informative)
I think we'll just have to keep this in mind?  But maybe it would make sense to have an aleph stage.
Incidentally, bootc has its own aleph which has less stuff basically for the same reason as here - the input is a container image.

I think we'll just have to keep this in mind? But maybe it would make sense to have an aleph stage.

Indeed. I would look at this PR as the start. There's a whole host of other things that need to be tidied up or added (one example is a bootupd stage) that will get unlocked after this merges.

Indeed. I would look at this PR as the start. There's a whole host of other things that need to be tidied up or added (one example is a bootupd stage) that will get unlocked after this merges.

Not to go too far off but...as I've been thinking about things here I would like to consider that we add a bootc install-to-filesystem stage actually.  That would drive us to embed the default base partitioning configuration inside the OS image, which is what I think we want long term.
(If for example I want to change the default for my OS installs from xfs to ext4 or so, that'd just be flipping https://github.com/containers/bootc/blob/c9f224cbb2d3fc3040410125c234c30e8b322cb9/lib/src/install/00-defaults.toml#L3 in a drop-in in my container build)
The reason I mention this is because bootc install-to-filesystem will also take care of the bootupd stuff too.

Yeah this merged! https://github.com/osbuild/osbuild/pull/1399
Ref https://github.com/osbuild/osbuild/pull/1402#issuecomment-1760299410
Is there anything we can do to test or move this forward? Happy to help!

Did a new upload here with some fixes and rebased on top of latest main branch.
I don't know if we want the last commit in this patchset to merge in (cc @achilleas-k).

Looking at the stage in its final form here I'm starting to wonder if it would be a better idea to split it into a separate one org.osbuild.ostree.container.deploy.  That way we could avoid conditional behaviour based on input type, ref being needed only for one input type, the whole target and verification discussion above, etc.  A separate stage would have some minor duplicate code (the main() part of the current stage) but the freedom to redefine the schema would let us communicate the purpose of all the options more easily, like having a target-imgref option instead of remote.

@dustymabe had a chat with some people from the team and we've agreed that it makes more sense in terms of osbuild's design for this to be a separate stage.  Like I mentioned yesterday:

It gets rid of automagic behaviour that switches based on input type, which isn't something we've done before and is hard to communicate.
The easiest stages to work with are generally the ones that are thin wrappers around the command they shell out to.
The stage options for the two cases are different enough that it makes it simpler to verify with two separate schemas, rather than having things like oneOf, inter-option dependencies, and options with duplicate meaning.

Also, as a correction to my previous comment, the name for the new stage should be org.osbuild.ostree.deploy.container.  That way, the stage gets namespaced under the deploy command, making it clear that it's associated (or an alternative to) the original org.osbuild.ostree.deploy stage.

Sound good @achilleas-k, we'll try to accommodate.

OK. We added a new push here that creates a new org.osbuild.ostree.deploy.container stage.

I have a couple of inline comments but also one more general one: since the org.osbuild.ostree.deploy stage isn't affected by this PR, can you revert the changes to it to avoid any confusion?

My preference is that we keep the changes to the deploy stage primarily to keep the deploy and deploy.container stages diff-able. Right now it's really easy to vimdiff the two files and see exactly where they differ.
I honestly prefer keeping the code in a single stage, but if we have to break them out preserving this diff-able ability I think makes it easier to manage. WDYT?

I'd also like the git history to be cleaned up to only have the introduction of the new stage and tests.

Yes. We can simplify things here. The reason we didn't squash to begin with: I was thinking maybe we keep the git history around in case we change our minds in the future and want the deploy stage to accept ostree or container as input.

I have a couple of inline comments but also one more general one: since the org.osbuild.ostree.deploy stage isn't affected by this PR, can you revert the changes to it to avoid any confusion?

My preference is that we keep the changes to the deploy stage primarily to keep the deploy and deploy.container stages diff-able. Right now it's really easy to vimdiff the two files and see exactly where they differ.

That's understandable, but in that case, let's make sure there were no leftover functional changes.  Should be easier to see when the history is cleaned up.

I honestly prefer keeping the code in a single stage, but if we have to break them out preserving this diff-able ability I think makes it easier to manage. WDYT?

I'd also like the git history to be cleaned up to only have the introduction of the new stage and tests.

Yes. We can simplify things here. The reason we didn't squash to begin with: I was thinking maybe we keep the git history around in case we change our minds in the future and want the deploy stage to accept ostree or container as input.

It was convenient for reviewing the change from the previous state, but I think it might make the history of the ostree.deploy confusing if we needed to to through it for whatever reason.
As for accepting a container in the ostree.deploy stage, since we're splitting them up now, I don't see why we would merge the two, unless the interface to the two commands got unified in the future, in which case the stage would be different anyway.

OK I pushed up an update that hopefully cleans up the git history a bit. LMK if that helps!

Note: I'm still not sure if we want the last commit. They are there to illustrate some usage of the new code, but not sure we need or want them.

Note: I'm still not sure if we want the last commit. They are there to illustrate some usage of the new code, but not sure we need or want them.

We should add the current fedora-coreos container to our GitLab container registry, use that for the test manifest, and update the test script at test/cases/ostree-images to build the new manifest as part of CI.

Note: I'm still not sure if we want the last commit. They are there to illustrate some usage of the new code, but not sure we need or want them.

We should add the current fedora-coreos container to our GitLab container registry, use that for the test manifest, and update the test script at test/cases/ostree-images to build the new manifest as part of CI.

Pushed the current quay.io/fedora/fedora-coreos:stable to our gitlab container registry as docker://registry.gitlab.com/redhat/services/products/image-builder/ci/images/fedora-coreos:stable (https://gitlab.com/redhat/services/products/image-builder/ci/images/container_registry/5710257).
You can use that in the manifest now and enable it in the test script so we can build the sample manifest in CI with the same image every time.

Note: I'm still not sure if we want the last commit. They are there to illustrate some usage of the new code, but not sure we need or want them.

We should add the current fedora-coreos container to our GitLab container registry, use that for the test manifest, and update the test script at test/cases/ostree-images to build the new manifest as part of CI.

Pushed the current quay.io/fedora/fedora-coreos:stable to our gitlab container registry as docker://registry.gitlab.com/redhat/services/products/image-builder/ci/images/fedora-coreos:stable (gitlab.com/redhat/services/products/image-builder/ci/images/container_registry/5710257).

You can use that in the manifest now and enable it in the test script so we can build the sample manifest in CI with the same image every time.

OK cool. I'll update it.
@lukewarmtemp should we just drop fedora-ostree-container-deploy.mpp.yaml now or does that still have value?

should we just drop fedora-ostree-container-deploy.mpp.yaml now or does that still have value?

Let's just drop it since I don't seem many use cases for this example outside of our initial need for testing.

ok I did a new push. I think we are pretty close so I'm lifting draft on this PR.

So testing this via a Silverblue Asahi Remix I'm working on, fails at this point:
⏱  Duration: 0s
org.osbuild.ostree.deploy.container: db4a447eda1413d32197f49e4fbcbb619e2283d0b73bb6fafdd218509f42d6e1 {
  "osname": "silverblue-asahi",
  "target_imgref": "ostree-remote-registry:quay.io/ecurtin/silverblue-asahi:39",
  "mounts": [
    "/boot",
    "/boot/efi"
  ],
  "kernel_opts": [
    "rw",
    "console=tty0",
    "console=ttyS0",
    "ignition.platform.id=qemu",
    "$ignition_firstboot"
  ]
}
/usr/lib/tmpfiles.d/journal-nocow.conf:26: Failed to replace specifiers in '/var/log/journal/%m': No such file or directory
/usr/lib/tmpfiles.d/systemd.conf:23: Failed to replace specifiers in '/run/log/journal/%m': No such file or directory
/usr/lib/tmpfiles.d/systemd.conf:25: Failed to replace specifiers in '/run/log/journal/%m': No such file or directory
/usr/lib/tmpfiles.d/systemd.conf:26: Failed to replace specifiers in '/run/log/journal/%m/*.journal*': No such file or directory
/usr/lib/tmpfiles.d/systemd.conf:29: Failed to replace specifiers in '/var/log/journal/%m': No such file or directory
/usr/lib/tmpfiles.d/systemd.conf:30: Failed to replace specifiers in '/var/log/journal/%m/system.journal': No such file or directory
/usr/lib/tmpfiles.d/systemd.conf:32: Failed to replace specifiers in '/var/log/journal/%m': No such file or directory
/usr/lib/tmpfiles.d/systemd.conf:33: Failed to replace specifiers in '/var/log/journal/%m/system.journal': No such file or directory
ostree container image deploy --imgref=ostree-unverified-image:dir:/tmp/tmpae4toj1l/image --stateroot=silverblue-asahi --target-imgref=ostree-remote-registry:quay.io/ecurtin/silverblue-asahi:39 --karg=rw --karg=console=tty0 --karg=console=ttyS0 --karg=ignition.platform.id=qemu --karg=$ignition_firstboot --sysroot=/run/osbuild/tree
error: Performing deployment: Deploying tree: opendir(var): No such file or directory
Traceback (most recent call last):
  File "/run/osbuild/bin/org.osbuild.ostree.deploy.container", line 139, in <module>
    r = main(stage_args["tree"],
        ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/run/osbuild/bin/org.osbuild.ostree.deploy.container", line 134, in main
    ostree_container_deploy(tree, inputs, osname, target_imgref, kopts)
  File "/run/osbuild/bin/org.osbuild.ostree.deploy.container", line 108, in ostree_container_deploy
    ostree.cli("container", "image", "deploy",
  File "/run/osbuild/lib/osbuild/util/ostree.py", line 200, in cli
    subprocess.run(["ostree"] + args,
  File "/usr/lib64/python3.11/subprocess.py", line 571, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['ostree', 'container', 'image', 'deploy', '--imgref=ostree-unverified-image:dir:/tmp/tmpae4toj1l/image', '--stateroot=silverblue-asahi', '--target-imgref=ostree-remote-registry:quay.io/ecurtin/silverblue-asahi:39', '--karg=rw', '--karg=console=tty0', '--karg=console=ttyS0', '--karg=ignition.platform.id=qemu', '--karg=$ignition_firstboot', '--sysroot=/run/osbuild/tree']' returned non-zero exit status 1.

⏱  Duration: 17s

Failed

it's probably more correct to report this in the ostree space, but just leaving it here for awareness.

Thanks I'll try that.


[Event Request] codeunit 6620 "Copy Document Mgt." - OnCopyFromSalesToPurchDocOnBeforePurchaseHeaderModify

Can we please get the following event?
procedure CopyFromSalesToPurchDoc(VendorNo: Code[20]; FromSalesHeader: Record "Sales Header"; var ToPurchHeader: Record "Purchase Header")
var
    FromSalesLine: Record "Sales Line";
    ToPurchLine: Record "Purchase Line";
    NextLineNo: Integer;
begin
    if VendorNo = '' then
        Error(Text011);

    with ToPurchLine do begin
        LockTable();
        OnCopyFromSalesToPurchDocOnBeforePurchaseHeaderInsert(ToPurchHeader, FromSalesHeader);
        ToPurchHeader.Insert(true);
        ToPurchHeader.Validate("Buy-from Vendor No.", VendorNo);
        OnCopyFromSalesToPurchDocOnBeforePurchaseHeaderModify(ToPurchHeader, FromSalesHeader); //NEW Event
        ToPurchHeader.Modify(true);
        FromSalesLine.SetRange("Document Type", FromSalesHeader."Document Type");
        FromSalesLine.SetRange("Document No.", FromSalesHeader."No.");

    [...]

end;

[IntegrationEvent(false, false)]
local procedure OnCopyFromSalesToPurchDocOnBeforePurchaseHeaderModify(var ToPurchaseHeader: Record "Purchase Header"; FromSalesHeader: Record "Sales Header")
begin
end;

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


RuntimeError: cuDNN error: CUDNN_STATUS_INTERNAL_ERROR

Traceback (most recent call last):
File "train.py", line 61, in
main(config, args.resume)
File "train.py", line 42, in main
trainer.train()
File "pytorch_segmentation-master/base/base_trainer.py", line 101, in train
results = self._train_epoch(epoch)
File "/pytorch_segmentation-master/trainer.py", line 72, in _train_epoch
loss.backward()
File "/anaconda3/envs/water/lib/python3.6/site-packages/torch/tensor.py", line 107, in backward
torch.autograd.backward(self, gradient, retain_graph, create_graph)
File "/anaconda3/envs/water/lib/python3.6/site-packages/torch/autograd/init.py", line 93, in backward
allow_unreachable=True)  # allow_unreachable flag
RuntimeError: cuDNN error: CUDNN_STATUS_INTERNAL_ERROR

Hi, this issue is due to some error when initializing CUDNN, I think it is related to your setup.
I would suggest reinstalling PyTroch and/or CUDA and trying again.

网上说的都没用，我昨天遇到这个问题等半个小时自动就好，应该是之前GPU占用正在释放


Fixed an apparent type in the SSL_CTX_set_security_level documentation

Muphry's Law strikes: should "apparent type" be "apparent typo"?

+1

fixed in a6099d4 thanks.


Namespace list does not populate

This is due to the fact that the namespace report is only available after the AEP sampling job has run.
The Application code needs to be updated to look at the entire list of identity namesapces.


Randomly blurred document

I'm using the jsPDF package to generate PDF document based on img from the web page.
The img are in a div where they are resized to a lower with and height (but still keeping the same ratio A4).
I do the basic following:

create an empty document
add a page
add the image
save the doc

My problem is that randomly for some reason, the pdf generated is totally blurred.
When I click on the picture, it opens the visualizer (viewers) and no pictures are blurred (all based on the same src) only the export is failing.
What could possibly be the reason? If the pictures are loaded well why is it blurred?

how are adding the content to the page?
Just be aware that .addHTML() ... is now depricated.

Hello @funnykanth, thank you for your answer.
The code is
I put you the entire code I'm using (in vue.js):
  extractPDF: function() {
        let doc = null;

        let isLandscape = page => {
          return this.file.orientation[page] == 90 ||
            this.file.orientation[page] == 270
            ? "l"
            : "p";
        };

        //NOTE: Add all pages:
        let width = 0;
        let height = 0;
        for (var i = 0; i < this.file.checked.length; i++) {
          let page = this.file.checked[i];
          let element = this.$el.querySelector("#page-" + page);

          let orientation = isLandscape(page);
          if (i == 0) {
            doc = new jsPDF({
              orientation: orientation
            });
          } else {
            doc.addPage(null, isLandscape(page));
          }
          width = doc.internal.pageSize.getWidth();
          height = doc.internal.pageSize.getHeight();
          if (orientation == "p") {
            if (this.file.orientation[page] == 0)
              doc.addImage(element, "JPEG", 0, 0, width, height);
            else if (this.file.orientation[page] == 180)
              doc.addImage(
                element,
                "JPEG",
                width,
                -height,
                width,
                height,
                null,
                null,
                -180
              );
          } else if (orientation == "l") {
            if (this.file.orientation[page] == 90)
              doc.addImage(
                element,
                "JPEG",
                0,
                -width,
                height,
                width,
                null,
                null,
                -90
              );
            else if (this.file.orientation[page] == 270)
              doc.addImage(
                element,
                "JPEG",
                width,
                -(width - height),
                height,
                width,
                null,
                null,
                -270
              );
          }
        }
        //NOTE: Convert to pdf and save
        doc.save(this.file.name + this.indexValue + ".pdf");
    },

Basically its addImage function used.

Can you condense your code into a minimal repro? Optimally, include one of the images that is blurred. Please also test with the current master branch.

Sure: https://github.com/mathias22osterhagen22/jsPDF-issues2773
Problem is that the image is not blurred all time, I even didn't succeed thousands of times to reproduce. It just occurs randomly on my user's side.
I would want to know in which case jsPDF could add a blurred image to be added to the document.

I've tried your sample a couple of times but I can't reproduce the issue. I assume this is some kind of browser or timing issue. In which browser could you reproduce it? If I'm not able to reproduce the issue, I'm afraid I can't do much about this. Especially since I think this is not a bug in jsPDF. Maybe you can try debugging yourself?

They are using Chrome in a really special environment that I can't access (computers made to only remote windows access session), I tried to debug with puppeteer, like keep repeating the action in a loop. Impossible to reproduce.
I was thinking too that could be a browser timing issue, in chrome you can debug turning your connection slower :

Still the same, jsPdf is always waiting at the end of the download before generating the pdf.
I was maybe expecting chrome to cache the images "sometimes" because in fact they are already loaded twice on the same page (one time for the page and another for the "viewers" in a div hidden (not really clean but easier to fix)) and then by clicking on the "export button" it makes a "get" request for each image (jsPdf fire it).
Then could it be possible than chrome answer to jsPdf some low-quality image cached instead of making a real get?
This issue is really curious I think to solve it would make everybody get some knowledge haha.

Dear @HackbrettXXX , we finnaly succed to find the problem this morning you will never guess.
Indeed it's not linked with the jsPDF library even if this blur document made me thought that.
There is what happened :

The user go on the website that is protected by a self security, the user then accept the untrusted certificate
The user go to process the file (convert img to pdf) he can see the dashboard that you can find above in our discussion. He can see well the pictures nothing to signal.
After X time the browser (chrome) "UNACCEPT" automatically in background the untrusted certificate.
Click on the extract button result into a 404 error:

The result document is completely blur:

The point was that I was thinking that if jsPDF get a 0k image by the ajax call it would result into an empty document, I don't know at all how jsPDF could get this low version image.
I'm supposing that the library is making some cache of the already loaded picture? Else it means that is chrome that give to the lib some thumbnail cache instead of a 0k image data.
I let this issue open just time that someone answers about this two last questions.

Glad you found the root of the issue. jsPDF caches the image only if the same image is included multiple times into one PDF. Otherwise it does a fresh XHR.

Otherwise it does a fresh XHR.

Sorry to re-open, but how it is possible that I get a blurry image if it does a fresh XHR?
Example:

3 images:

Turn it into pdf (with self signed certificat warning (see above)):

Result pdf :

Is there an explanation? Is jsPdf having a special behavior if the data from the HXR are 0k size? Like trying to manage in another way to get the image bytes?

jsPDF caches the image only if the same image is included multiple times into one PDF.

PS: I tried adding 3 times in a row the same image (on one new page each time) it makes a fresh HXR each time without caching.

I think someone needs to have a closer look at this. However, this currently has no high priority for the next release, as there are far more important open issues. I'm gonna reopen this so it is not forgotten.


Fix the error when creating a final print template after a title change recommendation

@CatoTH can you confirm that this fixes the isse?
In current master, you cannot create a modified final version of the title of a motion has change recommendations.


[NEW FEATURE] Have a printable version

What feature would you like?
Be able to print
What problem would it solve?
Who is the target audience?
Where does it differ from what we already have?
Additional context

We have an initial version