 We ran into several issues and made several workarounds for this.
I think it'd be great if we could write up this experience in a short blog post. I believe all of our scripts are here: https://plmlab.math.cnrs.fr/jupytercloud/kubernetes so perhaps this just means adding some context to them as well as a bit of narrative to help users make their way through the code (as well as a section on the particular issues we faced)
I think this could be a great way to provide a path forward for those who wish to deploy on OpenStack, and would also be a nice artifact to come out of our meeting.

There is also the kubernetes bare metal deployment @bitnik is working on

@choldgraf: As part of the DFG project iLCM @bitnik is currently setting up http://notebooks.gesis.org/ .
We have already asked @betatim to let us know when a european meetup (maybe in Zurich) will take place to learn more about bh.
Our project is in the very early stages but we aim in the longer term to work on enabling named-servers jupyterhub/jupyterhub#1409 with persistent storage #377 for authenticated users #323 . Our institute is dedicated to open source and work will be committed back as fare as possible.

For whatever it's worth, you may be interested by this blog post; kind of a personal wish list for our instance:
http://opendreamkit.org/2018/03/15/jupyterhub-binder-convergence/

@nthiery thank you.

@choldgraf we made the github repo of GESIS Notebooks public: https://github.com/gesiscss/orc

@psychemedia not for now but the work is almost done.
We plan to write a blog post on Medium soon which will explain how to install jupyterhub using Kubernetes on OpenStack.
An other post will follow for binderhub installation.

@gouarin Thanks - looking forward to giving it a try...

@gouarin have you been in touch at all with people at Compute Canada? They've got a Kubernetes-on-openstack deployment of JupyterHub running as well. I can try to hunt down the URL to their configuration if it'd be helpful

@choldgraf sorry for the delay.
We worked hard on that this week and we finally solved our issues with the MTU. So now, we have a jupyterhub and a binderhub up and running (we tried to deploy both).
I saw what they did at Compute Canada and it's really nice. Our goal is nevertheless different. We don't want to develop our own ansible and terraform scripts to deploy binderhub because we will not have time to maintain them. So the idea is to use community tools like kubespray and it works pretty well.
I can now write the blog post and we'll see if it's reproducible ;).

@gouarin I'm interested to see any guidance you have to see if I can get things to work with it...

@psychemedia done!
https://blog.jupyter.org/how-to-deploy-jupyterhub-with-kubernetes-on-openstack-f8f6120d4b1

Wahoo! Way to @gouarin and team, thanks for sharing your experiences :-)
I think that before closing this issue, we should add a link to this blog in the known binderhub deployments page!

@gouarin Great - thanks... will give it a go...

Closing as this is quite old now


JDASocket unable to reconnect

It looks like my music bot got disconnected from the web socket, so it attempted to reconnect. However, when it does reconnect it throws this IllegalStateException and it disconnects. It looks like this in the log:
[17:08:19] [Warning] [JDASocket]: Got disconnected from WebSocket (Internet?!)... Attempting to reconnect in 2s
[17:08:21] [Warning] [JDASocket]: Attempting to reconnect!
[17:08:22] [Info] [JDASocket]: Connected to WebSocket
[17:08:22] [Fatal] [JDASocket]: Encountered an exception:
[17:08:22] [Fatal] [JDASocket]: java.lang.IllegalStateException: Already attempting to start an AudioConnection with a VoiceChannel!
Currently Attempting Channel ID:<PHONE_NUMBER>26407681  |  New Attempt Channel ID:<PHONE_NUMBER>26407681
    at net.dv8tion.jda.managers.impl.AudioManagerImpl.openAudioConnection(AudioManagerImpl.java:71)
    at net.dv8tion.jda.requests.WebSocketClient.reconnectAudioConnections(WebSocketClient.java:535)
    at net.dv8tion.jda.requests.WebSocketClient.ready(WebSocketClient.java:133)
    at net.dv8tion.jda.requests.WebSocketClient.handleEvent(WebSocketClient.java:584)
    at net.dv8tion.jda.requests.WebSocketClient.onTextMessage(WebSocketClient.java:324)
    at com.neovisionaries.ws.client.ListenerManager.callOnTextMessage(ListenerManager.java:352)
    at com.neovisionaries.ws.client.ReadingThread.callOnTextMessage(ReadingThread.java:233)
    at com.neovisionaries.ws.client.ReadingThread.callOnTextMessage(ReadingThread.java:211)
    at com.neovisionaries.ws.client.ReadingThread.handleTextFrame(ReadingThread.java:910)
    at com.neovisionaries.ws.client.ReadingThread.handleFrame(ReadingThread.java:693)
    at com.neovisionaries.ws.client.ReadingThread.main(ReadingThread.java:102)
    at com.neovisionaries.ws.client.ReadingThread.run(ReadingThread.java:61)

[17:08:22] [Warning] [JDASocket]: Got disconnected from WebSocket (Internet?!)... Attempting to reconnect in 2s
[17:08:24] [Warning] [JDASocket]: Attempting to reconnect!
[17:08:25] [Info] [JDASocket]: Connected to WebSocket
[etc]

This cycle would then repeat until I terminated my bot, but it was unusable until then. This is possibly related to #110.

This as to do with the AudioWebsocket not closing properly / fast enough between the MainWS disconnect and subsequent reconnect process. When the MainWS disconnects it "saves" all known connected audio connections and tries to restore them when the MainWS reconnects to Discord.
Thus, if an audio connection doesn't actually die, or it isn't cleared in time, it looks like you already have an open connection.
When I recode the audio connecting system in 3.0 I'll be sure to fix this.

So my previous answer actually wasn't correct. This was caused by the AudioWebSocket closing before the MainWS. This meant that it attempted to reconnect immediately which involves sending data over the MainWS. However, the MainWS was probably also disconnected but it hadn't noticed yet. So the data sent to discord was never received.
This meant that JDA throught it had attempted to establish a connection to discord, and was expecting a response, but would never receive one. When the MainWS finally disconnected, it recorded that the audio connection had disconnected due to error (probably along with a ton of other audio connections). These connections are recorded and cached to be reestablished when the MainWS reconnected.
So, when the MainWS reconnected, it attempted to reestablish all audio connections, but the one in the stack trace had already been attempted, so the internals of JDA were out of sync with reality, thus you see the error shown.
Additionally, 2.x had a problem with easily killing the MainWS due to sending too many WS messages too quickly when reestablishing audio connections after a reconnect, especially when there were a ton of audio connections that needed to be reestablished.
Both problems will be addressed when audio finally releases to development. The last problem mentioned has already been addressed.

Reconnect killing Websocket due to too many messages; Fixed: 5f2bd4308c0c16d4827a4d1a9c59ef225fa8287e
Audio connections failing to reconnect, invalidating cache; Fixed: a97afac2c0bad4320998caad4f90d5465af62b89


High CPU utilization by AsyncScheduler thread

I am currently running

SpongeForge version: 1.12.2-2838-7.1.7-RC3947
Java version: 1.8.0_222/64-bit
Operating System: Linux
Plugins/Mods: only one test plugin that schedules an empty task for every 5 seconds.

Issue Description
https://github.com/SpongePowered/SpongeCommon/commit/6b29fb92a97a512cb0c2cc00be3fe0cf6617edfa
@dualspiral

My original comment on Discord was:

Yes, at a quick glance, I think I see why. Without looking at your scheduler test, I bet that you have a recurring async task. That recurring async task doesn't finish before the next one starts.
In RC3946, the new task will start without waiting for the old one. In RC3947, this was committed - https://github.com/SpongePowered/SpongeCommon/commit/6b29fb92a97a512cb0c2cc00be3fe0cf6617edfa. What's going on now is that in recalibrateMinimumTimeout, the timeout is always zero because it wants to execute the task as soon as the old one finishes, but it does this by continuously checking because there is no pause between checks.
This will only happen with plugins that have tasks that take longer than their set period.
I can't fix this right now, but can you open an issue on SpongeCommon and tag me in it?

However, that wouldn't sit right with this statement that the task is empty, and runs every 5 seconds - if an empty task takes 5 seconds to execute then it we have bigger problemsd.
It turns out there is a race condition here. The first part of it is this:
https://github.com/SpongePowered/SpongeCommon/blob/6b29fb92a97a512cb0c2cc00be3fe0cf6617edfa/src/main/java/org/spongepowered/common/scheduler/SchedulerBase.java#L174-L175
Once we start the task, we enter the RUNNING state. The key thing is what is going on in the startTask method, however:
https://github.com/SpongePowered/SpongeCommon/blob/6b29fb92a97a512cb0c2cc00be3fe0cf6617edfa/src/main/java/org/spongepowered/common/scheduler/SchedulerBase.java#L189-L190
The task gets set to EXECUTING before we run the task executor... but it's run within executeTaskRunnable as an anonymous method. This anonymous method, for the AsyncScheduler, is actually run within a thread pool - that is, on a different thread. In the ideal case here, task would to get set to the RUNNING state immediately after EXECUTING, which would be okay, but it would just mean that the previous issue the commit in question was meant to solve.
It is possible, if not probable, however, for the thread setup time to be relatively large, meaning that control is passed back to the calling method well before the supplied executor is ready to be executed. As a result this would mean that the task would get set to the RUNNING state, THEN the EXECUTING state. The task would then be stuck in EXECUTING for all eternity, even after the task finished to run. This has two major side effects when the task is a repeating one:

A repeating task will not run again
The scheduler, as written, will continuously try to check to see if it can call the task, knowing that it is due to do so, but not doing so because it is in the RUNNING phase.

