Updates release notes for 2.1.0 release.

:cactus:

I'd rename releasenotes/riak-2.0.5.md to releasenotes/riak-2.0.md to match the format that we're apparently using in that directory.


Unable to install due to bibtexparser

Hi, I wanted to try your app but am unable to install via conda, I tried python 3.11 and 3.8 more info below
AttributeError: module 'bibtexparser' has no attribute 'bparser'
conda version : 23.5.2
conda-build version : 3.25.0
python versions : 3.11.3, 3.8.18
```

Thanks for the issue. It seems to be to the new beta version of bibtexparser, which has a new api. The updated install.sh script should handle installing the correct dependencies for you.
I've been using this repo daily lately, since I'm finishing up my phd thesis -- it's working really well, except there is one issue where refman doesn't detect if you create two entries with the same bibtex key. So, just be wary of if you're citing two papers from the same author (or different authors with the same surname) from the same year. You can use the refman medit and refman rm to fix such issues.
I'll fix this eventually, but, I'm kinda busy with the thesis 😅
Let me know how it goes.

Thanks, now it works.
Good luck with the thesis! :)


/* is parsed as a block comment but should be invalid

Issue Kind
Other
Source Code
func test() {} /*/

Description
The source above parses fine and /*/ is parsed as a block comment. The lexer shouldn’t stop the block comment after the second /.

rdar://107424615


Invalid Binary Target for OpenSSL V3 on CentOS Stream 9

Bug description
Prisma CLI fails to initialize when deploying a new or existing project to a CentOS Stream 9 server. The error references an unknown binary target for openssl 3.0.x.
# npx prisma init
  prisma:engines binaries to download libquery-engine, migration-engine, introspection-engine, prisma-fmt +0ms
  prisma:download file<EMAIL_ADDRESS>does not exist and must be downloaded +0ms
Error: Error: Unknown binaryTarget rhel-openssl-3.0.x and no custom binaries were provided
    at /root/hello-prisma/node_modules/@prisma/engines/dist/index.js:21277:15
    at async Promise.all (index 0)
    at async /root/hello-prisma/node_modules/@prisma/engines/dist/index.js:6621:29

The same error is received when trying to initialize the new project directory or generating artifacts (prisma client) from an existing project.
OpenSSL v3.0.1 is confirmed to be installed.
# openssl version
OpenSSL 3.0.1 14 Dec 2021 (Library: OpenSSL 3.0.1 14 Dec 2021)
# cat /etc/redhat-release
CentOS Stream release 9

Running npx prisma completes successfully and shows help output.
How to reproduce

Start with an updated CentOS Stream 9 server with Node installed.
Create a new project. mkdir hello-prisma
Enter the directory. cd hello-prisma
Initialize the project. npm init -y
Install prisma. npm install prisma --save-dev
Test prisma to make sure it is working. npx prisma
Initialize prisma. npx prisma init
The error is now received.

Expected behavior
Prisma CLI should work as expected correctly generate the project files.
Prisma information
N/A as the error prevents a project from getting this far.
Environment & setup

OS: CentOS Stream 9
Database: MySQL
Node.js version: v16.10.0

Prisma Version
Prisma version flag fails to complete. I can confirm prisma was installed from NPM as detailed in the quickstart.
# npx prisma -v
  prisma:engines binaries to download libquery-engine, migration-engine, introspection-engine, prisma-fmt +0ms
  prisma:download file<EMAIL_ADDRESS>does not exist and must be downloaded +0ms
Error: Error: Unknown binaryTarget rhel-openssl-3.0.x and no custom binaries were provided
    at /root/hello-prisma/node_modules/@prisma/engines/dist/index.js:21277:15
    at async Promise.all (index 0)
    at async /root/hello-prisma/node_modules/@prisma/engines/dist/index.js:6621:29

I have the issue for debian
Error: Unknown binaryTarget debian-openssl-3.0.x and no custom binaries were provided

Is there a method to force prisma to use a different version ?
I did something not really clean to force prisma to think I have opensssl 1.1.1 and it works for now so it might be a workaround in the meantime.

Note: We changed this to a feature because although it looks like a bug, we don't publish binaries for openssl 3.0 yet because we still need to add support for it.

The feature request to support OpenSSL 3 is here: https://github.com/prisma/prisma/issues/11356 From a user perspective, Prisma not working in their environment is a defect that we track as a bug. When the feature request is resolved, we can also resolve the bug issue tracking the defect.

If somebody would like to build binaries for themeselves instead of waiting, just clone https://github.com/prisma/prisma-engines, run cargo build --release (pkg-config lib required in addition to rust toolcahin, at least in case of Ubuntu 22.04, not sure about others) and set those envs:
export PRISMA_QUERY_ENGINE_LIBRARY=/home/cdfn/dev/prisma-engines/target/release/libquery_engine.so
export PRISMA_QUERY_ENGINE_BINARY=/home/cdfn/dev/prisma-engines/target/release/query-engine
export PRISMA_MIGRATION_ENGINE_BINARY=/home/cdfn/dev/prisma-engines/target/release/migration-engine
export PRISMA_INTROSPECTION_ENGINE_BINARY=/home/cdfn/dev/prisma-engines/target/release/introspection-engine
export PRISMA_FMT_BINARY=/home/cdfn/dev/prisma-engines/target/release/prisma-fmt
export PRISMA_CLI_QUERY_ENGINE_TYPE=binary # you may not need this, I had weird error with lib not being able to load
export PRISMA_QUERY_ENGINE_TYPE=binary # you may not need this, I had weird error with lib not being able to load

Additionaly, you need to add in your schema.prisma:
 generator client {
    provider      = "prisma-client-js"
+   binaryTargets = ["darwin"]
 }

For me this setup works perfectly well.

wtf !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! f*  prisma developers

Today Ubuntu 22.04 dropped. It uses OpenSSL V3 by default. Is there any progress on this or we're forced to downgrade?

This is fixed and will ship with 3.13.0:
https://github.com/prisma/prisma/issues/11356#issuecomment-1103977740
That version will be release next Tuesday, and this comment includes instructions how you can temporarily use the development version of Prisma to confirm it works: https://github.com/prisma/prisma/issues/11356#issuecomment-1106208683


Rework the REST API and increase the cardinality of the back-end from one to many.

The / route should just present HTML help with demo links to do all the rest.

Done. Please see the new /?use, /?drop, and /People/?use.
These newly revised REST APIs allow creating/droping/using other tables. Linked-in examples are for tables People and Places. The Master table can also be dropped and recreated. All table-oriented commands such as for insert, update, delete, stats, list, etc are targeting the table that is currently in use with the /?use command.


Refactor Spanish

Closes #138

Coverage decreased (-0.1%) to 99.406% when pulling 620200cbb96060f8e7bae19085461ade32b3c633 on jlduran:refactor-spanish into 7f92a9f5152c1608ed082d5f7f24d19cadb5039d on kslazarev:master.

Beautiful work @jlduran! Merged.


Refine the intro parts of the package documentation

Extract the package documentation from hangulize.go to doc.go. It is an officially recommended convention for packages with long documentation.
Rewrite the intro parts of the package documentation. (before Spec section)
Use one space between sentences, rather than two. Two spaces are a kind of legacy and unnatural. I did a short check, and it appears that most packages including godoc itself using single space to separate sentences.

I merged it into develop instead.  Thank you for the great work.


Added David's advice

Added David's advice

Thanks so much for your contribution to Tiny Troves of Dev Wisdom. 😄
The current game build  will be updated frequently throughout Hacktoberfest 2023 so check back often to see new contributions!


CMP-2614: Implement update timestamps on ComplianceCheckResults

Adding the lastscanned timestamp annotation in each complianceCheckResult, added annotation compliance.openshift.io/last-scanned-timestamp with a value equal to scan.status.StartTimestamp
example of CCR
kind: ComplianceCheckResult
metadata:
  annotations:
    compliance.openshift.io/last-scanned-timestamp: "2024-08-15T04:26:11Z"
    compliance.openshift.io/rule: scc-limit-root-containers
  creationTimestamp: "2024-08-15T04:26:43Z"
  generation: 1
  labels:
    compliance.openshift.io/check-severity: medium
    compliance.openshift.io/check-status: MANUAL
    compliance.openshift.io/profile-guid: a230315d-3e4a-5b58-b00f-f96f1553e036
    compliance.openshift.io/scan-name: ocp4-cis
    compliance.openshift.io/suite: ocp4-cis-ssb
  name: ocp4-cis-scc-limit-root-containers
  namespace: openshift-compliance

[vincent@node compliance-operator]$ oc get scan ocp4-cis -o yaml
apiVersion: compliance.openshift.io/v1alpha1
kind: ComplianceScan
metadata:
  creationTimestamp: "2024-08-15T04:26:10Z"
  finalizers:
  - scan.finalizers.compliance.openshift.io
  generation: 1
  labels:
    compliance.openshift.io/profile-guid: a230315d-3e4a-5b58-b00f-f96f1553e036
    compliance.openshift.io/suite: ocp4-cis-ssb
  name: ocp4-cis
  namespace: openshift-compliance
  ownerReferences:
  - apiVersion: compliance.openshift.io/v1alpha1
    blockOwnerDeletion: true
    controller: true
    kind: ComplianceSuite
    name: ocp4-cis-ssb
    uid: b80577a9-de77-4b7f-af6c-cfb7eee7e36f
  resourceVersion: "5290391"
  uid: 7abb45d7-1a61-491a-bbc1-306406d75e04
spec:
  content: ssg-ocp4-ds.xml
  contentImage: ghcr.io/complianceascode/k8scontent:latest
  maxRetryOnTimeout: 3
  profile: xccdf_org.ssgproject.content_profile_cis
  rawResultStorage:
    nodeSelector:
      node-role.kubernetes.io/master: ""
    pvAccessModes:
    - ReadWriteOnce
    rotation: 3
    size: 1Gi
    tolerations:
    - effect: NoSchedule
      key: node-role.kubernetes.io/master
      operator: Exists
    - effect: NoExecute
      key: node.kubernetes.io/not-ready
      operator: Exists
      tolerationSeconds: 300
    - effect: NoExecute
      key: node.kubernetes.io/unreachable
      operator: Exists
      tolerationSeconds: 300
    - effect: NoSchedule
      key: node.kubernetes.io/memory-pressure
      operator: Exists
  scanTolerations:
  - operator: Exists
  scanType: Platform
  showNotApplicable: false
  strictNodeScan: true
  timeout: 30m
status:
  conditions:
  - lastTransitionTime: "2024-08-15T04:26:14Z"
    message: Compliance scan run is running the scans
    reason: Running
    status: "True"
    type: Processing
  - lastTransitionTime: "2024-08-15T04:26:11Z"
    message: Compliance scan doesn't have results yet
    reason: Processing
    status: "False"
    type: Ready
  phase: AGGREGATING
  remainingRetries: 3
  result: NOT-AVAILABLE
  resultsStorage:
    name: ocp4-cis
    namespace: openshift-compliance
  startTimestamp: "2024-08-15T04:26:11Z"

 vet: cmd/manager/aggregator.go:346:6: no new variables on left side of :=
make: *** [Makefile:308: vet] Error 1

verification pass with CATALOG_IMG=ghcr.io/complianceascode/compliance-operator-catalog:591-2ea830149c4ab084010d8c5544a0ac54dca8542c:
% oc get scan
NAME                    PHASE   RESULT
ocp4-stig               DONE    NON-COMPLIANT
ocp4-stig-node-master   DONE    NON-COMPLIANT
ocp4-stig-node-worker   DONE    NON-COMPLIANT
rhcos4-stig-master      DONE    NON-COMPLIANT
rhcos4-stig-worker      DONE    NON-COMPLIANT
% oc get scan -o=jsonpath="{.items[*].status.startTimestamp}"
2024-08-15T08:03:25Z 2024-08-15T08:03:24Z 2024-08-15T08:03:25Z 2024-08-15T08:03:25Z 2024-08-15T08:03:23Z%
% oc get ccr ocp4-stig-accounts-restrict-service-account-tokens -o=jsonpath={.metadata.annotations}| jq -r
{
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-15T08:03:25Z",
  "compliance.openshift.io/rule": "accounts-restrict-service-account-tokens"
}
% oc get ccr -o=jsonpath="{.items[*].metadata.annotations}" | jq -r | grep last-scanned-timestamp | head -n 5
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-15T08:03:25Z",
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-15T08:03:25Z",
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-15T08:03:25Z",
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-15T08:03:25Z",
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-15T08:03:25Z",
% oc get ccr -o=jsonpath="{.items[*].metadata.annotations}" | jq -r | grep last-scanned-timestamp | wc -l
     512
% oc get ccr --no-headers | wc -l
 % oc annotate compliancescan/ocp4-stig compliance.openshift.io/rescan=
compliancescan.compliance.openshift.io/ocp4-stig annotated
 % oc get scan -w
NAME                    PHASE     RESULT
ocp4-stig               RUNNING   NOT-AVAILABLE
ocp4-stig-node-master   DONE      NON-COMPLIANT
ocp4-stig-node-worker   DONE      NON-COMPLIANT
rhcos4-stig-master      DONE      NON-COMPLIANT
rhcos4-stig-worker      DONE      NON-COMPLIANT
ocp4-stig               AGGREGATING   NOT-AVAILABLE
ocp4-stig               DONE          NON-COMPLIANT
^C%                                                                                % oc get scan -o=jsonpath="{.items[*].status.startTimestamp}"
2024-08-15T08:22:39Z 2024-08-15T08:03:24Z 2024-08-15T08:03:25Z 2024-08-15T08:03:25Z 2024-08-15T08:03:23Z%
% oc get ccr ocp4-stig-accounts-restrict-service-account-tokens -o=jsonpath={.metadata.annotations}| jq -r
{
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-15T08:22:39Z",
  "compliance.openshift.io/rule": "accounts-restrict-service-account-tokens"
}

/unhold

@Vincent056 I can still see the last-scanned-timestamp is the same with scan's startTimestamp with index image ghcr.io/complianceascode/compliance-operator-catalog:591-cd850a508d36f939c8eb8cf84c1043577b94cc5f. Is it expected? Thanks.
% oc get scan
NAME                    PHASE   RESULT
ocp4-stig               DONE    NON-COMPLIANT
ocp4-stig-node-master   DONE    NON-COMPLIANT
ocp4-stig-node-worker   DONE    NON-COMPLIANT
rhcos4-stig-master      DONE    NON-COMPLIANT
rhcos4-stig-worker      DONE    NON-COMPLIANT
 % oc get scan -o=jsonpath="{.items[*].status.startTimestamp}"
2024-08-26T10:11:23Z 2024-08-26T10:11:27Z 2024-08-26T10:11:27Z 2024-08-26T10:11:23Z 2024-08-26T10:11:23Z%                                                                                % oc get ccr -o=jsonpath="{.items[*].metadata.annotations}" | jq -r | grep last-scanned-timestamp | head -n 5
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-26T10:11:23Z",
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-26T10:11:23Z",
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-26T10:11:23Z",
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-26T10:11:23Z",
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-26T10:11:23Z",
% oc get ccr ocp4-stig-accounts-restrict-service-account-tokens -o=jsonpath={.metadata.annotations}| jq -r
{
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-26T10:11:23Z",
  "compliance.openshift.io/rule": "accounts-restrict-service-account-tokens"
}

/open
sorry, close it by accident.

/reopen

Verification pass with 4.17.0-0.nightly-2024-08-28-171119 + ghcr.io/complianceascode/compliance-operator-catalog:591-baf525c3eb6cc0f0d80e31a58dadddfb425a8231 index image.
BTW, the ssb will will take much less time than before(previous commint in this PR), especially at AGGREGATING phase.
% cat ~/func/ssb_cis.yaml
apiVersion: compliance.openshift.io/v1alpha1
kind: ScanSettingBinding
metadata:
  name: cis-compliance
  namespace: openshift-compliance
profiles:
  - name: ocp4-cis
    kind: Profile
    apiGroup: compliance.openshift.io/v1alpha1
  - name: ocp4-cis-node
    kind: Profile
    apiGroup: compliance.openshift.io/v1alpha1
settingsRef:
  name: default
  kind: ScanSetting
  apiGroup: compliance.openshift.io/v1alpha1
% oc apply -f ~/func/ssb_cis.yaml
scansettingbinding.compliance.openshift.io/cis-compliance created
% oc get suite -w
NAME             PHASE         RESULT
cis-compliance   AGGREGATING   NOT-AVAILABLE
cis-compliance   DONE          NON-COMPLIANT
cis-compliance   DONE          NON-COMPLIANT
^C%                                                                                % date
Thu Aug 29 20:43:59 CST 2024
% oc get ccr ocp4-cis-accounts-restrict-service-account-tokens  -o=jsonpath={.metadata.annotations}| jq -r
{
  "compliance.openshift.io/last-scanned-timestamp": "2024-08-29T12:42:57Z",
  "compliance.openshift.io/rule": "accounts-restrict-service-account-tokens"
}

/label qe-approved

Adding px-approved since we've walked through this with @mkumku.

/doc-approved

/label doc-approved

/label docs-approved

/assign GroceryBoyJr


how to update the seclists once installed on kali later when soemthings add up

use the git version and do daily or weekly git pull

apt-get update && apt-get upgrade

This is covered in the readme.
If thats not clear enough, please explain in more detail the issue.


Rules for automatic reblocking

xref #58, #60
Automatic reblocking in dask operations will be a super useful follow-on to manual reblock functionality. Here are my initial thoughts. For now, I'm going to simplify things by assuming that each array has a fixed blockshape (in practice, we could use the mean of the blockdims along each axis).

For operations where one argument has a strictly larger blockshape (e.g., (100, 100) and (1000, 1000)), we probably want to reblock to the larger blockshape to minimize growth of the scheduling graph.
For operations with differently shaped blockshapes (e.g., (100, 10000) and (10000, 100)) but comparable chunk sizes let's consider using the geometric mean of the blockshape along each dimension. This has the nice property of conserving the size of each chunk, and I suspect it would also minimize total amount of concat/slicing work necessary for the reblocking itself. For this example, this yields a blockshape of (1000, 1000).
When given arrays with block shapes (10000, 1) and (1, 10000), we probably don't want chunks of shape (100, 100) -- that's too small. So shapes calculated from the geometric mean should probably be scaled up to ensure some minimum size (e.g., one million elements, or the largest chunk size currently in the dask).

"Uncut" dimensions deserve special consideration, because they are quite likely to arise in practice, both from array broadcasting (they'll have length 1) and from coercing fresh numpy arrays. But I think they are covered reasonably well by these rules.
For example, consider multiplying arrays with shapes/blockshapes (100, 1, 1) and (1, 1000, 1000). With the geometric mean, we get about 10000 chunks of shape (10, 32, 32), which after the scaling adjustment leaves us with about 100 chunks of size (47, 147, 147).

Hmm... I'm not so sure about my geometric mean rule anymore.
Consider an operation between the full array (blockshape (4, 200, 200)) and a vector along the time-axis (blockshape (1464, 1, 1)) from @mrocklin's weather data example. My algorithm (see below) would give a chunksize of (167, 31, 31), which would result in making a huge number of rechunks of the big array -- roughly ((3 * 7) * 7 * 7) * (1464 / 4) = 376614 calls to getitem alone. In contrast, the right approach would simply be to rechunk from (1464, 1, 1) to (4, 1, 1)`, which is only 365 slice operations.
This seems like the sort of problem that might be favorably formulated as an optimization problem.
from scipy.stats import gmean

def calc_chunksize(*shapes):
    gmean_shape = gmean(shapes, axis=0)
    sizes = np.prod(shapes, axis=1)
    scale_factor = ((np.max(sizes) / np.prod(mean_shape))
                    ** (1.0 / len(shapes[0])))
    return tuple(np.around(gmean_shape * scale_factor).astype(int))

Per offline discussion with @mrocklin, we may get a pretty decent solution simply by using the existing blockshapes from the larger of the supplied arrays, or if all arrays have the same size, whichever array has the largest chunk size.
For dask + ndarray operations, in most cases we can simply use chunk dimensions from the dask array.
Cases that use broadcasting to create new dimensions (e.g., multiplying arrays of size (100, 1, 1) and (1, 1000, 1000)) will require different logic -- possibly something like my geometric mean solution.

How much is this is covered by https://github.com/dask/dask/pull/3507?

I think that rechunking will have to be done on a per-operation basis.  The rules for tensordot will be different from the rules for fft.
This is discussed in https://github.com/dask/dask/issues/3587 .  Closing in favor of that issue.


Can not get the UpdateFailed status

I installed BTPSO in my cluster, and created a hana cloud instance via BTPSO, then I tried to update it with an invalid parameter（set memory to 35）, I expected to get a status like UpdateFailed, but it is always in UpdateInProgress status. I don't think it is a expected behavior, can somebody help to take a look?
ko8 get serviceinstances
NAME      OFFERING         PLAN   SHARED   DATACENTER   STATUS             READY   AGE
myhana1   hana-cloud-***   hana                         UpdateInProgress   True    80m

