Change mobile Readme to include screenshots, and update mobile code

Purpose
*Add sample screenshots to the readme
*Change contract instance code to have centered title instead of left adjusted
*Update contract refresh code so latest contract to be created comes to the top of the list
Does this introduce a breaking change?
[ ] Yes
[x] No

Pull Request Type
[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[x] Documentation content changes
[ ] Other... Please describe:

How to Test

not required

What to Check
*not required
Other Information
*nothing

PR to include README changes and slight changes to mobile code

closing PR because a one liner bug discovered... reopening.


Added new boilerplate, and fixed some errors

closes #16

Map components aren't loading, but I assume that's not supposed to be implemented in the new frontend yet


feat: containerize application

This PR will

introduce a Dockerfile to build a container image for the app

based on official php:httpd container image (Debian based)
everything runs rootless (port 8080 for the webapp)
has options to override the default timezone, set the default language and automatically create an admin user
runs the required cronjob every 5 minutes (although I suppose we could make that adjustable as well, if you prefer)

introduce a Github Workflow to directly build the container image, both as amd64 and arm64 images

either manually (gets tagged with dev then)
or when pushing a semver tag like v0.0.1 (gets tagged with latest and v0.0.1 then)

Let me review this implementation 😊
I'm using docker in some other projects like https://github.com/eusonlito/Password-Manager and I would like to do some similiar.
Regards!

Ah, okay. Haven't seen that one 🙈 If you want me to change something, please let me know.
Actually had already started on this, right after your project introduction on Reddit, last year. Just couldn't make friends with composer 😂

Please be careful with php artisan serve --host=<IP_ADDRESS> --port=80, that's fine for development, but shouldn't be exposed to the internet, as that exposes your PHP unprotected instance, which is running with superuser privileges.

As far as I know, running php as root inside a docker instance is not a security issue per se, it all depends on the code you run. I'm missing something?

https://www.php.net/manual/en/features.commandline.webserver.php

This web server is designed to aid application development. It may also be useful for testing purposes or for application demonstrations that are run in controlled environments. It is not intended to be a full-featured web server. It should not be used on a public network.

Yes, I know, but I'm using the php artisan serve in a lot of projects without problem :)
Also, as almost docker environments, you must set a web server as reverse proxy to add full server web server features (ssl, domains, etc...) in front the container.
You can test the new (and hope finally) version :)

