Is it possible to enable it by default?

Hi,
I'm new to tasty, so this is probably a dumb question.
I'm considering using tasty-fail-fast in the test suites for the Haskell exercises in http://exercism.io , but because the tests are supposed to be run by the students, we cannot expect them to always type stack test --test-arguments --fail-fast. Maybe I'm missing something, but I couldn't find a clean solution to this.
Is there any simple way to enable fail-fast in the source code, so that we don't have to supply --fail-fast in the command line?

Hi,
So it looks like I defaulted fail fast to off. I think this is the reasonable thing to do.
You can however on the haskell side inject the fail fast option and set it to true. It looks like localOption :: IsOption v => v -> TestTree -> TestTree is what you want. So if you want this applied at the root, your main would look something like defaultMain $ localOption (FailFast True) $ [ .... ]. I noticed that there's no actual example code in this repo so I'll go ahead and set that up and post here when done. Seems worthy of a release too.

Oh, actually I realized the home page on the package includes an example:
defaultMainWithIngredients (map failFast defaultIngredients) tests

So for your case I think you want:
defaultMainWithIngredients (map failFast defaultIngredients) (localOption (FailFast True) tests)

Thank you for you help! :smile:
Unfortunately, that doesn't seems to work:
import Test.Tasty
import Test.Tasty.HUnit
import Test.Tasty.Ingredients.FailFast

main :: IO ()
main = defaultMainWithIngredients (map failFast defaultIngredients) (localOption (FailFast True) tests)
  where
    tests = testGroup "Failure && Success" $
              [ testCase "Failure" $ True @?= False
              , testCase "Success" $ True @?= True ]

$ stack runghc Tests.hs

Failure && Success
  Failure: FAIL
    expected: False
     but got: True
  Success: OK

1 out of 2 tests failed (0.00s)

$ stack runghc Tests.hs -- --fast-fail

Failure && Success
  Failure: FAIL
    expected: False
     but got: True
  Success:

2 out of 2 tests failed (0.00s)

Maybe this can't be set that way:

Adjusting and querying options
Normally options are specified on the command line. But you can
also have different options for different subtrees in the same tree,
using the functions below.
Note that /ingredient options/ (number of threads, hide successes
etc.) set in this way will not have any effect. This is for modifying
per-test options, such as timeout, number of generated tests etc.
...
localOption :: IsOption v => v -> TestTree -> TestTree
Locally set the option value for the given test subtree
...

I think you may need to ask @feuerbach about this. I think it may be impossible. Looks like internally OptionSet is a Map and lookupOption which my library must use to get the selection does a lookup with defaulting. I would just reimplement lookupOption to have different defaulting behavior but the constructor for OptionSet isn't exported so its impossible.

Thank you very much for your time, @MichaelXavier. I appreciate the explanation. :smile:

You could do this by setting the environment variable -- either externally in the environment where you run the tests, or directly in main before you call defaultMain.

Interesting solution! Thanks, @feuerbach .
But now I have already rewritten most of the exercises to use hspec, so we'll probably stick with it for a while. It was the simplest solution I could find at the time:
import Test.Hspec.Runner (configFastFail, defaultConfig, hspecWith)

main :: IO ()
main = hspecWith defaultConfig {configFastFail = True} specs


[Question] Ongoing tasks: how to abandon a task that is not open?

Dear MAPF-Competition Team,
Could you please provide detailed steps for canceling an assignment (indicating the interactions between the scheduler and the environment data structure)?
That is, say that agent $i$ got task $j$ assigned at time $t$. After some time, the scheduler changes its mind, say $t'$. The scheduler checks whether agent $i$ has completed any of the errands of task $j$. If no errand has been completed (e.g. agent $i$ hasn't gone through the first location associated with tasks $j$), what would be the scheduler code to cancel the assignment? Does the scheduler needs to wait for one tick before assigning a different task to agent $i$?
Thank you

Hi Miquel,
You can assign this agent another task as long as the current task is not opened. You also can exchange unopened tasks between agents.
But, currently, you cannot abandon the task without assigning the agent another task. If you think abandoning a task without assigning a new task will be useful, we could explore such option.
Best,
Mike
Best,
Mike

Hi Mike,
Okay, that explains my issues. I will need to think carefully about the implications of that restriction.

. If you think abandoning a task without assigning a new task will be useful, we could explore such an option.

Ideally, I would be able to create "recovery" tasks that constrain the agents' behavior. The simplest example is what you mention: "stay in place (kind of)."
I am happy with the current challenge as it is. I just need to wrap my head around it :)
Daniel helpfully pointed me to the Discord channel - I will switch my questions there as it seems to be a more popular venue.

Hi Miquel,
After reviewing the code, I realised an issue with "assign an agent another task as long as the current task is not opened". If the current task is not reassigned to another agent, this task is abandoned. However, the code does not reset the task->agent_assigned in this case.
I'll raise a bug fix issue on this problem.
Best,
Mike

:+100:


index.js has a global reference to window, causing server side rendering to crash

Hi @jasonslyvia,
In 1.7.2, index.js on line 18, there is a reference to "window".  This causes an error when server side rendering a component using react-anything-sortable.  Can you move the window call to a client-only location?
Thanks,
Dave

You mean this line of code https://github.com/jasonslyvia/react-anything-sortable/blob/e789b55dee039400f38303598621f1f965c03672/src/index.js#L18 ?

Ohhhhh... you fixed it already.  HA, sorry, I did not notice.  Awesome, thanks!


add retry mechanism

Oftentimes, lock and unlock commands fail. When using automation this isn't very pleasant :-) to overcome it I created a somewhat "complex" NodeRed flow that handles command retries incase of failures to ensure that the commands sent are executed.
It will be great if we can support such a feature built-in.

Hi, I have to fix some other things before I can look into this. Maybe it's also a good idea to figure out why it fails that often for you, for me it works almost always. Maybe the connection between the lock and the ESP could be improved (move the ESP closer to the lock)?

It is very close... How can i get it to output relevant logs?

Add the moment there's unfortunately no logging over network yet. You can read output from the serial line for example with hterm (set to 115.200 baud)

@regevbr Maybe you can start by looking at the MQTT topics with MQTT Explorer. You will see how the topics are updated. There is a commandResult value that can be interesting to look at for things like time out issues.

I just see failed not tine out
On Sat, Dec 24, 2022, 11:02 Julien Ehrhart @.***> wrote:

@regevbr https://github.com/regevbr Maybe you can start by looking at
the MQTT topics with MQTT Explorer. You will see how the topics are
updated. There is a commandResult value that can be interesting to look
at for things like time out issues.
[image: image]
https://user-images.githubusercontent.com/6184289/209428670-c7e7869d-380c-484f-add6-ae5dfa6f01d2.png
—
Reply to this email directly, view it on GitHub
https://github.com/technyon/nuki_hub/issues/62#issuecomment-1364491447,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABMCBH4PXHR7JV2JLSVHAWDWO23ZFANCNFSM6AAAAAATGN7GXQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@Mincka What happened to your lock that you had a motorPowerFailure?

@Mincka What happened to your lock that you had a motorPowerFailure?

Hardware defect of the lock. It has been replaced by another one by Nuki since I was in the first year of warranty. That's the new one that is not compatible for some reason with the latest version of nimble...
I don't know the exact reason of the hardware failure. In the past, I had a motor jammed issue once because my door was not properly closed but the lock was still working fine after that. A few weeks later, it just stopped working with this specific issue and an error code in the app saying I need to contact the support. Anyway, the Nuki support was excellent and they send me back a new lock (that I guess is a refurbished one, but it works great).

Add the moment there's unfortunately no logging over network yet. You can read output from the serial line for example with hterm (set to 115.200 baud)

I only see "failed". completionStatus is uncahnged

@technyon just installed latest version - log topic is not being published to... so I can't find out why I get errors from time to time

Please go to the MQTT Configuration and enabled logging there.

Thanks but nothing special in the logs is showing

Please test the attached binary. It retries up to three times to send the lock action, and retries to query the lock state every 10 seconds if it fails.
nuki_hub-retry-1.zip

Thanks I just perfomred on OTA I will report back soon

It happened to me twice where the retry mechanism kicks in and then the whole thing gets stuck and unresponsive...
The logs I received:
2023-01-04 10:17:01.897 WARNING (MainThread) [nuki_hub] Nuki lock state update: unlocked
2023-01-04 10:17:12.975 WARNING (MainThread) [nuki_hub] Lock action received: lock
2023-01-04 10:17:17.988 WARNING (MainThread) [nuki_hub] Lock action result: failed
2023-01-04 10:17:18.078 WARNING (MainThread) [nuki_hub] Lock action failed, retry 0
2023-01-04 10:19:51.163 WARNING (MainThread) [nuki_hub] Lock action received: lock
As you can see there are no more retyr logs and when I close the lock using the physical nuki button, the hub doesn't get updated that the lock was locked and I need to restart it.

Would it be possible to have the retry mechanism implemented for the next release or rebased for 6.9 in this thread for testing?
The 6.9 version is working great most of the time for now.
I would like to confirm that the retry implementation would help for one of my lock that get a commandResult = failed Lock action result: failed from time to time. It usually works on the second attempt.

In my case, the lock is still responsive and one retry attempt in case of commandResult: failed is usually enough to succeed. I think it's because of the BT connection that is a little weak. I don't think the status query is needed at first (and we saw that's better to do small changes in each release). I don't know how you implemented it but a new attempt of the same command in case of failed status would be great.

Yes I thinking limiting the number of retries makes sense anyway.
@regevbr When testing this, did you disable your NodeRed flow?

Yes I thinking limiting the number of retries makes sense anyway.
@regevbr When testing this, did you disable your NodeRed flow?

Yes of course... For me without the fix + node red flow - everything is operating flawlessly. Sadly the fix here caused the crash for some reason. If you can figure out a way why that happened I will be glad to test it out again. In the meanwhile maybe @Mincka  can also give it a go and report back if it gets stuck for him as well or not.
@technyon thanks for looking into this :-)

Sure, I will test a retry mechanism if rebased for 6.10 or included in the next version.
I am not sure to get what exactly was added by @technyon in the test version of this thread. It looks like two different things, the retry on failure and the "retries to query". Maybe that's the second part that is not necessary and causing issues in your case.
Also, I don't know what would be the ideal delay to add between attempts. I hope it's enough to wait 1 second but in the meantime I don't think it should be less than that. Being able to have this ("Delay between retry attempts (in seconds)" as a parameter for testing would be the icing on the cake.

I gave it another try. You can configure number of retries and delay, please let me know how it works.
nuki_hub-6.10-retry-1.zip

Thank you so much for this. :)
I used this to begin:

It worked on the first try! Then, I tried again and this time it seemed that it did not even try to retry. Then again, and it worked. Even if the last command result was failed, when it was published again, it worked.
I continue to test. So for now, it worked for 2 failed unlocking actions but failed for the locking one.

I can confirm that from times to times, the retry mechanism is not triggered but I am not sure why.
I updated the number of attempts to 3 and I had one case where all 3 retry attempts failed. I'm going to increase up to 10, still keeping 100 ms delay.
Is it possible to add the retry count in the MQTT message like you did before? It's useful to get the state updated in HA and get a new event log.