As the EXECUTING phase is considered "active", the following can result in a zero minimum timeout:
https://github.com/SpongePowered/SpongeCommon/blob/6b29fb92a97a512cb0c2cc00be3fe0cf6617edfa/src/main/java/org/spongepowered/common/scheduler/AsyncScheduler.java#L90-L96
We then end up with a preTick that doesn't wait:
https://github.com/SpongePowered/SpongeCommon/blob/6b29fb92a97a512cb0c2cc00be3fe0cf6617edfa/src/main/java/org/spongepowered/common/scheduler/AsyncScheduler.java#L112
which then tries to process it, but returns and does nothing with it:
https://github.com/SpongePowered/SpongeCommon/blob/6b29fb92a97a512cb0c2cc00be3fe0cf6617edfa/src/main/java/org/spongepowered/common/scheduler/SchedulerBase.java#L153-L155
and then completes the loop, where the whole cycle of checking the minimum timeout, getting zero, and trying to execute again will continue to infinity.
I'll try to get around to fixing it tonight. It's a bit more complex than moving a check. I know what needs to be done, I just need a bit of time to fully test what's going on.

Fixed this in https://github.com/SpongePowered/SpongeCommon/commit/f7bde6a121d20b0f043b0d96ffd5edca711e103a - typo means I put the wrong issue in the commit!


Remove inapplicable #to_str method

As this Stack Overflow answer says, to_str should only be implemented for classes that actually represent a string – not classes that just have a string representation.

Awesome, thanks.  Haven't really written ruby since I wrote this so I'll take your word for it.

I should really repackage it as a new version of the gem now.  I wonder if anyone is really using it.

I’m not using the gem – I was simply curious to see other Ruby implementations of skip lists, after I had to write one for an interview question.

Nice! Do you think this one is good/fast?  I tried to focus on speed but I
think there may be quite a bit of premature optimization.  I honestly think
it is a great and under appreciated data structure.
On Sep 26, 2015 1:42 AM, "Rory O’Kane"<EMAIL_ADDRESS>wrote:

I’m not using the gem – I was simply curious to see other Ruby
implementations of skip lists, after I had to write one for an interview
question.
—
Reply to this email directly or view it on GitHub
https://github.com/light24bulbs/dynamic-skiplist/pull/2#issuecomment-143412246
.

It’s hard for me to tell. I implemented mine very differently. Your Node has two values key and value and an array of links on each level forward. My Node had two links next and below and one value value. So instead of using an array of links to represent links on each layer, I used a stack of Nodes whose below referred to each other, as if each box in this Wikipedia diagram had an arrow pointing down to the node below.
I think your array representation is probably faster to work with than my two links. But because your code had a different Node, I have trouble understanding your method walk(from, to, limit, level, output). The most similar method in my code is find_previous_or_equal_node(value, earlier_node_on_layer) that only searches on one layer, and is called for each layer by the recursive methods add and include?.
I do like that you have unit tests, unlike the other skiplist gem. I would trust this gem over that one.
I agree that skip lists are a cool data structure. I like the simplicity of randomness in algorithms to get average-case good time, as in lottery scheduling of OS processes.


Use workspace.findFiles to respect ignored files

This pull request aims to improve the performance of graph parsing when large folders are present (such as node_modules)
It does this by using findFiles which respects files excluded by either the global or workspace level files.exclude config option.
In a follow up PR, I'd be quite interested to propose automatically excluding files from the workspaces .gitignore, but thought that should be put to a discussion first!
Resolves, if files.exclude is set: https://github.com/tchayen/markdown-links/issues/33
Relates to: https://github.com/foambubble/foam/issues/130
Thank you for this extension. Love being able to visualise the links between files!

Thanks a lot! I wasn't aware of that option.
.gitignore is IMO ok too. There was separate issue about it #25 and I agree with the comments there.

@tchayen Ah great! Happy to work on that if you like? Might be able to drum something up today?

@tchayen Ah great! Happy to work on that if you like? Might be able to drum something up today?

I personally won't be able to work on this today but will be happy to help and/or merge a PR. Thanks a lot!

@tchayen Hey! Any update on this? Sorry to prod!
I might take a look at the Windows issue this week too

@tchayen Hey! Any update on this? Sorry to prod!
I might take a look at the Windows issue this week too

Hi, everyone.
Thank you for great plugin, but I've rechecked this branch on windows and links doesn't seem to work with examples folder as expected.

@vanadium23 Hey! If you check out the currently released version you'll see the examples folder doesn't work on windows their either. Issue #26 talks about it.
I want to take a look at this but have been busy this week, and it's probably outside the scope of this PR.
All this to say, to my knowledge, I've not introduced any new bugs. Graphs not linking with nested items on windows is already an issue.

@tchayen @vanadium23 Since I had time, and it was a simple fix, I've also resolved link resolution for nested folders on Windows
I've confirmed on a Macbook that nothing has broken for POSIX systems! Do please check this branch yourselves though for anything I've missed.
Hopefully resolves #26

@ingalless I've recheck. Everything works as expected.
Thank you, looking for release. <3

Sorry for taking so long to merge. I had a lot other problems to take care of and couldn't get back to it sooner. Looks good to me, merging the PR.
Huge thanks for all the help and involvement!


Feature Request: Past Pomodoro History

Similar to YAPA :  https://lukaszbanasiak.github.io/YAPA/  , it has a calendar like counter to track your previous sessions.

Thanks for great app!
Any updates on this feature request? I really need possibility to check daily, weekly, monthly etc. statistics


added table for ee version compatibility

So- is this output correct?

Based off of that- do we want to have php 7.1 included? I don't feel strongly.
Also v2 EE should work on php 7.0 per the changelog and it should work on 7.1 but I'm fairly positive there are a few bugs still.  I'd call it yellow.  See:
https://docs.expressionengine.com/v2/about/changelog.html#version-2-11-0

Added compatibility with PHP 7 and MySQL 5.7.

And you'll see some php 7.1 bug fixes in the v2 changelog as well.
For EE v3 see: https://docs.expressionengine.com/v3/about/changelog.html#version-3-5-13

Added PHP 7.2 compatibility.

EE4 has a few tweaks for 7.1 and 7.2 mentions.  Then 5.4 should work on php 8.0:
https://docs.expressionengine.com/v5/installation/changelog.html#version-540

Added support for PHP 8
Added support for MySQL 8


bring back previous view of /node/[nid]/rb/reviewed

honestly can't recall off the top of my head everything that was included but resembled the inbox view
not sure when this broke but must have been since the last prod deploy

Ill revert back to an older commit and see what it looked like (and figure out what changed since)

:cool: thanks @deadlybutter

hmm, problem reverting back b/c the latest work Diego did doesn't exist and it breaks things

Ill try fiddling around to see if i can hack it to work

I think if you cc all (or you might possibly have to rebuild) it should work without diego's stuff

so the only thing thats changed recently (8 days ago) thats related to this is the following commit https://github.com/DoSomething/phoenix/commit/d4e91e479a4ca31930070c544be72dffe8e92694#diff-67bc724f9b8588a3785047d82c4f1510R310
Im guessing in the switch to reportback item a variables usage changed and it broke the admin review form? ill keep digging

Yes, that change definitely could have broken this view. If you inspect the Reportback Files (I think thats what its named) view in the Drupal admin views UI.. you will probably see labels like "Broken handler" for where the Reportback Files were. cc @weerd


Add ion-locked and ion-person-stalker icons

 3d - PEMF - Implement EM account dashboard redesign

I have self-merged this in the interest of time. @gauthierm Can you retroactively review once you get a chance?


upgrade to dotnet core

