Use classnames module to control components classes

I mean this one

I like that.

About this.
It makes a lot of sense for this kind of code:

but it's not needed for a classic:

Sure, it is for conditional class sets only


Prevent deletion of Publications that also exist in the Deposition app

As a curator, the Curation app allows me to delete a publication. However, since the introduction of the Deposition app and the sync process that maintains publications in both the Curation app database and the Deposition app database a publication should not be able to be deleted from the Curation app database if it exists as a Publication in the Deposition app database (a publication object, not just a PMID string for a Body of Work).

@twhetzel - I've done the curation side of things for this ticket, but can't find the 'Delete publication' functionality in the Curation App. I'm sure I'm looking in the wrong place. Can you please point me to where exactly can this be done? Thank you.

@earlEBI @eks-ebi - thank you for helping me find the button.
In terms of expectation for the functionality mentioned in this ticket - would it be enough to add the submissions / body of works possibly associated with the publication to be deleted to that screen that is shown as a warning to confirm the deletion?
The one that starts with Warning! All study details and ancestry information will be deleted ...

That sounds reasonable to me

I think the warning should be enough to stop us from deleting when a submission exists. But I don't see a problem with deactivating the delete button in this case either.

The title talks about Publications but I think it's about Studies.
There is a bit of work by done for the issue that is not yet merged and it also revolves around Studies.
Some Studies that are not in ‘Publish Study’ status cannot be deleted, talked with Elliot and he agreed that this is weird.

@ala-ebi @eks-ebi I think this feature was implemented to prevent curators deleting studies that have a submission associated with them. When an author submits data, they recieve GCSTs, so we should never delete those GCSTs from the db. So that is already prevented.

I think the original ticket refers to the scenario where a submission has been created, but the data has not been imported to curation yet. - see screenshot below. This publication should not be deleted, because there's a submission for it. However, once the submission is imported, we do want to allow deletion of the original study(s) (as in 1. above).

@ala-ebi I tested the version in Snoopy hiding the button, and I think curators do need to have the flexibility to delete studies in certain cases, so it would be better to stick with the warning message. However, is it possible to make it more prominent? Highlighting the row with "Number of submissions in the deposition app" in a different colour could be enough.


Remove jquery DataTable

Resolves #835
This is a pretty intense PR, so apologies in advance.
These model changes are trivial and would remove some client code and/or fix at least one issue I've noticed:

Declare thumbnail and clustalInput attributes as unsortable
The key for pubmed link needs the space removed for CSS reasons
Ortho's accession attribute isn't typed as a linklike it should be

These model changes are less trivial but would eliminate some client hacks/guesswork:

Declaring sort types reliably
Declaring column types reliably

Other tasks/questions that come to mind are as follows:

Go up the RecordTable component's tree to remove unused props/code
Do we need to add truncation to Mesa? Currently the truncateTo property is being ignored.

I've played with the code on a local dev site, and I think it looks and behaves great. The only comment I have, at the moment, from a UI perspective, is that I think the expanded child rows should have a border, and expanded rows should be in bold. I think it makes it easier to parse what's going on. Thoughts?
Live site

This branch

Some updates below regarding the feedback up to this point.

It looks like we can't have both selectable and expandable rows. I don't think we have a use case for both right now, but seems plausible.

I made some changes to allow both features in a single table. As of now, the expand/collapse toggle renders in the first column and the select column renders in the second column. If and when we have a use case for this, we can explore the UX further.

If the first row is expanded, and then the sorting is updated, then new first row will be expanded. We should either use something other than the index to track expanded rows, or we should clear expansion when sorting.

I fixed this issue by passing in a getRowId method that uses the RecordTable's existing getSortIndex function. I think the identifiers stored in the expandedRows array are unique and stable now.

It might be nice if Mesa provided its own error boundary when rendering child rows. That way, if a developer forgets to add one to the childRow component, a render error won't destroy the whole table.

In a slack thread, we decided to just beef up the documentation of the optional childRow prop that tells users to wrap the components in wdk-client's ErrorBoundary. If we add an ErrorBoundary in the coreui library, we won't have the Redux dispatching that the wdk-client version includes.


Add new search predicate to enable searching for messages matching a regex

Pull request checklist:

[x] CHANGELOG.md was updated, if applicable

Description
This PR adds a new regex predicate to the search dialog, to enable filtering for messages matching a specific regex.
It also introduces the option to surround a predicates value in quotation marks, to enable predicate values that contain spaces. (The old predicate functionality was kept intact, so everything that worked before still works exactly the same, just some new options)
for example: regex:"^Kappa [0-9]{1,3}$"

This will require a wiki entry

Oh yeah true, will open a wiki PR once I get home from work


A little HOWTO would make this super useful

Once I get it installed, I’d love to know how to configure postfix to use it!
Thanks,
Dave

It's hard to provide a general documentation because this is just the client library - configuring it is entirely dependent on the software using it.
For Postfix, follow the Postfix SASL Howto. It's exactly the same as configuring for PLAIN (so you'll need noplaintext), with the bearer token in password field in your password map. The only trick is that you need to force it to use the XOAUTH2 mechanism, otherwise it will try to use PLAIN:
smtp_sasl_mechanism_filter = XOAUTH2

The other thing to know is that on most services (Gmail), the bearer token is short-lived, and needs to be regnerated regularly from the refresh token. At FastMail we use Postfix's socketmap table to connect to a daemon process which gets the refresh token from the database, does a request to the remote service to get a bearer token and then return that Postfix. For small numbers of users, it might be sufficient to run a cron job the refreshes tokens and rebuilds the password map.

