Issue/180

With this pull request i've implemented the following:

first commit is a simple fix to issue 180
the other commits implement a more complete solution that would require HumanizeDuration to integrate https://github.com/EvanHahn/HumanizeDuration.js/pull/55

@EvanHahn here you can find the integration extension for HumanizeDuration

.getSupportedLanguages() has been merged into the HumanizeDuration.js (as part of https://github.com/EvanHahn/HumanizeDuration.js/pull/55), so it might be worth re-running the CI build.
I didn't know about this library—glad to see someone integrating HumanizeDuration!

great @EvanHahn thanks! @siddii what about integratin this pull now that all is ready? :)

@evilaliv3 - Can you fix the tests please?

sure @siddii

the issue was simply that we need to update the library. i'm going to test it!

here you go! done! automagically the test will now work :)


Implement not dynamic delegate for ConfigureScope #511

Here is my PR for implementing the use of DECLARE_DELEGATE_OneParam for ConfigureScope #511
Converting FConfigureScopeDelegate to a non dynamic delegate might cause issues on migration of code for existing cpp users as now the cpp version of the implementation would be FConfigureScopeDynDelegate (but maybe could be good to make aware for people to replace their existing cpp code to use FConfigureScopeDelegate

Thanks for contributing and sorry for the delay, we'll get back to you as soon as possible.

Thanks for the reply, I got busy with other tasks so I didn't get the time to test it on mobile platforms but it should be ready for tests

@Maxmystere I've run some tests for this on my side and everything works perfectly. The only thing I'd like to suggest is to rename the newly added non-dynamic delegate to FConfigureScopeNativeDelegate instead of changing the existing dynamic one - it should allow us to avoid breaking things for those who are using the plugin's API in C++.

Thanks for the tests ! I've updated with what you asked, makes the review a bit bigger but yeah it's cleaner for people updating

Thanks for the tests ! I've updated with what you asked, makes the review a bit bigger but yeah it's cleaner for people updating

Great! I'll give it another go and get back to you.


Is the git tagging scheme applied as intended?

I see this PR was merged recently: https://github.com/OpenZeppelin/cairo-contracts/pull/493
But the result looks suspicious to me. E.g. browsing the repo at tag v0.5.0, the source file of IAccount has v0.4.0 specified in its SPDX comment.

That PR had a bug and we had to revert it to release. It will be reopened and properly fixed but in a future release.

@martriay Does the different SPDX comment (or actually any comment) affect the resulting class hash? I can check later, but just if you or somebody else already knows.

More importantly, which version will be whitelisted on mainnet? The one with the correct SPDX comment or the one coming from the correct git tag?

More importantly, which version will be whitelisted on mainnet? The one with the correct SPDX comment or the one coming from the correct git tag?

Hi @FabijanC, the one with the correct SPDX comment was the one sent to the whitelist.


Fix refs to data on web

base_url = "https://github.com/aeturrell/coding-for-economists/raw/refs/heads/general-hygiene/data/"  # TODO change to main post merge

closed in 718201c


Swift 3.0

Will you update?

There's already a swift3 branch here. I'll upgrade the master branch to swift 3 soon.


[BugFix] Using memcached on HHVM

This fix is specificly for HHVM, when adding servers there is an undefined index error.

I think this needs a more in depth analisys.

There are more occurrences of addServers($servers)
May this should be done in the return of $resource->getServerList()

@rms230 I'll close this due inactivity.

@Maks3w this closure's motivation is an internal role of @zendframework/community-review-team team? :)
Because into the ZF2 repo there are a lot of "inactive pr" :+1:

Re-opening. This corrects a number of issues on HHVM, bringing us closer to having the component work on that platform.

@weierophinney Seriously?

I think this needs a more in depth analisys.

There are more occurrences of addServers($servers)
May this should be done in the return of $resource->getServerList()

@Maks3w It's a start, which is far better than not taking it at all and leaving it completely uncorrected.

rm -rf P2P


NavSip.dll missing in SysWOW64 / Not able so sign App with SignTool.exe

PLEASE DO NOT INCLUDE ANY PASSWORDS OR TOKENS IN YOUR ISSUE!!!
Hi,
I was trying to copy the NavSip.dll to the local machine with ""Install-NAVSipCryptoProviderFromBcContainer"" and get the error:
`PS C:\Windows\system32> Install-NAVSipCryptoProviderFromBcContainer bcserver
Copy SIP crypto provider from container bcserver
Copy from container bcserver (C:\Windows\System32\NavSip.dll) to C:\Windows\System32\NavSip.dll
Copy from container bcserver (C:\Windows\SysWow64\NavSip.dll) to C:\Windows\SysWow64\NavSip.dll
Cannot find path 'C:\Windows\SysWow64\NavSip.dll' because it does not exist.
Exception Script Stack Trace:
bei Invoke-ScriptInBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\5.0.3\ContainerHandling\Invoke-ScriptInNavContainer.ps1: Zeile 61
bei Copy-FileFromBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\5.0.3\Misc\Copy-FileFromNavContainer.ps1: Zeile 39
bei Install-NAVSipCryptoProviderFromBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\5.0.3\AppHandling\Install-NAVSipCryptoProviderFromNavContainer.ps1: Zeile 44
bei , : Zeile 1
PowerShell Call Stack:
bei Invoke-ScriptInBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\5.0.3\ContainerHandling\Invoke-ScriptInNavContainer.ps1: Zeile 71
bei Copy-FileFromBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\5.0.3\Misc\Copy-FileFromNavContainer.ps1: Zeile 39
bei Install-NAVSipCryptoProviderFromBcContainer, C:\Program Files\WindowsPowerShell\Modules\BcContainerHelper\5.0.3\AppHandling\Install-NAVSipCryptoProviderFromNavContainer.ps1: Zeile 44
bei , : Zeile 1
Container Free Physical Memory: 5.6Gb
Services in container bcserver:

MicrosoftDynamicsNavServer$BC is Running
MSSQL$SQLEXPRESS is Running

C:\Windows\SysWow64\NavSip.dll doesn't exist.
C:\Windows\System32\NavSip.dll successfully registered.`
I originally tried so sign my BC App with the documentation from ssl.com: (can't sign the BC App with Powershell, since I the new certificate reglemantations don't let you export the private key and create a .pfx)
https://www.ssl.com/how-to/automate-ev-code-signing-with-signtool-or-certutil-esigner/
“C:\Program Files (x86)\Windows Kits\10\bin\10.0.22621.0\x86\signtool.exe” sign /fd sha256 /tr http://ts.ssl.com /td sha256 /sha1 XXXXXXX "C:\Users\Dell\Documents\Code\TEST\Default publisher_TEST_<IP_ADDRESS>.app"
I get the following error:

Any ideas how I can proceed? Right now I don't know how to sign AppFiles.
Thanks to anybode for help!

Thanks
This is a regression caused by a change in the Copy-File function.
a Fix should be ready in pre-release in 1-2 hours.

Hi Freddy,
thank you for the the fix in the newest prerelease. Running the "NASip" Command works fine now.
However my App File is still not being recognized by the Signtool.exe. I know this is slightly of topic, but do you have any idea what the issue could be?
I am still locking for a way so sign app files without using a .pfx (and hence the container helper command to sign).
Thank you!

Shipped in 5.0.4

Hi Freddy, thank you for the the fix in the newest prerelease. Running the "NASip" Command works fine now.
However my App File is still not being recognized by the Signtool.exe. I know this is slightly of topic, but do you have any idea what the issue could be? I am still locking for a way so sign app files without using a .pfx (and hence the container helper command to sign).
Thank you!

Same issue here after updating to 5.0.5.
Install-NAVSipCryptoProviderFromBcContainer sandbox1
Remove existing C:\Windows\System32\NavSip.dll
Copy SIP crypto provider from container sandbox1
Copy from container sandbox13 (C:\Windows\System32\NavSip.dll) to C:\Windows\System32\NavSip.dll
Copy from container sandbox13 (C:\Windows\SysWow64\NavSip.dll) to C:\Windows\SysWow64\NavSip.dll
C:\Windows\SysWow64\NavSip.dll doesn't exist.
C:\Windows\System32\NavSip.dll successfully registered.
Then executing signtool.exe
SignTool Error: This file format cannot be signed because it is not recognized.
SignTool Error: An error occurred while attempting to sign:

What is the status of this issue?
I also haven't been able to use this command for a long time because of this.


feat!: multi collateral support

Breaking changes

The vaults storage map now stores Option<Vault>, because Vault no longer implements default
secure_collateral_threshold, premium_redeem_threshold, liquidation_collateral_threshold and minimum_collateral_vault are now maps, mapping CurrencyId to the values.
The VaultRegistry::register_vault dispatchable function now takes an additional currency_id argument.
The Redeem::liquidation_redeem dispatchable function now takes an addition currency_id argument
The get_total_collateralization is for now not implemented -  see #221
wrapped_to_collateral and collateral_to_wrapped rpc functions now take an additional currency_id argument
added InvalidCurrency and ThresholdNotSet errors in vault-registry. Also NotImplemented, but this is only a temporary error - it will be removed once we decide on how to implement get_total_collateralization

We will need a new function to add a new collateral type.

@nud3l Currently this is not possible, since CurrencyId is an enum, so we require a runtime upgrade right now. We would have to make CurrencyId either some integer or  some string, e.g. "DOT". @gregdhill what do you think?

We will need a new function to add a new collateral type.

@nud3l Currently this is not possible, since CurrencyId is an enum, so we require a runtime upgrade right now. We would have to make CurrencyId either some integer or some string, e.g. "DOT". @gregdhill what do you think?

I would prefer to keep the enum, if and when we need to add new currencies we can perform a runtime upgrade. My reasons for this are as follows:

The current XCM standard (at least via tokens & xtokens) is to use CurrencyId which must be specified.
As stated by @sander2, allowing this via a function would require us to use some string or integer identifier which will be error-prone (no way to verify at compile time which currencies we support).
Same governance overhead for runtime upgrade vs single function call.
If we "authorize" particular currencies as collateral, there is no reason not to add as many types as possible up-front.

Yeah I think it probably makes sense to activate particular currencies as collateral, as you mentioned we may already have this implicitly when we check that the thresholds are set - this is configurable and explicitly updated by governance.


Tools mirror

Today's approach has some downsides:

Image builds sometime fail for periods if one of the hosts we download from is flaking
Self-hosted users who build their own image may not be allowed or find it easy to "open up ports" to so many hosts

Example of flakiness:
 > [test 13/17] RUN install-tool rust 1.69.0:
#42 0.214 installing v2 tool rust v1.69.0
#42 0.842 curl: (56) OpenSSL SSL_read: Connection reset by peer, errno 104
#42 0.845 Download failed: https://static.rust-lang.org/dist/rust-1.69.0-x86_64-unknown-linux-gnu.tar.gz

We should aim to have centralization and control of such dependencies where possible or necessary. I can think of two main possibilities:

We mirror everything onto github.com, probably as "Releases" because github doesn't yet support "generic" packages in its registry, or
We mirror everything statically onto e.g. S3 and essentially host a public mirror ourselves (paid for by Mend)

Obviously either way we still can have flakiness if our host (GitHub or CDN) has flakiness, but at least it's centralized flakiness and likely less than we get today

maven issues caused by ban^1

So our goal here is:

Every custom tool we have is downloadable via a single host we control (e.g. mirror.containerbase.org)
This mirror is resilient towards outages of its upstream hosts

If we can achieve this with reasonable cost efficiency, we could then default Containerbase to only use this host instead of the variety we have today.

Cloudflare's cache reserve is one approach to reducing requests to the origin server(s) and providing more resiliency for those which might have availability problems: https://developers.cloudflare.com/cache/advanced-configuration/cache-reserve/

          I've registered containerbase.dev just now and propose we aim to use cdn.containerbase.dev

Originally posted by @rarkins in https://github.com/containerbase/base/issues/1507#issuecomment-1733586167

Update: cdn.containerbase.dev is now ready
I would like to make this opt-in via CONTAINERBASE_CDN=https://cdn.containerbase.dev
Setting this would result in all known hosts to be redirected without the need for the http from/to being all set individually

Just to clarify: setting CONTAINERBASE_CDN=https://cdn.containerbase.dev/ should transform requests like https://example.com/foo/bar to the form like https://cdn.containerbase.dev/example.com/foo/bar

I was thinking that it would need to have an explicit list but I suppose you could add a general http rewrite rule? Might break if there's 30x responses though

https://github.com/containerbase/cdn/issues/27


omnisharp-vscode fails to load project with "It was not possible to find any installed .NET SDKs." [Solved]

I am posting this as it may be useful for someone else out there that hits this problem.
I thought it was an upgrade to my OS (upgraded to Big Sur on Mac OS) that did this. But in actual fact it was gitversion installed via brew that caused the issue, it created a dotnet directory in its Cellar directory and no matter what I did the later versions of dotnet core were ignored.
The issue that I was seeing is that Omnisharp was failing with an error stating it "It was not possible to find any installed .NET SDKs." therefore all Intellisense stopped working as did ability to launch debug from VS Code.
After a lot of digging and changing configuration I managed to isolate it down to the Cellar dotnet directory and then remembered I recently installed gitversion (hand to face). So removing gitversion command line (brew uninstall gitversion) and forced the removal of the dotnet cask, then reinstalled dotnet core and I am back in action. It seems that gitversion has a dependency on dotnet and it installs it rather than checking the system for already installed version...for what ever reason the installed version through brew cannot be detected by MS Build and hence the error above.

As above the issue is resolved, so closing it :-)


