A JavaScript library built to encourage a functional programming style & strategy. - http://eliperelman.com/fn.js
AmplifyJS
App Sandbox creates a sandbox for JavaScript modules to execute without harm to the module itself or its execution environment.
Backbone.js integrated with AMD modules as well as the mediator & facade patterns
AngularJS - HTML enhanced for web apps!
Parse ANSI color codes
A simple javascript module build utility
JSHint plugin for anvil
issue openednwtgck/actions-netlify
Case sensitivity in branch deploys
Wanted to drop a note that I ran into an issue with branch deploys that contain uppercased letters. For example, if I set an alias as alias: ISSUE-000, the deployment shows as successful as https://issue-000--my-app.netlify.app, but opening the URL returns a 404. If I lowercase the value first, then the deployment is actually successful. May be worth putting a note in the docs for this caveat.
created time in 4 days
pull request commentpublicsuffix/list
@dnsguru :wave: just wanted to give this a friendly bump.
comment created time in 5 days
issue closedcssinjs/jss
Nonces added for CSP support are still policy-blocked
Expected behavior:
Configuring CSP and csp-nonce meta tag to use nonces with JSS should render without the need for unsafe-inline.
Describe the bug:
I am using material-ui, and transitively JSS, to inject styles. When released to production, the CSP directive is blocking the loading of the styles, even though it appears that the nonces configured for CSP and JSS match.

Taking a look at the meta tags present in the HTML response:

So the CSP meta tag defines the style nonce as nonce-gq/sneT99hwrwvvbNkbMWg==, which matches the exact value set by the csp-nonce tag. Next, let's take a look at the style tags injected into the page:

🤔 It appears that all the style tags also have the same nonce set correctly.
Codesandbox link:
May try to create something to replicate this, but CSP is hard to make this happen.
Versions:
- jss: 10.3.0 (via material-ui)
- Browser [e.g. chrome, safari]: Chrome 84
- OS [e.g. Windows, macOS]: macOS Catalina
closed time in 11 days
eliperelmanissue commentcssinjs/jss
Nonces added for CSP support are still policy-blocked
Closing as resolved. Turns out that the nonce attribute needed for JSS should not actually include the nonce- portion of the nonce.
comment created time in 11 days
issue openedcssinjs/jss
Nonces added for CSP support are still policy-blocked
Expected behavior:
Configuring CSP and csp-nonce meta tag to use nonces with JSS should render without the need for unsafe-inline.
Describe the bug:
I am using material-ui, and transitively JSS, to inject styles. When released to production, the CSP directive is blocking the loading of the styles, even though it appears that the nonces configured for CSP and JSS match.

Taking a look at the meta tags present in the HTML response:

So the CSP meta tag defines the style nonce as nonce-gq/sneT99hwrwvvbNkbMWg==, which matches the exact value set by the csp-nonce tag. Next, let's take a look at the style tags injected into the page:

🤔 It appears that all the style tags also have the same nonce set correctly.
Codesandbox link:
May try to create something to replicate this, but CSP is hard to make this happen.
Versions:
- jss: 10.3.0 (via material-ui)
- Browser [e.g. chrome, safari]: Chrome 84
- OS [e.g. Windows, macOS]: macOS Catalina
created time in 11 days
push eventeliperelman/list
commit sha 758c8951fb05fe68180b020f5101867151609ab3
Add 12 sub zones to .br [20200714 update] (#1068) * .br updated - one new city domain barueri.br * .br updated - New ong.br launch date 20180927 * .br update - 12 new sld lauch date 20200720 app.br bib.br coz.br des.br det.br dev.br enf.br geo.br log.br rep.br seg.br tec.br Co-authored-by: Frederico A C Neves <[email protected]>
commit sha 35ee65e34adddd846661d35bf35c2c3ad0b83c15
gTLD autopull: 2020-07-18 (#1069) Co-authored-by: tld-update-bot <[email protected]>
commit sha fa95bbf06f98677ce3cb7e9b697d349d41a14962
Add algorithmia.com
push time in 14 days
push eventeliperelman/list
commit sha b0b1e0883e5b484e1b2273788ddbcc2c320b2475
Add algorithmia.com
push time in 14 days
push eventeliperelman/list
commit sha b650287c2bdeebee166ddc4990ebb259e4a31ff8
Add algorithmia.com
push time in 14 days
push eventeliperelman/list
commit sha 89a59110cb44efe52bd246563641ca024013067e
Add algorithmia.com
push time in 14 days
PR opened publicsuffix/list
<!-- #### READ THIS FIRST ####
If you haven't yet, please read our guidelines: https://github.com/publicsuffix/list/wiki/Guidelines#submit-the-change
If you'd like an example of what an excellent PR looks like see https://github.com/publicsuffix/list/pull/615 -->
- [x] Description of Organization
- [x] Reason for PSL Inclusion
- [ ] DNS verification via dig
- [x] Run Syntax Checker (make test)
<!--
As you complete each item in the checklist please mark it with an X
Example:
- [x] Description of Organization
-->
Description of Organization
Organization Website: https://algorithmia.com
Algorithmia provides the fastest time to value for enterprise machine learning. Rapidly deploy, serve, and manage machine learning models at scale. This PR is submitted by myself, Eli Perelman, representing Algorithmia as lead web engineer.
Reason for PSL Inclusion
We currently have a cookie set for algorithmia.com, but would like to share that with teams.algorithmia.com without sharing with our other subdomains that should not have access.
DNS Verification via dig
<!-- For each domain you'd like to add to the list please create a DNS verification record pointing to your pull request.
For example, if you'd like to add example.com and example.net you would need to provide the following verifications:
dig +short TXT _psl.example.com
"https://github.com/publicsuffix/list/pull/XXXX"
dig +short TXT _psl.example.net
"https://github.com/publicsuffix/list/pull/XXXX"
Note that XXXX is replaced with the number of your pull request. -->
make test
<details> <summary>results of <code>make test</code></summary>
➜ make test
cd linter; \
./pslint_selftest.sh; \
./pslint.py ../public_suffix_list.dat;
-n test_NFKC:
OK
-n test_allowedchars:
OK
-n test_dots:
OK
-n test_duplicate:
OK
-n test_exception:
OK
-n test_punycode:
OK
-n test_section1:
OK
-n test_section2:
OK
-n test_section3:
OK
-n test_section4:
OK
-n test_spaces:
OK
-n test_wildcard:
OK
test -d libpsl || git clone --depth=1 https://github.com/rockdaboot/libpsl; \
cd libpsl; \
git pull; \
echo "EXTRA_DIST =" > gtk-doc.make; \
echo "CLEANFILES =" >> gtk-doc.make; \
autoreconf --install --force --symlink;
Already up to date.
glibtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, 'build-aux'.
glibtoolize: linking file 'build-aux/ltmain.sh'
glibtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
glibtoolize: linking file 'm4/libtool.m4'
glibtoolize: linking file 'm4/ltoptions.m4'
glibtoolize: linking file 'm4/ltsugar.m4'
glibtoolize: linking file 'm4/ltversion.m4'
glibtoolize: linking file 'm4/lt~obsolete.m4'
configure.ac:36: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and its use is discouraged.
configure.ac:36: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro instead,
configure.ac:36: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am files.
configure.ac:11: installing 'build-aux/compile'
configure.ac:5: installing 'build-aux/missing'
fuzz/Makefile.am: installing 'build-aux/depcomp'
cd libpsl && ./configure -q -C --enable-runtime=libicu --enable-builtin=libicu --with-psl-file=/Users/eli/code/algorithmia/list/public_suffix_list.dat --with-psl-testfile=/Users/eli/code/algorithmia/list/tests/tests.txt && make -s clean && make -s check -j4
config.status: creating po/POTFILES
config.status: creating po/Makefile
Making clean in po
Making clean in include
Making clean in src
rm -f ./so_locations
Making clean in tools
rm -f psl
Making clean in fuzz
rm -f libpsl_icu_fuzzer libpsl_icu_load_fuzzer libpsl_icu_load_dafsa_fuzzer
Making clean in tests
rm -f test-is-public test-is-public-all test-is-cookie-domain-acceptable test-is-public-builtin test-registrable-domain
Making clean in msvc
Making check in po
Making check in include
Making check in src
CC libpsl_la-psl.lo
CC libpsl_la-lookup_string_in_fixed_set.lo
CCLD libpsl.la
Making check in tools
CC psl.o
CCLD psl
Making check in fuzz
CC libpsl_fuzzer.o
CC main.o
CC libpsl_load_fuzzer.o
CC libpsl_load_dafsa_fuzzer.o
CCLD libpsl_icu_fuzzer
CCLD libpsl_icu_load_fuzzer
CCLD libpsl_icu_load_dafsa_fuzzer
libtool: warning: '-no-install' is ignored for x86_64-apple-darwin19.6.0
libtool: warning: '-no-install' is ignored for x86_64-apple-darwin19.6.0
libtool: warning: '-no-install' is ignored for x86_64-apple-darwin19.6.0
libtool: warning: assuming '-no-fast-install' instead
libtool: warning: assuming '-no-fast-install' instead
libtool: warning: assuming '-no-fast-install' instead
PASS: libpsl_icu_load_dafsa_fuzzer
PASS: libpsl_icu_fuzzer
PASS: libpsl_icu_load_fuzzer
============================================================================
Testsuite summary for libpsl 0.21.1
============================================================================
# TOTAL: 3
# PASS: 3
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
============================================================================
Making check in tests
CC test-is-public.o
CC test-is-public-all.o
CC test-is-cookie-domain-acceptable.o
CC test-is-public-builtin.o
CC test-registrable-domain.o
CCLD test-is-cookie-domain-acceptable
CCLD test-is-public-builtin
CCLD test-is-public
CCLD test-is-public-all
libtool: warning: '-no-install' is ignored for x86_64-apple-darwin19.6.0
libtool: warning: '-no-install' is ignored for x86_64-apple-darwin19.6.0
libtool: warning: '-no-install' is ignored for x86_64-apple-darwin19.6.0
libtool: warning: assuming '-no-fast-install' instead
libtool: warning: assuming '-no-fast-install' instead
libtool: warning: assuming '-no-fast-install' instead
libtool: warning: '-no-install' is ignored for x86_64-apple-darwin19.6.0
libtool: warning: assuming '-no-fast-install' instead
CCLD test-registrable-domain
libtool: warning: '-no-install' is ignored for x86_64-apple-darwin19.6.0
libtool: warning: assuming '-no-fast-install' instead
PASS: test-is-public
PASS: test-is-cookie-domain-acceptable
PASS: test-is-public-builtin
PASS: test-is-public-all
PASS: test-registrable-domain
============================================================================
Testsuite summary for libpsl 0.21.1
============================================================================
# TOTAL: 5
# PASS: 5
# SKIP: 0
# XFAIL: 0
# FAIL: 0
# XPASS: 0
# ERROR: 0
============================================================================
Making check in msvc
</details>
pr created time in 15 days
issue commentnrwl/nx
Cypress - add reporters options
As a workaround, you can also specify these as environment variables that Cypress recognizes:
CYPRESS_REPORTER=junit CYPRESS_REPORTER_OPTIONS="mochaFile=reports/results-[hash].xml,toConsole=true" nx e2e myapp-e2e
comment created time in 19 days
PR merged algorithmiaio/api-docs
Bumps rake from 12.3.2 to 13.0.1. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/ruby/rake/blob/master/History.rdoc">rake's changelog</a>.</em></p> <blockquote> <p>=== 13.0.1</p> <p>==== Bug fixes</p> <ul> <li>Fixed bug: Reenabled task raises previous exception on second invokation Pull Request <a href="https://github-redirect.dependabot.com/ruby/rake/issues/271">#271</a> by thorsteneckel</li> <li>Fix an incorrectly resolved arg pattern Pull Request <a href="https://github-redirect.dependabot.com/ruby/rake/issues/327">#327</a> by mjbellantoni</li> </ul> <p>=== 13.0.0</p> <p>==== Enhancements</p> <ul> <li>Follows recent changes on keyword arguments in ruby 2.7. Pull Request <a href="https://github-redirect.dependabot.com/ruby/rake/issues/326">#326</a> by nobu</li> <li>Make <code>PackageTask</code> be able to omit parent directory while packing files Pull Request <a href="https://github-redirect.dependabot.com/ruby/rake/issues/310">#310</a> by tonytonyjan</li> <li>Add order only dependency Pull Request <a href="https://github-redirect.dependabot.com/ruby/rake/issues/269">#269</a> by take-cheeze</li> </ul> <p>==== Compatibility changes</p> <ul> <li>Drop old ruby versions(< 2.2)</li> </ul> <p>=== 12.3.3</p> <p>==== Bug fixes</p> <ul> <li>Use the application's name in error message if a task is not found. Pull Request <a href="https://github-redirect.dependabot.com/ruby/rake/issues/303">#303</a> by tmatilai</li> </ul> <p>==== Enhancements:</p> <ul> <li>Use File.open explicitly.</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/ruby/rake/commit/c8251e2299616d8126e4ac7426e0bb87df7e6922"><code>c8251e2</code></a> Bump version to 13.0.1</li> <li><a href="https://github.com/ruby/rake/commit/8edd860cd0fc9035bda472ef45110a40889b9627"><code>8edd860</code></a> Fixed build failure of the latest GitHub Actions</li> <li><a href="https://github.com/ruby/rake/commit/b6e2a66689e7ac2f39597283dc2276bd082fa279"><code>b6e2a66</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/ruby/rake/issues/271">#271</a> from thorsteneckel/bugfix-reenable_invocation_exception</li> <li><a href="https://github.com/ruby/rake/commit/985abffa9954d21790831d9626d9c38b24a94199"><code>985abff</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/ruby/rake/issues/327">#327</a> from mjbellantoni/mjb-order-only-arg-fix</li> <li><a href="https://github.com/ruby/rake/commit/4a90acb8923f0ea1f7acf50b8d529281a56f170d"><code>4a90acb</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/ruby/rake/issues/329">#329</a> from jeremyevans/skip-taint-test-on-2.7</li> <li><a href="https://github.com/ruby/rake/commit/4dc6282eb24c0117a012d07744ea1bbcae1b3a79"><code>4dc6282</code></a> Skip a taint test on Ruby 2.7</li> <li><a href="https://github.com/ruby/rake/commit/a08b6975a5568799e1d053b7c56ef40d28528d97"><code>a08b697</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/ruby/rake/issues/328">#328</a> from orien/gem-metadata</li> <li><a href="https://github.com/ruby/rake/commit/c3953d4b2935895e1bb4596c435653d3a865711a"><code>c3953d4</code></a> Add project metadata to the gemspec</li> <li><a href="https://github.com/ruby/rake/commit/46a8f7cbd4072431eb16e8e0858d556797ce677e"><code>46a8f7c</code></a> Update comments to reflect the current state</li> <li><a href="https://github.com/ruby/rake/commit/00aacdcf70309a17de2580fb380ed29f2d0fb6f7"><code>00aacdc</code></a> Fix an incorrectly resolved arg pattern</li> <li>Additional commits viewable in <a href="https://github.com/ruby/rake/compare/v12.3.2...v13.0.1">compare view</a></li> </ul> </details> <br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
</details>
pr closed time in a month
push eventalgorithmiaio/api-docs
commit sha 43721321db04ca02c843881c9c771a4c72270c6a
Bump rake from 12.3.2 to 13.0.1 Bumps [rake](https://github.com/ruby/rake) from 12.3.2 to 13.0.1. - [Release notes](https://github.com/ruby/rake/releases) - [Changelog](https://github.com/ruby/rake/blob/master/History.rdoc) - [Commits](https://github.com/ruby/rake/compare/v12.3.2...v13.0.1) Signed-off-by: dependabot[bot] <[email protected]>
commit sha a0d3727a650cbec6367bd870df1ab54513043ce4
Merge pull request #49 from algorithmiaio/dependabot/bundler/rake-13.0.1 Bump rake from 12.3.2 to 13.0.1
push time in a month
push eventalgorithmiaio/api-docs
commit sha 474e8644d130b03e4baeab3663a909721e6ce259
Bump nokogiri from 1.10.4 to 1.10.8 Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.10.4 to 1.10.8. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md) - [Commits](https://github.com/sparklemotion/nokogiri/compare/v1.10.4...v1.10.8) Signed-off-by: dependabot[bot] <[email protected]>
commit sha 5800008ecca7ffe447fbb4a60da59a3287f2ba9f
Merge pull request #48 from algorithmiaio/dependabot/bundler/nokogiri-1.10.8 Bump nokogiri from 1.10.4 to 1.10.8
push time in a month
PR merged algorithmiaio/api-docs
Bumps nokogiri from 1.10.4 to 1.10.8. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/sparklemotion/nokogiri/releases">nokogiri's releases</a>.</em></p> <blockquote> <h2>1.10.8 / 2020-02-10</h2> <h3>Security</h3> <p>[MRI] Pulled in upstream patch from libxml that addresses CVE-2020-7595. Full details are available in <a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1992">#1992</a>. Note that this patch is not yet (as of 2020-02-10) in an upstream release of libxml.</p> <h2>1.10.7 / 2019-12-03</h2> <h3>Bug</h3> <ul> <li>[MRI] Ensure the patch applied in v1.10.6 works with GNU <code>patch</code>. <a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1954">#1954</a></li> </ul> <h2>1.10.6 / 2019-12-03</h2> <h3>Bug</h3> <ul> <li>[MRI] Fix FreeBSD installation of vendored libxml2. [#1941, <a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1953">#1953</a>] (Thanks, <a href="https://github.com/nurse">@nurse</a>!)</li> </ul> <h2>1.10.5 / 2019-10-31</h2> <h3>Dependencies</h3> <ul> <li>[MRI] vendored libxml2 is updated from 2.9.9 to 2.9.10</li> <li>[MRI] vendored libxslt is updated from 1.1.33 to 1.1.34</li> </ul> </blockquote> </details> <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md">nokogiri's changelog</a>.</em></p> <blockquote> <h2>1.10.8 / 2020-02-10</h2> <h3>Security</h3> <p>[MRI] Pulled in upstream patch from libxml that addresses CVE-2020-7595. Full details are available in <a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1992">#1992</a>. Note that this patch is not yet (as of 2020-02-10) in an upstream release of libxml.</p> <h2>1.10.7 / 2019-12-03</h2> <h3>Fixed</h3> <ul> <li>[MRI] Ensure the patch applied in v1.10.6 works with GNU <code>patch</code>. [<a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1954">#1954</a>]</li> </ul> <h2>1.10.6 / 2019-12-03</h2> <h3>Fixed</h3> <ul> <li>[MRI] Fix FreeBSD installation of vendored libxml2. [<a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1941">#1941</a>, <a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1953">#1953</a>] (Thanks, <a href="https://github.com/nurse">@nurse</a>!)</li> </ul> <h2>1.10.5 / 2019-10-31</h2> <h3>Security</h3> <p>[MRI] Vendored libxslt upgraded to v1.1.34 which addresses three CVEs for libxslt:</p> <ul> <li>CVE-2019-13117</li> <li>CVE-2019-13118</li> <li>CVE-2019-18197</li> <li>CVE-2019-19956</li> </ul> <p>More details are available at <a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1943">#1943</a>.</p> <h3>Dependencies</h3> <ul> <li>[MRI] vendored libxml2 is updated from 2.9.9 to 2.9.10</li> <li>[MRI] vendored libxslt is updated from 1.1.33 to 1.1.34</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/sparklemotion/nokogiri/commit/6ce10d15d7af6ad65813a495eaf168f73eba211c"><code>6ce10d1</code></a> version bump to v1.10.8</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/2320f5bd6319dca9c68d85bbf41629bbf8052a49"><code>2320f5b</code></a> update CHANGELOG for v1.10.8</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/4a77fdb789aefed7ca65c7c7f57ad4dca0d3b209"><code>4a77fdb</code></a> remove patches from the hoe Manifest</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/570b6cbc5fbc5ee7ef969332c587b951ae35bcd0"><code>570b6cb</code></a> update to use rake-compiler ~1.1.0</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/2cdb68e95aa075ac36a08d4d82d9b410a950a051"><code>2cdb68e</code></a> backport libxml2 patch for CVE-2020-7595</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/e6b3229ec53ddf70f1d198bba0d3fc13fde842a8"><code>e6b3229</code></a> version bump to v1.10.7</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/4f9d443c2fddc40eefec3366000861433aff6179"><code>4f9d443</code></a> update CHANGELOG</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/80e67ef636ce0ddd55a4a7578d7bbdb186002560"><code>80e67ef</code></a> Fix the patch from <a href="https://github-redirect.dependabot.com/sparklemotion/nokogiri/issues/1953">#1953</a> to work with both <code>git</code> and <code>patch</code></li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/7cf1b85a5f8033252e55844ab2765e8f612d4d89"><code>7cf1b85</code></a> Fix typo in generated metadata</li> <li><a href="https://github.com/sparklemotion/nokogiri/commit/d76180d0d26a7afb76d84e0de2550ac3bb6abb15"><code>d76180d</code></a> add gem metadata</li> <li>Additional commits viewable in <a href="https://github.com/sparklemotion/nokogiri/compare/v1.10.4...v1.10.8">compare view</a></li> </ul> </details> <br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
</details>
pr closed time in a month
push eventalgorithmiaio/api-docs
commit sha 5fc6fbaddc25161b21b1d4682b3022653b1ef2b3
Bump rack from 2.0.7 to 2.2.3 Bumps [rack](https://github.com/rack/rack) from 2.0.7 to 2.2.3. - [Release notes](https://github.com/rack/rack/releases) - [Changelog](https://github.com/rack/rack/blob/master/CHANGELOG.md) - [Commits](https://github.com/rack/rack/compare/2.0.7...2.2.3) Signed-off-by: dependabot[bot] <[email protected]>
commit sha 3263da8b8ae8cb49f248af428af42e5c72f86134
Merge pull request #47 from algorithmiaio/dependabot/bundler/rack-2.2.3 Bump rack from 2.0.7 to 2.2.3
push time in a month
PR merged algorithmiaio/api-docs
Bumps rack from 2.0.7 to 2.2.3. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rack/rack/blob/master/CHANGELOG.md">rack's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>All notable changes to this project will be documented in this file. For info on how to format all future additions to this file please reference <a href="https://keepachangelog.com/en/1.0.0/">Keep A Changelog</a>.</p> <h2>[3.0.0] - Unreleased</h2> <h3>Changed</h3> <ul> <li>BREAKING CHANGE: Require <code>status</code> to be an Integer. (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1662">#1662</a>, <a href="https://github.com/olleolleolle">@olleolleolle</a>)</li> <li>Relax validations around <code>Rack::Request#host</code> and <code>Rack::Request#hostname</code>. (<a href="https://github-redirect.dependabot.com/rack/rack/issues/1606">#1606</a>, <a href="https://github.com/pvande">@pvande</a>)</li> <li>Removed antiquated handlers: FCGI, LSWS, SCGI, Thin. (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1658">#1658</a>, <a href="https://github.com/ioquatix">@ioquatix</a>)</li> <li>Removed options from <code>Rack::Builder.parse_file</code> and <code>Rack::Builder.load_file</code>. (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1663">#1663</a>, <a href="https://github.com/ioquatix">@ioquatix</a>)</li> <li>HMAC argument for <code>Rack::Session::Cookie</code> doesn't accept a class constant anymore, but only a string recognized by OpenSSL (e.g. <code>"SHA256"</code>) or compatible instance (e.g. <code>OpenSSL::Digest.new("SHA256")</code>) (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1676">#1676</a>, <a href="https://github.com/bdewater">@bdewater</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>Fix using Rack::Session::Cookie with coder: Rack::Session::Cookie::Base64::{JSON,Zip}. (<a href="https://github-redirect.dependabot.com/rack/rack/issues/1666">#1666</a>, <a href="https://github.com/jeremyevans">@jeremyevans</a>)</li> <li>Avoid NoMethodError when accessing Rack::Session::Cookie without requiring delegate first. (<a href="https://github-redirect.dependabot.com/rack/rack/issues/1610">#1610</a>, <a href="https://github.com/onigra">@onigra</a>)</li> <li>Handle cookies with values that end in '=' (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1645">#1645</a>, <a href="https://github.com/lukaso">@lukaso</a>)</li> </ul> <h2>[2.2.2] - 2020-02-11</h2> <h3>Fixed</h3> <ul> <li>Fix incorrect <code>Rack::Request#host</code> value. (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1591">#1591</a>, <a href="https://github.com/ioquatix">@ioquatix</a>)</li> <li>Revert <code>Rack::Handler::Thin</code> implementation. (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1583">#1583</a>, <a href="https://github.com/jeremyevans">@jeremyevans</a>)</li> <li>Double assignment is still needed to prevent an "unused variable" warning. (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1589">#1589</a>, <a href="https://github.com/kamipo">@kamipo</a>)</li> <li>Fix to handle same_site option for session pool. (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1587">#1587</a>, <a href="https://github.com/kamipo">@kamipo</a>)</li> </ul> <h2>[2.2.1] - 2020-02-09</h2> <h3>Fixed</h3> <ul> <li>Rework <code>Rack::Request#ip</code> to handle empty <code>forwarded_for</code>. (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1577">#1577</a>, <a href="https://github.com/ioquatix">@ioquatix</a>)</li> </ul> <h2>[2.2.0] - 2020-02-08</h2> <h3>SPEC Changes</h3> <ul> <li><code>rack.session</code> request environment entry must respond to <code>to_hash</code> and return unfrozen Hash. (<a href="https://github.com/jeremyevans">@jeremyevans</a>)</li> <li>Request environment cannot be frozen. (<a href="https://github.com/jeremyevans">@jeremyevans</a>)</li> <li>CGI values in the request environment with non-ASCII characters must use ASCII-8BIT encoding. (<a href="https://github.com/jeremyevans">@jeremyevans</a>)</li> <li>Improve SPEC/lint relating to SERVER_NAME, SERVER_PORT and HTTP_HOST. (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1561">#1561</a>, <a href="https://github.com/ioquatix">@ioquatix</a>)</li> </ul> <h3>Added</h3> <ul> <li><code>rackup</code> supports multiple <code>-r</code> options and will require all arguments. (<a href="https://github.com/jeremyevans">@jeremyevans</a>)</li> <li><code>Server</code> supports an array of paths to require for the <code>:require</code> option. (<a href="https://github.com/khotta">@khotta</a>)</li> <li><code>Files</code> supports multipart range requests. (<a href="https://github.com/fatkodima">@fatkodima</a>)</li> <li><code>Multipart::UploadedFile</code> supports an IO-like object instead of using the filesystem, using <code>:filename</code> and <code>:io</code> options. (<a href="https://github.com/jeremyevans">@jeremyevans</a>)</li> </ul> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rack/rack/commit/1741c580d71cfca8e541e96cc372305c8892ee74"><code>1741c58</code></a> bump version</li> <li><a href="https://github.com/rack/rack/commit/5ccca4722668083732ea2d35c56565fcc25312f8"><code>5ccca47</code></a> When parsing cookies, only decode the values</li> <li><a href="https://github.com/rack/rack/commit/a5e80f01947954af76b14c1d1fdd8e79dd8337f3"><code>a5e80f0</code></a> Bump version.</li> <li><a href="https://github.com/rack/rack/commit/b0de37dc3b67d2fdcaa8b0236ff076a0a4db0b4f"><code>b0de37d</code></a> Remove trailing whitespace.</li> <li><a href="https://github.com/rack/rack/commit/1a784e54c867d42214d9e1f315651b1f2cea8591"><code>1a784e5</code></a> Prepare CHANGELOG for next patch release.</li> <li><a href="https://github.com/rack/rack/commit/a0d57d4a1d917596e03e0aa969aff7e890d2123c"><code>a0d57d4</code></a> Fix to handle same_site option for session pool</li> <li><a href="https://github.com/rack/rack/commit/a9b223b6781201ae8faa5d0a373cd1a24f6d97a3"><code>a9b223b</code></a> Ensure full match. Fixes <a href="https://github-redirect.dependabot.com/rack/rack/issues/1590">#1590</a>.</li> <li><a href="https://github.com/rack/rack/commit/f4c5645642ec99fa82a5a343a6c79d4aff8d6165"><code>f4c5645</code></a> Double assignment is still needed to prevent an "unused variable" warning</li> <li><a href="https://github.com/rack/rack/commit/5c121dd6853fa231d1b1253b6e8e7cfc927791ca"><code>5c121dd</code></a> Revert "Update Thin handler to better handle more options"</li> <li><a href="https://github.com/rack/rack/commit/961d9761bcb2bee17c80bba8b7bc9e285086d6c4"><code>961d976</code></a> Prepare point release.</li> <li>Additional commits viewable in <a href="https://github.com/rack/rack/compare/2.0.7...2.2.3">compare view</a></li> </ul> </details> <br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
</details>
pr closed time in a month
issue commentUrigo/graphql-modules
Custom scalars don't run when using apollo-server `modules`
An alternative solution from https://github.com/apollographql/apollo-server/issues/2218#issuecomment-593271456 also allows you to continue to use modules via the @apollo/federation package:
import { buildFederatedSchema } from '@apollo/federation';
const server = new ApolloServer({
schema: buildFederatedSchema([MyGraphQLModule]),
});
comment created time in a month
push eventalgorithmiaio/api-docs
commit sha 44c16dfbf9e0b3f9642a5ce2735e51c8ba8b18b0
Bump rack from 2.2.2 to 2.2.3 Bumps [rack](https://github.com/rack/rack) from 2.2.2 to 2.2.3. - [Release notes](https://github.com/rack/rack/releases) - [Changelog](https://github.com/rack/rack/blob/master/CHANGELOG.md) - [Commits](https://github.com/rack/rack/compare/v2.2.2...2.2.3) Signed-off-by: dependabot[bot] <[email protected]>
commit sha 0e1fe5fb7e6fd8d914178abb104e4ff18cbec01c
Merge pull request #41 from algorithmiaio/dependabot/bundler/rack-2.2.3 Bump rack from 2.2.2 to 2.2.3
push time in a month
PR merged algorithmiaio/api-docs
Bumps rack from 2.2.2 to 2.2.3. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/rack/rack/blob/master/CHANGELOG.md">rack's changelog</a>.</em></p> <blockquote> <h1>Changelog</h1> <p>All notable changes to this project will be documented in this file. For info on how to format all future additions to this file please reference <a href="https://keepachangelog.com/en/1.0.0/">Keep A Changelog</a>.</p> <h2>[3.0.0] - Unreleased</h2> <h3>Changed</h3> <ul> <li>BREAKING CHANGE: Require <code>status</code> to be an Integer. (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1662">#1662</a>, <a href="https://github.com/olleolleolle">@olleolleolle</a>)</li> <li>Relax validations around <code>Rack::Request#host</code> and <code>Rack::Request#hostname</code>. (<a href="https://github-redirect.dependabot.com/rack/rack/issues/1606">#1606</a>, <a href="https://github.com/pvande">@pvande</a>)</li> <li>Removed antiquated handlers: FCGI, LSWS, SCGI, Thin. (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1658">#1658</a>, <a href="https://github.com/ioquatix">@ioquatix</a>)</li> <li>Removed options from <code>Rack::Builder.parse_file</code> and <code>Rack::Builder.load_file</code>. (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1663">#1663</a>, <a href="https://github.com/ioquatix">@ioquatix</a>)</li> </ul> <h3>Fixed</h3> <ul> <li>Fix using Rack::Session::Cookie with coder: Rack::Session::Cookie::Base64::{JSON,Zip}. (<a href="https://github-redirect.dependabot.com/rack/rack/issues/1666">#1666</a>, <a href="https://github.com/jeremyevans">@jeremyevans</a>)</li> <li>Avoid NoMethodError when accessing Rack::Session::Cookie without requiring delegate first. (<a href="https://github-redirect.dependabot.com/rack/rack/issues/1610">#1610</a>, <a href="https://github.com/onigra">@onigra</a>)</li> <li>Handle cookies with values that end in '=' (<a href="https://github-redirect.dependabot.com/rack/rack/pull/1645">#1645</a>, <a href="https://github.com/lukaso">@lukaso</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/rack/rack/commit/1741c580d71cfca8e541e96cc372305c8892ee74"><code>1741c58</code></a> bump version</li> <li><a href="https://github.com/rack/rack/commit/5ccca4722668083732ea2d35c56565fcc25312f8"><code>5ccca47</code></a> When parsing cookies, only decode the values</li> <li>See full diff in <a href="https://github.com/rack/rack/compare/v2.2.2...2.2.3">compare view</a></li> </ul> </details> <br />
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
<details> <summary>Dependabot commands and options</summary> <br />
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.
</details>
pr closed time in a month
issue closednwtgck/actions-netlify
Action seems to erroneously state credentials not provided
I am attempting to run this action that has been in place, but appears to now be failing that credentials are not provided. The secret appears to be passed according to the logs:

This is my job for the relevant action:
deploy:
name: Deploy
runs-on: ubuntu-latest
needs: [setup, compile]
if: ${{ needs.setup.outputs.affected-deploys != '[]' }}
strategy:
matrix:
node: ['12.x']
deploy: ${{ fromJson(needs.setup.outputs.affected-deploys) }}
steps:
- name: Checkout repository
uses: actions/checkout@v2
with:
fetch-depth: 0
- name: Set cache directory
id: yarn-cache-dir-path
run: echo "::set-output name=dir::$(yarn cache dir)"
- name: Restore cache
uses: actions/cache@v2
id: yarn-cache
with:
path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
restore-keys: |
${{ runner.os }}-yarn-
- name: Set up Node.js
uses: actions/setup-node@v2-beta
with:
node-version: ${{ matrix.node }}
- name: Install dependencies
env:
CACHE_HIT: ${{ steps.yarn-cache.outputs.cache-hit }}
run: tools/scripts/yarn-ci.sh
- name: Restore compilation
uses: actions/download-artifact@v2
with:
name: dist
path: dist/
- run: touch dist/apps/${{ matrix.deploy.project }}/.prod.env
- run: touch dist/apps/${{ matrix.deploy.project }}/.env
- uses: c-py/action-dotenv-to-setenv@v1
with:
env-file: dist/apps/${{ matrix.deploy.project }}/.prod.env
env:
DOTENV_DEFAULT: dist/apps/${{ matrix.deploy.project }}/.env
- name: Deploy to Netlify
uses: nwtgck/[email protected]
with:
publish-dir: dist/apps/${{ matrix.deploy.project }}
production-branch: master
github-token: ${{ secrets.GITHUB_TOKEN }}
deploy-message: "Deploy from GitHub Actions"
enable-commit-comment: false
netlify-config-path: ./netlify.toml
functions-dir: dist/functions/
env:
NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }}
Thanks for helping out!
closed time in a month
eliperelmanissue commentnwtgck/actions-netlify
Action seems to erroneously state credentials not provided
Nice catch! I was loading my .env files instead of passing the environment variable manually, but turns out the .env files weren't copied into the build directory.
comment created time in a month
issue openednwtgck/actions-netlify
Action seems to erroneously state credentials not provided
I am attempting to run this action that has been in place, but appears to now be failing that credentials are not provided. The secret appears to be passed according to the logs:

This is my job for the relevant action:
deploy:
name: Deploy
runs-on: ubuntu-latest
needs: [setup, compile]
if: ${{ needs.setup.outputs.affected-deploys != '[]' }}
strategy:
matrix:
node: ['12.x']
deploy: ${{ fromJson(needs.setup.outputs.affected-deploys) }}
steps:
- name: Checkout repository
uses: actions/checkout@v2
with:
fetch-depth: 0
- name: Set cache directory
id: yarn-cache-dir-path
run: echo "::set-output name=dir::$(yarn cache dir)"
- name: Restore cache
uses: actions/cache@v2
id: yarn-cache
with:
path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
restore-keys: |
${{ runner.os }}-yarn-
- name: Set up Node.js
uses: actions/setup-node@v2-beta
with:
node-version: ${{ matrix.node }}
- name: Install dependencies
env:
CACHE_HIT: ${{ steps.yarn-cache.outputs.cache-hit }}
run: tools/scripts/yarn-ci.sh
- name: Restore compilation
uses: actions/download-artifact@v2
with:
name: dist
path: dist/
- run: touch dist/apps/${{ matrix.deploy.project }}/.prod.env
- run: touch dist/apps/${{ matrix.deploy.project }}/.env
- uses: c-py/action-dotenv-to-setenv@v1
with:
env-file: dist/apps/${{ matrix.deploy.project }}/.prod.env
env:
DOTENV_DEFAULT: dist/apps/${{ matrix.deploy.project }}/.env
- name: Deploy to Netlify
uses: nwtgck/[email protected]
with:
publish-dir: dist/apps/${{ matrix.deploy.project }}
production-branch: master
github-token: ${{ secrets.GITHUB_TOKEN }}
deploy-message: "Deploy from GitHub Actions"
enable-commit-comment: false
netlify-config-path: ./netlify.toml
functions-dir: dist/functions/
env:
NETLIFY_AUTH_TOKEN: ${{ secrets.NETLIFY_AUTH_TOKEN }}
Thanks for helping out!
created time in a month
Pull request review commentalgorithmiaio/dev-center
+---+layout: article+title: "Event Listeners via Azure SB"+excerpt-short: "Set up an Event Listener to run an Algorithm with inputs from an Azure Service Bus Queue"+categories: [integrations]+tags: [integrations]+show_related: true+---++These directions will help you to set up an Algorithmia Event Listener, which will run an algorithm with input payloads provided in an Azure Service Bus Queue. For more info about Azure Service Bus read https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues++This is only available for Enterprise installations of Algorithmia. +{: .notice-warning}++## 1. Obtain a template file and account info from Algorithmia++Contact [[email protected]](mailto:[email protected]) to obtain the following, which you will need during CloudFormation setup:++* Azure Resource Manager(ARM) template for Service Bus Namespace and Queue+* Custom Role definition file - QueueReceiver+* Algorithmia Azure Account++## 2. Invite Algorithmia account as guest account in your account’s Active Directory++Using the Custom Role definition file you have gotten in step 1, create the Custom Role in your account. ++* Authenticate with Azure CLI+* Run “$ az role definition create --role-definition GuestRole.json”++More details on how to do this with Azure Cli can be found here: https://docs.microsoft.com/en-us/azure/role-based-access-control/custom-roles-cli+It can be also done via PowerShell and REST api.+++## 3. Invite Algorithmia account as guest account in your account’s Active Directory+Create a new guest user account with Algorithmia’s account email.++* Sign in to the Azure portal as an Azure AD administrator.+* In the left pane, select Azure Active Directory.+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_33.png">+* Select New guest user.+* On the New user page, select Invite user and then add the guest user's information.+* * Name. The first and last name of the guest user.+* * Email address. Use the email obtained in step 1 +* * Groups: You can add the guest user to one or more existing groups, or you can do it later.+* * Directory role: Use the role you created in step 2 (QueueReceiver)+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_34.png">+* * Select Invite to automatically send the invitation to the guest user. A notification appears in the upper right with the message Successfully invited user. The user account is now added to the directory as a guest account with the custom role.++## 4. Create Service Bus Namespace and Queue ++* Import ARM template and create your Service Bus Namespace and Queue.+Info about ARM templates: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/overview+Info about Service Bus: https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-quickstart-portal#:~:text=In%20the%20left%20navigation%20pane,if%20the%20name%20is%20available+* Create a new Template, and load the contents of the ARM template file from step 1 into the ARM template tab. Save the template and click “Deploy Template”
Add period to end of sentence.
comment created time in a month
Pull request review commentalgorithmiaio/dev-center
+---+layout: article+title: "Event Listeners via Azure SB"+excerpt-short: "Set up an Event Listener to run an Algorithm with inputs from an Azure Service Bus Queue"+categories: [integrations]+tags: [integrations]+show_related: true+---++These directions will help you to set up an Algorithmia Event Listener, which will run an algorithm with input payloads provided in an Azure Service Bus Queue. For more info about Azure Service Bus read https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues++This is only available for Enterprise installations of Algorithmia. +{: .notice-warning}++## 1. Obtain a template file and account info from Algorithmia++Contact [[email protected]](mailto:[email protected]) to obtain the following, which you will need during CloudFormation setup:++* Azure Resource Manager(ARM) template for Service Bus Namespace and Queue+* Custom Role definition file - QueueReceiver+* Algorithmia Azure Account++## 2. Invite Algorithmia account as guest account in your account’s Active Directory++Using the Custom Role definition file you have gotten in step 1, create the Custom Role in your account. ++* Authenticate with Azure CLI+* Run “$ az role definition create --role-definition GuestRole.json”++More details on how to do this with Azure Cli can be found here: https://docs.microsoft.com/en-us/azure/role-based-access-control/custom-roles-cli+It can be also done via PowerShell and REST api.+++## 3. Invite Algorithmia account as guest account in your account’s Active Directory+Create a new guest user account with Algorithmia’s account email.++* Sign in to the Azure portal as an Azure AD administrator.+* In the left pane, select Azure Active Directory.+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_33.png">+* Select New guest user.+* On the New user page, select Invite user and then add the guest user's information.+* * Name. The first and last name of the guest user.+* * Email address. Use the email obtained in step 1 +* * Groups: You can add the guest user to one or more existing groups, or you can do it later.+* * Directory role: Use the role you created in step 2 (QueueReceiver)+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_34.png">+* * Select Invite to automatically send the invitation to the guest user. A notification appears in the upper right with the message Successfully invited user. The user account is now added to the directory as a guest account with the custom role.++## 4. Create Service Bus Namespace and Queue ++* Import ARM template and create your Service Bus Namespace and Queue.+Info about ARM templates: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/overview+Info about Service Bus: https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-quickstart-portal#:~:text=In%20the%20left%20navigation%20pane,if%20the%20name%20is%20available+* Create a new Template, and load the contents of the ARM template file from step 1 into the ARM template tab. Save the template and click “Deploy Template”+* Fill in the Namespace Name, Queue Name, and choose region appropriate for you. ++Note: If the deployment fails, chances are there is already a namespace created with that name in the region you chose. If that is the error message you get on deployment error, you would need to redeploy with a different name until it works.++## 5. Test Event Listener++* Create a new Python 3.X Algorithm.+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_35.png">++* In web IDE replace source with the following:
s/In web IDE/In the web IDE/
comment created time in a month
Pull request review commentalgorithmiaio/dev-center
+---+layout: article+title: "Event Listeners via Azure SB"+excerpt-short: "Set up an Event Listener to run an Algorithm with inputs from an Azure Service Bus Queue"+categories: [integrations]+tags: [integrations]+show_related: true+---++These directions will help you to set up an Algorithmia Event Listener, which will run an algorithm with input payloads provided in an Azure Service Bus Queue. For more info about Azure Service Bus read https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues++This is only available for Enterprise installations of Algorithmia. +{: .notice-warning}++## 1. Obtain a template file and account info from Algorithmia++Contact [[email protected]](mailto:[email protected]) to obtain the following, which you will need during CloudFormation setup:++* Azure Resource Manager(ARM) template for Service Bus Namespace and Queue+* Custom Role definition file - QueueReceiver+* Algorithmia Azure Account++## 2. Invite Algorithmia account as guest account in your account’s Active Directory++Using the Custom Role definition file you have gotten in step 1, create the Custom Role in your account. ++* Authenticate with Azure CLI+* Run “$ az role definition create --role-definition GuestRole.json”++More details on how to do this with Azure Cli can be found here: https://docs.microsoft.com/en-us/azure/role-based-access-control/custom-roles-cli
s/can be found here/can be found at/ s/Cli/CLI/
comment created time in a month
Pull request review commentalgorithmiaio/dev-center
+---+layout: article+title: "Event Listeners via Azure SB"+excerpt-short: "Set up an Event Listener to run an Algorithm with inputs from an Azure Service Bus Queue"+categories: [integrations]+tags: [integrations]+show_related: true+---++These directions will help you to set up an Algorithmia Event Listener, which will run an algorithm with input payloads provided in an Azure Service Bus Queue. For more info about Azure Service Bus read https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues++This is only available for Enterprise installations of Algorithmia. +{: .notice-warning}++## 1. Obtain a template file and account info from Algorithmia++Contact [[email protected]](mailto:[email protected]) to obtain the following, which you will need during CloudFormation setup:++* Azure Resource Manager(ARM) template for Service Bus Namespace and Queue+* Custom Role definition file - QueueReceiver+* Algorithmia Azure Account++## 2. Invite Algorithmia account as guest account in your account’s Active Directory++Using the Custom Role definition file you have gotten in step 1, create the Custom Role in your account. ++* Authenticate with Azure CLI+* Run “$ az role definition create --role-definition GuestRole.json”++More details on how to do this with Azure Cli can be found here: https://docs.microsoft.com/en-us/azure/role-based-access-control/custom-roles-cli+It can be also done via PowerShell and REST api.+++## 3. Invite Algorithmia account as guest account in your account’s Active Directory+Create a new guest user account with Algorithmia’s account email.++* Sign in to the Azure portal as an Azure AD administrator.+* In the left pane, select Azure Active Directory.+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_33.png">+* Select New guest user.+* On the New user page, select Invite user and then add the guest user's information.+* * Name. The first and last name of the guest user.+* * Email address. Use the email obtained in step 1 +* * Groups: You can add the guest user to one or more existing groups, or you can do it later.+* * Directory role: Use the role you created in step 2 (QueueReceiver)+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_34.png">+* * Select Invite to automatically send the invitation to the guest user. A notification appears in the upper right with the message Successfully invited user. The user account is now added to the directory as a guest account with the custom role.++## 4. Create Service Bus Namespace and Queue ++* Import ARM template and create your Service Bus Namespace and Queue.+Info about ARM templates: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/overview+Info about Service Bus: https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-quickstart-portal#:~:text=In%20the%20left%20navigation%20pane,if%20the%20name%20is%20available+* Create a new Template, and load the contents of the ARM template file from step 1 into the ARM template tab. Save the template and click “Deploy Template”+* Fill in the Namespace Name, Queue Name, and choose region appropriate for you. ++Note: If the deployment fails, chances are there is already a namespace created with that name in the region you chose. If that is the error message you get on deployment error, you would need to redeploy with a different name until it works.++## 5. Test Event Listener++* Create a new Python 3.X Algorithm.+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_35.png">++* In web IDE replace source with the following:++{% highlight python %}+import Algorithmia++def apply(input):+ Algorithmia.client().file("data://<username>/event_output_directory/" + input.get("filename")).put(input.get("data"))++{% endhighlight %}+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_36.png">+* Click Save, then Build, then Publish buttons. On the algorithm page copy the full “path” of the algorithm.+* Create Hosted Data directory “event_output_directory”+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_37.png">+* Create event listener -> Azure, algorithm name, algorithm version+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_38.png">+* To test event listener, create a new Python 3.x algorithm just like before, and replace source code with the following:++{% highlight python %}+import Algorithmia+from azure.servicebus import QueueClient, Message++def apply(input):+ # Create the QueueClient+ queue_client = QueueClient.from_connection_string("<Connection String>", "<Queue Name>")++ # Send a test message to the queue+ msg = Message(b'{"filename":"test","data":"test-data"}')+ queue_client.send(msg) ++{% endhighlight %}++* Add these dependencies to the created algorithm:++{% highlight python %}+azure-common==1.1.25 +azure-servicebus==0.50.2+{% endhighlight %}+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_39.png">+* Run the algorithm that would send messages+* Check the event_output_directory, it should have a file with filename “test”
Let's make this once sentence:
* Check the `event_output_directory` for a file named “test”.
comment created time in a month
Pull request review commentalgorithmiaio/dev-center
+---+layout: article+title: "Event Listeners via Azure SB"+excerpt-short: "Set up an Event Listener to run an Algorithm with inputs from an Azure Service Bus Queue"+categories: [integrations]+tags: [integrations]+show_related: true+---++These directions will help you to set up an Algorithmia Event Listener, which will run an algorithm with input payloads provided in an Azure Service Bus Queue. For more info about Azure Service Bus read https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues++This is only available for Enterprise installations of Algorithmia. +{: .notice-warning}++## 1. Obtain a template file and account info from Algorithmia++Contact [[email protected]](mailto:[email protected]) to obtain the following, which you will need during CloudFormation setup:++* Azure Resource Manager(ARM) template for Service Bus Namespace and Queue+* Custom Role definition file - QueueReceiver+* Algorithmia Azure Account++## 2. Invite Algorithmia account as guest account in your account’s Active Directory++Using the Custom Role definition file you have gotten in step 1, create the Custom Role in your account. ++* Authenticate with Azure CLI+* Run “$ az role definition create --role-definition GuestRole.json”++More details on how to do this with Azure Cli can be found here: https://docs.microsoft.com/en-us/azure/role-based-access-control/custom-roles-cli+It can be also done via PowerShell and REST api.+++## 3. Invite Algorithmia account as guest account in your account’s Active Directory+Create a new guest user account with Algorithmia’s account email.++* Sign in to the Azure portal as an Azure AD administrator.+* In the left pane, select Azure Active Directory.+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_33.png">+* Select New guest user.+* On the New user page, select Invite user and then add the guest user's information.+* * Name. The first and last name of the guest user.+* * Email address. Use the email obtained in step 1 +* * Groups: You can add the guest user to one or more existing groups, or you can do it later.+* * Directory role: Use the role you created in step 2 (QueueReceiver)+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_34.png">+* * Select Invite to automatically send the invitation to the guest user. A notification appears in the upper right with the message Successfully invited user. The user account is now added to the directory as a guest account with the custom role.++## 4. Create Service Bus Namespace and Queue ++* Import ARM template and create your Service Bus Namespace and Queue.+Info about ARM templates: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/overview+Info about Service Bus: https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-quickstart-portal#:~:text=In%20the%20left%20navigation%20pane,if%20the%20name%20is%20available+* Create a new Template, and load the contents of the ARM template file from step 1 into the ARM template tab. Save the template and click “Deploy Template”+* Fill in the Namespace Name, Queue Name, and choose region appropriate for you. ++Note: If the deployment fails, chances are there is already a namespace created with that name in the region you chose. If that is the error message you get on deployment error, you would need to redeploy with a different name until it works.++## 5. Test Event Listener++* Create a new Python 3.X Algorithm.+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_35.png">++* In web IDE replace source with the following:++{% highlight python %}+import Algorithmia++def apply(input):+ Algorithmia.client().file("data://<username>/event_output_directory/" + input.get("filename")).put(input.get("data"))++{% endhighlight %}+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_36.png">+* Click Save, then Build, then Publish buttons. On the algorithm page copy the full “path” of the algorithm.+* Create Hosted Data directory “event_output_directory”+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_37.png">+* Create event listener -> Azure, algorithm name, algorithm version+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_38.png">+* To test event listener, create a new Python 3.x algorithm just like before, and replace source code with the following:
s/replace source code/replace the source code/
comment created time in a month
Pull request review commentalgorithmiaio/dev-center
+---+layout: article+title: "Event Listeners via Azure SB"+excerpt-short: "Set up an Event Listener to run an Algorithm with inputs from an Azure Service Bus Queue"+categories: [integrations]+tags: [integrations]+show_related: true+---++These directions will help you to set up an Algorithmia Event Listener, which will run an algorithm with input payloads provided in an Azure Service Bus Queue. For more info about Azure Service Bus read https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues++This is only available for Enterprise installations of Algorithmia. +{: .notice-warning}++## 1. Obtain a template file and account info from Algorithmia++Contact [[email protected]](mailto:[email protected]) to obtain the following, which you will need during CloudFormation setup:++* Azure Resource Manager(ARM) template for Service Bus Namespace and Queue+* Custom Role definition file - QueueReceiver+* Algorithmia Azure Account++## 2. Invite Algorithmia account as guest account in your account’s Active Directory++Using the Custom Role definition file you have gotten in step 1, create the Custom Role in your account. ++* Authenticate with Azure CLI+* Run “$ az role definition create --role-definition GuestRole.json”++More details on how to do this with Azure Cli can be found here: https://docs.microsoft.com/en-us/azure/role-based-access-control/custom-roles-cli+It can be also done via PowerShell and REST api.+++## 3. Invite Algorithmia account as guest account in your account’s Active Directory+Create a new guest user account with Algorithmia’s account email.++* Sign in to the Azure portal as an Azure AD administrator.+* In the left pane, select Azure Active Directory.+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_33.png">+* Select New guest user.+* On the New user page, select Invite user and then add the guest user's information.+* * Name. The first and last name of the guest user.+* * Email address. Use the email obtained in step 1 +* * Groups: You can add the guest user to one or more existing groups, or you can do it later.+* * Directory role: Use the role you created in step 2 (QueueReceiver)+<img src="{{site.cdnurl}}{{site.baseurl}}/images/post_images/eventlisteners/image_34.png">+* * Select Invite to automatically send the invitation to the guest user. A notification appears in the upper right with the message Successfully invited user. The user account is now added to the directory as a guest account with the custom role.++## 4. Create Service Bus Namespace and Queue ++* Import ARM template and create your Service Bus Namespace and Queue.+Info about ARM templates: https://docs.microsoft.com/en-us/azure/azure-resource-manager/management/overview+Info about Service Bus: https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-quickstart-portal#:~:text=In%20the%20left%20navigation%20pane,if%20the%20name%20is%20available+* Create a new Template, and load the contents of the ARM template file from step 1 into the ARM template tab. Save the template and click “Deploy Template”+* Fill in the Namespace Name, Queue Name, and choose region appropriate for you. ++Note: If the deployment fails, chances are there is already a namespace created with that name in the region you chose. If that is the error message you get on deployment error, you would need to redeploy with a different name until it works.++## 5. Test Event Listener++* Create a new Python 3.X Algorithm.
s/3.X/3.x/
comment created time in a month
Pull request review commentalgorithmiaio/dev-center
+---+layout: article+title: "Event Listeners via Azure SB"+excerpt-short: "Set up an Event Listener to run an Algorithm with inputs from an Azure Service Bus Queue"+categories: [integrations]+tags: [integrations]+show_related: true+---++These directions will help you to set up an Algorithmia Event Listener, which will run an algorithm with input payloads provided in an Azure Service Bus Queue. For more info about Azure Service Bus read https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues++This is only available for Enterprise installations of Algorithmia. +{: .notice-warning}++## 1. Obtain a template file and account info from Algorithmia++Contact [[email protected]](mailto:[email protected]) to obtain the following, which you will need during CloudFormation setup:++* Azure Resource Manager(ARM) template for Service Bus Namespace and Queue+* Custom Role definition file - QueueReceiver+* Algorithmia Azure Account++## 2. Invite Algorithmia account as guest account in your account’s Active Directory++Using the Custom Role definition file you have gotten in step 1, create the Custom Role in your account. ++* Authenticate with Azure CLI+* Run “$ az role definition create --role-definition GuestRole.json”++More details on how to do this with Azure Cli can be found here: https://docs.microsoft.com/en-us/azure/role-based-access-control/custom-roles-cli+It can be also done via PowerShell and REST api.
s/api/API/
comment created time in a month
Pull request review commentalgorithmiaio/dev-center
+---+layout: article+title: "Event Listeners via Azure SB"+excerpt-short: "Set up an Event Listener to run an Algorithm with inputs from an Azure Service Bus Queue"+categories: [integrations]+tags: [integrations]+show_related: true+---++These directions will help you to set up an Algorithmia Event Listener, which will run an algorithm with input payloads provided in an Azure Service Bus Queue. For more info about Azure Service Bus read https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues++This is only available for Enterprise installations of Algorithmia. +{: .notice-warning}++## 1. Obtain a template file and account info from Algorithmia++Contact [[email protected]](mailto:[email protected]) to obtain the following, which you will need during CloudFormation setup:++* Azure Resource Manager(ARM) template for Service Bus Namespace and Queue+* Custom Role definition file - QueueReceiver+* Algorithmia Azure Account++## 2. Invite Algorithmia account as guest account in your account’s Active Directory++Using the Custom Role definition file you have gotten in step 1, create the Custom Role in your account. ++* Authenticate with Azure CLI+* Run “$ az role definition create --role-definition GuestRole.json”
Remove the double quotes and replace with backticks. Let's also remove the $ shell so it's friendly with copy/paste.
Run `az role definition create --role-definition GuestRole.json`
comment created time in a month
Pull request review commentalgorithmiaio/dev-center
+---+layout: article+title: "Event Listeners via Azure SB"+excerpt-short: "Set up an Event Listener to run an Algorithm with inputs from an Azure Service Bus Queue"+categories: [integrations]+tags: [integrations]+show_related: true+---++These directions will help you to set up an Algorithmia Event Listener, which will run an algorithm with input payloads provided in an Azure Service Bus Queue. For more info about Azure Service Bus read https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues++This is only available for Enterprise installations of Algorithmia. +{: .notice-warning}++## 1. Obtain a template file and account info from Algorithmia++Contact [[email protected]](mailto:[email protected]) to obtain the following, which you will need during CloudFormation setup:++* Azure Resource Manager(ARM) template for Service Bus Namespace and Queue+* Custom Role definition file - QueueReceiver+* Algorithmia Azure Account++## 2. Invite Algorithmia account as guest account in your account’s Active Directory++Using the Custom Role definition file you have gotten in step 1, create the Custom Role in your account.
s/you have gotten/you received/
comment created time in a month
Pull request review commentalgorithmiaio/dev-center
+---+layout: article+title: "Event Listeners via Azure SB"+excerpt-short: "Set up an Event Listener to run an Algorithm with inputs from an Azure Service Bus Queue"+categories: [integrations]+tags: [integrations]+show_related: true+---++These directions will help you to set up an Algorithmia Event Listener, which will run an algorithm with input payloads provided in an Azure Service Bus Queue. For more info about Azure Service Bus read https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues
Can you change the prose to make the link inline?
[Read more about Azure Service Bus.](https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-dotnet-get-started-with-queues)
comment created time in a month
pull request commentalgorithmiaio/dev-center
Remove "robots: none" from all docs pages
This was done as part of GROWTH-738 to remove duplicate content, but maybe too many things were removed. @cannedyeti could you provide some information on this?
comment created time in a month
Pull request review commentalgorithmiaio/sample-apps
<h4>Easily Add Color to Your Black and White Photos</h4> <div class="col-md-8"> <p>Bring new life to old photos by automatically colorizing them using the Algorithmia API. It's as easy as pasting in a URL above.</p> <p>We're excited to introduce <a href="http://blog.algorithmia.com/2016/07/cloud-hosted-deep-learning-models/" target="_blank">cloud hosted deep learning models</a> on Algorithmia. The <a href="https://algorithmia.com/algorithms/deeplearning/ColorfulImageColorization" target="_blank">Colorful Image Colorization microservice</a> is a <a href="https://algorithmia.com/blog/introduction-to-computer-vision" target="_blank">computer vision</a> algorithm trained on a million images from the Imagenet dataset.</p>- <p>This microservice is an implementation of the <a href="http://richzhang.github.io/colorization/" target="_blank">Colorful Image Colorization algorithm created by Richard Zhang, Phillip Isola, and Alexei A. Efros</a>.<!-- and <a href="#">how we built this demo</a>-->.</p>+ <p>This <a href="https://algorithmia.com/blog/introduction-to-microservices" target="_blank">microservice</a> is an implementation of the <a href="http://richzhang.github.io/colorization/" target="_blank">Colorful Image Colorization algorithm created by Richard Zhang, Phillip Isola, and Alexei A. Efros</a>.</p>
Since this is also linking to an external page, let's set rel="noopener noreferrer" for security purposes.
comment created time in 3 months