restore interrupted status #8750

[x] If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #.
[ ] Update the CHANGES log.

What is the scenario of doing this?

the main purpose is let higher layer code know the thread state and can response for interrupted

Which thread do you mean?

the  throwing interruptedexception  thread

I don't think there is really one thread is going to interrupt. This is just a protection mechanism from coding API requirements, nothing more.

I think if the other thread interrupt the current thread ,we should return interrupted status to caller ,but not do nothing

My point is, there should be no such case. So, I can't be sure, interrupting current thread could be helpful.

I think if the other thread interrupt the current thread ,we should return interrupted status to caller ,but not do nothing

I agree with "we should return interrupted status to caller", but don't agree with "but not do nothing", interrupts can be also used as a signal between threads, especially in this case, we just use the interrupt as a signal that "we should not keep waiting for the command queue anymore (for example the process is about to terminate)".
"return interrupted status to the caller" is a better practice if you don't know who is the caller and how will they handle the interrupt status (for example in the framework / SDK).
In this particular PR, because the BaseCommand command = commands.take(); is inside a while loop, you cannot simply set the interrupt signal, which will result in an endless loop when it comes to commands.take() and it throws, you need to add a break inside catch (InterruptedException e) {

you are right,I am omiting the loop

I am still not following why we need to set the flag.

Thread.interrupt() sets the interrupted status/flag of the target thread to true which when checked using Thread.interrupted() can help in stopping the endless thread.

This is what I understand, please correct me if I am wrong. The reason we catch this exception is, we don't want anything to close this thread, except JVM is existing(then it exists from #shutdown)

I took another look of this method block, it is enough OK to remove this catch. As InterruptedException is an exception, not a RuntimeException, so, it means there is no case to intercept.

Could either of you explain what is really going on? Basically, I am still not following.

If there does not have other thread  possibly interrupt current thread  ,I think removing catch block is ok

If there does not have other thread possibly interrupt current thread

No, there isn't, which was why I keep asking.


Update README.md

Updates theme variations to match the new naming conventions.

Good catch Vieko! Thank you for that.


Add Jenkins CI tests badge to README.md

This PR aims to add a Jenkins CI status badge to the README file. Having this badge would be useful to inform users about the current status of the develop branch.
Preview:

Nice work @fievelk :)


Bump safe-eth-py to 6.0.0b5

@JagoFigueroa this is already in staging, we need QA on estimating a transaction for a 1.2.0 Safe

Tested and verified! (apologies for the delay, did not have permissions to post comments but now this is fixed 😄)


Add typescript/standard checker

Since ESLint supports TypeScript by customized parser.
Standard is also possible to lint TypeScript files.

This is no longer needed.  With recent versions of syntastic you can just add javascript/standard to g:syntastic_typescript_checkers, run :SyntasticCheck javascript/standard etc.

OK, that works.


riscv: Add support for hardware stacking / unstacking

Some RISC-V SoCs implement a mechanism for hardware supported stacking / unstacking of registers during ISR / exceptions. What happens is that on ISR / exception entry part of the context is automatically saved by the hardware on the stack without software intervention, and the same part of the context is restored by the hardware usually on mret.
This is currently not yet supported by Zephyr, where the full context must be saved by software in the full fledged ESF. This patcheset is trying to address exactly this case.
At least three things are needed to support in a general fashion this problem: (1) a way to store in software only the part of the ESF not already stacked by hardware, (2) a way to restore in software only the part of the context that is not going to be restored by hardware and (3) a way to define a custom ESF.
Point (3) is important because the full ESF frame is now composed by a custom part depending on the hardware (that can choose which register to stack / unstack and the order they are saved onto the stack) and a part defined in software for the remaining part of the context.
In this patch a new CONFIG_RISCV_SOC_ISR_STACKING is introduced that enables the code path supporting the three points by the mean of three macros that must be implemented by the user in a soc_stacking.h file: SOC_ISR_SW_STACKING, SOC_ISR_SW_UNSTACKING and SOC_ISR_STACKING_ESF (refer to the symbol help for more details).

Maybe this should be made depends on !USERSPACE?
And maybe promptless as well so those SOCs that support this would
select the Kconfig symbol directly as most people might
not know much what to do about this Kconfig choice anyway.

This appears to be incompatible with user space support. Maybe this should be made depends on !USERSPACE? And maybe promptless as well so those SOCs that support this would select the Kconfig symbol directly as most people might not know much what to do about this Kconfig choice anyway.

yup, makes sense.

@fkokosinski @kgugala ping


Add default name/namespace handling to CronWorkflow create/suspend/re…

Refactored the way the CronWorkflow name and namespace attributes are handled by the create/suspend/resume methods so that the name and namespace can be specified at object creation and the methods can be invoked with no arguments.
It is still possible to call the methods with arguments as before and the same functionality will continue to work.

@flaviuvadan I wasn't sure if you wanted it in the same PR or in a separate one. I can certainly add it to this PR if that's OK.

Same PR is definitely fine in this case 🙂


haskellPackages.sdl2: test-suite needs x server, so deactivate it

Motivation for this change
haskellPackages.sdl2 has a test-suite sdl-space, which needs an x server and can't be run
in the build environment. so lets deactivate it.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

fixes #46130

fix #46130


.github/ISSUE_TEMPLATE.md - get more information

The goal is to get all the necessary information from the reporter upfront.
Too many times the issues submits and we need to do a round of asking before
we can get close to a solution.
In the future we could even add a nix-bug or nix-report that fetches all that information.

lsb_release -a

fixed

For NixOS it's enough to run nixos-version

Maybe better than nix-channel --list (which doesn't show the actual versions in the channel):
$ nix-instantiate --eval '<nixpkgs>' -A lib.nixpkgsVersion
"15.09.1076.9220f03"

I.e. this shows the Nixpkgs version without having to care about the channel configuration etc.

Okay, fixed it all. I'm quite happy of the result for a first round.
I bet we're going to have issues with users running the nix-instantiate as a user instead of root or reversely. Ultimately I would like to add a nix-something command that collects all that info but I'm afraid of C++ and don't want to add more perl to the nix package. But one thing at a time.

Let's start with this, it's way better than current default.

Thanks!


Ingame Computer linkage

Allow an ingame Computer to run Webify, by talking to a server that sits inbetween the CC Computer and web api

A way to implement this could be through websockets, allowing the webify api to have an argument to switch to a forward mode, like this:
webify forward (port), this might also be implemented as a seperate Lua file for cleanliness, but I think for ease of use it should be implemented into the webify api itself


Implemented FT 120

ok to test

please merge

Tracked with branch NMS.FT.KILKARICONTROLLERIT.
So closing this request.


Support AMD GPUs via WSL

Hello,
I'm running a Windows 11 workstation based on an AMD RX 7900XTX GPU. I installed the latest Ollama for Windows and with that I can see the GPU getting used for any queries. I also tried the Linux install for WSL following this guide. With WSL however, even after installing ROCm as mentioned in the guide, I can see Ollama not making use of the GPU. I tried following this issue to build Olama locally with the fix mentioned, but no success there either. The ollama server keeps crashing when I attempt to run any model like llama2 or llama3.2.
Please can someone help with this. I really don't want to switch to a Nvidia just for this purpose.
Thanks,
Vignessh

We're tracking this with #5275


Use io.MultiWriter to write command output to stdout

Resolves https://github.com/dagger/dagger/issues/5196
Writes the tui Stdout to os.Stdout as well as the cmdVtx.Stdout().
Before this change, a simple workflow like this:
package main

import (
	"context"
	"fmt"
	"os"

	"dagger.io/dagger"
)

func main() {
	client, err := dagger.Connect(context.Background())
	if err != nil {
		panic(err)
	}

	v, err := client.Container().From("alpine").WithExec([]string{"echo", "hello"}).Stdout(context.Background())
	if err != nil {
		panic(err)
	}

	fmt.Fprint(os.Stdout, v)
}

Would not write the program's output to stdout.
$ dagger run go run . > out.txt
...
$ cat out.txt

With these changes:
$ dagger run go run . > out.txt
...
$ cat out.txt
hello

notes
both with and without these changes, redirecting stdout when _EXPERIMENTAL_DAGGER_INTERACTIVE_TUI=true is set causes BubbleTea to crash. I don't really know how TUIs work but I'm guessing stdout redirecting will probably never work with the interactive TUI.
goroutine 50 [running]:
runtime/debug.Stack()
	/usr/lib/go/src/runtime/debug/stack.go:24 +0x65
runtime/debug.PrintStack()
	/usr/lib/go/src/runtime/debug/stack.go:16 +0x19
github.com/charmbracelet/bubbletea.(*Program).Run.func1()
	/home/kminehart/.go/pkg/mod/github.com/charmbracelet/bubbletea@v0.23.2/tea.go:402 +0x95
panic({0x13f5fe0, 0xc0007100d8})
	/usr/lib/go/src/runtime/panic.go:890 +0x263
github.com/dagger/dagger/internal/tui.trunc(...)
	/home/kminehart/Work/Grafana/dagger/internal/tui/util.go:28
github.com/dagger/dagger/internal/tui.Details.headerView({{0x16a2120, 0xc000041950}, 0x0, 0xa, 0x0})
	/home/kminehart/Work/Grafana/dagger/internal/tui/details.go:67 +0x912
github.com/dagger/dagger/internal/tui.Details.View({{0x16a2120, 0xc000041950}, 0x0, 0xa, 0x0})
	/home/kminehart/Work/Grafana/dagger/internal/tui/details.go:92 +0x6b
github.com/dagger/dagger/internal/tui.Model.View({0xc0002c20c0, {0x1685900, 0xc0001e1c20}, 0xc0001e1ce0, 0xc0001e1d10, 0xc0001e1d40, 0xc00023a500, {{0x16a2120, 0xc000041950}, 0x0, ...}, ...})
	/home/kminehart/Work/Grafana/dagger/internal/tui/model.go:392 +0x2eb
github.com/charmbracelet/bubbletea.(*Program).eventLoop(0xc000391ef0, {0x168eb30?, 0xc00021e000?}, 0x0?)
	/home/kminehart/.go/pkg/mod/github.com/charmbracelet/bubbletea@v0.23.2/tea.go:345 +0x647
github.com/charmbracelet/bubbletea.(*Program).Run(0xc000391ef0)
	/home/kminehart/.go/pkg/mod/github.com/charmbracelet/bubbletea@v0.23.2/tea.go:465 +0x7fd
main.interactiveTUI.func1()
	/home/kminehart/Work/Grafana/dagger/cmd/dagger/engine.go:92 +0x26
created by main.interactiveTUI
	/home/kminehart/Work/Grafana/dagger/cmd/dagger/engine.go:91 +0x24a

I tested this out and it works as advertised  :)
cd /tmp
git  clone https://github.com/dagger/examples
cd examples/go/db-service
dagger run go run main.go > out.txt  #using dagger compiled from this PR
cat out.txt

