Use $HISTFILE for Ctrl-R to find results from multiple terminals

This PR allows to search in the history of multiple terminals in Bash while maintaining separate histories for each terminal.
To enable it one has to set:
export PROMPT_COMMAND="history -a"

While I find it desirable to not sync history between all terminals immediately, I think it is very useful to to be able to search for commands from other terminals.
With https://github.com/junegunn/fzf/pull/749 the same could be achieved, but this PR aims for a more specialized functionality. I'm curious if there is some interest for this feature :-)

Thanks for the suggestion, but I'm not interested in adding more options to these shell extension scripts because maintaining these scripts for three different shells has been really painful and time-consuming that I don't want to increase the complexity anymore. I suggest that you override the function in your shell configuration file.


Tifffile _biggestSeries() bug for large images

The _biggestSeries() method used to read tifffile sources rely on np.prod(shape) to find the biggest series in the file (macro image > image). This leads to an overflow for big images and the macro image is wrongly selected as the main content of the file. Simple fix is done with np.sqrt(), though a better solution could be found.

Do you have an example image where it fails?  If it can't be shared, can the output of tifftools dump <image> be shared?
I don't understand why the sqrt of the shape product would be desirable.  The intent is that the main series would be the series with the most total pixels.  If it is overflowing do to data types, a better choice might be to samples = np.prod(float(x) for x in s.shape) to cast the values to float values before multiplication.


Add detectLine in RenderLayer (+tests)

Part of #61

Fixed by https://github.com/CartoDB/renderer-prototype/pull/221


DOCS-6252 create connected app with UI

Option to create a connected app with UI is not present, so this info was removed in DOCS-6172 and https://github.com/mulesoft/docs-api-community-manager/pull/115 . It will be released Oct 19, so merge this PR as part of that release.

cc @jdeoliveira - Today I removed the info on creating a connected app with the UI, and I will add it back at the time of the Oct 19 release.


萌新 落落的问 个问题

在vue中怎么引入 这个气泡球插件
Error: Component series.liquidFill not exists. Load it first.
堆栈跟踪：
clazz.enableClassManagement/entity.getClass@webpack-internal:///23:166:23
visitComponent/<@webpack-internal:///440:195:51
each@webpack-internal:///0:263:13
visitComponent@webpack-internal:///440:178:17
componentUtil.enableTopologicalTravel/entity.topologicalTravel@webpack-internal:///89:89:21
mergeOption@webpack-internal:///440:147:13
initBase@webpack-internal:///440:642:9
resetOption@webpack-internal:///440:92:21
setOption@webpack-internal:///440:74:13
echartsProto.setOption@webpack-internal:///1:279:9
initChart@webpack-internal:///208:65:7
boundFn@webpack-internal:///17:184:9
mounted@webpack-internal:///208:27:5
callHook@webpack-internal:///17:2666:9
insert@webpack-internal:///17:3527:7
invokeInsertHook@webpack-internal:///17:5470:9
patch@webpack-internal:///17:5640:5
lifecycleMixin/Vue.prototype._update@webpack-internal:///17:2425:16
updateComponent@webpack-internal:///17:2539:7
get@webpack-internal:///17:2882:13
run@webpack-internal:///17:2959:17
flushSchedulerQueue@webpack-internal:///17:2725:5
queueNextTick/<@webpack-internal:///17:702:11
nextTickHandler@webpack-internal:///17:649:7

在echarts/index.js里面加上require('../echarts-liquidfill/index')就可以了，试试看~


[W5.7][W16-4] LAW YONG QIANG CLINTON

Update user guide to reflect the change in the find method

Very useful change to ab2, normally people wouldn't want to care about the upper/lower casing

Good and practical feature!

Very useful feature!

Very useful feature!

Nice!! Now we do not need to care about caps when finding things


Unloaded Minecart bug

What is the error?
Whenever you hold the GUI item on your hand, if you're far away from 0 0 (from a distance it stops loading the chunk), the minecart won't load
Yes, I'm using forceload 0 0, funnily enough, the minecart, marker and item display DO spawns and TP, but the minecart isn't loaded, and you can't open it
How to Reproduce?
Get up to 200+ blocks distance from 0 0 and hold the item
Pictures

Close to 0 0 0

Far from 0 0 0
You can see that the particles are still playing, and you can even TP to the minecart, but it wont show anything (I'm without the hide minecarts texturepack)

After more testing, I discovered that's a bug from minecraft, and somehow the cart was spawning at 0 0 0 by the server, instead of spawning at the player's location
Simple fix was just to run "execute as @a at @s" in the tick command, seems redundant as you execute like the player, but this way it works
A more safer fix to prevent anything else happening is to just put a at @s at the minecart spawning command

I was also having this issue. Thank you so much for figuring out a fix


Add logging to configuration

Currently, logging can only be set via the command-line argument:
-l, --log=[FILE|stdout]
       Path to logfile or stdout.

config.pl should also support setting this.

Maybe it wouldn't be fortunate to share settings between CLI options and configuration file. The disjunction is nice and clean now.
There is already a notion of dependency between the two: CLI option -c implies a custom config path. This means CLI options should be parsed first.
However, if we wanted logging configuration at both places, then it would be sensible if the CLI option overrode the config file setting.
Of course, we could drop the -l when introducing a logging setting to the config file, but I don't really see a compelling reason to do this either.
All things considered, this doesn't seem to worth overcomplicating things.
So I'm closing the issue.


Feat: Move2Kube Cheatsheet

#108

This is awesome. Thanks! @HarikrishnanBalagopal please review and merge.

@lakshay-nasa Please complete the DCA by signing the PR/commit

@HarikrishnanBalagopal In which directory should I add the source folder? Is ./docs/commands/move2kube_cheatsheet* the correct location? May you please provide guidance on how to complete the DCO for the 'Merge branch 'konveyor:main' into m2k_cheatsheet'? Thank you.

 ./docs/commands/move2kube_cheatsheet/ sure you can add it in that folder if there are multiple files that make the pdf.
You can read this but basically you need to sign the commit using the -s flag. You can also add it manually in the commit message.
https://github.com/konveyor/move2kube/blob/main/contributing.md#contributing
https://stackoverflow.com/questions/1962094/what-is-the-sign-off-feature-in-git-for
It adds a line, for example:
Signed-off-by: seshapad [seshapad<EMAIL_ADDRESS>
https://github.com/konveyor/move2kube-website/pull/104

Closing this pull request due to conflicts. Will submit a new one soon.


Codeunit 7600 "Calendar Management", Function: CheckDateStatus, Add new event

Hi,
Can the follow event please be added in,
Codeunit 7600 "Calendar Management",
Inside Function: CheckDateStatus
Where:

The new event:
[IntegrationEvent(false, false)]
local procedure OnCheckDateStatusAfterDateCustomized(var TargetCustomizedCalendarChange: Record "Customized Calendar Change"; TempCustChange: Record "Customized Calendar Change")
As I wish to pass the Temporary Customer Calendar change as a parameter.
Kind Regards Nic

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


[create-burner] Client errors when stored burners not found

Repro:

Run local Katana + Torii
Open client, create burner wallets
Close Katana + Torii
Migrate
Run local Katana + Torii
Open client
useBurner() will trigger a client error when trying to find the stored wallets that do not exist anymore

Dojo 0.3.15
create-burner 0.1.56
game

do you mean the txhash not found?

yes, I forgot to attach the error.
it should ignore unknown wallets, or raise a warning, but not a client error.


Use npm scripts instead of Makefile

Should fix #13

Another thing I noticed is that some deps are in devDeps instead of deps.
A diff of a potential other commit is (including pointing to latest react-router as the PR has been merged):
diff --git a/package.json b/package.json
index 5ca9841..fb830a8 100644
--- a/package.json
+++ b/package.json
@@ -37,14 +37,15 @@
     "mocha": "^2.2.5",
     "mocha-jsdom": "^1.0.0",
     "node-libs-browser": "^0.5.2",
-    "react": "0.13.x",
-    "react-redux": "2.x",
-    "react-router": "git+https://github.com/acdlite/react-router.git#d8a41c86090ee661bc19b93c0a9169db510c46d8",
-    "redux": "2.x",
     "redux-devtools": "^2.1.0",
     "rimraf": "^2.4.3",
     "sinon": "^1.15.4",
     "webpack": "^1.12.1"
   },
-  "dependencies": {}
+  "dependencies": {
+    "react": "0.13.x",
+    "react-redux": "2.x",
+    "redux": "2.x",
+    "react-router": "git+https://github.com/acdlite/react-router.git#6e16d3aca47f7152e41bf0055885893d8cfa1189"
+  }
 }

Let me know if you want me to submit another PR for that or if there is a reason I'm not aware of

React is better suited as a peer-dependency. Don't limit the version to 0.13 though, a lot of people are using the 0.14 betas, and that would break it for us.

Ah i thought peerDependencies were completely going away but apparently not. I do use 0.14 myself as well actually, i'll wait for @acdlite to see if we want to move to peerdeps/deps

The reason they're in devDependencies is because they're needed for testing.
The reason they're not in peerDependecies instead is because I hate peerDependencies with every part of my soul — until everyone is on npm3 and they are just a warning and don't block install. E.g. the other day I was trying out React 0.14 on a project and had to fork several dependencies and delete their peerDep just to get up and running.

Unrelated but could you publish that branch to npm as a beta? src is in npmignore so we need to clone + build  + cp to try it rather than installing through npm

I'd be fine with not using peer dependencies at all, I also find em extremely annoying

@Keats Just published v1.0.0-alpha1

Thanks !


Removing unmaintained plugins

What's the policy on removing unmaintained plugins?
E.g.:

sunjon/Shade.nvim is unmaintained for over a year now; full if bugs

In cases like this it's better to remove them, this is not a list of all plugins ever created but a list of recommended good plugins.


Huge CPU, GPU output diff after updates to fully_connected GpuDelegate gl kernel.

Please make sure that this is a bug. As per our
GitHub Policy,
we only address code/doc bugs, performance issues, feature requests and
build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
No

OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Android

Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
Tested on Pixel2

TensorFlow installed from (source or binary):
Built from source

TensorFlow version (use command below):
v2.3.0

Python version:
3.7

Bazel version (if compiling from source):
3.1.0

GCC/Compiler version (if compiling from source):
7.5.0

CUDA/cuDNN version:

GPU model and memory:

You can collect some of this information using our environment capture
script
You can also obtain the TensorFlow version with:

TF 1.0: python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
TF 2.0: python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"

Describe the current behavior
There seems to be a bug in tensorflow/lite/delegates/gpu/gl/kernels/fully_connected.cc that was first updated in this commit.
The test itself in tensorflow/lite/delegates/gpu/gl/kernels/fully_connected_test.cc passes but when running
https://github.com/tensorflow/tensorflow/tree/master/tensorflow/lite/tools/evaluation/tasks/inference_diff on a simple custom model, the avg_error between the CPU and the GPU delegate piles up and leads to completely different results.
Describe the expected behavior
The avg_error between the CPU and the GPU delegate should stay the same even after the updates to fully_connected code, and it should not produce weird outputs.
Standalone code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate
the problem. If possible, please share a link to Colab/Jupyter/any notebook.

Prepare run_eval in v2.3.0

bazel build -c opt \
  --config=android_arm64 \
  //tensorflow/lite/tools/evaluation/tasks/inference_diff:run_eval
cp bazel-bin/tensorflow/lite/tools/evaluation/tasks/inference_diff/run_eval ./run_eval_1

Change the fully_connected shader implementation to the one prior to commit 7c7d9248
The simple implementation without the usage of shared variables, memoryBarrierShared, etc.

Prepare run_eval after second step

bazel build -c opt \
  --config=android_arm64 \
  //tensorflow/lite/tools/evaluation/tasks/inference_diff:run_eval
