Files hierarchy is not correct for files in traffic_management/demos

The *_demo.md files in content/docs/tasks_usage/traffic_management/demos/ are not displayed under the Traffic Management Demos section, but rather under the Traffic Management top level section.
Based on the folder structure, I would expect the *_demo.md files to show up under an intermediary Traffic Management Demos folder instead.

There is an _index.md file (https://github.com/openservicemesh/osm-docs/blob/main/content/docs/tasks_usage/traffic_management/demos/_index.md) but I wonder if this is too many levels deep - @flynnduism to advise.

This looks like a stylesheet issue rather than a Hugo / templating issue. The sidebar is rendering the *_demo.md pages as children of the Traffic Management Demos page, but the CSS incorrectly makes it look like they are siblings.

I will review the styling to ensure that 3rd level items and 4th level items can be properly distinguished in the tree. My changes in #44 made things clearer for the upper levels, but looks like there's more styling needed.

@flynnduism can you give an update on this issue? Thank you!

This no longer appears to be an issue. Closing


Update plugin-options.md

The fix works, but only in the built artifacts.

Makes sense, thanks for the update to the docs!


Rewiring question

Hi~ Sorry I have many questions on this algorithm haha. I'm trying to fully understand the algorithm and I have a question on the REWIRE(r) function.
Suppose we already have already encounter a->b, w1 in our G, now we encounter a rule, r = b|a->c w2, and we want to rewire it. Based on the algorithm PrevSource = a, PrevTarget = b, and indeed edge(a, b|a) not in the graph, then we add the edge (a, b|a, w2) and remove (a, b). Is this correct?
So I'm confused why we make the edge (a, b|a) has weight w2, w2 can be different from w1 right? So we may overcount or undercount the transition between a and b? It seems weird that the transition between a and b is related to c. And one can also imagine, if we have b|a -> d, w3, then the weight of (a, b|a) will change if we encounter b|a -> d first and b|a->c second (since we don't need to rewire under this circumstances).
Thank you so much!

Hi @xindi-dumbledore , thank you for your question. This does seem to be a bug in this pyHON code.
If we have a->b, w1 and b|a->c w2, then the first link a->b w1 should be rewired as a->b|a w1.
For b|a->c w2, source = b|a, PrevSource = a and PrevTarget = b.
We should assign PrevSource -> source = w1, which is G[PrevSource][PrevTarget]. My current code incorrectly assigns Graph[source][target] (w2) to a->b|a.
That's a good catch! Thank you again, and please kindly let me know if you notice any other issue.

Also just checked the same step in the Lisp version of the code (cl-HON) which looked correct. Just pyHON's bug.


Update java-setup.md

Fixes #57
Short description of what this resolves:

What Changes proposed in this pull request:

Explanation Setting Up  environment for Java

Checklist

[x] Added description of change
[x] Added documentation so that the program is self-explanatory and educational.
[x] Relevant documentation/comments is changed or added
[x] I acknowledge that all my contributions will be made under the project's license.

Notes:

@Utkarsh1504 you are requested to review

@KhafiaAyyub your content looks great but you messed up this PR with your changes.
You should always create a new branch for any changes you do. So now just revert these changes if you know how to do it, otherwise, delete this Repository and then Fork it again, and then

firstly make a branch
then In that branch add documentation for quicksort
and make another branch and in that branch make changes for java setup
leave your main branch as it is.  Just use main branch for fetching upstream commits
By doing this you will never face any merge conflicts or any other kind of issues


Added custom parameters for accessibility button

Reasons for making this change
Makes it look better on the site by changing color to daily colors and also position to always bottom right.
Related tickets
fixes #191
Screenshots
[If this is a visual change, please add screenshots showing how the website looks like]
[Desktop screenshot]

@hs4man21 Exec wanted the red. I did test it over the footer/header and it's still easily visible because the white in the icon is still high contrast on the background. And yes, it has been tested on mobile.


SQL Server with Windows Auth working end-to-end with EF in K

@AndriySvyryd and I think this is probably already fixed but we need to verify.

Verified on SQL Express


Changes version to 1.7.3-RC1

Codecov Report

Merging #4042 into 1.7.x will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##            1.7.x    #4042      +/-   ##
==========================================
+ Coverage   40.57%   40.61%   +0.03%
==========================================
  Files        2203     2203
  Lines       71624    71624
  Branches     9890     9890
==========================================
+ Hits        29064    29091      +27
+ Misses      39803    39776      -27
  Partials     2757     2757

Impacted Files
Coverage Δ

...m/navercorp/pinpoint/test/OrderedSpanRecorder.java
72.11% <0%> (ø)
:arrow_up:

...navercorp/pinpoint/rpc/common/SocketStateCode.java
85.36% <0%> (+2.43%)
:arrow_up:

.../pinpoint/rpc/client/PinpointClientHandshaker.java
66.42% <0%> (+6.42%)
:arrow_up:

...pinpoint/profiler/instrument/AccessorAnalyzer.java
65.71% <0%> (+8.57%)
:arrow_up:

...rp/pinpoint/rpc/control/ControlMessageDecoder.java
78.57% <0%> (+14.28%)
:arrow_up:

...p/pinpoint/rpc/client/WriteFailFutureListener.java
75% <0%> (+18.75%)
:arrow_up:

...npoint/rpc/server/SimpleServerMessageListener.java
100% <0%> (+20%)
: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 b74921f...ec079e8. Read the comment docs.


Needs art

Notes of implemented (mostly) but no art I still need, preferably in vanilla/SOS2/existing spinal engines style:
Engine emergency overdrive injector: Block, gizmo icon. Currently 1X5, should connect to the side of the existing exhaust bell, somehow. Doesn't have to be 1X5, but due to current multiblock rules (and rimworld "center" block in even sizes), has to lineup in specific ways. Ugly placeholder art demo attached in comment
Test burn: Gizmo Icon (or use something from vanilla maybe?)
Gravitational compensators (to allow liftoff): block, currently 3X3, attaches to the same place as overdrive, same notes.
Supplemental fuel tanks presumably? to attach to the compensators? But could be attached to fuel end instead? 3X5 atm
Ramjet: Front scoop (5 wide by.... 3? deep, this is pretty flexible. Optionally perhaps "wings" to extend the scoop size to make it more of a solar sail vibe? Will require clearance to edge of map) NYI (Not Yet Implemented)
An entire new multiblock (Salvage yard): pawns work at stations installed in the edge of a rectangular structure, deconstructing the shipwrecks that have been moved inside. Items inside (including from deconstruction) are moved to the output ports for hauling.
Walls (basic structure, 1X1, draggable like well, walls. Will always form a rectangle when multiblock is correctly constructed)
Workstations (two, main controller (allows working) plus supplemental pawn workstations): currently 1X3, could possibly be 1Xwhatever, but I do like bilateral symmetry. No reason the controller isn't just the workstation with some extra whatever.
Item outputs (1X1, fit into walls, not draggable atm but placeholder art is just walls with a different colour)
AI "workstation" (A persona core that slowly works constantly, currently 1X3 but could be 1Xwhatever):
Anyone reading this and wanting to do some art feel free to reply, hmu on the SOS2 discord, whatever!
WIP: JT/entangled accelerators: block - erimathas was tinkering with this


[Bugfix] Fix bug create MV with explain query

What type of PR is this：

[x] bug
[ ] feature
[ ] enhancement
[ ] refactor
[ ] others

Which issues of this PR fixes ：

Fixes #10347
Problem Summary(Required) ：

we should not support create explain query for materialized view
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] I have added user document for my new feature or new function

