Exceeding CPU limit when pushing eosio.system contract

Hey,
when I run custom testnet nodeos with custom genesis file, I randomly get below error when pushing eosio.system contract.
$ cleos set contract eosio /tmp/eosio.contracts/build/contracts/eosio.system/
Reading WASM from /tmp/eosio.contracts/build/contracts/eosio.system/eosio.system.wasm...
Publishing contract...
error 2019-12-07T13:03:09.462 nodeos    http_plugin.cpp:652           handle_exception     ] FC Exception encountered while processing chain.push_transaction
Error 3080004: Transaction exceeded the current CPU usage limit imposed on the transaction

I use eos 1.8.5 from eostudio/eos:v1.8.5 docker image and eosio.contracts from release/1.8.x branch plus following genesis and config files:
{
  "initial_timestamp": "2018-03-02T12:00:00.000",
  "initial_key": "EOS55oVd4ZyC2QMiAMzs1WFYzEYU1GKAAALPCa45Dzs9wrUWo3hjD",
  "initial_configuration": {
    "max_block_net_usage": 1048576,
    "target_block_net_usage_pct": 1000,
    "max_transaction_net_usage": 524288,
    "base_per_transaction_net_usage": 12,
    "net_usage_leeway": 500,
    "context_free_discount_net_usage_num": 20,
    "context_free_discount_net_usage_den": 100,
    "max_block_cpu_usage": 100000,
    "target_block_cpu_usage_pct": 500,
    "max_transaction_cpu_usage": 50000,
    "min_transaction_cpu_usage": 100,
    "max_transaction_lifetime": 3600,
    "deferred_trx_expiration_window": 600,
    "max_transaction_delay": 3888000,
    "max_inline_action_size": 4096,
    "max_inline_action_depth": 4,
    "max_authority_depth": 6
  }
}

chain-state-db-size-mb = 65536
reversible-blocks-db-size-mb = 65536

producer-name = eosio
http-server-address = <IP_ADDRESS>:8888

plugin = eosio::chain_api_plugin
plugin = eosio::history_plugin
plugin = eosio::history_api_plugin
plugin = eosio::http_plugin
plugin = eosio::producer_plugin
plugin = eosio::producer_api_plugin

access-control-allow-origin = *
http-validate-host = false
enable-stale-production = true
max-transaction-time = 3000000

filter-on = *

To easily reproduce it I prepared a repo with Dockerfile: https://github.com/ulamlabs/eos-regtest.
Just build the image and run it couple of times.
What I tried?
Increasing max CPU time in genesis file - then the pushing the system contract takes seconds and errors with Please increase the expiration time of your transaction!.
Thanks for helping.

The max-transaction-time of 3000000 ms you have specified exceeds the maximum block time of 500 ms.  No transaction taking that long can be incorporated into a block.  You could try increasing max_transaction_cpu_usage in genesis.json from 50000 microseconds to something less than 500000 microseconds.

@jgiszczak I already tried that. When I increase all max cpus in the genesis file to some absurd values (like minutes), the transaction takes forever to execute and the node gives up with timeout error.
So there is something bad going on when executing that transaction (put system contract), looks like a deadlock to me.

As I said, increasing those limits to beyond the block time is useless.  Any transaction taking longer than block time will fail with the timeout you are seeing, always.  The transaction is expiring in the queue after repeated failures to be incorporated into a block.
Try building the 1.8.3 release of the system contract rather than the 1.8.x branch.  What version of CDT did you use to build the system contract?

Testing demonstrates that changing max_transaction_cpu_usage in genesis.json still works as advertised.  Note that EOS Mainnet uses a value of 150000 microseconds.  It's safe to say 50000 is too low for current common contracts.

I can confirm that changing those values works, but the issue that we're facing is that no matter if we set these values to something unreasonable like 20 seconds per block or we use mainnet values (0.2s for max block CPU usage and 0.15s for max transaction CPU usage), it doesn't guarantee us that this transaction won't exceed the deadline. We counteract this by repeatedly submitting it until it succeeds and ultimately it does, usually requiring only about ~0.01-0.03s of CPU time. There must be some reason why this transaction either exceeds 0.15s deadline or gets executed under just a fraction of that time.
We use eosio.cdt 1.6.3 as advised in release notes. Using v1.8.3 of system contract doesn't seem to resolve the issue.

Reopening.  I'm getting three independent reports of consistent timing failures in the 1.8 branch.

We're having these issues when running this on CI and to be honest I wouldn't call it underpowered. We currently run builds on general1.large codebuild instance, which has 15GB of RAM and 8 vCPUs. The only higher tier has 144GB of RAM and 72 CPUs and I'm not sure if it's worth switching to that one just to check if this resolves our issues as it's 12x the price of our current one. My laptop, on which this also fails half the time with deadline exceeded exception has an i7-4770HQ CPU and 16 GB of RAM.
I tried changing the niceness, but it still consistently takes at least 2 attempts to submit the contract. My machine also doesn't seem to be under much load while running it.

I prepared a Docker image and a simple script to reproduce this issue.
https://github.com/ksiazkowicz/eos-testnet
The idea behind the script is that we're trying to bootstrap EOS testnet until it succeeds. Sometimes 1st attempt to deploy eosio.system contract will fail, so I wait 10 seconds and try again. After exceeding 10 retries, I'm considering test run as failed, kill the container and try again. By default, the script will run 100 tests.
I ran these tests against an r5.large EC2 instance running Ubuntu 18.04 and on my Mid-2015 MacBook Pro (Core i7, 16 GB RAM).
My results are here if anyone wants to dig in:
https://1drv.ms/x/s!ApF6BBqdJeSZkaQ4u3tTOs4cEswMEQ?e=u4bTdc

This maybe the time-out issue on keosd. Can you try to following (sign the transaction manually without invoking keosd)?
./cleos set code eosio eosio.system.wasm -j -d -s -x 3600 > tmp
./cleos sign tmp -k THE_EOSIO_PRIVATE_KEY -p

Interesting. So if I understand correctly, you suggest that the transaction itself might be already expired by the time it's signed and ready to be submitted? That would make sense, looking at it again the logs mention that the deadline, not CPU usage is exceeded. I adjusted the bootstrapping script of my Docker image accordingly and ran it again. I added test results here: https://1drv.ms/x/s!ApF6BBqdJeSZkaQ4u3tTOs4cEswMEQ?e=PntAbv
What's interesting about the results, that 98 out of 100 builds were successful at first try. The 2 ones that failed had the error mentioned in the 1st message in this ticket:
info  2020-04-16T07:50:23.712 cleos     main.cpp:3306                 operator()           ] grabbing chain_id from nodeos
info  2020-04-16T07:50:23.901 nodeos    producer_plugin.cpp:2046      produce_block        ] Produced block 000000c2db5907e2... #194 @ 2020-04-16T07:50:24.000 signed by eosio [trxs: 0, lib: 193, confirmed: 0]
error 2020-04-16T07:50:24.154 nodeos    http_plugin.cpp:696           handle_exception     ] FC Exception encountered while processing chain.push_transaction
Error 3080004: Transaction exceeded the current CPU usage limit imposed on the transaction
Error Details:
transaction was executing for too long
pending console output:
+ echo retry
+ sleep 10
retry

I attached the log files here: https://1drv.ms/u/s!ApF6BBqdJeSZka8r05JuZtH-4R2YiQ?e=ETt3ac

Can you add verbose-http-errors=true which should provide you more info on the timeout.

It appears to be enabled:
root@2ff33b4cd2bb:/# ps aux | grep nodeos
root        11  1.5  0.8 134729372 67704 ?     Sl   10:34   3:16 nodeos -d /data --config-dir /app --genesis-json=/app/genesis.json
root      2650  0.0  0.0  11464  1000 pts/0    S+   14:06   0:00 grep --color=auto nodeos
root@2ff33b4cd2bb:/# cat /app/config.ini | grep verbose-http-errors
verbose-http-errors = true

When I submit it manually, the response does include the traceback but it's not really helpful.
{
    "code": 500,
    "message": "Internal Service Error",
    "error": {
        "code": 3080004,
        "name": "tx_cpu_usage_exceeded",
        "what": "Transaction exceeded the current CPU usage limit imposed on the transaction",
        "details": [
            {
                "message": "transaction was executing for too long",
                "file": "transaction_context.cpp",
                "line_number": 493,
                "method": "checktime"
            },
            {
                "message": "pending console output: ",
                "file": "apply_context.cpp",
                "line_number": 113,
                "method": "exec_one"
            }
        ]
    }
}

The weird part is that all runs have the same config and it doesn't matter how many times you try to submit it, it fails with this exception. If I kill the container, remove all its data and spin it up again, it will probably be fine. In fact, I spinned up another container based on the same image and it bootstrapped just fine.
Not sure how useful this is, but here is also cleos get info output for both nodes:
broken node
oot@2ff33b4cd2bb:/# cleos get info
{
  "server_version": "eb4456fd",
  "chain_id": "7479dd536fa543a6e5faafe8f90132f8d1aab58c746d7d7a4e01c10ea091e25a",
  "head_block_num": 26827,
  "last_irreversible_block_num": 26826,
  "last_irreversible_block_id": "000068ca42e0a8dbdd5d5f108a0cda5526a252aea1c1aa4e39515611ad9631f0",
  "head_block_id": "000068cbf0fa8c02aadaa1320a53508d9c4a9f620c8900aa40e9a2693c454120",
  "head_block_time": "2020-04-16T14:19:05.000",
  "head_block_producer": "eosio",
  "virtual_block_cpu_limit": 200000000,
  "virtual_block_net_limit":<PHONE_NUMBER>,
  "block_cpu_limit": 200000,
  "block_net_limit": 1048576,
  "server_version_string": "v1.8.13",
  "fork_db_head_block_num": 26827,
  "fork_db_head_block_id": "000068cbf0fa8c02aadaa1320a53508d9c4a9f620c8900aa40e9a2693c454120"
}

working node
root@30e879854ba4:/# cleos get info
{
  "server_version": "eb4456fd",
  "chain_id": "7479dd536fa543a6e5faafe8f90132f8d1aab58c746d7d7a4e01c10ea091e25a",
  "head_block_num": 55,
  "last_irreversible_block_num": 54,
  "last_irreversible_block_id": "000000368762efdad2bac8d4869a5117504bfd923af19057df2159b3b1c5942d",
  "head_block_id": "000000373495308ac2ed3f740c7d27a0b2351f700d7d415c2d1a068d5e86fe16",
  "head_block_time": "2020-04-16T14:18:52.500",
  "head_block_producer": "eosio",
  "virtual_block_cpu_limit": 211077,
  "virtual_block_net_limit": 1106757,
  "block_cpu_limit": 199900,
  "block_net_limit": 1048576,
  "server_version_string": "v1.8.13",
  "fork_db_head_block_num": 55,
  "fork_db_head_block_id": "000000373495308ac2ed3f740c7d27a0b2351f700d7d415c2d1a068d5e86fe16"
}


Improvement done in the contact page in Css.

Fixes:  #1749
Description
Improvement in the contact page in CSS by adding max-width and border-radius.
#1749
Type of PR

[x] Bug fix

Screenshots / videos (if applicable)
before:

After:

Checklist:

[x] I have made this change from my own.
[x ] My code follows the style guidelines of this project.
[ x] I have performed a self-review of my own code.
[x ] I have commented my code, particularly in hard-to-understand areas.
[ x] I have made corresponding changes to the documentation.
[x ] My changes generate no new warnings.
[ x] I have tested the changes thoroughly before submitting this pull request.
[x ] I have provided relevant issue numbers and screenshots after making the changes.

Conflicting files
assets/css/style.css
Please see the conflicts highlighted in the image above. Resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


WebApp create other pages?

index.pug
user.pug

download.pug or training.pug how do I add from which file?

Duplicate of cso2-webapp#6


gutter color scheme is not intuitive

VSCode Version: 1.18.0
OS Version: macOS 10.12.6

These line indicators

are great, but the color scheme is pretty weird. As far as I can tell,

A removed line is marked with red. Makes sense.
An added line is marked with green. Ok, I'm getting the picture now. These are the colors that anyone who has ever used git or any other version control system expects. Oh, and they match the color scheme that the file tree on the left-hand side of the editor. Got it.
A modified line is marked with.... blue. Wuuuuuut?

Why not do something like the gutter in Atom instead?

You can customize those colors with
"workbench.colorCustomizations": {
        "editorGutter.addedBackground": "#ff0000"
},

@roblourens Ah, that's great to know. Could we get better defaults though?

There are many themes that we ship. There are also many themes in the Marketplace. Use the one which you like best.

@joaomoreno Sure, having multiple themes is great and all. I can certainly customize the editor to my liking all day long, but the issue here precisely is that the default theme that ships is confusing and should be adjusted. It's simply not consistent with any other VCS color scheme. It's not even self-consistent within the editor: the file tree uses a totally different color scheme than the gutter.

cc @jrieken about the file tree


Add Embed Support

Not in a useable state yet. View this as very early stage, updates will follow.

Tests should now perform correctly.

Yeah, I'll work out what's wrong with them and then get this PR in. Thanks a ton for your contribution! If you don't mind documenting how it works, that would be fantastic!

Update: Travis won't let PRs from forks use encrypted variables, which is how I store the bot credentials. I'll see if it will let me run it and be ok, but if you know how to make this work let me know.

If you don't mind documenting how it works, that would be fantastic!

Is there a specific way you want it to be documented? Full Text, Docstring etc?

Added Support for Image, Thumbnail, Video and Author attributes. Tests should also work accordingly.

You can also look at my travis build, which builds correctly.
https://travis-ci.com/tooxo/distest/builds/128603178

If you don't mind documenting how it works, that would be fantastic!

Is there a specific way you want it to be documented? Full Text, Docstring etc?

If you could document the methods in the docstring, that would be great, I'll plug it into sphinx once you're done. Just look at one of the nearby functions for an example, doesn't need to be anything complicated. Full documentation here in case you want to take a look.

You can also look at my travis build, which builds correctly.
https://travis-ci.com/tooxo/distest/builds/128603178

Sound good, once the documentation is done, I'll approve the PR.

Hey! This is an awesome and much needed feature, is there anything I can do to help get it over the line?

@tooxo @JakeCover Bump :)

@rade0 Thank you for your patience, appreciate it. Didn't touch this repo for a long time, but I remember stopping working on it, because I wasn't entirely sure how to structure the feature.
For now its, I think, still working, and if you want to compare an embed you can compare all of it or just some attributes.
I don't have any intentions in working on it anymore, I instead implemented a feature in my bot, that, for tests, the bot doesn't use embeds, but thats obviously not ideal.
If you want to take over from here, I can add you as a contributer on my fork and help you getting started.

@tooxo @JakeCover Bump :)

I should be working on this more soon, I just got really busy but now thanks to covid19 I have more time! If you want to help in some way, feel free to help out and take tooxo up on their offer on contributions, I'll take a look at this probably today or tomorrow.

Awesome thank you both! @JakeCover I'll wait for you to give it the once over and if anything needs doing I'm your man 😀

Just tested it, looks good! Now I need to figure out how to get the bot tokens into travis on forks, sounds like a problem for future me!

Nice one! Will give it a whirl.
(Don’t worry I also rely on my own future me quite a lot 😂)

Just to confirm it works a charm, thanks dude!


Man page not rendering properly

The man page doesn't render properly here, I'm using man-db.  Maybe it works on some other man implementations but it seems to be conspicuously missing a .TH line at the top.
If I add ".TH xkcdpass 1" as line 1, then it mostly renders ok.  There are still some various quirks, including "Author |authorname| |authoremail|", and what looks like some vim metadata at the end:
^L^H^L
Local  variables: mode: rst coding: utf-8 time-stamp-format: "%:y-%02m-%02d" time-stamp-start: "^:Date:[
]+" time-stamp-end: "$" time-stamp-line-limit: 20 End: vim: filetype=rst fileencoding=utf-8 :

I've added a patch to gentoo for now to clean it up a bit:
https://gitweb.gentoo.org/repo/gentoo.git/plain/app-admin/xkcdpass/files/xkcdpass-manpage-fix.patch

Thank you for the patch. I have merged it in the most recent releases - could you confirm that it is working as expected? There is certainly more to be done to bring the manpage into sync with the current README and feature set, but I'd like to check that the code works as is before continuing with changes

I just bumped gentoo to latest release 1.19.2 and the man page is looking good without any additional patches.  Thanks!


test: compound expression for v-bind

close #35
This is a unit test PR related to the complex expression parsing of v-bind in Vue Vapor.
In addition to complex expressions, I also added some other tests related to v-bind.
I referred to the existing tests related to v-bind in /packages/compiler-core when adding these tests.

Thanks for your contribution! The tests are passed now.


Fix googleapis_reference_link in documentation for generated protos

Generated protos are not part of the googleapis repo. We need to figure out a solution for these locally defined proto files.

One option is to directly link the types in the reference documentation for the API.  We would need a new configuration parameter in the generator config that points to the API docs, for example:
https://cloud.google.com/compute/docs/reference/rest/v1
I think we can figure out what is the path to any resource or RPC within that directory.


Introduce ability to specify a CloudFormation role (resolves #1649)

When users provide the stack_role_arn, CloudFormation will assume that
role when provisioning, modify, or deleting the stack specified by Zappa.
From the Boto3 CloudFormation docs:
The Amazon Resource Name (ARN) of an AWS Identity and Access Management (IAM)
role that AWS CloudFormation assumes to roll back the stack. AWS CloudFormation
uses the role's credentials to make calls on your behalf. AWS CloudFormation always
uses this role for all future operations on the stack. As long as users have permission
to operate on the stack, AWS CloudFormation uses this role even if the users don't
have permission to pass it. Ensure that the role grants least privilege.

If you don't specify a value, AWS CloudFormation uses the role that was previously
associated with the stack. If no role is available, AWS CloudFormation uses a
temporary session that is generated from your user credentials.

Description

GitHub Issues

Coverage decreased (-0.04%) to 72.684% when pulling 8ecaeacda7711cbcc166109f0ba6267f6b2f87a4 on relwell:stack-role-arn into 32d86987b9dfc24fab99fa8fb7087bfffd449556 on Miserlou:master.

Coverage decreased (-0.04%) to 72.684% when pulling 8ecaeacda7711cbcc166109f0ba6267f6b2f87a4 on relwell:stack-role-arn into 32d86987b9dfc24fab99fa8fb7087bfffd449556 on Miserlou:master.

I was looking to add some tests to this PR, but I'm having a little difficulty figuring out where I would be able to add them, given the current test structure. I'd definitely appreciate some guidance!

Can someone help me get this change merged? Thanks

@jneves let me know if these updates work for you -- thanks!

Looks good to me. Just needs some user testing. Hoping to have some time later, but anyone else can take it for a run and report it back here.


Add str to all types

Off the top of my head we are missing one for ModuleInfo (edit: already exists)

Seems to be mostly resolved, reopen if this is not the case!


Firefox crashes

I am trying to record 2 : one audio stream (own stream) and one video stream (remote user stream)
When I am trying to stop record while both of users are connected - everything ok, But when connection between users is lost, I am trying to stop record and get blobs from remote stream firefox sometime crashes or sometime do not call my callback with dataurl .
On Chrome everything is fine, the problem is only for firefox.

Maybe you need to use "stream-ended-listener" to fire recorder.stopRecording as soon as stream stops.

https://www.webrtc-experiment.com/webrtcpedia/#stream-ended-listener

addStreamStopListener(remoteStream, function() {
    recorder.stopRecording();
});

Make sure to fire remoteStream.stop as soon as peer.iceConnectionState changes to disconnected:

http://www.muazkhan.com/2014/05/webrtc-tips-tricks.html

var peer = new RTCPeerConnection(iceSerersArray, optionalArgsArray);
peer.oniceconnectionstatechange = function() {
    if (peer.iceConnectionState == 'disconnected') {
        peer.getRemoteStreams().forEach(function(stream) {
            stream.stop();
        });

        // this one is preferred
        yourOwnRemoteStreamsList.forEach(function(stream) {
            stream.stop();
        });
    }
};

Firefox crashes in following cases:

If you are asking to record audio but stream has not audio track
If you are asking to record audio/video but no audio/video track or none of the tracks is active (at least one track must be active)


New icon design?

Recently, I have heard some advices on a new icon design. Unfortunately, I'm not good at drawing icons.

If you have any good idea, feel free to put it in the comment 💯

Can't we use font awesome or other free to use icon library?

@Alaev
Yes, actually we are using evil-icon in our next release. The issue is talking about the app icon:)

Oh... I saw now the icon in the previous message.
what kind of theme overall style are you thing about? I can come up with some sketches

Just kindly reminder, the spike of comma can't be seen in the small icon, looks like only a black point.
Refer to my desktop snapshot:

suggest remove shadow

@hackjutsu    Is there any plan to add a theme? like Sublime Text 2.

@maskleo I wish, but I'm not good at theme design.

With the help of Brandmark, the AI-based logo maker, I finally come out of something.

Not sure if you are aware but this icon is really similar to atom editor.

Most of early Electron-based apps are named after physics particles to show their origins like Atom, Photon. Lepton follows the naming convention intentionally at its very first beginning. So it’s not surprising to see these apps have similar icons.


Adding duplicate entries check in publish

Ensures that duplicate label entries cannot be submitted to Directory::publish successfully

Codecov Report
Patch coverage: 91.66% and project coverage change: +0.02% :tada:

Comparison is base (be1055e) 87.73% compared to head (4de9a4e) 87.75%.

