Slow jit with list argument

Providing a list of int to jax.ops.index_add results in a very slow jit performance. See example below.
import time

import jax
import jax.numpy as jnp
from jax import jit

def f(x, indices, y):
    return jax.ops.index_add(x, (indices,), y)

x = jnp.ones(10000)
y = jnp.ones(3000)

indices = list(range(3000))
start = time.time()
f(x, indices, y)
print('list: ' + str(time.time() - start))

f_jit = jit(f)
start = time.time()
f_jit(x, indices, y)
print('list jitting: ' + str(time.time() - start))

indices = jnp.array(indices)

start = time.time()
f(x, indices, y)
print('array: ' + str(time.time() - start))

f_jit = jit(f)
start = time.time()
f_jit(x, indices, y)
print('array jitting: ' + str(time.time() - start))

results in:
WARNING:absl:No GPU/TPU found, falling back to CPU. (Set TF_CPP_MIN_LOG_LEVEL=0 and rerun for more info.)
list: 0.08577799797058105
list jitting: 9.397922039031982
array: 0.0013730525970458984
array jitting: 0.02692389488220215

Is this a performance bug or should one never use lists as arguments to JAX functions?
macOS, jaxlib: 0.1.60, jax: 0.2.9

Thanks for the report! Agreed this is unexpected. In general, JAX does not automatically convert list inputs to arrays (for example, jnp.min([1, 2, 3]) will return an error). In this case, the idx input is very flexible, as mentioned in the function's documentation:

idx: a Numpy-style index, consisting of None, integers, slice objects, ellipses, ndarrays with integer dtypes, or a tuple of the above.

A list of 3000 indices is compiled to XLA as 3000 separate index objects, rather than a single index object with 3000 elements, and this causes the slowdown.
I think this should probably be considered a bug, and we should raise an informative error rather than silently choosing such a slow code path.

Hi @tetterl

jax.ops.index_add was deprecated in JAX v0.2.22, and removed in JAX v0.3.2.
Instead of jax.ops.index_add(x, (indices,), y), you can use x.at[idx].add(y). where idx is an array of sequence.  For example, you can write x.at[0:len(y)].add(y).
The size of idx must be equal to the length of y.

Please find the gist for reference.
Thank you

This issue still exists:
indices = list(range(1000))
x.at[(indices,)].add(0)  # executes without error, but compiles slowly
x.at[indices].add(0)  # TypeError

Using a list of indices within a tuple should probably fail, because it's a potential performance foot-gun.


Update and now Command failed, why?

Hello,
i update with the latest version and now i have this error:
Command failed: /bin/sh -c node-sass --output-style compressed --indent-type space --indent-width 2 --precision 5 "path_of_my_sass_file" "path_of_my_css_file" /bin/sh: node-sass: command not found.
i don't know why, it's works fine before that.
In my main.sass file i have on first line : // compileCompressed: main.css
echo $PATH: /Users/myname/.rvm/gems/ruby-2.2.2/bin:/Users/myname/.rvm/gems/ruby-2.2.2@global/bin:/Users/myname/.rvm/rubies/ruby-2.2.2/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/git/bin:/opt/ImageMagick/bin:/Users/myname/.rvm/bin
Mac OSX:  v Yosemite 10.10.5
Atom: v 1.0.19
sass-autocompile: v 0.10.3
What i doing now ?
Thank you,
awesome package

Hey!
There was an error in the versions before. First you can try to enter the following command to terminal, restart atom and retry to compile. But I don't think that this will fix your problem.
apm rebuild-module-cache

It's interessting that the node-sass command is not available for Atom, but I think it has to do with an permisson issue, decribed here. What is the output when you enter node-sass in terminal? Try to find out where the node-sass command is places (→ which node-sass) and set the path, where command is placed, to option Path to 'node-sass' command. Does this help you?

 I put the path for node-sass on first line and not in setting panel. I am sorry.
Thank you for reply so fast !

Great to hear that everything works now ;)

apm rebuild-module-cache worked for me.


Please document bracket notation for @item() array

Can you please add to the documentation how to access a property of the @item() array using bracket notation?
This is necessary when you have a lookup activity pulling from an Azure SQL table and a column name has a space in it.  In the ForEach activity, you reference values from particular columns of the table using @item().ColumnName.  However, if a column name has a space in it, then data factory is unable to parse the expression.  e.g. @item().Column Name2
The solution to this is to use bracket notation:
@item()['Column Name2']
However, this is not documented anywhere in the Docs as far as I can tell.
Thank you!

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

ID: 633f2967-1c61-51de-5787-a6ca7ac5bdae
Version Independent ID: d2862926-36d8-4e84-0c93-afdef9e373e2
Content: ForEach activity in Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/control-flow-for-each-activity.md
Service: data-factory
GitHub Login: @djpmsft
Microsoft Alias: daperlov

@jwk6 Thanks for bringing this to our notice. We are investigating into the issue and will update you shortly.

@djpmsft Can you please have a look at this ?
We have a couple of more issues that are related :
https://github.com/MicrosoftDocs/azure-docs/issues/44583

This is a valid ask and I have created a work item to add this to the documentation. ETA is this month. As you have discovered the fix and are unblocked, I will proceed to close this issue
#please-close

Thank you!


Recent changes broke META6

The commit 96b2d1d200ea815d46806499787ca45a16f0b71f (bisected,) appears to have broken the tests for https://github.com/jonathanstowe/META6 - see https://github.com/jonathanstowe/META6/issues/29
Investigating.

Actually the original reported error is caused by bogus test data that was previously ignored (it does need a fix here to improve the failure mode,)  it basically boils down to having an attribute being defined as positional in a class but being presented a Hash in the JSON, this probably wants to be an explicit exception.
However fixing that uncovers:
not ok 1 - create an object from projects.json
# Failed test 'create an object from projects.json'
# at t/040-projects.t line 24
# Type check failed in assignment to $!depends; expected <anon> but got Mu (Mu.new)
not ok 2 - and they're all META6 objects
# Failed test 'and they're all META6 objects'
# at t/040-projects.t line 25
No such method 'depends' for invocant of type 'Any'
  in block  at t/040-projects.t line 27
  in block <unit> at t/040-projects.t line 16

Which basically boils down to it being confused by the anonymous type in:
has             $.depends       is rw is specification(Optional) where Positional|Associative;

It works fine for the positional case, but the associative gets into a mess in the multi _unmarshal(%json, Mu $obj is raw).  Making another more explicit  (%, %) candidate would work but this might not play so nicely with some custom type that implements Associative.

I left a couple of comments to the commit.


intial push to quay

@cooktheryan
Need to sign the commit via something like:
git commit -a --amend -s

for the DCO build to be green. I think that's a "containers" org thing.

@cooktheryan feel free to merge if this is ready :)
Ideally we would build new containers and push to quay on:

every merge to main
nightly

important to note long term we will probably have container images for:

latest-rocm
latest-cuda
latest
stable-rocm
stable-cuda
stable

stable would be built via the "s" branch, nightly and on merge to "s" branch also.

Merging we will fix the above as we proceed

And the "stable" ones probably shouldn't have nightly builds at all I guess... Just in case, but re-build and push on merge to stable yes...


Monitor PV utilization

Monitor PV current utilization and predict the utilization trend
For a production platform, it is important for us to be able to see the current utilization effectively and take active action based on trend.
It will make our monitoring effective if NetApp expose the metrics needed by following dashboard.
https://grafana.com/grafana/dashboards/11454
To take an example,
kubelet_volume_stats_available_bytes
kubelet_volume_stats_used_bytes
kubelet_volume_stats_capacity_bytes

Hi @sfkwan,
We are already working on exposing additional metrics for the Trident 20.07 release.

Multiple commits were made to add this feature with the final commit being fbc91b7.


[Navigation Refactor] - IOS - App crashes when opening a chat with a draft message

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open iOS App and login with any account
Open any chat
Go Offline
Write message but do not send it and return to LHN
Close app, go online and open app again
Open chat with draft message from #4

Expected Result:
Chat opened and draft message is in composer
Actual Result:
App crashes
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[x] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: special build <IP_ADDRESS>
Reproducible in staging?: No
Reproducible in production?: n/a
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://platform.applause.com/services/links/v1/external/eff2faca59625bfa3a3a5c36a6c06a8e656fa224f1f52bae409cd58da784ea56
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

@kbecciv is this not repro on staging?

@mountiny There is issue on staging
https://github.com/Expensify/App/assets/93399543/4b2f3cb8-26fd-4521-a56f-c6e829af2dcb

@mountiny There is issue on staging

@kbecciv based on the video it seems like the app did not crash :D

@mountiny Very sorry, no issue on staging.

Could not reproduce anymore


Some questions about Autofocusing+

I am now reading "Autofocusing+: Noise-Resilient Motion Correction in Magnetic Resonance Imaging", but there are some questions confusing me.
Do you pretrain unet? What's the output of unet?

please refer to diagram and Algorithm 1:
Unet takes IFT of the result of classic Autofocusing (a bad quality image), and maps it to high-quality ground truth. The output of unet (a bit improved quality image) is then used in the next iteration of Autofocusing. So, the optimization of unet weights (training) and the optimization of Autofocusing are performed jointly. No need to pre-train unet.


Event propagation stopped for moves -> rangesliders do not work anymore

I am using rangeslider in the latest version 2.0.2 for my project and it works great all the time.
Now I want to have my web pages swipeable and I use Slick so that I can swipe from one page to another one.
So my setup is that I have some web pages which are swipeable and inside these pages I have some rangesliders (horizontally arranged).
Trying to change the value of the rangeslider by sliding, the web page will start to swipe instead to change the slider position / value. This is because of event propagation and prevents me from changing the slider position / value.
So I tried to stop the event propagation by doing this:
$('.rangeslider').on('touchmove.slick mousemove.slick', function(event) {
    event.stopPropagation();
});

With this source code snippet, I can try to slide the rangeslider and the web page does not start to swipe, which is good, but the position / value of the rangeslider won't change.
The issue is because of the event propagation which I stopped.
In Plugin.prototype.handleDown there are these two lines:
this.$document.on(this.moveEvent, this.handleMove);
this.$document.on(this.endEvent, this.handleEnd);