cp bazel-bin/tensorflow/lite/tools/evaluation/tasks/inference_diff/run_eval ./run_eval_2

Connect android device and push the tflite models below, run_eval_1 and run_eval_2 to device

adb push [] /data/local/tmp

simple.zip
The models in the zip file are submodels from a custom model that was sliced from the input layer to deeper layers accumulatively, so that running run_eval on them would show how the error changes in the subsequent layers.

Run both eval scripts on the models and save the output

# For example
adb shell find /data/local/tmp/simple -type f -name "*.tflite" | sort -V | xargs -L 1 -I{} sh -c "echo {}; adb shell /data/local/tmp/run_eval_1 --model_file={} --delegate=gpu --gpu_precision_loss_allowed=false --num_runs=5" > eval_1.txt

Compare output from both eval results

[Output from run_eval_1]

/data/local/tmp/simple/0_layer.tflite (input)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=350.6(us), std_dev=182(us)
Test run latency: avg=7788.33(us), std_dev=1361(us)
OutputDiff[0]: avg_error=0, std_dev=0

/data/local/tmp/simple/1_layer.tflite (conv2d)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=51505.2(us), std_dev=19231(us)
Test run latency: avg=76189.3(us), std_dev=21566(us)
OutputDiff[0]: avg_error=5.65735e-08, std_dev=1.23668e-10

/data/local/tmp/simple/2_layer.tflite (conv2d)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=156689(us), std_dev=34476(us)
Test run latency: avg=91240.9(us), std_dev=20015(us)
OutputDiff[0]: avg_error=2.88166e-07, std_dev=4.7596e-10

/data/local/tmp/simple/3_layer.tflite (average_pooling2d)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=154217(us), std_dev=49214(us)
Test run latency: avg=63426.3(us), std_dev=3858(us)
OutputDiff[0]: avg_error=2.06003e-07, std_dev=5.04424e-10

/data/local/tmp/simple/4_layer.tflite (average_pooling2d)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=154598(us), std_dev=56655(us)
Test run latency: avg=43006.3(us), std_dev=8692(us)
OutputDiff[0]: avg_error=8.01869e-08, std_dev=8.87667e-09

/data/local/tmp/simple/5_layer.tflite (dense)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=156916(us), std_dev=54132(us)
Test run latency: avg=36966.8(us), std_dev=1220(us)
OutputDiff[0]: avg_error=0, std_dev=0

/data/local/tmp/simple/6_layer.tflite (dense)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=152091(us), std_dev=53248(us)
Test run latency: avg=36698(us), std_dev=1180(us)
OutputDiff[0]: avg_error=0.00405404, std_dev=8.56487e-06

/data/local/tmp/simple/7_layer.tflite (reshape)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=157181(us), std_dev=52575(us)
Test run latency: avg=39436.9(us), std_dev=2816(us)
OutputDiff[0]: avg_error=0.00405404, std_dev=8.56487e-06

/data/local/tmp/simple/8_layer.tflite (mul)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=151318(us), std_dev=51893(us)
Test run latency: avg=47089.9(us), std_dev=3074(us)
OutputDiff[0]: avg_error=0.00415553, std_dev=1.17143e-05

/data/local/tmp/simple/9_layer.tflite (conv2d)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=176098(us), std_dev=49177(us)
Test run latency: avg=51363.7(us), std_dev=933(us)
OutputDiff[0]: avg_error=0.0141088, std_dev=9.8753e-05

/data/local/tmp/simple/10_layer.tflite (conv2d)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=194176(us), std_dev=42305(us)
Test run latency: avg=56783.7(us), std_dev=942(us)
OutputDiff[0]: avg_error=0.116762, std_dev=0.00102424

[Output from run_eval_2]

/data/local/tmp/simple/0_layer.tflite (input)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=404.067(us), std_dev=291(us)
Test run latency: avg=9060.07(us), std_dev=2928(us)
OutputDiff[0]: avg_error=0, std_dev=0

/data/local/tmp/simple/1_layer.tflite (conv2d)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=49690.5(us), std_dev=18876(us)
Test run latency: avg=76622.3(us), std_dev=16760(us)
OutputDiff[0]: avg_error=5.65735e-08, std_dev=1.23668e-10

/data/local/tmp/simple/2_layer.tflite (conv2d)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=154928(us), std_dev=37358(us)
Test run latency: avg=91402.5(us), std_dev=20801(us)
OutputDiff[0]: avg_error=2.88166e-07, std_dev=4.7596e-10

/data/local/tmp/simple/3_layer.tflite (average_pooling2d)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=156680(us), std_dev=51722(us)
Test run latency: avg=63421.1(us), std_dev=5300(us)
OutputDiff[0]: avg_error=2.06003e-07, std_dev=5.04424e-10

/data/local/tmp/simple/4_layer.tflite (average_pooling2d)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=168827(us), std_dev=51702(us)
Test run latency: avg=42583.5(us), std_dev=9370(us)
OutputDiff[0]: avg_error=8.01869e-08, std_dev=8.87667e-09

/data/local/tmp/simple/5_layer.tflite (dense)
GPU delegate is created.

Num evaluation runs: 5
Reference run latency: avg=158208(us), std_dev=54326(us)
Test run latency: avg=38795.7(us), std_dev=2783(us)
OutputDiff[0]: avg_error=2.78233e-08, std_dev=0

/data/local/tmp/simple/7_layer.tflite (reshape)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=159020(us), std_dev=56125(us)
Test run latency: avg=36865.9(us), std_dev=1231(us)
OutputDiff[0]: avg_error=2.78233e-08, std_dev=0

/data/local/tmp/simple/8_layer.tflite (mul)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=155681(us), std_dev=51329(us)
Test run latency: avg=46260.3(us), std_dev=2496(us)
OutputDiff[0]: avg_error=3.92487e-08, std_dev=9.90499e-11

/data/local/tmp/simple/9_layer.tflite (conv2d)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=192473(us), std_dev=49285(us)
Test run latency: avg=68372(us), std_dev=8581(us)
OutputDiff[0]: avg_error=1.127e-07, std_dev=2.97108e-10

/data/local/tmp/simple/10_layer.tflite (conv2d)
GPU delegate is created.
Num evaluation runs: 5
Reference run latency: avg=184917(us), std_dev=50705(us)
Test run latency: avg=57926.3(us), std_dev=4106(us)
OutputDiff[0]: avg_error=6.8757e-07, std_dev=1.08467e-09

in run_eval_1, the avg_error rises high after the dense layers, when compared to run_eval_2.
This leads to a weird output in the custom model that I'm using in an Android app. When I rollback the changes in the fully_connected code and build the aar myself, it works as expected and I can benefit the performance enhancements on devices that support OpenCL.
Could you please have a look at it?
Other info / logs Include any logs or source code that would be helpful to
diagnose the problem. If including tracebacks, please include the full
traceback. Large logs and files should be attached.

When I rollback the changes in the fully_connected code and build the aar myself, it works as expected and I can benefit the performance enhancements on devices that support OpenCL.

Can you clarify which commit breaks it?  Should make it much easier if you could pinpoint the problematic commit.

The commit was linked above, but let me paste it again here for convenience.
https://github.com/tensorflow/tensorflow/commit/7c7d924821a8b1b20433c2f3f484bbd409873a84

Must've missed that.  Thank you, Kevin!

Wow, that's a commit from a year ago.  Either nobody is using FC, or you're hitting a weird corner case.  We'll look into that.

I got in touch with the engineer who worked on that commit.  He told me that the implementation had a flaw but got fixed with commit 522aa755f9e4cdb37ab8d80ac252df60553c6439 from Sep 12, 2019.  Can you sync to that?

The comparison was done between
A. The code in tag v2.3.0, which includes the code changes you mentioned in 522aa755f9e4cdb37ab8d80ac252df60553c6439
and
B. Just the fully_connected.cc replaced by its former implementation, prior to commit 7c7d924821a8b1b20433c2f3f484bbd409873a84
So I don't think commit 522aa755f9e4cdb37ab8d80ac252df60553c6439 fixed the issue.


Add support for building on and targeting Mono

To build for mono:
$ ./build.sh -host mono
This will download a bootstrap msbuild/mono and use the system (in $PATH) mono to build.
You can use -useSystemMSBuild argument to skip the bootstrap msbuild/mono and just
use the system msbuild.

@radical I think mono CI jobs are disabled at the moment. Let me try a couple of things.

@dotnet-bot test ci please

@dotnet-bot test ci please

@dotnet-bot test ci please

@dotnet-bot test mono

@dotnet-bot test mono

eval "$(QQ $DOTNET_HOST_PATH) nuget locals all --clear"

How will this work without dotnet?

Refers to: build/build.sh:320 in 3cd9063. [](commit_id = 3cd90634f1d4026c3577af42c0a95ec374cc2a85, deletion_comment = False)

Updated.

Looking at the windows/full failure.

@dotnet-bot test ci please

@radical FYI, the RHEL job is broken, don't spend time on it.

I'm not sure what is causing this. windows:
11:21:02 D:\j\w\innerloop_Win---c5dcd6be\src\Package\MSBuild.VSSetup\files.swr(22,2): error SWIX1108: Could not find file at path: MSBuildTaskHost.exe. [C:\Users\runner\.nuget\packages\roslyntools.repotoolset\1.0.0-beta2-62901-01\tools\VisualStudio.SetupPackage.swixproj]
11:21:02 D:\j\w\innerloop_Win---c5dcd6be\src\Package\MSBuild.VSSetup\files.swr(23,2): error SWIX1108: Could not find file at path: MSBuildTaskHost.exe.config. [C:\Users\runner\.nuget\packages\roslyntools.repotoolset\1.0.0-beta2-62901-01\tools\VisualStudio.SetupPackage.swixproj]

MSBuildTaskHost project should be importing the ProducesNoOutput.Settings.props only for:
-  <Import Project="$(RepoRoot)build\ProducesNoOutput.Settings.props" Condition="'$(MSBuildRuntimeType)' == 'Core' or '$(MachineIndependentBuild)' == 'true'" />
+  <Import Project="$(RepoRoot)build\ProducesNoOutput.Settings.props" Condition="'$(MSBuildRuntimeType)' == 'Core' or '$(MachineIndependentBuild)' == 'true' or '$(MonoBuild)' == 'true'" />

The only change here is MonoBuild==true, which shouldn't be the case here!

oh, wait.. it passed? Did my earlier push not trigger the rebuild here?

re:RHEL, ah, thanks!

I'll wait to see a green mono build show up here, then I'll update the front page! Once this is merged, if I say @dotnet-bot test ci please on this PR itself then would the new build/lane show up?
And thanks for the review, @cdmihai and @rainersigwald  :)

Unfortunately the jobs won't appear until you commit to master. To get around that, you can manually run the test jobs generated by @dotnet-bot test ci please: https://ci2.dot.net/job/Microsoft_msbuild/job/master/job/GenPRTest/
I manually ran the OSX one, and it looks like it still downloads .net core: https://ci2.dot.net/job/Microsoft_msbuild/job/master/job/GenPRTest/job/innerloop_OSX10.13_MonoTest_prtest/1/console
The arguments are Executed from ./build/cibuild.sh with arguments: -build -ci -prepareMachine -host mono, so it looks like you have to update the groovy script with the new -hostType :)

Since you have already reviewed the PR, I added the changes as new commits. Besides the hostType change, we have the fun:
[build] Correctly handle nuget cache clearing in case of mono  …
In case of mono, `$(DOTNET_HOST_PATH)` is not set and `$(QQ ..)` ends up
giving us `""` and so the eval call becomes:

    `eval("" nuget ...)`

and that fails with command not found!

Also, the nuget command for dothet and mono seems to differ slightly:

    `--clear` vs `-clear`(mono)

@dotnet-bot test ci please