:exclamation: Current head 4de9a4e differs from pull request most recent head 76bf50b. Consider uploading reports for the commit 76bf50b to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the GitHub App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #400      +/-   ##
==========================================
+ Coverage   87.73%   87.75%   +0.02%
==========================================
  Files          39       39
  Lines        8771     8803      +32
==========================================
+ Hits         7695     7725      +30
- Misses       1076     1078       +2

Files Changed
Coverage Δ

akd/src/errors.rs
3.64% <0.00%> (-0.06%)
:arrow_down:

akd/src/tests.rs
95.46% <95.00%> (-0.01%)
:arrow_down:

akd/src/directory.rs
83.51% <100.00%> (+0.23%)
:arrow_up:

... and 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Lgtm


new to parseq

Tried to create animation as mention in your video: https://www.youtube.com/watch?v=MXRjTOE2v64. Love to understand what i am doing wrong:
https://github.com/rewbs/sd-parseq/assets/20493493/0fe5c361-444c-400e-8620-02de2dddbe0f

https://github.com/rewbs/sd-parseq/assets/20493493/a01d71f5-41a6-4706-ae8e-40b2f75f44ae
using sdxl-base  model for creating image but not getting any consistency

I'm closing this because it looks like you got the help you needed over on discord. Feel free to re-open if you need more input.


[Benchmarking] Getting info before the extrinsic fails with an error

Hey valuable Substrate engineers!
I just was running the following command for benchmarking my pallets. The problem I've got is that I only see an error, but would love to know the exact extrinsic which caused it.
./target/release/zeitgeist benchmark pallet --chain=dev --steps=2 --repeat=2 --pallet=zrml_prediction_markets --extrinsic='*' --execution=Native --wasm-execution=compiled --detailed-log-output --heap-pages=4096 --template="./misc/weight_template.hbs" --output=./zrml/prediction-markets/src/weights.rs

Output, if failure:
...
Error: Input("InvalidMarketPeriod")

