preformance_function error?

double Utilities::performance(std::vector<double> y_hat, std::vector<double> outputSet){
    double correct = 0;
    for(int i = 0; i < y_hat.size(); i++){
        if(std::round(y_hat[i]) == outputSet[i]){
            correct++;
        }
    }
    return correct/y_hat.size();
}

problem:std::round(y_hat[i]) == outputSet[i]???

Hello,
The reason I employed rounding is for the fact that it is unlikely that a model outputing discrete values would be able to exactly output, say [1, 0, 1]. Typically, these values are approached if an iterative algorithm is used, and a typical output would be something like [0.99, 0.001, 0.999], etc.. For this reason, rounding them to the nearest integer and then comparing them with the true outputs is more convienent for calcualting accuracy.


Feedback when good or bad move

Maybe confetti or something?

Start from position before move, think on move, decide if good or bad, and update status


Dendron: Paste File from clipboard, just like for image

Please Select if your Request is Either something new or an Enhancement

[ ] Enhancement of an existing Feature.
[x] Request of a new feature.

Please select the area your request applys to. (Multiple selections are Possible)

[ ] Onboard. Initial vault setup and import/export pods
[x] Create. Note creation, lookup, snippets and templates
[ ] Retrieve. Backlinks, references, graph view
[ ] Structure. Refactoring, multi-vault and schemas
[ ] Publish. Sharing your repo with the world
[ ] Misc (Choose this if your not sure)

Is your feature request related to a problem? Please describe
Paste a file just like an image from your clipboard. The current process is to right click > copy path > dendron paste file > paste path > remove double quotes on end > enter.
Describe the solution you'd like
Copy file to clipboard > dendron paste file > file added to assets and link added in active note at current cursor position
Describe alternatives you've considered
Current Dendron: Paste File function, but it requires too many steps.
Additional context
OS: WIndows 10
Dendron Version: 0.50.0

Hi ConnorSMaynes - thanks for the feedback. We had a similar issue reported earlier here: https://github.com/dendronhq/dendron/issues/575
The current solution is to use drag and drop with the tree view, as detailed in the note above.

I have multiple vaults and many files at this point, which leads to a large tree. Drag-n-drop requires scrolling through this large tree each time I need to import something. This is inconvenient and slow. An interface similar to Paste Image would be much faster.

One general comment here would be on the choice of function naming. "Paste image"/"Paste File".  I don't think many people will naturally arrive on the word "paste" in this context. This made the functionality challenging to find in the command palette and difficult to search for in documentation as well.
Consider using terminology that people are already familiar with, ie, attach. Using the word attach instead of or in addition to paste, leverages years of familiar functionality in the form of email.


Improve quote/code blocks display upon applying content or on character input

Treat quote & code block on zero-length selection as pending formats
Force redraw when applying content to text view

I found a bug on blockquotes when adding newlines, basically newlines cannot be added anymore.
I partially fixed it here: https://github.com/matrix-org/matrix-rich-text-editor/pull/515
However now consecutive newlines inside the blockquote will not be accepted (which was the whole point of using originally  )


Update overwrite all rows when id not specified

What version of Go are you using (go version)?
go version go1.9 darwin/amd64
Which database and its version are you using?
sqlite3
3.16.0 2016-11-04 19:09:39 0e5ffd9123d6d2d2b8f3701e8a73cc98a3a7ff5f
What did you do?
I'm following the docs for direction on update http://jinzhu.me/gorm/crud.html#update.
When I try to update a model's field and I don't specify the id, gorm updates the field for all rows in the table.  As this can be very destructive, I don't think this should be the default behavior.
Please provide a complete runnable program to reproduce your issue.
package main

import (
	"fmt"

	"github.com/jinzhu/gorm"
	_ "github.com/jinzhu/gorm/dialects/sqlite"
)

var db *gorm.DB

func init() {
	var err error
	db, err = gorm.Open("sqlite3", ":memory:")
	if err != nil {
		panic(err)
	}
	db.LogMode(true)
	db.AutoMigrate(&Place{})
}

type Place struct {
	ID   int
	Name string
}

func main() {
	// add some initial data
	db.Create(&Place{ID: 15, Name: "Dairy Queen"})

	// setName with empty struct
	setName(&Place{}, "Burger King")

	// Check the first place to see if it changed
	p := &Place{}
	db.First(p)

	if p.Name == "Burger King" {
		fmt.Println("failed")
	} else {
		fmt.Println("success")
	}
}

func setName(p *Place, name string) {
	if err := db.Model(p).Update("name", name).Error; err != nil {
		panic(err)
	}
}

Here is the output:
[2017-11-16 13:47:08]  [1.73ms]  CREATE TABLE "places" ("id" integer primary key autoincrement,"name" varchar(255) )

[2017-11-16 13:47:08]  [0.42ms]  INSERT INTO "places" ("id","name") VALUES ('15','Dairy Queen')

[2017-11-16 13:47:08]  [0.23ms]  UPDATE "places" SET "name" = 'Burger King'

[2017-11-16 13:47:08]  [0.58ms]  SELECT * FROM "places"   ORDER BY "places"."id" ASC LIMIT 1
failed

db.BlockGlobalUpdate(true)


[PE-D][Tester E] In User Guide, add command does not specify the limited range of departments.

In the User Guide, there is no mention of add command being able to take in specific departments (General Management, etc...). This should be something acknowledged so that the user knows.
Screenshot:

Error Message:

Labels: type.DocumentationBug severity.Low
original: kangzongxian/ped#12

Duplicate with #176.


Server has new service to create account and check hCaptcha

Acceptance criteria

[x] New service that will create accounts if catcha is correct
[x] new environment variable passes the private key used to sign the create account transaction to the server
[x] environment variable is added to staging and demo Digital Ocean apps
[x] docs are updated about the env variable

// new endpoint

createAccount(usernameHash: Checksum256, keys: {
  level: KeyManagerLevel,
  publicKey: PublicKey
}[], recaptchaResult: unknown) : {
  success: boolean
  error?: {
        code: SdkErrors;
        reason: string;
    };
}

previous sprint: 2
next sprint: 1


Unit tests

I think this project would benefit from unit tests. There are some functions that work different from PHP for some argument variations and there are some functions that are implemented partially. If there were unit tests prepared, we could easily track progress and fix many issues.
Should we maybe agree on one JS unit testing framework that is easy to set up and run and place all tests in the /tests directory?

Sounds like a very good idea---please feel free to take initiative on
making a choice. I've always been impressed with Dojo's broad approach
to problems so was curious to investigate their (stand-alone) unit
testing framework Doh!, but never got around to it. But I think any
ought to serve the need for verification. I don't know if Kevin prefers
any which could be tied into his automated processes (e.g., to flag a
function from the compiler which failed such tests).
Brett
On 12/29/2011 7:24 AM, Rafał Kukawski wrote:

I think this project lacks unit tests. There are many functions that work different from PHP and there are some functions that are implemented partially. If there were unit tests prepared, we could easily track progress and fix many issues. Should we maybe agree on one unit testing framework that is easy to set up and run and place all tests in the /tests directory?

Reply to this email directly or view it on GitHub:
https://github.com/kvz/phpjs/issues/25

While the current test framework is > 3y old, bloated, and could use a lot of love (or hate :), here's how to run it:
Install rhino. On osx:
brew install rhino

Run the suite for all functions in the math category:
./_tools/phpjstest.php category math

Run the suite for acos():
./_tools/phpjstest.php acos

Run the suite for acos() with debug information:
./_tools/phpjstest.php acos debug

Run the suite for acos() with and compare the js results with php results:
./_tools/phpjstest.php acos php

It parses the testcases & expected results from the function's headers and uses rhino to execute & compare. Afterwards it runs jslint on it.

Thanks Kevin for sharing instructions how to use the existing test suit. I see one problem with it. I don't want to bloat all js files with huge comments with tests for all possible arguments (like passing bool or strings to sin(), cos()). There are some very complex functions for those I would need to provide dozens of test cases in order to test them properly. That is why I am opting for a separate test suite - that doesn't necessarily have to be automated from the beginning, just that I can easily run on my local machine - where I can check for all kinds of strange cases that the users of this project don't necessarily have to bother with.
When it comes to unit testing frameworks, I personally like JS Test Driver, but I think it's too much for this project, since we mainly deal with core JS which is the part of the API that works the same in almost every major browser, so we don't need the possibility to check many browsers at once. Something that can be run in my favorite browser (QUnit) or based on rhino/node.js would be OK. Like I said, for me the priority is the ability to easily run it on my local machine. But in order not to make the automation in future difficult, we should better make a good decision now.


⚠ Bofrost.de has degraded performance

In d020913, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1345 ms

Resolved: Bofrost.de performance has improved in bf260cb after 20 minutes.


ios app Memory consume too fast  when I use [ initWithBridge: moduleName:] api

I  invoke
'_rootView = [[RCTRootView alloc] initWithBundleURL:jsCodeLocation moduleName:@"xxxxx" launchOptions:nil];'  in  - (void)viewDidLoad;
And invoke ‘_rootView = [_rootView initWithBridge:_rootView.bridge moduleName:@"xxxxx"];’  in - (void) viewWillAppear:(BOOL)animated.
so  when often invoke viewWillAppear.   the  memory warning  happen

Could you please investigate to see whether the memory is consumed by lots of root views, or if it's because you are creating a lot of views in general?

Yeah as @ide said we need some more information on what views are being created here, could you provide us with some more extensive sample code that reproduce the issue for you?

Hi there! This issue is being closed because it has been inactive for a while.
But don't worry, it will live on with ProductPains! Check out its new home: https://productpains.com/post/react-native/bridge-ios-app-memory-consume-too-fast-when-i-use-initwithbridge-modulename-api
ProductPains helps the community prioritize the most important issues thanks to its voting feature.
It is easy to use - just login with GitHub.
Also, if this issue is a bug, please consider sending a PR with a fix. We rely on the community to provide
bugfixes as the core team is heavily focused working on performance.


