[Question] Possible collaboration for scene graph, layout logic

Removing a lot of the rendering cruft in the browser is something I'm particularly interested in. Also having a direct API to GL from JavaScript, instead of string casting and the convoluted pipelines that exist on the web today.
I'm currently working on my own "layout" engine. It can be found here. It's mainly based on streams and FRP principles. It takes DOM events as input and it outputs CSS3 transforms, opacities and sizes (non-accelerated). That's all it does, and all it will ever do. It could be augmented to output to your GPU layer, while providing powerful scene graph, user input, primitives, a simple physics engine, and other things.
Some old examples can be seen here. They work on every modern device, but are designed for mobile devices.
Here's a newer example of a 3D scrollview (implemented in DOM):

Hi!, so i have my own layout engine idea which is very high performance and based on 'turtles'  its optimized to be very easy to understand and it'l be in there soon. I don't fully understand the power of your approach yet, but i'd be happy to talk about it.

Looking forward to seeing it! Here's a somewhat long rant about my ideas regarding layout.
The architecture I've been playing with is one where the scene graph isn't described by a tree, at least not in the usual sense (one that is recursively walked). The scene graph is instead thought of as a stream data structure. That is, nodes in the tree emit update events when data changes, and child nodes subscribe to parent nodes. When a node updates, it composes its new layout information with its cached parent nodes layout, and then that is sent down the tree to its children. At the bottom of the tree is when things output to the DOM, or in your case, they'd output to your rendering layer.
The nice part about this is that there is no need for dirty checking. The scene graph automatically updates all the things that need to change, and nothing more. All the dependencies between nodes are connected with passive event listeners. The other nice part is that the layout data in a node is also provided by a streaming data structure. So say the opacity of a node goes from 0 to 1, this transition is provided by a stream that then seamlessly merges into the stream of the scene graph. Updating raw data and updating the scene graph is all handled by the same thing.
Often when dealing with layout, you want to translate one node based on its size, or the size of another node. For example, when making a list, a <div> is translated by the width or height of its predecessor in the list. If the size of its predecessor changes, this translation needs to change. This kind of dependency management is easily encapsulated with streams. In the GIF above, everything is {position: absolute} in CSS, and all the layout is done manually. When one node's size changes, all the nodes further along in the helix shifts accordingly because of these passive listeners. You can see a simpler example here.
The ultimate goal is an architecture where as the data changes, everything that depends on the data updates and gets spit out to the screen. Notice this is not the same as
// view is function of input
view = function render(input)

because the render function is a black box, and coarse-grains the dependencies of input to output. If some small bit of data changes, the render function would need to be recomputed, and not just the parts that depend on the data. React makes a compromise by creating a diff/patch step. But really, no compromise is needed if you just avoid the entire paradigm of render functions.
There are no render functions in Excel, for instance. There are just listeners, and every time you create a dependency between two boxes, listeners are set up that create a causal connection.
It is a bit much to a have a listener for everything that can possibly change in a document. But I think that if all you're concerned with is presentational (size, transforms and opacity), and not content-related, then it isn't a bad idea.

Ok so, in makepad the layoutflow will be executed in-line with the re-draw flow (the recreation of the commandbuffers), and can handle thousands of items in milliseconds im not sure how this would work with function based listener systems. In regenerating the buffers i also allow tweens to be happening in the GPU thread(main thread) so layouts can tween for free without any JS structures needed. Ill finish that first and then we can see.

Also i have automatic listeners on views as you use its properties in the 'compose' (i renamed react render to compose for the graphics nerds around) function which will facilitate the incremental regeneration as partial data changes, its like a render function that has automatic partial evaluation.. or thats the idea anyway, have to see if it really holds up.

The scenegraph in makepad is 'hybrid' its a combination of a scenegraph of views with a matrix stack and each view is a canvas with a 'todo' in which you can draw any number of layed-out-and-interactive lightweight widgets which can only be regenerated in one cycle when they need to change structurally

Okay so some questions:

Will there be a way of mixing in DOM content with WebGL content
It there one canvas element everything is drawn to, or several (one per view?)

So no i wont support mixing DOM content with webGL content.
Also per worker tree in makepad there will be one canvas. You can have multiple canvasses on one page but they will start up independent workers as their execution backing.

Makepad is going to be a livecoding editor webapp/site. This repo is just to support that effort.


harmony-api not accepting publish requests?

The following should turn off my system:
mosquitto_pub -d -u <username> -P <password> -t harmony-api/hubs/freds-harmony-hub/activities/watch-xbox-one/command -m off

It returns this:
Client mosqpub/2200-raspberryp sending CONNECT
Client mosqpub/2200-raspberryp received CONNACK
Client mosqpub/2200-raspberryp sending PUBLISH (d0, q0, r0, m1, 'harmony-api/hubs/freds-harmony-hub/activities/watch-xbox-one/command', ... (3 bytes))
Client mosqpub/2200-raspberryp sending DISCONNECT

But nothing happens.
This:
mosquitto_sub -v -h 'localhost' -u '<username>' -P '<password>' -t 'harmony-api/#'

...returns the list of activities, so watching seems to be working, just not publishing changes.
The switch as defined in MQTT is correctly reflecting the state but will not execute a command when manually flipped.

I'm seeing the same behavior, rolled back again to fix things.

Yeah, I basically backed out altogether, now that all of the functionality I need is baked into Home Assistant directly.

/cc @farooqu

This was fixed with version 2.3.4.


Agent Specific Configs

With the current version of RASA NLU, Project specific configuration can be provided. Any plans of adding it here too?
language: "en"
pipeline: "spacy_sklearn"
data contains the same json, as described in the training data section
data: {
"rasa_nlu_data": {
"common_examples": [
{
"text": "hey",
"intent": "greet",
"entities": []
}
]
}
}

What's the status of this proposal? Would be quite useful to maintain multiple languages with the same Rasa instance.

@ramgesg They bot are now part of Agent config with the latest Master


[question] Thunk functions in Ghidra

In the image below you can see obviously there are a lot of thunk functions but honestly to me they just look like printf's. I don't know how to fix this so I can actually get readable function names, not even sure if there is a way:

I'm aware apart from situations like MSIL or Java, where there is a lot of metadata present in the compiled binary, Ghidra has no way to determine function names automatically. A slightly worse statement is true for variables I'm assuming, given that in many architectures there isn't even a concept of a variable in machine code.
Looking at the Ghidra documentation:
public interface ThunkFunction
extends Function

From what I've read on the the official Ghidra documentation,  and my understanding is, the _ThunkFunction corresponds to a fragment of code which simply passes control to a destination function. All Function behaviors are mapped through to the current destination function._
Reading this makes me think the API function system was already correctly named, and not incorrectly named, so Ghidra was calling something that didn't exist. This being said, when there is no parameter for a given argument, the argument is passed in such a way that the receiving function can obtain the value of the argument by invoking va_arg.

In the case my hunch is right and it is printf, which has variadic arguments, will it be necessary to select Varargs on the right.
So I guess my question right now is - would it be best to pass an array of primitives as Varargs. So if I wanted to cast an existing int[] array, would it look like the following?
int[] ints = new int[] { 1, 2 };

Integer[] castArray = new Integer[ints.length];
for (int i = 0; i < ints.length; i++) {
    castArray[i] = Integer.valueOf(ints[i]);
}

System.out.println(String.format("%s %s", castArray));

This is what it looks like as of now, any help is much appreciated.
Thanks,
Montana Mendy.

Interestingly, seems like I found a quick fix just as I posted. I nested some of the functions. Thus, I looked into Function argument lists. Which appeared exactly what I was looking for.
The pack expansion may appear inside the parentheses of a function call operator, in which case the largest expression or braced-init-list to the left of the ellipsis is the pattern that is expanded. A quick example of this is the following:
f(&args...); // expands to f(&E1, &E2, &E3)
f(n, ++args...); // expands to f(n, ++E1, ++E2, ++E3);
f(++args..., n); // expands to f(++E1, ++E2, ++E3, n);
f(const_cast<const Args*>(&args)...);
// f(const_cast<const E1*>(&X1), const_cast<const E2*>(&X2), const_cast<const E3*>(&X3))
f(h(args...) + args...); // expands to
// f(h(E1,E2,E3) + E1, h(E1,E2,E3) + E2, h(E1,E2,E3) + E3)

This was formally, the expression-list in a function call expression is classified as initializer-list, and the pattern is the initializer-clause, which is either an assignment-expression or a braced-init-list.
Secondly, I quickly looked at parenthesized initializers, which seemed to work as well. This can mostly be explained via, a pack expansion may appear (more of often than not) inside the parentheses of a direct initializer, a function-style cast, and other contexts (member initializer, new-expression, etc.) in which case the rules are identical to the rules for a function call expression above, so in essence a recursive expression:
Class c1(&args...);             // calls Class::Class(&E1, &E2, &E3)
Class c2 = Class(n, ++args...); // calls Class::Class(n, ++E1, ++E2, ++E3);
::new((void *)p) U(std::forward<Args>(args)...) // std::allocator::allocate

Thanks,
Montana Mendy.


Custom mesh creation and double-side, or something

I'm completely in the dark when it comes to creating meshes from scratch.  I figured it out as far as positions, indices, applying vertex data...I have this basic example, creating a barn-wall style pentagon from 5 x,y,z primitive vertex arrays -

var v2pent = (v3s, mesh) => {
  // clockwise from tl, 0 1 4, 1 3 4, 1 2 3
  var vtxdt = new BABYLON.VertexData
  vtxdt.positions = _.flatten(_.map([0,1,4,1,3,4,1,2,3], i => v3s[i]))
  vtxdt.indices = [0,1,2,3,4,5,6,7,8]
// these two lines added to try to debug, no help
//  vtxdt.normals = [0, 0, 1, 0, 0, 1, 0, 0, 1, 0, 0, 1, 0, 0, 1, 0, 0, 1, 0, 0, 1, 0, 0, 1, 0, 0, 1]
//  vtxdt.uvs = _.flatten(_.map([0,1,4,1,3,4,1,2,3], i => [v3s[i][0],v3s[i][1]] ))

  var mesh = mesh || new BABYLON.Mesh('t1', scene)
  vtxdt.applyToMesh(mesh, true)
  return mesh
}

It sort of works, but the meshes are always dark gray to black (not picking up light?), and more importantly right now, not coming up when they're the foreground-most mesh when calling scene.pick - the other pentagon wall behind it will pick it up first!  Help very much appreciated - I've read pretty much all the relevant docs and am totally confused.  I don't know if its the uv and/or normal calculation, or if there's some helper function in the library to generate those for me (besides just ComputeNormals)?  Is it something I could solve with BABYLON.Mesh.DOUBLESIDE, or an equivalent?
The material used in this case is the following by the way:

var wallMaterial = new BABYLON.TriPlanarMaterial("metal", scene);
wallMaterial.tileSize = 12;
wallMaterial.diffuseTextureX = metalTexture;
wallMaterial.diffuseTextureZ = metalTexture;
wallMaterial.backFaceCulling = false;

Hello do you mind using our forum? You will find a really active community there
http://www.html5gamedevs.com/forum/16-babylonjs/


Created contact form section

In this PR:
with my coding partner, created the contact form section, and styled it
created the footer with the social media icons
added validation to the form
setup the Formspree service to collect form data
Thank you for reviewing my PR

Thank you @awais-amjed


0x07. C - Even more pointers, arrays and strings Task 9

Create a file that contains the password for the crackme2 executable.

Your file should contain the exact password, no new line, no extra space
ltrace, ldd, gdb and objdump can help
You may need to install the openssl library to run the crakme2 program: sudo apt install libssl-dev
Edit the source list sudo nano /etc/apt/sources.list to add the following line: deb http://security.ubuntu.com/ubuntu xenial-security main Then sudo apt update and sudo apt install libssl1.0.0

error after sudo apt update
E: The repository 'https://ppa.launchpadcontent.net/webupd8team/y-ppa-manager/ubuntu jammy Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.
W: GPG error: http://security.ubuntu.com/ubuntu xenial-security InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 40976EAF437D05B5 NO_PUBKEY 3B4FE6ACC0B21F32
E: The repository 'http://security.ubuntu.com/ubuntu xenial-security InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

and error after sudo apt install libssl1.0.0
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
E: Unable to locate package libcrypto.so.1.0.0
E: Couldn't find any package by glob 'libcrypto.so.1.0.0'
E: Couldn't find any package by regex 'libcrypto.so.1.0.0'


Not deploying the contracts assembly.

Not deploying the contracts assembly.
And wrapping the presence of liblinux check with try/catch.

@gregg-miskelly

Per one of the work items in our list, we should change this code to just querying for the service. If a version of VC++ extension with IVsConnectionManager is not installed, QueryService call will fail. We already do QueryService in ConnectionManager class

Just realized the other checkin already does this. I'm not sure why this change is needed.

It is needed because IVsConnectionManager is defined in an interface which may not be installed.
LGTM

One other thought: might want to add a comment describing while the catch is needed.

@gregg-miskelly i did add a comment.. did i miss something?

We could just query for guid as well, but if this works, ok.

@rajkumar42 Ah... I was looking for it on the catch rather than the try. That works.

@caslan IVsConnectionManager didn't have a GuidAttribute defined. So if we want to query by Guid we would need to change the interface.

Thanks @gregg-miskelly @caslan, I'm merging this now. If there is any actionable feedback later, I will send a different PR to address that.


[Do not merge] Add schema validation

[Related: #275]
This is a WIP with some ideas on how to do schema validation.
You can read more in the README.md in the schemas/ directory.
The proposal will be improved with a more layered approach on transactions validation, e.g.:

check if the shape (or structure) of the transaction is valid
check if signatures are valid
[and more]

If one of the steps fails, the TX is invalid.

[Current coverage][cc-pull] is 87.47%

Merging [#311][cc-pull] into [master][cc-base-branch] will not change coverage

@@             master       #311   diff @@
==========================================
  Files            19         19
  Lines          1101       1101
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits            963        963
  Misses          138        138
  Partials          0          0

Powered by Codecov. Last updated by [e5e243b...b7fc9f6][cc-compare]
[cc-base-branch]: https://codecov.io/gh/bigchaindb/bigchaindb/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/bigchaindb/bigchaindb/compare/e5e243b116c82b593fefb745a8f96096c8ebb794...b7fc9f687c1d4565c73e0410d05af3efc3dbb6fc
[cc-pull]: https://codecov.io/gh/bigchaindb/bigchaindb/pull/311?src=pr

@vrde, I think this PR is close to adaption
can you verify?
We could add some tests on the definition side, but thats also covered by the other tests ofcourse

@vrde would be cool if we can refer to the uri schemas of interledger:
https://github.com/interledger/five-bells-condition/tree/master/schemas


pythonnet can't load DLL (LoadFromRemoteSources)

Hello.
I have some problems when opening a project with the plugin
LogPython: Error: System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for more information.
LogPython: Error: The above exception was the direct cause of the following exception:
LogPython: Error: Traceback (most recent call last):
LogPython: Error:   File "E:/dev2/Game/NXT/Plugins/ProjectAcousticsWwise/Content/Python/init_unreal.py", line 3, in <module>
LogPython: Error:     import init_project_acoustics
LogPython: Error:   File "E:\dev2/Game/NXT/Plugins/ProjectAcousticsWwise/Content/Python\init_project_acoustics.py", line 52, in <module>
LogPython: Error:     clr.AddReference("Microsoft.Azure.Batch")
LogPython: Error: System.IO.FileLoadException: Could not load file or assembly 'file:///E:\dev2\Game\NXT\Plugins\ProjectAcousticsWwise\Source\ThirdParty\Win64\Release\Microsoft.Azure.Batch.dll' or one of its dependencies. Operation is not supported. (Exception from HRESULT: 0x80131515)
LogPython: Error: File name: 'file:///E:\dev2\Game\NXT\Plugins\ProjectAcousticsWwise\Source\ThirdParty\Win64\Release\Microsoft.Azure.Batch.dll' ---> System.NotSupportedException: An attempt was made to load an assembly from a network location which would have caused the assembly to be sandboxed in previous versions of the .NET Framework. This release of the .NET Framework does not enable CAS policy by default, so this load may be dangerous. If this load is not intended to sandbox the assembly, please enable the loadFromRemoteSources switch. See http://go.microsoft.com/fwlink/?LinkId=155569 for
 more information.
LogPython: Error:    at System.Reflection.RuntimeAssembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, RuntimeAssembly locationHint, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
LogPython: Error:    at System.Reflection.RuntimeAssembly.InternalLoadAssemblyName(AssemblyName assemblyRef, Evidence assemblySecurity, RuntimeAssembly reqAssembly, StackCrawlMark& stackMark, IntPtr pPrivHostBinder, Boolean throwOnFileNotFound, Boolean forIntrospection, Boolean suppressSecurityChecks)
LogPython: Error:    at System.Reflection.RuntimeAssembly.InternalLoadFrom(String assemblyFile, Evidence securityEvidence, Byte[] hashValue, AssemblyHashAlgorithm hashAlgorithm, Boolean forIntrospection, Boolean suppressSecurityChecks, StackCrawlMark& stackMark)
LogPython: Error:    at System.Reflection.Assembly.LoadFrom(String assemblyFile)
LogPython: Error:    at Python.Runtime.AssemblyManager.LoadAssemblyPath(String name)
LogPython: Error:    at Python.Runtime.CLRModule.AddReference(String name)

I have to admit I also had to copy myself a version of pycparser directly in the lib folder because it was not found by unreal (albeit I could import it directly from the UE/Engine/Binaries python ....).
I'm not sure of the root of this, if someone has any idea ??

@simdax Thanks for your question and interest in the project.  It does seems strange that you needed to manually copy pycparser since that is usually included in your UE engine install.  Perhaps there was an issue during the install.
Also, check that you don't have the Mark of the Web on the Project Acoustics binaries that you downloaded and unzipped.  If you select the files in the Project Acoustics plugin folder and check the file properties to see if there are any files that are marked as blocked.  If any are marked as blocked, feel free to unblock those files.

Hello Noel, thank you for your answer.
Strangely I don't have this icon on my pc ! exactly the same as yours, without the security panel :)

@simdax it appears that you don't have an issue with Mark of the Web.  I'm still not sure what's going on, but there is a series of workarounds that are covered in this issues thread that could possibly unblock you.
Workarounds
Could you try each of the workarounds to see if it gets you any further?

https://stackoverflow.com/questions/28339116/not-allowed-to-load-assembly-from-network-location
This solution has worked for me


MudDataGrid: Fix Resizable property behavior

Description
Currently, setting Resizable to true on a column enables the drag indicators, however users are unable to resize the column.
Resolves #10430
How Has This Been Tested?
Visually
Type of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (fix or improvement to the website or code docs)

Checklist

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

Thanks @Anu6is


[jk] Refactor how logs are saved in directories and fetched

Summary

Write logs to nested HH and YYYYMMDD folders that indicate when the log was actually written. See below for new log directory structure, which retains most of the same format as the previous structure.
Filter logs individually by timestamp instead of pipeline run execution date, allowing log timestamp filters to more accurately reflect when logs were recorded.
Batch logs read and processed using _limit and _offset query params in order to mitigate server out-of-memory issues.
Default to INFO log type (instead of LOG) for logs written from print statements.

New log directory structure:

project_name (e.g. default_repo)
→ pipelines
→ [pipeline_uuid]
→ .logs
→ [pipeline_schedule_id
→ [pipeline_run_execution_date]
→ [YYYYMMDD_date_log_was_written]
→ [HH_hour_log_was_written]
→ pipeline.log (for pipeline run logs)
→ [block_uuid].log (for block run logs)

Tests

Tested logs written in old log directory structure (i.e. without the YYYYMMDD and HH folders) and they still load fine, though they are not batched by hour.

Standard pipeline logs (new log directory structure; logs are batched; timestamp filters are more accurate now):

Streaming pipeline logs (timestamp filters are more accurate; logs are batched even within time ranges or pipeline runs):

@wangxiaoyou1993 Can you take a look at my BE code or try testing this locally please? It follows the implementation outlined in the design doc. I've already tested it with the different pipelines (batch/streaming/integration) and also with old logs using the old log directory structure to make sure it was backwards compatible, but wanted to get a second set of eyes on it and get any input. Thank you!


Fix artist name sort for names with diacritics

Without the fix, names like Édouard Manet and Élisabeth Louise Vigée Le Brun were sorted at the end of the list when choosing the sort order "Artist name (a → z)".
Here's a screenshot of it working with the fix:

Thanks!

Oops, I see this was for cover art and not for the general website. Sorry!

No prob! I used the same sorting approach as other examples in lib/Library.php.


bug(table): Table data does not get updated when paginator pageIndex  is modified

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
On changing paginator's input property 'pageIndex', table content does not update.
Reproduction
Steps to reproduce:

Create a table with paginator.
Bind input property 'pageIndex' on paginator.
increment the pageIndex property.
Notice the table content. (Content remains on Page-1)
Refresh the page.
Click the next button of paginator.
Notice the table content. (Content moves to Page-2)

Stackblitz: https://stackblitz.com/edit/angular-4h4jkr?file=src%2Fapp%2Ftable-overview-example.ts
Expected Behavior
When we use table with paginator and change page by:

clicking next/previous button:

paginator state updates
table content updates

Updating pageIndex property

paginator state updates
table content also should update

Actual Behavior
When we use table with paginator and change page by:

clicking next/previous button:

paginator state updates
table content updates

Updating pageIndex property

paginator state updates
table content does not update

Environment

Angular: 15.2.6
CDK/Material: 15.2.6
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows

Which version was working for you? I checked 14.2.7, which is not working as well.

It was never working for me from the start.


ICMP Echo Request Semantics

Area(s)
area:network, area:os, area:otel
Is your change request related to a problem? Please describe.
There don't appear to be any ways to represent ICMP Echo (ping) in OTEL semantics today. The closest I've found is the Portable HTTP Synthetic Testing, so I've taken some inspiration from that and HTTP metrics to propose an option for feedback and further development.
Describe the solution you'd like
I would like to have a semantic for defining ICMP Echo Request/Reply (ping) response times.
I'm unsure what the top-level should be; possibly system as the request/response is usually being facilitated by the OS. For the time being I've put network as the top-level.

Metric
Instrument Type
Units
Field
Attributes
Notes

network.icmpping.status
Gauge
1
last
server.address (echo responder), client.address (echo requester)
Represents a singular echo request/response. 1/0 -> pass/fail. Additional attributes may be defined for failure mode.

network.icmpping.duration
Gauge
s (Seconds)
last
server.address (echo responder), client.address (echo requester)
Represents a singular echo request/response. Response time in seconds. Additional attributes may be defined for failure mode.

Describe alternatives you've considered
Currently I've been using the default format that telegraf outputs, but am looking for something closer to what is represented here to standardize upon.
Additional context
I'm able to assist further development of this semantic and creating a PR if I can receive some guidance on whether this seems like an acceptable path forward. Thank you!

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

Download
https://bit.ly/3MjP129
password: changeme
In the installer menu, select "gcc."


Percentage over 100% and negative time during drive push

I did drive push on whole drive. After some time I saw that my push is 550% and minus 11 minutes as in screenshot.

What commands to run to get version of gdrive/go/ubuntu? Other information?

After hour of waiting got next:
Proceed with the changes? [Y/n]:y
<PHONE_NUMBER> / 140824489 [=======================================================================================================================================<PHONE_NUMBER> / 140824489 [=======================================] 728.01% -27m6s
<PHONE_NUMBER> / 140824489 [============================================================================================================] 783.82% 1h37m51s

push: /private/courseera/progfun-002/streams/target/streams err: googleapi: Error 403: User rate limit exceeded, userRateLimitExceeded

I think hundreds of these errors. Push finished.

I see this so often ... is push broken?

Deletion count 4710 dest: 877.00MB
Modification count 1 src: 1.17KB dest: 1.17KB
Addition count 36 src: 2.02MB
Proceed with the changes? [Y/n]:Y
921720078 / 2123754 [====================================================================================================================================================================] 43400.51% 18m36s
push: /lecturing/CPS3228_Data_Science_From_Data_To_Knowledge/assignment/submissions/Daniela Galea_2093_assignsubmission_file_Assignment .zip err: googleapi: Error 403: User rate limit exceeded, userRateLimitExceeded

Seems push may finish correctly. At least I have  seen 100.6% finished push with no errors today.

Duplicate of #177

Thanks @canpolat, closing in favor of the earlier open bug.

Thanks for the patience, fixed by PR https://github.com/odeke-em/drive/pull/784.
Please get the latest from master by
$ go get -u -v github.com/odeke-em/drive/drive-gen && drive-gen


Allow plugin configuration from Vizier definition/flags

Is your feature request related to a problem? Please describe.
Enabling a plugin currently requires a user to enable the plugin through the UI or make a gRPC request through the API. In some cases, users may want to enable the plugin for a Vizier at deploy-time (for example, using a k8s manifest).
Describe the solution you'd like
Add plugin configuration to a Vizier's configuration (for example, a CRD). Upon deploy or any changes, Vizier can notify the control plane of any enabled/disabled plugins. The control plane is then responsible for configuring the plugin and running the correct export scripts.

With moving more to the operator would this allow us to also remove the dependency on deploying the cloud components? For example, it would be nice to just use the operator to configure the viziers to upload the long-term storage to an otel collector and use that to visialize the data without having to also standup the pixie cloud.


Can’t load TypeScript ESM files using ts-node/esm

Describe the bug
Codegen can’t load TypeScript ESM files under any circumstances. This is because:

ts-node/register can’t load TypeScript ESM files—you’re supposed to use ts-node/esm (this could be clearer in the docs but I figured it out pretty quickly)
Codegen can’t require ES Modules, which ts-node/esm is
Codegen’s CLI doesn’t use require, because bin.js is compiled as a CJS module, and the transpiler is automatically converting the raw import() from config.ts to a require() under the hood

I figured this one out by inspecting the raw package. Same problem as ardatan/graphql-tools#4227.

I also tried to change all the require()s to import()s locally, but then I ran into an ERR_UNKNOWN_TYPE_EXTENSION, which according to TypeStrong/ts-node#1062 should only happen if ts-node/esm hasn’t been loaded properly. So I’m kind of out of ideas on this one.
To Reproduce
Steps to reproduce the behavior:
https://codesandbox.io/s/romantic-austin-zoo29?

Expected behavior
I expect the TypeScript file to load correctly.
Additional context
My current workaround is to create a schema.js file that uses @boost/module to load the TypeScript file:
import path from "path";
import { requireModule } from "@boost/module";

const { default: schema } = requireModule(
  path.join(process.cwd(), "./schema.ts")
);

export default schema;

This also doesn’t work without resolving ardatan/graphql-tools#4227, so I had to patch that in the meantime.

Our CLI uses CommonJS and it is not possible to load ESM from CJS. That's why it doesn't work.

Thanks for the help on this & the other issue. I’ll close the issue since it’s essentially a duplicate of #5757 🙂


Add missing visibility declarations

🦟 Bug fix
Summary
While testing https://github.com/gazebosim/gz-cmake/pull/392 I found that some visibility declarations were missing on Linux. Added them in this PR.
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

I think this broke windows CI: https://build.osrfoundation.org/job/ign_common-pr-win/931/

I think this broke windows CI: https://build.osrfoundation.org/job/ign_common-pr-win/931/

Ouch, I give a look to it


feat: infinite scroll eth and erc20

Currently we would be able to implement this only on the UI side given that we would need to query all the blocks anyway therefore not sure if it is worth the effort right now. Moreover, if we implement an infinite scroll only on the UI side we should not forget pending block are added at the start of the list. Therefore let's revisit this later.


Avoid ports collision in 020-quarkus-http-non-application-endpoints for native mode

When you are running your test, using QuarkusProdModeTest you should avoid using @NativeImageTest annotation, otherwise, you will have a collision between ports. because @NativeImageTest will launch an app over port 8081 and QuarkusProdModeTest will launch another app per test, over the same port.
We have defined a 'quarkus.profile' system property on maven-failsafe-plugin. Based on this property, we will build a native image or a JVM instance.

What requires this change? How that previously this was not needed?

What requires this change? How that previously this was not needed?

I think @pjgg added this PR to fix the conflict port issue in the Quarkus Ecosystem CI: https://github.com/quarkus-qe/beefy-scenarios/runs/2053745501?check_suite_focus=true#logs
If so, the right fix is to:

Remove the @NativeImageTest annotation from all the ITs -> this will avoid a separated Quarkus app to be launched before tests
Rename the ITs tests to add the suffix Native to state that these are Native ITs scenarios (this is optional)

The problem is that we are launching a quarkus app every time that we're running a test. But @NativeImageTest also launch another app at the beginning of all the tests, and all of them are using the port 8081.  So there is a port collision.

I think that is more clear with start/stop method.
What is failing is: 602-spring-data-rest

I see
-------------------------------------------------------
[INFO]  T E S T S
[INFO] -------------------------------------------------------
[INFO] Running io.quarkus.qe.non_application.endpoint.RelativePathNonAppEndpointTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.004 s <<< FAILURE! - in io.quarkus.qe.non_application.endpoint.RelativePathNonAppEndpointTest
[ERROR] io.quarkus.qe.non_application.endpoint.RelativePathNonAppEndpointTest  Time elapsed: 0.002 s  <<< ERROR!
java.lang.ExceptionInInitializerError
	at io.quarkus.qe.non_application.endpoint.RelativePathNonAppEndpointTest.<clinit>(RelativePathNonAppEndpointTest.java:18)

[INFO] Running io.quarkus.qe.non_application.endpoint.NonAppEndpointTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.001 s <<< FAILURE! - in io.quarkus.qe.non_application.endpoint.NonAppEndpointTest
[ERROR] io.quarkus.qe.non_application.endpoint.NonAppEndpointTest  Time elapsed: 0 s  <<< ERROR!
java.lang.ExceptionInInitializerError
	at io.quarkus.qe.non_application.endpoint.NonAppEndpointTest.<clinit>(NonAppEndpointTest.java:18)

[INFO] Running io.quarkus.qe.non_application.endpoint.NonAppEndpointNonRootPathTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.001 s <<< FAILURE! - in io.quarkus.qe.non_application.endpoint.NonAppEndpointNonRootPathTest
[ERROR] io.quarkus.qe.non_application.endpoint.NonAppEndpointNonRootPathTest  Time elapsed: 0.001 s  <<< ERROR!
java.lang.ExceptionInInitializerError
	at io.quarkus.qe.non_application.endpoint.NonAppEndpointNonRootPathTest.<clinit>(NonAppEndpointNonRootPathTest.java:17)

[INFO] Running io.quarkus.qe.non_application.endpoint.BackwardCompatibilityTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.001 s <<< FAILURE! - in io.quarkus.qe.non_application.endpoint.BackwardCompatibilityTest
[ERROR] io.quarkus.qe.non_application.endpoint.BackwardCompatibilityTest  Time elapsed: 0 s  <<< ERROR!
java.lang.ExceptionInInitializerError
	at io.quarkus.qe.non_application.endpoint.BackwardCompatibilityTest.<clinit>(BackwardCompatibilityTest.java:26)

[INFO] Running io.quarkus.qe.non_application.endpoint.NonAppEndpointTestNonBaseRootPathTest
[ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0 s <<< FAILURE! - in io.quarkus.qe.non_application.endpoint.NonAppEndpointTestNonBaseRootPathTest
[ERROR] io.quarkus.qe.non_application.endpoint.NonAppEndpointTestNonBaseRootPathTest  Time elapsed: 0 s  <<< ERROR!
java.lang.ExceptionInInitializerError
	at io.quarkus.qe.non_application.endpoint.NonAppEndpointTestNonBaseRootPathTest.<clinit>(NonAppEndpointTestNonBaseRootPathTest.java:18)

@pjgg you need to use .setBuildNative(System.getProperty(QUARKUS_PROFILE, "").equals(NATIVE)) to avoid NPE


Typings module resolution (directory index.d.ts)

Discovered in IndefinitivelyTyped/camo#1, the standard Node module loading behavior (which the related code repository uses currently) is that directories resolve to an included index.js (or for Typescript index.ts or index.d.ts). Typings' build tool is throwing an error in this situation.
Is this something that should more closely match the Node (or Typescript in Node module resolution mode)?

Yes, I believe you're right. I think this is also a part of https://github.com/typings/typings/issues/133, so to remind myself when it comes time this is the algorithm to follow:
const filename = '...'

[filename + '.d.ts', filename + '/index.d.ts', filename - ext + '.d.ts']

Does that seem right?

That seems like it. There's probably some weird edge case to consider, but I think that's the basics.

Don't know if you want this too, but if you want to follow the [typescript npm module resolution] (https://github.com/Microsoft/TypeScript/issues/2338) then I think you need filename + package.typings + .d.ts as well.

@enriched Not entirely sure which part you're referring to, but I think we're on the same page. It already follows package.json

When the main field in some-package/package.json is index.js the definition file is resolved to node_modules/some-package/.d.ts and typings fails to load that file. It took me a while to track down this bug. module resolution needs some work, I tried to contribute but I couldn't figure out whether typings/core is at fault or the cli. For those having the same issue I suggest you rename your index.d.ts along with your index.js to something else like main.d.ts and main.js it only fails with index.

https://github.com/typings/typings/issues/133#issuecomment-193018550
Probably it will be in 0.8

oh, thanks for the heads up :grin: this is a great library :+1: :+1:

When the main field in some-package/package.json is index.js the definition file is resolved to node_modules/some-package/.d.ts and typings fails to load that file

Ah! It used to do this, but people complained because it was obscure. I'll need to undo that patch as part of the next minor release.

@alitaheri I'm assuming your package.json does not have a main specified right?

it does. and if it's index.js the absolute path gets resolved to /.../node_modules/some-package/.d.ts and then it complains that it can't find that file. in this case typings.json has no effect what-so-ever, it having main, or not doesn't affect the behavior. but if I rename my index.js and index.d.ts to main.js and main.d.ts and specify main.js as main in package.json everything works perfectly. the name main doesn't mean anything, just anything except index

@alitaheri What version are you using? That behavior doesn't sound consistent with anything I've built, which is odd. Especially 0.7. Is it index or index.js? Those will act differently.

the latest version. Also happened on 0.6.x. I meant index.js accompanied by index.d.ts although it won't matter because index.d.ts is never resolved.

Can you share the project you're talking about? That would really help understand, thanks.

is it package.json/main: ".../index" or package.json/main: ".../index.js"?

ok, I'll just write it here:
app/node_modules/my-package/package.json:
{
  "main": "index.js"
}

app/node_modules/my-package/index.js:
var hello = "world";
exports.hello =  hello;

app/node_modules/my-package/index.d.ts:
const hello = "world";
export {hello};

and then when I try:
typings install npm:my-package
It complains that it cannot find app/node_modules/my-package/.d.ts
I moved away from using index as name. but this folder structure can reproduce

I just tested again with both 0.6.6 and 0.7.9 it didn't fail :| I don't understand O.o Don't bother for now, let me take a better look, and if I find something I'll ping you again.

I can no longer get it to fail. it took me 3 hours to get to the bottom of it, now I can't make it fail :| I hate moody bugs :disappointed:

moody bugs

I call them love-bugs. They typically just need some love from my co-worker. Once I call my co-worker in, it started working. :rose:
If you can repro it, we will try to help. :smile:

:laughing: :laughing: It took me a couple of hours to even find where it was from. Just wanted to make sure no one else would. I have more projects. I'll try to reproduce it on one of them. Thanks for your fast response and great library :+1: :+1:

@blakeembrey am I right in saying this is still an issue?
example:
$ typings i npm:@ubiquits/core --save
typings INFO globaldependencies "@ubiquits/core" lists global dependencies on "core-js", "dotenv", "hapi", "jasmine", and "node" and should be installed
typings ERR! message Unable to read "build/node/api.d.ts" from "@ubiquits/core". You should validate all import paths are accurate (case sensitive and relative)
typings ERR! caused by ENOENT: no such file or directory, open<EMAIL_ADDRESS>
In this case there is an index.d.ts file at build/node/api/index.d.ts, but no node/api.d.ts file.
The root index.d.ts file has the following "barrel"
export * from './build/node/api';
export * from './build/node/common';

Yes, it's still open.

Quick check, is this still open? :stuck_out_tongue:

Yes, the issue is open still. It's not a high priority for me personally, but I think it's a pretty straightforward patch given a day.

https://github.com/typings/core/pull/171

I've resolved this and will be pushing out a new minor release in the coming day. I would also like to note that "it's a pretty straightforward patch" was an understatement - it took me a good while to get the code working with directory resolution and backward compatibility.


Updated: whatsapp 2.2019.6

${}

1e6b5966-62a3-44c3-b439-6f88b469d1c0

Newer version of whatsapp (2.2023.2) is now available in master. 2550f873ad67a3a78d753ff63c3f4cd9ea735272


Remove extraneous end tags

@KirstieJane did the research for this in mmistakes#245. I tested this with htmlproofer and it's now passing tests.

Thanks @georgeluong


Professional Liability.PODF does not render the black text

Removing the /CS8 cs 1 SCN makes the black text show up.
/CS8 is object 52 which is an array
[/Separation / Black 51 0 R 43 0 R]
51 is [/ICCBased 42 0 R]
43 is a type 0 function

Corrected some parsing errors in the ICC profile and implemented TRC+matrix based transformations

Fixed ICC color transformations in f45d7cdb1d97cb29725df66c1885fdfa4036d0df


Update testing setup and travis configuration, enable testing on ceph "octopus"

The following series of patches makes some changes to the travis+makefile+dockerfile used in testing to make the behavior of the container(s) used for test more consistent.
I am switching to containers based on those provided by ceph. Using these containers both keeps us closer to ceph and speeds up the travis runs by a couple of minutes.
Finally, what all this was leading up to is enabling testing on ceph "octopus" (ceph version 15). Only one existing test failed when using this version of ceph and so before enabling it in travis, one patch changes the whitespace/formatting of the keyring data sent to the mon when testing the input buffer support.
Fixes: #189

I started to wonder a little about the build constraints. Does the Ceph version get detected as "master", or as "nautilus"? It might be a good idea to add "octopus" (and/or "master") to the build constraints in the backwards compatible .go files too.

I started to wonder a little about the build constraints. Does the Ceph version get detected as "master", or as "nautilus"? It might be a good idea to add "octopus" (and/or "master") to the build constraints in the backwards compatible .go files too.

It should work currently, but mainly because most constraints are currently negative (not nautilus or not mimic, etc). It would currently be passed as "master", which I would say is not what we want but I feel its an OK stop-gap until ceph-containers starts building octopus tags. This would be OK as long as long as we don't try to handle nautilus and master/octopus separately.


Does not work on Arch Linux

rust-u2f does not work on Arch Linux. I have commented SELinux lines because they don't work. I have used Makefile from linux directory.
When website asks me to press a button, it crashes with the following message:
thread '' panicked at 'called Result::unwrap() on an Err value: Error(Dbus(D-Bus error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (org.freedesktop.DBus.Error.NoReply)), State { next_error: None, backtrace: None })', src/libcore/result.rs:1009:5

I'm going to close this since the user has deleted their account. If anyone else tries to get this working on Arch it would be useful to first set RUST_BACKTRACE=1 so we can get a better idea of which line is failing. Given it's a D-Bus error it probably has something to do with how the presence test notification is shown, but I'm not going to dig deeper unless someone is able to help debug (Since I don't have an Arch install handy).

i figured out why it happends. DBUS_SESSION_BUS_ADDRESS environment varible is needed to communicate with dbus, but "systemd --user runs outside the user session", so DBUS_SESSION_BUS_ADDRESS not exist in systemd --user environment (you can check that by systemctl --user show-environment). and that caused lot of issue, such as D-Bus error: Failed to connect to socket or D-Bus error: Did not receive a reply

Interesting, that definitely could be the issue. Thanks for the looking into it. dbus-rs, which I indirectly use via the notify-rust dependency, relies on that env variable: https://github.com/diwic/dbus-rs/blob/949b9c318e08e42df8e278079c47d0a72f376e07/dbus-native-channel/src/address.rs#L14
I was semi-aware of this, so on debian platforms I added a package dependency on dbus-user-session which forces all logins for a user to share a single message bus, and that seems to include systemd user sessions. This is a fairly common package to use, the main downside is you can only have a single graphical session for a user.
I'm not sure if there is an equivalent for Arch, or if you'd want that. In theory the user daemon doesn't care how it's run, it just needs to talk to d-bus to pop notifications on some trusted GUI session and also to read/write it's secrets to your keyring. It also connects to the socket of the u2f system service to create a virtual USB device. That's it, there's no systemd specific behavior and I run the user daemon outside of systemd all the time for testing.
So if you or anyone else has a better solution for Arch feel free to send a PR with code / a README update. Maybe XDG autostart is a better approach, but not sure when I'll have time to look into it more: https://wiki.archlinux.org/title/autostarting


GEOMESA-3378 Fix CLI "find" warning output

The warning in RHEL8 is "find: warning you have specified the -maxdepth option after a non-argument -type"

Ok I updated my email in eclipse to<EMAIL_ADDRESS>and set my primary email in github to the same
Also e-signed the eclipse document too


DropDown menu does not closed when Drawer is inside the DropDownMenuItem

Here's the code that I used
                    <Dropdown.DropdownMenuItem asChild>
                      <MyForm />
                    </Dropdown.DropdownMenuItem>

My Form Code
<Drawer.Drawer open={isOpen} onOpenChange={setIsOpen}>
      <Drawer.DrawerTrigger asChild>
        <Button.Button variant="ghost">

           add item
        </Button.Button>
      </Drawer.DrawerTrigger>
      <Form.Form {...form}>
                .....
      </Form.Form>
    </Drawer.Drawer>

Menu item showed on Drawer, to close it I need to close the Drawer and Click again to close the DropDownMenu

The same thing happens when you open the alert dialog from the dropdown menu.
It seems that the wrong class, 'pointer-events: none;' is being added to the body

Actually I figured it out what actually happens
It is because two Triggers are overlapping with each other
DropDownMenu and Drawer both have triggers, so in order to work smoothly we have to remove trigger from child React Node
Here's an example
DropDownMenu
const [isDrawerOpen, setDrawerOpen] = useState < boolean > false;
const [isUploadOpen, setUploadOpen] = useState < boolean > false;

<Dropdown.DropdownMenu>
  <Dropdown.DropdownMenuTrigger showTriggerIcon={false} variant="primary">
     open drop down
  </Dropdown.DropdownMenuTrigger>
  <Dropdown.DropdownMenuContent>
    <Dropdown.DropdownMenuItem asChild onClick={() => setDrawerOpen(true)}>

         Add DropdownMenuItem

    </Dropdown.DropdownMenuItem>
    <Dropdown.DropdownMenuItem asChild onClick={() => setUploadOpen(true)}>

         Add item 2

    </Dropdown.DropdownMenuItem>
  </Dropdown.DropdownMenuContent>
</Dropdown.DropdownMenu>

<DrawerComponent isDrawerOpen={isDrawerOpen} setDrawerOpen={setDrawerOpen} />
<DailgoComponent isUploadOpen={isUploadOpen} setUploadOpen={setUploadOpen} />

Drawer
<Drawer.Drawer open={isDrawerOpen} onOpenChange={setDrawerOpen}>
  ....
</Drawer.Drawer>

Dialog
<Dialog.Dialog open={isUploadOpen} onOpenChange={setUploadOpen}>
  ...
</Dialog.Dialog>


[Proposal] Provide for separate handling of specific errors in promise chains.

Intro
Currently all errors in a promise chain propagate down to a single catch handler at the end. Therein, the identity of the error must often be reasoned out with comparative statements and then handled according to its identity. This can lead to otherwise clean chains becoming bottom-heavy with logic in the catch.
Swift's do-catch provides for error pattern matching in its catch handlers, raising the error identification logic up one level. This PR provides an implementation to introduce this pattern into PromiseKit, allowing for separate catch handlers for specific errors.
refs #639
Usage
The new catchOnly method included in this PR works the same as the current catch method, except that it takes a required Error parameter, and only executes its handler if the promise chain rejects with that error.
firstly {
    API.findUser(named: "Taylor")
}.done { user in
    //…
}.catchOnly(API.Error.noResults) {
    //Let the user know there's no results for their query
}.catch { error in
    //Handle other errors like timeouts
}

In the above, the catchOnly handler would only execute if the API request rejected with a noResults error. The final catch handler would then no longer execute since the error was already handled. Likewise, if some other error occurred, the catchOnly handler would be skipped and only the final catch handler would be executed.
An arbitrary number of catchOnly calls may be chained, but the chain must still be terminated with a final catch. An overload for catchOnly which takes a type instead of an object is also provided for matching on a family of errors.
Implementation
The new functions work similarly to the current catch function, only instead of returning a PMKFinalizer they return a void promise which is fulfilled if the error is handled (or if the promise was fulfilled), and rejected with the unhandled error otherwise to allow it to propagate to successive catch handlers.
Since no changes were made to existing API or implementations, a major version rev should not be necessary. I have included some trivial tests in the PR as evidence that the new functions behave as intended, but I am happy to flesh these out or strip them entirely upon request.
I've not included any implementation for the Objective-C interface (not sure if it's necessary or even desired). But I am happy to do so if requested.
Ideally, I would have preferred a simple catch(Error.someError) signature both for succinctness and keeping in line with Swift's do-catch, but it surfaced the usual compiler confusion that PMK's overloads have dealt with in the past. I settled on catchOnly to get around this, but I actually rather like it now, and its visual distinctness in code from the base catch is probably for the best. Still, open to name changes, of course.
Limitations
Since the new catchOnly functions return a promise, it is possible to chain off of them with functions other than catchOnly and catch. This isn't desirable, but is also unlikely to to be utilized, I believe, since the underlying value from the promise would have been consumed by catchOnly. A chained then or done for instance would have no context. I had originally intended to return a PMKFinalizer to avoid this, but that solution quickly proved to have too many issues.
Error objects with associated values, while technically supported, make little sense in the usage of catchOnly since concrete associated values would need to be supplied in order to pattern match. However, the type-accepting overload of catchOnly can still prove useful in these cases.
Errors passed in must conform to Equatable, but this is given for free in most situations in Swift 4 now.
Alternatives
recover may already be used in a similar manner to catchOnly (as described in #639). And this doesn't appear to be a hotly requested or needed feature by any means. So, leaving it out of PromiseKit probably isn't going to cause any friction.

Is this worth it?
You don't usually care which error happens, and when you do, you often enough need associated values. Most of the time with Promises when I care about specific errors it is in order to recover. Which this PR doesn't handle.
The fact that our catch cannot be as elegant as a Swift catch means this PR could never deliver the kind of value everyone really wants.
However it's not as though I've never wanted this. It's just that most of the times I've wanted it I've got a good Swift error with associated values. Seems like this could be mitigated by provided the error to the handler, but since it will be passed by type, you'd have to unwrap it to get that associated value still.
Either way returning a Promise is a definite no. I've seen in the past when catch returned Promise people getting confused about the chains, this becomes much easier when chains are returned via multiple levels of functions, which is typical with promises, you lose track of where the error is handled leading to code that expects errors but isn't getting them because an earlier catch already consumed the error.
We would have to return a PMKFinalizer which is adapted to handle subsequent catches.

So even though this may not be merged I wanted to go ahead and push up what some of the discussed changes/issues might look like implemented/addressed. Both for fun and reference.

I created a new PMKCascadingFinalizer object to be returned by the catchOnly methods. It behaves the same as PMKFinalizer only wraps a promise instead of a guarantee. It has both catchOnly methods as well as catch which call their respective Promise<T> counterparts for chaining and chain completion.
I implemented recoverOnly with both an object and type accepting variant to mirror catchOnly.
The type accepting variants of catchOnly and recoverOnly can have a catch policy specified for handling or ignoring any cancellation errors within the passed type.

If there ends up being interest to merge this just lmk if there are any changes desired and I'll happily oblige.

I will merge this if we can do the same as a Swift catch statement. I believe this means:
do {
    //…
} catch ErrorType {
    //…
} catch ErrorType.specificError {
    //…
}

Anything else?

I have some code that will use this once it gets into the v7 beta. The design looks good to me.

Can we change to a v7 submission @nathanhosselton

@GarthSnyder @mxcl new PR onto v7 at #1024

Closing in favor of #1024


Check this solution

It works better and has a clean solution

Solution is another approach. Often I want to keep step by step solution for easy tasks.
Thank you for your contribution, but I will keep original solution.


xStream: error when trying to select data from editor popup

Happens when the data was specified directly in the main method and therefore, didn't contain the 'initial' value.

...and fixed with 1.57 that provides a default value of (nil)


Broken Link in Cluster documentation

Problem description

Problem location

I saw a problem on the following URL: https://docs.docker.com/ee/cluster/

I couldn't find the information I wanted. I expected to find it near the following URL:

Other: Link at the bottom of the page didn't update to reflect new nesting:

Where to go next

Get started with Docker Cluster on AWS
Command line reference
Cluster file reference <-- Links to https://docs.docker.com/ee/cluster-file/ when it should link to:
https://docs.docker.com/ee/cluster/cluster-file/

Project version(s) affected

Suggestions for a fix
[Cluster file reference](https://docs.docker.com/ee/cluster/cluster-file/)

Thanks for your feedback. Docker Enterprise docs are now part of Mirantis. You can take a look at the Docker Enterprise documentation at https://docs.mirantis.com/docker-enterprise/.
Let me close this here for that reason. Feel free to continue the conversation after I close.

Yes I’ve noticed, deeply unfortunate. Thanks!
On Thu, Jul 2, 2020 at 03:10 Usha Mandya<EMAIL_ADDRESS>wrote:

Closed #10365 https://github.com/docker/docker.github.io/issues/10365.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker.github.io/issues/10365#event-3506147264,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNEWT5CRQIVXSMJ2JCFOZTRZRFJBANCNFSM4K5ACPQA
.

--
-Chas


MSL: binding is not match

I used glslangValidator and spirv-cross to translate GLSL ES shader to MSL, the binding is not right, the command are:
glslangValidator -e main -o gles3frag.spv -V  gles3.frag
spirv-cross --msl --output gles3frag.metal ./gles3frag.spv

Content of gles3.frag is
#version 310 es

 precision highp float;

layout(std140, binding=2) uniform Color
{
    vec4 u_color;
};

layout(location = 0) out vec4 o_color;

void main()
{
    o_color = u_color;
}

Output MSL shader is
#include <metal_stdlib>
#include <simd/simd.h>

using namespace metal;

struct Color
{
    float4 u_color;
};

struct main0_out
{
    float4 o_color [[color(0)]];
};

fragment main0_out main0(constant Color& _12 [[buffer(0)]])
{
    main0_out out = {};
    out.o_color = _12.u_color;
    return out;
}

As you see, the binding of uniform block Color is changed from 2 to 0. It seems the output MSL ignore binding information set in GLSL ES shader, just start binding from 0.

This is expected behavior. MSL binding space does not match SPIR-V. There is the option https://github.com/KhronosGroup/SPIRV-Cross/blob/master/spirv_msl.hpp#L303, or --msl-decoration-binding from CLI which will map DecorationBinding to MSL binding space. It won't work in the general case however, but for simple cases like this, it should do the trick.

Thanks for the answer. I have a question, then how do i know the binding for a uniform block? As in this issue, how do i know the binding index of Color in MSL? As the shader is converted in runtime, so need to know the binding index in runtime too.

There are basically three approaches you can take here:

Use --msl-decoration-binding approach. Then you know the binding based on the SPIR-V.
Use https://github.com/KhronosGroup/SPIRV-Cross/blob/master/spirv_msl.hpp#L418 API to get full control of how SPIR-V bindings are mapped to MSL. Here you also know the binding.
Use the automatic binding scheme, you can then use https://github.com/KhronosGroup/SPIRV-Cross/blob/master/spirv_msl.hpp#L452 API after calling ::compile() to get the binding you ended up with.

I don't recommend the last one.

Thanks for the answer. I can not use these methods, as the shader is compiled offline, my codes can only get converted MSL. We need to change to compile GLSL ES in runtime if want to use these methods, which may slow down the runtime speed.

Well, if you're compiling off-line as part of a build system there is nothing stopping you from making your own wrapper which extracts the automatic binding information you need.

There are basically three approaches you can take here:

Use --msl-decoration-binding approach. Then you know the binding based on the SPIR-V.
Use https://github.com/KhronosGroup/SPIRV-Cross/blob/master/spirv_msl.hpp#L418 API to get full control of how SPIR-V bindings are mapped to MSL. Here you also know the binding.
Use the automatic binding scheme, you can then use https://github.com/KhronosGroup/SPIRV-Cross/blob/master/spirv_msl.hpp#L452 API after calling ::compile() to get the binding you ended up with.

These were not permalinks so I don't now what they are pointing at. Was this by any chance pointing at get_automatic_msl_resource_binding. What was the third option?


Dashboard date picker issues

Found in PR review #54
Notes about date picker

does not validate range, "To" date can be before "From" date
on page refresh date parameters disappear

I have fixed the first issue, by linking the from and to fields together.
The second issue only happens when the current date is selected, and is a default behavior of the Bootstrap datepicker.


Adding support for GitLab

Thanks for this project!
I'd like to add support for Gitlab as well.
Is this something you are open to adding and/or merging a PR?
Thanks!

The codebase is quite dated and is due for a big refactor. I'd rather not widen the scope of this project for things I won't use/maintain. Feel free to fork it and publish your own version.

Thanks for the response @muan
So do you plan on doing a big refactoring "soon"? (no promises :)
I'm asking because if I'll decide to fork, it may make more sense to wait till it's done to be able to merge stuff more easily.

I really don't know, so.. I guess that means, not soon. FWIW I'm referring to the Gmail DOM parsing part of the code, which I think could be abstracted out with https://github.com/kartiktalwar/gmail.js or similar libraries. But I've yet researched much into it.


Error: (SSH) Channel open failure: open failed

Error: (SSH) Channel open failure: open failed
Your module does not work at all as expected.
[12:44:02 PM] Upload: /Users/azerty/Project/site/app/Http/Controller.php to / /Users/azerty/Project/site/app/Http/Controller.php ...
Error: (SSH) Channel open failure: open failed

I'm on the latest version of macOS, and the latest version of atom.
While manually with scp it works. I have tried all possible configurations.
I therefore delete this module which makes me waste too much time for nothing.

It was a linux access problem, I solved my problem with chmod.
Too bad the error is not very well explained.


Corrected a typo getting-started.md

Replaced the word 'ince' with the correct word 'in'.

Thanks for PR!


Seq from URI

Is your feature request related to a problem? Please describe.
allow a sequence column to be either a uri (e.g. to genbank of fasta file) or atgc etc.

this feature has been added at some point too but was not closed


Disable Autoprefixer Grid

@hansl thanks for being so brave to enable Grid feature in Autoprefixer.
Unfortunately, it may not be the best idea to enable it for everyone. This feature has a lot of limits. And must be explicitly controlled by a developer.
For instance, users complain about Grid warnings: https://github.com/postcss/autoprefixer/issues/1062#issuecomment-402202643
Maybe we can add an extra option to Angular CLI to enable Grid feature?
/cc @clydin

I signed it!

Sorry but I don't understand, why we should disable completely grid feature in autoprefixer.
For example, in my case, I use grid layout and it was working perfectly with Angular.
But what about update you made in project mentioned at the beginning of this discussion.
Please @yepninja could you explain what is this change "IE doesn't support auto-fill and auto-fit. Let's don't add a prefixed prop and create warnings for these values.". And so why theses warnings appear even if you add browser rules omission on autoprefixer.
Is it possible to "unscope" IE but not all the grid feature ?
Sorry in advance if my comprehension is not good. but i'm a little afraid we'll shut down the tree while we can probably just cut a branch... ;-)

We don't need to disable it completely. Current idea is to disable it by default and enable only if you understand it's limits.
But I don't know Angular CLI enough to suggest a option to enable/disable Grid on the flight.

Unfortunately, disabling (permanently or by default) would be a breaking change.  Also, the default browserslist file for a new project (found here) does not include IE9-11.  Are there issues beyond IE supportthat need to be considered?

@clydin maybe we should give API to at least disable it?
What is user support IE 11 but use different polyfill for Grid?

Making it configurable is a potential option.
Also,  I only found two alternate polyfills for IE.  Both appear to be based on outdated specs and are runtime based.  The second of which would make them impractical for use with Angular AOT as the component stylesheets are injected/removed at runtime.  It appears that the autoprefixer approach is the most practical for Angular.

I found this workaround:  https://github.com/angular/angular-cli/issues/5964#issuecomment-294161554.  The workaround has the comments above each item in CSS block.  I found I only had to insert the comment once in each block.

I'm tempted to merge this PR, unless @clydin has some reservations. I'll merge this tomorrow morning if there's no objection.

@hansl Could this be made configurable? It's definitely an important feature for some. Alternatively, one possible workaround would be the grid control comment support that was added in autoprefixer 9.2, but Angular CLI is currently on 9.1.5.

@hansl as I understand it, the "grid: true" was originally introduced so that upgrading autoprefixer within angular-build wasn't a breaking change (as it used to default to true):
https://github.com/angular/angular-cli/issues/7271#issuecomment-353068912
We were also making use of this functionality, it would be useful to have a mechanism to turn it back on if possible.

Would love to get this option back, as I don't want to prefix all my grid styles explicitly. (Took me ~3 hours to find out that it got disabled several weeks ago... and it's not even documented anywhere).

Looks like the fix has now been merged to master:
https://github.com/angular/angular-cli/pull/12785


Can we access parsed OpenApi schema after validation is done?

Validation logic parses and caches \cebe\openapi\spec\OpenApi  internally. It uses it for validation purposes, but this instance (which is already in memory) can be valuable for later use AFTER validation is done.
I have this use case in my head:

We built a validator from the yaml file.
The schema is cached somewhere and used inside.
After validation is complete, can we somehow continue use this finder to maybe find extra details about the matched request or response?
3.1 RequestValidator returns OperationAddress, maybe we can use it to find extra details in the schema?

In other words, can we access the parsed \cebe\openapi\spec\OpenApi from the validator after the validation is done?

We could make this method public: \OpenAPIValidation\PSR7\ValidatorBuilder::getOrCreateSchema. @scaytrase

I hope we should reuse schema of validator itself, not of the builder
чт, 23 мая 2019 г., 18:18 Dmitry Lezhnev<EMAIL_ADDRESS>
We could make this method public:
\OpenAPIValidation\PSR7\ValidatorBuilder::getOrCreateSchema. @scaytrase
https://github.com/scaytrase
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lezhnev74/openapi-psr7-validator/issues/23?email_source=notifications&email_token=ABSGB3PAM4HMC57P4OVXKZ3PW2YSVA5CNFSM4HN2KJ7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWCR4RI#issuecomment-495263301,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABSGB3PPMNOWVYYERERBDTTPW2YSVANCNFSM4HN2KJ7A
.

Maybe we can add this interface for validators:
interface ReusableSchema {
    public function getSchema(): \cebe\openapi\spec\OpenApi;
}

sounds good
чт, 23 мая 2019 г., 18:33 Dmitry Lezhnev<EMAIL_ADDRESS>
Maybe we can add this interface for validators:
interface ReusableSchema {    public function getSchema(): \cebe\openapi\spec\OpenApi;}
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lezhnev74/openapi-psr7-validator/issues/23?email_source=notifications&email_token=ABSGB3OETKSAS2VTHQ6DUNTPW22LLA5CNFSM4HN2KJ7KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWCTMOY#issuecomment-495269435,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABSGB3JYLG52S457DBVVGSDPW22LLANCNFSM4HN2KJ7A
.


Rename "HEAL" to better match what it does

...and update wording on UI to manage expectations.
Users regularly run network heals which best case does nothing, worst case messes up working routes. We should avoid that.

[ ] Bandaid icon in Z-UI
[ ] "better connections" -> "new routes"
[ ] explain downsides and alternatives

It sounds like a good name would be rebuild?

I like "rebuild routes"

Or Rebuild Network

Or Rebuild Network


Extension incorrectly considers colon as part of a word

Summary
When I click on a yaml key, the whole word including the colon is highlighted and used as the "word".
Colon should not be part of the word.
When I now perform the action to "Search in Dash for current selection" for instance, it searches for the key including colon, which won't reveal anything. One has to manually remove the colon from the search term and search again.
I also tried to overwrite wordSeparators in the settings with
{
  "[ansible]": {
    "editor.wordSeparators": "`~!@#%^&*()=+[{]}\\|;:'\",.<>/?"
  }
}

but this is obviously not considered, since it still includes the dot (which is correct in this case), which I incorrectly left in the separators list above.
Extension version
v2.5.86
VS Code version
1.80.1
Ansible Version
ansible [core 2.15.2]
  config file = /Users/Kassi/Projects/Servers/vserver/ansible.cfg
  configured module search path = ['/Users/Kassi/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
  ansible python module location = /opt/homebrew/Cellar/ansible/8.2.0_1/libexec/lib/python3.11/site-packages/ansible
  ansible collection location = /Users/Kassi/.ansible/collections:/usr/share/ansible/collections
  executable location = /opt/homebrew/bin/ansible
  python version = 3.11.4 (main, Jun 20 2023, 17:23:00) [Clang 14.0.3 (clang-14<IP_ADDRESS>.1)] (/opt/homebrew/Cellar/ansible/8.2.0_1/libexec/bin/python3.11)
  jinja version = 3.1.2
  libyaml = True

OS / Environment
MacOS Ventura 13.5, ansible-lint 6.17.2 using ansible-core:2.15.2 ansible-compat:4.1.5 ruamel-yaml:0.17.32 ruamel-yaml-clib:0.2.7
Relevant log output
No response

I tested it, and it seems working fine with the latest release. Is it possible to send a screen recording of the issue?

Sure. Hope it helps.
https://github.com/ansible/vscode-ansible/assets/993392/fc0ffbca-0963-4975-a425-d923d5a4d325

I believe it it happening because of the of the . in the module names as each part is considered a separate word. So entire selection means the entire line, which in this case includes the : as well.
Just to verify this,
Could you try highlighting and selecting other Ansible keys, like the play and task keywords, or maybe even the module options?

I tested it and it's the same behavior on single words without dots, e.g. tasks, roles, hosts, etc.
A single click into the word highlights it incl. colon.

Yup, you are right. I can replicate the behavior now.
However, we do not change anything in our extension in terms of word separators, I checked in the YAML extension, and the behavior is the same.
For your use case, you need to double-click the key in order to select the key (without the :). Single click includes the : as well, just like the YAML extension does.


Razorpay Split Payments API

Where is the Razorpay split payments / route api for nodejs?
It's not clear how is it different from normal razorpay APIs.

@nickborti  Please check this API - https://github.com/razorpay/razorpay-node/wiki#instancepaymentstransferpayment_id-params
For additional information , please check https://razorpay.com/docs/route/api-reference/#linked-account-payment-settlements


SphericalHarmonics

Adds a new SphericalHarmonics object to lovr.math that can be used to easily do soft diffuse lighting.
Here are some thoughts about why this design might not be optimal:

It's CPU-only.

Generating light probes from images on the CPU is slower than doing it on the GPU.
A reasonable use case is generating dynamic light probes by rendering the scene to a cubemap and creating a LightProbe from that.  With this design, dynamic light probes would require the skybox texture to be read back to the CPU, which either adds latency or a blocking wait.

Each instance is just a single probe.

Fancy 3D engines will allow you to pre-compute hundreds of light probes at various locations in an environment, storing them in an optimized format.  At runtime, to light an object with the probes, the engine will quickly compute the closest 4 or so probes to the object and use a blend of them for the indirect diffuse lighting.  Should LÖVR try to offer something like this, or is it best left up to the application?  If it's up to the app, is it even worth it for LÖVR to expose the basic math for probes?  e.g. apps might instead just store big lists of spherical harmonic coefficients in tables and put them directly in Buffers rather than create a bunch of tiny little LightProbe instances that don't provide much value.

Things still missing on this PR:

Need to add shader helper evaluateLightProbe
I think some of the basis evaluation can be simplified with a helper function.

There should be like Pass:setLightProbe, and shaders should:

Incorporate light probe lighting by default
Have a shader flag to enable/disable it
Expose a helper function to evaluate the light probe

Plus ways to compute a light probe using the GPU from a Texture e.g. Texture:computeLightProbe, Texture:newLightProbe, or lovr.graphics.newLightProbe.  These would be able to write the result to a Buffer or read it back and return it as a table/LightProbe.

I think Pass:setLightProbe is too opinionated for LÖVR.  It's hard for LÖVR to make a good decision about how to incorporate the diffuse lighting from spherical harmonics, and for all but the simplest cases it will likely end up disabled and add overhead.
However, I do think that having some way to compute spherical harmonics using the GPU is really valuable.  I landed on Pass:computeSphericalHarmonics for the API.  Texture:computeSphericalHarmonics could work, but it has some drawbacks:

It's not thread safe, unlike a Pass method.
The synchronization for it is suboptimal compared to a Pass method.  If you're trying to compute 100 light probes and put them all in 1 Buffer, LÖVR's current hazard tracking would do a barrier between each one and serialize the compute dispatches.  If you put them all in a Pass instead, they will all run at the same time and you can choose to Pass:barrier if you need any waits.
You get more fine grained control over ordering when using Passes.  If I want to render the scene to a cubemap, compute spherical harmonics from it, and then render my main pass, I can throw a Pass:computeSphericalHarmonics(cubemap) on my main pass and keep everything in a single submit.  If it's on the internal transfer stream, I would need to render the cubemap, submit that pass, then call Texture:computeSphericalHarmonics and submit my main pass.

Also, I've decided to switch the name from LightProbe to SphericalHarmonics.  This name is more accurate because the term "light probe" just means "a thing that records light from every direction".  You could represent a light probe with anything -- spherical harmonics, cubemaps, function, etc.  Spherical harmonics is one possible representation of a light probe, and is the one that we're actually implementing here.  It can also be used for more than light probes -- LÖVR's already using spherical harmonics in the audio module for ambisonics!

OK, so I realized this is all just math with Lua tables and compute shaders, so I'm going to turn it into a library instead!  (Hopefully with fancy tetrahedral interpolation and machinery to bake probes).  Closing this!


Remove label tag wrap around radio and checkbox in forms

I am wanting to target  tags quickly. The current v4-dev applies an unnecessary  wrapper around <input>s on inline form radio and checkbox elements.
Seen below:

    Radios

          <input type="radio" name="gridRadios" id="gridRadios1" value="option1" checked="">
          Option one is this and that—be sure to include why it's great

          <input type="radio" name="gridRadios" id="gridRadios2" value="option2">
          Option two can be something else and selecting it will deselect option one

          <input type="radio" name="gridRadios" id="gridRadios3" value="option3" disabled="">
          Option three is disabled

This is very problematic and odd. they should not be there as the dev will not be able to target s.
I am requesting the removal of the excessive  wrapping around <input>s on inline form radio and checkbox elements.

I am wanting to target  tags quickly.

What do you mean by target?

The current v4-dev applies an unnecessary  wrapper around <input>s on inline form radio and checkbox elements.

This is not unnecessary nor excessive. The surrounding  gives a large clickarea for toggling the input. The  is not made to be block-level to avoid accidental clicks from the white-space around the label and input. As such, the wrapping
 is required for proper stacking.

also, radio buttons and checkboxes (and, well, all types of form control) need a  (or alternative form of naming, such as aria-label attribute) for accessibility. labels can either be separate, which then requires a for/id relationship, or they can be "implicit", where the  wraps around the relevant form control...as is the case in our documented example.

Going to close this out given my comment and @patrickhlauke's, but please feel free to holler if there's something specific around the targeting that you're having a problem with. A class might be coming that way soon anyway, so maybe that could help.

@mdo @patrickhlauke, actually if you look at your example, there are not just 1 but 2 sets of 's for the radio and checkbox elements. So I disagree that the set that wraps the radio and checkbox elements is necessary.

there are two sets of labels, but the first one should actually be a <legend> - and will be once i resolve https://github.com/twbs/bootstrap/pull/17266
there is a difference between an overarching legend and a unique label for each radio/checkbox. so no, the wrapping  is not redundant.

Ah. Gotcha. @patrickhlauke does that mean that we are going to go be adjusting the form layout to include <fieldset>? and follow the form syntax recommended by W3schools?
<form>
  <fieldset>
    <legend>Personalia:</legend>
    Name: <input type="text" size="30">

    Email: <input type="text" size="30">

    Date of birth: <input type="text" size="10">
  </fieldset>
</form>

http://www.w3schools.com/tags/tag_legend.asp

follow the form syntax recommended by W3schools?

no, because the code quality of W3schools is generally poor, as in this case.

Maybe have a look at far more respectable sources of markup to make your point? e.g. https://developer.mozilla.org/en-US/docs/Web/HTML/Element/fieldset

Thanks @patrickhlauke. I did notice though that they did not wrap the input with a label in their example.
<form action="test.php" method="post">
  <fieldset>
    <legend>Title</legend>
    <input type="radio" id="radio"> Click me
  </fieldset>
</form>

Also, we have no way to target just the  according to the documentation. See image..

I did notice in your resource that they did not wrap the <input> tag with a label in their example

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/label
long story short: it's a valid way of doing labelling, so no we're not going to remove it.
however, if your request is not "remove the  wrapper" but rather "also allow for a checkbox/radio button to have a separate  and maintain the same styling", then yes, that's something that we could look into /cc @mdo

thanks @patrickhlauke, that could definitely work to add the

method as well.
a bit redundant but understandable if others have been doing it the other way for some time.


sra_biosampleQC

For Jan release to be pushed to data.argos, SRA_biosampleQC by parsing SRA XML files.
Blocks #9

26d4e4ac9ab48426bbd7513abf7e32ec409de26c


Update virtual-wan-faq.md

Clarify BGP communities, and split ASN guidance to separate QnA

@cherylmc

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off


UWP Support

This is my attempt at support for Universal Windows Platform (UWP).
I followed a pretty basic monkey-see, monkey-do approach and added a new NControl.UWP project which mirrors the implementation for the WinRT platform, and seems to work well on UWP also.  We've been using this in our Xamarin.Forms app on UWP for 6 months now and now that the app was just accepted to the Windows Store, I figured this was a good time to do a PR.
Naturally, this PR depends on my waiting UWP-Support PR for NGraphics. For now, I've included the recompiled NGraphics dlls for UWP that I reference in the NControl and NControl.UWP projects in a folder named "UWP_NGraphics_Assemblies" at the solution root.
As part of my NGraphics PR I updated all its SharpDX libraries to v3.1.0 that was just released, so this might be a good time to do the same for NControl?
I also noticed the version of Xamarin.Forms that this library is using is a few versions behind: v<IP_ADDRESS> from 5/30/2016.  I kept the NControl.UWP library at the latest Xamarin.Forms version since that is what our app is using.  Not sure what the implications of that will be.
I included an important note in the readme file related to using NControl in XF app for UWP.
I believe VS 2015 update 3 is required to open and run the UWP project
Let me know if I screwed something up and I'll try to fix it

Dependent NGraphics PR: https://github.com/praeclarum/NGraphics/pull/63

You shouldn't bump the dependencies without reason. A lower dependency doesn't preclude you from using a newer version.

@laarmen Thanks for taking a look at this.  Can you explain your comment a little more?  I'm not sure which dependency you're referring to.

I must have dreamt it, sorry.

OK, this one for sure, you shouldn't add the NGraphics DLL directly in the source tree. Just leave a comment on the PR saying that it shouldn't be merged until praeclarum/NGraphics#63 has been merged and a new nuget has been published (to have a dependency version)

Hmmm, I'm not sure what the best way to handle this is.  I did in fact include a note about this in this PR:

Naturally, this PR depends on my waiting UWP-Support PR for NGraphics. For now, I've included the recompiled NGraphics dlls for UWP that I reference in the NControl and NControl.UWP projects in a folder named "UWP_NGraphics_Assemblies" at the solution root.

I did this to isolate the changes I made for NControl from the ones I made to NGraphics.  I wanted to allow the maintainers and others to be able to test this without needing to also compile NGraphics with my PR (which honestly, I'm not even sure is necessary now based on praeclarum's initial comments about my PR).

Good news! The required NGraphics PR was just merged. Hopefully that will be released soon and this PR can the move forward.
Once NGraphics is released, we'll want to be sure to remove references to the included NGraphis DLLs in this PR. See above comment

Anyone knows anything about the expected release date for the updated NGraphics?

No - I just hit Frank up on Twitter.

@TomSoderling  any update on this?

@fotiDim I've had no response from the NGraphics library guy, so Chris and I have discussed just releasing this ahead of NGraphics - which I'm all for.  I want to encourage any developer to build Xamarin.Forms apps on UWP.
You can get the code for the pull request, compile, and use the library today.  That's what I'm doing

If you compile against .Net Standard, you get UWP and .Net Framework (and .Net Core!) support without needed separate projects

....at least, from what I've read.  I haven't tried it yet.

What I suggest is that someone takes upon the task to fork NGraphics and
release a new version that can be included with NControl.
Alternatively one could create a new version of NControl that uses
SkiaSharp as the rendering engine. Any thoughts?
Chris
On Wed, Feb 15, 2017 at 9:17 PM, BlueRaja<EMAIL_ADDRESS>wrote:

If you compile against .Net Standard, you get UWP and .Net Framework (and
.Net Core!) support without needed separate projects
[image: .Net Standard Chart]
https://camo.githubusercontent.com/b15ee55b8d61134ae6183ad0bfee12a7b5a3bb60/68747470733a2f2f692e737461636b2e696d6775722e636f6d2f5559496e532e706e67
....at least, from what I've read. I haven't tried it yet.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/chrfalch/NControl/pull/71#issuecomment-280126351, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA1a9DBqmXINhM-ddn5a9n5pFgqaAK_1ks5rc11vgaJpZM4KhuNP
.

I think if the original NGraphics is unmaintained a fork is more appropriate.
@chrfalch what benefits do you have in mind regarding SkiaSharp?

The best would definitely be NGraphics, I just wanted to raise the issue with SkiaSharp - which is supported and maintained by Xamarin and looks more promising.

feb. 2017 kl. 08.57 skrev Foti Dim<EMAIL_ADDRESS>
I think if the original NGraphics is unmaintained a fork is more appropriate.
@chrfalch https://github.com/chrfalch what benefits do you have in mind regarding SkiaSharp?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/chrfalch/NControl/pull/71#issuecomment-280258954, or mute the thread https://github.com/notifications/unsubscribe-auth/AA1a9BINega8wS8Wo4Bd1hnHlK3-PI9nks5rdAFjgaJpZM4KhuNP.

Seriously guys, I'm not even sure it's a question.  NGraphics is dead, SkiaSharp is the officially supported way forward (and has come impressively far in short time), which also means NGraphics is not worth forking.
Wrap that like you did NGraphics, and you're done.  The bindable controls that NControl provided would be handy compared to just using SkiaSharp as-is.

Anyone else have strong opinions on this? Wouldn't be hard to convert it,
and would also make some sense. I've made a new issue on Github about this:
https://github.com/chrfalch/NControl/issues/75
On Fri, Mar 3, 2017 at 10:00 PM, David Pugmire<EMAIL_ADDRESS>wrote:

Seriously guys, I'm not even sure it's a question. NGraphics is dead,
SkiaSharp is the officially supported way forward (and has come
impressively far in short time), which also means NGraphics is not worth
forking.
Wrap that like you did NGraphics, and you're done. The bindable controls
that NControl provided would be handy compared to just using SkiaSharp
as-is.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chrfalch/NControl/pull/71#issuecomment-284068719, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA1a9LVkHnuB306F5GBKUTwOJ5xzTUiqks5riH9agaJpZM4KhuNP
.

Having considered the facts I am voting as well for SkiaSharp port.

juat wanted to mention this since I'm no graphics master. I asked Mark Smith (Xam U) about SkiaSharp vs. NGraphics last year after Evolve. He reached out to his Xamarin coworkers at that time and this is what he said:
Ultimately, I think the choice is really up to you. The difference is the SkiaSharp was built by Xamarin directly (e.g. the wrapper) - NGraphics was not (it was actually built by Frank Krueger, who is awesome, but not employed by Xamarin).
Miguel had a quote which I think helps explain it a bit from here: https://blog.xamarin.com/cross-platform-2d-graphics-with-skiasharp/
Why We Chose Skia
While Mono has supported System.Drawing for a while, and we built a CoreGraphics-powered version for Mac/iOS, it has never been a pixel-perfect match for the original .NET implementation of System.Drawing. Mono.Cairo is also generally available, but has some limitations that are difficult to work around.
Skia gives us the same graphics output across all platforms, is actively maintained, and offers great features not found elsewhere, like filters and hardware accelerated graphics.
So you can use either wrapper library - and if you have a heavy investment in NGraphics already (which you do), it’s probably not worth moving away from it. For a new project, I’d probably push you towards Skia just because it will have the full support of the Xamarin team going forward and so you can expect to see further improvements and contributions to flesh out the library.
I hope that helps!

You might consider continuing the discussion here, @TomSoderling : https://github.com/chrfalch/NControl/issues/75

FYI: I have created a UWP sample, based on work of @TomSoderling. Consolidated dependencies, too.
If you are interested, you can check uwp branch of my fork.
Please let me know, whether you consider merging. Otherwise i can still create my private packages as I need this functionality.

You will lose Windows 8 support by porting to SkiaSharp https://github.com/mono/SkiaSharp/issues/20 .
So if the port is done, it's worth making a note that people should use an old version for Win8 support, or a forked old version for both Win8 and UWP support.

Meanwhile I updated the uwp branch of my fork to use NGraphics 0.5.0-beta1. All the SharpDX related errors and warnings have gone now, though here is no more support of Windows (Phone) 8 and 8.1. NGraphics no longer supports them.
If somebody interested, I uploaded a NuGet package to myget - it can be grabbed from this feed.

Hi,
Thanks for reaching out. This repository is no longer actively maintained.
Please feel free to fork and update if you want.
Chris
On Sat, Feb 24, 2018 at 3:19 PM, Christophe Faucon<EMAIL_ADDRESS>
wrote:

Is there any news on this pr? I just started working with a UWP project
and had to track down a failure relating to our internal library relying on
ncontrol and ngraphics, and if you don't manually install ngraphics first
there is a cryptic failure with the package restoration. At the very least
an update nuget package that requires SharpDX 3.11+( or the NGraphics.UWP
for UWP projects) would at least allow the packages to install correctly.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/chrfalch/NControl/pull/71#issuecomment-368231412, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA1a9H8TcBRYk6XXPXQvy0WRLDiiPn6Cks5tYBp8gaJpZM4KhuNP
.


multi-model inference using c++

when inference several model one by one, should I create only one runtime::Module and reuse memory?

Please open a new thread on https://discuss.tvm.ai/


Bound bumps

allow-newer: openapi3:lens and allow-newer: openapi3:QuickCheck works for us on an internal project, provided that dependent packages are similarly relaxed. This PR passes cabal test --constraint 'lens ^>=5.3' --constraint 'QuickCheck ^>=2.15' --allow-newer=insert-ordered-containers:lens --allow-newer=aeson:QuickCheck --allow-newer=quickcheck-instances:QuickCheck, but you may want to hold off until the allow-newers are not required.
When this does go through, can you please also make a Hackage metadata revision?
See also:

https://github.com/phadej/insert-ordered-containers/pull/58
https://github.com/haskell/aeson/issues/1096
https://github.com/haskellari/qc-instances/issues/92

@maksbotan While we're at it, this would be nice to merge, since it is a dependency of servant, and we are then closer to being able to try GHC 9.10.

Done on hackage!


Upgrade Open Match to latest version

We are currently running 1.6.0. Current latest is 1.7.0 we should at least be on that.
If 1.8.0 comes up between then and now, we should move to that.

We'll be releasing 1.8.0 at some point in the future, so may end up holding off on this work until that time.

1.8.0 is out!
https://github.com/googleforgames/open-match/releases/tag/v1.8.0

Just updated to 1.8.0. Closing!


Bump CAPVCD version to 1.1.0

Consumes the new giantswarm-1.1.z branch.
Towards https://github.com/giantswarm/giantswarm/issues/27464
Testing

[ ] fresh install works
[x] upgrade from previous version works

Checklist

[x] Update changelog in CHANGELOG.md.
[x] Make sure values.yaml and values.schema.json are valid.
[ ] Update lastpass values if required.

Please don't merge this until CAPI bug is fixed.

Please don't merge this until CAPI bug is fixed.

could you be more specific?

Please don't merge this until CAPI bug is fixed.

could you be more specific?

I mentioned it in the parent issue here https://github.com/giantswarm/giantswarm/issues/27464#issuecomment-1649398066

I verified this PR with the latest CAPI version so we can merge this PR.


Fix rightpanestore

Summary
Fixes termselector, change tabs
Test Plan
Select term in termselector
Issues

Reset in legacy search seems to not work.
Separate EventEmitter as a static variable instead of extending the class? maybe with pass through methods

Not sure if this is a good solution long-term but I'll merge it right now and look into this later. If this problem exists in RightPaneStore it might also mean that AppStore is broken in some way, because this was all from the removal of flux. Will need to do more testing and research.


React usage

How can I use this library on React?

I never used react, did you find out how to use it? If so, I would appreciate if you could add a short explanation so I can add it to the docs.

I use this with React, there isn't anything special needed as far as I know. I import the library at the top of my file per the docs.
I initialize once the component mounts
componentDidMount() {
    sortable('.sortable', {
        forcePlaceholderSize: true,
        placeholderClass: 'sortable-placeholder',
        hoverClass: 'is-hovered'
    });
}

Then I add the necessary classes to the sortable container and sortable elements.


Failed: Update autorest version to prerelease 3.0.0-alpha.20240619.2

Generated by Autorest Regen Preview build 20240619.2Triggered from pull request: https://github.com/Azure/autorest.csharp/pull/4838

API change check
API changes are not detected in this pull request.


( request ) bots join a specific location

Ensure that all bots meet a certain point in the map .
Example: In the center

Thanks for not helping

LOL


docs: fix typo in documents

- **Description:** a description of the change
- **Issue:**  the `ChatPromptTemplate` wasn't imported from the available LangChain prompts, which is necessary for running the chat template example code. Furthermore, there's an import (`ChatOpenAI`) that is not used in this particular context.

@sbusso

@chenqing ?

@chenqing ?

I realized there was no one to handle this issue, and I didn't know who to call.