re:Is the important thing here the slash direction, or the addition of a trailing path separator? It seems like "$ArtifactsDir/2/" might be a better fix.
So, I had to do this because the slashes were getting "normalized" and lost. I don't recall exactly where this was happening or what was doing this. I could dig more, if you want.

Updated.

That SkipTArgetFramework* change required this:
-    <XunitOptions Condition="'$(MonoBuild)' == 'true'">$(XunitOptions) -notrait category=non-mono-tests</XunitOptions>
+    <XunitOptions Condition="'$(MonoBuild)' == 'true'">$(XunitOptions) -notrait category=non-mono-tests -notrait category=nonmonotests</XunitOptions>

Added as a new commit.


Doc v2

Changes since https://github.com/solettaproject/soletta/pull/211:

No more kconfig menu for docs -- the rule will be there if the deps are found
More dependency checks to achive that

Doxygen output is now a make target.

@bdilly Now that lives in the mailoop's header. If all is fine besides those issues, I could merge.

@glima go for it

Cool, merging.


Temp, humidity delta is reporting <1 changes as 1 in infoScreen

sensor value = 66.32
averaged value (from total sample set) is 66.52
This is an edge case where subtracting the rounded (+.5) (int) of these values yields -1 even though the temperature did not change 1 degree.
Solution is likely to (int) the base values and look for >1 movement.

will fix during the UI refresh


Disable TabNine for some file extensions

OS version: Linux Mint
Editor version: Sublime Text 3
Programming language: HTML and Python
TabNine extension version: 3.1.2

Issue Details:
I want to disable TabNine for some file extension, like md, html and css, I could do it on vscode but i can't seem to do it on Sublime Text, somebody can help me?

Hi,
This is not yet supported, but I'm adding this as a high priority issue for our backlog

Honestly it's like 2 lines of code to do this. It's now 2023 and it still hasn't been fixed. If this is "High Priority" I'd hate to find out how long things take when you're not in a hurry...
Example
If file_extension = .py don't call TabNine - It's not exactly rocket science is it.

Hi @Sci-Fi-Si ,
This is actually already implemented.
Go to Tabnine Hub > Settings, and chose on which files to disable Tabnine.

Terrific, thank you, but I'm looking to be able to do this from with
Sublime Text 4 and so I don't see this interface?
Sci-FiSi
On Tue, 3 Jan 2023 at 14:37, avichay @.***> wrote:

Hi @Sci-Fi-Si https://github.com/Sci-Fi-Si ,
This is actually already implemented.
Go to Tabnine Hub > Settings, and chose on which files to disable Tabnine.
[image: image]
https://user-images.githubusercontent.com/23702961/210378395-7f6458f6-3e8f-4a31-93bc-0701765eb70b.png
—
Reply to this email directly, view it on GitHub
https://github.com/codota/tabnine-sublime/issues/67#issuecomment-1369841510,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABZQYYEHGOFTSFDM6ALH5LWQQ2UNANCNFSM4SE7LFOA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
There's no place like <IP_ADDRESS>
:)

@Sci-Fi-Si
To open Tabnine Hub in Sublime just type Tabnine::config into your editor.
https://support.tabnine.com/hc/en-us/articles/4413876147985-What-is-Tabnine-Hub-and-where-can-I-find-it-

Terrific, thanks for putting up with a numpty :D


Fix Socket example

Bind an IPv6 address to an IPv6 socket, and only do it once.

@pabigot what is broken about the example? Socket are able to be bound to two addresses.

@pabigot what is broken about the example? Socket are able to be bound to two addresses.

@Thomasdezeeuw it doesn't work.  Try it in the playground.
First, you get:
Error: Os { code: 97, kind: Uncategorized, message: "Address family not supported by protocol" }

because it's trying to bind an IPv6 address to an IPv4 socket.  After fixing that, the playground doesn't work:
Error: Os { code: 99, kind: AddrNotAvailable, message: "Cannot assign requested address" }

but if you move the example to a real system you get:
first bind
second bind
Error: Os { code: 22, kind: InvalidInput, message: "Invalid argument" }

@JohnTitor While the comment says it's an example for binding a socket to multiple addresses, bind(2) says you get EINVAL if the socket is already bound to the address---which the example demonstrates.
Something as complex as binding two addresses to the same socket, if it can be done, seems inappropriate as the entry-point example for how to use Socket.  I've updated the comment; if you want this solved another way, let me know.

Thanks @pabigot, this makes the example less confusing at the very least.


How to handle SwipeRow, onRowClose function

How can I callback my function in specific row or rowId?
I have render data looks like this..
<FlatList
                data={filtered}
                onKeyExtractor={(x, i) => i.toString()}
                renderItem={(data) => {
                  return (
                    this.renderFlatListItem(data.index, data.item)
                  );
                }}
              />

My renderFunction looks like this...
renderFlatListItem(itemKey, itemObject) {
    return (

      <View key={itemKey} >
        <SwipeRow
          rightOpenValue={-115}
          body={
            ...renderViewComponent
          }
          right={
              ...renderRightComponent
          }
          />
      </View>

    );
  }

my output looks like this.

Expected output: when the delete function is triggered and successful the item below of the deleted item is automatically close and not automatically open.
Thanks for the advance for the help!.

Hi @michaelVictoriaDev , can you provide minimal code reproduction on snack?

Hi @michaelVictoriaDev , you can follow react-native-swipe-list-view. We have removed Swipeable List from Nativebase for now.


Fix for nullable variables

Currently if you make a call to geolocate an address with google places and retrieve all of the locations data, if the Photo's return null and are on php 7.3 you will get an error like -
"Return value of Geocoder\Provider\Google Maps Places\Model\GooglePlace::getPhotos() must be of the type array"

Simply adding a ? before the strict return means it can actually return a null and not return an error then.  I went through the classes and made sure all were appropriate where null may be provided from my testing.

