OpenAILike model and API Error

Question Validation

[X] I have searched both the documentation and discord for an answer.

Question
I set up LM Studio with TheBloke/Orca-2-13B-GGUF and am running it as server.
API endpoint is alive in browser
I am running llama-index-0.9.10
I am trying to define OpenAILike model with this code:
`import tqdm as notebook_tqdm
from llama_index import SQLDatabase,ServiceContext
from llama_index.llms import OpenAILike
from sqlalchemy import select, create_engine, MetaData, Table,inspect
from llama_index.indices.struct_store.sql_query import NLSQLTableQueryEngine
print("Okay starting")
llm = OpenAILike(
api_base="http://localhost:1234/v1",
is_chat_model=True,
context_window=1024,
model="TheBloke/Orca-2-13B-GGUF",
is_function_calling_model=True  # provide this field
)`
when trying to access model with
response = llm.complete("What can you tell me about the Ancient Aliens TV Series?") print(response.text)
I am getting API error below, any idea why is it popping up?
LocalProtocolError                        Traceback (most recent call last)
File ~/Codings/python/LLM_test1/.venv/lib/python3.9/site-packages/httpcore/_exceptions.py:10, in map_exceptions(map)
9 try:
---> 10     yield
11 except Exception as exc:  # noqa: PIE786
File ~/Codings/python/LLM_test1/.venv/lib/python3.9/site-packages/httpcore/_sync/http11.py:142, in HTTP11Connection._send_request_headers(self, request)
141 with map_exceptions({h11.LocalProtocolError: LocalProtocolError}):
--> 142     event = h11.Request(
143         method=request.method,
144         target=request.url.target,
145         headers=request.headers,
146     )
147 self._send_event(event, timeout=timeout)
File ~/Codings/python/LLM_test1/.venv/lib/python3.9/site-packages/h11/_events.py:96, in Request.init(self, method, headers, target, http_version, _parsed)
94 else:
95     object.setattr(
---> 96         self, "headers", normalize_and_validate(headers, _parsed=_parsed)
97     )
98 if not _parsed:
File ~/Codings/python/LLM_test1/.venv/lib/python3.9/site-packages/h11/_headers.py:164, in normalize_and_validate(headers, _parsed)
163     validate(_field_name_re, name, "Illegal header name {!r}", name)
...
(...)
912     stream_cls=stream_cls,
913 )
APIConnectionError: Connection error.

Ok,
looks like api key is required, so this will fix it
llm = OpenAILike(
api_base="http://localhost:1234/v1",
api_key="111",
is_chat_model=True,
context_window=1024,
model="TheBloke/Orca-2-13B-GGUF",
is_function_calling_model=False  # provide this field
)


C++: std::uint64_t vs std::size_t

Hello Devs,
Is there a reason to use std::uint64_t for indexes/sizes in generated c++ code instead of std::size_t?
Thanks

Simplicity of having one type cover all cases. It could be simplified if someone was interested in sponsoring the work.

There is mix of std::size_t/std::uint64_t

The only methods that return a std::size_t are the ones for the size of a type. Are there others?

The codecs use those types so that:

the class has a known size and consistent across platforms, and
are large enough for every use case across those platforms, etc.

The method to the madness is that the specific sizes are there so that they are consistent across platforms, compilers, and CPU architectures instead of being varied.


Add advisory for CVE-2021-32697 in neos/form

As far as I understand the related advisory every release from 1.2.0 to 4.3.2 is affected. Shouldn't this be reflected here?

Well, those versions are no longer supported, but I amended the affected versions. Hope that does the job!


merge from arlac77/template-arlac77-github,arlac77/template-esm-only

package.json

chore(deps): add ^3.11.1 remove ^3.11.0 (devDependencies.ava)
chore(deps): add ^7.3.0 remove ^7.2.1 (devDependencies.c8)

:tada: This PR is included in version 1.1.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Is it possible to disable the update check ?

Is it possible to disable that update check ?
We need it turned off, so that not everyone can update the mac and screw up out development environment. Hence the question, can we turn the update off ?
Or maybe a policy, so that certain users only may update xamarin.iOS on the buildserver ?
https://docs.microsoft.com/en-us/xamarin/ios/get-started/installation/windows/connecting-to-mac/#xamarinios

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

ID: 98c96bcc-1743-8d9f-f1b2-3c30d5b2a6e2
Version Independent ID: f57a6157-332a-3f31-c785-7efa99e62711
Content: Pair to Mac for Xamarin.iOS Development - Xamarin
Content Source: docs/ios/get-started/installation/windows/connecting-to-mac/index.md
Product: xamarin
GitHub Login: @bradumbaugh
Microsoft Alias: brumbaug

reopen as this issue is now on the correct place. Question remains the same: Can we disable the update check ?


rewriting the installation and init scripts in python

its a hassle for people on windows to run POSIX shell scripts

install script is now in python and cross platform

init scripts are now in python and cross platform


[macOS] Allow setting status item interactive removal behavior

This is largely bringing over https://github.com/getlantern/systray/pull/262 -- except there's a key fix in this version 🙂 (the setRemovalAllowed function as implemented in the original version is incorrectly using BOOL for the parameter instead of NSNumber *, which in practice means you can't ever set it back to false :P).
The new API is very basic but I didn't want to overdo it for a single-OS-specific feature anyway.

I don't understand why you are doing BOOL -> NSNumber -> BOOL

I don't understand why you are doing BOOL -> NSNumber -> BOOL

It does not build otherwise:
systray_darwin.m:362:50: error: cast of 'bool' to 'id' is disallowed with ARC

Right, so you would not cast the BOOL to an id. This is all in code you have added so it should be possible to use whichever types you want.

