JNI error on application start

Hi,
After I added docusign to pom and installed the dependency I can't start my Vert.x application. It's throwing a JNI error.
<dependency>
     <groupId>com.docusign</groupId>
     <artifactId>docusign-esign-java</artifactId>
     <version>2.4.2</version>
   </dependency>

Then in the console:
mvn clean install
mvn clean package

start app:
java -jar target\eSignApi-1.0-SNAPSHOT-fat.jar

Results in this:
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.SecurityException: Invalid signature file digest for Manifest main attributes
        at sun.security.util.SignatureFileVerifier.processImpl(Unknown Source)
        at sun.security.util.SignatureFileVerifier.process(Unknown Source)
        at java.util.jar.JarVerifier.processEntry(Unknown Source)
        at java.util.jar.JarVerifier.update(Unknown Source)
        at java.util.jar.JarFile.initializeVerifier(Unknown Source)
        at java.util.jar.JarFile.getInputStream(Unknown Source)
        at sun.misc.URLClassPath$JarLoader$2.getInputStream(Unknown Source)
        at sun.misc.Resource.cachedInputStream(Unknown Source)
        at sun.misc.Resource.getByteBuffer(Unknown Source)
        at java.net.URLClassLoader.defineClass(Unknown Source)
        at java.net.URLClassLoader.access$100(Unknown Source)
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.net.URLClassLoader$1.run(Unknown Source)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
        at java.lang.ClassLoader.loadClass(Unknown Source)
        at sun.launcher.LauncherHelper.checkAndLoadMain(Unknown Source)

If i remove docusign dependency and rebuild: app will start normally.

Closing: assuming the problem has been solved by the OP.


Added new NowcastingSEIRModel and supporting tests, enabled incremental run on old model

This is mostly new code implementing a new kind of SEIR Model and supporting tests

Key features of the model

TODO describe model

Please Check

[ ] Are the JSON schemas updated?
[ ] Are the api docs updated?
[ ] Are tests passing?

I think in general just removing unused bits and adding documentation and doc strings would be awesome : ).


Remove db class and use db sessions directly

@RustyBower I finally got around to deleting the db class, and converting everything to use session.query directly.


monaco-editor error

When I run:
npm run start

I'm getting the following errors in the terminal:
ERROR in ./node_modules/monaco-editor/esm/vs/base/browser/ui/codiconLabel/codicon/codicon.ttf 1:0
Module parse failed: Unexpected character '' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file.

Hi buddy, thanks for filing an issue.
I used to see this error as well, but after cleaning up the project I don't see it anymore.
Can you please try to clean up all cached files to see if it reproduces, and let me know how it goes?
rm -rf node_modules
rm -rf package-lock.json
rm -rf yarn.lock
yarn cache clean

@ShimiSun Thank you for the reply and help with this. I just tried to follow the steps you provided to clean out the npm modules and cache, but I still got the same error. I'm running this on a Google Cloud Shell which is "ephemeral and no system-wide change will persist beyond session end" and it seemed that they have a slightly older version of Node LTS installed (6.4.1) so I upgrade to the latest LTS (6.13.4) version. However that is still giving me the following errors:
nrydevops@cloudshell:~/grommet-site (nrydevops)$ npm run start

><EMAIL_ADDRESS>start /home/nrydevops/grommet-site
> cross-env NODE_ENV=development webpack-dev-server --mode development --open

Error: Cannot find module 'monaco-editor/esm/vs/editor/contrib/gotoSymbol/goToCommands'
Require stack:
- /home/nrydevops/grommet-site/node_modules/monaco-editor-webpack-plugin/out/index.js
- /home/nrydevops/grommet-site/webpack.config.js
- /home/nrydevops/grommet-site/node_modules/webpack-cli/bin/utils/convert-argv.js
- /home/nrydevops/grommet-site/node_modules/webpack-dev-server/bin/webpack-dev-server.js
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:797:15)
    at Function.resolve (internal/modules/cjs/helpers.js:80:19)
    at resolveMonacoPath (/home/nrydevops/grommet-site/node_modules/monaco-editor-webpack-plugin/out/index.js:26:20)
    at /home/nrydevops/grommet-site/node_modules/monaco-editor-webpack-plugin/out/index.js:161:63
    at Array.map (<anonymous>)
    at createLoaderRules (/home/nrydevops/grommet-site/node_modules/monaco-editor-webpack-plugin/out/index.js:161:43)
    at MonacoEditorWebpackPlugin.apply (/home/nrydevops/grommet-site/node_modules/monaco-editor-webpack-plugin/out/index.js:80:23)
    at webpack (/home/nrydevops/grommet-site/node_modules/webpack/lib/webpack.js:51:13)
    at startDevServer (/home/nrydevops/grommet-site/node_modules/webpack-dev-server/bin/webpack-dev-server.js:94:16)
    at /home/nrydevops/grommet-site/node_modules/webpack-dev-server/bin/webpack-dev-server.js:166:3
    at /home/nrydevops/grommet-site/node_modules/webpack-dev-server/lib/utils/processOptions.js:33:9
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>start: `cross-env NODE_ENV=development webpack-dev-server --mode development --open`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/nrydevops/.npm/_logs/2019-12-30T15_12_36_117Z-debug.log

I did try it with both yarn install as well as npm install and cleaning the npm_modules and cache each time following your instructions.


[gardening] Fix recently introduced typos: "fucntion" → "function", "functio" → "function", "mergable" → "mergeable", "mistmatched" → "mismatched"

What's in this pull request?
Fix recently introduced typos: "fucntion" → "function", "functio" → "function", "mergable" → "mergeable" and "mistmatched" → "mismatched".
Resolved bug number: –

Before merging this pull request to apple/swift repository:

[ ] Test pull request on Swift continuous integration.

Triggering Swift CI
The swift-ci is triggered by writing a comment on this PR addressed to the GitHub user @swift-ci. Different tests will run depending on the specific comment that you use. The currently available comments are:
Smoke Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please smoke test
    OS X platform               | @swift-ci Please smoke test OS X platform
    Linux platform              | @swift-ci Please smoke test Linux platform

Validation Testing
    Platform     | Comment
    ------------ | -------------
    All supported platforms     | @swift-ci Please test
    OS X platform               | @swift-ci Please test OS X platform
    Linux platform              | @swift-ci Please test Linux platform

Note: Only members of the Apple organization can trigger swift-ci.

@swift-ci Please test

@swift-ci Please test

@swift-ci Please test again (I believe the OS X CI fail is spurious :-))

@swift-ci Please test

@practicalswift Would you mind resolving conflicts?

@gribozavr Conflicts resolved :-)

@swift-ci Please test

@swift-ci Please test


[WebNN-native/Node] support context-based compute graph.

Move synchronous and asynchronous compute methods from MLGraph to MLContext and rename the methods to MLContext.computeSync and MLContext.compute.

Modified webnn.json and webnn_wire.json to sync with the latest spec.
Retained the ComputeImpl() method under the GraphBase class and made it as a public member.
Retained the overrides of the compute implementation in the Graph classes of each backend.
The context-based compute is implemented by calling the ComputeImpl() method of the GraphBase class.
Modified the test cases and nodejs binding.

BTW, CI may be blocked, because the PR in the polyfill has not been merged.
@fujunwei @mingmingtasd PTAL, I can optimize the code here firstly.

Fixed issues related to Wire, @fujunwei @mingmingtasd PTAL, Thanks.


Update /code to include syntax highlighting

It'd be nice to see some colors and better information.

Oh nice, thanks @zachmmeyer, we'll merge this after the testing stuff is implemented fully :)

Can we revisit this now that they've been merged? @zachmmeyer, are you willing to do the tests for this?

Can we revisit this now that they've been merged? @zachmmeyer, are you willing to do the tests for this?

I'm willing to do the tests, I just don't know how to do them.

I'm willing to do the tests, I just don't know how to do them.

We have a new README that has been merged to master and should have all the instructions! As a heads up though, you'll need to npm i the new dependencies, and when you run the tests only run npm test commandName.test.js instead of npm test as the README currently describes. Waiting on some PRs to update those pieces to be merged.

We have a new README that has been merged to master and should have all the instructions! As a heads up though, you'll need to npm i the new dependencies, and when you run the tests only run npm test commandName.test.js instead of npm test as the README currently describes. Waiting on some PRs to update those pieces to be merged.

Understood. I will go check out the README and look at the instructions. Thank you @twalton83 !!!

Understood. I will go check out the README and look at the instructions. Thank you @twalton83 !!!

Were you still interested in knocking this out?

Oh wow I completely forgot about this.
I'm going to say no!
I'll read the read me at another time, if you all don't think this is something necessary for the bot, might as well kill it. Or if someone else is willing to do the testing.

I wanted to close it


TypeError: "Error.captureStackTrace is not a function" in firefox

Describe the bug
Getting a TypeError: "Error.captureStackTrace is not a function" in Firefox when trying to parse a malformed CSV file
Using version 4.8.2
To Reproduce
Create a simple React application and include the following code
const data = "A,B\ntest"
parse(data, {}, (err, output) => {
  console.log(err);
  console.log(output);
});

