RuntimeWarning: compiletime version 3.4 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.5; uiltins.type size changed, may indicate binary incompatibility. Expected 432, got 412

Please make sure that this is a bug. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:bug_template
System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): No
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Raspbian 9
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device:
TensorFlow installed from (source or binary): binary, I think? (pip installed)
TensorFlow version (use command below): 1.11.0
Python version: 3.5.3
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): N/A
CUDA/cuDNN version: N/A, no GPU
GPU model and memory: N/A, no GPU

You can collect some of this information using our environment capture script
You can also obtain the TensorFlow version with
python -c "import tensorflow as tf; print(tf.GIT_VERSION, tf.VERSION)"
Describe the current behavior
As you know with the title, when I import tensorflow in shell window, I get a warning. (See code)
Describe the expected behavior
I recently saw some issues, and they says that it is OK to use tensorflow with this. But my question is: how can I get rid of this?
Code to reproduce the issue
Provide a reproducible test case that is the bare minimum necessary to generate the problem.

>>> import tensorflow as tf

Warning (from warnings module):
  File "/usr/lib/python3.5/importlib/_bootstrap.py", line 222
    return f(*args, **kwds)
RuntimeWarning: compiletime version 3.4 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.5

Warning (from warnings module):
  File "/usr/lib/python3.5/importlib/_bootstrap.py", line 222
    return f(*args, **kwds)
RuntimeWarning: builtins.type size changed, may indicate binary incompatibility. Expected 432, got 412
>>>

Other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

I know it is good to keep going, but I want to get rid of it. OK?

@sjkim04   Could you please try with Python 3.6 ?

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

Closing as this issue is in "awaiting response" status for more than 7 days and did not hear back from the user. Please post your comments if any, we will reopen. Thanks !

This issue still persists as of April 7, 2019. I installed Raspbian and then followed the instructions as per Tensorflow installation guide. Then, I got this error message.

the same error on rpi 3b+ with python 3.5

I've install Python 3.6.8 (Raspbian Stretch).
And I've got these warnings as well:
/usr/local/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: compiletime version 3.4 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.6
return f(*args, **kwds)
/usr/local/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: builtins.type size changed, may indicate binary incompatibility. Expected 432, got 412
return f(*args, **kwds)

the same error on rpi 2 with python 3.5

I'm on Raspbian Stretch with Python 3.6, and got thess warnings upon installing tensorflow-1.13.1-cp36-none-linux_armv7l.whl:
pi@raspberrypi:~ $ python -c "import tensorflow as tf;print(tf.reduce_sum(tf.random.normal([1000, 1000])))"
/home/pi/.pyenv/versions/3.6.8/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: compiletime version 3.4 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.6
  return f(*args, **kwds)
/home/pi/.pyenv/versions/3.6.8/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: builtins.type size changed, may indicate binary incompatibility. Expected 432, got 412
  return f(*args, **kwds)
Tensor("Sum:0", shape=(), dtype=float32)

I have the very same problem with the latest RaspberryPi image and tensorflow  https://www.piwheels.org/simple/tensorflow/tensorflow-1.13.1-cp27-none-linux_armv7l.whl
/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: compiletime version 3.4 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.5
  return f(*args, **kwds)
/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: builtins.type size changed, may indicate binary incompatibility. Expected 432, got 412
  return f(*args, **kwds)
^CTraceback (most recent call last):
  File "<frozen importlib._bootstrap_external>", line 88, in _path_is_mode_type
  File "<frozen importlib._bootstrap_external>", line 82, in _path_stat
FileNotFoundError: [Errno 2] No such file or directory: '/home/pi/.local/lib/python3.5/site-packages/gast/__init__.cpython-35m-arm-linux-gnueabihf.so'

During handling of the above exception, another exception occurred:

Any fix for this same issue as below:
/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: compiletime version 3.4 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.5
  return f(*args, **kwds)
/usr/lib/python3.5/importlib/_bootstrap.py:222: RuntimeWarning: builtins.type size changed, may indicate binary incompatibility. Expected 432, got 412
  return f(*args, **kwds)

I tested different tensorflow version on the latest raspian and I have always the same error.
(tested with tf  1.9.0, 1.10.1, 1.11.0, 1.12.0, 1.13.1)
I think the ticket should reopend...or?

I installed the arm6 version from here and it works on a pi zero
https://github.com/lhelontra/tensorflow-on-arm/releases/tag/v1.13.1

You saved my day. Many thanks.
But I don't understand why I have to access third party sources to install tensorflow properly on a current Raspberry. Anyway - I have a solution and am happy. Mayn thanks again to you and the
provider of the tensorflow whl
wget https://github.com/lhelontra/tensorflow-on-arm/releases/download/v1.13.1/tensorflow-1.13.1-cp35-none-linux_armv7l.whl
sudo pip3 install ./tensorflow-1.13.1-cp35-none-linux_armv7l.whl
python3 -c 'import tensorflow as tf; print(tf.__version__)'
1.13.1

@everyone this is not an error it is a warning. Tensorflow still works.

@bennuttall I think this is more than a warning, right?
If you look at @jingw222 's log, it says:
pi@raspberrypi:~ $ python -c "import tensorflow as tf;print(tf.reduce_sum(tf.random.normal([1000, 1000])))" /home/pi/.pyenv/versions/3.6.8/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: compiletime version 3.4 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.6   return f(*args, **kwds) /home/pi/.pyenv/versions/3.6.8/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: builtins.type size changed, may indicate binary incompatibility. Expected 432, got 412   return f(*args, **kwds) Tensor("Sum:0", shape=(), dtype=float32)
A sum of 0 doesn't seem right to me. I get the exact same error.

@bennuttall I think this is more than a warning, right?

RuntimeWarning: compiletime version 3.4 of module

You can turn warnings off: python -W ignore -c "import tensorflow"

A sum of 0 doesn't seem right to me. I get the exact same error.

That's not output, that's the stack trace.
If Tensorflow isn't working for you. I'd suggest showing code examples.


[OOBE] Start-up of Navigation buggy

Microsoft PowerToys version
0.35.0
Running as admin
No
Area(s) with issue?
General
Other Software
No response
Steps to reproduce

Open the Settings window
Click the "Welcome to PowerToys" link
Look closely at the nNavigation

✔ Expected Behavior
None or normal animation
❌ Actual Behavior
There's an animation at the moment the window is opened, but it only applies to Seven of Nine navigation items. First two are stationary.
Also notice the incorrect display of the contents, the very first time.
https://user-images.githubusercontent.com/65828559/113597113-8693c480-963b-11eb-91e0-ad8d7c41efee.mp4

Very rare:

Very rare:

That's strange. We had a bug on this while in pr state. But this should be fixed.
Can you add some details on you monitor setup for investigation, please.
cc: @niels9001

The monitor setup is very standard, 1920x1080 @ 100%. It happened the very fist time while recording, and once later after clicking the link again and again. But like I said: it's rare :)

The monitor setup is very standard, 1920x1080 @ 100%. It happened the very fist time while recording, and once later after clicking the link again and again. But like I said: it's rare :)

For me it's looks like a xaml/winui problem on your system. 🤷

I'm guessing it (the width) has to do with the logic that happens when the window is called for. There are functions like

"window.width=0"
"window.height=0"
"fit into window"
"move to center"

(with the idea to remove flickering) and they all "shake the window around" and the contents just has have to deal with it. I suggest to remove some of these weird things.

I'm guessing it (the width) has to do with the logic that happens when the window is called for. There are functions like

"window.width=0"
"window.height=0"
"fit into window"
"move to center"

(with the idea to remove flickering) and they all "shake the window around" and the contents just has have to deal with it. I suggest to remove some of these weird things.

The move to center must be there to avoid incorrect placing. (Don't know the issue number at the moment.)

#10022

This could totally be an artifact of XAML Islands / NavView WinUI 2.x.  I've never seen it so I'd defer to just the migration then for WinUI 3 rather than fix it here.
After the recalc, it is rendered correctly so i'd put this as a low pri item and there is no clear repro and have the actual fix be the port in #6715

@crutkas Freek and I have been going back and forth about the (rare) visual width bug, but what about the animation that does not get applied to the first two items??

I've noticed the animation quirk as well but that very well could also be a quirk of Islands.  Settings actually has a similar keyboard focus quirk for items 3 and lower.  Looking at the code nothing screamed smoking gun for cause.  Knowing in a few months all this code will go a lift and shift to WinUI3, not something i feel we need to spend time on since they do actual quickly render correctly.

I would like to mention that my name is neither htc nor freek. (htcfreek is a fantasy name made from letters of my name and a misspelled german word.) 😂 You can use htcfreek or Heiko.
@Jay-o-Way
I think this is a xaml bug. The animation is xaml driven and not initiated or manipulated by our code.

@Jay-o-Way Only OOBE suffers from this while we made no UI related changes to the default WinUI controls. I wasn't able to reproduce it on my machine.
I agree with @crutkas that this is probably one of the many visual bugs caused by XAML Islands. (The same code running in UWP does not have these bugs).
Once we adopt WinUI 3 these bugs are hopefully gone, if not let's revisit this issue then :).

I would like to mention that my name is neither htc nor freek. (htcfreek is a fantasy name made from letters of my name and a misspelled german word.) 😂 You can use htcfreek or Heiko.

My apologies. Freek is a plausible name, but I was indeed assuming, since your full name doesn't show next to your screen name :)
For the rest: alright then. 🤐

I would like to mention that my name is neither htc nor freek. (htcfreek is a fantasy name made from letters of my name and a misspelled german word.) 😂 You can use htcfreek or Heiko.

My apologies. Freek is a plausible name, but I was indeed assuming, since your full name doesn't show next to your screen name :)

Added my first name to the profile now. 😂

For the rest: alright then. 🤐

@niels9001 @crutkas @htcfreek Late insight 💡 I now believe the animation is an (unwanted and relatively slow) result of the immediate resizing - first to width & height of zero and back to normal. So, not a xaml bug, but a result of programming.


Doc updates; generating documentation. Will likely need heavy editing.

First attempt generating documentation for a module. Let me know if it's too long/short, if it needs more/less detail, etc.

This looks good to me. Thanks! In this case I think adding examples would be the best documentation, but this does not need to happen in this PR.

Since this PR is all about adding documentation for serialization, may I suggest to look at https://www.boost.org/doc/libs/1_72_0/libs/serialization/doc/index.html to get started? All of Boost's documentation is under the BSL, so there is no need to reinvent the wheel. At least a note that the HPX serialization module was designed to be (mostly) interface compatible with the Boost counterpart and a link to their documentation should be added.

This looks good to me. Thanks! In this case I think adding examples would be the best documentation, but this does not need to happen in this PR.

@rstobaugh did you close this on purpose? As for the examples I don't think we have anything specific in place at the moment but we could reuse the actual implementations we have. For example https://github.com/STEllAR-GROUP/hpx/blob/master/libs/serialization/include/hpx/serialization/complex.hpp just to show how to write the serialize/load/save functions.

@msimberg Sorry, I must have hit the "close and comment" button instead of "comment"; I've reopened it

I can't get my hyperlinks to API references to work; can anyone tell me what I'm doing wrong with this one?

@rstobaugh do you mean this one: https://github.com/STEllAR-GROUP/hpx/pull/4358/files#diff-c8874fed7487477687d7f84b646e05beR39? It should already be correct (it works in our generated documentation: https://stellar-group.github.io/hpx-docs/branches/master/html/libs/serialization/docs/index.html). Could I ask you to try a clean build of the documentation (delete the build directory and configure with CMake again)?

@msimberg Yes, that's the one I'm referring to. I'll have the others show me how to do a clean build of the documentation.

@rstobaugh I think we can go ahead with the content of this PR. Examples can come in a separate PR. Would you mind trying to rebasing on master and squashing the commits? Let me know if you need any help with that.


ZEPPELIN-491: Giving fixed height to container when result type is text

In current behaviour we have a fixed height for result container that contains either graph or table, but if type is text then the container expands to infinitely.
When type is text; then this is mostly logs, so we can have scroll around it and have fixed height for this container.
Before

After

Also I've removed  "loadResultType" function calls, as it did not had any respective loadResultType declaration or implementation.

Also I think this should have scroll to bottom of output button.

Have implement follow scroll to the end and scroll to top.
If there is a streaming output user can always have an eye on end of scroll.

Looks good. Can we get some attention from committers. Thanks!

wow you are building Zeppelin from within Zeppelin ;)
@corneadoug - could you check this out please?

Could you use the same tooltip as everywhere else in zeppelin for those two buttons?

@corneadoug Thanks for the review. I was just experimenting with look and feel of those two buttons, but what you recommend makes more sense.

@corneadoug does this looks ok?

Yes, LGTM

merging if no further discussion


Maesemen/riemann stiff pstar

Fixes pstar convergence. closes #213

For bugs like this, I think that it is a good idea to add a test case that would have caught this error. Is there a test case you can add to catch this?

It would take some work to figure out the conditions for the test case to catch this, but I did check with running a full simulation


Fix DISCO-H745I target name to stm32h745xihx

Fixes #1499

Note that it will raise a memory transfer fault if simply set the target to stm32h745xihx.
The error message is here.

/azp run


manager: Fix test build failure

Fixes a bad merge.

Current coverage is 53.77% (diff: 100%)

Merging #1901 into master will increase coverage by 8.86%

@@             master      #1901   diff @@
==========================================
  Files            34        106      +72
  Lines          4627      18367   +13740
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           2078       9876    +7798
- Misses         2298       7281    +4983
- Partials        251       1210     +959

Powered by Codecov. Last update 2df1a88...64d7433


Chore: Label that disables CI

Is your feature request related to a problem? Please describe.
Maybe it would he helpful to have a label that disables CI? I am sometimes working on a draft and I know that this draft does not yet work at all. Testing it would be a waste of resources. It would be nice if we had a label that disables all testing in such a case.
Let me know what you think about such an idea.

I was not aware that you can write [skip ci]. Where exactly do I have to do that?

And there was a proposal for cases that should work in the other way around

@lmatz Do you have the issue link to that? For me both approaches are fine.

And there was a proposal for cases that should work in the other way around

@lmatz Do you have the issue link to that? For me both approaches are fine.

I just edit the thread above, actually not an approach but a use case

Thank you @lmatz. Let me know if I should close this ticket as a duplicate of https://github.com/risingwavelabs/risingwave/issues/4941


[PR] Add single quotes into electric-pair-pairs for emacs version>24.1  to make it can be autopaired

