test for hyper pars

Adding test for hyper pars -- main check against price calced ref array.

also cleaned out try and excepts that we were using to get the runner back into a sane directory on fail
instead added autouse fixture to conftest.py that should set location before each test -- hopefully
stripped out ugly setup fixture to just have a function instead -- easier to pass args and now maintain with a bit more flexibility so we don't have to keep repeating ourselves in the initial setup of each pstfrom test.
added some docs to pp_options -- this might need formatting better for readthedocs.

coverage: 79.697% (+0.05%) from 79.644%
when pulling 6967a483f3946127153596cc8e65dba70bbfa086 on briochh:feat_ppu3
into 8b3f1b091a8aa67855e5b9f28946c737a2347282 on jtwhite79:feat_ppu3.


Split node min range is not stringent.

Previously, PassDownDomain always sets inner IterVar's extent to the split factor, even when the parent extent is less than the factor (usually happens the parent has been reduced to a single point).  Although predicates are added to guard bounds, unnecessary likely statements are inserted.  They are road blocks for tensorization/intrinsic.
The fix is simple -- set the inner IterVar's ext w/ min(r->factor, parent->range).  Here is an example from the new test:
Before:
// attr [EF] storage_scope = "global"
allocate EF[float32 * 8]
produce E {
  produce EF {
    for (i, 0, 8) {
      EF[i] = (I[i]*2f)
    }
  }
  for (i.inner, 0, 32) {
    if (likely((i.inner < 8))) {
      if (likely((i.inner < 8))) {
        EF[i.inner] = (EF[i.inner]*2f)
      }
    }
  }
}

After:
// attr [EF] storage_scope = "global"
allocate EF[float32 * 8]
produce E {
  produce EF {
    for (i, 0, 8) {
      EF[i] = (I[i]*2f)
    }
  }
  for (i.inner, 0, 8) {
    EF[i.inner] = (EF[i.inner]*2f)
  }
}

I also have to update an existing test.  I have confirmed that the test generates expected and even cleaner code (many if statements are gone) with the fix.

@Hzfengsy , can you review this PR, at least the test I updated.  Thank you.

