FFaField requires some special traits for std::array

I needed to add the following streaming traits at https://github.com/SAP/fedem-foundation/blob/main/src/FFaLib/FFaContainers/FFaField.H#L24:
template <typename T, size_t N>
std::ostream& operator<<(std::ostream& stream, const std::array<T, N>& v)
{
  for (unsigned int i = 0; i < N - 1; i++)
    stream << v.at(i) << ",";
  stream << v.at(N - 1);
  return stream;
}

template <typename T, size_t N>
std::istream& operator>>(std::istream& stream, std::array<T, N>& v)
{
  char tmp;
  for (unsigned int i = 0; i < N - 1; i++)
    stream >> v.at(i) >> tmp;
  stream >> v.at(N - 1);
  return stream;
}

So I can deal with this, which has the type defined here
Probably the smartest solution is creating a new type on the same fashion than FFaByteArray

Thanks for reporting these issues, @sanguinariojoe. May I ask what compiler/version you are using?
The fix you suggest here should not be necessary, as we already have the FmArray.H file containing similar definitions, except we there specialize for type int instead of the template parameter T. This file is then included in FmGraph.H such that the FFaField member then should work. And it compiles fine with gcc 7.5 (Ubuntu 18.04) to gcc 11.4 (Ubuntu 22.04) as well as on Visual Studio 2019 with its integrated C++ compiler.
Will it resolve your issue to just change the FmArray.H header accordingly in the fedem_mdb repo?
Another note on your suggestion: You here use comma ',' as separator between the values, whereas we (in FmArray.H) have used a space. Your version will therefore break (probably) when trying to read existing model files having space as separators.

Oh, i did not realiced on fmarray. My bad...
Then it is probably a problem on the order the includes are placed. I
already reported a similar problem with bytesarray on another issue.
I have to take my baby to the kindergarden now. But later i am checking and
giving you feedback (including compiler and so on)
On Tue, 6 Feb 2024, 06:35 Knut Morten Okstad, @.***>
wrote:

Thanks for reporting these issues, @sanguinariojoe
https://github.com/sanguinariojoe. May I ask what compiler/version you
are using?
The fix you suggest here should not be necessary, as we already have the
FmArray.H https://github.com/SAP/fedem-mdb/blob/main/vpmDB/FmArray.H
file containing similar definitions, except we there specialize for type
int instead of the template parameter T. This file is then included in
FmGraph.H such that the FFaField member then should work. And it compiles
fine with gcc 7.5 (Ubuntu 18.04) to gcc 11.4 (Ubuntu 22.04) as well as on
Visual Studio 2019 with its integrated C++ compiler.
Will it resolve your issue to just change the FmArray.H header accordingly
in the fedem_mdb repo?
Another note on your suggestion: You here use comma ',' as separator
between the values, whereas we (in FmArray.H) have used a space. Your
version will therefore break (probably) when trying to read existing model
files having space as separators.
—
Reply to this email directly, view it on GitHub
https://github.com/SAP/fedem-foundation/issues/9#issuecomment-1928817981,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMXKKACAWTYUX7OJTK2MVLYSG6JVAVCNFSM6AAAAABC2ANOJ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRYHAYTOOJYGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

Yeah, the solution is swapping a couple of includes:
#include "vpmDB/FmArray.H"
#include "vpmDB/FmResultBase.H"

at https://github.com/SAP/fedem-mdb/blob/main/vpmDB/FmGraph.H#L11 , and
#include "vpmDB/FmGraph.H"
#include "vpmDB/FmCurveSet.H"

at https://github.com/SAP/fedem-mdb/blob/main/vpmDB/FmGraph.C#L13

May I ask what compiler/version you are using?

My compiler is "gcc version 13.2.1 20230801 (GCC)", with "glibc 2.38".

Another note on your suggestion: You here use comma ',' as separator between the values, whereas we (in FmArray.H) have used a space. Your version will therefore break (probably) when trying to read existing model files having space as separators.

It mostly sure breaks, but I do not think the separator will be the problem, as long as the reader is agnostic to that (it would work with every single-char separator).
Maybe if one changes the locale nasty things might happens... Probably with your version also...

Thanks for quick reply. That's great, I'll just swap those headers then.

but I do not think the separator will be the problem, as long as the reader is agnostic to that (it would work with every single-char separator).

Not sure about this, think in year case the stream >> v.at(i) >> tmp will eat the second value (or the first digit of it) in the tmp variable when reading a file with space as separators? So unless you have other good reason to introduce comma-separators I think I stick with spaces, for the sake of backward compatibility.
So you are using a newer gcc version that we have tried so far. Our experience is that newers versions tend to get more and more strict to adhere to the coding standards (which is good). But then of course there might be some porting work like this before everything runs.
Also note, we have not built the gui part (the fedem-gui repo) with gcc on Linux in a very long time (not since with Ubuntu 16.04), so don't be surprised if there are a lot of issues there (like you already found a few of).

So unless you have other good reason to introduce comma-separators I think I stick with spaces

Absolute! Please, go ahead with the spaces. No interest on commas at all

Also note, we have not built the gui part (the fedem-gui repo) with gcc on Linux in a very long time (not since with Ubuntu 16.04), so don't be surprised if there are a lot of issues there (like you already found a few of).

Let's sail those water together then! :-p


Update DMP Id Lambda to include more info about source of changes

Update the dmphub_modifications array so that it includes a confidence score as well as a note about how the match was determined (e.g. 'matched on grant_id and PI names')

closing this and adding info to #60 since it will need to be done within those lambdas


Optional Redirect URI in documentation

Please follow the issue template below. Failure to do so will result in a delay in answering your question.
Library

[ ]<EMAIL_ADDRESS>or<EMAIL_ADDRESS>[X]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>[ ]<EMAIL_ADDRESS>
Documentation location

[ ] docs.microsoft.com
[ ] MSAL.js Github Wiki
[X] README file
[ ] Other (please fill in)
[ ] Documentation does not exist

Description
Hi, on page it is stated that the redirectURI is optional. By not providing it in the configuration, the authorization code is directly send back to the application.
However, when I remove the redirect uri in the azure project and leave out the field in the client, I get the error message "No reply address is registered for the application."
Is the authorization code flow with pkce even possible without providing a redirect uri? All I want is the authorization code directly back to the client after the user successfully logs in.
Thank you

You don't have to provide a redirectUri in the msal configuration (it defaults to the current page), but it still always needs to be registered in the portal msal to function properly.

@jmckennon thank you. The problem with this approach is that I get an error message after a successful login, saying that the provided redirect uri is not equal to the one provided in the azure project.

