Smart-Marker: cursor stops AFTER the marker. Not ON the marker

Reapere 7.15
SWS 2.12.1
by using the smart-markers to investigate an issue an user highlighted, I noticed that
if I use smartmarkers,the cursor executes them AFTER (well after) the marker and not ON the marker
Here the !1008 (Pause). Note that the cursor came to the stopAFTER the marker and not ON the marker
Underneath another screenshot.
I set the marker up with the action 10157 it means "insert marker"
When the cursor passed, created the marker 4 ... see the distance ...

Action makers are not sample accurate. SWS checks 30 times per second (nominal, can be slower!) if playback crossed an action marker.
There is no way for a REAPER extension or ReaScript to schedule something to occur at an exact time position.

Action makers are not sample accurate. SWS checks 30 times per second (nominal, can be slower!) if playback crossed an action marker.
There is no way for a REAPER extension or ReaScript to schedule something to occur at an exact time position.

SWS 2.12.1

By the way this version is 3 years out of date. The latest is 2.14 which is available from ReaPack or here.

Ok so we can't get better but the difference is very small (negligible) then.

Action makers are not sample accurate. SWS checks 30 times per second (nominal, can be slower!) if playback crossed an action marker.
There is no way for a REAPER extension or ReaScript to schedule something to occur at an exact time position.

SWS 2.12.1

By the way this version is 3 years out of date. The latest is 2.14 which is available from ReaPack or here.

Another thing: I did install SWS via ReaPack when it was available this feature, to try it. I update ReaPack several times in these few dasy: Why didn't it update also SWS?

Why didn't it update also SWS?

Only v2.14 is in ReaPack, so if you installed it from there (ReaPack > Browse packages > SWS > Install), you already got 2.14.

Its a shame this can't be fixed. I had a string of videos in Reaper using the pause markers but as it went down the timeline it gets more out of sync. Oh and I was using it also to control FLstudio which was controlling DMX lighting. The first three videos would play perfect the lights we in sync but as we got to the 4th video and on, it became more out of sync...sadly. Now Flstudio has pause markers, they do stop right on the money but they also will occasionally skip the marker not good for a live situation.  I ended up removing the pause markers from my set. Not what I wanted to do but was my only choice as of now.


High memory usage after plugin installation

Hello,
We have just installed this plugin version 1.11.0 by extending the kibana docker image :
FROM docker.elastic.co/kibana/kibana:7.5.1
RUN ./bin/kibana-plugin install https://github.com/fbaligand/kibana-enhanced-table/releases/download/v1.11.0/enhanced-table-1.11.0_7.5.1.zip
The creation of the docker image is fine and I see the new enhanced table visualization in our Kibana installation but I needed to increase container memory from 1Gb to 4Gb.
What could be the reason for the high memory usage?
Thanks,

Hi,
Well, first, I'm very very surprised by this big raise of your memory. 1 Gb to 4 Gb, it's a huge difference.
Then, I don't see how "enhanced table" can cause such a server memory consumption, because "enhanced table" has no server code. All plugin code is executed on front-end.
So the memory should be consumed on your browser.
Maybe the recompilation of Kibana core code?

Given that question is answered, I close the issue.


fcns of arrays

I'd like to be able to use boot with array data, not just vectors, something like:
dat = randn(5000, 3) #observations by row
muhat = mean(dat, 1)
f(boot_sample) = norm(mean(boot_sample) - muhat)

boot(dat, f, 100)

Unfortunately, boot is only defined for data which is an abstract vector.  Is there a fast way to change my data to a vector of vectors?  Would ideally want to do it "in place" to save on the memory, too.
Even better, it feels like this sort of functionality should be generically supported by the package, somehow...  Thoughts?

This will take longer than I expected since I have to address some namespace issues first.

@vgupta1 I add support for multi-dimensional arrays for the basic bootstrap, see the commit 717647f66bf39149dbb98497750602bafdc5190c. You can give it a first test, e.g.
dat = randn(100, 3)
mu_hat = mean(dat, 1)
fun_array(x::AbstractArray) = norm(mean(x) - mu_hat)

bs1 = boot_basic(dat, fun_array, nSamples)
ci_bs1 = ci_perc(bs1)

Let me know if this behaves as expected. I'll add support for the other bootstrap methods soon.

Thanks, Julian.  I'll find time to take a careful look soon.  At first
glance though, it looks like this implementation does a memory alloc every
iteration for the bootstrap indices.  (similar ot my last PR for the
unidimensional case).  It'd be nicer to reuse the same memory space each
iteration, if at all possible.  I can also tackle this myself when I look
at it if you prefer.
VG
On Fri Jan 09 2015 at 9:40:13 AM Julian Gehring<EMAIL_ADDRESS>wrote:

@vgupta1 https://github.com/vgupta1 I add support for multi-dimensional
arrays for the basic bootstrap, see the commit 717647f
https://github.com/julian-gehring/Bootstrap.jl/commit/717647f66bf39149dbb98497750602bafdc5190c.
You can give it a first test, e.g.
dat = randn(100, 3)
mu_hat = mean(dat, 1)fun_array(x::AbstractArray) = norm(mean(x) - mu_hat)
bs1 = boot_basic(dat, fun_array, nSamples)
ci_bs1 = ci_perc(bs1)
Let me know if this behaves as expected. I'll add support for the other
bootstrap methods soon.
—
Reply to this email directly or view it on GitHub
https://github.com/julian-gehring/Bootstrap.jl/issues/2#issuecomment-69369035
.

I'll optimize this in any way, the current implementation has room for improvement. At the moment, it would be good to know if it is sufficient for the analysis you have in mind.

To clarify, I mean if the interface and functionality works for you. I would like to make sure, it behaves for Arrays the way it should. Then I can go ahead, add support for the other methods, together with optimizations of the code.

Understood.  I'll take a look ASAP.
VG
On Fri Jan 09 2015 at 11:04:24 AM Julian Gehring<EMAIL_ADDRESS>wrote:

To clarify, I mean if the interface and functionality works for you. I
would like to make sure, it behaves for Arrays the way it should. Then I
can go ahead, add support for the other methods, together with
optimizations of the code.
—
Reply to this email directly or view it on GitHub
https://github.com/julian-gehring/Bootstrap.jl/issues/2#issuecomment-69381862
.

Hi Julian
This works exactly as I'd expect, thanks!
As a side note: I did a rough speed comparison to a knocked-up version i
have that avoids the copy, and the speed difference is substantial in this
multidimensional case.
Vishal
On Fri Jan 09 2015 at 11:06:20 AM Vishal Gupta<EMAIL_ADDRESS>wrote:

Understood.  I'll take a look ASAP.
VG
On Fri Jan 09 2015 at 11:04:24 AM Julian Gehring<EMAIL_ADDRESS>wrote:

To clarify, I mean if the interface and functionality works for you. I
would like to make sure, it behaves for Arrays the way it should. Then I
can go ahead, add support for the other methods, together with
optimizations of the code.
—
Reply to this email directly or view it on GitHub
https://github.com/julian-gehring/Bootstrap.jl/issues/2#issuecomment-69381862
.

Thanks for checking, it's always good to have a second pair of eyes looking at it.
968af5dcc2675333544b555125d017af98a9e9cb has an improved version of the basic bootstrap for arrays, which does a inplace sampling of the index variable. This decreases the memory allocation and makes for a slightly better runtime. However, the main bottleneck is slicedimoperation on the array. I'll look into this. If you have a smart idea about this...

86e764e88e1a2f8cb44f901f02ba87a15a3bcdbf has two boot_basic implementations with a low-memory footprint: boot_basic_lm and boot_basic_lm2, both are not exported. For large arrays, the memory usage is reduced by orders of magnitude, with an increase of runtime of about a factor of 2 (at least for my test cases).

With da7ad8a2be44f4ed00f763e9279549078b696755, all bootstrap methods support multi-dimensional arrays. I'll add memory optimized versions as part of a general refractoring soon.


[WIP] Add possibility to parameterize S3 service URL

Just a minor thing, related to #136
I didn't found contribution guides, so this is potentially draft PR.
Nevertheless, WDYT about the possibility to support non-AWS S3 deployments?
Re the PR: what else should be added?
P.S. Thank you folks for an awesome lib 👍

Happy to take this change! A few questions:

Can we add some notes to the docs about Min.IO and other S3 compatible object stores so that people can find it? Maybe at the end of the authentication path
Can we make a similar note in the docstring for the endpoint param?
I don't think we need additional mocked tests, but we may want a live server config to do this. Is there a min.io test server or hosted version with a free tier we could get creds for the test suite to access?

The notes are added here: 258392b
And the custom S3 rig here: 02f7a8c
Hope I get what you meant properly.


Problem building 1.0.1

sudo docker build -t weaveworks/weaveexec prog/weaveexec
Sending build context to Docker daemon 25.32 MB
Sending build context to Docker daemon
Step 0 : FROM gliderlabs/alpine
 ---> 5bd56d818842
Step 1 : MAINTAINER Weaveworks Inc<EMAIL_ADDRESS> ---> Using cache
 ---> 7304b5c73715