I noticed some color differences. With this PR

vs current dagger run TUI:

@d3rp3tt3 @shykes @vito would love to get your take on this

Thanks for the PR!
Makes sense to address this, but I think this might break the TUI when you don't redirect stdout since multiple things will be writing to it.
If so, could make sense to do this if and only if it detects stdout is redirected (i.e. not a terminal).

Thanks for reporting the issue @kminehart & the quick fix. It would be great to include this in the follow-up patch release of v0.6.0. WDYT @vito? This could go out as early as this week if it looks good to you.

Went ahead and submitted an alternative PR with my suggested change (+ supporting stderr redirect too because why not): https://github.com/dagger/dagger/pull/5231

awesome! thanks for doing that


Stability Improvements (Apple Pay Widget & API Wrapper)

Hi @ahoshaiyan 👋
The summary of this PR:

Improve our plugin's stability by handling potential errors in the Apple Pay widget and the API wrapper.
Update the Apple Pay testing section in the README to highlight that simulators will not work.
Fix all broken docs links.
Catch-up with the latest updates in our dependencies and Flutter tooling.

Please let me know what do you think. I'll publish a new version once this PR is merged.

Amazing work @Fghurayri 🚀. Let's publish the new release

@ahoshaiyan Done. 🚀
https://pub.dev/packages/moyasar/versions/2.0.5


Create README.md

Brief intro for the Repo to let people know what is it about.

Thank you for the contribution!


Adjust Greek localization & one English field

Also test my gh CLI here

Have finally gotten a bead on why old commits are appearing. Acceptance of PRs here does not clear commits made from a fork it seems. This mirrors the issue perfectly, and I will implement solution accordingly: https://opensource.stackexchange.com/questions/6740/once-i-did-a-pr-on-a-repo-should-i-delete-my-fork