@andydotxyz do you prefer having two separate methods, like this? Otherwise, we will need to wrap it. (https://stackoverflow.com/a/6120731 explains better than I can, as I obviously do very little macOS-specific development :))

@andydotxyz just wanted to check in on this again! Let me know if you have any other preferred solution here.

Sorry I got lost in the Apple documentation for passing parameters into different thread calls and understand the problem you were trying to work around.
What I forgot to post last week is that I think it's up to you - neither is ideal, but I see now the pattern you were copying before.

Well, let's go with the current (two method) approach then 🙂  This is just step one in a long side quest to free up some mandatory menu bar apps at work 😆

Yeah that sounds good.
I wonder, is there any point including the RemovalAllowed for platforms where it is not supported?
It feels misleading. If it is to be included it should certainly have documentation to show it is non-functional.

Yeah that sounds good.
I wonder, is there any point including the RemovalAllowed for platforms where it is not supported? It feels misleading. If it is to be included it should certainly have documentation to show it is non-functional.

Do we have any way to "exclude" it from other platforms? It's documented on the method that it is macOS only, and that's also mentioned in the readme. Where else would you like it documented?

Do we have any way to "exclude" it from other platforms?

Just removing the empty methods will do that won't it? The code will only compile if you use that method on macOS. Maybe that's a bit aggressive?

It's documented on the method that it is macOS only

I know that is what it looks like, but that won't actually be visible on generated API documentation - because it is on the Darwin method only. So if the person generating the docs is on macOS then it will be published, but if they are on a linux computer the docs will be empty... Do you see the challenge here?

Do we have any way to "exclude" it from other platforms?

Just removing the empty methods will do that won't it? The code will only compile if you use that method on macOS. Maybe that's a bit aggressive?

Yeah, I think that is too aggressive. There are a few other methods that do not work on every platform, and follow this same pattern, e.g.:
func SetTitle(t string)
    SetTitle sets the systray title, only available on Mac and Linux.

It's documented on the method that it is macOS only

I know that is what it looks like, but that won't actually be visible on generated API documentation - because it is on the Darwin method only. So if the person generating the docs is on macOS then it will be published, but if they are on a linux computer the docs will be empty... Do you see the challenge here?

The comment is on the empty method in systray_unix.go too -- I think it would still show up. I just checked quickly with go doc -all on a Linux box and see:
func SetRemovalAllowed(allowed bool)
    SetRemovalAllowed sets whether a user can remove the systray icon or not.
    This is only supported on macOS.

The comment is on the empty method in systray_unix.go too -- I think it would still show up.

My apologies, not sure how that didn't work for me.

@andydotxyz just wanted to bump this again - happy to make more changes if desired, but I think this might be mergeable now?

Thanks, I forgot sorry


How to use ForeignKeyContainer

With the Getting Started example model, I tried the following:
    Colony colony = new Colony();
    colony.name = "DBFlow Colony";
    colony.save();

    System.out.println("Colony: " + new Select().from(Colony.class).querySingle().toString());
    // => Colony:Colony{id=1, name='DBFlow Colony'} : OK

    Queen queen = new Queen();
    queen.name = "The Queen";
    queen.colony = colony;
    queen.save();

    System.out.println("Queen: " + new Select().from(Queen.class).querySingle().toString());
    // => Queen: Queen{id=1, name='The Queen', colony=Colony{id=1, name='DBFlow Colony'}, ants=null} : OK

    Ant ant1 = new Ant();
    ant1.type = "mater";
    ant1.isMale = true;
    ant1.associateQueen(queen);
    ant1.save();

    System.out.println("Ant1: " + new Select().from(Ant.class).querySingle().toString());
    // => Ant1: Ant{id=1, type='warrior', isMale=true, queenModelContainer=null}

At this point queenModelContainer is null. Is this normal ?

Same problem here.
It seems ForeignKeyContainer has a ModelClass object on it, but it does not save. It's used only for reading from database, not saving. To save data it is using DataClass object, but I don't know the relationship between a model and this dataclass.

This issue is duplicated:
https://github.com/Raizlabs/DBFlow/issues/313

I close it, because it’s a duplicate of #313 .


get_element_values raises no exceptions.

get_element_values does not raise any exceptions if you enter an incorrect input, it simply returns an empty list.

upon further inspection, it raises exceptions for incorrect field and handle inputs, provided the family is correct. However, if the family is incorrect it will not raise any exceptions regardless of what you input.


Mobile responsiveness || Hamburger menu

Hey, I would like to open this issue under JWOC. I wish to make this properly responsive by adding a hamburger menu for the mobile view and adjusting the responsiveness of the rest. Thank you!

can i work on this?

@ritika728 Go for it


Large NOTIFY gets unbearably slow

Summary
In my project, I'm connecting to a device that transfers a relatively large amount of data (up to 16MB) via a characteristic's NOTIFY. The equivalent code on iOS works fine, however on Android, using RxAndroidBle, it slows down to an unbearably slow speed the more data it receives.
MTU is set properly, and ends up being 247 (250 - 3b header), which is the maximum supported on the devices. iOS uses a lower MTU, 162 (165 - 3b header).
I've tried requesting lower MTU to see if it helps, to no avail.
The code is pretty simple, after the connection is established (using ReplayingShare), it creates the subscription via setupNotification.
The transfer starts out with pretty decent speed, 1MB takes around 1 minute to sync, however around 3MB received, the speed drops, and the next MB takes 2 minutes, the next MB then 3-4 minutes, and the transfer time keeps creeping up.
Initially I thought it was my fault, as I was storing the data the worst possible way:
var rawData = ByteArray(0)

// in the subscribe block:
rawData += it

However even after removing the storage of the data, the slow-down still happens.
Library version
1.10.4
Preconditions
Steps to reproduce actual result
Not sure if it's reproducible as I have not seen any devices that use a similar technique to transfer data stored on them.
Actual result
The speed of the transfer drops exponentially (or rather, the amount of time required to transfer the same amount of data increases exponentially). The time between the logged Transferred $x out of $y events also increases (initially it's around 10-20ms between messages, which increases to around 100-120ms by the time I transferred ~3MB).
Expected result
Speed should be somewhat constant, with minimum variation between the times required to transfer the same sized blocks.
Minimum code snippet reproducing the issue
var transferred = 0
connection
    ?.flatMap { it.setupNotification(id) }
    ?.flatMap { it }
    ?.subscribe(
        {
            transferred += it.size
            logger.i("[DataSync] Transferred $transferred out of $available")
        },
        { logger.e(it, "[DataSync] Exception happened") },
        { logger.i("[DataSync] Transfer complete!") }
    )
    .addToEventStream(eventStream)

Hi,
Thanks for the report — have you investigated the issue? Perhaps connection parameters are changing?

Yes, I've done some extensive investigation. Initially I thought it was my stupid way of handling the received data (I was recreating the ByteArray by calling rawData += it in subscribe, where rawData is a var ByteArray), however even moving to a preallocated ByteBuffer had the same issue. That's when I switched to the above size checking method, and it was showing the same issues - even though it was just an int field increment.
GC is also going crazy during these events, even without storing the received ByteArray, at the end running around every 200-300ms and freeing up megabytes of data.
I have a feeling there's some background caching going on that causes this issue.

I have a feeling there's some background caching going on that causes this issue.

There is nothing like this with notifications that I know of. Have you checked the connection parameters? What are they set to? How often and how big notifications are?

Have you checked the connection parameters?

Yes I did. PDU is phone-dependent, MTU is always 250.
Connection params on connection:
onConnectionUpdated(), status=0, interval=6 (7.50 ms), latency=0, timeout=500 (5000 ms)
First update (immediately after connection):
onConnectionUpdated(), status=0, interval=36 (45.00 ms), latency=0, timeout=500 (5000 ms)
After a transfer:
onConnectionUpdated(), status=0, interval=24 (30.00 ms), latency=0, timeout=500 (5000 ms)
After each transfer (when the unsubscribe from the NOTIFY characteristic happens), the above connection update happens.
Based on this, the message interval should be 30ms, which roughly correlates to my previous observation of roughly 10-20ms between messages (which technically was rather around 18-28 after doing some proper math, instead of rough estimate). However a longer transfer still increases the interval from this 30ms to around 150-200ms by the time 4MB is transferred, and even higher if a transfer is ongoing. Connection updates are not present during this.

Have you monitored the app? What is getting garbage collected — what not? Is this download the only thing that is getting the notifications?

Yes, I'm monitoring the app - and the RAM usage goes up the moment I start the transfer, and keeps going up. GC calls are mostly explicit, but it does not state the location. There are also some background calls, but they're like 1 out of 100-120 explicit calls.
Did a quick test, just measuring the intervals between received messages, and the intervals clearly increase - we begin at around 10-15ms, and by the time I receive around 10k notifications, it grows to 60ms between messages. Around 20k messages, average interval grows to around 120ms, and it skyrockets higher and higher. Tested the device with other solutions (nRF Connect), and it produced even lower intervals between messages (around 3-6ms!) continuously throughout the transfer, so it's definitely not the device, or the underlying core BLE bits.

This may be true — easy API usually have performance limitations — basing on RxJava definitely adds some more allocations + additional library abstraction. Your use-case is quite peculiar. You can create an RxBleCustomOperation and operate directly on BluetoothGatt and BluetoothGattCallback to cut out the middle man from equation.

That's probably what I'll do, unless I just straight out replace RxAndroidBle with nRF's solution (it fits in better/easier with my current Kotlin Coroutines structure anyway). I also have to write a custom operation to be able to receive the GATT response codes (the device I'm working on has some custom GATT opcodes that I need to process, but not as exceptions - and most of them aren't even thrown as BleGattCharacteristicExceptions), so this might be just the way I go on short term.

I would love to know what will be your results when getting notifications via custom operation. As for the inability to get GATT codes and BleGattCharacteristicExceptions I am surprised — could you create a separate issue for that so we could dig into it?
I had just looked into the source code but all onCharacteristicWrite() non GATT_SUCCESS GATT codes should be wrapped into BleGattCharacteristicException. All exceptions can be caught in RxJava code and unwrapped as separate results i.e.
connection.writeCharacteristic(uuid, data)
    .map(toYourResultWithData)
    .onErrorResumeNext(throwableToResultWithYourCustomGattCodeOrExceptionOtherwise)

@dariuszseweryn interesting thing with the RxBleCustomOperation - everything works (characteristic read-write, descriptor read-write), however after enabling notifications on the specific characteristic, I get no calls to onCharacteristicChanged. The following gist is the main part of my code (some identifying bits redacted): https://gist.github.com/fonix232/3d9fb22f25ecf7f3a1094bf6f6088c2b
I'm fairly certain I'm doing the NOTIFY subscription properly, and the device also thinks the notifications went through (NOTIFY verifies every package with the device if it was received, and after some time the device shows that all data was successfully transferred).  As you can see I have a log line before any sort of filtering of the incoming change happens, and that line never shows up.
Is it possible that even though I pass the native callback, the onCharacteristicChanged bit doesn't get called?

That is the exact funny thing about Android's BLE API. It is not easy to get it right.
See BluetoothGatt#setCharacteristicNotification — you must call it to register for notifications internally on the system — this and setting CCC descriptor are needed to get callbacks.

Ah, indeed you're right. Multiple sources suggested that writing the descriptor with BluetoothGattDescriptor.ENABLE_NOTIFICATION_VALUE value will also trigger setCharacteristicNotification() internally. This is not the case. All is working fine now, I will be reporting back sometime next week to see if this actually improves transfer speeds!

Report time!
The custom implementation, as above, indeed performs as expected - no memory spikes in Profiler, no GC going crazy, and transfer speeds are quite optimal - the previously mentioned 8MB and 16MB transfers complete in about 2 minutes 30 seconds and roughly 5 minutes. Which is much better than the direct RxAndroidBle notify's 16-20 minutes, and is in the expected range of transfer times.
Something is definitely going wrong in the Rx stack here. I understand that this won't affect most users as NOTIFY is mostly used to have periodic updates, however if anyone copies this method of transferring larger data chunks, they will definitely run into the same issue.

Glad to hear that using a custom operation helped your case.

however if anyone copies this method of transferring larger data chunks, they will definitely run into the same issue

That is the usual problem with performant vs. easy-to-use APIs. If you want to get performance you should strive for bare-metal implementations, which in case of Android BLE APIs are not exactly rookie friendly and can lead to a nonfunctional Android BLE stack and/or phone models incompatibility. This library aims for the ease-of-use and is highly reliant on RxJava which on one hand makes it easy to implement thread safe code and on the other adds (quite a lot of) additional allocations.
RxBleCustomOperation was meant for some advanced use-cases that need access to bare Android API to provide functionality that is not exposed otherwise and/or better performance.

This library aims for the ease-of-use and is highly reliant on RxJava which on one hand makes it easy to implement thread safe code and on the other adds (quite a lot of) additional allocations.

Yes, but shouldn't a transition from a callback to a simple Observable<> be somewhat linear? The increase in time is far worse than the usual overhead Rx adds, and the incrementing time between packets/messages/onNexts is what worries me. It seriously feels like there's some buffering going on which causes this issue at the core.

It should be linear. I am pretty sure there is no buffering. There is at least one explicit object allocation and a thread switch (which may be the cause of increasing times if it is overwhelmed with events). Other allocations are related to RxJava internals. Maybe it would be possible to optimise current code. I do not know what device/os you have tested on.

That's what I'd expect too, based on my prior experience with RxJava. I mean, if Rx can generally provide a streamlined access to massive, fast-streaming objects (a previous project of mine, where news articles were broken up into blocks and stored in an SQL database, and Rx was used to stream these objects into the actual article display objects), the same should apply to fast-streaming, but small (250b) objects as well. The thread switching part does sound suspicious though.
Testing was done on various devices - Pixel 1 and 2, a bunch of Samsung phones (S6, S7, S8+, Note8, Note9), OnePlus devices (really poor Bluetooth experience in general, but that's a device fault), and some Sony phones. All of them presented the same issue, the transfer time increase between 10% blocks was almost exponential (our best result was a 10-25-60-120-250-280s increase, and that was when I stopped the test at 80% - though I believe the increase started "evening out" at the end, given the small jump from 250s to 280s), and got unbearably slow around the end.

You may try commenting out the thread switching code (.observeOn() or .delay() depending on the code version) in RxBleGattCallback#getOnCharacteristicChanged and check if it helps in your case. I wonder what is the exact problem here.

I will see if I have any time - unfortunately I've got a bunch of deadlines before the holidays, and even this three-day party with custom operations have delayed some important work. But it's definitely worth taking a look at, I think - though I understand why you can't test it without any devices that emulate this behaviour.

I have patched up an nRF52 (PCA10056) based peripheral that spams notifications with MTU 512
Test code
Test code based on 1.11.0-SNAPSHOT (sha1 3c02d19173588ac66da593201fa1d143663ba7b1):
rxBleClient.scanBleDevices(
    ScanSettings.Builder().setScanMode(ScanSettings.SCAN_MODE_LOW_LATENCY).build(),
    ScanFilter.Builder().setServiceUuid(ParcelUuid(serviceUuid)).build()
)
    .take(1)
    .flatMap { it.bleDevice.establishConnection(false) }
    .flatMap { c ->
        c.setupNotification(settingsUuid)
            .flatMap { dataObs ->
                val throughputEvery10Seconds = dataObs
                    .window(10, TimeUnit.SECONDS)
                    .flatMapSingle { it.reduce(0, { sum, data -> sum + data.size }) }
                    .map { it.toFloat() / 10.0f }
                c.requestMtu(512).ignoreElement()
                    .andThen(throughputEvery10Seconds)
            }
    }
    .subscribe(
        { Log.e("SPEED", "$it Bps") },
        { Log.e("SPEED", "Whoops!", it) }
    )

For reference: Your target average throughput is 8MB / 2.5 min = ~56000 Bps.
 I have two ideas on what may potentially be wrong:

My test code is not reflecting your situation well enough — I have focused on measuring throughput using sheer RxJava operators
connection observable in your test code is a shared one and a different place in the app does something that is crippling the performance

Question
Do you see what may be different between our setups?

Well, for starters, I'm still using 1.10.4, though I doubt it means much of a difference.
Then, the actual difference - I'm using an abstraction layer that takes an RxBleDevice, and wraps its functions with Kotlin Coroutines. A quick excerpt of what I'm doing: https://gist.github.com/fonix232/fef86e6124431d012b2c42734589041b
As you can see, I've managed to cobble together a quite performant little Coroutine wrapper (the rest of the app also uses Coroutines, but there's simply no usable solution for BLE on Android that works nice with them, and changing the rest of the app to work Rx-style would be a challenge at this point).
However I don't see how Coroutines could cause this issue - there's no thread switching, no heavy computation, and the coroutines-rx conversion is also pretty lightweight on the Channel subscription (see e.g. enableNotifyAsync).

Is this abstraction layer https://github.com/Kotlin/kotlinx.coroutines/tree/master/reactive/kotlinx-coroutines-rx2 ?

That, and also https://github.com/Kotlin/kotlinx.coroutines/tree/master/reactive/kotlinx-coroutines-reactive

I might have find the culprit of high memory consumption in your code. .openSubscription() creates a SubscriptionChannel that is a LinkedListChannel — which as you can read has an unlimited buffer.
It seems that if the producer is quicker than consumer the buffer will get filled — slowing down the machine due to amount of work needed to allocate a bigger buffer.

Hmm, that's definitely interesting, and would explain why the slowdown happens only on larger transfers (e.g. an 8MB transfer shows now slowing down up until ~90% at worst, usually none at all).
@dariuszseweryn what do you recon, would a batching operation on the Rx end of things possibly mitigate the problem? Given the packet size and frequency, I'm thinking about either using your window() approach with an update, say, every second, or possibly by size (say, every kB) - but all of this would depend on the transfer size and MTU of course.

what do you recon, would a batching operation on the Rx end of things possibly mitigate the problem?

If the issue (and so it seems) is poor performance of data consumer then batching the data should decrease amount of "thread" switches — this may be a good path to take. Batching by time should be better approach I suppose.
I have also checked the performance of version 1.10.5 on Samsung Galaxy S8 / API 26 but results were comparable. 1.10.5 has a fix for a situation where notifications from two (or more) different characteristics could be emitted in different order than they arrived — @fonix232 in your case this should not be a problem since you mentioned you use single characteristic notifications.
Test vs notifications with MTU 23 (~25kB / ~1300 events per second) gave around 10% CPU utilisation. No memory spikes were observed.
This topic is somewhat related to #41

What I'm testing now is moving the custom operations' emitter.onNext() into a clause that only gets run if the percentage changes. In this case, this would mean that instead of some ~70k onNext calls, there would be a total of 101 messages (100x onNext + 1 onComplete). However sadly there doesn't seem to be any improvements - in case of a 16MB transfer, the speeds still drop around the end (and sometimes even in the middle - it's quite random and honestly I can't even wrap my head around where the bottleneck might be, as even RxBleLog reports the received packages arriving at larger and larger intervals). On the other hand, said message intervals do equalise out at the end - after a few messages (roughly 1-2% worth), the intervals become pretty stable, although high (initially I'd receive a message, logged, every 10-15ms, which then jumps up to 300-400ms per batches).

I may not be the best person to give advices about kotlin coroutines as I have little experience with them — I just try to rule out that the library is the culprit of bad performance.
The thread you use for processing BLE data may be shared with different parts of the code which may indirectly degrade performance of the subject code. Or the processing itself (disc IO?) is slow? Hard to say for me as I am not a part of your project and can only make a stub on my end — sample code seems to work with acceptable performance.

Except I even tested with no processing - not even storage of the data, just increment a counter - and the slowdown still happens.
I will try adapting your flow into a sample app to see if this issue still happens using pure Rx code and nothing else around it.

We have different results in our tests. You could prepare a repository which I could just copy and install that shows the problem so I can play with it. Without it cannot do much more.

Two weeks have passed. I am closing this issue. Still — feel free to share a minimal project that displays the issue — I could then start digging /experimenting from there and reopen the topic. Although it seems not related directly to the library, having experience with coroutines could help in the future or give hints whether a coroutines API is feasible for BLE.


test/third_party_tests are not running on staging branch

Search before asking

[X] I have searched the EvaDB issues and found no similar bug report.

Bug
Currently, we have Mysql and PostgreSQL setup on the staging branch and their third_party_tests are running on the staging branch.
However, other tests (e.g., test/third_party_tests/test_github_datasource.py, test/third_party_tests/test_native_similarity_index.py) seem to be not running on the staging now. Some of them do not need special set up, and can run with long integration tests.
@jiashenC which is the best way to handle this? Shall we move those tests that do not need special setup out of the third_party_tests or add a special mark to tests in third_party_tests that need special setup and include the directory in the long integration.
Environment
No response
Are you willing to submit a PR?

[ ] Yes I'd like to help by submitting a PR!

I see. Does test/third_party_tests/test_github_datasource.py require special setup? If not, we can move them out. The native similarity search test needs a special setup that Postgres's vector extension needs to be enabled.

Get it. No it does not require special setup. I will move it outside third_party_tests. Does the native similarity search test run any where now? I think the postgres third party test also does not run the test.

Right, I doubt we can install pgvector extension for the already built docker. We probably need to setup a completely new job with a different docker image. Or, we can work on the hosted postgres issue.


Can you please rename context menu items?

Sorry, it might be a little creepy, but i can never remember what those two items in the VS Code context menu should do (without lost my data):

To understand:
Means Sync To Remote more Sync From Local To Remote or Sync Local To Remote? The same for Sync To Local. Means it more Sync From Remote To Local or Sync Remote To Local?
I am dare to use those functions because i never know if something wrong happens if i am a little bit to busy :) Btw.: they never did what i thought they would do.
So, better could be:
Sync To Remote (Upload Files) or Sync To Local (Download Files)
Sync To Remote (Local is Master) or Sync To Local (Remote is Master)
or something like this :)
Maybe you have better names at all ;)
Thank you 👍

