Update app links to point to monorepo where appropriate

Some docs have URLs pointing to the legacy repos: github.com/OSC/ood-$APP. They should be updated to point to the mono repo at github.com/OSC/ondemand/tree/master/apps/$APP.
For example: https://github.com/OSC/ood-documentation/blob/develop/source/applications/dashboard.rst

NC166819:source mrodgers$ ag 'https://github\.com/OSC/ood-.+'
app-development/tutorials-passenger-apps/ps-to-quota.rst
13:The app we will be copying is: https://github.com/OSC/ood-example-ps. Running
120:   #. Git remote: ``https://github.com/OSC/ood-example-ps``

app-development/tutorials-interactive-apps/add-rstudio/copy-app.rst
120:   Launch button in the developer views. This `was fixed in 1.5 <https://github.com/OSC/ood-dashboard/pull/435>`_.

app-development/tutorials-interactive-apps/add-matlab/copy-app.rst
120:   Launch button in the developer views. This `was fixed in 1.5 <https://github.com/OSC/ood-dashboard/pull/435>`_.

app-development/tutorials-interactive-apps/add-jupyter/copy-app.rst
120:   Launch button in the developer views. This `will be fixed in 1.5 <https://github.com/OSC/ood-dashboard/pull/435>`_.

customization.rst
408:.. _Dashboard: https://github.com/OSC/ood-dashboard/blob/v1.33.4/config/locales/en.yml
409:.. _Job Composer: https://github.com/OSC/ood-myjobs/blob/v2.14.0/config/locales/en.yml

installation/resource-manager/test.rst
61:   <https://github.com/OSC/ood-dashboard/issues/364>`_.

installation/from-source/core-apps.rst
19:  .. _ood-activejobs: https://github.com/OSC/ood-activejobs/
20:  .. _ood-dashboard: https://github.com/OSC/ood-dashboard/
21:  .. _ood-fileeditor: https://github.com/OSC/ood-fileeditor/
22:  .. _ood-fileexplorer: https://github.com/OSC/ood-fileexplorer/
23:  .. _ood-myjobs: https://github.com/OSC/ood-myjobs/
24:  .. _ood-shell: https://github.com/OSC/ood-shell/

release-notes/v1.0-release-notes.rst
85:Please refer to the `Changelog <https://github.com/OSC/ood-portal-generator/blob/v0.4.0/CHANGELOG.md>`__ for details.
98:Please refer to the `Changelog <https://github.com/OSC/ood-dashboard/blob/v1.15.2/CHANGELOG.md>`__ for details.
112:Please refer to the `Changelog <https://github.com/OSC/ood-shell/blob/v1.2.3/CHANGELOG.md>`__ for details.
117:Please refer to the `Changelog <https://github.com/OSC/ood-fileexplorer/blob/589eb45945ede692628c2d07a6680c5acd7e2a58/CHANGELOG.md>`__ for details.
123:Please refer to the `Changelog <https://github.com/OSC/ood-activejobs/blob/v1.5.0/CHANGELOG.md>`__ for details.
134:Please refer to the `Changelog <https://github.com/OSC/ood-myjobs/blob/v2.5.0/CHANGELOG.md>`__ for details.
155:.. _ood-portal-generator: https://github.com/OSC/ood-portal-generator
159:.. _Dashboard App: https://github.com/OSC/ood-dashboard
160:.. _Shell App: https://github.com/OSC/ood-shell
161:.. _Files App: https://github.com/OSC/ood-fileexplorer
162:.. _File Editor App: https://github.com/OSC/ood-fileeditor
163:.. _Active Jobs App: https://github.com/OSC/ood-activejobs
164:.. _My Jobs App: https://github.com/OSC/ood-myjobs
166:.. _ood-apps-installer: https://github.com/OSC/ood-apps-installer

release-notes/v1.5-release-notes.rst
196:     - 1.30.2 → `1.31.0 <https://github.com/OSC/ood-dashboard/blob/v1.31.0/CHANGELOG.md>`__
197:       (`diff <https://github.com/OSC/ood-dashboard/compare/v1.30.2...v1.31.0>`__)
205:     - 1.6.9 → `1.7.0 <https://github.com/OSC/ood-activejobs/blob/v1.7.0/CHANGELOG.md>`_
206:       (`diff <https://github.com/OSC/ood-activejobs/compare/v1.6.9...v1.7.0>`__)
208:     - 2.10.2 → `2.11.0 <https://github.com/OSC/ood-myjobs/blob/v2.11.0/CHANGELOG.md>`__
209:       (`diff <https://github.com/OSC/ood-myjobs/compare/v2.10.2...v2.11.0>`__)

release-notes/v1.1-release-notes.rst
92:Please refer to the `Changelog <https://github.com/OSC/ood-dashboard/blob/v1.17.0/CHANGELOG.md>`__ for details.
106:Please refer to the `Changelog <https://github.com/OSC/ood-activejobs/blob/v1.5.1/CHANGELOG.md>`__ for details.
116:Please refer to the `Changelog <https://github.com/OSC/ood-myjobs/blob/v2.6.0/CHANGELOG.md>`__ for details.
131:.. _ood-portal-generator: https://github.com/OSC/ood-portal-generator
135:.. _Dashboard App: https://github.com/OSC/ood-dashboard
136:.. _Shell App: https://github.com/OSC/ood-shell
137:.. _Files App: https://github.com/OSC/ood-fileexplorer
138:.. _File Editor App: https://github.com/OSC/ood-fileeditor
139:.. _Active Jobs App: https://github.com/OSC/ood-activejobs
140:.. _Job Composer App: https://github.com/OSC/ood-myjobs
142:.. _ood-apps-installer: https://github.com/OSC/ood-apps-installer

release-notes/v1.4-release-notes.rst
127:     - 1.26.2 → `1.30.2 <https://github.com/OSC/ood-dashboard/blob/v1.30.2/CHANGELOG.md>`__
128:       (`diff <https://github.com/OSC/ood-dashboard/compare/v1.26.2...v1.30.2>`__)
130:     - 1.3.1 → `1.4.2 <https://github.com/OSC/ood-shell/blob/v1.4.2/CHANGELOG.md>`__
131:       (`diff <https://github.com/OSC/ood-shell/compare/v1.3.1...v1.4.2>`__)
133:     - 1.4.1 → `1.5.0 <https://github.com/OSC/ood-fileexplorer/blob/v1.5.0/CHANGELOG.md>`__
134:       (`diff <https://github.com/OSC/ood-fileexplorer/compare/v1.4.1...v1.5.0>`__)
136:     - 1.3.3 → `1.4.0 <https://github.com/OSC/ood-fileeditor/blob/v1.4.0/CHANGELOG.md>`_
137:       (`diff <https://github.com/OSC/ood-fileeditor/compare/v1.3.3...v1.4.0>`__)
139:     - 1.6.2 → `1.6.8 <https://github.com/OSC/ood-activejobs/blob/v1.6.8/CHANGELOG.md>`_
140:       (`diff <https://github.com/OSC/ood-activejobs/compare/v1.6.2...v1.6.8>`__)
142:     - 2.8.3 → `2.10.1 <https://github.com/OSC/ood-myjobs/blob/v2.10.1/CHANGELOG.md>`__
143:       (`diff <https://github.com/OSC/ood-myjobs/compare/v2.8.3...v2.10.1>`__)
170:The PUN will autogenerate its own unique per-user secret key base string which is generated at first launch if it doesn't exist. This is used by Rails apps to encrypt cookies and overrides the default one set in `env.production <https://github.com/OSC/ood-dashboard/blob/a20cae91fb0f636c8a7e3fc8dfe508d9afa34d50/.env.production#L1>`__.
190:Batch Connect applications may now define a Javascript file to add interactive frontend functionality. `Github OSC/ood-dashboard#426 <https://github.com/OSC/ood-dashboard/pull/426>`_.
223:Resolved a pair of issues (`#48 <https://github.com/OSC/ood-shell/issues/48>`_, `#55 <https://github.com/OSC/ood-shell/issues/55>`_) that caused problems with copy and paste in the Shell application.
228:Introduction of a whitelist mode for the Dashboard navbar which is disabled by default. This change means that by default, when deploying a new app, if properly configured it will appear in the Dashboard's navigation menu without the need for changing configuration. `OSC/ood-dashboard#295 <https://github.com/OSC/ood-dashboard/issues/295>`__
235:The Dashboard can now display a configurable disk usage warning to the user if they approach a certain usage threshold. This feature is enabled by defining the environment variable ``OOD_QUOTA_PATH`` which can take a colon delimited path, and may be defined in ``/etc/ood/config/nginx_stage.yml`` under the ``custom_env`` map. The version 1 format for quota files is defined in the `Dashboard README <https://github.com/OSC/ood-dashboard/blob/v1.30.2/README.md#disk-quota-warnings>`__.
240:Slurm 18.x introduced `a bug <https://bugs.schedmd.com/show_bug.cgi?id=6120>`__ with the fields `gres` or `tres` in `squeue` output which `broke prior versions <https://github.com/OSC/ood-activejobs/issues/169>`__ of the Slurm adapter. The OOD team has both updated the OOD Slurm adapter to function normally despite the bug, and submitted a fix which Slurm will be releasing in a future version.

release-notes/v1.2-release-notes.rst
56:     - `0.4.0 <https://github.com/OSC/ood-portal-generator/blob/v0.4.0/CHANGELOG.md>`__
81:     - 1.17.0 → `1.18.0 <https://github.com/OSC/ood-dashboard/blob/v1.18.0/CHANGELOG.md>`__
82:       (`diff <https://github.com/OSC/ood-dashboard/compare/v1.17.0...v1.18.0>`__)
84:     - 1.2.3 → `1.2.4 <https://github.com/OSC/ood-shell/blob/v1.2.4/CHANGELOG.md>`__
85:       (`diff <https://github.com/OSC/ood-shell/compare/v1.2.3...v1.2.4>`__)
87:     - 1.3.5 → `1.3.6 <https://github.com/OSC/ood-fileexplorer/blob/v1.3.6/CHANGELOG.md>`__
88:       (`diff <https://github.com/OSC/ood-fileexplorer/compare/v1.3.5...v1.3.6>`__)
90:     - `1.3.1 <https://github.com/OSC/ood-fileeditor/blob/v1.3.1/CHANGELOG.md>`__
92:     - 1.5.1 → `1.5.2 <https://github.com/OSC/ood-activejobs/blob/v1.5.2/CHANGELOG.md>`__
93:       (`diff <https://github.com/OSC/ood-activejobs/compare/v1.5.1...v1.5.2>`__)
95:     - 2.6.0 → `2.6.1 <https://github.com/OSC/ood-myjobs/blob/v2.6.1/CHANGELOG.md>`__
96:       (`diff <https://github.com/OSC/ood-myjobs/compare/v2.6.0...v2.6.1>`__)
107:.. _ood-portal-generator: https://github.com/OSC/ood-portal-generator
111:.. _Dashboard App: https://github.com/OSC/ood-dashboard
112:.. _Shell App: https://github.com/OSC/ood-shell
113:.. _Files App: https://github.com/OSC/ood-fileexplorer
114:.. _File Editor App: https://github.com/OSC/ood-fileeditor
115:.. _Active Jobs App: https://github.com/OSC/ood-activejobs
116:.. _Job Composer App: https://github.com/OSC/ood-myjobs
118:.. _ood-apps-installer: https://github.com/OSC/ood-apps-installer

release-notes/v1.3-release-notes.rst
178:     - 0.4.0 → `0.7.1 <https://github.com/OSC/ood-portal-generator/blob/v0.7.1/CHANGELOG.md>`__
179:       (`diff <https://github.com/OSC/ood-portal-generator/compare/v0.4.0...v0.7.1>`__)
205:     - 1.18.0 → `1.26.2 <https://github.com/OSC/ood-dashboard/blob/v1.26.2/CHANGELOG.md>`__
206:       (`diff <https://github.com/OSC/ood-dashboard/compare/v1.18.0...v1.26.2>`__)
208:     - 1.2.4 → `1.3.1 <https://github.com/OSC/ood-shell/blob/v1.3.1/CHANGELOG.md>`__
209:       (`diff <https://github.com/OSC/ood-shell/compare/v1.2.4...v1.3.1>`__)
211:     - 1.3.6 → `1.4.1 <https://github.com/OSC/ood-fileexplorer/blob/v1.4.1/CHANGELOG.md>`__
212:       (`diff <https://github.com/OSC/ood-fileexplorer/compare/v1.3.6...v1.4.1>`__)
214:     - 1.3.1 → `1.3.3 <https://github.com/OSC/ood-fileeditor/blob/v1.3.3/CHANGELOG.md>`_
215:       (`diff <https://github.com/OSC/ood-fileeditor/compare/v1.3.1...v1.3.3>`__)
217:     - 1.5.2 → `1.6.2 <https://github.com/OSC/ood-activejobs/blob/v1.6.2/CHANGELOG.md>`_
218:       (`diff <https://github.com/OSC/ood-activejobs/compare/v1.5.2...v1.6.2>`__)
220:     - 2.6.1 → `2.8.3 <https://github.com/OSC/ood-myjobs/blob/v2.8.3/CHANGELOG.md>`__
221:       (`diff <https://github.com/OSC/ood-myjobs/compare/v2.6.1...v2.8.3>`__)
357:.. _ood-portal-generator: https://github.com/OSC/ood-portal-generator
361:.. _Dashboard App: https://github.com/OSC/ood-dashboard
362:.. _Shell App: https://github.com/OSC/ood-shell
363:.. _Files App: https://github.com/OSC/ood-fileexplorer
364:.. _File Editor App: https://github.com/OSC/ood-fileeditor
365:.. _Active Jobs App: https://github.com/OSC/ood-activejobs
366:.. _Job Composer App: https://github.com/OSC/ood-myjobs

release-notes/v1.6-release-notes.rst
61:     - 1.31.0 → `1.35.0 <https://github.com/OSC/ood-dashboard/blob/v1.35.0/CHANGELOG.md>`__
62:       (`diff <https://github.com/OSC/ood-dashboard/compare/v1.31.0...v1.35.0>`__)
64:     - 1.4.2 → `1.4.6 <https://github.com/OSC/ood-shell/blob/v1.4.6/CHANGELOG.md>`__
65:       (`diff <https://github.com/OSC/ood-shell/compare/v1.4.2...v1.4.6>`__)
67:     - 1.5.1 → `1.5.3 <https://github.com/OSC/ood-fileexplorer/blob/v1.5.3/CHANGELOG.md>`__
68:       (`diff <https://github.com/OSC/ood-fileexplorer/compare/v1.5.1...v1.5.3>`__)
70:     - 1.4.1 → `1.4.3 <https://github.com/OSC/ood-fileeditor/blob/v1.4.3/CHANGELOG.md>`__
71:       (`diff <https://github.com/OSC/ood-fileeditor/compare/v1.4.1...v1.4.3>`__)
73:     - 1.7.0 → `1.9.2 <https://github.com/OSC/ood-activejobs/blob/v1.9.2/CHANGELOG.md>`__
74:       (`diff <https://github.com/OSC/ood-activejobs/compare/v1.7.0...v1.9.2>`__)
76:     - 2.11.0 → `2.15.0 <https://github.com/OSC/ood-myjobs/blob/v2.15.0/CHANGELOG.md>`__
77:       (`diff <https://github.com/OSC/ood-myjobs/compare/v2.11.0...v2.15.0>`__)
129:.. _ood-mjobs#291: https://github.com/OSC/ood-myjobs/issues/278
207:.. _ood-fileexplorer#191: https://github.com/OSC/ood-fileexplorer/issues/191
208:.. _ood-myjobs#285: https://github.com/OSC/ood-myjobs/issues/285

applications/shell.rst
6:`View on Github <https://github.com/OSC/ood-shell>`__

applications/job-composer.rst
8:`View on GitHub <https://github.com/OSC/ood-myjobs>`__

applications/dashboard.rst
6:`View on GitHub <https://github.com/OSC/ood-dashboard>`__

applications/active-jobs.rst
6:`View on GitHub <https://github.com/OSC/ood-activejobs>`__

applications/editor.rst
6:`View on GitHub <https://github.com/OSC/ood-fileeditor>`__

applications/files.rst
6:`View on GitHub <https://github.com/OSC/ood-fileexplorer>`__

applications.rst
17:     - https://github.com/OSC/ood-dashboard
19:     - https://github.com/OSC/ood-shell
21:     - https://github.com/OSC/ood-fileexplorer
23:     - https://github.com/OSC/ood-fileeditor
25:     - https://github.com/OSC/ood-activejobs
27:     - https://github.com/OSC/ood-myjobs

issues/overview.rst
41:        OSC/ood-fileexplorer#198
55:        OSC/ood-fileexplorer#187
66:        OSC/ood-fileexplorer#185
77:        OSC/ood-fileexplorer#196
88:        OSC/ood-fileexplorer#173
99:        OSC/ood-dashboard#465
112:        OSC/ood-dashboard#417
123:        OSC/ood-dashboard#397
131:        OSC/ood-dashboard#171
149:        OSC/ood-shell#57
160:        OSC/ood-shell#28
171:    OSC/ood-shell#16

@matthu017 to do this you will need to setup an environment to build the documentation. This uses Python. Docker can be used to build the documentation which will be easier, but you need to install Docker on your laptop.
Also this is 1.7 related, so it should be done off the 1.7 release branch, not the develop branch.

I was just about to open a new issue but I think this is the correct place to ask/note this:
The Tutorials > Add a Jupyter App > Copy Jupyter App section instructs users to git https://github.com/OSC/bc_example_jupyter.git
Both of these repos exist...

https://github.com/OSC/bc_example_jupyter
https://github.com/OSC/bc_osc_jupyter
...but the former hasn't had a commit for almost a year, so especially after seeing this issue, it seems like the tutorial should be pointing to the newer one?

Sort of related, a lot of the paths that are referenced within the tutorials seem like they need to be updated. Taking RStudio's tutorial as an example, Git actually clones to: ~/ondemand/dev/RStudio/, but...
RStudio's Software Requirements page references:

~/ondemand/dev/bc_example_rstudio/install-compute-dependencies.sh

...and RStudio's Customize Attributes page references:

~/ondemand/dev/bc_example_rstudio/form.yml
~/ondemand/dev/bc_example_rstudio/template/script.sh.erb

...and the Deploy RStudio App page references:

sudo cp -r bc_example_rstudio /var/www/ood/apps/sys/

@jasonbuechler thank you for the report. The https://github.com/OSC/bc_example_jupyter is for the tutorial. The https://github.com/OSC/bc_osc_jupyter is the one that OSC uses. So that's why that is different there.
The RStudio tutorial is a bug, however. The simplest solution would be to change the start of the tutorial so that the directory name is "bc_example_rstudio" not "RStudio". Then the rest of the tutorial would be the same.

My apologies -- after I spent more time looking through those repos, I realized the nature of those repos and probably should have deleted half of that comment. But thank you for verifying!

Fixed in https://github.com/OSC/ood-documentation/pull/234


ball is beeing blocked

Description
ball is not offensive and it is being blocked by the bot
Screenshots

@qwe123coder  is this issue still open??

i think its closed let me check

@qwe123coder is this issue still open??

ya there is a pr for this but not merged yet

Here is the PR link https://github.com/AbhijithGanesh/EddieBot/pull/1/files


Update README with NSPhotoLibraryAddUsageDescription

closes #923 #906 #927

@lwansbrough hi :)
Could you review this PR, please?
Thanks!!!


Allow http(s) as constraint file

Alternative to #2038.
In my opinion, this is probably overshooting.
Contributor checklist

[ ] Included tests for the changes.
[ ] PR title is short, clear, and ready to be included in the user-facing changelog.

Maintainer checklist

[ ] Verified one of these labels is present: backwards incompatible, feature, enhancement, deprecation, bug, dependency, docs or skip-changelog as they determine changelog listing.
[ ] Assign the PR to an existing or new milestone for the target version (following Semantic Versioning).

piptools/scripts/types.py:6:1: F401 'typing.Optional' imported but unused

Not exactly sure of this failure.

Converted to a draft as it is not ready due to failing checks and missing tests.

I added a comment in the other PR explaining why this is dangerous: https://github.com/jazzband/pip-tools/pull/2038#issuecomment-1874188017.


Add Blackmagic CLFs

Added CLFs for Blackmagic Film Wide Gamut (Gen 5) and DaVinci Intermediate Wide Gamut.  Many thanks to the staff at Blackmagic for reviewing the CLFs and providing helpful comments!
Enhanced create_conversion_matrix to allow use of the CAT02 chromatic adaptation method needed by the above transforms.  In addition, set "use_derived_transformation_matrices(True)" on the RGB_COLOURSPACES objects to align with the computational method used by both the Academy CTL reference and the OCIO built-ins.
Using the derived transformation matrices resulted in some changes to the matrices in the existing OCIO Utility CLFs but this is desired since they now match the corresponding OCIO built-in transforms.
Signed-off-by: Doug Walker<EMAIL_ADDRESS>

Following the conversation at the last working group, I've added CLFs for the linear (matrix-only) color space and the log-to-lin curve named transform.  Please take a look at the naming/ID to see if you have any suggestions.
@KelSolaar , @michdolan , I would appreciate your review since I plan to use it as the pattern for the other cameras this  week.


Alignment of How to add Task section

The alignment of How to Add Task section can be improved.

I want to work on this under JWOC.


Consider halt codes

Reason
Though rare, while MS-DOS had its own error codes, DD-DOS (not vDOS) COULD have its own "halt codes", whenever it panics. These codes can also be used and returned within the CLI, even for files not found.
Format
SHOULD be a 2-byte number.
Either plain or reserve a few bits (4?) for categorize things around.
Source Code
To void confusion with the vDOS codes, DD-DOS halt codes COULD take the DD_E_ prefix. Messages appends the _M suffix.
Example (CLI): DD_E_FILE_NOT_FOUND = 5 and DD_E_FILE_NOT_FOUND_M = "File was not found."
panic
panic SHOULD stay with the string+number signature.
It's easier to add an error code then add the panic line at one place than add the panic line + extra code in panic code.

Done a few commits ago, manual is up to date as well (2018.1)


Exception : Additional text encountered after finished reading JSON content

I am using this amazing library to read JSON response from InfluxDB.  With Chunked responses, the class is similar to Online generated
public class Series
{
    public string name { get; set; }
    public List<string> columns { get; set; }
    public List<List<object>> values { get; set; }
    public bool partial { get; set; }
}

public class Result
{
    public int statement_id { get; set; }
    public List<Series> series { get; set; }
    public bool partial { get; set; }
}

public class RootObject
{
    public List<Result> results { get; set; }
}

