Could not initialize an instance of the type 'UIKit.UIImage'

I'm trying to add TEditor to my Xamarin application (not using Xamarin.Forms) and when calling the
await CrossTEditor.Current.ShowTEditor it's giving me this error:
System.Exception: Could not initialize an instance of the type 'UIKit.UIImage': the native 'initWithContentsOfFile:' method returned nil.
It is possible to ignore this condition by setting MonoTouch.ObjCRuntime.Class.ThrowOnInitFailure to false.
  at Foundation.NSObject.InitializeHandle (IntPtr handle, System.String initSelector) [0x00094] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/Foundation/NSObject2.cs:453
  at UIKit.UIImage..ctor (System.String filename) [0x0002e] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/build/ios/native/UIKit/UIImage.g.cs:94
  at PopColorPicker.iOS.PopColorPickerViewController.SetViewControllers () [0x00000] in C:\Users\Michael\Documents\TEditor\PopColorPicker.iOS.Shared\PopColorPickerViewController.cs:112
  at PopColorPicker.iOS.PopColorPickerViewController.ViewDidLoad () [0x0007d] in C:\Users\Michael\Documents\TEditor\PopColorPicker.iOS.Shared\PopColorPickerViewController.cs:80
  at (wrapper managed-to-native) ObjCRuntime.Messaging:IntPtr_objc_msgSendSuper (intptr,intptr)
  at UIKit.UITabBarController..ctor () [0x0003b] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/build/ios/native/UIKit/UITabBarController.g.cs:53
  at PopColorPicker.iOS.PopColorPickerViewController..ctor () [0x00000] in C:\Users\Michael\Documents\TEditor\PopColorPicker.iOS.Shared\PopColorPickerViewController.cs:19
  at TEditor.TEditorViewController.AddColorPickerControl () [0x00000] in C:\Users\Michael\Documents\TEditor\iOS\Controls\TEditorViewController.cs:111
  at TEditor.TEditorViewController.ViewDidLoad () [0x00018] in C:\Users\Michael\Documents\TEditor\iOS\Controls\TEditorViewController.cs:245
  at (wrapper managed-to-native) UIKit.UIApplication:UIApplicationMain (int,string[],intptr,intptr)
  at UIKit.UIApplication.Main (System.String[] args, IntPtr principal, IntPtr delegate) [0x00005] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/UIKit/UIApplication.cs:77
  at UIKit.UIApplication.Main (System.String[] args, System.String principalClassName, System.String delegateClassName) [0x00038] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/UIKit/UIApplication.cs:61
  at TiendaNubeIOS.Application.Main (System.String[] args) [0x00008] in /Users/juane/mobile-apps/TIendaNubeIOS/Main.cs:13
2017-05-31 17:57:22.024 TiendaNubeIOS[31327:4189271] Unhandled managed exception:
Could not initialize an instance of the type 'UIKit.UIImage': the native 'initWithContentsOfFile:' method returned nil.
It is possible to ignore this condition by setting MonoTouch.ObjCRuntime.Class.ThrowOnInitFailure to false. (System.Exception)
  at Foundation.NSObject.InitializeHandle (IntPtr handle, System.String initSelector) [0x00094] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/Foundation/NSObject2.cs:453
  at UIKit.UIImage..ctor (System.String filename) [0x0002e] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/build/ios/native/UIKit/UIImage.g.cs:94
  at PopColorPicker.iOS.PopColorPickerViewController.SetViewControllers () [0x00000] in C:\Users\Michael\Documents\TEditor\PopColorPicker.iOS.Shared\PopColorPickerViewController.cs:112
  at PopColorPicker.iOS.PopColorPickerViewController.ViewDidLoad () [0x0007d] in C:\Users\Michael\Documents\TEditor\PopColorPicker.iOS.Shared\PopColorPickerViewController.cs:80
  at (wrapper managed-to-native) ObjCRuntime.Messaging:IntPtr_objc_msgSendSuper (intptr,intptr)
  at UIKit.UITabBarController..ctor () [0x0003b] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/build/ios/native/UIKit/UITabBarController.g.cs:53
  at PopColorPicker.iOS.PopColorPickerViewController..ctor () [0x00000] in C:\Users\Michael\Documents\TEditor\PopColorPicker.iOS.Shared\PopColorPickerViewController.cs:19
  at TEditor.TEditorViewController.AddColorPickerControl () [0x00000] in C:\Users\Michael\Documents\TEditor\iOS\Controls\TEditorViewController.cs:111
  at TEditor.TEditorViewController.ViewDidLoad () [0x00018] in C:\Users\Michael\Documents\TEditor\iOS\Controls\TEditorViewController.cs:245
  at (wrapper managed-to-native) UIKit.UIApplication:UIApplicationMain (int,string[],intptr,intptr)
  at UIKit.UIApplication.Main (System.String[] args, IntPtr principal, IntPtr delegate) [0x00005] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/UIKit/UIApplication.cs:77
  at UIKit.UIApplication.Main (System.String[] args, System.String principalClassName, System.String delegateClassName) [0x00038] in /Users/builder/data/lanes/3234/d8bedd03/source/maccore/src/UIKit/UIApplication.cs:61
  at TiendaNubeIOS.Application.Main (System.String[] args) [0x00008] in /Users/juane/mobile-apps/TIendaNubeIOS/Main.cs:13

It seems that<EMAIL_ADDRESS>cannot be found. Do you know any workaround?
Thanks!

Can you try to rebuild the project? It's wired, that images also in the source code.


[QUESTION] What if LiteDB direct and shared modes are used together?

What is the problem of using LiteDB and using direct and shared modes at the same time?
Let's say there are processes called A and B. A connected a DB file in the direct mode. Then B connects the DB file to the shared mode. It was expected that B wouldn't be able to connect the DB file, but it could be connected unexpectedly and data could be modified. In order not to cause a race condition problem, does the A processor need to connect in shared mode as well?

Don't use mixed mode in code. If you intend to access the db from multiple processes.. use shared mode only. If you intend to have a single process access the database (but perhaps use multiple threads to access), you gain the best performance from direct mode. If you are unsure, the easiest is to use shared as the mutex locking will handle all access cases.


Fix vet warning in devicemapper

Warning is:
pkg/devicemapper/devmapper_wrapper.go:234: possible misuse of unsafe.Pointer

Idea is to replace uintptr in whole call chain with unsafe.Pointer and then in GetStatus in pkg/devicemapper/devmapper.go replace task.GetNextTarget(0) with  task.GetNextTarget(unsafe.Pointer(nil)).

#dibs

@NinjaTrappeur What status here?

I made the modifications in the code, since it is my first contribution and I am a Go rookie, I am reading more about docker's testing environment. I'll tell you more in 1 or 2 hours :)

@NinjaTrappeur when you do a PR, can you please add fixes or closes keyword to it? Thanks!


ZEP0001 status clarification, not "Final"?

#260 and #261 marked ZEP0001 as Accepted.

ZEP0000 suggests that the status should now be Final.

Once a Specification ZEP has been Accepted, the second PR which was submitted in the zarr-specs repository must be merged. After that, the status will be changed to Final.

However, #263 and #264 seem to be approaching ZEP0001 as if it were Provisionally Accepted which is a state which is not supposed to apply to "core" specifications.
What kind of changes are permitted to ZEP0001 when it is Accepted but not yet Final? When does ZEP0001 become Final?  Are (minor) breaking changes are permitted in the Final state?

@MSanKeys963 , ping. Could you clarify the current state.

Hi @mkitti. 👋🏻

Could you clarify the current state

Yes!
As discussed in the last ZEP meeting (rolling notes here), the ZEP0001 is currently Accepted by the ZIC and ZSC.
Please check #227 for the votes.
The ZIC are currently in the implementation phase, and we're in a grace period (which will end soon) to accept minor changes to the specification.
Once we're sure that the implementors propose no additional changes, we will do a quick round of voting, and after that ZEP0001 will be Final.
I hope that helps. Please let me know if there's anything else.

Closing this now.


Docker based platform extension support documentation

Dependent on;

adop-platform-management#22

Hi Rob,
Thanks for adding documentation for the new platform extension type!
Can you move these changes to the master branch under the site folder please? The gh-pages branch is published to from this folder.
Thanks,
Nick


React Native Slow Performance

Hi,
Thanks a lot for the React Native compatibility package its been working great for me! One thing I have noticed however is the slow performance when changing the text inputs.
Console logging onQueryChange shows that at times values I type come out 500ms to upwards of 3s later. For now I solved the issue by disabling my submit button with a setTimeout until onQueryChange hasn't changed in over 2 seconds.

Could you share your component code? Input updates shouldn't take that long, so there may be some opportunities for optimization.

Apologies for this, appears to just be slow on the simulator for whatever reason but much faster when I built to my device. Memo-izing the custom controls (Native Base) I made also seems to have helped quite a bit
ie.
export const controlElements: Partial<Controls> = {
  addGroupAction: memo(memo(ActionElement)),
  addRuleAction: memo(ActionElement),
  cloneGroupAction: memo(ActionElement),
  cloneRuleAction: memo(ActionElement),
  lockRuleAction: memo(ActionElement),
  lockGroupAction: memo(ActionElement),
  removeGroupAction: memo(ActionElement),
  removeRuleAction: memo(ActionElement),
  notToggle: memo(NotToggle),
  combinatorSelector: memo(ValueSelector),
  fieldSelector: memo(ValueSelector),
  operatorSelector: memo(ValueSelector),
  valueSourceSelector: memo(ValueSelector),
  valueEditor: memo(ValueEditor)
};


services/horizon: Liquidity pools derived from order book stream does not match liquidity pool from ingestion

What version are you using?
2.13.0 (issue occurs in 2.12.1 too)
What did you do?
I noticed that:
liquidity pools derived from order book stream does not match liquidity pool from ingestion

error occurs around a few times per hour on average in production pubnet cluster. It's also happening in a cluster running the previous 2.12.1 version. It's not a big problem because in case of such thing the graph is rebuilt.
May be connected: https://github.com/stellar/go/issues/4195

Improved logging in https://github.com/stellar/go/pull/4211 because it's currently impossible to read it.


[DownloadBuildArtifactsV0] Add download post-check

Task name:

DownloadBuildArtifactsV0

Description:
This PR implements an additional check of the downloaded artifact' items.
Changes:

Added call of the checkArtifactConsistency function to related Promises in the following functions: main, downloadZip

Additions:

Introduced new task optional parameter - Check downloaded files (Can be found in advanced settings)
Added checkArtifactConsistency function for validation results of artifact download
Added isItemCorrupted function for checking information from download ticket of artifact item
Added check of the file size in local storage

Others:

Bumped up task minor version to 181
Added loc strings for messages

UI Demonstration

Documentation changes required: Yes
Added unit tests: No
Attached related issue:

#13250

Checklist:

[x] Task version was bumped - please check instruction how to do it
[x] Checked that applied changes work as expected

Can anyone give an ETA as to when this might be merged?

Can anyone give an ETA as to when this might be merged?

Hi @MattGal, I'm currently double-checking all changes to prevent any possible regressions for this task, so I believe we will merge these changes within 2-3 workdays.