Custom callout moves to next marker

Is this a bug report?
Seems to be yes

Have you read the Installation Instructions?
yes
Environment

react-native: 0.59.5
"react-native-maps": "^0.24.2",
Steps to Reproduce

Created a react native map and used custom callouts. The callouts appear correctly when clicking on a marker... If I move the map and get near to another marker the callout from the previous one is shown

Expected Behavior

The callout stays over the original marker (or maybe closes)
Actual Behavior

The callout moves to the next marker
Reproducible Demo

(Paste the link to an example project and exact instructions to reproduce the issue.)

Does someone have an idea or a working example? Occures on both, Android and IOS...

Does anyone has an idea? It still occurs

@Wangor  got the solution?


[Code] The purpose of learnable broadcast sum in UnicornHead

Thanks for your job,as mentioned in title,did you do Ablations for the learnable broadcast

Hi, "learnable broadcast sum" performs almost the same as "direct broadcast sum". Both of them perform better than "broadcast multiplication". Thanks.


Add paramter for container registry sku

I guess that's correct. I think this part is exported from the Azure portal, which do include tier as well

It follows the example from the documentation https://docs.microsoft.com/en-us/azure/container-registry/container-registry-get-started-geo-replication-template
But I agree, it seems to not be necessary so I can remove it.


Recursive Fibonacci extremely slow on TI-Nspire

The recursive Fibonacci algorithm is very slow on the Nspire. I am using Duktape 1.2.1, and compiling with -O3.
Here is a minimal working example:
#include "duktape.h"

int main(void) {
  duk_context *ctx = duk_create_heap_default();
  duk_eval_string(ctx, "function f(n){if (n<=1) return n; else return f(n-1)+f(n-2)}print(f(30));");
  duk_destroy_heap(ctx);
  return 0;
}

Computing f(30) takes about 57 seconds. For comparison, here is a graph of computation times for various other languages available on this calculator: https://i.imgur.com/fBPlXr1.png. (We are using recursive Fibonacci as a benchmark.)

It's a known issue and can be seen here too:

https://github.com/svaarala/duktape/issues/138#issuecomment-86065937

There are several reasons for this. For example, self reference (function fib() { ... } refers to fib) causes an explicit scope object to be created, and returning involves a longjmp. These weren't yet addressed in #138.

Thanks. In that case, I won't worry about it now.

Call handling optimization will happen in 1.4 so moving there.

Does this apply to performance of simple polymorphic classes, as well? I've found the performance of entity lists (in the context of games, or game like applications,) to be a bit on the slow side. I have a pretty dumb example below, generated from CoffeeScript (using its inheritance mechanism). Basically, it does some work up front to create a list of entities, and then those entities are looped over having methods and overloaded methods called. My testing is actually on Android, so, for instance, that run() function is called from Java via JNI, a hundred times or so, after the script is compiled and init has been called. Just the run is being timed, though. Apologies for not having a fully working test case, the Android JNI makes it hairy to package that up for viewing. I'll trying get a simple C case if you like, that can run on desktop.
Sorry for the code dump, just super curious if this is related. Definitely want to use DukTape for this project (its been really fantastic, by the way,) but the performance here might be slightly limiting
// Generated by CoffeeScript 1.9.1
var Entities, Entity, Rabbit, Skunk, Spook, _create_main_object, init, update,
  extend = function(child, parent) { for (var key in parent) { if (hasProp.call(parent, key)) child[key] = parent[key]; } function ctor() { this.constructor = child; } ctor.prototype = parent.prototype; child.prototype = new ctor(); child.__super__ = parent.prototype; return child; },
  hasProp = {}.hasOwnProperty;

Entity = (function() {
  function Entity() {
    this.init_object();
    this.init();
  }

  Entity.prototype.act = function() {};

  Entity.prototype.ax = function() {
    return 0.0;
  };

  Entity.prototype.ay = function() {
    return 0.0;
  };

  Entity.prototype.update = function() {
    this.x += this.dx;
    this.y += this.dy;
    this.dx += this.ax();
    return this.dy += this.ay();
  };

  Entity.prototype.init_object = function() {
    this.x = 0.0;
    this.y = 0.0;
    this.dx = 1.0;
    this.dy = 1.0;
    return this;
  };

  Entity.prototype.init = function() {};

  return Entity;

})();

Entities = (function() {
  function Entities() {
    this.init_object();
    this.init();
  }

  Entities.prototype.init = function() {
    var k, results;
    results = [];
    for (k = 1; k <= 10000; k += 1) {
      switch (Math.random()*3 | 0) {
        case 0:
          results.push(this.entities.push(new Rabbit()));
          break;
        case 1:
          results.push(this.entities.push(new Skunk()));
          break;
        default:
          results.push(this.entities.push(new Spook()));
      }
    }
    return results;
  };

  Entities.prototype.update = function() {
    var k, len1, ref;
    ref = this.entities;
    for (k = 0, len1 = ref.length; k < len1; k++) {
      ref[k].update();
    }
  };

  Entities.prototype.init_object = function() {
    this.entities = [];
    return this;
  };

  return Entities;

})();

Rabbit = (function(superClass) {
  extend(Rabbit, superClass);

  function Rabbit() {
    this.init_object();
    this.init();
  }

  Rabbit.prototype.act = function() {
    return ++this.hops;
  };

  Rabbit.prototype.ax = function() {
    return 3.0;
  };

  Rabbit.prototype.ay = function() {
    return 3.0;
  };

  Rabbit.prototype.init_object = function() {
    Rabbit.__super__.init_object.call(this);
    this.hops = 0;
    return this;
  };

  return Rabbit;

})(Entity);

Skunk = (function(superClass) {
  extend(Skunk, superClass);

  function Skunk() {
    this.init_object();
    this.init();
  }

  Skunk.prototype.act = function() {
    this.scent += 0.03;
    if (this.scent > 1.0) {
      return this.scent = 1.0;
    }
  };

  Skunk.prototype.ax = function() {
    return 1.0;
  };

  Skunk.prototype.ay = function() {
    return 1.0;
  };

  Skunk.prototype.init_object = function() {
    Skunk.__super__.init_object.call(this);
    this.scent = 0.0;
    return this;
  };

  return Skunk;

})(Entity);

Spook = (function(superClass) {
  extend(Spook, superClass);

  function Spook() {
    this.init_object();
    this.init();
  }

  Spook.prototype.act = function() {
    if (this.psychokinetic_energy) {
      return --this.psychokinetic_energy;
    }
  };

  Spook.prototype.ax = function() {
    return 2.0;
  };

  Spook.prototype.ay = function() {
    return 2.0;
  };

  Spook.prototype.init_object = function() {
    Spook.__super__.init_object.call(this);
    this.psychokinetic_energy = 100;
    return this;
  };

  return Spook;

})(Entity);

_create_main_object = function() {
  this._main_object = new Entities();
  return this._main_object;
};

init = function() {
  return _create_main_object();
};

run = function() {
  return _main_object.update();
};

Call handling in general is a bit slow and there hasn't yet been an effort to improve it so it affects pretty much all calls. There should be low hanging fruits there though.

There are some call handling improvements in 1.4.0, but I didn't have time to implement all planned improvements for 1.4.0 so call performance work continues in 1.5.0.
The Fibonacci example above is bottlenecked by a slow path GETVAR lookup for the function self reference, see #401. Concretely:
// test1.js - takes about 3.0 sec in master (3.8 sec in 1.3.0)
function f(n){if (n<=1) return n; else return f(n-1)+f(n-2)};print(f(33));

By using a function expression the self reference is faster:
// test2.js - takes about 1.9 sec in master (2.3 sec in 1.3.0)
var f = function f(n){if (n<=1) return n; else return f(n-1)+f(n-2)};print(f(33));

Since the bottleneck is the GETVAR, could you improve the performance of the example by wrapping the whole thing in a self-executing function and binding f to a register?

Yes, performance is better if you avoid the GETVAR. But it's still important for the external function declaration to work well, because users probably expect that :)
Duktape's current scope handling is pretty simplistic: it uses ordinary objects to keep variables, with the internal prototype chain providing the scope nesting reference. Optimizing property performance will improve the scope performance too. Much better gains would be possible by making scopes separate internal objects, with accessors optimized to work with them. The downside of this is a larger code footprint and a lot of trivial changes here and there (e.g. in garbage collection), so I'm not yet sure which path is best. I'd at least want to take a couple of stabs at the property performance before making such a change.

Closing this issue because there's no specific change to be made - call handling performance is monitored in master and, like other performance stuff, it's being improved slowly over time.


Cicero-server not working offline: options are not passed to "Template.fromDirectory()" in "initTemplateInstance()"

Bug Report 🐛
When Template.fromDirectory() is called within initTemplateInstance() (in packages/cicero-server/app.js), the options are not passed.
This in particular prevents to use cicero-server offline.
Expected Behavior
When "offline" option is set true in the request body, cicero-server does not try to update external models.
Current Behavior
When "offline" option is set true in the request body, cicero-server tries anyway to update external models.
Steps to Reproduce

Install cicero-server as explained in the Readme.md
Do the Draft request call (it will download external models)
Go offline and do the following call:

curl --request POST \
  --url http://localhost:6001/draft/latedeliveryandpenalty \
  --header 'accept: application/json' \
  --header 'content-type: application/json' \
  --data '{
    "data": {
        "$class": "org.accordproject.latedeliveryandpenalty.LateDeliveryAndPenaltyContract",
        "contractId": "ecd6257e-2ffe-4ef1-8a5c-38ca9084a829",
        "buyer": {
            "$class": "org.accordproject.cicero.contract.AccordParty",
            "partyId": "Dan"
        },
        "seller": {
            "$class": "org.accordproject.cicero.contract.AccordParty",
            "partyId": "Steve"
        },
        "forceMajeure": true,
        "penaltyDuration": {
            "$class": "org.accordproject.time.Duration",
            "amount": 9,
            "unit": "days"
        },
        "penaltyPercentage": 1000.5,
        "capPercentage": 88,
        "termination": {
            "$class": "org.accordproject.time.Duration",
            "amount": 5,
            "unit": "weeks"
        },
        "fractionalPart": "days"
    },
    "options": {
        "unquoteVariables": true,
        "offline": true    <------------------------------ ADDED OPTION
    }
}'

The following error is returned:

Error: Failed to load model file. Job: https://models.accordproject.org/accordproject/contract.cto Details: Error: getaddrinfo EAI_AGAIN models.accordproject.org
    at PromisePoolExecutor.handleJobError [as errorHandler] (/usr/local/lib/node_modules/@accordproject/cicero-server/node_modules/@accordproject/concerto-core/lib/introspect/loaders/modelfiledownloader.js:31:11)
    at /usr/local/lib/node_modules/@accordproject/cicero-server/node_modules/@supercharge/promise-pool/dist/promise-pool-executor.js:154:29
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async Promise.all (index 0)
    at async PromisePoolExecutor.drainActiveTasks (/usr/local/lib/node_modules/@accordproject/cicero-server/node_modules/@supercharge/promise-pool/dist/promise-pool-executor.js:187:9)
    at async PromisePoolExecutor.drained (/usr/local/lib/node_modules/@accordproject/cicero-server/node_modules/@supercharge/promise-pool/dist/promise-pool-executor.js:177:9)
    at async PromisePoolExecutor.start (/usr/local/lib/node_modules/@accordproject/cicero-server/node_modules/@supercharge/promise-pool/dist/promise-pool-executor.js:85:16)
    at async APModelManager.updateExternalModels (/usr/local/lib/node_modules/@accordproject/cicero-server/node_modules/@accordproject/concerto-core/lib/modelmanager.js:276:36)
    at async APModelManager.addAPModelFiles (/usr/local/lib/node_modules/@accordproject/cicero-server/node_modules/@accordproject/ergo-compiler/lib/apmodelmanager.js:102:40)

Possible Implementation
Change initTemplateInstance() with something like:
async function initTemplateInstance(req) {
    let options = {};
    if(Object.prototype.hasOwnProperty.call(req.body,'options')) {
        options = req.body.options;
    }
    const template = await Template.fromDirectory(`${process.env.CICERO_DIR}/${req.params.template}`, options);
    return new Clause(template);
}

Thanks for the report. I agree that allowing Cicero server to be used offline would be useful. It sounds like adding a new environment variable to specify offline usage of the server would be a good idea?

Thanks for the report @mgiofinc 🙌
This support is now added for cicero-server. See the new template loading function: cicero-server/app.js#L273. When we merge open PRs for other methods, all of them will allow you to pass options in the request body.

Thanks for the update @mehmettokgoz.
Unfortunately it seems it only applies to /invoke/:template, but not to /trigger/:template, /parse/:template and /draft/:template.
Could it be extended also to them?

@mgiofinc Yes, that's right. I didn't refactor trigger, parse and draft yet but they will be updated accordingly. Additionally, initialize, normalize, get, compile, and archive methods have this support natively. You can see the implementations from cicero/pulls.

Hello and happy new year!
@mehmettokgoz I was wondering if it is there any update about the refactoring of  /trigger/:template, /parse/:template and /draft/:template.
Thanks in advance.

Hi!
Is someone still working on this?
If not can i ?
Thanks...

Hello,
I would love to contribute in this organization.
can I ?


SegmentWriter interface

Introducing the SegmentWriter and SegmentUploader interface as proposed in https://github.com/apache/incubator-pinot/issues/6610
SegmentWriter - collects GenericRow and creates a Pinot segment
SegmentUploader - uploads the segments from given path to the Pinot cluster

Codecov Report

Merging #6611 (9b446f6) into master (1beaab5) will decrease coverage by 0.88%.
The diff coverage is 62.57%.

@@            Coverage Diff             @@
##           master    #6611      +/-   ##
==========================================
- Coverage   66.44%   65.56%   -0.89%
==========================================
  Files        1075     1352     +277
  Lines       54773    66536   +11763
  Branches     8168     9694    +1526
==========================================
+ Hits        36396    43624    +7228
- Misses      15700    19797    +4097
- Partials     2677     3115     +438

Flag
Coverage Δ

unittests
65.56% <62.57%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...e/pinot/broker/api/resources/PinotBrokerDebug.java
0.00% <0.00%> (-79.32%)
:arrow_down:

...pinot/broker/api/resources/PinotClientRequest.java
0.00% <0.00%> (-27.28%)
:arrow_down:

...ot/broker/broker/AllowAllAccessControlFactory.java
71.42% <ø> (-28.58%)
:arrow_down:

.../helix/BrokerUserDefinedMessageHandlerFactory.java
33.96% <0.00%> (-32.71%)
:arrow_down:

...ker/routing/instanceselector/InstanceSelector.java
100.00% <ø> (ø)

...ava/org/apache/pinot/client/AbstractResultSet.java
66.66% <ø> (+9.52%)
:arrow_up:

...n/java/org/apache/pinot/client/BrokerResponse.java
100.00% <ø> (ø)

.../main/java/org/apache/pinot/client/Connection.java
35.55% <ø> (-13.29%)
:arrow_down:

...org/apache/pinot/client/DynamicBrokerSelector.java
82.85% <ø> (+10.12%)
:arrow_up:

...n/java/org/apache/pinot/client/ExecutionStats.java
68.88% <ø> (ø)

... and 1214 more

Continue to review full report at Codecov.

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

@yupeng9

Interface doesn't appear to have any get method, nor are the existing method returning any information. How will we get metadata information from interface: number of rows written so far, size of segment file, name of underlying implementation (like jdbc driver name). Can multiple threads use this interface to feed information into a segment?