In my case, I stop the swiping of the web pages with Slick, because I stop the event propagation of the surrounding swipeable web page, but unfortunately I also stop it for the rangesliders, so it will never fire this.handleMove. And inside this function there are the "calculations" / setPositions which will change the value / position of the slider.
So how can I solve this issue? Any help would be really appreciated!

Check this out!
:v:

@andreruffert Really great, but how did you do this and prevent it while sliding the slider, that Slick does not swipe?

@ti-dev just click in the bottom left corner to see the code :)

Thanks for the example of codepen but how does one make slick slider draggable with rangeslider?


Can't resolve path @/utils or @/plugins/envSchema

packages/api stub$ unbuild
packages/api stub: ℹ Building api
packages/api stub: "encrypt" is imported from external module "@wecom/crypto" but never used in "src/routes/root.ts" and "src/services/wechat/crypto.ts".
packages/api stub: ✔ Build succeeded for api
packages/api stub:   dist/app.ts.mjs (size: 15.9 kB, exports: default)
packages/api stub: Σ Total dist size (byte size): 15.9 kB
packages/api stub:  WARN  Build is done with some warnings:
packages/api stub: - Potential implicit dependencies found: @/services/wechat/csh/message, @/services/wechat/wecom/message, @/database/supabase, @/services/EventCallback, @/services/envSchema, @/plugins/plugin-env
packages/api stub: - Potential missing package.json files: app.ts
packages/api stub:  ERROR  Exiting with code (1). You can change this behavior by setting failOnWarn: false .
packages/api stub: Failed

Hi. when I running unbuild command, it goes some error, though, it can use externals and alias fix this issue, but it is unfriendly for users
Have any attrs can fixed it?
export default defineBuildConfig({
  entries: [
    'src/app.ts',
  ],
  clean: true,
  declaration: true,
  externals: [
    '@/utils',
    '@/axios',
    '@/types',
  ],
  alias: {
    '@/utils': path.resolve(__dirname, 'src/utils'),
    '@/axios': path.resolve(__dirname, 'src/axios'),
    '@/types': path.resolve(__dirname, 'src/types'),
  },
  rollup: {
    emitCJS: true,
  },
})

Recommended use @src in tsconfig.json
"paths": {
  "@src/*": ["./src/*"]
}

then, set alias, it can resolve this question
alias: {
  '@src': path.resolve(__dirname, 'src'),
}

But, in stub mode, its get the same error

Having the same issue when using stub mode. Did anyone found a solution?

Aliases for stub mode will be supported in next version (#283)


Unexpected result when I use gulp.dest()

What were you expecting to happen?
Hi, I have a problem with gulp.dest when I use it to double generate.
e.g.
const stream = gulp.src(['./test.txt');
stream.pipe(gulp.dest('./zh'));
stream.pipe(gulp.dest('./en'));

I want to generate Chinese copy and English copy.
What actually happened?
But I only get the English copy.
If I write the code in this way:
gulp.src(['./test.txt');
  .pipe(gulp.dest('./zh'));
  .pipe(gulp.dest('./en'));

it works, I would get the right result, a Chinese copy and a English copy.
Please give us a sample of your gulpfile

Here is github action https://github.com/zhangzhiqiang37/gulp-dest-test/runs/1281077531?check_suite_focus=true
Please provide the following information:

OS & version : MacOS Catalina 10.15.7
node version : 8.11.3
npm version : 5.6.0
gulp version : 4.0.2

That is actually just the behavior of nodejs streams. You can't pipe the result to 2 different outputs and you'd need something like a "tee stream", such as something like https://github.com/streamxorg/teex (I'm not sure if it works on standard node streams).
However, it's not recommended to split a gulp stream and instead apply your transforms inline. You can even filter files after they've been modified or written.
I'm going to convert this to a discussion because it is not really an issue with gulp.


EAI_OVERFLOW: put behind #ifdef

It may not be defined on some systems.
See some other comments in #242
There's a remaining issue that AI_NUMERICSERV from src/udp.c is also not defined. Not sure how to fix that one other than also commenting it out.

Any idea of what system we are talking about here? Also for the case of AI_NUMERICSERV?

Any idea of what system we are talking about here?

More details are in #242.
This broke for me on Mac OS X 10.5, so we patched it locally.

I guess we can add the relevant ifdefs, I don't have a way to test this. Is 10.5 still in use?

I'm not claiming it's the most popular platform around, and I doubt it's used as the main machine anywhere (some do still use 10.6 as their main OS as they didn't like the direction where Apple was heading afterwards), but it's the last OS that works on PPC, so if you don't want to turn a 20 kg Mac Pro into a brick, that's what you are left with. We have some geeks who submitted & merged 7 pull requests for Tiger (10.4) support just in the last three days (which beats me as well, but hey ...)
I can try to test or ask @kencu for help, but it would be helpful to know what specifically to test. My initial main intent was to build the LuaTeX binaries in the first place, and I have no way of knowing whether LuaTeX even uses that part of code.
I tried to run the tests from the package manager now, but I have one tiny issue. We usually run the tests before installing the packages (that's a typical workflow, so that you don't install broken software). Basically we run
make DEBUG=DEBUG macosx LUAV=5.3
make DEBUG=DEBUG LUAV=5.3 DESTDIR=/some/strange/temp/path PREFIX=/opt/local PLAT=macosx install-unix

but then the tests refuse to run since there's no code in place to tell lua to look for the libraries in /some/strange/temp/path. This would be nice to fix (either on your side, or we can fix it on our side if you tell us how).
For the tests on 10.5 we can exceptionally try to first install the library first and then run the tests, the only question is whether the unit tests were supposed to catch potential failures related to missing definitions at hand.

I sympathize.
Testing before installation is possible, but maybe it is easiest to install to a temp directory and point LUA_PATH and LUA_CPATH there?
When I said this needed testing, I meant I can't test to see if it even builds after we make the changes.

Hello. I have lots of these systems, and I'd be happy to work with Mojca to get it building and run the tests.

The AI_NUMERICHOST and AI_NUMERICSERV avoid a potentially slow name resolution for the hostname (which will always be an ip address) and for service name (which will always be an actual port number).  By omitting any of these, the worst thing that can happen is the code becoming slower. Should still work, though. I can't test the impact on speed.
Thanks @kencu. Can you check that else we need in order for LuaSocket to compile properly on whatever version of Mac OS your users need? Then we add a commit to this pull request and solve everything in one go.

Yeah, well good/bad news. The current MacPorts lua-luasocket port installs without any modifications on 10.4 PPC and 10.5 PPC, and all the tests in the test suite pass.
@mojca -- if there is some newer version of the lua-luasockets git commit you were hoping to test, let me know.

Yeah, well good/bad news. The current MacPorts lua-luasocket port installs without any modifications on 10.4 PPC and 10.5 PPC

You mean: after you apply these patches, right?
https://github.com/macports/macports-ports/tree/master/devel/lua-luasocket/files

Ah. I didn't notice that the port was already patched in Macports, but certainly it is. Yes, with the current Macports' patches, it builds and tests properly on 10.4 & 10.5.

I have shamelessly stolen the other patch from MacPorts (I probably never payed attention to our existing patches).
@kencu: you say that you have the tests working. Can you please modify the port, so that port test will work automatically? I was probably missing some variable to point to the location of files before being installed.
Question to the authors: is there any plan to get a new official release out at some point? TeX Live release cycle is now quickly approaching. If a new release of luasocket gets out soon, we could still include it.

@mojca: We are trying to close as many of the outstanding issues as possible.
@kencu: Thanks. So I will merge here.

@kencu: I have another unrelated question. Lately, the
export MACOSX_DEPLOYMENT_TARGET="10.3"

began causing issuing a warning on recent versions of Mac OS X. Can I simply remove it from the makefile?

Yes. By default, all macOS build systems I know of set the deployment target to the system they are building on, which is appropriate 99% of the time.
Someone who wants to do something fancy like deploy on an older system than the build system will need to know what they are doing, so would not get caught by this, IMHO.

export MACOSX_DEPLOYMENT_TARGET="10.3"

began issuing a warning on recent versions of Mac OS X. Can I simply remove it from the makefile?

Absolutely, for at least two reasons:

You don't need this set at all, unless you want to build binaries yourself, targeting Mac OS X 10.3. You don't want that.
10.3 is totally obsolete. Trying to install a decent compiler is a nightmare and the set of functions available out of the box doesn't suffice to build anything reasonable.
(I didn't notice this one.)

And many many thanks for the fix.

Question to the authors: is there any plan to get a new official release out at some point? TeX Live release cycle is now quickly approaching. If a new release of luasocket gets out soon, we could still include it.

We are working for it. How soon are you looking at?

Here's the timeline: https://www.tug.org/texlive/
The 22nd February was officially the deadline to commit "simply anything", the sources were supposed to be ready by now, but the binaries were supposed to be committed by the 1st of March. The 22nd March is the final freeze. The sooner the freeze date, the less likely the changes are to be accepted.
But don't worry about this.

Give us a ping when the deadline is closer. We can, at least, tag a version, right? It won't be worse than the current situation. :)


[TASK] Update when to where in walkthrough docs

Description
Just a small doc correction. Closes #1658
Related Issue
Fixes #1658

Relates to #1658
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Other (security config, docs update, etc)

Checklist before merging

[x] Test, docs, adr added or updated as needed
[x] Contributor Guide Steps followed

Looks good to me but there are merge conflicts due to some walkthrough updates that went out today - that error is still on the now helm-oci deployment walkthrough though. And thanks for the PR!

My fault, you are right! Just rebased. My pleasure!


Panic building on Windows running: "rm" "-rf" ".termbox" (file not found)

I experienced a panic when building termbox-sys on Windows as a dependency of the rex crate.
The output looked like this:
error: failed to run custom build command for `termbox-sys v0.2.12`

Caused by:
  process didn't exit successfully: `C:\Users\build\AppData\Local\Temp\cargo-installKElqYD\release\build\termbox-sys-2c803b9c27aec6fd\build-script-build` (exit code: 101)
  --- stdout
  running: "rm" "-rf" ".termbox"

  --- stderr
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "The system cannot find the file specified." }', C:\Users\build\.cargo\registry\src\github.com-1ecc6299db9ec823\termbox-sys-0.2.12\build.rs:94:18
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: failed to compile `rex v0.1.0`, intermediate artifacts can be found at `C:\Users\build\AppData\Local\Temp\cargo-installKElqYD`

Caused by:
  build failed

Same with me:
error: failed to run custom build command for `termbox-sys v0.2.12`

Caused by:
  process didn't exit successfully: `C:\Users\nsdjs\Documents\Programming\Rust\hackertype\target\debug\build\termbox-sys-2f9b5f7709c33c52\build-script-build` (exit code: 101)
  --- stdout
  running: "rm" "-rf" ".termbox"

  --- stderr
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "The system cannot find the file specified." }', C:\Users\nsdjs\.cargo\registry\src\github.com-1ecc6299db9ec823\termbox-sys-0.2.12\build.rs:94:18
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
warning: build failed, waiting for other jobs to finish...
error: build failed

same with me:
error: failed to run custom build command for `termbox-sys v0.2.12`
Caused by:
  process didn't exit successfully: `E:\RustProject\iota\target\debug\build\termbox-sys-27c2e71ca970c78d\build-script-build` (exit code: 101)
  --- stdout
  running: "rm" "-rf" ".termbox"
  --- stderr
  thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 2, kind: NotFound, message: "系统找不到指定的文件。" }',

wanna know how to solve this, 😢


Addition of personal content & resources

Additional support for:

WHEN I click on the images of the applications
THEN I am taken to that deployed application

And to fulfill a more personalized response to:

If you don't have enough web applications to showcase at this point, use placeholder images and names. You can change them to real applications as you create them later in the course.

Resolved under PR #19


React ^0.12.x dependency clashes with v0.13.x

Please could you update your React dependency version as it is causing install errors.
They are caused by the special behaviour of using the caret syntax with version numbers < v1.0.0
FYI: https://github.com/npm/node-semver/blob/master/README.md#caret-ranges-123-025-004
Thanks!

@pedronauck Perfect! Thanks.


Make it explicit that Staticman doesn't work with anything other than GitHub

I recently moved from GitHub Pages to GitLab pages because GH doesn't support HTTPS for custom domains. Unfortunately, I lost all comments in the process because Staticman doesn't (yet) support GL (https://github.com/eduardoboucas/staticman/issues/22). If this had been made explicit in the docs, I'd not have chosen them to begin with. I'm now using Disqus as the comment provider. The same problem would occur for any kind of hosting solutions (which I was seriously considering before finding GL Pages).

Staticman now supports Gitlab Pages in principle.  See eduardoboucas/staticman#219.


Import from game slot offset by 1

Tried this plugin today and it seems like the imported waypoints get offset by 1
If I import slot 1 it ends up at 2, slot 2 at 3 etc etc, not sure if you just need a -1 or +1 somewhere, I see some -1 added in the code but not sure if that's it.
https://github.com/Infiziert90/WaymarkPresetPlugin/commit/8dd147c27d146a3686ba2d8363518ced2c131222#diff-66a2489a0da06a2aad9496ec565256feff18c04bfce84d21bbfedf1f711db05dL262

Seems to have fixed itself with dalamud updates.


Fix large _.template memory consumption

Problem: In order to support accepting a function for options.msg,
express-winston is calling _.template for every request.  This compiles
a brand new lodash template every request.  Under heavy load, this has
significant performance and memory usage implications.
Solution: During initialization, make the decision on whether to use
a single cached template or a dynamic function that compiles a template
for each request.  This way, we get the efficiency of a precompiled
template for the more common use cases, while remaining backwards
compatible with published features.
In a future version, it might be worth considering dropping support
for mustache formatting and just have express-winston consumers always
provide a function if they want a custom options.msg.  The api consumer
can use JS template literals if they need templating in their custom
message.

❤ Would you like to add yourself to AUTHORS?

Sick, thanks

@slickmb Released in<EMAIL_ADDRESS>


Fixed the edge case where kind-kind cluster are still being created a…

…s kind-kind-kind context

/lgtm
/approve


add knowledge base

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

adding knowledge base lab code


Button letter-spacing never made it to production?

Is your feature request related to a problem? Please describe.
While working on a button, I wanted to add letter-spacing to it. As a developer I checked GitHub first and I saw that had a PR for it already merged. When I tried to use it is not there yet, but looking at the commits it is right after the v4.5.1 release. So wasn't it deployed after all?
Describe the solution you'd like
A new release would be nice.
Describe alternatives you've considered
Forking everything and make it my own.
Additional context

Looks like we had it merge on master and push next branch instead 🤔
We have a small update on column gutter that should be pushed soon to npm so it should come with it

@iRyusa close this issue when this is release, will ya?

hummm i still cant use letter spacing...
what happened?

any work arounds for this?

seems that it works lol.. only the try-it-live page complains about it

You can check the try it live version right after the logo :) it's still not updated yet

It is also not listed in the docs yet: https://mjml.io/documentation/#mjml-button

Try it live isn't yet updated to 4.6, so as the doc we'll try to update it soon

Any updates on this? I got the same issue

It works just fine https://mjml.io/try-it-live/BJRPJGfLP  ¯\(ツ)/¯

It works just fine https://mjml.io/try-it-live/BJRPJGfLP ¯_(ツ)_/¯

Damn I’m stupid, I was using an older version of the mjml vscode plugin that was still running on mjml 4.2 🤦♂


Saving K_TUNNEL and K_BRIDGE edge flags #713

This PR saves tunnel:yes and bridge:yes in two additional generic flags (just like K_ROUNDABOUT).
The drawback is that since these are generic flags, they are currently duplicated among all the flag encoders. As a result, users will need 64-bit edge flags in most cases (2+ encoders).

Thanks, will investigate. Related to #713


Remove all NLP typing

We're getting module 'spacy.lang' has no attribute 'en' errors. There's probably a reasonable way of doing this but let's not right now.

It appears to be working?


the init_cleanup in uperf test is a relic

https://github.com/cloud-bulldozer/e2e-benchmarking/blob/de3a11a0f99a58af8f7275bc8de509063e9769e9/workloads/network-perf/common.sh#L235-L242
we need to use make undeploy

Some WIP here to handle benchmark-operator from a common wrapper. https://github.com/cloud-bulldozer/e2e-benchmarking/pull/249


Add Support for low-latency Dxgi-swapchain based presentation model

What does the pull request do?
This pull requests adds support for presentation via an ID3D11 Swapchain. This is yet another option that can be added to the ways Avalonia can be presented to the screen in Windows.
This swapchain uses IDXGIOutput to query and directly wait for VBlanks from the operating system, letting one consistently hit higher refresh-rates than one can without using the Windows Composition.
The Render Timer is hooking onto the Display itself and operates fine no matter how many windows are open.
Should support Windows 8.1 and above (Though I have no Win8.1 machine to test on).
When in fullscreen mode, the swapchain enters into DirectFlip where the front-buffer gets sent to the display-device directly, saving yet more resources as desktop composition does not need to be done for that display. This cannot occur using the Composition API.
This presentation style is suitable for kiosk applications on Windows and for realtime applications that want a more performant present cycle.
The interactivity feeling can be felt/measured by the addition of a new page on the Control catalogue demonstrating the use of the Avalonian Drawing Context to draw content with several transforms added and shown. This control shows a smiling sun with ten smaller planets orbiting the sun. The control can be panned using the pointer by pressing and dragging, and the page has controls for zooming in and out and rotating the viewport. The zoom can also be done through the mouse wheel.
Disadvantages:

Resizing the window results in wobbling as the chain resizing (render cycle) is occurring asynchronously to the windows message-pump. This doesn't happen in the Composition presenter. This is similar to using wGL or the legacy ANGLE swapchain.
Does not support Acrylic Blur etc. that the Composition presenter does.

What is the updated/expected behavior with this PR?
Adds new opt-in Win32Option that if turned on and Windows Composition is turned off, uses a D3D11 Swapchain to present the ANGLE contents to the screen. This is specifically opt-in so as to cause as little disruption as possible.
How was the solution implemented (if it's not obvious)?
Minimalistic IDXGI references were added in several structs used to represent the native pointers.
Raw pointers and unsafe code were used to stich the presenter and swapchain together.
This was initially started as a test to see if it could get issue 8293 to reproduce. It does not.
The new DXGI classes and interfaces are all placed in a new folder in the Win32 project, so they can be kept isolated and out of the way of the rest of the classes.
Perhaps further DXGI integration can be offered later, such as AvaloniaUI being used as the UI-layer for a D3D11 game? (Might be hard to cross a C#-C++ boundary, as most D3D11 games are in C++)
Checklist

[ ] Added unit tests (if possible)?
not sure how to write unit-tests for DXGI interfaces
[x] Added XML documentation to any related classes?
XML docs added to Win32 Options
[ ] Consider submitting a PR to https://github.com/AvaloniaUI/Documentation with user documentation

Breaking changes
There should be no breaking changes. This has been tested on the Control Catalogue with the new control addition to encourage Avalonia to "Draw more". This feature is opt-in, everything appears to work normally without it.
Obsoletions / Deprecations
Nonapplicable.
Fixed issues

N/A

You can test this PR using the following package version. 11.0.999-cibuild0026722-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0026727-beta. (feed url: https://nuget.avaloniaui.net/repository/avalonia-all/index.json) [PRBUILDID]

You can test this PR using the following package version. 11.0.999-cibuild0026792-beta. (feed url: https://pkgs.dev.azure.com/AvaloniaUI/AvaloniaUI/_packaging/avalonia-nightly/nuget/v3/index.json) [PRBUILDID]


[Ressources] Water technology of uncharted GDC 2012

https://www.slideshare.net/agebreak/water-technologyofunchartedgdc2012
As I've see discussion on FFT layer, underwater detection and others things, this can be interesting if not already seen!

Actually I'll link this from #85 and focus conversation there if thats cool


Move include directory

As requested on discord, this these commits were taken from the Splash PR and moved into a new one.

How to test: try to compile the solution with this PR. If it succeeds, it means its working

I assume I can merge this now, @pg9182?

Looks okay to me, but I haven't ran it.

looks fine to me, will build and run in a bit to make sure


add option --disable-reporting  to the command line via charm configuration switch

Enhancement Proposal
Currently grafana-agent (as well as grafana) calls home (sends anonymous usage statistics) to stats.grafana.org
Our customer does not want any application to call home and beyond that it puts significant load on their firewall while blocked it opens a lot ports for each of the LXD container, VMs and baremetal being part of Charmed Openstack solution (over 200).
More details available here:
https://grafana.com/docs/alloy/latest/data-collection/
So essentially the charm should have option to --disable-reporting to the command line.
Marking it as field-critical as it required for the closing deployment in 2 weeks.

Duplicates #40.
Thanks for surfacing this. We'll prioritize this.


Add: Forte's wiki_parser example

This PR introduces the following additions/changes:

Adds the wiki_parser example which runs on the Argo backend.
Enhancements to the docker image generation.
Minor bug fixes in the dockerize module.

Closes #20

@zhanyuanucb

I saw there are many downloaded files. Can we remove them from the repo? Providing the script and instructions to download those files should be enough.

Those files are present in the forte repository. Downloading instructions might not be very straightforward as these files are derived from the larger files for which the download instructions are already provided.

Put forte_example under examples so that all examples are together.

I changed the directory structure a bit. Please take a look and let me know if this looks fine to you.


Publicize _calculate_zoom

I think that contextily.tile._calculate_zoom should be part of a public API. It is useful if you want to fine-tune zoom levels, to know which one you start from. And it is also part of the intro guide. https://contextily.readthedocs.io/en/latest/intro_guide.html#Fine-tune-zoom-levels

+1 to make this easier in some way.
For me a potential downside of calculate zoom is that it requires (w, s, e, n)(but we could also improve the interface of course, eg accepting a geodataframe in different crs).
Another idea that I had at some point would be to add a verbose=True option to add_basemap (and other similar functions), which would eg print which zoom level is being used, so it's easier to set it slightly larger/smaller. Of course, that can only be used interactively, as it's not a function.

+1 Also, related, I've been using the new overlay feature and I find consistently that I end up going for the default value of zoom - 1 (one more zoomed out). Is this something you run into as well? If so, maybe we could change the 'auto' algorithm to have that as default?

I find consistently that I end up going for the default value of zoom - 1 (one more zoomed out). Is this something you run into as well?

I was changing the zoom level for overlay labels in about 50% of cases.


Convnextv2 outputs nan when training in fp16

tiny version

Actually have it nan also in fp32 after 100-200 steps. But in fp16 it's from the first step

Haven't tested it myself, may try it later, but tested v1. May set use_grn=False when creating the model, that's the different block from v1. Not sure if that's the reason.

Works fine with use_grn=False

I've finished training 105 epochs using ConvNeXtV2Tiny + cifar10 + adam.
CUDA_VISIBLE_DEVICES=1 python train_script.py -m convnext.ConvNeXtV2Tiny -dcifar10 -p adam -b 32 \
--lr_warmup 1e-6 --lr_base_512 1e-3

Have to use --lr_base_512 1e-3 here, also run into NaN when using default --lr_base_512 8e-3 on epoch 4, 2 times. I think it's something related with learning_rate / weight_decay / optimizer. May try a smaller learning_rate in your case also.
May not an issue but could also try setting 1e-6 to 1e-5 in convnext.py#L66.

btw trying to run 384x384 version warmup_learning_rate: 1.0e-5 and get nan from first step.
Tried with clipnorm=1.0 also no effect.
Tried with warmup 1e-6 no effect
Tried the change in the src you proposed, no effect.

I can replicate it now. My previously running is not using the pretrained weights.
I think this is a bug for tensorflow tf.norm function, and not happens for pytorch. There is some related issues like Numerical instability of gradient calculation of tf.norm (nan at 0, inf for small values) #12071. I think they should have fixed it, and I've tried those methods metioned there, but still got<EMAIL_ADDRESS>def custom_norm(x, axis=[1, 2], keepdims=True):
   # y = tf.norm(x, ord='euclidean', keepdims=keepdims, axis=axis)
   y = tf.sqrt(tf.reduce_sum(tf.square(x), axis=axis, keepdims=True))
   def grad(dy):
       return dy * (x / tf.maximum(y, 1e-7))
       # return dy * x / (y + 1e-7)
   return y, grad

I've made a work around using mean instead of sum calculating norm as shown in above check-in. Just works in my tests with cifar10.

Cool, thanks


Fix issue #796 : Toggle switch appearance

Issues Identification
Closes: #796
Description
Summary
A brief description of what this pull request does and why it is needed.
This pr is needed because before toggle switch appeared same on dark mode as well as light mode, but after this pr toggle switch will appear according to the website theme.
Details
Include any detailed information about the changes in this pull request.
Types of Changes
Please check the boxes that apply

[x] Bugfix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[ ] Other (please describe):

Checklist
Please check the boxes that apply

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] My changes do not break the current system and pass all existing test cases
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Screenshots
If applicable, please attach screenshots of the changes made to the user interface.
https://github.com/user-attachments/assets/a5e7efb1-d2f3-4129-b9bf-6c91e5ed3208
Additional Information
Please provide any other information that is relevant to this pull request.

@Adityadhiman0 hey, while  I was checking the preview, i can see the toggle ones only in home page, i can't see this in remaining pages.
Can you check the deploy preview and update it in all pages.

Good Work @Adityadhiman0.
Done.

Should I create a new pr. Please help me.

Thank you very much.

No need @Adityadhiman0.
your work is done.

Anyways Good work @Adityadhiman0.
Wishing you all the best and keep contributing to open source.


Uncaught AttributeError in sendchat.py line 30

Aider version: 0.56.0
Python version: 3.10.12
Platform: macOS-13.3.1-x86_64-i386-64bit
Python implementation: CPython
Virtual environment: No
OS: Darwin 22.4.0 (64bit)
Git version: git version 2.33.0
An uncaught exception occurred:
Traceback (most recent call last):
  File "aider", line 8, in <module>
    sys.exit(main())
  File "main.py", line 698, in main
    return 1
  File "base_coder.py", line 735, in run
    return self.io.get_input(
  File "base_coder.py", line 778, in run_one
    def check_for_urls(self, inp):
  File "base_coder.py", line 1202, in send_message
  File "base_coder.py", line 1885, in auto_commit
    self.io.tool_error(f"Unable to commit: {str(err)}")
  File "repo.py", line 102, in commit
    commit_message = self.get_commit_message(diffs, context)
  File "repo.py", line 187, in get_commit_message
    commit_message = simple_send_with_retries(
  File "sendchat.py", line 38, in wrapper
    retry_exceptions(),
  File "sendchat.py", line 30, in retry_exceptions
    litellm.llms.anthropic.chat.AnthropicError,
AttributeError: module 'litellm.llms.anthropic' has no attribute 'AnthropicError'

Thanks for trying aider and filing this issue.
This looks like a duplicate of #1278. Please see the comments there for more information, and feel free to continue the discussion within that issue.
I'm going to close this issue for now. But please let me know if you think this is actually a distinct issue and I will reopen this issue.


[Bug] When add the slider to the heat map the data will overlap

Version
5.3.2
Link to Minimal Reproduction
No response
Steps to Reproduce
If the slider is removed, this issue will not occur.
Add sliders in X axis and Y axis for heat map
Current Behavior
After the sliders is added to the heat map, some data overlap.

Expected Behavior
Adding the slider, the data will not overlap
Environment
- Windows 10
- Browser: Chrome 106.0.5249.119 (Official Build) (64-bit)
- Framework: Angular14

Any additional comments?
No response

https://codesandbox.io/s/infallible-snowflake-8krt0n?file=/src/index.js

@sarlemon Please provide a demo for the issue either with Official Editor, CodePen, CodeSandbox or JSFiddle.

https://codesandbox.io/s/infallible-snowflake-8krt0n?file=/src/index.js


Added get-free-social-traffic.com and sexyali.com to the filters

what about chinese-amezon.com?

@moakdesigns I added those 2 aswell to the pull request :-)


Added search of Skaffold files across the project space.

Fixes #37.
Implements recursive search of all Skaffold configuration files across the base project directory, skipping the excluded directories (i.e. build outputs etc.)
Unit tests are coming in the follow up PR - it will also need some initial test infrastructure to test virtual files and project.

@tiembo quick glance at Kotlin in general here is appreciated!

Also just a general question:
I think you hinted that the idea here is that the Skaffold run config would show a dropdown listing all of the available skaffold.yaml files.
At the same time, we plan to also have detection of skaffold.yaml files and autocreate the run configurations -> presumably it would then default the dropdown to the given skaffold.yaml. So I guess the idea is that a single run configuration is not tied to a specific skaffold.yaml and that a user can change it on the fly (instead of creating a new run config tied to a different skaffold.yaml).
I think this makes sense, just making sure I understand the approach.

@etanshaul on your general question, correct, it feels run configurations naturally allow changing their Skaffold configuration file. Auto-creating run configs for Skaffold files will help with that, but it doesn't make sense to "hard code" one Skaffold file per run configuration.

cool. that makes sense to me. some users may prefer having a single run configuration and jsut changing its context rather than having many.

Kotlin reviewers are at KotlinConf, and this is a small PR, so it looks as good to go.

Feel free to merge, but we can revisit the question I had about extension functions and refactor later if needed


Font object creation should not be based on marginbox

This issue completes a portion of #58

this is an old article about the ability to access font information for data pulled:
https://stackoverflow.com/questions/47767576/python-docx-access-to-paragraph-font-size

perhaps a more recent addition
https://stackoverflow.com/questions/74634807/python-docx-font-size-pt-not-defined

these kind of things can actually be done using python-docx styles
https://stackoverflow.com/questions/75601802/get-default-font-size-of-an-empty-document-in-python-docx
It looks like we can utilize the following to get the different styles for the paragraphs.
for paragraph in doc.paragraphs:

    style = paragraph.style

    if style != None:
        log(f'Style:{style.name}, font name:{style.font.name}, font size:{style.font.size}')

note:

the font size needs to be converted to readable '10, 12, etc'
also need to figure out how to utilize styles to help print out the information onto the template page
style that are None are a specific type of line that needs to be dealt with intentionally

https://python-docx.readthedocs.io/en/latest/user/styles-using.html
https://python-docx.readthedocs.io/en/latest/api/text.html
https://python-docx.readthedocs.io/en/latest/api/style.html#docx.styles.style._ParagraphStyle

Maybe should consider rebuilding the entire way styling is made in the script for this issue rather than focusing primarily on the font object.

Ultimately the issue described is completed, but more needs to be done. I will close this issue, and make more focusing on styling and structure of the code just added.


Added the ability to provide multi-paragraph descriptions.

Whilst writing a tool with GLI I found that you couldn't specify a description with paragraphs as the code to ensure wrapping compliance was stripping them out. This is particularly useful for long descriptions so I thought it would be worth adding.
This pull request adds the ability to specify paragraphs within your help text and have it maintained during the wrapping compliance. It follows the formatting rules you see in wiki and markdown syntax of there having to be at least one blank line between paragraphs so it should be non-breaking for existing text.
Two paragraphs
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi ultrices eros in orci auctor ut tincidunt magna auctor. Nam interdum pretium egestas.

Donec ipsum massa, mollis non laoreet tincidunt, consectetur id odio. Fusce a neque ligula, nec consectetur erat. Sed aliquam felis in orci pulvinar nec imperdiet magna feugiat.

Still two paragraphs
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi ultrices eros in orci auctor ut tincidunt magna auctor. Nam interdum pretium egestas.

Donec ipsum massa, mollis non laoreet tincidunt, consectetur id odio. Fusce a neque ligula, nec consectetur erat. Sed aliquam felis in orci pulvinar nec imperdiet magna feugiat.

One paragraph
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Morbi ultrices eros in orci auctor ut tincidunt magna auctor. Nam interdum pretium egestas.
Donec ipsum massa, mollis non laoreet tincidunt, consectetur id odio. Fusce a neque ligula, nec consectetur erat. Sed aliquam felis in orci pulvinar nec imperdiet magna feugiat.

If any changes need to be made then let me know.

I'll look at this in the next couple days, but seems like a good change


duration value is showing buffered's value in useProgress hook

Describe the Bug
The duration value is showing a buffered value of useProgress hook [may be only in network audio]. For example, the actual audio file duration is 5 minutes but it only shows the buffered value. sometimes even position is showing a bigger value than both of duration and buffered value, like position is already at 3 seconds and playing audio smoothly but the duration and buffered value is at 2 seconds. it only happens a few seconds of the beginning of the audio.
Code To Reproduce
const {position,buffered,duration} = useProgress();

console.log(position,buffered,duration);
/**
 duration always shows buffered value,
e.g.,
 position:12
 buffered:
*/

Environment Info:
System:
OS: macOS 11.4
CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
Memory: 156.66 MB / 8.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 14.17.0 - /usr/local/bin/node
Yarn: Not Found
npm: 6.14.13 - /usr/local/bin/npm
Watchman: 2<IP_ADDRESS> - /usr/local/bin/watchman
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4
Android SDK:
API Levels: 27, 28, 29, 30, 31
Build Tools: 29.0.2, 30.0.3, 31.0.0
System Images: android-29 | Intel x86 Atom, android-29 | Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom
Android NDK: Not Found
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7784292
Xcode: 12.5.1/12E507 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_282 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.2 => 0.64.2
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
react-native-track-player version ^2.1.3
Simulator
MacOs

Having the same issue on Android from commit 9b7d663
Any fix?

Same here on iOS Simulator.

Looking through source code related to this, I see the following which might be causing this bug:
https://github.com/doublesymmetry/SwiftAudioEx/blob/main/SwiftAudioEx/Classes/Observer/AVPlayerItemObserver.swift#L92-L95
        case AVPlayerItemKeyPath.duration:
            if let duration = change?[.newKey] as? CMTime {
                delegate?.item(didUpdateDuration: duration.seconds)
            }

        case AVPlayerItemKeyPath.loadedTimeRanges:
            if let ranges = change?[.newKey] as? [NSValue], let duration = ranges.first?.timeRangeValue.duration {
                delegate?.item(didUpdateDuration: duration.seconds)
            }

The second case seems to be updating the duration from the loadedTimeRanges, which looks to be the playable duration – which is a different thing.

loadedTimeRanges
An array of time ranges indicating media data that is readily available.
https://developer.apple.com/documentation/avfoundation/avplayeritem/1389953-loadedtimeranges

This code was introduced in this commit: https://github.com/doublesymmetry/SwiftAudioEx/commit/9072259631b03397c942fc3f00fe20d5e87775ce

I am unable to reproduce this bug in the example app – @kyimoemin do you have an example of an mp3 file where this is occurring?

Or perhaps @luco, @newfylox?

I actually think this issue is a dupe of https://github.com/doublesymmetry/react-native-track-player/issues/1521 and has been fixed.

@luco @newfylox @kyimoemin , please confirm or deny @puckey 's suspicion that this has been fixed. If we don't hear anything back to the contrary we're going to call this fixed.

Sorry for the late response, it works fine in the android simulator now, but the duration is always '0' in the iOS simulator.

@kyimoemin what kind of track are you using? Is it a live stream?

not live stream, normal mp3 audio file. it works in android so the bug may remain only in iOS

@kyimoemin could you open a fresh issue for the duration of 0 for iOS?
Thanks!

@jspizziri will do, thanks

Sorry for late reply, I can't confirm because we stopped the project in which I was working in.


Update Enterprise Kyverno link

Update the docs link for Enterprise Kyverno Release Compatibility Info
Related issue
The current docs link is broken for Enterprise Kyverno's Release Compatibility Matrix.

Proposed Changes
This PR fixes the broken link.

Checklist

[] I have read the contributing guidelines.
[] I have inspected the website preview for accuracy.
[] I have signed off my issue.

https://docs.nirmata.io/n4k/release-compatibility-matrix/ throws a page not found error.

@chipzoller I just got that merged on the Nirmata website. I should have marked this as draft until then. Can you please check now?


CORE-3262 fix: FileSystemResourceAccessor fails with non-hierarchical…

… URLs on class path
Multi-release Jars on the classpath caused a java.lang.IllegalArgumentException "URI is not hierarchical" in FileSystemResourceAccessor::addRootPath()

Any chance of this being merged? we can't upgrade JDK without this.

Merged in, thanks. Was this an issue you saw in 3.6 as well? Or just in master?

[FYI] We faced with it in version 3.6

[FYI] I was able to reproduce the issue in versions 3.5.5, 3.6.1 and master.

Thanks for merging. When is release planned including this change? a 3.6.x hotfix would be enough probably...

This fix is part of Liquibase Release 3.6.3.


Xcode marked build as failure in jenkins

I use Git to get the source code, and i build it with xcode but when i run the build is fail
ps: my .xcodeproj is located in workspace(platforms(ios(app.xcodeproj)))
This is part of the console in jenkins:
[workspace] $ /usr/bin/xcodebuild -list
xcodebuild: error: The directory /Users/user/.jenkins/jobs/testArt/workspace
does not contain an Xcode project or workspace.
Build step 'Xcode' marked build as failure
Finished: FAILURE

Hi,
It's not clear whether the problem you are reporting is related to the installation of jenkins using the chef cookbook, or just a jenkins failure where you are using xcode. Can you provide additional information about your environment?

@hajarbabour
If you are still requiring help with this issue, please reopen with additional information. Thanks.


TestCluster: Add attribute resets during Test cmd.

Problem
The test assumes that we start with the default values, which means
the test will fail the second time around. This fixes that.
Fixes #13434
Fixes #13435
Change overview
Adds an attribute reset to the Test command that is run at the start of the test.
Testing
Ran TestCluster tests using chip-tool 2x on linux and M5.

fast track: small delta, test code, lots of checkmarks, sufficient time for cross  timezone review passed.


I19-admin

Fixes #19

adds some cypress e2e tests, including authentication
refactors all the api calls to hooks (for GET) and actions (for PUT, POST) that return promises
sets up a context for global state (just activeEvent for now)
adds admin flag for Users, admins only can create / edit events and eventgroups/items, and change enrolement requests

I'll wait for @fcooper8472 's course to finish before I merge this 😄


Polish bot client

The csharp client needs a bit more polish and documentation.
Goals:

anyone can checkout the code and run it in seconds.
framework code should be hidden, there should be a trivial example that runs out of the box
modifying the code to become more intelligent should be easy (e.g. by following comments in the code)

I updated the client code a bit... try the following:
$ dotnet run
$ dotnet run  -- --help
$ dotnet run ask --help
$ dotnet run join --help
$ dotnet run start --help


Incorrect Javadoc in AbstractSerialisation

The Javadoc in AbstractSerialisation says that it provides a default implementation of  Serialisation#deserialiseEmptyBytes() - it doesn't.

Merged into develop.


client-side load balance multiple MarkLogic hosts

is there any way I can pass multiple hosts when I create new client, to client-side load balance between multiple MarkLogic hosts?
newClient(host, port, username, password, authentication)

Not for general operations.  If it did, there would of course be some things to consider: it would reduce the benefits of server-side caching, you'd need to keep any transactions on a single host, and you'd need to only talk to e-nodes (hosts with the REST server configured).  Nevertheless, MarkLogic Server is very efficient at server-side load-balancing even when all requests go to one host.  And the benefits of caching can be maximized that way.
With that said, it can make sense to push that load-balancing out further for data movement (ETL) scenarios.  That's why we developed the data movement SDK which does the client-side load distribution for you.  It not only distributes writes across the cluster, but for queries it pulls each batch from a single forest then targets follow-up calls (such as export, transform, or delete) to the host responsible for that forest.

Thanks @sammefford  for the information on Data Movement API. I will explore it.
My usecase is to ingest  ~200M  300k size json files into 3 mid size marklogic nodes.
With java-client-api and Apache Spark (which should be running on multiple client nodes)  I am getting 1500 TPS.   I am using WriteSet for 50. looking for advice on improving MarkLogic write performance.

Those are some very large files!  What do you mean by TPS?  If that's docs/sec, then that seems like a good number given the size of your files.  Are you able to share your code?
It's hard to give tuning advice, knowing so little about your setup.  The WriteSet size of 50 might be ideal, but it just takes trial and error on different batch sizes to know what's best for your content.  When testing docs of size 10K we saw batch size of 500 was faster than batch size of 100.
Also, have you looked at mlcp?  It's a command-line tool.  For MarkLogic 8 that's the best way to load lots of files if your use case supports it.

@xmlking are you still looking for help with this?  If not, I'll close.

No. Thanks.


Extract the information about operating systems outside AwsOperator for better testing

Originally reported by: Yung-Yu Chen (BitBucket: yungyuc, GitHub: yungyuc)

Bitbucket: https://bitbucket.org/solvcon/solvcon/issue/97

Close for the work may be addressed with #131


Book Store: components

Here:

I setaped a new React application using Create React App
I created a directory for your reusable components: /components.
I Installed React Router V6
I added 2 routes in your application, each should render a page.
I created components inside of the /components directory:

Contains individual book state, as well as a button to delete the book
Contains a list to renders individual books
Contains a form to create new books

Now it looks like this:

4. Contains a navigation to link to the 2 routes you created

Hi @najibullahjafari,
While you made a great effort in this project, unfortunately, I cannot proceed to review your code.
Invalid Code Review Request
You have submitted a project, that is invalid because linters are not properly set up for the project
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


[RFC] Doc generation

discuss!

What kind of generation? You mean generating docs from source, or using something like restructured text?
IMO this package isn't complex enough to warrant anything beyond a readme. Most simple node modules nowadays use the readme for such documentation.

This is a rather old ticket and I'm simply trying to do some housekeeping, so please feel free to close this if it's no longer pertinent (especially since v3 is out already).

Closing since the API of debug has been pretty much exactly the same since the 0.x releases 😅


Adds the media plugin to TinyMCE to allow insertion of videos.

Fixes #266
Signed-off-by: Abijeet<EMAIL_ADDRESS>
I've had to add an ugly hacky fix to remove the "Advanced" tab and the "Open" button,
https://github.com/BookStackApp/BookStack/commit/6f280bb4884b2d693d89e84e69b94f274b9747f3#diff-4fd06e033e83fb244f4d8c9752a26781R315
Otherwise this is how the default media dialog looks like with the open button not really doing anything.

@ssddanbrown  - Thanks for the quick review. I did try that, but the advanced tab was still visible. As per the changelog this was fixed in TinyMCE Version 4.7.7 released on February 19, 2018.
Search for -

fixed a bug where the advanced tab in the Media Plugin was being shown even if it didn't contain anything. Patch contributed by gabrieeel.

We are using version 4.6.6 (2017-08-30).
Maybe its time to upgrade?

@Abijeet ah, Makes sense. Yeah, Upgrading is probably a good idea, Think it's been a few releases since last TinyMCE upgrade.

@Abijeet Sorry but I've just made this a little more difficult to merge after pushing 736d7118b08ef7f03d35a237bf5a909ada90d9cd up.
Will need to move the resources/assets/js/pages/page-form.js changes to resources/assets/js/components/wysiwyg-editor.js.

@ssddanbrown - No problem, will take care of it this weekend.

rip

@ssddanbrown - Done!

@Abijeet Awesome, Thanks!


WIP: fix build with OpenSSL 3

update_engine has historically used the low-level OpenSSL hashing and RSA signature APIs, which have been deprecated in version 3. This PR migrates to the higher-level EVP APIs.
Testing done
Unit tests don't pass. PayloadSigner isn't returning the expected test vector. We may be using the wrong API for decrypting the RSA signature.

CI is running against ubuntu-latest which appears to not have OpenSSL 3 (and some of the EVP functions we need here are not present in earlier versions).

CI is running against ubuntu-latest which appears to not have OpenSSL 3 (and some of the EVP functions we need here are not present in earlier versions).

Try switching the CI to ubuntu-22.04

We need to test all possible compatibility issues first, e.g., this error here should not happen:
https://github.com/flatcar/coreos-overlay/pull/2318#issuecomment-1342533852

We need to test all possible compatibility issues first, e.g., this error here should not happen: flatcar/coreos-overlay#2318 (comment)

The error was caused by update engine being too lose in the download checks. Still it would be good to test the combinations of old update-engine vs new update-engine, old delta-generator vs new delta-generator, and dev key vs production key.


Can one boot from the SD card on the coral dev board mini?

Hi, this question was asked on issue #305, but I don't see that it was answered and I can't find an answer on the Web... With no dip-switches on the mini I wonder how/if SD card boot can be set.
Thanks much for any help,
--dave

@dripp33 Unfortunately you cannot boot dev board mini from a sd card

That's too bad, but thanks for the info.
--dave

While it's not possible to boot directly from an SD card, it is possible to mount the entire root filesystem / (also /boot and /home) from an SD card. I think it's useful to have the entire root on an SD which allows for quick backups and recovery should the filesystem get messed up.
It's pretty simple to achieve this with an empty SD card (at least 8GB), the trick is to either swap the SD cards' PARTUUID with the PARTUUID of the MMC using (gpart), or edit /etc/fstab and replace the MMC's PARTUUID of / with the SD card's PARTUUID (using blkid).

For posterity, the current instructions for the Dev Board have the DIP switch manipulations as follows:
https://coral.ai/docs/dev-board/get-started
Before flashing:
While the card is being flashed, make sure your Dev Board is completely unplugged, and change the boot mode switches to boot from SD card, as shown in figure 1.

 Boot switches set to SD card mode

After completion of flashing:
When the red LED turns off, unplug the power and remove the microSD card.

 Boot switches set to eMMC mode

For posterity, the current instructions for the Dev Board have the DIP switch manipulations as follows:

Those instructions are for the "Coral Dev Board" only. The "Coral Dev Board Mini" is a different hardware and the "Mini" has no DIP switches. This discussion was about the mini.

While it's not possible to boot directly from an SD card, it is possible to mount the entire root filesystem / (also /boot and /home) from an SD card. I think it's useful to have the entire root on an SD which allows for quick backups and recovery should the filesystem get messed up.
It's pretty simple to achieve this with an empty SD card (at least 8GB), the trick is to either swap the SD cards' PARTUUID with the PARTUUID of the MMC (using gpart), or edit /etc/fstab and replace the MMC's PARTUUID of / with the SD card's PARTUUID (using blkid).

Would it be possible for you to post a tutorial on how to do it?


Not able to make the crate work "the trait diesel::Expression is not implemented for enums::AccountStatus"

I added your crate and did the config in: https://github.com/air-balloon/api/commit/b5ec7ce8d7c514d62b6bef97dee9034fbede4acb
Summary of the problems:

It does generate a schema with account_status -> Enum, that does not work
I get the trait diesel::Expression is not implemented for enums::AccountStatus errors

If I apply this diff (to un-hack my compiling version)
diff --git a/src/models/user.rs b/src/models/user.rs
index d6df1ab..7621b41 100644
--- a/src/models/user.rs
+++ b/src/models/user.rs
@@ -13,7 +13,7 @@ pub struct User {
     pub username: String,
     pub first_name: String,
     pub last_name: String,
-    pub account_status: String,
+    pub account_status: AccountStatus,
     pub timezone: Option<String>,
     pub first_log_in_at: Option<NaiveDateTime>,
     pub last_log_in_at: Option<NaiveDateTime>,
@@ -29,7 +29,7 @@ pub struct NewUser<'a> {
     pub username: &'a String,
     pub first_name: &'a String,
     pub last_name: &'a String,
-    pub account_status: &'a String,
+    pub account_status: &'a AccountStatus,
     pub timezone: Option<&'a String>,
     pub first_log_in_at: Option<&'a NaiveDateTime>,
     pub last_log_in_at: Option<&'a NaiveDateTime>,
diff --git a/src/schema.rs b/src/schema.rs
index d727291..25ccfb8 100644
--- a/src/schema.rs
+++ b/src/schema.rs
@@ -9,7 +9,7 @@ table! {
         username -> Varchar,
         first_name -> Varchar,
         last_name -> Varchar,
-        account_status -> Varchar,
+        account_status -> AccountStatus,
         timezone -> Nullable<Varchar>,
         first_log_in_at -> Nullable<Timestamp>,
         last_log_in_at -> Nullable<Timestamp>,

I get the following errors
   Compiling api v0.1.0 (/mnt/Dev/@air-balloon/api)
error[E0277]: the trait bound `enums::AccountStatus: diesel::Expression` is not satisfied
  --> src/models/user.rs:23:10
   |
23 | #[derive(Insertable)]
   |          ^^^^^^^^^^ the trait `diesel::Expression` is not implemented for `enums::AccountStatus`
   |
   = note: required because of the requirements on the impl of `diesel::Expression` for `&'a enums::AccountStatus`
   = note: required because of the requirements on the impl of `AsExpression<enums::AccountStatus>` for `&'a enums::AccountStatus`
   = note: this error originates in the derive macro `Insertable` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0277]: the trait bound `enums::AccountStatus: diesel::Expression` is not satisfied
  --> src/models/user.rs:23:10
   |
23 | #[derive(Insertable)]
   |          ^^^^^^^^^^ the trait `diesel::Expression` is not implemented for `enums::AccountStatus`
   |
   = note: required because of the requirements on the impl of `diesel::Expression` for `&enums::AccountStatus`
   = note: required because of the requirements on the impl of `AsExpression<enums::AccountStatus>` for `&enums::AccountStatus`
   = note: this error originates in the derive macro `Insertable` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0277]: the trait bound `enums::AccountStatus: diesel::Expression` is not satisfied
  --> src/models/user.rs:23:10
   |
23 | #[derive(Insertable)]
   |          ^^^^^^^^^^ the trait `diesel::Expression` is not implemented for `enums::AccountStatus`
   |
   = note: required because of the requirements on the impl of `diesel::Expression` for `&'a enums::AccountStatus`
   = note: this error originates in the derive macro `Insertable` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0277]: the trait bound `enums::AccountStatus: diesel::Expression` is not satisfied
  --> src/models/user.rs:23:10
   |
23 | #[derive(Insertable)]
   |          ^^^^^^^^^^ the trait `diesel::Expression` is not implemented for `enums::AccountStatus`
   |
   = note: required because of the requirements on the impl of `diesel::Expression` for `&enums::AccountStatus`
   = note: this error originates in the derive macro `Insertable` (in Nightly builds, run with -Z macro-backtrace for more info)

error: aborting due to 4 previous errors

For more information about this error, try `rustc --explain E0277`.
error: could not compile `api`

To learn more, run the command again with --verbose.

Thank you in advance for helping me, I am new to Rust and am stuck on this error.
I checked in your tests folder but did not find something that helped, that said I applied all valid examples into mine.

The line
+        account_status -> AccountStatus,

should read
+        account_status -> AccountStatusMapping,

Take a look at the README for more information.

Hi
Thank you for this information, but I do not manage to make the type detection work so I still have to edit the schema file by hand
Can you help?

This is a basic problem with how Diesel generates a schema and is not really under control of this crate. There is a suggested solution here: https://github.com/adwhit/diesel-derive-enum/issues/53. Basically, make a 'dummy' module where you re-export the Mapping type under a different name, and import the module inside the diesel.toml. I haven't tried it but it should work,

This fixed all errors as you expected: https://github.com/air-balloon/api/commit/8d8c52634c9dba8bf495fbbbb2f2c178d572cff4
That said it still does not detect my enum and creates this diff when I run the migrate command:
diff --git a/src/schema.rs b/src/schema.rs
index ac9656d..93626f1 100644
--- a/src/schema.rs
+++ b/src/schema.rs
@@ -9,7 +9,7 @@ table! {
         username -> Varchar,
         first_name -> Varchar,
         last_name -> Varchar,
-        account_status -> AccountStatusMapping,
+        account_status -> Enum,
         timezone -> Nullable<Varchar>,
         first_log_in_at -> Nullable<Timestamp>,
         last_log_in_at -> Nullable<Timestamp>,

I tried the re-export method but I made this error whatever I tried
error[E0412]: cannot find type `AccountStatusMapping` in this scope
  --> src/schema.rs:12:27
   |
12 |         account_status -> AccountStatusMapping,
   |                           ^^^^^^^^^^^^^^^^^^^^ not found in this scope
   |
   = note: consider importing this struct:
           crate::models::enums::AccountStatusMapping

Ah, I see you are using MariaDB. It seems that Diesel does enum name mangling differently to Postgres. Your options are to a) re-export AccountStatusMapping as Enum inside your dummy module b) Rename AccountStatusMapping to Enum with the DieselType annotation c) use the 'patch' feature of Diesel to patch the schema after it has been generated.

Yup, MariaDB
a) and b) will forbid using more than one enum 😕
c) looks like a long term hack I will probably opt in
Do you think you can have a chance to get this fixed here ?
Reading the tests I was afraid this repository would be mostly compatible Postgres for the enums, was I right ?