The redirectUri in your app will always need to match one of the redirectUri listed in the portal whether it's provided in the app or not. It's optional to provide it in the app configuration only because it defaults to the current window. If that window (for example, http://localhost:30662) is not listed in the portal as a valid redirectUri, you will get an error like this one.


support value-wise query result

https://duckdb.org/dev/sqllogictest/result_verification#row-wise-vs-value-wise-result-ordering
# row-wise
query II
SELECT 42, 84 UNION ALL SELECT 10, 20;
----
42	84
10	20

# value-wise
query II
SELECT 42, 84 UNION ALL SELECT 10, 20;
----
42
84
10
20

sqlite only supports value-wise.
cockroach only supports row-wise, but will use value-wise when option -bigtest is used (i.e., when testing against sqlite's test cases).

I can work around this with tester.with_validator(sql_result_validator) and something like this. I ripped out the whitespace trimming to keep the code simple, the sqlite tests I was playing with don't have any whitespace ambiquity:
fn sql_result_validator(actual: &[Vec<String>], expected: &[String]) -> bool {
    let expected = expected
        .iter()
        .map(|s| s.split_ascii_whitespace().collect::<Vec<_>>())
        .collect::<Vec<_>>();
    if let Some(first_actual) = actual.first() {
        if expected.iter().all(|v| v.len() == 1) {
            // SQLite "value-wise" compatibility.
            // Flatten and re-chunk based on column width in `actual`.
            let expected = expected.into_iter().flatten().collect::<Vec<_>>();
            let expected = expected.chunks(first_actual.len()).collect::<Vec<_>>();
            return expected == actual;
        }
    }
    actual == expected
}

FYI, https://github.com/risinglightdb/sqllogictest-rs/pull/123 contains support for value sort. I forget whether it's finished though.


Server controllers: allow defining user accounts

This is needed to test SASL with servers.

Done.

Not for InspIRCd, actually.

Nor for Charybdis.

Now it is


Vertical lines at the end of a formula

Hi,
I use in Moodle 2.9 and 3.0 http://cdn.mathjax.org/mathjax/2.5-latest/MathJax.js
I get this (just the last months), vertical lines at the end of formulas etc.:

Duplicate of https://github.com/mathjax/MathJax/issues/1300. This was fixed in 2.6.0.


CAGR (Compound Annual Growth Rate)

Hello,
I'm looking at your lib and didn't find CAGR (Compound Annual Growth Rate).
Some Python implementations can be found here
qstrader https://github.com/mhallsmoore/qstrader/blob/c370f42497ad03eb77c56cea31eccc770ffee992/qstrader/statistics/performance.py#L29
quantstats https://github.com/ranaroussi/quantstats/blob/fa0a91a42400978bcc95f5f2fb2cf20e6f7af56c/quantstats/stats.py#L515
blankly-finance https://github.com/blankly-finance/blankly/blob/7fe1976b9db9132e798ba82b84b0522d18747dd7/blankly/metrics/portfolio.py#L27
https://github.com/blankly-finance/blankly/blob/7fe1976b9db9132e798ba82b84b0522d18747dd7/tests/metrics/test_portfolio_metrics.py#L32
empyrical https://quantopian.github.io/empyrical/_modules/empyrical/stats.html#cagr
Kind regards

Sure, I will add this.


[Feature Request] Pluggable Database Backend

It would be awesome to be able to use a different database backend instead of HBase (e.g. Cassandra). Is there any plans to implement such a thing, or at least any documentation on what would have to change to do so?

Hi aguerrieri,
No plans to support different backends just yet. Our backend code is more tightly coupled than we'd like. Once we do some abstraction/refactoring, coming up with a documentation and other backend support should be possible.
It'd require too much work to get started any time soon. Hope we'll get around to it some day.


SASS Lint - Space before { or not

We should standardise and create a Lint rule for h4 { ... or h4{ ...
My personal preference is the first one (with a space).

I think we should use the first option and use the same rule on JS and I think on PHP is already in that way so once we switch between languages we follow almost the same conventions.


Selection + paste link inside firefox

Hi,
There is a weird issue only with Firefox if I paste a link the cursor won't be out of the link (as it does with ex:Chrome).
I can replicate with the repo demo but not with the one online.

This is fixed in 9dda7cc8


How does toSelfObservable work?

Hello,
I have a question about how toSelfObservable works. I gather it should react to database changes on the given table, but what exactly does it return? Only the changed data? The whole table?
Thank you.

It returns an Observable of the type Result. The observable will be triggered on any entity operation could affect that result type. An example would be if you have query that lists some elements, then somewhere else in your code you modify/insert/delete elements. That would cause the observable to emit the Result and now you can re-run the query and get the changes. It's useful for saying updating a UI when you change your data from a background operation.

Yes, that's what I have gathered. Let me explain my situation. I have a list of events in the database. Every event has a particular status, and I am interested in only those of a certain status (three different statuses to be exact). Now I want to react when the table of events gets updated. Right now, it seems that the self observable I have returns only those elements that changed in the result Result (in the Observable). Is that the case?

It is linked to the original query you made. So you if have
data.select(Event.class).where(Event.STATUS.eq("something")).toSelfObservable().subscribe(
  new Action1<Result<Event>>() {
                public void call(Result<Event> persons) {
                    // result matching the query
                }
            });

The result in the subscription would be the same as if you called
data.select(Event.class).where(Event.STATUS.eq("something")).get()

The query I have is the following:
public Observable<Result<HistoryEvent>> getActiveHistoryEvents() {         return mDb.select(HistoryEvent.class)                 .where(HistoryEventEntity.STATUS.eq(HistoryEvent.STATUS_PENDING))                 .or(HistoryEventEntity.STATUS.eq(HistoryEvent.STATUS_UNRESOLVED))                 .or(HistoryEventEntity.STATUS.eq(HistoryEvent.STATUS_PENDING_POSTPONED))                 .get()                 .toSelfObservable();     }
The thing is, the Log I have in the getTimeline subscription keeps saying things like 1 or 2, even though when I go to another fragment in the viewpager (destroying the original one in the process), and back into the one with the list (so that getTimeline gets called again), it logs the supposedly correct number.

What is the value you are expecting? One thing to try is to make the query regularly after making a change and check the results, then also log the output of running the query from the Observable subscription, do you get differing results?

I am expecting to get all the active history events as far as the query goes, but it seems I only get one event, which is weird. Every pending event has a notification associated to it, and a pending event is supposed to change to unresolved as soon as the notification goes off creating a new pending event in the process. I want to update the list in the RecyclerView so that it correctly has both the unresolved event and the pending event (and the list of the upcoming events that are not saved in the db, generated by loadTimeline in the first code I posted).
When calling getActiveHistoryEvents right after changing the status and creating new pending event, it displays the correct amount when logging the size. But the self observable updating the list gets called multiple times (I guess on the status change, then on the new pending event), with sizes of 2 and then 1.

 I think that maybe why it's not matching what you're expecting.

The thing is, the changes happen at multiple places, how would I go about implementing it the runInTrasaction way?

If you're performing multiple update operations you can group those in a runInTransacton block, but even if not that is ok. You should receive all the notifications in order that you make them. Can you try again with the beta15 version? Made some changes there to the way the updates are published that may help on this issue.

I have gone around the issue by reacting on the table update by making another query for the whole table. But with beta15 it seems that even the original version should work, great job!
I have another issue that is connected to inserting stuff into the database and observing on this insert, I will open thread.

Closing this one since it seems the issue is covered


HTTP Requests with Precision parameter

I've just started working with your library, and I've found it quite helpful and easy to use so far. However, I got to a point where I needed to change the precision used for the timestamps, and I ended up modifying the http_request function to support this. It essentially just adds the precision parameter to the query, like so:

Is this something you'd want to include in your library, or is there some other way of doing this I missed? I can submit a pull request with my changes if you'd like.

Thanks for your liking influxdb-cpp and contribution.
Nice enhancement you've made, and please feel free to submit the PR.


Instructions switching the Units of Measurements

@siku2 This is a great improvement to this integration. My only question would be, could you add instructions on where to switch the unit of measurements for each sensor within the code? Thank you again!

Why do you want to adjust the units in the code?

I can't speak for NRutt2005, but it actually took me some time after installing the upgrade to work out why I wasn't able to find the new unit options.  I hadn't read the instructions carefully enough, and was expecting them to appear on the HACS card, not on the configuation page card.  Perhaps that could be stressed in the instructions? (or perhaps I should just read things more carefully ?)

This isn't something I considered documenting because it's not something that's particular to this integration. That's just how Home Assistant works as a whole.
Here's an idea though, I opened up the Repository Wiki so anyone can edit it.
I lack the "outsider perspective" to document all the details in a beginner-friendly way.

@siku2 @MichaelNMaggs I guess my problem is I'm not finding an "Instructions" section. I am also not seeing anything in the configuration page card for switching the units of measurements. That is the only reason I thought I would need to do the switching of units in the code. For an example of what I am wanting to do. Currently after loading the integration, the pressure is showing in PSI and I want to see this in inches Hg. All I see in the configure section of the card is the update interval. I've attached a photo of what I'm seeing. Maybe I am completely missing the mark on where to do the configuration changes or even to find the instructions. Sorry for the trouble.

i just happened to submit the update interval and it took me to the units of measurement configuration page. Sorry for the trouble. I still don't see the instructions part of the integration but I managed to click around enough to figure out how to change the configuration of unit of measurements settings. Thanks @siku2 and @MichaelNMaggs

I still don't see the instructions part of the integration but I managed to click around enough to figure out how to change the configuration of unit of measurements settings.

Again, please feel encouraged to help out by documenting your findings in the Wiki.

Yes, I see the problem. I agree that it would be better to have a direct visible link to the unit configurations rather than having them appear only after hitting submit on the update interval dialogue box. That does make the unit options somewhat invisible!

As far as I'm aware, this isn't possible, unfortunately.
I did try to make it easier to tell that there are multiple config "pages" in version 0.4.0 though.

OK. Could the text on the dialogue box perhaps isay something like "To access other options including rounding and units, click on the submit button" ?

It could, yes. The description can be changed here:
https://github.com/siku2/hass-weatherlink/blob/e1d8a7bf0aea90db43b2f37d6b4fbfefea3495bd/custom_components/weatherlink/translations/en.json#L24-L30

I've updated the wiki page for this integration to explain how to update the refresh interval and the units of measurement. Thank you @siku2 and @MichaelNMaggs

I've updated the wiki page for this integration to explain how to update the refresh interval and the units of measurement.

Awesome, thanks!

@siku2 thanks for your great work with this.


output sharing and how to run accelerate config

could you share some of the outputs? I mean meshes
i could not run accelerate config, as i have this error, do you know how to resolve it?
  File "/home/yulduz/.local/lib/python3.10/site-packages/torch/__init__.py", line 174, in _load_global_deps
    ctypes.CDLL(lib_path, mode=ctypes.RTLD_GLOBAL)
  File "/home/yulduz/anaconda3/envs/BakedAvatar/lib/python3.10/ctypes/__init__.py", line 374, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: libcufft.so.11: cannot open shared object file: No such file or directory

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/home/yulduz/anaconda3/envs/BakedAvatar/bin/accelerate", line 5, in <module>
    from accelerate.commands.accelerate_cli import main
  File "/home/yulduz/anaconda3/envs/BakedAvatar/lib/python3.10/site-packages/accelerate/__init__.py", line 16, in <module>
    from .accelerator import Accelerator
  File "/home/yulduz/anaconda3/envs/BakedAvatar/lib/python3.10/site-packages/accelerate/accelerator.py", line 32, in <module>
    import torch
  File "/home/yulduz/.local/lib/python3.10/site-packages/torch/__init__.py", line 234, in <module>
    _load_global_deps()
  File "/home/yulduz/.local/lib/python3.10/site-packages/torch/__init__.py", line 196, in _load_global_deps
    ctypes.CDLL(lib_path, mode=ctypes.RTLD_GLOBAL)
  File "/home/yulduz/anaconda3/envs/BakedAvatar/lib/python3.10/ctypes/__init__.py", line 374, in __init__
    self._handle = _dlopen(self._name, mode)
OSError: libcufft.so.11: cannot open shared object file: No such file or directory

Hi,
the error message you showed seems to have something to do with your Pytorch installation. Could you try it on another clean installation?
Here is an example of the multi-layer meshes outputted after stage 2 (without being fine-tuned). It contains some 3D obj files so you can take a quick visualization of the meshes. this pkl file contains all the fine-tuned mesh data after stage 3 and you can use the code/scripts/unpack_pkl.py script to convert it for the real-time web demo.


[Concurrency] Hide async_Main from other object files

Multiple executable targets with asyc entrypoints within a single package were not able to be tested due to the following linkage failure.
The sync main entrypoint is usually referenced by crt, so it should be visible from the outside of the object file and linked image unit. Therefore, the sync main entrypoints are renamed using -entry-point-function-name by SwiftPM to avoid conflicting with other executable targets.
On the other hand, the async async_Main entrypoint is only referenced from the sync main, so it doesn't need to be visible from other object files. Therefore, we can just hide it from other object files to avoid static link-time conflicts.
The async_Main symbol was defined as hidden SIL visibility, but hidden is still visible from other object files (not visible from other image unit), so this PR makes it private, which corresponds to internal LLVM visibility.
Resolves rdar://114231968
$ ../swift-DEVELOPMENT-SNAPSHOT-2023-10-09-a-ubuntu20.04/usr/bin/swift test
Building for debugging...
error: link command failed with exit code 1 (use -v to see invocation)
/usr/bin/ld.gold: error: /tmp/tmp.o984OA4fPZ/spm-async-main-repro/.build/x86_64-unknown-linux-gnu/debug/b.build/B.swift.o: multiple definition of 'async_Main'
/usr/bin/ld.gold: /tmp/tmp.o984OA4fPZ/spm-async-main-repro/.build/x86_64-unknown-linux-gnu/debug/a.build/A.swift.o: previous definition here
/usr/bin/ld.gold: error: /tmp/tmp.o984OA4fPZ/spm-async-main-repro/.build/x86_64-unknown-linux-gnu/debug/b.build/B.swift.o: multiple definition of 'async_MainTu'
/usr/bin/ld.gold: /tmp/tmp.o984OA4fPZ/spm-async-main-repro/.build/x86_64-unknown-linux-gnu/debug/a.build/A.swift.o: previous definition here
clang-15: error: linker command failed with exit code 1 (use -v to see invocation)
error: fatalError
[39/40] Linking spm-async-main-reproPackageTests.xctest
error: fatalError

let package = Package(
    name: "spm-async-main-repro",
    dependencies: [ ],
    targets: [
        .executableTarget(name: "a", dependencies: []),
        .executableTarget(name: "b", dependencies: []),

        .testTarget(name: "reproTests", dependencies: ["a", "b"]),
    ]
)

@swift-ci Please build toolchain

Please test with following pull request:
https://github.com/apple/swift-package-manager/pull/6986
@swift-ci Please smoke test

Thanks @kateinoigakukun 🥳

We're seeing test failures here. I believe the symbol should be both private linkage and have hidden visibility.
https://ci.swift.org/job/swift-PR-Linux/11278/
/usr/bin/ld.gold: error: /tmp/Miscellaneous_TestableAsyncExe.itEwsM/Miscellaneous_TestableAsyncExe/.build/x86_64-unknown-linux-gnu/debug/TestableAsyncExe2.build/main.swift.o: multiple definition of 'async_MainTu'
/usr/bin/ld.gold: /tmp/Miscellaneous_TestableAsyncExe.itEwsM/Miscellaneous_TestableAsyncExe/.build/x86_64-unknown-linux-gnu/debug/TestableAsyncExe1.build/main.swift.o: previous definition here
/usr/bin/ld.gold: error: /tmp/Miscellaneous_TestableAsyncExe.itEwsM/Miscellaneous_TestableAsyncExe/.build/x86_64-unknown-linux-gnu/debug/TestableAsyncExe2.build/main.swift.o: multiple definition of 'async_Main'
/usr/bin/ld.gold: /tmp/Miscellaneous_TestableAsyncExe.itEwsM/Miscellaneous_TestableAsyncExe/.build/x86_64-unknown-linux-gnu/debug/TestableAsyncExe1.build/main.swift.o: previous definition here
/usr/bin/ld.gold: error: /tmp/Miscellaneous_TestableAsyncExe.itEwsM/Miscellaneous_TestableAsyncExe/.build/x86_64-unknown-linux-gnu/debug/TestableAsyncExe3.build/NonMain.swift.o: multiple definition of 'async_Main'
/usr/bin/ld.gold: /tmp/Miscellaneous_TestableAsyncExe.itEwsM/Miscellaneous_TestableAsyncExe/.build/x86_64-unknown-linux-gnu/debug/TestableAsyncExe1.build/main.swift.o: previous definition here
/usr/bin/ld.gold: error: /tmp/Miscellaneous_TestableAsyncExe.itEwsM/Miscellaneous_TestableAsyncExe/.build/x86_64-unknown-linux-gnu/debug/TestableAsyncExe3.build/NonMain.swift.o: multiple definition of 'async_MainTu'
/usr/bin/ld.gold: /tmp/Miscellaneous_TestableAsyncExe.itEwsM/Miscellaneous_TestableAsyncExe/.build/x86_64-unknown-linux-gnu/debug/TestableAsyncExe1.build/main.swift.o: previous definition here
/usr/bin/ld.gold: error: /tmp/Miscellaneous_TestableAsyncExe.itEwsM/Miscellaneous_TestableAsyncExe/.build/x86_64-unknown-linux-gnu/debug/TestableAsyncExe4.build/NonMain.swift.o: multiple definition of 'async_Main'
/usr/bin/ld.gold: /tmp/Miscellaneous_TestableAsyncExe.itEwsM/Miscellaneous_TestableAsyncExe/.build/x86_64-unknown-linux-gnu/debug/TestableAsyncExe1.build/main.swift.o: previous definition here
/usr/bin/ld.gold: error: /tmp/Miscellaneous_TestableAsyncExe.itEwsM/Miscellaneous_TestableAsyncExe/.build/x86_64-unknown-linux-gnu/debug/TestableAsyncExe4.build/NonMain.swift.o: multiple definition of 'async_MainTu'
/usr/bin/ld.gold: /tmp/Miscellaneous_TestableAsyncExe.itEwsM/Miscellaneous_TestableAsyncExe/.build/x86_64-unknown-linux-gnu/debug/TestableAsyncExe1.build/main.swift.o: previous definition here
clang-15: error: linker command failed with exit code 1 (use -v to see invocation)
<unknown>:0: error: link command failed with exit code 1 (use -v to see invocation)

Actually, scratch that. The above link failure is on the 5.10 branch in a SwiftPM test.
I think this needs cherry-picking into the 5.10 branch. SwiftPM is still automerging changes from main to release/5.10, but Swift is not, so the tests copied into SwiftPM in https://github.com/apple/swift-package-manager/commit/f258cd551d6508acb2ef89588485659d4cf76729 are failing.


Can't install

I suspect this is a new update issue -- I just went to install this and it's giving me a "Plugin ID mismatch" error on the Obsidian installer. Help?

Duplicated: #31
Vertical Tabs does not support old versions of Obsidian. Installation is, therefore, disabled to prevent inconsistent performance. Please download the latest installer of Obsidian to update.


feat: implement support for model property default values

test: model default value
feat: support default value for model property
build: generate files

Looks good to me, thank you!


Highlight currently focused tile to help with visablity

I think having a colored border around the currently focus window, would be better to quickly show which window is in focus and follow focus as it changes.
Maybe when the user is switching focus a border shows up and follows the movement of focus and then after a few seconds it fades away. If the user then wants to quickly tell which window has focus they can hold down ALT (or some shortcut) and have some time threshold that once reached it will bring back the border highlight for the current focused window until ALT is let go.

I just researched this a bit and this would be very hacky. Basically we would have to create a new window ontop of each window and move the border along with the window. I am not sure whether I like this. We would have to play round with this a bit, to see how this impacts the usability of the existing windows.
Would you like to tackle this? I probably won't be working on this issue for a bit, because this is very low priority for me.

Sure I can try to take a swing at this.

Never got around to working on this, I think the codebase was so overwhelming I wasn't even really sure how I would have gone about implementing it especially since I am still a Rust newbie. I think with the current_window component this feature isn't really needed anymore. I will go ahead and close for the time being.

@TimUntersberger oops don't think that was supposed to happen. Sorry about that!

I think this issue should be re-opened. Many applications barely have any visual effect that indicates they are focused in Windows 10. It's very hard to see which window has the focus, especially when you switch to another workspace, and don't remember which window is supposed to be active.
It's really something Windows itself should do, better, as I occassionally have had problems during regular Windows usage as well. But the problem hasn't been too bad, since I usually remember the application I'm working on, and you also switch to other applications explicitely, which focuses them. But that does not seems to be something Microsoft is interested in fixing, because from the screenshots I have seen, Windows 11 does not handle this very differently. In previous Windows version, this was rarely a problem though.
After writing this, I looked deeper into the Windows options, you can enable the accent color for title bars, and it makes things much better for some applications. But Chrome for example becomes very ugly, and additionally it adds a close color to the inactive window as well, so the difference is not that huge. Other applications don't react to the change at all.
I suggest that rather than displaying a window on top of the real window, you display it beneath it. That way it doesn't mess with floating windows on top.  This would of course need some spacing between the windows, but that's already supported.
Another option is a layered top level window https://docs.microsoft.com/en-us/previous-versions/ms997507(v=msdn.10)?redirectedfrom=MSDN, and making sure that it is fully transparent if no window in the workspace has focus. That way only one window is needed, and the appbar could also be included in the same window. But that could potentially mess with the performance and some applications.


🐛 timeout

Relates to #119

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


atomic updates select fields that are not used

right now atomic updates select all the fields of a resource even though they are not used
e.g.
update resource
set attribute1 = _new_attribute1
from (
  select calc_something as _new_attribute1,
              attribute1,
              attribute2,
              ...
    from resource)
where something
returning attribute1, attribute2, ...

This has been completed. We now select only the primary key and the changing fields


Couldn't paste in any directory

Hey, @duke7553! Sorry for another issue but when I try to copy a file it works by storing the location variable in the clipboard but when I paste it then I couldn't because there is no space to right click other than the files and directories icons. I could still paste it somewhere else in the OG Explorer. You're doing great but just as a fellow programmer it's a piece of advice.

Does clicking paste in the "three dots" menu work?

@duke7553 Nope, It's not working. I still could copy the files but not paste it because the paste button is greyed out.

@duke7553 The new version has the fix. Thanks!


Expose closing tx in waiting_close_channels

Change Description
This PR exposes the raw closing tx of the waiting_close_channels in the PendingChannels response.
There are cases when a local force close transaction of a static remote key channel drops out of the mempool due to insufficient fees. Currently, the only way to get hold of this transaction to rebroadcast it is to restart LND. However, restarting LND is infeasible for large nodes that want to maintain their uptime. Even if restarting LND is an option, if the tx has insufficient fee, the only way to capture it currently is by scavenging the logs. By adding the raw tx to waiting_close_channels, unconfirmed closes can be pushed through a tx accelerator for example to ensure timely confirmation.
Steps to Test
A pending cooperate close and local force close in the waiting close state includes the raw tx hex of the closing transaction.
Pull Request Checklist
Testing

[ ] Your PR passes all CI checks.
[ ] Tests covering the positive and negative (error paths) are included.
[ ] Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

[x] The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
[x] Commits follow the Ideal Git Commit Structure.
[x] Any new logging statements use an appropriate subsystem and logging level.
[x] Any new lncli commands have appropriate tags in the comments for the rpc in the proto file.
[x]  There is a change description in the release notes, or [skip ci] in the commit message for small changes.

📝 Please see our  Contribution Guidelines for further guidance.

In addition, we should update our itest to validate ClosingTxHex is created as expected - maybe we could just add a few lines in one of our tests.

Thanks for the pointer to the itest, that's very helpful.
I added some lines of code in the first itest to check whether the tx is valid and matches the closing_txid. Let me know what you think.
I made the IncludeTx boolean true for all testcases using the PendingChannels rpc. I didn't think it could hurt. The alternative is to let every test pass a boolean or a request to that PendingChannels call instead. One has code changes in quite a few places, and the other 'affects' all the tests in those places. Let me know which one you prefer.

@coderabbitai review

I've also added the flag to lncli, which was a piece I hadn't included before.

Addressed the rabbit's actionable comment.

Addressed @guggero's comments and rebased.


Westlicht Performer sd card

Hi! Just received yesterday my performer, naturally without sd card. These are my firsts steps with this module, so thanks in advice for your help…

which type of micro sd may I use?
how can I format my brand new micro sd? Fat32? Ntfs?
may I format my micro sd directly from my Performer? Can you write me the entire procedure?
Do I have to download and put in my sd card some file system or Performer will do it for me if I’ll format my card internally in him?

Thank you so much for your help: I think performer will became my best sequencer in few hours 😊

16gb sd micro card will suffice. Format instructions can be found in the manual. Happy reading!

I tried yesterday to look in the manual but I couldn't find the instructions for formatting the card.

the question is: may I use a new sd card just to save my projects without downloading last update.dat file?

Is this attached the right procedure to format an sd card? It is named as FIRMWARE UPDATE


Pipeline support

I know that this has been written up before , and the current consensus is that 1) it has a limitation that it doesn't allow functions with multiple arguments, and that it is a niche functionality only useful for DSLs.. I think that 1) it doesn't have to have that limitation, and you can look at F#'s implementation to show this, and 2 it can be very generic and useful, as seen in both F# and more so in powershell.
here is a link to how it is done in F# http://lorgonblog.wordpress.com/2008/03/30/pipelining-in-f/
Here is some coffee of mine doing a scenario. first how i have to call it now, then how i'd like to be able to call it, and third how i can do it with a helper function, then following up with how it can be done in kaffiene currently. The example is rather contrived but it should be sufficient to communicate
where = (list,func) -> item for item in list when (func.call _ :item)
select = (list, prefix,postfix) -> "#{prefix}#{item}#{postfix}" for item in list
getnums = (x) -> [1..x]

is there any easier way i can write the following below
results = select( (where (getnums 10) ,-> @_ > 5) , "pre","post" )

alert res for res in results

what it really would like to do is be able, whether using | or say |> for a pipe do
getnum | where -> @_ > 5 | select "pre","post"

basically the pipe takes the output of the previous command and puts it as teh first argument, and then takes any other arguments after that (so 1st argument becomes 2nd, and second becomes third..
with my own pipe i can do something like
pipe getnum .to where, -> @_ > 5 .to select , "pre","post"
kaffiene though not complete lets me do this with
getnums = { [1,2,3,4,5,6,7,8,9,10] }select = (list,prefix,postfix) {
  res = []
  for x of list {
   res.push("#{prefix}#{x}#{postfix}")
    }
  return res
  }

and call it like this in kaffiene
getnums | select "pre","post"

generates the following javascript
var getnums, select; getnums = function() { return [1,2,3,4,5,6,7,8,9,10] }select = function(list,prefix,postfix) {
  var _a, x, res; res = []
  for(_a = 0; _a < list.length; _a++) { x = list[_a];
   res.push("" + (prefix) + (x) + "" + (postfix) + "")
    }
  return res
  }
__.select.call(this, getnums, "pre","post")

and
getnums | select "pre","post" | select "yo","dude"

__.select.call(this, __.select.call(this, getnums, "pre","post"), "yo","dude")

+1 for F# style pipelining. This is one of my favorite idioms from F#.

Folks, this isn't a full substitute for F# |>, but what would you think using:
pipeline = (v, fs...) -> v = f.call(v) for f in fs; v

As in:
r = pipeline 2,
    -> @*2
    -> @+1

i have played around with doing that sort of thing inline before, but
really want it with the language.. here is an example.. i've moved on from
asking though. what i'm playing around with now is producing a powershell
style syntax and pipelining language that uses coffeescript for the
expressions.
*where = (list,func) -> item for item in list when (func.call _ :item)
select = (list, prefix,postfix) -> "#{prefix}#{item}#{postfix}" for item in
list
getnums = (dummy,x) -> [1..x]
pipe = (listoflists...) ->
res = null
for list in listoflists
func = list[0]
args = list[1..list.length]
res = func.apply(this,[res].concat(args))
res
results = pipe [getnums, 10] , [where, -> @_ > 5 ] ,[select , "pre","post" ]
alert result for result in results*
*
*
On Mon, Nov 21, 2011 at 3:27 PM, Alessandro Vernet <
<EMAIL_ADDRESS>
wrote:

Folks, this isn't a full substitute for F# |>, but what would you think
using:
pipeline = (v, fs...) -> v = f.call(v) for f in fs; v
As in:
r = pipeline 2,
-> @*2
-> @+1

Reply to this email directly or view it on GitHub:
https://github.com/jashkenas/coffee-script/issues/1339#issuecomment-2823118

@klumsy, or, using the above pipeline:
pipeline = (v, fs...) -> v = f.call(v) for f in fs; v
filter = (p) -> -> vs = @; v for v in vs when p.call v
addPrePost = (pre, post) -> -> vs = @; "#{pre}#{v}#{post}" for v in vs

r = pipeline [1..10],
    filter -> @ > 5
    addPrePost "pre", "post"

Run it
I tend to prefer this pipeline construct as it also works for pipelines that operate on single "values" instead of just arrays/lists/sequences. For the later, using "just" Underscore's chain might even do the trick.

you opened my mind to a whole nother world of possibilies with your -> ->
usage!!
taking that to another level (where it returns an object with multiple funs
for begin , process and end, i can actually implement a streaming pipeline.
Thanks.
On Mon, Nov 21, 2011 at 4:12 PM, Alessandro Vernet <
<EMAIL_ADDRESS>
wrote:

@klumsy, or, using the above pipeline:
pipeline = (v, fs...) -> v = f.call(v) for f in fs; v
filter = (p) -> -> vs = @; v for v in vs when p.call v
addPrePost = (pre, post) -> -> vs = @; "#{pre}#{v}#{post}" for v in vs
r = pipeline [1..10],
filter -> @ > 5
addPrePost "pre", "post"
Run it
I tend to prefer this pipeline construct as it also works for pipelines
that operate on single "values" instead of just arrays/lists/sequences. For
the later, using "just" Underscore's chain might even do the
trick.

Reply to this email directly or view it on GitHub:
https://github.com/jashkenas/coffee-script/issues/1339#issuecomment-2823552

A recent proposal to add method cascades to Dart would make it possible to write Dart code as follows:
document.query('#myTable').{
    queryAll('.firstColumn').{
        style.{
            background = 'red',
            border = '2px solid black'
        },
        text = 'first column'
    },
    queryAll('.lastColumn').{
        style.background = 'blue',
        text = 'last column'
    }
};

In CoffeeScript, we can declare a cascade function, which is very similar to the above pipeline:
cascade = (v, fs...) -> f.call(v) for f in fs; v

This allows us to write the above Dart code, in CoffeeScript, as:
cascade document,
    -> cascade (@query '#myTable'),
        -> cascade (@queryAll '.firstColumn'),
            -> cascade @style,
                -> @background = 'red'
                -> @border = '2px solid black'
            -> @text = 'first column'
        -> cascade (@queryAll '.firstColumn'),
            -> @style.background = 'blue'
            -> text = 'last column'

Try it
(Posting this as a follow-up here, as the ressemblance between cascades and pipelines is striking.)

@vendethiel so is this open?!


Rework init task

Comment code in init task thouroughly as it is likely to be the entrypoint for others. Where possible, extract component-related functions.

Postponing this task until after the hand-in.


Add xmlns attribute to generated SVGs

Description
All generated icons now have the xmlns="http://www.w3.org/2000/svg"  attribute + value on them.
Why is this change required?
tl;dr: since SVG is an XML dialect you should specify its namespace so all rendering engine will properly display the SVG. More here.

[x] I've read the contributing guidelines and the Code of Conduct

@ericcornelissen Thanks for your contribution!


Discuss how many versions of Kernel flavors to keep

This was originally triggered by https://github.com/NixOS/nixpkgs/pull/343751#issuecomment-2368674323
linux_5_4_hardened was broken and the question is basically whether we even need numerous Linux hardened versions. There aren't many users anyways (if any given that nobody complained when the update script was broken and there weren't updates for months).
The idea is to drop all except latest and last longterm kernel.
Upon writing this, I'm wondering if we want to do the same for other variants such as rt kernels.
cc @alyssais @emilazy @fabianhjr @k900

Add a :+1: reaction to issues you find important.

I'm in agreement for removal. Kernel flavours should really only be provided for the latest and/or lts branches. Anything beyond that just doesnt seem practical to support.
Perhaps we could offer better documented tooling that provides users with the ability to bring forth a custom kernel variant fairly easily. I don't really think this is an extremely popular option though, given like you said, nobody noticed a derivation that was broken for months.

no need to support the world indeed. If there is demand, it can be done in NURR, nix-community and so on.

for other variants such as rt kernels

My understanding is that RT kernels probably going away since the RT patches were mainlined into 6.12.
https://www.phoronix.com/review/linux-612-features

due to the automation I think it is better to keep all lts versions but only build on hydra/cache and actively expect to maintain latest stable + latest lts on all kernel variants.

@Frontear

the latest and/or lts branches.

That is currently the case, the proposal of @Ma27 is to drop all but the latest LTS.

Btw, just on procedure side should probably get @NixOS/release-engineers involved (specially since the freeze is about 10 days away)

Ok, from looking at current nixpkgs recurseIntoAttrs is used to evaluate all of the packages of a kernel. (same mechanism as python3[minor]Packages)
Currently RT kernels aren't recursed into and I would propose to do the same for all the variants except latest stable and latest lts.
Will open a PR as draft with that specific change.

I think maybe having a few LTS releases is helpful for getting a rough idea of when something broke, but I am not opposed to removing them in general.

In theory it would be sufficient to just remove the stuff from linux-kernels, but it's kinda ugly to have an update-script generating commits for packages that don't exist.

Getting back to this I think that

I think maybe having a few LTS releases is helpful for getting a rough idea of when something broke

is not sufficient for the hardened (i.e. non-mainline) flavour that nobody seems to be really interested to maintain, let alone non-latest/LTS versions.
The python3 thing is somewhat a different situation because requiring an older interpreter is a more common use-cases and RT kernels were just older than our "no more additional flavours"-rule, but there's a clear path of those disappearing.
I haven't read about anybody particularly caring for non-LTS/non-latest hardened kernel. So I think I agree with @emilazy on just killing them. And it might be good to revisit the updater script anyways, I've seen it add commits for kernel minors we removed from nixpkgs already.
Does anybody oppose this proposal? Otherwise I'll file a PR for that soonish.

I've seen it add commits for kernel minors we removed from nixpkgs already.

It uses the mainline json so if it isn't removed there it will keep adding them back

I am not sure if we have a programmatic way of telling which kernel is the latest LTS. It would be easy to adapt the script to only maintain the latest LTS kernel that has patches and the latest stable kernel that has patches if we have a reliable source of that data it can read from.
Sorry for the neglect the hardened kernels and profile have seen. I am still interested in making them a good option at some point, but other things have taken priority, and I don’t want them to cause a burden on the kernel maintainers. I am okay with whatever kernel maintainers want to reduce the hassle here. If there’s a concrete task with the update script that needs doing I can look into doing it. I wouldn’t object strongly to just dropping the hardened kernels entirely either if they are causing too many problems, although it would be nice in that case if the door was open to them returning at a later date if I or someone else can actually properly take responsibility for them.

I am not sure if we have a programmatic way of telling which kernel is the latest LTS. It would be easy to adapt the script to only maintain the latest LTS kernel that has patches and the latest stable kernel that has patches if we have a reliable source of that data it can read from.

To clarify: Although the linux-hardened upstream is pretty good at releasing patches quickly, they’re not perfect at it. So if we only carried the latest stable and latest LTS we might end up with hardened kernels disappearing. What would make the most sense is “latest stable with hardened patches available” and “latest LTS with hardened patches available”. For instance, if mainline.json contained a flag representing which versions are LTS, it would be easy to do this.

It uses the mainline json so if it isn't removed there it will keep adding them back

Sure, but for the "only LTS & latest"-approach we'll just pick two from kernels-org.json which should fix the underlying issue of obsolete entries in there.

I am not sure if we have a programmatic way of telling which kernel is the latest LTS

I don't think there is, at least on eval time. But I think it's perfectly fine to either specify the latest LTS or to just use the default pkgs.linux (which is a recent LTS).


Old versions of itunes not detected.

A windows pc with itunes 12.5 installed does not have it detected properly (sometimes detecting, usually not), it also shows skype and spotify as installed though that is only because they were recently uninstalled.

Testing with a newer version installed (12.10) detects it properly.

I mean this is just a POC maybe we add a disclaimer like: "app not detected/app detected incorrectly?" and just list possible exceptions and reasons why it may not work for them

The external URL scheme might be different for 12.5 and 12.10


I'd like to help out!

Hi Bastiaan:
Sorry I couldn't find any other way to contact you. My company is looking at making a game accessory and would like to develop a launch title that works on the htc vive and also on android/iOS mobile VR headsets. I'd really like to develop the game using Godot since I'm a big advocate of open source software.
I am hoping there are some tasks that I can assist in and we can get this working. I unfortunately have little experience in any game engines, only a prototyped game on the vive using the worldviz vizard 5 game engine, which is not portable to mobile (nor open source). Though I do have extensive c programming experience (embedded) and a fair bit of c++ too.  I thought the easiest path would be to get a godot game working with the vive then try to move it over to the mobile targets.  I have a vive for development. If you can just give me some direction while I'm doing my research into openVR what godot needs I hope it will be beneficial for everyone. I'm usually on IRC from around 4-12UTC. In the meantime I'll be looking through your code in this repo and your OpenVR branch of the godot codebase.
Thanks,
_Spencer

ha, I just saw the roadmap in the readme, would you mind if I added each one as a separate issue here and we can maybe discuss them a bit? Or would they belong better in the upstream project tracker?

Hey Spencer,
I'm doing my openvr project for fun, I'd really like to make the jump to
PSVR one day. The Godot team themselves have VR on their longer term plans,
whether they will adopt what I've done so far or build their own version,
time will tell. I originally started the project with the idea to embed
some measure of cross platform support but gave up on that fairly quickly
due to the differences in platforms. I figures it would be far easier to
embed the specifics for each platform inside a scene and just load up the
correct one depending on what you deploy your game on. It also means not
having to deal with design choices for which you first need to gain some
experience. You'll see that in my prototype project that is how it is set
up, the main scene has what you see, and then there is an openvr scene that
contains all the HMD and controllor logic. That could be swapped out with a
scene for say mobile.
Last night was a pretty large milestone for me as the correct rendering of
the two eyes was the bit that really stopped us from going forward.
OpenVR as a platform allows you to deploy to Windows and potentially Linux
and Mac OS X in the near future and target Vive/Oculus and OSVR headsets.
Mobile is a different beast and in many ways simpler (and in some ways
harder). Just before the Godot 3 branch got merged in we had added all the
basic changes to make a cardboard type iOS VR solution and we were one
change short of having the same on Android (I don't have a capable android
phone).
The changes to the device orientation info (accelerometer, gyro and
magnetometer) have now been updated to Godot 3 and accepted into the master
branch but there are still issues preventing building an actual iOS build
on Godot 3 and I suspect that will stay like that for a little while longer
as the desktop versions have priority.
There is also another PR of mine that the openvr project also uses (check
out the stereo_camera branch) that adds the needed changes to Godot to
render the eyes correctly, both for openvr and mobile (and any other stereo
scopic solution). This has not yet been updated to Godot 3 but I plan to do
so soon.
With those two changes combined and the ability to deploy Godot 3 to iOS
we're a lot closer to building a VR mobile game.
For Android there is one more change needed (implementing the
TYPE_GYROSCOPE events for device orientation) and the same would apply.
So yeah, the biggest hurdle at this moment is actually Godot 3 not
compiling for iOS and Android just yet:)
On 3 February 2017 at 11:44, ssj71<EMAIL_ADDRESS>wrote:

ha, I just saw the roadmap in the readme, would you mind if I added each
one as a separate issue here and we can maybe discuss them a bit? Or would
they belong better in the upstream project tracker?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/BastiaanOlij/TestOpenVR/issues/1#issuecomment-277132118,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB2vaXKjkm-JvBSjp1aiJmoATtwteCTDks5rYnhygaJpZM4L10db
.

--
Kindest regards,
Bastiaan Olij

So yeah, the biggest hurdle at this moment is actually Godot 3 not compiling for iOS and Android just yet:)
that is a rather large hurdle right now. That and Godot 3 won't have a stable api for some months still. Its so close to being ready (I could deal with an alpha) but I doubt I'll convince anyone in management to wait a few months for Godot 3 to be even to alpha. :( They want an android or iOS VR game prototyped in the next month. I'll talk to them and see what I can work out. Probably the answer from them will be to just use unity. Worst comes to worst I'll do our prototype in unity and see if I can port to godot3 before release.

It sounds like the VR part is actually already fairly workable, very nice work. Its too bad the timing of the major changes, but I understand that sort of stuff needs to be done. If I am able to get an android phone that I can test with (which I should), I'll see if I can add the gyroscope sensor.
Would it be a waste of time or take extremely long to backport the changes for VR to godot 2.1 and perhaps try to create the game that way? If that's feasible I might be able to use godot after all.
Thank you so much for your feedback!

Hey @ssj71,
It's actually the accelerometer/gyro/magnetometer changes for iOS that are the only things that ended up in Godot 3 and not in Godot 2 so if you want to focus on Android adding gravity vector support would be the thing you need to do. Android already does accelerometer, gyro, magnetometer but didn't extract the gravity vector which is what you really need for VR (you can do it yourself with alot of math but why do it if the OS already supplies it for you).
With those vectors you can determine orientation of the device so that the movement of the device steers the camera. Actually for VR both android and iOS have support for giving you a final transform for this and it may be interesting to add that to both platforms as well.
I've got some code however that converts the 9DOF sensor data into orientation though its a bit simplistic, it does work.
The other thing you need is the stereo_camera project. My openVR project uses this as well.  Both of those are still based on an older Godot 2.2 version but in theory you can build a patch to apply to the latest Godot 2.1 branch and it should work just fine.

Btw, you can find some more about the changes needed to Android here:
https://github.com/godotengine/godot/issues/7503

I'm finally working on this a little more.
Where do I copy the openVR lib and bin directories to? I assume somewhere in the godot source tree?

Cool thanks! That readme was written in a hurry :)
This thursday I finally got all the controller logic working properly so this is enough now to create a steamvr game that works with the vive.
I'm also playing around with Trinus VR and VRidge, both offer SteamVR support and turn your cardboard/gearvr headset into an HMD for your PC. Not as good as hooking up a vive or rift but still. Trinus even has a PSVR version that allows you to hook up your PSVR to your PC though it hasn't worked on my laptop yet.
Obviously non of that will help you for a pure mobile VR app. I really need to get back into compiling the latest Godot 3 for iOS and see if all the work I did a few weeks ago paid off. I still have to write a lens distortion shader but shouldn't be too much more work to get it all running.

@ssj71 If you decide to help, only contribute to Bastiann's repo, not the main Godot one.
Lead developer is unfortunately very arrogant when it comes to feedback.  Bastiaan, on the other hand is actually pretty intolerant w/ mistakes and is pretty lenient.  Just a warning.


fix: resolve react native dir in monorepo in android build

📜 Description

I updated resolveReactNativeDirectory in  android/react-native-helpers.gradle to handle custom directory structures in a more generic way.
As in the previous version, I followed how software-mansion resolved this problem.
💡 Motivation and Context
I am working on a monorepo that's follow this structure
apps
├── react-native-app
│   ├── node_modules
│   │   └── react-native-keyboard-controller
packages
node_modules
├── react-native
package.json

The previous monorepo workaround was limited to two hardcoded paths.
My monorepo is build with Turborepo. Referring to their docs:

Referencing node_modules in your code
The specific locations for node_modules within the Workspace are not a part of the public API of package managers. This means that referencing node_modules directly (like node ./node_modules/a-package/dist/index.js) can be brittle, since the location of the dependency on disk can change with other dependency changes around the Workspace.
Instead, rely on conventions of the Node.js ecosystem for accessing dependency modules whenever possible.

We can't be sure that react-native and react-native-keyboard-controller folders are in the same node_modules folder.
📢 Changelog
fixed android build in monorepo
Android
resolve node modules react native directory using node resolver instead of hardcoded paths
🤔 How Has This Been Tested?

I tested android build in a monorepo created with turbo repo, in standalone react native app repo and in the example app.
📸 Screenshots (if appropriate):

📝 Checklist

[ ] CI successfully passed
[ ] I added new mocks and corresponding unit-tests if library API was changed

Thank you ❤ Changes look good to me!
I triggered CI - let's see whether it pass or not 👀


Wrong target on horizontal move

Hi,
i try to join group example with default one. So i get sortable groups with a list of items within.
The item list can also be sort vertically and horizontally.
As container i use jQuery-UI accordion (header = group, content = item list)
The vertical sort works fine, but i have a problem with horizontal sort. The target-item to place an item as child is always the last item in group.
Example:
A
-- A1
-- A2
-- A3
B
-- B1
-- B2
If i want to set A2 as child of A1 the target node is A3.
Used packages:
AngularJS v1.2.28
angular-ui-tree v2.1.5
jQuery UI v1.10.2 (customized build)
I also tried to disable accordion, but with no effect.
Hope you can help with this problem.
Additional info:
The dragInfo-object in line 1034 has the correct number of siblings, but all siblings are references to last node.
Regards
Thomas

I could implement "angular ui tree" sort with groups and nested lists in a separate environment and it works.
Now I try to transfer this into my project, but there is the same problem - all siblings of dragInfo-object are the same (reference to last sibling of a section).
Any idea what can affect horizontal movement. Vertical movement works great.
Regards
Thomas

I set the nodes of a tree via ng-init. All the nodes got a hashKey = 0.
I have solved the problem by using angular.copy().
Regards
Thomas


WIP: Gauntlet MIP-B15 and MIP-M25

Moonbeam proposal still fails simulation, will be watching for the governance migration to complete on chain to try again

MIP-M25 Output:
No files changed, compilation skipped
Script ran successfully.

== Logs ==
  deployerAddress:  0x9A187663E454e99CAFd40a2712606CC306e301b2

Proposal Description:

# MIP-M25: Gauntlet's Moonbeam Recommendations

A proposal to adjust 7 total risk parameters:

| Parameter                  | Current Value | Recommended Value |
| -------------------------- | ------------- | ----------------- |
| xcUSDC Collateral Factor   | 10%           | 15%               |
| WGLMR Collateral Factor    | 58%           | 57%               |
| WGLMR Borrow Cap           | 22,500,000    | 10,000,000        |
| WBTC.wh Borrow Cap         | 50            | 5                 |
| WETH.wh WBTC.wh Borrow Cap | 500           | 100               |
| xcUSDT Reserve Factor      | 20%           | 25%               |
| xcUSDC Reserve Factor      | 20%           | 25%               |

A proposal to make a IR curve adjustments for USDC.wh:

| USDC.wh IR Parameters | Current    | Recommended |
| --------------------- | ---------- | ----------- |
| BASE                  | 0          | 0           |
| Kink                  | 0.8        | 0.8         |
| Multiplier            | **0.0845** | **0.0875**  |
| Jump Multiplier       | **7.2**    | **7.4**     |

A proposal to make an IR curve adjustments for xcUSDC:

| xcUSDC IR Parameters | Current    | Recommended |
| -------------------- | ---------- | ----------- |
| BASE                 | 0          | 0           |
| Kink                 | 0.8        | 0.8         |
| Multiplier           | **0.0814** | **0.0875**  |
| Jump Multiplier      | **7.0**    | **7.4**     |

A proposal to make a IR curve adjustments for xcUSDT:

| xcUSDT IR Parameters | Current    | Recommended |
| -------------------- | ---------- | ----------- |
| BASE                 | 0          | 0           |
| Kink                 | 0.8        | 0.8         |
| Multiplier           | **0.0814** | **0.0875**  |
| Jump Multiplier      | **7.0**    | **7.4**     |

A proposal to make an IR curve adjustments for FRAX:

| FRAX IR Parameters | Current  | Recommended |
| ------------------ | -------- | ----------- |
| BASE               | 0        | 0           |
| Kink               | 0.8      | 0.8         |
| Multiplier         | **0.01** | **0.0563**  |
| Jump Multiplier    | **0.01** | **4**       |

Our recommendation post is located in the forums, please refer to this [link](https://forum.moonwell.fi/t/gauntlet-s-base-moonbeam-moonriver-recommendations-2024-03-26/841?u=gauntlet). By approving this proposal, you agree that any services provided by Gauntlet shall be governed by the terms of service available at gauntlet.network/tos

------------------ Proposal Actions ------------------
  1). Set collateral factor of mxcUSDC
  target: 0x8E00D5e02E65A19337Cdba98bbA9F84d4186a180
value: 0
payload
Proposal type: Moonbeam

  0xe4028eee00000000000000000000000022b1a40e3178fe7c7109efcc247c5bb2b34abe320000000000000000000000000000000000000000000000000214e8348c4f0000

  2). Set collateral factor of mGLIMMER
  target: 0x8E00D5e02E65A19337Cdba98bbA9F84d4186a180
value: 0
payload
Proposal type: Moonbeam

  0xe4028eee000000000000000000000000091608f4e4a15335145be0a279483c0f8e4c795500000000000000000000000000000000000000000000000007e90bfae1f90000

  3). Set reserve factor for mxcUSDC to updated reserve factor
  target: 0x22b1a40e3178fe7C7109eFCc247C5bB2B34ABe32
value: 0
payload
Proposal type: Moonbeam

  0xfca7820b00000000000000000000000000000000000000000000000003782dace9d90000

  4). Set reserve factor for mxcUSDT to updated reserve factor
  target: 0x42A96C0681B74838eC525AdbD13c37f66388f289
