fix/feat: automatically generation nonce values, exclude empty var fields, disable image digest validation

This PR includes four major changes:

Nonce values may no longer be specified in codiusvars.json for private variables. Nonce values and public encodings for private variables are now generated automatically with the final manifest.
If public or private variables are not specified in codiusvars.json, then the corresponding vars fields will not be included in the generated manifest.
The image digest validation feature is temporarily disabled until dependency vulnerabilities are resolved.
The generate manifest function has been refactored to enhance readability and organization.

I uploaded contracts to numerous hosts with and without the public/private vars specified in the manifest and it worked fine for most of them. I think we're good to merge.

It looks like some hosts are actually not accepting contract uploads if the public vars field is specified but the private vars field is left out. However, uploads do work if both fields are not included. I went ahead and made an issue on the codiusd repo about this. My latest commit allows you to optionally add in an empty private vars field when generating the contract manifest. This should work until we get the codiusd issue fixed.

@sharafian For sure, I'll test it against some

I uploaded contracts to numerous hosts with and without the public/private vars specified in the manifest and it worked fine for most of them. I think we're good to merge.

The empty private variable field will now be added automatically added when needed. I also removed a redundant test from the generate manifest test file.


Multiple cursors don't show up

Multiple cursors selection works and multiple regions are highlighted whereas adding new cursors don't show up. The cursors are there just not highlighted.