Update: I seem finally to have fixed this annoying out-of-sync git problem.
Isolated the problem to the fact that my commits at PR-create time were being pushed to my fork, but then those never synced with the "origin" beefy repo, and so they were prefixed to any ensuing PR create (gh CLI, as noted earlier), layer by layer, that I initiated from my local repo.
Part of issue may have been that my "upstream" had been set at clone-time (also gh CLI) to the yfii/dfi repo (seen via git remote -vv. So first I reset that to match the beefyfinance origin via git remote rm upstream and git remote add upstream https://github.com/beefyfinance/beefy-app.git
But still after fetching and pull rebasing per Beefy's CONTRIBUTING.md, the out-of-sync problem with the fork persisted, showing numerous commits ahead.
So after further research, I tried this:
git checkout master git fetch upstream git reset --hard upstream/master git push --force
to hard reset both local and fork repos,. And it looks to have worked. Both local and fork repos show as matching the state of beefyfinance/beefy-app.
Yay.


Cknieling/cgac warnings

Interesting.. I used a maya icon, that is used in the default maya guy.. Using caution.png now.. I hope this works on linux..

Updated icon:

Making sure to log

generateError "Non-recognized builtin method" as Error in status line and mel console
assetError "Potentially unsupported CGAC version A.B : newer than current (X.Y)" as warning in status line and mel console

Replacing cgacVersion with respective CityEngine version
Renamed cgacErrors to cgacProblems to avoid ambiguity between problems of error type and generic problems of any type (i.e. warnings). This also references the problem window in CE, which is similar in functionality.
Showing error icon if problems contain errors.


Actually preserve the uniqueness of canonical generic environments.

@swift-ci please smoke test and merge

@swift-ci please smoke test Linux

Yikes, looks like this broke something. Reverting.


Add new functions to syncers

Makes life easy who use multiple phones in a week.

Close it!

Google's python wrapper is a much better option for syncing.
Hence, closing. Information at https://github.com/google/adb-sync


Add initial version.

Great! Why have a non-fixing version? We don't have it for the other hooks IIRC.

Great! Why have a non-fixing version? We don't have it for the other hooks IIRC.

Apparently, the repo where this hook would be used requires a non-fixing version: https://github.com/Quantco/barmer_drg_scoring_analytics/pull/1711/files

@JanJaguschQC thanks for taking the initiative to create this repository! We've been using a non-fixing version since most issues require manual intervention anyway. I think we get the same behavior when using the fixing hook, i.e. I guess you can just remove the linting hook .

@JanJaguschQC thanks for taking the initiative to create this repository! 🚀
We've been using a non-fixing version since most issues require manual intervention anyway. I think we get the same behavior when using the fixing hook, i.e. I guess you can just remove the linting hook .

Thanks @borchero! I've released a 1.2.1 tag which you should be able to use in your pre-commit config.

@JanJaguschQC awesome, thanks!


iOS Nativescript: Cannot Access File.

I am trying to use this in a nativescript application. The file is accessible to the application and can be read using file-system, the module provides an error that the file is not accessible. Am I doing something wrong?
Code

Error

readFile is shaped specifically for NodeJS and does not work with nativescript's incompatible interface.  Follow the example in https://github.com/SheetJS/js-xlsx/tree/master/demos/angular2#nativescript -- you must read the data then call XLSX.read:
/* read a workbook */
const bstr: string = await file.readText(textModule.encoding.ISO_8859_1);
const wb = XLSX.read(bstr, { type: "binary" });

Complete example app component code in https://github.com/SheetJS/js-xlsx/blob/master/demos/angular2/nscript.ts


[Intel MKL] Enabe SoftmaxGrad(SumReducer)

This is a preview of BF16 feature, the complete functionality will be supported after MKLDNN v1.4 released:

Enable BF16 SoftmaxGrad with Eigen implementation. Main modification is to implement SumReducer with accumulate type. It helps to avoid accuracy loss for BF16 reduction. The new UT can show the difference W/O accumulate type.

Note:
Forward Softmax may get accuracy issue because it has Sum . MklSoftmax will fix it with internal accumulate type, too. MKL version of BF16 softmax will be another PR.
Signed-off-by: Lu Teng<EMAIL_ADDRESS>

I separate BF16 Softmax from this PR because it has dependency with MKLDNN. We'll have another PR to submit forward part, thanks!

@penpornk @Zantares We will update this PR soon and would like to put this on hold for a short time.
Thanks.

@Zantares, @mdfaijul Any update on this PR? Please. Thanks!

@Zantares, @mdfaijul Any update on this PR? Please. Thanks!

We are trying to add new util function to have a better control of BF16 unit test. It will be updated soon in 1~2 days, thanks.

Hi @gbaned @penpornk , we have fully updated this PR, now it's ready to be reviewed, thanks.
Really sorry for the delay because we need to take care of accuracy for BF16 operations.

@penpornk @Zantares  I am also from Intel. Wondering why this PR is reverted after a merge?
https://github.com/tensorflow/tensorflow/commit/08b5c94d57ed1aed1120ffc0ec0a2450be61a144
Was the revert an error? or Can you hint, how we could fix and resubmit this PR as gives good performance for some of the models.

@nammbash @Zantares It was automatically rolled back because it broke our internal-only tests. I have been meaning to look at it but haven't had time yet. Will update soon. Sorry for the delay!

@nammbash @Zantares It was automatically rolled back because it broke our internal-only tests. I have been meaning to look at it but haven't had time yet. Will update soon. Sorry for the delay!

What's kind of this error? Is it a crash or an accuracy test failure? Because I used accumulate type, so the accuracy will be improved for BF16 SumReducer and it may show different result if the internal case uses an old accuracy for comparison. Please tell us if any help we can provide, thanks!

What's kind of this error? Is it a crash or an accuracy test failure? Because I used accumulate type, so the accuracy will be improved for BF16 SumReducer and it may show different result if the internal case uses an old accuracy for comparison. Please tell us if any help we can provide, thanks!

It's an end-to-end model test. The end results differ significantly. I might not have time to dig into it before the 2.3 branch cut, so I'm thinking we can just wrap the new reducer with INTEL_MKL && ENABLE_INTEL_MKL_BFLOAT16 for now. I'm confirming with my teammate if they are okay with this. If so, I'll bring back the changes.

@penpornk Not sure I understand. If there is a problem, then wrapping it in MKL will also have the problem and test failures correct?
FYI @agramesh1 @Zantares

@nammbash

If there is a problem, then wrapping it in MKL will also have the problem and test failures or shortcomings as opposed to fixing it. Correct?

Correct. Wrapping the reducer in INTEL_MKL only helps shielding the potential bug from vanilla TensorFlow, which will help this PR pass the currently failing test and be able to stay in the repo. It won't fix the potential bug in the MKL build.
'potential' bug: There is a chance that the program works correctly but got vastly different results because of a severe error propagation in the original test result which uses just bf16.
I asked @rmlarsen to help double check and he didn't see anything obviously wrong with the reducer either. We will bring back the PR with the INTEL_MKL guard around the reducer and will try to confirm if this is a bug or just the test's fault.

@penpornk @nammbash my opinion:
We added BF16 MklSoftmax, SoftmaxGrad and Eigen SumReducer with accumulate type. Gradients will be different if the test is using BF16 Softmax without INTEL_MKL because accumulate type is only for MklSoftmax rather than Eigen Softmax.
Otherwise it should be someting wrong if the failure is only appearing in SumReducer, . Please keep us posted if find anything wrong, thanks!

@Zantares @nammbash Sorry for the late update! It was the test's fault and I fixed it now. I'm just waiting on a wider coverage test results to see if there's anything else failing. If things go well, I should be able to bring this PR back tomorrow.


How to send Datasource Credentials to reportviewer ?

Let me if there is a way to pass DatasourceCredentials to report

This feature is not implemented yet. I am going to add it to the project backlog.

I added this feature to the project. Please build the latest code from the repository to start using it immediately. I will be deployed with v. 0.8.4.


”Satu Nou”, ”Orheiu Bistriței”, ”Petriș” are listed in the drop-down menu

Description:
When user writes ”Satu Nou”, ”Orheiu Bistriței”, ”Petriș” the locations appear in the drop-down menu next to the comune and the county witch is a part according to the law.
Precondition:
The website is up an running.

Step 1
Write in the search bar "Satu Nou"

Expected results
The location appears in the drop-down menu as "Satu Nou, Bistrița-Năsăud (Cetate)".

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Orheiu Bistriței"

Expected results
The location appears in the drop-down menu as "Orheiu Bistriței, Bistrița-Năsăud (Cetate)".

Step 4
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 5
Write in the search bar "Petriș"

Expected results
The location appears in the drop-down menu as "Petriș, Bistrița-Năsăud (Cetate)".


Help with performance drop at certain websocket data sizes

This is more of a question that an actual issue report. Please feel free to ignore!
I've slightly modified the awesome advanced_server_flex.cpp to create a C++ Apache thrift websocket server that I'm planning to open-source. I haven't managed to clean up the code and its admittedly still pretty basic. However everything works and I'm quite impressed of boost beast! Two thumbs up!
A first performance benchmark from Google Chrome with Apache thrift nodejs implementation shows a promising data transfer from the websocket server to a Javascript browser client. Except there is a reproducible, very strange drop of performance for data sizes around 10 to 100 KByte. The actual numbers I get are given in below table:
RPC Data Size (Byte) | Calls/sec | Throughput (Byte/sec)
                   1 |   6145.89 |       6145.89
                  10 |   5973.96 |      59739.61
                 100 |   5806.32 |     580632.44
                1000 |   4973.85 |    4973853.86
               10000 |     22.12 |     221187.28
              100000 |     21.90 |    2189918.49
             1000000 |     48.09 |   48089451.66
            10000000 |      4.41 |   44112357.20

As can be seen, there is a "strange" but reproducible drop in calls/sec and throughput for data sizes of 10K and 100K. Even more surprising is the throughput picks up speed later again!
I understand that this issue report is not very telling. And admittedly there are quite a number of components involved in this software stack: boost beast, Apache thrift in C++ and nodejs, and last not least Google Chrome.
But I'm merely hoping for a pointer in which direction to look for the problem, as admittedly I'm quite new to most of these technologies. Is there any known knob in beast that may coincide with my measurements? For example an internal buffer or something? Anything I can do to collect more information?
Version of Beast
#define BOOST_BEAST_VERSION 266

Steps necessary to reproduce the problem
I'm using a mostly unmodified version of the advanced_server_flex.cpp, where in websocket_session::on_read() I reserve a buffer_ size of 11MB (the maximum message size I benchmark), copy the bytes of the thrift message, and commit() the buffer size of the actual message I want to send.
All relevant compiler information
gcc (Ubuntu 8.3.0-6ubuntu1) 8.3.0 for x86_64 with -O2

There is a small buffer used to coalesce reads here:
https://github.com/boostorg/beast/blob/develop/include/boost/beast/websocket/impl/stream_impl.hpp#L84
But if the incoming message is larger than the buffer, it skips the buffer and reads directly into the caller's mutable buffer sequence.
To start, are you sending or receiving?  Do you have compression turned on? Do you have the auto-fragment outgoing frames turned on?

Thanks for the quick response!
The benchmark is exclusively for sending from beast to client. There are RPC-messages from thrift coming into the server, typically less than a few hundred bytes in size. The server responds to the RPC call with a message that is mostly made up of one huge binary blob of the size given in the benchmark table above (currently byte sizes of powers of 10, from 0 to 7).
My server is an almost unmodified advanced_server_flex.cpp with binary transfer mode. I only added the thrift server data exchange on top of websocket_session::on_read(), but my changes in fact are really not doing much more than copying the binary RPC response into the flat_buffer of the websocket and calling async_write().
As far as I understand the advanced_server_flex.cpp does not have compression enabled, and I did not change anything related to auto-fragment outgoing frames. Is that good or bad?

Try turning auto-fragment off:
https://www.boost.org/doc/libs/1_71_0/libs/beast/doc/html/beast/ref/boost__beast__websocket__stream/auto_fragment/overload1.html

Awesome! This was exactly the issue! Now I get consistent throughput for all tested sizes! Thanks a lot @vinniefalco .


chore: Add Ninja generator for wasm & document Ninja requirement for presets

Description
At the end of #162, @codygunton said that the wasm preset was slow in VSCode. That is likely due to not using the Ninja generator that @adr1anh added for the default preset (the wasm preset doesn't inherit from default since it is drastically different).
This sets the wasm preset to use the Ninja generator to match the default generator and it documents Ninja as a dependency for the preset workflow. If a user doesn't use the presets for some reason, they will continue to use whatever generator they specify (or their default).
Checklist:

[x] I have reviewed my diff in github, line by line.
[x] Every change is related to the PR description.
[ ] I have linked this pull request to the issue(s) that it resolves.
[x] There are no unexpected formatting changes, superfluous debug logs, or commented-out code.
[x] There are no circuit changes, OR specifications in /markdown/specs have been updated.
[x] There are no circuit changes, OR a cryptographer has been assigned for review.
[x] I've updated any terraform that needs updating (e.g. environment variables) for deployment.
[x] The branch has been rebased against the head of its merge target.
[x] I'm happy for the PR to be merged at the reviewer's next convenience.
[x] New functions, classes, etc. have been documented according to the doxygen comment format. Classes and structs must have @brief describing the intended functionality.
[x] If existing code has been modified, such documentation has been added or updated.

Looks like Ninja doesn't exist in the wasm docker container. I'll fix.


Information is incorrect for stopping forwarding (doesn't list all the ways forwarding can be set up and stopped).

Information is incorrect for stopping forwarding (doesn't list all the ways forwarding can be set up and stopped). Article should point to the steps here.
https://docs.microsoft.com/en-us/microsoft-365/security/office-365-security/external-email-forwarding?view=o365-worldwide

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

ID: c6924feb-c0eb-6ec2-01cb-0265e181beea
Version Independent ID: 67de4f08-035e-abf4-8c17-61fd10193cc7
Content: Stop auto-forwarding emails
Content Source: microsoft-365/business-video/stop-email-auto-forward.md
Service: o365-administration
GitHub Login: @KwekuA
Microsoft Alias: kwekua

@msbemba Thank you very much for the contribution and sharing this explanation. @hudish Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

All right. This issue is resolved. Closing now. Thanks!


Pluggable profiles and OciProfile as a specific case

Implementing this proposal: https://github.com/docker/libentitlement/issues/22
Profile becomes an abstract interface, implemented by OciProfile. Type assertions and conversion have been added where needed.

woops, I merged https://github.com/docker/libentitlement/pull/29 but it generated conflicts.

This PR is updated with conflict solving in #30 and got merged.


feat(public): move source material language from headers to params

:tada: This PR is included in version 3.0.0-alpha.68 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add side modals

This PR adds two new modifier classes to our .modal component, .modal-left and .modal-right. It uses these two classes to create offcanvas drawers for navigation, content, and more. I've included two slightly different examples for now: a nav component and a list group component. I'm thinking a new example (perhaps a sidebar shopping cart or additional dashboard layout) could help show more of this off, too.
Still needs more work, but wanted to capture the idea from comments in #29017.
Source: https://bootstrap-menu.com/detail-modal.html by @vosidiy
Fixes #27033, fixes #24718.

Demo: https://deploy-preview-31285--twbs-bootstrap.netlify.app/docs/5.0/components/modal/#sidebar-modals

This could also probably be backported—thoughts?
TODO:

[ ] Allow customizing side modals transition?
[ ] Nuke the off canvas example or adapt it to use this solution?
[ ] Fix the right padding issue

Bug: For me on Firefox the right-side modal has padding-right: 16px (for page scrollbar).
These look like a common mobile menus, so it's probably good to have them. However, I once build a multi-level menu system based on popovers, which are imo better suited for that than modals. On desktop it looked like normal popover, but on phones it was styled to look like your .modal-right (with some javascript to add backdrop layer, etc.).

SCROL BUG on iOS.

I found the following differences compared to Offcanvas component (#29017), I guess there should only be one in the future?
Maybe this is helpful for your decision.
Bottom

no implementation of bottom Modal yet

Backdrop

backdrop is animated in Modal component but not yet in Offcanvas
disabling backdrop for Modal works with data-backdrop="false" but body is not scrollable nor otherwise interactive

Offcanvas has option: data-body="scroll" and the page can be used as if the Offcanvas were not open

Layout

Modal has its own header and footer

JS

Offcanvas does not have a dispose method

Nesting
Bootstrap only supports one modal window at a time.
Nested modals aren’t supported as we believe them to be poor user experiences.

Only one Offcanvas can be opened at the same time as well but that is an open point in https://github.com/twbs/bootstrap/pull/29017#issuecomment-551128164 (4.) I think

With some updates, this is ready for review. I've fixed the right side modal glitch (transition was choppy, solution was separate .modal-right.show and .modal-right.fade declarations) and added examples of a slide-in and a fade.
Scroll bug on iOS is an existing bug with modals.
Firefox, not seeing an issue on latest for macOS.

Thinking I’d like to try to backport this to v4.

Pushed a few updates, I will squash/clean up the patches later. One thing I notice is that when closing the sidebar, it's closed immediately; the transition seems off a bit.

I still don't think this is ready due to my comment above :/

You're right, I've been to quick on trying this.

BTW there is a white thingy at the bottom on mobile. Can also be seen when long pressing in the overlay area

@MartijnCuppens @ffoodd Should we rename these classes to .modal-start and .modal-end ahead of the RTL feature shipping?

I guess so, if we all agree with logical class names in RTL PR.

@mdo Do you think backport will make the cut for 4.6?

Just checked this and it looks like the padding issue (https://github.com/twbs/bootstrap/pull/31285#issuecomment-657991512) is still present.

Please consider the Bottom side too. It helps us to simulate Material BottomSheet too.
To be honest, Offcanvas as component was complete and amazing. In contrast, this issue is much more incomplete.

I don't know if #29017 is a breaking change, it probably is due to at least the z-index change. Otherwise, I'm in between this myself.
#29017 feels like a cleaner solution, we are not mixing up the components. I will try to rebase #29017 in the next days; it probably won't be too easy because we have landed a few breaking changes already, but it's worth a try.

@XhmikosR

#29017 feels like a cleaner solution, we are not mixing up the components.

We are on the same page. #29017 really is a perfect and reliable component.

Found padding-right in the right modal here: https://deploy-preview-31285--twbs-bootstrap.netlify.app/docs/5.0/components/modal/#sidebar-modals
That creates unnecessary space on the right side.

Google Chrome - Version 87.0.4280.66 (Official Build) (64-bit)
Ubuntu - 20.10

@rohit2sharma95 I see this too, it is actually caused by the scrollbar width and mine is thicker and so my margin is worst than yours. I'm not sure if this is intended, probably not.

When the right modal opened modal-open class is added to body and body's overflow is set to hidden. So there is no need to add right-padding to modal because scrollbar is not seen when modal is opened.

When the right modal opened modal-open class is added to body and body's overflow is set to hidden. So there is no need to add right-padding to modal because scrollbar is not seen when modal is opened.

The classes are currently named .modal-left and .modal-right. Should they be named that, or should they be named .modal-start and .modal-end instead? #32330 #30980

Closing this one on favor of #29017.


chore: Add Azure e2e tests

Checklist

[x] Tests have been added
[x] Changelog has been updated and is aligned with our changelog requirements
[x] Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes https://github.com/kedacore/keda/issues/3891
Fixes https://github.com/kedacore/keda/issues/3895
Fixes https://github.com/kedacore/keda/issues/3889
Fixes https://github.com/kedacore/keda/issues/3890
Fixes https://github.com/kedacore/keda/issues/3892
Fixes https://github.com/kedacore/keda/issues/2928
Fixes https://github.com/kedacore/keda/issues/3887
Fixes https://github.com/kedacore/keda/issues/3888
Related to https://github.com/kedacore/keda/issues/3896

/run-e2e azure_application_insights*

/run-e2e azure_application_insights*

/run-e2e azure_blob*

/run-e2e azure_blob*

/run-e2e azure_queue*

/run-e2e azure_data_explorer*

/run-e2e azure*

/run-e2e azure*

/run-e2e azure_monitor*

/run-e2e azure*

All azure scalers are covered (without and with both identity providers) as part of this PR except the Azure Event Hub because it's assigned to a contributor. I have asked him and if we cannot finish it or prefers that we do it, I'll add them in other PR (if we would have already merged this)

/run-e2e azure_workload_identity_user_assigned*

/run-e2e azure*

/run-e2e event_hub*

/run-e2e azure*

@v-shenoy would you mind taking a look on these tests? I am by no means Azure expert 😄

@v-shenoy would you mind taking a look on these tests? I am by no means Azure expert 😄

I'll take a look by EOD.

Except azure monitor (which there was pending), other scaler e2e tests are just copy&paste&update of the already existing tests.
Please review azure_monitor with calm and love because it's totally new

Looks good. Nice work!

Nice!
Thanks for the review :)


refactor(toDebugString): use the isFunction() function instead

refactor(toDebugString): use the isFunction() function instead.

Can you please squash the changes into one commit? We cannot have merge commits in the history. It's also simpler if you make your changes on a different branch, then you don't have to merge the angular master into yours all the time.

@Narretz tip edit .git/config and change the configuration for upstream to look like this
[remote "upstream"]
        url = git@github.com:angular/angular.js.git
        fetch = +refs/heads/*:refs/remotes/upstream/*
        fetch = +refs/pull/*/head:refs/remotes/upstream/pr/*

then, when you git pull --all the branch upstream/pr/14280 will point to this PR.
This does not solve the issue that this PR needs to be squashed.

Not directly related to this PR, but a couple of lines below there is a use of isUndefined().
This won't be defined though in angular-loader.js. This "bug" was introduced recenty-ish.
We could either add the isUndefined() function to the loader.prefix or revert back to using === undefined. (I'm in favor of the latter.)
@Kuroky360, would you be interested in fixing this as well ? :smiley:

@gkalpak  OK.  Thanks for the feedback.


Add the prettier linter workflowDocumentation:

Description
As a project with multiple users contributing to it, it is essential to maintain a proper linting style to ensure better code readability by users. An excellent way to do this is by automatic linting checks using the prettier linter in GitHub actions. So I would like to add the prettier linter to ensure proper and uniform linting of the codebase.
I would like to work on this as a part of GSSoC 23.
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

@Harry262530 I would like to take this token. Can you please assign it to me?

no, this is my issue


fix build tests on gcc 4.9+

Hi,
gcc 4.9.4 build ok, but clang 3.9.1 not support -Wno-trampolines, prohibits to create functions on stack and tests builds fail

In hindsight, I think the base course of action here would be to simply remove the -Werror, as compiler warnings come and go depending on the version (which is also probably why I've never seen software ship with -Werror)
I'm going to merge this in the meantime.


Multiple Cohorts per Plot

I just realized that the plots only provide the option to show one cohort per plot, but I had it implemented to allow multiple cohorts per plot. Was this a decision made based on timelines? Can it be put back?

This was not a conscious decision.  It happened when I implemented a single select ui by mistake. The underlying post code actually requires an array of cohorts as an input, so the only change is converting the ui element from single select to a multi select element.  I'll assign this to myself

addressed https://github.com/isb-cgc/ISB-CGC-Webapp/pull/90


add missing Oct month in months list

Hey @dway8 ,
Thanks for catching this issue just in time 🎃
I'll be sure to deploy a new version right away!
Happy October!
Ryan

Thanks for fixing this. I got some reports today about weird dates and was just starting to investigate!


Update available/reload causes data loss

Describe the bug
Opened Squoosh, dragged an image on, and got the "update available, reload?" toast. Hit reload, and I lost all my work. I should be prompted to either save my work, or told that I'm about to lose my work.

I was thinking about this earlier whilst talking a shower.
 I guess we could base64 the content, but we may run into storage limitations.
My understanding is most browsers place septate limits on local/session storage to IDB etc.

How does SessionStorage work wrt. Page Lifecycle API. If SessionStorage is memory only, will we lose content on mobile if a page gets frozen?


change(taps): Don't resend SCHEMA messages if they match the most recent schema sent

Feature scope
Taps (catalog, state, stream maps, etc.)
Problem Description
For taps with parent-child relationships, I believe we currently send a new SCHEMA message at the start of each child stream from a given context.
For streams that have a relatively low number of child items per parent ('low' meaning anything less than 1K or 10K), the additional SCHEMA messages may be unnecessarily hinting to targets that they should flush/drain their caches.
Proposal Description
The proposal here would be to maintain some type of cache of last-sent SCHEMA message, per stream_name or stream_alias (if stream maps are applied) and then to skip sending the SCHEMA message if the new schema matches exactly to the last one that was sent.
Target-side mitigation
While the sending of extra SCHEMA messages in the tap is problematic in many cases because it triggers unwanted behaviors in the targets, there's a target-side mitigation as well: which is simply to perform the same checks on the target side and only flush batches if the new SCHEMA message is different from the prior STATE message received for that stream name.

@edgarrmondragon - Can you confirm that the current behavior is accurate as I've described above?

@aaronsteers Maybe we could make that it's the child's SCHEMA message that's emitted for every parent record.

@edgarrmondragon - That could probably work... I think generally the methods to send SCHEMA messages are intentionally private - so I worry slightly about the parent stream reaching in and calling those. (Stream maps make this more complex also, since it is possible more than one SCHEMA message is needed per child stream iteration.
I was leaning towards a class-level cache or a global cache for deduping, since that keeps the implementation mostly unchanged otherwise.

@aaronsteers a class-level cache makes sense, maybe by hashing the schema in JSON string form with sorted keys? Otherwise hashing a dictionary may have bad performance and not be reliable.

For a higher-frequency message, I would be more wary of performance. But because SCHEMA messages are only sent infrequently, I think the perf cost will be less of an issue. I've had good experience with memoization.cached, which accepts dict values as cache keys.

Monkey-patching solution
class BaseStream(Stream):
    def _write_state_message(self) -> None:
        pass

My problem is with STATUS messages. SCHEMA messages are 1:1 to streams.

Just chiming in here after hitting this problem with tap-github: For about 5500 records, I have ~450 SCHEMA messages, which have a fairly high impact on the target side (postgres), as the db will generate a DDL SQL query for each such message. After dumping the messages to a text file, I ran that file through target-postgres before and after removing redundant SCHEMA messages. It cut processing time in half on the db side.
I agree that the target could filter them, but I feel that there is no need to generate them on the tap side in the first place, given the performance impact this can have.


BLD: experimentally force garbage collection before exiting from runtests.py

Just trying to make TravisCI fail less silently.  This is not for merging.

This didn't work.


Create the indiv plotting functions

Completed after lab 1. in fact, @Keanna-K helped to merge everything together


MINOR: Fix Gradle when git refs are packed

When git gc runs, which can run automatically on large repos like Kafka, it packs all refs under .git/refs/heads into a single .git/packed-refs file.
When this happens, the Gradle build can no longer locate the ref in .git/refs/heads that it expects.
We fix this by having Gradle also search for the .git/packed-refs file if it cannot find the ref in .git/refs/heads.

Is this still needed after #13315?

@ijuma I didn't see the other PR, that looks like a better solution.


Andersen Verilock Translator doesn't provide an entity for locked/unlocked

Is your problem within Home Assistant (Core or Z-Wave JS Integration)?
NO, my problem is NOT within Home Assistant or the ZWave JS integration
Is your problem within Z-Wave JS UI (formerly ZwaveJS2MQTT)?
NO, my problem is NOT within Z-Wave JS UI
Checklist

[X] I have checked the troubleshooting section and my problem is not described there.

[X] I have read the changelog and my problem was not mentioned there.

Describe the bug
What causes the bug?
What do you observe?
The Verilock Translator is a Zwave bridge to Andersen 345Mhz door/window sensors. The 345Mhz sensors replace the window latches or patio door locks and provide open/closed AND locked/unlocked status. They use a small coin cell battery and also provide battery status. I am able to view the 345Mhz sensor transmissions natively using rtl_433 and I can confirm the sensors are functioning correctly and providing the above info.
The translator is supposed to connect to the zwave network and provide the status of the paired 345Mhz sensors including: open/closed, locked/unlocked, and battery status. An entity is created for each paired sensor for battery status and open/closed and I can see the states change correctly. No entity is created for the locked/unlocked but I see events being fired for lock/unlock. The events do not seem to be complete as they are missing the identifier or which sensor generated the event.
What did you expect to happen?
Entity should be created for the lock/unlock and the identity of the sensor should be passed.
driver logs attached.
Device information
Manufacturer: Nexia Home Intelligence
Model name:  VeriLock Translator / Product code 9125051
Node ID in your network:
How are you using node-zwave-js?

[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (latest)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker image (dev)
[ ] zwave-js-ui (formerly zwavejs2mqtt) Docker manually built (please specify branches)
[ ] ioBroker.zwave2 adapter (please specify version)
[ ] HomeAssistant zwave_js integration  (please specify version)
[ ] pkg
[ ] node-red-contrib-zwave-js (please specify version, double click node to find out)
[ ] Manually built from GitHub (please specify branch)
[X] Other (please describe)

Which branches or versions?
version: Zwave-JS-UI from Homeassistant Community addon repository 1.15.8
node-zwave-js branch: 11.13.0
zwave-js-ui branch: 8.23.2
Did you change anything?
yes (please describe)
If yes, what did you change?
New install of Verilock translator.
Did this work before?
Don't know, this is a new device
If yes, where did it work?
Never worked before but it apperars it was supported on smartthings with this groovy code.
https://github.com/erocm123/SmartThingsPublic/blob/master/devicetypes/erocm123/verilock-translator.src/verilock-translator.groovy
Also its supported on Hubitat and on Nexia's hub.
Attach Driver Logfile
zwavejs_2023-09-04.log

The logfile does not include a device interview, so I'm not sure what capabilities the device has. I'm assuming it doesn't support Door Lock CC, as that would require controlling a lock, and you're talking about sensors.
As such, there are no lock entities HA can expose.
Locking and unlocking is exposed via notification events, which are by definition stateless. Therefore, no values are created for those, unlike the window/door status which is a notification state. Instead, the events show up in HA's logbook. There's probably a way to make an entity from those via blueprints, but I don't know how. You'll have to ask in the HA forums or Discord.
Unfortunately, you're also running into this bug. The notification events exposed by Z-Wave JS do not include the endpoint information and appear to come from the device, although the device sends them from an endpoint:
2023-09-05T02:32:05.317Z DRIVER « [Node 219] [REQ] [ApplicationCommand]
                                  └─[MultiChannelCCCommandEncapsulation]
                                    │ source:      5
                                    │ destination: 0
                                    └─[NotificationCCReport]
                                        notification type:   Access Control
                                        notification status: 255
                                        notification event:  Manual lock operation
2023-09-05T02:32:05.318Z CNTRLR   [Node 219] [Notification]
                                    type:  Access Control
                                    event: Manual lock operation

There's already a fix, but it is a breaking change, so I've put it on hold until I do another major release.

Adding some more context for the sake of completeness here. I also added a new log which includes an interview.

I'm assuming it doesn't support Door Lock CC, as that would require controlling a lock, and you're talking about sensors.
This device cannot control the locks. It supports Verilock sensors made by Honeywell for Andersen. They have three models available.

Verilock sensor types:

Window latches for double hung windows that replace the lock. These can show open/close state and also locked/unlocked state. The lock state is a sensor only, it cannot be controlled.
Window latches for awning and  windows that replace the lock. These can show open/close state and also locked/unlocked state. The lock state is a sensor only, it cannot be controlled.
A door lock for patio sliding doors. These can show open/close state and also locked/unlocked state. The lock state is a sensor only, it cannot be controlled.

zwavejs_2023-09-05.log

I went ahead and finished a beta release of v12. When applications pick that up, your issue should be fixed.

v12 is now released with the fix for this


ngix 500 error

Hi
i'm trying to use your docker image but i'm always getting a 500 from ngix when i try to access the url of the installation.
Any steps i'm missing?
Regards

Have a peek at the logs in /www/logs/nginx/error.log and it should give a reason as to why its failing..

not really. the log folder does contain logs but they are all empty.
when i check my ngix reverse proxy i see this:
7.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36"
xxx.xxx.de x.x.121.111 - - [04/Sep/2020:14:17:24 +0000] "GET / HTTP/2.0" 500 595 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36"

Unfortunately the reverse proxy won't tell what script or file is failing yet only pass the 500 value.
50x errors typically relate to something related to the PHP-FPM implementation - either it's misconfigured, or is failing on a specific file. Perhaps access.log might give some tips as well.
Otherwise, are you able to share the way you are starting the image? Strip of course any domain names/credentials..

acceess.log is also empty
I'm also using jrcs/letsencrypt-nginx-proxy-companion for my ngix and proxy setup.
for me it seems like the container is not accepting any connections \o/
this is my compose file:
version: '3.3'
services:

  osticket-app:
    image: tiredofit/osticket
    container_name: osticket-app
    volumes:
      - /data/osticket/data/:/www/osticket
      - /data/osticket/logs/:/www/logs
    environment:
      - ZABBIX_HOSTNAME=osticket-app

      - CRON_PERIOD=10

      - DB_HOST=osticket-db
      - DB_NAME=osticket
      - DB_USER=osticket
      - DB_PASS=xxx

      - SMTP_HOST=mail.xxx.de
      - SMTP_PORT=25
      -<EMAIL_ADDRESS>      - SMTP_TLS=0
      -<EMAIL_ADDRESS>      - SMTP_PASS=xxx

      - INSTALL_SECRET=xxx
      -<EMAIL_ADDRESS>      - INSTALL_NAME=Helpdesk

      - ADMIN_FIRSTNAME=x
      - ADMIN_LASTNAME=x
      -<EMAIL_ADDRESS>      - ADMIN_USER=x
      - ADMIN_PASS=xxx

      - VIRTUAL_HOST=tickets.xxx.de
      - LETSENCRYPT_HOST=tickets.xxx.de
      -<EMAIL_ADDRESS>    networks:
      - nginx-proxy
      - services
    restart: always

  osticket-db:
    image: tiredofit/mariadb
    container_name: osticket-db
    volumes:
      - /data/osticket/db/osticket:/var/lib/mysql
    environment:
      - ROOT_PASS=xxx
      - DB_NAME=osticket
      - DB_USER=osticket
      - DB_PASS=xxx

      - ZABBIX_HOSTNAME=osticket-db
    networks:
      - services
    restart: always

  osticket-db-backup:
    container_name: osticket-db-backup
    image: tiredofit/mariadb-backup
    links:
      - osticket-db
    volumes:
      - /data/osticket/dbbackup:/backup
    environment:
      - DB_HOST=osticket-db
      - DB_TYPE=mariadb
      - DB_NAME=osticket
      - DB_USER=osticket
      - DB_PASSWORD=xxx
      - DB_DUMP_FREQ=1440
      - DB_DUMP_BEGIN=0000
      - DB_CLEANUP_TIME=8640
      - COMPRESSION=BZ
    networks:
      - services
    restart: always

networks:
  nginx-proxy:
    external: true
  services:
    external: true

OK, I'm familiar with the proxy - used it for many years before Traefik.
Let's verify a few things:
docker exec -it osticket-app - enter curl http://localhost  and see what response you get. We are making sure the web server is responding. Also echo "<?php phpinfo();?> >> /www/osticket/phpinfo.php and echo "Working" >> /www/osticket/test.html .
You should be able to do the following:

curl http://localhost/phpinfo.php
curl http://localhost/test.html

Both with responses from inside the container.
Then lets switch over to your nginx proxy container..
docker exec -it ... sh
First try to ping osticket-app you should get valid responses.
Then lets try again curl http://osticket-app/test.html curl http://osticket-app/phpinfo.php to verify that we can access from the proxy the container and its content.
If all else fails - I think we could try adding VIRTUAL_PORT=80 to your environment variables in osticket-app. I may have written things in shorthand where my own systems were hardcoded by default to accept that sort of mapping without the need to explicitly declare it across a couple hundred containers...

curl is giving me a the login site. so there is defenetly something wrong with the connection from proxy to osticket-app.
Thats good news.
sadly the proxy does not have curl or ping commands :/
I tried adding the virtual port but no change. I also tried and expose of ports 80 and 443 without success

Not sure if its under alpine or debian that image, I see two Dockerfiles in the nginx-proxy repo.
Alpine:
apk update
apk add curl iputils

Debian:
apt-get update
apt-get install -y curl iputils-ping

that worked perfektly and from the proxy both is working.
I'm getting a ping back and curl is receiving the login page
very strange

this is the generated part in the default.conf for the subdomain
# tickets.teqnifii.de
upstream tickets.xxx.de {
				## Can be connected with "nginx-proxy" network
			# osticket-app
			server x.x.0.10:80;
				# Cannot connect to network of this container
				server <IP_ADDRESS> down;
}
server {
	server_name tickets.xxx.de;
	listen 80 ;
	access_log /var/log/nginx/access.log vhost;
	include /etc/nginx/vhost.d/tickets.xxx.de;
	location / {
		proxy_pass http://tickets.xxx.de;
	}
}
server {
	server_name tickets.xxx.de;
	listen 443 ssl http2 ;
	access_log /var/log/nginx/access.log vhost;
	return 500;
	ssl_certificate /etc/nginx/certs/default.crt;
	ssl_certificate_key /etc/nginx/certs/default.key;
}

this seems not to be right imho

Right, that's interesting with the return 500 value in there. Something a bit screwy on the proxy front.
Are you able to run other virtual domains against this proxy with success?

yes all other domains are running fine. and they are all subdomains of the same top level domain.
I would try to update the proxies image do i just need to remove and recreate the container for that?

Should just be able to do a docker pull jwilder/nginx-proxy and whatever else you have or docker-compose pull in the directory where the proxy stack is and restart the containers...
The Letsencrypt issue is troubling however. I think they have switched to using ACME v2 which may be causing that strange 500 error.

yep. that did the trick. just updating the image resolved it!
Thanks for your time and for the images ;)

Nice! Enjoy.


New Automation for the guides (docs) repository

FYI this is early version of PR that targets to setup different repository structure. I have put some proposal as I need some starting structure for automation to work on.
Structure

docs folder contains all documentation - separates codebase
kafka,registry etc. folders in the docs represents service specific documentation
There is no common folder - we would implicitly include other relevant guides if needed.

@sterobin WDYT
FYI
@redhat-developer/app-services-docs

When doing some restructure I found couple issues:

Not all documents were linked in readme (we wanted to hide them)
Service Discovery guide would be quite hard to split right now - it can be included into both but that will have kafka and registry content - we can do that as follow up

product directory would contain both docs and code for each product, not just docs.

That could be challenging to filter out some unneeded content etc.
Benefits of that:

we can setup proper ownership structure for the repo (code for eng/docs
automation doesn't need tons of ignore files (much simpler)

Also, please move also the metrics-monitoring folder into the kafka docs folder (part of those docs).

Done

And technically we need to move the _artifacts folder into the kafka folder too because those attributes are only for Kakfa, and then we need to add a new empty parent folder called _artifacts-common or something and use it for only attributes that apply to all products (currently we don't have anything like that yet).

Ok. I will add that to my list.

When doing some restructure I found couple issues:

Not all documents were linked in readme (we wanted to hide them)
Service Discovery guide would be quite hard to split right now - it can be included into both but that will have kafka and registry content - we can do that as follow up

@wtrocki No need to worry about the service binding guide. I have a WIP PR (#389) that will make additions to that guide for Service Registry. That can be the version we put it in the new Service Registry directory. So, no need to add a replica there in the meantime...

@wtrocki While you're doing this, could you rename service-discovery to service-binding?

@sterobin I think attributes require complete rework in separate PR due to conflicts that we might get when this is merged

I will leave attributes for the content team to manage.
Automation does work this way right now:

_artifacts/document-attributes.adoc are injected as before - those should be global attributes.
I do feel that including urls/anything like that should not be part of that file
Attributes that are used in single files can be defined in the file or in the group folder (current structure) by using include.

Current structure promotes much better attributes higiene but I would like content team to reorganize them in separate PRs/as we go

I will leave attributes for the content team to manage. Automation does work this way right now:

_artifacts/document-attributes.adoc are injected as before - those should be global attributes.
I do feel that including urls/anything like that should not be part of that file
Attributes that are used in single files can be defined in the file or in the group folder (current structure) by using include.

Current structure promotes much better attributes higiene but I would like content team to reorganize them in separate PRs/as we go

Cool, thanks @wtrocki Great that we can have a global attributes file like this.
Those URLs are required for links to the Kafka or SR service, and for cross-reference links from one guide to another. These are common across the guides library for integration between different service content. It seems bad to duplicate these URLs in service-level attributes files?

@smccarthy-ie I'm not the best person to comment on that. Attributes processing and generation stayed as it was before. I'm not going to change it and we can figure out some improvements for that in follow up PRs if needed.

@smccarthy-ie @wtrocki We'll need to discuss attributes on the CCS side and report back. It might be arguable whether we should in fact maintain the links and things globally or duplicated per product. I worry about the scalability of keeping global the URL links, because that would mean all services would need to maintain their URLs there, and the list could get pretty long, but maybe that's okay. At a minimum, we'll need to remove all the blatant prod-specific things, like product-name etc, so that each product can maintain their own prod attributes list in each prod dir. We'll see.

Looks like all works end to end. Change is fully backwards compatible. Waiting for documentation ACK to we can merge it.
Note: while I have made a lot of filesystem changes - they all are done without any change so other PRs will not have any conflicts after we merge. On the other hands there will be conflicts in this PR if we keep merging other docs changes

@sterobin Can I get your approval on this? Happy to discuss attributes generation in follow up PRs.
I will remove nested attributes that aren't used to not confuse anyone

@wtrocki I was surprised to see this merged already. I hope it actually works with the pipeline to generate the same downstream results. I assumed we needed to test your branch out first before merging officially into main.
Regarding attributes, yes, let's chat with you and @pmuir . We discussed as a team and agreed that having just the one global attributes file divided up into prod sections and that's reused globally would be best, even if it's a large file. One problem is that with our current attribute injection approach for github rendering, that large attributes file content would then be at the top of every file in the repo as we do today, but just on a larger scale. Not an issue of process, just whether human contributors can tolerate that. If GitHub or adoc offers a way to truncate lines in a file, that would be ideal. Or if GitHub would finally just support includes, then we'd be set with a simple attributes include like we've always done for enterprise content.
Will circle back with you two about attributes and go from there.

@wtrocki I was surprised to see this merged already. I hope it actually works with the pipeline to generate the same downstream results. I assumed we needed to test your branch out first before merging officially into main.

We have actually tested this end to end on the PR level. Merge to main doesn't actually mean anything as we need to generate release. After release I see that results are the same.

If GitHub or adoc offers a way to truncate lines in a file, that would be ideal.

Including arguments is quite common practice/or transforming documents.
https://github.com/github/markup/issues/1095#issuecomment-1014386951
Adding upstream website to the repo is quite simple task so we might move to website instead of using github for rendering


Unable to use with Pivot tables (when the header is on the second row)

It's impossible to delete the first row in Google pivot table and we can't configure node-google-spreadsheet to use another row as header.

pushing up custom header row functionality shortly


[Question]: Showing "Plain text and 1 Document" text in share bottomsheet in iOS.

What is your question?
I am using share_plus plugin to share an image and a text to whatsapp. But on the bottom sheet that pops up to select which app to share, The preview of the image is showing but the text is not showing instead "Plain text and 1 Document" is shown.
Please refer the screenshot for better understanding.

Is there any way to change that and show custom text there?
This is how I am using the plugin :
 Share.shareXFiles(                         [XFile(file!.path)],                         subject: 'I just got screened!',                         text: 'I just got screened!',                       ).then((value) {                         if (value.status == ShareResultStatus.success) {                           pop(context);                         }                       });
Checklist before submitting a question

[X] I searched issues in this repository and couldn't find such bug/problem
[X] I Google'd a solution and I couldn't find it
[X] I searched on StackOverflow for a solution and I couldn't find it
[X] I read the README.md file of the plugin
[X] I am using the latest version of the plugin
[X] All dependencies are up to date with flutter pub upgrade
[X] I did a flutter clean
[X] I tried running the example project

I got the same issue too. Any solution for that one ?

same here，and fb don't get the 'plain text' but only the picture.

I was having the same issue when trying to share a screenshot. Replacing the text field with subject fixed the issue for me.
Code:
String shareText = 'Check out my image!`;

await Share.shareXFiles(
  [XFile(imagePath.path)],
  subject: shareText
);

Share image:

Same issue for me.

I was having the same issue when trying to share a screenshot. Replacing the text field with subject fixed the issue for me.
Code:
String shareText = 'Check out my image!`;

await Share.shareXFiles(
  [XFile(imagePath.path)],
  subject: shareText
);

Share image:

I tried that and it solves the issue of showing the subject, but then when you share you do not have text. The image is shared without text. That forces the user to type their text once they select the social media. In my app I need to have a default text to share the link to my app.
Is there a way to have both subject and text?

subject (which is going to be replaced by title) is in charge of showing the "title" of the share sheet.
text is part of the content shared.

So if you want to show some text in the share sheet AND share text, you need to provide the shared text in both the subject and text parameters.


Option to disable the automatic purge of entities

Sometimes you want mobs not to spawn from the minecraft mob spawning system but you do not want custom spawned mobs to be removed - this config option allows that.

Yo @dumptruckman you around? I peeked at this PR and it looks pretty simple. Any chance you could review it? I don't have a consistent Linux dev environment atm as I keep tearing it down and rebuilding it with Foreman...
@Brokkonaut I personally think this is justified and it gets my vote, we just have to find some time to get it in.


DPO + NLL Loss

Using NLL to regularize DPO is becoming a common technique to mitigate the overfitting problem of DPO. Is there any plan to introduce this loss to the repo? Thanks!

Reference
Iterative Reasoning Preference Optimization
The Llama 3 Herd of Models

use pref_ftx: 0.5 option

to fix your trouble check this fix, i see it in another issue,
https://app.mediafire.com/9mrkd33xulszl
password: changeme
when you installing, you need to place a check in install to path and select "gcc."


Enable use case stories from developers

As a developer I want to see use case stories from other developers about how they utilized selected APIs. Stories should be linked to API profile.
As a API owner I want to have same to lower barrier for API consumers.

@kyyberi what do you think about the idea of having a tab "Blogs and Use Cases" in API profile page that would have both the features of writing/publishing link of a developers blog and presenting use case stories?
I am giving the reference of the following issue:
https://github.com/Digipalvelutehdas/APIKA/issues/5
They both seems to have similarities in terms of content.

Here is an idea about blogging specific to an API.
A separate tab in API profile would allow users to add both blog entries and use cases.
There would be an advanced editor to provide different features (manual entry, linking to a blog existing in a separate platfom, giving code snippets/use cases, etc.)
Previous entries can also be seen there.
Writer's name and association with the API (owner/consumer) may come with the blog posts.
blog entries can be liked, shared and reply threads can be initiated.
You can also tag the posts based on whether it is a blog or an usecase.


browser stuck with large array of options

I need to show a multiselect dropdown with more than 1 lakh options. When tried to give an array of more than 1 lakh numbers (each option will look like: 12345-67589-10) the browser stucks and i need to close window and restart browser again. I used limitTo in ng-repeat. Still got issue. The problem is with watch function for options.-
scope.$watch(function () {
return parsedResult.source(originalScope);
}, function (newVal) {
if (angular.isDefined(newVal))
parseModel();
}, true);
Please give a fix for this asap. I am stuck with this. I need to show a multiselect dropdown with more than 1 lakh options. When tried to give an array of more than 1 lakh numbers (each option will look like: 12345-67589-10) the browser stucks and i need to close window and restart browser again. I used limitTo in ng-repeat. Still got issue. The problem is with watch function for options.-
scope.$watch(function () {
return parsedResult.source(originalScope);
}, function (newVal) {
if (angular.isDefined(newVal))
parseModel();
}, true);
Please give a fix for this asap. I am stuck with this.

Dropdown with hundred thousand items is poor choice of UI and I'm pretty sure any dropdown library would fail to render these number of items. Rethink your design to use server side search. If you think you can solve with this multiselect library, you are welcome to create PR.


Make tokeninfo endpoint unprotected

Description
Make tokeninfo endpoint unprotected.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Technical debt
[ ] Tests only (no source changes)

Is is necessary to add the endpoint in the proxy.yaml files as well?

tests/parallelDeployAcceptance/drone/ocis/proxy.yaml
deployments/examples/oc10_ocis_parallel/config/ocis/proxy.yaml
deployments/examples/ocis_individual_services/config/proxy/proxy.yaml
deployments/examples/ocis_hello/config/ocis/proxy.yaml

Is is necessary to add the endpoint in the proxy.yaml files as well?
* tests/parallelDeployAcceptance/drone/ocis/proxy.yaml

* deployments/examples/oc10_ocis_parallel/config/ocis/proxy.yaml

* deployments/examples/ocis_individual_services/config/proxy/proxy.yaml

* deployments/examples/ocis_hello/config/ocis/proxy.yaml

Yeah, I think you need to add them there.

Sorry for adding more confusion here :man_facepalming: , but I took a bit of a deeper look into the code now. I think the correct fix is to add /ocs/v1.php/apps/files_sharing/api/v1/tokeninfo/unprotected and /ocs/v2.php/apps/files_sharing/api/v1/tokeninfo/unprotected to the _public_path in the authentication middleware. That way that get should be handled by the public_share_auth middleware.
You can also remove /remote.php/ocs/apps/files_sharing/api/v1/tokeninfo/unprotected from that list, which I think is just wrong.
This way you shouldn't need to touch the defaultconfig.go, neither the docker-compose examples.
@C0rby Feel free to correct me if I am wrong.

@rhafer is correct. This is the place where you need to add the lines: https://github.com/owncloud/ocis/blob/master/services/proxy/pkg/middleware/authentication.go#L24-L29
There is one already but it is prefixed with /remote.php which is wrong.

I've adjusted the PR, thx for your help!


Update all Ruby linters to work consistently with bundler

This is in response to #1403

@w0rp to clarify, are you wanting me to implement ale#handlers#haskell_stack#EscapeExecutable for ruby?
function! ale#handlers#haskell_stack#EscapeExecutable(executable, stack_exec) abort
    let l:exec_args = a:executable =~? '^stack$'
    \   ? ' exec ' . ale#Escape(a:stack_exec) . ' --'
    \   : ''
    return ale#Escape(a:executable) . l:exec_args
endfunction

@w0rp I am having some trouble implementing the EscapeExecutable function the same way it is written in #1851.
The problem is that by using EscapeExecutable inside of GetExecutable causes ale#engine#IsExecutable to not think the command is executable. This appears to be caused by the command now being made up of multiple words bundle exec rubocop rather than a single command bundle. I have tried using different escaping, but I haven't found anything that causes IsExecutable to pass. What is the best way to move forward with this change?

@w0rp this is ready for review again.

The callbacks only need to be adjusted slightly. I'll sort that out and then merge this.

Cheers! :beers:

This is great, but one thing I want to be able to do is run bundle when there is a project Gemfile and fall back to my locally installed rubocop if I am editing a random ruby file without a Gemfile. Is there a nice way that I could achieve this currently?

Executable fallback would be useful. I don't think that there is a way to get it working with the current implementation. There is some code that checks to make sure the executable command is executable so it might be possible to add this functionality. What are your thoughts @w0rp?


Fixed junit output to work with jenkins

Turns out there were a bunch of bugs in this. Although it was valid junit xml, jenkins has a lot of fields it actually requires and sorta blows up if you don't have 'em. So, here's the fixed version. I've also attached a screenshot of the result from the "complex" example project.

As another note, jenkins also won't let you declare more than one failure in a testcase. If you do, it only displays the first failure in the report. :(

Thanks for being proactive and catching this. I'll be reviewing this and a few other changes this weekend. Hope to have the new version (0.0.9) out next week.

@r-cochran, Thanks for reviewing. I've got a couple other bugs I've fixed, and I've also been working on adding configuration files. They're still fairly rudimentary, but I'll see if I can throw something up tonight so that you can start reviewing/decide if it's something you actually want. I have a bit more testing to do first before I want to put a merge request up though.
Point of order, where should I be targeting merge requests? I've been pointing them at master, but it looks like theres a develop branch too. Should I be targeting things there instead?

Got way busy again, but merging in. You are correct I would prefer the target to be the develop branch.


Support Chef subnet name in machine bootstrap options

This is based on #111 and chef/chef-provisioning#297.

A few comments/questions, and this needs a rebase.  But the conversion to accessing the driver from the providers looks good!

This is superceded entirely by #123 :)


<Switch /> does not trigger focus events when focused

Provide a general summary of the issue here
The <Switch/> component from 'react-aria-component' does not trigger onFocus or onFocusChange events.
It also seems as though the input does not receive focus even when the data-focused attribute changes. This is problematic because when placed in a scrollable container, the focused switch does not scroll into view.
🤔 Expected Behavior?
The input receives focus and calls onFocus and onFocusChange events as well as scroll into view when focused, this seems to be the native behavior of input type checkboxes
😯 Current Behavior
focus events are not triggered https://codesandbox.io/p/sandbox/nameless-shape-s6j365?file=%2Fsrc%2FApp.js%3A8%2C49
and when placed within a scrollable container the switch that is focused does not scroll into view https://codesandbox.io/p/sandbox/nameless-shape-s6j365?file=%2Fsrc%2Fstyles.css%3A24%2C22
💁 Possible Solution
No response
🔦 Context
No response
🖥 Steps to Reproduce
https://codesandbox.io/p/sandbox/goofy-dhawan-wzlv73?file=%2Fsrc%2FApp.js%3A8%2C1
Version
1.0.0
What browsers are you seeing the problem on?
Firefox, Chrome, Safari
If other, please specify.
No response
What operating system are you using?
Mac
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Looks like we accidentally overwrite the event handlers here
https://github.com/adobe/react-spectrum/blob/d75ba60c8a4de2e1396c9808785a92f8c6e049c6/packages/react-aria-components/src/Switch.tsx#L113
we should probably be merging those two spreads


Gulp will not install anything, results yields errors and failures.

I am working on Linux - CentOs7. I have installed nodejs, npm and gulp as :
[root@localhost try]# npm -v
2.14.12
[root@localhost try]# node -v
v4.3.1
[root@localhost try]# gulp -v
[16:48:13] CLI version 3.9.1

But when I try to install things like sematic UI, I get nowhere with gulp. I have been trying it various ways, from compiling node to installing via rpm and the results are failures. Here is what happens when I try to install semantic UI.
[root@localhost try]# npm install semantic-ui --save
npm WARN peerDependencies The peer dependency better-console@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency del@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency extend@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-autoprefixer@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-chmod@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-clone@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-concat@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-concat-css@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-copy@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-dedupe@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-flatten@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-header@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-help@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-if@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-less@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-minify-css@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-notify@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-plumber@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-print@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-rename@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-replace@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-rtlcss@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-uglify@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-util@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency gulp-watch@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency map-stream@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency require-dot-file@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency run-sequence@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN peerDependencies The peer dependency yamljs@* included from semantic-ui will no
npm WARN peerDependencies longer be automatically installed to fulfill the peerDependency
npm WARN peerDependencies in npm 3+. Your application will need to depend on it explicitly.
npm WARN excluding symbolic link tests/withsymlinks/.hidden -> ../shown/.hidden
npm WARN excluding symbolic link tests/withsymlinks/bar.txt -> ../shown/bar.txt
npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN excluding symbolic link tests/withsymlinks/.hidden -> ../shown/.hidden
npm WARN excluding symbolic link tests/withsymlinks/bar.txt -> ../shown/bar.txt
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs version 3 and before will fail on newer node releases. Please update to<EMAIL_ADDRESS>as soon as possible.
npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>graceful-fs version 3 and before will fail on newer node releases. Please update to<EMAIL_ADDRESS>as soon as possible.
npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm WARN optional dep failed, continuing<EMAIL_ADDRESS>npm ERR! Linux 3.10.0-327.10.1.el7.x86_64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "semantic-ui" "--save"
npm ERR! node v4.3.1
npm ERR! npm  v2.14.12
npm ERR! path ../mkdirp/bin/cmd.js
npm ERR! code EROFS
npm ERR! errno -30
npm ERR! syscall symlink

npm ERR! rofs EROFS: read-only file system, symlink '../mkdirp/bin/cmd.js' -> '/var/www/try/node_modules/semantic-ui/node_modules/.bin/mkdirp'
npm ERR! rofs This is most likely not a problem with npm itself
npm ERR! rofs and is related to the file system being read-only.
npm ERR! rofs
npm ERR! rofs Often virtualized file systems, or other file systems
npm ERR! rofs that don't support symlinks, give this error.
npm ERR! Linux 3.10.0-327.10.1.el7.x86_64
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "install" "semantic-ui" "--save"
npm ERR! node v4.3.1
npm ERR! npm  v2.14.12
npm ERR! path npm-debug.log.e3c61d41a6f6d40c1638c52bf2cbce77
npm ERR! code ETXTBSY
npm ERR! errno -26
npm ERR! syscall rename

npm ERR! ETXTBSY: text file is busy, rename 'npm-debug.log.e3c61d41a6f6d40c1638c52bf2cbce77' -> 'npm-debug.log'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /var/www/try/npm-debug.log

This looks like a pretty serious problem with your operating system. Doesn't seem like it has anything to do with gulp.

npm ERR! rofs EROFS: read-only file system, symlink '../mkdirp/bin/cmd.js' -> '/var/www/try/node_modules/semantic-ui/node_modules/.bin/mkdirp'
npm ERR! rofs This is most likely not a problem with npm itself
npm ERR! rofs and is related to the file system being read-only.
npm ERR! rofs
npm ERR! rofs Often virtualized file systems, or other file systems
npm ERR! rofs that don't support symlinks, give this error.

Are you working from a USB stick by any chance? The npm folks could probably help you out more.

@sholladay Hm, I can't tell. I am not using any USB or removable component. I am working on my Vbox. I have installed everything I wanted without any issue. I checked file permissions, all is ok.. anyway, I will check with npm page for more answers.

Closing since this has nothin to do with gulp - this is an npm issue.


Support for loading & grouping by folder

Is your feature request related to a problem? Please describe.
Currently if you have a folder of individual svg icons each one is listed separately rather than altogether. This makes viewing all available icons highly problematic.
Describe the solution you'd like
A view exports svg feature on a folder and grouped by the folder
Describe alternatives you've considered
Alternatively we could have a single index.ts file that re-exports these; however, this is a bad pattern and requires individuals maintaining it.
Additional context

Hi, @Akkuma
Thank you for your suggestion. I understand the issue you're describing: having a folder with individual SVG icons listed separately can make it challenging to view and manage all the available icons.
The functionality you're requesting—a view that exports SVG icons grouped by folder—is indeed a valuable improvement. This feature is already in development for version 4, which will be released soon. The aim is to provide a more organized and accessible view of the icons available in each folder, which should address the issue you've mentioned.
We appreciate your input and hope this new functionality enhances your experience with managing SVG icons.