The serviceinstance CR can show an obvious error from service broker Status/Conditions/Message, but the status is always UpdateInProgress (unexpected).
Status:
  Conditions:
    Last Transition Time:  2023-07-26T09:35:52Z
    Message:               request PATCH https://service-manager.cfapps.****.hana.ondemand.com/v1/service_instances/********-****-****-****-************ failed: StatusCode: 502 Body: {"error":"BrokerError","description":"Failed update instance request context: map[clusterid:********-****-****-****-************ global_account_id:********-****-****-****-************ instance_name:myhana1 license_type:SAPDEV namespace:default origin:kubernetes platform:sapcp region:cf-**** service_instance_id:********-****-****-****-************ signature:**********C3YnUFoiHkZFLxtEVvdo5jTtmFLnoLZS/adlAFytBjiQqg+yciRNnPdJYcEUms7bwSvp6wuDswOVyGMG8eFEKt3WDARuJtqjAKz4rwBBPVXLilysHWvqiifcClAQZO0uPTC693NLGHvvFhQJvxAj2WchwaWwvfcRtwpOHbfJmPRM2/Mike8t3tRFHi5etJDsRdUDCfAmByYW1FbxNZqmbls/2W2Me0w3H+m1LdAAd3fY9Jrr00vG/2wrvnMB4S8KX/Fb68FC7h5DuwNgufLkoXbdZdk1nJAmlLN82sOhTFXdG3xnE1MHzRn7BuweB0VarVc0CTfVvxukrSdpMb2wlhWG3S0UVJ78i8qa2Cqnw6b0NW83CahbTVbbhQVSMwy1zVtmqcZICPNZbn/nalATb653zrURIdp7GqmBpO1O7WM2Ml8p5s/yjjpIKsYADpcBAKkPL3P+BDc57pNx5nJGsbdSWN1zZ9Ez3ccrj8d2AeE3NluKi18sbhcmjK4a2SpDLdgyjdfL1WVJYYEV5rq0K5WBBYDv0IE91WoNUtL+b9BDib8SZ/XU/RPDc09Z+/+wvvkXmfveKEilb82TxaY4XORk+UG2vcK4es71yCA38kWCfjNufAmX5MUaqECmkRsOnx4g8y2dTotoT/fmkdKbDF8**********= subaccount_id:********-****-****-****-************ subdomain:i*******-test zone_id:********-****-****-****-************], instanceID: ********-****-****-****-************, planID: ********-****-****-****-************, serviceID: ********-****-****-****-************, acceptsIncomplete: true: Status: 422; ErrorMessage: \u003cnil\u003e; Description: invalid Parameter (memory): Memory 35 for HANA service not valid [ref **********hqIrvZiqBIDcLGlGq]; ResponseError: \u003cnil\u003e","broker_error":{"StatusCode":422,"ErrorMessage":null,"Description":"invalid Parameter (memory): Memory 35 for HANA service not valid [ref **********hqIrvZiqBIDcLGlGq]","ResponseError":null}}

    Observed Generation:   3
    Reason:                UpdateInProgress
    Status:                False
    Type:                  Succeeded
    Last Transition Time:  2023-07-26T09:00:55Z
    Message:
    Observed Generation:   3
    Reason:                Provisioned
    Status:                True
    Type:                  Ready
  Hashed Spec:             **********dd36c414a5e5ca0147d91d
  Instance ID:             ********-****-****-****-************
  Ready:                   True

Hi,
This issue is a known issue and we are just at the end of finish handling it
The reason you keep getting updateInProgress is that service-manager forward the request to the broker and gets an error - after that service-manager returns a status code 502 and the operator interprets this as a transient error (which means in other words temporary error, and keep trying to update the service instance)
This issue will be fixed in the following days.

Hello Tal, Thanks for your quick reply, I remember the known issue you mentioned, but as I recall, in the past, when this problem occurred, if the operator keeps trying to update the instance, soon it would reach the service manager api request limit: "The allowed request limit of 100 requests has been reached please try again later". But now, seems the sm api request limit is not reached, it still reports the service broker error after 30 mins.

It depends on the environment and the configuration of sm.
Any way - in the new solution a better operator rate limit is added

Hello Tal, Thanks.


Initial implementation of StatusStream

Split out setting up events from: https://github.com/remind101/empire/pull/916
Calling these "Scheduler Events" was too confusing given that we also have "Empire Events" that publish to various sources. I went with calling this a "StatusStream" that can be created and passed to an action (like Deploy) and can be published and read from throughout the lifecycle of the action.
I ended up creating a separate package status because otherwise we would have had to import the scheduler within deployments.go which felt off to me.

I ended up creating a separate package status because otherwise we would have had to import the scheduler within deployments.go which felt off to me.

remind101/empire already depends on remind101/empire/scheduler, so it would be fine to put StatusStream within remind101/empire/scheduler. I actually think that would be better until there's a reason to extract it.

This is looking great so far.

i'm fine moving within remind101/empire/scheduler. just to confirm, that is just moving remind101/empire/status/status.go to remind101/empire/scheduler/status.go or should we just include everything within remind101/empire/scheduler/scheduler.go?

I think everything in remind101/empire/scheduler/scheduler.go would be best.

ok cool

ok, i implemented the jsonmessageStatusStream as well as the other pieces of feedback.
the only part i'm not happy with is having to do: https://github.com/remind101/empire/pull/917/files#diff-48d76aef8c283046a79db32824933290R523

I just hacked together a couple changes in the CloudFormation backend to use this. So awesome seeing more context in the deployment stream:
https://asciinema.org/a/b6vnccpg2u2uykf9wyyb1ijej
This looks gtm 👍. We can make changes to Scheduler implementations to use this in a separate PR (or if you wanna just merge those changes into this branch, that's cool too).

@ejholmes i made one more change this weekend: https://github.com/remind101/empire/pull/917/commits/9843828726f53829bc56e2be0c9225aba0ddeab1
this fixes concurrent requests

Awesome 👍 (sorry for the churn :)).

@ejholmes https://github.com/remind101/empire/pull/917/commits/c6441b7c6d0cac2d1e525e9e09e71d43804068e7 is actually the commit I was talking about, I forgot I had done it in a different branch.
Without this the db transaction surrounds both the creation and the submission of the release, which breaks concurrency.

@ejholmes ok i think this is good to go. i added an -s flag so we'll only setup the status stream if someone enables it. This means people can opt in to the new UX.

Deploy now looks like:
$ ./build/emp deploy remind101/acme-inc:master -s
master: Pulling from remind101/acme-inc

420890c9e918: Already exists
a3ed95caeb02: Already exists
1e14aab0083d: Already exists
4393485f2bb3: Already exists
a2a051cf14f7: Already exists
1f9177248efa: Already exists
Digest: sha256:d05682347b56191a950f55ab06f11a6c6e34041921af32281b01f4a6a9a0f75f
Status: Image is up to date for remind101/acme-inc:master
Status: Created cloudformation template: https://empire-0b96756d-templatebucket-fzr5jqii49z4.s3.amazonaws.com/acme-inc/e904d241-a249-4b13-aa77-9dc0a3639617/57c5f02918c0fd1714d4689075924b42523c4fb6
Status: Stack update submitted
Status: Waiting for stack update to complete
Status: Stack update complete
Status: Finished processing events for release v9 of acme-inc

When a deploy has been superseded:
$ ./build/emp deploy remind101/acme-inc:master -s
master: Pulling from remind101/acme-inc

420890c9e918: Already exists
a3ed95caeb02: Already exists
1e14aab0083d: Already exists
4393485f2bb3: Already exists
a2a051cf14f7: Already exists
1f9177248efa: Already exists
Digest: sha256:d05682347b56191a950f55ab06f11a6c6e34041921af32281b01f4a6a9a0f75f
Status: Image is up to date for remind101/acme-inc:master
Status: Created cloudformation template: https://empire-0b96756d-templatebucket-fzr5jqii49z4.s3.amazonaws.com/acme-inc/86874600-74f0-4ee4-9517-51c13a3e7240/3c156706ec606aa39375c6dfd7182f2f8a1d0ee4
Status: Waiting for existing stack operation to complete
Status: Operation superseded by newer release
Status: Finished processing events for release v4 of acme-inc

While waiting for another deploy to finish:
$ ./build/emp deploy remind101/acme-inc:master -s
master: Pulling from remind101/acme-inc

420890c9e918: Already exists
a3ed95caeb02: Already exists
1e14aab0083d: Already exists
4393485f2bb3: Already exists
a2a051cf14f7: Already exists
1f9177248efa: Already exists
Digest: sha256:d05682347b56191a950f55ab06f11a6c6e34041921af32281b01f4a6a9a0f75f
Status: Image is up to date for remind101/acme-inc:master
Status: Created cloudformation template: https://empire-0b96756d-templatebucket-fzr5jqii49z4.s3.amazonaws.com/acme-inc/86874600-74f0-4ee4-9517-51c13a3e7240/d5e7525e4fb98ee49bd3aceceed7e726a9029e64
Status: Waiting for existing stack operation to complete
Status: Stack update submitted
Status: Waiting for stack update to complete
Status: Stack update complete
Status: Finished processing events for release v5 of acme-inc

Create looks like:
$ ./build/emp deploy remind101/acme-inc:master -s
master: Pulling from remind101/acme-inc

420890c9e918: Already exists
a3ed95caeb02: Already exists
1e14aab0083d: Already exists
4393485f2bb3: Already exists
a2a051cf14f7: Already exists
1f9177248efa: Already exists
Digest: sha256:d05682347b56191a950f55ab06f11a6c6e34041921af32281b01f4a6a9a0f75f
Status: Image is up to date for remind101/acme-inc:master
Status: Created cloudformation template: https://empire-0b96756d-templatebucket-fzr5jqii49z4.s3.amazonaws.com/acme-inc/04a75f65-c7c4-4e36-943b-0a09614db1b4/67f96646de01688a45cc9d8a5f25ff9cb1ce479c
Status: Creating stack
Status: Stack created
Status: Finished processing events for release v2 of acme-inc

I wanted to get the actual cloudformation url, but i didn't see that we had easy access to the stack arn.

We should also add Stream: true to https://github.com/remind101/empire/blob/0f2cc1aa401cd98e0b5f202a9c6bedb965713a84/server/github/deployer.go#L59-L63.

Couple of minor things, which we can follow up with later. This is awesome 👍.

Oh, can you update the changelog too?


Skip object checksum check on upload if server side AWS KMS encryption is used

This pull request updates S3 driver code to skip uploaded object checksum check at the end of the upload when server side AWS KMS encryption is used for that object.
In such scenario, ETag header value doesn't contain object data MD5 digest.
As part of that change I also noticed some of the tests were out of date and some of the mock http methods are not needed anymore so I did some cleanup. That likely happened during the requests migration.
Resolves #1401.

Codecov Report