Fix crashes when previewing NSData keychain items.

:wave:
This improves upon https://github.com/Flipboard/FLEX/pull/360, by also letting you view details of keychain items that have either service/account or password set to NSData types, incorrectly.
One frequent cause of this, is integrating the Firebase framework (c.f https://github.com/firebase/firebase-ios-sdk/issues/4742), which creates a keychain entry with a _pfo keychain entry, but using an NSData object, instead of a NSString.
This lets you view such items:

Feel free to reformat/rename anything in the PR — and thanks for all the hard work on FLEX before :)

Awesome, thanks :)


Op 15262: update the API Access

https://devopsmx.atlassian.net/browse/OP-15262 : update the API Access
We prefer small, well tested pull requests.
Please refer to Contributing to Spinnaker.
When filling out a pull request, please consider the following:

Follow the commit message conventions found here.
Provide a descriptive summary for your changes.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Add inline code comments to changes that might not be obvious.
Squash your commits as you keep adding changes.
Add a comment to @spinnaker/reviewers for review if your issue has been outstanding for more than 3 days.

Note that we are unlikely to accept pull requests that add features without prior discussion. The best way to propose a feature is to open an issue first and discuss your ideas there before implementing them.

This PR  triggered this build in this execution, please wait for it  and child pipelines to succeed before merging:  https://isd.prod.opsmx.net/deck/#/applications/gcp-gitprtrigger/executions/details/01G2YNHZDENVXYD6MEMPJMFBR0

This PR  triggered this build in this execution, please merge to master only if this succeeds:  https://isd.prod.opsmx.net/deck/#/applications/gcp-gitprtrigger/executions/details/01G2YNJ8245YPDJ4QM11Q68WGE

SUCCESSFUL RunTests RESULT: Tests run: 201, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 257.415 sec Reviewers ,  this PR did not cause the failures in  https://jenkins.opsmx.net:8181/jenkins/job/Dev-run-tests-on-gitpr-parallel/ws/emailable-report-99.html

RunTestJar RESULT: Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 Developers , please check that the commits to master branch did not cause the failures in  http://jenkins.opsmx.net:8181/jenkins/job/Dev-run-tests-on-staging-master/ws/emailable-report-380.html

RunTestJar RESULT: Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 Developers , please check that the commits to master branch did not cause the failures in  http://jenkins.opsmx.net:8181/jenkins/job/Dev-run-tests-on-staging-master/ws/emailable-report-568.html

RunTestJar RESULT: Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 Developers , please check that the commits to master branch did not cause the failures in  http://jenkins.opsmx.net:8181/jenkins/job/Dev-run-tests-on-staging-master/ws/emailable-report-603.html

RunTestJar RESULT: Tests run: 537, Failures: 85, Errors: 0, Skipped: 355, Time elapsed: 1,216.853 sec <<< FAILURE! Developers , please check that the commits to master branch did not cause the failures in  http://jenkins.opsmx.net:8181/jenkins/job/Dev-run-tests-on-staging-master/ws/emailable-report-628.html

RunTestJar RESULT: Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 Developers , please check that the commits to master branch did not cause the failures in  http://jenkins.opsmx.net:8181/jenkins/job/Dev-run-tests-on-staging-master/ws/emailable-report-638.html

RunTestJar RESULT: Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 Developers , please check that the commits to master branch did not cause the failures in  http://jenkins.opsmx.net:8181/jenkins/job/Dev-run-tests-on-staging-master/ws/emailable-report-652.html

RunTestJar RESULT: Tests run: 0, Failures: 0, Errors: 0, Skipped: 0 Developers , please check that the commits to master branch did not cause the failures in  http://jenkins.opsmx.net:8181/jenkins/job/Dev-run-tests-on-staging-master/ws/emailable-report-662.html

RunTestJar RESULT: Tests run: 494, Failures: 39, Errors: 0, Skipped: 175, Time elapsed: 2,959.105 sec <<< FAILURE! Developers , please check that the commits to master branch did not cause the failures in  http://jenkins.opsmx.net:8181/jenkins/job/Dev-run-tests-on-staging-master/ws/emailable-report-674.html


Re-org the source tree

Goals

Reduce the number of extensions under extensions
Increase the visibility of the extensions now under extensions/support. They are hard to find for newcomers and they are hard to scroll to for maintainers

Non-goals (possible future goals)

Split the extensions under extensions into even smaller groups, like we have in the GH workflow
Do anything with the itests

Current state:
├── catalog
├── docs
├── examples
├── extensions
│   ├── ...
│   ├── support
├── integration-tests
├── poms
└── tooling

Proposed state
├── catalog
├── docs
├── examples
├── extensions
├── extensions-core       # The extensions whose camel artifacts are under core in the Camel source tree
├── extensions-support   # Moved from extensions/support
├── integration-tests
├── poms
└── tooling

WDYT?

Fine with me, wonder if it could make sense to use core instead if extensions-core (same for support)

Fine with me, wonder if it could make sense to use core instead if extensions-core (same for support)

No problem, if you like it that way.
Now pondering whether it is worth to have a common parent folder for the three extension folders. We currently have some sanity checks defined in extensions - I'd either have to move the def to the top pom or have them three times.

I think I slightly prefer the option without the common parent folder for the three extension folders. It's less clicking around in the IDE.

Fine with me, wonder if it could make sense to use core instead if extensions-core (same for support)

No problem, if you like it that way.

Actually, we already have a module called camel-quarkus-core and I'd like to keep the naming scheme artifactId = "camel-quarkus-" + dirName. So extensions-core or core-extensions seems to be a better choice.


Fix broken CLA link on the main README.md file

Hi @mathieu-benoit, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@mathieu-benoit, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, AZPRBOT;

@mathieu-benoit - Nous apprécions la mise à jour du lien.


NPM install fails.

Hello,
Trying to install and configure a branch new Laravel project fails. I may have tracked down the reason to a problem with the dependencies required by this package.
When I run npm ls I get this output:
....
   │   ├──<EMAIL_ADDRESS>    │   ├──<EMAIL_ADDRESS>    │   └──<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>
npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! missing<EMAIL_ADDRESS>required by<EMAIL_ADDRESS>npm ERR! not ok code 0

Reinstall everything properly.

If it may help people, I had the same issue and as I was using yarn I had to do the following:
yarn cache clean
rm -rf node_modules
yarn

@phated using the search functionality lead me to more than 300 issues, many of them related but the answers were not very helpful:
https://github.com/gulp-sourcemaps/gulp-sourcemaps/issues/321
https://github.com/gulp-sourcemaps/gulp-sourcemaps/issues/320
https://github.com/gulp-sourcemaps/gulp-sourcemaps/issues/314
https://github.com/gulp-sourcemaps/gulp-sourcemaps/issues/311
https://github.com/gulp-sourcemaps/gulp-sourcemaps/issues/307
https://github.com/gulp-sourcemaps/gulp-sourcemaps/issues/306
https://github.com/gulp-sourcemaps/gulp-sourcemaps/issues/304
...

I did not find anything under the wiki/readme section. Would you consider adding a note on that topic to avoid so many related issues?

@jbe456 I'm open to reviewing any PRs that add a note.


Release/v0.2.2

Pushing viz fix to main via small patch release

Will let you delete branch since you might use it for the new develop.


Parse break, continue

Should be written as flow.break() and flow.continue()

I was dumb. We already have "break", "continue", "flush"


New command: Get health status of the different services in Office 365

Usage
service status list [options]
Description
Gets health status of the different services in Office 365
Options

Option
Description

-o, --output [output]
Output type. json|text. Default text

--verbose
Runs command with verbose logging

--debug
Runs command with debug logging

Additional Information
Implemented using the REST API: https://docs.microsoft.com/en-us/office/office-365-management-api/office-365-service-communications-api-reference#get-current-status

@waldekmastykarz I really would like to help, but the last time that I tried, I had some issues putting to work :( can I get this one to test/learn the contribution path?

@douglasromao, feel free to get this one.

Feel free to reach out if you need any assistance @douglasramao 👍🏻

Setting as available due to lack of response

@waldekmastykarz @garrytrinder @VelinGeorgiev - is anyone working on this request? If not, I am happy to pick it up.

All yours @anoopt 👍🏻
Thanks for the help 😊

Hello @garrytrinder - as per the documentation, this command would need permissions to the Office 365 Management API (scope - https://manage.office.com/.default). Can you please let me know where do we specify that?

There is no need to specify it. We'll add the necessary permission to the default AAD app that we use in the CLI. When that's done, we'd update the docs to include the newly added permissions. Shall I add the permission to the AAD app already?

@waldekmastykarz - Yes please. Thank you. FYI, please find below the details of the request (if that helps)

Hello all, the ServiceComms/CurrentStatus endpoint returns JSON data as shown below. Should the Office 365 CLI command output the data in a simplified format?
{
<EMAIL_ADDRESS>"https://office365servicecomms-prod.cloudapp.net/api/v1.0/contoso.sharepoint.com/$metadata#CurrentStatus",
  "value": [
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Networking Issues",
          "FeatureName": "Networking Issues",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Sign-in",
          "FeatureName": "Signin",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "E-Mail and calendar access",
          "FeatureName": "Access",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "E-Mail timely delivery",
          "FeatureName": "Delivery",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Management and Provisioning",
          "FeatureName": "Provisioning",
          "FeatureServiceStatus": "ServiceDegradation",
          "FeatureServiceStatusDisplayName": "Service degradation"
        },
        {
          "FeatureDisplayName": "Voice mail",
          "FeatureName": "UnifiedMessaging",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "Exchange",
      "IncidentIds": [
        "EX207367"
      ],
      "Status": "ServiceDegradation",
      "StatusDisplayName": "Service degradation",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "Exchange",
      "WorkloadDisplayName": "Exchange Online"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Service",
          "FeatureName": "service",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Form functionality",
          "FeatureName": "functionality",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Integration",
          "FeatureName": "integration",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "Forms",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "Forms",
      "WorkloadDisplayName": "Microsoft Forms"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Kaizala Messaging",
          "FeatureName": "kaizalamessaging",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Kaizala Management Portal",
          "FeatureName": "kaizalaportal",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "kaizalamessagingservices",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "kaizalamessagingservices",
      "WorkloadDisplayName": "Microsoft Kaizala"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Audio and Video",
          "FeatureName": "AudioVideo",
          "FeatureServiceStatus": "ServiceDegradation",
          "FeatureServiceStatusDisplayName": "Service degradation"
        },
        {
          "FeatureDisplayName": "Federation",
          "FeatureName": "Federation",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Management and Provisioning",
          "FeatureName": "ManagementandProvisioning",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Sign-In",
          "FeatureName": "Sign-In",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "All Features",
          "FeatureName": "All",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Dial-In Conferencing",
          "FeatureName": "DialInConferencing",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Online Meetings",
          "FeatureName": "OnlineMeetings",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Instant Messaging",
          "FeatureName": "InstantMessaging",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Presence",
          "FeatureName": "Presence",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Mobility",
          "FeatureName": "Mobility",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Cloud PBX",
          "FeatureName": "CloudPBX",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "PSTN Calling",
          "FeatureName": "PSTNCalling",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Meeting Broadcast",
          "FeatureName": "MeetingBroadcast",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "Lync",
      "IncidentIds": [
        "LY206705"
      ],
      "Status": "ServiceDegradation",
      "StatusDisplayName": "Service degradation",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "Lync",
      "WorkloadDisplayName": "Skype for Business"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Service and web access issues",
          "FeatureName": "Service",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "MicrosoftFlow",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "MicrosoftFlow",
      "WorkloadDisplayName": "Microsoft Power Automate"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Service and web access issues",
          "FeatureName": "Service",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "MicrosoftFlowM365",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "MicrosoftFlowM365",
      "WorkloadDisplayName": "Microsoft Power Automate in Microsoft 365"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Teams Components",
          "FeatureName": "TeamsComponents",
          "FeatureServiceStatus": "ServiceDegradation",
          "FeatureServiceStatusDisplayName": "Service degradation"
        }
      ],
      "Id": "microsoftteams",
      "IncidentIds": [
        "TM207342",
        "TM207796"
      ],
      "Status": "ServiceDegradation",
      "StatusDisplayName": "Service degradation",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "microsoftteams",
      "WorkloadDisplayName": "Microsoft Teams"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Mobile Device Management",
          "FeatureName": "MobileDeviceManagement",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "MobileDeviceManagement",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "MobileDeviceManagement",
      "WorkloadDisplayName": "Mobile Device Management for Office 365"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Office Client issues",
          "FeatureName": "OfficeClient",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "O365Client",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "O365Client",
      "WorkloadDisplayName": "Office Client Applications"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Excel Online",
          "FeatureName": "excelonline",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "OneNote Online",
          "FeatureName": "onenoteonline",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "PowerPoint Online",
          "FeatureName": "powerpointonline",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Word Online",
          "FeatureName": "wordonline",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Visio Online",
          "FeatureName": "visioonline",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "officeonline",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "officeonline",
      "WorkloadDisplayName": "Office for the web"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "OneDrive for Business",
          "FeatureName": "OneDrive for Business",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "OneDriveForBusiness",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "OneDriveForBusiness",
      "WorkloadDisplayName": "OneDrive for Business"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Sign-In",
          "FeatureName": "authentication",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Administration",
          "FeatureName": "administration",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "OrgLiveID",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "OrgLiveID",
      "WorkloadDisplayName": "Identity Service"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Portal",
          "FeatureName": "Portal",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Administration",
          "FeatureName": "Administration",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Purchase and Billing",
          "FeatureName": "PurchaseAndBilling",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "OSDPPlatform",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "OSDPPlatform",
      "WorkloadDisplayName": "Office 365 Portal"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Licensing and Renewal",
          "FeatureName": "LicensingRenewal",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Network Availability",
          "FeatureName": "networking",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Office Professional Plus Download",
          "FeatureName": "officedownload",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "OSub",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "OSub",
      "WorkloadDisplayName": "Office Subscription"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Planner",
          "FeatureName": "Planner",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "Planner",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "Planner",
      "WorkloadDisplayName": "Planner"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Service and web access issues",
          "FeatureName": "Service",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "PowerAppsM365",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "PowerAppsM365",
      "WorkloadDisplayName": "Power Apps in Microsoft 365"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Provisioning",
          "FeatureName": "provisioning",
          "FeatureServiceStatus": "ServiceDegradation",
          "FeatureServiceStatusDisplayName": "Service degradation"
        },
        {
          "FeatureDisplayName": "SharePoint Features",
          "FeatureName": "spofeatures",
          "FeatureServiceStatus": "RestoringService",
          "FeatureServiceStatusDisplayName": "Restoring service"
        },
        {
          "FeatureDisplayName": "Tenant Admin",
          "FeatureName": "tenantadmin",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Search and Delve",
          "FeatureName": "search",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Custom Solutions and Workflows",
          "FeatureName": "customsolutionsworkflows",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Project Online",
          "FeatureName": "projectonline",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Office Web Apps",
          "FeatureName": "officewebapps",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "SP Designer",
          "FeatureName": "spdesigner",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "Access Services",
          "FeatureName": "accessservices",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        },
        {
          "FeatureDisplayName": "InfoPath Online",
          "FeatureName": "infopathonline",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "SharePoint",
      "IncidentIds": [
        "SP207180",
        "SP207374",
        "SP207734"
      ],
      "Status": "ServiceDegradation",
      "StatusDisplayName": "Service degradation",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "SharePoint",
      "WorkloadDisplayName": "SharePoint Online"
    },
    {
      "FeatureStatus": [
        {
          "FeatureDisplayName": "Sway",
          "FeatureName": "Sway",
          "FeatureServiceStatus": "ServiceOperational",
          "FeatureServiceStatusDisplayName": "Normal service"
        }
      ],
      "Id": "SwayEnterprise",
      "IncidentIds": [],
      "Status": "ServiceOperational",
      "StatusDisplayName": "Normal service",
      "StatusTime": "2020-03-26T00:00:54.0547782Z",
      "Workload": "SwayEnterprise",
      "WorkloadDisplayName": "Sway"
    }
  ]
}

I'd suggest that we follow the typical setup where in the text format we return a subset information and then the complete object is sent to output in json mode. For text mode, workload display name, feature display name and status display name would be enough.

@anoopt https://manage.office.com/.default is not a permission scope you can grant. The docs mention ServiceHealth.Read. Is that the right scope?

@waldekmastykarz - Yes ServiceHealth.Read permission is what we need. Sorry for not mentioning it before.


[BUG REPORT] Sometimes the 20 mins timeout for wait_for_repo is exceeded

Bug report
Impacted system

EDAMAME Security App

Expected vs actual behavior
Sometimes the 20 mins timeout for wait_for_repo is exceeded. Likely the test for access needs to be improved/changed.
Steps to reproduce
Versions
Screenshots (if relevant)
Additional information

The integrated checkout fixes this.


[WIP] Upgraded tabs

Fixes #1267 and fixes #1268

btw we'll need an implementation with swipable tabs.. I can look into it parallely if u want

Sure

But aren't they swipeable already?

These are just TabBar.. we need to have like full fledged tabs(with content)

