Resolve output paths relative to .vcxproj rather than .sln

If you build ViGEmClient on its own (through Visual Studio), you'll end up with a directory structure like this, where output files are written to top-level directories called bin (for DLLs) or lib (for static libs), e.g.:

ViGEmClient/ViGEmClient.sln
ViGEmClient/src/ViGEmClient.vcxproj
ViGEmClient/lib/release/x64/ViGEmClient.lib

I cloned ViGEmClient into my own project as a submodule, giving me a directory structure like this:

myproject/build/myproject.sln
myproject/build/myproject.vcxproj
myproject/external/ViGEmClient/ViGEmClient.sln
myproject/external/ViGEmClient/src/ViGEmClient.vcxproj

To simplify the build process within Visual Studio, I added the project (ViGEmClient.vcxproj) to my solution (myproject.sln). However, I noticed that when I build ViGEmClient to generate static libs, they end up in an unexpected location:

myproject/build/myproject.sln
myproject/build/myproject.vcxproj
myproject/build/lib/release/x64/ViGEmClient.lib <-- currently, output libs are written here
myproject/external/ViGEmClient/ViGEmClient.sln
myproject/external/ViGEmClient/src/ViGEmClient.vcxproj
myproject/external/ViGEmClient/lib/release/x64/ViGEmClient.lib <-- but they should really be here

This is simply because the output directories configured in ViGEmClient.vcxproj are defined relative to $(SolutionDir). This change updates those paths to be resolved relative to $(ProjectDir), so that output files always end up in the expected locations (ViGEmClient/lib or ViGEmClient/bin) regardless of whether the library is built on its own or within another solution.
Thanks!

Neat, thanks!


Make tf use the rviz ros node

With #197 merged a running rviz effectively has 2 ros nodes: the main rviz node with name rviz and a second node with name transform_listener_impl which is created by tfs TransformListener.
@wjwwood If we hand the rviz node to tf (as in this pr) rviz repeatedly logs
Do not call canTransform or lookupTransform with a timeout unless you are using another thread for populating data. Without a dedicated thread it will always timeout.  If you have a seperate thread servicing tf messages, call setUsingDedicatedThread(true) on your Buffer instance.
We need some help with this.

Once working this should also solve #52 .

@anhosi I saw your comment as I was passing by. You might try something like https://github.com/ros2/navigation/blob/93468284d4c598669861e69734d9d50035a79175/amcl/src/amcl_node.cpp#L488 if you haven't already

@dhood That did it. Thanks.

Note that this is now conflicting and needs a rebase.

CI after rebase:

Linux
Linux-aarch64
macOS
Windows

CI after rebase:

Linux
Linux-aarch64
macOS
Windows


the benchmark of t1

Hello, I'm a beginner of t1.  I wang to figuer it out that does t1 have a benchmark? if not , how can we compare the performance between t1 and other  architectures?

Thanks for your interest!
For now, we have only a bunch of tests, including some MLIR based workload under tests dir, feel free to add your own benchmark!

Very impressive project, is there an example integration? For example, with Rocket?
If RV64GCBV is enabled, it is possible to test with auto-vectorized benchmarks, like some of SPECCPU benchmarks.

@sequencer
Is there an example integration? For example, with Rocket?
If RV64GCBV is enabled, it is possible to test with auto-vectorized benchmarks, like some of SPECCPU benchmarks.

Not currently. Because T1 uses a lot of new chisel features, we just forked the rocket core for integrating it as a demo.
But please note we currently don’t support this flow.
For compiler engineers, the emulator fully emulate scalar core with spike as well as memory subsystem. It also expose uarch events to users, you can directly use that.

Additionally, we don’t support MMU because we don’t want to suffer with pf and af or any other memory coherence overhead. We only support machine mode to use this framework as pure accelerator.


Add integration tests

With https://github.com/itsdalmo/github-pr-resource/pull/20 we have unit testing which mocks the github and git interfaces, in addition to end 2 end tests. However, there is a distinct lack of tests that verify that that the interfaces actually integrate correctly with the Github API. I.e., if we need to change any of the GithubClient methods the tests won't catch any mistakes without running make e2e.
Might be an idea to set up a test http server with fake routes.

We have e2e tests that can be run against this public (but archived) repository:
https://github.com/itsdalmo/test-repository
Can be run with:
export GITHUB_ACCESS_TOKEN=<personal access token>
make e2e


CPU Sensors show 0.0 for temperature.

I've updated the latest version of OpenHardwareMonitorLib (the 0.8.0 version) in the jar file, but still the code fails to detect the temperature. I can understand if this is not supported by my computer, but when I run the actual Open Hardware Monitor executable, it picks up the temperatures.
How can I know if my computer can support this?

Sorry, running the IDE as admin worked out for me!  :+1:


switch terminal is wrong when I use split terminal

VSCode Version: 1.23.0
OS Version: Windows 10 Pro 1709

Steps to Reproduce:

Create new integrated terminal
Split terminal
Create new integrated terminal
Open Command Palette
Select "Terminal: Switch Active Terminal"
Select 2
example

1: pwsh, pwsh
2: pwsh

I think that open "2:pwsh", but actually open "1: pwsh, pwsh" and active 2nd shell (right pane).

Does this issue occur when all extensions are disabled?: Yes

Thanks for spotting this, I recently fixed for the rename/kill buttons in the term menu but missed switching not working.


Flex 2971 automate regression test c151 change layout device list sequal

This pull request makes the build fail.

This pull request makes the build fail.

 All committers of the pull request should sign our Contributor License Agreement in order to get your pull request merged.1 out of 2 committers have signed the CLA.:white_check_mark: SamVanDijk:x: web-flow

This pull request makes the build fail.

restest this please

This pull request makes the build fail.

This pull request makes the build fail.

This pull request makes the build fail.

This pull request makes the build fail.

This pull request makes the build fail.

retest this please

This pull request makes the build fail.

This pull request makes the build fail.

retest this please

This pull request makes the build fail.

retest this please

This pull request makes the build fail.

This pull request makes the build fail.


ObservationAwareBaggageThreadLocalAccessor loses scopes in the wrong order

Hello,
i currently use observations to handle traces. As it is currently not possible to update Baggage using the Observation API, i need to use the Tracer API directly to interact with baggage. My root problem is that i use observations in a multithreaded environment and that baggage creation somehow interferes with the traces and spans. In my case, the spans and traces are not closed properly although the observation does. As i investigated this matter further i could reproduce the behaviour with a @ParameterizedTest.
I hope that resolving this problem, can resolve my root problem.
I added a minimal reproducer for you to see the issue. Basically, i have 3 tests and an otelTracer setup.
The first test is a normal junit test which opens an observation, creates some baggage, closes the baggage, closes the observation, and then verifies that the trace context is not set outside the observation.
The second tests does the same, but using @ParameterizedTest. This test fails as the trace context is not properly closed after the observation.
The third test is calling the first test again. This time it fails, because somehow the trace context is still set from the second test.
Disabling the second test and running the whole test class again fixes the test.
My best guess is that @ParameterizedTest somehow executes the tests in parallel which interferes with the baggage scopes which in return results in wrong spans and traces.
Thanks in advance for the help and keep up the good work!
Reproducer:
micrometer-baggage-interferes-with-observation.zip

Can you check if the problem is still there using the latest snapshots? We've managed to do some improvements related to the baggage api and thread locals

Hey, thanks for the suggestion. So i tried it with the 1.2.3-SNAPSHOT and with the ObservationAwareBaggageThreadLocalAccessor and it still did not work. Then i debugged the reproducer a litte more and found the problem.
The problem is that i create multiple baggage entries via tracer.createBaggageInScope() and save the Scope within a List. I assumed that closing the scopes before existing my observation was enough, but it seems that the scopes need to be closed in the reversed order that i opened them. After switching from a List to a Stack data structure and closing the Scope in reverse order, everything worked fine. (This also works on the current version 1.2.2)
I still do not know why the baggage closing order messes with observation and traces this much though.

That actually makes sense. You have to close it in the reverse order because the scopes are reverting to a previous value on close and most likely there's an issue with reverting to a wrong scope at certain moment.

Hey,
i noticed that you released micrometer-tracing 1.2.3. I think that ObservationAwareBaggageThreadLocalAccessor has the same bug that was responsible for the behaviour i described above. It closes the scopes in the same order that they are opened instead of the reversed order.
In think that changing this line to return scopeClosingBaggageAndScope(entry, baggage).andThen(scope); fixes the problem.
I hope i didn't miss anything but using the current ObservationAwareBaggageThreadLocalAccessor results in the same error i had before reversing the closing order.

Do you want to open a PR to fix this (with a test that reproduces the issue)?
(I haven't dig deeper into the proposed solution but based on the above in this issue it makes sense for the first sight.)
Btw I think these are slightly connected, feel free to add 👍🏼 to them if they would be useful to you:

https://github.com/micrometer-metrics/tracing/issues/563
https://github.com/micrometer-metrics/tracing/issues/455

Hey, will do :)

Hey I created the PR. Just maybe this will also fix #625 since it was so for me.


Killed

On a brand new jetson while running the test:
ubuntu@tegra-ubuntu:~/Documents/Projects/tf_to_trt_image_classification$ python scripts/test_tf.py
Testing mobilenet_v1_0p25_128
2018-03-15 01:29:49.697714: I tensorflow/stream_executor/cuda/cuda_gpu_executor.cc:865] ARM64 does not support NUMA - returning NUMA node zero
2018-03-15 01:29:49.697838: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1212] Found device 0 with properties:
name: NVIDIA Tegra X2 major: 6 minor: 2 memoryClockRate(GHz): 1.3005
pciBusID: 0000:00:00.0
totalMemory: 7.67GiB freeMemory: 6.14GiB
2018-03-15 01:29:49.697886: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1312] Adding visible gpu devices: 0
2018-03-15 01:29:50.859554: I tensorflow/core/common_runtime/gpu/gpu_device.cc:993] Creating TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 5664 MB memory) -> physical GPU (device: 0, name: NVIDIA Tegra X2, pci bus
id: 0000:00:00.0, compute capability: 6.2)
['Gordon setter\n', 'Rottweiler\n', 'Tibetan mastiff\n', 'black-and-tan coonhound\n', 'flat-coated retriever\n']
Testing resnet_v1_50
2018-03-15 01:29:57.964211: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1312] Adding visible gpu devices: 0
2018-03-15 01:29:57.964345: I tensorflow/core/common_runtime/gpu/gpu_device.cc:993] Creating TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 4491 MB memory) -> physical GPU (device: 0, name: NVIDIA Tegra X2, pci bus
id: 0000:00:00.0, compute capability: 6.2)
['Gordon setter\n', 'Irish setter, red setter\n', 'cocker spaniel, English cocker spaniel, cocker\n', 'black-and-tan coonhound\n', 'Rottweiler\n']
Testing mobilenet_v1_1p0_224
2018-03-15 01:30:06.583719: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1312] Adding visible gpu devices: 0
2018-03-15 01:30:06.583871: I tensorflow/core/common_runtime/gpu/gpu_device.cc:993] Creating TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 2178 MB memory) -> physical GPU (device: 0, name: NVIDIA Tegra X2, pci bus
id: 0000:00:00.0, compute capability: 6.2)
['Gordon setter\n', 'Irish setter, red setter\n', 'black-and-tan coonhound\n', 'cocker spaniel, English cocker spaniel, cocker\n', 'Tibetan mastiff\n']
Testing inception_v2
2018-03-15 01:30:11.103292: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1312] Adding visible gpu devices: 0
2018-03-15 01:30:11.103426: I tensorflow/core/common_runtime/gpu/gpu_device.cc:993] Creating TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 2131 MB memory) -> physical GPU (device: 0, name: NVIDIA Tegra X2, pci bus
id: 0000:00:00.0, compute capability: 6.2)
['Gordon setter\n', 'Irish setter, red setter\n', 'cocker spaniel, English cocker spaniel, cocker\n', 'Rottweiler\n', 'black-and-tan coonhound\n']
Testing inception_v3
2018-03-15 01:30:19.184979: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1312] Adding visible gpu devices: 0
2018-03-15 01:30:19.185114: I tensorflow/core/common_runtime/gpu/gpu_device.cc:993] Creating TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 2030 MB memory) -> physical GPU (device: 0, name: NVIDIA Tegra X2, pci bus
id: 0000:00:00.0, compute capability: 6.2)
['Gordon setter\n', 'Rottweiler\n', 'Irish setter, red setter\n', 'black-and-tan coonhound\n', 'English setter\n']
Testing resnet_v2_152
2018-03-15 01:30:38.026162: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1312] Adding visible gpu devices: 0
2018-03-15 01:30:38.026349: I tensorflow/core/common_runtime/gpu/gpu_device.cc:993] Creating TensorFlow device (/job:localhost/replica:0/task:0/device:GPU:0 with 27 MB memory) -> physical GPU (device: 0, name: NVIDIA Tegra X2, pci bus id: 0000:00:00.0, compute capability: 6.2)
Killed

new Jetpack. Any ideas why the jetson is not returning full memory?

No, I haven't be able to replicate the script, every time gets killed by memory consumption

I have seen that creating sessions and closing sessions it actually downs the available gpu memory usage. Maybe a bug in tf part?

@jaybdub-nv I can report the same issue. Reboot does not help. Memory consumption is constantly around 6.5GB but in resnet_v2_152 goes through the limit of 8GB.

I am also reporting this problem. Please let me know if you find any solutions :)


Precision_recall Curve questions

Hi
#13 I saw Anida's problem. I have a same problem. And i can not get the precision recall curve from your paper.
I want to know what will u put the precision value and recall value if there are no proposals exceed the threshold you set? You set it to precision:1.0 recall: 0.0 or something else? I tried many methods. I evaulated it by getting each image's p_r value and let the average mean of them to the final p_r of this threshold. I also tried to caculate all the TP and FP and FN numbers of the whole testing images and used the formula to get the final p_r of this threshold. But also didn't get the result. This trapped me a lot.
You said 'I analyzed if any of them had more than 0.5 intersection over union with any object of the ground truth, and that is a TP'. but I think that means one gt can have more than one TP.
And I want to know if your models given on github can be used directly to test and get the precision recall curve. Should i still need to train for getting the result of your paper.
You said this model is different from ones from your paper. One is for 1 object. One is for multiple objects. So did you have precision recall curve graph of this model ?
Or if it is possible. Could you please upload the metric codes. That will be of great help.
Thanks a lot.

@yuanyuanjiao
Hi!
Have you run this code both training and testing correctly?

@yuanyuanjiao
Hi!
Have you obtained the AP, mAP, and PRC of this code?


Ensure gauges can only be created for assets that exist on-chain

Currently gauges seem to be creatable for assets that don't exist on-chain. This doesn't really pose any efficiency problems, but we should nonetheless eliminate this. (If nothing else, just for integrators sanity lol)
Here is an instance for a gauge for the denom "Stake".
    {
      "id": "244",
      "is_perpetual": false,
      "distribute_to": {
        "lock_query_type": "ByDuration",
        "denom": "stake",
        "duration": "604800s",
        "timestamp": "2021-03-16T17:57:55Z"
      },
      "coins": [
        {
          "denom": "ibc/27394FB092D2ECCD56123C74F36E4C1F926001CEADA9CA97EA622B25F41E5EB2",
          "amount": "1000"
        }
      ],
      "start_time": "2021-07-01T20:36:45Z",
      "num_epochs_paid_over": "5",
      "filled_epochs": "0",
      "distributed_coins": []
    },

This can be fixed by making the CreateGauge logic in x/incentives check that the denomination exists in the bank keeper on the chain, somewhere.

@ValarDragon I've been working on this but am a bit uncertain about a few things with regards to denomination existence logic:

Should the check be performed against the lockup.QueryCondition Denom or sdk.Coin Denom? I would think the latter but you mention the lockup.QueryCondition.Denom ("stake") in the issue description.

Should supply or metadata be referenced for validating asset existence on-chain? I noticed there will be a HasSupply() method available so I would think supply is the standard reference for checking existence, however, technically an asset can exist on chain with no supply (after supply runs out). This seems like an edge case since supplies shouldn't run out for quite some time, but I figured I'd defer to you on the preferred methodology to verify asset existence

Either way, I'm seeing lots of test failures checking both lockup.QueryCondition Denom or sdk.Coin Denom? so it would be nice to have some clarity on the preferred approach

The check should basically be:
bankkeeper.HasSupply(lockup.QueryCondition.Denom)
We want to upgrade to SDK v0.44 ASAP, so probs best to wait on that. (Or can build it in a separate branch using Jacob's PR)

Sounds good; will wait until this is available via SDK version upgrade
I haven't taken a deep look into the SDK supply code, but I'm making an assumption here that an asset is not removed if the supply ultimately reaches zero - it's quite possible I'm incorrect about this expectation.


NVRAM option awareness in op-test

NVRAM options are generally used to work around issues or enable debugging features without re-building a pnor. When enabled they can significantly change the behaviour of firmware so it probably not safe to allow arbitrary NVRAM overrides to be enabled on a system undergoing testing. As a part of the system setup op-test should at the very least check what nvram overrides are being used. Ideally it should clear any that are in use since stock firmware should never be using them.
Allowing a white-list of nvram options would be useful in some cases though. Some of our test systems use a bootargs override to disable malfunctioning hardware and NVRAM options can be useful for doing A/B testing of fixes.
For an example of how this can cause issues, see https://github.com/open-power/op-test-framework/issues/491

Good idea!


Should syntax like +someVariable be allowed by itself?

TypeScript Version:  1.8.10
I've seen some developers at my organization do something like the following (usually a typo)
var num = 4;
var demo = +num;
console.log(demo); //4

Writing +num seems like it should not be valid syntax by itself, although it is allowed in plain JavaScript.  Either way it really does nothing except look strange as far as I can tell.
I can't really think of a valid reason why syntax like this should be allowed, but I'd be curious to hear if anyone knows reasons why it should.

It is a form of valid implicit coercion:
const four = 4;
const a = +four;
const b = +false;
const c = +'4';
console.log(a, b, c); // 4, 0, 4
console.log(typeof a, typeof b, typeof c); // number, number, number

So not in all cases would it be an error.  This sort of thing is usually addressed best by a linter (e.g. tslint) instead of "breaking" the JavaScript compatibility in TypeScript.

ah ok, I was not aware of that. I suppose I've only seen it used "improperly" then


changed hhvm-nightly to hhvm

as per https://travis-ci.org/swiftmailer/swiftmailer/jobs/70777435
HHVM nightly is no longer supported on Ubuntu Precise. See https://github.com/travis-ci/travis-ci/issues/3788 and https://github.com/facebook/hhvm/issues/5220

:+1:

Thank you @gondo.


Use a temp path to save local checkpoints for remote save path

What does this PR do?
Uses a temp path to save local checkpoints for remote save paths.
This avoids issues where the current path has limits on file sizes or permission restrictions. This also enables more configurability because we can configure the default temp dir if needed.
Testing
Tested on interactive, saving to a remote dbfs path. You can see that the checkpoints are now saved to a local folder:

And the checkpoints are uploaded correctly to the remote location in mlflow artifacts:

Test runs
multi-nodetest-tmpdir-checkpoints-remote-16-Ekpzdy
single-node test-tmpdir-checkpoints-remote-2eaXbb
What issue(s) does this change relate to?

Before submitting

[ ] Have you read the contributor guidelines?
[ ] Is this change a documentation change or typo fix? If so, skip the rest of this checklist.
[ ] Was this change discussed/approved in a GitHub issue first? It is much more likely to be merged if so.
[ ] Did you update any related docs and document your change?
[ ] Did you update any related tests and add any new tests related to your change? (see testing)
[ ] Did you run the tests locally to make sure they pass?
[ ] Did you run pre-commit on your change? (see the pre-commit section of prerequisites)

@mvpatel2000 Another benefit of using a tmpdir is that we can configure it via environment variable, so we can redirect it easily if needed to (which we'll need to do for notebooks)

Yeah this seems fine to me, the only worry I see here is checkpoints filling up the disk. /tmp is special in azure as its one of the two mount points for the nvme. On our other clusters we leverage ephemeral storage so /tmp would be included in that.
That being said, tempfile.mkdtemp requires manual clean up for the files and directory. Something to consider here if you are hoping for these to be taken care of.
IIRC there is a context manager that can handle this in a clean way if you do want automatic clean up.


multiprocessing issue

Python version: 3.5
GSEApy version 0.8.3
Platform: macOS 10.12.5
When I follow the example from EXAMPLE of the session GSEA, I got the result like this:

es
nes
pval
fdr
gene_set_size
matched_size
genes

Term

Cytokine-cytokine receptor interaction_Homo sapiens_hsa04060
0.229069
1.556522
0.000000
0.000000
265
18
IL10RB,VEGFC,CSF1,TNFSF12,LTBR,CXCL10,TNFRSF1A...

Ras signaling pathway_Homo sapiens_hsa04014
0.332033
1.141144
0.002004
0.002003
227
18
ETS1,GNG13,RRAS,VEGFC,GNB4,CSF1,SOS2,FGF17,PDG...

Rap1 signaling pathway_Homo sapiens_hsa04015
-0.285975
-1.621806
0.000000
0.005941
211
19
RRAS,VEGFC,CSF1,FGF17,PDGFRB,FGF4,PDGFC,SIPA1L...

MAPK signaling pathway_Homo sapiens_hsa04010
-0.392928
-1.037983
0.500000
0.010396
255
18
GADD45B,RRAS,SOS2,FGF17,PPP3CC,TNFRSF1A,PDGFRB...

HTLV-I infection_Homo sapiens_hsa05166
-0.249752
-0.899335
0.666667
0.996040
258
19
FZD2,ETS1,STAT5B,RRAS,LTBR,PPP3CC,TNFRSF1A,EGR...

PI3K-Akt signaling pathway_Homo sapiens_hsa04151
0.182245
0.668758
1.000000
1.000000
341
22
GNG13,VEGFC,GNB4,CSF1,SOS2,FGF17,THBS4,PDGFRB,...

Pathways in cancer_Homo sapiens_hsa05200
0.201838
0.573342
1.000000
1.000000
397
27
FZD2,ETS1,STAT5B,GNG13,VEGFC,GNB4,SOS2,FGF17,E...

It is strange that the P-value is either 0 or 1, after investigate the source, it seems the null distribution broken.
the part of value of the esnull:
[-0.5277168069182326, -0.3607821392991908, -0.27070554833780985, 0.14716709004244327, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, -0.19182208447985646, ....]

the value after index 4 are identical, which lead to a odd normal distribution.
And after trace of the identical value, I find the odd value is caused by the multiprocessing.Pool.
    if permutation_type == "phenotype":
        l2 = list(classes)
        dat2 = dat.copy()
        #multi-threading for rankings.
        rank_nulls=[]
        pool_rnkn = Pool(processes=processes)

        for i in range(n):
            rs.shuffle(l2)
            rank_nulls.append(pool_rnkn.apply_async(_rnknull, args=(dat2, method,
                                                                  phenoPos, phenoNeg,
                                                                  l2, ascending)))
        pool_rnkn.close()
        pool_rnkn.join()

In fact, the 1000 times RandomState.shuffle is done after the multiprocessing.Pool close. so the classes vector live in the memory of pool_rnkn keep the reference of the last generated l2.
After copy the shuffle classes vector every time by:
for i in range(n):
            rs.shuffle(l2)
            l3 = deepcopy(l2)
            rank_nulls.append(pool_rnkn.apply_async(_rnknull, args=(dat2, method,
                                                                  phenoPos, phenoNeg,
                                                                  l3, ascending)))

Then the module calculates the correct p-value.
I am not sure if this issue only occur in my system, but seem several methods using multiprocessing.Pool may suffers this issue. And I hope this will be fixed soon.
Thanks~
Sheep

Sorry for replying late. Yes, you are right @iseekwonderful , the multiprocessing Pool use the same randomstate, leading to the final bug. This is unexpected when multi-cores are applied, and we don't want it. With some testing, I recaptured this issue on Windows a few times, too.
Thank you very much for pointing this critical bug out and make GSEApy better!
-Zhuoqing

Could you please upgrade gseapy to 0.8.4 at pypi?

sure, but I need additional testing for other improvement. 0.8.4 will land soon.


Update docs warning about csv data split between distributed pods

Avoid confusion about test data usage and clarify that won't be duplicated data.

I'll take a look at this Lint issue from Go Releaser, it's kind of a :chicken: :egg: problem with the releases.. related to #196


reorg AccessLogging e2e tests

logging e2e mixed with other tests in stats/prometheus, it's odd, let's do something to improve it.

One thing to note is that each new test suite adds 2-3minutes. So it's recommended to only split them if they have different install values.
We can rename it of course

there's not existing suite for logging and WasmPlugin, those tests are put in stats/prometheus/nullvm/accesslogs_test.go and stats/prometheus/wasm/imagepullpolicy_test.go
we may need two suites for those, but that will cost more time for e2e tests.

The only reason to make more suites is if they need different Istio
installations. Unlikely normal packages it's not just organization - there
is a huge cost. If there are distinct features they can be split into
files, functions, etc.
Ideally there would be one suite
On Sun, Jun 26, 2022, 7:30 PM zirain @.***> wrote:

there's not existing suite for logging and WasmPlugin, those tests are put
in stats/prometheus/nullvm/accesslogs_test.go and
stats/prometheus/wasm/imagepullpolicy_test.go
we may need two suites for those, but that will cost more time for e2e
tests.
—
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/39623#issuecomment-1166763736, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXLS2U6U6GSPW2JNWJLVREG3TANCNFSM5ZZO4B3Q
.
You are receiving this because you commented.Message ID:
@.***>

https://github.com/istio/istio/pull/39687#issuecomment-1197526728
reorg telemetry e2e tests:
telemetry/
|-- v2/
|-- api/
|-- policy/


out-of-memory error

Students cannot generate a html file by clicking Preview for 05_Manipulating_data.Rmd after answering all questions of this r module. RStudio throws an error saying “Error creating notebook pandoc document conversion failed with error 251”.
This should be an out-of-memory error, because, in order to answer all questions in this R module, we have to define about at least 15 large data matrices (usually 22758 *21) and it simply run out of the memory of Westminster RStudio when clicking Preview, even we can run large matrices chuck by chuck in the script.

We increased the memory available for Westminster's Rstudio Server accounts. Having said that, I need to find a better way to manage the large data frames in this module.

Okay, it looks like this issue is still an issue, even after the memory increase. Here's two behaviors I've seen today:

In my session (Chrome, OS X or Chromebook), pandoc gets through about the "arrange" section and then refuses to generate the rest of the notebook. See attachment.
In a student's session who was just in my office (Safari on OS X), not even the partial file is displayed -- just a blank screen pops up. I can see if I can get the student to export whatever got written to their .nb.html file before pandoc gave up.

I will also note that I don't seem to have any problems creating all the dataframes -- it isn't until pandoc tries to generate the notebook that I start running into memory issues.

That is curious. It's not clear why the dataframes can all exist in memory,
and yet the HTML file seems not to render. Weird. Anyway, like I said
before, I'll probably end up restructuring this assignment for next
semester.
On Wed, Sep 12, 2018 at 4:01 PM rhinopotamus<EMAIL_ADDRESS>wrote:

Okay, it looks like this issue is still an issue, even after the memory
increase. Here's two behaviors I've seen today:

In my session (Chrome, OS X or Chromebook), pandoc gets through
about the "arrange" section and then refuses to generate the rest of the
notebook. See attachment.
In a student's session who was just in my office (Safari on OS X),
not even the partial file is displayed -- just a blank screen pops up. I
can see if I can get the student to export whatever got written to their
.nb.html file before pandoc gave up.

I will also note that I don't seem to have any problems creating all the
dataframes -- it isn't until pandoc tries to generate the notebook that I
start running into memory issues.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/VectorPosse/Intro_Stats/issues/4#issuecomment-420812382,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHbNn_g4c5fXmohTOxq6MXnmV06dxYeuks5uaYQggaJpZM4WYFRX
.

Advice on what we should ask students to turn in for this assignment?


Bond Management Service missing?

I was trying to restrict who can connect over Bluetooth to a device. To my understanding (and I don't really have much understanding of Bluetooth) I would need to bind the connection. And that is what the "Bond Management Service" is for.
However, I couldn't find anything related to that in nrf-softdevice. Is that just missing, or is there another way to deal with this?

Added in #109


Fix git push error for protected CLA branch

The pull request is created from master636939717726645111 to master to fix git push error for protected CLA branch

@Taojunshen : Thanks for your contribution! The author, @corob-msft, has been notified to review your proposed change.


Do not force creation of _cargo-index repo on publish

Hello there,
Cargo Index over HTTP is now prefered over git for package updates: we should not force users who do not need the GIT repo to have the repo created/updated on each publish (it can still be created in the packages settings).
The current behavior when publishing is to check if the repo exist and create it on the fly if not, then update it's content.
Cargo HTTP Index does not rely on the repo itself so this will be useless for everyone not using the git protocol for cargo registry.
This PR only disable the creation on the fly of the repo when publishing a crate.
This is linked to #26844 (error 500 when trying to publish a crate if user is missing write access to the repo) because it's now optional.

I noticed in a instance of mine that a _cargo-index repo was created, even though I never published a cargo package to it (I did publish other packages though). Will this get rid of this creation?

I noticed in a instance of mine that a _cargo-index repo was created, even though I never published a cargo package (I did publish other packages though). Will this get rid of this creation?

Hello, from what I understood only 3 actions can trigger the repo creation: cargo publish or use of the Settings > Packages > Initialize/Rebuild Index.
Are you sure you did not use the 2 last buttons ? Might be worth creating a separate issue including commit log and the logs around the commits if you did not.

Ah, yes it might have been the Initialize/Rebuild Index button. Sorry, it's off-topic here :)

Could we know the protocol of the client side? maybe we should obey the client side protocol to do that. Sparse or not.
Or maybe we can retire old protocol entirely.

Could we know the protocol of the client side? maybe we should obey the client side protocol to do that. Sparse or not. Or maybe we can retire old protocol entirely.

We can't know this this unfortunately, I think we should push users toward using exclusively httpregistry, maybe remove all instructions to setup git registry and make it optional, then disable it entirely in a future version ?

Could we know the protocol of the client side? maybe we should obey the client side protocol to do that. Sparse or not. Or maybe we can retire old protocol entirely.

We can't know this this unfortunately, I think we should push users toward using exclusively httpregistry, maybe remove all instructions to setup git registry and make it optional, then disable it entirely in a future version ?

I would like the idea. As this PR, maybe we can have an option to enable/disable git registry. Maybe the default value could be false. So spare protocol could be the default one but git registry is optional.

Could you change the method name from AddOrUpdatePackageIndex to just UpdatePackageIndex then? (or a better name? TryUpdatePackageIndex, UpdateExistingPackageIndex, ...?)

Thanks for the feedback, I renamed it to UpdatePackageIndexIfExists.


After clearing Storage container LegalHold, delete storage account returns 409 Error

create storage account
create container
set legal holds
update legal holds
clear legal holds
destroy all
6.1 get container:
GET /subscriptions/.../resourceGroups/acctestRG-201023143421224156/providers/Microsoft.Storage/storageAccounts/acctestacc88429/blobServices/default/containers/vhds?api-version=2019-06-01 HTTP/1.1

Response:
{"id":"/subscriptions/.../resourceGroups/acctestRG-201023143421224156/providers/Microsoft.Storage/storageAccounts/acctestacc88429/blobServices/default/containers/vhds","name":"vhds","type":"Microsoft.Storage/storageAccounts/blobServices/containers","etag":""0x8D8771E1940016B"","properties":{"deleted":false,"remainingRetentionDays":0,"defaultEncryptionScope":"$account-encryption-key","denyEncryptionScopeOverride":false,"publicAccess":"None","leaseStatus":"Unlocked","leaseState":"Available","lastModifiedTime":"2020-10-23T06:37:22.0000000Z","legalHold":{"hasLegalHold":false,"tags":[]},"hasImmutabilityPolicy":false,"hasLegalHold":false}}
Date: Fri, 23 Oct 2020 06:37:55 GMT
Etag: "0x8D8771E1940016B"
Expires: -1
Pragma: no-cache
Server: Microsoft-Azure-Storage-Resource-Provider/1.0,Microsoft-HTTPAPI/2.0 Microsoft-HTTPAPI/2.0
Strict-Transport-Security: max-age=31536000; includeSubDomains
Vary: Accept-Encoding
X-Content-Type-Options: nosniff
X-Ms-Correlation-Request-Id: 9c17c7ce-af00-032b-8ba0-307aa9a5f31d
X-Ms-Ratelimit-Remaining-Subscription-Reads: 11976
X-Ms-Request-Id: c0ed5a57-21ae-48da-92ef-228f20ed0e58
X-Ms-Routing-Request-Id: SOUTHEASTASIA:20201023T063755Z:bf0f604d-9cb1-44e3-baf2-5418c8627fc5
6.2 container deleted successfully
DELETE /subscriptions/.../resourceGroups/acctestRG-201023143421224156/providers/Microsoft.Storage/storageAccounts/acctestacc88429/blobServices/default/containers/vhds?api-version=2019-06-01 HTTP/1.1
Response:
HTTP/2.0 200 OK
Date: Fri, 23 Oct 2020 06:38:00 GMT
Expires: -1
Pragma: no-cache
Server: Microsoft-Azure-Storage-Resource-Provider/1.0,Microsoft-HTTPAPI/2.0 Microsoft-HTTPAPI/2.0
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Ms-Correlation-Request-Id: 9c17c7ce-af00-032b-8ba0-307aa9a5f31d
X-Ms-Ratelimit-Remaining-Subscription-Deletes: 14999
X-Ms-Request-Id: df503eb9-7d57-49bd-9e26-df9a61c3f125
X-Ms-Routing-Request-Id: SOUTHEASTASIA:20201023T063800Z:dc201919-ed23-4dc2-8ac3-db79f5490f91
Content-Length: 0
6.3 account delete return 409 Error
DELETE /subscriptions/.../resourceGroups/acctestRG-201023143421224156/providers/Microsoft.Storage/storageAccounts/acctestacc88429?api-version=2019-06-01 HTTP/1.1
Response:
Date: Fri, 23 Oct 2020 06:38:01 GMT
Expires: -1
Pragma: no-cache
Server: Microsoft-Azure-Storage-Resource-Provider/1.0,Microsoft-HTTPAPI/2.0 Microsoft-HTTPAPI/2.0
Strict-Transport-Security: max-age=31536000; includeSubDomains
X-Content-Type-Options: nosniff
X-Ms-Correlation-Request-Id: 9c17c7ce-af00-032b-8ba0-307aa9a5f31d
X-Ms-Ratelimit-Remaining-Subscription-Deletes: 14999
X-Ms-Request-Id: 2d91e345-718a-48ba-8962-bedd998021b8
X-Ms-Routing-Request-Id: SOUTHEASTASIA:20201023T063802Z:a49c09e8-a612-417b-baf2-b98eddd774ee
{"error":{"code":"AccountProtectedFromDeletion","message":"Account acctestacc88429 Containers vhds have legal hold."}}

@zfchen95, @Himanshu Chhabra
It seems a server issue, would you please help to look?

Fixed: https://msazure.visualstudio.com/One/_git/Storage-SRP/pullrequest/3714293

Thanks @HimanshuChhabra


Added root folder copy task

Currently, we are not able to copy files to the root of the dist. This task copies files in the src/public folder to the root of the dist folder.
Note that I can't name the task public to follow the naming pattern since this is a property in JS.

I think this is OK, yesterday I made something alike https://bitbucket.org/mirabeau/abccd-website/commits/7078cb45329c4d823af7170a7ef41d4b7613357d, just named it root and you named it public, I am not sure which is better.

I agree with @colin-aarts. Can anybody think of other use cases next to robots.txt? Otherwise I think it’s good to close this PR.

No one came up with another use case so I'm closing this PR now


CDK-972: Add PartitionView

This was refactored out of #357.

@tomwhite could you take a look at this? This separated the PartitionView addition from the other PR and added tests. That ended up requiring some changes to the directory iterator code that I think should be looked at. Thanks!

Looks good, +1.

Thanks, Tom!


!secret support requires copies of secrets.yaml in each config directory

Home Assistant release (hass --version):
0.23.0
Python release (python3 --version):
3.4.2
Component/platform:
secrets (yaml.py, I think)
Description of problem:
If you use the !include annotation with a nested directory (e.g. notify: !include config/devices/notify.yaml) and then in THAT file use !secret, you need to copy (or symlink) your secrets.yaml file to that directory.  Otherwise, the app does not start and prints an error that the secret key is not defined.
Expected:
There should be only one secrets.yaml per project.
Problem-relevant configuration.yaml entries and steps to reproduce:
In configuration.yaml:
notify: !include config/devices/notify.yaml

In config/devices/notify.yaml
platform: googlevoice
username: !secret gvoice_username
password: !secret gvoice_password
name: gvoice

In secrets.yaml
gvoice_username: MY_USERNAME
gvoice_password: MY_PASSWORD

Enter the above values into the appropriate config files
Start the app
App quits with error that "Secret gvoice_username not defined"

Traceback (if applicable):
Secret gvoice_username not defined

Additionally, if you're using !include_dir_list, it then tries to consume the secrets.yaml, doesn't find the proper keys, and pukes spectacularly.

Its a bit by design at the moment, the secrets should be located in the dir where they are used, but didnt consider the includes. :-/
Let me add the ignore bit and see if there is an elegant way to fall back to the main dir secrets.yaml


image thumbnails

I would definitely love to see image thumbnails also embedded in the project. It would be awesome

Hi @azerafati are you referring to thumbnails for image files?
how do u think? replacing icons??
Regards

yea, it would be great to see small versions on the images instead a of their icon so to find them more easily. I really enjoyed this work and plan to use it in one of my projects, so I guess I can work on that part. I'll give it a try

Great, Also I think about doing something like
https://codepen.io/tevko/pen/DdsnK
Or just use css class as extension, for example like this one:
https://gist.github.com/gschoppe/08a814043da5e5f02f5c#file-file-format-icons-css

wow the second one was so clever, but for images really a thumbnail would be so much better

@azerafati I just added file extension in icons for the moment.. You can check in http://angular-filemanager.zendelsolutions.com/ (large icon view)

@joni2back no that commit doesn't resolve this. Those Icons are awesome but I meant image thumbnails. That's totally necessary too
like this,
http://ckeditor.com/apps/ckfinder/3.3.0/ckfinder.html?Type=Images&CKEditor=editor1&CKEditorFuncNum=0&langCode=en

@joni2back i need this feature too.
plz reopen this issue and help us

@joni2back I would also love to see thumbnails supported natively in this project.


Content integration

Fetching from Github
Lot's of tiny fixes and refinements for Integration with sample projects.

Looking good!


Potential fix for cell caching issue

I'm by no means an expert in PowerShell, but did some debugging through the kernel to try and understand the heuristic used to determine when outputs are complete for a given cell.
It looks the kernel looks for a '^' to determine the above condition. The trouble is, for multiline cell sources, it appears that n '^' characters will be returned, where n is the number of lines in the cell's source.
So, I'm just keeping track of the number of lines in the source, and only setting the stop_flag to True when the expected carets goes below 1.

if (((Get-History).({ $_.ExecutionStatus -notin 'Completed', 'Stopped' }) |
measure).Count -eq 0) {
"No runniing commands!"
}
may be interesting, but then we're polling at the end, which seems not ideal.

I was thinking more about it today too, I think there is an easy workaround.
We should be able to wrap the whole cell in the & {...} block. That would guarantee that there is a single output command.
If anybody wants to try out this solution and let me know does it work / send PR, that would be awesome (and a strong point for becoming a potential maintainer, see #16 ).

Thanks @vors! Let me try this out and I'll get back to you 😄

@vors I tested this and couldn't find any issues. Attached a simple notebook that exhibited symptoms before the fix, and doesn't appear to have the same issues afterwards.
I reached out to @SQLVariant previously around notebooks that also had issues previously, and they didn't repro afterwards.
Deferring to your expertise here, but this definitely looks promising 😄
Archive.zip

Awesome, looks like we figured it out. 👍

Hi @vors, we are super excited about this kernel, and so many people are excited to see this in Powershell notebooks. Do you think you can help us make this possible with a new release?

I tried to make a quick release, but turned out that I don't remember how :D #18 I hope somebody who can become a maintainer can step up and help.


some bugfixes

related to https://github.com/sensiolabs-de/deptrac/pull/373

@smoench Thank you very much for looking into this, updating to the latest development version makes perfect sense!
I've just filed #58 which contains similar changes and also improves compatibility with all supported versions.
Keep it up :+1:


Leverage the pre-built images as the default way to start Guardian locally

Problem description
Multiple users want to run Guardian without major changes and start testing it locally quickly. The default option is to use docker to build from scratch any images. That takes time and, on specific hardware configurations, that can also lead to problems not trivial for new developers to fix.
Leveraging the pre-built images is a fast and ready solution for that.
At the moment, the repo does not contain a pre-build docker compose file, but a template to start from is present in the documentation (https://docs.hedera.com/guardian/guardian/readme/getting-started/installation/building-from-pre-build-containers)
Requirements

Update docker-compose.yml to leverage pre-built images from the latest release
Create a docker-compose-build.yml with the same content as the current docker-compose.yml file to allow developers to build images locally via docker
Update the docs accordingly

Definition of done

Leveraging the docker pre-built images is the default option for running Guardian from scratch
If developers follow the documentation, the shortest path leads them to start docker containers leveraging the pre-built images.
The documentation provides information about how to proceed if developers want to build the docker images locally instead.

Additional context
Here an example of the docker-compose.yml file I'm currently using for the purpose above:
services:
  mongo:
    image: mongo:6.0.13
    command: "--setParameter allowDiskUseByDefault=true"
    restart: always
    expose:
      - 27017

  mongo-express:
    image: mongo-express:1.0.2-20
    expose:
      - 8081
    environment:
      ME_CONFIG_MONGODB_SERVER: mongo
      ME_CONFIG_MONGODB_PORT: 27017
      ME_CONFIG_SITE_BASEURL: /mongo-admin # default credentials: admin/pass
    depends_on:
      - mongo

  ipfs-node:
    image: ipfs/kubo:v0.26.0
    ports:
      - "5001:5001"
      - "4001:4001"
      - "8080:8080"
    volumes:
      - ipfs_data:/data/ipfs:rw
      - ipfs_export:/export:rw

  message-broker:
    image: nats:2.9.24
    expose:
      - 4222
    ports:
      - '8222:8222'
    command: '--http_port 8222'

  vault:
    image: hashicorp/vault:1.12.11
    expose:
      - 8200
    ports:
      - '8200:8200'
    environment:
      VAULT_SERVER: "http://<IP_ADDRESS>:8200"
      VAULT_DEV_ROOT_TOKEN_ID: "1234"
    cap_add:
      - IPC_LOCK
    volumes:
      - ./file:/vault/file:rw
      - ./config:/vault/config:rw

  notification-service:
    image: gcr.io/hedera-registry/notification-service:2.23.1
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    depends_on:
      - message-broker
    environment:
      - GUARDIAN_ENV=${GUARDIAN_ENV}
    volumes:
      - ./notification-service/configs:/usr/local/notification-service/configs:ro

  logger-service:
    image: gcr.io/hedera-registry/logger-service:2.23.1
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    depends_on:
      - message-broker
    environment:
      - GUARDIAN_ENV=${GUARDIAN_ENV}
    expose:
      - 6555
    volumes:
      - ./logger-service/configs:/usr/local/logger-service/configs:ro

  worker-service:
    image: gcr.io/hedera-registry/worker-service:2.23.1
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    depends_on:
      ipfs-node:
        condition: service_healthy
      auth-service:
        condition: service_started
    environment:
      - GUARDIAN_ENV=${GUARDIAN_ENV}
    expose:
      - 6555
    volumes:
      - ./worker-service/tls:/usr/local/worker-service/tls:ro
      - ./worker-service/configs:/usr/local/worker-service/configs:ro
    deploy:
      replicas: 2

  auth-service:
    image: gcr.io/hedera-registry/auth-service:2.23.1
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    ports:
      - '5005:5005'
    volumes:
      - ./auth-service/tls:/usr/local/auth-service/tls:ro
      - ./auth-service/configs:/usr/local/auth-service/configs:ro
    depends_on:
      - mongo
      - vault
      - message-broker
      - logger-service
    environment:
      - GUARDIAN_ENV=${GUARDIAN_ENV}
    expose:
      - 6555
      - 5005

  api-gateway:
    image: gcr.io/hedera-registry/api-gateway:2.23.1
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    expose:
      - 3002
      - 6555
    depends_on:
      - mongo
      - message-broker
      - guardian-service
      - auth-service
      - logger-service
    environment:
      - GUARDIAN_ENV=${GUARDIAN_ENV}
    volumes:
      - ./api-gateway/configs:/usr/local/api-gateway/configs:ro

  ai-service:
    image: gcr.io/hedera-registry/ai-service:2.23.1
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    expose:
      - 3013
    depends_on:
      - mongo
      - message-broker
      - logger-service
    volumes:
      - ./ai-service/data:/usr/local/ai-service/data:rw
    environment:
      - GUARDIAN_ENV=${GUARDIAN_ENV}
      - VECTOR_STORAGE_PATH=./faiss-vector
      - DOCS_STORAGE_PATH=./data/generated-data

  policy-service:
    image: gcr.io/hedera-registry/policy-service:2.23.1
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    ports:
      - "5006:5006"
    depends_on:
      - mongo
      - message-broker
      - auth-service
      - logger-service
    environment:
      - GUARDIAN_ENV=${GUARDIAN_ENV}
    expose:
      - 50000-60000
      - 5006
    volumes:
      - ./policy-service/tls:/usr/local/policy-service/tls:ro
      - ./policy-service/configs:/usr/local/policy-service/configs:ro

  guardian-service:
    image: gcr.io/hedera-registry/guardian-service:2.23.1
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    ports:
      - "5007:5007"
    volumes:
      - ./guardian-service/tls:/usr/local/guardian-service/tls:ro
      - ./guardian-service/configs:/usr/local/guardian-service/configs:ro
    depends_on:
      - mongo
      - message-broker
      - auth-service
      - logger-service
      - worker-service
      - policy-service
    environment:
      - GUARDIAN_ENV=${GUARDIAN_ENV}
    expose:
      - 6555
      - 5007

  application-events:
    image: gcr.io/hedera-registry/application-events:2.23.1
    ports:
      - "3012:3012"
    depends_on:
      - mongo
      - message-broker
      - guardian-service
      - auth-service
      - logger-service
    expose:
    - 3012

  mrv-sender:
    build:
      context: .
      dockerfile: ./mrv-sender/Dockerfile
    init: true
    ports:
      - "5008:5008"
    expose:
      - 3003
      - 5008

  topic-viewer:
    build:
      context: .
      dockerfile: ./topic-viewer/Dockerfile
    init: true
    expose:
      - 3006
      - 5009
    ports:
      - "5009:5009"

  web-proxy:
    build:
      context: .
      dockerfile: ./web-proxy/Dockerfile
    init: true
    ports:
      - "3000:80"
    depends_on:
      - guardian-service
      - auth-service
      - api-gateway
      - mrv-sender
      - mongo-express

  prometheus:
    image: prom/prometheus:v2.44.0
    restart: unless-stopped
    volumes:
      - ./prometheus.yml:/etc/prometheus/prometheus.yml
      - prometheus_data:/prometheus
    command:
      - '--config.file=/etc/prometheus/prometheus.yml'
      - '--storage.tsdb.path=/prometheus'
      - '--web.console.libraries=/etc/prometheus/console_libraries'
      - '--web.console.templates=/etc/prometheus/consoles'
      - '--web.enable-lifecycle'
    ports:
      - "9090:9090"
    networks:
      - monitoring

  grafana:
    image: grafana/grafana:10.0.10
    volumes:
      - grafana_data:/var/lib/grafana
      - ./grafana/provisioning:/etc/grafana/provisioning
      - ./grafana/dashboards:/etc/grafana/dashboards
    environment:
      - GF_AUTH_DISABLE_LOGIN_FORM=true
      - GF_AUTH_ANONYMOUS_ENABLED=true
      - GF_AUTH_ANONYMOUS_ORG_ROLE=Admin
      - GF_SERVER_HTTP_PORT=9080
      - GF_DASHBOARDS_DEFAULT_HOME_DASHBOARD_PATH=/etc/grafana/dashboards/prometheus-dashboard.json
    ports:
      - "9080:9080"
    networks:
      - monitoring

volumes:
  prometheus_data:
  grafana_data:
  ipfs_data:
  ipfs_export:

networks:
  monitoring:
    driver: bridge

Can confirm building from scratch was (and continues to be) a hurlde for me.
That said, the pre built docker images are not available for ARM so the docker-compose you posted will not work for some Macs and other non x86 machines.

Yes, that example is for Linux, but you can make it work for M1 by adding the platform: linux/amd64 after the image attribute.
See docs here: https://docs.hedera.com/guardian/guardian/readme/getting-started/installation/building-from-pre-build-containers#docker-compose-configuration-for-apple-m1-using-images
  guardian-service:
    image: gcr.io/hedera-registry/guardian-service:2.23.1
    platform: linux/amd64
    env_file:
      - ./configs/.env.${GUARDIAN_ENV}.guardian.system
    ports:
      - "5007:5007"
    volumes:
      - ./guardian-service/tls:/usr/local/guardian-service/tls:ro
      - ./guardian-service/configs:/usr/local/guardian-service/configs:ro
    depends_on:
      - mongo
      - message-broker
      - auth-service
      - logger-service
      - worker-service
      - policy-service
    environment:
      - GUARDIAN_ENV=${GUARDIAN_ENV}
    expose:
      - 6555
      - 5007

In that way, you are actually running the container in virtualization mode, so not the best for performance but enough for local development.

We can definitely think about introducing also a specific build for ARM chip, but I think we need to tweak with the GitHub build pipeline, I'm not sure GitHub already offer a MacOS env for the build. It's worth digging more.


Update Banner of the Falcon to Ver. 1.2

Design Team require an update for Banner of the Falcon:

Banner of the Falcon (Ver. 1.2)
[neutral] Agenda
Banner. House Arryn.
You cannot include non-neutral locations in your deck.
While each opponent has a higher initiative value than you, each House Arryn character you control gets +1 STR.

For reference, here is the previous version of this card:

Banner of the Falcon (Ver. 1.1)
[neutral] Agenda
Banner. House Arryn.
Increase the cost of the first in-faction card each player plays, ambushes or brings out of shadows each round by 1.
While each opponent has a higher initiative value than you, each House Arryn character you control gets +1 STR.

General steps

[x] Update the code for this card (within 'server/game/cards/{current pack}')
[ ] (Optional) Test the implementation locally
[x] Create Pull Request to develop branch, linking this issue in the description as 'Closes: #[this issue]'

Alternatively, it will also be automatically closed once this card is marked as "Implemented" on the spreadsheet.

Updated throneteki-deck-helper as well; files ready to be pushed to aws instance


developers should not receive deprecation warnings about things in the core language.

Premise:
Compiler warnings are instructions to the developer about failings in their application that should be addressed.
Compiler warnings should NOT warn the developer about deprecations the language creators haven't gotten around to addressing yet.
Problem:
I just built my app and received this warning:
In /usr/local/Cellar/crystal/0.32.1/src/uri/encoding.cr:116:3

 116 | def self.unescape(string : String, plus_to_space = false)
       ^-------
Warning: Deprecated URI.unescape. Use .decode or .decode_www_form instead

A total of 1 warnings were found.

This is not a problem in my software.  Developers like me, should receive warnings about things we can address in our apps, but not about failings in the core language.
I'm not sure if this is actually possible, but it'd be awfully nice.
Crystal 0.32.1 (2019-12-18)

LLVM: 9.0.0
Default target: x86_64-apple-macosx

Are you sure this isn't an issue in your app or a shard that your app requires?
I built the compiler with warnings and didn't see any.

This is a deprecation warning.
Something is calling the deprecated URI.unescape, either your app or a shard does.

Yes but the error message is pointing to the method definition, not the callsite.
This is a bug.

@ysbaddaden  & @Blacksmoke16
entirely possible (maybe even probable), but as @RX14 pointed out, the error message is pointing to the wrong place which led me to think it was something in encoding.cr that was having the issue not something in my code.
I think the right thing to do here is to kill this ticket and create a new, more accurate one, about the warning pointing to the wrong place.   Yes?

That's odd, seems to work fine here:
In src/view_helpers.cr:15:24

 15 | google_search = URI.escape(url.name + " poster", true)
                          ^-----
Warning: Deprecated URI.escape. Use .encode or .encode_www_form instead

So yeah I'd file a new bug for it...with a simplified reproducible test case :)

Building
# foo.cr
require "uri"

URI.escape("foo")

leads to
$ ./bin/crystal build foo.cr
In foo.cr:3:5

 3 | URI.escape("foo")
         ^-----
Warning: Deprecated URI.escape. Use .encode or .encode_www_form instead

In src/uri/encoding.cr:174:3

 174 | def self.escape(string : String, space_to_plus = false)
       ^-----
Warning: Deprecated URI.escape. Use .encode or .encode_www_form instead

A total of 2 warnings were found.

The issue is that the compiler generates a method to introduce the default argument.

A minimalistic example is:
@[Deprecated]
def m(arg = 0)
end

m

$ ./bin/crystal build foo.cr
In foo.cr:5:1

 5 | m
     ^
Warning: Deprecated top-level m.

In foo.cr:2:1

 2 | def m(arg = 0)
     ^
Warning: Deprecated top-level m.

A total of 2 warnings were found.

Since it is equivalent to
@[Deprecated]
def m
  m(0)
end

@[Deprecated]
def m(arg)
end

m

Hence, the two calls m and m(0) to depreceated method.
To fix this the Def AST needs:

to have a property  that is an expansion by the compiler and
set that property when expanding default args
And use that as a filter when checking for deprecation warnings

As a workaround,

expand manually the default args, or
ignore std-lib in the warnings path crystal build --exclude-warnings=/usr/local/Cellar/crystal/0.32.1/src foo.cr

@bcardiff The explanation seems to fit, but what's the original cause for URI.escape being called at all? In your example the compiler warns about a deprecated call in foo.cr:3:5 which calls the method with default argument and this autogenerated method calls the declared method, causing the second deprecation warning.
In the OP, there is not primary deprecation warning. Any idea what could be the cause for this? @masukomi I'm assuming you've posted all deprecation warnings? Could you share the code that triggered this?


Fluent configuration slow

Example:
public class NullMappings: Mappings { }

...

var mappings = new NullMappings();
var fluentConfig = FluentMappingConfiguration.Configure(mappings);
var factory = DatabaseFactory.Config(x =>
{
    x.UsingDatabase(() => new NPoco.Database(...));
    x.WithFluentConfig(fluentConfig);
});

for (int i = 0; i < 1000; i++)
{
    using (var db = Factory.GetDatabase())
    {
        c = db.FirstOrDefault<Customer>(@"select C.* from Customers C where C.Id = @0", i);
    }
}

This takes ~5s on my machine and ~0.5s when the line x.WithFluentConfig(fluentConfig); is commented out. This does not occur in v2. Also, v2 is ~1.5 times faster (w/o fluent config).

Not sure about this one. 5s does seem way too long. We are not seeing that with our production instance.

Is it possible to create a console application which you can attach that reproduces this issue?

Sure: NPocoTest.zip
The included .mdf is a SQL Server 2016 LocalDB database file. You'll have to change the connection string in the app.config.
Here's the output on my machine (a different one from the one mentioned above, also 5000 iterations instead of 1000):
Fluent: 00:00:09.0168663
Non-fluent: 00:00:05.6720920

I'm not sure if the DB schema and the Customer POCO class were the same as in the initial comment. There may have been more columns/properties.

I have found the issue, however i'm not sure why you would be getting 1000 instances of database. I understand 1000 queries against a DB.
Anyways, here was my results from your program with NPoco 3.4.3

Thanks 👍 The example is just for illustration purposes. In a real single-threaded application you'd perform 1000 queries using a single Database instance, but I stumbled upon this problem when using NPoco 3 in a web application where you create a Database instance for each request.


Different types of face detection techniques.

Ex. 1 Using DL. 2 .Computer vision or anything else you want to add..

I would like to use MTCNN to perform facial detection model using deep learning and cascade classifier for detection using opencv.
can you please assign me the task.

@Niketkumardheeryan can I work upon this ?

Is there any issue to be addressed??


Use docsy with deps via NPM not git submodules

The site builds cleanly even after resetting the cache. For details, see the Netlify log.


[FEAT]Soft line break

Shift-Enter   Soft line break
Newline but does not generate new bullets

Example in Markdown
 * A
          * B
            BBB
          * C

Ref https://github.com/vslinko/obsidian-outliner/discussions/52

@5eagull @danieltomasz and everyone else!
After a lot of work, I finally released the first beta version of soft line break support!
I am looking for beta testers for this version. Please download the beta version and report your feedback.

Great! Good news! I copied the beta plugin files, it works with Enter + Shift,  but it still shows me 1.1.12 release number

@danieltomasz it’s okay

I didn't find any problem so far. I just have an suggestion: will it be better if you remove the indent before blockquotes? It seems that you indent blockquotes with 4 spaces, which makes it align to the next-level bullet. I think it may be a little confusing.

I'm really glad to hear the update by the way

I didn't find any problem so far. I just have an suggestion: will it be better if you remove the indent before blockquotes? It seems that you indent blockquotes with 4 spaces, which makes it align to the next-level bullet. I think it may be a little confusing.

I think this is in general how the quotes are handled by CSS in Obsidian and it is not  something caused by plugin;
Maybe it would be good to have toggle in setting for changing CSS for quotes, I dont know if is possible that change only affect quotes in soft line break, in worst case there the CSS may  affect all quotes and I dont know how many  would expect that

I didn't find any problem so far. I just have an suggestion: will it be better if you remove the indent before blockquotes? It seems that you indent blockquotes with 4 spaces, which makes it align to the next-level bullet. I think it may be a little confusing.

I think this is in general how the quotes are handled by CSS in Obsidian and it is not something caused by plugin;
Maybe it would be good to have toggle in setting for changing CSS for quotes, I dont know if is possible that change only affect quotes in soft line break, in worst case there the CSS may affect all quotes and I dont know how many would expect that

I rarely use blockquotes so I just realized the blockquotes are intended even if I don't use bullet list. Now I think it's okay to keep it that way. Thank you!

@vslinko  I obseved weird behaviour, I have this in outline in my vault(I removed some personal notes, but the structure of the outline is the same), I cannot outdent the last bullet point (I am using Outliner 1.2)
- Thinking in Systems
	-  Line 1
		- LIne 2
	- Line 3
	- Nie m liniowych systemow

	- Random link from Internet
		[Swasthi's Recipes - Indian food blog with easy Indian recipes](https://www.indianhealthyrecipes.com/)
	- Cannot move this line with Tab + Shift

@danieltomasz thank you for your feedback. I’ve already released it. Could you please create new issue.

Done!


Can not reference result by key

I have the following data in a CSV file(actually, my real data is larger but this is a good simplification):
ColumnA,ColumnB
1,X
5,G
9,F

I am reading it the following way, where url is the location of the file:
    val rawData = sqlContext.read
      .format("com.databricks.spark.csv")
      .option("header", "true")
      .option("inferSchema", "true")
      .load(url)

Then, I am applying a map on it:
    val formattedData = rawData.map(me => me("ColumnA") match {
        //some other code
      })

However, when I am referencing the column like this: me("ColumnA") I am getting a type mismatch:
Type mismatch, expected: Int, actual: String
Why is this occurring? Shouldn't every row of rawData be a Map?

https://spark.apache.org/docs/latest/api/java/org/apache/spark/sql/DataFrame.html#map(scala.Function1, scala.reflect.ClassTag)
Returns a new RDD by applying a function to all rows of this DataFrame.  So you are trying to reference the columns of the dataframe by name, but inside the map method, it operates on Row, so you need to reference the columns by index position.
val formattedData = rawData.map(me => me(0) match {
     case 1 => "yes"
     case _ => "default"})


HADOOP-17993. Disable JIRA plugin for YETUS on Hadoop

Description of PR
The jira-json goes missing all of a sudden and we get the following error in the Jenkins CI run -
[2021-10-27T17:52:58.787Z] Processing: https://github.com/apache/hadoop/pull/3588
[2021-10-27T17:52:58.787Z] GITHUB PR #3588 is being downloaded from
[2021-10-27T17:52:58.787Z] https://api.github.com/repos/apache/hadoop/pulls/3588
[2021-10-27T17:52:58.787Z] JSON data at Wed Oct 27 17:52:55 UTC 2021
[2021-10-27T17:52:58.787Z] Patch data at Wed Oct 27 17:52:56 UTC 2021
[2021-10-27T17:52:58.787Z] Diff data at Wed Oct 27 17:52:56 UTC 2021
[2021-10-27T17:52:59.814Z] awk: cannot open /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-3588/centos-7/out/jira-json (No such file or directory)
[2021-10-27T17:52:59.814Z] ERROR: https://github.com/apache/hadoop/pull/3588 issue status is not matched with "Patch Available".
[2021-10-27T17:52:59.814Z]

The hadoop-multibranch pipeline doesn't use ASF JIRA, thus, we're disabling the jira plugin to fix this issue.
How was this patch tested?
In progress.
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

@aajisaka could you please review this PR?

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
8m 12s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
shelldocs
0m  0s

Shelldocs was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

_ branch-3.2 Compile Tests _

+0 :ok:
mvndep
3m 28s

Maven dependency ordering for branch

+1 :green_heart:
shadedclient
16m 14s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 17s

Maven dependency ordering for patch

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
shellcheck
0m  0s

No new issues.

+1 :green_heart:
shadedclient
14m  2s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
asflicense
0m 35s

The patch does not generate ASF License warnings.

44m 57s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3624/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3624

Optional Tests
dupname asflicense codespell shellcheck shelldocs

uname
Linux 4e1934633265 4.15.0-156-generic #163-Ubuntu SMP Thu Aug 19 23:31:58 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.2 / b866a04c4a4e8a14f970f361f68237b884a8df04

Max. process+thread count
429 (vs. ulimit of 5500)

modules
C:  U:

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3624/1/console

versions
git=2.17.1 maven=3.6.0 shellcheck=0.4.6

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Added examples, and moar tests

Gulp also now outputs a concatenated js file. I'll add later something that runs the tests on non-concatenated files so we have a fine coverage report. This PR is kind of a WIP, though, but hey, it's a dev branch, eh ? :-)

awesome, thanks for you great work! My only remark is on the way we run the unit-tests; I think we should make them as easy and encapsulated as possible.
And actually, I think it would be a good idea to continue to support the data attribute with the 'old' format in addition to the datasets attribute with the new array-style format.

Sure !

nice, it looks great now :) I will merge it

:metal:

Coverage increased (+29.51%) to 80.31% when pulling b21f52131274abf1d2f62a685050b03153f2b813 on dev-tmp into 6fab6970b7c71625165a6e69f4ecc3a257af3a05 on dev.

Coverage increased (+29.51%) to 80.31% when pulling 3966d53556bba3c26eb20b3141dbebe1d10d083d on dev-tmp into 6fab6970b7c71625165a6e69f4ecc3a257af3a05 on dev.


docs(identity): fix wrong link to logging

Packages impacted by this PR
@azure/identity
Issues associated with this PR
None
Describe the problem that is addressed by this PR
Wrong documentation link
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Replace Link, chosen because lowest effort
Adapt Readme
Are there test cases added in this PR? (If not, why?)
No, because just docs
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[x] Added impacted package name to the issue description
[x] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[x] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.

Thank you for the contribution! This is an improvement for sure but I do wonder if we should point directly to the @azure/logger README as it better describes the environment variable to use and how to enable logging. What do you think @Makoehle ?
https://github.com/Azure/azure-sdk-for-js/tree/main/sdk/core/logger


Posting a group with an absolute path does not work.

=========================
HTTP request:
POST http://mesos.vm:8080/v2/groups
headers=
Accept: application/json
User-Agent: gatling
Content-Type: application/json
Content-Length: 38
Connection: keep-alive
Host: mesos.vm:8080
stringData={ "id": "/marathon/integration/test" }
=========================
HTTP response:
status=
422
headers=
Content-Type: [application/json]
Transfer-Encoding: [chunked]
Server: [Jetty(8.y.z-SNAPSHOT)]

{
  "errors": [
    {
      "attribute": "id",
      "error": "identifier /marathon/integration/test is not child of /. Hint: use relative paths."
    }
  ]
}

Let's verify whether this is still an issue.


quantile_test.py is not run at all with bazel #1202

fixes #1202 #1201

I have no idea how to solve the failing test (publish wheels to PyPi). There is some url that cannot be reached.

I have no idea how to solve the failing test (publish wheels to PyPi). There is some url that cannot be reached.

Yeah that's not on your end. The internet has been quite flaky these past couple of weeks. I've retriggered the tests.

Now the tests are passing except for one that does not depends on my changes:

I seems we merged the tf.compat.v1 check at the same time that we merged another pull request adding a tf.compat.v1. That's bad timing haha. Let me fix that. Thanks again for your pull request!


merge package template from arlac77/npm-package-template

Updated standard to latest version

Codecov Report

Merging #616 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master    #616   +/-   ##
======================================
  Coverage    62.5%   62.5%
======================================
  Files           1       1
  Lines           8       8
======================================
  Hits            5       5
  Misses          3       3

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 933a370...d352dad. Read the comment docs.


Default value applied twice when grouping options within a multiple select field

Package
filament/forms
Package Version
v3.0.60
Laravel Version
v10.24.0
Livewire Version
v3.0.5
PHP Version
PHP 8.1.2
Problem description
When setting the default value of a multiple select field that has grouped options, the default value is applied twice.

When the options are not grouped, the default value is applied in the expected way.

Expected behavior
I expect just one instance of the default value to be applied.
Steps to reproduce
Simply create a form with a Select Field that has grouped options, multiple select, and a default value. Example below:
Select::make('Multi-Select with Grouped Options')
                    ->options([
                            'Group 1' => [
                                    'option_1' => 'Option 1',
                                    'option_2' => 'Option 2',
                                    'option_3' => 'Option 3',
                                    'option_4' => 'Option 4'
                                ],
                            'Group 2' => [
                                'option_5' => 'Option 5',
                                'option_6' => 'Option 6',
                                'option_7' => 'Option 7',
                                'option_8' => 'Option 8',
                        ]
                    ])
                    ->multiple()
                    ->default(['option_2']),

Reproduction repository
https://github.com/EthosLuke/filament-select-group-bug
Relevant log output
No response

I'm having the issue.

I have this issue too. It is not only the default value, it also happening for manually selected values (e.g. in a multiselect filter with option groups). If you select an option and then reload the page and open the filter again the selected options are there twice.


How to pass Mustache in link in ASP.NET??

Hello All,
I am using ASP.NET 4.5 Web application using Mustache js.
In one of my requirement I am pass mustache value by query string like
{{OrderCount}}
here output is : requester=abc
It is actual result which I want.
It's working fine but when I try to pass by following way::
<a href='Record.aspx??<%=WebUtility.GetEncryptedQueryString("requester={{ClientName}}")%>'>{{OrderCount}}
When I decrypt It's getting like "requester={{ClientName}}" instead of "requester=abc".
Here 'abc' is ClientName.
Can Any one help me immediately?
Thanks in Advance

It would be helpful with more info about your current setup, e.g. what mustache libraries are you using?
Assuming your first successful example is pure client side HTML and JavaScript with mustache.js, the second example is something quite different. When you utilize <%=WebUtility.GetEncryptedQueryString("requester={{ClientName}}")%> you're suddenly in the world of ASP.NET, not JavaScript.
Are you using Nustache or ASP to support mustache when in C#/ASP?

As the current maintainer of Nustache it doesn't seem to be using that. I would guess in this case WebUtility.GetEncryptedQueryString is returning requester={{ClientName}} and it's not being interpolated by anything.
As @phillipj requested more information about what you're using to template would help

Thanks @Romanx!

Hi,
I am using "ASP".And mustache 0.8.1 download from GitHub. And I want to pass Query string parameter in encrypted form,so I use second case


Logging and Auditing

Add the ability to log moloch actions/queries into ES.  Will be usable both as a history for a user and for audit for an admin.
Data to log:

user
api or tab used
query
view if used
timestamp
maybe number of results?
on some tabs/api should the fields requested

Features

Should be able to set an expire time
db.pl maybe does the expire during other expires?

Normal user view:

See list of queries
sort on different columns
filter based on search box
can click and go to an item
would be nice to "favorite" an item and add to a favorite bar or something

Admin user view:

Same as user view but all users
a way to show just a single user by something in the filter, maybe "@username"
ability to delete items

Examples:

Searches on sessions tabs
Export of pcap
add/remove of users (doesn't have to be reproduceable)

First version in 53bcd0691e71dc698f9444fce35b80e02cf17176 more coming in phase 2 #734


Difference in citation of variables in a code

[Enter feedback here]
In the line: "You should configure the "empLocation" and "deptLocation" paths so that on the storage account they point to your desired location to save generated data files." two variables are used -- empLocation and deptLocation. However, the code following this line shows different variable names: emp_Location and dep_Location.
Please check and clarify. Thanks.

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

ID: 16beb7c6-13b1-647e-0a5f-811eb903b5af
Version Independent ID: 2ebbdad8-526c-bf71-66d7-ebb5b0ab0769
Content: Hyperspace indexes for Apache Spark - Azure Synapse Analytics
Content Source: articles/synapse-analytics/spark/apache-spark-performance-hyperspace.md
Service: synapse-analytics
Sub-service: spark
GitHub Login: @ekote
Microsoft Alias: eskot

@Keerthin9
Thanks for your feedback! We will investigate and update as appropriate.

@Keerthin9
Thank you for bringing this to our attention! We've initiated a pull request (PR) to address this issue. Once the author reviews the changes, they will be merged, and the updates should go live shortly. Your diligence is much appreciated!


Increment versions for databoxedge releases

Increment package versions for databoxedge releases

API change check
API changes are not detected in this pull request.


Application version not stored in the database

It would be ideal if there was a placeholder in the database to store the version of the ARMI application that was run. See:
https://github.com/terrapower/armi/blob/9de4be8b706a3b4ef96d78b57632fb3130bf3114/armi/bookkeeping/db/database3.py#L215

I believe it will be hard to get ARMI to know about the Application (which is outside it).  But an ARMI Application could certainly call an ARMI function to write the Application version/hash into the DB.  That seems fine.
ACTUALLY
We already finished this ticket in another way. Have you seen this?

Wait, are the settings not saved to the DB?

They are saved to the database, but at the surface it is difficult to assess which version of the code was used to generate the database. I saw that you added an option in the settings to store this, but it would be nice if the database itself stored this data directly. The reason this is coming up is that someone passes a database to someone else they don't immediately know the version. Additionally, when we run integration tests it would be nice to know when the last rebaselined version was generated.

If version data is provided as settings (like discussed in #1267), then this is done automatically, right?

If version data is provided as settings (like discussed in #1267), then this is done automatically, right?

Yup!
The tickets are heavily intertwined.

I think that this ticket might still be open (or at least from my perspective it should be). I think have version in the settings file adds something but it's not tied to the same release version number (or forced to) based on some git history or setup.py version. Basically for database migrations we still need the version number and maybe this is just opening up the settings stored in the DB and getting the version string from there but that seems fragile.
Thoughts @opotowsky and @john-science?

Presume I'm clueless ;-)
What's the difference between opening the db to get the version via h5db.attrs["version"] and getting it via h5db["inputs/settings"]?

You're right about the validation piece though. I can have versions: armi: 0.8000.1 in my settings and if I'm running armi 0.2.7 nothing will fail. When we want this perhaps to also validate the version bein run, correct?

We will not be removing the setting, as suggested in your option (1).  Here are three reasons:

Numerous people people have requested this feature.

The feature is used.

ARMI output traceability.

As a fun example, in meteorological and climate modeling the standard of best practice is to store the versions of software you are using in your configuration and output files. I agree with that standard. If in 3 years you're looking at an ARMI output database, and you don't know what version of ARMI that was used to generate it, the value of that output DB is greatly reduced.

Database Migrations.

How could we possibly do database migration if we don't know the versions?
You can not see it yet, but the upcoming re-design for the armi/migration/ module depends on this setting.

Sure, (2) is an interesting idea.  We can do that.  Open a new ticket. (However, if your concern is just that this setting is not used, the DB migration redesign is on the Roadmap.)

I support keeping the version in the DB, just that we actually make it useful. The concern is not that the setting is unused, but rather it's current use is confusing.
I will open a new ticket!

I support keeping the version in the DB, just that we actually make it useful. The concern is not that the setting is unused, but rather it's current use is confusing.

Again, it will be used in the database migration, but that work was postponed with all other ARMI work.


Refactor ui and di packages

Coverage remained the same at 14.514% when pulling 7b983fe18180ae6d1aa24d2b9753b064027bdd70 on package-refactor into a5543759a4093481f924d5debef034dfc5007aa7 on master.


create token on master, and check for empty master endpoint

WIP - Please see my TODO comments, it's pretty rough but working.  I'd like to have David's PR 69 merged first as well.

We could merge this, it is ready to try out.  We will need to build images based on this for integration testing with the CMA.

There are still TODOs that can be done later


Adjust spacing between Bottom Navigation items

Overview
The spacing between items in the Bottom Navigation bar is currently too narrow. We need to widen it to match the design specifications.

Links

Design: https://www.figma.com/design/XUk8WMbKCeIdWD5cz9P9JC/DroidKaigi-2024-App-UI
Code: https://github.com/DroidKaigi/conference-app-2024/blob/35ff30ea65796d02a286f1f2fd3623bce7a74e15/feature/main/src/commonMain/kotlin/io/github/droidkaigi/confsched/main/MainScreen.kt#L175

🙋

Thanks! Assigned 👍


Bug when installing MRTK and MRTK examples

So I've installed the latest version: HoloToolkit 2<IP_ADDRESS> - Refresh, and its example on my project and it introduced me to new issues.
This is what's happening now...
Either I install it by drag-and-drop into the Assets folder of my project, or I just double-click on the MRTK files themselves, it is the exact same scenario.
This is the latest error I'm getting...
Assets\HoloToolkit-Examples\SpectatorView\Scripts\SpectatorViewNetworkManager.cs(4,25): error CS0234: The type or namespace name 'Preview' does not exist in the namespace 'HoloToolkit.Unity' (are you missing an assembly reference?)
Assets\HoloToolkit-Examples\SpectatorView\Scripts\SpectatorViewNetworkManager.cs(19,13): error CS0246: The type or namespace name 'SpectatorView' could not be found (are you missing a using directive or an assembly reference?)
I don't know when am I ever going to complete this project? I have been doing this for the past 3-4 weeks to NO avail!
Every time I attempt to install MRTK and MRTK-Examples on my project--even new projects--
Errors. Nothing but errors. This is FRUSTRATING with all letters in capital!

Hi, thanks for asking a question. For troubleshooting questions like this it would be great to ask the question on stackoverflow with the tag "MRTK", since then other people can benefit from searching for your questions (many people don't know to search the issues on github). Please include your exact environment and repro steps so that we can reproduce your issue.
Reading the other conversation, it sounds like this might be more of a configuration issue rather than a bug, so hopefully the stackoverflow community can help. Closing this for now, but If this ends up being a bug with Holotoolkit or MRTK that others can reproduce we can re-open the issue.

Assets\HoloToolkit-Examples\SpectatorView\Scripts\SpectatorViewNetworkManager.cs(4,25): error CS0234: The type or namespace name 'Preview' does not exist in the namespace 'HoloToolkit.Unity' (are you missing an assembly reference?)
Assets\HoloToolkit-Examples\SpectatorView\Scripts\SpectatorViewNetworkManager.cs(19,13): error CS0246: The type or namespace name 'SpectatorView' could not be found (are you missing a using directive or an assembly reference?)

These errors indicate that the spectator view example requires HoloToolkit-Unity-Preview-2<IP_ADDRESS>-Refresh.unitypackage (https://github.com/Microsoft/MixedRealityToolkit-Unity/releases/download/2<IP_ADDRESS>-Refresh/HoloToolkit-Unity-Preview-2<IP_ADDRESS>-Refresh.unitypackage)


fix: automatically set instance when using Player.spectate

This PR makes Player.spectate automatically set the instance, just like how addPassenger sets the instance. This should help with uniformity

I dont think this behavior should exist, it should instead just be an error if they are not in the same instance. Passengers should also work this way, its odd to have this implicit switch to me.


Yieldbot bidder doc pbjs 1.0 support metadata

Adds metadata field prebid_1_0_supported to Yieldbot bidder developer docs.
Ref:

https://github.com/prebid/Prebid.js/pull/2135#issuecomment-369955633

thanks for the docs - released with PBJS 1.5


The message processing speed when using the outbox pattern

In what area(s)?

/area runtime

What version of Dapr?

1.14.1

edge: output of git describe --dirty

Expected Behavior
Improving the message processing speed when using the outbox pattern.
Actual Behavior
The message processing speed when using the outbox pattern is nearly 1 second per message.
I checked the source code of Dapr and found a 1-second delay when Dapr processes these events. It occurs in the file outbox.go at line 273.
Steps to Reproduce the Problem
Step 1: Setup pubsub.yaml and statestore.yaml
pubsub.yaml
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: orderpubsub
spec:
  type: pubsub.kafka
  version: v1
  metadata:
  - name: brokers
    value: localhost:9092
  - name: authType
    value: none

statestore.yaml
apiVersion: dapr.io/v1alpha1
kind: Component
metadata:
  name: replication-master-data-user-service
spec:
  type: state.postgresql
  version: v2
  metadata:
    - name: connectionString
      value: "host=localhost user=postgres password=postgres port=5432 database=outbox"
    - name: outboxPublishPubsub
      value: orderpubsub
    - name: outboxPublishTopic
      value: user-service

Step 2: Use a loop to call function executeStateTransaction  of DaprClient in Java SDK.
Here my function use executeStateTransaction of Java SDK
  public <T> void publishEventWithOutbox(String daprStore, T object, String id) {
    try {
      ExecuteStateTransactionRequest request = new ExecuteStateTransactionRequest(daprStore);
      State<T> state = new State<>(id, object, null);
      TransactionalStateOperation<T> transactionalStateOperation = new TransactionalStateOperation<>(
          OperationType.UPSERT, state);
      request.setOperations(List.of(transactionalStateOperation));
      client.executeStateTransaction(request).block();
      LogUtil.info("Executed state transaction for object with id: {}", id);
    } catch (Exception e) {
      LogUtil.error("Failed to execute state transaction for object with id: {}", id, e);
      throw e;
    }
  }

I use a loop to call my function approximately 1000 times.
    messages.forEach(categoryMappingMessage -> {
      try {
        categoryMappingMessage.setReplicationId(uid);
        categoryMappingMessage.setLastUpdated(timestamp);
        daprUtil.publishEventWithOutbox(prefix + service, categoryMappingMessage,
            UUID.randomUUID().toString());
      } catch (Exception e) {
        handlePublishMessageFail(importResult, categoryMappingMessage);
        LogUtil.warn("Publish message to service " + prefix + service + " fail!");
      }
    });

Step 3: Check the logs to observe the event processing speed.
After checking the logs, the processing speed is only 1 message per second. Look at the attached image.

Release Note

RELEASE NOTE:
Runtime error when using the Transactional Outbox Pattern

cc @yaron2


Send current state of the subscriptions

Improve #394
Make WebSocket subscriptions send the current status when subscribing. It would also be interesting to implement this logic into the PubSub crate. If we do this, this solution would be agnostic to the WebSocket, and any other bit of the rust code that wants to subscribe would inherit messages of current status when they subscribe. What are your thoughts @thesimplekid ?

It would also be interesting to implement this logic into the PubSub crate

It looks like the pubsub mod doesn't currently have access to the database so we would have to provide that? I'm happy with it in either place so if you think its worth refactoring to put it there I'm happy with that, I do see your point about making it agnostic, but if its much more complicated it may not be worht it?
Looking at the current code it looks good my only concern is it looks like we will silently fail, granted on calls that really shouldnt fail, but in general I think its good to at least log errors if returning them is impractical as we don't want to stop the whole call failing for a partial failure.

Rebase on main will fix the ci issue


Can't go back to the Activity

In gvr-events i set Clicklistner for to access 360 photo Activiity by adding these codes.
private OnClickListener clickListener=new OnClickListener() {
@Override
public void onClick(View v) {
startActivity(new Intent(EventsActivity.this, Minimal360PhotoActivity.class));
}
}
After seeing the 360 photo i press the back button in Gear VR, i can't go back previous activity, what code to go back and where it specified?

There are ways to do this, but it is recommended that you be cautious with multiple activities. Let me know if this helps:
https://github.com/Samsung/GearVRf/issues/477

Is there any coding examples for that?

We don't have examples for that as it is not expected to "just work".


Table convertion

IMO should be added the capability to convert HTML tables to markdown tables.

Sure, feel free to propose a pr.
As mentioned in the README, this is a port of turndown. I haven't tried it, but it seems that this plugin https://github.com/domchristie/turndown-plugin-gfm can support tables and convert them to github style tables. In case it helps as inspiration.

same questions,i hope this pr,thanks

same questions,i hope this pr,thanks


fix livekit-client version

I ran the command 'npm install @livekit/components-react @livekit/components-styles livekit-client' to use the react components. However, the error occurred because the version of the livekit-client was not compatible, so I corrected the version of the livekit-client to resolve the error.

Hi @junjunclub ,
This tutorial is not intended to use Livekit's React Components.
We will work to include a tutorial that uses these components and keep the dependencies updated.


x11docker: 7.1.0 -> 7.1.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mviereck/x11docker/releases.
meta.description for x11docker is: "Run graphical applications with Docker"
meta.homepage for x11docker is: "https://github.com/mviereck/x11docker"
meta.changelog for x11docker is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
Warning: no invocation of /nix/store/99ziil0mzkmxgagjqzzvhqjwpahdi841-x11docker-7.1.1/bin/x11docker had a zero exit code or showed the expected version
Warning: no invocation of /nix/store/99ziil0mzkmxgagjqzzvhqjwpahdi841-x11docker-7.1.1/bin/.x11docker-wrapped had a zero exit code or showed the expected version
0 of 2 passed binary check by having a zero exit code.
0 of 2 passed binary check by having the new version present in output.
found 7.1.1 with grep in /nix/store/99ziil0mzkmxgagjqzzvhqjwpahdi841-x11docker-7.1.1
found 7.1.1 in filename of file in /nix/store/99ziil0mzkmxgagjqzzvhqjwpahdi841-x11docker-7.1.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
0 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
x11docker

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/99ziil0mzkmxgagjqzzvhqjwpahdi841-x11docker-7.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A x11docker https://github.com/r-ryantm/nixpkgs/archive/3c778d442db3fe669fbb0f3dcf44fa098096ed06.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/99ziil0mzkmxgagjqzzvhqjwpahdi841-x11docker-7.1.1
ls -la /nix/store/99ziil0mzkmxgagjqzzvhqjwpahdi841-x11docker-7.1.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

x11docker

Maintainer pings

Change looks good to me.


Enhancement - Consistent Loading Style

Every page loads differently. The common principle is to display everything that doesn't need loading immediately and provide a loading indicator while data is being fetched.
On slow bandwidth, the profile page loads two buttons, then a blank profile image, then events, etc.
On the admin user management page, the buttons and view only load after the users have been fetched. We should be able to load the entire page besides user content and have a loading circle in the chart to indicate the page is working.
On the files page, there is no indication that files are loading. Users are presented with a completely blank category until all files are fetched.

Here's an example of the user page. Pretty egregious on slow 3g, but exemplified the problem pretty well
https://user-images.githubusercontent.com/29768212/194172263-a1f34627-54ed-4ecb-b078-1e0e36440742.mov


Feature/fix no throw literal

Yet to be published as a patch. Only prerelease currently.

@hally9k what was the use case for disabling this one?


Should EventsTable and ActionsTable also use start_time and stop_time

Currently  EventsTable and ActionsTable use an instantaneous timestamp. In ArControl it looks like all events have some duration associated with it. For generality, should  EventsTable and ActionsTable also use start_time and stop_time columns (similar to StateTable)?

BEADL events and actions do not have a duration (ref). Events/actions with a duration, e.g., LED is on or nosepoke beam is crossed, could just be interpreted as a state (which has a duration), where the start of the state is an event (LED onset) and the end of the state is an event (LED offset). But I can see how some data acquisition systems organize these kinds of data as events/actions with durations.
Do we want to allow for that or encourage users to follow the BEADL convention where events and actions are instantaneous?
If we want to allow for that, then I see two options:

add an optional "duration" column. This maintains backwards compatibility (which is nice but not necessary at this stage of development)
change "timestamp" column to "start_time" and "stop_time" for consistency with StatesTable. Either "stop_time" is optional or instantaneous events should store "stop_time" = "start_time"

I lean toward allowing for it and option 1.

I lean toward allowing for it and option 1.

I lean toward option 1 as well. Advantages of this approach I think are: 1) it implies that events/actions are instantaneous in nature, i.e., the state machine responds when the event/action happens, and keep events/actions distinct from states, 2) having duration as an optional column is more intuitive then having a start_time with an optional stop_time.

@rly @mavaylon1 can we add this change before release?

@oruebel sounds like a plan.

We will use a DurationVectorData like in ndx-events. I'll work on this.


fix: outer join should keep other condition

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall