Adding nrf52811 support

This PR adds support for nrf52811 SoC and DK.
The nRF52811 is a Bluetooth 5.1 Direction Finding SoC with comprehensive protocol support.
The nRF52811 SoC is capable of the latest features of Bluetooth 5.1, the most prominent being Direction Finding.
The radio in the nRF52811 SoC has comprehensive protocol capabilities, including Bluetooth 5.1 Directing Finding, all Bluetooth 5 features, 802.15.4, Thread, Zigbee, ANT and 2.4 GHz proprietary.
It has 4 dBm TX power and has been optimized to offer the best RX sensitivity of all SoCs in the nRF52 series.
The nRF52840 DK: PCA10056 is the recommend development kit, it emulates the nRF52811, and can be used as a starting point for development before moving over to a custom board. Please note that this development kit does not support Bluetooth Direction Finding. What is more it cannot be used with most of Arduino shields because of PCA10056 PIN layout.

@jarz-nordic Thank yo for adding nrf52811 support. I have pulled the code and try to build samples/bluetooth/beacon/ but failed.
Looks subsys/bluetooth/controller/ll_sw/nordic/hal/nrf5/radio/radio_nrf52811.h is missing.

@overheat : Thank you! I will update it.

@ioannisg : Thank you for comments.
Regarding radio file I was adviced by @cvinayak to reuse timings from nrf52840.

@ioannisg : Thank you for comments.
Regarding radio file I was adviced by @cvinayak to reuse timings from nrf52840.

Makes sense, it's similar Radio.

@jarz-nordic you would need a license header in all files, to make the license check pass.

@ioannisg : I added where it was possible. After discussion with @anangl we shall not add Apache license to ext/hal/nordic

@ioannisg : I added where it was possible. After discussion with @anangl we shall not add Apache license to ext/hal/nordic

You're right, we don't add that one in ext/nordic :)
Some headers are still missing (e.g. nrf52811_pca10056_defconfig both lic and copyright) or not complete (e.g. CMakeLists.txt & board.cmake, copyright is missing)

@ioannisg : done

@jarz-nordic perhaps sthg wrong with the counter driver (see CI error)

@anangl : Please take a look.

@ioannisg I fixed CI test. It seems that this problem is also valid for some more Nordic DKs.

Adding a "Block: HW Test" label, i.e. we should probably try to do some basic testing on HW before merging this Board/SOC support:

sanity check on the board, kernel tests, etc.
testing basic samples (e.g. Bluetooth, ...)

@ioannisg : I've tested few samples on this hardware:

/zephyr/samples/bluetooth/beacon/
/zephyr/samples/bluetooth/peripheral_hr
/zephyr/samples/hello_world
/zephyr/samples/subsys/shell/shell_module

All tests were passed

@ioannisg : counter test is failing on a board: holyiot_yj16019 which is not related to my PR.
The same tests is failing for nrf52810 which is already in Zephyr upstream. Apperantly there is some mess but in my opinion it shall not be fixed within this PR.

@ioannisg : counter test is failing for board: holyiot_yj16019 which is not related to my PR.
The same tests is failing for nrf52810 which is already in Zephyr upstream. Apperantly there is some mess but in my opinion it shall not be fixed within this PR.

Doesn't it compile, or compiles, runs bu fails?

@ioannisg : counter test is failing for board: holyiot_yj16019 which is not related to my PR.
The same tests is failing for nrf52810 which is already in Zephyr upstream. Apperantly there is some mess but in my opinion it shall not be fixed within this PR.

Great. Suppose, you are using nrf52840 DKs as hardware?

@ioannisg : Yes I am using nrf52840 DK to emulate nrf52811 (nrf52811_pca10056)
These tests were passed on board: -DBOARD=nrf52811_pca10056

/zephyr/samples/bluetooth/beacon/
/zephyr/samples/bluetooth/peripheral_hr
/zephyr/samples/hello_world
/zephyr/samples/subsys/shell/shell_module

It also passed test:

tests/drivers/counter/counter_basic_api

Currently in CI test tests/drivers/counter/counter_basic_api is failing for DK holyiot_yj16019 which is not related to my PR. My PR is not causing this error.

@ioannisg : Yes I am using nrf52840 DK to emulate nrf52811 (nrf52811_pca10056)
These tests were passed on board: -DBOARD=nrf52811_pca10056
* /zephyr/samples/bluetooth/beacon/

* /zephyr/samples/bluetooth/peripheral_hr

* /zephyr/samples/hello_world

* /zephyr/samples/subsys/shell/shell_module

It also passed test:
* tests/drivers/counter/counter_basic_api

Currently in CI test tests/drivers/counter/counter_basic_api is failing for DK holyiot_yj16019 which is not related to my PR. My PR is not causing this error.

 It's probably copypasted.
You could also add nrf52811_pca10056 configuration for counter test: https://github.com/zephyrproject-rtos/zephyr/tree/master/tests/drivers/counter/counter_basic_api/boards

@nordic-krch : I've added nrf52811 to supported boards, but as mentioned before nrf52810 is also failing this test despite the fact nrf52810 board is available for a longer period of time.
Why this test is actually failing for other boards while my PR shall not affect them?

@nordic-krch : I've added nrf52811 to supported boards, but as mentioned before nrf52810 is also failing this test despite the fact nrf52810 board is available for a longer period of time.
Why this test is actually failing for other boards while my PR shall not affect them?

Please, add the nrf52810_pca10040 configuration as well.
I think failing is maybe due to how CI selects the (test/sample, board) combinations to build for each run.

@nordic-krch : I've added nrf52811 to supported boards, but as mentioned before nrf52810 is also failing this test despite the fact nrf52810 board is available for a longer period of time.
Why this test is actually failing for other boards while my PR shall not affect them?

Please, add the nrf52810_pca10040 configuration as well.
I think failing is maybe due to how CI selects the (test/sample, board) combinations to build for each run.

Let's do that in a follow-up PR.

@carlescufi @galak , I suppose this could be merged now? The license check fail is expected.

+1 for merging it as it will fix CI for other PRs related to counter.


Temporaly bump the worker flavors

While we wait for custom flavors to maximize our resource usage
lets bump the flavor to what we can use now, this gives the workers
12 more Gb of ram so it should help a lot

hey look at that, less than 3 hours of jobs, airship deployed correctly, tempest did not fail with any 503! Seems that increasing resources is helping smooth the deploy!

we should not wait for the CI for this to be merged

@Itxaka I would like to see the CI for this, to see the timing. I think it's valuable input.

oh, you will see it @evrardjp its just that we should not wait to merge it (job will keep running) in order to rebase and test the SES rook stuff today :)


Hangs on at exit

Hangs on at exit when using async mode,
Fuel.get("http://www.google.com/").responseString { request, response, result ->
        println(result.getAs<String>())
    }

FuelManager.instance.executor.shutdown() // this line fixes problem

I am not sure I understand your problem. Are you using this on Android?

On desktop. Executor prevents jvm from stopping if not shutdown it (executor) explicity,

Ok. If you happen to know how to fix it please let me know. Even better you could do PR which I am happy to accept it.

Close as it stales.


deprecate scala_test suites

In using the scala rules for a short time, we have already seen several instances of people forgetting to update the suites attribute.
This changes to always run all tests in the target, print the timing for each test in the target (in the standard out) as well as full stack traces of errors.
what do you think @dinowernli

@johnynek
I believe I originally tried using the -R flag of the scalatest runner and ran into problems where the tests were not being picked up. However, it is possible that I hadn't found the magic combination of flags.
So, bottom line: if this works: LGTM.

@dinowernli hmm. It is scary for tests not to be run. And indeed, without the -o flag, it didn't find the tests, but I did verify they failed if I broke the test intentionally.
I'm inclined to merge and if we find an example of it not working then add that to the repo as a test case, and fix then.
What do you think?

@johnynek
Absolutely, I'm really happy you found a way to make it work :) LGTM.


update markdown

Codecov Report
Attention: 3 lines in your changes are missing coverage. Please review.

Comparison is base (b002632) 93.53% compared to head (4cea241) 93.32%.

Files
Patch %
Lines

...rces/HandyRouter/Classes/Router/Route/Router.swift
0.00%
3 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main       #3      +/-   ##
==========================================
- Coverage   93.53%   93.32%   -0.22%
==========================================
  Files          29       29
  Lines        1330     1333       +3
==========================================
  Hits         1244     1244
- Misses         86       89       +3

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Parallel computation is very slow

import monix.reactive._
import monix.execution._
import spire.syntax.cfor._

object MultiSum extends App {

  implicit val scheduler = Scheduler.computation()

  val N = 100000000L

  val obs = Observable.range(0L, N)

  val sumConsumer = Consumer.foldLeft[BigInt, Long](BigInt(0))(_ + _)
  val loadBalancer = Consumer.loadBalance(16, sumConsumer)

  val task = obs.consumeWith(loadBalancer).map(_.sum)

  val start = System.nanoTime()
  cforRange(0 until 10) { _ =>
    var sum = 0L
    cfor(0L)(_ < N, _ + 1) { i =>
      sum += i
    }
    println(sum)
  }
  val end = System.nanoTime()
  val time = (end.toDouble - start.toDouble) / 1.0e9
  println(s"Single thread took ${time / 10.0}s")

  val start2 = System.nanoTime()
  cforRange(0 until 10) { _ =>
    val sum = task.runSyncUnsafe()
    println(sum)
  }
  val end2 = System.nanoTime()
  val time2 = (end2.toDouble - start2.toDouble) / 1.0e9
  println(s"Multi-thread took ${time2 / 10.0}s")

}

Single thread took 0.0636171097s
Multi-thread took<PHONE_NUMBER>6450002s

Using monix 3.0.0-RC2 on a RHEL machine with 16 cores.

IIRC that was already discussed on gitter. Just on the glance, there seems to be quite a lot difference except just having multiple threads.
val obs = Observable.range(0L, N) // Long boxing
val sumConsumer = Consumer.foldLeft[BigInt, Long](BigInt(0))(_ + _) // BigInt allocs - note that + uses implicit conversion Long => BigInt first, not optimized BigInteger#add(long)
val loadBalancer = Consumer.loadBalance(16, sumConsumer) // Async queues allocations & usage

val task = obs.consumeWith(loadBalancer).map(_.sum) // Potentially lots of context switching - consumer itself is 17th logical thread

versus
var sum = 0L // No long or BigInt boxing

// not sure if JIT is smart enough, but pure range-sum
// can be replaced with a constant-time expression - (N-1)*N/2
cfor(0L)(_ < N, _ + 1) { i =>
  sum += i // no overflow protection, btw
}
println(sum)

So, throwing cores at a problem might not make anything faster. In fact, with pure CPU-bound tasks, the overhead of context shifting alone might negate all performance gains from parallelism.
I don't think there's any issue in monix itself to be fixed here. Observable is just not a proper tool for that problem.


