Ergonomic changes for I2S callbacks.

This makes a few changes suggested in the last bit of https://github.com/esp-rs/esp-idf-hal/pull/232:

Trait functions take impl FnMut instead of Box.
Callback bookkeeping is no longer static (like the GPIO callbacks); instead, it's stored with the channel.
Added rx/tx_unsubscribe() methods to the channels.

Also, fixed the naming of the I2sRxEvent/I2sTxEvent enums to be more inline with the brevity of Rust in general:

DataReceived -> RxDone
ReceiveOverflow -> RxOverflow
DataTransmitted -> TxDone
TransmitOverflow -> TxOverflow

@dacut: Overall, LGTM, two issues only:

Can you look at the CI build failures? The CI pipeline is now functioning OK, so these are real issues.
I think you are leaking the Box that you push into UnsafeCallback. The UnsafeCallback::callback member specifically. You need a Drop impl for UnsafeCallback that does Box::from_raw on the callback member and then does nothing with it so that the memory of the Box is dropped at the end of the drop() fn.

Ah, good catch on the leak. I forgot to add Drop when I changed Box<Box<...>> to *mut Box<...>.
I think I've fixed the no-alloc bit as well (and beat my CI pipeline into submission as well based on your fixes); looks better now: https://github.com/dacut/esp-idf-hal/actions/runs/5380466584

Thanks!

@dacut Question: are you using the Callback API for anything? The one use case I find for it is async send/receive as I mentioned earlier. However, if that's the only use case we can do with the callbacks, it can be implemented in a simpler way, without - actually - exposing an unsafe subscribe/unsubscribe API tot he end user. The callbacks would just become an internal implementation detail of two new methods - send_async and receive_async.
Asking because if we take that route, I need to remove the Callback API and replace it with the above two async methods. The benefit: simpler implementation, and the demotion of the callback API would actually remove the [cfg(feature = "alloc")] stuff from the codebase, as implementing callbacks specifically for async support does not need boxing.
What do you think?
BTW, this question and what I'm suggestion has consequences beyond I2S. I'm currently working on exposing the continuous, DMA-powered ADC driver of ESP IDF, and I face the same situation there w.r.t. callbacks. I wouldn't be surprised if it is the same also for SPI, UART, I2C and so on.