Running the application generates the following Error:
CsvError

  1155 | constructor(code, message, ...contexts) {
  1156 |   if (Array.isArray(message)) message = message.join(' ');
  1157 |   super(message);
> 1158 |   Error.captureStackTrace(this, CsvError);
       | ^  1159 |   this.code = code;
  1160 |
  1161 |   for (const context of contexts) {

Additional context
Verified in Firefox 71.0(32-bit)

It shall be fixed with commit f1081345e7376535665e9f56c913df50b9abb76d, thank you


[Feature Request] Kenmei Tracking?

Describe your suggested feature
I've been using this Manga/Manhwa/Manhua/Webtoon tracking website called Kenmei (kenmei.co) it's a super underrated tracker that is new. It's like how any other tracker works, but it has features that others don't have, and that is the support of TL Groups/other websites such as Webtoon and Mangadex and only base their database of series according to what their "supported sites" have iirc. and I would love to have this as a tracking option in Mangadex since it's painful to open their site again and add the series that I like or read again and again instead of just adding them via Neko.
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a short but informative title.
[X] I have updated the app to the newest version Latest.
[X] I have checked through the app settings for my feature.
[X] I will fill out all of the requested information in this form.

Until there is API support added this won't be added.  Scraping is against the TOS of a user of Kenmei and at this time the owner/maintainer says adding an API is on the back burner.


How to disable LOD System

Hello i want to disable lod system and create one tile ocean piece.
Want to achieve similar like this : https://www.youtube.com/watch?v=XDdch5IYAFc
Any help would be appreciated.
Thanks

Hello, thats tricky - the ocean system is built around the LOD data structure and this assumption is hardcoded into the system - there is a fair bit of code to ensure 0 pops.
It might be possible to hack it to work - i can get something okish by applying the following settings on OceanRenderer.cs:

Set Viewpoint to be a new GameObject placed where you want the object to be so the ocean doesnt follow the camera. Give it a y height of 100 or something above the ocean.
Set Min Scale and Max Scale to be the same, say 16
Set the Lod Count to be 2
Create anim wave settings using menu Assets/Create/Crest/Animated Waves Settings, assign it to the Sim Settings Animated Waves field. On this asset, disable Readback Data (because the readback system assumes > 2 lods currently - at least it does on a PR I'm working on at the moment).
Select Disable Skirt
Wherever you have your wave spectrum, disable enough octaves until the warnings about too many wave components go away (OR search all code for BATCH_SIZE and increase it in both places).

It would be possible to reduce Lod Count down to 1 - some fixup (or hacking..) would be required on ShapeGerstnerBatched.cs because it does fancy things with large wavelengths in the last 2 lods, to avoid pops. It might be possible to disable this fancy stuff - I think may involve disabling _renderBigWavelengthsShapeCmdBuf and _renderBigWavelengthsShapeCmdBufTransition .
That's pretty much the best i can do for now, let me know if that helps. Actually since I did that work I decided to push it - check main.unity on the branch feature/patch-of-ocean , commit bfcc0201c4c881dfde3e29d6b53a6263eb95ad56 .

Hello thanks for the hints.
I'm checking the commit.
It helped too much.
Thank you again.


[Performance][Core] Optimize the performance of evictor v1 and v2 by applying a priority queue and lazy deletion

FIX #6923
Summary

I discovered that the eviction logic with the OrderedDict free_table in Evictor V1 and V2 slows down overall performance (especially TTFT) when using prefix caching mode.
In some scenarios, utilizing prefix caching mode makes the system slower compared to when prefix caching is not used.
The evict function is frequently called when allocating a new block, as no block is evicted until the block space is full in prefix caching mode.
The eviction logic was slow because free_table is declared as an OrderedDict, which is a linked list, and it tries to find a block with content hash (Evictor V1) or block ID (Evictor V2) in this free_table.
Utilizing a priority queue and lazy deletion helps find the block faster.

Result Verification

As shown in the following output, the block ID and content hash had the same value between the as-is and to-be states (which is expected).
With this change, I could make the duration of the evict function much faster.

===============================
evicted_block_id compare:  12010   12010
content_hash_compare:  -7334740008364413937   -7334740008364413937
as-is evict duration:  7.0807114243507385 ms
to-be evict duration:  0.012848526239395142 ms
===============================
evicted_block_id compare:  12038   12038
content_hash_compare:  -7008894356950570757   -7008894356950570757
as-is evict duration:  7.1028973907232285 ms
to-be evict duration:  0.008581206202507019 ms
===============================

Performance

I checked the TTFT performance using llmperf and the Llama3-8B model with an A100 GPU.
I benchmarked with 1536 input token length (512 same prefix + 1024 random input) and 512 output token length.
By applying this commit, I can make the system faster while utilizing prefix caching.
The speed-up metric is calculated based on the performance without prefix caching mode.

as-is

Model
Num Clients
Block Manager
Prefix Caching
TTFT (mean)
Speed Up

Llama3-8B
16
v2
X
841 ms

Llama3-8B
32
v2
X
1441 ms

Llama3-8B
64
v2
X
2619 ms

Llama3-8B
128
v2
X
4729 ms

Llama3-8B
16
v2
O
1962 ms
0.43 (slowed down)

Llama3-8B
32
v2
O
8382 ms
0.17 (slowed down)

Llama3-8B
64
v2
O
12665 ms
0.21 (slowed down)

Llama3-8B
128
v2
O
22439 ms
0.21 (slowed down)

to-be

Model
Num Clients
Block Manager
Prefix Caching
TTFT (mean)
Speed Up

Llama3-8B
16
v2
O
541 ms
1.55

Llama3-8B
32
v2
O
901 ms
1.60

Llama3-8B
64
v2
O
1563 ms
1.68

Llama3-8B
128
v2
O
2947 ms
1.60

thanks for the contribution!
cc @alexm-neuralmagic @cadedaniel for block manager related optimization.

FYI this PR seems to be optimizing the same path https://github.com/vllm-project/vllm/pull/7193

At high level these fixes look great, will need evictor folks to review with more detail (sorry for second ping @robertgshaw2-neuralmagic )

At high level these fixes look great, will need evictor folks to review with more detail (sorry for second ping @robertgshaw2-neuralmagic )

Thanks, Alex is going to take a look from out side, since he most recently has been in this codepath optimizing BMv2

btw, I would rename the topic of the PR to "[Performance] ....", since it is not a bugfix

/ready

I rebased codes to resolve the conflict

@alexm-neuralmagic @Yard1
I rebased and tested my code again. I would appreciate your reviews.

In my local test, the test_eviction_alloc_mixed sometimes passes and sometimes fails.
tests/core/block/test_prefix_caching_block.py ................. [  6%]
............................................................... [ 29%]
............................................................... [ 53%]
............................................................... [ 76%]
............................................................... [100%]
=================== 269 passed, 2 warnings in 6.49s ===================

I believe the assertion in this part is not strictly necessary, because all blocks can be candidates for eviction if they have same last accessed time. The key difference is that the previous code search blocks from the beginning of the free table, while my implementation does not.
@leiwen83 @cadedaniel @comaniac
Could you check whether it would be fine to remove the assertion mentioned above and review my PR please?


[capture] Enable uJSON for KMAC

Similar to #218 , this PR enables uJSON support for capturing KMAC traces. The device command handler code can be found in #20563.
Consists of three commits:

uJSON implementation. Closes #238
Adds KMAC to CI. Closes #237
Switch byte array to int array in data generator.

Regarding the CI implementation: I've never done that, so I cannot comment on that


WebSocket client

Is your feature request related to a problem? Please describe.
I want to be able to use the http client for websocket connections
Describe the solution you'd like
We can start with a basic API that looks like this. Later on, add support for client configuration or potentially support SocketApp directly.
val fooBar = Socket.collect[WebSocketFrame] {
  case WebSocketFrame.Text("FOO") => ZStream.succeed(WebSocketFrame.text("BAR"))
  case WebSocketFrame.Text("BAR") => ZStream.succeed(WebSocketFrame.text("FOO"))
}

Client.socket(fooBar) // Task[Unit]

Describe alternatives you've considered

None

@tusharmath Client.socket(socket) would just give us a description for communication. I'm not sure how the Client should process this during execution. Do you think a seed is required  on open?

I am not sure what do you mean by "description for communication".

[ ] Unit test case for websocket client
[ ] queue internal for assertions
[ ] client socket handler
[ ] edit channel initializer
[ ] client api
[ ] websocket client config generation
[ ] websocket client example
[ ] general refactor


set user-agent to kpt + http headers

set the user agent for requests to kpt

strictly only the string "kpt" plus the version.
No full path to the kpt binary (could include PII).

Also, as extra "X-Header"s, we can add the kpt subcommand WITHOUT parameters/args (e.g. kpt live apply, kpt pkg) to get information on which subcommands are being used.


E tensorflow/stream_executor/cuda/cuda_blas.cc:464] failed to create cublas handle: CUBLAS_STATUS_NOT_INITIALIZED

When I run “ python trainer.py --dataset MNIST --batch_size 36 --num_dis_conv 6 --gan_type wgan-gp”， it shows error as follow：

I tried to download the whole file, and downloaded CIFAR100 dataset.
while I try to run the script:
python3 trainer.py --dataset CIFAR100 --batch_size 25 --num_dis_conv 6 --gan_type wgan-gp
I waited for one day and longer, however, it seems it stucks there and does not progress.
{'id': <tf.Tensor 'shuffle_batch:0' shape=(25,) dtype=string>,
'image': <tf.Tensor 'shuffle_batch:1' shape=(25, 224, 224, 3) dtype=float32>}
2019-10-18 16:18:03.281299: I tensorflow/stream_executor/dso_loader.cc:152] successfully opened CUDA library libcublas.so.9.0 locally
0 10000000 <tf.Variable 'global_step:0' shape=() dtype=int64_ref>
'now is at step 0*******'
[2019-10-18 16:18:04,956] Saved checkpoint at 0
Do you face the same issue if you try to run with CIFAR100 dataset??


Support for RxJS 7

Is your feature request related to a problem? Please describe.
Support for RxJS 7, currently we have the following error message when trying to use the lib:
Cannot find module 'rxjs/internal/scheduler/AsyncScheduler' from<EMAIL_ADDRESS>

Thanks @magne4000 !
This is the same issue as #39 , so closing this in favor of the original issue
Will update this week


No such method error asw.l()Lij

Getting the following error with Minecraft 0.13, Rift 1.0.3-41 and stockpile 0.1.0 (no other mods installed):
[10:31:58] [Server thread/FATAL]: Error executing task
java.util.concurrent.ExecutionException: java.lang.NoSuchMethodError: asw.l()Lij;
	at java.util.concurrent.FutureTask.report(FutureTask.java:122) ~[?:1.8.0_152]
	at java.util.concurrent.FutureTask.get(FutureTask.java:192) ~[?:1.8.0_152]
	at k.a(SourceFile:199) [k.class:?]
	at net.minecraft.server.MinecraftServer.w(SourceFile:701) [MinecraftServer.class:?]
	at sn.w(SourceFile:357) [sn.class:?]
	at net.minecraft.server.MinecraftServer.v(SourceFile:656) [MinecraftServer.class:?]
	at net.minecraft.server.MinecraftServer.run(SourceFile:559) [MinecraftServer.class:?]
	at java.lang.Thread.run(Thread.java:748) [?:1.8.0_152]
Caused by: java.lang.NoSuchMethodError: asw.l()Lij;
	at notjoe.stockpile.tile.TileBarrel.displayBarrelContents(TileBarrel.kt:109) ~[TileBarrel.class:?]
	at notjoe.stockpile.tile.TileBarrel.handleRightClick(TileBarrel.kt:83) ~[TileBarrel.class:?]
	at notjoe.stockpile.block.BlockBarrel.a(BlockBarrel.kt:79) ~[BlockBarrel.class:?]
	at bkt.a(SourceFile:281) ~[bkt.class:?]
	at tf.a(SourceFile:313) ~[tf.class:?]
	at ub.a(SourceFile:918) ~[ub.class:?]
	at nr.a(SourceFile:53) ~[nr.class:?]
	at nr.a(SourceFile:11) ~[nr.class:?]
	at ix.a(SourceFile:10) ~[ix.class:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) ~[?:1.8.0_152]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) ~[?:1.8.0_152]
	at k.a(SourceFile:198) ~[k.class:?]
	... 5 more

This error occurs when I try to interact (left or right click) with the item.
I also cannot break the item successfully.

Never mind, I just worked out you have to break the item from the non-face side.

The latest version of Stockpile was tested on Rift 1.0.2-33 (the latest CurseForge version), so there might be some changes in the mappings that warrant recompiling the mod. I'm not aware of any breaking changes between those versions, but I'll investigate further when I get the chance.

Just pushed a new version built against Rift 1.0.3-45 -- this appears to fix the issue, closing for now.

Yes, this works for me.


Tensorflow using Intel UHD graphics instead of Nvidia

While training my model tensorflow is using the Intel UHD graphics instead of Nvidia RTX 2060. But the thing is even if utilization is 0% the RTX memory is being used.
tensorflow = 2.7.0
cudaa = 11.2
cudnn = 8.1