I assume you're using multiple-cursors. Could you add this to your emacs.d and let me know if they become visible:
(custom-set-faces
 '(mc/cursor-face ((((class color)) (:background "red")))))

No, not visible. And I just noticed that this(cursors not being visible) happens only when I start emacs as daemon and open files using emacsclient. If I don't start it and open emacs filename the multiple cursors are visible and shows up as black

My mistake, sorry. It works properly.
I am not sure why this happens but I figured that js2-refactor caused this issue. I use use-package and when I defer js2-refactor the cursors show up but when I don't they don't show up. I currently don't have the knowledge to make sure that js2-refactor is causing this.


Support aliases for schema and field names

To allow schema and field names to evolve without breaking API level SQL queries, the API should support adding aliases for schema and field names.

Another idea that came up recently, we might want to support linking metadata schema fields. So for example, there might be two schemas that each define a field slightly differently but they both represent the same thing. One use for this would be to create a common metadata schema that links together the fields across more specific metadata schemas. Queries against the common metadata schema could then return results when matching fields in those more specific metadata schemas.
Essentially this comes down to a question of whether API users should define their own common metadata schema when metadata comes from multiple sources and then pre-process metadata to adhere to their common metadata schema. Or, they could leave the metadata as it is from each source and link together fields.


KServe not compatible with fluid

/kind bug
What steps did you take and what happened:
KServe is not compatible with fluid. When using fluid to load model for InferenceService, kserve controller will throw an error as below:
kserve-fluid-demo   2m33s       Warning   InternalError           pod/fluid-bloom-predictor-00001-deployment-5b6cf84f44-7whjh   Pod "fluid-bloom-predictor-00001-deployment-5b6cf84f44-7whjh" is invalid: [spec.volumes[5].name: Duplicate value: "kserve-pvc-source", spec.containers[1].volumeMounts[3].mountPath: Invalid value: "/mnt/models": must be unique, spec: Forbidden: pod updates may not change fields other than `spec.containers[*].image`, `spec.initContainers[*].image`, `spec.activeDeadlineSeconds`, `spec.tolerations` (only additions to existing tolerations) or `spec.terminationGracePeriodSeconds` (allow it to be set to 1 if it was previously negative)
  core.PodSpec{
      Volumes: []core.Volume{
        ... // 3 identical elements
        {Name: "bigboot-config-0", VolumeSource: {ConfigMap: &{LocalObjectReference: {Name: "oss-data-jindofs-config"}, DefaultMode: &420}}},
        {Name: "check-mount-unprivileged-0", VolumeSource: {ConfigMap: &{LocalObjectReference: {Name: "oss-data-jindo-check-mount-unprivileged"}, DefaultMode: &493}}},
+          {
+             Name: "kserve-pvc-source",
+             VolumeSource: core.VolumeSource{
+             PersistentVolumeClaim: &core.PersistentVolumeClaimVolumeSource{ClaimName: "oss-data"},
+             },
+          },
      },
      InitContainers: nil,
      Containers: []core.Container{
        {Name: "fluid-fuse-0", Image: "registry-vpc.cn-hangzhou.aliyuncs.com/jindofs/jindo-fuse:4.5.2", Command: {"/entrypoint.sh"}, Args: {"-okernel_cache", "-oro", "-oattr_timeout=7200", "-oentry_timeout=7200", ...}, ...},
        {
          ... // 7 identical fields
          Env:       {{Name: "STORAGE_URI", Value: "/mnt/models"}, {Name: "MODEL_NAME", Value: "bloom"}, {Name: "GPU_ENABLED", Value: "True"}, {Name: "PORT", Value: "8080"}, ...},
          Resources: {Limits: {s"cpu": {i: {...}, s: "12", Format: "DecimalSI"}, s"memory": {i: {...}, Format: "BinarySI"}}, Requests: {s"cpu": {i: {...}, s: "12", Format: "DecimalSI"}, s"memory": {i: {...}, Format: "BinarySI"}}},
          VolumeMounts: []core.VolumeMount{
            {Name: "kube-api-access-n6cdk", ReadOnly: true, MountPath: "/var/run/secrets/kubernetes.io/serviceaccount"},
            {Name: "kserve-pvc-source", ReadOnly: true, MountPath: "/mnt/models", SubPath: "bloom-560m", ...},
            {Name: "check-fluid-mount-ready", ReadOnly: true, MountPath: "/check-fluid-mount-ready.sh", SubPath: "check-fluid-mount-ready.sh", ...},
+             {
+               Name:      "kserve-pvc-source",
+               ReadOnly:  true,
+               MountPath: "/mnt/models",
+               SubPath:   "bloom-560m",
+             },
          },
          VolumeDevices: nil,
          LivenessProbe: nil,
          ... // 10 identical fields
        },
        {Name: "queue-proxy", Image: "registry-vpc.cn-hangzhou.aliyuncs.com/acs/serving-cmd-queue:2022"..., Ports: {{Name: "http-queueadm", ContainerPort: 8022, Protocol: "TCP"}, {Name: "http-autometric", ContainerPort: 9090, Protocol: "TCP"}, {Name: "http-usermetric", ContainerPort: 9091, Protocol: "TCP"}, {Name: "queue-port", ContainerPort: 8012, Protocol: "TCP"}, ...}, Env: {{Name: "SERVING_NAMESPACE", Value: "kserve-fluid-demo"}, {Name: "SERVING_SERVICE", Value: "fluid-bloom-predictor"}, {Name: "SERVING_CONFIGURATION", Value: "fluid-bloom-predictor"}, {Name: "SERVING_REVISION", Value: "fluid-bloom-predictor-00001"}, ...}, ...},
      },
      EphemeralContainers: nil,
      RestartPolicy:       "Always",
      ... // 26 identical fields
  }
]

I think the  possible reason is:
First, the webhook of kserve adds the PVC declared in STORAGE_URI as a volume of the container, and then it triggers the webhook of fluid to convert the PVC to hostPath. This behavior then triggers the watch for Pod UPDATE events in kserve webhook, which detects that the PVC is not mounted and tries to add a volume with the same name, resulting in an error.
The corresponding solution is to remove the watch for Pod UPDATE event in MutatingWebhookConfiguration inferenceservice.serving.kserve.io
https://github.com/kserve/kserve/blob/5900a68c398526996294e5647d436fd4d9d4877c/charts/kserve-resources/templates/webhookconfiguration.yaml#L43-L52
What did you expect to happen:
KServe is compatible with fluid.
What's the InferenceService yaml:
[To help us debug please run kubectl get isvc $name -n $namespace -oyaml and paste the output]
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
Environment:

Istio Version: v1.17
Knative Version: v1.4.2
KServe Version: build from master, commit ID: a224b740f31c7c9d9032ba257483f6fa869afb61
Kubeflow version:
Cloud Environment:[k8s_istio/istio_dex/gcp_basic_auth/gcp_iap/aws/aws_cognito/ibm]
Minikube/Kind version:
Kubernetes version: (use kubectl version):
OS (e.g. from /etc/os-release):

I have created a pr https://github.com/kserve/kserve/pull/2896 to fix this issue


GraphicsView EndInteraction Event dont show which Touchpoint has been ended

Type of issue
Missing information
Description
When i have e.g. two fingers on the graphics View and then release one finger, the EndInteraction will fire. so far so good. But in the TouchEventArgs parameter there is no information which finger has been released. So i cant do any logic, that depends on knowing the remaining touchpoint or the released touchpoint.
Page URL
https://learn.microsoft.com/en-us/dotnet/api/microsoft.maui.controls.graphicsview.microsoft-maui-igraphicsview-endinteraction?view=net-maui-8.0
Content source URL
https://github.com/dotnet/dotnet-maui-api-docs/blob/live/docs/xml/Microsoft.Maui.Controls/GraphicsView.xml
Document Version Independent Id
df2bcee0-85d9-f33d-57ea-ea39502ee97a
Article author
@dotnet-bot
Metadata

ID: df2bcee0-85d9-f33d-57ea-ea39502ee97a
Service: dotnet-mobile
Sub-service: dotnet-maui

someone is responsible for this?

Hey there! This repository is not for raising issues with the product but for issues with the API docs specifically.
I hope you have it figured out by now. If not, please turn to https://github.com/dotnet/maui. If you have a how-to question you might want to start on the Discussions tab. If you think there is a bug in the .NET MAUI SDK, please open an issue. Thanks!


The function type name 'CancelReservation' is invalid.

Function ($CancelReservation) Error: The function type name 'CancelReservation' is invalid.
Session Id: c9a26090b544491f99bbe9c70004d602
Timestamp: 2017-11-22T13:14:14.887Z
West-Europe

Can someone please post the rules for the naming? I'm constantly running into this. And with is the azure function cli publishing functions with invalid name anyway?

The only rule I found out is never start a function name with a number. But your name looks pretty good, like the names I use.

I created a function successfully without the same behaviour of yours. Did you already created a function with this name, deleted it and now recreate it?

In this case maybe. But it works with other recreated functions.
Also it happens to be related to the length of the name

I used the same name like you in my test and it works. :( Bad for you now.

fixed by deleting and recreating the function app


ios: split comma-delimited header values when creating platform representation

Description: Splits list-formatted header value on creation of header maps.  Per RFC 7230, does not perform this parsing on "set-cookie" headers, and additionally skips it on "www-authenticate" and "proxy-authenticate", due to their potential to contain commas in contravention of the spec.
Risk Level: Low
Testing: Pending
Signed-off-by: Mike Schore<EMAIL_ADDRESS>

Update to this coming early tomorrow.

https://github.com/envoyproxy/envoy-mobile/issues/1215


LG Editor: Ensure tabs remain in a consistent order

On the LG editor, if I start with a Text tab, add a Speech tab, I have the tabs in the order Text -> Speech.
If I then remove the Text tab and re-add a Text tab, my tabs are then in the order Speech -> Text.
Ideally we should try and ensure that tabs are shown in the order Text -> Speech -> Attachments -> Suggested Actions.

I dont agree, I think ideally we should keep the order in which user modified them.

@hatpick @sangwoohaan I think allowing the tabs to appear in the order they are created could lead to a very inconsistent experience over time. For example, I create a bot today and add 10 actions, each with multiple tabs and all of them end up in different orders.  Then I come back to the bot the next day / month etc and all of the tabs on all my actions are all in an inconsistent order. I think this would be a pretty poor experience.

That's a great argument for a static tab list. However, for a dynamic tab view such as this the behavior is that they appear in the order that they get added. For example look how Edge or vscode work.

I think for a future milestone this can be customizable in a way that it serves the user's intention for what the main modalities of your bot would be(i.e. if you decided to build an Alexa skill, you would want the speech tab to come first). But still, the tab order should be consistent across the board. I think giving too much control to users to individually determine the order of the tabs would eventually lead them to inconsistent UX.


[WIP] Backend API refactor

Partially (mostly?) complete refactor of backend API:

Features are now stored as an xray.Dataset and saved in netCDF format
Logic for featurization of unlabeled data (in the prediction step) is combined with logic for featurization of labeled data
High-level API functions now consist of a wrapper that handles file system logic and calls an inner function that performs a task on data residing in memory

Still needs:

Restructure and fix predict and flask_app tests
Tweaks to featurize and build_model tests since some of the inner logic has changed; should add new tests for these new subfunctions
Update lots of docstrings

Without scrutinizing every line (I'll leave that to @stefanv :wink:), it looks good overall to me. Nice work Brett, this is a good refactor. Docstrings for the new functions seem to be the only major missing piece so far. :+1: from me.

Excellent refactor, @bnaul.  I left some minor comments.

Since Ari and I are both out this week, please feel free to self-merge once you are satisfied.


[BUG] Can't Import - Module AIP Service

To Reproduce
Install-Module AIPService
Import-Module AIPService

Observed Behavior
Import-Module: Could not load file or assembly 'System.Web.Services, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.

Expected behavior
AIPService Module ready to be used
Is this specific to Cloud Shell?
Yes
Interface information
How are you accessing Cloud Shell - https://shell.azure.com, https://portal.azure.com, via Windows Terminal, or some other method?
If a browser, which Operating System and browser are you using? (ex. Edge on Windows 10)
Portal.azure.com
https://shell.azure.com
Additional context
Add any other context about the problem here.

Cloud Shell doesn't support this command because it needs administrator privileges on a Windows machine. Both of those requirements are not compatible with Cloud Shell. Sorry!

Is there a resolution to this?


Use keyboardLayoutGuide

When trying to use Keyboard Layout Guide it seems that the keyboard layout is not set (at top with no height) and the resulting screenshot is incorrect therefore. I am aware that for screenshot tests there is no keyboard, but my expectation would have been that the keyboard layout then matches the bottom part below the safe area (in other words keyboard layout top = safe area bottom). This would be in line with what Apple documents:

When the keyboard isn’t onscreen, the guide is at the bottom of the window and has a height equal to the bottom of the current safeAreaInsets.

Example:
class FooVC: UIViewController {

    override func viewDidLoad() {
        let button = UIButton()
        button.translatesAutoresizingMaskIntoConstraints = false
        button.setTitle("Foobar", for: .normal)
        view.addSubview(button)
        button.leadingAnchor.constraint(equalTo: view.safeAreaLayoutGuide.leadingAnchor).isActive = true
        button.trailingAnchor.constraint(equalTo: view.safeAreaLayoutGuide.trailingAnchor).isActive = true
        button.topAnchor.constraint(equalTo: view.safeAreaLayoutGuide.topAnchor).isActive = true
        button.bottomAnchor.constraint(equalTo: view.keyboardLayoutGuide.topAnchor).isActive = true
    }

}

class FooVCTests: XCTestCase {

    func testFoobar() {
        assertSnapshot(matching: FooVC(), as: .image)
    }

}

It correctly works when replacing the keyboard layout guide:
button.bottomAnchor.constraint(equalTo: view.safeAreaLayoutGuide.bottomAnchor).isActive = true

How do you use keyboard layout guide in snapshot tests? Is it possible to somehow set the keyboard layout guide in tests? Or are you using the keyboard layout guide differently (maybe always in combination with safe area layout guide)?

I found out that it does work if a safe area is defined with any non null bottom value.
Works:
assertSnapshot(matching: vc, as: .image(on: .init(safeArea: .init(top: 0, left: 0, bottom: 1, right: 0), size: .init(width: 375, height: 812))))

Does not work:
assertSnapshot(matching: vc, as: .image(on: .init(safeArea: .init(top: 0, left: 0, bottom: 0, right: 0), size: .init(width: 375, height: 812))))

Since all predefined configs have a safe area, this issue should not happen when these are used:
assertSnapshot(matching: vc, as: .image(on: .iPhoneX))


Add Airlock Notifications

Resolves #2010 Resolves #2011
What is being addressed
Add a notifications mechanism that notified TRE users (e.g. Researchers, Workspace owners) on Airlock operations, such as 'request waiting for approval'  or 'request approved'.
How is this addressed

Allow provisioning of an Azure Logic App, an API connection, a service bus queue, and an event gird topic as an infrastructure.
Deploy application 'configuration', in JSONs, for the actual logic.

@tamirkamara Ready for review

/test

/test


Check whether the cite detector is finding good citations

@kfunk074 asked for the citations we've found so far for these treatises.

F0103272617
F0151947538
F0105827925
F0103761500
F0102826781

The citations detected are attached. It's best to think about the information here as having two parts.

The citation detected (boils down to the raw field). The citations detected are not entirely final, but reasonably close.
The link between the citation and the case (the case field contains the CAP case ID). This was done quick and dirty, without any guessing for page numbers and so forth. So treat this as temporary data.

If there is a reporter_abbr field that looks like a reporter (i.e. not obviously junk) and there is not an entry in reporter_cap, then we want to add that to the whitelist.
If there is an entry in the reporter_capfield (and thus in thecleaner_citefield) but not in thecase` field it would be helpful to know the categories of problems that are causing that. I.e., is the volume number wrong? The page number? Is the page number wrong in the actual text? Or is it an OCR error. Stuff like that.
F0102826781.csv
F0103272617.csv
F0103761500.csv
F0105827925.csv
F0151947538.csv

That is a bit strange. Part of it can be explained by the fact that there are reporters without whitelists. But not all, and not that much. I did something janky to write the query quickly. Let me try again a different way.

Ha.

Here are twenty sample "citations" for each of the reporters to be whitelisted. The reporters are ordered by frequency, so best to start at the top and work down. Each "citation" has a link to a treatise in MOML, along with the page number of the citation. To make this file size manageable, it is only "reporters" that appear at least 1000 times, not 100 times as in the treatise-by-treatise files above.
Examples of citations to reporterts not whitelisted.csv

The following files supersede all those above. They have been updated to include a better list of what has already been whitelisted.
These are the top reporters still to be whitelisted, with sample citations for them.
Top reporters not yet whitelisted.csv
Sample citations for top reporters not yet whitelisted.csv
And these are the citations found for specific treatises, with the quick and temporary way of linking them to CAP cases.
F0102826781.csv
F0103272617.csv
F0103761500.csv
F0105827925.csv
F0151947538.csv

RA has checked F010327617. Out of 166 citations on the page, we had 8 errors and 7 missing citations, for an overall accuracy of 91% (88% if we ignore statutory cites). Not bad. Only one of the errors was a number error. All the others were text OCR problems that will be resolved on our next round of whitelisting.
The only systemic issue is that we consistently missed citations to Howell's Special Term Reports, which look like this: 1 How. Sp. T. Rep. 114. I checked the OCR on the MOML pages and it's flawless. We did pick up citations to the reporter when there was an OCR error, for instance How. Sp. T. Rep (no terminal period) and How. Sp.T. Rep. (missing internal space) are both in the detected citations list. Is there an alpha character limit or something that's excluding the full cites?

Slight amendment: 3 cites were missed because the volume number 1 was OCR'd as I or ]. Not worth addressing right now, but we can keep in mind that these kinds of errors happen.

As you surmised, that abbreviation is 16 characters long, but the regex limited the abbreviations to 15 characters. I have made a change and added a test in https://github.com/lmullen/legal-modernism/commit/914bbeb2766f43066632460ebb4e0ae178498c7e

RA has spot checked the other four treatises. Overall, we have an initial accuracy rate of 75%. That will improve somewhat with the next round of whitelisting. A couple of the treatises just have really bad OCR on the numbers and there's nothing our current approach can do about it. Column breaks in footnotes threw a lot of things off, too. The good news is that the treatise with the most column break errors also used parallel cites abundantly, so if we're just trying to draw one edge between a treatise and a cited case, we probably have an average of four different chances to get it right between the parallel cites and the table of authorities.
Only systemic issue that arose is we've identified some more single-volume reporters. My recollection is you're keeping a separate library of those. If so, these should be added: Baldw., Comst., Cro. Car., Hob., Palm., Peake's Cas. All except the first appear to be UK reporters.

reporters_citation_to_cap_whitelist-4.csv
Update to the whitelist, covering a little over 1,000 entries and 5 million "cites." Let me know if there's a better format, but this is the format used for the previous whitelisting efforts.

@kfunk074 I've added this to the database.
I'm not sure why, but about 50 of the entries were duplicated. I cleaned it up, and it's unlikely to happen again, so I wouldn't worry about it.

Another 1,000 entries to update the whitelist, hopefully with few duplicates, but there are probably some. This should cover all reporters cited more than 5,000 times (there may have been a troubling entry or two we left for further investigation).
reporters_citation_to_cap_whitelist-5.csv

At this point, to avoid duplicates, we should probably start with a fresh list of non-yet-whitelisted reporters cited more than 500 times. And the example entries have been really helpful, so we should provide an updated sheet of 10 random examples per each reporter for Sean as well (can be limited to more than 750 or 1000 cites if 500 is too large).

To collate the above into a task list:

[ ] Update whitelist with reporters_citation_to_cap_whitelist-5.csv
[ ] Run a new Top Reporters Not Yet Whitelisted for reporters cited over 500 times
[ ] Run a new Examples of Reporters Not Yet Whitelisted for reporters cited over 500 (or 750 or 1000) times
[ ] Pull the list of citations and their CAP matches for five random treatises for spot checking
[ ] Distribute whitelisting sheets to Sean and spot checking sheets to Conor


Delete the permission property form the JSON

It's not needed.

[x] First delete references in the JS.
[x] Then delete it from appearing in the JSON.

Done!


[Snyk] Security upgrade cypress from 10.11.0 to 13.13.0

Snyk has created this PR to fix 3 vulnerabilities in the yarn dependencies of this project.
Snyk changed the following file(s):

cypress/package.json
cypress/yarn.lock

Note for zero-installs users
If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Missing Release of Resource after Effective Lifetime SNYK-JS-INFLIGHT-6095116
  131

Server-side Request Forgery (SSRF) SNYK-JS-CYPRESSREQUEST-5871337
  111

Prototype Pollution SNYK-JS-TOUGHCOOKIE-5672873
  111

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Server-side Request Forgery (SSRF)
🦉 Prototype Pollution

:tada: Snyk checks have passed. No issues have been found so far.
:white_check_mark: security/snyk check is complete. No issues have been found. (View Details)
:white_check_mark: license/snyk check is complete. No issues have been found. (View Details)


Add "breandcrumbs" bar

Last release of IntelliJ IDEA added new "Breadcrumbs" toolbar:

If you click on a symbol on the toolbar, the cursor jumps to that symbol.
If you click on a symbol with right mouse button, the whole entity definition is selected.
When you hover over a symbol on the toolbar, it shows its type and, for lambdas, the whole definition.
It's similar to Xamarin's navigation bar, but without ability to select other symbols with comboboxes. I'm not sure which style is better though. If we are gonna to resurrect VFT's Navigation bar, then it makes sense to rewrite it to mimic Xamarin's behavior.

If each item could be a dropdown, and the first item is the list of modules/namespaces in the project, that would be killer feature :)

As I said, dropdowns makes it a different thing, you cannot click / right click on them to go-to-symbol / select definition with them.

having a part with the text (breadcrumb) and a part with dropdown (the down arrow) would bring best of both worlds.
The underlying service which keeps track of hierarchy of node would be useful for other features as well, I intend to implement solution explorer tree nodes under .fs files at some point.

@vasily-kirichenko it's possible to make a WPF control that allows both, it doesn't have to be the kind used in the current navigation bar

OK!

When is this useful? For selecting code?

@JohanLarsson The main feature - instant understanding where you are in a large file, I mean in what module, type, method or function the cursor is.

@JohanLarsson this would be really useful, especially when working through unfamiliar source
@vasily-kirichenko  should we do the same kind of preview windows that we use for collapsed outlined regions, or should we have intellisense tooltips pop up on hover instead?

Wrote a prototype for the UI.

The control is an ItemsControl bound to a collection of nodes where each node has Children and a SelectedChild, we will need to write a viewmodel that exposes the ast and cursor position like this, probably pretty straightforward.

Could you port it to F# and make it a margin, similar to QuickInfoPanel?

There's no need for the nodes to be drop down menus, there's only ever one path down the AST to the cursor position

I agree. We should not mix navba rand this feature.

@vasily-kirichenko everything can be ported to f# given enough time ans skill :)
I'll have to figure out what a margin is, have not used the VS api much.
@cloudRoutine dropping the dropdowns will simplify things a lot. Without having used f# much I think I agree with @smoothdeveloper that they can be useful. Maybe best to start simple without them.
About mixing features: screen space is a limited resource, if the ux can be made to make sense mixing could be a good thing.

@vasily-kirichenko Is ^ how you want it?

Yeah, but on gray background. Also, each type of symbol should be colored differently.

Leftaligning it with the text is somewhat tricky, is it better than:

^ is simpler.
About the background: should probably be set by dynamicresource to a resourcekey to make it theme aware.
About styling content: the sky is not the limit.

It should be left aligned with text, as on the previous screenshot.
The font should be the same as one used for code in editor.
Colors should be calm.

+1 about font
And I think maybe no colours at all, perhaps light up on mouseover or an underline with colour.
Making UI like a christmastree is not always awesome ux.

Regarding colors / background, I believe we should use the semantic coloring used in the source code itself, modules have some color, mutable variables some color, interfaces some color etc.

That makes sense, maybe just use foreground on the text.

It turns out this feature is more annoying than useful.


Error when FoM Goal is reached with AD algorithm

Using the AD algorithm, i get the following error message when the FoM Goal is reached:
Traceback (most recent call last):
  File "x.py", line 103, in <module>
    main(settings_AD)
  File "x.py", line 42, in main
    optimization_obj.execute()
  File "C:\Users\user\AppData\Roaming\Python\Python310\site-packages\quocslib\Optimizer.py", line 89, in execute
    self.opt_alg_obj.run()
  File "C:\Users\user\AppData\Roaming\Python\Python310\site-packages\quocslib\optimizationalgorithms\ADAlgorithm.py", line 137, in run
    self.inner_run()
  File "C:\Users\user\AppData\Roaming\Python\Python310\site-packages\quocslib\optimizationalgorithms\ADAlgorithm.py", line 156, in inner_run
    results = optimize.minimize(f_call,
  File "C:\Users\user\AppData\Roaming\Python\Python310\site-packages\scipy\optimize\_minimize.py", line 696, in minimize
    res = _minimize_lbfgsb(fun, x0, args, jac, bounds,
  File "C:\Users\user\AppData\Roaming\Python\Python310\site-packages\scipy\optimize\_lbfgsb_py.py", line 359, in _minimize_lbfgsb
    f, g = func_and_grad(x)
  File "C:\Users\user\AppData\Roaming\Python\Python310\site-packages\scipy\optimize\_differentiable_functions.py", line 285, in fun_and_grad
    self._update_fun()
  File "C:\Users\user\AppData\Roaming\Python\Python310\site-packages\scipy\optimize\_differentiable_functions.py", line 251, in _update_fun
    self._update_fun_impl()
  File "C:\Users\user\AppData\Roaming\Python\Python310\site-packages\scipy\optimize\_differentiable_functions.py", line 155, in update_fun
    self.f = fun_wrapped(self.x)
  File "C:\Users\user\AppData\Roaming\Python\Python310\site-packages\scipy\optimize\_differentiable_functions.py", line 137, in fun_wrapped
    fx = fun(np.copy(x), *args)
  File "C:\Users\user\AppData\Roaming\Python\Python310\site-packages\quocslib\optimizationalgorithms\ADAlgorithm.py", line 154, in f_call
    return np.array(self.inner_routine_call(x))
  File "C:\Users\user\AppData\Roaming\Python\Python310\site-packages\quocslib\optimizationalgorithms\ADAlgorithm.py", line 114, in inner_routine_call
    FoM = self._routine_call(optimized_control_parameters=optimized_control_parameters, iterations=0)
  File "C:\Users\user\AppData\Roaming\Python\Python310\site-packages\quocslib\optimizationalgorithms\OptimizationAlgorithm.py", line 163, in _routine_call
    self.dsm_obj.sc_obj.is_converged = True
AttributeError: 'ADAlgorithm' object has no attribute 'dsm_obj'. Did you mean: 'comm_obj'?

Fixed in Version 0.0.61


There is no way to sort the products

As there is no way to sort the products in the frontend, I was working on implementing it.
Now there are a few questions about the implementation:

Should it be implemented as a global parameter alongside the search or should be in the (template) body with the filtered keyword, so that it can work with searched result as well. I think when you have a lot of products, it would be useful.
What kind of sort features should be available, the ones that I have in mind are Price: low-to-high, Price: high-to-low, Popular and Featured.
For sorting by popular, we will have to either use the number of orders or better save the number of product views and bring up the popular ones.
For featured, we will have to give users an option to make a product featured. This is useful when you have 10 important products and others are like accessories. Then you want to sort by featured products by default.

Let me know your thoughts.

There is a way. Check the productOrderBy and productOrder setting in the config/settings.json file.

Sure, I am happy to give a helping hand.


feat: add castDurationToTime64 option

Fixes #470 by adding a castDurationToTime64. Note that its turned on by default and will cast the value emitted by DuckDB from milliseconds to microseconds.

Awesome, thx!


[MM-48014] Enable App Bar by default

Summary
This PR removes the EnableAppBar config setting, and replaces it with a DisableAppBar setting, to enforce a new default value. For all servers, new and upgrading, the App Bar will now be shown by default.
Ticket Link
https://mattermost.atlassian.net/browse/MM-48014
Related Pull Requests

https://github.com/mattermost/mattermost-server/pull/21715

Release Note

Apps Bar is enabled by default for on-prem servers

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.


Suggestion to support Chinese directory path

Thank you very much for your sharing! It helps a lot.
I have some tiny advice here.
In file ‘excelimporter.py’, Pandas's read_csv(file_name) funcion does not support Chinese directory path with the default parser engine. So I suggest to set the parameter 'engine' to 'python'.
Like this:
dataset = pd.read_csv(csv, encoding=encode, dtype=str, keep_default_na=False, engine='python') will work well.

I'm really appreciate thay you advised me this.
I will fix it soon after.
Best.

Pandas's read_csv(file_name) funcion does not support Chinese directory path with the default parser engine

Hi @xyliaaaaa ,

Thank you very much for your sharing! It helps a lot.
I have some tiny advice here.
In file ‘excelimporter.py’, Pandas's read_csv(file_name) funcion does not support Chinese directory path with the default parser engine. So I suggest to set the parameter 'engine' to 'python'.
Like this:
dataset = pd.read_csv(csv, encoding=encode, dtype=str, keep_default_na=False, engine='python') will work well.

Hi @xyliaaaaa ,
This is not a problem for me.
The version of my python is 3.7 and pandas is 0.25.
I guess the version caused this issue.
See https://github.com/pandas-dev/pandas/issues/17188.
It is maybe fixed in my version.
But I'm not sure and forgive me that I only can try my best to support/test it based on the latest python/pandas version.
Thanks again for your professional suggestion.


Support for other LSM303x devices

I am the maintainer for the stm32f3-discovery board support crate, which is a replacement for the old f3 bsc.
It has recently come to my attention that the STMF3Discovery board has newer revisions with this IMU on board instead of the LSM303DLHC. The accelerometers on the AGR and DLHC are compatible, only the magnometers and temperature sensors differ. In fact, the old, unmaintained, lsm303dlhc driver works just fine for the accelerometer.
This driver's API is also already almost compatible with the old lsm303dlhc driver.
I understand that the LSM303DLHC is obsolete and out of production, but there are still a number of them floating around in the wild and I would like to support both variants of the board if I can.
I can, obviously, plaster over the differences in APIs and use a feature gate to switch between the two drivers, but I was curious if you'd be open to adding support for the older device here, considering they share so much common implementation code. I'm happy to put in some work here, but didn't want to do so if there wasn't a chance of it being merged.

Thank you for your work on the stm32f3-discovery BSC. I have been wanting to switch to it myself here too.
This is an interesting point.
I would be open to making this driver compatible with the lsm303dlhc behind an lsm303dlhc flag or similar, provided that the code can be kept reasonably confined.
I would like to keep the method names used in this crate, though, at least for now.
It would be good if you could put as much as possible related to the lsm303dlhc inside a module similarly named, including all the applicable methods from the LSM303AGR as well as tests for the functionality as available here.
Once that is available, I can restructure the rest of the crate, provide a set of traits for both models and so on.
What I am skeptical about is implementing the Accelerometer traits as I have now seen in your BSC. That crate adds the whole micromath dependency just for a vector definition, contains a whole error mechanism with specific kinds, etc. But that is a separate discussion.

Ok. I’ll work on it as I have time.
FWIW I’m fine continuing to implement Accelerometer on the bsc side of things.
It has other problems, like using g instead of mg, which forces you into a float. Fine for my purposes, because the stm32f3 has an FPU. Not ok for a general use HAL IMO.
It’s also not we’ll maintained.
I’m probably going to take a stab at a different abstraction which includes magnometer and temperature as well as a compass, but I digress.
Thanks for the quick response and your work on this driver. I’ll see what I can come up with.


The "pip install" command isn't finding the package

[The "pip install" command isn't finding the package]

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

ID: 641aef05-1d16-ba0d-fb48-1527583a860d
Version Independent ID: 2ca9c55d-56a7-ec67-80da-7c0337316245
Content: Quickstart - Manage Phone Numbers using Azure Communication Services
Content Source: articles/communication-services/quickstarts/telephony-sms/get-phone-number.md
Service: azure-communication-services
GitHub Login: @Prakulka
Microsoft Alias: prakulka

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

Thank you!
Gerardo Tapia Vera
WBAMN
+18315407024
On Sat, Mar 27, 2021 at 12:14 AM YutongTie-MSFT @.***>
wrote:

Thanks for the feedback! I have assigned the issue to the content author
to investigate further and update the document as appropriate.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/72873#issuecomment-808676913,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQIKCNCG7SVPH2VC3E47G5LTFWAUNANCNFSM4Z4O64JA
.


need to remove rlks dependency for new operator deployment

rlks no longer needed. this removes rwx dependency as well. need to remove rlks dependency for new operator deployment

closed with v2.1.0 release
@mjperrins fyi closed issue


Everything is drawn a fixed amount of pixels above where it should be drawn

Hello,
I have a strange issue in all my projects using imgui-sfml, including the example project. Everything seems to be drawn a little bit above where it should normally appear. The offset seems equal to the window header bar height.

This is probably a simple issue to solve but I don't really know where to start investigating. Any help would be greatly appreciated :)
Thanks !

I updated my video card drivers and it fixed the issue 👍 (in case it is useful for solving future issues, my video card is an Intel HD Graphics 620). Thanks for your help and your work in general :)


not working in Win10 Edge browser

bag() require cannot callback in Win10 Edge browser without console open (f12)

Any details? Need example how to reproduce.

Closed as timed out. Could not reproduce.


Make 'contains' of CustomizationID in si-ubl-2.0-nlcius.sch

The construction below does not work for the SETU Invoice.
<let name="is_SI-UBL-2.0" value="$customizationID = 'urn:cen.eu:en16931:2017#compliant#urn:fdc:nen.nl:nlcius:v1.0'" /> <let name="is_SI-UBL-2.0-ext-gaccount" value="$customizationID = 'urn:cen.eu:en16931:2017#compliant#urn:fdc:nen.nl:nlcius:v1.0#conformant#urn:fdc:nen.nl:gaccount:v1.0'" />
Therefore, please change it into the following:
<let name="is_SI-UBL-2.0" value="contains($customizationID, '#compliant#urn:fdc:nen.nl:nlcius:v1.0')" /> <let name="is_SI-UBL-2.0-ext-gaccount" value="contains($customizationID, '#conformant#urn:fdc:nen.nl:gaccount:v1.0')" />

For whitespace flexibility or to allow for specialization? Technically, 'contains' could result in wrong customizationid values to be accepted; but perhaps something could be done with normalize-space.

Problem now is the schematron does not work for invoices with urn:cen.eu:en16931:2017#compliant#urn:fdc:nen.nl:nlcius:v1.0#compliant#urn:fdc:setu.nl:invoice:v2.2.

@tjeb this request is about the question "when to validate the NLCIUS rules?"
Currently, you've implemented this by looking at the complete CustomizationID and check if it matches urn:cen.eu:en16931:2017#compliant#urn:fdc:nen.nl:nlcius:v1.0. In other words the NLCIUS rules only apply when you have a EN16931 invoice according to NLCIUS spec. No more, no less.
However, we could easily support other use cases where communities (like SETU) reuse the NLCIUS rule set, by checking if the CustomizationID contains urn:fdc:nen.nl:nlcius:v1.0 (the part of the id that indicates use of NLCIUS).
As you can see by the CustomizationID, to indicate that SETU has added some usage specifications (hence ciUS) that are compliant with the EN and NLCIUS, the part #compliant#urn:fdc:setu.nl:invoice:v2.2 is added. However, reusing the NLCIUS ruleset does not work anymore, because it doesn't match the exact id.
As @RobinTNO suggests, you can we can use the contains() function for this.

Or perhaps starts-with(), to make it less error-prone; however, I'm currently thinking that the CustomizationID check shouldn't be in the included file at all, but in the file that does the including (si-ubl-2.0.sch, which, interestingly enough, does have a check that uses contains).

doh, my bad, this is only about the context specification, not the customizationid rule itself. Will update soon.


keybase version gives error if server isn’t started

$ keybase ctl stop
$ keybase version
▶ ERROR dial unix /run/user/1000/keybase/keybased.sock: connect: no such file or directory

Most other commands seem to start the server if it isn’t running already. Alternatively, it might make sense for this command to just print the client version if the server isn’t running. But this error shouldn’t happen, I think.
I’m on version 1.0.10-0 (Arch package).

Thanks! This was by design but another bug crept in that prevents it from
displaying the service isn't running before crapping out.
On Saturday, February 6, 2016, Lucas Werkmeister<EMAIL_ADDRESS>wrote:

$ keybase ctl stop
$ keybase version
▶ ERROR dial unix /run/user/1000/keybase/keybased.sock: connect: no such file or directory
Most other commands seem to start the server if it isn’t running already.
Alternatively, it might make sense for this command to just print the
client version if the server isn’t running. But this error shouldn’t
happen, I think.
I’m on version 1.0.10-0 (Arch package).
—
Reply to this email directly or view it on GitHub
https://github.com/keybase/client/issues/1923.

Should be fixed in our latest update (1.0.10). Thanks for the bug report.

Can confirm it’s fixed in 1.0.11. Thanks!


Jump To specific page

is it possible to jump to specific page?
let say i have url like this
www.example.com/tittle-hello.html#page=3
can i jump to the third pagination base on url fragment "#page=3",
Thanks

Yes, you can load arbitrary pages by writting your own custom function for path option

Thanks for the answer, i'll try it first, for now i'll close the issue


What does sr_nm stand for?

What does sr_nm stand for?
the VNM sparsity format?

Yes, it was an initial name candidate for VNM. Thank you for pointing out the typo.

您好，您的邮件我已经收到！

I am wondering the relationship between format_sr_nm and blockwise_format_origin/blockwise_format, could you please explain? thx

And I am also wondering the init function and the exec function. These two functions are not explained in the paper. Could you please provide a specific explanation of their functions?


Fix Windows Activate Process

Fixes #92305
Fixes #92304
Bugsquad edit:
Fixes #92307
Fixes #92759

I was able to reproduce the problem of key being stuck after Alt-Tab everything time after the editor windows moved.
The problem was caused by the move_timer_id that was not resetted and was stucked with same value of the activate_timer_id preventing the _process_activate_event from executing.
Godot 4.3 beta 1:
https://github.com/godotengine/godot/assets/81109165/f7f13f1f-7fda-4d31-880c-2b9a37e68d79
After the fix:
https://github.com/godotengine/godot/assets/81109165/84514045-bfca-4048-86a8-d6a8e6386fdf

Thanks!


[5.8] Refactor caching TTL to seconds

These changes will allow developers more finer granular caching. By allowing caching in seconds, developers can set even more specific caching times.
// This...
Cache::put('foo', 'bar', 60);

// Will change to this...
Cache::put('foo', 'bar', 3600);

This also makes the caching TTL conform with PSR-16 which states that:

Implementing Libraries MUST support at minimum TTL functionality as described below with whole-second granularity.

https://www.php-fig.org/psr/psr-16/
This refactor also simplifies things by removing support for floats and only supporting integers since floats aren't necessary anymore. If you take a look at the refactored tests and internals you'll see that we now do much less calculations.
I've added a separate commit which shows the places in the other components where the new behavior is updated. The changes don't affect other components but we may also consider if other components like auth and especially session could benefit from this.
This will have quite an impact on any app implementing caching and should be indicated in the upgrade guide as a high impact change.

Hi,
I'm going through the https://laravel.com/docs/5.8/upgrade#upgrade-5.8.0 process (first time ever) and found this page and https://github.com/laravel/framework/pull/27217/files were referenced in the cache section of upgrade notes.
The #27217 changed file  src/Illuminate/Cache/RedisTaggedCache.php uses $minutes. This page #27276 src/Illuminate/Cache/RedisTaggedCache.php changes that variable to $seconds.
In the future should I disregard older posts such as #27217 and only utilize #27276, in this case?

#27217 didn't change it to minutes. It was already minutes.

Hi @devcircus , yes, I saw that thank you. I may be misinterpreting how to use the upgrade guide, but it references both. Reading from top to bottom the newest #27276 is referenced first, so when I came to #27217 I decided to clarify.
Are we supposed to make the changes for each referenced pull request noted in the upgrade guide?

Not sure I follow. The upgrade guide is just pointing out that ttl has changed from minutes to seconds and that now, psr16 is more closely followed. The two ideas do not oppose each other. If you're digging in to a PR to see exactly how a specific piece of code works, always follow the most recent. Code is always changing.

So, e.g. on #27276, I completed all the changes first but when I went down the page and started making the next changes the older #27217 conflicted. I may be doing changes in a bad way. idk
To be sure...we should be updating the changes in Files changed tab at the top of the PR referenced? And we manually go through this each time there's an upgrade?
Or does updating the composer.json to "laravel/framework": "5.8.*" handle all that?
e.g. this line "In the very unlikely event you are implementing this interface, you should add these methods to your implementation." I took that as we manually update our app.

What are you changing using the pull requests? The actual code?

ha, man, this sounds badd...
`- $this->event(new KeyWritten($key, $value, 0));

$this->event(new KeyWritten($key, $value));`

e.g. in the above I removed,  0)
I wish the upgrade guide had a blue boxed tip about this. So if I've changed the composer.json dependency to "5.8.*" when are those changes "brought in?"

Hello. Is method (Illuminate\Cookie\CookieJar)->make() should receive seconds instead minutes?

No, the code looks correct with minutes?

@Tegos the cookie component was left untouched and still uses minutes.

Yeah, it's look correct.
I meant, whether is it necessary to update it as well as the Cache for the same reasons(granular, psr-16)?

@Tegos cookies don't have anything to do with PSR-16. But yeah I suppose it could profit from the same thing. You're free to send in a PR to the master branch for this.

@driesvints ok, sorry. I sent pr to the master.


feat(connector): [Payme] Support Apple Pay

Type of Change

[x] New feature

Description

Support Apple Pay for PayMe
Steps followed:

Session call: We will get an empty object with delayed session and connector as payme and next-action as confirm
confirm call: we hit generate-sale endpoint of PayMe to get payme-seller-id
Hyperswitch provides next_action that sdk has to use whcih contains connector_reference_id
Payment will reach to terminal status in sdk, so, there should be a retrieve call to hyperswitch that updates the status in the system

Additional Changes

[x] This PR modifies the API contract
[x] This PR modifies application configuration/environment variables

Added payme in connectors_with_delayed_session_response, as payme also follows delayed session flow

Motivation and Context

Add support for Apple Pay through PayMe
How did you test it?

Local testing not possible
Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[x] I reviewed submitted code

@Sangamesh26 If this PR is not required, can you close this?

Closing this, as same has been covered in #1922


fill screen

Hi
How to fill the screen.. see pic I don't need black area

视频会变形的

No problem, but how?

extends JCVideoPlayer{
  @Override
  onVideoSizeChanged(){
    //you can get video real size here
    //then set size you want
  }
}

You can see black on top and bottom in the video, the black is a part of the video, Video also has problem.

i want fill full screen ..
can write full code

I will tell you your shortcut is good effect. you do not need to change .

don't work :(
@Override
onVideoSizeChanged(){
//what write here
}
}
i want fill for all device

How is it going

you have skype ?

No,  we use Wechat, skype need to spend money.


Make Serial debug optional

This wrapps all Serial.print() into a macro to be able to switch the logging off at compile-time. Without it, there is more power for protocoll processing.
This is based on PR #15.

Debugging or Logging? Many of this messages are helpful for the user and support.
We should not make the Gateway silent.

I think the serial pronting is purely debugging, as teh device is not intended to have a serial adapter attached. However, I think its a waste of essources to pump stuff to the UART no matter if its connected to anything. My devices are a ESP-12E which are only connected to a serial adapter to get falshed (or debugged).
For logging or debugging y the enduser I would suggest to use something like Syslog or having a log-view in the Frontend. The esp8266_milight_hub is a good example how to present log messages in a frontend.

I think, serial logging, did not waste that much resources on a ESP, at least until now it did not.
I just say, we should not make the gateway silent. Logging is a important behavior. Mostly you are not required to see the logs, but if you run into trouble you are happy about logs. Using a simple lib is fine and a alternative log-view frontend would be nice.
syslog might be a little bit overkill.

Actually syslog is pretty simple. You just push some packets over UDP. To receive them you can just have a simple script. I built this for another project: https://github.com/Retardigrades/tent-update-controller/blob/master/syslog_receiver.py

The sender side could then look like https://github.com/Retardigrades/tent-gyro-esp/blob/master/src/log.h

Merged in dba9a95a62b3f6dc76de5bbf8d54d4ac0f1f69d0 .


SAR-9324 - Updated connector and service to call new BE register route

I wrote on slack ... have a look please


Background color with "artifacts"

The background color has "artifacts" and change while scrolling:

Thanks for the report, @xangelux . Which colorscheme are you using?

I was trying to use Molokai but I see it doesn't take it, it flickers when I open oni and then back to the default one

Unfortunately I'm not able to repro this (although I'm only testing on Windows & Linux) - perhaps its an OSX specific rendering issue?

I poked around a bit and set colorcolumn=80 and changed to Monokai colorscheme, and I do see a few rendering irregularities on Windows:

Could potentially be related

Not seeing this reproduce anymore (and the rendering strategy has changed a few times since this was opened!). Please feel free to reopen or log a new issue if you are still seeing this.


Adding an inter-window communications mechanism

I think it would be quite easy to add the ability for 2 or more windows who utilize the same cross-domain-local-storage to communicate with each other.   Each window would declare their reference-name to the cross-domain-local-storage package...and each window would addEventListener to a specific message that would come from the iframe.
The iframe (in each window) would monitor the localStorage message queue for messages directed at a particular window and call postMessage to deliver that message.
Do you see any problems with this strategy?   Do you know of any other packages that attempt this kind of functionalty?

@robertlight  - that's a great idea.
I think that it comes to solve somewhat of a different problem (real time communication between cross domain iframe).
I don't know if there are other packages that does that but I'm guessing that there are.

I was thinking of storing arrays in localStorage where we can push and pop messages off the array and then communicate those messages via postMessage to the parent window.
The problem, of course, is that localStorage is not threadsafe across multiple browser windows (or tabs)....so there is a small chance that the array would could be overwritten and a message lost.


correct position logic of track and thumb

When I cloned the project and run the example, everything works correctly! However, in my personal object, the track & thumb part are higher than expected.
Here I will show some screenshot:

My code is almost the same with Examples, but got incorrect result.
I read through the code and try to solve my problem:

minimumTrack use marginTop to get a correct Y axis coordinates, there is no need to set absolute to minimumTrack.
thumb use transform to get correct X|Y axis coordinates, and I preserve the X part and use top value instead.

I tested the Example's ios part and all work correctly. And I run my own project, position is correct now.
@jeanregisser Hope you can review the pr soon.

@jeanregisser what about accept that pr?

Thanks @creeperyang, this has been fixed by #67


Update dockertoolbox.rb v1.9.0d

version 1.9.0d https://github.com/docker/toolbox/releases/tag/v1.9.0d
sha256 = 3d331ce72576b55b1a7ad0b0570b9fb43f85479eefdb06b5b518ee308fc13acf

Thank you for the contribution. It was merged directly as 1d9ed6174637d148dc3d7342c7a4536ca651516b to keep commit history cleaner. Your contribution is still credited to you.

Thank you for the contribution. It was merged directly as 4dc1b8a34d410608965c5d6e7d3ea2c814dbc36f to keep commit history cleaner. Your contribution is still credited to you.


Fix for broken Angular dependency semver

Fixed error in package.json angular dependency semver which was forcing angular 1.4 installation

Thanks :+1:


Improvement human evaluation view

Summary

Users want a better way to do annotations in Agenta. We'll make it more flexible for setting up annotation jobs.

Description

Right now, our system doesn't let users customize annotation jobs. They want to:

Choose their own columns for marking the right answers.
Decide how they want feedback and evaluations (like simple annotations, single evaluations, or comparisons).

Proposed Solution

We'll add a new setup in the human evaluation area to let users:

Pick the type of evaluation (annotation, single, or comparison).
Choose and name their own columns, including one for the right answer.
Select the kind of feedback they want for each job.

[x] Create wireframes

Postponed two Q1 2025


Add support for new destructuring syntax

See ceylon/ceylon#7220.
Question: What do we do about the old syntax? Apparently the compiler still supports it for a while; do we want to have two kinds of destructuring expressions in the AST?

What do we do about the old syntax?

Unless I hear any objections, I think I’ll go with the easier route of only having one type of destructuring in ceylon.ast.core: the new syntax. ceylon.ast.redhat will probably map old-style destructuring to that, but it’ll be a lossy conversion.

So you would be able to consume all valid Ceylon programs, but only represent and produce non-deprecated destructurings? That sounds like a reasonable compromise to me.

In fact, that sounds quite nice for the use-cases I can think of. Anyone using ceylon.ast to read or analyze a program will have one less thing to worry about.

Hm, then you won’t like to hear that I’m already starting to second-guess myself on this :D
Because it looks like in ceylon.ast.core this will be a new node type either way, called LetStatement, analogous to LetExpression, so from that standpoint perhaps I might as well leave Destructure around? But the conversion is likely to be the hairier part, and that will probably be simpler if Destructure is removed.

I'm not sure I have a horse in this race, but I think the important thing is that it should be possible to consume all valid Ceylon source files, one way or another.

I am not sure, conversion should be the concern of ceylon.ast

Because it looks like in ceylon.ast.core this will be a new node type either way, called LetStatement, analogous to LetExpression

Hm, nevermind, the spec still calls it Destructure.

The parser produces equivalent ASTs for both syntaxes anyways, so we get support for the old syntax almost for free.


release interpret-community v0.14.2

release interpret-community v0.14.2

Categorical cohort fix for explanation dashboard
String class labels fix with mimic explainer
Add ipython as a dependency to visualization extra
Fixed credentialed POST requests for predictions in dashboard (tested in notebook VM), and added support for remote VM with public IP
Fix for job retries in pipelines

Approved.


Remove irrelevant exceptions

Codecov Report

:exclamation: No coverage uploaded for pull request base (validate-relation@8169497). Click here to learn what that means.
The diff coverage is n/a.

@@                  Coverage Diff                  @@
##             validate-relation        #7   +/-   ##
=====================================================
  Coverage                     ?   100.00%
=====================================================
  Files                        ?        18
  Lines                        ?      1010
  Branches                     ?         0
=====================================================
  Hits                         ?      1010
  Misses                       ?         0
  Partials                     ?         0

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


adding provenance log identifier proposal

Signed-off-by: Dave Huseby<EMAIL_ADDRESS>

merged with #8


Questions about stateful GRU

First, thank you for sharing stateful RNN(GRU) code.
I checked SGRU and the imdb examples for text generation.
It looks like

state reset or modifying is triggered when special callback conditions is met
in example code, the trigger is 'every N batch'

Probably, we can extend your code to any state change with any callback condition. correct?
One more simple question.
What's the main advantages of stateful RNN over normal RNN?
Is it just for controlling state?

There will be advantage when you have long sequences that you have to break into several batches. You know that we usually max the input sequence to 100 elements, right? But some phrases, in nlp for instance, are larger than that. Than we put part of the phrase in one batch and the rest in others. But if you clean up the hidden state after every batch your network won't actually have the right context.
I believe the imdb dataset does not have that problem. In that case, I think you will prefer the feature I'll introduce next "adaptive initial states". ;) stay tuned and thanks for you interest and kind words!!!

Thank you. Now I understood usage of stateful rnn. I am looking forward to adaptive initial state thing. :)
I will close this issue.

I wanted to ask more about the advantages of stateful rnn's. @EderSantana you mentioned that if you go longer than 100 input sequences, you should use a stateful rnn. Why is this the case?
Are you saying that a single LSTM/GRU 'memory' starts to diminish after 100 timesteps? Does it do a much better job on 10 timesteps than 100 timesteps?
If this is the case, wouldn't it be more advantageous to do 10 timesteps then perform the next batch? I'm sorry if some of these questions don't make sense. I'm just really confused as to what is being done, but it looks really cool.

we used to fix it up to 100 to avoid Theano exploding gpu memory or gradients from growing to large. Now we know better and it is easier to vanish a gradient than to explode it.
stateful is similar to using truncate_gradiente that also avoids iterations that are too deep in time, but is still better than restart the hidden state to zero. Use stateful when your sentence is longer than you can fit in a sample. Also, make sure the next batch continues the sequences.

Also, make sure the next batch continues the sequences.

Okay let me ask you this then: Is there an advantage to not randomizing your sequences, and always using a stateful GRU?
Right now, I'm feeding two sentences, and asking it to predict the next sentence. These sentences are from articles/textbooks on astronomy.
I can easily fit two sentences (about 50 words) with no gpu memory problems. Additionally, I know that when you use model.fit, Keras will randomize your sequences. But if I did not randomize them, would a stateful GRU be helpful here?
I guess what I'm asking is: Would it learn that the previous sequence is related to the next sequence? That way, when its predicting, it predicts a sentence. Then, you feed it the predicted sentence it just produced. Afterwards, without resetting its states, it goes ahead and predicts the next sentence.
I hate asking you so many questions, so if there is a paper or guide you would rather me read, I'm totally for it. Don't want carpal tunnel exacerbated!

This makes much more sense. Its good to know that this is available!


Bugfix/op 4381 maya  keep existing AOVs when creating render instance

Brief description
Introduce an option to allow users to choose if existing AOVs should be kept when creating render instance in Openpype setting.
The setting is se to false by default

Description
The new options in Openpype Setting named "remove_AOVs" is avaliable in this PR. If this is set to be True, it would clean up the previous AOVs which is left by the deleted render instance. If this is set to be False, It would still store the existing AOVs as renderpasses.
Additional info
Nothing specific
Testing notes:

In Openpype Settings > Maya> Render Settings > Arnold Renderer, there is a on/off options of remove_AOVs
If you enable it, it would help you to clean up the existing AOVs if you create a new render instance.
if you disable it, it would keep the existing AOVs while creating new AOVs without duplication of existing AOVs.

resolves https://github.com/pypeclub/OpenPype/issues/4073

I don't think it should be per renderer - and I agree with changing it to Remove existing AOVs

I don't think it should be per renderer - and I agree with changing it to Remove existing AOVs

I have renamed in the updated PR as well as swapping the position of remove existing AOVs attribute with the tiled attribute. The remove existing AOVs is now located right before the AOVs to create attribute

so for now is it only valid for Arnold?

I don't think it should be per renderer - and I agree with changing it to Remove existing AOVs

so the settings should be like this now

and the setting of removing AOV's should be valid for all renderers below.

I don't think it should be per renderer - and I agree with changing it to Remove existing AOVs

so the settings should be like this now

and the setting of removing AOV's should be valid for all renderers below.

I have moved the setting to the Render Settings. And also added the remove_aovs options for Redshift.

there is some issue with vray
# Error: KeyError: file D:\REPO\OpenPype\openpype\hosts\maya\api\lib_rendersettings.py line 179: 'remove_aovs'
and with redshift nothing is happening when running Set Render Settings or creating a Render Instance

The updated PR has fixed the error of removing aovs as well as removing the light-select aov

Did run new tests in maya with arnold and redshift and lastly with vray
Regarding OP settings for AOVs (creation / deleting existing ones) All works fine in all three renderers.
Succesfuly adds predefined AOVs in OP settings and also reacts to "Remove Existing AOVs" switch too...


[DOC] Missing old version APIs documentation

Is your doc request related to a problem? Please describe or add related issue ID.
Although we have multiple harvester version options in documentation, but we only have v1.3 and dev APIs documentation. When we click v1.1 harvester documentation, then click API, it'll be redirected  v1.3 APIs documentation. In other words, I can't see v1.1 APIs documentation.
Describe the solution you'd like
Do we need to add it back?
The other thing is that our openapi generator follows our harvester/harvester repo. If we fix some errors of openapi generator in new release version, we can't apply it on our old release version unless we backport. But, it seems weird that only backport those fixes for fixing openapi generator. Maybe we could have another repo only for openapi generator?
It's a open question here, welcome any ideas.

@innobead I am not familiar with how exactly the API documentation is generated. What I know is from this PR, which @m-ildefons created.

I'll check this one out. I'm sure it's a fairly small error in the docusaurus config somewhere.

The API docs for the old versions is there (e.g. https://docs.harvesterhci.io/v1.2/api/create-namespaced-virtual-machine-backup/) but what's missing is a link or a menu that leads to it. Somehow the version-change menu doesn't work for the API docs of older versions, but it does work for v1.4/dev and v1.3. There also doesn't seem to be a landing page/category index for those versions.


add vimeo tips

add tips on vimeo: here's demo video: https://vimeo.com/670055676
also fixed a strange bug that was adding these characters while parsing lightningaddress to lnurlp url https://lntxbot.com/.well-known/lnurlp/%EF%B8%8Fpseudozach. this was causing lnurlp tips on youtube/vimeo to fail silently.

hopefully fixes: https://github.com/getAlby/lightning-browser-extension/issues/477

Thanks a lot for taking this on!
how was it for you to create this? when thinking of the architecture we tried to make it easy for people to create such extractors without knowing much of the extension code. would love to hear your feedback.

it's great, just the way I like it. I just copied youtubevideo battery and modified it to work with vimeo. Definitely beginner friendly!

I found one more issues. when an account is "pro" then a pro badge is in that channelLink span.
e.g. here: https://vimeo.com/658711759

Not sure why but I am testing this and it is not working for me...

I found one more issues. when an account is "pro" then a pro badge is in that channelLink span. e.g. here: https://vimeo.com/658711759

good point .clip_info-subline--watch .js-user_link works for both I'll change it to this.

@secondl1ght what means "not working".
can you explain what you did? which video did you test? what was the URL? what did you see? what did you expect?

I went to https://vimeo.com/670055676 and when I opened up Alby there was no prompt to send any sats to the LN address displayed on the page.. did I miss a step?

@secondl1ght hmm. works for me. are you using the latest version of this branch?

yep.. :\

This worked for me, I've sent 1000 sats to @pseudozach for his nice video.

Only (unrelated to PR) feedback that I have is that it takes a bit (2-3 s) for the second screen to show up, and there is no loading indicator in the mean time.

thanks for the review!!
I think a simple loading indicator was added in: https://github.com/getAlby/lightning-browser-extension/pull/575
and I am not sure why the lntxbot sometimes seems slow?


Cryptomatte not working with DWA compression

Cryptomatte works fine on a multichannel EXR with ZIP scanline compression, but not with DWAA or DWAB compression. That is, it is not possible to select the objects in Nuke with the Cryptomatte gizmo when the image is rendered with DWA compression. Experiencing this both with Arnold and Vray renders.

DWA compression is lossy. Cryptomatte relies on exact values in the images,
so lossy compression will break it.
On Thu, 21 Sep 2017 at 15:19, sharktacos<EMAIL_ADDRESS>wrote:

Cryptomatte works fine on a multichannel EXR with ZIP scanline
compression, but not with DWAA or DWAB compression. That is, it is not
possible to select the objects in Nuke with the Cryptomatte gizmo when the
image is rendered with DWA compression. Experiencing this both with Arnold
and Vray renders.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Psyop/Cryptomatte/issues/35, or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2IXaQ3cJHRGo4-PsuroqvkhGIJrVbbks5skdW1gaJpZM4Pev0Q
.

DWA is only lossy on channels named:
R, G, B, RY, BY, Y (case sensitive). All other channel names are treated as lossless.

Yeah was just reading the source code. Yay for magic constants. So...
everyone has to change to outputting .xyz instead of .rgb now?
On Thu, 21 Sep 2017 at 15:44, Deke Kincaid<EMAIL_ADDRESS>wrote:

DWA is only lossy on channels named:
R, G, B, RY, BY, Y (case sensitive). All other channel names are treated
as lossless.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Psyop/Cryptomatte/issues/35#issuecomment-331042950,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2IXdcg-jF2X0XtFQlfRG4zIqqwlocJks5skdu5gaJpZM4Pev0Q
.

x y z should work, just be careful of Y (capitol Y is lossy). I believe if they were named r g b (lowercase) that would work too. They just can't be named R G B (capitol letters).

rgb gets lossy compression as well. Full list is here in function
initializeDefaultChannelRules():
https://github.com/openexr/openexr/blob/develop/OpenEXR/IlmImf/ImfDwaCompressor.cpp
Would be nice if they'd allowed for customising it via header metadata or
something rather than just hard-coding it...
On Thu, 21 Sep 2017 at 18:18, sharktacos<EMAIL_ADDRESS>wrote:

x y z should work, just be careful of Y (capitol Y is lossy). I believe if
they were named r g b (lowercase) that would work too. They just can't be
named R G B (capitol letters).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Psyop/Cryptomatte/issues/35#issuecomment-331062268,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2IXVJoTtCjjdvHXvldi0WmyFOxr2gPks5skf-ugaJpZM4Pev0Q
.

This will be fixed in a V-Ray nightly soon. To fix it we patched the OpenEXR2 library to allow us to explicitly specify if a channel should be DWA compressed.
Best regards,
Vlado

From: Anders Langlands<EMAIL_ADDRESS>Sent: Thursday, September 21, 2017 9:21:10 AM
To: Psyop/Cryptomatte
Cc: Subscribed
Subject: Re: [Psyop/Cryptomatte] Cryptomatte not working with DWA compression (#35)
rgb gets lossy compression as well. Full list is here in function
initializeDefaultChannelRules():
https://github.com/openexr/openexr/blob/develop/OpenEXR/IlmImf/ImfDwaCompressor.cpp
Would be nice if they'd allowed for customising it via header metadata or
something rather than just hard-coding it...
On Thu, 21 Sep 2017 at 18:18, sharktacos<EMAIL_ADDRESS>wrote:

x y z should work, just be careful of Y (capitol Y is lossy). I believe if
they were named r g b (lowercase) that would work too. They just can't be
named R G B (capitol letters).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Psyop/Cryptomatte/issues/35#issuecomment-331062268,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2IXVJoTtCjjdvHXvldi0WmyFOxr2gPks5skf-ugaJpZM4Pev0Q
.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/Psyop/Cryptomatte/issues/35#issuecomment-331062737, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABgLWi04WWpEfPoA-pT5OPyCxrljzDQUks5skgBWgaJpZM4Pev0Q.

@vkoylazov Very cool. Are you compressing the coverages? Roughly what kind of file size improvements are you seeing with DWA Cryptomattes?

Another observation: While you are required to have the same compression for the whole file, you are allowed to have different channels with different data types per channel. (EXR technical introduction, page 7), and having the coverages at half I think would always make sense, maybe even with lossy compression.
We'd have to test pretty carefully that images with RGBA set to different data types don't confuse the various applications, but that's another thing to try.

rgb doesn’t get lossy.  If you look at the source that is only for openexr 1.0 which was before dwa shipped to the public. 2.0 is only for capital RGBYGYRY.


Add support for tooltips and custom states for the ActivityDate entry

Adds support for tooltips to the date template (I can add support for the rest of the entries if needed)
Allows overriding the date field when a user supplies a getStateUsing closure to allow custom values for that part of the activity log. However, this is probably a breaking change so I'm open to suggestions on how to implement this.

Hello @sprtk-ches , awesome this is good! But can you also add this  in read me and explain what this use for so that users will know this functionality. Thank youu! I will review it once you added it.

Hello @sprtk-ches , awesome this is good! But can you also add this in read me and explain what this use for so that users will know this functionality. Thank youu! I will review it once you added it.

@199ocero 🤔 I'm really not sure about the 2nd change. For example, someone with the following code
ActivityDate::make('created_at')
    ->getStateUsing(fn ($record) => $record->created_at)
    ->date('F j, Y')

might expect that the created_at value will be formatted with the given format, but it won't.
I think it would be better to focus this PR on adding tooltip support, and I'll create another PR for the getStateUsing change and post it to the Discord channel for people to have a look. What do you think?

Yes @sprtk-ches  that would be better. Make this for tooltip and make another PR for state and will see where it goes. Thank youu! Oh and just make sure to edit also the read me for the tooltip.

Hey @sprtk-ches  any update for this? I will close this for now if no updates. Thank youu!


kernel.timer.tickless: frdmk64f failure

Describe the bug
FAIL - test_timer_duration_period
To Reproduce
Steps to reproduce the behavior:

mkdir build; cd build
cmake -DBOARD=frdm_k64f ..
make
See error

Expected behavior
test_timer_duration_period
Impact
timer settings
Logs and console output
*** Booting Zephyr OS version 2.4.0-rc1  ***
    Running test suite timer_api
    ===================================================================
    START - test_time_conversions
     PASS - test_time_conversions
    ===================================================================
    START - test_timer_duration_period

        Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/timer/timer_api/src/main.c:94: duration_expire: (interval >= 100) || (((10000 % 1000U) != 0) && (interval == 100 - 1)) is false

     FAIL - test_timer_duration_period
    ===================================================================
    START - test_timer_period_0
     PASS - test_timer_period_0
    ===================================================================
    START - test_timer_expirefn_null
     PASS - test_timer_expirefn_null
    ===================================================================
    START - test_timer_periodicity
     PASS - test_timer_periodicity
    ===================================================================
    START - test_timer_status_get
     PASS - test_timer_status_get
    ===================================================================
    START - test_timer_status_get_anytime
     PASS - test_timer_status_get_anytime
    ===================================================================
    START - test_timer_status_sync
     PASS - test_timer_status_sync
    ===================================================================
    START - test_timer_k_define
     PASS - test_timer_k_define
    ===================================================================
    START - test_timer_user_data
     PASS - test_timer_user_data
    ===================================================================
    START - test_timer_remaining
     PASS - test_timer_remaining
    ===================================================================
    START - test_timeout_abs
     PASS - test_timeout_abs
    ===================================================================
    Test suite timer_api failed.
    ===================================================================
    PROJECT EXECUTION FAILED

Environment (please complete the following information):

OS: (e.g. Linux)
Toolchain (e.g Zephyr SDK, ...)
Commit SHA or Version used: v2.4.0-rc1

@MaureenHelm , @dleach02

@hakehuang can you retest this? I'm unable to reproduce this particular issue.

tested here and it is working fine as well. Couldn't reproduce the problem.

@dleach02 If I rerun it for several times, it is OK, the is a low changes it gets wrong, looks like the test_timer_duration_period case does not give much margin if the code runs slow for same reason. I will close it.


Update Windows App SDK Roadmap

/azp run

/azp run

@gabbybilka did you see my comments above?

Doesn't matter now, went live and shown on WinUI Community Call. Great community engagement.

Hey @riverar, unfortunately I wasn't able to address your comments yesterday as we were running into issues with the Azure Pipelines bot and had to manually run the PR pipeline to merge in the roadmap. As time was short between then and the call, I prioritized having a publicly available roadmap for folks to view and leave additional feedback on.
I've opened up a new PR to refine the roadmap based off of your suggestions, thank you! #2273


Sliding Window Maximum

I am willing to add a sliding window maximum solution and explanation (with approach and thought process) in JAVA.
Kindly assign this task to me.
Thanks in advance:)

greetings to manager, can you assign this task to me? I can complete this test positively.

Hey! I want to contribute to this problem in C++, you can count on me for sure.

Heyyy @1dharode,
I would like to add the program of Sliding Window Maximum in C++,Java and Python.
Kindly Assign it to me.
Thank You!!

@1dharode Please assign this task to me
I have practiced n number of problems related to sliding window maximum
By the way I could make it in c++
Thank You!!

Hello, Can you please assign this issue to me?
Thanks in advance :)


Feature/AREG-131 - Fix - "Vendor type not set correctly"

Jira link - https://metacell.atlassian.net/browse/AREG-131
Task description:

pass antibody commercial_type from dto to set if new vendor is created.

Before this PR: it use to set OTHER as default commercial_type for a new vendor.
Logic for the implementation:

video demo
https://github.com/MetaCell/scicrunch-antibody-registry/assets/59233227/f65cf45d-943e-4179-96f8-6d66464e2535

Looks good to me
On Sun, Apr 21, 2024 at 3:08 AM D. Gopal Krishna @.***>
wrote:

Jira link - https://metacell.atlassian.net/browse/AREG-131
Task description:

pass antibody commercial_type from dto to set if new vendor is
created.

Logic for the implementation:
image.png (view on web)
https://github.com/MetaCell/scicrunch-antibody-registry/assets/59233227/51887944-ff7a-4209-817c-5b911ae41596
You can view, comment on, or merge this pull request online at:
https://github.com/MetaCell/scicrunch-antibody-registry/pull/243
Commit Summary

46ae44d
https://github.com/MetaCell/scicrunch-antibody-registry/pull/243/commits/46ae44dbb8b440b5b67f40a7560655fc41a0f4b7
AREG-131 - update the mapper to include the commercial-type
df7e5ce
https://github.com/MetaCell/scicrunch-antibody-registry/pull/243/commits/df7e5ce472bd3e246037ccafbb60c555c73db8f6
AREG-131 support commercial-type when new vendor is created
232c179
https://github.com/MetaCell/scicrunch-antibody-registry/pull/243/commits/232c179a2ddd8ba27dce4b5efd4adb25de25069a
AREG-131 default to commercial for vendor type
17a3508
https://github.com/MetaCell/scicrunch-antibody-registry/pull/243/commits/17a3508ff95975ad2052513058d3b6f78e767d47
Merge branch 'develop' into feature/AREG-131

File Changes
(2 files
https://github.com/MetaCell/scicrunch-antibody-registry/pull/243/files)

M applications/portal/backend/api/mappers/antibody_mapper.py
https://github.com/MetaCell/scicrunch-antibody-registry/pull/243/files#diff-13fd7257001dbedc1244636114fe1435c9cbe0992d60abc974244e71e4e65d09
(6)
M applications/portal/backend/api/models.py
https://github.com/MetaCell/scicrunch-antibody-registry/pull/243/files#diff-20dd32a0202b371bcaa24b03452ce44ee67bdd0c6bc2ce58ef0dd7495c290b2b
(12)

Patch Links:

https://github.com/MetaCell/scicrunch-antibody-registry/pull/243.patch

https://github.com/MetaCell/scicrunch-antibody-registry/pull/243.diff

—
Reply to this email directly, view it on GitHub
https://github.com/MetaCell/scicrunch-antibody-registry/pull/243, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNSWNI467G6JVV6K2W7Z43Y6OF2VAVCNFSM6AAAAABGRH6FPSVHI2DSMVQWIX3LMV43ASLTON2WKOZSGI2TKMBQGAZTENQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

--
All key biological entities deserve an #RRID!
orcid.org/0000-0002-5497-0243


Hodak/t 14310 relay meter on failure show error

Overview
This adds a generic banner card that can be used in different scenarios.  The current use of it, is for when our relay meter is not providing accurate data.  This at least gives users an alert to know they might be getting suspicious data.
Waiting on correct copy.
Error:

Informational:

Warning:

Success:

Type of change

[ ] Bug fix (non-breaking change; fixes an issue).
[X] New feature (non-breaking change; adds functionality).
[ ] Breaking change (fix or feature that breaks existing functionality).
[ ] This change requires a documentation update.
[ ] Operational change.
[ ] Test Coverage.

Checklist

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

Dependencies
A bulleted list of any pull requests that are required to be merged/deployed
before this pull request can be tested.

Operational changes
Back end changes
Updates to shared libraries
etc

Test Configuration
The hardware stack you used to test your changes.
Fill in those that apply, remove the rest.

Hardware: HARDWARE NAME
OS: OS NAME AND VERSION
Node version: NODE VERSION
PNPM version: PNPM VERSION

Evidence
video, screenshots, log output or other media that demonstrates your changes working.

greeen?

@kutoft it was green because I was screenshotting, that is the success banner.  It has been changed back to error for this instance.

Close T-14310


--fix removes curly bracket space after html

I just upgraded from "eslint": "^6.1.0", "eslint-plugin-react": "^7.14.2" to "eslint": "^6.5.1", "eslint-plugin-react": "^7.15.1".
Running yarn eslint ./src --fix removes any instance of a {' '} since a new line now creates a space in React jsx like:

    Hello
    {' '}
    World

> Hello World

--fix now changes to:

    Hello
    World

> Hello World

But if I have html within that, it removes the space and the newline does not create a space.   For example:

    Hello*
    {' '}
    World

> Hello* World

--fix now changes to:

    Hello*
    World

> Hello*World      (missing space)

I suspect this breaking change caused this https://github.com/yannickcr/eslint-plugin-react/pull/2422

This will be fixed in #2437.


Add FTDI udev rule

Hi! I would like to add one entry to the 69-probe-rs.rules:
#  FTDI JTAG Debugger
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6010", MODE="660", GROUP="plugdev", TAG+="uaccess"

Is that possible? Shall I open a PR to openOCD to get it here?

Hi :wave:
The file is stored here: https://github.com/probe-rs/webpage/blob/master/static/files/69-probe-rs.rules
So you can open a PR to that repository, and then it'll get updated on the web page.

Thanks for pointing to it! Just created https://github.com/probe-rs/webpage/pull/93


We cannot allow upcasting a DA to some arbitrary protocol P, where that protocol P requirement isn't async + throws, because cross-actor calls must always have this effect.
We missed to handle an edge case in the model, which is requirements declared on a protocol DAP: DistributedActor which is where we CANNOT "peel off" the distributedness off the distributed actor, by upcasting it to that DAP.
protocol WatchingDA: DistributedActor {
  func terminated(da: String) async
}

distributed actor DA_WatchingDA: WatchingDA {
  func terminated(da: String) { } // should be fine
}

// The isolation checking itself is UNCHANGED and relies on the usual rules:
func test<WDA: WatchingDA>(da: WDA) async throws {
  try await da.terminated(da: "") // error: because of the normal distributed isolation checking rules; nothing new here
  await da.whenLocal { await $0.terminated(da: "OK") } // this is allowed
  // self.terminated(da:) is of course also allowed

  await da.whenLocal { $0.terminated(da: "OK") } // crashes because of  #59356
}

Errors forcing us to adopt nonisolated or distributed for this method; while it is strictly speaking not necessary.
We CAN witness this method, but it will be impossible to call when erased to WatchingDA because distributed actor isolation will prevent it from being called (!),
and this is exactly what we want. To only be able to call "inside" or "when known to be local", which is how frameworks can implement their lifecycle management hooks.
Example:
In practice this missing checking rule caused us to have to write such terrible workarounds:
    public nonisolated func terminated(actor id: ActorID) async { // HORRIBLE; we know we are the local actor here always when this is called (because OUTER caller does this whenLocal dance)
       await self.whenLocal { __secretlyKnownToBeLocal in
           await __secretlyKnownToBeLocal.probe.tell("Received terminated: \(id)")
        }
    }

     public distributed func terminated(actor id: ActorID) async { // REALLY NOT distributed
         self.probe.tell("Received terminated: \(id)")
     }

I did tests with working around the limitation of actor isolation with generics -- once #59356 is done we can undo the hack here 👍

@swift-ci please smoke test

Thank you! I'll dig into the comments 🙏

@swift-ci please smoke test and merge


Collapsible metadata

This change hides some of the audit metadata in a collapsible section. It makes use of the existing partial used to hide some of the filters in the sidebar. The partial has been renamed and modified to fit this use case too.

Dependencies

[ ] https://github.com/alphagov/content-performance-manager/pull/422

 (3) Collapse content item metadata into "More details" section

Review app: https://cpm-prototype-426.herokuapp.com/audits


CUDA Error CUDA_ERROR_NO_DEVICE: no CUDA-capable device is detected while calling init (cuInit)

I have the same issue with my cuda 12.1 run under wsl2 with both python 310-312 tested
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Mon_Apr__3_17:16:06_PDT_2023
Cuda compilation tools, release 12.1, V12.1.105
Build cuda_12.1.r12.1/compiler.32688072_0
I got the error like:
[E 12/20/24 08:45:40.689 2984] [cuda_driver.h:operator()@92] CUDA Error CUDA_ERROR_NO_DEVICE: no CUDA-capable device is detected while calling init (cuInit)
However I can run in windows with cuda device working properly. but rendering is not supported,

the same problem with wsl2，python310,  cuda11.6

Hi @TTPlanetPig .
I encountered the same problem a few days ago, and I have solved it. Maybe you can refer to my issue #187  and try to solve it. Hope it can help you.


feat(dalle): Add support for OpenAI DALL-E

Integrate DALL-E image generation API.
https://beta.openai.com/docs/guides/images/usage

:tada: This PR is included in version 1.3.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Prefetch/prerender behavior

Do some research on whether this project needs them or not.
Implement, if needed.

It looks like an unnecessary complication for blogs:

Most people do not navigate to the second page, and it is difficult to tell which page it will be => there is no need for prerendering pages.
Custom scripts are rare; most of the time, it will be unnecessary traffic => There is no need for prefetching pages.


Update to 2.2.25

2.2.25	2017-01-25T10:59:53-0700
    Added "stamp-vti" and "version.texi" to ".gitignore".

2.2.24	2017-01-24T14:42:49-0700
    Added (against my better judgment) the unit "ppv". Use "1" instead and call
    the physical quantity "volume fraction".

    Fixed utCalendar() in the UDUNITS-1 interface returning 60 seconds.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Windows is failing with:
udunits2: Couldn't initialize unit-system from database "C:\bld\udunits2_1487327159760\_b_env\Library\share\udunits\udunits2.xml": No such file or directory
(C:\bld\udunits2_1487327159760\_t_env) C:\bld\udunits2_1487327159760\test_tmp>if errorlevel 1 exit 1
TESTS FAILED: udunits2-2.2.25-vc9_0

@ocefpaf yep! I've seen that... and I'm confused :confused: As far as I can tell the XML library should be being placed there by the build process...

I am puzzled too. I will try to get my hands on a Windows machine over the weekend to investigate.

@ocefpaf This is now causing the AppVeyor build for the main udunits2 repo to fail. No clue why.

So... The files do exist and they do make it into the package in the end. However, they are not in the right directory during the test phase.
@msarahan can you comment on that? Maybe there is a new feature in conda-build that I am missing here?

I guess that whatever bug made into conda-build got fixed and this is now passing on Windows!
Merging b/c Travis-CI is passing on my instance.


Fix link Markdown syntax

I believe the line break is causing the link to be displayed as raw markdown. I have a co-worker at NIWA that works with the Deep South Challenge and may be interested to have a look for their Earth System Models.
Thanks for sharing!
Bruno

thanks @kinow sincerely appreciate it!


[DCOS-2402] Prints the ssh command used in dcos node ssh and `dcos service log

marathon` to help the user debug SSH issues

Note I don't know how to test this because for some weird reason I can't get the stderr output from the subprocess.  stderr.read() always returns an empty string.  It has something to do with attaching stdin to the pty.

@jsancio: tests passing

Note I don't know how to test this because for some weird reason I can't get the stderr output from the subprocess. stderr.read() always returns an empty string. It has something to do with attaching stdin to the pty.

Can you point me to test that would need fixing? Maybe an extra pair of eyes can figure out what is wrong.

LGTM.


 It needs to take account for vanilla OMG specifications and have ability to modify/extend beyond that specification to be a genuine 'agnostic' and reliable tool.
link to current development effort.
Will eventually be a submodule.

EDIT: Project repository is located at https://github.com/binaryflesh/pyxmiparser .

After digging through both the normative and informative documentation, I am deciding on making all parts of this in python. This will set quicksilver in stone to stick with UML 2.5.1, which will work for my use case.

EDIT: Renamed repository to reflect now being a library. https://github.com/binaryflesh/xmilib


ci: add release.yml

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (6a7e183) compared to base (6b2ec07).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##              main       #13   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           48        48
  Lines         2201      2201
=========================================
  Hits          2201      2201

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Just a guess

Hi, I noticed that the description of your repo is "What's the issue with rust hashmaps?". The probable answer is that the default hasher in Rust is deliberately chosen to be cryptographically safe at the cost of memory and speed efficiency. Learn more about it here.

@Altair-Bueno Thanks, I have added a link to the video in the readme.
@JohnScience Well I guess the main issue in technique 3 lies in the map being consumed in:
for (key, val) in map {
	...
}

is being consumed out of order. Meaning that if the map was consumed in order (like a Vec) it would have left contiguous space in the memory for the new hashsets to be allocated in without introducing fragmentation.
If the hasher has a role in choosing how a map is consumed as an iterator (and can make it get consumed in order), then yeah, a different hasher could have probably done better with memory fragmentation.


Voxel Optimization

Voxels, as of now, are independent meshes, it would be best to join all of the Voxels into one giant mesh; further more, optimize the giant mesh as much as possible.

Greedy meshing algorithms are probably the best way to move forward with optimization

Voxel-Core now handles the creation of voxel content #29

Voxel-Core now handles the creation of voxel content #29


Can't buffer be used exclusively by a certain data source?

Since duration ms is 0, data will always be collected into the ring buffer. When the ctrlc signal is used to trigger the end of the acquisition, it is found that the data in the buffer with ID 1 does not have track event data, but is overwritten by ftrace.
How to ensure that the buffer with ID 1 only stores track event data and will not be interfered by other data sources?
The config file is as follows:
duration_ms: 0

buffers {
  size_kb: 32768
  fill_policy: RING_BUFFER
}

buffers {
  size_kb: 32768
  fill_policy: RING_BUFFER
}

data_sources {
  config {
    name: "linux.ftrace"
    target_buffer: 0
    ftrace_config {
      compact_sched: {
        enabled: true
      }
      ftrace_events: "sched/sched_switch"
      ftrace_events: "sched/sched_wakeup_new"
      ftrace_events: "sched/sched_wakeup"
      ftrace_events: "sched/sched_waking"
    }
  }
}

data_sources: {
  config {
    name: "track_event"
    target_buffer: 1
  }
}

data_sources {
  config {
    name: "linux.process_stats"
    target_buffer: 0
  }
}

This is definitely supported and something we make use of extensively so it seems unlikely to be a bug in Perfetto. More seems like something is going wrong in track_event or in how you're starting/stopping the trace.
Specifically, what happens if you turn off ftrace and process_stats. Does the track_event show up then?

If ftrace and process_stats are turned off, track_event data cannot be stored in the current RING_BUFFER, and it can be stored by changing the strategy to DISCARD.

I have no idea what that means. Ring buffer and discard do not affect what data can and cannot be stored in a buffer. They simply control the strategy followed when the buffer is full.