[FEATURES] Add events  and conditions when alluxio runtime is scaling out and in

What feature you'd like to add:
It's required the conditions and events to indicate when the runtime is scaled out  and in
Events:
  Message:                        The workers scaled in.
    Reason:                         Workers scaled in
    Status:                         True
    Type:                           WorkersScaledIn
    Last Probe Time:                2021-04-11T07:45:03Z
    Last Transition Time:           2021-04-11T06:03:52Z
    Message:                        The fuses scaled in.
    Reason:                         Fuses scaled in
    Status:                         True
    Type:                           FusesScaledIn
  Type    Reason   Age                  From                         Message
  ----    ------   ----                 ----                         -------
  Normal  Succeed  18m (x9 over 33m)    AlluxioRuntimeController  Alluxio runtime scaled in. current replicas:3, desired replicas:0.
  Normal  Succeed  6s (x18 over 34m)    AlluxioRuntimeController  Alluxio runtime scaled out. current replicas:0, desired replicas:3.

Why is this feature needed:

See https://github.com/fluid-cloudnative/fluid/pull/730#pullrequestreview-639462483


add several lines

Support color bg.
Support color char.
Support random image length.
Support select chars.
Support cache corpus.
Forgive me modified some params for self test.

maybe some difficult to merge ,we change it on the same time...

review.
libs/font_utils.py has some line confict,other is only some params differ.


Segmentation fault

<EMAIL_ADDRESS>commented:

Which version of PhantomJS are you using? Tip:
1.7
What steps will reproduce the problem?

just typing "./phantomjs"

2.
3.

What is the expected output? What do you see instead?

I expect phantomjs not to crash.
Which operating system are you using?

ubuntu 10.04 x64
Did you use binary PhantomJS or did you compile it from source?

tried both.
Please provide any additional information below.
what happens:
:~/phantomjs-1.7.0-linux-x86_64/bin# ./phantomjs
PhantomJS has crashed. Please read the crash reporting guide at https://code.goo
gle.com/p/phantomjs/wiki/CrashReporting and file a bug report at https://code.go
ogle.com/p/phantomjs/issues/entry with the crash dump file attached: /tmp/6dc0a3
05-25d0-0a0c-565d487d-295cb741.dmp
Segmentation fault

Disclaimer:
This issue was migrated on 2013-03-15 from the project's former issue tracker on Google Code, Issue #860.
:star2:   3 people had starred this issue at the time of migration.

Please test again with the latest version 2.1.


first implementation of scipy fftconvolve

I have prepared an implementation of the scipy fftconvolve function.
There are limitations wrt the scipy function on the mode used (only same is implemented) and axes argument is fixed to None.
I have not written proper test suite as I am not a specialist of this. However, I have a nb on Collab with some checks against scipy fftconvolve. see HERE.
As mentioned in discussion #15204, the scipy fft  next_fast_len would require more work to be adapted to all devices (CPU, GPU, TPU), in my implementation I only consider power of 2 like FFT extension of the original shapes.

I have signed the CLA yesterday but what I should expect?

If you are looking to rewrite the commit under your new author email, try git commit --amend --reset-author? You will then need to force-push the rewritten commit to the PR branch.

Hi, does I have something to validate/check?

Looks like the CLA check is fine now.
I think this implementation looks pretty good, but before a more detailed review it would be helpful to add tests. You could model them after some of the existing convolution tests here: https://github.com/google/jax/blob/67a28ce30fb5ed6b187d0e9d5f664959659c432d/tests/scipy_signal_test.py#L83

@jakevdp Thanks. I'm not a practitioner of "python test" but it is an occasion to learn :) I have some private tests that I have used in the Colab nb. I guess I have to refactor them. Can I use normal scipy.fftconvolve to get the truth and make the comparison?

Can I use normal scipy.fftconvolve to get the truth and make the comparison?

Yes, that would be my recommendation.

Hi, I have tried to make a small testFFTConvolution in scipy_signal_test.py with little adaptation of testConvolutions2D .
I've tryied
pytest -n auto tests/scipy_signal_test.py -k testFFTConvolution

but at a certain point the job crash due to the impossibility to make sub_thread. I run on a computer centre so it may be forbidden...

Hi - it looked like something went awry when you attempted to sync against the main branch. If you tell me what you did I can try to help set it straight

If you want me to help, you could start by telling me the output of this command:
git remote -v

ho ! sorry I'm not git very confortable
git remote -v
origin	git@github.com:jecampagne/jax.git (fetch)
origin	git@github.com:jecampagne/jax.git (push)
upstream	http://www.github.com/google/jax (fetch)
upstream	http://www.github.com/google/jax (push)

done

It looks like the tests are failing with an undefined variable – I'd suggest trying to run them locally and iterate until they pass. You can use standard pytest invocations for this. For example, to run only your new test, you could use the following command:
pytest tests/scipy_signal_test.py -k testFFTConvolution

pytest tests/scipy_signal_test.py -k testFFTConvolution
============================================== test session starts ===============================================
platform linux -- Python 3.8.16, pytest-7.2.2, pluggy-1.0.0
rootdir: /sps/lsst/users/campagne/jax, configfile: pytest.ini
plugins: xdist-3.2.1
collected 100 items / 90 deselected / 10 selected
tests/scipy_signal_test.py ..........                                                                      [100%]
======================================= 10 passed, 90 deselected in 3.63s ===============================

It seems that there is a "writing" error. I'm using Visual Studio. Do you know a wait to get the Lint running on the code to validate it when I write?

You can run the lint checks locally using pre-commit, described here: https://jax.readthedocs.io/en/latest/contributing.html#contributing-code-using-pull-requests
I believe there is a vscode extension for pre-commit, but I haven't used it myself.

does this will run on my particular code ???? I do not want to make a mess elsewhere...
pre-commit run --all

pre-commit run will run all lint checks against staged files (i.e. files that you have done git add on, but not yet git commit)
pre-commit run --all-files will run lint checks against the whole package, and is effectively what the lint_and_typecheck CI does.

Ok so I run  pre-commit run --all-files ....

It looks like there are some test failures when we run a larger number of test cases. You can probably reproduce them locally with this:
JAX_NUM_GENERATED_CASES=50 pytest tests/scipy_signal_test.py -k testFFTConvolution

Hello @jakevdp ,
I have run the tests and capture the outputs, but I must say that it is the first time that I see such reporting and do not know exactly how to reproduce the inputs that make the code failure.
If I try
key = jax.random.PRNGKey(2)
key, k1,k2 = jax.random.split(key,3)
s1=(10,)
s2=(1,)
x1 = jax.random.randint(k1, shape=s1, minval=0, maxval=10, dtype=np.int32)
x2 = jax.random.normal(k2, shape=s2, dtype=np.complex64)
sp_res = sp_fftconvolve(x1,x2, mode="same")
jax_res = fftconvolve(x1,x2)
print("sp_res= ",sp_res)
print("jax_res=",jax_res)
print("diff=", sp_res-jax_res)

then the difference is on CPU
diff= [ 8.94069672e-08-1.49011612e-08j  0.00000000e+00+0.00000000e+00j
  2.98023224e-08+0.00000000e+00j  5.96046448e-08+0.00000000e+00j
  0.00000000e+00+0.00000000e+00j -2.98023224e-08-1.49011612e-08j
  0.00000000e+00+0.00000000e+00j  5.96046448e-08+0.00000000e+00j
  5.96046448e-08+0.00000000e+00j  0.00000000e+00+0.00000000e+00j]

Can you give me an hint?

I think I have found the pb. I pass all the tests.  I run pre-commit run --all-files...

I succeed to make the axes =/= None working!
I realize that using scipy.fft  _init_freq_conv_axes is dealing with statics so I guess it is ok
in1, in2, axes = osp_fft_init_freq_conv_axes(in1, in2, mode, axes,
                                            sorted_axes=False)

The mypy errors are coming from the fact that if you write code like this:
def f(x: ArrayLike):
  x = jnp.asarray(x)
  x.shape  # fails in mypy

then x is still considered ArrayLike rather than Array by mypy, and so you can't use Array methods. To address this, you need to create a new variable name when you cast from ArrayLike to Array
def f(x: ArrayLike):
  x_arr = jnp.asarray(x)
  x_arr.shape  # passes in mypy

Yes, this is terrible, because static type checking in Python is a terrible post-hoc patch-work, but JAX users seem to like it.

Hey, I wanted to bring https://github.com/google/jax/pull/15411 to your attention. It's an independent PR implementing fftconvolve (the author hadn't seen this in-progress PR). Overall it's pretty similar to the approach you've landed on here, but it also implements different mode and axes options.
How would you like to proceed? You've put a lot of effort here and written some really nice code and I'd love to get it merged, and recognize you an official JAX code contributor. In the end, though, we will eventually want the full fftconvolve API that's implemented in #15411. Any thoughts on the best way to get there?

@jakevdp Thanks for your kind message.
Currently my code is extending the axes =/= None and BTW

I do not know if my management of testing "axes" at the beginning of the code is a correct JAX. I have not use some JAX apiutils method with "_"...
I do not know how to set up a test on this.
To extend to mode = valid/full  I guess is just a matter  of some more work to understand the scipy code. Of course I can have a look right now. It is a matter to converge to a code to fit in your plan of JAX branch merge... Let me know.

Hi! I finaly find a way to include mode=valid too. And I include the 3 modes tests
I do not yet know how to include a test on "axes" argument.

Hi - just to be clear, it's fine to use private jax imports. We have control over those, and so if they change we can update our code. My concern was that you were using private scipy imports: we have no control over those, and it means a new scipy release could break our code unexpectedly.

Hi @jakevdp May be the check of axes to be an sequence of int can be added with some internal JAX fnt?

I proceed...

Oops :
git rebase upstream/main
First, rewinding head to replay your work on top of it...
Applying: first implementation of scipy fftconvolve
Applying: add a fftconvolve test
Applying: new shapes testing
Applying: first implementation of scipy fftconvolve
Using index info to reconstruct a base tree...
M	jax/_src/scipy/signal.py
Falling back to patching base and 3-way merge...
No changes -- Patch already applied.
Applying: add a fftconvolve test
Using index info to reconstruct a base tree...
M	tests/scipy_signal_test.py
<stdin>:16: trailing whitespace.
      ((1,1), (1,1)),
warning: 1 line adds whitespace errors.
Falling back to patching base and 3-way merge...
Auto-merging tests/scipy_signal_test.py
CONFLICT (content): Merge conflict in tests/scipy_signal_test.py
Failed to merge in the changes.
Patch failed at 0005 add a fftconvolve test
The copy of the patch that failed is found in:
   /sps/lsst/users/campagne/jax/.git/rebase-apply/patch

When you have resolved this problem, run "git rebase --continue".
If you prefer to skip this patch, run "git rebase --skip" instead.
To check out the original branch and stop rebasing, run "git rebase --abort".

What should I do? I really not a git-geek

But the file has been completly reloaded to its very old version ?!

End it is teh same with my signal.py it is at a very old vesion...

That’s because there is a merge conflict in one of your earlier commits that needs to be resolved in the rebase, so it’s showing you a view of that earlier commit.

So if I resolve and git rebase --continue will at the end arrive to my last version????

when I do git add <file>after resolve, what I should do as "git rebase --continue" complains but do not see any more conflicts.
(jax-fork) cca003:~/my_sps/jax[(no branch, rebasing fftconvolve2dr)]$ git status
# HEAD detached from dfe95dc
# You are currently rebasing branch 'fftconvolve2dr' on 'dfe95dc'.
#   (all conflicts fixed: run "git rebase --continue")
#
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	jax/_src/__pycache__/
nothing added to commit but untracked files present (use "git add" to track)

Im not sure how sich a command would function in the presence of conflicts - the issue is that some of the code you changes has conflicting changes in the main branch, and this conflict resolution process lets you specify what to do with it. If gut just took your changes, it would wipe out the other changes that happened in the meantime. Does that make sense?

I’ve never seen the error you pasted above in ten years of using git, so I’m unsure how to fix it. You can run git rebase --abort if you want to start over

I do git rebase --abort
and so now I should do what in fact?

I’m not sure - I just pulled down your branch and tried locally, and the sequence of commands I mentioned above did the right thing. The only possible difference is what you did when resolving the conflict in the rebase. Can you tell me what you did there?

I would do “accept current change”, then “git add” the file, then “git rebase --continue”

here is the history
1040  git fetch upstream
 1041  git rebase upstream/main
 1042  ddt -h tests/
 1043  git branch
 1044  git rebase --continue
 1045  git status
 1046  git add tests/scipy_signal_test.py
 1047  git rebase --continue
 1048  git status
 1049  rm test_6_04_23_1*
 1050  git status
 1051  git rebase --continue
 1052  ls jax/_src/__pycache__/
 1053  git status
 1054  git rebase --abort

When I saw the conflit message and ask you what to do, the Visual Studio Code was updated the 2 files (signal.py & scipy_signa_test.py) showinf the conflict in  scipy_signa_test.py. Then I delete some lines to get a scipy_signa_test.py file and save it. Then I use git add, but then the git rebase --continue told me that something is missing...
I probably did something wrong somewhere but as I do use these "git" cmds  I do not really understand what is going on....
currently I am at this stage
(jax-fork) cca003:~/my_sps/jax[fftconvolve2dr]$ git status
# On branch fftconvolve2dr
# Untracked files:
#   (use "git add <file>..." to include in what will be committed)
#
#	jax/_src/__pycache__/
nothing added to commit but untracked files present (use "git add" to track)
(jax-fork) cca003:~/my_sps/jax[fftconvolve2dr]$ git branch
* fftconvolve2dr
  main

And I will leave it asis. And come back tomorrow morning... I am sorry.

Thanks - the only wildcard here is in the conflict resolution. When you say "Then I delete some lines", what did you do? With the conflict message you saw above, did you click "Accept Current Change"? Or did you delete the lines entirely?

Hi @jakevdp , well when I saw

I have removed either the green or the blue line (honesty I do not remember) and I have saved the file.  What should have done?
I will wait till for your advise.

That seems like the right thing to do. I'm honestly unsure of where it could have gone wrong from there.
Are you interested in continuing this exercise? If not I could do the required changes and force-push to your branch - what do you think?

Ho I can try to perform again. An I will then use "Accept Current Change", yes?

 Don't worry about the readthedocs build; that's an unrelated issue that I'm fixing in #15461

hi @jakevdp, do I have succeeded to make the one-commit?

And it's in! Thanks for the work on this!


Allow for multiple service accounts to have ImagePullSecrets applied

Description
Allow for ImagePullSecrets to be applied to other Service Accounts than the default.
Which issue # does this fix? And was it approved before you worked on it?
No Issue, however a feature I felt worth while.
Fixes: #7
How Has This Been Tested?
Multiple times on my own cluster.
Scenarios Tried:

New NS = Default Changed
New SA w/o NS Ignore Annotation = No Change
New SA w/ NS Ignore Annotation = No Change
New SA w/o NS ignore Annotation and SA annotation added (Invalid) = No Change
New SA w/o NS ignore Annotation and SA annotation added (valid) = PullSecret added

How are existing users impacted? What migration steps/scripts do we need?
No change, the default logic of the default SA is still valid.
Only when users add the alexellis.io/registry-creds.include annotation to their ServiceAccounts will the ImagePullSecret be added.
Checklist:
I have:

[X] updated the documentation and/or roadmap (if required)
[X] read the CONTRIBUTION guide
[X] signed-off my commits with git commit -s
[ ] added unit tests (No Present within current repo)

Hi David,
Thank you for your interest in the project. The contribution process is something that everyone needs to follow. I can see you've filled out part of the PR template, so that's something. The testing is also appreciated.

Which issue # does this fix? And was it approved before you worked on it?

When you just put "no, but I wanted to" it doesn't create a good first impression, but I want to give you benefit of the doubt.
So please can you raise an issue and start a discussion about why this is needed.
Alex

Hi Alex,
Apologies I hit submit too early 🤦 on that section, I should have expanded on this a little further.
The use case for this, was that I have multiple namespaces and deployments all using their own ServiceAccounts, while the original controller works with a many pull policies to one service account, my contribution allows for a Many:Many relationship of ImagePullPolicies to many ServiceAccounts.
A better example would be that a helmchart in which requires no ability to customise the ServiceAccount in which is used (enforced new SA) - I'm unable to pull images from a private repository.
With the patch/contribution applied, I'm able to patch said SA with the annotation alexellis.io/registry-creds.include=CLUSTERPULLSECRETNAME and now able to pull from said private repository.

@davidcollom how similar is your change to the following in #4?
https://github.com/alexellis/registry-creds/pull/4/files#diff-cace653417c1c5f437a99e61b744b78680b56528d614d2ef3092494ee8abf49cR78-R91

I'm uncomfortable with the additional number of lines added to secret_reconciler.go, it makes it very difficult to review and follow what is going on. Can you consider breaking some of that out into utility methods, and to remove nested expressions wherever you can? i.e. if you have an if/else and can return from the first condition, then do so and let the else be unindented as an expression.

Sure, I can take a look this weekend or later this week.
With regards to #4, these changes are very similar, #4 does have the addition of:

Upon ClusterPullSecret removal, the secret is removed from all namespaces and serviceaccounts

Which is not included within my changes.

Let's start over with a new PR that makes fewer, smaller changes.

Sorry for the lack of updates, I've been working on a new PR to fix this issue. I hope to get something ready for review this week, early next.

We should have this covered now by the work @developer-guy has been doing. We still need something to clean up image pull secret lists after secrets have been removed.


Updating documentation in example notebooks

Updating all documentation in example notebooks that require data.
With #55 , this is to close #51

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

Project coverage is 66.66%. Comparing base (05a08ce) to head (0a0e34d).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #56   +/-   ##
=======================================
  Coverage   66.66%   66.66%
=======================================
  Files           8        8
  Lines         717      717
=======================================
  Hits          478      478
  Misses        239      239

Flag
Coverage Δ

unit-tests
66.66% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@erikvansebille are there any other changes for the PR, or happy to merge?

All good; happy for you to merge!


[SPARK-25653][TEST] Add tag ExtendedHiveTest for HiveSparkSubmitSuite

What changes were proposed in this pull request?
The total run time of HiveSparkSubmitSuite is about 10 minutes.
While the related code is stable, add tag ExtendedHiveTest for it.
How was this patch tested?
Unit test.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/3717/
Test PASSed.

Merged build finished. Test PASSed.

Test build #96998 has started for PR 22642 at commit a85a843.

cc @gatorsmile for final sign-off since this is a test coverage.

@dilipbiswal . It's not skipped in the regular run. As you know, those test will be skipped when we give that explicitly. For example, -Dtest.exclude.tags=org.apache.spark.tags.ExtendedHiveTest.

@dongjoon-hyun Ah.. got it.. thanks a lot.

BTW, @gengliangwang . Please create a different JIRA issue for this. This doesn't resolve SPARK-25613 and SPARK-25614. If we close them with this, we will not improve those test cases eventually.
cc @gatorsmile

Test build #96998 has finished for PR 22642 at commit a85a843.

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

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/96998/
Test PASSed.

@dongjoon-hyun  thanks, I have created new Jira ticket: https://issues.apache.org/jira/browse/SPARK-25653

Thank you, @gengliangwang !

LGTM
Thanks! Merged to master.


debian build now builds also libbaresip and libbaresip-dev packages

In this branch debian build creates also libbaresip and libbaresip-dev packages.  The former includes dynamic library libbaresip.so.  The latter depends on the former and itself includes baresip.h include file as well as static library libbaresip.a.
Is something missing or wrong?

thanks. I have tested this patch by creating Debian packages (on Debian Testing).
my only comment is that we should perhaps sync with the Debian guys, who I believe
are maintaining their own set of scripts.

Alfred E. Heggestad writes:

thanks. I have tested this patch by creating Debian packages (on
Debian Testing).

I tested it on Debian stable (Stretch).

my only comment is that we should perhaps sync with the Debian guys,
who I believe are maintaining their own set of scripts.

Fine if they come up with better solution.
-- Juha


Some TEX containers do not pack properly

I have been using the tool for the past few days and I found out that some of the TEX containers can indeed be decompressed but they are unusable once recompressed, as an example M_WORLD.TEX will crash the tool when trying to decompress it AFTER having compressed it with the same tool, even with no changes made.
EDIT: It seems to happen if the filename has an underscore (_) in it, renaming the file before unpacking seems to work fine.

Fixed my issue renaming the files before and after using the tool.

Fixed it in newest version. It would not crash on my pc but the packed M_WORLD.TEX and other files with underscore would be corrupt.


Show User Profile card on screens that have the ability to fit it