I don't think I'll be able to run your version in production. And so probably shouldn't anybody else, as that's a security issue waiting to happen :(

the integrated php webserver isn't supposed to be exposed to the internet (even upstream says so)

it even needlessly runs as a privileged user

the container brings too many unneeded dependencies (apt-utils, htop, vim, procps, just to name a few)

there's also no cache managing for /root/.composer for example

the Dockerfile references composer:latest. Referencing latest is bad practice.
Running the entire thing with a permanent memory_limit of 2G also isn't the best idea

That's a development container, not ready for production use. Please look up some container guidelines by the NSA and the german BSI.
Also, just comparing our images
$ docker image ls | grep gps-tracker
gps-tracker   yours      8d932efb1e79   12 minutes ago   938MB
gps-tracker   mine       d7f8b9eaa800   21 minutes ago   557MB

938MB is wayy to much. That's a looot of overhead, if one wants to run multiple replicas of it.
Running it through aquasecurity/trivy also doesn't look good.

Ok, I will work more on it based on yours recomendations.
Maybe the size are required dependencies that you aren't loaded? My additional dependencies are all some additional kb.
Anyway thanks for your work and help.

Finally:
docker image ls | grep gpstracker

gpstracker-app   latest    351eed5f424b   20 minutes ago   657MB

sudo trivy image gpstracker-app --ignore-unfixed

2023-02-11T19:27:01.241+0100	INFO	Vulnerability scanning is enabled
2023-02-11T19:27:01.241+0100	INFO	Secret scanning is enabled
2023-02-11T19:27:01.241+0100	INFO	If your scanning is slow, please try '--scanners vuln' to disable secret scanning
2023-02-11T19:27:01.241+0100	INFO	Please see also https://aquasecurity.github.io/trivy/v0.37/docs/secret/scanning/#recommendation for faster secret detection
2023-02-11T19:27:01.254+0100	INFO	Detected OS: debian
2023-02-11T19:27:01.254+0100	INFO	Detecting Debian vulnerabilities...
2023-02-11T19:27:01.283+0100	INFO	Number of language-specific files: 1
2023-02-11T19:27:01.283+0100	INFO	Detecting composer vulnerabilities...

gpstracker-app (debian 11.6)

Total: 0 (UNKNOWN: 0, LOW: 0, MEDIUM: 0, HIGH: 0, CRITICAL: 0)

Thanks for your advices for the improvement of Docker integration.


Add Phrase.com (formerly PhraseApp)

Good news, they now have posted pricing for SSO. Bad news, it's high as hell.


The Wonderful Wizard of Haag

Prerequisites
This PR requires the latest CIM 4.20 to be installed. In addition, whatever EDR product in use, the TA must utilize the latest original_file_name field to use the enhanced datamodel queries found here.
Updated Analytics

Suspicious Rundll32 Rename
Suspicious Rundll32 startw
Detect Renamed RClone
Detect Renamed PSExec
Detect Renamed 7-Zip
Detect HTML Help Renamed
Detect microsoft.workflow.compiler.exe rename
Suspicious microsoft workflow compiler usage
Detect Renamed PSExec
Detect Renamed WinRAR
Detect SharpHound Usage

To Be Resolved

Detect renamed msbuild execution

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect Renamed rundll32.exe Rename :white_check_mark:

diskUsage: 593920
runDuration: 9.233s
scanCount: 13107

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect renamed msbuild execution :x:

diskUsage: 593920
runDuration: 3.685s
scanCount: 3193

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect renamed msbuild execution :x:

diskUsage: 593920
runDuration: 3.962s
scanCount: 3193

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Suspicious Rundll32 startw :white_check_mark:

diskUsage: 491520
runDuration: 8.812s
scanCount: 13107

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect Renamed PSExec :white_check_mark:

diskUsage: 602112
runDuration: 6.221s
scanCount: 7980

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect Renamed WinRAR :x:

diskUsage: 176128
runDuration: 0.005s
scanCount: 0

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect Renamed WinRAR :x:

diskUsage: 176128
runDuration: 0.005s
scanCount: 0

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect Renamed 7-Zip :white_check_mark:

diskUsage: 598016
runDuration: 10.562s
scanCount: 17070

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect microsoft.workflow.compiler.exe rename :x:

diskUsage: 569344
runDuration: 1.742s
scanCount: 1

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect HTML Help Renamed :x:

diskUsage: 593920
runDuration: 5.165s
scanCount: 6603

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect HTML Help Renamed :white_check_mark:

diskUsage: 598016
runDuration: 4.989s
scanCount: 6603

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect microsoft.workflow.compiler.exe rename :white_check_mark:

diskUsage: 602112
runDuration: 9.346s
scanCount: 14217

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect microsoft.workflow.compiler.exe usage :x:

diskUsage: 479232
runDuration: 2.2560000000000002s
scanCount: 0

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect microsoft.workflow.compiler.exe usage :white_check_mark:

diskUsage: 499712
runDuration: 10.370000000000001s
scanCount: 14217

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect Renamed PSExec :white_check_mark:

diskUsage: 602112
runDuration: 6.042s
scanCount: 7981

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect SharpHound Usage :x:

diskUsage: 491520
runDuration: 6.761s
scanCount: 9406

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect SharpHound Usage :white_check_mark:

diskUsage: 499712
runDuration: 6.421s
scanCount: 9406

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Any Powershell DownloadFile :x:

diskUsage: 516096
runDuration: 13.575000000000001s
scanCount: 21714

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
BCDEdit Failure Recovery Modification :x:

diskUsage: 581632
runDuration: 3.5780000000000003s
scanCount: 66

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Certutil exe certificate extraction :white_check_mark:

diskUsage: 581632
runDuration: 2.274s
scanCount: 13

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Common Ransomware Notes :x:

diskUsage: 495616
runDuration: 1.707s
scanCount: 1

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Account Discovery With Net App :white_check_mark:

diskUsage: 532480
runDuration: 154.967s
scanCount: 295393

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Attempt To Add Certificate To Untrusted Store :white_check_mark:

diskUsage: 598016
runDuration: 6.627s
scanCount: 6565

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Attempted Credential Dump From Registry via Reg exe :white_check_mark:

diskUsage: 651264
runDuration: 7.514s
scanCount: 7007

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Batch File Write to System32 :white_check_mark:

diskUsage: 978944
runDuration: 4.0600000000000005s
scanCount: 504

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
BITS Job Persistence :white_check_mark:

diskUsage: 536576
runDuration: 3.846s
scanCount: 3017

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
BITSAdmin Download File :white_check_mark:

diskUsage: 499712
runDuration: 4.659s
scanCount: 3017

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Create local admin accounts using net exe :white_check_mark:

diskUsage: 618496
runDuration: 6.349s
scanCount: 6394

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Create or delete windows shares using net exe :white_check_mark:

diskUsage: 516096
runDuration: 5.479s
scanCount: 6592

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Creation of Shadow Copy with wmic and powershell :white_check_mark:

diskUsage: 536576
runDuration: 6.4110000000000005s
scanCount: 7013

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Credential Dumping via Copy Command from Shadow Copy :white_check_mark:

diskUsage: 397312
runDuration: 6.273s
scanCount: 7013

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Credential Dumping via Symlink to Shadow Copy :white_check_mark:

diskUsage: 507904
runDuration: 5.891s
scanCount: 7013

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect PsExec With accepteula Flag :x:

diskUsage: 499712
runDuration: 5.344s
scanCount: 6156

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Domain Account Discovery With Net App :white_check_mark:

diskUsage: 614400
runDuration: 6.035s
scanCount: 7259

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect PsExec With accepteula Flag :white_check_mark:

diskUsage: 503808
runDuration: 2.89s
scanCount: 13

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Dump LSASS via procdump :white_check_mark:

diskUsage: 618496
runDuration: 6.66s
scanCount: 7963

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Extract SAM from Registry :white_check_mark:

diskUsage: 520192
runDuration: 6.646s
scanCount: 7007

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Extract SAM from Registry :white_check_mark:

diskUsage: 520192
runDuration: 6.345s
scanCount: 7007

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Processes created by netsh :white_check_mark:

diskUsage: 507904
runDuration: 9.4s
scanCount: 14187

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect Regasm with no Command Line Arguments :white_check_mark:

diskUsage: 499712
runDuration: 4.664s
scanCount: 4460

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect regsvcs with no Command Line Arguments :white_check_mark:

diskUsage: 499712
runDuration: 6.444s
scanCount: 4460

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Suspicious DLLHost no Command Line Arguments :white_check_mark:

diskUsage: 499712
runDuration: 55.548s
scanCount: 104295

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Suspicious GPUpdate no Command Line Arguments :white_check_mark:

diskUsage: 499712
runDuration: 56.248000000000005s
scanCount: 104295

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Suspicious Rundll32 with no Command Line Arguments :white_check_mark:

diskUsage: 499712
runDuration: 9.378s
scanCount: 13366

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Suspicious SearchProtocolHost no Command Line Arguments :white_check_mark:

diskUsage: 495616
runDuration: 55.594s
scanCount: 104295

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Office Document Spawned Child Process To Download :white_check_mark:

diskUsage: 544768
runDuration: 13.835s
scanCount: 22352

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect Renamed PSExec :white_check_mark:

diskUsage: 512000
runDuration: 6.678s
scanCount: 8239

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect Renamed 7-Zip :white_check_mark:

diskUsage: 606208
runDuration: 10.691s
scanCount: 17329

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect Renamed RClone :white_check_mark:

diskUsage: 606208
runDuration: 4.852s
scanCount: 5913

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Winword Spawning Cmd :white_check_mark:

diskUsage: 512000
runDuration: 17.528s
scanCount: 31087

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Winword Spawning PowerShell :white_check_mark:

diskUsage: 536576
runDuration: 17.647000000000002s
scanCount: 31087

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Windows Event Log Cleared :x:

diskUsage: 155648
runDuration: 1.103s
scanCount: 0

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
W3WP Spawning Shell :white_check_mark:

diskUsage: 548864
runDuration: 29.301000000000002s
scanCount: 49891

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Wermgr Process Create Executable File :x:

diskUsage: 937984
runDuration: 221.77s
scanCount: 295393

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect Renamed rundll32.exe Rename :white_check_mark:

diskUsage: 507904
runDuration: 9.041s
scanCount: 13366

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Suspicious Rundll32 dllregisterserver :white_check_mark:

diskUsage: 503808
runDuration: 9.315s
scanCount: 13366

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Detect regsvr32 Registering DLLs from non-standard paths :white_check_mark:

diskUsage: 524288
runDuration: 4.619s
scanCount: 3317

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Suspicious Rundll32 PluginInit :white_check_mark:

diskUsage: 503808
runDuration: 52.182s
scanCount: 98068

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
RunDLL Loading DLL By Ordinal :white_check_mark:

diskUsage: 507904
runDuration: 9.374s
scanCount: 13366

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Remote WMI Command Attempt :white_check_mark:

diskUsage: 499712
runDuration: 5.7940000000000005s
scanCount: 6574

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Remote Process Instantiation via WMI :white_check_mark:

diskUsage: 614400
runDuration: 5.655s
scanCount: 6575

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Recursive Delete of Directory In Batch CMD :white_check_mark:

diskUsage: 614400
runDuration: 2.552s
scanCount: 3

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Process Kill Base On File Path :white_check_mark:

diskUsage: 516096
runDuration:<PHONE_NUMBER>0000002s
scanCount: 271717

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Office Product Spawning CertUtil :white_check_mark:

diskUsage: 528384
runDuration: 4.281s
scanCount: 4596

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Office Product Spawning Wmic :white_check_mark:

diskUsage: 528384
runDuration: 4.4510000000000005s
scanCount: 4596

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
PowerShell Start-BitsTransfer :white_check_mark:

diskUsage: 626688
runDuration: 3.7030000000000003s
scanCount: 3019

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Office Product Spawning Rundll32 with no DLL :white_check_mark:

diskUsage: 528384
runDuration: 3.936s
scanCount: 3672

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Office Product Spawning BITSAdmin :white_check_mark:

diskUsage: 528384
runDuration: 4.587s
scanCount: 4596

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Mshta spawning Rundll32 OR Regsvr32 Process :white_check_mark:

diskUsage: 520192
runDuration: 10.299s
scanCount: 15578

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Office Product Spawn CMD Process :white_check_mark:

diskUsage: 520192
runDuration: 10.079s
scanCount: 15578

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Nishang PowershellTCPOneLine :white_check_mark:

diskUsage: 409600
runDuration: 13.765s
scanCount: 21930

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Office Application Spawn rundll32 process :white_check_mark:

diskUsage: 524288
runDuration: 33.092s
scanCount: 58627

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Office Application Spawn Regsvr32 process :white_check_mark:

diskUsage: 532480
runDuration: 27.949s
scanCount: 51146

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Powershell Disable Security Monitoring :white_check_mark:

diskUsage: 671744
runDuration: 8.038s
scanCount: 10934

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Excessive Usage Of Net App :white_check_mark:

diskUsage: 520192
runDuration: 137.308s
scanCount: 271717

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Office Product Spawning MSHTA :white_check_mark:

diskUsage: 528384
runDuration: 4.484s
scanCount: 4596

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Excessive Service Stop Attempt :white_check_mark:

diskUsage: 528384
runDuration: 135.862s
scanCount: 271717

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
CertUtil With Decode Argument :white_check_mark:

diskUsage: 499712
runDuration: 2.958s
scanCount: 1766

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Batch File Write to System32 :white_check_mark:

diskUsage: 978944
runDuration: 3.787s
scanCount: 504

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Attempt To Stop Security Service :white_check_mark:

diskUsage: 614400
runDuration: 6.034s
scanCount: 7345

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
CertUtil Download With VerifyCtl and Split Arguments :white_check_mark:

diskUsage: 507904
runDuration: 3.398s
scanCount: 2291

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Any Powershell DownloadString :white_check_mark:

diskUsage: 622592
runDuration: 13.648s
scanCount: 21931

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Any Powershell DownloadFile :white_check_mark:

diskUsage: 528384
runDuration: 14.387s
scanCount: 21929

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Allow Network Discovery In Firewall :white_check_mark:

diskUsage: 397312
runDuration: 5.113s
scanCount: 4628

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
CertUtil Download With URLCache and Split Arguments :white_check_mark:

diskUsage: 507904
runDuration: 3.279s
scanCount: 2291

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Malicious PowerShell Process - Connect To Internet With Hidden Window :white_check_mark:

diskUsage: 651264
runDuration: 11.579s
scanCount: 17751

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Malicious PowerShell Process - Encoded Command :white_check_mark:

diskUsage: 626688
runDuration: 5.392s
scanCount: 6238

This PR was created by Automated Detection Testing Service :robot:
Tested detections:
Malicious PowerShell Process With Obfuscation Techniques :white_check_mark:

diskUsage: 548864
runDuration: 17.931s
scanCount: 29946


Features/fix posts page

This is my new pr fix posts page, create Errorboundary component

https://drive.google.com/file/d/1f7hEZVN7eiUnqzQ6HcpIoRQf2hzOSjEN/view?usp=sharing
Don't worry about the rendering of component stack, the create-react-app package has a tool called the react-overlay-error. This shows error messages from the console as an overlay over your app so you can easily check the stack trace and debug.
This won't show up in production mode, it's just a development tool duplicating the normal browser console.


Increase timeout for couchdb_os_process_pool test

Fixes #631

This isn't sufficient to fix it, look at the failing Travis run. Closing for now.


Migration tool fails when experiment is enabled

When I was migrating a package, I enabled the experiment in my analysis_options.yaml:
analyzer:
  enable-experiment:
    - non-nullable

Then I ran dart migrate, which failed because there were now analyzer warnings.
Instead, is it possible to disable the experiment before dart migrate runs the analysis on the project?

We should likely minimally warn the user that they should comment out the opt-in for best results.
However, we likely want our primary use case to be:

people running on a 2.12 SDK (with the flag flipped, and no analyzer opt-in necessary), on a project w/ pre-2.12 pubspec sdk constraints, and
people running on a 2.12 SDK (with the flag flipped, and no analyzer opt-in necessary), on a project w/ 2.12 or greater pubspec sdk constraints

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


Add server capabilities API

What does this PR (Pull Request) do?
Add a new API for creating, reading, and deleting (not updating) server capabilities:
POST /api/1.4/server_capabilities
GET /api/1.4/server_capabilities[?name=<name>]
DELETE /api/1.4/server_capabilities?name=<name>

expected POST body:
{"name": "bar"}

expected POST response:
{
  "alerts": [
    {
      "text": "server capability was created.",
      "level": "success"
    }
  ],
  "response": {
    "name": "bar",
    "lastUpdated": "2019-10-07 22:10:00+00"
  }
}

expected GET response (can use ?name=... qparam to filter by name):
{
  "response": [
    {
      "name": "bar",
      "lastUpdated": "2019-10-07 20:38:24+00"
    }
  ]
}

expected DELETE response:
{
  "alerts": [
    {
      "text": "server capability was deleted.",
      "level": "success"
    }
  ]
}

[x] This PR is not related to any Issue

Which Traffic Control components are affected by this PR?

Traffic Control Client (Go)
Traffic Monitor
Traffic Ops

Documentation will be done in a follow-up PR.
What is the best way to verify this PR?

Read the added TO API tests to verify they're sufficient, then run the TO API tests.
The following criteria are ALL met by this PR

[x] This PR includes tests OR I have explained why tests are unnecessary
[x] This PR includes documentation OR I have explained why documentation is unnecessary
[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/4418/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/4419/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/4420/

Was this new endpoint brought to the mailing list's attention? Not that I think anyone will have a problem with it, just seems like something important enough to bother with.

I think Rob is working on a blueprint.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/4422/

Since there are no docs, can you add to your PR description what that routes are and the expected request payloads for each?

Updated the description with routes and expected payloads.

Updated the description with routes and expected payloads.

GET /server_capabilities[?name=]
POST /server_capabilities
DELETE /server_capabilities?name=
right?

right, updated to include that

Opened placeholder draft PR for adding documentation: https://github.com/apache/trafficcontrol/pull/3971

without reading thru the code, does DELETE validate that the "server capability" is:
a. not being used by any server and
b. is not required by any ds
with some sort of alert error like "server capability failed. server capability used by X servers/delivery services"
sorry, i should just read the code :)

without reading thru the code, does DELETE validate that the "server capability" is:

a. not being used by any server and
b. is not required by any ds

Server-Capabilities and DS-Required-Capabilities don't exist in this PR, that'll have to be added in a subsequent PR.
But, I'd vote we don't add custom Go logic to handle that - rather, if we make them proper Foreign Keys that don't CASCADE DELETE, the DB will automatically prevent it. Then, all we have to do is parse the Postgres error to return a useful message to the user (we already have a func for that api.ParseDBError

without reading thru the code, does DELETE validate that the "server capability" is:

a. not being used by any server and
b. is not required by any ds

Server-Capabilities and DS-Required-Capabilities don't exist in this PR, that'll have to be added in a subsequent PR.
But, I'd vote we don't add custom Go logic to handle that - rather, if we make them proper Foreign Keys that don't CASCADE DELETE, the DB will automatically prevent it. Then, all we have to do is parse the Postgres error to return a useful message to the user (we already have a func for that api.ParseDBError

FWIW Did add that constraint to my PR per @rawlinp feedback https://github.com/apache/trafficcontrol/pull/3964/files#diff-7d3547a278b38f437ab01966666c94a8R26

i don't suppose you happened to add entries to seeds.sql for creating a "capability" (i'm talking about a user capability here) like the following:
server-capabilities-read
server-capabilities-write
seems a bit silly since we don't use "user capabilities" yet but i feel like it will make our lives easier if every time we add new api endpoints we keep the "user capabilities" current.

@mitchell852 I didn't add seeds.sql entries yet. @mhoppa probably needs those for his API endpoints as well. Should POST/DELETE only be admin? Right now I have it set to Operations.

Should POST/DELETE only be admin? Right now I have it set to Operations.

probably a question for @rob05c

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/4435/

Should POST/DELETE only be admin? Right now I have it set to Operations.

I think Ops is right. Admin vs Ops is somewhat nebulous, but I think in general, Operations can do pretty much everything except see password and security stuff. So I think Operations is right for these endpoints.

Are there any restrictions on server capability name? I.e. no spaces, alphanumeric only, etc...

Are there any restrictions on server capability name? I.e. no spaces, alphanumeric only, etc...
The design reqs don't, I was originally thinking we'd let people put anything, but now that I think more about it, I think we should limit it to URI path chars, I.e. digit/alpha/_/-. That lets us put it in a path or query easier later, and I can't imagine why someone would need any other chars.

Thoughts? If no one objects, I'll put that in the blueprint (but not hold up this PR for it, we can easily add that in another)

Just a thought. What about a GET response like:
{
  "response": [
    {
      "name": "bar",
      "lastUpdated": "2019-10-07 20:38:24+00",
      "servers: [],
      "deliveryServices: []
    }
  ]
}

We do something similar with GET /parameters where we have a []profiles property. It gives me the ability in the UI to show a "server count" and a "delivery service count" which seems like interesting info to the user.

+1 on restricting the name to alphanumeric/-/_.
Could the "server count" and "ds count" information be answered by just including links to pages which are backed by the server_server_capabilities API? E.g. click into the RAM capability, then click the "show servers" link to see all the servers with this capability or "show DSes" to see all the DSes with this capability.

Could the "server count" and "ds count" information be answered by just including links to pages which are backed by the server_server_capabilities API?

yep. i think that's fine.

 "alerts": [
     {
         "text": "no server capability with that id found",
         "level": "error"
     }
 ]

}``` message here needs to be corrected. we are deleting server_capabilities only by name.
2. when spaces are at the start and end of name, they are trimmed and accepted instead of throwing error.
3. api parameters are not validated. for instance, requesting service_capabilities endpoint with param id doesn't throw any error.

message here needs to be corrected. we are deleting server_capabilities only by name.

Yep, looks like an artifact of api.GenericDelete. Good catch!
Looks like either api.GenericDelete will have to be changed to something like "no x with that key found," or otherwise extended to know the names of the key(s).

when spaces are at the start and end of name, they are trimmed and accepted instead of throwing error.

That should be fine. It should be documented, but the extra safety seems like a good thing to me.

api parameters are not validated. for instance, requesting service_capabilities endpoint with param id doesn't throw any error.

The API shouldn't do this. Unknown parameters should be ignored. This follows the Robustness Principle. See
https://tools.ietf.org/html/rfc1122#section-1.2.2
https://en.wikipedia.org/wiki/Robustness_principle
This makes our API easier to use, and less likely to break users, and more forward-compatible. For example, someone could be using a client with a newer version, or newer code within the same version, but knowingly double-checking their filtering params (atstccfg does this); or posting some kind of debug information that helps themselves; or simply making a simple mistake that doesn't need to break things.
I know some other APIs do this. It is a gross violation of the Robustness Principle, and I strongly disapprove. It makes servers brittle and fragile, and complicates integration and forward-compatibility.

Trimming whitespace should be fine. It should be documented, but the extra safety seems like a good thing to me.

agree

Unknown parameters should be ignored.

agree

 "alerts": [
     {
         "text": "no server capability with that id found",
         "level": "error"
     }
 ]

}``` message here needs to be corrected. we are deleting server_capabilities only by name.

Yeah, I noticed that as well and just kind of figured "name" is really the "id" of the resource, so I just left it as it was. I'll change the GenericDelete function to use "key" instead of "id".

when spaces are at the start and end of name, they are trimmed and accepted instead of throwing error.

I'm not intentionally trimming the name, but about to submit a fix that validates the name is alphanumeric/dash/underscore.

api parameters are not validated. for instance, requesting service_capabilities endpoint with param id doesn't throw any error.

I also agree unknown API parameters should be ignored.

on PUT which is not defined - may be we should do method not allowed?

This seems like a problem with our entire API rather than just this PR. We should fix that holistically and separately IMO.

When a post with no body is made. the following error is provided.

    "alerts": [
        {
            "text": "EOF",
            "level": "error"
        }
    ]
}```
 instead of a meaningful message indicating the missing info.

I suspect that is also a larger problem with the majority of our API, since we share the common code for unmarshalling JSON and returning errors across multiple endpoints. We should fix that separately.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/4455/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/4458/

When a post with no body is made. the following error is provided.

    "alerts": [
        {
            "text": "EOF",
            "level": "error"
        }
    ]
}```
 instead of a meaningful message indicating the missing info.

what to create a separate issue for that @lbathina


[RELEASE-0.26] Build images with Golang 1.17

Title. Ref openshift-knative/serverless-operator#1302

/lgtm


PR to address Issue #46, #48, #53, #54

Purpose

As part of CSE's OneWeek - this PR includes code that addresses the following issues:

https://github.com/Azure-Samples/iot-edge-opc-plc/issues/46
https://github.com/Azure-Samples/iot-edge-opc-plc/issues/48
https://github.com/Azure-Samples/iot-edge-opc-plc/issues/53
https://github.com/Azure-Samples/iot-edge-opc-plc/issues/54

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

I really like what you did last week! 👏


[feature] Use less data-uri

less has a data-uri function which will take the file provided and make it into a base64 uri as part of the build step. This makes the source files easier to edit and makes resources easy to replace without changing the css result.
I have successfully tested this in another project of mine (https://github.com/tcyrus/homebrewery-standalone/blob/master/client/homebrew/phbStyle/phb.assets.less).

This is a good idea. Would you be interested in making a Pull Request for this?

I'll try to port over my work from the other repo and make a new PR for this.

Thanks! As you have seen, progress here isn't always as fast as we want (it's basically just me and occasional volunteers like you... the owner is missing...) so PRs are super welcome.

This has been done for a while now. Closing.


Check whether transform exists in ddBotImageQueue and return if it do…

…esnt to avoid segfault
Thanks to this we don't need to define pseudo CAMERA_LEFT frames etc. in robot.cfg files for robots that don't have a multisense

By the way, when we first introduced director_config.json it was only intended to support the different joint names and urdf files of Atlas v3 and Atlas v4.  Then we used it to add support for Valkyrie, then fixed base arms, etc.  But all of this was just used to specify urdf files and kinematic groups for planning.
But now it's clear that we can use it to configure a lot more than robot urdfs.  For example, rather than hardcode the Multisense source and camera names, all of these features could be enabled/disabled from the config.  You guys are already using this idea somewhat to enable/disable code in startup.py, but we could do a lot more.  I think it's on the todo list.  Let me know if you want to chat in person about specific plans.

Yes, we are trying to make director more modular and reduce the amount of hacks required to integrate new platforms in terms of bot param and director_config files. Really looking forward to the new startup initialisation :)
Sounds great, happy to have a chat on the roadmap sometime next week :)

For our mapping husky, we have a fork of the director with some minor changes.
To give an idea about what's missing for an outdoor navigation / self driving robot, the following changes we made. Ideally director could be configured for a wheeled or quadruped navigation mode without hard coded changes. All other minor modifications live in the extension 'module' (as @patmarion created).