Test run of the pipeline with these changes (with Check downloaded files option enabled): https://dev.azure.com/v-alsmo/ArtifactsTest/_build/results?buildId=768&view=results

@alexander-smolyakov any update on when this might get merged?

@alexander-smolyakov any update on when this might get merged?

I see that the only code path that uses execWithRetries is a windows specific code path and when isZipDownloadDisabledBool==true. So this fix will only cause our issues to manifest on a different way by showing an error that the downloaded artifact is corrupt.
Can you add retry for the other code paths so that this task is more resilient?

I see that the only code path that uses execWithRetries is a windows specific code path and when isZipDownloadDisabledBool==true. So this fix will only cause our issues to manifest on a different way by showing an error that the downloaded artifact is corrupt.
Can you add retry for the other code paths so that this task is more resilient?

Could you add some tests - since there are a lot of changed related to refactoring?

Could you add some tests - since there are a lot of changed related to refactoring?

Checked with lightweight artifact (38 b) - I think it make sense to test it with more heavy artifacts also (at least 200 mb)

Checked with lightweight artifact (38 b) - I think it make sense to test it with more heavy artifacts also (at least 200 mb)

@alexander-smolyakov any updates on when this can get merged and deployed? It's hitting pretty often in our CI.

@alexander-smolyakov any updates on when this can get merged and deployed? It's hitting pretty often in our CI.

Checked with lightweight artifact (38 b) - I think it make sense to test it with more heavy artifacts also (at least 200 mb)

@anatolybolshakov I tested my changes on heavyweight artifacts items (The summary size of Artifact is 24399 mb).
The build artifact that I used for the test: https://dev.azure.com/v-alsmo/ArtifactsTest/_build/results?buildId=929&view=artifacts&pathAsName=false&type=publishedArtifacts
Run of the test pipeline that I used for e2e testing: https://dev.azure.com/v-alsmo/ArtifactsTest/_build/results?buildId=939&view=results

Checked with lightweight artifact (38 b) - I think it make sense to test it with more heavy artifacts also (at least 200 mb)

@anatolybolshakov I tested my changes on heavyweight artifacts items (The summary size of Artifact is 24399 mb).
The build artifact that I used for the test: https://dev.azure.com/v-alsmo/ArtifactsTest/_build/results?buildId=929&view=artifacts&pathAsName=false&type=publishedArtifacts
Run of the test pipeline that I used for e2e testing: https://dev.azure.com/v-alsmo/ArtifactsTest/_build/results?buildId=939&view=results

@MattGal @hoyosjs currently we on the testing stage for this PR, we plan to ship this fix with the release for the 183rd sprint. Usually, it requires two or three weeks to deploy the release to all Azure DevOps users. This means that the fix will be available for all users around the 5th of March.

@MattGal @hoyosjs currently we on the testing stage for this PR, we plan to ship this fix with the release for the 183rd sprint. Usually, it requires two or three weeks to deploy the release to all Azure DevOps users. This means that the fix will be available for all users around the 5th of March.

Could it make sense to expose retry count as input also?

Could it make sense to expose retry count as input also?

Could it make sense to expose retry count as input also (in advanced inputs group)?

Good point, I will add an additional input for it.
Thanks!

Could it make sense to expose retry count as input also (in advanced inputs group)?

Good point, I will add an additional input for it.
Thanks!

Btw tested it with artifact from the same pipeline - LGTM for me 👍

Btw tested it with artifact from the same pipeline - LGTM for me 👍

The UI "parallelizationLimit" input seem not used ? Same in previous version 0.178. Only the variable "release.artifact.download.parallellimit" works.

The UI "parallelizationLimit" input seem not used ? Same in previous version 0.178. Only the variable "release.artifact.download.parallellimit" works.

Hey @SamuelGuine, we fixed the issue with parallelizationLimit input (Link to related PR). This fix will be available in two or three weeks for all Azure DevOps users.


Wrong DLL version

So I have installed this extension, started visual studio and opened an RDL file that is working in CE, but when I try to preview the report I get an error that it is looking for Microsoft.Crm.Reporting.RdlHelper.dll v9.0 but the latest installer only has version 8.

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

ID: 92de73f2-5e22-ff0f-39ec-7a9fc4850e16
Version Independent ID: acf8abcc-3fff-4159-c78a-206d6833e19b
Content: Install Dynamics 365 Report Authoring Extension
Content Source: ce/analytics/install-dynamics-365-report-authoring-extension.md
Product: crm-2016
GitHub Login: @Mattp123

Thank you for your feedback. Unfortunately, we're unable to handle Support requests for the product here. To contact Support, consider one of the options described here: https://docs.microsoft.com/dynamics365/get-started/support/
Closing this issue.


ZTF Alert FP - deduplication logic, flux to mag space

This PR:

add the deduplication logic folks decided to use, i.e. when we have overlapping FP datapoints, replace existing ones only if the new alert is brighter (which means, the position should be more accurate).
add mag space information when the SNR is above 0. That way, filters that need the mag can trust it or not trust it by enforcing their own SNR cuts.
ensure that only brand new ZTF objects start accumulating forced photometry. That way, we either don't have FP, or we have the full history for that object. Otherwise, filters relying on FP could yield unpredictable results.
add tests for the deduplication

TODO: add tests for the mag space data maybe?

Thanks a lot for the review @mcoughlin (and sorry for the stupid english mistakes, you make one of them and then copilot propagates that error as much as possible yikes).


update select Table

table : affiliate blockchain account is not updated
Type is not displayed : it it the type in the json : TezVoucher_1 in our case
Replace in the table "Discount" by "Reward"
Need the landing page link (to copy in clipboard) in the Table (modifié)
Home button should go back to screen to chose and not to logout

the title of the col are the good one, see Pseudo/phone


Create tron glow lines shader

Looks like this:

For here:

Like this? http://thebookofshaders.com/edit.php?log=160714133247

@sensescape I add a glow line style ready to be use ; ) here https://github.com/tangrams/tron/commit/7f400d5f48dafccf622eb1b4aa65c441f3df1e41#diff-00a5904308f10281f68148761eb5ed90L21
Try it out first here (see that you need to change the inlay for add on the blend mode):
https://mapzen.com/tangram/play/?scene=https%3A%2F%2Fgist.githubusercontent.com%2Fanonymous%2F34214efaf9448fd7ac38fefb47837867%2Fraw%2F856e46dedaf2922550f9dbcc40a4107ebf8a92f4%2Fscene.yaml#17/40.70359/-74.01217

yay!


Featured Request: Block UI

Provide the option to block the rest of the UI when a notification has an action to prevent the user from clicking somewhere else why an action needs to be taken.
Right now this can be accomplished by adding a css class to the toasted container, and then styling that class to block everything else, but a simple boolean in options would be nice.

sorry, closing as inactive


Fix Performance Issue for filtering on varchar columns in MS_SQL database

Why make this change?

Closes #1973

Slow response of DAB when filtering on varchar columns in MS_SQL compared to other DBs.
Same query in mssql taking around ~1sec, compared to <50ms in other DBs for large number of rows, eg. 20 million
This was happening because the query generated by DAB when runs on Sql Server for varchar columns, it automatically assumes the filter value of type nvarchar, due to which it does implicit cast leading to slowness.
To fix this we needed to identify if the filter is for varchar column, we explitily specify it to be varchar for faster response.

What is this change?

We are modifying the DbCommand and adding extra information that is sent to SqlClient.

We introduced a new property called SqlDbType, By Default for String DbType, SqlDbType was considered as nvarchar. now we are updating this property to the correct sql type.

This allows db to directly execute the command without type casting due to type mismatch.

Carved out the code which creates DbCommand in QueryExecuter, and added an override method in MsSqlQueryExecuter. here we set the property SqlDbType for the Parameters.

Link to Discussion which talks about this highlighting the issue : https://github.com/Azure/data-api-builder/discussions/1964#discussioncomment-8121313
Added a new property SqlDbType in Column class, currently we used to have only DotNet DbType which doesn't differenciate between varchar and Nvarchar. So, adding this SqlDbType gave us the freedom to modify query based on the sql db type.

How was this tested?

Since, this is a performance issue and only a new column got introduced. The main aim here was to make sure excising functionality doesn't break.
Added few more extra tests.

The performance difference is more visible when there are large number of rows. So, I added 20 million records and ran perf test.
Below are the performance results with avg response time:

varchar(before)
nvarchar(before

GraphQL
~734ms
~23ms

REST
~655ms
~24ms

varchar(after)
nvarchar(after)

GraphQL
~18ms
~23ms

REST
~18ms
~25ms

BEFORE CHANGE
GRAPHQL
VARCHAR

NVARCHAR

REST
VARCHAR

NVARCHAR

AFTER CHANGE
GRAPHQL
VARCHAR

NVARCHAR

REST
VARCHAR

NVARCHAR

/azp run

Based on your screenshots, it seems like "varchar" variant had the perf boost:

varchar(before)
nvarchar(before

GraphQL
734ms
19ms

REST
655ms
24ms

varchar(after)
nvarchar(after)

GraphQL
18ms
23ms

REST
18ms
25ms

Question about:

CAST(@param1 AS VARCHAR(MAX))

why cast instead of setting the sqldbtype on the dbconnectionparameter that is created?

/azp run

/azp run

/azp run

/azp run

/azp run

I have tried setting sqldbtype in DbConnectionparam but it dodn't work.

Please provide more context on what you tried and what exactly didn't work. Are you saying when we create parameters and send them to SQL, SQL isn't honoring the type specified? Are you suggesting that there is a bug with SqlClient?

I have tried setting sqldbtype in DbConnectionparam but it dodn't work.

Please provide more context on what you tried and what exactly didn't work. Are you saying when we create parameters and send them to SQL, SQL isn't honoring the type specified? Are you suggesting that there is a bug with SqlClient?

So, what i did was, I added a new property called SqlDbType in DbConnectionParam, and then i was setting its value before execution. It didn't bring any perf improvement. Also, I checked the Class DbParameters.

which is required as part of command that we send to SqlClient, doesn't have SqlDbType property or any other relevant property that could be used to specify the underlying Sql DbType for the parameter.

/azp run

/azp run

/azp run

/azp run

/azp run

/azp run

/azp run

I'm finding the same varchar/nvarchar issue with Azure SQL views. Did the fix described in this issue cover views as well or only tables? If the fix was for tables only, is there a way (e.g., in dab-config.json) to declare a column's data type?


Update sfb-server-updates.md

Update SfB Server 2019 CU3

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@SerdarSoysal PR has been copyedited and is ready for final review, could you please check and merge? Thanks!


Revert "Change the way features are registered" (#69)

This is not a "clean" revert, i.e. changes have been made to files in the meantime. 2 new features have been added using the "new" registration method, so I changed them to the existing registration method (in options.js).
Nonetheless, the most important parts have been reverted, specifically the options.js file.

@RobPavey

I have already submitted a revert. Sorry. If you sync your fork you should get the revert changes and hopefully they align with yours.

@RobPavey beat me to it in https://github.com/wikitree/wikitree-browser-extension/commit/5f4fec117d74e166d6832c95176152c007400d93 :smile:


Endpoint ID is a byte (signed!)

Endpoint in org.bubblecloud.zigbee.network.impl.ZigBeeEndpointImpl is defined as a byte. My Hue bulb reports two endpoints (which I'm yet to work out) - one is currently showing as -14, which presumably should show 242?
I'll likely change this to short - just logging it here so I don't forget.

Nice work chris :)


Question regarding use of Microsoft.Data.Sqlite

I am using the Microsoft.Data.Sqlite nuget package on my project. I just noticed that the github page says its been archived and moved to EntityFrameworkCore.
Can anyone tell me what this means for people using Microsoft.Data.Sqlite package by answering these questions?
1. Can I continue using Microsoft.Data.Sqlite?
2. If yes, will it continue receiving updates and development?
3. if No, do I need to install EntityFrameworkCore Nuget package and remove the Microsoft.Data.Sqlite? My project uses actual Raw SQL like below, will I still be able to use those? I dont see anything like this in the https://docs.microsoft.com/en-us/ef/core/querying/raw-sql page.
sqlSqliteConnection.Open();
String tableCommand = "CREATE TABLE IF NOT " +
    "EXISTS MyTable (Primary_Key INTEGER PRIMARY KEY, " +
    "Text_Entry NVARCHAR(2048) NULL)";

SqliteCommand createTable = new SqliteCommand(tableCommand, sqlSqliteConnection);
createTable.ExecuteReader();
sqlSqliteConnection.Close();

Thank you.

We just combined a few repos. See https://github.com/aspnet/Announcements/issues/320. Microsoft.Data.Sqlite is otherwise unaffected. Issues are tracked here with the area-adonet-sqlite label. In fact, there are already several resolved issues in the 3.0 codebase.

Thanks for the confirmation.


Issue with az boards

I try to run an Azure CLI command as an inline powershell script for a Build in a pipeline. It throws an error on the following line: ##[error]ERROR: az: 'boards' is not in the 'az' command group. See 'az --help'.
Command to run : az boards iteration team show-default-iteration --team "MyTeamName" | ConvertFrom-Json;
I've ran locally this command several times, it works well on my local computer.

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

ID: 876612e4-7fe4-0078-24e9-110ad121f526
Version Independent ID: 38f3144e-39e2-952d-2f7b-5e5c406d6d83
Content: az boards iteration team
Content Source: latest/docs-ref-autogen/ext/azure-devops/boards/iteration/team.yml
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

https://marketplace.visualstudio.com/items?itemName=ms-vsts.cli Azure DevOps CLI must be installed in addition to the Azure CLI module.


Task generateSequence solved - working

@Marcinati please review and test solution proposed by me.

Task completed.


Error when runing

Error

Usage

By the way, what's kind of version that python-igraph needed?

Seems those code could only run in python2.7.


Fix default CloudCompute for flows

What does this PR do?
In the merged Add support for custom cloud compute configurations for Flows PR, we set default CloudCompute name for flows to be default (https://github.com/Lightning-AI/lightning/pull/14831/files#diff-6cbbb993a8c2bf30a487086dcd4cf9a595ffc7399ecfc3efbb79f7568a3b74c8R106 ) - this is undesirable change.
This PR fixes the issue, sets it to be default that is currently used for Lightning Flows - flow-lite.
Does your PR introduce any breaking changes? If yes, please list them.
No.
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[ ] Did you make sure to update the documentation with your changes? (if necessary)
[ ] Did you write any new necessary tests? (not for typos and docs)
[ ] Did you verify new and existing tests pass locally with your changes?
[ ] Did you list all the breaking changes introduced by this pull request?
[ ] Did you update the CHANGELOG? (not for typos, docs, test updates, or minor internal changes/refactors)

PR review
Anyone in the community is welcome to review the PR.
Before you start reviewing, make sure you have read the review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃
cc @borda

@dmitsf can you add a changelog note and specify which milestone?

@dmitsf can you add a changelog note and specify which milestone?

Sure, done!


Rejected promise and errorPipe/errorThen

This is similar to #44
var p = new Promise<Int>();
p.reject(2);
p.then(function(a){
    return true;
}).errorPipe(function(e){
    return Promise.promise(false);
});

I expect result to be Promise with true for no errors, and false for error. I use that in tests.
But now it ends up in unhandled exception from update_errors. And if I call reject after errorPipe everything is as expected.
In errorPipe there's then(ret._resolve); and it ends up immediateLinkUpdate, isErrored branch.
handleError will check _error.length > 0 before calling next.handleError, immediateLinkUpdate wont.
Similar thing with errorThen.

Thanks for these, I'll give more of a substantial update soon.

I think this is fixed now.


All prices are zero?

It seems a bit odd that your checking the e-commerce site, but the pricing doesn't seem relevant in your use case. Why is that so? :)

You're right, I hadn't thought about that. I'll think about adding some tests in the next days.


API push fails if key expire set 1

Note: If your issue/bug is regarding the AWS Amplify Console service, please log it in the
Amplify Console GitHub Issue Tracker

Describe the bug
API push fails if key expire set 1
Amplify CLI Version
4.21.1
To Reproduce
amplify add api
? Please select from one of the below mentioned services: GraphQL
? Provide API name: amplifytest
? Choose the default authorization type for the API API key
? Enter a description for the API key:
? After how many days from now the API key should expire (1-365): 1
? Do you want to configure advanced settings for the GraphQL API No, I am done.
? Do you have an annotated GraphQL schema? No
? Do you want a guided schema creation? Yes
? What best describes your project: One-to-many relationship (e.g., “Blogs” with
 “Posts” and “Comments”)
? Do you want to edit the schema now? Yes

Expected behavior
Following resources failed

Resource Name: 7eeywqbd6na5voygrlzgvyxciuGraphQLSchema (AWS::AppSync::GraphQLSchema)
Event Type: create
Reason: Resource creation cancelled

Resource Name: GraphQLAPIKey (AWS::AppSync::ApiKey)
Event Type: create
Reason: API key must be valid for a minimum of 1 days. (Service: AWSAppSync; Status Code: 400; Error Code: ApiKeyValidityOutOfBoundsException; Request ID: c490e268-4743-426f-8122-cf98c3f1fba3)

✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
An error occured during the push operation: Resource is not in the state stackUpdateComplete

Screenshots

Desktop (please complete the following information):

OS:  Mac
Node Version : 12.16.2

Additional context
When try expire value set 2, Push is success

Closing this as the fix has been merged and is in the latest release.


Schematic diagram in contributing/architecture is broken.

Hi. I found that schematic diagram image in contributing/architecure section is broken.
I found the original image (I think this image was missing when migrating to https://github.com/denoland/dotland) but I think this image is a pretty old one and I wanna know there can be any update in this diagram.
If there isn't, please upload this image on dotland or manual. thanks :)

docs bug

deno architecture diagram

https://deno.land/manual/contributing/architecture
https://github.com/denoland/manual/blob/v1.21.1/contributing/architecture.md


Add message limit for subscriptions

Subscription object has to have message limit integer. Default is 3.
So if schedulers find 10 new coubs, he will send only 3 to user.

Not important when #37 is implemented.

Closed as sent coubs registry (#37) has been implemented


[BUG][WEBJS] -  Sessions disapper after restart

Describe the bug
Hello Bro ,
Every time i save session in mongedb and when server restart and restart mongodb and waha container , the sessions disappers
Containers created by
docker run -d -p 27017:27017 --name mongodb mongo
docker run -e WHATSAPP_SESSIONS_MONGO_URL=mongodb://localhost:27017/ --network host --name wapi -e WAHA_DASHBOARD_USERNAME=momaiz -e WAHA_DASHBOARD_PASSWORD=MSJJH@64178122 devlikeapro/waha-plus
and restart as
docker restart mongodb docker restart wapi
the sessions disappered
my server resources is
2 GB Memory / 2 Intel vCPUs / 70 GB Disk / FRA1 Ubuntu 24.04 (LTS) x64
and waha only work with 2 sessions
Version
{
  "version": "2024.6.2",
  "engine": "WEBJS",
  "tier": "PLUS",
  "browser": "/usr/bin/chromium"
}

How can i prevent sessions from disapper and how can  i restore them ?
best regards

Sessions also not saved here.
my docker-compose script:
whatsapp:
image: devlikeapro/waha:latest
container_name: whatsapp
environment:
- WHATSAPP_RESTART_ALL_SESSIONS=True
- WHATSAPP_FILES_LIFETIME=0
- WHATSAPP_FILES_FOLDER=/app/.media
volumes:
- /home/docker/whatsapp/:/app/.sessions
- /home/docker/whatsapp/media:/app/.media
ports:
- "3100:3000"
restart: unless-stopped
folder are writeable for all (for testing purposes)
running version:
{
"version": "2024.6.2",
"engine": "WEBJS",
"tier": "CORE",
"browser": "/usr/bin/chromium"
}
maybe same issue, but media is not saved either.

Sessions also not saved here. my docker-compose script:
whatsapp: image: devlikeapro/waha:latest container_name: whatsapp environment: - WHATSAPP_RESTART_ALL_SESSIONS=True - WHATSAPP_FILES_LIFETIME=0 - WHATSAPP_FILES_FOLDER=/app/.media volumes: - /home/docker/whatsapp/:/app/.sessions - /home/docker/whatsapp/media:/app/.media ports: - "3100:3000" restart: unless-stopped
folder are writeable for all (for testing purposes) running version: { "version": "2024.6.2", "engine": "WEBJS", "tier": "CORE", "browser": "/usr/bin/chromium" } maybe same issue, but media is not saved either.

Thank you for answer
but when i started to use mongodb as database , sessions are saved in database ,
so on restart it should recovered to the container again

@Momaiz
for mongodb case - there's no persistent storage connected to mongodb. Sorry about that, we put example (not ready for production) in the document, will fix it!
Try this one:
   docker run -d -p 27017:27017 --name mongodb -v mongo-data:/data/db mongo

OR consider using docker-compose setup - two required services:  https://github.com/devlikeapro/waha/blob/core/docker-compose.yaml#L46-L80

@qwerk

"tier": "CORE",

That's the reason for your case.
Saving sessions between container restarts requires PLUS docker image
devlikeapro/waha-plus

https://waha.devlike.pro/docs/how-to/plus-version/


config file ignored

Hello,
I wanted to set up a standalone server based on the docs:
package.json
"scripts":{
    "start": "node ./node_modules/uppy-server/lib/standalone/start-server.js --config ./config.json",
}

config.json:
{
  "UPPYSERVER_SECRET": "my-super-secret",
  "UPPYSERVER_DOMAIN": "https://uppy-server.mydomain.com,localhost:3020",
  "UPPYSERVER_DATADIR": "/mnt/server-data",
  "UPPYSERVER_PATH": "",
  "UPPYSERVER_PROTOCOL":"HTTPS",
  "UPPYSERVER_PORT": 3020
}

I only receive following error message (it seems that --config does not work?
uppy: 2018-07-05T08:47:06.788Z [warn] startup.secret auto-generating server secret because none was specified
 Please specify the following options to run uppy-server as Standalone:
 "filePath",
"server.host"

Any idea what I am doing wrong? Thanks

I used now an sh file to set the config but there seems to be no listen() on the standalone server. I am not sure if I misunderstand the concept but it will be great to show a standalone server example without cloning this repo. Thanks

Hi @dohomi for the json config, the object should take the form here
It seems you are rather specifying options meant for the .sh config in .json

@ifedapoolarewaju thanks for your answer. Do you have a working example of standalone server? The object you were referring has some functions which wont be available using as json. Are there any examples on a server setup - I've seen the lambda example but would like to deploy via zeit.co/now

@dohomi no function options are supported via the standalone server. You can merely pass the whole object as is. You can declare a json file like so:
{
  "providerOptions": {
    "google": {
      "key": "***",
      "secret": "***"
    },
    "s3": {
      "key": "***",
      "secret": "***",
      "bucket": "bucket-name",
      "region": "us-east-1"
    }
  },
  "server": {
    "host": "localhost:3020",
    "protocol": "http"
  },
  "filePath": "path/to/download/folder",
  "sendSelfEndpoint": "localhost:3020",
  "secret": "mysecret",
  "uploadUrls": ["https://myuploadurl.com", "http://myuploadurl2.com"]
  "debug": true
}

this should work for sure.
uppy client currently starts the standalone-server using env variables. See

@ifedapoolarewaju thanks for your example 👍


Persistence issue with config

Current behavior

A layout is initialized with a config containing 1 row and 2 columns. When containers placed in the columns are destroyed, the config seems to change as well (only row as content is available). With persistence the new config is stored and by refreshing the browser only row layout is working and there is no chance to place containers in a furter column.
Expected behavior:
Original layout content is still available
Codepen example:
not available
REMARK: I may be missing some specific implementation, any advice would be very helpful!
THX in advance!
J.

If I recall GL will destroy all containers that are empty if a child is removed. I think this is what you mean, so after the containers are destroyed the column will also be removed.
I think this can be fixed by adding the is closable setting to the column.

Thanks for your help! I will try that!


client.reports.email_activity.all(get_all = True) returning JSONDecodeError

Hi,
I am trying to pull the email activity for a campaign and when trying 'True' for get_all I receive the following error:
'    raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)'
If I try 'False' it works fine, but obviously pulls only 10 rows of data. Do you know what is causing this issue? I tried to override this and use count = 1000 and it works fine. I guess the issue is the maxed out count? - is it smarted to override count to use the exact number of emails a campaign has?
Thanks

You should be able to do 2 calls, one to get the number of records and another asking for exactly that many records. Could you please try using a count of 5000 with get_all set to False and let us know what happens? Also, can you provide information on how many records there are in that report so that we know if 1000 and 5000 are more or less than that?

My list should have roughly 4300 results, I have tried the following:
1000, 2000 - work
2500, 3000, 4000, 5000 - don't work
Is it possible that it is because of the time it takes to pull this? should the iteration be for less than 5000? What I don't understand is for example if the data I am pulling has 4300 counts and I am attempting to pull 5000, what does the API do with the 700 difference? Does the API know when to 'stop' or does it return blank rows?
Also, I assume that to loop through say items 2000 to 4000 would need offset = 2000 and count = 2000?

For anything where the count is more than the records, it just gives whatever it can grab, so if there are 5 records and I ask for 10, it gives only 5 back. We use this fact to perform our paging, checking that the number of records returned matches the number we asked for, and if so, shifting the offset until we get a less than full set of data. I believe there is just not data returned if you use an offset larger than the number of records.
Regarding grabbing the second batch of 2000 records (specifically 2001-4000), you would use a count of 2000 and an offset of 2000. The offset is strictly the number of records to skip, so to get all records you will need to start from 0. You can see how we normally grab all records by looking at the _iterate() command that is used when an all() function is called with get_all=True set.
@charlesthk, do you think it would be a good idea to drop the iteration value from 5k to 1k since this may be an issue of timing out or something similar, or do you have any ideas on testing that case?


Long tags do not get truncated

Version

Vue version: 3

Description
Currently, there's no way to truncate long tags. Can we please have a property that can define if tags are truncated after a user-specified/default length?

Hi did you solve this issue ?

Hi did you solve this issue ?

Not really a soluction but you can enable the wrap in the multiselect-tag as a workaround.
.multiselect-tag {
  white-space: wrap;
}

Fixed in 2.6.3. Longs tags are now automatically truncated. You can use breakTags prop to optionally break long tags into multiple lines.


#5560: Add all_reduce op

Tracking Issue : #5560
Add all_reduce op under experimental folder
Checklist

[x] Post commit CI passes - https://github.com/tenstorrent/tt-metal/actions/runs/11363163144
[x] T3K Pipelines - https://github.com/tenstorrent/tt-metal/actions/runs/11363166696
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] Device performance regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

HI @Aswinmcw A few questions:

does it mean only sum as reduce op is supported?
What is the output shape after all_reduce, is it equal to shape on one device?
Right now after all reduce all devices have the same reduced tensor?
Do we do reduce over the batch dimmension only?
What is the memory footprint on one device? e.g we have 32 devices and call reduce on tensor with volume 16k how how many dram will be allocated during this op?

Hi @Denys88 , answering a few questions,

Working of this op is individual different input tensors will be created and stored on each devices then a new temporary outer dim will be created and the remaining dims will be merged to maintain the 4D structure and this all_gather operation will happen only on the newly created 0th dim
Then it will reduce all gathered tensors and finally all devices will have same data
After all_reduce operation, the output shape will be same as the shape of a single chip

HI @Aswinmcw A few questions:

does it mean only sum as reduce op is supported?
Today yes. Future, no. We'd need to support min, max, and other reduction operations.

What is the output shape after all_reduce, is it equal to shape on one device?
Yes (for cases where for whatever reason one of the devices may have less data, it would be the size of the larger tensors, and the device with a smaller tensor would logically be padded with identity value elements. Whether this is a legitimate use case for this operation I am not sure atm).

Right now after all reduce all devices have the same reduced tensor?
Yes

Do we do reduce over the batch dimmension only?
Not really. All-reduce is a rank-wise operation. That is we are doing element-wise reductions for tensors across devices.

What is the memory footprint on one device? e.g we have 32 devices and call reduce on tensor with volume 16k how how many dram will be allocated during this op?

Today
memory consumption is inefficient because we are providing the least optimized functional implementation for all-reduce (composite all-gather + eltwise operation).
if # devices = n and input tensor size per device = m, then the total memory working set size (per chip) will be (today) (n + 1) * m

That is n * m needed to store the intermediate all-gather results and then another m to store the final output. After the operation the n *m can be returned to the allocation

Near future
We will enable the reduce_scatter + all-gather (composite) optimization that will both reduce memory pressure and improve performance. This has 2 constraints:

All-gather and reduce scatter must enable support for non-uniform tensor sizes across chips
the input tensor shape must have a dim size > n

technically it just needs a volume > n but that would require multi-dimension scatter/concat dim for reduce scatter/all-gather which is totally out of the picture for the foreseeable future

With this version total memory pressure (per chip) would be m + m * (1/n) where m * (1/n) is the size of the intermediate tensor between reduce_scatter and all-gather
Long Term
We will support a proper non-composite implementation in which the memory needed per chip will simply b m


Add support for CentOS Stream 9

Description of the changes
Add support for CentOS Stream 9 using the image - quay.io/centos/centos:stream9 to GSC.

How to test this PR?
To test this PR, set follow similar procedure as followed with Ubuntu and do gsc build and signing commands.

This change is

gsc.py line 264 at r1 (raw file):
Previously, dimakuv (Dmitrii Kuvaiskii) wrote…
Aren't you supposed to also check that version_id == 9? Otherwise it seems that your code will try to use quay.io/centos/centos:stream8 even for CentOS 8.

Done.

templates/quay.io/centos/centos/Dockerfile.compile.template line 74 at r1 (raw file):
Previously, dimakuv (Dmitrii Kuvaiskii) wrote…
Why do you have these random packages like R?

Removed unnecessary packages

Closing this PR as the branch name should follow this convention - name/feature.
Updated PR #206


Black borders at the bottom of windows form and popups cause frequent small UI displacements

Tested versions
v4.2.2,v4.3-dev6
System information
Godot v4.2.2.stable.mono - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4060 Laptop GPU (NVIDIA; <IP_ADDRESS>85) - AMD Ryzen 9 7940HX with Radeon Graphics (32 Threads)
Issue description
https://github.com/godotengine/godot/assets/42198626/aac240a5-1bdc-4a32-bf57-b809c6369c73
This black border cannot be captured by screenshots or screen recording software and can only be seen through the monitor. It slightly affects the user interface layout and causes the UI to shift slightly when it appears.
I noticed it the first time I used Godot on my new laptop.
As the mouse moves over the Godot control, it sometimes appears and sometimes disappears, causing a slight UI jitter.
Steps to reproduce
N/A
Minimal reproduction project (MRP)
N/A

Do you have any third-party overlays installed (similar to https://github.com/godotengine/godot/issues/13208 or https://github.com/godotengine/godot/issues/32990)?
Vulkan layers shouldn't cause issues in the project manager as it always uses OpenGL, so it's likely a third-party overlay that affects OpenGL as well.

I tried using --single-window and I noticed that the black border no longer appears in the popup window, but the black border is still present throughout the godot windows form. I also noticed the other two issuss you mentioned.
Also I don't have any software installed on my computer that involves overlays, including Fence, and I've turned off overlays for both NVIDIA and AMD, and the problem still occurs.
I tried switching the operating mode of my NVIDIA graphics card, and in NVIDIA-only mode, the black border no longer appears in godot, but in both optimus and auto-select modes, it appears.

After using the official Windows 11 image on my laptop and reinstalling everything through a USB drive, then reinstalling all the drivers, I found that the issue no longer occurs. I cannot determine which step resolved the problem, but it seems that the issue has indeed disappeared.

Can you reproduce this when starting the project manager with the --single-window command line argument?
Do you have any third-party overlays installed (similar to #13208 or #32990)?
Vulkan layers shouldn't cause issues in the project manager as it always uses OpenGL, so it's likely a third-party overlay that affects OpenGL as well.

After using the official Windows 11 image on my laptop and reinstalling everything through a USB drive, then reinstalling all the drivers, I found that the issue no longer occurs. I cannot determine which step resolved the problem, but it seems that the issue has indeed disappeared.

Thanks for the update. Closing then as we won't be able to investigate further if you can't reproduce the issue anymore, but it was likely caused by a driver bug or similar.


Support Expire Bill API

Need to support the expire bill API

Support added PR raised
https://github.com/SetuHQ/node-upi-deep-links/pull/13


add geemap to the list of available modules

What is the name of your repository ?
https://github.com/sepal-contrib/sepal-geemap
The name of your dashboard app
geemap
A short description of the app
Provide access to the power of geemap as a SEPAL application
Is your module requiring a GEE account ?
yes
Any comment you want to add
We should use the logo of the application itself instead of the SEPAL one. You can find it here: https://geemap.org/assets/logo.png
Note that not all the functionalities will be available even if they are displayed as they interact with the underlying notebook. I'll take issues one by one if people complian but that's good enough as a start
maintainer checklist

[x] Name is set
[x] Description set
[x] Comprehensive README
[x] 3 languages documentation files (can be empty)
[x] The requirements.txt file have been updated
[x] Existence of a release branch
[x] check behaviour within a fresh venv

Support for geemap will need to deal with how geemap initializes connection to GEE. See  https://github.com/openforis/sepal/issues/286 and https://github.com/gee-community/geemap/issues/1558.


Typo in _apiFunc.py

line 28:
return '{0}-{1}'.format(y, str(int(y) % 100 + 1)[-2:].zfill(2))
should be:
return '{0}-{1}'.format(x, str(int(x) % 100 + 1)[-2:].zfill(2))
Thanks for all the hard work!

Getting fixed in the refactor!

Deprecated helper functions in version 0.7.1. May come back, but for now, new API interaction has eliminated the need for these in the near term


spec: Remove DNS-naming and signing entries from high-level components

We don't have these yet, and can restore the entries if/when we land spec sections describing them.

LGTM
However, I thought this was part of a road map thing. Do we have it represented anywhere?

Do we have it represented anywhere?

#11, #22, and https://www.opencontainers.org/about/oci-scope-table

@wking  conflict, needs a rebase :)

I don't feel extremely strongly about this, but why not just add a note saying "work has not yet started"?

we had roadmapped these. It's more of a "work has not yet started" like @jonboulle said

On Mon, Apr 10, 2017 at 05:08:59AM -0700, v1.0.0.batts wrote:

we had roadmapped these. It's more of a "work has not yet started"
like @jonboulle said

Right, and I think we should remove them from the spec as long as they
are roadmap-only.  For example, the README currently links to
milestones for roadmap information 1, although in this case tags are
probably more appropriate [2,3].  I'm fine adding links to those
labels (or just link to 4?) in an out-of-spec location (like the the
README), but I don't think we need or want to track roadmap
information in the spec itself.
Rebased around #641 with 15c38f9 → 8eef994.

+1 to work has not started language.

On Wed, Apr 19, 2017 at 11:42:59AM -0700, Brandon Philips wrote:

+1 to work has not started language.

Is that “and I require the not-started language to be in spec.md and
not in the “Roadmap” README section 1?  Or are you ok with me
removing the entries from spec.md if I add not-started language to
that README section?

Since the roadmap to 1.0 doesn't reference these, please just add work-not-yet-started here in this list.

On Thu, Apr 20, 2017 at 04:09:32AM -0700, Jonathan Boulle wrote:

Since the roadmap to 1.0 doesn't reference these, please just add
work-not-yet-started here in this list.

I see no reason for that README section to be 1.0-specific, especially
since the only accurate part of the current roadmap body is the link
to milestones (which is not 1.0-specific).  But whatever, it seems
like the maintainers really want to keep these two particular roadmap
entries in the spec itself, so in 8eef994 → d67c709 I've restored them
with a “we may get to these at some point” caveat.

LGTM

review please

lgtm


fix for dart:html import and related errors

Merry Christmas and a Happy new year, I've been busy with another project for a while.
The dart:html (and others) import were causing compile errors for the flutter environment.
I've added conditional imports and alternative non-functional dummy classes to enable a clean compile.
There are also a few minor formatting and syntax changes to address some compile warnings and errors.
and finally a small fix for the logger.

LGTM


Generate fatal error when cri plugin fail to start.

Fixes https://github.com/containerd/containerd/issues/2371.
This PR:

Let event monitor and streaming server return an error channel.
Let CRI plugin Run return error if an error is received from the error channels of event monitor or streaming server.
Ignore http.ErrServerClosed which is a normal error generated when http server is Shutdown/Closed.

@t3hmrman @crosbymichael
Signed-off-by: Lantao Liu<EMAIL_ADDRESS>

Log when fail to start streaming server:
INFO[0000] Connect containerd service
INFO[0000] Get image filesystem path "/var/lib/containerd/io.containerd.snapshotter.v1.overlayfs"
INFO[0000] loading plugin "io.containerd.grpc.v1.introspection"...  type=io.containerd.grpc.v1
INFO[0000] Start subscribing containerd event
INFO[0000] Start recovering state
INFO[0000] serving...                                    address="/run/containerd/containerd.sock"
INFO[0000] containerd successfully booted in 0.005218s
INFO[0000] Start event monitor
INFO[0000] Start snapshots syncer
INFO[0000] Start streaming server
ERRO[0000] Failed to start streaming server              error="stayUp=false is not yet implemented"
INFO[0000] Stop CRI service
INFO[0000] Event monitor stopped
INFO[0000] Stream server stopped
FATA[0000] Failed to run CRI service                     error="stream server error: stayUp=false is not yet implemented"

Hey @Random-Liu thanks so much for the quick fix! This change will definitely improve my setup and hopefully it helps others too.
As always thanks to the team for the work on containerd (and of course cri-containerd)

LGTM

Hey how would I find out when this PR will make it into containerd?  I just ran into this issue today on containerd 1.1.2 so I'm assuming it's not in yet?


Try to split out tests to speed up ci

Pull request
Description
This tires to separate testing for different workspace components to parallelize and spend less total time
Checklist

[x] The RFC, if required, has been submitted and approved
[x] Any user-facing impact of the changes is reflected in docs.tremor.rs
[x] The code is tested
[x] Use of unsafe code is reasoned about in a comment
[x] Update CHANGELOG.md appropriately, recording any changes, bug fixes, or other observable changes in behavior
[x] The performance impact of the change is measured (see below)

Performance
perhaps

Ja I really hope it does, the test stuff right now is the slow part, if this reduces the total time for test it'd be great

The slowest part will be the connector integration tests due to the docker spinup times.

This is a failed attempt, it barely affects runtime but significantly increases compute use.


Old copy of buster lite to use with allky and RPiHQ cam?

Like others, I can't get the RPiHQ camera to work with the Bullseye release.
I downloaded an old copy of Raspbian buster lite, and followed the steps to install allsky.
I'm still getting an error when loading the GUI screen that the pi camera isn't setup correctly.
Can anyone point me in the direction of a known working buster lite file that I can use with the RPiHQ cam and allsky?

@loykastj, I see you noticed the Discussion article about this, and I replied.
I'm closing this Issue since we can track it in the Discussion.


Modified main scene and main.gd

I made some modifications to the main scene file and the main.gd file

Can you please specify what your modification does and how it is implemented in the game?

I added a login button to the MainScene.tscn. This button shows up on the screen when the scene loads. It’s positioned near the top-left corner (50, 50) and is labeled "Login".
Right now, the button is just a clickable UI element—it doesn’t do anything yet. To make it functional, you’ll need to attach a script to it. For example, you can make it print a message or open a login form when clicked.
The button is added as part of the main scene, so it will always be visible when this scene is active. If you want to customize its behavior, you can edit it directly in the Godot Editor or tweak the .tscn file further.

Can you please specify what your modification does and how it is implemented in the game?

I added a login button to the MainScene.tscn. This button shows up on the screen when the scene loads. It’s positioned near the top-left corner (50, 50) and is labeled "Login".
Right now, the button is just a clickable UI element—it doesn’t do anything yet. To make it functional, you’ll need to attach a script to it. For example, you can make it print a message or open a login form when clicked.
The button is added as part of the main scene, so it will always be visible when this scene is active. If you want to customize its behavior, you can edit it directly in the Godot Editor or tweak the .tscn file further.

Hi Moyasi,
I added a login button to the MainScene.tscn. This button shows up on the
screen when the scene loads and is labeled "Login".
Right now, the button is just a clickable UI element—it doesn’t do anything
yet. To make it functional, you’ll need to attach a script to it. For
example, you can make it print a message or open a login form when clicked.
The button is added as part of the main scene, so it will always be visible
when this scene is active. If you want to customize its behavior, you can
edit it directly in the Godot Editor or tweak the .tscn file further.
I also responded on GitHub
On Sat, Dec 28, 2024, 12:37 AM Moyasi Ginko @.***>
wrote:

@.**** commented on this pull request.
Can you please specify what your modification does and how it is
implemented in the game?
—
Reply to this email directly, view it on GitHub
https://github.com/Play2HelpWorld-com/Play2World3D_Desktop/pull/8#pullrequestreview-2524433441,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ6H54AL3C22SOLRDHOXRNL2HXQFFAVCNFSM6AAAAABUIYNAPWVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDKMRUGQZTGNBUGE
.
You are receiving this because you authored the thread.Message ID:
@.***
com>


Link to pre-filtered alert-overview

Proposal
To allow good a good UX for developers and integration between different webapps, we would like to link to a pre-filtered alert view.
Use case
A concrete use case is to have one application link to a the alert list pre-filtered with the name of a specific microservice. This will show the developer what kind of alerts are currently defined for their service.
I think this should show:

Are there any specific alerts defined for this microservice (the pattern is part of the expression, labels or annotations)
Probably: Are there generic alerts firing for that microservice now (one of the firing alerts has this service name as part of a label value)

In #10142, the alert page is reworked to allow for filtering. After that is merged, or as a part of that PR, it would be nice to include this option.
cc @Nexucis

Yeah I think it's ok do it (@juliusv yell you have something against it ;) )
For consistency, we should be able to pre-filtered the Target and Service Discovery page that have the same search bar.

@Nexucis I think generally it's a good idea. Just take into account that we already sync the URL parameters + page content on the /graph page in both directions, so it's probably a good idea to use a similar approach on the other pages and / or generalize the existing code for that in Prometheus.

totally agree @juliusv, the behavior should be exactly the same than in the graph page !

Hello, good morning, is it possible to work on this issue? to separate it, thanks

yes of course @AndreSPy1 so far nobody is working on it, so you can totally do it.

sí, por supuesto, @AndreSPy1 hasta ahora nadie está trabajando en eso, así que puedes hacerlo por completo.

thaks :)

Should this issue be closed out following the merge of PR 10613? https://github.com/prometheus/prometheus/pull/10613

Yes indeed. This issue can be closed now.


Implement command history to view all entered commands in chronological order

Didn't realize it was already implemented.


Indirect Cache Fail

There is a problem with indirect cache rendering too bright in latest 2.6alpha.
Tested with Hall_Bench example from LuxCore example scenes, on both Mac and Windows, PathCPU and PathGPU,
while the viewport preview works alright the render is too bright:

:
Problem occurred in other scenes as well but not always.

I can reproduce the problem but it is quite strange: I get the same problem with v2.5 binaries while I'm pretty sure it was working fine ... scratching my head.


Cosmetic changes of pagination / version

WHY
Some code does not adapt to Golang naming convention.
WHAT
Make cosmetic changes in pagination.go and version.go

LGTM!!
Thank you for your review with regard to Golang naming convention.


New API Token cmdlets

Description
I would like to be able to programmatically request a new API Token as part of an automated workflow for token rotation.
Related Issue
Fixes #316
Motivation and Context
Even though a user can generate a new API Token using the GUI, there exists the need to rotate those tokens on a regular basis. This can be done through regular expiration / creation cycles, or by forcing an expiration of a token arbitrarily and creating a new token on demand.
How Has This Been Tested?

Tested against CDM 5.0 with several variety of API Tokens generated with different tags, expiration dates, and organizations.
Tested with Pester to ensure null and empty parameters are handled properly.

Screenshots (if appropriate):
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:
Go over all the following points, and put an x in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTION document.
[x] I have updated the CHANGELOG file accordingly for the version that this merge modifies.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

This cmdlet is only supported in 5.0 (new feature). Because of this, it appears that Pester tests for the Get-RubrikAPIData function are failing since there is no compatibility with 4.0, 4.1, and 4.2.


Building cheriot-safe for Artix-A7 100T

Hello,
I have been attempting to build the core for the Arty-A7 100T. I did get it to build but I wanted to point something out and also would like some guidance for getting CHERIot compiled software running on the core.
Software
I am using Vivado 2022.2
Commit used
https://github.com/microsoft/cheriot-safe/commit/31ddb4738863aa420e2f95c87ce97b937a3a46e1
Steps I used to build

I created a new project in Vivado targeting the Arty-A7 100T
For source directories I added: All directories in
a. All directories from src excluding msft_cheri_tb
b. rtl/ from cheriot-ibex folder
c. vendor/lowrisc_ip from cheriot-ibex
The top file for me was automatically detected which is: msftDvIp_cheri_arty7_fpga.sv
I added the constraint file from this reo

During synthesis and implementatin
When I was synthesising using the Vivado (running as a GUI), I encountered this error:
[Place 30-574] Poor placement for routing between an IO pin and BUFG. If this sub optimal condition is acceptable for this design, you may use the CLOCK_DEDICATED_ROUTE constraint in the .xdc file to demote this message to a WARNING. However, the use of this override is highly discouraged. These examples can be used directly in the .xdc file to override this clock rule.

      < set_property CLOCK_DEDICATED_ROUTE FALSE [get_nets sck0_i_IBUF] >
      sck0_i_IBUF_inst (IBUF.O) is locked to IOB_X1Y114
       and sck0_i_IBUF_BUFG_inst (BUFG.I) is provisionally placed by clockplacer on BUFGCTRL_X0Y31

So I added this line to the constraint file in the repo:
set_property CLOCK_DEDICATED_ROUTE FALSE [get_nets sck0_i_IBUF]

After adding the line, I managed to build and generate the bitstream.
My questions

I when I uploaded the bitstream, LED4 was blinking and it is labeled alive_o, is this a watchdog LED and does it indicate the system is working correctly?
I did compile the LLVM project (cheriot branch) for the compiler. Which produced the clangd binary. How do I go about running software on this core (on the Arty-A7 100T).
Was the constraint file change fine to use?

Thanks!

I did compile the LLVM project (cheriot branch) for the compiler. Which produced the clangd binary. How do I go about running software on this core (on the Arty-A7 100T).

We need to update the build instructions in the RTOS repo, because the CHERIoT compiler is now maintained here.
The easiest way of making sure that you have an up-to-date developer environment is to use the dev container, which includes the latest toolchain and the Sail and Ibex simulators.
The RTOS includes a board description file (ibex-safe-simulator.json) that is tested with the Verilator simulator (see: https://cheriot.org/jekyll/update/2023/10/17/ibex-now-in-dev-container.html).  The FPGA build should have the same memory layout, so firmware images built with that should work on the FPGA as well (I have not yet tested this).  @kliuMSFT can hopefully explain how to load it.
It's possible that the clock speed will be different and so you may need to tweak this line.

Hello,
After compiling C code, what is the process of getting the binary running on the core. Do I need to use openOCD to upload the code to the FPGA (running the cheriot)

@Thingybob8055 I updated a couple more scripts and a simple README under build/. However it looks like you are ahead of me - which is great. I believe just by putting firmware images in the right place during synthesis, they are included in the bitfile. Please give it a try. You can also use openocd/jtag to load image but that would require some scripting (to talk to the backdoor memory access port in FPGA through JTAG).

Thanks! I will try it out. I assume the compiler produces the firmware images.
Do you have an example code or how to compile using the compiler? Or can brief me how (with an example LED blink code if its no trouble)

Here's the answer to your earlier questions,

it's ok to add the command you suggested to the constraints. It probably doesn't matter yet (unless you are using SPI interfacd), since the signal is only used as SPI clock
The "alive" signal is actually driven by a hardware counter that runs on the main sysclk, so the blinking LED means the clock is alive.

I will try to work out a software build example. Meanwhile if you can try the cheri_sanity or coremark example in the sim/verilator directory it would be good. The examples don't drive LEDs but they do print to UART, which is connected to the USB port on A7 and if things work out you should be able to see printouts on a serial terminal like PuTTY or TeraTerm

@Thingybob8055 I have added an (hopefully complete) example under sim/verilator/examples/hello_world. The example simply prints out a message on uart and blinks 2 LEDs, however it contains all the necessary startup code that you can use to start developing bare-metal the CHERIoT way.. Please let me know how it works out.

Hello,
I was away for a few days. I will to work on this and let you know how it goes!
@kliuMsft To compile the C code for the hello word example, do I need to setup the dev container linked above in this issue post? So that I have the compiler for CHERIoT
And for now, can I just use the two .vhx file in the firmware folder to get the example running?

Yes the vhx in veriator/examples should work - I'd suggest trying the hello_world first since it also should blink LED. You can use either the dev container or locally installed toolchain (in which case the build_fpga_test.sh in hello_world can serve as an example)

Hello,
The hello world example provided is working, I saw a Hello World message in the serial monitor and also the LEDs are blinking!
I would like to setup the compiler locally.
Are these instructions now up to date: https://github.com/microsoft/cheriot-rtos/blob/main/docs/GettingStarted.md
After building, the compiler (and LSP) binaries will probably me put inside a build folder in the repo root. Will I need to edit build_fpga_test.sh to find the correct location of these binaries?
And if so can you provide an example?
Or can I simply run the binary from the terminal like this to compile:
-target riscv32-unknown-unknown -mcpu=cheriot -mabi=cheriot -mxcheri-rvc -mrelax -Oz -nostdlib -DCHERIOT

I followed the build instructions for the compiler (the same one linked above)
@kliuMsft I was trying to run the build_fpga_test.sh script, and I added a line:
CLANG=<path-to-compiled-clang>
When running the script, it kept saying that it can't find the folder ./csrc_cheri and startup.S not found. So I ran the following commands manually:
<path-to>/clang-13 -target riscv32-unknown-unknown -mcpu=cheriot -mabi=cheriot -mxcheri-rvc -mrelax -Oz -nostdlib -DCHERIOT -c csrc_cheri/startup.S
<path-to>/clang-13 -target riscv32-unknown-unknown -mcpu=cheriot -mabi=cheriot -mxcheri-rvc -mrelax -Oz -nostdlib -DCHERIOT -I./csrc_cheri/ -Tlink_fpga_test.ld -o hello_world.elf hello_world.c startup.o csrc_cheri/util.c csrc_cheri/cstart.c
I managed to get a hello_world.elf file. But if I run objcopy (one installed by default on Ubuntu 22.04), I get this error:
objcopy -O binary -S hello_world.elf hello_world.bin
objcopy: Unable to recognise the format of the input file `hello_world.elf'

Is this the correct way to convert the elf file to a .bin or do I need another tool/specific version of the tool?
And how would I next convert the .bin to a .hex?
Thanks!

I tried manually compiling a firmware hex file using my steps  and it did work!
But it is a bit of a hassle to manually re-generate the bitstream to get a binary running on the core (it takes a while!)
If its no trouble, can you show how to upload a binary via openocd to the core?
Thanks!

This might take a little time, as I need to remember how JTAG loading works for this board. Also this way you may not be able to use the same usb/jtag connection to load both bitfile and firmware image. Possibly another usb2jtag (FH232) is needed.

The other approach that I’ve been pondering is to provide an IROM loader that reads the firmware into IRAM over the UART and then jumps to it. That might be easier than using JTAG. Writing 256 KiBs at 115,200 baud will be a lot quicker than reprogramming the FPGA.

That's definitely a valid approach. Either way you probably want to program the bit file to flash or micro SD, so that you can reboot/reload bit file by just resetting the board.

I managed to make the hello_world example in build/ work on my Arty A7, though when I try with the hello_world example from cheriot-rtos, it prints random symbols instead. It works correctly with the cheriot_ibex_safe_sim simulator though. Any clue what I'm doing wrong ?

@atrieu, just to confirm, if you use the firmware image in sim/verilator/examples/hello_world/firmwrare on FPGA board (not in sim), do you see the correct UART printout?

@atrieu, just to confirm, if you use the firmware image in sim/verilator/examples/hello_world/firmwrare on FPGA board (not in sim), do you see the correct UART printout?

Yes, this one works. That's what I meant by build/ initially, but I brainfarted.

In this case I suspect the example in cheri-rtos may need an update. @davidchisnall, I recall that you had to tweak the uart settings to get it work in rtos?

Hi, I have a BSP for the A7 that I hope works, but have not got an A7 to test it with. I will post it to a branch this morning for feedback.

Try this branch:
https://github.com/microsoft/cheriot-rtos/tree/arty-a7
You will need to set board to ibex-arty-a7-100 during the configure step when building.
This should work with the UART and exposes an LED driver for two of the LEDs.

Note: Resetting still doesn't work, but if someone can confirm that the UART driver works then I will add something to load firmware over the UART that can run in IROM.

@davidchisnall Thanks, it worked on my board !
It printed the following over the UART
             Hello world compartment: Hello world
                                                 Error handler: Thread exit CSP=0x20040930 (v:1 0x20040730-0x20040930 l:0x200 o:0x0 p: - RWcgml -- ---)

For the record, I executed the following commands in the dev container in VSCode:
$ cd cheriot-rtos/examples/01.hello_world/
$ xmake config --sdk=/cheriot-tools/ --board=ibex-arty-a7-100
[...]
$ xmake
[...]
$ cd build/cheriot/cheriot/release/
$ ../../../../../../scripts/run-ibex-safe-sim.sh hello_world

Then I copied the produced firmware/ and used the build_arty_a7 script from here.

Hurray!
That is what should happen.  Can you try adding this to the example:
Somewhere at the top:
#include <platform-leds.hh>

Somewhere around the hello world line:
auto leds = MMIO_CAPABILITY(LEDs, gpio_led0);
leds->enable_all();
bool on = true;
while (true)
{
  if (on)
  {
    leds->led_off(0);
    leds->led_on(1);
  }
  else
  {
     leds->led_on(0);
     leds->led_off(1);
  }
  on = !on;
  Timeout t{100};
  thread_sleep(&t);
}

This should make two of the LEDs alternate on/off states.

I had to include a bit more, but it works ! LD5 and LD6 are alternating and LD4 is flickering.
Complete hello.cc
#include <platform-gpio-leds.hh>
#include <thread.h>
#include <compartment.h>
#include <debug.hh>
#include <fail-simulator-on-error.h>

/// Expose debugging features unconditionally for this compartment.
using Debug = ConditionalDebug<true, "Hello world compartment">;

/// Thread entry point.
void __cheri_compartment("hello") say_hello()
{
	auto leds = MMIO_CAPABILITY(LEDs, gpio_led0);
	leds->enable_all();
	bool on = true;
	Debug::log("Hello world");
	while (true)
	{
		if (on)
		{
			leds->led_off(0);
			leds->led_on(1);
		}
		else
		{
			leds->led_on(0);
			leds->led_off(1);
		}
		on = !on;
		Timeout t{100};
		thread_sleep(&t);
	}
	// Print hello world, along with the compartment's name to the default UART.
}

@davidchisnall Hi
I read through the previous commit you have made. Do you currently have instructions to load compiled code via UART?
And in order to do so, do I need to re-synthesise the core with the newly committed cpu_irom.vhx file?
Thanks!

Hi,
I wrote a few instructions here.  Basically, rerun the build_arty_a7 script with the committed vhx (if you don't like running random binaries, rebuild the vhx from here).  When it boots, it will then ask for firmware.  I use minicom for talking to the board.  Minicom (-c on to get pretty colours) should be set to 115200 8N1 (which, I think, is the default these days).  You can then use paste file (meta-z y - meta is escape by default, at least for me) to send it a firmware image.
If you are building CHERIoT RTOS, I've added a little bit of board support code there.  Use --board=ibex-arty-a7-100 to compile for this config.
David

Not sure if this is the right place to ask, but are CHERI exception causes fully implemented ?
I have tried playing around with it for testing. Basically, I have set up mtcc so that my handler is called:
void exn_handler() {
    volatile unsigned int mcause;
    volatile unsigned int mtval;
    char buf[11];

    __asm__ __volatile__("csrr %0, mcause": "=r" (mcause));
    __asm__ __volatile__("csrr %0, mtval": "=r" (mtval));

    uart_puts("Hello from the exception handler!");

    uart_print_string("Exception cause: 0x");
    write_nibbles(mcause, buf);
    uart_puts(buf);

    if (mcause == 0x1C) {
        unsigned int cap_exn_cause = mtval & 0x1F;
        uart_print_string("Capability exception cause: 0x");
        write_nibbles(cap_exn_cause, buf);
        uart_puts(buf);
    }

    while (1);

    return;
}

Then, I trigger an exception with
    cspecialr        ca0, mtdc
    ccleartag        ca0, ca0
    clw              x0, 0(ca0)

I get the following
Hello from the exception handler!
Exception cause: 0x1C
Capability exception cause: 0x0

while I would expect to find a tag violation with code 0x2.
Clearing the permissions with candperm ca0, ca0, x0 instead of the tag also results in a 0x0 code, while cspecialw pcc, ca0 results in a 0x18 permit access system registers violation code instead.
This happens on both the simulator and my Arty A7.

Hi @atrieu,
There is currently a bug in exception priorities in Ibex.  See this comment for the work-around that we use in the software stack.  You should still get CHERI exceptions at the right point, but they will be the wrong numbers.  This is tracked in microsoft/cheriot-ibex#11 and will hopefully be fixed soon.  We're currently not using the CHERI exception causes for anything other than debugging, so it hasn't been a high priority.
You might be interested in talking to Tom Melham at Oxford.  His students have been working on verifying the Ibex.

Hi @atrieu,
Any way you can attach your ibex trace for the exception handler execution? As David pointed we haven't fully implemented exception causes yet, but even the existing RTL is supposed to report code 2 in this case (I have a very similar test case). So I am a little bit puzzled as why you are seeing this. Thanks.

Hi @kliuMsft,
Sorry for the late answer, I was traveling. You can find the full simulator trace here: https://gist.github.com/atrieu/16ef5aa869676d37c79174068ee70453
I'm guessing the interesting part is here https://gist.github.com/atrieu/16ef5aa869676d37c79174068ee70453#file-cheriot_cap_exn_trace-log-L4586-L4596
              0	     19669	2004004a	feb5055b	CH.ccleartag	c10,c10	 x10:0x00000000+0x17e3e0000 x10=0x00000000+0x07e3e0000
              0	     19670	2004004e	00052003	-->clw	x0,0(c10)	 x10:0x00000000+0x07e3e0000  x0=0x00000000 PA:0x00000000 load:0x00000000
              0	     19674	20040090	    7179	c.CH.cinc16csp	c2,-48	  x2:0x20080000+0x17e3e0000  x2=0x2007ffd0+0x17e3e0000
              0	     19677	20040092	    f406	c.CH.cscsp	c1,40(c2)	  x2:0x2007ffd0+0x17e3e0000  x1:0x20040046+0x15ebe0000 PA:0x2007fff8 store:0x120040046+0x15ebe0000
              0	     19679	20040094	    f022	c.CH.cscsp	c8,32(c2)	  x2:0x2007ffd0+0x17e3e0000  x8:0x00000000+0x000000000 PA:0x2007fff0 store:0x000000000+0x000000000
              0	     19682	20040096	    ec26	c.CH.cscsp	c9,24(c2)	  x2:0x2007ffd0+0x17e3e0000  x9:0x00000000+0x000000000 PA:0x2007ffe8 store:0x000000000+0x000000000
              0	     19683	20040098	0051155b	CH.cincaddrimm	c10,c2,5	  x2:0x2007ffd0+0x17e3e0000 x10=0x2007ffd5+0x17e3e0000
              0	     19684	2004009c	00b5245b	CH.csetboundsimm	c8,c10,11	 x10:0x2007ffd5+0x17e3e0000  x8=0x2007ffd5+0x17e03c1d5
              0	     19685	200400a0	34202573	csrrs	x10,mcause,x0	  x0:0x00000000 x10=0x0000001c
              0	     19686	200400a4	    ca2a	c.swsp	x10,20(c2)	  x2:0x2007ffd0+0x17e3e0000 x10:0x0000001c PA:0x2007ffe4 store:0x00000001c
              0	     19687	200400a6	34302573	csrrs	x10,mtval,x0	  x0:0x00000000 x10=0x00000000

It shows that reading mcause gives 0x1c and reading mtval gives 0x0.

Hi @atrieu,
Thanks! There is indeed a bug in the cheriot-ibex reporting which caused mtval not updating for a rv32 load/stores. I pushed a fix in the cheriot-ibex repo, would really appreciate if you can give it a try.

Hi @kliuMsft,
Can confirm it works, both in simulator in a locally built devcontainer, and on the fpga board!

@atrieu, that's great, thanks for confirming!

Thanks.  I've kicked off a rebuild of the devcontainer, which should pick up this fix.


Addded raindrops test generator

Version number in file sorted, slipped past me, sorry

Looks good, thanks!


BASH-2 Bundle Mac Desktop App as DMG

Description
Changed build config for mac to generate DMG. User experience is much better when installing via DMG.

[x] read and understood our Contributing Guidelines
[x] completed Mattermost Contributor Agreement
[x] executed npm run lint:js for proper code formatting

Test Cases
run : npm run package:mac
Execute the resulting Mattermost-xxx.dmg file.

@jasonblais I had told about this problem before. We are using Linux when cutting a release, but dmg requires Mac. I think mattermost-mobile should have same problem when building iOS app. How do you do that?

@jasonblais This would not be a blocker for our team. We could add this in during our build process, but would love to have it as part of the platform as it improves the delivery. Most applications are offered as a signed product in DMG format, similar like the mobile app. I'd suggest finding a delivery that allows proper signing.

@yuya-oc Jonathan has a ticket to automate the build process and code-signing for Windows and Mac
https://mattermost.atlassian.net/browse/PLT-7540
Once that ticket is resolved, will that let us introduce the DMG file as well?

@jasonblais Yeah, we need to continue using tar.gz in CI because of Linux, but we can use dmg when cutting releases.

Thanks! Added the Pending label for now, and we'll talk to Jonathan about the JIRA ticket (PLT-7540). We were planning to automate the build process and code-signing in the next few weeks.

Work on PLT-7540 tentatively scheduled to start next week (for automating the build process and code-signing for Mac and Windows apps).

Rebased to latest and added fixes to copy the right file for mac and updated electron-builder version.

https://github.com/mattermost/desktop/pull/676 has changed ownership, and is in the process of being finished up. After that we should be able to review and merge this PR


All operations modifying resources (patch, replace) should take --resource-version

kubectl's annotate, label and scale operations take --resource-version. This allows to prevent a change overwriting another change that happens between reading a resource and updating it.
The same reasoning applies to all operations that update a resource, like patch and replace.
Specifically for me the use case to modify values in a configmap but while making sure there were no changes between getting the configmap and writing the changes back.

/good-first-issue

From https://github.com/kubernetes/kubernetes/pull/87951#issuecomment-584235273 and https://github.com/kubernetes/kubernetes/pull/87951#issuecomment-583750522, resourceVersion can be specified as part of the manifest for patch and replace operations. Specifying them as flags could be ambiguous if the flag and manifest conflict on this.
/close

Why do we even have annotate, label and scale operations in the first place? All this can be specified in a manifest, like the resource version. I expected that is to improve the UX, same applies to --resource-version.
Just my 2 cent.


Signing each request

Just tracking here since it is implemented on relay side, this change will break other clients when updated so should be implemented on each client and released at the same time
https://github.com/stakwork/sphinx-relay/issues/302
https://github.com/stakwork/sphinx-relay/pull/303

can close after this is merged
https://github.com/stakwork/sphinx-kotlin/pull/439


Update search result download links

Summary
Our links on the download search results page are not consistent with document download links elsewhere on the site. This brings them in line and removes the (ODF/CSV) suffix which is now brought before the link name. I've also slightly tweaked the content on what I think might work well, but @karlchillmaid to decide. @JeremyHHY FYI, these are our file download links.
Before

After

I think the only publicly shown document downloads are on the G-Cloud service pages, e.g. on the right-hand side here: https://www.digitalmarketplace.service.gov.uk/g-cloud/services/436997837732555
There are several more in the supplier account for suppliers on a framework, but tricker to get a look at right away.

Seems there may be some inconsistency around this...
During applications open the file links have the file type thing:

But then once framework is live and we show framework documents to suppliers we don't have it:

FWIW, I think the new version here is better than the previous version :+1:

FWIW I think "Download search results as" is repetitive and therefore obscures the difference between the links. The context / heading means the user knows what these links will be, if they are obvious, so I'd be tempted to just have "Spreadsheet" and "Comma-separated values data file" or something like that.

This is where I saw the inconsistency (because I was using this page to make sure I wasn't breaking the briefs download format 🙂)

Thoughts @galund @karlchillmaid @TheDoubleK?

Thoughts @JeremyHHY?

This looks good.
Are these icons contain alt text for screen readers?

Yes, the filetypes get read out by screenreaders. @JeremyHHY


Use Project instead of Namespace

$SUBJECT
as we also have odo project xxxxx commands, our user should not get confused between project and namespace

Where is namespace exposed to the user?

resolved :+1:

it was exposed in odo catalog list components


Apply for membership

Hi guys. I'd like to be a member of KubeVela community. I have contributed some PRs to KubeVela community.
Hope to become a Member and continue to contribute.
Thanks!
These are my contributions so far:
1、Fix: Failed to get detail policy for application #5043
2、Feat: support field selector filter for 'vela ls' #5016
3、Fix: vela cluster join reports 'resource name may not be empty' error #4998
4、Feat: support label selector filter for 'vela ls' #4966
5、Fix: update namespace only if it doesn't have the env label #4947
6、Feat: support dryrun operation when creating or updating applications #4860
7、Fix: it does not check the same name for 'vela env init' #4796

Great job! +1

/cc @wonderflow

ping @Somefive @FogDong @jefree-cat @barnettZQG

LGTM, thanks for contributing!

@nuclearwu According to our community rules, Wellcome to as a Reviewer. We are looking forward to more contributions.  The next role is Approver.

@nuclearwu Congratulations! According to our community rule, you've been supported by three Maintainer/Approvers. You can create a PR to add yourself.

Thanks everyone, I appreciate it!

Great Job! Welcome!

@wonderflow Could you please invite me to be a member?


Optimize ConsolidateBlocks pass

Summary
Tries to address #8779
The following commits attempt to speedup the ConsolidateBlocks pass by calculating the unitary of each block inside of the pass rather than passing it as a QuantumCircuit and converting it to an Operator, which is redundant.
Details and comments
Known issues:

When a circuit is generated from a qasm file, some non-traditional gates will not have a defined to_matrix method and the algorithm will throw an exception. Fixed in 653e23c.
On Windows devices, the transpiler will throw the following error with certain circuits:

LinAlgError: eig algorithm (geev) did not converge (only eigenvalues with order >= 4 have converged)

Performance
The following is an example with a 1024 qubit random circuit of depth 128.

Old ConsolidateBlocks:

New ConsolidateBlocks:

Old ConsolidateBlocks snakeviz:
New ConsolidateBlocks snakeviz:

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

41 of 46 (89.13%)  changed or added relevant lines in 1 file are covered.
13 unchanged lines in 5 files lost coverage.
Overall coverage increased (+0.02%) to 86.004%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/transpiler/passes/optimization/consolidate_blocks.py
41
46
89.13%

Files with Coverage Reduction
New Missed Lines
%

qiskit/circuit/tools/pi_check.py
1
91.23%

qiskit/transpiler/passes/synthesis/unitary_synthesis.py
1
90.18%

qiskit/pulse/library/waveform.py
3
93.75%

crates/accelerate/src/sabre_swap/layer.rs
4
97.32%

crates/qasm2/src/lex.rs
4
91.65%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
71733

Relevant Lines:
83407

💛  - Coveralls

The _block_to_matrix method seems to be taking over some of the responsibilities which Operator would normally take. If such an improvement is possible then it seems better to place it with Operator so other parts of the code could benefit from it. If it is the case, as suggested, that there is some trade off between matmul and einsum as a function of matrix size it would be nice to understand where that trade-off lies (e.g. n=2, 3,...) and apply the switch there.
Actually I believe @chriseclectic orginally was using matmul in Operator but switched to einsum for speed but perhaps that was just based on larger matrices?

Erick: this PR is deliberately meant to take over some of what Operator does just like #5909 does, because of the overheads from Operator itself.  There's potentially the case for some slightly faster paths to be added to Operator for the case of small numbers of qubits, but Operator is rarely performance critical, and is optimised more towards generality.  There's overhead in managing things like the OpShape, parsing the qargs into a format, and then of course there's the einsum parts.
einsum lets Operator avoid constructing the implicit full-tensor-product space matrices when composing a smaller operator onto a larger one, and it allows general argument re-ordering without the explicit swaps that the PR in its current form adds in (though of course it's possible to elide the 2 matmul swap ops and do a direct permutation, or the manual 4-tensor transposition in Numpy).  For the cases considered by this PR, there's no need for any of Operators general handling, and you can see in the results the huge improvement from avoiding that overhead.

Can you show othe profile result in table format sorted by cumtime and tottime for the top ~20 rows?

Can you show the profile result in table format sorted by cumtime and tottime for the top ~20 rows?

This is the profile result of the old version:

By tottime:

By cumtime:

This is for the optimized version:

By tottime:

By cumtime:


Repository as a model

We are developing a service where we need to create indexes in remote ES clusters.
Our use case is like that
class RemoteRepository
  include Elasticsearch::Persistence::Repository

  attr_reader :index_model, :remote_client

  def initialize(index_model)
    @index_model = index_model
    @remote_client = Elasticsearch::Client.new client_options

    define_settings
  end

  protected

  def client_options
    { host: index_model.cluster.host }
  end

  def define_settings
    index  index_model.name
    document_type index_model.type

    ...
  end

Problem raised when we were testing that approach with rspec. It seems like  mapping get cached.
Say we have following test setup
repo1 = RemoteRepository.new(model_1)
repo2 = RemoteRepository.new(model_2)

repo1.mapping
# => {:index=>"index_1", :body=>{:settings=>{:number_of_shards=>2}, :mappings=>{:"type_1"=>{:properties=>{...}}}}}
repo2.mapping
# => {:index=>"index_2", :body=>{:settings=>{:number_of_shards=>2}, :mappings=>{:"type_1"=>{:properties=>{...}}}}}

Since mapping is cached, it gets complicated  if you have to deal many repo instances at once.

Here is some technical insight.

Gateway is defined when repository class gets included into model
It includes class methods for model indexing
Here is how mapping gets cached

I wonder if that would be a good idea to initialize a new geteway instance for every RemoteRepository instance?

Hi, if I understand correctly, you're passing a model class as the index_model argument, and the access the mappings. This is what makes it a bit tricky, because the repository itself doesn't care about the mappings, but the model does.
I don't think we can throw out the caching in the model "just like that", because currently we support calling mapping repeatedly, and accessing the same object... and I think it makes sense to support it.
What's weird though, is that the mapping would be shared across the repository objects...

I solved my case by initializing new gateway for every repository instance
  def initialize(index_model)
    ...
    @gateway = Elasticsearch::Persistence::Repository::Class.new host: self.class
    ...
  end

I am not sure how efficient it will be in terms of memory, that I will have to figure out later, but it solves an obstacle atm.
IMHO this thing can be addressed by introducing a setter method for a gateway and covering that case in Readme.

I got this impression that Elasticsearch::Model should be included into Activerecord class and then it provided ES functionality to deal with records of this data.
Our case is a bit different. We use db to stare information about geographically distributed clusters and indexes that they contain and provide functionality to create and manage those indexes via web UI. In this context index_model contains an information about ES index it self (like name, host, fields) and is not for indexing or searching.

This is resolved with the release of elasticsearch-persistence 6.0.
Please see the documentation here.


Function signatures containing structs appear as undefined

I noticed that structs do not render in the docs with a description. This can be seen in the docs for set() in Bar.sol found in this repo.
### set

```solidity
function set(IBar.T t) external nonpayable

Parameters

Name
Type
Description

t
IBar.T
undefined

+1 also ran into this, would be great to get that fix in.


Vagrant image does not have /mnt path

When using the vagrant-vbguest plugin I have to ssh into the machine before it completes package installs and create the /mnt folder for the machine to come up cleanly.
Copy iso file /usr/share/virtualbox/VBoxGuestAdditions.iso into the box /tmp/VBoxGuestAdditions.iso
Mounting Virtualbox Guest Additions ISO to: /mnt
mount: /mnt: mount point does not exist.
Unmounting Virtualbox Guest Additions ISO from: /mnt
umount: /mnt: no mount point specified.
==> mymachinename: Checking for guest additions in VM...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

umount /mnt

Stdout from the command:

Stderr from the command:

umount: /mnt: no mount point specified.

What host OS are you running?
I ran into the same error after upgrading to macOS 12.1 and fixed it by reinstalling the vagrant-vbguest plugin:
vagrant plugin install vagrant-vbguest

@JeffPsycle In addition to @yippeykeiyay's comment, We need the details below to reproduce the issue.

OS version.
Ruby version ruby --version
Installation method(Upstream or Distro provided) of the vagrant and its version. vagrant version
Versions of the all installed vagrant plugins. vagrant plugin list

Thanks for the reply, here are the details:
OS Version: Fedora 34
Ruby Version: ruby 3.0.2p107 (2021-07-07 revision 0db68f0233) [x86_64-linux]
Installation Method: Upstream provided (RPM), vagrant-2.2.19-1.x86_64
vagrant.x86_64                       2.2.19-1                            @hashicorp

Versions of all the installed plugins:
vagrant-cachier (1.2.1, global)
vagrant-hostmanager (1.8.9, global)
vagrant-managed-servers (0.8.0, global)
vagrant-vbguest (0.30.0, global)

Dear @JeffPsycle  and @yippeykeiyay ,
Finally, I got time to install the VirtualBox provider and this plugin to try to produce the issue, and I did.
It's fixed on today's almalinux/8 and almalinux/9 releases. Please let me know if everything works for you too.

@LKHN thanks for the update. Unfortunately I am currently running Fedora 36 and it has a fair number of issues with VirtualBox at the moment. Waiting on VB 3.1.35 so I can test this correctly. I can confirm however that the /mnt folder is available and should get the members of my team running this on non-M1 Macs working smoothly.
Will chime in with a status update as soon as Virtual Box updates.

@LKHN VirtualBox 3.1.36 just came out which has fixed the 5.18 kernel issue so I have been able to test this and confirm that the /mnt path issue that breaks the Guest Additions has been fixed. Thanks for getting this corrected!


JGRP-2034 Use the JDK-specific SASL realm property so that it works w…

…ith IBM
https://issues.jboss.org/browse/JGRP-2034

Backported to 3.6 branch


Remove undeclared variable warnings from printed output

Terraform Repo makes use of .tfvars files to do partial backend initialization, see https://github.com/app-sre/terraform-repo-executor/blob/main/pkg/terraform.go#L107. This partial backend init includes Vault credentials however with the new secret approach in tf-repo M1, most repos will not be defining vault_addr, vault_role_id, and vault_secret_id in their .tf files.
Therefore, when a plan happens you see warnings like these:
....
Plan: 1 to add, 0 to change, 0 to destroy.

Changes to Outputs:
  + vpc_id = (sensitive value)

Warning: Value for undeclared variable

The root module does not declare a variable named "vault_addr" but a value
was found in file "aws.auto.tfvars". If you meant to use this value, add a
"variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.

Warning: Value for undeclared variable

The root module does not declare a variable named "vault_role_id" but a value
was found in file "aws.auto.tfvars". If you meant to use this value, add a
"variable" block to the configuration.

To silence these warnings, use TF_VAR_... environment variables to provide
certain "global" settings to all configurations in your organization. To
reduce the verbosity of these warnings, use the -compact-warnings option.

Warning: Values for undeclared variables

In addition to the other similar warnings shown, 1 other variable(s) defined
without being declared.

We can't use compact-warnings due to limitations in tfexec, and Terraform itself doesn't offer a way to disable these warnings so I'm just removing them with regex from the final output since they may confuse users.

LGTM