CSS Hack to fix safari text inputs

Details
For some reason the userSelect property is being overridden by react-native-web internals for text inputs. This CSS hack solves the problem and doesn't seem to introduce any others.
We should really consider filing a bug report in react-native-web, unless I'm gravely misunderstanding why TextInput components should by default (and in fact, in all cases) have the property user-select: none.
Fixed Issues
Fixes https://github.com/Expensify/Expensify.cash/issues/3598
Tests / QA Steps

Run the app in Safari
Hit the + icon in the ReportActionCompose and choose Request Money/Split Bill.
Enter an amount for the request, and hit Next
Verify that you can enter a value into the text input above "What's it for?"

Tested On

[x] Web
[x] Mobile Web
[x] Desktop
[ ] iOS
[ ] Android

Screenshots
Web
Still working on Chrome:

Also working on Safari:

Mobile Web

Desktop

iOS

Android

Awesome Find. I believe it has been fixed in the new version. @Jag96 here is trying to update the lib. So maybe, in that case, we don't need it at all.

I believe it has been fixed in the new version.

Did you see something about this in the changelog?

I haven't checked but It seems a major problem that I think should have been addressed. Also, we saw one more bug which was fixed in the new version on RN-web so I guessed, but still a belief. :smile:

Okay, well @Jag96 if/when we upgrade RNW let's try to remember to check if we can remove this CSS hack.

I haven't checked but It seems a major problem that I think should have been addressed

It might not have consistent reproduction ... maybe it has to do with the TextInput being nested in a ScrollView?

🚀 Deployed to staging in version: 1.0.69-2🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

In my testing, updating React-Native-Web to 0.17.0 (latest) doesn't fix this issue.
Platform iOS Safari.

🚀 Deployed to production in version: 1.0.73-3🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


changed sounds in SoundAscensionEffect.kt from Sound to String

this is a partner pr with https://github.com/MineInAbyss/server-config/pull/17. Need both prs to work since they change the type of params passed and expected.

this is a partner pr with https://github.com/MineInAbyss/server-config/pull/17. Need both prs to work since they change the type of params passed and expected.


button disabled during auth

Describe the bug
The button should be disabled during Signup/Sign-in so that user cannot make another request as well as to show a loading process just like netify login page
To Reproduce
Steps to reproduce the behaviour:

Go to 'Signup/Sign-in'
Click on button
Till request is completed one can click the button one more time which in turn will make one more request

Expected behaviour
The button  should be disable after the click is made
Screenshots
Required
https://user-images.githubusercontent.com/67755128/115105535-35f66280-9f7d-11eb-905e-397f629efe36.mp4
Desktop (please complete the following information):

OS: [e.g. iOS] WIN10
Browser [e.g. chrome, safari] edge
Version [e.g. 22] 89

Additional context
A feedback should be provided to user through loading or disabling the button

@VenomFate-619 Would you like to work on this issue?

Yes I will do it yes


Update Breez SDK to v0.5.0

This PR updates #1897 to the latest dev and upgrades the Breez SDK dependency to v0.5.0. This SDK update in turn upgrades the Greenlight CLN nodes to 24.02gl1 and various other features & bug fixes:

Merged manually into the branch


Add replace in composer.json for zf1 dependencies

ZF1 dependencies (i.e. zf1 doctrine) require the original zf1 package. This PR adds replace to composer.json to make sure regular zf1 is not included in the vendor.

Didn't know this was a thing, learn something new every day. Thank you

Sorry about the accidental close there, hit the wrong button


Update dependencies for v2023.4

When I run tests, I see the following warning. Sounds like we should update caniuse-lite:
Browserslist: caniuse-lite is outdated. Please run:
  npx update-browserslist-db@latest
  Why you should do it regularly: https://github.com/browserslist/update-db#readme


Rust Analyzer is not installing

Hello,
I just installed this Extension Pack and noticed that Rust Analyzer is not installing automatically.
Apparently Rust Analyzer's Extension ID changed from "matklad.rust-analyzer" to "rust-lang.rust-analyzer"

Hey @salvadormarcos
Thank you for your bug report. I just fixed it and released Version 1.1.1


Month appears truncated in TKCalendarMonthView (1st column Monday)

When the day for the 1st column of the calendar has been selected to be Monday then the height of the table is not calculated correctly for months that start with Sunday and end with Monday (ex. April 2012, September 2013). In these cases the row with the last day of the month is omitted, having thus the last day appearing in the table the 29th of the month.

I believe the problem stems from this method in NSDate+TKCategory category:
- (NSInteger) daysBetweenDate:(NSDate*) d{
	NSTimeInterval time = [self timeIntervalSinceDate:d];
	return abs(time / 60 / 60/ 24);
}

The problem can is demonstrated by the following code:
  NSDate *date = [NSDate date];
  TKDateInformation info = [date dateInformationWithTimeZone:local];
  info = [date dateInformationWithTimeZone:local];
  info.hour = 0;
  info.minute = 0;
  info.second = 0;
  info.day = 1;
  info.month = 3;
  info.year = 2012;
  NSDate *march1st = [NSDate dateFromDateInformation:info timeZone:local];

  info = [date dateInformationWithTimeZone:local];
  info.hour = 0;
  info.minute = 0;
  info.second = 0;
  info.day = 1;
  info.month = 4;
  info.year = 2012;
  NSDate *april1st = [NSDate dateFromDateInformation:info timeZone:local];

  NSInteger daysBetween = [april1st daysBetweenDate:march1st];

  NSLog(@"days between %@ and %@ ==> %d",
            [march1st descriptionWithLocale:[NSLocale currentLocale]],
            [april1st descriptionWithLocale:[NSLocale currentLocale]], daysBetween);

==>
days between Thursday, 1 March 2012 12:00:00 AM Central European Time and
                            Sunday, 1 April 2012 12:00:00 AM Central European Summer Time
 ==> 30

Flipping the dates yields (as expected) the same result:
 [march1st daysBetweenDate:april1st] ==> 30

My solution is to use the following as replacements for the NSDate+TKCategory daysBetweenDate: category method:
- (NSInteger) daysBetweenDate:(NSDate*) aDate {
  return [self daysBetweenDate:aDate calendar:[NSCalendar currentCalendar]];
}

- (NSUInteger) daysBetweenDate:(NSDate *) aDate calendar:(NSCalendar *) aCalendar {
  NSDate *fromDate, *toDate = nil;

  [aCalendar rangeOfUnit:NSDayCalendarUnit startDate:&fromDate
               interval:NULL forDate:self];
  [aCalendar rangeOfUnit:NSDayCalendarUnit startDate:&toDate
               interval:NULL forDate:aDate];

  NSDateComponents *difference = [aCalendar components:NSDayCalendarUnit
                                              fromDate:fromDate toDate:toDate options:0];
  return abs(difference.day);
}

Solution was cribbed from: http://stackoverflow.com/questions/4739483/number-of-days-between-two-nsdates
I would like to hear from the maintainer about this.

Fixing the number of days between two dates (see above) revealed another bug.  Now April 2012 does not display correctly - the last week (starting with Monday April 30) is missing.
The problem occurs when weeks start with Monday (sunday == NO).
The problem is in this method:
- (id) initWithMonth:(NSDate*)date
               marks:(NSArray*)markArray
    startDayOnSunday:(BOOL)sunday

and I believe it has to do with how the number or rows are computed:
int row = (daysInMonth + dateInfo.weekday - 1);
if(dateInfo.weekday==1&&!sunday) row = daysInMonth + 6;
if(!sunday) row--;
row = (row / 7) + ((row % 7 == 0) ? 0:1);

I do not have a solution yet.


Replaced process.exit() with process.exitCode()

fixes #708

Hey, thanks for sending this PR, but unfortunately we got two fixing the same issue and picked the other one instead. The reason is that process.exitCode is not a function, so this one doesn't work.


BUG: Dates are not diagonal when viewing from an iPhone

The Bug
The dates that are supposed to be on the X-axis are diagonal and overlapping with the graph itself and the graph's title.
To Reproduce:
Visit my profile, use the dev tools and then switch the view mode to an iphone
Expected behavior
Should be normally aligned across the X-axis
Screenshots

Device: iPhone 8+
OS:  iOS 15
Browser: Native GitHub App
Version 1.38.0

We are no longer supporting diagonal dates, due to limitations in safari


Allow Plugins for Automatic Actions

Hi,
Would it be possible to allow developers to create their own external providers for automatic actions (or is it possible already?) in a way that will be 'safe' if/when I upgrade the copy of Kanboard?
I'd like to link up our internal bug reporting software to Kanboard ... now, I know I can do this already through the REST-API, but it would be really cool if I could allow it to be used in the 'automatic actions' bit instead, so that users could customise it based on the project and use it just like they would github etc.
Thanks,
Algy
ps - great work on Kanboard, it's superb :)

It's now possible with the current development version by using plugins, see:

https://github.com/kanboard/plugin-example-automatic-action
https://github.com/fguillot/kanboard/blob/master/doc/plugins.markdown#extend-automatic-actions


Make building a mask easier

It would be nice to make creating a mask easier.
Taking the masking files from ds9 and having either a stand alone program to convert it into a fits mask or having lensed take the file directly as a mask would be excellent.

Thanks to the release of a region library at ericmandel/regions@92364d4 this should be a lot easier now.


Support const alias_tensor_instance

It would be nice if alias_tensor class had support for const tensor&, something like:
        alias_tensor_const_instance operator() (
            const tensor& t,
            size_t offset
        );

Is it feasible?

Not in any clean way since alias_tensor_const_instance needs to inherit from tensor.  So you will be able to pass it to functions that take a tensor& and it will compile.  We could make mutating functions throw an error, but I'm not sure that's any better than const casting and using the existing alias tensor.
You will also have a problem where an alias_tensor_const_instance is unusable unless it is itself declared const because the non-const members will be selected automatically when they are called, leading to exceptions being thrown.
I'm open to ideas to make it workable but it's not super clear how to do it without a bunch of problems.

What if: return simply a const alias_tensor_instance and defines a C++11 const move constructor for that class? Never seem it done, a const klass&& other parameter, but should work, right?

C++11 defines const constructors?  I don't think that exists.

Not const constructors, const rvalue reference constructors. But on a second thought, this is a recipe for a disaster...
class PointerHolder
{
public:
	PointerHolder(const PointerHolder&& other)
	{
		ptr = other.ptr;
	}

private:
	PointerHolder(int *ptr):
		ptr(ptr)
	{}

	friend const PointerHolder pointer_holder_creator(int *ptr);

	int *ptr;
};

const PointerHolder pointer_holder_creator(int *ptr)
{
	const PointerHolder ret(ptr);
	return ret;
}

int main()
{
	int *a = new int[42];

	{
		const PointerHolder h(pointer_holder_creator(a));

		h; // ...
	}

	delete[] a;
}

I don't know how to make it work on classes with non-trivial destructors without using mutable, because you wouldn't be able to change the state of the rvalue referenced object to a valid destructible state. One of possibly many problems is that one would be allowed to create a non-const version of a const object, like:
	PointerHolder const_removed_h(std::move(h));

Right, the central problem is the assignment to a non-const version of the
object.  That's the reason I didn't make a const version of alias tensor.

Hope you don't mind, I've asked on StackOverflow:
https://stackoverflow.com/questions/39168434/how-to-do-a-factory-of-const-objects

As people answered in Stack Overflow, a simple, if not very clean solution, would be return a new type not derived from tensor, but containing a const tensor&. How does this sound to you?
struct const_tensor_holder {
    /* Maybe make it private and add a get() method? */
    const alias_tensor_instance &t;
};

const_tensor_holder operator() (
            const tensor& t,
            size_t offset
        );

I deleted my previous comment because I didn't think I really understood the problem, and the solution proposed was wrong. The suggestion given by Yakk on Stack Overflow seems to work like this:
class alias_tensor_const_holder
{
public:
    const tensor& get() {
        return t;
    }
private:
    const alias_tensor_instance t;
}

/* ... */

alias_tensor_const_holder operator() (
            const tensor& t,
            size_t offset
);

The copy to non-const is solved by hiding the object privately, and never exposing it directly, but only through a const tensor& interface, so if the user makes a copy, it is a deep copy.

Very good ideas on stack overflow :+1:
That's definitely a good solution.  Adding an implicit conversion in addition to a get() makes it a really nice solution.  I'll add this to dlib.  Or you can make a pull request with the changes if like :)

Although I am not sure how to build a const alias_tensor_instance from a const tensor&, I'll try.

You can do the conversion like this: const_cast<tensor&>(t) and pass that to the existing operator() to get the alias_tensor_instance needed.  I can add the code if you would rather me to it, it's no trouble.

Please do it, or I'm afraid I'll waste effort trying to match the code style only to be rejected in the end. I was trying to do without using const_cats<> but it seems to be impossible...

I just pushed the code for this.  So you should be able to use const aliasing tensors now.   Thanks for suggesting the idea :)


PESQ No utterances detected

🐛 Bug
When calculating pesq for a batch, if an exception is thrown for a single audio in that batch, error thrown for entire batch.
To Reproduce
Steps to reproduce the behavior...

Code sample & error trace
# Ideally attach a minimal code sample to reproduce the decried issue.
# Minimal means having the shortest code but still preserving the bug.

import torch
from torchmetrics.audio import PerceptualEvaluationSpeechQuality

torch.manual_seed(42)
torch.cuda.manual_seed_all(42)

if __name__ == "__main__":
    preds = torch.randn(32, 16000*10)
    target = torch.randn(32, 16000*10)
    wb_pesq = PerceptualEvaluationSpeechQuality(16000, 'wb',2)
    print(wb_pesq(preds, target))

Error trace

