TypeLoadException in Signlas Window with Unity 2019.3

I get the following exception when clicking on Update Signals List:
ReflectionTypeLoadException: Exception of type 'System.Reflection.ReflectionTypeLoadException' was thrown.
System.Reflection.Assembly.GetTypes () (at <437ba245d8404784b9fbab9b439ac908>:0)
Supyrb.SignalReflectionHelper.GetAllDerivedClasses[T] (System.Collections.Generic.List`1[System.Type]& list, System.Reflection.Assembly assembly) (at Library/PackageCache/com.supyrb.signals@d761732506/Scripts/Editor/SignalReflectionHelper.cs:32)
Supyrb.SignalReflectionHelper.GetAllDerivedClasses[T] (System.Collections.Generic.List`1[System.Type]& list) (at Library/PackageCache/com.supyrb.signals@d761732506/Scripts/Editor/SignalReflectionHelper.cs:26)
Supyrb.SignalsEditorDatabase.UpdateDatabase () (at Library/PackageCache/com.supyrb.signals@d761732506/Scripts/Editor/SignalsEditorDatabase.cs:67)
Supyrb.SignalsTreeView.UpdateSignalData () (at Library/PackageCache/com.supyrb.signals@d761732506/Scripts/Editor/SignalsTreeView.cs:53)
Supyrb.SignalsTreeViewWindow.DoFooter () (at Library/PackageCache/com.supyrb.signals@d761732506/Scripts/Editor/SignalsTreeViewWindow.cs:142)
Supyrb.SignalsTreeViewWindow.OnGUI () (at Library/PackageCache/com.supyrb.signals@d761732506/Scripts/Editor/SignalsTreeViewWindow.cs:98)
System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at <437ba245d8404784b9fbab9b439ac908>:0)
Rethrow as TargetInvocationException: Exception has been thrown by the target of an invocation.
System.Reflection.MonoMethod.Invoke (System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object[] parameters, System.Globalization.CultureInfo culture) (at <437ba245d8404784b9fbab9b439ac908>:0)
System.Reflection.MethodBase.Invoke (System.Object obj, System.Object[] parameters) (at <437ba245d8404784b9fbab9b439ac908>:0)
UnityEditor.HostView.Invoke (System.String methodName, System.Object obj) (at <d0ffe769b7a34b4cac3a7cdc5c696293>:0)
UnityEditor.HostView.Invoke (System.String methodName) (at <d0ffe769b7a34b4cac3a7cdc5c696293>:0)
UnityEditor.HostView.InvokeOnGUI (UnityEngine.Rect onGUIPosition, UnityEngine.Rect viewRect) (at <d0ffe769b7a34b4cac3a7cdc5c696293>:0)
UnityEditor.DockArea.DrawView (UnityEngine.Rect viewRect, UnityEngine.Rect dockAreaRect) (at <d0ffe769b7a34b4cac3a7cdc5c696293>:0)
UnityEditor.DockArea.OldOnGUI () (at <d0ffe769b7a34b4cac3a7cdc5c696293>:0)
UnityEngine.UIElements.IMGUIContainer.DoOnGUI (UnityEngine.Event evt, UnityEngine.Matrix4x4 parentTransform, UnityEngine.Rect clippingRect, System.Boolean isComputingLayout, UnityEngine.Rect layoutSize, System.Boolean canAffectFocus) (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.IMGUIContainer.HandleIMGUIEvent (UnityEngine.Event e, UnityEngine.Matrix4x4 worldTransform, UnityEngine.Rect clippingRect, System.Boolean canAffectFocus) (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.IMGUIContainer.HandleIMGUIEvent (UnityEngine.Event e, System.Boolean canAffectFocus) (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.IMGUIContainer.SendEventToIMGUI (UnityEngine.UIElements.EventBase evt, System.Boolean canAffectFocus) (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.IMGUIContainer.HandleEvent (UnityEngine.UIElements.EventBase evt) (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.CallbackEventHandler.HandleEventAtTargetPhase (UnityEngine.UIElements.EventBase evt) (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.MouseCaptureDispatchingStrategy.DispatchEvent (UnityEngine.UIElements.EventBase evt, UnityEngine.UIElements.IPanel panel) (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.EventDispatcher.ProcessEvent (UnityEngine.UIElements.EventBase evt, UnityEngine.UIElements.IPanel panel) (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.EventDispatcher.ProcessEventQueue () (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.EventDispatcher.OpenGate () (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.EventDispatcherGate.Dispose () (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.EventDispatcher.ProcessEvent (UnityEngine.UIElements.EventBase evt, UnityEngine.UIElements.IPanel panel) (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.EventDispatcher.Dispatch (UnityEngine.UIElements.EventBase evt, UnityEngine.UIElements.IPanel panel, UnityEngine.UIElements.DispatchMode dispatchMode) (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.BaseVisualElementPanel.SendEvent (UnityEngine.UIElements.EventBase e, UnityEngine.UIElements.DispatchMode dispatchMode) (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.UIElementsUtility.DoDispatch (UnityEngine.UIElements.BaseVisualElementPanel panel) (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.UIElements.UIElementsUtility.ProcessEvent (System.Int32 instanceID, System.IntPtr nativeEventPtr) (at <57fa7f4ad1c34ed185465e0a9f71c244>:0)
UnityEngine.GUIUtility.ProcessEvent (System.Int32 instanceID, System.IntPtr nativeEventPtr) (at <59837000ebf54955a9cb1d31caa86097>:0)

I get that exception on Assembly.GetTypes() for "Microsoft.CodeAnalysis.Scripting" since 2019.3, personally I just fix it by ignoring that exception.

Hi @Froghut,
thanks a lot for the bug report. Seems to be related to this issue: https://github.com/dotnet/roslyn/issues/9417
Since the issue is quite old, I guess the best way is to ignore all assemblys that start with Microsoft.*, since those will have no defined signals in them. I'll get on that right away :)

Alright, I just went on to ignore processing all libraries that are outside the project folder. Those won't be relevant for searching for Signals classes (except when Unity itself decides to use the package), so I guess that is a nice optimization for now. Can you check if that fixes your problem? I sadly can't reproduce the problem, even though I'm testing on 2019.3.2f1.

I did not realize this is a general problem in Unity 2019. I found out the offending assembly is actually part of the unity package "Code Analysis" which is a dependency of the "Immediate Window" package I was using.
To come back to your fix, because the assembly is pat of a package it resides in the Library folder so is still checked.

Snap! I already though, that this might be tied to the code analysis package. Thanks for the analysis, I'll do a repro and will fix the problem.

I was able to reproduce the problem and blacklisted Microsoft.CodeAnalysis.* to avoid reading that assembly. That fixed the issue for me. Can you check as well? :)

I wasn't superhappy with the solution, so I included a try catch block which handles the exception. This way, future buggy assemblies should not break the update logic.
If you're interested, there is an issue filed for the very assembly that created a problem in our case: https://issuetracker.unity3d.com/issues/reflectiontypeloadexception-is-thrown-when-retrieving-assembly-types-in-project-that-contains-immediate-window-package
@Froghut Is the problem solved for you now? Version 0.4.3 should be safe to use again.

Yes, works! And thanks for the link to issue.

Sure thing, thanks for reporting and testing the issue :)


semi auto annotation function message Error : "point coordinate" is expected to be "number", but "object has been got.

Hi, I wanted to execute semantic segmentation(deeplabv3 inference) function, but I got error like below image.

my reslult is list, and object of list is like this. {
"label": str,
"points": [ [x1,y1],[x2,y2] ...]
"mask": cvat_mask.tolist(),
"type": "mask"}
below code is inference method of ModelHandler class.
    def infer(self, image, threshold):
        '''
            image(PIL Image)
        '''
        input_tensor = self.preprocess(image)
        input_batch = input_tensor.unsqueeze(0).to(self.device)
        output = self.model(input_batch)
        preds = output.argmax(1).detach().cpu().numpy()
        results=[]
        for pred in preds:
            color_mask = ImageHelper.label2bgr(pred, self.colors)
            for class_index in range(1,len(self.colors)):
                label_class = ImageHelper.get_label(pred, class_index)
                if label_class is not None:
                    class_binary_mask = label_class==class_index
                    label_image = measure.label(class_binary_mask, connectivity=2)
                    for num,region in enumerate(measure.regionprops(label_image)):
                        cvat_mask=to_cvat_mask(region.bbox,class_binary_mask.astype(np.uint8))
                        results.append({
                            "label": self.labels[class_index],
                            "points": region.coords.tolist(), # [ [x1,y1],[x2,y2] ...]
                            "mask": cvat_mask.tolist(),
                            "type": "mask",
                        })

        return results

and below code is to_cvat_mask method.
def to_cvat_mask(box, mask):
   min_row, min_col, max_row, max_col = box
   return mask[min_row:max_row,min_col:max_col]

it was nothing error message in function container's log.
what is wrong with my code?
i already saw issue #3620, but i cannot find the specified interface in cvat/apps/lambda_manager/views.py . Please Can you help me?

Thank you for your help. I refered to coco code.
region.coord was not boundary coord, it was coord of region's all pixel.
I'll close issue.


Use asserts instead of segfaults

I noticed some places try to crash the application using

(int)0 = 0;

Is there a reason not to use assert(1) from the std lib?
$ grep -nri '\*(int' src/rnn.c:99:    *(int*)0 = 0; src/rnn.c:145:      *(int*)0 = 0;

When targeting environments such as WASM with no standard libraries at all, terminating functions (e.g. assert(), abort(), exit()) require implementations at run-time. Since the trap is a debugging utility, it would better be a no-op (or something that compiles to unreachable in WASM to throw out to the JavaScript run-time) than linking in more code that never runs.

I wonder what would happen if *(int*)0=0; is replaced with __builtin_unreachable(); across different compilers and runtimes.

See https://github.com/scottt/debugbreak

This seems to be a duplicate of #6 .


Documentation request: Examples of using profiles in the Configuration documentation

I am attempting to test using different process defaults for some of my modules. It would be convenient if I could specify different profiles to use for testing in different test() blocks. The configuration documentation makes it seem that this might be possible. However, I cannot figure out how to do this.
For example, I have a default nf_test profile in my config file. I can specify extra options to be used by the process by using the task.ext process directive. However, I can't test this in individual test cases because there does not seem to be a straightforward way to select a profile in different tests. e.g. the following immediately fails with "Error: groovy.lang.MissingMethodException: No signature of method: fastp_nf$_run_closure1$_closure4.profile() is applicable for argument types: (String) values: [user_args]"
test("fastp trims reads -- PE reads + user args") {
        profile "user_args"
        ...
}

After rereading the Configuration documentation I believe this is just a case of incomplete docs. Point 2 of the profile priority order docs indicates that it should be possible to specify profiles at the level of testcases, but after rereading the rest of the docs it's not clear if this is actually possible. I think this section in general could use some more comprehensive examples of usage. e.g. can we combine profiles with "+" anywhere except the command line? How do we define a profile in a testcase? Can we only define one profile for an entire nextflow_process {} without having to configure with command line options, or is it possible to specify a profile and/or config inside of a test() block?


106 refine python

Removes some logic bugs : negative cash values, selling when no position exists
Added logging
Fix directory structure
Clean up main.py

https://github.com/calumrussell/rotala/issues/106


Have a way to reconstruct the solution to the cvxpy problem from the solution to the simplified Sedumi problem.

Maybe transformation/simplification that produces a Sedumi model should be done using a Sedumi model object that has a reconstruct method and uses information saved during the transformations.

Things to take into account:

[ ] min or max (when data is retrieved for CVXOPT format, max problems have been changed to the equivalent min problem)
[ ] constant offset (not reflected in c, A, b, G, h, but get_problem_data's dict has a key named 'offset' or something similar, is this what it is?)
[ ] undoing simplification

For the local case the matrix needed to recompile the original problem's solution could be passed to Matlab in the workspace and we could alter the Matlab run code to print the vars after translation back to the original space.


feat: US ZWA024-A Firmware to 1.6.7

Update MultiSensor 7 to V1.6.7
Manufacturer URL: https://aeotec.freshdesk.com/support/solutions/articles/6000255731-update-multisensor-7-v1-6-7
"brand": "Aeotec",
"model": "ZWA024-A",
"manufacturerId": "0x0371",
"productType": "0x0102", //US
"productId": "0x0018"

@Aeotec-ccheng can you review please?

Missed this one, i've included the firmware change on https://github.com/zwave-js/firmware-updates/pull/147

Thanks. Closing in favor of https://github.com/zwave-js/firmware-updates/pull/147


After first configuration, restart not working anymore

./wgd.sh start
[WGDashboard] WireGuard is already installed.
[WGDashboard] Starting WGDashboard with Gunicorn in the background.
Failed to read config file: ./gunicorn.conf.py
Traceback (most recent call last):
File "/root/WGDashboard/src/venv/lib/python3.11/site-packages/gunicorn/app/base.py", line 110, in get_config_from_filename
spec.loader.exec_module(mod)
File "", line 940, in exec_module
File "", line 241, in _call_with_frames_removed
File "/root/WGDashboard/src/./gunicorn.conf.py", line 1, in
import dashboard
File "/root/WGDashboard/src/dashboard.py", line 1649, in
DashboardConfig = DashboardConfig()
^^^^^^^^^^^^^^^^^
File "/root/WGDashboard/src/dashboard.py", line 1348, in init
"remote_endpoint": ifcfg.default_interface()['inet'] if ifcfg.default_interface() else '',
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/WGDashboard/src/venv/lib/python3.11/site-packages/ifcfg/init.py", line 81, in default_interface
return Parser(ifconfig=ifconfig)._default_interface(route_output=route_output)
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/root/WGDashboard/src/venv/lib/python3.11/site-packages/ifcfg/parser.py", line 34, in init
self.parse(self.ifconfig_data)
File "/root/WGDashboard/src/venv/lib/python3.11/site-packages/ifcfg/parser.py", line 76, in parse
raise RuntimeError(
RuntimeError: Got results that don't belong to a device
python3.11
debian 12.07

Hi, could you let me know what does ifconfig returns for you? If anything seems normal, try the following:
(assuming you're in wgdashboard/src)
./venv/bin/python3 -m pip install -r requirements.txt


Impossible to use pseudo-parameters in CFN Mapping

Hi CDK team,
I recently tried to use following construct to get mapping parameter basing on account and region
let mappings = new cdk.Mapping(this, 'RegionsMap', {
            mapping: {
                "us-west-2": {
                    "000000000000": "..."
                }
            }
        });

mappings.findInMap(new cdk.AwsRegion(), new cdk.AwsAccountId());

However during execution I get exception (https://github.com/awslabs/aws-cdk/blob/master/packages/%40aws-cdk/cdk/lib/cloudformation/mapping.ts#L36) as findInMap tries to check if value is in map.
I wonder if mentioned check could be removed, as syntax with findInMap is shorter and less error prone than new cdk.FnFindInMap.

Makes sense of course. We could use cdk.unresolved to determine if the key is a concrete string or a token like {AWS::Region} and only check existence of the key if it's resolved

The fix for this assumes that the two parameters are either string or pseudo parameters. If the first is a  pseudo parameter and the second a static string it fails with:
TypeError: Cannot use 'in' operator to search for 'ami-id' in undefined
This is due to a dependency on the first parameter resolving when checking the second.
The fix is:
33c33
<         if (!token_1.Token.unresolved(key2) && !(key2 in this.mapping[key1])) {

    if (!token_1.Token.unresolved(key1) && !token_1.Token.unresolved(key2) && !(key2 in this.mapping[key1])) {


soco.plugins.spotify seems unable to add tracks or albums to queue

The following code (imports excluded):
device = list(soco.discover())[0].group.coordinator
spotify.Spotify(device).add_album_to_queue(spotify.SpotifyAlbum('spotify:album:44F4vywhlpAhLoar8Jrd9k'))

generates the following error:
Traceback (most recent call last):
  File "soco_test.py", line 14, in <module>
    spotify.Spotify(device).add_album_to_queue(spotify.SpotifyAlbum('spotify:album:44F4vywhlpAhLoar8Jrd9k'))
  File "/usr/local/lib/python2.7/dist-packages/soco/plugins/spotify.py", line 235, in add_album_to_queue
    return self.soco.add_to_queue(spotify_album)
  File "/usr/local/lib/python2.7/dist-packages/soco/core.py", line 95, in inner_function
    return function(self, *args, **kwargs)
  File "/usr/local/lib/python2.7/dist-packages/soco/core.py", line 1586, in add_to_queue
    metadata = to_didl_string(queueable_item)
  File "/usr/local/lib/python2.7/dist-packages/soco/data_structures.py", line 55, in to_didl_string
    didl.append(arg.to_element())
AttributeError: 'SpotifyAlbum' object has no attribute 'to_element'

There's a corresponding error when you try to add a track.

Was the error resolved because I'm having the same issue

No, it wasn't resolved, but I found a gist with a temporary solution, and I think there was also something on Github suggesting the problem might be fixed in the next version of soco. I'll email you the link to the gist when I'm at my PC. I've been using it successfully for loading tracks (one at a time), but I haven't succeeded in loading containers, like albums or spotify radio stations.
On Mon, 21 Dec, 2015 at 13:28<EMAIL_ADDRESS>wrote:
Was the error resolved because I'm having the same issue
—
Reply to this email directly or view it on GitHub.

This is the gist ... A quick demo showing how to add a music service track to the queue
|   |
|   |  |   |   |   |   |   |
| A quick demo showing how to add a music service track to...A quick demo showing how to add a music service track to the queue |
|  |
| View on gist.github.com | Preview by Yahoo |
|  |
|   |
  From: millzee2000<EMAIL_ADDRESS>
To: SoCo/SoCo<EMAIL_ADDRESS>Cc: relevitt<EMAIL_ADDRESS>Sent: Monday, 21 December 2015, 13:28
Subject: Re: [SoCo] soco.plugins.spotify seems unable to add tracks or albums to queue (#381)
Was the error resolved because I'm having the same issue—
Reply to this email directly or view it on GitHub.

Thanks a lot :+1: it works... well yeah, hopefully there is a fix

Here's a gist for adding a spotify album ... https://gist.github.com/relevitt/21dd577e96bcbd8696e2


command not found: tmux

First of all, thanks for your work. Your setup and the Nord theme are exactly my kind of taste :)
Problem
When I execute the noobs-term.sh script, everything seems to work fine at first. But after re-login, I get the following error in iterm on MacOS:
/Users/mario/.zshrc:7: command not found: tmux
/Users/mario/.zshrc:7: command not found: tmux

Then I tried to execute tmux manually, but it did not work. All other commands did not work either eg. vim, brew etc. After inspecting, I saw that somehow my PATH variable did not include the /usr/local/bin anymore, where all the installed commands live.
After including export PATH=$PATH:/usr/local/bin at the top, everything works fine again.

Thanks for reporting this. I think this possibly has to do with the way Homebrew is installed. Did you have Homebrew installed prior to running the script?

Hi Aaron, yes I had Homebrew already installed before executing the script. But the script recognised it, since it informed me about it during execution.

Looks like Homebrew requires /usr/local/bin to be in your PATH which you already figured out. When you run the installer it will warn you:

Since the script detects Homebrew is already installed it assumes it is all good.

I think that is a good idea, since that ist the only thing preventing noobs-term to work as expected after script is done executing.


Function-name bikeshedding

The current proposal uses flow and pipe as names for very similar concepts however it's not clear how "flow" distinguishes the behaviour from pipe.
Given .pipe(initial, ...fns) is essentially just .flow(...fns)(initial) I feel like a terminology like .pipeline(...fns) would make more sense. i.e. .pipeline creates a pipeline which can be passed a value, .pipe would be treatable as a shorthand for passing a value into a pipeline.

I like the suggestion by @Jamesernator - an alternative could also be createPipe instead of flow (though this could imply that pipe is an object being created).
I guess something that is unavoidable is that pipe can be read as either a noun or a verb.
That said, I think compose tends to often imply the creation of a new unary function. But I don't know how heterodox composeLeft and composeRight might sound.

I lifted flow from Lodash, thinking that community precedent would make its meaning clearer. But it’s true that it’s pretty similar sounding to pipe.
I am fine with renaming flow to compose, and I think I’ll use compose when I present it to the TC39 plenary next week.
(I like pipeline and createPipe less, since they are still pretty similar to pipe and have less precedent than either flow or compose.)

I am fine with renaming flow to compose

Perhaps I'm misunderstanding, but don't these two create their respective pipelines in opposite directions?
Something like:
compose(3rd, 2nd, 1st)(x)

Vs:
flow(1st, 2nd, 3rd)(x)
pipe(x, 1st, 2nd, 3rd)

Have I got that wrong?

Oh, yeah, right, now I remember; it’s been a while.
The whole reason why I named it flow in the first place instead of compose was because compose usually refers to RTL composition…

LTR, RTL... why not both? 😁

Is the intent for these function(s) to be exposed as globals in JS programs, or to live in some namespace?
Like, will I literally have flow as a top-level built-in function (going to be SO MUCH namespace overlap with existing code) or will it more likely be something like Function.flow?

Due to its rejection for Stage 1 on 2022-07, I’m withdrawing this proposal. I really appreciate everyone here giving discussion, though. (In the far future, after the pipe operator gains users, pain points with the pipe operator may be enough motivation to revive this proposal.) Happy trails to all.


services/s3: Add tests that upon minio

Decription
minio is a widely used s3 compatible service, it could be nice if we run integration tests upon minio everything we have a change on services s3.
This could also avoid problems like https://github.com/beyondstorage/go-storage/issues/860#issuecomment-947460878
Solution
Add a new job under https://github.com/beyondstorage/go-storage/blob/master/.github/workflows/services-test-s3.yml.
The content may be similar with https://github.com/beyondstorage/go-storage/blob/master/.github/workflows/services-test-minio.yml

ping @Joey-1445601153, can you help solving this problem?

ping @Joey-1445601153, can you help solving this problem? We need to solve #924 before.

Yes. We can use #1000  to solve the problem #924.  And I checked your last PR. Maybe we lost a location in the new job .


Colors not rendering in pager

I'm not familiar with rich but the colors aren't rendering in my terminal (tried zsh and bash).
Current Behavior
Pager output of rtd projects nextstrain:
nextstrain nextstrain ESC[1m<ESC[0mESC[4;94mhttps:ESC[0mESC[4;94m//docs.nextstrain.org/en/latest/ESC[0mESC[1m>ESC[0m
(END)

Expected behavior
Output should be this with pretty colors:
nextstrain <https://docs.nextstrain.org/en/latest/>
(END)

Your environment

Version: v3

Fixed in v4.


World of Final Fantasy has rendering issues with dxvk's dxgi

World of Final Fantasy has trouble rendering on AMD with dxvk's dxgi.  The main menu renders correctly, but once you start an actual game (selecting new game is sufficient), the screen is mostly black with some occasional artifacts.  With wine's dxgi, the game renders correctly on AMD.
As a note - this game also has a rendering issue on NVIDIA #1216
Software information
World of Final Fantasy (552700)
Tested dxgi=n against dxgi=b
System information

GPU: AMD RX 570
Driver: 21.1.2
Vulkan: 1.2.168
Wine version: Proton 6.3-5
DXVK version: 1.9

Apitrace file(s)

Game exited immediately when I tried to run with apitrace

Log files

d3d11.log:WOFF_d3d11-working-wine-dxgi.log
WOFF_d3d11-black-screen-dxvk-dxgi.log
dxgi.log: WOFF_dxgi-black-screen-dxgk-dxgi.log
Proton logs: WOFF-black-screen-dxvk-dxgi-proton.log
WOFF-working-wine-dxgi-proton.log

The game is broken so rendering issues on Nvidia are expected, and cannot be fixed.
DXGI normally has no influence on rendering whatsoever so this makes no sense at all; really need some sort of apitrace to debug this.

Game itself works fine here with DXVK's DXGI, at least the prologue. If there's anything else I need to do to reproduce the problem, please give detailed instructions on how to do so.

Thank you for taking a look!  I tried using mesa-git (head at 669b6889e4b0ed4e3ca597dee8a1ab6834bac560) and it visually changed the graphical glitching a bit, but it was still totally unplayable.  The prologue has the bad graphics on my rig, so I don't have any other ideas on how you can repro right now.  I'm pretty sure that the difference is dxgi since the only thing I'm doing is switching between WINEDLLOVERRIDES=dxgi=b and =n
Sorry about the debug logs -- here are some hopefully cleaner logs with mesa-git just in case that is useful.  I also asked someone over here to take a look too  :+1:
WOFF_d3d11-wine-dxgi-mesa-git.log
WOFF_dxgi-dxvk-dxgi-mesa-git.log
WOFF_d3d11-dxvk-dxgi-mesa-git.log

I asked someone else to test the game on AMD and they saw the nearly black graphical glitching with both dxvk's dxgi and wine's dxgi (with mesa-git and a rx580).  So it seems likely that it is just by chance that I'm seeing a difference in behavior when switching dxgi, probably dependent on the exact GPU.  Feel free to close this :)

Leaving a new comment instead of editing the last one.  Turns out they had a typo in the launch options and actually they are seeing the same thing as me - switching back to wine's dxgi fixes the graphical failure.  So the failure does seem to be happening only with dxvk's dxgi.  I have a feeling the difference from what you are seeing could be explained by the GPU since we both have similar models (rx580 and 570) vs your 6900XT.

Can you try the woff branch (this build)?
This is provides a really dirty hack for the Nvidia problem, but it's the only thing that's actually going wrong on the DXVK side of things. I'm not seeing any other relevant Vulkan validation errors, which are not GPU-dependent. The game does not change behaviour based on the DXGI implementation as far as I can tell.

Edit: Actually managed to reproduce this on the Renoir APU in my laptop, the new branch fixes it there as well.

@doitsujin That build fixed the problem for me as well!  I dropped it into Proton 6.3-5 and WOFF was rendering correctly (with dxvk's dxgi of course).  Thank you!

Cool, gonna merge that then.


Add data prop - quick-and-dirty migration

Suggesting a small change to your post here https://github.com/sveltejs/kit/discussions/5774#discussioncomment-3292707_
export let data;
let { foo, bar } = data;
$: ({ foo, bar } = data); // so it stays in sync when `data` changes

This triggers every time one of the props changes. Expected behavior would be for it to trigger when data changes. Definitely appreciate the quick hack, saved me tons of time. Here's an alternative I'm proposing that fixes the issue I mentioned.
export let data;
let { foo, bar } = data;
const syncData = (d) => ({ foo, bar } = d);
$: syncData(data);

People should obviously just move to the new format, but in the meanwhile, this should prevent others from spending hours debugging incompatible setups.

CC @Rich-Harris in case it gets buried over time.

This triggers every time one of the props changes.

I'm not so sure this is the current behaviour. It only tracks when data is re-assigned and not the object properties.


update for bazel 0.6.0

What this PR does / why we need it: addresses a couple of issues that fail the build when updating bazel to 0.6.0
*Which issue this PR fixes:
fixes:
[vbatts@getdown] (master) ~/src/istio.io/pilot$ bazel build //...
ERROR: /home/vbatts/.cache/bazel/_bazel_vbatts/4cef8fba7ce23e923fa298b99fb665e8/external/io_bazel_rules_go/go/private/binary.bzl:226:48: name 'lib' is not defined (did you mean 'libs'?).
ERROR: error loading package '': Extension 'go/private/binary.bzl' has errors.
INFO: Elapsed time: 1.107s

and
[vbatts@getdown] {master *} ~/src/istio.io/pilot$ bazel build //...
ERROR: /home/vbatts/src/github.com/istio/pilot/WORKSPACE:452:1: Cannot redefine repository after any load statement in the WORKSPACE file (for repository 'com_github_google_protobuf').
ERROR: Error evaluating WORKSPACE file.
ERROR: error loading package 'external': Package 'external' contains errors.
INFO: Elapsed time: 0.063s

Special notes for your reviewer:
With the update to bazel 0.6.0, there were pilot build failures due to syntax in the commit of rules_go used. This updates to latest master.
Also, no git_repository can be done after load().
Release note:

Hi @vbatts. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

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

/assign @kyessenov

@vbatts: you can't request testing unless you are a istio member.

In response to this:

/assign @kyessenov

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

/ok-to-test

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

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
78d439205328b1ac0e0c56d1e6b0c29b25ac8073
link
/test pilot-presubmit

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

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

Test name
Commit
Details
Rerun command

prow/pilot-presubmit.sh
78d439205328b1ac0e0c56d1e6b0c29b25ac8073
link
/test pilot-presubmit

prow/pilot-e2e-smoketest.sh
78d439205328b1ac0e0c56d1e6b0c29b25ac8073
link
/test pilot-e2e-smoketest

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

rebased on master. PTAL.

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

Test name
Commit
Details
Rerun command

prow/pilot-e2e-smoketest.sh
78d439205328b1ac0e0c56d1e6b0c29b25ac8073
link
/test pilot-e2e-smoketest

prow/pilot-presubmit.sh
7afaf2f6e27e14803490e77bc73486f82690c711
link
/test pilot-presubmit

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

you need to make changes to test-infra first to create a new prow image with bazel 0.6
before this PR can pass the build

Yeah we would need to update the image running the test first, but that will impact other PRs. Have you tried with 0.6.1 ?

There's a PR in mixer side too (https://github.com/istio/mixer/pull/1423), I like the dependencies to be aligned well. More specifically, the sha of rules_go should be the same, and also use of proto_register_toolchain would be good.
I also think that gazelle in the new rules_go also changes the BUILD files too regarding importpath= param.

/retest

@jmuk aligning requires sharing bazel repositories (e.g. what I tried to do with API changes). That got blocked by envoy rules. Once that gets fixed, we'll redo sharing via api.

/lgtm

Has rules go sha been updated?

The commit has, or do you mean another checksum?
On Fri, Oct 13, 2017, 18:24 Shriram Rajagopalan<EMAIL_ADDRESS>wrote:

Has rules go sha been updated?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/istio/pilot/pull/1382#issuecomment-336581669, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAEF6bJ_2GKXGOyhkGG_-7H12ncswopOks5sr-MlgaJpZM4PsI8k
.

Build with bazel 0.5.3 always failed, so we will not support 0.5.3? If this case, we should also have the doc updated. Also it would be great to have a release note for this for such upgrade. @vbatts @rkpagadala
root@pc002:~/go/src/istio.io/pilot# make build
WARNING: /root/.cache/bazel/_bazel_root/1745129434edd1c4aecf285cdde2d234/external/bazel_tools/tools/build_defs/pkg/pkg.bzl:196:9: pkg_tar: renaming non-dict `files` attribute to `srcs`
ERROR: /root/go/src/istio.io/pilot/tools/version/BUILD:3:1: in go_library rule //tools/version:go_default_library:
Traceback (most recent call last):
	File "/root/go/src/istio.io/pilot/tools/version/BUILD", line 3
		go_library(name = 'go_default_library')
	File "/root/.cache/bazel/_bazel_root/1745129434edd1c4aecf285cdde2d234/external/io_bazel_rules_go/go/private/rules/library.bzl", line 33, in _go_library_impl
		ctx.toolchains["@io_bazel_rules_go//go:toolchain"]
key "@io_bazel_rules_go//go:toolchain" not found in dictionary
ERROR: Analysis of target '//tools/version:go_default_library' failed; build aborted
INFO: Elapsed time: 0.326s
FAILED: Build did NOT complete successfully (0 packages loaded)
Makefile:28: recipe for target 'build' failed
make: *** [build] Error 1

Created a PR here https://github.com/istio/pilot/pull/1482 /cc @vbatts @rshriram


Adding a copy feature

Whenever I click on any generated colors it should automatically copy the hex code.

Also there should be a small button icon which when I click should copy Hex, RGB or HSL codes very easily.

I can do this please assign this to me and add the hactoberfest and gssoc-extd label

Hi @mohtasheem135
Actually I was opening a similar issue which is now here: https://github.com/utk09-NCL/color-palette-generator/issues/25
Closing this for now and we can chat about the contribution on the other one!
Thanks again!


2 x false "name of Record is not valid" (AA0072) diagnostic reported for app.json - 1 per codeunit with TableNo?

Yet another case of a diagnostic nonsensically being reported against app.json:

I don't think this happens all the time, but nor do I know what would cause it in this specific project, so I just add it to the pile; obviously, let me know if I can help investigate any further.
AL Language 6.1.352568

You get this warning one time for each codeunit with the parameter TableNo

Indeed, the project from which I reported this does have 2 codeunits with TableNo parameter, and commenting out one of them (while of course causing lots of new errors) does reduce the count reported 'in' app.json to one. Thanks for that added info!

Hi, @dtkb  could you try again with the latest version? (https://github.com/microsoft/AL#al-developer-preview-builds) .

This issue has been closed because it needs more information and has not had recent activity. Please open a new issue if you believe this has not been resolved and reference the current issue.

I didn't have time to test with the preview build, but it seems that as of AL extension 7.1.441584 in VS Code the spurious warnings are not emitted, so thanks!


I cannot choose [--best_checkpoint_metric BLEU]

In translation task, I have to choice "best_checkpoint_metric".
But, my goal is to get the best BLEU score model in validation dataset.
So, I want to choice BLEU (not "loss") as "best _checkpoint_metric", because the lowest "loss" score model in validation dataset does not necessarily perform the best from the viewpoint of BLEU.
But  I cannot choose BLEU as best_checkpoint_metric.
Or, is it natural to use the lowest loss model's BLEU score as metric in NLP conference's paper??

Currently there is no way to use BLEU as your validation metric.  It is common to use lowest validation loss for choosing checkpoints.


Using database secrets from environment

Closes #26

 (2) Work with Web team to implement a solution for Secrets


Update IPP.php

quickbooks/v3-php-sdk/src\Data\IPP.php does not comply with psr-4 autoloading standard. It will not autoload anymore in Composer v2.0

Please can this be merged. Composer 2 has been upgraded and this is causing issues.

Any updates?

Should this be updated on this line too?
https://github.com/intuit/QuickBooks-V3-PHP-SDK/pull/361/files#diff-8d5f950d77a75e300294395ad65937126d90695bd8dc3285855c26326023ab5bR26

Sorry, I meant this line:
https://github.com/intuit/QuickBooks-V3-PHP-SDK/blob/aa377f9b5e54dc54eba652fc30255335a790ea57/src/Data/IPP.php#L26

This should be fixed with the release: 6.0.0


🚀 - Support Single Character Placeholder Definition

Which package(s) are relevant/related to the feature request?
@maskito/core, @maskito/kit
Description
Hello Maskito Team,
I'd like to propose an enhancement to the Maskito library to allow specifying a single character as a placeholder, instead of requiring a fully defined placeholder string.
Proposed Feature: Introduce a placeholderChar option that lets us define a single character to be used throughout the entire mask.
Example:
Maskito({    mask: '999-999',    placeholderChar: '*' }); // Allows using '*' instead of the default placeholder
In this example, * would be used automatically in place of all mask characters, generating a placeholder like -. This would improve usability and make placeholder configuration more concise.

Hello, @rizirf-connect !
Thanks for your proposal.
Unfortunately, we don't have plans to implement it for some reasons.
Firstly, it is impossible to implement it for RegExp mask expression.
It is possible only for Pattern mask expression. I am not sure that partially implemented feature is a good idea.
Moreover, the already existing approach to define Placeholder works fine for both types of mask expressions.
Secondly, it is too simple to implement the such behavior for Pattern mask expression without augmenting logic inside Maskito:
const PLACEHOLDER_CHAR = '*';
const mask = [/\d/, /\d/, /\d/, '-', /\d/, /\d/, /\d/];
const placeholder = mask.map(x => typeof x === 'string' ? x : PLACEHOLDER_CHAR).join('');

Our team does not prefer to add additional flags to the codebase without real necessity.
Adding additional property for Maskito only for one-line logic – too much for the light-weighted library.

Hello, @nsbarsukov !
Thank you for your prompt and thorough response to my proposal. I understand the limitations and appreciate the rationale you've provided regarding the placeholder implementation.
However, would it be possible for you to provide an example of how to implement a ControlValueAccessor directive for Maskito?
Your insights would be greatly appreciated.
Regards & Thanks!

@rizirf-connect Hello!
Maskito is already compatible with built-in DefaultValueAccessor.
Just put [ngModel] / formControl on native <input /> – everything should work.
If you want to augment DefaultValueAccessor (or any other already existing CVA) with "unmask"-logic, see this example:
https://maskito.dev/frameworks/angular#unmask
If you want to implement custom CVA. There is no limitations here. Just follow to any existing guide how to implement ControlValueAccessor.
maskitoTransform is useful utility to use inside writeValue.


ENH: ./nb/000-splinter-notebooks.py.ipynb: Jupyter notebooks for Splinter

GitHub renders .ipynb files (*currently only w/ the desktop interface)
Nbviewer renders .ipynb files

@westurner  I did not understand what this issue is about. can you elaborate? thank you

Would it be useful to write and PR jupyter notebook[s] in a top-level ./nb directory?

... The [docs] Makefile then would have a step like:
buildnbs:
  # build jupyter notebooks for :docs
  findnbs | makeindex.py --readme > README.rst
  findnbs | makeindex.py --html > index.html
  findnbs | xargs -I% jupyter-nbconvert --to html %
  findnbs | xargs -I% jupyter-nbconvert --to python %

Sort of like https://github.com/westurner/notebooks/blob/gh-pages/makeindex.py ... I should really factor this out ... - [ ] REF: makeindex.py -> [projectname]

Closing due to lack of clarity and inactivity.


Leap year but. Please update appdaemon version

Problem/Motivation

(Why the issue was filed)

Expected behavior

(What you expected to happen)

Actual behavior

(What actually happened)

Steps to reproduce

(How can someone else make/see it happen)

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

No content in issue.
Closing, feel free to open a new one with content.


section references are case sensitive

It appears that:
{{section 9 of RFC9019}}

does not work, while
{{Section 9 of RFC9019}}

does work.
The error that comes out is in xml2rfc, and is pretty obscure.

Indeed, kramdown-rfc is case-sensitive.
If it doesn't recognize any special syntax, it just ships the reference as is to xml2rfc.
Do you want this to change (e.g., to case-sensitive, to recognizing "Abschnitt" as well as "Section", etc.; or do you simply kramdown-rfc to emit a message that the reference looks fishy?

Indeed, kramdown-rfc is case-sensitive.
If it doesn't recognize any special syntax, it just ships the reference as is to xml2rfc.

I didn't know.

Do you want this to change (e.g., to case-sensitive, to recognizing "Abschnitt" as well as "Section", etc.); or do you simply kramdown-rfc to emit a message that the reference looks fishy?

I'm not sure.  I think "looks fishy" might be enough.

Fishy message will be in 1.5.1, which I'll push after the frenzy.


[SPARK-34728][SQL] Remove all SQLConf.get if extends from Rule

What changes were proposed in this pull request?

Remove all SQLConf.get to conf in all rules, since all rules extended from SQLConfHelper
Why are the changes needed?

Clean up code.
Does this PR introduce any user-facing change?

No
How was this patch tested?

Existing unit tests.

cc @wangyum

ok to test.

Can one of the admins verify this patch?

There are still some rules that have not been cleaned up:
https://github.com/apache/spark/blob/9e6882feca0800d5d4f9920886cb5dae73bbe1d4/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/CTESubstitution.scala#L34
https://github.com/apache/spark/blob/e3058ba17cb4512537953eb4ded884e24ee93ba2/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/DecimalPrecision.scala#L84
https://github.com/apache/spark/blob/66c5e0132209a5a94f9d7efb5e895f143b0ef53b/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/ResolveUnion.scala#L101
https://github.com/apache/spark/blob/5d9cfd727c21f0f50f92c0236cdeb20f3b9111dc/sql/catalyst/src/main/scala/org/apache/spark/sql/catalyst/analysis/TypeCoercion.scala#L275
https://github.com/apache/spark/blob/32a523b56fc329e858f3a463314c13e3710be5e0/sql/core/src/main/scala/org/apache/spark/sql/execution/adaptive/QueryStageExec.scala#L225

Test build #136027 has started for PR 31822 at commit ead156c.

Test build #136027 has finished for PR 31822 at commit ead156c.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Kubernetes integration test unable to build dist.
exiting with code: 1
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40611/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136027/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40611/

Test build #136029 has started for PR 31822 at commit 096b2da.

Test build #136029 has finished for PR 31822 at commit 096b2da.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136029/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40613/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136037/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40620/

cc @cloud-fan

looks good, let's fix all the places.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40646/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136063/

retest this please

Looks fine, too.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40676/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136093/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136095/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40678/

Rename Remove all SQLConf.get if extends from Rule to Remove all SQLConf.get if extends from SQLConfHelper?

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40684/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136102/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136109/

Kubernetes integration test starting
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40691/

Kubernetes integration test status failure
URL: https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder-K8s/40691/

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40691/

Test build #136193 has started for PR 31822 at commit 10e5128.

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/40775/

Merged to master.

Test build #136193 has finished for PR 31822 at commit 10e5128.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class Abs(child: Expression, failOnError: Boolean = SQLConf.get.ansiEnabled)
case class TimestampAddYMInterval(

Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/136193/


Changed default theme to Source

refs TryGhost/Product#3510

Added Source as a submodule to Ghost
Updated hardcoded instances and protections for casper to include source

@cmraible We should also include the actual git submodule addition (?) in this. You'll need to initialize it locally and then git add ghost/core/core/content/themes/source

@daniellockyer my bad, I thought I had done that but I think the .gitignore blocked me.
When running git add ghost/core/content/themes/source I was getting an error (I think from a git hook): 'Aborting commit due to submodule update. Please unstage the submodule(s) and commit again.'
Got around this by using git commit --no-verify ... and that seemed to work, but just wanted to give a heads up in case that borked anything else up. That was the only change in the commit, so I don't think it would have bypassed any important tests, but just wanted to double check with you.

@cmraible Yeah that's totally cool. That check is just there to stop people committing the submodule in day-to-day operations
I tend to do CI=1 git ... to bypass it myself 😀


Good job adding LiveQuery

I like Parse server because its actually a decent alternative to Firebase

You're welcome @ctalladen78, but I think was mainly the work of @rodrigosmarques. Great effort!


run example.py get error '403 Client Error: Forbidden for url'

requests.exceptions.HTTPError: 403 Client Error: Forbidden for url: https://relay-goerli.flashbots.net/

Goerli is sunset. Recommend using Holesky for test net right now.


[Bug]: Dropdown option invisible but visible in preview

Is there an existing issue for this?

[X] I have searched the existing issues

Description
https://github.com/user-attachments/assets/38afc570-f7b9-416d-a89a-086d57281785
Steps To Reproduce
Label key Js is not wokring which was working earlier
Public Sample App
No response
Environment
Production
Severity
Critical (Broken Production apps)
Issue video log
No response
Version
1.38.0

@gokaco please can I see what your source data looks like so I can debug further, thanks.

@gokaco please can I see what your source data looks like so I can debug further, thanks.

Something like
[
  {
    "liveClassThumbnailURL": "https://res.cloudinary.com",
    "cover": {
      "vidURL": "https://res.cloudinary.com"
    },
    "email"<EMAIL_ADDRESS>    "name": "Kartikeya Goswami",
    "imgURL": "https://res.cloudinary.com",
    "password": "abcdefg",
    "roles": [
      {
        "roleId": "uuid"
      },
      {
        "roleId": "uuid"
      }
    ],
    "subCategory": "COACH",
    "expertise": [],
    "trainerId": "uuid",
    "category": "category",
    "description": "description"
  }
]

Thanks @gokaco. The label key cannot be the joined string you are using in the video, the label key needs to be one of the keys from your object above, e.g name. Add. name as the label key and see if it works.

@gokaco Did above comment help resolve your issue?

Thanks @gokaco. The label key cannot be the joined string you are using in the video, the label key needs to be one of the keys from your object above, e.g name. Add. name as the label key and see if it works.

@jacquesikot But earlier this was working. And this issue started happening from some days only. How it was working earlier? Have any changes been made in the new release?

@gokaco We don't think anything has changed in the recent release. The key field should be one of the keys in your JSON. This should work for your use case, please let us know if there's anything that is not working.


iOS 8 support

This is more of a question than an issue.
Could you point me to what would have to change to make this iOS 8 compatible. And I don't mean that the feature has to work, just to prevent the app from crashing.
I could work an a PR if you give me some pointers.

Hi @pietropizzi! Take a look at #12 and #19. This is something we've attempted to do before but never made much progress. Good luck! Let me know if you have any questions. I'll keep this ticket open for a while.


[SP-3695][PDI-16339]--Saving a job with a duplicate name makes PDI work inconsistently

fixed, added unit test

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f ui/build.xml clean-all resolve jacoco && ant -f ui/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  ui/src/org/pentaho/di/ui/spoon/delegates/SpoonJobDelegate.java
  ui/test-src/org/pentaho/di/ui/spoon/delegates/SpoonJobDelegateTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.ui.spoon.delegates.SpoonJobDelegate

Branch Change:  + 1.77%
Complexity Change:  + 2.65%
Instruction Change:  + 1.38%
Line Change:  + 1.86%
Method Change:  + 6.84%


Make library compatible with babashka

Nextjournal is using this library. I was asked to make this library compatible with babashka.
I wonder if you are willing to accept this back into the original library or if we should maintain our own fork.
I'd be happy to discuss next steps if you're not happy with something in this PR.
I've made the following changes that do not affect the behavior in CLJ and CLJS (with regards to the unit tests at least):

In babashka a multi-hash is a defrecord rather than a deftype (bb does not support deftype at the moment)
Added support in babashka itself for overriding toString on a record (will be available in next release)
Added algorithm, digest and length API functions, rather than going through ILookup via keywords. Implementing ILookup isn't supported by babashka yet. I also added these API functions for CLJ and CLJS, since I don't think it hurts to have them as an alternative for invoking these functions via keywords (it might even be seen as a tad more idiomatic). The tests use these new API functions. I can add back some tests to exercise the ILookup access which I realize isn't tested anymore.
Upgraded to mvxcvi/alphabase "2.1.0". Not sure if this should be done in project.clj since I'm not sure what effect this has on compatibility with previous Clojure versions, but at least that newer version runs well with babashka.
Added bb.edn so you can easily run babashka tests with bb test.

Feel free to squash-merge all commits into one single commit. I can also do this prior to merge if you want.
Locally all tests pass:
$ bb test

Testing multihash.core-test

Testing multihash.digest-test

Ran 11 tests containing 391 assertions.
0 failures, 0 errors.

$ lein test

lein test multihash.core-test

lein test multihash.digest-test

Ran 11 tests containing 392 assertions.
0 failures, 0 errors.

$ lein cljs-test
WARNING: :preloads should only be specified with :none optimizations

;; ======================================================================
;; Testing with Phantom:

Testing multihash.core-test

Ran 8 tests containing 370 assertions.
0 failures, 0 errors.

@greglook I wonder if you've had time to consider this PR.

closing due to inactivity, archiving repo


[GHSA-c25h-c27q-5qpv] Keycloak leaks configured LDAP bind credentials through the Keycloak admin console

Updates

Affected products
References

Comments
update the issue for this cve on GitHub: https://github.com/keycloak/keycloak/issues/30434
and 8 patch commits for diverse versions (including backporting):
https://github.com/rmartinc/keycloak/commit/02bb60505f8c4472d7564f71a8eb38450f861fd5
https://github.com/rmartinc/keycloak/commit/768f5d1d48a2ad981c08067104c8e10eb433cd6c
https://github.com/rmartinc/keycloak/commit/d30512c07aa0f225c30e2c9b49ac16912a91ba13
https://github.com/rmartinc/keycloak/commit/446476adf9ad320278104f38684779d2a83c318a
https://github.com/rmartinc/keycloak/commit/81336a510fcd03e804c9140c58ae7c390c0fe098
https://github.com/keycloak/keycloak/commit/bde8568d4174a7072f7c7bb507d2c7d05824b1a6
https://github.com/keycloak/keycloak/commit/1f56a9e48bf96c3bcb18dfc6cd93e3dd16f281f1
https://github.com/keycloak/keycloak/commit/0d0530046b9cb4b0d74d2fdefc9bd04f1d20cac0
The patch commits are all shown in the issue, and commit msgs also show their intention.

Hi there @rmartinc! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory


Add OAM workload and trait reconcilers

Description of your changes

This PR moves the OAM Workload and Trait reconcilers from https://github.com/crossplane/addon-oam-kubernetes-remote. We should not merge until we figure out the crossplane circular dependency this introduces, which is a result of defining the WorkloadReferencer interface for Trait here.
Checklist

I have:

[x] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.
[ ] Updated any relevant documentation, examples, or release notes.
[ ] Updated the RBAC permissions in clusterrole.yaml to include any new types.

@negz I have updated with the implementation of TypedObjectReference there are quite a few places where this turned out to be appropriate. This is a fairly significant (breaking, depending on how you define it) change, and will require updates to method generation in crossplane-tools and is changing APIs (though not in a way that should have a real effect on end users) in numerous places.

@hasheddan Would it be easier to proceed with this PR if we only updated OAM to use TypedReference for the time being? We could replace our many instances of *ObjectReference in a future PR.

@negz I thought about that, but I just looked through provider-gcp and I actually feel as though this would be pretty mechanical with the updates. I am usually one to push for doing something early if we think it is inevitable, but would be happy to wait if you feel strongly :+1:

@hasheddan If you're signing up to push through all the changes I'm happy either way!

@hasheddan If you're signing up to push through all the changes I'm happy either way!

Actually, on second thought I'd feel more comfortable reviewing and moving forward this if we broke it up into two changes. I'm not sure about some of the changes we're introducing here (e.g. variants like TypedNamespaceNameOf), and I don't think there's an urgency to replace all existing instances of *ObjectReference.

@negz updated :+1:

Thanks @hasheddan!


Upgrade Rakudo version used in Appveyor

We should try to base our AppVeoyr tests on the latest Rakudo Start version.

thanks


fix: Update obiDialogParser to use code from CL-Model

Small change to use CL-Model code in https://github.com/microsoft/ConversationLearner-Models/pull/198 (addToLGMap -> CLM.ObiUtils.parseLGString)

Yes - I was waiting for an LGTM on the Model PR first  :)

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

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix #500: Webpki roots

This works to resolve CA issues in static binaries.
I added two new features:

acme-native-roots which acme aliases for backwards compatibility.  I left acme in the documentation though, maybe I should replace that with acme-native-roots?
acme-webpki-roots which selects webpki roots

I think this is similar to what other libraries do.  I thought this was clear and would provide a path for doing manual roots too in the future.  However, if you don't select either feature, there will be a compile error when building the AcmeClient.
An alternative is to have acme-webpki-roots be a toggle, where if it's missing native roots are used and if it's enabled native roots are disabled (and webpki roots are enabled).  This restricts it to exactly two modes however.

Thanks a lot, I replaced acme in the docs with acme-native-roots.

Awesome, thank you!


Hold key not working

Hi,
When I try the hold key option I think he press multiple time.
I use the pannel with Star Citizen, I know its not made for it but when I need to press for one second a key he execute the commend when I press and release the key (example I just go out of the chair and don't eject).
Thanks ^^'

Has it worked with previous versions of DCSFP?
It works by sending a stream of Key "x" events when you hold down a button. It differs then how the program interprets it. Windows key API:s are little of a jungle imho.
Have you tried the other Windows API, you can select it from the Settings menu.

So you keep the key pressed but Star Citizen interprets it like a single key press?

I think, I use the Ctrl buttons for the assign who need to stay press like the quantum travel and the ejection, but if I use another key it's don't work

Yup, tried SHIFT + A (continuous) and it produces only small "aaaaaaaaa". I will investigate.

I did a new compile, didn't really make any changes to the actual Windows API call. Anyways I can now produce AAAAAAAAAAAA using the "Keep pressed" option. Try the latest release. Wonder if this was some kind of fluke error? I hope so. :)

Is a bit hard testing CTRL+Key, don't know how to verify it. Shift+Key is easy.

Okay =) thanks a lot, I will try it Sunday ^^

Hi I am sorry but how to download the new compil?

I think is not working, when I use the hold shif+a key its work on the pannel but in game its not working

OK. I have to check what the hell differs between and event made by DCSFP and that of a keyboard key press.

I think I found something that could be the problem using Spy++. Can you head over to our Discord server and I will share a link to you where you can find the test version. I don't want to make release for this.
https://discord.gg/5svGwKX

My nick is ArturDCS.

I spent more than 1h to make a fix, to find what could be wrong and you don't care testing it?

Sorry I just have bigs problem in this time, I am really sorry about that, I can have my computer only 4/5 day ^^' I am really sorry

OK still not working. I will have a look at it again. Can't figure it out straight away as Spy++ showed same Windows messages now between keyboard and DCSFP. But I will look at it again.

@jckaboom Did you get it to work also with using VKNULL? Missed your post here.

https://github.com/DCSFlightpanels/DCSFlightpanels/wiki/Emulating-a-key-being-pressed-down-continuously


Bugfix/report template

Fixing quality report template

Pull Request Test Coverage Report for Build 331347616

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 55.647%

Totals

Change from base Build 329910313:
0.0%

Covered Lines:
404

Relevant Lines:
726

💛  - Coveralls


Bottles published but revision not merged

We have regularly cases where bottles are published but the corresponding revision is not merged to homebrew-core. The latest is opencv in https://github.com/Homebrew/homebrew-core/pull/124578
We're left in a state that the test-bot alone cannot recover from:
Error: docker://ghcr.io/homebrew/core/opencv:4.7.0_2 already exists!

Published 3 days ago. But the corresponding revision was not committed to homebrew-core, so any revision bump will now fail on bottles publishing.
How can we make the bottles publishing atomic? I.e., ensure that bottles are published if and only if the revision is committed?

How can we make the bottles publishing atomic? I.e., ensure that bottles are published if and only if the revision is committed?

I don't think we really can do this without changing our workflow (which we should probably do).
Eventually we really need to get to a "bottle commits are pushed to PRs and only actually published when they are merged into master".
The public beta for the new merge queue feature could help us here. You can have additional CI jobs which are only run when something is "queued for merge" which, in our case, could be the job that does the actual publishing and then merges it to master only when the publishing succeeds.

But the corresponding revision was not committed to homebrew-core, so any revision bump will now fail on bottles publishing.

Zero blame here but: any ideas why this happened?
CC @Homebrew/maintainers @Homebrew/core for input and thoughts here.

Zero blame here but: any ideas why this happened?

I'm guessing GitHub packages outage

I'm guessing GitHub packages outage

Can confirm this is what happened.


tx.Rollback() panics

When the connection to Oracle DB is lost, the rollback panics.
This is what I've done without having connection to the DB:

Open a transaction: tx, err := conn.Begin(). This works, although I think it should fail
I try to run a SQL query: tx.QueryRowContext(...)
This gives the error golang.org/x/sys/unix.ECONNREFUSED (111) = 0x0
Then I rollback: err := tx.Rollback(). This panics with invalid memory address or nil pointer dereference

I put a protection to avoid call transaction when connection closed
please test again and see if it is fixed

Perfect, it's returning the correct error now, thanks.
I found a related issue. When the connection drops and a client tries to use it, it is closed and it can't be used anymore. That forces me to re-open the connection. I think it would be better if the connection doesn't definitely closes so that when it is restablished, it can be used without re-opening. Can this be done?

for now what I found from other oracle driver when connection lost and return back you should re-open with with full open steps
may be there is advanced feature in oracle that let you regain the lost connection without calling for all step of open process

Okey thanks for  the help!


Add an extra step in 'Build Actions for the Google Assistant (Level 1)'

After 6. Build > Actions in the left nav. if the user does not have any actions they need to click the Add your first action button in order to show the Create Action dialog referred to in 7. On the Create Action dialog...

Due to more than 3 months of inactivity, this issue is being closed.
If you think this resolution is in error, please re-open the request with fresh information.

Due to more than 3 months of inactivity, this issue is being closed.
If you think the resolution is in error, please re-open the request with fresh information.


wandboard quad c1 etnaviv

Hi,
etnaviv driver on 4.5 branch use to work very well on debian stretch, however I tested 4.6 and 4.7, the driver loads but a simple cursor is blinking on the upper left of the screen.
by the way, I had to append -armmp to version.sh because dpkg refused to install the build package if the flavor was wrong.
Thank you so much for providing theses easy to use build scripts.
Cheers
Pierre

hi @duperray
yeah i've fallen behind on my imx etnaviv testing. (v4.5.x was when i was testing it the most)
Double check that you are using:
https://github.com/austriancoder/libdrm
and the newest mesa branch:
https://github.com/etnaviv/mesa/tree/12.0_etnaviv
as i know debian stretch had a newer version of libdrm come down.
Regards,

Hi,
I was completely wrong,
the stretch debian kernel work perfectly well, I'm using console + xorg
there (4.6.3) and your patched 4.7 branch kernel work
also very well.
Sorry for the noise... I don't know what happened!@#%
for the record, I have libdrm 2.4.68 on debian stretch.
for mesa, I did not test anything (11.2.2 available).
As soon as 12.0 will be packaged for stretch, I will try acceleration.
But wait a minute, there is no 3d games for arm? does it?
anyway, thank you very much to take time for you last reply.
Cheers,
Pierre
PS: you probably own many wandboard but if I can test on debian (as you
seems to use ubuntu) for you or just help in anyway in "basic" testing
just ask :)
On 07/19/2016 07:23 PM, Robert Nelson wrote:

hi @duperray https://github.com/duperray
yeah i've fallen behind on my imx etnaviv testing. (v4.5.x was when i
was testing it the most)
Double check that you are using:
https://github.com/austriancoder/libdrm
and the newest mesa branch:
https://github.com/etnaviv/mesa/tree/12.0_etnaviv
as i know debian stretch had a newer version of libdrm come down.
Regards,
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/RobertCNelson/armv7-multiplatform/issues/31#issuecomment-233704809,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABZavxWeQyHLyDXdJdGibBqqeAROsz6Nks5qXQgEgaJpZM4JP84H.

Hi,
the packaged kernel can't install on debian, because uboot need the dtbs to be in /usr/lib/linux-image-${uname -r}/
Another point is that dpkg refuse to install the package if you don't provide the correct flavor `-armmp'
in the package name (easy workaround is to put BUILD="-armmp" in version.sh).
thank you so much for your work
Cheers
Pierre

@duperray not sure what your complaining about, if you use debian's u-boot and flash-kernel packages you will have issues with my repo..
Either use the "netinstall" i provide
https://github.com/RobertCNelson/netinstall
or the step by step directions here:
https://eewiki.net/display/linuxonarm/Wandboard
Or you can just wait till Stretch+1 when debian integrates all of this. ;)
Regards,

Hey robert, I'm not complaining ;)
Thanks for the links, I did not realize I had to use a customized netinstall for your armv7-multiplatform repo.
I only installed with the jessie installer thru the serial link and later upgraded to stretch.
I tested a few of your kernels the 4.5 was a good one for me because it provided video.
unfortunately, after switching to the stock debian 4.8 kernel, video broke again.
So I tested (I have a wandboard quad rev1c) your 4.8.x, same pb, tryied the 4.9.x, same pb, now
using your 4.10.x and TADA, video again :)
the only thing is, I have to dpkg -x the builded .deb linux image and manually copy the dtbs in /usr/lib
see https://packages.debian.org/stretch/armhf/linux-image-4.8.0-2-armmp/filelist
(the official stretch 4.8 kernel put *.dtb in /usr/lib/linux-image-`uname -r')
or uboot during installation of the kernel complain about this (uboot, not me ;)
How heavily did you change the netinstall? it's completely different project from the debian netinstall?
Regards,
Pierre

So the netinstall is just a wrapper around debian's debian-installer..

It provides its own u-boot
provides a mainline kernel (with patches for enablement of devices not support by debian yet)
preseed file with a generic default partition layout
adds repos.rcn-ee.net
neuter's flash-kernel

flash-kernel: this is the pain, unless your board is supported by debian, flash-kernel goes out of it's way to do things "it" want's to do.. So we override the flash-kernel database, this let's us "just" install the linux-image*.deb, and allow a grub inspired script setup the vmlinuz/dtbs in the correct location in the boot directory.
flash-kernel: it's what is forcing "armmp"..
flash-kernel: https://sources.debian.net/src/flash-kernel/3.73/db/all.db/#L1381
Machine: Wandboard i.MX6 Quad Board
Kernel-Flavors: armmp
DTB-Id: imx6q-wandboard.dtb
Boot-Script-Path: /boot/boot.scr
U-Boot-Script-Name: bootscr.wandboard
Required-Packages: u-boot-tools

Now look what we patch in:
https://github.com/RobertCNelson/netinstall/blob/master/lib/flash_kernel/all.db#L2460
Machine: Wandboard i.MX6 Quad Board
Method: generic

and here's our linux-image post install:
https://github.com/RobertCNelson/netinstall/blob/master/lib/shared/zz-uenv_txt
in the most generic case, it just updates uname_r in /boot/uEnv.txt, so U-Boot knows what vmlinuz/dtb to load..
Regards,

Robert,
Thx for the explanation, I have a long way to go but I think I will follow your advice and wipe out my mmc and give a go to your netinstall. Hopefully after some learning I could do more useful comments and testing on the wandboard.
Thanks again for your time.


No data to support your claims?

This claim is made:

(CACAO) is a highly optimized adaptive sampling ambient occlusion implementation.

But there's no data available how much better it does vs Intel's ASSAO or Nvidia's HBAO+ or VXAO.
Will such data be made available on a later date?

HBAO, ASSAO, and CACAO are essentially very close technologies. VXAO (and other voxel-based AO) is superior to all of them, and CACAO, HBAO and ASSAO are all the same level of quality.

Ahh, that makes sense! Thanks for letting me know!


Update repository after transfer

See https://github.com/senzing-garage/garage-roadmap/issues/3

Pull requests:

https://github.com/senzing-garage/aws-cloudformation-database-cluster/pull/85
https://github.com/senzing-garage/aws-cloudformation-database-cluster/pull/87


MVVM?

Currently the app is written with a lot of business logic in page behinds, rather than with an MVVM architecture.  This will potentially limit the extent to which code can be tested as UI is tightly coupled to business logic.  Is there any interest in migrating the app to an MVVM architecture?

Absolutely not:)

Alright then


Added vcpkg support

Use vcpkg for loading opencv and sse2neon

OpenCV compilation with vcpkg fails with obscure errors, don't know how to fix it, so closing this PR


cleanup noop prefixes in _pool

make expand dim=None as noop (in addition to -1). then slice, reshape, expand in _pool can share the same noop prefix

replaced the long reshape -> expand -> reshape with repeat
i think the slices can be replaced by shrinks after repeat, will do in a separate pr to see if we can remove all use of slice


Draft: Vendor Pyodide into workerd

This vendors a copy of Python into workerd. Only stock Python + Pyodide's ffi is included, no packages. There's a hello world example here:
./bazel-bin/src/workerd/server/workerd serve --verbose samples/pyodide/config.capnp

@dom96

Hmm, what's the reason for vendoring this?
I would sort of expect that we'd have an entirely separate repo for pyodide from which we'd occasionally produce a release build of the Wasm module, and then we'd embed those release builds into the workerd binary separately. Depending on how these builds work and the ABI compatibility story, I could even imagine that it's important to do it this way to make sure we don't introduce an ABI incompatibility due to the wasm module inadvertently being compiled in a different way?

We don't intend to merge this, it's just to allow us to prototype faster.


hidpp10: convert resolution according to sensor type

Here is a proposition for handling the different resolution formats. It was tested with G500 and G500s only.
You may want to change the way the device info is retrieved (maybe in the base hidpp_device or in another function).
For invalid resolution values, hidpp10_sensor_to_dpi silently returns 0. Because of disabled dpi modes, it would output a lot of error messages if I logged errors there.

We had a private discussion (sorry for not talking about this earlier) last Wednesday with Peter regarding the retrieval of the DPI values.
The outcome of it was that we would prefer to store this information in the HWDB. The rational being that it's trivial to add something in the hwdb and would allow to support new hidpp10 devices (if there are any left) without recompiling the library.
For some sensors, it's rather easy. We can just put the whole list of accepted values in a udev tag (RATBAG_HIDPP10_DPI_LIST) for instance. Then in drvhidpp10_probe, we retrieve this list, parse it and store it as a table in hidpp10_device. Then, when we have 0x8n, we just take the n-th element in this table.
By looking at your patch I realize that some more recent sensors will be more of a pain to handle because of the number of values. HIDPP10_SENSOR_S9500 and HIDPP10_SENSOR_S9808 are the ones I am thinking about, and for them, we might want to encode this in the hwdb in a different way. This could be a combination of RATBAG_HIDPP10_DPI_MIN, RATBAG_HIDPP10_DPI_STEP, RATBAG_HIDPP10_DPI_MAX. Or in one udev property: RATBAG_HIDPP10_DPI_PARAMETERS, or even just a magic setting RATBAG_HIDPP10_DPI_TYPE which contains either HIDPP10_SENSOR_S9500 or HIDPP10_SENSOR_S9808.
Any thoughts?

Because of the variety of resolution encoding, I think RATBAG_HIDPP10_DPI_TYPE would be the best for the driver. But the min/max/step/list would make more sense for the UI. Accepting any value and rounding it seems bad when the step is too wide like with the G5 (or even the G9). Also silently clamping values to the sensor range is a problem.
If the "step" value is for UI only, it may be different from the actual dpi step. The G500 step (400/17 ~ 24 dpi) is not very user-friendly. LGS use a 50 dpi step instead. Rounding with an accuracy of +/- 12 dpi looks fine to me, especially given that the actual sensor resolution change more than that from the type of surface the mouse is used on.

I wonder if the A6090 is really the correct sensor for the G9. I found it on wikipedia and a forum. But the available data sheet (See register 0x09 "Resolution" on page 28) does not match the resolutions @phomes told me. Also that would be the only non modified Avago sensor used by Logitech (G9x/G500 use S9500 instead of A9500, ...).

there's two issues here that we need to fix: how to we export this to the next layer (i.e. what's the API that tells the caller which resolutions are supported) and the internal bit: what resolutions does the device actually support. so maybe we should start thinking about the external API first, then worry about the internal bits which we can change at any time anyway?
a general comment: if we have a mix/max with a step size, this should imo be a single property with a specific format, e.g. 50:8200@50 or so, not split across multiple properties. the latter would make the hwdb unwieldly quickly.

so maybe we should start thinking about the external API first, then worry about the internal bits which we can change at any time anyway?

Though I agree there are indeed two problems, I think @cvuchener tried to solve the internal one in his pull request, and I was only commenting on this. The udev props "RATBAG_*" should not be used in any ways by the clients of the library.
The external API problem should be solved through an API call (ratbag_get_resolution_min|max|steps or any other API), but the internal one (what does 0x84 means for which device) should be IMO solved through a udev prop. We should support both the DPI list (the matching values are not linear in case of the S6006) and also the min/max/step to be able to feed the driver with the correct values while parsing the device.

a general comment: if we have a mix/max with a step size, this should imo be a single property with a specific format, e.g. 50:8200@50 or so, not split across multiple properties. the latter would make the hwdb unwieldly quickly.

ACK for that

right, my argument here is that if we figure out how the external API should look like, it may give us a hint on how we want the internal bits hooked up. for example, depending on the external API it may be simpler to ignore the min/max/step option and just have an explicit list. or it may not be :)

Please see pull request #47 for the udev approach.

if we figure out how the external API should look like, it may give us a hint on how we want the internal bits hooked up

No. We want to be able to parse whatever comes from the device, so we need to be able to understand every possible value. Thus, the udev rules are independent from the external API.

Pull request #47 has been merged, closing this one.


Fscherf/topic/multiple bugfixes

@maratori: I found some bugs today while using 1.5. Maybe you can take a look.

Codecov Report

Merging #46 (8e39513) into master (86650ac) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##           master      #46      +/-   ##
==========================================
- Coverage   32.06%   32.04%   -0.02%
==========================================
  Files          67       67
  Lines        4170     4172       +2
==========================================
  Hits         1337     1337
- Misses       2833     2835       +2

Impacted Files
Coverage Δ

lona/events/input_event.py
11.53% <0.00%> (-0.23%)
:arrow_down:

lona/html/abstract_node.py
54.73% <0.00%> (-0.59%)
:arrow_down:

lona/html/document.py
24.00% <0.00%> (ø)

lona/html/widget.py
42.59% <ø> (ø)

Continue to review full report at Codecov.

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

@maratori: Thanks!


prepareForPipeline static method must be implemented in class extending data

Hey!
After the latest update to the laravel-data version 2.0.16, for some reason I need to declare an extra prepareForPiplenie static method.
Is this a bug or an undocumented breaking change?
Thanks

Updated from version 2.0.13 to 2.0.16, when I started experiencing the issue. Tried updating from 2.0.13 slowly up to 2.0.16 and realized, the issue is introduced in the 2.0.14 tag

Hi @truesteps ,
Version 2.0.16 works okay for me. Was this just a warning generated by PhpStorm or were you also running into an exception when running your code?
The packages Data class should be using the PrepareableData trait added in that commit (via DataTrait) which implements the prepareForPipeline method so you shouldn't need to do anything.

@bentleyo like you're saying, it seems that it's only an error generated by PHPStorm. Do you think it's a bug in phpstorm or is there a reason it throws this error?
Thanks.

@truesteps I think it it might be a bug in PHPStorm. My PHPStorm doesn't show that inspection warning for the Data class.
I was running into a very similar false positive warning before (saying that a method wasn't implemented - even though it was being implemented by a trait) and updating to PHPStorm 2022.2.3 made it go away.


feat(lit-controller): scaffold lit-controller package

POC implementation of https://github.com/statelyai/xstate/discussions/2186
TODO:

[ ] Implement helpers for @xstate/fsm
[ ] Add tests
[ ] Add documentation

cc @justinfagnani @santicros

Is this something that y’all want to add to this repo? Or would it be better to publish it myself?

@davidkpiano Is this something that y’all want to add to this repo? Or would it be better to publish it myself?

Sorry, I'll get to this later today and let you know!

No rush, just something i should have asked before i put up a PR! Still a little work on my end to complete it!

@justinfagnani appreciate the review 🙏

Hey folks, I wonder if there is any movement on this, as a consumer of xstate/lit I think it'd be super helpful.

This has completely flown under the radar for me - I'll try to review this next week.

Given my limited knowledge about Lit and web components, I really miss usage examples here (that could be tests in the repo 😉 )

@Andarist - I can't claim to be a lit expert myself, as I've only just started using it in the last month or so! So other folks here can probably input better than me 😅
I can throw some examples of an app I'm writing at the minute with a main machine + child actor.
export class Checkout extends LitElement {
service = interpret(CheckoutMachine(), { devTools: true })
@property({ attribute: false })
state = this.service.initialState
connectedCallback(): void {
super.connectedCallback()
this.service.onTransition((state, event) => {
  this.state = state
  const label = `[${this.service.id}]`.toUpperCase()
  console.log(label, event, state.value)
})

this.service.start({})

}
// Stop service on removal from the Light DOM
disconnectedCallback(): void {
this.service.stop()
}
....
Then in my render method, I'm rendering a new lit element for representing a child actor
render() {
return html<handoff .actor=${this.state.context.handOffActor}></handoff>
}

Then in my other lit elem

export class HandOff extends LitElement {
@property()
actor: HandOffActor | null = null
@property()
state: any
@property()
subscription!: Subscription | undefined
connectedCallback(): void {
super.connectedCallback()
this.subscription = this?.actor?.subscribe((emitted) => {
  this.state = emitted
  const label = `[${emitted?.machine?.id}]`.toUpperCase()
  console.log(label, emitted._event.data, emitted.value)
})

}
disconnectedCallback(): void {
this.subscription?.unsubscribe()
}

using subscribe here I can use `this.state` and get the updated child machine on any transitions/events.

I've yet to correctly manage to type the `this.state` property which is good fun 😅

Would love to see progress here!

@ChrisShank let me know if you're still interested pursuing this and need more review from the Lit side!

Thanks for the PR! Doing a bit of cleanup and closing this as outdated - would be happy to accept an updated lit-controller package though 🧹


PDHG and new callbacks

Description
Run the tomography reconstruction binder demo TomographyReconstruction

using the SIMPLE_PHANTOM_2D dataset not Tomophantom
on jupyterlab with cpu ProjectionOperator

Environment
23.1.0 g5e4938b5 3.9.19 (main, Mar 21 2024, 12:07:41)
[Clang 14.0.6 ] darwin

Some problems

PDHG with verbose=2 does not print primal-dual gap as before

from cil.optimisation.utilities import callbacks

# Setup and run PDHG
pdhg = PDHG(f = f, g = g, operator = K, sigma = sigma, tau = tau,
            update_objective_interval = 50)
pdhg.run(iterations=500, verbose=2, callbacks=[callbacks.TextProgressCallback()])

Different precision in objective values between ProgressCallback and TextProgressCallback

pdhg = PDHG(f = f, g = g, operator = K, sigma = sigma, tau = tau,
            update_objective_interval = 50)
pdhg.run(iterations=500, verbose=2, callbacks=[callbacks.ProgressCallback(), callbacks.TextProgressCallback()])

There is no  timing attribute in PDHG or Algorithm class. This used to return a list with times (per update_objective_interval) without measuring computational time of the objectives.
What does it mean 13.57it/s? For some stochastic algs, it would be nice to get the time per one iteration when a stochastic gradient is used and the time per one iteration when full gradient iscomputed.

Since we compute primal-dual gap by default, I think is better to print it (if one wants) as we did before.
Also, it is strange to see a continuous representation for iterations, e.g., 13.57 iterations. Seconds per iteration is more reasonable which is equal to Seconds per execution time for the update method.
Why in ProgressCallback we get 11.57it/s and with TextProgressCallback 13.01 it/s?
We can do many things with callbacks but previous default behaviour was much better. Also, printing in jupyter is very strange.


perf(core): improve binary size with API serde refactor and feature flags

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Docs
[ ] New Binding issue #___
[ ] Code style update
[x] Refactor
[ ] Build-related changes
[x] Other, please describe: Performance update - binary size improvements

Does this PR introduce a breaking change?

[ ] Yes, and the changes were approved in issue #___
[ ] No

Checklist

[ ] When resolving issues, they are referenced in the PR's title (e.g fix: remove a typo, closes #___, #___)
[x] A change file is added if any packages will require a version bump due to this PR per the instructions in the readme.
[ ] I have added a convincing reason for adding this feature, if necessary

Other information
…ize (#3956)

On my machine (aarch64-apple-darwin) the size comparison turns out like this:

branch
size

dev
1920.248 KB

perf/improve-binary-size
1488.648 KB

diff: 431.6 KB


Unable to open new tab when the only open tab is settings

Windows Terminal version (or Windows build number)
10.0.19042, 1.7.1033.0
Other Software
None relevant.
Steps to reproduce

Disable 'Always show tabs' (and relaunch if necessary).
Open a Settings tab using ctrl+, or the dropdown, it doesn't matter.
Close all other tabs.
Attempt to open a new tab using ctrl+shift+1, and find that it doesn't work.

Expected Behavior
To be able to open a new tab.
Actual Behavior
You are locked into the settings tab. Along with ctrl+shift+1, I tried ctrl+shift+n, ctrl+shift+p, and ctrl+shift+t. None work.

Yes this is a known issue. See #8767

And 8987 it seems. /dup #8767

Ha sorry the bot only listens to certain people that have the correct permission😅
I'll close it for you. Thanks for the feedback!

Ha sorry the bot only listens to certain people that have the correct permission😅

I was afraid of that...


[VEN-1066][VEN-1130] Add analytics and error logger

Jira ticket(s)
VEN-1066
VEN-1130
Changes

add analytics through PostHog
add error logger through Sentry

For now I think we should keep them in until Sentry is integrated to the dApp (https://github.com/VenusProtocol/venus-protocol-interface/pull/1010) so they can be replaced with sending an event to Sentry. What do you think?


not able to make a purchase from amazon app store

Please use Discussion board if you want get some help out of it. Please report issue if there is a bug.

i understand that Amazon support is still beta but any help would be appreciated...
Version of react-native-iap
"react-native-iap": "^6.0.3",
Version of react-native
"react-native": "0.63.3",
Platforms you faced the error (IOS or Android or both?)
Android amazon fireOS
Expected behavior
user to subscribe
Actual behavior
app get freezes and log show a warning [Error: purchase is not assigned]
Tested environment (Emulator? Real Device?)
Real kindle fire tablet
code snippet
prepIAP = async () => {
const productIds = Platform.select({
android: [
'xxxx.subscription.weekly',
'xxxx.subscription.monthly',
'xxxx.subscription.annually',
]
});
    if (__DEV__) {
        await RNIap.setFallbackInstallSourceAndroid(RNIap.InstallSourceAndroid.AMAZON);
      }

    try {
        await RNIap.initConnection()
        const products = await RNIap.getProducts(productIds);
        this.setState({amazonProducts:products})
        this.detectStoreOffers()
    } catch(err) {
        console.warn('error connecting to store',err); // standardized err.code and err.message available
    }
    try {
        RNIap.getPurchaseHistory().catch(()=>{}).then((res)=>{
            try {
                const receipt = res[res.length -1].transactionReceipt
            } catch (error) {

            }
        })
    } catch (error) {

    }

    purchaseUpdateSubscription = RNIap.purchaseUpdatedListener((purchase)=>{
            this.props.doSubscribe(true)
            console.log('777777777777777777777777777777777777777777', purchase)
            this.props.navigation.goBack()
    })

    purchaseErrorSubscription = RNIap.purchaseErrorListener((error)=>{
        if(!(error['responseCode'] === '2')){
            Alert.alert('Error', 'There has been an error with your purchase, error code' + error['code'])
        }
    })

    return () => {
        try{
            purchaseUpdateSubscription.remove()
        }catch(e){

        }

        try{
            purchaseErrorSubscription.remove()
        }catch(e){

        }

        try{
            RNIap.endConnection()
        }catch(e){

        }
    }

}

the issue was because im using revenue cat and RNiap in the same function .....


Opentelemetry Prometheus & Autometrics Compatibility

Hello! First, I'm a big fan of y'alls work. Thank you again for streaming your talk at Rust NYC @emschwartz 🙏
I am doing a 'zero-to-prod' style conference talk next month on Rust, with an emphasis on observability. I'd like to showcase autometrics, and am able to get autometrics working when I implement AM alone using the the AM prometheus exporter & metrics endpoint handler (i.e. follow the quickstart guide).
However, I also want to show off opentelemetry-prometheus metrics, and expose both metrics together. Is this a supported use case? If so, any pointers as to what I'm doing wrong? The current behavior is that only the OTEL-prom metrics are being exposed, not the autometrics metrics.
Initializing the otel-prom exporter:
https://github.com/ShockleyJE/zero-to-rust-at-neurelo/blob/main/data-plane/authn_service/src/main.rs#L37
Instrumenting one of the functions for autometrics:
https://github.com/ShockleyJE/zero-to-rust-at-neurelo/blob/main/data-plane/authn_service/src/authn/postgres_token_repo.rs#L22
Expectation:

Annotate a function store_token on the token creation code path
Create a token via the API

curl --location 'localhost:8000/' \
--header 'Content-Type: application/json' \
--data '{
    "environment" : "howderino"
}'

View metrics

curl --location 'localhost:9464/metrics'

I would expect to the function-level metrics for  store_token, but only see the otel-prom metrics
# HELP http_server_active_requests HTTP concurrent in-flight requests per route
# TYPE http_server_active_requests gauge
http_server_active_requests{http_flavor="HTTP/1.1",http_host="localhost:8000",http_method="POST",http_scheme="http",http_server_name="<IP_ADDRESS>:8000",http_target="/",net_host_port="8000",service_name="unknown_service"} 0
# HELP http_server_duration HTTP inbound request duration per route
# TYPE http_server_duration histogram
http_server_duration_bucket{http_flavor="HTTP/1.1",http_host="localhost:8000",http_method="POST",http_scheme="http",http_server_name="<IP_ADDRESS>:8000",http_status_code="200",http_target="/",net_host_port="8000",service_name="unknown_service",le="1"} 0
http_server_duration_bucket{http_flavor="HTTP/1.1",http_host="localhost:8000",http_method="POST",http_scheme="http",http_server_name="<IP_ADDRESS>:8000",http_status_code="200",http_target="/",net_host_port="8000",service_name="unknown_service",le="2"} 0
http_server_duration_bucket{http_flavor="HTTP/1.1",http_host="localhost:8000",http_method="POST",http_scheme="http",http_server_name="<IP_ADDRESS>:8000",http_status_code="200",http_target="/",net_host_port="8000",service_name="unknown_service",le="5"} 0
http_server_duration_bucket{http_flavor="HTTP/1.1",http_host="localhost:8000",http_method="POST",http_scheme="http",http_server_name="<IP_ADDRESS>:8000",http_status_code="200",http_target="/",net_host_port="8000",service_name="unknown_service",le="10"} 0
http_server_duration_bucket{http_flavor="HTTP/1.1",http_host="localhost:8000",http_method="POST",http_scheme="http",http_server_name="<IP_ADDRESS>:8000",http_status_code="200",http_target="/",net_host_port="8000",service_name="unknown_service",le="20"} 0
http_server_duration_bucket{http_flavor="HTTP/1.1",http_host="localhost:8000",http_method="POST",http_scheme="http",http_server_name="<IP_ADDRESS>:8000",http_status_code="200",http_target="/",net_host_port="8000",service_name="unknown_service",le="50"} 1
http_server_duration_bucket{http_flavor="HTTP/1.1",http_host="localhost:8000",http_method="POST",http_scheme="http",http_server_name="<IP_ADDRESS>:8000",http_status_code="200",http_target="/",net_host_port="8000",service_name="unknown_service",le="+Inf"} 1
http_server_duration_sum{http_flavor="HTTP/1.1",http_host="localhost:8000",http_method="POST",http_scheme="http",http_server_name="<IP_ADDRESS>:8000",http_status_code="200",http_target="/",net_host_port="8000",service_name="unknown_service"} 29.957
http_server_duration_count{http_flavor="HTTP/1.1",http_host="localhost:8000",http_method="POST",http_scheme="http",http_server_name="<IP_ADDRESS>:8000",http_status_code="200",http_target="/",net_host_port="8000",service_name="unknown_service"} 1

Hi @ShockleyJE, thanks in advance for featuring autometrics, and sorry this didn't work right away!
I think the problem is that two different prometheus::Registrys are being used to collect the metrics.
Previously, we had thought mostly about the use case of producing custom metrics but still using autometrics' prometheus_exporter for exposing them.
The plan in #20 is to allow you to pass in a registry so that you could ensure that autometrics uses the same one you're using with OpenTelemetry. I'm actually working on that issue right now but unfortunately it'll only be included in the next release of autometrics.

No worries, you guys are doing great work & adapting to hard problems!
Even if 0.6.0 isn't ready by for the conference August 19th I can still mock up a preview of how the result might look. Will check in on #20 and lend a hand if I can annex some time.
Feel free to close the issue as related to #20

Thanks 😊
I'm pretty sure the 0.6 release will be out before the conference. I'd estimate 2-3 weeks.
I'll close this now and indeed the issue should be fixed by #20.

Hi @ShockleyJE, I just took another look at this and I think the issue is different than what I had initially thought.
In order to make autometrics use the opentelemetry crate for producing metrics, you need to add the opentelemetry feature flag:
autometrics = { version = "0.5", features = ["opentelemetry"] }

I think you'll also need to update your version of the opentelemetry crates to 0.19 in order for it to work.
I ran into some issues trying to compile your project and so wasn't able to test it out, but could you let me know if that works for you?


Improve getNFTs compatibility for ERC1155 contracts

#4653  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jnsdls and the rest of your teammates on  Graphite


Discoverer e2e tests

@MaidaB, please add a description to this PR detailing the scenarios that are tested.


No track playing

Not really sure where to start with this one.
I've got Flatpak spotify running, and a song playing. However, SPDCK shows no track playing.
I've even tried playing a song in the web browser you get when you click the spotify icon, but with that I can't open the quick access menu without closing the browser anyway so it's fairly useless.
The song is clearly showing as playing on my other machines logged into spotify, so I know it's working in that regard. For whatever reason though, SPDCK just doesn't see the playing song no matter how it's played.

I'm experiencing the same thing with my new install today.