Something like:
Last command failed, retrying (2/3) after 100 milliseconds. Lock action result: failed

Ouch, I just tried to unlock one more time and it made the ESP reboot and spam the 10 retries.

This one should work :). Also added a retry counter MQTT node.
nuki_hub-6.10-retry-2.zip

Thank you. ☕;-)
First attempt, 2 retries because of commandResult = failed then commandResult = error and in this case, it pushed failed in retry.

Despite this one glitch, all other retry mechanism triggers managed to succeed in the end with 1 to 5 retries needed.
I had a look at MQTT history and when commandResult = error after the third or fourth attempt, it does not wait between new attempts and looped to 10 in 600 ms I guess (100ms x 6), so the retry attempts are exceeded and the code push retry = failed. That's the same kind of behavior I had on reboot previously. Maybe you need to handle differently failed, that needs retries vs other error codes. You're almost there!

Yes you're right, the delay didn't work, I fixed it.
nuki_hub-6.10-retry-3.zip

100% success on 10 locks / 10 unlocks both locks with different kinds of error (error, timeOut, failed).
The retry mechanism even helped to update a status that was not correct after the lock was triggered.
I need to confirm this other a few days but this feature helps so much for the reliability of the actions. 👍🤩

Released as 6.11

Just for reference, it seems a similar issue was discussed upstream in the NukiBleEsp32 project:
https://github.com/I-Connect/NukiBleEsp32/issues/24#issuecomment-1265349390
Maybe that's the same thing, but it's now it handle in this lib. I can confirm again that it helps a solve for reliability.


[Typo Fix] "baseUrl" in Readme.md , but baseURL used in source codes

I wrote 'baseUrl:http://<IP_ADDRESS>:12345' in webpack.config.js as the document specified, but the code generated 'localhost:8080'. I discovered the typo by searching for keywords.
Thanks you for this great project !

Thank you for pointing out the typo.


Nuke disk left behind even when not left behind

Description

Lone ops always seem to get the display message wrong even when the crew has the nuke disk at CentCom

Reproduction

Screenshots

Additional context

I was able to debug this locally. The issue is that at the moment the results are evaluated, the nuke disk resolves as still being on the FTL grid, so it isn't considered on CentCom.


Print complex numbers fix

When printing complex numbers, the i was being left off. The buf and buf_len were incremented by the wrong value.
Before:
slate/test> ./tester --dim 2 --verbose 4 --type c gemm
SLATE version 2022.07.00, id cc1215cd
...
C_out = [
     0.8788 +     5.4334    -0.0757 +     4.6075
    -0.2857 +     4.9629    -1.5520 +     8.4006
];

After:
slate/test> ./tester --dim 2 --verbose 4 --type c gemm
SLATE version 2022.07.00, id 82a4b7d9
C_out = [
    -1.8994 +     8.1239i    -1.8884 +     5.9303i
    -0.6405 +     5.4799i     0.7901 +     3.9769i
];

Also cleans up the code. slate:: is unnecessary since print is in the slate namespace. (At one point it was in the test directory, outside the slate namespace.) Options like width can be int instead of int64_t, which avoids the need to cast them when using in printf.
Also fixes a hang if tile is on device. It wasn't doing tileGetForReading.

Manually tested with CUDA and Open MPI, since the CI container is currently broken. Nearly all tests passed.
trsmA had unrelated issue.
unmqr had unrelated issues on some runs (race condition?).


Fix sbt console

Fixes sbt/sbt#3129

Weird, CI is not running at all.

Unfortunately, merging the formatting PR made this PR have conflicts. Can you update @dwijnand and I merge?

Yeah, I knew merging your PR would have this effect. But I did it because it was 9 days in the making and this one is brand new, so I'll rebase my work.


Display page number of pdf

How to display pager in pdf?

Hi,
this has been already solved in #5. Have a look at the solutions.
Thanks!


Unicode problems?