This variable it original value is:
((?\" . ?\")
    (,(nth 0 electric-quote-chars) . ,(nth 1 electric-quote-chars))
    (,(nth 2 electric-quote-chars) . ,(nth 3 electric-quote-chars)))

So, when we do coding on rust-mode, when we typing  double quotes ",  it can be autopaired into "|" (| is cursor)
But, single quote can't.
After add following code into rust-mode-hook
(add-to-list (make-local-variable 'electric-pair-pairs) '(?' . ?'))

Now, when we typing '|,  it can be autopaired into '|' now, and not take effect others mode. e.g. emacs-lisp-mode
Thank you.

Because ' is used by lifetime parameter, so, maybe this is not a good idea. sorry.

Because ' is used by lifetime parameter, so, maybe this is not a good idea. sorry.

Following is a working solution for:
single quote autopair only valid unless a & is ahead of single quote.
(defvar electric-pair-inhibit-predicate-mode-chars-alist
  '((t . nil))
  "A list of major-mode and inhibit chars.

Each element is in the form of (MODE . (CHAR/CHAR-STRING/CHAR-FUNCTION ...)).

MODE
    A mode, or t for all modes.

CHAR
    A character to match the input. for example:

        ?\{

CHAR-STRING
    A pair of character and string, the character to match the input,
    the string for ‘looking-back’. for example:

        (?\{ . \":{\")

CHAR-FUNCTION
    A pair of character and function, the character to match the input,
    the function accept the input character as parameter. for example:

        (?\{ . (lambda (_c)
                 (eq ?: (char-before (1- (point))))))")

(defun electric-pair-inhibit-predicate-function (c)
  (let ((alist
         (append
          (assoc-default major-mode electric-pair-inhibit-predicate-mode-chars-alist)
          (assoc-default t          electric-pair-inhibit-predicate-mode-chars-alist))))
    (or (cl-member c
                   alist
                   :test
                   (lambda (c it)
                     (cond
                      ((characterp it) (equal c it))
                      ((and (consp it) (equal c (car it)))
                       (cond ((stringp   (cdr it)) (looking-back (cdr it) 1))
                             ((functionp (cdr it)) (funcall (cdr it) c)))))))
        (electric-pair-default-inhibit c))))

(with-eval-after-load 'elec-pair
  (setq electric-pair-inhibit-predicate
        #'electric-pair-inhibit-predicate-function))

(add-to-list 'electric-pair-inhibit-predicate-mode-chars-alist
             '(rust-mode . ((?' . "&'"))))

(add-hook 'rust-mode-hook
          #'(lambda ()
              (modify-syntax-entry ?' "\"" rust-mode-syntax-table)
              ))


chore: format function signature

Description

Introduced a new Param struct with fields for visibility, pattern, type, and span.
Updated FunctionDefinition to use a vector of Param instead of a tuple for its parameters.
Modified various functions and methods across different modules (expression.rs, function.rs, statement.rs, resolver.rs, expr.rs, type_check/mod.rs, and others) to accommodate the new Param structure.
Adjusted parsing logic in parser.rs to construct Param objects instead of tuples.
Made necessary changes in formatting and error handling to align with the new parameter representation.

Problem
Documentation
Check one:

[x] No documentation needed.
[ ] Documentation included in this PR.
[ ] [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

ah...


HDDS-5512. Intermittent failure in SCM HA testInstallSnapshot

What changes were proposed in this pull request?
TestSCMInstallSnapshotWithHA#testInstallSnapshot fails intermittently in CI environment.  PR includes small patch to integration test to fix intermittent problem.  Problem occurs when transactions are added to leader SCM that are then applied to a follower SCM that is placed into the active state from inactive.  Test puts the follower SCM into active state from inactive and expects the follower to install transactions up to leader index when it checks the SCM follower lastAppliedTermIndex, however the updates are done with a nonblocking background thread.  Checking the SCM index in this manner is prone to error due to the nonblocking install.
To fix the intermittent issue, a simple wait and retry construct is used to check the follower index periodically until it updates.  A 3s timeout is used to propagate a fatal error.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5512
How was this patch tested?
Tested though hadoop-ozone/dev-support/checks/integration.sh script in CI environment with environment variables $ITERATIONS=60, $MAVEN_OPTS: -Dhttp.keepAlive=false -Dmaven.wagon.http.pool=false -Dmaven.wagon.http.retryHandler.class=standard -Dmaven.wagon.http.retryHandler.count=3
hadoop-ozone/dev-support/checks/integration.sh  -Dtest=TestSCMInstallSnapshotWithHA#testInstallSnapshot
Run cat target/integration/summary.txt
Iteration 1 exit code: 0
Iteration 2 exit code: 0
Iteration 3 exit code: 0
Iteration 4 exit code: 0
Iteration 5 exit code: 0
Iteration 6 exit code: 0
Iteration 7 exit code: 0
Iteration 8 exit code: 0
Iteration 9 exit code: 0
...
Iteration 60 exit code: 0

Thanks @neils-dev for the fix. It looks good to me.
Thank you for testing it repeatedly via Github Actions. I find it a bit hard to follow, because:

Multiple fixes are present on the branch which is tested by scheduled workflow (HDDS-5358).
The fix relevant for this PR is not the same commit or cherry-pick of this commit.  It has extra log lines which may or may not affect the results (I guess they don't, but still, it's a difference).

I would like to suggest the following process to make it more transparent next time:

Create a branch for the bug (HDDS-5512 here).  Apply the fix, push for full CI.
From that commit start a new branch and change the workflow definition, removing unnecessary checks and adding iterations.  Push for repeated tests.
Once you have enough repetitions, open the PR from the fix-only branch.

I think this setup makes it trivial to check that the same fix proposed in the PR was verified in the repeated runs.

Thanks @adoroszlai for the setup to test and validate with the CI for flaky tests.  I will try it out.  The git actions for you mentioned  (HDDS-5358) that I used was actually meant for other jira issues I was running and used to validate in the CI environ the integration tests for the issues - but it's good that you saw it.

Thanks @neils-dev for the fix, @bshashikant for the review.


Push to main automatically

TL;DR
Would it be possible to have the functionality of release-please without the PR? As in, push directly to main branch without need for approval? thanks
Detailed design
No response
Additional information
No response

This is outside the design of release-please -- we do not and do not plan to support directly pushing to main.
We suggest finding/building an automerge automation if you want this feature.

ok thanks i appreciate the answer! 👍


documentation for clipboardRead and clipboardWrite is inaccurate

The documentation for clipboardRead and clipboardWrite seems to have a couple of typos.  Currently, it is:
clipboardRead | Required if the extension uses document.execCommand('paste').
and
clipboardWrite | Indicates the extension uses document.execCommand('copy') or document.execCommand('cut').
Shouldn't it be:
clipboardRead | Required if the extension uses document.execCommand('copy').
and
clipboardWrite | Indicates the extension uses document.execCommand('paste') or document.execCommand('cut').

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

ID: 90d301ef-7984-899c-dfa8-33a1825f2846
Version Independent ID: 90d301ef-7984-899c-dfa8-33a1825f2846
Content: Declare API permissions in extension manifests - Microsoft Edge Development
Content Source: microsoft-edge/extensions-chromium/developer-guide/declare-permissions.md
Product: microsoft-edge
Technology: extensions
GitHub Login: @MSEdgeTeam
Microsoft Alias: msedgedevrel

Thanks for the question.
I don't think this is a mistake to be honest. I'll need to double check, but here is my understanding:

It's when you paste from the clipboard that you need to read its content.
It's when you copy something to the clipboard that you need to write to it.

Does that make sense?

Yeah, ok.  D’oh. Sorry about that.
Sumit
From: Patrick @.>
Sent: Tuesday, June 6, 2023 2:51 AM
To: @.>
Cc: @.>; @.>
Subject: Re: [MicrosoftDocs/edge-developer] documentation for clipboardRead and clipboardWrite is inaccurate (Issue #2626)
Thanks for the question.
I don't think this is a mistake to be honest. I'll need to double check, but here is my understanding:

It's when you paste from the clipboard that you need to read its content.
It's when you copy something to the clipboard that you need to write to it.

Does that make sense?
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/edge-developer/issues/2626#issuecomment-1578317915, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ADRRBUGRJS6ZAOVJA5DLVTDXJ34RHANCNFSM6AAAAAAY3TGSOE.
You are receiving this because you authored the thread.Message ID: @.***>


The Paint Timing API is now supported by Safari

That is, the stable Safari that ships with iOS 14.5 or macOS 11.4.

BTW it seems a little flakey.
I've a demo page here: https://www.tunetheweb.com/experiments/web-vitals/
And here's the results from Safari 14.1 desktop after several reloads:

As you can see continually reloading the page sometimes leads to FCP being logged, but often doesn't.
Any ideas why?
Seems to be logged a bit more often in Safari Technology Preview (14.2) but still does miss it quite often.
Reloading the page in Chrome, it looks to be consistently logged.
Not sure if this should be raised as a separate issue, or whether it's a Safari issue, or an issue with the Web-Vitals library but thought I'd ask the question here first in case it influences the decision to merge this change or not.

The above comment FYI @noamr, the implementer.

Not sure what call gives you this console message.... Calling this: performance.getEntriesByType('paint') worked for me after every reload, couldn't reproduce a scenario when it didn't

It's this library that produces those logs. Agree it does appear to be there consistently (I added a script to the demo page to log the results of performance.getEntriesByType('paint') on load and it's consistently there).
@philipwalton / @tomayac want me to raise a separate issue for this to move the discussion out of this PR?

It's this library that produces those logs. Agree it does appear to be there consistently (I added a script to the demo page to log the results of performance.getEntriesByType('paint') on load and it's consistently there).
@philipwalton / @tomayac want me to raise a separate issue for this to move the discussion out of this PR?

I'm yielding to Phil. Just bearer of the news here, not a subject matter expert…

@noamr Can you clarify whether the Safari implementation supports use with PerformanceObserver and the buffered flag? Just looking at @bazzadp's demo, I'm assuming that's why it's not being logged.

I don't have Safari 14.5 yet, but based on running the following in STP, it looks like the buffered flag is not supported:
new PerformanceObserver(console.log).observe({type: 'paint', buffered: true});

@noamr Can you clarify whether the Safari implementation supports use with PerformanceObserver and the buffered flag? Just looking at @bazzadp's demo, I'm assuming that's why it's not being logged.

AFAIK The buffered flag is not supported at all in WebKit (for any performance entry). PerformanceObserver should work (without buffered). See https://github.com/web-platform-tests/wpt/tree/master/paint-timing/fcp-only for usage of FCP in a compatible way.

@noamr the buffered flag is supported for resource entry types (at least in STP). I can verify by running the following code in the console:
new PerformanceObserver((l)=>console.log(l.getEntries())).observe({type:'resource', buffered: true});

Looks like it buffered support may have been implemented after paint timing was implemented though. @npm1 did you end up filing a bug for this the we can link to? If not, I can.

@noamr the buffered flag is supported for resource entry types (at least in STP). I can verify by running the following code in the console:
new PerformanceObserver((l)=>console.log(l.getEntries())).observe({type:'resource', buffered: true});

Looks like it buffered support may have been implemented after paint timing was implemented though. @npm1 did you end up filing a bug for this the we can link to? If not, I can.

Ah yes, Igalia did this after paint timing went in. Good to know!

I haven't filed a bug on WebKit, but does seem like it was an omission. I can create a buffered flag test on fcp-only folder if that helps...

I haven't filed a bug on WebKit, but does seem like it was an omission. I can create a buffered flag test on fcp-only folder if that helps...

That and a bug in webkit would probably help...

Filed https://bugs.webkit.org/show_bug.cgi?id=225305

#145 should address the lack of buffered support until https://bugs.webkit.org/show_bug.cgi?id=225305 is addressed. Once a version with that PR is released, I'll merge this PR.

Safari support for buffered: https://bugs.webkit.org/show_bug.cgi?id=225305


KOGITO-7740: KN Workflow plugin does not allow to use RHBQ version

JIRA
https://issues.redhat.com/browse/KOGITO-7740
On this PR

Add [--quarkus-platform-group-id|-G] to change the the Quarkus platform group Id.
Add a P flag for --quarkus-version. Now, the Quarkus version can be also changed with the  -V flag.
Remove the --kogito-version flag, as it should be determined by the quarkus-kogito-bom.
Remove the config subcommand as it should manipulate the bom version instead of extension versions.

Does any of the checks produce the plugin binary to test or should I checkout the branch?

@jstastny-cz The artifacts associated with this PR are available in the last CI :: Monorepo run [1].
[1] https://github.com/kiegroup/kie-tools/actions/runs/2836163777

@ljmotta Hi, do we track changes in documentation that will be needed because of these changes anywhere, please?

I've been able to run successfully command as
kn workflow create --name serverless-workflow-hello-world --extension quarkus-jsonp,quarkus-smallrye-openapi -G com.redhat.quarkus.platform -V 2.7.6.Final-redhat-00006
Looking at the output, there seems to be some unintended fragment popping up in console:
✅ Checking dependencies...
 - Java version check.
 - Maven version check.
-DplatformVersion=2.7.6.Final-redhat-00006Creating a Kogito Serverless Workflow project...
Workflow file created on ./serverless-workflow-hello-world/src/main/resources/workflow.sw.json
🚀 Project creation took: 6.075902689s

specifically -DplatformVersion=2.7.6.Final-redhat-00006 3rd line from the bottom.

@cimbalek These changes will be added in the https://github.com/kiegroup/kogito-docs/pull/135
@jstastny-cz Thanks for testing. Indeed I forgot a log there while I was testing. Could you please re-test? Also, regarding the https://issues.redhat.com/browse/KOGITO-7742, with those fixes, the default bom (quarkus-kogito-bom) should be generated.


fix #525 - plugin can now run standalone .dart files

no package layout required in script's folder

Nice! Thank you :)
On Sat, Jun 13, 2015 at 17:07 Guillermo López-Anglada <
<EMAIL_ADDRESS>wrote:

no package layout required in script's folder

You can view, comment on, or merge this pull request online at:
https://github.com/guillermooo/dart-sublime-bundle/pull/536
Commit Summary

fix #525 - plugin can now run standalone .dart files

File Changes

M run.py
https://github.com/guillermooo/dart-sublime-bundle/pull/536/files#diff-0
(13)

Patch Links:

https://github.com/guillermooo/dart-sublime-bundle/pull/536.patch
https://github.com/guillermooo/dart-sublime-bundle/pull/536.diff

—
Reply to this email directly or view it on GitHub
https://github.com/guillermooo/dart-sublime-bundle/pull/536.


Fix wrong unsupported message

Currently
$ ./vcpkg install libpq[*] --enforce-port-checks --triplet=x64-windows
Computing installation plan...
libpq is only supported on '!windows, mingw', which does not match x64-windows. This usually means that there are known build failures, or runtime problems, when building other platforms. To ignore this and attempt to build libpq anyway, rerun vcpkg with `--allow-unsupported`.

New
$ vcpkg install libpq[*] --enforce-port-checks --triplet=x64-windows
Computing installation plan...
libpq[readline] is only supported on '!windows, mingw', which does not match x64-windows. This usually means that there are known build failures, or runtime problems, when building other platforms. To ignore this and attempt to build libpq anyway,
rerun vcpkg with `--allow-unsupported`.

And
$ ./vcpkg install --allow-unsupported --enforce-port-checks --triplet=x64-windows
warning: libpq[readline] is only supported on '!windows, mingw', which does not match x64-windows. This usually means that there are known build failures, or runtime problems, when building other platforms. To ignore this and attempt to build libpq anyway, rerun vcpkg with `--allow-unsupported`.

New
$ vcpkg install --allow-unsupported --enforce-port-checks --triplet=x64-windows
warning: libpq[readline] is only supported on '!windows, mingw', which does not match x64-windows. This usually means that there are known build failures, or runtime problems, when building other platforms. Proceeding anyway due to `--allow-unsupported`.

Thank you!


NNNN-direct-clean-path-layout  becomes 0011-direct-clean-path-layout for object extensions

0011-direct-clean-path-layout for object extensions is now official community extension for ocfl objects (not storage roots)

Both extensions are now available. The registered extension should be used for objects only.


Resources section to have scrum, note taking articles like that.

Here what all you come across as learning, tools that you make will come here.

Scrum
KMS
etc

write whatever was there i=on your old site

done


device.launchApp won't give notification permissions on 7.3.2

Description
I use detox for testing RN app only on ios and jest as test runner. After upgrade from 7.2.0 to 7.3.2, tests do not pass - they fail on timeout:
Steps to Reproduce
create an app that asks for notification permissions on start.
//App.js
import FCM from 'react-native-fcm';
...
componentDidMount() {
    FCM.requestPermissions()
      .then(() => console.debug('notifications granted'))
      .catch(() => console.debug('notifications rejected'));
}

//init.js
...
beforeAll(async () => {
  await detox.init(config);

  await device.launchApp({
    permissions: {
      notifications: 'YES',
    },
  });
});
...

boot simulator, reset its content and settings,  run detox test and you will see that app starts, and the alert asking for notification permissions shows up, but is not handled by detox. The app will hang in there until the timeout fails the tests.
Interestingly, if you kill the tests before the timeout and run them again, the notification permissions are set and the tests pass.
Detox, Node, Device, Xcode and macOS Versions

Detox: 7.3.2
React Native: 0.53
Node:9.7.1
Device: ios simulator
Xcode: 9.2
macOS: 10.13.3

Device and verbose Detox logs
first run (fails but I killed it before the timeout): gist
second run (succeeds): gist

On the first log, I don't see a call to applesimutils --setPermissions.

I'm not sure why it wouldn't go through the setPermission code path. https://github.com/wix/detox/blob/792a78233e0c634d42b2e605c105cd4c6f6e41de/detox/src/devices/Device.js#L84

I'll try do some debugging and get back to you, or create a minimal repro.
On Fri, Mar 30, 2018, 14:43 Leo Natan<EMAIL_ADDRESS>wrote:

I'm not sure why it wouldn't go through the setPermission code path.
https://github.com/wix/detox/blob/792a78233e0c634d42b2e605c105cd4c6f6e41de/detox/src/devices/Device.js#L84
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wix/detox/issues/653#issuecomment-377516614, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABfmwwxvjsrR9mAC25nO2Q_Xuhwo9IU0ks5tjihrgaJpZM4S_azH
.

sorry, not quite sure what happened, but I cannot reproduce it any more.

If you reproduce again, please open a new issue. Thanks.


candidates2corpus.py: verify that splitters exist

If the splitters specified in the command line do not exist this just fails silently and the script still runs through the entire corpus download.

In https://github.com/ModernMT/DataCollection/blob/65e4700ed46910c1e7e7e7e1bf5a541511650a64/baseline/external_processor.py#L19
subprocess.Popen should throw an OsError exception if the splitter command doesn't exist. Curious why it doesn't in this case.

In the constructor above self.cmd is an array, as the ExternalTextProcessor object is constructed like this:
https://github.com/ModernMT/DataCollection/blob/65e4700ed46910c1e7e7e7e1bf5a541511650a64/baseline/external_processor.py#L82

Well, the splitter is executed in a thread
https://github.com/ModernMT/DataCollection/blob/65e4700ed46910c1e7e7e7e1bf5a541511650a64/baseline/external_processor.py#L31
Can't really catch exceptions in threads https://stackoverflow.com/questions/2829329/catch-a-threads-exception-in-the-caller-thread-in-python
So need to check earlier if command exists.

self.cmd in the Popen call above can be a command string or an array. Only if it is an array one can check if the first parameter is actually an available command (either checking the full path and/or searching for it in PATH). This would only partially fix the problem. Not fixing this for now.
Needs to be looked into with larger context how to call the splitters from the script https://stackoverflow.com/questions/2629680/deciding-among-subprocess-multiprocessing-and-thread-in-python


[msal-node] Cache-1: Msal node cache entities

This is the first PR for "Cache" supporting UnifiedSchema for msal-node.This PR adds cache entries for the below entities:

Account
AccessToken
IdToken
RefreshToken
AppMetadata

Thanks @sangonzal, regarding the naming, I agree with you, I wasn't a fan of the name as it was too long but may be we should add it to be accurate.

Coverage decreased (-2.7%) to 78.531% when pulling b6803bae11e9548b5f098da0fa04372199db6636 on msal-node-cache-entities into ad1a86c2196b7313516c49cfabb9fddf0dfb0c22 on dev.

@jasonnutter  Since I got a verbal ACK last time on this PR, I am merging this. If there are any comments, future PRs can attest to them. Since we have too many changes to be pushed to dev going forward, I did not want to wait. Thanks.


How does one uninstall everything?

Hi,
I have found most of the folders that this package installs to, it's quite spread out on Windows. Is there a good way to uninstall everything if needed?

Hi,

pip uninstall chatdocs will uninstall the tool. You can use Python virtual environments to install which will make uninstalling easier as you can just delete the venv directory.
C:\Users\USERNAME\.cache\huggingface\hub contains downloaded models.
C:\Users\USERNAME\AppData\Roaming\nltk_data may contain some downloaded data.


Rendered mermaid graphs mess up anchor positions of subsequent content

Not sure if this is an issue of the way the plugin works or of mermaid graphs in general, but I have an issue that in certain situations, the size of mermaid graphs is not taken into account when jumping to anchors below these graphs.
For example take this link: https://rollupjs.org/plugin-development/#renderdynamicimport
It should directly jump to the corresponding section in the Rollup docs, but very often, it ends up quite a bit further up on the page. The offset roughly corresponds to the size of two large mermaid graphs embedded in the page further up here and here.
The problem does not occur when navigating within the page but only when either directly opening such a link in a new tab or navigating from a different page. Also, links above the graphs work correctly like this one https://rollupjs.org/plugin-development/#build-hooks.
There also seem to be subtle differences between browsers, e.g. for me Chrome sometimes worked while Safari seemed reliably broken. Not sure if there is anything that can be done from plugin side and I admit, I did not do any deeper debugging yet. Maybe others noticed the issue as well and have some deeper insights?
Page source is here https://github.com/rollup/rollup/blob/master/docs/plugin-development/index.md

Hi @lukastaegert  can you try the last version of mermaid and vitepress?
the links above are working for me but you probably change your code.

In the meantime I actually converted to pre-compiling the page with mermaid CLI and no longer use the plugin. This has the advantage that I do not need mermaid in my runtime, but may not be a solution for everyone.

Thanks for taking the time to look into this, though.


I can't escape special characters

Hi everyone,
I can't understand how to escape dash when I send the query to opensearch.
I'm using this structure to search on every field in my index:
{
    "index": "preg",
    "body": {
        "query": {
            "bool": {
                "must": [
                    {
                        "query_string": {
                            "query": "*2022*"
                        }
                    },
                    {
                        "bool": {
                            "should": [
                                {
                                    "match": {
                                        "owner": 6
                                    }
                                },
                                {
                                    "match": {
                                        "owner": 2
                                    }
                                }
                            ]
                        }
                    }
                ]
            }
        }
    }
}

and everything works fine.
But when I add a dash to the date (2022-), no items are found.
I tried with "2022\-" but it still doesn't work.
Can you tell me what is the correct way to escape special chars?

I think the best place for a question like this would be the OpenSearch forum: https://forum.opensearch.org/
If you post here, you'll target the js topic area: https://forum.opensearch.org/tags/c/clients/60/opensearch-js

you're right, sorry.


[BEAM-11611] Add transformation for computing approximate quantiles.

Adds a new transform to the stats package: Approximate Quantiles. This allows approximately computing quantiles for given comparable data.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @lostluck

Thanks for the acknowledgement 👍 and looking forward to your review. Let me know if there's anything I can do to help.


Total obtained does not match specific items collected. Please re-upload collection log data.

What are you experiencing, describe the bug
Please provide a clear and concise description so triage will be easier. Provide screenshots of the bug if applicable.
"Total obtained does not match specific items collected. Please re-upload collection log data." on website, even after resetting, recalculating, reuploading etc.
How are you expecting it would work?
Please provide a clear and concise description what your expectation is. This provides a better context for the bug.

Please supply your in-game username if applicable.
gnarly nacho

So, the intent of the message is to indicate that there's missing data for some specific items. The plugin (currently) is only able to grab the total unique item count (as shown on your account as the 833/1443), and any items on pages that you've iterated through with the plugin open. If you were to add all of the unique items listed under your account on the website, it wouldn't add to 833, and that's where the message comes from.
I believe @evansloan is working on an update to the plugin that will mitigate this, but until then, there isn't a catch-all solution.
Perhaps it's worthwhile to add something to the FAQ (and link to it from the message) in the meanwhile?

Thank you for the response, I appreciate it. I'm imagining it's brought on by me getting coll log slots on other clients (mobile). Something in the FAQ would be useful, although I mainly reported just incase nobody else had this issue yet. Again, thank you for everything you guys do :)

@gnarlynacho If you open it in RL and iterate through each page it'll correct it.

Awesome, have heard loads of good things in my cc about the recent updates :)


Writing matrix to by using feather in Julia

The problem here is that: When we want to transfer a matrix  from Julia to Python, we need to convert the matrix to dataframe first, and then save it by using feather.
However, when it saves a dataframe, we can see that the first row is 1   │<PHONE_NUMBER> │<PHONE_NUMBER>, which should not be the case.

I'm not sure if it is the bug of the package or the problem or myself...
Maybe we should think another way to do it? However, it will also happen for dataframe in Julia.

I will take care of it. Are you safely at home? The rain is getting bigger.

I am! Thanks Professor! 😄  Went back home at 2:00 pm from office today. And I bought a lot of food and water as well. Be safe too Professor!!! 💪

It somehow works fine here...? 😕

Yes, I added parameter nullable=false, not sure if it helped.


IslandwoodHouse application launch fails on develop daily build - 20161209.1

Build configuration: Release - desktop
Pass rate for this app seems to be 60%. We need to understand why.

This is a stale issue. Closing out.


'devspace enter' session is interrupted

Not sure whether this is a bug. Problem is somewhat similar to this issue, but I am not on windows (ubuntu). I have devspace (without helm) and exec into three processes (once with devspace dev and twice with devspace enter) into two containers. So:
A) one process on container A
B) two processes on container B
I lose contact (suddenly instead of terminal output I get a prompt) with (especially with B) quite often. Output seems to vary, e.g. last time I got:
errors.log:
{"level":"info","msg":"Sync started on /home/usr/api/trex \u003c-\u003e /home/usr (Pod: default/mymarkers-6cb47df99f-rv4ws)","time":"2019-03-27T22:48:43+01:00"}
{"level":"info","msg":"Opening shell to pod:container \u001b[1;37mmyapp-7cc4dc5c56-4hkvp\u001b[0m:\u001b[1;37mapp\u001b[0m","time":"2019-03-27T22:49:58+01:00"}
{"level":"fatal","msg":"[Sync] Fatal sync error: \n[Downstream] Stream closed unexpectedly. For more information check .devspace/logs/sync.log","time":"2019-03-28T08:04:50+01:00"}

sync.log:
{"container":"/home/usr","level":"info","local":"/home/usr/api/trex","msg":"[Upstream] Successfully processed 12 change(s)","pod":"mymarkers-6cb47df99f-rv4ws","time":"2019-03-27T22:48:45+01:00"}
{"container":"/home/usr","level":"info","local":"/home/usr/api/trex","msg":"[Sync] Sync stopped","pod":"mymarkers-6cb47df99f-rv4ws","time":"2019-03-28T08:04:50+01:00"}
{"container":"/home/usr","level":"error","local":"/home/usr/api/trex","msg":"Error: \n[Downstream] Stream closed unexpectedly, Stack: \n[Downstream] Stream closed unexpectedly\n/Users/travis/gopath/src/github.com/devspace-cloud/devspace/pkg/devspace/sync/downstream.go:187: \n/Users/travis/gopath/src/github.com/devspace-cloud/devspace/pkg/devspace/sync/downstream.go:114: ","pod":"mymarkers-6cb47df99f-rv4ws","time":"2019-03-28T08:04:50+01:00"}

What is causing this? Is it a loss of internet connection? That is odd, since when I disconnect my internet and reconnect it still can continue the sessions, so seems a slight internet connection disruption should cause no problems.
And furthermore: When getting the prompt and then devspace enter into the same container and trying to restart the service (server), it gives connection error as process seems to be still running in background. Can I somehow reattach to the (PID) process with a terminal screen?

In my errors.log I find in enormous amount of this type of error:
{"level":"error","msg":"Runtime error occurred: an error occurred forwarding 9229 -\u003e 9229: error forwarding port 9229 to pod 38808f5233094765db6b8f626855bb061bc6998a94c1240e641e5573ee792e84, uid : exit status 1: 2019/03/28 15:25:50 socat[113437] E connect(5, AF=2 <IP_ADDRESS>:9229, 16): Connection refused\n","time":"2019-03-28T16:25:50+01:00"}

And then at the end:
{"level":"error","msg":"Runtime error occurred: an error occurred forwarding 9229 -\u003e 9229: error forwarding port 9229 to pod 38808f5233094765db6b8f626855bb061bc6998a94c1240e641e5573ee792e84, uid : exit status 1: 2019/03/28 15:25:50 socat[113437] E connect(5, AF=2 <IP_ADDRESS>:9229, 16): Connection refused\n","time":"2019-03-28T16:25:50+01:00"}
{"level":"error","msg":"Runtime error occurred: an error occurred forwarding 9229 -\u003e 9229: error forwarding port 9229 to pod 38808f5233094765db6b8f626855bb061bc6998a94c1240e641e5573ee792e84, uid : exit status 1: 2019/03/28 15:25:50 socat[113438] E connect(5, AF=2 <IP_ADDRESS>:9229, 16): Connection refused\n","time":"2019-03-28T16:25:50+01:00"}
{"level":"error","msg":"Runtime error occurred: an error occurred forwarding 9229 -\u003e 9229: error forwarding port 9229 to pod 38808f5233094765db6b8f626855bb061bc6998a94c1240e641e5573ee792e84, uid : exit status 1: 2019/03/28 15:25:51 socat[113500] E connect(5, AF=2 <IP_ADDRESS>:9229, 16): Connection refused\n","time":"2019-03-28T16:25:51+01:00"}
{"level":"error","msg":"Runtime error occurred: an error occurred forwarding 9229 -\u003e 9229: error forwarding port 9229 to pod 38808f5233094765db6b8f626855bb061bc6998a94c1240e641e5573ee792e84, uid : exit status 1: 2019/03/28 15:25:51 socat[113503] E connect(5, AF=2 <IP_ADDRESS>:9229, 16): Connection refused\n","time":"2019-03-28T16:25:51+01:00"}
{"level":"error","msg":"Runtime error occurred: an error occurred forwarding 9229 -\u003e 9229: error forwarding port 9229 to pod 38808f5233094765db6b8f626855bb061bc6998a94c1240e641e5573ee792e84, uid : exit status 1: 2019/03/28 15:25:52 socat[113507] E connect(5, AF=2 <IP_ADDRESS>:9229, 16): Connection refused\n","time":"2019-03-28T16:25:53+01:00"}
{"level":"error","msg":"Runtime error occurred: an error occurred forwarding 9229 -\u003e 9229: error forwarding port 9229 to pod 38808f5233094765db6b8f626855bb061bc6998a94c1240e641e5573ee792e84, uid : exit status 1: 2019/03/28 15:25:53 socat[113508] E connect(5, AF=2 <IP_ADDRESS>:9229, 16): Connection refused\n","time":"2019-03-28T16:25:53+01:00"}
{"level":"error","msg":"Runtime error occurred: an error occurred forwarding 9229 -\u003e 9229: error forwarding port 9229 to pod 38808f5233094765db6b8f626855bb061bc6998a94c1240e641e5573ee792e84, uid : exit status 1: 2019/03/28 15:25:54 socat[113537] E connect(5, AF=2 <IP_ADDRESS>:9229, 16): Connection refused\n","time":"2019-03-28T16:25:54+01:00"}
{"level":"error","msg":"Runtime error occurred: an error occurred forwarding 9229 -\u003e 9229: error forwarding port 9229 to pod 38808f5233094765db6b8f626855bb061bc6998a94c1240e641e5573ee792e84, uid : exit status 1: 2019/03/28 15:25:54 socat[113538] E connect(5, AF=2 <IP_ADDRESS>:9229, 16): Connection refused\n","time":"2019-03-28T16:25:54+01:00"}
{"level":"error","msg":"Runtime error occurred: lost connection to pod","time":"2019-03-28T16:25:55+01:00"}
{"level":"error","msg":"Runtime error occurred: lost connection to pod","time":"2019-03-28T16:25:55+01:00"}
{"level":"error","msg":"Runtime error occurred: EOF","time":"2019-03-28T16:25:55+01:00"}
{"level":"error","msg":"Runtime error occurred: EOF","time":"2019-03-28T16:25:55+01:00"}
{"level":"error","msg":"Runtime error occurred: error creating error stream for port 9229 -\u003e 9229: Timeout occurred","time":"2019-03-28T16:26:25+01:00"}
{"level":"error","msg":"Runtime error occurred: EOF","time":"2019-03-28T16:27:54+01:00"}
{"level":"error","msg":"Runtime error occurred: EOF","time":"2019-03-28T16:27:54+01:00"}

Any suggestions how to solve the refusal of connection or is this 'normal'...?

Thanks for opening this issue @musicformellons . I looked through your logs and usually I get the 'Stream closed unexpectedly' when the container somehow crashes or restarts. The 'Runtime error occured' logs are related to port forwarding, which seem to indicate that somehow the connection to the pod was interrupted, which is the case either because the pod seems to have restarted or because of a connection disruption.
@KaelBaldwin could solve the issues by upgrading his cluster to a newer version, because it seems that sometimes the connection disruption is caused by kubernetes itself (not sure why though, maybe a bug in kubectl or the api server itself). You can check if kubernetes is the problem by also running 'kubectl port-forward' or 'kubectl exec' along with the devspace commands, because the sync and port-forwarding are using essentially these commands internally. If they are also interrupted after a while, kubernetes seems to be the problem, otherwise there is an issue in devspace we somehow have to investigate.
Regarding your question:

Can I somehow reattach to the (PID) process with a terminal screen?
Unfortunately I don't think this is possible currently, kubernetes gives us no option to attach to a specific PID yet, so the only solution is to restart the server on devspace enter.

Ok, thanks for the pointers! I am upgrading my kubernetes right now, so maybe that helps. The error Runtime error occurred: an error occurred forwarding 9229 happens like twice every second. Within my cluster the 9229 port is not really necessary, but as far as I remember it used to be configured by Devspace for 'debugging'. However in current docs I do not find this any longer, so maybe I can just get rid  of it?

9229 is the node debugger port, which is only necessary if want to debug node applications locally. You can just delete that if you don't use it

'Debug node application locally', I suppose that means: I edit on my local machine and then it syncs my changes to my kubernetes cloud? That's essential to me.
My current portforwarding config:
  ports:
  - labelSelector:
      app: myapp-pod
    portMappings:
    - localPort: 8089
      remotePort: 8089
    - localPort: 8088
      remotePort: 8088
    - localPort: 9229
      remotePort: 9229
  - labelSelector:
      app: mymarkers-pod
    portMappings:
    - localPort: 8081
      remotePort: 8081
    - localPort: 8011
      remotePort: 8011
    - localPort: 8060
      remotePort: 8060
    - localPort: 9229
      remotePort: 9229

Does using 9229 on both pods give conflicts, or should that be ok?

No with debug node applications locally I mean attaching a node debugger to your remotely running node application, I guess in your use case you just want to sync file changes which is not affected by this, so I think you can remove the 9229 port.

Ah, that makes sense! I will get rid of it!

Looks solved now.

Actually was not really solved... After updating Kubernetes and Devspace and change correct ports I still have basically the same behavior: My session is ended and I have to devspace purge and devspace dev to have a working session again. Only error log I find:
{"level":"error","msg":"Runtime error occurred: EOF","time":"2019-05-02T17:14:42+02:00"}

@musicformellons mhh that is odd, could you try to open a kubectl exec shell in parallel to see if that loses connection aswell? I don't think you have to run devspace purge everytime the terminal loses connection, you could just run ps aux in the new shell afterwards and kill the still running processes.

Ok, will test kubectl exec. Regarding your interesting suggestion on devspace purge probably being unnecessary: When I ps aux on my local machine I can not find 'what process to kill' (lsof -i  does not return anything), which in a way makes sense as the connection seems dropped locally. When I try to devspace enter it works but when I start the server in my app it gives 'connection already in use error', and when I want to kill it there I do not have these tools installed in my container. So does not really work for me it seems.

I tried twice and both times the kubectl connection to the two pods also lost connection. Error logs in devspace:
{"level":"error","msg":"Runtime error occurred: lost connection to pod","time":"2019-05-06T01:32:46+02:00"}
{"level":"error","msg":"Runtime error occurred: lost connection to pod","time":"2019-05-06T01:33:12+02:00"}
{"level":"error","msg":"Runtime error occurred: EOF","time":"2019-05-06T07:41:34+02:00"}
{"level":"error","msg":"Runtime error occurred: write |1: broken pipe","time":"2019-05-06T07:41:34+02:00"}
{"level":"error","msg":"Runtime error occurred: EOF","time":"2019-05-06T07:41:34+02:00"}
{"level":"error","msg":"Runtime error occurred: EOF","time":"2019-05-06T07:41:34+02:00"}

@musicformellons Thanks for testing that out! Unfortunately I don't think we can do much about this issue I think, because internally we just use the kubectl functionality. This seems to be more of a problem with the general cli streaming functionality. The error logs also indicate that somehow the connection to the pod was lost, I cannot really tell why though.

As I am using Istio (on GKE) this might be related.

@musicformellons Is this still an issue for you with the newest version of DevSpace CLI or can we close this issue?

It still is an issue...

Solved through issue #643 !!

Very glad it solved the issue!


Fix desktop icons and do not disturb behavior

We can save what the setting was when we start recording and use that when we stop, instead of pulling it from the store again, to avoid mismatch if the settings changed mid-recording.
This way we don't have to hide the Preferences window

This way we don't have to hide the Preferences window

I still think we should hide it during recording though. You wouldn't want it in the recording and there might be other synchronization issues we haven't thought of.


--without=rust-docs breaks installs with Rust <IP_ADDRESS>

See esp-rs/espup#92, the issue is the same
https://github.com/esp-rs/rust-build/blob/main/install-rust-toolchain.sh#L227
https://github.com/esp-rs/rust-build/blob/main/install-rust-toolchain.sh#L234

Closed by #183


added SHA-1 hashing algorithm detection regex

added SHA-1 hashing algorithm detection regex, a really usefull feature
⚠ Pull Requests not made with this template will be automatically closed 🔥
Prerequisites

[x] Have you read the documentation on contributing? https://github.com/bee-san/pyWhat/wiki/Adding-your-own-Regex

Why do we need this pull request?

Explain the why behind your PR. We can see what it does from the code. But why does it do that?

This is a common algorithm that is currently undetected by this application

What GitHub issues does this fix?

Fixes #10000

Copy / paste of output
Please copy and paste the output of PyWhat with your new addition using an example that tests this addition below:
> what "A14D3682C92974987D0CB5B1CC61D2D098D9CD51"

Matched on: A14D3682C92974987D0CB5B1CC61D2D098D9CD51
Name: SHA-1 hash format
Description: SHA-1 algoritm, used to check integrability of a file.

Hey sorry but we don't want hashes in pywhat, you can use name-that-hash for this :) https://github.com/HashPals/Name-That-Hash


Incorrect production time for batteries

Should be 4 sec, not 5 sec.
https://wiki.factorio.com/Battery

Similar problem with explosives, crafting time is also 4 s (per craft of 2), not 5s.
Also the timing for all three solid fuel recipes is wrong, it should be 2 s instead of 3 s.


ng-Google-Maps and Ng-inspector

IMPORTANT:
ng-inspector is not working after embedding ng-map on my website and also it hangs the google chrome.

Are you on the correct repository? this uses ng-map as the directive name.

yes, i updated my comment

Hi I'm not using ng-map nor ng-google-maps, just a custom directive with a google map div and it's freezing too...


A user should only be able to add a club for themselves

The Owner name and Owner email fields in the AddClubPage should be prefilled with the user's information and be given the "disabled" attribute to prevent changes. This ensures that a user can only create a club for themselves.

Implemented. The currently logged in user will see their name and email address in the Owner and Owner email fields respectively.

Admin users will also see the same. The club that is created will have the admin's name and email address in the information for the club, but the admin user themselves will not be listed as a member. This is because an Admin user is not a member of any club.


owmweather: upgrade to One Call API 3.0

One Call API 2.5 will be deprecated in June 2024.
Upgrade to One Call API 3.0.
Add pressure to weather.json

Thanks!


Bundle td-pyspark

td-pyspark gives easier access to TD databases, tables, and Plazma APIs. Plus, since the package internally bundles td-spark JAR file, SparkWriter does not necessarily have to download the JAR file at the first time.

@Lewuathe Just let you know that pytd has started using td_pyspark. Let me know if you noticed something weird :)