Hi @Abhinav-Bhattarai! Could you try again specifying GPU device  using tf.device ?

It started to use my Nvidia graphics for a bigger dataset


Remove aws-sdk dev dependency

This dependency has been causing issues (#215) and does not appear to be used anymore since node-usb switched to using node-pre-gyp-github to host binaries on GitHub a few years ago.
I think we can safely remove it now.

Agree with this #https://github.com/LedgerHQ/ledgerjs/issues/242

Ok this is open to anyone as a great first contribution. Otherwise, I'll add it to my Bug Fix Friday list. 😄

Could you kindly assign this bug to me?

I've added a pull request for this issue:
https://github.com/tessel/node-usb/pull/295/commits/fce72ce7664e9e6e5753fdbc684a012a6e710386

Fixed in https://github.com/tessel/node-usb/pull/300


Is this project still active?

Hello, I use Paq and I have no complaints: it does everything I need, I think that it is amazing.
Nonetheless, I wonder if it is/will still be active.
Best wishes

@savq I subscribed to this issue.

I'm loving Paq.  It's simplicity&speed is the way to go!!  The only thing I wanted (wish) is to have a command like  "PaqVSync"  for verbose syncing.  When I used to use Plug I liked the verbose output of what libraries/plugins/packages were getting updated.   I created this little function to do what I thought was necessary but since PaqSync is asynchronous the last PaqLogOpen opens the cleaned log before sync has actually run... So the Verbose syncing doesn't really work as I intended.

So if there is a way to automatically open the Paq log after the PaqSync has completed that would be great to know (and do).

I decided to make a 1.0 release so that people know the current features are mostly stable and won't change in the near future.
I also added a bug report template. Hopefully I'll be able to fix bugs in a more timely manner.

@danshumaker I'll probably won't add your suggested feature, but you might be able to achieve something similar using autocommands. like:
PaqLogClean
autocmd User PaqDoneSync PaqLogOpen

I'll close this since the answer for the past 2 years has been "Yes. It's active, but not much."
Near future developments are tracked in #149


[MRG] Sensor selection

Closes https://github.com/mne-tools/mne-python/issues/3258.
I'll wait until https://github.com/mne-tools/mne-python/pull/3290 gets merged so I can use the fake_click there for testing.

I like this idea. Only minor comments.

can this be used to select interactively the visible channels in raw.plot?
also can you make the lasso line in red?

can this be used to select interactively the visible channels in raw.plot?

That's an interesting idea. I'll look into it.

I was thinking about using this in interactive channel properties - so that when multiple channels are selected their average properties are shown. For this to be easy it would be nice if attaching user-specified callback to SelectFromCollection I was thinking about using this in interactive channel properties - so that when multiple channels are selected their average properties are shown. For this to be easy it would be nice if attaching user-specified callback (that gets self as the only argument) was possible. In my case the callback would look up the channel indices and update properties. WDYT? It would be a small change.(a callback that gets self as the only argument for example) was possible. In my case the callback would look up the channel indices and update properties. WDYT? It would be a small change.

My phone messed up that comment, sorry, editing...

Good idea @mmagnuski . I actually just added an mpl event 'lasso_event', which doesn't pass any args, but you can access the selection through SelectFromCollection.lasso attribute. Maybe we could pass the selections through the event too. Wdyt?

@jaeilepp - I was thinking about the onselect method in SelectFromCollection . It could end in running something like self.callback that by default would highlight channels but could also be a user-specified function. But I know much more about interactivity in matlab so there could be better solutions - I don't know if you can emit custom events and add listeners to these in matplotlib...

I don't know if you can emit custom events and add listeners to these in matplotlib

Yes you can. Now it has 'lasso_event' which is emitted after each selection. So now you need to do fig.canvas.mpl_connect('lasso_event', callback) and since the event doesn't pass args, the signature is simply def callback():

@jaeilepp Cool, thanks!

[Current coverage][cc-pull] is 86.64%

Merging [#3309][cc-pull] into [master][cc-base-branch] will decrease coverage by 5.36%

@@             master      #3309   diff @@
==========================================
  Files           336        335      -1
  Lines         57247      57513    +266
  Methods           0          0
  Messages          0          0
  Branches       8712       8745     +33
==========================================
- Hits          52671      49830   -2841
- Misses         4576       5033    +457
- Partials          0       2650   +2650

[][cc-pull]

Powered by Codecov. Last updated by [f248db9...e1fbf78][cc-compare]
[cc-base-branch]: https://codecov.io/gh/mne-tools/mne-python/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/mne-tools/mne-python/compare/f248db95eb90601ff34eda3a29e227f496f10913...e1fbf785ddd6e8e540449b8e10e8ee238fd9f1b5
[cc-pull]: https://codecov.io/gh/mne-tools/mne-python/pull/3309?src=pr

This is ready for review. I added 'all' option to plot sensors and made raw browser selection to use that. This way it is possible to select several sensor types instead of just one, but it makes the topomap a bit clogged. Lmk what you think.

Tbh Alex I never use the interactive functions, so I can't really say too much. Hope my comments are useful though.

Comments addressed.

The lasso works nicely, except:

It will not be sufficient for dipole fitting subselection, or other types of subselection. There needs to be a way to e.g. select discontinuous sets of sensors. For example, holding down shift or control while doing a second selection could make it so that the results are appended to the existing selection instead of replacing the existing selection.

In such a "concatenation" mode via ctrl/select, re-selecting a channel that is already selected should probably de-select it.

Clicking on a channel name/location does not select it in selection mode. I wonder if using some simple heuristic you could make the selector smart enough to tell if a user was trying to lasso versus select a single channel based on e.g. lasso size (if less than a couple of pixels, assume it was a click not a click-drag lasso operation).

WDYT?

sounds like useful additions. If it's non trivial I vote to postpone this
to another PR

The control modifier now works as @Eric89GXL suggested. I assume it doesn't work for mac though. IIRC the modifier keys aren't available for mac backends.

Now the lasso selection is on when using 'selection' and 'position' options for raw.plot. This also means that clicking the topomap no longer selects the corresponding selection group. 'lasso' option is removed.
Minimal script for testing:
import mne
from mne.datasets import sample
data_path = sample.data_path()

raw = mne.io.read_raw_fif(data_path + '/MEG/sample/sample_audvis_raw.fif')
raw.plot(order='position')

Works really nice!
Just two things:

shouldn't it work for epochs.plot() too?
when I select some channels with lasso and then click one of these channels timecourses - it goes gray but also seems to change, probably to some other channels signal?

shouldn't it work for epochs.plot() too?

Eventually maybe, but definitely not on this PR. I fear it will be a bit more painful process.

when I select some channels with lasso and then click one of these channels timecourses - it goes gray but also seems to change, probably to some other channels signal?

I believe it's just the projectors turning on/off. For bad channels the projectors are turned off. Can you confirm this (open the proj dialog and uncheck all the boxes, the line shouldn't change now when selected)?

I added block param. I didn't include 'auto' option though.

Works great, +1 for merge

I can confirm it was because of projections. Everything works great!
Just two other little things:

when I click on proj button, deselect average reference, close the proj menu and then click proj button again, the average reference is still selected (although not active) - to activate it again I have to uncheck the checkbox and then check it again. But this is most likeliy not related to this PR, but a separate issue.
I have a (metaphysical) feeling that the order in which the spatial selections are shown in the radio-button menu (temporal, parietal, occipital, frontal) is a little suboptimal. Would be nice if frontal channels were at the top and occipital at the bottom. :) This is only half-serious, so you don't have to take it seriously (but you can ;) ).

Otherwise +1, really cool feature.

Ready for review/merge.

+1 for merge

I'm still +1 so that's our two, thanks @jaeilepp


Fixes #2497 no_closing_tag: strip closing tag with whitespace to EOF

This PR is made after #2497 . It updates no_closing_tag fixer, allowing whitespace between closing tag and EOF to be stripped.

not sure did I get your intentions.

allowing whitespace between closing tag and EOF to be stripped.

you did not provide test case with whitespace between ?> and EOF.
the case you have provided is already there in non-monolitic version:
https://github.com/FriendsOfPHP/PHP-CS-Fixer/blob/master/tests/Fixer/PhpTag/NoClosingTagFixerTest.php#L57-L65
the change in code you have introduced is to start modifying non-monolitic files, sth different that what you described in PR title/description.
what is your intention?
if intentions are to hande non-monolitic files, then it's BC breaking change
and apart of that, non-monolitic files could be:

php-based templates
weird php files without clean purpose
for first case, in templates, each opening tag should have closing tag
for second case, we don't want to touch them

We discussed it at #2497 . After some time I can review my intentions, so basically I want to strip closing php tag in files like this:
<?php

// php code

?>
\n
\n
\n

But PHP-CS-Fixer considered it to be non-monolithic and did not fix it.

then it's totally different what you have implemented here.
please make new, risky fixer that will:

check if there is one inline html, that is at the end of file and contains only whitespaces, if so - remove it
make integration test + priority utest that will make sure that new fixer works nicely with existing fixer you have just modified

ping @cronfy
are you willing to finish this PR ?

@keradus no, sorry, I am unable to do it in a near time.

ping @cronfy any plans on finishing this, no rush or pressure, just trying to get a feeling on where some PRs stand ATM :)

@SpacePossum sorry, no: I am not PHP-CS-Fixer user anymore, so I afraid I can't do this job good.

No worries @cronfy , thanks for letting us know, I'm sure someone will pick this one up and finish it.
Sad to hear you're no longer a user of the fixer though!

Closing as this PR got out dated with the project and the author stated no longer using the project.
If anyone wants to picks this up, please lets us know :)


fix the fix on README.rst

See wordreference.

Thanks for teaching me a word ;)

I have to tell you I was wrong either, I had to look at the correct spelling ;)


Data have not been decoded (verified contract / Optimism)

Could you please help add the following ABI to the safe-UI on the Optimism chain?
https://optimistic.etherscan.io/address/0x471d3dA2eB7D91149dA5e0dD4ce523267237380B#code
A contract is verified but data have not been decoded.
https://gnosis-safe.io/app/oeth:0xBCA3839a7fDeA4a008b6a115E1EFa4008eE85e5a/transactions/multisig_0xBCA3839a7fDeA4a008b6a115E1EFa4008eE85e5a_0x7c6b2b01f8980a89b0f0e746931e99d8dac9d11e21720f0bed63f552b986466f

Done, it will show up as soon as cache refreshes


Release/10 14 21

Tested this fix, works like a charm. All 3d models are working perfect, However there is a bug somewhere because I have found some item images do not load after this commit is applied.
When i visit Moon Cats collection and try click on any nft to loan item details I see that images do not load! None of them do.
When I undo the commit then I can view moon cats images no problem so I'm sure you need to maybe take a look.


txn: Forbit pushing min_commit_ts of async commit transaction

Signed-off-by: MyonKeminta<EMAIL_ADDRESS>
What problem does this PR solve?
This  PR adds a check to check_txn_status that prevents it from misusing that may push min_commit_ts of async commit transactions.
Related changes

No

Check List
Tests

Unit test will be added after merging https://github.com/tikv/tikv/pull/8349 , which added some test utility for async commit.

Release note

No release note

/test

@sticnarf If so, I think it's necessary  to use a special protocol to notify TiKV that the transaction type is being changed and it's no longer a async-commit transaction. That's because pushing forward a async-commit transaction's  commit ts may lead to correctness problem. It may happen when the client is misused or its version is too old.
For example session 1 performs async-commit transaction T1 at start_ts = 1, and then performs another transaction T2 at start_ts = 10. Then T1's result must be visible by T2. However, if another transaction pushes the min_commit_ts of T1 before T2 performs read and T1 being committed, the final commit ts of T1 become larger than 10, making it invisible to T2.

@sticnarf @youjiali1995 PTAL again. It's better to be merged after implementing transaction recoverying in TiDB, though.

/lgtm

/merge

/merge


[Bug] [Workflows] Export the json workflow, and then import the work and report an error

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened

What you expected to happen
Import succeeded
How to reproduce
Export the json workflow, and then import the work and report an error
Anything else
No response
Version
dev
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

same issue #12078


Add test data for ccs

Hesitating on this PR because of the new unit test code. MultiQC is a bit shaky on unit testing (as in, there isn't really any) but people have tried to add some in the past in the main repo. I want to have a bit of think about how I want it to be done before accidentally setting a precedent here if that's ok 😅 Will hopefully have time to sit down with MultiQC code soon(ish - there's a bit of a backlog).
Phil

Hi,
That makes sense, I didn't notice until I was done developing the new features I needed that the project was using unittest instead of pytest. Since pytest also runs the unittest code that is already in the project, I decided to keep the tests I had already written in. As a last resort, I can always remove the tests that I wrote for CCS, and only keep the example files. That way, we can at least test that the example files do not crash MultiQC.
Slightly offtopic, if you are more interested in having high level tests for MultiQC, you could have a look at pytest-workflow. It is quite simple and powerful, in the below example I test to make sure that the statistics I am interested in for my pipeline end up in the MultiQC HTML report.
- name: test-workflow-hsmetric-baits
  tags:
    - integration
  command: >
    cromwell run
    --inputs tests/data/config/variant_calling_hsmetric_baits.json
    PacBio-variantcalling.wdl
  files:
    - path: test-output/multiqc/multiqc_report.html
      contains:
        - "Alignment Summary"
        - "GC Coverage Bias"
        - "HSMetrics"
        - "Target Region Coverage"
    - path: test-output/multiqc/multiqc_data.zip

The project was using unittest instead of pytest.

The project isn't really using anything at the moment - I guess the code coverage is under 1%. What is there currently was a stab at starting something from a contributor at a hackathon several years ago. It's not more than a stub.
pytest-workflow looks really interesting! Potentially for MultiQC, but especially for @nf-core where we are starting to play with / write something that looks pretty similar for workflows. Thanks for the tip!

x-ref https://github.com/ewels/MultiQC/pull/1288

ok I figure I've left this long enough and as I think the CI will ignore it there should be no harm in merging it 😄  Can worry about the big picture later..
Thanks again!


Jackson serialize PrivateData EmptyList field to empty string

Currently, if the privateData list is empty , jackson outputs it as json array i.e "[]" , to keep it inline with chaincode_event empty privateData, it is made empty string.

Signed-off-by:Jitendra Das<EMAIL_ADDRESS>

Please run git commit --amend -s and remove the incorrectly copied sign off line.

Done


Worksheet flag

Added

New red flag added to config
I don't know how Virginia's scroll branch got in here but that's probably a sign to call it a day

Screenshot

:+1:  Looks good!


fix(rgaa): change titles for _target

:tada: This PR is included in version 1.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


WireFrame for Style Surveys

FE team will need to put together a wireframe for how the page should look / render and how the user should be able to interact with it.


Fix #72: Add the possibility to specify chrony configuration for NTP

Create terraform variables in order to configure chrony (ntp) on coreOS node.
This is related to changes in ocp4-playbook project (commit 22f883869be8aaf9e470301a24796a20e7782d37)
issue : https://github.com/ocp-power-automation/ocp4-playbooks/issues/31
PR: https://github.com/ocp-power-automation/ocp4-playbooks/pull/34
creation of to variable:
chrony_config: true or false (default)
chrony_config_servers: list of ntp server and options
terraform variable usage example
chrony_config = true
chrony_config_servers = [ {server = "0.centos.pool.ntp.org", options = "iburst"}, {server = "1.centos.pool.ntp.org", options = "iburst"} ]

@schabrolles Please update the quickstart doc with the new variables.
Also, you need to sign your commit. You can run: git commit -m 'small message' -m 'Fixes #72' -s. Also can use --amend option and force push the same commit. No need to close/recreate the PR.

@yussufsh thanks for the advice.

Time to squash all your commits into 1 with same commit message format.

How can I rebase / squash my commit without deleting the remote branch ?

How can I rebase / squash my commit without deleting the remote branch ?

@schabrolles you can rebase and squash in your local copy and then force push it to your remote branch (chrony_setup)
Ref: https://www.w3docs.com/snippets/git/how-to-squash-commits-after-they-have-been-pushed.html
Let me know if there are any issues..

@bpradipt Looks ok now. thanks for the tip ;)


fix: only emit 'end' after unzip is done writing

When using node:stream.pipeline or node:stream/promises.pipeline with superagent, the pipeline often fails with a 'write after end' error or with truncated data.  This is because, in _pipeContinue, we are emitting 'end' as soon as the response is done.  This is fine for normal requests, but for compressed content, there is an extra transform stream introduced in the pipe line.  If we emit end on the agent request before the unzipObject transform stream is done writing data, pipeline will end the target stream too early and unzipObject will attempt to continue writing to the closed stream (resulting in an error, or, depending on the stream being written to, truncated data).
To fix, we make sure to emit 'end' on the agent request only after the unzipObject stream has finished writing.
Checklist

[x] I have ensured my pull request is not behind the main or master branch of the original repository.
[x] I have rebased all commits where necessary so that reviewing this pull request can be done without having to merge it first.
[x] I have written a commit message that passes commitlint linting.
[x] I have ensured that my code changes pass linting tests.
[x] I have ensured that my code changes pass unit tests.
[x] I have described my pull request and the reasons for code changes along with context if necessary.

yes, I believe it is.

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.25 :tada:

Comparison is base (73c7efb) 94.19% compared to head (ef969fa) 94.45%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1766      +/-   ##
==========================================
+ Coverage   94.19%   94.45%   +0.25%
==========================================
  Files          14       14
  Lines        1155     1155
==========================================
+ Hits         1088     1091       +3
+ Misses         67       64       -3

Impacted Files
Coverage Δ

src/node/index.js
94.30% <100.00%> (+0.55%)
:arrow_up:

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

If there's anything I can do to help with the review of this code, please let me know.

Please let me know if there's anything I can do to help facilitate the review of this code.  This bug can result in data loss for anyone using this library to pipe GZIP'ed content to a stream.  The bug seems more prevalent when running node 18 or higher.


Classes on custom Astro components aren't getting sorted

What version of prettier-plugin-tailwindcss are you using?
v0.2.3
What version of Tailwind CSS are you using?
v3.2.7
What version of Node.js are you using?
v16.14.2 & v18.14.2
What package manager are you using?
npm & pnpm
What operating system are you using?
Linux
Reproduction URL
https://stackblitz.com/edit/node-lf1jgc?file=package.json,src%2Fpages%2Findex.astro

Run npm run format and check the order of the classes in src/pages/index.astro file

Describe your issue
In a .astro file, Tailwind classes that are specified on default HTML elements are getting sorted correctly, whereas the same classes on a custom Astro component aren't. I have both prettier-plugin-astro and prettier-plugin-tailwindcss plugin installed.

Hey! So you'll need to follow the steps in the readme for working with other Prettier plugins. You can find that here: https://github.com/tailwindlabs/prettier-plugin-tailwindcss#compatibility-with-other-prettier-plugins
I've updated your reproduction, and it's working for me with the addition of the .prettierrc file:
https://stackblitz.com/edit/node-hf7jt6?file=.prettierrc
Hope that helps! 👍

Thank you @reinink
I've just tried your fork, but the classes on <Custom /> remained unchanged like before.
Can you please run npm run format again on your fork and confirm it is working?
I've actually had that config file before I submitted the issue, but it didn't work then, so I deleted it to keep the reproduction minimal.

Confirming this is still an issue. The sorting doesn’t seem to work in custom (non-native-html) components.

Thanks for adding this quickly. Really appreciate it.
Btw is it still necessary to include "pluginSearchDirs": false in the config file? I just tried without it, and seems to be working fine.

@ni554n Hey our pleasure, thanks for bring this to our attention 👍


synth just-build insists on building more than is in the list

OK. Maybe this is intentional. But I could find no evidence in the man file
that indicates that synth will build any more, than what is in the file.list.
eg; synth just-build ./build.list
where "build.list" contains
textproc/libxslt
x11/libxcb
x11/libX11
x11/libXext
x11/libXfixes
x11/libXv
graphics/libdrm
x11/libXdamage
x11/libXvMC
My list file is much bigger. But my issue is, that when synth is passed my list, it insists upon
adding devel/llvm39 && devel/llvm40. Both of which are already installed on the system and
are not in the build.list file.
What am I missing. Should I have assumed synth would automatically include any
dependency it felt it needed? If so, I would have rather thought that synth would simply
"dismiss" files it felt it couldn't build w/o additional files. Much as it does when it finds
other conflicts.

--Chris

Both of which are already installed on the system
What is installed on your system is irrelevant.
are not in the build.list file.
The build list are the packages you want.  It's implicit that if those packages have dependencies, those dependencies will be built in order to accomplish the list.

Extreme example:
Your build list contains two ports on it: libreoffice and kde4
Obviously hundreds of packages have to be built to accomplish that.
So by now it should be obvious that some requirement of your build list has a requirement on llvm39 and llvm40, maybe 2 or 3 levels deep.  And it's probably graphics related.

Huge thanks for the reply, John.
Indeed. I do understand that in order to fulfill/complete (the building of) the list. That
dependencies must also be fulfilled. But, as I also noted; it seemed that it may
well be possible to simply dismiss those within the list that don't also include their dependencies
within the list. Much as it already does when asking it to "prepare-system", and there is some
problem encountered that prevents it from building some, or one of the ports.
No matter. I didn't see a conclusive answer within the man pages. So I simply asked.
Now I understand. :-)
Thanks John, for taking the time to answer -- greatly appreciated!
Have a nice weekend!
--Chris

it's a recursive list.  For every package that isn't already built adds its dependencies to the list, and each of of those can to.  Nothing can be removed off the list; they are all necessary.
For a system that's only served by synth, there are no build dependencies installed.  Thus the build list could easily exceed the installed list of a given system.  That's normal.

Thanks again, John.
I get what it's intent is. I just wasn't sure which way it would turn. IOW
If I tell it to prepare-system. It builds a list, and attempts to fulfill that list, creating every item in it.
But if for some reason, it encounters a problem building one of the ports in that list; it returns
Failure, which in turn cascades to those that depend ON it. Resulting in a list of Skipped.
THIS is why I wasn't sure what would be my results feeding it a build.list. You see, it could
have gone either way. But you decided it best to ensure satisfaction of the dependencies.
I understand, and that makes plenty of sense. :-)
But in this case. I was hoping it would have chosen to simply Fail, and only build those
whose dependencies were met.
Not a big deal. I appreciate you taking the time to help. I hope to give synth a real workout.
It is my intent to make this box it's working on, a build-box. Which synth will largely be
responsible for.
--Chris

Oh, and just for the record. I am NOT complaining about the direction you chose
for dealing with the build.list. I just wasn't sure, and I needed it to do the "wrong"
thing, in this ONE case. :-)
Thanks again!
--Chris

But in this case. I was hoping it would have chosen to simply Fail, and only build those
whose dependencies were met.

It does build everything it can.
The fail cascades to a number of skips.  Whatever is still left in the queue will build (unless another failure causes it to skip of course).

Chris, have you noticed a triad of new repositories in my github account?
https://github.com/jrmarino/Ravenports
https://github.com/jrmarino/ravenadm
https://github.com/jrmarino/ravensource

Umm. How can I say this... WOW!
Mind you; I've mostly just grabbed the gist of it. But if my further reading concurs with my
initial impression. Count me in. I love it!
It's funny. I've been working on a large scale project with someone over the last few months.
I also needed to deal with managing ports/software that would need to built on a regular basis,
and had been building a model in my mind to best accomplish that task. Yours, I must say, is
quite a different direction than I was taking -- not that I disagree with it (your direction). I'm just
appreciating the difference. That's all. :-)
OK I just spent some more time reading the source. Being an old Perl hack made it quite simple. ;-)
It seems a combination of Perl, C &&sh. Simple, and easy to follow. Easy reading. Tho it doesn't
hurt to have some background with the FreeBSD ports framework -- thanks John!
Oh, and I love the "conspiracy" label/term you coined for this. :-)
What's the status? How far out is it, would you estimate?
As soon as I can [finally] get my development system fully up'd (see next comment in this thread)
I'd love to help with this.
Thanks for pointing this out!
--Chris

OK I've struggled with this for ~72hrs. now, and I'm out of thoughts. This system tracks FreeBSD 12
current. Has now had 2 new worlds/kernels (both custom). I (initially) built all the ports from the tree.
I upped the src && ports together. So they're in sync. World && kernel built/installed w/o incident.
Synth will get me a complete repo, minus 17 ports. It all involves a cascade from a 3 port apex.
The 3 culprits are:
devel/libnotify (skipped 8)
textproc/libxml++26 (skipped 6)
devel/gnome-vfsmm

The complete list of skipped:
sysutils/gnome-mount by devel/libnotify
devel/gvfs by devel/libnotify
sysutils/xfce4-settings by devel/libnotify
x11-fm/thunar by devel/libnotify
deskutils/xfce4-notifyd by devel/libnotify
x11-wm/xfce4 by devel/libnotify
x11-wm/xfce4-desktop by devel/libnotify
www/firefox-esr by devel/libnotify
graphics/gx by textproc/libxml++26
graphics/cairomm by textproc/libxml++26
graphics/gimmage by textproc/libxml++26
x11-toolkits/gtkmm24 by textproc/libxml++26
x11-toolkits/pangomm by textproc/libxml++26
devel/gconfmm26 by textproc/libxml++26

I've attempted to singly target any one of the three culprits. But haven't managed to get
any of them to build (within synth). Regarding: textproc/libxml++26
attempting to build it within synth seemed to fail based (according to synth) on the fact that
a dependency on devel/glib20, and that devel/glib20 is one revision too new -- it wants
revision 1. But glib20 is at revision 2. I can't understand this. Everything comes from the
same local ports tree.
Any way to get around this sort of thing within synth?
Thanks, John!
--Chris

It seems a combination of Perl, C &&sh. Simple, and easy to follow. Easy reading. Tho it doesn't hurt to have some background with the FreeBSD ports framework -- thanks John!

Well, there's no C or Perl in it at all.
Everything runs through ravenadm, which is essentially "synth 2.0".  The "ports" are single file "buildsheets" that ravenadm processes.  the "make" program is not involved at the user level.
There is a "make" framework that is based on ports but completely re-written. That is make + shell scripts only though.  It's pure Ada other than about 1% C objects used in ravenadm/ravenexec.

conspiracy

A flock of ravens is known as an "unkindness", "conspiracy" or a "constable".  But yes, there's a double-entendre there.

portsnap may have failed on you (assuming you are using portsnap and not svn).
If you are using portsnap, I suggest blowing the tree away and repulling it.

It seems a combination of Perl, C &&sh...

Well, there's no C or Perl in it at all.
Everything runs through ravenadm, which is essentially "synth 2.0". The "ports" are single file "buildsheets" that ravenadm processes. the "make" program is not involved at the user level.
There is a "make" framework that is based on ports but completely re-written. That is make + shell scripts only though. It's pure Ada other than about 1% C objects used in ravenadm/ravenexec.

Indeed. I was trying to get up to speed too quickly. It just felt that way, I guess. Still. I
found it easy reading. Tho much of that also speaks to your organization. Well conceived!

conspiracy

A flock of ravens is known as an "unkindness", "conspiracy" or a "constable". But yes, there's a double-entendre there.

I always thought a flock of ravens were referred to as Murders. No?
Thanks John.

a flock of crows are a "murder".
Ravens are cousins to crows but not the same.
FYI, a porter's guide I'm slowing writing: https://github.com/jrmarino/Ravenports/wiki/Ravenporters_Guide

portsnap may have failed on you (assuming you are using portsnap and not svn).
If you are using portsnap, I suggest blowing the tree away and repulling it.

Hmm. No portsnap involved here. Never use it.
I'l have to figure some way to coerce it into a package. I'm confident that a 1 point revision
won't give too much grief, if any.
Back to the think tank...
Thanks for trying, John.

Ravens are cousins to crows but not the same.

Heh. Funny how crows, and ravens were given such dubious names. It might be interesting to look further into that, some time.
Thanks for the clarification!
--Chris

the point is that the ports tree you are using is disintegrated.
Or at least that's the theory based on what you are seeing.
If the tree is good, then everyone would see what you are seeing.  I assume if's a "just me" situation so suspect either make.conf or your tree.

P.S.
I wish your Triad was complete, and the [ports] repo was full right now. I kick all this
mess I'm currently working on, to the curb, and start using immediately!
The more I read in your wiki. The more I'm liking it.
Thanks!
--Chris

the point is that the ports tree you are using is disintegrated.
Or at least that's the theory based on what you are seeing.
If the tree is good, then everyone would see what you are seeing. I assume if's a "just me" situation so suspect either make.conf or your tree.