Merging #1406 into trunk will increase coverage by 0.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##            trunk    #1406      +/-   ##
==========================================
+ Coverage   86.44%   86.46%   +0.01%
==========================================
  Files         366      366
  Lines       76767    76773       +6
  Branches     7529     7529
==========================================
+ Hits        66365    66378      +13
+ Misses       7534     7527       -7
  Partials     2868     2868

Impacted Files
Coverage Δ

libcloud/test/storage/test_s3.py
92.77% <100%> (+1.3%)
:arrow_up:

libcloud/storage/drivers/s3.py
89.34% <100%> (+0.06%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 435d82b...8bf5724. Read the comment docs.


Regarding the old issue...

I did all the steps in readme still having issues, idk what's happening

does it give any errors

You just need to run PySilon.bat script and you have literally a GUI for everything. After you set needed values, click Generate source and then Compile buttons (after "accepting" disclaimer). If you hav issues, then please describe them here because I don't know how can I help you without any information what are the issues about.


Update docs links on README

What kind of change does this PR introduce?
Bug fix - Update docs links on README

Legend thanks @zlwaterfield

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Remove authentication from readme

After  commit ad236285833586b4b15e101797841b59fe70858b there is no longer authentication fields to be filled in Wordpress so the following should be removed from the readme:
https://github.com/bitcartcc/bitcart-woocommerce/blob/ad236285833586b4b15e101797841b59fe70858b/readme.txt#L67

Thank you for pointing out! WIll fix it now


vNode passed as children has unexpected type. Make sure it's using the correct h() function.

When using state tunnel with stencil 1.3.3 I get  vNode passed as children has unexpected type. Make sure it's using the correct h() function. I simply just followed the guide.
This is my tunnel:
import { h } from "@stencil/core";
import { createProviderConsumer } from "@stencil/state-tunnel";

export interface CollapsibleState {
  isOpen: boolean;
  setIsOpen: (fn: (oldVal: boolean) => boolean) => void;
}

export const CollapsibleTunnel = createProviderConsumer<CollapsibleState>(
  {
    isOpen: true,
    setIsOpen: () => false
  },
  (subscribe, child) => (
    <context-provider subscribe={subscribe} renderer={child}></context-provider>
  )
);

Setting up the provider:
export class Collapsible {
  @State()
  isOpen = false;

  render() {
    return (
      <div class="cui-collapsible">
        <CollapsibleTunnel.Provider
          state={{
            isOpen: this.isOpen,
            setIsOpen: fn => {
              this.isOpen = fn(this.isOpen);
            }
          }}
        >
          <slot />
        </CollapsibleTunnel.Provider>
      </div>
    );
  }
}

Using the tunnel:
export class CollapsibleBody {
  render() {
    return (
      <CollapsibleTunnel.Consumer>
        {({ setIsOpen }) => (
          <button onClick={() => setIsOpen(o => !o)}>Toggle</button>
        )}
      </CollapsibleTunnel.Consumer>
    );
  }
}

Types are also not correctly inferred to the Consumer, setIsOpen is typed as any.

The warning message is coming from stencil core. See https://github.com/ionic-team/stencil/issues/2007

My component does not display anything though, so to me it seems to be more than just a warning.


Fractions guidance

What do you need?
Guidance on writing fractions. Andrew confirms decimals are preferable (0.5 1.5). Need to consider 2/3, 3/4 and so on.
Which entry/section is this related to?
http://content-style-guide.apps.staging.digital.gov.au/az-indexes/n.html#numbers

Libby to talk to Andrew

I'll take on to investigate screen reader issues (if any) with the various alteratives

Suggestion: We agree decimals for simple fractions eg 2.5, 0.5 etc.
AA to investigate best approach for two-thirds versus 2/3 with screen readers.

Suggestion is to use percentage (eg nn%) where ever appropriate. Response from an experienced JAWS user ...
Response in _italics_ for each point/question.

for one-half - 1/2 (one slash two) or 0.5 _JAWS states ‘one half’ with or without subscript activated or zero point five for the decimal example_
for one-third - 1/3 (is it pronounced 1 / 3 or one third?) - as a decimal it would be 0.3333 repeating so no good as a decimal _JAWS states ‘one slash three’_
some others - 3/4, 1/4, 1/5 etc. _JAWS states ‘three slash four’, ‘one slash four’ and ‘one slash five’_
what is the safest way to represent these to be sure they are understood? _I would use whole words to describe the fraction i.e. one half, three quarters, one fifth etc. or, depending on context ‘up to 1/3  of respondents stated…..’ use the percentage 33%_

This works with 'say all’ or word by word.  I’m using JAWS 17 with intermediate level of verbosity and some punctuation.

https://github.com/govau/content-guide/issues/48


[WIP] metrics: add summary statistics

WIP: will remove [WIP] when ready for full review.

[x] Closes #231 .

[x] I am familiar with the contributing guidelines.
[x] Tests added.
[ ] Updates entries to docs/source/api.rst for API changes.
[ ] Adds descriptions to appropriate "what's new" file in docs/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[ ] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
[ ] Maintainer: Appropriate GitHub Labels and Milestone are assigned to the Pull Request and linked Issue.

This PR adds solarforecastarbiter.metrics.summary, which contains functions for computing summary statistics of observations/forecasts (e.g. min, max, mean and std). These summary statistics will eventually be incorporated into the report interface (which will be addressed in subsequent PRs).

@wholmgren Before I go too far with this PR, is this the direction you were thinking for the summary statistics? If so, what level of documentation and testing is needed (e.g. full docstrings + tests per function or something more minimal given that the summary functions are mainly just wrapping numpy functions)?

I don't think we need detailed docstrings. I guess it's good to test behavior in the presence of nans.
Do you think we'd be ok skipping these wrappers and only defining the _MAP dictionary in terms of the numpy functions? It seems unlikely that any direct user of the python code would ever want to call our versions of these functions.
Why did you choose to go with the nan versions of the functions in this PR?

Do you think we'd be ok skipping these wrappers and only defining the _MAP dictionary in terms of the numpy functions? It seems unlikely that any direct user of the python code would ever want to call our versions of these functions.

I agree with your point and think we'll be okay with no wrappers. I'll revise accordingly.

Why did you choose to go with the nan versions of the functions in this PR?

I was originally thinking that there may be cases where these summary functions would be called before/without the validation and preprocessing steps, and therefore the functions would need to handle inputs with nan values. But reflecting on this, I don't think that's likely to be a real concern. So I'll switch back to the non-nan versions (np.mean(), np.min(), etc.).

@wholmgren I've revised to just defining the _MAP dictionary (rather than adding full wrappers to the numpy functions) and adding (simple) tests to confirm the functions work as expected when called via the _MAP dictionary.

Do I need to add anything to docs/api or docs/whatsnews about this PR? I would think no since the the summary metrics will only be used "internally" by other parts of the codebase.

@dplarson I agree we can skip the documentation. Thanks!


Setup initial project

https://docs.npmjs.com/misc/scripts
https://babeljs.io/docs/usage/cli/

Use Electron: https://github.com/atom/electron/blob/master/docs/tutorial/quick-start.md

Looks good to me!

Application Menu: https://github.com/atom/electron/blob/master/docs/api/menu.md


Problem with multiple draggable cursors

Not sure how to describe this so I'll demonstrate with this:

For some reason there's a big discrepancy between where the mouse cursor actually is versus where the annotation thinks it is. Any idea what the problem is here?
import numpy as np
from mpldatacursor import datacursor
import matplotlib.pyplot as plt

t = np.linspace(0, 10, 200)
x = np.cos(t)
y = np.sin(t)

plt.close('all')
plt.figure()
plt.plot(t, 3 * x)
plt.plot(t, 10 * y, 'r')

cursor = datacursor(axes=[plt.gca()], display='multiple', draggable=True)

Just out of curiosity, how did you record your desktop ?
Nils
Am 22.03.2015 um 22:23 schrieb wilywampa<EMAIL_ADDRESS>
Not sure how to describe this so I'll demonstrate with this:
For some reason there's a big discrepancy between where the mouse cursor actually is versus where the annotation thinks it is. Any idea what the problem is here?
import numpy as np
from mpldatacursor import datacursor
import matplotlib.pyplot as plt
t = np.linspace(0, 10, 200)
x = np.cos(t)
y = np.sin(t)
plt.close('all')
plt.figure()
plt.plot(t, 3 * x)
plt.plot(t, 10 * y, 'r')
cursor = datacursor(axes=[plt.gca()], display='multiple', draggable=True)
—
Reply to this email directly or view it on GitHub.

LICEcap: https://github.com/lepht/licecap

This is a matplotlib issue: https://github.com/matplotlib/matplotlib/issues/4295


Cant join rust server

#It looks fine when i start my rust server, but when I join it on the rust client nothing happens.
I installed the server using UltimateBytes video.
I am running debian 8.4.
I am editing the server over SSH because it is my friends. Could it be a problem with the ports?
Here are my logs:
Mono path[0] = '/home/rustserver/serverfiles/RustDedicated_Data/Managed'
Mono path[1] = '/home/rustserver/serverfiles/RustDedicated_Data/Mono'
Mono config path = '/home/rustserver/serverfiles/RustDedicated_Data/Mono/etc'
Initialize engine version: 5.3.4f1 (fdbb5133b820)
Forcing GfxDevice: Null
NullGfxDevice:
Version:  NULL 1.0 [1.0]
Renderer: Null Device
Vendor:   Unity Technologies
AudioManager: Using Unknown: NoSound Driver
Begin MonoManager ReloadAssembly
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/UnityEngine.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/UnityEngine.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Assembly-CSharp-firstpass.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/Assembly-CSharp-firstpass.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Assembly-CSharp.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/Assembly-CSharp.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Assembly-UnityScript-firstpass.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/Assembly-UnityScript-firstpass.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/UnityEngine.UI.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/UnityEngine.UI.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/UnityEngine.Networking.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/UnityEngine.Networking.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/ConvexHull.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/ConvexHull.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/I18N.CJK.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/I18N.CJK.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/I18N.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/I18N.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/I18N.MidEast.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/I18N.MidEast.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/I18N.Other.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/I18N.Other.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/I18N.Rare.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/I18N.Rare.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/I18N.West.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/I18N.West.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Ionic.Zip.Reduced.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/Ionic.Zip.Reduced.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/LZ4n.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/LZ4n.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Newtonsoft.Json.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/Newtonsoft.Json.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Behave.Unity.Assets.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/Behave.Unity.Assets.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Behave.Unity.Runtime.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/Behave.Unity.Runtime.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/protobuf-net.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/protobuf-net.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/RustBuild.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/RustBuild.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/EasyAntiCheat.Client.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/EasyAntiCheat.Client.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/EasyAntiCheat.Server.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/EasyAntiCheat.Server.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Facepunch.Input.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/Facepunch.Input.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Facepunch.Network.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/Facepunch.Network.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Facepunch.Rcon.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/Facepunch.Rcon.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Facepunch.System.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/Facepunch.System.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Facepunch.UnityEngine.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/Facepunch.UnityEngine.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Rust.Data.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/Rust.Data.dll into Unity Child Domain
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/websocket-sharp.dll (this message is harmless)
Loading /home/rustserver/serverfiles/RustDedicated_Data/Managed/websocket-sharp.dll into Unity Child Domain

Completed reload, in  0.096 seconds
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/System.Core.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/System.dll (this message is harmless)
UnloadTime: 1.711000 ms
System
Name: sparky
OS:   Linux 3.16 Debian 8.4 64bit

CPU
Model:  Intel(R) Atom(TM) CPU  C2750  @ 2.41GHz
Cores:  8
Memory: 32218 MB
GPU
Model:  Null Device
API:    NULL 1.0 [1.0]
Memory: 128 MB
SM:     20
Memory
Private:     0 MB
Working Set: 0 MB
Process
Priority: 0
Threads:  0
Memory:   60 MB
Peak:     61 MB
Mono
Collects: 4
Memory:   0 MB
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Oxide.Core.dll (this message is harmless)
server.ip: "<IP_ADDRESS>"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.port: "28015"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.tickrate: "30"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.hostname: "Rust"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.identity: "rust-server"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.maxplayers: "50"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.worldsize: "4000"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.saveinterval: "300"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
rcon.ip: "<IP_ADDRESS>"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
rcon.port: "28016"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
rcon.password: "CHANGE_ME"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/System.Runtime.Serialization.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/System.Xml.Linq.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/System.Xml.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/System.Data.dll (this message is harmless)
Fallback handler could not load library /home/rustserver/serverfiles/RustDedicated_Data/Mono/x86_64/kernel32
Fallback handler could not load library /home/rustserver/serverfiles/RustDedicated_Data/Mono/x86_64/libkernel32.so
Fallback handler could not load library /home/rustserver/serverfiles/RustDedicated_Data/Mono/x86_64/./kernel32
Fallback handler could not load library /home/rustserver/serverfiles/RustDedicated_Data/Mono/x86_64/./libkernel32.so
Fallback handler could not load library /home/rustserver/serverfiles/RustDedicated_Data/Mono/x86_64/kernel32
Fallback handler could not load library /home/rustserver/serverfiles/RustDedicated_Data/Mono/x86_64/libkernel32
Fallback handler could not load library /home/rustserver/serverfiles/RustDedicated_Data/Mono/x86_64/libkernel32.so
Fallback handler could not load library /home/rustserver/serverfiles/RustDedicated_Data/Mono/x86_64/./libkernel32
Fallback handler could not load library /home/rustserver/serverfiles/RustDedicated_Data/Mono/x86_64/./libkernel32.so
Fallback handler could not load library /home/rustserver/serverfiles/RustDedicated_Data/Mono/x86_64/libkernel32
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/System.Configuration.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Oxide.Ext.CSharp.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Mono.Cecil.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Oxide.Ext.JavaScript.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Jint.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Oxide.Ext.Lua.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/NLua.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/KeraLua.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Oxide.Ext.MySql.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/MySql.Data.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Oxide.Ext.Python.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Microsoft.Scripting.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/IronPython.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Microsoft.Dynamic.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Microsoft.Scripting.Core.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/IronPython.Modules.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Mono.Security.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Oxide.Ext.SQLite.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/System.Data.SQLite.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Oxide.Ext.Unity.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Oxide.Game.Rust.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/System.Transactions.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/System.Configuration.Install.dll (this message is harmless)
Platform assembly: /home/rustserver/serverfiles/RustDedicated_Data/Managed/Mono.Data.Tds.dll (this message is harmless)
Command Line: "./RustDedicated" "-batchmode" "+server.ip" "<IP_ADDRESS>" "+server.port" "28015" "+server.tickrate" "30" "+server.hostname" "Rust" "+server.identity" "rust-server" "+server.maxplayers" "50" "+server.worldsize" "4000" "+server.saveinterval" "300" "+rcon.ip" "<IP_ADDRESS>" "+rcon.port" "28016" "+rcon.password" "CHANGE_ME" "-logfile" "gamelog-2016-06-03-13-45-06.log"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.ip: "<IP_ADDRESS>"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.port: "28015"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.tickrate: "30"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.hostname: "Rust"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.identity: "rust-server"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.maxplayers: "50"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.worldsize: "4000"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
server.saveinterval: "300"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
rcon.ip: "<IP_ADDRESS>"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
rcon.port: "28016"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
rcon.password: "CHANGE_ME"
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
Server Config Loaded
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
Loading Items Took: 0.892 seconds
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
Building Items Took: 0.948 seconds / Items: 275 / Blueprints: 193
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
Unloading 4 Unused Serialized files (Serialized files now loaded: 33)
WARNING: Shader Unsupported: 'Nature/Water/Ocean' - Setting to default shader.
WARNING: Shader Unsupported: 'Rust/Standard Terrain BaseMap' - All passes removed
WARNING: Shader Unsupported: 'Rust/Standard Terrain BaseMap' - All passes removed
WARNING: Shader Unsupported: 'Rust/Standard Terrain BaseMap' - All passes removed
WARNING: Shader Unsupported: 'Rust/Standard Terrain BaseMap' - All passes removed
WARNING: Shader Unsupported: 'Rust/Standard Terrain' - All passes removed
WARNING: Shader Unsupported: 'Rust/Standard Terrain' - All passes removed
WARNING: Shader Unsupported: 'Rust/Standard Terrain' - All passes removed
WARNING: Shader Unsupported: 'Rust/Standard Terrain' - All passes removed
WARNING: Shader Unsupported: 'Rust/Standard Terrain' - All passes removed
WARNING: Shader Unsupported: 'Rust/Standard Terrain' - All passes removed
WARNING: Shader Unsupported: 'Nature/Water/River' - Setting to default shader.
UnloadTime: 11.757000 ms
Generating terrain of size 4000 with seed 52267562
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[AmplifyColor] This image effect is not supported on this platform. Please make sure your Unity license supports Full-Screen Post-Processing Effects which is usually reserved forn Pro licenses.
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
Unloading 46 unused Assets to reduce memory usage. Loaded Objects now: 7700.
Total: 93.519005 ms (FindLiveObjects: 1.170000 ms CreateObjectMapping: 1.071000 ms MarkObjects: 91.007004 ms  DeleteObjects: 0.268000 ms)
[Oxide] 13:45 [Info] Loading Oxide Core v2.0.1988...
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[Oxide] 13:45 [Info] Loading extensions...
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[Oxide] 13:45 [Info] Loaded extension CSharp v1.0.1988 by Oxide Team
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[Oxide] 13:45 [Info] Loaded extension JavaScript v1.0.1988 by Oxide Team
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[Oxide] 13:45 [Info] Loaded extension Lua v1.0.1988 by Oxide Team
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[Oxide] 13:45 [Info] Loaded extension MySql v1.0.1988 by Oxide Team
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[Oxide] 13:45 [Info] Loaded extension Python v1.0.1988 by Oxide Team
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[Oxide] 13:45 [Info] Loaded extension SQLite v1.0.1988 by Oxide Team
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[Oxide] 13:45 [Info] Loaded extension Unity v1.0.1988 by Oxide Team
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[Oxide] 13:45 [Info] Loaded extension Rust v1.0.1988 by Oxide Team
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[Oxide] 13:45 [Info] Using Covalence provider for game 'Rust'
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[Oxide] 13:45 [Info] Loading plugins...
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[Oxide] 13:45 [Info] Loaded plugin Unity Core v1.0.0 by Oxide Team
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[Oxide] 13:45 [Info] Loaded plugin Rust v1.0.0 by Oxide Team
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[AmplifyOcclusion] GBuffer Normals only available in Camera Deferred Shading mode. Switched to Camera source.
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
RCon Started on 28016
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[12.3s] HEIGHT MAP
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[6.5s] MOUNTAINS
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[0.5s] BIOME MAP
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[3.9s] TOPOLOGY MAP
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[1.2s] SPLAT MAP
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[14.6s] LARGE MONUMENTS
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[1.0s] MEDIUM MONUMENTS
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[1.8s] SMALL MONUMENTS
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[12.5s] RIVER LAYOUT
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)
[0.3s] RIVER OBJECTS
(Filename: /home/builduser/buildslave/unity/build/artifacts/generated/common/runtime/UnityEngineDebugBindings.gen.cpp Line: 37)

