libmbim: 1.28.2 -> 1.28.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/libmbim/versions.
meta.description for libmbim is: Library for talking to WWAN modems and devices which speak the Mobile Interface Broadband Model (MBIM) protocol
meta.homepage for libmbim is: https://www.freedesktop.org/wiki/Software/libmbim/
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.28.4 with grep in /nix/store/avn7d95ik2d7yn7fmdlch4b46l3m0cjd-libmbim-1.28.4
found 1.28.4 in filename of file in /nix/store/avn7d95ik2d7yn7fmdlch4b46l3m0cjd-libmbim-1.28.4

Rebuild report (if merged into master) (click to expand)

682 total rebuild path(s)

682 package rebuild(s)

First fifty rebuilds by attrpath
ChowKick
CuboCore.coretoppings
adapta-gtk-theme
adwaita-qt6
airgeddon
alfis
alice-tools-qt6
almanah
apache-directory-studio
apostrophe
appgate-sdp
astroid
autosuspend
aws-workspaces
balsa
bambootracker-qt6
beamerpresenter
beamerpresenter-mupdf
beamerpresenter-poppler
bespokesynth
bespokesynth-with-vst2
birdfont
blueman
bookworm
breath-theme
bubblemail
calcmysky
calibre
calligra
calls
cambalache
cargo-tauri
cawbird
chatty
chirp
cinnamon.cinnamon-common
cinnamon.cinnamon-control-center
cinnamon.cinnamon-gsettings-overrides
cinnamon.cinnamon-screensaver
cinnamon.cinnamon-session
cinnamon.cinnamon-settings-daemon
cinnamon.nemo-fileroller
cinnamon.nemo-with-extensions
cinnamon.pix
cinnamon.xreader
cinny-desktop
citrix_workspace
citrix_workspace_23_02_0
clash-verge
claws-mail

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/avn7d95ik2d7yn7fmdlch4b46l3m0cjd-libmbim-1.28.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A libmbim https://github.com/r-ryantm/nixpkgs/archive/9eb7621cbb8d0ae7a140c9516f99c6cbdc844095.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/avn7d95ik2d7yn7fmdlch4b46l3m0cjd-libmbim-1.28.4
ls -la /nix/store/avn7d95ik2d7yn7fmdlch4b46l3m0cjd-libmbim-1.28.4/bin

Pre-merge build results
NixPkgs review skipped

Maintainer pings
cc @jtojnar for testing.

@GrahamcOfBorg eval


Skill section is not responsive on iPhone

In the skills section, Skill Cloud appears weirdly and is not responsive.

This issue is from media queries that have been fixed I will deploy the fix in a couple of minutes.


panic: interface conversion: *flatbuffers.Builder is not proto.Message: missing method ProtoMessage

I was using flatbuffers as a serialization mode, but this exception occurred while compiling.
`
panic: interface conversion: *flatbuffers.Builder is not proto.Message: missing method ProtoMessage
goroutine 1 [running]:
panic(0x89bc80, 0xc08218e0c0)
E:/Go1.6.2/src/runtime/panic.go:481 +0x3f4
google.golang.org/grpc.protoCodec.Marshal(0x92e2c0, 0xc0820fc4e0, 0x0, 0x0, 0x0, 0x0, 0x0)
E:/goapp/src/google.golang.org/grpc/rpc_util.go:70 +0x78
google.golang.org/grpc.(*protoCodec).Marshal(0xbd43c8, 0x92e2c0, 0xc0820fc4e0, 0x0, 0x0, 0x0, 0x0, 0x0)
:34 +0xc5
google.golang.org/grpc.encode(0x3a0268, 0xbd43c8, 0x92e2c0, 0xc0820fc4e0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
E:/goapp/src/google.golang.org/grpc/rpc_util.go:268 +0xbb
google.golang.org/grpc.sendRequest(0x3a01b8, 0xc08200a278, 0x3a0268, 0xbd43c8, 0x0, 0x0, 0xc0820f34a0, 0x3a1670, 0xc0821583c0, 0x92e2c0, ...)
E:/goapp/src/google.golang.org/grpc/call.go:117 +0x232
google.golang.org/grpc.invoke(0x3a01b8, 0xc08200a278, 0x99f660, 0x1c, 0x92e2c0, 0xc0820fc4e0, 0x8c8740, 0xc08214ee00, 0xc0821066c0, 0x0, ...)
E:/goapp/src/google.golang.org/grpc/call.go:235 +0xd81
google.golang.org/grpc.Invoke(0x3a01b8, 0xc08200a278, 0x99f660, 0x1c, 0x92e2c0, 0xc0820fc4e0, 0x8c8740, 0xc08214ee00, 0xc0821066c0, 0x0, ...)
E:/goapp/src/google.golang.org/grpc/call.go:143 +0x14a
/e/goproject/rpc-test-client/src/message.(*messageServiceClient).Send(0xc0820f4220, 0x3a01b8, 0xc08200a278, 0xc0820fc4e0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
e:/goproject/rpc-test-client/src/message/MessageService_grpc.go:31 +0x17b
main.main()
e:/goproject/rpc-test-client/src/app.go:67 +0x3cc
`

Found answer for this? Me to having similar problem with protoBuffers.

We are cleaning up the gRPC issue backlog and are unable to address this issue with the current information. If you are still experiencing this issue, please open the issue under grpc-go repository as it only affects the Go implementation with information on how to reproduce. Thanks!

We hit the same issue as @zplzpl @pavamana1123. Our problem was with the flatbuffer codec, or rather, the fact that we didn't instantiate the server with it.
When creating our server and connections, we switched to
var server = grpc.NewServer(grpc.CustomCodec(flatbuffers.FlatbuffersCodec{}))
var conn, err = grpc.Dial(addr, grpc.WithInsecure(), grpc.WithCodec(flatbuffers.FlatbuffersCodec{}))

I recommend going through the flatbuffers grpc go test.
The master's head test doesn't build at the time of writing, so you should checkout an earlier commit like  https://github.com/google/flatbuffers/commit/cc8424009853447b209c5d3ccb12c23a2f134fa4
In hope that this helps.
It should at least provide some reference for anyone searching for this issue.


Added code for the Max31855 sensor  v3

Code is based on the UPM code, it should work as intended.
updated the code to follow up the new sol_spi signatures.
Signed-off-by: Tomaz Canabrava<EMAIL_ADDRESS>

closing for v4...


⚠ Spryr has degraded performance

In 98960c6, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 4879 ms

Resolved: Spryr performance has improved in 429a40b after 12 minutes.


Ladder match crash at startup

Describe the bug
Once matched with someone for 1v1 ladder, game crash with the following log:
Failed to setup initial search path.

Program : Z:\home\greg\.faforever\bin\ForgedAlliance.exe
Cmd line arguments : /init init.lua /nobugreport /uef /log /home/greg/.faforever/logs/game.log /gpgnet <IP_ADDRESS>:30422 /mean 1212.68 /deviation 65.6584 /savereplay gpgnet://<IP_ADDRESS>:42631/10509631/BlackMelon.SCFAreplay /country GB /numgames 89 /team 1 /players 2

Callstack:
    unavailable.

Last 100 lines of log...

warning: Running "Z:\home\greg\.faforever\bin\init.lua" failed: cannot read init_faf.lua: No such file or directory
         stack traceback:
         	[C]: in function `dofile'
         	Z:\home\greg\.faforever\bin\init.lua(1): in main chunk

To Reproduce
Get in queue for 1v1 ladder and wait.
OS
Linux
The path Z:\ is mapped to / in wine.
Client version: 1.0.0 (and same bug with 1.0.1-RC5)
Custom games work fine, which is really weird since init.lua and init_ladder1v1.lua are identical (same content, same permissions).

I think it might be related with #1442. At least I did not face any troubles with ladder for a while.

@Brutus5000 we need to change this some day. This is the thing u tried to fix and it blew up XD

Duplicate of some other issue lemme see

https://github.com/FAForever/faf-java-api/issues/353 you also find a work arround there


Batch files for building and copying binaries to HoloToolkit-Unity

Fixes #99.
These batch files are modeled on the approach used in Sharing (BuildAll.bat, DeploySDKToUnity.bat).

Build succeeded and copy copied.


Adding Register Faces Page

Adding a skeleton for the New User registration Page.
Added link to Login Page.

Added maven ozark dependency as mentioned in blog https://ozark.java.net/download.html


Add banner saying project is archived

Contributes to #69
Preview:

https://deploy-preview-70--smi-spec.netlify.app/
https://deploy-preview-70--smi-spec.netlify.app/blog

Screenshot

/cc @nate-double-u

Looks good to me, thanks @chalin


Document how to install it, the package name

Describe the bug
This might sound like a beancounter issue, but I came from some issue where the solution had twMerge so I went and searched and found this repository.
But, maybe I'm blind, I don't see the package name anywhere.
So my suggestion is to add lines like
npm i tailwind-merge
pnpm add tailwind-merge
yarn add tailwind-merge
bun install tailwind-merge
Sometimes the packages are named differently than the repo name.
To Reproduce

Expected behavior

Environment

tailwind-merge version: [e.g. 1.13.1]

Additional context

Makes sense, will add them to the configuration docs.


Exclude Contact Us Controller from Authorization/Authentication

I have this filter in my ApplicationController and would like to add this controller so that my contact us form is not behind authentication.  Can I do something similar or is there another technique to accomplish this?
before_action :authorize, unless: :devise_controller?

You could skip the before action if it's the contact controller, which would be something like: skip_before_action :authorize, if: -> { params[:controller] == 'contact_us/contacts' }


Make it possible to use Duration instead of seconds (Carina web)

There are situations when 1 second is a long time. I would like to be able to use milliseconds and so on - it can be done with Duration

After https://github.com/zebrunner/carina-webdriver/issues/19


update rescue page to use form components

closes #984

Coverage remained the same at 86.396% when pulling 9bd0404d27593d5c3de9ae6cdc78e2b07cdf46f2 on abemassry:update-rescue-form into 8261f01c52cc918f061b36cf73a40997884f1112 on linode:master.

Coverage remained the same at 86.396% when pulling 0382b333ba09cf6c385ba86d60542a1d0b9ec079 on abemassry:update-rescue-form into 8261f01c52cc918f061b36cf73a40997884f1112 on linode:master.

Screenshot?


[BRAAV-2572] ACH Account Linking page

A page to link ach fiat account.

Minor: can we move the endpoint closer to POST /wires?

Minor: can we move the endpoint closer to POST /wires?
Please also add the endpoint to the overview page: /debug

@kristinfritsch I've added the overview of adding ach account. I am not sure where to move the ach account endpoints to tbh. ACH account can be used for making a payment and also making a payout. I think this is what we need to think a little more on where to put it.
CC: @MasterXen on the above question.


Add a guide for custom CSS

Extracted from #84.

I don't see why not. This should end up becoming external packages over time, but we'll have more control in saying "no thanks, please create a package instead" in the doc rather than in the publicly-editable wiki.

I think it should just simply stay in the repo wiki, instead of moving it here as a intermediary step.

Also added a commit to fix images:

Before
After


[FEATURE REQUEST] Add ImageBufAlgo::normalize implementation

A relatively common step when dealing with interchange of 3D file formats is normalizing certain data such as vertex normal vectors.
A parallel use-case in the 2D world would be normalizing non-standard normal map textures for compatibility with a given render engine, which provides a solid case for the addition of an ImageBufAlgo::normalize function.
Ideally, the implementation should be general enough to support images with different center values and value ranges.
Suggested interface from @lgritz :
IBA::normalize(ImageBuf& dst, const ImageBuf& src, float center = 0.0f, scale = 1.0f, ROI roi = {}, int nthreads = 0);

Herr my attempt for this function.
I expecting that user input can be RGB and RGBA, and function should allow conversion between ranges.
template<class Rtype>
static bool normalize_impl(ImageBuf& R, const ImageBuf& A, float inCenter, float outCenter, float scale, ROI roi, int nthreads)
{
    ImageBufAlgo::parallel_image(roi, nthreads, [&](ROI roi) {
        ImageBuf::ConstIterator<Rtype> a(A, roi);
        for (ImageBuf::Iterator<Rtype> r(R, roi); !r.done(); ++r, ++a)
        {
            float x = a[0];
            float y = a[1];
            float z = a[2];

            x = x - inCenter;
            y = y - inCenter;
            z = z - inCenter;

            float length = std::hypot(x, y, z);

            if (length > 0) {
                x /= length;
                y /= length;
                z /= length;
            }

            r[0] = x * scale + outCenter;
            r[1] = y * scale + outCenter;
            r[2] = z * scale + outCenter;

            if (A.spec().nchannels == 4) {
                r[3] = a[3];
            }
        }
        });
    return true;
}

bool normalize(ImageBuf& dst, const ImageBuf& A, float inCenter, float outCenter, float scale, ROI roi, int nthreads)
{
    if (!ImageBufAlgo::IBAprep(roi, &dst, &A))
        return false;
    bool ok;
    OIIO_DISPATCH_COMMON_TYPES(ok, "normalize", normalize_impl, dst.spec().format, dst, A, inCenter, outCenter, scale, roi, nthreads);
    return ok;
}

ImageBuf normalize(const ImageBuf& A, float inCenter, float outCenter, float scale, ROI roi, int nthreads)
{
    ImageBuf result;
    bool ok = normalize(result, A, inCenter, outCenter, scale, roi, nthreads);
    if (!ok && !result.has_error())
        result.errorfmt("normalize error");
    return result;
}

For simplicity and performance, I would be tempted to replace
float length = std::hypot(x, y, z);
if (length > 0) {
    x /= length;
    y /= length;
    z /= length;
}

with
float length = std::hypot(x, y, z);
if (length > 0.0f)
    scale /= length;

No, wait, that's not right, that would change scale permanently. How about this:
float length = std::hypot(x, y, z);
float s = (length > 0.0f) : scale / length : scale;
...
r[0] = x * s + outCenter;
...etc...

I think what the code you propose is correct for what it's trying to do, but I'm worried about the generality with respect to channels. Your code assumes either 3 or 4 channels, and specifically that you want to normalize the first 3 and copy the 4th (if it exists), but there are no checks anywhere that these conditions are true. Also, nothing in here respects the chbegin,chend fields of the roi parameter.
What happens if it's a 1-channel or 2-channel image? (I suspect it might crash?) What if it's a 5-channel image? (I suspect you'll end up with uninitialized memory for channel 4 in the result image.)
Are there cases (outside of the normal map use case) where somebody might want to normalize the magnitude of a 2D vector image that has 2 channels? Of a 4 channel image that represents 4D vectors rather than xyz+alpha?
Are normal maps with alpha or any other 4th channel common? Or do normal map files pretty much always have 3 channels?
It may be a helpful exercise to try to write the comment that will accompany the normalize() function in imagebufalgo.h, which specifies in detail the behavior that users should expect for the function. What's allowed, what isn't, what are error conditions and how are they handled, etc.

template<class Rtype>
static bool normalize_impl(ImageBuf& R, const ImageBuf& A, float inCenter, float outCenter, float scale, ROI roi, int nthreads)
{
    ImageBufAlgo::parallel_image(roi, nthreads, [&](ROI roi) {
        ImageBuf::ConstIterator<Rtype> a(A, roi);
        for (ImageBuf::Iterator<Rtype> r(R, roi); !r.done(); ++r, ++a)
        {
            float x = a[0];
            float y = a[1];
            float z = a[2];

            x = x - inCenter;
            y = y - inCenter;
            z = z - inCenter;

            float length = std::hypot(x, y, z);

            float s = (length > 0.0f) : scale / length : scale;

            r[0] = x * s + outCenter;
            r[1] = y * s + outCenter;
            r[2] = z * s + outCenter;

            if (A.spec().nchannels == 4) {
                r[3] = a[3];
            }
        }
    });
    return true;
}

Not sure how common to normalize 2D or 4D/5D/#D vectors for texture processing but in that case probably better to just have another function, that will use all channels passed to it?

If we think that all but 3D (+ optional alpha) is the only use case that people need for now, then it's ok to support only that -- we can always make it more general later. But in that case, it's important that the outermost normalize() function should do the error checking to ensure that this is the case, and issue helpful error messages when those assumptions are not met.

https://github.com/OpenImageIO/oiio/pull/3945

This was fixed by https://github.com/OpenImageIO/oiio/pull/3945. Closing.


Replace pragma

[ ] Add attribute testRef:...
[ ] Remove other attributes except active
[ ] Adapt Deserializer to always set active to false when loading for first time
[ ] Use Deserializer to build example object instead of pragma
[ ] Use Serializer to save example

Pull Request Test Coverage Report for Build 514679044

12 of 12 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 69.793%

Totals

Change from base Build 512525654:
0.03%

Covered Lines:
4882

Relevant Lines:
6995

💛  - Coveralls

Pull Request Test Coverage Report for Build 514679044

12 of 12 (100.0%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.03%) to 69.793%

Totals

Change from base Build 512525654:
0.03%

Covered Lines:
4882

Relevant Lines:
6995

💛  - Coveralls


Add doc release to ci

Use https://github.com/rrd108/vue-mess-detector/blob/main/release-docs.sh as a starter

I created a PR for this @rrd108


MINIFICPP-1205 - do not show inline script option for ExecutePythonProcessor

Correct documentation for ExecutePythonProcessor
Clean up related leftover code

Added related Jira for implementing and testing the missing functionality:
https://issues.apache.org/jira/browse/MINIFICPP-1206


create default alarm.wav file

Create a simple 1 second alarm.wav audio file and add it to the /assets/ directory.

Audio is being generated by the Web Audio API, so a file is no longer needed.


test: minimal json schema only with required fields

According to the json schema only the bomFormat, specVersion and version fields are required. serialNumber  (bom.uuid which is RECOMMENDED but not REQUIRED), metadata and externalReferences` could be empty.
I've put some fixtures and tests together which only have those required fields according to the spec. The tests are unfortunately failing due to several reasons:

metadata is always assumed to be there. It could be empty or None.

Tweaked this in the assertEqualJsonBom method in tests/base.py. See 0916ff38c0ddb94cde1f18182fe8b40dfc6d8c7c and
in several places where metadata is accessed. see 573357f2ad49aeeb5bef1a644c09c9390f6f39cd

serialNumber  (bom.uuid) is also assumed to exist for the tests.

I know this is an edge case which does not make any sense but one or another field which is not required should be empty.
I was not sure if I'd open an issue for this. I think a PR is better where we could start the discussion with some examples.

In general, I am against these proposed changes.
The models are not a representation of the JSON schema, nor the XML schema, nor the ProtoBuff representation.
The models are a general purpose thing with a certain design.
The JSON/XML/PB are bound to the constraints of their specific systems.
The models are NOT simply a 1:1 of one of the schema definitions, but are intended to be python-specific and pythonic and serve downstream implementations.
The purpose of being JSON/XML schema compatible is taken care by de-/normalizers and de-/serializers which are a decoupled topic.
Metadata is a DataClass. Having it nullable makes implementations downstream more cumbersome, as they always need to check if the bom.metatada exists, before accessing it.
Therefore, it was designed to be mandatory.
Same for UUID.
The __init__ actually takes care of these facts and creates the empty nested models, if they were not provided.
Therefore, I do not see a benefit in having these optional.

I see and understand your points with the DataClass and the (de)serialization strategy. I think both are valid.
Nevertheless, according to the spec, this is just a valid BOM (apart from the discussion of whether it's a meaningful one):
{
  "$schema": "http://cyclonedx.org/schema/bom-1.4.schema.json",
  "bomFormat": "CycloneDX",
  "specVersion": "1.4",
  "version": 1
}

I wanted to make sure that this edge case gets tested and supported by the API.  Optional[] changes were just my proposal to get this done.
I understand your concerns about that. If you still think testing and supporting the edge case makes sense, we can discuss an alternative. I'll see to revise the changes. WDYT?

@hakandilek , if a test for the edge case of a minimal BOM was the reason, then
please revert the changes to the models, and just leave the get_bom_minimal() test you've added
and the resulting fixtures.

please revert the changes to the models, and just leave the get_bom_minimal() test you've added and the resulting fixtures.
Please also add the test for the XML tests, please.

sure, will do :+1:


How to save/load an 8-bit model?

I'm loading a model into 8bit like so:
from transformers import AutoModelForCausalLM, AutoTokenizer
model = AutoModelForCausalLM.from_pretrained("./model", device_map="auto", load_in_8bit=True)
tokenizer = AutoTokenizer.from_pretrained("./model")

I would like to save this 8bit version of the model because it's smaller, so I used
model.save_pretrained("model-8bit")
tokenizer.save_pretrained("model-8bit")

When trying load it again, I get the following error message:
model = AutoModelForCausalLM.from_pretrained("./model-8bit", device_map="auto")
--> RuntimeError: Only Tensors of floating point and complex dtype can require gradients

When trying to load it like so
model = AutoModelForCausalLM.from_pretrained("./model-8bit")

it loads in FP16 mode, which I find curious.
How can I save & load an 8-bit version of a model correctly?
Thanks
Heiko

I think you can do,
    kwargs["load_in_8bit"] = True
    model = AutoModelForCausalLM.from_pretrained(model_name, **kwargs)

https://github.com/huggingface/transformers/issues/19480

Unfortunately this doesn't work - I get the following error:
~/anaconda3/envs/pytorch_p38/lib/python3.8/site-packages/transformers/utils/bitsandbytes.py in set_module_8bit_tensor_to_device(module, tensor_name, device, value)
     63                 new_value = value.to("cpu")
     64                 if value.dtype == torch.int8:
---> 65                     raise ValueError(
     66                         "You cannot load weights that are saved in int8 using `load_in_8bit=True`, make sure you are",
     67                         " using `load_in_8bit=True` on float32/float16/bfloat16 weights.",

But thanks for linking to the issue in the transformers library. Since the error occurs in the transformers library I will close this issue and continu to comment there.


[rt.openssl.org #4172] SRP VBASE stuff still leaking memory

Migrated from rt.openssl.org#4172 (status was 'open')
Requestors:

<EMAIL_ADDRESS>
Attachments:

srp_vfy-1.0.2e.patch
fix_srp_memleak.patch
0001-Fix-SRP-VBASE-memory-leak.patch
0001-Fix-SRP-VBASE-memory-leak.patch
srp_vfy-1.1.0.patch

From<EMAIL_ADDRESS>on 2015-12-07 15:47:56:
Hi,

Following my previous mail, here attached is an updated patch against 1.02e
to fix the SRP VBASE memory leaks.
I understand the VBASE stuff is not a TLS critical component, but it is part
of the SRP command line tool.
NB : it's a pity that the base64 encoding is not the same than the one use
elsewhere by OpenSSL.

Regards,

Michel.

De : openssl-dev<EMAIL_ADDRESS>De la part de
Michel
EnvoyÃ© : lundi 23 mars 2015 12:10
Ã<EMAIL_ADDRESS>Objet : [openssl-dev] SRP memory leaks and more leaks

Hi,

Trying to use the 'SRP' code, I found two kinds of memory leaks in srp_vfy.c
.

1)  The first kind was due to bad use of OpenSSL 'stack' code and cumbersome
/ confusing names of structure / functions.
In this case, leaks occurs when loading a verifier file containing 'index'
lines.
Two structures are used : SRP_gN and SRP_gN_cache.
And unfortunatly, the SRP_gN_free function free a SRP_gN_cache structure.
The SRP_VBASE_free() function, line 276, should call :
sk_SRP_gN_cache_pop_free(vb->gN_cache, SRP_gN_cache_free);
instead of :
sk_SRP_gN_cache_free(vb->gN_cache);
And consequently the SRP_gN_cache_free() function, lines 305-312, has to
move before SRP_VBASE_free()

The attached patch solve this kind of leaks.

2) When simulating a 'fake user' as per RFC 5054, Â§ '<IP_ADDRESS>.  Unknown SRP
User Name',
the SRP_VBASE_get_by_user() function returns a newly allocated SRP_user_pwd
structure whose adress is not kept anywhere else.
So, the caller should free it later, but from outside the function, there is
no way to distinguish between 'fake users' and real ones
which are managed and freed throught the use of the SRP_VBASE structure /
functions.

I am afraid there is no other solution than changing the
SRP_VBASE_get_by_user() function prototype.

It is better I do not share here my opinion about the comments below :
/* need to check whether there are memory leaks */, s_server.c line 433
or :
/* there may be still some leaks to fix, Â */ srp_vfy.c line 449
>:(

Hope this will save time to other users,

Michel.

From<EMAIL_ADDRESS>on 2015-12-10 12:17:04:
On Mon, Dec 07, 2015 at 03:47:56PM +0000, Michel via RT wrote:
> Hi,
>
> Following my previous mail, here attached is an updated patch against 1.02e
> to fix the SRP VBASE memory leaks.

Can you confirm that this would be the correct patch for master?

I still need to look at it.

Kurt

From<EMAIL_ADDRESS>on 2015-12-10 12:21:30:
On Thu, Dec 10, 2015 at 12:17:04PM +0000, Kurt Roeckx via RT wrote:
> On Mon, Dec 07, 2015 at 03:47:56PM +0000, Michel via RT wrote:
> > Hi,
> >
> > Following my previous mail, here attached is an updated patch against 1.02e
> > to fix the SRP VBASE memory leaks.
>
> Can you confirm that this would be the correct patch for master?
>
> I still need to look at it.

It doesn't even compile ...

Kurt

From<EMAIL_ADDRESS>on 2015-12-10 12:27:41:
On Thu, Dec 10, 2015 at 01:16:48PM +0100, Kurt Roeckx wrote:
> On Mon, Dec 07, 2015 at 03:47:56PM +0000, Michel via RT wrote:
> > Hi,
> >
> > Following my previous mail, here attached is an updated patch against 1.02e
> > to fix the SRP VBASE memory leaks.
>
> Can you confirm that this would be the correct patch for master?

The following patch should at least compile.

Kurt

From<EMAIL_ADDRESS>on 2015-12-10 13:06:03:
Hi Kurt,

First, thanks to look at this.

I just look at your mail.
Quick answer : I applied this patch before sending to RT, and not only it compiles but I tested it concerning memory leaks, consequently I am very surprise. So I will review this and return to you soon.

In the meantimehere some additional info :
I am working with Visual Studio 2015 community Ed., under Windows 7, OpenSSL 1.0.2e.

Thanks again,

Regards,

Michel

-----Message d'origine-----
De : Kurt Roeckx via RT<EMAIL_ADDRESS>EnvoyÃ© : jeudi 10 dÃ©cembre 2015 13:28
Ã<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Objet : Re: [openssl-dev] [openssl.org #4172] SRP VBASE stuff still leaking memory

On Thu, Dec 10, 2015 at 01:16:48PM +0100, Kurt Roeckx wrote:
> On Mon, Dec 07, 2015 at 03:47:56PM +0000, Michel via RT wrote:
> > Hi,
> >
> > Following my previous mail, here attached is an updated patch
> > against 1.02e to fix the SRP VBASE memory leaks.
>
> Can you confirm that this would be the correct patch for master?

The following patch should at least compile.

Kurt

From<EMAIL_ADDRESS>on 2015-12-10 13:15:39:
I did not try it on master, only with 1.0.2e.

I will prepare a new one againt master to see what happened.

-----Message d'origine-----
De : Kurt Roeckx via RT<EMAIL_ADDRESS>EnvoyÃ© : jeudi 10 dÃ©cembre 2015 13:28
Ã<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Objet : Re: [openssl-dev] [openssl.org #4172] SRP VBASE stuff still leaking memory

On Thu, Dec 10, 2015 at 01:16:48PM +0100, Kurt Roeckx wrote:
> On Mon, Dec 07, 2015 at 03:47:56PM +0000, Michel via RT wrote:
> > Hi,
> >
> > Following my previous mail, here attached is an updated patch
> > against 1.02e to fix the SRP VBASE memory leaks.
>
> Can you confirm that this would be the correct patch for master?

The following patch should at least compile.

Kurt

From<EMAIL_ADDRESS>on 2015-12-10 14:20:02:
On Thu, Dec 10, 2015 at 01:27:38PM +0100, Kurt Roeckx wrote:
> On Thu, Dec 10, 2015 at 01:16:48PM +0100, Kurt Roeckx wrote:
> > On Mon, Dec 07, 2015 at 03:47:56PM +0000, Michel via RT wrote:
> > > Hi,
> > >
> > > Following my previous mail, here attached is an updated patch against 1.02e
> > > to fix the SRP VBASE memory leaks.
> >
> > Can you confirm that this would be the correct patch for master?
>
> The following patch should at least compile.

I fixed a few more things, cleaned up some things.  New patch
attached.

Kurt

From<EMAIL_ADDRESS>on 2015-12-10 14:37:46:
On Thu, Dec 10, 2015 at 03:19:54PM +0100, Kurt Roeckx wrote:
> On Thu, Dec 10, 2015 at 01:27:38PM +0100, Kurt Roeckx wrote:
> > On Thu, Dec 10, 2015 at 01:16:48PM +0100, Kurt Roeckx wrote:
> > > On Mon, Dec 07, 2015 at 03:47:56PM +0000, Michel via RT wrote:
> > > > Hi,
> > > >
> > > > Following my previous mail, here attached is an updated patch against 1.02e
> > > > to fix the SRP VBASE memory leaks.
> > >
> > > Can you confirm that this would be the correct patch for master?
> >
> > The following patch should at least compile.
>
> I fixed a few more things, cleaned up some things.  New patch
> attached.

I think there is something wrong with new SRP_gN_free().  You now
also free g and N, and it's not clear to me who the owner of those
is.  I think the cache is, in which case we should not free them.
I think the cache also isn't cleared, we should probably call
SRP_VBASE_free() when SRP_VBASE_init() fails.

Kurt

From<EMAIL_ADDRESS>on 2015-12-10 16:00:06:
Hi Kurt,

At first glance, it's a fact that your patch is better.
:-)
I should have thought to some of your improvement, like SRP_gN_new().

I will test it tonight and come back to you.

Many for thanks for your interrest in this matter,

Michel.

-----Message d'origine-----
De : Kurt Roeckx via RT<EMAIL_ADDRESS>EnvoyÃ© : jeudi 10 dÃ©cembre 2015 15:38
Ã<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Objet : Re: [openssl-dev] [openssl.org #4172] SRP VBASE stuff still leaking memory

On Thu, Dec 10, 2015 at 03:19:54PM +0100, Kurt Roeckx wrote:
> On Thu, Dec 10, 2015 at 01:27:38PM +0100, Kurt Roeckx wrote:
> > On Thu, Dec 10, 2015 at 01:16:48PM +0100, Kurt Roeckx wrote:
> > > On Mon, Dec 07, 2015 at 03:47:56PM +0000, Michel via RT wrote:
> > > > Hi,
> > > >
> > > > Following my previous mail, here attached is an updated patch
> > > > against 1.02e to fix the SRP VBASE memory leaks.
> > >
> > > Can you confirm that this would be the correct patch for master?
> >
> > The following patch should at least compile.
>
> I fixed a few more things, cleaned up some things.  New patch
> attached.

I think there is something wrong with new SRP_gN_free().  You now also free g and N, and it's not clear to me who the owner of those is.  I think the cache is, in which case we should not free them.
I think the cache also isn't cleared, we should probably call
SRP_VBASE_free() when SRP_VBASE_init() fails.

Kurt

From<EMAIL_ADDRESS>on 2015-12-10 22:37:07:
Hello Kurt,

I was not able to 'configure' the master branch for debug-VC-WIN32.
I got the error message 'pick os/compiler from: ...
However I succeeded with VC-WIN32.
I guess this is something related to the new configure perl script and debug/non-debug options, but I am lost with perl.

Could you please help for this ?

Michel.

-----Message d'origine-----
De : openssl-dev<EMAIL_ADDRESS>De la part de Michel via RT
EnvoyÃ© : jeudi 10 dÃ©cembre 2015 17:00
Cc<EMAIL_ADDRESS>Objet : Re: [openssl-dev] [openssl.org #4172] SRP VBASE stuff still leaking memory

Hi Kurt,

At first glance, it's a fact that your patch is better.
:-)
I should have thought to some of your improvement, like SRP_gN_new().

I will test it tonight and come back to you.

Many for thanks for your interrest in this matter,

Michel.

-----Message d'origine-----
De : Kurt Roeckx via RT<EMAIL_ADDRESS>Envoy  : jeudi 10 d cembre 2015 15:38<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Objet : Re: [openssl-dev] [openssl.org #4172] SRP VBASE stuff still leaking memory

On Thu, Dec 10, 2015 at 03:19:54PM +0100, Kurt Roeckx wrote:
> On Thu, Dec 10, 2015 at 01:27:38PM +0100, Kurt Roeckx wrote:
> > On Thu, Dec 10, 2015 at 01:16:48PM +0100, Kurt Roeckx wrote:
> > > On Mon, Dec 07, 2015 at 03:47:56PM +0000, Michel via RT wrote:
> > > > Hi,
> > > >
> > > > Following my previous mail, here attached is an updated patch
> > > > against 1.02e to fix the SRP VBASE memory leaks.
> > >
> > > Can you confirm that this would be the correct patch for master?
> >
> > The following patch should at least compile.
>
> I fixed a few more things, cleaned up some things.  New patch
> attached.

I think there is something wrong with new SRP_gN_free().  You now also free g and N, and it's not clear to me who the owner of those is.  I think the cache is, in which case we should not free them.
I think the cache also isn't cleared, we should probably call
SRP_VBASE_free() when SRP_VBASE_init() fails.

Kurt

_______________________________________________
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

From<EMAIL_ADDRESS>on 2015-12-11 23:40:56:
Hello Kurt,

I finally managed to compile a debug 1.1.0 version.
(I manually modified the makefile)
:-(

Anyway, I can confirm the patch you send to me fixes the first memory leak case.
BUT,
You are right, we should not free g and N, because they are shared/referenced by the VBASE cache.
They will be freed by SRP_VBASE_free();
BUT (again) we need to free the *ID* of g and N, which was allocated and no longer in use or referenced elsewhere.
I believe the data structures should have been made differently such that they do not share only part of internal data.

That's why I did not call sk_SRP_gN_pop_free() in my first patch.

Here attached is an updated version of your patch that, I hope, can meet our first requirement.

As long as the memory is in a stable state, I think it is not mandatory to free immediatly the VBASE data in case of error.
We can let the caller decide what he wants to do. But it is just my opinion.

Thanks again,

Regards,

Michel

-----Message d'origine-----
De : openssl-dev<EMAIL_ADDRESS>De la part de Michel via RT
EnvoyÃ© : jeudi 10 dÃ©cembre 2015 23:37
Cc<EMAIL_ADDRESS>Objet : [openssl-dev] TR: [openssl.org #4172] SRP VBASE stuff still leaking memory

Hello Kurt,

I was not able to 'configure' the master branch for debug-VC-WIN32.
I got the error message 'pick os/compiler from: ...
However I succeeded with VC-WIN32.
I guess this is something related to the new configure perl script and debug/non-debug options, but I am lost with perl.

Could you please help for this ?

Michel.

-----Message d'origine-----
De : openssl-dev<EMAIL_ADDRESS>De la part de Michel via RT Envoy  : jeudi 10 d cembre 2015 17:00 Cc<EMAIL_ADDRESS>Objet : Re: [openssl-dev] [openssl.org #4172] SRP VBASE stuff still leaking memory

Hi Kurt,

At first glance, it's a fact that your patch is better.
:-)
I should have thought to some of your improvement, like SRP_gN_new().

I will test it tonight and come back to you.

Many for thanks for your interrest in this matter,

Michel.

-----Message d'origine-----
De : Kurt Roeckx via RT<EMAIL_ADDRESS>Envoy  : jeudi 10 d cembre 2015 15:38<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Objet : Re: [openssl-dev] [openssl.org #4172] SRP VBASE stuff still leaking memory

On Thu, Dec 10, 2015 at 03:19:54PM +0100, Kurt Roeckx wrote:
> On Thu, Dec 10, 2015 at 01:27:38PM +0100, Kurt Roeckx wrote:
> > On Thu, Dec 10, 2015 at 01:16:48PM +0100, Kurt Roeckx wrote:
> > > On Mon, Dec 07, 2015 at 03:47:56PM +0000, Michel via RT wrote:
> > > > Hi,
> > > >
> > > > Following my previous mail, here attached is an updated patch
> > > > against 1.02e to fix the SRP VBASE memory leaks.
> > >
> > > Can you confirm that this would be the correct patch for master?
> >
> > The following patch should at least compile.
>
> I fixed a few more things, cleaned up some things.  New patch
> attached.

I think there is something wrong with new SRP_gN_free().  You now also free g and N, and it's not clear to me who the owner of those is.  I think the cache is, in which case we should not free them.
I think the cache also isn't cleared, we should probably call
SRP_VBASE_free() when SRP_VBASE_init() fails.

Kurt

_______________________________________________
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

_______________________________________________
openssl-dev mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-dev

I believe this can be closed as @ekasper fixed that his way on 1 march 2016 [CVE-2016-0798].

thanks, closing.


CUDA simulator device function may not have the right "cuda" module

Fix issue #1837.
The CUDA simulator injects/monkeypatches the global dictionary of the kernel function to replace the "cuda" module with a FakeCudaModule instance that has all the kernel api (e.g. cuda.shared, cuda.threadIdx, etc..).  However, this was not performed on device functions.  Problem occurs when the device function is imported from another module, which has a unpatched global dictionary.  This PR fixes it.
In additional to the fix, the monkeypatching of global will not replaces globals that are referencing the "cuda" module object; instead of just replacing the variable with the name "cuda".

Current coverage is 87.60%

Merging #1844 into master will not affect coverage as of 931c849

@@            master   #1844   diff @@
======================================
  Files          287     287
  Stmts        51114   51110     -4
  Branches      5302    5284    -18
  Methods
======================================
  Hit          44776   44776
+ Partial        902     899     -3
+ Missed        5436    5435     -1

Review entire Coverage Diff as of 931c849

Powered by Codecov. Updated on successful CI builds.


tasks to do when typescript-eslint supports ESLint v9

delete .npmrc
delete package-lock.json and run npm install

fixed in #105


Failed to read Git log

Hi,
I'd love to use this theme, but every time I try to start hugo server with ExampleSite content I get the following error. I am running latest Hugo extended version with Manjaro Linux.
Failed to read Git log: fatal: Not a git repository (or any parent up to mount point /home)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
Built in 123 ms
Error: Error building site: logged 1 error(s)

Comment this line enableGitInfo=true in your config.toml
ref #63539a3
Thank's

Many thanks! Just a quick question. How can I make archives.md show content?

this template automatically lists your posts by creating a section page, term page, or taxonomy page.
if you mean to list all your posts on a single page, you could try some of  these snippets.


[threadpool] Can't detect same thread or not when call fork after creating threadpool

Add API for fork


Attaching APK files to the release

Would it be possible to attach APK files to the releases? At the moment there is only the AAB package. It is possible to extract the APKs, but then one has to sign them before installing.

@kuhlmannmarkus This would be a great addition, as it would allow installing directly with Obtainium.
It also benefits those who do not use the Play Store, like GrapheneOS users.

Also, @dovholuknf, your Mattermost workflow is failing.

Wow, it sure is! I'll see if I can fix that. Thanks.

Glad to help :)

fixed it. thanks for letting me/us know. @ekoby will probably have to comment on the APK ask

Sure thing!

Awesome! Thank you so much!

@ekoby Thank you, indeed!
There is a failure in the webhook action, though: https://github.com/openziti/ziti-tunnel-android/actions/runs/5836422783

@ekoby. Did you see the action failure?


Drawing classifier must run on Mac GPUs

Currently, drawing classifier does not run on the Mac GPUs. We need to:

[ ] Investigate if this is possible using MacOS 10.14 APIs.
[ ] Implement after the investigation is complete.

This is a dupe of #1888 , closing this in favor of that.


Custom static assets path

What problem does this feature solve?
To provide a solution to rename the static assets folder.
I was using vue-cli v2 to build my SPA and trans to v3.x last week. There is some reason for me that I cannot use 'public' as a name for static assets folder (I already have a soft link named 'public' for some other assets)
What does the proposed API look like?
It may as simple as add a prop in vue.config.js like:
module.exports = {
  ...,
  assetsPathName: '',
  ...
}

I find it is able to use 'copy-webpack-plugin' in vue.config.js to handle this problem.
I will close this issue.
Thanks for this great lib.


Can I populate the enum entries of a select box with dynamic data returned from db?

Hi,
I have a big form with 100+ fields, with many select box.
indeed to populate items statically via enum entries from schema,
can I add items to select box dynamically from db?
thanks in advance

You can use ui:enumOptions to dynamically update options, or update the schema enum
https://codepen.io/ljj/pen/zYjmobw

Thanks, but I can populate also the data from db whitin the '@form-mounted' event.


Caar

Moved the memory allocations for host and device dti arrays to grid3D.cpp, so they are single allocated. These are used for the GPU time step reduction in Calc_dt_GPU. Also, the cooling dti calculation now re-uses the same arrays (since both are only used in the kernel).
Added definition of global variable 'ngrid' - the number of GPU thread blocks - to grid3D.cpp. Removed duplicate definitions in hydro integrators.
Removed duplicate hydro conserved variable array on the host (in grid3D.cpp).

That's right, no more buffers. Thanks!


[CELEBORN-655][SPARK][0.2] Rename newAppId to appUniqueId

What changes were proposed in this pull request?
Rename variable newAppId to appUniqueId in Spark client.
Why are the changes needed?
Make the variable name intuitive.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.
Closes #1565 from pan3793/CELEBORN-655.
Authored-by: Cheng Pan<EMAIL_ADDRESS>

Merged to 0.3


Various bugs

update explore more link on tiles to go to the new vis tools
in explore page, when new place is clicked, clear the query input
fix all cap section headers
when choosing per capita at block level, use percent instead of ratio

thanks for the reviews!


Issues while setting minDateRange or FutureDate

Hello,
I am trying to set minDateRange(date) and .setOnFutureDate(), but somehow when I open the dialog, it shows previous day for ex. if currently it is 2:10 PM, it will show Today, 2:00 PM. And thus it allows user to pick past time which my app can't let user do.
Please let me know how to fix this.
Thanks,
Arpit

It might be late but, still it will surely help someone using this library. After going thru the code i figured out how to fix this issue.
In WheelMinutePicker.java, in menthod findIndexOfMinute(int minute) line no: 79: change the following:
if (minute < value) {
               return i - 1;
           }

          to

if (minute < value) {
                return i;
            }

Above code will show up current time on Picker or if current time(minutes) doesn't fall under multiple of 5, then it will show time(minutes) greater than current time.
In WheelPicker.java, in menthod findIndexOfDate(Date date) line no: 857: change the following:
if (formatItem.equals(object)) {
       return i;
     }

          to

 if (formatItem.equals(object)) {
                return i + 1;
            }

Above code will not let the user to select the time less than current time.

This will still have bug when the time is 8.56. It will select 8.00.


Scrolling to error message

PR Type
[x] Feature
What Is the Current Behavior?

On checkout error message doesn't get scrolled to
Issue Number: Closes #848
What Is the New Behavior?
When the checkout has some errors, the browser will scroll to it
Does this PR Introduce a Breaking Change?
[x] No
Other Information
Uses Scrolling Directive developed for #911
AB#71917

This adds automatic scrolling in checkout step 3 (payment). Please comment if it is required elsewhere.

This adds automatic scrolling in checkout step 3 (payment). Please comment if it is required elsewhere.

Hi, it works very well.
I think we should add this behavior to the inline error message in general. This ensures consistent behavior no matter where these messages are used. In addition, automatic scrolling is necessary in the shopping cart and at each checkout step, where there is always a lot of content displayed and the "Checkout" button can be seen far below (especially in the phone view) - This makes it very difficult to notice the error message as I mentioned in the ticket.

Alright, the way this current implementation works is by checking the basket error status. I will work on tying it to the inline error message in general so it can be used everywhere.

Scrolling is now attached in the basket-validation-results component. It will work for all messages used there but is still not attached on messages in general. Here are some thoughts regarding general attaching to any kind of error messages:

Is it really desired to automatically scroll to every error message? Some messages e.g. on form validation show up while user is still filling out forms. Automatically scrolling to those messages will result in an unoptimized user experience.
If multiple error messages are shown, all will be scrolled to in order which results in scrolling to the last one. This way the user only notices the last message at first glance. This can be problematic since error messages could as well be triggered by preceeding errors.
Depending on where messages are shown it is not desired to scroll them directly but to some point above them since the message will otherwise be hidden on mobile by the navigation bar. The scroll directive supports spacing to leave some space above the element when scrolling but I am not sure if this should be set for all messages in general since some cases might require different spacing or no spacing at all.

Considering the points above I advise to simply scroll to the top when an error occurs (mentioned as alternative solution in #848). This behvior might not be archived on a message component but has to be implemented on the corresponding page. Easiest option would be to scroll automatically to the top after the checkout button gets pressed since even on success, user will land at the top for the next checkout step.
Please reflect on these thoughts and decide how to proceed.

Scrolling is now attached in the basket-validation-results component. It will work for all messages used there but is still not attached on messages in general. Here are some thoughts regarding general attaching to any kind of error messages:

Is it really desired to automatically scroll to every error message? Some messages e.g. on form validation show up while user is still filling out forms. Automatically scrolling to those messages will result in an unoptimized user experience.
If multiple error messages are shown, all will be scrolled to in order which results in scrolling to the last one. This way the user only notices the last message at first glance. This can be problematic since error messages could as well be triggered by preceeding errors.
Depending on where messages are shown it is not desired to scroll them directly but to some point above them since the message will otherwise be hidden on mobile by the navigation bar. The scroll directive supports spacing to leave some space above the element when scrolling but I am not sure if this should be set for all messages in general since some cases might require different spacing or no spacing at all.

Considering the points above I advise to simply scroll to the top when an error occurs (mentioned as alternative solution in #848). This behvior might not be archived on a message component but has to be implemented on the corresponding page. Easiest option would be to scroll automatically to the top after the checkout button gets pressed since even on success, user will land at the top for the next checkout step.
Please reflect on these thoughts and decide how to proceed.

Thank you for your feedback. I think we have a little misunderstanding: I would only add this behavior to the inline error messages - the bootstrap error alerts. Only this pattern/component:

Currently we use the inline error messages or error alerts only in the cart and checkout pages. I think it is fine to attach it on the basket-validation-results component. My assumption: If the basket validation fails, then the pattern shown above is always used, isn't it?

Form field validation uses another pattern. No auto-scrolling should be used for this.
This is rather rarely the case. Even if it were, you could fix one mistake first and then the other. Currently, both errors would be out of view.
As I mentioned I would use this for the error inline messages (not all messages in general), which we are only use for cart and checkout now. I have to check how it feels on the cart page, where we have a sticky navigation at the top.

I will check the error behavior in the whole checkout and when something is unclear or feels unnatural, I will come back to you. Is this fine for you? It seems that the demo server is not loading the pwa, yet (504 Gateway time-out). I try it later again.

Thanks for clarifying, I guess I did in fact misunderstood your request.
I would appreciate it if you could review the checkout process once the demo server is back online and inform me about further changes you wish to happen.


Tests repeat angular4 + karma + mocha

I'm sure that I've made a mistake in my karma config, unfortunately I can't see it, so perhaps I've found an issue hence i'm raising one here.
I've done an investigation and posted it on Stack Overflow.
Context
Basic angular-cli project (angular4 + karma + jasmine) converted to use mocha results in tests being run twice Chromeium 53.0.2785 (Ubuntu 0.0.0): Executed 6 of 3 SUCCESS (0.347 secs / 0.042 secs).
Expected Behavior

Tests should only be run once.

Additional information

Using wallabyjs, the tests only run once as expected
Downgrading from Angular4 -> Angular2 dependencies results in the tests only running once as expected

This issue has been raised because of further investigation in relation to karma-runner/karma/issues/2657
More specifically it seems to be related to using mocha + angular4 + karma-runner/karma-mocha

This was due to frameworks in the karma conf
karma-runner/karma/issues/2657


Test Coverage Badge on README.md

Add a test coverage badge in README.md to create transparency of our code quality

Let's have this thing on v2.0 with a better code implementation


ci: update containerfile with penumbra support

Creates a container image that builds a version of Hermes for compatibility with Penumbra chains. Defaults to building the Penumbra dependency from the upstream "main" branch in [0], but the gitref can be overridden to be a stable tag.
[0] https://github.com/penumbra-zone/penumbra

Still to come: GHA for building it. GHA aren't currently enabled on this repo, due to its being a fork, so will first need to clean up the old CI jobs.


Update zipkin deployment.

Update zipkin deployment to include priorityClassName, imagePullSecrets and nodeAffinity.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
8f29ec235c7966abcd42ae5c58e5588955c4cba8
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
8f29ec235c7966abcd42ae5c58e5588955c4cba8
link
/test istio-integ-k8s-tests

prow/istio-unit-tests.sh
a1c8d73138699279bdb5fbf1127dc004e70d8bb6
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
8f29ec235c7966abcd42ae5c58e5588955c4cba8
link
/test istio-pilot-multicluster-e2e

prow/istio-unit-tests.sh
a1c8d73138699279bdb5fbf1127dc004e70d8bb6
link
/test istio-unit-tests

prow/e2e_pilotv2_auth_sds.sh
a1c8d73138699279bdb5fbf1127dc004e70d8bb6
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
a1c8d73138699279bdb5fbf1127dc004e70d8bb6
link
/test istio-unit-tests

prow/e2e_pilotv2_auth_sds.sh
a1c8d73138699279bdb5fbf1127dc004e70d8bb6
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
a1c8d73138699279bdb5fbf1127dc004e70d8bb6
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
e3c8476000243438910bf768480030477a551058
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: PR needs rebase.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
e3c8476000243438910bf768480030477a551058
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-local-tests.sh
5c2f201fbba4a809c7ee0b822bbcd45a86c0d9a2
link
/test istio-integ-local-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
e3c8476000243438910bf768480030477a551058
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-local-tests.sh
5c2f201fbba4a809c7ee0b822bbcd45a86c0d9a2
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
5c2f201fbba4a809c7ee0b822bbcd45a86c0d9a2
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
e3c8476000243438910bf768480030477a551058
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-local-tests.sh
5c2f201fbba4a809c7ee0b822bbcd45a86c0d9a2
link
/test istio-integ-local-tests

prow/istio-integ-k8s-tests.sh
5c2f201fbba4a809c7ee0b822bbcd45a86c0d9a2
link
/test istio-integ-k8s-tests

prow/istio-presubmit.sh
5c2f201fbba4a809c7ee0b822bbcd45a86c0d9a2
link
/test istio-presubmit

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
e3c8476000243438910bf768480030477a551058
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
5c2f201fbba4a809c7ee0b822bbcd45a86c0d9a2
link
/test istio-integ-k8s-tests

prow/e2e-simpleTests-cni.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
e3c8476000243438910bf768480030477a551058
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
e3c8476000243438910bf768480030477a551058
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test istio_auth_sds_e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test istio-integ-k8s-tests

prow/e2e_pilotv2_auth_sds.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
ba7667cf8660dd3f9dae06c7bf6e6eeff5ffdc6b
link
/test e2e-simpleTests-cni

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e_pilotv2_auth_sds.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test istio_auth_sds_e2e

prow/istio-pilot-multicluster-e2e.sh
e29396149e4ff44db983b10a44bbf9ff9839b941
link
/test istio-pilot-multicluster-e2e

prow/e2e-simpleTests-cni.sh
ba7667cf8660dd3f9dae06c7bf6e6eeff5ffdc6b
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
ba7667cf8660dd3f9dae06c7bf6e6eeff5ffdc6b
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests-cni.sh
ba7667cf8660dd3f9dae06c7bf6e6eeff5ffdc6b
link
/test e2e-simpleTests-cni

prow/istio-integ-k8s-tests.sh
ba7667cf8660dd3f9dae06c7bf6e6eeff5ffdc6b
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
ba7667cf8660dd3f9dae06c7bf6e6eeff5ffdc6b
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@wenchenglu Can we merge this to release-1.1?

Maybe we can fix this in post 1.1.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
ba7667cf8660dd3f9dae06c7bf6e6eeff5ffdc6b
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
1c524aef43ca31fb099996bc08d0398cebcce750
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
1c524aef43ca31fb099996bc08d0398cebcce750
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
1c524aef43ca31fb099996bc08d0398cebcce750
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
1c524aef43ca31fb099996bc08d0398cebcce750
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
7d761e182cddb0a3d125b641a9f6d48782d436af
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
7d761e182cddb0a3d125b641a9f6d48782d436af
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
7d761e182cddb0a3d125b641a9f6d48782d436af
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-multicluster-e2e.sh
7d761e182cddb0a3d125b641a9f6d48782d436af
link
/test istio-pilot-multicluster-e2e

prow/istio-integ-k8s-tests.sh
3a39f71413960e28127c2f6c0cb6128df8142103
link
/test istio-integ-k8s-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-integ-k8s-tests.sh
3a39f71413960e28127c2f6c0cb6128df8142103
link
/test istio-integ-k8s-tests

prow/istio-pilot-multicluster-e2e.sh
3a39f71413960e28127c2f6c0cb6128df8142103
link
/test istio-pilot-multicluster-e2e

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@morvencao should we target this to the istio/installer artifacts instead now?

@douglas-reid Oh, yes, thanks for reminder, i think this has been fixed in new installer , see: https://github.com/istio/installer/pull/132
Closing this.


[Question] how to read results?

Hey @mmarchini
I'm new to node and memory profiling on node apps,
rn i'm using node20 with a React App, and I want to get the heap-profile to decide on memory limits for my node app under a docker container, I was able to run your library without any problems, but there's nothing under README.md file describing any tool that can read the output from your library, Maybe can you point me out a way to read the profiling results?
all the best

Hey @rafaelingaramo,
The results could be loaded on Google Chrome Developer Tools. If you need some FlameGraphs for CPU Profiling, then you can use some tools that support FlameGraphs, e.g., speedscope


Go Live Tasks

https://www.hlx.live/docs/go-live-checklist

[x] Add query-index to support sitemap
[ ] Generate Sitemap
[ ] Push invalidation setup with CDN
[ ] Update production host for sidekick
[ ] Check redirection rules
[ ] Ensure apex domain points to www
[x] Update cdn.prod.host in .helix/config.xlsx
[ ] Test redirects

I'd add to check the redirection rules too.

Sitemap generated at https://caesars.com/careers/sitemap.xml
Query index generated at https://caesars.com/careers/query-index.json

Push invalidation setup with CDN (needs customer) - N/A since they are using Imperva so its just based on TTL.


Rename metro-react-native-babel-transformer to @react-native/babel-transformer

Summary:
This renames metro-react-native-babel-transformer package to react-native/babel-transformer. It also updates references in packages that depend on it.
Changelog: [General][Changed] - Rename metro-react-native-babel-transformer to react-native/babel-transformer
Differential Revision: D46564389

Closing as abandoned internally


document dontMoveLib64 variable controlling the fixup phase

Recently I ran into issue when nix moved static libraries of a foreign (MIPS) architecture from lib64 to lib silently overwriting the contents on destination. It's a compiler supporting both x32 and x64 architectures needed to be packaged from binaries.
I've spent several hours finding the needed dontMoveLib64 option to skip the moving, digging deeply through the whole phases/stdenv/hooks infrastructure internals.

Still relevant.

I've tried to reproduce with
with import <nixpkgs> {};

stdenv.mkDerivation {
  name = "test";
  dontUnpack = true;
  installPhase = ''
    mkdir -p $out/lib{,64}
    echo 32 > $out/lib/test
    echo 64 > $out/lib64/test
  '';
}

but does not silently override any contents in lib/, it prints an explicit message and fails the build:
moving /nix/store/85cdvfblldj22mpzr87vmxcd0fb5vlaw-test/lib64/* to /nix/store/85cdvfblldj22mpzr87vmxcd0fb5vlaw-test/lib
rmdir: failed to remove '/nix/store/85cdvfblldj22mpzr87vmxcd0fb5vlaw-test/lib64': Directory not empty
builder for '/nix/store/0xcaz1jp5622n5sz7by4lzvdf8i5d1fd-test.drv' failed with exit code 1

My fault. It seems my observation was related to dontStrip option which caused inappropriate modification of static libraries. Apparently I used dontStrip in conjunction with dontMoveLib64.
Nevertheless the issue is about documenting the dontMoveLib64 option. Not about it's behavior.


[Style] Text in black

Describe the bug
Hi !
I can't use the module, all texts are in black.
See here pnpblacktext
To Reproduce
Foundry virtual Tabletop 0.7.6
Warhammer Fantasy Roleplar 4th Edition 3.0.1
Desktop (please complete the following information):

Windows 10 2004
Goggle Chrome 86 // Firefox 82

you can still use it, its just kinda difficult to set up..
I'd prefer this to be fixed on the wfrp side, since this issue would possibly not only affect this module, so i posted an issue over there (as seen above)
If i don't hear back from them i'll provide a fix from my side for this module...

I fixed it.. i hate it though and it really should be done by wfrp and not by every module themself creating custom apps <_<

Thank you. After tests, the color came from windows.app. I don't think the wfrp system would proceed on it.


plugin_lint_mac test fails on Xcode 14.3: a function declaration without a prototype is deprecated in all versions of C

pod lib lint packages/integration_test/ios/integration_test.podspec --no-clean

fails on Xcode 14.3 in CI:
App/main.m:4:9: warning: a function declaration without a prototype is deprecated in all versions of C [-Wstrict-prototypes]

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8782535317087304833/+/u/run_plugin_lint_mac/test_stdout
This is because
int main() {}

causes the warning in 14.3.  This was reported in https://github.com/CocoaPods/CocoaPods/issues/11846 and fixed in CocoaPods 1.12.1 in https://github.com/CocoaPods/CocoaPods/pull/11847 which changed it to:
int main(void) {}

CI version of CocoaPods needs to be updated to 1.12.2.  This is blocked by https://github.com/flutter/flutter/issues/122057.

Docs on how to create/update ruby packages: go/flutter-ruby

Removing from ticket queue. This requires recompiling ruby for arm and x64 along with its dependencies and infra gardeners do not have the context on how to do it.

This requires recompiling ruby for arm and x64 along with its dependencies and infra gardeners

I don't think we need new versions of ruby or bundler, just the gems themselves.

Umbrella bug for updating the ruby self contained package: https://github.com/flutter/flutter/issues/136377

This issue is also impacting Wonderous app (https://github.com/gskinnerTeam/flutter-wonderous-app.git).

@vashworth can you please help us validate this bug is fixed?

Removing myself from this bug as only the final confirmation is needed.


Rewrite TF batch norm; remove batch_norm_inference

Depends on #1362
Rewrites the TF batch norm like operators to other MIGX operators
Removes the code related to batch_norm_inference
Do we have an equivalent to verify_onnx.cpp for the TF parser?

@CharlieL7  can you target this on the branch it depents on from PR #1362 , it'll be easier to see changes relative to that branch

Not sure why CI is being odd on the perf test again. Everything else looks fine for this one.

For the epsilon value I'm using the eps from this: https://www.tensorflow.org/api_docs/python/tf/raw_ops/FusedBatchNorm and this: https://www.tensorflow.org/api_docs/python/tf/raw_ops/FusedBatchNormV3. Since those are the TensorFlow ops used in the tests.


TypeError when trying to format with black

Hi,
Thanks for this extension. However, I can't use it because it always throws this error in my face:

This happens in an existing notebook, in a fresh notebook, from the button and via the CTRL-B keyboard shortcut.
Running the notebook with --log-level=DEBUG only shows these 4 lines when the error occurs:
[D 10:12:42.912 NotebookApp] activity on ffbe4112-f925-46b3-91a4-5e09801c2865: status
[D 10:12:42.914 NotebookApp] activity on ffbe4112-f925-46b3-91a4-5e09801c2865: execute_input
[D 10:12:42.928 NotebookApp] activity on ffbe4112-f925-46b3-91a4-5e09801c2865: error
[D 10:12:42.931 NotebookApp] activity on ffbe4112-f925-46b3-91a4-5e09801c2865: status

My environment:
> lsb_release -a
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04.3 LTS
Release:	18.04
Codename:	bionic
> firefox -v
Mozilla Firefox 70.0.1
> vivaldi --version
Vivaldi 1.15.1147.64
> python3 -V
Python 3.6.9
> pip3 show black
Name: black
Version: 18.9b0
Summary: The uncompromising code formatter.
Home-page: https://github.com/ambv/black
Author: Łukasz Langa
Author-email<EMAIL_ADDRESS>License: MIT
Location: /home/yann/.local/lib/python3.6/site-packages
Requires: click, appdirs, attrs, toml
Required-by: clean-ipynb
> pip3 show jupyter_contrib_nbextensions
Name: jupyter-contrib-nbextensions
Version: 0.5.1
Summary: A collection of Jupyter nbextensions.
Home-page: https://github.com/ipython-contrib/jupyter_contrib_nbextensions.git
Author: ipython-contrib and jupyter-contrib developers
Author-email<EMAIL_ADDRESS>License: BSD
Location: /home/yann/.local/lib/python3.6/site-packages
Requires: traitlets, nbconvert, notebook, ipython-genutils, jupyter-nbextensions-configurator, jupyter-contrib-core, jupyter-core, pyyaml, tornado, jupyter-highlight-selected-word, lxml, jupyter-latex-envs
Required-by:

I previously installed the extension manually as instructed in the README. Same error.
I might just be blind.
Any ideas?

I ran into this as well. The underlying cause of the issue was having an out-of-date black install (specifically, I was on black-18.9b0, which had a different signature for black.format_str).
To fix, run:
python3 -m pip install --upgrade black

And restart the notebook server.

Wow, how did I now upgrade black before posting this...
Thanks @madebyollin!


20 node quadratic hexahedral element

This begins the work on #327 .
Edit: Includes also a feature for merging two meshes via __add__.

The convergence rate seems to be lower than I expect; I'm not sure what causes this. Need to investigate a bit further.

Added several new tests but couldn't find the culprit: still the new element converges as O(h^1/2) in H^1 norm and O(h) in L^2 norm which isn't O(h^2) and O(h^3) as I'd expect.

Figured out that there could still be a hidden bug in the facet->edge expansion. Added a test in the latest commit.

Yes! Figured it out. The facet->edge expansion that was fixed in #83 was working only in case of tetrahedral elements.

Now we have the first quadratic hexahedral element. Do we still need the 27 node element? Maybe for Stokes?

Do we still need the 27 node element? Maybe for Stokes?

Well we probably want it for completeness anyway and yes for Stokes, I think.  ElementHex2 is often recommended for Stokes (e.g. Ern & Guermond 2004, Theory and Practice of Finite Elements, figure. 4.4), but I don't think I've seen serendipity elements used for incompressible fluids.

Well we probably want it for completeness anyway and yes for Stokes, I think.

Sure. That can be my next follow up task.


new switch-to-configuration-ng: Failed to run user activation...

https://github.com/NixOS/nixpkgs/blame/d2679dcbf1a032b0583915a8e3f9faffe936e9f1/pkgs/by-name/sw/switch-to-configuration-ng/src/main.rs#L1671
when attempting to nixos-rebuild on a wsl instance I am getting this
/nix/store/xj3icmv6yp869q7x0bvkvm5g3jda9b1r-nixos-system-wsl-24.11.20240612.57d6973/bin/switch-to-configuration switch

activating the configuration...
--- diff to current-system
<<< /run/current-system
>>> /nix/store/xj3icmv6yp869q7x0bvkvm5g3jda9b1r-nixos-system-wsl-24.11.20240612.57d6973
No version or selection state changes.
Closure size: 645 -> 645 (0 paths added, 0 paths removed, delta +0, disk usage +0B).
---
setting up /etc...
setting up /bin...
setting up /bin/login...
sops-install-secrets: Imported /etc/ssh/ssh_host_rsa_key as GPG key with fingerprint 6cc739adb08686e46c9a438a7745b1977c437fc1
sops-install-secrets: Imported /etc/ssh/ssh_host_ed25519_key as age key with fingerprint age1w42mwytnct7j978vz9wxn65g74f89uwzx27y8dhjxzkukjnrpdys9df55x
setting up /sbin/init shim...
reloading user units for sedlund...
Error: Failed to run user activation for sedlund

Caused by:
    Permission denied (os error 13)

This error message is not great.  How can I find out what is breaking?
tag @jmbaur

Yeah that error message is not great! What sort of WSL setup do you have? Are you using https://github.com/nix-community/NixOS-WSL?

I'm not immediately seeing where the program would have failed in such a way that it failed to produce some meaningful error message. With the username change, did your UID happen to change as well? Perhaps it could have failed here.

yeah remained 1000:100
maybe this helps. but I don't see anything glaring here either.

strace output
[pid 613199] execve("/nix/store/w5qgrjabiwh5ijm5vmc1kcpn04jfj3nw-switch-to-configuration-0.1.0/bin/switch-to-configuration", ["/nix/store/w5qgrjabiwh5ijm5vmc1kcpn04jfj3nw-switch-to-configuration-0.1.0/bin/switch-to-configuration"], ["DISPLAY=:0", "DISTRO_ID=nixos", "GTK_A11Y=none", "GTK_PATH=/root/.nix-profile/lib/gtk-2.0:/root/.nix-profile/lib/gtk-3.0:/root/.nix-profile/lib/gtk-4.0:/nix/profile/lib/gtk-2.0:/nix/profile/lib/gtk-3.0:/nix/profile/lib/gtk-4.0:/root/.local/state/nix/profile/lib/gtk-2.0:/root/.local/state/nix/profile/lib/gtk-3.0:/root/.local/state/nix/profile/lib/gtk-4.0:/etc/profiles/per-user/root/lib/gtk-2.0:/etc/profiles/per-user/root/lib/gtk-3.0:/etc/profiles/per-user/root/lib/gtk-4.0:/nix/var/nix/profiles/default/lib/gtk-2.0:/nix/var/nix/profiles/default/lib/gtk-3.0:/nix/var/nix/profiles/default/lib/gtk-4.0:/run/current-system/sw/lib/gtk-2.0:/run/current-system/sw/lib/gtk-3.0:/run/current-system/sw/lib/gtk-4.0", "HOME=/root", "INFOPATH=/root/.nix-profile/info:/root/.nix-profile/share/info:/nix/profile/info:/nix/profile/share/info:/root/.local/state/nix/profile/info:/root/.local/state/nix/profile/share/info:/etc/profiles/per-user/root/info:/etc/profiles/per-user/root/share/info:/nix/var/nix/profiles/default/info:/nix/var/nix/profiles/default/share/info:/run/current-system/sw/info:/run/current-system/sw/share/info", "INSTALL_BOOTLOADER=/nix/store/php4qidg2bxzmm79vpri025bqi0fa889-coreutils-9.5/bin/true", "LANG=en_US.UTF-8", "LC_TIME=en_GB.UTF-8", "LIBEXEC_PATH=/root/.nix-profile/libexec:/nix/profile/libexec:/root/.local/state/nix/profile/libexec:/etc/profiles/per-user/root/libexec:/nix/var/nix/profiles/default/libexec:/run/current-system/sw/libexec", "LOCALE_ARCHIVE=/nix/store/fsyf478vqk0d2p0l3g3i6vga3ka0573c-glibc-locales-2.39-52/lib/locale/locale-archive", "LOGNAME=root", "LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=00:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.7z=01;31:*.ace=01;31:*.alz=01;31:*.apk=01;31:*.arc=01;31:*.arj=01;31:*.bz=01;31:*.bz2=01;31:*.cab=01;31:*.cpio=01;31:*.crate=01;31:*.deb=01;31:*.drpm=01;31:*.dwm=01;31:*.dz=01;31:*.ear=01;31:*.egg=01;31:*.esd=01;31:*.gz=01;31:*.jar=01;31:*.lha=01;31:*.lrz=01;31:*.lz=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.lzo=01;31:*.pyz=01;31:*.rar=01;31:*.rpm=01;31:*.rz=01;31:*.sar=01;31:*.swm=01;31:*.t7z=01;31:*.tar=01;31:*.taz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tgz=01;31:*.tlz=01;31:*.txz=01;31:*.tz=01;31:*.tzo=01;31:*.tzst=01;31:*.udeb=01;31:*.war=01;31:*.whl=01;31:*.wim=01;31:*.xz=01;31:*.z=01;31:*.zip=01;31:*.zoo=01;31:*.zst=01;31:*.avif=01;35:*.jpg=01;35:*.jpeg=01;35:*.mjpg=01;35:*.mjpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35"..., "MAIL=/var/mail/root", "NIXOS_ACTION=switch", "NIX_PATH=nixpkgs=flake:nixpkgs", "NO_AT_BRIDGE=1", "OUT=/nix/store/xj3icmv6yp869q7x0bvkvm5g3jda9b1r-nixos-system-wsl-24.11.20240612.57d6973", "PATH=/run/wrappers/bin:/home/sedlund/.nix-profile/bin:/nix/profile/bin:/home/sedlund/.local/state/nix/profile/bin:/etc/profiles/per-user/sedlund/bin:/nix/var/nix/profiles/default/bin:/run/current-system/sw/bin:.:/home/sedlund/bin", "PWD=/nix/store/cvpvxia61l0hxs99lifz0pawa7hpbckm-activatable-nixos-system-wsl-24.11.20240612.57d6973", "QTWEBKIT_PLUGIN_PATH=/root/.nix-profile/lib/mozilla/plugins/:/nix/profile/lib/mozilla/plugins/:/root/.local/state/nix/profile/lib/mozilla/plugins/:/etc/profiles/per-user/root/lib/mozilla/plugins/:/nix/var/nix/profiles/default/lib/mozilla/plugins/:/run/current-system/sw/lib/mozilla/plugins/", "SHELL=/nix/store/3vwx4g1b59z0kzivcmadbjzn3ar1l488-wrapped-bash/wrapper", "SHLVL=0", "SUDO_COMMAND=/run/current-system/sw/bin/strace -f -v -s999 ./bin/switch-to-configuration switch", "SUDO_GID=100", "SUDO_UID=1000", "SUDO_USER=sedlund", "SYSTEMD=/nix/store/xjiifrz7ha6s29gp0p0j3w0155phxmia-systemd-255.6", "TERM=tmux-256color", "TERMINFO_DIRS=/home/sedlund/.nix-profile/share/terminfo:/nix/profile/share/terminfo:/home/sedlund/.local/state/nix/profile/share/terminfo:/etc/profiles/per-user/sedlund/share/terminfo:/nix/var/nix/profiles/default/share/terminfo:/run/current-system/sw/share/terminfo", "TOPLEVEL=/nix/store/xj3icmv6yp869q7x0bvkvm5g3jda9b1r-nixos-system-wsl-24.11.20240612.57d6973", "TZ=Europe/Budapest", "TZDIR=/etc/zoneinfo", "USER=root", "XCURSOR_PATH=/root/.icons:/root/.local/share/icons:/root/.nix-profile/share/icons:/root/.nix-profile/share/pixmaps:/nix/profile/share/icons:/nix/profile/share/pixmaps:/root/.local/state/nix/profile/share/icons:/root/.local/state/nix/profile/share/pixmaps:/etc/profiles/per-user/root/share/icons:/etc/profiles/per-user/root/share/pixmaps:/nix/var/nix/profiles/default/share/icons:/nix/var/nix/profiles/default/share/pixmaps:/run/current-system/sw/share/icons:/run/current-system/sw/share/pixmaps", "XDG_CONFIG_DIRS=/etc/xdg:/root/.nix-profile/etc/xdg:/nix/profile/etc/xdg:/root/.local/state/nix/profile/etc/xdg:/etc/profiles/per-user/root/etc/xdg:/nix/var/nix/profiles/default/etc/xdg:/run/current-system/sw/etc/xdg", "XDG_DATA_DIRS=/root/.nix-profile/share:/nix/profile/share:/root/.local/state/nix/profile/share:/etc/profiles/per-user/root/share:/nix/var/nix/profiles/default/share:/run/current-system/sw/share", "XDG_RUNTIME_DIR=/run/user/1000", "__NIXOS_SWITCH_TO_CONFIGURATION_PARENT_EXE=/nix/store/w5qgrjabiwh5ijm5vmc1kcpn04jfj3nw-switch-to-configuration-0.1.0/bin/switch-to-configuration"]) = -1 EACCES (Permission denied)

Did switch-to-configuration-ng work prior to changing usernames under wsl? I'm going to spin up a windows machine so I can try and reproduce.

I don't recall.  The currently released image is still 23.11, and the first thing I did was to nixos-rebuild my flake onto it username and upgrade it to unstable.  without reading how to do the name change.  This was several weeks ago probably before the *ng switcher was added?
I didn't get around to digging into this specifically until today.
everything on the wsl machine seems ok.  I tend to think this is just my problem as I don't see any related issues in the nixos-wsl issue tracker.
I would try to re-deploy from the 23.11 image and do the upgrade again and properly change the username to test, but I'm currently situated with a very slow internet connection for a bit.

@sedlund Please test the changes in #321662 on your machine! I was able to reproduce the issue on WSL without any changes to the stock NixOS-WSL setup (and no name changes either).

@jmbaur Tested on my WSL and it looks good!  Also tested on regular nixos x86_64.
Looks good!   Thanks very much


color picker uses invalid alpha format

https://v.usetapes.com/Nu25L75YLh
It should be rgba(x,x,x,y)

It actually supports both of them, if you click the rgb tab at the bottom of the dialog and then change the opacity, it'll produce result in that format.
Also this package has no color picker code in itself, it's just a proxy to https://github.com/thomaslindstrom/color-picker

we should remove any options that will break Flint, or add options in color picker via pull requests that allow us to hide things that break flint

Filed here https://github.com/thomaslindstrom/color-picker/issues/170


Docs/binder v2

Description
This PR intends to create a binder enviroment of this repository along with mongodb and other required dependencies

Related Issues

Checklist

[ ] Is this code covered by new or existing unit tests or integration tests?
[ ] Did you run make test successfully?
[ ] Do new classes, functions, methods and parameters all have docstrings?
[ ] Were existing docstrings updated, if necessary?
[ ] Was external documentation updated, if necessary?

Additional Notes or Comments

Codecov Report
Patch coverage has no change and project coverage change: -0.01% :warning:

Comparison is base (0d08229) 79.66% compared to head (aadc8a8) 79.65%.
Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #608      +/-   ##
==========================================
- Coverage   79.66%   79.65%   -0.01%
==========================================
  Files          79       79
  Lines        4819     4813       -6
==========================================
- Hits         3839     3834       -5
+ Misses        980      979       -1

see 5 files with indirect coverage changes

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


fit pca on a smaller sub sample

Fitting PCA on just 500 samples makes the code faster and reduces memory requirement. The performance might reduce slightly.

Also added svd_solver="full" to fix issue related to ValueError: array must not contain infs or NaNs

Results with modification to code. dinov2_matching.pdf

Thanks for your PR. That method is ok for visualization.
Additionally, tokens from multiple images (e.g. a small target dataset) can be used to fit a PCA to use it in place of random sampling. Thus, instead of random sampling + fitting 500 dim vectors using PCA, it is possible to project from the input dimension to 3 directly using the pre-configured PCA.


KAFKA-14585: Refactoring for moving the storage tool

Refactoring related to #14847.
The following properties are migrated from KafkaConfig (core).

LogConfig (storage)

log.dir
logs.dirs
metadata.log.dir
inter.broker.protocol.version
unstable.api.versions.enable
unstable.metadata.versions.enable

RaftConfig (raft)

node.id
process.roles

@showuon I rebased and addressed your comments. Did not remove properties definitions from KafkaConfig, because this breaks a lot of tests. I think this should be done as part of KafkaConfig migration. In the end it is a small amount of duplication, but properties are always defined in one place.

Thanks @fvaleri ! I had another look, and still think the duplication is not a great idea. It might cause potential issue someday, even if it looks good now. From what I can see, almost all the config validation exists in KafkaConfig, so could we remove the config definition in LogConfig? My imagination is the LogConfig can do something similar as RaftConfig, that has no config definition there. If you want to have a copy of the config value, you could pass in KafkaConfig instance into LogConfig here. Do you think that make sense?

Closing this one in favor of the work done for KAFKA-15853.


Creating new python function app project failed on UNC paths

Repro steps:

try to create new python azure function app project

Running command: "py -3.6 -m venv .venv"...
'\CNFCNPL40E\ISHomeDir02<userID>\My Documents\dev\python\incapsula-token-app'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported.  Defaulting to Windows directory.
Error: [WinError 5] Access is denied: 'C:\Windows\.venv'
Error: Failed to run "py -3.6" command. Check output window for more details.

Action: azureFunctions.createNewProject
Error type: Error
Error Message: Failed to run "py -3.6" command. Check output window for more details.
Version: 0.18.1
OS: win32
Product: Visual Studio Code
Product Version: 1.38.0
Language: en

Call Stack
Object.<anonymous> extension.bundle.js:1:135603
o extension.bundle.js:1:134668

@JackHartCNB looks like VS Code doesn't support this by default and you have to follow a few extra steps to make it work. See https://github.com/Microsoft/vscode/issues/22872#issuecomment-288240595


[TR#19] Side Panel

Task
TR #19
Why?
Side Panels are a common use-case for various application needs
What Changed

[X] Add Side Panel
[X] Update Alert Docs JS to allow fixing a storybook documentation style conflict

Sanity Check

[X] Have you updated any usage of changed tokens?
[X] Have you updated the docs with any component changes?
[X] Have you updated the dependency graph with any component changes?

[X] Have you tried building the css?
[X] Have you tried building storybook?
Do you need to update the package version?

Screenshots

 Side Panel

 Build common layout templates in Figma with mirrored code in our docs


npm publish v1.0.0

Hi @fouad
Could you publish the latest version of this package or provide access for me to do so please?
Thanks,
Woody

@f2prateek could you help with this one?


I have some questions about receiving messages

Hi ,recently I am doing some work on your jabit SDK. But now I have some trouble with receiving messages. What should I do for receiving message ?
1，For receiving messages , the only thing I need to do is building the Context of BitmessageContext ? Is it right ? Is there anything else I have to do ?
2，Did the bmContext need the identity of  address to receive messages ? Or the bmContext receives all the meesages , and get the specified message out of them by the identity of  address ?
3，Based on the Question2 , Can I receive messages of three identities at the same time ?
Thank you for your reply .

@Dissem I alse hope your reply.

I'm sorry for the late reply. I hope those answers will help:

You will also need to call startup() on the context, so it starts connecting to the BM network
I'm not quite sure I understand the question. In order to receive messages sent to a specific address, the context must of course know the corresponding identity. Usually it's the other way: you create a new identity using the context, and start sending messages to its address.
If you just want to start a relay that gets messages and distributes them, no identity is needed.
Yes, you can have as many identities as you want. Please be aware that the more identities you have, the more CPU is used. I didn't make any tests, but 3 identities certainly are fine, with hundreds or thousands you might experience some issues. (In case you do any tests, I would be interested in the results)

@Dissem By trying more times, messages can be sent and received. Thank you for your patient reply.


Lazysizes plugin integration

I have a new issue with my integration.
I try to use the plugin only with jquery. The problem is that all originals images are loaded when the page is loading. After that, responsive images are lazy-loaded normally when I scroll my page.
My reflection :

I replace src attribute with a small image - but browser keeps to load original images before change src with this small image.
all images aren't display in the viewport when the page load because I use the padding ratio trick for each of them.
I tried to move my script in the header of the page, but nothing change.
I run my script in a  $('document).ready before lazysizes script

Maybe this isn't possible only this Jquery ? Do I need to rewrite my script with a server-side language like php ?
here my script :
//lazy init
window.lazySizesConfig = window.lazySizesConfig || {};
lazySizesConfig.loadMode = 2;
lazySizesConfig.preloadAfterLoad = false;
$('img').addClass('lazyload');

$("img.lazyload").each(function() {
var src = $(this).attr('src').replace(/\.jpg$/i, "");
$(this).attr("data-sizes","auto");
$(this).attr("data-srcset",
  src + '-240.jpg 240w,' +
  src + '-360.jpg 360w,' +
  src + '-480.jpg 480w, ' +
  src + '-720.jpg 720w,' +
  src + '-768.jpg 768w,' +
  src + '-960.jpg 960w,' +
  src + '-1280.jpg 1280w'
);
$(this).attr(
   "src",
   "data:image/gif;base64,R0lGODlhAQABAAAAACH5BAEKAAEALAAAAAABAAEAAAICTAEAOw=="
);
});

Maybe this isn't possible only this Jquery ? Do I need to rewrite my script with a server-side language like php ?

It depends: I don't know what you want to achieve in general. What I can say for sure, you will never get image request aborted in Safari.

The problem is that all originals images are loaded when the page is loading.

Normally the so called preload parser gets all image sources and starts to download those images. This happens before scripts and stylesheets are loaded, parsed and evaluated. It actually also happens before even the DOM is parsed. Therefore you won't be able to remove these image requests entirely with JS and yes you need to render the HTML without src to get this done.
However Chrome, IE and Firefox 36+ do support aborting an already started image download (This means it doesn't work in FF 35- and it won't work in any Safari/Webkit version). But this needs to be done quickly, you can't wait for the dom ready event for this.
You can try this by doing the following. Move jquery and all your JS at the bottom of your page (or add the async and then include the following script inline (not in an external js file!), after all images but before any other JS file, that has no async attribute:
<script>
[].slice.call(document.querySelectorAll('img[src]')).forEach(function(elem){
	var src = elem.src.replace(/\.jpg$/i, "");
	elem.setAttribute('data-sizes', 'auto');
	elem.setAttribute('data-srcset', src + '-240.jpg 240w,' +
		src + '-360.jpg 360w,' +
		src + '-480.jpg 480w, ' +
		src + '-720.jpg 720w,' +
		src + '-768.jpg 768w,' +
		src + '-960.jpg 960w,' +
		src + '-1280.jpg 1280w');

	elem.className += ' lazyload';

	if(!elem.complete){
		elem.removeAttribute('src');
	}
});
</script>

With this approach you will see that some images are fully loaded (2-6), but most are aborted (you will still see them in the network panel, but the downloaded data/size is (much) smaller than the actual size of the image).
Please close if this answers your question.

Ok, it's what I thought... the right way of this integration is to use a server-side language. Do you have a link to a tutorial for a php integration of lazysizes ?
Thanks a lot.


Script of generating the RGB-D point cloud using the sequences of RGB-D images

Thanks for your code release, I want to know whether can I obtain the script of generating the RGB-D point cloud using RGB-D images for ScanNet

Hi, it happens in the data loader, you can refer to the relevant part of the code here: https://github.com/ayushjain1144/odin/blob/main/odin/data_video/dataset_mapper_scannet.py#L264-L269

Thanks for your answer, another question is that for the scannet intrinsic matrix. I see that your code has provided the intrinsic matrix for scannet data:
def get_scannet_intrinsic(image_size, intrinsic_file=None):
    scannet_intrinsic = np.array([[577.871,   0.       , 319.5, 0.],
                                  [  0.       , 577.871, 239.5, 0.],
                                  [  0.       ,   0.       ,   1., 0. ],
                                  [0., 0., 0., 1.0]
                                ])
    scannet_intrinsic[0] /= 480 / image_size[0]
    scannet_intrinsic[1] /= 640 / image_size[1]
    return scannet_intrinsic

It's a little diffferent from the original scannet depth intrinsic matrix:
575.491882 0.000000 321.158966 0.000000
0.000000 578.235840 242.023804 0.000000
0.000000 0.000000 1.000000 0.000000
0.000000 0.000000 0.000000 1.000000

May I know the reasons behind the difference?

Besides, I didn't find any inference script in the repo, only training script found. May I know when will the inference script be released? Thanks so much!

Hi, I don't remember exactly where I took this intrinsics from, but it was from some prior codebase I believe. Feel free to use the different intrinsics, I don't think they would make any difference (but let me know if they do make a difference!)
For evaluation, you basically need to add --eval-only flag (and use the right checkpoints as referenced in the readme). let me know if the readme is unclear/confusing in some aspect.


Issue with dropping and adding different widgets on to the grid

I have been having issues trying to add different widgets on to the grid. I'm trying to incorporate a sidebar that has different items in it to which I can drag and drop them anywhere on the grid. I've been looking over the examples provided such as the toolbox example and the drag from outside example but they don't really help me understand how I can use multiple widgets. The issue that I keep getting is that no matter which widget I drag from the outside, the same one will appear on the grid. I just need a clear explanation on how to add different widgets that are outside of the grid because I'm still new at this. One example that I would like to sort of imitate is the gif @daynin posted on #980

This is exactly what I am looking to do!!  Drag an item from an external list and have it appear as a new item in the grid.

It's good to know that I'm not the only one with this problem. It would be great if a solution could be shared to help us out. I've tried other packages like react-beautiful-dnd but that is generally for creating and rearranging lists which isn't what I am aiming for. I've also been trying to find examples on codepen and codesandbox that might have something similar to what I'm trying to accomplish but I have yet to find one.