@ivmarkov I am not. The main use case I envisioned for it was processing DMA buffers in a just-in-time manner. I think async is a good fit here, but I have not played with async code on ESP32 yet (that usually means bringing in Tokio to me in the non-embedded world, but here I'm guessing it just means plugging the async subsystem into FreeRTOS).
I do wish the ESP-IDF SDK exposed the DMA buffers directly, though. It ends up copying the data over, which I found a bit limiting on performance (though I was trying crazy things like spectrum analysis/FFTs).
Also, the ESP32 (but no other models) supports a direct I2S to ADC/DAC mode that isn't exposed in the ESP-IDF SDK (similar to the LCD/Camera mode). Let me know if that's of interest to you. (I'd have to toy a bit with these modes; I wish they had been kept in later models as I find them useful, but at least LCD mode is buggy on the ESP32 so I suspect that factored into the decision.)

@ivmarkov I am not. The main use case I envisioned for it was processing DMA buffers in a just-in-time manner. I think async is a good fit here, but I have not played with async code on ESP32 yet (that usually means bringing in Tokio to me in the non-embedded world, but here I'm guessing it just means plugging the async subsystem into FreeRTOS).

OK, good to know. Then in the name of simplicity, I might be removing the subscribe``unsubscribe API and replacing it with a simple hidden notification mechanism to power the future async send/receive pair of functions.
W.r.t. tokio - no, you don't need that. I'm personally using a tailoring of async-task here. In future, we might be supporting async-executor as well, from the embassy ecosystem (though it needs all futures to be ultimately resolving to functions which take non-generic parameters, which is a bit of a restriction).
The nice thing about async-task (aside from it being minimal and amenable to customization) is that it plays well with async-io, which we can natively support on the ESP32 (unlike tokio's mio which requires Linux-style epoll which we cannot support on the ESP IDF). async-io gives you async for network sockets.

I do wish the ESP-IDF SDK exposed the DMA buffers directly, though. It ends up copying the data over, which I found a bit limiting on performance (though I was trying crazy things like spectrum analysis/FFTs).

I think zero-copy DMA might be difficult with the async metaphor in Rust, but I could be wrong.

Also, the ESP32 (but no other models) supports a direct I2S to ADC/DAC mode that isn't exposed in the ESP-IDF SDK (similar to the LCD/Camera mode). Let me know if that's of interest to you. (I'd have to toy a bit with these modes; I wish they had been kept in later models as I find them useful, but at least LCD mode is buggy on the ESP32 so I suspect that factored into the decision.)

We might be looking into this in future. For now, for me personally at least - I2S IO and continuous ADC is good enough.

Ah, yeah, wasn't proposing bringing in Tokio here. It's just my sole exposure to async Rust for now; I'll take a look at what you're doing with async-task.
I'd have to think how DMA and async work together a bit. The read API is easy enough: async fn read_async(self: Pin<&mut Self>, data: &[u8]), where data is created via slice::from_raw_parts.
The write API is trickier, because you now need two APIs: one to get the next buffer, one to submit it:

async fn wait_write_buffer(self: Pin<&mut Self>) -> &mut [MaybeUninit<u8>]
async fn write_async(self: Pin<&mut Self>, data: &[u8])

But this is insufficient:

You need to make sure data is the same slice returned from wait_write_buffer.
If the caller never calls write_async, there's likely cleanup work that needs to be done.

This calls for a struct to wrap the buffer, which I need more time to think about.

I'd have to think how DMA and async work together a bit. The read API is easy enough: async fn read_async(self: Pin<&mut Self>, data: &[u8]), where data is created via slice::from_raw_parts.
The write API is trickier, because you now need two APIs: one to get the next buffer, one to submit it:

async fn wait_write_buffer(self: Pin<&mut Self>) -> &mut [MaybeUninit<u8>]
async fn write_async(self: Pin<&mut Self>, data: &[u8])

IMO neither read nor write is easy. Just look at the Embassy Matrix channel. Zero-copy DMA is like the topic for the past year, if not more. :)
My (very superficial) understanding of the zero-copy DMA problem is that is is roughly isomorphic to the Linux io_uring problem. In other words, both io_uring and zero-copy DMA are essentially completion based, while the Rust Future model is polling based. Intuitively, a completion based model means you need to "hand off" ownership of your read or write buffer to the DMA engine for the duration of the read/write operation. Once the DMA operation is over (and you are notified via a callback), you can reclaim the ownership of your buffer, but what you should NOT do - by any means - is to drop/free the buffer while the DMA operation is running. The problem is, typical & [u8] and &mut [u8] buffers are only valid while the Rust future is alive. But since you can drop the future at any time, these references might become invalid while the DMA engine is still using them, which is the crux of the problem. Now, if you can - in your Future::drop - stop the DMA engine in a quick, synchronous way, you still have a way out (kinda), as this way you reclaim your buffers "in emergency". This is still half-baked though, as if you just call core::mem::forget(my_future) (which is a completely safe Rust API), the drop won't be called, yet the lifetime of the & [u8] / &mut [u8] reference would be over, so you can move / drop your buffers immediately after forget-ing the future and still mess it up completely, as the DMA engine might still be accessing that memory!
You can of course refcount the buffers - thus allowing shared ownership - but if you do this, you take another hit - you need to allocate the memory from the heap so the thing is not zero cost for other reasons now. Or you just let the DMA engine have its own buffers, and then you copy from/to those buffers, as the ESP IDF driver does.
There has been a lot of talks in the community how to remedy the situation, including linear types, async drop and whatnot, but in the meantime, supporting a completion-based API from Rust means you have to choose your poison: refcounting and a heap allocation, or non-zero-copy.


In Pulsar client, the effective value of NackRedeliveryDelay is about 1/3 of its specified value

Describe the bug
the effective value of NackRedeliveryDelay is about 1/3 of its specified value.
To Reproduce
Steps to reproduce the behavior:
In my test, I set NackRedeliveryDelay=200 second delay, but it is retrying at second 57
See my log:
2 - ID: (10,1,-1,-1)
3 - ID: (10,2,-1,-1)
4 - ID: (10,3,-1,-1)
5 - ID: (10,4,-1,-1)
6 - ID: (10,5,-1,-1)
7 - ID: (10,6,-1,-1)
8 - ID: (10,7,-1,-1)
9 - ID: (10,8,-1,-1)
10 - ID: (10,9,-1,-1)   //at second 10,  processed message #9
68 - ID: (10,9,-1,-1)    //at second 68,  processed message #9 again,  delay is 57 seconds only.
69 - ID: (10,0,-1,-1)    //at second 69,  processed message #0 again,  delay is 68 seconds only.

Expected behavior
The delay for the nack redelivery is not meant to be precise, but it should not be around 1/3 of the value. In my case, retrying should happen around 200s
Desktop (please complete the following information):
Mac, or linux
Additional context
-Standalone Pular server 2.4.1. or 2.3.1
-Python or golang,  with C++ client 2.4.0

Hi @Jesse-Zhang-Bose . I think that is the right process.
There are two variables of NackRedelivery. One is NackRedeliveryDelay, another is TimeInterval.
The NackRedeliverDelay is the message should redelivery after how long. And the TimeInterval is the scheduler time interval.
The scheduler will check is there any messages that need to redeliver. And it will be scheduled with the time gap specified by TimeInterval. The TimeInterval is set to 1/3 NackRedeliveryDelay. So you will see it retry after 1/3 of  nack redelivery delay.
You can see the implementation of the Nack at here https://github.com/apache/pulsar/blob/master/pulsar-client-cpp/lib/NegativeAcksTracker.cc
It implemented as same as java   https://github.com/apache/pulsar/blob/7275d53af463ed3526d93a88d27d278802425a4d/pulsar-client/src/main/java/org/apache/pulsar/client/impl/NegativeAcksTracker.java#L54

@zymap, thanks for the feedback.
The internal work does explains the behavior I reported. But I would still think the behavior itself is unexpected, or at least quite confusing.

@Jesse-Zhang-Bose Ah. I see.
You need a explicit value to control the redeliver delay.
I will try to add this feature.

@Jesse-Zhang-Bose
I think we can expose the TimeInterval to config.
Because of all nacked messages will queue into the redeliver map. We need to keep the TimeInterval as small as possible so that we can redeliver the nacked message quicker.
As your case, if it retries after 200s, it will redeliver the first message and the rest messages will redeliver after the next 200s if the messages are not sent at the same time as the first message.

Hi @Jesse-Zhang-Bose, I think exposing the TimeInterval might is not a good idea to address this.
I will close this issue if you have not any problem.

@zymap i agree with you,timeInterval is pulsar's internal work, exposing it is not necessary.  However,  I would still think this is an issue need to fix, maybe use another way?

@Jesse-Zhang-Bose Sorry for my late response.
I think we can use the NackRedeliveryDelay as the redeliver time. So you can configure it by yourself.
Hi @merlimat. Because you wrote the NackRedelivery, what do you think? Can we use NackRedeliveryDelay?

Closed as stale. The development of the C++ client has been permanently moved to http://github.com/apache/pulsar-client-cpp. Please open an issue there if it's still relevant.


Test Filesystem::searchpath_split behavior on an empty string

It should make a vector with no entries, not a vector with one entry
that is an empty string. Verify.

Withdrawing, I have a replacement coming.


Schema validation for hatch fails with [tool.hatch.env]

In the hatch documentation, if one wants to use a different environment type, then you need to specify, for instance with juftin/hatch-pip-compile
[tool.hatch.env]
requires = [
    "hatch-pip-compile"
]

However, the current schema definition seems to fail with
Invalid file: pyproject.toml
[ERROR] `tool.hatch` must not contain {'env'} properties

I'm not sure if this is expected, as I'm having a hard time reading the associated PEPs to understand (and digging into the code to understand what is expected).

https://github.com/SchemaStore/schemastore/blob/master/src/schemas/json/hatch.json probably needs to be fixed, then.

@flying-sheep, was this hand written or generated somehow?

The part that's a bit confusing is one can see the definitions in the schema: https://github.com/SchemaStore/schemastore/blob/7a7f32e81810a8909773810564fe52b43f31bcd4/src/schemas/json/hatch.json#L376-L413 with requires right there, but it seems to be missing the .env portion of the definition at the CollectorEnv level.

Ahh, I think this might not be updating. It should have changed in https://github.com/SchemaStore/schemastore/commit/c20b9a01ec850d7bf19559bd7e20d565b74f3832 but don't see anything.

Ahh, you are not pinning on us, so it's using an old cached version. Pre-commit globally caches. If you put >=2024.04.20 or probably 2024.04.08 is fine, it should work.
You can instead put this repo as your pre-commit hook, then it pins on this instead of validate-pyproject.

Ahh, you are not pinning on us, so it's using an old cached version. Pre-commit globally caches. If you put >=2024.04.20 or probably 2024.04.08 is fine, it should work.

I did follow the README instructions you have in this project https://github.com/henryiii/validate-pyproject-schema-store/blob/353a7a8a74a6c3aa552c21e8017b9e5629a7981e/README.md?plain=1#L25-L32 so it's not clear to me what I messed up initially. I can re-clear and update pre-commit, but I can also add a >= in additional dependencies.

I'd add >= whenever you start using a new hatch feature that was added at some point, such as >=2024.04.08 for .env.
The other way to do it would be to use
repos:
  - repo: https://github.com/henryiii/validate-pyproject-schema-store
    rev: <insert here>
    hooks:
      - id: validate-pyproject

Which is an alternative suggested in the README.

Ahh, yes, that’s a pre-commit quirk, svn versioning no longer works for the main repo being checked out. Maybe we should drop the min version requirement.


Description of node is not shown

Godot version:

Godot 3.1.beta fa7329f64
OS/device including version:

Kubuntu 18.10
Issue description:

Description of node is not shown.
Steps to reproduce:
Captured with Godot 3.1.beta3 official

Captured with Godot 3.1.beta fa7329f64

Minimal reproduction project:

I was about to mention that it could be related to #25338 (only recent change to CreateDialog), but it seems it was merged right before beta3.

possibly https://github.com/godotengine/godot/commit/a1f955a1d#diff-d1da977380504a5977e37b7e442eeb0a

CC @groud

It is unlikely my change caused this behavior but who knows. I'll have a look.

Seems to work fine in 3.1 beta 4 (17809ca), which is only a few commits before the reported broken version at fa7329f... I'll try a bisect.

It's a regression from 4fd7115, CC @YeldhamDev.

But, that commit doesn't even touch that, as far as I can see?

You removed some signals in the search bar code, maybe it has to do with this problem?

@groud Yes, the search bars in the script editor and docs, nothing to do with the "New Node/Resource" dialog.

CreateDialog uses EditorHelpBit, which you changed from a PanelContainer to a MarginContainer.

@akien-mga Huh, I couldn't even imagined that this was part of the dialog code, fixing it right now.


Add testing for R script files

Is your feature request related to a problem? Please describe.
There currently isn't a system in place to test the functionality of the R scripts. This is cumbersome (see: testing for #575) because there's no good way to mock up the functionality in Python, especially because some R code now uses parallelization.
Describe the solution you'd like
This is unfortunately not available in a local pytest environment. However, we may be able to add another job called r_test in .travis.yml which handles this for us.
The library testthat will allow us to accomplish this. Here's a good starter describing the basic process: https://www.r-bloggers.com/2019/11/automated-testing-with-testthat-in-practice/.
This job will need to run the test script directly using Linux commands. We can likely use similar methods as with the docker_deploy job with r_test.
Additional context
This should be tested on the Python 3.7 Docker image.
Additionally, a refactor of the scripts is likely in order to ensure specific functionality can be tested.

I think it's worth spending a day or so seeing if this is feasible. If it looks like it will be, then opening a design doc for what the restructuring would look like

No longer necessary, we'll be transitioning to full python


fixes for  backend/sr/db.js, readme file

URI for the mongo cluster used for development was in /backend/src/db.js file.  I took that out, and added one config value show in readme.   Now entire connection string is built from configured values.  Have tested this with
API_MONGO_LOCATION="mongodb"
and local dev environment.

Thanks for the update. I have merged it into main repo.


Updated files update.ts and package.json

The project build didn't work.
I cloned the main repository and installed all the "npm i" dependencies, then tried to build the project "npm run build".
I saw errors in the console:

I fixed the update.ts file and now “npm run build” builds the project correctly.
I also updated all dependencies to the latest versions.
Related to #188

Please synchronize the latest code. No need to modify package.json. Just add the type in the 'update. ts' file.thanks.


fix: conversion of environment variables refs does not consider compound cases

What this PR does / Why we need it:
Fixes a bug while converting v1 config with multiple env var references to a v2 config, e.g.:
- name: "{{ .Env.alertgroup }} - {{ .Env.application_name}}"

produces only a single Environment type parameter for {{alertgroup}} and loses the {{application_name}} variable reference.
The fix contains the code to detect multiple environment variable references and converts them into a compound parameter, e.g.:
  - name: "{{ .Env.GOPATH }} - {{ .Env.GOROOT }}"

gets converted to:
    name:
      format: '{{ .gopath }} - {{ .goroot }}'
      references:
      - gopath
      - goroot
      type: compound
    parameters:
      gopath:
        name: GOPATH
        type: environment
      goroot:
        name: GOROOT
        type: environment

Special notes for your reviewer:
Does this PR introduce a user-facing change?
Multiple env var refs in v1 config yaml files are correctly transformed into compound parameters in the resulting v2 config

yeah I've tried (multiple) env vars in the JSON payload as well. The result is somewhat different of course as it is not converted into a compound variable but I think it is fine:
json:

v2 yaml:

yeah I've tried (multiple) env vars in the JSON payload as well. The result is somewhat different of course as it is not converted into a compound variable but I think it is fine:
[...]

Perfect thanks!
As discussed in person, I was thinking about this wrong - works perfectly then.


Misc cleanup of javalang, type coercion, jsonya, and Maybe

big tidy is https://github.com/apache/brooklyn-server/commit/ec4da197d5caf3ac9bb63ab94924718aae83c615 moving most of our static TypeCoercions to a non-static utils impl (but not changing how we use TypeCoercions ... apart from the exception it throws)
others are as described in the individual commits, nothing too exciting, and big improvements to tests and javadocs
encountered while looking at how we can improve yaml type inference

@ahgittin Nice, looks like a good refactor. Minor comment about singletons...?

good idea @grkvlt , done


Cannot build docker image

Are you experiencing an issue with...

[ ] shields.io
[x] My own instance
[ ] gh-badges NPM package

:beetle: Description
Hi, I'm trying to build a docker image and host shileds locally, so I just cloned the code and try building it, but an error occurred.
$ docker build -t shields .
Sending build context to Docker daemon  2.912MB
Error response from daemon: Dockerfile parse error line 19: unknown instruction: NODE

It seems we're missing the RUN keywork in line 19, I fixed it and run building again, and I got this error.
Step 9/15 : RUN npm install
 ---> Running in f088c77a58d9
npm WARN deprecated<EMAIL_ADDRESS>New custom equality api does not play well with all equality helpers. Please use v5.x
npm WARN deprecated<EMAIL_ADDRESS>no longer maintained
npm WARN deprecated<EMAIL_ADDRESS>Package no longer supported. Contact<EMAIL_ADDRESS>for more info.
npm WARN deprecated<EMAIL_ADDRESS>CircularJSON is in maintenance only, flatted is its successor.
npm ERR! code ENOLOCAL
npm ERR! Could not install from "gh-badges" as it does not contain a package.json file.

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2019-01-20T01_46_18_335Z-debug.log
The command '/bin/sh -c npm install' returned a non-zero code: 1

Please take a look. If you have an official docker image, please add it to README. Thanks!
:link: Link to the badge

:bulb: Possible Solution

I've opened #3165 as the build does produce an image but it cannot be started (hangs forever).


Scrape letterboxd by popular movies

This is extremely slow and inefficient so we might want to find another way to circumvent this.

We'll merge this for now, as this does not interfere with the recommender system that we intend to build.


Writing to Network Shares failes

Hi,
writing to network-shares does not work.
OS: Windows 10 - 2004
Share: Ubuntu 18.04 - Samba on ZFS
Command line:
not Working
 --out-dir "\\fileserver2.grote.lan\Podcasts\{{podcast_title}}"
 --out-dir \\fileserver2.grote.lan\Podcasts\{{podcast_title}}
working
 --out-dir "Z:\Podcasts\{{podcast_title}}"
 --out-dir Z:\Podcasts\{{podcast_title}}
Output
C:\Users\mg\Desktop>podcast-dl-win-x64.exe --url https://sternengeschichten.podigee.io/feed/aac --out-dir "\\fileserver2.grote.lan\Podcasts\{{podcast_title}}" --include-episode-meta --include-meta --episode-template "{{release_date}} - {{title}}" --archive "\\fileserver2.grote.lan\Podcasts\{{podcast_title}}\archive.log"
\\fileserver2.grote.lan\Podcasts\Sternengeschichten does not exist. Creating...
(node:18220) UnhandledPromiseRejectionWarning: Error: UNKNOWN: unknown error, mkdir '\\fileserver2.grote.lan\Podcasts\Sternengeschichten'
    at Object.mkdirSync (fs.js:914:3)
    at main (C:\snapshot\podcast-dl\bin\bin.js:112:8)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
(node:18220) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:18220) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Thx
mg

Hey! It sounds like the Node process isn't able to create a new directory in the share. Might be a permissions issue?
I would try saving the podcast into an existing folder on the share and see if it works or if you get a different error. Let me know!

i, thx for the reply, ive have tried following:
Create Folder first, then start podcast-dl
But same issue
Wishes
mg

Thanks for checking! Don't have much experience with UNC paths in Windows.
Looks like this should work if you provide a drive letter based on this Stack Overflow post. Something like c:\\server\share.

Hi,
yes, Paths mounted on drive Letters are working perfectly.


jackett: 0.20.4029 -> 0.20.4078

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for jackett is: API Support for your favorite torrent trackers
meta.homepage for jackett is: https://github.com/Jackett/Jackett/
meta.changelog for jackett is: https://github.com/Jackett/Jackett/releases/tag/v0.20.4078
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.20.4078 with grep in /nix/store/4fs1jx13ja9lv5piwnv8piab0jc7lzry-jackett-0.20.4078
found 0.20.4078 in filename of file in /nix/store/4fs1jx13ja9lv5piwnv8piab0jc7lzry-jackett-0.20.4078

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
jackett

Instructions to test this update (click to expand)

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

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/4fs1jx13ja9lv5piwnv8piab0jc7lzry-jackett-0.20.4078
ls -la /nix/store/4fs1jx13ja9lv5piwnv8piab0jc7lzry-jackett-0.20.4078/bin

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

1 package built:

jackett

Maintainer pings
cc @edwtjo @nyanloutre @purcell for testing.

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

1 package built:

jackett


Ignore class

Is there any way to ignore the click of specific button so it's not sending an alert?
For example I have a form within this form I have a button that open a popup to add item to the list
and I don't want the user get notified if he click on that button
Also having an ignore class for a specific field can be usefull

Here is a solution base on submit button, to prevent alert on specific button #ID onclick.
Edit dirrty.js find this part
d.form.on('submit', function(){
 	d.submitting = true;
 });

Add this part just under, you can change ID name for your needs
                       ```

// new code this will prevent onclick alert on a button that have ADD #ID.
d.form.on('click', "#add", function(){
d.clicking = true;
});
 Change this part to add && !d.clicking
this part

if(d.options.preventLeaving){
$(window).on('beforeunload', function(){
if(d.isDirty && !d.submitting){
return d.options.leavingMessage;
}
});
}
become  this
				```
//add d.clicking
 				if(d.options.preventLeaving){
					$(window).on('beforeunload', function(){
						if(d.isDirty && !d.submitting && !d.clicking){
							return d.options.leavingMessage;
						}
					});
				}

Next need to found a way to add a class to ignore a field to get dirrty.


Renamed completeWithAsync to completeWithTask

In swift-nio completeWithAsync was renamed to completeWithTask
https://github.com/apple/swift-nio/commit/e66b64e4e3e3409729befb31d894b89062e003dc
Motivation:
completeWithAsync causes build errors on macOS 12 and Xcode 13
Modifications:
Renamed completeWithAsync to completeWithTask
Result:
No more build errors

@swift-server-bot test this please

@tomerd I think we should cherry-pick this with #218 into a patch release.

@saltzmanjoelh Thanks for providing this fix. Since this change was made in the latest SwiftNIO release, we will need to update the SwiftNIO requirement to 2.32.0 in the Package.swift as well.

On it...

@fabianfett Done.
https://github.com/swift-server/swift-aws-lambda-runtime/pull/221/commits/e78f903c3e018b73502df8faf74682cfb77c938f

@swift-server-bot test this please

thanks @saltzmanjoelh

@tomerd My pleasure.
Is it failing on 5.6 though?
https://ci.swiftserver.group/job/swift-aws-lambda-runtime-swift-nightly-prb/86/console
12:42:48 [187/219] Compiling _NIOConcurrency AsyncAwaitSupport.swift
12:42:48 /code/.build/checkouts/swift-nio/Sources/_NIOConcurrency/AsyncAwaitSupport.swift:72:39: error: cannot use parameter 'body' with a non-sendable type '() async throws -> Value' from concurrently-executed code
12:42:48                 let value = try await body()
12:42:48                                       ^

12:42:48 /code/.build/checkouts/swift-nio/Sources/_NIOConcurrency/AsyncAwaitSupport.swift:72:39: note: a function type must be marked '@Sendable' to conform to 'Sendable'
12:42:48                 let value = try await body()
12:42:48                                       ^
12:42:48 error: fatalError
12:42:49 Build step 'Execute shell' marked build as failure

@saltzmanjoelh this is an issue in SwiftNIO: https://github.com/apple/swift-nio/pull/1943

@fabianfett Ah! Ok thanks!


Supporting changes for backups UI

These are supporting changes for https://github.com/aptible/dashboard.aptible.com/pull/625

👍 Great!


Need support for overflow based style wrt to X and Y axis

🚀 Feature request

Support for X and Y-axis in the overflow styles

🧱 Problem Statement / Justification

Currently, NUML doesn't seem to have any support for overflow on the X and Y axis only, so we need to add its support in https://github.com/numldesign/numl/blob/main/src/styles/overflow.js

✅ Proposed solution or API

Please provide code snippets, gists, or links to the ideal design or API

<nu-block overflow="x-axis">
This is where my componnet exist
</nu-block>
<nu-block overflow="y-axis">
This is where my componnet exist
</nu-block>

↩ Alternatives

What alternative solutions have you considered before making this request?

📝 Additional Information

What resources (links, screenshots, etc.) do you have to assist this effort?

It has. Like in original overflow CSS property:
"The overflow property is specified as one or two keywords chosen from the list of values below. If two keywords are specified, the first applies to overflow-x and the second to overflow-y. Otherwise, both overflow-x and overflow-y are set to the same value."


Cannot find modules after install

After successful installation of torchaudio in conda environment, I am able to import the module import torchaudio, but I am unable to import any submodules (i.e. import torchaudio.transforms as t )
This seems like a very promising project... sorry to see that there are so many installation issues. Let me know if any further information is needed to reproduce the error.
Thank you for your efforts!

@tarekmaketechno What command did you use to install torchaudio? Also what is the error message when trying to import the submodules?

@jamarshon I think I fixed the issue - I had run setup using sudo (to work around a dependency issue)...  this seems to have caused all sorts of other dependency problems. I've gotten it working now by redoing the entire install in a fresh conda environment.
Thanks just the same though!


usernames (Emp_Username) are not unique

At this time we have multiple Employee records (accounts) with the same username.
We need to address this as we cannot ensure that we are always logging in
with the proper account.

TODO, clean-up dummy employee entries


Java SDK v2 support is broken

A user reported failure use our support for the AWS Java SDK v2 on recent versions of the SDK. SDK versions 2.20.7 and 2.25.29 were tested and failed, with our Demo2.java example or the following simple example:
public class ScyllaDbTest {
  public static void main(String[] args) {
    URI url = URI.create("http://localhost:8000/");
    DynamoDbClient ddb = AlternatorClient.builder(url.getScheme(), url.getHost(), url.getPort())
                                         .credentialsProvider(DefaultCredentialsProvider.create())
                                         .build();

    for (int i=0; i<10; i++) {
      DescribeEndpointsRequest request = DescribeEndpointsRequest.builder().build();
      DescribeEndpointsResponse response = ddb.describeEndpoints(request);
      System.out.println(response);
    }
  }
}

Java 17 was used.
The error is:
[main] WARN com.scylladb.alternator.AlternatorApacheClient - SSL Certificate verification is disabled. This is not a safe setting and should only be used for testing.
Apr 11, 2024 1:57:04 PM com.scylladb.alternator.AlternatorLiveNodes run
INFO: AlternatorLiveNodes thread starting
Exception in thread "main" java.lang.NullPointerException: Cannot invoke "software.amazon.awssdk.metrics.MetricCollector.reportMetric(software.amazon.awssdk.metrics.SdkMetric, Object)" because "metricCollector" is null
	at software.amazon.awssdk.http.apache.internal.conn.ClientConnectionRequestFactory$InstrumentedConnectionRequest.get(ClientConnectionRequestFactory.java:73)
	at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:190)
	at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
	at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
	at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
	at software.amazon.awssdk.http.apache.internal.impl.ApacheSdkHttpClient.execute(ApacheSdkHttpClient.java:72)
	at com.scylladb.alternator.AlternatorApacheClient.execute(AlternatorApacheClient.java:179)
	at com.scylladb.alternator.AlternatorApacheClient.access$200(AlternatorApacheClient.java:90)
	at com.scylladb.alternator.AlternatorApacheClient$1.call(AlternatorApacheClient.java:159)
	at com.scylladb.alternator.AlternatorApacheClient$1.call(AlternatorApacheClient.java:156)
	at software.amazon.awssdk.core.internal.util.MetricUtils.measureDurationUnsafe(MetricUtils.java:63)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.executeHttpRequest(MakeHttpRequestStage.java:77)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.execute(MakeHttpRequestStage.java:56)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.MakeHttpRequestStage.execute(MakeHttpRequestStage.java:39)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:73)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptTimeoutTrackingStage.execute(ApiCallAttemptTimeoutTrackingStage.java:42)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:78)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.TimeoutExceptionHandlingStage.execute(TimeoutExceptionHandlingStage.java:40)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:50)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallAttemptMetricCollectionStage.execute(ApiCallAttemptMetricCollectionStage.java:36)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:81)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.RetryableStage.execute(RetryableStage.java:36)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:56)
	at software.amazon.awssdk.core.internal.http.StreamManagingStage.execute(StreamManagingStage.java:36)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.executeWithTimer(ApiCallTimeoutTrackingStage.java:80)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:60)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallTimeoutTrackingStage.execute(ApiCallTimeoutTrackingStage.java:42)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallMetricCollectionStage.execute(ApiCallMetricCollectionStage.java:48)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ApiCallMetricCollectionStage.execute(ApiCallMetricCollectionStage.java:31)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.pipeline.RequestPipelineBuilder$ComposingRequestPipelineStage.execute(RequestPipelineBuilder.java:206)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ExecutionFailureExceptionReportingStage.execute(ExecutionFailureExceptionReportingStage.java:37)
	at software.amazon.awssdk.core.internal.http.pipeline.stages.ExecutionFailureExceptionReportingStage.execute(ExecutionFailureExceptionReportingStage.java:26)
	at software.amazon.awssdk.core.internal.http.AmazonSyncHttpClient$RequestExecutionBuilderImpl.execute(AmazonSyncHttpClient.java:193)
	at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.invoke(BaseSyncClientHandler.java:103)
	at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.doExecute(BaseSyncClientHandler.java:171)
	at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.lambda$execute$1(BaseSyncClientHandler.java:82)
	at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.measureApiCallSuccess(BaseSyncClientHandler.java:179)
	at software.amazon.awssdk.core.internal.handler.BaseSyncClientHandler.execute(BaseSyncClientHandler.java:76)
	at software.amazon.awssdk.core.client.handler.SdkSyncClientHandler.execute(SdkSyncClientHandler.java:45)
	at software.amazon.awssdk.awscore.client.handler.AwsSyncClientHandler.execute(AwsSyncClientHandler.java:56)
	at software.amazon.awssdk.services.dynamodb.DefaultDynamoDbClient.describeEndpoints(DefaultDynamoDbClient.java:1743)