Edit your post using pastebing, and maybe i'll read it.

Here are my ./rustserver details
http://pastebin.com/ugFceZSe

Seems like an OVH Game server ? Got the same :)
There is a firewall to setup in your OVH interface. It's enabled by default and will block this. It's pretty hard to find the first time. Call OVH for support if needed, otherwise i may make some screenshots for you.

Okay, my friend owns the server. I will ask him about this OVH thing. Thank you.

Could you make some screenshots for me? it may help.

Good server choice. Best server choice actually. :)
You're welcome :)

Its his own dedicated server and its at his house.

Well, bad port redirection then ?

Hi @PuggerHugger
Could you execute the following command in an ssh session on sparky:

curl http://icanhazip.com/
This will return an IPv6 or IPv4 address. That's your public IP address. Currently the server is starting on a private IP address so you won't be able to connect to it whatever you do. (Your friend should be able to if he's on the same subnet.)

I don't know what you're planning with your Rust server but the Atom C2750 isn't exactly a powerhouse. You'll soon run in performance issues if you're going to go bigger than a few players.

@JHulsmans Didn't even see that.
Actually, if it's a self hosted server, it should use a private IP, but then the router has to have the right port redirection.


Are you ever gonna update this to the most current version?

Sure! I don't play the game much anymore but if anyone could let me know what's changed I'll do what I can!

most recent update
https://store.steampowered.com/news/app/739630/view/6215608421522854557?l=english

For anyone interested, my fork of the project is kept updated. It is a heavily modified fork though, so do read the project page description first.


Wrap pre element so it doesn't overflow

Fixes https://issues.redhat.com/browse/AAH-599
Collection detail documentation page of: ibm -> power_ibm -> module > ibmi_install_product_from_savf
Before:

After:

@himdel Updated. Please have a look. Thanks :)


Lifecycle bug: Test runner teardown does not yeet gameobjects that DontDestroyOnLoad(). This is the case for CamerasManager.

The map is thus broken, as there is more than 1 main camera and the code didn't expect such thing. (only in unity test, and for the 2nd test onwards.)

usually GOs that call DontDestroyOnLoad() will be singleton- style objects.
Monobehavior singletons will often check for existing instance of themselves
our camera manager is not implementing this.
ie :
if (AudioManager.Instance != null)
    Destroy(this.gameobject);

    // if an instance already exists, yeet self.