@amrishlal Why do you need to get metadata information from SegmentWriter?
I think that those stats will be used internal implementation and as long as the implementation internally keeps those stats, we can generate segments.

@mcvsubbu would you please review again and unblock from merging?


python36Packages.shippai: 0.2.4 -> 0.3.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.6-shippai/versions.
meta.description for python36Packages.shippai is: '"Use Rust failures as Python exceptions"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.3.0 with grep in /nix/store/56vka0cmn5cfp22wr64n7jnbbspbfybx-python3.6-shippai-0.3.0

directory tree listing: https://gist.github.com/3867eeded6332f7477feae46ed6c2c16

du listing: https://gist.github.com/bb6ba0cef6bf3855c49faec4833135a4

Outpath report (click to expand)

Outpath difference report
16 total rebuild paths
4 package rebuilds
4 x86_64-linux rebuilds
4 i686-linux rebuilds
4 x86_64-darwin rebuilds
4 aarch64-linux rebuilds
First ten rebuilds by attrpath
khal
python27Packages.shippai
python36Packages.shippai
vdirsyncer

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/56vka0cmn5cfp22wr64n7jnbbspbfybx-python3.6-shippai-0.3.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A python36Packages.shippai https://github.com/r-ryantm/nixpkgs/archive/8b3f51a320290c1b6273cc5c123a9dd4449e8e8b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/56vka0cmn5cfp22wr64n7jnbbspbfybx-python3.6-shippai-0.3.0
ls -la /nix/store/56vka0cmn5cfp22wr64n7jnbbspbfybx-python3.6-shippai-0.3.0/bin

cc @gebner for testing.

Success on aarch64-linux (full log)
Attempted: python36Packages.shippai
Partial log (click to expand)
writing top-level names to shippai.egg-info/top_level.txt
reading manifest file 'shippai.egg-info/SOURCES.txt'
writing manifest file 'shippai.egg-info/SOURCES.txt'
running build_ext

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/irqp6n56gxia4nd9vdjaywgcs433ps9f-python3.6-shippai-0.3.0

Success on x86_64-darwin (full log)
Attempted: python36Packages.shippai
Partial log (click to expand)
writing top-level names to shippai.egg-info/top_level.txt
reading manifest file 'shippai.egg-info/SOURCES.txt'
writing manifest file 'shippai.egg-info/SOURCES.txt'
running build_ext

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/5i9sgsdaf29q4qnxfsq97i7h3dzn4v3f-python3.6-shippai-0.3.0

Success on x86_64-linux (full log)
Attempted: python36Packages.shippai
Partial log (click to expand)
writing top-level names to shippai.egg-info/top_level.txt
reading manifest file 'shippai.egg-info/SOURCES.txt'
writing manifest file 'shippai.egg-info/SOURCES.txt'
running build_ext

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/56vka0cmn5cfp22wr64n7jnbbspbfybx-python3.6-shippai-0.3.0

Failure on x86_64-linux (full log)
Attempted: vdirsyncer
Partial log (click to expand)
    'shippai_cast_error_{}'.format(name)
E   AttributeError: cffi library '/nix/store/g5fpg3d0mgsym5c0pdvb1rykmq67n5gw-vdirsyncer-0.17.0a3/lib/python3.6/site-packages/vdirsyncer/_native__lib.so' has no function, constant or global variable named 'shippai_cast_error_DavError'
=========================== slowest 3 test durations ===========================
0.24s call     tests/storage/test_singlefile.py::TestSingleFileStorage::test_generic[VCARD]
0.19s call     tests/storage/test_singlefile.py::TestSingleFileStorage::test_generic[VTODO]
0.18s call     tests/storage/test_singlefile.py::TestSingleFileStorage::test_generic[VEVENT]
============== 30 failed, 163 passed, 102 skipped in 4.41 seconds ==============
make: *** [Makefile:78: storage-test] Error 1
builder for '/nix/store/dzsfl0c5mai9lzghrya35rf8si1dz085-vdirsyncer-0.17.0a3.drv' failed with exit code 2
error: build of '/nix/store/dzsfl0c5mai9lzghrya35rf8si1dz085-vdirsyncer-0.17.0a3.drv' failed

Failure on aarch64-linux (full log)
Attempted: vdirsyncer
Partial log (click to expand)
    'shippai_cast_error_{}'.format(name)
E   AttributeError: cffi library '/nix/store/28n2l6ibwnyqrkcz94kwvyg3cnjpm67z-vdirsyncer-0.17.0a3/lib/python3.6/site-packages/vdirsyncer/_native__lib.so' has no function, constant or global variable named 'shippai_cast_error_DavError'
=========================== slowest 3 test durations ===========================
0.09s call     tests/storage/test_singlefile.py::TestSingleFileStorage::test_generic[VCARD]
0.07s call     tests/storage/test_singlefile.py::TestSingleFileStorage::test_generic[VTODO]
0.06s call     tests/storage/test_singlefile.py::TestSingleFileStorage::test_generic[VEVENT]
============== 30 failed, 163 passed, 102 skipped in 4.19 seconds ==============
make: *** [Makefile:78: storage-test] Error 1
builder for '/nix/store/qvsmvhbyn2djsgcfjnjxlp00if60lgpa-vdirsyncer-0.17.0a3.drv' failed with exit code 2
error: build of '/nix/store/qvsmvhbyn2djsgcfjnjxlp00if60lgpa-vdirsyncer-0.17.0a3.drv' failed


Unbind-key -a makes using cmdline, search, and goto-url impossible

[Output of newsboat -v]
newsboat r2.14.1-8-gf03c - https://newsboat.org/
Copyright (C) 2006-2015 Andreas Krennmair
Copyright (C) 2015-2019 Alexander Batischev
Copyright (C) 2006-2017 Newsbeuter contributors
Copyright (C) 2017-2019 Newsboat contributors
Newsboat is free software licensed under the MIT License. (Type `newsboat -vv' to see the full text.)
It bundles JSON for Modern C++ library, licensed under the MIT License: https://github.com/nlohmann/json
It bundles an alphanum algorithm implementation licensed under the MIT license: http://www.davekoelle.com/alphanum.html
newsboat r2.14.1-8-gf03c
System: Linux 4.20.10-arch1-1-ARCH (x86_64)
Compiler: g++ 8.2.1 20181127
ncurses: ncurses 6.1.20180127 (compiled with 6.1)
libcurl: libcurl/7.64.0 OpenSSL/1.1.1a zlib/1.2.11 libidn2/2.1.1 libpsl/0.20.2 (+libidn2/2.1.1) libssh2/1.8.0 nghttp2/1.36.0 (compiled with 7.64.0)
SQLite: 3.27.1 (compiled with 3.27.1)
libxml2: compiled with 2.9.9
[Recreating the Issue]
I edited the config file and unbound all default keybindings with "unbind-key -a"
I then added keybindings for all relevant keys, including ENTER and ESC (For open and quit respectively)
However, upon loading newsboat and starting the cmdline (using ':' ), there is no way to actually send that command to newsboat. Pressing ESC does nothing as well.
[Other Details]
With default keybindings, if I open the command line and enter an invalid command (and use ENTER to send it through), newsboat will tell me it's not a valid command. Upon pressing ESC, I can cancel out of that dialog. However unbinding all keys removes those functionalities, even if I rebind ENTER and ESC back to open and quit respectively.
I have not been able to get it working by tweaking what commands ENTER and ESC are bound to. I also tried tweaking what specific dialogs I unbound all keys from, and I found that only if I unbind keys from "feedlist" can I recreate this issue. Unbinding keys from any of the other dialogs does not recreate the issue. However, even when I specifically bound the ENTER and ESC keys to open/quit in the feedlist dialog, the issue persists.
All of the above issues apply also doing anything in newsboat that requires you to manually type/enter something, such as searching and goto-url.

Thank you for the report.
Looks like the problem is within a territory of my feature. I will hopefully take a look in a few days.

I ended up testing this as well, here's reproduction steps for future reference:

create Newsboat config with the following:
unbind-key -a
bind-key : cmdline

start Newsboat with that config;

press : to enter command line;

press Esc to leave command line.

The expected behaviour is for ":" at the bottom of the screen to disappear. The actual behaviour: colon doesn't disappear, all further keystrokes are entered into the command line.


__align private field in in6_addr

Hi, is there any reason why __align is declared in in6_addr?  As of now it is preventing in6_addr struct to be created.

Ah yeah this is unfortunately because we don't support unions in a great way right now, I'd recommend creating instances via mem::zeroed or mem::uninitialized and then initializing each member individually (as you would in C). Eventually I hope to remove these fields though!


Updated bolding

two list items were missing the same format as the first item in the list. This change makes it more clear when viewing the list.

@mcvic1rj : Thanks for your contribution! The author, @MicrosoftGuyJFlo, has been notified to review your proposed change.

hmm that seems a bit weird. I was just reading  the article and skipped over the other two because they were not bolded and had to go back and look for them.
@MicrosoftGuyJFlo What about using a bulleted list instead in order to call out each of the different options?

@mcvic1rj Ill go ahead and approve this and keep an eye on how it performs. Sorry for the delay I have been out for MS Ignite and vacation.

#sign-off


Can I build a simple forum use for learning go and meeting gopher ?

Can I do that via http://www.google.com/permissions/

Please ask questions on the golang-nuts mailing list.


thousandeyes_http_server returns 400 when specifying alert_rules

I am getting 400 errors when creating/updating a thousandeyes_http_server resource with alerts_enabled set to true and alert_rules specified or unspecified
Terraform and provider version
Terraform: 0.13.7 and 1.1.7
Provider: thousandeyes/thousandeyes version 1.0.0-alpha.3

Expected behavior
thousandeyes_http_server resources are successfully created/updated when specifying alert rules via alert rule ID
Actual behavior
Setting alerts_enabled to true and specifying an alert_rule block with a valid rule ID results in Error: Failed call API endpoint. HTTP response code: 400. Error: &{0xc000228c10}
What works:
When alerts_enabled is set to false with no alert_rules specified, this creates the resource as expected:
resource "thousandeyes_http_server" "example" {
  test_name      = "tf test"
  interval       = 3600
  alerts_enabled = false
  url            = "redacted-url"

  agents {
    agent_id = 69
  }
}

What doesn't work:
Simply setting alerts_enabled to true returns a 400. I'd expect this to use the default alert rules in this case based on the wording in the documentation
Manually setting the alert rules in the web UI and updating the Terraform code accordingly reports no changes: Apply complete! Resources: 0 added, 0 changed, 0 destroyed.
resource "thousandeyes_http_server" "example" {
  test_name      = "tf test"
  interval       = 3600
  alerts_enabled = false
  url            = "redacted-url"

  agents {
    agent_id = 69
  }

  alert_rules {
    rule_id = 4795258
  }
  alert_rules {
    rule_id = 4795254
  }
}

Removing one of the alert_rules also returns a 400:
resource "thousandeyes_http_server" "example" {
  test_name      = "test"
  interval       = 3600
  alerts_enabled = false
  url            = "redacted-url"

  agents {
    agent_id = 69
  }

  alert_rules {
    rule_id = 4795258
  }
}

The plan shows only the following change:
      - alert_rules {
          - alert_rule_id             = 0 -> null
          - default                   = 0 -> null
          - include_covered_prefixes  = 0 -> null
          - minimum_sources           = 0 -> null
          - minimum_sources_pct       = 0 -> null
          - notify_on_clear           = 0 -> null
          - rounds_violating_out_of   = 0 -> null
          - rounds_violating_required = 0 -> null
          - rule_id                   = 4795254 -> null
          - test_ids                  = [] -> null
        }

The apply fails with the following error: Error: Failed call API endpoint. HTTP response code: 400. Error: &{0xc000228c10}
Please let me know if there's other relevant information I can provide to help with this.

Thanks for reporting this issue, @Saffron-City. I a have a fix underway and will open a pull request shortly.


Write rebar3.crashdump on errors

I do prefer the DEBUG=1 for contextual output, though.

this does not change the behavior of DEBUG=1 or the error message, it simply adds a rebar3.crashdump to the cases where a DEBUG=1 message was formerly printed.

WOuld that also drop files over the filesystem when run in API mode? I don't really like that.

Updated it so the sentences are nicer and it will recognize api mode and not write a crash file

+1 on this. Does not sound like a bad idea.


Feature Request: Allow manifests to specify minimum director and CLI versions

As part of cf-deployment, we'd like to be able to encode in the manifest the minimum compatible versions of the BOSH Director and the CLI.
In the past, we've had to build out compatibility matrices, or leave notes in release notes of cf-release. We really like the pattern that has emerged from cf-deployment, where the manifest itself contains the information about which releases and stemcells are considered compatible. We'd like to extend that UX to BOSH compatibility as well.
This is especially valuable because we want to stay on top of integrating against new BOSH features -- both on the Director and the CLI. For example, our compiled-releases ops-file depends on BOSH CLI 2.0.30, but there's not an easy place to specify that. Just a few weeks later, cf-deployment started to depend on CLI 2.0.42 to use the :before/:after syntax in ops-files.
Proposal
I can specify something like this in the manifest:
---
name: cf
minimum_bosh_director: 263.3.0
minimum_bosh_cli: 2.0.42
instance_groups:
...

And see the following behaviors:

If the BOSH CLI version is less that 2.0.42, the BOSH CLI should return some error, asking the user to upgrade their CLI.
If the targeted BOSH Director is less than 263.3.0, the BOSH CLI (or BOSH director, perhaps) should return an error, asking the user to upgrade their director.
Otherwise, the deployment should proceed as planned.

Definitely. I would like to remember our friends who don't have directors yet and suggest following additional behavior

If I run bosh create-env bosh.yml and the minimum_bosh_cli specified in bosh.ymlis higher thanbosh version` then the cli should return some error, asking the user to upgrade their CLI.
director version is ignored by create-env


[Snyk] Upgrade mocha from 10.1.0 to 10.2.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade mocha from 10.1.0 to 10.2.0.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 1 version ahead of your current version.
The recommended version was released 21 days ago, on 2022-12-11.

Release notes

Package name: mocha

10.2.0 - 2022-12-1110.2.0 / 2022-12-11
🎉 Enhancements

#4945: API: add possibility to decorate ESM name before import (@ j0tunn)

🐛 Fixes

#4946: Browser: color of failed test icon (@ kleisauke)

📖 Documentation

#4944: Remove duplicated header (@ PauloGoncalvesBH)

10.1.0 - 2022-10-1510.1.0 / 2022-10-16
🎉 Enhancements

#4896: Browser: add support for prefers-color-scheme: dark (@ greggman)

🔩 Other

#4912: Browser: increase contrast for replay buttons (@ JoshuaKGoldberg)
#4905: Use standard Promise.allSettled instead of polyfill (@ outsideris)
#4899: Upgrade official GitHub actions to latest (@ ddzz)
#4770: Fix regex in function clean(@ yetingli)

    from mocha GitHub release notes

Commit messages

Package name: mocha

202e9b8 build(v10.2.0): release
6782d6d build(v10.2.0): update CHANGELOG
73bb819 feat(esm): ability to decorate ESM module name before importing it (#4945)
fc4ac58 chore(devDeps): remove unused depedencies (#4949)
0a10ddc docs: remove duplicated header (#4944)
b0a0fb8 fix(browser): failed test icon color (#4946)
3cc9cac ci: update stale action (#4931)
8f3c37b chore(ci): workaround for firefox error (#4933)

Compare

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

LGTM


Add handling for unknown errors from the server

@ish2028, can you please provide the stack trace from Sentry that you believed was caused by this issue?

This is the error that appears and it's caused by a 504 from the API

{"event_id":"e745b98dad6d408b8c4c3bb7a448c053","project":1479867,"release":"keiser.metrics.facility.web@1.17.2","dist":null,"platform":"javascript","message":"","datetime":"2021-06-22T09:11:32.534000Z","tags":[["browser","Chrome 91.0.4472"],["browser.name","Chrome"],["environment","production"],["handled","no"],["level","error"],["mechanism","onunhandledrejection"],["os","Windows 10"],["os.name","Windows"],["release","keiser.metrics.facility.web@1.17.2"],["user","ip:<IP_ADDRESS>"],["url","https://metrics.keiser.com/facility/app/account/dashboard/members"]],"metrics":{"bytes.ingested.event":3989,"bytes.stored.event":10887},"breadcrumbs":{"values":[{"timestamp":1624352460.576,"type":"http","category":"xhr","level":"info","data":{"method":"GET","status_code":200,"url":"assets/i18n/en.json"}},{"timestamp":1624352462.507,"type":"default","category":"navigation","level":"info","data":{"from":"/facility/#/app/account/1/dashboard/session-plan-template/list","to":"/facility/"}},{"timestamp":1624352462.511,"type":"default","category":"navigation","level":"info","data":{"from":"/facility/","to":"/facility/facility-selection"}},{"timestamp":1624352462.513,"type":"default","category":"navigation","level":"info","data":{"from":"/facility/facility-selection","to":"/facility/facility-selection"}},{"timestamp":1624352462.515,"type":"default","category":"navigation","level":"info","data":{"from":"/facility/facility-selection","to":"/facility/"}},{"timestamp":1624352462.517,"type":"default","category":"navigation","level":"info","data":{"from":"/facility/","to":"/facility/"}},{"timestamp":1624352462.533,"type":"default","category":"navigation","level":"info","data":{"from":"/facility/","to":"/facility/app/facility-selection"}},{"timestamp":1624352465.571,"type":"default","category":"ui.click","level":"info","message":"div.p-20 > div.km-select > select.ng-untouched.ng-pristine.ng-valid"},{"timestamp":1624352466.939,"type":"default","category":"navigation","level":"info","data":{"from":"/facility/app/facility-selection","to":"/facility/app/account/dashboard/facility-check-in-out"}},{"timestamp":1624352472.435,"type":"default","category":"ui.click","level":"info","message":"li.ng-tns-c77-0 > div.side-bar-link.ng-tns-c77-0 > span.ng-tns-c77-0"},{"timestamp":1624352472.457,"type":"default","category":"navigation","level":"info","data":{"from":"/facility/app/account/dashboard/facility-check-in-out","to":"/facility/app/account/dashboard/help"}},{"timestamp":1624352991.895,"type":"default","category":"ui.click","level":"info","message":"div.side-bar-link.ng-tns-c77-0 > span.ng-tns-c77-0"},{"timestamp":1624352991.909,"type":"default","category":"navigation","level":"info","data":{"from":"/facility/app/account/dashboard/help","to":"/facility/app/account/dashboard/equipment"}},{"timestamp":1624353091.399,"type":"default","category":"ui.click","level":"info","message":"li.ng-tns-c77-0 > div.side-bar-link.ng-tns-c77-0 > span.ng-tns-c77-0"},{"timestamp":1624353091.405,"type":"default","category":"navigation","level":"info","data":{"from":"/facility/app/account/dashboard/equipment","to":"/facility/app/account/dashboard/members"}},{"timestamp":1624353092.523,"type":"http","category":"xhr","level":"info","data":{"method":"POST","status_code":504,"url":"https://metrics-api.keiser.com/api?action=facilityConfiguration:show"}},{"timestamp":1624353092.525,"type":"http","category":"xhr","level":"info","data":{"method":"POST","status_code":504,"url":"https://metrics-api.keiser.com/api?action=facilityRelationship:facilityList"}},{"timestamp":1624353092.533,"type":"default","category":"sentry.event","level":"error","message":"TypeError: Cannot read property 'code' of undefined","event_id":"89a65fcba08047058edbba4fde8d43b2"}]},"contexts":{"browser":{"name":"Chrome","version":"91.0.4472","type":"browser"},"os":{"name":"Windows","version":"10","type":"os"}},"culprit":"Array.find()","environment":"production","exception":{"values":[{"type":"TypeError","value":"Cannot read property 'code' of undefined","stacktrace":{"frames":[{"function":"t.MetricsConnection.actionRest","module":"@keiser/metrics-sdk/index.browser","filename":"webpack:/node_modules/@keiser/metrics-sdk/index.browser.js","abs_path":"webpack:/node_modules/@keiser/metrics-sdk/index.browser.js","lineno":2,"colno":113965,"pre_context":["/*! For license information please see index.browser.js.LICENSE.txt /"],"context_line":"{snip} e?void 0:e.response)||void 0===i?void 0:i.data)){const t=c.GetErrorInstance(e.response.data.error);t instanceof c.RequestError||t instanceof {snip}","in_app":false,"data":{"sourcemap":"https://metrics.keiser.com/facility/main-es2018.4f9c7bdb70ff73334193.js.map"}},{"function":"GetErrorInstance","module":"@keiser/metrics-sdk/index.browser","filename":"webpack:/node_modules/@keiser/metrics-sdk/index.browser.js","abs_path":"webpack:/node_modules/@keiser/metrics-sdk/index.browser.js","lineno":2,"colno":116141,"pre_context":["/! For license information please see index.browser.js.LICENSE.txt */"],"context_line":"{snip} st t=[o,c,h,l,u,d,g,f,p,y,,m,w,x,S,b,D,E,v,M,A,k,O,R,C,P].find((t=>t.code===e.code));return void 0!==t?new t(e):new n(e)};class i extends s {snip}","in_app":false,"data":{"sourcemap":"https://metrics.keiser.com/facility/main-es2018.4f9c7bdb70ff73334193.js.map"}},{"function":"Array.find","filename":"","abs_path":"","in_app":true},{"module":"@keiser/metrics-sdk/index.browser","filename":"webpack:/node_modules/@keiser/metrics-sdk/index.browser.js","abs_path":"webpack:/node_modules/@keiser/metrics-sdk/index.browser.js","lineno":2,"colno":116161,"pre_context":["/*! For license information please see index.browser.js.LICENSE.txt */"],"context_line":"{snip} f,p,y,,m,w,x,S,b,D,E,v,M,A,k,O,R,C,P].find((t=>t.code===e.code));return void 0!==t?new t(e):new n(e)};class i extends s{}t.RequestError=i;c {snip}","in_app":false,"data":{"sourcemap":"https://metrics.keiser.com/facility/main-es2018.4f9c7bdb70ff73334193.js.map"}}]},"raw_stacktrace":{"frames":[{"function":"t.MetricsConnection.actionRest","filename":"/facility/main-es2018.4f9c7bdb70ff73334193.js","abs_path":"https://metrics.keiser.com/facility/main-es2018.4f9c7bdb70ff73334193.js","lineno":1,"colno":723320,"context_line":"{snip} e?void 0:e.response)||void 0===i?void 0:i.data)){const t=c.GetErrorInstance(e.response.data.error);t instanceof c.RequestError||t instanceof {snip}","post_context":["//# sourceMappingURL=main-es2018.4f9c7bdb70ff73334193.js.map"],"in_app":false},{"function":"Object.t.GetErrorInstance","filename":"/facility/main-es2018.4f9c7bdb70ff73334193.js","abs_path":"https://metrics.keiser.com/facility/main-es2018.4f9c7bdb70ff73334193.js","lineno":1,"colno":725496,"context_line":"{snip} st t=[o,c,l,u,h,d,f,p,g,m,y,,b,v,w,S,E,x,D,O,C,M,A,P,k,T].find(t=>t.code===e.code);return void 0!==t?new t(e):new a(e)};class i extends n{} {snip}","post_context":["//# sourceMappingURL=main-es2018.4f9c7bdb70ff73334193.js.map"],"in_app":false},{"function":"Array.find","filename":"","abs_path":"","in_app":true},{"filename":"/facility/main-es2018.4f9c7bdb70ff73334193.js","abs_path":"https://metrics.keiser.com/facility/main-es2018.4f9c7bdb70ff73334193.js","lineno":1,"colno":725515,"context_line":"{snip} ,p,g,m,y,_,b,v,w,S,E,x,D,O,C,M,A,P,k,T].find(t=>t.code===e.code);return void 0!==t?new t(e):new a(e)};class i extends n{}t.RequestError=i;cl {snip}","post_context":["//# sourceMappingURL=main-es2018.4f9c7bdb70ff73334193.js.map"],"in_app":false}]},"mechanism":{"type":"onunhandledrejection","handled":false}}]},"fingerprint":["{{ default }}"],"grouping_config":{"enhancements":"eJybzDRxY05qemJypZWRgaGlroGxrqHRBABbKAcD","id":"legacy:2019-03-12"},"hashes":["db8266d9c28cb295f491c295b6956f0c"],"key_id":"858212","level":"error","location":"","logger":"","metadata":{"filename":"","function":"Array.find","type":"TypeError","value":"Cannot read property 'code' of undefined"},"received":1624353092.880818,"request":{"url":"https://metrics.keiser.com/facility/app/account/dashboard/members","headers":[["User-Agent","Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.106 Safari/537.36"]]},"sdk":{"name":"sentry.javascript.angular","version":"6.3.6","integrations":["InboundFilters","FunctionToString","TryCatch","Breadcrumbs","GlobalHandlers","LinkedErrors","UserAgent"],"packages":[{"name":"npm:@sentry/angular","version":"6.3.6"}]},"timestamp":1624353092.534,"title":"TypeError: Cannot read property 'code' of undefined","type":"error","user":{"ip_address":"<IP_ADDRESS>","geo":{"country_code":"ZA","city":"Durban","region":"South Africa"}},"version":"7"}


Support Twemoji (Or allow running scripts on load)

A straightforward method is to allow running twemoji.parse() on the container of the emojis. Able to run it after importing the script tag here. However, I cannot do it myself due to the shadow DOM.

This is actually something I explicitly didn't want to support – for performance and simplicity reasons, emoji-picker-element is designed to use the browser's built-in emoji.
I've considered supporting emoji fonts (#82) but the browser support is not great right now, and Firefox and Chrome both implement competing standards. Maybe someday this will make sense.
I'm curious to know why you want twemoji?

I'm curious to know why you want twemoji?

Basically, I really dislike the look of emojis on windows specifically- plus I've noticed emojis have irregular padding in text on some systems so sometimes it looks a bit off. On GitHub for example, I think they use default and for me, with "🏡a", the emoji bleeds into the text directly next.

To add to this, some users running my webapp aren't on the latest system update and cannot see specific emojis without twemoji or some other replacement font.

emoji-picker-element should automatically filter out unsupported emoji so you don't see the empty boxes. As for the padding issue you mention, I take it that that occurs with inline text and not in emoji-picker-element specifically?
I suppose I'm arguing that you could use native emoji for the picker, and Twemoji elsewhere in your app, but I understand if you'd prefer to have the same unified experience everywhere. When color fonts are available cross-browser, I may be interested in adding a generic way for emoji-picker-element to support that. (#82)

As for the padding issue you mention, I take it that that occurs with inline text and not in emoji-picker-element specifically?

That's correct - seems to be a general emoji issue on MacOS specifically.

When color fonts are available cross-browser, I may be interested in adding a generic way for emoji-picker-element to support that. (#82)

Sounds good. Issue is definitely low-urgency as native emoji in the picker is suitable.

I hope this support comes, because it's better that we see the same emoji designs on every device. The user should not see different design emoji between windows and macos.

The user should not see different design emoji between windows and macos.

I think this is debatable – arguably, iOS users are accustomed to seeing the iOS emoji, and it's weird for them to see some other design. Ditto for Android and Windows users. Sadly the state of emoji support across browsers and OSes is bad enough (e.g. Windows rendering flag emoji as letters) that most chat apps seem to want to just bring their own emoji everywhere.
A primary goal of this project is to optimize for performance, preferring native browser support wherever possible. Twemoji is a stretch, but I still think color font support would be pretty reasonable (doesn't require <img>s instead of text, is basically just a CSS change). However the browsers still don't agree on a color font format: https://github.com/nolanlawson/emoji-picker-element/issues/82#issuecomment-1045260517

I looked into it, and it is possible to use Twemoji with emoji-picker-element. There is definitely a perf cost, and you'd probably want to host the image files yourself and do some other tweaks, but you can do it. Added a link to a demo to the README.

Perfect- got it working. Though, consider adding a note to use pointer-events: none on the twemoji images so that click events still fire.


TypeError: Cannot read property '_serverPromise' of undefined

Getting this error. not sure from where.
TypeError: Cannot read property '_serverPromise' of undefined
    at close$ (/Users//home/user/test/node_modules/promised-mongo/dist/Database.js:123:22)
    at tryCatch (/Users//home/user/test/node_modules/babel-runtime/regenerator/runtime.js:72:40)
    at Generator.invoke [as _invoke] (/Users//home/user/test/node_modules/babel-runtime/regenerator/runtime.js:334:22)
    at Generator.prototype.(anonymous function) [as next] (/Users//home/user/test/node_modules/babel-runtime/regenerator/runtime.js:105:21)
    at tryCatch (/Users//home/user/test/node_modules/babel-runtime/regenerator/runtime.js:72:40)
    at invoke (/Users//home/user/test/node_modules/babel-runtime/regenerator/runtime.js:146:20)
    at /Users//home/user/test/node_modules/babel-runtime/regenerator/runtime.js:191:11
    at F (/Users//home/user/test/node_modules/core-js/library/modules/$.export.js:30:36)
    at callInvokeWithMethodAndArg (/Users//home/user/test/node_modules/babel-runtime/regenerator/runtime.js:190:16)
    at AsyncIterator.enqueue [as _invoke] (/Users//home/user/test/node_modules/babel-runtime/regenerator/runtime.js:211:37)
    at AsyncIterator.prototype.(anonymous function) [as next] (/Users//home/user/test/node_modules/babel-runtime/regenerator/runtime.js:105:21)
    at Object.runtime.async (/Users//home/user/test/node_modules/babel-runtime/regenerator/runtime.js:228:12)
    at close (/Users//home/user/test/node_modules/promised-mongo/dist/Database.js:118:34)

My bad. had to bind to db: this.db.close.bind(this.db) in my callback


Migrate to System.Reactive

Hi,
Have been playing around with EtwStream and it is looking really good. Much easier to use than some other alternatives. It would be good to migrate from Rx-Main to the System.Reactive.* nuget packages if possible.
Cheers,
Isaac

Thank you.
Yes, I should do it!

I've uploaded 1.3.3!


fix: error when running zk init

Resolves #689.
What ❔

This PR fixes zk init cmd. Updating the path to the volume passed to the docker run --rm -v cmd in infrastructure/zk/src/down.ts.
Why ❔

The change mentioned above is made because the command docker run -v does not accept a relative paths but absolute paths, and ./volumes/... is being passed on line 7 of the mentioned file.
If you clone this repo and run zk init after installing zk, you'll see something like this:
docker: Error response from daemon: create ./volumes: "./volumes" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path.
See 'docker run --help'.
Error: Child process exited with code 125
error Command failed with exit code 1.

Checklist

[x] PR title corresponds to the body of PR (we generate changelog entries from PRs).
[ ] Tests for the changes have been added / updated.
[ ] Documentation comments have been added / updated.
[x] Code has been formatted via zk fmt and zk lint.
[x] Spellcheck has been run via cargo spellcheck --cfg=./spellcheck/era.cfg --code 1.

There's a chance that we should update the workflows files too, waiting to see if the CI fails.


Add ability to read pixels

Add POINT(x,y) which reads either the pixel at the screen, or the lower 4 bits in sprite mode.

Added


[Doc Improvement][Add a link in see also of publish app overview][2809656]

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/apps-publish-overview.md
96
2
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Learn Build status updates of commit 3deae0e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/concepts/deploy-and-publish/apps-publish-overview.md
:white_check_mark:Succeeded
View

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

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/apps-publish-overview.md
96
2
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/concepts/deploy-and-publish/apps-publish-overview.md
96
2
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.


Compiling nolonger works

just start getting this ...
am_fix.c:118:2: error: expected '}' before 'const'
118 |  const unsigned int original_index = 1;
|  ^~~~~
am_fix.c:105:2: note: to match this '{'
105 |  {
|  ^
am_fix.c:104:35: error: 'am_fix_gain_table' defined but not used [-Werror=unused-const-variable=]
104 |  static const t_am_fix_gain_table am_fix_gain_table[] =
|                                   ^~~~~~~~~~~~~~~~~
am_fix.c:100:23: error: 'pga_dB' defined but not used [-Werror=unused-const-variable=]
100 |  static const int16_t pga_dB[]       = {-33, -27, -21, -15, -9, -6, -3, 0};
|                       ^~~~~~
am_fix.c:99:23: error: 'mixer_dB' defined but not used [-Werror=unused-const-variable=]
99 |  static const int16_t mixer_dB[]     = { -8,  -6,  -3,   0};
|                       ^~~~~~~~
am_fix.c:98:23: error: 'lna_dB' defined but not used [-Werror=unused-const-variable=]
98 |  static const int16_t lna_dB[]       = {-24, -19, -14,  -9, -6, -4, -2, 0};
|                       ^~~~~~
am_fix.c:97:23: error: 'lna_short_dB' defined but not used [-Werror=unused-const-variable=]
97 |  static const int16_t lna_short_dB[] = {-33, -30  -24,   0};   // corrected'ish
|                       ^~~~~~~~~~~~
cc1.exe: all warnings being treated as errors
make: *** [am_fix.o] Error 1
D:_______\uv-k5-firmware-custom>del /S /Q *.o  1>nul 2>nul
Been happening since around the last 3 sets of commits on GH
this happens even when using the win_make.bat

Forgot to add '};'
That test option is just a temporary bit if code to let me test the front end registers.

Forgot to add '};'
That test option is just a temporary bit if code to let me test the front end registers.

Arrr ok no worries
https://github.com/OneOfEleven/uv-k5-firmware-custom/assets/48331155/099e7097-aef7-486d-9fad-8bbf05605343
On the plus side the prebuilt bin file you have uplaoded is now the best I have heard from your fw in some time

Thank you for re-adding the compile option... what options do yu have enabled/disabled in the preconfig firmware file on GH??  I compiled and am back to the poor reception/clarity issues have reported..
 It was creating incorrect table entries.
It will still fail though with too string a signal, the radio's hardware just can't cope with them.

oh good :)
I found a bug in the code I wrote to create the register look-up table. It was creating incorrect table entries.
It will still fail though with too string a signal, the radio's hardware just can't cope with them.

Buddy you have still done wonders...Given the quality and cost of the radio  I don't expect miracles and if the current quality etc I am experiencing is the best  we can get dam n so be it. It is still 20x better than stock FW's... If I want better AM I can buy better or use my SDR's.


[no-extraneous-dependencies]: peerDependencies option behavior

It looks like peerDependency works in the following way:
Given the following package structure:
Package A
    Package B
        Package B1
        Package B2
    Package C
    ...

import will pass if package A has peerDependency.
But also, it will pass if any subpackage (e.g. package B, package C) has peerDependency.
My question:
Is it expected behavior or this rule should check the presence of peerDependency in package A?
If it is expected behavior, is it possible to add an option so that rule requires peerDependency to package A (i.e. peer dependencies in subpackage won't do)?
The reason for these questions is that I prefer all imports to be listed in root package JSON rather than relying on some subsubpackage of subpackage having peer dependency that may be removed at any moment.

I'm not really sure what you're asking.
If you're describing a graph/tree, every single package should be explicitly listing its peerDependencies (which includes all the peer deps of its transitive dependencies). Removing a peer dep is always a breaking change.
IF you're describing a monorepo, there's different schools of thought about whether deps should be listed by each subproject or only in the root. Can you elaborate?


[RESOLVED] Unavailable by ICMP ping

Problem started at 05:57:33 on 2023.06.02
Problem name: Unavailable by ICMP ping
Host: S100-Santiago
Severity: High
Operational data: Down (0)
Original problem ID: 23067
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23516&eventid=23067

Problem has been resolved in 7m 0s at 06:04:33 on 2023.06.02
Problem name: Unavailable by ICMP ping
Host: S100-Santiago
Severity: High
Original problem ID: 23067


refactor: do not expose base components

Description

Do not expose the LWCC base components as they won't be available for Lightning Pages. Only the chart builder and sample components will be exposed
Motivation and Context
resolves #98

How Has This Been Tested?
Scratch org

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

LGTM
Just an issue with the CI It could be fixed here or in the chore one, or in a dedicated PR

@scolladon Yes, I was thinking about a dedicated PR (I already opened the issue some time ago for that warning). I want to test it to tmake sure that we don't break the deploy to scratch orgs 😅  #97
The CI error is due to the scratch org daily limit... we'll just have to wait until tomorrow 🤦♂  (I will check if we can have a new devhub with a highest limit)

@scolladon can you re-approve (no rush) when you have the time please ? I had to rebase the branch with master due to some conflicts with the last merge. Thanks ! 🙏


Black Patches On Text Fields

I'm currently using the flutter_neumorphic package.
And all the text-fields there have black patches on them. (Left side in the below screenshot).

It's device-specific issues (such as in Samsung and Vivo devices).
Please help.

Hey @,
This issue tracker is used for tracking bugs and feature requests for the flutter framework, engine and the flutter tool.
Since this is a bug with a 3rd party package, please close this issue and open it here instead.
Thanks

Hey sure. Thank you @sidrao2006. I will post it there.


Remote monitoring services failed running due to missing environment variables.

Type of issue

[x] Bug
[ ] New feature
[ ] Enhancement

Description
Deploy all Microservices by following below instruction.
https://docs.microsoft.com/en-us/azure/iot-accelerators/iot-accelerators-remote-monitoring-deploy-local
Two services failed to start because of missing environment variable.
If I set environment variable manually, services were running without an error.
Steps to reproduce

Follow instruction: https://docs.microsoft.com/en-us/azure/iot-accelerators/iot-accelerators-remote-monitoring-deploy-local
Run all microservices from visual studio 2017

Expected behavior
all services running
Current behavior <!-- The actual behavior observed --
two services failed running because of missing environment variables.
Known workarounds
Set all environment variables manually.
Possible solution
...
Context and Environment

Operating System: ...
GitHub branch: ...
Node.js Runtime: ...

I’m seeing the same problem when trying to deploy locally, either through VS 2017 or Docker following the Microsoft docs. It looks like it fails on the database connection. Also can’t start the
Stream Analytics Job through the Azure Portal as that fails in the database connection. What is the workaround? How do you set the environment variables manually?


Bug: White border on popup

Think this may have been introduced within the last week or so.

Any ideas about this one @Vadim121197?

i`ll fix it! i don't have any ideas

Starting to realize that all chrome extensions have this border. It's only visible when you have a dark screen behind the extension and it's noticeable. Don't think we can do anything about this.


Package request: nodePackages.pgraphs

Project description
This package implements parsers and serializers to convert between labeled property graph formats and databases. For example, I'm trying to transliterate a JSONCanvas file from Obsidian to other formats.
Thank you!
Metadata

homepage URL: https://www.npmjs.com/package/pgraphs#json-canvas
source URL: https://github.com/pg-format/pgraphs
license: MIT
platforms: NodeJS

Add a :+1: reaction to issues you find important.

Note for packagers: buildNpmPackage with pkgs/by-name should be preferred over nodePackages.


LayerNorm == torch.nn.InstanceNorm1d ?

I believe what you call LayerNorm is actually InstanceNorm1d in pytorch.
https://github.com/mravanelli/SincNet/blob/488c9822e94b1bbfdbf25ba2ca5986632f952909/dnn_models.py#L112-L123
It is my understanding that Layer Normalization would actually have one weight/bias per sample in the sequence, while Instance Normalization only has one per channel.  Do you confirm?
References

Layer Normalization : https://arxiv.org/abs/1607.06450
Instance Normalization : https://arxiv.org/abs/1607.08022

OK. Thanks.


Paper cut: Better handling of "CoverageException: Can't add arcs to existing line data" ?

Is your feature request related to a problem? Please describe.
Previous closed issue, with comments: #476
Reproduction: In the process of adding coverage to an existing project's test suite, I first ran it without branch coverage, and then again after enabling branch coverage in .coveragerc, resulting in "CoverageException: Can't add arcs to existing line data".
I'm familiar enough with coverage to have guessed that it's a data file format problem, and deleted the .coverage file to fix it, but this won't be obvious to new or inexperienced users, and it probably represents a significant usability hurdle / paper cut bug (especially since it's most likely to occur when first adding coverage to a project in this way)
Describe the solution you'd like
One or more of:

A more descriptive and actionable error message: at least, something that would lead new / inexperienced users to clearing the coverage database, for example.
More generally, a mechanism to recognise when the coverage database format is not compatible with a coverage run's invocation options, so that this kind of case can be handled better in general?

Additional context
This is the relevant traceback (with coverage 4.5.3, invoked via nosetests --with-coverage):
Traceback (most recent call last):
  […]
  File "…/site-packages/coverage/control.py", line 807, in combine
    self.get_data()
  File "…/site-packages/coverage/control.py", line 833, in get_data
    if self.collector.save_data(self.data):
  File "…/site-packages/coverage/collector.py", line 404, in save_data
    covdata.add_arcs(abs_file_dict(self.data))
  File "…/site-packages/coverage/data.py", line 365, in add_arcs
    raise CoverageException("Can't add arcs to existing line data")
coverage.misc.CoverageException: Can't add arcs to existing line data

I think you are right, this is definitely a place where the messaging could be made more relevant to the user's perspective rather than the code's perspective, so that the user understands what's happening.

This is now released as part of coverage 5.5.


Error: unable to build kubernetes objects from release manifest: resource mapping not found for name: "btp-invoicing-cron-job" namespace: "" from "": no matches for kind "CronJob" in version "batch/v1beta1"

Hi Team, I am now at the steps to deploy the cron-job, but it fails as below. please advise. thanks
ferrymul@909c4acf1983 cron-job % npm run deploy:kyma --namespace=default

<EMAIL_ADDRESS>deploy:kyma
npx cross-var helm upgrade --install btp-invoicing-cron-job ./chart --namespace $npm_config_namespace

WARNING: Kubernetes configuration file is group-readable. This is insecure. Location: /Users/ferrymul/.kube/kubeconfig--garden-kyma--c035588-external.yaml
WARNING: Kubernetes configuration file is world-readable. This is insecure. Location: /Users/ferrymul/.kube/kubeconfig--garden-kyma--c035588-external.yaml
Release "btp-invoicing-cron-job" does not exist. Installing it now.
Error: unable to build kubernetes objects from release manifest: resource mapping not found for name: "btp-invoicing-cron-job" namespace: "" from "": no matches for kind "CronJob" in version "batch/v1beta1"
ensure CRDs are installed first

This issue is now fixed by changing batch/v1beta1 to batch/v1 in cron-job\deploy-job.yaml and cron-job\chart\templates\deployment.yaml


Disabling autotune_serialize_test

The test failed for rocm in a weekly sync. Investigation under way but disabled it for rocm for now to keep community CI clean.
@cheshire @chsigg  @deven-amd @stevenireeves

@wenchenvincent  Can you please sign CLA. Thanks!

@wenchenvincent Can you please sign CLA. Thanks!

I have signed CLA.

@googlebot I consent.

@awpr FYI

@wenchenvincent for this and others, could you also attach the failing log?

@wenchenvincent for this and others, could you also attach the failing log?

Attached is the failing log.
autotune_serialize_test_gpu_test.log


Update documentation

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


zeit: add time comparison methods

Boolean time comparison methods (after, before, equal) similar to those in go's time package. Additional compare method that returns an enum with after, before and equal values

Thanks for the PR! Left a couple comments.

Made the changes you suggested. Coming from rust, I still forget enum values can be inferred in zig. :)
Thank you for this library! It's usually one of the first ones I need whenever I pick a new language. Feel free to ask any further tweaks to the PR.


removed shared package

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: geeknoid
If they are not already assigned, you can assign the PR to them by writing /assign @geeknoid in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

mixer/OWNERS
pkg/OWNERS
security/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@hzxuzhonghu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
cb3c81f394414942abc8057d6d079a1b53595ea2
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
05176ec5d23e935bb8680b0eb89afc87d209681a
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@hzxuzhonghu: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-unit-tests.sh
c0b65c776739a373f57bf2f2695af033258676d9
link
/test istio-unit-tests

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

I don't believe we want these changes. Please see #4821 for some context.


feat(redux): dispatcher with middleware

一般的によくみるDispatcherをベースとしたmiddlewareの実装を追加
#58

[Current coverage][cc-pull] is 96.22%

Merging [#97][cc-pull] into [master][cc-base-branch] will increase coverage by <.01%

@@             master        #97   diff @@
==========================================
  Files             6          6
  Lines          1032       1033     +1
  Methods           0          0
  Messages         39         39
  Branches          0          0
==========================================
+ Hits            993        994     +1
  Misses           39         39
  Partials          0          0

Powered by Codecov. Last updated by [b5f4779...17b9949][cc-compare]
[cc-base-branch]: https://codecov.io/gh/azu/JavaScript-Plugin-Architecture/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/azu/JavaScript-Plugin-Architecture/compare/b5f4779bd428a694730d1b09d7e0cce1721628c4...17b99498f0350a513fd56ce85b2ad9f760ab44ad
[cc-pull]: https://codecov.io/gh/azu/JavaScript-Plugin-Architecture/pull/97?src=pr


CosmosDB connector

CosmosDB is Microsofts new cloud database
It would be great to have a connector for this database

+1

+1 We are making a foray into Cosmos DB after starting out with graphcool.  Lack of other database support is probably our biggest hurdle for Prisma (i.e. we want MS SQL, Cosmos DB or Postgres).

Thank you all!
We have finished the ground work required to support more database connectors. The implementation of Postgress is set to start next week and more will follow soon after. I can't offer a concrete timeline for Cosmos DB yet though.

@sorenbs great news! Any update on a Cosmos DB roadmap? I'd potentially be interested in contributing.

+1

Just a heads up? Any updates on that?


Add ORC: Orbit Chain

[v] I understand that token listing is not required to use the Polygon Wallet with a token.

Please provide the following information for your token.
Token Name: Orbit Chain
Token Symbol: ORC
Decimals: 18
Polygon Address: 0x1bd5048e0b85c410dd039aa9c05069a9d82488b8
Ethereum Address: 0x662b67d00a13faf93254714dd601f5ed49ef2f51
Logo URI (svg): https://s.ozys.io/icon/orbitchain.svg
Project Name: Orbit Chain
Project Summary: Orbit Chain is a cross-chain project that challenges the limitations of scalability due to the lack of connectivity and limited resources of existing public chains. Orbit Chain has worked to surpass the ever-present scalability and connectivity constraints that have limited traditional public chains. Its improvements and innovations grow user accessibility and convenience so blockchain-based protocols and services can have more real-life integration.
Project Contact<EMAIL_ADDRESS>Project Website: https://orbitchain.io
Mainnet/Testnet: Mainnet
Additonal Notes: Orbit Chain/Orbit Bridge/Orbit Farm

Added to allTokens v2.2.0


When will the code be released?

您好，请问代码什么时候可以开源呢？做毕设想参考一下，非常感谢！救救孩子吧！

Soon after the AAAI deadline. =.=

请问为什么还没有开源鸭？AAAI deadline应该以后过了吧，求代码！！！

Thank you for your attention to our work. The code and pre-trained model will be released within a week.

请问为什么还没有开源鸭？AAAI deadline应该以后过了吧，求代码！！！

Thank you for your attention to our work. The code and pre-trained model will be released within a week.

okkk，thanks very much ！感激涕零！

When can the code be released?

The code and pretrained model have been released just now.

The code and pretrained model have been released just now.

Thanks very much


HTTP 400 error if editing pets with invalid date instead of 'invalid date' message

If you try to edit pet's birth name with some invalid value (e.g. 2012/09/44), the HTTP Status 400 error page is shown instead of displaying nice 'invalid date' message in edit pet form.
This error is caused by https://github.com/spring-projects/spring-petclinic/commit/3bcf84543ec586173731942a83178eed561f7d3a

I've confirmes the bug is cause by 3bcf845

The BindingResult parameter should be follow the parameter annoyed with@Valid


Highlight shortest path when searching

When you search for an item, the shortest way to get to that item should be highlighted.
I've not played with one line display, but I would think it also useful if the lines are sorted by length so when you search line by line the shortest line is displayed first.

Yup, I'm already working on adding that. Just wanted to get it working first.