I can reproduce this issue: Out of the box, our Demo2 demo still works (mvn exec:java -Dexec.mainClass=com.scylladb.alternator.test.Demo2 -Dexec.classpathScope=test, see the README.md), but this is because because our pom.xml fixed the SDK version at 2.15.46 - which works. But if the pom is updated to ask for SDK version 2.25.29 (as in the above report), I get a similar NullPointerException to what was reported above.

The cause of this issue is frustrating. The way we (Piotr Sarna) did the Java SDK 2 support was to basically copy and fork an internal SDK class ApacheHttpClient (our fork is AlternatorApacheClient). Not very suprisingly, the SDK's implementation of this class changed - they now have code that sets a new internal THREAD_LOCAL_REQUEST_METRIC_COLLECTOR for every request, and without it, the deeper level of the implementation (which we did NOT fork) failed, on that NullPointerException.
I could fix this problem by making a copy of the new ApacheHttpClient instead of the old one, but a better solution would not involve copying SDK code at all. I want to consider this approach version, and only if I fail, go back to copying code wholesale :-(

I found a much, much simpler solution: The Java SDK v2 has a new feature, DynamoDbEndpointProvider (https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/services/dynamodb/endpoints/DynamoDbEndpointProvider.html) - which seems to be called separately for every request and can return a different endpoint every time.  A quick test showed this actually works! I need to do more testing to verifies it really does work correctly, but it seems very promising - it's simplifies everything, doesn't duplicate and SDK code, and even simpler than the other new SDK v2 feature that I wanted to use - ExecutionInterceptor - but is much more general (and I'll only need to consider it if EndpointProvider doesn't work).

By the way, I checked, and my fix uses a new API that was added in Java SDK 2.20, released in February 2023. This is also the version that broke the old, complicated, code. In theory we could have had code that supported both the old and the new versions of the SDK (both of them SDK v2, mind you), but I don't want to do this unless we absolutely must. I'm planning to send a PR that will only work on SDK 2.20 and above and drop the ugly support for the newer versions. I assume that customers can use a modern version of the SDK and won't stick to a 2 year old one. I hope I'm assuming right - if not we can always revert my patch...


VM with vdisk block size less than 4096, doesn't boot

Steps

create  vm with this vdisk
{
"id": "vdisk6",
"size": 15,
"blocksize": 1024,
"type": "boot",
"templatevdisk": "ardb:///template:ubuntu-1604",
"blockStoragecluster": "st"
}
check vm status , will be running
try to login to vm , vm will not boot

Issue
If size doesn't enough for  template,should be prevented from beginnig

The problem here is not the block size. 1024 is a power of 2 and greater than 512, so that isn't what is stopping you.
The error here is the property templatevdisk is wrong. The property is named templateVdiskID. See https://github.com/zero-os/0-Disk/blob/master/docs/config.md#VdiskStaticConfig for more information (docs are pretty useful).
I suppose you don't get an error from this at startup as templatevdisk won't be recognized and thus just ignored. Sadly because the fact that 0-Orchestrator also adds unknown properties on purpose to the ETCD 0-Disk configs, we cannot unmarshal in strict mode. If we could this would also be an error we can detect at startup time.
However while there is no error on runtime, if you would run the nbdserver using the verbose (-v) flag, you should see logged debug lines containing content such as: content not available in primary storage for vdisk6 and no template storage available: ..., which should make you think that the problem is really with the template storage.
Either way, as we cannot do strict unmarshalling, it is even more important you read and know the config docs very well.

I believe this issue is due to we populated the ubuntu template in hub.gig.tech using 4096 blocksize, and you specified 1024  when creating it. I will block this issue on https://github.com/zero-os/0-orchestrator/issues/1005 since it proposes a fix for that conflict

This issue is outdated since an export of a vdisk now also writes this kind of metadata in the export to the ftp server. Also the zero-ctl command does accept the blocksize parameter anymore.


Remove path in command block

By removing the path in the command block, this helps users to easily copy + paste with builtin copy button. Using the copy button as-is copies the path in the example.

Docs Build status updates of commit 947a29f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-conceptual/azureadps-2.0/install-adv2.md
:warning:Warning

Details

docs-conceptual/azureadps-2.0/install-adv2.md

[Warning] Missing attribute: title. Add a title string to show in search engine results.
Line 25: [Warning] Link 'https://docs.microsoft.com/en-us/powershell/azure/active-directory/ad-pshell-v2-version-history' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 47: [Warning] Link 'http://go.microsoft.com/fwlink/?LinkID=624830&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 48: [Warning] Link 'http://go.microsoft.com/fwlink/?LinkId=398175' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 49: [Warning] Link 'http://go.microsoft.com/fwlink/?LinkID=746217&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 51: [Warning] Link 'http://go.microsoft.com/fwlink/?LinkID=760387&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 53: [Warning] Link 'http://go.microsoft.com/fwlink/?LinkID=760387&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 53: [Warning] Link 'http://go.microsoft.com/fwlink/?LinkID=760387&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 54: [Warning] Link 'http://go.microsoft.com/fwlink/?LinkID=760387&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 54: [Warning] Link 'http://go.microsoft.com/fwlink/?LinkID=760387&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 55: [Warning] Link 'http://go.microsoft.com/fwlink/?LinkID=760387&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 55: [Warning] Link 'http://go.microsoft.com/fwlink/?LinkID=760387&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 56: [Warning] Link 'http://go.microsoft.com/fwlink/?LinkID=760387&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 56: [Warning] Link 'http://go.microsoft.com/fwlink/?LinkID=760387&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 57: [Warning] Link 'http://go.microsoft.com/fwlink/?LinkID=760387&clcid=0x409' is insecure. Links to Microsoft sites must use 'https' instead of 'http'.
Line 73: [Warning] Link 'https://msdn.microsoft.com/en-us/library/5a4x27ek.aspx' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 133: [Warning] Link 'https://msdn.microsoft.com/en-us/powershell/scripting/getting-started/getting-started-with-windows-powershell' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Closing and re-opening for validation

Docs Build status updates of commit 947a29f:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azureadps-2.0/install-adv2.md
:bulb:Suggestion

Details

docs-conceptual/azureadps-2.0/install-adv2.md

Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


remove not frequently used CLI parameters

Parpare for making full use of toml based config file.
Signed-off-by: Changwei Ge<EMAIL_ADDRESS>

Codecov Report
Base: 30.50% // Head: 30.57% // Increases project coverage by +0.07% :tada:

Coverage data is based on head (46b4514) compared to base (c84085c).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #321      +/-   ##
==========================================
+ Coverage   30.50%   30.57%   +0.07%
==========================================
  Files          37       37
  Lines        3800     3800
==========================================
+ Hits         1159     1162       +3
+ Misses       2520     2517       -3
  Partials      121      121

Impacted Files
Coverage Δ

pkg/blob/blob_manager.go
32.65% <0.00%> (+3.06%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


support for Cyclone V SoC Development Kit

Adding support for Cyclone V SoC Development Kit

@mevalver  please follow the project guidelines: https://docs.zephyrproject.org/latest/contribute/guidelines.html#commit-guidelines


Introspection API for components of the same application

Say you're writing a multi-component application, and wish to send a request from component A to component B.
The issue here is that when writing the multiple components, there is no way of precisely knowing the application base path, nor the route a component will be configured for.
Which leaves the task of sending a request from component A to component B of the same Spin application unclear.
We could choose to expose an introspection API (or some methods on a context object) that would optionally return the different components of an application and the URL they can be reached at.

Is this still something that we want to see happen? Does it still make sense given the current focus on composition and recently added self feature?

I think the "self" feature covers the main request here. There are probably other introspectiony things that might be nice but we'd probably be better off working from more focused use cases.


Add "last seen at" in titlebar

When the chat is offline, show a last-seen-at indicator (WhatsApp-style) to communicate to the user that the bot is unreachable. We should save and update this value in localStorage

Add in PR #39


[W5.7][W14-1]Lee Zhuo Xun

noted. i saw that the listing of person in address book is immutable thus i thought that any listing is immutable.


Compatible Drawer Builders?

This library does not provide the user with drawer builders. What drawer builders would you suggest or are compatible with this library? Would you suggest just building your own using RecyclerView? Thank you!

The only drawer builder I've ever used is MaterialDrawer and it is an awesome library. AFAIK it has a method to get drawer as a View and not to inject it, so I'm pretty sure you can combine it with SlidingRootNav.

@yarolegovich Thanks for the quick response! I have come across MaterialDrawer before and thought it was too complex haha.  Thank you so much for not bundling your own drawer implementation and providing essentially a blank canvas to work with. I am going to develop my own drawer layout with some pretty extreme customizations.
I'm thinking about a large profile picture surrounded with particles from https://github.com/Doctoror/ParticlesDrawable
And then maybe a background with procedurally generated triangles from https://github.com/Oyzuu/PatternPlaceholder-Android
The possibilities are endless!

Cool libraries.
I thought that if a developer uses my library, the design will probably be unusual and it will be extremely hard to provide a flexible enough builder to satisfy all the possible customizations.

God bless this library! This is amazing:
![Sliding Nav Menu Particles]
(https://cloud.githubusercontent.com/assets/19896174/25930046/6f2fbf1e-35c9-11e7-83c9-ea9a6194ee37.gif)
The particles make a really nice background! The way they ooze onto the screen from the edges is so zen.
For anyone who wishes to make this effect, just use a frame layout for the menu_left_drawer.xml, Also, the particles effect uses around 20% CPU on the Snapdragon 820 and drains a bit of battery. Set the particle view visibility to GONE when the slide drawer is not open to save battery!

Posted on MaterialUp:
https://material.uplabs.com/posts/particle-navigation-drawer-interface


Fix build issue on macOS in github.com/docker/docker/pkg/term

Why
The current version of github.com/docker/docker/pkg/term is affected by a build issue on Darwin. This occurs when a Go module depends on a version of golang.org/x/sys more recent than 6fcdbc0, see https://github.com/moby/term/issues/15.
Let's enable consumers of this module to build on Darwin with the latest version of golang.org/x/sys by updating the dependency.
What

[x] Update dependencies to use latest version of github.com/moby/term package. This requires upgrading the version of github.com/moby/moby to at least v20.10.0-beta1, which includes 8312004.
[ ] Ensure make test succeeds.
[ ] Run tests in CI.

Notes:

github.com/docker/docker was renamed to github.com/moby/moby.
github.com/docker/docker/pkg/term is deprecated. Use github.com/moby/term instead.
The build issue was fixed by https://github.com/moby/term/pull/16.
github.com/moby/moby removed usages of the deprecated github.com/docker/docker/pkg/term package in 8312004.

Upgrading moby/moby from v17.x -> v20.x is not trivial. Closing in favour of removing the dependency on this unmaintained package.
A workaround for consumers of this package is to pin golang/x/sys to the commit before the constants were removed: https://github.com/moby/term/issues/15#issuecomment-684865946.


The power of singular nouns (discussion)

I am a firm proponent of using singular nouns throughout my application.  This prevents nonsense words like mooses and I believe it is easier for non-native english speaking developers.
What this means for this project is I want to change all plural nouns in the directory structure to singular.  Such as

app

core

guard
interceptor
service

layout
module
shared (not shareds)

This repository is used by a LOT of developers as the source of truth.  I believe this change will benefit them all.  It adds clarity and removes disambiguation.   Please comment.

Well. There are some great benefits of using singular nouns to describe the overall directory structure, but what really matters to me is that we're consistent throughout the application when going with the one or the other. What I've seen from other enterprise apps is a good combination between the two, and I can see this leading to confusion for new developers. I'm open for PR(s) here.

First off, thank you so much for your openness to my ideas.  I've only been programming 30ish years so what do I know :)  Thanks for your acceptance.
Today I'll create a PR with singular names for the directory structure.  I will not try to modify the code to use singular names.  That is a whole other debate.  So for now I'm happy that we can just change the directory names.

I'm always open to good ideas that directs this beginner project in the right direction. There's a lot of debatable issues regarding an application-structure, and there is no blueprint here. This repo should help developers by giving them an indication of a scalable structure, in order for them to figure what best suite their use-case.
Looking forward to see the changes. Thanks.

+1 revert to plurals in line with angular norms.


Ability to redirect stdout and stderr (tee program output)

Functionality is available in PTVSD (https://github.com/Microsoft/ptvsd/issues/60)
Needs a PR in extension

Closed, fixed in #875


Tidy up

Tidying up in the test suite.

We can write synchronous tests because when loading from VFS application boot-up happens
synchronously (even if it is call asynchronously).
Introducing FindAndReplace test

Codecov Report

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

@@            Coverage Diff             @@
##           master     #728      +/-   ##
==========================================
+ Coverage   64.99%   65.37%   +0.38%
==========================================
  Files         289      289
  Lines        7518     7518
==========================================
+ Hits         4886     4915      +29
+ Misses       2632     2603      -29

Impacted Files
Coverage Δ

src/TextureWebApp.js
0% <0%> (-16.67%)
:arrow_down:

src/TextureWebAppChrome.js
35.71% <0%> (-14.29%)
:arrow_down:

src/article/shared/nodeHelpers.js
88.88% <0%> (-11.12%)
:arrow_down:

src/article/shared/TableComponent.js
70.2% <0%> (-0.41%)
:arrow_down:

src/article/shared/AuthorsListComponent.js
82.6% <0%> (+8.69%)
:arrow_up:

src/article/shared/ReferenceListComponent.js
100% <0%> (+10.52%)
:arrow_up:

src/article/shared/FootnoteGroupComponent.js
100% <0%> (+11.11%)
:arrow_up:

src/kit/app/FindAndReplaceManager.js
22.72% <0%> (+12.98%)
:arrow_up:

src/kit/app/FindAndReplaceDialog.js
56.66% <0%> (+13.33%)
:arrow_up:

Continue to review full report at Codecov.

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


refactor: Fix and simplify benchmark processing notebook

Should help https://github.com/qdrant/vector-db-benchmark/issues/104#issuecomment-2057970146

lgtm, I ran the notebook against qdrant-rps-m16-ef128-glove-100-angular, works fine


kie-issues#1178: On the DMN Editor's Boxed Expression Editor, FEEL identifiers with spaces should be treated as non-breaking spaces.

Closes: https://github.com/apache/incubator-kie-issues/issues/1178
I found another edge case that is also fixed in this PR:

The other cases fixed are shown in the video below:
https://github.com/user-attachments/assets/608920b8-35c7-4724-9134-f61fe3a732b7
I also added more comments to the code, to make it easier to understand what is happening.
Sorry for the Portuguese in the pictures. Consider it as random chars to test the issues.
UPDATE: I'm attaching a file that shows the issues fixed if someone wants to use it to test it. About the other issue, reported in this comment here, you can test it with the "Loan Pre Qualification" example in Storybook or Online editor.
kie1178-english.dmn.txt

P.S.: we NEED to add test coverage to this feature asap.

I found a new issue, which will also be fixed with this PR, regarding line breaks. This issue happens only in some browsers and is related to the line ending (if it is *nix or Windows style). See in the video below a comparison between the broken behavior and the new one, @tiagobento
https://github.com/user-attachments/assets/147e966f-0c05-4680-a5dd-6aa90857a8bd
The fix has not been pushed in the PR yet, it will come with the new unity tests.

Changes applied! The issue about breaking lines, reported in the video above, it is also fixed.
I had to do some refactoring to make it easier to test and to organize the code. I'm testing only the SemanticTokensProvider that is what "translates" the parser result to the Monaco.
Let me know if the Jest tests are ok with our standards. I didn't found any case similar to this one in our codebase to compare. @tiagobento @ljmotta

@tiagobento Changes applied! Now the test is testing all the stack, from feel-input-component to the dmn-feel-antlr4-parser.

@tiagobento New tests integrated!

@tiagobento Ready to merge.


Cannot buy paid content in latest release

In the latest release (0.35.4) I cannot buy paid content. I don't get the confirm purchase dialog box. The waiting animation just plays indefinitely. If this is confirmed it should be fixed ASAP as some people are making quite good use of paid content (e.g., Efe Aydal has 1631 views in just a few weeks, all of paid content).

Confirmed 😞
Will release a fix shortly. Thank you for reporting!

I'm just glad we caught it early.

Trying your latest RC and it's working. :-)

Great. Thanks again


Improve examples of using packit-service locally

I confirm that your approach works and I think we can actually remove the binding on other hosts section to keep the description as simple as possible.

Do you think that we can move the description of the flask behaviour and configuration elsewhere? I think they can be handy when setting up a network with no binds to localhost?


找不到offb/obj.h

/home/nvidia/AUTO/src/AUTO-master/offb/src/camera.cpp:14:10: fatal error: offb/obj.h: 没有那个文件或目录
#include "offb/obj.h"
^~~~~~~~~~~~
compilation terminated.
AUTO-master/offb/CMakeFiles/camera.dir/build.make:62: recipe for target 'AUTO-master/offb/CMakeFiles/camera.dir/src/camera.cpp.o' failed
make[2]: *** [AUTO-master/offb/CMakeFiles/camera.dir/src/camera.cpp.o] Error 1
CMakeFiles/Makefile2:1874: recipe for target 'AUTO-master/offb/CMakeFiles/camera.dir/all' failed
make[1]: *** [AUTO-master/offb/CMakeFiles/camera.dir/all] Error 2
make[1]: *** 正在等待未完成的任务....

may I ask which version of ubuntu are you using?
make sure that the msg file including obj.msg is in the directory
you can also check CMakelists.txt as well as package.xml for message_generation-related lines, whether they are all properly placed.

yes,CMakelists.txt and package.xml doesn't contain message_generation-related lines, like "message_generation" from find_package, and" message_generation message_runtime" in catkin_package, so obj.h doesn't been generated.
And after that, when I rosrun offb camera and offb track , I find  "mydnn.forward(netOutput, net_outputNames);" from run_yolo.cpp can't generate output  "netOutput" so that object like human cannot be detected.
net_outputNames contain"yolo_30 and yolo_37" in yolo_tiny has been affirmed.

result like this:
480 x 640
affirm whether been here : *****************01
names:yolo_30
names:yolo_37
time:0.581299
fps: 1.72028
affirm whether been here : *****************03
output structure: [8 x 1083]
affirm whether been here : *****************03
output structure: [8 x 4332]
fps: 1.6777
fps_avg: 1.5862
temp size: 0
ms: 0.596512
notFoundCount:19
show predict
object: 0
X_c: 0
Y_c: 0
Z_c: 0
480 x 640
affirm whether been here : *****************01
names:yolo_30
names:yolo_37
^Ctime:0.600099
fps: 1.66639
affirm whether been here : *****************03
output structure: [8 x 1083]
affirm whether been here : *****************03
output structure: [8 x 4332]
fps: 1.62726
fps_avg: 1.58826
temp size: 0
ms: 0.614944
notFoundCount:20
show predict
object: 0
X_c: 0
Y_c: 0
Z_c: 0

I've just tried it out, and the code should not be a problem. But please do make sure you have the correct version of opencv, the right path to cfg file and weight file


Yii2 swift mailer logic chain with embed images

Hey there.
I find it hard to figure out how to embed content such as images to mail messages created with Yii2 wrapper for Swift Mailer:
Yii::$app->mail->compose('email-template', [param => ...])
<EMAIL_ADDRESS>    ->setTo($form->email)
    ->setSubject($form->subject)
    ->send();

Swift Mailer uses Swift_Message::embed() to embed an image and return its CID to be used in a template. But we can't use it in arguments to compose() as no Swift_Message instance was created yet. If we use compose() with no arguments, we get Swift_Message back, but then we lose the ability to render body with views - we can only assign a body as a string.
I guess we could use $this::embed() inside the view itself, but this kind of against views logic which is not the best way to contain anything apart from presentation layout.
Swift mailer bases on a separate creation of Swift_Message instance which allows embedding of content easily, but with Yii2 I didn't find anything in the docs that could separate embedding and presentation layers in email messages.
Is there a miss in Yii2 swift mailer wrapper functionality or did I miss something obvious? I used PHPMailer before a lot, and there you can pass a literal to embed() function which you can use in a view layout later easily. Swift mailer is different in this regard.

For me $message is undefined. So I use
<img src="<?= Swift_Message::embed($imageFileName); ?>">
instead.


Fix broken links on documentation

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


Add travis logo to README badge

While reading through your docs tonight, I noticed that the first two badges in the main README are indistinguishable visually:

Would you consider this small PR to add the Travis logo to the Travis badge?

Thanks!


Consider moving no-std/alloc error stuff from internals to a new stable crate

Context: I'm preparing a presentation about error handling in Rust and it looks like a crate containing write_err! and input_string would make sense. In a way it increases our maintenance burden but it also makes some things easier by allowing us to have InputString in public API. It's also so trivial that it could be stabilized ~immediately which could give us more experience with the process. (BTW I have a recent experienced: yesterday I've stabilized my first crate! Also see MSRV section for some fun.)
To be clear: this doesn't propose to move all error stuff, in particular, it won't move the ParseIntError which is unrelated to no-std support.

Yeah, agreed. This is a pretty common need across our ecosystem and would give us some experience stabilizing crates. And it would be nice to see some 1.0s.


Remove version: Nikkho.FileOptimizer version <IP_ADDRESS>

[Automated] It returns code over 400 in all urls
Microsoft Reviewers: Open in CodeFlow

URL: https://sourceforge.net/projects/nikkhokkho/files/FileOptimizer/15.80.2721/FileOptimizerSetup.exe/download
Status Code: 200
(Automated message - build 896)

Close with reason: Package still available.;


Updating status doesn't change main page icon

If I update the status via API or even mannually, despite the status internally(DB) is right.
The status changes on the front page does not update, one workaround is to set the status of another service manually that refreshes the main page.
Alredy played with some cache options but had no luck.

+1


vertical scrolling stuck when the scrollbar-content is forced shifted

I have implemented scrollbar inside the jquery selectmenu widget and on dropdown open I am forcing the scrollbar to move to the position of the selected menuitem. But when I try to scroll top whithout initially scrolling down the scrollbar does not work on wheel movement. But when scrolled down and then scrolled up using mouse wheel, the scrollbar moves up.
Any remedy would appreciate

How do you force scrollbar position? Do you use scrollTop ?

yes used scrollTop

Did you find out how to fix it? If no, prepare example on jsFiddle.net and I will try to help you


Add docker to CI

Codecov Report

Merging #11 (b31d821) into master (775cb66) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #11   +/-   ##
=======================================
  Coverage   80.17%   80.17%
=======================================
  Files          23       23
  Lines        1170     1170
=======================================
  Hits          938      938
  Misses        141      141
  Partials       91       91

Continue to review full report at Codecov.

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


Kubernetes Scheduler: use distinct names for Scheduling Policies and Scheduling Policies

https://kubernetes.io/docs/concepts/scheduling-eviction/kube-scheduler/#kube-scheduler-implementation says:
There are two supported ways to configure the filtering and scoring behavior of the scheduler:
1. Scheduling Policies allow you to configure to...
2. Scheduling Policies allow you to configure to...

Where Scheduling Policies are hyper links, pointing to different locations.
If there are two ways to achieve something, the names of the ways must be distinct.

Hi @dilyanpalauzov, I think you misread the paragraph. It is written as Scheduling Policies and Scheduling Profiles.

I agree.


Is this project still live?

We are considering using this project to stream calls to Google for real-time call transcription (while a person is still talking), and would like to know if the project is still live and supported? Is it compatible with any Asterisk versions after 16? Thanks in advance!

Hi David,
It hasn’t been touched recently so could definitely do with a bit of work
to update things but it should work with newer Asterisk versions no problem.
Dan
Dan Jenkins
Founder @ Nimble Ape / Everycast Labs / CommCon
Nimble Ape: nimblea.pe
Everycast Labs: everycastlabs.uk // broadcastbridge.app
CommCon: commcon.xyz
On Thu, 9 May 2024 at 03:47, David Cunningham @.***>
wrote:

We are considering using this project to stream calls to Google for
real-time call transcription (while a person is still talking), and would
like to know if the project is still live and supported? Is it compatible
with any Asterisk versions after 16? Thanks in advance!
—
Reply to this email directly, view it on GitHub
https://github.com/nimbleape/dana-tsg-rtp-stt-audioserver/issues/20, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAB3LLMHU7WW7P2A22HCNF3ZBLPVFAVCNFSM6AAAAABHOBJAB6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGI4DMNZYHEYDSNI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you Dan.


Document internal functions.

On a separate perfectionist note, we have also documented our internal functions in iSEE. You'll see that we've given then @rdname prefixed with INTERNAL_*  and that we've added that pattern to our .gitignore so that those pages only show up on our developers computers, not in the main documentation.
Internal documentation proved useful more than once given the shear size of iSEE and the need for coordination between four remote developers (including our own future selves).

This is a good idea.

Closed by #17.


Register background activities

Contents
Registers a background activity with the system during the delay countdown and auto click phases of execution.
The activity is registered as .userInitiated, which prevents system throttling of the application.
When the app returns to its idle state the activity tokens are released, and the system is once again allowed to throttle the app to conserve resources.
Background
When the app window is not visible to the user the system considers the app eligible for app nap.
App nap will, among other things, throttle the active timers of the app. This can cause automatic clicks to not occur with the expected frequency.
The degree to which the app is throttled is determined by the OS, and is more notable on systems with lower performance characteristics.
On a 2016 Intel MacBook Pro I observed a significant slowdown of a 1 CPS run after about a minute of the app being off screen, with clicks occurring about once every 3-5 seconds instead of every second.
Testing
Manual testing only, since app nap is not easily testable.
The "Energy" tab of the Activity Monitor app will indicate whether the app is currently in app nap, or is currently preventing system sleep.
Obscuring the app's window and observing the properties displayed in Activity Monitor will confirm that the app no longer enters the app nap state during an active run.

Thank you for your contributions and the PR! I would have never have thought about this occuring. I'll have a look and merge later today and push out a new v1.3.1 build.


Chapter sort issue with large volume/chapter counts

When I imported a manwha with 500+ chapters, the sorting ordered them as follows:
1
10
100
101-109
11
110-119
12
etc. etc.
Would it be possible to have them listed in the proper order without having to prepend zeroes into the names?

This is the expected behavior when sorting by filename. It would be unreliable if Mango has to parse numbers from the filenames. For example, a filename might contain both volume and chapter numbers (e.g., One-Punch Man Vol.02 Ch.120). Sometimes people might have files with non-English filenames ,so parsing the number proceeding Ch. might also fail.
How do you think Mango should handle this?

I have been thinking about this, and one way to handle the problem to add an "intelligent sorter" to the list of sorting options. The intelligent sorter would attempt to parse the filenames to fetch the chapter/volume numbers and sort the files accordingly, and when it fails it can simply fall back to use the default filename sorting.
I will try to include this in the next release.

This is added in v0.2.0. The default sorting option for chapters is "Auto", which sorts files in the way you described.

Auto sort is working! My manwha displays correctly (after renaming the files as Volumes, as opposed to their original naming as Episodes).
Thank you for your hard work!


Update moon.mod.json

gmlewis/jsonutil is not available in deps, please fix it.

Did you run moon update && moon install ?
Here is the package: https://mooncakes.io/docs/#/gmlewis/jsonutil/ and I'm not seeing any errors.
I just ran this myself, and got:
$ cat moon.mod.json
{
  "name": "gmlewis/moonbit-pdk",
  "version": "0.34.0",
  "deps": {
    "gmlewis/jsonutil": "0.22.0"
  },
  "readme": "README.md",
  "repository": "https://github.com/gmlewis/moonbit-pdk",
  "license": "Apache-2.0",
  "keywords": [
    "extism",
    "pdk",
    "moonbit"
  ],
  "description": "Extism MoonBit PDK: This library can be used to write Extism Plug-ins in MoonBit."
}

$ moon update && moon install
From https://mooncakes.io/git/index
 * branch            main       -> FETCH_HEAD
Already up to date.
Registry index updated successfully

Can you please share the error message you are getting?

I'm using this version:
$ moon version --all
moon 0.1.20240816 (6614fd3 2024-08-16) ~/.moon/bin/moon
moonc v0.1.20240819+fecaf8ce0 ~/.moon/bin/moonc
moonrun 0.1.20240814 (c6a4947 2024-08-14) ~/.moon/bin/moonrun

Even if gmlewis/jsonutil were not available, which is not the case, this PR makes no sense to me.
Closing.

https://github.com/gmlewis/moonbit-libs/jsonutil in mooncakes.io is not accessible, you can try it. I can only get the jsonutil v0.22 in mooncakes, but the latest jsonutil(v0.34) in github is Page Not Found. I just want to get jsonutil v0.34, as the v0.22 cannot match the latest pdk, there are errors about json while building. Please run pdk from scratch, you will understand that.

That's a mooncakes.io bug - here's what you are looking for:
https://github.com/gmlewis/moonbit-libs/tree/gmlewis-master/jsonutil

The latest moonbit-pdk runs fine for me from scratch:
$ cat moon.mod.json
{
  "name": "gmlewis/moonbit-pdk",
  "version": "0.34.0",
  "deps": {
    "gmlewis/jsonutil": "0.22.0"
  },
  "readme": "README.md",
  "repository": "https://github.com/gmlewis/moonbit-pdk",
  "license": "Apache-2.0",
  "keywords": [
    "extism",
    "pdk",
    "moonbit"
  ],
  "description": "Extism MoonBit PDK: This library can be used to write Extism Plug-ins in MoonBit."
}

$ rm -rf target
$ ./build.sh
+ moon fmt
+ moon build --target wasm
Finished. moon: ran 17 tasks, now up to date
+ moon test
Total tests: 2, passed: 2, failed: 0.

$ ./run.sh
+ extism call target/wasm/release/build/examples/greet/greet.wasm greet --wasi --input Benjamin
Hello, Benjamin!

+ extism call target/wasm/release/build/examples/count-vowels/count-vowels.wasm count_vowels --wasi --input 'Once upon a dream'
{"count":7,"total":7,"vowels":"aeiouAEIOU"}

+ extism call target/wasm/release/build/examples/http-get/http-get.wasm http_get --wasi '--allow-host=*.typicode.com'
{
  "userId": 1,
  "id": 1,
  "title": "delectus aut autem",
  "completed": false
}

+ extism call target/wasm/release/build/examples/kitchen-sink/kitchen-sink.wasm kitchen_sink --wasi --allow-host=extism.org --input 'Testing the kitchen sink'
Testing the kitchen sink

+ extism call target/wasm/release/build/examples/arrays/arrays.wasm progressive_sum_ints --wasi --input '[0,1,2,3,4,5,6]'
[0,1,3,6,10,15,21]

+ extism call target/wasm/release/build/examples/arrays/arrays.wasm progressive_sum_floats --wasi --input '[0,0.1,0.2,0.3,0.4,0.5,0.6]'
[0,0.1,0.30000000000000004,0.6000000000000001,1,1.5,2.1]

+ extism call target/wasm/release/build/examples/arrays/arrays.wasm progressive_concat_strings --wasi --input '["0","1","2","3","4","5","6"]'
["0","0|1","0|1|2","0|1|2|3","0|1|2|3|4","0|1|2|3|4|5","0|1|2|3|4|5|6"]

+ extism call target/wasm/release/build/examples/arrays/arrays.wasm all_three_object --wasi --input '{"ints":[0,1,2,3,4,5,6],"floats":[0,0.1,0.2,0.3,0.4,0.5,0.6],"strings":["0","1","2","3","4","5","6"]}'
{"ints":[0,1,3,6,10,15,21],"floats":[0,0.1,0.30000000000000004,0.6000000000000001,1,1.5,2.1],"strings":["0","0|1","0|1|2","0|1|2|3","0|1|2|3|4","0|1|2|3|4|5","0|1|2|3|4|5|6"]}

$ moon version --all
moon 0.1.20240816 (6614fd3 2024-08-16) ~/.moon/bin/moon
moonc v0.1.20240819+fecaf8ce0 ~/.moon/bin/moonc
moonrun 0.1.20240814 (c6a4947 2024-08-14) ~/.moon/bin/moonrun

I see the problem now.  The mooncakes.io site is out-of-date.
I'll ask @zshipko on Discord to perform a moon publish, and that should remove all confusion.
If this ever happens in the future, please first check the gmlewis/moonbit-pdk version and compare it against the extism/moonbit-pdk version - they SHOULD BE identical.  If they are not, please simply ask for a moon publish in this repo.


Injection model issues

session.setup.models.discrete_phase.general_settings.interaction.option = "coupled"
session.setup.models.discrete_phase.injections.create("spray_nozzle")
session.setup.models.discrete_phase.injections["spray_nozzle"].injection_type.option = "pressure-swirl-atomizer"
session.setup.models.discrete_phase.injections["spray_nozzle"].particle_type = "inert"

doesn't update init_props state.
There are 2 issues:

The initial_props state in settings API is updated only if the injection panel is kept open in Fluent.
The injection commands aren't available at TUI for PyFluent.

I'm having the same issue so would love to see this being worked on. In my case:
solver.setup.models.discrete_phase.injections.create("injection-1")  solver.setup.models.discrete_phase.injections["injection-1"].injection_type.option = "surface"  pprint(solver.setup.models.discrete_phase.injections["injection-1"].initial_props())
returns
{'diameter': {'option': 'uniform'}, 'flow_rate': {'flow_rate': 1e-20}, 'location': {'random_surface_inj': False, 'x': 0, 'y': 0, 'z': 0}, 'velocity': {'use_face_normal_direction': False}}
while it should have updated to something like
{'diameter': {'diameter': 0.0001, 'option': 'uniform'},  'flow_rate': {'scale_by_area': False, 'total_flow_rate': 1e-20},  'location': {'injection_surfaces': [],               'random_surface_inj': False},  'velocity': {'use_face_normal_direction': False,               'x_velocity': 0,               'y_velocity': 0,               'z_velocity': 0}}

@mkundu1 @antonpersson-ba I'm not able to reproduce this with the current 24R1 build. (initial_values now)
@mkundu1 any outstanding issues?


ERROR: Unknown instruction: COMPOSER

Just clean installation:
$ git clone https://github.com/LaraDock/laradock.git
Cloning into 'laradock'...
$ cd laradock/
$ docker-compose up -d php-fpm
Creating network "laradock_default" with the default driver
Building workspace
ERROR: Unknown instruction: COMPOSER
$ uname -a
Linux vip 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
$ docker-compose -v
docker-compose version 1.9.0, build 2585387
$ docker -v
Docker version 1.13.0-rc1, build 75fd88b

well, i think that this is just docker's bug
if i remove all the comments from Dockerfiles than i can install php-fpm and other images but in any case nginx and php-fpm containers are out of service (i can't do smth like docker-compose exec nginx bash, i don't see any opened docker's proxy listener on host machine etc )
imo this is ubuntu 16.10 and docker 1.13 specific, so i'll continue to watch this issue, may be i'll be solved soon

interesting but after downgrading to docker 1.12 (Ubuntu 10.04 now) the previous problem still exists:
$ docker-compose ps
         Name                Command       State           Ports
------------------------------------------------------------------------
laradock_applications_1   /true           Exit 0
laradock_nginx_1          nginx           Exit 1
laradock_php-fpm_1        php-fpm         Exit 78
laradock_workspace_1      /sbin/my_init   Up        <IP_ADDRESS>:2222->22/tcp

php-fpm just can't be started at all and i can't see any logs from it.
is anyone able to reproduce the full installation sequence of the laradock with the latest images ?
possible this is a subject for a new issue

@mxswar What did you end up doing to make this work?

Same here with Docker version 1.13.0-rc2, build 1f9b3ef

@mxswar Like you pointed out this is a known Docker issue (https://github.com/docker/docker/issues/29005). Hopefully this will be resolved soon...

@mxswar @abbert Fixed it by downgrading to 1.12.3.

WOW I was just struggling with this one on a new project! Thanks! :)
I just ripped out all the comment lines embedded in run blocks for now. :)


Add contributor installation instructions

The motivation

As a potential contributor, I want to do a development installation. I couldn't find these instructions. I cloned the repository and naively ran
pip install -e .
Obtaining file:///home/bandela/src/cmip-ref/cmip-ref
  Installing build dependencies ... done
  Checking if build backend supports build_editable ... done
  Getting requirements to build editable ... error
  error: subprocess-exited-with-error

  × Getting requirements to build editable did not run successfully.
  │ exit code: 1
  ╰─> [14 lines of output]
      error: Multiple top-level packages discovered in a flat-layout: ['stubs', 'packages'].

      To avoid accidental inclusion of unwanted files or directories,
      setuptools will not proceed with this build.

      If you are trying to create a single distribution with multiple packages
      on purpose, you should not rely on automatic discovery.
      Instead, consider the following options:

      1. set up custom discovery (`find` directive with `include` or `exclude`)
      2. use a `src-layout`
      3. explicitly set `py_modules` or `packages` with a list of names

      To find more information, look for "package discovery" on setuptools docs.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× Getting requirements to build editable did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

which didn't work.
Then I went into the packages/ref directory and tried to install from there, but that didn't work either because it couldn't find the ref-core package. So then I went to the packages/ref-core directory, did pip install -e . there, and then backed up to the packages/ref directory and did a pip install -e . there, and now things seem to work. It would be nice if this process was a simpler, to avoid scaring potential contributors away.
The proposed solution

Add installation instructions for potential contributors
Alternatives

Additional context

Did you see the section at the bottom of the README? If not we should make it more prominent.

Thanks! I thought I'd seen uv mentioned somewhere, but I couldn't find it anymore. The places where I looked were CONTRIBUTING.md (does not exist) and https://cmip-ref.readthedocs.io/en/latest/development/ (only provides very generic information). I would suggest moving these instructions to the readthedocs page and linking them from CONTRIBUTING.md (and optionally from README.md). I can help with that if you like?

That would be great thanks


WIP - 01-04-54-post-iris-call-receive-headers / 01-04-55-post-iris-call-receive-header

first part refactor of 01-04-54-post-iris-call-receive-headers 01_04_54-post_iris_call_receive_headers.js

pipeline:run

pipeline:run

pipeline:run


net: Set Dummy net_if as default one for tests

If we run network tests under tests/net, then set the Dummy network interface as a default one so that it will be picked up first.
This should solve the issue if the DUT is having a real network interfaces like onboard Ethernet interface which could cause the test to fail. The test might fail in this case because the network tests assume that only simulated network interfaces are used by the tests.

@hakehuang please try this one if it solves the issues you see in https://github.com/zephyrproject-rtos/zephyr/issues/64062


Generate 3D structure from SMILES?

Hi, this is amazing work! I just have a question: Can this model generate a molecule's structure from an input SMILES? If so, is there any example code for how to do this?

Thank you for your interest and kind words! Yes, the model can indeed generate molecular structures from SMILES input. I'll provide a code example soon demonstrating how to accomplish this using the model.
Stay tuned!

Thanks! Looking forward to the example.

Hey @dizhou-wu! I've just committed a new file smiles_generation.py to the repository that demonstrates how to generate 3D structures from SMILES input.
You can generate a conformer by running:
python smiles_generation.py model.pt --smiles 'CC(C)(C(=O)NC(C))' --out_sdf output_conformer.sdf
This is a basic example, but it should give you a good foundation to build upon for other use cases. Keep in mind that you might need to adjust some parameters/code depending on your specific needs.


Bump several dependencies

coverage: 86.473%. remained the same
when pulling 584b082b4dad28ea8075b1b9f900cf935b0bcedc on deps/update
into 3a41aaefb24b7b6b8c25961c289b43af7c286083 on main.


Fix version number for npm

Apparently you have to have version number be three numbers divided by
dots. Otherwise npm thinks that package.json is not valid and won't
install dependencies.

Good catch! Are you installing directly from GitHub?

Yes, I wanted to make some changes to the theme and could not build it. Because npm couldn't install dependencies.

Oh whoops, guess that's something to remember for next time. Merci~


[bug] Double spaces

When I insert a double space in "  " in the editor and save and go back in the editors gets very buggy.
To recreate (using Chrome)

Create a new post
insert asdf asdf in the editor.
Save and close
Go back in. You can now select the text.
Insert one more space in between asdf and asdf
Save and close
Go back in and you cannot select the text, cursor just jumps to the end.

After some digging, it seems the issue lies with my fix for the i18n issue.
I keeps updating the content of the editor when it shouldn't.

This is fixed in version 0.8.1


Option to return only identifiers or different realizations of a catchment.

Would like to get back the json data without the geo part. Not sure what the API should look like for this, but seems like a simple thing to offer.

/ids
/atts

If we want to match the OGC API specification, it looks like these links would go into a links JSON array at the top level of the feature. http://opengeospatial.github.io/e-learning/ogcapi-features/text/operations.html#feature


Add a Gitter chat badge to readme.md

SAP/chevrotain now has a Chat Room on Gitter
@bd82 has just created a chat room. You can visit it here: https://gitter.im/chevrotain-parser/Lobby.
This pull-request adds this badge to your readme.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

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


Add validation for ij_dir_or_endpoint setting

This allows us to fall back to a reasonable default when an empty value is provided, and prevents the user from setting their configuration to a blank directory or endpoint.

Codecov Report
Base: 90.36% // Head: 90.45% // Increases project coverage by +0.08% :tada:

Coverage data is based on head (28e832f) compared to base (e32c8ee).
Patch coverage: 85.18% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #150      +/-   ##
==========================================
+ Coverage   90.36%   90.45%   +0.08%
==========================================
  Files          41       41
  Lines        3984     4011      +27
==========================================
+ Hits         3600     3628      +28
+ Misses        384      383       -1

Impacted Files
Coverage Δ

src/napari_imagej/widgets/menu.py
77.17% <ø> (+1.24%)
:arrow_up:

src/napari_imagej/__init__.py
73.68% <66.66%> (-1.32%)
:arrow_down:

tests/widgets/test_menu.py
81.36% <90.47%> (+0.79%)
:arrow_up:

src/napari_imagej/widgets/result_tree.py
91.50% <0.00%> (+1.88%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


mkcloud: explicitly catch broken DNS

we had a recent DNS failure resulting in mysterious calls of
wget --progress=dot:mega -N http:///images/x86_64/SP3-64up.qcow2
and this should give a clearer message to the user

+1

+1

+1

+1


Only try to dump diagnostics if you have diagnostics.

Only try to dump diagnostics if you have diagnostics.

I think this will still break if you have meanfields or if steady_state_dump_err is True. I made having diagnostics the default behaviour to avoid having if diagnostics is not None in several places, and also because it seems useful to have in general. We could make a basic minimal set of diagnostics in a base diagnostics class if you'd prefer that to setting diagnostics=None (there is only one diagnostic at present anyway!)

OK, then we need to actually make having diagnostics the default
behaviour. My example didn't execute!
On 5 May 2016 at 22:01, jshipton<EMAIL_ADDRESS>wrote:

I think this will still break if you have meanfields or if
steady_state_dump_err is True. I made having diagnostics the default
behaviour to avoid having if diagnostics is not None in several places,
and also because it seems useful to have in general. We could make a basic
minimal set of diagnostics in a base diagnostics class if you'd prefer that
to setting diagnostics=None (there is only one diagnostic at present
anyway!)
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/firedrakeproject/dcore/pull/35#issuecomment-217278733

--
http://www.imperial.ac.uk/people/colin.cotter
www.cambridge.org/9781107663916

Sorry, looks like I forgot to update all the examples files then. I was copying the way that the timestepping, output and parameters classes are set up in the setup file - i.e. you have to pass them in - but with diagnostics it does make sense to have a default class.

From: Colin J Cotter<EMAIL_ADDRESS>Sent: 05 May 2016 22:28:19
To: firedrakeproject/dcore
Cc: Shipton, Jemma; Comment
Subject: Re: [firedrakeproject/dcore] Only try to dump diagnostics if you have diagnostics. (#35)
OK, then we need to actually make having diagnostics the default
behaviour. My example didn't execute!
On 5 May 2016 at 22:01, jshipton<EMAIL_ADDRESS>wrote:

I think this will still break if you have meanfields or if
steady_state_dump_err is True. I made having diagnostics the default
behaviour to avoid having if diagnostics is not None in several places,
and also because it seems useful to have in general. We could make a basic
minimal set of diagnostics in a base diagnostics class if you'd prefer that
to setting diagnostics=None (there is only one diagnostic at present
anyway!)

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/firedrakeproject/dcore/pull/35#issuecomment-217278733

--
http://www.imperial.ac.uk/people/colin.cotter
www.cambridge.org/9781107663916

You are receiving this because you commented.
Reply to this email directly or view it on GitHubhttps://github.com/firedrakeproject/dcore/pull/35#issuecomment-217285350

Superseded but diagnostics_default.


Add DisableLengths for pairity with DisableCapacities

For test usage, the diff will already be included, so there's no need to
list the len.
This is pretty similar to https://github.com/davecgh/go-spew/pull/58 except length-only and includes tests.

The tests for go 1.6, 1.7, and 1.8 fail because the tests require gometalinter, which doesn't support those go versions.


Fixes temporal_model_AVID-CMA tests

Removing dash from file name to make it a valid python module, fixing import error

@YingtianDt

Thanks. I will avoid the dash in the future.


Change "10.10% - 19.65%APY" to "Projected APY ..." instead.

Sort of like Ribbon Finance

Is there a reason why you can't include the Max APY in the original USDC APY button?

Also the 10% fee should not be highlighted.

The requirements should be clarified.
Projected APY ...
where ... is max APY?

If so, the new title will look like
Projected APY 19.65%


Replace PCF references with cf-release

...since these are community docs that should apply to any downstream deployment, not just PCF.

Thank you, mogul