Update dendron.topic.schema.md

What does this PR do?
The first line of a newly created schema (at least created with "Dendron: lookup schema") is:
version: 1

Shouldn't the docs be updated with this change?
What issues does this PR fix or reference?

Relates to: https://github.com/dendronhq/dendron-site/issues/347

Merge requirements satisfied

For more information, visit the Contributing Guide for Documentation

[ ] Check rendered output to ensure formatting is correct for renderings of wikilinks, note refs, tables, and images. Dendron: Show Preview can be used in your workspace to confirm the page renders as expected. Sometimes, Dendron: Reload Index needs to be ran if certain wikilinks aren't working as expected. (ignore this if contribution is made via the Edit this page on GitHub button from the published site)
[ ] If this PR includes any refactoring (renaming notes, renaming headers, etc.), make sure that these changes were done via Dendron Refactoring Commands. This will ensure that any other impacted areas of the documentation, that link to or embed modified notes (via note references), are automatically updated.

Verify GitHub Actions tests are passing, which can be seen in the Checks tab of the PR:

[ ] URL validator GitHub Action passes
[ ] Dendron site build GitHub Action passes

NOTE: If you are a new contributor, a maintainer will need to provide approval for GitHub Actions to run on your PRs.

yes they should. thanks for the update :)


Link to next-css/sass/less in docs are broken

Expected Behavior
Docs are accurate.
Current Behavior
Docs are inaccurate.
Steps to Reproduce (for bugs)

Go here: https://github.com/zeit/next.js#importing-css--sass--less-files
Click any of the three css/sass/less links

Happy to put together a quick PR if someone can tell me where the relevant branch is located.

Duplicate #3643

@Albert-Gao Apologies. When is the release?

Quote from the owner one day ago:

it'll be public soon with the upcoming v5 release


Consumer group.id should not be set

Consumer group.id should not be set by default.
When you launch a scenario a first with a consumer group set via  group.id Kafka will register the offset read by this consumer group.
If you launch the same scenario some times later, Kafka will send you all the messages sent between the two launch of the scenario.
This is usually not what to do for a end to end test perspective when you're only interested on the messages send during your scenario.
So I propose to not set consumer group.id by default.

In fact, you must se group.id to avoid commiting offset on a topic enable.auto.commit should be set to false by default.
This will allow to have idempotent scenario.

Consumer group.id should not be set by default.
When you launch a scenario a first with a consumer group set via group.id Kafka will register the offset read by this consumer group.
If you launch the same scenario some times later, Kafka will send you all the messages sent between the two launch of the scenario.
This is usually not what to do for a end to end test perspective when you're only interested on the messages send during your scenario.
So I propose to not set consumer group.id by default.

Good point. Thanks for the feedback .

I can provide a PR if you want


basic_test.go:TestVmGroupVolumeIsolation() should use physical datastore name

The TestVmGroupVolumeIsolation() test creates a volume (which lands on the default DS) and checks for accessibility. The volume is accessible.
Then a new vmgroup is created with VM_DS as the default datastore. Again the volume accessibility is checked.
Its entirely possible that the volume created earlier is in the datastore that VM_DS refers to. A subsequent check on accessibility succeeds, while expecting failure.
The test should check what datastore is actually backing VM_DS in the DEFAULT vmgroup then pick another datastore and create the vmgroup with that.
The test logs from https://ci.vmware.run/vmware/docker-volume-vsphere/775 -
2017/06/28 12:22:19 Creating volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_134801] on VM [<IP_ADDRESS>]
2017/06/28 12:22:26 Checking volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_134801] availability from VM [<IP_ADDRESS>]
2017/06/28 12:22:26 Checking volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_134801] availability from VM [<IP_ADDRESS>]
2017/06/28 12:22:27 Creating a vmgroup [T1] on esx [<IP_ADDRESS>]
2017/06/28 12:22:29 Checking volume [BasicTestSuite.TestVmGroupVolumeIsolation_volume_134801] availability from VM [<IP_ADDRESS>]
FAIL: basic_test.go:159: BasicTestSuite.TestVmGroupVolumeIsolation
basic_test.go:180:
c.Assert(accessible, Equals, false, Commentf("Volume %s is still available on [%s]", s.volName1, s.vm1))
obtained bool = true
expected bool = false
Volume BasicTestSuite.TestVmGroupVolumeIsolation_volume_134801 is still available on [<IP_ADDRESS>]

Closing for now, may have been caused by debug code in this CI.


Media keys on keyboard is triggered twice.

OS:
WIndows 10
GPMDP Version:
4.6.0 I think, cant find any info in the application but its updated to latest that its asked me for.
Issue Descriptions:
Enabling Windows 10 system media service will cause my keyboard media keys to happen twice.
Steps to Reproduce:
Enable said option and use the media keys on a logitech G610

Think this was fixed recently in master

Have the same issue, but it seems to have something to do when the main window is minimized. Otherwise it works fine.

update today, same issue persists and it does not matter if window is minimized or not (wont matter if window is in focus or not either).

reproduce of #3156 #3014 #2364 #2253

MarshallOfSound commented 27 days ago
Known and fixed in master

However I can still reproduce this.
This is mainly due to Windows Media Service + GPMDP Still both picking up on the Next Media Key it seems.

I misdeclared #3156 as fixed, this is still a duplicate of #2364


Updated to latest version v0.60.0 and now I can no longer edit FancyZones layout

Microsoft PowerToys version
v0.60.0
Running as admin

[X] Yes

Area(s) with issue?
FancyZones Editor
Steps to reproduce