The fundamental problem is that when generating the schema, Diesel looks at the database and decides that your type should be given the name Enum. This crate unfortunately cannot control how Diesel works and cannot change this fact, only work around it.
Note that this problem only occurs when generating the schema, which typically only has to be done once. When I have hit this problem before I have just hand-edited the schema.rs after the fact. Not ideal but not too problematic.

I should add that this crate is intended to support every database that Diesel supports. But it happens to be that Postgres has the best support for enums and thus gives a better experience

Okay, maybe a bunch of documentation would be cool so other mysql users dont waste time searching for something they will not find
I suspected what you explained by reading the tests and did not see an obvious mysql example
Adding a mysql example and some notes on the readme could be possible?

Closing since I do no recall what this was about exactly


chore(PL-3096): upgrade to ubuntu-24

Why the change from -latest to pinning a specific version?

https://nestomortgage.slack.com/archives/C02RCBVTJ3G/p1730842671303269


[improve][broker]Improve PersistentMessageExpiryMonitor expire speed when ledger not existed

Motivation
Speed up  the process of PersistentMessageExpiryMonitor expiring message when ledgers not exist.
Without consumer acking messages, the PersistentMessageExpiryMonitor expires messages process could be very slow if the ledger PersistentMessageExpiryMonitor  be read has been deleted from the bookkeeper.
The root cause is that,  when autoSkipNonRecoverableData is true and the ledger to be read has been deleted, the expireMessages will read entry failed and set the markDeletePosition as the failed position, see Line194.  And then waiting to be scheduled(defalut value is 5min)
https://github.com/apache/pulsar/blob/49eaa548b97eca06a6aff5d79391d49f085adb9e/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentMessageExpiryMonitor.java#L186-L196
In the next scheduled, the PersistentMessageExpiryMonitor will read the next position of markDeletePosition , which is also not existed because they may belong to the same ledger.
So the markDeletePosition just go forward 1 every 5min. And if there are  many deleted ledgers, it will lead to the ttl expire lose efficacy
Modifications
If read entry failed with ledger not existed exceptions,  we will set the markDeletePosition as the last position of the deleted ledger.
Verifying this change