add spec for the @disable new(); allocator relic

Is that actually implemented still? I thought it was removed (but would be very happy to see it still here, it is useful)

Yes, I've managed to keep it when working on the final deprecation step, see https://github.com/dlang/dmd/pull/11581.

And the author is gone.

we could fork the PR if need be

There is no reason to left this PR open if isn't going to be merge.

This PR is already linked in dlang/dmd#11581 and the author is gone. If anyone wants to adopt this, we can reopen.

This PR is already linked in dlang/dmd#11581 and the author is gone. If anyone wants to adopt this, we can reopen.


⚠ POST to /fact_check has degraded performance

In 09dc5cc, POST to /fact_check (https://dev.factiverse.no/v1/fact_check) experienced degraded performance:

HTTP code: 200
Response time: 24161 ms

Resolved: POST to /fact_check performance has improved in c023924.


[RESOLVED] S100-Primario has been restarted (uptime < 10m)

Problem started at 20:11:29 on 2023.05.24
Problem name: S100-Primario has been restarted (uptime < 10m)
Host: S100-Primario
Severity: Warning
Operational data: 00:06:15
Original problem ID: 22336
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23452&eventid=22336

Problem has been resolved in 4m 0s at 20:15:29 on 2023.05.24
Problem name: S100-Primario has been restarted (uptime < 10m)
Host: S100-Primario
Severity: Warning
Original problem ID: 22336


modernize project setup:

use poetry
add isort
run tests with pytest and tox
expand Makefile

What's with the binary .coverage file? This does not look like something we should check in.

What's with the binary .coverage file? This does not look like something we should check in.

Oh, sorry. Removed.


[OPPRO-326] Add byte array bool validation

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@rui-mo
Please help to review. Thanks for your help!


[ModuleInterfaces] Rename 'parseable interfaces' to 'module interfaces'

Cherry-pick of #23969 to 5.1.

@swift-ci please test


Conflict detection for default optionsets

We would like to protect against duplicate optionsets, and need to check for optionsets that already exist in PowerFx as defaults. SymbolTable.TryLookupSlot currently returns false for default optionsets, so we need another way to perform this logic. We also need to be able to get back the optionset FormulaType to convert between our internal wrapped type and the true PowerFx type. TIA

Today, optionSets are added via Config and that just adds an entity
https://github.com/microsoft/Power-Fx/blob/78ad88658ec02308c1f1108b0729f42518f50fb7/src/libraries/Microsoft.PowerFx.Core/Public/Config/PowerFxConfig.cs#L164
Add this to ReadOnlySymbolTable:
        public bool TryLookupOptionSet(string name, out OptionSet slot)

And ensure that this can indeed find builtin option sets, like Color, etc.
see examples here: https://github.com/microsoft/Power-Fx/blob/main/src/libraries/Microsoft.PowerFx.Core/Types/Enums/EnumStoreBuilder.cs

This gets a bit more interesting since Color is an EnumSymbol (internal), not an OptionSet (public).
They both implement IExternalOptionSet - which is internal.


Demo STGneuron not working

Hi @wsphillips !
I tried to run the STGneuron file in the demo folder, with a freshly downloaded Conductor, and get this error:
WARNING: could not import Conductor.Cationic into Main
ERROR: LoadError: MethodError: no method matching MembranePotential(::Quantity{Int64, 𝐋² 𝐌 𝐈⁻¹ 𝐓⁻³, Unitful.FreeUnits{(mV,), 𝐋² 𝐌 𝐈⁻¹ 𝐓⁻³, nothing}})
Closest candidates are:
  MembranePotential() at ~/.julia/packages/Conductor/idY1O/src/Conductor.jl:95

Stacktrace:
 [1] top-level scope
   @ ~/.julia/dev/Conductor/demo/prinz_kinetics.jl:6
in expression starting at /Users/andrearamirez/.julia/dev/Conductor/demo/prinz_kinetics.jl:6

These are the packages in my environment
Status `~/.julia/dev/Conductor/demo/Project.toml`
  [d194a933] Conductor v0.0.2
  [615f187c] IfElse v0.1.1
  [961ee093] ModelingToolkit v6.4.9
  [1dea7af3] OrdinaryDiffEq v6.7.1
  [91a5bcdd] Plots v1.27.1
  [295af30f] Revise v3.3.3
  [1986cc42] Unitful v1.11.0

and I'm using Julia Version 1.7.0.
The same error shows up when I try to run STGnetwork.jl and hodgkinhuxley.jl. These demos should work straight from the src code, right?
Thanks for your help!

Hi @AndreaRamirezH
I can get STGneuron.jl and hodgkinhuxley.jl both running with the following setup:
Julia v. 1.7.2
    Project Conductor v0.0.2       Status~/Documents/GitHub/Conductor.jl/Project.toml   [479239e8] Catalyst v10.7.0   [615f187c] IfElse v0.1.1   [1914dd2f] MacroTools v0.5.9   [961ee093] ModelingToolkit v8.5.2   [1dea7af3] OrdinaryDiffEq v6.7.1   [91a5bcdd] Plots v1.27.1   [efcf1570] Setfield v0.8.2   [d1185830] SymbolicUtils v0.19.7   [0c5d862f] Symbolics v4.3.1   [1986cc42] Unitful v1.11.0   [b77e0a4c] InteractiveUtils
I think the critical package(s) here are Symbolics (and SymbolicUtils?). The other discrepancies may be needed to glue things together though (e.g. ModelingToolkit update for compatibility with the preceding?).
I'm getting a different error with STGnetwork.jl - will poke it and see what I can find.
Hopefully this gets you moving though!
Oh and you might get send: Broken pipe at the last step rather than a plot, usually just re-running the script will work.

For STGnetwork.jl I get errors via prinz_synapses.jl calling Gate and EquilibriumPotential. Re ordering the parameter calls might be sufficient.
I've made a related minimal PR #23 for the moment; next trial step is swapping out Soma for CompartmentSystem in STGnetwork.jl but think I will need to look at MTK to make progress.

Hi @pfcrowe
You're right, activating the environment using the Project.toml file inside the demo folder was not giving me those two packages (Symbolics and SymbolicsUtils).
I updated all packages listed in the dependencies (in here: /.julia/dev/Conductor/Project.toml) and it works :)
I guess the question now is, should there be two different Project and Manifest files? Why are there Manifest and Project files in the demo?
Both STGneuron.jl and hodgkinhuxley.jl work fine, but I get the same error you mention with STGnetwork.
ERROR: LoadError: MethodError: no method matching Conductor.GatingVariable(::Conductor.GateVarForm, ::Symbol, ::Num, ::Num, ::Int64)
Closest candidates are:
  Conductor.GatingVariable(::Any, ::Any, ::Any, ::Any, ::Any, ::Any, ::Any) at ~/.julia/dev/Conductor/src/gates.jl:16
  Conductor.GatingVariable(::Conductor.GateVarForm, ::Num, ::Num, ::Real; name) at ~/.julia/dev/Conductor/src/gates.jl:27
  Conductor.GatingVariable(::Num, ::Num, ::Num, ::Num, ::Num, ::Real, ::Conductor.GateVarType) at ~/.julia/dev/Conductor/src/gates.jl:16
  ...