Step 2 : RUN apk add --update     curl     ethtool     iptables     iproute2     util-linux     conntrack-tools   && rm -rf /var/cache/apk/*
 ---> Running in 311e72369b2a
fetch http://dl-4.alpinelinux.org/alpine/v3.2/main/x86_64/APKINDEX.tar.gz
ERROR: http://dl-4.alpinelinux.org/alpine/v3.2/main: IO ERROR
WARNING: Ignoring APKINDEX.abd86498.tar.gz: No such file or directory
ERROR: unsatisfiable constraints:
  conntrack-tools (missing):
    required by: world[conntrack-tools]
  curl (missing):
    required by: world[curl]
  ethtool (missing):
    required by: world[ethtool]
  iproute2 (missing):
    required by: world[iproute2]
  iptables (missing):
    required by: world[iptables]
  util-linux (missing):
    required by: world[util-linux]
INFO[0000] The command [/bin/sh -c apk add --update     curl     ethtool     iptables     iproute2     util-linux     conntrack-tools   && rm -rf /var/cache/apk/*] returned a non-zero code: 6
Makefile:78: recipe for target 'weaveexec.tar' failed

That just looks like a transient issue with the alpinelinux repo. or some network issue at your end. works fine for me.

Yes, I think my Docker networking must have got screwed up through two Ubuntu updates

Seems I need --net=host on the docker command line

That's odd.

Hmm, --net=host doesn't work with docker build.

Someone else has seen it: https://github.com/kitematic/kitematic/issues/651

This could be a DNS issue. etc/resolv.conf in Alpine seems to be <IP_ADDRESS> and perhaps my ISP is blocking that

I needed to add
DOCKER_OPTS="--dns <IP_ADDRESS>"

to /etc/default/docker


Relative imports do not work in custom webterm commands

Describe the bug
This is not an important bug, just thought I would include, especially for anyone else who is trying to figure it out!
Relative imports from the index.js file of a custom webterm command do not function and return a TypeError: Cannot read property 'yourCustomCommand' of undefined when installed. Absolute imports work file with the full 'hyper://xxx.." work fine.
To Reproduce
Steps to reproduce the behavior:

Create a webterm command in a 'index.js' file
Create a 'test.js' that exports a single constant
Import said constant in index.js import {x} from "./test.js"
Attempt to install command
See error
Note that if you change import to "hyper://xxx/test.js" it works fine.

Expected behavior
Either have relative imports succeed as expected, or fail with a more descriptive error message, telling user to use absolute paths.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Ubuntu
Browser: Beaker
Version: beta 2

Additional context
Nope! Again, not a major issue at all!

Thanks for reporting, I'll check into it

Okay fixed


Srollbar elements in the way of styling a layout

I'm a bit confused as to how I can make a Layout fill its parent block.  My component hierarchy is like <Layout><LayoutHeader>...</LayoutHeader><Flex>...</Flex></Layout>.
I have set min-height: 100vh on the outermost element generated by the layout (.thaw-layout), and FF inspector shows it has expected height.  But then the flex element deep within all 3 levels of thaw-scrollbar* elements just takes the minimum height for its contents.  It seems really clunky to compute a  min-height for the Flex by finding out the header height to substracting it from 100vh, so I may be missing something.
I'm also not very sure of what those thaw-scrollbar* elements brings over standard CSS scroll stuff.
Still with FF inspector, I can get the result I want by:

removing those 3 layers of scrollbar elements
setting display: flex; flex-direction: column on the .thaw-layout
setting flex:1 on the thaw-flex

This seems to confirm the source of the difficulty lies in the presence of those scrollbar elements.  How can we improve the situation?

You can use content_style or content_class to solve this problem. For example:
<Layout content_style="min-height: 100vh; display: flex; flex-direction: column">
      <LayoutHeader>"…"</LayoutHeader>
      <Flex style="flex: 1">"…"</Flex>
</Layout>

or
<Layout content_class="...">
      <LayoutHeader>"…"</LayoutHeader>
      <Flex class="...">"…"</Flex>
</Layout>

That's perfect, thanks much!


Add the description about the logical OR operator of label selector

Description
From the beginning of libcalico-go [1], || operator can be used
for label selector. It is also tested since then [2]. Add the description
of it.
[1] https://github.com/projectcalico/libcalico-go/commit/edacd2825053476830a832969c526e29fd350091#diff-e89ca2c7d45afb10e9b6ea966a13ab80R36
[2] https://github.com/projectcalico/libcalico-go/commit/edacd2825053476830a832969c526e29fd350091#diff-4b722fc8108b1054cf799bcc9d2bb615R52

the type of fix

bug fix

some details on why this PR should be merged

the || operator is very convenient for selecting labels

the details of the testing you've done on it (both manual and automated)

Follow the official workflow.
https://github.com/projectcalico/calico/blob/master/CONTRIBUTING_DOCS.md#building-the-doc-site-locally

which components are affected by this PR

Document about label selector

links to issues that this PR addresses
-->

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note
None required

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Deploy preview for calico ready!
Built with commit f2b3e494ca513454166808d27dd05056e77d78c4
https://deploy-preview-2722--calico.netlify.com


Validate signature on public/readonly instance (ref #29, #32)

Ref #32
Do not skip any collection if signer is not enabled and no info about signing resources can be obtained

What? Do we know if the lambda runs against the public endpoint or the writer?

What? Do we know if the lambda runs against the public endpoint or the writer?

It runs on the reader apparently:
https://github.com/mozilla-services/cloudops-deployment/blob/dc72e8241f5f721e49c054c8726a4fc4a7089b61/projects/kinto-lambda/ansible/playbooks/refresh_signature_lambda.yml#L15
https://github.com/mozilla-services/cloudops-deployment/blob/dc72e8241f5f721e49c054c8726a4fc4a7089b61/projects/kinto-lambda/ansible/playbooks/validate_signature_lambda.yml#L15

Sorry, I got turned around and thought this was adding another reason why we would skip a collection, rather than removing one. Either way is fine. If you want to go with this solution, maybe add a note explicitly explaining the situation why we would validate signatures on even though kinto-signer capability isn't there (because it's a readonly clone I guess).

I think I prefer to remove this and go with something like a fix for #31


Test 4

Description
This should be added to the db
Goals

[ ] Get Detected

Expected Outcome
Detection
Acceptance Criteria

[ ] Detection

Implementation Details
[List any technical details about the proposed implementation, including any specific technologies that will be used.]
Mockups / Wireframes
[Include links to any visual aids, mockups, wireframes, or diagrams that help illustrate what the final product should look like. This is not always necessary, but can be very helpful in many cases.]

Project
Testing
Organization Name:
Samagra
Domain
Something
Tech Skills Needed:
Some, Others
Mentor(s)
@KDwevedi
Complexity
Low
Category
Test, Feature
Sub Category
Database, Breaking Change

Hello

Hello 3

Hello 4

Hello 5

Hello 7

Hello 8

HEllo 9


Switching role sometimes results in a 400 or 404

Hi,
Firstly, thank you for such a great extension and for fixing the issues with the new AWS UI so quickly!
Perhaps this should be raised as two separate issues but they are very similar so I think they're related. I've noticed that sometimes when switching role I get a 400 Bad Request or a 404 Not Found.
This was happening before the recent switch to v2, I've only just looked further into why it was happening.
400 Example
In this example, I am on the S3 console page (https://s3.console.aws.amazon.com/s3/home?region=us-east-1) and I am switching to a role that has the region set to eu-central-1.
I compared a broken and working request to https://signin.aws.amazon.com/switchrole and noticed that in the form data on the broken request the redirect_uri was different
Broken: https%3A%2F%2Feu-central-1.s3.console.aws.amazon.com%2Fs3%2Fhome%3Fregion%3Deu-central-1
Working: https%3A%2F%2Fs3.console.aws.amazon.com%2Fs3%2Fhome%3Fregion%3Dus-east-1%23
The region hasn't changed as the normal AWS console doesn't take the region switching into account, however I tested using curl with changed the request_uri and I got a working 302 response
Working with Region change: https%253A%252F%252Fs3.console.aws.amazon.com%252Fs3%252Fhome%253Fregion%253Deu-central-1
404 Example
In this example, I am on the IAM Roles page (https://console.aws.amazon.com/iam/home?region=eu-central-1#/roles) using the role that has the region set to eu-central-1 and I am switching to the role that has the region set to us-east-1. This results in a 404 on https://aws.amazon.com/iam/home/?region=us-east-1#/roles
In this scenario the /switchrole endpoint returns a 302, which sends me to https://aws.amazon.com/iam/home?region=us-east-1 which returns a 301 which then sends me on to the 404 URI above.
Again, comparing the broken and working requests to the /switchrole endpoint the redirect_uri was different
Broken: https%3A%2F%2Faws.amazon.com%2Fiam%2Fhome%3Fregion%3Dus-east-1%23%2Froles
Working: https%3A%2F%2Fconsole.aws.amazon.com%2Fiam%2Fhome%3Fregion%3Dus-east-1%23
Testing again with curl but adjusting the request_uri to add the region change I got a 200 response after following the redirects as above.
Working with Region change: https%3A%2F%2Fconsole.aws.amazon.com%2Fiam%2Fhome%3Fregion%3Dus-east-1%2523%252Froles

Unfortunately, I wouldn't know where to start with fixing this change myself 😞  But hopefully the above gives you enough information. However, if you need more information or have any questions let me know 👍
Thanks again!

Realised that I didn't say which browser I'm using 🤦  I'm using Brave Version 1.14.84 Chromium: 85.0.4183.121 (Official Build) (64-bit), however, I see the same behaviour in Chrome Version 85.0.4183.121 (Official Build) (64-bit)

This issue occurs when viewing some AWS global services.

I'm still getting the 400 error while switching roles from the CodeArtifact service (region eu-central-1).
I'm on Firefox 81.0.1

Hello @th3noname , @tilfin, @phr3nzii : I discovered that one reason (certainly one out of many) for the 404 can be caused by the length of the "DisplayName" parameter for the account (in the switchrole HTTP call).
In my case, I had not checked the "Hide Account Id" checkbox. Thus, the DisplayName is constructed by the concatenation of the name of the profile + "  |  " + account_id (the later part adds 17 characters to the display name).
My profile names are "quite long".
If the whole string length is > 64 characters, then I always have a 404 page.
As soon as I reduce the size of the profile name, so that the whole DisplayName is <= 64 characters, the 404 page disappears. (Of course another solution is to check the "Hide Account Id" checkbox)
(And when using aws web console, there is a forced truncation by the interface so that DisplayName is not > 64 chars)
Could it be that you are also impacted by this ?

The display names I have are < 64 characters. 2.0.5 resolved this issue for me, I haven't had any 400 or 404 errors since

I get 400 when the redirect_uri parameter is complicated, such as the CodePipeline "Pipelines" page which has URIs like https://ap-southeast-2.console.aws.amazon.com/codesuite/codepipeline/pipelines?region=ap-southeast-2&pipelines-meta=<long URI-encoded JSON>. When that happens, navigating to a page with a simpler URI (like the CodePipeline "Getting started" page) allows me to switch the role.
It's not clear whether it's the encoded JSON {/"/} characters that's causing the issue or the URI length, but it seems possible to switch roles using the AWS console's builtin role history on those pages.


feat: add support for BatchMsg in sequenceMsg

#415 added new Sequence command. This command should run the passed commands in order. However it doesn't take Batch command into account.

@meowgorithm what do you think about this? Something that could be considered?

@stoffeastrom Yep, absolutely. Thanks for raising this issue?

@meowgorithm Great, Did a PR but not sure if I need to do anymore except waiting for you guys to 👀 on it :D


Unit test updates.

Fixed deprecation warnings (future failures) related to using async and "done" callbacks together in Jasmine. For async tests, I removed the Jasmine "done" callback and used promises for callback completion signaling. Removed deprecated argument from done callbacks for non-async tests.

I'm not sure how to interpret the -0.0% coverage decrease.

okay master branch is updated with the linting config - merge or rebase into yours and you'll get the results from CI or via npm run lint locally

Thanks for the lint configs. I had some trouble rebasing from master and that's the reason for the manual "merge" commits into the branch. I'll squash the commits when you feel they are ready.

@steve-bate thanks for the update. Working through reviewing all the changes. This was a massive amount of work you've contributed and I really appreciate it


Add route to connect to database

I added routes! Pretty simple.
Next up: Integrate Jest and enzyme

This is what the client looks like right now!


Non-descriptive error when encountering a typeclass mismatch

Example code
The problem here is that the user is trying to define a Set of items which are not comparable. This is of course not allowed. However, the error message given does not provide any indication of that.
The right side of (|>) is causing a type mismatch.
(|>) is expecting the right side to be a:

Json.Decoder (List (List Selection)) -> a

But the right side is:

Json.Decoder (List (List Selection)) -> Json.Decoder (Set (List Selection))

Hint: With operators like (|>) I always check the left side first. If it seems
fine, I assume it is correct and check the right side. So the problem may be in
how the left and right arguments interact.

According to the error message the code appears to be correct.

I think this would be a better fit for https://github.com/elm-lang/error-message-catalog
Do you mind retargeting it there?
And can you put the code directly in the issue? If I'm changing the compiler I cannot test it in Ellie.


dev/root 100% and no access to homebridge

Hi,
After several months of use the homebbridge on PI with apple homekit it stops responding and i found that the pi memory is full. PI is used only for homebridge to control my cbus lighting with homekit. It seems that each time when i select to do something it write something somewhere so after several months it full the memory. I know that my sd card is only 8gb but i had about 3gb emty when i set it up. Can i clear any cache or temp folder? is there any specific folder that all commands are stored?
thanks in advance
Filesystem      Size  Used Avail Use% Mounted on
/dev/root       5.6G  5.4G     0 100% /
devtmpfs        458M     0  458M   0% /dev
tmpfs           462M     0  462M   0% /dev/shm
tmpfs           462M   12M  450M   3% /run
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           462M     0  462M   0% /sys/fs/cgroup
/dev/mmcblk0p6   65M   22M   43M  34% /boot
tmpfs            93M     0   93M   0% /run/user/109
tmpfs            93M     0   93M   0% /run/user/1000

Can you share how are you running homebridge? Depends on the setup, the log might live in system journal, a log file, or some random place...

Can you share how are you running homebridge? Depends on the setup, the log might live in system journal, a log file, or some random place...

hmmm... homebridge is running as systemctl if this is what you mean. can i find somewhere a log or a config file to help you understant better?
thanks

You can try https://unix.stackexchange.com/questions/139513/how-to-clear-journalctl
Or if you can link me the systemd unit file I can take a look too.
Sent from my iPhone

On Apr 5, 2019, at 10:07 AM, discjockeyr<EMAIL_ADDRESS>wrote:
Can you share how are you running homebridge? Depends on the setup, the log might live in system journal, a log file, or some random place...
hmmm... homebridge is running as systemctl if this is what you mean. can i find somewhere a log or a config file to help you understant better?
thanks
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

KhaosT thanks again for your reply. Unfortunately i am not familiar enough with linux. i have follow several instractions to set it up so i am trying to understant what you are trying to explain me.
Fro the link i did not manage to find any solution.
When you said to sent you the systemd unit file you mean the file that i found on /lib/systemd/systemd ?

Try run journalctl --vacuum-time=2d in terminal I mean.
Do you remember which instruction you end up using for start homebridge on boot?

Below are the commands that i end up to run the service
systemctl daemon-reload
systemctl enable homebridge
systemctl start homebridge

@discjockeyr with that journalctl command should work... have you tried that?

Vacuuming done, freed 0B of archived journals from /run/log/journal/fe0d289b0919                                     413d970ec4768e111cd8.
but the root is still at 100%

@discjockeyr Let's try sudo du -a / 2>/dev/null | sort -n -r | head -n 20 to find the biggest file then...

this is what i get
sort: write failed: /tmp/sortHFIJU5: No space left on device

Okay ... let's try rm -rf /var/cache/apt/archives and then run the sudo du -a / 2>/dev/null | sort -n -r | head -n 20

still no space left error

😞 That's annoying... two things you can try I guess
First one:
cd /
sudo du -cks *

and then manually find the biggest folder and recursively run it.
Second one:
sudo du / 2>/dev/null
and then copy the result to your computer, then run "sort -n -r | head -n 20" manually

6928    bin
22498   boot
46528   cgate
0       dev
5824    etc
913116  home
188552  lib
16      lost+found
16      media
4       mnt
989000  opt
du: cannot access 'proc/5364/task/5364/fd/3': No such file or directory
du: cannot access 'proc/5364/task/5364/fdinfo/3': No such file or directory
du: cannot access 'proc/5364/fd/3': No such file or directory
du: cannot access 'proc/5364/fdinfo/3': No such file or directory
0       proc
20984   root
du: cannot access 'run/user/109/gvfs': Permission denied
47728   run
7520    sbin
972     ser2sock
4       srv
0       sys
72      tmp
2928112 usr
417240  var
5595114 total

Looks like something in /usr is really big...
I figured out a way to run the sort with not enough space. You can run this from your computer, it should pipe the result back (file list), and then sort on your computer so we wont run into issue like no space...
ssh pi@YOUR_RASPBERRYPI_ip "sudo du -a / 2>/dev/null" | sort -nr | head -40

KhaosT i apreciate too much your help and thank you.
from where i can run this command? whitout connect to putty?

Ah... you are using windows... Any chance you have Windows Subsystem for Linux configured?
If not, I don't have a good solution for you other than manually try running
sudo du -cks /home/*
sudo du -cks /opt/*
sudo du -cks /usr/*
sudo du -cks /var/*

on raspberry pi and see why those folders are so big...

ok KhaosT
i will try it again with sudo commands as i am on windows and not have subsystem for linux.... i will try ti find out what are those big files and let you know. thanks very very much for your time and help.

Hi @discjockeyr,
From https://github.com/nfarina/homebridge/wiki/Basic-Troubleshooting#examine-logs-for-errors, it looks like the log files should be automatically created in these paths:
/var/log/homebridge.log
/var/log/homebridge.err

If you are only running homebridge in your pi, I'd say the log has gone over your space.
Can you check the size of those 2 files by running
sudo ls -lh /var/log/homebridge.*

If they are around the GBs size, you might be able to truncate them by simply running:
sudo su
:> /var/log/homebridge.log
:> /var/log/homebridge.err

hi afharo,
i don't know if this is normal but i cannot find those 2 files in pi
Seems that my homebridge is not in the specific folder, but if i serach any of those 2 files i found nothing.
Something strange it happens. It was working now for some months and now gets fu;;. is clear that all the commands are stored somewhere and full up the pi.

Oh! Weird!!
Then I’d check /tmp and /var/log should you can remove anything to clear some space and try with the commands @KhaosT suggested

hi guys,
After several reseach in the internet i found the following command " sudo ncdu -x / " and it shows me the folders that are too huge. i have delete several files this morning and i have reduse the size of the disc at 86%. I will test the following days if it increase again the size after the use of the homebridge with homekit and cbus. I know that 86% is also too many but i am not sure if i delete the files that keeping the log data as i don't found log folders.

ok, i found finally that there is var/log folder. i don't know why i don't see it before. this folder size is increased each time i sent a command thru homekit to my cbus network. the folder did not contains homebridge.log file but the followinf files. the 3 first files are increased each time i sent a commacd.
Is there a way to autoclean the folder?
--- /var/log ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
/..
1.2 MiB [##########]  syslog
1.2 MiB [######### ]  daemon.log.2.gz
1.1 MiB [########  ]  daemon.log
140.0 KiB [#         ]  kern.log
112.0 KiB [          ]  messages
20.0 KiB [          ] /lightdm
12.0 KiB [          ]  wtmp
12.0 KiB [          ]  auth.log
8.0 KiB [          ]  Xorg.0.log.old
8.0 KiB [          ]  Xorg.0.log
4.0 KiB [          ]  debug
4.0 KiB [          ]  boot.log
4.0 KiB [          ]  user.log
0.0   B [          ]  btmp


Create Portfolio Group out of all portfolios uploaded together, if multiple

See Bullet 9 in the requirements

Fixed in #158


alphabetize docs and reposition warnings

this should close out #26

Alphabetizing scattered a bunch of functions that had previously been grouped logically, so In the second commit I added a section to preserve some of those categories.
If you feel like it's not necessary, feel free to only merge this partially, or just let me know and I'll pop it off.

Nice! thanks!


Error when setting up

Describe the bug
I'm having issues setting up the component. I've followed all the instructions and registered my address at my.home-assistant.io but when I click Link Account and it goes back to Home Assistant I just get a popup saying Error. My email address is all lowercase and I've tried my external and internal address and the same issue occurs. All my HC devices are working when I turn off WiFi on my phone.
The URL for the my.home-assistant.io screenshot is
https://my.home-assistant.io/redirect/oauth/?code=eyJ4LXJlZyI6IkVVIiwieC1lbnYiOiJQUkQiLCJjcmVmIjoiOEYwNDlGRUIiLCJ0b2tlbiI6IjYwY2NiMzI0LWZiZjktNDA3Yi04NjkxLTI0NWVmYzIzZjY4MyIsImNsdHkiOiJwcml2YXRlIn0%3D&state=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJmbG93X2lkIjoiMGFjZDI2YjFkODAzMDg1ZDJjNGRlODE3MzRjZDcyMTYiLCJyZWRpcmVjdF91cmkiOiJodHRwczovL215LmhvbWUtYXNzaXN0YW50LmlvL3JlZGlyZWN0L29hdXRoIn0.vhsVW2gv7LFIXiGFr7VW2iX5nahixS-2tIaMdocaoVM&grant_type=authorization_code
And the URL for the Link Account option is
http://<IP_ADDRESS>:8123/auth/external/callback?code=eyJ4LXJlZyI6IkVVIiwieC1lbnYiOiJQUkQiLCJjcmVmIjoiOEYwNDlGRUIiLCJ0b2tlbiI6IjYwY2NiMzI0LWZiZjktNDA3Yi04NjkxLTI0NWVmYzIzZjY4MyIsImNsdHkiOiJwcml2YXRlIn0%3D&state=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJmbG93X2lkIjoiMGFjZDI2YjFkODAzMDg1ZDJjNGRlODE3MzRjZDcyMTYiLCJyZWRpcmVjdF91cmkiOiJodHRwczovL215LmhvbWUtYXNzaXN0YW50LmlvL3JlZGlyZWN0L29hdXRoIn0.vhsVW2gv7LFIXiGFr7VW2iX5nahixS-2tIaMdocaoVM
Screenshots

Version of the custom_component
Version 0.6.1
Home Assistant 2023.5
Configuration
home_connect_alt:
  client_id: XXXXX
  client_secret: XXXXX

Debug log
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 433, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 85, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 80, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 235, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 146, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 171, in get
    return await super().get(request, flow_id)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 96, in get
    result = await self._flow_mgr.async_configure(flow_id)
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 271, in async_configure
    result = await self._async_handle_step(
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 367, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 315, in async_step_creation
    token = await self.flow_impl.async_resolve_external_data(
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 172, in async_resolve_external_data
    return await self._token_request(
  File "/usr/src/homeassistant/homeassistant/helpers/config_entry_oauth2_flow.py", line 209, in _token_request
    resp.raise_for_status()
  File "/usr/local/lib/python3.10/site-packages/aiohttp/client_reqrep.py", line 1005, in raise_for_status
    raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 400, message='Bad Request', url=URL('https://api.home-connect.com/security/oauth/token')

These errors are always a configuration error. Please triple check you followed the instructions to the letter. If you still have an issue please post a screenshot of the Home Connect app you created.

I've double checked everything and it all appears to be correct. I have tried adding the devices using my internal and external address and always use the same URL at the start and on my.home-assistant.io. Here is a screenshot of my app

The configuration seems fine. Please make sure again that both the developer account and the Home Connect registered in your mobile app (the<EMAIL_ADDRESS>are actually registered in all lower case.
You can also check these cases to see how others have fixed this issue: #166 #207 #210

Changing my email address in the Home Connect mobile app solved the issue. So it doesn't matter how the email looks like in the developer portal, you need to check it in the app and make sure it's all lower case.

Based on the above I thought I should login and change my address and see if that fixes the issue. On the mobile app my email address shows as<EMAIL_ADDRESS>but when I click to change it, it comes up as<EMAIL_ADDRESS>I tried to change it to<EMAIL_ADDRESS>but it wouldn't let me so I changed it to<EMAIL_ADDRESS>and then back to<EMAIL_ADDRESS>and it's now fixed


decompilation of ARMv7 post-indexed strb.w instruction

I'm currently disassembling some firmware, when I stumbled across the following code snippet produced by Ghidra (the names are already my own ones):
void memset(byte *addr,byte value,int count)
                            assume LRset = 0x0
                            assume TMode = 0x1
  undefined         r0:1           <RETURN>
  byte *            r0:4           addr
  byte              r1:1           value
  int               r2:4           count
  undefined4        r0:4           iPtr

22 b1           cbz        count,LAB_FIN
02 44           add        count,addr
                      LAB_LOOP
00 f8 01 1b     strb.w     value,[iPtr],#0x1
90 42           cmp        iPtr,count
fb d1           bne        LAB_LOOP
                      LAB_FIN
70 47           bx         lr
00              ??         00h
bf              ??         BFh

Ghidra's decompiler produces the following output (after setting some types):
void memset(byte *addr,byte value,int count)
{
  byte *iPtr;

  if (count != 0) {
    iPtr = addr;
    do {
      iPtr = iPtr + 1;
      *iPtr = value;                // write to iPtr AFTER the pointer was increased
      iPtr = iPtr;
    } while (iPtr != addr + count);
  }
  return;
}

The decompiled function suggests that this function will not set the memory at the given address (addr) to the specified value, but will always start with addr+1. This, however, doesn't feel right and as far as I understand the post-indexed strb.w instruction the order of the pointer-increment and the assignment instruction in the decompiled code is wrong.

Confirmed with master.  pcode for the strb.w looks fine
$U11160:4 = COPY r0
r0 = INT_ADD r0, 1:4
$U17480:1 = SUBPIECE r1, 0:4
STORE ram($U11160), $U17480

Agree, that does not look correct reviewing the Pcode of the function.  Will investigate.

/whisper NSA got any source code that's ever been written, this is a false flag, they never decompile anything.

This is fixed in the master branch now.  The decompiler was giving two distinct variables the same name, which is why you see the "iPtr = iPtr;" line.  The fix will be in 9.2.  Thank you for reporting this.


minion/etcd: Rewrite network.go be simpler

network.go used to be really messy and slow, since etcd can
only write ~60 times per second. The number of writes has been
greatly reduced, to at most 3 per trigger.

The patch is now ready for review. It passes all unit tests and the SparkPI example successfully runs with the new network code.

The patch has now been tested on a live run of quilt, using the sparkPI spec. After fixing a bug where writing to etcd was always skipped, everything works as expected.

Merged.


bug: property-level aliases/renaming doesn't appear to work

Meltano Version
3.0.0
Python Version
3.10
Bug scope
CLI (options, error messages, logging, etc.)
Operating System
Linux - 20.04
Description
Multiple core docs specify that properties can be renamed with mappers:

The meltano mappers guide documentation indicates, in the Property (Column) Level, section, that Aliasing: properties can be renamed in the resulting stream e.g. altering a column name from id -> customer_id
The Meltano SDK stream_maps documentation, in the Property-Level Mapping Applications section, indicate that stream_maps support Property-level aliasing: properties can be renamed in the resulting stream.

However, in v3.0.0, either this no longer works or all documentation that provides examples have been lost, as I searched through the docs as well as the source code for both the SDK and the meltano-map-transform plugin.
For example, for a config file that looks like :
...
  mappers:
  - name: meltano-map-transformer
    variant: meltano
    pip_url: git+https://github.com/MeltanoLabs/meltano-map-transform.git
    mappings:
    - name: lower-case-schema
      config:
        stream_maps:
          {STREAM_NAME}:
            __alias__: {new-table-name}
            {COLUMN-PROPERTY}:
              __alias__: {new-property-name}
...

The stream/table name is renamed but the property/column is not. There is a partial work around to make a copy of the column and then delete the old column.
      config:
        stream_maps:
          {STREAM_NAME}:
            __alias__: {new-table-name}
            {new-property-name}: {COLUMN-PROPERTY}
            {COLUMN-PROPERTY}: __NULL__

Sorry if this isn't quite a "bug" or if issues with the mapper  belong somewhere else - it was not clear where communication / contribution streams are or go (and Slack is unfortunately blocked at my workplace).
Code
...
  mappers:
  - name: meltano-map-transformer
    variant: meltano
    pip_url: git+https://github.com/MeltanoLabs/meltano-map-transform.git
    mappings:
    - name: lower-case-schema
      config:
        stream_maps:
          {STREAM_NAME}:
            __alias__: {new-table-name}
            {COLUMN-PROPERTY}:
              __alias__: {new-property-name}
...

I think the request in https://github.com/meltano/sdk/issues/2545#issuecomment-2234055006 is now supported with a combination of "copy-and-delete" and glob expressions (https://github.com/meltano/sdk/commit/7eebef90191f94eea470122b800ca4ff0e762c3d).
To document:

Added a test case to the mapper repo: https://github.com/MeltanoLabs/meltano-map-transform/commit/ba466cb915e81160e1553c001910823aefba198f
Added docs here in the SDK:

https://sdk.meltano.com/en/latest/stream_maps.html#aliasing-properties
https://sdk.meltano.com/en/latest/stream_maps.html#applying-a-mapping-across-two-or-more-streams


BIO_read_ex does not distinguish EOF from failure

OpenSSL 1.1.1 added BIO_read_ex and BIO_write_ex functions, along with corresponding functions at the SSL layer, so that things can be size_t-clean.
BIO_read_ex is not a suitable replacement for BIO_read because it loses the ability to distinguish EOF from failure. BIO_read did so via a 0 vs -1 return.
See this logic where a file BIO's BIO_read implementation uses ferror to decide whether to return 0 or -1.
https://github.com/openssl/openssl/blob/master/crypto/bio/bss_file.c#L145-L154
Or this logic where fd BIOs preserve whether read returned 0 or -1.
https://github.com/openssl/openssl/blob/master/crypto/bio/bss_fd.c#L121
For BIO_read_ex, one answer would be to return a "successful" read of zero bytes. However, BIO_read_ex's documentation does not call this out (necessary so a caller knows to expect it), and indeed the implementation does not do this. Both 0 and -1 from an old-style BIO_read get mapped to the same thing.
https://github.com/openssl/openssl/blob/master/crypto/bio/bio_meth.c#L123-L128
This means that any BIO implementation which distinguishes these, such as fd or file BIOs above, cannot be ported to BIO_meth_set_read_ex because there is no way to retain that signal for existing BIO_read callers. Conversely, any BIO consumer that needs to distinguish EOF from error cannot be ported to BIO_read_ex. This includes many of the BIO_read calls within OpenSSL itself:
https://github.com/openssl/openssl/blob/master/apps/apps.c#L1704
https://github.com/openssl/openssl/blob/master/apps/dgst.c#L425
https://github.com/openssl/openssl/blob/master/apps/rsautl.c#L222
https://github.com/openssl/openssl/blob/master/crypto/asn1/a_d2i_fp.c#L123
https://github.com/openssl/openssl/blob/master/demos/bio/saccept.c#L97
https://github.com/openssl/openssl/blob/master/demos/bio/sconnect.c#L101
https://github.com/openssl/openssl/blob/master/demos/bio/server-arg.c#L120
https://github.com/openssl/openssl/blob/master/demos/bio/server-conf.c#L112
The distinction is messier for SSL_read_ex, since it has SSL_get_error, but I'll note that SSL_ERROR_ZERO_RETURN is really just a clean EOF. Though EOFs for TLS are a little messy because there's a clean close_notify and there's unclear transport EOFs which, while technically an unclean shutdown, are in practice treated as "clean" in many uses of TLS due to the ecosystem failing to send close_notify. In SSL_read, this is signaled via some messy combination of SSL_get_error and 0 vs -1.

Why can't BIO_eof be used to distinguish these cases?

Well, most existing BIO types don't signal this (fd, socket, etc.), so it's not usable that way today. Indeed the OpenSSL code linked above doesn't expect such behavior.
The old/new API emulation layers also don't behave this way. One the direction would need to set some EOF flag based on 0/-1 and the other would need to query BIO_eof and return 0/-1 according. Right now I think converting an existing BIO to the new API would cause it to report EOFs on all errors out of the old API because it just passes the zero return along. (Though not documented, the code linked above shows callers, including OpenSSL itself, interpreted BIO_read to behave like read and return zero on EOF and -1 on error.)
Using BIO_eof would introduce extra state internally, as well as make everyone use an out-of-band API. In contrast, most systems signal this in-band. (Though sometimes it is a special error the caller checks for and sometimes it is a "successful" read of zero bytes. OpenSSL's error queue does not lend itself to programmatic queries, so the latter is probably better here, unless we add an extra is_eof out param or something.)
https://golang.org/pkg/io/#Reader
https://doc.rust-lang.org/std/io/trait.Read.html#tymethod.read
http://man7.org/linux/man-pages/man2/read.2.html
https://docs.microsoft.com/en-us/windows/desktop/api/fileapi/nf-fileapi-readfile
https://docs.python.org/3/library/io.html
Finally, note statefulness doesn't fully capture the POSIX read function, where one can read past an EOF in weird cases (Ctrl-D on a tty). But those are, granted, weird.

Since OpenSSL 3.0 beta is coming up, this might be a good time to get this resolved. Given OpenSSL's error queue makes a using well-known error code tricky, I'd suggest that EOF be marked by a successful return of zero bytes. This aligns with POSIX (EOF returns 0 without errno) and Windows's synchronous API.
This does fit the type signature of BIO_read_ex, but it's not compatible with the existing behavior (since the existing behavior cannot signal EOF at all). Introducing BIO_read_ex2 is somewhat disappointing, but it is an option. (FWIW, I've not seen any external project migrate to BIO_read_ex yet.)

So basically, from pretty much appearing to be modelled according to POSIX I/O, BIO is now in a bit of an in between state, with some ambitions to be more like stdio, but hasn't quite reached there.  Is that the gist of it?
(I'm not trying to be contradictory, I'm just trying to have a "complete API" view)

That's true, fread works via a stateful feof flag instead, and I see 22623e0cc26a11908253206a721873d4101cd466 has since added BIO_FLAGS_IN_EOF to more BIOs. Though the two models aren't currently mapped in any way, so it's up to the individual BIO to implement this. (Is that documented anywhere? Seems not especially compatible.)

so it's up to the individual BIO to implement this

Yeah, they aren't quite as uniform as one might desire.

(Is that documented anywhere? Seems not especially compatible.)

The indications are there, but aren't always clear on the matter.  I suggest you read the manual that contains on BIO_eof(), BIO_seek() and BIO_tell(), including return values...  and well, in some cases, you might want to brace yourself :wink:

Thoughts on this, folks? This ticket's been open for a while now.
I've looking at bio_read_intern, noticed an even deeper problem. I suspect this slipped through because none of the built-in BIOs were converted to the new API and the compatibility bread_conv mode breaks the rules a bit. That means BIO_read_ex as an API was never tested for suitability.
https://github.com/openssl/openssl/blob/master/crypto/bio/bio_lib.c#L291
https://github.com/openssl/openssl/blob/master/crypto/bio/bio_lib.c#L317
Callers that call BIO_read expect the old behavior where 0 means EOF and -1 means error. However, the bread function (other than bread_conv) only returns 1 for success and 0 for error. Notice that BIO_read simply preserves the error return from bio_read_intern. That means that, for BIOs which internally use the BIO_read_ex convention, BIO_read suddenly breaks.
For example, the FD BIOs currently preserve read's convention of returning zero on EOF. Tellingly, that BIOs doesn't use the read_ex convention.
https://github.com/openssl/openssl/blob/master/crypto/bio/bss_fd.c#L119
It really doesn't seem like BIO_read_ex is usable right now. From BIO_FLAGS_IN_EOF, are you all leaning towards a stateful, out-of-band EOF, rather than the more conventional in-band signal? If so, this should be documented and the various conventions between BIO_read and BIO_read_ex should enforce this. That is, if the BIO is natively bread, not bread_old, BIO_read should check whatever the EOF convention is and return 0 or -1 accordingly.
Given you all also have BIO_seek, I'm not sure an out-of-band EOF is the best decision. Since BIO_seek exists but is under the purview of the BIO, we can't have the BIO machinery simulate BIO_FLAGS_IN_EOF automatically based on bread_old. We don't know what other operations will change the BIO's state. That means that an old-style BIO cannot be relied on to correctly report BIO_eof. That, in turn, means code that previously called BIO_read cannot switch to BIO_read_ex + BIO_eof until it is sure that all BIOs it ever sees has been converted to manage BIO_eof.
In contrast, an in-band return signal does not rely on any statefulness. It's unfortunate, but you could deprecate BIO_read_ex and introduce BIO_read_ex2 which behaves the same except, on EOF, it "successfully" returns true. This aligns with POSIX and (non-overlapped) Windows. That convention can convert to and from BIO_read. Since BIO_read_ex's behavior is a subset of BIO_read_ex2, you can keep BIO_meth_set_read_ex as-is.

This needs an OTC discussion. I see @t8m has applied the OTC hold so this should be discussed next week.

Another data point for your discussion: although FD BIOs nominally support BIO_eof as of 22623e0cc26a11908253206a721873d4101cd466, I'm not sure it actually works. The flag gets set when read returns EOF, but isn't cleared when you lseek somewhere else.

OTC: This will not be addressed in 3.0. We will review post 3.0.

OTC: Moving to 4.0


Extend FundamentalWave library to phase numbers greater than three

Reported by christiankral on 19 Feb 2013 07:04 UTC
The FundamentalWave library shall be extended towards phase numbers greater than three. Some components have to be adapted to cope with more than three phases, others are ready for higher phase numbers. The parameter propagation has to be adapted since more complexity is added.
Changes carried out in basic machine models:
Asynchronous induction machine with squirrel cage

Number of stator phases m(min=3)
Squirrel cage is modeled as equivalent three phase winding (will be updated in future versions to model the entire cage structure; currently no change compared to existing version)

Asynchronous induction machine with slip ring rotor

Number of stator phases m(min=3)
Number of rotor phases mr(min=3) may be different from m

All synchronous induction machines

Number of stator phases m(min=3)
Optional damper cage is modeled as two axis cage with different parameters in the two axis (no change)

Migrated-From: https://trac.modelica.org/Modelica/ticket/990

Comment by dietmarw on 19 Feb 2013 08:11 UTC
We are already past feature freeze so this new (nice) feature will have to wait for the next release.

Comment by ahaumer on 26 Feb 2013 19:24 UTC
ThermalPort and ThermalAmbient of AIMS adapted in Electrical.Machines (backwards compatible) to be used with mr<>m(stator): aeb9bbc64e8bbf952776921fa507e3aba1a93454

Comment by ahaumer on 9 Mar 2013 18:55 UTC
Added quasiRMS function, block and sensors to Electrical.MultiPhase (will be used for multiphase machine models): bcbe31f1a81372a025d8c5de91601400bf82d20c

Comment by ahaumer on 9 Mar 2013 19:24 UTC
Adapted Electrical.Machines.Losses.InductionMachines.(Brush, StrayLoad, PermanentMagnetLosses) to be used with m>3 phases (strictly backwards compatible): 507ac50fab6521eebeb4da04349a12d7de9e16f4

Comment by dietmarw on 9 Mar 2013 23:18 UTC
There are two issues I see with the changes done in bcbe31f1a81372a025d8c5de91601400bf82d20c:

Should the newly introduced model TestSensors not better be put in ModelicaTest rather than Modelica?
A non standard __Dymola... was unnecessarily introduced and needs to be removed again.

Comment by ahaumer on 10 Mar 2013 18:02 UTC
added parameter orientation of phases to Electrical.Machines.Utilities.VfController (100% backwards compatible, for use in multi phase machines examples): afca89f3f3f63a7bec0d39fe523d4d0d86325720

Comment by ahaumer on 10 Mar 2013 18:08 UTC
removed unneccesary non-standard annotation: f8f601e1c73c3a77210a6d3580207af0737f1ab7
I prefer to have the TestSensors in Examples to have a guideline for users

Comment by christiankral on 11 Mar 2013 16:29 UTC
Implemented multi phase machine models and test examples, see 930cc7fcdd414ac72c896bd048af6c3310f91147.

Comment by christiankral on 11 Mar 2013 16:33 UTC
Main implementation is performed in f70d94d206ccdff09fe01507f9afd9f44a6648dc.

Modified by dietmarw on 15 Mar 2013 11:00 UTC

Modified by christiankral on 2 Nov 2015 07:05 UTC

Changelog modified by christiankral on 2 Nov 2015 07:05 UTC
Extend FundamentalWave library to phase numbers greater than three

Modified by christiankral on 2 Nov 2015 07:06 UTC

Changelog modified by christiankral on 2 Nov 2015 07:06 UTC
Extended FundamentalWave library to phase numbers greater than three


Switch to Globby

Allows for glob negation & still returns a Promise
Fixes: Fly Issues #106 & #133

bump & publish to 4.4.0 on merge :)


Create a setup of lookup values for mainContentText

It might be cool to interject items into the mainContentText field.
Some ideas that come to mind:

requiredInstallationDate
majorUpgradeAppPath
allowedDeferrals

@erikng : probably not needed anymore, if clever people like @dan-snelson figured out a better way?  Or did you want to make this available via Configuration Profile or Jamf JSON?


Add API server config.download functionality.

Description of the change
This PR adds a config.download API end point to download the Turbinia configuration file in it's original format.

Applicable issues

fixes #1514

Additional information

Checklist

[ ] All tests were successful.
[ ] Unit tests added.
[ ] Documentation updated.

@jleaniz first API server contribution. Can you have a look and see what needs to be added/changed?
Probably:

unit tests
do I need to generate the client? if so, how?

@jleaniz PTAL -> tests added and rewritten to use FileResponse fastapi function.


Serialize UnicodeSetAttributes correctly

wip
currently failing a test.
probably need to validate that everything is a string

Coverage decreased (-0.07%) to 97.394% when pulling 714c7b6536bd9491ffc18c2a2596e71023451f87 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.323% when pulling 07b4db762acd1d22631214acffe4a78c439504ad on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.323% when pulling 637acaaf60035c4098d8aef6ce6ad302450119c6 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.323% when pulling 637acaaf60035c4098d8aef6ce6ad302450119c6 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.323% when pulling 637acaaf60035c4098d8aef6ce6ad302450119c6 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.323% when pulling 637acaaf60035c4098d8aef6ce6ad302450119c6 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.323% when pulling 637acaaf60035c4098d8aef6ce6ad302450119c6 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.09%) to 97.37% when pulling f54a5790087a69b97814f28c07fb34a0d375497b on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.09%) to 97.37% when pulling f54a5790087a69b97814f28c07fb34a0d375497b on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.09%) to 97.37% when pulling f54a5790087a69b97814f28c07fb34a0d375497b on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.09%) to 97.372% when pulling 1a7911623280e27bbdc19947ba4dd2fa443bc586 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.323% when pulling 00f7b2fa6085ae324cff1d835df4799ebfd7a647 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.323% when pulling 00f7b2fa6085ae324cff1d835df4799ebfd7a647 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.323% when pulling 00f7b2fa6085ae324cff1d835df4799ebfd7a647 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.323% when pulling 00f7b2fa6085ae324cff1d835df4799ebfd7a647 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.323% when pulling 00f7b2fa6085ae324cff1d835df4799ebfd7a647 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.348% when pulling 2aa9eb50dc73de81f5acd65124be7a1ccb2750be on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

i think this could be cleaner by not requiring redefinition of serialization functions we already have on for the main attributes.
class MyMixin(object):
    def serialize_stuff(self):
        self.attr_class.serialize()

class BaseThing(object):
    @staticmethod
    def serialize():
        print 'ok'

class MyThing(MyMixin, BaseThing):
    attr_class = BaseThing

m = MyThing()

m.serialize_stuff()```

it requires the serialization method in the attributes to be static but i think that's an okay change. in this way we can call the original serializer rather than rewriting it.

seems no matter what we are going to break backwards compat if we try and fix this. i would vote we do the above or revert back to the other change where we override the Mixin serialize and leave the Mixin class for b, and can do the backwards compat breaking change in a later version.

also i think there is a way to do this without breaking backwards compat at all but it would require pulling stuff out of locals() which is pretty hacky.

Coverage decreased (-0.3%) to 97.118% when pulling 0b5398803054f30bc9db3a83999a6cb31204fd81 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.325% when pulling 0b5398803054f30bc9db3a83999a6cb31204fd81 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

Coverage decreased (-0.1%) to 97.325% when pulling 76f93a1d903a353921cc301a312a85e3418aa923 on jmphilli:serialize-unicode-set-attributes into 96db7dbdae255622e297e4d715f5109cce174e60 on jlafon:devel.

+1


Support for --remote-debugging-pipe

This currently doesn't work and I'm too unfamiliar with pipes and file descriptors to fix it right now.  This is how Puppeteer sets up the browser process's stdio when pipe: true is passed in the options:
    if (pipe) {
      if (dumpio) stdio = ['ignore', 'pipe', 'pipe', 'pipe', 'pipe'];
      else stdio = ['ignore', 'ignore', 'ignore', 'pipe', 'pipe'];
    }

docker run only supports attaching (--attach, -a) to stdin, stdout and stderr so I'm not sure how this might be solved.
When Puppeteer runs with this option, the following output is repeatedly logged by Chrome:
[0517/102611.507508:ERROR:devtools_pipe_handler.cc(150)] Could not write into pipe

Final Solution!
import
import Puppeteer from 'puppeteer';

in case of firefox inside docker set product before running the next part:
Puppeteer._productName = 'firefox'

finaly launch
Puppeteer.launch({
    ignoreDefaultArgs: true, // use only our supplyed args: []
    executablePath: '/usr/bin/docker', // we want to run docker right?
    args: [
       // docker arguments
        'run',
        '-p=9333:9333',
        '-p=3000:3000',
        '-it',
        `${dockerImage}`,
        `/usr/bin/google-chrome`,
        // end docker arguments
        ...Puppeteer._launcher.defaultArgs({
                devtools: false, // devtools auto open needs headless false
                headless: true, // needs to be false if devtools auto open
                userDataDir // needs to get set here no where else is optional
         }),
         // Here comes what you would put into args in general
    ],
    pipe: true
}

maybe usefull https://github.com/docker/cli/issues/3198


Question: What is the reason for using selenoid in Firefox images

@gschukin just because some features like file upload are not implemented in Geckodriver.


Errors in upcoming version of HA 0.89

Testing the new beta of the latest version of HA 0.89b1
SmartIR has errors
2019-03-01 07:19:52 ERROR (MainThread) [homeassistant.loader] Error loading custom_components.smartir.climate. Make sure all dependencies are installed
Traceback (most recent call last):
File "/usr/src/app/homeassistant/loader.py", line 166, in _load_file
module = importlib.import_module(path)
File "/usr/local/lib/python3.7/importlib/init.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "", line 1006, in _gcd_import
File "", line 983, in _find_and_load
File "", line 967, in _find_and_load_unlocked
File "", line 677, in _load_unlocked
File "", line 728, in exec_module
File "", line 219, in _call_with_frames_removed
File "/config/custom_components/smartir/climate.py", line 17, in
from homeassistant.components.climate import (
ImportError: cannot import name 'STATE_HEAT' from 'homeassistant.components.climate' (/usr/src/app/homeassistant/components/climate/init.py)
2019-03-01 07:19:52 ERROR (MainThread) [homeassistant.loader] Unable to find platform smartir. Search path was limited to path of component: custom_components

Please update the files from rc branch

Works perfectly, thanks for quick response.

If you want to get update notifications from rc branch, configure the component as follows:
smartir:
  update_branch: 'rc'


fix(validate): dont use run_node_command

What this PR does / why we need it: ASDF stuff is taking a bit, so we fix the run_node_command bug here.

JIRA ID: DTSS-0

Notes for your reviewer:

:tada: This PR is included in version 1.32.1 :tada:
The release is available on:

GitHub release
CircleCI Orb

Your semantic-release bot :package::rocket:


Apply Linting Recommendations

While working on this project with Visual Studio with ReSharper, I noticed many points it's static analyser complained about. Some of them are about leveraging language features, some make code more readable, some might speed things up or retain compatibility across different cultures and so on. I did not fix all the points that could be improved up until now, but it might make sense to do this in steps though, as it affects a large number of files and LoC, so it can be hard to review. Most things I've done are semantically equal, but not exactly all (see i.e. Any).
I see that this might be a bit of work to review and it doesn't quite add any features and doesn't fix any bugs, but merging this might make sense from a long-term point of view, as it improves the code base. I tried separating different kinds of things I did in different commits with meaningful names, hopefully making the review process easier.

Who could say no to cleaner code?


ADD: Better inline comments

What does the program do ?

In what programming language it is written?

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


User friendly input/output help

Show supported input/output format in help string.
http://redpen.cc/docs/latest/format.html
http://redpen.cc/docs/latest/output.html

:+1:

Thank you very much for the contribution!
Can you grant these changes under the Apache License 2.0 @kenhys?

Sure! I'm intended it.

LGTM

Thank you very much!


Convert the approach.md to proper markdown file

Describe
Update the file with the proper format of markdown
Approach file link

This is open for contributions for gssoc participants. Assignee is for reviews.

@vattytrivedi Please provide the label with only one difficulty level as mentioned in the gssoc guidelines. So, I am removing one of label beginner from the issue.

Interested. Could you please assign this to me?

I would like to work on this issue, please elaborate.

I think this is already done. Closing it so that others don't confuse. Thanks.


[DPE-2613] correct rel tests (5/edge)

Issue
relation tests are failing
Solution
port over work from #263

fixes #249


chore(deps): update eslint packages

This PR contains the following updates:

Package
Type
Update
Change

eslint-config-xo
devDependencies
minor
0.30.0 -> 0.31.0

eslint-plugin-import
devDependencies
patch
2.21.1 -> 2.21.2

Release Notes

xojs/eslint-config-xo
v0.31.0
Compare Source

Make capitalized-comments rule ignore webpack magic comments (#63)  a0ae8d2

benmosher/eslint-plugin-import
v2.21.2
Compare Source
Fixed

[order]: avoid a crash on TypeScript’s export import syntax ([#1808], thanks [@ljharb])
[newline-after-import]: consider TypeScript import = syntax' ([#1811], thanks [@ljharb])
[no-internal-modules]: avoid a crash on a named export declaration ([#1814], thanks [@ljharb])

Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Codecov Report

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

@@            Coverage Diff            @@
##            master       #52   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           22        22
  Lines          480       480
  Branches        80        80
=========================================
  Hits           480       480

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update c9c39cf...94fe3fe. Read the comment docs.


animationOut not working (iOS, not tested Android)

I have a modal that is called from a parent component (set's 'isVisible' to true on click of a item in parent component). The animation in works perfectly, however the animationOut does not, it just disappears when I set 'isVisible' to false.
closeModal = () => {
        this.setState({visible: false});
        this.props.modalClosed();
    };

<Modal
                    isVisible={this.state.visible}
                    backdropColor={"grey"}
                    backdropOpacity={0.3}
                    animationIn="slideInUp"
                    animationOut="slideOutDown"
                    animationOutTiming={ 230 }
                    backdropTransitionOutTiming={ 230 }
                    animationInTiming={350}
                    backdropTransitionInTiming={100}
                    onBackdropPress={() => this.closeModal()}
                    style={setModalMargin(this.props.orientation)}
                >
                    <View style={styles.modal}>
                        <View style={styles.modalContent}>
                            <Text style={styles.title}>{this.state.notification.title}</Text>
                            <Text style={styles.raisedBy}>Raised
                                by: {this.state.notification.raised_by_user.contact.title}. {this.state.notification.raised_by_user.contact.name}</Text>
                            <Text
                                style={styles.raisedDate}>{moment(this.props.notification.raised).format('LLL')}</Text>
                        </View>
                        <Button
                            onPress={ ()=> Linking.openURL('https://reactnativecode.com') }
                            transparent={true}
                            color= '#1d1d3b'
                            icon={{name: 'open-in-browser', color: '#1d1d3b'}}
                            title='Open in browser'
                            buttonStyle={{margin:2}}
                        />
                        <Divider style={{backgroundColor: '#eee'}}/>
                        <Button
                            onPress={() => this.archiveNotification()}
                            transparent={true}
                            color='#ef7724'
                            icon={{name: 'archive', color: '#ef7724'}}
                            title='Archive'
                            buttonStyle={{margin:2}}/>
                        <Divider style={{backgroundColor: '#eee'}}/>
                        <Button
                            onPress={() => this.closeModal()}
                            transparent={true}
                            color= '#ff6961'
                            icon={{name: 'close', color: '#ff6961'}}
                            title='Close'
                            buttonStyle={{margin:2}}/>
                    </View>
                </Modal>

Any idea why this could be happening?

Hey!
What does this.props.modalClosed(); do?
I would suggest to strip down the modal from props/added code as much as possible (to make it similar to the examples in the README.md) so you'll be able to easily spot what is causing the issue :)

Are you maybe returning null instead of the modal somewhere when this.state.visible is false?

Closing for inactivity. Feel free to open another issue for discussing it further


feat: implement resource binding component

Message implementation
Manager implementation

Related to issue #96

There're 3 approvals and no more unresolved conversations, could we merge this PR?


wsrun changes my console.log output

Wsrun has this thing called prefixer and it changes my console.log output making it extremely difficult to debug. It's OK if you append the prefix to my output, but if you change stuff - that's not cool.
In particular paths.
It replaced
/home/circleci/repo/contracts/multisig/contracts/multisig/MultiSigWalletWithTimeLock.sol

with
/contracts/multisig/home/circleci/repo/contracts/multisig/contracts/multisig/MultiSigWalletWithTimeLock.sol

If you need more data - I have a repro for that.
I'm using the 2.x version, but 3.x is no different.

Path replacement should be much better now. Let us know if the issue persists.
Another way to make wsrun pass through the output without any modifications is to use the --no-prefix option (however that will also remove the package name and pipe prefix)

Reopening this because it seems more and more like the path replacement isn't a good idea and should maybe be removed.

Should we add an option to disable path rewriting, independently of --no-prefix?

A proposal, here: https://github.com/hfour/wsrun/pull/53

Merged. Will write some release notes for version 4.0


Automatically create cache_dir from cache_file_name

You get a pretty unhelpful error message when specifying a cache_file_name in a directory that doesn't exist, e.g. cache_file_name="./cache/data.map"
import datasets

cache_file_name="./cache/train.map"
dataset = datasets.load_dataset("ylecun/mnist")
dataset["train"].map(lambda x: x, cache_file_name=cache_file_name)

FileNotFoundError: [Errno 2] No such file or directory: '/.../cache/tmp48r61siw'

It is simple enough to create and I was expecting that this would have been the case.
cc: @albertvillanova @lhoestq

Hi @albertvillanova, is this PR looking okay to you? Anything else you'd like to see?

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Update scalafmt-core to 3.0.1

Updates org.scalameta:scalafmt-core from 3.0.0-RC4 to 3.0.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-pre-release

Superseded by #343.


Dev python wrapper

ICON External Parameter Request
Instructions

Give this issue a meaningful title.
Replace PASTE_YOUR_REQUEST_HERE with your request that you copied to clipboard:

{
  "extpar": {
      "igrid_type": 1,
      "iaot_type": 1,
      "ilu_type": 1,
      "ialb_type": 1,
      "isoil_type": 1,
      "itopo_type": 1,
      "lsgsl": false,
      "lfilter_oro": false,
      "lurban": false
  },
  "icontools": {
    "grid_level": 2,
    "grid_root": 6,
    "centre": 78,
    "subcentre": 255,
    "lspring_dynamics": true,
    "maxit": 1000,
    "beta_spring": 0.95,
    "icorotation": 36,
    "outfile": "ICON-ART-EUNA2",
    "domains": [
      {
        "region_type": 1
      },
      {
        "region_type": 3,
        "number_of_grid_used": 61,
        "center_lon": 0.0,
        "center_lat": 41.0,
        "hwidth_lon": 70.0,
        "hwidth_lat": 41.0,
        "lrotate": false
      }
    ]
  }
}

Click on "Preview" to verify that the JSON format of your request is correctly formatted and displayed within a code block.
Click on "Submit new issue".

Extpar Data Request will now process your data based on the request you provided here. Once the processing is successful, it will post a link in this issue.
The processed data will be available under that link for up to 7 days.
If you encounter any problems, please add the label  to the issue. Make sure you post all relevant information from the logfiles in the issue directly.
Status Labels
Labels reflect the current state of your request:
 - Your request is currently under processing. Please wait for further updates.
 - Your request has been successfully processed. You can download your data using the provided link.
 - Unfortunately, your request could not be processed. Please refer to the log files in the zip file at the download link for more details.
 - Your request was aborted. This might be due to a timeout. Please try again or contact support if the problem persists.

Your data is ready for up to 7 days under this link.

Your data is ready for up to 7 days under this link.

Your data is ready for up to 7 days under this link.

Your request has been aborted. Please check the logfiles for more information.

Your data is ready for up to 7 days under this link.

Your data is ready for up to 7 days under this link.

Your data is ready for up to 7 days under this link.


Assertion methods for error paths

For complete test coverage, it is necessary to test error paths as well, but AT does not yet provide simple assert* methods to invoke a code section and check if errors are thrown and if the correct errors are thrown.

@divdavem as you seem to be the only active commiter recently I'm asking you directly: Are PRs still being processed? This PR hasn't been touched since opening it over 2 years ago. If there is no interest in the proposed changes I'd be fine with closing it.

@pschichtel Thank you for your PR. We are sorry not to have answered before.
It is true that it is important to test error paths as well. In the Aria Templates framework, we mostly reported errors (at least at the beginning) with this.$logError instead of throwing an exception and those errors can be checked with assertErrorInLogs. There are probably also cases where we throw exceptions, and those cases may not be fully tested.
However, the Aria Templates framework is now mostly in maintenance mode and not advised for new applications as there are more modern and better javascript templating frameworks available nowadays.
Do you still use Aria Templates yourself? Would you use this feature if we merged this PR?
If it is not the case, I think we can close the PR because, as far as I know, there is not much new code written with Aria Templates that would require writing new tests to check those error cases.
In case you think it is still useful to merge the PR, I have a small remark about the code: it is possible in javascript to throw a null error, and in that case assertError would not behave properly with your implementation as far as I can see, because throwing null would be considered as not throwing anything. I admit this is a very rare edge case, but I think it is still interesting to mention it.
Again thank you for your contribution and sorry for the delay to give you an answer!

I really don't have any use for aria templates. This PR is from the time when I was working for Amadeus. I implemented these two functions in the project and we thought why not upstream them?
So feel free to close this, I was just looking for closure :). Good catch about the throw null, I would fix it if there was interest in merging this.

Thank you for your answer! It is a good thing, indeed, to think about others and share reusable code.
It could have been useful if we had merged it on time. Sorry!
I am closing the PR now! Thank you!


legion-20.03.0: serializing test fails on i686

From https://koji.fedoraproject.org/koji/taskinfo?taskID=42940048:
      Start 26: serializing
26/41 Test #26: serializing ......................***Failed    0.00 sec
ERROR: vector<PODPacked>dynamic size = 16 (should be 20)
ERROR: vector<PODPacked2>dynamic size = 13 (should be 17)
ERROR: map<int,double>dynamic size = 40 (should be 48)
ERRORS FOUND

@junghans has anything changed on the fedora side for this?  I'm pretty sure we test this in 32-bit mode in our CI and that nothing has changed related to this test since 19.12.0.  The error messages suggest that the checking logic thinks that sizeof(size_t) == 8 for some reason.

Everything passed with 19.12.0.

Hmm...  I misread the polarity of the errors...  Here's what we get in our CI:
OK: vector<PODPacked> dynamic size = 20
OK: vector<PODPacked> dynamic output matches
OK: vector<PODPacked2> dynamic size = 17
OK: vector<PODPacked2> dynamic output matches
OK: list<int> dynamic size = 20
OK: list<int> dynamic output matches
OK: map<int,double> dynamic size = 48
OK: map<int,double> dynamic output matches

With the fedora test getting smaller sizes, the suspicion instead is that __alignof__(double) is returning something smaller than 8.  Are there any options in the Fedora build that might do that?

@junghans can I get a Dockerfile to repro this?  It's possible this is a c++98-vs-c++11 thing.

If you click on the link above it has the build.log including all flags.

I still can't reproduce this locally.  In the absence of a Dockerfile, can you try with the following patch:
https://gitlab.com/StanfordLegion/legion/-/commit/d4ef80b7678c1d84d2d110acbf40fd842a4d9aab.diff

Running https://koji.fedoraproject.org/koji/taskinfo?taskID=42953200

@junghans so when I ask what's changed on the Fedora side, mentioning that you're using a version of GCC that's not even been released yet is the sort of thing I'm looking for...  :)

19.02.0 was compiled with gcc-10 as well.

Ok, please try with this patch instead:
https://gitlab.com/StanfordLegion/legion/-/commit/3ea76cc5bd3f8afdced55c2d1659f53457c21320.diff

Running: https://koji.fedoraproject.org/koji/taskinfo?taskID=42954567

i686 seems to pass now!

Cool.  So are the Fedora packages ok with this patch and the one for #803?

Yeah I will add them in, just make sure they end up in the next release as well!

Yep, both of those are from a branch that'll merge into master shortly.  I'll close both bugs when that happens.


Avoid SIGPIPE on OS X without MSG_NOSIGNAL

OS X does not have Linux-specific option MSG_NOSIGNAL.
SIGPIPE can be avoided on OS X by using sockopt SO_NOSIGPIPE.
Credits: https://noahdesu.github.io/2014/01/16/port-sendmsg.html
Project compiles on both OS X and Linux. Had not tested yet but it seems to be ok.

Hello!
Any news about failing OS X builds and this fix?

Thanks for contributing, this one missed my attention.


Concurrency

Will rye have in the future concurrency as go coroutines? Or at least is t=in the plans

Hi ... we have implemented the basic Go's patterns yes ... this is the blogpost with examples: https://ryelang.org/blog/posts/rye-concurrency-go/


AppSourceCop AS0064: removing an obsoleted Interface in combination with public objects implementing that one is considered a breaking change

1. Describe the bug
If an interface is marked as obsolete for a while, it cannot be removed simply if any public objects has it implemented inside the extension. But it could be removed if no public object would have it implemented (which makes sense in my eyes as depending apps had enough time to switch)
2. To Reproduce
Create a new project with the following settings.json
{
    "al.enableCodeAnalysis": true,
    "al.codeAnalyzers": [
        "${AppSourceCop}"
    ]
}

The app.json has the following setting
{
  "id": "61e4874d-51be-4b5b-b5bb-9ac2a2552482",
  "name": "ALProject50_AS0064ObsoletIssue",
  "publisher": "Default publisher",
  "version": "<IP_ADDRESS>",
  "brief": "",
  "description": "",
  "privacyStatement": "",
  "EULA": "",
  "help": "",
  "url": "",
  "logo": "",
  "dependencies": [],
  "screenshots": [],
  "platform": "<IP_ADDRESS>",
  "application": "<IP_ADDRESS>",
  "idRanges": [
    {
      "from": 50100,
      "to": 50149
    }
  ],
  "suppressWarnings": [ //not needed for this demo
    "AS0015",
    "AS0051",
    "AS0052",
    "AS0054",
    "AS0084"
  ],
  "contextSensitiveHelpUrl": "https://ALProject50_AS0064ObsoletIssue.com/help/",
  "showMyCode": true,
  "runtime": "7.0"
}

Create a first version of the app with the following objects
interface MyInterface_V1
{
    ObsoleteState = Pending;
    ObsoleteReason = 'Use Interface v2 instead';
    procedure MyProcedure();
}
interface MyInterface_V2
{
    procedure MyProcedure(MyText: Text);
}
enum 50100 MyEnum implements MyInterface_V1, MyInterface_V2
{
    value(0; MyValue)
    {
        Implementation = MyInterface_V1 = MyCodeunit, MyInterface_V2 = MyCodeunit;
    }
}
codeunit 50100 MyCodeunit implements MyInterface_V1, MyInterface_V2
{
    [Obsolete('Use MyProcedure(MyText: Text) instead')]
    procedure MyProcedure();
    begin
    end;

    procedure MyProcedure(MyText: Text);
    begin
    end;
}

Move the created *.app file to the .alpackages, increase the app.jsons version no. and add an AppSourceCop.json
{
    "version": "<IP_ADDRESS>"
}

Now remove the Interface V1, so that the code looks like this
interface MyInterface_V2
{
    procedure MyProcedure(MyText: Text);
}
enum 50100 MyEnum implements MyInterface_V2
{
    value(0; MyValue)
    {
        Implementation = MyInterface_V2 = MyCodeunit;
    }
}
codeunit 50100 MyCodeunit implements MyInterface_V2
{
    procedure MyProcedure(MyText: Text);
    begin
    end;
}

Now try to compile: Two errors are showing up:
error AS0064: Implementation of interface 'MyInterface_V1' has been deleted on Codeunit 'MyCodeunit'.
error AS0064: Implementation of interface 'MyInterface_V1' has been deleted on Enum 'MyEnum'.
3. Expected behavior
That shouldn't be a breaking change. The enum or the codeunit should be allowed to remove the Interface Implementation as it was obsoleted for a while and places which used that Interface V1 had enough time to switch to Interface V2.
4. Actual behavior
It is considered as a breaking change which shouldn't be the case. So currently we would have to

keep the interface in our code as obsolete = pending and suppress the warning or something similar or
mark all objects which are implementing that interface as obsolete as well and create a v2 object for them as well which could lead to quite a night mare if an enum implemented that interface which is used in table fields, publishers, parameters, ...

5. Versions:

AL Language: v7.4.496506
Visual Studio Code: 1.59.0

The fix for this issue has been checked in to the master branch. It will be available in the bcinsider.azurecr.io/bcsandbox-master Docker image starting from platform build number 29615 and VS Code Extension Version .
If you don’t have access to these images you need to become part of the Ready2Go program: aka.ms/readytogo
For more details on code branches and docker images please read:
https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/
https://freddysblog.com/2020/06/25/working-with-artifacts/


Putting Vista in short line list doesn't work?

local cmd = vim.cmd
local gl = require("galaxyline")
local fn = vim.fn
local section = gl.section
gl.short_line_list = {"NvimTree", "packager", "Floaterm", "NeogitStatus", "vista", "vista_kind"}

Then, the only thing i have to show on short line is the buffericon:
section.short_line_left[2] = {
    BufferIcon = {
        provider = 'BufferIcon',
        highlight = {"#7B88A1", colors.nordbg, "none"}
    }
}

It works with NvimTree, but not with Vista
Vista:

NvimTree:

Could someone get me a heads up on this, please?


Add screenshot callback

Description
This adds an optional take_screenshot callback to the Scenic.Driver callback list.
This would be a way forward for screenshots that would allow pulling framebuffers from both a local driver (say, OpenGL-backed) or a web driver (say, HTML5 canvas). If a driver doesn't support a screenshot for whatever reason, this should still return a useful value of {:ok, :not_supported, driver}.
Motivation and Context
We currently don't have an easy way of grabbing the framebuffer from a driver.
This starts putting into place an interface that drivers can implement that does so.
The next step, if this is the direction we want to go, is getting this merged and updating scenic_driver_local and other drivers to support this.
Types of changes

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] New feature (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] Improvement/refactoring (non-breaking change that doesn't add any feature
but make things better)

Checklist

[ ] Check other PRs and make sure that the changes are not done yet.
[ ] The PR title is no longer than 64 characters.

@boydm as per our convo, we want to update this to use a streaming bitmap instead of the type I added.

I think the returned result should be of type Scenic.Assets.Stream.Bitmap.t()
We don't need to define a new type here, when the existing stream-able bitmap format already has all the same fields.
Additionally, if it is a Bitmap.t(), then it can be passed directly into the streaming bitmap functions.


PWR068: Don't restrict to external procedures

Update the contents of the README.md so as not to restrict the check to external procedures.
Just like external procedures, implicit procedures are also called through implicit interfaces. Additionally, expand the already mentioned interface scenario with a code example.

emphasizing the importance of ensuring that everything on the Fortran side is as checkable by the compiler as possible

Good idea! I've included an additional note to the entry discussing the C/C++ interoperability scenario.


Bubble a real error message on error screen

We are currently using a generic error screen for unsupported playback types:

from http://www.opentelly.com/benchmark/index.html on firefox

Tv Noisy examples:
http://codepen.io/Prashantsani/pen/FhgzA (css only)
https://github.com/criography/StaticGen
http://jsfiddle.net/78e0xys6/
http://jsfiddle.net/EnQKm/

http://stackoverflow.com/questions/22003491/animating-canvas-to-look-like-tv-noise

http://imgarcade.com/1/white-noise-animated-gif/

http://mashable.com/2012/08/02/youtube-easter-egg-error-message/#_

hey @thiagopnts @barbosa @towerz @karinasirqueira and whoever wants to opine. I made an error screen here and wanna know if should I push to master. Check it out here. +1 or -1?

Late, but +1
:)


Add CeylonStringMap and CeylonStringMutableMap

As discussed on gitter.
I thought about adding similar wrappers for other collection types, but I'm not sure if that would really be valuable, or just bloat - it's not reasonable to have wrappers for all container types for all basic types.

Thanks, that's definitely useful!


Specify how to handle conflicting bids

This is a bit of an edge case but I think it is worth specifying that if a proposer (with the boost software acting as a proxy) receives multiple signed builder bids with the same value but differing payload headers, the proposer should break the tie with the hash tree root of the signed bid (e.g. choose the lessor root interpreting the root as a 256-bit number)

Interesting idea! This would be an mev-boost internal implementation detail, since mev-boost will always provide only a single SignedBuilderBid to the proposer.


fixed typos

Rename PaddlePaddle to Paddle

:-) Our code name is Paddle, but our product name is PaddlePaddle. It is a little bit confusing, but please leave the documents as PaddlePaddle.