Good advice!

Done in  v1.6.0.


[Doc] Remove as=system:admin for developer user

With https://github.com/code-ready/snc/pull/361, developer user
is not part of sudoers cluster role. This patch remove as=system:admin
mentions for developer user.
fixes: #2097

/assign @robin-owen


lines of code do not respect the margin

when the code text line  is longer, the code line he settles down, but does not respect horizontal clearance, and looks messy.
"Sublime Text" if it respects the margins when the codes are great.
I will give an example:

BRACKETS
22
23.....................<text_> texttextt exttexttexttexttext texttexttexttexttexttexttex ttexttexttextte xttexttexttextte x ttexttexttexttextt exttextt exttex ttexttexttex ttexttext<text_>
24
25

SUBLIME TEXT
22
23............................................<text_> texttextt exttexttexttexttext texttexttexttexttexttexttex ................................................ttexttexttextte xttexttexttextte x ttexttexttexttextt exttextt exttex ................................................ttexttexttex ttexttext<text_
24
25

The text looks more neat, clean and easy to read.
I hope I can do the same as it has cost me a lot of work visually adapt to this "disorder"
Thank you very much for your attention

Correct me if I'm wrong: you want the text to

wrap at a certain position
and indent the remaining line according to the indentation of the line that was wrapped

Correct?

I like this suggestion. Some people might still want the old wrapping. I think this should be something enabled by default, but keep the ability to turn of this feature.
A good name for this might be "Indent on wrap" and have it sit under the Word Wrap option in the view menu.


Making dynanmic reference volatile

@kwin : can you please review and merge

@abhinavsinha347 Thanks for the PR. Please also add a changelog entry according to https://github.com/Adobe-Consulting-Services/acs-aem-commons/blob/master/CONTRIBUTING.md.

Pull Request Test Coverage Report for Build 6371

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 56.305%

Totals

Change from base Build 6363:
0.0%

Covered Lines:
16566

Relevant Lines:
29422

💛  - Coveralls

@kwin done. When is the next release planned, as this is one of the feature we need to use for our client.


Decoupling from express, modernization/refactor, use context qsh

This PR makes a lot of changes I believe are beneficial. Sorry for the size.
Inline comments will explain it in more details

I forgot to update the README documentation and perhaps add some useful comments on interfaces, classes, and methods.

[] Update documentation
[] Add useful comments where relevant

PR is ready for review.


reproduce Mapillary val recall

Hi,
can youj tell me how to reproduce val recall? I try  get the val recall by val.py,but the result is bad.
global feature with pca(4096) and use weights mapillary_WPCA4096.pth.tar .
====> Recall@1: 0.4649
====> Recall@5: 0.5378
====> Recall@10: 0.5581
====> Recall@20: 0.5770
====> Recall@50: 0.6054
====> Recall@100: 0.6162
but in paper the the recall@1(Single-Spatial-Patch-NetVLAD)=77.2  and recall@1(NetVLAD)=60.8.
Could you tell me the some detail about reproduce  Mapillary val recall?
thanks

Hi @bixiaopeng0, thanks for flagging this issue with us. I suspect we have a bug in val.py, which is causing the low numbers. This will require extensive investigation, we will endeavor to fix the bug as soon as possible.

Hey @StephenHausler - quick reminder re this.

Hiya,
Sorry for taking so long to get back to you, @bixiaopeng0!
The reason why you do not get the same numbers as in the paper is that the https://github.com/QVPR/Patch-NetVLAD/blob/main/patchnetvlad/training_tools/val.py file does not properly calculate the recall values on the MSLS dataset. Instead, please use the official https://github.com/mapillary/mapillary_sls/blob/main/evaluate.py
You can obtain the predictions file for the cph and sf parts of the Mapillary dataset by using https://github.com/QVPR/Patch-NetVLAD/blob/main/feature_match.py
Then concatenate these two files, e.g. using cat:
cat PatchNetVLAD_predictions_cph.txt PatchNetVLAD_predictions_sf.txt > PatchNetVLAD_predictions_combined.txt

Now this file needs to be converted to a format suitable for the evaluate.py provided by the Mapillary authors. I just created a script to do that in https://github.com/QVPR/Patch-NetVLAD/blob/main/patchnetvlad/training_tools/convert_kapture_to_msls.py
Simply call it like so:
python ./convert_kapture_to_msls.py /path/to/PatchNetVLAD_predictions_combined.txt /path/to/PatchNetVLAD_predictions_combined_msls.txt

