Feature/support nested captures

It's nice to be able to group captures by test suite. It may also be useful to Alon.

I'm concerned this is going to break thumbnails in existing spook run reports. Given the idea is to view the images via the spook server output, I'm not sure of the value of the grouping.

I'll refactor to prefix basename with thumb. then to match existing
output.
On Thu, Aug 20, 2015 at 1:03 PM, Matthew Hadley<EMAIL_ADDRESS>wrote:

I'm concerned this is going to break thumbnails in existing spook run
reports. Given the idea is to view the images via the spook server output,
I'm not sure of the value of the grouping.
—
Reply to this email directly or view it on GitHub
https://github.com/creativelive/spook/pull/5#issuecomment-133155684.

 Please print this email immediately. And then burn
it.

Any change to the path (nested directory, filename change, etc)  is going to have this problem, as the files have already been written to disk, long ago.

This will yield the same output for any single directory path, but now has
the capability of writing to subdirectories, which before would try to
write to a nonexistent directory and fail. This is just allowing writing to
subdirectories if the path specified when calling capture contains one,
rather than moving thumbnails around.
On Thu, Aug 20, 2015 at 2:51 PM, Matthew Hadley<EMAIL_ADDRESS>wrote:

Any change to the path (nested directory, filename change, etc) is going
to have this problem, as the files have already been written to disk, long
ago.
—
Reply to this email directly or view it on GitHub
https://github.com/creativelive/spook/pull/5#issuecomment-133188484.

 Please print this email immediately.  Please print this email immediately.

Does explain why I wasn't aware of it. I happen to be using node 0.12.5
locally, which is why it worked. I'll revert to the previous approach.
On Thu, Aug 20, 2015 at 4:05 PM, Matthew Hadley<EMAIL_ADDRESS>wrote:

@joshuafcole https://github.com/joshuafcole turns out path.isAbsolute
isn't on node 0.10 :( looks like it's on 0.12.
—
Reply to this email directly or view it on GitHub
https://github.com/creativelive/spook/pull/5#issuecomment-133207512.

 Please print this email immediately. And then burn
it.

Can you move the dbd change out of this PR and leave it for #4? Let's just make this about the thumbs. I've tested that change and it seems good. I'm just looking into lint issues

Will do

Thanks @joshuafcole - I'll merge and cleanup

$ npm publish
+<EMAIL_ADDRESS>


Make handle_request take a &mut Write instead of a closure

In normal use, this is a UnixStream; in tests, this is a Vec.
Seems a bit easier to follow the logic.

Not sure if we want to do this or just have the handler return a Vec (or even a Vec<Vec>, honestly, which I think would be fine and would continue to avoid the extra copy).

Oh I missed #19, which conflicts with this.

wanna close in favor of #19?


Move definitions of datatypes and tokens to their proper namespace

Messages that use the ff_system namespace:

Org registration
Node registration
Namespace definition

Messages that use whatever namespace is specified in the API request path:

Everything else

Codecov Report

Merging #312 (f7e8afc) into main (04cd718) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head f7e8afc differs from pull request most recent head 7c8bd15. Consider uploading reports for the commit 7c8bd15 to get more accurate results

@@            Coverage Diff             @@
##              main      #312    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files          224       229     +5
  Lines        12387     12562   +175
==========================================
+ Hits         12387     12562   +175

Impacted Files
Coverage Δ

internal/broadcast/manager.go
100.00% <ø> (ø)

internal/broadcast/datatype.go
100.00% <100.00%> (ø)

internal/broadcast/definition.go
100.00% <100.00%> (ø)

internal/broadcast/namespace.go
100.00% <100.00%> (ø)

internal/broadcast/tokenpool.go
100.00% <100.00%> (ø)

internal/events/aggregator.go
100.00% <100.00%> (ø)

internal/networkmap/register_node.go
100.00% <100.00%> (ø)

internal/syshandlers/syshandler.go
100.00% <100.00%> (ø)

pkg/fftypes/event.go
100.00% <0.00%> (ø)

pkg/fftypes/message.go
100.00% <0.00%> (ø)

... and 16 more

Continue to review full report at Codecov.

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

Re-running the build because it failed due to this bug: https://github.com/hyperledger/firefly/issues/265

Re-running the build because it failed due to this bug: https://github.com/hyperledger/firefly/issues/265

Looks good, thanks for making those adjustments.


build accept array

Clear and concise description of the problem
marketing and admin fe in same project. marketing page use way less deps, admin page needs a lot, use multi build to separate chunks, prevent marketing page load too much
marketing page assets, the size will not change

one admin page assets, the size will become larger when import not

multi builds for different pages
Suggested solution
build accept array
Alternative
use multi config like

Additional context
rollup accept array like
export default []

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

If I remember correctly, we already got this feature request in the past
But we (the team) decided that users should use monorepo instead
In other words: we don't want to support this
Sorry :slightly_frowning_face:
@patak-js Correct me if I'm wrong, otherwise close this issue

But I think this is "monorepo"
structure like

just in one package, different type of page will need different sub modules, but manual chunk is hard, multi build allowed "chunk by page".

See https://github.com/vitejs/vite/issues/2039#issuecomment-779356090, and https://github.com/vitejs/vite/issues/4164. We are trying to keep complexity low in Vite core, and this feature request can be implemented using multiple config files (you can extract shared code out to reuse). Or you can use env variables and a single config.


How to draw a grid feature map

Thank you for your work and how to draw a grid feature map?

Not implemented out of the box, but you can use tikz library(tex) to create a grid on any block.


[BUG] Longhorn is very, very slow on HDD (e.g. 3x slower even with one local replica)

Hi thanks for the storage solution! However, it seems very very slow. For example, I run sysbench on a folder that is mounted via hostPath:
root@benchmark-0:/test/pvc# cd /test/host-data-disk
root@benchmark-0:/test/host-data-disk# sysbench fileio --file-total-size=15G --file-num=1 --file-test-mode=rndrw --time=300 --max-requests=0 prepare ; sysbench fileio --file-total-size=15G --file-num=1 --file-test-mode=rndrw --time=300 --max-requests=0 run
sysbench 1.0.17 (using bundled LuaJIT 2.1.0-beta2)

1 files, 15728640Kb each, 15360Mb total
Creating files for the test...
Extra file open flags: (none)
Creating file test_file.0
16106127360 bytes written in 133.00 seconds (115.49 MiB/sec).
sysbench 1.0.17 (using bundled LuaJIT 2.1.0-beta2)

Running the test with following options:
Number of threads: 1
Initializing random number generator from current time

Extra file open flags: (none)
1 files, 15GiB each
15GiB total file size
Block size 16KiB
Number of IO requests: 0
Read/Write ratio for combined random IO test: 1.50
Periodic FSYNC enabled, calling fsync() each 100 requests.
Calling fsync() at the end of test, Enabled.
Using synchronous I/O mode
Doing random r/w test
Initializing worker threads...

Threads started!

File operations:
    reads/s:                      2307.86
    writes/s:                     1538.57
    fsyncs/s:                     38.47

Throughput:
    read, MiB/s:                  36.06
    written, MiB/s:               24.04

General statistics:
    total time:                          300.0051s
    total number of events:              1165492

Latency (ms):
         min:                                    0.00
         avg:                                    0.26
         max:                                  704.32
         95th percentile:                        0.83
         sum:                               299310.16

Threads fairness:
    events (avg/stddev):           1165492.0000/0.00
    execution time (avg/stddev):   299.3102/0.00

Then, I run the same thing, this time on a PersistentVolume, whose PVC has storage class handled by longhorn:
root@benchmark-0:/test/pvc# sysbench fileio --file-total-size=15G --file-num=1 --file-test-mode=rndrw --time=300 --max-requests=0 prepare
sysbench 1.0.17 (using bundled LuaJIT 2.1.0-beta2)

1 files, 15728640Kb each, 15360Mb total
Creating files for the test...
Extra file open flags: (none)
Creating file test_file.0
16106127360 bytes written in 136.71 seconds (112.36 MiB/sec).
root@benchmark-0:/test/pvc# sysbench fileio --file-total-size=15G --file-num=1 --file-test-mode=rndrw --time=300 --max-requests=0 run
sysbench 1.0.17 (using bundled LuaJIT 2.1.0-beta2)

Running the test with following options:
Number of threads: 1
Initializing random number generator from current time

Extra file open flags: (none)
1 files, 15GiB each
15GiB total file size
Block size 16KiB
Number of IO requests: 0
Read/Write ratio for combined random IO test: 1.50
Periodic FSYNC enabled, calling fsync() each 100 requests.
Calling fsync() at the end of test, Enabled.
Using synchronous I/O mode
Doing random r/w test
Initializing worker threads...

Threads started!

File operations:
    reads/s:                      628.59
    writes/s:                     419.06
    fsyncs/s:                     10.48

Throughput:
    read, MiB/s:                  9.82
    written, MiB/s:               6.55

General statistics:
    total time:                          300.0087s
    total number of events:              317448