This is what I got so far. All tests are passing, although I noticed some are failing sometimes (PostgreSqlAllPersistenceIdsSpec with error: Message: Failed: Timeout 00:00:03 while waiting for a message of type Akka.Streams.TestKit.TestSubscriber+OnNext`1[System.Object] ).
I haven't touched the build scripts because it isn't clear to me what has to be changed.

In the meantime i have also added support for SerializerWithStringManifest. It wasn't the case and using this plugin with Cluster Sharding was not possible.
Can i add these changes to this pull request or do i wait for this one to be finalized?

@JimmyHannon if you could go ahead and add the support for SerializerWithStringManifest to this PR that'd be fine.  I will assist with build script changes too

@JimmyHannon Please disregard my last comment re: SerializerWithStringManifest.  I'm going to merge this one now since the reviews are approved.  If you don't mind, can you add that as a separate PR?  That way I can work on the build scripts/v1.3.1 upgrade in parallel.  Thanks!

OK, thanks.
I wil submit a new PR.


EIA 861 using new datastore and generic excel extractor WIP

I was trying to make a PR for just my last commit, not everything on this branch. but alas here we are. this branch is a WIP, but you should be able to run an EIA 860 extractor:
raw_eia861 = pudl.extract.eia861.Extractor().extract(
    pc.working_years['eia861'],
    testing=True)

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8
- Added 27

Complexity increasing per file
==============================
- src/pudl/workspace/zenodo_download.py  6
- test/datastore_test.py  2

Complexity decreasing per file
==============================
+ src/pudl/workspace/datastore.py  -19
+ src/pudl/extract/eia861.py  -6

Clones added
============
- src/pudl/workspace/datastore.py  3
- src/pudl/workspace/zenodo_download.py  3

Clones removed
==============
+ test/datastore_test.py  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8
- Added 35

Complexity increasing per file
==============================
- test/datastore_test.py  2
- src/pudl/workspace/zenodo_download.py  6

Complexity decreasing per file
==============================
+ src/pudl/extract/eia861.py  -6
+ src/pudl/workspace/datastore.py  -19

Clones added
============
- src/pudl/workspace/zenodo_download.py  3
- src/pudl/workspace/datastore.py  3

Clones removed
==============
+ test/datastore_test.py  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8
- Added 40

Complexity increasing per file
==============================
- test/datastore_test.py  2
- src/pudl/workspace/zenodo_download.py  6

Complexity decreasing per file
==============================
+ src/pudl/extract/ferc1.py  -11
+ src/pudl/extract/eia861.py  -6
+ src/pudl/workspace/datastore.py  -19

Clones added
============
- src/pudl/workspace/datastore.py  3
- src/pudl/workspace/zenodo_download.py  3

Clones removed
==============
+ test/datastore_test.py  -1
+ test/conftest.py  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8
- Added 38

Complexity increasing per file
==============================
- test/datastore_test.py  2
- src/pudl/workspace/zenodo_download.py  6

Complexity decreasing per file
==============================
+ src/pudl/extract/eia861.py  -6
+ src/pudl/extract/ferc1.py  -11
+ src/pudl/workspace/datastore.py  -19

Clones added
============
- src/pudl/workspace/zenodo_download.py  3
- src/pudl/workspace/datastore.py  3

Clones removed
==============
+ test/datastore_test.py  -1
+ test/conftest.py  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8
- Added 38

Complexity increasing per file
==============================
- test/datastore_test.py  2
- src/pudl/workspace/zenodo_download.py  6

Complexity decreasing per file
==============================
+ src/pudl/workspace/datastore.py  -19
+ src/pudl/extract/eia861.py  -6
+ src/pudl/extract/ferc1.py  -10

Clones added
============
- src/pudl/workspace/datastore.py  3
- src/pudl/workspace/zenodo_download.py  3

Clones removed
==============
+ test/datastore_test.py  -1
+ test/conftest.py  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8
- Added 37

Complexity increasing per file
==============================
- src/pudl/workspace/zenodo_download.py  6
- test/datastore_test.py  2

Complexity decreasing per file
==============================
+ src/pudl/extract/ferc1.py  -10
+ src/pudl/extract/eia861.py  -6
+ src/pudl/workspace/datastore.py  -19

Clones added
============
- src/pudl/workspace/datastore.py  3
- src/pudl/workspace/zenodo_download.py  3

Clones removed
==============
+ test/conftest.py  -1
+ test/datastore_test.py  -1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8
- Added 32

Complexity increasing per file
==============================
- test/datastore_test.py  2

Complexity decreasing per file
==============================
+ src/pudl/extract/eia861.py  -6
+ src/pudl/extract/ferc1.py  -10
+ src/pudl/workspace/datastore.py  -19

Clones removed
==============
+ test/conftest.py  -1
+ test/datastore_test.py  -1

See the complete overview on Codacy


#1625: Update root README.md and SAMPLES.md

Fix #1625

Update default user information - Web Chat will now generate a random id.
Add rootHeight and rootWidth styling examples in SAMPLES.md

new screen caps:

Merged this in since Travis build said it passed but GH didn't update


Export model with non-default input size

Hi all, hope you can help with this.
I successfully trained the network and deployed it to a Jetson Xavier. Here it succesfull runs at the default resolution (1280x1280). I would like to have it run at 720x720 however.
This is where my problem occurs: when I try to export my .pth to a .onnx file with a non-default resolution, I get the following error.
Command : retinanet export model.pth model.onnx --size 720
Output:

Loading model from model.pth...
model: RetinaNet
backbone: ResNet50FPN
classes: 1, anchors: 9
Exporting to ONNX...
Traceback (most recent call last):
File "/opt/conda/bin/retinanet", line 11, in
load_entry_point('retinanet', 'console_scripts', 'retinanet')()
File "/workspace/retinanet/retinanet/main.py", line 181, in main
worker(0, args, 1, model, state)
File "/workspace/retinanet/retinanet/main.py", line 164, in worker
exported = model.export(input_size, args.batch, precision, calibration_files, args.calibration_table, args.verbose, onnx_only=onnx_only, opset=args.opset)
File "/workspace/retinanet/retinanet/model.py", line 226, in export
torch.onnx.export(self.cuda(), zero_input, onnx_bytes, *extra_args)
File "/opt/conda/lib/python3.6/site-packages/torch/onnx/init.py", line 27, in export
return utils.export(*args, **kwargs)
File "/opt/conda/lib/python3.6/site-packages/torch/onnx/utils.py", line 111, in export
_retain_param_name=_retain_param_name)
File "/opt/conda/lib/python3.6/site-packages/torch/onnx/utils.py", line 313, in _export
_retain_param_name)
File "/opt/conda/lib/python3.6/site-packages/torch/onnx/utils.py", line 237, in _model_to_graph
graph, torch_out = _trace_and_get_graph_from_model(model, args, training)
File "/opt/conda/lib/python3.6/site-packages/torch/onnx/utils.py", line 204, in _trace_and_get_graph_from_model
trace, torch_out = torch.jit.get_trace_graph(model, args, _force_outplace=True)
File "/opt/conda/lib/python3.6/site-packages/torch/jit/init.py", line 219, in get_trace_graph
return LegacyTracedModule(f, _force_outplace, return_inputs)(*args, **kwargs)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 491, in call
result = self.forward(*input, **kwargs)
File "/opt/conda/lib/python3.6/site-packages/torch/jit/init.py", line 276, in forward
out = self.inner(*trace_inputs)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in call
result = self._slow_forward(*input, **kwargs)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 479, in _slow_forward
result = self.forward(*input, **kwargs)
File "/workspace/retinanet/retinanet/model.py", line 104, in forward
features.extend(backbone(x))
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 489, in call
result = self._slow_forward(*input, **kwargs)
File "/opt/conda/lib/python3.6/site-packages/torch/nn/modules/module.py", line 479, in _slow_forward
result = self.forward(*input, **kwargs)
File "/workspace/retinanet/retinanet/backbones/fpn.py", line 44, in forward
p4 = F.interpolate(p5, scale_factor=2) + p4
RuntimeError: The size of tensor a (46) must match the size of tensor b (45) at non-singleton dimension 3

Does this mean I should define my input size correctly during training, or ?
Thanks!

Export dimensions have to be a multiple of model.stride. For standard ResNet FPN it should be a multiple of 128.

That did the trick, thanks!


Poor performance compared with qemu-img convert

Converting compressed qcow2 is about 10 times slower compared with qemu-img convert.
qemu-img convert use many technics to speed up the operation:

Using thread pool for reading and decompressing clusters
Use block status to avoid reading unallocated areas
Use fast zlib library in C for decompression
Caching L2 tables to avoid disk access for checking if a cluster is allocated, zero or getting the cluster host offset
Zero detection using 4k granularity (defualt)
Unordered writes - having multiple in-flight reads and writes.

We can learn from qemu-img and apply some of the technics in this library.
How thread pool affects performance
We can use -m N to control the numbner of coroutines, practically controlling the number of threads doing I/O and decompression in parallel.
Testing with limactl create, since we don't have useful tool for benchmarking.
Testing show that single threaded qemu-img convert is 4 times faster, and with 8 threads it is 9 times faster.
Limactl create
% time limactl create --plain --tty=false
...
INFO[0000] Using cache "/Users/nsoffer/Library/Caches/lima/download/by-url-sha256/346ee1ff9e381b78ba08e2a29445960b5cd31c51f896fc346b82e26e345a5b9a/data"
INFO[0000] Converting "/Users/nsoffer/.lima/default/basedisk" (qcow2) to a raw disk "/Users/nsoffer/.lima/default/diffdisk"
3.50 GiB / 3.50 GiB [-------------------------------------] 100.00% 198.96 MiB/s
...
limactl create --plain --tty=false  19.88s user 1.47s system 116% cpu 18.294 total

qemu-img convert with different number of coroutines
% SRC=/Users/nsoffer/Library/Caches/lima/download/by-url-sha256/346ee1ff9e381b78ba08e2a29445960b5cd31c51f896fc346b82e26e345a5b9a/data
% for i in 1 2 4 8; do echo "=== $i coroutines"; time qemu-img convert -O raw -m $i $SRC tmp.img; done
=== 1 coroutines
qemu-img convert -O raw -m $i $SRC tmp.img  2.27s user 1.63s system 85% cpu 4.567 total
=== 2 coroutines
qemu-img convert -O raw -m $i $SRC tmp.img  2.33s user 1.81s system 154% cpu 2.687 total
=== 4 coroutines
qemu-img convert -O raw -m $i $SRC tmp.img  2.37s user 2.09s system 213% cpu 2.097 total
=== 8 coroutines
qemu-img convert -O raw -m $i $SRC tmp.img  2.38s user 2.10s system 223% cpu 2.004 total

How unordered writes affect performance
With ordered writes (the default), when a read (and decompress) is finished, the coroutine waits until it can write the data to the target image in order. This decreases performance and cpu usage.
With unordered writes, when a read (and decomporess) is finished, the coroutine writes the data to the target without waiting for previous reads. This increase fragmentation of the file, but greatly improve performance in some cases (e.g. writing to shared block storage can be 6 times faster).
Using unordered writes is more effective with direct I/O (1.5 times faster). With buffered I/O it is only 1.14 times faster.
This is not great improvement for our use case, but we can consider this later.

With uncompressed images we are fast as qemu-img, but it can be 2 times faster using direct I/O and unordered writes.
% time limactl create --plain --tty=false
INFO[0000] Using cache "/Users/nsoffer/Library/Caches/lima/download/by-url-sha256/346ee1ff9e381b78ba08e2a29445960b5cd31c51f896fc346b82e26e345a5b9a/data"
INFO[0000] Converting "/Users/nsoffer/.lima/default/basedisk" (qcow2) to a raw disk "/Users/nsoffer/.lima/default/diffdisk"
3.50 GiB / 3.50 GiB [-------------------------------------] 100.00% 296.81 MiB/s
...
limactl create --plain --tty=false  12.11s user 0.70s system 103% cpu 12.355 total

Comparing uncompressed images - for reference:
% cat test.yaml
images:
- location: /tmp/test.qcow2
  arch: "aarch64"
vmType: vz
plain: true

% time limactl create --tty=false test.yaml
...
INFO[0000] Downloaded the image from "/tmp/test.qcow2"
INFO[0000] Converting "/Users/nsoffer/.lima/test/basedisk" (qcow2) to a raw disk "/Users/nsoffer/.lima/test/diffdisk"
3.50 GiB / 3.50 GiB [---------------------------------------] 100.00% 3.87 GiB/s
...
limactl create --tty=false test.yaml  0.70s user 0.53s system 82% cpu 1.494 total

Converting same image with qemu-img with different number of threads:
% for i in 1 2 4 8; do echo "=== $i coroutines"; time qemu-img convert -O raw -m $i /tmp/test.qcow2 tmp.img; done
=== 1 coroutines
qemu-img convert -O raw -m $i /tmp/test.qcow2 tmp.img  0.03s user 0.74s system 83% cpu 0.927 total
=== 2 coroutines
qemu-img convert -O raw -m $i /tmp/test.qcow2 tmp.img  0.03s user 0.76s system 84% cpu 0.933 total
=== 4 coroutines
qemu-img convert -O raw -m $i /tmp/test.qcow2 tmp.img  0.04s user 0.77s system 88% cpu 0.916 total
=== 8 coroutines
qemu-img convert -O raw -m $i /tmp/test.qcow2 tmp.img  0.05s user 0.79s system 88% cpu 0.953 total

Converting same image with qemu-img convert using direct I/O and unordered writes:
% for i in 1 2 4 8; do echo "=== $i coroutines"; time qemu-img convert -O raw -m $i -W -t none /tmp/test.qcow2 tmp.img; done
=== 1 coroutines
qemu-img convert -O raw -m $i -W -t none /tmp/test.qcow2 tmp.img  0.05s user 0.57s system 58% cpu 1.056 total
=== 2 coroutines
qemu-img convert -O raw -m $i -W -t none /tmp/test.qcow2 tmp.img  0.05s user 0.58s system 107% cpu 0.591 total
=== 4 coroutines
qemu-img convert -O raw -m $i -W -t none /tmp/test.qcow2 tmp.img  0.07s user 0.71s system 175% cpu 0.440 total
=== 8 coroutines
qemu-img convert -O raw -m $i -W -t none /tmp/test.qcow2 tmp.img  0.08s user 0.91s system 226% cpu 0.435 totalful

Faster decompression
Looks like the builtin flate library is slow. We can find a better library or use the C library with cgo.
#33 added a test for fully allocated compressed image. This test shows that decompression is extremely slow.
Faster zero reads
With the inefficient io.Reader interface, we have to fill a buffer with zeros when reading zero cluster. This should be many times faster compared with reading data from storage,  close to memory bandwidth (e.g. 50 GB/s). However the new test for completely image (#33) shows that this is almost 3 times slower compared with reading fully allocated image.
Improving this will not save lot of time, but can very simple change, like copying a preallocated zero buffer, or using memset() via cgo.
Using internal thread pool for I/O and decompression
We can split the read request (e.g. 1 MiB) to 16 sub requests (for default cluster size) process in a goroutine pool.
The request can complete when:

all sub request completed
at least one sub request failed

This keeps the io.ReaderAt interface, which makes the library easy to use, but it will never perform well like an async interface.
This also add a lot of complexity to the library.
Providing block status interface
Using io.ReaderAt (and io.Reader) will never be efficient for sparse images. The efficient way to copy sparse images is:

Get the next run of clusters with same status (allocated, zero, unallocated, compressed)
Process clusters:

Zero clusters (clusters allocated but marked as zero): skip
Unallocated clusters: skip
Uncompressed clusters: read all clusters (in one read call if possible)
Compressed clusters: read and decompress each cluster

Write data to target

So we need an interface like:
type Qcow2Reader intreface {
    BlockStatus(offset int64) (*Status, error)
    ReadAt(b []byte, offset int64) (int64, error)
}

With this the user of the library can use find runs of clusters of the same type, and process them in a thread pool, reading and decompressing in parallel.
Implementing BlockStatus with backing files is not trivial, but much less work comparing to implementing internal thread pool.
Related issues

https://github.com/lima-vm/lima/issues/2579

Tasks

[x] Cache L2 tables (#31)
[x] Faster zero reads (#34)
[x] Faster decompression (#36)
[ ] BlockStatus interface - nice to have, we can do add this later.

Probably we can keep this open for the BlockStatus interface


VS code Server for WSL closed unexpectedly. check WSL terminal for more details.

[2020-06-27 17:32:12.874] Resolving wsl+Ubuntu, resolveAttempt: 1
[2020-06-27 17:32:12.916] Starting VS Code Server inside WSL (Ubuntu)
[2020-06-27 17:32:12.916] Extension version: 0.44.4, Windows build: 19041. Multi distro support: available. WSL path support: enabled
[2020-06-27 17:32:13.055] Probing if server is already installed: C:\WINDOWS\System32\wsl.exe -d Ubuntu -e sh -c "[ -d ~/.vscode-server/bin/cd9ea6488829f560dc949a8b2fb789f3cdc05f5d ] && printf found || ([ -f /etc/alpine-release ] && printf alpine-; uname -m)"
[2020-06-27 17:32:13.161] Probing result: found
[2020-06-27 17:32:13.161] Server install found in WSL
[2020-06-27 17:32:13.161] Launching C:\WINDOWS\System32\wsl.exe -d Ubuntu sh -c '"$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" cd9ea6488829f560dc949a8b2fb789f3cdc05f5d stable .vscode-server 0  ' in c:\Users\tank2.vscode\extensions\ms-vscode-remote.remote-wsl-0.44.4}
[2020-06-27 17:32:13.265] sh: 1: /mnt/c/Users/tank2/.vscode/extensions/ms-vscode-remote.remote-wsl-0.44.4/scripts/wslServer.sh: Input/output error
[2020-06-27 17:32:13.265] VS Code Server for WSL closed unexpectedly.
[2020-06-27 17:32:13.265] For help with startup problems, go to
[2020-06-27 17:32:13.265] https://code.visualstudio.com/docs/remote/troubleshooting#_wsl-tips
any idea to solve this problem?

Bump

@dohkim Did you sloved? what' wrong that is?

How you solved this ?

Dear all,
resolved issue by command below...i made with bat file.,,
wsl.exe --shutdown
On Fri, Aug 7, 2020 at 2:03 AM putrafajarh<EMAIL_ADDRESS>wrote:

How you solved this ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/101191#issuecomment-670343165,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABU7AXDCHNL2SVFYH2PFSW3R7OKLTANCNFSM4OKD5SQQ
.


Add authorization policy to Service Fabric

Fixes https://github.com/microsoft/reverse-proxy/issues/1465

This SF code is no longer under development and we expect to remove it soon now that https://github.com/microsoft/service-fabric-yarp is available.


HADOOP-15887: Add an option to avoid writing data locally in Distcp

In https://issues.apache.org/jira/browse/HDFS-3702 we add a flag in DFSClient to avoid replicating to the local datanode.  We can make use of this flag in Distcp.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
30m 21s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
18m  9s
trunk passed

+1 :green_heart:
compile
0m 30s
trunk passed

+1 :green_heart:
checkstyle
0m 25s
trunk passed

+1 :green_heart:
mvnsite
0m 31s
trunk passed

+1 :green_heart:
shadedclient
13m 33s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 24s
trunk passed

+0 :ok:
spotbugs
0m 43s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 41s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 26s
the patch passed

+1 :green_heart:
compile
0m 21s
the patch passed

+1 :green_heart:
javac
0m 21s
the patch passed

-0 :warning:
checkstyle
0m 19s
hadoop-tools/hadoop-distcp: The patch generated 1 new + 113 unchanged - 2 fixed = 114 total (was 115)

+1 :green_heart:
mvnsite
0m 24s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
13m  8s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 20s
the patch passed

+1 :green_heart:
findbugs
0m 45s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
12m 51s
hadoop-distcp in the patch passed.

+1 :green_heart:
asflicense
0m 30s
The patch does not generate ASF License warnings.

95m 21s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1794/1/artifact/out/Dockerfile

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

JIRA Issue
HADOOP-15887

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 7b19cd995ff9 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 4a76ab7

Default Java
1.8.0_232

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1794/1/artifact/out/diff-checkstyle-hadoop-tools_hadoop-distcp.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1794/1/testReport/

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

modules
C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1794/1/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m 10s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
24m 44s
trunk passed

+1 :green_heart:
compile
0m 33s
trunk passed

+1 :green_heart:
checkstyle
0m 28s
trunk passed

+1 :green_heart:
mvnsite
0m 34s
trunk passed

+1 :green_heart:
shadedclient
17m  7s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 24s
trunk passed

+0 :ok:
spotbugs
0m 51s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 49s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 30s
the patch passed

+1 :green_heart:
compile
0m 22s
the patch passed

+1 :green_heart:
javac
0m 22s
the patch passed

-0 :warning:
checkstyle
0m 18s
hadoop-tools/hadoop-distcp: The patch generated 1 new + 113 unchanged - 2 fixed = 114 total (was 115)

+1 :green_heart:
mvnsite
0m 24s
the patch passed

+1 :green_heart:
whitespace
0m  1s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
16m 28s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 22s
the patch passed

+1 :green_heart:
findbugs
0m 51s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
13m 34s
hadoop-distcp in the patch passed.

+1 :green_heart:
asflicense
0m 32s
The patch does not generate ASF License warnings.

81m 59s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1794/2/artifact/out/Dockerfile

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

JIRA Issue
HADOOP-15887

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 4a750e828a67 4.15.0-60-generic #67-Ubuntu SMP Thu Aug 22 16:55:30 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / a43c177

Default Java
1.8.0_232

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1794/2/artifact/out/diff-checkstyle-hadoop-tools_hadoop-distcp.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1794/2/testReport/

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

modules
C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1794/2/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

thanks

could those assertTrue calls have a string saying what failed? I hate having to debug a test failure without those (as I am doing right now...)

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
25m  9s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 4 new or modified test files.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
19m 21s
trunk passed

+1 :green_heart:
compile
0m 28s
trunk passed

+1 :green_heart:
checkstyle
0m 25s
trunk passed

+1 :green_heart:
mvnsite
0m 29s
trunk passed

+1 :green_heart:
shadedclient
12m 59s
branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 26s
trunk passed

+0 :ok:
spotbugs
0m 43s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
0m 42s
trunk passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 27s
the patch passed

+1 :green_heart:
compile
0m 21s
the patch passed

+1 :green_heart:
javac
0m 21s
the patch passed

-0 :warning:
checkstyle
0m 17s
hadoop-tools/hadoop-distcp: The patch generated 1 new + 112 unchanged - 2 fixed = 113 total (was 114)

+1 :green_heart:
mvnsite
0m 23s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedclient
13m 52s
patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 22s
the patch passed

+1 :green_heart:
findbugs
0m 45s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
13m 13s
hadoop-distcp in the patch passed.

+1 :green_heart:
asflicense
0m 31s
The patch does not generate ASF License warnings.

91m 42s

Subsystem
Report/Notes

Docker
Client=19.03.5 Server=19.03.5 base: https://builds.apache.org/job/hadoop-multibranch/job/PR-1794/3/artifact/out/Dockerfile

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

JIRA Issue
HADOOP-15887

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient findbugs checkstyle

uname
Linux 9b3a5a022781 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
personality/hadoop.sh

git revision
trunk / 1c51f36

Default Java
1.8.0_232

checkstyle
https://builds.apache.org/job/hadoop-multibranch/job/PR-1794/3/artifact/out/diff-checkstyle-hadoop-tools_hadoop-distcp.txt

Test Results
https://builds.apache.org/job/hadoop-multibranch/job/PR-1794/3/testReport/

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

modules
C: hadoop-tools/hadoop-distcp U: hadoop-tools/hadoop-distcp

Console output
https://builds.apache.org/job/hadoop-multibranch/job/PR-1794/3/console

versions
git=2.7.4 maven=3.3.9 findbugs=3.1.0-RC1

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.


fix: upgrade to version 3.1.99

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign jstrachan
You can assign the PR to them by writing /assign @jstrachan in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

gsm
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

gsm
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

gsm
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test gsm

tls
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

gsm
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test gsm

tls
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test tls

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/retest

/retest

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

gsm
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test gsm

tls
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test tls

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

gsm
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test gsm

tls
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test tls

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test gsm

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

gsm
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test gsm

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

gsm
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

gsm
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test gsm

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

/test kube

/test kube

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

gsm
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test gsm

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.

@jenkins-x-bot-test: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

vault
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test vault

gsm
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test gsm

kube
31857d7c9a9497968f9e3773a4098739de3c757a
link
/test kube

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. I understand the commands that are listed here.


xsel is an unknown command to fish, therefore pbcopy broke in my Mac :(

I tried to run a command and pipe the output to pbcopy but it's not working. :(
> git changes --author="Marcos Hernández" | pbcopy
fish: Unknown command 'xsel'
in function 'pbcopy'
	called on standard input

> omf --version
Oh My Fish! 1.0.0

> fish -v
fish, version 2.2.0

I have the same error with pbcopy.

i have the same problem with fish version 2.2.0

Your Mac already has pbcopy and pbpaste. This plugin is so Linux can have it too :)

I know. The thing is I cannot use them in Fish :( I think something in OMF is replacing it


Mongo driver should reconnect when server forks

@scottmessinger Should this be in config/puma.rb instead of puma.rb?
https://puma.io/puma/#clustered-mode gives this example:
# config/puma.rb
on_worker_boot do
  # configuration here
end

If it was setup more typically, yes. But, same file -- just loaded from a
different place.
On Wed, Nov 6, 2024 at 4:06 PM mweidner037 @.***> wrote:

@scottmessinger https://github.com/scottmessinger Should this be in
config/puma.rb instead of puma.rb?
https://puma.io/puma/#clustered-mode gives this example:
config/puma.rbon_worker_boot do
configuration hereend
—
Reply to this email directly, view it on GitHub
https://github.com/commonstandardsproject/api/pull/47#issuecomment-2460780332,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAYOGOISCJBCBSRBVMCQULZ7KAGHAVCNFSM6AAAAABRJUV75KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRQG44DAMZTGI
.
You are receiving this because you were mentioned.Message ID:
@.***>


feat(resource): adding resource for eventbridge pipes

@ekristen hi! added support for eventbridge pipes, but I didn't format my title correctly on the first try, and I think the commit-link check is not picking up new changes? lmk if i can fix it :)

Ah great, thanks. Included your change :)

@MSchouwPablo I did a force update on your branch to fix the commits so commit-lint would pass, however I should have asked before I did. If you'd like to force push your own branch so you retain full author on your commits, please do, otherwise let me know and I'll merge. I can provide rebase instructions should you need them.
Either way I'm good. If you are ok with it as is, let me know and I'll just merge.

:tada: This PR is included in version 3.18.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: add delete_by_id to AbstractRepository

I'm missing this command. It's needed for crud applications where I'm getting the ID to delete.

@jefersondaniel can I ping you? :)


Concurrent disk I/O

Commands that perform a lot of disk I/O (cp, mv, rm, etc.) are likely to complete much faster, especially when operating on SSDs[^1] but potentially also on slower disks[^2], if they issue concurrent I/O requests (ideally asynchronously and in bulk[^3], but synchronously via a thread pool could also work).
Examples of cases where this could be very beneficial include:

cp -r <source> <dest> where <source> contains large number of files/subdirectories
cp <sources> <dest> where <sources> is a large number of files
rm -r <source> where <source> contains large number of files/subdirectories
rm <sources> where <sources> is a large number of files
mv <sources> <dest> where <sources> is a large number of files
ln <sources> <dest> where <sources> is a large number of files
ls <path> and ls -r <path> where <path> contains large number of files/subdirectories
du <path> where <path> contains large number of files/subdirectories

(and so on, the list above is not exhaustive: examples include stat, readlink, touch, chown, chgrp, chmod, etc.)
Whether this behavior should be opt-out/default-off or opt-in/default-on, I lean towards opt-out but I must admit I am not sure. With ever-increasing core counts and ever-higher capacity disks, I would argue there is a pretty strong case for the behavior to be opt-out rather than opt-in. At the same time, there may be concerns about these tools suddenly generating large I/O spikes, in which case it should be opt-in. In all cases,  the proposed behavior should never affect the correctness of the command, or its semantics (e.g. ordering of results, behavior on error, etc.).
Currently, the closest that can be achieved with standard tools is running processes in parallel by using something like xargs -P<n>, but this is somewhat easy to get wrong (e.g. forgetting to use -0, dynamically choosing between -I{} and normal mode based on how many files we need to operate on and how long their names are, etc) and it does not, in general, maintain the standard semantics of the tools (e.g. ordering needs to be done separately, handling errors is left to the user, etc.)

Update: in this section I will collect any available evidence, concerning performance, for or against this proposal:
For

My quick benchmarks using find | xargs -P showing 50-100% improvements in wall time
Fast Unix Commands (fuc) benchmarks showing up to 250% improvements in wall time
(please ping me so that I can add any further relevant evidence)

Against

(nothing yet, please ping me so that I can add any relevant evidence)

[^1]: as they tend to deliver higher throughput when operating with high queue depths
[^2]: as the OS can potentially coalesce a greater number of logical writes into a smaller number of disk write operations
[^3]: especially if via io_uring or similar mechanisms that can guarantee that in practice file operations never block, and that support batch submission

Interesting ideas! This should be something that Rust excels at over C too, with more thread safety and convenience. I have two reservations about this.

I think this should not complicate or bloat the code too much.
Part of compatibility with GNU is doing operations in the same order. For instance, if you do 2 operations in order and you exit if the first one fails, the second operation never gets executed. If you make those two operations concurrent, they will both have executed. In cases where this is an issue, we might need some flag or something that specifies that the order is random.

@thecotne tried with findutils: https://github.com/uutils/findutils/pull/142
and it didn't provide much ROI

@sylvestre I can acknowledge it depends on the OS, the filesystem in use, the hardware, the implementation, the operation being performed and so on, so obviously ROI may vary... but definitely I have seen it improve performance many times in the past.
Case in point, I just ran this very synthetic benchmark and even my utterly unrefined bash "implementation" on my laptop does improve throughput by 1.5x~2x:

bash-3.2$ N=1000000
bash-3.2$ P=100

bash-3.2$ time (seq 1 $N | xargs touch)
real	2m17.307s
user	0m2.254s
sys	1m31.966s
bash-3.2$ ls -1 | wc -l
 1000000

bash-3.2$ time (find . -type f | xargs rm)
real	4m28.594s
user	0m2.096s
sys	2m3.315s
bash-3.2$ ls -1 | wc -l
       0

bash-3.2$ time (seq 1 $N | xargs -P$P touch)
real	2m2.976s
user	0m4.890s
sys	9m55.269s
bash-3.2$ ls -1 | wc -l
 1000000

bash-3.2$ time (find . -type f | xargs -P$P rm)
real	3m9.421s
user	0m3.746s
sys	5m55.275s
bash-3.2$ ls -1 | wc -l
       0

bash-3.2$ N=100000
bash-3.2$ P=100

bash-3.2$ time (seq 1 $N | xargs touch)
real	0m9.580s
user	0m0.200s
sys	0m8.054s
bash-3.2$ ls -1 | wc -l
  100000

bash-3.2$ time (find . -type f | xargs rm)
real	0m18.979s
user	0m0.192s
sys	0m9.386s
bash-3.2$ ls -1 | wc -l
       0

bash-3.2$ time (seq 1 $N | xargs -P$P touch)
real	0m6.558s
user	0m0.340s
sys	0m31.672s
bash-3.2$ ls -1 | wc -l
  100000

bash-3.2$ time (find . -type f | xargs -P$P rm)
real	0m15.399s
user	0m0.274s
sys	0m12.768s
bash-3.2$ ls -1 | wc -l
       0

bash-3.2$ N=10000
bash-3.2$ P=100

bash-3.2$ time (seq 1 $N | xargs -I{} touch {})
real	0m31.932s
user	0m4.369s
sys	0m14.138s
bash-3.2$ ls -1 | wc -l
   10000

bash-3.2$ time (find . -type f | xargs -I{} rm {})
real	0m37.942s
user	0m5.437s
sys	0m16.991s
bash-3.2$ ls -1 | wc -l
       0

bash-3.2$ time (seq 1 $N | xargs -P$P -I{} touch {})
real	0m13.282s
user	0m4.663s
sys	0m21.291s
bash-3.2$ ls -1 | wc -l
   10000

bash-3.2$ time (find . -type f | xargs -P$P -I{} rm {})
real	0m14.835s
user	0m6.580s
sys	0m28.038s
bash-3.2$ ls -1 | wc -l
       0

I don't have access to it anymore, so I can't run experiments, but in the past being able to run large deletes concurrently cut down rm -r operations on a gluster volume from many hours to few tens of minutes.

The latest benchmark was run on the hardware described above, and can be trivially replicated on any hardware you happen to have available. Doing so should likely result in some speedup, but its magnitude may differ according to all factors listed in my previous message.
The old one (deletion of many millions of files) was IIRC on a 15 nodes glusterfs cluster running on top of a large VMware farm (hundreds of servers) attached to a large SAN. The exact hardware details are lost to time (this was 10+ years ago) but, I would argue, are ultimately irrelevant. My point wasn't that in that specific case it was beneficial, but rather that I've seen it reduce wall-time in multiple scenarios, over multiple years, running from large networked file systems, to Linux servers, to modern laptops (as evidenced by the latest benchmark).
I agree though there may be cases in which doing I/O concurrently will not provide much benefit. Crucially though, this is at least on my part just a hunch without proof (contrary to the opposite case), while also being the bulk of the argument why this functionality ought to be at least opt-in or opt-out. Just FTR being a hunch without proof is not for lack of trying: I tried running that newest benchmark on a couple of laptops I have (in addition to the Mac above, a Dell 9360 with W11/WSL2) and a throwaway GCP VM with a persistent SSD volume: in all cases wall time improved. At this point I would be extremely curious about any concrete counterexample where wall time becomes worse (apart from that findutils experiment, that looks at least to my eye somewhat flawed as outlined in my previous message) to drive the conversation forward.

I started collecting/summarizing the available experimental evidence, either in favor or against this proposal, in the first post of this issue. If additional evidence comes up please ping me and I'll add it as well.

Yeah, I would be happy to use more parallelism in this project :)


Add Suspend to MQTT

Describe the solution you'd like
I think being able to Suspend/Standby via MQTT would be great.
As a side note, I think it should be configurable if you want to be able to unlock a session via mqtt.

Hey @chripede thanks for the suggestion. I've just added suspend and hibernate commands via MQTT to the agent in version 7.2.0. Check it out!
Also note, you can create your own commands as needed (as long as what you want to do is something that can be triggered through D-Bus). However, I am still keen to add commands directly where they would be widely useful or common, so keep the suggestions coming (clicky here for a template for suggestions).

Oh no @chripede, that's not good. Okay so one thing to try, make sure the agent is registered and you've enabled MQTT support in it. Then:

Stop the agent.
Run go-hass-agent reset. This will wipe the agent config but also wipe any agent config in MQTT. It's crucial you've enable MQTT in the agent before doing this, otherwise it won't remove any configuration from MQTT.
Run the agent again and re-register.
Enable MQTT. Stop the agent.
Restart the agent.

If that doesn't work, can you run the agent with trace logging enabled with go-hass-agent --trace, let it run for a minute, then stop and attach the log located at ~/.local/state/go-hass-agent.log?
Side note: It's a bit clunky I know to enable MQTT with the stop/start. I need to work out a good way to do this dynamically...

That does indeed fix it, but only until I restart Mosquitto and HA. Then the problem returns.
Maybe the agent should register mqtt on every start?

Hey @chripede, that's interesting. I restart my development environment running Home Assistant and Mosquitto all the time, and the controls stay. This is done by sending the configuration messages to the broker with a retained status requested. A broker should hold on to those messages across restarts and each time Home Assistant connects to the broker, the broker sends those retained messages to it.
I wonder if your Mosquitto instance is configured without any persistence between restarts? In that case, maybe it is ignoring the retained request or only storing it until next restart? Currently, the agent requires persistence enabled on the broker.

Hey. Yes, my mqtt is not set up with persistence - I'd prefer not to because some of my topics receives a lot of messages that needs no persistence.
Can I suggest that this agent registers mqtt on startup and also listens on homeassistant/status to re-register every time it changes from offline to online?

Hey @chripede of course you can make a suggestion and yes I agree it will be better to have the agent work without needing persistence (which would also work with persistence anyway).
I will look to implement this in the next release. I'm going on a holiday shortly, so likely I won't get to this until sometime in April. But look out for the next release sometime that month in which I'll target this change!

Hey @chripede v7.3.0 now works without needing persistence on the MQTT broker. Please do try it out when you get a chance and report back!

I'm going to close this issue as the agent no longer requires persistence on the MQTT server and the suspend action is available.
If there is still something not working regarding the above, please re-open and we can continue to investigate.


PR: Handle case when kernel fault file doesn't exist and show error with info explaining that no connection was possible (IPython Console)

Description of Changes

Seems like passing a .json file that doesn't correspond to a kernel connection file (like for example a .json that corresponds to a notebook server instance connection file) can cause the kernel fault file to not be initialized causing and error when trying to compute a message to show to the user. Also, add an error message to prevent keep showing the Connecting to kernel over the console infowidget when no connection was possible.
A preview:

Issue(s) Resolved

Fixes #22448
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct: dalthviz

A couple of questions for @dalthviz:

Connecting to external kernels is working as expected, right?
What if instead of your approach, we parse the json file in the dialog, detect if it's valid and if not show a warning inside the dialog? I think that would make things simpler, but what do you think?

Connecting to external kernels is working as expected, right?

From what I tested it seems like yes :+1:

What if instead of your approach, we parse the json file in the dialog, detect if it's valid and if not show a warning inside the dialog? I think that would make things simpler for users, but what do you think?

Make sense but I would say that involves adding new logic and sounds more like an enhancement than a bug fix alone. Following your last comment, should an issue be created to track that enhancement idea (validation logic + feedback icon when selecting a kernel connection file)?

Make sense but I would say that involves adding new logic and sounds more like an enhancement than a bug fix alone. Following your last comment, should an issue be created to track that enhancement idea (validation logic + feedback icon when selecting a kernel connection file)?

Yeah, I think that's a good idea. Please create one so that we don't forget to address it later.

@meeseeksdev please backport to 6.x


108 issue solved

#108 solved! I've added the solution for Trapping Rain Water in java ,kindly check the PR and let me know if any changes are required !

kindly give the project a star


[LUA] How do I get custom arrow type (left,down,up,right) and user color?

Describe your problem here.
I want to make a custom note type that looks like the default one, but changes colors on beat, then goes back to the original color. I want the color to change depending on the note direction (left, down, up, right). Also, I need the user's color choices and textures from the note customizer so I can make them look like it's a default note.
Here's my attempt at getting the note direction (left, down, up or right)
function onCreate()
	--Iterate over all notes
	for i = 0, getProperty('unspawnNotes.length')-1 do
		--Check if the note is an Instakill Note
		if getPropertyFromGroup('unspawnNotes', i, 'noteType') == 'disguised_instakill' then
			if getPropertyFromGroup('unspawnNotes', i, 'noteData') == 0 then
				setPropertyFromGroup('unspawnNotes', i, 'rgbShader.r', 0xFF5500);
				setPropertyFromGroup('unspawnNotes', i, 'rgbShader.g', 0xFFFFFF); --Change color (left arrow)
				setPropertyFromGroup('unspawnNotes', i, 'rgbShader.b', 0x331100);
			end

			if getPropertyFromGroup('unspawnNotes', i, 'mustPress') then --Doesn't let Dad/Opponent notes get ignored
				setPropertyFromGroup('unspawnNotes', i, 'ignoreNote', true); --Miss has no penalties
			end
		end
	end
	--debugPrint('Script started!')
end

Are you modding a build from source or with Lua?
Lua
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
No response

Update: Somehow, the arrow Data detection works now (it didn't work earlier), but I still can't figure out how to get the user's colors and textures.


null value and lines connections

hello,
"Connect null values" option in Grafana panel settings, won't work if there is no data pulled from the check_mk source. At the end, all points are connected.
like on this graf. Query interval is on 60s like in check_mk (enterprice version).
Tested also the Connect null values/Threshold with <2m settings and nothing has changed

the goal is to have such graf

Is it possible to go around with such a problem?
Maybe I missed some settings?
Grafana v8.0.4 (81fef5b4b4)
Checkmk enterprice  1.6.0p19
Marcin

Hello :
Same problem here
https://forum.checkmk.com/t/bug-checkmk-datasource-with-0-value/28276/4
For me the reason is because the Checkmk data source dont' have "Fill" option, like Fill:Null, Fill:zero or other.
We have this option in PNP datasource, InfluxDB datasource ...
Thank you.


JSON parse error

I'm having trouble with a high number of records not being indexed and I'm not sure what's causing the error. Can you help determine if it's a config on my end or an issue?
Here is my config:
# Config for logger_logstash_backend
config :logger,
  backends: [{LoggerLogstashBackend, :error_log}, :console],
  format: "$time $metadata[$level] $message\n",
  metadata: [:request_id]

config :logger, :error_log,
  host: "logstash.hostname.com",
  port: 10_001,
  level: :info,
  type: "elixir_log",
  metadata: [
    application_name: "og_v2",
    env: "prod"
  ]

Here's the input filter:
udp {
    codec => json
    port => 10001
    type => elixir_log
    queue_size => 10000
    workers => 10
  }

Here's the output filter:
}else if [type] == "elixir_log" {
      elasticsearch {
                hosts => ["elasticsearch.hostname.com:9200"]
                index => "%{[fields][application_name]}-%{+YYYY.MM.dd}"
                document_type => "doc"
    }

Here's an example of the log:
[2018-10-10T14:31:37,223][ERROR][logstash.codecs.json     ] JSON parse error, original data now in message field {:error=>#<LogStash::Json::ParserError: Unexpected character ('\' (code 92)): was expecting double-quote to start field name
 at [Source: (String)"{\"@timestamp\":\"2018-10-10T14:31:37+0000\",\"fields\":{\"application\":\"plug\",\"application_name\":\"og_v2\",\"env\":\"prod\",\"file\":\"lib/plug/logger.ex\",\"function\":\"call/2\",\"level\":\"info\",\"line\":34,\"module\":\"Elixir.Plug.Logger\",\"pid\":\"#PID<0.9798.1>\",\"request_id\":\"ha8cd41ahpu56t1905jev0a17s8k8dd3\"},\"message\":\"Sent 200 in 261\xB5s\",\"type\":\"elixir_log\"}"; line: 1, column: 3]>, :data=>"{\\\"@timestamp\\\":\\\"2018-10-10T14:31:37+0000\\\",\\\"fields\\\":{\\\"application\\\":\\\"plug\\\",\\\"application_name\\\":\\\"og_v2\\\",\\\"env\\\":\\\"prod\\\",\\\"file\\\":\\\"lib/plug/logger.ex\\\",\\\"function\\\":\\\"call/2\\\",\\\"level\\\":\\\"info\\\",\\\"line\\\":34,\\\"module\\\":\\\"Elixir.Plug.Logger\\\",\\\"pid\\\":\\\"#PID<0.9798.1>\\\",\\\"request_id\\\":\\\"ha8cd41ahpu56t1905jev0a17s8k8dd3\\\"},\\\"message\\\":\\\"Sent 200 in 261\\xB5s\\\",\\\"type\\\":\\\"elixir_log\\\"}"}

We're seeing this issue because of how a unicode character µ is being escaped in the message. I can make it work by changing the options on JSX.encode. If there's interest I can make a pull request to allow passing JSX options through in configuration.

@otherchris

We're seeing this issue because of how a unicode character µ is being escaped in the message.

I'm a little confused by what you wrote. I used netcat (nc) as a 'dummy' Logstash server and the µ character came thru fine. The problem definitely seems to be with Logstash – it's not accepting that character as being valid UTF-8 (which it totally is). Maybe you meant that you were seeing this because of how that character is not being escaped?
I noticed that other Unicode characters in log messages would result in the error covered in issue #28. The changes in your pull request (#26), along with the option (:uescape) you used in the unit test you added, resolved that error – thanks!
I'm willing to accept that these characters (i.e. any non-ASCII characters) will need to be escaped for Logstash itself – I'm definitely not 'happy' that, despite their claims to the contrary, they don't in fact accept (all possible valid) UTF-8 – but I wonder if another option would be more appropriate for, e.g. a better behaved Logstash.

@otherchris Thanks again for the pull request – that definitely resolves this error.
I'm still frustrated that Logstash won't just accept UTF-8. From all of the things I read, I vaguely remember someone speculating that it's likely due to Ruby conventions about handling 'printable characters' (and assuming that at least some output devices won't be able to handle anything beyond ASCII characters). [The Logstash JSON codec plugin is written in Ruby.]


[bugfix] issue-6390 , wrong result in query view with an added null column

Proposed changes
Fix fe/fe-core/.../analysis  isNullpredicate.java ,add a getResultValue function to fix issue-6390
Types of changes
What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
[ ] Code refactor (Modify the code structure, format the code, etc...)
[ ] Optimization. Including functional usability improvements and performance improvements.
[ ] Dependency. Such as changes related to third-party components.
[ ] Other.

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have created an issue on (Fix #6390 ) and described the bug/feature there in detail
[ ] Compiling and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] If these changes need document changes, I have updated the document
[ ] Any dependent changes have been merged

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

hi morningman～ I add some unit test in QueryPlanTest.java. the bug need createView and orderby，so I add a function to create view，use LOG.info show explainString，and use assertTrue to test。

@morningman i solve the conflict,please try again.


Labeling Interface won't finish loading for simple TextArea labeling task with pre-annotation.

Describe the bug
The labeling interface on a new project sits at the loading bar for a very long time. It is a sequence-to-sequence labeling tasks, and tasks are loading just fine on another project with much longer text.
To Reproduce
Steps to reproduce the behavior:

This is my interface xml:

<View>
  <Text name="source_uri" value="Excel File: $excel_file"/>
  <Text name="sheet_name" value="Sheet: $sheet_name"/>
  <Header value="Official Fields"/>
  <Text name="official_fields" value="$official_fields"/>
  <Header value="Extracted Fields"/>
  <TextArea name="target_sequence" toName="official_fields" showSubmitButton="true" maxSubmissions="1" editable="true" rows="5" required="true"/>
</View>

This is a small example task json, with a (fake) prediction to use as pre-annotation:

{'data': {'excel_file': 'Redacted Customer Name',
  'sheet_name': 'P&L- Monthly',
  'mongo_id': '664e22cdbe7762824cd41056',
  'official_fields': "['Revenues', 'Cost of Good Sold', 'Gross Profit', 'Operating Expenses', 'Depreciation & Amortization', 'Operating Income', 'Interest', 'Taxes', 'EBITDA', 'EBITDA Adjustments', 'Adjusted EBITDA']"},
 'meta': {},
 'annotations': [],
 'predictions': [{'model_version': 'claude-3-haiku-20240307',
   'result': [{'id': None,
     'from_name': 'target_sequence',
     'to_name': 'official_fields',
     'type': 'textarea',
     'value': {'text': ['this is fake and short']}}]}],
 'prediction_model': 'claude-3-haiku-20240307',
 'id': 0}

**Expected behavior**
The labeling interface should eventually load completely.

**Screenshots**
This is what I see, and it just sits there forever. Notice that all the data seem to be loading, but they're in the background waiting for the progress bar to stop. Again, a simlar task that has large csv files as input texts and very long textarea outputs on a similar project are loading just fine.

![image](https://github.com/HumanSignal/label-studio/assets/165709641/2cbf6041-5f97-4014-8fea-c977821dcad6)

**Environment (please complete the following information):**
 - OS: Sonoma 14.4.1 is the local machine where the browser is running
 - Label Studio is running on a t2.large EC2 box with  Ubuntu 22.04.4
 - Label Studio Version 1.12.0

**Additional context**
- I can provide an axample from the other project that works if that will help to use as a reference point.
- Label-studio is not running inside a docker container, but there are two other docker lightweight containers running on the same machine
- I have tried rebooting the EC2 instance as well as Label Studio and have done a `docker system prune` just in case there were disk space issues making things hang up. The problem persisted through those initial sniff tests.

Hi @sajarin, thanks for taking this issue on.
It hangs indefinitely; the longest I've waited before closing out the window is approximately 30 minutes. I have upgraded to 1.12.1, and the issue persists.


Change Torque time-series widget behavior on range selection (2nd iteration)

The current behavior when a range is selected in a torque time-series widget (as of #786) is to animate the time-slider within the range. When a range is selected the behavior should be changed to:

[ ] the torque controls (play/pause) and (step) time-info views should be hidden
[ ] all points within the selected time-series should be visible on the map
[ ] histogram size/bins should remain after first render of data, even if other filters (e.g. bbox) and/or range selection is changed
[ ] information about the selected range (same as time-info but for range) should be displayed
[ ] a button to clear the selected range should be available

@saleiva did we get the details correct? something missing?

after talking with @javisantana and @rochoa this is not feasible atm, and will need more discussion before continuing.

This will use: https://github.com/CartoDB/torque/issues/246

Moved to https://github.com/CartoDB/deep-insights.js/issues/6, since the the concerned code was extracted :wave:

Reopening, there's still some work TBD here (updated desc)

Done in #937


Allow the customer to set up the dm endpoint by configuration

Now the customer can use the CollectorURL configuration in order to setup dm endpoints to ensure FedRAMP compliance.
By default collector_url return: https://infra-api.newrelic.com.
More information about FedRAMP compliance in NR docs.
Resolve #122

Pull Request Test Coverage Report for Build 276313249

2 of 3 (66.67%)  changed or added relevant lines in 2 files are covered.
10 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.02%) to 58.441%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

cmd/newrelic-infra/newrelic-infra.go
0
1
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/metrics/sampler/sampler_routine.go
2
94.74%

pkg/integrations/v4/logs/cfg_watcher.go
4
67.5%

pkg/integrations/v4/logs/logs/cfg_watcher.go
4
67.5%

Totals

Change from base Build 268820474:
0.02%

Covered Lines:
11077

Relevant Lines:
18954

💛  - Coveralls


Introduce AnyTag to allow users not specify tags in AccessTraits

Allow user to not specify the AccessTraits tags when there is clear disambiguation. If the same struct is used for both primitive and predicates, the tags are still required.
Mostly want to start the discussion and get the feedback. This works but I have not thought too deeply about whether it's a good implementation.

Superseded by #1172.


initial changes for consul template

Not ready yet for merging, but wanted others to see the initial changes I’m thinking about.

Won't do and will stick with envconsul


OpenNebula: VM_HIDDEN_ATTR and posibility for hide some flieds from user

Author Name: kvaps kvaps (kvaps kvaps)
Original Redmine Issue: 5479, https://dev.opennebula.org/issues/5479
Original Date: 2017-10-19

I want to hide some flieds from user, so only oneadmin can see or edit this.
I suggest you entering the following variables in the config file:
VM_HIDDEN_ATTR
VNET_HIDDEN_ATTR
INHERIT_HIDDEN_ATTR
INHERIT_HIDDEN_ATTR
USER_HIDDEN_ATTR

It will work like VM_RESTRICTED_ATTR and VNET_RESTRICTED_ATTR but will prevent showing this flieds for user.

This will somehow break the current data model. We'll close this and if a good use case need this will reopen to implement it.


linuxacademy.com - Site Support Request

Make sure you are using the latest version: run youtube-dl --version and ensure your version is 2016.11.18. If it's not read this FAQ entry and update. Issues with outdated version will be rejected.

[x] I've verified and I assure that I'm running youtube-dl 2016.11.18

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[ ] Bug report (encountered problems with youtube-dl)
[x] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

Carefully read new issue template and provide all requested information.

@sejpalsaurabh Please try https://github.com/vassim/linuxacademy-dl. It's still in its early-alpha but damn cool and useful! (and its the second time I'm making the similar comment in this repo!!)


Add ability to name/identify queries

For logging purposes it would be beneficial if we could add arbitrary identifier (e.g. a name) when queries are defined. Then we could extract this identifier at the point of logging (e.g. in AfterQuery) and accordingly mark the logs (and traces).
This would help a lot with debugging and profiling in systems where one has hundreds of different queries in a code base (sometimes also performed at more then hundreds queries per second on production servers).

In OpenTelemetry/Uptrace we use file:line extracted from stacktrace to identify the query. Is not that enough?

Hi Vladimir,
at your suggestion I found the function fn, file, line := funcFileLine("github.com/uptrace/bun") that extracts function name (+ file, line) that calls bun (i.e. the function where the query is). This would be enough information for us to identify separate SQL queries.
Thank you for your help.


Support resetting config

Coverage increased (+0.009%) to 54.645% when pulling c3626edd429d25b3be2ca81bc0c3e43b1a3a6836 on ywk253100:170313_reset_config into 3b53b354d3cda3f023d53cb79262c03ce61ea75a on vmware:dev.

Coverage increased (+0.05%) to 54.691% when pulling c5917eddf31f13ce5c81e893af6e924f92ecc869 on ywk253100:170313_reset_config into 3b53b354d3cda3f023d53cb79262c03ce61ea75a on vmware:dev.


fix: vmware horizon product key

fixes #1545

:tada: This PR is included in version 2.23.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Set up custom server for image tiles

Make it easy to set up an openstreetmap tile server

This has been moved to Minerva issue https://github.com/Kitware/minerva/issues/248


Implement watch stories function during interact

args: --stories-count 2-4
During user interaction watch a random number of stories before liking the picture
https://github.com/GramAddict/bot/projects/1#card-49292778

Hey Alex, could you please explain more how it works?
Does it watch some stories of the user the bot is supposed to like a picture? Or it just go some random random user and watch it?
Thanks for the feature btw!

Yes of course, I'll try to explain but my English It's not the best 😂
The logic it's the same of interaction-blogger or like hashtag-likers
So:

Iterate the list of followers or likes
Open the page
Check the filter, if all of the condition is meet continue
If the user have a stories watch a randomly number of stories between
range defined in --stories-count 2-4 (of use --stories-count 0 if you
don't want to watch the stories)
Scroll down and like random pictures as has always been done
Return to users list

On Sun, 15 Nov 2020, 01:59 Arthur Silva<EMAIL_ADDRESS>wrote:

Hey Alex, could you please explain more how it works?
Does it watch some stories of the user the bot is supposed to like a
picture? Or it just go some random random user and watch it?
Thanks for the feature btw!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/GramAddict/bot/pull/51#issuecomment-727289108, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADLJAGPLATYZBBTAT3LL423SP4RXJANCNFSM4TVZCDDA
.

@arthurspa I've see right row about the view, yes I'll try to update the code


Create yash-dj-films-and-studio.is-local.org.json

Requirements

[x] You have completed your website.
[x] The website is reachable.
[x] The CNAME record doesn't contain https:// or /.
[x] There is sufficient information at the owner field.
[x] Your website is not hosting on the following due to SSL issues: Vercel, Netlify

Description
the domain will be used for my projects, my home vps so it does not be able to access in the pubic, and i would not like to make ip address public so i will be using proxy for that
Link to Website

it will also be for project use


Define transaction schema

{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/jwaspin/luca-ledger/main/schemas/v2.0/transaction.json",
  "title": "Transaction",
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "A unique identifier for the transaction."
    },
    "payorId": {
      "type": "string",
      "description": "The identifier for the entity making the payment."
    },
    "payeeId": {
      "type": "string",
      "description": "The identifier for the entity receiving the payment."
    },
    "categoryId": {
      "type": ["string", "null"],
      "description": "The identifier for the category this transaction is associated with. Can be null if not categorized."
    },
    "amount": {
      "type": "number",
      "description": "The monetary value of the transaction."
    },
    "date": {
      "type": "string",
      "format": "date",
      "description": "The date the transaction took place."
    },
    "description": {
      "type": "string",
      "description": "A textual description of the transaction."
    },
    "state": {
      "type": "string",
      "enum": ["planned", "scheduled", "pending", "completed", "cancelled"],
      "description": "The current state of the transaction."
    },
    "createdAt": {
      "type": "string",
      "format": "date-time",
      "description": "The timestamp when the transaction was created."
    },
    "updatedAt": {
      "type": ["string", "null"],
      "format": "date-time",
      "description": "The timestamp when the transaction was last updated. Nullable to accommodate transactions that have not been updated."
    }
  },
  "required": [
    "id",
    "payorId",
    "payeeId",
    "categoryId",
    "amount",
    "date",
    "description",
    "state",
    "createdAt",
    "updatedAt"
  ],
  "additionalProperties": false
}

https://github.com/jwaspin/luca-ledger/pull/158


added Azure server-side example

Description
Added an example of doing push in a node.js backend from Azure using an
Azure Mobile App, push notification hubs, and push notification templates.
Related Issue
Motivation and Context
There are various examples of using the plugin server-side such as ADM, but none for Azure.
How Has This Been Tested?
This has been tested in Cordova apps against Android, iOS, and Windows. It is the same code found in the official Azure documentation here:
https://azure.microsoft.com/en-us/documentation/articles/app-service-mobile-cordova-get-started-push/#add-push-to-app
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@Mikejo5000 do you think you can write some markdown to go with this file describing how to use it?

@macdonst I included two links to key documents in the comments for the code. The complete E2E process seems like a lot of information for this page. If you think a task summary with links for more info is better than the links in the comments, I will be happy to do that.

@Mikejo5000 Merged, thanks for the PR. I know people will find the information useful. I just wish I had time to use all of the backends.


Clicking on tab number in tabline doesn't switch to selected tab

In fact, double clicking can open new tabs sometimes for some reason. Probably I messed up the placement of the %<n>T component which has something to do with mouse click events according to :h setting-tabline.

Fixed in 39f8b6f, the double-click seems to be a feature but at least the clickable area is a bit better now.