And then evaluate the performance:
python /path/to/mapillary_sls/evaluate.py --msls-root=/please/add/path --cities=cph,sf --prediction=path/to/PatchNetVLAD_predictions_combined_msls.txt

This leads to<EMAIL_ADDRESS>which is a bit better than what we state in the paper.
Closing here - let us know if you have more questions.


H7020 Wrong colors in HK / breaks colors in Govee app

What issue do you have? Please be as thorough and explicit as possible.
After adding the light bulbs in the Govee app and in homebridge, in HomeKit it is not possible to adjust the color normally. All settings result in wrong colors. The brightness adjustment also seems to show different values compared to the Govee app.
On top, after setting up the bulbs in the homebridge plugin, the color adjustment also slightly breaks in the Govee app. For example, orange will always be displayed as green. After deleting the plugin and resetting the bulb string lights (pressing the power button for some seconds) they work again fine in the app.
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?
Homebridge on Synology

Which version of Homebridge/HOOBS do you have?
v1.6.1

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
Synology DSM 7.1.1
Node.js 18.15.0

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
v9.4.1
Problem was always there, but I did just use the one previous version

Which Govee devices do you have that are causing issues? Please include product models if applicable.
H7020
Version 1.00.14
Hardware Version 3.01.01

Please paste any relevant logs below.

8/28/2023, 12:00:08 PM] [Govee] [LAN] client enabled and found 0 device(s).
[8/28/2023, 12:00:08 PM] [Govee] [HTTP] client enabled and found 1 device(s).
[8/28/2023, 12:00:08 PM] [Govee] [AWS] client enabled.
[8/28/2023, 12:00:08 PM] [Govee] [BLE] disabling client as Cannot find package '@abandonware/bluetooth-hci-socket' imported from /volume1/homebridge/node_modules/homebridge-govee/lib/platform.js at new NodeError (node:internal/errors:399:5).
[8/28/2023, 12:00:08 PM] [Govee] [LED Bulb String Lights] initialising with options {"adaptiveLightingShift":0,"aws":"enabled","ble":"disabled","brightnessStep":1,"colourSafeMode":false,"lan":"unsupported"}.
[8/28/2023, 12:00:08 PM] [Govee] [LED Bulb String Lights] initialised with id [DD:33:CD:38:32:30:28:1F] [H7020].
[8/28/2023, 12:00:10 PM] [Govee] ✓ Setup complete. This plugin has been made with ♥ by bwp91, please consider a ☆ on GitHub if you are finding it useful!
[8/28/2023, 12:00:40 PM] [Homebridge UI] [homebridge-govee] Terminating child process...
[8/28/2023, 12:00:40 PM] [Homebridge UI] [homebridge-govee] Child process ended
[8/28/2023, 12:01:19 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 56 51].
[8/28/2023, 12:01:20 PM] [Govee] [LED Bulb String Lights] current state [on].
[8/28/2023, 12:01:20 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 56 51].
[8/28/2023, 12:01:23 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 129 53].
[8/28/2023, 12:01:24 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 129 53].
[8/28/2023, 12:01:25 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 69 29].
[8/28/2023, 12:01:26 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 69 29].
[8/28/2023, 12:01:26 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 77 22].
[8/28/2023, 12:01:28 PM] [Govee] [LED Bulb String Lights] current colour [rgb 69 255 150].
[8/28/2023, 12:01:28 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 77 22].
[8/28/2023, 12:01:29 PM] [Govee] [LED Bulb String Lights] current colour [rgb 69 255 150].
[8/28/2023, 12:01:33 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 179 161].
[8/28/2023, 12:01:34 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 113 88].
[8/28/2023, 12:01:34 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 179 161].
[8/28/2023, 12:01:35 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 113 88].
[8/28/2023, 12:01:35 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 130 45].
[8/28/2023, 12:01:36 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 133 47].
[8/28/2023, 12:01:37 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 130 45].
[8/28/2023, 12:01:37 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 133 47].
[8/28/2023, 12:01:38 PM] [Govee] [LED Bulb String Lights] current colour [2300K / 434M].
[8/28/2023, 12:01:40 PM] [Govee] [LED Bulb String Lights] current colour [4100K / 244M].
[8/28/2023, 12:01:40 PM] [Govee] [LED Bulb String Lights] current colour [5600K / 178M].
[8/28/2023, 12:01:40 PM] [Govee] [LED Bulb String Lights] current colour [6500K / 154M].
[8/28/2023, 12:01:41 PM] [Govee] [LED Bulb String Lights] current colour [6700K / 149M].
[8/28/2023, 12:01:41 PM] [Govee] [LED Bulb String Lights] current colour [4100K / 244M].
[8/28/2023, 12:01:41 PM] [Govee] [LED Bulb String Lights] current colour [5600K / 179M].
[8/28/2023, 12:01:41 PM] [Govee] [LED Bulb String Lights] current colour [6500K / 154M].
[8/28/2023, 12:01:42 PM] [Govee] [LED Bulb String Lights] current colour [7000K / 143M].
[8/28/2023, 12:01:43 PM] [Govee] [LED Bulb String Lights] current colour [6700K / 149M].
[8/28/2023, 12:01:43 PM] [Govee] [LED Bulb String Lights] current colour [7000K / 143M].
[8/28/2023, 12:01:43 PM] [Govee] [LED Bulb String Lights] current colour [7100K / 140M].
[8/28/2023, 12:01:45 PM] [Govee] [LED Bulb String Lights] current colour [6700K / 150M].
[8/28/2023, 12:01:45 PM] [Govee] [LED Bulb String Lights] current colour [7100K / 141M].
[8/28/2023, 12:01:45 PM] [Govee] [LED Bulb String Lights] current colour [4700K / 211M].
[8/28/2023, 12:01:47 PM] [Govee] [LED Bulb String Lights] current colour [6700K / 149M].
[8/28/2023, 12:01:47 PM] [Govee] [LED Bulb String Lights] current colour [4500K / 223M].
[8/28/2023, 12:01:47 PM] [Govee] [LED Bulb String Lights] current colour [4700K / 213M].
[8/28/2023, 12:01:48 PM] [Govee] [LED Bulb String Lights] current colour [3100K / 322M].
[8/28/2023, 12:01:49 PM] [Govee] [LED Bulb String Lights] current colour [4500K / 222M].
[8/28/2023, 12:01:49 PM] [Govee] [LED Bulb String Lights] current colour [3100K / 323M].
[8/28/2023, 12:01:50 PM] [Govee] [LED Bulb String Lights] current colour [2000K / 497M].
[8/28/2023, 12:01:55 PM] [Govee] [LED Bulb String Lights] current brightness [91%].
[8/28/2023, 12:01:55 PM] [Govee] [LED Bulb String Lights] current brightness [100%].
[8/28/2023, 12:01:57 PM] [Govee] [LED Bulb String Lights] current brightness [91%].
[8/28/2023, 12:01:57 PM] [Govee] [LED Bulb String Lights] current brightness [100%].
[8/28/2023, 12:02:00 PM] [Govee] [LED Bulb String Lights] current brightness [61%].
[8/28/2023, 12:02:00 PM] [Govee] [LED Bulb String Lights] current brightness [60%].
[8/28/2023, 12:02:01 PM] [Govee] [LED Bulb String Lights] current brightness [61%].
[8/28/2023, 12:02:01 PM] [Govee] [LED Bulb String Lights] current brightness [60%].
[8/28/2023, 12:02:02 PM] [Govee] [LED Bulb String Lights] current brightness [86%].
[8/28/2023, 12:02:03 PM] [Govee] [LED Bulb String Lights] current brightness [86%].
[8/28/2023, 12:02:04 PM] [Govee] [LED Bulb String Lights] current brightness [54%].
[8/28/2023, 12:02:04 PM] [Govee] [LED Bulb String Lights] current brightness [55%].
[8/28/2023, 12:02:05 PM] [Govee] [LED Bulb String Lights] current brightness [54%].
[8/28/2023, 12:02:05 PM] [Govee] [LED Bulb String Lights] current brightness [85%].
[8/28/2023, 12:02:05 PM] [Govee] [LED Bulb String Lights] current brightness [55%].
[8/28/2023, 12:02:06 PM] [Govee] [LED Bulb String Lights] current colour [rgb 255 44 41].
[8/28/2023, 12:02:07 PM] [Govee] [LED Bulb String Lights] current brightness [85%].

Hi @esrauscht
You may need to adjust the commands that the plugin sends for this device.
Everything is explained a bit more on this wiki post:
https://github.com/bwp91/homebridge-govee/wiki/Common-Errors
This may be what is causing the issues


ci(deploy): render doc cfg for cache & lavalink

cache-in-memory used the wrong nightly feature and lavalink was missing the feature entirely.
I also took the time to simplify the build-docs and deploy-docs jobs' Build docs step (the previous workaround was required due to a compile_error! invokation when multiple TLS backends were enabled at the same time).

For this I wish we could have a live preview of the docs cause I don't have the target to see for myself

That would be a great addition! For now you can execute the CI steps locally with my patch and diff against api.twilight.rs

Like I said I don't have a target, I can't compile simd


reduced genome and enz_file

Hi Ramya,
I come back to you with questionning about the reduced genome that is now included in the createR4CkerObject function. In a previous version of your package, the enz_file was not required. Could you comment and that point?
My concern is that there is basically 2 ways to conduct the mapping: your way i.e. mapping experiment directly on the reduced genome and the second which consist of first mapping experiment on full genome and filter it to the reduced genome. The last strategy is the one I have adopted and I am worry about the consequence of this "enz_file" fork in your package.
Could you please add either the mm10_hindiii_flanking_sequences_25_unique.fa file or the enz_file to you data folder so that one can reproduce your example experiments?
Thank you,
Nadia

Hi,
The reason I added it was to check the QC of the 4C samples. One of the criteria is to have >40% coverage in the region surrounding the bait. You can substitute this with a file containing the fragments for your primary restriction enzyme.

And yes I can add the enz_file to the data folder.

Hi Ramya,
Thank you for the explanation.
Thank you for putting the enz_file from your examples.
Best,

mm10_hindiii_flanking_sites_25_unique_2.bed.gz


As a developer, I need to fix bug in node ledger service which causes staged ledger hash mismatch when applying subsequent empty blocks

We index staged ledgers by mask hash. Problem is that when applying an empty block, without coinbase transaction, mask hash stays the same as no account is updated in there. Instead scan state ParallelScan::curr_job_seq_no is incremented, which causes aux_hash to change. So we need to index staged ledgers by mask hash and aux hash.

It has long been fixed now, since using staged ledger hashes for ledger indexing.


{{ site.baseurl }} Not evaluated then running simulator, causes style and urls to be broken

See this screenshot:

