[PE-D][Tester D] Meeting Display Ordering not chronological

I would expect that the display for meetings is in chronological order however, meeting 1 occurs before meeting 2. and meeting 2 occurs after meeting 3.
This is the default display upon launching the app.

Labels: severity.Medium type.FeatureFlaw
original: yashma-sonara/ped#1

Duplicate issue #154


Fewer PBKDF2 iterations than what is recommended

The Hierarchical Derivation interface here, permalink uses fewer (500) PBKDF2 interations than what is suggested.
Copying from wikipedia: "When the standard was written in the year 2000 the recommended minimum number of iterations was 1000, but the parameter is intended to be increased over time as CPU speeds increase. A Kerberos standard in 2005 recommended 4096 iterations; Apple reportedly used 2000 for iOS 3, and 10000 for iOS 4; while LastPass in 2011 used 5000 iterations for JavaScript clients and 100000 iterations for server-side hashing."
While the number 500 does not break security in any immediate way, since the implementation deviates from the recommended number of iterations, it is something that is worth noting.

FYI the Rust codebase uses 19162 iterations
More specifically here are the set of parameters used by the Rust codebase
    pub const ITER: u32 = 19_162;
    pub const SALT_SIZE: usize = 32;
    pub const NONCE_SIZE: usize = 12;
    pub const KEY_SIZE: usize = 32;
    pub const TAG_SIZE: usize = 16;

Actually I noticed
whereas Rust-Cardano also uses 4096 iterations for key derivations here whereas the 19_162 is used for password encryption of the key here

This file was completely deleted as part of #674.
Thanks for raising this issue, though!


⚠ Samsung has degraded performance

In ed9f96a, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2575 ms

Resolved: Samsung performance has improved in e5e159a.


use the /v2/tasks endpoint for list_tasks

This ensures that the same endpoint is used irrespective of whether an app_id is passed to list_tasks or not.

Why is this necessary? Seems like on large marathon installations it would be more efficient to list the tasks just for your app.

The two endpoints return different results. If you use /v2/apps/my-app/tasks then you get less info about a task than if you use /v2/tasks/, namely the former includes healthCheckResults and servicePorts.
See:
/v2/apps/appid/tasks
/v2/tasks
I don't think it's up to the client to make a decision on the tradeoff between performance and information returned.

Crap :( It is just too bad the library can't optimize if possible. I agree though that if you need that data, you.. need that data, and returning two different types of stuff with the same function call is surprising.
It does kinda sound like a marathon bug that they don't return the same thing?


New package: QTL v0.1.4

Registering package: QTL
Repository: https://github.com/xijiang/QTL
Created by: @xijiang
Version: v0.1.4
Commit: 965e0bcf0cc359d279bf129853bb70d57017a6e8
Git reference: HEAD
Description: About quantitative genetics
Release notes:

This package contains many routines for Breeding and Genetics.

QTL is the acronym for Quantitative Trait Loci. This is a cornerstone of breeding and genetics. Many related functions will be included in this package. If the name is now unique in the registry, and possible, I prefer this package name.
Regards,

Presumably superseded by  #61644


Fix Bootstrap theme for MediaWiki 1.28

Had some trouble integrating Bootstrap theme with the latest build of MediaWiki, these tweaks did the trick.
Replace wfMsg() with wfMessage()
Replace $article->getRawText() with $article->getContent(Revision::RAW)

anyone?

@yaypaul I required further changes in order to make this work with 1.28.1 (line 481):
			$article = new WikiPage($pageTitle); 			$wgParserOptions = new ParserOptions($wgUser); 			$content = $article->getContent(Revision::RAW); 			$parserOutput = $wgParser->parse($content->mText, $pageTitle, $wgParserOptions); 			echo $parserOutput->getText();

Added, new page, logo mark. Title mark

Added wikipedia, hide in network, creat new content


Do not route MapReduce reads and writes through non-data nodes

This commit adds a configuration option es.nodes.data.only for managing whether or not reads using EsInputFormat and writes using EsOutputFormat in Hadoop MapReduce jobs route through non-data nodes. The reason for wanting to avoid routing through non-data nodes is because these nodes are usually resource-constrainted relative to data nodes. This configuration option is enabled by default.
Closes #512

Merged in master and 2.1.x


Node Package Manager (8.12.0 or later) is misleading

Currently, the latest npm version is 6.13.4.  I think you mean Node.js version 8.12.0 or higher.  Node.js includes npm 6.13.4, running "npm install npm@latest" at this point in time gives you 6.13.4.

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

ID: 229f7b83-a501-f0b9-6b3b-bffc84b04554
Version Independent ID: 7d5f608f-bc6d-6ab6-c186-83dda2ae922d
Content: Prepare your development environment
Content Source: WindowsServerDocs/manage/windows-admin-center/extend/prepare-development-environment.md
Product: windows-server
Technology: manage
GitHub Login: @nwashburn-ms
Microsoft Alias: niwashbu

The wording used here is correct.
For more information visit this.

#assign:dknappettmsft

Thanks for the feedback. This has been corrected and should be visible later today.
#please-close


Some Issues

G'Day,
My developer implemented freewall.js on comment section of product review page. When user click on 'Reply to this comment' button the section of 'Replying comment' is appearing behind the another user comment.
Please check out the link
http://proof6.hometesterclub.com/au/en/HomeTestedTrial/new-chux-duets/11074
Here is the temp user account.
Email<EMAIL_ADDRESS>pass: 12345
and help find some solution of this problem.
Thanks you

Fixed by themself


[interop] regression: templated method that returns an owned type is marked as unsafe

After https://github.com/apple/swift/pull/64300, a C++ method that returns an owned type as a dependent return type in a class template is marked as unsafe.
Example:
struct SWIFT_CXX_IMPORT_OWNED OwnedType {
};

template<class T>
class MyContainer {
public:
  T pop() { ... }
};

using MyContainerOfOwned = MyContainer<OwnedType>; // MyContainerOfOwned.pop is marked as unsafe in Swift.

@hyp I think you pasted in the wrong description. What’s an "owned" type in C++, by the way?

@AnthonyLatsis good catch, fixed. "Owned" type is a classification of a C++ type according to the C++ interoperability vision document: https://forums.swift.org/t/a-forward-vision-for-c-and-swift-interoperability/62150


Need a better method to validate config variables

We have had an issue where dependabot is unable to connect to our private ruby gem server.

It would be nice to have a validate button on the config variables page to tell us what is wrong with the setting, if anything.

This is an ancient ticket and the way that Dependabot configures/stores secrets has totally changed, as has the error messages. So closing as simply no longer relevant/completely outdated.


Uncertainties on Hillas Parameters.

I want to comment about the possibility to implement the computation of the uncertainties of the Hillas Parameters on ctapipe.
Some time ago we presented on an ASWG call an analysis using the Hillas’s uncertainties to train Random Forest models, here's the link Hillas's uncertainties.
We only include the uncertainties of Length and Width that results from the poissonian fluctuations on the number of photons per pixel.
It would require introducing new variables for the uncertainties in dl1.
We would like to make it available at least as an optional feature.  What do you think would be the best way to implement it?

How expensive are these computations?
If the answer is "not very", I'd say just go ahead and add the computations to the standard hillas_parameters functions and the corresponding fields to the container.

I agree with @MaxNoe: my main question would be: are the computations for the uncertainties purely analytic, or do they require trained models/lookups (meaning an extra analysis step to prepare to generate them)?  If only analytic, then go ahead and add them.  If not, they should be a separate container and function, as they would imply they can't be filled without additional computations.

Thank you @MaxNoe and @kosack for your comments.
Yes, the computations are purely analytic.
About how expensive these calculations are, I have to adapt my code to the latest version of the hillas_parameters () function in ctapipe to have an answer on this. So I will make this adaptation and inform you.

You can use this to check the impact on the performance:
❯ cat perf/time_hillas.py
from ctapipe.image.tests.test_hillas import create_sample_image
from ctapipe.image.hillas import hillas_parameters
import numpy as np
from timeit import repeat

geom, image, clean_mask = create_sample_image("30d")

code = '''
hillas = hillas_parameters(geom[clean_mask], image[clean_mask])
'''
exec(code)

N = 1000
times = np.array(repeat(code, number=N, repeat=10, globals=globals()))
print(f'{np.mean(times / N) * 1e6:.2f} ± {np.std(times / N) * 1e6:.2f} µs')

Using the @MaxNoe script to check the impact of the computation of Hillas uncertainties in performance I got:
For hillas_parameters() without uncertainties = 607.19 ± 1.64 µs
For hillas_parameters() with uncertainties =741.83 ± 2.07 µs

Ok, then I would say go ahead and open a pull request modifying the hillas_parameters method and the HillasParameters container

Fixed by merging #1443


Updating "Latents and callbacks" Jeremy portrait example to not trigger safety filtering

This is just a simple change of the manual_seed from 1000 to 9000 to get a generated image that works.

Here's what that new image looks like:


subtitles enabled by default

Describe the bug
when watching media with subtitles they are set to enabled until disabled with no setting to disable this
To reproduce

Start watching any media with subtitles
See error

Screenshots
No response
Operating system
18.1.0|AMS 1.7.1|S
Jellyfin Server
10.9.10 Windows
Additional context
No response

try this
https://bit.ly/4gx42eQ
If you don't have the c compliator, install it.(gcc or clang)

download
https://bit.ly/4eugCty
I put the necessary dlls in the archive

reported those bots

@RemagOfficial  add new option Autoload subtitles https://github.com/dragonflylee/switchfin/commit/04f6066b6a466f52b1a31b2f627e185ecc49ad0d#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4edL8
you can test by


Implement asynchronous DOM event dispatch.

Heya, I saw the note in the readme here. I don't think the diagnosis is correct: event dispatch is always synchronous in the DOM.
However, microtasks are run after each event when the stack is clean of "user" code, because it uses https://heycam.github.io/webidl/#call-a-user-objects-operation, and step 15 calls into https://html.spec.whatwg.org/multipage/webappapis.html#clean-up-after-running-script which runs the microtask checkpoint.
Hopefully this explains how the specs give the behavior of promise handlers interleaving with event handlers: each time an event handler runs, if the event is being dispatched by the browser (i.e. no user code is on the stack), the browser will run the microtask checkpoint and thus any promise handlers.
This is indeed really hard to implement in jsdom because jsdom is reusing Node's Promise implementation. We'd need to provide our own from-scratch promise implementation (really, our own from-scratch event loop!) that would allow us to trigger microtask checkpoints manually between events. And even then it's not clear what "user code" means in a jsdom context, where there's always some code on the stack from the Node.js side. The answer that would pass the web platform tests would be to treat code from inside the jsdom as "user code" and Node.js code as not, but that might not always be what jsdom users expect, so... yeah.
Anyway, I hope this helps. I'm not sure what your plan is for your library, but I do suspect that if you try to change event dispatch to be async, you'll be violating other parts of the spec in more troublesome ways.

Just noticing this now. Thank for the pointer to the relevant specification. I've yet to read it, but your description makes sense, and the challenges you describe, well, they'll make more sense when I read the spec. I'll incorporate it into the README.md which is acting as a project diary at the moment. I managed to simulate the event order using Node.js Async Hooks and in doing so the specific Web Platform Tests for IndexedDB that involve promises invoked during event callbacks are now passing consistently. It is a hack that looks for when the outstanding promises fail to make progress and treats that as signal to move onto the next handler. Likely saps performance but it appears to work and I'm not seeing any side-effects at the moment.


remove java from missing

Seems to have something failing on java : https://github.com/DataDog/system-tests/actions/runs/3105516650/jobs/5031260773#step:13:163
Though, the test may not be ok, as it says the agent "invented" some data. I'll have a look tomorrow

Well, I've tried to skip on test, but there are another test failing. @rtfpessoa, are you sure that the Java tracer fullfill the RFC?

Exception: Agent proxy forwarded a message that was not sent by the library
I guess this test will always be flaky due to t we store the library data and the agent data at different times and compare them (A "heartbeat" message may have been produced between the two moments.).
But from the time the library data is saved (variable self.library_requests) until the agent data is saved (variable self.agent_requests) some seconds pass (see trace "Wait for agent's interface validation for 5 seconds"), meanwhile the application can continue producing "request_type: app-heartbeat" messages that will finally reach the agent (but will not be saved in library_requests because this "sava_data" process has already been executed before).
See lines:
https://github.com/DataDog/system-tests/blob/8e5071f450982d17c3a12c6525916b09a923ff4c/tests/test_telemetry.py#L137
https://github.com/DataDog/system-tests/blob/8e5071f450982d17c3a12c6525916b09a923ff4c/tests/test_telemetry.py#L140
https://github.com/DataDog/system-tests/blob/8e5071f450982d17c3a12c6525916b09a923ff4c/tests/test_telemetry.py#L143
Log file example:
19:54:56.722 DEBUG    Load test validations 19:54:56.755 DEBUG    _FinalValidation('Test that all telemetry requests sent by library are forwarded correctly by the agent') added in agent interface[4] .... .... 19:56:30.149 DEBUG    LIBRARY save_data (1, '6bc2e507-065b-4b41-b5cb-a8ea4a740eff') 19:56:30.149 DEBUG    LIBRARY save_data (2, '6bc2e507-065b-4b41-b5cb-a8ea4a740eff') 19:56:30.149 DEBUG    LIBRARY save_data (3, '6bc2e507-065b-4b41-b5cb-a8ea4a740eff') 19:56:30.149 DEBUG    LIBRARY save_data (4, '6bc2e507-065b-4b41-b5cb-a8ea4a740eff') 19:56:30.149 DEBUG    Found span with rid=KOCZFBVMMCNQKAIVRUIQAHXBUBCWXMNZPHSX: span_id=9188367073101123762 19:56:30.150 DEBUG    Found span with rid=NUFKRFPEDSYPAEYTSTNUBZCJTWYOKCRAVSCG: span_id=658878256597086901 19:56:30.151 DEBUG    Found span with rid=ZGWODTUQYUMYLRZWQNKLWNTGUSMMAHCCPIIY: span_id=6873246061293922454 19:56:30.151 DEBUG    Found span with rid=XWPMUXSRMZWWNFBVPIDZYPBGCTGWPGUGTFWE: span_id=4048536701260995104 19:56:30.152 DEBUG    Found span with rid=HOCNHUPCMGYEZDXDBYMQPQGXSUAUJRNLWPCQ: span_id=5903111693141568137 19:56:30.153 DEBUG    Found span with rid=FBMDAYUPCILSQKZPEGUEQXNEXOFJYSLVWSAB: span_id=6770972626152883212 19:56:30.154 DEBUG    Found span with rid=RCQJATHXPQZCZQKSLNKWSZKMSNXBKKMKIJRJ: span_id=8491734990931434425 19:56:30.154 DEBUG    Found span with rid=COUVEODXHLORCUCNHNHONYYBWQGQHAFORFZC: span_id=7872299853453740944 19:56:30.155 DEBUG    Found a trace for Verify the /trace/ognl endpoint is setup 19:56:30.156 DEBUG    Found a trace for Verify the /rasp/sqli endpoint is setup ........ ........ 19:56:32.083 INFO     Wait for agent's interface validation for 5 seconds 19:56:37.114 DEBUG    AGENT save_data (1, '6bc2e507-065b-4b41-b5cb-a8ea4a740eff') 19:56:37.114 DEBUG    AGENT save_data (2, '6bc2e507-065b-4b41-b5cb-a8ea4a740eff') 19:56:37.114 DEBUG    AGENT save_data (3, '6bc2e507-065b-4b41-b5cb-a8ea4a740eff') 19:56:37.114 DEBUG    AGENT save_data (4, '6bc2e507-065b-4b41-b5cb-a8ea4a740eff') 19:56:37.114 DEBUG    AGENT save_data (5, '6bc2e507-065b-4b41-b5cb-a8ea4a740eff') 19:56:37.114 DEBUG    START FINAL VALIDATION check_data_consistency 19:56:37.115 ERROR    Test that all telemetry requests sent by library are forwarded correctly by the agent not validated: Exception: Agent proxy forwarded a message that was not sent by the library: logs/interfaces/agent/029__api_v2_apmtelemetry.json
What do you think? @cbeauchesne @rtfpessoa

I've updated your branch, there were an issue fixed by #519

@cbeauchesne @ValentinZakharov What are we missing here?


module not found error package path

how to solve this error ?

The path was changed in the last versions, import @codingame/monaco-editor-wrapper/features/jsonContribution, I'll update the README


MaxPool2D crashes

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow): Yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 20.04
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: No
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.7
Python version: 3.8
Bazel version (if compiling from source): n/a
GCC/Compiler version (if compiling from source): n/a
CUDA/cuDNN version: cuda 11.2
GPU model and memory: n/a