That'd be odd. I haven't done anything but svn up, on both trees.
This is the extent of my make.conf
DEFAULT_VERSIONS+=perl5=5.24 pgsql=9.6 python3=3.4 python2=2.7 ruby=2.3 linux=c7 tcl=87 tk=86
Not really arguing with you. Just having a bit of trouble explaining to myself how that it's
even possible. I've been on *BSD for ~35yrs. and don't ever recall running into a
corrupted tree, via cvs, or svn.
But in the end. You're probably right. The only reasonable answer is to blow it (the tree) away,
and start afresh. :-(
Thanks for the reply, John.
--Chris

what about libnotify?  what's causing that to fail?

by the way, IIRC you are using "upgrade-system" rather than using your own buildlists

meaning what is installed on your system could be given bad instructions to synth.

try this:
pkg query -e '%a=0' '%o' > my.list

The check UPDATING for libnotify and modify list as needed.

(and obviously give my.list to synth instead of using update-system)

Thanks, John!
I really appreciate your taking so much time for this!
OK followed your advice, and fed the list pkg generated. But, of course, only 3 of the build slots got
populated, and they were those same 3 ports. Which ultimately failed, as before.
So, at this point. I've decided to use as much as I've managed to get synth to build for me, and
issued
pkg upgrade -r Synth
I'm now going to bounce the box, query synth && feed it that list again. If failure ensues. I'm
just going to cd to those 3 port directories and issu a
make package install clean
Ask synth what it then thinks. If all looks good, synth will complete building the dependent
ports, and life is good; else
cd /usr/ports; svn up .
followed by
synth rebuild-repository
&&
synth prepare-system
Wish me luck, and have a wonderful weekend!
--Chris
P.S.
There was nothing in UPDATING regarding libnotify
my ports tree is at 437523

Well. That flushed out the problem. Well, one of them;
After allowing pkg to upgrade the system, and bouncing the box. I took a stab at
cd /usr/ports/textproc/libxml++26
make package install clean

The build of which, failed. Seems the addition of llvm39 && llvm40, from the ports
tree revealed a problem with textproc/libxml++26, that my base install of llvm40 did not.
So synth was spot on, about there being a problem. It just couldn't tell me what exactly.
Anyway. Looks like it's time to up the ports tree, and see if I can get a buildable version.
Take care!
--Chris out...


[Feature]: llama2, Are you ready to integrate llama2 into it? What is the approximate time to do it?

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

we already released v0.3.2,  which support llama-2.  #347


Paginate is showing as false even if set in config.rb to true

Expected behavior
With paginate set as true in config.rb it is expected to see the paginate variable set as true in layouts/templates.
paginate set to true: https://github.com/0foo/0foo.dev/blob/master/config.rb#L41
Actual behaviour

https://github.com/0foo/0foo.dev/blob/master/source/layouts/layout.erb#L17

https://0foo.dev/

this autodeploys via netlify

[Steps to reproduce the problem]
Can just run docker-compose up on this repository.
(https://github.com/0foo/0foo.dev)

Please provide a repository or some tests we can run through

(https://github.com/0foo/0foo.dev)

Should just be able to go here and docker-compose up

Additional information

Ruby version: 3.2  https://github.com/0foo/0foo.dev/blob/master/Dockerfile#L3
Middleman version: 4.5.0 https://github.com/0foo/0foo.dev/blob/master/Gemfile.lock#L46
Middleman Blog version: 4.0.3 https://github.com/0foo/0foo.dev/blob/master/Gemfile.lock#L55
OS version:

nick@nick-XPS-9315:~$ docker exec -it 638410c7762a /bin/bash
root@638410c7762a:/middleman# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@638410c7762a:/middleman#

Hello @0foo 👋🏼
I'm helping to maintain this project now, so no, this is not abandoned... but maintaining "large" open source projects for years is hard. This project is more than 12 years old now, so of course there are some legacy code and decisions that will be really hard to understand at this point. That said, I'm still exploring the code, issues, ... but I'll try to do my best (last week I fixed the CI and moved to GH Actions, which a good 1st step).
Could you please send a failing test or an app that reproduces your error? I'm using this pagination module in a couple of sites with no problems at all.
Best,
Marc

Hey cool! Glad to see this project is still alive.  Its my fav static site generator.
The ticket has a repo with a docker container in it. Should just be able to pull the repo down and docker-compose up.
I couldnt figure it out but I didnt have time to work on it.

It's still my favorite too 👌 And it's really powerful, you can even write more tools and abstractions on top. I've been building a small framework on top: https://github.com/Subgin/tonic. The combination of Data + Sitemap + configuration as code => super powers 🚀
I already checked those links, but it seems now a Jekyll site.


node-red-contrib-viseo-google-spreadsheet

Hello i'm trying to setup a project to call data from a spreadsheet as data variables and also dump data to a data log on another spreadsheet, However i'm constantly getting this error.
"Error: error:0906D066:PEM routines:PEM_read_bio:bad end line"
any thoughts on how to fix this issue?
Thanks in advance.

Hi,
Never seen this before... This is not an error from Node-RED, but maybe from OpenSSL or nginx.


Parameters functional

List of changes:

uses '.' instead of '/' as a name delimiter in the container tree (to mimic pytorch)
tentative changes to rnn parameters names to resemble more pytorch's,
Functional container designed for use in Sequential,
clang-format.

I've reverted the formatting changes, sorry about that!
I think I should probably add a test to verify that param() is consistent with parameters()?


[top] Fix typo in comment in top_earlgrey.hjson

This is "software clock gate", not "software config". The naming in
the actual code is sw_cg.

Force-push adds missing tag to commit message 1st line.


Reorganize modules

Changes:

Move CachePadded into the root module because use crossbeam_utils::cache_padded::CachePadded is unnecessarily long.
Likewise, move AtomicConsume into the root module.
Rename scoped to thread because it's a module with thread-related utilites (i.e. an extension of std::sync::thread).
Rename spawn_unsafe/builder_spawn_unsafe to spawn_unchecked/builder_spawn_unchecked.

I fixed the test here: https://github.com/jeehoonkang/crossbeam-utils/commit/e1648afd375f36d2ee372523c4647f8c92094ad2
After merging this commit, I'd like to merge this PR.


share image with firebase url dont work

i'm try to send image like :
(window).plugins.socialsharing.share('message', null, 'URL FROM FIREBASE' , null);
but he dont open in whatsapp, can someone help-me?

Making all objects in a bucket publicly readable
https://cloud.google.com/storage/docs/access-control/making-data-public#buckets


Could monosdf work with CUDA11.6?

Hello! Thanks for the amazing work!
I'm wondering could this project work with cudatoolkit==11.6 and cudatoolkit-dev==11.6 instead of 11.3?

Hi, I think it should work if you install pytorch version properly.

Sorry for being unclear. My question is that, it seems that CUDAToolkit-dev only has 11.4 version (https://anaconda.org/conda-forge/cudatoolkit-dev).
If I install cudatoolkit=11.6 and cudatoolkit-dev=11.4, would that cause any inconsistency?
Thanks!

Sorry to bother again, I'm wondering whether it is doable to install different version of cudatoolkit & cudatoolkit-dev, for we're hoping to use cuda11.6 in our work.
Could you give me a hint about that?
Many thanks!  :-)

Did you solved the problem? I'm using CUDA 11.7, but have some errors.

@YJ-142150 I'm sorry, I couldn't run this with CUDA11.6, there's some version conflicts with CUDA that I can't fix.


Update readme with "Example Project Structure"

I'm trying to integrate kue with existing (Express) application. And found that it's a challenge.
It would be cool to know how make it done. Googling not helped me.
Is it true that I have to run 2 express apps in this case?

we have related topics with example codes showing using kue app inside your express app, please search issues


[CLI] <-- allDubs -- allSubs>

** Main info: -- allDubs only downloading Eng and -- allSubs not downloading any subs**
Script version: 1.0.0
Service: -- allDubs  -- allSubs
What do you want to do: want to be able to download all dubs and subs with said commands
** Additional Info: **
anidl.exe --service "funi" - s 1007443 - e 1 - q 0 -- allDubs --allSubs
Not sure if this could be the issue but Eng audio is 1007443 while Jap audio is 1008381

@drknss89 Where do you get the language ids from? Funimation doesn’t have those.
Can you give me the console output?

Should be fixed with the newest release

I will give it a try when I get home, sorry I couldn't get you the output, had to work

@izu-co it works, thank you so much, this is an amazing project and it's great to have, I can get my animes onto my media server without having to wait for someone else to do it first, ty ty ty

Glad you like it


Sockets can emit close before end, breaking #479.

In this week's installment "Node Streams Incompatibility", it turns out that Sockets can emit end after close even though the Readable streams docs say that

The [close] event indicates that no more events will be emitted, and no further computation will occur.
- https://nodejs.org/api/stream.html#stream_event_close

Emphasis mine.
#479 was written under the assumption that a close means no more data to emit. It will end the wrapper stream if it ever receives close without having seen end before. This seems compatible with the Readable docs.
However, for a Socket, close means the client disconnected. There may still be buffered data previously received that has not yet been emitted. In fact, it is possible to receive end after close (see below). The end result is that if you are slow at consuming the incoming data, and the client disconnects before you're done, the Highland stream will end, unpipe from the socket, and you lose any pending data.
Now, there's a reason why #479 tries to end the wrapper when it gets . It is possible to get close without end (see below). If we don't close, the wrapper stream will never end.
So now we have a case where we can't end on close or we lose data and a case where we must end on close or we hang. What should we do?
I'm of the opinion that it is better to hand (visible though difficult to debug) than to throw away data (possibly not visible). Especially since the former case seems to require an explicit call to destroy by the user.
Thoughts?

Close before end in Sockets
I discovered this when messing around with sockets from the discussion in #489. Start this server.
var i = 0;
var dest = _();
var server = net.createServer((socket) => {
    var id = i++;

    console.log(`Client ${id}: connected`);
    socket.on('end', () => console.log(`Client ${id}: ended`))
        .on('close', () => console.log(`Client ${id}: closed`));

    socket.setEncoding('utf-8');

    _(socket)
        .doto(x => {
            console.log(`Client ${id}: received '${x.trim()}'`);
            if (x === 'consume\r\n') {
                console.log(`Client ${id}: consuming`);
                dest.each(() => {});
            }
        })
        .pipe(dest, {end: false});
});

server.listen(8080, () => console.log('server up.'));

In this example, dest starts out blocked, simulating slowness. In a different terminal, use telnet to send some data.
$ telnet localhost 8080
Trying <IP_ADDRESS>...
Connected to localhost.
Escape character is '^]'.
abc
def
ghi
^]

telnet> Connection closed.

Close the connection, you should see the server print out
server up.
Client 0: connected
Client 0: received 'abc'
Client 0: closed

Open a different connection and unblock the stream by sending the word consume.
$ telnet localhost 8080
Trying <IP_ADDRESS>...
Connected to localhost.
Escape character is '^]'.
consume
^]

telnet> Connection closed.

You will see this under v2.7.4
Client 1: connected
Client 1: received 'consume'
Client 1: consuming
Client 0: received 'def'
Client 0: received 'ghi'
Client 0: ended         <-- `end` event from the first client!
Client 1: ended
Client 1: closed

and this under master. Note all the missing data from the first client.
server up.
Client 0: connected
Client 0: received 'abc'
Client 0: closed
Client 1: connected
Client 1: received 'consume'
Client 1: consuming
Client 1: ended
Client 1: closed

Close without end
Destroying an FS stream emits close but not end.
// The file here must be larger than the highWaterMark.
var read = fs.createReadStream('some-large-file');

var dest = _(read);

read.on('close', () => {
    console.log('closed');
    dest.done(() => console.log('I am done.'));
});

read.on('end', () => console.log('end'));

dest.pull((err, x) => {
    console.log("Received chunk.");
    read.destroy();
});

// Under master
// => Received chunk.
// => closed
// => I am done.

// Under 2.7.4
// => Received chunk.
// => closed

Since silent dropping data seems way worse, I've gone ahead and reverted the relevant parts of the changes from #479. See https://github.com/caolan/highland/commit/76d13ecfccc5c9125a0aa53cb5c725bcd2abd645. This is released as v2.8.1.
Feel free to reopen if anyone has anything to say.

@vqvu I was waiting for this fix. 'end' or 'error' isn't called when e.g. http requests to a server is aborted by the client... only 'close'...

Yeah...I'm not sure what we can do about it, honestly. We can't support both the IncomingMessage close behavior and the Socket close behavior at the same time. I guess it's too much to ask for node Readables to have consistent semantics...
The best we can do here, is to add some sort of new _.fromReadable method that takes an options object that defines how to proceed. So the IncomingMessage usage would be something like _.fromReadable(req, {endOnClose: true}). We could also add it directly to the _ constructor if I can figure out a way to describe the usage without being too confusing.
I assume something like that would work for you?

@vqvu: Yes, that would work... Right now I do this:
    const stream = new PassThrough()
    req.on('error', err => stream.emit('error', err))
    req.on('close', err => stream.emit('end'))
    req.pipe(stream)
    const stream2 = _(stream)

Can't we solve the socket case by testing whether more data can be retrieve after 'close' and of not 'end'.

I'm not sure how. I don't know of any API that lets us check for buffered data.

Not sure if this is any help? https://github.com/jshttp/on-finished

That code does inspection on specific http request/response data structures, which we can't really do, since it doesn't apply to all Readables. However, it does give me an idea. See  #505.
We can simply punt the issue to the user entirely by allowing the second argument to be an arbitrary handler which can be as simple or complex as necessary. People can then delegate this behavior to a library like on-finish if they'd like (e.g., _(req, onFinish)).


final wrap ups

Not quite ready yet!

fix sim section typo

Lol, it's not done yet!
On Tue, Sep 8, 2015 at 5:48 PM, Katy Huff<EMAIL_ADDRESS>wrote:

Merged #136 https://github.com/cyclus/fundamentals-paper/pull/136.
—
Reply to this email directly or view it on GitHub
https://github.com/cyclus/fundamentals-paper/pull/136#event-403786339.

--
Matthew Gidden, Ph.D.
Postdoctoral Associate, Nuclear Engineering
The University of Wisconsin -- Madison
Ph.<PHONE_NUMBER>

I'm confused. Why open an unready pr?
On Tue, Sep 8, 2015, 8:51 AM Matthew Gidden<EMAIL_ADDRESS>wrote:

Lol, it's not done yet!
On Tue, Sep 8, 2015 at 5:48 PM, Katy Huff<EMAIL_ADDRESS>wrote:

Merged #136 https://github.com/cyclus/fundamentals-paper/pull/136.
—
Reply to this email directly or view it on GitHub
https://github.com/cyclus/fundamentals-paper/pull/136#event-403786339.

--
Matthew Gidden, Ph.D.
Postdoctoral Associate, Nuclear Engineering
The University of Wisconsin -- Madison
Ph.<PHONE_NUMBER>
—
Reply to this email directly or view it on GitHub
https://github.com/cyclus/fundamentals-paper/pull/136#issuecomment-138606595
.

To warn others who might be editing the same items.
On Tue, Sep 8, 2015 at 5:56 PM, Katy Huff<EMAIL_ADDRESS>wrote:

I'm confused. Why open an unready pr?
On Tue, Sep 8, 2015, 8:51 AM Matthew Gidden<EMAIL_ADDRESS>wrote:

Lol, it's not done yet!
On Tue, Sep 8, 2015 at 5:48 PM, Katy Huff<EMAIL_ADDRESS>wrote:

Merged #136 https://github.com/cyclus/fundamentals-paper/pull/136.
—
Reply to this email directly or view it on GitHub
<https://github.com/cyclus/fundamentals-paper/pull/136#event-403786339
.

--
Matthew Gidden, Ph.D.
Postdoctoral Associate, Nuclear Engineering
The University of Wisconsin -- Madison
Ph.<PHONE_NUMBER>
—
Reply to this email directly or view it on GitHub
<
https://github.com/cyclus/fundamentals-paper/pull/136#issuecomment-138606595

.

—
Reply to this email directly or view it on GitHub
https://github.com/cyclus/fundamentals-paper/pull/136#issuecomment-138608218
.

--
Matthew Gidden, Ph.D.
Postdoctoral Associate, Nuclear Engineering
The University of Wisconsin -- Madison
Ph.<PHONE_NUMBER>

@gonuke has explicitly stated he will be editing soon, and I don't want
either of use to work on the same areas, so I'm trying to be as transparent
and explicit as possible.
On Tue, Sep 8, 2015 at 6:02 PM, Matthew Gidden<EMAIL_ADDRESS>wrote:

To warn others who might be editing the same items.
On Tue, Sep 8, 2015 at 5:56 PM, Katy Huff<EMAIL_ADDRESS>wrote:

I'm confused. Why open an unready pr?
On Tue, Sep 8, 2015, 8:51 AM Matthew Gidden<EMAIL_ADDRESS>wrote:

Lol, it's not done yet!
On Tue, Sep 8, 2015 at 5:48 PM, Katy Huff<EMAIL_ADDRESS>wrote:

Merged #136 https://github.com/cyclus/fundamentals-paper/pull/136.
—
Reply to this email directly or view it on GitHub
<
https://github.com/cyclus/fundamentals-paper/pull/136#event-403786339>.

--
Matthew Gidden, Ph.D.
Postdoctoral Associate, Nuclear Engineering
The University of Wisconsin -- Madison
Ph.<PHONE_NUMBER>
—
Reply to this email directly or view it on GitHub
<
https://github.com/cyclus/fundamentals-paper/pull/136#issuecomment-138606595

.

—
Reply to this email directly or view it on GitHub
https://github.com/cyclus/fundamentals-paper/pull/136#issuecomment-138608218
.

--
Matthew Gidden, Ph.D.
Postdoctoral Associate, Nuclear Engineering
The University of Wisconsin -- Madison
Ph.<PHONE_NUMBER>

--
Matthew Gidden, Ph.D.
Postdoctoral Associate, Nuclear Engineering
The University of Wisconsin -- Madison
Ph.<PHONE_NUMBER>

ah gotcha. sorry.
On Tue, Sep 8, 2015 at 9:03 AM, Matthew Gidden<EMAIL_ADDRESS>wrote:

@gonuke has explicitly stated he will be editing soon, and I don't want
either of use to work on the same areas, so I'm trying to be as transparent
and explicit as possible.
On Tue, Sep 8, 2015 at 6:02 PM, Matthew Gidden<EMAIL_ADDRESS>wrote:

To warn others who might be editing the same items.
On Tue, Sep 8, 2015 at 5:56 PM, Katy Huff<EMAIL_ADDRESS>wrote:

I'm confused. Why open an unready pr?
On Tue, Sep 8, 2015, 8:51 AM Matthew Gidden<EMAIL_ADDRESS>wrote:

Lol, it's not done yet!
On Tue, Sep 8, 2015 at 5:48 PM, Katy Huff<EMAIL_ADDRESS>wrote:

Merged #136 <https://github.com/cyclus/fundamentals-paper/pull/136
.
—
Reply to this email directly or view it on GitHub
<
https://github.com/cyclus/fundamentals-paper/pull/136#event-403786339>.

--
Matthew Gidden, Ph.D.
Postdoctoral Associate, Nuclear Engineering
The University of Wisconsin -- Madison
Ph.<PHONE_NUMBER>
—
Reply to this email directly or view it on GitHub
<

https://github.com/cyclus/fundamentals-paper/pull/136#issuecomment-138606595

.

—
Reply to this email directly or view it on GitHub
<
https://github.com/cyclus/fundamentals-paper/pull/136#issuecomment-138608218

.

--
Matthew Gidden, Ph.D.
Postdoctoral Associate, Nuclear Engineering
The University of Wisconsin -- Madison
Ph.<PHONE_NUMBER>

--
Matthew Gidden, Ph.D.
Postdoctoral Associate, Nuclear Engineering
The University of Wisconsin -- Madison
Ph.<PHONE_NUMBER>
—
Reply to this email directly or view it on GitHub
https://github.com/cyclus/fundamentals-paper/pull/136#issuecomment-138612293
.

--
http://katyhuff.github.com


Fix HDR demo

This fixes a nit in the demo.
@petele You can merge and push live at your leisure.

Whoops!
There were 6 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/updates/2017/12/chrome-63-64-media-updates.md#L220 - '

:tada: This has been pushed live to https://developers.google.com/web/


P4: As a user, I want to see all upcoming tasks, so I can plan ahead and don't forget.

Acceptance Criteria

[x] Given the user is on the main page, when viewing the displayed plants, next watering/caring schedules are displayed.
[x] Given the user is on the main page, when clicking on a plant, the user is redirected to the plant detail page, where the planned schedule is displayed.

Development Tasks
Frontend

[x] sopra-fs24-group-01/sopra-fs24-plantparent-client#19
[x] sopra-fs24-group-01/sopra-fs24-plantparent-client#20

Backend

On the main page the plant status is shown. Days overdue and in how many days an action needs to be applied.
Opening the plant the details of the schedule is shown


Upgrades to vaadin 24

Should solve https://github.com/vaadin-component-factory/selection-grid-flow/issues/37


Add option to run slow tests only?

It might be useful to provide an option, e.g. --slow-only, or provide some other mechanism to enable running only those tests marked as slow and skipping others? This could be useful in CI where normal tests run as usual, but there can be an optional job to run only the slow tests without re-running all of the non-slow tests.

Argh. Didn't check closed issues... 🤦🏻
Duplicate of #3.


Fix typos

Summary
Fix typos
Impact
No impact
Testing

@sgysh could you fix the nxstyle warning too? https://github.com/apache/incubator-nuttx/pull/1905/checks?check_run_id=1174233927.

I'll try to fix them.


update x-project-id values in .toc files

hi there
I noticed your forks have retained the original project IDs. To avoid confusion would you consider updating or removing them?
These are what I found:

[ ] SFX-WoW/Masque_Dominos shares x-curse-project-id: 699643 with tullamods/Dominos
[ ] SFX-WoW/Masque_Dominos shares x-wowi-id: 26455 with tullamods/Dominos
[ ] SFX-WoW/Masque_Dominos shares x-wago-id: WL6JYRNv with tullamods/Dominos
[ ] SFX-WoW/Masque shares x-curse-project-id: 13592 with RealUI/RealUI
[ ] SFX-WoW/Masque shares x-wowi-id: 12097 with RealUI/RealUI
[ ] SFX-WoW/Masque shares x-wago-id: kRNLgpGo with RealUI/RealUI

Cheers,

Those are the correct IDs for my projects. Otherwise, they would not be able to be published since I use the BigWigsPackager to push them to those web sites and it uses those IDs.

You're right, I'm mistaken. Some bad data has crept in to my catalogue.
Thanks for your patience.

ss


Issue with Submitting Slack App Modal when 'user' Element is Included in Initial Value

Hello,
I'm currently working on a Slack app that features a rich_text_input within a modal, allowing users to input content and submit it. While I've successfully handled various types of styling content submissions, I've encountered an issue when a user element ({'type': 'user', 'user_id': 'UXXXXXX'}) is included in the initial_value.
The problem arises when the modal fails to submit the view to the backend, providing a vague error message: "We had some trouble connecting. Try again?" Despite having a correctly set up handler on the backend for processing submissions with other styling, in this particular case, the modal fails without triggering the event handler. This leads me to suspect an internal issue with how Slack handles the initial_values.
Notably, I observed that the issue seems to resolve if users type anything in the rich_text_input area before submitting. I speculate that the UI may refresh during user typing, potentially resolving the problem.
Code snippet of my modal:
block = {
    "type": "modal",
    "callback_id": "my-callback-id",
    "title": {
        "type": "plain_text",
        "text": "Title",
    },
    "submit": {
        "type": "plain_text",
        "text": "Submit",
    },
    "close": {
        "type": "plain_text",
        "text": "Back",
    },
    "blocks": [
        {
            "type": "input",
            "element": {
                "type": "rich_text_input",
                "action_id": "my-action-id",
                "initial_value": {
                    "type": "rich_text",
                    "elements": [{"type": "user", "user_id": "UXXXXX"}],
                },
            },
            "label": {
                "type": "plain_text",
                "text": "Description",
            },
        }
    ],
}

While this appears to be a broader issue with Slack app modals, I couldn't find a more suitable place to report it. If there's a more appropriate channel for reporting such issues, please guide me accordingly. Your assistance is much appreciated!
The slack_bolt version
slack-bolt==1.18.0
slack-sdk==3.26.1

Python runtime version
Python 3.11.6

OS info
ProductName:            macOS
ProductVersion:         14.1.2
BuildVersion:           23B92
Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000

Expected result:
The modal view being submitted, and the backend handler receive the event.
Actual result:
Received an error: "We had some trouble connecting. Try again?". No event triggered.

Hi @lancewl thanks for writing in and providing a great description 💯
I was able to reproduce this behavior with the following app
# app.py
import logging
from slack_sdk import WebClient
from slack_bolt import App, Ack
from slack_bolt.adapter.socket_mode import SocketModeHandler

logging.basicConfig(level=logging.DEBUG)

app = App()

block = {
    "type": "modal",
    "callback_id": "my-callback-id",
    "title": {
        "type": "plain_text",
        "text": "Title",
    },
    "submit": {
        "type": "plain_text",
        "text": "Submit",
    },
    "close": {
        "type": "plain_text",
        "text": "Back",
    },
    "blocks": [
        {
            "type": "input",
            "element": {
                "type": "rich_text_input",
                "action_id": "my-action-id",
                "initial_value": {
                    "type": "rich_text",
                    "elements": [
                        {
                            "type": "rich_text_section",
                            "elements": [
                                {
                                    "type": "user",
                                    "user_id": "UXXXXX",
                                }
                            ],
                        }
                    ],
                },
            },
            "label": {
                "type": "plain_text",
                "text": "Description",
            },
        }
    ],
}

@app.view_submission("my-callback-id")
def view_sub(ack: Ack):
    ack()
    print("view submitted")

@app.command("/hello")
def handle_command(
    ack: Ack, body: dict, client: WebClient
):
    ack()
    client.views_open(trigger_id=body["trigger_id"], view=block)

if __name__ == "__main__":
    # export SLACK_APP_TOKEN=xapp-1-...
    # export SLACK_BOT_TOKEN=xoxb-...
    # python app.py

    SocketModeHandler(app).start()

{
  "display_information": {
    "name": "test-app"
  },
  "features": {
    "slash_commands": [
      {
        "command": "/hello",
        "description": "A test command"
      }
    ],
    "bot_user": {
      "display_name": "test-bot"
    }
  },
  "oauth_config": {
    "scopes": {
      "bot": ["commands", "chat:write", "chat:write.public"]
    }
  },
  "settings": {
    "interactivity": {
      "is_enabled": true
    },
    "org_deploy_enabled": true,
    "socket_mode_enabled": true
  },
  "outgoing_domains": []
}

Results
Submitting the modal with only the default value result in the following 🔴

Editing the default value and then submitting the modal works as expected 🟢
I believe this is a server side issue and does not strictly affect Bolt Python, I will bring this up internally, you can also email our developer support team<EMAIL_ADDRESS>about this


Bundle installation files to avoid installing 21,000+ loose JavaScript files

Is your feature request related to a problem? Please describe.
Installation, upgrade or removal of storage takes a long time even with modern SSDs because of the sheer number of small files involved. The installation package bundles over 21 thousand files.
Describe the solution you'd like
Bundle the installation files to avoid littering the filesystem with 21k+ loose files.
Describe alternatives you've considered
N/A, but admittedly the friction pushes me to use alternatives like Cyberduck often
Additional context
Other electron-based MS apps do this already.

Hi @stewartadam , this is already something we are actively moving towards. :)