[x] Make sure that the change passes the CI checks.
org.apache.pulsar.broker.service.PersistentMessageFinderTest#testMessageExpiryWithTimestampNonRecoverableException has coverd this change

Does this pull request potentially affect one of the following parts:
Documentation

[x] doc-not-needed
(Please explain why)

Matching PR in forked repository
PR in forked repository: https://github.com/AnonHxy/pulsar/pull/4

/pulsarbot ready-to-test

@codelipenghui @Technoboy-  PTAL

/pulsarbot run-failure-checks


Remove 'socket' file type

This was envisioned to be useful in the very earliest days of OIIO,
but we never really finished it or used it in any helpful way.
In addition to being essentially dead and untested code, it ties us
to boost.asio, which we use nowhere else.
So just get rid of it this vestigial piece.

Going once... going twice...


how to get started to train?

I had this problem when I start to train BR-Net.py:
geoseg-master/utils/runner.py", line 332, in
self.train_log = [round(x, 3) for x in train_log]
TypeError: type Tensor doesn't define round method
could you tell me how to tackle this problem?Thanks very much

Which version of pytorch are you using? this repo is based on pytorch 3.0.


ppc64le naming is wrong?

Hi!
Thanks again for putting this together, I've recently made a release with the new archs added in your PR from earlier: https://github.com/milesgranger/pyrus-cramjam/pull/54
In a separate build for cramjam I'm getting a cramjam-2.3.0-cp37-cp37m-manylinux_2_24_ppc64le.whl is not a supported wheel on this platform. Note that this build for conda is merely just installing the wheels from PyPi.
When I look at a project like retworkx their ppc64le is formatted like retworkx-0.8.0-cp36-cp36m-manylinux2014_ppc64le.whl
where mine is cramjam-2.3.0-cp36-cp36m-manylinux_2_24_ppc64le.whl
Makes me believe the naming is all that is off. What do you think?
Ref: https://github.com/conda-forge/cramjam-feedstock/pull/14

It's manylinux_2_24 because I can't build a manylinux2014 compatible docker image for cross compiling. retworkx builds ppc64le with QEMU so it can use manylinux2014 but it's really slow to build.

You can try running pip debug --verbose to dump compatible tags.

https://anaconda.org/conda-forge/pip

It seems the pip version on conda-forge for linux/ppc64le platform is v20.0.2? I think manylinux_2_24 tag needs pip v20.1

Good find!
But it seems in general installing from PyPi/pip was frowned upon, so I think they're going to try and make it work the "conda way". If it comes to trying to re-use the wheels from PyPi I'll definitely give this a go!
Thanks for the help! :-)

Good news! I've managed to build an manylinux2014 ppc64le docker image for cross compiling, the hard part was getting GLIBC 2.17 compile. Should be available soon in maturin-action.

Oi! What a legend, that is awesome! :open_mouth: :raised_hands:

It's available now. You can simply re-run the release workflow to use it.

Doing that now, thanks again!

Note that the wheel name was changed to include PEP 600 alias: cramjam-2.3.0-cp39-cp39-manylinux_2_17_ppc64le.manylinux2014_ppc64le.whl

ah just was looking into that as the naming looked a bit different than I'm used to, thanks for clarifying that. :-)


filelock is erasing file contents

I was trying out this library, but found that opening a file for reading while under a lock would completely erase the file's contents.
The following code reproduces the issue:
#!/usr/bin/python3

import filelock

with open("test.txt", "w") as f:
	f.write("This is some testing text")

lock = filelock.FileLock("test.txt")
with lock:
	with open("test.txt", "r") as f:
		a = f.read()
		print(a)

This issue occurs on 64bit Ubuntu 17.04, using Python 3.5.3
I have no idea if there is a particular way I am supposed to open files with filelock.  If there is, it wasn't covered in the readthedocs page, which has absolutely no information on reading or writing files.

An additional note: if you open the test.txt file after running this script, the file actually is empty, it's not just being misread as empty.

I also thought at first that the purpose of this library was to prevent simultaneous access to the specified file (test.txt in your example), but that may be mistaken.  If I understand correctly now, to lock test.txt you want to choose a different name for the lockfile, e.g.
lock = filelock.FileLock("test.txt.lock")
Now, as long as every process that wants to use test.txt must first acquire the lock on test.txt.lock, test.txt will be protected.  However, test.txt won't be protected from any programs that don't care about your lock.


Add WorkflowStep Factory and implement XContent-based Template Parsing

Description

Creates a WorkflowStepFactory class to map a template "step type" to the correct instance
Parses the entire Use Case Template into XContent
Process the user inputs section for the workflow into WorkflowData params
Processes the user inputs section for each node into WorkflowData content
Refactors code to separate parsing functionality (WorkflowNode et. al.) from execution functionality (ProcessNode et. al.).  Uses the WorfklowStep and Workflow Data when creating the ProcessNode.
Implements an executor service to use the OpenSearch thread pool for the async execution.
Added tests.
Fixed the ProcessNodeTests bug

Issues Resolved
Fixes #41
Fixes #42
Fixes #46
Fixes #50
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Flipping back to draft to integrate the commits from #24 and #44 into the factory class (and delete my demo version).

And flipping back to ready for review, after rebasing and also completing tasks from #42 and fixing #50.

To ease review, a general summary of the main part of this PR:

Parsing.  Starts with Template, which also parses workflow, which also parses WorkflowEdge and WorkflowNode.
Process Sorting: takes the WorflowNodes and WorkflowEdges and creates the sorted ProcessNode sequence with links to predecessor ProcessNodes (no change from previous code, just separated out the parsing part)
WorkflowStepFactory: takes the node "type" field and generates a unique instance of the correct workflow step

Additional changes:

Made the sorter and step factory singletons taking the needed arguments that will go into the process nodes and workflow steps
Passed an executor service around to have better control of threading.  This can be changed in the future away from the generic one.
Misc. cleanup of warnings (casting, deprecation)

Thanks @dbwiddis for adding the Pipeline Processor parsers!


Provide a way for regular users to ignore xcode check

In some corporations folks run vendored versions of xcode where updating
to the latest version of xcode is simply not possible with the toolchain
they are working with. Given there is already a way to bypass the xcode
check in github actions, there should be a reasonable way for most users
to bypass the check too if they would like knowing the risks it may
entail.
There is already a rather widely shared solution similar to this:
https://stackoverflow.com/a/56252549
However this is brittle and is prone to reverting if a brew update is
run (which the default brew configuration will do when installing a new
package https://github.com/Homebrew/brew/issues/9285)

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same change?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

Sorry, we don't want this behaviour. We print these messages because things are known to be broken without them.

Given there is already a way to bypass the xcode
check in github actions, there should be a reasonable way for most users
to bypass the check too if they would like knowing the risks it may
entail.

This is only because we use GitHub Actions for our own CI.

Note that the "up to date" checks are merely warnings, not errors, so you can ignore them if you want.
The minimum version check is however mandatory - other parts of brew will break without it, for example in #12078.

Yeah I don't mind the print statements, but I was hoping to get around the minimum version checks.
I'll see if we can have a non-vendored version at work just brew, but it would be nice if there was just a: let me ignore it switch.

Yeah I don't mind the print statements, but I was hoping to get around the minimum version checks.

You cannot because, as @Bo98 said, many things are known to break without them.


Add optional statistics

After browsing my Podcast Addict statistics it dawned on me that it might be neat to know how much time is spent writing commits. This would be wholly optional through the configuration file and I'm imagining allow for breakdowns per day, week, month, and year. The values would just be stored as integers (32 bit should be enough, giving a possible of 68 years of data) as running seconds.
I'll need to consider how to account for time spent in the $EDITOR if the 'specifyBody' option was chosen. My current assumption would be to just time the amount it takes for the model to run and that should take into account all possible scenarios.
The statistics would be stored in a plain old text file (most likely in JSON) and showing the statistics could be done through a --stats flag, either prepended to the actual interface or stand-alone (this could be configurable).
I'm also imagining that some sort of toast could happen (e.g. confetti) if a defined number of seconds has passed for the day, week, month or year. This is a stretch goal.

I've made a few commits on the issue-11 branch, but I'm once again getting bogged down in terms of performance, much like in #10. I'll have to have a look on how to improve things as I really don't want any noticeable delays when starting the program.

For future reference: the way to quit the program right after the first draw is to add the following:
--- a/gui.go
+++ b/gui.go
@@ -182,6 +182,7 @@ func (m *model) Init() tea.Cmd {
 }

 func (m *model) Update(msg tea.Msg) (tea.Model, tea.Cmd) {
+       return m, tea.Quit
        switch msg := msg.(type) {
        case tea.KeyMsg:
                switch {

And the current benchmark off of master is:
$ hyperfine --warmup 10 --output inherit --ignore-failure './cometary'
...
Time (mean ± σ):      47.8 ms ±   6.5 ms    [User: 11.1 ms, System: 13.5 ms]
  Range (min … max):    39.0 ms …  82.7 ms    52 runs

Looks like I'm on the home stretch with the latest commits and with no impact to the start-up time; the measurement is basically identical to the above 🎉

Resolved in release v1.7.0.


WIP: test local zone batch

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

AWS CodeBuild CI Report

CodeBuild project: IDFModuleTestsInfrastructur-59JoFoVH64CI
Commit ID: 7621ec9c1ab59f1755b71675b79e98d5849b5290
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Please fix the below @kevinsoucy:

static checks
do not commit changes to the manifest files
make sure to add changelog


[USABILITY] - Safer Illinois - Notification is posted every single minute in iOS

Describe the bug
Notification is posted every 1 minute in iOS. Due to the notification phone battery is drained so fast.
To Reproduce
Steps to reproduce the behavior:
Install the Safer Illinois app in iOS
Complete the initial onboarding and COVID onboarding process with Exposure notification ON
User successfully see the COVID screen
Actual Result
Notification is posted on the device every single minute and due to that issue battery is drained so fast
Expected behavior
Battery should not drain so fast. Also, the user is not expecting notification every single minute.
Smartphone (please complete the following information):
Device: [e.g. iPhone]
-App Version [e.g. 2.6.13]

@Priyaravi8 that is expected and required behavior of the exposure notification system when it runs in the background. Please see Illinois KB: Safer Illinois, Exposure Notifications.
If you have suggestions to update that page, let's talk about them.


When I create new stack , input field "Project_Path" length limited at 20 chars, it's better get it more greater, like 200 chars ...

Hi @dehengxupix ,
fixed v2.24.1, redeploy

Appreciate for improvement


Which indicators can it measure?

Can it be used to measure throughput, page load time, etc.?

Hi there!
Currently this is in very early development, so at the moment it is not able to measure anything.
The first goal is to measure throughput though. Give it another 2 - 3 weeks and it should be working!

Looking forward to your work！

@wangjianyayaya The tool itself is now able to measure throughput. Although my tests are pretty strange. I also measured Page Load Times via E2E testing tool Selenium where I loaded youtube.com and google.com a bunch of times (> 100). My results show that for Page Load Times itself QUIC is faster when Cache is enabled in the Browser, otherwise TCP+TLS would be faster.
But back to throughput testing: It seems like the Go TCP implementation is faulty since it does not seem to scale the receive window properly, thus leading to strange results when RTT or packet loss is increased (where the receive window is not adjusted).
So when you use QUIC in the test and have high simulated RTT or packet loss, QUIC performs better, while TCP does not. But as said, it is due to the TCP Go implementation.


DBus Monitor to pass events to input modules: First cut

This is a working implementation of the DBus monitor applied to Input Modules!
I've folded it directly into this project instead of in a separate repo.
Try it out with RUST_LOG=debug cargo run --target x86_64-unknown-linux-gnu -p framework-inputmodule-dbus-monitor, to see debug output too, then try making a test calendar event with notification. Assuming your system uses the same DBus monitoring channel as mine, your LED Matrix module should blink when a notification comes in for a calendar event.
Some things I am working on/trying to make better:

I know this is only one level better than calling the binary you've outputted, but I think passing Clap CLI arguments is a pretty good interface, I'm not sure if it's worth going to a level lower in the existing modules or not when you've implemented a pretty great interface there.
~I want to make this much more generic as @kiram9 and I have discussed, where a user can create a config file in their home directory, subscribe to specific events, and then have certain commands run in response to them! But wanted a working example first.~ This is done, you can now have this respond to any DBus message and run any command!

I think for this reason the CLI interface is good because it's pretty understandable to users who might configure this through a file.

~I can't seem to figure out how to make my run_inputmodule_command which calls the serial_commands function go on to the next command...it just stays on the first one. Any ideas @JohnAZoidberg ? Sorry if this is super obvious and I'm missing something!~ I added a new command that doesn't loop to address this!

@JohnAZoidberg @kiram9 FYI, I finished up a pretty decent implementation of this that let's you configure which channel you want to monitor and what commands to run through a configuration file! Eventually you could have an n of more than 1 here, but this is a decent PoC.
It is based on my packaging-process-and-systemd-service branch which hasn't been merged yet, my intention is to eventually shove this into systemd and run all of the time.
I think I'm going to pause here for now though until I receive the newer hardware so I can test it with that, but if you'd like to merge it sooner for any reason let me know, or feel free to try it yourself :).


Better configuration for quick action prompts

Validations

[X] I believe this is a way to improve. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that requests the same enhancement

Problem
Quick Actions (experimental.quickActions) currently have a prompt field that gets inserted into a hardcoded template.
There also appears to be no mechanism to set the system prompt.
While this is fine as a default, it's frustrating as a power user with prompt engineering skills. It would be nice if I could define my own prompt template, including the system message and prefilled assistant response. (Prefilling the response makes it much more likely that the AI will respond in the correct way -- for example, you can prefill with the opening ticks of a code block to push it to respond with a codeblock.)
Solution
I propose breaking the prompt field into three fields:
{
  "systemMessage" //system message sent to the model
  "prompt" //user message sent to the model
  "prefilledResponse" //prefilled response sent to the model

Yeah, that would be a better way to do it. I didn't realize prompt files could be global, so I hadn't paid much attention to them.


refactor: reduce duplicate code in airflow2 scheduler

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

37 of 48 (77.08%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 72.836%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ext/scheduler/airflow2/airflow.go
37
48
77.08%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
5234

Relevant Lines:
7186

💛  - Coveralls