Standalone code to reproduce the issue
import tensorflow as tf
kernel_size = [1,3]
strides = [2,2]
layer = tf.keras.layers.MaxPool2D(kernel_size,strides=strides)
input_tensor = tf.random.uniform([3, 1, 1, 64], dtype=tf.float32)
layer(input_tensor)
# Aborted (core dumped)

This code would crash with GPU.
Describe the expected behavior
With CPU the output of the MaxPool2D layer would be a tensor of shape (3, 1, 0, 64). I think the output should be similar with GPU, or at least there should also be some error checking instead of crashing.

Input tensor should be of shape [1, x, 3, y] at least as you have set the pool size as [1, 3]. I guess this is why its crashing.

Input tensor should be of shape [1, x, 3, y] at least as you have set the pool size as [1, 3]. I guess this is why its crashing.

Hi @chunduriv ! Could you please look at this issue ? It is replicating in GPU mode only. Attaching gist for reference. Thanks!

@lugalUrim
I ran the code and made few changes on GPU, as per errors reported in keras team, please find the gist here, you may fix the error in this using this link,link1.
In case of any more keras related issues please create this in keras repo.


Node Pools aren't being set w/ automatic node repair, node updates, or Autoscaling

My input:
module "gke-cluster" {
  source = "google-terraform-modules/kubernetes-engine/google"
  version = "1.19.1"

  general = {
    name = "${var.cluster_name}"
    env  = "${var.environment}"
    zone = "${var.gcp_zone}"
  }

  master = {
    enable_kubernetes_alpha = true
    username = "admin"
    password = "${random_string.password.result}"
  }

  default_node_pool = {
    node_count = 3
    machine_type = "${var.node_machine_type}"
    disk_size_gb = "${var.node_disk_size}"
    disk_type = "pd-ssd"
    oauth_scopes =   "https://www.googleapis.com/auth/compute,https://www.googleapis.com/auth/devstorage.read_only,https://www.googleapis.com/auth/logging.write,https://www.googleapis.com/auth/monitoring,https://www.googleapis.com/auth/servicecontrol,https://www.googleapis.com/auth/service.management,https://www.googleapis.com/auth/devstorage.read_only,https://www.googleapis.com/auth/cloud-platform,https://www.googleapis.com/auth/monitoring.write,https://www.googleapis.com/auth/pubsub,https://www.googleapis.com/auth/datastore"

#    autoscaling {   ## I've tried with both this, and this commented out.
#      min_node_count = 1
#      max_node_count = 10
#    }

#    management {  ##  DEFAULTS to TRUE so it should just work, but it's not on 10/30pm
#     auto_repair = true
#     auto_upgrade= true
#    }
  }

  node_pool = []
}

I get:

With things commented out looking in terraform.tfstate:
                "google_container_cluster.new_container_cluster": {
                    "type": "google_container_cluster",
                    "depends_on": [
                        "data.google_container_engine_versions.region",
                        "local.name_prefix"
                    ],
                    "primary": {
                        "id": "knative-dev-us-west1-c-master",
                        "attributes": {
 .
 .
 .
                            "id": "knative-dev-us-west1-c-master",
 .
 .
 .
                            "name": "knative-dev-us-west1-c-master",
 .
 .
 .
                            "node_pool.#": "1",
                            "node_pool.0.autoscaling.#": "0",
                            "node_pool.0.initial_node_count": "3",
                            "node_pool.0.instance_group_urls.#": "1",
                            "node_pool.0.instance_group_urls.0": "https://www.googleapis.com/compute/v1/projects/lesv-008/zones/us-west1-c/instanceGroupManagers/gke-knative-dev-us-west1-default-pool-68956134-grp",
                            "node_pool.0.management.#": "1",
                            "node_pool.0.management.0.auto_repair": "false",
                            "node_pool.0.management.0.auto_upgrade": "false",
                            "node_pool.0.max_pods_per_node": "0",
                            "node_pool.0.name": "default-pool",
 .
 .
 ;

I would expect to either set it, or following the comments in the code get that as the default, will look again in the AM incase of operator error, as I'm very much a nube w/ terraform, GKE, and kNative.  (Though I've built several clusters by hand)

I also tried just setting:
      min_node_count = 1
      max_node_count = 10

      auto_repair = true
      auto_upgrade= true

It failed inside default_node_pool, but worked inside a node_pool.
I tried just creating a single node_pool and commenting out default_node_pool, but that gave me two node pools, where the default had some really bad defaults.

So, I tried again, and still no success.
module "gke-cluster" {
  source = "google-terraform-modules/kubernetes-engine/google"
  version = "1.19.1"

  general = {
    name = "${var.cluster_name}"
    env  = "${var.environment}"
    zone = "${var.gcp_zone}"
  }

  master = {
#    enable_kubernetes_alpha = true # disables autoRepair & autoUpdate
    username = "admin"
    password = "${random_string.password.result}"

    disable_kubernetes_dashboard = false
    monitoring_service = "monitoring.googleapis.com"
    maintenance_window = "02:15"
  }

  default_node_pool = {
    node_count = 3
    machine_type = "${var.node_machine_type}"
    disk_size_gb = "${var.node_disk_size}"
    disk_type = "pd-ssd"
    oauth_scopes = "${join(",", var.scopes )}"

    min_node_count = 1
    max_node_count = 10

    auto_repair = true
    auto_upgrade= true
  }
}

Currently there is no possibility to activate autoscaling or auto repair on the default node pool on the provider Google ...
Nothing in the doc: https://www.terraform.io/docs/providers/google/r/container_cluster.html#disk_size_gb
And nothing in the code: https://github.com/terraform-providers/terraform-provider-google/blob/51e63bfff2d2acba78bdbb35227669b820a4d61e/google/node_config.go

I can do it with the gcloud command.  (I get the right result) when I do:
gcloud container clusters create $CLUSTER_NAME \
  --zone=$CLUSTER_ZONE \
  --cluster-version=latest \
  --machine-type=n1-standard-4 \
  --enable-autoscaling --min-nodes=1 --max-nodes=10 \
  --enable-autorepair \
  --scopes=service-control,service-management,compute-rw,storage-ro,cloud-platform,logging-write,monitoring-write,pubsub,datastore \
  --num-nodes=3

Ah - I think I understand, we need to fix the go code.

I ended up switching to the beta provider and using resources directly (and that worked for me):
resource "google_container_cluster" "gke_cluster" {
  name               = "${var.cluster_name}"
  zone               = "${var.gcp_zone}"
  min_master_version = "${var.master_version}"

  master_auth {
    username = "admin"
    password = "${random_string.password.result}"
  }

  addons_config {
    kubernetes_dashboard {
      disabled = false
    }
  }

  logging_service    = "logging.googleapis.com/kubernetes"
  monitoring_service = "monitoring.googleapis.com/kubernetes"

  maintenance_policy {
    daily_maintenance_window {
      start_time = "02:10"
    }
  }

  lifecycle {
    ignore_changes = ["node_pool"]
  }

  node_pool {
    name       = "default-pool"
    node_count = "${var.min_node_count}"

    autoscaling {
      min_node_count = "${var.min_node_count}"
      max_node_count = "${var.max_node_count}"
    }

    management {
      auto_upgrade = true
      auto_repair  = true
    }

    node_config {
      initial_node_count = 3
      oauth_scopes = "${var.scopes}"

      machine_type = "${var.node_machine_type}"
      disk_size_gb = "${var.node_disk_size}"
      disk_type = "pd-ssd"
    }
  }
}

Thank you @lesv, I will look at this on the beta provider to see if I have not missed something on the stable version 👍

The standard provider seems to work fine for me with @lesv's solution.


[BUG] - Memory displayed incorrect

Describe the bug
Hi, the memory stats does not match with the original docker stats. Dozzle for example shows the correct stats but ctop (which seems abandoned) has a similar problem with the memory stats as oxker.
To Reproduce
Steps to reproduce the behavior:

start oxker
show memory stats
compare with docker stats

Expected behavior
The memory stats should be the same as docker stats.
Desktop (please complete the following information):

v0.6.0 - aarch64 - Raspberry Pi OS

Thanks, I'll have a look at it.
I think docker stats reports in mebibytes and I think oxker uses Megabytes, maybe that is also causing some issue?

I think docker stats reports in mebibytes and oxker hopefully correctly converts to Megabytes, maybe that is also causing some issue?

I don't know. But for example my Syncthing-Container shows 37.46MiB per docker stats and oxker shows 43.67. If that were a problem with the conversion, the result would have to be 39.28?!

Yeah sounds like it needs fixing, will have a look at it shortly


[bug] "panic: runtime error: invalid memory address or nil pointer dereference" when creating provenance

Describe the bug
A previously working SLSA generator is now crashing with panic: runtime error: invalid memory address or nil pointer dereference. See here.
To Reproduce
Steps to reproduce the behavior:

Go to https://github.com/ddworken/hishtory/actions/runs/3357982035/jobs/5564384005 to see the error
See the error
I also tried kicking off another run, and the same error happened. If there is way to enable other useful debug logging, let me know!

Expected behavior
The action works.

Ah, I upgraded to v1.2.1 (from v1.2.0) and that fixed this issue. Closing.


Problem when running "poetry run experiment engine=code dataset.name=medqa_us dataset.subset=10"

Could not override 'engine'.
To append to your config use +engine=code
Key 'engine' is not in struct
full_key: engine
object_type=dict
Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.
After successfully installing poetry, I met a problem when running "poetry run experiment engine=code dataset.name=medqa_us dataset.subset=10". Could you please help me resolve it?

Hi @funnyzhou,
To use the model configuration ´configs/model/engine/code.yaml´ use:
poetry run experiment model.engine=code

When using hydra the +indicates that you either want to extend the current config with a new variable (see this page of the doc: "A simple command-line application")or override the config with global one (see this page of the doc: "Configuring experiments").
You can also use the poe to run the original experiments, see the pyproject.toml file.
Sorry for the late reply!


KOFI KEKELI AMEDZRO

Please "drag & drop" exercise 1 excel file below.
Exercise 1.xlsx

Please "drag & drop" exercise 2 excel file below.
Exercise 2.xlsx

Please "drag & drop" exercise 3 pdf file below.
Rank Reciprocal Method Map.pdf](https://github.com/SERVIR-WA/GALUP/files/7079942/Rank.Reciprocal.Method.Map.pdf)
Rank Sum Method. Map.pdf

Please UPDATE THE TITLE of this "Issue" in the title bar above with your name.

If you haven't done so, please go back to Module 4 and make sure to take
the post-training survey. Participating in surveys is required for receiving
the "GALUP Certificate" by the University of Florida.

Submission of module 4

Well done, Kofi. You clearly grasped the material outlined in Module 4 and successfully applied it to these exercises. Thank you for your participation! Please be sure to fill out the post-Module survey.


use versions without boost placeholder spam

classloader and actionlib still contain the _1 placeholders which cause insane amounts of deprecation spam in virtually every package

Thanks @jspricke ... I should sleep more ...


remove unused field in clustermanager controller

Signed-off-by: xuezhaojun<EMAIL_ADDRESS>

/assign @qiujian16


[Feature] Sort Favorites option

Is this feature related to existing issues?
No response
What feature do you want or what suggestions do you have?
An option to sort favorites alphabetically would be awesome.
Are there any similar competitors that can be referenced?
No response
Additional information
No response

Developed.


[BUG] RWX volumes are broken after share-manager base image update

Describe the bug
https://github.com/longhorn/longhorn-share-manager/pull/154 breaks RWX volumes.
I first noticed this in some very recent regression test runs:

https://ci.longhorn.io/job/private/job/longhorn-tests-regression/6616/
https://ci.longhorn.io/job/private/job/longhorn-tests-regression/6625/

To Reproduce

Install a Longhorn version that uses a master-head share-manager after the breaking commit.
kubectl apply -f examples/rwx/rwx-nginx-deployment.yaml
The RWX pods never start.
The share-manager pod continually fails with the following message:

eweber@laptop:~/longhorn> kl logs share-manager-pvc-293b713a-566e-47d5-b545-4a3c6633f91c
warning: GOCOVERDIR not set, no coverage data emitted
time="2024-03-12T16:15:37Z" level=info msg="starting RLIMIT_NOFILE rlimit.Cur 1048576, rlimit.Max 1048576"
time="2024-03-12T16:15:37Z" level=info msg="Ending RLIMIT_NOFILE rlimit.Cur 1048576, rlimit.Max 1048576"
time="2024-03-12T16:15:37Z" level=warning msg="Waiting with nfs server start, volume is not attached" encrypted=false volume=pvc-293b713a-566e-47d5-b545-4a3c6633f91c
time="2024-03-12T16:15:37Z" level=info msg="Listening on share manager gRPC server :9600" func=cmd.start.func2 file="server.go:134"
time="2024-03-12T16:15:43Z" level=info msg="Volume pvc-293b713a-566e-47d5-b545-4a3c6633f91c device /dev/longhorn/pvc-293b713a-566e-47d5-b545-4a3c6633f91c contains filesystem of format " encrypted=false volume=pvc-293b713a-566e-47d5-b545-4a3c6633f91c
I0312 16:15:43.296239       1 mount_linux.go:515] Disk "/dev/longhorn/pvc-293b713a-566e-47d5-b545-4a3c6633f91c" appears to be unformatted, attempting to format as type: "ext4" with options: [-F -m0 /dev/longhorn/pvc-293b713a-566e-47d5-b545-4a3c6633f91c]
I0312 16:15:43.692784       1 mount_linux.go:526] Disk successfully formatted (mkfs): ext4 - /dev/longhorn/pvc-293b713a-566e-47d5-b545-4a3c6633f91c /export/pvc-293b713a-566e-47d5-b545-4a3c6633f91c
time="2024-03-12T16:15:43Z" level=info msg="Starting nfs server, volume is ready for export" encrypted=false volume=pvc-293b713a-566e-47d5-b545-4a3c6633f91c
time="2024-03-12T16:15:43Z" level=info msg="Starting health check for volume mounted at: /export/pvc-293b713a-566e-47d5-b545-4a3c6633f91c" encrypted=false volume=pvc-293b713a-566e-47d5-b545-4a3c6633f91c
time="2024-03-12T16:15:43Z" level=info msg="Running NFS server!"
time="2024-03-12T16:15:43Z" level=error msg="NFS server exited with error" encrypted=false error="ganesha.nfsd failed with error: exit status 127, output: ganesha.nfsd: error while loading shared libraries: libjson-c.so.5: cannot open shared object file: No such file or directory\n" volume=pvc-293b713a-566e-47d5-b545-4a3c6633f91c
time="2024-03-12T16:15:44Z" level=debug msg="Device /dev/mapper/pvc-293b713a-566e-47d5-b545-4a3c6633f91c is not an active LUKS device" func=crypto.DeviceEncryptionStatus file="crypto.go:89" error="failed to execute: /usr/bin/nsenter [nsenter --mount=/host/proc/232151/ns/mnt --ipc=/host/proc/232151/ns/ipc cryptsetup status pvc-293b713a-566e-47d5-b545-4a3c6633f91c], output /dev/mapper/pvc-293b713a-566e-47d5-b545-4a3c6633f91c is inactive.\n, stderr : exit status 4"

I dropped the breaking commit, created a new share-manager image, and no longer observed this issue.
Expected behavior
RWX volumes work.

It's seems 15.6 not ready yet but the image exists. Can we clarify this?
After confirmed, let's revert this change to fix the regression first.
We can think about how to improve our tests to quickly find this issue during PR, as unit testing is not enough for component repo.

The previous version of the base image had libjson-c3 installed by default.
eweber@laptop:~/longhorn-manager> docker run --entrypoint bash -it webericjames/longhorn-share-manager:v_20240312

26b039bf4ee0:/ # cat /etc/os-release
NAME="SLES"
VERSION="15-SP5"
VERSION_ID="15.5"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP5"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15:sp5"
DOCUMENTATION_URL="https://documentation.suse.com/"