[FE PR Coverage Check]
:heart_eyes: pass : 7 / 8 (87.50%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
3
4
75.00%
[1188]

:large_blue_circle:
com/starrocks/sql/common/MetaUtils.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
3
3
100.00%
[]

[FE PR Coverage Check]
:heart_eyes: pass : 8 / 8 (100.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/sql/parser/AstBuilder.java
4
4
100.00%
[]

:large_blue_circle:
com/starrocks/sql/common/MetaUtils.java
1
1
100.00%
[]

:large_blue_circle:
com/starrocks/sql/parser/SqlParser.java
3
3
100.00%
[]

run starrocks_admit_test


Minor changes to make router-view & v-card-media changes obvious

Minor changes to make sure that:

people (those who look at code blocks first, like me..) actually get router-view into their app
added a couple of lines so that the v-card matches the 'end result' file for this workshop, with a link to v-card docs in Vuetify

We're going to close this PR with the router addition but not the vuetify change. thanks!


SoA (Struct of Array) Interface Selection

SoA support would be an important feature for symusic, since it is more suitable for AI applications than the current AoS (Array of Struct) interface.
SoA interface could enable lots of flexible conversion, resampling, quantization and other operations. #10
These functions take full advantage of numpy's eco (like numba), and could be very fast.
It's also important that we don't need to introduce more time_unit types (like beat) in symusic, which would make the general purpose code in c++ part more and more complex.
However, the interface for SoA is still to be determined. I'd like to hear your advice @Natooz @ilya16 . And of course, other design options are welcome!
Here, I will list some possible options I could think of.
Option 1: Dict of Numpy Array
In this case, we won't introduce new classes in symusic, but only use dict and numpy.ndarray.
from symusic import Score, Note, ControlChange
s = Score(...)

# get the soa of controls
# because "controls" is not a python list, but a c++ vector
# we could bind a .numpy() method for it
controls_arr: Dict[str, np.ndarray] = s.controls.numpy()
notes_arr: Dict[str, np.ndarray] = s.tracks[0].notes.numpy()

# create traditional AoS from numpy array
# Here, we could utilize the existing factory class for events like notes
s.controls = ControlChange.from_numpy(controls_arr['time'], controls_arr['number'], controls_arr['value'])
s.tracks[0].notes = Note.from_numpy(notes_arr['time'], notes_arr['duration']， notes_arr['pitch']， notes_arr['velocity'])
# or we could use ** to shorten this
s.controls = ControlChange.from_numpy(**controls_arr)
s.tracks[0].notes = Note.from_numpy(**notes_arr)

Option 2: New SoA Classes in C++
In this case, we will define new classes for SoA, and use them in symusic. It seems more object-oriented.
The problem is, they will be defined 3 times, because of time unit. (The same reason for NoteTick, NoteQuarter and NoteSecond)
We will define a Union for them in symusic.types
from symusic import Score
import symusic.types as smt

# get the soa of controls and notes
controls_arr: smt.ControlChangeArr = s.controls.numpy()
notes_arr: smt.NoteArr = s.tracks[0].notes.numpy()

# convert them back to AoS
s.controls = controls_arr.list()
s.tracks[0].notes = notes_arr.list()

Also, although we have switched to nanobind, which get a much smaller overhead on accessing class attributes, the overhead is still there. Note that those overhead are almost constant, so it's not a problem for those "ms level" functions.
So if not necessary, I would not recommend create new class in c++. (Well, this overhead should be considered more in AoS part, not the SoA part)
Here is a benchmark for those tiny operations.

lib
Create a Note
Access Note.pitch
Note.pitch += & -=

python dict
66 ns
17 ns
69.9 ns

miditoolkit
162 ns
15.2 ns
48.1 ns

NamedTuple
175 ns
17.4 ns
tuple is const

symusic[nanobind]
251 ns
27.8 ns
110 ns

symusic[pybind11]
791 ns
238 ns
1070 ns

nb.jitclass in py
5.6 µs
37.8 ns
656 ns

Option 3: New SoA Classes in Python
In this case, we define the new class in python. It is more flexible, python native (no overhead).
But, these class can't be called in c++ (At least I don't know how to achieve this now. Maybe it's possible).
So, we won't get the .numpy() function here.
from symusic import Score, NoteArr, ControlChangeArr

controls_arr = ControlChangeArr(s.controls)
notes_arr = NoteArr(s.tracks[0].notes)

# convert them back to AoS
s.controls = controls_arr.list()
s.tracks[0].notes = notes_arr.list()

Option 1 seems reasonable to me, for both simplicity and performance.

I agree that option 1 seems the most simple, versatile and low maintenance.

We finally choose option 1 in v0.3.0. #19


[share_plus] iOS: fix file names and preview

Description
Currently, when using sharing files on iOS, saved files would have new generic names like "image PNG", "image PNG 2", etc, instead of ones they were shared with.
This PR also fixes an issue where images had no previews and the share-sheet always displayed the App's icon.
As always I provide a test respository for these changes here.
Related Issues
Fixes #821
Closes #808
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated the version in pubspec.yaml and CHANGELOG.md.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (flutter analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
[x] No, this is not a breaking change.

Can you please fix the merge conflict? I tried to push into your branch to fix it, but I didn't have permissions.

That’s weird because ‘Allow edits by maintainers’ is checked… Will fix today and bump version to ‘4.0.6’.

perfect, thanks!


Add xhprof_frame_begin & xhprof_frame_end

Add functions for sub-function profiling.

xhprof_frame_begin : Starts an artificial frame. Together with
xhprof_frame_end, this times one block of code execution as if it
were a function call, allowing people to define arbitrary function
boundaries.

xhprof_frame_end : Ends an artificial frame that xhprof_frame_begin
started. One has to make sure there are no exceptions in between these
two calls, as otherwise, it may report incorrect timings. Also,
xhprof_frame_begin and xhprof_frame_end have to be paired up
really well, so not to interfere with regular function's profiling,
unless that's the intention.

XhprofFrame : Wrapper object that calls xhprof_frame_begin in its
constructor and xhprof_frame_end in its destructor.

This functionality was back ported from HHVM's internal XHProf
implementation. There has been one small change from the HHVM
implementation with the addition of the optional $wrapped boolean
parameter to xhprof_frame_begin which is used to fix a bug in the
upstream XhprofFrame implementation which mis-attibutes function calls
in a frame introduced via XhprofFrame to XhprofFrame::__construct
rather than the name provided for the frame.
Fixes #51

:birthday: I meant to ping on 2015-11-28, but better late than never as the Hallmark® cards tell me.


Create JSON-backed dialog for virtualizing Teradata & MongoDB

Create JSON-backed dialog with following fields to inject into Teradata/MongoDB Virtualization Notebooks:
Summary of the variables we need support for:

master_key
external_data_source_name
external_table_name
database_name
credential_name
username
password
server_address

I'm going to close this since we're going to be enabling MongoDB/Teradata support in the Data Virt wizard soon so this seems unnecessary.


[Polymetis] Franka gripper fix

Description
Apparently franka::Gripper hates it when being interrupted while executing commands (move or grasp).
Terminating the previous command using franka::Gripper::stop to terminate the previous command didn't work well either.
Final fix consists of gRPC calls that are always blocking.
GripperInterface caches the latest gripper command and only sends it after the previous command has completed.
Type of change
Please check the options that are relevant.

[x] Bug fix (non-breaking change that fixes an issue)
[ ] Proposes a change (non-breaking change that isn't necessarily a bug)
[ ] Refactor
[ ] New feature (non-breaking change that adds a new functionality)
[ ] Breaking change (fix or feature that would break some existing functionality downstream)
[ ] This is a unit test
[ ] Documentation only change
[ ] Datasets Release
[ ] Models Release

Type of requested review

[x] I want a thorough review of the implementation.
[ ] I want a high level review.
[ ] I want a deep design review.

Before and After
If this PR introduces a change or fixes a bug, please add before and after screenshots (if this is causes a UX change) or before and after examples(this could be plain text, videos etc ) to demonstrate the change.
If this PR introduces a new feature, please also add examples or screenshots demonstrating the feature.
Testing
Please describe the tests that you ran to verify your changes and how we can reproduce.
Checklist:

[ ] I have performed manual end-to-end testing of the feature in my environment.
[ ] I have added Docstrings and comments to the code.
[ ] I have made changes to existing documentation where needed.
[ ] I have added tests that show that the PR is functional.
[ ] New and existing unit tests pass locally with my changes.
[ ] I have added relevant collaborators to review the PR before merge.
[ ] [Polymetis only] I have verified that all scripts in tests/scripts runs on hardware.

Might want to use a size-1 queue for thread safety and simplicity, in case people are calling a lot of _send_gripper_commands in a row. I am not sure that this code is thread safe, e.g. a new command may occur right before line 47 and get deleted. Regardless, probably can decrease the number of Event flags to keep track of.

I don't see how a size-1 queue would help since managing the length of the queue would essentially be the same as replacing the variable.
Line 47 can actually be removed, since we're using update_event to keep track of cache updates and done_event to keep track of command execution (for blocking use cases). I don't see how we can remove any one of these events.

Python queues have a maxsize input parameter which you can set to 1 -- I think you can just get rid of all the Event objects, call q.get() in the child thread in a loop, and simply add to the queue and get thread safety for free.

Also, what are the benefits of shutting down gracefully?
I think having it as a daemon thread makes sense because:

The command execution thread doesn't hold any complicated resources that would cause problem during shutdown.
It'll eliminate the need to track one extra "stop event".
Daemon threads are guaranteed to not block the termination of the main thread.

Ah okay, I missed that -- yep, daemon sounds good to me!


Inconsistency in UX when using tenanted URLs in user-portal

Steps to reproduce

Create a tenant wso2.com in the WSO2 IS.

access https://localhost:9443/user-portal

login as super.tenant user 'admin:admin'

In the same browser access 'https://localhost:9443/t/wso2.com/user-portal'

Following error page is displayed

In the same browser access 'https://localhost:9443/t/wso2.com1/user-portal', with a non-existing tenant.

A blank page is displayed

In both cases, user experience can be improved.

Duplicates https://github.com/wso2/product-is/issues/8695


TeX file syntax: recognize "align" as math environment

Problem: In TeX files "align" and "align*" environments are not
recognized as math-environments, causing misleading syntax highlighting
in their content.
Solution: Register "align" as math environment

In https://github.com/vim/vim/commit/f0b03c4e98f8a7184d8b4a5d702cbcd602426923#diff-9aa7419d9504f85f995d943175f49e46 align and other environments provided by amsmath were removed.
I wonder why?

Moved here: http://www.drchip.org/astronaut/vim/.  Justification:

Syntax/tex.vim should not support packages' macros, environments, etc.;

I don't know about that.. but either way this PR would not be the right fix.  Unfortunately, right now the user has no way of knowing they have to fetch packages from another website to support amsmath (an exceedingly common package).

@cecamp's answer is here:
https://groups.google.com/d/topic/vim_use/dyrKDG8bm8s/discussion
I coincidentally noticed his answer in the vim_use mailing list, but other people in this thread won't notice that, I think.

Syntax/tex.vim should not support packages' macros, environments, etc.;

Then syntax/tex.vim should not support the following macros (symbols) provided by amsmath or amssymb.

list

\backepsilon
\backsimeq
\barwedge
\because
\beth
\between
\blacksquare
\boxdot
\boxminus
\boxplus
\boxtimes
\Box
\bumpeq
\Bumpeq
\Cap
\circeq
\circlearrowleft
\circlearrowright
\circledast
\circledcirc
\complement
\Cup
\curlyeqprec
\curlyeqsucc
\curlyvee
\curlywedge
\doteqdot
\dotplus
\dotsb
\dotsc
\dotsi
\dotso
\doublebarwedge
\eqcirc
\eqsim
\eqslantgtr
\eqslantless
\eth
\fallingdotseq
\geqq
\gimel
\gneqq
\gtrdot
\gtreqless
\gtrless
\gtrsim
\iiint
\iint
\implies
\leadsto
\leftarrowtail
\leftrightsquigarrow
\leftthreetimes
\leqq
\lessdot
\lesseqgtr
\lesssim
\lneqq
\ltimes
\measuredangle
\ncong
\nexists
\ngeq
\ngeqq
\ngtr
\nleftarrow
\nLeftarrow
\nLeftrightarrow
\nleq
\nleqq
\nless
\nmid
\nparallel
\nprec
\nrightarrow
\nRightarrow
\nsim
\nsucc
\ntriangleleft
\ntrianglelefteq
\ntriangleright
\ntrianglerighteq
\nvdash
\nvDash
\nVdash
\pitchfork
\precapprox
\preccurlyeq
\precnapprox
\precneqq
\precsim
\rightarrowtail
\rightsquigarrow
\rightthreetimes
\risingdotseq
\rtimes
\sphericalangle
\sqsubset
\sqsupset
\Subset
\subseteqq
\subsetneq
\subsetneqq
\succapprox
\succcurlyeq
\succnapprox
\succneqq
\succsim
\Supset
\supseteqq
\supsetneq
\supsetneqq
\therefore
\trianglelefteq
\triangleq
\trianglerighteq
\twoheadleftarrow
\twoheadrightarrow
\ulcorner
\urcorner
\varnothing
\vartriangle
\vDash
\Vdash
\veebar
\Vvdash

Closing for no activity


Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'android.view.Surface android.media.ImageReader.getSurface()' on a null object reference

Steps to reproduce

My app embed the native, banner ads with video player, and I catch some randomly crashes on firebase.
Unlike the #19595 , My app is do nothing with camera.
It shows crashed devices are 81% Samsung and 15% Motorola along with 68% Android 14, 32% Android 13.
According to the fireabse events, it shows the crashes may not relate to be video player, because some users were never reach the player view before this crash.
The logs is attached below.

Expected results
no crash
Actual results
crash
Code sample
Sorry, but I have no idea where is the key code to cause this crash, the stack trace is not point to anywhere in my code, and the firebase events indicates even no specific screen of my app cause this crash.
What I only got is crash logs from firebase.
Screenshots or Video
No response
Logs
Logs
Fatal Exception: java.lang.NullPointerException: Attempt to invoke virtual method 'android.view.Surface android.media.ImageReader.getSurface()' on a null object reference
       at io.flutter.plugin.platform.b.getSurface(ImageReaderPlatformViewRenderTarget.java:3)
       at io.flutter.plugin.platform.b.lockHardwareCanvas(ImageReaderPlatformViewRenderTarget.java:1)
       at io.flutter.plugin.platform.n.draw(PlatformViewWrapper.java:16)
       at android.view.View.updateDisplayListIfDirty(View.java:24024)
       at android.view.View.draw(View.java:24895)
       at android.view.ViewGroup.drawChild(ViewGroup.java:4789)
       at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4547)
       at android.view.View.updateDisplayListIfDirty(View.java:24010)
       at android.view.View.draw(View.java:24895)
       at android.view.ViewGroup.drawChild(ViewGroup.java:4789)
       at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4547)
       at android.view.View.updateDisplayListIfDirty(View.java:24010)
       at android.view.View.draw(View.java:24895)
       at android.view.ViewGroup.drawChild(ViewGroup.java:4789)
       at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4547)
       at android.view.View.updateDisplayListIfDirty(View.java:24010)
       at android.view.View.draw(View.java:24895)
       at android.view.ViewGroup.drawChild(ViewGroup.java:4789)
       at android.view.ViewGroup.dispatchDraw(ViewGroup.java:4547)
       at com.android.internal.policy.DecorView.dispatchDraw(DecorView.java:1185)
       at android.view.View.draw(View.java:25168)
       at com.android.internal.policy.DecorView.draw(DecorView.java:1167)
       at android.view.View.updateDisplayListIfDirty(View.java:24024)
       at android.view.ThreadedRenderer.updateViewTreeDisplayList(ThreadedRenderer.java:764)
       at android.view.ThreadedRenderer.updateRootDisplayList(ThreadedRenderer.java:770)
       at android.view.ThreadedRenderer.draw(ThreadedRenderer.java:868)
       at android.view.ViewRootImpl.draw(ViewRootImpl.java:5993)
       at android.view.ViewRootImpl.performDraw(ViewRootImpl.java:5662)
       at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:4770)
       at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:3275)
       at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:11256)
       at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1650)
       at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1659)
       at android.view.Choreographer.doCallbacks(Choreographer.java:1129)
       at android.view.Choreographer.doFrame(Choreographer.java:1055)
       at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1622)
       at android.os.Handler.handleCallback(Handler.java:958)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loopOnce(Looper.java:230)
       at android.os.Looper.loop(Looper.java:319)
       at android.app.ActivityThread.main(ActivityThread.java:8913)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:608)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)