Traceback (most recent call last):
  File "/data/veera/zspeech/temp/sample.py", line 11, in <module>
    print(wb_pesq(preds, target))
  File "/home/veera/anaconda3/envs/zspeech/lib/python3.10/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/home/veera/anaconda3/envs/zspeech/lib/python3.10/site-packages/torchmetrics/metric.py", line 311, in forward
    self._forward_cache = self._forward_reduce_state_update(*args, **kwargs)
  File "/home/veera/anaconda3/envs/zspeech/lib/python3.10/site-packages/torchmetrics/metric.py", line 380, in _forward_reduce_state_update
    self.update(*args, **kwargs)
  File "/home/veera/anaconda3/envs/zspeech/lib/python3.10/site-packages/torchmetrics/metric.py", line 482, in wrapped_func
    update(*args, **kwargs)
  File "/home/veera/anaconda3/envs/zspeech/lib/python3.10/site-packages/torchmetrics/audio/pesq.py", line 124, in update
    pesq_batch = perceptual_evaluation_speech_quality(
  File "/home/veera/anaconda3/envs/zspeech/lib/python3.10/site-packages/torchmetrics/functional/audio/pesq.py", line 108, in perceptual_evaluation_speech_quality
    pesq_val = torch.from_numpy(pesq_val_np)
TypeError: can't convert np.ndarray of type numpy.object_. The only supported types are: float64, float32, float16, complex64, complex128, int64, int32, int16, int8, uint8, and bool.

Variable pesq_val_np holds the value as below

[1.5404247045516968 1.4244357347488403 1.7014210224151611
 1.3647973537445068 1.1401857137680054 1.4725890159606934
 2.0076751708984375 1.088727355003357 1.5617468357086182
 1.2922636270523071 1.2720121145248413 1.284945011138916
 1.2110638618469238 1.5236833095550537 1.9427233934402466
 1.3616420030593872 1.1479936838150024 1.2334833145141602
 2.5019659996032715 1.1108096837997437 1.4132858514785767
 1.6151965856552124 3.488539218902588 1.12986159324646
 NoUtterancesError(b'No utterances detected') 1.1446586847305298
 1.2475643157958984 1.3870091438293457 1.4756184816360474
 1.3193098306655884 1.5343947410583496 1.2668492794036865]

when converting the above the pesq_val_np to tensor, error is thrown. (above mentioned error trace)
either it can be replaced with 0 or with average value.

Expected behavior

Error handling

Environment

TorchMetrics version 2.0.0
Python 3.10.6 & torch 2.0.0

Additional context

If an audio file encountered an error and dont have pesq value, then replacing it with 0 may affect the overall batch score, what could be the best solution ?

TorchMetrics version 2.0.0

are you sure?

My bad, apologies. updated now.
the torchmetric in my environment was version 1.4.0.post0


Trust Registry Protocol 2.a. #2

issuer URI

Vitor P: Issuer names for shipped COVID credentials might not be URIs
e.g. EU uses a truncated hash
e.g. SHC uses a HTTPS URL
Antti K: In this case ToIP issuers are required to have a URI (i.e. DID), see comment above.
Vitor P: So, you are saying I can't use this spec with COVID certificates that are out today?
Antti K: ToIP specs are primarily targeted for use in systems implementing the ToIP stack. So, if the Covid certification system does not implement ToIP stack, it likely cannot implement this spec fully. Obviously it can use the spec to model the trust registry & APIs.
In the Motivation chapter, it is clearly scoped that "the purpose of a ToIP specification is to enable the technical interoperability necessary to support transitive trust within and between different trust communities implementing the ToIP stack."

comments from v1 draft - closing


Presto cli supports --timeout

This will be useful for debugging.  When debug presto step by step for a long time, I always got presto-cli timed out with following error
Query is gone (server restarted?)

@yaoxin226 Hi, I can do it, if nobody is working on it.
As far as I could see, it is currently 2 minutes. Should it be in minutes or in seconds, which one would be better?

This is actually not a CLI issue. There are two related server config variables:

query.client.timeout -- if the client does not heartbeat within this period, the server fails the query with the ABANDONED_QUERY error
query.max-age -- the server will expire queries older than this (if there are more than query.max-history queries awaiting expiration)

I think there are two situations:

How long should server wait if it hasn't receive a heartbeat from client (Already configurable as @electrum mentioned)
How long should client wait if it hasn't receive a response from server ( I think Presto is missing this )

At, yes, you are correct, that "server is gone" can happen here:
https://github.com/facebook/presto/blob/master/presto-client/src/main/java/com/facebook/presto/client/StatementClient.java#L254
We could make that configurable. Probably "client request timeout" or similar.

@electrum I was thinking to add this option to ClientOptions and pass it to ClientSession then finally use it in StatementClient.
Do you think, this is the right approach here?
FYI: I am literally new to codebase and everything so is there anything I need to know before starting. Thanks!

@electrum @yaoxin226
I implemented it in on my fork's branch. I just want to show it before PR. You can have look at it here https://github.com/harunurhan/presto/commit/53121ecbc9eb9316b5147fdc115cc4c1bc0890c1
All tests passed and seems to work as far as I could test.

This looks like a good start. One comment is to use the Airlift Duration object, since that is both easier for users (can say "2m" or "30s") and avoids needing to specify the unit in code.

@electrum
Thanks for your help, changed it here:
https://github.com/harunurhan/presto/commit/a18b09ac1ae793e0856ea240578d902594dcd682

Please create a pull request!

0.129 will have --client-request-timeout


Add key to network view

Need to indicate what the node colors correspond to and whether the links are forward or reverse citations

Partially done. Colors are hard coded in though so not ideal

Try looking at this example for a dynamic legend:
https://stackoverflow.com/questions/33167452/how-to-add-a-dynamic-legend-to-a-d3-force-directed-graph-in-apex

These two examples also have legends:
http://bl.ocks.org/Guerino1/2879486
http://bl.ocks.org/rpgove/10603627


Conection Error

Hello,
When I do a local connection, it's work. But when I do a remote conection, don't work and appear this error, how as imagem attached.
I need your help.
Thanks

So the reason for this is socket.io is not loading.  You need to change the url in your index.html folder to the place you have your socket server on.

But I have been changed this. My index.html url is my IP. They connect, but happen this.


chore: bump to 1.31.0

fixes #102:

removes everything that is related to WebSockets
bump the vaultwarden version to 1.31.0
bump the chart minor version

Thanks for the PR @victor-keltio.


knative-serving: Revert component's version to 1.8.0

Revert knative-serving version to 1.8.0 since knative-operator cannot fetch manifests for versions >=1.10.x. More details in #147
How to test the PR

Deploy knative-operator
Deploy knative-serving (from the PR's branch always)
Check that

there is no error or sth weird in knativeserving CR conditions (kubectl get knativeserving -n knative-serving -o yaml)
it creates deployments that do not error out
it spins up pods for each of the deployments in knative-serving namespace that go in Running state

Could not verify. Deployment failed.
juju deploy ./knative-operator_ubuntu-20.04-amd64.charm --trust --resource="knative-operator-image=gcr.io/knative-releases/knative.dev/operator/cmd/operator:v1.10.3" --resource="knative-operator-webhook-image=gcr.io/knative-releases/knative.dev/operator/cmd/webhook:v1.10.3"
juju deploy ./knative-serving_ubuntu-20.04-amd64.charm --trust
juju relate knative-operator knative-serving

Juju status:
Model     Controller          Cloud/Region        Version  SLA          Timestamp
kubeflow  microk8s-localhost  microk8s/localhost  2.9.44   unsupported  11:30:54-04:00

App               Version  Status   Scale  Charm             Channel  Rev  Address         Exposed  Message
knative-operator           active       1  knative-operator             0  <IP_ADDRESS>  no
knative-serving            waiting      1  knative-serving              0  <IP_ADDRESS>   no       installing agent

Unit                 Workload  Agent  Address     Ports  Message
knative-operator/0*  active    idle   <IP_ADDRESS>
knative-serving/0*   error     idle   <IP_ADDRESS>         hook failed: "config-changed"

Relation provider                Requirer                        Interface       Type     Message
knative-operator:otel-collector  knative-serving:otel-collector  otel-collector  regular

Error:
unit-knative-serving-0: 11:30:38 ERROR unit.knative-serving/0.juju-log Uncaught exception while in charm code:
Traceback (most recent call last):
  File "./src/charm.py", line 190, in <module>
    main(KnativeServingCharm)
  File "/var/lib/juju/agents/unit-knative-serving-0/charm/venv/ops/main.py", line 441, in main
    _emit_charm_event(charm, dispatcher.event_name)
  File "/var/lib/juju/agents/unit-knative-serving-0/charm/venv/ops/main.py", line 149, in _emit_charm_event
    event_to_emit.emit(*args, **kwargs)
  File "/var/lib/juju/agents/unit-knative-serving-0/charm/venv/ops/framework.py", line 344, in emit
    framework._emit(event)
  File "/var/lib/juju/agents/unit-knative-serving-0/charm/venv/ops/framework.py", line 841, in _emit
    self._reemit(event_path)
  File "/var/lib/juju/agents/unit-knative-serving-0/charm/venv/ops/framework.py", line 930, in _reemit
    custom_handler(event)
  File "./src/charm.py", line 107, in _on_config_changed
    self._apply_and_set_status()
  File "./src/charm.py", line 64, in _apply_and_set_status
    self.resource_handler.apply()
  File "/var/lib/juju/agents/unit-knative-serving-0/charm/venv/charmed_kubeflow_chisme/kubernetes/_kubernetes_resource_handler.py", line 340, in apply
    apply_many(
  File "/var/lib/juju/agents/unit-knative-serving-0/charm/venv/charmed_kubeflow_chisme/lightkube/batch/_many.py", line 72, in apply_many
    returns[i] = client.apply(
  File "/var/lib/juju/agents/unit-knative-serving-0/charm/venv/lightkube/core/client.py", line 457, in apply
    return self.patch(type(obj), name, obj, namespace=namespace,
  File "/var/lib/juju/agents/unit-knative-serving-0/charm/venv/lightkube/core/client.py", line 325, in patch
    return self._client.request("patch", res=res, name=name, namespace=namespace, obj=obj,
  File "/var/lib/juju/agents/unit-knative-serving-0/charm/venv/lightkube/core/generic_client.py", line 242, in request
    br = self.prepare_request(method, res, obj, name, namespace, watch, headers=headers, params=params)
  File "/var/lib/juju/agents/unit-knative-serving-0/charm/venv/lightkube/core/generic_client.py", line 173, in prepare_request
    raise ValueError("resource name not defined")
ValueError: resource name not defined

@orfeas-k Do we need to also change metadata.yaml to have versions 1.8.2 for workload containers?
https://github.com/canonical/knative-operators/blob/kf-4288-revert-knative-serving-to-1-8-2/charms/knative-operator/metadata.yaml#L22
https://github.com/canonical/knative-operators/blob/kf-4288-revert-knative-serving-to-1-8-2/charms/knative-operator/metadata.yaml#L25

Retried with 1.8.0 images - still same issue.
juju deploy ./knative-operator_ubuntu-20.04-amd64.charm --trust --resource="knative-operator-image=gcr.io/knative-releases/knative.dev/operator/cmd/operator:v1.8.0" --resource="knative-operator-webhook-image=gcr.io/knative-releases/knative.dev/operator/cmd/webhook:v1.8.0"
juju deploy ./knative-serving_ubuntu-20.04-amd64.charm --trust
juju deploy ./knative-serving_ubuntu-20.04-amd64.charm --trust
juju relate knative-operator knative-serving


Feature request: add flag to stop repetitions at first failure.

Rationale: when tracking flaky tests, --repeat is useful, but may be wasteful (especially in continuous integration). In most cases, it would be enough to stop at first failure.
May we add a flag to have this behavior, e.g. --stop-repeat-after-failure?

The resource waste of --repeat without stopping would only be high if the flaky tests use significantly more resources than the passing ones (especially since the passing ones would always have to repeat N times). Hopefully this isn't the case for your test suite in general.
Would the semantics for --gtest_break_on_failure be sufficient for your intended use case (stop running gtest-parallel when any test fails? I'm a bit hesitant to add flags that don't have a corresponding --gtest ones. I can see --gtest_break_on_failure being useful locally as you can start looking into the first detected failure without having to ctrl+c to abort execution.

Context: running a handful of tests a lot of time. If one of the test if flaky at 3%, first failure will appear on average at 33th try. With 1000 iterations, that's 967 more than needed!
--gtest_break_on_failure is not an ideal fit, since we still want to detect all tests failing at least once.
I agree this is not specific to gtest-parallel. Opened https://github.com/google/googletest/issues/2645

Thanks, do let me know what the outcome of that is as I'm more inclined to consider upstream flags. I was more thinking if you run 100 tests 100 times and only one of them is flaky, that 33th time only lowers the total number of iterations from 10000 to 9967, at which point the savings are less than 1%.


Features in Transit but missing here

TODO:

[ ] Do we need lock management like Transit?
[ ] Versions of keys with the same name

(Sub)Key versioning and maybe rolling keys via the API is the one feature i'm missing with this plugin. It would be great if this got implemented!

Sorry, no time (either to implement, or to review/maintain PRs)...


Cleanup default metrics configuration

This PR makes minor modifications to the recent changes to the default configuration for metrics. It attempts to simplify and clarify the generated data.
Three major changes have been implemented:

reporter label values transition to source and destination to match the {source|destination}_* other labels. The new values replace client and server.
connection_mtls label renamed to connection_security_policy. The values for the label have been updated to be one of {"unknown", "none", "mutual_tls"}. This reflects a move away from the boolean value of connection.mtls, which cannot be properly populated when Report()s from source.
removes source_namespace and destination_namespace labels. these were redundant with source_workload_namespace and destination_workload_namespace and not used.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: douglas-reid
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [douglas-reid]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@douglas-reid: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
6ee5517278e6055398cd321920c61d524866aeac
link
/test istio-pilot-e2e-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@douglas-reid: The following tests failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/istio-pilot-e2e-envoyv2-v1alpha3.sh
6ee5517278e6055398cd321920c61d524866aeac
link
/test istio-pilot-e2e-envoyv2-v1alpha3

prow/e2e-bookInfoTests-v1alpha3.sh
6ee5517278e6055398cd321920c61d524866aeac
link
/test e2e-bookInfo-envoyv2-v1alpha3

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test e2e-bookInfo-envoyv2-v1alpha3
/test istio-pilot-e2e-envoyv2-v1alpha3

Should connction_mtls be changed to connection_security_policy for accesslogs too?

@douglas-reid, Glad to see the redundant namespace labels go away.  FYI, we do use the connection_mtls label in Kiali to add that info to graph edges, but the change makes sense and is not a problem.  I'm not a big fan of  the reporter label (at least not yet) but I'm +1 on the terminology alignment.

@gargnupur done.

Ping.
Reviewers, I would really like to merge this PR as a first pass at cleaning up the telemetry configs for 1.0.

Also, I'm interested in the following:

Should we remove *_principal from the default label set? Do we believe that value will be lost if not included?

Should we remove *_principal

From the Kiali side we are not currently using those labels.

Should we remove *_principal from the default label set?

Shouldn't increase cardinality, right?

Do we believe that value will be lost if not included?

Not sure what you mean here.


[ADAP-721] [Bug] [Regression] Canceled or failed run creates a Database Error

Is this a new bug in dbt-redshift?

[X] I believe this is a new bug in dbt-redshift
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
When dbt tries to cancel a query it raises a Database Error with the pid as output:
Encountered an error:
Database Error
  syntax error at or near "123456789"

The cases I noticed that are triggering this bug but they may not be exhaustive:

Cancel a dbt execution while models or tests are running
A model is failing because of an error while running --fail-fast and other running models are cancelled

This is happening only since version 1.5, I don't see the issue on previous versions.
Debugging guess, not tested:

As per redshift-connector documentation fetchone() seems to return an array instead of a tuple like in psycopg.
When a query is cancelled the array is provided instead of the pid, which results in the error. Example: select pg_terminate_backend([123456789]);.
https://github.com/dbt-labs/dbt-redshift/blob/cbb45ca585a61b1bb250b48aac69c410f8ef4efb/dbt/adapters/redshift/connections.py#L253

Thanks a lot for your help! I am available if you need more information :)
Expected Behavior
The query should be cancelled without any error and print usual logs.
Steps To Reproduce
Easy steps to reproduce

Use Jaffle Shop project
Run the DAG
Cancel it while queries are still in RUN status (with ctrl+C)
Look at the error log

Harder steps to reproduce

Use a big project which have big models running in parallel (Jaffle Shop project is too simple)
Update a model usually running in parallel to make it fail
Run the DAG with --fail-fast
Look at the error log

Relevant log output
❯ dbt run

08:31:16  Running with dbt=1.5.3
08:31:16  Registered adapter: redshift=1.5.8
08:31:17  Found 5 models, 20 tests, 0 snapshots, 0 analyses, 346 macros, 0 operations, 3 seed files, 0 sources, 0 exposures, 0 metrics, 0 groups
08:31:17
08:31:23  Concurrency: 4 threads (target='dev')
08:31:23
08:31:23  1 of 5 START sql view model dev.stg_customers .......................... [RUN]
08:31:23  2 of 5 START sql view model dev.stg_orders ............................. [RUN]
08:31:23  3 of 5 START sql view model dev.stg_payments ........................... [RUN]
^C08:31:28
08:31:28  Finished running  in 0 hours 0 minutes and 10.50 seconds (10.50s).
08:31:28  Encountered an error:
Database Error
  syntax error at or near "1073857832"
08:31:28  3 of 5 ERROR creating sql view model dev.stg_payments .................. [ERROR in 4.89s]
08:31:28  2 of 5 ERROR creating sql view model dev.stg_orders .................... [ERROR in 4.90s]
08:31:28  1 of 5 ERROR creating sql view model dev.stg_customers ................. [ERROR in 4.90s]

Environment
- OS: MacOS 13.4.1 Intel
- Python: 3.9.16
- dbt-core: 1.5.3
- dbt-redshift: 1.5.8

Additional Context
No response

We're also noticing this. cc @stlee-aurora

Thanks for reporting this @hacherix and @olly-writes-code !
I've raised a PR to fix this: https://github.com/dbt-labs/dbt-redshift/pull/568

Hi! is there anything blocking this PR?

Thanks for the MR @dbeatty10! Any reason why it is not merged? Is there anything we can do to help?

@mikealfare / @dbeatty10  -- should we backport this to 1.6?


ASR limitations

[Enter feedback here]
ASR doesn't Support Ephemeral Disks but this is not explicitly documented here. Suggest it should be.
FYI it is documented at the other end...
https://learn.microsoft.com/en-us/azure/virtual-machines/ephemeral-os-disks#unsupported-features

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

ID: 7a8f2ca3-19b1-330d-8dd3-6dcdce38c8d4
Version Independent ID: 700335aa-c802-0314-1579-3493918f5000
Content: General questions about the Azure Site Recovery service
Content Source: articles/site-recovery/site-recovery-faq.yml
Service: site-recovery
GitHub Login: @atikmapari

@mike-westaway Thanks for your comment! We will review and provide an update as appropriate.

@mike-westaway I have raised a pull request to update the document as required. Once the pull request is merged, the changes will reflect live in the document. Thanks again!


Allow manual entry/editing of Meeting ID for Conference Details

Currently only the meeting link (URI) can be edited for an Ensemble. Need to allow the rest of the Conference Details to be edited.

See test: ensembleScheduledWithManuallyEnteredZoomLinkThenHasZoomLink


Support tensorflow 2.5 through 2.8.

Dropped support for Python 3.6.
Added Python 3.9 and 3.10.
Added TensorFlow 2.6, 2.7 and 2.8.
Updated github actions to test all of these combinations.
Had to update some of the tests_requirements - this caused some reformatting.
tfp.Distributions are sometimes wrapped in a _TensorCoercible - I added unwrap_dist to handle this.
For some versions there are problems serialising gpflow.Parameters. I skip the relevant tests.
Apparently the tags that are exported by TensorBoard changes slightly with version. Did a version test for that.
Had to down-adjust coverage to 96% - presumably related to the skipped tests above.

Notice the changes to the build system will require you/us to update the settings on which tests are required to merge.

Before you will be able to merge I need to disable the old quality check tests (Python-3.6 tensorflow~=2.5.0, Python-3.7 tensorflow~=2.5.0, Python-3.8 tensorflow~=2.5.0) and enable the new ones. Let me know when you want this to be done.


split out live and pre live query pack queries

Description
Split the query pack query into two separate ones for the live and pre-live slots
Issue
https://github.com/CDCgov/trusted-intermediary/issues/1657

PR Code Suggestions ✨
Explore these optional code suggestions:
Category	Suggestion                                                                                Score
General
Improve the accuracy of log filtering by refining the query conditions
7

Although this seems like good input, our ResourceId's do not contain the text live in them. Leaving a thumbs down in hopes that PR bot learns from this


MRG: Fix split file writing

Fixes a corner case bug where our auto-writing of split raw files would fail if we hit the file size limit right as we used up the last buffer. @kambysese @ChristinaZhao I don't know how you each independently managed to hit this long-standing rare bug in the span of a couple of days, but I'm impressed :) Feel free to try out the fix if you have time.
This PR does a few things to fix it:

Adds sanity double-check while writing that we will actually write some data.
Adds an extra conditional before splitting the file that only does it if we actually have more data to write.
Improves error messages related to bad choices of buffer_size_sec and split_size.
Moves raw.annotation reading and writing to come before the data block. This seems to make more sense than having it in the data block, and also keeps us safer in our file-size computations. Now nothing comes after the data writing other than closing tags, whereas before we could have broken things by having a large set of Annotations.

Ready for review/merge from my end.
Closes #3210.

Coverage decreased (-35.5%) to 55.38% when pulling 8a603378c2448c894e5afbf5b0971f263ed95283 on Eric89GXL:fix-split into 1edafe34f02c14cda0d4fd28942c56d2871f9135 on mne-tools:master.

Coverage decreased (-0.004%) to 90.831% when pulling<PHONE_NUMBER>be987baf7e0af0e1ff25aa7006d9e7 on Eric89GXL:fix-split into 1edafe34f02c14cda0d4fd28942c56d2871f9135 on mne-tools:master.

CIs are happy.

So #3210 read error was due to this bug in how the split files were being written, correct? Looks like a proper fix I am not seeing the error with 1 of 2 cases, the other I have not tried yet but I assume it will work as well. Thanks for the quick fix.

Thanks !

It worked! :)

Great, thanks for checking @ChristinaZhao


Joining collaboration session: Invalid connection URI:

Issue Type: Bug
Trying to connect VS Code to a Live Share that's in 2019. It shows the Workspace name that's open in 2019, so it's definitely connecting. However, midway through the connection process it suddenly fails with the error "Invalid connection URI:" with that colon. Logs attached.
LiveShareLogs.zip
Extension version: 1.0.182
VS Code version: Code 1.34.0 (a622c65b2c713c890fcf4fbf07cf34049d5fe758, 2019-05-15T21:59:37.030Z)
OS version: Windows_NT x64 10.0.17763

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz (8 x 2112)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_on<br

native_gpu_memory_buffers: disabled_softwarerasterization: enabledsurface_synchronization: enabled_onvideo_decode: enabledwebgl: enabledwebgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|7.93GB (2.19GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|

@jramsay can you take a look..

Closing due to inactivity. Please re-open if this you're still encountering the issue and can share more details. Thanks!

I don't understand why this is closed. It wasn't waiting on me, and it's a bug, and it's been reproduced by other users #2147, #2713.
Is there another issue where the fix is being tracked?

Thanks for catching this! I was doing a cleanup of old issues and I mis-closed this one. I’ll re-open it to track the fix for this specific bug.

This issue has been resolved. Thank you for reporting it. If the issue persists please reopen.


Local debugging fails because of accessToken

Describe the bug
I am trying to set up local debugging.
I followed these instructions up to the point where I have the launch.json file shown in the screenshots below.
When I click Run>Start Debugging, it throws this error an error saying the access token is not recognized as an internal or external command. I think this has something to do with the pipe character | just after 'Atza'. See screenshots for the full error.29.png)
To Reproduce
Steps to reproduce the behavior:

Create a new skill with Alexa Skills Toolkit
Follow the instructions here to set up local debugging
Open the Run menu and then choose Start Debugging.
The error occurs

Screenshots

Desktop:

OS: Microsoft Windows 10 Pro
Visual Studio Code Version: 1.68.1
Alexa Skill Toolkit Version: 2.11.1

Just covering the basics here, are you sure you are logged in on the dev console?
https://developer.amazon.com/en-US/docs/alexa/ask-toolkit/get-started-with-the-ask-toolkit-for-visual-studio-code.html#login
follow the steps under Sign in to your Amazon developer account from VS Code.

hmm looking at the command it's trying to run it seems the access token is setup with a pipe char |  and  the command prompt appears to treat the remainder of the command as a new command... and hence the error that the command doesn't exist..

could you try updating the configuration to encapsulate the accesstoken param with single quotes?
ie.
"args" : [
   "--accessToken",
   "'#{command:ask.accessToken}'",
    ...

]

Yep I am logged in on the dev console.
I tried encapsulating the accesstoken with double/single quotes but I'm still getting the same error.
I think you are right about the pipe char, do you know if every accesstoken contains one? If so then the issue may be with the way my vs code debugger handles it. Otherwise could it be possible to generate an accesstoken that doesn't contain a pipe char?

ok maybe try replacing pipe char with ^|  somehow ?    I'll try it out later but let me know if how that worked out! if so, that could potentially be done in the code as a fix eventually

That worked! I copied the accesstoken that was printed in the error message and replaced | with ^| and the debugging session successfully started.
I am having another issue now though, the skill simulator isn't running off local files. Any changes I make aren't seen until I deploy the skill with git commit and git push , any breakpoints I set don't pause the code execution and skill inputs and outputs don't appear in the debug console.

Hey @MichaelBriggsFluidra , I'm trying to narrow down what the root cause of the issue here is, I was wondering if you could try a couple things in your configuration? So far, I've not been able to produce this exact behavior, even using the same VSC version you listed above.

What terminal is listed as the default for you?

If you change the default terminal by using the Select Default Profile button in that dropdown, does it change the behavior for you?

Can you also try adding "console": "integratedTerminal" to the end of the configuration like below?

I can also check on the skill simulator issue, but I'll have to get back to you on that.

Hi @tydonelson

The powershell is set to default for me.
Changing the default terminal didn't seem to change anything.
Adding "console": "integratedTerminal" worked! This is the output in the terminal:

Thanks for checking on that, @MichaelBriggsFluidra ! Using "console": "integratedTerminal" is the best recommendation I have for now, we're working on getting some documentation updated around that exception for any Windows users running into the problem you're seeing. You should only have to add that line the first time you establish the launch.json skill debug configuration for a skill, so I hope it's not too painful of a workaround for now.
We are giving some thought to how to better resolve this in the future, but want to ensure that any change we make is passive and works with the many different O/S and shells that VSCode is compatible with.


declare the volume first, so that following commands also work when mounting on host

run the docker container and mount the data volume to an (existing, but empty) directory, e.g. docker run -ti -p 80:80 -v /home/mp/tmp/miniflux-data-new:/var/www/html/data mpollmeier/miniflux
when you request the start page, you get The data directory must be writeable by your web server user.
This PR fixes it.

I tested your PR and your changes doesn't change anything for me. Basically, you try to solve the same issue as this PR https://github.com/miniflux/miniflux/pull/592.

Interesting. It does make a difference for me. Anyway, feel free to ignore/close this PR then.

The Dockerfile is only used when building the image. If you use a custom folder location to bind the volume when running the container, you should have the correct permissions on this folder. To avoid this issue, you could use the provided docker-composer.yml that declare a named volume.


Migration Baumkataster 2023

This Pull Request contains all changes that were made due to the new Baumkataster 2023 and our slightle new database schema.
Changes are the following:

convert column 'pflanzjahr' to type integer accroding to new database schema and handle undefined or Null values
add dynamic file naming to allow easier migrations in the future
add year to the conf.yml to allow easier migrations in the future
handle (basically drop) trees from the new tree cadastre that have a duplicated gmlid
improved exception for better debugging
update README.md

@ff6347: I would be very happy if you could have a look at this :)

@all-contributors please add @julizet for code, docs


Only use JSON.parse to check for Objects

To Reproduce:
const db = dynamoose.model('db', new dynamoose.Schema({
  id: { type: String, hashKey: true}
}), {
  saveUnknown: true
});

db.create({
  id: 'foobar',
  unknown: '12345',
}).then(() => {
  db.get({ id: 'foobar' }).then(console.log);
});

This issue came up because I am storing a number as a string and JSON.parse('12345') does not throw. (Neither does JSON.parse('true') or JSON.parse('false')
In v1.0 will dynamoose always use dynamo Maps and BOOLs? If so then we can always assume a string is a string.

@ecwyne Looks like the tests are failing for this. It'd probably be good to add tests cases for this too right?
In terms of Dynamo types. In v1.0 the default will be switched to use Dynamo types by default, but this can be overwritten in the options object. I still need to find the code where I can change the default for this.

The tests are failing because it expects { S: '1' } to parse to 1 and not '1'.
I am of the opinion that if an unknown value comes in as { S: '1' } the assumption should be made that it's a string (because if it had originally been created as a Number it would have been stored in dynamo as such)
@fishcharlie what do you think?

@ecwyne For unknown types I personally disagree. If it's an unknown type I think we should try to parse it as far as possible. Parsing it as 1 instead of '1' gives the developer more flexibility. Especially since it's the current behavior and I don't think changing it has enough positives and breaking the behavior doesn't seem to have enough advantages right now. What do you think?

As a developer I'd expect to get back what I put in.
If I put in a Boolean I get back a Boolean
If I put in a Number I get back a Number
if I put in an Object I get back an Object
If I put in an Array I get back an Array
If I put in a String I get back a String (regardless of what is in the string)
If I wanted to get back a Number I would have put it in that way.

@ecwyne That's great, but if the model is using saveUnknown and not using Dynamo types, why shouldn't we try to parse that as far as we can? I understand what you are saying, but if we don't know the type the user meant it to be, why not parse that as far as we can?

Let's say I'm storing commit hashes. I would expect them to all be strings, but I only have to go back ~20 to find 5982320 which would be returned to me as a Number?
Also, as currently written I was getting errors when reading string numbers. It tried to treat it like a Map and converted '90210' to the following:
{
  '0': '9',
  '1': '0',
  '2': '2',
  '3': '1',
  '4': '0'
}

@ecwyne That use case is totally legit. Although I think that is a one off use case. For every one of those cases there are many cases that would work better with the current behavior.
Dynamoose shouldn't interpret anything about the use case that the developer is trying to build. If you'd like it to be strict and parse it as a number then I believe enabling Dynamo types or adding a property to your schema should work.
If I get a lot of push back we might reconsider. But I think Dynamoose can't confidently interpret the type it should parse as far as it can. Especially since that is the current behavior and making this a breaking change doesn't seem worth it.
If anyone has more feedback on this I'd love to hear it.

Is there any reason not to use Dynamo types (other than backwards compatibility)?

@ecwyne Not that I'm aware of. I think backwards compatibility is the biggest thing. I know I have tables using the old system. I'm still not quite sure how I can migrate those to the new system.

@fishcharlie
#373 is a reproduction of the issue I had originally (which prompted me to create this PR in the first place)


Application build for release crashes in GetCurrentClassLogger

Everything works when app is built for Debug but as soon as it is built for Release, GetCurrentClassLogger throws a null reference exception.
Is it only me or may be this is a limitation of the StackFrame?

Any change of a repro @alexeyzimarev ? No other reports yet of this yet....
(Sorry for slow response, other things and I'm holding off liblog work until netstandard & tooling have settled)

No repro and no other reports so closing.
Point of note: release builds do end up with different stackframe info because of optimisations.

Hello @damianh,
one user of websocket client library reported a similar issue.
Release build on UWP platform. I had to implement fallback and turn off logging for that situation.
Here is a callstack:
System.NullReferenceException: Object reference n ot set to an instance of an object.
  Module "Websocket.Client.Logging.LogProvider", in GetCurrentClassLogger
  Module "Websocket.Client.WebsocketClient", in .cctor
  ?
System.TypeInitializationException: A type initializer threw an exception. To determine which type, inspect the InnerException's StackTrace property.
  ?
  ?
  Module "Websocket.Client.WebsocketClient", in Start
  Module "System.Runtime.ExceptionServices.ExceptionDispatchInfo", in Throw
  ?
  ?
  ?
  Module "System.Runtime.CompilerServices.TaskAwaiter", in GetResult
  Module "MyAppUWP.ServerNotifications", in InitializeWebSocket


How to perform down-stream task for image classification?

Hei @turian @Froskekongen @Froskekongen @Borda @ojss,
It's really a nice repo on using self-supervised learning, like ALL-in-1.
I am new to SSL, however I have implemented your repo and developed model using main_pretrain.py code on Image classification dataset. Now I have pretrained model say byol-resnet-custom.ckpt, so how do I have to use this as down-stream task on my dataset? Please guide, I gone through main_linear.py but causing following errors:
usage: main_linear.py [--help] [--hydra-help] [--version] [--cfg {job,hydra,all}] [--resolve] [--package PACKAGE]
                      [--run] [--multirun] [--shell-completion] [--config-path CONFIG_PATH]
                      [--config-name CONFIG_NAME] [--config-dir CONFIG_DIR] [--experimental-rerun EXPERIMENTAL_RERUN]
                      [--info [{all,config,defaults,defaults-tree,plugins,searchpath}]]
                      [overrides [overrides ...]]
main_linear.py: error: unrecognized arguments: --dataset --backbone resnet18 --data_dir ./ --max_epochs 100 --gpus 0 --sync_batchnorm --precision 16 --optimizer sgd --scheduler step --lr 0.1 --lr_decay_steps 60 80 --weight_decay 0 --batch_size 128 --num_workers 4 --name general-linear-eval --pretrained_feature_extractor cifar10/byol-cifar10.ckpt --project self-supervised --wandb

Please guide regarding down-stream task, steps.
Thanks in advance.

Hey @saifhassan. I think you tagged the wrong people :). Anyways, from what I understood, you just wanna run the offline linear eval on a custom dataset. Can you share your full script?From the error, it looks like you are missing the --dataset parameter.

Hey @saifhassan. I think you tagged the wrong people :). Anyways, from what I understood, you just wanna run the offline linear eval on a custom dataset. Can you share your full script?From the error, it looks like you are missing the --dataset parameter.

being tagged wrong, you replied very fast. Thank you for that.
however that error is solved, Can you just guide me regarding the down-stream task, Like I have pretrained model using BYOL, Barlows, and others with ResNet18 and now want to apply on down-stream task (Image Classification)?

Hey @saifhassan. I think you tagged the wrong people :). Anyways, from what I understood, you just wanna run the offline linear eval on a custom dataset. Can you share your full script?From the error, it looks like you are missing the --dataset parameter.

I assumed that main_linear.py in repo means performing down-stream task, am I correct? if not, can you please guide me regarding how to perform down-stream task on pre-trained model which I have achieved using main_pretrain.py.

Thanks @vturrisi in advance

Yes, the main_linear.py file is used for downstream tasks. You just need to pass the downstream dataset and the pre-trained model in the config file. See an example here https://github.com/vturrisi/solo-learn/blob/main/scripts/linear/imagenet-100/barlow.yaml.

Yes, the main_linear.py file is used for downstream tasks. You just need to pass the downstream dataset and the pre-trained model in the config file. See an example here https://github.com/vturrisi/solo-learn/blob/main/scripts/linear/imagenet-100/barlow.yaml.

Thank you @DonkeyShot21. I have applied, will experiments more. Thanks again.

Yes, the main_linear.py file is used for downstream tasks. You just need to pass the downstream dataset and the pre-trained model in the config file. See an example here https://github.com/vturrisi/solo-learn/blob/main/scripts/linear/imagenet-100/barlow.yaml.

and what about finetune folder? what's the actual work of it?

@saifhassan you can also use main_linear.py to fine-tune the whole model instead of just training a linear classifier on top of the frozen backbone. For that, just follow the examples inside finetune. We don't support generating a confusion matrix, but you can easily implement it with lightning bolts or something like this.

@saifhassan you can also use main_linear.py to fine-tune the whole model instead of just training a linear classifier on top of the frozen backbone. For that, just follow the examples inside finetune. We don't support generating a confusion matrix, but you can easily implement it with lightning bolts or something like this.

Can you explain more regarding finetune. Actually that folder contains same .yaml file, How it can be used for finetuning?
or can you please guide, how can I finetune model generated by main_linear.py? some code snippet?


Remove x86 support

As mentioned here e2k is used by evil countries and we don't need to support it. So I think it would be a good solution to remove x86 support because this hardware is in use by the army of many evil countries

Отчет: прочитал 7 главу LYAH, решил кату "Решить задачу по глюкам"

ARM architecture is used by Russian "Baikal" processors. I propose to leave support only RISC-V

RISC-V shall be removed too: https://www.theregister.com/2021/07/15/yadro_riscv/

I truly believe with my entire heart that the x86 infrastructure, used by evil people all across the world to commit evil and heinous crimes, does not deserve to be supported in this project. As upstanding citizens and simply people who care about injustices and horrors happening in this world, we have a moral obligation to ban x86, x86-64 and everything related to those two from the open source community. Tools of violence never belonged here in the first place, but it's our job to correct history's mistakes by removing them now, even if it was past due ages ago. Down with X86!
#DownWithX86

Closing as spam/trolling. And blocked all trolls too.


Help need for running the project locally

Hello team,
Thanks @gregormendelinstitute and @MiroslavPolacek for open-sourcing this project and the documentation.
I am new to AI and ML, would be great if someone could help me run this project. I have tried running the project on an Ubuntu laptop and on an AWS ec2 instance but I am getting some errors as explained below.

WARNING: Could not find any nv libraries on this host!
/opt/conda/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:516: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint8 = np.dtype([("qint8", np.int8, 1)])
/opt/conda/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:517: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint8 = np.dtype([("quint8", np.uint8, 1)])
/opt/conda/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:518: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint16 = np.dtype([("qint16", np.int16, 1)])
/opt/conda/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:519: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint16 = np.dtype([("quint16", np.uint16, 1)])
/opt/conda/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:520: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint32 = np.dtype([("qint32", np.int32, 1)])
/opt/conda/lib/python3.6/site-packages/tensorflow/python/framework/dtypes.py:525: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  np_resource = np.dtype([("resource", np.ubyte, 1)])
/opt/conda/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:541: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint8 = np.dtype([("qint8", np.int8, 1)])
/opt/conda/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:542: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint8 = np.dtype([("quint8", np.uint8, 1)])
/opt/conda/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:543: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint16 = np.dtype([("qint16", np.int16, 1)])
/opt/conda/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:544: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_quint16 = np.dtype([("quint16", np.uint16, 1)])
/opt/conda/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:545: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  _np_qint32 = np.dtype([("qint32", np.int32, 1)])
/opt/conda/lib/python3.6/site-packages/tensorboard/compat/tensorflow_stub/dtypes.py:550: FutureWarning: Passing (type, 1) or '1type' as a synonym of type is deprecated; in a future version of numpy, it will be understood as (type, (1,)) / '(1,)type'.
  np_resource = np.dtype([("resource", np.ubyte, 1)])
Using TensorFlow backend.
/home/ubuntu

Configurations:
BACKBONE                       resnet101
BACKBONE_STRIDES               [4, 8, 16, 32, 64]
BATCH_SIZE                     4
BBOX_STD_DEV                   [0.1 0.1 0.2 0.2]
COMPUTE_BACKBONE_SHAPE         None
DETECTION_MAX_INSTANCES        100
DETECTION_MIN_CONFIDENCE       0
DETECTION_NMS_THRESHOLD        0.3
FPN_CLASSIF_FC_LAYERS_SIZE     1024
GPU_COUNT                      1
GRADIENT_CLIP_NORM             5.0
IMAGES_PER_GPU                 4
IMAGE_CHANNEL_COUNT            3
IMAGE_MAX_DIM                  1024
IMAGE_META_SIZE                14
IMAGE_MIN_DIM                  800
IMAGE_MIN_SCALE                0
IMAGE_RESIZE_MODE              square
IMAGE_SHAPE                    [1024 1024    3]
LEARNING_MOMENTUM              0.9
LEARNING_RATE                  0.001
LOSS_WEIGHTS                   {'rpn_class_loss': 1.0, 'rpn_bbox_loss': 1.0, 'mrcnn_class_loss': 1.0, 'mrcnn_bbox_loss': 1.0, 'mrcnn_mask_loss': 2.0}
MASK_POOL_SIZE                 14
MASK_SHAPE                     [28, 28]
MAX_GT_INSTANCES               100
MEAN_PIXEL                     [123.7 116.8 103.9]
MINI_MASK_SHAPE                (56, 56)
NAME                           RetrainedRings
NUM_CLASSES                    2
POOL_SIZE                      7
POST_NMS_ROIS_INFERENCE        1000
POST_NMS_ROIS_TRAINING         2000
PRE_NMS_LIMIT                  6000
ROI_POSITIVE_RATIO             0.33
RPN_ANCHOR_RATIOS              [0.5, 1, 2]
RPN_ANCHOR_SCALES              (32, 64, 128, 256, 512)
RPN_ANCHOR_STRIDE              1
RPN_BBOX_STD_DEV               [0.1 0.1 0.2 0.2]
RPN_NMS_THRESHOLD              0.9
RPN_TRAIN_ANCHORS_PER_IMAGE    256
STEPS_PER_EPOCH                1
TOP_DOWN_PYRAMID_SIZE          256
TRAIN_BN                       False
TRAIN_ROIS_PER_IMAGE           200
USE_MINI_MASK                  True
USE_RPN_ROIS                   True
VALIDATION_STEPS               1
WEIGHT_DECAY                   0.0001

Traceback (most recent call last):
  File "/home/mambauser/postprocessing/postprocessingCracksRings.py", line 112, in <module>
    from training.prepareAnnotations import prepareAnnotations
  File "/home/mambauser/training/prepareAnnotations.py", line 9, in <module>
    from lxml import etree
ModuleNotFoundError: No module named 'lxml'

Help needed here:

Not sure on how to fix ModuleNotFoundError: No module named 'lxml'

Notes:

When the --nv flag is removed the first two warnings are gone, but getting the same rest of the output.
test.tiff is a copy of this I converted to tiff using https://cloudconvert.com/tif-to-tiff
Not sure if this is the issue with my low system specifications.
I used this method to setup singularity in my machines https://github.com/apptainer/singularity/issues/5390#issuecomment-899111181

Questions:

Will this work on docker? or singularity is necessary.

Any help will be highly appreciated.
I am interested to contribute to the repo in the future.
Thanks and regards
Amal

I was able to run the project locally.
Few learnings:

I used docker to build a new image by adding the missing dependencies lxml and libiconv.
I built the new docker image in the Ubuntu desktop system with the configuration mentioned in the above comment.
The building of the docker image was not working on Mac because Micromamba requires Linux.
weightRing looks like a required field.
I was not able to access the local files in the system, so I ended up creating the input and output folder inside the docker image.


[WIP] Replace DHTMLX Accordions with Patternfly panels

Styling problem with trees when showing virtual machines:

@miq-bot assign @skateman

@miq-bot remove_label wip

Reviewed the changes, all looks good. The new patternfly panels / accordions work as expected.


PD-13194 added point cache annotations to dgp v1 and v0 decoders

Test for point cache annotation should fail atm unless we test with a dataset that actually has a point cache folder (didnt have any for testing)

a PointCache has a instance_id to make the connection to the 3D BBs


PC Oculus should bet set to 90Hz

Oculus on PC will respect target_fps as a maximum, but it will automatically turn down the fps to what ever the HMD requires.
Thus setting this to the maximum of 90Hz will allow those HMDs to run at their proper rate, and Oculus will handle reducing it for other HMDs that need a lower rate.
When this was set to 80Hz, the original Rift would run at 80Hz, increasing this to 90Hz allowed it to run at it's native refresh rate of 90.
Tested on Quest 1 and 2 via link, and Oculus automatically lowers the refresh rate to 72Hz.

Thanks!


Http Connection not getting closed ( CLOSE_WAIT)

Using OkHttp results in too many connections in CLOSE_WAIT if a service behind loadbalancer is not responding.
Seems like HttpURLConnectionImpl.getResponse() is not handling the exception scenarios.

Can you provide a short test case for this?

Below is the code, but to reproduce the issue you will need to specify the loadbalancer url with endpoint being down.
I think issue is occurs when HttpURLConnectionImpl.getResponse() throws exception during execute.
public class ReproduceLeakOkHttp {
public static final int TOTAL_RETRIES = 10;
private InfluxDB influxDB;

private RestAdapter restAdapter;

private InfluxDBService influxDBService;

@Before
public void setUp() {

    OkHttpClient okHttpClient = new OkHttpClient();
    restAdapter = new RestAdapter.Builder().setEndpoint("loadbalancerurl")
        .setErrorHandler(new ErrorHandler() {
            @Override
            public Throwable handleError(RetrofitError cause) {

                Response r = cause.getResponse();
                if (r != null && r.getStatus() >= 400) {
                    try {
                        return new RuntimeException(CharStreams.toString(new InputStreamReader(r.getBody().in(),
                            Charsets.UTF_8)));
                    } catch (IOException e) {
                        // LOG
                    }
                }
                return cause;
            }
        }).setClient(new OkClient(okHttpClient)).build();
    restAdapter.setLogLevel(LogLevel.FULL);
    influxDBService = restAdapter.create(InfluxDBService.class);
}

@Test
public void leak() {

    for (int i = 0; i < TOTAL_RETRIES; i++) {

        try {
            influxDBService.ping();
        } catch (Exception e) {

        }
    }
    System.out.println("Run netstat -an or use TCP view to monitor TCP connections");
}

private static interface InfluxDBService {

    @GET("/ping")
    public Pong ping();

    @GET("/interfaces")
    public Response version();
}

}

Does adding a timeout fix the problem?

No. The only option is to kill the client using okhttp. We have seen this issue in production and had to restart the application because OkHttp was using too many File Descriptors.
I am able to reproduce the scenario in lower environment and I can reproduce this every single time.  I have tried the similar test with Apache Http and it works without any issue,

Ahh, got it. It's a resource leak. Are you calling close() after the connection fails?

I think restAdapter does not provide access to the connection.

I think this is similar to 1502

Connections in flight are not returned to the pool until their response bodies have been consumed. Imagine a large streaming response: we don't want to buffer it; it's the application's job to close the response body.

But what happens if application is down but load balancer is returning the response. In this framework should return the connection to pool.


CORS Issue when using the latest image

Hello,
I just pulled the latest version of the docker images, and styling seems to be broken due to the fact that static assets are failing due to CORS.

I am proxying this over Apache, but it shouldn't cause a problem.
[Edit] - This seems to be happening only on Safari
Version 14.0.3 (166<IP_ADDRESS>.7)

Your originmonitoring.existanze.lan seems to be disallowing those requests. Seems to be an issue with your virtual host configuration within Apache. Might be useful to post the response headers you're seeing.

Hello @ruimarinho this is only on Safari, on Chrome it works fine. So it is not a headers issue on the proxy.

Could be related to HTTP vs HTTPS.


[WIP] Some other fixes for archive_api

I’m in the middle of a fairly major refactor of archive_api. Please can we keep these out of master, and I’ll fold them into my PRs as appropriate?

ook, but these are part of the reason why things don't talk to each other, so if they stay out of master it means what's in master stays broken


Add dynamic token precision

We have a static const VAULT_TOKEN_PRECISION_VALUE with 8 decimals for now.
We should fetch this info for respective vault token with readHederaVaultDecimals call and use the response value for the amounts formatting int <> bigint

This also should be considered for the output formatting of the tokens and balances we show in the UI.

We should swap our current formatNumberToBigint and formatBalance to viem's parseUnits and formatUnits respectively.


Update FAQ: What are Topic Tags?

Overview
While users read the FAQs, we want them to stay on CTI while they can also read the description with a source attached.
Action Items

[ ] Write copy on what are topic tags

[ ] Replace wording with the following keeping the link to the source page on the word GitHub

Github's description of the purpose of topic tags: "To help other people find and contribute to your project. You can add topics to your repository related to your project’s intended purpose, subject area, affinity groups, or other important qualities."

Resources/Instructions

FAQ Page

Notes about tracking and history (do not have to read to work this issue)

This requirement was surfaced in this issue #1096 in this comment
This issue is being tracked on Issue #1066 but is not launch critical as wording has been updated

Need access to the database in order to change the copy of the FAQ answer.


There should be a server-side version of UnitTests

This would allow AppVeyor and Travis-CI to execute some UnitTests after the compilation, allowing to see if any (server-side) regression occured.

Fixed by 6c140695c4f5a5b54eb634cabf4a4ea0b3cd51ba


Student thesis D3 is not available in Biblio, but appears in filters. Remove.

Bug description
Student thesis is not available in Biblio, but appears in filters. Remove.

Whenever we get a green flag of the biblio review team, D3 should also be gone.


API Changes: Sol-Arena

Task Description
In order to keep our API consistent with soletta's style, some changes are required in Sol-Arena.

[ ] Rename sol_arena_strndup() to sol_arena_str_dup_n()  (Tip: Use sed for this one, for more info type man sed in your terminal)
[ ] In sol_arena_slice_dup_str_n() rename the str argument to src.
[ ] In sol_arena_slice_dup_str() rename the str argument to src.
[ ] In sol_arena_slice_dup() rename the slice argument to src.

Dependencies
None.

@ceolin we can close this :)


Fix mappings

Multiple template.add_mapping calls were squashing the previous key, this patch fixes that

Hey @lrascao thanks for the PR, the code looks good - I'm a little worried that this is a change in behavior which might be used by other users of troposphere (the code for add_mapping is quite old, so there's a decent chance that someone is doing so).  Also the term add_mapping might not necessarily mean update existing mapping at first.  @markpeek any thoughts?