Stacktrace:
 [1] top-level scope
   @ ~/.julia/dev/Conductor/demo/prinz_synapses.jl:3
in expression starting at /Users/andrearamirez/.julia/dev/Conductor/demo/prinz_synapses.jl:3

Thanks for your help!!

Hey sorry for some reason I didn't get a ping when you opened this issue.
First question: Are you both working with the latest tagged version on the registry or the latest commit to main?
Networks are definitely broken on the main branch at the moment because I simply haven't finished implementing NetworkSystem in the same manner as CompartmentSystem and ConductanceSystem

Yeah ok. The problem is you're probably both using package/demo files that are out of sync. This is partly because I made some mistakes with the Project/Manifest files.
The tagged version of Conductor.jl on the public registry is older, but should work for ALL demos. This is the version of Conductor.jl you get if you ]add Conductor.jl. (v0.0.2)
If you dev Conductor.jl you will get the latest commit on the main branch, which definitely has some broken bits!
So first, be careful to distinguish whether you are running the v0.0.2 tag or the latest commit of main. I just pushed a version bump to main to make this more obvious on fresh installations. Now if you accidentally dev Conductor.jl without checking out the stable version, it will display version 0.0.3 in the package manager.
If you choose to dev Conductor and you want to run all the demo files, you will have to change to the v0.0.2 tag in the development directory with git checkout v0.0.2 (e.g. inside the .julia/dev/Conductor.jl by default)
If you add Conductor it will install v0.0.2 by default at the moment.
When running the demo, it does appear there's some weirdness because of version changes since I tagged the repo, but you can try the following (I've got this to work on my end):
Once you're sure you have Conductor v0.0.2 installed, go to the demo directory. If you used add Conductor, it might be easier to clone a copy of Conductor.jl to an easily reached directory (and remember to checkout v0.0.2!)
Then, in the demo directory:

julia --project=.
(in package mode) instantiate
(in package mode) up
Run the demo script you want while in the project environment. Best if you go line by line from an editor/IDE

Note: Right now you'll need to up to fix some compatibility issues. This has a side effect of bumping up the version of MTK, which changes the plot recipes. Therefore, to plot the output by variable name, you'll need to use the kwarg vars=[Vₘ] (or similar) in most cases.
Finally, if you're planning to contribute to development, note that the instructions above use the last stable version to get the demos working. However, a lot has changed since then. If you're working with the latest commit on the main branch, the single neuron examples should work but anything with synapses should NOT work right now. That's because of the comment I made earlier:

Networks are definitely broken on the main branch at the moment because I simply haven't finished implementing https://github.com/wsphillips/Conductor.jl/pull/18 in the same manner as CompartmentSystem and ConductanceSystem

In STGNetwork.jl using v0.0.2 there's a missing import Unitful.nS. Otherwise, it works using instructions above.

Hi @wsphillips
Yup, that was it. I was getting the main branch when doing dev, indeed.
Thanks for clarifying the instructions to get to the stable v0.0.2. I was trying to simply try out the single neurons so this should be enough. Will be looking forward to testing the network when it's ready! ;)

Thanks @wsphillips that was also my case - your instructions were accurate throughout including for the plotting variable.
Wrt development, would you be interested in mentoring J/GSoC this year?

hey @wsphillips i thought to bump this and will follow up with an email - not sure if you are getting pinged as you mentioned. I'm interested in whether or not conductor.jl would be suited to a j/gsoc project - I guess a first question from my side is would this be feasible for you over the relevant period, assuming 350h over min 10 max 22 weeks (targeting 15w?).

relatedly @ChrisRackauckas is Conductor.jl a sufficient priority within the Julia (SciML/NumFOCUS?) ecosystem to merit competitiveness for j/gsoc (this round)?

sorry for hijacking this thread 😄

I'd be happy to see it move to SciML and make it a GSoC project, and I could help mentor though it would need @wsphillips involved too.

(BTW, remember that SciML GSoC is through NumFOCUS, not JuliaLang)

Hi Peter,
I'm open to the possibility of mentoring a GSoC project. Aside from an application (see guidelines), we'd like to see a non-trivial trial PR for Conductor.jl.
Given that you now have the stable tagged version of Conductor.jl working, you can explore it a bit to get a rough idea of how things work. Once you feel comfortable, bump up to the latest commit on the development branch. You'll find that there's some changes happening in the structure of the package. Not everything works or is finished yet, but you ought to be able to at least simulate single neurons.
As you're getting familiar with the code base, you may find it helpful to also cross-reference the source for ModelingToolkit.jl itself, as well as Catalyst.jl.
You can take a stab at an open issue/PR or propose something yourself. If you want to bounce ideas off of me, you can email me or ping me on Slack.
Since both @pfcrowe and @AndreaRamirezH seem to have demos running now, I'm going to close this issue. GSoC discussion we can do via other channels.


Migrate latest.py from endoflife.date to release-data

It makes more sense as it closely related to the JSON version file format, which is more subject to change than the product file format.

Checked in deploy logs, works as expected. Merging.

@captn3m0 FYI

Good idea, but this reduces testability of the script? Worth adding a test-harness for this in the release-data repo now perhaps.


feat(kibbeh): add bot badges to many places

add bot badges to many places

here's what it looks like:

Why can't on the avatar one it just have a bot label next to it's name?

much bad

Why can't on the avatar one it just have a bot label next to it's name?

looks bad

@benawad @ajmnz if you don't like the icons or the placement just tell me on disc, ill change it


[Task]:Add Merge Join deadlock example to "Avoiding deadlocks..."

What needs to happen?

Add Merge Join deadlock example
Rename page to “Avoiding deadlocks”

Issue Priority
Priority: 3
Issue Component
Component: Documentation

.take-issue


Integration tests use mobile clients

Apparently the IOS client stopped working while we weren't watching.  That client should be added to the server's integration tests.

Will fix https://github.com/m-lab/ndt7-client-ios/issues/57

Two subtasks:

getting the library tested
fixing the underlying problems


[AJ-661] array representation in WDS data tables

https://broadworkbench.atlassian.net/browse/AJ-661
Fix handling of array column in WDS-powered data tables. Arrays should now behave the same way they do in Entity Service-powered data tables. (note: editing is intentionally not supported)
Before:

After:

Additionally, fix translation of WDS relations to Entity Service references.
Tested manually, and added unit tests.

Tried adding an "array of relations"
{   "attributes": {     "number": 123,     "relationArr": ["terra-wds:/type2/1", "terra-wds:/type2/2"]    } }
through the swagger page and this is how it displays:

Although it's good when I click on the "2 items":

@calypsomatic good catch, and I obviously missed it - should be fixed now.

@calypsomatic good catch, and I obviously missed it - should be fixed now.

Whoops, accidentally messed around a bit before approving and found that if I made an array with one string that matches terra-wds:/type/name and one that doesn't it gets confused:

Also, weirdly, the expanded view shows "entityType" and "entityName" for the relation:

But a "pure" relation array displays differently:

@calypsomatic I'm now doing much deeper inspection of the whole array to look for relations. I hope that when WDS supports arrays-of-relations on the backend, mixed arrays like this will be much less likely … but it's still possible to have a string array, where one of the strings happens to be a terra-wds:/ URI. So, I dig into everything now.


mention? what does mention mean?

mention test dataset text file in the line 57 of test.py, for example
i do not know  this  'mention' means what ?

test.py code needs the images names to be tested. so we should test images names in a text file, and that file name should be assigned to the val_filename variable, for example below we mentioned or assigned 'val_list_SIRR.txt' to the val_filename variable.
val_filename = 'val_list_SIRR.txt'


Enable usage with browserify

Hello,
We use browserify (http://browserify.org/) in our project to build our browser scripts. The current implementation of d3-legend requires the d3 module to be imported globally before importing the legend module. With browserify all modules need to be imported in local scopes similar to Node.js.
This pull requests adds the missing imports to enable building with browserify.
Best regards
Marcel

Is this still required with the d3v4 module syntax?

Yes, the new module system made this pull request obsolete. It's working fine with browserify now.

Great thanks!


Dont assume local storage

This adds a few fixes so the code works with remote cubes.
An example script is here:
using PyramidScheme, Zarr
const PS = PyramidScheme
using GLMakie
using DimensionalData.Dimensions
@dim lon XDim
@dim lat YDim
import DimensionalData as DD
replacenan(i) = i<=0 ? NaN32 : Float32(i)
p2020 = replacenan.(PS.Pyramid("https://s3.bgc-jena.mpg.de:9000/pyramids/ESACCI-BIOMASS-L4-AGB-MERGED-100m-2020-fv4.0.zarr"))
p2017 = replacenan.(PS.Pyramid("https://s3.bgc-jena.mpg.de:9000/pyramids/ESACCI-BIOMASS-L4-AGB-MERGED-100m-2017-fv4.0.zarr"))

pdiff = p2020 .- p2017
plot(pdiff, colormap = :curl)

This works for me locally but has very huge latency problems. I am still going to merge now, because this might also be caused by my bad internet connection at home. I would like to take it for a test in a better internet setting but away from the institute.
We might want to make the chunks even smaller, because at the moment we might end up downloading 4 million pixel values for the plot because we might need 4 chunks. It might be better to have a bit smaller chunks, so that we don't have to download as much data.


chore: update timeout for GitHub workflows

What this PR does / why we need it:
There are 29 PRs from @team-eng-enablement that set the default timeout for our GitHub workflows. This PR aims to do it in one shot.

Special notes for your reviewer:
I am wondering if the default timeout that this PR sets is suitable for all our workflows...

PR Readiness Checklist:
Complete these before marking the PR as ready to review:

[ ] the CHANGELOG.md release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR

It seems that ${{ fromJSON(vars.GHA_DEFAULT_TIMEOUT) }} is 10 minutes. It's not enough for our use case, how should we proceed?

It seems that ${{ fromJSON(vars.GHA_DEFAULT_TIMEOUT) }} is 10 minutes. It's not enough for our use case, how should we proceed?

You can ask eng enablement team on #ask-eng-enablement-guild.


Upgrades coraza docker

Run coraza-spoa as unprivileged user within the container
Device images in a main image without CRS and a coreruleset target to include CRS
Add multiarch images for multiple platforms
Use docker-entrypoint.sh
Use tini

Do you mind installing the pre-commit hook and running the linter?

Can you please rebase?

@jcchavezs rebased and fixed some stuff... can you take a look?


remove offering button should not be shown if the action is not  allowed

ISSUE TYPE

Improvement Request

COMPONENT NAME

CLOUDSTACK VERSION

4.19

CONFIGURATION

OS / ENVIRONMENT

SUMMARY

as described in https://github.com/apache/cloudstack/pull/9391#issuecomment-2228126972  remove backup offering should only be shown if remove backup offering is allowed.  (i.e. not for dummy offering or any other that might disallow it.)
see also

STEPS TO REPRODUCE

EXPECTED RESULTS

ACTUAL RESULTS

@DaanHoogland in the given example in https://github.com/apache/cloudstack/pull/9391#issuecomment-2228126972, the backup offering could be deleted using the 'force' option.
So, I think the remove offering button should still be shown. The error only gives the warning that using the 'force' option will delete all the backups.
Please let me know your thoughts

@DaanHoogland in the given example in #9391 (comment), the backup offering could be deleted using the 'force' option. So, I think the remove offering button should still be shown. The error only gives the warning that using the 'force' option will delete all the backups. Please let me know your thoughts

So you are saying we should not implement this at all, right @abh1sar ? If the functionality is consistant, I am fine with keeping it, but it seemed odd to me at the time (close at will)


[SPARK-7888] Be able to disable intercept in linear regression in ml package

Merged build triggered.

Merged build started.

Test build #35418 has started for   PR 6927 at commit 3bb9ee1.

Test build #35418 has finished for   PR 6927 at commit 3bb9ee1.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #35419 has started for   PR 6927 at commit 319bd3f.

Test build #35419 has finished for   PR 6927 at commit 319bd3f.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #35421 has started for   PR 6927 at commit f34971c.

Test build #35421 has finished for   PR 6927 at commit f34971c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

LGTM except minor issues.

Merged build triggered.

Merged build started.

Test build #35526 has started for   PR 6927 at commit ae5baa8.

Test build #35526 has finished for   PR 6927 at commit ae5baa8.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Although LeastSquaresAggregator and LeastSquaresCostFun are private, MiMa is not happy about the changes.
[error]  * method this(org.apache.spark.mllib.linalg.Vector,Double,Double,Array[Double],Array[Double])Unit in class org.apache.spark.ml.regression.LeastSquaresAggregator does not have a correspondent in new version
[error]    filter with: ProblemFilters.exclude[MissingMethodProblem]("org.apache.spark.ml.regression.LeastSquaresAggregator.this")
[error]  * method this(org.apache.spark.rdd.RDD,Double,Double,Array[Double],Array[Double],Double)Unit in class org.apache.spark.ml.regression.LeastSquaresCostFun does not have a correspondent in new version
[error]    filter with: ProblemFilters.exclude[MissingMethodProblem]("org.apache.spark.ml.regression.LeastSquaresCostFun.this")

Please exclude them. Thanks.

Test build #35530 has started for   PR 6927 at commit 4016fac.

Test build #35530 has finished for   PR 6927 at commit 4016fac.

This patch fails MiMa tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Merged build triggered.

Merged build started.

Test build #35534 has started for   PR 6927 at commit 0ad384c.

Test build #35534 has finished for   PR 6927 at commit 0ad384c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Thanks. Merged into master.


Upgraded to gradle 7.2

Given the upgrade on https://github.com/rsksmart/rskj/pull/1616 we want to also upgrade this repo Gradle version to 7.2.
Updated to Gradle 7 version in order to take advantage of newer tools.
Description

Updated gradle wrapper.
Updated Removed Jcenter().

Motivation and Context

Upgrade Gradle version.

How Has This Been Tested?

I ran  ./gradlew clean assemble --refresh-dependencies
Finally I ran gradle build

Types of changes

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

Checklist:

[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Requires Activation Code (Hard Fork)

rskj:upgrade-gradle-to-v7

pipeline:run

pipeline:run


Regression: cannot extend headers in requestTransform fn

Before https://github.com/angular/angular.js/commit/5da1256fc2812d5b28fb0af0de81256054856369, it used to be possible to do this:
        function requestTransform(data, headers) {
            headers = angular.extend(headers(), {
              'X-MY_HEADER': 'abcd'
            });
          }
          return angular.isObject(data) ? angular.toJson(data) : data;
        }

This is because the headersGetter used to re-use the argument instead of declaring a new one: https://github.com/angular/angular.js/commit/5da1256fc2812d5b28fb0af0de81256054856369#diff-748e0a1e1a7db3458d5f95d59d7e16c9L71
/cc @pkozlowski-opensource

I would argue that this is incorrect usage since the idea behind transformRequest is to transform data to be sent - if I understand its intention correctly. In this sense it is like a filter so it really shouldn't assume that it can have side effects on its arguments....
My vote would be to documenting it as a breaking change.

If someone wants to modify headers it should be done via a header being a function.

I guess it's pretty weird to use it that way, yes.
You could basically change the whole headers object if you wanted to ... you can still to this with an interceptor, so that use case is covered.
An adding headers in the config is obviously the preferred way.

Right, so my proposal is this:

let's write an explicit tests that shows that we are not allowing this
let's update the changelog with a breaking change (I'm on a fence here)