value: 0
payload
Proposal type: Moonbeam

  0xfca7820b00000000000000000000000000000000000000000000000003782dace9d90000

  5). Set reserve factor for mxcUSDT to updated reserve factor
  target: 0x42A96C0681B74838eC525AdbD13c37f66388f289
value: 0
payload
Proposal type: Moonbeam

  0xfca7820b00000000000000000000000000000000000000000000000003782dace9d90000

  6). Set interest rate model for mxcUSDC to updated rate model
  target: 0x22b1a40e3178fe7C7109eFCc247C5bB2B34ABe32
value: 0
payload
Proposal type: Moonbeam

  0xf2b3abbd00000000000000000000000032f3a6134590fc2d9440663d35a2f0a6265f04c4

  7). Set interest rate model for mxcUSDT to updated rate model
  target: 0x42A96C0681B74838eC525AdbD13c37f66388f289
value: 0
payload
Proposal type: Moonbeam

  0xf2b3abbd0000000000000000000000001cdb984008dcee9d06c28654ed31cf82680eea62

  8). Set interest rate model for mFRAX to updated rate model
  target: 0x1C55649f73CDA2f72CEf3DD6C5CA3d49EFcF484C
value: 0
payload
Proposal type: Moonbeam

  0xf2b3abbd000000000000000000000000e1dd796dbeb5a67ce37cbc52dcd164d0535c901e

  9). Set interest rate model for mUSDCwh to updated rate model
  target: 0x744b1756e7651c6D57f5311767EAFE5E931D615b