ping?

bump

Thanks! Sorry for the delay.


Convert to Franklin.jl?

This would be a bit of a heavy lift, I think, but it might be worth converting to a Franklin.jl site, so that we can do everything in julia. And @tlienart tends to be super helpful working out bugs.

Note: A GitHub workflow example of a Franklin.jl deployment. https://github.com/JuliaLang/www.julialang.org/blob/main/.github/workflows/deploy.yml

As a note I had started working on this myself some time ago then put it on the back burner but could resuscitate it if there is interest from devs here. Most of it is Academic template which is now mostly supported in Franklin. A couple of things that would probably require a bit of figuring out are:

dark mode (seems to be mostly a toggle in javascript with a cookie so should be mostly ok)
search (I'm not exactly sure what search this is but it's not Lunr, it's probably also one of those javascript libs)

I could get you guys started if you wanted to but I'll need help (e.g.: tracking down minor issues & checking for the two points above)

Most of it is Academic template which is now mostly supported in Franklin

Amazing! where's that development happening?

I could get you guys started if you wanted to but I'll need help (e.g.: tracking down minor issues & checking for the two points above)

Thanks so much! I'd be happy to help out with this. Regarding search - I don't know that we actually care, as long as we have something functional? Re: Dark mode - There's an example of this in https://github.com/fredrikekre/fredrikekre.se (see https://fredrikekre.se/)

where's that development happening?

https://github.com/tlienart/ft-academic-resume

Re: Dark mode - There's an example of this in https://github.com/fredrikekre/fredrikekre.se (see https://fredrikekre.se/)

yes but this typically requires a bit of care (esp around CSS) so I think it would be the kind of stuff where I'd let you guys do it and help out if you think there are Franklin-specific things that can be done to help :)

@tlienart You said you already made some progress on this - is there something I can do to help? I can try to move the content files over to that academic franklin template, but if you've already started, I don't want to reinvent the wheel.
Realistically, I'm not going to put much effort into this until the summer, so there's zero rush, just curious.

I should probably re-start this if you folks are keen, I can do some of the early work and you can do the grunt work of adding blog posts and fine tuning :)
summer sounds good! ping me if I forget but I should have the time (maybe not immediately but soon)

Mostly done in #16, but having some deployment issues https://github.com/tlienart/Xranklin.jl/issues/252

A lot of work still left to do, but I'm going to close this in favor of new issues on the current site :tada:


Fix: Hero text title

What we want :)
What we got :(

Add tailwindCSS font, add appropiate text size and attributes. Delete the hardcoded part in the current version (any left, right, transpose stuff can and should go!)

unfamiliar with tailwind but looking to learn -- it seems that most font customization in tailwind comes from applying a font from file or web font. Is there a specific font used in the top image that I should be looking for? I'll make a PR if I can get it all together

awesome! i'll see what I can do


Bug Report: Improve responsiveness of 'Blogs' page

Reproduction steps
For width less than 480px, the cards do not reduce in size to fit the entire card. Instead, a part of it cut and not visible.
Expected behavior
The card size should reduce for width less than 480px as well so that the entire card is visible.
Actual Behavior

👀 Have you spent some time to check if this issue has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

I can make the necessary changes to make the page responsive. Please assign this issue to me under GSSoC 23.

@riddhigupta1110 You can go for it.
For any help, you can reach out to me here: https://sauravmukherjee.bio.link/

I'm a GSSoC contributor ..
I would like to work on this section...
would you please assign me to this task ??


using cufflinks without credentials

is it possible to just use cufflinks without a plotly-account?

Definitely! Use the following code:
import cufflinks as cf
cf.go_offline()

thank you for the lightning-fast answer!


Feature added to accept friend request

This PR closes #953
I have added the feature to accept friend request.

@Palakkgoyal I wanted to clarify that while I did raise those issues, I hadn't yet had a chance to work on them myself. I understand that you saw the problems and wanted to help, which is commendable. However, I would appreciate it if, in the future, you could coordinate efforts before creating pull requests based on someone else's issues. It was very unprofessional of you to work on the issues before asking.
In the future, could you please ask before creating pull requests for someone else's issues? Collaboration works best when we communicate and coordinate efforts.

@Palakkgoyal I wanted to clarify that while I did raise those issues, I hadn't yet had a chance to work on them myself. I understand that you saw the problems and wanted to help, which is commendable. However, I would appreciate it if, in the future, you could coordinate efforts before creating pull requests based on someone else's issues. It was very unprofessional of you to work on the issues before asking. How can you create PRs for other's issues without even asking? I checked that you have your own pending issues. You could have worked on them to get your PRs merged.

agreed!

@Palakkgoyal I wanted to clarify that while I did raise those issues, I hadn't yet had a chance to work on them myself. I understand that you saw the problems and wanted to help, which is commendable. However, I would appreciate it if, in the future, you could coordinate efforts before creating pull requests based on someone else's issues. It was very unprofessional of you to work on the issues before asking. How can you create PRs for other's issues without even asking? I checked that you have your own pending issues. You could have worked on them to get your PRs merged.

Yes, I did a mistake to not claim the issue and I am sorry about that, as the issues that are 2 weeks or more older were stale and anyone could claim them whether they are mine and I only took those issues that were older than 2 weeks. You were creating so many issues and so so many were pending. This is also unprofessional to just create issues, get assigned and leave them. I don't mind if my issues are old, I am not working on them and just creating more and someone else take them. You also should have completed your assigned issues and create new. My only those issue are pending which I don't know how to fix.


Hello

I need to rdpwrap file for win 10 build 1809 because i cant update it in remote machine i need setup file with win 10 1809 support

Closed as not clear (no rdpconf screenshot)


Improve from skill and knowledge form elements

closes : https://github.com/instructlab/ui/issues/149

Hi, I think there are still issues with the commit history for this one.

Merge branch 'main' of https://github.com/ashapadmashetti/ui should not be needed. Your branch in your forked repository should be up to date with the parent/origin main project branch initially.
The the other commits appear to be co-signed between two accounts. Is this a mistake?

If I were you I would update your forked project main branch. Branch off this to your feature branch and then make the commits again.
Thanks for your hard work!


EwsUtilities.getPrintableTypeName() is completely broken

It appears that EwsUtilities.getPrintableTypeName() is supposed to nicely print "List" instead of the usual debug output, but it winds up throwing Exceptions instead. I'm not even going to try describing what this method was attempting to reach this goal, but needless to say, it doesn't work at all. Either this should be implemented correctly if possible or removed entirely.

From what I see, it is only used in two errormessages. And yes. it seems to be completely broken. I'll have a look at it.

+1 for complete deletion of this thing since it seems to do a lot of expensive work for only one simple message. Maybe we can just think of another suitable error-message?


Pass 'eps' option to xpdf_distill when compiling eps.

Great, thanks a lot! I use mplCairo to generate eps figures because scientific journals often require figures in eps format. And I find the mplCairo backend gives more consistent formatting and text-placement between backends than the default matplotlib backends. So thank you for your contributions!
Bug summary
Eps files are not cropped correctly
Code for reproduction
import numpy as np
import matplotlib as mpl
import matplotlib.pyplot as plt

mpl.use("module://mplcairo.base")
mpl.rcParams.update({'ps.usedistiller':'xpdf'})

x = np.linspace(0,6*np.pi,100)

fig, ax = plt.subplots()
ax.plot(x, np.sin(x))

fig.savefig('Foo.eps')

Actual outcome
Foo.eps has size 612px by 792px
Foo.pdf
Expected outcome
Foo.eps has a size 416px by 346px
Foo.pdf

Thanks for providing a reproducing example, and for your appreciation :)


Initial implementation

add the initial implementation of the c SDK, with support for query, live query and other main methods in the rust sdk

I don't know the roadmap or you guy's future plans for surreal but it seems to me like if you are already making a binding for a shared library, something most languages can directly interact with I don't see much point of just calling it "C driver", this could be as well used as a generic shared library implementation where you can later create a thin wrapper for other languages without forking this repo or needing to create different repos. Something like
/include/csharp/prodecures.cs
/include/c/prodecures.h
// etc...

Where you would build a single shared library and import the function procedures for whatever language you have, where in something like C# you could define procedures in procedures.cs:
static extern void test_query(Surreal *db);
etc.., I don't use C# but whatever a proper equivalent would be etc..
It seems to me like the only thing that qualifies this repo as a "C driver" is the fact that it generates a header file, if you want to support other language bindings than it would be more pain to maintain multiple repos and sync them, instead you could have a thin wrapper around it that languages could import the procedures of calls etc..
Like I said I don't know the roadmap of surreal, so I don't know how much you guys want to support different languages but I can't see the reason of making only the "C driver" for something that could as well be some other driver for another language very easily.


core:paste of text copied using editor:copy-selection pastes at start of line, instead of cursor.

Background
Hi, pressing ctrl-c on an empty line, copies the whole line.  Which is fine, except it deletes what's on the clipboard which is incredibly annoying.  I'd select the line if I wanted it.
A work-around, from this merge: https://github.com/atom/atom/pull/8025
and described here: https://github.com/atom/atom/issues/7103
is to use this in keymap.cson:
'atom-text-editor':
  'ctrl-c': 'editor:copy-selection'    # linux and windows

But unfortunately that pastes at the start of the line, instead of the cursor.  I'm using Atom 1.5.3 on Ubuntu 14.04.
Thanks!
Steps to Reproduce

Edit -> Preferences -> keybindings -> tiny link at top: 'your keymap file'
paste above code
Save keymap.cson
Open file.  Select some text in middle of line.  ctrl-c
Ctrl-v and it's pasted at start of line.

Expected behavior: [What you expected to happen]
pasted at cursor
Actual behavior: [What actually happened]
pasted at start of line
Versions
You can get this information from executing atom --version and apm --version at the command line. Also, please include the OS and what version of the OS you're running.
Atom 1.5.3 on Ubuntu 14.04

@lpommers @maxbrunsfeld Hey, am I using this right?  Thanks!

Copying the entire line when there is no selection is the intended behavior. If you wish to have Ctrl+C mapped to core:copy-selection for your own use, you can add the entry you give to your keymap.cson.
Please let me know if I've misunderstood your submission.

Hi @lee-dohm , I think you misunderstood.
I'm having a bug with 'editor:copy-selection'.  It pastes incorrectly.
Here's a demo video:  demo.ogv.zip
core:copy-selection has a different issue.  I'll make another issue for that.

editor:copy-selection doesn't do any pasting, so I'm not sure what you mean by "pastes incorrectly".

Yes, thank you!  I rarely think about editors my life is so full of them :-)

the suggested solution doesn't work in newer versions (e.g. ver 1.22.1), as worked before, because of different coding of the keymap.cson file:
but these steps work:
Atom -> Preferences -> Keybindings -> Click link at very top "your keymap file"
This should open a keymap.cson file in the editor.
Paste this:
'body':
  'cmd-c': 'editor:copy-selection' # mac os
  'ctrl-c': 'editor:copy-selection'    # linux and windows

(I tested it on Mac, if it doesn't work on Win, you might need to adjust 'ctrl-c' code)
P.S. if the internal coding of the keymap.cson file changes over time, you can go to
Atom -> Preferences -> Keybindings
and then you find there an entry with 'Keystroke' equal to 'cmd-c' and Selector equal to 'body'.
You should copy the code of this settting by clicking on the icon on the left of that entry-row, and use it as a model for your entry in  keymap.cson
Here is screenshot (for Mac) of the above-writen: