Fix memory issue with PHP

Fixes #64
I investigated the php memory usage and found of that the $builkQuery->toArray() continuously consume more memory
echo "\n $i query size: " .strlen(serialize($bulkQuery->toArray())) / 1024 . 'kb';

0 query size:<PHONE_NUMBER>75kb
 1 query size: 1196.4482421875kb
 2 query size: 1777.361328125kb
 3 query size: 2358.2333984375kb
 4 query size: 2942.728515625kb
 5 query size: 3523.8935546875kb
 6 query size: 4105.1845703125kb
 7 query size: 4684.66015625kb
 8 query size: 5297.61328125kb
 9 query size: 5913.3798828125kb
 10 query size: 6518.1962890625kb
 11 query size: 7125.005859375kb
 12 query size: 7702.3818359375kb
 13 query size: 8305.986328125kb
 14 query size: 8885.056640625kb
 15 query size: 9461.77734375kb
 16 query size: 10066.586914062kb
 17 query size: 10729.510742188kb
 18 query size: 11320.864257812kb
 19 query size: 11900.455078125kb
 20 query size: 12480.25390625kb
 21 query size: 13099.028320312kb
 22 query size: 13696.590820312kb
 23 query size: 14276.595703125kb
 24 query size: 14871.677734375kb
 25 query size: 15451kb
 26 query size: 16031.254882812kb
 27 query size: 16608.224609375kb
 28 query size: 17207.390625kb
 29 query size: 17789.02734375kb
 30 query size: 18366.375976562kb
 31 query size: 18943.423828125kb
 32 query size: 19548.782226562kb

It seems  $bulkQuery->reset() does not have any affect on memory releasing. After I create new BulkQuery for each BulkAction the memory usage drop significantly to amost equally same amount of memory.
 0 query size:<PHONE_NUMBER>75kb
 1 query size:<PHONE_NUMBER>5kb
 2 query size:<PHONE_NUMBER>75kb
 3 query size:<PHONE_NUMBER>5kb
 4 query size:<PHONE_NUMBER>625kb
 5 query size:<PHONE_NUMBER>75kb
 6 query size:<PHONE_NUMBER>375kb
 7 query size:<PHONE_NUMBER>5kb
 8 query size:<PHONE_NUMBER>125kb
 9 query size:<PHONE_NUMBER>75kb
 10 query size:<PHONE_NUMBER>625kb
 11 query size:<PHONE_NUMBER>25kb
 12 query size:<PHONE_NUMBER>75kb
 13 query size: 603.625kb
 14 query size:<PHONE_NUMBER>125kb
 15 query size:<PHONE_NUMBER>375kb
 16 query size:<PHONE_NUMBER>25kb
 17 query size:<PHONE_NUMBER>375kb
 18 query size:<PHONE_NUMBER>375kb
 19 query size:<PHONE_NUMBER>25kb
 20 query size:<PHONE_NUMBER>375kb
 21 query size:<PHONE_NUMBER>75kb
 22 query size:<PHONE_NUMBER>125kb
 23 query size:<PHONE_NUMBER>25kb
 24 query size:<PHONE_NUMBER>625kb
 25 query size:<PHONE_NUMBER>375kb
 26 query size:<PHONE_NUMBER>25kb
 27 query size:<PHONE_NUMBER>75kb
 28 query size:<PHONE_NUMBER>375kb
 29 query size:<PHONE_NUMBER>625kb
 30 query size:<PHONE_NUMBER>25kb
 31 query size:<PHONE_NUMBER>75kb
 32 query size:<PHONE_NUMBER>5kb

Coverage decreased (-0.09%) to 77.982% when pulling 1c02a1186325d08737779363e2506be09cbb5127 on fix-php-memory-issue into c152771dca6543ee44147ca6cb973cdfe71ef2f0 on develop.

Nice catch by the way! This should hopefully speed things up too.

Coverage decreased (-0.09%) to 77.982% when pulling a95e4bec997bc37be1dd533cfdf7b4f0b2f1935a on fix-php-memory-issue into c152771dca6543ee44147ca6cb973cdfe71ef2f0 on develop.

Coverage remained the same at 78.071% when pulling 93b07ad603effdd0d27df26f55bbef005bdab886 on fix-php-memory-issue into c152771dca6543ee44147ca6cb973cdfe71ef2f0 on develop.

Coverage remained the same at 78.071% when pulling 0609d32070087db0df83a9928ca3d40d6834c3af on fix-php-memory-issue into c152771dca6543ee44147ca6cb973cdfe71ef2f0 on develop.

Coverage remained the same at 78.071% when pulling 53b2d6c291a275137b2f2195b3b0a4fdc7e4cced on fix-php-memory-issue into c152771dca6543ee44147ca6cb973cdfe71ef2f0 on develop.

Coverage remained the same at 78.071% when pulling 0b84b0137aff3131897494ebe6b36488fae61d1e on fix-php-memory-issue into c152771dca6543ee44147ca6cb973cdfe71ef2f0 on develop.

Coverage remained the same at 78.071% when pulling 3c2329faeb6b29d68d60f0cc191ce79d630e6d21 on fix-php-memory-issue into c152771dca6543ee44147ca6cb973cdfe71ef2f0 on develop.

@Jalle19 Ready to merged now 🚀

I've turned off the Coveralls comment spam for this repo, but we'll still get coverage reports via the Status API for each commit.

@Jalle19 I think I didn't really solve the problem. Close the PR for now.


Undefined behavior error for UISearchController

In my project I have a Table View Controller embedded in a Navigation Controller. I am launching the LocationPickerViewController via a button in the navigation bar.
Sometimes when I don't select any location and go back to the previous screen and again come to the Location Picker scene the following error is printed to the console:

Attempting to load the view of a view controller while it is deallocating is not allowed and may result in undefined behavior (<UISearchController: 0x14a851f90>)

Searching the web, I found this stackoverflow answer which recommended to call the loadViewIfNeeded() method of the UISearchController in the class' deinit.
I added it as follows in LocationPickerViewController:
	deinit {
		searchTimer?.invalidate()
		localSearch?.cancel()
		geocoder.cancelGeocode()
        searchController.loadViewIfNeeded() // Added call to loadViewIfNeeded()
	}

The error does not appear anymore after this. Maybe this call to loadViewIfNeeded() needs to be added.

Thanks for reporting, closed by 13c8a7a6e91adc20d89786757082b01ceb202cb1.


cdc: update info message for ‘/api/v2/changefeeds/{changefeed_id}/synced’

What problem does this PR solve?

Issue Number: ref https://github.com/pingcap/tiflow/issues/10289
What is changed and how it works?
update info message to make more clear
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
Please refer to [Release Notes Language Style Guide](https://pingcap.github.io/tidb-dev-guide/contribute-to-tidb/release-notes-style-guide.html) to write a quality release note.

If you don't think this PR needs a release note then fill it with `None`.

/retest


GEOMESA-1480 KafkaDataStore - fixing spatial queries against non-default geometries

Signed-off-by: Emilio Lahr-Vivaz<EMAIL_ADDRESS>

@elahrvivaz this looks good to me.
@mdzimmerman can you read through briefly and comment?  Also, if you have a chance, can you check out the downstream projects which might be affected by the 'getIterator' -> 'toIterator' change?

Doesn't affect Iktomi, which uses the public GeoTools interface. Checking geomesa-tutorials next.

geomesa-tutorials works fine too.

looks good

@elahrvivaz mind rebasing this to remove the conflict?

merge conflict resolved


racer.racerBinPath is not set in your config.

[Enter steps to reproduce below:]

...
...

Atom Version: 1.7.2
System: Microsoft Windows 10 Pro
Thrown From: Atom Core
Stack Trace
racer.racerBinPath is not set in your config.
At undefined

undefined

Commands
     -0:24.5.0 editor:newline (atom-text-editor.editor.is-focused)
     -0:24.1.0 core:move-up (atom-text-editor.editor.is-focused)

Config
{
  "editor": {
    "fontSize": 19
  }
}

Installed Packages
# User
d-struct, v1.0.4
language-d, v3.2.2
language-rust, v0.4.6
racer, v0.20.0

# Dev
No dev packages

This is a duplicate of edubkendo/atom-racer#64 - feel free to subscribe there for updates.


fix korean translation of bezier method reference

Fixes #943
Changes:
https://p5js.org/ko/reference/#/p5/bezier
fix the mistranslation of bezier method parameters.

thank you so much @sosunnyproject!
we added you as a contributor here
https://github.com/processing/p5.js
:)


Attaching user interaction spans and initial load span

Is your feature request related to a problem? Please describe.
I'm encountering a use-case where it'd be handy if I could view both initial load data as well as custom spans together. Right now, any custom spans appear separately from the initial load data.
Describe the solution you'd like
I'd like to have some global span that gets started automatically via the initial load, but then requires manual closing. The initial page load span can live under that global span, and any user interaction or custom spans will live under that global span as well.
Describe alternatives you've considered
I've been digging through the code to see if it should already be possible to do this, but it was not able to find a solution.

May have figured a way to make this happen:
import { tracing } from "@opencensus/web-core";
import { OCAgentExporter } from "@opencensus/web-exporter-ocagent";
import {
  getPerfEntries,
  getInitialLoadRootSpan
} from "@opencensus/web-instrumentation-perf";

const TRACE_ENDPOINT = "/v1/trace";

tracing.registerExporter(
  new OCAgentExporter({
    agentEndpoint: `${window.ocAgent}${TRACE_ENDPOINT}`,
    serviceName: window.ocServiceName
  })
);

let rootSpan = getInitialLoadRootSpan(tracing.tracer, getPerfEntries());

setTimeout(() => {
  rootSpan.end();
}, 5000);

setTimeout(() => {
  let childSpan = tracing.tracer.startChildSpan({
    name: "child-1",
    childOf: rootSpan
  });

  setTimeout(() => {
    childSpan.end();
  }, 500);
}, 1000);

Seems to allow exporting initial page load as well as custom events under the same root.


added option to pass caps in the settings variable

CrossBrowserTesting.com has extra optional selenium caps ( "screen_resolution", "record_video", "record_network"). We at least need the ability to pass the screen_resolution into the desiredCapabilities.

Sorry. I realized that you can pass additional options with the settings variable already.


create a new document containing all errata and additions to RFC 8794

As discussed during our last IETF meeting, this should go in a new document which not an errata document nor a replacing RFC.
We need to collect all the PRs with errata label and put them in a new generated document.

@SpencerDawkins sent a proposal for the format to follow with this document.

Some followup emails on how to handle it: https://mailarchive.ietf.org/arch/msg/cellar/kCL24UZRcv-ySh3FTbPljNOlkQI/

It looks like we should push this further. That may be needed to update the IANA registry. And IMO we should also do #164 so we can use it in Matroska v5.


Fix CI builds

I fixed the Linux and Mac Clang builds of the project.
As far as I can tell, the Conan package for SFML is incompatible with GCC on Mac. The package specifies the compiler flag -stdlib=libc++, which applies to Clang but not GCC. I removed the Mac GCC build entirely. I really don't like this solution, but I'm not seeing any other option here.

thanks! That had been on my to-do list


Set default less and css to new default name

Remove mentions to Gogs on js, css and less files, generated with lessc 2.7.1

Current coverage is 2.21% (diff: 100%)

Merging #54 into master will increase coverage by 0.02%

@@            master       #54   diff @@
========================================
  Files           31        31
  Lines         7508      7508
  Methods          0         0
  Messages         0         0
  Branches         0         0
========================================
+ Hits           164       166     +2
+ Misses        7327      7326     -1
+ Partials        17        16     -1

Powered by Codecov. Last update 137dcbf...30ae023

LGTM

LGTM

Done, with rebase

LGTM

LGTM

LGTM

LGTM


Copyright warning for beta flavor

What is the user problem or growth opportunity you want to see solved?
We have a first-time tutorial, but many beta users seem to believe that it is does not apply.
In fact, the beta server is also very strict on copyright.
Recently two users of the beta flavor of the app uploaded copyrighted images and got banned.
Most beta users probably do not read the wiki nor any documentation, and just git clone from GitHub then run the app and upload test pictures.
For the beta flavor only, I suggest adding a popup at the beginning of the first-time tutorial that says:
Please only upload pictures you have taken by yourself.
Uploaders of copyrighted images will be blocked.
This applies to the beta flavor too.
Thank you for testing the app!

How do you know that this problem exists today? Why is this important?
No response
Who will benefit from it?
No response
Anything else you would like to add?
No response

I would like to work on this issue please assign me

Wow🤔

@Rishavgupta12345 Just show the popup on the first page of the first-time tutorial. No relation with the peer review feature. Thanks!

@nicolas-raoul  you have suggested adding a popup in the first time tutorial for copyright, but I have seen that popup works only when there is a button click, but there is no button click so should I add a new layout that gives the copyright message just like as other things in the first time tutorial

"I have seen that popup works only when there is a button click"

What do you mean? Could you please giving us an Android documentation page explaining this?


Simplified macOS warning

I figured as I go through your book I should probably help as I go a long.
With this change I tried to distil the macOS changes down to the minimum. This book is very dense as it is, and I figured less is more :)

I didn't realize adding more commits to my fork would also update the pull request.
How to do you feel about having Kotlin code samples as well? :)

No Kotlin, please :D. I have more than enough in maintaining just Java code....

Thanks!!


Question: recommended CustomDumpFlags when full dump is not possible?

I have a somewhat niche question about using PyExt: can I use !pystack on dump files that are not full dumps but have CustomDumpFlags set so that autoInterpreterState is still available to PyExt? (It's possible that the answer is "no, full dumps are required", which is fine, I just wanted to confirm this.)
Here is the motivation: I am troubleshooting an intermittent stack exhaustion issue (STATUS_STACK_OVERFLOW, ExceptionCode c00000fd) in a PyQt5 program running Python 3.6. I think it might be caused by a race condition that occurs while updating one of the PyQt widgets, but that is pure conjecture at this point. Windows Error Reporting creates the default MiniDumps that are about 18 MB in size, but when I try enabling full dumps by setting DumpType to 2 the machine locks up for many hours trying to write the dump file to disk. (I rebooted the machine after about 6 hours when it crashed overnight and it had managed to write about 330 MB to disk, but unsurprisingly WinDbg could not load the partially written dump file. If nothing else I could just let it run indefinitely to try to get a full crash dump, but the machine is unusable in this state so this is not ideal.) When I load the MiniDumps into WinDbg it warns me that "Only registers, stack and portions of memory are available" and unsurprisingly when I use PyExt on the MiniDump files I get the expected error message that others have seen:
0:000> !pystack
Thread 0:
ERROR: !pystack: extension exception 0x80004005.
    "ExtRemoteTyped::Field: unable to retrieve field 'tstate_head' at 70d76350"

I've made one attempt at setting CustomDumpFlags to enable MiniDumpFilterMemory, MiniDumpWithProcessThreadData, MiniDumpWithThreadInfo, and MiniDumpWithCodeSegs, but that was not sufficient for PyExt and I'm not sure which flag to enable to ensure that autoInterpreterState is available. Is MiniDumpWithFullMemory absolutely required or will another flag suffice?
I should also mention that otherwise PyExt works splendidly on this program; when I attach WinDbg to a running process I can see the stack just fine, for example:
0:020> .load pyext
0:020> ~*e!pystack
Thread 0:
	File "C:\Users\NV Confocal\anaconda3\envs\original\lib\site-packages\pyqtgraph\widgets\GraphicsView.py", line 154, in paintEvent
		[Frame] [Globals]
	File "C:/Users/NV Confocal/Documents/original/gui/mainexp_gui.py", line 3085, in main
		[Frame] [Globals]
	File "C:/Users/NV Confocal/Documents/original/gui/mainexp_gui.py", line 3089, in <module>
		[Frame] [Locals] [Globals]
<snip>
Thread 6:
	File "C:\Users\NV Confocal\anaconda3\envs\original\lib\socket.py", line 205, in accept
		[Frame] [Globals]
	File "C:\Users\NV Confocal\anaconda3\envs\original\lib\site-packages\rpyc\utils\server.py", line 140, in accept
		[Frame] [Globals]
	File "C:\Users\NV Confocal\anaconda3\envs\original\lib\site-packages\rpyc\utils\server.py", line 264, in start
		[Frame] [Globals]
	File "C:\Users\NV Confocal\anaconda3\envs\original\lib\threading.py", line 864, in run
		[Frame] [Globals]
	File "C:\Users\NV Confocal\anaconda3\envs\original\lib\threading.py", line 916, in _bootstrap_inner
		[Frame] [Globals]
	File "C:\Users\NV Confocal\anaconda3\envs\original\lib\threading.py", line 884, in _bootstrap
		[Frame] [Globals]

I would be happy to pass along any of the raw dump files if they would be of any use. Let me know if any other information would be of use, this sort of debugging is not my area of expertise and I may be missing something obvious.
Version information:

PyExt version 0.1.60 (latest, July 1)
WinDbg client version 1.2407.24003.0
WinDbg engine version 10.0.27668.1000
PyQt 5.9.2
Python 3.6.13

Related reports:

https://github.com/SeanCline/PyExt/issues/3

Hi Nathaniel,
Unfortunately, the only way I know to reconstruct a stack trace is to create a full dump. The automated tests use MiniDumpWithFullMemory for this exact reason.
This is because CPython stores its bookkeeping data all over the address space. Some stuff is stored on the stack and doesn't present a huge problem, but things like the PyThreadState (which holds the tstate_head) are on the heap.
No promises, but if you can get a hold of a pointer to the PyFrameObject at the top of the stack you're interested in, you could pass it into !PyStack so it doesn't have to track down the PyThreadState. That will likely run into the same issue of needing heap data, so it might not even be worth the effort.
But back to the problem at hand -- slow dumps.
Setting WER's DumpType to 2 (Full dump) has always worked well for me so I wonder what's tripping it up in your situation.
Whenever I need custom rules for when to generate a dump, I set up DebugDiag. You can tell it to generate dumps on STATUS_STACK_OVERFLOW and hopefully it'll work better that WER.
Alternatively, you could attach WinDbg and let it break when the stack overflow happens and run !PyStack from there.

@SeanCline Thanks so much for the response!

@nbeaver No worries. Let me know how you make out with either DebugDiag or Windbg.
If neither works out, I could try taking a peek at one of your minidumps to see if there's any evidence on the native stack of where it is in Python code.

@SeanCline Attaching WinDbg to the process, letting it break, and running !PyStack from there was the ticket. Writing a full dump file is still a no-go (I'm guessing because the call stack is over 200 levels deep) but the main thing is I can see where in the code this is happening, which will go a long ways towards fixing the issue. Thanks again!


clipPath support

I don't see anywhere in document. Is clipPath supported?

Yes,you can find the usage in the example

thanks


of views & listens by album and song

Hey,
I noticed Spotify's API does not have sales and/or listens by album and song. Is that true? If so, where could I retrieve this data from?

Since this is related to the web API, it's better if you ask this in https://github.com/spotify/web-api/


v1.5.0

This branch switches cache busting via query strings to cache busting via asset hashing file names.

:rocket:


Add oci gen ai support

Adding support to OCI Gen AI Services https://www.oracle.com/artificial-intelligence/generative-ai/generative-ai-service/
Just two simple functions:
oci_list_models -> Returns available model per region/compartment
oci_embed -> Return a vector from a string

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @adrianotanaka, sorry for the delay on this PR.
We have been in focus mode but we will be reviewing this shortly. 🙏

Thanks @smoya , please let me know if I can help with anything.

Hey @adrianotanaka I'm really sorry for the late response. We were on focus mode for the vectorizer work. We are also figuring and add more structure to the way we want to interact with the community, and how to handle, contributions. Expect some new guides, and guidelines coming soon.
Regarding your PR. You should not put SQL code directly in the ai--0.3.0--0.4.0.sql file. You need to add a new file projects/extension/sql/idempotemp/015-oci.sql, add your functions there. This is explained in:
https://github.com/timescale/pgai/blob/main/DEVELOPMENT.md#develop-sql-in-the-pgai-extension
Give it a read, and please if you have any feedback please share.
Since you're importing the oci package, you need to follow the guidelines Develop Python in the pgai extension
, basically you need to add oci as a dependency in the requirementes.txt file:
https://github.com/timescale/pgai/blob/main/projects/extension/requirements.txt
And add #ADD-PYTHON-LIB-DIR as a header in your functions before the import oci, see an example from openAI's embed function:
https://github.com/timescale/pgai/blob/main/projects/extension/sql/idempotent/001-openai.sql#L70
Once you have that, run just ext build-sql and that will generate some sql files like ai--0.4.2-dev.sql, and the upgrades from all the old versions to the new version ai--0.4.1--0.4.2.sql, .... For some reason, might be a bug, or by design, these files are gitignored, you'd need to manually add them to your changes.
Last thing (I think), you need to add some tests for the code, some docs about it:
https://github.com/timescale/pgai/blob/main/projects/extension/sql/idempotent/001-openai.sql#L70
And you can follow the openAI's tests as a guide:
https://github.com/timescale/pgai/blob/main/projects/extension/tests/test_openai.py
Hope this helps, and sorry again for the late response.


Liqo Terraform/Helm installation

Hi, as we are investigating the Liqo implementation for our school project, we had some issues related to Liqo automation!
While deploying the Liqo into EKS by using Helm chart (automated by Terraform), when installing the liqo using
liqoctl install eks --only-output-values
to extract the values.yml and use it with Terraform the following issues occurred:
"│ Warning: Helm release "liqo" was created but has a failed status. Use the helm command to investigate the error, correct it, and then run Terraform again.
│
│   with helm_release.liqo,
│   on helm_release.tf line 45, in resource "helm_release" "liqo":
│   45: resource "helm_release" "liqo" {
│
╵
╷
│ Error: timed out waiting for the condition
│
│   with helm_release.liqo,
│   on helm_release.tf line 45, in resource "helm_release" "liqo":
│   45: resource "helm_release" "liqo" {"
And this is correlating to the Terraform script about the Helm:
provider "helm" {
  kubernetes {
    host                   = data.aws_eks_cluster.eks-cluster.endpoint
    cluster_ca_certificate = base64decode(data.aws_eks_cluster.eks-cluster.certificate_authority.0.data)
    exec {
      api_version = "client.authentication.k8s.io/v1alpha1"
      args        = ["eks", "get-token", "--cluster-name", data.aws_eks_cluster.eks-cluster.name]
      command     = "aws"
    }
  }
}
...

resource "helm_release" "liqo" {
  name        = "liqo"
  chart       = "liqo"
  repository  = "./charts"
  namespace   = "liqo"
  version    = "v0.4.0"
  max_history = 3
  create_namespace = true
  wait             = true
  reset_values     = true
  # set {
  #   name  = "controller.service.type"
  #   value = "NodePort"
  # }
}

We're expected to make the automation progress successfully by using Helm chart and terraform
To recreate this issue:
Create a simple cluster on EKS and have the extracted chart value from deployment/liqo and use it with Terraform deployment on AWS.
The code is used for this project is in the following link:
https://github.com/AndyHoang29/Liqo-automation-testing
Environment:

Liqo version: v0.4.0
Kubernetes version (use kubectl version): Client version "v1.22.5"
Cloud provider or hardware configuration: AWS
Install tools: Terraform, kubectl, AWS CLI

Hi @AndyHoang29,
Most likely, the issue you reported is relate to a bug in the logic used by the liqo Helm chart to decide whether to use production or development images, in case you do not use the upstream chart. You can confirm this by checking that the pods that are reporting an ImagePullBackOff status have images ending in -ci, although they shouldn't.
We fixed this problem (#1265) through an improved logic to decide whether to add the suffix or not, which will be included in the next release. In the short term, you can fix this issue backporting that change to your local copy of the chart, or uncommenting this line and configuring v0.4.0 as appVersion (i.e., the same as the tag entry in the values.yaml file).

Hi @giorio94,
Thank you for your support in resolving the issue. But after successful automation installation, I have an issue with the liqo-auth service in the cluster, which does not allow the Liqo app to work. I also tried to investigate what was happening, the image2  and image3 send to me a CrashLoopBackOff.
Note:
I also have updated my code by following your instruction.
Hope to hear from you soon
Thank you in advance!

Could you please check and post the logs of the liqo-auth service, to help troubleshooting the problem?
In the meanwhile, looking at the values file in your repo (and especially in the awsConfig section), the accessKeyId and secretAccessKey fields are empty. This definitely makes sense, as those should not be shared on a public registry. Still, I just wanted to make sure you are configuring them when running the deployment process.

Thank you for your information!
After tracking the logs for the liqo-auth service, I finally figured out the error by the following image, which I haven't provided the API server address in the values.yaml file
And I also do have some questions related to the chart value:

Is there any way that the chart value file can auto-generate the API server address for Liqo?
As you have mentioned to me in the comment above, I already have provided AWS config section before deploying. But is there any chance that the value.yaml file can automate/create a random accessKeyId and secretAccessKey fields?

Thank you for your information! After tracking the logs for the liqo-auth service, I figured out the error by the following image, which I haven't provided the API server address in the values.yaml file.

Glad you solved the problem.

And I also do have some questions related to the chart value:
1. How can I receive the appropriate API address for the value and can the chart auto-generate the API server address? (I think it is not safe by providing the API address during the deployment)

Liqo needs to know a reachable URL of the kubernetes API server, since this is leveraged by remote peered clusters. With on-prem clusters, liqo attempts to infer the API server url based on the control plane node addresses. Yet, this is not possible with public cloud clusters, since that is an external components (hence the reason for the failure you observed).
In case you use liqoctl to perform the installation (or generate the Helm values file), that value is typically retrieved from the kubeconfig that is being used, or the cloud provider APIs, but that is not possible with plain helm templating. Differently, you have to specify it yourself. I suppose there should be some way in terraform to extract that API server URL and use it in the values.yaml file, but I have no experience in that direction.
Finally, I do not think that should be considered a strictly secret value, since the API server is nonetheless protected by standard Kubernetes authn/authz mechanisms.

2. As you have mentioned to me in the comment [above](https://github.com/liqotech/liqo/issues/1263#issuecomment-1149988963), I already have provided [AWS config section ](https://github.com/AndyHoang29/Liqo-automation-testing/blob/5eb183737a6f99fa87004dea2856e4b5beb24c56/Liqo%20automation%20project/charts/liqo/values.yaml#L24-L28)before deploying. But is there any chance that the _value.yaml_ file can automate/create a random `accessKeyId` and `secretAccessKey` fields?

No, this is not possible, since you would need to specify more privileged credentials to be able to generate the ones actually used. This is exactly what liqoctl does for you (if you do not provide pre-configured credentials), but that is a tool meant to be executed on your machine, and granted the proper privileges.


Realsense Gazebo Plugin: submit upstream

[x] Move code out of coav's repo
[ ] Format it according to Gazebo's standards
[ ] Submit upstream

Repo https://github.com/01org/gazebo-realsense created, so the code can be moved out of collision-avoidance-library repo. Later, this code will need to be adapted to Gazebo's standards to be submitted upstream.

#90 Move code to its own repo

Previous PR submitted (declined due to non-technical issues): https://bitbucket.org/osrf/gazebo/pull-requests/2366/an-intel-real-sense-r200-camera-plugin/diff

@anselmolsm As per discussion in above PR (https://bitbucket.org/osrf/gazebo/pull-requests/2366/an-intel-real-sense-r200-camera-plugin/diff) it cant be merged due to copyright issues and it was to agreed to submit as plugin.
So can we close this issue?

@avinash-palleti what blocked that PR was what I called "non-technical issues" in my previous comment.
The copyright  / CLA thing has been discussed and solved. Thus, this task is still open.


use TRC of --source-gamut-icc as device EOTF

Gamma of modern OLED displays with high contrast and dark black level is close to pure 2.2-2.3. sRGB defines black level as 0.2cd/m2 (flare 1%), "ideal" sRGB display must set contrast to 1:400. That is why sRGB has linear segment near zero. BT.1886 says that EOTF of displays with higher contrast must be pure power function. To make it possible to generate MHC-ICC-profiles with CSC to sRGB with pure gamma 2.2 we can use gamma of ICC-profile passed as argument to parameter --source-gamut-icc. So one can create syntenic ICC-profile with gamma 2.2 and use it with high-contrast OLED display.

I verified my display (DELL XPS 15 9520, SDR). I've used X-rite i1 Display with adjustment matrix created with X-rite ColorMunki.
ICC-profile with calibration to gamma 2.2 (shaper-only profile created with colprof -as):
targen -v -d3 -e1 -B1 -m6 -g100 -f0 -W verify
cp verify.ti1 ref.ti1
fakeread -v "sdr-2023-12-06-6500-g2.2.icm" "ref"
cp verify.ti1 measure.ti1
dispread.exe -v -X ccmx10bit.ccmx measure
colverify.exe -v 2 -s -k -N ref.ti3 measure.ti3

Verify results:
  File 1 L*a*b* ref. XYZ 95.486500 100.000000 109.377000
  File 2 L*a*b* ref. XYZ 108.584831 114.091841 125.234796
  Total errors (CIEDE2000):     peak = 1.789642, avg = 0.603097
  Worst 10% errors (CIEDE2000): peak = 1.789642, avg = 1.276646
  Best  90% errors (CIEDE2000): peak = 1.000323, avg = 0.529316
  avg err X  0.005333, Y  0.004399, Z  0.002786
  avg err L* 0.372157, a* 0.564666, b* 0.583094

ICC-profile is quite accurate.
sRGB emulation with MHC2Gen:
MHC2Gen.exe sdr-csc "sdr-2023-12-06-6500-g2.2.icm" "_CSC-sRGB-orig.icm" --source-gamut sRGB --profile-desc "_CSC-sRGB-orig.icm"
targen -v -d3 -e1 -B1 -m6 -f0 -p 2 -W _verify_srgb
cp .\_verify_srgb.ti1 _ref_srgb.ti1
fakeread -v '.\sRGB Color Space Profile.icm' .\_ref_srgb
cp _verify_srgb.ti1 _measure_srgb.ti1
dispread.exe -v -X ccmx10bit.ccmx _measure_srgb
colverify.exe -v -s -k -N _ref_srgb.ti3 _measure_srgb.ti3

No of test patches = 216
File 0 Chose patch 1 as white, XYZ 95.054000 99.997100 108.930000
File 1 White is from display luminance ref. XYZ 106.837293 113.210102 123.816579
L*a*b* white reference = XYZ 0.964203 1.000000 0.824905
No of test patches in worst 10% are = 22
No of test patches in best 90% are = 194
Verify results:
  File 1 L*a*b* ref. XYZ 95.054000 99.997100 108.930000
  File 2 L*a*b* ref. XYZ 106.837293 113.210102 123.816579
  Total errors (CIEDE2000):     peak = 6.821777, avg = 0.876519
  Worst 10% errors (CIEDE2000): peak = 6.821777, avg = 2.640756
  Best  90% errors (CIEDE2000): peak = 1.981422, avg = 0.676450
  avg err X  0.002263, Y  0.002342, Z  0.003046
  avg err L* 0.415378, a* 1.097902, b* 1.212849

Create MHC-ICC-profiles emulated sRGB and verify them against reference sRGB profiles.
sRGB gamma 2.2 emulation with modified MHC2Gen:
&"MHC2\MHC2Gen\bin\x64\Debug\net7.0\MHC2Gen.exe" sdr-csc "sdr-2023-12-06-6500-g2.2.icm" "_CSC-sRGB-preserve_gamma.icm" --source-gamut-icc sRGB-g2.2.icm --profile-desc "_CSC-sRGB-preserve_gamma.icm"
cp .\_verify_srgb.ti1 _ref_srgb_22.ti1
fakeread -v .\sRGB-g2.2.icm .\_ref_srgb_22
cp _verify_srgb.ti1 _measure_srgb_22.ti1
dispread.exe -v -X ccmx10bit.ccmx .\_measure_srgb_22
colverify.exe -v -s -k -N _ref_srgb_22.ti3 _measure_srgb_22.ti3

No of test patches = 216
File 0 Chose patch 1 as white, XYZ 95.045400 100.000000 108.905000
File 1 White is from display luminance ref. XYZ 107.370575 113.884910 124.632632
L*a*b* white reference = XYZ 0.964203 1.000000 0.824905
No of test patches in worst 10% are = 22
No of test patches in best 90% are = 194
Verify results:
  File 1 L*a*b* ref. XYZ 95.045400 100.000000 108.905000
  File 2 L*a*b* ref. XYZ 107.370575 113.884910 124.632632
  Total errors (CIEDE2000):     peak = 6.978121, avg = 0.692786
  Worst 10% errors (CIEDE2000): peak = 6.978121, avg = 2.314104
  Best  90% errors (CIEDE2000): peak = 1.408896, avg = 0.508925
  avg err X  0.002057, Y  0.002327, Z  0.002801
  avg err L* 0.358454, a* 0.767816, b* 0.807251

The latest profile with gamma 2.2 is a little more accurate than profile with gamma sRGB. What do you think about it? Can DeGamma/ReGamma be pure 2.2 from EDID? Here is said that this functions are controlled by driver and can be sRGB.

My experiments show using gamma 2.2 will result in a higher delta-E when proofing sRGB gamut with MHC2 CSC on a P3 display. (still in the acceptable range, though)
Verification reports for reference: mhc2-g22-exp.zip

I think it makes sense to estimate errors in DE in pipeline : gamma 2.2 -> degamma sRGB -> CSC -> gamma sRGB -> 1dlut to gamma 2.2.

I estimated error in the pipeline with the following code:
def mhc_srgb22_to_xyz(srgb_gamma22):
    # embedded into pipeline
    source_rgb_lin = [srgb.EOTF(x) for x in srgb_gamma22]
    xyz = dci_p3.RGB_to_XYZ @ source_rgb_lin
    # CSC to sRGB
    user_matrix = srgb.RGB_to_XYZ @ dci_p3.XYZ_to_RGB
    xyz_csc = user_matrix @ xyz
    # embedded into pipeline
    target_rgb = dci_p3.XYZ_to_RGB @ xyz_csc
    target_rgb_xfer = [srgb.OETF(x) for x in target_rgb]
    # interpret as encoded with gamma 2.2
    display_rgb = [srgb_g22.EOTF(x) for x in target_rgb_xfer]
    display_xyz = dci_p3.RGB_to_XYZ @ display_rgb
    return display_xyz

Optimization showed that max error is 2.2DE for color Lab [ 38.,  47.,  51.] that is displayed as Lab [ 38.,  47.,  56.].
My display gamut is close to DCI P3. Real measurements of color Lab [ 38.,  47.,  51.] in Photoshop:

MHC2 profile with CSC to sRGB with standard gamma: Lab 37.898758 46.690806 51.098780
MHC2 profile with CSC to sRGB with gamma 2.2: Lab 38.064040 46.754568 55.552657

This is in complete agreement with the calculations. Probably, this error is acceptable for most users who use their displays in dark environment.


Make navbar fixed

hey @QAZIMAAZARSHAD, I would like to make the navbar of the website fixed and sticky on top. Please assign this to me

@archanagandhi this issue is already open. See issue number https://github.com/QAZIMAAZARSHAD/Movie-Streaming-Website/issues/33.
Before opening any issue always make sure that no other similar issue is open.


Fix parsing of ZWJ emojis

We needed to prioritize matches by length so the smaller emojis wouldn't
be consumed individually first.


Goaccess takes long time to quit

There is a considerable time delay before goaccess closes once I send SIGINT to it. Is there any way to skip whatever it is doing throughout that time (other than killing it)? I need to start a new instance on the same port as soon as possible. Right now I use a slight time delay, around 2 minutes just to be sure.
I tried using --keep-db-files and it still takes long. I need it to reset at midnight to show statistics for the current day or, better, display only the last 24 hours. None of these two things seem to be possible currently with realtime html.

Can you please post the exact command you are running so I can try to reproduce this from my end? Thanks.

I run it like this with only log format specified in goaccess.conf:
/usr/bin/goaccess -f /storage/log/nginx/example.com/nginx-access-current.log --real-time-html --ws-url=ws://logs.example.com:80/ws2/ --port=8010 --ignore-crawlers -o /storage/goaccess/index.html --db-path=/storage/goaccess --origin=http://logs.example.com --fifo-in=/tmp/wspipe2.in --fifo-out=/tmp/wspipe2.out

This was apparently due to using the on disk database that is the default in Debian's package.
I switched to goaccess repo to install the newest goaccess and now it doesn't create any database on the disk, which is good for me. What CLI switch actually controls this, if I may ask? Could you make it more apparent in the manual? For some reason Debian's package does not use in-memory hash tables by default.

What do you mean? I just did apt install goaccess.

My guess is that you are using goaccess with the on-disk storage. You can run goaccess -s to find out. I'd try installing goaccess from the official deb repo  and see if that solves the issue. Please let me know how it goes. Thanks.

Yes it did solve the issue. As I said in my last message:
This was apparently due to using the on disk database that is the default in Debian's package.
I switched to goaccess repo to install the newest goaccess and now it doesn't create any database on the disk, which is good for me. What CLI switch actually controls this, if I may ask? Could you make it more apparent in the manual? For some reason Debian's package does not use in-memory hash tables by default.
So basically I just asked if you could make it clearer in the manual how to switch the storage backend because I still honestly don't know. I am just glad that it works :D
Thanks for the awesome app, I love the visual design.


A humble feature request: Insertion of extra points

Thank you for an excellent library!
I have a use case where I would like to add elevation points at specific locations. For example, after having run the simplifier, I would like to insert some extra points (that I select) from the heightmap into the triangulation to have maximum accuracy (ie full resolution) there.
I have had a look at the code (src/triangulator.cpp) but cannot quite find out how to proceed. It seems the triangulation process (in Triangulator::Step()) is triangle-driven, ie it starts with a candidate triangle (the one having the maximum vertical error to a vertex), finds the candidate point for that triangle, inserts it and re-triangulates.
Do you know of a way to start with a point instead? I have thought of somehow marking the triangle containing each extra points with a very high dummy error value, and then proceed from there, but it seems I would then need to find the enclosing triangles for all of those extra points. Is there a simpler way?
It might be sufficient for my use case to use a bounding box to define the extra points, and then the error calculation / candidate finding process could perhaps be overridden with an extra criterion, for example: If a given point is inside that bounding box, then don't calculate the vertex-to-plane distance, instead just set it to some max value - and/or add the point directly to the candidate queue. Do you see other options?
With a little bit of input on how to approach this I could likely implement the solution myself and post it here as a PR.

Ok! Thanks for your suggestion!


Handshake failed after updated to okhttp 3.14.0

When I use okhttp 3.12.2, I can make a GET request on https web site.
After upgrading to okhttp 3.14.0, I have an IO exception on execute when I perform the same GET request. The interceptor message indicates "handshake failed".
request = new Request.Builder().url("https://anhttpswebsite").build(); response = client.newCall(request).execute();

Can you run a report for the site with https://www.ssllabs.com/ssltest/

Hi,
here is the result.
Christian
Le sam. 30 mars 2019 à 13:33, Yuri Schimke<EMAIL_ADDRESS>a
écrit :

Can you run a report for the site with https://www.ssllabs.com/ssltest/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/square/okhttp/issues/4823#issuecomment-478241544, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALlJqCPOGgTG7RJov-GJhU6E3i8QU3KYks5vb1l9gaJpZM4cTtU6
.

Hi Yuri, I sent the report via email (using reply button)

Hi,
my email isn't<EMAIL_ADDRESS>I suggest asking this sort of question on stackoverflow, most likely it's related to the server using insecure ciphers etc.

Ok, I understand the server makes the  problem, but why using okhttp 3.12.2 there is no handshake failed and using 3.14.0 there is a handshake failed ?
I' not sure I can get help on stackoverflow !

In between those versions we dropped support for older unsupported versions of TLS
https://github.com/square/okhttp/blob/master/CHANGELOG.md
"TLSv1 and TLSv1.1 are no longer enabled by default"
But we are not setup to provide 1:1 support when often the fix is to upgrade your server etc, so you should use stackoverflow and make sure all relevant information is in the question you ask on stackoverflow.  There are a lot more people seeing your question there, than a bug tracker here.

Good to remove TLS 1 and TLS 1.1
But the server I try to connect uses 1.1 and 1.2
I also use Chrome 73 and I can access the website (since Chrome 72, TLS 1 and 1.1 are not supported anymore), so it shows that the server is accessible via TLS 1.2
I don't request a 1.1 support, and I can't upgrade the server (which is not mine !), anyway the server is TLS 1.1 and 1.2 so Chrome is working fine, okhttp 3.12.2 is working fine, okhttp 3.14.0 is not working...
I don't request any support, I just want to report my problem, that's all !
If there is no bug, OK... the end, but I don't need stackoverflow or something else !

Yep. I appreciate that. But there are millions of ssl handshake failures happening every day between various servers and clients. This isn’t a reproducible bug report and it’s quite a lot of effort to investigate each one. So stackoverflow is a better forum for support.
Sent with GitHawk

I see, thanks Yuri


smoke tests are failing for app pack

https://github.com/adobe/aio-e2e-tests/actions/runs/5040508752
This is because the ora() library output defaults to stderr, not stdout.
Either change it to stdout: https://github.com/sindresorhus/ora#stream or output the stderr to the same text file.

Best solution is change the GH workflow: https://stackoverflow.com/a/7527438

New error:
- Validating deploy.yaml...
✖ Missing or invalid keys in deploy.yaml: [
  {
    "instancePath": "",
    "schemaPath": "#/required",
    "keyword": "required",
    "params": {
      "missingProperty": "workspaces"
    },
    "message": "must have required property 'workspaces'"
  }
]
 ›   Error: Missing or invalid keys in deploy.yaml: [
 ›     {
 ›       "instancePath": "",
 ›       "schemaPath": "#/required",
 ›       "keyword": "required",
 ›       "params": {
 ›         "missingProperty": "workspaces"
 ›       },
 ›       "message": "must have required property 'workspaces'"
 ›     }
 ›   ]

Should be resolved via https://github.com/adobe/aio-cli-plugin-app/issues/676


jq: add configuration option to disable regex support

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

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

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

Builds on macos 10.14.
Pretty much all of its reverse-dependencies are already broken on darwin currently so :shrug:

Result of nixpkgs-review pr 117895 at 406ea2a0 run on x86_64-linux 1

6 packages marked as broken and skipped:

linuxPackages-libre.sysdig
linuxPackages_4_4.sysdig
linuxPackages_4_9.sysdig
linuxPackages_hardkernel_4_14.sysdig
linuxPackages_hardkernel_latest.sysdig
linuxPackages_latest-libre.sysdig

3 packages failed to build:

oq
python38Packages.jq
python39Packages.jq

30 packages skipped due to time constraints:

anki
ankisyncd
code-server
corectrl
hydrus
jellyfin-mpv-shim
linuxPackages.sysdig (linuxPackages_5_4.sysdig)
linuxPackages_4_14.sysdig
linuxPackages_4_19.sysdig
linuxPackages_5_10.sysdig
...

76 packages built successfully:

bash-my-aws
cargo-download
carnix
celluloid
chrome-gnome-shell
common-updater-scripts
curaLulzbot
curseradio
dune-release
element-desktop
glslang
google-cloud-sdk (google-cloud-sdk-gce)
hydra-unstable
i3-layout-manager
ijq
imgur-screenshot
jftui
jq
kodi-cli
libplacebo
lutris
lutris-free
lutris-unwrapped
memtest86-efi
minitube
monado
mpc-qt
mpv
mpv-unwrapped
mpvScripts.mpris
nix-direnv
nix-prefetch
nix-prefetch-docker
nix-update
nixFlakes (nixUnstable)
nixos-generators
nixos-rebuild
nixpkgs-review
ocamlformat (ocamlformat_0_17_0)
ocamlformat_0_11_0
ocamlformat_0_12
ocamlformat_0_13_0
ocamlformat_0_14_0
ocamlformat_0_14_1
ocamlformat_0_14_2
ocamlformat_0_14_3
ocamlformat_0_15_0
ocamlformat_0_15_1
ocamlformat_0_16_0
pb_cli
playonlinux
python38Packages.mpv
yq (python38Packages.yq)
python39Packages.mpv
python39Packages.yq
qimgv
qmplay2
r2mod_cli
rmount
rofi-systemd
slack-cli
somafm-cli
sublime-music
sway-contrib.grimshot
systemfd
todoman
toml2nix
twa
vscode-extensions.matklad.rust-analyzer
vscode-extensions.ms-vscode.cpptools
vscode-extensions.ms-vsliveshare.vsliveshare
vulkan-extension-layer
vulkan-tools
vulkan-validation-layers
xrgears
ytfzf

1 suggestion:

warning: unused-argument
Unused argument: nixosTests.
Near pkgs/development/tools/jq/default.nix:1:16:
  |
1 | { lib, stdenv, nixosTests, fetchurl, autoreconfHook
  |                ^

This diff is also an option:
diff --git i/pkgs/development/tools/jq/default.nix w/pkgs/development/tools/jq/default.nix
index ad4304fc6e1..f31950a9a23 100644
--- i/pkgs/development/tools/jq/default.nix
+++ w/pkgs/development/tools/jq/default.nix
@@ -1,18 +1,47 @@
-{ lib, stdenv, nixosTests, fetchurl, oniguruma }:
+{ lib
+, stdenv
+, fetchFromGitHub
+, fetchpatch
+, autoreconfHook
+, onigurumaSupport ? true
+, oniguruma
+}:

 stdenv.mkDerivation rec {
   pname = "jq";
   version = "1.6";

-  src = fetchurl {
-    url =
-      "https://github.com/stedolan/jq/releases/download/jq-${version}/jq-${version}.tar.gz";
-    sha256 = "0wmapfskhzfwranf6515nzmm84r7kwljgfs7dg6bjgxakbicis2x";
+  src = fetchFromGitHub {
+    owner = "stedolan";
+    repo = pname;
+    rev = "jq-${version}";
+    sha256 = "CIE8vumQPGK+TFAncmpBijANpFALLTadOvkob0gVzro=";
   };

+  patches = [
+    # https://github.com/stedolan/jq/pull/2292
+    (fetchpatch {
+      url = "https://github.com/stedolan/jq/pull/2292/commits/f6a69a6e52b68a92b816a28eb20719a3d0cb51ae.patch";
+      sha256 = "pTM5FZ6hFs5Rdx+W2dICSS2lcoLY1Q//Lan3Hu8Gr58=";
+    })
+  ];
+
   outputs = [ "bin" "doc" "man" "dev" "lib" "out" ];

-  buildInputs = [ oniguruma ];
+  buildInputs = lib.optionals onigurumaSupport [ oniguruma ];
+
+  nativeBuildInputs = [
+    autoreconfHook
+  ];
+
+  # Their script that writes the version that's eventually compiled and printed
+  # in `jq --help` relies on a .git directory which our src doesn't keep. If
+  # switching to using an src from a release tarball, this hook shouldn't be needed.
+  preConfigure = ''
+    echo "#!/bin/sh" > scripts/version
+    echo "echo ${version}" >> scripts/version
+    patchShebangs scripts/version
+  '';

   configureFlags = [
     "--bindir=\${bin}/bin"
@@ -20,6 +49,7 @@ stdenv.mkDerivation rec {
     "--datadir=\${doc}/share"
     "--mandir=\${man}/share/man"
   ]
+    ++ lib.optional (!onigurumaSupport) "--with-oniguruma=no"
   # jq is linked to libjq:
     ++ lib.optional (!stdenv.isDarwin) "LDFLAGS=-Wl,-rpath,\\\${libdir}";

But it still requires a small preConfigure script to make the correct version get compiled into the executable, as our src doesn't have a .git directory. I still think it's slightly @KAction but feel free to discard this suggestion. My best argument is that it's a good practice to apply patches send upstream when we send them.

These "personal preference issues" will all become a thing of the past when nixpkgs-fmt becomes the standard style enforcer, so there really isn't much point in spending a lot of time on this now.

Is it going to enforce vertical whitespace? I use nixfmt, but it preserves vertical whitespace.

Is it going to enforce vertical whitespace? I use nixfmt, but it preserves vertical whitespace.

I don't know. The only real difference I noticed it's that nixfmt enforces short lines for very long strings which usually ends up with a strange line break after the variable followed by a 140 character URL which does not improve anything.

I don't know. The only real difference I noticed it's that nixfmt enforces short lines for very long strings which usually ends up with a strange line break after the variable followed by a 140 character URL which does not improve anything.

Sure, it's not perfect but a consistent style that people don't have to talk about/waste time on is much preferred to the current situation.

Okay, looks like I applied all suggestions:

patch is downloaded from github
autoreconfHook is run unconditionally


Port to ros2 rolling

only kr5 is ported

@Robotgir Do you think that it would make sense to move launch files into kuka_common and here just have short launch files that import them?
We have a lot of copy-paste code now.
OK, let's do the following:
1. Make robot description package and launch file name paramterizable in the launch files.

2. Make a general launch file in "kuka_common"

3. Shorten all the launch files by providing parameters but using launch file from "kuka_common"

i was thinking of using robot description package and package name as parameters, i dont understand what you mean by "launch file name" parametrizing ?

i was thinking of using robot description package and package name as parameters, i dont understand what you mean by "launch file name" parametrizing ?

o i cannot imagine how to use launch file name for paramtrizing?

i was thinking of using robot description package and package name as parameters, i dont understand what you mean by "launch file name" parametrizing ?

o i cannot imagine how to use launch file name for paramtrizing?

I updated it. I meant XACRO file name

A bit late, but could you comment on the decision to 'hard-code' ros2_control support into the base models ported here?
As nice as it is / can be, ros2_control is not the only way these robots can be controlled, and many use-cases would have no use for the ros2_control elements in the top-level .xacros / the macros.
It would be cleaner if the models are kept driver/interfacing technology-agnostic as much as possible, and provide support for specific interfaces and use-cases in additional packages.
Experience shows radically limiting dependencies and assumptions facilitates reuse greatly (also outside of ROS), hence my question.


Ignore type errors caused by lack of a sourcemap file

Type errors for require(), game, script, etc when no sourcemap.json file exists should be ignored.
These should instead be typed as any.

The errors are useful to highlight that no sourcemap is present, or there is an issue with it.
If you use non strict mode, it shouldn't error

Can it be an extension setting?

What is your usecase for this? I'm curious why one would not wish for these variables to be typed even though they are used.
It will be unlikely to prevent the require errors, but we could potentially suppress the others

After opening this issue, I added sourcemap support to Lync. So I no longer have a use case.
For other tools it would be nice to disable require errors and such if they don't (yet?) generate sourcemaps.

Having a sourcemap is pretty much vital otherwise no require will resolve appropriately, so I don't really see the value in suppressing the warning for require in these cases.
It also looks like game / script etc. already don't error when no sourcemap is present?


Request a paper for this entire project

Hi Guys
First of all, Thanks for your good job.
I am a graduate student from Taiwan.
Today, I found this project from Internet that are so close my research topic.
So I want ask you, Do you have this whole project paper can be a reference?
I looking forward to your reply. Thank you!

Hello,
Thank you very much for your interest.
We have a journal paper that is under reviewing at the moment. Hopefully,
it will be published in a month. No more than two.
Meanwhile, I can just try to answer the possible questions that you can
have.
Sorry for the inconvenience.
Best regards,
Noé
El lun., 2 dic. 2019 8:32, q576333<EMAIL_ADDRESS>escribió:

Hi Guys
First of all, Thanks for your good job.
I am a graduate student from Taiwan.
Today, I found this project from Internet that are so close my research
topic.
So I want ask you, Do you have this whole project paper can be a reference?
I looking forward to your reply. Thank you!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/noeperez/indires_navigation/issues/1?email_source=notifications&email_token=ADUK36GHBSY34G6SNAEOYJ3QWS2YFA5CNFSM4JTRP4IKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H5FSTQA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADUK36AYF67QHUYQJOJKXPLQWS2YFANCNFSM4JTRP4IA
.

You can find the paper here: https://doi.org/10.3390/s20010220


Material TabBars should scroll horizontally with the mouse wheel by default

Use case
I have a TabBar with many tabs in my desktop application. At the moment, the only way to properly scroll across the tab list is to hold shift while moving the scroll wheel (if #75180 isn't an issue).
Proposal
TabBars should scroll horizontally by default in response to the mouse wheel, as it makes no sense to scroll them vertically since they cannot move on that axis.

Hi @hacker1024, Thanks for filing the issue. This seems like a valid feature request. But I believe this should be fixed once the issue you have linked gets fixed.
cc: @Piinks  for confirmation.

This sounds like a reasonable proposal. Presumably it would apply to any scrollable that only supports horizontal scrolling.

@hacker1024 this should already work, since a mouse scroll is handled in such a way that it applies to the scrolling widget's main axis. The linked issue is specific to applying the shift modifier key, but it sounds like you are talking about this working without the modifier key. Can you confirm ? If so, that issue will not solve this.
Can you also provide a minimal runnable sample of code that illustrates your issue? Thanks!

@Piinks
https://dartpad.dev/?id=d3d3e89425655cdd835eb6fa3be20b68
I am indeed talking about using just the mouse wheel without the modifier key. As you can see in this example, the tabs do not scroll with the wheel unless the modifier key is pressed.
While my example puts the TabBar in an AppBar, the same problem occurs if it is used by itself.

Thanks for the dartpad, can you also share what platform you are running it on? Mac, windows, linux? Even though dartpad is running on web, some behaviors defer to the actual platform it is running on.

I've tested on the desktop, Chrome and Safari on macOS 10
15, with both a regular mouse and a trackpad.

any updates yet? I am trying to create this same behavior for my sliver app bar but it doesn't allow scroll wheel to scroll through horizontal list view which is inside SliverPersistentHeaderDelegate.

Any update on this?

So after looking into this a bit, I am not sure we can support this by default, but may be able to make it configurable.
When scrolling with a vertical mouse wheel, the input from the platform is vertical. Just because the mouse may be hovering over a horizontal scroll view does not necessarily mean the input can automatically assume it should be altered. It is not atypical for a horizontal scrolling TabBar to be contained within a vertical scroll view, for example.
https://github.com/flutter/flutter/pull/115610 added support for shift->horizontal scroll, or whichever keys you'd like to configure, which is a more common convention across platforms. Perhaps we can introduce something similar that allows users to indicate this assumption can be made.


publish image for supporting arm64 and amd64

refer to https://docs.docker.com/build/ci/github-actions/multi-platform/
I have test the docker build arm64 and amd64 on my local as the screenshot.

Nice. Thanks!


ESM max length

Hello!
ESM2 uses rotary embeddings (even though it has a normal position embedding matrix it doesn't use it), so ESM2 has no max length. This is a very common misconception in the field, and there is a setting for it in the Huggingface implementation.
Cheers!
Logan

Thank you for the discussion. The maximum length of 1024 mentioned in our paper refers to the upper limit for sequences input into the model, not the maximum sequence length that the model can handle. The original ESM-2 model truncates proteins longer than 1024 amino acids to a length of 1024 during training. However, as our model needs to unfold the protein sequences, we have allowed for the input of longer protein sequences into the model.

Ah, I see. Love the paper, great work!


add rsync_repo for Leap 16

Make sure to rsync also Leap 16 repo not just images

Closing in favor of submission #263 from @andrii-suse.


Gracefully handle revoked Device

After a device has been revoked starting the desktop app will yield an error and a stack trace. This should be better handled.

Yes, absolutely! It probably already is handled better during sync, but not during event selection.

That was actually on startup after the key was revoked. Before the app was closed and the key revoked no event was select, so maybe this explains that.


Python: don't track virtualenv files.

Don't track files created by virtualenv.
Typical location are "venv" or "ENV" directories (relatively to project's home). These files depend on environment preferred by particular user. They shouldn't be committed to repository, because 1) it's meaningless and 2) could overwrite or conflict with settings of  another user of the same repository.
http://docs.python-guide.org/en/latest/dev/virtualenvs/
https://virtualenv.pypa.io/en/latest/userguide.html

@e-yes thanks for all the details!


Challenge token format

In the WACI context, Step 3 - Send Message Requesting Presentation, there is mention of a challenge token, but no guidance is provided as to what type of value is acceptable for this property.

also domain isn't specified

They should be normatively strings, point them to https://w3id.org/security/#domain and https://w3id.org/security/#challenge
give some brief guidance on what a nonce/challenge is.


[SPARK-21064][Core][Test] Fix the default value bug in NettyBlockTran…

What changes were proposed in this pull request?
Fix the default value bug in NettyBlockTransferServiceSuite.
The defalut value for spark.port.maxRetries is 100, but we use the 10
in the suite file, we change 10 to 100.
How was this patch tested?
No Test

Can one of the admins verify this patch?

@djvulee this needs to be a pull request vs master

we should port this to master too.

@djvulee no, it needs to be merged to master first. Close this and open a PR vs master

Ok, thanks!


Lower bounds > Upper Bounds for Conformalized Quantile Regression

Describe the bug
I cannot share exacty the code since it is done on proprietary dataset, however, I noticed that for less than 0.01% of my test dataset. Mapie produced some lower bounds which are greater then my upper bound. I can share with you something which should be indeed a proof even without sharing the data:
mapie = MapieQuantileRegressor(model, **{"method": "quantile", "cv": "split", "alpha": 0.2})
mapie.fit(
    X_train, y_train,
    X_calib=X_calib, y_calib=y_calib,
    random_state=1337
)
y_pred, y_pis = mapie.predict(X_test)

np.any(y_pis[:, 0, :] > y_pis[:, 1, :])

> True

Is it something that can happen? During the fitting I got a Warning: UserWarning: WARNING: The predictions are ill-sorted.. Is this related with this "bug" ?

OS: Win10
Browser Chrome
MAPIE Version 0.8.3

Hi @francescomandruvs, I do not know if this is a MAPIE-specific problem, but I manually implement conformalized quantile regression and I also had the case where the lower bounds are greater than the upper bounds at certain timestamps. But I am also curious, how this is possbile...
What model are you inserting into the MapieQuantileRegressor?

Hey @francescomandruvs,
Thank you for this issue. Indeed, the warning is supposed to raise your attention to this aspect.
When estimating a lower and an upper quantile by two separate quantile regressions, there is no guarantee that the lower estimate will actually be smaller than the upper estimate. This is known as the quantile crossing problem. - page 10 of the original CQR paper [2]. The reference for this issue is discussed in the paper by Bassett [1].
[1] Bassett Jr, Gilbert, and Roger Koenker. "An empirical quantile function for linear models with iid errors." Journal of the American Statistical Association 77.378 (1982): 407-415.
[2] Romano, Yaniv, Evan Patterson, and Emmanuel Candes. "Conformalized quantile regression." Advances in neural information processing systems 32 (2019).

Hi @francescomandruvs, I do not know if this is a MAPIE-specific problem, but I manually implement conformalized quantile regression and I also had the case where the lower bounds are greater than the upper bounds at certain timestamps. But I am also curious, how this is possbile...
What model are you inserting into the MapieQuantileRegressor?

I think that @LacombeLouis answered to us quite well :)


Replace BlackBox functions vendoring from backend to library

As a Developer
I would like to be able to resolve BlackBox functions from library linked to execution
so that I am no tightly coupled with backend providing those (currently through Barretenberg backend).
AC:

acvm-backend-barretenberg should be replaced while BlackBox functions are resolved with a library providing those.

We could approach this in two ways:

Move the barretenberg wasm binary from acvm_js to another crate which gets included in the acvm crate by default
Bring the barretenberg wasm binary up to nargo and then pass it in to ACVM similarly to how we do now but as a BlackBoxSolver rather than as a Backend.

The first is preferable but will need testing to ensure that this works across targets nicely. The second is definitely possible but prevents encapsulation of this barretenberg wasm.


tautulli: 2.13.2 -> 2.13.4

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[X] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[X] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 272722 run on x86_64-linux 1

1 package built:

tautulli

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/1365


Show the past efforts to keep the same Form number

It's an Enhancement Request :
As a user, when I read the Fitness Trend I would love to see what are the past efforts (run, ride or swim) that I have to reproduce today in order form me the keep the same Form value (or number).
Let's imagine I am at Form 18.7, I would love to know what are the past effort that I need to reproduce to keep the value unchanged. That might be a 45min footing I just did the week before or 1 hour of home trainer a couple of days ago. With all the activities you have recorded, I'm sure you can propose a list of approaching efforts to keep our Form value unchanged.

Yes, sorry, I meant Fitness value.


Problem. Test case 'id_000000' results in a timeout

Hi I have launched the command afl-fuzz.exe -i in -o out -D "C:\Users\User\Desktop\Tools\Fuzzing\DRRUN\DynamoRIO-Windows-8.0.18929\bin64" -t 20000 --  -coverage_module dllmain.dll -coverage_module dllmain2.dll -coverage_module dllmain3.dll  -fuzz_iterations 5000 -target_module program.exe    -target_method WinMain -nargs 2 --  "program.exe" @@
but it gives me a timeout testcase error:
`[-] The program took more than 20000 ms to process one of the initial test cases.
In WinAFL, this error could also mean incorrect instrumentation params.
Please make sure instrumentation runs correctly using the debug mode
(see the README) before attempting to run afl-fuzz.
[-] PROGRAM ABORT : Test case 'id_000000' results in a timeout
Location : perform_dry_run(), C:\Users\User\Desktop\Tools\Fuzzing\DRRUN\winafl\afl-fuzz.c:3233`
Test case is less than 1mb.

Please run the debug mode first as explained in https://github.com/googleprojectzero/winafl/blob/master/readme_dr.md and check the log. It can help you debug issues such as this.

I have launched the debug mode and opened the .proc.log file but it gives me only a list of loaded modules and I have this error
[-] PROGRAM ABORT : Cannot kill child process
     Location : destroy_target_process(), C:\Users\User\Desktop\Tools\Fuzzing\DRRUN\winafl\afl-fuzz.c:2648

but when I am quitting the fuzzed application it gives me this error

I have launched winafl with administrator privileges but nothing (same crash)


[DRAFT]: Move base flow to app folder

What changed? Why?
Notes to reviewers
How has it been tested?

🟡 Heimdall Review Status

Requirement
Status
More Info

Reviews

🟡
0/1

Denominator calculation

Show calculation

1 if user is bot
0

1 if user is external
0

From .codeflow.yml

1

Additional review requirements

Show calculation

Max
0

0

From CODEOWNERS

0

Global minimum
0

Max

1

1

1 if commit is unverified
0

Sum
1


TypeError: Attempted to wrap componentDidMount which is already wrapped

 const initialProps = setup();
      const groups = {
        fetchGroups: sinon.stub(),
        groupsStore: {
          profilesList: []
        }
      };
      const props = _.merge({}, initialProps, { groups });
      const spy = sinon.spy(Groups.prototype, 'componentDidMount');
      shallow(<Groups {...props} />);
      expect(spy.calledOnce).to.equal(true);

It says : Attempted to wrap componentDidMount which is already wrapped
I am not sure what I am missing.

Basically, I have a bunch of methods that I fire on componentDidMount:
 componentDidMount() {
    this.props.fetchGroups();
    this.props.fetchProfilesForGroup();
    this.props.resetGroupsStatuses(Types.FORM, Types.BLOCK);
    this.props.fetchStats();
  }

I just want to check if they are called on componentDidMount. I was going through a recent PR and I believe shallow render supports to check react life cycle methods. Not sure what I am missing here. Thanks in advance.

Are you doing that in multiple tests? I don't see you cleaning up the spy after that test.

Yeah my bad I figured it out. Now, I have this:
 const props = _.merge({}, initialProps, { groups });
      const spy = sinon.spy(Groups.prototype, 'componentDidMount');
      shallow(<Groups {...props} />);
      expect(spy.calledOnce).to.equal(true);
      spy.reset();

It expects false. Doesn't shallow render supports lifecycle methods?

Seems like I needed  { lifecycleExperimental: true } to make shallow work with componentDidMount. Since this is experimental, is it safe to go with this? If not what's the alternative you recommend best at this moment? @ljharb

@laumair I'd recommend using { lifecycleExperimental: true } if you want to test lifecycle methods with shallow wrappers! We hid it behind a flag for now to be sure it worked as expected, so we'd really appreciate it if you used it and let us know if you have issues 👍

@Aweary thanks for the quick response. I am already using it :)
+1 for allowing shallow wrappers to test lifecycle methods.

@Aweary Is it possible to test methods other than render inside class using shallow? If yes, I'd really appreciate if you could point me to the docs maybe?

export default class Foo extends Component {
someFunction(){}
render() {}
}

What I meant to ask is if I wanted to test someFunction() with shallow? Is this possible?

Instance is what I needed.


New resource loading: long IO requests can drain resource Id pool

If too many resources are taking too long to load they can drain the free resource ids. Throttling inside Gfx doesn't help here, instead the app must be able to ask the Gfx system whether it's ok to create new resources (or better query for the number of free slots for a resource type).
Additionally the Create functions should return an InvalidId if no more free Ids are in the required resource pool.

Fixed on assets branch


[LRS-83] POST with empty list

This adds a test for POST with empty list

@cliffcaseyyet (Sorry just saw that you responded) Actually I would not close this PR, since I added commits to this branch to bring in the updated schema deps + new tests.

@cliffcaseyyet (Sorry just saw that you responded) Actually I would not close this PR, since I added commits to this branch to bring in the updated schema deps + new tests.

Ah ok, i thought this was the alternative path from what you did.


add zsh style autocompletion docs

WHAT
Adding docs for Zsh autocompletion setup.
WHY
Took me too long to setup and find the issues.
Related issue (if exists)
#44 #32

Thank you! I also made sure the procedure works.
This is helpful a lot!!

Thank you very much for this project!


tool hangs on first run

root@letsencrypt ~# ps auxw
USER      PID  %CPU %MEM    VSZ   RSS TT  STAT STARTED    TIME COMMAND
certbot 28367 100.0  0.2  68684 30524 13  R+J  15:36   3:01.71 /srv/letsencrypt/.cargo/bin/letsencrypt-inwx create -c /srv/letsencrypt/.config/letsencrypt-inwx-cred -d _acme-challenge.topsecret -v omitted

FreeBSD 11.1, rust v1.26.2

I did not test this crate on freebsd since I'm not using it. However it's hard to believe for me that that this crate is causing the problem.
The only loop in this crate looks like this:
if !matches.is_present("nodnscheck") {
	println!("Waiting for the dns record to be publicly visible...");

	let start = Instant::now();
	let mut wait_secs = 5;

	loop {
		// timeout after 10 minutes
		if start.elapsed() > Duration::from_secs(60 * 10) {
			return Err("timeout!".to_owned());
		}

		if check_txt_record(domain, value) {
			break;
		}

		wait_secs *= 2;

		sleep(Duration::from_secs(wait_secs));
	}

	println!("=> done!");
}

So while it could loop for up to around 10 minutes it should not be possible for it to cause 100% cpu usage since it uses sleep.
Could you try to run letsencrypt-inwx create with the --no-dns-check flag to test if this is the problem?

I hope you could solve your problem. If your problem still persists I can reopen this issue.


DE&I Policies

DE&I (Diversity, Equity, and Inclusion) Policies are the set of policies and practices that promote diversity, equity, and inclusion in the workplace.  DE&I policies may include training, recruitment and hiring practices, promotion and advancement opportunities, and company culture initiatives.

DE&I (Diversity, Equity, and Inclusion) policies are designed to create a workplace that is welcoming and supportive of individuals from all backgrounds, experiences, and perspectives. The goal of these policies is to create an inclusive environment where everyone feels valued and respected, and where everyone has equal opportunities to succeed.
Diversity refers to the presence of individuals with a range of different backgrounds, experiences, and perspectives. This can include diversity in terms of race, ethnicity, gender, age, sexual orientation, disability, religion, and many other factors. The goal of diversity policies is to ensure that the workplace reflects the diversity of the broader community and to create a more diverse and inclusive workplace culture.
Equity refers to ensuring that everyone has access to the same opportunities and resources, regardless of their background or identity. Equity policies may include measures to address historic inequalities or to provide support for individuals who face barriers to advancement. The goal of equity policies is to create a more level playing field and to ensure that everyone has a fair chance to succeed.
Inclusion refers to creating a workplace culture that values and respects everyone's unique perspectives and experiences. Inclusion policies may include training, mentorship programs, and other initiatives to promote diversity and foster a sense of belonging. The goal of inclusion policies is to create a workplace where everyone feels welcome and valued, and where everyone can contribute to their full potential.
Together, these policies promote a workplace that is diverse, equitable, and inclusive, and that supports the well-being and success of all employees. By implementing DE&I policies, organizations can create a more positive and productive workplace culture, attract and retain top talent, and better serve their customers and communities.


Updating enhanced enum causes Hot Reload to crash DartVM

Modifying a running Flutter instance by adding a constructor and a field to a enum is enough to crash the DartVM:
Launching lib/main.dart on Linux in debug mode...
Connecting to VM Service at ws://<IP_ADDRESS>:42535/sjzt2FE7Jqg=/ws
Reloaded 1 of 594 libraries in 182ms (compile: 23 ms, reload: 65 ms, reassemble: 68 ms).
Reloaded 1 of 594 libraries in 153ms (compile: 18 ms, reload: 65 ms, reassemble: 59 ms).
../../third_party/dart/runtime/vm/heap/become.cc: 314: error: become: No indirect chains of forwarding
version=2.18.4 (stable) (Tue Nov 1 15:15:07 2022 +0000) on "linux_x64"
pid=123651, thread=123670, isolate_group=main(0x7f337400f5a0), isolate=(nil)((nil))
isolate_instructions=7f33ca3d9000, vm_instructions=7f33ca3d9000
  pc 0x00007f33ca5083ec fp 0x00007f3395ff9710 /home/brettmorgan/Documents/flutter-projects/enum_testing/build/linux/x64/debug/bundle/lib/libflutter_linux_gtk.so+0x1f083ec
-- End of DumpStackTrace
Lost connection to device.
Exited

Code before modification:
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

enum ContentEnum { a, b, c, d, e }

class MyHomePage extends StatelessWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text(title)),
      body: ListView.builder(
        itemCount: ContentEnum.values.length,
        itemBuilder: (context, index) => ListTile(
          title: Text(
            ContentEnum.values[index].name,
          ),
        ),
      ),
    );
  }
}

Code after modification:
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

enum ContentEnum {
  a('A'),
  b('B'),
  c('C'),
  d('D'),
  e('E');

  const ContentEnum(this.displayName);
  final String displayName;
}

class MyHomePage extends StatelessWidget {
  const MyHomePage({super.key, required this.title});

  final String title;

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text(title)),
      body: ListView.builder(
        itemCount: ContentEnum.values.length,
        itemBuilder: (context, index) => ListTile(
          title: Text(
            ContentEnum.values[index].displayName,
          ),
        ),
      ),
    );
  }
}

System info:
$ flutter doctor -v
[✓] Flutter (Channel stable, 3.3.7, on Debian GNU/Linux rodete
    5.18.16-1rodete4-amd64, locale en_US.UTF-8)
    • Flutter version 3.3.7 on channel stable at /home/brettmorgan/flutter
    • Upstream repository https://github.com/flutter/flutter
    • Framework revision e99c9c7cd9 (5 days ago), 2022-11-01 16:59:00 -0700
    • Engine revision 857bd6b74c
    • Dart version 2.18.4
    • DevTools version 2.15.0

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from:
      https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK
      components.
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup
      for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • Debian clang version 14.0.6-2
    • cmake version 3.24.2
    • ninja version 1.11.1
    • pkg-config version 0.29.2

[!] Android Studio (not installed)
    • Android Studio not found; download from
      https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup
      for detailed instructions).

[✓] VS Code (version 1.72.2)
    • VS Code at /usr/share/code
    • Flutter extension version 3.52.0

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Debian GNU/Linux rodete
      5.18.16-1rodete4-amd64
    • Chrome (web)    • chrome • web-javascript • Google Chrome 107.0.5304.87

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 2 categories.

/cc @rmacnak-google @bkonyi

Can confirm I'm also experiencing this issue.
I'm using
Flutter (Channel stable, 3.7.3, on macOS 13.2 22D49 darwin-arm64, locale en-US)

And this is on a real Pixel 7 Pro.


Docker build for the revised ITs

Includes the Docker image build for the revised ITs. Split out from PR #12368 to simplify review and merge.
This PR contains two items:
it-tools which defines the IT test extensions that are added into the IT Docker image. These are the same as what the integration-tests project provides, just built separately and packaged so they can be added to the image. it-tools is built as part of the Maven build, after distribution. Its output is an extension jar. No harm in including it even in non-IT builds.
it-image which builds the Docker image. It is activated by the test-image profile.
In addition, .travis.yml is modified to run the Docker image to show that it builds. Nothing uses the image, that will come when #12368 is merged. We're just proving that that the build works to assure reviewers that things are correct.
The changes here have already been reviewed as part of #12368. This is a subset of those changes. The test themselves, and the documentation, is omitted to keep the PR small.

This PR has:

[X] been self-reviewed.
[ ] added documentation for new or modified features or behaviors. (No, will come later.)
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader. (No. Will come later with extensive documentation.)
[ ] added integration tests. (Not yet, will come later.)

Ready for re-review. The build failed, but due to some issue on Travis with an ARM build:
Automatic restarts limited: Please try restarting this job later or contact<EMAIL_ADDRESS>
This same error has occurred randomly on other PRs, so I'm assuming the test is flaky.

@kfaraz, thanks much for the final review! The final commit updates script documentation as you suggested. Changing script comments should not break anything, but Travis will do its thing anyway. Let's hope we get lucky and don't hit any flaky tests.


Service-like feature for FE pages of facilities to BE

User story

As a facility manager
I want to see the right facilities with their information from the backend
So that I can fetch and view up-to-date data regarding my facilities

Acceptance criteria

[ ] the frontend calls (api/facilities) instead of (api/timeseries) to see the facilities. This also means we see one card per facility on the Facilities Overview Page and not 2/3 like before.
[ ] the facilities show their description and name from the backend instead of just their id.
[ ] both the facilities overview page and the facilities with issues page are adjusted
[ ] also on the details page we get the corresponding facility from the backend

What is not inlcuded
Since this issue regards the facilities endpoint and not the timeseries endpoint it is not included to show Pump/ Environment data from the backend on the details page.
DoD general criteria

[ ] Feature has been fully implemented
[ ] Feature has been merged into the mainline
[ ] All acceptance criteria were met
[ ] Product owner approved features
[ ] All tests are passing
[ ] Developers agreed to release

After @Persists explained us where the backend provides the data @Sabo2k and I implemented a service to fetch the data from the backend in the feat/xd-29-fetching-service branch. We will not merge this branch as we still need to figure out a good architecture to get the data in the frontend and not just have it in one service. It is still very useful to show that it works and how to get the data

It is still on the feat/xd-82 branch because the backend part is also not already on develop but it is basically done. Now the facilities we can see make more sense. Before this we actually displayed 2 cards for every facility and did not get a lot of meaningful data (only assetId and propertysetname):

Now we actually see the facilities with their name and description from the backend. We still get the id and use it tho.

And now to the other part of this issue, which is basically #158. But it is also listed here that "the frontend of the facility details view displays data from the application's backend" and since this was the only branch where backend and frontend were ready for this stuff it should be ok. The facilities now show the actual pump data from the backend. The SIEMENS API only has meaningful values for 3 of the pumps right now tho
Playground-MSAgentPump (id: 8ccb6c1c6c464e5784410e5a1c8a8def)

PUMP-003 (id: bfcfbbdae35c4c9da77ef477b6612084)

PUMP-002 (id: ba9361db82f4411297bdd8494ecb040f)

Since my comments must now be confusing, I adjusted the description so only the part with the facilities and not the part about pump data is included


Add Astro support

Hi, just a small tweak to add .astro file support to the extension for use with https://astro.build static sites.
Let me know if I've missed anything 🙂

Perfect! Added in v4.3. Thanks James.


#44: Cluster registration

Description

Closes #44

Cluster registration script
Verification steps

Run local-setup with only the control cluster
make local-setup

Create the tenant namespace in the control cluster
kubectl create namespace my-tenant

Create the tenant cluster
# Import the util scripts
source hack/.setupEnv
source hack/.kindUtils

kindCreateCluster tenant-cluster 9091 8446

Run the register cluster script
export KUBECONFIG=$(pwd)/tmp/kubeconfigs/mctc-control-plane.kubeconfig
kubectl config use-context kind-mctc-control-plane
./hack/register-cluster.sh $(pwd)/tmp/kubeconfigs/internal/mctc-control-plane.kubeconfig $(pwd)/tmp/kubeconfigs/tenant-cluster.kubeconfig my-tenant kind-tenant-cluster > agent-manifests.yaml

Deploy the syncer in the tenant cluster
# Build and load the syncer image
make docker-build-syncer
kind load docker-image syncer:latest --name tenant-cluster  --nodes tenant-cluster-control-plane

export KUBECONFIG=$(pwd)/tmp/kubeconfigs/tenant-cluster.kubeconfig
kubectl create namespace mctc-system
kubectl apply -f agent-manifests.yaml

trying this out locally. Changes look reasonable

I think we may be able to limit the syncer to a particular namespace on the data plane cluster. This will simplify thing quite a bit, as a tenant cp ns maps to a data plane ns on a set of clusters.
I mention it as we have a cluster role and cluster role binding currently. Don't need to change it as of now, but if we do move to a 1:1 then we should def change it

@sergioifg94 looks like might need to update the flags to the syncer
flag provided but not defined: -control-plane-namespace

Usage of /syncer:
  -control-plane-config-name string
    	The name of the secret with the control plane client configuration (default "control-plane-cluster")
  -control-plane-config-namespace string
    	The namespace containing the secret with the control plane client configuration (default "mctc-system")
  -health-probe-bind-address string

@maleck13 Oh yes for now I'm just removing the flag from the generated manifest, but when #96 is merged it should work

ok so is this blocked by that PR? wondering how to check the registration worked?

everything seemed to work as expected, but just the start up of the syncer failed.

Just a note. When I ran make local-setup a second time I got the following error
make local-setup
test -s /Users/maleck13/projects/src/github.com/kuadrant/multi-cluster-traffic-controller/bin/yq || GOBIN=/Users/maleck13/projects/src/github.com/kuadrant/multi-cluster-traffic-controller/bin go install<EMAIL_ADDRESS>./hack/local-setup.sh
Deleting mctc network
Error response from daemon: error while removing network: network mctc id 3e25dc23e481a5e7b8ba2b1f9a7a71169a4b31510b99b03fe73c07f602ce48bb has active endpoints
Error response from daemon: network with name mctc already exists

looks like there's an error in the steps to setup:
pbrookes@pbrookes-mac multi-cluster-traffic-controller % source hack/.setupEnv
source hack/.kindUtils

kindCreateCluster tenant-cluster 9091 8446
kindCreateCluster:5: no such file or directory: /Users/pbrookes/Projects/src/github.com/Kuadrant/multi-cluster-traffic-controller/../bin/kind
kindCreateCluster:26: no such file or directory: /Users/pbrookes/Projects/src/github.com/Kuadrant/multi-cluster-traffic-controller/../bin/kind
kindCreateCluster:27: no such file or directory: /Users/pbrookes/Projects/src/github.com/Kuadrant/multi-cluster-traffic-controller/../bin/kind

I've manually worked around it for now. Not sure if this needs correcting though?

@philbrookes Are you using bash? I have zsh and I get similar errors so I need to explicitly open a bash terminal for it

oh, yes I am using zsh, I'll try switching to bash. Can we not make this work for zsh? Considering that a few of us are using Macs?

I think all the scripts are meant to be run in bash. See the #!/bin/bash at the first line. So when executing the script even if you're on zsh it will run it on bash and that's how it's always worked fine. The only thing is that if we source the script from zsh as we're doing in the verification steps it will fail because some stuff is not compatible.
I think that as this is only for the sake of verifying the PR and not a common step it's fine to leave it the way it is


Add a new header to the Prepare message to implicitly inline type names

The Prepare protocol message now has a new header to make the compiler
implicitly inline a "tname := .type.name" computable.  This is
especially useful for REPL-like applications.

Issue: https://github.com/edgedb/edgedb/issues/1350

@elprans @tailhook I'd like to merge this asap to land the edgecon.pyx refactorings and unblock my ports rework. The REPL works with this PR as is, although it crashes when \set introspect-types on is set (https://github.com/edgedb/edgedb-cli/pull/108 addresses that).


Chore: switch to node 18

We are currently using node 16 for developing the package, 16 has been deprecated in September, so we should switch to just using 18 moving forward.
This involves:

developing the package using 18 and making sure that everything still works
updating our dependencies and everything that might be related to 16
(in particular, the node-fetch dependencies we have should be removed since in 18 fetch is built in into node)
updating our readmes and the cloudflare docs asking users to use 18+

Note
Since this might effect existing users/applications it needs to be done in the next major release

This is blocked by: https://github.com/cloudflare/next-on-pages/issues/623 (and https://github.com/cloudflare/next-on-pages/pull/648) since node-fetch is being used in the setupDevBindings utility, so we first need to update such utility (which can also remove the node-fetch dependency)


FUIArray is slow when query has thousands of snapshots

Objective C or Swift: Both
iOS version: 12
Firebase SDK version: 4.0.1
FirebaseUI version: 6.0
CocoaPods Version: 1.6.1

Steps to reproduce:

Create a FUIArray with thousands of results

Observed Results:

It takes 8s on simulator and even more on device.

I created a pull request that optimize indexForKey method.
Here's my results :

Closed in #610.


chore: light node optimizations and fix

Clear light node history on startup
dag_blocks_level column created based on dag_blocks_index which is removed to have column ordered by level to support deleting by level for light node
Fix issue with incorrect transaction hash used to delete old transactions on light node
Delete additional columns data for light node: old transactions data in trx_period and old dag blocks in dag_block_period and dag_block_level

prnet cleaned-up successfully


Planning to add an option to generate fully immutable data model classes

I am currently planning to create an option flag in the CSharpClientGeneratorSettings of the NSwag.CodeGeneration.CSharp client generator, to generate an immutable client data model, so the changes to the client model would mainly be:

Only private property setters
Constructors that require all properties to be passed
Using only collections from System.Collections.Immutable

I think these are the main requirements. Since newtonsoft can handle the deserialization from json if a constructor with all properties is available I hope that I wont have to change much to the rest of the generated code, but without having looked at the details of the NSwag implementation, I already have a few questions:

Does anybody see any roadblocks that make this impossible? Or any tips where to start?
Is there already a way to tell the generator "Please only generate the model classes but not the REST client code"? Not that relevant to me but might make the scope of my changes a little bit easier if I don't have to worry about the code generated around the model

As a note for anybody looking into generating immutable model code in the future, this configuration got me very close to the output I described above:
var settings = new CSharpClientGeneratorSettings {
                CSharpGeneratorSettings = {
                    ClassStyle = CSharpClassStyle.Record,
                    ArrayType = "System.Collections.Immutable.IImmutableList",
                    ArrayInstanceType = "System.Collections.Immutable.ImmutableList",
                    ArrayBaseType = "System.Collections.Immutable.ImmutableList",
                    DictionaryType = "System.Collections.Immutable.IImmutableDictionary",
                    DictionaryInstanceType = "System.Collections.Immutable.ImmutableDictionary",
                    DictionaryBaseType = "System.Collections.Immutable.ImmutableDictionary",
                },
                GenerateDtoTypes = true,
                GenerateClientClasses = false,
            };


Tiling to gpkg 184

create a GeoPackage directly from the tiling process

Coverage decreased (-0.63%) to 55.86% when pulling d975d8f4b5ceb8744bb3ff2c476ff13ea24c1121 on tiling-to-gpkg-#184 into 8feb8a2f281ca59b924dc50db628b9a2cbf6edc9 on master.

Coverage decreased (-0.63%) to 55.86% when pulling 6a7b9ae34905d83f8d1351f860ad6e2358f9c2c6 on tiling-to-gpkg-#184 into 8feb8a2f281ca59b924dc50db628b9a2cbf6edc9 on master.

Coverage decreased (-0.63%) to 55.86% when pulling b9d24b509bb2424dd540eedc72cf850ef33d3921 on tiling-to-gpkg-#184 into 8feb8a2f281ca59b924dc50db628b9a2cbf6edc9 on master.

Coverage decreased (-0.63%) to 55.86% when pulling e6198b78d9b88ad5e10bb6dd236d3e9e8434ebee on tiling-to-gpkg-#184 into 8feb8a2f281ca59b924dc50db628b9a2cbf6edc9 on master.

Coverage decreased (-0.63%) to 55.86% when pulling 52b07991c17ee78e41d7f0b26259e2afa68c6ac6 on tiling-to-gpkg-#184 into 8feb8a2f281ca59b924dc50db628b9a2cbf6edc9 on master.

Finished, review remaining comments and commit :)

Coverage decreased (-0.63%) to 55.86% when pulling c5b99a29ae5a11f70dc5e6ee20a3ef59dd9e1708 on tiling-to-gpkg-#184 into 8feb8a2f281ca59b924dc50db628b9a2cbf6edc9 on master.


grep: handle empty suite titles. Fixes #2360.

Fixes #2360.
@mochajs/core Please take a look.

@mochajs/core Hey guys, the AppVeyor seems to fail it can’t download phantomjs. What is the appropriate way to handle this? Is there a way to re-start the build? 🤓

@gurdiga can I suggest a slight update to this PR's title:
- grep: handle empty suite titles. Fixes #2360.
+ grep: skip adding connecting space for empty suite titles. Fixes #2360.

Yeah, I guess that gives a bit more detail regarding on what exactly changes, which I guess this may be a good idea. 🤔 Thanks! 🙂

(I have force-pushed same changes just to see if it’d make the build pass this time.)


Allow secrets with legacy annotations for issuer name and kind to match

This PR allows the certificate controller to accept a secret matches its spec if the secret is using legacy issuer annotations.
This is to ensure that during the upgrade process to 0.11, not all certificates are reissued due to the current Secret resources having the old annotations.
Allow permissive acceptance for matching Certificates with Secrets that are using legacy annotations to reduce non-required certificate reissue.

/milestone v0.12
/milestone v0.11
/cherry-pick release-0.11
/assign @munnerz

/lgtm

/lgtm cancel

/lgtm


Starter kit DRS does not support /objects/<drs_id>/access/<access_id>

I got Part 2 visas working on another machine. The Passport UI wasn't working when I tried on Friday.
With the passport token from the UI successfully got a response to http://localhost:5000/ga4gh/drs/v1/objects/HG00740.1000genomes.lowcov.downsampled.cram
{
    "id": "HG00740.1000genomes.lowcov.downsampled.cram",
    "description": "Low coverage, downsampled CRAM file for sample HG00740",
    "created_time": "2022-06-26T11:06:31Z",
    "mime_type": "application/cram",
    "name": "HG00740 1000 Genomes Downsampled Low Coverage CRAM file",
    "size": 5582919,
    "updated_time": "2022-06-26T11:06:31Z",
    "version": "1.0.0",
    "aliases": ["HG00740 low coverage downsampled CRAM"],
    "checksums": [
        {
            "checksum": "07e0f2598f0663380296d62a2c7f4839b5fc457a",
            "type": "sha1"
        },
        {
            "checksum": "0c0d0eaaf052417f131d5401924f8cab9847d96e22f702a9abef38adc3021f2a",
            "type": "sha256"
        },
        {
            "checksum": "28ffe6386b78fffb7cd0a7b2d0a79846",
            "type": "md5"
        }
    ],
    "self_uri": "drs://localhost:5000/HG00740.1000genomes.lowcov.downsampled.cram",
    "access_methods": [
        {
            "access_url": {"url": "s3://ga4gh-ismb-tutorial-2022/data/1000genomes/cram/lowcov/HG00740.lowcoverage.downsampled.cram"},
            "type": "s3",
            "region": "us-east-2"
        }
    ]
}

One should then be able to make the following call
http://localhost:5000/ga4gh/drs/v1/objects/HG00740.1000genomes.lowcov.downsampled.cram/access/<access_id>
Where access_id is the access method the user wants to use.
Two issues arise from this:

The response above to /objects does not include the access_id for each access methods.
Calling /objects/objects/HG00740.1000genomes.lowcov.downsampled.cram/access/s3 gives the error below

 {
    "timestamp": "2022-06-26T15:59:54Z",
    "statusCode": 405,
    "error": "Method Not Allowed",
    "message": "Request method 'POST' not supported"
}

As far as I know an object can have multiple access methods with the same type (for example s3), that is why I don't think /objects/<drs_id>/access/s3 is a suitable solution since we wouldn't be able to distinguish between them.
I think the best solution is to have a separate <access_id> for every access method. While writing tests I have already written the code to extract the type of access in question and send the correct request depending on the type. So the same could be the used to find which access method is requested from the <access_id> and then process it accordingly before sending back a response.
So far that code only covers these three access types: https, s3 and file. It can always be extended.