move constructor missing on ElementReference

The ElementReference contains a
Vc_INTRINSIC ElementReference(const ElementReference &) = delete;

this seems to imply (didn't check the standard...) that the move constructor is also not available.
This poses some issues is our code. We provide several helper functions, which are specialized for different SIMD types, for example a lane function, which allows immediate access to a particular lane. This is specialized for scalar C++ types and for SIMD types. This function fails since the introduction of ElementReference (we didn't update in a while...) and the obvious fix (auto return type and std::move) does not work, because the move constructor is missing.
Adding
Vc_INTRINSIC ElementReference(ElementReference &&) = default;

fixed everything for us. I'm not sure about the reasons not to include the move constructor...
Can this fix be included? Or what are the reasons to prohibit this? I understand that we want to avoid copying references, but a std::move should be ok.

The semantics of ElementReference are modeled after subscripts on Clang vector builtins. I.e. you can only assign to them directly, never take an address of it. This design is also the guidance from the C++ committee on this issue.
In previous Vc versions the subscript operator returned a "proper" lvalue reference. This is not implementable with standard C++, as it requires special measures to turn strict aliasing optimizations off. GCC and Clang provide this via the [[gnu::may_alias]] attribute. But note that this attribute can get lost in certain situations, so that I'd like to keep use of this workaround down to a minimum and never leak such may_alias types through the public interface.
So why no move on the reference wrapper? Technically, I don't see an issue with it either. But from an interface design view there's a good reason. Consider what happens when you can work with lvalues of ElementReference: you can store them and keep them around for as long as the Vector object lives. While you can do this for std::array too, the situation is slightly different for Vector, since ElementReference implements type-punning.
However, IIUC, all that you really need is guaranteed copy-elision (i.e. C++17). You just want to return an ElementReference object from a wrapper around Vector::operator[], right? I expect that this'll just work fine when you flip the -std= switch. See here: https://godbolt.org/g/uJ2eyM
Hmm, then again, C++17 enables users to create ElementReference lvalues through guaranteed copy elision. So maybe it is a sensible idea to provide the move ctor until users switch to C++17. Any opinion?

While I understand you argument regarding the life time of objects, I don't think this is something we should enforce here. In general many interfaces allow access via a mutable reference and it is always something where the documentation has to be clear regarding the lifetime, but the compiler can't do the work for you.
In the case of SIMD data structures, I think it is the exact right thing to go via the wrapper, as there might even be types where you can't provide a reference to double or float due to aliasing. On the other hand we want it behave like a reference and this implies that there is some way of copying or moving the thing around. copying might become costly, some is imho preferable. You reference the C++17 standard, where copy-elision allows me to avoid the copy immediately due to compiler support. But does this really change anything? Internally the compiler does basically a move, so I think it would be better to directly allow the move. It is a clear construct, it can't be done implicitly like in the case of a reference, so users should be aware of the problem (as they explicitly have to write std::move instead of a simple assignment) and it avoid additional overhead.

I can prepare a patch... (including documentation)

I created an according PR...


fix(numpy): remove np.float_ and np.complex_ for compatibility with numpy 2.0

This PR removes np.float_ and np.complex_ that have been removed in numpy 2.0 (see NumPy release notes).

np.float64 must be used instead of np.float_
np.complex128 must be used instead of np.complex_

Does the change works on old numpy too?

I have added a check on the numpy's version to make sure it is still working with old numpy versions.


Error when using -filter

Hi,
I am executing the following command
ffmpeg -i /tmp/3fd7c430-f5bc-11e5-82a0-fd37cbe56ffe.mp4 -y -filter:v "select=gte(n\,60)" -frames:v 1 -s 800x600 -f image2 test.png

The code snippet
ffmpeg(tempAssetFileName).addOptions([
  '-filter:v \"select=gte(n\\,60)\"',
  '-frames:v 1',
  '-s 800x600',
  '-f image2'
])
.on('start', function(commandLine) {
  console.log(commandLine);
}).output('test.png')
.run();

The commandLine logged can be executed via in the shell correctly but, the code returns the following
events.js:154
      throw er; // Unhandled 'error' event
      ^

Error: ffmpeg exited with code 1: Error opening filters!
    at ChildProcess.<anonymous> (/Users/jeanre/Work/critique-compositor/node_modules/fluent-ffmpeg/lib/processor.js:168:22)
    at emitTwo (events.js:100:13)
    at ChildProcess.emit (events.js:185:7)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:200:12)

Hello,
Please add a handler for the 'error' event, you'll probably find the reason why it is failing in one of its 3 arguments. Also, avoid passing a full command line as addOptions, this is not what fluent-ffmpeg is for, use dedicated methods instead.


Cannot unlock token on 15.2

I just migrated from an iPhone 8 to an iPhone 13 Pro 256GB
Since then, I cannot unlock tokens that were locked with finger print before. I guess it should ask to use FaceID instead...
Nothing happens when I tap on the locked token...
It does not seem to be the same issue as #258 as there were no photo attached to this locked token and in 15.2 there is no way to add access to Photos for FreeOTP.
All the not previously locked tokens work fine.
The screen capture shows the first token is locked and unusable...

Did you use backup and restore to transfer tokens from iPhone 8 to the iPhone 13 Pro device? Biometrics data is not included in iOS backups by design, therefore locked tokens cannot be transferred.
A warning message about this was added in 019b603c828602cafb2bb828939c0d43c1e38db9 on the add token interface view.

I used peer to peer transfer with both phones side by side...
This locked token is for a highly secure access and was created on the customer's site around 2 years ago, I do not remember this warning message...
I wish I did not already erase the iPhone 8 as of course, I need to access the customer's system urgently and I will have to to onsite instead...
I also have a backup of the old iPhone 8 with iMazing, I will see if I can just restore it before I sell it
Thanks.

Has anyone tried to restore the backup on the old phone in order to make the token work? I'm also locked out because i moved to a new iphone and the tokens are locked.

welcome to the club.... I have tried it and it doesn't work. I have been locked out of my facebook business account because of this. As far as i know the tokens are lost. they cannot be unlocked..


Add programming note for strided load/store with stride of 0.

address https://github.com/riscv/rvv-intrinsic-doc/issues/78.

Thanks to fix my typo!!


SIP Features improvement

Description
Add version to @SIPFeature annotation and additional conditions on actuator extensions
Please delete options that are not relevant.

[x] New feature (non-breaking change which adds functionality)
[x] This change requires a documentation update

How Has This Been Tested?
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing (regression) unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

I'm not sure if for all of the features it should be possible to tur them off. But we can handle it in separate task.


Fix : Only open properties array popup if mouse is on left margin

Fix for #55401 so that there is only one popup at a time.

cc @groud

I think that's an acceptable workaround, but I am not sure this is the best way to fix the issue.
In a normal situation, the first popup should simply accept the event and not propagate it to the parent, so the second menu should not pop up. I would first make sure the event is accepted correctly (with accept_event() if I am not mistaking) in the property editor, and if not, fix the problem there.

Properties do not shows up anymore on array element, and as the file has changed a lot since my pull request it is no longer relevant


Type on Step 5: Get data updates

"In this step, you modify the application to display messages that are send to Firebase from any client."
Should say:
"In this step, you modify the application to display messages that are sent to Firebase from any client."

This is a collection of codelabs. Which codelab exactly are you referring to?

Firebase: Build a Real Time Web Chat App


Reduce flakiness of 2e test

make killApiConnection async, the execution time of the synced version isn't reliable
let checkNoNodeRecreate consistently do the check for some minutes instead

/hold
run e2e a few times to see if this helps

/test e2e-test

/retest

/test e2e-test

/test e2e-test

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/test e2e-test

/retest
no clue if this makes things better... but I think it also doesn't make things worse

yeah, I think https://github.com/medik8s/poison-pill/pull/72 makes a real improvement.
the last failure is the first to fail on logs

I believe that https://github.com/medik8s/poison-pill/pull/107 has done similar thing but with different approach - blocking until context is expected to expire. e2e test seems to be much more stable now (5 out of 5).
I'm closing this, let me know if you have any objection


Implementing google translate API into the chat.

Hi, I am trying to implement a google translate API  into the default chat on the website (Twilio). I am not sure which files to configure, can someone help?

Or is it possible to add other users to the chat? The messenger. (I would add a translation bot)


Use Casbin as the authorization module for etcd

Hi, I'm the creator of Casbin. It is a Go authorization library that supports access control models like ACL, RBAC, ABAC. See details here: https://github.com/casbin/casbin
I noticed the etcd uses a RBAC model to do the authorization. However, I don't think it's flexible or enough secure. In terms of flexibility and security, Casbin will bring several advantages:

the current permissions can only be granted to roles, cannot directly granted to users. Sometimes this is inconvenient. Casbin supports assigning permissions to both roles and users.
the current RBAC doesn't support cascaded roles (aka only RBAC0), while in Casbin, roles can be cascaded, aka roles can have roles (so RBAC1 is supported).
Casbin also supports resource roles (or groups), so we can group some keys and use groups instead of resource keys in permission granting. This is useful when we have some important built-in keys that want to protect (for example, the keys used by Kubernetes), so we can define these keys into a group like built_in_keys.
Current etcd only has two permissions (or actions): read and write, and they are hard-coded in the code. Casbin supports customized actions, for example, the HTTP methods or CRUD or whatever.
Currently root user and root role are hard-coded in the etcd, I don't think it's flexible and secure, because this root can do anything. Maybe a etcd user (like Kubernetes) wants to split the power into several admin users, one for user management, one for permission management and one can read/write all keys to inspect some errors. With current implementation, the etcd user (k8s team) has to modify the source code.
Current etcd only supports Allow authorization. While, Casbin can support both Allow and Deny. In fact, you can use logical or math operators to express your authorization objective.
The resource prefix matching only supports *. Casbin supports the resource matching via regex, so the user can write very flexible matching rules if he knows regex. (Casbin also supports the tradtional * matching).
the permission granting in Casbin can be persisted in files or database, or not persisted at all (just kept in memory), just dynamically modified with Casbin API. Of course, persistence for etcd's permission granting is never a problem and can just store in etcd itself. But Casbin just provides another option for the user to store the policy elsewhere. For example, storing the granting into file in the test stage to test the authorization is more convenient than storing them into the datastore, because files can be easily modified by hand.
Casbin supports a model description language to describe the access control model. So when etcd wants to update its model anytime (e.g., remove the root role or add some ABAC, attribute-based access control support), it will be as easy as modifying the model file, no need to change the code. Because Casbin already supports RBAC and ABAC, and also supports their mix.

So please consider using Casbin. Let me know if there's any question:)

@hsluoyz thanks for your suggestion and sorry for my reply. I'll check Casbin but it would take a time for a while because it is interesting but also difficult. Please feel free to ping me if you feel waiting too long :)

Hi @mitake ,
Thanks for your reply! The model language is a new conception and may be difficult at the first glance, but the core idea is to define the matching rules between the access request and the policy rule, which makes it flexible.
There are many examples here, which shows what this library can do. I will try to make an example specifically for etcd scenario these days.

Hi @mitake ,
I have made a PR about the Casbin auth store here: https://github.com/coreos/etcd/pull/8154
Casbin auth store reuses many functions provided by the original authStore, like user add/delete, role add/delete, authentication related (like password management). Casbin implements the functions mainly for user-role mapping, permission management and permission checking.
The current auth store mixes authentication (AuthN) and authorization (AuthZ) together. AuthN is about who you are (aka log-in), it can use HTTP basic authentication, OAuth, LDAP, etc. AuthZ is about what resource a logged-in user can access. AuthZ can choose to use ACL, RBAC, ABAC, etc. Casbin is only an authorization library. So it can't handle the password checking, and it doesn't maintain the list of users (so no way to add or delete a user), because that part belongs to authentication. So besides integrating Casbin, I also suggest we separate AuthN and AuthZ, maybe an authnStore and an authzStore. So this will be clearer and more convenient to develop alternative modules for different purposes (authn or authz).
I also made some tests in this PR, including features like wildcard (*), RBAC with multi-level inheritance, root support, etc. Other features like regex, ABAC, custom functions are not demonstrated in my test.
I think this shows that Casbin is more flexible in auth policy enforcement. Most of the etcd users are not end-users and they may have need to customize the authorization policy for etcd API. So I think Casbin can satisfy their need.
This PR still doesn't enable Casbin auth store by default. And the policy storage is still using file. I think it should finally use etcd itself for policy storage. I'm still learning the default auth store about its storage part. And I want to hear your advice first. Thanks!

@hsluoyz thanks a lot for your PR, it is very interesting. Providing the flexible authorization policy based on Casbin seems to be very valuable because the default authorization mechanism of etcd v3 is very simple (it is intentional. Complex mechanisms would be able to result unintentional authorization that makes users surprise). I'll review your PR next week because I have some work to do today.
BTW, do you have any suggested docs or papers that is helpful for understanding the design of Casbin?

Hi @mitake these docs may be a help:

The docs for Casbin: https://github.com/casbin/casbin
Docs for Casbin model language: https://github.com/casbin/casbin/blob/master/Model.md
Examples for different models: https://github.com/casbin/casbin#examples

Another question is that my PR still doesn't store policy in etcd itself as what the default auth store does. I still need to learn how to do that. If you have any suggestion for the policy storage, please let me know:)

@hsluoyz thanks for the pointers, I'll visit them.
For storing the Casbin policies in etcd, I suggest following how other auth related RPCs work (e.g. UserAdd(): https://github.com/coreos/etcd/blob/master/etcdserver/v3_server.go#L407). The auth related metadata is stored in their own buckets of backend like this: https://github.com/coreos/etcd/blob/master/auth/store.go#L907
Creating a special bucket for Casbin and adding new RPCs for manipulating it would be a good idea. If you have questions, please let me know.

Hi @mitake ,
I have updated the PR: https://github.com/coreos/etcd/pull/8154. It stores the policy into etcd backend.

For storing the Casbin policies in etcd, I suggest following how other auth related RPCs work (e.g. UserAdd(): https://github.com/coreos/etcd/blob/master/etcdserver/v3_server.go#L407).

The current Casbin auth store uses the same perm management API with the default auth store. So it does not require to change the server API for now. But it may be changed in future.
Here's the roadmap I planed personally, please advise:

Create the Casbin auth store, which uses the same permission management API with the default auth store. Make sure Casbin can provide at least the same capability as the original auth store.

Separate the authentication (AuthN) and authorization (AuthZ) in the default auth store, maybe via two stores: an AuthN store and an AuthZ store. This will serve as a good basis to replace the AuthZ-specific part with other libs like Casbin. So we can still use the original AuthN store after replacing the AuthZ store. (I don't know if this is a good idea?)

Make Casbin the default AuthZ store. This may need more test, because all users will use it now. (if this is not acceptable, I'm also OK with the current optional way. So any user who wants to use it can enable it in code or via an etcd API).

Enhance the authorization and provide more features based on the new Casbin authZ store, including enhancing the permission management API at etcdserver. And etcdctl can support the new perm mgmt commands too.

Please advise:)

The auth related metadata is stored in their own buckets of backend like this: https://github.com/coreos/etcd/blob/master/auth/store.go#L907

A backet named casbinAuth is created to store the auth policies. But the Casbin model is still in file, because I think it's static and won't change at run-time. Is this OK? If not, I can also change to initialize the Casbin model in Golang code.

@hsluoyz sorry for my late response, I'll reply this wednesday possibly (your idea and PR are interesting but heavy ;)

@mitake , thanks, let me know for any questions:)

this is not active. we do not have any plan to make etcd auth more complicated at the moment. so closing.


Parameterise StakePools API over apiPool type

Issue Number
ADP-311, #1718
Overview

[x] I parameterised StakePools API over apiPool
[x] I renamed ApiStakePool to ApiJormungandrStakePool, such that we can later introduce a haskell ApiStakePool
[x] I made the default Api type use ApiJormungandrStakePool. We should later switch to ApiStakePool, and update the swagger scheme such that it targets haskell, and not jormungandr.
[x] I moved StakePoolLayer to the jormungandr package.

Comments

I am keeping the Pool DB in core, since I think we still want it. But I have not thought about how it would work with shelley.
changelog: this is pure refactoring, but in combination with follow-up PRs this is a new feature.

bors try

bors r+

bors r-

bors r+

bors r+

This doesn't make sense, because this is not the actual code:
src/Cardano/Wallet/Shelley/Api/Server.hs:23:1: error:
    Could not find module ‘Cardano.Pool’
    Perhaps you meant
      Cardano.Pool.DB (from cardano-wallet-core-2020.6.5)
    Use -v to see a list of the files searched for.
   |
23 | import Cardano.Pool
   | ^^^^^^^^^^^^^^^^^^^...
[2 of 6] Compiling Cardano.Wallet.Shelley.Compatibility ( src/Cardano/Wallet/Shelley/Compatibility.hs, dist/build/Cardano/Wallet/Shelley/Compatibility.o )
[3 of 6] Compiling Cardano.Wallet.Shelley.Network ( src/Cardano/Wallet/Shelley/Network.hs, dist/build/Cardano/Wallet/Shelley/Network.o )
[4 of 6] Compiling Cardano.Wallet.Shelley.Transaction ( src/Cardano/Wallet/Shelley/Transaction.hs, dist/build/Cardano/Wallet/Shelley/Transaction.o )
builder for '/nix/store/q9jxhhslcw0j4f4aqdkn3xpvyyx0y9z6-cardano-wa

The build failure can't be cached, since master has changed?

Ok, it is because of the merge 🤔

bors r+


istioctl x create-remote-secret should accept an optional name

istioctl x create-remote-secret creates a k8s secret with credentials to access the current cluster. It populates the secret name and key within the secret using the cluster's kube-system UID. This is essentially unique across environments which is useful for tooling. Our docs, however, still refer to hardcoded names such as ns-k8-config. It would be helpful to provide an option for the user to override the default ClusterID with their own. Something like the following could work:
istioctl x create-remote-secret --name ns-k8s-config

fixed by https://github.com/istio/istio/pull/21223


Migrate to version catalog.

Moved classpath and dependencies into version catalog and deleted dependencies.gradle file.
Intended to fix #103.

Thanks!


Bulking out documentation; dynamic version; test workflow

Locally the documentation builds, albeit with TypeError reported on imports from numba.
Here I've added the following sections...

Introduction
Installation
Usage
Contribution
Code of Conduct
copying (not yet linked)
API documentation

Not all modules, classes or functions/methods have docstrings as yet (run pylint from project root to see what is missing).
For now I'm checking the workflow builds and deploys the documentation correctly.

Codecov Report

Merging #44 (f1a10a3) into main (5a8aa0a) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head f1a10a3 differs from pull request most recent head c632c0a. Consider uploading reports for the commit c632c0a to get more accurate results

@@           Coverage Diff           @@
##             main      #44   +/-   ##
=======================================
  Coverage   83.26%   83.26%
=======================================
  Files           9        9
  Lines         998      998
=======================================
  Hits          831      831
  Misses        167      167

Continue to review full report at Codecov.

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

Apologies for the masses of commits, I've been working on this in tandem with developing and testing the PyPI release (and should really get in the habit of holding back and rebasing/squashing).
I've used @jwillbailey excellent Notebooks and have (hopefully) translated them to docs/usage.md. One of the challenges with releasing to PyPI is including the recipes, and they are included in Test PyPI - pyclarity but where they are installed depends on what Virtual Environment is being used. I've included examples of where they might be and how to find them on UNIX like systems.
The documentation builds and is currently deployed to claritychallenge.org/clarity. I think I tweaked most docstrings to build (many required an blank line before the Args and Returns headers for Sphinx to build). At the same time I've applied Black formatting so whilst there may look like a lot of changes many are cosmetic.
If anyone is keen to test the documentation Usage instructions against an install from Test PyPI then you can create a clean Virtual Environment and install with...
pip install --index-url https://test.pypi.org/simple/ --extra-index-url https://pypi.org/simple/ pyclarity==0.1.8

This will install pyclarity from test.pypi.org but all other packages that it requires from pypi.org.
I know there is on-going work with regression tests to be pushed before we can release to PyPI and I've a branch with some changes on that I'll hold back on until everything is ready.
Feedback more than welcome and if there is anyone else who could be included as a reviewer please let me know, the more eyes the better. :eyes:

Thanks Jon.
Good idea on additional pre-commit hooks (I'm liking pre-commit more and more, I had been experimenting with Megalinter but pre-commit seems much nicer).
The only existing hook for checking docstrings is check-docstring-first which only checks they are in the correct location.
On a related note typehints are used throughout the code but currently the pre-commit for checking these with mypy are disabled. I've had a quick look and there are 86 errors currently reported, although about 30 or so of these are warnings of the type missing stubs or py.typed marker and pertain to imported libraries.
Would you like me to address these and enable mypy typehint checking in pre-commits?  If so I'll write it up as an issue for me to work through.

Hi Neil,
Yes, good idea - let's start a branch for integrating mypy in the
pre-commits. I'd commented it out simply because we previously didn't have
many (any?) type hints in the code.  I don't have a lot of experience with
mypy, but I guess many of the issues will be fixed by tweaking the type
hints but some could be detecting some genuine errors. If you can deal with
clear cases I'm happy to look at anything not obvious.
Cheers,
Jon
On Fri, 29 Jul 2022 at 11:00, Neil Shephard @.***>
wrote:

Merged #44 https://github.com/claritychallenge/clarity/pull/44 into
main.
—
Reply to this email directly, view it on GitHub
https://github.com/claritychallenge/clarity/pull/44#event-7088224698,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACO7SJC22Z5VRBQF73I7O3DVWOTULANCNFSM54HNA7SQ
.
You are receiving this because your review was requested.Message ID:
@.***>

--
Professor Jon Barker,
Department of Computer Science,
University of Sheffield
+44 (0)<PHONE_NUMBER>

Thanks Jon,
I've created #53 to address this. Because your current pull request #52 addresses quite a few of the errors reported on main I'll hold back on starting work until that has been merged, although I can make the necessary change to pyproject.toml now to suppress error messages based on imports.
Neil

Thanks for the code review. I’ll deal with remaining issue on #52 this
evening so that it is ready to merge.
On Fri, 29 Jul 2022 at 14:48, Neil Shephard @.***>
wrote:

Thanks Jon,
I've created #53 https://github.com/claritychallenge/clarity/issues/53
to address this. Because your current pull request #52
https://github.com/claritychallenge/clarity/pull/52 addresses quite a
few of the errors reported on main I'll hold back on starting work until
that has been merged, although I can make the necessary change to
pyproject.toml now to suppress error messages based on imports.
Neil
—
Reply to this email directly, view it on GitHub
https://github.com/claritychallenge/clarity/pull/44#issuecomment-1199308625,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACO7SJEXN42K3CA4CYACZCTVWPOMTANCNFSM54HNA7SQ
.
You are receiving this because your review was requested.Message ID:
@.***>

--
Professor Jon Barker,
Department of Computer Science,
University of Sheffield
+44 (0)<PHONE_NUMBER>


shouldBeCalled assertion

Would it be possible to implement an assertion that asserts that a function is called? We have a use-case where our function takes couple of functions as parameters and based on other parameters it may or may not call the functions. We'd like to test that correct functions are being called.
I've seen these kind of functions implemented in JS & Python test frameworks but didn't find such in Kotlintest.

I believe this goes more into mocking and spying business than testing itself.
I don't believe this should be supported by KotlinTest

I don't think there's even a way to verify this without bytecode manipulation, the way mockk does, for example

We could do something like,
someFun.shouldBeInvoked {
.. some code here that uses "it".
}
It wouldn't be as powerful as mocking, but might be ok for simple scenarios.

I've added the following matchers to master:
   val fn0 = { println("") }
   fn0.shouldBeInvoked {
      it.invoke()
   }
   val fn1 = { a: String -> println(a) }
   fn1.shouldBeInvoked {
      it.invoke("qwe")
   }

Does something like that work for you @joni-

I think this goes too much into mocking business, doesn't it?

It's just wrapping a function. I guess you could call it mocking but it
doesn't do any jvm tricks.
On Mon, 13 Jan 2020, 18:32 Leonardo Colman Lopes<EMAIL_ADDRESS>wrote:

I think this goes too much into mocking business, doesn't it?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/kotlintest/kotlintest/issues/1015?email_source=notifications&email_token=AAFVSGQ7FO6XZALGWJYVKJTQ5UBYJA5CNFSM4I3D57W2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEI22LLA#issuecomment-573941164,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFVSGQ7RQBMRSKTJAIJGATQ5UBYJANCNFSM4I3D57WQ
.


Remove edpm_encoded_privatekey workaround

As agreed, removing the workaround after merging https://review.rdoproject.org/r/c/rdo-jobs/+/49298

recheck

recheck

recheck

recheck

lgtm and green run here https://review.rdoproject.org/zuul/buildset/74c53e39eabf4901b47669e896edb020
going to merge @fao89 ... other cores are out this week and this is a simple fix that follows on from yesterday's merge


bug-fix single-edge-definition-editing

Scope & Purpose
Short: fixed editing single occurrence of an edge definition in case of multiple available graphs.
e.g. Graph A has edge definition Z
e.g. Graph B has edge definition Y
Now we want to change edge definition Z. This will be tried for both graphs and will fail for Graph B.
This PR fixed that behaviour.
(Can you describe what functional change your PR is trying to effect?)

[x] Bug-Fix for devel-branch
[x] Bug-Fix for a released version (needed, yes, all supported versions)
[x] The behavior in this PR can be (and was) manually tested
[x] The behavior change can be verified via automatic tests

Related Information
(Please reference tickets / specification etc )

[x] There is a JIRA Ticket number: https://arangodb.atlassian.net/browse/DEVSUP-509

Testing & Verification
This PR adds tests that were used to verify all changes:

[x] Added new integration tests (i.e. in shell_server / shell_server_aql)
./scripts/unittest shell_client --test tests/js/common/shell/shell-general-graph.js

http://jenkins01:8080/view/PR/job/arangodb-matrix-pr/7678/

Jenkins green.


In-Game Tooltip redraws every time the durability on a tool updates.

Fix is just by making it not respond to the metadata values for tools or other things that'll be updating their metadata value as you hold them

Two fixes, either make it so if the meta changes but your slot didn't, don't redraw the tooltip, or two, make it so the durability is displayed when holding a tool.

Made the latter as a solution since the solutions I can think of to make the former are way too funky. Check out your DMs and close it if you like the solution.

Ok, durability is considered a different option for a different day, fixed it normally.


Build fixes for compiling NuttX with Eigen

Adds some missing macro definitions to ctype.h which are required to get Eigen to compile.
It also modifies time struct tm adding some data fields that were commented out /*not supported*/ (required by Eigen as well).

Awesome, thanks! @davids5

This does not look appropriate for upstream NuttX.  There are two basic challenges and the will not be accepted upstream:

Definition of bit maps.  Not used in NuttX.  Defining these would be a timebomb since any use of them is inherently wrong.

Unused fields in struct tm are uncommented.  This is less lethal, but certainly is not desireable, expecially for parts with highly constrained memory usage.

@nuttx I'd like to do a bit more readup on the C++ standard before drawing any conclusions, and this patch set wasn't submitted upstream because we know there is more evaluation to be done.

I am very picky about what goes into NuttX header files.  I don't accept non-standardized changes to go into them just to permit external code to compile; nor do I accept changes that imply something is implemented when it is not (although there are cases like that in the code).
While I refuse to put such non-standard or useless stuff in NuttX header files, there are ways to work around this.  Here is somoething that I proposed to David:  Suppose there is a directory called myincludes/ and in myincludes/ is a header called ctype.h.  In this ctype.h is:
#define _U  01
#define _L  02
#define _N  04
#define _S  010
#define _P  020
#define _C  040
#define _X  0100
#define _B  0200
#include_next <ctype.h>
And suppose that there is another header time.h that looks like this:
#define tm __tm
#include_next <time.h>
struct tm
{
int tm_sec;     /* Seconds (0-61, allows for leap seconds) /
int tm_min;     / Minutes (0-59) /
int tm_hour;    / Hours (0-23) /
int tm_mday;    / Day of the month (1-31) /
int tm_mon;     / Month (0-11) /
int tm_year;    / Years since 1900 /
int tm_wday;    / Day of the week (0-6) /
int tm_yday;    / Day of the year (0-365) /
int tm_isdst;   / Non-0 if daylight savings time is in effect */
};
Then in your CFLAGS, you use an -isystem setting to include files from myincludes/ before nuttx/includes. In this way you an append or modify any of the NuttX header files with my having to accept changes that I do not want upstream.
Here is an example where I used this technique in the past to graft MMU-less shared memory support into uClibc++: http://xflat.cvs.sourceforge.net/viewvc/xflat/xflat/arch-include/ .  Works nicely and gives you independent control over the content of header files.
Greg

@Zefz  Please let me know once you have a build with Eigen in the Firmware repo.
For the short term, we will use the "PX4 build time patching" from the nuttx-patches directory. (It is old school but easy to understand) I will generate a PR to your PR for Eigen in the Firmware repo that will add the patches.
For the long term:
I will research the usage of the #defines from ctype.h to determine how and if their usage is a legitimate c++ requirement/dependance or just a use of an implementation detail that should be carpartimantlized.
Once that is sorted, out we can discuss what is the best long term way to move forward with these ctype.h related changes.
On the issues of time.h
The long term solution would be as follows as follows:
Greg is open to incorporate a patch upstream, If we provide the code to support the implementation of the extended time functions:
Day of the week
Day of the year
Is daylight savings time is in effect

wrapped in CONFIG_TIME_EXTENDED
That is on my list to do.

@davids5 Eigen is now added to the PX4 repository through this pull request:
https://github.com/PX4/Firmware/pull/1929

@Zefz Sorry for the delay. I have submitted patches https://github.com/PX4/NuttX/commit/6c18397707a17eb2097f4957fb4355a46398958d to Greg in support of the nuttx/include/time.h extension. nuttx_next currently has those changes applied for testing. As far as the ctype.h changes. These are being handled as buildtime patching in the nuttx next branch.
There still the concern of binary incompatibilities due to the inclusion of toolchain header files that need to be scrutinized and in the long term resolved.

@LorenzMeier the patches have been submitted.

@Zefz This is applied to our current WIP branch and David is working on the more long-term solution with Greg.


error: no member named 'stack' in namespace 'std'

In file included from /disk-samsung/freebsd-ports/science/dd_package/work/dd_package-2.1.0/include/dd/Export.hpp:13:
/disk-samsung/freebsd-ports/science/dd_package/work/dd_package-2.1.0/include/dd/Package.hpp:2212:18: error: no member named 'stack' in namespace 'std'
            std::stack<Edge*> stack;
            ~~~~~^

Every C++ module using some STL class is expected to include the header for this class.

Thank you for bringing this error up. It is fixed in the current main branch. I'll try to create a new release today.


Support for Explicitly built modules

Hello,
Do you think adding support for Explicitly built modules will be useful for Scipio ?

https://developer.apple.com/videos/play/wwdc2024/10171/
https://useyourloaf.com/blog/xcode-explicitly-built-modules/
https://bitrise.io/blog/post/demystifying-explicitly-built-modules-for-xcode

Hi! I don't plan to enable Explicitly built modules, however, you can pass any XCConfig to use extraBuildParameters option


Flash Rendering Has Not Been Implemented Consistently Across Our Site

Small notifications to inform a user that their action has been successful would add a nice touch to our site. We have to implement these consistently throughout.

See Issue #133


[Core] add standard "read-only" property to any DocStore

the read-only store must implement MapLoader interface only and bypass any store/delete attempts

implemented; awaiting tests

done


[WIP:] init new way of doing integration tests in more maintenable and user-friendly fashion

wip

closing for the moment, i still have the branch


Crash occurring on Keyboard Extension on Landscape Orientation

Run the Demo App's keyboard target (Keyboard Extension) on Safari.
Or open Safari & Change Keyboard of KeyboardKit Locale
Change keyboard with any locale.
Now change orientation to Landscape.
UI break occurs

Actually there was an crash
open func keyboardLayout(for context: KeyboardContext) -> KeyboardLayout {
layoutProvider(for: context).keyboardLayout(for: context)
}
When changing orientation this method calling infinite times. So crash occurs.

I see the same crash, but only in Safari.

@reazsumon I have a solution for this problem, but would like some people to try it out.
Basically, syncing the context in viewWillLayoutSubviews() caused layout to change, which caused the function to be called again, which caused a new sync etc.
Removing the context sync in viewWillLayoutSubviews() seems to have solved the problem, so I am considering releasing a new 5.9.2 with this fix before releasing 6.0.
Could you try this out and see if you can notice any negative side-effects with not syncing the context here?

I have released this fix in 5.9.2, since I can't reproduce the bug in Safari now.
Just let me know if you're still experiencing problems and I'll look at it again.


Test with armbian on cubietruck

Based on fresh jessie armbian installation and following the blog guide as a base.
Installed docker-compose from dpkg directly, since the following did not provide the package, only the docker-hypriot package.
curl -s https://packagecloud.io/install/repositories/Hypriot/Schatzkiste/script.deb.sh | sudo bash

Armbian does use init instead of systemd by default, which leads to:
$ sudo systemctl start cluster-start
Failed to get D-Bus connection: Unknown error -1

Found the following solution to change to systemd http://forum.armbian.com/index.php/topic/342-dbus-error-when-using-systemctl/
Latest not so easy solved problem is that the kernel does not support vxlan, which leads to not working overlay networks. In order to make this work the kernel has to be recompiled with the option -> Device Drivers -> Network device support -> Network core driver support -> Virtual eXtensible Local Area Network (VXLAN) [m].

@MariusRumpf: We will soon have a FAQ, which will also cover of how to use our "Schatzkiste" properly. This would have made your day easier. Sorry for now!
We recommend to copy & paste this into the terminal:
sudo apt-get update
sudo apt-get install -y apt-transport-https
echo "deb https://packagecloud.io/Hypriot/Schatzkiste/debian/ wheezy main" | sudo tee /etc/aptsources.list.d/hypriot.list
sudo apt-get update

Then, install any of the available packages, such as docker-compose like this:
sudo apt-get install -y docker-compose

Thanks for your pointer to the VXLAN kernel option! Do you think you could prepare a small PR that includes your hint in the README.md's troubleshooting section?

@MathiasRenner There is a typo in your example sudo tee /etc/apt / sources.list.d/hypriot.list
But I checked it again now and that works perfect.
Reported the VXLAN kernel option and it has been merged already, so that should be in the next release of armbian kernel. https://github.com/igorpecovnik/lib/issues/134
I will see that I find my complete problem again to show it in the README. I cannot provide a complete tutorial but some resources on how to fix it.

@MariusRumpf in order to check all the kernel settings that are important for running Docker, you should use this script from the Docker repo: https://github.com/docker/docker/blob/master/contrib/check-config.sh. Can you run it on your board and provide the output log, then we can check if there are any other important kernel settings still missing.

@MariusRumpf: Good to hear that it works for you. I updated the command, thanks!
And good to see that Igor handled it in Armbian! :+1: +1

@DieterReuter The check does not provide any notice on the VXLAN kernel flag as far as I noticed.
https://gist.github.com/MariusRumpf/dee22640175d28267558 (with VXLAN enabled in kernel)
The check you posted previosly in your blog does seem to have the same output as I can tell.
https://gist.github.com/hypriot/5d1236bb9c63f7ef7be8 (this had VXLAN disabled in kernel)

You're right, they only check the VETH setting. But these kernel settings are quite OK, maybe some of the optional features could be activated too. Then the kernel would be really perfect for running Docker.

@DieterReuter Or maybe you extend the script to check that flag too. Like so https://gist.github.com/MariusRumpf/7a0858b5fadb68adbd75 (Haven't tested it in a not enabled state)

New armbian version was released yesterday which includes all needed kernel changes (v5.0.0). So getting up and running is only a matter installing the hypriot schatzkiste.


Specify Artifact Trigger behavior and format for filter if artifact is ACR image

Ok, it's clear how to filter branches as a pre-deployment trigger if our artifacts if a git repo.
But it's unclear how to filter if my artifact is docker image from ACR.
Please, specify more samples.
I'm asking, because I can't save neither "dev-[0-9]" not just "latest". It's either a bug, or misconfiguration

Doesn't matter what I included as a filter, Azure DevOps will not save it.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: d9e313c5-9120-9172-bc27-c21d10fcd5ae
Version Independent ID: 1a837182-591f-3cbc-1632-7b50d857b13c
Content: Release triggers for stages, branches, and pipelines - Azure Pipelines
Content Source: docs/pipelines/release/triggers.md
Product: devops
Technology: devops-cicd
GitHub Login: @RoopeshNair
Microsoft Alias: ronai

@azooinmyluggage  - can  you please take a look?

@azooinmyluggage will be nice to have any answers. @azooinmyluggage

any updates?

@cxwtool @shashankbarsin @azooinmyluggage could you fix this issue, not just close! 180 days without update from Microsoft side, not from my.


Having trouble upgrading to wasmd v0.26

Hi there!
I'm trying to build wasmd v0.26.0 and having trouble doing so.
My ultimate goal is to upgrade osmosis to wasmd v0.26.0. I have some work done in this PR . However, it is failing to build with the following error:
https://github.com/osmosis-labs/osmosis/runs/6459547928?check_suite_focus=true
I made sure to match the wasmvm and wasmd versions according to: https://github.com/osmosis-labs/wasmd#compatibility.
Also, I tried building both locally and in Docker without success.
To further test, I attempted  to git checkout the v0.26.0 wasmd tag and build it locally without Osmosis involved:
LEDGER_ENABLED=false BUILD_TAGS=muslc LINK_STATICALLY=true make build

This is from wasmd Dockerfile: https://github.com/CosmWasm/wasmd/blob/dc5ef6fe84f0a5e3b0894692a18cc48fb5b00adf/Dockerfile#L28

However, I would get the same error as before:
$ LEDGER_ENABLED=false BUILD_TAGS=muslc LINK_STATICALLY=true make build
go build -mod=readonly -tags "netgo,muslc" -ldflags '-X github.com/cosmos/cosmos-sdk/version.Name=wasm -X github.com/cosmos/cosmos-sdk/version.AppName=wasmd -X github.com/cosmos/cosmos-sdk/version.Version=0.26.0 -X github.com/cosmos/cosmos-sdk/version.Commit=dc5ef6fe84f0a5e3b0894692a18cc48fb5b00adf -X github.com/CosmWasm/wasmd/app.Bech32Prefix=wasm -X "github.com/cosmos/cosmos-sdk/version.BuildTags=netgo,muslc" -linkmode=external -extldflags "-Wl,-z,muldefs -static"' -trimpath -o build/wasmd ./cmd/wasmd
# github.com/CosmWasm/wasmvm/api
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libwasmvm_muslc.a(num_cpus-c4ff72c03458de44.num_cpus.a9a66fc0-cgu.1.rcgu.o): in function `num_cpus::linux::init_cgroups':
num_cpus.a9a66fc0-cgu.1:(.text._ZN8num_cpus5linux12init_cgroups17h501ed59e51417282E+0x900): undefined reference to `ceil'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libwasmvm_muslc.a(wasmer_vm-89f7c555213e842a.wasmer_vm.7c8f493e-cgu.11.rcgu.o): in function `wasmer_vm_f32_ceil':
wasmer_vm.7c8f493e-cgu.11:(.text.wasmer_vm_f32_ceil+0x2): undefined reference to `ceilf'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libwasmvm_muslc.a(wasmer_vm-89f7c555213e842a.wasmer_vm.7c8f493e-cgu.11.rcgu.o): in function `wasmer_vm_f32_floor':
wasmer_vm.7c8f493e-cgu.11:(.text.wasmer_vm_f32_floor+0x2): undefined reference to `floorf'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libwasmvm_muslc.a(wasmer_vm-89f7c555213e842a.wasmer_vm.7c8f493e-cgu.11.rcgu.o): in function `wasmer_vm_f32_trunc':
wasmer_vm.7c8f493e-cgu.11:(.text.wasmer_vm_f32_trunc+0x2): undefined reference to `truncf'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libwasmvm_muslc.a(wasmer_vm-89f7c555213e842a.wasmer_vm.7c8f493e-cgu.11.rcgu.o): in function `wasmer_vm_f32_nearest':
wasmer_vm.7c8f493e-cgu.11:(.text.wasmer_vm_f32_nearest+0x22): undefined reference to `ceilf'
/usr/bin/ld: wasmer_vm.7c8f493e-cgu.11:(.text.wasmer_vm_f32_nearest+0x31): undefined reference to `floorf'
/usr/bin/ld: wasmer_vm.7c8f493e-cgu.11:(.text.wasmer_vm_f32_nearest+0x87): undefined reference to `floorf'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libwasmvm_muslc.a(wasmer_vm-89f7c555213e842a.wasmer_vm.7c8f493e-cgu.11.rcgu.o): in function `wasmer_vm_f64_ceil':
wasmer_vm.7c8f493e-cgu.11:(.text.wasmer_vm_f64_ceil+0x2): undefined reference to `ceil'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libwasmvm_muslc.a(wasmer_vm-89f7c555213e842a.wasmer_vm.7c8f493e-cgu.11.rcgu.o): in function `wasmer_vm_f64_floor':
wasmer_vm.7c8f493e-cgu.11:(.text.wasmer_vm_f64_floor+0x2): undefined reference to `floor'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libwasmvm_muslc.a(wasmer_vm-89f7c555213e842a.wasmer_vm.7c8f493e-cgu.11.rcgu.o): in function `wasmer_vm_f64_trunc':
wasmer_vm.7c8f493e-cgu.11:(.text.wasmer_vm_f64_trunc+0x2): undefined reference to `trunc'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libwasmvm_muslc.a(wasmer_vm-89f7c555213e842a.wasmer_vm.7c8f493e-cgu.11.rcgu.o): in function `wasmer_vm_f64_nearest':
wasmer_vm.7c8f493e-cgu.11:(.text.wasmer_vm_f64_nearest+0x28): undefined reference to `ceil'
/usr/bin/ld: wasmer_vm.7c8f493e-cgu.11:(.text.wasmer_vm_f64_nearest+0x39): undefined reference to `floor'
/usr/bin/ld: wasmer_vm.7c8f493e-cgu.11:(.text.wasmer_vm_f64_nearest+0x9d): undefined reference to `floor'
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/11/../../../../lib/libwasmvm_muslc.a(handlers.o): in function `wasmer_register_setjmp':
handlers.c:(.text.wasmer_register_setjmp+0x32): undefined reference to `sigsetjmp'
collect2: error: ld returned 1 exit status
make: *** [Makefile:85: build] Error 2

Lastly, I tried building the image for the following Dockerfile: https://github.com/CosmWasm/wasmd/blob/dc5ef6fe84f0a5e3b0894692a18cc48fb5b00adf/Dockerfile and it worked.
As a result, it tells me that either the OS or some of the installed dependencies prevent me from building locally or in the Osmosis container. However, I do not see what exactly yet.
Is there anything obvious I am missing?
Any help would be greatly appreciated.
Roman

I'm trying to upgrade to v0.27.0.rc3 now instead. Will update here if I run into the same issue

The problem was the base image. We were using golang:1.18-bullseye.
Switched to using: 1.18.2-alpine3.15. The same one as in https://github.com/CosmWasm/wasmd/blob/dc5ef6fe84f0a5e3b0894692a18cc48fb5b00adf/Dockerfile . It ended up working

Thanks for letting us know how you fixed it. 👍
For support our discord is open as well


shortened the function in index.php

tiny refactoring of index.php

Will create another PR based on recipe


Support Y.js messages > 1MB

Problem
The Workers platform rejects WebSocket messages when they are above 1MB.
The Y.js provider does not like this, and end up in a nasty reconnect/retry loop, which will spam the room with very large messages.
Solution
Chunk large Y.js update messages to 1MB chunks and reassemble them on the server side.
This implementation is not 100% resilient to network issues such as dropped messages, but I've tried to validate the inputs as well as I can and not pass malformed messages to the handler on the server. In this case, the worst case behaviour is the same as it was before applying this fix in the first place.
Considerations
Generally, limiting WebSocket message sizes is a good idea, but with Y.js it's reasonable for the document size to grow to exceed 1MB.  Sending the large message should only happen on initial sync, when the server doesn't have a state vector for the document.

an alternative solution would be to send messages over 1mb over http.


Feature: Bumps v20200325

Fixes some vulnerabilities ... but I don't see how we test it. Any hints?

If we bump it in dreams-triggers on staging, it will get tested in the general system


ci: Bump mobile build images

This makes the build images used in mobile ci consistent with those in Envoy
it will also allow updating the github checkout action (cf #24123) which breaks due to the git version in the currently used images
NB: this changes the ubuntu version of the container 18 -> 20
Signed-off-by: Ryan Northey<EMAIL_ADDRESS>
Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/retest

Code coverage 96.0 is lower than limit of 96.1

https://dev.azure.com/cncf/envoy/_build/results?buildId=122305&view=logs&jobId=5035ce29-be3c-5fcf-dc50-abb6a265f8b1&j=5035ce29-be3c-5fcf-dc50-abb6a265f8b1&t=548c3e59-0417-5971-4f1b-f8545005c291

sure - i think that is a flake - ive raised a PR here to address https://github.com/envoyproxy/envoy/pull/24320

arggh seems like more than a flake - its happening every time here - wierd - pretty sure this doesnt affect coverage

There could've been a merge race that cumulatively caused the threshold to be hit.

/retest


Revert "Switching from xUnit to NUnit"

Reverts b3b00/csly#22
appVeyor CI has no direct support for NUnit unit tests (it does not display the tests results in the tests tab as it does with xunit.  The only reason to switch to NUnit is to have a Mac V2017 support which far less important than a correctly working CI.

finally reverted . appveyor does not display natively nunit test reports.


Analyzer: Offer a TypeSystem.mostUpperBound

Hello!
Currently, package:analyzer#TypeSystem has a leastUpperBound method. This returns the shared type between two types.
For example, when passing leastUpperBound("int?", "double?"), we'd get "num?" as result.
This is useful for merging the getters of two interfaces:
sealed class Base {
  num? get value;
}

abstract class A implements Base {
  int? get value;
}

abstract  class B implements Base  {
   double? get value;
}

But what about for "setters"? More particularly copyWith.
Would it be possible to have a type utility that returns a DartType that would be compatible as copyWith for all input types?
For example, given  maxUpperBound(int?, double?), the result would be Null. As that's the only type assignable to both int? and double?:
sealed class Base {
  Base copyWith({Null value});
}

abstract class A implements Base {
  A copyWith({int? value});
}

abstract  class B implements Base  {
   B copyWith({double? value});
}

In the case that no compatible type is available, the utility could return InvalidType.
Similarly, given maxUpperBound(num, int?), the result would be int (excluding Null), such that we have:
sealed class Base {
  Base copyWith({int value});
}

abstract class A implements Base {
  A copyWith({num value});
}

abstract  class B implements Base  {
   B copyWith({int? value});
}

If you cast your TypeSystem to dynamic, you might even be able to call getGreatestLowerBound

😆

You sound like you're asking for the "greatest lower bound" instead of the "least upper bound".

Indeed. I wasn't quite sure how to name this
Glad to hear there's already something for this, just not public! Sounds like adding those officially would require much less work than I originally thought.

If you just want the minimum of two related types, it'll work, and it will probably work fine with nullability too, but it won't come up with a shared subclass of two unrelated classes.

That's fine by me. I don't care about subclasses of those two types. That would be unpredictable
I would prefer for it to support functions and generics if possible though. Those are the main reasons why I'm not trying to implement one myself. It gets quite complex when taking into account function parameters and generic constraints.

CC @scheglov @bwilkerson

If the API is already implemented internally but not public, would you be willing to have a PR make it public?

https://dart-review.googlesource.com/c/sdk/+/318000


Questions about your results?

The results of PD-MeshNet in your paper are very different from the results in the original paper. I also notice your answer to question 15. But the metric of PD-MeshNet is on the primal nodes (on faces), which means that the metric is strict. Therefore, I'm curious about the reason. Thanks! Have a nice day!

Hi, @lidan233
Many have questions on the inconsistent performance results of MeshCNN / PD-MeshNet. The brief answer is that MeshCNN / PD-MeshNet / SubdivNet is evaluated with different metrics. In our paper, we use a unified metric, i.e., per-face accuracy on the raw meshes.
More detailed discussion is described in the first paragraph of the segmentation experiment  in our paper. Feel free to ask if you have more questions.

Give me one day! Thanks!

I read your paper carefully. Due to my poor foundation, I have the following problems or misunderstandings.
Your method may have the same metric as PD-MeshNet in segmentation?
In your code:
`
def train(net, optim, dataset, writer, epoch):
net.train()
acc = 0
for meshes, labels, _ in tqdm(dataset, desc=str(epoch)):
mesh_tensor = to_mesh_tensor(meshes)
mesh_labels = jt.int32(labels)
outputs = net(mesh_tensor)
loss = nn.cross_entropy_loss(outputs.unsqueeze(dim=-1), mesh_labels.unsqueeze(dim=-1), ignore_index=-1)
optim.step(loss)
    preds = np.argmax(outputs.data, axis=1)
    acc += np.sum((labels == preds).sum(axis=1) / meshes['Fs'])
    writer.add_scalar('loss', loss.data[0], global_step=train.step)
    train.step += 1
acc /= dataset.total_len
print('train acc = ', acc)
writer.add_scalar('train-acc', acc, global_step=epoch)

In PD-MeshNet:
# targets are the labels of each face
targets = primal_graph_batch.y
# Compute number of correct predictions.
num_correct_predictions = compute_num_correct_predictions(
task_type=self.__task_type,
outputs=outputs,
targets=targets)
# The number of predictions corresponds to the number of samples
# in the batch in case of mesh classification (in which a single
# label is assigned to each shape) and to the number of total
# mesh faces in the batch in case of mesh segmentation (in which
# a label is assigned to each face).
num_predictions_in_batch = targets.shape[0]
total_num_correct_predictions += num_correct_predictions
total_num_predictions += num_predictions_in_batch
`
Therefore, both your accuracy and PD-MeshNet accuracy are based on each face's label. What are the differences between your method's metric and the PD-MeshNet's metric?

You are right that both subdivnet and pdmeshnet uses per-face accuracy. However, PDMesh is originally evaluated on the simplified mesh, which contains 1000+ faces. FYI, the original meshes in humanseg and coseg contains up to more than 10,000 faces.

You are right that both subdivnet and pdmeshnet uses per-face accuracy. However, PDMesh is originally evaluated on the simplified mesh, which contains 1000+ faces. FYI, the original meshes in humanseg and coseg contains up to more than 10,000 faces.

I agree with you. I also notice the attention mechanism in PD-MeshNet is based on the local information. They use the local attention value as the metric to remove edges. Therefore, their method may be not fit for large meshes. Do you agree with this reason? In addition, I can only get the coseg data containing 1000+ faces. How do you get the meshes with high resolution? Which subdivision method do you choose?

PD-MeshNet was trained on the simplified meshes and I projected their segmentation results to the raw meshes. Because I found their code is not easy to be modified for the original humanseg and coseg datasets. So I cannot simply conclude that PD-MeshNet is not suitable for large meshes.
But I have tested MeshCNN to segment 10000-face meshes and MeshCNN works worse than on the simplified meshes. In my opinion, the subdivision-based pooling layer and the dilated convolution are the most important for large meshes, because both of them provides reasonable and larger receptive fields. This seems to be a more effective strategy than removing edges according to the intermediate feature, like MeshCNN and PD-MeshNet.
The original coseg dataset can be downloaded via http://irc.cs.sdu.edu.cn/~yunhai/public_html/ssl/ssd.htm.
The Loop subdivision scheme, or 1-to-4 triangle splitting, is used all-over the paper while other subdivision scheme may also be compatible.


Update com.github.jnr:jnr-posix to 3.1.18 to avoid M1 docker crash

Zipkin found the following crash when running a docker container that uses this driver on Apple Silicon. Note: the problem doesn't happen when run via java directly on the host. Updating jnr-posix is all that was needed to remedy the situation.
# below crash happens after hitting the /health endpoint on zipkin and it doesn't matter if the cassandra host is present or not.
~ $  STORAGE_TYPE=cassandra3 start-zipkin

                  oo
                 oooo
                oooooo
               oooooooo
              oooooooooo
             oooooooooooo
           ooooooo  ooooooo
          oooooo     ooooooo
         oooooo       ooooooo
        oooooo   o  o   oooooo
       oooooo   oo  oo   oooooo
     ooooooo  oooo  oooo  ooooooo
    oooooo   ooooo  ooooo  ooooooo
   oooooo   oooooo  oooooo  ooooooo
  oooooooo      oo  oo      oooooooo
  ooooooooooooo oo  oo ooooooooooooo
      oooooooooooo  oooooooooooo
          oooooooo  oooooooo
              oooo  oooo

     ________ ____  _  _____ _   _
    |__  /_ _|  _ \| |/ /_ _| \ | |
      / / | || |_) | ' / | ||  \| |
     / /_ | ||  __/| . \ | || |\  |
    |____|___|_|   |_|\_\___|_| \_|

:: version 2.25.1 :: commit 82c3d7a ::

2023-12-15 05:45:58.195  INFO [/] 8 --- [oss-http-*:9411] c.l.a.s.Server                           : Serving HTTP at /<IP_ADDRESS>:9411 - http://<IP_ADDRESS>:9411/
2023-12-15 05:46:06.887  INFO [/] 8 --- [cking-tasks-2-1] c.d.o.d.i.c.c.CqlPrepareAsyncProcessor   : Adding handler to invalidate cached prepared statements on type changes
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000005e30, pid=8, tid=59
#
# JRE version: OpenJDK Runtime Environment (21.0.1+12) (build 21.0.1+12-alpine-r1)
# Java VM: OpenJDK 64-Bit Server VM (21.0.1+12-alpine-r1, mixed mode, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
# Problematic frame:
# C  [jffi11042031320136118671.so+0x7f7c]  jffi_throwExceptionByName+0xfc
--snip--

@michaelsembwever any chance we can get this in?


Tracking issue: Delendum benchmarks project

Goal(s)

Benchmark Miden VM against the defined scenarios in https://github.com/delendum-xyz/zk-benchmarking
Add necessary features and change code to be able to benchmark

Details
For this target, we want to benchmark the Miden VM against other proving systems, e.g. Risk0. Therefore, we have predefined scenarios. Our goal is to create a neutral and objective playground to benchmark several proving systems also to invite other systems like Cairo VM in the future.
Must have

[x] #9
[x] #12
[x] #13
[x] #14
[x] #30
[x] #31

Nice to have

[ ] #15

Working group:
@Dominik1999 @itzmeanjan

Workflow

Discussion should happen here or in the related sub-issues.
PRs should only be merged by the coordinator, to ensure everyone is able to review.
Aim to complete reviews within 24 hours.
When a related sub-issue is opened:

add it to the list of sub-issues in this tracking issue

When opening a related PR:

request review from everyone in this working group

When a sub-issue is completed:

close the related issue with a comment that links to the PR where the work was completed

Coordinator: @Dominik1999

Workflow
The working group coordinator ensures scope & progress tracking are transparent and accurate. They will:

Merge approved PRs after all working group members have completed their reviews.

add the PR # to the relevant section of the current tracking PR.
close any completed sub-issue(s) with a comment that links to the PR where the work was completed

Monitor workflow items and complete anything that slips through the cracks.
Monitor scope to see if anything is untracked or unclear. Create missing sub-issues or initiate discussion as required.
Monitor progress to see if there's anything which isn't moving forward. Initiate discussion as required.
Identify PRs with especially significant changes and add @grjte and @bobbinth for review.

I would also add benchmarks for hash chain and Merkle path verification using Rescue Prime.

I would say hash chain using BLAKE3, SHA256, and Rescue Prime is a "must have" and things beyond that (e.g., Merkle Path verification) are "nice to have" for now.

So for the Delendum Project, we now have decided to start with a scenario of a hash chain using the natural hash functions. In our case that would be Rescue Prime.

I would still benchmark all 3 functions listed above, I think it would be much more informative than benchmarking native functions.

I would still benchmark all 3 functions listed above, I think it would be much more informative than benchmarking native functions.

Agreed, benchmarking only Rescue Prime won't give us full picture of the stage. I think we should keep

Blake3
SHA256
Rescue Prime
Keccak256

In above list, except using Keccak256, we've ability to hash both 32/ 64 -bytes input.

Got it, in the Delendum project we can now benchmark Rescue Prime, Sha256, Blake3.
I am unsure in which cases a developer would not use the "natural" hash function. I think, in the case for the final proof that is being put the Ethereum it is necessary to use Keccak. But besides that, are there significant security differences?

Developers will likely use native hash function as frequently as possible. The main purpose for benchmarking other hash functions is to shows how the VM can handle complex computations which it wasn't optimized for. Basically, we use non-native hash functions as a sort of a proxy for other complex computations.

got it

We decided to pause the second scenario for now. RISC Zero is not having it yet and we can pick it up later.


Update sites.js

After losing the webring icon with the latest iteration of my site, re-added it to the contact/about page (http://electricgecko.de/kontakt), among other active accounts.

Thanks :)


Prometheus Exporter App Written in Go.

Goal: app written in Golang that connects to provider’s inventory GRPC endpoint and exports it as prometheus metrics.
protobuf description for GRPC is here: https://github.com/akash-network/akash-api/blob/d05c262a17178a33e3e5383dcceea384d6260a17/proto/provider/akash/inventory/v1/service.proto#L31

PoC of the "Inventory Exporter" updating gauge values every t, where t is an arbitrary time value:

This specific test was ran against the Europlots provider which I validated in the Quasarch's provider page as being consistent:

Reminder the metrics values are in Bytes and in the screenshot in Gibibytes (1024^3)

Repository available under inventory-exporter.


Dismissable widget inside PageView listens to all swiping-directions even when only assigned one

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce

Have a PageView widget with 2 children.
in child2 have a Dismissable with direction set to EndToStart (opposite swiping direction of going back to child1)
The Dismissable blocks the LTR-gesture even though it is only reacting to RTL.

Expected results
If the Dismissable is only listening to one swiping direction, the other directions should be up for graps by other widgets.
Would be nice if this mirrored the functionality when you set the direction to 'none' wherein all triggers are disabled. I am just requestion partial detection when I set a specific direction.
Actual results
Regardless of what swiping direction you assign to the Dismissable, it will listen to all of them.
Code sample
Code sample
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Bug',
      theme: ThemeData(
        colorScheme: ColorScheme.fromSeed(seedColor: Colors.deepPurple),
        useMaterial3: true,
      ),
      home: const MyHomePage(),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key});

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
        body: PageView(
      children: const [
        PageLeft(),
        PageRight(),
      ],
    ));
  }
}

class PageLeft extends StatelessWidget {
  const PageLeft({super.key});

  @override
  Widget build(BuildContext context) {
    return const Center(
      child: Text("Page LEFT"),
    );
  }
}

class PageRight extends StatelessWidget {
  const PageRight({super.key});

  @override
  Widget build(BuildContext context) {
    return Center(
      child: Column(
        mainAxisSize: MainAxisSize.max,
        mainAxisAlignment: MainAxisAlignment.center,
        children: [
          const Text("Page RIGHT"),
          Dismissible(
              key: UniqueKey(),
              direction: DismissDirection.endToStart,
              child: const Row(
                mainAxisSize: MainAxisSize.max,
                children: [
                  Padding(
                    padding: EdgeInsets.all(16.0),
                    child: Text(
                        "You can swipe left on me, but swiping right\n does not trigger page view :("),
                  )
                ],
              ))
        ],
      ),
    );
  }
}

Flutter Doctor output
Doctor output
[!] Flutter (Channel stable, 3.10.1, on macOS 13.4 22F66 darwin-arm64 (Rosetta), locale en-DK)
    • Flutter version 3.10.1 on channel stable at /Users/mikkelthygesen/Downloads/flutter
    ! Warning: `dart` on your path resolves to /opt/homebrew/Cellar/dart/2.19.2/libexec/bin/dart, which is not inside your current Flutter SDK
      checkout at /Users/mikkelthygesen/Downloads/flutter. Consider adding /Users/mikkelthygesen/Downloads/flutter/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision d3d8effc68 (12 days ago), 2023-05-16 17:59:05 -0700
    • Engine revision b4fb11214d
    • Dart version 3.0.1
    • DevTools version 2.23.1
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks
      and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
    • Android SDK at /Users/mikkelthygesen/Library/Android/sdk
    • Platform android-33, build-tools 33.0.1
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] IntelliJ IDEA Ultimate Edition (version 2023.1.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] IntelliJ IDEA Community Edition (version 2022.2.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart

[✓] VS Code (version 1.78.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.64.0

Hi @Mikkelet, thanks for filing the issue.
I see there's an open issue addressing the case you described https://github.com/flutter/flutter/issues/31476.
Closing this issue as a duplicate, so please follow up on it for further updates. You can leave there your comment and react an upvote to the original comment will help to raise the issue. Thank you!


Gizmo in CSGMesh3D is not updated when scaling the node in the 3D editor viewport

Tested versions
4.3 stable, 4.4 dev2
System information
Godot v4.4.dev2 - Windows 10.0.19045 - Vulkan (Forward+) - dedicated Radeon RX 560 Series (Advanced Micro Devices, Inc.; 31.0.14001.45012) - Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (4 Threads)
Issue description
I noticed two problems when using CSGMesh3D

AABB does not update (blue border) when resizing with the scale tool in the top bar

When selecting CSGMesh3D, the Gizmo struggles for depth, this is especially noticeable when moving the camera

Steps to reproduce

Open MRP
Select the biggest cube (BIGBOX)
Move the camera, you will notice artifacts on the cube (fight for depth)
Reduce the cube, AABB will not update until we select another node

Minimal reproduction project (MRP)
vox.zip

When selecting CSGMesh3D, the Gizmo struggles for depth, this is especially noticeable when moving the camera

This should be fixed by https://github.com/godotengine/godot/pull/100211.

When selecting CSGMesh3D, the Gizmo struggles for depth, this is especially noticeable when moving the camera

This should be fixed by #100211.

This does not fix the Gizmo update, but fixes the second issue


[BUG]:Uncaught (in promise) bad-precaching-response in production

Description of the bug
I am following this tutorial https://next-pwa.imam.dev/usage,
all works fine until I send it to production, then I get this error, any suggestion on how to fix it?

Environment
N/A
Steps To Reproduce
N/A
Additional Information
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

exclude it with buildExcludes: [/.*manifest.json$/]

I managed to fix the error with this:  buildExcludes: ["app-build-manifest.json"]


Invalid validation for PL postal code

In reference to official documents (https://www.poczta-polska.pl/hermes/uploads/2013/11/spispna.pdf, https://bip.poczta-polska.pl/bez-kategorii/system-pocztowych-numerow-adresowych-pna/), and other sources (https://en.wikipedia.org/wiki/Postal_codes_in_Poland, https://en.wikipedia.org/wiki/List_of_postal_codes), postal code format for Poland is NN-NNN, then - is not redundant and should not be removed.
Now is:
{
  "Description": "PL : 99-999",
  "RedundantCharacters": " -",
  "ValidationRegex": "^[0-9]{5}$",
  "TestData": {
    "Valid": [
      "44100",
      "44-100"
    ],
    "Invalid": [
      "44f00",
      "e4410",
      "44-100d",
      "c44-100",
      "b44100",
      "44100a"
    ]
  }
}

should be:
{
  "Description": "PL : 99-999",
  "RedundantCharacters": " ",
  "ValidationRegex": "^[0-9]{2}-[0-9]{3}$",
  "TestData": {
    "Valid": [
      "44-100"
    ],
    "Invalid": [
      "44100",
      "44f00",
      "e4410",
      "44-100d",
      "c44-100",
      "b44100",
      "44100a"
    ]
  }
}

Thanks for raising the issue. The PR below should have resolved it.
https://github.com/Cimpress-MCP/postal-codes-js/pull/51


[Editor] Add a menu option to create camera3d from current 3d editor view.

Implements the proposal: https://github.com/godotengine/godot-proposals/issues/1798 , https://github.com/godotengine/godot-proposals/issues/11133
This PR adds a option menu and a shortcut to create Camera3D node from the current 3d editor view.
Menu option button:

By using shortcuts:  CMD OR CTRL + ALT + C
Demonstration video:
https://github.com/user-attachments/assets/d0a61e08-f414-4f83-abaf-ebd9febd6b96
Note

The created camera takes and applies the properties from the current 3d editor view camera property such as VFOV, Z-Near, and Z-far.
If there is no nodes selected in the scene then the base node would be the parent of the created camera from view.
Only one selected node is allowed as a parent when creating the camera from the current view. If multiples nodes are selected then it won't create the camera from the current view.
When in Orthogonal perspective view, it creates a Orthogonal Camera3d node.

Purpose of this PR.
With this anyone would be able to create Camera3d for the current 3d editor view quickly. So, that they can see which view (composition) would be best and can be used for taking screenshots and such.
This feature is present in various game engines such as CryEngine, Unreal Engine, etc.
In CryEngine 5:

In Unreal Engine 4 or 5:

fixed formatting issue and it should pass the tests I guess.

I tried this PR, seems to work as advertised.
Two comments though:

Why do you cast the selection to Node and check for nullptr in line 5428 Node *sp = Object::cast_to<Node>(selection.front()->get());? The object you get is already a Node and there should not be null objects in the selection. I removed the cast in my copy of this PR,  checked the behavior and didn't notice anything weird with trying to make cameras, was there something you found?
PRs should be single commits to keep history clean but you have 3 commits in yours. I think it should be simple to fix with an interactive git rebase and mark all later commits to be squished. Check the docs for how to do that: https://docs.godotengine.org/en/latest/contributing/workflow/pr_workflow.html#the-interactive-rebase

It does work, although if selecting multiple nodes, I would recommend greying out the selection in the perspective menu or at least maybe a toast notification as feedback for nothing happening. Using the first selection as the parent is also an option.
As a side note, adding another item in the menu is desperately asking for an implementation for this proposal: godotengine/godot-proposals#11256

I made that proposal, but its reception is somewhat mixed. I think there's no reason for any new feature to wait or worry about it.


feat: add new secret_environment_variables variable

As per the title.
THIS IS DRAFT, REVIEW BUT DO NOT MERGE!

@bartekrutkowski-ext looks like tests discovered a bug...
source_archive is a required argument and can't be null by default.. would that make sense?

@bartekrutkowski-ext looks like tests discovered a bug...
source_archive is a required argument and can't be null by default.. would that make sense?

Yes I've seen it, who could've thought tests are useful ;) I'm thinking on how to solve that, but I want to fix the tests first.


authentication: add service account and webhook docs and update formatting

It was brought up in #sig-auth today that the service account authenticator isn't mentioned in the authentication docs, and that this document is generally pretty outdated. Took the opportunity to fix up the following:

Added top level section about what authenticators do.
Added section about service account tokens.
Added section describing webhook authenticator.
Updated OpenID Connect section.
Provided more recent link to Keystone authenticator work.
Generally updated formatting to bring more in line with the authorizer document.
Removed @yifan-gu from assignees as I'm taking over the OpenID Connector authenticator from him.

cc @kubernetes/sig-auth @lavalamp @erictune
edit:
This possibly addresses #598 @nVitius

@deads2k

@lavalamp should @deads2k be the reviewer?

YEs.
On Wed, Aug 3, 2016 at 4:09 PM, Phillip Wittrock<EMAIL_ADDRESS>wrote:

@lavalamp https://github.com/lavalamp should @deads2k
https://github.com/deads2k be the reviewer?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/kubernetes.github.io/pull/959#issuecomment-237402992,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAnglo4q6EcCjTu_TAeNjPvVilb2xnrJks5qcR-qgaJpZM4JcJqw
.

@ericchiang Please also add @deads2k as an assignee

Nice improvements, Eric, thanks!

@ericchiang friendly bump.

Fixed typos and resolved some smaller issues pointed out by @erictune and @deads2k.
Added a section at the top titled "Users in Kubernetes" to emphasize how Kubernetes thinks of users and the difference between service accounts and normal users.
Expanded the service accounts section to note that they're automatically created and associated with pods by the ServiceAccount Admission Controller.

Oh couple questions. How do we spell:

service account vs Service Account
API server, API Server, apiserver?

Oh couple questions. How do we spell:

I do "service account" and "API server", but I suspect that an editor will sweep eventually.
Changes lgtm.

I do "service account" and "API server", but I suspect that an editor will sweep eventually.

Okay, I've standardized on those for now and will defer to a future editor.

lgtm, manually merging per: https://github.com/kubernetes/kubernetes.github.io/pull/946#issuecomment-238952955


[Packager]bugfix: require in comment still effect sometimes on Windows.

blockCommentRe and lineCommentRe should support lines ending with '\r\n'.

this pr is outdated


$app_version_string and $app_build_number properties are being set as the version of the SDK rather than the version of the app itself (iOS only)

Using version 1.4.2 of mixpanel-flutter.
Our current app version is set to 1.2.0 however we're seeing the App Version in Mixpanel set as 3.0.0. It seems this may be mapped to the version of the underlying Swift SDK rather than the version of the app itself.
The same inconsistency is happening for the App Build Number.
This is only happening on iOS and not Android.

Obs: If it helps, a very similar issue was found and fixed on the mixpanel-reactive-native lib (issue)

hi @arctouch-danielishara , we have fixed this issue in v1.4.3.  sorry for the inconvenience. Please feel free to reopen if the problem still exists.


Upgrade Spring Cloud Horsham SR3 to Horsham SR5, configure the routingKeyExpression parameter, and an exception occurs when the project starts

configuration:
spring:
  application:
    name: spring-cloud-rabbit-service-1
  cloud:
    stream:
      binders:
        local_rabbit:
          type: rabbit
          environment:
            spring:
              rabbitmq:
                host: <IP_ADDRESS>
                port: 5672
                username: guest
                password: guest
                virtual-host: /
      bindings:
        myOutput:
          destination: my-messages
          binder: local_rabbit
      rabbit:
          bindings:
            myOutput:
              producer:
                exchangeType: direct
                routingKeyExpression:  headers.key
                queueNameGroupOnly: true

start exception  as follows:
Failed to bind properties under 'spring.cloud.stream.rabbit.bindings.myoutput.producer.routing-key-expression' to org.springframework.expression.Expression:

    Property: spring.cloud.stream.rabbit.bindings.myoutput.producer.routingkeyexpression
    Value: headers.key
    Origin: class path resource [application.yml]:64:37
    Reason: No converter found capable of converting from type [java.lang.String] to type [org.springframework.expression.Expression]

is bug

@tangdelong Could you share you solution?

What solution? It was a big and it is fixed

Horsham.SR6 has been released as well

@olegz Thanks, after upgrade cloud to Horsham.SR6, this issue is fixed.


[Feature Request] - Add media.error on any media processing errors

Part https://github.com/devlikeapro/waha/issues/509
Add error that describing what happened there in message.media object (so it'll help us in the future)

Added media.error to clearly see what happened without checking the logs
    "media": {
      "url": null,
      "filename": null,
      "mimetype": "image/jpeg",
      "error": {
        "errno": -111,
        "code": "ECONNREFUSED",
        "syscall": "connect",
        "address": "<IP_ADDRESS>",
        "port": 9000,
        "$metadata": {
          "attempts": 3,
          "totalRetryDelay": 206
        },
        "details": "Error: connect ECONNREFUSED <IP_ADDRESS>:9000\n    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1595:16)\n    at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)"
      }

in 2024.9.1


DllNotFoundException

Hey, couldn't run the app. Here is the error from Event Viewer:
Application: Idasen.SystemTray.Win11(2).exe CoreCLR Version: 6.0.522.21309 .NET Version: 6.0.5 Description: The process was terminated due to an unhandled exception. Exception Info: System.DllNotFoundException: Dll was not found.    at MS.Internal.WindowsBase.NativeMethodsSetLastError.SetWindowLongPtrWndProc(HandleRef hWnd, Int32 nIndex, WndProc dwNewLong)    at MS.Win32.UnsafeNativeMethods.CriticalSetWindowLong(HandleRef hWnd, Int32 nIndex, WndProc dwNewLong)    at MS.Win32.HwndSubclass.HookWindowProc(IntPtr hwnd, WndProc newWndProc, IntPtr oldWndProc)    at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
Desk is paired and called "Desk 023". The app just doesn't run.
Windows 11 Pro. Version: 21H2
Build: 22000.856
idasen-desk version: V0.0.160

V0.0.111 works for me by the way

Hi,
I can confirm that I get the same issue on Windows 11 (Version 10.0.22000 Build 22000). I'll try to fix it.
Q: Which Windows version do you use 10 or 11?
Regards,
Thomas

Windows 11 Pro. Version: 21H2
Build: 22000.856

Thanks, I found the issue and fixed it for Windows 10 and 11.
Can you try V<IP_ADDRESS>?
(https://github.com/tschroedter/idasen-desk/releases/download/V0.0.171/Idasen.SystemTray.Win11.exe)

Fixed in V0.0.171


TABLE component responsiveDynamicHeight does not work

Hi,
starting using the TABLE component and when I set to true the responsiveDynamicHeight this property does not work or I don't understand how to use it.
What I need is not to fix the height, the height have to resize their self.
Thanks.
Juan Ramírez

Hi Juan,
the responsiveDynamicHeight is applicable only if the table is used in responsiveForms. Still the responsiveHeight property will be used as maxHeight;
it basically allow the table to use only the height necessary up to max responsiveHeight (then will show scrollbar);
For example if you have a responsiveHeight of 500px but your table shows only 2 records, when responsiveDynamicHeight is true the table will take only few pixels in height (the header + the 2 rows). The table will grow up to the max 500px, then if more rows are added it will show a scrollbar.
Regards,
Paolo


SOS constraints in or-tools?

Is it possible to specify SOS constraints in the linear programming module? Many MILP solvers are compatible with such specification.

seems related to  #1084 #1085

Actually CBC solver is also compatible with SOS. :)

FYI, since version 2.10.0, CBC includes new handling of SOS constraints. It would be nice if SOS constraints in or-tools also worked for CBC.
Release 2.10.0
Improved handling of SOS, starting point, and symmetries.
https://github.com/coin-or/Cbc

I just pushed limited support for SOS:
You need to use the protobuf API
It is currently only supported for SCIP and Gurobi.

Can you please point out how to indicate ortools that a constraint is of the SOS type?

Look at linear_solver.proto on master
Le jeu. 18 juil. 2019 à 19:25, Roger Lloret-Batlle<EMAIL_ADDRESS>a écrit :

Can you please point out how to indicate ortools that a constraint is of
the SOS type?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/or-tools/issues/1113?email_source=notifications&email_token=ACUPL3LQIDZJWOO66PTWDQLQAEQYHA5CNFSM4G4SAFI2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2KL7PI#issuecomment-513064893,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACUPL3NZVTKD7VLBB3MWMFTQAEQYHANCNFSM4G4SAFIQ
.

You need to use the linear solver protobuf interface
http://google.github.io/or-tools/python/ortools/linear_solver/pywraplp.html#pywraplp.Solver.SolveWithProto
It takes a response proto as input (not used), and will return the computed solution proto.
Please note that currently, this is only supported for SCIP and Gurobi.