The response I get from InfluxDB is
{"results":[{"statement_id":0,"series":[{"name":"ChunkTest","columns":["time","Val"],"values":[[1490584276233503400,0],[1490584276247138800,1],[1490584276263674700,2],[1490584276277906600,3],[1490584276293388400,4],[1490584276311209600,5],[1490584276326084200,6],[1490584276341423000,7],[1490584276357200800,8],[1490584276372130200,9]],"partial":true}],"partial":true}]}
{"results":[{"statement_id":0,"series":[{"name":"ChunkTest","columns":["time","Val"],"values":[[1490584276700208200,30],[1490584276716050800,31],[1490584276731527700,32],[1490584276746938100,33],[1490584276763240500,34],[1490584276778480700,35],[1490584276793635900,36],[1490584276809912100,37],[1490584276825775700,38],[1490584276841033300,39]],"partial":true}],"partial":true}]}
{"results":[{"statement_id":0,"series":[{"name":"ChunkTest","columns":["time","Val"],"values":[[1490584276856816700,40],[1490584276871956700,41],[1490584276887248800,42],[1490584276903294600,43],[1490584276918772500,44],[1490584276935431700,45],[1490584276950390900,46],[1490584276965931500,47],[1490584276981850300,48],[1490584276996947400,49]]}]}]}

While trying to parse this I am getting an exception Newtonsoft.Json.JsonReaderException with an message Additional text encountered after finished reading JSON content: {. Path '', line 2, position 0.
THe position is for the second line, but I am not sure what is the issue, the same content in the online class generator (which too uses same library) is just fine.
Note: The class is correct, and if I get only one line it just works fine.

Ask on Stackoverflow

@JamesNK Thanks, I found that the InfluxDB is sending a malformed JSON, raised https://github.com/influxdata/influxdb/issues/8212

Having a similar issue is there a fix to this


Incorrect description in SQL Database REST API?

Hi folks,
I am trying to execute a failover REST request following: https://docs.microsoft.com/en-us/rest/api/sql/failovergroups/failover?source=docs
From the doc, it shows that:

Apparently during my testing (via postman), this isn’t not correct.
It’s supposed to be the secondary (target) server name which we’d like to failover.
FYI, this is the error that I am getting if I define “serverName” which containing the failover group.
{
"error": {
"code": "FailoverGroupFailoverRequestOnPrimary",
"message": "The failover request should be initiated on the secondary server of failover group."
}
}
Unfortunately there’s no way for me to edit / submit a pull request on the doc.
So, raising this here.
For the owner of the doc, feel free to reach out to me to verify / clarification.

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

ID: d36567a2-90d8-8764-0b7d-dee312844c2d
Version Independent ID: 60ed26b8-8344-d6ec-3ad7-6c59cf1402f8
Content: Configure a failover group - Azure SQL Database
Content Source: articles/sql-database/sql-database-configure-failover-group.md
Service: sql-database
Sub-service: high-availability
GitHub Login: @MashaMSFT
Microsoft Alias: mathoma

@wely Thank you for bringing this to our attention. The way the REST API docs and functional specs are addressed is through this repository: azure-rest-api-specs. The dev team will triage and correct both documentation and api issues. This channel does not support REST issues. I apologize for having to redirect you and until we have a better way to communicate the process, I need to redirect you to this other repository. Please create an issue there and I will link it to this issue for tracking purposes. Thank you!

Hi @Mike-Ubezzi-MSFT , i have created another one there: https://github.com/Azure/azure-rest-api-specs/issues/9557

@wely We will proceed to close this issue now.
Please follow the issue on azure-rest-api-specs repo for further updates.


Netsparker scan parsing failure

Bug description
Netsparker vulnerability export can have multiple CWE values or "" defined in a single entry, causing the parser to fail
https://github.com/DefectDojo/django-DefectDojo/blob/13cdb6a0f3905c8db3bd73d86b376eacfa97d5d7/dojo/tools/netsparker/parser.py#L53
Steps to reproduce
Import a Netsparker scan with multiple CWE field values
        "Cwe": "937, 1035",
Expected behavior
Single value for CWE used
Deployment method (select with an X)

[X] Docker
[ ] Kubernetes
[ ] GoDojo
[ ] setup.bash / legacy-setup.bash

Environment information

Operating System: 20.04.2 LTS
DefectDojo Commit Message: [2021-07-09 16:41:23 -0500] 24477ef3: Add release cadence to README (#4796) [ (HEAD -> master, origin/master, origin/HEAD)]

Sample scan files
scan-report-name-vulnerabilities-15_07_2021 11_26 AM.txt

Fixed with #4826


⚠ Bofrost.nl has degraded performance

In df9f8f8, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 864 ms

Resolved: Bofrost.nl performance has improved in be702e5.


Missing proposal-trait.clar file

Due to missing proposal-trait.clar file it is impossible to run test suite.
On top of that CI is producing false positive results: https://github.com/alexgo-io/alex-v1/runs/5458993192?check_suite_focus=true

Hi @LNow , we use a custom dependency management tool, please run the following and try running test suites again.
> cd <project root>/clarity
> sh ./scripts/clarinet_manager.sh update alex_dao main
> sh ./scripts/clarinet_manager.sh install alex_dao

The list of dependencies (not all are required) is available here: https://github.com/alexgo-io/alex-v1/blob/main/clarity/Clarinet.json
@caoer , fyi

Hey @fiftyeightandeight !
It doesn't work anyway.
https://github.com/alexgo-io/alex-dao-proposals is not accessible - I bet it is a private repository.

Yes, https://github.com/alexgo-io/alex-dao-proposals is a private repo. Have you tried with this private repo removed from https://github.com/alexgo-io/alex-v1/blob/main/clarity/Clarinet.json? That should work.

Without alex-dao-proposals it works as it should.


Dace race in EVP_KEYEXCH_fetch()

EVP_KEYEXCH_fetch first calls evp_generic_fetch() and then separately fetches an EVP_KEYMGMT object. Finally it associates the EVP_KEYMGMT object with the EVP_KEYEXCH object. However as soon as evp_generic_fetch returns the EVP_KEYEXCH object has been cached and may be returned by an EVP_KEYEXCH_fetch call from another thread. So now the threads are competing to associate the EVP_KEYEXCH object with an EVP_KEYMGMT object.

Note there is a similar issue in EVP_CIPHER_fetch and EVP_MD_fetch. #9590 attempts to resolve the issues in those functions.

A thought: maybe the association should happen in evp_keyexch_from_dispatch instead of in EVP_KEYEXCH_fetch().  It means that we need to pass down the library context and the properties, but I think we can live with that...

That was the solution I came up with for EVP_CIPHER_fetch and EVP_MD_fetch in #9590, although there the issue was quite a bit simpler.


Vagrant 1.8 support

Verify molecule works properly with the release of Vagrant 1.8.

First attempt failed:
$ molecule create --platform trusty64
Vagrant failed to initialize at a very early stage:

The plugins failed to load properly. The error message given is
shown below.

Unable to find binary extension, was hitimes installed correctly?
ERROR: Command '['/usr/local/bin/vagrant', 'up', '--no-provision']' returned non-zero exit status 1

Ok I solved the issue by doing rm -fr ~/.vagrant.d. Now molecule is working fine with the latest Vagrant and VirtualBox.

Ok I solved the issue by doing rm -fr ~/.vagrant.d. Now molecule is working fine with the latest Vagrant and VirtualBox.

Yeah, same issue solved my problem.  I'm okay with this being a reasonable solution to upgrading to a newer version of Vagrant.

Verified Vagrant 1.8 is working as expected while validating #66.


Uncaught TypeError: Cannot read property 'firstChild' of null

I followed the steps provided in the documentation but I am unable to get it working. I am getting the following error message
Uncaught TypeError: Cannot read property 'firstChild' of null

in the https://maps.google.com/maps/api/js script. From the error message, what I understand is that the script is trying to call the method firstChild method on a Node object but it's null.
I am not sure how to solve this. Any help would be appreciated.

My bad. I was trying to load the script before DOM was loaded. I moved the script to the end of the body and things went fine.
I'll close the issue as it was mistake from my side.

My bad. I was trying to load the script before the DOM was loaded. I moved the script to the end of body and it worked fine.

I have been 2 days trying delete cache for several methods! but the solution was this! Thanks mate ;-)


Warning  in the new HA beta

Logger: homeassistant.helpers.frame
Source: helpers/frame.py:77
First occurred: 13:46:27 (4 occurrences)
Last logged: 13:47:29

Detected integration that called async_setup_platforms instead of awaiting async_forward_entry_setups; this will fail in version 2023.3. Please report issue to the custom integration author for weatherbit using this method at custom_components/weatherbit/__init__.py, line 165: hass.config_entries.async_setup_platforms(entry, WEATHERBIT_PLATFORMS)

Closed with V1.0.19


Update build date/ version methodology

@mzy2240 - would you have time to tackle this today? I gained some information from PowerWorld this morning:

There's a way to get both the version number, and the build date in a date format: GetParametersSingleElement( "PowerWorldSession", ["Version", "ExeBuildDate"], ["", ""])

We could run this in init and simply add a version attribute to SAW. Then, we wouldn't have to mess around with any of the writing to file stuff.

Ok


Random subsampling of reads from BAM files

I'm trying something like this https://www.biostars.org/p/76791/
How can I do it using biobear?
I started from this
session = bb.connect()

subsampling_seed=42
number_of_reads=50000

bam = session.sql(f"""
    SELECT *
    FROM bam_scan('{BAM}') bam
""")

Then I could also do this which is not exactly random selection
bam = session.sql(f"""
    SELECT *
    FROM bam_scan('{BAM}') bam
    LIMIT {number_of_reads}
""")

Finally I'm trying this which is not exactly what I should do:

@tshauck – what do you think? Thanks for your helps!

@abearab Hey, I think you were very close... could you try, ORDER BY RANDOM(), though I don't think you can set the seed if that's critical.
Also, I should make this clearer, but biobear leverages Apache DataFusion for general purpose SQL functions, standard joins, etc, and you can see info about which functions are available here: https://arrow.apache.org/datafusion/user-guide/sql/index.html (in addition to the specialized ones I've added like reverse_complement). E.g. the docs for random.

@abearab Hey, I think you were very close... could you try, ORDER BY RANDOM(), though I don't think you can set the seed if that's critical.

I see, thanks for the correction. I just tried it and it's seems it's working now.

Also, I should make this clearer, but biobear leverages Apache DataFusion for general purpose SQL functions, standard joins, etc, and you can see info about which functions are available here: https://arrow.apache.org/datafusion/user-guide/sql/index.html (in addition to the specialized ones I've added like reverse_complement). E.g. the docs for random.

Cool, I'll look into datafusion docs. Thanks
Two questions / comments:

how can I write bam files after I made these kind of manipulation?
it took 20 minutes and it didn't finish [for 26G BAM file], should I just keep waiting or there is a faster way for this? I also tried sambamba with 10 cores but that also didn't finish after 20-30 minutes.

Regrettably one cannot write files yet. I need to finish supporting reading CRAM files, then the next major thing is supporting file output.

I think you answered my question here, I'm going to close this issue for now to cleanup your repo! Thanks

Thanks!


Travis Testing

Just testing Travis for now, will create a new PR when the work is finalized

Looks good to me.


Make header for top 3s more noticeable, maybe bold?

@partini Explain more about in this part. Specify in details please!


Fix incorrect message when opening SC while unauthenticated

Everything was correct, but the configuration sent to the alert was the same as the one that is shown when secure conversations are unavailable because the queue doesn't support it.
MOB-2032

!merge


Can sequential module be distributed into mulit machines and how?

Can sequential module be distributed into multi machines and how?
@eric-haibin-lin

@quietsmile   Hope you got answer to your question. For further queries , you can use https://discuss.mxnet.io/.
@sandeep-krishnamurthy  Please close this issue.


Removing non-working packages jderobot_camviz and jderobot_carviz to avoid failure emails from ros buildfarm

Please add the following dependency to the rosdep database.
Package name:
TODO
Package Upstream Source:
TODO link to source repository
Purpose of using this:
TODO Replace. This dependency is being used for this reason. This is why I think it's valuable to be added to the rosdep database.
Distro packaging links:
Links to Distribution Packages

Debian: https://packages.debian.org/

REQUIRED

Ubuntu: https://packages.ubuntu.com/

REQUIRED

Fedora: https://src.fedoraproject.org/browse/projects/

IF AVAILABLE

Arch: https://www.archlinux.org/packages/

IF AVAILABLE

Gentoo: https://packages.gentoo.org/

IF AVAILABLE

macOS: https://formulae.brew.sh/

IF AVAILABLE

Alpine: https://pkgs.alpinelinux.org/packages

IF AVAILABLE

NixOS/nixpkgs: https://search.nixos.org/packages

OPTIONAL

Please Add This Package to be indexed in the rosdistro.
ROSDISTRO NAME
The source is here:
http://sourcecode_url
Checks

[ ] All packages have a declared license in the package.xml
[ ] This repository has a LICENSE file
[ ] This package is expected to build on the submitted rosdistro

When removing a package, no old versions of it will be kept around for users to install (see item 4.).
Are you okay with that?

Hello! Yes that is fine with me.


[question] LoadAdError: unable to resolve host, should be internal error (code 0) or network error (code 2)?

as title

Hi @peterweb2005
When opening an issue, please provide information indicated in the issue template so that we can verify the issue properly, see Bug report template.
More specifically, please provide:

A completed and minimal reproducible code sample
The complete output of flutter run -v which contains entire stack trace of error.
The current ads plugin version you are using
Which environment did this issue happen in? (Android/iOS)

Regarding the error message above,  maybe the device does not have an internet connection, using proxy or on airplane mode. Please make sure ad request is not blocked by these reasons.

so, for the error code 0,
the party consider that is client error not network error?
which, if error code 0, should i ask user to retry the network, or check anything happend?
can any suggestions to handle error code 0 at runtime?

For error code 0, it's probably because you used the wrong ID as I gave in this issue.
For error code 2, it's probably related to network issue, you can ask user to retry to see if it happens again.

but i what see:
LoadAdError(code: 0, domain: com.google.android.gms.ads, message: Error while connecting t
o ad server: Unable to resolve host "googleads.g.doubleclick.net": No address associated with hostname, responseInfo: ResponseInfo(responseId: null, mediationAdapterClassName: , adapterResp
onses: [], loadedAdapterResponseInfo: null), responseExtras: {})

For that error, I would like to forward the same case from Developer Forum here: https://groups.google.com/g/google-admob-ads-sdk/c/-bDd5tNp0ns/m/6Skb8p33mzcJ

One common reason for this is that your device is not able to contact a dns server in order to perform a lookup.
This most common reason for this is that your device doees not have a network connection.

This issue doesn't seem to be related to the google mobile ads flutter plugin, so I will close it from here. If you disagree, please write in comments with more info or reach out to our support team on the Developer Forum. Thanks!

yes, you call that dns error, but it comes to error code 0, network error should be code 2

i found that, in ios, the client network error will not state code 0, still code 2, LoadAdError(code: 2, domain: com.google.admob, message: The Internet connection appears to be offline


policy: Keep track of dependent (deny) entries

MapState entries that should be deleted together with some other
entry are "dependent entries". These are created for some deny
entries. Keep track of them, and delete them when the main entry is
deleted via an incremental update that happens when an identity is
removed.

test-me-please

flake in test-1.19-5.4 should be fixed in https://github.com/cilium/cilium/pull/16990.

Superseded by #16258, closing.


website is generating rkt documentation incorrectly

see api usage links that go to 404s while in github they work fine
https://coreos.com/rkt/docs/latest/subcommands/api-service.html#using-the-api-service
vs
https://github.com/coreos/rkt/blob/master/Documentation/subcommands/api-service.md

Let's track this on the website repository.


fix: custom plugins

Since we aren't using the build-in GH Pages renderer, like Scikit-HEP was, we can add custom plugins. Adding one for tabs (designed after the Hugo one I use on iscinumpy.dev), details (ditto), and rr (shorter and faster than an include). Fixed more more old-style note.
We should add --deployment to the learn repo too, should be a bit better (and won't include rubocop).

@jarrodmillman could you look into fixing the webhooks for readthedocs.org for this repo and repo-review? I don't have permission to.
Could not send GitHub build status report for scientific-python-cookie. Make sure you have the correct GitHub repository permissions and your [GitHub account](https://readthedocs.org/accounts/social/connections/) is connected to Read the Docs.

Could not send GitHub build status report for repo-review. Make sure you have the correct GitHub repository permissions and your [GitHub account](https://readthedocs.org/accounts/social/connections/) is connected to Read the Docs.

Read the docs is building PRs, but it doesn't have permissions to update the PR with the status.
Build is at https://readthedocs.org/projects/scientific-python-cookie/builds/21172843/ for this one, for example.


make a clean (without react) client server demo

I think we need to add a simple mosca server with minimal code
and minimal web client (static html) js page
so people can understand the basic and run the client from browser console commands
so they can see simplest way to establish MQTT connection

Excellent point.
In fact, I prepared exactly this in the file WWW/mqtt-client.html --- but for some reason, this file ended up empty in the repository.  This is a bug that will be fixed soon...

I uploaded the WWW/mqtt-client.html file --- it is a very simplistic jquery 'chat' client.  Execute this:
git pull         # this will pull in the new file and fixes
npm install  # probably NOOP if you did this before
npm start    # start the mosca server

If you did this on your own computer, try the simple chat: http://<IP_ADDRESS>:8080/mqtt-client.html
You can connect to the simple chat client on my server: http://mqtt-meetup-yaakov-belch.c9users.io/mqtt-client.html
If you run this on c9 (as recommended), exchange the domain name by your corresponding domain name.  Please note that c9 usually uses https URLs (which is normally better) --- but for our chat examples, we need http URLs.  Why?  That's a separate question to answer.
Please keep this issue open until I updated the documentation of this script (in the README.md file and possibly in the wiki).


Bump bdg-formats dependency to version 0.12.0.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/ADAM-prb/2945/
Test PASSed.


Fix type switch on ID's initializing identifier

Given the following signature of ID.__Init__:
class ID:
    def __init__(
        self,
        identifier: Union[str, Sequence[str], "ID"],
        location: Location = None
    ) -> None:

... the type switch on identifier should be matching against Sequence instead of list.

Oops, commit on the wrong branch :(

Superseded by #1010.


Forced volume mount in Docker image

Hello,
The current Logspout Docker image contains the following Dockerfile instruction:
VOLUME /mnt/routes

This causes Docker to always mount a volume for the container into the /mnt/routes mount-point, regardless of the user desiring or not to persist ephemeral routes.
According to the README file, one would assume that mounting a volume for persisting routes is opt-in instead of forced:

Routes are stored on disk, so by default routes are ephemeral. You can mount a volume to /mnt/routes to persist them.

The issue with forcing a volume is that all Logspout containers start to pollute the Docker volumes subsystem with unnecessary volumes (if the user does not require persistence). For example:
$ docker volume ls
DRIVER              VOLUME NAME
local               artifactory_data
local               b1d471d60ec5676c173b729f1db87a7e3f540539c3986ba3be11887c924cace6
local               loki_data
local               prometheus_data
local               grafana_data
local               portainer_data

The more Logspout instances you have, the more of these unnamed volumes you get. Moreover, users that want to mount the volume in a different location than /mnt/routes and use ROUTESPATH are also affected by this pollution.
Please note that at this time it is not possible to "unset" a VOLUME instruction during container-instantiation in Docker. Therefore there is no way to avoid this unless having your own custom Dockerfile for Logspout without the VOLUME instruction.
I believe that we can safely remove this instruction here in upstream instead and avoid users having to create custom images that don't have functional differences except disabling the volume.
Users that actually want to mount a volume will not see any difference anyway.
Thoughts?

Hi @michaelshobbs , sorry to ping you :)
Would you have some time to take a look on this issue?
It is the last remaining issue from logspout in our deployment that needs a bit of attention.
If you are okay with the proposed change I can make a PR for you as well. Thanks!

TL;DR I have questions on why but would accept a PR with specific requirements.
I've been thinking about this off and on since this issue was opened. I'd prefer not to remove this as it easily gives us a sane default for route persistence. Since this concern has not been brought up before, I'd like to understand better why having this default mount is a problem in your environment. So a couple questions:

What is the problematic effect of having these unnamed volumes?
Why run multiple logspout instances on a single docker instance? (logspout is supposed to be able to send all logs from a docker instance to whatever logging services the user would like)

Regarding removing the default mount. I would accept a PR that removes the mount and:

maintains the default behavior
tests the default and overridden ROUTESPATH behaviors
updates the documentation with a usable example

Hello, sorry for the long delay coming back to this. I forgot to reply because we are not using Logspout anymore and switched to Vector to implement our use-case and also to unify other observability use-cases we work with. I will anyway answer your questions below for closure.

What is the problematic effect of having these unnamed volumes?

The problem is more on the management point-of-view (i.e. humans) than technical. Volume management starts to become harder due to the clutter and hard to read volume names. This generates visual noise specially on deployments with many services.

Why run multiple logspout instances on a single docker instance? (logspout is supposed to be able to send all logs from a docker instance to whatever logging services the user would like)

Our environments have multiple nodes running in Docker Swarm mode. We used Logspout (and now Vector) to collect container logs from each node in each swarm. Then, each Logsput used to send the logs to a central Loki instance. However, Logspout still needed to be deployed distributed (mode: global).
In some Docker images that we use (e.g. Grafana and Loki), instead of having a forced VOLUME instruction in the Dockerfile, the images resort to a default in-memory or volatile persistence used to get you starting first. Once you are familiar with the application, you are usually instructed on how to mount the volume if you want persistence.
Thanks anyway for Logspout, it worked quite well for us in our initial approach for capturing logs from Docker!

I just found this very nice article that summarises and explains the issues with specifying VOLUME in Dockerfiles much better than I did: https://boxboat.com/2017/01/23/volumes-and-dockerfiles-dont-mix/


Launchpad Rest API Key Application

Hi there,
I'm currently working on a workflow (https://github.com/coinbase/chainstorage/pull/91) which replicate block data from another chainstorage.
Is there a way to apply for a launchpad api key (mentioned in the notion doc), so that I can test it?

Thank you for reaching out. I created an new API key for external testing purpose.
What's your email that I can share the key to?

Thank you @zhanwux
<EMAIL_ADDRESS>

@zhanwux sorry the previous one doesn't work.
<EMAIL_ADDRESS>


Feat(eos_config_deploy_cvp): Updated cv_collection version to v3 by default

Change Summary
Updated cv_collection: v3 variable to use v3 cv collection by default
Related Issue(s)
Fixes #1796
Component(s) name
arista.avd.eos_config_deploy_cvp
Proposed changes
cv_collection: v1 to
cv_collection: v3
in https://github.com/aristanetworks/ansible-avd/blob/devel/ansible_collections/arista/avd/roles/eos_config_deploy_cvp/defaults/main.yml
How to test
molecule converge --scenario-name eos_config_deploy_cvp
Also, manually tested the role.
Checklist
User Checklist

N/A

Repository Checklist

[x] My code has been rebased from devel before I start
[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation and documentation have been updated accordingly.
[x] I have updated molecule CI testing accordingly. (check the box if not applicable)

Adding what I posted on google chat here:
So I did not have time to conduct extended testing - I was questioning in my first comment if using “non fqdn” in the fqdn field would cause an issue. After some troubleshooting there is cuurently no way to tell ansible-avd to call the ansible-cvdptask(s) with a different search_key so by default we end up using host name as search_key (as per ansible-cvp code) so I don’t know the implications of the pr
From my initial it “looks to be working” except that we end up with “non valid fqdn” in the fqdn fields. For now it seems it does not have any impact (given that we will always use hostname as search key) but I think it could get some when we modify ansible-avd role to use different search_key in the case where the fqdn is different from the host name (I.e. there is a dns domain configured on the device)

Replaced with #2882 for now, since we are not ready to remove v1 support until we have feature parity.


Detect change in KeyVault references

I have an Azure Function, where we use Azure App Configuration to pull a certificate from our KeyVault. The AppConfiguration to KeyVault reference has been setup. The AppConfiguration registration looks something like this -
aadConfigBuilder.AddAzureAppConfiguration(options =>
            {
                options.Connect(Environment.GetEnvironmentVariable("AppConfiguration:ConnectionString"))
                    .ConfigureKeyVault(kv =>
                       {
                           kv.SetCredential(new DefaultAzureCredential());
                       })
                    .Select("ExternalSystemAuthentication:AadConfig:*")
                       .ConfigureRefresh(refreshOptions =>
                            refreshOptions
                            /* .Register("ExternalSystemAuthentication:AadConfig:AuthCert", refreshAll: true) */ // want to detect when this changes
                            .Register("ExternalSystemAuthentication:AadConfig:Sentinel", refreshAll: true) // this works as expected
                            .SetCacheExpiration(TimeSpan.FromMinutes(2)));
                configurationRefresher = options.GetRefresher();
            });

Everything works as expected when I use a value based 'Sentinel' key to detect a change in config. However, in my case I have auto-rotation setup on the KeyVault certificate. When a new version is available, I want the latest version to be pulled into my Function. However, since the KeyVault reference is just a URL its value does not change in the AppConfiguration, and this key cannot be used as the observable key. So I am forced to manually update the 'Sentinel' so that my function can refresh config. Is there a way App Configuration can detect a change in the KV secret value? Or is there a way I can force refresh of the App Configuration periodically without checking for a change in any key?
Thanks.

Overview
Azure App Configuration Provider supports loading secrets from Key Vault into your application configuration based on the Key Vault references stored in your App Config store. Key Vault references are a special type of key-value in AppConfig, where the value is a URI that references the secret in Key Vault.
There are times when your application could be using secrets from Key Vault that are no longer valid. Here are some situations when your application should automatically reload secrets from Key Vault:

A secret that the application is using has expired in Key Vault.
A certificate that the application is using has an auto-renewal policy which caused the certificate to auto-rotate in Key Vault.

Problem
Azure App Configuration Provider does not automatically reload secrets in any of the above scenarios. There are only two situations where we load/reload secrets from KeyVault:

Initial configuration loading during application start up.
A sentinel key-value changed in App Config and it was registered for refresh with the ConfigureRefresh method (the sentinel key-value may or may not be a Key Vault reference).

Proposed Solution
We can start caching secrets in application memory along with their expiry time (or auto-renewal time in case of certificates).
Whenever application configuration is refreshed, we use the secret value from the cache if it has not expired. If it has expired, we can reload the secret from Key Vault and update the in-memory cache with the new secret value and expiry time.
To optimize the number of times Azure App Configuration Provider loads a secret from Key Vault, the following behavioral changes will be made:

With every call to RefreshAsync, scan all the secrets present in the secret cache and reload those that have expired/rotated in Key Vault. If a secret has not expired, keep using the cached value, thereby reducing the number of requests made to Key Vault to fetch secrets.
Do not reload the secret from Key Vault if a refresh registered key-value changes in AppConfig but refreshAll is false.

Additionally, if the cached secret expires and we try to reload the secret from KeyVault, we could hit one of these condtions:

The secret/certificate was deleted from Key Vault.
Application's permission to read the secret was revoked.

In these cases, the secret will be deleted from your secret cache and your application configuration.
Application changes needed for auto-reloading certificates from Key Vault
Currently, we use a SecretClient to read both secrets and certificates from Key Vault. This approach works well for reading the value of a secret/certificate and the expiration time of a secret. However, this does not fetch the auto-renewal policy of certificates. For getting more details about when a certificate will be auto-rotated in Key Vault, we need to use a CertificateClient.
Therefore, if the Key Vault reference points to a certificate, we need an instance of CertificateClient which has the Certificates - Get permission to read certificates and their auto-renewal policy from Key Vault. Your application is responsible for providing the right credentials to read certificates from Key Vault. If these credentials are missing or do not have sufficient privileges, your certificates will not be auto-reloaded from Key Vault and no exception will be thrown.
There are two ways to provide credentials for fetching certificates from Key Vault:
1. EXISTING API: AzureAppConfigurationKeyVaultOptions SetCredential(TokenCredential credential)
If you are using this method to provide a default token credential to read secrets from Key Vault, the same credential can be used to read certificates from Key Vault too. Make sure that the credential you provide here has Certificates - Get permission in addition to Secrets - Get permission.
Usage example
var builder = new ConfigurationBuilder();
builder.AddAzureAppConfiguration(options =>
{
    options.Connect(connectionString)
           .Select("KeyVaultRef*")
           .ConfigureKeyVault(kv =>
           {
               // If you are using a default token credential for all Key Vault secrets, the same credentials will be used to read certificates too
               kv.SetCredential(new DefaultAzureCredential());
           });

2. NEW API: AzureAppConfigurationKeyVaultOptions Register(CertificateClient certificateClient)
We have introduced an overload for the existing Register method in AzureAppConfigurationKeyVaultOptions that accepts a CertificateClient instance. You can directly register all the CertificateClients that your application might need for auto-reloading certificates from Key Vault.
Usage example
var builder = new ConfigurationBuilder();
builder.AddAzureAppConfiguration(options =>
{
    options.Connect(connectionString)
           .Select("KeyVaultRef*")
           .ConfigureKeyVault(kv =>
           {
               // If you are registering a SecretClient to read Key Vault certificates, make sure to register a CertificateClient for reading their auto-renewal policy too
               kv.Register(new SecretClient(new Uri("https://abc.vault.azure.net"), new DefaultAzureCredential()));
               kv.Register(new CertificateClient(new Uri("https://abc.vault.azure.net"), new DefaultAzureCredential()));
           });

Breaking Changes
This solution introduces the following changes that may break existing applications:

Added an explicit dependency on Azure.Security.KeyVault.Certificates package version 4.1.0 .
Changing a refresh registered key-value in App Config will not reload the secret from Key Vault unless refreshAll is true or unless the refresh registered key-value is a Key Vault reference.

cc: @drago-draganov @jimmyca15 @zhenlan


Add repositories, fix category view model bugs, refactor dao module

There are changes that will be in 1.0.3 version.

Restore Podfile.lock


Add DB2 drivers to command line package

It would be good if you could add DB2 drivers to the default set of pre-packaged drivers.
https://repo1.maven.org/maven2/com/ibm/db2/jcc/<IP_ADDRESS>/
Which version and edition of Flyway are you using?
latest, community
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
command-line
Which database are you using? (Type & version)
DB2 <IP_ADDRESS>
Which operating system are you using?
N/A
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
Use the docker image which is missing drivers, see https://github.com/flyway/flyway-docker/issues/124
What did you expect to see?
DB2-drivers pre-packaged with cmdline.
What did you see instead?
missing drivers

?

Hi @davidkarlsen , many thanks for the PR. I will raise this requirement to the team.

Hi @davidkarlsen , we won't be able to do that due to the driver is under International Program License Agreement (IPLA).


About AmazonS3 Presigned URL

Hello,
I am developing my service via Spring Cloud AWS.
I have some question
How can I get the presigned URL from amazon S3?
thank you.

Autowire the AmazonS3 bean and call the generatePresignedUrl method http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/s3/AmazonS3Client.html#generatePresignedUrl-com.amazonaws.services.s3.model.GeneratePresignedUrlRequest-

Hi!
Is there any way to make this without autowiring the AmazonS3 bean?
Could it be added as a feature?
Thank you very much!


DO NOT MERGE: Adding kneaddata pipeline

Retest this please

retest this please

retest this please

retest this please

closing in favor of https://github.com/qiita-spots/qp-shotgun/pull/19


regex tool

missing from tools.tplant

regex101 is closed source but the js could be scraped. otherwise https://github.com/gskinner/regexr/, might support postgres


Create KitReo.js

its a really cool mod! i have nothing else to say.

Must follow naming scheme!
Green Tea KitKat -> green_tea_kitkat
Your recipes may not work otherwise

Must follow naming scheme!
Green Tea KitKat -> green_tea_kitkat
Your recipes may not work otherwise

i updated it and now it follows the scheme


Use modern extension import method in docs

The flask.ext module has existed since Flask 0.8, which was
released in 2011, so it should be safe to recommend this way.

Looks good, thanks!

Please don't, the flask.ext module will be deprecated in 1.0.

http://flask.pocoo.org/docs/0.10/api/#extensions still calls it "canonical" and doesn’t mention deprecation… So, what’s the right thing to do?

@untitaker interesting, I wasn't aware of that.

Deprecation will start with 1.0. I thought I'd just say it now because for app devs, there's no gain in using that indirection (flaskext isn't really used anywhere).

Reverted.

Perhaps the documentation on extensions should be changed to reflect this? I checked the development branch documentation here which still says to use flask.ext.
By the way, this explains some references I have seen recently with people saying flask.ext is deprecated even though the documentation disagrees :)

Agreed on the docs. Even if deprecation warnings are not emitted yet (why not, by the way?), if this is the intent it should be documented.

Even if deprecation warnings are not emitted yet (why not, by the way?)

I should've phrased that better: These warnings will be emitted with 1.0, the actual support will end much later.
Will see about the docs.

My point is: if you already know this is going to be deprecated, why wait to start emitting warnings?

I don't think there's going to be a 0.11 release where we could add such warnings (and adding it in a 0.10 release seems out of scope for a patch release). Not sure whether that's smart, but there's already too much breakage in master.


Add "New -> Test" menu for Test Case classes

Not sure whether it is possible to modify by custom project provider default menus, but the idea is to add to "New" menu of Test Case class new item "Test method" or something - so it will create new test method.

Sometimes template test method VI could be removed, or modified so then can not be used for different tests. But as test method is just simple static dispatch VI, it would be more "natural" way of adding test via "New" menu for the test class.
And, that generated new test method could contain some code already - either the same as template test, or "Given, When, Then" template from VITAC toolkit.

@jimkring , wouldn't you mind if it will be separate tool?
I might work on this feature, but the question is whether you have time now to build new release of VI Tester. So instead of adding this menus to VI Tester, it could be done and released as separate package which will be dependent on VI Tester, and add new menu item as described above.

@jimkring , wouldn't you mind if it will be separate tool?
I might work on this feature, but the question is whether you have time now to build new release of VI Tester. So instead of adding this menus to VI Tester, it could be done and released as separate package which will be dependent on VI Tester, and add new menu item as described above.

Hi @kosist. Let's add this to the main package. We already have a project provider. I'm happy to help with the build and release.

Hi @kosist. Let's add this to the main package. We already have a project provider. I'm happy to help with the build and release.

Thank you @jimkring, then I'll go for it, and create pull request when it will be finalized.

Thank you @jimkring, then I'll go for it, and create pull request when it will be finalized.

Sounds great!

Sounds great!

@jimkring , let me ask you please about the following. When I open "VI Tester Project Integration.lvproj", there are missing VIs from API folder. Should I place first the whole project to "C:\Program Files (x86)\National Instruments\LabVIEW 2013\resource\Framework\Providers" folder? Because seems that it searches "API" folder one level upper.

I've checked .gitignore file, and API folder is not there - so seems that "LabVIEW Project Plugin" was placed to "...\Providers" folder, wasn't it?
I could also relink all API VIs/controls which are missing to new location, but not sure whether it could cause then some issues while building package.

@jimkring , let me ask you please about the following. When I open "VI Tester Project Integration.lvproj", there are missing VIs from API folder. Should I place first the whole project to "C:\Program Files (x86)\National Instruments\LabVIEW 2013\resource\Framework\Providers" folder? Because seems that it searches "API" folder one level upper.

I've checked .gitignore file, and API folder is not there - so seems that "LabVIEW Project Plugin" was placed to "...\Providers" folder, wasn't it?
I could also relink all API VIs/controls which are missing to new location, but not sure whether it could cause then some issues while building package.

@kosist this part of LabVIEW development has historically been (and continues to be) a pain.
Starting in LV2012 (I think), the <LabVIEW>\resource folder has been a Symbolic Path, meaning if a VI calls a VI that's located underneath the <LabVIEW>\resource folder, then the caller will save the dependency VIs path relative to <resource>.  Based on that, I'm not sure why the linkages are bad, since we're working in LV2013.
I can take a look...

@kosist this part of LabVIEW development has historically been (and continues to be) a pain.
Starting in LV2012 (I think), the <LabVIEW>\resource folder has been a Symbolic Path, meaning if a VI calls a VI that's located underneath the <LabVIEW>\resource folder, then the caller will save the dependency VIs path relative to <resource>.  Based on that, I'm not sure why the linkages are bad, since we're working in LV2013.
I can take a look...

Ok, I've sort of figured it out. It's going to be a little strange, but I think we'll get it working.
For now, let's ignore the LabVIEW Project file.
First, I've committed some changes to the master branch.

Separated compiled code from the project provider
Removed some dead code inside diagram disabled structures

Second, lets do your development in a feature branch named Provider-New-Test-Menu. We can them merge into master once it's ready.
Finally, I verified that I can run the provider from source code and build it.
I've documented how you can do this, here:
https://github.com/JKISoftware/JKI-VI-Tester/wiki/VI-Tester-Development-Guide
For starters, see if you're able to load the project provider from source code. This will enable to you do development.
Thanks and let me know how it goes.

Ok, I've sort of figured it out. It's going to be a little strange, but I think we'll get it working.
For now, let's ignore the LabVIEW Project file.
First, I've committed some changes to the master branch.

Separated compiled code from the project provider
Removed some dead code inside diagram disabled structures

Second, lets do your development in a feature branch named Provider-New-Test-Menu. We can them merge into master once it's ready.
Finally, I verified that I can run the provider from source code and build it.
I've documented how you can do this, here:
https://github.com/JKISoftware/JKI-VI-Tester/wiki/VI-Tester-Development-Guide
For starters, see if you're able to load the project provider from source code. This will enable to you do development.
Thanks and let me know how it goes.

Thanks a lot!
Now dependencies are correct - I've placed also VIs and ini file to Providers... folder, and Project Provider was loaded properly.
Just, I didn't see items in Tools menu - so going to check why it is not there... Things are not so easy than it seemed before )))

Thanks a lot!
Now dependencies are correct - I've placed also VIs and ini file to Providers... folder, and Project Provider was loaded properly.
Just, I didn't see items in Tools menu - so going to check why it is not there... Things are not so easy than it seemed before )))

That's great that it seems to be working.
As for the Tools menu, one thought that I have is that maybe you didn't first install the built VI Tester package (e.g. the latest in VIPM) into LabVIEW 2013 -- this as in the instructions for development of the project provider state, as an early/first step.
Doing this step should put the tools menu items in the right spot.  Then, in a subsequent step, you delete the installed project provider and put your provider source code in its place.
Hope that helps. Yes, it's not so easy :)

That's great that it seems to be working.
As for the Tools menu, one thought that I have is that maybe you didn't first install the built VI Tester package (e.g. the latest in VIPM) into LabVIEW 2013 -- this as in the instructions for development of the project provider state, as an early/first step.
Doing this step should put the tools menu items in the right spot.  Then, in a subsequent step, you delete the installed project provider and put your provider source code in its place.
Hope that helps. Yes, it's not so easy :)

Sorry, my fault - I wasn't aware about developer's guide... Now I see ))
Thanks a lot!
Btw, there is issue with installing of latest VI Tester package via VIPM (v<IP_ADDRESS>4-1), I'll post issue about it... Previous build (v<IP_ADDRESS>2-1) works fine.

Sorry, my fault - I wasn't aware about developer's guide... Now I see ))
Thanks a lot!
Btw, there is issue with installing of latest VI Tester package via VIPM (v<IP_ADDRESS>4-1), I'll post issue about it... Previous build (v<IP_ADDRESS>2-1) works fine.

No problem. Yes, the Developer's Guide is quite long and very detailed, since there are lots of ways to get things to not work properly :))
Glad you're you're figuring it out.
Regarding the installation issues with the latest package, yes, please let me know about any issues and probably we can fix that, in this next next release 👍

No problem. Yes, the Developer's Guide is quite long and very detailed, since there are lots of ways to get things to not work properly :))
Glad you're you're figuring it out.
Regarding the installation issues with the latest package, yes, please let me know about any issues and probably we can fix that, in this next next release 👍


Exception occurres when use FindOperator.

To use 'where in' clause, I execute next code. But TypeError is thrown.
Are there any way to avoid this?
import { In } from "typeorm"

const repo = getRepository<XXX>()

await repo.find({
  where: {
    encryptedField: In(["aaa"])
  }
})

Error
TypeError [ERR_INVALID_ARG_TYPE]: The first argument must be of type string or an instance of Buffer, ArrayBuffer, or Array or an Array-like Object. Received an instance of FindOperator

      at EncryptionTransformer.Object.<anonymous>.EncryptionTransformer.to (node_modules/typeorm-encrypted/src/transformer.ts:28:4)
      at Function.Object.<anonymous>.ApplyValueTransformers.transformTo (src/util/ApplyValueTransformers.ts:19:28)
      at ColumnMetadata.Object.<anonymous>.ColumnMetadata.getEntityValue (src/metadata/ColumnMetadata.ts:658:44)
      at SelectQueryBuilder.<anonymous> (src/query-builder/QueryBuilder.ts:1088:51)
      at step (node_modules/typeorm/node_modules/tslib/tslib.js:143:27)
      at Object.next (node_modules/typeorm/node_modules/tslib/tslib.js:124:57)
      at SelectQueryBuilder.Object.<anonymous>.QueryBuilder.getWhereCondition (src/query-builder/QueryBuilder.ts:1208:80)
      at SelectQueryBuilder.Object.<anonymous>.SelectQueryBuilder.where (src/query-builder/SelectQueryBuilder.ts:721:32)

IIRC the encryptedField can't be used in a complex query (including where clauses). The predicate is pushed down to the database. The field is encrypted in the database and will not be decrypted when evaluating the where clause.
You may want to use full database encryption.

https://github.com/generalpiston/typeorm-encrypted#why-wont-complex-queries-work

Thanks @takezoux2

Released in 0.6.0.


S2 tinyusb examples (IDFGH-3295)

Hi.
I know S2 API is still in beta stage, or alpha, but would it be possible to have tinyusb example for MSC and CDC at least, please? I saw it is working, but i couldnt adapt tinyusb example to show esp32s2 as disk drive.
https://github.com/hathach/tinyusb/blob/develop/examples/device/cdc_msc_freertos/src/main.c
Thanks

Found it, fixed it and prepared PR.


hset only accepts 1 single field/value pair while HSET command has allowed for multiple field/value pair since 4.0.0 (variadic)

client.hset('hashKey', 'key1', 'OK' 'key2', '123') should set key1 and key2 to value but only sets key1.
As per the HSET documentation, it has been variadic since 4.0.0, which is released in 2017. Any plans to update this?

 Feel free to fork and improve!

Okay sure, thanks!


🎈V0.1.3 Release Plan

[x] use a more engineering-oriented error code wrapper.
[x] update tangseng pages docs
[x] add Prometheus as project's monitor
[x] add Jaeger to provide project with the capability of distributed tracing

If u want to contribute this project, don't be shy and share your ideas.😘

done!


FSRS-5 test

I'm currently writing tests for the py-fsrs update for fsrs-5 and was wondering where you got these intervals from.
https://github.com/open-spaced-repetition/ts-fsrs/blob/65fd676414e23e21612b5344af947480f7dafa7e/__tests__/FSRSV5.test.ts#L59-L61
I was looking through the fsrs-optimizer repo and am guessing you got the weights for this test from there?
https://github.com/open-spaced-repetition/fsrs-optimizer/blob/ef723f82da08c3e8bf2890c557f5a4e4bd4dc936/src/fsrs_optimizer/fsrs_simulator.py#L574-L594
Did you use the fsrs-optimizer to compute those intervals? If that's where you computed the intervals, how should I replicate it? The documentation for the fsrs-optimizer is still quite sparse.

I was looking through the fsrs-optimizer repo and am guessing you got the weights for this test from there?

The weights for TS-FSRS are derived from the DEFAULT_PARAMETERS in fsrs-rs, as shown here: https://github.com/open-spaced-repetition/fsrs-rs/blob/ea80c61ac0cfc6847a19d0ea3d63eaae4947e87c/src/inference.rs#L24-L27.
The weights in the FSRS v5 test set for TS-FSRS do not change with the default parameters. Additionally, every method implementation in TS-FSRS is consistent with FSRS-RS in unit tests, though there may be minor differences in decimal tail numbers. You can see the tests here:

https://github.com/open-spaced-repetition/ts-fsrs/blob/v4.1.2/tests/algorithm.test.ts.
https://github.com/open-spaced-repetition/ts-fsrs/blob/65fd676414e23e21612b5344af947480f7dafa7e/__tests__/algorithm.test.ts#L270-L280
https://github.com/open-spaced-repetition/fsrs-rs/blob/v1.1.4/src/inference.rs
https://github.com/open-spaced-repetition/fsrs-rs/blob/ea80c61ac0cfc6847a19d0ea3d63eaae4947e87c/src/inference.rs#L472-L478

Currently, TS-FSRS has two scheduling modes (short-term and long-term Scheduler), so the ivl_history used in testing is calculated from internal outputs.

Thanks for the response!
A couple things

The weights in the FSRS v5 test set for TS-FSRS do not change with the default parameters.

The weights for this FSRS-5 test: https://github.com/open-spaced-repetition/ts-fsrs/blob/65fd676414e23e21612b5344af947480f7dafa7e/tests/FSRSV5.test.ts#L12-L16
are different from the default ts-fsrs weights: https://github.com/open-spaced-repetition/ts-fsrs/blob/65fd676414e23e21612b5344af947480f7dafa7e/src/fsrs/default.ts#L6-L10
So I'm not really sure what you mean here?

the ivl_history used in testing is calculated from internal outputs.

Do you mean that the ivl_history in https://github.com/open-spaced-repetition/ts-fsrs/blob/65fd676414e23e21612b5344af947480f7dafa7e/tests/FSRSV5.test.ts#L59-L61
was originally calculated by ts-fsrs and not somewhere else? I was wondering if the intervals were originally taken from somewhere else as a 'ground truth' to test again. Is this the case?

are different from the default ts-fsrs weights:

I'm sorry I updated the weights in the last patch and forgot to remind @ishiko732.

I was wondering if the intervals were originally taken from somewhere else as a 'ground truth' to test against.

ts-fsrs is ground truth unless we integrate the scheduler part into fsrs-rs, but it requires a huge work: https://github.com/open-spaced-repetition/fsrs-rs/issues/210

My questions have been answered! 谢谢 to you both


[DR] Result paging strategy for related entities query

Description
Closes #188. Add decision record considering options for result paging, in particular for the related entities query.

Hi @feltech... if I'm understanding correctly, a manager can internally figure out how it wants to break up network requests such that its back-end will not be overwhelmed. Then it calls the success callback when it's sure it has acquired all the data for a particular EntityReference. Is that right? If so, then is pagination more for a host/UI to communicate the limits of what it wants to handle?

Hi @feltech... if I'm understanding correctly, a manager can internally figure out how it wants to break up network requests such that its back-end will not be overwhelmed. Then it calls the success callback when it's sure it has acquired all the data for a particular EntityReference. Is that right? If so, then is pagination more for a host/UI to communicate the limits of what it wants to handle?

Thanks for the question, I'll try to break it down since I'm not 100% sure I understand:

a manager can internally figure out how it wants to break up network requests such that its back-end will not be overwhelmed

Yeah, a manager plugin can do what it wants, as long as the host application can retrieve slices/pages of data lazily, through whatever mechanism we decide on, in chunks of the requested size.
Obviously it's in the manager's interest to optimise around the fact that data is being lazily requested, page by page.  But a naive implementation may well fetch all the data up-front, cache it, then regurgitate page by page as requested (in fact we have discussed this as a possible default behaviour, to be overridden by plugins that support more intelligent paging).

it calls the success callback when it's sure it has acquired all the data for a particular EntityReference

The manager should call the success callback when it has acquired the requested page of data for a particular EntityReference (assuming we're talking about Option 1).

is pagination more for a host/UI to communicate the limits of what it wants to handle?

Yes indeed, as mentioned it's the host that selfishly wants paged data, regardless of how that's implemented by the manager plugin.
Having said that, host applications will have some concern for back-end performance too - that's the whole point of batching requests, after all.

Ok perfect thanks, I think we're aligned:

Code on the host side declares the data that it wants, which includes paginated subsets of the data
Code on the manager side determines the (hopefully optimal) execution plan for acquiring that data. Or as you suggested, it may well over-fetch data that the host hasn't asked yet.

I'll give some more thought to the options with that mental model in mind...


Changing font color throughout the website.

Hi, I want to change the font color throughout the website to make it effective and eye-catching. Kindly, assign this work to me under GSSOC'24.

With my skills adn deep knowledge related to proper designing and colour combinations, I can work on this issue more effectively.
Please assign this issue to me under GSSoC '24.
Thank you!

please assign me this issue under GSSoC'24

hey @sonarani1 kindly work upon it

hello I want to work on it can you assign it to me @sonarani1

hello, I am a gssoc 2024 contributer, could you please assign this task to me, please add the gssoc 2024 label

Hey, I would like to work on the same. Can you please assign this to me under GSSoC'24.

Can you please assign me this issue , I want to work on this

Issue solved.


missing comma after authoringKey entry

"authoringKey": "<your authoring key>" -> "authoringKey": "<your authoring key>",

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

ID: 7fb99c59-443b-e949-63f7-10dc3621046d
Version Independent ID: c58faee3-d99b-d101-ca0f-9a0ee36a0ac4
Content: Create a bot using Bot Builder SDK for JavaScript - Bot Service
Content Source: articles/v4sdk/bot-builder-service-file.md
Product: bot-framework
GitHub Login: @JonathanFingold
Microsoft Alias: jonathanfingold

Thanks! Fixed, should be published shortly


Flatbuffers version needs a bump up

https://github.com/Microsoft/vcpkg/blob/273b8ce3d0d3533f3b959a7ecf4b0aa1eef22cab/ports/flatbuffers/CONTROL#L2
Current version as reported by flatc appears to be 1.10.0 which has some significant differences (like default values for enums and several compilation breaks on dependent libraries)

Thanks for posting this issue. Flatbuffers has upgrade to 1.11.0, you can update vcpkg and rebuild.


template_merge > Dev

Many thanks to contributing to nf-core/nanodemux!
Please fill in the appropriate checklist below (delete whatever is not relevant). These are the most common things requested on pull requests (PRs).
PR checklist

[ ] This comment contains a description of changes (with reason)
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If necessary, also make a PR on the nf-core/nanodemux branch on the nf-core/test-datasets repo
[ ] Ensure the test suite passes (nextflow run . -profile test,docker).
[ ] Make sure your code lints (nf-core lint .).
[ ] Documentation in docs is updated
[ ] CHANGELOG.md is updated
[ ] README.md is updated

Learn more about contributing: https://github.com/nf-core/nanodemux/tree/master/.github/CONTRIBUTING.md

Travis tests are going to fail because we still dont have an appropriate test dataset yet.


Builder to customize and disable idle animations

Appended an Option to Reedline struct that allows library users to customize the time waited between repaints.  It is interpreted as milliseconds, and if it is 'None', then no repainting occurs.  Added corresponding builder function.
Ideally, it would be friendlier if we could disable repainting dynamically, especially, when the prompt is not visible, or on 'MouseEventKind::ScrollUp'.  Unfortunately, my terminal (xfce4) would not report mouse events, so I couldn't get that to work.

I like it! Nice.
Can you run cargo fmt on it? That and the tests (and maybe also cargo clippy) are going to get checked by the CI.

Looks good!

Thanks!  Just wanted to say thanks for your Reedline livestreams- I've
learned a ton from them.
On Fri, Nov 5, 2021 at 1:17 PM JT @.***> wrote:

Merged #168 https://github.com/nushell/reedline/pull/168 into main.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/nushell/reedline/pull/168#event-5576037391, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALYHOLLJ4JLFQQZZS654VWDUKQNUNANCNFSM5HKJXT6A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Error: Cannot find module

Hi @EcomGraduates

installed via npm i loom-dl

added 32 packages in 3s

3 packages are looking for funding
  run `npm fund` for details

then this command to download node loom-dl https://www.loom.com/share/00f316f743954f92b1e2ccf8fc741e3e

node:internal/modules/cjs/loader:1222
  throw err;
  ^

Error: Cannot find module '/Users/macbookpro/loom-dl'
    at Module._resolveFilename (node:internal/modules/cjs/loader:1219:15)
    at Module._load (node:internal/modules/cjs/loader:1045:27)
    at TracingChannel.traceSync (node:diagnostics_channel:315:14)
    at wrapModuleLoad (node:internal/modules/cjs/loader:215:24)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:158:5)
    at node:internal/main/run_main_module:30:49 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

Node.js v22.5.1

any ideas?
PS.
macOS 14.5
Node.js v22.5.1

Try installing globally looks like you installed into a project

Nope it was installed globally /Users/macbookpro/node_modules/loom-dl
But for some reason, the command skips the main folder which is node_modules

run this command
loom-dl -u  https://www.loom.com/share/00f316f743954f92b1e2ccf8fc741e3e

ah the whole point is to add this flag to make it work :) I apologize, my bad.

not a problem at all! just updated the readme as the instructions were not very clear :)


MM-20447: Migrate 'components/integrations/add_command' module and associated tests to TypeScript

Summary
This PR migrates 'components/integrations/add_command' module (also convert it to FC) and associated tests to TypeScript
Ticket Link
Fixes https://github.com/mattermost/mattermost-server/issues/16127
JIRA: https://mattermost.atlassian.net/browse/MM-20447
Release Note
NONE

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

/e2e-test

Successfully triggered e2e testing!
https://git.internal.mattermost.com/qa/cypress-ui-automation/-/pipelines/218803


Files specified in dependencies get copied twice

For instance when I create  a dependency
destination:
./build
dependencies:

./css

the expected output should be
/build/css/
This works fine for the first time. However if you run 'hologram' a second time it will copy the dependency files to
/build/css/css
I am using hologram 1.3, ruby 2.1.2p95 on Mac Os X 10.9.2

I'm getting the same issue, when I first generate the files it is fine. The files are generated to docs/css, but the second time I generate they go to docs/css/css and I've no idea why. It is getting irritating having to delete the directory every time as I can't use grunt clean on this project.
Relevent config
# The directory containing the source files to parse recursively
source: ../scss

# The directory that hologram will build to
destination: ./docs

dependencies:
  - ../css
  - ../scss
  - ../fonts
  - ../img
  - ../js

Same here.

Yep, exactly the same issue, using gulp-hologram

This should be fixed in 1.3.1 which is now available.


Name importers according to reverse DNS of service

Please consider naming importers in knut according to the reverse DNS name of the "main" domain they communicate with, or the service that they interoperate with. That is, "com.revolut" instead of "revolut" and "com.interactivebrokers" instead of "us.interactivebrokers". There'll probably be many entries for "com", but it'd be a little more predictable.

Good idea, why not!


Create AzureSQLServerVectorStore class & implement add_text function

In this PR, we create AzureSQLServer_VectorStore class which serves as the point of initialization for the vector store.
During class initialization, we create the vector store table which will be used during the lifetime of the AzureSQLServer_VectorStore object.
Implemented functions in the PR

init: Class initialization function. Sets all the class members and performs table creation.
_create_table_if_not_exists: Makes a connection to the DB and creates a table if the table name does not exist in the DB.
_get_embedding_store: Helper function that creates the table base model (EmbeddingStore) used during table creation and returns an EmbeddingStore object.
add_texts: Function that takes texts to be stored and runs it through an embedding model.
_insert_embeddings: This helper function parses texts, metadatas, ids and embeddings (in varbinary) format and inserts this into the vectorstore table. We've employed the use of parameterized queries here to avoid SQL injections.

Here is a sample usage and output of the add_texts function
azvs = AzureSQLServer_VectorStore(
        connection_string=_CONNECTION_STRING,
        embedding_function=CohereEmbeddings(cohere_api_key=_COHERE_API_KEY, model="embed-english-light-v3.0"),
        table_name="langchain_vector_store_test"
    )

azvs.add_texts(
    texts=["chair", "book", "school", "potato"],
    metadatas=[
        {"id":1, "material":"wood"},
        {"id":2, "material":"paper"},
        {"id":3, "material":"numerous"},
        {"id":4, "material":"plant"}])

Result - content of langchain_vector_store_test table

Other methods in this PR that haven't been implemented are abstract methods that we need to implement.
Tests

Unit test for function add_text asserts that when add_text is called, the function returns the same number of IDs as the number of input texts.

The following rules have been run on the files as stipulated by the contribution guide.

make format
make lint

Note that in later development, connection authentication will be implemented.

I believe the results seen in the PR description shows contents of the langchain_vector_store_test after invoking the add_texts call Is that right? Its not clear from the description..

I believe the results seen in the PR description shows contents of the langchain_vector_store_test after invoking the add_texts call Is that right? Its not clear from the description..

This has now been updated, thanks.

I had a few questions which you have clarified, now this looks good to me. Really good work!


Question: Is Privileges 2 Beta available for evaluation?

Hiya, I came across this nice solution while looking at things we may have to change for incoming EU DORA legislation.
Is it possible to test and evaluate v2 Beta outside of your org at the moment?

Please see here


MultiThreadedEventLoopGroup: allow users to specify the thread name pattern

Right now, MTELG's thread name pattern is always NIO-ELT-x-#y. The NIO-ELT- part should be configurable by the user. And NIOSingletons's ELG's (once https://github.com/apple/swift-nio/pull/2471 is in) should set that to something useful.

So the whole code infrastructure for this is already implemented in #2471: https://github.com/apple/swift-nio/pull/2471/files#diff-4b1291d44c519e5e77e9d2d3f165562ca65b739df1286327c5a0b0e1b5e98ff1R199
It's the API design that is the challenging part?
I'm happy to poke you (and @glbrntt) with a pull request with a draft — that tends to spawn pretty fun discussions, it seems 🙃 (At least fun for me)

And NIOSingletons's ELG's (once https://github.com/apple/swift-nio/pull/2471 is in) should set that to something useful.

As in, automatically default to something other than "NIO-ELT-"? Hmmm. Any chance we could grab the current swift module name the code is compiled in when NIOSingletons is invoked? I mean, we could slice the path of #file 👀, right? Then we could do something like NIO-MODULE-%idx%.

I do not believe it is possible to get the module name of the invoking module.

I do not believe it is possible to get the module name of the invoking module.

#fileID is guaranteed to be <module name>/<file base name>.swift so it is possible but requires parsing.


Remove symbolsource no longer relevant

Fixes: https://github.com/NuGet/Client.Engineering/issues/1692
Removing references to symbolsource, follow up on https://github.com/NuGet/docs.microsoft.com-nuget/pull/2855.

Learn Build status updates of commit 1975b94:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/reference/cli-reference/cli-ref-push.md
:white_check_mark:Succeeded
View

docs/release-notes/NuGet-1.3.md
:white_check_mark:Succeeded
View

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 learn.microsoft.com contributor guidesPost your question in the Learn support channel


Remember already typed operator values and allow autocomplete

Ideally: operator values in downloaded data would be also available as autocomplete and there would be way to remove mistyped one without reinstalling app.

Wow, I never thought you need autocomplete for operators. To me it's like autocomplete for names. Technically possible, but I struggle to find even a single case when I needed it.

To me it's like autocomplete for names.

Also useful when editing streams/rivers/roads.


Issues with login into a Cloud Key Gen2 plus

I tried to use pyunifi against a Cloud Key Gen2 plus, and I found a login issue to it.
I tried to use version="unifiOS" and then I got this error back:
raise APIError("Login failed - status code: %i" % r.status_code)
APIError: Login failed - status code: 401
I used F12 to login to the cloud key, and checked which URI it posted the login call to.
It is supposted to be towards: https://IP/api/auth/login.
In the script, the self.url is:
self.url = 'https://' + host + '/proxy/network/'
and the login function is using self.url like this:
login_url = self.url + 'api/login'
Which means it gets /proxy/network/ before api/login.
So I changed the init from:
if version == "unifiOS":
self.host = host
self.username = username
self.password = password
self.site_id = site_id
self.ssl_verify = ssl_verify
self.url = 'https://' + host + '/proxy/network/'
to:
if version == "unifiOS":
self.host = host
self.username = username
self.password = password
self.site_id = site_id
self.ssl_verify = ssl_verify
self.url = 'https://' + host + '/proxy/network/'
self.urllogin= 'https://' + host + '/'
self.version=version
And the login function I changed from this:
def _login(self):
log.debug('login() as %s', self.username)
    # XXX Why doesn't passing in the dict work?
    params = {'username': self.username, 'password': self.password}
    login_url = self.url + 'api/login'

To:
def _login(self):
log.debug('login() as %s', self.username)
    # XXX Why doesn't passing in the dict work?
    params = {'username': self.username, 'password': self.password}
    if self.version=="v5":
        login_url = self.url + 'api/login'
    elif self.version=="unifiOS":
        login_url = self.urllogin + 'api/auth/login'

And then I could login to the Cloud key and pull everything I needed.
Just wanted to inform you about this issue, awesome job with the library!

@finish06 , this is not fixed in the development branch and UDMP-unifiOS version?
When, did you plan to make a new release? This is also seems to block https://github.com/custom-components/sensor.unifigateway/issues/17 / https://github.com/custom-components/sensor.unifigateway/issues/35 and probably more.

FYI: v2.21 has been uploaded to PyPi and is reported to have fixed these issues.  Let me know what you find.  Thanks.

@mgottholsen - I do not have a CloudKey.  Can you confirm the URL that is being accessed when logging into the CloudKey?

Just wanted to say that I can use pyunifi (2.21 version) with my CK+ when I set version to UDMP-unifiOS.


feat: Initial Algorand Structure

This PR aims to deliver an initial structure of the Algorand integration within the Icon Bridge.
In the algo folder there is the implementation of the Relayer and on the Pyteal one the implementation of the smart contracts.
This is meant to be first of a set of PR iterations, to show Icon our current progress so that they can provide any feedback they see fit and suggest any changes.
However this code was not fully tested yet, despite of having been built without any errors.
There is currently a unit test for the receiver module but not for the sender one yet.
There are already initial iterations for the BMC and BSH algorand contracts, with a small set of functionalities and test cases supporting them.

This PR is failing some tests. Please run git remote update --prune  and try again.

Could you please create a new branch for your implementation,  we can't merge this changes directly to the main branch.

which I believe only requires running git remote update --prune

@CyrusVorwald  I already ran this command on my local branch and it fetched the upstream, getting some updates. Also added a git push which returned an Everything up-to-date.
Nothing seemed to have changed on this PR. Should I go ahead and create a new branch on this repo and merge there?

which I believe only requires running git remote update --prune

@CyrusVorwald  I already ran this command on my local branch and it fetched the upstream, getting some updates. Also added a git push which returned an Everything up-to-date.
Nothing seemed to have changed on this PR. Should I go ahead and create a new branch on this repo and merge there?

Strange. Yeah  that's fine

The "Build icon-bridge BMR" CI check failure does not seem to be a Github runner associated issue and should be fixed. It fails with
--- FAIL: Test_GetLatestBlock (0.00s)
client_test.go:25: Error getting latest round: Get "/v2/status": unsupported protocol scheme ""
--- FAIL: Test_Subscribe (0.00s)
receiver_test.go:46: Couldn't retrieve latest round
Please take a look. If it's nontrivial to fix and only CI related, continuing to use an independent branch is fine.
The other failures are fine.


Models with commercial license

Can you release model weights that can be used for commercial purposes?

Interested in this one too, please.

Interested in this one too, please.


Prep for v1.0 release

Codecov Report

Merging #37 (f677905) into master (0d8f635) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #37   +/-   ##
=======================================
  Coverage   92.30%   92.30%
=======================================
  Files           1        1
  Lines         104      104
=======================================
  Hits           96       96
  Misses          8        8

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 0d8f635...f677905. Read the comment docs.


Raphael 2.0?

Has this library been updated to use Raphael 2.0? Or, does it require the older version? I haven't tested it with the new version of Raphael, but wanted to ask if you were aware of any problems. Thanks.

I can't remember if I updated/tested it, I'll add this to my to-do list

I just tested docs/examples.html and it seems to work fine with Raphael 2.0.  I think remember the Raphael author saying 2.0 wasn't going to introduce major API changes.

Fantastic. Thanks. I'll post another update to my blog post that consistently gets at least thirty visits a day -- it's about g.line.js from gRaphael, but I link to you as a better option for line charts. ;-)
Sent from my iPhone
On Nov 9, 2011, at 3:55, Alex<EMAIL_ADDRESS>wrote:

I just tested docs/examples.html and it seems to work fine with Raphael 2.0.  I think remember the Raphael author saying 2.0 wasn't going to introduce major API changes.

Reply to this email directly or view it on GitHub:
https://github.com/alexyoung/ico/issues/9#issuecomment-2680400


[IO] Allow overriding arrow schema in the to_arrow method on DataFrame

Is your feature request related to a problem? Please describe.
We typically override the arrow schema (cast to appropriate types) when calling read_table. However, daft's parquet reader does not allow overriding arrow schema which it will infer based on parquet metadata automatically. We have a workaround right now to use table.cast but casting can be expensive (if arrow ends up using additional memory). Moreover, this is not a hard blocker.
Describe the solution you'd like
Would it make sense to pass in schema to the to_arrow method as described below:
df.to_arrow(schema=arrow_schema)

or

df.read_parquet(arrow_schema=arrow_schema)

Describe alternatives you've considered

table.cast: we will employ this workaround until daft supports it natively.

This is addressed in 0.1.16.


TestPipelineExceedMaximumServing

--- FAIL: TestPipelineExceedMaximumServing (0.01s)
	pipeline_test.go:100: failed to send out message

https://travis-ci.org/coreos/etcd/jobs/155682812#L3382

I've run over 15,000 rounds with no failure. Pretty sure this is just CI being slow, so not able to receive from channel within 10ms. If it happens again, I will reopen this.

2016-12-29 19:48:02.842951 I | rafthttp: started HTTP pipelining with peer 1
2016-12-29 19:48:02.843639 I | rafthttp: peer 1 became active
2016-12-29 19:48:02.860835 I | rafthttp: stopped HTTP pipelining with peer 1
2016-12-29 19:48:02.862097 I | rafthttp: started HTTP pipelining with peer 1
2016-12-29 19:48:02.904865 I | rafthttp: stopped HTTP pipelining with peer 1
2016-12-29 19:48:02.906194 I | rafthttp: started HTTP pipelining with peer 1
2016-12-29 19:48:02.930548 I | rafthttp: peer 1 became active
2016-12-29 19:48:02.947504 I | rafthttp: stopped HTTP pipelining with peer 1
--- FAIL: TestPipelineExceedMaximumServing (0.04s)
	pipeline_test.go:82: failed to send out message
	pipeline_test.go:89: unexpected message sendout

https://travis-ci.org/coreos/etcd/jobs/187536186#L1759

@xiang90 @heyitsanthony
Should we just make https://github.com/coreos/etcd/blob/master/rafthttp/pipeline_test.go#L81
for i := 0; i < connPerPipeline+pipelineBufSize; i++ {
	select {
	case p.msgc <- raftpb.Message{}:
	case <-time.After(10 * time.Millisecond):
		t.Errorf("failed to send out message")
	}
}

to
for i := 0; i < connPerPipeline+pipelineBufSize; i++ {
	p.msgc <- raftpb.Message{}
}

like https://github.com/coreos/etcd/blob/master/rafthttp/pipeline_test.go#L219-L222
As we explained in https://github.com/coreos/etcd/commit/0d35ba9b94369c72e46ed7b57b2bb3427faf66a8
after pipelineBufSize gets filled up, it might block in slow CPU systems
I ran over 10K rounds on this test, and can't reproduce...

probably should bump the timeout to 1s like the fix from #6398