disabled atlasdriver, irisdriver, handdriver, footstepdriver. And a few derivatives e.g. continuous walking code.
generalised the 'footstep goal' to be a 'driving goal' and disabled the footstep planner (which isn't very pretty). Otherwise this provides the same role. (TODO: support moving this on the terrain map.
there a several irrelevant button on the right side which we havent removed e.g. footstep planning
enabled moving grid and fixed some bugs in it
add new map server types - basically different buttons in the maps request panel
adding robot follow mode. (pushed upstream)
added a mesh directory to getBuiltinPackagePaths() ... which is necessary for all robots. I think this list should be stored in the json
added 2 hard-coded lidarDriver instances for two static lidars. This should instead be populated from a list. (bot-viewer does this from the list of lidars in the bot_config)
more properties become necessary e.g. intensity range for a SICK is way different than hokuyo.
required drc_lcmtypes to launch due to "import drc" in a variety of unused functions.

In time we will push these mods upstream.


Create pmtiles directly

This is an experiment to generate pmtiles directly in Rust, not using tippecanoe. It's specialized for the use case in od2net -- a bunch of tiny LineStrings representing segments of the road network. The "importance" of the roads is given by a count property in the GeoJSON data, so this should be used to figure out which features to drop at low zooms.
CC @stuartlynn
"Correctness" to use in the od2net viewer:

[ ] Include the actual feature properties (and maybe revisit squeezing osm_tags into a single JSON string, to improve encoding)
[ ] Plumb along the JSON metadata field
[ ] Decide what to do about the other layers (points representing origins and destinations)
[ ] Use compression internally (which does tippecanoe use?)
[ ] Enforce per-tile limits on number of features or total size, by sorting by the count property

Performance of the tool itself:

[ ] Figure out what spatial indexing we can use to filter for each tile. rstar with Web Mercator coordinates? Something specialized for WGS84? Can we directly use tile boundaries as the spatial indexing bins?
[ ] Does processing each tile in parallel help?

Logistic:

[ ] File bug about empty geometry encoding in mvt
[ ] Name this properly and make a separate repo
[ ] Get feedback from georust and others

Hey I am going to try and take a swing at doing bbox filtering using rstar. I have used it on some projects before with good results.

Yes please! Maybe I don't understand coordinate systems well enough, but can this be done with WGS84, or do we have to project to Web Mercator or something else first?
(I won't pick this up until Monday again, no fear of merge conflicts)

I think given that we need to convert to WebMercator anyway to generate the tiles, it makes sense to

Load the features
Transform to WebMercator
Build the RTree
Iterate through the tiles and use the RTree to select the features for each
Generate the tile
Add it to PMTiles.

One thing that might be interesting to experiment with is generating the tiles in parallel (with rayon) and storing them somewhere intermediary before constructing the full pm tiles at the end? That's an enhancement though

@stuartlynn , there's some chatter in the georust discord about possible distance metrics that could be useful: https://discord.com/channels/598002550221963289/963346313708195880/1167857249977372733

@stuartlynn , there's some chatter in the georust discord about possible distance metrics that could be useful: https://discord.com/channels/598002550221963289/963346313708195880/1167857249977372733

Not sure that link is working for me. What were you thinking if using the different distance metrics for?

Moved to https://github.com/Urban-Analytics-Technology-Platform/lines2pmtiles


Add troubleshooting info re. iOS build

r @keybase/react-hackers?
Verified that:

installing watchman was all I needed to fix this error, and
without watchman, none of the other tricks (raising various system limits) worked.


Don't use eTRNG data verbatim; mix it with previous eTRNG responses and UDS

Data sent to the eTRNG interface may be coming from an SoC microcontroller that has been compromised later in boot. The compromised firmware could feed Caliptra the same bits over and over, convincing the firmware to reuse a nonce, or worse.

Integration requirements require eTRNG to be supplied by a HW gasket with no firmware involvement. It is tougher to audit this though.

From section 8 of Caliptra_Integration_Specification.pdf:

It is a requirement that this TRNG HW API is always handled by a SOC HW gasket logic (and not some SOC ROM/FW code) for FIPS compliance.

I'm worried that folks that don't care about FIPS will do the easy thing and just implement this in the management CPU.


[incubator/elasticsearch] Add pod disruption budgets.

So that clusters don't become unavailable during node restarts.
cc @icereval

Marking this as stale. Please update within one week.

@unguiculus this is ready for review.

/ok-to-test

@jmcarp Readme update still missing.

Marking stale. Please update readme.

Closing as stale. Feel free to reopen if/when you decide to pick this up again.


[WIP] configuration option to Broker to control launch_apb_on_bind

 Update Broker to incorporate workaround for lack of async bind.


Cannot create HTML5 or Normalized DITA using test files on Windows

Preprocess files on Windows are not recognized as passthrough
With the changes made in bd3a551 I can create a PDF from fox.jason.passthrough.pandoc\test\single-topic\document.ditamap. I have tested various files from the test directory. I have also tested a simple rST file I have. With all of them I can produce a PDF.
But with none of them can I produce HTML or Normalized DITA.
The suspicion is that preprocess may be implicated because preprocess2 is used for PDF.

Quick fix - amend the Normalize DITA plugin to use preprocess2 for now by changing the depends in org.dita.normalize/build.xml line 10.

This suggestion did not work for me.

I'll need the temp job.xml and the intermediate ditamap to look at.

Here you go. Attached is a the temp directory from \single-topic\document.ditamap that may be helpful in debugging the issue.
Also, I notice this directory is sometimes created: test\single-topic\${_dita.map.output.dir}. Yes, that's the actual name of the directory.
Environment:

Windows 10
DITA-OT 3.3.3 (standalone)
Oxygen 21.1 (using DITA-OT 3.3.3)

The issue is once again Windows file path processing vs XML paths.
Linux/Mac
Read job.xml
[read-job.xml] Applying com.oopsconsultancy.xmltask.AnonymousCallAction@77fec3b6 to
//file[@result='file:/Users/jasonfox/Workspace/dita/dita-ot-3.3.3/plugins/
fox.jason.passthrough.pandoc/test/html-local-file/topic.dita']

.job.xml
<file src="file:/Users/jasonfox/Workspace/dita/dita-ot-3.3.3/plugins/
fox.jason.passthrough.pandoc/test/single-topic/markdown.md"
 uri="markdown.md" path="markdown.md"
result="file:/Users/jasonfox/Workspace/dita/dita-ot-3.3.3/plugins/
fox.jason.passthrough.pandoc/test/single-topic/markdown.md'" format="dita" target="true">

Windows
Read job.xml
[read-job.xml] Applying com.oopsconsultancy.xmltask.AnonymousCallAction@77fec3b6 to
//file[@result='file:G:\git\dita-ot-3.3.3\plugins\
fox.jason.passthrough.pandoc\test\single-topic\markdown.md']

or even:
[read-job.xml] Applying com.oopsconsultancy.xmltask.AnonymousCallAction@77fec3b6 to
//file[@result='file:C:\Program%20Files\Oxygen%20XML%20Editor%2021\frameworks\dita\DITA-OT3.x\plugins\
fox.jason.passthrough.pandoc\test\single-topic\markdown.md']

<file src="file:/G:/git/dita-ot-3.3.3/plugins
/fox.jason.passthrough.pandoc/test/single-topic/markdown.md"
 uri="markdown.md" path="markdown.md"
result="file:/G:/git/dita-ot-3.3.3/plugins/
fox.jason.passthrough.pandoc/test/single-topic/markdown.md"
format="dita" target="true">

Antlib line 100
<property name="result" value="file:${ditamap.dir}${file.separator}@{href}"/>

Will have to be replaced by a <scriptdef> function

Potential fix: d52829e
Additional debug: ba6a881 - this should give more info in the log if -v is used.

@lief-erickson : As I'm fixing this blind, could you re-install the necessary plugins and try running again and provide more feedback as necessary. Thanks.
dita --uninstall fox.jason.passthrough
dita --install https://github.com/jason-fox/fox.jason.passthrough/archive/master.zip

The potential fix was able to produce valid output using the sample test files from the plugin, but not without some lingering side effects.  When trying a more complex rST file I was running into some issues, but I'm not certain that they are the fault of the the passthrough plugin or belong to the preprocessing stage.
I'll gather everything and update this ticket when I have it.

@lief-erickson any further progress to report?

Yes. I'll post it later tonight (my time).

I'm going to record a couple of issues that I'm seeing here, but upon reflection not all of them may be with the passthrough or pandoc plugin and instead may be located elsewhere in the processor (although where exactly I'm not certain).
Issues:

Using the dita output format does not produce files with .dita or .xml extension. Instead it is the source files extension even though the contents of the converted file are in fact DITA. I'm forced to rename the extension.
Lists inside the csv_table (in the second column) are not rendered as an unordered list.
Notes are not rendered as <note>.

This .zip file contains a sample rST file following similar structure as your other test files. Also included are the log file and temp directory as well as the output directory. In the output directory rename the ..rst file to .dita to see the transformed DITA.
This isn't a comprehensive test of what's possible in rST, but it's a start. Also, I'm a neophyte with rST, so there may be rST syntax errors that cause downstream issues. You may use and extend this sample as you wish.
rst-sample1.zip

None of the remaining issues touch the passthrough plug-in processing, they are all pandoc or dita transform related. I'll close this Windows processing issue, and raise three separate new issues in the pandoc plug-in.


Add YAML parsing capabilities

The OCP walking parameters can be read from a YAML file.
See https://github.com/olivier-stasse/sobec/blob/topic/yaml/tests/config_walk.yaml
No emitting capabilities yet (would it be useful ?)

Perfect, thanks !


runtime-lite has not been added as maven module

runtime-lite has not been added as a maven module and so it won't build with the rest of the project.
It needs an entry in the <modules> section of runtime/pom.xml, but when added it gives some compile errors
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.11.0:testCompile (default-testCompile) on project runtime-lite: Compilation failure: Compilation failure:
[ERROR] appengine-java-standard/runtime/lite/src/test/java/com/google/appengine/runtime/lite/RequestManagerTest.java:[295,63] cannot find symbol
[ERROR]   symbol:   method getGeneratedRegistry()
[ERROR]   location: class com.google.protobuf.ExtensionRegistry
[ERROR] appengine-java-standard/runtime/lite/src/test/java/com/google/appengine/runtime/lite/RequestManagerTest.java:[334,63] cannot find symbol
[ERROR]   symbol:   method getGeneratedRegistry()
[ERROR]   location: class com.google.protobuf.ExtensionRegistry
[ERROR] -> [Help 1]

Be careful with this new module as the way it can be used publicly is tricky (completely different boot process, no app class loader, no jsp support, no static files, etc, and expectation of a big fatjar at the end with the app to execute the app). Before pushing to maven central, we need to think


Realm crash sometimes when app just started

@xilin commented on Fri Sep 01 2017
Goals
Save launch record using Realm when app just started.
Expected results
Successfully insert one record.
Actual results
Sometimes it works successfully, but in production I can see quiet a lot crash reports.
Crashed: com.apple.main-thread
0  libsystem_kernel.dylib         0x181a05014 __pthread_kill + 8
1  libsystem_pthread.dylib        0x181acf264 pthread_kill + 112
2  libsystem_c.dylib              0x1819799c4 abort + 140
3  MaiTian                        0x100b03e34 std::__1::basic_ostream<char, std::__1::char_traits<char> >& std::__1::operator<<<std::__1::char_traits<char> >(std::__1::basic_ostream<char, std::__1::char_traits<char> >&, char) + 2363456
4  MaiTian                        0x100b04168 realm::util::terminate_internal(std::__1::basic_stringstream<char, std::__1::char_traits<char>, std::__1::allocator<char> >&) + 2364276
5  libsystem_pthread.dylib        0x181acf264 pthread_kill + 112
6  MaiTian                        0x100b04384 realm::util::terminate(char const*, char const*, long, std::initializer_list<realm::util::Printable>&&) + 2364816
7  libsystem_pthread.dylib        0x181acf264 pthread_kill + 112
8  MaiTian                        0x1007e867c realm::_impl::RealmCoordinator::RealmCoordinator() (realm_coordinator.cpp:296)
9  MaiTian                        0x10089a224 realm::Realm::cache_new_schema() (shared_realm.cpp:490)
10 MaiTian                        0x10089a68c realm::Realm::begin_transaction() (shared_realm.cpp:560)
11 MaiTian                        0x100876a90 -[RLMRealm beginWriteTransaction] (RLMRealm.mm:535)
12 MaiTian                        0x100876d88 -[RLMRealm transactionWithBlock:error:] (RLMRealm.mm:576)
13 MaiTian                        0x100876d4c -[RLMRealm transactionWithBlock:] (RLMRealm.mm:572)
14 MaiTian                        0x10020e930 -[MTPersistentManager insertNewPageLog:] (MTPersistentManager.m:435)
15 MaiTian                        0x100384a24 -[MTAnalyticsManager enterPageWithPageTypeName:url:params:startupType:] (MTAnalyticsManager.m:81)
16 MaiTian                        0x100384a90 -[MTAnalyticsManager recordLaunch] (MTAnalyticsManager.m:88)
17 MaiTian                        0x100510a1c -[AppDelegate application:didFinishLaunchingWithOptions:] (AppDelegate.m:118)
18 UIKit                          0x188ba6e48 -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 380
19 UIKit                          0x188db337c -[UIApplication _callInitializationDelegatesForMainScene:transitionContext:] + 3452
20 UIKit                          0x188db8e24 -[UIApplication _runWithMainScene:transitionContext:completion:] + 1684
21 UIKit                          0x188dcd8b0 __84-[UIApplication _handleApplicationActivationWithScene:transitionContext:completion:]_block_invoke.3147 + 48
22 UIKit                          0x188db60b8 -[UIApplication workspaceDidEndTransaction:] + 168
23 FrontBoardServices             0x1845b4884 __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 36
24 FrontBoardServices             0x1845b46f0 -[FBSSerialQueue _performNext] + 176
25 FrontBoardServices             0x1845b4aa0 -[FBSSerialQueue _performNextFromRunLoopSource] + 56
26 CoreFoundation                 0x1829b942c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 24
27 CoreFoundation                 0x1829b8d9c __CFRunLoopDoSources0 + 540
28 CoreFoundation                 0x1829b69a8 __CFRunLoopRun + 744
29 CoreFoundation                 0x1828e6da4 CFRunLoopRunSpecific + 424
30 UIKit                          0x188b9ffc8 -[UIApplication _run] + 652
31 UIKit                          0x188b9ac9c UIApplicationMain + 208
32 MaiTian                        0x1003512e8 main (main.m:11)
33 libdyld.dylib                  0x1818f559c start + 4

Steps to reproduce
I don't know how to reproduce it.
Version of Realm
2.8.3

The backtrace suggests that realm_coordinator.cpp:296 is where the assertion is occurring, but there's no assertion on that line in the version of object store used by Realm Cocoa v2.8.3. Based on the backtrace, this may be the assertion being hit: https://github.com/realm/realm-object-store/blob/39d33531363d8ac9faf0333c9abd9b7c86588d13/src/impl/realm_coordinator.cpp#L289

I can reproduce this with a java test now:
    @Test
    public void lockTest() throws InterruptedException {
        //RealmLog.setLevel(LogLevel.ALL);
        CountDownLatch latch = new CountDownLatch(1);
        for (int i = 0; i < 200; i++) {
            Thread thread = new Thread(new Runnable() {
                @Override
                public void run() {
                    try {
                        while (true) {
                        /*
                        try {
                            Realm.deleteRealm(realmConfig);
                        } catch (IllegalStateException ignored) {
                            //RealmLog.error("Cannot ");
                        }
                        */
                            Realm realm = Realm.getInstance(realmConfig);
                            realm.beginTransaction();
                            realm.commitTransaction();
                            realm.close();
                            Realm.compactRealm(realmConfig);
                            try {
                                boolean result = Realm.deleteRealm(realmConfig);
                                //RealmLog.error("deleted " + result);
                            } catch (IllegalStateException ignored) {
                                //RealmLog.error("Cannot ");
                            }
                        }
                        /*
                    } catch (RealmFileException e) {
                        RealmLog.error(e);
                    } catch (RealmError e) {
                        RealmLog.error(e);
                    */
                    } catch (UnsupportedOperationException e) {

                    }
                }
            });
            thread.start();
        }
        latch.await();
    }

Please note there is a java bug related with compactRealm() and deleteRealm() which will crash first.

@beender, do you think it would be possible to translate the Java test case that reproduces this into an object store test case so someone not familiar with the Java binding could more easily look into this?

I will try

Any updates on this issue?

Realm version: github "realm/realm-cocoa"
Realm framework version: ? "v3.21.0"
Xcode version: ? 11.2
iOS/OSX version: ? 12.3.1  iPhone X
Dependency manager + version: Carthage 0.34.0
Looks like this one is still an issue. I got a crash report with a similar stack track. On the app start, there was a migration to a new schema version then an app worked for some time ~5s and then an app crashed when one thread tried to write while another thread tried to read. The good news is that after a user restarted an app it worked fine.
The main thread that tried to write:
#0. Crashed: com.apple.main-thread
0  libsystem_kernel.dylib         0x1caf560dc __pthread_kill + 8
1  libsystem_pthread.dylib        0x1cafd39b0 pthread_kill$VARIANT$armv81 + 296
2  libsystem_c.dylib              0x1caeafea8 abort + 140
3  Realm                          0x1032b3df4 realm::util::terminate(char const*, char const*, long) + 10
4  Realm                          0x1032b40c0 realm::util::terminate_internal(std::__1::basic_stringstream<char, std::__1::char_traits<char>, std::__1::allocator<char> >&) + 716
5  Realm                          0x1032b4238 realm::util::terminate(char const*, char const*, long, std::initializer_list<realm::util::Printable>&&) + 328
6  Realm                          0x102fef4b8 realm::_impl::RealmCoordinator::RealmCoordinator() + 399 (realm_coordinator.cpp:399)
7  Realm                          0x1030c12c0 realm::Realm::cache_new_schema() + 587 (shared_realm.cpp:587)
8  Realm                          0x1030c1590 realm::Realm::commit_transaction() + 2637 (memory:2637)
9  Realm                          0x10308e704 -[RLMRealm commitWriteTransactionWithoutNotifying:error:] + 663 (RLMRealm.mm:663)
10 RealmSwift                     0x10353d284 Realm.write(withoutNotifying:_:) + 276 (Realm.swift:276)

Another thread that tried to read:
#6. LocationUpdateEventRealmModel
0  libsystem_kernel.dylib         0x1caf55f2c __psynch_mutexwait + 8
1  libsystem_pthread.dylib        0x1cafd6180 _pthread_mutex_firstfit_lock_wait + 92
2  libsystem_pthread.dylib        0x1cafd60f0 _pthread_mutex_firstfit_lock_slow$VARIANT$armv81 + 260
3  libc++.1.dylib                 0x1ca561610 std::__1::mutex::lock() + 12
4  Realm                          0x102fef308 realm::_impl::RealmCoordinator::cache_schema(realm::Schema const&, unsigned long long, unsigned long long) + 365 (realm_coordinator.cpp:365)
5  Realm                          0x1030bfdcc realm::Realm::read_schema_from_group_if_needed() + 320 (shared_realm.cpp:320)
6  Realm                          0x1030bed7c realm::Realm::read_group() + 254 (shared_realm.cpp:254)
7  Realm                          0x103010f7c RLMClassInfo::table() const + 43 (RLMClassInfo.mm:43)
8  Realm                          0x10302a610 RLMGetObjects + 236 (RLMObjectStore.mm:236)
9  RealmSwift                     0x10353e4b0 Realm.objects<A>(_:) + 704 (Realm.swift:704)

Might be also related to this one https://github.com/realm/realm-cocoa/issues/6230

Probably fixed by https://github.com/realm/realm-cocoa/releases/tag/v4.4.1


TP: Track offer/response involvement on each moji

Each moji needs an offers array with the address of each offer they are listed in, either as one of the offer moji, or in one of the responses.
This should then be used to add some extra verification:

You cannot select sires in an offer/response you initiated
If your new sire is in a response someone else initiated, that response should be nulled
When moji are traded any offers or responses they are a part of should get removed or nulled.

Should be addressed by version 2 redesign #121


IPAM to DNS replication

Hello,
We have a problem when we use the provider to create an ip with the resource "solidserver_ip_address". We have a block like this one:
resource "solidserver_ip_address" "ip" {
  space  = "MAIN"
  subnet = "SIEGE"
  pool   = "TEAM1"
  name   = "myhost.domaine.local"
}

The creation is ok:
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # solidserver_ip_address.ip will be created
  + resource "solidserver_ip_address" "ip" {
      + address = (known after apply)
      + id      = (known after apply)
      + name    = "myhost.domaine.local"
      + pool    = "TEAM1"
      + space   = "MAIN"
      + subnet  = "SIEGE"
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

solidserver_ip_address.ip: Creating...
solidserver_ip_address.ip: Creation complete after 0s [id=148898]

Since we set a FQDN in the name argument, the DNS entry is correctly created:
$ host myhost.domaine.local
myhost.domaine.local has address <IP_ADDRESS>

But if we go to the WebUI:

And we try to add an alias by clicking on the "Edit" button in the "ALIASES" box:

We have a warning on the "IP address name" field, which is missing the name we defined with terraform, and the "IPAM to DNS replication" section is empty, so we have to re-enter the hostname.
Is it possible to provide missing information via the API so we can add it to the provider?

And I have the same problem when trying to create the IP via the solidserver-go-client library: https://github.com/EfficientIP-Labs/solidserver-go-client/blob/main/sdsclient/docs/IpamApi.md#ipamaddressadd

Hello,
Your issue is not with the terraform provider nor the go-client.
Your IPAM is configured to use the automatic construction of the IP name, from the class parameters 'hostname' and 'domain' (Refers to the SOLIDserver_Administrator_Guide for details - Look for 'IP Address Advanced Properties').
As a result, in addition to the name of the IP address, you need to provide the class parameters 'hostname' and 'domain' while creating IP resources.
Kind regards.

Oh ok, sorry for the wrong analysis. And thanks for your solution resolving our issue :)


BUG-Image comparison

Image comparison cannot open right-click menu。

I can't seem to reproduce this. The menu opens fine for me.
Can you open your Browser DevTools Console (usually F12) and check if there are any new errors that appear when you right-click in the comparison node?

ComfyUI_NestedNodeBuilder    I checked if there is a conflict with this, just delete it


MCS-1743 console output to log file

MCS
This side of the branch makes a log file with all of the output from the unity console. I also added a more in depth output of what happened each action. The output and updating of the log file only happens if outputLogFile is set to true in MCSMain

@jaudick It feels like this PR has two separate purposes:

Log all of the console messages to file, for reference while debugging
Log all of the actions taken in the Unity Editor, to replicate them exactly when running via Python

I'd recommend that we save this information in two separate log files. Your current log file serves the purpose for number 1. For purpose number two, we can have another log file where each action and its parameters are saved in an individual line, like this:
MoveAhead
MoveAhead
LookDown
PickupObject,objectImageCoordsX=300,objectImageCoordsY=200

Then we could use the existing run_action_file script on it. Maybe doing this would also solve the issues you said you're having getting some of the actions to work properly. This also means you wouldn't need a separate python script just for this purpose, which can also be easily broken if someone changes the format of the log messages in the future.

@ThomasSchellenbergNextCentury That change to two log files here works for me

@ThomasSchellenbergNextCentury Just pushed a change and closed the python branch


java.sql.Date cannot be parsed

Dear Devs,
When I calling fixture.create() to a class which has java.sql.Date as a field, the following exception comes:
com.flextrade.jfixture.exceptions.ObjectCreationException: Error setting property setHours at com.flextrade.jfixture.behaviours.autoproperty.AutoPropertyPopulater.trySetProperty(AutoPropertyPopulater.java:71)
Thank you very much for your help!

Hi @MrMojoR thanks for the issue.
This isn't working for you because JFixture doesn't explicitly handle java.sql.Date objects so it uses the default resolution algorithm (try a constructor, and then call the setters), which errors because the setHours will sometimes be called with numbers > 24 (as it just picks a random int).
A simple workaround is to override this algorithm and generate a java.util.Date (which JFixture has explicit logic to handle) and create the java.sql.Date from that.
fixture.customise().lazyInstance(java.sql.Date.class, new SpecimenSupplier<java.sql.Date>() {
    @Override
    public java.sql.Date create() {
        return new java.sql.Date(fixture.create(java.util.Date.class).getTime());
    }
});

Obviously this can be much simpler with Java 8 lambdas if they're available to you.


Feature request: Autocomplete

I just wish this would work with juicy-ace-editor

You mean code completition? Is there some simple switch in Ace that we can use which learns from the vocabulary in the current document? I am afraid we will not be able to do anything else, since juicy-ace-editor is just a thin wrapper for Ace.

I've described my use case here https://github.com/DenisKolodin/elm-ace/issues/5#issuecomment-302318469

Thanks. Just a sincere question, what are the benefits of using juicy-ace-editor in Elm rather than directly using Ace in Elm?
The main purpose of custom elements is to encapsulate complex functionality with a simple DOM API, so I guess that's the reason, but maybe there's something more. Are custom elements a big thing in the Elm world?

To have autocomplete working. Currently this should work https://github.com/lostinbrittany/ace-widget
Look at https://github.com/LostInBrittany/ace-widget/issues/16

To have autocomplete working. Currently this should work lostinbrittany/ace-widget

This does not answer my question, but now I have another one... Why don't you use https://github.com/lostinbrittany/ace-widget?
Again, I am asking sincerely, because juicy-ace-editor was created 3 years ago when there was no other custom element wrapper around Ace editor. It is still actively maintain, but maybe we should give space to ace-widget because it also seems nice and has more features.

What are the benefits of using juicy-ace-editor in Elm rather than directly using Ace in Elm

This package DenisKolodin/elm-ace uses ace directly, but to add autocomplete you have to know how the Native works https://github.com/DenisKolodin/elm-ace/blob/master/src/Native/Ace.js
Or maybe you have some other way in your mind to use ace directly.

Why don't you use https://github.com/lostinbrittany/ace-widget?

At that time I didn't know how to enable autocomplete in any of these packages.


Explore using rust-skeptic

Related to #987.
Skeptic is a project to build and test code examples in markdown files.
We should explore using it to ensure that the example in README.md is always up-to-date.

Could we punt on this issue to get the new release cut?

I took a quick stab this. Add a $RUSUTO_ROOT/build.rs is a little tricky because the root Cargo.toml is a workspace does haven't the required [package] (with name, version, etc). I guess a workspace-only file is a meta package?
One solution might be to have the core Cargot.toml go up and level and pull this in?

Hmm, yeah, that's a bit tricky. We can't really test this example in the context of the rusoto_core crate, since we'd need to make rusoto_dynamodb a dev-dependency, which creates a dependency cycle :/
In theory we could have something like a rusoto_workspace package at the top level and test the README in the context of that, but I'm not sure if it's worth doing...

I've just implemented skeptic for rusoto.org in https://github.com/rusoto/rusoto.github.io/pull/90 . We could do something similar as the approach done there: make a new project in this repo that relies on relative directories for source code and the README example. Probably have it run on a CI server other than Travis, which we're leaning on really hard.


A "Design FAQ" document

 Issue by bstrie
Tuesday Nov 27, 2012 at 20:34 GMT
For earlier discussion, see https://github.com/rust-lang/rust/issues/4047
This issue was labelled with: A-docs, I-wishlist in the Rust repository

In the vein of the Project FAQ and the Language FAQ.
In addition to being really interesting, this would save a lot of time and divert a lot of potential questions in the long run. Some topics to discuss:

Why was typestate removed?
Why are some types nominal instead of structural?
Why do I have to declare impls in the same crate as a type or trait?
Why is trait inheritance the only means of inheritance?
Why doesn't Rust do tail-call optimization?
(see e.g. rust-dev post.)

Explanations should be technical and include code examples wherever possible.
Some of the questions of this nature overlap with the latter half of the Language FAQ, but not all, e.g. "Can Rust code call C code?" and "What is the difference between a managed pointer and an owned pointer?" do not belong. The document should focus on large-scale design decisions and tradeoffs; think "Why split stacks?" rather than "How do split stacks work?".
If you think of good questions, add them in the comments here. There are probably a lot of ripe areas for explanation, especially with regard to mutability and regions.

I liked having a complete list of the questions on one web page (as I noted in my comment on the original issue)
I suggest we either:

close this ticket and reopen https://github.com/rust-lang/rust/issues/4047 , or
open a shared document somewhere and transcribe all of the comments from https://github.com/rust-lang/rust/issues/4047 into that shared document.

In the meantime I am planning to continue writing my comments in https://github.com/rust-lang/rust/issues/4047 (even though it is closed) , since for the short term, that is the easiest way to keep all of the proposed questions in one place.  (I suggest others do the same until we decide on some other way to resolve this problem.)

quick decision: I will try to import the comments from rust-lang/rust#4047 in the near term.

I could move this over without the --ignore-comments flag and it would
just move all the comments over?

That didn't work due to rate limiting.

I believe https://www.rust-lang.org/en-US/faq.html satisfies this "Design FAQ" document idea. So I'm closing this as being completed.


Various addresses and constants for Chronos and Metis chains

Also add the gOHM token address for Optimism.

Coverage increased (+0.002%) to 97.996% when pulling c0583822463011b92f5d6a6af8ab5bd0dcf69a20 on chains/chronos-metis into abdd54942830687324ba07aa56689d9e25ea7534 on dev.


Evaluators ambiguity: class/module

There is ambiguity between classes and modules under the evalutors module. Specifically, evaluators objects under mteb/evaluation/evaluators are named the same as the modules which contain them. For example:
mteb.evaluation.evaluators.RerankingEvaluator references the class RerankingEvaluator in mteb/evaluation/evaluators/RerankingEvaluator.py.
This is problematic because it does not allow to reference the mteb/evaluation/evaluators/RerankingEvaluator.py module and therefore referencing any other definition within it.

I agree that this is a general problem within mteb. Ideally, we should have the modules in lowercase to avoid confusing the module with the object. I believe this is also the pep8 recommendation.
We also have quite a high usage of * imports, which also leads to a few oddities e.g.:
from mteb import load_dataset

I would love a fix for this. Will just check in with @Muennighoff and @isaac-chung as well to make sure that everyone agrees

Thanks for bringing this up! I think it's great if we can follow something like pep8. This would lead to a breaking change that might not be backwards compatible, so this would trigger a major version bump. We should consider this for perhaps for 2.0.

This is problematic because it does not allow to reference the mteb/evaluation/evaluators/RerankingEvaluator.py module and therefore referencing any other definition within it.

But there is no other definition within RerankingEvaluator.py besides RerankingEvaluator, no?
Note that we also name all task & abstask files in this style e.g. https://github.com/embeddings-benchmark/mteb/blob/main/mteb/tasks/Classification/ara/TweetEmotionClassification.py - I think if we change it for evaluators we should also change it there but still unsure if the change is needed. 🤔

Thanks @KennethEnevoldsen and @isaac-chung, +1 that following pep8 standards is a good path forwards.
I think that @Muennighoff brings a valid point and this is my bad as RerankingEvaluator might not be the best example. A more relevant example would be the RetrievalEvaluator.py module if we want to reference classes such as DenseRetrievalExactSearch within that module.


Add zig 0.3.0 compiler

Corresponding image commit is here: https://github.com/mattgodbolt/compiler-explorer-image/pull/115.

Must have left that in when testing the install scripts. Added.

@tiehuis 0.2.0 gives
https://godbolt.org/z/196Da9
Unable to find zig lib directory. Reinstall Zig or use --zig-install-prefix.
Compiler returned: 1

So Zig 0.2.0 doesn't do lookup the zig lib directory at runtime but uses a hardcoded value or the compiler flag as specified. This was the initial reason I didn't add it. I realise though that the dummy panic handler uses old syntax and is incompatible as well.
I think I'll make a PR and remove 0.2.0 completely as I initially planned to.

I think I'll make a PR and remove 0.2.0 completely as I initially planned to.

Just a heads up! Under most (if not all) circumstances, we will not merge something that removes a compiler that has already been in production (As part of the "URLs should live forever" goal) @tiehuis
Is there a way to support both? The panic handler being incompatible is easily fixable by either checking against the version to decided what to inject.


Setup docs.phcode.dev site

Wire in docs.phcode.dev to githuib pages

https://docs.phcode.dev/ is now live.
Push code to docs folder to preview.


[Hacken 2022-11-25 High #1] Denial of Service Vulnerability

The internal function _remainingAllowance() will revert with overflow in situations where the approveRenewable() or permitRenewable() functions will be used to approve a max uint256 value with a recoveryRate > 0.
The overflow can occur with different edge cases:
approveRenewable(, type(uint256).max - type(uint192).max + 1, type(uint192).max)

approveRenewable(, type(uint256).max - type(uint64).max + 1, type(uint64).max)

The _remainingAllowance() function is used by allowance() and transferFrom(). These functions will be unusable after such approval.
Path
./src/Funnel.sol: allowance(), _remainingAllowance(), transferFrom()
Recommendation
Rewrite the logic to prevent overflows.
Status
New

Can't seem to replicate an overflow.


Should update the documentation.

Update the documentation with more explanation, use cases and different type examples.

@AyushTiwary hi - thanks for raising the issue. It is important we give useful and comprehensive examples; can you give pointers where documentation is currently lacking?

Tracked in #492


Split cache step into two, always save cache, fix hash files

Please let me know if I should re-run on latest of this PR. Also please see the comments in this PR, they might be hiding between the test results.

@TWiStErRob go for it, please test this branch!

Queued https://github.com/TWiStErRob/net.twisterrob.libraries/actions/runs/4416412575/jobs/7769498594

😍

I reran it just to try and it took more than a minute second time:
https://github.com/TWiStErRob/net.twisterrob.libraries/actions/runs/4416412575/attempts/4
Both times it restored caches.
I cleared caches and running it again:
https://github.com/TWiStErRob/net.twisterrob.libraries/actions/runs/4416412575
and will run again when it finishes to see the cache-reuse.

Can you rerun the 🧪 Instrumentation Tests on 21 job, please? There is still an issue with the cache key.

Cancelled and running again with latest: https://github.com/TWiStErRob/net.twisterrob.libraries/actions/runs/4416412575/attempts/6
invited you, feel free to edit the branch and run the CI directly on https://github.com/TWiStErRob/net.twisterrob.libraries/pull/38

invited you

Thanks!

Run with cache miss:
https://github.com/TWiStErRob/net.twisterrob.libraries/actions/runs/4429767427/jobs/7790625895#step:6:92
Run with cache hit:
https://github.com/TWiStErRob/net.twisterrob.libraries/actions/runs/4429767427/jobs/7791493539#step:6:96

Amazing! Congrats, it looked like a very hard labor. It's funny how 15MB can cut 3.5min to 15 seconds


统一行分隔符

保持Windows与Linux分格统一。

I signed it!
我在中国大陆，注册Google账号时，大陆手机号码无法进行验证。
这意味着我无法注册，请问还有其他方式可以签署这份协议吗？

I signed it!

It looks like that worked.  Unfortunately, we don't really have a process for merging PRs for this repository.  You might be better off making your own fork with this change locally.  For what it's worth, this file hasn't changed since 2011 and is unlikely to ever change in the future, so you won't need to worry about keeping it up to date.


Data exchange status of contributing groups

Google spreadsheet for tracking status:
https://docs.google.com/spreadsheets/d/1Ph7w-dLAFNJJY3-8i5kgDRstBedg9a8zVmHbVyWgK_I/edit?gid=1076042544#gid=1076042544
Folder with individual files
https://drive.google.com/drive/folders/13UHsK6Q3VLAqzJ8AgxfIc8tjurMJb7Gv

MGI - discussed with @LiNiMGI the GOA syntax error file
The most important problem is 3800 unmapped identifiers, for eg: MGI:5792253
It's in AmiGO: https://amigo.geneontology.org/amigo/gene_product/MGI:MGI:5792253 but he link to MGI doesn't work
Li sees it in the MGI internal server, but not on the public server.
@LiNiMGI will investigate these genes.


Problem while running my first web app

Problem encountered on https://dotnet.microsoft.com/learn/web/aspnet-hello-world-tutorial/run
Operating System: Linux Debian 9 - x64
Provide details about the problem you are experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

What error did you encounter?

No follow up, closing.


Feature Request: Correct Radiance HP

Modify all HP related values of Absolute Radiance to make her die at 0 HP

Implemented in 9976a22


Improve OP labels

Fixes #387 and changes the label tooltip if it is the logged in user to match GitHub's own tooltip messages.

Released as 1.5.2

🎉


ModuleNotFoundError: No module named 'sparkocr'

I tried all the things, but sparkocr I was not able to use in my colab notebook.

Hello @RAravindDS , have you restarted the environment after installing the libraries in Colab?


Copy layout components & file uploads when applying message create data

Pull Request Etiquette

[X] I have checked the PRs for upcoming features/bug fixes.
[X] I have read the contributing guidelines.

Changes

[X] Internal code
[X] Library interface (affecting end-user code)
[X] Documentation
[ ] Other: _____

Closes Issue: #2234
Description
This PR fixes layout components and file uploads being copied by reference, which allowed modifications to carry over duplicated messages

Getting some kind of fix out that addresses the components part of this problem seems like a small win that we should push forward with. @MinnDevelopment do you have any other suggestions on how to proceed on this? Seems like we could just drop files and mention that they're dropped in the copy process?

I'm fine moving forward with it as long as we limit it to components.


There was an error loading a Vagrantfile

TASK [geerlingguy.drupal : Run composer install.] ******************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: OSError: [Errno 2] No such file or directory: '/vagrant/vendor/geerlingguy/drupal-vm/provisioning'
fatal: [drupalvm]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Traceback (most recent call last):\n  File \"/tmp/ansible_x296Jk/ansible_module_composer.py\", line 264, in <module>\n    main()\n  File \"/tmp/ansible_x296Jk/ansible_module_composer.py\", line 252, in main\n    rc, out, err = composer_command(module, command, arguments, options, global_command)\n  File \"/tmp/ansible_x296Jk/ansible_module_composer.py\", line 185, in composer_command\n    return module.run_command(cmd)\n  File \"/tmp/ansible_x296Jk/ansible_modlib.zip/ansible/module_utils/basic.py\", line 2813, in run_command\nOSError: [Errno 2] No such file or directory: '/vagrant/vendor/geerlingguy/drupal-vm/provisioning'\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 0}

followed by
There was an error loading a Vagrantfile. The file being loaded
and the error message are shown below. This is usually caused by
a syntax error.

Path: /drupal-vm/Vagrantfile
Line number: 11
Message: LoadError: cannot load such file -- /drupal-vm/vendor/geerlingguy/drupal-vm/Vagrantfile

I am using the composer dependency method as per https://github.com/geerlingguy/drupal-vm/blob/master/docs/deployment/composer-dependency.md
Any ideas please?

Id presume you have skipped some steps.
Can you update your issue with the default information that is requested when you create a new issue for this repo? Those should be supplied on helping debug this.
So on the drupal vm folder: you have got a composer.json, Vagrant file and a vendor folder present and those errors happen when you run vagrant up?

Hi @FinBoWa
Thanks for the reply. Sorry I didnt provide enough info in the first instance, It was late in the night and I didnt want to forget raising the issue..
So, here is how I set it up:
Step1
Created a new composer drupal project with
composer create-project drupal-composer/drupal-project:8.x-dev drupal-vm --stability dev --no-interaction

Step2
Added Drupal VM as composer dependency
composer require --dev geerlingguy/drupal-vm

Updated composer project
composer update

At this point I have the drupal-vm in the myproj/vendor/geerlingguy/drupal-vm/ folder
Step3
I created a new folder in the root, as follows, and created the config file
myproj
-- composer.json (one from drupal-composer/drupal-project)
-- Vagrantfile
-- config
---- config.yml
Contents of myproj/config/config.yml looks like this:
drupal_build_composer_project: false
drupal_build_composer: true
drupal_composer_path: false
drupal_composer_install_dir: "/var/www/drupalvm"
drupal_core_path: "{{ drupal_composer_install_dir }}/docroot"

Contents of myproj/Vagrantfile looks like this:
# The absolute path to the root directory of the project. Both Drupal VM and
# the config file need to be contained within this path.
ENV['DRUPALVM_PROJECT_ROOT'] = "#{__dir__}"
# The relative path from the project root to the config directory where you
# placed your config.yml file.
ENV['DRUPALVM_CONFIG_DIR'] = "config"
# The relative path from the project root to the directory where Drupal VM is located.
ENV['DRUPALVM_DIR'] = "vendor/geerlingguy/drupal-vm"

# Load the real Vagrantfile
load "#{__dir__}/#{ENV['DRUPALVM_DIR']}/Vagrantfile"

Step4
in the root folder myproj I am running:
vagrant up

That tries to go through and provision everything.... and I get the error above.

just tested with a empty folder with:
composer require --dev geerlingguy/drupal-vm
and your vagrant file
and vagrant up
It works just fine I just omitted your config and manual install of the drupal

Thank you @FinBoWa
Your Environment
Vagrant 2.0.0
5.1.28r117968
ansible: command not found

Your OS

macOS 10.12.6
Windows (version)
Linux (version)

Did you try to run drupal vm like i did? if it works there's something weird in your config.yml file.
Thought I do have ansible installed on my host and you haven't installed that on yours so its running the vagrant boxes ansible and losing the files at some point
According to this error you pasted:

TASK [geerlingguy.drupal : Run composer install.] ******************************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: OSError: [Errno 2] No such file or directory: '/vagrant/vendor/geerlingguy/drupal-vm/provisioning'
fatal: [drupalvm]: FAILED! => {"changed": false, "failed": true, "module_stderr": "Traceback (most recent call last):\n  File \"/tmp/ansible_x296Jk/ansible_module_composer.py\", line 264, in <module>\n    main()\n  File \"/tmp/ansible_x296Jk/ansible_module_composer.py\", line 252, in main\n    rc, out, err = composer_command(module, command, arguments, options, global_command)\n  File \"/tmp/ansible_x296Jk/ansible_module_composer.py\", line 185, in composer_command\n    return module.run_command(cmd)\n  File \"/tmp/ansible_x296Jk/ansible_modlib.zip/ansible/module_utils/basic.py\", line 2813, in run_command\nOSError: [Errno 2] No such file or directory: '/vagrant/vendor/geerlingguy/drupal-vm/provisioning'\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 0}
``

It cant find the file '/vagrant/vendor/geerlingguy/drupal-vm/provisioning' . either the nfs share isnt working or the ansible inside the vagrant box doesnt work right when run as depencency.

Anyways you should triage this by

1. run with miniman modifications > just use the vagrant file end dont do any config changes
2. if 1 fails try installing ansible on your host
3. if 1 works then your config is broken

Related but without any solutions https://github.com/geerlingguy/drupal-vm/issues/1359.

Hi @FinBoWa & @oxyc
Thank you again for your help.
I managed to get it installed with the following steps:
brew install ansible
and deleting the .vagrant folder inside y project. Completely removed the old VM and followed the steps I outlined in my post above.
I am getting this issue, BUT it is installed and my project is mounted correctly.
TASK [geerlingguy.drupal : Run composer install.] ******************************
fatal: [drupalvm]: FAILED! => {"changed": false, "failed": true, "msg": "> DrupalProject\\composer\\ScriptHandler::checkComposerVersion Loading composer repositories with package information Installing dependencies from lock file Package operations: 0 installs, 0 updates, 25 removals - Removing phpunit/phpunit (4.8.36) - Removing phpspec/prophecy (v1.7.2) - Removing phpunit/php-code-coverage (2.2.4) - Removing phpunit/php-token-stream (1.4.11) - Removing phpunit/php-file-iterator (1.4.2) - Removing phpunit/php-timer (1.0.9) - Removing phpunit/phpunit-mock-objects (2.3.8) [RuntimeException] Could not delete /var/www/drupalvm/vendor/phpunit/phpunit-mock-objects/tests/MockObject/Matcher/ConsecutiveParametersTest.php: install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--] [<packages>]...", "stdout": "> DrupalProject\\composer\\ScriptHandler::checkComposerVersion\nLoading composer repositories with package information\nInstalling dependencies from lock file\nPackage operations: 0 installs, 0 updates, 25 removals\n  - Removing phpunit/phpunit (4.8.36)\n  - Removing phpspec/prophecy (v1.7.2)\n  - Removing phpunit/php-code-coverage (2.2.4)\n  - Removing phpunit/php-token-stream (1.4.11)\n  - Removing phpunit/php-file-iterator (1.4.2)\n  - Removing phpunit/php-timer (1.0.9)\n  - Removing phpunit/phpunit-mock-objects (2.3.8)\n\n                                                                                \n  [RuntimeException]                                                                                \n  Could not delete /var/www/drupalvm/vendor/phpunit/phpunit-mock-objects/tests/MockObject/Matcher/ConsecutiveParametersTest.php:   \n                                                                                \n\ninstall [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--] [<packages>]...\n\n", "stdout_lines": ["> DrupalProject\\composer\\ScriptHandler::checkComposerVersion", "Loading composer repositories with package information", "Installing dependencies from lock file", "Package operations: 0 installs, 0 updates, 25 removals", "  - Removing phpunit/phpunit (4.8.36)", "  - Removing phpspec/prophecy (v1.7.2)", "  - Removing phpunit/php-code-coverage (2.2.4)", "  - Removing phpunit/php-token-stream (1.4.11)", "  - Removing phpunit/php-file-iterator (1.4.2)", "  - Removing phpunit/php-timer (1.0.9)", "  - Removing phpunit/phpunit-mock-objects (2.3.8)", "", "                                                                                ", "  [RuntimeException]                                                                                ", "  Could not delete /var/www/drupalvm/vendor/phpunit/phpunit-mock-objects/tests/MockObject/Matcher/ConsecutiveParametersTest.php:   ", "                                                                                ", "", "install [--prefer-source] [--prefer-dist] [--dry-run] [--dev] [--no-dev] [--no-custom-installers] [--no-autoloader] [--no-scripts] [--no-progress] [--no-suggest] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--ignore-platform-reqs] [--] [<packages>]...", ""]}

I'm wondering if there's a bug with the composer setup when ansible is running in the VM. Can't really see why it wouldn't work though.

I ran composer require --dev geerlingguy/drupal-vm command again and it worked for me.


[Blueprints] Add published blueprint object to the payload to support change notes

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-java

Automation for azure-sdk-for-go

Can one of the admins verify this patch?

@filizt , please make sure all checks are passed, thanks.

The model validation failures in the checks are caused by a tooling issue here: https://github.com/Azure/oav/issues/431. We had an another PR earlier this week that had the same failures but the they were suppressed and PR was merged since the failures were also due to the tooling issue. See here: https://github.com/Azure/azure-rest-api-specs/pull/6297
Could you help suppress the failures and merge the PR?

@erich-wang could you review the PR please?

@sergey-shandar, the check failure is caused by a bug in ova, please merge this PR, thanks.


Creating enhance api for deepstack SDK

The tests are not active yet; you need to add section for the Enhance class like it is added for other classes in this file
https://github.com/johnolafenwa/DeepStackPython/blob/dev/.github/workflows/pr_test.yml

Add a sample code section for the Enhance class at the end of the repository README

Add sample codes for the Enhance class into the examples folder. Add the following samples

enhance_file_to_file.py
enhance_pil_to_file.py
enhance_cv2_to_file.py


WIP: Feature: add 'hubType' label

An additional label to the metrics: hubType.
Possible values:

first: the hub is the first of the hubs on the path from src to dst
last: the hub is the one
first_last: the hub is the first AND last one
intermediate: the hub is one of many hops between first and last

Related #12

and it's all three at the same time it makes sense.

if first == last, then there is no intermediate.

Though honestly I've never seen that edge case because usually I measure things that are farther away.

Its usually the edge cases that makes programs crash up in flames .)

Okay, then I'll keep this around for a bit, you check out how much you like the feature and how well it works in real life.

Yah, and all are lower-cases. So, here I would need to transform the existing labels also. So, maybe worth doing it.

I still dislike the naming of hubType / hub_type.
Maybe step is better. Or hop … "first hop, intermediate hops, last hop" …

I'd say "hop" is the more commonly used word. And snake_case > camelCase, any time, any day, any place.
Using camelCase is for - pardon my french - Java developers.

camelCase: https://pkg.go.dev/strconv#pkg-functions
hop: so i'll adjust the PR to reflect that, than you toy around with it how it feels in practice.