Flutter Doctor output
Doctor output

[✓] Flutter (Channel stable, 3.19.5, on macOS 14.4 23E214 darwin-x64, locale zh-Hans-CN)
    • Flutter version 3.19.5 on channel stable at /Users/london/Library/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 300451adae (4 weeks ago), 2024-03-27 21:54:07 -0500
    • Engine revision e76c956498
    • Dart version 3.3.3
    • DevTools version 2.31.1

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/london/Library/Android/sdk/
    • Platform android-34, build-tools 34.0.0
    • ANDROID_SDK_ROOT = /Users/london/Library/Android/sdk/
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15E204a
    • CocoaPods version 1.14.3

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

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

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

[✓] Proxy Configuration
    • HTTP_PROXY is set
    • NO_PROXY is localhost,<IP_ADDRESS>,::1
    • NO_PROXY contains localhost
    • NO_PROXY contains <IP_ADDRESS>
    • NO_PROXY contains ::1

[✓] Connected device (4 available)
    • Pixel 6 (mobile)         • 26111FDF6002Q4            • android-arm64  • Android 14 (API 34)
    • London’s iPhone (mobile) • 00008101-001E39DE3A63001E • ios            • iOS 17.4.1 21E236
    • macOS (desktop)          • macos                     • darwin-x64     • macOS 14.4 23E214 darwin-x64
    • Chrome (web)             • chrome                    • web-javascript • Google Chrome 124.0.6367.61
    ! Error: Browsing on the local area network for 邓慧的 iPhone. Ensure the device is unlocked and attached with a cable or
      associated with the same local area network as this Mac.
      The device must be opted into Developer Mode to connect wirelessly. (code -27)

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Thanks for the report @LondonX
Maybe it is related to Android SurfaceView that external plugins (ads in your case) could be using.
Is there a way for you to narrow it down by removing ads implementation ?
Would also be interesting to check if the same exception occurs using virtual display or hybrid composition of android views or is it just specific to surface view.

I finally reproduced the crash on my device.
For now, my conclusion is the crash is related with ads (google_mobile_ads) which contained in AnimatedContainer.
I fixed it by replacing the AnimatedContainer to isKeyboardShowing ? const SizeBox(width: double.maxFinite) : MyAdsView(...).
But I wonder if this crash may also reproduce on any other PlatformView with AnimatedContainer?
BTW, it seems like the refresh rate and the FPS may be positively correlated with crash rate, so I cannot reproduce this crash on Pixel 3 but can reproduce on Pixel 6, and crashed devices shows on firebase are high-end even flagship devices.

Good to know you were able to replicate the crash.

For now, my conclusion is the crash is related with ads (google_mobile_ads) which contained in AnimatedContainer.
I fixed it by replacing the AnimatedContainer to isKeyboardShowing ? const SizeBox(width: double.maxFinite) : MyAdsView(...).

I suggest you to follow-up in dedicated repo for further resolution.

But I wonder if this crash may also reproduce on any other PlatformView with AnimatedContainer?

If you can come up with reproducible code sample for this, we would be happy to look into it further.

Strange, I created a new project with minimal code to make a Native ad in AnimatedContainer, also collapsing and expanding with keyboard visibility changing, nothing crash.
Maybe I show close this issue for now.
Thank you for your patient reply!


Emeded Video's - This content is blocked.

Describe the Bug
I have upgraded to the latest version and embeded videos are saying that the content is blocked and to contact the site owner to fix the issue.

Steps to Reproduce
Go to article, and embed a known shared video on the article and post.
Expected Behaviour
Video preview to be there.
Screenshots or Additional Context
I have upgraded to the latest version this week but only noticed today.
Browser Details
Chrome, Edge, firefox
Exact BookStack Version
22.04.2
PHP Version
PHP 7.4.28
Hosting Environment
Ubuntu 18.04.6 LTS on Hyper-V

Hi @davecowley,
This is very much likely related to update notice for v22.02.3:
https://www.bookstackapp.com/docs/admin/updates/#updating-to-v22023-or-higher

Hi @ssddanbrown
thanks for your help, I added the line in as mentioned and it worked.
for anyone else reading this.
add this line to your .env file /var/www/bookstack/.env
ALLOWED_IFRAME_SOURCES="https://.draw.io https://.youtube.com https://.youtube-nocookie.com https://.vimeo.com https://*.microsoftstream.com"


Add support for custom table row classes based on the record

This PR adds the ability to dynamically add classes to a table row based on the record.
It therefore provides a single method to alter for example text-color, background and borders on a table row.
It supports a flexible and even conditional return type:
protected function getTableRecordClassUsing(): ?Closure
    {
        return function (Post $record) {
            return match ($record->status) {
                'draft' => 'opacity-30',
                'reviewing' => [
                    'border-l-solid',
                    'border-l-2',
                    'border-l-orange-600',
                    'dark:border-l-orange-300' => config('filament.dark_mode'),
                    'opacity-30',
                ],
                'published' => 'border-0 border-l-solid border-l-2 border-l-orange-400',
                default => null,
            }
            return null;
        };
    }

Preview:

I think we prefer getRecordClasses over getRecordClass. So could you change Class to plural in all places you added it?

Related: #2746, #3465

@danharrin, this should be ready to be merged. Tested it locally and cleaned up the new documentation.

Thanks @marcoboers

Was this removed again?

