Question service

Description
Implement Question service.
Paired with @carolinedanzi
Checklist

[X] Created tests which fail without the change (if possible)
[ ] Extended the README / documentation, if necessary

Issue(s)
#101 #102 #103

Ah gotcha, cool
On Fri, Feb 19, 2021 at 4:15 PM AWBaumann<EMAIL_ADDRESS>wrote:

@AWBaumann commented on this pull request.
In
universal-application-tool-0.0.1/app/services/question/QuestionDefinitionBuilder.java
https://github.com/seattle-uat/universal-application-tool/pull/197#discussion_r579548666
:

@@ -0,0 +1,91 @@
+package services.question;

+import com.google.common.collect.ImmutableMap;
+import java.util.Locale;
+import java.util.Optional;
+
+public class QuestionDefinitionBuilder {
I would have preferred that as well but I couldn't do that because that'd
create a circular dependency.
QuestionDefinition doesn't know about AddressQuestionDefinition.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/seattle-uat/universal-application-tool/pull/197#discussion_r579548666,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADTUR7G7OVJM42BWWMNJ3DS735KRANCNFSM4X5G7P2Q
.

--
[image: Google Logo]
Bion Johnson (he/him)
Senior Software Engineer & Google.org Software Engineering Lead
<EMAIL_ADDRESS>


"Carbon 1 is deprecated" warning

Hello! Recently I become to get this warning during composer update. Seems that yii2mod/yii2-behaviors depends on deprecated package "nesbot/carbon ~1.0".

Thanks for the issue, I'll update yii2mod/yii2-behaviors

created new release - https://github.com/yii2mod/yii2-behaviors/releases/tag/2.0

Still can't update. Did you merged release branch?


Update learning in each project based on README files of individual projects

The repository contains links to 15 open-sourced react projects.
Each project has it's own README containing a Learnings section.
We need to update the README in this repo with learnings listed in each individual project.
Sample learnings are added in first 2-3 projects as per README in each individual project.
This needs to be done for all the 15 projects listed.

I would like to contribute onto this project. Feel free to assign me this task.

@bineetNaidu Issue is assigned to you. You can make the required changes.

i would like to contribute onto this project

I would like to contribute to this issue

@subahan8055 and @AaronF3PS  Issue is assigned to you. You both can make the required changes.


Uncaught Error: Cannot read property 'object' of undefinedTypeError: Cannot read property 'objec...

[Enter steps to reproduce below:]

...
...

Atom Version: 1.9.8
System: Mac OS X 10.11.6
Thrown From: Atom Core
Stack Trace
Uncaught Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
at ObjectsRegistry.get (/Applications/Atom.app/Contents/Resources/electron.asar/browser/objects-registry.js:44:28)
at EventEmitter. (/Applications/Atom.app/Contents/Resources/electron.asar/browser/rpc-server.js:309:31)
at emitMany (events.js:121:13)
at EventEmitter.emit (events.js:195:7)
at EventEmitter. (/Applications/Atom.app/Contents/Resources/electron.asar/browser/api/web-contents.js:141:25)
at emitTwo (events.js:100:13)
at EventEmitter.emit (events.js:185:7)
At /Applications/Atom.app/Contents/Resources/electron.asar/renderer/api/remote.js:178

Error: Cannot read property 'object' of undefined
TypeError: Cannot read property 'object' of undefined
    at ObjectsRegistry.get (/Applications/Atom.app/Contents/Resources/electron.asar/browser/objects-registry.js:44:28)
    at EventEmitter.<anonymous> (/Applications/Atom.app/Contents/Resources/electron.asar/browser/rpc-server.js:309:31)
    at emitMany (events.js:121:13)
    at EventEmitter.emit (events.js:195:7)
    at EventEmitter.<anonymous> (/Applications/Atom.app/Contents/Resources/electron.asar/browser/api/web-contents.js:141:25)
    at emitTwo (events.js:100:13)
    at EventEmitter.emit (events.js:185:7)
    at metaToValue (/Applications/Atom.app/Contents/Resources/electron.asar/renderer/api/remote.js:178:13)
    at undefined.remoteMemberFunction (/Applications/Atom.app/Contents/Resources/electron.asar/renderer/api/remote.js:112:18)
    at ContextMenuManager.module.exports.ContextMenuManager.showForEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/context-menu-manager.js:172:33)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentContextmenu (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:250:47)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands
  3x -0:13 tree-view:remove (span.name.icon.icon-file-text)

Config
{
  "core": {
    "disabledPackages": [
      "atom-prettify",
      "atom-jshint",
      "linter-jshint",
      "rest-client",
      "unitjs",
      "vim-mode"
    ],
    "themes": [
      "one-dark-ui",
      "an-old-hope-syntax"
    ]
  },
  "editor": {
    "backUpBeforeSaving": true,
    "scrollPastEnd": true,
    "softWrap": true
  }
}

Installed Packages
# User
aesthetic-ui, v2.0.0 (inactive)
an-old-hope-syntax, v0.5.0 (active)
atom-beautify, v0.29.10 (inactive)
atom-jshint, v2.0.0 (inactive)
fancy-bracket-matcher, v0.4.1 (active)
file-icons, v1.7.18 (active)
language-nginx, v0.6.1 (active)
linter, v1.11.16 (active)
linter-jshint, v2.1.0 (inactive)
local-history, v3.3.0 (active)
minimap, v4.24.7 (active)
open-recent, v5.0.0 (active)
rest-client, v1.2.1 (inactive)
unitjs, v1.0.0 (inactive)
vim-mode, v0.65.1 (inactive)
atom-dark-syntax, v0.27.0 (inactive)
atom-dark-ui, v0.51.0 (inactive)
atom-light-syntax, v0.28.0 (inactive)
atom-light-ui, v0.43.0 (inactive)
base16-tomorrow-dark-theme, v1.1.0 (inactive)
base16-tomorrow-light-theme, v1.1.1 (inactive)
one-dark-ui, v1.3.2 (active)
one-light-ui, v1.3.2 (inactive)
one-dark-syntax, v1.2.0 (inactive)
one-light-syntax, v1.2.0 (inactive)
solarized-dark-syntax, v1.0.2 (inactive)
solarized-light-syntax, v1.0.2 (inactive)
about, v1.5.2 (active)
archive-view, v0.61.1 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.11.1 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.31.0 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.27.0 (inactive)
autosave, v0.23.1 (active)
background-tips, v0.26.0 (active)
bookmarks, v0.41.0 (active)
bracket-matcher, v0.82.1 (active)
command-palette, v0.38.0 (inactive)
deprecation-cop, v0.54.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.39.0 (active)
fuzzy-finder, v1.3.0 (active)
git-diff, v1.1.0 (active)
find-and-replace, v0.198.0 (inactive)
go-to-line, v0.31.0 (inactive)
grammar-selector, v0.48.1 (active)
image-view, v0.58.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.0 (active)
link, v0.31.1 (inactive)
markdown-preview, v0.158.0 (active)
metrics, v0.53.1 (active)
notifications, v0.64.1 (active)
open-on-github, v1.2.0 (inactive)
package-generator, v1.0.0 (inactive)
settings-view, v0.238.2 (active)
snippets, v1.0.2 (active)
spell-check, v0.67.1 (active)
status-bar, v1.4.1 (active)
styleguide, v0.46.0 (active)
symbols-view, v0.113.0 (inactive)
tabs, v0.98.1 (active)
timecop, v0.33.1 (active)
tree-view, v0.208.0 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.34.0 (active)
whitespace, v0.32.2 (active)
wrap-guide, v0.38.1 (active)
language-c, v0.52.1 (active)
language-clojure, v0.21.0 (active)
language-coffee-script, v0.47.0 (active)
language-csharp, v0.12.1 (active)
language-css, v0.36.2 (active)
language-gfm, v0.86.0 (active)
language-git, v0.13.0 (active)
language-go, v0.42.0 (active)
language-html, v0.44.1 (active)
language-hyperlink, v0.16.0 (active)
language-java, v0.22.0 (active)
language-javascript, v0.119.0 (active)
language-json, v0.18.0 (active)
language-less, v0.29.3 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.35.0 (active)
language-php, v0.37.0 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.0 (active)
language-ruby, v0.68.5 (active)
language-ruby-on-rails, v0.25.0 (active)
language-sass, v0.52.0 (active)
language-shellscript, v0.22.3 (active)
language-source, v0.9.0 (active)
language-sql, v0.21.1 (active)
language-text, v0.7.1 (active)
language-todo, v0.28.0 (active)
language-toml, v0.18.0 (active)
language-xml, v0.34.8 (active)
language-yaml, v0.26.0 (active)

# Dev
No dev packages

This is a duplicate of #11692 - feel free to subscribe there for updates.


A new cheatsheet for following the StackClub git workflow

This code is ready for review!  Could you take a look please, @Madejski ?
Here are particular items I am hoping for review:

The git merge steps described in the cheatsheet.
In general:  anything in particular missing?

Many thanks!

Thanks, @Madejski !  For some reason, I did not get any notifications in my inbox, so only saw your comments a bit later.  I will digest your suggestions and start making fixes.  Thanks!

(Maybe I did not get notifications because I forgot to assign myself to the pull request.  I just assigned myself.  We'll see if that works!)

OK, I am getting the notifications now (via e-mail).  This happened after I had assigned myself to the pull request, but I am not sure if doing this was the actual trigger for getting the notifications.  Strange...

Those were all minor.  I am planning to do a more extensive "road test" of your cheat-sheet - probably on Monday.  Thanks!  --Greg


Completes mempool transaction API

With this PR, the full Data API for Rosetta is implemented modulo
necessary protocol changes denoted in TODOs scattered across the
codebase.
Much testing is still needed after protocol changes come through.
These changes were tested by running the (currently commented-out) unit test in mempool and visually inspecting the output.

I'm combining these two PRs because they're too coupled in the changes I'm about to make


Python syntax warning on some az command groups

For me some command groups such as e.g. webapp and appservice (not an exhaustive list) any command causes python syntax warnings to appear. Example:
az webapp --help
/usr/local/Cellar/azure-cli/2.0.80/libexec/lib/python3.8/site-packages/azure/storage/blob/_upload_chunking.py:403: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if n is 0 or self._buffer.closed:
/usr/local/Cellar/azure-cli/2.0.80/libexec/lib/python3.8/site-packages/azure/storage/blob/baseblobservice.py:1009: SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if lease_duration is not -1 and \
/usr/local/Cellar/azure-cli/2.0.80/libexec/lib/python3.8/site-packages/azure/storage/blob/baseblobservice.py:2660: SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if lease_duration is not -1 and \
/usr/local/Cellar/azure-cli/2.0.80/libexec/lib/python3.8/site-packages/azure/storage/common/_connection.py:82: SyntaxWarning: "is" with a literal. Did you mean "=="?
  self.protocol = self.protocol if parsed_url.scheme is '' else parsed_url.scheme

Group
    az webapp : Manage web apps.

Subgroups:
    auth                        : Manage webapp authentication and authorization.
...

Environment summary
mac os Catalina (10.15.3)

@SaschaSchlemmer , thanks for reporting, we are looking at it.

I had the same issue on an Azure Pipeline Mac hosted agent. It seems the same version.
2020-02-07T18:25:59.5809080Z ##[error]Error: /usr/local/Cellar/azure-cli/2.0.80/libexec/lib/python3.8/site-packages/azure/multiapi/storage/v2018_11_09/blob/_upload_chunking.py:403: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if n is 0 or self._buffer.closed:
/usr/local/Cellar/azure-cli/2.0.80/libexec/lib/python3.8/site-packages/azure/multiapi/storage/v2018_11_09/blob/baseblobservice.py:1063: SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if lease_duration is not -1 and \
/usr/local/Cellar/azure-cli/2.0.80/libexec/lib/python3.8/site-packages/azure/multiapi/storage/v2018_11_09/blob/baseblobservice.py:2719: SyntaxWarning: "is not" with a literal. Did you mean "!="?
  if lease_duration is not -1 and \
/usr/local/Cellar/azure-cli/2.0.80/libexec/lib/python3.8/site-packages/azure/multiapi/storage/v2018_11_09/common/_connection.py:82: SyntaxWarning: "is" with a literal. Did you mean "=="?
  self.protocol = self.protocol if parsed_url.scheme is '' else parsed_url.scheme
/usr/local/Cellar/azure-cli/2.0.80/libexec/lib/python3.8/site-packages/azure/multiapi/cosmosdb/v2017_04_17/common/_connection.py:91: SyntaxWarning: "is" with a literal. Did you mean "=="?
  self.protocol = self.protocol if parsed_url.scheme is '' else parsed_url.scheme

Similarly on Linux:
$ az account list -o table
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if x is 0 or x is 1:
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if x is 0 or x is 1:
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif y is 0 or y is 1:
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif y is 0 or y is 1:
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:260: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if original_result is 0:

I am not sure why it even uses different Python versions:
$ az --version
azure-cli                         2.0.80 *

command-modules-nspkg              2.0.3
core                              2.0.80 *
nspkg                              3.0.4
telemetry                          1.0.4

Extensions:
azure-cli-iot-ext                  0.5.2

Python location '/home/cm/.pyenv/versions/3.8.1/bin/python3'
Extensions directory '/home/cm/.azure/cliextensions'

Python (Linux) 3.8.1 (default, Jan 30 2020, 16:51:40)
[GCC 9.2.1 20190827 (Red Hat 9.2.1-1)]

Legal docs and information: aka.ms/AzureCliLegal

You have 2 updates available. Consider updating your CLI installation. Instructions can be found at https://docs.microsoft.com/en-us/cli/azure/install-azure-cli

Please let us know how we are doing: https://aka.ms/clihats

I also have this issue on MacOS 10.15.4 with the latest Homebrew install of azure-cli.

I hit this today.  Fresh install of Catalina using azure cli from Homebrew

I now have this as well.  I updated to Fedora 32 and with it came Python 3.8 and these SyntaxWarnings.
I tried updating to the latest Azure CLI 2.6.0 but no change for my case.
I'm getting
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with a literal. Did you mean "=="?
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif y is 0 or y is 1:
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif y is 0 or y is 1:
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:260: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if original_result is 0:
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if x is 0 or x is 1:
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:32: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if x is 0 or x is 1:
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif y is 0 or y is 1:
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:34: SyntaxWarning: "is" with a literal. Did you mean "=="?
  elif y is 0 or y is 1:
/usr/lib64/az/lib/python3.6/site-packages/jmespath/visitor.py:260: SyntaxWarning: "is" with a literal. Did you mean "=="?
  if original_result is 0:

which is generated by several calls to
az servicebus topic subscription list ...

If the warnings are getting in the way, you can suppress them:
export PYTHONWARNINGS="ignore"

also hit this today, while performing an upload-batch to a storage account fileshare
az storage file upload-batch --account-name managementops --destination destionation --source source  --pattern '*.app' /usr/local/Cellar/azure-cli/2.8.0/libexec/lib/python3.8/site-packages/azure/multiapi/storage/v2018_11_09/blob/_upload_chunking.py:403: SyntaxWarning: "is" with a literal. Did you mean "=="?   if n is 0 or self._buffer.closed: /usr/local/Cellar/azure-cli/2.8.0/libexec/lib/python3.8/site-packages/azure/multiapi/storage/v2018_11_09/blob/baseblobservice.py:1063: SyntaxWarning: "is not" with a literal. Did you mean "!="?   if lease_duration is not -1 and \ /usr/local/Cellar/azure-cli/2.8.0/libexec/lib/python3.8/site-packages/azure/multiapi/storage/v2018_11_09/blob/baseblobservice.py:2719: SyntaxWarning: "is not" with a literal. Did you mean "!="?   if lease_duration is not -1 and \ /usr/local/Cellar/azure-cli/2.8.0/libexec/lib/python3.8/site-packages/azure/multiapi/storage/v2018_11_09/common/_connection.py:82: SyntaxWarning: "is" with a literal. Did you mean "=="?   self.protocol = self.protocol if parsed_url.scheme is '' else parsed_url.scheme /usr/local/Cellar/azure-cli/2.8.0/libexec/lib/python3.8/site-packages/azure/multiapi/cosmosdb/v2017_04_17/common/_connection.py:91: SyntaxWarning: "is" with a literal. Did you mean "=="?   self.protocol = self.protocol if parsed_url.scheme is '' else parsed_url.scheme There is no credential provided in your command and environment, we will query account key for your storage account.  Please provide --connection-string, --account-key or --sas-token as credential, or use --auth-mode login if you have required RBAC roles in your command. For more information about RBAC roles in stoarge, you can see https://docs.microsoft.com/en-us/azure/storage/common/storage-auth-aad-rbac-cli.  Setting corresponding environment variable can avoid inputting credential in your command. Please use --help to get more information. []
the issue is that the upload did not go trough

This is not app service but package issue I recommend using version 3.7 of Python on your Mac instead of 3.8.*

azure-storage-blob is replaced by azure-multiapi-storage and the syntax warning will be fixed by https://github.com/Azure/azure-multiapi-storage-python/pull/31

hi @fengzhou-msft https://github.com/Azure/azure-multiapi-storage-python/pull/31 is merged. Can this issue been closed now? thanks.

Resolved by #14785, please try with Azure CLI 2.11.0.


CBAPI-5151: Add devices pagination

Pull request checklist
Please check if your PR fulfills the following requirements:

[ ] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Tests have been added that prove the fix is effective or that the feature works.
[x] New and existing tests pass locally with the changes.
[x] Code follows the style guidelines of this project (PEP8, clean code, linter).
[x] A self-review of the code has been done.

What is the ticket or issue number?

Pull Request Description

Does this introduce a breaking change?

[ ] Yes
[x] No

How Has This Been Tested?

The current pagination would work, yet in our particular case it is inefficient. The reason for that is that the request to CBC is made from within a request handler in the Flask app and we cannot maintain context (CBCloudAPI and DeviceQuery) across subsequent HTTP requests to that route. On the UI side it is relatively easy to maintain state and keep track which rows we are currently visualising, but, whenever a request to the Flask backend is made (e.g "get me the list of devices from 300th to 400th"), in views.py we need to reinstantiate CBCloudAPI and do the device search again and since we cannot provide a starting row, that would always be from row 0. We could in theory maintain a pool of DeviceQuery objects on the Flask side if we had the session cookie, but the request to Flask is made via the QRadar app proxy, not directly by the browser and session information is stripped (we can only get the QRadar username doing the request, but that is not enough).

This would work, my concern is that it would be much slower than searching devices with search offset as we need to get up to 10000 devices while we only need the "page size" number of them and UI-wise it could be unacceptably slow to browse the list of devices.

Should this be a separate API call outside of CBC SDK device model selecting?

Hello,
I managed to get access to a work with 10000 endpoints (not real) provided by QA.
I did a quick test with two quick python scripts:
mrangelov@mrangelovYMD6R /tmp % cat a.py
from cbc_sdk import CBCloudAPI
from cbc_sdk.platform import Device

cb = CBCloudAPI()
devs = cb.select(Device).set_max_rows(10000)
last_page = devs[9900:10000]
data = []
for dev in last_page:
    data.append(dev._info)

mrangelov@mrangelovYMD6R /tmp % cat b.py
from cbc_sdk import CBCloudAPI
from cbc_sdk.platform import Device

cb = CBCloudAPI()
devs = cb.select(Device).set_max_rows(100).set_start(9900)
data = []
for dev in devs:
    data.append(dev._info)

Those are the timings:
mrangelov@mrangelovYMD6R /tmp % time python3 a.py
python3 a.py  1.27s user 0.20s system 29% cpu 5.015 total
mrangelov@mrangelovYMD6R /tmp % time python3 b.py
python3 b.py  0.70s user 0.12s system 49% cpu 1.644 total

So the difference is ~4.4 seconds.
I slightly changed the scripts to get devices from 1000th to 1100th and the results are similar (which is a bit surprising):
mrangelov@mrangelovYMD6R /tmp % cat a.py
from cbc_sdk import CBCloudAPI
from cbc_sdk.platform import Device

cb = CBCloudAPI()
devs = cb.select(Device).set_max_rows(10000)
last_page = devs[900:1000]
data = []
for dev in last_page:
    data.append(dev._info)

mrangelov@mrangelovYMD6R /tmp % cat b.py
from cbc_sdk import CBCloudAPI
from cbc_sdk.platform import Device

cb = CBCloudAPI()
devs = cb.select(Device).set_max_rows(100).set_start(900)
data = []
for dev in devs:
    data.append(dev._info)
mrangelov@mrangelovYMD6R /tmp % time python3 a.py
python3 a.py  1.25s user 0.19s system 25% cpu 5.583 total
mrangelov@mrangelovYMD6R /tmp % time python3 b.py
python3 b.py  0.72s user 0.12s system 51% cpu 1.631 total

However in a.py when I modify set_max_rows from 10000 to 1000 it makes sense:
time python3 a.py
python3 a.py  0.77s user 0.13s system 40% cpu 2.243 total

Looks like I made a mistake with the limitations of paging in the Devices API though, as I reread the developer network (need to address that in the code). There is no start+rows limit of 10000, instead we have rows limit of 10000 and start limit of 200000 (how do orgs with more than 200k endpoints work?)
Anyway, this leads me to the conclusion that the workaround (without providing start) gets slower and slower as the number of devices grows. With the workaround, we have a hard limit of rows up to 10k (would that still work if we need to get the 10001th device?). With the introduction of start parameter we can fetch up to 200k+10k devices and the execution time remains the same (around 1.6 seconds). With the workaround, the execution time increases with the overall number of devices that we have in the org.

Actually my tests were wrong, I was doing them on my branch. I switched back to develop and rerun time python3 a.py and now I get similar timing. So my only question would be, would it be possible (using just set_max_rows and slicing) to get devices past the 10000 set_max_rows limit?

Actually my tests were wrong, I was doing them on my branch. I switched back to develop and rerun time python3 a.py and now I get similar timing. So my only question would be, would it be possible (using just set_max_rows and slicing) to get devices past the 10000 set_max_rows limit?

As long as we didn't add any SDK checks we should be able to continue to paginate. Additionally if we want to get devices beyond 200k that is the intent behind the _scroll endpoint though that requires maintaining state with the search_after value.
Something we should consider is what problem are we trying to solve in QRadar with the device tab

The idea was to solve an issue that we had with orgs with large number of devices as they were all fetched and passed to the UI to do the pagination in the frontend. Once we started working on that, the next potential issue that we wanted to avoid was having an unresponsible UI as we are going to make a search request whenever we change the page and having to wait a long time wasn't desired. However, the timing tests convince me that no start parameter is needed and performance does not degrade linearly with the number of devices in the org. I will do some more tests to ensure we can get past max_rows by getting slices past it and if it works fine, I will drop that PR as it would not be needed.

That makes sense. I was also trying to frame why do we even have a device tab what problem are we solving for customers by having a device view in the app. By focusing on the problem we are trying to solve we can account for performance issues in other ways too. Do we really want to paginate 500k devices or should we be focusing more on device details and pivots back to the CBC console? or is this designed to given non CBC console users access.
Though based on the performance numbers I would say lets stay away from adding a set_start and if we truly need more granular fetching then we should approach that with a different mechanism that iterating the query

Not sure I see what issue you are referencing

devs[0:5] gets devices from index 0 to 4 as expected
devs[5:10] gets devices from index 4 to 8 (not 5..9)
devs[0:10] gets devices from 0 to 9 properly
This is a little bit unexpected, e.g:
>>> result = [0,1,2,3,4,5,6,7,8,9]
>>> result[0:5]
[0, 1, 2, 3, 4]
>>> result[5:10]
[5, 6, 7, 8, 9]
>>> result[0:10]
[0, 1, 2, 3, 4, 5, 6, 7, 8, 9]


Look for packages.dhall not spago.dhall at the root folder

When I setup a mono-repo as described in spago's documentation, I am instructed to put separate spago.dhall files in each subproject.  Therefore there is no spago.dhall at the root directory and I get this warning when I start my editor at the root directory.
Moving to a subproject directory like app1/ still fails since I no longer have a .spago/ or output/ folder in my working directory.
I think purescript-language-server should instead be checking for a packages.dhall file instead since it will always be at the root directory of the project and is a closer equivalent to a bower.json file.

More issues when trying to use the language server in a spago-mono repo.

The server will try to execute spago sources to get a list of sources but it needs to do spago -x <project>/spago.dhall sources to get the sources it needs for a project.

This can be bypassed by setting the sources in PURS_IDE_SOURCES
Or it a work around would be to have a "sourcesCommand" option which works similarly to "buildCommand".  It would also replace "addSpagoSources" and "addPscPackageSources"

If PURS_IDE_SOURCES is set then the server crashes with:Could not start the IDE server process. Check the configured port number is valid.
psci-ide-server error:{ code: ENOENT, errno: ENOENT, syscall: spawn node_modules/.bin/purs }

I don't know the exact cause of this but the .psc-ide-port exists in app1/ not at the project root.

Eh just found a better work around.  Just create a spago.dhall file at the project root and have it import and include all your subprojects' sources and dependencies.  Example
let liba =./liba/spago.dhall

let libb = ./libb/spago.dhall

let app1 = ./app1/spago.dhall

let app2 = ./app2/spago.dhall

in  { name =
        "spago-monorepo"
    , dependencies =
          liba.dependencies
        # libb.dependencies
        # app1.dependencies
        # app2.dependencies
    , sources =
          liba.sources # libb.sources # app1.sources # app2.sources
    , packages =
        ./pacakges.dhall
    }

Not sure what the intended process is for spago monorepos - the documentation wasn't enough for me and I've not had time to experiment - but I'm unlikely to support per-project build while opening at the top monorepo level. This language server does not have a "multi-root" support, so will not support doing something different per sub-project.
Either (which probably means both) we can support a whole-repo workflow (which is what I think your work-around does) or we can support opening the individual sub-project directory. The latter should include setting the output directory purescript.outputDirectory, not sure if spago will then give the correct sources, maybe there is little or nothing to do then?
The PURS_IDE_SOURCES sounds like a different issue that is not related to the monorepo, at first glance

From scanning spago's issues pages, it seems like there is no canonical or even consistent way for configuring mono-repos in spago.  I think the above workaround - having a root spago.dhall file that defines how to build all projects in the repo - should be considered ta solution.
That said there is an issue with my example,
, dependencies =
          liba.dependencies
        # libb.dependencies
        # app1.dependencies
        # app2.dependencies

would almost always result in there being multiple dependencies, and since explicity dhall prohibits any string equality functions we can't write a unique function to solve it.  Users will need to structure their dhall files to have a list of unique dependencies.  Something like
, dependencies =
          liba.dependencies
        # libb.extraDeps
        # app1.extraDeps
        # app2.extraDeps

might do.

@ptwales Would you mind leaving this issue open? The workaround you proposed doesn't actually work, for the reasons you outlined.

This problem will go away (or be less problematic) once Spago implements "targets".


Update script.sh

fix #1
Hi @agardnerIT,
trying to update duration variable, hopefully as your expected, please check it out

Thanks for the PR. This isn't quite complete yet. There are variables that can be removed. Please walk through the logic to try and understand why.
If you get stuck, LMK and I'll explain :)

Hi @agardnerIT,
already update script.sh by removed time_start variable. Are there any other variables that should be removed ? Please LMK


[DEVOPS-135] Resolving false negatives

@chrisgocode I have the following error after updating to this branch. The same command worked from the main branch:
PS D:\ed-fi\DevSecOps\edfi-repo-auditor> poetry run python .\edfi_repo_auditor\ -o Ed-Fi-Alliance-OSS -p $token -r Data-Management-Service -s -f dms.after
2024-07-29 10:24:32,258 - INFO - edfi_repo_auditor.auditor - Scanning repository Data-Management-Service
2024-07-29 10:24:32,475 - ERROR - __main__ - {'process': 'Query for Querying for protection rules for Ed-Fi-Alliance-OSS/Data-Management-Service.', 'error_message': '{"errors":[{"message":"Parse error on \\", owner: \\" (STRING) at [2, 45]","locations":[{"line":2,"column":45}]}]}', 'status_code': 200}
A fatal error occurred, please review the log output for more information.


Migrate to sbt-typelevel

Fudged the versioning for now. Let's see how this fares in CI.

Ok, this is a good first step 👍


Hugo documentation duplicated here

The example content source code incorporated here is a snapshot (taken two years ago) borrowed from its canonical location in spf13/hugo.
As I'm aware, Hugo's showcase of themes (spf13/hugoThemes) is generated by a shell script resident in repository spf13/generateThemeSite. Repeatedly (and desirably), Hugo's theme showcase presents the same default content, each time utilizing a different theme.
If any theme lacks its own example content (in its own directory exampleSite/content), the example content from this repository supplements it in the showcase (as this shell script line reveals).
For a showcase to present content repeatedly is good in many ways. However, here, apparently—in practice—some setup detail has led many themes to:

Re-borrow the example content from this repository; and
Incorporate it in their own source code!

When we look at a particular theme in the showcase, it makes no visible difference whether the identical content is:

Automatically copied (from this repository by the above shell script); or
Already present in the theme's source code.

Arguably, the combination of borrowing and incorporating content into this repository, and then presenting it automatically in Hugo's theme showcase (rather than simply referring to it):

Enables (or stimulates) certain themes to borrow and incorporate into their own repositories some of Hugo's documentation content; and
Obscures that they do so.

In a repository, incorporating borrowed Hugo documentation source code IMO is a bad thing—when we consider Hugo's presumed overall goals of keeping its documentation (found anywhere in the wild) up to date (as far as possible) and improving it.
Since this repository—along with some of the themes—is providing obsolete content in the showcase, it seems likely that people sometimes will read it. For people to read obsolete documentation in general IMO is undesirable for them, and for us.
For example, when we look at hugo-cactus-theme in the showcase, we observe that the creating-a-new-theme.md document (in its example site) is outdated, compared with Hugo's current copy of the same document.
Incorporating copies of documentation source code into other repositories isn't something people naturally do. However, once a piece of documentation source code has escaped "into the wild" (i.e., is copied into other repositories, due to people being encouraged to do so), it's extremely difficult—naturally—to keep it up to date (in those copies).
This problem should be corrected IMO sooner rather than later, before the increasing number of Hugo themes further worsens the problem.
Perhaps this example content would be better as Lorem ipsum text? Or would it be better if the shell script automatically copied this example content from spf13/hugo each time it runs?
Which solution is preferable (or perhaps another)?
Presently, Hugo's user base seems large enough to benefit from such a change. And this repository IMO seems the best place to start.
Currently, nineteen (19) repositories (beyond this one) have incorporated some of the spf13/hugo documentation source code. The problematic theme sites are:

appernetic: hugo-bootstrap-premium
crakjie: hugo-base-theme
devcows: hugo-universal-theme
dgraph-io: hugo-dgraph-theme
digitalcraftsman:

hugo-cactus-theme
hugo-hikari-theme
hugo-icarus-theme
hugo-minimalist-theme
hugo-steam-theme
hugo-strata-theme
hugo-type-theme

djuelg: Shapez-Theme
Eisenbarth: slender
jbub: ghostwriter
jpescador: hugo-future-imperfect
lambdafu: hugo-finite
syui:

hugo-theme-arch
hugo-theme-wave, in two (2) places: here and here

yoshiharuyamashita: blackburn

Here are some references (for your enjoyment):

Single-source information (Agile Modeling)
Orthogonality & the DRY principle (Artima Developer)
Don't repeat yourself (Wikipedia)
Don't repeat yourself (Ward's Wiki)
Once & only once (Ward's Wiki)

@digitalcraftsman I've extensively rewritten the above issue. Would you please take another look, and give me the benefit of your thoughts? :)


Discuss project governance, relationships upstream and down

@tomwhite
@fnothaft
@ryan-williams
@jacarey
@tfenne
@lbergelson
@cmnbroad
@droazen
@magicDGS
@vdauwera
@cseed
Sorry to @-mention you all here on this issue, but unfortunately I only know some of you by your github handles.
I would like to invite you all to attend, in person or virtually, the OpenBio Winter Codefest 2018 on Thursday Jan 18th and Friday Jan 19th in Boston, MA.
https://www.open-bio.org/wiki/Codefest_Winter_2018
Hadoop-BAM is an upstream dependency shared by GATK4 and ADAM (and possibly also Hail?) and is in need of clarification around project governance, similar to the process recently undertaken by htsjdk (https://github.com/samtools/htsjdk/issues/871).  I see the Codefest as a good opportunity to discuss this and then branch out into other areas of possible collaboration between the various projects.
One possible way forward would be to incubate at Apache Software Foundation a new project starting from Hadoop-BAM, extending out into bdg-formats, bdg-utils, and ADAM on our side and common/utility code extracted from GATK4 and Hail, and perhaps even upstream into htsjdk.  We welcome friendly competition on algorithms and analyses, but there is no reason to duplicate effort on the underlying technology stack.
Please feel free to discuss here on this issue or in the Codefest Gitter chat room.  We can refine an agenda on the Codefest shared project ideas doc.  Hope to meet some of you in Boston!

Just getting back after being on leave for a month... Glad to see this being discussed. Are there any outcomes or discussions from the Codefest that you can share here @heuermh?
@kheljanko thanks for sharing the information about the virus paper - sounds interesting!

I've written a bit about a new Spark API on this ticket: #196. I've now added a page describing the scope and features of the new API. There's also a bit about a home and governance, which it would be good to discuss more.
@cmnbroad, @droazen, @fnothaft, @heuermh, @kheljanko, @lbergelson, @magicDGS, @ryan-williams (and others who are interested) - I'd like to propose an online meeting. If you are interested in participating, please fill in this Doodle poll to select a day: https://doodle.com/poll/fikirnp8wwsh6bfa
Thanks!

I'd love to join the discussion, but unfortunatelly I will be on vacation next week. I'm looking forward to see the result of the meeting here, so please keep us update on this thread. Thanks!

Thanks to everyone who responded to the Doodle poll! The result is here: https://doodle.com/poll/fikirnp8wwsh6bfa, Apr 10, 2018 at 5pm UK time (GMT+1). Unfortunately, there wasn't a slot that suited everyone, so @magicDGS and @kheljanko won't be able to make it - please let me know if you have anything you'd like to relay to the meeting.
Here's the hangout link: https://meet.google.com/amb-zxti-qwe

I would like to:

Extract BGZF and related non-biology functionality from htsjdk and donate it to Apache Commons-IO or another general purpose library.
Rewrite core htsjdk domain classes for API correctness, style, and immutability.  I have an approach here.  There are others.
Evolve htsjdk into a reference implementation of the various specifications, or develop new reference implementation(s).  https://github.com/samtools/htsjdk/commit/d181e9ea3415c956a0aeb100d640bc63731b138a
Combine the best of the various approaches to distributed reading/writing native bioinformatics formats (Hadoop-BAM, spark-bam, this branch, ADAM + bdg-utils, GATK4, Hail, Google Nucleus, etc.) into a single library or set of libraries.
Convert between domain models using a common library.  I have an approach here, with biojava & ga4gh and other conversions.  ADAM converts between htsjdk ↔ bdg-formats.
Collaborate successfully on these shared upstream dependencies, and compete on downstream applications/analyses.

V short summary of the meeting. There were three technical areas (raised by Frank):

Better split picking (from spark-bam)
htsjdk compatibility and generalization (e.g. more efficient representations for variants)
Spark RDDs vs datasets/dataframes (datasets are more efficient)

There was general agreement for all of these being in scope for a new project. There may need to be some phasing - e.g. have RDD implementations with existing htsjdk classes, and add others (e.g. dataset) in the future.
After discussing governance and hosting the next steps  are (summarized by Ryan):

New code goes in a new GitHub repo under the samtools org
MIT-licensed
Credit to the lineage of the ideas and code (Hadoop-BAM, spark-bam)
Find a new name

Regarding naming, in the meeting a couple of names were suggested:

dist-bio
hts-sharded

I'd also like to put forward the following (in the Spark sequencing vein):

squark
speeq

I said I would send out a poll for the name. If you have any ideas or suggestions, please post them here so I can include them in the vote.

Also

Implement directly on Spark Datasource v2 APIs

I wouldn't say that any decisions have been made with regards to hosting under the samtools organization or that the software license should be MIT.  Part of the trouble with not having project governance is that no process is in place to make decisions.
How about this for a proposal:

Create a new repository unaffiliated any Github organization initialized with the MIT license.
Give write permissions to anyone on this thread, on the call, or otherwise interested.
Establish a process to make decisions.  I suggest using the Apache Voting Process where everyone from step 2 are initially given binding votes.
Create issues/pull requests for various discussion topics: Github organization, repository name, domain name, Maven coordinates (groupId, artifactId), software license, copyright assignment, code of conduct, Contributor License Agreement (CLA), Github project administration, documentation hosting, the release process, code signing keys, etc.
As discussion settles on any given topic, call for a vote.  Vote passes with at least three +1s and no -1s.

I will help with any or all of those.

My opinion about some points brought by @heuermh and the summary by @tomwhite:

HTSJDK related changes: I agree with you about non-biological code moving away from HTSJDK and move to a proper API-based library (and thus, to v3). But I believe that this is an effort that should be solved at the htsjdk level (and its governance). There are several discussions about it and I have also several proposals (check ...)
I agree with a new project combining the best from other projects, but I think that it is quite important to have a time-frame to have a functional library which provides full support as the current Hadoop-BAM. Otherwise, the efforts for maintaining this repository and the new one would delay the inclusion and fix of new code into downstream software.
I agree with a proper voting system to decide most of the governance stuff. Nevertheless, I disagree with starting a new repository before deciding some basics that can be discussed on this thread (or a different one). The basics before starting the new repository, from my point of view, are: project name and GitHub affiliation. Otherwise, the project might change ownership and link before even started, making it difficult to track from people not involved in the governance discussion. I do agree that once the repo with the new name (and under either samtools, HadoopGenomics or a new organiztion), discussion can start in different issues/PRs for license, etc.
Move to a different project sounds like a nice idea to fix stuff from scratch, but what that means for the fate of this project? If this is going to become an archived project, maybe others not included in this issue should be included in the voting process. And also it should be evaluated the impact on downstream projects...

Thus, my proposal is a bit different than the one from @heuermh:

Create a poll for name and affiliation
Create the new repository as decided
Start discussion on issues/PRs on that repository about the rest of topics: process to make decisions is the most important, but also about the rest.
Finally, decide the new design and what is needed in upstream projects (e.g., HTSJDK changes)

It seems like I may have misunderstood what was agreed (if only tentatively) in the meeting regarding github org (samtools) and license (MIT). In the meantime, here’s the code I’ve been working on (temporary location): https://github.com/tomwhite/squark.
@magicDGS regarding the fate of this project - it still needs to be maintained at least until any replacement has a superset of functionality. I plan to do another Hadoop-BAM release next week with a few changes.

I've created a nameless Genomics on Apache Spark organization and repository
https://github.com/nameless-gos/nameless
I'll flesh out the issues there with details from this issue and the email thread from the meeting.

I'd like to organise another meeting to see if we can make some progress on the new project. I've created a poll at https://doodle.com/poll/k9hc9sgbf9uhue7i to find a time. Please select which times you can make if you are interested in attending. Thanks.

Hi @tomwhite! I would love to join, but can't make any of the dates due to travel and other commitments. Can we do a time in June?

@fnothaft Sure - I was thinking of running a monthly meeting at least while we get things set up so I'll add a new poll for June - and go ahead with a meeting this month too (probably next week now).

Thanks everyone who responded to the poll! The result is here: https://doodle.com/poll/k9hc9sgbf9uhue7i. The time of the meeting is 5pm (GMT+1) on Tue May 22. Here's the hangout link: https://hangouts.google.com/hangouts/_/calendar/dG9tLmUud2hpdGVAZ21haWwuY29t.7grvb1g73s1svncmcg840jt6ee?authuser=0.

Thanks to everyone who attended the meeting. There was a desire expressed to work together on foundational projects to avoid duplication, starting with a more tightly-scoped focus than perhaps before - i.e. a Spark-native Hadoop-BAM project (Squark). We have actually been working on Hadoop-BAM together over the last few years, so it would be worth seeing how we can continue that with a better defined governance model.
Actions: please comment on the governance issues here: https://github.com/nameless-gos/nameless/issues.

Note the Github organization and repository have changed, the new link is:
https://github.com/disq-bio/disq/

@tomwhite and I would like to submit an abstract on Disq to the BOSC 2019 conference.
Please consider adding your contact information and author affiliation to the following shared doc
https://docs.google.com/document/d/1by-YA5FQra8CyqMHOwa6278fNM0fZpD8PDD5XxLOIPM/edit?usp=sharing

I took the liberty of adding @lbergelson in his absence, since he probably won't see this in time.

Sorry for the ping, closing an old issue.


Fix explore link

resolves Azure/azure-sdk-for-python#25325

Docs Build status updates of commit a3536c4:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/latest/power-bi.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/latest/power-bi.md

Line 2, Column 1: [Warning: ms-date-missing - See documentation] Missing required attribute: 'ms.date'. A freshness date is required for this content set. Add a date in format MM/DD/YYYY.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8cb64f3:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/latest/power-bi.md
:white_check_mark:Succeeded
View (azure-python)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@lmazuel Could you please review and merge this? Thanks!

Docs Build status updates of commit 510d62e:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-services/latest/power-bi.md
:warning:Warning
View (azure-python)
Details

docs-ref-services/latest/power-bi.md

Line 2, Column 1: [Warning: ms-date-missing - See documentation] Missing required attribute: 'ms.date'. A freshness date is required for this content set. Add a date in format MM/DD/YYYY.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8a824f8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/latest/power-bi.md
:white_check_mark:Succeeded
View (azure-python)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit d978d12:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-services/latest/power-bi.md
:white_check_mark:Succeeded
View (azure-python)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


How to start servers?

 It seems to have successfully deployed, but when I ssh into the machines no relevant processes seem to be running. Can anyone shed some light on what should be the next step in getting everything to run?
Thanks!

Ok so this is pretty tough to answer without diving into a rabbit hole.
This repo is mainly used to configure our servers so they have all the right processes and software to run commcare hq. what you've done with the vagrant setup is essentially test that setup in VMs.
This is supposed to be run on actual machines, a cluster if you will; the instructions in the readme are bit misleading. you essentially need 4 things for this to work for you:

A control machine. Ansible needs to be on a machine for it to run and have access to the machines it's going to run commands on.

An inventory file. There's a sample one in this repo that will setup the services on the VMs. Our production inventory can be found here. You can read more about them in the ansible docs.

A vars file. There's a sample one in this repo called dev.yml. It has all the variables that configure HQ and have reasonable defaults.

Once all the machines have the correct software, you'll need to deploy using our fabric deploy system (fab <your_env> deploy). This will actually start all the software and connect the services to the Django web server.

The process can be involved and the documentation is probably lacking at the moment. Apologies for the complexity but it's somewhat innate with having a complex application with lots of functionality that needs to work in different environments. Hope this helps a bit.

Hi @benrudolph thanks so much - I was a bit worried I was missing something obvious. I think I'll continue with setting everything up in docker, but this seems to be the best documentation of what dependencies are needed, so it's still a big help. Am I correct in understanding that fabric should then be run from the app1 server? I guess that's where it lives, right?
No need to apologize, I think it's wonderful what you are guys are contributing to the community with CommcareHQ. I might submit a pull request for some updated docs for the main repository - it's a bit misleading now as to how to get the system up and running - what do you think?

I might submit a pull request for some updated docs for the main repository - it's a bit misleading now as to how to get the system up and running - what do you think?

This would be great!

fabric would be run from your local machine to app1. it'd take some configuration to tell it to run on that VM. but if you're simply trying to run a local instance, use ./manage.py runserver see Running CommCareHQ. ansible is for your production rig. +1 to the PR idea!

Right. the main reason I am interested is that there seems to be a lot of dependencies that ansible takes care of automatically, whereas setting everything up manually with docker, as I am trying do now, is a bit difficult. In any case I am trying to get close to a production rig. The internet connection in Bissau is not exactly stellar, so I am trying to get as much as possible in order from home.


Dialog调confirm方法时，传unmountOnExit为false提示警告：Warning: You are calling ReactDOMClient.createRoot() on a container that has already been passed to createRoot() before. Instead, call root.render() on the existing root instead if you want to update it.

[ ] I'm sure this does not appear in the issue list of the repository

Basic Info

Package Name And Version<EMAIL_ADDRESS>

Dialog调confirm方法时，传unmountOnExit为false提示警告：Warning: You are calling ReactDOMClient.createRoot() on a container that has already been passed to createRoot() before. Instead, call root.render() on the existing root instead if you want to update it.
传unmountOnExit为true没问题

@limingxxoo 同学，你的react/react-dom版本号发一下呢，看起来是用的react18对吧？

@limingxxoo 同学，你的react/react-dom版本号发一下呢，看起来是用的react18对吧？

对18，

@limingxxoo 同学，你的react/react-dom版本号发一下呢，看起来是用的react18对吧？

对18，
"react": "^18.2.0",
"react-dom": "^18.2.0",

@limingxxoo 这个问题已复现并修复，本周发个正式版~

<EMAIL_ADDRESS>已发布


Write guide for how users can map domain to Route53

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/625
Originally created by @bencodezen on 2019-04-30 20:00:04

Problem to solve
Users need to know how to map their ECS instance to a domain name and not use the IP address.
Target audience
Any user setting up their ECS deployment.
Further details
Benefit: Users prefer domain names over IP addresses
Proposal

[ ] Setup a sample ECS instance
[ ] Setup a Route53 domain
[ ] Connect the two together
[ ] Write guide for doing so

What does success look like, and how can we measure that?
Users will be able to map their IP addresses to Route53.
Regression test
(Ensure the feature doesn't cause any regressions)

[ ] Write adequate test cases and submit test results
[ ] Test results should be reviewed by a person from the team

Links / references
Please note that this was taken from GitLab, to be changed accordingly

View 2 previous comments from the original issue on GitLab