Most things are fixed with just one small bug left (at least from what I've found)

Okay and a major one. Active tabs are making some problems

I was having architectural problems with how to test the active tab.
Setting a Tab active does not work with the state management of mdc and setting it on Tabs makes Problems with the styles on the active Tab. And also time...

The netlify preview is broken somehow, I guess preact-render-to-string has to be added to dev-dependencies in the docs since the cli update

deploy preview is fixed

Looks quite quite good I'll fix a few small thing and then it's good to go

@cromefire i plan to upgrade all deps after this pr and publish an alpha. WDYT?

Seems fine

Hi! I am speaking about Preact Ecosystem changes on http://reactindia.io.
Would like to publish an alpha before that WDYT?

I'm fine with that just keep in mind that you still wanted to implement the tab content things

It kinda tough, i'll try doing it in beta may be

i just wanted to use nuka carousel but isnt straight forward

so the alpha wont have the swipable tabs for now

Do we even have non swipable tabs right now?

Also so I would like to keep this in alpha until we have all the features

(but of course there can be multiple alpha versions)

Yes totally aligned, all I am aiming for is alpha1

Well then go for it

wopuld like to get this PR in for alpha 1

Nobody is stopping you

Lol the WIP was blocking me 😛

That's the purpose of it

Thanks for working on this.. will check the tests and probably merge it


🐞 [Bug]: Grid cli getting an error while deleting all contracts

What happened?
gridcli getting an error when deleting all contracts but working fine in one contract.
also fails to delete while deleting by solution name tfcmd cancel <deployment-name>
go version go1.21.6 darwin/arm64
the binary v0.15.1

(no contracts were deleted )
which network/s did you face the problem on?
Dev, QA
Twin ID/s
No response
Node ID/s
No response
Farm ID/s
No response
Contract ID/s
No response
Relevant log output
10:46AM FTL error="all not a valid contract id: strconv.ParseUint: parsing \"all\": invalid syntax"

Where is all param documented? To me the error sounds like it needs a uint, also please "getting error in the title isn't enough"
Component: summarized error eg tfcmd: all is invalid argument in canceling contracts

I followed the documents in the deletion process and i found all pram but I missed the -- but it still miss behaves some time
tried it again now and it worked

(contracts are deleted but got the same error as mentioned here)

for deleting a unit per time it did not work and always misbehaving  like this :
here is a contract for the vm called kube :

it should be canceled like documented here :

open the issue problem you have with --all please in a new ticket i'll close this one


[Request] Output to stdout

Thank you for the amazing tool. One request for the team. Could it be possible to send the output to stdout instead to a file? A lot of times the space on the disk is smaller than the size of the memory, and compress is not enough. Currently I am using CIFS, S3FS or mounting an additional volume into the VM and format it to be able to dump into an external storage that it is mounted locally. However this creates unwanted artefacts.
If I was able to send output to stdout, I could pipe it to any of the tools to transfer files without touching disk: rsync, aws s3, scp, etc; Thank you!
NOTE: aware of the risk of delaying the memory acquisition due to dumping to an external device, but usually if same data center we are talking about 150-100 mb/s

@moxilo, you should be able to use /dev/stdout as the output file, which enables sending the output to stdout instead of a file.
I've used this method to acquire memory from remote machines over an SSH session.

Thanks for the answer. I tried via /dev/stdout by AVML behaviour is erratic.
This works:
echo "joaquin test" | /usr/bin/aws s3 cp --expected-size 13 - s3://asdf/test1.avml --acl bucket-owner-full-control

This also:
SIZE=$(du -b /bin/ls | awk {'print $1'})
cat /bin/ls | /usr/bin/aws s3 cp --expected-size $SIZE - s3://asdf/test2.avml --acl bucket-owner-full-control

However, when I try with AVML:
grep MemTotal /proc/meminfo | awk '{print $2 * 1024}'
32655360000
./avml  --compress /dev/stdout | /usr/bin/aws s3 cp --expected-size<PHONE_NUMBER>0 - s3://asdf/test3.avml --acl bucket-owner-full-control
(immediate crash)
unable to read memory
/dev/crash failed: unable to create image. source:/dev/crash destination:/dev/stdout

Caused by:
    0: unable to open source file: /dev/crash
    1: No such file or directory (os error 2)
/proc/kcore failed: unable to copy block: 4096..651264

Caused by:
    0: unable to copy block: 4096..651264
    1: unable to seek to location
    2: Invalid seek (os error 29)
/dev/mem failed: unable to write block: 4096:654335

Caused by:
    0: unable to copy block: 4096..654335
    1: unable to copy block: 4096..654335
    2: unable to seek to location
    3: Invalid seek (os error 29)
Error: unable to collect memory

Caused by:
    unable to read physical memory

and without compress:
./avml  /dev/stdout | /usr/bin/aws s3 cp --expected-size<PHONE_NUMBER>0 - s3://asdf/test4.avml --acl bucket-owner-full-control
(it crashes after a while)

Manual dump worked:
./avml /dev/stdout >> test.txt

Can you try avml --compress --source /proc/kcore /dev/stdout | aws s3 cp ...

As I hinted in my previous comment, I identified a potential problem when writing to /dev/stdout without specifying a source.  This may be partially responsible for the instability you were seeing.
If the user doesn't specify a source, avml iterates over /dev/crash, /proc/kcore, and /dev/mem to attempt to read memory.  If one fails, it starts over and tries the next one on the list.  With any other output file, this is fine (and preferred, given some of the 3rd party kernel lockdown patches I've come across)
PR https://github.com/microsoft/avml/pull/35 should address the concern I identified.

Specifying the output worked for me. We are now checking if kcore is available, and if it is, we run against kcore. If it is not available, we run against crash.  I have not tested yet 0.4.1 to see if fix the problem, I will test it tomorrow (sorry for the delay)

We have tested with 0.3 binary provided in the repo and we have compile the last available version (0.4.1) with same results. When /dev/stdout is used with compress, it fails:

Work: avml --source /proc/kcore /dev/stdout
Does NOT work: avml --source /proc/kcore --compress /dev/stdout >> image.raw
Work: avml --source /proc/kcore /dev/stdout | aws s3 cp  ...
Does NOT work: avml --source /proc/kcore --compress /dev/stdout | aws s3 cp  ...

Example:
sudo ./avml --compress --source /proc/kcore /dev/stdout
AVML?Error: unable to collect memory

Caused by:
    0: unable to copy block: 4096..647168
    1: unable to copy block: 4096..647168
    2: unable to seek to location
    3: Invalid seek (os error 29)

Interesting.  Can you share the VM instant type and /proc/iomem?  I'd like to dig into that more.  I've not seen that in any of the VMs I've interacted with thus far.

Yes sure:
# uname -r
5.10.68-62.173.amzn2.x86_64
# cat /etc/image-id
image_name="amzn2-ami-kernel-5.10-hvm"
image_version="2"
image_arch="x86_64"
image_file="amzn2-ami-kernel-5.10-hvm-2.0.20211103.0-x86_64.xfs.gpt"
image_stamp="8c91-3a82"
image_date="20211108205243"
recipe_name="xxxx"
recipe_id="xxxxx"
# curl http://<IP_ADDRESS>/latest/meta-data/ami-id
ami-097607527741dc147
# curl http://<IP_ADDRESS>/latest/meta-data/instance-type
m1.large
#

# cat /proc/iomem
00000000-00000fff : Reserved
00001000-0009dfff : System RAM
0009e000-0009ffff : Reserved
000a0000-000bffff : PCI Bus 0000:00
000c0000-000c8bff : Video ROM
000e0000-000fffff : Reserved
  000f0000-000fffff : System ROM
00100000-efffffff : System RAM
  01000000-01c02fb6 : Kernel code
  01e00000-024bcfff : Kernel rodata
  02600000-02f371ff : Kernel data
  03548000-03bfffff : Kernel bss
f0000000-fbffffff : PCI Bus 0000:00
  f0000000-f1ffffff : 0000:00:02.0
  f2000000-f2ffffff : 0000:00:03.0
    f2000000-f2ffffff : xen-platform-pci
  f3000000-f3000fff : 0000:00:02.0
fc000000-ffffffff : Reserved
  fec00000-fec003ff : IOAPIC 0
  fed00000-fed003ff : HPET 0
    fed00000-fed003ff : PNP0103:00
  fee00000-fee00fff : Local APIC
100000000-1efffffff : System RAM

And taking System RAM, total 7.5GB of ram which it is what we see:
>>> a = 0x0009dfff - 0x00001000
>>> b = 0xefffffff - 0x00100000
>>> c = 0x1efffffff - 0x100000000
>>> (a + b + c) / 1024 / 1024
7679.613278388977
>>> (a + b + c) / 1024 / 1024 / 1024
7.499622342176735

@moxilo, can you try PR #48?
You should be able to get pre-built artifacts from our ADO pipeline.

@bmc-msft thank you for working on this. Yes changing seek by counter did the trick. It is working now. Thank you


Re-design default list of images handling in Katib

Description
Currently, katib-controller has default images hardcoded in the source code of the charm. PR: https://github.com/canonical/katib-operators/pull/98
In order to simplify maintenance of list of default images it is better to have default images in a separate file that can be loaded by charm. In similar fashion as it was done in Seldon https://github.com/canonical/seldon-core-operator/pull/192
Solution
Added separate JSON file with list of default images and populate datastructures in the charm using this file.

This issue was fixed by this PR: https://github.com/canonical/katib-operators/pull/133
Closing.


[✨] Automatic unwrap template binding variables which use useSignal

Is your feature request related to a problem?
It'd be more convenient to have automatic unwrap variables which use useSignal just like Vue ref when using a reactive variable in JSX template.
Describe the solution you'd like
Just like Vue where we can use directly inputRef in JSX template without explicitly .value
import { component$, useSignal } from<EMAIL_ADDRESS>
interface MyComponentPropsInterface {
  showInput: boolean;
}

export const MyComponentLite = component$(
  (props: MyComponentPropsInterface) => {
    const inputRef = useSignal<HTMLInputElement>();

    return (
      <div>
        {props.showInput ? <input ref={inputRef} onChange$={() => inputRef.focus()}></input> : null}
        Hello
      </div>
    );
  }
);

In this example, inputRef is used in JSX template without .value, which is the ideal way to go IMO.
See Vue example at https://vuejs.org/guide/essentials/template-refs.html#accessing-the-refs
Describe alternatives you've considered
I don't have any alternatives.
Additional context
No response

I dont understand what it's being proposed in Vue you do this:
onMounted(() => {
  input.value.focus()
})

Hi, I've edited the example codes by adding onChange$ listener. Would you please take a look? The proposal is developers don't have to do inputRef.value.focus() when using the reactive variable in JSX template.

I am not sure how this proposal could be implemented, the problem is that primitive values cant not be dynamic, a signal is basically a pointer to a value, whenever the pointer changes to a different value the reactivity happens.
I understand that .value is a bit extra work, but i am not sure how it could be done otherwise.


Wrong dependency resolution when using dynamic versions

While using Gradle 4 with native dependency locking we found out an issue, given the following example we found out gradle prefers static versions over dynamic ones.
Lets say I have the following modules:
1. 'com.example:module1' -> ['1.0.0']
2. 'com.example:module2' -> ['1.0.0']
3. 'com.exampe:module3' -> ['2.0.0', '2.1.0']

And the dependency tree is as follows
com.example:module1:1.0.0
\---- com.example:module3:2.+
com.example:module2:1.0.0
\---- com.example:module3:2.0.0

Expected Behavior
The expected behavior would be for gradle to resolve module3 with version 2.1.0 since is the latest
Current Behavior
Currently, Gradle resolves module3 as 2.0.0 since module2 defines it explicitly
Context
The issue occurs while running dependencies for the module as well as locking the dependencies
Steps to Reproduce (for bugs)

Use a structure similar to the one posted above
Run dependencies

Your Environment
Gradle version: 4.9

Duplicate of #6102, which was fixed in 4.10.

Actually, when dependency locking is enabled this issue persists in 4.10. See #6340.


 With one minor exception, these are simple DaemonIsLinux requirement removals. The other is a simple switch to using the minimal base image for the platform.
Some of the tests are very expensive in terms of time, but it's better to get decent coverage, and the time on RS1 is a lot better than it was back in TP4 and TP5 days.

LGTM :+1:

Oops :panda_face:
09:36:57 # github.com/docker/docker/integration-cli
09:36:57 .\docker_cli_build_test.go:4088: undefined: name
09:36:57 .\docker_cli_build_test.go:4091: undefined: name
09:36:57 FAIL	github.com/docker/docker/integration-cli [build failed]

Huh! OK, fixing...


App building but not working on PowerPC: GUI is “frozen”

@ArthurSonzogni I built the same app (v. 1.1) on Sonoma aarch64 and Snow Leopard ppc, and in the latter case GUI is unresponsive (static, as on the screenshot below). There are no crashes or errors displayed.
Any idea what can I try to have it fixed?

I upgraded FTXUI version:
Could you please check if this improves something?
Does GDB reports a stack trace when trying to interrupt it?

@ArthurSonzogni Turned out I somewhat mischaracterized the situation. GUI is not dead, it is just not responding to clicks on it (as it does on Sonoma). From keyboard I was able to move sliders, and colors change. Does not look overly usable still due to how colors are displayed, but it is not broken, as I thought initially.

P. S. I actually used FTXUI lib which we have it MacPorts: https://github.com/macports/macports-ports/blob/cf2aa331b84e43ab897c546f2e1896d13cb4c668/graphics/rgb-tui/Portfile
Could you make a new release of FTXUI, maybe v. 5.0.1? MacPorts folks do not like commit-based versions, especially when the port already used a release.

The terminal should advertise itself as supporting 256 colors, otherwise, FTXUI will fallback toward the "closest" color available.
This can be done with:
export TERM=xterm-256color

or
export COLORTERM=truecolor

Does this appears to be good enough for you?
I can also "force" FTXUI to output the true colors, but users of incompatible terminal will see some black colors instead of the fallback ones.

Could you make a new release of FTXUI, maybe v. 5.0.1? MacPorts folks do not like commit-based versions, especially when the port already used a release.

The next version will be 6.0.0. I would like to avoid introducing a new breaking release too often.
Why do you need a new version in MadcPorts?

@ArthurSonzogni If 5.0.0 is good enough for all apps which use it, no need to introduce anything. I just thought that update you mentioned implied an update to FTXUI itself.
Env variables should be good, perhaps rather not force any specific setting for all users. I will try setting colors once back to the PowerMac.
Support for mouse events is something SDK-related, so it won’t work on earlier OS? No big deal, just to confirm.

@ArthurSonzogni Setting either of env variables makes it looks really strange for me :)
This is with truecolor:

Your terminal probably doesn't support true colors. That's why it doesn't set those variable. That's why FTXUi fallback toward the "closest" supported colors.
Does it make sense?

Your terminal probably doesn't support true colors. That's why it doesn't set those variable. That's why FTXUi fallback toward the "closest" supported colors.
Does it make sense?

Oh okay, looks like Apple Terminal had no true color up to very recently (or maybe still does not have it): https://stackoverflow.com/questions/6403744/are-there-terminals-that-support-true-color
Then no surprise, indeed.
I will look for some feasible alternative, I want to see how it works at least.

@ArthurSonzogni I can confirm it works in vte:

Sorry for the false alarm, there is no problem on rgb-tui side at all.


removing Duplicate

Related Issue

removing duplicate elements from sorted array

Solved: #100
Describe the changes you've made
i had given a solution of this in C++.
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Language used for coding
C++
Checklist:

[x ] My code follows the style guidelines of this project.
[ x] I have performed a self-review of my own code.
[ x] I have commented my code, particularly in hard-to-understand areas.
[ x] I have made corresponding changes to the documentation.
[ x] New and existing unit tests pass locally with my changes.

@Nivedita967  check my pull request .

Your folder name is "Contains Duplicate" but always write folder name by the exact name of problem as on coding platform. Check that exact name is "Remove Duplicates from Sorted Array" rename your folder.

@Nivedita967  check it now

Now this is perfect :)

thanks XD


The refresh button is not displayed when we use a local archive

Describe the bug
In the configuration page, when we use the local archive option, the button "Refresh the page" is not displayed after Clicking "Save".
We should refresh the page manually, so this button is displayed.

Upgrade environment (please complete the following information):

Version you started from: <IP_ADDRESS> / <IP_ADDRESS>
Version you upgrade to: <IP_ADDRESS>
Way of upgrade: Local archive

Expected behavior
When we click on "save" => the button "Refresh the page" should be automatically displayed.
Screenshots
https://drive.google.com/file/d/1mJZwWZVm2WRNWDnXJQ8fCS_K_R4Powbn/view
Server (please complete the following information):

Web Server: Apache
PHP Version: <IP_ADDRESS> / <IP_ADDRESS>
Module Version: 4.4.0

Additionally, the javascript should manage the autoreload automatically.
Hint:
the problem lies in the afterUpdateConfig when calling showConfigResult with a type (undefined), this check doesn't work:
if (type === null) {
    type = "conf";
  }

Fixed by #187. Thanks.


License

Can this project be used for commercial use?
EDIT: Is the Apache License the one for this repo or is it for another repo?

After digging around on the internet, I am going to assume that the license is Apache 2.0.


add random access range member functions to bit_span

Change-Id: I765c657b65dfa246b67e20c73c90f05c9b49c5c3

Codecov Report

:exclamation: No coverage uploaded for pull request base (I34772c33111e073f58d75c7949bea68dc232353a@1ebc412). Click here to learn what that means.
The diff coverage is 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@                             Coverage Diff                              @@
##             I34772c33111e073f58d75c7949bea68dc232353a      #85   +/-   ##
============================================================================
  Coverage                                             ?   99.57%
============================================================================
  Files                                                ?       11
  Lines                                                ?      237
  Branches                                             ?        0
============================================================================
  Hits                                                 ?      236
  Misses                                               ?        1
  Partials                                             ?        0

Files Changed
Coverage Δ

huffman/src/detail/iterator_interface.hpp
100.00% <ø> (ø)

huffman/src/bit_span.hpp
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Feature Request:  Update compute_duration function to have "min" and "sec" for output units

Feature Idea
Roche uses controlled terminology for any derivation with unit of duration, this controlled terminology is the same as used by SDTM variables.
For "seconds" the controlled terminology is "sec" and for "minutes" its "min".
Relevant Input
For compute_duration for units of minutes the function outputs "minutes" and for seconds the function outputs "seconds"
Relevant Output
For compute_duration for units of minutes the function should output "min" and for seconds the function should output "sec"
Reproducible Example/Pseudo Code
No response

@esimms999-gsk @bms63 can you check if GSK uses controlled terminology for ADaM derivations related to units of duration. If not can you check what controlled terminology is used for SDTM variables relating to unit of duration?

I've only seen "Study Specific" in our derivations for units of duration.  Let's go with the standard practice and make this enhancement.  We can always fix it internally at GSK if I am in wrong here.
I think this would be a good first issue as well.

@imaheshdivakaran We'd like to include this in our release next month. Can you get this done by then?

Hi @pharmaverse/admiral  Can anyone pick up this issue please?

It looked a similar change was needed for derive_vars_duration() to be consistent, so I updated that as well.  Based on previous discussion pharmaverse/admiraldev#122 it looks like valid_time_units() would not be updated since only the out_unit is affected.


rfc: remove or allow dotenv configuration in from_env

In the LitestarEnv.from_env method, we attempt to use the dotenv configuration if it's there.
This is helpful, however, there are cases where you'd like to skip this execute or execute with a different env_file path or stream.
We should consider enhancing or removing this functionality for 3.0
https://github.com/cofin/litestar/blob/af24784bbb3d584226ba39c323b021701fbb0678/litestar/cli/_utils.py#L105-L108

[!NOTE]
While we are open for sponsoring on GitHub Sponsors and
OpenCollective, we also utilize Polar.sh to engage in pledge-based sponsorship.
Check out all issues funded or available for funding on our Polar.sh dashboard

If you would like to see an issue prioritized, make a pledge towards it!
We receive the pledge once the issue is completed & verified
This, along with engagement in the community, helps us know which features are a priority to our users.

It's actually called automatically during the boot-up process of the CLI.


VectorTest.findDuplicateValue fails in CircleCI

Bug description
https://app.circleci.com/pipelines/github/facebookincubator/velox/24798/workflows/5015a9f8-2014-4a70-8f50-03d51c196b5a/jobs/157242/tests
System information
CircleCI
Relevant logs
../../velox/vector/tests/VectorTest.cpp:2325
Failed
Expected an exception

cc @mbasmanova

The check that is supposed to throw is a debug-only check. Hence, it doesn't throw in release builds. I'm going to remove this test.


Create: 424-Longest-Repeating-Character-Replacement.ts

File(s) Modified: 424-Longest-Repeating-Character-Replacement
Language(s) Used: Typescript
Submission URL: _https://leetcode.com/submissions/detail/787323299/_

Thanks, @andra961!


[RESEARCH] MediaCollection

I think I've found a way to send any file to chats. But we need more research before be able to send anything. DO NOT EXCITE, yet.
There is a class I call MediaCollection used to prepare files before send to a chat. We could get it from module "dhcbbcecif". I don't know how to add to autodiscovery.
var mediaCollection = new modules["dhcbbcecif"].exports();

This object has a method to add more files to collection called processFiles. So we could use Blobs in order to add new files.
mediaCollection.processFiles([myBlob],  chatObj, 1);

I guess it internally creates a Media object with all stuff it needs to send to a chat (including media keys).
Finally media object could be sent to a chat:
var mediaObj = mediaCollection.models[0];
mediaObject.sendToChat(chatObj, {})

I did not try the whole process, nor did I write any code. It is just a research.

May be we could use this for autodiscovery:
 if (module.exports.prototype.processFiles !== undefined) {...}

Well, there seems to be no interest... But it works, I'm using it on new project: https://github.com/alfred82santa/whalesong/blob/master/js/src/whalesong/chat.js#L118
You can try to adapt code for mukulhase/WebWhatsapp-Wrapper

@alfred82santa this definitely has my interest, please keep it going.

feel free to test this feature: https://github.com/alfred82santa/whalesong#minibot

https://github.com/mukulhase/WebWhatsapp-Wrapper/pull/300


bump falcosidekick

What type of PR is this?
Any specific area of the project related to this PR?
What this PR does / why we need it:

bump falcosidekick

Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Checklist

[ ] Chart Version bumped
[ ] Variables are documented in the README.md
[ ] CHANGELOG.md updated

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [cpanato]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@leogr: Closed this PR.

In response to this:

Closing and reopening to wake up tide
/close

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

@leogr: Reopened this PR.

In response to this:

/reopen

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

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [cpanato,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: b71bdf74c6d1210334cc8e06954eb8bfaf50dcf7

/hold

/hold cancel


[AutoDiff upstream] Add @derivative(of:) attribute.

The @derivative(of:) attribute registers a function as a derivative of another function.
This patch adds the @derivative(of:) attribute definition, syntax, parsing, and printing.
Resolves TF-826.
Todos:

Type-checking (TF-829).
Serialization (TF-837).

cc @rxwei @marcrasi @bgogul

I addressed all comments and rebased onto master.
There are no major changes: the biggest syntax change is renaming @differentiating to @derivative(of:), which has already been done on tensorflow branch: https://github.com/apple/swift/pull/28481.

@swift-ci Please test
https://github.com/apple/swift-syntax/pull/188

@swift-ci Please test
apple/swift-syntax#188

apple/swift-syntax#188
@swift-ci Please test

Build failed
Swift Test Linux Platform
Git Sha - 9acdfba49cc212523c0224a44a4da95bfb2e760e

Build failed
Swift Test OS X Platform
Git Sha - 9acdfba49cc212523c0224a44a4da95bfb2e760e

Merging since there are no major changes since the last approval and CI has passed.


Chapter 13 solution no longer working

https://github.com/kyclark/command-line-rust/blob/e977e5b1412bb3cd20737465d61f0baca05536d3/13_calr/src/lib.rs#L98
This line currently fails with an error message like:
error[E0277]: `&()` is not an iterator
   --> src/lib.rs:100:40
    |
100 |                     for lines in izip!(m1, m2, m3) {
    |                                  ------^^---------
    |                                  |     |
    |                                  |     `&()` is not an iterator
    |                                  required by a bound introduced by this call
    |
    = help: the trait `Iterator` is not implemented for `&()`
    = note: required for `&()` to implement `IntoIterator`

@kennethlove FWIW, this is what I get from running cargo run to build 13_calr (commit e977e5b1412bb3cd20737465d61f0baca05536d3) using Rust 1.74.1:
$ cargo run
warning: use of deprecated associated function `chrono::Local::today`: use `Local::now()` instead
  --> src\lib.rs:64:24
   |
64 |     let today = Local::today();
   |                        ^^^^^
   |
   = note: `#[warn(deprecated)]` on by default

warning: use of deprecated associated function `chrono::NaiveDate::from_ymd`: use `from_ymd_opt()` instead
   --> src\lib.rs:176:16
    |
176 |     NaiveDate::from_ymd(y, m, 1).pred()
    |                ^^^^^^^^

warning: use of deprecated method `chrono::NaiveDate::pred`: use `pred_opt()` instead
   --> src\lib.rs:176:34
    |
176 |     NaiveDate::from_ymd(y, m, 1).pred()
    |                                  ^^^^

warning: use of deprecated associated function `chrono::NaiveDate::from_ymd`: use `from_ymd_opt()` instead
   --> src\lib.rs:186:28
    |
186 |     let first = NaiveDate::from_ymd(year, month, 1);
    |                            ^^^^^^^^

warning: `calr` (lib) generated 4 warnings
    Finished dev [unoptimized + debuginfo] target(s) in 0.05s
     Running `target\debug\calr.exe`
   February 2024
Su Mo Tu We Th Fr Sa
             1  2  3
 4  5  6  7  8  9 10
11 12 13 14 15 16 17
18 19 20 21 22 23 24
25 26 27 28 29

It doesn't show well here, but the 6 has an inverted terminal foreground/background color to highlight it.


Add rudimentary support for crosvm

This PR adds two new packages

github.com/intel/govmm/vmmlog
github.com/intel/govmm/crosvm

vmmlog provides an abstract logging interface that can be used by other packages in the govmm repo.  Currently, it's only used by the crosvm package but soon the qemu package will be modified to use it as well.
crosvm provides a set of data structures and methods for launching and manipulating crosvm guests.  The API support by crosvm is fairly limited and simple, when compared to qemu, so this package provides fewer features than the corresponding qemu package.
The PR makes no changes to the qemu package and so shouldn't affect any existing govmm clients.

Coverage decreased (-4.4%) to 66.813% when pulling 8334bf511eed3150ecf85d0507dca84193b4b274 on markdryan:crosvm into 82c67ab9b21e8cd0042b6c2d3be2d3705a511603 on intel:master.

Coverage decreased (-4.4%) to 66.813% when pulling 8334bf511eed3150ecf85d0507dca84193b4b274 on markdryan:crosvm into 82c67ab9b21e8cd0042b6c2d3be2d3705a511603 on intel:master.

Coverage decreased (-4.4%) to 66.813% when pulling 8334bf511eed3150ecf85d0507dca84193b4b274 on markdryan:crosvm into 82c67ab9b21e8cd0042b6c2d3be2d3705a511603 on intel:master.

I'm not actively working on this right now so will close.  We can update it in the future if anyone needs this.


Coverage pool in KEEP Token Dashboard

Depends on: #2522
This is an integration PR for the coverage pool in KEEP Token Dashboard.

Prototype

Rafał, I created this small PR with update of the dependency to the coverage-pools project: https://github.com/keep-network/keep-core/pull/2563 (we have the cov-pools already published to the NPM registry, so we no longer need to refer to the local file).


Quality

Change quality via config

Thanks!

is it me or this PR is not available in any tagged version ?


Mounting when "Rider can move freely" does not snap to grid

Possibly this isn't a bug but just a design choice, but it seems wrong to me.
When a grid is in place, tokens will snap to them (at least in my settings, possibly this is not the default case, though I think it is).
When mounting a mount which has the "riders can move freely" option set, the rider gets moved onto the mount, but the movement stops in an awkward position, rather than snapping to one of the available grid positions on the mount.

If you then try to manually move the rider token, it will snap into the grid properly.

I forgot about grids, since all my games use gridless maps. In v.2.0.0 correct snapping will be implemented (at least for square grids)

Now improved with v2.0.0

I am not seeing any difference in 2.0.1 in v10, gridded.  It continues to not snap to the grid, and stops the token half on and half off the mount somewhere around the boundary.

It seems the previous enhancement i implemented does not work for Foundry v10 (which is rather strange). I will look into it

The bug is now fixed with v2.1.0, thanks again for all the bug reports and suggestions.


Start testing the translator through CPython tests

[ ] Find the most simple tests from #22
[ ] Remove unsupported instructions
[x] Create test case in Tests.scala
[ ] Check test output in EO

Current progress and results:

exploring test initialization in Scala
working with current assertion in immutabilization test
fixed crash before test assert

@PetrB09 what did you mean with point - remove unsupported instructions. Is it connected with the most simple test from mentioned ticket or removing such instructions from the current repository version?

For testing was selected this test

Current status:

added test with translator usage
added .py file for testing which contains all supported constructions
small refactoring of existing test for immutabialization

more info is in the commit

see #22

#49  tests parser and printer with 364 of the cpython tests


Migaloo v2

Migaloo v2 tracking issue
The key feature of v2 is alliance.  Any other features are nice-to-have at this stage.
Features:

[ ] Alliance

Fixes:

[ ] State sync

Nice-to-haves:

[ ] async-icq
[ ]  bump wasmd to v0.31.x-4611

NOTE

cosmos-sdk v0.46.11 uses comet v0.34.27, and currently there's no version of skip for this.  I'm checking with the Skip team currently.

Shall we squeeze in the updated token factory https://github.com/osmosis-labs/osmosis/pull/4417 @faddat?

Is notional wasmd the only one that works with sdk 46?

Yes.


Update Turing dep

Any reason not to bump support for this to allow Turing 0.15?

Just checked, and nope! Good to go.


feat/signup

Changelog

fix eslint not recognizing styled-system from panda css by allowing the commons option on eslint config.

https://stackoverflow.com/questions/63804747/how-to-generate-and-set-jwt-secret-and-jwt-expiration-time-in-express

The other users have already answered the question of how to set JWT_SECRET, and I'll add how to generate it. slebetman gave good advice to generate the string using password generators (they exist both separately and as part of most password managers). For this purpose, I usually use the following command, which I simply enter into the terminal and copy it to the .env file:
openssl rand -base64 172 | tr -d '\ n'
Where 172 is the number of characters in the generated string (choose the one you want).


App exits during debug "The program '[2967] xxxxxxx.dll' has exited with code 0 (0x0)."

VSCode Version: Version: 1.53.0-insider
OS Version: macOS Big Sur 11.1 (MacBook Pro, 13 inch, M1, 2020)

Steps to Reproduce:

Open a Razor Pages project
Click on .NET Core Launch (web)

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

/causedByExtension

/causedByExtension

Please file the issue against the C# extension.

Please file the issue against the C# extension.


How to sample from HF models?

Hi, this is great great project!
I'm thinking about reproducing your scores in the paper first. Specifically from the model ContextualAI/archangel_sft_llama7b. How to sample from this HF model? Right now the eval.py takes in a path from /data/..., which exists only if I trained it myself.

You should be able to sample from it as if it were any Llama-7B based Huggingface model: https://huggingface.co/blog/how-to-generate

I was trying to find an easy way to plug HF models into your code base, just for evaluation.
I've solved my problem. Thank you.

close


error when running with profile test

I just tried running the test profile and got the following error:
nextflow run nf-core/chipseq -profile test
and received this error:
Command executed:

  check_design.py design.csv design_reads.csv design_controls.csv

Command exit status:
  1

Command output:
  (empty)

Command error:
    File "/home/ryan/.nextflow/assets/nf-core/chipseq/bin/check_design.py", line 46
      print "{} header: {} != {}".format(ERROR_STR,','.join(header),','.join(HEADER))
                                ^
  SyntaxError: invalid syntax

Do I need to provide it a design file?  or does the test download one?
Thanks!

Hi @rrdavis77 . I you just use -profile test the pipeline will assume that you have all of the software installed locally and available on your PATH. Im assuming this isnt the case. Ideally, you will need to be able to use Docker or Singularity where ever you are running the pipeline. If and when you have this setup you can run the pipeline test using:
nextflow run nf-core/chipseq -profile test,docker or
nextflow run nf-core/chipseq -profile test,singularity
The error itself is coming from the fact that the check_design.py script has been executed with Python 3 which Im assuming is installed locally. However, the pipeline requires Python 2 which is the version installed in the Docker container.
Let me know how you get on.

You will only need to run the command above to run the tests. Providing you have an internet connection where you are running the pipeline, everything will be downloaded for you.

Thank you @drpatelh !  I didn't think I could have two options under the flag profile.  It is running fine now!
Maybe the installation guide can elaborate and add the fact that you can add the docker or singularity option when running a test.  Thank you once again!

No probs. Yep, a quick start section like the one below will be rolled out in the next release :+1:
https://github.com/nf-core/mnaseseq#quick-start

If you have any further issues or comments please feel free to also ping me on the chipseq channel on the nf-core workspace.


[BUG} Contents page in readme points to dead links

Clicking on readme links doesn't point to sections anymore

Fixed!


Traffic Portal - DS Server Assignments

The old UI had a DS assigning tool that seemed easier to view/use at a glance.
The servers were nested in a visual view that grouped all servers by profile and allowed batches to be checked and selected in groups.
This made it simple to compare one DS's server assignments to another.

Under the new portal, servers have to be selected individually
When comparing two DS's, we have to parse through an entire list.
It might be useful to have a visual representation on the new Portal similar to the old UI, or perhaps even a DIFF function to compare server assignments on two DS's.
I know we have a compare feature that performs a diff on top-level DS configs, but I don't believe it goes down to the server assignment level yet.

yeah, currently in TP if you want to select ALL servers for a certain profile, you'd have to filter the list by profile name and then hit the "select all" checkbox.

Would be nice if we could clone the "server assignments" from another delivery service then. The selecting PROFILE groups in Traffic Ops was really useful.

ds/server assignments will no longer be relevant going forward as topologies will be used instead. however, orgins still need direct assignment due to MSO.


Add LhloLegalizeToLoopPass and InputInlineFusionPass to support kLoop…

Move kLoop/kInput style fusion of XLA to MLIR. This is part of work from:
mlir dynamic shape codegen.
And is intended to work with the fusion/shape inference pass in HLO layer:
add a pass to outline kLoop/kInput fusion pattern in xla_hlo dialect
The fusion codegen is seperated into two phases:
1, in LhloLegalizeToLoopPass, the (multiple) root ops is lowered into a set of nested loops.
(1) find out all the root ops and choose a legal schedule (kColReduction/kRowReduction/kLoop etc);
(2) Lower the root ops into nested loops with the selected schedule.
2, in InputInlineFusionPass, greedily perform input inline fusion on LHLO_Op->Loops patterns. The LHLO_Op is supported to be any fusible Ops in XLA codegen.

@googlebot I signed it!

@googlebot I signed it!

@googlebot I signed it!

@linearhit Can you please check @yangjunpro's comments and keep us posted. Thanks!

@linearhit Can you please check @yangjunpro's comments and keep us posted. Thanks!

I made some major revision on the schedule implementation during later works. I'll update this merge request in recent days.

@linearhit Can you please resolve conflicts? Thanks!

It has been 14 days with no activity and the awaiting response label was assigned. Is this PR still valid? Assigning the stalled label. Please comment to reassure me that this is still being worked on.

@linearhit Any update on this PR? and please resolve conflicts Thanks!

I'm going to go ahead and close this PR, because it seems to have stalled. If you're still interested in pursing this (and responding to my comments), please feel free to reopen!


Extract Hyperx from core

Depending on https://github.com/substack/hyperxify/pull/8 to be merged to move forward is not reasonable. But the truth is that even if it's not merged, hyperxify can still be used with HyperApp, it's just a little more laborious.
const { h, app } = require("hyperapp")
const hyperx = require("hyperx")
const html = hyperx(h)

app({
    model: "Hi.",
    view: model => html`<h1>${model}</h1>`
})

browserify -t hyperxify index.js -g uglifyify | uglifyjs > bundle.js

HyperApp is officially neutral in the Hyperx/template functions VS JSX debate (although the README is biased in favor of JSX on the premise that it looks "cool"), so extracting Hyperx seems a natural move.
I'll update online examples still using html via HyperApp and write the docs.

I was thought same thing. If we are just elm architecture + virtual dom + JSX, it jsut enough. It looks fancy and everyone seems to use JSX haha.

Not "breaking JS" is one of the reasons why I like hyperapp. :-1:

everyone can include hyperx and pass our h to it so he won't break HIS JS for his project :D
I was against JSX, but kinda like it now. Not sure enough, except that it is hard to write because is html :D no matter even if you have some snippets or "lanugage-*" or etc stuff on you editor. :D

@dodekeract Extracting hyperx doesn't mean HyperApp can't use template functions. The reason I want to remove hyperx is because of maintenance, hyperxify won't likely ever work with HyperApp out of the box (forcing me to fork the repo or create my own transform and tell everyone to use it).
Extracting hyperx is arguably trueer to the minimalist nature of hyperx.

With regards to breaking JavaScript

I've become ambivalent towards the debate. HyperApp lets you use whichever you like.

True, you will no longer import { html }, which was neat, but on the other hand using hyperx out of the box makes HyperApp opinionated about two things:

using template functions (HyperApp is neutral, use what you want)
using the hyperx module (what if someone writes a new html parser template function better than hyperx, should we switch? use both?)

I believe removing the hyperx dependency is a logical move.
Now let's see the biggest positive from this move:

You can start using Hyperapp in production right now, because we finally have a build setup that works and no longer need to wait for my PR to be merged (assuming it will be ha).

@tunnckoCore Jade/Pug

Let's write a Jade/Pug parser as a template function, https://www.npmjs.com/package/pugx.
Then you can use it like this:
const { h, app } = require("hyperapp")
/** @pugx h */

app({
    model: "Hi.",
    view: model => pug`h1 ${model}`
})

Haha.

Haha. Interesting and still be a cool thing to have tagged template fn for pugx instead of what hyperx returns. But i meant instead of writing raw html as JSX, to write raw pug :D, But yea space sensitivity can be awful sometimes.
Something like
const mainView = (model, actions) =>
  section.hello
    h1 {model.title}
    p Hello {model.name}

app({
    model: {  name: 'Charlike', title: 'Hello World' },
    view: mainView
})

agree with removing hyperx.
actually it's wired to use tag template string to build virtual-dom. not easy to write, also not easy to write.
however, jsx is is not bad, at least so many people ar using it, but also not good enough, because it's also kind hard to write. and bearking html with js is not problem for me.
btw, pug is a good idea, i like it for that it's quit easy to write.

@liadbiz Hyperx is not wired to use virtual-dom, you can use HyperApp too. The problem with Hyperx is its tooling, hyperxify is wired in a way that makes it impossible to use when exporting Hyperx inside HyperApp (like we were doing before).
In other words, Hyperx works better when used directly by the consumer, so it was only logical to extract it from core.

HyperApp+Hyperx+Browserify
HyperApp+JSX+Browserify

Closing as this landed in<EMAIL_ADDRESS>


Deprecation warning with Python 3.12.0b4

Describe the bug
Actually a hint, not really a bug: Experimenting with Python 3.12.0b4 gives 2 deprecation warnings:

.venv\Lib\site-packages\griffe\agents\nodes_values.py, line 21
.venv\Lib\site-packages\griffe\agents\nodes_docstrings.py", line 8

Debug logs
$ mkdocs build -v
...
DEBUG    -  mkdocstrings: Using handler 'python'
INFO     -  DeprecationWarning: ast.Ellipsis is deprecated and will be removed in Python 3.14; use ast.Constant instead
              File "C:\Zimmermann\Python\Lib\warnings.py", line 529, in _deprecated
                warn(msg, DeprecationWarning, stacklevel=3)
              File "C:\workspace\python\flaskapp\.venv\Lib\site-packages\griffe\agents\nodes\_values.py", line 21, in
                from ast import Ellipsis as NodeEllipsis
INFO     -  DeprecationWarning: ast.Str is deprecated and will be removed in Python 3.14; use ast.Constant instead
              File "C:\Zimmermann\Python\Lib\warnings.py", line 529, in _deprecated
                warn(msg, DeprecationWarning, stacklevel=3)
              File "C:\workspace\python\flaskapp\.venv\Lib\site-packages\griffe\agents\nodes\_docstrings.py", line 8, in
                from ast import Str as NodeStr

To Reproduce
Any project using mkdocs and mkdocstrings, but Python 3.12.0b4
Expected behavior
No (annoying) warning.
System (please complete the following information):

griffe version: 0.32.0
Python version: 3.12.0b4
OS: Windows 11 Enterprise 22H2

Thanks for the heads up! I'm waiting for LXML to release its v5, compatible with Python 3.12, before I can actually run CI on 3.12. And I think LXML is waiting for 3.12.0 to be released :confused:

Ah, v4.9.3 actually provides wheels for Python 3.12, great! Will then fix this ASAP :slightly_smiling_face:

@pawamoy Thank you for the immediate fix. It works fine.

Thanks for testing and confirming it works!


Make ref_slice jobs use refs to commits

Interesting, nightly failed. It does not appear it's related to this PR, so I'll merge this and look at the failure separately.


Youtube now detects this script and blocks it

Script version
5,6
Describe the bug
When the script is enabled and I try to watch a video, this screen appears:
There is now way around this screen, only if I disable the script. The thing is that im already signed in so I cant sign in "again", to confirm im not a bot.
Screenshots

Desktop (please complete the following information):

OS: Windows 11
Browser: Opera GX

This seems more of a bug, than a (deliberate) feature. Anybody else on Opera GX?


I deployed with mupx but no phantomjs.

Im getting this
stdout:
[ip] spiderable: phantomjs failed at http://abc.com/en: { [Error: Command failed: Can't open '/dev/stdin'
[ip] ] killed: false, code: 255, signal: null }
[ip] stderr: Can't open '/dev/stdin'

there was no setting related to  phantomjs when I do "init". should I need to add and if not for now if I install it manually, will it work?

If you look here at meteorD at the bottom is a link to a meteor issue with spiderable link and possible solution that might be helpful.
https://github.com/meteorhacks/meteord

yeap I fixed it with that thanks ;) btw off topic but can we manually tell phantomjs to wait like 30s or something with meteor or with mupx?

I'm thinking not currently available but possibly a useful suggestion for the newer port underway at kadirahq. Maybe there is a phantom approach that will achieve your goal like...
http://charles.lescampeurs.org/2013/07/02/phantomjs-wait-for-it


Missing .swift_version parameter in podspec

Expected behavior
When integrating this Pod into a Xcode project in swift 4.2, it should compile.
Actual behavior
It does not compile.
Steps to reproduce the behavior
Integrate this Pod into an Xcode project where the main target's swift_version is set to 4.2.
Podspec should just include the .swift_version parameter in podspec.
I just noticed, this pod doesn't take into account the UIKit renamings that occurred in swift 4.2.

I still recommend, putting the swift_version parameter into the podspec.
I noticed, you already migrated the offending classes to swift 4.2. Would you make a new release then?


Attempting to reconnect

How to disable this message after reconnect 10-15 seconds?

Could you provide more info? This notification should only display if you're disconnected, in which case we definitely want to notify you.
Closing for now until more info is provided.


Webcam cannot be found by Facebook

Version
24.07.3
What desktop?
Official MATE
Explain the issue and what happens
Facebook Live cannot see the webcam. Webcamtest.com, VLC and Youtube all have no problem seeing the webcam as video1. This problem is with both Chromium and Firefox. Firefox does ask permission but the popup shows a blank for camera options. Under camera permissions, Facebook does not show up as having asked permission.
Explain how to reproduce the bug?

What is the Expected behavior (if applicable)
Seeing camera view on the Live Prod screen
Additional context (if applicable)
No response

I looked to see, and Facebook wouldn't let me click the icon to call.

I looked back, and it looked like the person was called disabled because he was there and it was working on another person.

I use Firefox sync, so it is possible. I do not have the default; I must test another profile.


improve sass coding style

ColorKeyword: Color white should be written in hexadecimal form as #fff
ElsePlacement: @else should be placed on same line as previous curly brace
LeadingZero: 0.3 should be written without a leading zero as .3
PropertySortOrder: Properties should be ordered box-shadow, text-shadow
PseudoElement: Begin pseudo elements with double colons: ::
SingleLinePerSelector: Each selector in a comma sequence should be on its own single line
SpaceAfterComma: Commas in function arguments should be followed by a single space
StringQuotes: Prefer single quoted strings
ZeroUnit: 0px should be written without units as 0

I'm closing this issue because this project is no longer being maintained


make cleanup and pre-creation recurrence period configurable

This PR allows Jenkins operator to configure the recurrence period for cleanup and pre-creation threads.
This allows to faster cleanup and pre-creating machines, I find this setting particular useful in scenario where openstack agents are single-use (1 executor, 0 retention time) and combined with set of quick jobs (less than 1 minute or so) that are often executed. It may lead to situation when openstack plugin is not able to create new machines due to hitting limit but at the same time the already existing machines are marked for termination filling up quota. In worst case almost 10 min to get cleanup and freed up limit.
Implementation has been inspired by same issue in ec2 jenkins plugin
This PR relates to https://github.com/jenkinsci/openstack-cloud-plugin/issues/282

[x] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[x] Ensure that the pull request title represents the desired changelog entry
[x] Please describe what you did
[x] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

This would be pretty useful. Even if the jobs aren't short, when the build queue gets longer it's painful to wait 10 minutes for a VM to get removed.

Hello,
Will this pull request be merged in the next releases?
Have a great day.


Send messages

Is there a command or plugin to send a message to account or group at a specific time ?

This bot now hasn't had this plugin, you may want to make your own plugin by using this package: cron
Document for making plugin: kb2abot-cli (sorry for not using english in comment)


Release to OSSRH staging repository

[x] Uptake new Eclipse versions of dependencies. Use GlassFish 5.1 Release Tracker wiki to find components versions to use.

[x] Release to OSSRH staging repository

[x] Update GlassFish 5.1 Release Tracker with released version number.

How to release first versions of EE4J components

See in it staging:
https://oss.sonatype.org/content/groups/staging/com/sun/xml/ws/jaxws-ri/2.3.2/
Closing.


Deferred properties

Defer parsing certain properties until accessed.
This will only generate properties if accessed when not set, will also clear them on exec call.
Also, some minor performance changes (opcode counting, etc).

Should resolve #313

Gah, I keep forgetting all sorts of bitty things.  Full disclosure: no, I didn't test, yes, I am using Travis to test.

About time...  You and your tests...  :-D

@zachborboa - Ok, it seems Travis is having a stroke right now.  Again with nginx not behaving in hhvm, I would consider that last test as passing.

@zachborboa - Were there questions of concerns about this PR?

Thank you for the pull request. Some of these changes have now been incorporated.


Validate before insert that all fields are existing

In NoSQL implementations, it's possible to insert fields that's not exist in the schema and that's causing problems later.
Need to add validation before insert and allow insert only to existing fields in schema.

prepareForInsert cover that case.
The bug was because the user added a new column, and inserted data into it and the Wix site didn't refresh, so it didn't execute another schemas/list, and the collection schema wasn't updated.
After refreshing, the site executed another schemas/list and the message disappeared.


[SPARK-44553][BUILD][3.4] Ignoring connect-check-protos logic in GA testing

What changes were proposed in this pull request?
The pr aims to ignoring connect-check-protos logic in GA testing for branch-3.4.
Why are the changes needed?
Make GA happy.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Pass GA.

LGTM, merged to branch-3.4


Issue 132

This PR covers issues #119, #132, and #133. This also covers changes requested by PR #92. It is planned to add the changes from PR #131 and complete the request from issue #107 before merging this PR. Please check this code while I write/merge the rest for any issues or errors.

@stephenross thanks for this huge work. I have reviewed all your commits and everything just look fine to me.
Sorry for the delay, I haven't seen that I was a reviewer of this.
I let you merge and I will push to PyPi.
Thanks.

I am not yet done and will be rebasing it later as well as adding the other mentioned changes. This has sadly fallen on the side for the last few weeks.

Gonna update this probably tomorrow since I see you are touching all of the things and mentioning this, plus it has been way too long

This should resolve #92, #107, #119, #132, and #133. #131 was resolved to master prior to this release. Updates to add some of the additional functionality requested such as batch webhook serializing will need to be built on this. Please verify and merge.

@charlesthk Can you please verify and then release?


Support for null safety models

Please, create Null safety library version

You can track progress here
#140

Hi @Andrushka1012
Since 2.0 we support null safety. I'm closing the issue.


Resolve dependency for unnamed struct and macro

Resolve dependency for unnamed struct.
resolve_dependency! now accepts options as last parameter.
Resolve dependency for macros. This commit is also included because of the API change above.
Fix #325

I think I can add a few test cases for this.


Primary Document

"Primary Document" is a very specific Kleros word and new people will not understand it. A newcomer will probably think this is a requirement to submit your ID or passport. I think we want to explain what this is. I'd probably clarify here something like "Submission Guidelines".
Also, when I click into "Primary Document" nothing happens. I should be able to download the document, right? Maybe adding a little PDF icon would make it clearer too.

The link is not going anywhere because the current meta evidence has no primary document.
I'm not sure what the correct wording is, but this isn't a bug.


Jump form docerina generated doc to to source.

It is extremely useful to jump to the github source from the doc. Rust docs has this.

This is a duplicate issue of https://github.com/ballerina-platform/ballerina-lang/issues/4777 and is already tracked, so closing this issue.