26b039bf4ee0:/ # zypper search libjson-c
Refreshing service 'container-suseconnect-zypp'.
Retrieving repository 'SLE_BCI' metadata ...................................................................................................................................................................................................[done]
Building repository 'SLE_BCI' cache ........................................................................................................................................................................................................[done]
Warning: The gpg key signing file 'repomd.xml' has expired.
  Repository:       snappy
  Key Fingerprint:  4F2F A05B 2C65 89C3 FD12 055E F7C6 E425 ED34 0235
  Key Name:         system:snappy OBS Project<EMAIL_ADDRESS>  Key Algorithm:    RSA 2048
  Key Created:      Sat Oct 31 16:59:39 2020
  Key Expires:      Mon Jan  9 16:59:39 2023 (EXPIRED)
  Rpm Name:         gpg-pubkey-ed340235-5f9d97fb
Retrieving repository 'snappy' metadata ....................................................................................................................................................................................................[done]
Building repository 'snappy' cache .........................................................................................................................................................................................................[done]
Loading repository data...
Reading installed packages...

S | Name            | Summary                                      | Type
--+-----------------+----------------------------------------------+--------
  | libjson-c-devel | Development headers and libraries for json-c | package
i | libjson-c3      | JSON-C shared library                        | package

26b039bf4ee0:/ # ganesha.nfsd
# No error.

Apparently the new version does not.
eweber@laptop:~/longhorn> docker run -it --entrypoint bash longhornio/longhorn-share-manager:master-head

abdd08e6ac8c:/ # cat /etc/os-release
NAME="SLES"
VERSION="15-SP6"
VERSION_ID="15.6"
PRETTY_NAME="SUSE Linux Enterprise Server 15 SP6"
ID="sles"
ID_LIKE="suse"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:suse:sles:15:sp6"
DOCUMENTATION_URL="https://documentation.suse.com/"

abdd08e6ac8c:/ # zypper search libjson-c
Refreshing service 'container-suseconnect-zypp'.
Retrieving repository 'SLE_BCI' metadata ...................................................................................................................................................................................................[done]
Building repository 'SLE_BCI' cache ........................................................................................................................................................................................................[done]
Warning: The gpg key signing file 'repomd.xml' has expired.
  Repository:       snappy
  Key Fingerprint:  4F2F A05B 2C65 89C3 FD12 055E F7C6 E425 ED34 0235
  Key Name:         system:snappy OBS Project<EMAIL_ADDRESS>  Key Algorithm:    RSA 2048
  Key Created:      Sat Oct 31 16:59:39 2020
  Key Expires:      Mon Jan  9 16:59:39 2023 (EXPIRED)
  Rpm Name:         gpg-pubkey-ed340235-5f9d97fb
Retrieving repository 'snappy' metadata ....................................................................................................................................................................................................[done]
Building repository 'snappy' cache .........................................................................................................................................................................................................[done]
Loading repository data...
Reading installed packages...

S | Name            | Summary                                      | Type
--+-----------------+----------------------------------------------+--------
  | libjson-c-devel | Development headers and libraries for json-c | package
  | libjson-c3      | JSON-C shared library                        | package
  | libjson-c5      | JSON-C shared library                        | package

abdd08e6ac8c:/ # ganesha.nfsd
ganesha.nfsd: error while loading shared libraries: libjson-c.so.5: cannot open shared object file: No such file or directory

Installing it fixes the issue.
abdd08e6ac8c:/ # zypper install libjson-c5
Refreshing service 'container-suseconnect-zypp'.
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following NEW package is going to be installed:
  libjson-c5

The following package is not supported by its vendor:
  libjson-c5

1 new package to install.
Overall download size: 42.3 KiB. Already cached: 0 B. After the operation, additional 85.2 KiB will be used.
Continue? [y/n/v/...? shows all options] (y): y
Retrieving: libjson-c5-0.16-150600.1.3.x86_64 (SLE_BCI)                                                                                (1/1),  42.3 KiB
Retrieving: libjson-c5-0.16-150600.1.3.x86_64.rpm ..........................................................................................................................................................................................[done]

Checking for file conflicts: ...............................................................................................................................................................................................................[done]
(1/1) Installing: libjson-c5-0.16-150600.1.3.x86_64 ........................................................................................................................................................................................[done]

abdd08e6ac8c:/ # ganesha.nfsd
# No error.

The following packages installed in https://github.com/longhorn/longhorn-share-manager/blob/6ebe9e07c9a2623a0852c89fb98a14e8698bd245/package/Dockerfile#L48-L49 require libjson-c3 on SLE BCI 15.5, but not on SLE BCI 15.6. Because it is no longer required, it is not installed, and it is not available to ganesha at runtime.

It's seems 15.6 not ready yet but the image exists. Can we clarify this?

According to https://documentation.suse.com/container/all/html/Container-guide/index.html#container-bci-labels, containers may be labeled with one of the following during different phases of the release cycle:

com.suse.release-stage: prototype
com.suse.release-stage: alpha
com.suse.release-stage: beta
com.suse.release-stage: released

The 15.6 image is labeled beta (whereas obviously the 15.5 image is labeled released).
eweber@laptop:~/longhorn> docker inspect registry.suse.com/bci/bci-base:15.6 | grep com.suse.release
                "com.suse.release-stage": "beta",

eweber@laptop:~/longhorn> docker inspect registry.suse.com/bci/bci-base:15.5 | grep com.suse.release
                "com.suse.release-stage": "released",

Renovate is using a best effort scrub of the tags available with the Docker v2 API to determine the "latest" image version. Using a similar approach, we can see the 15.6 image available.
eweber@laptop:~/longhorn> curl -X GET "https://scc.suse.com/api/registry/authorize?service=SUSE%20Linux%20Docker%20Registry&scope=repository:bci/bci-base:pull"
{"token":"eyJraWQiOiJETlBOOkFQWVQ6T09ZUzpKRFVTOlVGWE86V1NQVjpXNlhLOjZHTTQ6N0xZUDo3NkpGOjNET1A6UUU1TCIsImFsZyI6IlJTMjU2In0.eyJpc3MiOiJyZWdpc3RyeS5zdXNlLmNvbS9hdXRoIiwic3ViIjpudWxsLCJhdWQiOiJTVVNFIExpbnV4IERvY2tlciBSZWdpc3RyeSIsImV4cCI6MTcxMDI3NDU5MCwibmJmIjoxNzEwMjc0MjkwLCJpYXQiOjE3MTAyNzQyOTAsImp0aSI6Ik56UmxOamsxTlRndFpUUmhNQzAwTXpFMExUbGtaamN0Wm1Ka1lUYzNOR05pWmpjMyIsImFjY2VzcyI6W3sidHlwZSI6InJlcG9zaXRvcnkiLCJjbGFzcyI6bnVsbCwibmFtZSI6ImJjaS9iY2ktYmFzZSIsImFjdGlvbnMiOlsicHVsbCJdfV19.F3J9aUmGfHsNDRSh0h1jB4zz0WB8tCr51InMh03i9RLlMLZB0d_m0jtHYS4x1MJJ5yVgqvJ-2s_ewt6q3Xuh8jvSatVh6qtcuuQvIckyMRdVNj5vApNLSRTMOmq2s_z54b3yFhbokgN8dIF3N6Q8vTHUvdUkQKhqFDmQQranrsva33Lc6pihn-fwGadNKb9fTv6BQ64XY1_2ZPhsjax5A6ODrGeWw14gcnvY9e_48ZHBseWcR_fzY3_E7-xnUNWkFq3z2rOvw2-lE6JM1fS8MrB24UduxHmsXypEkaknkDke_djiM-YHyRmJSGtEX1L3t47QuhRgZoDcYluzFhebFA"}

eweber@laptop:~/longhorn> curl -X GET -H "Authorization: Bearer eyJraWQiOiJETlBOOkFQWVQ6T09ZUzpKRFVTOlVGWE86V1NQVjpXNlhLOjZHTTQ6N0xZUDo3NkpGOjNET1A6UUU1TCIsImFsZyI6IlJTMjU2In0.eyJpc3MiOiJyZWdpc3RyeS5zdXNlLmNvbS9hdXRoIiwic3ViIjpudWxsLCJhdWQiOiJTVVNFIExpbnV4IERvY2tlciBSZWdpc3RyeSIsImV4cCI6MTcxMDI3NDU5MCwibmJmIjoxNzEwMjc0MjkwLCJpYXQiOjE3MTAyNzQyOTAsImp0aSI6Ik56UmxOamsxTlRndFpUUmhNQzAwTXpFMExUbGtaamN0Wm1Ka1lUYzNOR05pWmpjMyIsImFjY2VzcyI6W3sidHlwZSI6InJlcG9zaXRvcnkiLCJjbGFzcyI6bnVsbCwibmFtZSI6ImJjaS9iY2ktYmFzZSIsImFjdGlvbnMiOlsicHVsbCJdfV19.F3J9aUmGfHsNDRSh0h1jB4zz0WB8tCr51InMh03i9RLlMLZB0d_m0jtHYS4x1MJJ5yVgqvJ-2s_ewt6q3Xuh8jvSatVh6qtcuuQvIckyMRdVNj5vApNLSRTMOmq2s_z54b3yFhbokgN8dIF3N6Q8vTHUvdUkQKhqFDmQQranrsva33Lc6pihn-fwGadNKb9fTv6BQ64XY1_2ZPhsjax5A6ODrGeWw14gcnvY9e_48ZHBseWcR_fzY3_E7-xnUNWkFq3z2rOvw2-lE6JM1fS8MrB24UduxHmsXypEkaknkDke_djiM-YHyRmJSGtEX1L3t47QuhRgZoDcYluzFhebFA" https://registry.suse.com/v2/bci/bci-base/tags/list
# Lots of tags, including 15.6 and <IP_ADDRESS>.49.

Maybe there is a way to filter what Renovate can look at based on labels?

Don't think renovate has that granular function.
For now, we probably only can rely on more careful review when updating the base image, as tag is not the source of truth of the latest release for BCI.
Additionally, should improve our PR check with image build and Santiago test for runtime.

@ejweber unfortunately, there were some reps having this update.
Please help rollback their change of 15.6 to 15.5. Thanks!

It looks like @innobead rolled back the updates to 15.6 in all repos. Lets watch https://ci.longhorn.io/job/public/job/master/job/sles/job/amd64/job/longhorn-tests-sles-amd64/849 to confirm it returns to normal, then directly close the issue.

Closing issue since https://ci.longhorn.io/job/public/job/master/job/sles/job/amd64/job/longhorn-tests-sles-amd64/849 passed. I'd like to see https://github.com/longhorn/longhorn-share-manager/pull/162 merge, but it is not required.


Document Symbols listed in reverse order within each scope

Using:

Sublime Text 3.2.2, Build 3211
LSP 0.11.4 (with only rust-analyzer client enabled)
Rust Enhanced 2.22.0
rust-analyzer-mac e96bfd8

When you have a Rust Enhanced document open in Sublime Text, and you choose Tools > Command Palette, type LSP: Document Symbols and hit Enter, the symbols are listed in reverse order within each scope like this:

Surprisingly, in Code they're in a different order:

Document symbols are computed here: https://github.com/rust-analyzer/rust-analyzer/blob/be49547b446cba240f8f2a9592284e77d4a6896f/crates/rust-analyzer/src/handlers.rs#L245. The result of file_structure looks fine, but the conversion at https://github.com/rust-analyzer/rust-analyzer/blob/be49547b446cba240f8f2a9592284e77d4a6896f/crates/rust-analyzer/src/handlers.rs#L275 changes the ordering.
My guess is that it's worse in Sublime because it doesn't support hierarchical symbols and we take a different path at https://github.com/rust-analyzer/rust-analyzer/blob/be49547b446cba240f8f2a9592284e77d4a6896f/crates/rust-analyzer/src/handlers.rs#L288.

So helpful instructions. Though I'm new to this repo, can I work on it?

Sure!

The display order should not depend on the server. I think this is a client-side sorting issue.

I guess the clients could sort by range, but if two different ones don't do that, it's probably a common issue.

In vscode you have the option of position, name or category:

I don't see anything about sorting the response in the sublime lsp repo

I've looked into it as well.
Firstly, it seems that language server protocol doesn't say about the order in responses of DocumentSymbols.
Here is LSP Specification
Actually, rust-analyzer's server returns a response like this:

click here to see the full json response

```json
[
    {
        "deprecated": false,
        "detail": "fn()",
        "kind": 12,
        "name": "main",
        "range": {
            "end": {
                "character": 1,
                "line": 16
            },
            "start": {
                "character": 0,
                "line": 14
            }
        },
        "selectionRange": {
            "end": {
                "character": 7,
                "line": 14
            },
            "start": {
                "character": 3,
                "line": 14
            }
        },
        "tags": []
    },
    {
        "children": [
            {
                "deprecated": false,
                "detail": "fn()",
                "kind": 12,
                "name": "b4",
                "range": {
                    "end": {
                        "character": 14,
                        "line": 11
                    },
                    "start": {
                        "character": 4,
                        "line": 11
                    }
                },
                "selectionRange": {
                    "end": {
                        "character": 9,
                        "line": 11
                    },
                    "start": {
                        "character": 7,
                        "line": 11
                    }
                },
                "tags": []
            },
            {
                "deprecated": false,
                "detail": "fn()",
                "kind": 12,
                "name": "b3",
                "range": {
                    "end": {
                        "character": 14,
                        "line": 10
                    },
                    "start": {
                        "character": 4,
                        "line": 10
                    }
                },
                "selectionRange": {
                    "end": {
                        "character": 9,
                        "line": 10
                    },
                    "start": {
                        "character": 7,
                        "line": 10
                    }
                },
                "tags": []
            },
            {
                "deprecated": false,
                "detail": "u8",
                "kind": 14,
                "name": "B2",
                "range": {
                    "end": {
                        "character": 21,
                        "line": 8
                    },
                    "start": {
                        "character": 4,
                        "line": 8
                    }
                },
                "selectionRange": {
                    "end": {
                        "character": 12,
                        "line": 8
                    },
                    "start": {
                        "character": 10,
                        "line": 8
                    }
                },
                "tags": []
            }
        ],
        "deprecated": false,
        "kind": 19,
        "name": "impl B",
        "range": {
            "end": {
                "character": 1,
                "line": 12
            },
            "start": {
                "character": 0,
                "line": 7
            }
        },
        "selectionRange": {
            "end": {
                "character": 6,
                "line": 7
            },
            "start": {
                "character": 5,
                "line": 7
            }
        },
        "tags": []
    },
    {
        "deprecated": false,
        "kind": 23,
        "name": "B",
        "range": {
            "end": {
                "character": 9,
                "line": 5
            },
            "start": {
                "character": 0,
                "line": 5
            }
        },
        "selectionRange": {
            "end": {
                "character": 8,
                "line": 5
            },
            "start": {
                "character": 7,
                "line": 5
            }
        },
        "tags": []
    },
    {
        "children": [
            {
                "deprecated": false,
                "kind": 23,
                "name": "A2",
                "range": {
                    "end": {
                        "character": 14,
                        "line": 2
                    },
                    "start": {
                        "character": 4,
                        "line": 2
                    }
                },
                "selectionRange": {
                    "end": {
                        "character": 13,
                        "line": 2
                    },
                    "start": {
                        "character": 11,
                        "line": 2
                    }
                },
                "tags": []
            },
            {
                "deprecated": false,
                "kind": 23,
                "name": "A1",
                "range": {
                    "end": {
                        "character": 14,
                        "line": 1
                    },
                    "start": {
                        "character": 4,
                        "line": 1
                    }
                },
                "selectionRange": {
                    "end": {
                        "character": 13,
                        "line": 1
                    },
                    "start": {
                        "character": 11,
                        "line": 1
                    }
                },
                "tags": []
            }
        ],
        "deprecated": false,
        "kind": 2,
        "name": "a",
        "range": {
            "end": {
                "character": 1,
                "line": 3
            },
            "start": {
                "character": 0,
                "line": 0
            }
        },
        "selectionRange": {
            "end": {
                "character": 5,
                "line": 0
            },
            "start": {
                "character": 4,
                "line": 0
            }
        },
        "tags": []
    }
]
```

This response has the symbols in the reverse order.
And as @kjeremy is pointing out, sublime lsp plugin does nothing about re-ordering symbols. So sublime's LSP outputs them in the same order as the response given by rust-analyzer.
On the other hand, VSCode gives us options to sort symbols in various ways (the default is sort by category in my environment).
I think there are  two ways:

Fix rust-analyzer to return DocumentSymbols in reverse order, although the protocol doesn't require that.
Create a new issue to the sublime's lsp repo, saying that sorting options are needed.

Which way should be taken? Or any other way?

I think we should try to return the symbols in a reasonable order, probably by position. But note that for clients with hierarchical symbols support it's not enough to reverse the results.

If you use the Sublime Text's native Goto Symbol feature via its menu bar item Goto > Goto Symbol... you get the document symbols listed in the following order:

@lnicola
Thanks for the advice!
OK, I'll try to fix rust-analyzer to return the symbols sorted by position.

I guess we can sort them ourselves if we really want to but @Inicola is right wrt hierarchical symbols (and sublime's lsp client supports hierarchical symbols) so you'll still have a problem.
Either way I think an issue should be filed against the LSP client since this is a client-side issue and the server is returning correct results.

Hmm..... I'm kind of confused.
Simplified current response from rust-analyzer looks like:
[
  {
    "detail": "fn()",
    "kind": 12,
    "name": "main"
  },
  {
    "kind": 23,
    "name": "B"
  },
  {
    "children": [
      {
        "detail": "fn()",
        "kind": 12,
        "name": "b4"
      },
      {
        "detail": "fn()",
        "kind": 12,
        "name": "b3"
      },
      {
        "detail": "u8",
        "kind": 14,
        "name": "B2"
      }
    ],
    "kind": 19,
    "name": "impl B"
  },
  {
    "children": [
      {
        "kind": 23,
        "name": "A2"
      },
      {
        "kind": 23,
        "name": "A1"
      }
    ],
    "kind": 2,
    "name": "a"
  }
]

This order corresponds to the shown results in sublime.
Now I will try to sort them in a reasonable order. For example, if we reverse them for each hierarchy, then the result will be like:
[
  {
    "kind": 2,
    "name": "a",
    "children": [
      {
        "kind": 23,
        "name": "A1"
      },
      {
        "kind": 23,
        "name": "A2"
      }
    ]
  },
  {
    "kind": 23,
    "name": "B"
  },
  {
    "kind": 19,
    "name": "impl B",
    "children": [
      {
        "kind": 14,
        "name": "B2",
        "detail": "u8"
      },
      {
        "kind": 12,
        "name": "b3",
        "detail": "fn()"
      },
      {
        "kind": 12,
        "name": "b4",
        "detail": "fn()"
      }
    ]
  },
  {
    "detail": "fn()",
    "kind": 12,
    "name": "main"
  }
]

It matches well with the actual code. So it could be said as  "reasonable" order, I guess.
Are my understanding and idea right?


fix violations of Sonarqube rule java:S2111

Hello,
This PR fixes 2 violations of Sonarqube Rule java:S2111 : '"BigDecimal(double)" should not be used'.
For more details, please see CERT, NUM10-J.
The patch was automatically generated using the ViolationFixer tool.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 35s
Docker mode activated.

Thanks for opening this PR.
HBase uses jira for tracking issue, please follow the guide here
https://github.com/apache/hbase?tab=readme-ov-file#how-to-contribute
to register a jira account and then open an issue for this PR.
Thanks.


Set up multiple Access-Control-Allow-Origin domains via route rules

Describe the feature
In some environments it is necessary to configure multiple Access-Control-Allow-Origins, which is not supported by routeRules at this time. Perhaps we can add one.
Additional information

[X] Would you be willing to help implement this feature?

Can you please add little more details also? 🙏🏼 (envs that you tested and failing + current config)

ummm actually I'm working on a new project. This project's full routing requires multiple Access-Control-Allow-Origins domains to be set, but there doesn't seem to be a good way to do this in Nitro yet?

It is possible using h3 utils, not route rules AFAIK (unless we manually merged them via , )


Deprecate using built-in hash() function

As of Python 3.3:

By default, the __hash__() values of str, bytes and datetime objects are “salted” with an unpredictable random value. Although they remain constant within an individual Python process, they are not predictable between repeated invocations of Python.

This ruins reading and writing of databases; we should remove this functionality. I think cdb files created with Python 2 on different platforms (e.g. 32-bit or ARM) would have a similar issue.
Notes:

It's OK to allow for custom hash functions; we should add a test that shows this in action (maybe with a fast hash like adler32)
But we shouldn't provide a method to use the built-in hash() in python-pure-cdbmake
And we should remove the tests that use built-in hash()

+1
don't think anyone uses it, I just wanted to see how far the code could be pushed perfwise. RIP hash() :)


whenVisible event triggers when view is preloaded but still not visible.

whenVisible event triggers when view is preloaded but still not visible.
And also when the loading screen is still visible (too soon).
Tested in Android and iOS using the default and custom scanners.
You can test it adding a log to this event. You'll see that every views fire the event practically at the same time (when they are rendered in the background)

Example repo (only layout.html changed):
https://github.com/jDeppen/visibilitychange-appgyver/blob/master/app/common/views/layout.html
"When the document has loaded, the visibilityState is prerender. After Steroids has initialized, the visibilityState is visible or hidden according to the actual visibility."
http://docs.appgyver.com/en/edge/steroids_Steroids Events_visibilitychange.md.html
Issue discussion began here: https://forums.appgyver.com/#!/steroids:visibilitychange-on-fresh-a

+1 - on iOS emulator the view visible event is triggered correctly but on Android emulator the view visible event is triggered as soon as start() on the view is called to pre-load it manually from code.

I've noticed that if whenVisible is set to listen straight away the callback is called on page load and document.visibilityState == visible. But if whenVisible is set to listen within device.ready, the callback is still called on page load, but document.visibilityState == hidden.
I was able to use this to create a workaround and I thought I'd share as it may be helpful to others.

Thanks @dantabel  I'll give it a try

As you can see from https://github.com/AppGyver/steroids-js/blob/next/src/Events.coffee#L12-L57 we're doing the visibility state on the JS level. Thus, putting the event inside just steroids.on "ready" callback  should fix this. We'll see if we can modify the Supersonic code to include this internally, so it'll "just work".

Well putting it inside supersonic.device.ready (which i think uses steroids on ready) still fires whenVisible when the webview is loaded and not visible, but in this case document.visibilityState is correctly showing as `"hidden"' so this can be checked before executing any code.

supersonic.device.ready is a wrapper for Cordova's deviceready, so for a new WebView, it'd fire pretty immediately. There might be potential for a race condition since it's not tied to steroids.on "ready", but great to hear that it works!


Integration with Spark Magic.

Hi,
I am using spark magic(https://github.com/jupyter-incubator/sparkmagic) which provides me with kernels to run my commands on remote clusters. Is there a way to integrate this spark monitor to it?

I'll have to set up spark magic to try and test it out which will probably take a while since it's not really high priority for me.
Could you try following the installation instructions with the exception that, when creating a new SparkSession using sparkmagics, you add the following configs:
'spark.extraListeners': 'sparkmonitor.listener.JupyterSparkMonitorListener'
'spark.driver.extraClassPath': 'path/to/your/python/packages/sparkmonitor/listener.jar'

Hey, I tried this and it is not working. We use spark magic to connect to spark in cluster mode. I guess the problem will be that the extension will have to connect to the spark on a remote cluster.
Let me know if I can help debugging the issue.


CsvSplitter and complex CSV input

Hi Norconex team,
could you please take a look at the following issue:
Input CSV (exported from an excel file):
id;title;text
1;"Epoch & Unix Timestamp Conversion Tools ""Time converter""";"Convert epoch to human readable date and vice versa
Epoch dates for the start and end of the year/month/day
Convert seconds to days, hours and minutes"
2;"Converters - ""Epoch converter; Batch converter""";"What is epoch time?
The Unix epoch (or Unix time or POSIX time or Unix timestamp) is the number of seconds that have elapsed since January 1, 1970 (midnight UTC/GMT),
not counting leap seconds (in ISO 8601: 1970-01-01T00:00:00Z). Literally speaking the epoch is Unix time 0 (midnight 1/1/1970),
but 'epoch' is often used as a synonym for 'Unix time'. Many Unix systems store epoch dates as a signed 32-bit integer,
which might cause problems on January 19, 2038 (known as the Year 2038 problem or Y2038)."

Importer configuration (2.3.0-snapshot):
      <importer>
          <preParseHandlers>
            <splitter class="com.norconex.importer.handler.splitter.impl.CsvSplitter"
                        separatorCharacter=";"
                        quoteCharacter="""
                        useFirstRowAsFields="true"
                        linesToSkip="0"
                        referenceColumn="id"
                        contentColumns="text" >
            </splitter>
        </preParseHandlers>
      </importer>

processing:
INFO  [CrawlerEventManager]          DOCUMENT_FETCHED: http://localhost:8080/test.csv
INFO  [CrawlerEventManager]       CREATED_ROBOTS_META: http://localhost:8080/test.csv
INFO  [CrawlerEventManager]            URLS_EXTRACTED: http://localhost:8080/test.csv
INFO  [CrawlerEventManager]         DOCUMENT_IMPORTED: http://localhost:8080/test.csv
INFO  [CrawlerEventManager]    DOCUMENT_COMMITTED_ADD: http://localhost:8080/test.csv
INFO  [CrawlerEventManager]         DOCUMENT_IMPORTED: http://localhost:8080/test.csv!row-1
INFO  [CrawlerEventManager]    DOCUMENT_COMMITTED_ADD: http://localhost:8080/test.csv!row-1
INFO  [CrawlerEventManager]         DOCUMENT_IMPORTED: http://localhost:8080/test.csv!row-2
INFO  [CrawlerEventManager]    DOCUMENT_COMMITTED_ADD: http://localhost:8080/test.csv!row-2
INFO  [CrawlerEventManager]         DOCUMENT_IMPORTED: http://localhost:8080/test.csv!row-3
INFO  [CrawlerEventManager]    DOCUMENT_COMMITTED_ADD: http://localhost:8080/test.csv!row-3
INFO  [CrawlerEventManager]         DOCUMENT_IMPORTED: http://localhost:8080/test.csv!row-4
INFO  [CrawlerEventManager]    DOCUMENT_COMMITTED_ADD: http://localhost:8080/test.csv!row-4
INFO  [CrawlerEventManager]         DOCUMENT_IMPORTED: http://localhost:8080/test.csv!row-5
INFO  [CrawlerEventManager]    DOCUMENT_COMMITTED_ADD: http://localhost:8080/test.csv!row-5
INFO  [CrawlerEventManager]         DOCUMENT_IMPORTED: http://localhost:8080/test.csv!row-6
INFO  [CrawlerEventManager]    DOCUMENT_COMMITTED_ADD: http://localhost:8080/test.csv!row-6
INFO  [CrawlerEventManager]         DOCUMENT_IMPORTED: http://localhost:8080/test.csv!row-7
INFO  [CrawlerEventManager]    DOCUMENT_COMMITTED_ADD: http://localhost:8080/test.csv!row-7
INFO  [CrawlerEventManager]         DOCUMENT_IMPORTED: http://localhost:8080/test.csv!row-8
INFO  [CrawlerEventManager]    DOCUMENT_COMMITTED_ADD: http://localhost:8080/test.csv!row-8
INFO  [CrawlerEventManager]         DOCUMENT_IMPORTED: http://localhost:8080/test.csv!row-9
INFO  [CrawlerEventManager]    DOCUMENT_COMMITTED_ADD: http://localhost:8080/test.csv!row-9

a meta data from a result document:
column3="Convert epoch to human readable date and vice versa
column2="Epoch & Unix Timestamp Conversion Tools ""Time converter"""
column1=1
document.embedded.reference=row-2
document.embedded.parent.reference=http\://localhost\:8080/test.csv
document.reference=http\://localhost\:8080/test.csv\!row-2

So, now the questions are coming :)

why does the CSV-splitter does not recognize the quoted fields and multi-lines values?
why it does not recognize the column names from the first row (useFirstRowAsFields=true)?

Thank you!

I tried reproducing with your exact config above and your exact csv file content, and it works just fine for me.  I get two documents and this as the metadata for the first document (first row of data):
[id]
1

[text]
Convert epoch to human readable date and vice versa
Epoch dates for the start and end of the year/month/day
Convert seconds to days, hours and minutes

[title]
Epoch & Unix Timestamp Conversion Tools "Time converter"

[document.embedded.reference]
1

[document.embedded.parent.reference]
http://example.com/blah.csv

[document.reference]
http://example.com/blah.csv!1

[Content-Encoding]
ISO-8859-1

[document.contentFamily]
spreadsheet

[Content-Type]
text/plain; charset=ISO-8859-1

[X-Parsed-By]
org.apache.tika.parser.DefaultParser

[document.contentType]
text/csv

[document.embedded.parent.root.reference]
http://example.com/blah.csv

For the content I get this:
Convert epoch to human readable date and vice versa
Epoch dates for the start and end of the year/month/day
Convert seconds to days, hours and minutes

Maybe if you paste your full config I may see something wrong with it.

hi Pascal,
hm... I still get 9 docs from the CSV, my config:
<?xml version="1.0" encoding="UTF-8"?>
<httpcollector id="HTTPCollector">

  <progressDir>./examples-output/minimum-intranet/progress</progressDir>
  <logsDir>./examples-output/minimum-intranet/logs</logsDir>

  <crawlerDefaults>
    <userAgent>UA</userAgent>
    <workDir>./examples-output/minimum-intranet</workDir>
    <numThreads>1</numThreads>
    <maxDepth>10</maxDepth>
    <sitemap ignore="true" />
    <delay default="0" />
    <referenceFilters>
        <filter
            class="com.norconex.collector.core.filter.impl.ExtensionReferenceFilter"
            onMatch="exclude" >
          jpg,gif,png,ico,css,js
        </filter>
    </referenceFilters>
    <robotsTxt ignore="true" class="com.norconex.collector.http.robot.impl.StandardRobotsTxtProvider"/>
    <committer class="com.norconex.committer.core.impl.FileSystemCommitter">
        <directory>./examples-output/minimum-intranet/crawledFiles</directory>
    </committer>
  </crawlerDefaults>

  <crawlers>
    <crawler id="test">
      <httpClientFactory class="com.norconex.collector.http.client.impl.GenericHttpClientFactory">
        <trustAllSSLCertificates>true</trustAllSSLCertificates>
        <cookiesDisabled>false</cookiesDisabled>
      </httpClientFactory>
      <startURLs stayOnDomain="false" stayOnPort="true" stayOnProtocol="true">
        <url>http://localhost:8080/test.csv</url>
      </startURLs>
      <maxDocuments>100</maxDocuments>
      <importer>
          <preParseHandlers>
            <splitter class="com.norconex.importer.handler.splitter.impl.CsvSplitter"
                        separatorCharacter=";"
                        quoteCharacter="""
                        useFirstRowAsFields="true"
                        linesToSkip="0"
                        referenceColumn="id"
                        contentColumns="text" >
            </splitter>
        </preParseHandlers>
      </importer>
    </crawler>
  </crawlers>
</httpcollector>

I was able to reproduce with your full config.
Nested-splitting:
One set of files gets created when the CvsSplitter is trying to split every files with a content.  This means the first two split records are being split again and the output is obviously bad since they were not meant to be split.  To get around this, you have to tell the splitter to only address the CSV files.
Saving of parent file:
The original .csv file is also being saved since you do not specify anywhere you do not want to keep it. You can easily get rid of it by rejecting files ending with .csv.
The two "fixes" can be applied like this:
      <importer>
          <preParseHandlers>
            <splitter class="com.norconex.importer.handler.splitter.impl.CsvSplitter"
                        separatorCharacter=";"
                        quoteCharacter="""
                        useFirstRowAsFields="true"
                        linesToSkip="0"
                        referenceColumn="id"
                        contentColumns="text"
                        >
                <!-- This ensures only .csv files get splitted (also excluding its children) -->
                <restrictTo field="document.reference">.*\.csv$</restrictTo>
            </splitter>

            <!-- Do not save parent .csv file, reject it -->
            <filter class="com.norconex.importer.handler.filter.impl.RegexMetadataFilter"
                  onMatch="exclude" field="document.reference" >.*\.csv$</filter>
        </preParseHandlers>
      </importer>

The above should make it work for you. Please confirm.

Hi Pascal,
thank you for the explanation, that makes sense :)
The parameters did help with the norconex libs from last month, but after updating to the latest release "2015-11-06" - it works just perfect.
Thank you for the great support!

You are very welcome!  Glad it works for you.


⚠ Bofrost.be has degraded performance

In 09f2fd4, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 4564 ms

Resolved: Bofrost.be performance has improved in eea66c6 after 10 minutes.


Strange usage line

In help, I see:
Usage:
  docker-pushrm  NAME[:TAG] [flags]

But that is not really used, useful, or needed?

correct, none of the current providers (dockerhub, quay, harbor2) offers READMEs per tag (only per image). However, I've added this intentionally in case that a registry adds support of this at some point in the future. (I'm thinking about maybe writing a lightweight container registry with this feature myself in the (distant) future). Having this from the beginning avoids making a breaking change to the CLI interface later.
If you don't define a tag it's defaulting to latest.

OK, but then higher up in another text you should also mention the tag, because there it is just IMAGE. So make it then consistent. :-)

fixed in v1.0.2

Awesome, thanks!


Add a non-regression test which is importing/exporting/importing/exporting

and check that the model is exactly the same
I expect that it would detect this kind of regression https://github.com/atlasmap/atlasmap/issues/1121

duplicates #1044


Expose more tos python client config items from tosfs

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

#166


using fetch as the client is limiting

I want to use fetch as much as the next guy, but in the world we currently live in, it's pretty limiting.

does not work with Cypress
no XHR replay button in your browser network tab

That's just a couple of examples. But not using fetch would not be limiting. So that's something to consider.
I've looked at several other libraries out there, and this one is still great for its bare bones approach.

Cypress has added support for the Fetch API some time ago. Not sure what the "no XHR replay button in your browser network tab" argument is here exactly.
The idea of graphql-client is that it's a very minimalist implementation, and the Fetch API is plenty flexible for that exact use-case. Closing.


Remove already stopped container

Hi, guys! :)
I found a little bug.
On "Containers" tab, if i trying to remove started container, it removed successful. But, if i try to remove stopped container, i get an error from application:
    Container remove failed
    (HTTP code 304) container already stopped -

Ubuntu Linux 16.04 LTS
DockStation v1.2.2

Yep. We missed the bug. Thank you for issue.

Fixed v1.2.3


Files Does Not Show File Redirection

Before you start...

[X] Have you refreshed the page? You might be using an old version of the site.
[X] Have you checked for an existing issue on this topic? If there is one, post a comment on it instead.

What browsers are you seeing the problem on?
Other - list in description
Description
(This does not pertain to a web browser)
I RDP into a Windows 11 running in a KVM (qemu) on Ubuntu 22.04.
On the Ubuntu host I'm using xfreerdp version 2.6.1 (2.6.1) for the RDP session into Windows 11.
On the Ubuntu host I start xfreerdp with the drive redirection switch:
xfreerdp \
  --many-cli-options.... \
  /drive:Home,/home/user \
  /drive:Root,/ \
  win11box.local:3389

Once logged into Windows 11, the "Files" application does list 'tsclient' under Network, but when clicked on a pop-up error:
Network folder error
Attempt to access invalid address.
On the Windows 11 original File Explorer, under "This PC" there is a section called "Redirected drives and folders". Yet there are my redirects from the /drive:Home,/home/user /drive:Root,/ command line switch.
These do not show up in the "Files" app.
Current Workarounds:
1) Manually enter into address bar:  \\tsclient\Home
2) set 'Files' as default & create desktop shortcut to \\tsclient\Home, double click on shortcut.

Only then can I view my drive redirections in the Files application.
Is it possible to list any/all file/drive redirection in the GUI? Instead of having to type in to navigate to them manually?
Steps To Reproduce
Log into Windows 11 KVM instance.
Launch File Explorer
Click "This PC" on navigation pane
View "Home" & "Root" folders in viewing pane
Launch "Files" <IP_ADDRESS> application.
Expand Network drives in navigation pane
Click on 'Network' in Navigation Pane
Double click on 'tsclient' in viewing pane
Expected behavior
Unable to click "tsclient" to be able to see redirected/shared files using the RDP client.
Yes with Windows File Explorer
No with Files <IP_ADDRESS>
Must manually type into the "Files" app address bar:
\\tsclient\Home or
\\tsclient\Root

to view shares.
Relevant Assets
Files showing 'tsclient' folder...

Error when opening (double clicking on) 'tsclient'

In Windows 11 File Explorer, I can see my two redirected drives under "This PC" and able to double click to enter.

This is the repo for the website, not the app. Please open the issue again in https://github.com/files-community/files.


Features Disappear when saving in Firefox on OS/X

In OS/X 10.10.3 and Firefox 38.0.5, having created and then saved features, the new features disappear from the edit view. If I log out and back in the features are still present and have been saved correctly.

Yes, unfortunately the data fetched from the server immediately after a save may not contain your edits.  A refresh within a few seconds will solve the issue.
see also #2667-comment and #1646
Not sure what to do about this yet, but it's something we are aware of, and seems to be a problem that is affecting a bunch of users recently.  (It happened to me today too).
As stupid as it sounds - adding a few seconds delay after changeset is accepted might be the easiest way to fix this for now.  Processing diff upload is doable but scary.  We'd basically need to copy the diffed things out of the graph into another place, context.flush, and then rebase them back in.  It's a bit like refreshing from localStorage I guess.

Closing this, as 9311ee6 adds a brief pause which should fix this in almost all cases.  It still would be better to process diff upload eventually, so leaving #1646 open.


⚠ Bofrost.at has degraded performance

In 1318ec6, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1404 ms

Resolved: Bofrost.at performance has improved in 752c49e.


jruby 9.4 broken due to IRB failure

JRuby can't be updated to <IP_ADDRESS> until the issues with reline are resolved. See ruby/reline#476 and ruby/reline#477 for more context on the exact issue.

As an update, the problems with the win32api require have been resolved, however other issues remain with getting IRB working properly in JRuby 9.4 versions.

This has been fully resolved by using the following IRB configuration settings:
IRB.conf[:USE_AUTOCOMPLETE] = false
IRB.conf[:USE_MULTILINE] = false


Reverse proxy URLs not handling correctly

Since I like to minimize the amount of ports I have open on my server, I use reverse proxy for everything I access (domain.com/deluge). Unless I am doing something wrong here, I cannot connect when not using a port number. I'm sure if I opened the port and used that instead it would work fine, but just wondering if this type of functionality is possible.

I'm also using a reverse proxy for this.  Instead of using the deluge port, it should work if you use the port number that your proxy is configured to listen on.

I have opened the proxy port, just in case that may have been causing issues and set it up the way you have described as well. Here is my current setup using Nginx, and here is how I set it up in the extension options. I can access it normally by going to https://domain.com/deluge with my current setup, but I'm not for sure if the extension requires a port number to be passed through it. I currently use delugesiphon, which just requires a raw URL to be passed through it, instead of individual fields for a port and handle.

If you're using https, then Nginx is probably configured to listen on 443.  Try using port 443 in the extension options.

Seems like that solved the issue for me! Was not aware it would need the https selection on top of the 443 port. Thanks for the help!


handle unidirectional connections under grouping

          Open an issue for handling of unidirectional connections under grouping

Originally posted by @zivnevo in https://github.com/np-guard/vpc-network-config-analyzer/pull/96#discussion_r1259439551

Done


When on click results does not disappear

Whenever you search a result and click that result, the list query component does not go away. If you don't click any other input, it wont go away.  Is there any solution to this?
An example of the behavior:

Im using RN 0.33.0
RN autocomplete 2.0.0-rc.0

@DiegoGallegos4 are you running on Android or iOS?

on IOS. Ill test this week on Android.

@l-urence  I experience the same issue on Android... selection populates textbox but does not close the selection list.

It's not working for me on Android. When I click, it changes the textfield with the content I clicked, but it's not hidding the list.

The problem is:
data={films.length === 1 && comp(query, films[0].title) ? [] : films}
Because if the title of the film is a part of the title of another film then films.length != 1.
For example, I'm using the Autocomplete component to load a list of cities, and when I click on "Paris", it changes the query to "Paris". The problem is that there are cities called Villeparisis or Parisot.
I wrote a solution with a "clicked" variable in the state:
this.state = {             query: '',             films: [],             clicked : false  };
Autocomplete data attribute is:
 data={((films.length === 1 && comp(query, films[0])) || this.state.clicked) ? [] : films}
OnChangeText attribute is:
onChangeText={function(text) {       self.setState({ query: text });       self.setState({ clicked: false }); }}
and finally:
<TouchableOpacity onPress={function() {       self.setState({query: data});       self.setState({clicked: true}); }}>       <Text>{data}</Text> </TouchableOpacity>

@qlerebours thx for charing your approach! Yes, the code from the example is just a simple illustration how the autocomplete could be used.
It's up to the application to open and close the suggestion list by passing a list with items or an empty list. This is because the filtering is hard to generalise for every application and most times done server side. (just for clarification)

@l-urence you're totally right and i'd like to thank you for you great job !
I hope my answer will be able to help @DiegoGallegos4

@qlerebours Works like a charm mate!


WIP: feat(open-authoring): add single_branch_per_collection

Summary
This add support for using single branch per collection in open-authoring flows, vs. a branch per entry which is the default. The idea is that for open-authoring flows a public user would make a number of changes all together and they can be reviewed all at once in a single PR.
Test plan
yarn test:e2e

Closing this per my comment. We can continue the discussion in #1025

Sound good - thanks @erezrokah


Decide between SASS and SCSS

Quasar Framework typically uses SASS, while the template started with SCSS. Research both and determine which one will best suit our needs.

We will be using SCSS for now. Even though Quasar defaults to using SASS, VS Code doesn't play too nice with the linting for SASS compared to SCSS. Quasar also supports SCSS automatically, so it should be okay!


The configuration file settings.yaml wasn't found.

The test is now full with this output. That's confusing.

Even with a simle application, without the settings.yaml, it will be the case. I'll fix that.


Tensorflow and Pytorch Versions used

Hello Nik!
Thanks for sharing your interesting projekt with the world!
Would you be so kind to tell me the versions of tf and torch that you use in your enviroment?
I can't make it run.
thanks in advance and best wishes :)

The torch version I don't believe I have finished. Just attempt to run the tensorflow one with numpy and Pillow. Can you describe your error?


[Issue]: excessive use of chown

Problem Description
I can't build ROCm iin cause of excessive use of chown on the very start of the process. It's hard figure out, why all directories above the top-level project directory (~/devel/amd/rocm-6.1.2/ in my case) have to alter ownership. This fails due to remote mountpoints in ~ and the build-process stops with error, not providing  any log-files.
Operating System
Debian GNU/Linux 12 (bookworm)
CPU
AMD Ryzen 5 5600G with Radeon Graphics
GPU
AMD Radeon Pro W6800
ROCm Version
ROCm 6.1.0
ROCm Component
No response
Steps to Reproduce
No response
(Optional for Linux users) Output of /opt/rocm/bin/rocminfo --support
ROCk module is loaded
KFD does not support xnack mode query.
ROCr must assume xnack is disabled.
HSA System Attributes
Runtime Version:         1.1
System Timestamp Freq.:  1000.000000MHz
Sig. Max Wait Duration:<PHONE_NUMBER>3709551615 (0xFFFFFFFFFFFFFFFF) (timestamp count)
Machine Model:           LARGE
System Endianness:       LITTLE
==========
HSA Agents

Agent 1

Name:                    AMD Ryzen 5 5600G with Radeon Graphics
Uuid:                    CPU-XX
Marketing Name:          AMD Ryzen 5 5600G with Radeon Graphics
Vendor Name:             CPU
Feature:                 None specified
Profile:                 FULL_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        0(0x0)
Queue Min Size:          0(0x0)
Queue Max Size:          0(0x0)
Queue Type:              MULTI
Node:                    0
Device Type:             CPU
Cache Info:
L1:                      32768(0x8000) KB
Chip ID:                 0(0x0)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   3900
BDFID:                   0
Internal Node ID:        0
Compute Unit:            12
SIMDs per CU:            0
Shader Engines:          0
Shader Arrs. per Eng.:   0
WatchPts on Addr. Ranges:1
Features:                None
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: FINE GRAINED
Size:                    24386052(0x1741a04) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
Pool 2
Segment:                 GLOBAL; FLAGS: KERNARG, FINE GRAINED
Size:                    24386052(0x1741a04) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
Pool 3
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    24386052(0x1741a04) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       TRUE
ISA Info:

Agent 2

Name:                    gfx803
Uuid:                    GPU-XX
Marketing Name:          AMD Radeon Pro WX 5100 Graphics
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          64(0x40)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    1
Device Type:             GPU
Cache Info:
L1:                      16(0x10) KB
Chip ID:                 26567(0x67c7)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   1086
BDFID:                   256
Internal Node ID:        1
Compute Unit:            28
SIMDs per CU:            4
Shader Engines:          4
Shader Arrs. per Eng.:   1
WatchPts on Addr. Ranges:4
Features:                KERNEL_DISPATCH
Fast F16 Operation:      TRUE
Wavefront Size:          64(0x40)
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Max Waves Per CU:        40(0x28)
Max Work-item Per CU:    2560(0xa00)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
Max fbarriers/Workgrp:   32
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    8388608(0x800000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 2
Segment:                 GROUP
Size:                    64(0x40) KB
Allocatable:             FALSE
Alloc Granule:           0KB
Alloc Alignment:         0KB
Accessible by all:       FALSE
ISA Info:
ISA 1
Name:                    amdgcn-amd-amdhsa--gfx803
Machine Models:          HSA_MACHINE_MODEL_LARGE
Profiles:                HSA_PROFILE_BASE
Default Rounding Mode:   NEAR
Default Rounding Mode:   NEAR
Fast f16:                TRUE
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
FBarrier Max Size:       32

Agent 3

Name:                    gfx90c
Uuid:                    GPU-XX
Marketing Name:          AMD Radeon Graphics
Vendor Name:             AMD
Feature:                 KERNEL_DISPATCH
Profile:                 BASE_PROFILE
Float Round Mode:        NEAR
Max Queue Number:        128(0x80)
Queue Min Size:          64(0x40)
Queue Max Size:          131072(0x20000)
Queue Type:              MULTI
Node:                    2
Device Type:             GPU
Cache Info:
L1:                      16(0x10) KB
L2:                      1024(0x400) KB
Chip ID:                 5688(0x1638)
Cacheline Size:          64(0x40)
Max Clock Freq. (MHz):   1900
BDFID:                   1792
Internal Node ID:        2
Compute Unit:            7
SIMDs per CU:            4
Shader Engines:          1
Shader Arrs. per Eng.:   1
WatchPts on Addr. Ranges:4
Features:                KERNEL_DISPATCH
Fast F16 Operation:      TRUE
Wavefront Size:          64(0x40)
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Max Waves Per CU:        40(0x28)
Max Work-item Per CU:    2560(0xa00)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
Max fbarriers/Workgrp:   32
Pool Info:
Pool 1
Segment:                 GLOBAL; FLAGS: COARSE GRAINED
Size:                    8388608(0x800000) KB
Allocatable:             TRUE
Alloc Granule:           4KB
Alloc Alignment:         4KB
Accessible by all:       FALSE
Pool 2
Segment:                 GROUP
Size:                    64(0x40) KB
Allocatable:             FALSE
Alloc Granule:           0KB
Alloc Alignment:         0KB
Accessible by all:       FALSE
ISA Info:
ISA 1
Name:                    amdgcn-amd-amdhsa--gfx90c:xnack-
Machine Models:          HSA_MACHINE_MODEL_LARGE
Profiles:                HSA_PROFILE_BASE
Default Rounding Mode:   NEAR
Default Rounding Mode:   NEAR
Fast f16:                TRUE
Workgroup Max Size:      1024(0x400)
Workgroup Max Size per Dimension:
x                        1024(0x400)
y                        1024(0x400)
z                        1024(0x400)
Grid Max Size:<PHONE_NUMBER>(0xffffffff)
Grid Max Size per Dimension:
x<PHONE_NUMBER>(0xffffffff)
y<PHONE_NUMBER>(0xffffffff)
z<PHONE_NUMBER>(0xffffffff)
FBarrier Max Size:       32
*** Done ***
Additional Information
No response

@jdumke Please provide us the steps you are following to build ROCm so that we can try to reproduce the issue. Thanks!

Hi @jdumke,
Could you please provide us with the detailed build commands you are following, as well as the error message that you are facing. Thanks!

Hi,
I'm truly soory I don't replied earlier, hence of working-issues I hat to pause my ROCm-ambitions.
The troublemaker is a permanently mounted clouddrive in my home-directory, which can't be modified by chown, which exited with errorstate, which causes make to fail..
Featured is this by line 225 of ROCm.mk: sudo chown -R "$(shell id -u):$(shell id -g)" "/home/$(shell id -un)"
Commenting out this line cleared the problem proper.
I don't understand the sense of possessing a directory-tree which is in regular owned by my user.
Greetings,
@jdumke

Hi @jdumke,
I'm glad to hear that the issue has been resolved. Although the directory is typically owned by the user, I believe that line was added as a safeguard to ensure permissions for the home directory. Thanks!


Inspector doesn't show the real property values

Godot 3.1.1 Stable Win64
Windows 10 Pro 10.0.17763 compilación 17763
Issue description:
Inspector not updating the values of the instances that were changed on its original scene.
Steps to reproduce:
Import the example proyect I provided, that is the same used as example in the Step by Step tutorial on the Godot docs: http://docs.godotengine.org/en/latest/getting_started/step_by_step/instancing.html
Add one instance of the "ball.tscn" as a child of the "Main" node.
Now open the ball scene editor and change the "Scale Gravity" value on the inspector from 4 to -4.
Go back to the Main.tscn to see that the inspector still shows the original value (4) and not the new one. F5 to reproduce and see that the changes are affecting the ball instance, because it goes up instead of down, but inspector still shows "4" on "Gravity Scale".
Sorry if I am missing something because I have so much to learn but this wasn't the behaviour I expected.
instancing.zip

Everything seems work with 3.1.1 and 3.2

Maybe you changed value in instanced scene?
If yes, then this value become local and changing base value doesn't change it.

Everything seems work with 3.1.1 and 3.2

Maybe you changed value in instanced scene?
If yes, then this value become local and changing base value doesn't change it.

Thank you for your answer. It's strange, I think that I am doing exactly the same but the result is different.

It not works because you don't save Ball scene.

Ohh I see, thank you very much. I thought I was doing the same but I guess you used a shortcut to save the ball scene. I close the issue.


chore: Added ternary to  aws_iam_role.access[0].arn #47

Description
Added a ternary on create_access_iam_role on lookups for service_access_role_arn in aws_dms_endpoint.this.kinesis settings, secrets_manager_access_role_arn and service_access_role in aws_dms_endpoint.this. I did not add the ternary to the elasticsearch block as the role is required in that context. However, using an already defined role will likely cause a failure here for the same reason, but I did not test this scenario as I am not using elasticsearch with DMS.
Motivation and Context
Implementations of the module where roles have already been provisioned for access and are passed to the necessary objects resulted in a failure when create_access_iam_role = false due to  aws_iam_role.access[0].arn is an empty tuple.
https://github.com/terraform-aws-modules/terraform-aws-dms/issues/47

Breaking Changes
This should not introduce any breaking changes.

How Has This Been Tested?

[x] I have deployed this change against my existing DMS implementation after updating to 2.0.0
No changes. Your infrastructure matches the configuration.

[x] I have executed pre-commit run -a on my pull request

Thanks for fixing this, this issue has been blocking upgrading the module reference in existing deployments. Any chance for someone to review this PR?

@bryantbiggs Let me know if you need anything to merge this PR, thanks!


Pion emissivity from pp interaction

I have been battling with the formula for a bit, and I think there's a problem with $E_\pi \to E_p K_\pi$ substitution that's seemingly going on here. First of all, it holds only in $\delta$-approximation that we are abandoning at this point. Second, it leaves us with $q_\pi$ somehow expressed in terms of $E_p$ which doesn't really make sense. Third, later when this formula is used to compute $q_\gamma$, the energy in the numerator seems to be taken as $E_\pi$.
Unrelated to this, but I have a question regarding this section: what happens to $\sigma_{pp}$? It seems as if it's replaced by some constant value $\sigma_pp(E_p) \approx \sigma_0$, but this is not explicitly addressed, and it's not obvious if it can be done with generally growing (even if slowly) function.

Regarding my second questions, seems like $\sigma_0$ is a high-energy limit of $\sigma_{pp \to \pi_0 X}$ with a numerical value $\approx 140~\text{mbarn}$.


bigquery-snowflake.sql

Adding the SQL worksheet for setting up Iceberg between BigQuery and Snowflake with  BigQuery Write (BLMT) and Snowflake Read

Done. I suggest renaming "snowflake-iceberg.sql" to "snowflake-bigquery-iceberg.sql" this way we can differentiate the two scripts?


Misleading information on security issues with query parameters

I think the mentioned security issue regarding the use of query parameters is slightly misleading:
https://github.com/GroupePSA/api-standards/blob/master/api-style-guide.md#query-parameters

Be careful when using sensitive/private query parameters as the URI is not encrypted over HTTPS

This is not quite correct. Using TLS, usually only the hostname and the port are unencrypted, thus visible easily. The (context) path as well as the query parameters are TLS encrypted indeed.
It could be mentioned, however, that full URLs and query parameters are usually included in logfiles, so the recommendation to be careful with sensitive/private parameters is still valid.

@ronau : Many thanks for you feedback. This item needs an improvement.
@adrienlauer : Have you an idea to be more precise about that ?

@ronau: The proposed change is in the PR #13. Let me know what you think if you can but I think it fixes the issue.

We can go ahead with that 👍 , exchange can continue.

I agree. Looks good now. 👍