Open PowerToys as Admin
Go to FancyZones
Click Launch Layout Editor
Or use Windows + Shift + ` shortcut
Error message is displayed, and I cannot edit the zones

✔ Expected Behavior
Expected to be able to edit FancyZones layout.
❌ Actual Behavior
Error message is displayed:

Other Software
No response

Uninstall and reinstall seems to have worked. However I still don't have the ability to snap Visual Studio (and some other apps) to any Zones

Similar issue.
Although I can open the Options and make changes to the layout, the layout does not save.
Plus FancyZones no longer works on extended monitors.

/dup of https://github.com/microsoft/PowerToys/issues/19223

/dup #19223


[SP-3134][PDI-15870] Incorrect error when verifying step

Build Completed
:fire: This pull request has some issues. It would be preferable to fix them in order for it to be just perfect. See below for more details. Some links are also available below for further assistance in addressing those issues.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f engine/build.xml clean-all resolve jacoco && ant -Dtestreports.dir=bin/reports/integration-test -f engine/build.xml jacoco-integration checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  engine/src/org/pentaho/di/trans/steps/rest/RestMeta.java
  engine/test-src/org/pentaho/di/trans/steps/rest/RestMetaTest.java

Unit test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.core.auth.core.impl.DefaultAuthenticationConsumerFactory

Branch Change: -7.14%:small_red_triangle_down:
Complexity Change: -7.69%:small_red_triangle_down:

org.pentaho.di.job.entries.evalfilesmetrics.JobEntryEvalFilesMetrics

Branch Change: -.39%:small_red_triangle_down:
Complexity Change: -.51%:small_red_triangle_down:
Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.job.entries.getpop.MailConnectionMeta

Branch Change: -1.00%:small_red_triangle_down:
Complexity Change: -1.41%:small_red_triangle_down:
Instruction Change: -.30%:small_red_triangle_down:

org.pentaho.di.job.entries.sql.JobEntrySQL

Instruction Change:  + 3.28%
Line Change:  + 3.87%

org.pentaho.di.trans.steps.checksum.CheckSumMeta

Instruction Change: -.11%:small_red_triangle_down:

org.pentaho.di.trans.steps.datagrid.DataGridMeta

Instruction Change:  + .09%

org.pentaho.di.trans.steps.groupby.GroupByMeta

Branch Change:  + 3.12%
Complexity Change:  + 3.16%
Instruction Change:  + .28%
Line Change:  + .75%

org.pentaho.di.trans.steps.insertupdate.InsertUpdateMeta

Instruction Change: -.05%:small_red_triangle_down:

org.pentaho.di.trans.steps.memgroupby.MemoryGroupByMeta

Branch Change:  + 1.18%
Complexity Change:  + 1.35%
Instruction Change:  + .18%
Line Change:  + .48%

org.pentaho.di.trans.steps.replacestring.ReplaceStringMeta

Instruction Change: -.07%:small_red_triangle_down:

org.pentaho.di.trans.steps.rest.RestMeta

Branch Change:  + 9.46%
Complexity Change:  + 1.90%
Instruction Change:  + 4.43%
Line Change:  + 5.11%
Method Change:  + 1.47%

org.pentaho.di.trans.steps.rowgenerator.RowGeneratorMeta

Instruction Change: -.08%:small_red_triangle_down:

org.pentaho.di.trans.steps.sortedmerge.SortedMergeMeta

Instruction Change:  + .18%

org.pentaho.di.trans.steps.synchronizeaftermerge.SynchronizeAfterMergeMeta

Instruction Change:  + .04%

Integration test coverage change
These statistics help you identify how your changes have affected the coverage of the following files. If a file is not in this list, then its coverage was not affected by your changes. To get some help interpreting these metrics, please refer to Jacoco's documentation.
org.pentaho.di.trans.step.BaseStep

Branch Change:  + .29%
Complexity Change:  + .18%
Instruction Change:  + .05%
Line Change:  + .08%

@pamval @mbatchelor please take a look.
This is a backport of #3245.


Add an option to override WhatsAppBusinessCloudApiConfig for specific messages

Currently when using this library with dependency injection we can only use the WABA and Phone Number provided when configuring the service provider.
Our use case requires using different phone numbers for each country we operate with, and it seems that creating a new WhatsAppBusinessClient for each message we send could be inefficient as a service provider is built and a new HttpClient is created for each new instance.
I suggest adding an optional parameter or using a context override to specify a different WhatsAppBusinessCloudApiConfig for each message we send, without the need of creating new WhatsAppBusinessClient instances.

Hi, I will have a look at your feature request for the multiple phone numbers specified in whatsappbusinesscloudapiconfig to use a single instance I will have free time in the weekend.
If you have a pull request I can have a look and merge it.


css-modules @import from node_modules issue/question

@davezuko, your repo was directly linked in https://github.com/css-modules/css-modules/pull/65.
I am trying to get css-modules to
// global.scss
:global {
  @import "~normalize.css/normalize.css"
}

results in:
Module build failed: ModuleNotFoundError: Module not found: Error: Cannot resolve module '~normalize.css/normalize.css' in /Users/chris/github/app/src/components

styles/core.scss shows you are importing locally managed version. Did you have similar issues using the npm version?
This seems to be the suggested way to import css from node_modules. https://github.com/webpack/css-loader/issues/12 SurviveJS's Webpack loading styles section
@gajus I would love to see if you had any input on this as well.
Thank you for your time.
//cc @bebraw

@chrisblossom Your problem is probably that you're specifying the .css extension (see this PR for libsass. What if you drop it and just try to @import "~normalize.css/normalize"?
If that doesn't work, it might also be because you need a modules definition your webpack config's resolve option.

Just shipped a change doing exactly what @SohKai recommends. Let me know if you run into any trouble.
Commit: https://github.com/davezuko/react-redux-starter-kit/commit/3dbdc0efeb8d03758d59db1732ff49cfdf3cbf28


⚠ Bofrost.fr has degraded performance

In 3db5ab6, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1007 ms

Resolved: Bofrost.fr performance has improved in 721ee5f after 6 minutes.


Support debugging mocha tests in vscode

This file allows debugging of the mocha tests in vscode, this will be super helpful particularly when fixing the vt tests.

It will only work if it's located at <opened folder>/.vscode/launch.json and it's a dot file so it will be hidden by default on Unix-like OS'. It's quite an inconvenience to copy and paste it like that. Note that we're still ignoring the directory, just not this file (which shouldn't change automatically).


 For example, many VTIL instructions and more exotic native registers lack implementation. Also, making vexit compile into a "ret" is a bad idea. I think it would make more sense to compile into an unconditional jmp to the operand of the vexit. Whoever wrote the compiler seems to think that VTIL routines should be subroutines with their own stack frame, but at least with vmprotect it makes more sense to think of them as code that could be executed inline with the native code wrapping vmenters, because a single vmenter rarely (maybe never?) represents a routine with its own stack frame and instead represent snippets of code that modify the stack of the "caller" (vmenterer?) I am not sure the facilities provided by asmjit for virtual register allocation are best suited to this project because they seem to be bound to the notion of a function with its own stack, perhaps a custom one will need to be built or a different library used.

i will make a pr if i can manage to get my fork working. I would call the compiler half complete but that would be generous, it is more like 40% done.

Yeah it was just some POC code from the Discord that I didn’t want to get lost. Improvements are definitely welcome!

Sorry for making this rude issue. I appreciate the work you and others have put into this

Haha, no worries ^^
On Fri, 18 Nov 2022 at 12:07, sussy baka @.***> wrote:

Sorry for making this rude issue. I appreciate the work you and others
have put into this
—
Reply to this email directly, view it on GitHub
https://github.com/vtil-project/VTIL-Utils/issues/7#issuecomment-1319791095,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AASYFGJW7TYRKKGW3BTD45DWI5IMLANCNFSM6AAAAAAR3G6KOM
.
You are receiving this because you commented.Message ID:
@.***>


Not building on RPi2 - Raspbian and Nodejs 0.12.0

These are the errors output but npm:
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:267:23)
gyp ERR! stack     at ChildProcess.emit (events.js:110:17)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (child_process.js:1067:12)
gyp ERR! System Linux 3.18.7-v7+
gyp ERR! command "node" "/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /home/pi/node_modules/airtunes
gyp ERR! node -v v0.12.0
gyp ERR! node-gyp -v v1.0.2
gyp ERR! not ok
npm ERR! Linux 3.18.7-v7+
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "airtunes"
npm ERR! node v0.12.0
npm ERR! npm  v2.5.1
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: `node-gyp rebuild`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-gyp rebuild'.
npm ERR! This is most likely a problem with the airtunes package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-gyp rebuild
npm ERR! You can get their info via:
npm ERR!     npm owner ls airtunes
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/npm-debug.log

It seems to be an issue with Nodejs 0.12.0 as I've managed to install successfully with Nodejs 0.10.36

+1

Had the same problemen, and looking at it at the moment. It seems that the V8 api has had a major overhaul with many breaking changes. I've made some modifications to the cpp lib and it seems to work now. Will do some more testing, but thing i'm there!


Avoid nested skylark functions as they don't work with bazel 4.*

This PR should fix https://github.com/grailbio/bazel-toolchain/issues/145 - please review.  Thanks!


[9.x] Fix HasOneThrough (added tests)

I added the missing tests for the PR #2738 so that it can be merged. The original 2 commits are not my work, they belong to RF1705
Related:

#2738

Released on v9.21.2 🚀 Thanks @Arne1303  and @RF1705


Can I get the contents and titles of emails?

I want to get the contents and titles of emails, but can't I do that from the API?
If I want to achieve this, should I access it using imap 4?
type Message.Raw does not seem to have a value.

Which Go package in this repo are you referring to?
Also, we may not be able to help you because the code in this repo is generated from the discovery document (machine-readable description) of the API. You should probably begin by consulting the API reference first, and only file an issue here if you believe the generated client does not correctly implement the API.

Thank you for filing this issue. We asked some clarifying questions or suggested a course of action a week or more ago and never heard back from you. We are unable to proceed with this issue until then, so we are closing it. Please feel free to comment with more information and we will re-open this issue.


Trouble getting a SIP Device

Hi, I am working using the atapi 64 bit dll and using it to query the CUCM 11.5 system for lines. However, I only see the lines associated with Cisco devices, not SIP devices. Any ideas why this maybe?
My configuration settings in the CUCM admin part is exactly the same for all 3 devices and my SIP Device can "talk" and "call" the other devices OK. I have associated a line, device and unique user to the SIP device, similar to the other ones.
_tapiManager = new TapiManager("Hills.CiscoCallManager");

                _tapiManager.LineAdded += this._tapiManager_LineAdded;
                _tapiManager.LineRemoved += this._tapiManager_LineRemoved;

                Logger.Info("Initialising Tapi Manager..");
                var pass = _tapiManager.Initialize();

// now when I query the Lines Property, I do not see the SIP Device in there.

thanks,
Randeep

Hello Randeep,
I am quite sure that issue is not related to ATAPI at all, but due to a CUCM misconfiguration.
To be sure: just open a TAPI client, such as phone.exe, see here, and look whether those SIP lines are present or not.
If, as I think, SIP lines are not present, I suggest to check permission of the CUCM Application User you're using. In particular, ensure user has privileges:

Standard CTI Allow Control of Phones supporting Connected Xfer and conf
Standard CTI Allow Control of Phones supporting Rollover Mode

BTW, the right place to investigate Cisco CTI issue is this forum.
Regards, Marco.

Hello Marco,
Indeed you are right and thank you for posting the answer so quickly. After further reading and exploring, I discovered that 3rd Party SIP Devices do not have this flag to turn on for calling monitoring:
"Allow Control of Device from CTI".
So, even after setting the permissions as you stated in your email I couldn't get access to the phones (even using phone.exe).
Thank you for the resources provided, I will close this issue now as it needs to be answered by Cisco really.
Randeep


Add CodeContests dataset

Adding a Dataset

Name: CodeContests
Description: CodeContests is a competitive programming dataset for machine-learning.
Paper:
Data: https://github.com/deepmind/code_contests
Motivation: This dataset was used when training AlphaCode.

Instructions to add a new dataset can be found here.

@mariosasko Can I take this up?

This dataset is now available here: https://huggingface.co/datasets/deepmind/code_contests.


Updating aarch64 actions to use 1.0.0 images

Note: this is already late, as we need 1.1.0 images, but for the moment it should suffice.

Uuh duplicate of https://github.com/crystal-lang/crystal/pull/10814 ?

@oprypin Nope. The other PR changed to crystallang/crystal which doesn't have aarch64 images. This keeps using the (unofficial) aarch64 images at jhass/crystal but with an updated version.

Unfortunately, the aarch64 CI jobs keep failing more or less consistently and without any error indication.

It isn't failing now, or at least, some are working that before weren't. But the x86 alpine one is failing (unrelated to this) 🤷

Only the build jobs pass. All the *-test-* aarch64 jobs are failing: https://github.com/crystal-lang/crystal/actions/runs/1053459506

Seems like something had hang up, some of the VMs were showing significant CPU usage despite no job running at the moment. I rebooted all the VMs and reran the workflow, looks much better so far.

@jhass Looks like the aarch64 runners hang up again while running compiler specs (I don't think they should take over an hour for that, but we can wait a little longer to see if they might finish later).

Well, they did take that long :)

This was apparently incomplete:
https://github.com/crystal-lang/crystal/blob/a8bc392ae80a91b96d3ba600fc38d5f266938025/.github/workflows/aarch64.yml#L36

Oops. @jhass if you find yourself with time to update the images, it would be nice to have 1.1.1 version to compile the latest pulls. Thanks!

@beta-ziliani These images just package up https://dev.alpinelinux.org/archive/crystal/. As you can see there's no archive there for 1.1.1 or 1.1.0. Feel free to find a different solution/way to build them, all the code used is at https://github.com/crystal-lang/crystal-infrastructure/tree/main/docker


multi gpu training error

ERROR:torch.distributed.elastic.multiprocessing.api:failed (exitcode: 1) local_rank: 1 (pid: 8665) of binary: xxxxxx/anaconda3/envs/esr/bin/python
CUDA_VISIBLE_DEVICES=2,3 python -m torch.distributed.launch --nproc_per_node=2 --master_port=4321 realesrgan/train.py -opt xxx --launcher pytorch --auto_resume

Can you provide more info?
It seems it's an issue of your installed pytorch.


Fix #9847 Add shouldRenderAsyncScripts option

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] It's submitted to the dev branch for v2.x (or to a previous version branch), not the master branch
[x] When resolving a specific issue, it's referenced in the PR's title (e.g. fix #xxx[,#xxx], where "xxx" is the issue number)
[x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
[x] New/updated tests are included

If adding a new feature, the PR's description includes:

[ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

Other information:

Actually, this is not fixing the issue. I need to investigate a bit more on this.

@yyx990803 Please look to this at affection :pray: :heart_eyes:

Hi guys, this is super important for performance. Do we have any ETA? Thanks :)

Would be really great to see this one pushed through, this feature is very important to reduce Javascript load in front end, which will be a big boost to SEO

Any update on when this feature will be available?
We are using lazy hydration it will be a huge plus to not load the not needed bundles at first.

+1 for this - would speed out Vue/Nuxt applications greatly. Any updates on when somebody pushes the merge button?

C'mon guys @jeanphilippeds did all the hard work on this one, it shouldn't even be that hard a merge as it's an optional boolean, can we get this in soon?

Can we merge this please? <3

WE WANT THIS! WE WANT THIS! WE WANT THIS! WE WANT THIS!
WE WANT THIS! WE WANT THIS! WE WANT THIS! WE WANT THIS!

PLEASE <3

please

yeah this would allow great performance improvements!

For everyone who is using nuxt, here is a workaround: https://github.com/vuejs/vue/issues/9847#issuecomment-626154095

@yyx990803 @posva @Akryum @Kingwl @LinusBorg Can we merge it please ? 🙏

I wonder what's keeping us from merging this with latest release? How can I help?

Guys, any news? how can we help? Sice google Web Vitals now scan more for unused code, this would help greatly.

We currently focus all our efforts on bringing Vue 3 and its supor libs into RC stage.
Please understand that we currently have less bandwidth for Vue 2, and improvements such as this are currenty not a the very top of the list.
We will ge back to Vue 2 and do a round of bug fixes and improvements as soon as our bandwidth allows.

@LinusBorg Fully understandable. Can't wait for vue 3. However, is this fix expected to hit Vue 3 as well?

Man, this is killing me waiting for this!
@jeanphilippeds, well done! Gutted it still hasn't made it's way in 7 months later

Hi, @LinusBorg, any progress on this? We are still waiting. It is even harder to get nice score after last PageSpeed Insights update.

Hi guys, there are still projects on Vue 2, can someone merge this, please? It really became a problem with new versions of Google Lighthouse.

can we merge this please?

How can I help getting this merged?


GPMDP floods error logs when off

Home Assistant release (hass --version):
0.36.1
Python release (python3 --version):
Python 3.4.2
Component/platform:
media_player/gpmdp
Description of problem:
When the desktop player is turned off, logs are flooded with below stacktrace repeatedly (every < 5mins)
Expected:
Proper error handling of GPMDP being off without logs being filled
Traceback (if applicable):
17-01-17 23:55:02 homeassistant.core: Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/lib/python3.4/asyncio/tasks.py", line 233, in _step
    result = coro.throw(exc)
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 387, in _update_entity_states
    yield from update_coro
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/helpers/entity.py", line 216, in async_update_ha_state
    yield from self.hass.loop.run_in_executor(None, self.update)
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/media_player/gpmdp.py", line 235, in update
    playstate = self.send_gpmdp_msg('playback', 'getPlaybackState')
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/media_player/gpmdp.py", line 210, in send_gpmdp_msg
    websocket = self.get_ws()
  File "/srv/homeassistant/homeassistant_venv/lib/python3.4/site-packages/homeassistant/components/media_player/gpmdp.py", line 195, in get_ws
    self._ws = self._connection((self._url), timeout=1)
  File "/home/homeassistant/.homeassistant/deps/websocket/_core.py", line 489, in create_connection
    websock.connect(url, **options)
  File "/home/homeassistant/.homeassistant/deps/websocket/_core.py", line 216, in connect
    options.pop('socket', None))
  File "/home/homeassistant/.homeassistant/deps/websocket/_http.py", line 67, in connect
    sock = _open_socket(addrinfo_list, options.sockopt, options.timeout)
  File "/home/homeassistant/.homeassistant/deps/websocket/_http.py", line 109, in _open_socket
    sock.connect(address)
OSError: [Errno 113] No route to host

Will check after I updated.


Benchmark Prototypes

Contains a set of prototypes for benchmarks.
I've cleaned up the code, and it should now have a consistent style.
Documentation is rather sparse, but should be enough to understand. In case of problems down the road @-mention me.
The plotted results of our example benchmarks are attached:
Maxprojection (for X, Y, Z direction)

Mean calculation using Non-/Seperable Filters

And in case you need it, this contains the used data & a gnuplot script to generate the graphs from it: means_gnuplot.tar.gz

This is nice :)
I will fix the conflicts


Make Side Bar A Separate Window

It would be nice if there was an option to make the sidebar separate from the client to place on a second screen, make it bigger or smaller, etc. No clue how this could be done but having a pop out sidebar is something I've always wanted to put on a second monitor.

Duplicate of #2463


Can not figure out the structure required for --override-package-information | missing documentation

I'm having trouble figuring out the correct JSON structure required for the --override-package-information option in the nuget-license tool. The available documentation does not provide clear guidance on how to format the override JSON file. I tried various approaches and also had a look into the source but no success so far. Can you please provide me with a sample. It would be greatly appreciated!

Please find an example here: https://github.com/sensslen/nuget-license/blob/main/.github/workflows/assets/Tests/overwritePackageInformation.json. I'd be very happy if you could help improve the documentation. I know it's lacking but I currently do not have the time to really work on that. Feel free to file Pull Requests for that.

Worked perfectly. I was not looking into the .github section of the project. Maybe it would be good to somehow set a link or such to the examples :)
Appreciate your swift response and the project!


Is it possible that two PromScale replicas behind one loadbalancer pick different leaders from two Prometheus instances?

Assuming Prometheus instances already configured properly based on docs: https://github.com/timescale/promscale/blob/master/docs/high-availability/prometheus-HA.md

A new leader will be chosen only if Promscale has not heard from the previous leader for some time. This time is 30 secs, please correct me @VineethReddy02  if I am wrong.

Yes, that's right. At any point, Promscale elects only one leader from Prometheus instances for writes.

@Harkishen-Singh @VineethReddy02 Thanks for your quick reply. But I still have some confusion. A picture speaks a thousand words, take below deployment as an example:

If Promscale1 and Promscale2 don't communicate with each other, then will they elect different leaders and send duplicate samples to TSDB?

Promscale1 and Promscale2 talk to each other through the Timescaledb. They update their state of last received leader in Timescaledb which is read by other Promscale instances.
I think our explaination in the doc needs some more technical details so that everyone cab have a very clear picture. Cc @VineethReddy02
Feel free to ask now questions @jxl4650152.

@Harkishen-Singh That sounds makes sense. Thanks.
One more question about running Promscale in HA mode: why is the external labels method of leader election recommended instead of the PostgreSQL lock method? what is the advantage of external labels? The doc seems doesn't mention it.

Hey @jxl4650152 , using the external_labels method for HA allows you to independently scale Promscale based on your requirement. The pg_lock based HA has a strong one-to-one bonding between each Prometheus and Promscale instance and restricts the free scaling of Promscale.

cc @VineethReddy02 for doc updates.

@jxl4650152 we have a blog post about this topic https://blog.timescale.com/blog/promscale-0-4-drawing-inspiration-from-cortex-to-rewrite-support-for-prometheus-high-availability/

The docs for the new HA already explain the inner working model. However, in upcoming releases, we deprecate the older HA.
So I do not see a reason for explaining the differences as the older one isn't an option anymore to use.
We can add a reference to the blog post on HA shared by mat to the docs for a detailed overview of how HA in Promscale evolved.

@cevian @VineethReddy02 Thanks, I see the blog.


Bundle together a release

Tag a release and make sure setup.sh only pulls the most recent release, not the most recent push

This is done


This repo is huge. Remove cache and build files from Git?

What happened?
This Git repo is huge. It currently weighs 713 MB, with only 16 MB of code and assets.
Most of the size is due to cache and bin directories, and the Git objects (.git/objects/pack/pack-*.idx) that version them:
.yarn/
packages/app-executor/bin/
packages/app-executor/dist/
packages/docs/.yarn/
packages/cli/bin/
packages/python/
...

Is there any use in versioning them?
To remove the extraneous objects from Git:
Command to find them:
for hash in $(git verify-pack -v .git/objects/pack/pack-*.idx | sort -k 3 -n | tail -10 | awk '{print $1}'); do git rev-list --all --objects | grep $hash; done

Command to remove them safely:
git filter-repo --invert-paths --path .yarn/ --path packages/app-executor/bin/  --path packages/app-executor/dist/ --path packages/docs/.yarn/ --path packages/cli/bin/ --path packages/python/ [...]

(From https://github.com/newren/git-filter-repo/)
I was able to reduce the repo to 44 M.

Yeah the main discussion for this is here https://github.com/yarnpkg/berry/discussions/4845
So, this repo follows yarn zero-install (unfortunately it does need a yarn install still for a few native deps), but I still like the idea of all the data being download with the one git install, rather than the data needing to be installed via yarn. I know it's a controversial take, but recommending --filter=blob:none is a pretty small thing.
I'd prefer to keep it like this for now, since it's not really hurting anyone.

Ok


[ZEPPELIN-2691] fix: should display setting for table

What is this PR for?
The table has few settings, but currently, the menu is not displayed.
I attached screenshots for comparison.
What type of PR is it?
[Bug Fix]
Todos
DONE
What is the Jira issue?
ZEPPELIN-2691
How should this be tested?
Create a table result and check whether setting menu is displayed or not.
print("%table a\tb\n1\t2")

Screenshots (if appropriate)
Before

After

Questions:

Does the licenses files need update? NO
Is there breaking changes for older versions? NO
Does this needs documentation? NO

CI failed but irrelevant.

https://travis-ci.org/1ambda/zeppelin/jobs/247463188

Results :

Tests in error:
  ZeppelinIT.testSparkInterpreterDependencyLoading:249->AbstractZeppelinIT.waitForParagraph:68->AbstractZeppelinIT.pollingWait:94 Â» Timeout
  ParagraphActionsIT.testRunOnSelectionChange:284 Â» NoSuchElement Unable to loca...
  SparkParagraphIT.testPySpark:157 Â» NoSuchElement Unable to locate element: {"m...

Tests run: 24, Failures: 0, Errors: 3, Skipped: 0

LGTM

@jongyoul Thanks for the review.

Will merge this if no more discussion

Hey @1ambda
I don't mean to create overhead on this already closed PR but, I've 0.73v installed and this happens to me.
Are there specific considerations I should have in mind to make it work or what?
Thanks


fix(buildrun): Enable buildrun to generate sa by default

Please refer to this issue: https://github.com/OpenFunction/OpenFunction/issues/219

@lizzzcai Thanks very much for this PR!


Asset dropdown to quickly change asset from trading view

Description
Asset dropdown to quickly change asset from trading view. When changing asset the URL whille change and update the whole trading UI
Motivation and Context
Beta testing feedback
How Has This Been Tested?
Locally, Optimism Kovan
Screenshots (if appropriate)
https://user-images.githubusercontent.com/5688912/136728201-b36d7a21-e16f-48d3-ab80-c962e51ed82e.mov
:

Can we change a bit so that the market is a separate section above the trade input box?


Add Tests to the project

Adds basic tests to the project
You will need to add a file called "testkey" to the root of the project directory, which contains the API key for a project in Instrumental.  Execute the tests with script/test and your test metrics should appear in that project.

tests pass, seems like the testkey thing could happen automatically as part of running script/test, but not a big deal. I put a real key in so I'm guessing now prod instrumental has some metrics from the test suite? If the intent of this was to write a script that would shoot stuff at prod instrumental and make sure no exceptions, :+1:

Yep, that's the goal.  There's an instrumental project (1010) that you have access to where I've been dumping my test metrics.


Display Data Update Time on Homepage

*This will require a decent bit of work*
The last update time of the GTFS data should be displayed on the home page of the website.
All of the GTFS data is audit tagged in postgres, so every row has a created/updated column timestamp and the data set it was ingested from is also present under the dataset column.
Currently it only has TFI data but in theory it could hold many sets of data.
A new entity could be created to store this data but seeing as we already have everything tagged using the first Agency from each dataset as update times seems acceptable and easy/light.
This should include two catagories:

Static schedules (Agency) (nightly update)
Realtime Update (updated every minute)

Each should be broken down into the individual dataset providers (just TFI for now)
For the frontend, a table type layout might work.

Here is an example from a previous site I made where I just supported 1 provider.

I introduced events that can serve this purpose for the BE
https://github.com/ANIALLATOR114/SimplyTransport/pull/43
Events are currently recording the attributes required to display the information above, simply fetch the most recent corresponding event for each catagory and display its created at time. Potentially other information too.
I am yet to implement vehicle positions but this doesnt block the other two.
Events should be used over just grabbing an arbitrary record as events distinguish between datasets. So in the future if there are multiple datasets they will all work together and can be filtered.


New rule proposal: Identifiers should be named only with Latin letters

Category: Naming
Title: Identifiers should be named only with Latin letters
One feature I am really really missing is verification that only Latin letters are used when naming identifiers.
This is very common mistake to use Cyrillic letter а instead of the Latin letter a in my country (Bulgaria) and other countries that use Cyrillic alphabet (Russia, Serbia, Macedonia, Ukraine, etc.).
These letters (a (а), o (о), e (е), k (к) and few others) look exactly the same in both Latin and Cyrillic alphabets and it is common to use the Cyrillic one without noticing.

Is this a good candidate for an optional rule? Or possibly for an entirely different analyzer package?

:+1: for rule

Is this a good candidate for an optional rule? Or possibly for an entirely different analyzer package?

Don't think so...

:+1:


Detect and avoid infinite redirects

Reported via Gitter at https://gitter.im/Aurelia/Discuss?at=5547f7af00544af36bdf8b8f
If a route redirects to a second route, which fails to activate, the router navigates back to the original, entering an infinite redirect loop.
Probably low-priority, but would be good to detect and log a helpful error.

Note that this can also happen if the first route to be activated fails.

:+1: maybe add some event or callback when the route fails to activate.
I have a route, lets' say it's called list and a redirection from '' to 'list'. the list veiw model loads some data in the activate method returning a promise but when the promise is rejected it enters the infinte loop. I should be able to do somthing when the promise is rejected like redirecting somewhere else.
Redirecting from the catch method of the promise returned in the activate callback didn't work


Support 8bit wav

From WAV specification:

8-bit samples are stored as unsigned bytes, ranging from 0 to 255. 16-bit samples are stored as 2's-complement signed integers, ranging from -32768 to 32767

This requires additional conversion to support 8bit WAV files.

Done


WIP Keep Flutter.framework binaries writable so they can be code signed

Description
Flutter.framework files were made read-only to "Provide a strong hint to developers that editing Flutter framework headers isn't supported" (https://github.com/flutter/flutter/commit/cb2b89c389e06c2cceb1a3361d520eaccb4cec8c)  However this is making the Flutter binary readonly, which is being copied into the final embedded Frameworks directories, then can't be codesigned.
Related Issues
Fixes https://github.com/flutter/flutter/issues/39507.
Tests
Turn back on add2app shard.
Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I signed the [CLA].
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change

[ ] Yes, this is a breaking change (Please read [Handling breaking changes]). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

This is a bit speculative.  See https://github.com/flutter/flutter/issues/39507#issuecomment-526407580.

The original logic was introduced in 2017, so what changed?
I wasn't able to reproduce this in a non-module, so what's the difference?
This seems flaky.  Even though according to a git bisect this was exposed 20 days ago with https://github.com/flutter/flutter/commit/78cca6250a7104cc1dd89edf1982878530e55ee6, there are many Cirrus runs of add2app that succeeded.  So why is this flaky?

First add2app-macos test passed.  Will keep rebasing to see if it's still flaky.

First add2app-macos test passed. Will keep rebasing to see if it's still flaky.

Passed a second time.

First add2app-macos test passed. Will keep rebasing to see if it's still flaky.

Passed a second time.

add2app-macos test failed, but got way past signing permissions to a flaky unit test?  So not from this change (though still concerning).
https://cirrus-ci.com/task/4538022030213120

First add2app-macos test passed. Will keep rebasing to see if it's still flaky.

Passed a second time.

add2app-macos test failed, but got way past signing permissions to a flaky unit test? So not from this change (though still concerning).
https://cirrus-ci.com/task/4538022030213120

        Cirrus CI
[Remove](#)

  [Instruction test_all failed in 02:52](https://cirrus-ci.com/task/4538022030213120)

    ✅ 01:41 clone

✅ 00:01 print_date
✅ 00:03 install_cocoapods
✅ 01:06 git_fetch
✅ 05:45 setup
✅ 00:02 setup_xcpretty
❌ 02:52 test_all

> > [[EarlGrey selectElementWithMatcher:grey_buttonTitle(@"Full Screen (Cold)")]
> > performAction:grey_tap()];
> > ```
> >
> > testFullScreenCanPop, failed: caught "EarlGreyInternalTestInterruptException", "Immediately halt execution of testcase"
> > /tmp/flutter sdk/dev/integration_tests/ios_add2app/ios_add2appTests/IntegrationTests.m:41
> > ```
> >
> >
> > [[EarlGrey selectElementWithMatcher:grey_buttonTitle(@"Full Screen (Cold)")]
> > performAction:grey_tap()];
> > ```
> >
> > testHybridView, Exception: NoMatchingElementException
> > /tmp/flutter sdk/dev/integration_tests/ios_add2app/ios_add2appTests/IntegrationTests.m:114
> > ```
> >
> >
> > [[EarlGrey selectElementWithMatcher:grey_buttonTitle(@"Hybrid View (Warm)")]
> > performAction:grey_tap()];
> > ```
> >
> > testHybridView, failed: caught "EarlGreyInternalTestInterruptException", "Immediately halt execution of testcase"
> > /tmp/flutter sdk/dev/integration_tests/ios_add2app/ios_add2appTests/IntegrationTests.m:114
> > ```
> >
> >
> > [[EarlGrey selectElementWithMatcher:grey_buttonTitle(@"Hybrid View (Warm)")]
> > performAction:grey_tap()];
> > ```
> >
> >
> >    Executed 4 tests, with 6 failures (6 unexpected) in 22.883 (22.919) seconds
> > 2019-08-30 14:50:15.653 xcodebuild[16360:33968] [MT] IDETestOperationsObserverDebug: 103.533 elapsed -- Testing started completed.
> > 2019-08-30 14:50:15.654 xcodebuild[16360:33968] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
> > 2019-08-30 14:50:15.654 xcodebuild[16360:33968] [MT] IDETestOperationsObserverDebug: 103.533 sec, +103.532 sec -- end
> >
> > Failing tests:
> >   ios_add2appTests:
> >   	-[FlutterTests testDualFlutterView]
> >   	-[FlutterTests testDualFlutterView]
> >   	-[FlutterTests testFullScreenCanPop]
> >   	-[FlutterTests testFullScreenCanPop]
> >   	-[FlutterTests testHybridView]
> >   	-[FlutterTests testHybridView]
> >
> > Test session results and logs:
> >   /Users/anka/Library/Developer/Xcode/DerivedData/ios_add2app-csiwhdwugybmwjeggtidemdjpolj/Logs/Test/Test-ios_add2appTests-2019.08.30_14-47-54--0700.xcresult
> >
> > ** TEST FAILED **
> >
> > ▌14:50:22▐ ELAPSED TIME: 3min 53.429s for ../../../build_and_test.sh  in dev/integration_tests/ios_add2app
> > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> > ERROR: Last command exited with 65 (expected: zero).
> > Command: ../../../build_and_test.sh
> > Relative working directory: dev/integration_tests/ios_add2app
> > ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
> > ```
> >
> >
> >
> >
> >        Show more
> >        Show less

Test Suite ios_add2appTests.xctest started
FlutterTests
    ✗ testDualFlutterView, Exception: NoMatchingElementException
    ✗ testDualFlutterView, failed: caught "EarlGreyInternalTestInterruptException", "Immediately halt execution of testcase"
    ✗ testFullScreenCanPop, Exception: NoMatchingElementException
    ✗ testFullScreenCanPop, failed: caught "EarlGreyInternalTestInterruptException", "Immediately halt execution of testcase"
    ✗ testHybridView, Exception: NoMatchingElementException
    ✗ testHybridView, failed: caught "EarlGreyInternalTestInterruptException", "Immediately halt execution of testcase"
ViewControllerRelease
    ✓ testReleaseFlutterViewController (2.455 seconds)
FlutterTests
  testDualFlutterView, Exception: NoMatchingElementException
  /tmp/flutter sdk/dev/integration_tests/ios_add2app/ios_add2appTests/IntegrationTests.m:96

// Verify that there are two Flutter views with the expected marquee text.
[[[EarlGrey
selectElementWithMatcher:grey_accessibilityLabel(@"This is Marquee")]
testDualFlutterView, failed: caught "EarlGreyInternalTestInterruptException", "Immediately halt execution of testcase"
/tmp/flutter sdk/dev/integration_tests/ios_add2app/ios_add2appTests/IntegrationTests.m:96

// Verify that there are two Flutter views with the expected marquee text.
[[[EarlGrey
selectElementWithMatcher:grey_accessibilityLabel(@"This is Marquee")]
testFullScreenCanPop, Exception: NoMatchingElementException
/tmp/flutter sdk/dev/integration_tests/ios_add2app/ios_add2appTests/IntegrationTests.m:41

[[EarlGrey selectElementWithMatcher:grey_buttonTitle(@"Full Screen (Cold)")]
performAction:grey_tap()];
testFullScreenCanPop, failed: caught "EarlGreyInternalTestInterruptException", "Immediately halt execution of testcase"
/tmp/flutter sdk/dev/integration_tests/ios_add2app/ios_add2appTests/IntegrationTests.m:41

[[EarlGrey selectElementWithMatcher:grey_buttonTitle(@"Full Screen (Cold)")]
performAction:grey_tap()];
testHybridView, Exception: NoMatchingElementException
/tmp/flutter sdk/dev/integration_tests/ios_add2app/ios_add2appTests/IntegrationTests.m:114

[[EarlGrey selectElementWithMatcher:grey_buttonTitle(@"Hybrid View (Warm)")]
performAction:grey_tap()];
testHybridView, failed: caught "EarlGreyInternalTestInterruptException", "Immediately halt execution of testcase"
/tmp/flutter sdk/dev/integration_tests/ios_add2app/ios_add2appTests/IntegrationTests.m:114

[[EarlGrey selectElementWithMatcher:grey_buttonTitle(@"Hybrid View (Warm)")]
performAction:grey_tap()];
   Executed 4 tests, with 6 failures (6 unexpected) in 22.883 (22.919) seconds

First add2app-macos test passed. Will keep rebasing to see if it's still flaky.

Passed a second time.

Passed (the step in question) a fourth time.  Removing WIP.
@cbracken Does any of this make sense to you? https://github.com/flutter/flutter/pull/39539#issuecomment-526421383

Even though I can't prove this will fix the flaky add-to-app test, I'm going to merge it since I still think it's a good change.  If we continue to see the flakes we can try to gather more info about the environments where this is reproducing.

This broke devicelab, because now we can't delete the flutter repo anymore.


sagittarius-scheme: 0.9.9 -> 0.9.10

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/sagittarius-scheme/versions.
meta.description for sagittarius-scheme is: An R6RS/R7RS Scheme system
meta.homepage for sagittarius-scheme is: https://bitbucket.org/ktakashi/sagittarius-scheme
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.9.10 with grep in /nix/store/q81mgms02mj7xc854amfy1i0fcxbzdwg-sagittarius-scheme-0.9.10
found 0.9.10 in filename of file in /nix/store/q81mgms02mj7xc854amfy1i0fcxbzdwg-sagittarius-scheme-0.9.10

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
sagittarius-scheme

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/q81mgms02mj7xc854amfy1i0fcxbzdwg-sagittarius-scheme-0.9.10
ls -la /nix/store/q81mgms02mj7xc854amfy1i0fcxbzdwg-sagittarius-scheme-0.9.10/bin

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

1 package built:

sagittarius-scheme

Maintainer pings
cc @wahjava for testing.

Result of nixpkgs-review pr 240952 run on aarch64-darwin 1

1 package marked as broken and skipped:

sagittarius-scheme

Result of nixpkgs-review pr 240952 run on x86_64-linux 1

1 package built:

sagittarius-scheme


Tab completion support

Is your feature request related to a problem? Please describe.
When I hit c, it prompts me for filename, but I can't use TAB completion to complete sub directories before entering the filename. Instead when I press TAB I see ^I injected:

Describe the solution you'd like
Pressing TAB should complete the subdirectories or files in that path.
Describe alternatives you've considered
Manually type in the sub path name.

I'm currently working in #118 on reusing the telescope prompt for the file input with something like this
https://user-images.githubusercontent.com/39233597/165178718-c1bde432-5c3a-43bc-9837-72142a2b0530.mp4
(it's already revised a bit and works better now)
which will enable you to complete file paths within the currently opened directory by means of telescope selection.
That said, file/folder creation of telescope-file-browser is primarily intended to be performed within the currently opened folder of the file_browser. Of course, generating a file in other folders is possibly, but that would make completion a bit more tricky.
I'll see what I can do, but that might have to wait until a later iteration (as I'm working on the stuff in the video as means to leverage telescope for vim.ui.input).

Apologies, I was overthinking this a bit in my efforts to leverage telescope prompt for vim.ui.input :) With dressing.nvim and the default implementation tab completion now should work nicely. Let me know in case there's any issues.


Followed streams not returning correct datas

Hi @dustinlakin
I had some strange values returned from this call :
client = Twitch.new access_token: '**********************'
JSON.parse(cient.followed_streams.to_json)

I actually even checked for a response 200 status and I'm still getting channel I haven't followed. It happens occasionally.
I checked if the issue was something from your gem but apparently I cannot find anything but:
Could the twitch API v2 be deprecated ?
Thanks for you time and your work!
Axel

I posted the issue: post

Thanks @catuss-a
I took a look at the issue you posted on twitch's api issues. I appreciate you looking into it and posting more there, we can leave this issue here until we hear back on it.
Cheers!
Dustin


1.4: executionTimeout property for async

We need a property on the semaphore isolated path for timeout now that we support async timeout.
Currently in the 1.4 RCs it uses the threadIsolated property for both, but that's confusing to set it for semaphoreIsolated configs.

@KoltonAndrus I don't see this property referenced anywhere in the execution flow.  Are you able to pick this back up and get that wired in?

After further thought, I think the ideal design is to have 1 timeout value defined, regardless of whether the command is sempahore- or thread-isolated.
Since only the async timeout mechanism is used now (as of #579), it's straightforward to wire a signal timeout into the AbstractCommand flow.  The only interesting thing is the configuration API.  My view is that the config setting should be agnostic of semaphore or thread isolation, and the config that is thread-specific (HystrixCommandProperties.executionIsolationThreadTimeoutInMilliseconds) should be deprecated.

Closed by #664


Uncaught think\exception\ErrorException : attribute should be used to temporarily suppress the notice

hi
after i do the demo,i found some bugs

During inheritance of Iterator: Uncaught think\exception\ErrorException: Return type of MacFJA\RediSearch\Redis\Response\PaginatedResponse::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress

my php version is 8.2.16
after i add #[\ReturnTypeWillChange] on the top of current() and other function in

macfja/redisearch/src/Redis/Response/PaginatedResponse.php

everything goes well
is there a plan to do some update ?
@MacFJA

I figure out  the problem.


Fix timewarp attacks

See conversation on https://delvingbitcoin.org/t/timewarp-miners-harvesting-and-vaults/218
Good open question on any timewarp fix, do we wish to constrain future consensus rules evolvability w.rt things like “forward block”.

How useful is fixing timewarp attacks on a permissioned PoW network?
I understand it makes a lot of sense on testnet4 or future mainnet softfork, but the miner of a Signet network (even a custom signet one) is not incetivized to trigger timewarp. Maybe for learning and experimentation purposes?

Maybe for learning and experimentation purposes?

Yes, if timewarp fixes ported on mainnet a day.


Review/update shell script of checking RC images

There is a script that reviews what is in RC in a Rancher release:
https://github.com/rancher/rancher/blob/release/v2.8/scripts/create-components-file.sh
rancher-images.txt
rancher-windows-images.txt
Dockerfile
go.mod
My bash skills aren't great, but does it check pkg/apis/go.mod pkg/settings/settings.go?
Is it possible to list out for each component, what file the RC info is still listed?

Templatize the output to be similar to how the rancher/rancher script is outputing the info for the update to the release in GH.

Script Update:

Remove references of dev in the Components with -rc section
Split Components with dev- section into 2 new sections

KDM References with dev branch
Chart References with dev branch

Script to be updated in release/v2.8, release/v2.7 and create a GH action for it.

This looks good. Let's update release/v2.8 so that it could be part of the next tagging of the RC.

When updating rancher/rancher for the script, we want to updated it in both release/v2.8, release/v2.7, release/v2.6 branches.
https://github.com/rancher/rancher/blob/release/v2.8/scripts/create-components-file.sh
https://github.com/rancher/rancher/blob/release/v2.7/scripts/create-components-file.sh
https://github.com/rancher/rancher/blob/release/v2.6/scripts/create-components-file.sh


maps/vdso: Simplify Base Address calculation

Simplify base address calculation
Improve VDSO handling
Reduce metrics on the hot path

Why?
To reason about things easily, in this PR, I remove legacy codepaths we had from pprof.
Now, the normalization and base address handling should be easier to reason about.
Moreover, this should fix some edge cases around mapping.
What?

🤖 Generated by Copilot at 8e029e5
This pull request refactors and improves the parca-agent codebase by extracting the kernel and process logic into separate packages, deleting unused and outdated code, fixing bugs and paths in tests, adding tracing spans and flags, and renaming packages and files for clarity and consistency.
How?

🤖 Generated by Copilot at 8e029e5

Rename the kconfig package to kernel and add functions for kernel version and VDSO detection (link, link, link, link, link, link, link, link, link)
Extract the executable package from the internal/pprof/binutils package and rename it to elfreader, which contains functions for reading and manipulating ELF files (link, link, link, link)
Delete the internal/pprof package and its subpackages, which are no longer needed (link, link, link, link, link)
Delete the address package and move its functionality to the process package, which handles the normalization of addresses in the process maps (link, link, link, link)
Add and remove tracing spans in the debuginfo package, which uploads the debug information of the ELF files to the server (link, link)
Update the paths to the testdata files in the debuginfo and kernel packages, which use the ELF files and the kernel config files for testing (link, link, link, link)
Move the isInContainer function from the kernel package to the main package, which checks whether the process is running in a container or not (link, link, link)
Replace the import of the kconfig package with the import of the kernel package in the main package, which uses the kernel package to check the BPF support (link, link)
Fix a bug in the defer statement in the main package, which used an undefined variable (link)

Test Plan

make ENABLE_RACE=yes test
Local on-host run
Local cluster run

I'm going to go ahead and merge this. Please let me know if you see anything to improve retrospectively.

Loooooove these changes!!
Especially love the improved ergonomics of using the mapping to bind the normalize function to.


Custom TestCase Templates

Hi,
It would be nice to have an option to add custom test case/suites templates from menu or using VI tester GUI. Right now there is only option to add the ones provided with VI tester.

This could solve issue #20 .
I guess implementation could be quite simple.
While adding new Test Case, there could be window with:

Test Case Name;
checkbox "Save to Project Folder?" (default: selected). If selected, then test case will be saved to root folder of the project, into the created folder. If not selected, then dialog window will appear to select folder to save test case;
path control "Test Case Template". And then:
If it is empty, then no template is used (but default one).
If it is not empty, then toolkit checks, if class is child of "TestCase.lvclass".
If yes, then it'll be copied and used as template.
If it is not in hierarchy of "TestCase.lvclass", then it will be not used (and promted to user) OR it could be set as child of "TestCase.lvclass".
If it is in hierarchy of "TestCase.lvclass", but not its "direct" child, then possible to use it, but change inheritance to "TestCase.lvclass" OR copy it with all its parents hierarchy. This is something what I'm not sure...

Will it be OK, please @jimkring ? Could it be implemented like that?

I think it would be better if it could be part of the context menu.
New Test >> Standard Template
New Test >> Wiresmith Template
etc. More complex installation but better developer experience.


rbd: replace Manager.DeleteVolumeGroup() by VolumeGroup.Delete()

There is no need for the Manager.DeleteVolumeGroup() function as
VolumeGroup.Delete() should cover everything too.
By moving the .Delete() functionality of removing the group from the
journal to the shared commonVolumeGroup type, a volume group snaphot
can use it as well.
Signed-off-by: Niels de Vos<EMAIL_ADDRESS>

@mergifyio queue


FlatList scrollToIndex scrolls to wrong place when used for the first time

[x] I have reviewed the documentation
[x] I have searched existing issues
[x] I am using the latest React Native version

When using a FlatList to display a small number of Buttons, the first time I call scrollToIndex, it miscalculates the position to put things on screen relative to the viewPosition specified.
Environment
Environment:
OS: macOS High Sierra 10.13.4
Node: 9.8.0
Yarn: 1.5.1
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.3.1 Build version 9E501
Android Studio: Not Found
Packages: (wanted => installed)
react: 16.3.1
react-native: 0.55.2
Steps to Reproduce
Load this snack: https://snack.expo.io/@amcvitty/flatlist-scroll-bug
This app simply scrolls the appropriate red box in the FlatList at the top to the center of the view when you click the corresponding button in the list below.

Click the "D2" button. Note that the D2 box scrolls to the extreme left ignoring the viewPosition specified (this is incorrect)
Click the "D2" button again. Note that the D2 box now scrolls to the center, respecting the viewposition
Further clicks on D2 will continue to leave the box in the middle correctly.

Expected Behavior
The first click should take the D2 box to the center
Actual Behavior
The first click ignores the viewPosition, unless the user does an actual scroll before the first call to scrollToIndex.
My debugging
I did a bit of debugging and the reason seems to be that this._scrollMetrics.visibleLength in VirtualizedList has been incorrectly set to 0 in a call to onScroll that happens after onLayout (when it is set correctly), but before any user interaction. The list receives a scroll event with all zeros, and specifically on this line:
VirtualizedList.js:1267: let visibleLength = this._selectLength(e.nativeEvent.layoutMeasurement);
the layoutMeasurement is 0.
Since the visibleLength is used in onScrollToIndex to calculate the appropriate scroll offset, the calculation is incorrect.
Scroll events triggered by user action have real event content and so the layoutMeasurement is reset correctly (to 375 on my iphone 7).

Replying to stale bot -  The issue has not been fixed. The snack looks the same and our app still suffers from this bug.

Still a bug

I think this is fixed in the latest release, at least I can't reproduce it in the latest version of the snack using those steps - @amcvitty any chance you can give it a re-run?

@orta Thanks for taking a look. I just reran the snack and I still see the same behavior. The first click scrolls D2 to the left of the screen, subsequent clicks scroll it to the center as expected
Here's me running it with expo 32.0.0:
http://recordit.co/w1vfrsGHpa


macOS Sierra 10.12.2 - Requirements not satisfied

I installed python via brew:
$ pip --version
pip 9.0.1 from /usr/local/lib/python2.7/site-packages (python 2.7)

Afterwards I installed requirements as described. But I still get the following error:
$ sudo python kickthemout.py

ERROR: Requirements have not been properly satisfied. Please try running:
	$ sudo pip install -r requirements.txt

If you still get the same error, please submit an issue here:
	https://github.com/k4m4/kickthemout/issues

If I try to install requirements again, I get the following:
$ sudo pip install -r requirements.txt
Requirement already satisfied: scapy in /usr/local/lib/python2.7/site-packages (from -r requirements.txt (line 1))

Hay I am not sure how much this will help but this helped to fix that problem with me
export PYTHONPATH=brew --prefix/lib/python2.7/site-packages:$PYTHONPATH

Adding the following to my ~/.bash_profile did not fix the problem for me:
export PYTHONPATH='brew --prefix'/lib/python2.7/site-packages:$PYTHONPATH
But thank you anyway.

just to ask did you run the command i sent or did you just try to add it to the profile

I tried both. Neither did work :(

Hi, I have the same problem running MacOS Yosemite 10.10.5 . If you have any ideas please let us know. Thanks.

Hi there. Check out the following issues: #13, #7 & #10. Please let me know if this resolves your issue. Thanks.


[release-1.11] autoregistration: allow bootstrap node to override locality

This is an automated cherry-pick of #33426

@S-Chan you need to make the bot happy

@googlebot I consent.


Like improvements

Try to implement "Unlike"
Integrate with notification (Spy), if it isn't done yet

It would be nice if the colour of the thumbs up like icon can be changed to blue to indicate that you liked it, and also a link added to the like count that you can click on to see who has liked the post...
knowing that the post is liked is not enough, knowing that you liked it is important and knowing who else has too is ;)


Update documentation to account for switch to Django

The app was switched from Flask to Django because I wasn't comfortable producing a user-facing service that wasn't regularly maintained with security vulnerabilities. Update the README to reflect this change.

Done.


Fixed stocks api

Changed the API to iextrading.com
Now we will be able to use the stocks program again
Pull Request Label:

[ ] Bug
[ ] New feature
[ ] Enhancement
[ ] New component
[ ] Typo
[x] Repair

Pull Request Checklist:

[x] Have you followed the guidelines for contributing?
[x] Have you checked that there aren't other open pull requests for the same fix or component?
[ ] Have you ran the tests locally with bats tests?

Fixes the issue #131

I have committed this directly to the master branch because I just replaced the previous API with the current API, that means it is direct consumer ready. Also, no previous feature has been deleted

@alexanderepstein What do you think about it ?

Looks perfect, thanks for fixing this :+1:  :tada:


"Affinity does not work if there are more workers than cores" causes hang

Describe the bug
I'm running parsl --config local tests in a docker container with a single CPU allocated to that container via docker run --cpuset-cpus=0
The parsl/tests/sites/test_affinity.py test hangs. When I dig into the htex worker logs I find this error. This error should be properly propagated to the submit side in some way rather than resulting in a hang.
2021-05-17 13:04:35.266 worker_log:505 Rank:1 [INFO]  Worker 1 started
2021-05-17 13:04:35.266 worker_log:507 Rank:1 [DEBUG]  Debug logging enabled
2021-05-17 13:04:35.266 worker_log:31 Rank:1 [ERROR]  Exceptional ending for worker on thread MainThread
Traceback (most recent call last):
  File "/home/benc/parsl/src/parsl/parsl/process_loggers.py", line 27, in wrapped
    r = func(*args, **kwargs)
  File "/home/benc/parsl/src/parsl/parsl/executors/high_throughput/process_worker_pool.py", line 514, in worker
    assert cores_per_worker > 0, "Affinity does not work if there are more workers than cores"
AssertionError: Affinity does not work if there are more workers than cores

To Reproduce
Run the above test in a docker container with --cpuset-cpus=0 set, on a machine that has more than 1 core.
Expected behavior
The error should propagate to the submit side and the test should fail (more generally - the workflow user should be presented with this error rather than a hang)
Environment
python 3.9.2, parsl master bf83c06af78ac0e4243fa2b6686d3b99110cf01c

@yadudoc and I had some discussion offline about the block error handling for the cases where the process worker pool starts, but then fails deeper into startup.
I think our talk was more in the context of misconfigured networking (eg. process_worker_pool start but cannot make a network connection), but I realise now this #2072 misconfiguration is also exactly that failure case.


DAVE34: Read and apply background data to lightcurve

Added bck file selector to toolPanel
Changed light curves methods for supporting optional background file
The method applied is to subtract background light curve count from the src light curve counts.
I juts only tested with the files passed by Simmone, but i dont know what happends if the lenght of the counts arrays are not equal , and im not checking that the time intervals were fitting the same range of time.  I suppose this will be checked on further versions.
Also added DataSet_Cache and Session_Helper files for cleaner code.

Hello @ricardovb! Thanks for submitting the PR.

In the file src/main/python/server.py, following                are the PEP8 issues :

Line 44:37: E251 unexpected spaces around keyword / parameter equals
Line 44:39: E251 unexpected spaces around keyword / parameter equals
Line 46:38: E211 whitespace before '('
Line 47:13: E128 continuation line under-indented for visual indent
Line 50:38: E251 unexpected spaces around keyword / parameter equals
Line 50:40: E251 unexpected spaces around keyword / parameter equals
Line 52:39: E211 whitespace before '('
Line 53:13: E128 continuation line under-indented for visual indent
Line 66:1: E305 expected 2 blank lines after class or function definition, found 1

There are no PEP8 issues in the file src/main/python/utils/dataset_cache.py !

There are no PEP8 issues in the file src/main/python/utils/dave_endpoint.py !

In the file src/main/python/utils/dave_engine.py, following                are the PEP8 issues :

Line 13:1: E302 expected 2 blank lines, found 1
Line 28:5: E265 block comment should start with '# '
Line 35:5: E265 block comment should start with '# '
Line 36:5: E265 block comment should start with '# '
Line 38:5: E265 block comment should start with '# '
Line 39:5: E265 block comment should start with '# '
Line 121:5: E265 block comment should start with '# '
Line 122:5: E265 block comment should start with '# '
Line 124:5: E265 block comment should start with '# '
Line 125:5: E265 block comment should start with '# '

In the file src/main/python/utils/dave_reader.py, following                are the PEP8 issues :

Line 46:9: E265 block comment should start with '# '
Line 50:44: E128 continuation line under-indented for visual indent
Line 51:44: E128 continuation line under-indented for visual indent
Line 123:42: E211 whitespace before '('
Line 139:37: E128 continuation line under-indented for visual indent
Line 140:37: E128 continuation line under-indented for visual indent
Line 145:121: E501 line too long (148 > 120 characters)

There are no PEP8 issues in the file src/main/python/utils/session_helper.py !

Hello @ricardovb! Thanks for updating the PR.

In the file src/main/python/server.py, following                are the PEP8 issues :

Line 41:80: E501 line too long (84 > 79 characters)
Line 47:13: E128 continuation line under-indented for visual indent
Line 47:80: E501 line too long (82 > 79 characters)
Line 52:80: E501 line too long (110 > 79 characters)
Line 53:13: E128 continuation line under-indented for visual indent
Line 67:80: E501 line too long (88 > 79 characters)
Line 71:80: E501 line too long (83 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/dataset_cache.py !

In the file src/main/python/utils/dave_endpoint.py, following                are the PEP8 issues :

Line 104:80: E501 line too long (89 > 79 characters)

In the file src/main/python/utils/dave_engine.py, following                are the PEP8 issues :

Line 29:80: E501 line too long (91 > 79 characters)
Line 130:80: E501 line too long (92 > 79 characters)
Line 135:80: E501 line too long (83 > 79 characters)
Line 136:80: E501 line too long (87 > 79 characters)
Line 149:80: E501 line too long (82 > 79 characters)

In the file src/main/python/utils/dave_reader.py, following                are the PEP8 issues :

Line 46:9: E265 block comment should start with '# '
Line 50:44: E128 continuation line under-indented for visual indent
Line 51:44: E128 continuation line under-indented for visual indent
Line 92:80: E501 line too long (92 > 79 characters)
Line 139:80: E501 line too long (88 > 79 characters)
Line 140:37: E128 continuation line under-indented for visual indent
Line 141:37: E128 continuation line under-indented for visual indent
Line 146:80: E501 line too long (148 > 79 characters)
Line 148:80: E501 line too long (80 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/session_helper.py !

In the file src/test/python/test/utils/test_dave_engine.py, following                are the PEP8 issues :

Line 11:1: E302 expected 2 blank lines, found 1

Hello @ricardovb! Thanks for updating the PR.

In the file src/main/python/utils/dataset_helper.py, following                are the PEP8 issues :

Line 9:1: E265 block comment should start with '# '
Line 29:18: E211 whitespace before '('
Line 30:22: E211 whitespace before '('
Line 44:5: E265 block comment should start with '# '
Line 45:43: E261 at least two spaces before inline comment
Line 45:44: E262 inline comment should start with '# '
Line 48:33: E226 missing whitespace around arithmetic operator
Line 52:33: E226 missing whitespace around arithmetic operator
Line 53:30: E226 missing whitespace around arithmetic operator

There are no PEP8 issues in the file src/main/python/utils/dave_endpoint.py !

There are no PEP8 issues in the file src/main/python/utils/dave_engine.py !

There are no PEP8 issues in the file src/main/python/utils/dave_logger.py !

In the file src/main/python/utils/dave_reader.py, following                are the PEP8 issues :

Line 46:9: E265 block comment should start with '# '
Line 50:44: E128 continuation line under-indented for visual indent
Line 51:44: E128 continuation line under-indented for visual indent
Line 140:37: E128 continuation line under-indented for visual indent
Line 141:37: E128 continuation line under-indented for visual indent
Line 146:121: E501 line too long (148 > 120 characters)

There are no PEP8 issues in the file src/main/python/utils/file_utils.py !

In the file src/main/python/utils/gevent_helper.py, following                are the PEP8 issues :

Line 13:1: E302 expected 2 blank lines, found 1
Line 20:22: E203 whitespace before ':'
Line 21:23: E203 whitespace before ':'
Line 22:20: E203 whitespace before ':'
Line 48:30: E261 at least two spaces before inline comment
Line 55:5: E265 block comment should start with '# '

In the file src/main/python/utils/plotter.py, following                are the PEP8 issues :

Line 4:1: E302 expected 2 blank lines, found 1

There are no PEP8 issues in the file src/main/python/utils/session_helper.py !

There are no PEP8 issues in the file src/test/python/test/utils/test_dataset_helper.py !

In the file src/test/python/test/utils/test_dave_engine.py, following                are the PEP8 issues :

Line 11:1: E302 expected 2 blank lines, found 1

Hello @ricardovb! Thanks for updating the PR.

In the file src/main/python/model/column.py, following                are the PEP8 issues :

Line 3:1: E302 expected 2 blank lines, found 1

In the file src/main/python/model/dataset.py, following                are the PEP8 issues :

Line 6:1: E302 expected 2 blank lines, found 1
Line 46:80: E501 line too long (110 > 79 characters)
Line 48:80: E501 line too long (84 > 79 characters)
Line 52:13: E211 whitespace before '('
Line 57:80: E501 line too long (86 > 79 characters)
Line 75:80: E501 line too long (94 > 79 characters)
Line 81:80: E501 line too long (144 > 79 characters)
Line 114:80: E501 line too long (146 > 79 characters)
Line 139:80: E501 line too long (104 > 79 characters)
Line 143:80: E501 line too long (90 > 79 characters)
Line 144:80: E501 line too long (86 > 79 characters)
Line 155:80: E501 line too long (94 > 79 characters)
Line 157:80: E501 line too long (139 > 79 characters)

In the file src/main/python/model/table.py, following                are the PEP8 issues :

Line 45:80: E501 line too long (156 > 79 characters)

In the file src/main/python/server.py, following                are the PEP8 issues :

Line 47:80: E501 line too long (84 > 79 characters)
Line 53:13: E128 continuation line under-indented for visual indent
Line 53:80: E501 line too long (82 > 79 characters)
Line 58:80: E501 line too long (110 > 79 characters)
Line 59:13: E128 continuation line under-indented for visual indent
Line 83:80: E501 line too long (88 > 79 characters)
Line 89:80: E501 line too long (83 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/dataset_cache.py !

In the file src/main/python/utils/dataset_helper.py, following                are the PEP8 issues :

Line 9:1: E265 block comment should start with '# '
Line 13:80: E501 line too long (81 > 79 characters)
Line 14:80: E501 line too long (90 > 79 characters)
Line 45:43: E261 at least two spaces before inline comment
Line 45:44: E262 inline comment should start with '# '
Line 45:80: E501 line too long (110 > 79 characters)

In the file src/main/python/utils/dave_endpoint.py, following                are the PEP8 issues :

Line 102:80: E501 line too long (89 > 79 characters)

In the file src/main/python/utils/dave_engine.py, following                are the PEP8 issues :

Line 113:80: E501 line too long (82 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/dave_logger.py !

In the file src/main/python/utils/dave_reader.py, following                are the PEP8 issues :

Line 46:9: E265 block comment should start with '# '
Line 50:44: E128 continuation line under-indented for visual indent
Line 51:44: E128 continuation line under-indented for visual indent
Line 92:80: E501 line too long (92 > 79 characters)
Line 139:80: E501 line too long (88 > 79 characters)
Line 140:37: E128 continuation line under-indented for visual indent
Line 141:37: E128 continuation line under-indented for visual indent
Line 146:80: E501 line too long (148 > 79 characters)
Line 148:80: E501 line too long (80 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/file_utils.py !

In the file src/main/python/utils/gevent_helper.py, following                are the PEP8 issues :

Line 49:30: E261 at least two spaces before inline comment
Line 49:31: E262 inline comment should start with '# '

In the file src/main/python/utils/plotter.py, following                are the PEP8 issues :

Line 4:1: E302 expected 2 blank lines, found 1

There are no PEP8 issues in the file src/main/python/utils/session_helper.py !

There are no PEP8 issues in the file src/test/python/test/utils/test_dataset_helper.py !

There are no PEP8 issues in the file src/test/python/test/utils/test_dave_engine.py !

-Added GEVENT library for sending data to client
-Added Dave_Logger as Logging library wrapper and also send logs to client via gevent
-Modified client for subscribing server messages
-Cleaned unused code and refactored some client an server code
-Added loading dialogs to client
-Prepared tests
-Solved some pep8 styles issues

Hello @ricardovb! Thanks for updating the PR.

In the file src/main/python/model/dataset.py, following                are the PEP8 issues :

Line 6:1: E302 expected 2 blank lines, found 1
Line 52:13: E211 whitespace before '('
Line 81:121: E501 line too long (144 > 120 characters)
Line 114:121: E501 line too long (146 > 120 characters)
Line 157:121: E501 line too long (139 > 120 characters)

In the file src/main/python/model/table.py, following                are the PEP8 issues :

Line 45:121: E501 line too long (156 > 120 characters)

In the file src/main/python/server.py, following                are the PEP8 issues :

Line 53:13: E128 continuation line under-indented for visual indent
Line 59:13: E128 continuation line under-indented for visual indent

There are no PEP8 issues in the file src/main/python/utils/dataset_cache.py !

In the file src/main/python/utils/dataset_helper.py, following                are the PEP8 issues :

Line 9:1: E265 block comment should start with '# '
Line 45:43: E261 at least two spaces before inline comment
Line 45:44: E262 inline comment should start with '# '

There are no PEP8 issues in the file src/main/python/utils/dave_endpoint.py !

There are no PEP8 issues in the file src/main/python/utils/dave_engine.py !

There are no PEP8 issues in the file src/main/python/utils/dave_logger.py !

In the file src/main/python/utils/dave_reader.py, following                are the PEP8 issues :

Line 46:9: E265 block comment should start with '# '
Line 50:44: E128 continuation line under-indented for visual indent
Line 51:44: E128 continuation line under-indented for visual indent
Line 140:37: E128 continuation line under-indented for visual indent
Line 141:37: E128 continuation line under-indented for visual indent
Line 146:121: E501 line too long (148 > 120 characters)

There are no PEP8 issues in the file src/main/python/utils/file_utils.py !

In the file src/main/python/utils/gevent_helper.py, following                are the PEP8 issues :

Line 45:1: E302 expected 2 blank lines, found 1
Line 54:30: E261 at least two spaces before inline comment
Line 54:31: E262 inline comment should start with '# '

In the file src/main/python/utils/plotter.py, following                are the PEP8 issues :

Line 4:1: E302 expected 2 blank lines, found 1

There are no PEP8 issues in the file src/main/python/utils/session_helper.py !

There are no PEP8 issues in the file src/test/python/test/utils/test_dataset_helper.py !

There are no PEP8 issues in the file src/test/python/test/utils/test_dave_engine.py !

Hello @ricardovb! Thanks for updating the PR.

In the file src/main/python/model/dataset.py, following                are the PEP8 issues :

Line 47:80: E501 line too long (110 > 79 characters)
Line 49:80: E501 line too long (84 > 79 characters)
Line 58:80: E501 line too long (86 > 79 characters)
Line 76:80: E501 line too long (94 > 79 characters)
Line 119:29: E128 continuation line under-indented for visual indent
Line 120:29: E128 continuation line under-indented for visual indent
Line 145:80: E501 line too long (104 > 79 characters)
Line 149:80: E501 line too long (90 > 79 characters)
Line 150:80: E501 line too long (86 > 79 characters)
Line 161:80: E501 line too long (94 > 79 characters)
Line 163:21: E128 continuation line under-indented for visual indent
Line 163:30: E251 unexpected spaces around keyword / parameter equals
Line 163:32: E251 unexpected spaces around keyword / parameter equals
Line 164:21: E128 continuation line under-indented for visual indent
Line 164:27: E251 unexpected spaces around keyword / parameter equals
Line 164:29: E251 unexpected spaces around keyword / parameter equals
Line 164:80: E501 line too long (83 > 79 characters)
Line 165:21: E128 continuation line under-indented for visual indent
Line 167:13: E128 continuation line under-indented for visual indent
Line 168:17: E128 continuation line under-indented for visual indent
Line 170:5: E122 continuation line missing indentation or outdented
Line 171:1: E901 TokenError: EOF in multi-line statement

In the file src/main/python/model/table.py, following                are the PEP8 issues :

Line 46:41: E127 continuation line over-indented for visual indent
Line 46:80: E501 line too long (80 > 79 characters)
Line 47:80: E501 line too long (85 > 79 characters)

In the file src/main/python/server.py, following                are the PEP8 issues :

Line 47:80: E501 line too long (84 > 79 characters)
Line 53:13: E128 continuation line under-indented for visual indent
Line 53:80: E501 line too long (82 > 79 characters)
Line 58:80: E501 line too long (110 > 79 characters)
Line 59:13: E128 continuation line under-indented for visual indent
Line 98:80: E501 line too long (88 > 79 characters)
Line 103:80: E501 line too long (83 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/dataset_cache.py !

In the file src/main/python/utils/dataset_helper.py, following                are the PEP8 issues :

Line 13:80: E501 line too long (81 > 79 characters)
Line 14:80: E501 line too long (90 > 79 characters)
Line 45:43: E261 at least two spaces before inline comment
Line 45:44: E262 inline comment should start with '# '
Line 45:80: E501 line too long (111 > 79 characters)

In the file src/main/python/utils/dave_endpoint.py, following                are the PEP8 issues :

Line 102:80: E501 line too long (89 > 79 characters)

In the file src/main/python/utils/dave_engine.py, following                are the PEP8 issues :

Line 113:80: E501 line too long (82 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/dave_logger.py !

In the file src/main/python/utils/dave_reader.py, following                are the PEP8 issues :

Line 46:9: E265 block comment should start with '# '
Line 50:44: E128 continuation line under-indented for visual indent
Line 51:44: E128 continuation line under-indented for visual indent
Line 92:80: E501 line too long (92 > 79 characters)
Line 139:80: E501 line too long (88 > 79 characters)
Line 140:37: E128 continuation line under-indented for visual indent
Line 141:37: E128 continuation line under-indented for visual indent
Line 146:80: E501 line too long (99 > 79 characters)
Line 147:80: E501 line too long (96 > 79 characters)
Line 149:80: E501 line too long (80 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/file_utils.py !

There are no PEP8 issues in the file src/main/python/utils/gevent_helper.py !

There are no PEP8 issues in the file src/main/python/utils/plotter.py !

There are no PEP8 issues in the file src/main/python/utils/session_helper.py !

There are no PEP8 issues in the file src/test/python/test/utils/test_dataset_helper.py !

There are no PEP8 issues in the file src/test/python/test/utils/test_dave_engine.py !

Hello @ricardovb! Thanks for updating the PR.

In the file src/main/python/model/dataset.py, following                are the PEP8 issues :

Line 47:80: E501 line too long (110 > 79 characters)
Line 49:80: E501 line too long (84 > 79 characters)
Line 58:80: E501 line too long (86 > 79 characters)
Line 76:80: E501 line too long (94 > 79 characters)
Line 119:29: E128 continuation line under-indented for visual indent
Line 120:29: E128 continuation line under-indented for visual indent
Line 145:80: E501 line too long (104 > 79 characters)
Line 149:80: E501 line too long (90 > 79 characters)
Line 150:80: E501 line too long (86 > 79 characters)
Line 161:80: E501 line too long (94 > 79 characters)
Line 163:21: E128 continuation line under-indented for visual indent
Line 164:21: E128 continuation line under-indented for visual indent
Line 164:80: E501 line too long (81 > 79 characters)
Line 165:21: E128 continuation line under-indented for visual indent
Line 167:13: E128 continuation line under-indented for visual indent
Line 168:17: E128 continuation line under-indented for visual indent
Line 170:5: E122 continuation line missing indentation or outdented
Line 171:1: E901 TokenError: EOF in multi-line statement

In the file src/main/python/model/table.py, following                are the PEP8 issues :

Line 46:41: E127 continuation line over-indented for visual indent
Line 46:80: E501 line too long (80 > 79 characters)
Line 47:80: E501 line too long (85 > 79 characters)

In the file src/main/python/server.py, following                are the PEP8 issues :

Line 47:80: E501 line too long (84 > 79 characters)
Line 53:13: E128 continuation line under-indented for visual indent
Line 53:80: E501 line too long (82 > 79 characters)
Line 58:80: E501 line too long (110 > 79 characters)
Line 59:13: E128 continuation line under-indented for visual indent
Line 98:80: E501 line too long (88 > 79 characters)
Line 103:80: E501 line too long (83 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/dataset_cache.py !

In the file src/main/python/utils/dataset_helper.py, following                are the PEP8 issues :

Line 13:80: E501 line too long (81 > 79 characters)
Line 14:80: E501 line too long (90 > 79 characters)
Line 45:43: E261 at least two spaces before inline comment
Line 45:44: E262 inline comment should start with '# '
Line 45:80: E501 line too long (111 > 79 characters)

In the file src/main/python/utils/dave_endpoint.py, following                are the PEP8 issues :

Line 102:80: E501 line too long (89 > 79 characters)

In the file src/main/python/utils/dave_engine.py, following                are the PEP8 issues :

Line 113:80: E501 line too long (82 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/dave_logger.py !

In the file src/main/python/utils/dave_reader.py, following                are the PEP8 issues :

Line 46:9: E265 block comment should start with '# '
Line 50:44: E128 continuation line under-indented for visual indent
Line 51:44: E128 continuation line under-indented for visual indent
Line 92:80: E501 line too long (92 > 79 characters)
Line 139:80: E501 line too long (88 > 79 characters)
Line 140:37: E128 continuation line under-indented for visual indent
Line 141:37: E128 continuation line under-indented for visual indent
Line 146:80: E501 line too long (99 > 79 characters)
Line 147:80: E501 line too long (96 > 79 characters)
Line 149:80: E501 line too long (80 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/file_utils.py !

There are no PEP8 issues in the file src/main/python/utils/gevent_helper.py !

There are no PEP8 issues in the file src/main/python/utils/plotter.py !

There are no PEP8 issues in the file src/main/python/utils/session_helper.py !

There are no PEP8 issues in the file src/test/python/test/utils/test_dataset_helper.py !

There are no PEP8 issues in the file src/test/python/test/utils/test_dave_engine.py !

Hello @ricardovb! Thanks for updating the PR.

In the file src/main/python/model/dataset.py, following                are the PEP8 issues :

Line 47:80: E501 line too long (110 > 79 characters)
Line 49:80: E501 line too long (84 > 79 characters)
Line 58:80: E501 line too long (86 > 79 characters)
Line 76:80: E501 line too long (94 > 79 characters)
Line 119:29: E128 continuation line under-indented for visual indent
Line 120:29: E128 continuation line under-indented for visual indent
Line 145:80: E501 line too long (104 > 79 characters)
Line 149:80: E501 line too long (90 > 79 characters)
Line 150:80: E501 line too long (86 > 79 characters)
Line 161:80: E501 line too long (94 > 79 characters)
Line 163:30: E225 missing whitespace around operator
Line 164:27: E225 missing whitespace around operator
Line 164:80: E501 line too long (81 > 79 characters)

In the file src/main/python/model/table.py, following                are the PEP8 issues :

Line 46:41: E127 continuation line over-indented for visual indent
Line 46:80: E501 line too long (80 > 79 characters)
Line 47:80: E501 line too long (85 > 79 characters)

In the file src/main/python/server.py, following                are the PEP8 issues :

Line 47:80: E501 line too long (84 > 79 characters)
Line 53:13: E128 continuation line under-indented for visual indent
Line 53:80: E501 line too long (82 > 79 characters)
Line 58:80: E501 line too long (110 > 79 characters)
Line 59:13: E128 continuation line under-indented for visual indent
Line 98:80: E501 line too long (88 > 79 characters)
Line 103:80: E501 line too long (83 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/dataset_cache.py !

In the file src/main/python/utils/dataset_helper.py, following                are the PEP8 issues :

Line 13:80: E501 line too long (81 > 79 characters)
Line 14:80: E501 line too long (90 > 79 characters)
Line 45:43: E261 at least two spaces before inline comment
Line 45:44: E262 inline comment should start with '# '
Line 45:80: E501 line too long (111 > 79 characters)

In the file src/main/python/utils/dave_endpoint.py, following                are the PEP8 issues :

Line 102:80: E501 line too long (89 > 79 characters)

In the file src/main/python/utils/dave_engine.py, following                are the PEP8 issues :

Line 113:80: E501 line too long (82 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/dave_logger.py !

In the file src/main/python/utils/dave_reader.py, following                are the PEP8 issues :

Line 46:9: E265 block comment should start with '# '
Line 50:44: E128 continuation line under-indented for visual indent
Line 51:44: E128 continuation line under-indented for visual indent
Line 92:80: E501 line too long (92 > 79 characters)
Line 139:80: E501 line too long (88 > 79 characters)
Line 140:37: E128 continuation line under-indented for visual indent
Line 141:37: E128 continuation line under-indented for visual indent
Line 146:80: E501 line too long (99 > 79 characters)
Line 147:80: E501 line too long (96 > 79 characters)
Line 149:80: E501 line too long (80 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/file_utils.py !

There are no PEP8 issues in the file src/main/python/utils/gevent_helper.py !

There are no PEP8 issues in the file src/main/python/utils/plotter.py !

There are no PEP8 issues in the file src/main/python/utils/session_helper.py !

There are no PEP8 issues in the file src/test/python/test/utils/test_dataset_helper.py !

There are no PEP8 issues in the file src/test/python/test/utils/test_dave_engine.py !

Hello @ricardovb! Thanks for updating the PR.

In the file src/main/python/model/dataset.py, following                are the PEP8 issues :

Line 47:80: E501 line too long (110 > 79 characters)
Line 49:80: E501 line too long (84 > 79 characters)
Line 58:80: E501 line too long (86 > 79 characters)
Line 76:80: E501 line too long (94 > 79 characters)
Line 119:29: E128 continuation line under-indented for visual indent
Line 120:29: E128 continuation line under-indented for visual indent
Line 145:80: E501 line too long (104 > 79 characters)
Line 149:80: E501 line too long (90 > 79 characters)
Line 150:80: E501 line too long (86 > 79 characters)
Line 161:80: E501 line too long (92 > 79 characters)
Line 163:30: E225 missing whitespace around operator
Line 164:27: E225 missing whitespace around operator

In the file src/main/python/model/table.py, following                are the PEP8 issues :

Line 46:41: E127 continuation line over-indented for visual indent
Line 46:80: E501 line too long (80 > 79 characters)
Line 47:80: E501 line too long (85 > 79 characters)

In the file src/main/python/server.py, following                are the PEP8 issues :

Line 47:80: E501 line too long (84 > 79 characters)
Line 53:13: E128 continuation line under-indented for visual indent
Line 53:80: E501 line too long (82 > 79 characters)
Line 58:80: E501 line too long (110 > 79 characters)
Line 59:13: E128 continuation line under-indented for visual indent
Line 99:80: E501 line too long (88 > 79 characters)
Line 104:80: E501 line too long (98 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/dataset_cache.py !

In the file src/main/python/utils/dataset_helper.py, following                are the PEP8 issues :

Line 13:80: E501 line too long (81 > 79 characters)
Line 14:80: E501 line too long (90 > 79 characters)
Line 45:43: E261 at least two spaces before inline comment
Line 45:44: E262 inline comment should start with '# '
Line 45:80: E501 line too long (111 > 79 characters)

In the file src/main/python/utils/dave_endpoint.py, following                are the PEP8 issues :

Line 102:80: E501 line too long (89 > 79 characters)

In the file src/main/python/utils/dave_engine.py, following                are the PEP8 issues :

Line 113:80: E501 line too long (82 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/dave_logger.py !

In the file src/main/python/utils/dave_reader.py, following                are the PEP8 issues :

Line 46:9: E265 block comment should start with '# '
Line 50:44: E128 continuation line under-indented for visual indent
Line 51:44: E128 continuation line under-indented for visual indent
Line 92:80: E501 line too long (92 > 79 characters)
Line 139:80: E501 line too long (88 > 79 characters)
Line 140:37: E128 continuation line under-indented for visual indent
Line 141:37: E128 continuation line under-indented for visual indent
Line 146:80: E501 line too long (99 > 79 characters)
Line 147:80: E501 line too long (96 > 79 characters)
Line 149:80: E501 line too long (80 > 79 characters)

There are no PEP8 issues in the file src/main/python/utils/file_utils.py !

There are no PEP8 issues in the file src/main/python/utils/gevent_helper.py !

There are no PEP8 issues in the file src/main/python/utils/plotter.py !

There are no PEP8 issues in the file src/main/python/utils/session_helper.py !

There are no PEP8 issues in the file src/test/python/test/utils/test_dataset_helper.py !

There are no PEP8 issues in the file src/test/python/test/utils/test_dave_engine.py !