hehe


MINOR: Generated classes should have standard equals

Previously, generates classes that were used as keys got non-standard
equals and hashCode functions which only checked the fields that were
part of their keys.  This was confusing for people using those functions
in different contexts.
Instead, we should give ImplicitLinkedHashCollection and subclasses the
ability to use a separate function to compare and hash the key fields,
and generate standard equals and hashCode functions.

Superseded by #8539


[R] Checking whether DMatrix has field implies making full data copies of said field

Follow up from https://github.com/dmlc/xgboost/pull/9863
ref https://github.com/dmlc/xgboost/issues/9810
In methods such as print.xgb.DMatrix:
https://github.com/dmlc/xgboost/blob/562352101d5dd1630eded1522b9b4ed9b07e8692/R-package/R/xgb.DMatrix.R#L517
The code checks whether a DMatrix has a given field by retrieving it.
This causes a full (maybe even two?) data copy of the underlying field being retrieved, but the data there is not used: it's only being checked that it exists.
Would be more efficient to use some way of checking that the DMatrix has a field taht would not involve copying all of the data in that field.

We don't have this method yet. For the print method you referenced, I think it's easy to just get all meta info and filter it by null values. We need all the available fields anyway.
As for the AFT PR, I think we can merge it for now, but wouldn't it be better for the long term that we can avoid processing the DMatrix and move toward the high-level interface? If so, we can just get the label/bounds from user inputs instead of the DMatrix.


Bug: Periods not allowed in task name

 Issue by rclough
Thursday Jun 12, 2014 at 18:01 GMT
Originally opened as https://github.com/thieman/dagobah/issues/98

Periods apparently aren't allowed in the task name. This should either be checked by JS on the front end, or at least we should have more intelligent error reporting around it.
Error from stderr:
The dotted field 'Name with.period' in 'dependencies.Name with.period' is not valid for storage.

 Comment by rclough
Thursday Jun 12, 2014 at 18:22 GMT

after a hard refresh it appears the job gets added but it causes errors on all further commands, haven't tested for other issues.

 Comment by thieman
Friday Jun 13, 2014 at 12:04 GMT

I'm guessing this only affects the Mongo backend, but we'll need to protect against periods regardless to keep things consistent.

 Comment by rclough
Friday Jun 13, 2014 at 15:59 GMT

Confirming this is just with mongo


How to run the camera inference in online mode?

Hi Guanghan,
Thanks for your work. Now in demo_video_mobile.py, we read an video and process with online mode (one by one frame.)
Do you have scripts with run the model with a camera? You will get one frame each time without knowing the total number of frames.
Thank you.

Hi Zhuoran,
Currently, I do not have such scripts available. Reason is... I did not have a local machine and a camera at hand. But this is an important feature, I plan to implement it in the near future. I believe it should be easy to adapt from the current code. Thanks!

@WuZhuoran
The camera demo has been added. Please check the master. Thanks!


[CLI]: api.runs() Method Returns Duplicate and Missing Runs

Describe the bug

I am encountering an issue with the Weights and Biases API where the api.runs() method returns duplicate runs and omits some other runs. What is important, is that the total number of runs returned is correct, but the runs do not correspond to the actual ones.

import wandb

# Initialize the API
api = wandb.Api()

# Project is specified by <entity/project-name>
runs = api.runs("kotekjedi/llm-rs")

# Use a set to track processed run IDs
processed_run_ids = set()

summary_list, config_list, name_list = [], [], []

for run in runs:
    run_id = run.id
    if run_id not in processed_run_ids:
        # Add the run ID to the set
        processed_run_ids.add(run_id)

        # Process the run data
        summary_list.append(run.summary._json_dict)
        config_list.append(
            {k: v for k, v in run.config.items() if not k.startswith('_')}
        )
        name_list.append(run.name)
    else:
        print(f"Duplicate run found: {run_id}")

Duplicate run found: k14f2vc7
Duplicate run found: la325tya
Duplicate run found: 4cx54f3h
Duplicate run found: 7owoqll6
Duplicate run found: lxtzne8y
Duplicate run found: kr18m6w6
Duplicate run found: 2yokxira
Duplicate run found: sf8sb853
Duplicate run found: o72vgxfy
Duplicate run found: k0vyhar6

Additional Files
No response
Environment
WandB version:
'0.17.0'
OS:
Windows 11
Python version:
Python 3.11.5
Versions of relevant libraries:
Additional Context
No response

Hi @kotekjedi , we tried to repro this one but did not get the same result. Are you also seeing those result in the UI, runs being duplicated?

HI @JoanaMarieL, thanks for reaching out!
In UI it is perfectly fine, runs are not duplicated or missing. However, when I try to download it I am not getting all of the runs - some are just missing, and some are duplicated.

Hey,
I just want to confirm that I am having the same issue. In my case: total number of runs is 1200 (same as in UI), number of distinct run ids is 1163 and the number of duplicates is 37 as verified through this code snippet;
import wandb

api = wandb.Api()
runs = api.runs(project_name)

distinct_run_ids = set()
duplicate_run_ids = set()

print(f"Number of runs (total): {len(runs)}")

for run in runs:
    if run.id in unique_run_ids:
        duplicate_run_ids.add(run.id)
    else:
        distinct_run_ids.add(run.id)

print(f"Number of distinct run ids: {len(distinct_run_ids)}")
print(f"Number of duplicate run ids: {len(duplicate_run_ids)}")

With output:
Number of runs (total): 1200 Number of distinct run ids: 1163 Number of duplicate run ids: 37
I also verified that there are as many IDs missing as there are duplicate IDs in the runs list when compared to the UI. I did so by downloading the .csv from the UI and comparing its IDs with the IDs in the runs object. Just to make sure there are no duplicate IDs displayed already in the UI.
Python: 3.10.14 / wandb: 0.15.12 on MacOS 14

Hello @kotekjedi and @PhilippBordne , thank you both for flagging this, we have the fix for this issue this coming June. As a work around please add this to your code:
runs = api.runs(
    path=<entity/project>,
    order="+created_at"
)

Hope this helps. Thanks!

Hi @kotekjedi , our engineers already fixed the issue, could you please try and confirm if it is also working on your end. Thanks!

You are most welcome @kotekjedi , marking this as resolved. Feel free to reach us out again anytime.

Hey,
I am sorry to report that the issue has not been resolved yet. I am facing the same issue, using version 0.17.9

api = wandb.Api()
sweep = api.sweep(f"{entity}/{project}/{sweep_id}")

run_ids = [run.id for run in sweep.runs]
run_ids_unique = list(set(run_ids))

print(len(run_ids))
print(len(run_ids_unique))´´´

yields:

0.17.9
4608
4600
´´´

This happens on 0.18.0 as well, accessing sweep.runs like @majoma7 did.
Modifying the pagination bysweep.runs.per_page = len(sweep.runs) before accessing sweep.runs seem to solve the problem, at least in my case. This might be indicative of a problem with how pages are handled inside the Runs object.


Segmentation fault on Ubuntu16.04

The demo was failing with segmentation fault on ubuntu16.04 because of this line:
egl_.display = eglGetDisplay(EGL_DEFAULT_DISPLAY);
If it is changed to
egl_.display = eglGetDisplay((EGLNativeDisplayType)gbm_);
is working.

I would like to know the cause of this issue.

This is also the case on Ubuntu 19.10 and for Raspbian Buster on the Raspberry Pi 4.
For the Raspberry Pi 4, you will also need to enable FKMS and use the following drive:
./gbm_es2_demo -D /dev/dri/card1

The demo was failing with segmentation fault on ubuntu16.04 because of this line: egl_.display = eglGetDisplay(EGL_DEFAULT_DISPLAY); If it is changed to egl_.display = eglGetDisplay((EGLNativeDisplayType)gbm_); is working.

Thanks，Valid here in debian11


RUST compatibility (AIV-509)

Any plans for this library to support the ESP Embedded Rust Community?
https://github.com/esp-rs

Hi @elasticdotventures, sorry we don't have this plan yet.


How to reference Tx in transfer proof when using P2C scheme?

When implementing some RGB proofs, it seems the txid has a circular dependence when the pay-to-contract scheme is used. The proof references the on chain Tx to which it is bound in the bind_to field
My understanding:
->bind_to references original_txid in proof
-> proof used to tweak public keys of some outputs
-> Tx output public keys have changed, therefore SHA256d(Tx) = new_txid != original_txid
-> bind_to is changed to now reference new_txid
-> etc.
As far as I can tell, the current behaviour is not explicitly defined. Should the bind_to field be omitted when tweaking the keys and verifying commitments?

How do future parties know where the commitments will lie if the TxID is not referenced within the proof at each step?
For vout based transfer they can just walk back up the chain and the location of the commitment will be deterministic; but for UTXO-based transfer, the TxID of previous transfers must be included, no?

