Gradle process always failing

I can't run any flutter apps, been working on it all day. Had a power failure , came back after 4 hours and it didn't run anymore. I tried it with brand new projects as well, the create commands work fine, flutter run fails.
Steps to Reproduce

Create a brand new project
Run
Expect the app to run, but it fails.

ProcessException: ProcessException: Process "C:\Code\Content\time_selection_widget\android\gradlew.bat" exited abnormally:
Unzipping C:\Users\User\.gradle\wrapper\dists\gradle-4.10.2-all\9fahxiiecdb76a5g3aw9oi8rv\gradle-4.10.2-all.zip to C:\Users\User\.gradle\wrapper\dists\gradle-4.10.2-all\9fahxiiecdb76a5g3aw9oi8rv

Exception in thread "main" java.util.zip.ZipException: error in opening zip file
	at java.util.zip.ZipFile.open(Native Method)
	at java.util.zip.ZipFile.<init>(ZipFile.java:219)
	at java.util.zip.ZipFile.<init>(ZipFile.java:149)
	at java.util.zip.ZipFile.<init>(ZipFile.java:163)
	at org.gradle.wrapper.Install.unzip(Install.java:214)
	at org.gradle.wrapper.Install.access$600(Install.java:27)
	at org.gradle.wrapper.Install$1.call(Install.java:74)
	at org.gradle.wrapper.Install$1.call(Install.java:48)
	at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:65)
	at org.gradle.wrapper.Install.createDist(Install.java:48)
	at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:128)
	at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:61)
  Command: C:\Code\Content\time_selection_widget\android\gradlew.bat -v

#0      runCheckedAsync (package:flutter_tools/src/base/process.dart:250:5)
<asynchronous suspension>
#1      _initializeGradle (package:flutter_tools/src/android/gradle.dart:209:9)
<asynchronous suspension>
#2      _ensureGradle (package:flutter_tools/src/android/gradle.dart:190:37)
<asynchronous suspension>
#3      _readGradleProject (package:flutter_tools/src/android/gradle.dart:118:31)
<asynchronous suspension>
#4      _gradleProject (package:flutter_tools/src/android/gradle.dart:110:34)
<asynchronous suspension>
#5      getGradleAppOut (package:flutter_tools/src/android/gradle.dart:104:29)
<asynchronous suspension>
#6      AndroidApk.fromAndroidProject (package:flutter_tools/src/application_package.dart:137:23)
<asynchronous suspension>
#7      ApplicationPackageFactory.getPackageForPlatform (package:flutter_tools/src/application_package.dart:37:32)
<asynchronous suspension>
#8      FlutterDevice.runHot (package:flutter_tools/src/resident_runner.dart:288:56)
<asynchronous suspension>
#9      HotRunner.run (package:flutter_tools/src/run_hot.dart:295:39)
<asynchronous suspension>
#10     RunCommand.runCommand (package:flutter_tools/src/commands/run.dart:405:37)
<asynchronous suspension>
#11     FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:551:18)
#12     _asyncThenWrapperHelper.<anonymous closure> (dart:async/runtime/libasync_patch.dart:77:64)
#13     _rootRunUnary (dart:async/zone.dart:1132:38)
#14     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#15     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#16     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#17     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#18     Future._complete (dart:async/future_impl.dart:473:7)
#19     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#20     _AsyncAwaitCompleter.complete (dart:async/runtime/libasync_patch.dart:28:18)
#21     _completeOnAsyncReturn (dart:async/runtime/libasync_patch.dart:294:13)
#22     RunCommand.usageValues (package:flutter_tools/src/commands/run.dart)
#23     _asyncThenWrapperHelper.<anonymous closure> (dart:async/runtime/libasync_patch.dart:77:64)
#24     _rootRunUnary (dart:async/zone.dart:1132:38)
#25     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#26     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#27     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#28     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#29     Future._complete (dart:async/future_impl.dart:473:7)
#30     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#31     _AsyncAwaitCompleter.complete (dart:async/runtime/libasync_patch.dart:28:18)
#32     _completeOnAsyncReturn (dart:async/runtime/libasync_patch.dart:294:13)
#33     AndroidDevice.targetPlatform (package:flutter_tools/src/android/android_device.dart)
#34     _asyncThenWrapperHelper.<anonymous closure> (dart:async/runtime/libasync_patch.dart:77:64)
#35     _rootRunUnary (dart:async/zone.dart:1132:38)
#36     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#37     _FutureListener.handleValue (dart:async/future_impl.dart:126:18)
#38     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:639:45)
#39     Future._propagateToListeners (dart:async/future_impl.dart:668:32)
#40     Future._complete (dart:async/future_impl.dart:473:7)
#41     _SyncCompleter.complete (dart:async/future_impl.dart:51:12)
#42     _AsyncAwaitCompleter.complete.<anonymous closure> (dart:async/runtime/libasync_patch.dart:33:20)
#43     _rootRun (dart:async/zone.dart:1124:13)
#44     _CustomZone.run (dart:async/zone.dart:1021:19)
#45     _CustomZone.bindCallback.<anonymous closure> (dart:async/zone.dart:947:23)
#46     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#47     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#48     _runPendingImmediateCallback (dart:isolate/runtime/libisolate_patch.dart:115:13)
#49     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:172:5)

flutter doctor
[✓] Flutter (Channel master, v1.2.1-pre.143, on Microsoft Windows [Version 10.0.17134.523], locale en-ZA)
    • Flutter version 1.2.1-pre.143 at C:\src\flutter
    • Framework revision ad3da3b4a3 (2 hours ago), 2019-02-11 16:20:45 +0000
    • Engine revision 067045757f
    • Dart version 2.1.2 (build 2.1.2-dev.0.0 174d6fec3d)

[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Android\android-sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • ANDROID_HOME = C:\Android\android-sdk
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)
    • All Android licenses accepted.

[✓] Android Studio (version 3.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 29.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)

[✓] VS Code, 64-bit edition (version 1.30.2)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 2.22.3

[✓] Connected device (1 available)
    • Android SDK built for x86 • emulator-5554 • android-x86 • Android P (API 27) (emulator)

• No issues found!

Deleting this folder C:\Users\User.gradle\wrapper\dists\gradle-4.10.2-all\ and running the project in Android Studio, not Visual Studio resolved it.

Hello there,
on MacOS Mojave same issue and same solution:

Remove all from ~.gradle/wrapper/dists/gradle-4.10.2-all/9fahxiiecdb76a5g3aw9oi8rv/
Run gradlew -v and make sure that error pure gradle:

Downloading https://services.gradle.org/distributions/gradle-4.10.2-all.zip
Exception in thread "main" java.net.NoRouteToHostException: No route to host (Host unreachable)

Remove all files from ~.gradle/wrapper/dists/gradle-4.10.2-all/9fahxiiecdb76a5g3aw9oi8rv/ again
Download https://services.gradle.org/distributions/gradle-4.10.2-all.zip manualy
Put zip archive in ~.gradle/wrapper/dists/gradle-4.10.2-all/9fahxiiecdb76a5g3aw9oi8rv/
Run gradlew -v and make sure that all files unzipped correctly

I'm working on ubuntu 18 and i still have the same issue
I tried the solution mentioned above but it doesn't work
can anyone help please


Feat/return operation data

:tada: This PR is included in version 10.0.0-next.1 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Test suite

[x] testsuite added in the distutils standard way
[x] setup.py modified a lot :

will retrieve the version from init instead hardcoded to make versioning easier
will fetch requirements from requirements.txt, no errors from double admin.
setup.py publish gives you the git command to tag the last version : configure .travis.yml with a deploy attribute and it will enable you to deploy to pypi from Travis using twine

[x] added pyth 3.3 / 3.4 and 3.6 : also passing
[x] version badge added (right versions will show up after merging)
[ ] implement coverage ? (it's easy to hook up coveralls) (and landscape / codacy)

Personally I deploy to pypi from Travis: bump the version in __init__, update your master, tag it and you are done.

[x] rewrite README.md to README.rst : reason I rewrote my README.md's to README.rst's is because pypi likes .rst files a lot better. If you have a README.rst and modify the setup.py for that, then the deployment to pypi will show the README there also.

This setup is partially based on work of Tom Christie, @tomchristie, author of the Django Rest Framework, he wrote an article about depoying to pypi: https://tom-christie.github.io/articles/pypi/. For some of my own packages I've extended that a lot.
Travis has some annoying differences between the different environments. Sometimes you run into them

@hootnot waiting for the fat lady to sing, but this looks great!

do you want me to fix README from md to rst ?

That'd be @tom-christie.

rst makes more sense given your argument and experience, thanks for that too. I'll merge as is unless you plan to add coverage (yes please!).

Fixed the setEncoder/setDecoder internal links. Should be it now.
You can merge now if you like.
To setup coverage you need to modify .travis.yml with a key from coveralls.io . You are the boss! so you have to do this because of key related stuf.
Lets handle this one first

Thanks again -merging and starting to think about releasing the next version codenamed "hootnot" :)

... I would be honoured :-), saw the 95% coverage too. A few extra tests and you have it 100%.
The version still sits on 2.7, that  is because that info is retrieve from pypi and not from the master as I wrote in the PR. So when you upload a new release that is fixed.

In case I forgot to say it, thank you. After taking the project for a test drive, it feels like I moved from

to

Getting this atm, but I'm sure it is something that I missed:
$ pip install rejson
Collecting rejson
  Downloading rejson-0.2.0.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/tmp/pip-build-EobKFa/rejson/setup.py", line 22, in <module>
        requirements = map(str.strip, open("requirements.txt").readlines())
    IOError: [Errno 2] No such file or directory: 'requirements.txt'

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-EobKFa/rejson/


update write-mirror-list.sh with idea from issue #8561

Motivation for this change
Things done

[ ] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

For me it fails with egrep or grep -E and succeeds with grep.  Nevertheless, it's a really hacky piece of code.

Aha, the suggestion on the issue was slightly different...


[T2A4][W14-A2]HonKeanWai

Allowed users to find people using non case sensitive keywords.

Accepting this PR without a review because another of your PRs for this tutorial was reviewed in detail.


deps: regenerating with new Protobuf (2.2.x)

'To merge into 2.2.x branch. This PR was generated using Protobuf 3.19.6. Source-Link: https://github.com/googleapis/googleapis/commit/2921f9fb3bfbd16f6b2da0104373e2b47a80a65e'

Running into:
Failed to execute goal org.jacoco:jacoco-maven-plugin:0.8.7:prepare-agent (default) on project google-cloud-service-usage-bom: Execution default of goal org.jacoco:jacoco-maven-plugin:0.8.7:prepare-agent failed: Plugin org.jacoco:jacoco-maven-plugin:0.8.7 or one of its dependencies could not be resolved: Could not transfer artifact org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-6 from/to central (https://repo.maven.apache.org/maven2): transfer failed for https://repo.maven.apache.org/maven2/org/apache/maven/wagon/wagon-provider-api/1.0-alpha-6/wagon-provider-api-1.0-alpha-6.jar: Connect to repo.maven.apache.org:443 [repo.maven.apache.org/<IP_ADDRESS>] failed: Connection timed out


Ensure the commands are lower case in Redis request mirroring

Description: We need to lower case the command name when we're deciding if we want to mirror the command.
Risk Level: Low
Testing: Added unit test
Docs Changes: N/A
Release Notes: N/A

PTAL @mattklein123 @FAYiEKcbD0XFqF2QK2E4viAHg8rMm2VbjYKdjTg @msukalski

@htuch for senior approver.


Do not break on missing let declarations.

This change fixes #42 for let a, b; declarations
until now handled like const missed declrations.
Outstainding: the var a, b; case still fails.

Coverage increased (+0.002%) to 96.509% when pulling 4b8ec601f582489e87cfab20995850eaf5066a01 on WebReflection:master into 6efb1be71ced4847ef22242968e5a6670d2d1f99 on cherow:master.

fixed in a better way already


Set node name to be hostname

Relates to https://github.com/eucalyptus/calyptos/issues/104

Can one of the admins verify this patch?


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target-new/pull/2 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target-new.git

Docs Build status updates of commit 7b0f274:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-09-20-11-23-24 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-09-20-11-23-24

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


AWS ssh key-pair authentication problem

Describe the bug
I have created a Panorama VM version 1.10.6 using Terraform.
The VM gets created successfully but the SSH authentication using PEM key is not working. It falls back to password authentication.
I created the instance manually providing the same key pair and then I was able to SSH successfully.
Expected behavior
SSH authentication should work if Panorama VM is provisioned using Terraform
Current behavior
SSH authentication doesn't work using the syntax ssh -i /path/to/key.pem admin@<ip-address>. It falls back to password authentication and password can only be configured after login to VM using SSH.
Steps to reproduce

Create a Panorama VM using this module https://github.com/PaloAltoNetworks/terraform-aws-vmseries-modules/tree/develop/modules/panorama
Note down the IP address of the VM
Try SSH to the VM using syntax ssh -i /path/to/key.pem admin@<ip-address>

NOTE: I tested both with existing key pair and generate key pair locally, passing the public key to Terraform. It fails in both scenarios.
Screenshots

Context
I'm trying to automate the provisioning of Panorama and Firewalls using Terraform. All the Panorama resources like device groups, security profiles, objects, etc will also be managed using Terraform
Your Environment
Terraform Version is 1.0.6
Panorama Version 1.10.6
Panorama AMI is obtained using AWS Marketplace so it's an official AMI.

What type of ssh key are you using ?

I have tried both RSA and ed25519.
RSA was existing SSH pem key in AWS account I use for other VMs.
When that didn't work, I generated ed25519 key pair locally and passed public key to Terraform. That didn't help either.

What type of ssh key are you using ?

I have tried both RSA and ed25519.
RSA was existing SSH pem key in AWS account I use for other VMs.
When that didn't work, I generated ed25519 key pair locally and passed public key to Terraform. That didn't help either.

CORRECTION: Panorama version is 10.1.6

hi @rickyb30 did you find the solution? for some strange reason i'm facing the same issue with panorama 10.2.0. Thanks in advance

hi @rickyb30 did you find the solution? for some strange reason i'm facing the same issue with panorama 10.2.0. Thanks in advance

Hey @ulm0 Yeah so I figured it doesn't work if we use instance metadata v2. So in my terraform script, I removed metadata {} block configured in aws_instance resource.

I ran into a same problem and this worked for me:
ssh -oHostKeyAlgorithms=+ssh-rsa<EMAIL_ADDRESS>-i ./key-pair-name.pem


Remove compareMCMCs

I think we could remove the placeholder for the original compareMCMCs (just giving a message) that is now deprecated in favor of package compareMCMCs (which will get an update soon).

@perrydv Agreed.

Yes. I'll just put it on my to-do list and take care of with other minor things.

Working on this now.
@danielturek it appears on initial glance that the only use case for the returnComponents argument to readBUGSmodel was the now defunct MCMCsuite. What do you think about me removing that argument?

@paciorek I, personally, think this returnComponents option is useful to have.  But that said, if the momentum is to clean up and remove it, I would understand.

I'm happy to leave it.
Taking out the placeholders is done on devel, so closing this.


Minor changes to the Tutorials

This updates the pagecontent/index.md files in both the docs and docs-beta tutorials to more accurately describe the time of FSH calls, and to ensure all working links.
This also changes the terminal symbol to $ from >_.

Suggest you use font awesome's dollar sign. And can you please reflect whatever changes you made in the tutorial via another PR on https://github.com/FSHSchool/fsh-tutorial ?

Ugh sorry forgot about that repo again. I will make the corresponding change there.

Ok @cmoesel, made the font change, and added a PR https://github.com/FSHSchool/fsh-tutorial/pull/2 to update that tutorial.


Fix to support Storybook UI and React

Hi @erie149,
Thank you a lot for contributing to Flagpack!
I've checked your PR and it looks like it's having some issues regarding importing React. It looks like React shouldn't be a peerDependency.
When changing react to a regular dependency I'm also facing a bug where the SVG isn't loaded properly. I'm not completely sure why.

Are you able to reproduce this error? Please let me know.


helm: Helm chart tunes

User description
The following changes were tested on AWS EKS.

Add missing ingressClassName key to the values.yaml under ingress block
pathType: Prefix will expose all existing endpoints but pathType: ImplementationSpecific exposes / path as Exact match. See docs - https://kubernetes.io/docs/concepts/services-networking/ingress/#path-types
Rework fulfilment of the HOST environment variable to fetch the value from the ingress resource values. Previously, it was set to localhost even if the application was exposed with ingress resource

PR Type
enhancement, bug fix

Description

Changed pathType from ImplementationSpecific to Prefix for ingress paths.
Modified HOST environment variable to fetch value from ingress resource.
Added ingressClassName key under ingress block in values.yaml.
Set SSL to true by default in values.yaml.

Changes walkthrough 📝
Relevant filesEnhancement

ingress.yamlUpdate ingress pathType to Prefix

templates/ingress.yaml
Changed pathType from ImplementationSpecific to Prefix for ingress paths.

+1/-1

values.yamlAdd ingressClassName key and set SSL to true by default

values.yaml
Added ingressClassName key under ingress block.  Set SSL to true by default.

+2/-1

Bug fix

onetimesecret-deployment.yamlUpdate HOST environment variable to match ingress hostname

templates/onetimesecret-deployment.yaml
Modified HOST environment variable to fetch value from ingress resource.

+3/-1

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

Sorry for the delay. Will take a look no later than this weekend, if not sooner.

@blacktig3r if you can take a look as well that would be great.

@blacktig3r if you can take a look as well that would be great.

@venkatamutyala Changes looks good to me. I have tried to deploy it on GKE and working fine.

Thanks @blacktig3r


feature: add kubectl ws -i

Feature Description
We should support kubectl ws -i for interactive browsing the tree
Proposed Solution
use something like https://github.com/manifoldco/promptui or https://github.com/rivo/tview/
Alternative Solutions
No response
Want to contribute?

[ ] I would like to work on this issue.

Additional Context
No response

Similar:
https://github.com/kcp-dev/kcp/pull/2309

https://github.com/charmbracelet/bubbletea

Small note, I wrote a bash-based prototype for this functionality. It's available at https://github.com/embik/kubectl-switch-ws. I don't think the bash-based version cuts it for integrating it into kubectl ws, but maybe we can get away with using fzf over our own full TUI.

Hey Folks! Is this issue open for grabs?

Hey @rakshitgondwal, it is, yes!

Hey @embik, have we come to any conclusion on what framework to use for the TUI? I've worked with Bubbletea before but I would be open to implementing any other as well.

No real conclusion, I think. We are looking for a solution that is lightweight and fast, and no one has too many thoughts on the matter. Something that I was wondering is if running echo "option1\noption2\n" | fzf in a shell exec within the code might be the "best" solution (basically implement https://github.com/embik/kubectl-switch-ws in Go and get the data via Go clients instead of kubectl calls), but I'm open to whatever works and looks and feels nice.

/assign jmcshane

I'd like to take this issue, investigating now


Aclaration in README.md

You do not always want to repeat infinitely

Thanks for the PR. The wording on that phrase make it clear already that infinite is optional. Closing this.


add ability in cloudflare_access_application to set the browser rendering setting for zero trust application settings.

Current Terraform and Cloudflare provider version
Terraform v1.2.6
on linux_amd64
+ provider registry.terraform.io/cloudflare/cloudflare v3.21.0

Description
Add the ability to change the browser rendering configuration in the Cloudflare Zero Trust application settings with the Terraform provider under the cloudflare_access_application resource.
Use cases
It would be nice to be able to set an applications browser rendering settings via Terraform instead of doing it manually in the UI.
Potential Terraform configuration
resource "cloudflare_access_application" "staging_app" {
  zone_id                   = "0da42c8d2132a9ddaf714f9e7c920711"
  name                      = "staging application"
  domain                    = "staging.example.com"
  type                      = "self_hosted"
  session_duration          = "24h"
  auto_redirect_to_identity = false
  # new configuration option
  browser_rendering         = "ssh"
}

### References

_No response_

@jacobbednarz Do you have any insight into when this could potentially be implemented into the Cloudflare API or Terraform Provider? As I can't toggle this option programmatically my project has come to a bit of a halt at the moment.

Changing
type                      = "ssh"

Worked for me.

@jacobbednarz I'm pretty sure this is a non issue. ssh and vnc are just a type of access application and are already being validated here https://github.com/cloudflare/terraform-provider-cloudflare/blob/c9eef200b557bd1f41fb0c492bf5e2bcbad38fb2/internal/provider/schema_cloudflare_access_application.go#L49

cc @Justin-Holmes

@haydndup is correct, set the application to ssh and that will create a browser rendering ssh app.

thanks for confirming! closing as this is already supported.


search: phrase search is not working

Package version (if known):
Describe the bug
A clear and concise description of what the bug is.
Steps to Reproduce

Go to https://<IP_ADDRESS>:5000/search?q=&p=1&s=10&sort=bestmatch
Type "open science" in the search field and hit enter.
Copy/paste the URL (should match https://<IP_ADDRESS>:5000/search?q=%22open%20science%22&p=1&s=10&sort=bestmatch)
Paste the URL in the browser address bar and hit enter.

See that "open science" changed to open science (i.e. without quotes).

Here the bug in RSK: https://github.com/inveniosoftware/react-searchkit/issues/176

fixed with https://github.com/inveniosoftware/react-searchkit/pull/177


add again rpm (for rpmbuild used in sbt native packager)

apt-get install rpm was removed (accidentally along with apt-get install sbt ?)

we are no longer installing through apt/rpm
mainly because of https://github.com/sbt/sbt/releases/tag/v1.4.9 mention that the packages are no longer provided as jcenter is going down
Do you have problems starting scala or sbt in the image?

When running
sbt rpm:packageBin

rpmbuild binary is required in the image

You can install that yourself? Must be that some base Image we build on no longer provides this. I already saw that some switched from yum to microdnf before we switched to installing using the sbt .tar.gz archive.
I don't think this is something that needs solving here. The purpose of these images is providing scala and sbt which is working as expected.
What image are you using?

Have you tried this?
microdnf -y install rpm-build

Thanks for your reactivity !
It worked before and it was useful.
I need to build a RPM in my ci pipeline (that uses scala-sbt image) and I need to do that using a sbt command thus I need rpmbuild binary in the same image than sbt.
I cannot use one separate image/ci job to launch rpmbuild because is is launched by sbt (with sbt native packager plugin)
I would like to avoid maintaining my own image (and this is the purpose of scala-sbt image to "pool" this effort)
I could install it each time in the build job but it would be inefficient.
I don't see how micodnf or yum could help me ? (maybe i misunderstood) I just need rpmbuild binary in the image for my build process, I don't need to find another package manager.
I'm not sur to understand the problem : sbt is not available in deb repository but it "rpm" package is and is contains rpmbuild binary.
the lines
apt-get update &&
apt-get install sbt rpm -y

were removed but the intention was to stop installing sbt package using apt-get command (and use tag.gz instead). The intention was not to stop install "rpm" package itself ?

To be clear, my suggestion is to add again (in debian dockerfile)
apt-get update &&
apt-get install rpm -y

This will install "rpm" debian package (containing rpmbuild that allows to build rpm) but not sbt. rpm package is available in debian repository.

I understand now, can you not do apt-get install rpm -y as fist thing in your ci job? It's quite a waste to make the image bigger just for this specific case?

anyway, since this is a regression I will put it back
I see it was previously added in #114

@gbrd let me know if this issue is fixed, thanks for pointing to the regression.

It works ! thanks a lot. :)


Buttons + icons not vertically aligned

Is there a way to get the icons in the buttons vertically aligned?
As you can see from my example all the icons are not vertically aligned with the text.

Demo
Please let me know if you have any plan to update this behavior. I will be glad to submit a pull request

I think at moment it's only possible with weird css hacks (and this sucks!).

https://jsfiddle.net/gianlucaguarini/7ntmanxm/

You could use flexbox inside mdl-button.

It does not solve the problem :(

@GianlucaGuarini Oh really? http://codepen.io/Zodiase/pen/MyYxjJ

Alternatively, since the line-height of mdl-button is set based on 16px height content, you could shrink the icon from 24px to 16px, or offset it as you are doing right now.

@Zodiase should not this be supported directly by mdl?

@Zodiase btw have you tested your demo on firefox?

@GianlucaGuarini Nope I mainly develop for Chrome.

@GianlucaGuarini Demo updated to work for Firefox and Safari.

thanks @Zodiase but that's the result of the demo ( i have also tried other kind of icons):
Firefox

Safari

Chrome

It seems the icons are always 1px misaligned from the top. I am wondering whether we need an official solution and not trying to hack the issue. I guess also the lateral padding is not nice, I think a button with an icon should look more like my previous example
Of course your solution is ok but it does not produce any better result compared to the default icon + button solution ( without flexbox ). I think this topic is quite important if we want to use mdl for building professional pixel perfect UIs.. for amateurs the current solution is more than ok.

We need MD Guidance here to see if icons in buttons are acceptable. Currently the specification does not say anything about the occurrence.

@GianlucaGuarini: @Garbee is correct in that icons inside rectangular buttons aren't a documented use-case in the spec. I'm reluctant for us to ship fixes to improve this use-case without any guidance into how to do it correctly (if it is indeed correct usage); I'd want to know whether it would affect button size, what the paddings should be like, etc.

As side note, the buttons + icons are already used on https://www.polymer-project.org/1.0/ having an awful design ( wrong padding and alignment )

So probably It's worth spending some time defining the specs regarding how material should handle these kind of elements
cc @ebidel

Looks like the problem is not so much the icon as it is the (bottom space) of the text? If text is aligned vertically it sits a bit higher to accommodate for the lower parts of letters like 'g', 'y', etc.

@GianlucaGuarini The existing Polymer site uses polymer 0.5, which uses the old element set. However, the text seems vertically centered to icon to me. The same is true with the 1.0 set: https://elements.polymer-project.org/elements/paper-button?view=demo:demo/index.html&active=paper-button.
AFAIK, the icons themselves no not build in the padding. This is left to other elements like paper-icon-button and paper-item.
Keep in mind that one thing that can affect alignment is line-height. if the page has set this, than it will inherit and can mess things up.

@ebidel you are right the icons look vertically aligned but only on chrome, even on the last paper-icon-button version there seems to be 1px misalignment at least on firefox (48.0a2 Macbook Pro 10.11.4).

Keep in mind that one thing that can affect alignment is line-height. if the page has set this, than it will inherit and can mess things up.

Yes of course, I agree.. but here I am speaking about a vanilla version of mdl that should already provide a solution to these problems IMHO

Yes but what I'm saying is that line-height is an inheritable property. So
if the page has messed with it, it's possible it will affect the pre-made
solution. This is one reason we need shadow dom so badly.
On Fri, Apr 29, 2016, 12:44 AM Gianluca Guarini<EMAIL_ADDRESS>wrote:

@ebidel https://github.com/ebidel you are right the icons look
vertically aligned but only on chrome, even on the last paper-icon-button
version there seems to be 1px misalignment at least on firefox (48.0a2
Macbook Pro 10.11.4).
[image: screen shot]
https://cloud.githubusercontent.com/assets/879612/14910554/af04f248-0dee-11e6-90e9-342e54decc82.png
Keep in mind that one thing that can affect alignment is line-height. if
the page has set this, than it will inherit and can mess things up.
Yes of course, I agree.. but here I am speaking about a vanilla version of
mdl that should already provide a solution to these problems IMHO
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/google/material-design-lite/issues/4165#issuecomment-215650644

I still have the same issue, the icons are not aligned with the text


Fix CMake configuration error in snappy

This closes #792.

@torwig @aleksraiden Hi, could you guys help me to check whether this PR really fixed the CMake error on Fedora? So thanks!

May you describe a bit how adding these two files helps resolve the issue?
I think it's about CMake resolving order while it looks like we always set GFLAGS_FOUND & GTEST_FOUND to false.

By default, for find_package(X), CMake will use the builtin FindX.cmake file (provided by CMake) to find the X package.
It will try to find the package in system, e.g. installed from package manager.
We overwrite this file to make sure CMake do not use some builtin logic to find the package, because we do not need these package in snappy.
It is actually a bug in (old version of) snappy, we defined SNAPPY__BUILD_TEST=OFF, but snappy will always find gtest regardless of our option, and we do not need gtest in snappy since we do not build unit tests in snappy.
@tisonkun

@torwig Thanks for your confirmation!
Merging...

@tisonkun I can confirm too, that the build process on Debian 11 are OK.


enable token authentication

POST {"username":"foouser","password":"secret"} or the equivalent form to /api/v1/tokens/ to get {"token": "9c158ea8132b23e823c945e37dcc63fcbd1977df"}.
Apply this to any API view as Authorization: Token 9c158ea8132b23e823c945e37dcc63fcbd1977df for L. Dallas multipass.
Possible future improvements

DELETE on /api/v1/tokens/9c158ea8132b23e823c945e37dcc63fcbd1977df to revoke a token
The default implementation of obtain_auth_token currently returns the same token when POSTed again. We may want to allow different tokens for different devices.
GET on /api/v1/tokens/ to query currently active tokens.

Sure. For future development, https://github.com/GetBlimp/django-rest-framework-jwt does good things. :3


Fix plugin settings restore and schema_version validation error in preferences dialog

Description
This fixes items 3 and 4 from #3206 ... probably want to get this in for 0.4.11
Type of change

[ ] Bug-fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

References

How has this been tested?

[ ] example: the test suite for my feature covers cases x, y, and z
[ ] example: all tests pass with my change

Final checklist:

[ ] My PR is the minimum possible work for the desired functionality
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If I included new strings, I have used trans. to make them localizable.
For more information see our translations guide.

@tlambert03 it looks like this PR broke our docs building with the following error - see
Run python docs/update_docs.py
WARNING: QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-runner'
Traceback (most recent call last):
  File "docs/update_docs.py", line 164, in <module>
    create_preferences_docs()
  File "docs/update_docs.py", line 134, in create_preferences_docs
    if not issubclass(field.type_, BaseModel):
  File "/opt/hostedtoolcache/Python/3.8.11/x64/lib/python3.8/abc.py", line 102, in __subclasscheck__
    return _abc_subclasscheck(cls, subclass)
TypeError: issubclass() arg 1 must be a class
Error: Process completed with exit code 1.

Any chance @tlambert03 @goanpeca @jaimergp for a quick fix here. I think this is the last thing needed before I can make the next rc

yep, I mentioned the fix in https://github.com/napari/napari/pull/3296#issuecomment-908831386
will take care of it

https://github.com/napari/napari/pull/3305


Reset Password or Username

Summary
The user needs to reset their password
Basic Flow

The use case starts when the user indicates they want to reset their
password.
The system requests the username.
The system emails the user a password reset link.
On clicking the link, the system allows the user to set a new password.
The system starts a new login session.

Preconditions
The user is registered.
The username is the user’s email address.
Postconditions
The user can now login.

Could either have the same Components for when a User Logs In with some conditional formatting to hide/disable the password input field, and show/enable once the separate link has been clicked so they can enter a new password.
Or, could just have own components of an input field for username and directs the User to the Login Page once the link has been clicked but the logic now SETS a password instead of checking it exists?
Depends on HOW the password is reset, I'm not sure if the link acts as a simple verification/authentication for us so we know this is the correct User to change their password, so there is a timeout mechanism for when the link expires, and if it's clicked before timeout, update the components and logic to allow a new password to be entered/update document.

Investigate firebase - It might already have a way to verify user emails

Documentation for Sending a User Password Reset email: https://firebase.google.com/docs/auth/web/manage-users#send_a_password_reset_email
I will probably add my own personal email address to FireStore so I can test whether or not an email is sent, and if the password is reset.

Once the Email is successfully sent, Firebase takes care of literally everything else in terms of resetting the Password.
Could sort out a redirect back to the Login page but I'd rather just have the proof-of-concept finished first before adding fancy extras (K.I.S.S principle)

[ ] Add my own Email to Firebase
[ ] Create new RouterView called "ResetUserPasswordView"
[ ] ResetUserPasswordView should contain an <input type="email"> and a <button @click="sendResetLink">Send Link</button>
[ ] Add path to router/index.js
[ ] Add function called sendResetLink to Composables folder from https://github.com/advweb-grp1/advanced-web-final-year-project/issues/6#issuecomment-1497657053
[ ] Test with personal Email
[ ] Once verified to be working, add a link to ResetUserPasswordView from Login page

Could have a Modal stating an Email has been successfully sent and prompting User to check inbox (and spam)

Unit Test: Have a set of valid and invalid emails for trying to find Users (and sending emails) in firebase

Email/link was successfully sent to my email address (in spam). From there, firebase lets you change password and confirms your password change, however I can't actually verify password (before/after) on Firebase console because it doesn't show user passwords for security reasons.
But I still think it works properly:thumbsup:
Could wait for #4 (Login) to properly verify whether or not password has changed??... even though firebase says it has!


'declare' modifier required on top-level type alias in a .d.ts file

type Foo = number;

Save this as a .d.ts file, you'll get an error about how a declare modifier is required in a top-level declaration.

@maybejulian is interested in taking this on.

thanks @maybejulian!


Scrolling up doesn't work with scrollMode: if-needed

👋 hey there,
After some investigation of an issue posted in react-scroll-into-view-if-needed here. It looks as though there is a bug with the following behavior:

scrolling up to a target block with scrollMode: 'if-needed'.

I setup this codesandbox to demonstrate: https://codesandbox.io/s/l4w26w2jz7
(note: it is in React, but I'd be happy to setup an html/css only one soon if it helps)
In this example, with scrollMode set to 'always', scroll to the bottom of the page and click this button at the bottom:

Notice that it scrolls up to the target as expected
Now, switch to 'if-needed' and notice the button does not scroll up to the target.
I'm happy to dig deeper in the near future and submit a PR if I can find the problem, but in the meantime just wanted to document it here for visibility.
Thanks for your work on this package!

Hey thanks for the detailed report! I am on the go today but I will circle back in around 10 hours and have a go at it 😄
The flaw is probably too simplistic logic here: https://github.com/stipsan/scroll-into-view-if-needed/blob/73e7d76ab7a1e678a47f3c63a0452a3e1b96f6a5/src/compute.ts#L256-L273

@icd2k3 #276 should fix it. I have tested it locally as well as on the codesandbox you shared. 😄

:tada: This issue has been resolved in version 2.2.5 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Sweet! Thanks for the timely fix @stipsan

No problem! 😄

On 9 Jun 2018, at 06:33, Justin Schrader<EMAIL_ADDRESS>wrote:
Sweet! Thanks for the timely fix @stipsan
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Sysmon v11.0 04/28/2020

Sysmon version 11.0 was released on 04/28/2020.
A new event ID was added.
23 FileDelete
The parser will need to be updated for this.
I'm not sure what else has changed with this version.

Field
Description

UtcTime
Time in UTC when event was created

ProcessGuid
Process Guid of the process that made the delete

ProcessId
Process ID of the process that made the delete

User
User that created the

Image
File path of the process that made the

TargetFilename
Name of the file that was deleted

Hashes
Full hash of the file with the algorithms in the HashType field

IsExecutable
Boolean Value if deleted file was executable

Archived
Boolean Value if deleted file was archived in the ArchiveDirectory folder based on the CopyOnDelete* settings

Will review and update - thanks

Updated - thanks


Documentation

Someone please review @vietj @cescoffier @pmlopes

Will do.

I've made two small comments (obviously on the adco file and not on the pacakge-info.java file....).
Everything else is fine. So you can merge (I don't have the right to merge on this repo).

Thanks for the comments clement, I have added a few more bits as you suggested.


LocalVideoTrack's source .unknown instead of .camera

For my app on iOS (which never uses screen sharing) the firstCameraPublication is always nil.  It appears that source = .unknown for the published LocalVideoTrack associated with the camera capturer.  This breaks the computed property firstCameraPublication on ObservableParticipant, because the filter for the call to first() never finds a track with source == .camera
https://github.com/livekit/client-sdk-ios/blob/main/Sources/LiveKit/SwiftUISupport/ObservableParticipant.swift#L119
Investigating this, I've found that the correct value for source = .camera is passed here:
https://github.com/livekit/client-sdk-ios/blob/main/Sources/LiveKit/Participant/LocalParticipant.swift#L48
However in the next handler in the promise chain, the deserialized trackInfo from the server response results in source = .unknown
https://github.com/livekit/client-sdk-ios/blob/main/Sources/LiveKit/Participant/LocalParticipant.swift#L64

@doesnotexist what version of the server are you running? I think it's old enough that publishing with Source is not yet supported.

@davidzhao v0.13.1
I can see how the no source coming back in the response could result in the .unknown value.
Let me see if upgrading to a newer version fixes the behavior.
If thats the case, is that the intended behavior, that a client should depend on the server state's values even for metadata about their own published local tracks?

Server versions before v0.13.5 does not support the Source attribute.. so the getTrackPublication(source:) functions will not work properly for versions before then.
Even if it uses the local information (instead of remote), it won't work properly for all of the remote participants' publications. So you really need the right version of server in order to utilize the *Source APIs.

Got it, thanks.  Closing this issue.


[coindirect] fixed incorrect access of raw constructors + path tweaks

Apologies for this, access of *Raw constructors was incorrect, need this for the xchange-stream implementation.

just following up on this one :) xchange-stream pull request I have references this patch. Thanks

@timmolter thanks!


Adding Inference Pools, Groups and Endpoints recreated for https://github.com/Azure/azure-rest-api-specs/pull/25783 for rebased issue

ARM (Control Plane) API Specification Update Pull Request
PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

[1] ARM review queue (for merge queues, see [4])
The PRs are processed by time opened, ascending. Your PR may show up on 2nd or later page.
If you addressed Step 1 from the diagram and your PR is not showing up in the queue, ensure the label ARMChangesRequested
is removed from your PR. This should cause the label WaitForARMFeedback to be added.
[2] https://aka.ms/azsdk/support/specreview-channel
[3] List of SDK breaking changes approvers in pinned Teams announcement
[4] public repo merge queue, private repo merge queue (for ARM review queue, [1])
If you need further help with anything, see Getting help section below.
Purpose of this PR
What's the purpose of this PR? Check all that apply. This is mandatory!

[ ] New API version. (Such PR should have been generated with OpenAPI Hub, per this wiki doc.)
[ ] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix swagger quality issues in S360.
[ ] Other, please clarify:

edit this with your clarification

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[ ] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[ ] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to Step 2, "ARM Review", for this PR.

Breaking changes review (Step 1)

If the automation determines you have breaking changes, i.e. Step 1 from the diagram applies to you,
you must follow the breaking changes process.
IMPORTANT This applies even if:

The tool fails while it shouldn't, e.g. due to runtime exception, or incorrect detection of breaking changes.
You believe there is no need for you to request breaking change approval, for any reason.
Such claims must be reviewed, and the process is the same.

ARM API changes review (Step 2)

If this PR is in purview of ARM review then automation will add the ARMReview label.
If you want to force ARM review, add the label yourself.
Proceed according to the diagram at the top of this comment.

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Getting help

For general PR approval workflow, see the diagram at the top of this comment.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

Please provide the purpose of the API and complete the due diligence checklist so that we can understand the changes better.

        "description": "Create or update request is successful.",

200 is updated only

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:8315 in 1fca1a3. [](commit_id = 1fca1a3a1190049682795960b3e91e3f6d38dada, deletion_comment = False)

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearningServices/workspaces/{workspaceName}/inferencePools/{name}": {

do you mean this is {inferencePoolName}

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:8441 in 1fca1a3. [](commit_id = 1fca1a3a1190049682795960b3e91e3f6d38dada, deletion_comment = False)

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearningServices/workspaces/{workspaceName}/inferencePools/{name}/status": {

post action needs to have verb in the actionName, you could say fetchStatus instead of just status as the action name

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:8803 in 1fca1a3. [](commit_id = 1fca1a3a1190049682795960b3e91e3f6d38dada, deletion_comment = False)

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearningServices/workspaces/{workspaceName}/inferencePools/{name}/status": {

having so many nested levels is discouraged. This can become an issue for RBAC

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:8803 in 1fca1a3. [](commit_id = 1fca1a3a1190049682795960b3e91e3f6d38dada, deletion_comment = False)

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearningServices/workspaces/{workspaceName}/inferencePools/{name}/status": {

post action needs to have verb in the actionName, you could say fetchStatus instead of just status as the action name
Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:8803 in 1fca1a3. [](commit_id = 1fca1a3, deletion_comment = False)

Updated

Please provide the purpose of the API and complete the due diligence checklist so that we can understand the changes better.

These are new resources to support large fleet of compute running specific models.

"/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.MachineLearningServices/workspaces/{workspaceName}/inferencePools/{name}/status": {

having so many nested levels is discouraged. This can become an issue for RBAC
Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:8803 in 1fca1a3. [](commit_id = 1fca1a3, deletion_comment = False)

These are child/sub resources within the InferencePool. Where each InferencePool can have many groups and each group can have many endpoints. We currently have OnlineEndpoint and OnlineDeployment resouces in similar way. Can you explain a bit more about the issue

        "type": "object"

Why is this a free-form object? Please define a schema for the model here, as users won't know how to read/parse this.

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:19174 in afce89c. [](commit_id = afce89cf3ee90a68ca8cf9c256737be82bb0ea4e, deletion_comment = False)

    "data": {

Rename data to metadata?

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:20367 in afce89c. [](commit_id = afce89cf3ee90a68ca8cf9c256737be82bb0ea4e, deletion_comment = False)

"InferenceGroupMinimalTrackedResourceWithSku": {

Same here: why not use TrackedResource from common types v3?

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:20389 in afce89c. [](commit_id = afce89cf3ee90a68ca8cf9c256737be82bb0ea4e, deletion_comment = False)

      "$ref": "#/definitions/InferencePool"

Rename InferencePool to InferencePoolProperties?

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:20547 in afce89c. [](commit_id = afce89cf3ee90a68ca8cf9c256737be82bb0ea4e, deletion_comment = False)

      "x-nullable": true

As long as the upper level definition calls out the "required" properties, this x-nullable is redundant, so it can skipped to define explicitly for all properties.

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:25218 in afce89c. [](commit_id = afce89cf3ee90a68ca8cf9c256737be82bb0ea4e, deletion_comment = False)

    "properties": {

Can this not be named as additionalProperties? Properties inside Properties seems odd.

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:25507 in afce89c. [](commit_id = afce89cf3ee90a68ca8cf9c256737be82bb0ea4e, deletion_comment = False)

additionalProperties

@visingla-ms we have the same structure for existing ARM resources like OnlineEndpoint and Deployment. We wanted to keep it consistent.

        "type": "object"

Schema?
Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:25309 in afce89c. [](commit_id = afce89c, deletion_comment = False)

      "x-nullable": true

As long as the upper level definition calls out the "required" properties, this x-nullable is redundant, so it can skipped to define explicitly for all properties.
Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:25218 in afce89c. [](commit_id = afce89c, deletion_comment = False)

@visingla-ms this is coming from the common Microsoft.MachineLearningServices RP implementation and is there for all the resources in this RP. After talking to the RP owners it will have some side effects and would be better to avoid

    "properties": {

Can this not be named as additionalProperties? Properties inside Properties seems odd.
Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:25507 in afce89c. [](commit_id = afce89c, deletion_comment = False)

@visingla-ms  we have the same structure for existing ARM resources like OnlineEndpoint and Deployment. We wanted to keep it consistent.

"InferenceEndpointMinimalTrackedResource": {

Why not derive it from common types v3 TrackedResource, and not define id, name, type etc. properties here?
Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:20270 in afce89c. [](commit_id = afce89c, deletion_comment = False)

@visingla-ms this is coming from the common Microsoft.MachineLearningServices RP implementation and is there for all the resources in this RP. After talking to the RP owners it will have some side effects and would be better to avoid

      "$ref": "#/definitions/InferencePool"

Rename InferencePool to InferencePoolProperties?
Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:20547 in afce89c. [](commit_id = afce89c, deletion_comment = False)

@visingla-ms All the ARM resources for this RP Microsoft.MachineLearningServices has the same structure and naming convention.

"InferenceEndpointMinimalTrackedResource": {

But I see at line 24179, that the same swagger has been using definitions from common types, so why not for this resource also? Please use it from common types.

In reply to:<PHONE_NUMBER>

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:20270 in afce89c. [](commit_id = afce89cf3ee90a68ca8cf9c256737be82bb0ea4e, deletion_comment = False)

"InferenceGroupMinimalTrackedResourceWithSku": {

Same here, I can see many other resources in this same mfe.json using TrackedResource etc. from common types.

In reply to:<PHONE_NUMBER>

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:20389 in afce89c. [](commit_id = afce89cf3ee90a68ca8cf9c256737be82bb0ea4e, deletion_comment = False)

      "x-nullable": true

As long as the upper level definition calls out the "required" properties, this x-nullable is redundant, so it can skipped to define explicitly for all properties.
Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:25218 in afce89c. [](commit_id = afce89c, deletion_comment = False)

@visingla-ms this is coming from the common Microsoft.MachineLearningServices RP implementation and is there for all the resources in this RP. After talking to the RP owners it will have some side effects and would be better to avoid

What kind of side effects here?

      "description": "Description of the endpoint deployment.",

This being base for multiple other property bags, endpoint word is not right in each context, right?

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:25487 in 907011c. [](commit_id = 907011ca3bd0ab6a38b7eb5abf38d42a427471c9, deletion_comment = False)

      "additionalProperties": {

The use of additionalProperties is not allowed, specifically, when getting it as input from users. What is the purpose of this field?
Even if it is being used in other resource types so far, it is no longer recommended for newer types.

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:25494 in 907011c. [](commit_id = 907011ca3bd0ab6a38b7eb5abf38d42a427471c9, deletion_comment = False)

TrackedResource

@visingla-ms
TrackedResource has all properties like identity, sku which are not relevant for many resources. All resources just added it even if its not needed or supported. I refactored it so that Identity and sku are extended properties and resources can decide if they need them or not.

Discussed in the office hour about the API and models. cc @Suhas Rao

In reply to:<PHONE_NUMBER>

    "properties": {

For this RP all resources has properties.properties. For this RP to be consistent we need this for this resource as well

In reply to:<PHONE_NUMBER>

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:25507 in afce89c. [](commit_id = afce89cf3ee90a68ca8cf9c256737be82bb0ea4e, deletion_comment = False)

"InferenceEndpointMinimalTrackedResource": {

Updated

In reply to:<PHONE_NUMBER>

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:20270 in afce89c. [](commit_id = afce89cf3ee90a68ca8cf9c256737be82bb0ea4e, deletion_comment = False)

"InferenceGroupMinimalTrackedResourceWithSku": {

Updated

In reply to:<PHONE_NUMBER>

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:20389 in afce89c. [](commit_id = afce89cf3ee90a68ca8cf9c256737be82bb0ea4e, deletion_comment = False)

Discussed this in ARM office hours. RP owner has an active work to address this for all resources in the RP as its coming from the common swagger generation.
cc @Suhas Rao

In reply to:<PHONE_NUMBER>

      "additionalProperties": {

@raosuhas we need a Dictionary<string,string> in our contract and swagger adds this during generation, is this something which can be omitted ?

In reply to:<PHONE_NUMBER>

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:25494 in 907011c. [](commit_id = 907011ca3bd0ab6a38b7eb5abf38d42a427471c9, deletion_comment = False)

      "additionalProperties": {

This is similar to environmentVariables

In reply to:<PHONE_NUMBER>

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:25494 in 907011c. [](commit_id = 907011ca3bd0ab6a38b7eb5abf38d42a427471c9, deletion_comment = False)

      "additionalProperties": {

This is not recommended at all since these additional properties do not work well with the arm tooling since the schema is not defined. I see you have scheduled one more discussion in the office hours so we can discuss there.

In reply to:<PHONE_NUMBER>

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:25494 in 907011c. [](commit_id = 907011ca3bd0ab6a38b7eb5abf38d42a427471c9, deletion_comment = False)

/pr requestmerge

      "additionalProperties": {

As discussed in office hours we can go with this.

In reply to:<PHONE_NUMBER>

Refers to: specification/machinelearningservices/resource-manager/Microsoft.MachineLearningServices/preview/2023-08-01-preview/mfe.json:25494 in 907011c. [](commit_id = 907011ca3bd0ab6a38b7eb5abf38d42a427471c9, deletion_comment = False)


Add better conditional functionality

Make it so that conditionals & options can be nested inside conditionals.

Was this updated to support nested conditionals? If so can you provide me an example please, I can't seem to do it

Hi @iamw00t, thanks for the question! Nested conditionals do now work. Example:
https://runkit.com/nebrelbug/squirrelly-nested-conditionals
Let me know if this solves your problem!


Posts per user

Currently any user logging in will see all the posts of any user (even though each post is correctly associated with the user that created it).
Is this the expected behaviour?
I'd be happy to to PR a fix if you consider it a bug, or pr a feature to add a config option so you can only see your own posts.
Thanks :)

Thanks for offering a PR! That fix will actually be included in the v4.3 release coming up soon.
The updated controller response can be seen here: https://github.com/cnvs/canvas/blob/develop/src/Http/Controllers/PostController.php#L23

Oh ok, perfect. Thanks!


unix c sample for Rolling Spider

Hey,
I wanted to play with the rolling spider but there is no c sample for it.
I tried to start with the JumpingSumoPiloting and modify it, but I have trouble to deal with BLE. (and my c is old)
A sample for that would be highly appreciated!

Hi,
You have a contribution sample which deals with RollingSpider on MacOS system. You can use this sample and change the library used to handle the BLE connection (on MacOS it is CoreBluetooth).
Best regards,
Djavan

In fact, this sample is in Objective C, so it won't help.
So you will need to use a library that handles Bluetooth Low Energy and adapt the JumpingSumo sample to connect to a RollingSpider (for this last part, you can see the Rolling Spider samples on iOS, Android or MacOS).

Thanks for the help!
I'll look for BLE lib.

Hi,
Do you achieve to connect the Rolling Spider to your computer through SDK ?
I am also looking for an unix sample.
Thanks


Update CloudSql sample to .NET core 2.0.

Change-Id: I265af8d9de8c990aacb8bee66a19353099398834

The Windows test failure is unrelated.


[5.3] Allow reserved words as table name in sqlite

When using sqlite the below fails as group is a reserved word.
Schema::getColumnListing('group');

Thank you for the suggestion @fernandobandeira. This has now been done.


Padding and margins in the archive wizard are wrong

The archive wizard has been redesigned and this is no longer relevant.


Any possible to have an English version?

@LinuxSuRen it is easily available to find on github; https://github.com/molly/manager-README


Allow fallback on value package.rust-src if XARGO_RUST_SRC doesn't exist

This allows for including a package table in Xargo.toml, which optionally can contain a rust-src string specifying a rust source path in lieu of the existence of the XARGO_RUST_SRC environment variable.
Example Xargo.toml:
[package]
rust-src = "/home/jam/a/dev/rust-skyline/rust-std-skyline/src"

[dependencies.std]
stage = 0

@jam1garner thanks for the PR!
I have to say however, that this feels rather ad-hoc. Could you talk a bit about why you want this new feature, and why the [package] section is the best one for this?

The CI failure seems to also occur on master, but I haven't been able to reproduce it locally yet (still on it). It worked fine a few weeks ago when the last PR landed; might be a rustc regression.

So my motivation for this is, admittedly, somewhat ad-hoc in nature. After having a lot of issues with git (primarily upstream issues from cargo and libgit2), I've found builds to be easier for users to reproduce through XARGO_RUST_SRC, but given I:

Don't want to further complicate the build process
Don't want to be dependent on something like cargo-make
Would rather not use a introduce a makefile or shell script or anything along those lines

I can't really set the Rust source path. Having a more permanent per-project means of configuring this felt appropriate.
As far as why the [package] section:

Consistency with Cargo.toml
Indicates that it is a package-level configuration
Root-level string configurations in toml seem to not be idiomatic (at least from what I've seen from usage of tomls in the Rust community)
Xargo's toml doesn't seem to have any top-level configuration yet (unless I'm missing something, I didn't do the deepest dive on the code) and having top-level configurations being "loose" feels both subjectively wrong and a bit short-sighted, as if any other such configurations are added they'd probably want to be grouped in some manner

I'm open to any suggestions as to how to better integrate something that serves these needs while fitting the existing structure of the project, but if this style of change is just not a good fit for Xargo I certainly don't mind if I have to continuously maintain this soft fork for my users.
Regardless, thanks for taking time to consider my PR!

After having a lot of issues with git (primarily upstream issues from cargo and libgit2), I've found builds to be easier for users to reproduce through XARGO_RUST_SRC

I am very confused... you are working around cargo issues by using xargo, but would not otherwise need xargo? Do you have a reference for where these upstream issues you mentioned are tracked? Seems better to fix them than to accumulate more hacks elsewhere in the ecosystem. ;)
Also your example Xargo.toml does not look very portable; what kind of setup do you envision where the same XARGO_RUST_SRC will work on many different machines? That would be my other concern -- typically the exact location where the sources reside is different from platform to platform and even from machine to machine, so having it in a version-controlled file seems counterproductive.

Xargo's toml doesn't seem to have any top-level configuration yet

Yeah and that is exactly why I am wary of adding one, in this stage of xargo (maintenance-only, I am here mostly because I care about xargo working for the sake of miri.)

I am very confused... you are working around cargo issues by using xargo, but would not otherwise need xargo?

I am using xargo for providing an stdlib implementation for an otherwise unsupported platform. I was mentioning my motivation for this PR, not for using xargo in general.

Do you have a reference for where these upstream issues you mentioned are tracked?

Yes, not having shallow clones is actually the main issue that comes to mind -- rust-lang/cargo#1171

Seems better to fix them than to accumulate more hacks elsewhere in the ecosystem. ;)

Y'know what? Fair. I'm afraid I don't quite have the time or motivation to try and make such large contributions to libgit2 (and then cargo) as would be required to push this along while the issue is still relevant to me. (Which, to be clear, is on me_

Also your example Xargo.toml does not look very portable; what kind of setup do you envision where the same XARGO_RUST_SRC will work on many different machines? That would be my other concern -- typically the exact location where the sources reside is different from platform to platform and even from machine to machine, so having it in a version-controlled file seems counterproductive.

I mean yeah of course absolute paths aren't robust (admittedly the example I gave in the original comment was just the output of pwd that I had thrown into my toml for testing). What I actually use now is:
[package]
rust-src = "../rust-std-skyline-squashed/src"

The idea is that, for my use case, a user has a lot of projects linking against the same libstd and would like to ensure they are sharing the same copy (to save space and for control over updating). And, for other projects, including the rust source a submodule is reasonable.

I am using xargo for providing an stdlib implementation for an otherwise unsupported platform. I was mentioning my motivation for this PR, not for using xargo in general.

That is very useful information, thanks. Indeed it seems quite reasonable to not rely on xargo figuring out where the normal rust std source are as those are not very useful to you anyway. Suddenly it feels much less like a hack. ;)
Is rust-std-skyline-squashed in a git repo somewhere to look at, just to get a feel for it? You mention "including the rust source as a submodule"; I am not sure if you literally mean the full rustc repo with patches or something that just contains whatever libstd needs.

The idea is that, for my use case, a user has a lot of projects linking against the same libstd and would like to ensure they are sharing the same copy (to save space and for control over updating). And, for other projects, including the rust source a submodule is reasonable.

Okay, so (for the cases where you don't use submodules) you are expecting the user to perform some setup steps to get a matching folder layout. Makes sense.
Honestly the submodule case sounds even more convincing to me, that could then even be entirely self-contained: git clone, submodule setup, xargo build, done.

Is rust-std-skyline-squashed in a git repo somewhere to look at, just to get a feel for it?

Yep! you can find it here: https://github.com/jam1garner/rust-std-skyline-squashed, it's a Github Actions squashed repo created from here: https://github.com/jam1garner/rust-std-skyline. Honestly it's nothing special, just a fork + squash of the rust-lang/rust repo.

Okay, so (for the cases where you don't use submodules) you are expecting the user to perform some setup steps to get a matching folder layout.

Yep!

Honestly the submodule case sounds even more convincing to me, that could then even be entirely self-contained: git clone, submodule setup, xargo build, done.

I certainly agree. If I didn't expect people to have a g good number of projects at once depending on my stdlib, I would absolutely have gone that route.

Yep! you can find it here: https://github.com/jam1garner/rust-std-skyline-squashed, it's a Github Actions squashed repo created from here: https://github.com/jam1garner/rust-std-skyline. Honestly it's nothing special, just a fork + squash of the rust-lang/rust repo.

Interesting.
So, assuming the cargo issue with shallow clones wouldn't exist, what would you do instead? You said this motivates having control over the source location in Xargo.toml, but to me it seems like even if you could use https://github.com/jam1garner/rust-std-skyline, you would have all the same problems?

Wow I had no idea there are xargo wrappers out there, let alone several of them... I hope they all have appropriate warnings that they rely on a tool that's basically unmaintained.^^


Problem: there are no events for invalid blocks

Solution: update the documentation to reflect this. I've also removed
the documentation about the event plugin API. That part needs to be
refactored to work properly with BigchainDB 2.0. We can reintroduce it
later.

I built the docs from this branch on my local machine and that worked fine.

I also have a question about process. How should we remind ourselves to refactor the Event Plugin API (and update/republish the associated docs)?

It can be a nice test to see if this feature is actually used :)

Creating a new issue seems like the wrong answer. Should we create a BEP?

I think a BEP is too much for this.

@kansi Can we approve and merge this PR now?


Add an error predicate to complement success

This PR adds an error? predicate to complement success?.

Looks good!
Could you rebase or merge with master?

I've rebased and pushed.


Application secrets management

This PR implements secrets management as defined in epic #190.
Instead of creating PRs for each issue, I've decided to batch up the entire set applications changes in one PR, since it's only functional once the entire task list has been implemented.
Azure environment changes will end up in a separate PR, as environment changes will need to be deployed out prior the application code.
Changes

Implements a CredentialService: #293

This ticket defines out the base inheritance strategy for both the CredentialService and Credential objects
The CredentialService will store the credential object as serialized JSON in whatever secret store is used
The secret store can be changed and configured with the environment variable CREDENTIAL_STORAGE_METHOD
The names of the classes have been shorted from the proposal for brevity and clarity

Implements a Hashicorp Vault version of the CredentialService: #294

Implements Hashicorp Vault API using the existing HTTP library we're using, fuel
Adds a dependency to mock-fuel to enable easier testing
Documents in getting_started.md how to use the local version of Hashicorp Vault
Fixes some issues with unsealing and initializing the Vault from my earlier PR #325 (anyone who initialized a Vault prior to this PR will need to re-initialize their Vault)

Implements Azure Key Vault version of the CredentialService: #295

Adds an environment variable CREDENTIAL_KEY_VAULT_NAME to define the Azure Key Vault name
Adds a dependency to azure-security-keyvault-secrets and azure-identity to use Azure's client for Key Vault

Connects the SftpTransport to the CredentialService #304

Adds additional logging when credential do not exist in the secret store
Removes the existing environment variable in docker-compose.yml

Updates the SFTP-SETUP.md with directions on how to use the secret store #305

TLDR; What Do I Care About as a Developer?

Documented how to use the secrets manager in getting_started.md.

If you don't do anything, you'll use an in-memory version of the secret store that will not persist, which may or may not be okay for the type of development you're doing.
If you're using docker-compose, you need to run this command once from the prime-router folder: touch .vault/env/.env.local
You will need to follow the directions in getting_started.md to re-initialize your Vault, as the earlier code I committed did not work as expected.

New CLI command prime create-credential for generate credential JSON or persisting directly to the secret store
Updated SFTP-SETUP.md with directions on how to use the secret store instead of environment variables
Added a dependency mock-fuel to enable easier testing of HTTP calls using fuel.

Areas I'm Looking for Feedback

This is my first ever Kotlin code written (although I come from a Java background). Am I following best practices for Kotlin and team standards?
Names have been changes for brevity from the proposal. Do the shorter names make sense, or should I go back to the more verbose ConnectionCredential* naming?
My strategy for dependency injection. I'm finding Kotlin has a lot of nice features built right into the language and this was one of the cool ones.
Logging of credential access.
Any other areas that need a specific call out, I'll add a comment in the code.

Checklist

[x] Tested locally?
[x] Added new dependencies? Yes, mock-fuel, azure-security-keyvault-secrets, azure-identity
[x] Updated the docs? Yes, getting_started.md, SFTP-SETUP.md. Also added a helpful comment in docker-compose.yml for first-time errors that occur.
[x] Added a test?
[ ] Did you check for sensitive data, and remove any?
[x] Are additional approvals needed for this change? Yes, this is a large change. We should get multiple approvals and take care in rolling this out.
[ ] Are there potential vulnerabilities or licensing issues with any new dependencies introduced?

To Be Done

Before this can be deployed, Key Vaults need to be stood up in Azure and secrets migrated to them.

This will be handled in the remaining tasks in epic #190

This PR is ready for review, but do not merge! Azure changes are required for this to work when deployed out.

This PR is ready for review, but do not merge! Azure changes are required for this to work when deployed out.


Add technical charter. Closes #81.

Signed-off-by: Daniel Krook<EMAIL_ADDRESS>Describe at a high level the solution you're providing
Uploaded the Technical Charter document to supplement the contribution guidelines.
Is this a patch, a minor version change, or a major version change
Minor addition, no code.
Is this related to an open issue?
#81

I also ran a "format Markdown" command in VSCode, which is why you see some spacing changes.


Automate hash scans

🗣 Description
Create extra file to automate the IOC Hash scans.

This script currently is only valid for Debian and Fedora systems.
Requires AWS_CREDENTIALS_FILE and AWS_REGION environmental variables to already be set.
Assumes it will be run from ioc-scanner/extras
Takes a file with a list of instance id's in separate lines
Requires declaring the AWS_PROFILE as an argument
Starts port forwarding on the local system. Then it verifies that netcat is installed in the instance and starts netcat listening on port 6666. It uploads the latest copy of ioc_scanner.py with the latest hashes to the instance. Then it executes ioc_scanner.py and directs the output to a local log file.

💭 Motivation and context
The current process requires manually uploading the ioc_scanner.py file to each instance one at a time. This is a laborious method and not scaleable.
🧪 Testing
This was tested using the default test blobs in ioc_scanner.py.
✅ Pre-approval checklist

[x] This PR has an informative and human-readable title.
[x] Changes are limited to a single goal - eschew scope creep!
[x] All relevant type-of-change labels have been added.
[x] I have read the CONTRIBUTING document.
[x] These code changes follow cisagov code standards.
[x] All new and existing tests pass.

For the same reasons as discussed in #53, this PR will not require a version change to this repo, so I deleted the "Pre-merge" and "Post-merge" checklist sections in the PR description.

@bra1ncramp Just pinging on this PR so that it doesn't get forgotten.  It's good stuff- we should try to get it across the finish line soon.

@bra1ncramp - Are you running pre-commit locally?  That should have automatically caught the correction I made in commit 93e1b32.

@bra1ncramp - Are you running pre-commit locally? It should have automatically caught the correction I made in commit 93e1b32.

@bra1ncramp - Are you running pre-commit locally? It should have automatically caught the linting error you committed in e21a303227373d33b7b8b48d6a8d71c335fa419d.

@bra1ncramp - Are you running pre-commit locally? It should have automatically caught the correction I made in commit 93e1b32.

@bra1ncramp - Are you running pre-commit locally? It should have automatically caught the linting error you committed in e21a303.

~What's the error? pre-commit isn't showing me any error.~
I was running it wrong. I should have run pre-commit run --all-files instead of just pre-commit

You should run pre-commit install to install the git hook.  Then pre-commit will check your changes before you are allowed to commit them.  See the instructions here, for example.


Adjust "de novo" preset

Is your feature request related to a problem? Please describe.
When using the current preset “de novo” the index and the parents are set to 0/0. This will exclude de novo hemizygous variants.
Describe the solution you'd like
Use the setting: variant (index), non-variant or 0/0 (parents).
With this settings we would also find the de novo x-chromosomal variants in males (index=1/1 and parents: 0/0 are missed by currently used de novo preset and also not displayed by x-chromosomal settings (index 1/1, mother 0/1).
Describe alternatives you've considered
N/A
Additional context

From internal helpdesk.

Are there plans to make presets in general configurable?
Specifically LB deals mostly with mono-exomes and a larger focus on panel assessments. It would be great if teams or individual investigators could add these as other presets and possibly remove the current default presets.

@xiamaz No. The settings have been agreed on with N.E. and are part of the LB/Charite SOP to the best of my knowledge.

We now have configurable presets.


Make use of common environment variables consistent

Presently the AWS service configuration reuses variables for AWS access key and secret key for both the SQS and S3 services. However, the Azure and GCP service configurations always define unique variables for each service. See the links in the Environment Variables section of the README.md to compare.
We should have a consistent and simple policy for reuse of common parameters. "Consistency" of course is in the mind of the beholder, and requires an understanding of how the variables are used in each service.
For GCP consider consolidating some of the variables, like URIs, which are unlikely to change. Verify with GCP rep.

Not reusing environment variables at present. All services have unique environment variable names.


Update MD file on new branch 2017-11-24_05-35-40

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update training.py

add _add_tags method
Description
This adds additional tags to the wandb logger, including modelforge version and dataset/potential name as well as the properties present in the loss function.
Note: this should have been added with the last PR, but something seemed to have gone wrong during refactoring.
Status

[ ] Ready to go

Codecov Report
Attention: Patch coverage is 12.50000% with 7 lines in your changes missing coverage. Please review.

Project coverage is 83.48%. Comparing base (19a5c24) to head (cde505c).
Report is 36 commits behind head on main.

Additional details and impacted files


data leakage problem in your model

The design of your adjacency matrix adj_mats_orig and the way you split the train/test set will cause a huge data leakage problem in your training, because your validation and test set is created independently for gene_adj and gene_adj.transpose(copy=True), and therefore the edges from the validation / test set in gene_adj is actually included in the training set of gene_adj.transpose(copy=True).
Same problem goes for the train / validate set between gene_drug_adj and drug_gene_adj. The validation edges from gene_drug_adj are actually used for training  in drug_gene_adj, and vise versa.
Could you please clarify?
Thanks!
Originally posted by @hurleyLi in https://github.com/marinkaz/decagon/issues/7#issuecomment-519645774

Hello @hurleyLi , I have the same problem as you at first, but now I think this is not a big problem because what we want to predict is between drug nodes, which means p-p and p-d edge doesn't matter

Hello @hurleyLi , I have the same problem as you at first, but now I think this is not a big problem because what we want to predict is between drug nodes, which means p-p and p-d edge doesn't matter


Fix rails 5 deprication warnings

Fix these annoying deprecation warnings:
DEPRECATION WARNING: before_filter is deprecated and will be removed in Rails 5.1. Use before_action instead. (called from get at /home/oleg/.rbenv/versions/2.3.0/lib64/ruby/2.3.0/forwardable.rb:184)
DEPRECATION WARNING: env is deprecated and will be removed from Rails 5.1. (called from get at /home/oleg/.rbenv/versions/2.3.0/lib64/ruby/2.3.0/forwardable.rb:184)

So, what about this? Will we merge it or drop rails3 support first?

I think we should drop Rails 3 support for the next release. Is that something you might be interested in doing?

Well, I can try


connections of road/lane at junction in OpenDrive file are missing

In the OpenDrive map xodr files (at least in town01 and town02), I found some links/connections are missing, especially at the junction. To my understanding, a connection should be defined at both ways.
For example at one of the junctions of town01, there are 3 missing connections

Road 6 -> Road 68
Road 68 -> Road 7
Road 6 ->Road 68

Although in the userData tag, it explicitly clarities the driving direction. But shouldn't we still need the connections? Because it's indeed connected.

Or are the connections completed as long as I follow the right-handed driving direction?


Log if no WidgetPod::set_layout_rect before event

This will hopefully make an easy mistake harder to make.
motivated by this discussion on zulip

@Finnerale good catch, I've updated so that we don't log on WindowConnected and Size, which can arrive before a layout pass 😅

@cmyr Did you push it?

just now. :)


Double tap zoom is not working

hi admin please enable also double tap zoom feature

There is an issue with the double tap zoom, and it was disabled in version 1.1.0. I can possibly add an option to enable it, but overall I found the double tap zoom didn't work very well.


Make vstest.console, and datacollector upgrade across major .NET version

Description
vstest.console and datacollector are our tools and they should be able to run on any .NET version from netcoreapp2.1 onwards. But in the cli, and portable packages we ship runtime config with them that ties them to netcoreapp2.1.
dotnet SDK rewrites our runtime.config.json to use the same version as what the SDK is, but our nugets don't have that change, and tooling authors work around this by setting DOTNET_ROLL_FORWARD policy by environment variables, which inherits downwards to testhost where that policy is undesirable.
Setting RollForward in our project will emit it in runtimeconfig.json and will tell vstest.console and datacollector and allows us to upgrade to a newer runtime even across major version. This won't upgrade to pre-releases, and won't upgrade to the latest version available, because we currently have no way to rewrite this option in the actual SDK shipment.

My only concern here is what dotnet SDK actually does with our runtimeconfig.json and if we can strip the preference there, because we want to keep it working as is.
What users currently see:
C:\t> dotnet "C:\Users\jajares\Downloads\
		microsoft.testplatform.portable.17.2.0-preview-20220401-08\tools\
		  netcoreapp2.1\vstest.console.dll"

You must install or update .NET to run this application.

App: C:\Users\jajares\Downloads\microsoft.testplatform.portable.17.2.0-preview-20220401-08\tools\netcoreapp2.1\vstest.console.dll
Architecture: x64
Framework: 'Microsoft.NETCore.App', version '2.1.0' (x64)
.NET location: C:\Program Files\dotnet\

The following frameworks were found:
  3.0.3 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

This is what they're doing https://github.com/dotnet/sdk/blob/main/src/Layout/redist/targets/GenerateLayout.targets#L403-L428

Updated the description and code to use Major, instead of LatestMajor, so we can ship this asap.
No shipments in sdk use LatestMajor, except for dotnet-format which is a dotnet-tool.

/fyi @rouke-broersma @peterwald this will ship in .NET 7, and TP17.3. You both have DOTNET_ROLL_FORWARD policy in place to work around this.

Cool! I am liking these recent improvements to the portable/client-wrapper workload :)

@nohwnd Do we need .net7 AND TP17.3 for this to work? I'm currently testing with TP17.3 and .net6 and it's failing with this message:
[11:20:02 DBG] Runner 0: You must install or update .NET to run this application. (VsTest error)
[11:20:02 DBG] Runner 0:  (VsTest error)
[11:20:02 DBG] Runner 0: App: /home/vsts/work/1/.nuget/packages/microsoft.testplatform.testhost/17.3.2/lib/netcoreapp2.1/testhost.dll (VsTest error)
[11:20:02 DBG] Runner 0: Architecture: x64 (VsTest error)
[11:20:02 DBG] Runner 0: Framework: 'Microsoft.NETCore.App', version '3.1.0' (x64) (VsTest error)
[11:20:02 DBG] Runner 0: .NET location: /opt/hostedtoolcache/dotnet/ (VsTest error)
[11:20:02 DBG] Runner 0:  (VsTest error)
[11:20:02 DBG] Runner 0: The following frameworks were found: (VsTest error)
[11:20:02 DBG] Runner 0:   6.0.9 at [/opt/hostedtoolcache/dotnet/shared/Microsoft.NETCore.App] (VsTest error)
[11:20:02 DBG] Runner 0:  (VsTest error)
[11:20:02 DBG] Runner 0: Learn about framework resolution: (VsTest error)
[11:20:02 DBG] Runner 0: https://aka.ms/dotnet/app-launch-failed (VsTest error)
[11:20:02 DBG] Runner 0:  (VsTest error)
[11:20:02 DBG] Runner 0: To install missing framework, download: (VsTest error)
[11:20:02 DBG] Runner 0: https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=3.1.0&arch=x64&rid=ubuntu.20.04-x64 (VsTest error)


Drift process

adds DriftProcess to cover also deterministic dynamical systems.

Codecov Report

Merging #35 (1733bce) into master (2fbf4da) will increase coverage by 1.44%.
The diff coverage is 55.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##           master      #35      +/-   ##
==========================================
+ Coverage   36.39%   37.84%   +1.44%
==========================================
  Files          10       10
  Lines        1242     1279      +37
==========================================
+ Hits          452      484      +32
- Misses        790      795       +5

Impacted Files
Coverage Δ

src/utils.jl
69.95% <0.00%> (+1.61%)
:arrow_up:

src/processes.jl
46.39% <75.00%> (+1.23%)
:arrow_up:

src/symbolics.jl
89.02% <100.00%> (+1.18%)
:arrow_up:

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


clean up unused usages

Signed-off-by: SchrodingerZhu<EMAIL_ADDRESS>This PR makes UNUSED as a function marked by [[maybe_unused]]. This enables us to put UNUSED to namespace without pollute global macros.

I haven't seen this idiom before, but I really like it.  Unfortunately, the PR missed adding the namespaced version in a few places so it's failing CI.  Looks good once those are fixed though.

There is one issue with msvc, however:
With always inline, GCC can elim the symbol even at debugging:
https://godbolt.org/z/5z8qE9Kqf
However, MSVC may generate some junk code:
https://godbolt.org/z/so1e4EsPj

I think that is fine for there to be a few artifacts in Debug builds.  I alway struggle to read the assembly unless it has been optimised anyway ;-)


Wish: FRR routing daemon

My machine every now and then loose the OSPF and BGP routing.
Your API is great and my wish is to add endpoints for the FRR daemon.
/GET status for each daemon
/GET routes (for each damon)
/POST restart of the FRR service
/POST restart of each daemon
Thanks

Hey!
Thanks for the feature request. I'll look into these features when I get a chance and see what it will take to incorporate them into endpoints. I'll keep this issue updated as progress is made.
Thanks again!


pkg-config --version exits with code 29

Running pkg-config --version fails with "Illegal instruction".
I'd like to report the version of pkg-config where this error happens, but...

Hmm, was this with one of the w64devkit 1.23.0 releases. Built yourself
from master? What version of Windows? The full source is distributed with
the release under src/. The version string is at the top, which I expect
is 0.33.1. You can also use that to get more detailed information like a
stack trace: Use the build command in the source header, but add -g3 and
run under gdb.
I'm unable to reproduce even in a fresh installation. Perhaps one of the
environment variables isn't handled properly. I'm interested in knowing
their values on your system when the crash occurs, if set at all:

PKG_CONFIG_PATH
PKG_CONFIG_LIBDIR
PKG_CONFIG_TOP_BUILD_DIR
PKG_CONFIG_ALLOW_SYSTEM_CFLAGS
PKG_CONFIG_ALLOW_SYSTEM_LIBS

Another possibility is some mishandling of GetModuleFileNameW, so if it's
installed under an unusual path, that would be interesting as well.
Do other commands work? For example, commands that behave differently but
don't require .pc files:
$ pkg-config --help
$ pkg-config --modversion pkg-config
$ pkg-config --variable pc_path pkg-config
Also interesting to know would be any unusual environment under which it
might be running (e.g. ConEmu).
Lastly, and least likely, if it's the 32-bit version, the host CPU must
support SSE2 (i.e. at least a Pentium 4), or such errors are likely.

Hey! Sorry for the long delay.
I had compiled w64devkit myself, so I tried recompiling from source with w64devkit GCC, and now it works. I noticed that when I compile w64devkit, it happens that the compilation crashes many times due to random segfaults or internal errors, so I suspect that my RAM is faulty, and there's one bug that unfortunately resulted in a malformed program.
Sorry for the false alarm!