It would be nice if the scheduled rooms and profile card showed up on 13.5" screens as well
 (regular zoom on 13.5" screen)
 (90% zoom on 13.5" screen)

#2167 mentions this as well I think


Binding a number input restricts what you can type in it

Setting bind:value or bind:valueAsNumber for an input of type number restricts what you can type in it. As far as I can tell:

Typing digits works as expected
Typing . does nothing in Firefox, and moves the cursor to the beginning of the field in Chromium
Typing anything else clears the input in Firefox, and does nothing in Chromium

To Reproduce
A maintainer has provided an executable that reproduces the problem. Maybe they could add the source code to this issue report.
Expected behavior
Setting bind:value or bind:valueAsNumber does not affect how a number input responds to typing.
Environment

Sycamore: 0.9.0-beta.3
Browser: Firefox 132.0 (64-bit) and Ungoogled Chromium 129.0.6668.100
OS: Ubuntu 22.04

Note: https://examples.sycamore.dev/number-binding/ is just the automatically hosted version of the examples located at https://github.com/sycamore-rs/sycamore/tree/main/examples/number-binding
The problem is that something like 123. gets parsed as the number 123, which, when formatted, is just 123. Since bind:valueAsNumber is a "controlled" input, typing the . will automatically get removed by the signal updating. This results in the bug where we can never type 123.456 since we'll never get pass the .

Turns out React had the same issue which they fixed. Could be a useful reference: https://github.com/facebook/react/issues/6556

Note: https://examples.sycamore.dev/number-binding/ is just the automatically hosted version of the examples located at https://github.com/sycamore-rs/sycamore/tree/main/examples/number-binding

I've added the source code link to the issue!


安卓样式切换报数字格式的异常

当样式发生改变时，一下属性会抛数字格式异常，borderRaduis、left、top、left、right、bottom、flex
我们在做很多 active 状态的时候都会使用  :class[true ? 'active' : '' ]，当 active 中含有上面这些属性时就会抛数字格式异常
setTimeout 不传时间时安卓也会抛异常

This PR/issue doesn't received response since Weex migrated to Apache two years ago and this repository is no longer active yet.
Feel free to ask question in new repository and thanks for your contribution.

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.


UI lags on iPhone 14 Pro

🐛 Bug Report
I like your UI kit and want to try work with it, but currently unfortunately I faced problem that it laggy even on modern powerful device (not any kind of dinosaurus even a little bit) and it scares. Any thoughts about can it be fixed? Do you or anybody facing this problem too?
To Reproduce
Steps to reproduce the behavior:

Install app from AppStore
Launch it and navigate to different screens and make different gestures with screens and elements
Pay attention on smoothness, especially when swiping to back screen from left side of screen or scrolling
Write here feedback of your test

Expected behavior
Smooth gestures transitions without any lag expected
UI Kitten and Eva version
Idk about version, but I downloaded the app from AppStore 2-3 days ago since that message.

Recorded videos:
https://mega.nz/folder/oqICRAIC#PNoVnhtj5_a0fqIaAnB00g
When I swipe from left side to right (to reach back screen), it's laggy. Scrolling is fine and smooth, only swipe "< Back" is laggy

Not sure I got the issue from the attached videos. Does this laggy behavior affect some of the apps you're working on?

I don't developed anything due to this problem, lag when you swiping to back screen. It's performing not smooth


Esp32 micro ros transport wifi

Issue template
I am trying to connect my esp32 over wifi with the micro ros agent. It runs in a docker container. My machine is a Ubuntu 22.04.

Hardware description: esp32-wroom-32 (Az Delivery)
RTOS: no Rtos
Installation type: platform io
Version or commit hash: humble

Steps to reproduce the issue
My code is working with serial transport, i tried also with the example code form adruino and platform io adapted for wifi, nothing woked.
But here my code for the wifi:
IPAddress agent_ip(192, 168, 1, 100);
size_t agent_port = 8888;

char ssid[] = "ssid";
char psk[] = "pswd";
set_microros_wifi_transports(ssid, psk, agent_ip, agent_port);

My platform.ini:
[env:esp32doit-devkit-v1]
platform = espressif32
board = esp32dev
framework = arduino
monitor_speed = 115200
board_microros_transport = wifi
monitor_filters =
   direct
   esp32_exception_decoder
lib_deps =
<EMAIL_ADDRESS>   https://github.com/micro-ROS/micro_ros_platformio

Micro ros agent in docker (it runs):
docker run -it --rm -v /dev:/dev -v /dev/shm:/dev/shm --privileged --net=host microros/micro-ros-agent:humble udp4 --port 8888 -v6
Expected behavior
working (connecting to agent) :)
Actual behavior
No output on docker. I tried with serial print the program runs and I cloud print all the wifi credentials
Additional information
Esp is in wifi range and i tried some time before with esp idf and it worked also.
Thanks for help and super cool project thanks for making it possible!

Share code for replicating this issue.
Which transport are you using?
Does the board connect to wifi with your setup without micro-ROS?

Does your network works without micro-ROS?
Could you link here the transport implementation you are using?

I am sorry I don't now what you mean with your second point.

In general, I just need instructions for replicating your issue. Share here your project so we can build and reproduce your problem.

Hi,
sorry for replying so late. I switched my location and  also the wifi. I used the same code like before but now it works. Probably it was something with the wifi. The only difference I know of is that I now saved it in the default location of platfrom io and not in a costume one like I did before. In about a week I am back in the other location. I`ll see if I can set it up then properly.
But thank you very much!


⚠ Processors has degraded performance

In 1b5a9d0, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 47 ms

Resolved: Processors performance has improved in e703f2d.


FancyZones does not keep layout after reboot

Microsoft PowerToys version
0.63.0
Installation method
WinGet
Running as admin
None
Area(s) with issue?
FancyZones
Steps to reproduce
Create a new layout and select it.

Then, reboot.
✔ Expected Behavior
Expected the layout to be the user-created layout set before rebooting.

❌ Actual Behavior
The layout in use is now set back to the built-in Priority Grid.

Other Software
No response

Hi @cutecycle, sometimes Windows resets the screens identifiers and we're unable to reapply the layouts, since the screens are treated as new screens.
On 0.64.0, we've released a way to set default layouts for horizontal/vertical monitors. You can assign default layouts in the editor. Does this setting help in making this behavior better?
/needinfo


Rate limit endpoint enum

All Endpoints decorated with

Description
Rate Limits (per App/User, reset Time)
Counts against the Tweet Cap
max operations limits
And also Endpoint relevant information
Endpoint Type
Endpoint Url
Access Level

This information will help to get relations between these properties.
All information are carried together from:
Twitter API v2
Developer Portal - Products
Rate limits

I also optimized the Namespaces. Now i it suits better. I cant name the Endpoint-"Folder" "Endpoint" because it collides with the enum Name. So ApiEndpoint was my solution to that.


Switch from RPC via zig to direct websockets between browser and bun

Sometimes you want to send binary data between bun and zig. Eg: reading a file from the system.
How it currently works
The current RPC mechanism between bun and browser is something like:

request payload is json encoded
rpc request wrapper is json encoded
json request sent via objc postMessage handler to zig
zig passes encoded string to bun via named pipe
bun json decodes request, calls the corresponding handler and gets a result
bun then double encodes the response payload and wrapper
bun sends it back to zig over a named pipe
zig injects the response into the browser where a handler in the browser context double decodes the wrapper and payload
and returns the response as a resolved promise

If you want to send binary via json you have to base64 encode it which is expensive. In addition to all the json serialization this is not great even though bun and zig are pretty fast.
Benefits of websockets
It'd be nice if each Browser context (where you want to enable rpc with bun) established websocket connection with bun where it could send request/responses

avoid named pipes and all the chunking logic and overflow issues
websockets are bidirectional compared to named pipes which require a separate pipe for each direction
websockets natively support binary frames so you can send both text and binary content back and forth without base64 encoding

can convert ArrayBuffers to Blob and send binary directly

probably able to bypass zig and send messages directly between bun and browser

Notes:

Each electrobun app would use a single localhost port for the Bun side of the websocket. multiple browser contexts within the app would connect to that websocket port
ports to avoid:

Reserved System Ports (1–1023)
Common Development Ports (3000, 3001, 5000, 5001, 8080, 8081)
Common Application Ports (3306 Mysql, 5432 Postgresql, 6379 redis, 27017 mongodb)

target port range (49152–65535).
Security:

use Bun's tls.
regenerate certificates whenever the bun process starts
share token with browser contexts for auth
a browser context with given token should not be possible to trigger rpc for a different browser

Some early tests of a prototype using sockets when sending a 2MB file from bun to the browser

via named pipes / evaluateJavascript = 5 seconds
direct from bun to browser via sockets  = 400ms

Additionally because the thread/pipe gets blocked with all the extra encoding/decoding all the other requests have to wait for the 5 second delay as well.
The main problem is that sockets work:

when loading bundled/local content via the views:// schema
or for remote content when you control the server and can configure CORS headers

For building browser "extension" like functionality in electrobun via a preload script that works on any arbitrary remote domain that has CORS restrictions it will have to fall back to the old postMessage -> named pipe -> evaluateJavascript rpc.
CORS is not just a bottleneck here, you probably don't want a random domain you don't control to be able to make network requests to anything on localhost. So security-wise this is a good posture, but maintenance-wise it means we still have to maintain both socket and postMessage based RPC.
The trick will be coming up with an API and mechanism for when to use which


php timeout during package install requiring Doctrine entity updates

PHP times out during package installation with Doctrine because Doctrine update is 10x slower than it was prior to upgrade of php to v7.4 and mariadb to v10.4. May be related to this bug: https://github.com/concrete5/concrete5/issues/8216#issuecomment-574394670 or maybe not. But I can't install many packages which require Doctrine entity updates.
This happens on c5 v8.3.2, v8.4.2, v8.5.2, v8.5.4. This did not happen with php 7.2 and mariadb v10.2.

This sounds like a server configuration issue.

No, it's not a server configuration issue. It's a known MySql/MariaDb bug which concrete5 can't handle:
https://github.com/doctrine/dbal/issues/4015
https://github.com/concrete5/concrete5/issues/8216

Updating or regressing MySQL or MariaDB is only a workable solution for sites that have that degree of control over their environment.
Pre-packaged web host accounts do not provide such control. Providers of such accounts don't update their environments that often, if at all. Such a host afflicted by this bug is likely to remain so for 6-12 months, possibly 'forever', and the only way to dodge the issue for a live site may be to move hosts.
While it is someone else's bug, that doesn't make it not concrete5's problem or Doctrine's problem.

Yeah but I’ve seen no evidence that this is being called a doctrine bug simply because doctrine is the database layer used to query this information. Are you saying that we now need to rewrite every single place we list table foreign keys because of MySQL inefficiency?

Its only a MySQL bug.
But its also Doctrine's problem and concrete5's problem. I don't know the solution.
On general principles, if something is buggy, I look for ways to avoid using it unless I really have to. Damage limitation.
For concrete5, how much analysis has been made of the benefits of each declaration of foreign keys? Which foreign keys in c5 data provide a genuine performance benefit and which are there purely because of developer habit when declaring relationships? (and depending on the write/read ratio, in rare circumstances foreign keys may actually slow things down, irrespective of the MySQL bug)
Even when foreign keys do provide benefits, is that always in a situation where performance is critical?
I am not suggesting avoiding foreign keys completely. Just being self-critical when declaring foreign keys, especially for Doctrine entities, and applying the KISS principle. Use them only where they provide a measurable advantage. Remove them where they don't. Hence encounter the MySQL bug less often.
Back to the top. I don't think this is a solution. But maye one component of a damage limitation strategy.


Object directory for all build artifacts

Currently, our various build script produce binaries all over the tree.

Hardware build artifacts are in build/.
Software build artifacts are in sw/build (for Make) and some other directories for meson.

This setup is problematic for a variety of reasons.

It makes it hard to separate build and test pipelines into stages, and have artifact transfer between the stages.
It makes it hard to rely on artifacts from another build step.
For example, the FPGA build includes the bootrom, so it needs to reference the boot_rom.vmem file in a reasonably stable way.
In-tree builds (which is "build artifacts intermixed with source code", as we do today) make it hard to implement a "make distclean", i.e. "remove all build artifacts and start over".

Can we

Keep this in mind when developing the meson (or any other) build system improvements?
Create a single top-level directory for all build artifacts? (a typical name would be $REPO_TOP/objdir), and roughly document its structure?

I'd go for something like this, mirroring the structure in the source tree.
$REPO_TOP/objdir
|- sw/device/fpga (or other target name)
|- sw/device/sim (or other target name)
|- sw/host/...
|- hw/top_earlgrey_nexysvideo/...

Note that the object directory is not equal to a distribution directory; the object directory contains intermediate build outputs (like *.o files), which would not be present in a distribution directory. (A distribution directory, as created by a hypothetical "make dist" step, would take binary artifacts out of the objdir and create a binary distribution archive from it. Let's keep this issue separate for now.)
@mcy @gkelly

I did prepare a proposal draft at https://docs.google.com/document/d/153s9kH4SyQif88K1k-6GzLCmTj1RCa4V_eWbY-hdrD4/edit# This is mostly how I'd envision things to be; we will need to tweak the proposal to find a common denominator with how meson likes things to be organized. (But meson is not set in stone either, we can improve it as necessary to work for our use case.) @mcy can you have a look?
Please feel free to comment and modify the document if you have ideas. Possibly we can add this to the agenda of the software meeting tomorrow @gkelly?

I think that doc does a good job of expressing a lot of issues I currently see with how we build stuff, thanks for writing it up. I've left some individual comments one stuff that I think could cause problems going forward, but otherwise looks like a reasonable design (and somewhat approximates what I did in #917, up to change of directory names).

@mcy Now that you've implemented a modified form of the directory structure proposed in the Google Doc, would you mind documenting it as part of https://github.com/lowRISC/opentitan/blob/master/doc/ug/directory_structure.md?

@imphil Well, first I want to add the two hardware artifacts we ship, the Verilated system and the FPGA bitstream, to that structure. But, yes, we should document build-bin's structure sooner rather than later.

I think this has now been closed by 3c8ab3b so I'm going to close this issue.


Question: Is the Flexvolume a ram disk?

Describe the request
This is just a generic question but I can’t seem to tell if the Flex Volume is backed in tmpfs.  Could you confirm if the secrets in the volume are stored in non-persistent storage?
Explain why Key Vault FlexVolume needs it
No secrets on disk!
Describe the solution you'd like
Secrets in a RAM disk.
Describe alternatives you've considered
Additional context

Good question @johnlento! And yes it is a tmpfs volume. https://github.com/Azure/kubernetes-keyvault-flexvol/blob/master/deployment/flexvol-installer/kv#L148
Hope this helps!


[BUG] Sign up is not working as expected

sign up form is giving error

@kom-senapati Please assign this issue to me

@kom-senapati Please assign this issue to me

the issue is solved waiting to be merged

@parteekxo Thanks for updating


Path issue

First off, this is a great project. I have gotten the web server working inside a windows service and my code works great.
My issue is that the root of the project is

/publish-output/approot/packages/MYPROJNAME/1.0.0/root.

That folder contains the views and config files, but wwwroot is located at

/publish-output/wwwroot.

I am getting an unstyled page as all of my stylesheets and images are located at wwwroot and thus the server cannot find them. Do you know how to properly set up the paths so I can avoid these 404 errors?

It appears that the relative path I specify in hosting.json is getting ignored.

I managed to fix it. I had to add a couple new config providers to get things working properly:
var configBuilder = new ConfigurationBuilder()
                    .AddJsonFile("appsettings.json");

                configBuilder.AddJsonFile("hosting.json");
                configBuilder.AddEnvironmentVariables();
                var config = configBuilder.Build();


⚠ ClamAV has degraded performance

In da72609, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 692 ms

Resolved: ClamAV performance has improved in c469d92.


Upgrade to Webpack 2

Todo:

Fix the build
Replace codecov, or leave it out?

Don't forget to enable tree shaking with
    new webpack.LoaderOptionsPlugin({
      minimize: true,
      debug: false
    }),

Note that this might minimize everything too. If you don't want that I think you need to give each loader a minimize false argument.


Implement a temporary solution for Streaming Audio

The Gist
Currently bevy kira only supports StaticAudioHandle's and for small projects this may not be a big issue but for big projects this is quite bad.
Bandaid Fix
Bevy is currently in talks of this
See: https://github.com/bevyengine/bevy/issues/5422
This Kira plugin however should provide its own temporary solution. I'll start cooking up something when it's the weekend due to school.

I found this crate kira-loaders that built its own streaming interface on top of kira, without bevy. It looks like it would be somewhat straightforward to expand channels in bevy_kira_audio to support StreamingSoundSettings too.

That crate was part of an older kira version.


pombase gaf

I noticed the past week or so I am no longer able to download from the ftp site

What did you try to do (which browser, or command line?), and what were the symptoms?
I just downloaded the GAF via the GO annotations PomBase page, and directly from the pombase ftp site; both worked, although there was a bit of a lag.

OK it just worked for me...


Update to the latest ring version

Closing because MacOS builders seem not to like the new rustls version.


Update generated source code

Automated PR triggered by new code generation.
Update generated source code
Generated SDK source code using:

Generator version 3.12.2
Specification version 0.0.26
Automation (cloudant-sdks) version 90e4131

Thank you for the review @bessbd and @ricellis ! I am about to merge this.


OWLS-84562 - added tests for Namespace management enhancements

Jenkins : https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/2210/
Added tests to cover [https://jira.oraclecorp.com/jira/browse/OWLS-82046]  (https://github.com/oracle/weblogic-kubernetes-operator/pull/1860)
the tests don't cover Dedicated method, it is covered by other testclass
Testcases:

Create operator managing domain namespaces by SelectLabels
a. create namespace with specified label, make sure domain is started and operator can scale it
b. verify that domain with namespace with different label is not started/managed by operator, verify that as soon as namespace will be assigned the label, managed by operator, domain will be started and managed by operator.
c. verify that SelectLabel override domainNamespaces option from values and domain is not started even domainNamespace option is specified.
d. verify that domain in default namespace is not started
e. verify that operator can add/remove namespaces by upgrading helm chart and switch to different select method (RegExp)
f. verify that another operator (using List for domainNamespaces selection ) failed to share same namespace

Create operator managing domain namespaces by Expression searching for namespaces name starting with xoxoxo
a. create two namespace with namespaces staring with xoxoxo, make sure domains are started and operator can scale it
b. verify that domain with namespace with different name is not started/managed by operator
c. verify that RegExp override domainNamespaces option from values and domain is not started even domainNamespace option is specified.
d. verify that domain in default namespace is not started
e. verify that operator can add/remove namespaces by upgrading helm chart and switch to different select method (SelectLabels)
f. verify that another operator (using List for domainNamespaces selection ) failed to share same namespace

Create namespace before operator with setting enableRoleClusterBinding=false, and SelectLabel using that namespace, verify that domain can't be started , upgrade operator with reuse values, verify domain is started after upgrade.

newest results
https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/2263

latest run https://build.weblogick8s.org:8443/job/weblogic-kubernetes-operator-kind-new/2282/


Not able to scale chart properly

I have an app which shows chart and proportionally scales it based on window size. I scale everything (fonts, paddings, lines, bullets size ...). I want the chart to look exactly the same in every size. In this regard it should behave like a picture.
Problem is the that labels on x axis are changing their rotation when resizing. This is caused by bulhar constants in code like this one. I had to create custom category scale where I overrode the calculation of tick width to look something like this:
var tickWidth = me.getPixelForTick(1) - me.getPixelForTick(0);
var tickWidth = 0.9 * tickWidth;

I think you should reconsider using such constants.

@GabrielMancik I'd love to replace any constants like this. I'm not sure what the best way to go about it is. Do you have any thoughts on that matter? Should we have config options for this stuff?

I believe the constant mentioned initially has been replaced by the barPercentage option. https://github.com/chartjs/Chart.js/blob/8438da9e8426f8b707b1b0dbb87d43ae32ffc7d1/src/controllers/controller.bar.js#L497
In general, a lot of these constants have been cleaned up by this point so I'm going to close this. Going forward, let's file issues for each specific constant we find.


Add Elixir Support

mix.exs files for elixir projects should be supported to be updated

👍 thanks for the feature request @thepiwo.


Use a specific schema and version in Kafka Connect converter without auto-registering?

Hi folks,
I'm working on using Glue Schema Registry to provide an Avro schema for a source connector. What I would like to do is simply specify the registry name, schema name, and schema version and serialize incoming records using that specific schema. This is as opposed to having the connector convert Connect schemas into Avro schemas. I want to write the schema myself and then provide it directly to the connector. If incoming data is incompatible with the specified Avro schema in some way I would want the Connect task to fail rather than attempting to auto-register a new version of the Avro schema derived from the Connect schema.
Is this setup possible?
Thank you!

Hello,
Glue Schema Registry library does not support serializing the data by specific schema in the source connector. However, you can disable auto-registration by setting properties.put(AWSSchemaRegistryConstants.SCHEMA_AUTO_REGISTRATION_SETTING, false) (it is false by default, so not specifying also works). Ref

Is serializing by specific schema on the roadmap? I have a use case where I want to enforce a schema on my source record messages.


Don't require Job.create_job to pass in the class name

Instead of passing in the class name as the first argument to
Job.create_job you can just call .create_job on the end class
Depends: https://github.com/ManageIQ/manageiq-providers-kubernetes/pull/335

cc @Fryguy

@agrare Shouldn't it also remove https://github.com/ManageIQ/manageiq/blob/master/app/models/infra_conversion_job.rb#L2-L4 ?

@Fryguy there is a cyclic dependency (core has some kubernetes tests, and fixing that requires changing kubernetes repo which depends on this)
The kubernetes PR is green with this applied (https://github.com/Fryguy/manageiq-cross_repo/pull/3) and this is green with the kubernetes PR applied (I can't test this with manageiq-cross_repo yet)


Is it possible to get older WhatsApp messages?

Is it possible to get older WhatsApp messages? - that appear after pressing the  button “Click here to get older messages from your phone.”

I thin this features it still not yet implemented by team, you need to manage that in a database : mongodb for example

It's only possible to get "older" messages not read.
Adjust your config.ts to:
webhook -> readMessage: false,
Then use the method:
/api/{session}/unread-messages


Is there a way to switch ctx automatically?

currently, caffe2 supports CPUCtx and CUDACtx.   To run a model such as Googlenet, I need to implement all operators with the same context.  I want to implement an op such as  fully connection op(CUDA) inside Googlenet,  but others use existing operators(CPU),  is it feasible?

you can specify the context of each operator in the net as you want.  are you asking if you can run some operators on CPU and others on GPUs?


ManageIdentity

Hello,
I wonder to know if the library supports Managed Identity Authentication?
I have tried the suggested connection string to enable Microsoft Documentation (Endpoint=sb://{{Fully qualified namespace name}}/;Authentication=Managed Identity), then the connection string has not been resolved.
Thank you in advance

I have the same question.
@alisharifi01 did you found a solution?

@OlafKa I have not so far

did the issue resolve.. ?


Add TapeRulesStatus to the alarm message && Decrease alarm severity.

Fixes #11456
Status
ready
Description
With the current PR we are decreasing the alarm severity for all workflows stuck in the system unarchived for more than a month and we also add the list of TapeRulesStatus and the flag ParentageResolved to the alarm message, because those are the two most probable reasons for getting a workflow stuck into the system.
Is it backward compatible (if not, which system it affects?)
YES
Related PRs
None
External dependencies / deployment changes
No

One thing must be mentioned here:
While working on the tests of this PR I found out that, because we decided to send alarms with more clear messages as early as possible (basically from the _dispatcher method) and also from the archival pipeline as well, we obviously have ended up raising one and the same alarm per every workflow twice: [1]. Instead of creating a separate bug issue just for that. I am fixing this with my next commit to the current PR.
FYI @amaltaro
[1]
In [88]: msr._dispatchWflow(msrWflows['pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143'])
2023-04-03 14:10:36,333:INFO:MSRuleCleaner: Tape rule: a92d525de4f3464d9c599564f68de11a in non final state: SUSPENDED for workflow: pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143
2023-04-03 14:10:36,334:INFO:MSRuleCleaner: Skipping workflow: pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143 - tape transfers are not yet completed. Will retry again in the next cycle.
2023-04-03 14:10:36,340:CRITICAL:MSRuleCleaner: Found a workflow not archived since Sat Jan 28 00:39:48 2023.
Workflow:
{'ParentageResolved': True,
 'RequestName': 'pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143',
 'TapeRulesStatus': [('a92d525de4f3464d9c599564f68de11a',
                      'SUSPENDED',
                      '/NMSSM_XToYHTo2B2G_MX-320_MY-100_TuneCP5_13TeV-madgraph-pythia8/RunIISummer16MiniAODv3-PUMoriond17_94X_mcRun2_asymptotic_v3-v1/MINIAODSIM'),
                     ('a92d525de4f3464d9c599564f68de11a',
                      'SUSPENDED',
                      '/NMSSM_XToYHTo2B2G_MX-320_MY-100_TuneCP5_13TeV-madgraph-pythia8/RunIISummer16MiniAODv3-PUMoriond17_94X_mcRun2_asymptotic_v3-v1/MINIAODSIM')],
 'TransferDone': True,
 'TransferTape': False}
Has exceeded the Status Advance Timeout of: 720 hours for its current status: announced.
Additional info: Skipping workflow: pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143 - tape transfers are not yet completed. Will retry again in the next cycle.
Actions need to be taken!
2023-04-03 14:10:36,369:CRITICAL:MSRuleCleaner: Found a workflow not archived since Sat Jan 28 00:39:48 2023.
Workflow:
{'ParentageResolved': True,
 'RequestName': 'pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143',
 'TapeRulesStatus': [('a92d525de4f3464d9c599564f68de11a',
                      'SUSPENDED',
                      '/NMSSM_XToYHTo2B2G_MX-320_MY-100_TuneCP5_13TeV-madgraph-pythia8/RunIISummer16MiniAODv3-PUMoriond17_94X_mcRun2_asymptotic_v3-v1/MINIAODSIM'),
                     ('a92d525de4f3464d9c599564f68de11a',
                      'SUSPENDED',
                      '/NMSSM_XToYHTo2B2G_MX-320_MY-100_TuneCP5_13TeV-madgraph-pythia8/RunIISummer16MiniAODv3-PUMoriond17_94X_mcRun2_asymptotic_v3-v1/MINIAODSIM')],
 'TransferDone': True,
 'TransferTape': False}
Has exceeded the Status Advance Timeout of: 720 hours for its current status: announced.
Additional info: Not properly cleaned workflow: pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143
Actions need to be taken!
2023-04-03 14:10:36,378:INFO:MSRuleCleaner: plineArchive: Proper conditions not met: <@========== WMException Start ==========@>
Exception Class: MSRuleCleanerArchivalSkip
Message: Not properly cleaned workflow: pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143
	ClassName : None
	ModuleName : WMCore.MicroService.MSRuleCleaner.MSRuleCleaner
	MethodName : __init__
	ClassInstance : None
	FileName : /data/WMCore.venv3/srv/WMCore/src/python/WMCore/MicroService/MSRuleCleaner/MSRuleCleaner.py
	LineNumber : 66
	ErrorNr : 0

Traceback:

<@---------- WMException End ----------@>. Skipping archival in the current cycle.

And here is the result of my final fix: [1]
No alarm repetitions at all && every single reason contributing to the archival delay is properly logged into the alarm.
[1]
In [133]: msr._dispatchWflow(msrWflows['pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143'])
2023-04-03 15:01:00,016:INFO:MSRuleCleaner: Tape rule: a92d525de4f3464d9c599564f68de11a in non final state: SUSPENDED for workflow: pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143
2023-04-03 15:01:00,016:INFO:MSRuleCleaner: Skipping workflow: pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143 - tape transfers are not yet completed. Will retry again in the next cycle.
2023-04-03 15:01:00,048:CRITICAL:MSRuleCleaner: Found a workflow not archived since Sat Jan 28 00:39:48 2023.
Workflow:
{'ParentageResolved': True,
 'RequestName': 'pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143',
 'TapeRulesStatus': [('a92d525de4f3464d9c599564f68de11a',
                      'SUSPENDED',
                      '/NMSSM_XToYHTo2B2G_MX-320_MY-100_TuneCP5_13TeV-madgraph-pythia8/RunIISummer16MiniAODv3-PUMoriond17_94X_mcRun2_asymptotic_v3-v1/MINIAODSIM')],
 'TransferDone': True,
 'TransferTape': False}
Has exceeded the Status Advance Timeout of: 720 hours for its current status: announced.
Additional info: Skipping workflow: pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143 - tape transfers are not yet completed. Will retry again in the next cycle.
Not properly cleaned workflow: pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143

Actions need to be taken!
2023-04-03 15:01:00,056:INFO:MSRuleCleaner: plineArchive: Proper conditions not met: <@========== WMException Start ==========@>
Exception Class: MSRuleCleanerArchivalSkip
Message: Not properly cleaned workflow: pdmvserv_task_HIG-RunIISummer15wmLHEGS-05610__v1_T_220914_155035_4143
	ClassName : None
	ModuleName : WMCore.MicroService.MSRuleCleaner.MSRuleCleaner
	MethodName : __init__
	ClassInstance : None
	FileName : /data/WMCore.venv3/srv/WMCore/src/python/WMCore/MicroService/MSRuleCleaner/MSRuleCleaner.py
	LineNumber : 66
	ErrorNr : 0

Traceback:

<@---------- WMException End ----------@>. Skipping archival in the current cycle.

Hi @vkuznet,
While discussing about redirecting those  alarms to DM Team, I have two inquiries to make to you (hope the answer to those  won't take much of your time):

Do we have a well defined reposirotry to which we must create a PR for defining the new rerouting rules for those alarms
Can we start aggregating those alarms in the alert manager so that people (DM and Us) receive only a single message/alarm containing all of those workflows/tape rule Ids etc.

FYI: @amaltaro

Todor, CMS Monitoring configs are available in gitlab repo and what you're looking for is AlertManager config where you can provide regular PR, of course I would assume you'll learn AM configuration to understand the logic.
Regarding alerts aggregation. AlertManager by itself does not provide aggregation, even though its routes allow alerts flow. Said that, in CMS Monitoring we developed intelligence service which does the aggregation. So far the service consumes GGUS, and SNOW tickets to annotate our dashboards, but its logic and architecture will allow alert aggregation. Said that, to make aggregation someone needs to clearly define set of requirements and process of aggregation, then this can be easily implemented in intelligence service. Basically it allows to consume alerts from multiple sources and yield alerts since it is based on AM APIs. But, this will be separate development and with Ceyhun departure I'm not aware of anyone who can manage this task (I can do it but my time is tight to WMCore issues rather then monitoring one).

Todor, on further reading about AM it may be possible to do some aggregation if alerts in questions will have common attributes. I found one recipe which we may explore, see here. Therefore, it will require properly setup alert attributes among those which you may want to aggregate. For instance, if a specific agent will issue multiple alerts in some time interval those can be grouped by agent name, and only one alert will be issue to a specific web hook.

Thanks for the review @amaltaro
I think I've addressed all your comments. Please take another look.


🎛 Add basic Stimulus documentation for developers building with Wagtail

As part of the Stimulus  🎛 RFC 78 it would be good to ensure that there is a basic set of documentation for how to use Stimulus in Wagtail.
Pertinent section of the Wagtail docs
There is a section in the Wagtail docs Customising Admin Templates > Extending client-side components, it would be good to either split this out to its own page and/or extend this with an introduction to using Stimulus within Wagtail
Details
The RFC contains a proposed draft for this section - https://github.com/wagtail/rfcs/blob/main/text/078-adopt-stimulus-js.md#a-documentation-for-developers
Clarity required

Should we split out Custom user interface fonts, Custom user interface colours and Extending client-side components to a new page maybe called Customising the user interface?
Are we happy to document four levels of customisation; a. fonts & colours, b. dispatching / listening to DOM events, c. Stimulus, d. React?
Is there somewhere else we want to put this documentation?
What controllers, if any, do we want to formalise in the docs (maybe; w-action, w-sync, w-slug/clean?).

Additional details

Example use cases could be the following issues;

Adding a keyboard shortcut (w-action) - pending https://github.com/wagtail/wagtail/issues/10167
Adding a global message (via event dispatching) - pending https://github.com/wagtail/wagtail/issues/9493
A live field - could close https://github.com/wagtail/wagtail/issues/1063 & pending https://github.com/wagtail/wagtail/issues/10088
A dynamic field - could close https://github.com/wagtail/wagtail/issues/161 & probably also pending https://github.com/wagtail/wagtail/issues/10088
A smart validator field - could copy/paste the answer here and close this issue https://github.com/wagtail/wagtail/issues/7417#issuecomment-1438396850

Documentation examples may be revised based on the progress of https://github.com/wagtail/wagtail/issues/10133
Should link to the contributor documentation for general Stimulus tips & approach - based on result of https://github.com/wagtail/wagtail/issues/10093 PRs

Assigning myself for now - will raise this for a quick bit of clarity at the next Core Team meeting.
@thibaudcolas  any thoughts on documentation structure here?

@lb- I think we could rename this existing page to "Customising the admin interface", and give Stimulus its own page if we think it’ll be long enough to justify it?
If we want to document specific controllers I’d keep it to a minimum (name and description?) so we still have room to change how they work in the future.

@thibaudcolas good idea.

General vibe from core team is a new page within Extending Wagtail would make more sense https://docs.wagtail.org/en/stable/extending/index.html

Would be good to include a replacement for WidgetWithScript (just using a static js with Stimulus attached to a widget so the JS only loads when needed). See https://github.com/wagtail/wagtail/pull/10311 for context.

Made a start https://github.com/lb-/wagtail/tree/docs/10197-extending-wagtail-with-stimulus

Going to pull from 5.0, I have something close but likely no time to get it reviewed and merged.


app stops and music stop playing after 5-10 minutes in background.

Latest version plus many before it
on Android 12 and 11 on Realme/Oppo

check that the app has unrestricted network and battery permission. It isn't the app that stops, it is android that is stopping the app.

Tried many  things like disabling optimization etc  to no avail

I don't really have any idea but maybe this can help
https://github.com/katzer/cordova-plugin-background-mode


How to write comments: discuss

Right now there are two elements and two styles of writing comments:

say what the function does wrt to the spec (from Surma): constructor, createdCallback
say what the element does in that function (from Rob): constructor, createdCallback

Both are great! Should we do both?

I actually didn’t follow my own review nit I gave to Rob: The block comment above a function should give a high-level description of what that function does. I’ll adjust my comments.
That doesn’t mean we should not mention the spec, but I’d be interested to hear what y’all think about that. It might get repetitive across elements, but it’s also an important thing to teach with regards to CEv1. WDYT?

We could make a kind of generic element  that explains the features of CE and have folks lead off with that maybe?

class DashExample extends HTMLElement {
  // Explain how constructor works
  constructor

  // Explain how connected works
  connectedCallback

  // Explain how attribute changed works
  attributeChangedCallback
}

Yeah could do. Doesn’t feel right to me, but I also don’t have a better suggestion except for duplicating it across all elements.

Another option would be to write a kind of intro/preamble to the project
linking to Eric's primer on custom elements
https://developers.google.com/web/fundamentals/getting-started/primers/customelements
On Wed, Jan 25, 2017 at 9:07 AM, Surma<EMAIL_ADDRESS>wrote:

Yeah could do. Doesn’t feel right to me, but I also don’t have a better
suggestion except for duplicating it across all elements.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/dash-elements/issues/6#issuecomment-275168265,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABBFDRJrZbgftiTilVqx1f5Dld6xOFxCks5rV4FqgaJpZM4Ls9P_
.

What do y’all think is the main use-case for external folks of this?
Are they going to read all of DASH because they are interested or are they on the hunt for an accordion and find this and just gonna read through that one element?
My gut says it’s the latter, and that would speak in favor duplicating that information across multiple elements. I do realize that it’s hard to draw the line as to what is assumed to be “common knowledge” and what needs to be explained, so having a collection of links in the intro is a really good idea imo.

The latter. Yeah maybe just some primer links in the beginning of each
element would suffice
On Thu, Jan 26, 2017, 6:59 AM Surma<EMAIL_ADDRESS>wrote:

What do y’all think is the main use-case for external folks of this?
Are they going to read all of DASH because they are interested or are they
on the hunt for an accordion and find this and just gonna read through that
one element?
My gut says it’s the latter, and that would speak in favor duplicating
that information across multiple elements. I do realize that it’s hard to
draw the line as to what is assumed to be “common knowledge” and what needs
to be explained, so having a collection of links in the intro is a really
good idea imo.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/GoogleChrome/dash-elements/issues/6#issuecomment-275409092,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABBFDRYoctL5TwfV3B8FT6pPslI94rAZks5rWLS_gaJpZM4Ls9P_
.

Okay, let’s add a section to the template :)
Feel free to grab this issue, otherwise I’ll do it at some point.

So bottom line: We will go with @robdodson’s version and move the spec relevant stuff to the intro section. Agreed?

agreed. btw sorry for lagging i've been traveling the last 4 days

Fixed with #15


Kstream binder: producer default Serde changes

Change the way the default Serde classes are selected for key and value
in producer when only one of those is provided by the user.
Fix #190

Merged as 1aecd024041601ea05f3cb93dcd8c3f1340fefba


result of 2d ground truth

Hello, when using 2d ground truth training, I set use_daj_as_2d to True, but my results are higher than those in the paper. I would like to ask about the specific parameter settings for the 2d ground truth results in the paper

@l2day How much difference are you observing? Note that selection of GPU and batch size also matters. We have used 2x A40 GPUs so when you see batch size is 16 in config, that means each GPU has received batch of 8 data. So Maybe you'll get a closer result compared to paper if you divide the batch size by 2 in case you are using one gpu or multiply by 2 if you use 4 GPUs. The choice of GPU also matters and it is hard to replicate the exact same result when using a different GPU.


[R-package] Factor out custom R interface to lib_lightgbm

Summary
The R  package calls a C++ library (lib_lightgbm.so) with the  R function .Call().  Doing this requires an interface to map R data types to C data types and back. Right now we do not use the SEXP ("S expression") interface that ships with R's built-in headers.
So far our custom implementation has worked well, but there is a risk that future versions of R  will not work with it.
To close this issue, remove R_object_helper.h, including LGBM_SER and  LGBM_SE. Replace them with the corresponding symbols from R.h, Rinternals.h, and the other R built-in headers.
It is likely possible to do this in pieces....it does not have to be a single pull request.
Motivation
This may not be strictly necessary to get to CRAN, but it will bring the R package into tighter compatibility with the R build tools, so should improve the chances we'll be able to support new  versions of R with no changes.
I suspect, though I don't know for sure, that this would also resolve these warnings we're getting from some compilers:

See https://github.com/microsoft/LightGBM/pull/3009#issuecomment-617219336 and

Closing this in favor of being in #2302 , the place where we keep all feature requests. Anyone is welcome to contribute this! If you want to work on it, leave a comment here.

I don't get the context in full:

Why does the GH version use lib_lightgbm while the CRAN version uses lightgbm? Why not make both lightgbm?
What was the reason why it had replacements for R's headers in the first place? Is there something that will break if it were to switch to R's headers?
Why even the .Call are wrapped into some lgb.* function?
If it were to use R headers, should it use R's external pointers system in order to call the C++ destructors? Or was it intentional that those destructors were put into R6 finalizers?
Is there some particular reason why e.g. the pointers are stored in objects of type double? Is the R package meant to be compilable in non-standard CPU architectures?
What about things like the logger? Should it also switch to R's functions?
Is the R library meant to be compiled in non-standard ways too? e.g. will you create R builds using msvc or something like that?

Why does the GH version use lib_lightgbm while the CRAN version uses lightgbm? Why not make both lightgbm?
Is the R library meant to be compiled in non-standard ways too? e.g. will you create R builds using msvc or something like that?

This is related to the fact that we also offer CMake-based builds of the package (using a different toolchain from CRAN) for some features that are difficult to get to CRAN or prohibited by CRAN's policies, like a GPU-enabled version of the package and builds with MSVC.
You can see https://github.com/microsoft/LightGBM/blob/master/build_r.R and https://github.com/microsoft/LightGBM/tree/master/R-package#install for reference.

What was the reason why it had replacements for R's headers in the first place? Is there something that will break if it were to switch to R's headers?

When the LightGBM R package was first created, the original authors were concerned that pieces of R.h were GPL-licensed, and so they created this custom re-implementation. We've since come to the understanding that that isn't problematic, but haven't yet done the work to replace LightGBM's custom interface to R.
https://github.com/microsoft/LightGBM/issues/629#issuecomment-474995635
https://github.com/microsoft/LightGBM/blob/13d0ceee76f4643df13ecd5f841facca919e665a/R-package/src/R_object_helper.h#L8-L11
That historical legal stuff is the only reason.

Why even the .Call are wrapped into some lgb.* function?

Right now .Call() calls are wrapped in an internal function lgb.call() to do error handling on the R side. But I have two PRs open currently to switch them all to bare .Call() calls: #4163, #4155.

If it were to use R headers, should it use R's external pointers system in order to call the C++ destructors? Or was it intentional that those destructors were put into R6 finalizers?

I don't understand this question, sorry. Would appreciate some specific links to code or documentation.

Is there some particular reason why e.g. the pointers are stored in objects of type double? Is the R package meant to be compilable in non-standard CPU architectures?

The handles created to data are doubles with 64-bit R and integers with 32-bit R. https://github.com/microsoft/LightGBM/blob/13d0ceee76f4643df13ecd5f841facca919e665a/R-package/R/utils.R#L9-L15
Does that answer your question?

What about things like the logger? Should it also switch to R's functions?

When lib_lightgbm is built as part of the R package, its logger already uses the R I/O functions:
https://github.com/microsoft/LightGBM/blob/13d0ceee76f4643df13ecd5f841facca919e665a/include/LightGBM/utils/log.h#L132-L159.
https://github.com/microsoft/LightGBM/blob/13d0ceee76f4643df13ecd5f841facca919e665a/include/LightGBM/utils/log.h#L121-L128

These are the destructors that I'm talking about:
https://github.com/microsoft/LightGBM/blob/1e95cb097757996cd82699071c82c205bf2b48a5/R-package/src/lightgbm_R.cpp#L314
https://github.com/microsoft/LightGBM/blob/1e95cb097757996cd82699071c82c205bf2b48a5/R-package/src/lightgbm_R.cpp#L196
Which are put under R6 finalizers:
https://github.com/microsoft/LightGBM/blob/1e95cb097757996cd82699071c82c205bf2b48a5/R-package/R/lgb.Booster.R#L13
https://github.com/microsoft/LightGBM/blob/1e95cb097757996cd82699071c82c205bf2b48a5/R-package/R/lgb.Dataset.R#L10
And BTW using them like this currently can lead to segmentation faults as their validity is not checked (https://github.com/microsoft/LightGBM/issues/4208).
Another thing: Rf_error used in the logger is a C function which produces an R error. It does not do the same as a C++ exception as it won't trigger stack unwinding (i.e. will lead to memory leaks in some functions). That'd be better replaced by REprintf (prints an error message) and then throwing the R error from the calling function, being careful to destruct any C++ objects if needed.

Oh interesting! It sounds like you're really knowledgeable about this. We'd really appreciate some contributions if you see opportunities to improve the way the package is set up. It doesn't have to be one large PR that completely solves this issue.
For example, the point you made about using REprintf seems like it could be done in a fairly focused PR.
If you don't have the time or interest we'll understand and I will try to do what I can based on your detailed write-ups here.

Would you be willing to add a dependency on either Rcpp or cpp11? That'd make things a lot easier.

I'm opposed to adding a new dependency unless we really have to, and at this moment I'm not convinced that it's necessary.
{xgboost}'s codebase is very similar to this project's R package, and they haven't needed to do that.

@david-cortes are you interested in contributing fixes for this issue in the next few weeks?
If you aren't, I'm going to make it my next priority in this project (using all the excellent insight you've given us in recent comments). Just want to know so you and I aren't working on the same thing at the same time.

I don't have any plans to work on these issues right now, but feel free to ask if you need more suggestions.

Ok great, thank you so much! I probably will be asking you. We really appreciate it!!
I recognized you from {catboost}'s CRAN issue (https://github.com/catboost/catboost/issues/439), glad to see you here as well 😀


Process Error Log Filenames

The function get_error_log_file_content takes a filename, but we didn't have functions to readily retrieve the filenames.
Return error log filenames for given process, return top 5, and sort descending:
tm1.processes.get_error_log_filenames(process_name=<process name>, top=5, descending=True)
Return all error log filenames with 202312 timestamp in descending order
tm1.processes.search_error_log_filenames('202312', descending=True)
These functions may not work with V12.

Nice work. Thanks


Adding another home page

Suggestion
It is unclear especially to nontechnical users what the whole process is. Making another home page that explains the process, and having an option to go to either web capture or upload would be helpful.

@erikanoms , Could you please drop here any suggestions that you have  for the changes in UI

HOMEPAGE Figma file: https://www.figma.com/file/exSOAQauxk9QRcca9uwgD4/ReproServer-Redesign?node-id=302%3A103&t=zOT6Vv2kVVvJvdna-1

Make "Share reproducible work" bold text
Change the text description under "share reproducible work" to the one in the Figma file. (Fixed some errors, got rid of the bottom margins, and made the text 18px)
Texts inside the ellipses look like the bottom line of the text box is aligned center in the circles, so maybe get rid of the bottom margin of the texts? (currently, it shows as margin-bottom: 0.5rem)
Change the colors of the ellipses to make them more accessible. For HEX codes, please refer to the Figma file(just something to consider but you could use an image for the trace-pack-record-replay part? It might be easier to make it responsive)
Add a margin of 15px between the ellipses and the texts at the bottom (please refer to the Figma file)
Change the color of the arrows to #838383
Get rid of the horizontal lines around the upload section. Instead, change the background colors of each section (Top section: #F9F9F9, upload section #FFFFFF, Examples section #F9F9F9)
Add the text "Select a package to upload"  to the upload section
Get rid of the box around choose file (It confuses users between text box), and shorten the text box for the URL. please refer to the Figma file

WHILE UPLOADING

Can you make the Upload button disappear while uploading?
Change the progress text "x% uploaded... please wait" to "Uploading... x%" and bring it below the progress bar

PACKAGE (Please refer to the design systems page on the figma file)

Change the text sizes
Package xxx: Bold 36px
Run the experiment: Regular 13px
Parameters, Expose ports, Input files: Bold 24px
Other texts above text boxes and files: Regular 18pt
Get rid of boxes around "Choose File No file chosen" and can you change them to a button? (Screen shot if from the home page on the figma file).

WEB CAPTURE

Change the text sizes
Web Capture: Bold 36px
The description below that: Regular 18px
RPZ File, WACZ File, Hostname, Port number: Regular 18px
Get rid of the text description under "Web Capture"
Get rid of the text "Would you like to replace the web archive?"
Add text above the three buttons "Click "Record from browser" if you want to have more control and manually crawl. Click "Start automated crawl" if you prefer to crawl automatically. After the crawl is complete, you will be redirected to this page. From there, download the new RPZ file (It has a WACZ file in it)."
Add horizontal spaces of 30px between three buttons

WEB CAPTURE

Change the text sizes
Web Capture: Bold 36px - changed to display-6 in bootstrap, as text is responsive(40 px)
The description below that: Regular 18px -
RPZ File, WACZ File, Hostname, Port number: Regular 18px - Done ( changed to h5, which is 20 px)
Get rid of the text description under "Web Capture" - Done
Get rid of the text "Would you like to replace the web archive?" - Done
Add text above the three buttons "Click "Record from browser" if you want to have more control and manually crawl. Click "Start automated crawl" if you prefer to crawl automatically. After the crawl is complete, you will be redirected to this page. From there, download the new RPZ file (It has a WACZ file in it)." - Done
Add horizontal spaces of 30px between three buttons - Spacing added using bootstrap utility(mx-4), 24 px

WHILE UPLOADING

Can you make the Upload button disappear while uploading? - done
Change the progress text "x% uploaded... please wait" to "Uploading... x%" and bring it below the progress bar - done

HOMEPAGE Figma file: https://www.figma.com/file/exSOAQauxk9QRcca9uwgD4/ReproServer-Redesign?node-id=302%3A103&t=zOT6Vv2kVVvJvdna-1 **you can see CSS by clicking an element and selecting Inspect tab from the top right bar

Make "Share reproducible work" bold text - Done
Change the text description under "share reproducible work" to the one in the Figma file. (Fixed some errors, got rid of the bottom margins, and made the text 18px) - Done
Texts inside the ellipses look like the bottom line of the text box is aligned center in the circles, so maybe get rid of the bottom margin of the texts? (currently, it shows as margin-bottom: 0.5rem) - Not Sure about this
Change the colors of the ellipses to make them more accessible. For HEX codes, please refer to the Figma file(just something to consider but you could use an image for the trace-pack-record-replay part? It might be easier to make it responsive)
Add a margin of 15px between the ellipses and the texts at the bottom (please refer to the Figma file) - Done (16px - mt3)
Change the color of the arrows to #838383 - Done
Get rid of the horizontal lines around the upload section. Instead, change the background colors of each section (Top section: #F9F9F9, upload section #FFFFFF, Examples section #F9F9F9) - Done
Add the text "Select a package to upload"  to the upload section - Done
Change the text size for "Upload a .rpz file to get started" & "or provide a package's URL" to 18px
Get rid of the box around choose file (It confuses users between text boxes), and shorten the text box for the URL. please refer to the Figma file - Needs Rework


operator [R] 3scale-community-operator (0.3.0 0.4.0 0.5.1 0.6.0 0.7.0)

Signed-off-by: Eguzki Astiz Lezaun<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@eguzki you are missing com.redhat.openshift.versions: "v4.6-v4.8" line in annotations.yaml for every relevant operator.
This gives an instruction where you would like to release your opertor. OLM properties are related to upgrade for already released operator. In packegmanifest format there was no way to apply label, so we labeled it on the fly during backgroud conversion to bundle format.

related to https://github.com/operator-framework/operator-sdk/issues/5688#issuecomment-1149618189
@eguzki
you have 2 options:

use v1beta1 with preserveUnknownFields: false
use v1

/merge possible

/retest

/merge possible

/merge possible


$.prompt doesn't support utf-8?

windows, vscode, gitbash

Could you include some reproduction steps?


USB: usb_dc_stm32_isr causing memory data access violation fault

Describe the bug
When usb_dc_stm32_isr is invoked and performs a USB DC Reset (by calling msd_init()) it clears the curr_offset to zero. If this ISR is activated after memoryWrite() has been called and has updated curr_offset to a block size (thus thread_op will be set to THREAD_OP_WRITE_QUEUED), then when thread_memory_write_done() is invoked the curr_offset will be reset to 0 which will result in overflowed_len being set to a negative number. Since it is treated as a unsigned integer it results in memmove attempting to move a very large block of data resulting in a memory access violation, and thus a fault and reset.

Target: STM32F4112G
Workaround:

	if (BLOCK_SIZE > (curr_offset + size)) {
		overflowed_len = 0;
	}

Commit that changed this behavior was: 6d4266a45173754e2e231dfdc096250b1e956595
To Reproduce
Not fully sure how to consistently reproduce, but the following may work often.

Build zephyr code for a board that has USB mass storage capabilities (I am using the STM32F4112G chipset).
Flash the board with the built code and use a debugger (I am using a Segger)
Put a breakpoint at the following lines of code:

thread_op = THREAD_OP_WRITE_QUEUED; /* write_queued */

in
static void memoryWrite(uint8_t *buf, uint16_t size)
{
	if (curr_lba >= block_count) {
		LOG_WRN("Attempt to write past end of device: lba=%u", curr_lba);
		fail();
		return;
	}

	/* we fill an array in RAM of 1 block before writing it in memory */
	for (int i = 0; i < size; i++) {
		page[curr_offset + i] = buf[i];
	}

	/* if the array is filled, write it in memory */
	if (curr_offset + size >= BLOCK_SIZE) {
		if (!(disk_access_status(disk_pdrv) & DISK_STATUS_WR_PROTECT)) {
			LOG_DBG("Disk WRITE Qd %u", curr_lba);
			thread_op = THREAD_OP_WRITE_QUEUED; /* write_queued */
			defered_wr_sz = size;
			k_sem_give(&disk_wait_sem);
			return;
		}
	}

	curr_offset += size;
	length -= size;
	csw.DataResidue -= size;

	if ((!length) || (stage != MSC_PROCESS_CBW)) {
		csw.Status = (stage == MSC_ERROR) ? CSW_FAILED : CSW_PASSED;
		sendCSW();
	}
}

and
curr_offset = 0U;

in
static void msd_init(void)
{
	(void)memset((void *)&cbw, 0, sizeof(struct CBW));
	(void)memset((void *)&csw, 0, sizeof(struct CSW));
	(void)memset(page, 0, sizeof(page));
	curr_lba = 0U;
	length = 0U;
	curr_offset = 0U;
}

and
memmove(page, &page[BLOCK_SIZE], overflowed_len);

in
static void thread_memory_write_done(void)
{
	uint32_t size = defered_wr_sz;
	size_t overflowed_len = (curr_offset + size) - BLOCK_SIZE;

	if (overflowed_len > 0) {
		memmove(page, &page[BLOCK_SIZE], overflowed_len);
	}

	curr_offset = overflowed_len;
	curr_lba += 1;
	length -= size;
	csw.DataResidue -= size;

	if (!length) {
		if (disk_access_ioctl(disk_pdrv, DISK_IOCTL_CTRL_SYNC, NULL)) {
			LOG_ERR("!! Disk cache sync error !!");
		}
	}

	if ((!length) || (stage != MSC_PROCESS_CBW)) {
		csw.Status = (stage == MSC_ERROR) ? CSW_FAILED : CSW_PASSED;
		sendCSW();
	}

	thread_op = THREAD_OP_WRITE_DONE;

	usb_ep_read_continue(mass_ep_data[MSD_OUT_EP_IDX].ep_addr);
}

When the breakpoint at
thread_op = THREAD_OP_WRITE_QUEUED; /* write_queued */

is reached wait about 20 seconds, before pressing play. (I have also the USB Console enabled and I am seeing the console on my computer show USB disconnected before continuing, perhaps this is what is invoking the USB ISR).
After resuming the reset should occur by hitting the breakpoint
curr_offset = 0U;

followed by
memmove(page, &page[BLOCK_SIZE], overflowed_len);

where overflowed_len should be a very large value, resulting in a memory access violation.
Stacks at the breakpoints are:
usb_dc_stm32_isr -> HAL_PCD_IRQHandler -> PCD_EP_OutXfrComplete_init -> HAL_PCD_DataOutStageCallback -> mass_storage_bulk_out -> memoryWrite
usb_dc_stm32_isr -> HAL_PCD_IRQHandler -> HAL_PCD_ResetCallback -> forward_status_cb -> mass_storage_status_cb -> msd_init
z_thread_entry -> mass_thread_main -> thread_memory_write_done
Expected behavior
When the USB ISR is invoked, after the memoryWrite call sets up the buffer for a write of a block size or greater, but before the thread memory write done is invoked, thread memory write should not attempt to write a block size of an invalid length.
Impact
Minimal impact with the patch I added to my code base, but might not be best long term solution.
Environment (please complete the following information):

OS: MacOS
Toolchain: Zephyr SDK
Version: v3.4.0

Minimal impact with the patch I added to my code base, but might not be best long term solution.

Could you please submit this patch with a PR? This looks good enough for me because the old stack MSC implementation is doomed anyway.
The long term solution is to switch to next USB stack which has completely new MSC implementation which properly synchronizes accesses (and also properly reports errors instead of hardcoding an response to make test suite pass).


keras create/load model fails on Apple M2 cpu.  Same code works on Ryzen

tf_env.txt
You can obtain the TensorFlow version with:
python -c "import tensorflow as tf; print(tf.version.GIT_VERSION, tf.version.VERSION)"
result:
v2.13.0-rc2-7-g1cb1a030a62 2.13.0
Can't load a keras model that I just created.  The issue is not specific to Adam; all of the optimizers have the same issue.
Describe the problem.
code:
  from tensorflow import keras

  optimizer = keras.optimizers.Adam()

  vh  = keras.Input(shape=(2,3), name = 'vh')
  v1  = keras.layers.Dense(512)(vh)

  output  = keras.layers.Dense(1, activation='softmax', name='prediction')(v1)

  model = keras.Model(inputs=vh, outputs=[output], name="antibody_model")

  model.compile(optimizer=optimizer )

  model.save('nn_model.keras')
  test = keras.models.load_model('nn_model.keras')

output:
the legacy Adam is missing the method  "build".  This same code works on non-mac platforms.
WARNING:absl:At this time, the v2.11+ optimizer tf.keras.optimizers.Adam runs slowly on M1/M2 Macs, please use the legacy Keras optimizer instead, located at tf.keras.optimizers.legacy.Adam.
WARNING:absl:There is a known slowdown when using v2.11+ Keras optimizers on M1/M2 Macs. Falling back to the legacy Keras optimizer, i.e., tf.keras.optimizers.legacy.Adam.
WARNING:absl:At this time, the v2.11+ optimizer tf.keras.optimizers.Adam runs slowly on M1/M2 Macs, please use the legacy Keras optimizer instead, located at tf.keras.optimizers.legacy.Adam.
WARNING:absl:There is a known slowdown when using v2.11+ Keras optimizers on M1/M2 Macs. Falling back to the legacy Keras optimizer, i.e., tf.keras.optimizers.legacy.Adam.
Traceback (most recent call last):
File "/Users/matthewclark/eclipse-workspace/antibody_classification/test/test.py", line 17, in
test = keras.models.load_model('nn_model.keras')
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/Shared/anaconda3/envs/ability/lib/python3.11/site-packages/keras/src/saving/saving_api.py", line 230, in load_model
return saving_lib.load_model(
^^^^^^^^^^^^^^^^^^^^^^
File "/Users/Shared/anaconda3/envs/ability/lib/python3.11/site-packages/keras/src/saving/saving_lib.py", line 275, in load_model
raise e
File "/Users/Shared/anaconda3/envs/ability/lib/python3.11/site-packages/keras/src/saving/saving_lib.py", line 240, in load_model
model = deserialize_keras_object(
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/Shared/anaconda3/envs/ability/lib/python3.11/site-packages/keras/src/saving/serialization_lib.py", line 710, in deserialize_keras_object
instance.compile_from_config(compile_config)
File "/Users/Shared/anaconda3/envs/ability/lib/python3.11/site-packages/keras/src/engine/training.py", line 3582, in compile_from_config
self.optimizer.build(self.trainable_variables)
^^^^^^^^^^^^^^^^^^^^
File "/Users/Shared/anaconda3/envs/ability/lib/python3.11/site-packages/keras/src/optimizers/legacy/optimizer_v2.py", line 997, in getattribute
raise e
File "/Users/Shared/anaconda3/envs/ability/lib/python3.11/site-packages/keras/src/optimizers/legacy/optimizer_v2.py", line 987, in getattribute
return super().getattribute(name)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'Adam' object has no attribute 'build'

@drmatthewclark,
I tried to execute the mentioned code on Apple M1 with the tf-nightly(2.15.0-dev20230927) and it was executed without any fail or error. Kindly find the screenshot below for the reference.

Thank you!

@tilakrayal i confirm that with tf-nightly the error it seems to be fixed
% pipenv graph
...
tf-nightly==2.15.0.dev20230928
└── tf-nightly-macos [required: ==2.15.0-dev20230928, installed: 2.15.0.dev20230928]

it seems it solves the error
% pipenv run adam
WARNING:absl:At this time, the v2.11+ optimizer `tf.keras.optimizers.Adam` runs slowly on M1/M2 Macs, please use the legacy Keras optimizer instead, located at `tf.keras.optimizers.legacy.Adam`.
WARNING:absl:At this time, the v2.11+ optimizer `tf.keras.optimizers.Adam` runs slowly on M1/M2 Macs, please use the legacy Keras optimizer instead, located at `tf.keras.optimizers.legacy.Adam`.
WARNING:absl:Skipping variable loading for optimizer 'Adam', because it has 9 variables whereas the saved optimizer has 1 variables.

I also reported the same finding here: https://github.com/tensorflow/tensorflow/issues/61915#issuecomment-1738816019

I'm using mac m1 pro and tensorflow version is 2.14.0. I was facing the same error "AttributeError: 'Adam' object has no attribute 'build'" while loading the saved model, if I save the model as below
model = Sequential() model.add(Embedding(MAX_FEATURES+1, 32)) model.add(Bidirectional(LSTM(32, activation='tanh'))) model.add(Dense(128, activation='relu')) model.add(Dense(256, activation='relu')) model.add(Dense(128, activation='relu')) model.add(Dense(1, activation='sigmoid')) model.compile(loss='BinaryCrossentropy', optimizer='Adam') model.fit(train, epochs=1, validation_data=val) model.save('data/model_data.keras')
I updated the optimizer and it is working fine now
import tensorflow as tf
model.compile(loss='BinaryCrossentropy', optimizer=tf.keras.optimizers.Adam())

@EswarJanjanam The fix is on tf-nightly. Please do pip install tf-nightly and see if your code works, thanks!

$pip install tf-nightly
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
ERROR: Could not find a version that satisfies the requirement tf-nightly (from versions: none)
ERROR: No matching distribution found for tf-nightly

$pip install tf-nightly
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
ERROR: Could not find a version that satisfies the requirement tf-nightly (from versions: none)
ERROR: No matching distribution found for tf-nightly

Crap, it's my mirroring problem, sorry!
But it didn't solve the problem.

AttributeError: 'Adam' object has no attribute 'build'

$pip install tf-nightly
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
ERROR: Could not find a version that satisfies the requirement tf-nightly (from versions: none)
ERROR: No matching distribution found for tf-nightly

Same error exists on M2 mac.
AttributeError: 'Adam' object has no attribute 'build'

.h5 format is one of solution instead of .keras format for now.
I hope I can save model as .keras format.

$pip install tf-nightly
Looking in indexes: https://pypi.tuna.tsinghua.edu.cn/simple
ERROR: Could not find a version that satisfies the requirement tf-nightly (from versions: none)
ERROR: No matching distribution found for tf-nightly

Same error exists on M2 mac.
AttributeError: 'Adam' object has no attribute 'build'

.h5 format is one of solution instead of .keras format for now. I hope I can save model as .keras format.

Yeah, I mean can't he just automatically adapt to the solution?

Having the exact same issue, and can confirm that tf-nightly is NOT working for me.

same issue

Having the same issue as well on Mac M1. The same code works on cloud workstation on linux.

After much trial and error, installing keras-nightly solved the issue and my model started working.


REL: 4.0.2

https://github.com/conda/libconda/releases/tag/4.0.2

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

fyi, @ericdill

Might be worth giving this a re-render.

Thanks all.


Explicitly autoincrement the ID

SAP HANA doesn't autoincrement by default, so flask_profiler doesn't work with that RDBMS.

I think I just had an issue in my local environment, sorry.


tensorflow build failure on x86_64-linux as of 9cfb5c05

Issue description
Build of tensorflow failed on x86_64-linux as of 9cfb5c053b8cfecd56f41d07a1fc141cdf0302ee. This is currently breaking python3Packages.tensorflow.
error: builder for '/nix/store/25l8gv78aasn75w9qdl6kpp8cp4yd7dy-tensorflow-2.9.1.drv' failed with exit code 1;
       last 10 log lines:
       >                  from tensorflow/lite/schema/schema_utils.cc:15:
       > /nix/store/532rdc2yrbfva8lhpbhyvgn1ihix4zbd-flatbuffers-2.0.6/include/flatbuffers/table.h:115:8: note: candidate: 'bool flatbuffers::Table::VerifyField(const flatbuffers::Verifier&, flatbuffers::voffset_t, size_t) const [with T = unsigned int; flatbuffers::voffset_t = short unsigned int; size_t = long unsigned int]'
       >   115 |   bool VerifyField(const Verifier &verifier, voffset_t field,
       >       |        ^~~~~~~~~~~
       > /nix/store/532rdc2yrbfva8lhpbhyvgn1ihix4zbd-flatbuffers-2.0.6/include/flatbuffers/table.h:115:8: note:   candidate expects 3 arguments, 2 provided
       > INFO: Elapsed time: 1138.232s, Critical Path: 24.86s
       > INFO: 2236 processes: 559 internal, 1677 local.
       > FAILED: Build did NOT complete successfully
       > FAILED: Build did NOT complete successfully
       >
       For full logs, run 'nix log /nix/store/25l8gv78aasn75w9qdl6kpp8cp4yd7dy-tensorflow-2.9.1.drv'.
error: 1 dependencies of derivation '/nix/store/wzp84jfz776ywpcx5dlqbk4dlasyhgnd-python3.10-tensorflow-2.9.1.drv' failed to build

full build log
python3Packages.tensorflow maintainers cc: @jyp @abbradar
tensorflow maintainers cc:
Other cc: n/a
Steps to reproduce

Checkout nixpkgs at commit 9cfb5c053b8cfecd56f41d07a1fc141cdf0302ee
Run nix-build -A tensorflow

Technical details
 - system: `"x86_64-linux"`
 - host os: `Linux 5.15.0-1014-azure, Ubuntu, 20.04.4 LTS (Focal Fossa), nobuild`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.10.3`
 - nixpkgs: `/nix/store/dwmdnf3w9vsrnqqsppnx2rgi732iig4z-source`

Misc.
This issue was automatically generated by nixpkgs-upkeep.

CI workflow that created this issue.
Internal tags: -8643130738251957971<PHONE_NUMBER>189490839

dup of https://github.com/NixOS/nixpkgs/issues/185273