Here is my error report:
2018-03-21 00:01:13 =ERROR REPORT==== ** gen_event handler {lager_file_backend,"log/console.log"} crashed. ** Was installed in lager_event ** Last event was: {log,{lager_msg,[],[{application,blockchain},{module,ws_handler},{function,terminate},{line,41},{pid,"<0.11250.0>"},{node,nonode@nohost}],info,{["2018",45,"03",45,"21"],["00",58,"01",58,"13",46,"229"]},{1521,586873,229857},{crash,error,{badmatch,{error,enoent}}}}} ** When handler state == {state,"log/console.log",{mask,127},{file_descriptor,prim_file,{#Port<0.651800>,38}},24285019,false,10485760,[{hour,0}],5,lager_rotator_default,{lager_shaper,"log/console.log",undefined,0,{1521,586725,110873},0,true,0,#Ref<0.1198586251.2507931650.164416>,#Fun<lager_file_backend.0.86890548>},lager_default_formatter,[],{mask,15},1000,1000,65536,{1521,586873,206059}} ** Reason == {badarg,[{unicode,characters_to_binary,[[["2018",45,"03",45,"21"]," ",["00",58,"01",58,"13",46,"229"]," ",[],"[","info","] ","<0.11250.0>",[["@"],"ws_handler",[":","terminate"],[":",["41"]]]," ",{crash,error,{badmatch,{error,enoent}}},"\n"]],[]},{lager_file_backend,do_write,3,[{file,"/Users/David/IdeaProjects/bc/_build/default/lib/lager/src/lager_file_backend.erl"},{line,278}]},{lager_file_backend,handle_event,2,[{file,"/Users/David/IdeaProjects/bc/_build/default/lib/lager/src/lager_file_backend.erl"},{line,177}]},{gen_event,server_update,4,[{file,"gen_event.erl"},{line,573}]},{gen_event,server_notify,4,[{file,"gen_event.erl"},{line,555}]},{gen_event,handle_msg,6,[{file,"gen_event.erl"},{line,296}]},{proc_lib,init_p_do_apply,3,[{file,"proc_lib.erl"},{line,247}]}]}
Why I think that problem is with unicode:
** Reason == {badarg,[{unicode,characters_to_binary,[[["2018",45,"03",45,"21"]...
Here my configuration in rebar:
{lager, {git, "https://github.com/erlang-lager/lager", {tag, "3.6.1"}}}
and
{lager, [   {log_root, "log"},   {handlers, [     {lager_console_backend, [{level, debug}]},     {lager_file_backend, [{file, "error.log"}, {level, error}]},     {lager_file_backend, [{file, "info.log"}, {level, info}]},     {lager_file_backend, [{file, "debug.log"}, {level, debug}]}   ]} ]}.

Might be a unicode problem. Goodness knows that lager has never been especially good at handling unicode text.
But it looks to me like the invalid "unicode" [{unicode,characters_to_binary,[[["2018",45,"03",45,"21"]... is a datetime stamp that has somehow been interpreted as a potential unicode byte sequence for a file name. (ASCII 45 is the "-" character, so it would be 2018-03-21 as a string)

Any update on this issue?

I'm going to close this issue because there's been no updates for several months. Please open a new ticket if you still need help.

Not Unicode.  It tries to do
unicode:characters_to_binary([
  ["2018",45,"03",45,"21"]," ",
  ["00",58,"01",58,"13",46,"229"]," ",[],"[","info","] ",
  "<0.11250.0>",[["@"],"ws_handler",[":","terminate"],[":",["41"]]],
  " ",
  {crash,error,{badmatch,{error,enoent}}},  % ⟵
  "\n"
]).


[ISSUE] Default values causes chart to fail to start up due to standby user

Have a look at Troubleshooting or some Common Issues

Describe the bug
I have secrets for timescaledb-release-certificate and timescaledb-release-credentials defined. The credentials secret is like
kubectl get secret timescaledb-release-credentials -o yaml
apiVersion: v1
data:
  PATRONI_ADMIN_PASSWORD: <base64encoded>
  PATRONI_REPLICATION_PASSWORD: <base64encoded>
  PATRONI_SUPERUSER_PASSWORD: <base64encoded>

When I apply the chart without specifying any values.yaml, the logs in the pod say
2021-04-08 05:41:46 UTC [99]: [606e979a.63-1] [unknown]@[unknown],app=[unknown] [00000] LOG:  connection received: host=<IP_ADDRESS> port=60824
2021-04-08 05:41:46 UTC [99]: [606e979a.63-2] standby@[unknown],app=[unknown] [28P01] FATAL:  password authentication failed for user "standby"
2021-04-08 05:41:46 UTC [99]: [606e979a.63-3] standby@[unknown],app=[unknown] [28P01] DETAIL:  Password does not match for user "standby".
	Connection matched pg_hba.conf line 8: "hostssl   replication     standby            all                md5"

To Reproduce
Use helm chart for the single db for version 0.8.2. Create the 2 secrets above. Deploy the chart without specifiying any other values.
Expected behavior
It should start up.
Deployment

What is in your values.yaml
Nothing
What version of the Chart are you using?
0.8.2
What is your Kubernetes Environment (for exampe: GKE, EKS, minikube, microk8s)
EKS

Hi @NickLavrov. I've got the same issue. Did you resolve it?


Better build and release

This PR contains several changes which attempt to improve how we build and release Cog.

When building cog's Go binary, we embed the wheel with the full path generated by build. This makes it clearer what version of cog's Python package is being injected by any given cog binary at runtime.
Omit test files from the built wheel.
Run tests against the cog package installed from the built wheel, not against an editable installation from the local directory.
Use goreleaser to build cog so we have only one way of building the cog binary, not two.

There's more I want to do here, specifically to replace the release.yaml workflow, but this is more than enough for one PR so I'm stopping here.


Does neon support tesla k80

hi,
Does the current version of neon support Tesla K80 GPUs ?
Thanks.

Yes, Kepler support is back in neon as of v1.2, 85fd5c1. See #80 and http://www.nervanasys.com/neon-v1-2-release-kepler-aws-support-are-back-deep-resnets-and-more/

Great !
I'm trying out neon on a Linux 3.16 machine with 4x K80's and I'm getting the following error. Please advise.
from neon.backends import gen_backend
be = gen_backend(backend='gpu', batch_size=128, rng_seed=1, stochastic_round=False)

---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-13-b4c3bcb788a4> in <module>()
      1 # setup the backedn
      2 from neon.backends import gen_backend
----> 3 be = gen_backend(backend='gpu', batch_size=128, rng_seed=1, stochastic_round=False)

/home/firdaus/.conda/envs/neon/lib/python2.7/site-packages/neon-1.2.1-py2.7.egg/neon/backends/__init__.pyc in gen_backend(backend, rng_seed, datatype, batch_size, stochastic_round, device_id, max_devices, compat_mode, deterministic_update)
     89         if gpuflag is False:
     90             raise RuntimeError("Device " + str(device_id) + " does not have CUDA compute " +
---> 91                                "capability 3.0 or greater")
     92         if backend == 'gpu':
     93             from neon.backends.nervanagpu import NervanaGPU

RuntimeError: Device 0 does not have CUDA compute capability 3.0 or greater

Can you add a print before line 88 for check_gpu.get_compute_capability(device_id) ?
Were the CUDA drivers installed at the time of neon installation, and does your PATH include /usr/local/cuda/bin and LD_LIBRARY_PATH include /usr/local/cuda/lib ?

No - I'm using a remote cloud machine and I don't think cuda was installed (at least the above path's don't exist). Is there some documentation on what pre-reqs are needed to run neon with gpus ?
Thanks !

You would need the CUDA SDK and drivers.
General docs on installation are here.

Hi,
I added cuda/lib64 to LD_LIBRARY_PATH  and cuda/bin to PATH (for cuda sdk version 7.0). Also, I added the print statement on line 88 of init.py.
this is the result:
# setup the backedn
from neon.backends import gen_backend
be = gen_backend(backend='gpu', batch_size=128, rng_seed=1, stochastic_round=False)

0

---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<ipython-input-1-b4c3bcb788a4> in <module>()
      1 # setup the backedn
      2 from neon.backends import gen_backend
----> 3 be = gen_backend(backend='gpu', batch_size=128, rng_seed=1, stochastic_round=False)

/home/firdaus/.conda/envs/neon/lib/python2.7/site-packages/neon-1.2.1-py2.7.egg/neon/backends/__init__.py in gen_backend(backend, rng_seed, datatype, batch_size, stochastic_round, device_id, max_devices, compat_mode, deterministic_update)
     90         if gpuflag is False:
     91             raise RuntimeError("Device " + str(device_id) + " does not have CUDA compute " +
---> 92                                "capability 3.0 or greater")
     93         if backend == 'gpu':
     94             from neon.backends.nervanagpu import NervanaGPU

RuntimeError: Device 0 does not have CUDA compute capability 3.0 or greater

Please advise.

Can you run the following checks to make sure the GPUs, Cuda and PyCuda are being recognized correctly?
nvidia-smi
nvcc --version
python -m pycuda.autoinit
For the last one make sure that the neon virtualenv has been activated.

>nvidia-smi                                                        [0/9941]
Thu Feb 11 01:02:48 2016
+------------------------------------------------------+
| NVIDIA-SMI 346.89     Driver Version: 346.89         |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  Tesla K80           Off  | 0000:05:00.0     Off |                    0 |
| N/A   38C    P0    61W / 149W |     55MiB / 11519MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   1  Tesla K80           Off  | 0000:06:00.0     Off |                    0 |
| N/A   36C    P0    73W / 149W |     55MiB / 11519MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   2  Tesla K80           Off  | 0000:84:00.0     Off |                    0 |
| N/A   40C    P0    57W / 149W |     55MiB / 11519MiB |      0%      Default |
+-------------------------------+----------------------+----------------------+
|   3  Tesla K80           Off  | 0000:85:00.0     Off |                    0 |
| N/A   35C    P0    72W / 149W |     55MiB / 11519MiB |     96%      Default |
+-------------------------------+----------------------+----------------------+

>nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2015 NVIDIA Corporation
Built on Mon_Feb_16_22:59:02_CST_2015
Cuda compilation tools, release 7.0, V7.0.27

 >python -m pycuda.autoinit
/home/firdaus/.conda/envs/neon/bin/python: No module named pycuda

Something went wrong during installation, and the pycuda package, which is a dependency for neon, did not get installed. It looks like you are using anaconda python, which does not support the standard virtualenv installation. There is a community contributed neon install script for anaconda you can find through the install docs at http://neon.nervanasys.com/docs/latest/user_guide.html#anaconda
Hope that helps!

I have the same problem (but with a GTX980). I'm using Anaconda on Ubuntu 14.04. I've followed the Anaconda installation instructions, but they seem to be for Mac OS X, as the dependencies contain OS X-only packages (like appnope). Also, some of the dependencies in neon-conda-environment.yaml are referring to specific package versions that are no longer available.
After some changes I got the installation running:
(neon)neon>python setup.py develop
running develop
running egg_info
creating neon.egg-info
writing neon.egg-info/PKG-INFO
writing top-level names to neon.egg-info/top_level.txt
writing dependency_links to neon.egg-info/dependency_links.txt
writing manifest file 'neon.egg-info/SOURCES.txt'
reading manifest file 'neon.egg-info/SOURCES.txt'
writing manifest file 'neon.egg-info/SOURCES.txt'
running build_ext
Creating /home/manordin/anaconda2/envs/neon/lib/python2.7/site-packages/neon.egg-link (link to .)
Adding neon 1.2.1 to easy-install.pth file
Installing neon script to /home/manordin/anaconda2/envs/neon/bin
Installing nvis script to /home/manordin/anaconda2/envs/neon/bin

Installed /home/manordin/neon
Processing dependencies for neon==1.2.1
Finished processing dependencies for neon==1.2.1

I can run examples using CPU but not GPU.
examples>nvidia-smi
Thu Feb 11 11:54:18 2016
+------------------------------------------------------+
| NVIDIA-SMI 352.79     Driver Version: 352.79         |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|===============================+======================+======================|
|   0  GeForce GTX 980     Off  | 0000:02:00.0      On |                  N/A |
| 32%   39C    P8    16W / 180W |    381MiB /  4086MiB |      1%      Default |
+-------------------------------+----------------------+----------------------+

(neon)examples>nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2015 NVIDIA Corporation
Built on Tue_Aug_11_14:27:32_CDT_2015
Cuda compilation tools, release 7.5, V7.5.17

(neon)examples>python -m pycuda.autoinit
/home/manordin/anaconda2/envs/neon/bin/python: No module named pycuda

@ursk I followed those instructions initially. However, during installation A lot of packages didn't get resolved (eg appnode, astroid). Also, yesterday I tried to explicitly install pycuda, but because I'm behind a firewall, pycuda has issues with the proxy server. Not sure how to proceed.

creating dist
creating 'dist/pycuda-2015.1.3-py2.7-linux-x86_64.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing pycuda-2015.1.3-py2.7-linux-x86_64.egg
creating /srv/home/firdaus/.conda/envs/neon/lib/python2.7/site-packages/pycuda-2015.1.3-py2.7-linux-x86_64.egg
Extracting pycuda-2015.1.3-py2.7-linux-x86_64.egg to /srv/home/firdaus/.conda/envs/neon/lib/python2.7/site-packages
Adding pycuda 2015.1.3 to easy-install.pth file

Installed /srv/home/firdaus/.conda/envs/neon/lib/python2.7/site-packages/pycuda-2015.1.3-py2.7-linux-x86_64.egg
Processing dependencies for pycuda==2015.1.3
Searching for appdirs>=1.4.0
Reading https://pypi.python.org/simple/appdirs/
Download error on https://pypi.python.org/simple/appdirs/: [Errno 111] Connection refused -- Some packages may not be found!
Couldn't find index page for 'appdirs' (maybe misspelled?)
Scanning index of all packages (this may take a while)
Reading https://pypi.python.org/simple/
Download error on https://pypi.python.org/simple/: [Errno 111] Connection refused -- Some packages may not be found!
No local packages or download links found for appdirs>=1.4.0
error: Could not find suitable distribution for Requirement.parse('appdirs>=1.4.0')

We are looking into what's up with the Anaconda installation. In the mean time can you use the regular apt-get python ?

I'll do that. Thanks for looking into thus.
I think another problem with the Anaconda install instructions (in addition to the dependency issues) is that skipping the "make" step makes no sense. A lot of stuff will never get built if you use those instructions.

I've been able to configure neon for anaconda on a Ubuntu 14.04 Kepler instance on AWS with the following:
Create cuda environment variables (substitute your own proper cuda path)
export PATH="/usr/local/cuda/bin:$PATH"
export LD_LIBRARY_PATH="/usr/local/cuda/lib64:$LD_LIBRARY_PATH"

Then, create a conda environment
conda create --name neon pip

Activate the environment, then run a system-wide install
source activate neon
cd ~/path/to/neon
make sysinstall

Because you are inside a conda environment, sysinstall will install all the files in /path-to-anaconda/envs/neon/bin/python. I was able to run GPU examples without any issues. Let me know if that works!

Thanks.  I will try that out and get back!
On Feb 24, 2016 10:33 PM, "hanlin-nervana"<EMAIL_ADDRESS>wrote:

I've been able to configure neon for anaconda on a Ubuntu 14.04 Kepler
instance on AWS with the following:
Create cuda environment variables (substitute your own proper cuda path)
export PATH="/usr/local/cuda/bin:$PATH"
export LD_LIBRARY_PATH="/usr/local/cuda/lib64:$LD_LIBRARY_PATH"
Then, create a conda environment
conda create --name neon pip
Activate the environment, then run a system-wide install
source activate neon
cd ~/path/to/neon
make sysinstall
Because you are inside a conda environment, sysinstall will install all
the files in /path-to-anaconda/envs/neon/bin/python. I was able to run
GPU examples without any issues. Let me know if that works!
—
Reply to this email directly or view it on GitHub
https://github.com/NervanaSystems/neon/issues/200#issuecomment-188588569
.

@hanlin-nervana your solution worked for me on Ubuntu  15.04 with  GeForce GTX 960 and Cuda 7. Thanks


Node stop with Failed to write response

Bug description

morpheus-10000 suddenly stopped due to Poseidon was down. From the log, it was down because
cosmovisor[5635]: E[2020-10-07|18:59:15.344] Failed to write response                     module=rpc-server protocol=websocket remote=<IP_ADDRESS>:61015 msg="RPCResponse

Full log is at here.
I saw similar behaviour from explorer nodes with RPC being requested frequently on Kava and Band before but it should have been fixed. Will look for related issue from Tendermint Core.
Steps to reproduce

Expected behavior

Filed tendermint/tendermint#5475

Closing this as it never happened again


add windows ci

should be g2g after this round of ci @danielhuppmann

thanks @gidden for this heroic effort!


Make the temp directory for multipart upload configurable

Describe the solution you'd like
Looking at the source, when a file is uploaded using s3api multipart upload, the individual file parts go into a hard-coded directory name under the main directory for the bucket, prior to them being merged to the target file. This does not appear to be configurable, ie. we cannot put this temp directory to another location if we want. We would like this to be a configurable option. In the additional context I will place a customer need statement.
Additional context
STATEMENT OF NEED
In the modern world of global 24x7 follow the sun workflows, data synchronisation is continually ongoing to ship data site to site just in time.
Creating temporary data directly in the path of areas of synchronisation causes additional overhead of data transactions and manual effort to resolve.
An alternative is to exclude all such temporary locations from synchronisations, but this presumes that a) such software is capable b) time to invest to setup, test and monitor is cost free.
By making the  .sgwtmp location configurable, data assembly for Versity can occur out of synchronisation path and finalised to the correct location (at the cost of a move operation).  Additionally a configurable location provides a path to store data assembly on cheaper tiers of storage (e.g. SATA) and finalised data on more expensive storage (e.g. NVMe) as per a company's workflow requirements.

Currently the .sgwtmp directory is below the bucket directory. For example:
//.sgwtmp/
I assume if you want to make this configurable, you would want that to switch so that the specified temp directory is the top level directory, and then the buckets directories are below that directory? For example:
//
The desire is tmpdir to be able to be any directory on the system, not necessarily below the gateway root.
Like you point out, when enabled there is no longer the opportunity for the copy_file_range optimizations for filesystems that used cloned extents. But thats not always available anyways. We would probably need to keep a file descriptor open in this tmpdir for the life of the gateway also so that it wont get unmounted underneath the gateway.
I dont think it would be too difficult to add a configurable option for the temp dir.

Thanks for the response Ben! I'll discuss this with my colleagues.

Sorry for the delay, here's our response to this enhancement request:
The centralised // would be very welcomed.
We'd like to propose that in addition to the centralised temporary storage suggestion there is additional granularity available per bucket.
Scenario:
Customer access to buckets is per secured container.
Buckets are mapped to the underlying file system directory such as /
Customers do not wish to view the .sgwtmp folder within the /.
To satisfy security considerations customer data must be stored inside of the .
Copying files from the central // incurs an expensive move operation (on the underlying file system).  I.E. alike a cross file system copy.
Being able to store the temporary data at / would only incur a file system metadata update.
We had the thought that relative pathing would be a simple way to do this, but this could introduce security issues from badly configured software.
Could this be easily solved by passing new variable metaTmpDirRoot passed per bucket from .New() which then prepends alike so: ?
const (
metaTmpDirRoot      = "" || myset value
metaTmpDir          = metaTmpDirRoot +"/.sgwtmp"
metaTmpMultipartDir = metaTmpDir + "/multipart"


perl failing to build on os x

I just installed nix 1.10 and tried to run nix-shell -p python27 on OS X 10.10.5. It looks like perl expecting a version of the find command that doesn't work on os x. Is there a workaround?
...
strip: can't process non-object and non-archive file: /nix/store/fj08s8j4dfpiz7dyi90cs713dwg82n8v-perl-5.20.2/bin/ptardiff
strip: can't process non-object and non-archive file: /nix/store/fj08s8j4dfpiz7dyi90cs713dwg82n8v-perl-5.20.2/bin/ptargrep
strip: can't process non-object and non-archive file: /nix/store/fj08s8j4dfpiz7dyi90cs713dwg82n8v-perl-5.20.2/bin/s2p
strip: can't process non-object and non-archive file: /nix/store/fj08s8j4dfpiz7dyi90cs713dwg82n8v-perl-5.20.2/bin/shasum
strip: can't process non-object and non-archive file: /nix/store/fj08s8j4dfpiz7dyi90cs713dwg82n8v-perl-5.20.2/bin/splain
strip: can't process non-object and non-archive file: /nix/store/fj08s8j4dfpiz7dyi90cs713dwg82n8v-perl-5.20.2/bin/xsubpp
strip: can't process non-object and non-archive file: /nix/store/fj08s8j4dfpiz7dyi90cs713dwg82n8v-perl-5.20.2/bin/zipdetails
patching script interpreter paths in /nix/store/fj08s8j4dfpiz7dyi90cs713dwg82n8v-perl-5.20.2
find: -perm: /0100: illegal mode string
builder for ‘/nix/store/v16mzzb4dajbj3d13f5fl9sdy1b3ds4i-perl-5.20.2.drv’ failed with exit code 1
cannot build derivation ‘/nix/store/qrajznbph77yw7ishi9nvkwd7p95qjqf-openssl-1.0.1p.drv’: 1 dependencies couldn't be built
building path(s) ‘/nix/store/ry1xfxg5rm02caqzszjidqrgvzhp75hg-zlib-1.2.8’
killing process 63435
cannot build derivation ‘/nix/store/6bj1h78vlx4zrjdaadj9wvyg5c6jmd0m-curl-7.43.0.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/k207hrhnrks9ivfa8nsmhv3anlw8w6a0-sed-4.2.2.tar.bz2.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/2rxp8yj0mjf0wwpvp3hdi5bs0n94amhh-xz-5.2.1.tar.bz2.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/gfbnb9s14xq6f77m8gimknml5kdybllj-gnused-4.2.2.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/6gjvcw8f6sf6kal1zf06jh1z5ygg78dh-xz-5.2.1.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/3fvwri55235nqj14xszi756rlbqp7vpx-stdenv-darwin-boot-2.drv’: 1 dependencies couldn't be built
cannot build derivation ‘/nix/store/77sz7kg2x2aq67d9yskyy7mliifjsqif-bash-4.3-p39.drv’: 1 dependencies couldn't be built
error: build of ‘/nix/store/77sz7kg2x2aq67d9yskyy7mliifjsqif-bash-4.3-p39.drv’ failed
/Users/michael/.nix-profile/bin/nix-shell: failed to build all dependencies

Dupe of #9044.


Tailwind CSS IntelliSense compatibility

After migrating a few Reason files to the ReScript syntax, I noticed that the Tailwind CSS IntelliSense (e.g. autocomplete, linting, hover previews, syntax highlighting) provided via the Tailwind CSS VS Code extension does not appear to work for res files. I'm not certain as to whether this would be an issue with rescript-vscode or vscode-tailwindcss, but I figured I'd open an issue here to hopefully identify the issue origin. Thanks!

Reason Syntax
ReScript Syntax

Can you report this in tailwind vscode extension repo?
this is not related to rescript-vscode, they need to add support for rescript.
p.s. the change should be trivial maybe somewhere in this file?

@amiralies absolutely. I wasn't sure where the issue may reside. Thank you for the guidance.


Issue-572 akka-http response headers

implementation of https://github.com/guardrail-dev/guardrail/issues/572
Contributing to Twilio

All third-party contributors acknowledge that any contributions they provide will be made under the same open-source license that the open-source project is provided under.

[x]  I acknowledge that all my contributions will be made under the project's license.

/bar:
    get:
      operationId: getBar
      responses:
        '204':
          headers:
            X-Required-Header:
              type: string
              required: true
            X-Optional-Header:
              type: string

According to: https://swagger.io/docs/specification/describing-responses/
headers:
            X-RateLimit-Limit:
              schema:
                type: integer
              description: Request limit per hour.
            X-RateLimit-Remaining:
              schema:
                type: integer
              description: The number of requests left for the time window.
            X-RateLimit-Reset:
              schema:
                type: string
                format: date-time
              description: The UTC date/time at which the current rate limit window resets.

it seems like the spec expects the type to be nested under schema. Why was the implementation here made against the spec?

We are using the official OpenAPI parser, walking their domain objects, to ensure we're as close to the spec as we can be. Perhaps this is a bug upstream?
Alternately, we may be relying on a deprecated property and not realizing it, I suppose.


Fix xrefs

Fixes https://github.com/dotnet/docs/issues/24792
Please confirm on staging that it renders correctly.

Hi @Youssef1313 - how are these incorrect? I'm missing something, either that or the fix didn't work as I'm not observing a difference in the live content version the staging / internal preview.


Remove registry storage testdriver

This PR aims to close #2151 by removing the storage testdriver and using the inmemory driver.
This also update the inmemory storage driver to make sure that any written data is not available before commit.
Signed-off-by: glefloch<EMAIL_ADDRESS>

@glefloch can you please rebase?

Ping @glefloch

I think you might need to run go mod tidy and go mod vendor 🤔

@glefloch are you still interested in getting this PR done? There are some merge conflicts that need fixing

I need to set up my computer but yes, still interested into getting this merged!

It looks better thanks to go mod commands

@squizzi PTAL


docs: clarify use of PinStatus.id

This PR  does not change the spec, it simplifies docs related to /pins endpoint

/pins/{cid-of-pin-object} can be confusing because we mean PinStatus.id, but a field named cid is present in PinStatus.Pin.cid
/pins/{id} has a clear connection to PinStatus.id and reduces cognitive overhead

Preview: https://ipfs.github.io/pinning-services-api-spec/#specUrl=https://raw.githubusercontent.com/ipfs/pinning-services-api-spec/docs/clarify-object-id/ipfs-pinning-service.yaml

Merging in preparation for v0.0.5, will check copy in bulk before tagging the release.


Problem with documentation for first use

Stack trace
IDE errors when following docs. Using Latest Release
Cannot resolve symbol 'CustomHeightFilter'

Cannot resolve symbol 'EarlyExitFilterStage'

Missing 'PathEnviorment' as ARG 1

location Requires Bukkit.Location, provided PathPosition

Actions to reproduce (if known)
Hi i got these issues when using the latest release, and followings the docs. On a clean project, with no other dependencies. I assume the docs is not accureate with latest releases.
I hope that these errors are just a simple fix of updating the docs.
Other
No response

hi, it seems like you've copied the example from here.
that is solely an example and doesn't use actual existing filters. if you want to have an accurate example on how to use pathetic, see the pathetic-example module.
but you're right, it can be a bit confusing. we will adjust that in the future, thank you!
if you are experiencing any other issues, feel free to share them here :)

Ah got it thanks for refering to a example code! Got a little confused by that code snippet yea, thanks for letting me know. Il look into the example module now.

nice!
i will close this issue then, thanks for using pathetic and if you have any other questions just open another issue :)


Change Language icon not showing

Bug Report
Environment
Zola version: 0.18.0
tabi version or commit: latest
Expected Behavior
There should have been a language changing icon
Current Behavior
There is no language changing icon
Step to Reproduce
Changed the config.toml to include Dutch as well.
Made the _index.nl.md files and created a blog post with index.nl.md
Served the website, now the blog post shows up twice, once in Dutch, once in English.
However, there is no button to change the language of the website, it defaults back to English
I'm probably doing something wrong somewhere, but I have no clue what it could be.

Changed the config.toml to include Dutch as well.

Can you elaborate on this? Did you follow the steps from the docs?

Yeah, as far as I can see, I followed all the steps from the docs.
I'm not quite sure why it isnt working.
The language part of my config.toml file:
base_url = "example.com"
theme = "tabi"

default_language = "en"

title = "TITLE"
description = "DESCRIPTION"
author = "Myrdin"

generate_feed = true
compile_sass = true
minify_html = false
build_search_index = true
taxonomies = [{name = "tags", feed = true}]

[language.nl]
title = "TITEL"
description = "BESCHRIJVING"
author = "Myrdin"

generate_feed = true
compile_sass = true
minify_html = false
build_search_index = true
taxonomies = [{name = "tags", feed = true}]

[language.nl]

There's a typo. Should be in plural:

[languages.nl]

That did seem to do something, however, now I seem to be getting the following error:
Building site...
Checking all internal links with anchors.
> Successfully checked 0 internal link(s) with anchors.
-> Creating 4 pages (0 orphan) and 9 sections
Error: Failed to serve the site
Error: Tried to build search index for language nl which is not supported

Zola doesn't support building a search index for Dutch, it seems.
You'll need to disable it with:

[languages.nl]
build_search_index = false

You'll still be able to use search on the English version of the site.

Aha! Issue resolved :)

One more issue I just found, the about me page doesn't seem to work in Dutch, despite there being a about.nl.md file

Please see the structure necessary for the about page to work on multiple languages here.
You need multiple index pages within a directory, and to set the path on each file.

One more question, Im quite new to git, how would I update the theme's submodule to the latest version?

Go to the tabi directory (say, yousite/themes/tabi) and run git pull.
That should do it :)

Seems like all issues have been resolved now.
The Dutch translation is working on my website :)


React to xunit.runner.aspnet package updates

aspnet/aspnet.xunit@5a12e89

FYI only since this fixes a build break.

fea510f


change label for CDS coordinates

To avoid confusion about the original meaning (and any other interpretations, correct or incorrect) of "CDS", change the label to "start and end coordinates". Even if "CDS" would be technically correct, enough people don't realize it so changing to something ploddingly unambiguous won't go wrong.

I guess this is from V1?
Currently in V2 we just have "II, 1500197-1502095 (1899nt)" with no CDS bit.
Would "start and end translation coordinates" be clearer?

Hmm, I  still think CDS is the correct way to refer to the coding sequence genome coordinates.
The problem is that  people (incorrectly IMHO)  are expecting the number 1899nt to represent the translation lenght. However it does't if it's the start and end of a spliced gene in the genome.
The CDS length (or the number we report) is the  entire length of the coding sequence with introns in the genome, and I think that is correct.
The problem is how to explain this.....

Maybe it should be the translated length in nucleotides. I think the meaning has changed over time. it used to be "from coding DNA sequence", which to me would make the CDS length the start and end of the CDS in the DNA not the start and end of the edited sequence.
The edited sequence seems to be what people expect. So we could report the nucleotide length of the translation in  this case....

Genomic location	II, 1500197-1502095 (1899nt) start to stop
Genomic location	II, 1500197-1502095 (1899nt) plus UTRs

I removed the milestone as I con't imagine it will impede anyone.

So here we just need text changes? If so could you provide suitable? @mah11

If we just stick with the current single set of coordinates, its current label ("genomic location") is fine. If you want to show with and without UTRs, the version from Jun 1 above (https://github.com/pombase/website/issues/59#issuecomment-305459606) would do.

Removed discuss label.
Just need to add CDS start and end coordinates.

What text should we have for RNA genes and pseudogenes?

What text should we have for RNA genes and pseudogenes?

III, 	2111204-2116520 (5317nt)

III, 2111204-2116520 (5317nt)

Sorry, hit submit too soon.  For now I've implemented it like "III, 2111204-2116520 (5317nt)" for genes without a translation, which is what we have at the moment.  Is that enough in that case?

For now I've implemented it like ...

It's on the main site now.  Is it OK?

it looks a bit odd, but I think it is clear what it means
Maybe we could say
(CDS start/end)
and
(+UTRs)
to make  the text shorter.

Is my suggestion naff?

I think it would be clear to users .  You said it is the "coding sequence genome coordinates" but according to HGVN +1 is assigned to translation initiation codon in the CDS. What you are talking about is the "genomic reference sequence"?

Its the genomic location of the CDS  though?
I still maintain that CDS was "invented" to describe the genomic location in an  EMBL/Genbank  file,
so its the coordinates of the coding sequence in whichever sequence you are referring to.
i.e the genome here:
FT   CDS             complement(23589..23978)

well yeah, but according to the site I linked to, different people use the term differently, which is why I find it confusing.

but what else could it mean in the context we are using it above?

I think it's OK to close.


fix: invalidate ssrError when HMR update occurs

Description
When a module is invalidated for HMR we need to also invalidate mod.ssrError in order to allow the module to attempt to be re-executed.
Additional context
No

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

For future reference, this is a regression we introduced in https://github.com/vitejs/vite/pull/7177. I'll cherry-pick this one in v2 so we can release a patch for 2.9.x

@matthewp this PR has been included in<EMAIL_ADDRESS>

@patak-dev looks like I missed a spot :/. New PR to finish it up: https://github.com/vitejs/vite/pull/8124


Alert if gateway node does not have external ip

It may happen that there are multiple nodes with submariner gateway labels, but if one of those gateway nodes does not have external IP, submariner will fail to connect:

export KUBECONFIG=/home/nmanos/automation/ocp-install/nmanos-cluster-a/auth/kubeconfig
test_submariner_engine_status
cd /home/nmanos/go/src/github.com/submariner-io/submariner-operator
./bin/subctl info
Discovered network details:
Network plugin:  OpenShift
Service CIDRs: [<IP_ADDRESS>/16]
Cluster CIDRs: [<IP_ADDRESS>/14]
/home/nmanos/automation/ocp-install/oc get pods -n submariner-operator
NAME                                   READY   STATUS    RESTARTS   AGE
submariner-gateway-dvjpn               1/1     Running   0          12m
submariner-gateway-ptwl9               1/1     Running   0          12m
submariner-operator-8446795d99-9hvj5   1/1     Running   0          13m
submariner-routeagent-j9qkx            1/1     Running   0          12m
submariner-routeagent-nm79w            1/1     Running   0          12m
submariner-routeagent-wl48v            1/1     Running   0          12m
submariner-routeagent-xxwvx            1/1     Running   0          12m
/home/nmanos/automation/ocp-install/oc exec submariner-gateway-dvjpn -n submariner-operator strongswan stroke statusall
highlight Security Associations (0 up
Status of IKE charon daemon (strongSwan 5.8.2, Linux 4.18.0-147.3.1.el8_1.x86_64, x86_64):
uptime: 11 minutes, since Mar 10 07:40:13 2020
malloc: sbrk 2957312, mmap 0, used 960880, free 1996432
worker threads: 11 of 16 idle, 5/0/0/0 working, job queue: 0/0/0/0, scheduled: 1
loaded plugins: charon pkcs11 tpm aesni aes des rc2 sha2 sha1 md4 md5 mgf1 random nonce x509 revocation constraints acert pubkey pkcs1 pkcs7 pkcs8 pkcs12 pgp dnskey sshkey pem openssl gcrypt fips-prf gmp curve25519 chapoly xcbc cmac hmac ctr ccm gcm drbg curl attr kernel-netlink resolve socket-default farp stroke vici updown eap-identity eap-sim eap-aka eap-aka-3gpp eap-aka-3gpp2 eap-md5 eap-gtc eap-mschapv2 eap-dynamic eap-radius eap-tls eap-ttls eap-peap xauth-generic xauth-eap xauth-pam xauth-noauth dhcp led duplicheck unity counters
Listening IP addresses:
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
Connections:
submariner-cable-nmanos-cluster-b-tunnel-10-166-0-13:  <IP_ADDRESS>...<IP_ADDRESS>  IKEv2
submariner-cable-nmanos-cluster-b-tunnel-10-166-0-13:   local:  [<IP_ADDRESS>] uses pre-shared key authentication
submariner-cable-nmanos-cluster-b-tunnel-10-166-0-13:   remote: [<IP_ADDRESS>] uses pre-shared key authentication
submariner-child-submariner-cable-nmanos-cluster-b-tunnel-10-166-0-13:   child:  <IP_ADDRESS>/32 <IP_ADDRESS>/16 <IP_ADDRESS>/14 === <IP_ADDRESS>/32 <IP_ADDRESS>/16 <IP_ADDRESS>/14 TUNNEL
Security Associations (0 up, 1 connecting):
submariner-cable-nmanos-cluster-b-tunnel-10-166-0-13[1]: CONNECTING, <IP_ADDRESS>[%any]...<IP_ADDRESS>[%any]
submariner-cable-nmanos-cluster-b-tunnel-10-166-0-13[1]: IKEv2 SPIs: f397df0d07040eed_i*<PHONE_NUMBER>000000_r
submariner-cable-nmanos-cluster-b-tunnel-10-166-0-13[1]: Tasks active: IKE_VENDOR IKE_INIT IKE_NATD IKE_CERT_PRE IKE_AUTH IKE_CERT_POST IKE_CONFIG CHILD_CREATE IKE_AUTH_LIFETIME

subbmariner no connection if gw node does not have external ip.log

with on-prem cluster and public cluster, If one of the gateway nodes on the public cluster does not have an external ip, submariner will fail to connect to it later. SubCtl should probably alert if no external ip exists.

@nyechiel  I believe this is a useful thing to add.
Shall we change it to feature request ?

bump

bump

bump

Not relevant any more. Closing it.


Django style connection settings

Hi @robinedwards, thank you so much for this!
In the work I did do, I wrote a new Database class in the utils that would support configuring the Neo4j settings like you might a RDBMS:
""" New format for the config parameters (Django):
        NEO4J_DATABASE = {
                'USER': '<username>',
                'PASSWORD': '<password>',
                'HOST': '<uri>',
                'PORT': '<port>',
                'BOLT': True|False,
                'SECURE': True|False
        }
"""

I can't remember how far I got with this, but would you be interested in using it?
utils.zip

Np :-) re the settings I think in core I am ok. But I think it would work
great in a django plugin. Which I think we should build.
On 27 Nov 2016 18:21, "the4thv"<EMAIL_ADDRESS>wrote:

Hi @robinedwards https://github.com/robinedwards, thank you so much for
this!
In the work I did do, I wrote a new Database class in the utils that would
support configuring the Neo4j settings like you might a RDBMS:
""" New format for the config parameters (Django):
NEO4J_DATABASE = {
'USER': '',
'PASSWORD': '',
'HOST': '',
'PORT': '',
'BOLT': True|False,
'SECURE': True|False
}
"""
I can't remember how far I got with this, but would you be interested in
using it?
utils.zip
https://github.com/robinedwards/neomodel/files/614830/utils.zip
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/robinedwards/neomodel/issues/219, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJ0YdUm_OwxpkdfiDRqUkJ5W9S0_omWks5rCbv_gaJpZM4K9MyQ
.

My plan was to support both calls in core and underlying remove passing username and password in the connection string and use Py2Neo's Graph() call with parameters instead. I make a branch, I'll move the django specific logic out into 'plugins/django.py' and keep the amendment connection call in core, ok?

Ah py2neo has been removed entirely it uses neo4j_driver internally. Re
django/plugins I was actually wanting to create a new python package
django_neomodel which handles all the django integration. I think the term
is a django 'app' in there lingo. Do you follow?
On 1 Dec 2016 10:17 a.m., "the4thv"<EMAIL_ADDRESS>wrote:
My plan was to support both calls in core and underlying remove passing
username and password in the connection string and use Py2Neo's Graph()
call with parameters instead. I make a branch, I'll move the django
specific logic out into 'plugins/django.py' and keep the amendment
connection call in core, ok?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/robinedwards/neomodel/issues/219#issuecomment-264120824,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJ0YTL-VfizE31ZgLSFOFoQrunL19F7ks5rDpCOgaJpZM4K9MyQ
.

Ah ok, no worries. I can work with that. Regarding the use of another python package for django, are you thinking of other functionality for django? Just going on my usage at the moment: neomodel is really good as it is and I wouldn't want to have to re-write anything in the models. If it's just the settings then I'm not sure it would justify an entire package itself?

Ah don't worry none of the API for neomodel would change.
The only thing that may move would be the signals integration. Initially it
may just be settings, some documentation and test integration but could
grow to include other things
On 2 December 2016 at 21:01, the4thv<EMAIL_ADDRESS>wrote:

Ah ok, no worries. I can work with that. Regarding the use of another
python package for django, are you thinking of other functionality for
django? Just going on my usage at the moment: neomodel is really good as it
is and I wouldn't want to have to re-write anything in the models. If it's
just the settings then I'm not sure it would justify an entire package
itself?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/robinedwards/neomodel/issues/219#issuecomment-264548670,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJ0YfX6f247QevpsbodwtU49-oHD3Bpks5rEHkEgaJpZM4K9MyQ
.

Hi Robin, is there a chance we chat a a skype chat on this? I really want to start coding on this, but I'm not sure how, for example, you would import neomodel into Django if we're using a 'django-neomodel' library as well as neomodel and how you envisage this working without making it so people need to refactor their code. I'll send you an email.

Hey not sure whether I can get to Skype but feel free to send me a email
On 4 Dec 2016 14:45, "the4thv"<EMAIL_ADDRESS>wrote:

Hi Robin, is there a chance we chat a a skype chat on this? I really want
to start coding on this, but I'm not sure how, for example, you would
import neomodel into Django if we're using a 'django-neomodel' library as
well as neomodel and how you envisage this working without making it so
people need to refactor their code. I'll send you an email.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/robinedwards/neomodel/issues/219#issuecomment-264704773,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJ0YT6zt25Lgspjf1QRpsEJKwo2LWFRks5rEsPegaJpZM4K9MyQ
.

@the4thv I've released the django plugin now https://github.com/robinedwards/django-neomodel so closing this issue.


Tabstrip.createTab creates bad ids.

Tabstrip.createTab uses the current number of tabs to create ids for the new title and tab objects. When using it e.g. to create a second tab, close the first, then create another tab, that last tab won't be created because of a duplicate id.
See also this code example: http://plnkr.co/edit/eGEiG66L989QGYLJxtps
Possible solutions could be to keep an internal counter or not assign ids at all.
Best regards, Rolf.
PS: Also, unless you're going to deprecate the call, please document that it returns the new tab (not void as it says now).

Hello rg1,
thank you for reporting this issue. I was able to reproduce it and contacted the control owner of the tabstrip control. We will get back to you soon here.
Great hint for the documentation too, thank you!
Internally tracked as: #1670047917
Kind Regards,
Michael

Fix has been submitted but keeping the issue open for the documentation suggestion above.
Contacted @nvankov again

The documentation has been fixed as well. Thanks for the heads up.
Best regards,
Nikolay


[To Main] - DESENG-597 - Fixed : Date shown on rejection email preview is incorrect

Issue #: https://apps.itsm.gov.bc.ca/jira/browse/DESENG-597
Related PR : https://github.com/bcgov/met-public/pull/2471
Description of changes:

Fixed the date formatting issue and using the end_date in the email preview
Updated unit tests

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 75.78%. Comparing base (bb62952) to head (6ec7658).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2505      +/-   ##
==========================================
- Coverage   75.78%   75.78%   -0.01%
==========================================
  Files         590      597       +7
  Lines       21133    21334     +201
  Branches     1529     1568      +39
==========================================
+ Hits        16016    16167     +151
- Misses       4870     4913      +43
- Partials      247      254       +7

Flag
Coverage Δ

metweb
63.81% <100.00%> (+0.21%)
:arrow_up:

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

Files
Coverage Δ

...omments/admin/review/emailPreview/EmailPreview.tsx
82.60% <100.00%> (ø)

... and 7 files with indirect coverage changes


Node DeprecationWarning Related to fs.rmdir

Environment info

NooBaa Version: master
Platform: CI

Actual behavior

I noticed that we have DeprecationWarning related to fs.rmdir.

Expected behavior

Avoid having this warning.

Steps to reproduce

When submitting a pull request/push in the run-nc-unit-tests logs you can see this warning.

More information - Screenshots / Logs / Other output
I saw this in the CI of run-nc-unit-tests (see here):

(node:8) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead

@shirady I couldn't find the usage of fs.rmdir() in our code. We are using rmdir() that implemented in napi layer not node functionality.
I could see fs.rmdir() in nc_coretest.js we might need to update that.
cc : @romayalon


[natural-language-classifier] testClassifyWithTrainedClassifier crashing test execution when not possible to create classifiers

If you run the unit tests testClassifyWithTrainedClassifier(), and you're not allowed to create new classifier (Error 400, 8 classifiers maximum when using Bluemix trail account), the test execution crashes due to EXC_BAD_INSTRUCTION, stopping the execution of the remaining tests.

To reproduce the error you should:

Create a Bluemix trial account
Create the credentials to use the Natural Language Classifier API
Configure Credentials.plist
Create 8 classifiers using the NLC API
Run the testClassifyWithTrainedClassifier(), on NaturalLanguageClassifierTests class

This issue is fixed in the rest-kit branch, where we:

No longer need to force-unwrap the classifier, given the separate success and failure closures.
Set continueAfterFailure = false.


feat(client): add AutoLink component

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

18 of 59 (30.51%)  changed or added relevant lines in 6 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.7%) to 41.11%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

packages/client/src/router/resolveRoute.ts
0
1
0.0%

packages/client/src/router/resolveRoutePath.ts
0
2
0.0%

packages/client/src/components/RouteLink.ts
0
9
0.0%

packages/client/src/components/AutoLink.ts
0
29
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.7%

Covered Lines:
693

Relevant Lines:
1721

💛  - Coveralls

See here https://github.com/vuejs/router/blob/8fbd9c427447a8e4a6ff486ae94224d040fb7b00/packages/router/src/RouterView.ts#L34
I strongly recommend preserving the prop interface.


test-branch/execute-job/wrong-comment-on-pr/cf86b4ae-96d4-437c-b781-467342ce4f28

PR for testing 3e1370f3051a26d2d2e7065b09366d0670eca1a9

comment 1


Incomprehensible karma error when using mat-form-field

Bug, feature request, or proposal:
Karma Disconnected, because no message in 10000 ms when we not imported BrowserAnimationModdule in testbed and use mat-form-field (or maybe something else too)
What is the expected behavior?
Must be error Please include either "BrowserAnimationsModule" or "NoopAnimationsModule" in your application.
What is the current behavior?

Karma Disconnected, because no message in 10000 ms

What are the steps to reproduce?
Providing a StackBlitz reproduction is the best way to share your issue.
StackBlitz starter: https://goo.gl/wwnhMV

Create a component with mat-form-field component
Run karma test without importing BrowserAnimationsModule in testbed

What is the use-case or motivation for changing an existing behavior?
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 5.2.0
Material 5.2.0
Is there anything else we should know?

Unfortunately, the error that is being seen is because Karma is timing out.  It is not possible for the code being tested to determine it is timing out and throw an error.  Because of this we are not able to provide different error messaging from Karma.


Add mirrors for the fedora image

What this PR does / why we need it:
Add mirrors for the Fedora image
I chose one with the biggest bandwidth from https://admin.fedoraproject.org/mirrormanager/mirrors/Fedora/29
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

@slintes I still can see the problem with Fedora image, so I do not really sure it helps.
I think the problem, that download partially succeeds, but after checking the hash sum fails.

Too bad. But still better than only having 1 url only, that way we at least prevent errors when a mirror is down.
Maybe even remove download.fedoraproject.org? Maybe that's the only one causing problems?

@rmohr Checked bazel cache, and it has the Fedora image, so looks like we have some problems with connectivity to bazel cache

@rmohr Propose to build artifacts, before running the cluster, so I will try it

@cynepco3hahue removed the cache clean and the error is back. Could it be that stdci recycles the docker volume and your clean  really did the trick?

But still not sure if it wouldn't have occurred with the cache clean again.

@rmohr Clean does not really help, I still can see 3 lanes with the same error. Also, I added curl before and it succeeds to download the image without any troubles. I currently do not have any other ideas, any thoughts?

Currently, docker volumes are not being kept between jobs. Can we use a bind mount instead of a docker volume?

It indeed looks like the download didn't finished successfully, thus the sha256 was wrong. Do we know from where it tried to download the image greenhouse or fedora mirrors?

Currently, docker volumes are not being kept between jobs. Can we use a bind mount instead of a docker volume?

That is perfect. We don't want to keep them.

It indeed looks like the download didn't finished successfully, thus the sha256 was wrong. Do we know from where it tried to download the image greenhouse or fedora mirrors?

We still have the Fedora mirror on the first place. So it is still preferred. Maybe we just have to move it to the end of the list.
Gal could you also verify that all nodes have sufficient space left for docker in docker? It still looks a little bit like it might be related to a single node issue.

Currently, docker volumes are not being kept between jobs. Can we use a bind mount instead of a docker volume?

That is perfect. We don't want to keep them.

It indeed looks like the download didn't finished successfully, thus the sha256 was wrong. Do we know from where it tried to download the image greenhouse or fedora mirrors?

We still have the Fedora mirror on the first place. So it is still preferred. Maybe we just have to move it to the end of the list.

I would like to understand if the connectivity issue is between the ci pod and greenhouse pod, or between the ci pod and the fedora mirror. How can we know if it failed to fetch the image from cache or not?

Gal could you also verify that all nodes have sufficient space left for docker in docker? It still looks a little bit like it might be related to a single node issue.
I've checked it now, all nodes have 200GB+ free space.

ci test please

ci test please

ci test please

@rmohr @slintes
I think I will close this PR, it just does not solve anything, we still have two problems:

from some reason, build does not take fedora image from greenhouse
it downloads only part of the image, so checksum does not correct(I think it some bazel bug)

We should really try downgrading to bazel 0.21.

Closing this one works for me.


what-if result inaccuracies across scope boundaries.

Discussed in https://github.com/Azure/bicep/discussions/10332

Originally posted by JoshuaXu-Wen April  6, 2023
Hi there, I write a resource group module, the main.bicep target scope is 'resourceGroup'.
module resourceGroupPrimary 'Module/resourceGroup.bicep' = {
  scope: subscription(subscriptionId)
  name: 'resourceGroupPrimaryDeploy-${uniqueString(deployment().name)}'
  params: {
    location: locationPrimary
    rgName: rgPrimaryName
    tags: tags
  }

When I use what-if to verify the result, the deployment gives the following error:
DeploymentWhatIfResourceError - The request to predict template deployment changes to scope '/subscriptions/XXXXXXXXXXXXX/resourceGroups/rg-Backup' has failed due to a resource error. See details for more information.
ResourceGroupNotFound - Resource group 'rg-Primary' could not be found.
If I create the resourceGroup, the script can create the resource group 'rg-Primary' correctly.
az bicep version: Bicep CLI version 0.16.1 (d77dcc750a)

more information
@JoshuaXu-Wen
Adding code in case anyone else wants to test this out OR view the scope specific issue examples
main. Bicep - resource group scoped deployment
param location string = 'eastus'
param rgName string = 'myRG2'

// targetScope = 'subscription'

module RG 'temp.bicep' = {
  name: 'rg'
  scope: subscription()
  params: {
    location: location
    rgName: rgName
  }
}

output rgname string = RG.outputs.RGName

temp.bicep
param rgName string
param location string
param tags object = {}

targetScope = 'subscription'

resource RG 'Microsoft.Resources/resourceGroups@2022-09-01' = {
  name: rgName
  location: location
  tags: tags
  properties: {}
}

output RGName string = RG.name

If the resource group does not exist, you will get an error, since going across scopes it is unable to complete the what-if

'The request to predict template deployment changes to scope '/subscriptions/4185fa9b-f470-466a-b3ae-8e6c3314a543/resourceGroups/AEU1-PE-CTL-RG-D1' has failed due to a resource error. 🟥

if the resource group does exist, it doesn't detect it and it shows it will create it. 🟥

It appears this is a result from going across scopes: Resource Group --> Subscription --> Resource group.
The workaround

Deploy in the subscription scope initially and what-if works as expected

param location string = 'eastus'
param rgName string = 'myRG2'

targetScope = 'subscription'

module RG 'temp.bicep' = {
  name: 'rg'
  // scope: subscription()
  params: {
    location: location
    rgName: rgName
  }
}

output rgname string = RG.outputs.RGName

When no RG exists - corretly shows it will be created ✅

When the RG exists - correctly shows it will be ignored ✅

Interesting finding. I'm going to move this to the arm-template-whatif repo


Is it possible to treat the stdout as an integer instead of a string?

I would like to treat the stdout value of the previous step as an integer, not a string. Is it possible to do this?
steps:
  -
    exec:
      # generate random number
      command: echo -n `seq 1 100000 | sort -R | head -n 1`
  -
    req:
      /sample:
        post:
          body:
            application/json:
              id: "{{ steps[0].stdout }}" # require integer but the actual value passed is string

Alternatively, is there a way to get a random number using built-in features?

I would like to treat the stdout value of the previous step as an integer, not a string. Is it possible to do this?

You can use int().
desc: Test desc
runners:
  req: https://httpbin.org
steps:
  -
    exec:
      # generate random number
      command: |
        echo `seq 1 100000 | sort -R | head -n 1`

  -
    req:
      /anything:
        post:
          body:
            application/json:
              id: "{{ int(steps[0].stdout) }}"
    dump:
      current.res.body

$ runn run tmp.yml
{
  "args": {},
  "data": "{\"id\":11211}",
  "files": {},
  "form": {},
  "headers": {
    "Accept-Encoding": "gzip",
    "Content-Length": "12",
    "Content-Type": "application/json",
    "Host": "httpbin.org",
    "User-Agent": "Go-http-client/2.0",
    "X-Amzn-Trace-Id": "Root=1-651e7fa5-777242411278879e43a4d581"
  },
  "json": {
    "id": 11211
  },
  "method": "POST",
  "origin": "<IP_ADDRESS>",
  "url": "https://httpbin.org/anything"
}
.

1 scenario, 0 skipped, 0 failures

Alternatively, is there a way to get a random number using built-in features?

You can use faker.IntRange(1, 100000)
<EMAIL_ADDRESS>

That's just what I was looking for. Awesome, thanks!


.NET stack

request for a stack for dotnet 3.0

Thanks @jaricsng
We are always trying to add more stacks to expand the set of technologies currently supported.
Would you be willing to make a start at this? Appspody team will be happy to help and support you in creating this.


(dev-branch) Model Explorer not loading without page refresh

I start with an empty ADT instance and then upload a set of model files.  If I go straight to the Model View tab, nothing shows up.  The model will only show up after I refresh the entire ADT-Explorer web page with the browser refresh button.  I would expect viewing a newly uploaded model to work without a page refresh

Hi @stevebus ,
I have tried to reproduce this issue without much luck.
Steps:

Empty ADT instance.
Upload multiple models via bulk import.
Graph reloaded as expected.

Just wanted to check a few things:

What browser are you using?
Have you pulled the latest from develop?

Thanks for the additional info!

Hey @jamiewilbraham  - I just duplicated it again..  In my pull of the development branch, I did a git pull to bring it up to date, ran npm install again, and then ran it..
I created a completely fresh ADT instance, launched ADT Explorer from my dev branch, imported the same model files, immediately clicked on "model view"  (not graph)  without doing anything else and got a blank screen again.
I'm using Microsoft Edge as the browser.   I also heard from another member of the ADT team who has the same experience.
You said above "Graph loaded as expected" -- to confirm, you mean the 'model' graph right (without running any queries), not the twin instance graph.

As an aside, as mentioned above, after hitting the "Refresh" button in the browser, the model view loads

Hi @stevebus,
Thanks for providing this additional information. Yes, I was referring to the model graph. However, I have since been able to reproduce the issue, so thanks for reporting it.
After the initial load of models in the instance (which doesn't load the nodes on the model graph), if you delete all the models and then repeat the steps (without a refresh), do you still get the issue?
I would just like to confirm if this is specific to fresh ADT instances.
Thanks for your help!

Hey @jamiewilbraham  --   I deleted all the models and then imported a fresh set of models (I picked a different set to avoid any potential caching benefits).  I then went straight to the model view and it worked fine!   So it looks like it might be just related to a totally fresh ADT instance, as you suspect.

Great - thanks for confirming @stevebus! We are looking into it.

@stevebus - this should now be fixed in the development branch

Closing as the fix is now in the new default main branch here: https://github.com/Azure-Samples/digital-twins-explorer
Thanks again for reporting!


[question] Prevent gap between media

I try to load 2 videos after another without having a gap between them (the desktop is shown for a very short period of time). I tried with the ListPlayer() but it did not work.
My next idea was to pause at the last frame, make sure the next video is playing and then stop the current media. Hence this question. However, this causes the flickering between the two videos until the first video is stopped.
Idea 3: Every 10ms check if the video 2 has MediaTime() > 0 and stop video 1. I now have only 1 "Flicker-Frame". Still not what I want.
I do not know what to do next. Do you have an idea? How to prevent the gap between to videos?
Videos are played on a Raspberry 4 with --vout mmal_vout.

Hi @masseelch. I don't think there's a good way to accomplish this in libVLC 3. I know that this feature is being worked on in libVLC 4, but that is not out yet. You can join the libVLC Discord server (there's a link badge in the README of this project) and ask there (the General channel is probably most appropriate) but as far as I know, this is not possible in the current version on libVLC.

I'll try that, thank you!


replacements-config.yaml is a 1.5.0+ feature but is not identified as such

Describe the bug
https://docs.aws.amazon.com/solutions/latest/landing-zone-accelerator-on-aws/working-with-solution-specific-variables.html#parameter-store-reference-variable
The implementation guide describes the replacements-config but does not indicate that it is a 1.5.0+ feature.

Hi @jtirrell-amazon , thanks for bringing this to our attention. The page has since been updated to clarify the functionality was introduced in v1.5.0.


First build of learn-ocaml-corpus fails

Following @yurug's suggestion https://github.com/ocaml-sf/learn-ocaml/pull/302#issuecomment-520208261, I've tried compiling learn-ocaml/master = 718d1f12ff2ef78b1db34d2f70e4b24ddad0ed53 + learn-ocaml-corpus and noticed a subtle bug: the first build of learn-ocaml-corpus fails, but the second succeeds.
For the record, I summarize below the opam dependencies I used to reproduce this.
OPAM dependencies
$ opam list
# Packages matching: installed
# Name                  # Installed  # Synopsis
asak                    0.1          Partitioning OCaml codes
astring                 0.8.3        Alternative String module for OCaml
base                    v0.9.4       Full standard library replacement for OCaml
base-bigarray           base
base-bytes              base         Bytes library distributed with the OCaml compiler
base-num                base         Num library distributed with the OCaml compiler
base-threads            base
base-unix               base
base64                  2.3.0        Base64 encoding for OCaml
bigarray-compat         1.0.0        Compatibility library to use Stdlib.Bigarray when possible
biniou                  1.2.0        Binary data format designed for speed, safety, ease of use and backw
bos                     0.2.0        Basic OS interaction for OCaml
checkseum               0.0.3        Adler-32, CRC32 and CRC32-C implementation in C and OCaml
cmdliner                1.0.3        Declarative definition of command line interfaces for OCaml
cohttp                  1.1.1
cohttp-lwt              1.1.1        An OCaml library for HTTP clients and servers
cohttp-lwt-unix         1.1.1        An OCaml library for HTTP clients and servers
conduit                 1.3.0        An OCaml network connection establishment library
conduit-lwt             1.3.0        An OCaml network connection establishment library
conduit-lwt-unix        1.3.0        An OCaml network connection establishment library
conf-git                1.0          Virtual package relying on git
conf-libev              4-11         High-performance event loop/event model with lots of features
conf-m4                 1            Virtual package relying on m4
conf-openssl            1            Virtual package relying on an OpenSSL system installation
conf-pkg-config         1.1          Virtual package relying on pkg-config installation
conf-which              1            Virtual package relying on which
cppo                    1.6.6        Code preprocessor like cpp for OCaml
cstruct                 3.3.0        Access C-like structures directly from OCaml
decompress              0.8.1        Implementation of Zlib in OCaml
digestif                0.7.1        Hashes implementations (SHA*, RIPEMD160, BLAKE2* and MD5)
dune                    1.6.3        Fast, portable and opinionated build system
easy-format             1.3.1        High-level and functional interface to the Format module of the OCam
eqaf                    0.4          Constant-time equal function on string
ezjsonm                 0.6.0        An easy interface on top of the Jsonm library
fieldslib               v0.9.0       Syntax extension to define first class values representing record fi
fmt                     0.8.6        OCaml Format pretty-printer combinators
fpath                   0.7.2        File system paths for OCaml
hex                     1.4.0        Library providing hexadecimal converters
ipaddr                  2.8.0        IP (and MAC) address manipulation
jbuilder                transition   This is a transition package, jbuilder is now named dune. Use the du
js_of_ocaml             3.3.0        Compiler from OCaml bytecode to Javascript
js_of_ocaml-compiler    3.3.0        Compiler from OCaml bytecode to Javascript
js_of_ocaml-lwt         3.3.0        Compiler from OCaml bytecode to Javascript
js_of_ocaml-ppx         3.3.0        Compiler from OCaml bytecode to Javascript
js_of_ocaml-toplevel    3.3.0        Compiler from OCaml bytecode to Javascript
js_of_ocaml-tyxml       3.3.0        Compiler from OCaml bytecode to Javascript
jsonm                   1.0.1        Non-blocking streaming JSON codec for OCaml
logs                    0.6.3        Logging infrastructure for OCaml
lwt                     3.3.0        Promises, concurrency, and parallelized I/O
lwt_react               1.1.1        Helpers for using React with Lwt
lwt_ssl                 1.1.2        OpenSSL binding with concurrent I/O
magic-mime              1.1.1        Map filenames to common MIME types
markup                  0.8.0        Error-recovering functional HTML5 and XML parsers and writers
merlin                  3.1.0        Editor helper, provides completion, typing and source browsing in Vi
num                     0            The Num library for arbitrary-precision integer and rational arithme
ocaml                   4.05.0       The OCaml compiler (virtual package)
ocaml-base-compiler     4.05.0       Official 4.05.0 release
ocaml-compiler-libs     v0.9.0       OCaml compiler libraries repackaged
ocaml-config            1            OCaml Switch Configuration
ocaml-migrate-parsetree 1.3.1        Convert OCaml parsetrees between different versions
ocamlbuild              0.14.0       OCamlbuild is a build system with builtin rules to easily build most
ocamlfind               1.8.0        A library manager for OCaml
ocamlgraph              1.8.8        A generic graph library for OCaml
ocp-build               1.99.20-beta Project builder for OCaml
ocp-indent-nlfork       1.5.3        ocp-indent library, "newline tokens" fork
ocp-ocamlres            0.4          Manipulation, injection and extraction of embedded resources
ocplib-json-typed       0.6          Type-aware JSON and JSON schema utilities
odoc                    1.3.0        OCaml documentation generator
omd                     1.3.1        A Markdown frontend in pure OCaml.
opam-core               2.0.4
opam-file-format        2.0.0        Parser and printer for the opam file syntax
opam-format             2.0.4
opam-installer          2.0.4
optint                  0.0.2        Abstract type on integer between x64 and x86 architecture
pprint                  20180528     A pretty-printing combinator library and rendering engine
ppx_ast                 v0.9.1       OCaml AST used by Jane Street ppx rewriters
ppx_core                v0.9.3       Standard library for ppx rewriters
ppx_cstruct             3.3.0        Access C-like structures directly from OCaml
ppx_derivers            1.2.1        Shared [@@deriving] plugin registry
ppx_driver              v0.9.2       Feature-full driver for OCaml AST transformers
ppx_fields_conv         v0.9.0       Generation of accessor and iteration functions for ocaml records
ppx_metaquot            v0.9.0       Write OCaml AST fragment using OCaml syntax
ppx_optcomp             v0.9.0       Optional compilation for OCaml
ppx_sexp_conv           v0.9.0       Generation of S-expression conversion functions from type definition
ppx_tools               5.0+4.05.0   Tools for authors of ppx rewriters and other syntactic tools
ppx_tools_versioned     5.2.2        A variant of ppx_tools based on ocaml-migrate-parsetree
ppx_traverse_builtins   v0.9.0       Builtins for Ppx_traverse
ppx_type_conv           v0.9.1       Support Library for type-driven code generators
re                      1.9.0        RE is a regular expression library for OCaml
react                   1.2.1        Declarative events and signals for OCaml
reactiveData            0.2.1        Functional reactive programming with incremental changes in data str
result                  1.4          Compatibility Result module
rresult                 0.6.0        Result value combinators for OCaml
seq                     0.1          Compatibility package for OCaml's standard iterator type starting fr
sexplib                 v0.9.3       Library for serializing OCaml values to and from S-expressions
ssl                     0.5.7        Bindings for OpenSSL
stdio                   v0.9.1       Standard IO library for OCaml
stdlib-shims            0.1.0        Backport some of the new stdlib features to older compiler
stringext               1.6.0        Extra string functions for OCaml
topkg                   1.0.0        The transitory OCaml software packager
tyxml                   4.3.0        TyXML is a library for building correct HTML and SVG documents
uchar                   0.0.2        Compatibility library for OCaml's Uchar module
uri                     1.9.7        An RFC3986 URI/URL parsing library
uutf                    1.0.1        Non-blocking streaming Unicode codec for OCaml
yojson                  1.5.0        Yojson is an optimized parsing and printing library for the JSON for

Example session
$ cd .../learn-ocaml && rm -fr www

$ make && make opaminstall && learn-ocaml --repo=../learn-ocaml-corpus build serve
[…]
Learnocaml v.0.11 running.
Updating app at ./www
counting_trees               [OK]
enumerating_trees            [OK]
leftist_heaps                [OK]
merge_sort                   [OK]
persistent_arrays            [OK]
pprint                       [OK]
random_access_lists          [OK]
symbolic_sequences_data      [OK]
symbolic_sequences_objects     [OK]
Cannot process exercises: Unix.Unix_error(Unix.EEXIST, "mkdir", "./www/static/tree_iterators")

$ make && make opaminstall && learn-ocaml --repo=../learn-ocaml-corpus build serve
[…]
Learnocaml v.0.11 running.
Updating app at ./www
counting_trees           (no changes)
enumerating_trees        (no changes)
leftist_heaps            (no changes)
merge_sort               (no changes)
persistent_arrays        (no changes)
pprint                   (no changes)
random_access_lists      (no changes)
symbolic_sequences_data  (no changes)
symbolic_sequences_objects (no changes)
tree_iterators               [OK]
Learnocaml server v.0.11 starting on port 8080
Found the following teacher tokens:
[…]

$ git rev-parse HEAD
718d1f12ff2ef78b1db34d2f70e4b24ddad0ed53

$ cd ../learn-ocaml-corpus && git rev-parse HEAD
8f97c4e831dd04e2659b9122386b96edc90d1a9a

@yurug I suppose the error at stake Cannot process exercises: Unix.Unix_error(Unix.EEXIST, "mkdir", "./www/static/tree_iterators") is triggered in learnocaml_process_exercise_repository.ml, but I did not investigate further.

By the way, this makes me think it could be worth it to add another Travis job to learn-ocaml's CI, to test it against the corpus…

I think I’m onto something on this one.  If I understand the code correctly, here: https://github.com/ocaml-sf/learn-ocaml/blob/a13226be6f94d33640a08d43542dbba4c681c276/src/repo/learnocaml_process_exercise_repository.ml#L231-L238
All the subdirectories of exercises are copied in parallel, and the parent directory is created if it doesn't exist.  If there is only one subdirectory (like in all exercises, but not in tree_iterators), there is no problem: mkdir_p will test if the parent exist.  As it does not, it will create it, then create the subdirectory.  But I believe that if multiple subdirectories exists, each thread will test if the parent exist and create it in parallel.  Only one of them should succeed, all others would fail.

I can confirm that creating the directory of the exercise before copying subdirectories seems to fix the issue.


getpixelcolor()

A very nice and simple library. I am glad I found it. In the future, it might be useful to have a getpixelcolor() that returns the current color code of the given LED.

Hi. Glad you found it useful.
Should be able to implement a method like that. I've been watching progress on version 3 of the arduino-esp32 core, looking to time the next release with that as it will break LiteLED due to a complete rewrite by Espressif of the RMT implementation.
In the mean time: could you let me know which LED type(s) you use with LiteLED and roughly the number of LED's. Curious about how the library is being used.

Wasn't too hard to add. See new Release v1.1.0
Let me know how it works out for you.


Unwanted bar appearing on the navbar of the CART page

![Uploading image.
A colored bar appears on the top of the page.

@khushi-joshi-05  Assign it to me
Thank you

show your screenshot.


What is an OData filter?

The term 'OData' filter under --filter option for az ad sp list should be a link here to a description of what that means.
This is REALLY important because az ad sp list shows pages and pages and pages of information, most of which isn't relevant, so filtering feels critical.

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

ID: e99d25ff-03e2-e015-37f4-a29b59ec50d4
Version Independent ID: 1a8e88ed-72c7-fbe7-b0ad-68f23b3946cd
Content: az ad sp
Content Source: src/azure-cli/azure/cli/command_modules/role/_help.py
Service: active-directory
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

add to S168

I was really hoping this issue would have an explanation and examples for OData filters!

Some old documentation:
https://docs.microsoft.com/en-us/previous-versions/azure/ad/graph/howto/azure-ad-graph-api-supported-queries-filters-and-paging-options#filter
Examples:
az ad sp list --filter "displayName eq 'governance'" --output jsonc
az ad sp list --filter "startswith(displayName, 'gov')" --query "[].displayName" --output yaml

This issue is fixed in the sprint 167


Add SPM support

MockNRoll should support Swift Package Manager

This can be tested in the "xcode11" branch.

This is now available in the 0.1.0 beta.


'autoHideArrows' options is not documented in the readme

Scooch supports this option autoHideArrows but it's not documented in the readme yet.

@vmarta good catch! Want to open up a quick PR with the change, and we'll merge it in?

Will fix as part of v1.0.0 release.


Add Serilog Support to log Messages

This can be implemented easily Created the custom services that takes a ILogger however is a good opportunity also to Implement MessageTranslation to configure how a Message want to be loged of with SeriLog.

What is your take on these kind of custom implementations, do you want to have them as seperate nuget packages? If not it means every consumer is forced on external dependencies even if they are not using it.


Allow filtering events on multiple event/containers/images

Signed-off-by: Sylvain Baubeau<EMAIL_ADDRESS>

A less intrusive fix could be :
diff --git a/dockerclient.go b/dockerclient.go
index fb1fdd9..e83a761 100644
--- a/dockerclient.go
+++ b/dockerclient.go
@@ -442,13 +442,13 @@ func (client *DockerClient) MonitorEvents(options *MonitorEventsOptions, stopCha
 		if options.Filters != nil {
 			filterMap := make(map[string][]string)
 			if len(options.Filters.Event) > 0 {
-				filterMap["event"] = []string{options.Filters.Event}
+				filterMap["event"] = strings.Split(options.Filters.Event, ",")
 			}
 			if len(options.Filters.Image) > 0 {
-				filterMap["image"] = []string{options.Filters.Image}
+				filterMap["image"] = strings.Split(options.Filters.Image, ",")
 			}
 			if len(options.Filters.Container) > 0 {
-				filterMap["container"] = []string{options.Filters.Container}
+				filterMap["container"] = strings.Split(options.Filters.Container, ",")
 			}
 			if len(filterMap) > 0 {
 				filterJSONBytes, err := json.Marshal(filterMap)

but it may be a bit awkward to use the Event property for specifying multiple events.

ping @samalba

ping @vieux @donhcd :-/

LGTM. fwiw I don't think anybody is really actively maintaining this repo anymore, and docker's supported go client is https://github.com/docker/engine-api and it seems like it does have the filters working the way you want https://github.com/docker/engine-api/blob/master/client/events.go#L36 though the return types are atrocious :(

@donhcd Thank you.
That may be a good idea to change the "Well maintained docker client library." baseline then :-)


Generate missing models from legacy spec

This spawns from https://github.com/opensearch-project/opensearch-api-specification/issues/80
Basically use legacy spec to generate smithy models so we don't have to fill out 308 operations by hand.
The translator code can be found here: https://github.com/nhtruong/opensearch-smithy-spec-translator

Goals
We chose maintaining OpenSearch API Spec via Smithy, even though the end-result is standard OpenAPI spec, mainly for its maintainability. So, the generated Smithy Spec should take advantage of Smithy unique features while assure that the models can still be properly translated to OpenAPI:

Each OpenSearch action, each comprised of one or many API operations, are grouped into folders. For example, the smithy files for indicies.create action will be stored in ./model/indices/create folder. (This grouping is impossible with OpenAPI 3.1, one of many reasons we chose Smithy)
Each action has 2 smithy files:

operations.smithy: Describes the operations of said action
structures.smithy: Describes the structures of the Inputs and Outputs of the operations.

Most parameters are not only shared within the operations of the same action, but they are also reused in other actions. The parameter definitions, therefore, are stored in common locations for resuse. For example, common_booleans.smithy and common_string_lists.smithy

@nhtruong the choice of Smithy is still not obvious, specifically taking into account plugins and extensions, I believe there are compelling arguments to use OpenAPI 3.0+ directly [1], without Smithy shim.
[1] https://github.com/opensearch-project/opensearch-clients/issues/55

@reta I'm still drafting this comment and accidentally hit Comment. Still editing it now. It will be a bit clearer. As discussed in https://github.com/opensearch-project/opensearch-api-specification/issues/80, the end result will be OpenAPI 3.1. We're only using smithy, for now at least, as a device to backfill missing info (like Output schemas, and Body schemas), because it's easier to do so.

Reopening this issue, since there is a part 2 for the PR.