Hi @dingobar, to my knowledge the Simulator and the examples are the only things intended for you to be running locally. Everything else is just for the hosted GitHub pages and is built with Jekyll. If you need to run the pages locally you can follow this guide.
-Keshia


Allow env_inherit values to be added or overridden.

Added env_inherit to bazel_integration_test and bazel_integration_tests to allow the env_inherit values to be overridden.
Added additional_env_inherit to bazel_integration_test and bazel_integration_tests to allow additional env_inherit values to be specified.

I am going to finish this in another PR.


ENABLE_JAVASCRIPT_CONTROLS use

Bug description
I have Superset 2.1.3 in production and I would like to upgrade to 4.0.2, however a feature that works great in 2.1.3 has been deprecated in 4.0.2, the feature is the option to use JS code in maps, that is:
ENABLE_JAVASCRIPT_CONTROLS
Therefore I would like your help to find an alternative and be able to solve this problem.
How to reproduce the bug
Upgrade from Superset 2.1.3. to 4.0.2
Screenshots/recordings
The map look like this in superset 2.1.3:

In the newest supeset look equal, but when I place the mouse cursor over the map this happend:

I mean this:
An error occurred while rendering the visualization: Error: Minified React error #31; visit https://reactjs.org/docs/error-decoder.html?invariant=31&args[]=EvalError%3A%20Refused%20to%20evaluate%20a%20string%20as%20JavaScript%20because%20'unsafe-eval'%20is%20not%20an%20allowed%20source%20of%20script%20in%20the%20following%20Content%20Security%20Policy%20directive%3A%20%22script-src%20'self'%20'strict-dynamic'%20'nonce-7ZywRWntR57icaAOAZiKN_Qp24uqef_N'%22.%0A&args[]= for the full message or use the non-minified dev environment for full errors and additional helpful warnings.

Superset version
4.0.2
Python version
3.9
Node version
16
Browser
Chrome
Additional context
This feature is really important to my users so I'll be so thankful if you could help me with this.
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Likely due to Talisman, please refer https://github.com/apache/superset/issues/25871#issuecomment-1967064535

Thank you very mucho dear @harshit2283, your example allow me to solve my problem, only that in my case I'm in superset 4.0.2 so the two changes where made in the same file.


Does ROS2_Rust support .srv code generation?

Hello,
I would like to define a user type for client/service nodes, but I don't see how to generate the code for a .srv

You should be able to just create a package containing your .srv like you would for C++ or Python, and follow https://github.com/ros2-rust/ros2_rust/blob/main/docs/building.md. Does that not work?
cc @ros2-rust/dev

I didn't know it worked that way. Everything is working fine, thank you!

Okay, great!


riak_kv_vnode:put() should use even-more-unreliable command

Bring one patch, commit c927c7f, from PR #1009 forward to develop,
to fix a bug in put FSM processing when sending the put vnode op to
a node that isn't the coordinator blocks due to busy_dist_port
status.
cc: @jonmeredith @lordnull

Can one of the admins verify this patch?


add resource type into method's summary

First step to fixes https://github.com/Azure/autorest.csharp/issues/3650. add resource type into method's summary
Checklist
To ensure a quick review and merge, please ensure:

[ ] The PR has a understandable title and description explaining the why and what.
[ ] The PR is opened in draft if not ready for review yet.

If opened in draft, please allocate sufficient time (24 hours) after moving out of draft for review

[ ] The branch is recent enough to not have merge conflicts upon creation.

Ready to Land?

[ ] Build is completely green

Submissions with test failures require tracking issue and approval of a CODEOWNER

[ ] At least one +1 review by a CODEOWNER
[ ] All -1 reviews are confirmed resolved by the reviewer

Override/Marking reviews stale must be discussed with CODEOWNERS first

default api-version


Support Go 1.11 modules

closes #15

Coverage remained the same at 97.952% when pulling 6f28b9af0ce0c236503b70005e439852e68661f7 on issue-15 into 77a408a1aca4ae880fcff532f8f9c96ea59fce51 on master.


How to show tooltip data on tap and drag in v0.40.0 like with v0.36.3?

Love that the new update lets us handle touch events, but I am a bit unclear on how to reproduce the old functionality where touching a graph and dragging around (no long press required) would display the tooltip for the current touch point.
After this change it appears to only show you the initial touch point.
Any help here is appreciated!

Hi @TheMeanCanEHdian
Everything should work like before on touch handling. We just added support for long-press.
Can you explain a little more about the problem? Is it reproducible in our samples?
If you can please provide me a reproducible code.
Thanks!

Sure thing. I have created a repo for fl_chart 36.4 and 40.0 where I introduced 2 changes to the example code.

I commented out all pages but the LineChartPage
I added fl_chart to the pubspec

On 36.4 pressing and dragging will update the tooltip, but on 40.0 you have to long press to achieve this.
Here are GIFs of the behavior
36.4

40.0

Any thoughts on this?

Yes. when you long-press on a chart, the parent's scroll will be locked. Then chart will receive the touch events.

Is there a way to eliminate the need for a long press before touch events, and revert back to the previous behavior of immediate touch events when swiping over data in a graph?


How to use kata-container runtime with k8s cluster

Which feature do you think can be improved?
Specify the feature you think could be made better.
How can it be improved?
Describe how specifically you think it could be improved.
Additional Information
Anything else to add?
Before raising this feature request
Have you looked at the limitations document?

Hi @ravvy00, here is a guide that can help you: https://github.com/kata-containers/documentation/tree/master/how-to#kubernetes-integration
Let us know if you have any question.

Closing this issue since Salvador provided an answer.

Closing this issue since Salvador provided an answer.


Configuration - Could not retrieve or read configuration (ConfigurationError)

Just checking my speeds, system has been running since early november 22 with no issues.  On the 13-Jan, last Friday it stopped working and is returning a error.
This was the first error raised.  The hour before it worked fine.
{"type":"log","timestamp":"2023-01-13T20:00:13Z","message":"Configuration - Could not retrieve or read configuration (ConfigurationError)","level":"error"}
Except for the date/time the same error was generated every hour since then.
Interestingly the system reports the container was updated 7 days ago, on the 13th.   I've changed nothing, the .env file is readable both on the NAS and inside the container.  The Containers are running OK and the Internet is working fine.
I've restart the containers.  I even remove the volume link to config so it used the container one only.  I wiped the containers and reloaded the images. No difference.
Any ideas?

@Bag72 you ran into the new reporting on failures feature, try changing the server you speedtest against.

I've not chosen a server.  I leave the field blank to let it select the best server as it says in the field.
I click the drop down and there is nothing there and if I type something in the field, like google.com, it fails with a Server 500.

Yeah that's because google.com wouldn't be an accurate server ID. From the container make sure it has access to the internet but pinging google with ping google.com and making sure there is no packetloss and/or the connection is successful.
In the server field the IDs should only be valid Speedtest Server id's from the search feature or that you've manually entered in integer form.

Alex,  Thanks for the quick responses.
I can access the internet fine from the host.   Not sure what to do from inside the container to test it has a link though.
As I said I don't have anything in the dropdown for the server list and so I typed in the IP and server id for the last successful link.
Funnily enough I noticed that I had one successful connection yesterday at 1400.  Just the one since it stopped working.
So how do I enter server ids,  what are valid server ids that I could use and why is is not picking up some as before when I don't enter anything as in 'Leave empty to let the system pick the best server.'   It is clearly picking invalid servers.

Update : Although inside the container I couldn't ping or wget, curl worked fine so I was able to pull something down from within the container.  It also has internet access.

Hello,
First, many thanks for this project.
Then, exact same issue here. There is no way to add a server Id in the field. I only get a "500 | Server Error" message, whatever the id number or server address I put in the field. The problem started after I've upgraded to the last version... Any further test idea is welcome

Hello,
First, many thanks for this project.
Then, exact same issue here. There is no way to add a server Id in the field. I only get a "500 | Server Error" message, what ever the id number or server address I put in the field.

Clearly not everyone is hitting this.  I've rebuilt the docker again but not wiped the DB.   The config area has the .env in it.   Should I just delete the lot and lose all my data or is there a way I can reset the server ids and move on.
Is there anything I can try?

If you use something like dbeaver you can open the SQLite DB or others. You can then go into the settings table and modify the server listing.
Obviously make sure to take a backup before doing so.
If dbeaver gives you issues for sqlite there are other ide's you can use

Alex, I have no idea what to change in the DB so that doesn't help me.  Do you have more detailed instructions?
It looks to me that I may as well wipe all my data and start again.   I can do this if necessary but would prefer not to lose my data.   Do you know what happened so it won't happen again?

Alex, I'm going to reinstall from scratch wiping all my data.  I'm actually already using Maria DB as I used your docker-compose file to get it going and I've several Maria and MySQL instances and none of those have been corrupted.
I am convinced it is something in the last build you released.  It died immediately after that was applied.  Funny it only happened to a few people.  Maybe I'll skip the upgrades unless there are major changes.

Well that didn't go well.   I stopped the containers, wiped everything, after making a backup, and even deleted the images so it would have to download.     Same situation.  No ids in the dropdown and the system complains about the configuration file again.
I'm now going to try a previous version, although never done this before, to take me back to the previous working version.  Let you know how that goes.

If you go into the container's terminal try running php artisan migrate --force and see if anything happens. Hint: nothing should. It should say "no migrations" or something to that effect.
If that doesn't work and you want a fresh install at the DB layer try php artisan app:install --force, WARNING: it will reset everything!

The first cli line said 'Nothing to Migrate' as you suspected.  The second one went through an initialisation script which wiped the DB but it still did not work.   Same configuration error.
I also tried previous versions of the docker containers and none of them worked.  I even tried it without the data being mapped to a volume outside the container.  Nothing got exactly the same configuration error.  I'm guessing that there are several failures at the start that show up as configuration errors as I am now beginning to suspect that it is reading the file fine but hitting an error with a DNS resolution or something and it simply displays that as an error.
Anything else I can run to identify the issue?

Can you get the logs from when the docker container starts?

speedtest-tracker.log
Im getting similar issues. I have pasted my log from docker-compose
_speedtest-tracker_logs.txt

My log files.
DC Up.txt is the logs generated on the console at startup then it sits and waits
DC Up.txt
DC_Log_Test.txt is where I connect to the GUI and trigger a queued job
DC Log Test.txt

Alex,   Brian @AwesomeOpenSource on YouTube has just released a video on this software.  Watching it I realised that I had not seen that version before.   So it appears that I have been running the same version since early November.   Which made me think my config file might be missing some key changes that the latest version needs.  Hence the config issue.
So I wiped everything in the shared directories, the .env file, the Maria DB files and wiped the docker images I had downloaded.  Funnily enough deleting the latest version of the image crashed my NAS and it took a bit of fiddling, and a few crashes, to remove the image.  Eventually, it was a clean system with no speedtest data at all and no old container images.   I then performed docker-compose up and it downloaded the latest image and it came up working.   I then brought it down, reloaded the MariaDB databases and tried again and it stayed working so I have my data as well.   Fantastic, Win Win.
So mine is fixed.   Not sure what I did as I had already rebuilt without the .env.  Perhaps my downloaded version was corrupt.  It did start when it was upgraded and brought my system down removing it and now it is gone it worked when I downloaded the latest version.  I'm not sure tbh.
However, love the new version. you have made so many improvements.  I'm impressed.  Thank you for your help on this.

I realised that I had not seen that version before.

so you were using the old ST project with instructions taken from this new project? Didn't you see the screenshots in the documentation?
This could explain why other users are having issues, they're mixing projects. :)

No, I was not mixing projects.  I meant an older version of the 'alexjustesen/speedtest-tracker' docker image which is now 0.11.   I loaded it up with docker compose in November and think I was on 0.6.1 or something close having looked through them all.   Now I have 0.11 installed and working.

You wrote yesterday:

So what did you mean by "latest"?

I meant build v0.11 being the latest build.

So you were not using the old version...

Just because another product is available that you mistakenly thought I was using doesn't change the fact that v0.6 is an older version of this product.   You understand what I meant by old version after I clarified it.  Who cares?  It's not a big deal.
For the record I've not even tried the other guys version.  This is the first and only one I tried and it does everything I want and he hasn't even finished his plans yet..

You said you updated to latest version and it didn't work. After a while you said everything was fixed, because you were simply using a very old version (0.6). I see some contradictions. :)
But you're correct on one thing: who cares...let's not waste more time on a non-existent issue.
Good luck. And please close the issue if you're ok now.

  :)
I was leaving it open because others were having similar issues and although I now believe my issue was my own system being corrupt somehow others may have different view.
I'm happy to close it.    Thanks again for the help.

Glad the video helped! I saw it too because I noticed a big jump in stars over the last couple of days


Merge pull request #1 from spring-projects/master

upgrade

@AzalKhan please use your own fork to test Github's PR features.


Failed to build