The verification process implemented in rgb-rust is dependent upon being to fetch the transaction using tx_provider function, which takes as input the bind_to fields of the relevant proofs/inputs.
I don't think this is an issue of rgb-rust specifically, it's an issue affecting the general verification protocol.
commitment verification
[verification of previous comments] (https://github.com/rgb-org/rgb-rust/blob/95e84e652f56969d6f11406c5636ed177515fa50/src/proof.rs#L233)

The code is wrong b/c of the bug introduced into the original rgb version at some point, and I just copied it.
The spec was also incomplete in this regard. Basically, you need to always commit within the tx that spends any of RGB assets, so there is no need to reference its txid inside the proof itself. I've updated the spec – pls see https://github.com/rgb-org/spec/issues/102 and https://github.com/rgb-org/spec/pull/106/commits/da3a77b0b6746751b5f5696f10758ca8fc8f2de8
bind_to field within the proof should not be part of the commitment, it's an extended prunable field added to enhance the speed of communications with Bitcoin Core – check https://github.com/rgb-org/spec/issues/78 This field will be removed if we will accept https://github.com/rgb-org/spec/issues/80


Fix build hanging

Changed runnner and added-back code for freeing disk space
Closes #10
Note: need to

change-back docker username from 'okmo' to 'swedishembedded'
remove tmate?
change ubuntu runner to ubuntu-20.04

Set CMAKE_PREFIX_PATH for user builds in Dockerfile.develop
as mentioned in https://github.com/swedishembedded/sdk/issues/20

Merged after fixing a few things.


Delegate properly to custom Resolver instances

Let EmptyTemplateResolver create instances of either EmptyTemplateResolver::ResolverDecorator or EmptyTemplateResolver::FileSystemResolver, depending on whether the given path argument is an ActionView::Resolver instance or not.
The new EmptyTemplateResolver::ResolverDecorator class simply delegates all method calls to its given resolver, except for #find_all and #find_all_anywhere which it overrides to return templates that render with EmptyTemplateHandler.
Supersedes #1568 and hopefully also #1557.

Example of code that this PR will fix: https://gist.github.com/bquorning/6bf534e4b145b1738bb2. It’s a bit contrived, since I didn’t want to create tables and fetch custom templates from the database.

cc @JonRowe and @pixeltrix

Needs specs demonstrating what this actually solves vs #1557, in fact ideally we need smoke specs for both "rendering" views and "not rendering" views via this code path.

See my comment https://github.com/rspec/rspec-rails/pull/1557#discussion_r55332474 for why #1557 doesn’t work.
I agree that it would be nice to have specs for this (as we discussed in #1551), but they are pretty hard to write. Any suggestions are welcome.

Any suggestions are welcome.

Take the scenario you posted that supposedly doesn't work and put it into one of the smoke test apps.

I added a smoke spec that passes for this branch, and fails on both master and #1557. Suggestions for cleaning up the spec are much welcome.

@JonRowe, @pixeltrix This PR has a green build and is ready for review.

@JonRowe You were right, there was a bug in the view rendering code (inside ResolverDecorator, see the last commit).
How do the added specs look?
(I’ll need to squash the commits before the PR is mergeable)

@JonRowe We have specs, a green build and squashed commits. Wanna review?

:+1: Thanks


[ci] Segfaults?

See https://github.com/RobotLocomotion/drake-ros/actions/runs/9670843228
=================== Test output for //drake_ros:tf2_test:
...
drake_ros/test/tf2_test.py Fatal Python error: Segmentation fault
...
Extension modules: numpy._core._multiarray_umath, numpy._core._multiarray_tests, numpy.linalg._umath_linalg, tf2_py._tf2_py (total: 4)
...
//drake_ros:geometry_conversions_test                                    FAILED in 26.7s
//drake_ros:tf2_test                                                     FAILED in 25.2s
//drake_ros:viz_test                                                     FAILED in 27.1s

On my machine, I do not see these segfaults.
EDIT: Naive guess is that numpy gets upgraded by this (silly?) setup:
https://github.com/ros-tooling/setup-ros/blob/v0.4/src/setup-ros-linux.ts#L132-L138
https://github.com/ros-tooling/setup-ros/blob/v0.4/src/package_manager/pip.ts#L63
\cc @IanTheEngineer @calderpg-tri

Per #363, something in ros-tooling/setup-ros seems like the culprit. Most likely the numpy upgrade.


Add a package.json script for auto-generating metadata typings from json schema

One of the issues I've run into with the DLP redesign is that dandiset metadata has no typings (obviously, since that would mean having to maintain and change them every time there's a schema change), so the benefits of TypeScript are mostly lost for a pretty significant part of the redesign. I tried to come up with a solution to this in this PR.
I found this nice package that converts JSON schemas to TypeScript typings; using this, we can generate typings for any metadata schema version. I tried out the typings it generated for schema 0.5.1 while doing some of the DLP redesign stuff and it seems to work great. This PR adds a yarn script to automatically download and generate typings for a given schema version.
This does introduce some overhead for developers in that someone has to run the script whenever a new schema version is released, but I think it's well worth it considering that we'll get all of the benefits of TypeScript in any metadata-related code (including catching any breaking schema changes at compile time :astonished: )

Didn't look in detail, but can that script

be ran by pre commit
CI run it too, and if it introduced changes, means that developer didn't run it, or ran using different/outdated version of dandischema - error out

Didn't look in detail, but can that script

be ran by pre commit
CI run it too, and if it introduced changes, means that developer didn't run it, or ran using different/outdated version of dandischema - error out

A CI job to run this script and fail or warn if the results introduce changes is a good idea, but I don't think we should immediately enforce the latest schema version as a requirement on all PRs (at least, to start).
Is there a reason to believe that any PR that doesn't work with the latest schema version is flawed from the start?

Would it be appropriate to move this functionality to a new node package in https://github.com/dandi/schema and simply import the package+types in dandiarchive? Then the types would be generated automatically by CI in schema, and updating the schema version would be as simple as updating the dependency.

I think that sounds like a great idea. I'll merge this PR for now since it will be immediately helpful to me as I work on more of the DLP redesign, but I vote that we do this at some point. There's even a json-schema-to-typescript CLI that should make generating the types in CI easy.

Great idea indeed.  If I got it right -- this would be the actual workflow https://github.com/dandi/dandischema/blob/master/.github/workflows/release.yml of dandischema which produces a release within schema repository.  Should be trivial to extend and we could populate those files if needed for already existing release there.


[Feature] Provide DocumentFindReplace plugin for univer doc

Initial checklist

[X] Is this really a problem?
[X] I have searched the Github Issues for similar issues, but did not find anything.

Problem
Provide document's find and replace plugin

maybe this solution will solve your problem click


Give larhauga write access to repo

@hasheddan could you give @larhauga access? thanks!

I believe @muvaf set up this repo so I don't have access to add new folks. @muvaf could you add @larhauga and then close this out? :)

Ugh sorry that took some time. @larhauga you should get an invite now


dashboard reports not working

Description
I want to create a dashboard report.
The report doesn't seem to be created.
Steps to Reproduce
create a very simple dashboard -> one page -> one widget
widget is a pie chart.
like this:

execute a dashboard report with the dashboard guid.
cli:
./nr-reports-cli/bin/nr-reports.sh -d <redacted-dashboard-guid> --verbose

or docker:
#!/bin/bash
docker run --rm \
    --name nr-reports \
    -e NEW_RELIC_LICENSE_KEY='<redacted>' \
    -e NEW_RELIC_API_KEY='<redacted>' \
    -e NEW_RELIC_ACCOUNT_ID=<redacted> \
    -e DELAY_TIMEOUT_MS=15000 \
    newrelic-reports -d <redacted-dashboard-guid> --verbose

with docker settings:
FROM alpine:3.19

# Install required packages
RUN apk add --no-cache chromium nss freetype harfbuzz ca-certificates ttf-freefont nodejs yarn npm

# Copy function code
COPY nr-reports-core /app/nr-reports-core/
COPY nr-reports-cli /app/nr-reports-cli/
COPY templates /app/nr-reports-cli/templates/
COPY include /app/nr-reports-cli/include/

# Tell Puppeteer to skip installing Chrome. We'll be using the installed package.
ENV PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true \
    PUPPETEER_EXECUTABLE_PATH=/usr/bin/chromium-browser

# Add user so we don't need --no-sandbox.

Relevant Logs / Console output
{"level":20,"time":1719223387834,"pid":92361,"hostname":"my-hostname","name":"nr-reports","component":"engine","newrelic":"[REDACTED]","runnerId":"nr-reports-cli","runnerVersion":"3.1.2","secrets":"[REDACTED]","defaultChannelType":"file","namespace":{"length":0},"dashboardIds":"<redacted-dashboard-guid>","noRender":false,"msg":"Engine started."}
(node:92361) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
(node:92361) NOTE: We are formalizing our plans to enter AWS SDK for JavaScript (v2) into maintenance mode in 2023.

Please migrate your code to use AWS SDK for JavaScript (v3).
For more information, check the migration guide at https://a.co/7PzMCcy
{"level":20,"time":1719223387841,"pid":92361,"hostname":"my-hostname","name":"nr-reports","component":"engine","msg":"Running 1 reports..."}
{"level":20,"time":1719223387844,"pid":92361,"hostname":"my-hostname","name":"nr-reports","component":"util","msg":"Created temporary directory /var/folders/x3/b63zyv212s30790xjw3ds_l40000gp/T/nr-reports-Rvg36jFwpiEB"}
{"level":20,"time":1719223387845,"pid":92361,"hostname":"my-hostname","name":"nr-reports","component":"engine","msg":"Running report \"dashboard-report\"..."}
{"level":50,"time":1719223388148,"pid":92361,"hostname":"my-hostname","name":"nr-reports","component":"nerdgraph","msg":"GraphQL post error for query: {\"data\":{\"dashboardCreateSnapshotUrl\":null},\"errors\":[{\"extensions\":{\"classification\":\"DataFetchingException\",\"errorClass\":\"SERVER_ERROR\",\"type\":\"UNSUPPORTED_OPERATION\"},\"locations\":[{\"column\":7,\"line\":2}],\"message\":\"Unsupported operation on dashboard with given guid: <redacted-dashboard-guid>\",\"path\":[\"dashboardCreateSnapshotUrl\"]}]}"}
{"level":50,"time":1719223388148,"pid":92361,"hostname":"my-hostname","name":"nr-reports","component":"dashboard-generator","err":{"type":"ApiError","message":"GraphQL post error for query: {\"data\":{\"dashboardCreateSnapshotUrl\":null},\"errors\":[{\"extensions\":{\"classification\":\"DataFetchingException\",\"errorClass\":\"SERVER_ERROR\",\"type\":\"UNSUPPORTED_OPERATION\"},\"locations\":[{\"column\":7,\"line\":2}],\"message\":\"Unsupported operation on dashboard with given guid: <redacted-dashboard-guid>\",\"path\":[\"dashboardCreateSnapshotUrl\"]}]}","stack":"Error: GraphQL post error for query: {\"data\":{\"dashboardCreateSnapshotUrl\":null},\"errors\":[{\"extensions\":{\"classification\":\"DataFetchingException\",\"errorClass\":\"SERVER_ERROR\",\"type\":\"UNSUPPORTED_OPERATION\"},\"locations\":[{\"column\":7,\"line\":2}],\"message\":\"Unsupported operation on dashboard with given guid: <redacted-dashboard-guid>\",\"path\":[\"dashboardCreateSnapshotUrl\"]}]}\n    at NerdgraphClient.post (/Users/myuser/GIT/nr-reports/nr-reports-core/lib/nerdgraph.js:104:13)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async NerdgraphClient.query (/Users/myuser/GIT/nr-reports/nr-reports-core/lib/nerdgraph.js:134:25)\n    at async downloadDashboardPdf (/Users/myuser/GIT/nr-reports/nr-reports-core/lib/generators/dashboard.js:28:15)\n    at async /Users/myuser/GIT/nr-reports/nr-reports-core/lib/generators/dashboard.js:88:9\n    at async Promise.all (index 0)\n    at async Object.generateDashboardReport [as generate] (/Users/myuser/GIT/nr-reports/nr-reports-core/lib/generators/dashboard.js:90:23)\n    at async /Users/myuser/GIT/nr-reports/nr-reports-core/lib/engine.js:131:28\n    at async withTempDir (/Users/myuser/GIT/nr-reports/nr-reports-core/lib/util.js:212:5)\n    at async Engine.run (/Users/myuser/GIT/nr-reports/nr-reports-core/lib/engine.js:99:7)"},"msg":"GraphQL post error for query: {\"data\":{\"dashboardCreateSnapshotUrl\":null},\"errors\":[{\"extensions\":{\"classification\":\"DataFetchingException\",\"errorClass\":\"SERVER_ERROR\",\"type\":\"UNSUPPORTED_OPERATION\"},\"locations\":[{\"column\":7,\"line\":2}],\"message\":\"Unsupported operation on dashboard with given guid: <redacted-dashboard-guid>\",\"path\":[\"dashboardCreateSnapshotUrl\"]}]}"}
{"level":40,"time":1719223388148,"pid":92361,"hostname":"my-hostname","name":"nr-reports","component":"engine","msg":"No output generated for report \"dashboard-report\"."}
{"level":20,"time":1719223388149,"pid":92361,"hostname":"my-hostname","name":"nr-reports","component":"engine","msg":"Completed report \"dashboard-report\"."}
(node:92361) [DEP0147] DeprecationWarning: In future versions of Node.js, fs.rmdir(path, { recursive: true }) will be removed. Use fs.rm(path, { recursive: true }) instead
{"level":20,"time":1719223388149,"pid":92361,"hostname":"my-hostname","name":"nr-reports","component":"util","msg":"Removing temporary directory /var/folders/x3/b63zyv212s30790xjw3ds_l40000gp/T/nr-reports-Rvg36jFwpiEB..."}
{"level":20,"time":1719223388152,"pid":92361,"hostname":"my-hostname","name":"nr-reports","msg":"Letting agent data settle..."}
{"level":20,"time":1719223398155,"pid":92361,"hostname":"my-hostname","name":"nr-reports","msg":"Processing pending New Relic data..."}
{"level":20,"time":1719223398228,"pid":92361,"hostname":"my-hostname","name":"nr-reports","msg":"All done."}

I also have a version in a docker container where I updated the nr-reports the the newest versions (aws-sdk, node modules, and so on)
this is the output of that:
{"level":20,"time":1719222148702,"pid":1,"hostname":"8760ee2780e2","name":"nr-reports","component":"engine","newrelic":"[REDACTED]","runnerId":"nr-reports-cli","runnerVersion":"<unknown>","secrets":"[REDACTED]","defaultChannelType":"file","namespace":{"length":0},"dashboardIds":"<redacted-dashboard-guid>","noRender":false,"msg":"Engine started."}
{"level":20,"time":1719222148713,"pid":1,"hostname":"8760ee2780e2","name":"nr-reports","component":"engine","msg":"Running 1 reports..."}
{"level":20,"time":1719222148722,"pid":1,"hostname":"8760ee2780e2","name":"nr-reports","component":"util","msg":"Created temporary directory /tmp/nr-reports-XXXXXXojcAdI"}
{"level":20,"time":1719222148723,"pid":1,"hostname":"8760ee2780e2","name":"nr-reports","component":"engine","msg":"Running report \"dashboard-report\"..."}
{"level":50,"time":1719222149208,"pid":1,"hostname":"8760ee2780e2","name":"nr-reports","component":"nerdgraph","msg":"GraphQL post error for query: {\"data\":{\"dashboardCreateSnapshotUrl\":null},\"errors\":[{\"extensions\":{\"classification\":\"DataFetchingException\",\"errorClass\":\"SERVER_ERROR\",\"type\":\"UNSUPPORTED_OPERATION\"},\"locations\":[{\"column\":7,\"line\":2}],\"message\":\"Unsupported operation on dashboard with given guid: <redacted-dashboard-guid>\",\"path\":[\"dashboardCreateSnapshotUrl\"]}]}"}
{"level":50,"time":1719222149208,"pid":1,"hostname":"8760ee2780e2","name":"nr-reports","component":"dashboard-generator","err":{"type":"ApiError","message":"GraphQL post error for query: {\"data\":{\"dashboardCreateSnapshotUrl\":null},\"errors\":[{\"extensions\":{\"classification\":\"DataFetchingException\",\"errorClass\":\"SERVER_ERROR\",\"type\":\"UNSUPPORTED_OPERATION\"},\"locations\":[{\"column\":7,\"line\":2}],\"message\":\"Unsupported operation on dashboard with given guid: <redacted-dashboard-guid>\",\"path\":[\"dashboardCreateSnapshotUrl\"]}]}","stack":"Error: GraphQL post error for query: {\"data\":{\"dashboardCreateSnapshotUrl\":null},\"errors\":[{\"extensions\":{\"classification\":\"DataFetchingException\",\"errorClass\":\"SERVER_ERROR\",\"type\":\"UNSUPPORTED_OPERATION\"},\"locations\":[{\"column\":7,\"line\":2}],\"message\":\"Unsupported operation on dashboard with given guid: <redacted-dashboard-guid>\",\"path\":[\"dashboardCreateSnapshotUrl\"]}]}\n    at NerdgraphClient.post (/app/nr-reports-core/lib/nerdgraph.js:114:13)\n    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async NerdgraphClient.query (/app/nr-reports-core/lib/nerdgraph.js:144:25)\n    at async downloadDashboardPdf (/app/nr-reports-core/lib/generators/dashboard.js:27:15)\n    at async /app/nr-reports-core/lib/generators/dashboard.js:87:9\n    at async Promise.all (index 0)\n    at async Object.generateDashboardReport [as generate] (/app/nr-reports-core/lib/generators/dashboard.js:89:23)\n    at async /app/nr-reports-core/lib/engine.js:131:28\n    at async withTempDir (/app/nr-reports-core/lib/util.js:212:5)\n    at async Engine.run (/app/nr-reports-core/lib/engine.js:99:7)"},"msg":"GraphQL post error for query: {\"data\":{\"dashboardCreateSnapshotUrl\":null},\"errors\":[{\"extensions\":{\"classification\":\"DataFetchingException\",\"errorClass\":\"SERVER_ERROR\",\"type\":\"UNSUPPORTED_OPERATION\"},\"locations\":[{\"column\":7,\"line\":2}],\"message\":\"Unsupported operation on dashboard with given guid: <redacted-dashboard-guid>\",\"path\":[\"dashboardCreateSnapshotUrl\"]}]}"}
{"level":40,"time":1719222149209,"pid":1,"hostname":"8760ee2780e2","name":"nr-reports","component":"engine","msg":"No output generated for report \"dashboard-report\"."}
{"level":20,"time":1719222149211,"pid":1,"hostname":"8760ee2780e2","name":"nr-reports","component":"engine","msg":"Completed report \"dashboard-report\"."}
{"level":20,"time":1719222149212,"pid":1,"hostname":"8760ee2780e2","name":"nr-reports","component":"util","msg":"Removing temporary directory /tmp/nr-reports-XXXXXXojcAdI..."}
{"level":20,"time":1719222149228,"pid":1,"hostname":"8760ee2780e2","name":"nr-reports","msg":"Letting agent data settle..."}
{"level":20,"time":1719222164233,"pid":1,"hostname":"8760ee2780e2","name":"nr-reports","msg":"Processing pending New Relic data..."}
{"level":20,"time":1719222164315,"pid":1,"hostname":"8760ee2780e2","name":"nr-reports","msg":"All done."}

but same errors here
Your Environment
local cli:

MacBook Pro 16-inch, 2019:

2,6 GHz 6-Core Intel Core i7
AMD Radeon Pro 5300M 4 GB
16 GB 2667 MHz DDR4
13.6.7 (22G720)

docker:

Docker version 26.1.4, build 5650f9b
image: alpine:3.19

Additional context

Take a look here: https://forum.newrelic.com/s/hubtopic/aAX8W0000008cUvWAI/unsupported-operation-on-dashboard


Support text marks

Lyra 2 should support Vega's text mark type. This will involve creating:

[x] an primitive mark class.
[x] a manipulators transform class
[x] property inspector
[ ] test cases for rules

First three points ticked off in #281

@arvind can you clarify what "test cases for rules" means -- functional test cases, or unit tests?

I meant functional test cases. I had started on some for symbol marks which I used to produce PNGs. Producing PNGs affords visual inspection, but I'm not sure how robust it is against variations in server-side rendering (e.g., fonts). Another alternative is to generate the SVG strings and compare. Both of these, though, could come later and for now, we can just verify that rules produce the necessary properties on the model.

@arvind thanks for clarifying. I am going to close this now, then, and we can open more specific issues for iteration on text mark support/testing/etc as they occur to us.


test: ACTUALLY lint typescript and turn on strict mode for typescript

Don't merge this until all other pull requests are merged!!!
There will be a ton of conflicts that should be fixed before this can be merged.

tHiS bRaNcH hAs cOnFlIcTs tHaT mUsT bE rEsOlVeD

🚀 🚀 🚀


modified for DIG - JSON/J

Modified JDAO for the out in DIG.

I don't think you should modify the JDAO, just DIG. DIG should output data in the same format as the JDAO, but these modifications will make the JDAO slower even when not being used with DIG.


Thku8507 NCEI submission

Looks good!

Hello. Your page looks good. The Silverthorne photo isn't displaying on the page. One other tiny suggestion for future plots is to rename the series in the legend (instead of "temperature_f").  We are supposed to be reviewing the page, correct? Or should I look at the code in your repo?

@cmq879 - when doing these reviews, please go to Files Changed and add an Approve review with your comment. Makes it easier for me to see that you have completed your review!


Fix multiselect selected options overflow arrow

Coverage remained the same at 92.254% when pulling cb43f016f0f4dbcde50270f01a6dc4800fd76203 on tb:styles-fixes into 5656539bda156f6421dee3abc97842fc833b32b1 on mseemann:master.

Coverage remained the same at 92.254% when pulling a15a002909d5ad6df01b11421f649b275a22d664 on tb:styles-fixes into 5656539bda156f6421dee3abc97842fc833b32b1 on mseemann:master.

Coverage remained the same at 92.254% when pulling e42ce30cec197865f89b06075f40c54d231df7c4 on tb:styles-fixes into 5656539bda156f6421dee3abc97842fc833b32b1 on mseemann:master.

👍  published<EMAIL_ADDRESS>and<EMAIL_ADDRESS>did this fix #39 ?  @tb you should be able to close the issue i have added you as a collaborator. can you confirm this?


/mv set spawn

Hi,
I have a paper spigot  server running MultiVerse-Core but for some reason the "/mv set spawn" does not work, when I issue the command it says that the spawn was set but when I come out and then back in I dont spawn to the place I set.
Do you know what to try?

Is there another plugin controlling the spawn points?

The set spawn is for new players only, you will spawn at your last location afterwards.

Closing old ticket. If you still need help, it's best (way faster as we use GitHub to track bugs/suggestions) to receive support on the Multiverse Discord.