value: 0
payload
Proposal type: Moonbeam

  0xf2b3abbd000000000000000000000000f22c8255ea615b3da6ca5cf5aecc8956bff07aa8

  ------------------ Proposal Targets, Values, Payloads ------------------
  target: 0x8E00D5e02E65A19337Cdba98bbA9F84d4186a180
value: 0
payload

  0xe4028eee00000000000000000000000022b1a40e3178fe7c7109efcc247c5bb2b34abe320000000000000000000000000000000000000000000000000214e8348c4f0000
  target: 0x8E00D5e02E65A19337Cdba98bbA9F84d4186a180
value: 0
payload

  0xe4028eee000000000000000000000000091608f4e4a15335145be0a279483c0f8e4c795500000000000000000000000000000000000000000000000007e90bfae1f90000
  target: 0x22b1a40e3178fe7C7109eFCc247C5bB2B34ABe32
value: 0
payload

  0xfca7820b00000000000000000000000000000000000000000000000003782dace9d90000
  target: 0x42A96C0681B74838eC525AdbD13c37f66388f289
value: 0
payload

  0xfca7820b00000000000000000000000000000000000000000000000003782dace9d90000
  target: 0x42A96C0681B74838eC525AdbD13c37f66388f289
value: 0
payload

  0xfca7820b00000000000000000000000000000000000000000000000003782dace9d90000
  target: 0x22b1a40e3178fe7C7109eFCc247C5bB2B34ABe32
