Add support for Liquid

Would love to see support for Liquid if possible: https://github.com/Shopify/liquid

Here's a Liquid example:

  {% for product in products %}

{{ product.name }}

      Only {{ product.price | price }}

      {{ product.description | prettyprint | paragraph }}

  {% endfor %}

It looks like ERB.
Using http://prettydiff.com/ (/cc @prettydiff) I think it works right now:
Input:

{% for product in products %}

{{ product.name }}

Only {{ product.price | price }}
{{ product.description | prettyprint | paragraph }}

{% endfor %}

Output:

    {% for product in products %}

{{ product.name }}

        Only {{ product.price | price }} {{ product.description | prettyprint | paragraph
            }}

    {% endfor %}

@hughker please play around with Pretty Diff's beautification at http://prettydiff.com/ and let me know if that does work. If so, then this could be added very soon.

@Glavin001 seems to work pretty well. I see some things are breaking onto another line such as shown in your example with the }} above the
 and with a few examples I tried. Better than nothing, that's for sure.

Great!
I am open to reviewing Pull Requests for adding this language and using Pretty Diff as the beautifier. See https://github.com/Glavin001/atom-beautify/blob/master/docs/add-languages-and-beautifiers.md#how-to-add-a-language for details, and let me know if anyone has any questions.

@hughker I am writing a new markup parser from scratch: http://prettydiff.com/ignore/testlocation/prettydiff.com.xhtml
That should provide superior support using half the code and execute 5x faster. Please let me know if you experience any bugs. The new parser is not released yet as I am still performing edge case testing.

@prettydiff the new markup parser works great! I used the same code sample provided by @Glavin001 and it provided the following code:

  {% for product in products %}

{{ product.name }}

    Only
    {{ product.price | price }}
    {{ product.description | prettyprint | paragraph }}

  {% endfor %}

Would the new parser still be able to integrate with this?

@hughker The new parser was released shortly after my prior comment. It should do everything you need.

+1 for liquid support!

+1 for liquid support

+1 for liquid support!

+1 for liquid support

You guys please try passing Liquid samples through http://prettydiff.com/?m=beautify and let me know if there are problems.  If this works well then I will write the pull request.

@prettydiff definitely! Thank you.

@prettydiff link to provide feedback/track issues?

@macdonaldr93 https://github.com/prettydiff/prettydiff/issues

@prettydiff awesome! I'll get the team here using it and we can get some feedback for you.

@prettydiff what code type have you found works best with liquid? I've tried html and ERB Template and they both seem to work pretty well.

@macdonaldr93 when I first opened this I tried ERB as well and it seemed to work the best IMO. I think I remember when I tested it out with more complex Liquid it seemed to have a tougher time. However, for the majority of the Liquid formatting it seems to do the trick.

@hughker sweet thanks! I'm going to keep testing and hopefully some other guys on the team will help out too so that we can get this into Atom Beautify.

Please feel free to open Pretty Diff issues for advanced defects.  If I am made aware of problems I can provide an opinion or resolution.  If I have no idea then it won't get any better.

@prettydiff I just want to confirm here that the intention of adding Liquid is to actually select Liquid as the language in Atom.

We're probably going to develop our own syntax hightlighting so it would be nice if this was in it's own language rather than improved the existing ERB Template.

@prettydiff I've added two issues. I will continue to log any issues with the Liquid:  prefix. Does that work for you?

Yes, a more specific language grammar would be ideal.  It would be less ideal to identify this as ERB in the case that support for these languages diverge into the future.
Yes, the liquid issue prefix will be very helpful... thank you.

Great! Well I'll continue testing on a daily basis. Look forward to getting this liquid beautifier and language added to Atom.

@prettydiff Thanks for your work on this!

Support added to Pretty Diff v1.16.28.

You rock!

@prettydiff just out of curiosity, when would you expect this to be added to Atom Beautify?

@macdonaldr93 : You can uninstall and reinstall Atom Beautify to trigger a fresh and up-to-date installation of Pretty Diff dependency.

@macdonaldr93 You don't need any special grammar to trigger support.  HTML grammar is good enough to get the full benefits.  It would be nice to specify Liquid so as to call out support, though.  The fastest way to get that though is to modify a couple files in Atom Beautify and submit a pull request.

@Glavin001 thanks! @prettydiff just to confirm though, the HTML grammar wouldn't be using the new Liquid Template code type though? That's where we'd have to add Liquid grammar to Atom Beautify?

@macdonaldr93 I only hide template features behind options and flags in the case of collisions.  In this case the {% and {{ are unique enough from HTML, JavaScript, and CSS syntax that there isn't any collision so regular HTML containing this code parses the same as HTML specific to Liquid.
The only exception is when one of the delimiters occurs inside a JavaScript string and is not complete, for instance: "some string {% liquid code".  This would cause a problem because it would attempt to parse and beautify the template code and insert the result back into that place in the string, but there is not a closing delimiter so the parser won't realize the string has finished before the Liquid code.  I have some bounds checking to compensate for this as necessary to prevent recursive errors in beautifying Pretty Diff code.

@prettydiff that would be invalid Liquid syntax anyway since it is compiled before any javascript can run.
+1 for everything you are doing :punch:

@rickydazla Pretty Diff has had some updates since my previous comment that may fix this and other issues.  Would you mind passing some code through the tool (http://prettydiff.com/) and let me know if quickly spot defects.

@prettydiff yes: :sparkles: b.e.a.u.t.i.f.u.l!

@prettydiff I did find an error when applying to a file of type .scss.liquid...
e.g. this:
margin: 0 {{ some_variable }}em;

.... became this:
  margin: 0{{some_variable}}em;

The removal of spacing in between the curly braces is ok (although not really necessary, I think it looks nicer with), but the removal of space after the zero is an obvious issue.

@rickydazla I opened a defect for that minor item.  I am currently away at a military school right now, so this weekend would be the earliest I could get to it.  I have opened A LOT of issues since yesterday (first time being back online in 5 weeks), so I will get to it as quickly as I can.

Do what you gotta do brother man, I'll be sitting here writing fugly code!

Any clear instructions on how to add .LIQUID support? I don't see a Liquid option...

Instructions on adding a new language (such as Liquid) can be found at https://github.com/Glavin001/atom-beautify/blob/master/docs/add-languages-and-beautifiers.md#how-to-add-a-language
Let me know if you have any questions! Feel free to submit a Pull Request earlier than later so we can discuss changes, etc. Thanks in advance!

I am closing this issue as Liquid support is long since added to Pretty Diff.  Please follow the guidance from Glavin for extending language support in Atom Beautify.

Pull Requests welcome!

It's been a while since anyone has made comment on this. Is this still being worked on? I'm having formatting issues as described above.
The frontmatter is getting inlined as mentioned on issue #261. Liquid tags are also breaking as shown below:
Input Before Beautification

        {% regionblock about_quote, type: text %}

Some paragraph text.

    {% endregionblock %}
      {% regionblock about_image, type: image %}

     {% endregionblock %}

Expected Output

    {% regionblock about_quote, type: text %}

Some paragraph text.

    {% endregionblock %}
    {% regionblock about_image, type: image %}

    {% endregionblock %}

Output Using JS Beautify

    {% regionblock about_quote, type: text %}

Some paragraph text.

    {% endregionblock %} {% regionblock about_image, type: image %}
     {% endregionblock %}

Output Using Pretty Diff

    {% regionblock about_quote,
    type: text %}

Some paragraph text.

    {% endregionblock %}
    {% regionblock about_image,
    type: image %}

    {% endregionblock %}

I realize these are custom tags, but it would seem anything inside the {% %} tags would be unformatted.
Also, the above is only if I highlight the single section. When I try to beautify the entire file with frontmatter present, Pretty Diff errors:
Cannot convert undefined or null to object

TypeError: Cannot convert undefined or null to object
    at Function.keys (<anonymous>)
    at markuppretty__beautify_apply_attArray (/home/brad/.atom/packages/atom-beautify/node_modules/prettydiff2/lib/markuppretty.js:3349:47)
    at markuppretty__beautify_apply (/home/brad/.atom/packages/atom-beautify/node_modules/prettydiff2/lib/markuppretty.js:3367:34)
    at markuppretty__beautify (/home/brad/.atom/packages/atom-beautify/node_modules/prettydiff2/lib/markuppretty.js:3479:20)
    at Object.markuppretty_ [as markuppretty] (/home/brad/.atom/packages/atom-beautify/node_modules/prettydiff2/lib/markuppretty.js:3480:10)
    at core__markuppretty (/home/brad/.atom/packages/atom-beautify/node_modules/prettydiff2/prettydiff.js:77:30)
    at core_ (/home/brad/.atom/packages/atom-beautify/node_modules/prettydiff2/prettydiff.js:307:37)
    at prettydiff_ (/home/brad/.atom/packages/atom-beautify/node_modules/prettydiff2/prettydiff.js:334:16)
    at commonjs_prettydiff (/home/brad/.atom/packages/atom-beautify/node_modules/prettydiff2/prettydiff.js:369:20)
    at /home/brad/.atom/packages/atom-beautify/src/beautifiers/prettydiff.coffee:128:16
    at Promise._execute (/home/brad/.atom/packages/atom-beautify/node_modules/bluebird/js/release/debuggability.js:303:9)
    at Promise._resolveFromExecutor (/home/brad/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:483:18)
    at new Promise (/home/brad/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:79:10)
    at PrettyDiff.module.exports.PrettyDiff.beautify (/home/brad/.atom/packages/atom-beautify/src/beautifiers/prettydiff.coffee:75:16)
    at /home/brad/.atom/packages/atom-beautify/src/beautifiers/index.coffee:355:28
    at tryCatcher (/home/brad/.atom/packages/atom-beautify/node_modules/bluebird/js/release/util.js:16:23)
    at Promise._settlePromiseFromHandler (/home/brad/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:512:31)
    at Promise._settlePromise (/home/brad/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:569:18)
    at Promise._settlePromiseCtx (/home/brad/.atom/packages/atom-beautify/node_modules/bluebird/js/release/promise.js:606:10)
    at Async._drainQueue (/home/brad/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:138:12)
    at Async._drainQueues (/home/brad/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:143:10)
    at Async.drainQueues (/home/brad/.atom/packages/atom-beautify/node_modules/bluebird/js/release/async.js:17:14)

I've created a Gist of the full file if it's helpful.
Software Versions
OS
Linux (Ubuntu 17.10)
$ uname -r
4.13.0-21-generic

Atom
$ atom -v
Atom    : 1.22.1
Electron: 1.6.15
Chrome  : 56.0.2924.87
Node    : 7.4.0

Atom-Beautify
0.30.9


Support arithmetic expressions in COUNT()

tl;dr:
Following is now allowed (example):
SELECT COUNT(DISTINCT CONCAT(u.name, u.surname)) FROM User u

I am not aware of RDBMS implementations that do not support this. Ping @guilhermeblanco

@Ocramius see http://www.doctrine-project.org/jira/browse/DDC-3340 for an issue about this


Fixes concerning RELX_REPLACE_OS_VARS

only replace variables when RELX_REPLACE_OS_VARS=true
use sys.config with processed variable substitutions instead
of fresh sys.config from release folder
overwrite old sys.config and vm.args from
${RELEASE_MUTABLE_DIR}/running-config with the processed files
instead of using copies which are not compatible in their
naming with OTP.

The last fix in particular solves an issue where changes in the
.conf file of the release folder are only honored after the
SECOND start of the release.
See also

erlang/rebar3#731
erlware/relx@447df92

Hey @bitwalker, to be honest i cannot fully explain the part with honoring .conf file changes after the second start. Do you have some idea?

And I have another question: I just tried to build in env variables into my config.exs and I could see that the sys.config in running-config already contains the substituitons. This means that variable substitution isn't done at all by exrm? Is relx doing it?

@GalaxyGorilla Sorry it's taken me awhile to get to this, I have finite time, and most of that is focused on distillery these days.
The $RELEASE_MUTABLE_DIR in exrm is different than in distillery, and it's weird in exrm. In distillery, it is where all generated or temporary files go (such as logs, pipes, generated configs, etc.), and is not intended to be modified by hand. In exrm however, the generated configs are considered hand-editable, and is generally why things are so messed up. Exrm will not overwrite the generated sys.config or vm.args, with the exception of conform, which currently appears to always overwrite sys.config when it runs, which is probably why the "second run" problem exists. To be honest though, I no longer know what behaviour various people using exrm rely on, so I have been hesitant to touch it at all.
The problem with changing the way these work (with the exception of the "second run" bug imo, and issues with the relx env var replacements), is that exrm has been around long enough, and enough varieties of use cases exist, that making changes always ends up breaking something for someone. One of the major motivations for distillery was in fact a revamping of how this works so that there is a much clearer separation between generated configs and hand-edited ones.

@bitwalker No problem, I really appreciate that you do all this stuff :)
I was already experimenting with distillery and it feels a lot more mature than exrm already. If you don't want to do any more changes in exrm then I am fine with this and switch to distillery soon. Still thanks for the explanation!


Google location permission does not enable,  could not able to fetch even google map

Describe the bug
Hello Team / Everyone,
I am facing an issue after I incorporated next-safe code script in next.config js
Objective is -> post image & files to aws s3, fetch image & files from aws s3,  using googles geocode api, geolocation api, directions api, showing google maps in frontend, using redis , using mongodb
getting all issues in production website @ aws EC2
issues -> location permission auto disabled though location is working fine. All geocode , geolocation related functions are giving error and  navigator.geolocation.getCurrentPosition does not provide correct latitude and longitude
Code as below
const nextSafe = require('next-safe')
const isDev = process.env.NODE_ENV !== 'production'
async headers() {
return [
{
source: '/(.)',
headers: nextSafe({
contentTypeOptions: "nosniff",
contentSecurityPolicy: {
"base-uri": "'none'",
"child-src": "'none'",
"connect-src": ["'self'","googleapis.com","google.com","gstatic.com","webpack://"],
"default-src": "'self'",
"font-src": ["'self'","fonts.gstatic.com"],
"form-action": "'self'",
"frame-ancestors": "'none'",
"frame-src": "'none'",
"img-src": ["'self'","amazonaws.com","cloudinary.com", "googleapis.com","gstatic.com","google.com","googleusercontent.com"],
"manifest-src": "'self'",
"media-src": ["'self'","amazonaws.com"],
"object-src": "'none'",
"prefetch-src": "'self'",
"script-src": ["'self'","unsafe-eval","googleapis.com","gstatic.com","google.com","ggpht.com","googleusercontent.com"],
"style-src": ["'self'","fonts.googleapis.com","'unsafe-inline'"],
"worker-src": "'self'",
mergeDefaultDirectives: false,
reportOnly: false,
},
frameOptions: "DENY",
permissionsPolicy: {},
permissionsPolicyDirectiveSupport: ["proposed", "standard","experimental","legacy"],
isDev: false,
referrerPolicy: "no-referrer",
xssProtection: "1; mode=block",
   })

},
Steps To Reproduce

Create new Next.js app
Setup next-safe:code example

Start app
See error

Version
v3.x.x
Relevant log output
log output-> Finally tried to find errors in local console after turning isDev to true.

API resolved without sending a response for /api/geocoding/geo-location?lat=&lon=, this may result in stalled requests.
OperationalError: Status is INVALID_REQUEST. Invalid request. Invalid 'latlng' parameter.
    at D:\Projects\cyain\node_modules\node-geocoder\lib\geocoder\googlegeocoder.js:325:11
From previous event:
    at Geocoder.<anonymous> (D:\cyain\slchain\node_modules\node-geocoder\lib\geocoder.js:46:23)
    at process.processImmediate (node:internal/timers:476:21)
From previous event:

Code of Conduct

[X] I agree to follow this project's Code of Conduct

This looks like a problem with your implementation of the Google library you are using.
Invalid request. Invalid 'latlng' parameter.


Curation Doubt on GO:0008656

Hi,
I have a curation doubt on GO:0008656 cysteine-type endopeptidase activator activity involved in apoptotic process:
Definition: "Increases the rate of proteolysis catalyzed by a cysteine-type endopeptidase involved in the apoptotic process."
Comments: "Examples of this are 1) granzymes that may bind to initiator caspases and cleave them, and 2) already active caspases, e.g. caspase 9, that cleave effector caspases."
I have a complex, called PIDDosome whose components are 7xCASP2:7xCRADD:5xPIDD1 and whose functions is to allow pairs of CASP2 subunits to self-cleave to release a processed and functional Caspase-2. I was wondering whether I can annotate this complex with the GO:0008656 function.
Thanks in advance
Kindest regards
Livia
@bmeldal

Thanks, David. It was actually I who had doubts. Should we add a further comment that self-activation is also applicable for this term?
Would you still co-annotate with the direct term
GO:0097153 cysteine-type endopeptidase activity involved in apoptotic process?
I guess so.

Hi @bmeldal
GO terms don't specify the substrate, only the gene product that mediates the activity. So acting on itself is fine. I can add something to the definition, but we cannot be exhaustive relative to possible substrates. I a little reluctant to add just because then, do we want to add this to all known cases ? (protein kinases seem a good example of this)
What do you think ?
Thanks, Pascale

I was doubting if we did the right thing as the term has comments with examples that didn't quite fit the selfactivation situation; it mentions caspases that activate other caspases rather than themselves. Maybe I'm just too cautious. The PIDDosome is a bit of a nightmare to de-tangle, tbh.

@bmeldal @liviap Can you send the paper you are annotating ?

I think self activation doesn't just hang on this term. I think it is generally applicable as legitimate MF. @vanaukenk, @thomaspd  and @pgaudet do you agree in light of the MF refactoring? Should this be moved to the annotation tracker? It seems like more an annotation practice question than an ontology question.

I think it's in this paper: PMID:15073321
Yes, should be in Annotation tracker.

This issue was moved to geneontology/go-annotation#2133


KAFKA-6628: RocksDBSegmentedBytesStoreTest does not cover time window serdes

Updated RocksDBSegmentedBytesStoreTest class to include time window serdes

\cc @bbejeck @vvcephei

This would be covered by RocksDBWindowStoreTest, WindowKeySchemaTest etc

@dguy Does that means this ticket(KAFKA-6628) is redundant ?

It seems so to me, but I'll leave it to @guozhangwang to decide as he raised the ticket

I think the functionality of RocksDBSegmentedBytesStore, or more generally speaking, RocksDBSegmentedBytesStore + Segments + SegmentIterator is independent of the key schemas that is used. But the test coverage of these three could arguably be a bit redundant between RocksDBSegmentedBytesStoreTest, SegmentsTest and SegmentIteratorTest.
I'd suggest we still keep this test class along with the other two above, especially as I'm working on https://github.com/apache/kafka/pull/4576 which would have high dependency on RocksDBSegmentedBytesStore to trigger the correct calls on the key schemas / segments classes.

@lijubjohn are you still working on this PR?

@guozhangwang Didn't get time this week to incorporate your review comments. Hopefully will complete by next week. If it is urgent then please feel to reassign it to others

No worries :) please take your time, just double checking if you are still taking on it.

@guozhangwang Too late but finally got some time to incorporate your review comments


Cow: Watch maha66.org

Cow requests the watch of the watch_keyword maha66\.org. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

maha66\.org has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by double-beep in Charcoal HQ


Use a 2-letters ISO 3166 country code, as required by RFC 2459

Hi there,
In order to fix cloudfoundry/bosh#2473 and cloudfoundry/bosh-cli#632, here is a small patch so that the generated certificates have a valid 2-letters ISO 3166 country code, as required by RFC 2459 in Appendix A.
I’ve also written some short instructions for running unit and integration tests, based on my experience doing it today. About golangci-lint, I also wonder if this installation code is still relevant :
https://github.com/cloudfoundry/config-server/blob/master/bin/lint#L6-L11
Indeed, this way of doing is no more recommended, see https://golangci-lint.run/usage/install/#install-from-source, and I’ve not been able to run golangci-lint this way.
Cheers

DO NOT MERGE!! We first need to figure out a way to roll out these changes without breaking director ← NATS → agent communication: https://github.com/cloudfoundry/bosh/blob/main/src/bosh-nats-sync/lib/nats_sync/nats_auth_config.rb#L32C1-L43C8

On-going discussion in #2473.


Module not accept typescript path alias

Environment

Operating System: Linux
Node Version:     v16.14.0
Nuxt Version:     3.0.0-27498764.32c798c
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      typescript, buildModules, components, windicss, autoImports, router, experimental, features, globalName, build, vite, loading, cli, alias, privateRuntimeConfig, publicRuntimeConfig, css
Runtime Modules:  -
Build Modules<EMAIL_ADDRESS><EMAIL_ADDRESS>~/modules/test.ts

Reproduction

create new fresh nuxt
create new file lib/test.ts

export const testLib = {
  ok: true,
};

create new file modules/test.ts

import { defineNuxtModule } from '@nuxt/kit';
import { testLib } from '~~/lib/test';

export default defineNuxtModule({
  setup() {
    console.log('module inited');
    console.log(testLib);
  },
});

input module into nuxt.config.js

import { defineNuxtConfig } from 'nuxt3';

export default defineNuxtConfig({
  modules: ['~~/modules/test.ts'],
});

run project and see error not found file lib from ~~/lib...
Describe the bug
This is repo test
https://stackblitz.com/edit/github-fjh4sx-bfb1gj?file=nuxt.config.ts
Additional context
No response
Logs
No response

I have a similar issue here, but it comes from using local modules, iterating through the file system and importing/binding to an event.
<!-- modules/discord/index.ts -->
 const dir = resolve(nuxt.options.serverDir, "discord/events");
      const events = await new fdir()
        .glob("./**/*.js", "./**/*.ts", "./**/*.mjs")
        .withFullPaths()
        .withMaxDepth(1)
        .crawl(dir)
        .withPromise();

      if (events.length) {
        logger.info("Setting up events:");

        for (const event of events) {
          try {
            const e: DiscordEvent = await import(event);

            if (e.once) {
              client.once(e.name, (...args) => e.execute(...args));
            } else {
              client.on(e.name, (...args) => e.execute(...args));
            }
            logger.success(`Loaded: ${e.name}`);
          } catch (err) {
            logger.error(err);
            break;
          }
        }
      }

I scan ./server/discord/events and bind them to the discord client.
each event listener/handler is a file with similar structure:
<!-- server/discord/events/onReady.ts -->
import { Events, Role } from "discord.js";
import { defineDiscordEventHandler } from "../../../modules/discord/runtime/server/utils"; <-- works
import { usePrisma } from "../../../server/services/usePrisma"; <-- works. BUT if I have another module inside using an alias it will throw an error.

however this doesn't work:
import { defineDiscordEventHandler } from "#discord" <-- module is type defined and "works", but since it;s imported into the module during compilation it will throw an error saying the module cannot be found.

export default defineDiscordEventHandler(
  Events.ClientReady,
  true,
  async (client) => {
    const guilds = client.guilds.cache;

    const prisma = usePrisma();
    /**
     * grab pre-existing roles from the database and see if we need to add more.
     */
    const result = await prisma.discordRole.findMany();

    const rolesMapped = result.map(({ roleId }) => roleId);

    /**
     * grab the roles from the discord server (guild) and filter out them out if they already exist in the database.
     */
    const roles = guilds
      .flatMap((guild) => guild.roles.cache)
      .reduce((arr: { roleId: string; name: string }[], role: Role) => {
        if (!rolesMapped.includes(role.id)) {
          arr.push({ roleId: role.id, name: role.name });
        }
        return arr;
      }, []);

    /**
     * if there are no roles to be needed we just exit out.
     */
    if (!roles.length) return;

    try {
      await prisma.discordRole.createMany({
        data: roles,
      });
    } catch (err: any) {
      throw new Error(err);
    }
  }
);

What is a good alternative to preserving the aliases in a local module?

Any plan to support alias in the future?


06/01 Added Map class

Added Map class to contain all blocks
Removed most code concerning blocks out from the rest of the code

 Level 1


Bootstrap predefinitions for user roles

At the Moment, after a new GOKb installation you have to edit the rights manually. This should be done in the Bootstrap.groovy according to this template: https://docs.google.com/document/d/1wxvLuwmaZyXwlE-SDO6JRHQ2hnLMosiZGykFmdMODUo/edit#heading=h.tfwkt66ewl10

Added in #78


error deploying chaincode at node startup

on a local single node setup, I get this error:
	 deploy resp error - there is no chaincode hash name in response: { jsonrpc: '2.0',
  error:
   { code: -32001,
     message: 'Deployment failure',
     data: 'Error when deploying chaincode: Error getting chaincode package bytes: Error getting code Getting chaincode took too long' },
  id:<PHONE_NUMBER>587 }
! looks like a deploy error, holding off on the starting the socket
 { name: 'deploy() error no cc name',
  code: 502,
  details:
   { jsonrpc: '2.0',
     error:
      { code: -32001,
        message: 'Deployment failure',
        data: 'Error when deploying chaincode: Error getting chaincode package bytes: Error getting code Getting chaincode took too long' },
     id:<PHONE_NUMBER>587 } }

do you know if this network is setup correctly? have you deployed other chaincode on this network before, such as example02?
you will likely need to look at the logs in the peer to see the root cause getting code Getting chaincode took too long. could be a networking problem or bad deployment parameters,

I can deploy example02.
Here are the logs:
17:51:15.201 [rest] Register -> INFO 530 REST client login...
17:51:15.202 [rest] Register -> INFO 531 Local data store for client loginToken: /var/hyperledger/production/client/
17:51:15.202 [rest] Register -> INFO 532 User 'bob' is already logged in.
17:51:22.854 [rest] ProcessChaincode -> INFO 533 REST processing chaincode request...
17:51:22.854 [rest] processChaincodeDeploy -> INFO 534 REST deploying chaincode...
17:51:22.855 [rest] processChaincodeDeploy -> INFO 535 Local user 'bob' is already logged in. Retrieving login token.
17:51:22.855 [devops] getChaincodeBytes -> DEBU 536 Received build request for chaincode spec: type:GOLANG chaincodeID:<path:"http://gopkg.in/ibm-blockchain/marbles.v2/chaincode" > ctorMsg:<args:"init" args:"99" > secureContext:"bob"
17:51:22.855 [golang/hash] getCodeFromHTTP -> DEBU 537 getCodeFromHTTP gopkg.in/ibm-blockchain/marbles.v2/chaincode
17:51:22.856 [golang/hash] getCodeFromHTTP -> DEBU 538 go get gopkg.in/ibm-blockchain/marbles.v2/chaincode
17:51:42.167 [peer] ensureConnected -> DEBU 539 Touch service indicates no dropped connections
17:51:42.167 [peer] ensureConnected -> DEBU 53a Connected to: []
17:51:42.167 [peer] ensureConnected -> DEBU 53b Discovery knows about: []
17:51:52.861 [devops] getChaincodeBytes -> ERRO 53c Error getting chaincode package bytes: Error getting code Getting chaincode took too long
17:51:52.862 [devops] Deploy -> ERRO 53d Error deploying chaincode spec: type:GOLANG chaincodeID:<path:"http://gopkg.in/ibm-blockchain/marbles.v2/chaincode" > ctorMsg:<args:"init" args:"99" > secureContext:"bob"

 error: Error getting chaincode package bytes: Error getting code Getting chaincode took too long
17:51:52.862 [rest] processChaincodeDeploy -> ERRO 53e Error when deploying chaincode: Error getting chaincode package bytes: Error getting code Getting chaincode took too long
17:51:52.862 [rest] ProcessChaincode -> INFO 53f REST successfully deploy chaincode: {"jsonrpc":"2.0","error":{"code":-32001,"message":"Deployment failure","data":"Error when deploying chaincode: Error getting chaincode package bytes: Error getting code Getting chaincode took too long"},"id":1484761882851}
17:56:43.169 [peer] ensureConnected -> DEBU 540 Touch service indicates no dropped connections
17:56:43.169 [peer] ensureConnected -> DEBU 541 Connected to: []
17:56:43.169 [peer] ensureConnected -> DEBU 542 Discovery knows about: []

try bumping up deploytimeout to 120000

That would mean rebuilding the whole docker image...

you can increase it by passing environment variable CORE_CHAINCODE_DEPLOYTIMEOUT=120000. You don't need to rebuild the image

the env variable setup worked but it is still timing out.
I tried to run the go get command directly from my computer, and after a very long time (like 2mn, I got this error)
$ go get gopkg.in/ibm-blockchain/marbles.v2/chaincode

# gopkg.in/ibm-blockchain/marbles.v2/chaincode
go/src/gopkg.in/ibm-blockchain/marbles.v2/chaincode/marbles_chaincode.go:67: cannot use new(SimpleChaincode) (type *SimpleChaincode) as type shim.Chaincode in argument to shim.Start:
	*SimpleChaincode does not implement shim.Chaincode (wrong type for Init method)
		have Init(shim.ChaincodeStubInterface, string, []string) ([]byte, error)
		want Init(shim.ChaincodeStubInterface) ([]byte, error)

go version
go1.7.4 darwin/amd64

you have mismatching hyperledger versions. since you are using the branch v2.0 you should have hyperledger fabric v0.6.x.  If you have 0.7.x or 0.5.x fabric it will not work b/c they changed the chaincode stub interfaces.

I guess I too hit upon this issue..
cache busting hash js 5f0791a56911bb2a730efb972c0441ce css 5c5213ec16de93e801c4aaf7a7eb956b
------------------------------------------ Server Up - localhost:3000 ------------------------------------------
Running using Developer settings

Tracking Deployment
loading hardcoded peers
loading hardcoded users
[ibc-js] Peer:  vp0-vp0...:7050
[ibc-js] Registering  vp0-vp0...:7050  w/enrollId - bob
[ibc-js] Registration success x1 : bob
[ibc-js] removing temp dir
[ibc-js] Downloading zip
redirect... https://codeload.github.com/IBM-Blockchain/marbles/zip/v2.0
[ibc-js] Downloading zip
[ibc-js] Unzipping zip
[ibc-js] Unzip done
[ibc-js] Scanning files [ 'marbles_chaincode.go' ]
[ibc-js] Parsing file for shim version
[ibc-js] Found shim version: github.com/hyperledger/fabric/core/chaincode/shim
[ibc-js] Parsing file for invoke functions - marbles_chaincode.go
[ibc-js] Found cc invoke function:  init
[ibc-js] Found cc invoke function:  delete
[ibc-js] Found cc invoke function:  write
[ibc-js] Found cc invoke function:  init_marble
[ibc-js] Found cc invoke function:  set_user
[ibc-js] Found cc invoke function:  open_trade
[ibc-js] Found cc invoke function:  perform_trade
[ibc-js] Found cc invoke function:  remove_trade
[ibc-js] Parsing file for query functions - marbles_chaincode.go
[ibc-js] Found cc query function:  read
[ibc-js] load_chaincode() finished
[ibc-js] Deploy Chaincode - Starting
[ibc-js] 	function: init , arg: [ '99' ]
Waiting...
deploy resp error - there is no chaincode hash name in response: { jsonrpc: '2.0',
error:
{ code: -32001,
message: 'Deployment failure',
data: 'Error when deploying chaincode: Error getting chaincode package bytes: Error getting code Getting chaincode took too long' },
id:<PHONE_NUMBER>810 }
! looks like a deploy error, holding off on the starting the socket
{ name: 'deploy() error no cc name',
code: 502,
details:
{ jsonrpc: '2.0',
error:
{ code: -32001,
message: 'Deployment failure',
data: 'Error when deploying chaincode: Error getting chaincode package bytes: Error getting code Getting chaincode took too long' },
id:<PHONE_NUMBER>810 } }

The hyperledger fabric version is v0.6.1-preview. I also tested the Rest calls to Query Chaincode and it returns fine.

did you try the solutions in this thread yet?
you can increase it (the timeout) by passing environment variable CORE_CHAINCODE_DEPLOYTIMEOUT=120000. You don't need to rebuild the image

or
try bumping up deploytimeout https://github.com/hyperledger/fabric/blob/v0.6/peer/core.yaml#L314 to `120000`

none of these commands solve the issue on my side

These commands do not work for me too.
Sent from Yahoo Mail on Android
On Wed, Feb 1, 2017 at 8:28 PM, Vincent<EMAIL_ADDRESS>wrote:
none of these commands solve the issue on my side
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

well they aren't commands. the first one is an environmental variable you should set. the command would be export CORE_CHAINCODE_DEPLOYTIMEOUT=500000.
and the 2nd method is to change the .yaml file and rebuild.
i'm also going to suggest bumping it up even farther to 500 seconds.  time it yourself to make sure your setting is actually getting applied. You could also time how long it takes to clone marbles locally and set your timeout to 1.5 times that.

I could get this working by adding CORE_CHAINCODE_DEPLOYTIMEOUT=1000000. That was a random number I selected.

bumping the timeout worked for me. Thanks


iOS build error!

Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.0.4, on Mac OS X 10.15.6 19G2021 darwin-x64,
locale zh-Hans-CN)
[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
✗ Android license status unknown.
Run flutter doctor --android-licenses to accept the SDK licenses.
See https://flutter.dev/docs/get-started/install/macos#android-setup for
more details.
[!] Xcode - develop for iOS and macOS
! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
CocoaPods is used to retrieve the iOS and macOS platform side's plugin
code that responds to your plugin usage on the Dart side.
Without CocoaPods, plugins will not work on iOS or macOS.
For more info, see https://flutter.dev/platform-plugins
To upgrade see
https://guides.cocoapods.org/using/getting-started.html#installation for
instructions.
[✓] Chrome - develop for the web
[✓] Android Studio (version 4.1)
[✓] Connected device (2 available)
/Users/test1/klapp/aaa/flutter_app1/ios/Pods/ScanKitFrameWork/scansdk-ios-tool-<IP_ADDRESS>0/ScanKitFrameWork.framework/ScanKitFrameWork' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. file '/Users/test1/klapp/aaa/flutter_app1/ios/Pods/ScanKitFrameWork/scansdk-ios-tool-<IP_ADDRESS>0/ScanKitFrameWork.framework/ScanKitFrameWork' for architecture arm64

@mrstluo
Perhaps you should heed the prompt message that reports the error and disable the bitcode. The reason for this error is probably because the HUAWEI ScanKit SDK does not provide bitcode support.
You can see this setting in the "Build Settings" -> "Enable Bitcode" option. Just set it to NO

i try set 'Enable Bitcode" to NO, bug the problem has not been solved
It can be solved by the following method:
post_install do |installer|
  installer.pods_project.targets.each do |target|
    flutter_additional_ios_build_settings(target)
    #start
    target.build_configurations.each do |config|
      config.build_settings['ENABLE_BITCODE'] = 'NO'
    end
   #end
  end
end


No 'VIA' in the Outlook web app when the (spoofed) address is an office 365 group.

We have executed a phishing test in our company. The sender spoofed the sending email as<EMAIL_ADDRESS>At our company, we have an office 365 group called 'IT' (IT@contoso.com).
The signs to check for a spoofed message are described here.
In Outlook Desktop, I can clearly see that the email is being spoofed (as described in the documentation):

However, in OWA, the spoofed address is shown as being the O365 group, and there is no hint that the sender was spoofed:

It actually looks very legit.
Is this expected behavior? Is there another way that my users can see the address is being spoofed (except for looking at the headers in the message details)?
Thanks,

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

ID: e130b60f-b97b-cfb1-4857-a08e79fdfd59
Version Independent ID: 19e405c4-a6c0-7c75-b925-ff9637f1889e
Content: Anti-spoofing protection - Office 365
Content Source: microsoft-365/security/office-365-security/anti-spoofing-protection.md
Service: o365-seccomp
GitHub Login: @chrisda
Microsoft Alias: chrisda

@w0ut0 Thank you for your feedback. This is not the expected behavior. I tested it and it does not look like this and shows the original email address in brackets both in outlook and OWA.
I'd recommend you contact the support team via the Need help button on the admin center and report/troubleshoot this as there could be a bug. After troubleshooting, if you feel there is a modification needed in the document, let us know so that we can verify and make the changes.
@yogkumgit Please close the issue as there is no changes needed.
Thanks
Sri

@w0ut0, definitely open a a support case, which will get the attention of the product team. I'm told that it's supposed to work in OWA.

@msbemba  Thank you very much for the contribution and sharing this explanation. @w0ut0 Hope this comment is helpful for you. Considering the nature of the issue, as advised, please open a service ticket in your tenant and follow with them for the resolution. We proceed here to close it.
We will be very happy if you can share the outcome or resolution with us if you see documentation update is required. We will certainly update this documentation with that valuable information. Thanks again, for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

Thank you all for your feedback @msbemba @chrisda @yogkumgit, I opened the support case (office 365 support #21395898).
The support agent escalated the issue and got back to me with the message that OWA is not designed to show the 'via' address on spoofed emails??
`Hello Wout,
Thank you for your time and patience with us.
As informed, OWA will not show up the information as showing in the Outlook Desktop by product design.
We are sharing the Product Feedback link with you, so that you can provide your feedback regarding the issue and feature:
We appreciate your opinions and recommendations on Office 365 products as a valued customer. The feedback that our customers submit are logged and read by our development team. The more times that certain features or issues are submitted the higher chance of it getting added or fixed in the next release
http://office365.uservoice.com/
As discussed, we will be archiving this case for now and feel free to write back to us for any query or concerns and we will be glad to assist you further.
`
In my opinion, this is a very strange reaction, no? According to the documentation, it should be supported.
I will follow up with the support case.

Update, the documentation I supplied, only applies to Outlook on the web Outlook.com Outlook on the web for Exchange Server 2016. Not to office 365 OWA.
The functionality is not supported, I created a uservoice suggestion:
https://office365.uservoice.com/forums/289138-office-365-security-compliance/suggestions/41192461-show-the-via-option-for-spoofed-email-adresses
There is already an existing suggestion to stop linking spoofed adresses to group/user images: https://office365.uservoice.com/forums/264636-general/suggestions/35657518-stop-automatically-linking-user-profile-pictures-w)


Increase build timeout to 120 minutes.

Description
An attempt to mitigate some of the recent timeout-related pipeline failures.

@rajatch-ff ADO:6680 should cover this


Make the TBRM tests work

This subsumes PR #34731

Implement the PanChange feature in the network-manager example app
Fix various small issues in YAML tests 2.2 and  and 2.3
Incorporate the test for armed failsafe (2.4) into 2.2
Remove test 2.5 (setting SetPendingDataset does not require failsafe as per spec)

The test plan will need to be updated to reflect these tweaks.

Verified the tests on my DUT and they work as expected.

The test plan is updated to ensure consistency : https://github.com/CHIP-Specifications/chip-test-plans/pull/4307/commits/caeed0c5004734321458bf85a890af64a2d08abe


Fix notification policy bug

Low Urgency alarm occurs even when Notification Policy is set to High Urgency.

This is related PR information.
[Monitoring]
https://github.com/cloudforet-io/monitoring/pull/22


Lzhan55/ase enum mmio test

Added enumeration and mmio tests.
These tests are mostly negative tests. ASE's coverage tests need to run some sample tests.

@michael-adler Can you see it now?


pact-mock-service is not found when run in docker container node:v10.15.3

Software versions

OS: docker node:10.15.3
Library version: 9.0.4
node: v10.15.3

Expected behaviour
Pact provider initialised and tests are started .
Actual behaviour
[2019-09-16T10:13:01.237Z] ERROR<EMAIL_ADDRESS>on 452dacd35513:
    Pact Binary Error: /bin/sh: 1: ./standalone/linux-x64-1.70.2/bin/pact-mock-service: not found

Steps to reproduce
Run consumer side contract tests in docker container using image node:10.15.3
NB: Everything works fine on version 9.0.3.

Can you please provide a repro for this?
I've seen this issue before when the node modules from a different host (e.g. Mac OSX) are volume mounted into the container. It should work just fine with Node 10

@mefellows
here is an example of test
const { Pact, Matchers } = require('@pact-foundation/pact');
const path = require('path');
const axios = require('axios');

const SERVICE_NAME = 'service-provider';

describe('When service is our Provider', () => {
    let provider;

    beforeAll(async () => {
        const options = {
            provider: SERVICE_NAME,
            consumer: 'service-consumer',
            log: path.resolve(__dirname, './logs', `pact-${SERVICE_NAME}.log`),
            dir: path.resolve(__dirname, './contracts'),
            logLevel: process.env.LOG_LEVEL || 'WARN',
            spec: 2,
            port: 9090,
        };
        provider = new Pact(options);

        await provider.setup();
    });

    afterEach(async () => {
        await provider.verify();
    });

    afterAll(async () => {
        await provider.finalize();
    });

    test('returns 200 from our service with the right response body', async () => {
        await provider.addInteraction({
            uponReceiving: 'a POST request to /v1/user',
            withRequest: {
                method: 'POST',
                path: '/v1/user',
                headers: {
                    // "Content-Type": "application/json;charset=utf-8",
                },
                body: {
                    name: Matchers.string('Alice'),
                    age: Matchers.string('13'),
                },
            },
            willRespondWith: {
                status: 200,
                headers: { 'Content-Type': 'application/json; charset=utf-8' },
                body: {
                    name: Matchers.string('Alice'),
                    id: Matchers.string('12312313'),
                },
            },
        });
        const { data: body } = await axios.post('http://localhost:9090/v1/user', {
            name: 'Alice',
            age: '13',
        });
        expect(body.name).toBe('Alice');
    });
});

Install pact node of version 9.0.4 =>  npm install<EMAIL_ADDRESS>start container mounting local dir

docker run  -it -v "$(pwd)"/:/tmp node:10.15.3 /bin/bash

Inside container:

root@d5090416df14:/# cd /tmp/
root@d5090416df14:/tmp# npm run pact:contract

><EMAIL_ADDRESS>pact:contract /tmp
> CONFIG_ENV=pact NODE_ENV=pactTest jest --testMatch '**/test/pact/**/service.test.pact.js' --runInBand

[2019-09-16T13:58:12.573Z]  INFO<EMAIL_ADDRESS>on d5090416df14:
    Creating Pact Server with options:
    {"consumer":"service-consumer","cors":false,"dir":"/tmp/test/pact/contracts","host":"<IP_ADDRESS>","log":"/tmp/test/pact/logs/pact-service-provider.log","pactFileWriteMode":"overwrite","port":9090,"provider":"service-provider","spec":2,"ssl":false}
[2019-09-16T13:58:12.594Z] DEBUG<EMAIL_ADDRESS>on d5090416df14: Starting pact binary with '/bin/sh,-c,./standalone/linux-x64-1.70.2/bin/pact-mock-service service --consumer 'service-consumer' --pact_dir '/tmp/test/pact/contracts' --host '<IP_ADDRESS>' --log '/tmp/test/pact/logs/pact-service-provider.log' --pact-file-write-mode 'overwrite' --port '9090' --provider 'service-provider' --pact_specification_version '2',{"cwd":"/tmp/node_modules/@pact-foundation/pact-node","detached":true,"env":{"npm_config_cache_lock_stale":"60000","npm_config_ham_it_up":"","npm_package_scripts_swagger_mock_validator":"./node_modules/swagger-mock-validator/bin/swagger-mock-validator","npm_package_dependencies_read_pkg_up":"^4.0.0","npm_config_legacy_bundling":"","npm_config_sign_git_tag":"","npm_package_devDependencies_eslint_plugin_security":"^1.4.0","npm_package_devDependencies_jest":"^24.9.0","npm_config_user_agent":"npm/6.4.1 node/v10.15.3 linux x64","npm_config_always_auth":"","NODE_VERSION":"10.15.3","npm_package_devDependencies__stryker_mutator_jest_runner":"^2.0.2","npm_package_devDependencies_crypto":"^1.0.1","npm_package_bugs_url":"https://github.com/getndazn/service-dcb-web-api/issues","npm_config_bin_links":"true","npm_config_key":"","YARN_VERSION":"1.13.0","HOSTNAME":"d5090416df14","npm_config_allow_same_version":"","npm_config_description":"true","npm_config_fetch_retries":"2","npm_config_heading":"npm","npm_config_if_present":"","npm_config_init_version":"1.0.0","npm_config_user":"","npm_node_execpath":"/usr/local/bin/node","SHLVL":"1","npm_package_scripts_test_all":"npm test -- --runInBand --testMatch '**/test/(unit|component)/**/**spec.js'","npm_package_dependencies_enjoi":"^6.0.0","npm_config_prefer_online":"","npm_config_noproxy":"","CONFIG_ENV":"pact","HOME":"/root","OLDPWD":"/","npm_config_force":"","npm_config_only":"","npm_config_read_only":"","npm_package_engines_node":"^10.15.0","npm_package_scripts_test_component":"npm test -- --testMatch '**/test/component/**/**spec.js'","npm_package_scripts_test_contract":"node ./test/scripts/runContractsValidator.js -o 6","npm_package_dependencies_axios_mock_adapter":"^1.16.0","npm_package_dependencies_bunyan":"^1.8.12","npm_package_devDependencies_chai":"^4.2.0","npm_config_cache_min":"10","npm_config_init_license":"ISC","npm_package_scripts_start_debug":"node --inspect=<IP_ADDRESS>:5858 --max-old-space-size=${CUSTOM_MAX_OLD_SPACE_SIZE:-460} src/index.js","npm_package_devDependencies__stryker_mutator_core":"^2.0.2","npm_config_editor":"vi","npm_config_rollback":"true","npm_config_tag_version_prefix":"v","npm_package_scripts_lint_fix":"eslint ./src --ext .js --fix","npm_config_cache_max":"Infinity","npm_config_timing":"","npm_config_userconfig":"/root/.npmrc","npm_package_contributors_0_email":"Oleksandr.Smorodin@dazn.com","npm_package_dependencies_compression":"^1.7.3","npm_package_dependencies_moment":"^2.24.0","npm_package_devDependencies_nyc":"^14.1.1","npm_config_engine_strict":"","npm_config_init_author_name":"","npm_config_init_author_url":"","npm_config_preid":"","npm_config_tmp":"/tmp","npm_package_description":"Service DCB","npm_package_contributors_1_email":"Joao.Henrique-Silva@dazn.com","npm_package_dependencies__hapi_joi":"^15.1.0","npm_package_dependencies_json_refs":"^3.0.13","npm_package_dependencies_swagger_mock_validator":"^7.0.0","npm_config_depth":"Infinity","npm_config_package_lock_only":"","npm_config_save_dev":"","npm_config_usage":"","npm_package_contributors_2_email":"Vasily.Gorin@dazn.com","npm_package_readmeFilename":"README.md","npm_package_homepage":"https://github.com/getndazn/service-dcb-web-api#readme","npm_config_metrics_registry":"https://registry.npmjs.org/","npm_config_cafile":"","npm_config_otp":"","npm_config_package_lock":"true","npm_config_progress":"true","npm_config_https_proxy":"","npm_config_save_prod":"","npm_package_contributors_3_email":"Marta.Fernandes@dazn.com","npm_package_scripts_docker_build":"docker build -t massive/node-template .","npm_config_audit":"true","npm_config_cidr":"","npm_config_onload_script":"","npm_config_sso_type":"oauth","npm_package_devDependencies_eslint_plugin_import":"^2.16.0","npm_config_rebuild_bundle":"true","npm_config_save_bundle":"","npm_config_shell":"bash","_":"/usr/local/bin/npm","npm_package_dependencies_express":"^4.16.4","npm_config_dry_run":"","npm_config_prefix":"/usr/local","npm_package_scripts_lint":"eslint ./src --ext .js","npm_package_dependencies_newrelic":"^5.6.0","npm_package_devDependencies__stryker_mutator_javascript_mutator":"^2.0.2","npm_config_scope":"","npm_config_browser":"","npm_config_cache_lock_wait":"10000","npm_config_ignore_prepublish":"","npm_config_registry":"https://registry.npmjs.org/","npm_config_save_optional":"","npm_config_searchopts":"","npm_config_versions":"","TERM":"xterm","npm_config_cache":"/root/.npm","npm_config_proxy":"","npm_config_send_metrics":"","npm_package_scripts_start":"node --max-old-space-size=${CUSTOM_MAX_OLD_SPACE_SIZE:-460} src/index.js","npm_package_scripts_start_win":"node --max-old-space-size=460 src/index.js","npm_config_global_style":"","npm_config_ignore_scripts":"","npm_config_version":"","npm_package_author_email":"bruno.germano@massive.co","npm_package_dependencies_axios":"^0.19.0","npm_package_devDependencies_shx":"^0.3.2","npm_config_local_address":"","npm_config_viewer":"man","npm_config_node_gyp":"/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js","PATH":"/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/tmp/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin","npm_package_name":"service-dcb-web-api","npm_package_repository_type":"git","npm_package_devDependencies__pact_foundation_pact":"^9.1.1","npm_config_audit_level":"low","npm_config_prefer_offline":"","NODE":"/usr/local/bin/node","npm_package_scripts_docker_run":"docker run -dP massive/node-template","npm_package_scripts_docker_compose_up":"docker-compose up","npm_package_scripts_test_integration":"npm test -- --testMatch '**/test/integration/**spec.js' --passWithNoTests","npm_package_dependencies__perform_middleware_common_trackers":"^1.0.2","npm_package_devDependencies_eslint_config_airbnb_base":"^13.1.0","npm_config_color":"true","npm_config_sign_git_commit":"","npm_package_scripts_test_unit":"npm test -- --testMatch '**/test/unit/**/*.spec.js'","npm_package_scripts_pact_contract":"CONFIG_ENV=pact NODE_ENV=pactTest jest --testMatch '**/test/pact/**/service.test.pact.js' --runInBand","npm_config_fetch_retry_mintimeout":"10000","npm_config_maxsockets":"50","npm_config_offline":"","npm_config_sso_poll_frequency":"500","npm_package_devDependencies__stryker_mutator_html_reporter":"^2.0.2","npm_package_devDependencies_eslint":"^5.15.1","npm_config_umask":"0022","npm_package_contributors_0_name":"Oleksandr Smodorin","npm_package_dependencies_aws_sdk":"^2.422.0","npm_package_devDependencies_supertest":"^3.4.2","npm_package_gitHead":"35bd2c8089fc22e415f0e406c30d17c4651b1a94","npm_config_fetch_retry_maxtimeout":"60000","npm_config_loglevel":"notice","npm_config_logs_max":"10","npm_config_message":"%s","npm_lifecycle_script":"CONFIG_ENV=pact NODE_ENV=pactTest jest --testMatch '**/test/pact/**/service.test.pact.js' --runInBand","npm_package_contributors_1_name":"Joao Machado Silva","npm_package_scripts_test":"CONFIG_ENV=testing jest","npm_package_dependencies_body_parser":"^1.18.3","npm_config_ca":"","npm_config_cert":"","npm_config_global":"","npm_config_link":"","npm_package_version":"0.6.0","npm_package_contributors_2_name":"Vasily Gorin","npm_package_repository_url":"git+https://github.com/getndazn/service-dcb-web-api.git","npm_package_scripts_test_mutation":"CONFIG_ENV=testing stryker run","npm_package_dependencies_jest":"^24.9.0","npm_config_access":"","npm_config_also":"","npm_config_save":"true","npm_config_unicode":"","npm_lifecycle_event":"pact:contract","npm_package_contributors_3_name":"Marta Fernandes","npm_package_dependencies_cors":"^2.8.5","npm_package_dependencies_js_yaml":"^3.13.1","npm_package_dependencies_jwks_rsa":"^1.5.1","npm_package_dependencies_uuid":"^3.3.2","npm_config_argv":"{\"remain\":[],\"cooked\":[\"run\",\"pact:contract\"],\"original\":[\"run\",\"pact:contract\"]}","npm_config_long":"","npm_config_production":"","npm_config_searchlimit":"20","npm_config_unsafe_perm":"","npm_config_update_notifier":"true","npm_package_scripts_test_coverage":"npm run test:all -- --coverage","npm_package_dependencies_lodash":"^4.17.15","npm_package_devDependencies_chai_as_promised":"^7.1.1","npm_config_auth_type":"legacy","npm_config_node_version":"10.15.3","npm_config_tag":"latest","npm_package_devDependencies_nock":"^11.3.3","npm_config_git_tag_version":"true","npm_config_commit_hooks":"true","npm_config_script_shell":"","npm_config_shrinkwrap":"true","npm_package_devDependencies__pact_foundation_pact_node":"^9.0.4","npm_config_fetch_retry_factor":"10","npm_config_save_exact":"","npm_config_strict_ssl":"true","npm_config_dev":"","npm_config_globalconfig":"/usr/local/etc/npmrc","npm_config_init_module":"/root/.npm-init.js","npm_config_parseable":"","PWD":"/tmp","npm_config_globalignorefile":"/usr/local/etc/npmignore","npm_execpath":"/usr/local/lib/node_modules/npm/bin/npm-cli.js","npm_package_author_name":"Bruno Germano","npm_config_cache_lock_retries":"10","npm_config_searchstaleness":"900","npm_config_node_options":"","npm_config_save_prefix":"^","npm_config_scripts_prepend_node_path":"warn-only","npm_package_dependencies_jsonwebtoken":"^8.5.1","npm_config_group":"","npm_config_init_author_email":"","npm_config_searchexclude":"","npm_package_scripts_pact_publish":"node test/scripts/publishPact.js","npm_config_git":"git","npm_config_optional":"true","NODE_ENV":"pactTest","npm_config_json":"","INIT_CWD":"/tmp","JEST_WORKER_ID":"1"}}'
[2019-09-16T13:58:12.605Z]  INFO<EMAIL_ADDRESS>on d5090416df14: Created './standalone/linux-x64-1.70.2/bin/pact-mock-service service --consumer 'service-consumer' --pact_dir '/tmp/test/pact/contracts' --host '<IP_ADDRESS>' --log '/tmp/test/pact/logs/pact-service-provider.log' --pact-file-write-mode 'overwrite' --port '9090' --provider 'service-provider' --pact_specification_version '2'' process with PID: 32
[2019-09-16T13:58:12.616Z] DEBUG<EMAIL_ADDRESS>on d5090416df14:
    /bin/sh: 1: ./standalone/linux-x64-1.70.2/bin/pact-mock-service: not found

[2019-09-16T13:58:12.616Z] ERROR<EMAIL_ADDRESS>on d5090416df14:
    Pact Binary Error: /bin/sh: 1: ./standalone/linux-x64-1.70.2/bin/pact-mock-service: not found

[2019-09-16T13:58:12.626Z]  WARN<EMAIL_ADDRESS>on d5090416df14: Pact exited with code 127.
[2019-09-16T13:58:12.626Z]  INFO<EMAIL_ADDRESS>on d5090416df14: Removing Pact with PID: 32
 FAIL  test/pact/service.test.pact.js (32.579s)
  When service is our Provider
    ✕ returns 200 from our service with the right response body (23ms)

  ● When service is our Provider › returns 200 from our service with the right response body

    Timeout - Async callback was not invoked within the 20000ms timeout specified by jest.setTimeout.Error: Timeout - Async callback was not invoked within the 20000ms timeout specified by jest.setTimeout.

      at mapper (node_modules/jest-jasmine2/build/queueRunner.js:25:45)

  ● When service is our Provider › returns 200 from our service with the right response body

    TypeError: Cannot read property 'addInteraction' of undefined

      32 |
      33 |     test('returns 200 from our service with the right response body', async () => {
    > 34 |         await provider.addInteraction({
         |                        ^
      35 |             uponReceiving: 'a POST request to /v1/user',
      36 |             withRequest: {
      37 |                 method: 'POST',

      at Pact.Object.<anonymous>.Pact.addInteraction (node_modules/@pact-foundation/src/httpPact.ts:102:29)
      at Object.addInteraction (test/pact/service.test.pact.js:34:24)

  ● When service is our Provider › returns 200 from our service with the right response body

    TypeError: Cannot read property 'verify' of undefined

      24 |
      25 |     afterEach(async () => {
    > 26 |         await provider.verify();
         |                        ^
      27 |     });
      28 |
      29 |     afterAll(async () => {

      at Pact.Object.<anonymous>.Pact.verify (node_modules/@pact-foundation/src/httpPact.ts:113:8)
      at Object.verify (test/pact/service.test.pact.js:26:24)

Test Suites: 1 failed, 1 total
Tests:       1 failed, 1 total
Snapshots:   0 total
Time:        32.785s

This is great detail, thanks.
It’s just after midnight here, so I might be mistaken, but it looks like the path for the standalone isn’t correct (it should be inside node_modules).
I took a close read of the diff between 9.0.3 and 9.0.4, and I can’t immediately see the cause, but I did notice some dead code related to paths that we should remove.
I’ll have a closer look tomorrow.
Sent from my mobile

Have to investigate it deeper. Now I face this issue on 9.0.3 as well, and I managed to run it without any problem on 9.0.4.
It looks that problem hidden somewhere else.

Is it a permissions issue? I have run in to weirdness with docker and executing files through node/npm before

What's you host OS? It looks like you're installing pact on the host first and then running in docker. This will cause issues because Pact has platform specific code in it. You can't volume mount node_modules in this instance (i.e. run npm install in container)

The path looks correct, it's relative to the pact-node dependencies path which is within node_modules.

It's definitely related to docker. It's done automatically in container during pipeline execution and I was surprised when it stoped working without any changes.
I think I have to find some issue in different place and it is not a problem of pact.
Sorry for bothering you guys and thank you for fast responses.


style: changed the background of QRCodeScan to have more opacity

Motivation
Changed to opacity of the QR Code Scan background to 60% (value agreed with @artkorotkikh-dfinity) and using the theme color.
Changes
Before

After

Closed in favor of PR #1387


404 Not Found. But why?

Hi.
I created a systemctl service to run the server. And it always return '404 Not Found' in plain/text when I access http://(IP pointed to the server in LAN)/, and the request just headed on the root path.
Service file and status are below.
# File /lib/systemd/system/aria2-webui.service

[Unit]
Description=Aria2 WebUI Daemon
After=network.target

[Service]
Type=simple
User=root
Group=root
ExecStart=/usr/bin/node /usr/app/aria2-webui/node-server.js

[Install]
WantedBy=multi-user.target

# Status
root@Pi: /usr/app/aria2-webui master
 # systemctl status aria2-webui                                                       [22:16:09]
● aria2-webui.service - Aria2 WebUI Daemon
   Loaded: loaded (/lib/systemd/system/aria2-webui.service; disabled; vendor preset: enabled)
   Active: active (running) since Sat 2019-02-16 22:16:09 CST; 4s ago
 Main PID: 6544 (node)
   CGroup: /system.slice/aria2-webui.service
           └─6544 /usr/bin/node /usr/app/aria2-webui/node-server.js

2月 16 22:16:09 Pi systemd[1]: Started Aria2 WebUI Daemon.
2月 16 22:16:11 Pi node[6544]: WebUI Aria2 Server is running on http://localhost:8888

It seems all OK... But why there's a 404?

Just tried with shell /usr/bin/node /usr/app/aria2-webui/node-server.js and it shows correctly.

Try the fix from #477.

@x86-app problem solved?

fix #477 works for me.
(on raspbian stretch)

ExecStart=cd /usr/app/aria2-webui/ && /usr/bin/node node-server.js


C++11 support

Just to communicate here.

In Linux and lambda function, the auto keyword cannot be used.  Removing the auto keyword in lambda.
Ingemar

I have fixed the build errors on linux. C++ support is now completed.


Image with link in markdown not working properly

Hi,
Image links in markdown are not working properly. Sometimes, the link is replaced with the image url.
For example, this markdown command :
[![Project Stats](image_url)](link_url)
sometimes produces a link to image_url instead of link_url :

instead of

The problem can be reproduced on https://try.gogs.io (Gogs Version: <IP_ADDRESS>5):
https://try.gogs.io/chengbs/Openfire/src/3.10/README.md
The link of the first badge (travis-ci) is correct, but the second (openhub badge) is linking to the gif image.

Thanks,

Right now, only image path ends with .svg will produce a link to link, not image itself...

Found the same problem in the latest develop build (<IP_ADDRESS>6)
Markdown:
[![Alt Text](http://image_url)](http://google.com)
Html:

For full example:
https://try.gogs.io/Mr_Dark/Markdown-Test/src/master/README.md

I think I said something very clear...

I think the mimetype is wrong for svg images. When accessing a readme file with a linked svg image gogs offers a 'plain' file; even opening it just shows me the text because the mimetype is wrong

Confirmed, this snippet also doesn't work on gogs:
[![build status]
(https://drone.osgeo.kbt.io/api/badges/geos/php-geos/status.svg?branch=master)]
(https://drone.osgeo.kbt.io/geos/php-geos?branch=master, alt=build status)

That is, it only produces the image, but not the link, as it should:
[![build status]
(https://drone.osgeo.kbt.io/api/badges/geos/php-geos/status.svg?branch=master)]
(https://drone.osgeo.kbt.io/geos/php-geos?branch=master, alt=build status)

@Unknwon ending or not with .svg doesn't make a difference, see here:
https://try.gogs.io/strk/test1/issues/5

Putting the image and link text onto the same line seems to fix the issue:
[![build status]
(https://drone.osgeo.kbt.io/api/badges/geos/php-geos/status.svg?branch=master)](https://drone.osgeo.kbt.io/geos/php-geos?branch=master, alt=build status)

[![build status]
(https://drone.osgeo.kbt.io/api/badges/geos/php-geos/status.svg?branch=master)](https://drone.osgeo.kbt.io/geos/php-geos?branch=master, alt=build status)
This is not a problem on github.

I was wrong, single-line doesn't fix it either:
https://try.gogs.io/strk/test1/issues/5#issuecomment-948

@Unknwon As I understand the rationale behind the code, it is there to have internally linked images being served from raw instead of src. But it also checks for links being absolute, i.e., have a protocol (validLinksPattern).
It seems to me that there are two issues here:

the processing should only occur for internal links, i.e., links that match the current working tree, or at least only the gogs instance. Can you maybe write up a list of test cases that should work, as you probably know better what the original reasoning behind the code was?
On the other hand, if the link already is inside an ..., then it would not make sense processing it at all. That would probably be a more robust fix anyway. Maybe the image render can do a reverse scan on the output buffer to check if there is an unclosed a tag already in the buffer.

Meanwhile I've figured my own issue, and filed it as https://github.com/gogits/gogs/issues/3545

Patch has pushed to fix this issue, please test on develop branch or https://try.gogs.io/gogs/gogs.

Sorry, not develop branch, it's release/0.11.


V0.7.1 and get the gce build happening inside Dapper too

@cloudnautique @ibuildthecloud
not quite done yet, but getting closer here too.

@ibuildthecloud updated to use the checksum file on GH


Tooltip and docs updates

Small adjustments to Tooltips. Fixes z-index issue wherein hidden tooltip would cover clickable/hoverable objects. Adds width parameter. Standardizes font and font-size of tooltip text.
Updates docs for printing reports, addressing #236
Tested working in fsm-nearshore-reports

This PR needs to be updated.  Merging dev into it should bring in ESM upgades, and probably a few conflicts


What is the preservedRouteParameters attribute syntax for multiple route values?

What is the syntax for preserving multiple route parameters?
I have tried
preservedRouteParameters = "dr, topnav" failed
preservedRouteParameters = "dr topnav" failed
preservedRouteParameters = "dr,topnav" failed

I have a site abc.com for almost 200,000 PARTS which are in DB. I have custom links i.e. abc.com/part-number. Part-number can be any string like "123", "87686-ABC" etc. I actually have a page requestQuote.cshtml where the info for the specific part in the link is shown. So i hv virtually over 200,000 links. Now I am trying to use


util: remove the deleteLock acquistion check for clone and snapshot

At present while acquiring the deleteLock on the volume, we check
for ongoing clone and snapshot creation operations on the same.
Considering snapshot and clone controllers does not allow parent
volume deletion on subjected operations, we can be free from this
extra check.
Updates: #2197
Signed-off-by: Humble Chirammal<EMAIL_ADDRESS>

/retest  ci/centos/mini-e2e/k8s-1.21

/retest ci/centos/mini-e2e/k8s-1.21


[flakytest] timeout in fork most likely on RealtimeKinesisIntegrationTest

see
https://github.com/apache/pinot/actions/runs/5595643067/jobs/10231738127?pr=11132
https://github.com/apache/pinot/actions/runs/5595738571/jobs/10231935149?pr=11133
https://github.com/apache/pinot/actions/runs/5600370566/jobs/10242653727?pr=11105
which occurs on 3 different PR

Kinesis consumer was re-implemented in #12806. Don't observe the same failure since then


supoprt socks5 proxy

What type of PR is this?
/kind feature
add socks5 proxy to support  SSH to the edge node. It is convenient to manage edge nodes
    ssh -o "ProxyCommand nc --proxy-type socks5 --proxy <IP_ADDRESS>:10800 {nodeName} {host ssh port}" root@any ip

would you mind add some example or readme for this feature?


ID user role:
User feedback: something
(user_ask_role)

Question ID
user role

Details
The "How do I know?" on this page is below the answer choices. On other pages it goes below the question/prompt but above the answer choices. I think I like it above the answer choices more.

Variable being sought
user_ask_role

Package version
0.3

Filename
docassemble.FeeWaiverRequest:data/questions/fee_waiver_request.yml

BEFORE

AFTER


English grammar changes

Ill go though the repo and help update the "English" later today.

@charl-kruger
This is exactly what I wanted. Thank you!


By default localhost:9200 should be used as host but it is not the case

According to README.MD:
Host
By default it uses localhost:9200 as host. you can change this with the host and port variables
But when I install elasticsearch with the following yaml:
elasticsearch::java_install: false
elasticsearch::package_url: 'file:/vagrant/salt/states/puppetmaster/files/elk-external-resources/elasticsearch-1.7.3.noarch.rpm'
elasticsearch::instances:
'es-01':
'config':
'node.name': ${HOSTNAME}
I can reach elasticsearch from an another machine through its IP address.
[root@puppetmaster ~]# wget http://<IP_ADDRESS>:9200/
--2015-10-29 19:55:43--  http://<IP_ADDRESS>:9200/
Connecting to <IP_ADDRESS>:9200... connected.
HTTP request sent, awaiting response... 200 OK
Length: 336 [application/json]
Saving to: ‘index.html’
100%[============================================================================================================================================================================================>] 336         --.-K/s   in 0s
2015-10-29 19:55:43 (74.5 MB/s) - ‘index.html’ saved [336/336]
[root@puppetmaster ~]# cat index.html
{
"status" : 200,
"name" : "elkagent",
"cluster_name" : "elasticsearch",
"version" : {
"number" : "1.7.3",
"build_hash" : "05d4530971ef0ea46d0f4fa6ee64dbc8df659682",
"build_timestamp" : "2015-10-15T09:14:17Z",
"build_snapshot" : false,
"lucene_version" : "4.10.4"
},
"tagline" : "You Know, for Search"
}
[root@puppetmaster ~]#
Is this a bug?

this is part of kibana.yml
[root@elkagent config]# cat kibana.yml
Kibana is served by a back end server. This controls which port to use.
port: 5601
The host to bind the server to.
host: "<IP_ADDRESS>"
The Elasticsearch instance to use for all your queries.
elasticsearch_url: "http://localhost:9200"
preserve_elasticsearch_host true will send the hostname specified in elasticsearch. If you set it to false,
then the host you use to connect to this Kibana instance will be sent.
elasticsearch_preserve_host: true
Kibana uses an index in Elasticsearch to store saved searches, visualizations
and dashboards. It will create a new index if it doesn't already exist.
kibana_index: ".kibana"

Hi,
In all the examples i use localhost indeed but the module doesn't change what the defaults are for Elasticsearch it self.
By default for the 1.x releases is bounds to <IP_ADDRESS>
Starting with ES 2.0 its bound to localhost by default.
Hope this clarifies it a bit.

Definitely. Thank you very much for the explanation.


Lua VM crashed using Docker on MacBook M1

Hello! I'm using an Apple MacBook M1 and when I try to use the latest kong image (2.5.0), I get this error:

nginx: lua atpanic: Lua VM crashed, reason: not enough memory

Here is my docker-compose.yml for kong:
  kong:
    platform: linux/x86_64
    image: kong:latest
    user: "${KONG_USER}"
    depends_on:
      database:
        condition: service_healthy
    environment:
      KONG_ADMIN_ACCESS_LOG: /dev/stdout
      KONG_ADMIN_ERROR_LOG: /dev/stderr
      KONG_PROXY_LISTEN: '${KONG_PROXY_LISTEN:-<IP_ADDRESS>:8000}'
      KONG_ADMIN_LISTEN: '${KONG_ADMIN_LISTEN:-<IP_ADDRESS>:8001}'
      KONG_DATABASE: postgres
      KONG_CASSANDRA_CONTACT_POINTS: ${KONG_PG_HOST}
      KONG_PG_HOST: ${KONG_PG_HOST}
      KONG_PG_DATABASE: ${KONG_PG_DATABASE}
      KONG_PG_USER: ${KONG_PG_USER}
      KONG_PG_PASSWORD: ${KONG_PG_PASSWORD}
      KONG_PROXY_ACCESS_LOG: /dev/stdout
      KONG_PROXY_ERROR_LOG: /dev/stderr
      KONG_PREFIX: ${KONG_PREFIX:-/var/run/kong}
    networks:
      - my-net
    ports:
      - '${KONG_INBOUND_PROXY_LISTEN:-<IP_ADDRESS>}:8000:8000/tcp'
      - '${KONG_INBOUND_SSL_PROXY_LISTEN:-<IP_ADDRESS>}:8443:8443/tcp'
      - '<IP_ADDRESS>:8001:8001/tcp'
      - '<IP_ADDRESS>:8444:8444/tcp'
    healthcheck:
      test: ["CMD", "kong", "health"]
      interval: 10s
      timeout: 10s
      retries: 10
    restart: on-failure:5
    read_only: true
    volumes:
      - kong_prefix_vol:${KONG_PREFIX:-/var/run/kong}
      - kong_tmp_vol:/tmp
    deploy:
      restart_policy:
        delay: 50s
        condition: on-failure
        max_attempts: 5
        window: 10s
      resources:
        limits:
          cpus: 2
          memory: 2g
    security_opt:
      - no-new-privileges

Hi @vitor-l,
Can you please add more info on how to retro? Is it right after spinning up the stack, or after you load a configuration?
Thanks!

Hi @gszr,
It happens when I try to run the container with the image.
Command:

docker compose up

Thanks for the additional info, @vitor-l! We will look into it.

If I find more useful info, I will post it here.
Thank @gszr for the quick answer.

@gszr, more info:
I enter the container bash by running:

docker-compose run kong bash

Then, inside the bash, I run:

kong start --conf /etc/kong/kong.conf

You can check my kong.conf here. I was trying to change some configs to consume less memory (but unsuccessful).
Kong starts ok, but when I run:

./docker-entrypoint.sh kong docker-start --vv

I got this:
2021/08/04 17:41:27 [error] 185#0: init_by_lua error: /usr/local/share/lua/5.1/luarocks/loader.lua:104: error loading module 'kong.db.schema.plugin_loader' from file '/usr/local/share/lua/5.1/kong/db/schema/plugin_loader.lua':
	not enough memory
stack traceback:
	[C]: in function 'a_loader'
	/usr/local/share/lua/5.1/luarocks/loader.lua:104: in function </usr/local/share/lua/5.1/luarocks/loader.lua:101>
	[C]: in function 'require'
	...are/lua/5.1/kong/db/schema/others/declarative_config.lua:7: in main chunk
	[C]: in function 'require'
	/usr/local/share/lua/5.1/kong/db/declarative/init.lua:1: in main chunk
	[C]: in function 'require'
	/usr/local/share/lua/5.1/kong/runloop/handler.lua:13: in main chunk
	[C]: in function 'require'
	/usr/local/share/lua/5.1/kong/init.lua:72: in main chunk
	[C]: in function 'require'
	init_by_lua:2: in main chunk
nginx: [error] init_by_lua error: /usr/local/share/lua/5.1/luarocks/loader.lua:104: error loading module 'kong.db.schema.plugin_loader' from file '/usr/local/share/lua/5.1/kong/db/schema/plugin_loader.lua':
	not enough memory
stack traceback:
	[C]: in function 'a_loader'
	/usr/local/share/lua/5.1/luarocks/loader.lua:104: in function </usr/local/share/lua/5.1/luarocks/loader.lua:101>
	[C]: in function 'require'
	...are/lua/5.1/kong/db/schema/others/declarative_config.lua:7: in main chunk
	[C]: in function 'require'
	/usr/local/share/lua/5.1/kong/db/declarative/init.lua:1: in main chunk
	[C]: in function 'require'
	/usr/local/share/lua/5.1/kong/runloop/handler.lua:13: in main chunk
	[C]: in function 'require'
	/usr/local/share/lua/5.1/kong/init.lua:72: in main chunk
	[C]: in function 'require'
	init_by_lua:2: in main chunk

I'm having exactly the same issue with Mac M1 and Kong 2.5 via Docker.
@vitor-l did you manage to find a solution?

@joaoccmatos, I did not find a solution. I hope @gszr save us...

Any news on this? I'm having the same issue.

@fbaltor, I am running into this same issue (LUA in OpenResty) on two other projects.  In one case (the image for this https://github.com/jitsi/docker-jitsi-meet/blob/master/web/Dockerfile), by rebuilding the image (and also rebuilding the base image) for linux/arm64, I was able to get it running.  In fact, I was able to run the entire project with only that one image as arm64, while the rest of the images were the default amd64.

Thank you, @adam-at-mobomo! I will check this out.

While I didn't manage to solve my issue, I documented the (perhaps incomplete?) steps to rebuild an image for ARM in docker-jitsi-meet/issues/1099.

Hi folks,
Kong provides images for arm64 - I see the Dockerfile above is pulling linux/x86_64. Could you try changing the platform to linux/arm64/v8?
Also, a full docker-compose file and reproduction steps would be appreciated.
Cheers!

We believe that this problem is fixed and I'm closing the issue now. Please reopen if needed.


Yandex station mini no entity after setup

Yandex station mini doesn't present as entity after integration setup and configuration.
Error from logs
Logger: homeassistant.components.media_player
Source: custom_components/yandex_station/core/yandex_quasar.py:44
Integration: Media Player (documentation, issues)
First occurred: 21:41:30 (1 occurrences)
Last logged: 21:41:30
Error while setting up yandex_station platform for media_player
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/entity_platform.py", line 249, in _async_setup_platform
    await asyncio.shield(task)
  File "/config/custom_components/yandex_station/media_player.py", line 80, in async_setup_entry
    for speaker in await quasar.load_speakers():
  File "/config/custom_components/yandex_station/core/yandex_quasar.py", line 90, in load_speakers
    scenarios = await self.load_scenarios()
  File "/config/custom_components/yandex_station/core/yandex_quasar.py", line 119, in load_scenarios
    return {
  File "/config/custom_components/yandex_station/core/yandex_quasar.py", line 120, in <dictcomp>
    decode(d['name']): d
  File "/config/custom_components/yandex_station/core/yandex_quasar.py", line 44, in decode
    return ''.join([MASK_EN[MASK_RU.index(s)] for s in uid[3:]])
  File "/config/custom_components/yandex_station/core/yandex_quasar.py", line 44, in <listcomp>
    return ''.join([MASK_EN[MASK_RU.index(s)] for s in uid[3:]])
ValueError: substring not found

Go to scenarios list in Yandex mobile app and remove all scenarios that starts with XA...

Go to scenarios list in Yandex mobile app and remove all scenarios that starts with XA...

Yuup. Problem resolved. Thanks.
But I'm little bit confused... How its possible from that logs to know that I have scenarios that starts with XA?
Its because service scenario starts from the same letters so thats lead to some conflict or ....? ))

Yes. Same letters


Missing default colors for some components

Test all components without having an immediate data-color present to test fallback/default colors.
I found it best to test this downstream in a clean app, as we have a lot of other defaults in storybook defined. It was very cumbersome to find and remove/disable all layers of coloring we had in storybook and other apps.

Checkbox is missing default color when checked

This was due to edge-case of generating and regenerating tokens, with old built css contaminating :root. #2809


Cannot install

This is what I get
[XYZ /usr/local/sbin] #>go install  github.com/mliezun/hilink@latest
go: downloading github.com/mliezun/hilink v0.0.0-20181205192430-f76e2a89c450
go: finding module for package github.com/clbanning/mxj
go: found github.com/clbanning/mxj in github.com/clbanning/mxj v1.8.4
package github.com/mliezun/hilink is not a main package

How can I fix this?

same problem here


README: slack banner sends user to skipbox landing page

yes, we need to get a #kompose channel created in k8s slack then switch over.

@sebgoa thanks updated the issue. I'll ask around and see who can make this happen.

maybe if we just ping @sarahnovotny she will create a #kompose channel for us on k8s slack ?

done.
(after a brief foray on the wrong slack)
On Thu, Oct 20, 2016 at 8:55 AM, sebgoa<EMAIL_ADDRESS>wrote:

maybe if we just ping @sarahnovotny https://github.com/sarahnovotny she
will create a #kompose channel for us on k8s slack ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/kompose/issues/222#issuecomment-255148038,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAHxirpC8kq65YWlbZ5BZzwLlqHD_N6Nks5q148LgaJpZM4KbjiU
.


Handle things a bit better when cursor not on code

If I rest my cursor above some code and do option-enter, the console pops up and I get this:
Uncaught TypeError: Cannot read property 'start' of undefined /usr/share/atom/resources/app/node_modules/text-buffer/lib/range.js:26
Mind you it's handy to have the console open to see error messages..

Ah tried with latest atom and it doesn't open a console, but does pop up the same error:
[Enter steps to reproduce below:]

...
...

Atom Version: 0.176.0
System: linux 3.13.0-37-generic
Thrown From: tidal package, v0.3.0
Stack Trace
Uncaught TypeError: Cannot read property 'start' of undefined
At /usr/share/atom/resources/app/node_modules/text-buffer/lib/range.js:26

TypeError: Cannot read property 'start' of undefined
  at Function.module.exports.Range.fromObject (/usr/share/atom/resources/app/node_modules/text-buffer/lib/range.js:26:31)
  at TextBuffer.module.exports.TextBuffer.getTextInRange (/usr/share/atom/resources/app/node_modules/text-buffer/lib/text-buffer.js:351:36)
  at TextEditor.module.exports.TextEditor.getTextInBufferRange (/usr/share/atom/resources/app/src/text-editor.js:641:26)
  at REPL.module.exports.REPL.getMultiLineExpression (/home/alex/.atom/packages/tidal/lib/repl.coffee:117:25)
  at REPL.module.exports.REPL.currentExpression (/home/alex/.atom/packages/tidal/lib/repl.coffee:101:37)
  at REPL.module.exports.REPL.eval (/home/alex/.atom/packages/tidal/lib/repl.coffee:57:28)
  at atom-text-editor.REPL.atom.commands.add.tidal:eval-multi-line (/home/alex/.atom/packages/tidal/lib/repl.coffee:20:35)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app/src/command-registry.js:243:29)
  at /usr/share/atom/resources/app/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:558:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/share/atom/resources/app/node_modules/atom-keymap/lib/keymap-manager.js:396:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/usr/share/atom/resources/app/src/window-event-handler.js:170:20)

Commands
     -0:00.7 tidal:eval-multi-line (atom-text-editor.editor.is-focused)

Config
{
  "core": {
    "themes": [
      "graphite-ui",
      "adventurous-syntax"
    ],
    "autoHideMenuBar": true
  }
}

Installed Packages
# User
adventurous-syntax, v0.1.2
autocomplete-plus, v2.0.3
graphite-ui, v0.13.2
ide-haskell, v0.3.0
language-haskell, v1.0.0
linter-hlint, v0.3.1
tidal, v0.3.0

# Dev
No dev packages

/cc @atom/core

BTW there are a lot of deprecation warnings with that atom too..

I apologize for the delay, kind of busy these day……now it's chinese new year holiday finally had time to look at this.
Just publish 0.3.1 to fix eval empty line
deprecation warnings seems to come from the upgrading to 1.0 movement, https://atom.io/docs/v0.179.0/upgrading/upgrading-your-package. I take try move the deprecated api first.

Just update to 0.4.0! all deprecated waring should be gone.
try to working on display ghci ouput to editor

Nice work, thanks a lot!
I noticed that with multiline evals, some characters aren't counted, for example the trailing square bracket here isn't included, and the pattern doesn't evaluate:
d1 $ weave 16 (speed (scale 1 1.4 sine1)) [jux (iter 8) $ sound "sd8:4*4",
                                           jux (iter 4) $ sound "bd*2",
                                           jux (iter 3) $ sound "sd8:3*4"
                                          ]

Oh and happy new year :)

@yaxu
Thx! not sure why the trailing ] doesn't get evaluated, need to check that!

Thanks @seansay ! It happens also e.g. if , is on its own line.. I guess something is looking for letters of the alphabet.


feat(reports) report anonymous usage data of dbless feature

Summary
This PR reports certain usage of the new DB-less or declarative config feature.

Add tests for hourly "ping" report when database = off
Generate dbless-reconfigure event when /config API is used to reconfigure with tests
Generate dbless-import  event when kong config db_import cmd is used to import config from .yml into database with tests
Fix small styling issue in /config API endpoint

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Uncaught Exception: Attempting to call a function in a renderer window that has been closed or released. Function provid

An uncaught exception was reported.
Info:
OS: win32
Arch: ia32
GPMDP Version: 3.0.1
Time: Sat Mar 12 2016 19:38:43 GMT-0800 (Pacific Standard Time)
Error:
Attempting to call a function in a renderer window that has been closed or released. Function provid
Error: Attempting to call a function in a renderer window that has been closed or released. Function provided here: Object.<anonymous> (C:\Users\Cathedral\AppData\Local\GPMDP_3\app-3.0.1\resources\app\build\inject\GPMInject\interface\mouseButtonNavigation.js:8:8.
    at BrowserWindow.callIntoRenderer (C:\Users\Cathedral\AppData\Local\GPMDP_3\app-3.0.1\resources\atom.asar\browser\lib\rpc-server.js:201:19)
    at emitTwo (events.js:92:20)
    at BrowserWindow.emit (events.js:172:7)

This issue was created automatically inside the uncaughtException handler

Closing this automatically reported issue as a duplicate of #470


adding python-anyjson

This also appears to be in debian: https://packages.debian.org/source/wheezy/python-anyjson and fedora https://admin.fedoraproject.org/pkgdb/package/rpms/python-anyjson/ generically. Could you add those rules too.
And for the record the ubuntu packages: http://packages.ubuntu.com/trusty/python/python-anyjson

like that ?


TicketInfo response did not include expected ticket

A few days ago I used dcrwallet --vsp.sync to add several missing tickets to vspd. vspd is reporting TicketInfo response did not include expected ticket on all of the voting wallets. Meanwhile the voting wallets do show the stakesubmission address is valid. Not quite sure, but seems like this is a spurious error. My example below is with a voted testnet ticket, and on mainnet I have a live ticket (my own) that has the same exact issue. So whether the ticket is already voted or not doesn't seem to matter.
When I restart vspd, it attempts to add the ticket to the voting wallets again, but then continues reporting the same TicketInfo response did not include expected ticket on all of the voting wallets.
dcrd/dcrwallet is 1.6RC3 and I'm running a vspd build from the 17th on testnet.
vspd:
2020-11-20 18:51:05.161 [WRN]  BG: blockConnected: TicketInfo response did not include expected ticket (wallet=wss://<IP_ADDRESS>:19120/ws, ticketHash=ac23ccf03707ce9c94e7a0ce1509e8d276609191b44e139e9873113e5595e735)

After restarting vspd:
Nov 20 18:58:38 fra-test vspd[31075]: 2020-11-20 18:58:38.907 [DBG]  BG: checkWalletConsistency: Adding missing ticket (wallet=wss://<IP_ADDRESS>:19120/ws, ticketHash=ac23ccf03707ce9c94e7a0ce1509e8d276609191b44e139e9873113e5595e735)

All the voting wallets dutifully show RPC methods importprivkey,addtransaction, and rescanwallet commands being run.
Checking to see if the voting wallet knows about the ticket stakesubmission address:
dcrctl --wallet validateaddress TsZfe9cyYG18Lpj8KB3tmqJkfRU2ZvnQ1aL
{
  "isvalid": true,
  "address": "TsZfe9cyYG18Lpj8KB3tmqJkfRU2ZvnQ1aL",
  "ismine": true,
  "pubkeyaddr": "TkQ5F1eCa93HEAs4BTs1NnPKt7dnrm55zaW9VGZfoxiR1inWn2uJo",
  "pubkey": "03f70d57c716f829821355ae947b49262f8639aea065d6a97265344ddc536bf931",
  "iscompressed": true,
  "account": "imported"
}

Seems good, but vspd continues reporting the same about all wallets:
Nov 20 19:23:57 fra-test vspd[31075]: 2020-11-20 19:23:57.738 [WRN]  BG: blockConnected: TicketInfo response did not include expected ticket (wallet=wss://<IP_ADDRESS>:19120/ws, ticketHash=ac23ccf03707ce9c94e7a0ce1509e8d276609191b44e139e9873113e5595e735)

I think you might be able to reproduce this by shutting down vspd, buying tickets with ticketbuyer, starting vspd back up, then using dcrwallet --vsp.sync to add the missing tickets.

Hm, I am guessing that ticket info is being called with the wrong start height.
Could you please try running ticketinfo yourself with dcrctl and see if the expected ticket is in the response?
Additionally, could please you deploy #208  and set log level to debug to aid further investigation

That seems to be it:
Nov 22 06:05:50 fra-test vspd[589]: 2020-11-22 06:05:50.885 [DBG] RPC: TicketInfo RPC returned 52 tickets (wallet=wss://<IP_ADDRESS>:19120/ws, startHeight=559861)
Nov 22 06:05:50 fra-test vspd[589]: 2020-11-22 06:05:50.885 [DBG]  BG: checkWalletConsistency: Adding missing ticket (wallet=wss://<IP_ADDRESS>:19120/ws, ticketHash=ac23ccf03707ce9c94e7a0ce1509e8d276609191b44e139e9873113e5595e735)

That ticket was included in block 554887

Also one small note I left out was that on mainnet I see this message in the log as well:
Nov 22 ... [WRN]  BG: checkWalletConsistency: Ticket missing from voting wallet (wallet=%!s(func() string=0x7e2fa0), ticketHash=...)

Haven't seen that wallet=%!s(func() string=0x7e2fa0 on the testnet instance. The only difference I can think of is that the ticket is live. This is with a vspd build I made this morning.

This could be related to missing PurchaseHeight as a result of #189. I'm chatting with isuldor on Matrix to work through the issue.

Confirmed that this is due to missing purchase heights in the database. Here is a temporary patch to fix the database, should be fine to use this on both testnet and mainnet.
https://github.com/decred/vspd/compare/master...jholdstock:missing-purchase-height-fix?expand=1
diff --git a/database/ticket.go b/database/ticket.go
index 242d099..05adbdc 100644
--- a/database/ticket.go
+++ b/database/ticket.go
@@ -190,6 +190,29 @@ func (vdb *VspDatabase) GetTicketByHash(ticketHash string) (Ticket, bool, error)
        return ticket, found, err
 }

+func (vdb *VspDatabase) GetTicketsWithMissingPurchaseHeight() ([]Ticket, error) {
+       var tickets []Ticket
+       err := vdb.db.View(func(tx *bolt.Tx) error {
+               ticketBkt := tx.Bucket(vspBktK).Bucket(ticketBktK)
+
+               return ticketBkt.ForEach(func(k, v []byte) error {
+                       var ticket Ticket
+                       err := json.Unmarshal(v, &ticket)
+                       if err != nil {
+                               return fmt.Errorf("could not unmarshal ticket: %v", err)
+                       }
+
+                       if ticket.PurchaseHeight == 0 {
+                               tickets = append(tickets, ticket)
+                       }
+
+                       return nil
+               })
+       })
+
+       return tickets, err
+}
+
 func (vdb *VspDatabase) CountTickets() (int64, int64, int64, error) {
        defer vdb.ticketsMtx.RUnlock()
        vdb.ticketsMtx.RLock()

diff --git a/vspd.go b/vspd.go
index b667c3c..9eb9cae 100644
--- a/vspd.go
+++ b/vspd.go
@@ -83,6 +83,35 @@ func run(ctx context.Context) error {
        wallets := rpc.SetupWallet(cfg.walletUsers, cfg.walletPasswords, cfg.walletHosts, cfg.walletCerts)
        defer wallets.Close()

+       tickets, err := db.GetTicketsWithMissingPurchaseHeight()
+       if err != nil {
+               log.Error(err)
+               return err
+       }
+
+       client, err := dcrd.Client(ctx, cfg.netParams.Params)
+       if err != nil {
+               log.Error(err)
+               return err
+       }
+
+       for _, ticket := range tickets {
+               rawTx, err := client.GetRawTransaction(ticket.Hash)
+               if err != nil {
+                       log.Error(err)
+                       return err
+               }
+
+               log.Debugf("Adding purchase height %d for ticket %s",
+                       rawTx.BlockHeight, ticket.Hash)
+               ticket.PurchaseHeight = rawTx.BlockHeight
+               db.UpdateTicket(ticket)
+       }
+
+       // Exit.
+       log.Infof("Missing purchase height added for %d tickets. Exiting.", len(tickets))
+       return nil
+
        // Create and start webapi server.
        apiCfg := webapi.Config{
                VSPFee:               cfg.VSPFee,

[INF]  BG: blockConnected: Ticket no longer votable: outcome=voted, ticketHash=ac23ccf03707ce9c94e7a0ce1509e8d276609191b44e139e9873113e5595e735

Thanks!


Relax hard-pinning of starlette

starlette is up to 0.13.4 now.
Unless a specific patch release is actually a hard requirement it's more user-friendly to pin to a compatible release so as to automatically benefit from bug/security fixes.

Thanks! Yep, the problem is that as FastAPI is very tightly integrated with Starlette, there could be (and have been) breaking changes very easily, even for patch releases :pensive:
For Pydantic it's possible to have more relaxed pinning mainly because Pydantic runs all of FastAPI's tests as part of its own CI tests.
On the other hand, I'm thinking of migrating from Flit to Poetry, that way I could set up Dependabot to make it send PRs for each new version.
But for the time being, I have to keep the strict pinning...
Anyway, thanks for your contribution! And for all the management in Conda Forge! :bow: :rocket:


Regent - Assertion failure when partitioning 1D region into 3D ispace using equal partition.

I'm not sure if this is a Legion bug or Regent allowing me to do something thats not allowed. The following code fails an assertion:
import "regent"
fspace part{
  thing : int,
  thing2 : int
}
task main()
  var i = 2
  var space = ispace(int1d, {1000})
  var thing = region(space, part)
  var part = partition(equal, thing, ispace(int3d,{5,5,5}))
end

regentlib.start(main)

terra: /home/aidan/Legion/legion/runtime/legion/legion_domain.inl:1061: Legion::Domain::operator Legion::Rect<DIM, T>() const [with int DIM = 1; T = long long int; Legion::Rect<DIM, T> = Realm::Rect<1, long long int>]: Assertion `DIM == dim' failed.

I'm not sure if I'm just not allowed to partition a 1D region using a 3D index space, but I know if I have an int3d inside the field space, I can partition with:
  fill(thing.int3d_parameter, int3d({0,0,0}))
  var part = partition(thing.int3d_parameter, ispace(int3d, {5,5,5}))

with no issues.
I tried to grab a backtrace but even building regent with --debug this was the best I could get, not quite clear why
  [0] = /lib/x86_64-linux-gnu/libpthread.so.0(+0x12890) [0x7f314a192890]
  [1] = /lib/x86_64-linux-gnu/libc.so.6(gsignal+0xc7) [0x7f314901ee97]
  [2] = /lib/x86_64-linux-gnu/libc.so.6(abort+0x141) [0x7f3149020801]
  [3] = /lib/x86_64-linux-gnu/libc.so.6(+0x3039a) [0x7f314901039a]
  [4] = /lib/x86_64-linux-gnu/libc.so.6(+0x30412) [0x7f3149010412]
  [5] = /home/aidan/Legion/legion/bindings/regent/libregent.so(_ZNK6Legion6DomaincvN5Realm4RectIXT_ET0_EEILi1ExEEv+0x47) [0x7f3146e9c90d]
  [6] = /home/aidan/Legion/legion/bindings/regent/libregent.so(legion_domain_get_rect_1d+0x4b) [0x7f3146ef78a0]
  [7] = [0x7f314aa35454]
  [8] = [0x7f314aa34cdb]
  [9] = /home/aidan/Legion/legion/bindings/regent/libregent.so(+0x20b36d5) [0x7f3147c876d5]
  [10] = /home/aidan/Legion/legion/bindings/regent/libregent.so(+0x1ee387d) [0x7f3147ab787d]
  [11] = /home/aidan/Legion/legion/bindings/regent/libregent.so(+0x1ee88b4) [0x7f3147abc8b4]
  [12] = /home/aidan/Legion/legion/bindings/regent/libregent.so(+0x1ee68dc) [0x7f3147aba8dc]
  [13] = /home/aidan/Legion/legion/bindings/regent/libregent.so(+0x1eee5de) [0x7f3147ac25de]
  [14] = /home/aidan/Legion/legion/bindings/regent/libregent.so(+0x1ebe624) [0x7f3147a92624]
  [15] = /lib/x86_64-linux-gnu/libc.so.6(+0x586b0) [0x7f31490386b0]

Is this expected from Legion (so Regent could maybe prevent this call at compilation?) or is it a Regent bug?

This looks like a Legion bug to me, there's no particular reason why the element space and color space of an equal partition need to be the same dimensionality. (Though the partitions you get this way may look increasingly strange.)
Just FYI, you can probably get a better backtrace by running with LAUNCHER="gdb --args" ./regent.py test_file.rg. (Enter run and then backtrace once you hit the assert.) Realm's backtrace tool doesn't capture line numbers right now.

This is not a Legion bug, look at the backtrace:
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007ffff7a64859 in __GI_abort () at abort.c:79
#2  0x00007ffff7a64729 in __assert_fail_base (fmt=0x7ffff7bfa588 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n",
    assertion=0x7ffff6d92d01 "DIM == dim", file=0x7ffff6d92c7a "/home/mebauer/legion/runtime/legion/legion_domain.inl",
    line=1061, function=<optimized out>) at assert.c:92
#3  0x00007ffff7a75f36 in __GI___assert_fail (assertion=0x7ffff6d92d01 "DIM == dim",
    file=0x7ffff6d92c7a "/home/mebauer/legion/runtime/legion/legion_domain.inl", line=1061,
    function=0x7ffff6d9420a "Rect<DIM, T> Legion::Domain::operator Rect() const [DIM = 1, T = long long]") at assert.c:101
#4  0x00007ffff576d236 in _ZNK6Legion6DomaincvN5Realm4RectIXT_ET0_EEILi1ExEEv (this=0x7fffb01ff9f0)
    at /home/mebauer/legion/runtime/legion/legion_domain.inl:1061
#5  0x00007ffff57c1e90 in legion_domain_get_rect_1d (d_=...) at /home/mebauer/legion/runtime/legion/legion_c.cc:133
#6  0x00007ffff7fc8454 in ?? ()
#7  0x0000000000000000 in ?? ()

(gdb) p DIM
$1 = 1
(gdb) p dim
$2 = 3

Something on the regent side called legion_domain_get_rect_1d when it should have called legion_domain_get_rect_3d.

@elliottslaughter I just opened a PR for this that seems to handle everything I could throw at it. Please take a look. I'm not too familiar with this part of codegen so may have messed up the semantics...

Sorry it took so long, this has been fixed now.


(bedrock): adopt official cloudformation resources

Describe the feature
The Amazon Bedrock team recently released CloudFormation support. https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-bedrock-agent.html
Use Case
We can remove the bedrock custom resources.
Proposed Solution
No response
Other Information
No response
Acknowledgements

[ ] I may be able to implement this feature request
[X] This feature might incur a breaking change

Thank you @jstrunk , we will add it to the backlog

It looks like this relates to https://github.com/aws/aws-cdk/issues/29858