Latency (ms):
         min:                                    0.00
         avg:                                    0.94
         max:                                  676.27
         95th percentile:                        1.32
         sum:                               299753.51

Threads fairness:
    events (avg/stddev):<PHONE_NUMBER>/0.00
    execution time (avg/stddev):   299.7535/0.00

As you can see, it is much much slower.
I wonder what am I doing wrong?

@fzyzcjy
Thanks for the benchmarking. The latency in engine to replicas results in the slow performance. We are still working on performance improvement.
Currently, Longhorn is suitable for the SSD storage.

@derekbit Hi thanks for the reply. So may I know when will it be faster? It seems to be the most lightweight storage provisioner and is quite promising.

Argh. It drives me insane how slow Longhorn is on HDD's. I feel like x3 1TB 7200 RPM disks in a RAID 0 doesn't help much at all.
Simply the way Longhorn is designed by COMPELTETLY rebuilding the data any time there's a problem makes me long for Ceph, why can't it checksum/reuse actual data bits!? But because of Monitor instability and needing 3/5 monitors and the fact that it blew up on me and has only mirroring to external Ceph cluster made me settle for Longhorn, begrudgingly

@voarsh2 Ah... So how did you solve it?

@voarsh2 Ah... So how did you solve it?

I wish I did...... The only thing that has made me stick with Longhorn is the S3 compatible backups.... and there's no quorum.... otherwise I'd be rooting for Ceph.
I will review SSD's in the future, but it simply isn't in my budget, especially since I have several TB's of data.
Even 2-10GB volumes take forever to rebuild. The only solution I have at the moment is to split up your volume didn't into "sub" volumes and mount volumes within volumes so that the data per volume is smaller which can help with restoring and rebuilding. You'd just need to remove the bad volume if you're completely restoring and the workload can (depends on your app) continue with that data gone....
Databases (especially Maria Galera) is especially painful as Longhorn doesn't support TRIM, so when it drops and recreates table the size just grows and grows. I find myself frequently deleting volumes and recreating them to reclaim space and rebuild times....