Error message:
[ 12%] Building CXX object CMakeFiles/hpenc.dir/src/aead.cc.o
In file included from /usr/include/c++/7.1.1/memory:80:0,
from /home/xxxx/hpenc/src/aead.h:26,
from /home/xxxx/hpenc/src/aead.cc:29:
/usr/include/c++/7.1.1/bits/unique_ptr.h: In instantiation of ‘void std::default_delete<_Tp>::operator()(_Tp*) const [with _Tp = evp_cipher_ctx_st]’:
/usr/include/c++/7.1.1/bits/unique_ptr.h:268:17:   required from ‘std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp = evp_cipher_ctx_st; _Dp = std::default_delete<evp_cipher_ctx_st>]’
/home/xxxx/hpenc/src/aead.cc:77:19:   required from here
/usr/include/c++/7.1.1/bits/unique_ptr.h:76:22: error: invalid application of ‘sizeof’ to incomplete type ‘evp_cipher_ctx_st’
static_assert(sizeof(_Tp)>0,
^
make[2]: *** [CMakeFiles/hpenc.dir/build.make:63: CMakeFiles/hpenc.dir/src/aead.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:68: CMakeFiles/hpenc.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
ArchLinux: gcc 7.1.1, OpenSSL 1.1.0f (probably because of this).
Thanks.

[ 12%] Building CXX object CMakeFiles/hpenc.dir/src/aead.cc.o
In file included from /usr/include/c++/6/memory:81:0,
from /root/hpenc/src/aead.h:26,
from /root/hpenc/src/aead.cc:29:
/usr/include/c++/6/bits/unique_ptr.h: In instantiation of 'void std::default_delete<_Tp>::operator()(_Tp*) const [with _Tp = evp_cipher_ctx_st]':
/usr/include/c++/6/bits/unique_ptr.h:239:17:   required from 'std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp = evp_cipher_ctx_st; _Dp = std::default_delete<evp_cipher_ctx_st>]'
/root/hpenc/src/aead.cc:77:19:   required from here
/usr/include/c++/6/bits/unique_ptr.h:74:22: error: invalid application of 'sizeof' to incomplete type 'evp_cipher_ctx_st'
static_assert(sizeof(_Tp)>0,
^
CMakeFiles/hpenc.dir/build.make:62: recipe for target 'CMakeFiles/hpenc.dir/src/aead.cc.o' failed
make[2]: *** [CMakeFiles/hpenc.dir/src/aead.cc.o] Error 1
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/hpenc.dir/all' failed
make[1]: *** [CMakeFiles/hpenc.dir/all] Error 2
Makefile:127: recipe for target 'all' failed
make: *** [all] Error 2
Getting the same error on Debian Stretch
libssl-dev/stable,stable,now 1.1.0f-3+deb9u2
libsodium-dev/stable,now 1.0.11-2 amd64
I am running
cmake .
make


[GSSOC'23] Absence of Screenshots or working videos

Describe the bug ✍
All the README.md files in the games of this repository lack proper screenshots and working videos of the games.
I would like to add screenshots and working videos for all the games in this repository.
@Atharva-3000 Please assign me this issue under GSSoC'23
Provide step by step information reproduce the bug 📄
I will run all games on my system and provide proper screenshots and working videos for all the games and add them to the README.md files.
That way it would look more attractive.
Select program in which you are contributing
GSSoC23
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

Hey @PoulasthaMukherjee !
Thank you for raising an issue 💗
You can self assign the issue by commenting /assign in comment 😀
Make sure you follow CODE OF CONDUCT and CONTRIBUTING GUIDELINES 🚀
Don’t Forget to ⭐ our GameZone🎮
Make sure you join our Discord🕹

Hey @PoulasthaMukherjee! 🙂
It seems like you are not following proper guidelines !! 👀
Read documentation properly !!🙏
If you have any queries reach out to us on Discord🕹 .

Hey @PoulasthaMukherjee ! Thank you so much for your raising the issue💗
It’s all yours, you can come anytime again and make some contributions! 🚀
Alone, we can do little, but together we can do so much! 😇

What seems to be the issue?


Component audit

An extensive component audit must be performed before entertaining a v1 release.
Identify non-reactive props
Issues #343 , #234
Identify inconsistent or confusing prop/value nomenclature

size values are inconsistent (e.g. "small" vs."sm", undefined vs. "default")
ambiguous prop value (For PaginationNav, the page prop is an index value while in Pagination the same prop represents the current page number)
"is it slottable?" - make prop names more semantic (e.g. "labelText" must be a string while "label" signifies that it can be slottable)

Identify feature delta compared to flagship Carbon Design System
The basic expectation is that components from the library are compatible with the latest CSS from carbon-components.
What features are missing compared to their counterparts in the flagship Carbon library?

I'd recommend also taking a look at the breakpoints for the UIShell when you have both a sidebar and navigation items, as at larger width it shows both

( not trying to pile on, and I'm finding work-arounds by using the DOM API - so it's not a blocker for me, but better to report I assume )
Spotted this also Dropdown selectedIndex also is not reactive.

@orta I'll open separate issues for those

Should Toggle and ToggleSmall be a configurable Toggle ?

@ispyinternet I agree. Besides the size, Toggle and ToggleSmall are pretty much identical. Related https://github.com/carbon-design-system/carbon/issues/6653


pnpm don't install tarball when run pnpm install

{
  "private": true,
  "name": "pnpm-test",
  "devDependencies": {
    "bootstrap": "https://github.com/twbs/bootstrap/archive/6ec9aa34a4b6d43b593b97f9b207410eff8f0152.tar.gz"
  }
}

Run pnpm install. It exit without an error. No file was downloaded
  pnpm:install installing bootstrap@https://github.com/twbs/bootstrap/archive/6ec9aa34a4b6d43b593b97f9b207410eff8f0152.tar.gz +0ms
  pnpm:mkdirp /home/khoa/web/pnpm-test/node_modules/.store +32ms
  pnpm:symlink /home/khoa/web/pnpm-test/node_modules/.tmp/dff843d5-8c00-45b8-a3f3-03770d3ab463 -> /home/khoa/web/pnpm-test/node_modules/.store/6ec9aa34a4b6d43b593b97f9b207410eff8f0152#864578030e98551c4bed7d221b20b5c6255c44fa +4ms
  pnpm:symlink /home/khoa/web/pnpm-test/node_modules/.tmp/dff843d5-8c00-45b8-a3f3-03770d3ab463 -> /home/khoa/web/pnpm-test/node_modules/.store/6ec9aa34a4b6d43b593b97f9b207410eff8f0152#864578030e98551c4bed7d221b20b5c6255c44fa +2ms
  bootstrap https://github.com/twbs/bootstrap/archive/6ec9aa34a4b6d43b593b97f9b207410eff8f0152.tar.gz queued ↓
  pnpm:mkdirp /home/khoa/web/pnpm-test/node_modules/.store +5ms
  pnpm:mkdirp /home/khoa/web/pnpm-test/node_modules/.tmp/dff843d5-8c00-45b8-a3f3-03770d3ab463/_ +0ms
  pnpm:http bootstrap@https://github.com/twbs/bootstrap/archive/6ec9aa34a4b6d43b593b97f9b207410eff8f0152.tar.gz +5ms [stream]

not sure in which version it was implemented but it works as of v0.31.0


Dynamic module import seems to be causing error

My dev dependencies:
{
    "@nuxt/devtools": "^0.5.5",
    "@nuxtjs/tailwindcss": "^6.4.1",
    "@vitest/coverage-c8": "^0.31.3",
    "nuxt": "^3.5.2",
    "nuxt-vitest": "0.8.2",
    "tailwindcss": "^3.3.2",
    "vitest": "^0.31.3"
  }

The app is building fine, but trying to start Vitest is causing the following error:
ERROR  Only URLs with a scheme in: file and data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'
It seems to be breaking down on const { startVitest } = await import(await resolvePath("vitest/node")); in module.mjs
Is anyone else experiencing this issue with the latest version of Nuxt or is it just me?

Thank you @danielroe! That solved my issue with module dynamic module resolution.
I am running into another issue now though, and I'm not sure if it should be under a new issue or if its still related some how.
I can't seem to be able to view the GUI now.

Let's make it a new issue. 👍


AD Connect Agent Update question

I posted this but got no reply:
my questions are:
Am I OK to install the required software for Azure Active Directory Password Protection on both my DC and member servers?
Would the version of Microsoft Azure AD Connect Agent Updater conflict with the version to be installed by the Azure AD Password Protection DC agent and Azure AD Password Protection Proxy ?

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

ID: 23e000f0-84ce-7ec7-e5ed-4bd9c49f5d49
Version Independent ID: e636b9d1-be81-0f00-97c4-ff4fa9078be3
Content: Deploy on-premises Azure AD Password Protection
Content Source: articles/active-directory/authentication/howto-password-ban-bad-on-premises-deploy.md
Service: active-directory
Sub-service: authentication
GitHub Login: @Justinha
Microsoft Alias: justinha

@ii-batman
Thanks for your feedback! We will investigate and update as appropriate.

@ii-batman
Thank you for your time and patience throughout this issue and I apologize for such a delayed response on your Q&A thread.
Based off your issue, I'll summarize it for my knowledge, and to make sure I correctly understand your issue.
Goal:
-You want to install Azure AD Password Protection
Scenario:
-Your DC has the Authentication Agent installed for PTA
-This Auth Agent also installed the Microsoft Azure AD Connect Agent Updater service (version 1.5.1742.0)
Issue:
-The Microsoft Azure AD Connect Agent Updater documentation has a warning stating:

Azure AD Password Protection proxy and Azure AD Application Proxy install different versions of the Microsoft Azure AD Connect Agent Updater service... These different versions are incompatible when installed side by side and doing so will prevent the Agent Updater service from contacting Azure for software updates, so you should never install Azure AD Password Protection Proxy and Application Proxy on the same machine.

Since your Authentication Agent installed the Updater service, this is essentially the same scenario as the above warning. Which is why you want to make sure you can install the Azure AD Password Protection agent on your DC and member servers.
Because this GitHub issue isn't related to our documentation, I'll go ahead and close this out. However, I've reached out to our engineering team regarding this and will update your Q&A thread as soon as possible.
If you have any other questions or if I incorrectly summarized your issue, please let me know.
Thank you for your time and patience throughout this issue.

Hi @JamesTran-MSFT  and thank you for your email, this was the most well written and well-structured emails I came across in a long time. 😃
Thanks also for pushing the case to your devs - appreciated.

@ii-batman
Thank you for working with me on your Q&A post!
I received a response from our engineering team and "there wont be any problems having proxy & PTA agent on the same server."
If you have any other questions, please let me know.
Thank you for your time and patience throughout this issue.

@ii-batman
Thank you again for your time and patience throughout this issue.
I've created a PR to update the documentation and it's currently waiting for the author to review and sign off. In the meantime, feel free to double check my PR and if I missed anything or worded it incorrectly, please let me know.

Please allow some time for the author to review and the changes to reflect.
Thank you again!


[Do Not Merge] CORTX-28919 : RGW: add motr trace paramater in rgw config file

Signed-off-by: Sachitanand Shelake<EMAIL_ADDRESS>Problem Statement

Problem statement

Design

For Bug, Describe the fix here.
For Feature, Post the link for design

Coding
Checklist for Author

[ ] Coding conventions are followed and code is consistent

Testing
Checklist for Author

[ ] Unit and System Tests are added
[ ] Test Cases cover Happy Path, Non-Happy Path and Scalability
[ ] Testing was performed with RPM

Impact Analysis
Checklist for Author/Reviewer/GateKeeper

[ ] Interface change (if any) are documented
[ ] Side effects on other features (deployment/upgrade)
[ ] Dependencies on other component(s)

Review Checklist
Checklist for Author

[ ] JIRA number/GitHub Issue added to PR
[ ] PR is self reviewed
[ ] Jira and state/status is updated and JIRA is updated with PR link
[ ] Check if the description is clear and explained

Documentation
Checklist for Author

[ ] Changes done to WIKI / Confluence page / Quick Start Guide

@andriytk , @madhavemuri  could you please suggest any other parameters needs to be added in ceph.conf file ?

will add this as a part of ongoing PR.hence closing this


Bug: Angular CLI test running module build/chrome concurrently

Bug Report or Feature Request (mark with an x)
- [x ] bug report -> please search issues before submitting
- [ ] feature request

Versions.
"dependencies": {
"@angular/animations": "4.3.1",
"@angular/common": "4.3.1",
"@angular/compiler": "4.3.1",
"@angular/core": "4.3.1",
"@angular/forms": "4.3.1",
"@angular/http": "4.3.1",
"@angular/platform-browser": "4.3.1",
"@angular/platform-browser-dynamic": "4.3.1",
"@angular/router": "4.3.1",
"core-js": "2.4.1",
"rxjs": "5.1.0",
"zone.js": "0.8.5"
},
"devDependencies": {
"@angular/cli": "1.3.1",
"@angular/compiler-cli": "4.3.1",
"@types/jasmine": "2.5.38",
"@types/node": "6.0.60",
"codelyzer": "2.0.0",
"jasmine-core": "2.5.2",
"jasmine-spec-reporter": "3.2.0",
"json-server": "0.9.6",
"karma": "1.4.1",
"karma-chrome-launcher": "2.0.0",
"karma-cli": "1.0.1",
"karma-coverage-istanbul-reporter": "0.2.0",
"karma-jasmine": "1.1.0",
"karma-jasmine-html-reporter": "0.2.2",
"karma-junit-reporter": "1.2.0",
"karma-remap-istanbul": "0.6.0",
"protractor": "5.1.0",
"ts-node": "2.0.0",
"tslint": "4.5.0",
"typescript": "2.2.0"
}
node: 6.10.1
os: linux x64 (Bash on Ubuntu)
Repro steps.

I'm trying to run tests with following:
"ng test -cc --single-run=true"
In v.1.0.0, when doing ng test, the tests will do the following in serial order:

Build modules
Start chrome
Start the test suite

In v.1.3.1, the tests starts Chrome at the same time it starts to build the modules,
it tries to build modules and start Chrome concurrently. The result of this is that Chrome is waiting too long,
resulting in a "Chrome have not captured in 60000 ms, killing."-error.
The log given by the failure.

ng test -cc --single-run=true
0% compiling 10% building modules 0/1 modules 1 active ...
.... module building....
active                                     71% sealing 72% optimizing 73% basic module optimization       74% module optimization 75% advanced module optimization     76% basic chunk optimization 76% basic chunk optimization pass 2 76% basic chunk optimization pass 3              77% chunk optimization 78% advanced chunk optimization 79% module and chunk tree optimization         80% chunk modules optimization 81% advanced chunk modules optimization                     82% module reviving 83% module order optimization    84% module id optimization         85% chunk reviving 86% chunk order optimization    87% chunk id optimization               88% hashing 89% module assets processing  90% chunk assets processing 91% additional chunk assets processing                          92% recording 91% additional asset processing    92% chunk asset optimization       94% asset optimization11 09 2017 13:23:46.394:WARN [launcher]: Chrome have not captured in 60000 ms, killing.
           95% emitting             11 09 2017 13:23:50.802:INFO [launcher]: Trying to start Chrome again (1/2).
11 09 2017 13:23:58.517:INFO [Chromium 59.0.3071 (Ubuntu 0.0.0)]: Connected on socket lEAXE18XTbsYhWwIAAAA with id 21814804
11 09 2017 13:24:09.216:WARN [Chromium 59.0.3071 (Ubuntu 0.0.0)]: Disconnected (1 times), because no message in 10000 ms.
Chromium 59.0.3071 (Ubuntu 0.0.0) ERROR
Disconnected, because no message in 10000 ms.
Chromium 59.0.3071 (Ubuntu 0.0.0) ERROR
Disconnected, because no message in 10000 ms.
Chromium 59.0.3071 (Ubuntu 0.0.0) ERROR
Disconnected, because no message in 10000 ms.
Chromium 59.0.3071 (Ubuntu 0.0.0) ERROR
Disconnected, because no message in 10000 ms.
11 09 2017 13:24:11.505:WARN [launcher]: Chrome was not killed in 2000 ms, sending SIGKILL.
npm ERR! Linux 4.4.0-62-generic
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run-script" "test-coverage"
npm ERR! node v6.10.1
npm ERR! npm  v3.10.10
npm ERR! code ELIFECYCLE
npm ERR!  : ng test -cc --single-run=true
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the   test-coverage script 'ng test -cc --single-run=true'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the ngflash-webgui package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     ng test -cc --single-run=true
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs ngflash-webgui
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls ngflash-webgui
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!      /npm-debug.log
:ngTestCoverage FAILED
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':ngTestCoverage'.

Process 'command 'npm'' finished with non-zero exit value 1

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED
Total time: 6 mins 36.346 secs
Desired functionality.

Finishing running module build before executing Chrome in order to avoid time out.
Mention any other details that might be useful.

Older working package dependencies with previous version 1.0.0:
"dependencies": {
"@angular/animations": "4.0.0",
"@angular/common": "4.0.0",
"@angular/compiler": "4.0.0",
"@angular/core": "4.0.0",
"@angular/forms": "4.0.0",
"@angular/http": "4.0.0",
"@angular/platform-browser": "4.0.0",
"@angular/platform-browser-dynamic": "4.0.0",
"@angular/router": "4.0.0",
"core-js": "2.4.1",
"rxjs": "5.1.0",
"zone.js": "0.8.5"
},
"devDependencies": {
"@angular/cli": "1.0.0",
"@angular/compiler-cli": "4.0.0",
"@types/jasmine": "2.5.38",
"@types/node": "6.0.60",
"codelyzer": "2.0.0",
"jasmine-core": "2.5.2",
"jasmine-spec-reporter": "3.2.0",
"json-server": "0.9.6",
"karma": "1.4.1",
"karma-chrome-launcher": "2.0.0",
"karma-cli": "1.0.1",
"karma-coverage-istanbul-reporter": "0.2.0",
"karma-jasmine": "1.1.0",
"karma-jasmine-html-reporter": "0.2.2",
"karma-junit-reporter": "1.2.0",
"karma-remap-istanbul": "0.6.0",
"protractor": "5.1.0",
"ts-node": "2.0.0",
"tslint": "4.5.0",
"typescript": "2.2.0"
}

Hi @SelfishLucho,
I cannot seem to be able to reproduce this issue with the CLI 1.4.1 (latest version). Could you either try with that version, or provide a project where we could reproduce and investigate?
I'll keep this alive for a few days to wait for your answer.
Thanks!

Hi @hansl,
I tried with version 1.4.1 and it didn't work out, however stumbled into this thread and added the flag --sourcemap=false. Still the same behavior as originally but this time it actually ran through the tests successfully, did this give any hints on why this could be?
Let me figure out to reproduce this on a separate project...

I have the same issue.
ng test --single-run results in Disconnected, because no message in 1000ms errors.
ng test --single-run --sourcemap=false  runs all the tests just fine
Oddly enough, ng test works fine too. It just seems to be --single-run causing the problem?

@hansl You can view this behaviour from a new project created using the CLI.  Running ng test will start both the webpack process and the browser at the same time.
INFO [launcher]: Starting browser Chrome
 25% building modules 133/144 modules 11 active ...s/modules/core.get-iterator-method.js

If you're application if large enough then you will run into the following
WARN [launcher]: Chrome have not captured in 60000 ms, killing.
WARN [launcher]: Chrome was not killed in 2000 ms, sending SIGKILL.

As a workaround you can add a retry to the karma.conf.js to be able to eventually run the browser after webpack finishes.
module.exports = function (config) {
    config.set({
        /* the rest of it */
        retryLimit: 5
    });
};

Ideally the broswer shouldn't be launched until after wepack finishes

@webstp I've been having this issue for the past 24 hours. I tried your workaround with the retryLimit property set to 5, but it still fails.

I'm getting that error message in CircleCI "Chrome have not captured in 60000 ms, killing."
My circle is set for version 1, and this is the test section in circle.yml, which is what is suggested in the angular cli docs:
test:
  override:
    - xvfb-run -a npm run test -- --single-run --no-progress --browser=ChromeNoSandbox

I also tried updating the version of Chrome that circle runs (45), to the latest version (61), but that didn't change the outcome.

Looks like the issue is with Karma:
https://github.com/jasmine/jasmine/issues/1327
tl;dr try changing the jasmine-core version to 2.5.2, and or changing all beforeEach(() => to beforeEach(async(() =>. I've tried both together and it's still getting that error.

I mentioned before that ng test --single-run --sourcemap=false worked. After many weeks of working fine, it has now quit working and broke all our CI builds :(
I've used git log any changes to our package.json file and I can't seem to find anything would break the unit testing functionality. I guess my version numbers in package.json aren't strict enough?
As before, ng test --single-run  doesn't work.
ng test still works.

Regarding my previous comment, it looks like if I have ng serve running in another terminal window, ng test --single-run --sourcemap=false will fail, too. If I stop the ng serve process,  ng test --single-run --sourcemap=false works great.

I should also mention that running ng-test --single-run, seems to launch a chrome window with the correct URL (and the tests look like they run in the browser window), but the console application cannot communicate with Chrome, apparently.

I created a repo that reproduces this issue. Please try to run ng test --single-run with it; see if you get the same error.
https://github.com/jongunter/ng-cli-test-issue-repro

You could try debugging this issue in the browser. There is more information being logged in into the console than in the terminal

Everything was working fine for me until a few day ago this issue appeared. Maybe something with Chrome? My Chrome version is 63.0.3239.13 is it possible that this has something to do with latest Chrome update?

We are seeing the same issue with a code-base with ~4000 Jasmine tests.
Depending on the build machine hardware the default captureTimeout may not be enough.
The problem is also harder to troubleshoot because the angular compilation progress is reported using console escape sequences and is not captured to the standard output. So in Jenkins logs it seems that the browser is started and nothing else is happening until it times out while actually compilation is running at the same time.

I was experiencing the same issue and then I found the solution here:
https://github.com/ionic-team/ionic-unit-testing-example/issues/79
Basically it is downgrading to "jasmine": "2.99"
Here are my jasmine/karma related dependencies:
"jasmine-core": "2.99",
"jasmine-spec-reporter": "4.2.1",
"karma": "2.0.0",
"karma-chrome-launcher": "2.2.0",
"karma-cli": "1.0.1",
"karma-coverage-istanbul-reporter": "1.2.1",
"karma-jasmine": "1.1.0",

https://medium.com/@martatatiana/poor-detective-angular2-browser-crash-and-debugelement-f0a651dbf33 this article provide information useful for me.

I'm sorry, but this issue is not caused by Angular CLI. Please contact the author(s) of the jasmine project or file an issue on their issue tracker.


debug mode

Hey there,
I'm trying to make "Floodgate" work with FabricProxy-Lite. Specifically, it sends some data via player-info-forwarding when a linked bedrock player connects, which just produces a "com.velocitypowered.proxy.util.except.QuietRuntimeException: The connection to the remote server was unexpectedly closed." error in the velocity console - however, java players (for whom floodgate does nothing), and unlinked floodgate players (where stuff is also sent via player-info-forwarding) is working just fine.
Therefore, i was wondering whether there's some kind of debug mode in this mod to see what gets received/sent? (To be able to see where the issue is)
Thanks in advance!

thought i would just +1 this issue too...
velocity, and floodgate on the proxy/velocity must be sending the correct things/packets out as paper server work underneath them ok ..
so its defo within the FabricProcy-Lite mod not receiving/relaying the info to floodgate fabric properly, unless its a fabric-floodgate issue ?

Nope, I've been able to track that issue down; it's a floodgate-fabric issue :/
Here are the appropriate posts:
https://github.com/GeyserMC/Floodgate-Fabric/pull/70
that's the attempt to get FabricProxyLite support working, but according to Tim, it's now an issue with the packets send being too long (I've asked in the #development channel of the discord)
Here's the initial bug report with the current workaround of disabling linked accounts, that makes send-floodgate-data work
https://github.com/GeyserMC/Floodgate-Fabric/issues/56

Also, I'd close this issue here; but it still would be nice to have some kind of debug mode to see what's going in and out

excellent find/info thankyou ! ...
will the "local linking" still work, if global linking is switch off, or does that also suffer with same long packet issue ?

Not sure; haven't tried local linking. But I'd assume it would have the same issue :/
Anyways, we should probably discuss this on the floodgate-fabric post, that's more fitting to the issue instead of here

FabricProxy-Lite itself does not delegate / "relay" packets or anything of the sort; it just allows Fabric to interpret the player data info packets Velocity sends (in "modern" forwarding mode). (Said packets are identical no matter which software your backend is running, i.e. Paper, Fabric, Forge, etc.; Velocity knows no difference. However, different backends require different implementations to interpret the packets.)
You can monitor packets going to/from the Fabric server (or any Minecraft server) by reconfiguring Log4j. Note the following, however:

Unfortunately, since the Netty rewrite (Minecraft 1.7) only packet IDs and classes are logged, and not their contents; however, this information may still be helpful.

(Velocity uses Log4j as well, so the same approach should work there, too - though I'm not sure what Velocity's packet debug logging looks like in comparison to Minecraft's)

Oh. Well, thank you for explaining why this wouldn't be possible and for providing a solution for what to do instead :)
I'll close this then.

Forgot to mention this - gadget is a Fabric / Quilt mod that can record and inspect incoming / outgoing packets in-game. Definitely a lot more helpful than "OUT: [PLAY:2] ClientboundCustomPayloadPacket; OUT: [PLAY:5] ClientboundCustomPayloadPacket; IN: [PLAY:13] ClientboundCustomPayloadPacket".


Consolidate kc-app and keymaster-app

These apps differ only in the libraries imported during the build.

Create a local package for the wallet react component


Add alias to help

QoL improvement to add the .h alias to .help.

I don't believe this is a priority for the project (and I'm not even sure this is done correctly), so I'm closing this. Feel free to reopen if this is something you want.


compaction conf dictionary vals for cqlsh describe

This changes the order of the values in the compaction configuration dictionary. Locally, this fixes this error:
http://cassci.datastax.com/view/trunk/job/trunk_dtest/516/testReport/cqlsh_tests/TestCqlsh/test_describe/

And this passes on every version we test against?

If so, +1

Yep, green across the board. Thanks for the review, merging.


config specify watermark width

current default watermark width is 400 and it is not configurable.
When I use a large font size, the watermark will appear incomplete.

Thanks for picking that up @pangxiezhou. I've increased the default width and also made it a configurable option.
Included in Sphinxmark 0.1.17 release.


RHSTOR-5960: Manage policy modal refactoring as per new design

Issue: https://issues.redhat.com/browse/RHSTOR-5960

If we are in edit mode shouldn't modal header say as Edit instead of Enroll ??

https://github.com/red-hat-storage/odf-console/pull/1440#issuecomment-2175692852
It is not exactly editing, assigning the same policy to the new subscriptions. end of the day we are going to create new DRPC only.

/approve
/lgtm


cannnot user LevelError as type Threshold

github.com/spf13/hugo
./main.go:34: cannot use "github.com/spf13/hugo/vendor/github.com/spf13/jwalterweatherman".LevelError (type "github.com/spf13/hugo/vendor/github.com/spf13/jwalterweatherman".Threshold) as type "github.com/spf13/jwalterweatherman".Threshold in argument to commands.Hugo.Deps.Log.LogCountForLevelsGreaterThanorEqualTo

Please use http://discuss.gohugo.io/ for questions/troubleshooting. Also see  Hugo Documentation.


Remove the custom layernorm for convnext

What does this PR do?

Removes the custom layernorm used in convnext that correctly handled mixed precision. This fix is now in upstream transformers since 4.23 so we remove it from here.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


No property first-moov-then-finalise in element qtdemux

If I remove the property from https://github.com/insight-platform/Savant/blob/b3a12f959ab60595fe8b683f430aa57ce50f7a97/adapters/gst/gst_plugins/python/video_files_sink.py#L87, it works.

No property fragment-mode in element qtdemux

@Y-T-G Could you please clarify what doesn't work with that property? video_files_sink uses qtmux, not qtdemux. And qtmux has the property fragment-mode:
  fragment-mode       : How to to write fragments to the file.  Only used when 'fragment-duration' is greather than 0
                        flags: readable, writable
                        Enum "GstQTMuxFragmentMode" Default: 0, "dash-or-mss"
                           (0): dash-or-mss      - Dash or Smoothstreaming
                           (1): first-moov-then-finalise - First MOOV Fragment Then Finalise

@tomskikh Yes, sorry. I meant qtmux. I don't see that property when I check.

I am using ghcr.io/insight-platform/savant-adapters-deepstream:latest.

@Y-T-G Use ghcr.io/insight-platform/savant-adapters-gstreamer:latest for video files sink.

@tomskikh Thanks


Adding Container Apps Environment

A Container App needs to be in a container apps environment. I tend to name them with ctae. What do you think?

Learn Build status updates of commit 57002fc:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/ready/azure-best-practices/resource-abbreviations.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@stephen-sumner
Can you review the proposed changes? IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Learn Build status updates of commit d9047c2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/ready/azure-best-practices/resource-abbreviations.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

@agoncal and @sinedied - Thanks so much for the feedback and input! I always want this to meet customer needs.
I just pushed a commit to update the namespace based on this page: https://learn.microsoft.com/en-us/azure/templates/microsoft.app/managedenvironments?pivots=deployment-language-bicep
I liked both, but ultimately aligned to Yohan's suggestion since Antonio gave it a thumbs up.

Learn Build status updates of commit 87a1e8e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/ready/azure-best-practices/resource-abbreviations.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the learn.microsoft.com contributor guidesPost your question in the Learn support channel

#sign-off