But there is no info about the pallet (we know it's prediction-markets here, but it could be --pallet=*) and the extrinsic benchmark which caused it. That would be useful for a quick fix. So that one can see the benchmark name before the error output.

Well, you can try running the tests first cargo test --features runtime-benchmarks in your pallet dir.
Otherwise the log output sometimes tells you which benchmark failed. You can also run them one-by-one after listing them with the --list command.
If you still see a failure only with your real runtime, then it must be a discrepancy between the mocked and the real runtime that is causing it.
Are you talking about this one https://github.com/zeitgeistpm/zeitgeist/tree/main/zrml/prediction-markets?

Well, you can try running the tests first cargo test --features runtime-benchmarks in your pallet dir.

That is fine, thanks. I like that.

Are you talking about this one https://github.com/zeitgeistpm/zeitgeist/tree/main/zrml/prediction-markets? Then please give me a commit hash that I can try.

No, it's okay @ggwpez . It is a specific workflow on a PR here. I just struggled multiple times and thought about telling you this. It just would be useful to print out the extrinsic name before a failure happens.

It literally prints this a few lines before failing Pallet: "zrml_liquidity_mining", Extrinsic: "set_per_block_distribution.
But yea, we could improve the error message a bit.

Oh, this is a misunderstanding. It is not the extrinsic set_per_block_distribution. It was another extrinsic. That's why I am asking for a change.


Add feature to reuse localisation files

Let's say we have iso code routes (i.e.: locale codes are en-us, en-gb, de-de, de-at); the module will then create 4 global localisation files, but we actually have 2 locales.
Adding a file config would be helpful to maintain only 2 localisations json for these 4 locales.
e.g.:
locales: [
  { code: 'en-us', iso: 'en-US', dir: 'ltr', file: 'en.json' },
  { code: 'en-gb', iso: 'en-GB', dir: 'ltr', file: 'en.json' },
  { code: 'de-de', iso: 'de-DE', dir: 'ltr', file: 'de.json' },
  { code: 'de-AT', iso: 'de-at', dir: 'ltr', file: 'de.json' },
]

It seems to me that such functionality introduces unnecessary complexity. From a practical perspective, this approach doesn’t offer any performance gains or improve the logic. Instead, it introduces a lot of redundant conditions, which only leads to more issues and potential bugs.
As the saying goes, "Penny wise, pound foolish."

I could fix this quickly with a module that "paste" localisation files in relevant global translations file.
Closing as not planned then.
I understand your point of view, my request is coming from someone who's trying to migrate in the quickest way possible from nuxt-i18n :) Thanks for your amazing work


To remove the synonyms for four GO terms related to cold-induced thermogenesis.

Hi GO,
We request to remove the synonyms for four GO terms previously assigned to us.
GO:0106106  cold-induced thermogenesis                         CIT
GO:0120161  regulation of cold-induced thermogenesis           regulation of CIT
GO:0120162  positive regulation of cold-induced thermogenesis  positive regulation of CIT
GO:0120163  negative regulation of cold-induced thermogenesis  negative regulation of CIT

Where CIT should not be a synonym for cold-induced thermogenesis since CIT is ambiguous that can refer to many other meanings, such as cold ischemia time (PMID: 29952816). Particularly, PubMed has returned over 3000 papers mentioning CIT, but most of them are not related to cold-induced thermogenesis. Therefore, please help remove the synonyms for above four GO terms. Thank you.
Best regards,
Jin

Or perhaps just change the scope.

already "related synonym"; would broad be better?

Related should be fine.

From original request: "Cold-induced thermogenesis (CIT) should be a children term of the existing term "adaptive thermogenesis".

Synonyms
Alternative words or phrases closely related in meaning to the term name, with indication of the relationship between the name and synonym given by the synonym scope. The scopes for GO synonyms are:
exact
an exact equivalent; interchangeable with the term name
e.g. ornithine cycle is an exact synonym of urea cycle
broad
the synonym is broader than the term name
e.g. cell division is a broad synonym of cytokinesis
narrow
the synonym is narrower or more precise than the term name
e.g. pyrimidine-dimer repair by photolyase is a narrow synonym of photoreactive repair
related
the terms are related in some way not covered above
e.g. cytochrome bc1 complex is a related synonym of ubiquinol-cytochrome-c reductase activity virulence is a related synonym of pathogenesis

We can also use an abbreviation synonym type
This is the uberon syn guidelines which are derived from the GO ones:
https://github.com/obophenotype/uberon/wiki/Using-uberon-for-text-mining
I'd like to unify this across OBO ontologies
On 29 Jun 2018, at 10:08, David Hill wrote:

Or perhaps just change the scope.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/geneontology/go-ontology/issues/15973#issuecomment-401416537


Can we integrate both model backend and AzureADtoken backend for django rest framework?

In my project we are dealing with micro-services sending JWT token between micro services to authenticate API's.
If you have some sample code please share the link.
Some micro-services take more than 1 hrs to execute end to end flow so please suggest how to fix token expiry issue across the microservices.

Some micro-services take more than 1 hrs to execute end to end flow so please suggest how to fix token expiry issue across the microservices.

I think we need more information about what you’re initial goal is here. Sounds to me that you should make one endpoint to kick off the flow, and another to check the status of the flow.

Do you have links to the packages you want to glue together?
Anyway, the expiry of the token is a setting on ADFS (not sure about azure). So Google the docs for ADFS and you'll find it.
On the other hand, calling a microservice that takes an hour sounds like an architectural issue. You'll start to bump into all sorts of timeouts. Not only from the token but also things like firewalls an the like.
Might be better to look into things like Celery and handle it as background tasks. The call to the microservice would then immediately return the task id. The caller can then request the task status every so often to check it's progress.

You want to use django-auth-adfs to integrate DjangoRestFramework with AzureAD?
But at the same time also use Django (without the rest framework) to login using a login page?
 Because the way you describe your problem now makes it difficult to understand what exactly you want to do.
Anyway, it should be possible to have multiple Django authentication backends (https://docs.djangoproject.com/en/2.2/ref/settings/#std:setting-AUTHENTICATION_BACKENDS). As does Django Rest Framework: https://www.django-rest-framework.org/api-guide/authentication/#setting-the-authentication-scheme
So it all depends on what exactly you want and where you send your users to to authenticate.

Closed because of inactivity. Feel free to reopen if you have more questions.


If an SGR escape sequence sets the background color to the terminal background color, it is not opaque

Which operating system does the issue occur on?

Arch Linux

If on Linux, are you using X11 or Wayland?

Wayland

I realized this when a truecolor program I wrote appeared with a noticeable hole in it. Because I use opacity in my terminal, I can see the background through it, instead of it being completely opaque due to the escape code.
Example using 0x303030 background with opacity 0.0:

As you can see, when \e[48;2;48;48;48m  is printed, instead of a solid grey, it is completely transparent.

It’s a known thing and not a bug, since it was done intentionally iirc. The main problem with this behavior is that it’s not documented in config file. This thing exist for achieving transparency in alt-screen apps like alsamixer/vim/mutt etc.
If you dont want this behavior just change background color a bit.

This thing exist for achieving transparency in alt-screen apps like alsamixer/vim/mutt etc.

Ah, I'm used to urxvt, which does not do this.  I understand why this behavior exists; a program explicitly setting the background to the same as its default color probably has the intention of resetting the background.
The program I was using broke this assumption, since it intends to print arbitrary colors. pixterm is another program which will have this issue; if an image is printed which happens to have a pixel match the background color, a noticeable hole will appear.
I would like to disable this behavior completely for this reason, or even better change it so that only the 16-color black causes this. I'll try and patch this myself, so leave this issue closed unless someone else wants this behavior.

I would like to disable this behavior for this reason, or even better change it so that only the 16-color black causes this. I'll try and patch this myself, so leave this issue closed unless someone else wants this behavior.

As I said, just slightly change background your color, you're already using opacity setting, so you shouldn't notice it. Otherwise you have to change how alacritty rendering works.

slightly change your background color ... you shouldn't notice it

If I'm understanding you correctly, you're talking about something like setting black: '0x000020' and background: '0x00001F', right? That way \e[40m will display in #000020, and not trigger the opacity setting.
This won't help if I want to use pixterm or a similar program.  If my background is 0x000020, then I'll see a hole whenever pixterm displays an image with #000020. If I slightly change it to 0x00001F, then I'll see a hole whenever pixterm displays an image with #00001F.  I could view any image with any colors in pixterm, so any background will cause this papercut somewhere.

While setting the color to the background color should give transparency, specifying a truecolor should not cause any transparency. @nixpulvis is already working on a patch to fix this, so hopefully we can get the best of both worlds here again (seems like there was a regression in e964af8a5ea390d96667e80873060d33079134fd).


Hold until the repo has been moved, as per #10.


Automate drought map

Per #109, this PR implements a GitHub Action to automate weekly Drought Map activities.
@jbum, I had to modify your Python script a bit, mainly to output a JSON data file. We then use this data file, latestDroughtMap.json, to update info in the HTML markup and Javascript.
I've set up this job to run every Thursday at 6am (that's 1pm UTC, which explains the 13 in the cron setting). Let me know if we should change this schedule.

Yes, ImageMagick comes standard with ubuntu-latest. But I did need to install PNGCrush. Here's where that's installed during the GitHub Action.
In that same snippet, you can see where mechanicalsoup is installed with pip via the requirements.txt file. This file can be found at src/py/generate-drought-map/requirments.txt. We can add additional python dependencies to that file per-line as needed, docs here.
I also had to install all of Python; there's a whole separate GitHub Action step which takes care of it.


have you ever  considered the feature of  comments??

Have  you even  considered the  feature  of  comment leaving???

For a personal blog site, I think there is no need implement a comment module. There're many third-party commenting tools we can choose, such as Disqus, Duoshuo(in China).


content-type in text response is undefined, should it be 'text/plain' ?

When returning a simple text string from a router, content-type is undefined, is this by design or should it be set to text/plain ?
Simple test case:
test('Elysia should return content-type text/plain', async () => {
	const req = new Request('http://localhost/text')
	const app = new Elysia().get('/text', () => 'Elysia')
	const res = await app.fetch(req)
	console.log(res)
	const resText = await res.text()
	expect(res.status).toBe(200)
	expect(resText).toBe('Elysia')
	expect(res.headers.get('content-type')).toBe('text/plain') // FAILS
});

Also .. i found the documentation for the response a bit lacking. In the first examples text is returned but it is not described. I like in Hono you are more explicit about this by calling  text or json on the Context object.

Looks like its a bug with bun, i opened an issue: https://github.com/oven-sh/bun/issues/8530

Bun automatically add content-type to text/plain on network layer but not programmatically.
We are not going to implement this as it introduce performance overhead.
Closing as not going to implement. Thanks for your understanding.


Fix and deduplicate compute_no_op_goal

Recently we had to implement a compute_no_op_action function on controllers in order to be able to make robots stay still. There also is a compute_no_op_goal function which is used to populate the initial goal after a controller reset. But the latter does not always do what you expect (e.g. see multifinger) and might even be redundant since the goal could simply be computed using the no_op action.

CC @Arpitrf  @ChengshuLi


Develop_v4 to master

Hi dr.max @maximilien,
Just create a PR from develop_v4 which consolidates bosh-softlayer-cpi-release and lastest bosh-softlayer-cpi(master ce0ebf8). This is a massive one... but most commits of mine have been reviewed in develop_v4. Thank you.

@zhanggbj you have conflicts (perhaps just need to rebase). Please resolve.

Hi Dr.Max @maximilien ,
Sorry, when I just tried to fix the conflicts, this PR is merged to master accidentally by mis-operations. Is this PR still need review, if yes, I'll undo this merge. Thanks.


Fixed "active" class bug with toggle within a segmented control body

I had originally made a pull request and completely screwed up the commit. Hopefully this is much clearer. It's a simple fix that more precisely specifies the CSS class in the queryselectors to prevent altering any other "active" CSS classes that may exist as child nodes, mainly the toggle switches.

Hi thewax, would you mind if I incorporate this PR into racthetPro??

Absolutely!!!
On Aug 10, 2016 9:30 PM, "Jim Ma"<EMAIL_ADDRESS>wrote:

Hi thewax, would you mind if I incorporate this PR into racthetPro?
https://github.com/mazong1123/ratchet-pro?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/twbs/ratchet/pull/840#issuecomment-239071922, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABxEQjOaslhfUgVBzKOaYLjj_csOuVypks5qeqVMgaJpZM4JhWhe
.

@thewax Pulled the code to RatchetPro: https://github.com/mazong1123/ratchet-pro/commit/d24fe4668001835d0f27b6a9d3c29e970d173104


[docathon] updated readme

[docathon] updated readme
updated the readme as part of docathan to be much more concise.
redirects to full documentation for more information on SDK details, faqs, and other resources that were here before.

Have the deleted sections been moved to the docs or to the wip_docs section? If not it will be good to move them as part of this diff @tanya-rai

okay will move to wip-docs so it's not lost


Image compatible

Unable to set hideBackgroundDots: true on Safari Browser.
Result: The spacing of the image will become a blank empty space, without any image render.

Can use base64 image on chrome browser only, unable to work on safari and ionic platform.
Result: No image generated.

Unable to use external url for image.
Result: No image generated.

Unable to read image while using Ionic + Capacitor + Angular, on mobile platform, eg iOS and Android.
Result: Once passed image the whole QR code unable to generate.

I love qr-code-styling it really solve the problem and look nice, but I need it to works on Ionic platform.
Any ideas?

I have the same issue

It started working for me after I passed a margin into the options.
new QRCodeStyling({
    ...
    imageOptions: {
      crossOrigin: 'anonymous',
      margin: 1, // <- This fixed the issue for me
    },
})

Removing the type 'svg' fixed it for me:
new QRCodeStyling({
    width: size,
    height: size,
    // type: 'svg', <- Removing this line fixed it for me
    data,
    ...
})

Having the same issue when loading for the first time.  After a refresh, the image loads.  @Kiesco08 is the image still an SVG when you remove that 'type' property?  My guess is it's now a .PNG.

It becomes an PNG. In my case, I needed to display the QR on a webpage, and offered a "Download" button. I worked around the issue by having two version of the same QR code.

When displayed, I use an SVG
When downloading, I create a new QR code that uses PNG

Actually never mind, I have a regression on Safari.

I found out that upgrading the qrcode-generator library to the latest version fixed the issue.
But I didn't want to fork my own version of qr-code-styling, so I ended up fixing the issue by using the maintained version instead:
In package.json:
  "dependencies": {
     "qr-code-styling": "https://github.com/sallandpioneers/qr-code-styling.git",
  }

Having the same issue when loading for the first time. After a refresh, the image loads. @Kiesco08 is the image still an SVG when you remove that 'type' property? My guess is it's now a .PNG.

Same issue, Have you fixed it now ?

Still can't use hideBackgroundDots with safari in version 1.8.4 @kozakdenys
Really appreciate you coming back with patches, I love the added personality a customized QR gives a pdf/website.

"qr-code-styling": "^1.6.0",
solution


Matching Pair and Balance don't work with Vue template markup

Attributes beginning @ (v-on) and : (v-bind) seem to break Emmet's find matching tag and tag balancing functions.
Also Vue attributes with fullstops (keydown.enter) with or without @ or : seems to break balancing and matching.
Would love to see fixed as it breaks these functions when working with markup in single file Vue components.

Fixed by modifying opening tag regex, PR #692
(see PR detail)

I have been struggling with the same when writing Angular template, can this be tweaked to fix this too.
https://github.com/emmetio/emmet/issues/529


Ability to select template from a list

Currently when adding full house template command, need to type template name manually.
It will be great if list of templates can be shown, similar to regular templates behavior.
*Current workaround: adding command for each template in config.edn with full render full house template name. (Or using text expander)
Thanks for this great plugin! 🙏

Hello! Thanks for the feedback!
I do plan to add the option to choose a template from a list, but first it's important to do some restructuring and add the feature of rendering standard templates with <% %> syntax. I think we can use the current task to keep track of the progress on the «template list» feature. And this one for the related.


x64 build throws malloc errors

This wouldn't run correctly for me on OS X 64-bit without the 32-bit compiler flag (-m32). I believe it comes down to line 397 in demofilebitbuf.cpp. Size of 32 is hard coded for some things but we convert to an unsigned long and move pOut by that much, which when built for 64-bit is 64 bits, and therefore write to more memory than we assigned. I believe just using an int in its place should work and appears to work.
Is this only designed for 32-bit architecture? Are other things likely to go wrong with this fix? I have briefly tested out putting game events and it appeared to work as expected.

Hi Will,
this commit https://github.com/abenea/demoinfogo-linux/commit/da17ab2b0cef6f4cbd98c01df5ecb3cc3c26edcc might help


✨ Support creating management v3 cluster

What this PR does / why we need it:
This PR adds support for representing imported CAPI clusters as management.cattle.io/v3 clusters instead of the current provisioning.cattle.io/v1 resource.
ADR 8 contains the rationale behind choosing this implementation approach and the discussions on different alternatives before agreeing to a decision.
This includes a new import controller specific for the new type of resource, which is only enabled if using a feature flag, so the default behavior of Rancher Turtles is to continue with the current import strategy. Some of the functions that are used by both controllers have been centralized so that we have less code to maintain. Still, some of the controller code is very similar to one another but re-utilizing it would probably increase complexity and reduce readability.
An E2E specification equivalent to the existing import gitops has been created for when Rancher Turtles is executed with this feature flag enabled.
There are definitely improvements to the way the code is structured. Especially in terms of increasing the re-usability, for both controller and E2E, but my opinion is that this PR is large enough to also add a larger refactor. Probably it would be better if we can have a couple of follow-ups to simplify the code where possible. But this is obviously a team decision. Additionally, there will be a discussion on whether we should move completely to this new controller and deprecate provisioning.cattle.io, so it may not make much sense to invest time in increasing re-usable components at this point.
Which issue(s) this PR fixes:
Fixes #298
Special notes for your reviewer:
~The DeletionTimestamp seems to not be set when the Rancher Cluster is deleted. The logic is the same that we use for other controller, though. I would appreciate any feedback on this. I'll leave a comment below.~
The new feature flag is added to the docs here.
Checklist:

[x] squashed commits into logical changes
[x] includes documentation
[x] adds unit tests
[x] adds or updates e2e tests

@richardcase review suggestions have been addressed.

This is now updated and rebased with the recent changes to the test environment.

Reminder that there's also this documentation PR https://github.com/rancher-sandbox/rancher-turtles-docs/pull/59 to document the new feature flag.


Update Cognito post-confirmation Lambda hook

I was running though this workshop in preparation for an upcoming event - when signing up on the frontend, I was getting an error after inputting my confirmation code:

I traced it back to the post confirmation Lambda trigger - it was trying to reference cognito:email_alias instead of simply email which stores the user email. This error was also preventing the SNS subscription from being auto-created since this is also done in the same Lambda function.
I changed the line of code, redeployed, and all is working well.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

+1

+1


Kore debugger

The code for the debugger API, and the KORE based implementation. Carries over code from #1532 .
@grosu @dwightguth This pull request is not yet ready for merging. Please feel free to review. More commits to be added.

Jenkins: test this please

lgtm, one minor thing to do, plus gut the internal of DebugExecutionMode so that it's not cluttered with temporary code, and then you can merge it if the tests pass.

lgtm. You can merge this if you are done working on it.


Improve error reporting for short cluster names

Improve error reporting for short cluster names

Coverage remained the same at 23.673% when pulling 1131dee90ee88d4f677b69686a9fbfaa96058878 on fix-short-names into 75a1d782b0d533a8db279dce5319af1a8dd0e1fa on master.

:+1:


PKG-3453

Changes:

new feedsotck

https://github.com/jupyter-widgets/traittypes/tree/0.2.1

Linter check found the following problems:
The following problems have been found:
WARNING: clone/recipe/meta.yaml:41: missing_description: The recipe is missing a description
Warnings were found


Mod using too many ticks on dedicated server. 1.17.1

I installed the mod on a server of mine because I thought it would bring more life to my modded server. everything was fine at first, and that probably was because we hadn't walked on that many grass blocks yet. after a few days however, the server started experiencing lots and lots of problems and lag. I was forced into installing a mod called Observable, it basically allows me to see what is causing lots of lag on the server. This mod was doing almost 7 million ticks. I assume that was every second. i was forced to remove the mod in order to clear the lag on my server. my server was running with 8GBs of ram. and it was on a separate device that had nothing running in the background with good connection. perfect for a dedicated server.
I think mobs being able to produce paths is part of the issue. because mobs walking everywhere creating path blocks would definitely cause some performance issues as it will be detecting these movements. Therefore, I think that if you attempt to optimize this mod. Allowing to toggle Mob path off through config would be great.
On this screen shot, you can see just how much this mod ticks, and in the background, all those green highlighted blocks are path blocks. each of them individually ticking.

Yes it's indeed a lot of ticks. I put it on the to-do list, first I will add a toggle switch for the creation of path by the mob. Then I'll look deeper in the mod to optimize it

I think one of the issues is that path blocks that aren't rendered are still ticking. Because using Observable I could detect path blocks far in the distance. That chunk wasn't even loaded I think. One thing I also think would be helpful is if I get to decide specifically how much each path block stage takes to be walked on to go up or down. Because then I could turn off mob paths, and then set the first stage to turn back to normal grass after a very short period of time. Which means that the only actual paths would be the ones we constantly walk on, and not the ones that we make while we go out adventuring.

So I added a value to enable mob path creation. You can already tweak time between states of path block.
I don't close this issue because I think I can go deeper in the optimisation.

I think that you should also add a whitelist feature. Being able to select individual mobs to create paths would be great! Optimization + Customization. I'd probably use it to make it so that the only other entity that makes paths are villagers.

What are you using to show that aggregated results list of us/t per block type?

Observable. I don't remember whether it's on forge or fabric, maybe both. I'll leave that to you :)

It's on both, thanks!


Update to version 2.4

Issue: https://github.com/open-cluster-management/backlog/issues/13635
This PR also removes the kui chart from release-2.4

/lgtm

/unhold


Add public keys for more issuers

EFTLab provides a list of keys from well-known issuers:
https://www.eftlab.com/knowledge-base/243-ca-public-keys/
Wish it could be added to the default configuration. Thanks a lot.

I haven't added the keys in the past as I don't have test cards to verify if the cards work with the project. However, if there's need for having more keys in the configuration I (or anyone else) could add them easily.
Currently added keys are stored and can be edited in following files:

https://github.com/mrautio/emvpt/blob/master/emvpt/src/config/scheme_ca_public_keys_production.yaml
https://github.com/mrautio/emvpt/blob/master/emvpt/src/config/scheme_ca_public_keys_test.yaml

Thank you for replying. May I later issue a PR to add keys that can successfully complete the transaction on test card?

Yes, you may. 😄  Let me know if any help is needed in case of any issues.


Compile information about the different kinds of encodings used across FHE schemes

For one data point, the OpenFHE pke library supports BGV, BFV, and CKKS, and they use the same plaintext base and encoding parameters base for all schemes: https://github.com/openfheorg/openfhe-development/blob/4ebb28ea7bdd894a73bc5b73e59fcfbc78253308/src/pke/include/encoding/plaintext.h#L65

@AlexanderViand-Intel do you have any references to those more exotic encodings?

CKKS in microsoft SEAL encoding is implemented separate from BG/FV - (some example here: https://github.com/microsoft/SEAL/blob/82b07db635132e297282649e2ab5908999089ad2/native/examples/5_ckks_basics.cpp#L77C44-L79C54) but per the scaling, it seems like that could be achieved with the common parameter base you linked.

So it seems like the three approaches are:

CGGI: encode a small integer inside a larger integer segmented as padding | cleartext | noise, with padding=1 usually.
BGV/BFV with "DCRT": encode a vector of integers as evaluations of the plaintext polynomial at roots of unity, use INTT to get the actual polynomial plaintext (with some ring theory to show why INTT corresponds to a CRT reconstruction). If the input cleartext is too large for the polynomial ring coefficient space, you can precede this encoding with another CRT (just on plain integers) to decompose the cleartext into a vector of small-enough integers. Hence, they call this the "double CRT" representation.
CKKS with RNS: encode a vector of real or complex numbers by inverting the "canonical embedding" (evaluate at half the roots of unity, ignoring complex conjugates since they can be derived from the first half), discretizing halfway through because arbitrary complex numbers won't land in the image of the canonical embedding. Apparently there are multiple discretization options (including component-wise randomized rounding!) but they all first scale the input by a scaling factor to preserve the MSBs.

One thing that I'm still not clear on is how BGV and BFV differ in their encodings. I have heard that BFV uses the LSBs and BGV the MSBs, but I don't see that difference materializing in SEAL or OpenFHE directly.

I have heard that BFV uses the LSBs and BGV the MSBs, but I don't see that difference materializing in SEAL or OpenFHE directly.

This isn't found in the plaintext encoding, but is actually a result of their differing encryption techniques. In BGV, the encryption of a message m with plaintext modulus t is
m + t*e mod q

While in BFV it is
[ (q/t)*m ] + e mod q

You can see this for example in the BGV encryption here: https://github.com/ericastor/openfhe-development/blob/2b067383a7c8d7f94620f1a13a50e3678d4dd4f3/src/pke/lib/scheme/bfvrns/bfvrns-pke.cpp#L131
while the default, (I think?) is https://github.com/ericastor/openfhe-development/blob/2b067383a7c8d7f94620f1a13a50e3678d4dd4f3/src/pke/lib/schemerns/rns-pke.cpp#L63

Based on this, my plan is to create the LWE toolbox dialect (named lwe) to contain three attributes for RLWE encoding with a common base class, one for each of:

CoefficientEncoding (CGGI LUT polynomials and uncommon encodings for BGV/BFV)
RNSEncoding (BGV/BFV default encoding)
ApproximateEmbeddingEncoding

And then an attribute for LWE int-within-an-int encodings that is basically only for CGGI.


Added .travis.yml CI configuration

For instructions how to enable Travis CI for your github project see:
https://docs.travis-ci.com/user/getting-started/

If you decide to merge this you'll have to configure the project settings in github to allow travis ci to integrate with the project. You should set that up first, and then I can update the README.me to point to your repository on the master branch prior to merging.
For an example to see what this will do, you can review the branch in my repository. Everything is configured and working properly.

Here's the link https://travis-ci.org/groakley/phase-vocoder-java. Let me know if I need to change any of the settings.

I think everything is setup properly now such that if you merge the pull request your project's README.md file will show the CI build status. That's with the assumptions that you've configured the project to use travis ci.

I think everything is setup properly now such that if you merge the pull request your project's README.md file will show the CI build status. That's with the assumptions that you've configured the project to use travis ci.


[1.12] Increase number of diagnostics fetchers

High-level description
Number of diagnostics feathers controls the parallelism level of diagnostics bundle creation job. We did test it on latest master release and it is safe to increase it to 100. This should significantly reduce diagnostics bundle generation time.
Corresponding DC/OS tickets (required)

DCOS-51483 Increase number of workers configured

Related tickets (optional)

DCOS-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot label Ready For Review

@mesosphere-mergebot request-review @drewvanstone @br-lewis @makkes @bamarni @rgo3

@mesosphere-mergebot sync

:wave: @drewvanstone @br-lewis @makkes @bamarni @rgo3  Can you review, please?


Add support for HTTP

Advantages:

Easier to run behind other reverse proxies (see #38)
Can enable ACME HTTP challenge while we're at it
HTTP is insecure but it has its place. If the choice is between someone putting their site on the web as HTTP vs not because they couldn't figure out TLS, I'll take the HTTP.

This will be useful for a setup that I am currently planning to setup with boringproxy, not knowing this was currently not yet possible.
+-----------+         +-----------+
| OpenWRT   |         | Nextcloud |
| hostnames |         | http      |
+-----|-----+         +------|----+
      |                      |
      |                      |
      |                      |
+-----|-----+        +-------|------+
| LAN User  ---------- Caddy        |
+-----------+        | http + https |
                     +-------|--|---+
                             |  |
                             |  |
                             |  |
                            +|--|----------+
                            ||Boringproxy  |       +-----------+
                            ||http + https --------- WAN User  |
                            +|--|----------+       +-----|-----+
                             |  |                        |
                             |  |                        |
                             |  |                        |
                     +-------|--|---+             +------|------+
                     | ACME Server  |             | PowerDNS    |
                     +--------------+             | authorative |
                                                  +-------------+

In this setup the authorative name server and the recursive LAN resolver will serve different IP addresses for the desired host, but both Caddy and Boringproxy are expected to generate and serve valid TLS certificates through an ACME server.
This has the effect that the Nextcloud can be accessed locally at full LAN speed, while being available securely on the public internet, both with the same address and scheme.

@almereyda what's your timeline for this? I'm pretty strapped at the moment. It would be ideal if you can wait a couple-three weeks.

Actually an alternative path has been laid out by you in https://github.com/boringproxy/boringproxy/issues/35#issuecomment-758091437
I'm not pressed in any way, this is an experiment for aesthetical tryouts extending from the experiences in #8 and #38.

Sounds good. Let me know if anything changes and I may be able to bump the priority.

This should be working in the latest release, using -http-port, -https-port, and -allow-http.


Parallel requests

We could consider adding a concurrency API to simplify making multiple requests in parallel.
I'll give sync examples here, but we'd also have equivelent async cases too.
If you have a number of requests that you'd like to send in paralell, then...
with client.parallel() as parallel:
    homepage = parallel.get("http://example.com/homepage")
    another = parallel.get("http://example.com/another")
    response = homepage.get_response()
    response = another.get_response()

Alternatively, if you don't need to care about getting the responses back out-of-order, then:
with client.parallel() as parallel:
    for page_number in range(0, 10):
        parallel.get(f"http://example.com/{page_number}")
    while parallel.pending:
        response = parallel.next_response()

Nice things here:

Bring the goodness of async's lightweight parallelization to standard threaded code.
For the async case, users don't need to touch lower-level flow-forking primitives. asyncio.gather or whatevs.

Currently I'm using requests-async to generate a bunch of requests to get simultaneously and using asyncio.gather and to run them all (Modified from actual code that splits up a large range into multiple "pages"):
async def get_async_results(*, kwargs):
    ...
    queries = []
    for i in ...:
        # modify params dict
        queries.append(async_session.get("/services.json", params=params))
    return await asyncio.gather(*queries)

results = asyncio.run(get_async_results(kwargs))
return sorted([inner for outer in results for inner in outer])

And then I join the results together and return the resulting formatted data.
I recently came across the requests-toolbelt again and found it has a solution for threading as well:
https://toolbelt.readthedocs.io/en/latest/threading.html
https://github.com/requests/toolbelt/blob/master/requests_toolbelt/threaded/pool.py
Is the second example something I could use in my current code? I'd imagine something as simple as:
results = []
with client.parallel() as parallel:
    for page_number in range(0, 10):
        parallel.get(f"http://example.com/{page_number}")
    while parallel.pending:
        response = parallel.next_response()
        results.extend(response)
results.sort()

Would get me far.

Just curious, why not just asyncio.gather ?

The ability to loop through several generated requests and extend a list of results is appealing, and I haven't figured out how to do that with asyncio.gather() yet.

Let's just leave this up to the primatives of whatever concurrency framework the user is working with.


Hello, can you provide the train_config file?

Same file missing.

Thanks for comments. We have no plans to release the training code recently. You can try it according to the details of the paper.

Thanks for comments. We have no plans to release the training code recently. You can try it according to the details of the paper.

Ok,So how can i test with the pretrained model without training?How to config the test_config.py file?Can u give some tips?Thank you very much.

Here are some mistakes and we have fixed them. Use the latest code please.

Here are some mistakes and we have fixed them. Use the latest code please.
You only need to set MODEL_PATH to your model path in test_config.py.

useless!ImportError: No module named 'train_config'. I git the latest code.But I still have the same mistakes!

Here are some mistakes and we have fixed them. Use the latest code please.
You only need to set MODEL_PATH to your model path in test_config.py.

I have git the latest code,Same problem,it need the train_config.py file.

Sorry for that, we have updated the code again.

Sorry for that, we have updated the code again.

Thank you very much! It works now.

Sorry for that, we have updated the code again.

Thank you very much!


[PDI-15507] Connections not being released after SQL Exception

-added tests for throw exception in methods commit() and pstm.close()
-added fix in disconnect() for close connection  in these cases

Build Completed
:x: This pull request has errors. They will need to be addressed before it can be accepted. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/unit-test -f core/build.xml clean-all resolve jacoco && ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/integration-test -f core/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  core/src/org/pentaho/di/core/database/Database.java
  core/test-src/org/pentaho/di/core/database/DatabaseUnitTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.database.Database

Branch Change:  + 1.74%
Complexity Change:  + .66%
Instruction Change:  + 1.08%
Line Change:  + 1.90%
Method Change:  + 1.73%

org.pentaho.di.core.logging.LogChannel

Complexity Change:  + 1.61%
Instruction Change:  + 1.93%
Line Change:  + 1.38%
Method Change:  + 2.56%

License header violations

:heavy_exclamation_mark: Copyright year is not the current year on core/test-src/org/pentaho/di/core/database/DatabaseUnitTest.java. Found 2015. Was expecting 2016

Copyright year is fixed.

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/unit-test -f core/build.xml clean-all resolve jacoco && ant -Dpentaho.resolve.repo=http://ivy-nexus.pentaho.org/content/groups/approved -Dtestreports.dir=bin/reports/integration-test -f core/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  core/src/org/pentaho/di/core/database/Database.java
  core/test-src/org/pentaho/di/core/database/DatabaseUnitTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.database.Database

Branch Change:  + 1.74%
Complexity Change:  + .66%
Instruction Change:  + 1.08%
Line Change:  + 1.90%
Method Change:  + 1.73%

org.pentaho.di.core.logging.LogChannel

Complexity Change:  + 1.61%
Instruction Change:  + 1.93%
Line Change:  + 1.38%
Method Change:  + 2.56%


custom training data split

hello. Thanks for sharing your great research!
I'm going to do an experiment to see the effect of data size on diffsinger model training.
So, I want to train using only a part of the opencpop data, but I am having a hard time figuring out how to use only the specified segment file for training.
Can I just make the desired data exist in data/raw and then run binarize.py?
It would be a great help if you could give me an answer.
thank you!

Has this problem been solved? If yes, how did you solve it? thank you

Have you done the experiment yet? How does data size affect the quality of Diffsinger model (midi version)?


Support dynamic values via field substitution for the opsgenie_addr field

Description

Checklist

[x] I have reviewed the contributing guidelines.
[x] I have included unit tests for my changes or additions.
[x] I have successfully run make test-docker with my changes.
[x] I have manually tested all relevant modes of the change in this PR.
[x] I have updated the documentation.
[x] I have updated the changelog.

Questions or Comments
Unit test is not necessary as the current tests sufficiently cover this small change.

Thanks for the submission. Unit tests are required, even for this small change. It should be possible to modify an existing test to prove that the to_addr is dynamically updated with the match data.

Thank you. It looks like the build failed due to some whitespace linting checks. Please review the build output. Once you get this to pass we can get it merged in. make test-docker will give the same failure and results, so you can use that to verify before you push.

One more:
 ./alerters/opsgenie_test.py:1275:39: E231 missing whitespace after ','


Ability to configure Emissary to route to pods in the same Availability Zone if possible

Please describe your use case / problem.
Is it possible with Emissary to route requests to pods located in the same Availability Zone as the Emissary pod handling the traffic?
We are using KubernetesEndpointResolver which as far as I can tell has no configuration.
We would like to reduce the cross-AZ traffic to reduce costs.
Describe the solution you'd like
A way to configure Emissary (or the KubernetesEndpointResolver to prefer to use Pods for a given service that are within the same AZ as the Emissary pod handling the request).
Describe alternatives you've considered
I looked through the Emissary documentation and didn't find anything to this effect.
https://emissary-ingress.dev/docs/3.8/topics/using/mappings/
https://emissary-ingress.dev/docs/3.8/howtos/route/
https://emissary-ingress.dev/docs/3.8/topics/running/resolvers/#the-kubernetes-endpoint-resolver
https://emissary-ingress.dev/docs/3.8/topics/running/load-balancer/
I didn't find anything that looked like it would solve this in the LoadBalancer policy
Additional context
We are using Emissary 3.8.2

Emissary can't do this natively. 🙁 The endpoint resolver is definitely where to start, but if you're after reducing cross-AZ traffic you're probably better off doing that in the service mesh.
(Full disclosure: I'm employed by Buoyant. I think Linkerd's HAZL is extremely cool, but on the other hand, if you're interested in adding this to Emissary, I'd be totally down to support you! though I'd strongly suggest you start with the dev/v4` branch rather than Emissary 3.)

Thanks @kflynn
After some further research, I think I may be able to get what I need with Topology Aware Routing in newer versions of K8S.
Just gotta do those upgrades now.


Opening directories containing spaces are not working

Failed hard, sorry for that: URL.path will replace "%20" with " " but the constructor of URL(string:) is  assuming the string contains "%20" -> An instance of of URL(string:) will always fail if the path contains space

All right, I've had fixed this before, but forgot to commit.
The version I have uploaded online is working.
Thanks :)

Good to know you've already fixed that. Sorry again.


The default_config and the cloud component will not initialize

Home Assistant release with the issue:

Version 0.98.5
arch	x86_64
dev	false
docker	true
hassio	true
os_name	Linux
python_version	3.7.4
timezone	Europe/Copenhagen
version	0.98.5
virtualenv	false
Last working Home Assistant release (if known):
Versin 0.98.4
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Component/platform:

default_config
cloud
Description of problem:
The default_config and the cloud component will not initialize.
If the system is rebooted, it takes about 15-30 minutes to become online.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

# Configure a default setup of Home Assistant (frontend, api, etc)
default_config:

homeassistant:
  name: GravgaardKlanen
  auth_providers:
   - type: homeassistant
   - type: legacy_api_password
     api_password: <REDACTED>
  customize: !include customize.yaml

group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:
#   base_url: example.duckdns.org:8123

#Stream configuration
stream:

# You can leave MAC empty if you only have one gateway.
xiaomi_aqara:
  discovery_retry: 20
  gateways:
    - mac: 7811<REDACTED>
      key: <REDACTED>
    - mac: 04CF<REDACTED>
      key: <REDACTED>
    - mac: 04CF<REDACTED>
      key: <REDACTED>

input_boolean:
  notify_driveway:
    name: Bevægelse i indkørslen
    initial: off
  sonos_p7:
    name: Sonos spiller P7 mix
    initial: off
  sonos_p4:
    name: Sonos spiller P4
    initial: off
  heater_state:
    name: Håndklædetører State
    initial: off
  empty_mailbox:
    name: Tøm postkassen
    initial: off

input_select:
  sonos_playing:
    name: Is Sonos Playing
    options:
      - Playing
      - Not Playing
    initial: Not Playing
    icon: mdi:music-note
  sonos_playing_p7:
    name: Is Sonos Playing P7
    options:
      - Playing
      - Not Playing
    initial: Not Playing
    icon: mdi:music-note
  sonos_playing_p4:
    name: Is Sonos Playing P4
    options:
      - Playing
      - Not Playing
    initial: Not Playing
    icon: mdi:music-note
  springvand:
    name: Springvand
    options:
      - Turned on
      - Turned off
    initial: Turned off
    icon: mdi:water

#Alert
alert:
  alert_driveway:
    name: Bevægelse i indkørslen
    done_message: Ingen bevægelse
    entity_id: input_boolean.notify_driveway
    state: 'on'
    repeat: 15
    can_acknowledge: true
    skip_first: true
    notifiers:
      - notify.ios_christian

# Sensors
sensor:
  # Weather prediction
  - platform: yr
  - platform: darksky
    api_key: <REDACTED>
    language: da
    latitude: 55.987075
    longitude: 12.032299
    forecast:
      - 0
      - 1
    hourly_forecast:
      - 0
      - 1
    monitored_conditions:
      - summary
      - icon
      - temperature
      - precip_type
      - precip_intensity
      - precip_probability
      - precip_accumulation
      - temperature
      - apparent_temperature
      - dew_point
      - wind_speed
      - wind_gust
      - wind_bearing
      - cloud_cover
      - humidity
      - pressure
      - visibility
      - ozone
      - daily_summary
      - minutely_summary
      - hourly_summary
      - temperature_high
      - temperature_low
      - apparent_temperature_high
      - apparent_temperature_low
      - precip_intensity_max
      - uv_index
      - moon_phase
      - sunrise_time
      - sunset_time
      - nearest_storm_distance
      - nearest_storm_bearing

http:
  cors_allowed_origins:
    - <REDACTED>
    - <REDACTED>
  use_x_forwarded_for: true
  trusted_proxies:
    - <IP_ADDRESS>/16
  ip_ban_enabled: false
  login_attempts_threshold: 3
  base_url: <REDACTED>

# Text to speech
tts:
  - platform: google_translate
    language: 'en-us'
    cache: true
    cache_dir: /tmp/tts
    time_memory: 300

ihc:
  - url: <REDACTED>
    username: <REDACTED>
    password: <REDACTED>
    auto_setup: true
    info: true
    light:
      - id: 79451
        name: ventilator_stort_bad
      - id: 1884507
        name: standby_kreds
      - id: 437851
        name: hustilstand_nat
      - id: 437595
        name: hustilstand_hjem
      - id: 437339
        name: hustilstand_ude
      - id: 437083
        name: hustilstand_ferie
      - id: 66899
        name: Springvand
      - id: 438362
        name: alarm_armeret
      - id: 438874
        name: alarm_gaaet
      - id: 4941147
        name: forhave_uplights
    binary_sensor:
      - id: 436826
        name: hustilstand_nat
      - id: 436570
        name: hustilstand_hjem
      - id: 436314
        name: hustilstand_ude
      - id: 436058
        name: hustilstand_ferie
      - id: 84570
        name: Køkken Nederst venstre
      - id: 84826
        name: Køkken Nederst højre
    sensor:

google:
  client_id: <REDACTED>
  client_secret: <REDACTED>

device_tracker:
  - platform: icloud
    username: <REDACTED>
    password: <REDACTED>
    account_name: <REDACTED>
    gps_accuracy_threshold: 100
    max_interval: 10

proximity:
  home:
    devices:
      - device_tracker.annkathrines_iphone
      - device_tracker.christian
      - device_tracker.max
      - device_tracker.victor
    tolerance: 50
    unit_of_measurement: km

Traceback (if applicable):

2019-09-12 20:36:23 ERROR (MainThread) [homeassistant.setup] Error during setup of component cloud
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/setup.py", line 168, in _async_setup_component
    hass, processed_config
  File "/usr/src/homeassistant/homeassistant/components/cloud/__init__.py", line 167, in async_setup
    from hass_nabucasa import Cloud
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/__init__.py", line 13, in <module>
    from .auth import CognitoAuth
  File "/usr/local/lib/python3.7/site-packages/hass_nabucasa/auth.py", line 9, in <module>
    import warrant
  File "<frozen importlib._bootstrap>", line 983, in _find_and_load
  File "<frozen importlib._bootstrap>", line 967, in _find_and_load_unlocked
  File "<frozen importlib._bootstrap>", line 677, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 724, in exec_module
  File "<frozen importlib._bootstrap_external>", line 857, in get_code
  File "<frozen importlib._bootstrap_external>", line 525, in _compile_bytecode
ValueError: bad marshal data (invalid reference)
2019-09-12 20:36:24 ERROR (MainThread) [homeassistant.setup] Unable to set up dependencies of default_config. Setup failed for dependencies: cloud
2019-09-12 20:36:24 ERROR (MainThread) [homeassistant.setup] Setup failed for default_config: Could not set up all dependencies.

Additional information:

After subscribing to the beta channel and upgrading to 0.99.0b1 problem went away. It seems to be fixed.


The github project description / website seems inappropriate

The description reads: Configuration library for JVM languages
The website is: http://typesafe.com
I don't think anyone who would like to learn more about this specific project would find the cited website terribly insightful. Perhaps leave that field blank?

While I see your point Mike, it's the website of the company which funds people to maintain this project...
Why not use the field to say thanks? I'd personally do this even on personal projects to raise awareness of "oh, it's that guy", why not do this with a library and company backing it then?

how about pointing at https://typesafehub.github.io/config/ instead...?

@SethTisue I think that would be appropriate

lightbend.com is just as broken as typesafe.com, unless Lightbend has decided to start running ads on all their github projects. I'll step back now.

We can do https://typesafehub.github.io/config/ however this requires additional work of making the docs actually available there.

@ktoso aren't they already? am I missing something?

Not really a nice page to show and direct people to 😉  Thus, I agree on directing to that site, but it should make sense, i.e. the readme be hosted there in a usable format. Which needs to be fixed before we do the link change.

unless or until something changes there, how about just not having any link at all, then? I agree with Mike that linking to typesafe.com or lightbend.com isn't helpful to the users we would like to attract. having that link there is likely to give people a lower opinion of Lightbend, not a higher one. it isn't what the URL field is for; the field has an established purpose and this isn't it.
if we want to thank or credit Lightbend for supporting the creation of the library, a better way to do that would be something in the readme.
well, I guess I'm bikeshedding a bit about a pretty small issue. you've heard my opinion, I'm fine with whatever you decide.

The "home page" right now is effectively the README, I would say. Thats where all the info is.

So to re-iterate what I think is useful and resolves this issue: making README.md available such that it's under https://typesafehub.github.io/config/
Is this simple to do on github pages? I can try some of my nights but help would be welcome ;)

Check out the gh-pages branch and you can edit index.html; the reason it has a link instead of a cut-and-paste of README right now is to avoid it getting out of date. Maybe could use JS to dynamically suck in the latest README, or something like that, or just make updating it part of the release instructions in CONTRIBUTING.md.

Yeah I'd want to avoid the gh-pages branch and the copy pasta. I believe that's doable, will attempt to find time for it tonight.

Here is a JQuery HTML includer that has worked well for me in the past. Usage example:
$("#id").load("mypage.html");

The SBT Microsites Plugin looks like it might be useful

So sadly it's not really possible to make this pain free without investing into a lot of external automation: http://stackoverflow.com/questions/15214762/how-can-i-sync-documentation-with-github-pages
Changed the link, hope the ugly page does not so nice looking page does not scare anyone away ;-)
Any help on improving it is very welcome.


Switch image uploading to a library

So that we don't have to maintain our own library for this.
I used ng-file-upload to upload to s3, essentially just taking out the existing ngs3upload library, which was pretty messy, and removing the uploader.js coffee script file which was just causing confusion.
The result is slightly more straightforward, and it should be easier to now set up an alternative upload process for local development without s3 (because ng-file-upload can also handle this).
Also removed angular-sanitize and angular libraries stored in our source code which closes #906.

Coverage increased (+0.0006%) to 99.361% when pulling 71840efe15450675aad0e16cb5fd1bee5eef882f on fix/image-uploading into c385e9864d176841a2462f8a88e0447a9e0277f6 on master.

Coverage remained the same at 99.361% when pulling 9fb0b45249ff881c4c18f2d82d62a6c16e76aeee on fix/image-uploading into c385e9864d176841a2462f8a88e0447a9e0277f6 on master.

Coverage remained the same at 99.361% when pulling 9fb0b45249ff881c4c18f2d82d62a6c16e76aeee on fix/image-uploading into c385e9864d176841a2462f8a88e0447a9e0277f6 on master.

Coverage remained the same at 99.361% when pulling 9fb0b45249ff881c4c18f2d82d62a6c16e76aeee on fix/image-uploading into c385e9864d176841a2462f8a88e0447a9e0277f6 on master.

Coverage decreased (-0.05%) to 99.313% when pulling f460af5a02da52f82d410d59988f159d701f7698 on fix/image-uploading into c385e9864d176841a2462f8a88e0447a9e0277f6 on master.

Coverage decreased (-0.05%) to 99.313% when pulling d1063f6c37bf89469657e518d210b0cf33ea3728 on fix/image-uploading into c385e9864d176841a2462f8a88e0447a9e0277f6 on master.

Coverage decreased (-0.05%) to 99.313% when pulling 687dfbf4608ac9fa99984cf2a48f58f177946a02 on fix/image-uploading into c385e9864d176841a2462f8a88e0447a9e0277f6 on master.

Coverage decreased (-0.05%) to 99.313% when pulling<PHONE_NUMBER>ebe6bc33cff2a5e3055572224a577e on fix/image-uploading into c385e9864d176841a2462f8a88e0447a9e0277f6 on master.


Fixes: https://github.com/komuw/ote/issues/19

Codecov Report

Merging #21 (0ddd53e) into main (b996935) will decrease coverage by 0.44%.
The diff coverage is 0.00%.

:exclamation: Current head 0ddd53e differs from pull request most recent head 5e2492d. Consider uploading reports for the commit 5e2492d to get more accurate results

@@            Coverage Diff             @@
##             main      #21      +/-   ##
==========================================
- Coverage   53.16%   52.71%   -0.45%
==========================================
  Files           5        5
  Lines         237      239       +2
==========================================
  Hits          126      126
- Misses         89       90       +1
- Partials       22       23       +1

Impacted Files
Coverage Δ

import.go
70.29% <0.00%> (-1.43%)
:arrow_down:

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 b996935...5e2492d. Read the comment docs.


Update cards for M20

Hi @Fugiman -- Just thought I'd send a PR with the M20 card updates for Deckmaster.  The set went live this week on Arena and it'll help Twitch streamers and community if the cards are visible with the Deckmaster extension.
CC @JeffHoogland

I just regenerated redirector/cards.js using the same language and image sort order so that the diff is cleaner.  That's the force push on this branch.  I spot-checked some of the new additions and the image links seem correct.

Closing in favor of #47


Extracted text is not indexed unless you manually reindex

Stumbled into this when testing the build for 1.1.0.
To recreate

Ingest some paged content
Go to a page and look at its extracted text file
Search for something in the text
Should get no results
Go to Configuration > Search and Metadata > Search API and click on the "Default Solr content index" link next to "Index".
Re-index solr by clicking on "Queue all items for re-indexing"
Click confirm
Scroll down and click "Index now"
Search again for something you know is in the text
Now you should get results

Resolved with https://github.com/Islandora/islandora/commit/029bbcfe5dd6abe510bcda8717ed36d4fc61269e


Can you modify the implementation?

thank you provide this lib。
for sub/pub model, subscriber received msg include the code。
server code:
if((i % 2) == 0)
{
ZmqMsg workMsg("A workA" + i);
socket.send(workMsg);
}
if((i % 2) == 1)
{
ZmqMsg workMsg("B workB" + i);
socket.send(workMsg);
}
subscriber A received msg is
A workA0
...
subscriber B received msg is
B workB1
...
i hope subscriber A received msg is
workA0
...
subscriber B received msg is
workB1
...
i more hope server code like this:
if((i % 2) == 0)
{
socket.subscribe("A");
ZmqMsg workMsg("workA" + i);
socket.send(workMsg);
}
if((i % 3) == 1)
{
socket.subscribe("B");
ZmqMsg workMsg("workB" + i);
socket.send(workMsg);
}
can you modify it?

ok, wo study zmq no enough. ==

ok, i study zmq no enough. ==


Failed to load dynamic library 'libopencv_dart.so': dlopen failed: library "libcamera2ndk.so" not found

Describe the bug
I get this exception when I run my code to decode Uint8List image.
E/flutter ( 2931): #1      new DynamicLibrary.open (dart:ffi-patch/ffi_dynamic_library_patch.dart:22:12)
E/flutter ( 2931): #2      loadNativeLibrary (package:opencv_dart/src/native_lib.dart:37:29)
E/flutter ( 2931): #3      cimgcodecs (package:opencv_dart/src/native_lib.dart:47:48)
E/flutter ( 2931): #4      cimgcodecs (package:opencv_dart/src/native_lib.dart)
E/flutter ( 2931): #5      imdecodeAsync. (package:opencv_dart/src/imgcodecs/imgcodecs_async.dart:91:32)
E/flutter ( 2931): #6      cvRunAsync (package:opencv_dart/src/core/base.dart:115:21)
E/flutter ( 2931): #7      imdecodeAsync (package:opencv_dart/src/imgcodecs/imgcodecs_async.dart:91:7)
To Reproduce
This is my code:
var res = await http.get(Uri.parse("https://avatars.githubusercontent.com/u/135967503?v=4"));
var buf = res.bodyBytes.buffer.asUint8List();
final im0 = await cv.imdecodeAsync(buf, cv.IMREAD_GRAYSCALE);
Smartphone (please complete the following information):

Android emulator
API 23 - arm64 I think

Thank you for this great library. I'm so excited for the CV optical flow !

use API 24 and above please.


vCenter :: Store empty block images in directory

Proposed fix to add option to create empty block images on specified directory instead root directory
It is needed add FOLDER_IMG attribute on datastore.

This will be treated as part of #2762


udp on windows is not aio

libuv udp on windows is not using asynchronous io, just using unblock mode. they two are not the same. unblock udp on windows is not the highest io rate.

https://github.com/libuv/libuv/blob/v1.x/src/win/udp.c#L436-L450
Are you sure about that? This code block looks to me like it is using IOCP if it doesn't immediately succeed.

Yes, I am sure.  IOCP not means AIO.  First ,udp in libuv created  never using WSA_FLAG_OVERLAPPED. Next, uv_active_udp_streams_threshold is a dead value zero, every recv using flag: MSG_PEEK, zero buf, IOCP here, just for detect data coming or not, then,do a  real recv data. Third, GetQueuedCompletionStatusEx is not using perfectly.  And, it is not able to  multiple recv or read in the same time.

Do you want to write a patch fixing this?

Does it make sense to use AIO for UDP?  Does the NT kernel block when it can't send the datagram right away or does it queue it up?

When I try to get  higher io bitrate in 10gb network,  I got a program using udp AIO,  but I cannot reach my target. So I try to using libuv to do it ( I think it's so good ), but it got more poor.  then, I  study the libuv codes.  Maybe It does not aim this.

Maybe it's different on Windows but on UNIX systems, if you simply want to pump out datagrams at the highest possible rate, the event loop model is a poor fit because of the latency it introduces.  Standard operating procedure is to have one or more dedicated threads that simply call sendmsg() in a loop.

UDP on Windows is undoubtedly using a AIO for UDP.
There's an additional optimization where the asynchronous notification is bypassed a send/receive operation can be completed no blocking, which is maybe throwing you off.
If you don't believe me, try to find the place in the source where we poll the file descriptor for readiness, which would be unavoidable if we were relying on nonblocking I/O only.
I would also like to remark that AIO isn't noticeably faster than nonblocking I/O, at least not on Windows 7 where I did most of the benchmarking. We use AIO because the preferred multiplexer GetQueuedCompletionStatusEx, which is much faster and than the alternatives (select etc), doesn't support readiness notifications (not always/officially anyway).
Closing this bug as invalid.


Fixed a few typos in ExampleRawIO

Was checking out the new documentation--theme looks great by the way and saw a few typos.  This just fixes those.

Hi @zm711 Thanks for going through this and opening a PR to fix!

Failing tests are not related to the changes here.


Parallel Domain GUDA dataset link broken

Bug
Hello,
I am unable to download the ParallelDomain GUDA dataset from the provided link (https://paralleldomain.com/public-datasets)
The link to the dataset appears to be broken/ incorrect.
To Reproduce
I use: curl -s https://tri-ml-public.s3.amazonaws.com/github/vidar/datasets/PD_guda.tar | tar xv -C vidar/
Expected behavior
The PD GUDA data should be downloadable from the link provided on this page: https://paralleldomain.com/public-datasets

Thanks for reporting this!
@kuanleetri , @chrisochoatri , when I navigate to https://paralleldomain.com/public-datasets, scroll to the bottom, and click "Download Here" for the GUDA dataset, I get an access-denied error. Did sharing permissions change?

@jieli352 @RaresAmbrus any idea about this GUDA dataset?


Vulkan instance creation

Ok this is a new branch and or to allow for more focused development of the vulkan branch. This PR relates exclusively to instance creation.

The app fails to launch unless Vulkan SDK is in PATH, because it forces validation layers in Debug, can't find libVkLayer_khronos_validation.so, and createInstance throws an error.
[E][T0] Error: { General }:
        messageIDName   = <Loader Message>
        messageIDNumber = 0
        message         = <libVkLayer_khronos_validation.so: cannot open shared object file: No such file or directory>
 [2023-08-06 07:47:01] [vkHelpers.cpp]
[E][T0] Error: { General }:
        messageIDName   = <Loader Message>
        messageIDNumber = 0
        message         = <Requested layer "VK_LAYER_KHRONOS_validation" failed to load!>
 [2023-08-06 07:47:01] [vkHelpers.cpp]
terminate called after throwing an instance of 'vk::LayerNotPresentError'
  what():  vk::createInstanceUnique: ErrorLayerNotPresent

If we detect that validation layers are requested but not available, we should remove them from the extension list. Same for debug messenger.
Or, just don't bother with validation in the app and use Vulkan Configurator.
Additionally, this exception isn't caught by the app at all, and causes it to terminate.
Related: these log messages should be on one line.

I’ve decided to just have our app not care about layers.

Didn't find anything else to add on top of karnage's review, except maybe the name of the function gameLoop() in application that I think isn't right

Yeah I’ve had some contention on how the application should be handled and I don’t like its current approach. I honestly may want to discuss it further with y’all over discord as I’m not 100% on how we are going to marry the engine and the editor.


Demo Kit Inside Demo Kit

Steps to reproduce the problem:

Visit the documentation topic "Formatting, Parsing, and Validating Data"
Click on the image (either "View" or "Model")

What happens?

The question is forwarded to my colleagues with #1870217318
Updates will be posted here as well

Dear Boghyon,
Thanks for reporting this issue. The issue is fixed in our internal documentation system. You can view the result on our nightly: https://openui5nightly.hana.ondemand.com/#/topic/68b9644a253741e8a4b9e4279a35c247
Thanks again for reporting,
Daniel Nanovski


"test5" movie metadata mismatches

( not yet sure what causes it, could be bumped dependencies )
in 2.2.0, test_refine_video_metadata started failing on video_codec and release_group:
_________________________________ test_refine_video_metadata __________________________________

    def test_refine_video_metadata(mkv):
        scanned_video = scan_video(mkv['test5'])
        refine(scanned_video, episode_refiners=('metadata',), movie_refiners=('metadata',))
        assert type(scanned_video) is Movie
        assert scanned_video.name == mkv['test5']
        assert scanned_video.source is None
        assert scanned_video.release_group is None
        assert scanned_video.resolution is None
>       assert scanned_video.video_codec == 'H.264'
E       AssertionError: assert None == 'H.264'
E        +  where None = <Movie [test5]>.video_codec

tests/test_core.py:256: AssertionError

_________________________________ test_refine_video_metadata __________________________________

    def test_refine_video_metadata(mkv):
        scanned_video = scan_video(mkv['test5'])
        refine(scanned_video, episode_refiners=('metadata',), movie_refiners=('metadata',))
        assert type(scanned_video) is Movie
        assert scanned_video.name == mkv['test5']
        assert scanned_video.source is None
>       assert scanned_video.release_group is None
E       AssertionError: assert 'subliminal' is None
E        +  where 'subliminal' = <Movie [2]>.release_group

tests/test_core.py:254: AssertionError

It looks like enzyme was not updated to version 0.5.0. Earlier versions don't work with python 3.12 if you don't have setuptools manually installed. See #1126

the latter happens with enzyme 0.5.1, and setuptools installed as well

Mmm, that's strange. The automatic tests are passing and I also cannot reproduce in local.
On 25 June 2024 16:35:38 GMT+01:00, Patrycja @.***> wrote:

the latter happens with enzyme 0.5.1, and setuptools installed as well
--
Reply to this email directly or view it on GitHub:
https://github.com/Diaoul/subliminal/issues/1135#issuecomment-2189279720
You are receiving this because you commented.
Message ID: @.***>

So it is a feature of guessit to look for parent folder to guess the name and other stuff. Because the filename test5.mkv is not indicative enough, it looks for the parents. In case of #1157, the subliminal-2.2.1 parent folder was parsed as release_group and name. I will remove this assert in #1154, so it should be solved.


DELETE FROM database not fully working

Sup, I have a problem with deleting these two values from database :
exports.oxmysql.execute('DELETE FROM player_contacts WHERE citizenid =?', { citizenid })
exports.oxmysql.execute('DELETE FROM playerskins WHERE citizenid =?', { citizenid })
Whenever i run ck command, first 4 get deleted from database, but those 2 wont.. could you give me some advice on how to repair this?
Also I wanted to add some new delete, everything was set right, still it did not deleted.. My last idea is , that it might have to do something with Database it self and values configurated in those tables? But it is just my hunch..
Thanks for your help.

Well, this is definitely weird behaviour. Are there any errors in the server console while running the character deletion?

Nie, práveže nie je tam v konzole žiadny error. Iba keď som si dal print za
každým deletom, tak som zistil, že prvé 4 fungujú, tie hodí do konzole a
potom nič. Môžem zajtra poslať screenshot ako to vyzerá?
(pardon som si až teraz všimol, že si Čech. 😅Prípadne nemáš Discord? Ale
ak ti vyhovuje github/email tak pohode. )
Dňa ne 19. 2. 2023, 12:40 Matěj Vnouček @.***>
napísal(a):

Well, this is definitely weird behaviour. Are there any errors in the
server console while running the character deletion?
—
Reply to this email directly, view it on GitHub
https://github.com/IngPleb/qb-characterkill/issues/4#issuecomment-1435965172,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALS6DDKYV74KE4EJ3WE7LP3WYIBDBANCNFSM6AAAAAAVAU75TM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Klidě si mě přidej na discordu, tam to dořešíme — IngPleb#5121


Play Store Removal?

Went to go pull down the app from the play store and I see the link is dead, searched as well and cant seem to find it, has it been removed permanently or has the name changed?

Hi,
if you need the apk, you can find it in this alt-store: https://store.nethunter.com/ .

I'm not being able to connect the app to my Cactus despite I can browse to the web page on the same mobile.
Any clue?