That sounds like a painful experience... :(

@fzyzcjy Thanks for the benchmarking. The latency in engine to replicas results in the slow performance. We are still working on performance improvement. Currently, Longhorn is suitable for the SSD storage.

No, it's not. It's insanely slow on SSD as well. I just benchmarked.

This pretty much sums up my issue here, getting some strange results when I run tests on host disk and the LVM for Longhorn (which is also on the same physical disk): https://github.com/longhorn/longhorn/discussions/4186


When stopping or restarting a run with PyCharm, shell refuses to close

Weights and Biases version: 0.8.36
Python version: Python 3.7.5
Operating System: CYGWIN_NT-10.0

Description
There's no real error, but it's an annoying issue I run into when I use wandb with PyCharm all the time. When I'm done with a run that I don't care about, or don't need the run synced (or I forget I'm using wandb with this issue and just restart anyway), if I click the restart or stop button for the Python shell in PyCharm I get this error:
ConnectionResetError: [WinError 10054] An existing connection was forcibly closed by the remote host
(full exception: https://pastebin.com/0weX5Lh7)
It wouldn't be a huge issue except when this occurs I cannot stop or restart the Python shell within PyCharm, it remains open in PyCharm, stuck like that. So when I want to start training, there's a Python process that's taking up system and GPU RAM because it refuses to shut down from PyCharm. I end up having to use Task Manager to shut down all the Python processes because 3 or 4 accumulate after a while, but PyCharm restarts Python processes stopped by Task Manager, so they all restart at once.
What I Did
Use the stop or restart buttons in PyCharm to restart the current run without issuing a Keyboard Interrupt and waiting for it to sync.

Ideal Behavior
What would be great is for wandb to ignore any errors about not syncing a run if the user shuts down the Python shell manually and to let the shell stop fully.

ccing @raubitsj — we're working on a new beta of the Weights & Biases client that improves support for environments like Windows. Would you be interested in giving it a try?

Join the Slack forum and go to the wandb-cling channel.
Install CLI-NG following directions from the GitHub repo.
Try tracking a model with the new client, no code changes necessary.

Message us in the wandb-cling channel— we’d love to hear any questions or feedback.

Excellent! wandb-ng works as expected within PyCharm compared to the normal build. It takes a few seconds to restart or stop once I press either button, but I'm guessing it's syncing the run in the background and waiting for it to complete. Much nicer response than not allowing me to close the shell at all and throwing an error. Thanks!

Hey @ShaneSmiskol
We are closing this issue due to the inactivity of the thread. Please feel free to open it if the issue persists :smile:


test: arch: arm: arm_interrupt: clear FPSCR register in ISR

test: arch: arm: arm_interrupt: clear FPSCR register in ISR
Clear Floating Point Status and Control Register (FPSCR),
in case FPU IRQ is selected by the test as "Available IRQ line"
Fixes #31982

Note: I am not sure about the switches used.
Other switches may be more appropriate.

Though this seems to fix your issue, @ABOSTM , for a proper fix for FPU_SHARING in this test, we also need to get #32041 in. We could do this post 2.5.0 release if @nashif does not want to merge that now. I've not noticed any failures of this test in cortex-m platforms so #32041 could wait, perhaps


UnicodeDecodeError: 'cp932' codec can't decode byte 0x87 in position 47: illegal multibyte sequence

https://github.com/seigot
https://github.com/seigot/tetris/commit/886badcae40958fec9f223347c5641b8f9dcb7f1
PS C:\Users\staka\Desktop\work\tetris> python.exe .\start.py -m predict_sample -l2 -t5 --predict_weight .\weight\DQN\sample_weight.pt
game_level: 2
game_time: 5
RANDOM_SEED: -1
IS_MODE :predict_sample
OBSTACLE_HEIGHT: 0
OBSTACLE_PROBABILITY: 0
USER_NAME: window_sample
SHAPE_LIST_MAX: 6
BLOCK_NUM_MAX: 180
RESULT_LOG_JSON: result.json
TRAIN_YAML: config/default.yaml
PREDICT_WEIGHT: .\weight\DQN\sample_weight.pt
Python 3.10.9
CompletedProcess(args='python --version', returncode=0, stderr='')
Traceback (most recent call last):
  File "C:\Users\staka\Desktop\work\tetris\game_manager\game_manager.py", line 267, in timerEvent
    self.nextMove = BLOCK_CONTROLLER_TRAIN.GetNextMove(nextMove, GameStatus,yaml_file=self.train_yaml,weight=self.predict_weight)
  File "C:\Users\staka\Desktop\work\tetris\game_manager\machine_learning\block_controller_train_sample.py", line 499, in GetNextMove
    self.set_parameter(yaml_file=yaml_file,predict_weight=weight)
  File "C:\Users\staka\Desktop\work\tetris\game_manager\machine_learning\block_controller_train_sample.py", line 62, in set_parameter
    cfg = self.yaml_read(yaml_file)
  File "C:\Users\staka\Desktop\work\tetris\game_manager\machine_learning\block_controller_train_sample.py", line 40, in yaml_read
    cfg = yaml.safe_load(f)
  File "C:\Users\staka\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\yaml\__init__.py", line 125, in safe_load
    return load(stream, SafeLoader)
  File "C:\Users\staka\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\yaml\__init__.py", line 79, in load
    loader = Loader(stream)
  File "C:\Users\staka\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\yaml\loader.py", line 34, in __init__
    Reader.__init__(self, stream)
  File "C:\Users\staka\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\yaml\reader.py", line 85, in __init__
    self.determine_encoding()
  File "C:\Users\staka\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\yaml\reader.py", line 124, in determine_encoding
    self.update_raw()
  File "C:\Users\staka\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\yaml\reader.py", line 178, in update_raw
    data = self.stream.read(size)
UnicodeDecodeError: 'cp932' codec can't decode byte 0x87 in position 47: illegal multibyte sequence
error: subprocess failed.
PS C:\Users\staka\Desktop\work\tetris>

diff --git a/game_manager/machine_learning/block_controller_train_sample.py b/game_manager/machine_learning/block_controller_train_sample.py
index a1cceff..00b428c 100644
--- a/game_manager/machine_learning/block_controller_train_sample.py
+++ b/game_manager/machine_learning/block_controller_train_sample.py
@@ -36,7 +36,7 @@ class Block_Controller(object):

     #パラメータ読み込み
     def yaml_read(self,yaml_file):
-        with open(yaml_file) as f:
+        with open(yaml_file, encoding='utf-8') as f:
             cfg = yaml.safe_load(f)
         return cfg

diff --git a/game_manager/machine_learning/block_controller_train_sample2.py b/game_manager/machine_learning/block_controller_train_sample2.py
index d10f8ee..c91e330 100644
--- a/game_manager/machine_learning/block_controller_train_sample2.py
+++ b/game_manager/machine_learning/block_controller_train_sample2.py
@@ -36,7 +36,7 @@ class Block_Controller(object):

     #パラメータ読み込み
     def yaml_read(self,yaml_file):
-        with open(yaml_file) as f:
+        with open(yaml_file, encoding='utf-8') as f:
             cfg = yaml.safe_load(f)
         return cfg


setup ci/cd pipeline using jenkins

Set up CI/CD pipeline using Jenkins
This commit introduces the initial setup for a CI/CD pipeline using Jenkins. The pipeline is configured to automate the build, test, and deployment processes of our project. It includes:

Installation of Jenkins and necessary plugins.
Configuration of Jenkins URL and admin user.
Creation of a Jenkins job with a Pipeline script from SCM (Git).
Addition of a Jenkinsfile defining build, test, deploy stages.
Instructions for triggering and monitoring the pipeline.
Troubleshooting guide for common Jenkins-related issues.

This CI/CD setup will streamline our software delivery process, improve code quality, and enhance team collaboration. Please review and merge these changes to integrate Jenkins into our project workflow.

@litesh1123 please mention the issue number, so I can understand which issue you worked on, and it helps me to add the label.

@mdazfar2 ok sir I will issue number and issue link

Issue link
https://github.com/mdazfar2/HelpOps-Hub/issues/27


[Feature 6] Train

Train package handles Train class, Station Class, subway map, ticket tracking, (Jarett + Charles + Matt)

Train modelling system already finished


[Question] Any method to create a event like DLL_PROCESS_DETACH?

I wanna stop a memory leak, no ideia to do this without a event while end the process.

https://github.com/3F/DllExport/issues/45#issuecomment-317802099
https://github.com/3F/DllExport/issues/5

Therefore, the easy way to aggregate control of this manually via Observer pattern etc. (unmanaged / managed side)
Also if you have logic from unmanaged code that will be executed with managed env, try to use Conari.

Thank you, this Conari looks interesting, should I close the issue or keep it open for future reference?

Leave it open if your problem still is actual.

Opened issues may be reconsidered later again by me or anyone else.
After closing it still may be referenced & commented without any problems.

@marcussacana  just noticed your new edit (please note, github will never send notification for edit)
I do not recommend to use AppDomain.ProcessExit event because it doesn't give guarantee for this operation.
Also, the timeout settings available only for unmanaged api, e.g.:
ICLRPolicyManager* clrpm;
if(FAILED(pControl->GetCLRManager(__uuidof(ICLRPolicyManager), (void**)&clrpm))) {
    return -1;
}

// https://docs.microsoft.com/en-us/dotnet/framework/unmanaged-api/hosting/eclroperation-enumeration
clrpm->SetTimeout(OPR_ProcessExit, 30000); //30sec

Thus, try to implement any your custom manager. I don't know what you do, but for example:

Extract a common interface like IUnmanagedResource which will contain methods for allocation and  release, like Alloc(), Free() etc.
Implement a common manager that will aggregate all IUnmanagedResource and provide a common methods through pointer to struct for other side.

Define a Host side that will manage resources: if clr side is unstable (domain may be destructed in any time without notice the unmanaged side) you should share it from unmanaged for managed side but it can be implemented vice versa for any allocation of resources.
The managed module can request allocation of resources from unmanaged side and access to this data via pointer to structures etc. Conari also may help to work with this data even without declaration of this structures at all, for example:
unmanaged C++
    struct TSpecB
    {
        bool d;
        TSpecA* s;
    };

    struct TSpecA
    {
        int a;
        int b;
    };

    A->a = 4;
    A->b = -8;
    B->d = true;
    B->s = TSpecA*;

Conari:
IntPtr ptr = ...

var TSpecBPtr = NativeData
                    ._(ptr)
                    .t<bool>("d")
                    .t<IntPtr>("s")
                    .AlignSizeByMax;

...
dynamic dlr = TSpecBPtr.Raw.Type;

IntPtr addrA = dlr.s;
Assert.AreEqual(true, dlr.d);

// B->A

var TSpecAPtr = NativeData
                    ._(addrA)
                    .align<Int32>(2, "a", "b");

dynamic s = TSpecAPtr.Raw.Type;

Assert.AreEqual(4, s.a);  // B->s->a
Assert.AreEqual(-8, s.b); // B->s->b

Therefore, even if domain of some this loaded module will be destroyed (unexpectedly for unmanaged side) you can still release it via known IUnmanagedResource methods.

I closed this issue. Please reopen if this still is actual.
About:

I wanna stop a memory leak,

You can also look #78


:pencil: Adds limit + offset to inventory item calls

I ran into this trying to import an inventory of >100 items. Happy to refactor if you have a preference.

Thanks @jefftriplett !


added gcp support for go-api-boot

Added gcp support for go-api-boot, I have added following features in this PR:

Modified the existing LoadSecretsIntoEnv(useAzureKeyvault bool) => LoadSecretsIntoEnv(useAzureKeyvault bool, useGCPSecrets bool). All secrets of a project are loaded by the function, it is dependent on the projectId environment var. Authentication is handled by ADC.

Added UploadStream function for GCP,  which works similar to the UploadStream function written for azure buckets. The function doesn't handle access for fine grained buckets.

Features remaining to be added:

Presigned URLs: I'll soon add support for presigned URL, I faced some minor issues so resolving that.

Good change, consistent with current practice. However, I guess from beginning it should have been architected little differently. Better late than never, I guess below changes woud make it easier for framework user:

Have interface cloud.go with functions - LoadSecrets, UploadToStorage and GetPresignedUrlKey in package cloud.
Let there be three implementations of the interface in form of struct - aws, gcp and azure in the same package cloud.
Framework user should be able to use cloud as:     var cloudFns Cloud = gcp{} // or aws{} or azure{}
     cloudFns.LoadSecrets()
     cloudFns.UploadToStorage()
     ...

This way, just the cloud type has to be changed in dependency injection of framework user instead of renaming methods etc. etc. and framework user can switch cloud anytime.


Can't find right version of glibc with most recent nix rust toolchain (libwasm_bindgen_macro-9c397868eee48ed6.so).

Describe the Bug
On nix, when I try to compile anything with the wasi target with the wasm-bindgen library, I get an error.
Steps to Reproduce

Install the rust toolchain with nix (nix-env -iA nixpkgs.rustup)
Install "cargo-wasi" (cargo install cargo-wasi)
follow this tutorial

Given how reproducible is nix, I think this is enough.
For completeness, here is my Cargo.toml:
[package]
name = "demo"
version = "0.1.0"
authors = ["me"]
edition = "2018"

[lib]
crate-type = ['cdylib']

[dependencies]
wasm-bindgen = "=0.2.74"
# I get this error with every version of wasm-bindgen ...

here is the verbose error I get with cargo wasi build --release --verbose:
https://pastebin.com/TMUAEs5Q
Expected Behavior
The compilation of this crate to any target should not depend on a specific glibc version, or at least provide the exact one needed.
Apparently the error comes from this object file: libwasm_bindgen_macro-9c397868eee48ed6.so
Actual Behavior
I can't compile to this specific target.
I don't know if this is specific to this target, but I can use wasm-pack without any issue for example.
Additional Context
My nix installation is on archlinux, which has the last version of glibc (2.33-5).
The rustup toolchain from nix uses an older version (2.32-48)

This was really not the fault of wasm-bindgen, sorry :(


Retry Interval doesn't work for LocalActivity, default value is used instead

Retry interval doesn't work for LocalActivity.
The problem is that in LocalActivityWorker.class there is a method "handleLocalActivity", which sets retryPolicy.
in line 255 there is a check:
if (retryPolicy.getMaximumInterval().getNanos() > 0) {         roBuilder.setMaximumInterval(             ProtobufTimeUtils.toJavaDuration(retryPolicy.getMaximumInterval())); }
The problem is that getNanos() always returns 0, so default value is used. It doesn't matter if use MethodRetry annotation or specify RetryOptions via setRetryOptions method of LocalActivityOptions. (I do specify nanos in Duration.ofSeconds(30, 1) like so)
Specifications

Version: 1.7.1
Platform: 1.7.1

Confirm. Thanks for the report!


Add additional safety check when mapping image vulnerabilities to image metadata

Description
A detailed explanation of the changes in your PR.
Feel free to remove this section if it is overkill for your PR, and the title of your PR is sufficiently descriptive.
Checklist

[ ] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why
you did not do so. Valid reasons include, for example, "CI is sufficient",
"No testable changes". Feel free to attach JSON snippets, curl commands,
screenshots.
In addition to reviewing your code, reviewers must also review your testing
instructions and make sure they are sufficient.

Current dependencies on/for this PR:

master

PR #6106

PR #6169

PR #6196   👈

PR #6165

PR #6112

This comment was auto-generated by Graphite.


Experimental - Move JS and CSS to Webpack build

@alexsoble This is more experimental, let me know what you think.  It builds on top of https://github.com/codeforamerica/somerville-teacher-tool/pull/335, and adds moves the JS and CSS into a separate folder and container, where Webpack builds them and Rails can just consume.
This came up because I noticed that loading so many assets in development mode takes quite a bit of time, 15 seconds to load the page sometimes:

In Web Inspector it looks like the bottleneck is the server trying to serve all the individual asset files:

So this PR adds a new container that builds the JS and CSS assets with webpack into a single bundle that can be used in development.  This moves those files out Rails' asset pipeline and improves the performance quite a bit, and it paves the way to take advantage of other front-end tooling going forward (e.g., transpilation from ES6, JSX for React, hot reloading).  And while the single asset file helps optimize for loading all the JS and CSS into the browser, webpack also support sourcemaps so the development experience is the same as it would be with individual files:

The webpack container mounts the webpack folder with all the JS and CSS assets.  For the JS, it's a straight port and so everything is still global and attached to window.  We can break that into modules with new UI work, and will be helpful when introducing a JS framework.  For the CSS, it's also a straight port.  The only difference was removing the asset_path helpers for images, which regresses the asset digest feature in Rails.  I didn't look at how that would work for production deploys yet.
This cut the development load time down quite a bit:

The jQuery UI assets were the remaining bottleneck.  I swapped the vendored Ruby gem for pre-built CSS and JS artifacts, and this cut down the load time even further, to under 2 seconds:

So the final state of assets of this PR is: all JS and CSS in webpack/, except for jQuery UI JS, CSS and images, which are all still in Rails for now.
For Teaspoon, I also shimmed in the built JS file so that continues to work as before.
No visual regressions, eg:
Before:

After:

I'm curious to hear if this seems useful.  It's a little tied to the docker development workflow, so I could pull those apart.  Or I can figure out how the build would work for production deploys if this seems useful, and I'm happy to go in a different direction altogether if it makes more sense. :)

This is still experimental, and would need to add an asset build step to the Travis build and production deploys (just shared here for input and discussion).

Fiddling with how the Travis build setup works over here: https://github.com/kevinrobinson/somerville-teacher-tool/pull/1

Baseline comparison for installing the project directly on my laptop:

So the performance regressions from adding VirtualBox/Docker are pretty severe!
From reading around, this is mostly do to the way volumes are mounted.  There are a few projects that try to help this, notably https://github.com/adlogix/docker-machine-nfs and http://www.ybrikman.com/writing/2015/05/19/docker-osx-dev/, and I'm most familiar with the approach of using rsync from https://github.com/twitter-fabric/galley.  I first tried using docker-machine-nfs, since it's a oneline command, and here's what the impact is using the asset pipeline setup from  feature/dockerize-rails:

And here it is using the Webpack build for this commit:

And after a few other iterations over at https://github.com/kevinrobinson/somerville-teacher-tool that are on master:

In summary, read performance is pretty bad on VirtualBox shared volumes, but this can be improved quite a bit by switching to NFS with a one line command.  So I'll move the instructions for docker-machine-nfs to the README over in https://github.com/codeforamerica/somerville-teacher-tool/pull/335.  The Webpack build and bundling process is great for separate reasons, and also does help development performance a bit too.
Separately, I think it makes sense to close this PR for now.    This work was more useful for me to just wrap my head around everything, but moving forward we can pull in separate pieces from there if they become useful (eg, Webpack for JS modules or JSX, deploying to EC2 instead of Heroku).

@alexsoble From our conversation earlier today, let's close this and focus on the folder structure and refactoring the checks for classes on the body tag first.  There's still lots of value in switching to Webpack, but since we decided to go forward with https://github.com/codeforamerica/somerville-teacher-tool/pull/340 and keep some server-side rendering, there's no forcing function for using Webpack yet.
If we want to do this in the future, there's code in https://github.com/kevinrobinson/somerville-teacher-tool/pull/24 that sets up Babel with Webpack to use JSX and ES6.  I'm closing that as well, and we can pull in as needed.


Working with java synchronization

Article checklist
Attention
Our Peer Reviewer and Content Moderator teams do NOT provide any revisions services. All revisions and edits should be completed on your own forked repo (as to not take up room in the queue) in order for our team to review them all in a timely manner.
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.

As a rule of thumb - please be sure to only submit articles (pull requests) that are fully polished and ready to be published. Be sure to go through our resources documents for extra and 3rd party (vetted) resources to help improve overall technical writing.

Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels, under 300KB in size, and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[x] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[x] Have you checked your article for readability? - Tool: Hemmingway
[ ] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[x] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #5936

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

Plagiarism check complete

I will be closing this pull request while you implement my changes. When you are done, please make a new pull request with the changes and ping me in the comments of that new pull request. If you need assistance, feel free to message me via slack.


Fix Dockerfile in CAN Feeder

Set Patchelf to hardcoded version

Wouldn't it be better to define these pip packages in the requiremens.txt file?

Wouldn't it be better to define these pip packages in the requirements.txt file?

It might depend on what we want to include in requirements.txt and  requirements-dev.txt, i.e. what is the purpose/scope of the files. patchelf is not needed for native builds, so does it qualify for the existing files. And if it is only needed for build, is dev a better location?

While at it, last line of file
CMD ["./dbcfeeder-exe"]

Should be changed to ENTRYPOINT (so you can give parameters to feeder when starting the container)

Wouldn't it be better to define these pip packages in the requirements.txt file?

It might depend on what we want to include in requirements.txt and requirements-dev.txt, i.e. what is the purpose/scope of the files. patchelf is not needed for native builds, so does it qualify for the existing files. And if it is only needed for build, is dev a better location?

In my opinion it does not belong in requirements.txt for sure. If it belongs to requirements-dev.txt depends on the scope of this file but I think it does not belong in either of this txt files as it is no "real" requirement. It is not necessarily nedded to build the code. Only if you want to use staticx and the generation of an executable.

While at it, last line of file
CMD ["./dbcfeeder-exe"]

Should be changed to ENTRYPOINT (so you can give parameters to feeder when starting the container)

Schould then also be changed in https://github.com/eclipse/kuksa.val.services/pull/54 ?


Accordion: Prevent AccordionItem from opening when property is set

Describe what feature you'd like. Pseudo-code, mockups, or screenshots of similar solutions are encouraged!
Just like how locked={true} on Steps prevents Steppers to continue, it would be great to be able to prevent specific AccordionItems from opening.
What type of pull request would this be?
Enhancement
Any links to similar examples or other references we should review?
No response

Sounds more a disabled state, correct? Can you elaborate on the use case. I'm just curious.

Sounds more a disabled state, correct?

Yes.

Can you elaborate on the use case. I'm just curious.

One use case would be that users can take on modules where they have to complete specific tasks. However, some tasks may depend on other tasks to be finished before they can be completed. Users will be able to complete tasks by submitting their result from within the AccordionItems content. (Not implemented yet)
The other use case is locking some items when the user does not have the required subscription to access them. (I am still not sure if I want to go down that route but it is a possibility)

Hmm, seems like a scenario that the Stepper solves. Any particular reason you went with an Accordion instead?

Thanks for sharing. This does seem to have some overlap with the role of the Stepper component.  I can't say I've ever seen someone use an Accordion in that fashion.
The first thing we'll need to do is determine if this works within the guidelines provided by the WAI-ARIA APG guidelines:
https://www.w3.org/WAI/ARIA/apg/patterns/accordion/
At a glance, the only seem to describe the opposite behavior -> if the panel is open and can't be closed:

If the accordion panel associated with an accordion header is visible, and if the accordion does not permit the panel to be collapsed, the header button element has aria-disabled set to true.

@mc-0bit Sorry for the delay in returning to this. The v1.0 launch ended up taking most of our attention.
After reviewing for a bit I don't think we'll be able to implement this as requested. Per the ARIA APG guidelines mentioned above, only the opposite behavior seems to documented (set disabled to keep open). For Skeleton we prioritize a11y, which means we're subject to the guidelines as stated.
The good thing is these components are all open source. If you wish, you can copy an instance of the Accordion/AccordionItem components into your local project, modify the behavior as desired, then utilize that version instead.
You can find the source for these here:
https://github.com/skeletonlabs/skeleton/tree/dev/src/lib/components/Accordion
Alternatively I might suggest reviewing the Stepper component or consider building a custom component of your own.

I ended up just editing the title and content off the accordion items when it is not available, but still letting the user interact with them. This is probably the way disabled accordion items are supposed to behave per ARIA guidelines.


allow ssh transport protocol for a git module spec

Fix regression. Issue description: #3237

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.mcarrolle seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the PR, i just started the tests on it. Assuming those pass I think we can get this merged, can you squash your commits and format the commit message according to https://github.com/puppetlabs/bolt/blob/main/CONTRIBUTING.md#pull-requests (i think you can use !bug)?

Tests are passing, once the commit messages are formatted we will merge


Incorrectly HTML encoded text in the description of this property

[Enter feedback here]

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

ID: 134deede-600a-05a1-07a3-861652c44284
Version Independent ID: ae907bbd-e90c-7846-3f32-8bbacef5f03c
Content: Site.Enabled Property (Microsoft.Azure.Management.WebSites.Models) - Azure for .NET Developers
Content Source: xml/Microsoft.Azure.Management.WebSites.Models/Site.xml
Service: app-service
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

This is ref doc which auto-gen by docs team


Sort order changes on rowsUpdate.

Please refer the pen for the issue. http://codepen.io/ashishku/full/vLmybX/
This happens for the first click only.

Changed the title... i don't think clicking has anything to do, it's rowsUpdate which changes the order.


perf(ngOptions): don't render options before the first digest

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
perf
What is the current behavior? (You can also link to an open issue here)
see commit message
What is the new behavior (if this is a feature change)?
see commit message
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

Other information:
Previously, ngOptions would collect and render the options during linking
and then again immediately after the next digest passed, in order to have
the options ready when the select directive tries to render ngModel.
Since we are completely removing the options when they are updated, this means
we are essentially creating each ngOptions select twice after it is compiled.
This fix changes it so that ngOptions creates a noop version of the internal API
so that select can correctly try to render ngModel

I wanted to change this before, but Pete you had some reservations - maybe this time it'll be okay.

How confident are we that this is not a BC?
Won't this for example cause the model value to change for one digest?
What if someone is watching for changes?

Can you actually show that this has a measurable impact on performance?
Without it I would rather leave things as they are

I don't see a measurable impact. Probably because the rendering with documentFragment is very fast now. I mainly found it weird that we render the whole select twice after it has been created (since we aren't reusing options anymore).


Assets replaced with same filename don't trigger cache clearing

As per our discussion on Slack, an assets (image, in my tests) uploaded and replaced over an existing assets with the same filename does not trigger any Imager cache clearing functions, thus the Imager transformed cached image on the front-end does not get updated.

Pretty sure we have seen this too.

Forgot to write an update on this.
There is support for the assets.onReplaceFile event in Imager and has been for a while. I assumed that this also accounted for when you drag a file into Assets, and choose "Replace" when the folder already has a file with that name, not only when you choose "Replace file" from the element action menu. But, according to P&T, these are two different things: the latter is actually replacing the file on disk, whereas the first actually replaces the asset (with fields and everything).
There isn't a specific event for the first, because that's basically deleting one asset, and creating a new one. I think the only solution would be to actually delete transforms when an asset is deleted. I opted not to do this when I created Imager because that would mean that cached pages that used (non-cached) transforms that got deleted, would show broken images until the cache was updated. Not sure which scenario is the worst atm.

I ran into this and brought it to the attention of the developers — a fix will be out with the next release of Craft: https://github.com/craftcms/cms/issues/1761

https://craftcms.com/changelog#2-6-2984 includes this and is now released


[Feature request] Add ".." (go one direcory up) in directory listing

I was looking for something like http-file-server for a while and couldn't find a perfect solution. There are many tools like this and all of them miss some important features (like downloading a folder as zip).
http-file-server is almost perfect, but could you add ".." in directory listing to go to parent directory?

I made a fork which adds this for every folder: https://github.com/muller2002/http-file-server/blob/master/README.md
You have to build with go manually and have to navigate to the default go installtion path and then run http-file-server


Allow Gitea to run on POSIX shell (not relying on bash)

Gitea version (or commit ref): 1.5.1
Git version:  2.18.0
Operating system: Alpine Linux v3.8
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[x] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Not relevant

Log gist:

Description
As I found out during working around issues described in #4894, Gitea relies on bash being present on host system.
I think it should be beneficial to evaluate if it is possible to make Gitea compatible with POSIX compliant shells. This would drop Bash dependency and make Gitea more flexible and portable.

Did you try setting SCRIPT_TYPE in gitea configuration?
After doing this, do "Resynchronize pre-receive, update and post-receive hooks of all repositories." in gitea admin panel

I tried it with this in my app.ini:
[repository]
SCRIPT_TYPE = sh

Still, with busybox sh, I get this when pushing to repo:
halt: unrecognized option: c
BusyBox v1.28.4 (2018-07-17 15:21:40 UTC) multi-call binary.

Usage: halt [-d DELAY] [-n] [-f]

Halt the system

	-d SEC	Delay interval
	-n	Do not sync
	-f	Force (don't go through init)
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

And with dash I get this:
Enumerating objects: 9, done.
Counting objects: 100% (9/9), done.
Delta compression using up to 8 threads.
Compressing objects: 100% (5/5), done.
Writing objects: 100% (5/5), 530 bytes | 530.00 KiB/s, done.
Total 5 (delta 3), reused 0 (delta 0)
remote: env: can't execute 'bash': No such file or directory
To ssh://domain.tld/user/repo.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to 'ssh://domain.tld/user/repo.git

Resynchronize hooks and try with dash again

Oh, I missed that for dash. It does run on dash now, bit still no luck on busybox.
Thanks for the assistance!

Tested for both docker alpine:3.8 (under Ubuntu 18) and alpine-virt-3.8.0-x86_64.iso (under Virtualbox) - for both of them gitea 1.5.1 worked without problems under busybox sh (in both cases I user SCRIPT_TYPE = sh to make sh used in hooks). Checked with both openssh and internal gitea ssh server, had no problem with git push at all. Even tried auto-rejecting hook - and it printed message well.
Could not reproduce your "halt: unrecognized option: c" result.

Still I think gitea install script should check whenever bash is available and default to sh if not


Cannot reproduce BLEU score on test set

Hi,
I couldn't find a way in the code to reproduce the BLEU score of 38.97 you published in your paper on the test set of WikiSQL.
Can you please instruct me on how to reproduce it?
Thanks.

I have the same question. The format of WikiSQL seems to be different from the input format in the data/no_cycle folder. Any suggestion on creating the input for different dataset?

Dear All,
Please see our newly released graph4nlp library: https://github.com/graph4ai/graph4nlp, which have implemented many GNN methods like Graph2Seq and Graph2Tree models.


Allow loading from file-like object

I can't delegate all file-loading to tabulator on https://github.com/okfn/datapackage-py because I have to support non-tabular data as well. It would be good to be able to use tabulator just for the parsing.

Def. want this, yes.

BTW, this is not necessarily possible for all supported formats. But for CSV, JSON, yes.

DONE

It seems like this is no longer supported since topen is removed. Am I correct or is there another way I can provide a file-like object to read from?

Hi @michaelmior,
Have you tried to so with Frictionless - https://github.com/frictionlessdata/frictionless-py? It supports file-like object. Although, tabulator also should support it something lie stream = Stream(file-like)

@roll I figured it out although I did Stream(fille_like, scheme='stream'). I'll have to check out Frictionless. Thanks!


OrientDB static initialisation is not thread-safe

OrientDB Version: 2.2.12
Java Version: Oracle JDK 8u172
OS: macOS 10.13
Expected behavior
It should be possible to create two independent databases in the same JVM, even if this occurs at the same time on two different threads.
Actual behavior
We attempt to create two databases, and occasionally get errors such as:
java.lang.NullPointerException
	at com.orientechnologies.orient.core.engine.local.OEngineLocalPaginated.changeCacheSize(OEngineLocalPaginated.java:80)
	at com.orientechnologies.orient.core.config.OGlobalConfiguration$1.change(OGlobalConfiguration.java:114)
	at com.orientechnologies.orient.core.config.OGlobalConfiguration.setValue(OGlobalConfiguration.java:1032)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.configureDefaultDiskCacheSize(OMemoryAndLocalPaginatedEnginesInitializer.java:89)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.configureDefaults(OMemoryAndLocalPaginatedEnginesInitializer.java:63)
	at com.orientechnologies.orient.core.engine.OMemoryAndLocalPaginatedEnginesInitializer.initialize(OMemoryAndLocalPaginatedEnginesInitializer.java:52)
	at com.orientechnologies.orient.core.engine.local.OEngineLocalPaginated.startup(OEngineLocalPaginated.java:56)
	at com.orientechnologies.orient.core.Orient.startEngine(Orient.java:858)
	at com.orientechnologies.orient.core.Orient.loadStorage(Orient.java:466)
	at com.orientechnologies.orient.core.db.document.ODatabaseDocumentTx.<init>(ODatabaseDocumentTx.java:171)
	at com.orientechnologies.orient.core.db.OPartitionedDatabasePool$DatabaseDocumentTxPooled.<init>(OPartitionedDatabasePool.java:425)
	at com.orientechnologies.orient.core.db.OPartitionedDatabasePool$DatabaseDocumentTxPooled.<init>(OPartitionedDatabasePool.java:421)
	at com.orientechnologies.orient.core.db.OPartitionedDatabasePool.initQueue(OPartitionedDatabasePool.java:357)
	at com.orientechnologies.orient.core.db.OPartitionedDatabasePool.<init>(OPartitionedDatabasePool.java:116)
	at com.tinkerpop.blueprints.impls.orient.OrientGraphFactory.<init>(OrientGraphFactory.java:71)
	at com.tinkerpop.blueprints.impls.orient.OrientGraphFactory.<init>(OrientGraphFactory.java:52)

Steps to reproduce
Since it's a multi-threading issue, I don't have a reliable reproduction.
Investigation so far
If I look through the stack trace, for OEngineLocalPaginated.changeCacheSize, the null thing is surely readCache. You can tell that readCache would be null on construction, but that startup() has not yet been called.
Further down the stack, OMemoryAndLocalPaginatedEnginesInitializer.initialize is performing an unsafe static initialisation:
/**
  * Initializes common parts of memory and plocal engines if not initialized yet. Does nothing if engines already initialized.
  */
 public void initialize() {
   if (initialized)
     return;
   initialized = true;

   configureDefaults();

   OMemory.checkDirectMemoryConfiguration();
   OMemory.checkByteBufferPoolConfiguration();
   OMemory.checkCacheMemoryConfiguration();

   OMemory.fixCommonConfigurationProblems();
 }

In this case, initialized should not be set to true until after initialisation. But proper locking should probably be put in place so that multiple threads don't simultaneously try to initialise all this static state.
Current master appears to have the same issue:
  /**
   * Initializes common parts of memory and plocal engines if not initialized yet. Does nothing if engines already initialized.
   */
  public void initialize() {
    if (initialized)
      return;
    initialized = true;

    configureDefaults();

    OMemory.checkCacheMemoryConfiguration();
    OMemory.fixCommonConfigurationProblems();
  }

So I take it this has been fixed?

Hi @hakanai . We close old issues which were not been active for a long time. Seems like this issue is still actual for you, so I reopen it.

Hi,
This bug refer to "OEngineLocalPaginated" that has been removed from all the currently maintained release, and replaced with another component that seems to not have this problem, clonsing


Use @wessberg/rollup-plugin-ts + change output naming structure

Addresses #208 and #200.

Switch the output naming structure/convention. We are kind of forced to do that to make a better and more predictable experience, and integrating this plugin.
Update tsdx create according to new output structure; Plus, correct "package generation". Currently, if user type @hela/core in the prompt it will create core folder in the cwd and also will add to the generated package.json file a name field to be core instead @hela/core, which definitely isn't correct behavior.
Remove the "utils safePackageName" test.
Remove the safePackageName function, at all.
ESLint autofix is enabled on my VSCode, so ESLint removed the use strict on the tsdx-build.test.js, obviously according to the given eslint config and prettier.
Immediately before I started anything with just pnpm i on fresh branch, the pnpm's lockfile changed.

The only left is to update the babelPluginTsdx file, meaning to drop the rollup-plugin-babel dependency and just generate babel config and pass it as babelConfig option to the ts plugin. But keep in mind the ts plugin also automatically includes some plugins and does merging some default options.

Why are we changing the output format?

Why are we changing the output format?

For "reasons", the other PR has comments around that :) Or at least because such design decisions, problems and "features" appear in some other places/tools (referring the new "hook" option in the ts plugin). All this is just one simple example that may seem negligible, but this is happening for years in the ecosystem.


Turkish Localization for Logitech G810

What are you experiencing an issue with?

[ ] Aurora
[ ] Aurora supported game, (Fill in the game)
[ ] Aurora Wrapper
[ ] Aurora Profile
[ ] Aurora supported device, (Fill in problematic devices)
[ ] Aurora Scripts
[ ] Aurora Updater
[x] Aurora Lighting issue
[ ] Other, (Fill in another issue here)

What kind of an issue is it?

[ ] Crash
[ ] Performance problems
[x] Visual bug
[x] Localization issue
[ ] Enhancement suggestion
[ ] Device issue
[ ] Other, (Fill in another type of issue here)

Expected behavior:
In Interactive Layer type mode, 4 keys flashing/colouring etc. wrongly.
Actual behavior:
First of all, I love this program. Thank you for this bro o7
Like a said, i have Localization problem for "Ö", "Ç", ":" and ";" buttons.
This link will show you the Turkish keyboard layout = http://prnt.sc/f548td
OR
In Turkish Keyboard
"<" -- "Ö"
">" -- "Ç"
"?" -- ":"
" \ " -- ";"
I have only visual problem for only this 4 keys, my keyboard working nicely. So it's not critical but a little bit annoying :(
In International Keyboard:
Pressing "<" button, triggering "?" button.
Pressing ">" button, triggering " \ " button.
Pressing "?" button, triggering ">" button.
Pressing " \ " button, triggering "<" button.
How often does this problem occur?
This problem occurs every time.
What is the version of Aurora you are experiencing this issue with?
My version is beta v0.6.0b.
Does the previous version of Aurora have this issue?
Nope, I'm newbie.
My English is not perfect, sorry for this. I hope I could tell my problem. Have a nice day

When you say Pressing x button, triggering x button. Using "Pressing "<" button, triggering "?" button." does it mean when you press "<" on your keyboard the button displayed as "?" in Aurora is triggered?

@simon-wh  yes, that's right.


Whitespace after completion

I did notice that when adding completer, the console automatically insert a " " character at the end. This is particularly annoying with FileNameCompleter since I would want to complete (pressing TAB) many times before accepting the result
example code:
			.createInputPrompt() 			.name("folderWatcher").message("Cartella da monitorare") 			.addCompleter(new FileNameCompleter()) 			.addPrompt() 			;

Hi. Unfortuantely this is a question for Jline itself. The InputPromt in consoleUI is just a wrapper that uses ConsoleReader.readLine() for input. All the completer implementation is up to Jline.

Hi, thanks for the reply.
The issue is imho in the InputPrompt, the private reader variable is initialized as new ConsoleReaderImpl();
I see no chance to cutomize the instance, since it is private and has no accesor.
The space is authomatically added from the completitionHandler inside the ConsoleReader. The handler itself (CandidateListCompletionHandler) has a boolean property named printSpaceAfterFullCompletion
I tried with the help of a debugger to set it to false (the default is true) and this solve the problem.
Unfortunately I'm not familiar enough with consoleui to understand where to eventually insert a configuration option to disable the automathic space


Unable to upgrade to 24.3.0 or highter

🐛 Bug Report
I receive a 404 for @jest/fake-timers when I try to upgrade jest to 24.3.0 or higher (including up to the most recent build 24.5.0)
To Reproduce

Update the entry in your package.json file to either "babel-jest": "24.3.0", or "babel-jest": "^24.0.0",
npm install

Expected behavior
npm install runs without error.
Actual results
npm ERR! code E404
npm ERR! 404 Not Found<EMAIL_ADDRESS>
npm ERR!      /Users/hoffman/.npm/_logs/2019-03-25T16_01_48_265Z-debug.log

The package that 404s is published on the registry, this is a problem with npm, not Jest.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

If you're running into this, and until npm fixes this issue, you can do the following
git clone https://github.com/facebook/jest
# warning, this is a 204MB download of the entire jest repo
cd jest
git checkout v24.5.0
cd packages/jest-fake-timers
npm pack

This will generate a jest-fake-timers-24.5.0.tgz npm package locally that you can place in your app to install it first, and then install everything else in your app.
mv jest-fake-timers-24.5.0.tgz ~/myapp
cd ~/myapp
npm i jest-fake-timers-24.5.0.tgz
npm i

Hope this helps as an interim measure


Fix for WFCORE-5462, Upgrade to Bootable JAR plugin 5.0.0.Beta1

Issue: https://issues.redhat.com/browse/WFCORE-5462

retest this please

Core - Full Integration Build 10721 outcome was FAILURE using a merge of 71909543a2c840ba9f3e3b60fcfd0c0a34bac5bf
Summary: Exit code 1 (Step: Build & test full (Maven)) (new) Build time: 00:01:29

Core - Full Integration Build 10722 outcome was FAILURE using a merge of 71909543a2c840ba9f3e3b60fcfd0c0a34bac5bf
Summary: Exit code 1 (Step: Build & test full (Maven)) Build time: 00:01:21

@jfdenise thanks


Error: validation: chart.metadata.version is invalid

I'm trying to understand why my versioning doesn't work.
I keep getting "Error: validation: chart.metadata.version  is invalid"
Here's the latest results from the pipeline:
Error: validation: chart.metadata.version "1.0.20240930-093258.1-RELEASE" is invalid
Error: validation: chart.metadata.version "1.0.20240930102036.1-RELEASE" is invalid
Error: validation: chart.metadata.version "1.0.20240930110209.1" is invalid
I've seen 3 or 4 other issues that were closed (dismissed) without real explanation. I'm not against semver, but I'm against improper validation. I have tested all those string against an online checker (not really scientific, but hey) and they all tell me those are A-OK.
What's wrong with my version or what's wrong with your validation?

The version property is expected to be valid semantic versioning.
Here is a breakdown of reasons they are invalid...

1.0.20240930-093258.1-RELEASE: The -093258.1-RELEASE is considered a pre-release with the initial - being a separator from the version. Pre-releases are separated by . into different identifiers where you have 093258 and 1-RELEASE. The spec states that "Numeric identifiers MUST NOT include leading zeroes". This is the error as 093258 starts with a 0.
1.0.20240930102036.1-RELEASE: This has 4 parts separates by .. SemVer only allows for 3. The -RELEASE is considered pre-release and is ok.
1.0.20240930110209.1: This has 4 parts separates by .. SemVer only allows for 3

I would be curious to see which online checker you used as I was able to spot the error each time. Granted, I know semver far better than I wish I did.


Appending many items to an array

It would be lovely if I could append multiple items in a single operation. It can become a bit unwieldily writing it many times.
- type: replace
  path: /releases/-
  value:
    name: extra-release-0
    version: 0
    url: file://extra-release-0

- type: replace
  path: /releases/-
  value:
    name: extra-release-1
    version: 1
    url: file://extra-release-1

- type: replace
  path: /releases/-
  value:
    name: extra-release-2
    version: 2
    url: file://extra-release-2

--->
?

Wish I had a good suggestion for what could be done here 😋

A proposal:
- type: append
  path: /releases/
  values:
    -  name: extra-release-0
       version: 0
       url: file://extra-release-0
    -  name: extra-release-1
       version: 1
       url: file://extra-release-1
    -  name: extra-release-2
       version: 2
       url: file://extra-release-2


Optionally implement terraform-provider-tlsconvert as a provider-defined function for Terraform 1.8+

Thank you for supporting the Terraform community with this data provider! If you were using the data provider construct to work around the lack of support in Terraform for external functions, please consider the following new feature of Terraform.
Terraform version 1.8 launches with support of provider-defined functions. It is now possible to implement this functionality as a function, rather than wrap the functionality in a data provider. Provider-based functions have the advantage of a simpler in-line syntax that does not require the data block (or any other resource blocks) to use.
The caveat is that, as provider-defined functions are new to Terraform 1.8, you would need to continue to maintain the current data provider functionality if you wished to continue to support earlier versions of Terraform.
Please see the provider-defined functions documentation to learn how to implement functions in your providers. If you have any questions, please visit the Terraform topic in our official forum.
We greatly appreciate your support of the Terraform community with your contributions. If you do not wish to implement this functionality as a function, please feel free to close this issue. This issue is simply to raise awareness of the new capability. Thanks again!

Thanks! Since the upstream tls provider added pkcs8 functionality, we're mostly not using this anymore. However, we also can't delete it because terraform doesn't support removing providers, so we're stuck maintaining this at the status quo.


Check minimum rust-version for recently stabilized features.

This adds some checks for the rust-version field in Cargo.toml to check that it isn't too low for any recently stabilized features in the manifest.  The intent here is to ensure that the rust-version is truly compatible with the package.
It checks:

Edition
named profiles (minimum 1.57)
profile strip (1.59)
weak and namespaced features (1.60)

r? @alexcrichton
(rust-highfive has picked a reviewer for you, use r? to override)

cc @djc FYI

Personally I don't feel that we should be doing something like this in Cargo. While it may weed out a mistake here or there I would naively expect that the vast majority of "mistakes" are things related to the source code rather than the configuration itself. If that's the case this seems like a chunk of code that will be pretty annoying/arduous to maintain for not a whole lot of benefit over time.
Is this perhaps fitting into some sort of larger overall story though?

That's fair.  No, there isn't a larger story here, I was just thinking it would be a simple check for mistakes.  But you're right, if someone wants to actually validate rust-version, they have to actually build and test with that version, in which case these errors will be immediately exposed.


1 suggestion

can you provide a sample workflow,please

I have done ,thanks for you node,it's very helpful

Is this not just… IPAdapter with inpainting? 😅

I aggred with you.  hahaha.  😅
as explain in #2 , the paper enchance IPA material transfer with depth & illumination information, which give out a better output.

update the READM with a sample workflow node detail

As commit 9625be3, add sample workflow.


Error:   Dimensions exceed 50 inches (height and width are specified in 'in' not pixels).

Hi Gufeng, FB Team
I'm running a model with a lot of paid variables (more than 20) and I'm getting this error:
Error:   Dimensions exceed 50 inches (height and width are specified in 'in' not pixels).
If you're sure you want a plot that big, use limitsize = FALSE.
From the message, I understand that Robyn is not able to plot the different model onepagers because of the number of variables but since it shows me that error, Robyn does not generate the csv outputs either.
Is there any workaround to avoid the plotting error and get the csv output?
I tried running the model in RStudio 1.3.1073 (R 3.6.1/Robyn 3.4.7 Windows  and R 4.1.2/Robyn 3.4.8 Linux). The demo works perfectly and generated all the plots and csvs so far.
Thank you for all the work,
Lionel

hey we're seeing this for the first time. you can set plot_pareto = FALSE in the robyn_run function to disable the onepagers. That should solve your problem for now

Hi Gufeng,
Thanks for your answer. I had set this option to False but it shows me the same error.
This is the full response I got

rlang::last_error()
<error/rlang_error>
Dimensions exceed 50 inches (height and width are specified in 'in' not pixels).
If you're sure you want a plot that big, use limitsize = FALSE.
Backtrace:

Robyn::robyn_run(...)
ggplot2::ggsave(...)
ggplot2:::plot_dim(...)
Run rlang::last_trace() to see the full context.

rlang::last_trace()
<error/rlang_error>
Dimensions exceed 50 inches (height and width are specified in 'in' not pixels).
If you're sure you want a plot that big, use limitsize = FALSE.
Backtrace:
x

-Robyn::robyn_run(...)
+-base::suppressMessages(...)
| -base::withCallingHandlers(expr, message = function(c) invokeRestart("muffleMessage"))
-ggplot2::ggsave(...)

\-ggplot2:::plot_dim(...)

Thanks again for your support.

Ok the argument is in ggsave. I'm on holiday from today on. I recommend you to clone the repo first, then open the model.R file under subdir /R/R, search ggsave and add the argument limitsize = TRUE to all ggsave, save the script, restart R session and then run devtools::load_all().
This way, you have customised the package. I'll update it when I'm back from PTO

this should work now

this should work now

Hi, I just encountered this error using Robyn version Robyn_3.4.12

FYI I've pushed another commit to deal with this. https://github.com/facebookexperimental/Robyn/commit/eb0dc8efcf9bac699a42742bb269a43e7c123570


Support status message & spinner

:Release Notes:
Support spinner and target information
:Detailed Notes:

Some of the CLI commands do not show up the process,
which makes the user feel as though it has stopped running.
To resolve it Add a processing spinner.
Show the information of the connected target when executing the command
ares-shell, ares-log do not show target information
Updated TC

:Testing Performed:

TC passed on AUTO & OSE target and Auto emulator.
eslint passed
Verified with CLI commands

a. Print target info & Processing spinner
$ ./ares-push.js demo.mp4 /tmp -i
$ ./ares-push.js demo.mp4 /tmp
$ ./ares-pull.js /tmp/demo.mp4 store -i
$ ./ares-pull.js /tmp/demo.mp4 store
$ ./ares-install.js ../spec/tempFiles/com.jasmine.web.app_0.0.1_all.ipk
$ ./ares-inspect.js -s com.jasmine.web.app.service
$ ./ares-device.js -c
Set target device : emulator

... Processing
[command result]

b. Show only target info
$ ./ares-install.js -l
$ ./ares-launch.js com.domain.app
$ ./ares-launch.js -r
$ ./ares-install.js -F
Set target device : emulator

c. Do not show target info for ares-log&ares-shell
$ ./ares-shell.js
$ ./ares-log.js -n 2

:Issues Addressed:
[PLAT-139817] Implement CLI status message

@ssuminahn, please check feasibility of progress spinner.

Code 👍
Verified 👍

Code :+1:
Verified :+1

Please update commit log

remove ares-device example
update result format(remove new line and add [INFO])
add ares-inspect -a in b. Show only target info
add ares-device in b. Show only target info

Code :+1:
Verified :+1:

Please update commit log
* remove ares-device example

* update result format(remove new line and add [INFO])

* add ares-inspect -a in b. Show only target info

* add ares-device in b. Show only target info

Done :)