How does it sound @Narretz ?

We've had breaking change notes for very minor things, so we should definitely do it. I'm not sure a test is needed, but it can't hurt.

@Narretz I've sent #11503 to close this one. Mind having a look?


Skip all the createWriteStream() functional tests on OSX.

(for #9953)
A while back we skipped one of the "raw" createWriteStream() functional tests (but only on OSX).  However, other tests in the same suite are having the same problem.  So we are skipping all the tests in the suite for now (to be resolved in #10031).

Codecov Report

Merging #10449 into master will decrease coverage by 0.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #10449      +/-   ##
==========================================
- Coverage   60.95%   60.94%   -0.02%
==========================================
  Files         571      578       +7
  Lines       30809    31190     +381
  Branches     4387     4429      +42
==========================================
+ Hits        18779    19008     +229
- Misses      11077    11216     +139
- Partials      953      966      +13

Impacted Files
Coverage Δ

src/datascience-ui/react-common/arePathsSame.ts
75% <0%> (-12.5%)
:arrow_down:

src/client/common/utils/platform.ts
64.7% <0%> (-11.77%)
:arrow_down:

src/client/linters/pydocstyle.ts
86.66% <0%> (-2.23%)
:arrow_down:

src/client/activation/node/manager.ts
28.3% <0%> (-1.7%)
:arrow_down:

src/client/datascience/debugLocationTracker.ts
76.56% <0%> (-1.57%)
:arrow_down:

...tascience/interactive-ipynb/nativeEditorStorage.ts
49.36% <0%> (-1.29%)
:arrow_down:

src/client/datascience/jupyter/serverSelector.ts
90.76% <0%> (-1.07%)
:arrow_down:

src/client/common/process/proc.ts
14.49% <0%> (-0.73%)
:arrow_down:

src/client/datascience/jupyter/jupyterSession.ts
65.35% <0%> (-0.43%)
:arrow_down:

.../datascience/interactive-common/interactiveBase.ts
5.71% <0%> (-0.01%)
:arrow_down:

... and 29 more

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 63befc6...54af0e7. Read the comment docs.


Added signatures, tests, and docs for append_array function (Issue 481)

Submisison Checklist

[x] Run unit tests: ./runTests.py src/test/unit
[x] Run cpplint: make cpplint
[x] Declare copyright holder and open-source license: see below

Summary
Added append_array function hooks into Stan (https://github.com/stan-dev/math/issues/481)
For the docs I woulda simplified the definitions with a T parameter as is used elsewhere in the manual, but these functions don't support appending arrays of arrays so I wanted to be clear (usually T can be array of arrays in all the other places it comes up)
How to Verify
./runTests.py src/test/unit/lang/parser/matrix_functions_test.cpp
Documentation
Added under "Array Concatenation" in src/docs/stan-reference/functions.tex
Reviewer Suggestions
@seantalts or @bob-carpenter
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company): University of California, Santa Barbara
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

Sure, I'll change it to support all the arrays-of types as well. It should work fine. The only reason I didn't include them was cause there weren't explicit tests in the math library for them. But assuming copy constructors work, it'll be fine :p.

Alright nevermind, I lied. tldr; I think this should go in with the limited types. I updated the docs to make them shorter.
It seems like the signature:
template <typename T1, typename T2>
inline typename std::vector<typename return_type<T1, T2>::type>
append_array(const std::vector<T1>& x, const std::vector<T2>& y)

Should work. However, return_type returns the promoted scalar type.
So if T1 == std::vector<std::vector<double> >, T2 == std::vector<std::vector<var> >, then the return type is std::vector<var> not std::vector<std::vector<var> >.
The promotion needs to be there to allow mixing of data/params.
The crudest way I see to get this to work is to manually add signatures std::vector<std::vector<T1> >, std::vector<std::vector<std::vector<T1> > > etc.
It should also be possible to build a return_type metaprogram that keeps the std::vectors intact so the original signature works.
Very likely there's some alternative I missed, but both of these (and probably any alternative) go back to the Math library. The difficulty in any case is figuring out what the tests should be (to keep the combinatorics under control). The implementation code, either way, is probably pretty simple.
Your call, but I think this is useful as is.

What's needed is the metaprogram to compute return type.  Then the rest is trivial.
I agree that it's worth doing even if it lacks generality.

Let's go ahead and include this as is. It is useful. I'll update the append_array issue with details on the vector return types and put that on my list of things to do.

I guess this can wait now. I've opened a pull req in the math lib (https://github.com/stan-dev/math/pull/575) to address (https://github.com/stan-dev/stan/pull/2343#pullrequestreview-48164940). Everything should still work here, just once that goes through we can support any type instead of just a subset.


arch: arm: API to allow Non-Secure FPU Access

This commit introduces and implements an internal ARM
TrustZone-M API to allow the Non-Secure firmware to use
the Floating Point Unit (FPU).
Signed-off-by: Ioannis Glaropoulos<EMAIL_ADDRESS>

ARM reference: http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0500j/BABGCFFJ.html

Codecov Report

Merging #10790 into master will increase coverage by 0.15%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #10790      +/-   ##
==========================================
+ Coverage   53.08%   53.24%   +0.15%
==========================================
  Files         215      215
  Lines       25820    25820
  Branches     5692     5692
==========================================
+ Hits        13707    13748      +41
+ Misses       9803     9756      -47
- Partials     2310     2316       +6

Impacted Files
Coverage Δ

lib/posix/pthread_sched.c
41.66% <0%> (-20.84%)
:arrow_down:

lib/posix/pthread_mutex.c
77.77% <0%> (+1.38%)
:arrow_up:

lib/posix/pthread.c
80.36% <0%> (+12.32%)
:arrow_up:

lib/posix/pthread_cond.c
83.33% <0%> (+20.83%)
:arrow_up:

include/posix/posix_sched.h
100% <0%> (+100%)
:arrow_up:

lib/posix/pthread_barrier.c
100% <0%> (+100%)
:arrow_up:

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 da699e4...1c05807. Read the comment docs.

@pizi-nordic , please, take a quick look

Are FPU regisers cleared on transition from Secure Zone to Non-Secure Zone?
If not, please add code/issue in order to not miss that in the design.

Good point. Yes, this is the responsibility of the compiler. It is done when we call a Non-Secure pointer (i.e. with attribute _cmse_nonsecure_call). So, I do not think we need to open an issue for that.


feat: add gh

@mason-org/triage notify(Reason::NewPullRequest)
This comment ensures a notification is delivered to maintainers.
 🤖 This is an automated comment.    📖 Source code


Pick stylesheets

Is it an idea to further expand the datatype? For clients we often use a dropdown to give the content editor the option to choose a stylesheet (a theme). The way you do this is of course much more beautiful. Of course I can add the path to the stylesheet as the name of the theme, but it would be nice if I could add a stylesheet (path to) in addition to an image and a name.

HI @erikjanwestendorp and thanks you for the great suggestion.
I've been having a little think about it and I wonder if maybe there could be a toggle for the data type that would turn on the stylesheet functionality. When checked, the additional file picker field would appear and the return value would be the relative path of the selected file rather than the label. From a content editors perspective there would be no changes.
That's probably going to be the "simplest" way to do with without introducing a breaking change. When I have some time i'll have a play, alternatively feel free to experiment yourself and submit a PR if you want.
Thanks


Build --extract-css does not do anything

Please provide us with the following information:

OS?

Windows 7, 8 or 10. Linux (which distribution). Mac OSX (Yosemite? El Capitan?)

Mac OSX Siera
Versions.

Please run ng --version. If there's nothing outputted, please run in a Terminal: node --version and paste the result here:

@angular/cli: 1.0.0-rc.1
Repro steps.

Was this an app that wasn't created using the CLI? What change did you do on your code? etc.

Created a new cli project , added some css to one of my components, expected the --extract-css to extract to css into one file as per the documentation says, but the css is still is inside the js file when looking at the dist folder.
The log given by the failure.

Normally this include a stack trace and some more information.

Mention any other details that might be useful.

Thanks! We'll be in touch soon.

The extraction option applies to global styles.  Global styles are the stylesheets referenced in the styles field within the project's angular-cli config file.

@clydin, alright , didn't know that.
I'd be better to add that to the documentation.
I would've thought that would extract the inline css, that would be cooler :)
The global styles are already extracted, no point in putting it and then extracting it for me.

Closing as answered by @clydin, thanks!