Thanks!
I didn’t know about these tokens (really I know nothing about OAUTH2 yet; I’m just trying to avoid enabling less-secure applications, and it sounds a bit complex.  I’m just using postfix as to queue and relay outgoing email from my personal machine.  Can you suggest an approach for this case?

If it were me I'd use the cronjob method - every X (half-hour maybe), get a new bearer token and recreate the password map.
The "get a new bearer token" bit would require some command line program that can speak OAuth2. I'm not familiar with any, but I'd put good money on one or two existing. You could also fake it with curl. Google have a bunch of docs showing how to make the calls.


removing a failing system and integration will still cause a request to fail

Bug Description
even after removing a failing system and integration will still cause a request to fail
Steps to Reproduce

create a system from add a system
click on the integrations tab and add an integration (i used domo which will fail connection test once creds are added)
add a new system and integration (i used friendbuy nextgen)
process a access your data request submitted through the privacy center (it will error on domo)
go to view systems and remove the domo system
reprocess the request

Expected behavior
the request still errors on domo
Screenshots
If applicable, add screenshots to help explain your problem.
Environment

Version:
OS:
Python Version:
Docker Version:

Additional context
Add any other context about the problem here.

after doing some initial investigation, it's worth noting that this isn't even specifically tied to reprocessing an existing privacy request. this seems to impact any new, future privacy request too.
this implies a bigger impact to users, and also a different root cause technically - it doesn't have anything to do with request reprocessing, it's some artifact from the deleted system/integration being left around generally, not something tied to a particular request state.

on first glance, it looks like the problem here is that both the connectionconfig and the datasetconfig records are left in tact even after deleting the system (the ctl_systems record is properly removed).
in request_runner_service.py we pretty basically just query for all DatasetConfig and ConnectionConfig records to create our execution graph.
at this point it's probably worth clarifying expectations, since i do notice that the "old" connection still exists in the "connection manager"  screen. do we expect deleting a system to effectively also delete its integration, or should users have to go into the connection manager and explicitly delete the integration? if it's the former, then i think we'll need to update the system delete operation to remove these "integration" artifacts from the db (either by making multiple API calls from the FE or adjusting the API on the BE.

They won't be able to use the connection manager anymore so, yes, deleting a systems should delete the connection/integration.


Enhance Command related UT, reduce running time.

Fix a issue caused by MoverPool.removeStatus.
Reduce the running time of TestcommandExecutor.
Fix a issue caused by ActionRegister singleInstance.
Remove/Modify UT logs.

Codecov Report

Merging #245 into trunk will decrease coverage by 0.23%.
The diff coverage is 60%.

@@            Coverage Diff             @@
##            trunk     #245      +/-   ##
==========================================
- Coverage   57.66%   57.42%   -0.24%
==========================================
  Files         102      102
  Lines        4417     4423       +6
  Branches      658      661       +3
==========================================
- Hits         2547     2540       -7
- Misses       1620     1633      +13
  Partials      250      250


using authentication keys instead of hardcoded email in 2fa

[#136768599]

@edbo are you ok with this change?
It is blocking agents feature.

I'm actually not super keen tying this implementation to our user model. Email kind of stinks too!
Ideally this would something really generic in this library and could be configured to something really specific in a config file.

I dont think im quite following, what do you mean @edbo, that you would like to have the fields by which a user can log in, in a config file which is used here?
authentication_keys option is a feature which they added in some version (and it is mentioned in the readmes and FAQ on how to change the login field for a devise user). Unfortunately the devise_google_authentication was not updated such that it uses the new features, which this pr enables.

can we update this gem to latest version and keep or changes in the same time?

https://github.com/AsteriskLabs/devise_google_authenticator/compare/master...bitgaming:master there seems to be a couple of bug fixes which shouldnt brake anything

Ideally can we fully revert back to their gem?
I just think we've hacked the crap out of this gem to make it work for our benefit and would be good if we didn't at all.

I think we could do that
I will play with it today and get back to you

@mauisu Is this stuck now?

didn't look into it yet as we had other tasks prioritized

@mauisu Apparently this is blocking logging in for agents, suggest we start to give this some priority.

already in progress @edbo

this is a comparison to master https://github.com/AsteriskLabs/devise_google_authenticator/compare/master...bitgaming:feature/pt136768599-agents_fixes
what I left out is:

configurable return path
authentication key rather then email cookie signing (it falls back to email because it is the default)


Add an association class between Tutor and assigned Tutee

The class should represent the link between which tutees were assigned to which tutor.

Added a lesson class in #90 and #91


Make translations work for trends too

Currently courses, studyprogrammes and faculties are shown in Finnish in trends. Trends info is also in Finnish.

#3035 contains this, closing as duplicate


Strange behavior of apoc.agg.statistics

apoc.agg.statistics looks broken. At least with custom percentiles:

Pls. correct me if I'm wrong. To my understanding, passing 0.1  percentile is a request to evaluate a threshold between lowest 10% of the population and the rest of the population. 0.5 percentile is a median.
There's no way in which values for 0.1 and 0.25 could be below (or even equal to) min.
Is it a rounding issue went too far or what? There's a large dispersion, yes, but median & other percentiles should be unaffected by outliers 🤔

Thanks for taking the time to report! I agree, this looks wrong. I'll make sure the relevant team is notified. Sorry for the inconvenience.

Any news on this?

Hi! sorry for the slow response. I took a look and APOC is simply using another library - HdrHistogram, I would assume this is a rounding error and that it would be the min value. It is using the getValueAtPercentile() of the DoubleHistogram class: http://hdrhistogram.org/.

Thank you. The issue was on our side.
In case someone else wants to verify their logic I'm posting a cypher version of statistics with harcoded percentages.
In my case it returns the same data as apoc.agg.statistics.
MATCH (u:User)--(s:Specialization {name: "Web Engineer"})
WITH u
ORDER BY u.articlerank
WITH collect(u) AS us
WITH us[0] AS `u-0.0`,
     us[size(us) * 1 / 10] AS `u-0.1`,
     us[size(us) * 2 / 10] AS `u-0.2`,
     us[size(us) * 3 / 10] AS `u-0.3`,
     us[size(us) * 4 / 10] AS `u-0.4`,
     us[size(us) * 5 / 10] AS `u-0.5`,
     us[size(us) * 6 / 10] AS `u-0.6`,
     us[size(us) * 7 / 10] AS `u-0.7`,
     us[size(us) * 75 / 100] AS `u-0.75`,
     us[size(us) * 8 / 10] AS `u-0.8`,
     us[size(us) * 85 / 100] AS `u-0.85`,
     us[size(us) * 9 / 10] AS `u-0.9`,
     us[size(us) * 95 / 100] AS `u-0.95`,
     us[size(us) * 97 / 100] AS `u-0.97`,
     us[size(us) * 98 / 100] AS `u-0.98`,
     us[size(us) * 99 / 100] AS `u-0.99`,
     us[size(us) - 1] AS `u-1.0`
WITH {
  `0.0`: `u-0.0`.articlerank,
  `0.1`: `u-0.1`.articlerank,
  `0.2`: `u-0.2`.articlerank,
  `0.3`: `u-0.3`.articlerank,
  `0.4`: `u-0.4`.articlerank,
  `0.5`: `u-0.5`.articlerank,
  `0.6`: `u-0.6`.articlerank,
  `0.7`: `u-0.7`.articlerank,
  `0.75`: `u-0.75`.articlerank,
  `0.8`: `u-0.8`.articlerank,
  `0.85`: `u-0.85`.articlerank,
  `0.9`: `u-0.9`.articlerank,
  `0.95`: `u-0.95`.articlerank,
  `0.97`: `u-0.97`.articlerank,
  `0.98`: `u-0.98`.articlerank,
  `0.99`: `u-0.99`.articlerank,
  `1.0`: `u-1.0`.articlerank
} AS r
RETURN r


python3Packages.opensfm: refactor after upstreaming cmake patch

Description of changes

The patch that fixes eigen/ceres discovery in CMake has been merged upstream. Neither the previous nor the new revision have been released yet, so I'm just updating to the latest one and removing the redundant patch
Added changelog URL

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 163584 run on x86_64-linux 1

2 packages built:

python310Packages.opensfm
python39Packages.opensfm


The container host is on unsupported build version 18363.

As of this writing, the latest release of Windows 10 is version 1909 (18363).  I have a desktop NUC with Windows 10 Pro installed with that version.  Can I turn this device into an IoT Edge Device?
When I run the system checks outlined on this Azure documentation page, I get the following result:
PS C:\WINDOWS\system32> get-service vmcompute
Status   Name               DisplayName
------   ----               -----------
Running  vmcompute          Hyper-V Host Compute Service

PS C:\WINDOWS\system32> (Get-Process -Id $PID).StartInfo.EnvironmentVariables["PROCESSOR_ARCHITECTURE"]
AMD64
PS C:\WINDOWS\system32> . {Invoke-WebRequest -useb https://aka.ms/iotedge-win} | Invoke-Expression; `
>> Deploy-IoTEdge

ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     0.0        IoTEdge                             {Deploy-IoTEdge, Get-IoTEdgeLog, Initialize-IoTEdge, Insta...
The container host is on unsupported build version 18363.
Please use a container host running one of the following build versions for running Windows containers:
17763

The prerequisites for installation of the IoT Edge Security daemon are not met. Please fix all known issues before rerunning this script.

Does this mean that it will run ONLY on version 17763, and nothing later?  Any help would be greatly appreciated.
Regards,
Tam

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

ID: 4f41e023-819c-64a1-8bef-d050481a7ef7
Version Independent ID: 6f918de8-3e37-5f10-9b5b-aaf453869d2e
Content: Install Azure IoT Edge on Windows
Content Source: articles/iot-edge/how-to-install-iot-edge-windows.md
Service: iot-edge
GitHub Login: @kgremban
Microsoft Alias: kgremban

@Tam66662 Thank you for your feedback! We will review and provide an update as appropriate.

@Tam66662 Please see the below supported OS for installing Azure IoT Edge with Windows containers

I hope that answers your question. Do let me know if you have further queries.

@kgremban  Please add more clarity on the doc for supported OS and versions.

@AshokPeddakotla-MSFT just to be clear, you are saying that I can only create an IoT Edge device on ONLY version 17763 and not on any later versions of Windows 10?
Regards,
Tam

@Tam66662 Yes, as mentioned in the Tier1 OS list, it specifically calls out required the required build is 17763.
Do let us know if you have further questions.

@Tam66662 Please let me know if you have further questions.

We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

I have a question: why?  Additional question:  why not 18363?

@brendanrempel 17763 is the latest long-term support version of Windows. That's the version that the IoT Edge modules for Windows are based on, and the version of the host machine must match the version of the containers.
If you check out this page about Windows 10 versions, IoT Edge is using the Enterprise and IoT Enterprise LTSB/LTSC releases, not the semi-annual releases: https://docs.microsoft.com/en-us/windows/release-information/
Does that help?

@kgremban @AshokPeddakotla-MSFT
Imho this could be more clear in two aspects:
exact vs minimum requirement
In the text, it should be stated that the windows version is not a minimum but an exact requirement. This would remove a lot of ambiguity
Versions for Development and test
As far as I see, the statement

Development and test: For development and test scenarios, Azure IoT Edge with Windows containers can be installed on any version of Windows 10 or Windows Server 2019 that supports the containers feature.

is not entirely clear.

Newer versions of windows support the container feature, yet the scripts in the section "Option 1: Install and manually provision" do not work.
If this is intended, it should be stated that those instructions are limited to the OS version with production support.

Does this issue still exists ? I have Windows version 19044 and still unable to install IoT Edge. I am getting error that The container host is on unsupported build version 19044. Please use a container host running one of the following build versions for running Windows containers 17763.

This error still occurs even on latest LTSC, i.e Windows 10 IoT Enterprise 21H2

.


<IP_ADDRESS> (rxjava2)

Coverage increased (+1.4%) to 97.771% when pulling ca01953be6acf3bf1202484ba3b0554d3e35f943 on <IP_ADDRESS>-rxjava2 into 2a4bc177a8719211e5bcfa25a4a8895b0eb09f7e on rxjava2.


Review and update form parsing logic

src/Microsoft.AspNet.WebUtilities/ParsingHelpers.cs has at least one place where it calls char.IsWhiteSpace, but this allows many strange Unicode characters. Review this parsing code and update it to be more accurate.

Moving this to beta6

Is this something that @blowdart should care about?

Yea, I'd like to see the PR when it's done, although if you're narrowing to just space and tab I'm not so concerned.
It is worth reviewing where other things call IsWhiteSpace when parsing user input.

Moving out of V1.  We're open to PRs @blowdart :)

Yea, we all know you don't want me issuing PRs for anything other than Docs :+1:


TypeScript: VectorSource<Feature<Point>> can't be used as a source for VectorLayer

Describe the bug
I have a somewhat surprising typing issue where TypeScript will not let me use a VectorSource<Feature<Point>> as source for a VectorLayer, which seems surprising:
const source = new VectorSource({
  features: [new Feature(new Point([0, 0]))],
});
const layer= new VectorLayer({
  source,
});

This gives the error:
Type 'VectorSource<Feature<Point>>' is not assignable to type 'VectorSource<FeatureLike>'.
  Types of property 'setLoader' are incompatible.
    Type '(loader: FeatureLoader<Feature<Point>>) => void' is not assignable to type '(loader: FeatureLoader<FeatureLike>) => void'.
      Types of parameters 'loader' and 'loader' are incompatible.
        Types of parameters 'arg4' and 'arg4' are incompatible.
          Type '((arg0: Feature<Point>[]) => void) | undefined' is not assignable to type '((arg0: FeatureLike[]) => void) | undefined'.
            Type '(arg0: Feature<Point>[]) => void' is not assignable to type '(arg0: FeatureLike[]) => void'.
              Types of parameters 'arg0' and 'arg0' are incompatible.
                Type 'FeatureLike[]' is not assignable to type 'Feature<Point>[]'.
                  Type 'FeatureLike' is not assignable to type 'Feature<Point>'.
                    Type 'Feature<Geometry>' is not assignable to type 'Feature<Point>'.typescript(2322)

It looks similar to https://github.com/openlayers/openlayers/issues/15356, but that should have been fixed and I'm using 9.2.0 when I see this error.
To Reproduce
Steps to reproduce the behavior:

Visit the code sandbox I made: https://codesandbox.io/p/sandbox/ol-vectorlayer-typings-mkyp3m?file=%2Fsrc%2Findex.ts%3A12%2C1-18%2C1
A typing error is indicated on line 16 where source is provided to VectorLayer's contstructor, see error message above

This issue occurred in my app code which of course is a lot more complicated. It used to work, but after an upgrade (probably updating my TypeScript version), several errors like this one occurred. I tried upgrading to latest OpenLayers, but the issue persists.
Expected behavior
I expect to be able to use a VectorSource<Feature<Point>> as a source for VectorLayer without having to resort to type casting.

Apparently did a bad job of searching the issues (searched for "typescript"), I see that my issue seems to be a duplicate of #15830. Sorry


Character literal quirks

Character literals should only support one character in them except for escape sequences:
//allowed
let escaped = '\xFF'

// forbidden
let multiple_chars = 'FF'

The current logic for creating an Int from multiple characters is to concatenate the least significant Bytes into the target type Integer/Float.
Unicode characters Always seem to return 0.
The empty character literal '' also results in 0 although an empty character literal doesnt make sense and should be considered invalid syntax (imo).
See: https://playground.ponylang.org/?gist=3aedc58eadfca46c5c0133fa2af4a703
actor Main
  new create(env : Env) =>
    let wat_chars: Array[U64] = [as U64:
      ''       // 0
      'AAA'    // 0b010000010100000101000001
      '\n\0\0' // 10 * (2^16)
      '🎠'     // 0
    ]
    for wat_char in wat_chars.values() do
      env.out.print(wat_char.string())
    end

Does anybody have a valid use case for multi-character character literals?

Agreed.
Marking this as a bug, ready for work.

Multi-character literals are useful things (and also valid in C). For example, Lightwave 3D uses multi-character literals in their file format (http://www.sandbox.de/osg/lightwave.htm), allowing C to do:
switch(n)
{
  case 'PNTS':
    // stuff!
}

Or in Pony:
match n
| 'PNTS' => // stuff!
| 'SRFS' => // other stuff!

So the bug is that '🎠' should decode as 0x1F3A0.

In my last comment, I was thinking that we shouldn't allow multibyte character literals, but I'm okay with saying "it works like C" in this case, since @sylvanc says it's useful and he finds it to be expected.

Just to clarify (i am also currently writing a tutorial section on literals and want to understand the intended behavior):

When we say it works as in C do we also forbid empty literals ''? clang and gcc do so. I would vote for that.
The 🎠 is actually coded into F0 9F 8E A0 with UTF-8 and would result in 0xF09F8EA0. If we generate an Numeric directly from the encoded bytes, we get different results based on the file encoding. If we want to create unicode code points, we need to detect the actual encoding too, or just assume UTF-8. What is the preferred approach?


typescript transpiler errors

Is it anyhow possible to get rid of the typescript errors caused by Angular2Apollo?
ERROR in [default] /Users/.../app-angular2/node_modules/angular2-apollo/build/src/Angular2Apollo.d.ts:1:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/angular2-apollo/build/src/Angular2Apollo.d.ts:5:35
Cannot find module 'graphql'.

also apollo-client is throwing a lot of typescript transpilation errors:
ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/ApolloClient.d.ts:1:0
Cannot find type definition file for 'chai'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/actions.d.ts:1:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/actions.d.ts:3:0
Cannot find type definition file for 'chai'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/actions.d.ts:4:40
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/core/ObservableQuery.d.ts:1:0
Cannot find type definition file for 'chai'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/core/QueryManager.d.ts:1:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/core/QueryManager.d.ts:3:0
Cannot find type definition file for 'chai'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/core/QueryManager.d.ts:8:25
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/core/watchQueryOptions.d.ts:1:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/core/watchQueryOptions.d.ts:2:0
Cannot find type definition file for 'chai'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/core/watchQueryOptions.d.ts:4:45
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/extensions.d.ts:1:0
Cannot find type definition file for 'chai'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/mutationResults.d.ts:1:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/mutationResults.d.ts:2:0
Cannot find type definition file for 'chai'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/mutationResults.d.ts:4:40
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/readFromStore.d.ts:1:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/readFromStore.d.ts:2:0
Cannot find type definition file for 'chai'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/readFromStore.d.ts:3:25
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/scopeQuery.d.ts:1:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/scopeQuery.d.ts:3:29
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/storeUtils.d.ts:1:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/storeUtils.d.ts:2:0
Cannot find type definition file for 'chai'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/storeUtils.d.ts:3:64
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/writeToStore.d.ts:1:0
Cannot find type definition file for 'chai'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/writeToStore.d.ts:2:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/data/writeToStore.d.ts:4:39
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/errors/ApolloError.d.ts:2:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/errors/ApolloError.d.ts:3:29
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/fragments.d.ts:1:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/fragments.d.ts:2:45
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/mutations/store.d.ts:1:0
Cannot find type definition file for 'chai'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/mutations/store.d.ts:3:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/mutations/store.d.ts:5:29
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/queries/getFromAST.d.ts:1:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/queries/getFromAST.d.ts:2:66
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/queries/store.d.ts:1:0
Cannot find type definition file for 'chai'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/queries/store.d.ts:3:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/queries/store.d.ts:5:43
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/transport/batchedNetworkInterface.d.ts:2:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/transport/batchedNetworkInterface.d.ts:3:30
Cannot find module 'graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/transport/networkInterface.d.ts:1:0
Cannot find type definition file for 'typed-graphql'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/transport/networkInterface.d.ts:2:0
Cannot find type definition file for 'chai'.

ERROR in [default] /Users/.../app-angular2/node_modules/apollo-client/transport/networkInterface.d.ts:5:40
Cannot find module 'graphql'.

@Urigo wouldn't it make sense to include typed-graphql into angular2-apollo to avoid this errors?
Similar discussions are on apollo-client:

https://github.com/apollostack/apollo-client/issues/725
https://github.com/apollostack/apollo-client/issues/713

manually installing npm install --save @types/chai @types/isomorphic-fetch typed-graphql solves the problem.
However I'm still getting one error, which I don't know how to get rid off?
ERROR in [default] /Users/.../app-angular2/src/app/+home/home.component.ts:52:8
Cannot find name 'ApolloQueryObservable'.

However code still works in client

Are you using Typescript 2?

@types/chai @types/isomorphic-fetch typed-graphql are related to apollo-client
About ApolloQueryObservable, maybe you just forgot to import it from angular2-apollo?

Any update on "removing" the need for the @types/chai @types/isomorphic-fetch typed-graphql workaround?

@schickling Right now, TS adds @types/chai to the distributed files, it's not apollo specific, it's a known issue with TypeScript and it will be fixed with 2.1. I can't find an issue about it, will look for it later today.

I think that you can now $ npm install apollo-client angular2-apollo and that's it, no need to install any more packages with types independently. Does it work for you guys?


Optional Daily notes replacement request

Hi,
I've started out using Obligator, and I really like the features behind being able to pre-schedule things in the template using cron. I tend to need to get a broad overview of how things have gone, though, which I've been using the Daily notes in the Calendar plugin for. Would it be possible to have an option to have the Obligator plugin actually directly replace the notes created by the core Daily notes plugin, so that Calendar will recognize that the note exists?
Thank you!

I think it's possible, I'll think about if it makes sense for me to implement the change. It would require pulling all of the daily note settings out of Obligator and then hooking into the daily note button rather than the Obligator carrot.
Can you share some screenshots of how your calendar plugin works? Obligator right now processes the entire file except for what comes after the terminal heading. If the calendar is adding text to the file, I would have to specifically add support for that which I probably don't want to do (unless I can think of a general solution).

It's the Calendar plugin at https://github.com/liamcain/obsidian-calendar-plugin . Every day with a Daily note created shows a mark underneath it in the calendar sidebar, and it has the CTRL + hover preview of the Daily note, so you can reference something from a date on the calendar without having to leave the currently open tab. If there's an upcoming event for a day, you can create the note in advance (though I don't know how that would play out with Obligator). If there's a past date and there was no note created, you can make one by selecting the date in the calendar and following the prompt.
There is another calendar plugin, OZ Calendar, https://github.com/ozntel/oz-calendar , which can be used to see any note that has been created depending on its YAML or file name, but it doesn't allow the preview or week numbering that Calendar does. And the Gregorian preset for the Fantasy Calendar, https://github.com/fantasycalendar/obsidian-fantasy-calendar , which can have any note added to an event and events are tracked on the calendar. It does allow week numbering, but doesn't allow hover previews, though a day can be opened below the calendar in the sidebar.
All of which is to say, if it's not possible, I'll manage with a different calendar than Calendar, but I would really appreciate at least having the option of using Calendar.

I'm coming into this a bit late, but the Calendar plugin is working for me with Obligator notes.
It looks like that plugin, unless daily Periodic Notes are enabled, uses the core Daily Notes settings even if it's not enabled, and if your Obligator note filenames match the format defined there, it seems to pick them up just fine.
Creating a new file through its interface, however, appears to work through its own method using the configuration it has pulled, which is to say that it will not use Obligator's features, and neither would hooking into the core Daily Notes plugin or Periodic Notes for that matter, from what I can tell with my amateur code-reading abilities.
It looks like you could hook into the plugin's creation method too, if you wanted to, but even putting aside the extra workload I'm not sure you really intend to handle forward/backdated notes in the first place.

@Lyssabet Can you try to see if your use case is covered by matching the daily notes date format with the Obligator date format as mentioned above?

I had already tried that before I commented the first time. I think it's just not working correctly on my computer, though. Obligator timed to-dos (the *** formatted ones) from the template setup are correctly appearing on new Obligator notes, but to-dos from Obligator notes on previous days aren't rolling over to the new day.

I had already tried that before I commented the first time. I think it's just not working correctly on my computer, though. Obligator timed to-dos (the *** formatted ones) from the template setup are correctly appearing on new Obligator notes, but to-dos from Obligator notes on previous days aren't rolling over to the new day.

Hm, can you verify that you're on the latest version of Obligator? 3.20.1?
If so, can you show me how to reproduce that? That shouldn't be happening.

It is indeed 3.20.1, and to reproduce it: I create an Obligator note one day, and I start a new Obligator note the next day (by selecting the Obligator icon in the left toolbar). The new Obligator note contains everything from the preset template that it should, and none of the new but incomplete to-dos from the previous day's note. They're all new ones a couple of headings before the end heading that's set in the options. I also tried uninstalling and reinstalling it to see if that would make a difference, and tried it in a different vault. No joy.

I'm unable to recreate your issue, can you take a look at this and tell me what you're doing differently?

I will close until you respond.


Dockerfile problem on upgrading

"Error updating Hass.io Access Point: COPY failed: file not found in build context or excluded by .dockerignore: stat run.sh: file does not exist"
Looks like an issue with with the Dockerfile?  If it's any help, it's on a Pi3b and upgrading to the latest v2.0.

I no longer offer addon support from this account, now the addons I develop will be uploaded in this repository.
https://github.com/deadbeef3137/home-assistant-addons


i just find 1 card after using the tool and checking the tag

for example, i have 3 card 'a','b','c', and each one has their own duplicate card.
first I used the tool, and when i checked the tag in the browser, I only found 1 card was taged, such as 'a'.
yes, there is no 'b' and 'c' card which should be taged.
And after i delete the card 'a' and remove the 'needverify' tag, I use the tool again and I got card 'b' with the 'needverify' tag and 'needremove' tag.
I am not a native speaker and I hope you can understand what I describe above.
please tell me what to do, thank you very much!

did you choose the duplicate field? can you export your sample deck into an apkg file and shared it with me? thank you


fix(KCheckbox): wrap label slot in span

Summary
Wrap the whole KCheckbox slot in a span tag, rather than just the label prop
Changes made:

Wraps the whole KCheckbox slot in a span tag, rather than just the label prop. https://github.com/Kong/kongponents/pull/296 works when the label prop is used, but if the default slot is used instead, the span is overridden. Wrapping the slot will ensure it's not overridden, and will still work if the label prop is used.

PR Checklist

[x] Does not introduce dependencies
[x] Functional: all changes do not break existing APIs and if so, bump major version.
[x] Tests pass: check the output of yarn test packages/
[x] Naming: the files and the method and prop variables use the same naming conventions as other Kongponents
[x] Framework style: abides by the essential rules in Vue's style guide
[x] Cleanliness: does not have formatting issues, unused code (e.g., console.logs), or leftover comments
[x] Docs: includes a technically accurate README, uses JSDOC where appropriate

@kaiarrowood I've added the requested example to the docs:

nonblocking: While you're in this component, can we update the TOC to put this in the right place alphabetically? This has been driving me nuts for a long time.

Code lives in the .vupress config file.

Otherwise this looks awesome!

nonblocking: While you're in this component, can we update the TOC to put this in the right place alphabetically? This has been driving me nuts for a long time.

Definitely, fixed the ordering of Icon too.
Screenshots:
Before

After


We should clarify the difference in versioning between packaged & unpackaged

re: https://github.com/microsoft/terminal/issues/15739

Download asset https://github.com/microsoft/terminal/releases/download/v1.17.11461.0/Microsoft.WindowsTerminal_1.17.11461.0_x64.zip
Run and Open About dialog

Expected Behavior
Displayed version should be 1.17.11461.0
Actual Behavior
Displayed version is 1.17.230526001

Let's just add a note that it's expected that the version numbers are different

Documented in Releases.


Move everything to OZ extensibility standard

Currently a lot of our code does not support the OZ standard. Would be nice to move to 100% OZ standard.

Duplicate of #251, closing


appsody build of java-microprofile hangs

Describe the bug
I'm running appsody build of the java-microprofile stack and the command does not complete. It hangs on the following command...
Docker] Downloading from central: https://repo.maven.apache.org/maven2/io/openliberty/openliberty-runtime/<IP_ADDRESS>/openliberty-runtime-<IP_ADDRESS>.zip
I've waited over an hour so far and it is still hung
See attached log for full output:
java-microprofile-hang.log
To Reproduce
Steps to reproduce the behavior:

mkdir java-microprofile
cd java-microprofile
appsody init java-microprofile
appsody build java-microprofile

Expected behavior
A clear and concise description of what you expected to happen.
Actual behaviour
What is the actual behaviour.
Environment Details (please complete the following information):

OS: [e.g. iOS] mac

If applicable please specify:

CLI version: 0.4.9
Stack you are using (including the version): java-microprofile

Is this recreatable?
It would be interesting to run curl https://repo.maven.apache.org/maven2/io/openliberty/openliberty-runtime/<IP_ADDRESS>/openliberty-runtime-<IP_ADDRESS>.zip while this is happening to rule out transient network issues.

I tried a few things just now...

works: curl -O https://repo.maven.apache.org/maven2/io/openliberty/openliberty-runtime/<IP_ADDRESS>/openliberty-runtime-<IP_ADDRESS>.zip
works: appsody build -> docker shows 19 steps
hangs: appsody stack validate -> docker shows 32 steps during appsody build
restarted docker then tried appsody stack validate again but it still hangs

I think the root cause is likely that we need to do the mvn -B  (batch).. otherwise the download progress gets messed up.     I recreated, made this change, and it went away.

Thanks @scottkurz, this has been giving a few of us some headache since Friday.
FYI: @neeraj-laad @groeges @tnixa I just tried this also and the problem was fixed.


Copy to clipboard tooltip is not aligned / scroll always visible

Description

Copy to Clipboard tooltip is not align properly
Scroll always visible.

Expected Behavior

Copy to Clipboard tooltip should be aligned properly.
Keep the scroll as auto like if the content exceeds then only it will be visible else remains hidden in the modal.

Screenshots
https://user-images.githubusercontent.com/44670961/171209794-8cd25020-c7d6-4914-be83-5a4160933c03.mp4
Enviroment:

OS:  Ubuntu
Browser: Chrome, firefox

[Optional] To Reproduce

Go to Meshery Catalog
Click on any card which will open a modal
Hover over Copy Url button.
See error

Contributor Resources
The meshery.io website uses Jekyll and GitHub Pages. Site content is found under the master branch.

See the Contributing to Meshery.io Website section of the readme.md and other contributing instructions, too.
See Meshery site designs in this Figma designfile. Fill-in the Layer5 Community Member Form and join the Layer5 Community Slack for access.

Does this look good ?
@chinmaym07 @theBeginner86 @leecalcote

Removed unused white space aligned copy to clipboard tool-tip @leecalcote @theBeginner86 @chinmaym07
https://user-images.githubusercontent.com/55309324/173629228-a75560d0-1d83-4315-bb0e-7ba3fa73bd2e.mp4

Hi @Rohith-Raju .
Great work. Just a small tweak here.
It will be much better to keep the tooltip at the bottom rather than placing side by side .

@chinmaym07 any particular reason? I aligned it to the side because there was a lot of unused space, as of now the height spans automatically, if we decide to add it to the bottom it will just take up more space  😄. What do you say?

I also think that it's better if we try to fit the content rather than telling the user to scroll for more info.

It wont be possible to have that much of information inside a modal especially in mobile without a scroll, we can hide the scrollbar but we can't remove it's functionality.
Currently I dont see a scrollbar in mobile view.
Browser: Chrome

@warunicorn19   yes fixing on that

@Rohith-Raju i think that you have this one covered with n your upcoming PR…. @asubedy ?

Yes @leecalcote  this will be covered once @Rohith-Raju PR gets merged, just one final image issue is left.


Improve SonarQube addon configuration

The improvements to the SonarQube addon are described in these 3 tickets:

https://jira.sonarsource.com/browse/MMF-349
https://jira.sonarsource.com/browse/MMF-383
https://jira.sonarsource.com/browse/MMF-384

In addition to the rspec tests, we have integration tests for it that simulate most of the use cases:
https://github.com/SonarSource/travis-build-test

@dbmeneses This has been deployed to staging.

@dbmeneses Have you had a chance to test this?

@BanzaiMan It's on my side, and I'm just back from holidays. I'll do it next week!

@bellingard OK. I'm off to Japan next week, and I might be slow in responding. It might take a while to coordinate, but we should be able to find some time to test this.

This has been deployed again to .org staging.

Hi @dbmeneses, I've started testing the feature and I've got some issues with key encryption.
Let's take the following repo as an example: https://github.com/FabOrga/multi-language-project. Here's the scenario:

I've encrypted a SonarQube token following https://docs.travis-ci.com/user/encryption-keys/#Usage (I encrypted it in the correct GitHub repository)
I've specified the encrypted value in the .travis.yml file (see line #7) like this is expected to be supported by the latest developments of the add-on
I output the $SONARQUBE_SCANNER_PARAMS environment variable that is supposed to contain the decrypted value of the token (see line #13)
But when the staging instance executes the job, we can see that the token is not decrypted (see line #96 in the logs)

Any idea why this does not work?

@BanzaiMan do secure variables get replaced by the decrypted values in the parsed YAML when using the staging?
As @bellingard reported, it doesn't seem to be the case. I also get the raw encrypted values during the build.

Sorry for the delay. I've been traveling the last couple of weeks. I'll take a look at this PR next week!

@dbmeneses Encrypting for staging requires a different API endpoint from the one used for production. Using a wrong API endpoint renders the encrypted value invalid and the build won't see the decrypted value.
To encrypt, try:
travis encrypt -e https://api-staging.travis-ci.org -r FabOrga/multi-language-project

@BanzaiMan It appears that this p/r is not included in the staging anymore.
I've rebased this p/r on master and changed the sonarqube scanner cli version, which fixes a problem found during testing with the staged addon (https://jira.sonarsource.com/browse/TRAVIS-4). Could you please deploy it again in staging so that we can do the final testing?

@dbmeneses Sorry about that. I've deployed it again. Thanks.

@BanzaiMan @bellingard I've rebased on master again and fixed the spec tests. I've tried secure variables, they are working: https://staging.travis-ci.org/dbmeneses/sonarqube-addon-test

@BanzaiMan Looks like you've not deployed the latest version that includes modifications of this PR. The following line in the logs shows that the currently deployed version is the same as the production one: https://staging.travis-ci.org/FabTemp/multi-language-project/builds/513386#L150

Sorry about that. Staging can be in an unpredictable state. I'm waiting to deploy it now, pending Heroku's issue (https://twitter.com/herokustatus/status/779302180020822016).

OK. It's been deployed again.

@BanzaiMan Looks like the new deployment did not work correctly. The version of the SonarQube Scanner that is downloaded is "2.7-build314" (see https://staging.travis-ci.org/FabTemp/multi-language-multi-module-project/builds/513499#L149) whereas version "2.8" is specified in @dbmeneses 's latest commits (see https://github.com/travis-ci/travis-build/pull/831/files#diff-1ef94773b86865fbc2213f4860ea73f0R10).
So looks like the Staging is still in an unpredictable state. :-/

Sorry about the delay. Could you test this again? Thanks.

@BanzaiMan , the addon deployed in staging has some problems that we don't understand.
It seems that it's not succeeding downloading the scanner-cli 2.8. This could be explained if the deployed addon didn't have the latest fix before 95913a8, which fixed the usage of the maven central repository.
Could you please confirm that the addon deployed in staging is the commit 95913a8, and re-deploy if necessay?
Also, are there any restrictions to download external files in staging?
The P/R has currently changes to init.rb that should be dropped (committed by mistake), but I won't do changes until we figure out why testing is failing.
Thanks!

@dbmeneses There must have been some merge conflict I did not resolve correctly. I re-merged the test branch and deployed it. Could you try again?
Thank you.

@BanzaiMan Looks like the Add-on is now working as expected, I'll be able to keep on doing my validation tomorrow. Thanks!

Is this ready?

No, I will do a last fix today. I will let you know when it's ready.

@BanzaiMan Staging is again back to a non up-to-date state regarding this PR. :-/ For instance, I relaunched a job that used to work 2 days ago and now I can see that the Add-on is back to the "prod" version (see https://staging.travis-ci.org/FabTemp/multi-language-project/builds/513548#L150).
I'm almost done with the validation - so hopefully we can get the PR on the staging back so that I can finish and the PR can finally be merged!

Hello. Sorry for the delay. I've deployed this to staging again.

@BanzaiMan The addon is not running on external pull requests. Reading https://github.com/travis-ci/travis-ci/issues/2135, it seems that the sonarqube addon needs to be on a whitelist so that it runs on external p/r. Is that correct?

FYI @BanzaiMan, when the SonarQube addon is in the whitelist, then I will have to only do a latest test and we will be done!

Since SonarQube (generally) needs secrets to function, I do not think it is a good idea to allow it in PR builds from forks. See https://github.com/travis-ci/travis-ci/issues/1946, as well as https://docs.travis-ci.com/user/jwt and https://github.com/travis-ci/travis-ci/issues/6569.

Is further testing required?

@BanzaiMan Not executing the add-on in PR builds from forks changes a couple of things, so if you don't allow this, we'll have to make some new changes unfortunately. :-/
Still, before we try to change something, I'd just like to clarify what the add-on is supposed to do on external PR: it won't pass any secret at all but only 1 parameter (i.e. no sensitive information) that disables the SonarQube analysis to not break the builds of external PR. You can check that in the code of the add-on (I think this is pretty straightforward for you to validate this). Why we're doing this? Just to keep the YML file as simple and not require end-user to check wether or not they should execute the SonarQube analysis.
With this clarification on how the add-on is working, can you reconsider @dbmeneses's request to activate it on external PR?
If it's still not clear, we can plan a Skype if you want to discuss this further. We are extremely cautious about security concerns (we operate our own cloud service too!) so I'm pretty sure we can show you that the add-on is safe.

Sorry for the delay. The code to remove that one Maven build phase looks good. I have deployed this to https://staging.travis-ci.org/.

@BanzaiMan The add-on is indeed deployed on https://staging.travis-ci.org, but still not activated on external pull requests.
You can see it here: https://staging.travis-ci.org/FabTemp/multi-language-project/builds/513650

There's nothing in the log that shows the activation of the Add-on
The Maven "sonar:sonar" build phase breaks the analysis whereas we would expect to just be silently skipped

@bellingard Please try again.

@BanzaiMan I've changed the P/R to fix a problem we found with unsecured pull requests. Could you please deploy it once again in staging so that we can do the final validation?

Sorry for the delay. We will get to this in an hour or so.

Deployed to staging.

Thanks @BanzaiMan. The addon is not doing what it should on unsecured pull requests and we don't know why.
Could you please check if the addon is still in the whitelist and that the latest commit (46eeab3) is deployed?

I think the staging scheduler may not include what production does (with respect to PRs from forks). Is there anything else to address?

https://github.com/travis-ci/travis-scheduler/pull/51 has been deployed to .org staging. Sonarqube addon should now work on external PRs. (Only to be skipped by the addon itself.)

@BanzaiMan I confirm that it's working! 👍  So my validation is done on this PR. :-D
I will now work on the update of the documentation so that we can go to production ASAP.

We are going to deploy this on Monday.

This has been deployed to production.

Thanks @BanzaiMan :-), I can now use it live!

Hey - it seems that the code has been deployed but the Travis-CI documentation hasn't been updated to match.  Took some wild guessing to figure out what was going wrong when I tried to follow the docs.

@bbockelm I'm currently working on the documentation. New version is supposed to be backward compatible with previous one, so not sure that the issue you faced is due to documentation.

Hit two issues(-ish):

Was trying to add this to an existing project as a PR from an external repo.  Dunno if it worked in the old version, but it definitely isn't allowed in the new one (probably a tripwire that deserves a mention in the docs).
I figured (1) out from reading the code and then put the branch in the primary repo, then hit the fact that, even though I had sonar.branch set right in sonar-project.properties, I didn't have it set in the .travis.yml.

I now got SonarQube's scanner working, but am currently trying to figure out a permission-denied issue when it is uploading results (https://travis-ci.org/singularityware/singularity/builds/178443079#L1846).  I'm guessing something is wrong with my token, but it's not entirely clear.  So close!

Ah - and if you start with a fresh project foo:bar and analyze a branch named baz, then you get the permission denied:
https://travis-ci.org/singularityware/singularity/builds/178447624#L2260
(but in SonarQube it auto-creates a project named foo:bar:baz.
However, if you manually set the project key to foo:bar:baz in the sonar properties file, it will upload to the correct project name and succeed:
https://travis-ci.org/singularityware/singularity/builds/178447831#L2323
So, I'm not entirely sure the branches feature is working correctly: I have to change sonar-project.properties for each active branch by hand (either that or it's just an issue for fresh projects?).

@bbockelm Please come on the SonarQube Google group to talk about this - I will answer there. This PR is not the place for that kind of discussion.


Hi

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version:
OS Version:

Steps to Reproduce:

Y3y4u

@ivannggnnavi Please close the issues if you just want to annoy people


Restoring SMS and Call logs on GN ICS

After clicking restore button the items are restored successfully but the following issue come up:

In SMS: I don't see the actual time stamp of the message received instead it shows the current time stamp of the message restored . The Nexus one and Nexus S are perfect they are running android 2.3.6 - time stamp is perfect whereas my galaxy nexus is running 4.0.1? Can you let me know if there is any work around for the above problem?

Call logs: The call logs are not getting restored from Gmail.

All issues above are same even after couple of tries.
Can you please help me out with the above two issues?
Awaiting your response!
Thanks!

I found this problem aswell, times in the overview are set to the update time, if you click through to the conversation the time & date is correct

Screengrabs edited for privacy.
Messaging list http://i.imgur.com/KZ5xt.png
Conversation view http://i.imgur.com/VxznJ.png

Two days later and the fields are correct, only have to assume a device restart fixed it. Does that work for you, vijaykd?

Nope. You are lucky...It didn't work for. Actually I tried the restart thrice or four times before posting the issue. :(

http://www.tbray.org/ongoing/When/201x/2012/02/29/Undocumentedness#p-3 & http://stackoverflow.com/questions/6903885/android-programatically-inserted-sms-have-incorrect-timestamp-in-messaging-apps/6911015#6911015 gives an answer!


pca_variance_ratio does not return axis

https://github.com/theislab/scanpy/blob/2a7fb7cdf56ff44ef6338c7dba3b84b4b32d216c/scanpy/plotting/_tools/__init__.py#L120-L129
Is it meant that the pca_variance_ratio does not return the generated axis? There is no return in the function definition, in addition to it not handling the returned fig object from ranking(...)

I believe it is, pinging @Koncopd who probably knows more about it. If this is desired behaviour, we could close this.

Hi @HypoChloremic
would something like this be useful for your question? https://scanpy.readthedocs.io/en/stable/api/scanpy.pl.pca_overview.html#scanpy.pl.pca_overview
https://scanpy.readthedocs.io/en/stable/api/scanpy.pl.pca_variance_ratio.html#scanpy.pl.pca_variance_ratio
?

will close this due to inactivity


Can't submit, servers busy

Hello,
I have not been able to submit any any answers since last night,
Submission timed out while communicating with our servers. This may infrequently happen if our servers are extremly busy. Please try again. If issues persist you can check status.codewars.com to see if server issues are being investigated.

Just a heads up.

I'm currently investigating a couple of major issues, although code execution is running fine for me. Is there any other information you may be able to provide?

I just sat back down and when I refreshed, logged out, and logged back in about 50% of my submissions work. I just need to refresh once or twice. Perhaps its local to my machine.


[Pick 2.0](inverted index) fix build index error status when batch_next (#33532)

Proposed changes
Issue Number: close #xxx
Pick From #33532
Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Fix cuDNN preloading

Currently some of features in cuDNN v8 is not working when installed via wheels.
import ctypes
import cupy
import cupy.cuda.cudnn as libcudnn
import cupy.cudnn
x = cupy.arange(12, dtype=cupy.float32).reshape(3, 4)

# This is implemented in cudnn_ops_infer:
cupy.cudnn.activation_forward(x, libcudnn.CUDNN_ACTIVATION_RELU)
# This is implemented in cudnn_cnn_train (error)
cupy.cudnn.create_fused_ops_plan(0)  # CUDNN_FUSED_SCALE_BIAS_ACTIVATION_CONV_BNSTATS

The above example fails because cudnn_cnn_train depends on cudnn_ops_infer, cudnn_ops_train, and cudnn_cnn_infer, but cudnn_ops_train and cudnn_cnn_infer are not loaded and could not be discovered automatically by cuDNN.
This issue only occurs when chain-loading dependencies (i.e., loading a split module from another split module).
libcudnn.so.8 has a $ORIGIN in RUNPATH, so libcudnn.so.8 can find split modules in the same directory and load them.
~/.cupy/cuda_lib/11.2/cudnn/8.2.0/lib64 % for FILE in libcudnn*8.2.0; do echo $FILE; readelf -d $FILE | grep RUNPATH; done
libcudnn_adv_infer.so.8.2.0
libcudnn_adv_train.so.8.2.0
libcudnn_cnn_infer.so.8.2.0
libcudnn_cnn_train.so.8.2.0
libcudnn_ops_infer.so.8.2.0
libcudnn_ops_train.so.8.2.0
libcudnn.so.8.2.0
 0x000000000000001d (RUNPATH)            Library runpath: [$ORIGIN]

This PR fixes the preload system to load all split modules.
This changes the wheel metadata structure but does not affect conda-forge distributions.
xref: #5103
TODO:

[x] verify this works on Windows

I confirmed this worked on Windows.
pfnCI, test this please.

Jenkins CI test (for commit b656c40e49f56df1be4f0e60899614aaf53466cb, target branch master) succeeded!


pin PyYAML to 5.3.1 in source setup.py

This fixes #183 by pinning PyYAML to version 5.3.1 in setup.py.
I understand contributions are not being accepted currently, so I will use my fork until this gets merged, but wanted to get the core team's attention to the bug and it's fix.
Contributing to Customizations for AWS Control Tower (CfCT).
Thank you for your interest in contributing to Customizations for AWS Control Tower (CfCT).
At this time, we are not accepting contributions. If contributions are accepted in the future, Customizations for AWS Control Tower (CfCT) is released under the Apache license and any code submitted will be released under that license.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@awseric thank you for bringing this up.
I will create a backlog to look into this.

Hi @awseric , thank you again for bringing this to our attention. Latest patch v.2.7.1 (release notes) included changes to pin the PyYAML in setup.py to 5.3.1.
I am going to resolve this issue, please reopen if there are follow up questions.


Fork bomb with restricted memory instead of processes count exhausts file descriptors

sandbox test leading to this result:
/*
description: Fork bombs can be prevented by limiting available memory
script: |
    expect(run(limits=Metrics(memory="100 MB")))
*/

#include <stddef.h>
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>

int main() {
    for (int i = 0; ; i++) {
        switch (fork()) {
        case 0:
            for (;;) {
                pause();
            }
        case -1:
            fprintf(stderr, "Failed to fork at process %d\n", i);
            return -1;
        }
    }
    fprintf(stderr, "Did not fail to fork\n");
    return 1;
}

My system:
$ uname -a
Linux reimu 6.8.7-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Wed, 17 Apr 2024 15:20:00 +0000 x86_64 GNU/Linux

Reproduced on dev (37cc370a Update miniserde dep to make code more rust-2024 compatible), but probably can be reproduced even on current master


Sig bindings

#190

@gabizon103 any luck debugging the failing test?

@rachitnigam Haven't had much of a chance yet, but that's what I'm going to do today!

@gabizon103 it is occurring to me that a possible problem can be that we're not defining the parameters in the with section use a subcomponent:
comp foo[#W](in: [G, G+1] #B) -> () with {
  #B = #W + 2
} { ... }
comp bar(...) {
  f := new foo[10]; // This should define both #W and #B
}

If the #B parameter is not defined within bar, then the port f.in is going to use an unknown parameter causing problems. In general, all parameters in the with section must be visible to the parent component.

If the #B parameter is not defined within bar, then the port f.in is going to use an unknown parameter causing problems. In general, all parameters in the with section must be visible to the parent component.

Yeah I've come to this conclusion also. I am trying to figure out how to do this - astconv is pretty dense and I haven't looked at it much before this

I've mucked up the PR because of this merge. If you're not working on it in the next hour or two, I can take a shot and you can try getting #263 PR merged in the meantime?

Sure, I'll work on #263!

Subsumed by #294.


Can't import the named export 'Header' from non EcmaScript module

Hi, I am working on a reactjs project written in javascript and I am new to this package.
After I installed the package and used it, the error said
<EMAIL_ADDRESS>Can't import the named export 'Header' from non EcmaScript module (only default export is available)
"@cabify/prom-react": "0.2.1"

Hi!
I've just checked this is working correctly in most of our applications. I've also checked in a fresh CRA installation.
The export this stack mentioned belongs to @shopify/network, can you double check which version you have installed of this dependency? because in the latest version it seems to be exported..
This may be also related to how your bundler does resolve dependencies.

Can you provide further information on what bundler configuration are you using for your app?
Webpack, rollup, nextjs...

The solution was an update to React 16.14 instead of 16.13.

Maybe we should update React peerDependency to >=16.14. Thanks for the response, closing this issue.


Use a simpler border and background color strategy

Sometimes I notice that the borders aren't always showing up for me on some columns.
This made me look into the logic, and I noticed that it was more confusing than it needed to be.
The BorderColor was used as the BackgroundColor.
This PR changes it so that the background color of the rows is indeed the BackgroundColor, and the border color is indeed the BorderColor.
In order to accomplish this, I unfortunately needed to change the data type of the BorderThickness to a double, to match the data type used on Border's StrokeThickness.  Allowing this to work with Thickness would be a good change, but I don't see how to do it. Feel free to edit this.
One level of nesting with the ContentView was removed, but then another level with the Border was added, which nets out to about even.
This all makes much more sense to me.

Can you resolve merge conflicts before I review?

Done.

Oh, I see you made some changes to the header. I will need to make one more fix now.

Now I'm ready for review.

I'm not convinced with the implementation, yet. On windows device borders looks weird + double size.

I will give it another go. This approach puts a box inside of each cell. The caveat here is that the ColumnSpacing property as currently implemented will end up putting blank space in the middle between each cell.
But we set the spacing to 0 by default, then there should be no space.
Also looks like the propertyChanged delegate on the BorderThicknessProperty needs to be removed.


[RN 72] iOS compat: test project

Hi all. Thank you guys for your hard working on detox. Do you have any timelines for creating test project ?

Hi @PetroPavlenko,
Detox will support rn 72 very soon (a few days / weeks)


Nested event loop crash

Potentially-linked issue in DPF: https://github.com/DISTRHO/DPF/issues/299
It looks like when LV2 UIs call puglUpdate from the idle callback on macOS, they can occasionally process events which cause the UI to be destroyed. This in turn causes the host to crash, because the next part of puglUpdate tries to use resources which have been freed during sendEvent.
The issue linked above contains some steps to reproduce the issue.
I believe that it is an error to call NSApplication sendEvent from within a plugin. It places a very large burden on the host to assume that any event could be processed inside an LV2 idle callback. Hosts which weren't designed with LV2 in mind may have to undergo significant rewrites in order to work around this issue, if they can at all. It seems much more straightforward to provide both "standalone" and "plugin" versions of puglUpdate, so that users of pugl can avoid manually processing events in contexts which already have an event loop in place.
Would it be possible to modify pugl such that sendEvent can be bypassed in projects with an existing event loop?

pugl knows during runtime if the program is standalone or a plugin, so it can make a decision based on that.
A similar issue was pointed out in https://github.com/lv2/pugl/pull/55 where plugins are calling a global function typically reserved for hosts/standalones.

The first part sounds like a bug that just needs to be fixed regardless, but I don't know about the second part.  The sendEvent is there to "put back" events that pugl is not going to process because the event mask is not precise enough to filter out exactly the events that are handled specially.
The intent is not to "process" events there, just the opposite: sending the event to the application is the way pugl "puts back" the event, for lack of a proper way to do that (that I can find anyway).  But MacOS is very unpredictable internally in general, IIRC nextEventMatchingMask itself dispatches events sometimes, and other system things do as well, more or less whenever.  I am not sure this is possible to entirely avoid, even if pugl doesn't call sendEvent.
It's also not clear to me why this is problematic anyway.  A more concrete example would help.  But anyway, in short...

Would it be possible to modify pugl such that sendEvent can be bypassed in projects with an existing event loop?

I have no idea.
Maybe it's possible to specify just NSApplicationDefined as a mask to handle the client events, but this would only reduce the scope of the problem (though by quite a bit), or specify false for dequeue, but my experience with this method is that it's very cryptic and temperamental and usually doesn't do what you expect, so it will probably take some tinkering.
Have at it, but client events still need to work, so I don't think it's as simple as just stubbing the whole thing out.

I've pushed a potential fix to #57. It seems to work here, but it'd be great if you could try it out and check that I haven't missed any edge cases.
I'm not sure what you mean about a concrete example - https://github.com/DISTRHO/DPF/issues/299 has an example of a real-world crash in REAPER caused by calling sendEvent from puglUpdate inside an LV2 UI's idle callback. It's reasonably easy to reproduce with the latest DPF demo projects.

Returning to this one, I still don't quite get it.  Obviously the quitting thing is an issue, but Pugl needs to dispatch events here somehow.
Maybe, at least in module mode, it should be working with the event queues of the views instead of the application?  At a high level, that's what puglUpdate is supposed to do: update all the Pugl things, so if on MacOS sending events to the application makes them be processed immediately (which wasn't the intent there), then that shouldn't be happening?
Client events still need to work somehow though.  I don't really understand how the event loop stuff works that well, but it doesn't seem to really fit the programming model to me.  That said, MacOS in general doesn't fit it so well, so... whatever?
If it's really just the quit thing, I imagine that specific case can be suppressed, but I'm not enough of a MacOS expert to really know what the proper solution here is.  Are there established vaguely similar projects (that set up and run sub-views on MacOS) that we can steal some inspiration from?

Fixed in 28d75f7


Running async procedure in custom validator

Hi,
I'm using jsonschema for a while... Going deeper in schema validation I figured out that I can define my own validation procedures.(Thanks Radek Lat for his nice article)
So one of the feature I'd like to use is the custom validators. However (in my use case), it would be useful only if I can run asynchronous task.  Furthermore I'm running validation from a coroutine.
So here is my question: How can I execute async calls in a custom validator ? Does the generator can help me ?

Think I mentioned via PM that this is a long term goal (to better support async use cases, more so for ref resolution than validation but sure there too). Closing this for now but of course happy to review any proposed changes.

I think I finally found an elegant way to do mixed async/sync validation. Indeed it needs some changes but few ! Here is my proposal...
The idea would be to declare a new type of ValidationError to yield during the validation (for instance AsyncValidation) . This new "pseudo validation error" may go through the generator validation tree until a Validator#async_iter_errors method where we may check if it isinstance(error, AsyncValidation). If yes, we shall call asynchronously error.async_validate which will populate a buffer of errors later yielded by the original validator method. Pay attention that it will NOT work out of the box with "conditional checks" (like anyOf, ..) but I'm pretty sure that there is not a lot of changes to do to handle these cases.
If AsyncValidation is not supported (for instance if we "only" call iter_errors) it will generate a validation error.
Quiet confusing ? Ok, here is an example:
import asyncio
import functools
from jsonschema import ValidationError, Draft7Validator
from jsonschema.validators import extend

class AsyncValidation(ValidationError):

    def __init__(self, callback, value, *args, message='async validation not supported', **kwargs):
        super(AsyncValidation, self).__init__(message, *args, **kwargs)
        self.callback = callback
        self.value = value
        self.errors = []

    async def async_validate(self):
        async for error in self.callback(self.validator, self.value, self.instance, self.schema):
            self.errors.append(error)

class AsyncValidator():

    def __init__(self, draft_src, validators, schema):
        validator = extend(draft_src, validators)(schema)
        self.__class__ = type(validator.__class__.__name__, (self.__class__, validator.__class__), {})
        self.__dict__ = validator.__dict__

    async def async_iter_errors(self, body):
        for error in self.iter_errors(body):
            if isinstance(error, AsyncValidation):
                await error.async_validate()
            else:
                yield error

def wrap_async_validator(coroutine):
    def co_validator(coroutine, validator, value, instance, schema):
        async_validation = AsyncValidation(coroutine, value=value, validator=validator, instance=instance, schema=schema)
        yield async_validation
        for error in async_validation.errors:
            yield error

    return functools.partial(co_validator, coroutine)

async def custom_validation(validator, value, instance, schema):
    await asyncio.sleep(5)
    yield ValidationError('hmmm, something goes wrong here...')

async def async_validation_example():
    body = {'x': '...'}
    schema = {'type': 'object', 'properties': {'x': {'type': 'string', 'custom': True}}}
    validator = AsyncValidator(
        Draft7Validator,
        {'custom': wrap_async_validator(custom_validation)},
        schema,
    )

    async for error in validator.async_iter_errors(body):
        print(str(error))

I would enjoy to have your feedback about this idea ! ;-)
Kind regards,


feat: MLmodel Graphql Query

This PR includes changes in datahub-graphql-core to include GraphQL Query functionality changes for MLModel Entity.
Includes fixes in GMS based on Tests for MLModel
Also organized mappers into packages by entity.
Checklist

[ X] The PR conforms to DataHub's Contributing Guideline (particularly Commit Message Format)
[ ] Links to related issues (if applicable)
[ X] Tests for the changes have been added/updated (if applicable)
[ X] Docs related to the changes have been added/updated (if applicable)

@jjoyce0510 : could you take a look at this?

Thanks for taking time to review @jjoyce0510.
Let me know what do you think.


Choice buttons with multiple languages don't show up

I fixed this in my local branch but my client is using the main web build which rejected my pull request for this fix.
Basically, values_button tries to get a string from an object and fails so no buttons show up.

Hello! i Saw your changes, they have two problems
You make changes at "runtime", but not in the main "tuesday.js" file (main file for runtime), so i can't see what was changed.
You are also making overly drastic changes that could damage other users projects.
How are you trying to use localization and values_button function?

Basically, we have 3 languages and the choices buttons are not showing up. This blocks the client from playing the game.
When debugging, I noted the matchAll function tries to run on an object of a locale string (like en:"") instead of the actual string itself. This produces an error and the buttons don't render. My fix sanitizes the language lookup as done elsewhere in the codebase. I wasn't aware of the runtime vs main runtime differences. That's a small problem to fix.
I totally understand the need to protect other projects - my CSV separator change for example handles this with a new setting value (we need commas) and the default behavior preserves current functionality. Localization is crucial for this project.

The problem with buttons is very simple to solve. the default 'width size' = 0 is done to make the button fit the text on it. to prevent the button from disappearing, set it to a fixed size.

For CSV export I added settings for Separated and Delimiter

I think I figured out what the problem is. It wasn't the choice button but the global interface button - if the global interface button is purely iconic, that is it has no text, this causes button addition failure so the choice buttons do not get made.

Also there may be another issue related to this where additional languages are not added if the text button is purely iconic with no string. This causes localization for other languages to fail. It's easy to fix by directly editing the JSON. Thanks for your assistance earlier.

unfortunately the error could not be repeated. Can you send a JSON snippet with this problem, or describe how I can replicate this problem?

I'll make a new issue with the repro steps.


Use as new tab page?

Is there a way to use this as a new tab page
in other words, if i run :tabnew the dashboard will show up unless a file is specified

something like
vim.api.nvim_create_autocmd('TabEnter', {
    command ='Dashboard'
})

something like
vim.api.nvim_create_autocmd('TabEnter', {
    command ='Dashboard'
})

Doesn't work - causes many errors
Error executing vim.schedule lua callback: ...packer/start/dashboard-nvim/lua/dashboard/theme/doom.lua:112: Cursor pos
ition outside buffer
stack traceback:
        [C]: in function 'nvim_win_set_cursor'
        ...packer/start/dashboard-nvim/lua/dashboard/theme/doom.lua:112: in function 'generate_center'
        ...packer/start/dashboard-nvim/lua/dashboard/theme/doom.lua:178: in function <...packer/start/dashboard-nvim/l
ua/dashboard/theme/doom.lua:176>
        .../pack/packer/start/dashboard-nvim/lua/dashboard/init.lua:214: in function 'load_theme'
        .../pack/packer/start/dashboard-nvim/lua/dashboard/init.lua:270: in function 'callback'
        .../pack/packer/start/dashboard-nvim/lua/dashboard/init.lua:192: in function ''
        vim/_editor.lua: in function <vim/_editor.lua:0>

TabEnter is also a bad event to use as it will run whenver i enter a tab, empty or not old or new. So I tried TabNewEntered.
This works fine if :tabnew is given no args, but if a file is opened using tabnew, id like it to not launch dashboard.
In other words i need a way to make this
vim.api.nvim_create_autocmd('TabNewEntered', { command = 'Dashboard'})

only run if the new tab is blank


[Intel MKL] Fixing a build issue

@jktomer Can we merge this PR?

It's in the process of being merged.

Already cloned to a internal change list to fix. @tatianashp  please update the status once that CL is submitted.


Using smappee APIv2 instead of APIv1

Smappee just release v2 of their API https://smappee.atlassian.net/wiki/spaces/DEVAPI/pages/526581817/Get+Sensor+Consumption#GetSensorConsumption-Version2(v2)
by using this version of the API the temperature unit is returned as degrees Celsius instead of centi degrees Celsius which is more human readable which resolves #30

I already changed it in my https://www.home-assistant.io/components/smappee/ setup and I do get all the information including power consumption etc..

Ok, I'll take your word for it ;-)
Thanks for your contribution!
The change was published as version 0.2.16


Add OTLP exporter constructors for convenience

Codecov Report
Attention: 13 lines in your changes are missing coverage. Please review.

Comparison is base (2a06abd) 93.74% compared to head (24ce07b) 93.24%.
Report is 1 commits behind head on main.

Files
Patch %
Lines

clue/exporters.go
75.00%
8 Missing and 4 partials :warning:

clue/config.go
66.66%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #353      +/-   ##
==========================================
- Coverage   93.74%   93.24%   -0.50%
==========================================
  Files          31       32       +1
  Lines        1774     1822      +48
==========================================
+ Hits         1663     1699      +36
- Misses         92      100       +8
- Partials       19       23       +4

Flag
Coverage Δ

micro
93.24% <74.50%> (-0.50%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


The trait bound impl std::future::Future<Output = std::result::Result<std::vec::Veclib::prisma::user::Data, std::string::String>>: specta::function::result::FunctionResult<_> is not satisfied

I'm getting this error while trying to use Prisma Rust Client with tauri-specta.
error[E0277]: the trait bound `impl std::future::Future<Output = std::result::Result<std::vec::Vec<lib::prisma::user::Data>, std::string::String>>: specta::function::result::FunctionResult<_>` is not satisfied
   --> src/main.rs:10:1
    |
10  | #[specta::specta]
    | ^^^^^^^^^^^^^^^^^ the trait `specta::function::result::FunctionResult<_>` is not implemented for `impl std::future::Future<Output = std::result::Result<std::vec::Vec<lib::prisma::user::Data>, std::string::String>>`
...
34  |             tauri_specta::ts::builder().commands(tauri_specta::collect_commands![get_users]);
    |                                                  ------------------------------------------ in this macro invocation
    |
    = help: the following other types implement trait `specta::function::Function<TMarker>`:
              fn() -> TResult
              fn(T10) -> TResult
              fn(T2, T3, T4, T5, T6, T7, T8, T9, T10) -> TResult
              fn(T3, T4, T5, T6, T7, T8, T9, T10) -> TResult
              fn(T4, T5, T6, T7, T8, T9, T10) -> TResult
              fn(T5, T6, T7, T8, T9, T10) -> TResult
              fn(T6, T7, T8, T9, T10) -> TResult
              fn(T7, T8, T9, T10) -> TResult
            and 3 others
    = note: required for `fn(State<'_, Arc<PrismaClient>>) -> impl Future<Output = Result<Vec<Data>, String>>` to implement `specta::function::Function<_>`
    = note: the full type name has been written to '/home/niraj/Documents/rust/tauri/local-first-tauri/src-tauri/target/debug/deps/app-b89adf94dac85c84.long-type-5392976783934926372.txt'
note: required by a bound in `specta::internal::get_fn_datatype`
   --> /home/niraj/.cargo/registry/src/index.crates.io-6f17d22bba15001f/specta-2.0.0-rc.12/src/internal.rs:232:40
    |
232 |     pub fn get_fn_datatype<TMarker, T: Function<TMarker>>(
    |                                        ^^^^^^^^^^^^^^^^^ required by this bound in `get_fn_datatype`
    = note: this error originates in the macro `__specta__fn__get_users` which comes from the expansion of the macro `tauri_specta::collect_commands` (in Nightly builds, run with -Z macro-backtrace for more info)

Steps to reproduce:

Clone the repo
Run pnpm tauri:dev to start Rust server and pnpm next:dev Next.js server

I used the code from this starter example.

This issue is due to your Specta versions not matching up. This error is pretty horrible I will look into improving that in a future release.
Prisma Client Rust 0.6.11 is using Specta 1.0.2 while your using Tauri Specta v2 which depends on Specta v2.
You will likely need to fork Prisma Client Rust and upgrade the Specta version to match or downgrade Tauri Specta to v1.

I seem to have the same issue with the following command:
#[tauri::command]
#[specta::specta]
pub async fn register_event<R: Runtime>(app: AppHandle<R>, event: String) -> Result<()> {
    app.grpc().register_event(event).await
}

I pinned tauri, specta and tauri-specta to those versions in my workspace:
tauri = { version = "=2.0.0-beta.22" }
specta = { version = "=2.0.0-rc.12" }
tauri-specta = { version = "=2.0.0-rc.11" }

And use those features in my plugin package:
tauri = { workspace = true, features = ["specta"] }
specta = { workspace = true, features = ["function"] }
tauri-specta = { workspace = true, features = ["typescript"] }

But I have this error when compiling:
❯ cargo check
    Checking tauri-plugin-grpc v0.0.0 (/home/florian/Repos/admiral/crates/tauri-plugin-grpc)
error[E0277]: the trait bound `impl Future<Output = std::result::Result<(), error::Error>>: function::result::FunctionResult<_>` is not sati
   --> crates/tauri-plugin-grpc/src/commands.rs:23:1
    |
23  | #[specta::specta]
    | ^^^^^^^^^^^^^^^^^ the trait `function::result::FunctionResult<_>` is not implemented for `impl Future<Output = std::result::Result<(),
    |
   ::: crates/tauri-plugin-grpc/src/lib.rs:42:23
    |
42  |             .commands(tauri_specta::collect_commands![commands::register_event,]); // <- Each of your commands
    |                       ---------------------------------------------------------- in this macro invocation
    |
    = help: the following other types implement trait `Function<TMarker>`:
              fn() -> TResult
              fn(T1, T2, T3, T4, T5, T6, T7, T8, T9, T10) -> TResult
              fn(T2, T3, T4, T5, T6, T7, T8, T9, T10) -> TResult
              fn(T3, T4, T5, T6, T7, T8, T9, T10) -> TResult
              fn(T4, T5, T6, T7, T8, T9, T10) -> TResult
              fn(T5, T6, T7, T8, T9, T10) -> TResult
              fn(T6, T7, T8, T9, T10) -> TResult
              fn(T7, T8, T9, T10) -> TResult
            and 3 others
    = note: required for `fn(AppHandle<_>, std::string::String) -> impl Future<Output = std::result::Result<(), error::Error>>` to implement `Function<_>`
note: required by a bound in `get_fn_datatype`
   --> /home/florian/.cargo/registry/src/index.crates.io-6f17d22bba15001f/specta-2.0.0-rc.12/src/internal.rs:232:40
    |
232 |     pub fn get_fn_datatype<TMarker, T: Function<TMarker>>(
    |                                        ^^^^^^^^^^^^^^^^^ required by this bound in `get_fn_datatype`
    = note: this error originates in the macro `commands::__specta__fn__register_event` which comes from the expansion of the macro `tauri_specta::collect_commands` (in Nightly builds, run with -Z macro-backtrace for more info)

As I'm not using any other packages depending on specta, I don't think it comes from an issue with some versions of specta not matching. Do you have any idea about where this issue comes from ?

@FlorianStasse Does error::Error implement specta::Type? tauri-specta v2 requires everything you return from a command to implement it.

@Brendonovich Thanks for the insight, I forgot about this type. I added the required `#[derive(specta::Type)]" to my type.
But it now seems that the generic <R: Runtime> in my commands is triggering a new error, and I can't find an example online of someone using tauri-specta with this kind of generic:
error[E0283]: type annotations needed
  --> crates/tauri-plugin-grpc/src/commands.rs:23:1
   |
23 |   #[specta::specta]
   |   ^^^^^^^^^^^^^^^^^ cannot infer type
   |
  ::: crates/tauri-plugin-grpc/src/lib.rs:41:60
   |
44 |           let builder = tauri_specta::ts::builder().commands(tauri_specta::collect_commands![
   |  ____________________________________________________________-
45 | |             commands::register_event,
46 | |         ]); // <- Each of your commands
   | |_________- in this macro invocation
   |
   = note: cannot satisfy `_: tauri::Runtime`
note: required by a bound in `register_event`
  --> crates/tauri-plugin-grpc/src/commands.rs:24:32
   |
24 | pub async fn register_event<R: Runtime>(app: AppHandle<R>, event: String) -> Result<()> {
   |                                ^^^^^^^ required by this bound in `register_event`
   = note: this error originates in the macro `commands::__specta__fn__register_event` which comes from the expansion of the macro `tauri_specta::collect_commands` (in Nightly builds, run with -Z macro-backtrace for more info)

@FlorianStasse See the custom plugin example for where that generic comes from. It should be inferred via invoke_handler.

@Brendonovich Thanks for your quick replies, I cloned the repository and went to the plugin example to implement a function with the same signature as mine:
// Uses the app handle for something
#[tauri::command]
#[specta::specta]
async fn use_app_handle<R: tauri::Runtime>(_app: tauri::AppHandle<R>) {}

// We recommend re-using the builder via a macro rather than function as the builder's
// generics can be tricky to deal with
macro_rules! specta_builder {
    () => {
        ts::builder()
            .commands(collect_commands![add_numbers, use_app_handle])
            .events(collect_events![RandomNumber])
    };
}

But running cargo check still shows an error:
error[E0283]: type annotations needed
  --> examples/custom-plugin/plugin/src/lib.rs:19:1
   |
19 | #[specta::specta]
   | ^^^^^^^^^^^^^^^^^ cannot infer type
...
36 |         specta_builder!().build_plugin_utils(PLUGIN_NAME).unwrap();
   |         ----------------- in this macro invocation
   |
   = note: cannot satisfy `_: tauri::Runtime`
note: required by a bound in `use_app_handle`
  --> examples/custom-plugin/plugin/src/lib.rs:20:28
   |
20 | async fn use_app_handle<R: tauri::Runtime>(_app: tauri::AppHandle<R>) {}
   |                            ^^^^^^^^^^^^^^ required by this bound in `use_app_handle`
   = note: this error originates in the macro `__specta__fn__use_app_handle` which comes from the expansion of the macro `specta_builder` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0283`.
error: could not compile `tauri-plugin-specta-example` (lib) due to 1 previous error

If the code snippet from above is not enough, I can fork the repository and push the modified plugin example that triggers this error.

Oh, the command has a runtime generic. Didn't notice that. You'll need to hardcode the generic like this.

Thanks for you help, I was able to fix everything !

Thanks for this @Brendonovich!
Could we add the requirement for this derive in the docs/examples?
#[derive(Error, Serialize, Deserialize, Debug, Type)]

I was missing the "Type" which isn't in the main example

Would be happy for a PR to add a section showing how to add custom errors using thiserror.
It would be important to call out that thiserror is not required and all you need is Serialize + Type on the error type.


Add CI runs on mirrord releases

Make so new releases of mirrord will trigger e2e tests

e2e tests will now be tackled on releases in mirrord, refer https://github.com/metalbear-co/mirrord/pull/1915


Create MedianSortedArrays.cpp

Pull Request Template
Description
Median of two Sorted Arrays
If we cut the sorted array to two halves of EQUAL LENGTHS, then
median is the AVERAGE OF Max(lower_half) and Min(upper_half), i.e. the
two numbers immediately next to the cut
Put check marks:
Have you made changes in README file ?

[x] Added problem & solution under correct topic.
[x] Specified Space & Time complexity.
[x] Specified difficulty level, tag & Note(if any).

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

[ ] Test A
[ ] Test B

Make sure all below guidelines are followed else PR will get Reject:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code so that it is easy to understand
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] Any dependent changes have been merged and published in downstream modules

@GouravRusiya30  Please review this

@vedant-z
What is the time and space complexity of your code ?

TIME COMPLEXITY : O(log(min(M,N)))
SPACE COMPLEXITY : O(1)

@GouravRusiya30 Is there anymore changes left to be made?

@GouravRusiya30 If the required changes are made then please merge this PR


Match Trigger at end of message not working

Describe the bug

While the box to match command triggers at the end of messages is checked, nothing happens when typing the trigger at the end of the message.
To reproduce

Check the "match trigger at end of message box in the commands tab  in settings.
Type out a message with a command trigger at the end of it, the command does not trigger.
Screenshots

Chatterino version

Chatterino 2.2.3-beta2 (commit 6499b7c12)
Operating system

Additional information

No wonder it doesn't work, there are no usages of the setting. Duplicates #2308

No wonder it doesn't work, there are no usages of the setting. Duplicates #2308

Duplicate of #2308

Duplicate of #2308


Locstar/KAS-600 (LS-8015-ZW) lock failed to complete interview

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?
NO, my problem is NOT within Z-Wave JS UI
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
What causes the bug? Try to include or re-interview KAS-600 door lock.
What do you observe? The device gets stuck in NodeInfo. The last message from the driver log before communication stops is
Error during node interview: Node #11 does not support the command TimeOffsetGet! (ZW0302)

Some items do appear in Z-Wave JS UI, but there are a lot of undefined labels, and things that previously worked like battery level no longer appear.

What did you expect to happen? Interview to complete and device be available in HomeAssistant
Steps to reproduce the behavior:

Go to the control panel in Z-Wave JS UI
Click on the node associated with the KAS-600 lock (Node 11 in my case)
Click on the Advanced button
Click on the Re-interview Node button
Selecting the Reset security classes checkbox makes no difference to the outcome
Click OK
The Re-interview process begin, but the node stays stuck in NodeInfo.

Device information
Manufacturer: KAS
Model name: KAS-600 (LS-8015-ZW)
Node ID in your network: 11
How are you using node-zwave-js?

[X] zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[x] HomeAssistant zwave_js integration  2023.1.4
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[ ] Other (please describe)

Which branches or versions?
Z-Wave JS version: 10.10.0
Z-Wave JS UI version: <IP_ADDRESS>d9d59c
Did you change anything?
yes (please describe)
If yes, what did you change?
I excluded the node from the network and re-added it.
Did this work before?
Yes (please describe)
If yes, where did it work?
This device previously worked with OpenHAB and HomeAssistant prior to the change to Z-Wave JS. It has also worked with previous versions of Z-Wave JS. I couldn't tell you which version I included the lock originally, though.
Attach Driver Logfile
zwavejs_2023-02-20.log

Looks like we only ever tested Schedule Entry Lock CC on devices supporting V2/V3. Fix on the way