Nope, and we wouldn't as that would be a breaking change.

Is it not more available? I can't find it, or I don't know how to apply it =(

Please just search the docs https://filamentphp.com/docs/3.x/tables/advanced#custom-row-classes

Please just search the docs https://filamentphp.com/docs/3.x/tables/advanced#custom-row-classes

oh I see sorry, thank you!

can we do that with grid layout as well?


Hide and show password functionality button in form

Feature request:
Hide and show password functionality button in form

@abhay27chauhan do you wanna take this issue?

Yes
On Sun, 4 Apr, 2021, 1:38 AM Vaishali, @.***> wrote:

@abhay27chauhan https://github.com/abhay27chauhan do you wanna take
this issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Girl-Code-It/Opportunity-Calendar-Frontend/issues/184#issuecomment-812919045,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKG5GE2ZEFC2ZSJRNTX3WXTTG5YVDANCNFSM42KPQN5Q
.

@vaishali614 what should use for the icon ?

@vaishali614 done.


[TACHYON-1068] Add new regexp rule for reserved ratio conf

https://tachyon.atlassian.net/browse/TACHYON-1068

+1 LGTM

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/Tachyon-Pull-Request-Builder/5506/
Test PASSed.


exec for update does not correctly return sql.Results

sql.Results for update is always showing RowAffected as zero updated even though the update actually happened
code included to replicate
poc.tar.gz

I figured out what the issues was. it does not work through a view, but works against the table directly


self.generator.predict(noise) in SGAN.py is returning [nan, ..., nan] after first training epoch.

Hello there,
As I said self.generator.predict(noise) returns nan after g_loss = self.combined.train_on_batch(noise, validity, class_weight=[cw1, cw2]) has run once:
        gen_imgs = self.generator.predict(noise)
        print(gen_imgs) # [[[[ 0.06864215] [ 0.00251574] [ 0.035886] ...,

        # Train the generator
        g_loss = self.combined.train_on_batch(noise, validity, class_weight=[cw1, cw2])

        gen_imgs = self.generator.predict(noise)
        print(gen_imgs) # [[[[ nan][ nan][ nan]...,

May you please specify the different versions (python, numpy, matplotlib, keras, tensorflow) in use? :) Would be awesome! Have a nice day and thank you very much for your effort!

from future import division fixed it :)


Inaccurate display of "Viewed" count in file diff when expanding files

Description
I have observed a bug in Gitea's file diff feature regarding the display of "Viewed" count in the context of expanding files.
I have configured the "MAX_GIT_DIFF_LINES:200" and "MAX_GIT_DIFF_FILES:20" settings in  app.ini . However, when I expand files in the diff view, the "Viewed" count appears to be inaccurately tracked. Specifically, clicking "View More" seems to reset the viewed count and sometimes even results in a negative count when unchecking previously viewed files.
Gitea Version
1.19.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots

Git Version
<IP_ADDRESS>
Operating System
centos 7
How are you running Gitea?
it is being run from a helm chart.
Database
PostgreSQL

I think that bug was already fixed, please update to 1.20.


source_id -- register ''ACCESS-OM2"

label = ACCESS-OM2
label_extended = Australian Community Climate and Earth System Simulator Ocean Model Version 2
source_id = ACCESS-OM2
institution_id = CSIRO-COSIMA
release_year = 2020
activity_participation = OMIP
aerosol:
description = none
nominal_resolution = none
atmos:
description = none
nominal_resolution = none
atmosChem:
description = none
nominal_resolution = none
land:
description = none
nominal_resolution = none
landIce:
description = none
nominal_resolution = none
ocean:
description = ACCESS-OM2 (MOM5, tripolar primarily 1deg; 360 x 300 longitude/latitude; 50 levels; top grid cell 0-2.3 m)
nominal_resolution = 100 km
ocnBgchem:
description = WOMBAT (same grid as ocean)
nominal_resolution = 100 km
seaIce:
description = CICE5.1.2 (same grid as ocean)
nominal_resolution = 100 km

@sjmarsland another registration complete, I was curious about the WOMBAT version but didn't want to hold up registration. Take a peek at CMIP6_source_id.html and let me know of any additional tweaks

Thanks @durack1. No, WOMBAT does not have an official version number so all good.


MAINT: cluster: cleaning up VQ/k-means code

Much of the code in scipy.cluster.vq is almost 10 years old, so I figured it was time for an overhaul.
Backwards compatibility

The method for selecting random elements from an array changed, so code relying on a random seed to produce the same codebook initialization will break (e.g., the test I removed).
The py_vq fallback function now computes all n * k distances at once, instead of k at a time. This is much faster (see the benchmarks), but does incur a potentially large memory cost if n and k are large. If this is a problem, we can change it to use a chunking strategy similar to scikit-learn's pairwise_distances_argmin_min function.
The unused py_vq2 function is now just an alias for py_vq. I'm happy to deprecate it, though.
Passing a non-numeric scalar k to kmeans now throws a TypeError rather than a ValueError.
Some warning/error messages were re-written for clarity.

If you think any of the above changes (or any I missed) are problematic, let me know.
Benchmarks
I added new benchmarks to make sure k-means and VQ don't regress in terms of speed, and here are the relevant changes for this PR:
BENCHMARK                                    BEFORE      AFTER     FACTOR
cluster.KMeans.time_kmeans(10)              61.52ms    53.16ms   0.86403187x
cluster.KMeans.time_kmeans(2)               23.07ms    19.77ms   0.85714533x
cluster.VQ.time_vq(50, 'float128')          96.44ms     3.33ms   0.03448292x
cluster.VQ.time_vq(10, 'float128')          81.17ms     1.02ms   0.01251954x
cluster.VQ.time_vq(2, 'float128')           76.28ms   473.52μs   0.00620748x

Note that last 3 lines are the branches which end up in py_vq. I think the use of a length-limited deque is responsible for the speedup in kmeans, but I haven't confirmed that by profiling.
@pv: I'm not sure that my method for generating a consistent random matrix for the benchmarks is the correct approach. The idea is to test each run using the same random values, though the variation in cluster initialization probably makes that irrelevant anyway...

That looks like a much-needed cleanup!

selecting random elements changed: I think that's fine, just needs to be documented in the release notes as a backwards incompatible change.
py_vq2: go ahead and deprecate that I'd say
chunking strategy, not so sure. float16/float128 is probably not interesting, but there may be users with large integer arrays.
the last two points you mention seem perfectly fine

I added a mention in the release notes and deprecated py_vq2.

Test failures for kmeans are real.

Old code crept back in during my rebase. Fixed now.

LGTM, merged. Thanks @perimosocordiae!


Configure ORCID authentication

The ORCID authentication link under 'edit profile' won't work until we connect our services.
Need to do this before testing DMPonline

@briri can you advise on Orcid login capability?

You need to make sure 'orcid' appears in the identifier_schemes table. Once that's in place you should just need to make sure your devise.rb has it defined as well
config.omniauth :orcid, 'client_id', 'client_secret', {'scope': '/authenticate'}

You need to register your DMPonline app with them in order to get the API keys

Thanks, already registered a 'sandbox' account with ORCiD.

Works in DMPonline test and staging. Closing out

@briri
Referring to your answer above 'You need to register your DMPonline app with them in order to get the API keys' - please advise.

@Ebrahim1010
I think ORCiD explains their side of it better than we could:
https://members.orcid.org/api/oauth
As for how we're configuring this with rails, check out the config page for the gem we're using, omniauth-orcid:
https://github.com/datacite/omniauth-orcid
Between the two of those, you should be able to request an API key from ORCiD, and then get this setup in your application.
We also have a wiki page of documentation about how the application side handles things:
https://github.com/DMPRoadmap/roadmap/wiki/OAuth-Providers


v0.10 Planning

Now that Most of big fishes are fried, v0.10 will focus on polishing Browser detection, opening, profiles...

[ ] #150

[ ] #32

[ ] #149
[ ] Move to WinAppSDK v1.6

[ ] Fix specifying a solution-level output path results in all projects copying outputs to the same directory, which can lead to inconsistent builds warning during release build
[ ] Adopt AoT compilation

0.9.1

[ ] #100
[x] Option to disable Minimize on focus loss
[ ] Explore auto-updater
[ ] #162

May I suggest:

include the BrowserSelector page in the main window (for quick access to settings, remove wpfui, theme adapting)

Brush up the XAML for that page (let me know if you want me to pick up something here)

use a (compact) NavigationView control
use as native as possible solution for TitleBar

include the BrowserSelector page in the main window

Not sure what you mean by this.

use a (compact) NavigationView control

I don't prefer the compact one, but something like MS Store or Windows Settings is preferable.
(the current implementation in Hurl Settings doesn't clean up memory, so memory usage rises up in 1 MBs as it's navigated, even to the same page)

include the BrowserSelector page in the main window

My idea would be to combine this page with the rest

I personally prefer to keep Hurl Settings and Selector separately.

📰 WASDK 1.6.0 is out 😄

Any specific areas / issue you want help with?

Any specific areas / issue you want help

Guess so, one thing I want to experiment is migrate Hurl.BrowserSelector (maybe should be renamed to Hurl.Selector) to WinAppSDK. so only thing I am not sure there is how minimizing to Tray works there.
So, If you are interested, A minimal PR that only does migration to WinAppSdk and WinUi components without much UI or functional changes or you can choose to help with anything else, but focused PRs haha.

Waiting on https://github.com/actions/runner-images/issues/10734 to release v0.9.1
https://github.com/actions/runner-images/blob/main/images/windows/Windows2022-Readme.md#workloads-components-and-extensions

too many thanks for your amazing work.


Handle io streams as daemon process

CRI itself should close stdin/stdout/stderr and reopen stdout and stderr with pointing them to a log file.

We use systemctl now


Lock an element ?

Hello everyone.  I wonder if it's possible to lock an element in a list.
For example, I've got a list that I can sort :

...

...

...

I used the filter to my .locked element but the others
 can be positioned below my .locked element.
Is there a way to prevent this ?
Thanks !

Create example on jsbin.com (draft)

Thanks for your reply.
As you can see on this JS Bin I can drag my first li under my .locked li.
I'd like to keep my .locked li always at the end of my ul. Is there a way to do this with the library?

onMove:function (evt) {
	    if (evt.related)
	    {
	    	return !evt.related.classList.contains('lock');
	    }
	}

hope can help you.

It works fine ! Exactly what I need ! Thanks !

onMove:function (evt) {
        if (evt.related)
        {
            return !evt.related.classList.contains('locked');
        }
    }

hope can help you.

Thank you for your solution.


Plotting error when running with specific humidity (Q)

Both @juliecaron and @andrewgettelman have received the following error when running the diagnostics with the variable Q (specific humidity):
Q has lev dimension.

Traceback (most recent call last):

  File "./run_diag", line 178, in <module>

    diag.create_plots()

  File "/glade/campaign/cgd/amp/jcaron/python/CAM_diagnostics/lib/CamDiag.py", line 1028, in create_plots

    function_caller(plot_func_name, plot_func_args, func_kwargs=plot_func_kwargs, module_name=plot_func_name+'.py')

  File "/glade/campaign/cgd/amp/jcaron/python/CAM_diagnostics/lib/CamDiag.py", line 175, in function_caller

    return func(*func_args, **func_kwargs)

  File "/glade/campaign/cgd/amp/jcaron/python/CAM_diagnostics/lib/../scripts/plotting/zonal_mean.py", line 183, in zonal_mean

    oseasons[s], ops_season, ohya, ohyb)

  File "/glade/campaign/cgd/amp/jcaron/python/CAM_diagnostics/lib/plotting_functions.py", line 330, in plot_zonal_mean_and_save

    diffnorm = normfunc(vmin=np.min(diff), vcenter=0.0, vmax=np.max(diff))

  File "/glade/u/apps/dav/opt/python/3.7.9/gnu/9.1.0/pkg-library/20201220/lib/python3.7/site-packages/matplotlib/colors.py", line 1136, in __init__

    raise ValueError('vmin, vcenter, and vmax must be in '

ValueError: vmin, vcenter, and vmax must be in ascending order

This is very likely a bug, and thus should be fixed accordingly.

Ah! This is raising a ValueError because min(diff) > 0. I thought I had put in logic to catch that case. In the absence of using some kind of default color levels, there are a couple options. To keep using the diverging colormap, I would recommend just making vmin=min(min(diff),-1*max(diff)); i.e., just a symmetric colormap, and the lower half won't be used in the plot.

Great, thanks for finding the fix @brianpm!  I can include this fix in my own development work, unless you or @bitterbark want to take a stab at it?


Tried to optimize annotation fetching

Motivation and context

How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have added a description of my changes into the CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (see GitHub docs)
[ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

@bsekachev , can we pack all your changes into https://www.django-rest-framework.org/api-guide/serializers/#baseserializer? Inherit LabeledShapeSeiralizer from BaseSerializer and implement all logic here? Will it work?


Need scala classes generated with recent scala/java versions

Hi,
Looks like Scala version is used in this project is 2.11. There are recent versions like 2.12 and 2.13.
Also, Scala 2.12 onwards requires java 1.8 or later.

Superseded by #1199


Parsed and unparsed uri is not a same

Example:
$source_uri = '/?#';
$parsed_uri = Zend\Uri\UriFactory::factory($source_uri, 'http');
$unparsed_uri = $parsed_uri->toString();
echo $unparsed_uri; // we see '/', but must be same as source uri
It's because in Zend\Uri::toString() only host check on null. Can you fix it, please, and add check on null with other uri components? It will be more right behavior of this method.

The query string and anchor are empty so there is no reason to put the '?' and '#' characters in the $unparsed_uri

This repository has been closed and moved to laminas/laminas-uri; a new issue has been opened at https://github.com/laminas/laminas-uri/issues/6.


[BugFix] should return early if submit completed/aborted transaction

Fixes #issue
this problem frequently occurr in Flink scenarios: flink process the data source and then sink to multiple starrocks table, for some reason，the job is interrupted and restart to recover, some completed transaction will be committed again. If the fe restart will discard the transcation info,  will cause some exception. we should better process this case in fe side.

[FE PR Coverage Check]
:disappointed: fail : 0 / 17 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/http/rest/TransactionLoadAction.java
0
17
00.00%
[162, 181, 183, 184, 185, 187, 188, 189, 190, 191, 193, 194, 195, 197, 198, 199, 200]

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


Problem with interstitial ads in version 0.6.0. The ad starts. I close it. But it remains as a separate application in multitask.

Most likely, this happened due to changes in the SDK of the latest version.
SDK has banned advertising outside of the main thread (which react-native does by default).
I made a wrapper so that the ads run in the main thread.
Perhaps a similar wrapper should be added here

Спасибо за быстрый ответ! Но я не понял какую именно обертку я должен написать? Не планируете ли вы написать патч этой баги? Очень надо.)


entity.assign(...) crash with combo of managed entities

Describe the bug
assigning a managed, freshly created, entity to another managed, freshly created, entity via entity.assign (inherited from BaseEntity) crash with an error message saying the entity is not managed.
error message says:
To use assign() on not managed entities, explicitly provide EM instance: wrap(entity).assign(data, { em: orm.em })
Assigning it via em.assign works.
entity.assign
minimal repro:
https://stackblitz.com/edit/mikro-orm-repro-mcfbsu?file=test.ts
@Entity()
export class Foo {
  @PrimaryKey()
  id!: number;
}

@Entity()
export class User extends BaseEntity<User, 'id'> {
  @PrimaryKey()
  id!: number;

  @ManyToOne(() => Foo) // you can specify type manually as a callback
  foo!: Foo;
}

orm = await MikroORM.init({
  type: 'sqlite',
  dbName: ':memory:',
  entities: [User],
  persistOnCreate: true, // 👈 persist on create
});

test('assign via em.assign', async () => {
  const em = orm.em.fork();
  const user = em.create(User, {}, { managed: true, persist: true }); // 👈 managed: true
  const foo = em.create(Foo, {}, { managed: true, persist: true }); // 👈 managed: true
  // vvvv DIFFERENCE HERE
  em.assign(user, { foo }); // 🟢 WORKS
  expect(user.foo).toBe(foo);
});

test('assign via BaseEntity.assign()', async () => {
  const em = orm.em.fork();
  const user = em.create(User, {}, { managed: true, persist: true }); // 👈 managed: true
  const foo = em.create(Foo, {}, { managed: true, persist: true }); // 👈 managed: true
  // vvvv DIFFERENCE HERE
  user.assign({ foo }); // 🔴 CRASH
  expect(user.foo).toBe(foo);
});

Dependency
Version

node
v16.14.2

typescript
Version 4.8.3

mikro-orm
5.4.2

your-driver
Postgres

not shown in the minimal repro: entity.assign works well for anything else other than an other freshly created entity.
assigning any scalars via entity.assign() work well. assigning an other entity fetched also works.

managed: true does not mean the entity will become managed automatically (yes, weird naming) - this basically controls the constructor usage, as for managed entities we dont call constructors and rather build the instance via Object.create().
This is documented in the em.create() jsdoc:

Creates new instance of given entity and populates it with given data.
The entity constructor will be used unless you provide { managed: true } in the options parameter.
The constructor will be given parameters based on the defined constructor of the entity. If the constructor
parameter matches a property name, its value will be extracted from data. If no matching property exists,
the whole data parameter will be passed. This means we can also define constructor(data: Partial<T>) and
em.create() will pass the data into it (unless we have a property named data too).

That persist: true is also wrong assumtion - you dont need to persist it, you need to merge it.
const em = orm.em.fork();
const user = em.create(User, {}, { managed: true, persist: true }); // 👈 managed: true
const foo = em.create(Foo, {}, { managed: true, persist: true }); // 👈 managed: true
user.assign({ foo });
expect(user.foo).toBe(foo);

thanks a lot for the quick answer ! 🙏
(I don't know if you plan to do something in the code or in the docs, so I'll leave this open and let you close it when you want)

Btw technically all you need to do to create managed entity instance is em.merge(User, { ... }), as it accepts POJOs too this way.
Note that in your repro you create managed entity without providing any data. That itself doesnt make any sense - managed entity needs to have at least the primary key (plus any other non-null value).

Btw technically all you need to do to create managed entity instance is em.merge(User, { ... }), as it accepts POJOs too this way.

thanks for the tip !

Note that in your repro you create managed entity without providing any data. That itself doesnt make any sense - managed entity needs to have at least the primary key (plus any other non-null value).

yeah, sorry for the too-minimal repro, in my project, those entities are indeed both created with primary keys

what I am missing, why can't A.assign({ message: B }) just work by default ?

Because none of those entities are managed = they dont have the reference to the EM. And I kinda doubt this is actually happening, the EM will be required only if you try to work with FKs instead of entities, e.g. assign({ rel: 1 }) and not assign({ rel: new Rel() }).

em.merge(B) is not really an option, as it leads to B not being persisted, since merge reset the diff

What you apparently failed to understand is what em.merge() is for. It makes entity managed, just like if it was loaded from database = after that call, there cant be any queries done by flush, as it saves the snapshot. You need to merge the entity, and modify/mutate its state afterwards - those changes will be respected during flush.
Maybe first try to explain what this snippet should be actually doing, as I have no idea. What queries do you want to achieve in the end?
Also note that assign was never really meant to be used for new entities, you should just use em.create(), it works out of box with complex inputs and builds the entity graph for you.
// this will create new user entity, that has 3 relation properties, all of them using FK, so they are considered as existing entities
const e = em.create(User, {
  mother: 123,
  father: 321,
  books: [1, 2, 3],
});

Lastly, dont use the string signatures (dont use string name of entity class), your snippet is not type safe because of it.

@B4nan

I kinda doubt this is actually happening, the EM will be required only if you try to work with FKs instead of entities, e.g. assign({ rel: 1 }) and not assign({ rel: new Rel() }).

here is a super tiny repro showing it happening: https://stackblitz.com/edit/mikro-orm-repro-mcfbsu?file=test.ts

Because none of those entities are managed = they dont have the reference to the EM.

Is there a way for me to ensure all of my non-managed entities to hold a reference to EM ? I will always create them with em.getRepository(...)create() without having to implement custom repositories ?; I didn't ponder much on the manged vs un-managed debate; I just want em.create to use their constructor so I can assign default values.  My use-case is simple, I fork Em only once at the script start, then em.create entities, send them around, and sometimes assign them params, then at the very end of the script, I flush the em

What you apparently failed to understand is what em.merge() is for. It makes entity managed, just like if it was loaded from database = after that call, there cant be any queries done by flush, as it saves the snapshot. You need to merge the entity, and modify/mutate its state afterwards - those changes will be respected during flush.

👍

Maybe first try to explain what this snippet should be actually doing, as I have no idea. What queries do you want to achieve in the end?

I just hope to be able to assign several times and the expected final query to be an insert that sets all the accumulated diffs done with successive assign.
foo  = em.create(...)
foo.assign({a:1})
foo.assign({b:2})
// more stuff...
bar = em.create(...)
foo.assign({bar})

=>
insert into bar (id) values('b7a1cdbe-8064-439b-a5b5-2d226bea6d5f')
insert into foo (a,b,bar_id) values (1,2,'b7a1cdbe-8064-439b-a5b5-2d226bea6d5f')

Also note that assign was never really meant to be used for new entities, you should just use em.create(), it works out of box with complex inputs and builds the entity graph for you.

yes, I love how assign just works, that's why I was hoping I could just use-it several time successively on newly created instances before actually flushing the transaction.

Is there a way for me to ensure all of my non-managed entities to hold a reference to EM ?

That is a definition of managed entity - that it holds the EM. Non-managed entity = no reference to EM.
I feel like you are not understanding our discussion. I told you how em.create() works with the managed: true, and that you need to call em.merge() on that to actually make it managed. And I closed this issue with a commit, that automatically does that. If you update the ORM to latest dev version, your repro is not failing with that error anymore, as the em.merge() is called automatically. The test still fails, because you clearly still expect wrong outcome of this - if you create managed entity, it means the entity has to be already present in the database - that will never produce any insert query.
Adding both managed: true and persist: true is again misunderstanding of the concepts. Only not managed entities (those you want to produce insert statements) need to be persisted. Persisting managed entity is a no-op.

// user.assign({ car: M.wrap(car).toReference() }); // ALT 4: 🔴 CRASH

You are not using reference wrapper there, this makes no sense either. Feels like you just try different snippets you find in various places, without really understanding the options you are using :]
I feel like you keep talking about several use cases at once. If you want to see insert queries, you cant create managed entities. And you cant use assign for what you want on not managed entities. But you try to make them managed and expect things to start working - and there is the fundamental misconception, if the entity is not already present in database, you cant just create a managed instance of it.
But I can also see that it does not behave exactly as expected, the user.assign({ car }) fails if both entities are not managed, while it should fail only in case you do user.assign({ car: 123 }). Will try to fix that during the day.

@B4nan Argh ! 🤦 🤦
My latest stackblitz was full of copy-pasta glitches, I didn't mean to write things like managed: true 🤦
I also already use "@mikro-orm/core": "5.4.3-dev.46" in my personal project.
The reference wrapper was also a copy-pasta error; 🤦  I use those wrapped refs in my project, but indeed does not in this stackblitz repro case

Point A: managed: all clear now.
speaking about managed entities was wrong. I don't need to create managed entities.  Managed are for those that are already persisted; those fetched in the DB. I'll probably never or almost never need to em.create(...,{managed:true}). Usually, when I use create, I'll want sql to be emited when I'll flush. The fact that constructor is not called for managed entities also makes sense. all good.
Point B: what I wanted to say

But I can also see that it does not behave exactly as expected, the user.assign({ car }) fails if both entities are not managed, while it should fail only in case you do user.assign({ car: 123 }). Will try to fix that during the day.

yes, that's what I was trying to say;
my whole question should have been :
** how can I make this seemingly natural piece of code to work **
// Bar : {id: string}
// Foo: { id:string, a?: number, b?: number, bar?: Bar}

foo  = em.create(Foo, {id:'foo-1'})
foo.assign({a:1})
foo.assign({b:2})
bar = em.create(Bar, {id : 'bar-1'})
foo.assign({bar}) // 🔴
em.flush()

// insert into bar (id) values('bar-1')
// insert into foo (id, a, b, bar_id) values ('foo-1', 1, 2, 'bar-1')

The whole issue was juste about that x)
🙏 sincere thanks for you time !

ok, this should do it, the validation was indeed too strict. also found another bug in the assigning to collections.

Amazing. thanks!


[Microsoft Teams][AdaptiveCard] Enable file upload through Adaptive Card

What platform is your feature request related to? (Delete other platforms).

[ ] Microsoft Teams

Is your feature request related to a problem? Please describe.
the chat bot is becoming the interface between Human and backend systems. but currently we cannot upload images like invoice picture to the bot, which limit the bot functionality.
Describe the solution you'd like
We are looking for the feature in the adaptive card to get files or images from users when they talk with chat bot.
Describe alternatives you've considered
they only we we can do now is to manually upload the invoice images to the system without bot support.

Hi team,
I want to integrate the File upload option in adaptive cards. Can someone guide me on how to do that?
Its urgent requiremnt.
Regards,
Kamaraj.P

Hi Team,
I want to attach or upload the file to my adaptive card. Can you suggest to me the possibilities?
Regards,
Kamaraj.P

Reference

Hi Team,
I want to attach or upload the file to my adaptive card. Can you suggest to me the possibilities?
Regards,
Kamaraj.P

Is there Any Update now for uploading file from adaptive card ?


Add listener level access logs

We should add an access log filter on listeners. This allows us to capture things like:

no filter chains matched
Listener filter failure (ie protocol sniffing) (blocked by https://github.com/envoyproxy/envoy/issues/12809)

Consensus in WG: add the access log, with the same format as current. In parallel, we will work on getting listener filter failures. Requirement: must have no duplicate access logs.
Prototype: https://github.com/howardjohn/istio/pull/new/logs/listener-level-access-logs

Listener filter error capture should be fixed with https://github.com/envoyproxy/envoy/pull/12935.
We should validate that Wasm supports listener-level access logging  (@jplevyak).

I think this is fiexed.


Fix UUID byte-order in serialization

I can't submit this, since I don't have write access. Would one of you mind doing so? Thanks


feat(ses): Expand TypeScript coverage for Compartment and lockdown

This change includes Compartment and lockdown in the SES shim’s exported types and generally extends the reach of TypeScript verification into SES sources. This change uses the expedient of reexporting the return types of functions that are checked by yarn tsc:lint which may not be sufficient. In a subsequent change, it will likely be necessary to convert the Compartment and lockdown types into interface definitions that are imported by the sources and also exported by index.d.ts.

I'll review this when tests pass.  Feel free to ping me when ready.


Add scopes params

Added scopes params to makeRequest call.
Commited IDEWorkspaceChecks according to this answer - https://stackoverflow.com/a/49564624
Fixes https://github.com/blockstack/blockstack-ios/issues/47

@alvesjtiago we merge into develop, then into master with every release. But develop will get this change very soon as I am sending a PR out that includes this fix. Thank you!


Sequenced containers within a single pod

Summary
Similar to how Tekton does it:
https://github.com/tektoncd/pipeline/tree/master/cmd/entrypoint

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Merged into #2551

Merged into #2551


Resources not found during linkage

I have this kind of error when trying to sync project after adding implementation of your lib.
Android resource linking failed
Output:
.../app/build/intermediates/incremental/mergeDebugResources/merged.dir/values-v28/values-v28.xml:7: error: resource android:attr/dialogCornerRadius not found.

.../app/build/intermediates/incremental/mergeDebugResources/merged.dir/values-v28/values-v28.xml:11: error: resource android:attr/dialogCornerRadius not found.

.../app/build/intermediates/incremental/mergeDebugResources/merged.dir/values/values.xml:910: error: resource android:attr/fontVariationSettings not found.

.../app/build/intermediates/incremental/mergeDebugResources/merged.dir/values/values.xml:910: error: resource android:attr/ttcIndex not found.
error: failed linking references.

May be it's because of conflicts with another libs. I can send you a whole gradle file i you will need it

The latest version 1.1.0 has been migrated to AndroidX. I suspect that may cause you the problem
Please try this version implementation 'com.muddzdev:pixelshot:1.0.0'
The only difference between the two version is the AndroidX migration and some implementation of Exceptions

@RomanAnchugov Great!
How are you using the library? which usecase?

I've just tested it. It works perfectly. Great lib


fix: token naming

What
I updated the token names because variables like spaces and corners with sizes that started with 0 like 025, 050, and 075  are not correctly "found" by the square bracket notation.
This change was also reported in the Figma version to avoid losing this change with the next updates.
Fixes #68

i think that we can also remove this code if now the token do not have the initial 0..
that code probably solve the type isuee, but add this ui error.


Implement batching of reading and writing when using datagram with io…

…_uring.
Motivation:
io_uring does not support recvmmsg / sendmmsg directly and so we need to
"emulate" it by submitting multiple IORING_IO_RECVMSG /
IORING_IO_SENDMSG calls.
Modifications:

Allow to issue multiple write / read calls at once no matter what
concrete AbstractIOUringChannel subclass it is
Add support for batching recvmsg / sendmsg when using
IOUringDatagramChannel

Result:
Better performance

If I wanna write only 1 packet, does it call multiple times?

Nope

Related feature request:
<EMAIL_ADDRESS>

Rebased this one... let me merge it now :)


Add support for ForeFlight format

Support for ForeFlight format
Implements #40. Enjoy!
So, here comes the basic support for the ForeFlight format. I've tried to break it down into atomic commits so that it's easier for you to understand and review, but I haven't ensured that each one compiles separately, that would just be way too much work.
I started testing it by converting the books, which seemed too painful on the iPad, and found some minor problems that I fixed in follow-up commits instead of squashing everything, just to give you an idea of the issues. Maybe with more testing I'll find something else, but for now it seems to work pretty well.
Below are some points for consideration and perhaps discussion.
New fields added to the models
I've added description to your metadata model, because I couldn't find a sensible way to map it.
I've also added type to categories for the reasons discussed in #40:
ForeFlight has 3 predefined categories, and your categories are what they call subcategories. So either we need a more nested structure, or we need to flatten it somehow. My idea was to flatten it by mapping ForeFlight categories to category types.
Which brings us to the next point:
Support for category types
I made sure they are ignored by default. What is missing is:

Ability to select type when creating a new category
Ability to change the type of an existing category
Unknown category type is not displayed (on purpose)

So currently you have to start with a ForeFlight checklist to be able to create one. My understanding is that asking for more properties would require a proper modal dialog. Not sure what you think. Would you like to help with this?
Possible future refactorings
I noticed that the list of supported formats and their properties are currently scattered all over the application. It would be nice to create an Enum to centralize this.
Unfortunately, TypeScript doesn't seem to have object-based enums like Python, but they can be type-safe emulated with some minimal trickery: https://stackoverflow.com/a/50224786/5132088 .

Ha-ha, got bit by my own linter :) Fixed the CI!

This is amazing, thank you so much for the PR!!
A few comments, but nothing major.

Hmmm something else is not right - I tried to export my plane's checklists as FMD with this code, and it gave me a 560-byte file which was empty :/
Original file: N425RP.json
Written contents:
{
  "type": "checklist",
  "payload": {
    "objectId": "42eb846306a4322f1009a839e52c89a2",
    "schemaVersion": "1.0",
    "metadata": {
      "name": "N425RP",
      "tailNumber": "N425RP"
    },
    "groups": [
      {
        "objectId": "433d476f7f529883ea5f472a462232ae",
        "groupType": "normal"
      },
      {
        "objectId": "1abc3aa6d3370b49caa08f3cba183001",
        "groupType": "abnormal"
      },
      {
        "objectId": "d04a8f7cab143b404aa5209beae25749",
        "groupType": "emergency"
      }
    ]
  }
}

Original file: N425RP.json

I can't believe it, but apparently it wasn't possible to import the native format before, so I implemented it in d6f7b58. I hope you don't mind.

Hmmm something else is not right - I tried to export my plane's checklists as FMD with this code, and it gave me a 560-byte file which was empty :/

This was expected with my original implementation which decoupled EFIS categories from ForeFlight groups. I added the UNKNOWN (default) category to EFIS to make sure nothing changes for other formats, and the UI for changing the category type is still missing. So you could only create non-empty FF checklists starting from an existing FF checklist. I noted this in the PR, but since I'm more on the verbose side of things, that mention got lost in the stream of text.
It seems that it's okay for you to infest your model with FF group types, so I think UNKNOWN doesn't add any value under these circumstances, and tends to cause confusion like we just witnessed. In the new implementation, this should "just work" (tm)

Original file: N425RP.json

I can't believe it, but apparently it wasn't possible to import the native format before, so I implemented it in d6f7b58. I hope you don't mind.

Good catch, thanks for adding that! I cherrypicked that change in since it's unrelated to Foreflight.

Hmmm something else is not right - I tried to export my plane's checklists as FMD with this code, and it gave me a 560-byte file which was empty :/

This was expected with my original implementation which decoupled EFIS categories from ForeFlight groups. I added the UNKNOWN (default) category to EFIS to make sure nothing changes for other formats, and the UI for changing the category type is still missing. So you could only create non-empty FF checklists starting from an existing FF checklist. I noted this in the PR, but since I'm more on the verbose side of things, that mention got lost in the stream of text.
It seems that it's okay for you to infest your model with FF group types, so I think UNKNOWN doesn't add any value under these circumstances, and tends to cause confusion like we just witnessed. In the new implementation, this should "just work" (tm)

Thanks. I tested again with my checklist and it looks like it's exporting properly now! :) I like the dropdown for selecting group type.
There was one bug I found - I have this checklist section:

that got translated to:
...
{
  "objectId": "df137d3b4a674c7a80ed796dd845fbf9",
  "title": "O2 mode",
  "detail": "N(IGHT) OR D(AY)",
  "note": "(D)ay / (D)elayed mode turns on at 7,000ft MSL"
},
{
  "objectId": "8888b1738581482a92f3468574418a00",
  "title": "O2 auto-on (if desired)",
  "detail": "HOLD CLR/OFF TO TURN OFF, HOLD MODE FOR AUTO-ON",
  "note": "Auto-on turns on at 10,000ft"
},
...

so the "NOTE: (N)ight / (N)ow mode turns on immediately" entry got dropped completely. I guess consecutive notes like this could just be all joined together into the notes field? Need to see if Foreflight can deal with a multi-line note.
(but also feel free to finish this PR first and we can both do refinements like this afterwards, if you want)

It seems that it's okay for you to infest your model with FF group types, so I think UNKNOWN doesn't add any value under these circumstances, and tends to cause confusion like we just witnessed. In the new implementation, this should "just work" (tm)

As the next logical step in making categories a first-class citizen in your internal representation, I've implemented not only display, but also editing in 070d938. Not super proud of the code, but surprisingly it looks and works OK. I'd be interested in your thoughts on this:
Do you want to use the categories for other formats? I assume they don't support that. Are you otherwise okay with them getting lost on export for formats that can't display them?

Yes I'm fine with that - my principle in general is that no text should ever get dropped (since that'd mean someone may end up skipping an important checklist item), but that formatting/metadata can be dropped to adapt to the various formats. Does that sound reasonable?

Good catch, thanks for adding that! I cherrypicked that change in since it's unrelated to Foreflight.

Thanks, it will then be gone when I do the final rebase!

There was one bug I found - I have this checklist section

Well, sorry, that was a kind of known artifact of not supporting multiline notes, and those in turn couldn't be supported until I mapped all items to ForeFlight concepts. This should be fixed now.
I've done some cursory testing, and your checklist generally looks good, but there are some ForeFlight specifics to consider. There's a lot of space between headings, so extra spacing isn't really needed. And it has a tendency to collapse long notes, so you will have to adjust according to your desired display device.

Yes I'm fine with that - my principle in general is that no text should ever get dropped (since that'd mean someone may end up skipping an important checklist item), but that formatting/metadata can be dropped to adapt to the various formats. Does that sound reasonable?

Absolutely! I've now tried to map everything that makes sense to the ForeFlight concepts, and the only things that can get lost now should be indentation and centering. The rest should be reliably recoverable. I've tried to come up with a checklist for what's left, and I think we're getting closer! If you don't want to do the categories for other formats, I'll cross them out.

If you don't want to do the categories for other formats, I'll cross them out

It's not obvious to me how we would, so let's start without that?
(some formats don't even support groups, and I'm already taking liberties to adapt to that by only adding a group name to the checklist name after the first group - I don't think that adding the category to the checklist title for those would help at all).

Only very minor comments left - so looks like this is almost ready to merge? :) (am I forgetting anything that's still left?)
Once you think it's ready please rebase to the latest main (looks like there's some trivial conflicts to resolve) and let me know.

It's not obvious to me how we would, so let's start without that?

Agreed!

Only very minor comments left - so looks like this is almost ready to merge? :)

Looks pretty good to me now, let me know if the latest changes are ok and I will do a rebase!

let me know if the latest changes are ok and I will do a rebase

Go for it!
Thanks again for this large contribution.

let me know if the latest changes are ok and I will do a rebase

Go for it! Thanks again for this large contribution.

The pleasure is all mine! 👍


Setting of odbc_dm needed on 64-bit Windows with 64-bit Oracle

As requested in the Known Issues section of the README, this issue is being opened due to a need to use const odbc_dm = "C:\\Windows\\System32\\odbc32.dll" when connecting to a 64-bit Oracle database running on a 64-bit Windows 10 preview OS image.
As shown in the attached screenshot:  connecting successfully required two steps to be performed.  The setting of const odbc_dm needed to be performed before executing using ODBC, and a System DSN entry for the database of interest needed to be added as a 64-bit ODBC data source.  The second step is independent of Julia but might be helpful to add to the documentation of this package for use on Windows.
The second attached screenshot shows the error message received when performing a query against the same database if the const odbc_dm = "C:\\Windows\\System32\\odbc32.dll" is not performed prior to using ODBC.  The same System DSN entry is present on this system with this second screenshot.

Hmmmm.....this seems odd. It should be picking up odbc32.dll automatically. I'm working on an overhaul, so I'd appreciate it you could test changes as they get pushed.

Any chance it is currently picking up C:\Windows\SysWOW64\odbc32.dll by default (instead of C:\Windows\System32\odbc32.dll) when on a 64-bit machine?
And, yes, I will test any changes that you make.

hey @AndyGreenwell, I know this is like a year late, but if you'd be willing ot try latest master, I've finally merged the overhaul. Let me know if you're still seeing issues here.

I'll need to recreate that test environment, but yes I will perform this test as soon as feasible.

Great. And let me know if you see any other issues. I have test environments set up on my end currently for MySQL, Teradata, and SQL Server, with PostgreSQL and Oracle coming soon.

Using the current ODBC.jl master with the new usage instructions, I can confirm that one can execute successfully the example query in the above screenshots without needing to set const odbc_dm prior to the execution of using ODBC when connecting to a 64-bit Oracle installation's DSN running on 64-bit Windows with 64-bit Julia.

Great news. Thanks for checking this out @AndyGreenwell. Do let me know if you run into any other issues on the new ODBC release or if there are any big features that would be helpful for you.


Readline should honor inputrc

# /etc/inputrc - global inputrc for libreadline
# See readline(3readline) and `info readline' for more information.

FWIW, the current key bindings can be returned via the bash builtin bind -p.

I still think that this feature makes perfect sense :+1: However, there are currently no immediate plans to build this from my end (no demand at the moment and more important outstanding issues currently), but I would be really happy to accept PRs :+1:
(If you need this for a commercial project and you want a quote, please check out my profile and send me an email)
I'd like to focus on getting the next release out and believe this has been answered already, so I'm closing this for now. :shipit:


Add support for R11F_G11F_B10F, and/or fix IBL instructions in Sandcastle

In the Image-Based Lighting Sandcastle Demo, there are comments recommending how to create a .ktx file for use as an HDRI lighting environment.  The instructions recommend downloading Google Filament and using their cmgen tool (from the bin folder).
So I tried that with Filament 1.8.1 on a free HDRI called Symmetrical Garden (from HDRI Haven), and the result is this KTX file:
symmetrical_garden_1k_ibl.zip
The KTX file came out of Filament with a pixel format of R11F_G11F_B10F (35898), which is not supported in Cesium.
Can support for this pixel format be added?  (I tried naively adding the format to the supported list, but clearly it takes a little more than that to get it working).

Worth noting that the old cmgen, at the time this demo was first published, had this note in the command-line help message:

   KTX files are always encoded with 4-channel RGBM data

But the latest cmgen has this note instead:

   KTX files are always encoded with 3-channel RGB_10_11_11_REV data

@YoussefV you ran into something similar right? I know there were a few open threads about Filament, the KTX1->KTX2 converter, and CesiumJS. Where did we settle on those?
CC https://github.com/CesiumGS/cesium/pull/9040

Yep, so for R11F_G11F_B10F pixel formats, you can use the WebGLConstants.R11F_G11F_B10F for the format of the image. The IBL sandcastle instructions didn't work for me either when i tried converting the kiara environment map to .ktx2, so I had to basically rewrite the original .ktx binary.


MetroWindow as a pure Window Style

Is your feature request related to a problem? Please describe.
I want to use Mahapps.Metro for styling my app.
This is unique situation where, the app is composed of vairous WPF User Control class libraries.
Our firm uses a custom bootstrapper to launch these components.
It automatically creates a shell window for the app and host's the views inside it.
I cannot touch the bootstrapper in anyway.
Describe the solution you'd like
What I want is a standalone Window style, which targets a Window object.
I just need the basic MetroWindow style like window tile bar along with min, max & close buttons.

@ironhide91 This is currently not possible. The MetroWindow does many code behind action which is not possible to do only with a style.


Ungroup items on the Taskbar in Windows 11

Description of the new feature / enhancement
Ability to ungroup items on the Taskbar in Windows 11.
Scenario when this would be used?
navigate to different windows with a single click.
Supporting information
https://techcommunity.microsoft.com/t5/windows-11/ungroup-items-on-the-taskbar-in-windows-11/m-p/2585176

This would be sure helpful!!

great feedback, best spot for this is Windows feedback hub


Update dependencies

Armeria 0.55.1 -> 0.56.0
JSON unit 1.25.1 -> 1.27.0
Hibernate Validator 6.0.5 -> 6.0.7
Mockito 2.12.0 -> 2.13.0
Spring Boot 1.5.8 -> 1.5.9

Codecov Report

Merging #114 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #114      +/-   ##
==========================================
- Coverage    61.1%   61.09%   -0.02%
==========================================
  Files         254      254
  Lines        8678     8678
  Branches     1005     1005
==========================================
- Hits         5303     5302       -1
- Misses       2759     2760       +1
  Partials      616      616

Impacted Files
Coverage Δ

...erver/internal/mirror/DefaultMirroringService.java
62.02% <0%> (-1.27%)
:arrow_down:

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 49fa7be...09faa75. Read the comment docs.


Add support for RDS option group

What resource do you need?

RDS option group
What is your use case?

It's a basic feature of RDS which I was surprised to find out isn't supported yet by the provider.
Would you be willing to contribute it using code generator?
Yes.

Is possible via Code-Generator https://github.com/crossplane-contrib/provider-aws/blob/master/apis/rds/generator-config.yaml#L69 you can try it out ;)


cache downloaded images for faster loading, remote work

Would it be possible to cache images and/or ROI's on the local computer so that image sets would load faster and working remotely would be more feasible?
If so, if the cache directory was a known location the user could manage that manually so it doesn't eventually fill up the hard drive.
It would be fantastic to load up several dives while onsite, then work with those offsite using VPN so that db changes are stored but images are local. This is what we do when working offsite with VARS.

I'll target parallel downloads in the interim to hopefully speed up the loading process.
When I get to caching, I will add a setting for the cache location that defaults to an appropriate location in your filesystem (e.g. /Users/username/Library/Caches/VARS GridView on macOS). I'll also add a cache size setting.
We should be very careful about caching (specifically, cache invalidation) as we are working on getting the video framegrab timing correct. For example, if we were to change the way Beholder grabs frames, we would need to invalidate any framegrabs that were cached prior to that change.


Copy attention based decoder

You guys really did an excellent work with high scalability. Better than OpenNMT in my opinion :)
Copy mechanism could greatly enhance the performance of Seq2Seq model, would you guys implement a decoder with copy mechanism?

@AtmaHou we'll see if it can be integrated in the next release. You're welcome to submit a PR. We need all the help we can get.

Thanks for your reply, it will be in great need.

Any Update on this?

@varunAI Yup working on it. Will push to develop as soon as it's done.

@pskrunner14 Any news on this ?

@Diego999 no, I'm facing some issues with dimensions as mentioned and there seems to be a problem with the dynamic dictionary too. I'll get to this asap. Will post any updates on this thread.

@pskrunner14 Thank you for your quick answer !


fix: limit numpy version to fix ReadTheDocs build

Closes #681
This PR limits the numpy version to <0.1.24 to make it compatible with numba==0.56.4.
Moreover, it adds a couple of steps to the continuous integrations to run the test suite with the latest dependencies versions.
Please, let me know your thoughts on this :D

Running pytest upgrading the dependencies I found another error:
 ERROR  - ImportError: cannot import name 'validate_email_deliverability' from 'email_validator' (/opt/hostedtoolcache/Python/3.9.16/x64/lib/python3.9/site-packages/email_validator/__init__.py)

You could also split the hotfix from the CI feature, if you want.

On checking if we still support the latest versions of dependencies (the upgrade case) only once per PR:
I see that we mostly run every action twice as we specify on: ["push", "pull_request"]. The latter contains many events in the PR's life, but they should only be executed when we open the PR:
By default, a workflow only runs when a pull_request event's activity type is opened, synchronize, or reopened.

However, as I'm checking a few PRs, this is not what is happening in our case.
We should stop using pull_request in a bare manner here, and try this instead:
on:
  pull_request:
    types: [opened, reopened]

Then, maybe the best approach to use the upgrade variable (or we'll call it test-upgrades-dependencies) by setting its truth value to github.event.action == 'opened'. I didn't find this exact example, so I'm not certain this is how that check should look like ― I read here.
Another interesting example is how to run a job when a PR is approved, but that works a little differently. Just an inspiration.

No changelog entry required imo. If anyone disagrees, feel free to place back the label.

Should this be backported, actually?


No EEPROM data

Have been using this tool for fortus 250mc and dimension series for quite some time .
Now, I was trying to refill a 450mc Chip, I  was able to read and the id is "b3-xxxxxxx" usually it will be "23-xxxxxx" and it doesn't have eeprom in it it has "rw" , when i tried to read rw it is showing " ff ... " only. so i was not able to get the eeprom data copied for editing the material percentage
Is there a way refill the chip?
I am using Rasp pi 3  for refilling the chip

450mc chips use SHA-1 protection, so you will need to know the HMAC secret in order to write back to it with a RasPi.

Is there any possibility that the fortus 250cc Chip working with 450mc ? Any Ideas ?

Is there any possibility that the fortus 250cc Chip working with 450mc ? Any Ideas ?

maybe if you have Fortus 250 tri to swap eeprom reader with 450 if they have same connection. but the main problem is SHA-1 protection.


Use cji_smoke_test instead of smoke_test.sh in pr_check.sh

/retest

/reteste

/retest

It looks like the cji smoketest script is looking for the wrong clowdapp, it's looking for sources-api-go instead of sources-api:
08:49:39 2022-07-11 13:49:39 [   ERROR] [          MainThread] [clowdjobinvocation/sources-api-go] not ready, details: clowdjobinvocation/sources-api-go not ready, status conditions:
08:49:39   - JobInvocationComplete: False (Some Jobs are still incomplete)
08:49:39   - ReconciliationFailed: True (ClowdApp.cloud.redhat.com "sources-api-go" not found)
08:49:39   - ReconciliationSuccessful: False
08:49:39
08:49:39 ERROR: deploy-iqe-cji: hit timeout error: Could not do 'wait for Job to appear owned by CJI 'sources-api-go'' at /srv/volume/jenkins/workspace/RedHatInsights-sources-api-go-pr-check/.bonfire_venv/lib64/python3.6/site-packages/bonfire/openshift.py:204 in time

So it really looks like a lot more tests ran - but a lot of them failed particularly the bulk_create then wait for available ones, which makes sense because we aren't running cloud-meter or cost to tell us the availability status.
I want to merge this - but can't unless we can get it to go green. It's "unstable" right now which still results in red tests.

/retest

I'm actually going to merge this. That way even though the tests will be red the unit/integration tests will still get ran.