Code :+1:
Verified :+1:

One of commit log is not correct.
$ ./ares-inspect -a
to
$ ./ares-inspect.js com.jasmine.web.app OR $ ./ares-inspect.js -a com.jasmine.web.app
Please update this.

One of commit log is not correct.
$ ./ares-inspect -a
to
$ ./ares-inspect.js com.jasmine.web.app OR $ ./ares-inspect.js -a com.jasmine.web.app
Please update this.

Fixed.

code :+1:
verify :+1:

I will merge this commit after developer branch is ready to release CLI 2.2.0.


jobs running at 99% cpu

*Description of issue:
When ever i run jobs it lags my server out its 10gb server but makes the cpu skyrocket

Server Type (Spigot/Paperspigot/etc):
paper 1.14.4
Server Version (using /ver):
paper 186
Relevant plugins (Delete if this isn't needed):

Paste server timings report and plugins list.

@irobertrs What cpu model are you running out of curiosity?

I dont have timings as i was asking for help for a few days on discord but never got any help so i just deleted jobs and cpu is Xeon E5-1650v3 @ 3.8Ghz
basically what happens is i load up my server with jobs and it just goes laggy. even if i delete every plugin but vault and jobs

Run /timings paste and done.
@LogGits CPU information is only needed if we have run out of ideas and there is no way to fix it. So the CPU has no place right now, because it only needs to run our server on a very weak server machine.
Also, for help on discord mention me to get help about your problem.

i dont have it installed on my server i will put it on a spare server running the same specs later and do a timings report.
also who are u on discord?

Without server timings this issue can't reproduce. Or just use a memory leak checker and send a screenshot about it.
Same as here.


Prefixed filter queries are easier to parse

So I'm implementing the filter mechanic and I realized the annoyance I would have to go through in order to make it work.
In simple use cases the filtering mechanic is arguably simple to parse:
GET /comments?post=1

Comment.where(post: params["post"])

However scaling this to both multiple endpoints and with multiple includes becomes...cumbersome:
GET /profiles?account=1&age=23&visible=true&include=posts,comments&fields=id

models = Profile.where(account: params["account"], age: params["age"], visible: params["visible"]).includes(params["includes"].split(","))
models.map(&:to_hash).map { |hash| hash.slice(params["fields"].split(",")) }

The natural inclination is to mimic the other areas as demonstrated above, but it's not practical to parse. I propose with this pull request that we mimic the already established way of doing complex filters:
GET /profiles?filter[account]=1&filter[age]=23&filter[visible]=true&include=posts,comments&fields=id

models = Profile.where(params["filter"]).includes(params["includes"].split(","))
models.map(&:to_hash).map { |hash| hash.slice(params["fields"].split(",")) }

You've got your reserved filter param in #341. Thanks for the suggestion @krainboltgreene!


Increment version for communication releases

Increment package version after release of Azure.Communication.Rooms

/check-enforcer override

Failure is unrelated to changes.  Merging.


the elastic search inner hits problem

6.8.3 seem have some problem with inner_hits query.
It always return the wrong inner_hits.
But I try 6.2.3 get the correct result.
Here is the schema
body: {
properties: {
mac: { type: "keyword" },
data: {
type: "nested",
include_in_parent: true,
properties: {
name: { type: "keyword" },
value: { type: "keyword", "ignore_above": 10000 },
nameid: { type: "keyword", "index": false }
}
}
}
}
insert data
body: {
data: [
{ name: "CPU", value: "intel V1" },
{ name: "MEM", value: "samsung" },
{name:"HDD", value:'WD'}
],
mac: "301422"
}
Here is the query.
body: {
_source: false,
query: {
nested: {
path: "data",
query: {
term: {
"data.value": "WD",
},
},
inner_hits: {
highlight: {
fields: {
"daata.value": {},
},
},
},
},
},
},
6.8.3 will alwasy get the
{ name: "CPU", value: "intel V1" },
but 6.2.3 wiil get the
{name:"HDD", value:'WD'}

Similar issue has been fixed in release <IP_ADDRESS>, please check it fixes your issue.
Thanks.

The problem already solve in <IP_ADDRESS>
Thanks,


Merge refs/heads/temp-branch-6404024505 into alpha

Merge refs/heads/temp-branch-6404024505 into alpha

This PR has been merged into alpha. Thanks for your contribution!

This PR has been merged into alpha. Thanks for your contribution!


Smarthings: Hub is Not a Valid Device

The problem

All smartthings entities became unavailable. No changes to HA or configuration made, was working normally this morning and now everything unavailable.
Environment

Home Assistant release with the issue: 99.3
Last working Home Assistant release (if known): 99.3
Operating environment (Hass.io/Docker/Windows/etc.): Hassio
Integration causing this issue: smartthings
Link to integration documentation on our website:

Problem-relevant configuration.yaml

Traceback/Error logs

ValueError: 'HUB' is not a valid DeviceType

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 190, in async_setup
    hass, self
  File "/usr/src/homeassistant/homeassistant/components/smartthings/__init__.py", line 116, in async_setup_entry
    devices = await api.devices(location_ids=[installed_app.location_id])
  File "/usr/local/lib/python3.7/site-packages/pysmartthings/smartthings.py", line 77, in devices
    return [DeviceEntity(self._service, entity) for entity in resp]
  File "/usr/local/lib/python3.7/site-packages/pysmartthings/smartthings.py", line 77, in <listcomp>
    return [DeviceEntity(self._service, entity) for entity in resp]
  File "/usr/local/lib/python3.7/site-packages/pysmartthings/device.py", line 651, in __init__
    self.apply_data(data)
  File "/usr/local/lib/python3.7/site-packages/pysmartthings/device.py", line 94, in apply_data
    self._type = DeviceType(data['type'])
  File "/usr/local/lib/python3.7/enum.py", line 310, in __call__
    return cls.__new__(cls, value)
  File "/usr/local/lib/python3.7/enum.py", line 564, in __new__
    raise exc
  File "/usr/local/lib/python3.7/enum.py", line 548, in __new__
    result = cls._missing_(value)
  File "/usr/local/lib/python3.7/enum.py", line 577, in _missing_
    raise ValueError("%r is not a valid %s" % (value, cls.__name__))
ValueError: 'HUB' is not a valid DeviceType

Additional information
Attempted resolution: Removed integration, reinstalled integration and smartapp, generated new token

Nevermind, fixed it by manually disabling Nabu Cloudhook. Thanks for the assistance Andrew! Love this integration.

How did you disable that? I have the same error, seemingly out of nowhere with the latest version of HA

@vnbx
Go to Configuration > Cloud and scroll down, you'll see all the available webhooks. Disable smartthings and then add the integration again.


Add Redis service account name to CRD

Included Service Account to Redis CR

Signed-off-by: Oladipupo Ajayi<EMAIL_ADDRESS>

LGTM, but tests are broken, I don't know if it's linked to your PR or not

Since the limit of secret in kube is 1MB  and helm manages its revisions via secret, adding these new fields in CRD broke the harbor-operator installation of pipeline. https://kubernetes.io/docs/concepts/configuration/secret/#restriction-data-size
We should install CRDs first with kubectl and helm upgrade/install harbor-operator with flag installCRDs=true to avoid having long secret of helm release https://helm.sh/docs/chart_best_practices/custom_resource_definitions/

@DeeAjayi Can you rebase this PR on the latest master? It should resolve all the issues we had with testing.

 Can you check if you can fix the signing?

Yes looking into it

@MarcelMue the failed DCO step has been fixed

Thanks for the help @DeeAjayi !

@DeeAjayi - congrats on merging your first PR here mate :)


Integration tests for PostgresGeneration

Write a suite of integration tests for the PostgresGenerator family, also including the code to generate and populate prepared statements in scala.

Please merge develop into this


Release first production version to Google Play Store

@posterzh

Disable device transfer
Enable add hotspot
Enable assert location
Create APK and share with @Louisreed
Update register hotspot button so that assert location flow is correct

@marvinmarnold

Create a signing certificate
Add cert to 1Password
Build, sign, upload to Play Store
Update store copy and images
Publish

This has been published and is waiting approval.

Released an initial version: https://play.google.com/store/apps/details?id=com.nebra.helium.maker
Will close this at the end of the sprint when a more stable version is out.

@marvinmarnold Thank you.

v1.0.1 released


delta functions are not generating next and delta links properties

Assemblies affected
1.1.0, 1.0.11, 1.0.10
Steps to reproduce
Convert the Microsoft Graph description, and look at delta functions /applications/microsoft.graph.delta()
Expected result
  /applications/microsoft.graph.delta():
    get:
      responses:
        2XX:
          description: Success
          content:
            application/json:
              schema:
                title: Collection of application
                type: object
                properties:
<EMAIL_ADDRESS>                      type: string
                      nullable: true
<EMAIL_ADDRESS>                      type: string
                      nullable: true
                  value:
                    type: array
                    items:
                      anyOf:
                        - $ref: '#/components/schemas/microsoft.graph.application'
      x-ms-docs-operation-type: function
      x-ms-pageable:
        nextLinkName<EMAIL_ADDRESS>        operationName: listMore

Actual result
  /applications/microsoft.graph.delta():
    get:
      responses:
        2XX:
          description: Success
          content:
            application/json:
              schema:
                title: Collection of application
                type: object
                properties:
                  value:
                    type: array
                    items:
                      anyOf:
                        - $ref: '#/components/schemas/microsoft.graph.application'
                        - type: object
                          nullable: true
      x-ms-docs-operation-type: function
      x-ms-pageable:
        nextLinkName<EMAIL_ADDRESS>        operationName: listMore

Additional detail
In fact I'd even expect the delta response to inherit from the countable response and be a reusable model instead of being defined inline multiple times. like we've done with #270 for entity sets and navigation properties.

Additional context at https://github.com/microsoft/OpenAPI.NET.OData/issues/231

@baywet If the linked content is closed within the next 48 hours, I want to verify that it would not be until next week that it would shipped into the library.

next week or maybe the one after as we have to merge this PR, release this library, then update and release hidi (our conversion tool)


Update versionsFrom to 1.8

@marcuscarr We are not currently using this package. Shall we just close this PR?

@rbeitra - gladly