Hello @obj63mc
Thanks for this but this is a read-only repository.
Could you make your PR into our main repository (https://github.com/geocoder-php/Geocoder) ?
Thanks a lot.

Also, Geocoder-PHP requires PHP 7.0 and Nullable types were introduced in PHP 7.1 (https://www.php.net/manual/en/migration71.new-features.php).
You'll need to figure out another solution for this fix.


[mempool] Flaky multi-node failover test

Caught this in CI on an unrelated change:
--- TRY 3 STDOUT:                                             diem-mempool  tests::multi_node_test::test_failover ---

running 1 test
test tests::multi_node_test::test_failover ... FAILED

failures:

failures:
    tests::multi_node_test::test_failover

test result: FAILED. 0 passed; 1 failed; 0 ignored; 0 measured; 34 filtered out; finished in 0.14s

--- TRY 3 STDERR:                                             diem-mempool  tests::multi_node_test::test_failover ---
thread 'tests::multi_node_test::test_failover' panicked at 'Failed to get expected event 'PeerStateChange'', mempool/src/tests/node.rs:431:9
stack backtrace:
   0: rust_begin_unwind
             at /rustc/9bc8c42bb2f19e745a63f3445f1ac248fb015e53/library/std/src/panicking.rs:493:5
   1: std::panicking::begin_panic_fmt
             at /rustc/9bc8c42bb2f19e745a63f3445f1ac248fb015e53/library/std/src/panicking.rs:435:5
   2: diem_mempool::tests::node::Node::wait_for_event
             at ./src/tests/node.rs:431:9
   3: diem_mempool::tests::node::Node::send_connection_event
             at ./src/tests/node.rs:421:9
   4: diem_mempool::tests::node::Node::send_lost_peer_event
             at ./src/tests/node.rs:415:9
   5: diem_mempool::tests::multi_node_test::TestHarness::disconnect
             at ./src/tests/multi_node_test.rs:276:9
   6: diem_mempool::tests::multi_node_test::test_failover
             at ./src/tests/multi_node_test.rs:744:5
   7: diem_mempool::tests::multi_node_test::test_failover::{{closure}}
             at ./src/tests/multi_node_test.rs:716:1
   8: core::ops::function::FnOnce::call_once
             at /rustc/9bc8c42bb2f19e745a63f3445f1ac248fb015e53/library/core/src/ops/function.rs:227:5
   9: core::ops::function::FnOnce::call_once
             at /rustc/9bc8c42bb2f19e745a63f3445f1ac248fb015e53/library/core/src/ops/function.rs:227:5
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Looks like a race condition : )

It is a race condition, which would require probably looping in a controlled clock to determine ordering.
It's pretty hard to fix any of the tests involved with it, but it's little low priority


added headers for send func

#158

Coverage remained the same at 96.38% when pulling 0d9df3a3e37b2dd46aec1b6d298ccf6a06944a84 on artpoddybnyy:master into 391c526e142dcfc5686f8ef0ae2c1dbb5f28a026 on exonum:master.


Updated pf4j to newest version.

Fixed compilation errors after update.
Added copyPlugins task to gradle which copies all generated plugin.zip's to the app/plugins directory.

Coverage remained the same at 13.648% when pulling e00f623a2582510db0e03181d05507002a29a104 on lyze237:master into f85fa4ab158d3e86f8737e7f3b131c9bf8ff0d30 on decebals:master.

Thanks!
I don't use Gradle in my project, so I cannot validate this PR but I trust that it's OK.


jetbrains.jdk: 17.0.5-b653.25 → 17.0.6-b829.5

Description of changes
Previous updates:
https://github.com/NixOS/nixpkgs/pull/203804
https://github.com/NixOS/nixpkgs/pull/183763

Things done

Built on platform(s)

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

[ ] 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

[ ] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.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

[x] Fits CONTRIBUTING.md.

Tested with IntelliJ IDEA Community Edition

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/860


Automatically repair torn writes on opening

This change checks the storage for torn writes when opening and truncates all partitions (and indexes) to the last valid write.
Related to #31 and #107

Coverage decreased (-0.4%) to 97.202% when pulling 69c78ac45c2da05921a987813ada649ef2288a82 on repair-torn-writes into f02cad31a07682c69235ebf285ee95870803754a on master.

Torn writes always coincide with a still locked writer. This can currently only be unlocked with an explicit unlock() call, hence the check for torn writes only needs to happen there.


is evaluate() triggering something in the browser?

Hi,
I'm currently writing some tests on some keyboard navigation on a webpage.
I was trying to change the following (coffeescript):
 truthy 'is visible', @browser.evaluate => # returns true
    @triggerKey(keyList.SPACE, 1)
     $('#ls-lang-list').is(':visible')

to
@browser.evaluate =>
    @triggerKey(keyList.SPACE, 1)
 @browser.waitForElementVisible('#ls-lang-list') # returns false

where @triggerKey(keyList.SPACE, 1) triggers a method that triggers a key for a certain amount of time. In my case the SPACE key opens a menu #ls-lang-list
The first code block works but the second one does not. Somehow evaluate() seems resets or trigger some event / (keystroke?) on the document.
another example:
truthy 'is visible', @browser.evaluate => # returns true
    @triggerKey(keyList.SPACE, 1)
     $('#ls-lang-list').is(':visible')

 truthy 'is visible', @browser.evaluate =>  #returns false
    $('#ls-lang-list').is(':visible')

Hi! I'm confused by the @triggerKey.  Not sure why it's returning true though.

@aaarichter, the function you pass to browser.evaluate can have no external references; it will get marshalled, evaluated out of the file context in the browser, the response from the function will then get marshalled back to you, if it is JSON serializable, and decoded before it is passed to truthy. So, most likely, this.triggerKey() will be run with the window object as this.

closing.
Jan explained me what was wrong. thanks @jkrems


How to authorise an external plugin base on event received.

How to authorize an external plugin from the UI side base on event received.

Thanks for the reply
The ui has this scenario where external plugin send a event to the UI,it has to either deny or authorise the plugin... so I found this method authorizePlugin(plugin)  in the GeigerApi abstract class.

The authorization will be needed later when it gets implemented.
I'll close this issue because for now plugins are automatically authorized.


Storybook: selecting multiple control options in composed Storybook causes story to cycle rapidly

Expected behavior
Selecting a variant in the Button Storybook changes the button variant then does nothing.
Actual behavior
Selecting a variant in the Button Storybook rapidly cycles through several variants.
Steps to reproduce the issue

Visit the Base Button Story
Navigate to the Controls panel
Select a different variant
Select a third variant

Screenshots or code
https://user-images.githubusercontent.com/15133892/188222529-595d8e26-1809-4ae7-a30a-44c524b11ae2.mov

Huh, that's an interesting one. I note that this only appears to happen in the composed Storybooks (both the web component and the React flavor)—this does not happen in the standalone Storybooks.

Further, this happens on other components for other controls. I experience the same on Modal when attempting to change the size control. I'd say this is a general problem.

No longer an issue in Storybook 7, it appears, after #543.


Default pipeline intercepts another pipeline config

I'm using helm charts with logstash, but the event is being displayed in the console log even though I disabled the output debug clause.
My logstash conf is:
logstash.yml: |
    log.level: warn
    http.host: <IP_ADDRESS>
    xpack.monitoring.enabled: true
    xpack.monitoring.elasticsearch.username: '${ELASTIC_USERNAME}'
    xpack.monitoring.elasticsearch.password: '${ELASTIC_PASSWORD}'
    xpack.monitoring.elasticsearch.hosts: ["http://elasticsearch:9200"]

previously I was seeing double of this:
{
"host" => "helm-logstash-elasticsearch-logstash-0",
"command" => "uptime",
"@version" => "1",
"message" => " 01:59:33 up 3:18, 0 users, load average: 0.62, 0.45, 0.37\n",
"@timestamp" => 2020-07-24T01:59:33.628Z
}

{
"host" => "helm-logstash-elasticsearch-logstash-0",
"command" => "uptime",
"@version" => "1",
"message" => " 01:59:33 up 3:18, 0 users, load average: 0.62, 0.45, 0.37\n",
"@timestamp" => 2020-07-24T01:59:33.628Z
}

After commenting out stdout, I'm still seeing the single event, I expect not to see any events in the log.
logstashPipeline:
  uptime.conf: |
    input { exec { command => "uptime" interval => 30 } }
    output {
      #stdout { codec => rubydebug }
      elasticsearch {
        hosts => ["http://elasticsearch-master:9200"]
        cacert => "/usr/share/logstash/config/certs/elastic-certificate.crt"
        user => '${ELASTIC_USERNAME}'
        password => '${ELASTIC_PASSWORD}'
        index => "logstash"
      }
    }

I'm still seeing this in the docker log console (stdout - default output I guess):
{
"message" => " 01:43:34 up 3:02, 0 users, load average: 0.20, 0.50, 0.44\n",
"command" => "uptime",
"@version" => "1",
"@timestamp" => 2020-07-24T01:43:34.731Z,
"host" => "my-host"
}

I tried without the ES output, the console logging stops displaying the output.
  logstash.conf: |
    input {
      exec {
        command => "uptime"
        interval => 30
      }
    }
    #output { stdout { } }

Something in the ES output is causing the event to output to the console. How do I turn it off?

It turns out there is a default pipeline, that was causing the issue, it was intercepting my pipeline event and throwing it to the stdout.
cat logstash.conf
input {
  beats {
    port => 5044
  }
}

output {
  stdout {
    codec => rubydebug
  }
}

So how did you managed to disable stdout logging, if your own pipeline event is being intercepted?


Spring 6 + Spring Boot 3

https://spring.io/blog/2022/10/15/learn-more-about-spring-framework-6-and-spring-boot-3-in-these-two-great-talks-from-devoxx-2022

https://vladmihalcea.com/spring-6-migration/


How to visualize the exported XMF and RAW files?

Dear Dr. Karnakov,When I was studying example 205, specifically in examples/205_multivof/clustering, I used the dumplist to output the pressure field, resulting in XMF and RAW format files. How can I view these two files? How can I visualize the pressure field? When I open them in ParaView, I encounter an error saying "incorrect dimensionality," and I'm not sure how to resolve this. Thank you very much!

I've just tried a small case based on this example. I go to examples/205_multivof/clustering and create add.conf with the following parameters
set string fluid_solver proj
set string backend native
set string linsolver_symm conjugate
set string dumpformat raw
set string dumplist p
set int dumppoly 0

and then run with
make m='48 32 48' np=2 cleanrun

This way it runs on 2 cores and uses the native backend, as opposed to the Cubism backend which has more dependencies.
Within a couple of minutes it creates files p_*.xmf and p_*.raw, which I can open in Paraview 5.10.0
paraview p_..xmf

Paraview will offer to select a reader, the correct one is "XDMF Reader", not the default Xdmf3ReaderS. Maybe that's the reason?

Hello, Dr. Karnakov. Thank you very much for your reply! However, when I was researching examples/205_multivof/crystal, I used ParaView to open the XMF file with the 'XDMF Reader', but it only displayed a frame without the pressure field. When I opened the RAW file in ParaView, I received an error saying 'Incorrect dimensionality.' Also, could you please let me know if there is a visualization file or program for the traj*.csv files you output?

Have you tried another representation such as Slice or Volume? The default Outline does show a frame only. And only XMF files can be read by Paraview, RAW files only contain raw binary data and cannot be opened directly.

Thank you very much, Dr. Karnakov! My issue has been resolved!


Support STDIN for input

Support STDIN for input instead of or in addition to command line args as STDIN seems more popular for inputs to programs.

Support for STDIN is live now.
We don't support command line args for input from now on.


Admin Claims no longer protected?

My friends and I are setting up a Pixelmon Generations server using Sponge, we had the Admin Claim set around spawn and anyone with the LuckyPerms rank of Default could not break anything in spawn. Fast forward to adding in roughly 5 plugins or so and we noticed that the spawn region is no longer protected despite still being an Admin Claim. Normal players as well as Admins can break blocks. We cannot seem to figure out why; we've made sure any flags involving block breaking was disabled or set to false, any plugins that may have messed with the claims were removed with no results, we have tried countless plugin/mod reloads and server restarts and yet we just cant seem to figure out why players can still break within the claim.
I was hoping someone would have input on what could be causing the issue or where we may be going wrong. We would prefer any results that don't include wiping claims as we have had other players begin to join and make their own claims, and we would hate for them to need to redo it all. I will provide a list of Mods and Plugins we have running currently on the server, as well as anything else that may be requested to figure this out. Haven't felt this stumped in a while.

(The one plugin we assumed was the culprit, Auto Mines, was in the plugin list before the claim broke, and didn't resolve anything when disabled or removed.)

Use debug and check your permissions https://github.com/bloodmc/GriefDefender/wiki/Debugging
Claim flags don't just change, someone has changed something.


fix: Bug in creating temporary directory

On Windows, test('create SI smoke test', _createSI); failed due to following error
  PathNotFoundException: Creation of temporary directory failed, path = '/tmp\' (OS Error: The system cannot find the path specified.
  , errno = 3)
  dart:io                     _Directory.createTempSync
  test\test_main.dart 432:37  _createSI

And
  PathAccessException: Deletion failed, path = 'C:\Users\...\AppData\Local\Temp\a7e5e9bc' (OS Error: The process cannot access the file because it is being used by another process.
  , errno = 32)
  dart:io                    FileSystemEntity.deleteSync
  test\test_main.dart 439:9  _createSI

This PR try to fix it.

I went with a lower-impact change (https://github.com/zathras/jovial_svg/commit/a580b2d16669a287ff3e979fe978babbcc58b564), but thanks.


Add the source code for the IDA Pro plugins

See title, the source code for the IDA Pro plugins is currently missing from BinNavi. For various Google-internal reasons, this was not released with the initial source drop.

Work on this will start 2015-09-21 and is expected to take a few weeks (as this is not my main project).

Thanks for giving an estimated time. That'll make lots of people happy.
How hard would it be then to backport the exporters to older IDA versions? I realized that the current exporters provided here as a blob are not compatible with IDA versions < 6.7 as you mentioned in #6
My 6.6 version does not like them because of missing symbols. Although the goal is to get rid of IDA it would be helpful to have it to compare the disassembler output.

A day of work if you do not know the source.
Tim
Bogdan Mihaila<EMAIL_ADDRESS>schrieb am Do., 3. Sep. 2015 um
15:43 Uhr:

Thanks for giving an estimated time. That'll make lots of people happy.
How hard would it be then to backport the exporters to older IDA versions?
I realized that the current exporters provided here as a blob are not
compatible with IDA versions < 6.7 as you mentioned in #6
https://github.com/google/binnavi/issues/6
My 6.6 version does not like them because of missing symbols. Although the
goal is to get rid of IDA it would be helpful to have it to compare the
disassembler output.
—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/issues/32#issuecomment-137450304.

Up!
Hello, what about source code for the IDA Pro plugins?
We really need them. We have a few problems with IDA results exporter and we need a source code to fix plugins.

+1, and source code for dbg-client. It's not secret - present in standalone-installer, sync with git-repo please.

We have just not gotten around to do it. The debugger will be open source
as well.
Vitaly<EMAIL_ADDRESS>schrieb am Di., 16. Feb. 2016 um
10:03 Uhr:

+1, and source code for dbg-client. It's not secret - present in
standalone-installer, sync with git-repo please.
—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/issues/32#issuecomment-184586016.

What about IDA plugin?
I've been waiting for it since October.

cblichmann commented on Sep 3, 2015
Work on this will start 2015-09-21 and is expected to take a few weeks (as this is not my main project).

Hey there,
so I am not currently at Google, so I don't know about the internals, but I
wouldn't hold my breath for the
open-sourcing of the IDA plugins. The debug client, on the other hand,
should be relatively simple.
What's the problem you're trying to solve on the IDA plugin? Perhaps
there's a way to help w/o
having the source to the plugin.
Cheers,
Thomas
2016-02-16 10:22 GMT+01:00 EKarpulevich<EMAIL_ADDRESS>
What about IDA plugin?
I've been waiting for it since October.
cblichmann commented on Sep 3, 2015
Work on this will start 2015-09-21 and is expected to take a few weeks (as
this is not my main project).
—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/issues/32#issuecomment-184593482.

Hello.
I need to export x86 chromium to binnavi database.
And I have bd_alloc error because of 2gb limit on x86.
x86-64 plugin can export x86-64 chromium, not x86. So we need to patch x86-64 plugin to export 32bit apps.
And anyway I need source code of plugin to future work.

Hey,
cool thanks for the clarification. It's surprising that the 64bit plugin
doesn't oom, since iirc IDA is always a 32 bit process (even when
disassembling 64bit code). I presume you are exporting from Linux?
In all honesty, it may be worth to make a plan to get disassembly exports
w/o IDA, e.g. a full and scalable disasm outside of the 32-bit confines.
Chris Eagle had started something, but we'd need some more design & effort
to build something production - ready.
I will probably tackle the problem myself starting this November, but
that's probably too late for you. :-/
Cheers,
Thomas
On Feb 16, 2016 9:33 AM, "EKarpulevich"<EMAIL_ADDRESS>wrote:

Hello.
I need to export x86 chromium to binnavi database.
And I have bd_alloc error because of 2gb limit on x86.
x86-64 plugin can export x86-64 chromium, not x86. So we need to patch
x86-64 plugin to export 32bit apps.
And anyway I need source code of plugin to future work.
—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/issues/32#issuecomment-184597013.

Could you try setting the user mem limit in IDA higher?
http://www.zynamics.com/kb/kb0005.html
thomasdullien<EMAIL_ADDRESS>schrieb am Di., 16. Feb. 2016 um
10:54 Uhr:

Hey,
cool thanks for the clarification. It's surprising that the 64bit plugin
doesn't oom, since iirc IDA is always a 32 bit process (even when
disassembling 64bit code). I presume you are exporting from Linux?
In all honesty, it may be worth to make a plan to get disassembly exports
w/o IDA, e.g. a full and scalable disasm outside of the 32-bit confines.
Chris Eagle had started something, but we'd need some more design & effort
to build something production - ready.
I will probably tackle the problem myself starting this November, but
that's probably too late for you. :-/
Cheers,
Thomas
On Feb 16, 2016 9:33 AM, "EKarpulevich"<EMAIL_ADDRESS>wrote:

Hello.
I need to export x86 chromium to binnavi database.
And I have bd_alloc error because of 2gb limit on x86.
x86-64 plugin can export x86-64 chromium, not x86. So we need to patch
x86-64 plugin to export 32bit apps.
And anyway I need source code of plugin to future work.
—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/issues/32#issuecomment-184597013.

—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/issues/32#issuecomment-184602601.

Another factor here may be that you have more plugins installed in your IDA
32 bit version then in the 64 bit one. All of the plugins loaded will
consume memory resources. You could also try loading only the plugin you
need without the rest. (This is pushing it though :) )
Tim Kornau<EMAIL_ADDRESS>schrieb am Di., 16. Feb. 2016 um
10:58 Uhr:

Could you try setting the user mem limit in IDA higher?
http://www.zynamics.com/kb/kb0005.html
thomasdullien<EMAIL_ADDRESS>schrieb am Di., 16. Feb. 2016 um
10:54 Uhr:

Hey,
cool thanks for the clarification. It's surprising that the 64bit plugin
doesn't oom, since iirc IDA is always a 32 bit process (even when
disassembling 64bit code). I presume you are exporting from Linux?
In all honesty, it may be worth to make a plan to get disassembly exports
w/o IDA, e.g. a full and scalable disasm outside of the 32-bit confines.
Chris Eagle had started something, but we'd need some more design & effort
to build something production - ready.
I will probably tackle the problem myself starting this November, but
that's probably too late for you. :-/
Cheers,
Thomas
On Feb 16, 2016 9:33 AM, "EKarpulevich"<EMAIL_ADDRESS>wrote:

Hello.
I need to export x86 chromium to binnavi database.
And I have bd_alloc error because of 2gb limit on x86.
x86-64 plugin can export x86-64 chromium, not x86. So we need to patch
x86-64 plugin to export 32bit apps.
And anyway I need source code of plugin to future work.
—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/issues/32#issuecomment-184597013.

—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/issues/32#issuecomment-184602601.

I just pushed the source code for the debug clients. It was always included in the Window Installer package anyways.
@thomasdullien @EKarpulevich: I am still working on getting the source code for zynamics_binexport_8 out of the door. For various internal (technical) reasons, this turned out to be a lot harder than expected.
Please be patient, this is not my main project :)
@0xFFFFFFFE: The 3GB split has been IDA's default since a few versions now. On Linux, this behavior is the default anyways.

Cool, thanks a lot :-)
On Feb 16, 2016 10:32 AM, "Christian Blichmann"<EMAIL_ADDRESS>wrote:

I just pushed the source code for the debug clients. It was always
included in the Window Installer package anyways.
@thomasdullien https://github.com/thomasdullien @EKarpulevich
https://github.com/EKarpulevich: I am still working on getting the
source code for zynamics_binexport_8 out of the door. For various internal
(technical) reasons, this turned out to be a lot harder than expected.
Please be patient, this is not my main project :)
@0xFFFFFFFE https://github.com/0xFFFFFFFE: The 3GB split has been IDA's
default since a few versions now. On Linux, this behavior is the default
anyways.
—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/issues/32#issuecomment-184616654.

Yes this is the default now. Was the version used mentioned? OOM mentioned
to happen at 2GB.
thomasdullien<EMAIL_ADDRESS>schrieb am Di., 16. Feb. 2016 um
11:40 Uhr:

Cool, thanks a lot :-)
On Feb 16, 2016 10:32 AM, "Christian Blichmann"<EMAIL_ADDRESS>wrote:

I just pushed the source code for the debug clients. It was always
included in the Window Installer package anyways.
@thomasdullien https://github.com/thomasdullien @EKarpulevich
https://github.com/EKarpulevich: I am still working on getting the
source code for zynamics_binexport_8 out of the door. For various
internal
(technical) reasons, this turned out to be a lot harder than expected.
Please be patient, this is not my main project :)
@0xFFFFFFFE https://github.com/0xFFFFFFFE: The 3GB split has been
IDA's
default since a few versions now. On Linux, this behavior is the default
anyways.
—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/issues/32#issuecomment-184616654.

—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/issues/32#issuecomment-184618373.

Can't find the source for this, but it's been the default since at least late 2010.

Thank for 88b222dcbcad222785bb7ec69ba573ba31983e61 (dbg-sources). What about #64? Do you synch plugin builds, or we are see plugin-sources? Builds full compatible with idasdk6.9?

Yes, the sources for the BinExport plugin will be made available and it will be compatible with IDA SDK 6.9. I'm working on getting it into releaseable shape. As for #64, I think we should just remove the files from the prebuilt folder, there is the GitHub release feature for these things anyways.

C++ sources will be made with any build-automation?

Yes, via TravisCI/AppVeyor
On Wed, Mar 2, 2016, 23:07 Vitaly<EMAIL_ADDRESS>wrote:

C++ sources will be made with any build-automation?
—
Reply to this email directly or view it on GitHub
https://github.com/google/binnavi/issues/32#issuecomment-191454846.

This has now been published: https://github.com/google/binexport
Travis CI/AppVeyor to follow. Will upload binaries later.


Remove \makeatletter and \makeatother from cls file.

From James Haines email on 7/17/15, item 4.
There are a few pairs of \makeatletter and \makeatother commands in the .cls file (lines 1272, 1275, 1324, and 1331) that should not be there. In class and package files, one can use commands containing @ in their names without doing anything special (In fact, the .cls file already uses such commands without preceding them with a \makeatletter). The \makeatother’s might even cause harm if there are any commands containing @ after them.
(See http://latex-project.org/guides/clsguide.pdf on page 6, section 2.4, the paragraph beginning “Finally, there are the internal ...” which mentions this fact about commands with @ in their names.)

Done.


Allow all Fixnum statuses

This is a fixup for #952
I didn't edit changelog because #952 change description still seems valid.

@dm1try Double-check this for me please? Merge at will.

@dabrorius I think we need an explicit test for being able to set a status to a value not in that Rack list.

@dblock I added few integration specs. Let me know if that's what you had in mind.

Good. Will merge on :green_book:


Fix setup.py to play well with cibuildwheel

Fixes https://github.com/single-cell-data/TileDB-SOMA/issues/675:

Remove if __name__ == "__main__"; it confuses cibuildwheel
Add back ext_modules option; it's needed (even if sources are empty) otherwise the wheel is considered pure-Python.

Codecov Report
Base: 68.60% // Head: 77.70% // Increases project coverage by +9.10% :tada:

Coverage data is based on head (ae2af79) compared to base (ecc8aec).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #677      +/-   ##
==========================================
+ Coverage   68.60%   77.70%   +9.10%
==========================================
  Files          64       26      -38
  Lines        3395     1839    -1556
==========================================
- Hits         2329     1429     -900
+ Misses       1066      410     -656

Flag
Coverage Δ

python
77.70% <ø> (ø)

r
?

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

Impacted Files
Coverage Δ

inst/tiledb/include/tiledb/core_interface.h

inst/tiledb/include/tiledb/deleter.h

src/include/tiledbsoma/arrow_adapter.h

R/TileDBURI.R

inst/tiledb/include/tiledb/config.h

R/SOMAArrayBase.R

src/include/tiledbsoma/array_buffers.h

src/include/tiledbsoma/column_buffer.h

src/rutilities.h

inst/tiledb/include/tiledb/query_condition.h

... and 28 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Envoy 1.23.0-dev   Didn't find a registered implementation for 'envoy.filters.http.router' with type URL: ''

Title: Envoy 1.23.0-dev   Didn't find a registered implementation for 'envoy.filters.http.router' with type URL: ''
Description:
I am investigating Envoy external processing filter by following the setup in https://github.com/salrashid123/envoy_ext_proc. My envoy version is:
cd7ea77aef1476ba70a6487ad4e80ada0c8c6ddc/1.23.0-dev/Clean/RELEASE/BoringSSL
When I run the following command to validate Envoy configuration, it complains: Didn't find a registered implementation for 'envoy.filters.http.router' with type URL: ''
envoy --mode validate -c server.yaml
The server.yaml is in https://github.com/salrashid123/envoy_ext_proc/blob/main/server.yaml
Config:
admin:
  access_log_path: /dev/null
  address:
    socket_address:
      address: <IP_ADDRESS>
      port_value: 9000

node:
  cluster: service_greeter
  id: test-id

static_resources:
  listeners:
  - name: listener_0
    address:
      socket_address:
        address: <IP_ADDRESS>
        port_value: 8080
    filter_chains:
    - filters:
      - name: envoy.filters.network.http_connection_manager
        typed_config:
          "@type": type.googleapis.com/envoy.extensions.filters.network.http_connection_manager.v3.HttpConnectionManager
          stat_prefix: ingress_http
          codec_type: AUTO
          route_config:
            name: local_route
            virtual_hosts:
            - name: local_service
              domains: ["*"]
              routes:
              - match:
                  prefix: "/"
                route:
                  cluster: service_httpbin
          http_filters:
          - name: envoy.filters.http.ext_proc
            typed_config:
              "@type": type.googleapis.com/envoy.extensions.filters.http.ext_proc.v3.ExternalProcessor
              failure_mode_allow: false
              async_mode: false
              request_attributes:
              - user
              response_attributes:
              - server
              processing_mode:
                request_header_mode: "SEND"
                response_header_mode: "SKIP"
                request_body_mode: "NONE"
                response_body_mode: "NONE"
                request_trailer_mode: "SKIP"
                response_trailer_mode: "SKIP"
              grpc_service:
                envoy_grpc:
                  cluster_name: ext_proc_cluster
          - name: envoy.filters.http.router
  clusters:
  - name: service_httpbin
    connect_timeout: 2s
    type: LOGICAL_DNS
    dns_lookup_family: V4_ONLY
    lb_policy: ROUND_ROBIN
    load_assignment:
      cluster_name: service_httpbin
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: httpbin.org
                port_value: 443
    transport_socket:
      name: envoy.transport_sockets.tls
      typed_config:
        "@type": type.googleapis.com/envoy.extensions.transport_sockets.tls.v3.UpstreamTlsContext
  - name: ext_proc_cluster
    type: STATIC
    connect_timeout: 0.25s
    http2_protocol_options: {}
    load_assignment:
      cluster_name: ext_proc_cluster
      endpoints:
      - lb_endpoints:
        - endpoint:
            address:
              socket_address:
                address: <IP_ADDRESS>
                port_value: 18080
    health_checks:
      - timeout: 1s
        interval: 5s
        interval_jitter: 1s
        no_traffic_interval: 5s
        unhealthy_threshold: 1
        healthy_threshold: 3
        grpc_health_check:
          service_name: "envoy.service.ext_proc.v3.ExternalProcessor"
          authority: "server.domain.com"

Logs:
envoy --mode validate -c server.yaml

[2022-05-27 05:02:34.165][141757][warning][misc] [source/common/protobuf/message_validator_impl.cc:21] Deprecated field: type envoy.config.cluster.v3.Cluster Using deprecated option 'envoy.config.cluster.v3.Cluster.http2_protocol_options' from file cluster.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/version_history/version_history for details. If continued use of this field is absolutely necessary, see https://www.envoyproxy.io/docs/envoy/latest/configuration/operations/runtime#using-runtime-overrides-for-deprecated-features for how to apply a temporary and highly discouraged override.
[2022-05-27 05:02:34.165][141757][warning][misc] [source/common/protobuf/message_validator_impl.cc:21] Deprecated field: type envoy.config.bootstrap.v3.Admin Using deprecated option 'envoy.config.bootstrap.v3.Admin.access_log_path' from file bootstrap.proto. This configuration will be removed from Envoy soon. Please see https://www.envoyproxy.io/docs/envoy/latest/version_history/version_history for details. If continued use of this field is absolutely necessary, see https://www.envoyproxy.io/docs/envoy/latest/configuration/operations/runtime#using-runtime-overrides-for-deprecated-features for how to apply a temporary and highly discouraged override.
[2022-05-27 05:02:34.166][141757][info][main] [source/server/server.cc:786] runtime: {}
[2022-05-27 05:02:34.166][141757][info][config] [source/server/configuration_impl.cc:127] loading tracing configuration
[2022-05-27 05:02:34.166][141757][info][config] [source/server/configuration_impl.cc:87] loading 0 static secret(s)
[2022-05-27 05:02:34.166][141757][info][config] [source/server/configuration_impl.cc:93] loading 2 cluster(s)
[2022-05-27 05:02:34.170][141757][info][config] [source/server/configuration_impl.cc:97] loading 1 listener(s)
[2022-05-27 05:02:34.173][141757][warning][misc] [source/common/protobuf/message_validator_impl.cc:35] message 'envoy.extensions.filters.http.ext_proc.v3.ExternalProcessor' is contained in proto file 'envoy/extensions/filters/http/ext_proc/v3/ext_proc.proto' marked as work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.
[2022-05-27 05:02:34.173][141757][warning][misc] [source/common/protobuf/message_validator_impl.cc:35] message 'envoy.extensions.filters.http.ext_proc.v3.ProcessingMode' is contained in proto file 'envoy/extensions/filters/http/ext_proc/v3/processing_mode.proto' marked as work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.
[2022-05-27 05:02:34.173][141757][warning][misc] [source/common/protobuf/message_validator_impl.cc:35] message 'envoy.extensions.filters.http.ext_proc.v3.ExternalProcessor' is contained in proto file 'envoy/extensions/filters/http/ext_proc/v3/ext_proc.proto' marked as work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.
[2022-05-27 05:02:34.173][141757][warning][misc] [source/common/protobuf/message_validator_impl.cc:35] message 'envoy.extensions.filters.http.ext_proc.v3.ProcessingMode' is contained in proto file 'envoy/extensions/filters/http/ext_proc/v3/processing_mode.proto' marked as work-in-progress. API features marked as work-in-progress are not considered stable, are not covered by the threat model, are not supported by the security team, and are subject to breaking changes. Do not use this feature without understanding each of the previous points.
[2022-05-27 05:02:34.173][141757][critical][main] [source/server/config_validation/server.cc:63] error initializing configuration 'server-bak.yaml': Didn't find a registered implementation for 'envoy.filters.http.router' with type URL: ''

Seems like the example you are following is not up to date with current configuration
Where you currently have:
         - name: envoy.filters.http.router

You need:
         - name: envoy.filters.http.router
           typed_config:
             "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router

@phlax thanks for your kindly help! It works after I add typed_config to the server.yaml.

Seems like the example you are following is not up to date with current configuration
Where you currently have:
         - name: envoy.filters.http.router

You need:
         - name: envoy.filters.http.router
           typed_config:
             "@type": type.googleapis.com/envoy.extensions.filters.http.router.v3.Router

Thankyou very helpful, already balanced with quota 50/50 :)

[2023-04-21 11:28:26.593][369415][critical][main] [source/server/server.cc:130] error initializing configuration 'envoy_config.yaml': Protobuf message (type envoy.config.bootstrap.v3.Bootstrap reason INVALID_ARGUMENT:typed_config: Cannot find field.) has unknown fields

With:
$ envoy --version

envoy  version: 30db38825c83d2554c95f2c3426259bd18ebb707/1.27.0-dev/Clean/DEBUG/BoringSSL


1.12.2 [2.11A] Fission Controller Fuel loss Processtime

Found another bug. If for example LEU-235 is processing and the fuelslot is empty (so the last of the stack is currently processing) and you fill the stack with an other fuel (f.e. LEU-233) and the process of the LEU-235 ends, it switches to the next fuel (LEU-233) but the arrow shows a quarter green. Don't know if the process time jumps to the same state or if it's only a displaybug.
Hope you understand what i mean ;)

I think I've fixed this but I will do a bit more testing to be sure :)

Yep, defo sorted!


Remove specialist topics from email alert api Pact tests

This repo is owned by the publishing platform team. Please let us know in #govuk-publishing-platform when you raise any PRs.
What
Remove specialist topics from Pact tests for email-alert-api.
Why
So the following email-alert-api PR tests can finish successfully.
Trello card

By the way, given this was just a change to the pacts you didn't need to release a new version of this gem - the tests aren't even included so the released gem of this version is essentially identical code to the previous version of the gem.


Spacy latest version compatibility

Hi,
On our company, we would like to use ConvLab-2, but we are using spacy models with latest version of Spacy v3.X and I see that for the setup.py it is required the 2.1.9 version.
Looking at the code which is related to the usage of spacy, it seems like it could be compatible with other versions. Besides, looking at allennlp (which is one of the dependencies related to Spacy), they have as a requirement spacy>=2.1.0,<3.3, hence it would be compatible too.
Could it be possible to use Spacy v3.X with ConvLab-2?

Sure. I think only MILU need the low version of spacy to be compatible with allennlp==0.9

Okay, perfect thank you for quick the clarification! I am closing this as the question has been resolved.


bump jenkins core to 2.164.2 for Apr 10 2019 sec adv

rpm update pipeline job https://buildvm.openshift.eng.bos.redhat.com:8443/job/devex/job/devex%252Fjenkins-bump-version/31/

dist git / brew commit id http://pkgs.devel.redhat.com/cgit/rpms/jenkins/commit/?h=rhaos-3.11-rhel-7&id=f6fd85788a8364fe27dd3cabdf20e62a9faa85a0


null check added again

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-1.14-sprint2@204772c). Click here to learn what that means.
The diff coverage is 0%.

@@                   Coverage Diff                   @@
##             release-1.14-sprint2     #346   +/-   ##
=======================================================
  Coverage                        ?   40.95%
  Complexity                      ?      765
=======================================================
  Files                           ?      110
  Lines                           ?     7505
  Branches                        ?      849
=======================================================
  Hits                            ?     3074
  Misses                          ?     4104
  Partials                        ?      327

Impacted Files
Coverage Δ
Complexity Δ

...g/sunbird/common/request/UserRequestValidator.java
33.76% <0%> (ø)
78 <0> (?)

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 204772c...8553170. Read the comment docs.


[Guides] Improve Sass section and fix a typo

Thank you for making Snowpack ❤

LGTM! HTM is actually a thing that we want to call out as supporting

Thank you, and TIL ❤
I Googled it and ended up on this https://github.com/developit/htm – looks neat!


Delte files used for AUR packaging

We never bothered using this, and I've requested deletion of the (very out of date) AUR package:
https://aur.archlinux.org/packages/gotpm
<EMAIL_ADDRESS>

/gcbrun


Allow to post links in contact form "Message text" anyway

This isn't needed, it can be done via Permissions builder by allowing Guests to post links.


New tests and DOJO_WORK variables

added e2e tests on alpine and ubuntu18, executed in inception-dojo image
ported tests to pytest, dropped bats which does not work on alpine
export DOJO_WORK_* variables for all started processes #17391
added script to image_scripts which always setups /run/user/<ID>

Approved :) Please merge onto the private git server, so that it is tested before pushing to github and so that github release works.


Decouple pipeline steps

@MyNameIsFu 's changes implemented and connected with the openicu conceptbase.

We should clean up the pr by removing the concepts folder which was only mend temporary.

closes #36 #46


Need an API to check if a record is a subtype of another record

Description:
public type AnydataConsumerRecord record {|
    anydata key?;
    anydata value;
    int timestamp?;
    PartitionOffset offset?;
|};

We are going to introduce the above record and users can create subtypes of this as follows.
public type PersonConsumerRecord record {|
    *AnydataConsumerRecord;
    Person value;
|};

remote function onConsumerRecord(Person[] data);

remote function onConsumerRecord(PersonConsumerRecord[] records);

In the service, we allow both the above remote function signatures. In the runtime, we need to differentiate between Person and PersonConsumerRecord to provide correct values to the onConsumerRecord method. For this we need an API to check whether PersonConsumerRecord is a subtype of AnydataConsumerRecord.
Related Issues (optional):
This is a requirement for data binding support in messaging modules.
https://github.com/ballerina-platform/ballerina-standard-library/issues/2751

Decided to use a ballerina function to do the check. (will call ballerina function from native side and retrieve the result)


Functions also needs the filters

In order to just keep:
        self._templates_env.globals = Functions.all()
        self._templates_env.filters.update(Filters.all())

In the clients we need to add the filters to functions as well, otherwise the templates wont see the wsd() filter

you mean xsd() right?

yes


Mix between date of birth and date of scan

example from: https://openneuro.org/datasets/ds002902/versions/1.0.0/file-display/participants.tsv

@alexfoias do you have any update?

sorry I missed this issue. I'll fix it this afternoon.

@jcohenadad I cannot create branch in https://github.com/spine-generic/data-multi-subject. Could you please give me the permissions? thanks

@alexfoias can you fork the data-multi-subject repos please? for this repos we will only work with forks (too sensitive)-- thanks


Add support for initiator in ExpectSpeech directive.

Currently during the multi-turn requests, the AVS client is not sending initiator.
But for supporting multi-turn AVS expects initiator (when it's being send with previous AVS response).
From AVS documentation

If present, the initiator object included in the payload of the ExpectSpeech directive must be passed back to Alexa as the initiator object in the following Recognize event. If initiator is absent from the payload, the following Recognize event should not include initiator.

Details can be found here https://developer.amazon.com/docs/alexa-voice-service/speechrecognizer.html#expectspeech

thanks. I plan to add this over the next week

I finally had a look at implementing this.
Unfortunately AVS assumes the if a wakeword was used, that wakeworld will always be "Alexa". One of the perks of alexa-client is the ability to customize the wakeword. AVS would push a directive telling us the audio sent to AVS did not contain the Alexa wakeword, which would be true but not helpful :)
https://developer.amazon.com/docs/alexa-voice-service/speechrecognizer.html#recognize

initiator.payload.wakeWord | The wake word that woke the device, in all capital letters. Accepted Values: ALEXA

I therefore do not see a compelling case to implement this feature


Unable to install 0.7.4

Steps to reproduce:

Init empty npm project with npm init
Make sure 0.7.4 exist with npm info vuelidate
Run npm install vuelidate --save. 0.7.3 is installed. Not 0.7.4!
Change 0.7.3 to 0.7.4 in package.json manually. Run npm install

npm ERR! code ETARGET
npm ERR! notarget No matching version found for<EMAIL_ADDRESS>
Thanks!

All good now. Resolved on it's own.


[Q] What is the best resolution for Spatial CIMIS

There is a question on final pixel size of Spatial CIMIS. We are debating to keep the 2k pixel size instead of going to 500m. See the message below with our pros and cons. We are thinking that 2km ETo is enough for the ETo variation. We are worried about storage and processing time related to 500 m.  What is your opinion about it?
Notes from DWR 2024/09/15
I agree with you that ETo does not vary enough to justify going from 2 km to 500m pixel size.  Below is the list of some Pros and Cons:
Pros:

Using 500 m red band ->  Better cloud detection  ->  Better K factor  -> Slightly better Rs
Smaller pixel  during interpolation ->   Better application of lapse rate  ->   Slightly better Tmin, Tmax Tdew       (only in mountains, but anyway we are not sure on the lapse rate value, so this is not clear)

Cons:

16 times more data.  one 2km pixel will convert into sixteen (16) 0.5 km pixel.
More data  ->  16X more storage
More data  ->   more time to process Spatial Statistics

In general, I would run this at the higher 500m resolution.  There are a couple of reasons for this:

Unless DWR made some drastic changes, I'm pretty confident the current setup runs at 500m and only downscales for the final output.  So you would be changing even more processing

If you run it at 2km, then you'll have less of a good method for testing new interpolations using old data.

If later on you decide to run at 500m, then you'd need to recalculate everything, including the Amazon downloads.

I made a real effort to create smaller per-day mapsets, and they are much smaller than what DWR is currenlty saving.

I don't think the processing time changes that much.

Our discussion with symsoft on 2024-10-04 indicated that internally, the process will be run at the 500m increment, while some of the output available to the public will be kept at the 2km resolultion.


Fix CI breakage from recent merge

#12498 merged with trailing whitespace. fixing here.

The patch file format may actually require the trailing whitespace. Let me try a build against this branch to double check.

The patch file format may actually require the trailing whitespace. Let me try a build against this branch to double check.

OK, looks like it still works. 👍


109: Replace retired microarray in Regulatory documentation pages

Description
Microarray examples in the documentation page are out of date:

https://rest.ensembl.org/documentation/info/probe
https://rest.ensembl.org/documentation/info/array

This PR is to replace the retired microarray with a valid one ( HumanWG_6_V2 -> HumanWG_6_V3 ).

Coverage: 44.439%. Remained the same when pulling e901022780062c79ffbd1a5547070731cf5a8390 on pblins:109_fix_microarray_example into 05a747c74bb080dc5430c9bf0bd79e3bd636ce48 on Ensembl:release/109.


Don't ctl stop updater in Keybase.app quit

See discussion here:
https://keybase.atlassian.net/browse/CORE-3418
With this change the updater would still be running if Keybase.app wasn't so
either this isn't the right solution or we need to address that too (as
mentioned in JIRA discussion), before merging this.

cc @cjb @cnojima

Closing this... we'll undo the before-quit changes (and maybe do something slightly different there).


Lint apis_authorization directory

This PR is part of #236 endeavor.

@Digipalvelutehdas/apika-tiimi please review.


[docs] Warn about checking for version mismatch

… between the client and server when doing SSR.
First discussed in #12434

@hluedeke It's a great first pull request on Material-UI 👌🏻. Thank you for giving it a shot!

Thank you for letting me! Glad I could help! And hope I can help more in the future 👍


'\n' characters in sentences in *.json data files.

There are some sentences having \n characters.
Ex) There are 147 \ns in mscoco_minival.json file as below.

Not only \n. There are many other cases like this, which adds "." sentences during training.
Is there a code somewhere that cleans these weird sentences?

This is the raw annotations from the MS COCO dataset. Details could be found in the annotations folder after downloading the dataset.

Yes, I just found same problems in the raw COCO annotations. Similar problems are in other datasets as well (VG also have similar issue in the second image).
Is this handled somewhere in your code?

Yes... I also just realized it recently... This code is build based on the BERT tokenizer,  which will consider \n's as spaces. So it does not require explicit handler. (That's why I just notice this when using some other tokenizers...)


This is a bug in card-deck?

Why this sample have horizontal scroll?

Can reproduce on Chrome v52, Ubuntu 14.04.
Bootlint says "no errors".
The reason seems to be that .card-deck-wrapper has -20px margin on both sides, while the .container has 15px padding on both sides. This means that the wrapper overflows 5px on each side which results in a horizontal scrollbar.
I tried a max-width: 100% on the wrapper but it messes up the grid :confused:

Duplicate of #19883, FWICT.


Deprecation warning on Ember 3.0

DEPRECATION: ember-cli-babel 5.x has been deprecated. Please upgrade to at least ember-cli-babel 6.6. Version 5.2.8 located: project-name -> ember-bootstrap-datetimepicker -> ember-cli-babel

This can be fixed by bumping ember-cli-babel to 6.6.0

Is this getting fixed?

Any progress on this issue?


Add the option to include basic Auth

I think this would be a good first step. It's definitely imperative that Users can turn on and off the option for their own deployment as Users may want to implement their own solution or use services provided by their cloud-provider.

The stac-fastapi base allows you too add route-dependencies at app creation:
routes = [
    {"path": "/collections", "method": "POST"},
    {"path": "/collections/{collectionId}", "method": "PUT"},
    {"path": "/collections/{collectionId}", "method": "DELETE"},
    {"path": "/collections/{collectionId}/items", "method": "POST"},
    {"path": "/collections/{collectionId}/items/{itemId}", "method": "PUT"},
    {"path": "/collections/{collectionId}/items/{itemId}", "method": "DELETE"},
]
dependencies = [Depends(must_be_bob)]
StacApi(
    title=os.getenv("STAC_FASTAPI_TITLE", "stac-fastapi-elasticsearch"),
    description=os.getenv("STAC_FASTAPI_DESCRIPTION", "stac-fastapi-elasticsearch"),
    api_version=os.getenv("STAC_FASTAPI_VERSION", "2.1"),
    settings=settings,
    extensions=extensions,
    client=CoreClient(
        database=database_logic, session=session, post_request_model=post_request_model
    ),
    search_get_request_model=create_get_request_model(extensions),
    search_post_request_model=post_request_model,
    route_dependencies=[(routes, dependencies)]
)

Or after the apps been created:
api.add_route_dependencies(scopes=routes, dependencies=[Depends(must_be_bob)])

I'm not sure the best way to include this in the current workflows. I've been overwriting the whole app.py.

Hi @rhysrevans3. Can you look at this pr https://github.com/Healy-Hyperspatial/stac-fastapi-mongo/pull/13? We are thinking about adding this here also.

@jonhealy1 this can be closed now :)


added MainsailOS support and ascii art

Description
Added MainsailOS ascii art so if mainsailOS devs change default /etc/lsb-release and /etc/os-release, it will work

how long does one have to wait till someone looks at the pull requests?

Thank you for your contribution!
This PR is merged into hyfetch since this repo (dylanaraps/neofetch) seems no longer maintained.
HyFetch is a fork of neofetch with LGBTQ pride flags, but the repo also maintains an updated version of the original neofetch, addressing many pull requests that are not merged in the original repo.
Read the "Running Updated Original Neofetch" section for more info!


keep_best_iv logic changed?

related to #4459
Do you confirm that "JoeThePokemon": {"keep_best_iv": 1} only triggers transfer when min_free_slot is reached?
Your FULL config.json (remove your username, password, gmapkey and any other private info)
http://pastebin.com/XzFy46Tv
Other Information
OS: OSX Capitan
Branch: dev
Git Commit: 4f2e976
Python Version: Python 2.7.12

I can confirm I am seeing the same thing
   "release": {
      "any": {"release_below_cp": 100, "release_below_iv": 0, "logic": "or"},
      "// Example of always releasing Rattata:": {},
      "// Rattata": {"always_release": true},
      "// Example of keeping 3 stronger (based on CP) Pidgey:": {},
      "// Pidgey": {"keep_best_cp": 3},
      "// Example of keeping 2 best (based on IV) Zubat:": {},
      "// Zubat": {"keep_best_iv": 2},
      "// Also, it is working with any": {},
      "any": {"keep_best_iv": 3},
      "// Example of keeping the 2 strongest (based on CP) and 3 best (based on IV) Zubat:": {},
      "// Zubat": {"keep_best_cp": 2, "keep_best_iv": 3},
          "// Example of custom order of static criterion": {},
          "// Zubat": {"keep_best_custom": "moveset.defense_perfection, hp_max", "amount":2}
    },

While I havn't reached max bag space yet, I'm getting close to it.
Dev Branch
Ubuntu 16.04
#4231
Additionally on startup it displays these pokemon which don't fit the above config.
2016-08-21 09:55:01,272 [PokemonGoBot] [INFO] #4 Charmander[1]: (CP 65, IV 0.67)
2016-08-21 09:55:01,273 [PokemonGoBot] [INFO] #10 Caterpie[1]: (CP 24, IV 0.29)
2016-08-21 09:55:01,273 [PokemonGoBot] [INFO] #16 Pidgey[1]: (CP 111, IV 0.56)
2016-08-21 09:55:01,273 [PokemonGoBot] [INFO] #17 Pidgeotto[1]: (CP 47, IV 0.56)
2016-08-21 09:55:01,273 [PokemonGoBot] [INFO] #21 Spearow[2]: (CP 148, IV 0.51) | (CP 45, IV 0.69)
2016-08-21 09:55:01,274 [PokemonGoBot] [INFO] #23 Ekans[2]: (CP 153, IV 0.4) | (CP 73, IV 0.51)
2016-08-21 09:55:01,274 [PokemonGoBot] [INFO] #24 Arbok[1]: (CP 501, IV 0.53)
2016-08-21 09:55:01,274 [PokemonGoBot] [INFO] #27 Sandshrew[1]: (CP 175, IV 0.51)
2016-08-21 09:55:01,274 [PokemonGoBot] [INFO] #29 Nidoran F[2]: (CP 33, IV 0.58) | (CP 32, IV 0.4)
2016-08-21 09:55:01,275 [PokemonGoBot] [INFO] #32 Nidoran M[1]: (CP 146, IV 0.62)
2016-08-21 09:55:01,275 [PokemonGoBot] [INFO] #35 Clefairy[1]: (CP 141, IV 0.44)
2016-08-21 09:55:01,275 [PokemonGoBot] [INFO] #37 Vulpix[1]: (CP 10, IV 0.71)
2016-08-21 09:55:01,275 [PokemonGoBot] [INFO] #41 Zubat[1]: (CP 10, IV 0.71)
2016-08-21 09:55:01,275 [PokemonGoBot] [INFO] #46 Paras[1]: (CP 11, IV 0.69)
2016-08-21 09:55:01,276 [PokemonGoBot] [INFO] #50 Diglett[2]: (CP 10, IV 0.64) | (CP 26, IV 0.47)
2016-08-21 09:55:01,276 [PokemonGoBot] [INFO] #52 Meowth[1]: (CP 31, IV 0.87)
2016-08-21 09:55:01,276 [PokemonGoBot] [INFO] #54 Psyduck[1]: (CP 152, IV 0.27)
2016-08-21 09:55:01,276 [PokemonGoBot] [INFO] #56 Mankey[1]: (CP 184, IV 0.73)
2016-08-21 09:55:01,277 [PokemonGoBot] [INFO] #58 Growlithe[3]: (CP 54, IV 0.58) | (CP 269, IV 0.47) | (CP 95, IV 0.82)
2016-08-21 09:55:01,277 [PokemonGoBot] [INFO] #59 Arcanine[1]: (CP 666, IV 0.93)
2016-08-21 09:55:01,277 [PokemonGoBot] [INFO] #60 Poliwag[1]: (CP 10, IV 0.51)
2016-08-21 09:55:01,277 [PokemonGoBot] [INFO] #63 Abra[1]: (CP 68, IV 0.47)
2016-08-21 09:55:01,277 [PokemonGoBot] [INFO] #66 Machop[1]: (CP 232, IV 0.78)
2016-08-21 09:55:01,278 [PokemonGoBot] [INFO] #67 Machoke[1]: (CP 182, IV 0.96)
2016-08-21 09:55:01,278 [PokemonGoBot] [INFO] #72 Tentacool[1]: (CP 62, IV 0.73)
2016-08-21 09:55:01,278 [PokemonGoBot] [INFO] #74 Geodude[1]: (CP 197, IV 0.62)
2016-08-21 09:55:01,278 [PokemonGoBot] [INFO] #75 Graveler[1]: (CP 19, IV 0.82)
2016-08-21 09:55:01,279 [PokemonGoBot] [INFO] #77 Ponyta[1]: (CP 20, IV 0.78)
2016-08-21 09:55:01,279 [PokemonGoBot] [INFO] #81 Magnemite[1]: (CP 84, IV 0.6)
2016-08-21 09:55:01,279 [PokemonGoBot] [INFO] #84 Doduo[1]: (CP 11, IV 0.76)
2016-08-21 09:55:01,279 [PokemonGoBot] [INFO] #90 Shellder[1]: (CP 173, IV 0.8)
2016-08-21 09:55:01,279 [PokemonGoBot] [INFO] #95 Onix[1]: (CP 10, IV 0.51)
2016-08-21 09:55:01,280 [PokemonGoBot] [INFO] #98 Krabby[1]: (CP 120, IV 0.71)
2016-08-21 09:55:01,280 [PokemonGoBot] [INFO] #104 Cubone[2]: (CP 43, IV 0.89) | (CP 157, IV 0.69)
2016-08-21 09:55:01,280 [PokemonGoBot] [INFO] #105 Marowak[1]: (CP 68, IV 0.53)
2016-08-21 09:55:01,280 [PokemonGoBot] [INFO] #111 Rhyhorn[3]: (CP 193, IV 0.93) | (CP 117, IV 0.73) | (CP 260, IV 0.84)
2016-08-21 09:55:01,281 [PokemonGoBot] [INFO] #118 Goldeen[2]: (CP 37, IV 0.33) | (CP 12, IV 0.62)
2016-08-21 09:55:01,281 [PokemonGoBot] [INFO] #128 Tauros[1]: (CP 183, IV 0.64)
2016-08-21 09:55:01,281 [PokemonGoBot] [INFO] #129 Magikarp[2]: (CP 41, IV 0.53) | (CP 10, IV 0.82)
2016-08-21 09:55:01,281 [PokemonGoBot] [INFO] #133 Eevee[1]: (CP 47, IV 0.91)
2016-08-21 09:55:01,282 [PokemonGoBot] [INFO] #140 Kabuto[1]: (CP 46, IV 0.8)

Never reached max slot for pokemon yet...but i think so ... Pokemon only will release when poke bag almost full....
Different trigger for latest update...

@k4n30 you closed, means you acknowledge this answer?


I'm using a module replacement:
replace github.com/crabmusket/gosunspec => github.com/andig/gosunspec v0.0.0-20190802074646-9596f4c956e3

Doing
go get -u github.com/andig/gosunspec@rollup

does not update the replacement I have in go.mod to the latest commit available. Instead, it adds it as new requirements.
What did you expect to see?
It would be nice if the replacements allowed upgrading too. Currently it doesn't, instead it adds the module to the required modules and I manually need copy the commit across to the replacement line plus remove the added module.
Granted this is probably not too common but would be nice.

@andig Do you have require github.com/crabmusket/gosunspec in your go.mod file. Please check this #29299 PR for reference. It might be useful for you.

Do you have require github.com/crabmusket/gosunspec in your go.mod file

Yes, I do (https://github.com/volkszaehler/mbmd/blob/master/go.mod#L4).
I've read both #29299 and #26241 now, it seems they are about not having to write the actual require when using replace.
Neither seems to mention the missing upgrade behaviour of go get -u with replace?

Duplicate of #32721


@opentelemetry/instrumentation-fastify has not been published since November

It looks like @opentelemetry/instrumentation-fastify have not be published to NPM since November. It has been work done on the code after that, but they are not published.
The effect of this is that the current @opentelemetry/instrumentation-fastify on npm (v0.25.0) is not compatible with @opentelemetry/instrumentation v0.27.0.
Gets the error:
Type 'Meter' is missing the following properties from type 'Meter': createValueRecorder, createValueObserver, createSumObserver, createUpDownSumObserver, createBatchObserver
Looking at the commit I see that it is fixed in #769

seems there is no owner for this instrumentation mentioned in https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/.github/component_owners.yml
@obecny you created this one initially in #611. Do you still feel responsible for it?

seems the fastify instrumentation is missing in release config. I created https://github.com/open-telemetry/opentelemetry-js-contrib/pull/873 to add it.

looks to be 0.26.0 that is published to npm now
https://www.npmjs.com/package/@opentelemetry/instrumentation-fastify
closing


Exec tachikoma update<PHONE_NUMBER>4823

:hamster::hamster::hamster:   Strategy none
Powered by Interval Pull Request as a Service - Tachikoma.io

Coverage remained the same when pulling 0e225883b3420bbf2314b299373f55c7638c4f69 on tachikoma/update-20150107104823 into ddf31327ec9d3097b29bd6c49c1071d946319912 on master.


[WIP]  BlazingSQL - Q08: Remove unused tables

This PR removes unused tables.

@Christian8491 is this still WIP?

@randerzander just updated to REVIEW


There is no configuration :(

I tested it with Modmenu, I tested it by searching for the configuration file and it doesn't take/exist a configuration file.

I tested it with Modmenu, I tested it by searching for the configuration file and it doesn't take/exist a configuration file.

Which version of Minecraft of the mof? Also, does pressing the Configure... button on this mod's mod menu entry do nothing? Pressing it should be showing the config by automatically opening youtlr text editor. (There's no config screen)

visual-snowy-leaves-0.4.0+mc1.21.1
Yep, does nothing. In this case, it doesn't create any configuration files

That's not good... Could you also check the logs? Those of note are ones containing [Visual Snowy Leaves] and see if anything's up? Or send a whole chunk of the logs since finding those lines may be tedious. (I can't make a fix rn).

Also, fix the resourcepack version.
https://paste.atlauncher.com/view/da19df9b-c313-4289-a3e9-c4f90f8886a4

Summary:
[20/11/2024 22:50:32 PM] [Render thread/WARN] [Visual Snowy Leaves] Unable to read config json
[20/11/2024 22:50:32 PM] 	at java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:85)
[20/11/2024 22:50:32 PM] 	at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103)
[20/11/2024 22:50:32 PM] 	at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108)
[20/11/2024 22:50:32 PM] 	at java.base/sun.nio.fs.WindowsFileSystemProvider.newFileChannel(WindowsFileSystemProvider.java:119)
[20/11/2024 22:50:32 PM] 	at java.base/java.nio.channels.FileChannel.open(FileChannel.java:309)
[20/11/2024 22:50:32 PM] 	at java.base/java.nio.channels.FileChannel.open(FileChannel.java:369)
[20/11/2024 22:50:32 PM] 	at java.base/java.nio.file.Files.lines(Files.java:4112)
[20/11/2024 22:50:32 PM] 	at java.base/java.nio.file.Files.lines(Files.java:4207)
[20/11/2024 22:50:32 PM] 	at knot//io.github.startsmercury.visual_snowy_leaves.impl.client.VisualSnowyLeavesImpl.loadConfig(VisualSnowyLeavesImpl.java:123)
[20/11/2024 22:50:32 PM] 	at knot//io.github.startsmercury.visual_snowy_leaves.impl.client.VisualSnowyLeavesImpl.reloadConfig(VisualSnowyLeavesImpl.java:109)
[20/11/2024 22:50:32 PM] 	at knot//io.github.startsmercury.visual_snowy_leaves.impl.client.entrypoint.VisualSnowyLeavesModMenu.openConfigFile(VisualSnowyLeavesModMenu.java:20)
[20/11/2024 22:50:32 PM] 	at knot//io.github.startsmercury.visual_snowy_leaves.impl.client.entrypoint.VisualSnowyLeavesModMenu$1.method_25426(VisualSnowyLeavesModMenu.java:30)
[20/11/2024 22:50:32 PM] 	at knot//net.minecraft.class_437.method_25423(class_437.java:309)
[20/11/2024 22:50:32 PM] 	at knot//net.minecraft.class_310.method_1507(class_310.java:1143)
[20/11/2024 22:50:32 PM] 	at knot//com.terraformersmc.modmenu.gui.ModsScreen.safelyOpenConfigScreen(ModsScreen.java:647)
[20/11/2024 22:50:32 PM] 	at knot//com.terraformersmc.modmenu.gui.widget.entries.ModListEntry.openConfig(ModListEntry.java:182)
[20/11/2024 22:50:32 PM] 	at knot//com.terraformersmc.modmenu.gui.widget.entries.ModListEntry.method_25402(ModListEntry.java:172)
[20/11/2024 22:50:32 PM] 	at knot//com.terraformersmc.modmenu.gui.widget.ModListWidget.method_25402(ModListWidget.java:294)
[20/11/2024 22:50:32 PM] 	at knot//net.minecraft.class_4069.method_25402(class_4069.java:38)
[20/11/2024 22:50:32 PM] 	at knot//net.minecraft.class_312.method_1611(class_312.java:107)
[20/11/2024 22:50:32 PM] 	at knot//net.minecraft.class_437.method_25412(class_437.java:431)
[20/11/2024 22:50:32 PM] 	at knot//net.minecraft.class_312.method_1601(class_312.java:107)
[20/11/2024 22:50:32 PM] 	at knot//net.minecraft.class_312.method_22686(class_312.java:196)
[20/11/2024 22:50:32 PM] 	at knot//net.minecraft.class_1255.execute(class_1255.java:108)
[20/11/2024 22:50:32 PM] 	at knot//net.minecraft.class_312.method_22684(class_312.java:196)
[20/11/2024 22:50:32 PM] 	at knot//org.lwjgl.glfw.GLFWMouseButtonCallbackI.callback(GLFWMouseButtonCallbackI.java:43)
[20/11/2024 22:50:32 PM] 	at knot//org.lwjgl.system.JNI.invokeV(Native Method)
[20/11/2024 22:50:32 PM] 	at knot//org.lwjgl.glfw.GLFW.glfwWaitEventsTimeout(GLFW.java:3509)
[20/11/2024 22:50:32 PM] 	at knot//com.mojang.blaze3d.systems.RenderSystem.limitDisplayFPS(RenderSystem.java:184)
[20/11/2024 22:50:32 PM] 	at knot//net.minecraft.class_310.method_1523(class_310.java:1310)
[20/11/2024 22:50:32 PM] 	at knot//net.minecraft.class_310.method_1514(class_310.java:882)
[20/11/2024 22:50:32 PM] 	at knot//net.minecraft.client.main.Main.main(Main.java:256)
[20/11/2024 22:50:32 PM] 	at net.fabricmc.loader.impl.game.minecraft.MinecraftGameProvider.launch(MinecraftGameProvider.java:480)
[20/11/2024 22:50:32 PM] 	at net.fabricmc.loader.impl.launch.knot.Knot.launch(Knot.java:74)
[20/11/2024 22:50:32 PM] 	at net.fabricmc.loader.impl.launch.knot.KnotClient.main(KnotClient.java:23)

Also, fix the resourcepack version.

I forgot! NooooOo. I will update the resourcepack version(s)... anything other than the one for 1.20.1 is not updated, great job me X)

I think that's all the logs, thanks! The mod's logs are actually lacking and it is partially my fault, and probably the logger.

I think that's all the logs we need, thanks! The mod's logs are actually lacking and it is partially my fault, and probably the logger.

I think that's all the logs we need, thanks! The mod's logs are actually lacking and it is partially my fault, and probably the logger.

The issue was a logic error. It was detecting that a config is non-existent, or the first time to create in in this case. The issue prevented the generation of the config file. 0.4.1 just released and it should hopefully fixes this and the resource pack version.

It seems that this has been fixed, but in my modpack your mod is not working correctly, I will see which mod is the problem.
And from what I've seen, the resource pack version is still wrong.

And from what I've seen, the resource pack version is still wrong.

Oh! I just checked, it's using data pack version numbers instead of resource pack version numbers. Great :')