What's the status on this? Installing and upgrade remains a huge pain because of the number of small files. brew upgrade just spun for several minutes on storage explorer because of this.

@stewartadam as an FYI, in our latest major release, 1.22, the number of files went from 18k to 13k. Between now and the end of this year, I'd love for us to get below 10k, but there's a lot of work that needs to be done for that. Unfortunately we have lots of things to do, so I can't promise anything, but please rest assured this is something we are actively working towards, even if only step by step.

@MRayermannMSFT thanks for the update! This is good to hear.
I recognize I'm commenting from a user perspective with little knowledge of the codebase challenges involved - but wanted to share that even with a couple thousand, it's still going to cause long delays due to the high number of filesystem calls involved (particularly so if not on a solid state disk). Perhaps something like webpack can be used to minimize dependencies and bundle the numerous small files into a single, larger file?

Perhaps something like webpack can be used to minimize dependencies and bundle the numerous small files into a single, larger file?

@stewartadam  Yes, that is exactly what we are using! The issue is that the architecture of Storage Explorer was originally written without any concern for bundling. And unfortunately that also led to an architecture where we can't just simply start webpacking without doing anything else. So we're having to enable webpacking slower than you might expect.

A quick update on this. We've made lots of progress in reducing the footprint of Storage Explorer on disk. Both by file count and overall app size. When this issue was first opened, the latest version of Storage Explorer (on Windows) took up 449.20 MB of space and had 17,943 files. Now the latest version is 397.00 MB and 8,087 files.
We're currently working on bundling the core of Storage Explorer, and then after that, I think there's just one or two sub-components which still need bundling. I'm hopeful (so no promise 🙃), that by mid next year we'll be well under 400 MB, with only a few thousand files.

I'm going to go ahead and close this as completed in 1.33.
After an almost 4 year battle, all JavaScript code that we're shipping is now bundled. There's one loose end left to clean up related to our native node modules (https://github.com/microsoft/AzureStorageExplorer/issues/7553), but cleaning those up isn't going to make a drastic change from where things sit as of today.
We've also de-duped a bunch of other file types (like images) leading to even more savings.
Here's a comparison of where we our latest dev build is at:

Stats
1.18.1
1.33.0-dev
Change

Total Files
17,943
2,900
-84%

JavaScript Files
9,172
248
-98%

Size (MB, not incl. allocation)
449.2
354.7
-21%

Thanks all for the patience!


test: run cypress via docker

Purpose
In order to have alignment between CI and local (Mac) development, we decided to run Cypress via Docker.
Approach
Run E2E Cypress tests in a Docker container with Compose.
Also use XQuartz to communicate between Cypress in Docker container, and Cypress GUI locally.
On CI, caching is in place for Docker images.
Sources used:

https://www.cypress.io/blog/2019/05/02/run-cypress-with-a-single-docker-command/
https://sourabhbajaj.com/blog/2017/02/07/gui-applications-docker-mac/

Testing
Locally, CI should also pass with newly generated snapshots.
Risks
This heavily now relies on Mac being a development machine.

Few questions

This heavily now relies on Mac being a development machine.

From code it seems that only a Bash terminal is needed, so Linux and Windows should work as long as that condition is met, no?
Or is it because XQuartz only works properly on Mac?

It seems that XQuartz is only needed for cypress open, and cypress run works fine inside Docker without external communication, is that right?
If that's the case, do you think it'd be better to avoid the extra setup complexity and just run cypress open like before, outside Docker, and either just disable screenshot taking or disregard them, requiring snapshot to be run to update baseline images?

Do you think it's still valuable to keep the baseline screenshots job in CI just in case someone has issues with Docker or for any other reason can't update the images locally?
Might be useful when we're not able to use our work machines.

From code it seems that only a Bash terminal is needed, so Linux and Windows should work as long as that condition is met, no?
Or is it because XQuartz only works properly on Mac?

XQuartz is a Mac software, yes.
This should also work on another system, adding missing pieces. However, docs inform about Mac usage. On the other hand, we already do use Homebrew on docs, so assuming that macOS is used...

It seems that XQuartz is only needed for cypress open, and cypress run works fine inside Docker without external communication, is that right?
If that's the case, do you think it'd be better to avoid the extra setup complexity and just run cypress open like before, outside Docker, and either just disable screenshot taking or disregard them, requiring snapshot to be run to update baseline images?

I'm not sure.
I think better to use same machine as used for screenshot taking. That is, Cypress would always run in a Docker container.
What you suggest seems even more confusing - taking screenshots (that is, overriding them), then running locally. But later running via Docker to re-generate proper screenshot.

Do you think it's still valuable to keep the baseline screenshots job in CI just in case someone has issues with Docker or for any other reason can't update the images locally?
Might be useful when we're not able to use our work machines.

We could keep it, but only as manual job - otherwise no CI would be longer.


Format For Final Presentations

I really liked the poster sessions we did last year! Unfortunately, this really won't be an option this year - what should we do instead?

Aravind's idea: Could make a course "demo video", post on YouTube

every member of the project records a video explaining the part he/she contributed to the project.
one of the team members stitches all the videos and send it to us.

OR

members of the project join a webex meeting and record their part one by one explaining their project.
send the recording to us

I really like this video idea, especially the first one
We may need to do a little research into free editing software to recommend to students
We can then make an overall course project video (we can make a long and a "highlight" reel), and promote on LinkedIn etc.

For Windows OS:

Stitching can be done using the default 'Photos' app.
More details are in the following link:
https://www.msftnext.com/merge-videos-windows-10-photos-app/
Students can download the following free application that is available in the Microsoft store:
https://www.microsoft.com/en-us/p/simple-video-trim-merge/9pfdgvnpd3zc?activetab=pivot:overviewtab

For MAC OS:

Students can use the QuickTime player and stitch videos:
https://help.vyond.com/hc/en-us/articles/115005667026-How-do-I-merge-two-or-more-videos-in-QuickTime-
(I never used MAC OS and I guess QuickTime player is pre-installed in Apple computers and laptops)

Updated the readme file professor. Please let me know if it looks good or any changes to be made.


Crash on "no field 'Policy'" with SQS

Possibly related to #34 , just had this crash with the latest published image from Docker Hub:
Traceback (most recent call last):
	15: from /usr/local/bundle/gems/parallel-1.20.1/lib/parallel.rb:215:in `block (4 levels) in in_threads'
	14: from /usr/local/bundle/gems/parallel-1.20.1/lib/parallel.rb:366:in `block in work_in_threads'
	13: from /usr/local/bundle/gems/parallel-1.20.1/lib/parallel.rb:518:in `with_instrumentation'
	12: from /usr/local/bundle/gems/parallel-1.20.1/lib/parallel.rb:367:in `block (2 levels) in work_in_threads'
	11: from /usr/local/bundle/gems/parallel-1.20.1/lib/parallel.rb:507:in `call_with_index'
	10: from /usr/local/bundle/gems/aws_recon-0.2.25/lib/aws_recon/aws_recon.rb:99:in `block (2 levels) in start'
	 9: from /usr/local/bundle/gems/aws_recon-0.2.25/lib/aws_recon/aws_recon.rb:49:in `collect'
	 8: from /usr/local/bundle/gems/aws_recon-0.2.25/lib/aws_recon/collectors/sqs.rb:11:in `collect'
	 7: from /usr/local/bundle/gems/aws_recon-0.2.25/lib/aws_recon/collectors/sqs.rb:11:in `each_with_index'
	 6: from /usr/local/bundle/gems/aws-sdk-core-3.110.0/lib/aws-sdk-core/pageable_response.rb:93:in `each'
	 5: from /usr/local/bundle/gems/aws_recon-0.2.25/lib/aws_recon/collectors/sqs.rb:14:in `block in collect'
	 4: from /usr/local/bundle/gems/aws_recon-0.2.25/lib/aws_recon/collectors/sqs.rb:14:in `each'
	 3: from /usr/local/bundle/gems/aws_recon-0.2.25/lib/aws_recon/collectors/sqs.rb:21:in `block (2 levels) in collect'
	 2: from /usr/local/lib/ruby/2.6.0/ostruct.rb:314:in `delete_field'
	 1: from /usr/local/lib/ruby/2.6.0/ostruct.rb:314:in `delete'
/usr/local/lib/ruby/2.6.0/ostruct.rb:315:in `block in delete_field': no field `Policy' in #<OpenStruct QueueArn="arn:aws:sqs:eu-west-1:123456789:MyBestQueue", ApproximateNumberOfMessages="0", ApproximateNumberOfMessagesNotVisible="0", ApproximateNumberOfMessagesDelayed="0", CreatedTimestamp="1590487053", LastModifiedTimestamp="1593502746", VisibilityTimeout="70", MaximumMessageSize="262144", MessageRetentionPeriod="345600", DelaySeconds="5", ReceiveMessageWaitTimeSeconds="0", type="queue", arn="arn:aws:sqs:eu-west-1:123456789:MyBestQueue"> (NameError)

Thanks for catching this. It will be fixed in the next version, later today.


Swerve code missing !!!!


New home page design

Refractoring home page to look like figma design.

@PepiPetrov Please add link to the design and attach a screenshot


Next-Generation Share Details

Introduce a CLI command (and supporting API calls) to show all current share details. This should close the gap on showing the access grants for the --closed permission model and provide all of the available information about shares.

Necessary for #724.


NobodyNada: Blacklist we, offer

NobodyNada requests the blacklist of the following keyword(s):

we - MS search
offer - MS search

we has been seen in 19452 true positives, 3369 false positives, and 507 NAAs.
offer has been seen in 2654 true positives, 98 false positives, and 10 NAAs.

That didn't work; is it possible to blacklist a multi-word keyword?