value: 0
payload

  0xf2b3abbd00000000000000000000000032f3a6134590fc2d9440663d35a2f0a6265f04c4
  target: 0x42A96C0681B74838eC525AdbD13c37f66388f289
value: 0
payload

  0xf2b3abbd0000000000000000000000001cdb984008dcee9d06c28654ed31cf82680eea62
  target: 0x1C55649f73CDA2f72CEf3DD6C5CA3d49EFcF484C
value: 0
payload

  0xf2b3abbd000000000000000000000000e1dd796dbeb5a67ce37cbc52dcd164d0535c901e
  target: 0x744b1756e7651c6D57f5311767EAFE5E931D615b
value: 0
payload

  0xf2b3abbd000000000000000000000000f22c8255ea615b3da6ca5cf5aecc8956bff07aa8
  Governor artemis proposal calldata
  [encoded data, 10378 characters]
  Governor multichain proposal calldata
  [encoded data, 9098 characters]

Proposal Description:

# MIP-M25: Gauntlet's Moonbeam Recommendations

A proposal to adjust 7 total risk parameters:

| Parameter                  | Current Value | Recommended Value |
| -------------------------- | ------------- | ----------------- |
| xcUSDC Collateral Factor   | 10%           | 15%               |
| WGLMR Collateral Factor    | 58%           | 57%               |
| WGLMR Borrow Cap           | 22,500,000    | 10,000,000        |
| WBTC.wh Borrow Cap         | 50            | 5                 |
| WETH.wh WBTC.wh Borrow Cap | 500           | 100               |
| xcUSDT Reserve Factor      | 20%           | 25%               |
| xcUSDC Reserve Factor      | 20%           | 25%               |

A proposal to make a IR curve adjustments for USDC.wh:

| USDC.wh IR Parameters | Current    | Recommended |
| --------------------- | ---------- | ----------- |
| BASE                  | 0          | 0           |
| Kink                  | 0.8        | 0.8         |
| Multiplier            | **0.0845** | **0.0875**  |
| Jump Multiplier       | **7.2**    | **7.4**     |

A proposal to make an IR curve adjustments for xcUSDC:

| xcUSDC IR Parameters | Current    | Recommended |
| -------------------- | ---------- | ----------- |
| BASE                 | 0          | 0           |
| Kink                 | 0.8        | 0.8         |
| Multiplier           | **0.0814** | **0.0875**  |
| Jump Multiplier      | **7.0**    | **7.4**     |

A proposal to make a IR curve adjustments for xcUSDT:

| xcUSDT IR Parameters | Current    | Recommended |
| -------------------- | ---------- | ----------- |
| BASE                 | 0          | 0           |
| Kink                 | 0.8        | 0.8         |
| Multiplier           | **0.0814** | **0.0875**  |
| Jump Multiplier      | **7.0**    | **7.4**     |

A proposal to make an IR curve adjustments for FRAX:

| FRAX IR Parameters | Current  | Recommended |
| ------------------ | -------- | ----------- |
| BASE               | 0        | 0           |
| Kink               | 0.8      | 0.8         |
| Multiplier         | **0.01** | **0.0563**  |
| Jump Multiplier    | **0.01** | **4**       |

Our recommendation post is located in the forums, please refer to this [link](https://forum.moonwell.fi/t/gauntlet-s-base-moonbeam-moonriver-recommendations-2024-03-26/841?u=gauntlet). By approving this proposal, you agree that any services provided by Gauntlet shall be governed by the terms of service available at gauntlet.network/tos

------------------ Proposal Actions ------------------
  1). Set collateral factor of mxcUSDC
  target: 0x8E00D5e02E65A19337Cdba98bbA9F84d4186a180
value: 0
payload
Proposal type: Moonbeam

  0xe4028eee00000000000000000000000022b1a40e3178fe7c7109efcc247c5bb2b34abe320000000000000000000000000000000000000000000000000214e8348c4f0000

  2). Set collateral factor of mGLIMMER
  target: 0x8E00D5e02E65A19337Cdba98bbA9F84d4186a180
value: 0
payload
Proposal type: Moonbeam

  0xe4028eee000000000000000000000000091608f4e4a15335145be0a279483c0f8e4c795500000000000000000000000000000000000000000000000007e90bfae1f90000

  3). Set reserve factor for mxcUSDC to updated reserve factor
  target: 0x22b1a40e3178fe7C7109eFCc247C5bB2B34ABe32
value: 0
payload
Proposal type: Moonbeam

  0xfca7820b00000000000000000000000000000000000000000000000003782dace9d90000

  4). Set reserve factor for mxcUSDT to updated reserve factor
  target: 0x42A96C0681B74838eC525AdbD13c37f66388f289
value: 0
payload
Proposal type: Moonbeam

  0xfca7820b00000000000000000000000000000000000000000000000003782dace9d90000

  5). Set reserve factor for mxcUSDT to updated reserve factor
  target: 0x42A96C0681B74838eC525AdbD13c37f66388f289
value: 0
payload
Proposal type: Moonbeam

  0xfca7820b00000000000000000000000000000000000000000000000003782dace9d90000

  6). Set interest rate model for mxcUSDC to updated rate model
  target: 0x22b1a40e3178fe7C7109eFCc247C5bB2B34ABe32
value: 0
payload
Proposal type: Moonbeam

  0xf2b3abbd00000000000000000000000032f3a6134590fc2d9440663d35a2f0a6265f04c4

  7). Set interest rate model for mxcUSDT to updated rate model
  target: 0x42A96C0681B74838eC525AdbD13c37f66388f289
value: 0
payload
Proposal type: Moonbeam

  0xf2b3abbd0000000000000000000000001cdb984008dcee9d06c28654ed31cf82680eea62

  8). Set interest rate model for mFRAX to updated rate model
  target: 0x1C55649f73CDA2f72CEf3DD6C5CA3d49EFcF484C
value: 0
payload
Proposal type: Moonbeam

  0xf2b3abbd000000000000000000000000e1dd796dbeb5a67ce37cbc52dcd164d0535c901e

  9). Set interest rate model for mUSDCwh to updated rate model
  target: 0x744b1756e7651c6D57f5311767EAFE5E931D615b
value: 0
payload
Proposal type: Moonbeam

  0xf2b3abbd000000000000000000000000f22c8255ea615b3da6ca5cf5aecc8956bff07aa8

  New addresses after deploy:
  New addresses after deploy:
EIP-3855 is not supported in one or more of the RPCs used.
Unsupported Chain IDs: 1284.
Contracts deployed with a Solidity version equal or higher than 0.8.20 might not work properly.
For more information, please see https://eips.ethereum.org/EIPS/eip-3855

## Setting up 1 EVM.
  [21550] xcUSDT::setSymbol("xcUSDT")
    └─ ← EvmError: Revert

  [21550] xcUSDC::setSymbol("xcUSDC")
    └─ ← EvmError: Revert

  [21538] xcDOT::setSymbol("xcDOT")
    └─ ← EvmError: Revert

MIP-B15 Output:
No files changed, compilation skipped
Script ran successfully.

== Logs ==
  deployerAddress:  0x9A187663E454e99CAFd40a2712606CC306e301b2

calldata for execution on temporal gov: abi.encode(temporalGovernor, targets, values, payloads)
  0x0000000000000000000000008b621804a7637b781e2bbd58e256a591f2df7d51000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000e000000000000000000000000000000000000000000000000000000000000001400000000000000000000000000000000000000000000000000000000000000002000000000000000000000000703843c3379b52f9ff486c9f5892218d2a065cc8000000000000000000000000edc817a28e8b93b03976fbd4a3ddbc9f7d176c220000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000024fca7820b00000000000000000000000000000000000000000000000002c68af0bb140000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd0000000000000000000000000f36dda2b47984434051aecaa5f9587dea7f95b700000000000000000000000000000000000000000000000000000000

  temporal governance calldata
  0xb19a437e0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c800000000000000000000000000000000000000000000000000000000000002600000000000000000000000008b621804a7637b781e2bbd58e256a591f2df7d51000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000e000000000000000000000000000000000000000000000000000000000000001400000000000000000000000000000000000000000000000000000000000000002000000000000000000000000703843c3379b52f9ff486c9f5892218d2a065cc8000000000000000000000000edc817a28e8b93b03976fbd4a3ddbc9f7d176c220000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000024fca7820b00000000000000000000000000000000000000000000000002c68af0bb140000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd0000000000000000000000000f36dda2b47984434051aecaa5f9587dea7f95b700000000000000000000000000000000000000000000000000000000
  wormhole publish governance calldata
  0xb19a437e0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c800000000000000000000000000000000000000000000000000000000000002e4b19a437e0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000c800000000000000000000000000000000000000000000000000000000000002600000000000000000000000008b621804a7637b781e2bbd58e256a591f2df7d51000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000e000000000000000000000000000000000000000000000000000000000000001400000000000000000000000000000000000000000000000000000000000000002000000000000000000000000703843c3379b52f9ff486c9f5892218d2a065cc8000000000000000000000000edc817a28e8b93b03976fbd4a3ddbc9f7d176c220000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000024fca7820b00000000000000000000000000000000000000000000000002c68af0bb140000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd0000000000000000000000000f36dda2b47984434051aecaa5f9587dea7f95b70000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000

calldata for execution on temporal gov: abi.encode(temporalGovernor, targets, values, payloads)
  0x0000000000000000000000008b621804a7637b781e2bbd58e256a591f2df7d51000000000000000000000000000000000000000000000000000000000000008000000000000000000000000000000000000000000000000000000000000000e000000000000000000000000000000000000000000000000000000000000001400000000000000000000000000000000000000000000000000000000000000002000000000000000000000000703843c3379b52f9ff486c9f5892218d2a065cc8000000000000000000000000edc817a28e8b93b03976fbd4a3ddbc9f7d176c220000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000000000000024fca7820b00000000000000000000000000000000000000000000000002c68af0bb140000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000024f2b3abbd0000000000000000000000000f36dda2b47984434051aecaa5f9587dea7f95b700000000000000000000000000000000000000000000000000000000

  multichain governor queue governance calldata
  [encoded data, 4874 characters]

Proposal Description:

#  MIP-B15: Gauntlet's Base Recommendations

A proposal to adjust 5 risk parameters:

| Risk Parameter    | Current Value | Recommended Value |
| ----------------- | ------------- | ----------------- |
| WETH Supply Cap   | 12,500        | 18,000            |
| WETH Borrow Cap   | 10,500        | 14,000            |
| wstETH Supply Cap | 1,800         | 2,100             |
| wstETH Borrow Cap | 800           | 900               |
| USDbC RF          | 15%           | 20%               |

<sub> *Cap Recommendations will be implemented via Guardian </sub>

### IR Parameters

A proposal to adjust USDC's IR curve:

| USDC IR Parameters | Current   | Recommended |
| ------------------ | --------- | ----------- |
| Base               | 0         | 0           |
| Kink               | **0.8**   | **0.9**     |
| Multiplier         | **0.065** | **0.067**   |
| Jump Multiplier    | **8.6**   | **9.0**     |

Our recommendation post is located in the forums, please refer to this [link](https://forum.moonwell.fi/t/gauntlet-s-base-moonbeam-moonriver-recommendations-2024-03-26/841?u=gauntlet). By approving this proposal, you agree that any services provided by Gauntlet shall be governed by the terms of service available at gauntlet.network/tos

------------------ Proposal Actions ------------------
  1). Set reserve factor for Moonwell USDBC to updated reserve factor
  target: 0x703843C3379b52F9FF486c9f5892218d2a065cC8
value: 0
payload
  0xfca7820b00000000000000000000000000000000000000000000000002c68af0bb140000

  2). Set interest rate model for Moonwell USDC to updated rate model
  target: 0xEdc817A28E8B93B03976FBd4a3dDBc9f7D176c22
value: 0
payload
  0xf2b3abbd0000000000000000000000000f36dda2b47984434051aecaa5f9587dea7f95b7

  New addresses after deploy:
  New addresses after deploy:


Unused variable. Remove redundant $tableName variable.

https://github.com/dnadesign/silverstripe-elemental/blob/b91912a9ad54a78c388878e055e8c28515d892a3/src/Extensions/ElementalAreasExtension.php#L269

Bump @StephenMakrogianni

Closing because this appears to be done


Build 6.1.3 DB2 connection initialization settings lost

System information:

Windows 10
Build 6.1.3 CE
Java Comming with 6.1.3 CE
DB2 LUW 10.5 HF10 jdbc driver

Connection specification:

DB2 LUW 10.5 HF10
db2jcc4.jar
No Proxy No tunnel

Describe the problem you're observing:
The initialization settings in the connection settings for all DB2 LUW connections get lost when closing and restarting DBeaver 6.1.3. Such as auto commit flag, standard schema, isolation grade etc.
Steps to reproduce, if exist:
Well, change the initialization setting of a DB2 connection, then klick ok. close DBeaver, restart DBeaver, change is lost...

Exactly the same problem with Sqlite.
Dbeaver 6.1.3
Sqlite 3.28
Mac OS X 10.13.6

I can't reproduce this (with any database).
Please send error and/or debug log file. https://github.com/dbeaver/dbeaver/wiki/Log-files

Thank you Serge!
Unfortunately, there are no errors, you will find the attached file.
This is what I do:

I'm launching Dbeaver
I open my sqlite database
In the connection settings of this database, "initialization", I choose an isolation level "Serializable" and in bootstrap requests, I type "PRAGMA page_size = 8192;", I confirm.
I'm testing the connection: okay.
I click on "ok". Dbeaver informs me that he will have to reconnect the database because the connection has been modified.
I confirm that
Dbeaver opens my sqlite database again
I check the connection settings: everything is ok, my settings are there.
I leave Dbeaver and relaunch it
I open my database, check the connection settings: it's empty, my settings are no longer there.

Thank you
Olivier
log.txt

Thanks for details. now I can reproduce this.

verified


browserify recipe breaks when using transforms

The gulp recipe for browserify makes use of vinyl-transform, but I've found it not to be the best option.
Specifically it breaks whenever I add any sort of transform to the browserify bundling process.
See this reproduction.
vinyl-transform breaks down when coffeeify gets added to the mix, while vinyl-source-stream handles it like a champ.
I am developing a browserify transform and have found it to be incompatible with vinyl-transform as well.
I have a few questions:

Is there some advantage to vinyl-transform over vinyl-source-stream?
Is this a fixable issue?
Would it be better to update the recipe to use vinyl-source-stream so gulp & browserify noobs are not banging their heads against the wall when their build breaks because they tried to use a browserify transform?

You can use it to create multiple browserify bundles more easily, but otherwise the difference for browserify is just semantic.
Sadly, I have no idea what's causing it to break in this case. I suspect it's something in browserify but I'm not sure. How does it break? Does it throw an error, does it not transform the first file, does it hang, or does it just output an empty file?
If browserify transforms are broken with vinyl-transform I'd recommend just using vinyl-source-stream.

There have been maybe one or two occasions in the last three-ish years where I've needed more than one browserify bundle, so I'd personally recommend sticking with vinyl-source-stream as the default approach. I don't want to get caught up in the debate though, it seems people keep disagreeing on this one :(

I don't want to get caught up in the debate though, it seems people keep disagreeing on this one :(

The debate around integrating gulp with browserify just baffles me. That it's to the point where people (especially prolific authors who have contributed as much as yourself) would rather disengage is troubling.
I apologize for not including the console dump. That was silly of me. Also, my reproduction is truly minimal (just look at the last two gulp tasks - I wrote the rest before I discovered the controversy surrounding gulp-browserify).
git clone https://github.com/jamestalmage/coffeeify-issue.git
cd coffeeify-issue
npm install
gulp vinyl-transform

console dump:
events.js:72
        throw er; // Unhandled 'error' event
              ^
Error: write after end
    at writeAfterEnd (/Users/jamestalmage/WebstormProjects/coffeeify-issue/node_modules/browserify/node_modules/readable-stream/lib/_stream_writable.js:161:12)
    at Labeled.Writable.write (/Users/jamestalmage/WebstormProjects/coffeeify-issue/node_modules/browserify/node_modules/readable-stream/lib/_stream_writable.js:208:5)
    at /Users/jamestalmage/WebstormProjects/coffeeify-issue/node_modules/browserify/index.js:283:27
    at Array.forEach (native)
    at resolved (/Users/jamestalmage/WebstormProjects/coffeeify-issue/node_modules/browserify/index.js:282:28)
    at /Users/jamestalmage/WebstormProjects/coffeeify-issue/node_modules/browserify/index.js:314:13
    at /Users/jamestalmage/WebstormProjects/coffeeify-issue/node_modules/browserify/node_modules/resolve/lib/async.js:44:21
    at ondir (/Users/jamestalmage/WebstormProjects/coffeeify-issue/node_modules/browserify/node_modules/resolve/lib/async.js:187:31)
    at /Users/jamestalmage/WebstormProjects/coffeeify-issue/node_modules/browserify/node_modules/resolve/lib/async.js:153:39
    at onex (/Users/jamestalmage/WebstormProjects/coffeeify-issue/node_modules/browserify/node_modules/resolve/lib/async.js:93:22)

I really like how simple and straightforward the gulp recipe is using vinyl-transform, but sadly I'm having the same issue.
Here is my recipe:
// Excerpt from `../config`
// ------------------------
// javascript: {
//   src: src + '/javascript_app/**/*.{js,coffee}',
//   rootFiles: [
//     src + '/javascript_app/app.js',
//     src + '/javascript_app/test.js'
//   ],
//   dest: dest + '/js'
// },

// The gulp recipe
// ------------------------
var gulp       = require('gulp');
var sourcemaps = require('gulp-sourcemaps');
var browserify = require('browserify');
var reactify   = require('reactify');
var transform  = require('vinyl-transform');
var uglify     = require('gulp-uglify');
var config     = require('../config');

gulp.task('javascript', function () {
  var browserified = transform(function(filename) {
    var b = browserify({
        entries: filename, // Only need initial file, browserify finds the deps
        //transform: [reactify], // We want to convert JSX to normal javascript
        debug: true // Gives us sourcemapping
    });

    b.transform(reactify);

    return b.bundle();
  });

  return gulp.src(config.javascript.rootFiles)
    .pipe(browserified)
    .pipe(sourcemaps.init({loadMaps: true}))
      .pipe(uglify())
    .pipe(sourcemaps.write())
    .pipe(gulp.dest(config.javascript.dest));
});

Log without transforms

D:\repos\my_repo>gulp javascript
[09:54:27] Using gulpfile D:\repos\my_repo\gulpfile.js
[09:54:27] Starting 'javascript'...
[09:54:30] Finished 'javascript' after 3.41 s

When using the first transform method (when creating b variable)
or when using the second transform method b.transform(reactify);

D:\repos\my_repo>gulp javascript
[09:54:38] Using gulpfile D:\repos\my_repo\gulpfile.js
[09:54:38] Starting 'javascript'...
events.js:85
      throw er; // Unhandled 'error' event
            ^
Error: write after end
    at writeAfterEnd (D:\repos\my_repo\node_modules\browserify\node_modules\readable-stream\lib\_stream_writable.js:161:12)
    at Labeled.Writable.write (D:\repos\my_repo\node_modules\browserify\node_modules\readable-stream\lib\_stream_writable.js:208:5)
    at Producer.ondata (_stream_readable.js:540:20)
    at Producer.emit (events.js:107:17)
    at Producer.Readable.read (_stream_readable.js:373:10)
    at flow (_stream_readable.js:750:26)
    at resume_ (_stream_readable.js:730:3)
    at _stream_readable.js:717:7
    at process._tickCallback (node.js:355:11)

I depend on transforms so will have to use vinyl-source-stream for now.

If anyone stumbles onto the same issue looking for a solution, I've created a gist that uses vinyl-source-stream and vinyl-buffer to recreate the same functionality as my recipe above that uses vinyl-transform.
I tried keeping it as simple as possible, it is mostly adapted from @sogko's great article about gulp, browserify and vinyl. It includes react JSX, coffeescript, uglify & sourcemaps and supports multiple input & output files.

Make sure to also look at https://github.com/jamestalmage/coffeeify-issue/pull/1

@hughsk Any suggestions on how to do this with vinyl-transform?


Create design of about us page by canva/figma

Take care of the theme of website

Hey, I would like to work on about us design, Can you Assign me this task

Don't forget to star the repo.
Thank you for contributing.

Sure Mayank

Hello, I am almost going to finish the design for About us Page but dont know how to contribute it

Hi @SkullShoT007 , first share the canva or figma link here, We can discuss the changes , then i would guide you to contribute it.

https://www.figma.com/design/nmHY7JEE6tPSWQr8sm2d7t/603?node-id=0-1&t=xW6wQvlWy87D6wr7-1 (Do tell me what do you think)

I have requested for access.

check your mail

Approved

give me the access to edit .

looks good
to contribute make a .md file named ''design'' file and put it in the assests folder and put your link in there and make a pr.

Okay, Thanks for the info, and I have you access to edit the file


[Improvement] [Seatunnel-web] Add support to provide reason for job failure.

Search before asking

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

What happened
Add support to give job failure cause incase of job failure.
Currently, when job fails, the error message is not stored in the database.
Store the error message along with other information like job status etc.
SeaTunnel Version
2.3.7
SeaTunnel Config
NA

Running Command
NA

Error Exception
NA

Zeta or Flink or Spark Version
No response
Java or Scala Version
No response
Screenshots

Apart from above fields one more field should be added to capture the job failure error message.
Are you willing to submit PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

Raised PR https://github.com/apache/seatunnel-web/pull/196


Dev 1.35.0

Added values to the info part of the status api
int maxPlayers - Max players supported per server lobby
bool supportsPPModifiers
bool supportsPPDifficulties
bool serversupportsPPMap
(PP meaning per player)

renamed bool serversupportsPPMap to bool supportsPPMap

@cubicgraphics I've merged the info data/endpoint into status. I don't really see the value in having two separate endpoints here, and seemingly arbitrarily splitting config data between the two. As far as I know /info has not yet been used anywhere. LMK if you see an issue with this

Yep, I'm fine with this.

If there is any more values you think should be added please do so

I've written up some documentation on multiplayer status handling / fields, so we have a common standard for master servers:
https://github.com/Goobwabber/MultiplayerCore/wiki/Multiplayer-Status
I've also gone ahead and added the new fields to MpStatusData in https://github.com/Goobwabber/MultiplayerCore/pull/49/commits/3a7e582eaa71076866d2e0990b4c9363fda0c399 so it will be available for mods
If there's any other fields we want to introduce it'd be good to try and get them in before the upcoming release cycle