Regarding to the failure (https://ci.tvm.ai/blue/organizations/jenkins/tvm/detail/PR-4885/1/pipeline), the underline issue is irrelevant.  This PR happens to exposed the bug, when it removes "if" statements.  I have created an issue (https://github.com/apache/incubator-tvm/issues/4890).  In such situation, how to proceed?

In this case, unfortunately we need to wait until #4890 is fixed

Update this PR with the same change to the split node's nparts mode.  It causes two more test failures:

tests/python/unittest/test_lang_tensor_overload_op.py verify_conv2d_scalar_bop
tests/python/unittest/test_codegen_blob.py test_resnet18

Further investigation shows that schedule_direct_cuda() in topi/python/topi/cuda/conv2d_direct.py binds IterVars from output stage, input padding stage, and weight loading stage to threadIdx.x.  The latter two stages attach to output stage.  With my nparts change, the latter two stage's IterVars have different ranges from the output stage's IterVar's.  TE generated wrong CUDA code causing numerical mismatch.
I propose to change schedule_direct_cuda() by removing the threadIdx.x binding in the input padding and weight loading stages.  I measured the performance of the two affected tests.  After my change, the first one changes from 0.007306 ms to 0.005902 ms, the second one 30.47 ms to 30.59 ms.


README Update

Add installation guide for the Project (How to run + Local Setup)
@akscoder082003

Add installation guide for the Project (How to run + Local Setup)
@akscoder082003

Created  a PR check out!

closed with  #5


Remove MetricConfig and directly store configs in Metric

Metric is instantiated by appropriate MetricConfig. This strategy is used only in Metric and any other classes are instantiated by directly calling __init__ with specific arguments. This special architecture around Metric actually causes some confusion (e.g., #455).
This separation also requires explicit circular dependency: Metric holds MetricConfig, while MetricConfig knows corresponding Metric (in to_metric). This is somewhat annoying because it always lets us to refactor both concepts at the same time.
As long as I checked the all subclasses of Metric, there is no heavy implementation: they simply hold configs without any special initialization processes. It looks we have no any reason to separate MetricConfig from Metric at interface level. Integrating them into the Metric could simplify the architecture.
RFC: @neubig @pfliu-nlp @tetsuok

MetricConfig is stored in MetricResult too, but it seems this information is not necessarily required. There is also Performance that has almost the same information with MetricResult, and the only difference is that it stores metric's name instead.
I think using Performance rather than MetricResult is sufficient. We can pass the original Metric with the corresponding Performance if the both should be referred.

@odashi I agree with the proposal and the potential changes. Removing the circular dependency seems a good idea to make things simpler.

@odashi

"Remove MetricConfig, store every information necessary to perform metrics to Metric."

In general, I think it looks good. I think the reason why we have two separate classes originally (Metric and MetricConfig) is to handle the following case (ref: https://github.com/neulab/ExplainaBoard/blob/cc2d315695cec30e21d369362d1c76ca2ce9d40c/explainaboard/processors/kg_link_tail_prediction.py#L134)
            HitsConfig(name='Hits1', hits_k=1),
            HitsConfig(name='Hits2', hits_k=2),
            HitsConfig(name='Hits3', hits_k=3),
            HitsConfig(name='Hits5', hits_k=5),
            HitsConfig(name='Hits10', hits_k=10),

When we merge MetricConfig into Metric, I think we will have two names for each Metric class: metric_name and metric_class_name.
(Again, I think this refactoring will potentially affect explainaboard web and I will follow PRs on this discussion.)

When we merge MetricConfig into Metric, I think we will have two names for each Metric class: metric_name and metric_class_name.

It looks natural to me, though it also looks the name field needs to be separated from Metric because it behaves a key of the objects.
Currently, metric configss are stored as list[MetricConfig] with internal key name, but it is more natural to reform it to dict[str, Metric] with explicit dictinary key so that metric_name in other classes point to the key of this dict, not the member of Metric.

@pfliu-nlp I think we can first implement dict[str, MetricConfig] and then come back to this issue.
(Generally I recommend dict[str, something] over list[(str, something)])

I found that EaaSMetricConfig has some abuse of the name field: it is used to specify external metric.
https://github.com/neulab/ExplainaBoard/blob/215785c7f8ad938ae74c47b398ca82419ecc12a5/explainaboard/metrics/eaas.py#L107

Sorry about the late comment on this, but I agree with getting rid of MetricConfig. Sounds good!


It will likely be annoying to make argparse handle this case, but I can think of a few other ways to achieve this same feature:

Pipe the command to qbatch, e.g. echo 'echo "hello world"' | qbatch -. It works, but it's unwieldy.
Create a wrapper script that calls qbatch as above. We may have to be a little clever if we also want users to be able to pass arguments to qbatch.

Do we want to encourage people to rely on the old sge_batch paradigm?
I'd be okay with a basic wrapper that allows qbatch to replace for this application,  using the default qbatch settings (modified by environment) but not any argument passing.

Do we want to encourage people to rely on the old sge_batch paradigm?

I do see how it's useful. Even without sge_batch, there are people that
use fsl_sub in the same way.

I'd be okay with a basic wrapper that allows qbatch to replace for
this application,  using the default qbatch settings (modified by
environment) but not any argument passing.

Yeah, I agree. I'll leave this for post 1.0 though.

Do we have a name for this command? Pretty sure I can hack a bash wrapper really easily..

Hmm.. What about qbatch_sub or qbsub?
Are you thinking of doing: echo "$@" | qbatch -? Almost doesn't seem worth it. :-)

yes, that is indeed what I'm thinking, I agree, it doesn't seem like it's worth it, but if it can attract users who have that workflow, might as well offer it.

Implement via the "--" heuristic mentioned in #90
@pipitone you had previously implemented -- for the options method, can you repurpose that argparse magic for single-job submission?

There's an ambiguity here: with a  single positional argument it's unclear whether the argument is a file of commands or a command itself, e.g. qbatch ./process might be running commands in the file process or running the script process.
What about a "subcommand" to disambiguate:
Usage:
    qbatch [options] <command_file>
    qbatch [options] cmd <command> [command_opts...]

e.g. qbatch ./process vs qbatch cmd ./process. With options: qbatch --ppj 8 ./process vs qbatch --ppj 8 -- cmd ./process -p
Alternatively, we could use the double dash (--) separator as indicating that the user is submitting a command to run, not a file. eg. qbatch ./process vs ./qbatch -- ./process. Two issues with that: argparse doesn't naturally handle this case so we'd have to do our own gymnastics, and it fails with command files that start with a dash, e.g. qbatch -- -process (but I think we can all agree we hate people that would try to do that).

I'm all for using the -- version as this is common in other unix things.
I'm sure I've used this before in argparse but couldn't find it so resorted
to the internet (which is likely what I did the first time too).  See the
first answer here:
http://stackoverflow.com/questions/25872515/python-argparse-treat-arguments-in-different-ways
On 29 May 2016 at 21:43, Jon Pipitone<EMAIL_ADDRESS>wrote:

There's an ambiguity here: with a single positional argument it's unclear
whether the argument is a file of commands or a command itself, e.g. qbatch
./process might be running commands in the file process or running the
script process.
What about a "subcommand" to disambiguate:
Usage:
qbatch [options] <command_file>
qbatch [options] cmd  [command_opts...]
e.g. qbatch ./process vs qbatch cmd ./process. With options: qbatch --ppj
8 ./process vs qbatch --ppj 8 -- cmd ./process -p
Alternatively, we could use the double dash (--) separator as indicating
that the user is submitting a command to run, not a file. eg. qbatch
./process vs ./qbatch -- ./process. Two issues with that: argparse
doesn't naturally handle this case so we'd have to do our own gymnastics,
and it fails with command files that start with a dash, e.g. qbatch --
-process (but I think we can all agree we hate people that would try to
do that).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pipitone/qbatch/issues/35#issuecomment-222356295, or mute
the thread
https://github.com/notifications/unsubscribe/AATwit1D0iol4UHE0AaQm6iC8ORNWPduks5qGXvJgaJpZM4HqaFT
.

Another very interesting option is docopt, I've used it a few times when
creating quick hacks, it's eerily similar to GetOpt::Tabular, but even
better.
http://docopt.org/
On 30 May 2016 at 06:25, Andrew Janke<EMAIL_ADDRESS>wrote:

I'm all for using the -- version as this is common in other unix things.
I'm sure I've used this before in argparse but couldn't find it so
resorted to the internet (which is likely what I did the first time too).
See the first answer here:
http://stackoverflow.com/questions/25872515/python-argparse-treat-arguments-in-different-ways
On 29 May 2016 at 21:43, Jon Pipitone<EMAIL_ADDRESS>wrote:

There's an ambiguity here: with a single positional argument it's unclear
whether the argument is a file of commands or a command itself, e.g. qbatch
./process might be running commands in the file process or running the
script process.
What about a "subcommand" to disambiguate:
Usage:
qbatch [options] <command_file>
qbatch [options] cmd  [command_opts...]
e.g. qbatch ./process vs qbatch cmd ./process. With options: qbatch
--ppj 8 ./process vs qbatch --ppj 8 -- cmd ./process -p
Alternatively, we could use the double dash (--) separator as indicating
that the user is submitting a command to run, not a file. eg. qbatch
./process vs ./qbatch -- ./process. Two issues with that: argparse
doesn't naturally handle this case so we'd have to do our own gymnastics,
and it fails with command files that start with a dash, e.g. qbatch --
-process (but I think we can all agree we hate people that would try to
do that).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pipitone/qbatch/issues/35#issuecomment-222356295,
or mute the thread
https://github.com/notifications/unsubscribe/AATwit1D0iol4UHE0AaQm6iC8ORNWPduks5qGXvJgaJpZM4HqaFT
.

Absolutely love docopt. I didn't go with it because I wanted the flexibility of argparse and to avoid the added dependency. Neither are very strong reasons but docopt wouldn't help us here I don't think ; we'd still need to handle parsing ambiguities ourselves.
In any case a +1 for --. I'll try it out and we can see what it's like in practice.

On May 29, 2016, at 4:31 PM, Andrew Janke<EMAIL_ADDRESS>wrote:
Another very interesting option is docopt, I've used it a few times when
creating quick hacks, it's eerily similar to GetOpt::Tabular, but even
better.
http://docopt.org/
On 30 May 2016 at 06:25, Andrew Janke<EMAIL_ADDRESS>wrote:

I'm all for using the -- version as this is common in other unix things.
I'm sure I've used this before in argparse but couldn't find it so
resorted to the internet (which is likely what I did the first time too).
See the first answer here:
http://stackoverflow.com/questions/25872515/python-argparse-treat-arguments-in-different-ways
On 29 May 2016 at 21:43, Jon Pipitone<EMAIL_ADDRESS>wrote:

There's an ambiguity here: with a single positional argument it's unclear
whether the argument is a file of commands or a command itself, e.g. qbatch
./process might be running commands in the file process or running the
script process.
What about a "subcommand" to disambiguate:
Usage:
qbatch [options] <command_file>
qbatch [options] cmd  [command_opts...]
e.g. qbatch ./process vs qbatch cmd ./process. With options: qbatch
--ppj 8 ./process vs qbatch --ppj 8 -- cmd ./process -p
Alternatively, we could use the double dash (--) separator as indicating
that the user is submitting a command to run, not a file. eg. qbatch
./process vs ./qbatch -- ./process. Two issues with that: argparse
doesn't naturally handle this case so we'd have to do our own gymnastics,
and it fails with command files that start with a dash, e.g. qbatch --
-process (but I think we can all agree we hate people that would try to
do that).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/pipitone/qbatch/issues/35#issuecomment-222356295,
or mute the thread
https://github.com/notifications/unsubscribe/AATwit1D0iol4UHE0AaQm6iC8ORNWPduks5qGXvJgaJpZM4HqaFT
.

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

I've got something cooking over in https://github.com/pipitone/qbatch/tree/fix_single_command_submit
It works, but:

I've disabled the check for command_file existence (need to call which)
The usage/help doesn't reflect the change (not sure exactly how to do this nicely)
Preserving quotations doesn't work yet (which is one reason the test fails)

In the meantime, you can use this bash wrapper:
#!/bin/bash
# Submits a single command to qbatch (like sge_batch)
#
# Usage:
#     qbatchsub.sh [qbatch options] -- command [options]
#
# For example,
#   qbatchsub -o '-l walltime=30:00' --ppj 8 -- ./process.sh "hello world"
#
# This submits the command "./process.sh 'hello world'"

qbatch_args=()
cmd=()
dashdash_unseen="no"

while [[ $# > 0 ]]; do
    if [[ $1 = "--" ]]; then
        dashdash_unseen="yes"
    elif [[ ${dashdash_unseen} = "no" ]]; then
        qbatch_args+=("$1")
    else
        cmd+=( $(printf '%q' "$1") )
    fi
    shift;
done

echo "${cmd[@]}" | qbatch "${qbatch_args[@]}" -

Hey @andrewjanke see implementation in #157

I like!
More reasons to dump my old perl script.
On Thu, 26 Apr 2018 at 11:52, Gabriel A. Devenyi<EMAIL_ADDRESS>wrote:

Hey @andrewjanke https://github.com/andrewjanke see implementation in
#157 https://github.com/pipitone/qbatch/pull/157
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pipitone/qbatch/issues/35#issuecomment-384487455, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AATwivif27gPhPI4Iln1NLPOS1Rryc3Hks5tsShugaJpZM4HqaFT
.

Great. can you do a quick look over and see if there's any other show stopping features you need? If so, open or poke some issues

Fixed in #164


tinc: 1.0.28 -> 1.0.29

Motivation for this change
package update
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Here is a summary of the changes:

Fix UDP communication with peers with link-local IPv6 addresses.

Ensure compatibility with OpenSSL 1.1.0.

Ensure autoreconf can be run without requiring autoconf-archive.

Log warnings about dropped packets only at debug level 5.


Add biometry type detection to local_auth plugin

Should resolve Issue https://github.com/flutter/flutter/issues/22727
Two new functions were added to the local_auth plugin

bool canCheckBiometrics > if device is able to do local auth (with biometrics)
List<BiometricType> getAvailableBiometrics > list of enrolled biometrics

Enum BiometricType:

face
fingerprint
iris (not yet implemented)

@mehmetf here's the fix according to your mail. Thanks!

I signed it!

Thank you! This looks good now. One last thing:
Please update changelog.md and pubspec.yaml with a new version: 0.3.0 since there's a new API.

Done!


Another race condition, causing poison

This one seems a little more subtle than #2, but under certain conditions it seem a race condition causes None.unwrap():
thread '<unnamed>' panicked at 'called `Option::unwrap()` on a `None` value', ~/.cargo/registry/src/github.com-1ecc6299db9ec823/tracing-indicatif-0.3.2/src/pb_manager.rs:140:69

Followed by any subsequent use getting a poison error:
thread '<unnamed>' panicked at 'Mutex poisoned: PoisonError { .. }', ~/.cargo/registry/src/github.com-1ecc6299db9ec823/tracing-subscriber-0.3.17/src/registry/sharded.rs:433:54
thread '<unnamed>' panicked at 'called `Result::unwrap()` on an `Err` value: PoisonError { .. }', ~/.cargo/registry/src/github.com-1ecc6299db9ec823/tracing-indicatif-0.3.2/src/lib.rs:546:22

The repro is almost the same as in #2, but with the info! statements removed. Presumably they either cause synchronization via get_stderr_writer, or simply affect the timing. It's not guaranteed to happen; for me it happens about every other time when running this program in debug build.
use tracing_indicatif::IndicatifLayer;
use tracing_subscriber::layer::SubscriberExt;
use tracing_subscriber::util::SubscriberInitExt;

fn main() {
	let indicatif_layer = IndicatifLayer::new();
	tracing_subscriber::registry()
		.with(tracing_subscriber::fmt::layer().with_writer(indicatif_layer.get_stderr_writer()))
		.with(indicatif_layer)
		.init();

	let handles = (0..256)
		.map(|_| {
			std::thread::spawn(move || {
				let _span = tracing::info_span!("ch").entered();
			})
		})
		.collect::<Vec<_>>();
	handles.into_iter().for_each(|i| i.join().unwrap());
}

Oh wow, that is super subtle. Looks like what happened is I assume the span is removed from the tracing registry as soon as on_close is finished... but it's possible there are other layers (ergo other on_close calls) tracing has to iterate through first before it can remove the span from the registry. So there's a brief period where we have closed out the progress bar (from IndicatifLayer's on_close call) but the span still exists in the registry, and I incorrectly assume that "if span exists in registry, it must still have a progress bar."
the fix here is to check whether we have a progress bar when we grab a span off the tracing registry. I've run this repro a few thousands times now with the fix and have not encountered a panic, so feel very confident I have fixed this race condition as well.
Thanks again for finding and reporting this! Will put out another release shortly with this fix. :)


Anti-aliasing for Firefox

awesome work!
just one problem, we can see apparently  aliasing when open the demo in Firefox.

especially this one

It was as simple as adding a outline: 1px solid transparent;


eth_call:execution reverted

When I execute eth_call, the node reports an error
curl --location 'http://<IP_ADDRESS>:8545' \ --header 'Content-Type: application/json' \ --data '{ 	"jsonrpc":"2.0", 	"method":"eth_call", 	"params":[         {             "to":"0x4401e30b92c0a9deab9943880586d478d5d15c89",             "data":"0xc913d6d5000000000000000000000000d0b53d9277642d899df5c87a3966a349a798f2240000000000000000000000000000000000000000000000000000000000000001"         },         "latest"], 	"id":1 }'
{
    "jsonrpc": "2.0",
    "id": "1",
    "error": {
        "code": -32000,
        "message": "execution reverted"
    }
}

start base with conifg:
geth --datadir=/opt/rockx/base --verbosity=3 --http --http.corsdomain=* --http.vhosts=* --http.addr=<IP_ADDRESS> --http.port=8545 --http.api=web3,debug,eth,net,engine,txpool,personal --authrpc.addr=<IP_ADDRESS> --authrpc.port=8551 --authrpc.vhosts=* --authrpc.jwtsecret=/opt/rockx/base/secrets/engine-auth-jwt --ws --ws.addr=<IP_ADDRESS> --ws.port=8546 --ws.origins=* --ws.api=debug,eth,net,engine,txpool --syncmode=full --gcmode=full --maxpeers=100 --rollup.sequencerhttp=https://mainnet-sequencer.base.org --rollup.halt=major --op-network=base-mainnet --port=30303  --rpc.gascap=150000000 --txpool.globalqueue=5000
I use a public node https://base-rpc.publicnode.com/  that can return data
What is the reason for this? Thank you.

Is someone here? Is there anyone officially present?

Contact the Support page to resolve your error.
Note: you can also initiate a chat with the live agent on the chat button to get more information about your request via Live Chat
@zhy827827
Support.

I don't think the issue is with your node setup since both your local node and the public node (base-rpc.publicnode.com) are giving the same "execution reverted" error. This means the contract itself is rejecting the call.
Looking at your transaction data:
Contract: 0x4401e30b92c0a9deab9943880586d478d5d15c89
Function: 0xc913d6d5
Params: An address (d0b53d...) and what looks like a boolean/uint (1)
The contract is probably rejecting your call because either the input parameters don't meet the contract's requirements or function's conditions aren't being met.
My guess would be there's some business logic causing it to revert.


BinaryRequestEntity. Implements #104

This adds a BinaryRequestEntity which takes a Single<byte[]>. It can be used to compose HttpRequestEntities for complex types which can be converted to an array of bytes.
This also adds a DelegatingRequestEntity which can serve as the abstract base of such a delegating request entity.

Codecov Report

Merging #105 into master will increase coverage by 0.3%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##             master     #105     +/-   ##
===========================================
+ Coverage     66.34%   66.64%   +0.3%
- Complexity      469      477      +8
===========================================
  Files           142      144      +2
  Lines          1634     1649     +15
  Branches        112      112
===========================================
+ Hits           1084     1099     +15
  Misses          497      497
  Partials         53       53

Impacted Files
Coverage Δ
Complexity Δ

...tpessentials/entities/DelegatingRequestEntity.java
100% <100%> (ø)
4 <4> (?)

...s/httpessentials/entities/BinaryRequestEntity.java
100% <100%> (ø)
4 <4> (?)

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 92decfa...5d9b805. Read the comment docs.


ordered-imports rule doesn't sort in the same order as Organize Imports in TypeScript

Bug Report

TSLint version: master
TypeScript version: 2.9
Running TSLint via: CLI

See https://github.com/Microsoft/TypeScript/issues/25114
TypeScript code being linted
import { foo, _bar } from 'baz';

with tslint.json configuration:
{
  "ordered-imports": true,
}

Actual behaviour
It sorts it to import { _bar, foo }, which is different to how TypeScript organises it.
Expected behaviour
No lint error.
The difference seems to be that TypeScript is normalising strings using toUpperCase where as tslint uses toLowerCase.

Is there a reason this isn't being picked up? This is a feature I (and I'm guessing many others) have been waiting for for a long time.

@Timebutt it's marked as Status: Accepting PRs which means anybody is welcome to send a PR. Including you! 😉

I know and I'm looking to contribute, was just wondering if there is a specific reason why this wouldn't be fixed? Implementing this will be a breaking change, forcing everybody to change code and this might not be desired. If there is nothing preventing us from fixing this, I will try my hand at implementing this for sure!

Gotcha, great!

just wondering if there might be a specific reason why this wouldn't be fixed
breaking change

Good call - adding the missing label. We can review a PR and hold off merging it until the next major version, which should be soon.

We have a PR for it, it's #4064. I'd love to see this merged although personally I just forked months ago.

So we actually have the fix, and it was just waiting for a next major version? In that case, it seems like the timing is in our favour, as a new version will be around soon right @JoshuaKGoldberg?

Correct! 🙌

Removing the Type: Breaking Change label per #4811. Now accepting PRs!

Is the fix expected to ship in the next release  ?


[Systemml 2085] Initial version of local backend for paramserv builtin function

Hi @mboehm7 ,
Here is the PR for the initial version of local backend. To summarize, I implemented the "BSP" as well as "BATCH" update frequency which you can see in the new added test. In general, the idea is to launch a local ps which maintains a map. And the exchange of intermediates is done by looking up the corresponding key. On one hand, the local workers will work out and push the gradients to ps and then wait for a pending new global parameter pushed by the aggregation service. On the other hand, the aggregation service will wait for the pending gradients and then update and broadcast the updated model. "Broadcast" here means to deep copy the model and push them with each worker's "global parameter" key. So each worker will not impact the other's global parameter.
Thanks for the review,
Guobao

Can an Admin verify this patch?

Thanks @mboehm7 for the review. I will go over your points and make another PR for the aggregation service and parameter server.


Unable to set HTTP port in dropwizard 0.9.x

This page:
http://www.dropwizard.io/0.9.1/docs/manual/configuration.html#simple
suggest that this should work in the application yml config file:
  connector:
    type: http
    port: 8080

I'm finding it errors though.
Exception in thread "main" java.lang.NoSuchMethodError: com.fasterxml.jackson.core.JsonParser.hasToken(Lcom/fasterxml/jackson/core/JsonToken;)Z
	at com.fasterxml.jackson.module.afterburner.deser.SettableIntMethodProperty.deserializeAndSet(SettableIntMethodProperty.java:56)

Seems to particularly be the port number causing the issue. Works in 0.8.5.

@richmidwinter Check your Jackson dependencies for incompatible versions (e. g. by running mvn dependency:tree).

Good call, thanks!


[docs] Document ref forwarding (requirements)

Will close #14415
TODO:

[ ] ClickAwayListener child ref (and derived components)
[ ] ref forwarding in "API Design Approach"
[ ] https://next.material-ui.com/getting-started/faq/#how-can-i-access-the-dom-element

Should we add a soft deprecation for RootRef?


SQLite binaries should be upgraded to latest patched sqlite 3.32.1, due critical and high vulnerabilities

Hi Mapbox team,
Recently our company internal docker image scanner reported a bunch of critical and high vulnerabilities related to the sqlite binaries version 3.31.1 which is used by the sqlite3 npm package version 4.2.0.
The list of vulnerabilities is:

https://nvd.nist.gov/vuln/detail/CVE-2020-11656 - CRITICAL
https://nvd.nist.gov/vuln/detail/CVE-2020-13630 - CRITICAL
https://nvd.nist.gov/vuln/detail/CVE-2020-13631 - HIGH
https://nvd.nist.gov/vuln/detail/CVE-2020-13632 - HIGH
https://nvd.nist.gov/vuln/detail/CVE-2020-13434 - HIGH
https://nvd.nist.gov/vuln/detail/CVE-2020-13435 - HIGH
https://nvd.nist.gov/vuln/detail/CVE-2020-11655 - HIGH
https://nvd.nist.gov/vuln/detail/CVE-2020-9327 - HIGH

Is there any planned activity to perform the upgrade of the latest sqlite distribution version 3.32.1 from 2020-05-25?
Looking forward your soon feedback.
Thank you in advance.

Hey, I also have the same issue that I really need to get rid of these vulnerabilities. Is there any plan when to upgrade the sqlite version to some newer and less vulnerable one?

One more PR #1353 that points to the latest sqlite distribution 3.32.3

Updating to the latest 3.32 versions would also mean that by default the variable limit increases from 999 to 32766 which would be amazing.
https://www.sqlite.org/releaselog/3_32_0.html

Hi @ErisDS ,
The PR https://github.com/mapbox/node-sqlite3/pull/1351 was already merged. It contains the upgrade to SQLite 3.32.3.
The only missing part is to make the release 5.0.1. Hope that will not last ages.

This release was published so I'm going to close the issue 🙂


fix(container): enhance Capability enum with ALL cap (#4064)

Backport
This will backport the following commits from k8s-29/main to k8s-28/main:

fix(container): enhance Capability enum with ALL cap (#4064)

Questions ?
Please refer to the Backport tool documentation

When https://github.com/cdk8s-team/cdk8s-plus/pull/4064 was created, we forgot to label it with backport-to-k8s-28/main and backport-to-k8s-27/main. Since then, cdk8s-plus-30 has been released, which means this PR exists both on cdk8s-plus-29 and cdk8s-plus-30, so the only thing missing is cdk8s-plus-28.
Also created this to make sure we don't forget to label PRs anymore.

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 4274

Questions ?
Please refer to the Backport tool documentation


[BUG] Demonstration can't find steps

Is there an existing issue for this?

[X] I have searched the existing issues and none matched.

Operating System
Windows10 Pro
CPU
i5-7500 3.4GHz
GPU
GeForce GTX 1060 6GB
Storage
SSD
Game Version
4.18.1
Game Mode
I was using the editor!
Theme
Themes inheriting from fallback
metrics.ini
[Global]
FallbackTheme=_fallback

[ScreenInit]
NextScreen="ScreenDemonstration"

[ScreenDemonstration]
NextScreen="ScreenInit"
TimerSeconds=5
AllowStyleTypes="OnePlayerOneSide"

Describe the problem
Even when a song is present, ScreenDemonstration gives "No matching steps found." (ja: 条件に適合する譜面が見つかりませんでした。) and the demo is skipped
I have confirmed that this phenomenon occurs in both 4.18.1 and 4.19 (test version)
Describe what should happen
If the game mode is Dance, a 4-panel steps is selected
Relevant Log output
ProjectOutfox.Crash.2023-01-29--21.24.13.log
ProjectOutfox.MainLog.2023-01-29--21.24.13.log
ProjectOutfox-sample.ThemeLua.2023-01-29--21.24.14.log

Probably related with #625. The demonstration screen would present this situation of non-available steps.

Fixed in 042


test: dart c at_chops interoperability tests

- What I did

Used dart ffi to import the c version of atchops encrypt/decrypt functions
tested the aesctr encrypt/decrypt in c against at_chops in dart

N.B.:

I used static aes key / plaintext / iv, but I at least made sure the iv was non-zero
The GH action as is fails to build the dll, but it is set to run when triggered manually

Not ideal, but at least I was able to test locally, which is good enough for now
We can fix the GH action later, included it in the PR so that anyone can pick up the work

- How I did it

Encrypt in C then decrypt in Dart
Encrypt in Dart then decrypt in C

- How to verify it
- Description for the changelog
test: dart c at_chops interoperability tests

Does this PR close #45 ?

Does this PR close #45 ?

Yes, or at least lowers the priority of it greatly


Is support for the LILYGO®TTGO T-Echo and similar nRF52 boards possible?

Hi, thanks for the work that you've put into this firmware. It's great.
I'm interested in developing a solar powered digipeater, and the ESP32 based boards are quite power hungry in comparison to the lora boards with lower powered microprocessors.
Many thanks once again,
Stuart MM7SHX

Hi!
Do you have a T-echo?
Would love to start porting this firmware into more boards. But for now I don't have any t-echo available for this.

I do yes. I'd be happy to test any firmware you'd like on it. I'd even lend you it but it might be a bit far to post it to you though. :)

Absolutely! Thanks so much for your work. I'm happy to help with testing whenever you're ready. All the best.

Hello Ricardo
I would also love if we could use in future the T-Echo. One question which came up here. The best woudl be if you have one T-Echo at your premsies for testing. Can you order one via Amazon or Lillygo or any other online shop right now.
May be the easiest thing would be that we sponsor you one T-Echo in transfering moeney to you via PayPal  and then you have a chance to get it shipped directly to you. That would be much cheaper than shipping it form UK or Germany.
Would that something which would help you?
Just an idea.
vy 73 de Michael DB2GM

I second this!
I also have a T-Echo and would like to run your software on it.  Happy to help test!

Hopefully it should be fairly straightforward to support the wisblock too if the t-echo works. Happy to help with any testing!

Hello sdhuk
Ricardo and I looked last week a bit inter Wisblock modules.
The only restriction we found that the WiFi capability is missing which would be a serious problem in using it as an iGate.
Do you have any experience with these Wisblock modules.
vy 73 de Michael DB2GM

I think there's an ethernet module available for the wizblocks. My main interest is in using one of these boards as a solar digipeater though.

T-Echo has been ordered ;) (thanks for the  sponsorship!)
I'will close this and continue on the tracker side as soon as it arrives !


Upgraded main aspnet core project to 2.0

Upgraded the Mvc.JQuery.DataTables.AspNetCore and Mvc.JQuery.DataTables.AspNetCore.Example with their dependencies to asp.net core 2.0, also fixed the issues that arose through this upgrade.

Failed build, it might be due to this: https://stackoverflow.com/questions/45569378/upgrading-to-net-core-2-0-packagetargetfallback-and-assettargetfallback-cannot

My apologies for the late reply and thank you for your advice. I should have fixed all the build errors now.

Are all those js/css assets not required for the example project?

Great work BTW.


mimalloc: 2.0.2 -> 2.0.5

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[x] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

On macos 10.15:
[1/40] Building C object CMakeFiles/mimalloc.dir/src/random.c.o
FAILED: CMakeFiles/mimalloc.dir/src/random.c.o
/nix/store/18i795dcmzx2jlc7560nf65qybp0y41p-clang-wrapper-11.1.0/bin/clang -DMI_MALLOC_OVERRIDE -DMI_OSX_INTERPOSE=1 -DMI_OSX_ZONE=1 -DMI_SHARED_LIB -DMI_SHARED_LIB_EXPORT -Dmimalloc_EXPORTS -I/tmp/nix-build-mimalloc-2.0.5.drv-0/source/include -O3 -DNDEBUG -fPIC -Wall -Wextra -Wno-unknown-pragmas -fvisibility=hidden -Wstrict-prototypes -Wpedantic -Wno-static-in-inline -ftls-model=initial-exec -fno-builtin-malloc -std=gnu11 -MD -MT CMakeFiles/mimalloc.dir/src/random.c.o -MF CMakeFiles/mimalloc.dir/src/random.c.o.d -o CMakeFiles/mimalloc.dir/src/random.c.o -c /tmp/nix-build-mimalloc-2.0.5.drv-0/source/src/random.c
In file included from /tmp/nix-build-mimalloc-2.0.5.drv-0/source/src/random.c:198:
/nix/store/c5jrszdq2hy3hj9rpyx3hk9gba60wd1d-Libsystem-1238.60.2/include/CommonCrypto/CommonRandom.h:35:9: error: unknown type name 'CCCryptorStatus'
typedef CCCryptorStatus CCRNGStatus;
        ^
1 error generated.

The above problem is resolved by
    substituteInPlace src/random.c \
      --replace '#include <CommonCrypto/CommonRandom.h>' \
        $'#include <CommonCrypto/CommonCryptor.h>\n#include <CommonCrypto/CommonRandom.h>'
  '';

But then we get
/nix/store/18i795dcmzx2jlc7560nf65qybp0y41p-clang-wrapper-11.1.0/bin/clang -DMI_MALLOC_OVERRIDE -DMI_OSX_INTERPOSE=1 -DMI_OSX_ZONE=1 -DMI_SHARED_LIB -DMI_SHARED_LIB_EXPORT -Dmimalloc_EXPORTS -I/tmp/nix-build-mimalloc-2.0.5.drv-2/source/include -std=c11 -O3 -DNDEBUG -fPIC -Wall -Wextra -Wno-unknown-pragmas -fvisibility=hidden -Wstrict-prototypes -Wpedantic -Wno-static-in-inline -ftls-model=initial-exec -fno-builtin-malloc -std=gnu11 -MD -MT CMakeFiles/mimalloc.dir/src/alloc.c.o -MF CMakeFiles/mimalloc.dir/src/alloc.c.o.d -o CMakeFiles/mimalloc.dir/src/alloc.c.o -c /tmp/nix-build-mimalloc-2.0.5.drv-2/source/src/alloc.c
In file included from /tmp/nix-build-mimalloc-2.0.5.drv-2/source/src/alloc.c:19:
/tmp/nix-build-mimalloc-2.0.5.drv-2/source/src/alloc-override.c:80:21: error: use of undeclared identifier 'aligned_alloc'; did you mean 'mi_aligned_alloc'?
    MI_INTERPOSE_MI(aligned_alloc),
                    ^~~~~~~~~~~~~
                    mi_aligned_alloc

Aha https://github.com/microsoft/mimalloc/pull/550

  patches = [
    (fetchpatch {
      name = "older-macos-fixes.patch";
      url = "https://github.com/microsoft/mimalloc/commit/40e0507a5959ee218f308d33aec212c3ebeef3bb.patch";
      sha256 = "15qx2a3axhhwbfzxdis98b8j14y9cfgca0i484aj2pjpqnm0pb8c";
    })
  ];

fixes it for me, macos 10.15.

Thank you @risicle
Just updated the PR with your suggestion, really good review btw, thank you

It's possible to enable the tests too with
  doCheck = true;
  preCheck = let
    ldLibraryPathEnv = if stdenv.isDarwin then "DYLD_LIBRARY_PATH" else "LD_LIBRARY_PATH";
  in ''
    export ${ldLibraryPathEnv}="$(pwd)/build:''${${ldLibraryPathEnv}}"
  '';

Thank you @risicle
Just updated the PR, works like a charm on *-linux

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/750


remove install dependencies so they don't build

Address issue #101
Signed-off-by: Mike Brown<EMAIL_ADDRESS>

fine, @mrunalp ?

Yeah :+1:


NixOS: can't get machine FQDN when resolved is enabled

Describe the bug
When services.resolved.enable = true is used (either manually or with networking.useNetworkd = true), I can no longer get the FQDN of my machine with hostname -f.
Steps To Reproduce
Steps to reproduce the behavior:

Checkout f09a770d9c938fe2986fead7d96af5743eefe516 (current master commit)
Put services.resolved.enable = true in nixos/tests/hostname.nix
Run nix-build ./nixos/tests/hostname.nix -A explicitDomain
The test fails:

...
ahost: must succeed: hostname --fqdn
(0.01 seconds)
error:
Traceback (most recent call last):
  File "/nix/store/mb9lhv3n6h20ybbpr2j8xdhbv5jgijwb-nixos-test-driver/bin/.nixos-test-driver-wrapped", line 943, in run_tests
    exec(tests, globals())
  File "<string>", line 1, in <module>
  File "<string>", line 11, in <module>
AssertionError
cleaning up
killing ahost (pid 10)
(0.00 seconds)

Expected behavior
The test should succeed and hostname -f should return the FQDN when networking.domain is set.
Additional context
With the above procedure I could bisect the failure to #130503.
After #130503 the noExplicitDomain test in nixos/tests/hostname.nix also fails with the following error:
...
(0.06 seconds)
ahost: must succeed: getent hosts <IP_ADDRESS> | awk '{print $2}'
ahost: output:
error:
Traceback (most recent call last):
  File "/nix/store/mb9lhv3n6h20ybbpr2j8xdhbv5jgijwb-nixos-test-driver/bin/.nixos-test-driver-wrapped", line 943, in run_tests
    exec(tests, globals())
  File "<string>", line 1, in <module>
  File "<string>", line 22, in <module>
  File "/nix/store/mb9lhv3n6h20ybbpr2j8xdhbv5jgijwb-nixos-test-driver/bin/.nixos-test-driver-wrapped", line 483, in succeed
    raise Exception(
Exception: command `getent hosts <IP_ADDRESS> | awk '{print $2}'` failed (exit code 2)
cleaning up
killing ahost (pid 10)
(0.00 seconds)

Notify maintainers
@flokli
Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 5.13.0, NixOS, 21.11 (Porcupine)`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.4pre20210712_099df07`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

That's interesting /etc/nsswitch.conf should contain:
without resolved:
hosts:     mymachines files myhostname dns

with resolved:
hosts:     mymachines resolve [!UNAVAIL=return] files myhostname dns

This suggests something inside the resolve module resolves things differently.
What does hostname --fqdn do under the hood?

This suggests something inside the resolve module resolves things differently.

Yes, systemd doesn't know about the domain name, only the hostname. IIRC it should work with this:
hosts:     mymachines files resolve [!UNAVAIL=return] myhostname dns

What does hostname --fqdn do under the hood?

It was implemented like this when I last looked at it: https://gist.github.com/primeos/8f7f8e1e95518076ef38924125a2f921

The report doesn't mention what hostname --fqdn actually prints for the author, so I'm not sure if it's the same issue, but on my system, nixpkgs-unstable with networking.hostName and networking.domain set, hostname --fqdn shows only short hostname (without domain).
[japhy@bmo:~] % nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.0.17, NixOS, 23.05 (Stoat), 23.05.20230106.b3818a4`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.12.0`
 - nixpkgs: `/etc/nixpkgs/channels/nixpkgs`

I was attempting to fix nixos.tests.networking.hostname.explicitDomain for ZHF and saw that seeminly this issue was fixed at some point but broke again in this build: https://hydra.nixos.org/build/208026588 on Feb 3rd. I bisected the changes and it seems it broke with fbfe290 introducing nsncd (assuming I bisected correctly).
I'm sort of piecing things together, from man hostname:

The FQDN is the canonical name returned by gethostbyname2(2) when resolving the result of the gethostname(2) name. The DNS domain name  is  the  part after the first dot.

I browsed through the code and noticed gethostbyname and some others are not currently implemented, but from twosigma/nsncd#49 it seems @flokli you're working on that in nsncd. So perhaps this gets resolved when that does? I didn't see any mention of gethostbyname2 in the project but maybe there is something equivalent that will resolve this issue/fix that test.

Related:
https://github.com/NixOS/nixpkgs/issues/196934
https://github.com/nix-community/nsncd/issues/4

I still have this issue on my system (or a closely related one).
The exact conditions to trigger this issue seem to be:

use systemd-resolved and nsncd
have networking.enableIPv6 = true

hostname --short returns my actual (short) hostname, hostname --fqdn always returns localhost for me.
If I stop systemd-resolved, stop nscd or remove the line ::1 localhost from /etc/hosts, the correct FQDN is returned.

relevant systemd-resolved logs for the error case

varlink-28: New incoming message: {"method":"io.systemd.Resolve.ResolveHostname","parameters":{"name":"$hostname","family":10,"flags":0}}
Looking up RR for $hostname IN AAAA.
Following CNAME/DNAME $hostname → localhost.
varlink-28: Sending message: {"parameters":{"addresses":[{"family":10,"address":[0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,1]}],"name":"localhost","flags":786945}}

relevant systemd-resolved logs when IPv6 is disabled

varlink-28: New incoming message: {"method":"io.systemd.Resolve.ResolveHostname","parameters":{"name":"$hostname","family":10,"flags":0}}
Looking up RR for $hostname IN AAAA.
varlink-28: Sending message: {"error":"io.systemd.Resolve.NoSuchResourceRecord","parameters":{}}
varlink-28: New incoming message: {"method":"io.systemd.Resolve.ResolveHostname","parameters":{"name":"$hostnamefamily":2,"flags":0}}
Looking up RR for $hostname IN A.
Following CNAME/DNAME $hostname → $fqdn.
varlink-28: Sending message: {"parameters":{"addresses":[{"family":2,"address":[127,0,0,2]}],"name":"$fqdn,"flags":786945}}

When the nscd service is stopped, no DNS query is logged by systemd-resolved. This looks like nsncd first tries to resolve the short hostname over IPv6 only and systemd-resolved rewrites this to localhost because all three entries for localhost, the short hostname and the FQDN are mapped to the same IPv6 address ::1 in /etc/hosts.

 Did you double-check that https://github.com/picnoir/nixpkgs/commit/364a38956d05b52e67bf3a3bcc9640368786bae1 is in your pin?

I'm on 8efd5d1e283604f75a808a20e6cde0ef313d07d4 but with nsncd overridden from 364a38956d05b52e67bf3a3bcc9640368786bae1.

Gah. This will never end.
Do we have a VM test for this?
I can't check it out rn. Re-opening the issue in the meantime.

cc @Mic92 for https://github.com/NixOS/nixpkgs/issues/132646#issuecomment-1782594859
Maybe you have more context about this name resolution since you added this ::1 line in the hosts file.
@999eagle, could you try the same test with services.nscd.enableNscd = false; to see if we hit the same behaviour with Nscd. It'd be handy to see if this is Nsncd related or not.

I've tried again with nscd instead of nsncd now and it shows the exact same issue with the same logs in systemd-resolved. The "default" nscd apparently also tries to resolve the FQDN using IPv6 first. systemd-resolved still resolves the short hostname to ::1 with the name localhost as that's the first name matching ::1 in /etc/hosts.
Manually changing /etc/hosts to contain the line ::1 $fqdn $hostname localhost makes systemd-resolved correctly return the FQDN. The discussion in #119236 which was already linked here before seems to be very relevant to this.

Do we have a VM test for this?

The reproduce steps from https://github.com/NixOS/nixpkgs/issues/132646#issue-960221270 are sufficient to trigger the bug.
The test still fails when services.resolved.enable = true; is added. Adding services.nscd.enableNsncd = false; also does not fix the issue (tested on master c05811cfed793c83e1b2d431384f13d64ffdfc13).

On 23.11 with
networking.hostName = "nixos";
networking.domain = "lan";
systemd.network.enable = true;

I get:
$ hostname
nixos

$ hostname -f
localhost

Fedora 39 has files first.  more specifically:
hosts:      files myhostname resolve [!UNAVAIL=return] dns

RedHat is a large contributor to systemd, uses it in their distribution and recommends it
I made files first and hostname -f returns nixos.lan as expected.  I also removed [!UNAVAIL=return] as it caused my pings to shortnames of my resolved.domains to time out and falsely claim they didn't exist.

Small, note if you end up here. There's a known regression ATM. Temporarily reverting https://github.com/NixOS/nixpkgs/pull/362132 should fix the issue up until we find a proper fix.


docs: update readme

:tada: This PR is included in version 0.18.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Results are very poor using the API

The results using the website (https://azure.microsoft.com/en-us/services/cognitive-services/computer-vision/#text) are very good. But when I use the API, it's very poor. How would you explain the difference in the results? I used the exact code from this website and even used images from the website to test (Like the green closed sign).
i use v2.0 and both westcentralus and westeurope
Does the website do some preprocessing? like rotating the text?

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

ID: 9d6a5f5a-4f15-366c-891a-5c953b4a4643
Version Independent ID: 3090f05f-8557-3296-fda3-3cd28920556b
Content: Computer Vision API C# quickstart OCR - Microsoft Cognitive Services
Content Source: articles/cognitive-services/Computer-vision/QuickStarts/CSharp-print-text.md
Service: cognitive-services
GitHub Login: @noellelacharite
Microsoft Alias: nolachar

@LanderVe Thanks for the feedback! We are currently investigating and will update you shortly.

@LanderVe Hi, thanks for your feedback. Since this is not document issue but a product issue, I posted it in the correct forum. Please keep eyes on it. Thanks again.
We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Intro slider tutorial for new users

Currently  the app does not contain a intro sliders tutorial at its first run and the features in Zulip may be intimidating for few users. To make sure that every user knows all the features of the Zulip-mobile app There should be a tutorial about all the tools the app provides to increase user’s productivity.
And also having an option to access this tutorials again in future.
Guidance to new people on react : We can use this library  for this issue. :)

@zulipbot label "android"

@zulipbot label "enhancement"

This is definitely a feature that should be for both iOS and Android.

@zulipbot label "iOS"

@zulipbot claim

Hello @vihanggodbole, you claimed this issue to work on it, but this issue and any referenced pull requests haven't been updated for a week. Are you still working on this issue?
If so, please update this issue by leaving a comment on this issue to let me know that you're still working on it. Otherwise, I'll automatically remove you from this issue in 3 days.
If you've decided to work on something else, simply comment @zulipbot abandon so that someone else can claim it and continue from where you left off.
Thank you for your valuable contributions to Zulip!

I claimed this issue just yesterday and this issue too was raised just yesterday. I am definitely working on this issue!
Vihang
On 26 Mar 2017, 7:37 AM +0530, Cynthia Lin<EMAIL_ADDRESS>wrote:

Hello @vihanggodbole, you claimed this issue to work on it, but this issue and any referenced pull requests haven't been updated for a week. Are you still working on this issue?
If so, please update this issue by leaving a comment on this issue to let me know that you're still working on it. Otherwise, I'll automatically remove you from this issue in 3 days.
If you've decided to work on something else, simply comment @zulipbot abandon so that someone else can claim it and continue from where you left off.
Thank you for your valuable contributions to Zulip!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Yeah that notice was a zulipbot bug :(

@vihanggodbole Sorry about that, please reclaim the issue by posting @zulipbot claim

Oh alright never mind :)
Are there any specific instructions or graphics that I must include in the intro?
If possible I'd like to discuss it with  you guys on the chat.

@zulipbot claim

@zulipbot claim

@zulipbot label "Android"

@zulipbot label "enhancement"

@synicalsyntax Does this labels are not supported or Is this a bug in zulipbot?

@saketkumar95 Sorry for late reply, but the enhancement label doesn't exist in the repository. See here

Hello @saketkumar95, if this issue is still under consideration and isn't being worked on already then I'd love to take it up. Any instructions or design strategies moving forward? I'm participating in Outreachy and looking forward to an internship with Zulip.

Hi @Chiamaka , Actually I don't think this feature is High priority right now as told by @borisyankov
@borisyankov  Let me know if I can work on this?

Yes, indeed this is low priority.

We will consider some onboarding later, but closing this for now.


Add CloudFront-TLS-1-0-2020 for the new default TLS1.3 security policy

Please note that while we are transitioning from travis-ci to AWS CodeBuild, some tests are run on each platform. Non-AWS contributors will temporarily be unable to see CodeBuild results. We apologize for the inconvenience.
Resolved issues:
resolves #ISSUE-NUMBER1, resolves #ISSUE-NUMBER2, etc.
Description of changes:
Add a new TLS 1.3 security policy that can serve to be the default CloudFront's policy.
Describe s2n’s current behavior and how your code changes that behavior. If there are no issues this pr is resolving, explain why this change is necessary.
Call-outs:
Address any potentially confusing code. Is there code added that needs to be cleaned up later? Is there code that is missing because it’s still in development?
Testing:
How is this change tested (unit tests, fuzz tests, etc.)? Are there any testing steps to be verified by the reviewer?
Unit tests, another manually tested against local s2nd.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Closing this for now to reduce the number of total number of known security policies.


Using the display with a raspberry Pi

I really like your API for the oled displays. Unfortunately I am not able to use it yet as I am using my Johnny Five either with a

ESP8266 (with Etherport-client) or
preferrer a Raspberry Pi (with rapi-io).

Is there any way to figure out the correct address for the display? Would really help me out.

You can see a working example here: https://github.com/ryall/rpi-oled


/sauce command

It'd be nice if we have /sauce command to get image source (fuck pinterest)

Currently a private saucenao wrapper is being worked on, stay tuned for the sauce feature xD

Implemented in 1299f740a19e285c64e314e8d63ce52c344b031a


Excluding node_modules but then what about 6to5 deps?

I don't understand the logic of excluding node_modules from 6to5 compile.
That means ES6-based modules to be compiled beforehand, which means a dep's deps cannot be shared across other deps' deps... This is bad.

Honestly I place 6to5 in the same bag than coffeescript.
I believe that it's polite to compile your modules before hand so that you don't force other people to work with flavors they're not comfortable, specially because es5 is still the middle ground, at least for a while...
You can always use the postinstall hook on npm to compile your module after it has been installed by someone, this way you can always develop in es6 and users will get es5 after they've installed your module.
If you don't exclude the node_modules you'll notice that compiling times will increase a lot, because 6to5 will have to parse every dependency that your application requires, even if they're not in es6.

I realize there may be no good solution but please note your also saying "throw away module sharing and create more kilobytes for end-users to download". This is not a good solution.

Making users compile their entire node_modules folder is extremely slow (there were issues being opened with people wondering why their builds were taking minutes).
The solution for now is the precompile modules. We're looking to make something smarter than that though.

This isn't forced on you at all and you can just change your exclude regex so I'm not sure what the problem is?

The problem is obvious, as much as no obvious solution exists.
This is not like the CoffeeScript problem; CoffeeScript was never an ECMA standard. People will be publishing ES6 modules that leave it up to clients to compile or otherwise simply not use. Koa takes this approach by simply refusing to work on node 0.10.x, unless of course clients decide to do the transpiling themselves.
Thanks for listening.


Problem about how to show the policy being executed in the GridWorld?

Execuse me , can you tell me how to show the policy being executed in the environment like the matlab version (http://www.cs.ox.ac.uk/conferences/LCRL/)?
Your reply is highly appreciated!

Thanks for the comment. I haven't implemented a plotter/animator yet, but it will be included in the next update of the repo!

Thank you very much.

Dear @hychong1997,
The animator is added to the repo. Please let me know if you run into an issue, otherwise I am going to close this as solved.
Cheers!

Dear Hosein Hasanbeig,
Thank you very much!
---Original---
From: "Hosein<EMAIL_ADDRESS>Date: Sun, Sep 27, 2020 20:31 PM
To<EMAIL_ADDRESS>Cc: "hychong1997"<1034227906<EMAIL_ADDRESS>Subject: Re: [grockious/lcrl] Problem about how to show the policy being executed in the GridWorld? (#1)
Dear @hychong1997,
The animator is added to the repo. Please let me know if you run into an issue, otherwise I am going to close this as solved.
Cheers!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Enabling Systemd service in jenkins-1-centos7 image

I have a situation where I need to start some services within this jenkins container to make it work in our project. So i need Systemd enabled in order to do that...
As of now I get the below error when I try to run "systemctl" command within this container:

Failed to get D-Bus connection: Operation not permitted
Which is expected.

Now on my research, I found that if we use the below docker file to create an image and then run a container, we should be able to run systemctl commands:

FROM centos:7
MAINTAINER "you"<EMAIL_ADDRESS>ENV container docker
RUN (cd /lib/systemd/system/sysinit.target.wants/; for i in ; do [ $i ==
systemd-tmpfiles-setup.service ] || rm -f $i; done);
rm -f /lib/systemd/system/multi-user.target.wants/;
rm -f /etc/systemd/system/.wants/;
rm -f /lib/systemd/system/local-fs.target.wants/;
rm -f /lib/systemd/system/sockets.target.wants/udev;
rm -f /lib/systemd/system/sockets.target.wants/initctl;
rm -f /lib/systemd/system/basic.target.wants/;
rm -f /lib/systemd/system/anaconda.target.wants/*;
VOLUME [ "/sys/fs/cgroup" ]
CMD ["/usr/sbin/init"]

Now I believe this should work fine with the docker file which is provided for given image.
So I  updated the DOCKERFILE present in the slave-base folder, by adding the above commands.
After creating the image successfully, and running with the below command:

docker run -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro -p 8080:8080 image-name

Still the systemctl command fails...
My question is, what else do I need to do to enable systemctl commands.
There are currently 3 slave folders in this repository, do i need to update all three?

the systemctl commands failed when you ran "docker run" with your image?

You may need to specify --privileged as well... see http://developers.redhat.com/blog/2014/05/05/running-systemd-within-docker-container/
However, the issue of running systemd inside a Docker container has been discussed in many other places and has nothing to do with this repository. For example:  http://unix.stackexchange.com/questions/305340/how-to-run-systemd-services-in-arch-linux-docker-container
I am closing this issue. Please reopen if you feel there's something specific to the Jenkins image that is preventing you from doing what you want.

Well that's ok...
I get the error after i try running the command in the bash after this command

docker exec -i -t --user root --privileged=true  image-id /bin/bash

And I tried running a new image with --privileged, with the same results...


fix(material-experimental/button): expose fab and icon-button mixins

The mdc fab and icon-button mixins were missing from the package's _index.scss entry-point.

There's another pending PR that does something similar https://github.com/angular/components/pull/22449.

I even approved it, too 🙃


Hosted service Observer2NOTVisible/FeatureServer does not have a service definition item

The hosted service "Observer2NOTVisible" item exists a30800f1f8c8403b8a0f144120cf5423 but does not have an associated service definition portal item. Without the service definition item the service won't be published during Ops Server publishing.
NOTE: Only hosted services published from ArcGIS Desktop or ArcGIS Pro, which upload a service definition item to portal, are supported by the ops server config publishing scripts.

@elinz I'll get this cleaned up when we get the ability to publish multipatch buildings to the NSEC Portal. This feature service works in conjunction with a UC presentation I created around the Scene Viewer and without the multipatch buildings the demo is essentially moot...so I'll be tabling this until that's resolved, at which point I'll knock this out.  In the meantime I'll unshare everything so at least others do not see it.

@elinz it doesn't appear I'm going to be able to get data permissions for the main focal point of this demonstration, hence I'm not going to clean this up and have simply deleted it.


[BUG] API extension group needs upgrade

Warning in the Harvester log
apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition

will need to bump the API extension version of the upstream dependency framework of steve.

https://github.com/rancher/wrangler/pull/154/files

https://github.com/rancher/wrangler/pull/154

CRDs(v1) created by Harvester are not compatible with CRDs(v1beta1) used in rancher v2.5.7 https://github.com/harvester/harvester/issues/749

this should be addressed with https://github.com/harvester/harvester/pull/998, the CustomResourceDefinition is deprecated error is expected to be gone in the harvester logs.

I've installed the latest harvester master-head branch (master-ada6b573-head) and I still see some warnings about the API version for CRDs but not in the harvester logs directly, so I tend to say ok.
cert-manager-cainjector-74459fcc56-ql6st_cert-manager_cert-manager-5c454923457a864d4724b8250c81ee3e0181484e8c5e27454d7e3963bce70bce.log:2021-08-04T10:20:17.076558032Z stderr F W0804 10:20:17.076341       1 warnings.go:67] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
harvester-webhook-6d94fd86cb-fvs2m_harvester-system_harvester-webhook-774ef67c2719e93a3853cf89c174658dbdcb61246c7a78ce4d26047308192f87.log:2021-08-04T10:20:26.908500481Z stderr F W0804 10:20:26.908309       7 warnings.go:70] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
rancher-76c6f7cf65-bftds_cattle-system_rancher-ec085f7f0147310fe6b4f078d8250402e0ac6db41b035cbf8c84429bb325b2f3.log:2021-08-04T10:23:43.999486964Z stderr F W0804 10:23:43.999192      31 warnings.go:80] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
@gitlawr @guangbochen WDYT?

I think it's better for us to fix those related CRD as well, thanks

[ ] https://github.com/rancher/wrangler/pull/180

The majority of the CRD update has been done. Since Harvester has pinned down an underlying Kubernetes version, this is not a release blocker for v0.3.0. Move to v1.0.0.

We cannot fix the issues in the controllers at this moment due to https://github.com/rancher/wrangler/pull/180#issuecomment-933787561 . Move the issue to beyond future, waiting for Rancher team to figure out a solution.


Directly add NuGet.org to nuget.config

Summary of the pull request
Add NuGet.org to nuget.config.  This enables other packages versions to be used without requiring credentials to add to DevHomeDependencies feed.
References and relevant issues
Detailed description of the pull request / Additional comments
Validation steps performed
PR checklist

[ ] Closes #734
[ ] Tests added/passed
[ ] Documentation updated

/azp run

I don't think we should have multiple nuget sources per security policy. Can we just ingest the required upstream packages?

/azp run

/azp run


Adding SSAE 18

closes https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/3851
@MicrosoftHeidi please review
@scanum

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.


[Text-Analytics, Search, Form Recognizer] Review and update the test/README.md

Please review the readme at the folder: test/README.md. Make updates to this file if necessary.
Consider the following questions while reviewing this file:

Are the listed environment variables sufficient to run all of the live tests?

If there are missing environment variables, please consider updating the test-resources.json at your service folder to provide the missing variables to the live tests that run on CI.

Are we communicating what Azure resources are needed to run the tests?

Consider that you are a new user who wants to set up these resources using the Azure portal, can they follow the Azure guides to make these resources or do they need special instructions?

Do the environment variables that are specific to this project reference the project? Variables such as ENDPOINT should be prefixed with a distinct reference to the endpoint of the service they're targeting.

The same applies to search-documents as well. I believe we copied over the test infrastructure from TA

I am merging #8928 as-is so that we can deliver the README changes for Text Analytics p.5. Conversation is here: https://github.com/Azure/azure-sdk-for-js/pull/8928/files#r426892674
Still on the table is whether or not to move the AAD setup documentation to a common location or leave it in many places.

I think we can close this for now.


[translation] Spanish

Added spanish translation of half of the file

Please don't create PR's for unfinished translations. If you need help to finish this translation, please ask for help in #39


add installation guide for fedora

CentOs also

Hi, do you actually need to compile and build the code?
Runnable binaries are here:

https://github.com/zcoinofficial/zcoin/releases/tag/v<IP_ADDRESS>

I am personally running this code on Fedora 23 in a XEN VM on Qubes as my main wallet.
May we close this issue?


Does geo-replication failover group for managed instance support auto failover of SQL replication subscriber ? Provide the guidance for recovery of replication topology in failover across region.

Does geo-replication failover group for managed instance support auto failover of SQL replication subscriber ? Provide the guidance for recovery of replication topology in failover across region

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

ID: d7cd1942-8ac7-eae9-4ac8-eb716ecd7b7b
Version Independent ID: 559730f0-71fd-b16c-ecac-56954d5f2f64
Content: Configure replication in an Azure SQL Database managed instance database
Content Source: articles/sql-database/replication-with-sql-database-managed-instance.md
Service: sql-database
Sub-service: data-movement
GitHub Login: @allenwux
Microsoft Alias: xiwu

@hpatel01 Could you please provide us with the link to the Microsoft Documentation you were referring to ?
Thanks,
Adam

Two separate features, one supporting auto failover group and 2nd to configure replication subscriber for managed instance.
Is it transparent to replication subscibed databases when DBs are moved from Primary to Secondary managed instance and vice versa?

@hpatel01 Given that there was no specific document referenced when you created this issue, we need to fully understand the desired functionality you are seeking but did want to explain a few things.
Firstly, Active Geo-Replication is not supported with Azure SQL Managed Instance. If you are looking for this functionality with Managed Instance, you will need to leverage Failover Groups.

Azure SQL managed Instance currently does not support multiple failover groups. Also, what I am unable to identify is any support for Data Sync in Failover Group(s) or with Geo-Replication. So, I am investigating this piece but, can you please be more specific with your desired use case? This will be very helpful.

@douglaslMS @CarlRabeler @stevestein In looking through the Geo-Replication and Failover Group docs, I do not see any details with regard to Data Sync being supported or not supported. Any input would be greatly appreciated here. Thank you!

@Mike-Ubezzi-MSFT please assign to @MashaMSFT

Hi @hpatel01, thanks for contacting Microsoft! Can you please review this and let us know if this satisfies your question?
https://docs.microsoft.com/en-us/azure/sql-database/sql-database-managed-instance-transact-sql-information#replication
Thanks!
Masha from the SQL Docs team

Hi @Masha, as I understand based on above doc, publisher and distributor in  failover group on managed instance will have to be reconfigured on secondary MI but my question is about subscribed database and seems there is no guidance on subscribed database in failover group on managed instance. Since failover group creates a DNS CNAME record I am hoping same can be used to avoid re-configure replication for subscribed database when failover to secondary managed instance.

Hi @hpatel01, ah! I see what you mean :) Let me do a little bit of digging and get back to you.
Thank you!
Masha from the SQL Docs team

Hi @hpatel01, just wanted to let you know I'm still looking into this. Thank you for your patience and I apologize for the delay!
Masha from the SQL Docs team

Hi @hpatel01 , thanks for your patience! You are able to add a subscriber MI into a failover group as long as you keep in mind the following limitations:

For failover with no data loss, replication will just work after failover
For failover with data loss, replication will work as well. It will replicate the lost change again.
For failover with data loss but the data loss is outside of distribution DB retention period, customer will have to reinitialize subscription database.

We are working on updating the documentation to reflect this.
I hope that helps and please let us know if anything further is needed from our end? If not we will proceed with closing out this Git Issue. However, please feel free to respond and we would be happy to reopen and continue to assist you.
Thanks!
Masha from the SQL Docs team
#please-close

Thank you Masha, this answers my question.


Fix inconsistencies in frequency response at poles

This PR addresses issue #532 regarding inconsistencies in the return values for various frequency response functions.  The changes fixes a number of previous inconsistencies, where state space and transfer function representations could return different values and evaluating the frequency response at the "origin" gave different values depending on whether you evaluated at 0 or 0j.
The changes here only affect results when evaluating the system at a pole of the system.
In this PR:

State space systems and transfer functions return the same values when evaluated at poles (including poles at the origin):

Evaluation at 0 with pole at the origin: returns (inf + nanj)
Evaluation at non-origin pole with nonzero numerator: returns (inf + infj)
Evaluation at pole with cancellation by a zero: returns (nan + nanj)

State space systems and transfer functions interpret argument as a complex number, so that G(0) and G(0j) return the same value.
Computing the DC gain is (exactly) the same as evaluating at 0

A few other small changes:

Added a warn_infinity flag to all functions used to evaluate frequency response.  By default this is set to True, in which case you get a divide by zero warning or singular matrix warning when evaluating at a pole.  Setting it to False suppresses this warning.  (Also, dcgain sets warn_infinity to False by default).
Updated docstrings and unit tests

Coverage decreased (-0.009%) to 88.293% when pulling 598058cb3eb8203c8bdfbffca322ba81ec458b91 on murrayrm:infinite_gain into eb62d80995f461cf86cab8911d81929affb9e477 on python-control:master.


AG-592 Extended /auth/session to contain user role

This is OK but not very generic for a framework purpose, but good enough.
However you use roles in 2 different ways. Using set_auth(roles=xxx) duplicates returning the roles within attributes. The set_auth variant should probably be reserved for framework roles.


Details for externs option flag

What is the format of the externs option flag?
I've tried a couple but nothing worked:
var the_flags = {
  externs: ['cljs.user.foo = function(){};'],
  compilationLevel: "ADVANCED",
  jsCode: [{src: 'var a = cljs.user.foo();console.log(a);'}]
};
var the_out = compile(the_flags);
console.info(the_out);

var the_flags = {
  externs: [{src:'cljs.user.foo = function(){};'}],
  compilationLevel: "ADVANCED",
  jsCode: [{src: 'var a = cljs.user.foo();console.log(a);'}]
};
var the_out = compile(the_flags);
console.info(the_out);

In any case, the compiledCode is:
 "var a=cljs.b.a();console.log(a);"

Anyone could help here?

maybe @samthor ?

Please set warningLevel: 'VERBOSE' and you'll get more output to see what might be going wrong.
The latter is correct re: src, as per the README. The issue is that Closure doesn't know what cljs.user is. So you can try-
var cljs;
cljs.user = {};
cljs.user.foo = function(){};

I'll also add that this is not a Closure Compiler in JS specific issue, so I'm going to close this. Externs are a complex part of Closure. For more information check out the official tutorial or the wiki.

I think you have to declare the root variable in the extern as well.
Something like this, perhaps:
externs: ['var cljs; cljs.user.foo = function(){};']


Support for Rebar3 style deps

Elvis fails on a rebar.config file which uses Rebar3 style deps with the following error.
# rebar.config [FAIL]
Error: 'function_clause' while applying rule 'protocol_for_deps_rebar'.
Loading files...
Applying rules...

This is the style which it fails on.
{deps, [
  {poolboy, {git, "https://github.com/devinus/poolboy.git", {tag, "1.5.1"}}},
  {gproc,   {git, "https://github.com/uwiger/gproc.git", {branch, "master"}}}
]
}.

According to Elvis:

Dependency 'getopt' revision is specified 'master', please change this to a tag, branch or specific commit.

According to Elvis:

Dependency 'aleppo' revision is specified 'master', please change this to a tag, branch or specific commit.

@walrusVision Thanks for your PR. Could you check the line length warnings from gadgetci? Just ignore the other ones about a dep being in master since that's just the test file, which is supposed to fail. Thanks!


add support for single (json?) config stored in a project directory

e.g. we could use it for defining output binary, location of manatee lib etc.

For this ticket, I would suggest adding just a first item: targetBinary with a filesystem path (both relative and absolute paths should be supported). It should be possible to run manabuild without parameters and it should look for the binary name in the file.
For the file name, I would suggest .manabuild.json. And manabuild should clearly print (during its startup) that it found the configuration file (if applicable) and it will be used.


Capture escape sequences

I didn't test it with this plugin, but tmux's capture-pane command has a -e flag to also capture escape sequences.
This will allow us to also capture colored output etc.
From quick testing it seems to work:
set test (tmux capture-pane -e -p -J)
echo $test

I added a new flag @tmux-last-color to make this work.  Off by default as it takes a little extra configuration for prompt patterns and such plus PAGER doesn't usually include flags to consume escape codes by default (I assume).
https://github.com/mskelton/dotfiles/commit/86c171e9


Failing include does not lead to non zero exit code

When an include fails, pandoc still returns 0 when exiting.
Take for example this file:
example.md
and execute this pandoc command:
pandoc --fail-if-warnings --lua-filter=include-files.lua example.md --output jan.html

This results in this messages in the terminal:
Cannot open file file_to_include.html | Skipping includes

However, the exit code is still 0 instead of an error code.
Initially, I incorrectly reported this issue here: https://github.com/jgm/pandoc/issues/9972
The response was:
Please re-raise this issue with the project from where you've gotten the include-files.lua filter. The filter should use the pandoc.log module to raise the warning.
Pandoc version?
pandoc 3.1.3
Features: -server +lua
Scripting engine: Lua 5.4

I've pushed a fix, but it requires pandoc 3.1.4.


Ability to configure build when deploying from source

TL;DR
Is there any way to configure build when deploying from source?
I mean setting basic configuration variables from this page:
https://cloud.google.com/docs/buildpacks/service-specific-configs
Detailed design
No response
Additional information
No response

When deploying from CLI using gcloud run deploy --source ., you can configure these values using project.toml, but this file is ignored for some reason when using this action (it's not uploaded to the cloud build)

my bad, project.toml is actually working


Add multi-field search with boosts

Coverage decreased (-0.4%) to 97.917% when pulling 504cd3ed699a9619a7c27749d9cc94b5be74efe2 on sstults:master into c1f3b72f80459ba55682a234ca3c642f09c7d76e on boundlessgeo:master.

Coverage decreased (-0.4%) to 97.917% when pulling f9ccc95125e8d393e008204836befbe8daa5cec2 on sstults:master into c1f3b72f80459ba55682a234ca3c642f09c7d76e on boundlessgeo:master.

Coverage decreased (-0.4%) to 97.917% when pulling f9ccc95125e8d393e008204836befbe8daa5cec2 on sstults:master into c1f3b72f80459ba55682a234ca3c642f09c7d76e on boundlessgeo:master.

I'm looking into why this is failing on ES_VERSION < 2

Hey Scott,
In Elasticsearch 1.7 the tests are failing. It seems to be related with the ordering of the results, could you help us investigate? It should be as easy as changing the elasticsearch version in docker-compose.

Coverage increased (+0.002%) to 99.655% when pulling df87ae9401767bdd9f5c8d0f6ca2c80dad44e334 on sstults:master into b7ebd334ecea3f51515af0ca990ea846c7c8bbd0 on boundlessgeo:master.

For ES < 2 the full-text query was being added to the boolean query filter. It needs to be outside of the filter in order to preserve score, and score is what lets field boosts work. So I reordered the final structure of the query a bit.

@sstults It means that for versions > 2, elasticsearch computes scores even the query_string is within a filter? Good to know!


Add workflow and publication status options to administrative information

This pull request introduces several changes to support the addition of workflow and publication status information in both the English and Chinese locales, as well as updates to the form and view components to handle this new information.

@linancn


[Feat]: enhance the announcement bar

Description
please replace the announcement bar message with something more catchy.
Solution
might be: "Are you a Content Creator? Join the Community"
Join the Community should have the link to the 4c community
Anything else?

Code of Conduct

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

Great issue @FrancescoXX!!

Fixed by #392


Added sleep before creating a pool

Etherium contracts take time to be created. So, if the program is run by copying the code to a .py file, it will throw an error. Therefore, the program must be paused for 30 seconds before creating the pool if it is executed through a .py file. This is linked to the issue #106

Follow-up change: https://github.com/oceanprotocol/ocean.py/commit/7577639b4875fa249c6479f03c838a5dd9848652

Follow-up change: https://github.com/oceanprotocol/ocean.py/commit/7577639b4875fa249c6479f03c838a5dd9848652


Compilation problem

Hi, when I try to compile Maple with GCC 4.9.2, I get the following error message. Any ideas what's going wrong? Thanks!
g++ -fPIC -D_GNU_SOURCE -D_USING_DEBUG_INFO -Wall -Werror -g -D_DEBUG  -I/home/mch11220/pin-2.14-71313-gcc.4.4.7-linux/source/include/pin -I/home/mch11220/pin-2.14-71313-gcc.4.4.7-linux/source/include/pin/gen -I/home/mch11220/pin-2.14-71313-gcc.4.4.7-linux/extras/components/include -I/home/mch11220/pin-2.14-71313-gcc.4.4.7-linux/extras/xed-intel64/include -I/home/mch11220/pin-2.14-71313-gcc.4.4.7-linux/source/tools/InstLib -DBIGARRAY_MULTIPLIER=1 -Wall -Werror -Wno-unknown-pragmas -fno-stack-protector -DTARGET_IA32E -DHOST_IA32E -fPIC -DTARGET_LINUX  -I/home/mch11220/pin-2.14-71313-gcc.4.4.7-linux/source/include/pin -I/home/mch11220/pin-2.14-71313-gcc.4.4.7-linux/source/include/pin/gen -I/home/mch11220/pin-2.14-71313-gcc.4.4.7-linux/extras/components/include -I/home/mch11220/pin-2.14-71313-gcc.4.4.7-linux/extras/xed-intel64/include -I/home/mch11220/pin-2.14-71313-gcc.4.4.7-linux/source/tools/InstLib -O0 -g -Isrc/ -I/usr/local/include  -c -o build-debug/tracer/profiler.o src/tracer/profiler.cpp
In file included from src/core/execution_control.hpp:37:0,
from src/tracer/profiler.hpp:23,
from src/tracer/profiler.cpp:20:
src/core/wrapper.hpp: In member function ‘void Wrapper<W, void()>::CallOriginal()’:
src/core/wrapper.hpp:172:23: error: cannot convert ‘LEVEL_VM::PARG_T’ to ‘LEVEL_VM::CALL_APPLICATION_FUNCTION_PARAM_’ for argument ‘5’ to ‘LEVEL_BASE::VOID LEVEL_PINCLIENT::PIN_CallApplicationFunction(const CONTEXT_, LEVEL_VM::THREADID, LEVEL_VM::CALLINGSTD_TYPE, LEVEL_BASE::AFUNPTR, LEVEL_VM::CALL_APPLICATION_FUNCTION_PARAM*, ...)’
PIN_PARG_END());
^
src/core/wrapper.hpp:285:5: note: in expansion of macro ‘CALL_ORIGINAL_NORET’
CALL_ORIGINAL_NORET(NUM_ARGS);
^
src/core/wrapper.hpp:322:1: note: in expansion of macro ‘WRAPPER_TEMPLATE_NORET’
WRAPPER_TEMPLATE_NORET(0);
^
Makefile:121: recipe for target 'build-debug/tracer/profiler.o' failed

It compiles with Pin 2.14 Rev 67254. However, when trying to run the shared_counter example as described in the README, the following error message is omitted:
Traceback (most recent call last):
File "/home/mch11220/Downloads/maple-1.1.0/script/maple/idiom/main.py", line 1207, in
main(sys.argv[1:])
File "/home/mch11220/Downloads/maple-1.1.0/script/maple/idiom/main.py", line 1202, in main
eval('_command%s(argv[1:])' % command)
File "", line 1, in
File "/home/mch11220/Downloads/maple-1.1.0/script/maple/idiom/main.py", line 768, in __command_default
idiom_testcase.run()
File "/home/mch11220/Downloads/maple-1.1.0/script/maple/core/testing.py", line 226, in run
self.body()
File "/home/mch11220/Downloads/maple-1.1.0/script/maple/idiom/testing.py", line 185, in body
self.profile_testcase.run()
File "/home/mch11220/Downloads/maple-1.1.0/script/maple/core/testing.py", line 226, in run
self.body()
File "/home/mch11220/Downloads/maple-1.1.0/script/maple/core/testing.py", line 257, in body
test.run()
File "/home/mch11220/Downloads/maple-1.1.0/script/maple/core/testing.py", line 84, in run
self.body()
File "/home/mch11220/Downloads/maple-1.1.0/script/maple/core/testing.py", line 110, in body
stderr=self.fio[2])
File "/usr/lib/python2.7/subprocess.py", line 710, in init
errread, errwrite)
File "/usr/lib/python2.7/subprocess.py", line 1335, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory

Anyone here for Pin error: cannot convert ‘LEVEL_VM::PARG_T’ to ‘LEVEL_VM::CALL_APPLICATION_FUNCTION_PARAM_’ for argument ‘5’, the quick fix is to add a NULL in after the function pointer.
Relevant documentation. The missing argument:
[in] | param | Additional parameters to define the exact behavior of this function invocation (or NULL for using the defaults)

@TACIXAT Hello, I encountered the same problem and read your answer. However, I didn't fully understand it. Can you please give me an example? Thank you.

@ShadowLL It's been two years, but my understanding is the fifth argument to the call can be null. Recent documentation link.
Example here - https://github.com/sarabjeetsingh007/sniper-7.2-debug/blob/84495873c991308a7441b5b1db1a64f8ec2da538/sift/recorder/emulation.cc#L146 (see the NULL in the fifth argument)


Cleanup atmospec.ipynb

Blocked on upstream changes in aiidalab_widgets base
https://github.com/aiidalab/aiidalab-widgets-base/pull/332

I have merged this in to unblock development although https://github.com/aiidalab/aiidalab-widgets-base/pull/332 needs more work. For now this mean that the main branch here only works with https://github.com/danielhollas/aiidalab-widgets-base@conformer-manager (which also meant disabling a test for now).


Using d3-force and d3-quadtree with create-react-app

CRM  strictly requires ES5 modules while d3-force and d3-quadtree are known to have ES6 code. Any suggestions on using these  modules with CRM?
Thanks!
Parul

Duplicate of d3/d3-quadtree#23.


AMQP-788 Add delegate publisher connection factory

#JIRA: https://jira.spring.io/browse/AMQP-788
To avoid deadlocks, it is best to use a different connection for producers and
consumers (unless the producer is partiticipating in a consumer transaction).

Add a delegate publisherConnectionFactory to the CachingConnecetionFactory.
Use the same underlying com.rabbitmq.client.ConnectionFactory in each.
Propagate all properties to the delegate.
Except, enhance the connection name and bean name with .publisher.
Add a boolean usePublisherConnection to the RabbitTemplate.
If true, use createPublisherConnection() when appropriate.

TODO: Docs (after review)

What am I missing?

It's very simple (in my mind) and quite different to what I was proposing at SpringOne (SimpleConnection having two delegate connections internally). That solution became very complicated, with regard to caching channels.
This simply uses 2 connection factories so the caches are completely independent.

otherwise they can configure them differently and the order in which they configure them would matter.

Not sure how it is related to us. They always can configure two different CFs and inject them to different components. That's already end-user code will be. What we suggest here is for convenience: the configuration of two CFs in a single place. They always can do that themselves like we recommend in docs.
More over how they can re-configure a result of the public ConnectionFactory getPublisherConnectionFactory()? Unless they are too cool to cast do the harm for themselves 😄
I absolutely agree about copy CF in the CCF, but I don't get yet one would we need that createPublisherConnection(). That's what I don't like because it breaks CF contract per se.
That's my feeling

Yes; convinced - it also makes the backport easier 😄
Thanks!

I don't know why GitHub won't allow me to reply to this comment.

But if we select the publsherCF before calling this getTransactionalResourceHolder(), we don't need the logic around publisherConnectionIfPossible here at all. Isn't it?

No, because when a transaction is in process, the bound channel to use is from the outer connection factory. The RabbitTemplate has to lookup the transactional channel based on the container's connection factory, not the publisher CF.

Merged as https://github.com/spring-projects/spring-amqp/commit/4b78c200012bbe7ac8112bcd4753d0f111de3762


raco test laundry: Rule wsnn has no definition

$ raco test laundry
raco test: "laundry/block.rkt"
raco test: "laundry/cli.rkt"
raco test: (submod "laundry/colorer.rkt" test)
#<class:text-mixin>
raco test: "laundry/expander.rkt"
raco test: "laundry/grammar/heading.rkt"
raco test: "laundry/grammar/org.rkt"
raco test: "laundry/grammar/paragraph.rkt"
raco test: "laundry/grammar/plain-list.rkt"
laundry/grammar/planning.rkt:5:35: wsnn: Rule wsnn has no definition
  in: wsnn
  location...:
   laundry/grammar/planning.rkt:5:35
  context...:
   /home/bost/.local/share/racket/8.3/pkgs/brag-lib/brag/codegen/codegen.rkt:158:0: check-all-rules-defined!
   /home/bost/.local/share/racket/8.3/pkgs/brag-lib/brag/codegen/expander.rkt:24:0
   /gnu/store/bgsjf1g4bjicnliispayis9zjfqpdcfb-racket-8.3/share/racket/pkgs/compiler-lib/compiler/commands/test.rkt:383:27
   /gnu/store/bgsjf1g4bjicnliispayis9zjfqpdcfb-racket-8.3/share/racket/pkgs/compiler-lib/compiler/commands/test.rkt:385:0: call-with-summary
   .../private/map.rkt:40:19: loop
   [repeats 4 more times]
   /gnu/store/bgsjf1g4bjicnliispayis9zjfqpdcfb-racket-8.3/share/racket/pkgs/compiler-lib/compiler/commands/test.rkt:385:0: call-with-summary
   .../private/map.rkt:40:19: loop
   [repeats 5 more times]
   /gnu/store/bgsjf1g4bjicnliispayis9zjfqpdcfb-racket-8.3/share/racket/pkgs/compiler-lib/compiler/commands/test.rkt:385:0: call-with-summary
   .../private/map.rkt:40:19: loop
   /gnu/store/bgsjf1g4bjicnliispayis9zjfqpdcfb-racket-8.3/share/racket/pkgs/compiler-lib/compiler/commands/test.rkt:1113:1: test
   body of "/gnu/store/bgsjf1g4bjicnliispayis9zjfqpdcfb-racket-8.3/share/racket/pkgs/compiler-lib/compiler/commands/test.rkt"
   /gnu/store/nivzasmjdp2pgh93hj7wvwrlmwkasljh-racket-minimal-8.3/share/racket/collects/raco/raco.rkt:41:0
   body of "/gnu/store/nivzasmjdp2pgh93hj7wvwrlmwkasljh-racket-minimal-8.3/share/racket/collects/raco/raco.rkt"
   body of "/gnu/store/nivzasmjdp2pgh93hj7wvwrlmwkasljh-racket-minimal-8.3/share/racket/collects/raco/main.rkt"

This should have been fixed in the push yesterday: https://github.com/tgbugs/laundry/blob/fa9e70aa607cb48f97445cd24e8ca63addb74e9d/laundry/grammar/planning.rkt#L18. Can you check to make sure that you have the latest version installed?

$ pwd
/home/bost/.local/share/racket/8.3/pkgs

$ sha1sum laundry/grammar/planning.rkt
0873af6b6c51c7106491fa8fcdb882556107f6cc  laundry/grammar/planning.rkt

$ cat -n laundry/grammar/planning.rkt
     1	#lang brag
     2
     3	; TODO clean this up as a sub-grammar
     4
     5	planning : ( plan-sep plan-info )+ /wsnn* ;not-plan-keyword-timestamp-newline?
     6	plan-sep : /wsnn*
     7
     8	plan-info : plan-keyword /COLON /wsnn* plan-timestamp?
     9	plan-keyword : plan-dead | plan-sched | plan-open | plan-close
    10	plan-timestamp : timestamp
    11	plan-dead : CHARS-DEADLINE
    12	plan-sched : CHARS-SCHEDULED
    13	plan-open : CHARS-OPENED ; XXX suggested improvement
    14	plan-close : CHARS-CLOSED
    15
    16	timestamp : TIMESTAMP
    17
    18	wsnn : WSNN

The commit you created yesterday was made at:
$ git show fa9e70a | grep Date
Date:   Sat Feb 5 11:17:26 2022 -0800

And I deleted the cache and reinstalled the packages with following commands:
$ history | grep "rm.*download-cache"
rm -rf ~/.cache/racket/download-cache/

$ history | grep "org.*laundry"
raco pkg install org laundry
raco pkg remove org laundry

more than 24 hours later, at:
$ ls -lA --time-style="+%d-%m-%Y %H:%M:%S" | grep "laundry\|org"
drwxr-xr-x 4 bost users 4096 06-02-2022 14:29:13 laundry
drwxr-xr-x 3 bost users 4096 06-02-2022 14:29:14 org

(my timezone is CET - Central European Time; that's UTC +1)

0873af6b6c51c7106491fa8fcdb882556107f6cc matches the hash that I have for planning.rkt at fa9e70a.
I cannot reproduce the error running in a clean environment with a separate user from ~/.local/share/racket/8.3/pkgs with raco test laundry. I get a single test failure of parse of "  #+begin_srclol" does not contain paragraph.
The only thing I could think of would be if there was some other source for the code. It looks like you have a git repo of laundry around as well? If you ran raco pkg install laundry instead of raco pkg install laundry/ that will install from pkgs and not use the local git repo. If you did not pull the git repo but you run raco test laundry from in the git repo it would test against the stale version in .e.g ~/git/laundry/laundry instead of the up-to-date version in ~/.local/share/racket/8.3/pkgs/laundry. Not sure if this is what happened but it might be?
You could check if this happened by looking at the contents of
~/.local/share/racket/8.3/links.rktd. My git install points to
("laundry" (up up #"git" #"laundry" #"laundry")), whereas my pkgs install points to
("laundry" (#"pkgs" #"laundry")).

I created myself a clean and reproducible development environment (RDE) under GNU Guix and it seems like the problem is on my side. I'm closing this issue.
Regarding the RDE definition - I'll send you a PR soon.


Update README.rst

Summary of the changes / Why this improves CrateDB
Checklist

[ ] Added an entry in CHANGES.txt for user facing changes
[ ] Updated documentation & sql_features table for user facing changes
[ ] Touched code is covered by tests
[ ] CLA is signed
[ ] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

not directly related to this PR but just in case - this page has old slogan "Put machine data to work"

Hm,
CI job #16260 tells us that:
The message received from the daemon indicates that the daemon has disappeared.
Build request sent: Build{id=d4ffb046-6217-479a-b504-70cc4bbf1ea9, currentDir=/var/lib/jenkins/workspace/CrateDB/crate_on_pr}
[...]
FAILURE: Build failed with an exception.

* What went wrong:
Gradle build daemon disappeared unexpectedly (it may have been killed or may have crashed)

Is this something you know anything about, @BaurzhanSakhariev?
With kind regards,
Andreas.

Is this something you know anything about

Probably related to https://github.com/crate/crate/pull/11935#issuecomment-981720657
retest this please


Fix typo in exclamation icons

Hi there, the v2 release introduced a typo in the exclamation icon names:
-exclaimation
+exclamation

Duplicate of #735, oops.