Unable to refer certificates in KV

How do I refer to certificates stored in KV. I want to use the certificate URL in my application gateway deployment. Looks like I am able to get the secret URL but not the certificate. Is it possible to get the certificate URL?
resource keyvault 'Microsoft.KeyVault/vaults@2021-06-01-preview' existing = {
  name: 'foo-gf-kv'
  scope: resourceGroup('acme-gf-rg')
}

resource alphasecret 'Microsoft.KeyVault/vaults/secrets@2021-06-01-preview' existing = {
  name: 'foo-bar-com'
  parent: keyvault

}

output kvid string = keyvault.id
output secretid string = alphasecret.properties.secretUri

The above file works well with secret but I need to get the same for the certificate.

cc @brwilkinson

Hi @jobinjosem
Certificates also can be referenced via the secret value/path.
E.g. connecting to the KV via User Assigned Managed Identity.
https://github.com/brwilkinson/AzureDeploymentFramework/blob/0aa5f1500b29fc7327956d3af621514625bf371b/ADF/bicep/WAF-WAF.bicep#L133
That is a Bicep template that I decompiled from ARM and is using the old syntax... I just reference the KV, then use string interpolation to join the path to the secret/certname.
However below is an example, adding onto what you provided.
Notice either secretidcert OR 'secretidcert ' provide the value that the App gateway is looking for.
var certName = 'WildcardCert'

resource keyvault 'Microsoft.KeyVault/vaults@2021-06-01-preview' existing = {
  name: 'ACU1-BRW-AOA-P0-kvVLT01'
}

resource alphasecret 'Microsoft.KeyVault/vaults/secrets@2021-06-01-preview' existing = {
  name: 'localadmin'
  parent: keyvault
}

resource alphasecretCert 'Microsoft.KeyVault/vaults/secrets@2021-06-01-preview' existing = {
  name: certName
  parent: keyvault
}

output kvid string = keyvault.properties.vaultUri
output secretid string = alphasecret.properties.secretUri
output secretidcert string = alphasecretCert.properties.secretUri
output valueusedinAppGateway string = '${keyvault.properties.vaultUri}secrets/${certName}'

If you look at the Cert in the KV, you can see that it has the secret identifier property listed: without the guid at the end it will always pull the latest version, you only need the guid to pull a specific version.

Thanks for the idea @brwilkinson . I fixed it using the first method like you used in your module.


External  library added in libs folder should be referred in windows

Expected behavior
External libraries added in libs folder should be referred when specified in properties file as below
gauge_additional_libs = libs/*
Actual behavior
Libraries are not referred and throws package does not exists error.
Linked https://github.com/getgauge/gauge-java/issues/377#issuecomment-616606623 ,
Gauge version
Gauge version: 1.0.8
Commit Hash: 28617ea

Plugins
-------
html-report (4.0.10)
java (0.7.6)
screenshot (0.0.1)

Related to https://github.com/getgauge/gauge-java/pull/419#discussion_r413974030
While the resolution of the gauge_additional_libs should be addressed, should there be a consideration made for a pre-defined directory in a project that would always be included on the classpath to potentially reduce its size?  Currently, this type of logic is being done in the launcher.ps1 > AddRunnerInClassPath to include all libs in the $PluginDir.  Should there also potentially be a $env:GAUGE_PROJECT_ROOT/<some directory>/* also added as a generic default?


Delete ExpandDirs and DiscoverPath

[ch3321]

I'll be removing ShiftedRead and replacing it with Read (starting when we compile from LogicalPlan) in a separate PR.

Definitely breaking. I think that if anyone is actually relying on this stuff that maybe they deserve to be broken, but it's probably better to have our semver reflect reality.
One thing I'd like to do at some point is reduce the footprint of our public API.

Travis build failed due to the ch2153 flake. Restarted it.


Application Verifier leak detected on agsDeInitialize()

when running agsDeinitialize(), ApplicetaionVerifier halts with the following error:
	=======================================
	VERIFIER STOP<PHONE_NUMBER>000900: pid 0x6424: A heap allocation was leaked.

	000001D3EBFBFFF0 : Address of the leaked allocation. Run !heap -p -a <address> to get additional information about the allocation.
	000001D3E1FBAD90 : Address to the allocation stack trace. Run dps <address> to view the allocation stack.
	000001D3E894FFD8 : Address of the owner dll name. Run du <address> to read the dll name.
	00007FFD980D0000 : Base of the owner dll. Run .reload <dll_name> = <address> to reload the owner dll. Use 'lm' to get more information about the loaded and unloaded modules.

	=======================================
	This verifier stop is continuable.
	After debugging it use `go' to continue.

	=======================================

	ags_sampled.exe has triggered a breakpoint.

This repros in the ags_sample. When running that in Debug config, the 000001D3E894FFD8 address points to "atiadlxx.dll"

I've repro'ed this. Thanks for the report. It will be something in the driver rather than in AGS itself. We'll see what we can do to resolve the issue.


Pinging Script with a mailer.

Description
A script that will continuously ping a server to see if the server is live or not and email the users of it is not live.
Technologies and Languages
Python.

@mdegis I have a script ready for this. If you need more details as to what the script does. Do ask. Otherwise assign or choose the issue.

Hi @arnav-deep, I guess u tagged the wrong person. Never mind.
And yes, this project seems interesting. Go ahead with it. Waiting for your PR

Hi @bislara
Sorry about tagging the wrong person. Not sure how that happened.
Linked a PR.


Fix getting partition metadata of a nonexistent topic returns 0

Fixes #8813
Motivation
Actually #8818 didn't fix the issue. The reason is when PulsarAdmin tries to get partition metadata, the checkAllowAutoCreation query param is false, so the topic existence check will never be performed.
Modifications

Check if the topic exists when the partition's metadata is 0 and checkAllowAutoCreation is false. See comments for detail explanations.
Change the current tests to make sure the check works.

Verifying this change

[ ] Make sure that the change passes the CI checks.

This change is already covered by existing tests, such as AdminApiTest#partitionedTopics.

Mark it as WIP first because there may be still some failed tests.

Now it's ready for review. It looks like there're still two flaky tests that can always pass in my local env.

LoadBalancerTest.testBrokerRanking
MessagePublishBufferThrottleTest.testBlockByPublishRateLimiting

/pulsarbot run-failure-checks

Thanks @eolivelli for your advice. I tried to add tests for non-persistent topics and found some difference between persistent topics and non-persistent topics. In this PR, I'll only fix the getPartitionedTopicMetadata implementation of non-persistent topics and mark the difference as comments.

@BewareMyPower can you please follow up with a new PR for non persistent topics ?
I am fine with merging this patch (but please check my comments)

@eolivelli I'll push a commit to fix the getPartitionedTopicMetadata for non-persistent topics in this PR. The other problems are subscription related admin operations. I may not have time to fix them recently, maybe we can open an issue to track it first.

@codelipenghui Please include this fix in 2.8.0 if it's merged

@eolivelli PTAL again

This PR breaks all previous clients who would like to use HTTP lookup. HTTP lookup at client side expects partitioned metadata with 0 partition and this PR gives TopicNotFoundException to client and old client couldn't handle it and won't be able to create a new topic which breaks topic creation semantics of Pulsar.
I have seen multiple such instances in past where we broke the compatibility and it's not acceptable.

@rdhabalia
I agree that this is a behaviour change in the API (although we introduced it in a major release, 2.8.0)
I think that this is fixing a bug, if the topic does not exist we should return "not found".
I understand that this is painful for clients who expected "0" instead of "Not Found", we should have advertised this change better or dealt with it in a different way.
Actually at the time of 2.8.0 we didn't have good tools/processes to deal with this kind of breaking changes (generally speaking breaking changes shouldn't be allowed at all!) .
Now the community evolved and before doing this kind of change we have to follow  a more strict process (PIP) and that's should allow us to not fall anymore in this kind of problems for existing users.

I am going to revert this change as old clients are just failing. let me know if anyone has any objections. I have experienced such intentional changes in past as well and I would like to check if anyone thinks that it's fine to do destructive changes just because their PRs will be merged then it's not a good practice. So, this time I want to set the message clear for these intentionally breaking changes.

This change has been released with 2.8 that now is a  very old release (very close to be considered obsolete). I am aware of many new users since 2
8 and for them we will introduce another breaking change.
I think that you could send out PR and start a discussion on dev@

before this change, the previous behavior was there for 8 years so, I definitely reject the claim that it's been there for the last 2 years. And again: this change is breaking the lookup for an old clients. it's a P0 and it's not acceptable with any justification.

also I don't understand why do we defend breaking changes.? what's the main motivation here? does anyone want me to find out all past breaking change list and we have to live with those changes by patching on top of open source?

This PR was included in 2.8.0 and didn't break the compatibility with 2.7.x because https://github.com/apache/pulsar/pull/4963 introduced a query param checkAllowAutoCreation in HTTP client.  Actually #4963 introduced a breaking change (allowAutoTopicCreationType=partitioned) so that the query param was added. The breaking change has been reverted in https://github.com/apache/pulsar/pull/5308 (allowAutoTopicCreationType=non-partitioned), but the client side changes are not reverted.
The C++ client tests should expose the breaking change because there was no checkAllowAutoCreation in C++ client before https://github.com/apache/pulsar/pull/11557. Unfortunately, the CI in master was accidentally broken at that time (see https://github.com/apache/pulsar/pull/11575) so the C++ client tests passed.
I agree that it's a breaking change. But this new behavior is also needed in some cases to differ a non-partitioned topic and a non-existent topic.
I prefer to add a new config to keep the compatibility for old version clients. Reverting this PR would also bring many breaking changes for those external systems that depend on Pulsar 2.8.0 or later. @rdhabalia @eolivelli
I will send an mail to dev and reference the discussion here soon.

Let's continue the discussion here: https://lists.apache.org/thread/88t1xxf68j092k09srdwyzj1tk4ml5n9


[BUG] Wrong multi-line input direction for RTL text

Describe the bug
In multi-line input, the RTL text does not have the correct direction. The single-line input is fine though.
To Reproduce
copy this sample RTL text as input
لورم ایپسوم

Single-line input ✅
https://github.com/user-attachments/assets/cbbc41be-1061-4328-95a8-0fab8140f76b
Multi-line input ❌
https://github.com/user-attachments/assets/d74abfa5-0d67-4f85-a376-ae62c1ed7259
Obsidian Version = v1.6.7
Operating System: Windows 11

Thank you for opening this issue! Should be resolved as of the latest version - please let me know if not. Providing text I could test with is very much appreciated :)


[Autocomplete] Remove excess option from property forcePopupIcon

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡
Property forcePopupIcon has an option auto that is not needed. I suggest removing this option. And simplify condition:
const hasPopupIcon = (!freeSolo || forcePopupIcon === true) && forcePopupIcon !== false;

to
const hasPopupIcon = !freeSolo || forcePopupIcon;

Motivation 🔦
I think that this change will simplify the code. It will become easier to understand.

It would break the logic.

What logic breaks?
I did a codebase analysis and nothing should break.


Handle project_salted_key_from_passphrase correctly with SWIG

Expected Behavior
The call to project_salted_key_from_passphrase returns a byte[] (correctly) and new_encryption_access_with_default_key expects a byte[].
Actual Behavior
The call to project_salted_key_from_passphrase returns a SWIGTYPE_p_uint8_t (wrong) Which can't be passed to new_encryption_access_with_default_key as it expects a byte[]. Therefore I've included a new_encryption_access_with_default_key2-inline-function to storj_uplink_second.i. It internally calls new_encryption_access_with_default_key but expects a uint8_t as import-parameter.
Help wanted
If someone knows how to let SWIG return a byte[] on new_encryption_access_with_default_key the inline-function in the interface-file could be removed.

This method is no more necessary with the latest Uplink-c, so this Topic can be closed.


Add service annotations to helm chart

Codecov Report

Merging #150 (5b7c956) into main (7a37254) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main     #150   +/-   ##
=========================================
  Coverage     93.34%   93.34%
  Complexity      603      603
=========================================
  Files           132      132
  Lines          2118     2118
=========================================
  Hits           1977     1977
  Misses          141      141

Flag
Coverage Δ

phpunit
93.34% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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 7a37254...5b7c956. Read the comment docs.

Thank you @naormatania


Hilite GC Stalls

Garbage collector stalls in Hilite take forever (minutes to hours) and are most likely related to Ag/Incremental stuff.

According to http://reedcopsey.com/2009/07/08/systemweakreference-internals-and-side-effects/ weakreferences have a significant performance impact when used extensively...
This is caused by the fact, that upon garbage collection the GC must scan all weakreferences in order to determine if they are still valid.
If an invalid weakref is found its internal pointer is set to null...
Since we use a bazillion of these this will definitely hit us...
Our incremental system massively relies on that construct so maybe we could find a better way of dealing with mods/etc going out of scope...
When replaced by strong references the inputs will force the existence of outputs and vice versa...
On the good side there would not be a significant performance penalty ....

Bug in GC:
http://blogs.msdn.com/b/maoni/archive/2015/08/12/gen2-free-list-changes-in-clr-4-6-gc.aspx
Fixed after installing hotfix KB3088956


Fixes #18 add wait for meta filewriter to be ready

Fixes #18

So whilst I'm sure this is required it's currently failing against S03 and getting stuck waiting for the the meta writer to be ready:
(python3.7) [ffv81422@ws455 python-artemis]$ camonitor BL03S-EA-EIGER-01:OD:META:Writing_RBV BL03S-EA-EIGER-01:OD:Capture_RBV BL03S-EA-EIGER-01:OD:META:ProcessConnected_RBV -S BL03S-EA-EIGER-01:OD:AcquisitionID
BL03S-EA-EIGER-01:OD:META:Writing_RBV 2022-02-03 13:13:09.757993 Done
BL03S-EA-EIGER-01:OD:Capture_RBV 2022-02-03 13:16:40.342380 Done
BL03S-EA-EIGER-01:OD:META:ProcessConnected_RBV 2022-02-03 13:13:09.758119 1
BL03S-EA-EIGER-01:OD:AcquisitionID 2022-02-03 13:15:37.829977 file.h5
BL03S-EA-EIGER-01:OD:AcquisitionID 2022-02-03 13:17:08.007233 001
BL03S-EA-EIGER-01:OD:AcquisitionID 2022-02-03 13:17:08.053712 file.h5
BL03S-EA-EIGER-01:OD:Capture_RBV 2022-02-03 13:17:09.338266 Capturing

I've spent some time trying to work out why (and fixed an issue with bit depth being set incorrectly in the process) but it's still failing.

This seems wrong
BL03S-EA-EIGER-01:OD:AcquisitionID 2022-02-03 13:15:37.829977 file.h5
BL03S-EA-EIGER-01:OD:AcquisitionID 2022-02-03 13:17:08.007233 001
BL03S-EA-EIGER-01:OD:AcquisitionID 2022-02-03 13:17:08.053712 file.h5

Firstly, nothing (e.g. file name, acquisition ID) should include .h5 on the end as this is just one section of the full file name (for the data writers and the meta writers).
Secondly, OD:FileName is synced to the more specific records to provide a simple interface. If you want more fine grained control you should set only the lower level PVs and not OD:FileName. I.e. it shouldn't be set OD:FileName and FP:FileName / OD:AcquisitionID. Assuming you want the acquisition id to be different to the file prefix, you can set OD:Acquisition and then FP:FileName. Setting META:FileName is also redundant if it is not different, but I don't think that should cause any harm.


Fork to add read only bloom filter and concurrent read only bloom filter

Again meant to open against our fork... GitHub UI is bad here.  Apologies.

Coverage decreased (-1.1%) to 92.523% when pulling 7d4edd8590387a98502815093bcfb9162b244155 on m3db:r/fork into 54e3b963ee1652b06c4562cb9b6020ebc6e36e59 on willf:master.


[Backup] Added Resume Protection functionality for Azure Virtual Machine

Description
Added Resume Protection functionality for Azure Virtual Machine
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[X] The PR title and description has followed the guideline in Submitting Pull Requests.

[X] I adhere to the Command Guidelines.

add to S169


Fix axis label of static_sim_plots

left panel: It should be indicated that the potential energy is in units of k_BT
middle panel: y-axis is currently labled with "simulation". Correct default label could be e.g. "probability density" or "frequency"
right panel: y-label "dhdpos" is not descriptive. Better label needed.

was solved


mvn install error

Hi, I checkout the code ,and run mvn clean install, then I got this error information:
[ERROR] Plugin org.jacoco:jacoco-maven-plugin:0.7.6-SNAPSHOT or one of its dependencies could not be resolved: Could not find artifact org.jacoco:jacoco-maven-plugin:jar:0.7.6-SNAPSHOT -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException

My network has no problem.
What should I do for this error?
Thanks a lot!

hi 0604hx, thanks for the interest. I merged a fix to the master branch. Please check it out. You might find more details in the merge commit.


Horusec is not reading my config-file.json

What happened: I am running Horusec in a pipeline using Docker. I have a Python script that receives the desired parameters and configurations, runs the scan, and shows the results. Two weeks ago it was working fine, but I ran it again yesterday and some issues appeared. First, it returned an error saying "open: /tmp is a directory". I just create a new branch and without any change in the code, the scanner started to work but currently, it is not taking my config-file.json
How to reproduce it (as minimally and precisely as possible): This is how I am building the command structure in my Python code:
def GetStartHorusecCMD(imageName, reportName, outputFormat, configFilePath):
    command =("docker run -v /var/run/docker.sock:/var/run/docker.sock -v $(pwd):/src "+imageName+
            ":latest horusec start -p /src -P $(pwd) --config-file-path "+configFilePath+" -o "+outputFormat)
    if outputFormat != 'text':
            command = command + " -O /src/Horusec/"+ reportName
   return command

And the variables that I am passing in my pipeline (running in an Ubuntu environment in GitHub) are:
imageName: "horuszup/horusec-cli"
reportName: "Horusec-21-10-07"
outputFormat: 'json'
configFilePath: '/src/Horusec/horusec-config.json'

Anything else we need to know?: This is my project structure:

Configurations showed using the --log-level=debug flag:

Environment:

Horusec version (use horusec version): We are downloading the latest version from Docker
Operating System: Ubuntu-latest (GitHub pipeline environment)
Network plugin / Tool and version (if this is a network-related / tool bug): N/A
Others:

Hello @NahuelHerr
Apparently your command is correct.
We will be analyzing to identify the possible reason and I will get back to you soon.
tnks for you report  :rocket:

Hello,
today is tried again and I still having the same behaviour.
First I tried to set a custom config file path, but I receive this error message:
docker run -v /var/run/docker.sock:/var/run/docker.sock -v $(pwd):/src horuszup/horusec-cli:latest horusec start -p /src -P $(pwd) --config-file-path /src/Horusec/horusec-config.json -o json -O /src/Horusec/Horusec-16-20211015115537.json
Error: open /tmp: is a directory

Later, I moved the horusec-config.json to the root and the scanner did not read it.  This script run the scan (in this image you can see a CONFIG_FILE_PATH variable, but I did not use it in the script for this try)

These are the History and the Manifest of the image:
Pulled image history:
IMAGE          CREATED       CREATED BY                                      SIZE      COMMENT
25f7cc6fa4d4   6 days ago    /bin/sh -c #(nop)  LABEL org.opencontainers.…   0B
<missing>      6 days ago    /bin/sh -c #(nop)  LABEL org.opencontainers.…   0B
<missing>      6 days ago    /bin/sh -c #(nop)  LABEL org.opencontainers.…   0B
<missing>      6 days ago    /bin/sh -c #(nop)  LABEL org.opencontainers.…   0B
<missing>      6 days ago    /bin/sh -c #(nop)  CMD ["sh"]                   0B
<missing>      6 days ago    /bin/sh -c chmod +x /usr/local/bin/horusec      0B
<missing>      6 days ago    /bin/sh -c #(nop) COPY file:9853eeb88a12f634…   27.7MB
<missing>      6 days ago    /bin/sh -c apk add git                          15.2MB
<missing>      6 weeks ago   /bin/sh -c #(nop)  CMD ["sh"]                   0B
<missing>      6 weeks ago   /bin/sh -c #(nop)  ENTRYPOINT ["docker-entry…   0B
<missing>      6 weeks ago   /bin/sh -c mkdir /certs /certs/client && chm…   0B
<missing>      6 weeks ago   /bin/sh -c #(nop)  ENV DOCKER_TLS_CERTDIR=/c…   0B
<missing>      6 weeks ago   /bin/sh -c #(nop) COPY file:5b18768029dab817…   1.85kB
<missing>      6 weeks ago   /bin/sh -c #(nop) COPY file:abb137d24130e7fa…   587B
<missing>      6 weeks ago   /bin/sh -c set -eux;   apkArch="$(apk --prin…   203MB
<missing>      6 weeks ago   /bin/sh -c #(nop)  ENV DOCKER_VERSION=20.10.8   0B
<missing>      6 weeks ago   /bin/sh -c [ ! -e /etc/nsswitch.conf ] && ec…   17B
<missing>      6 weeks ago   /bin/sh -c apk add --no-cache   ca-certifica…   4.81MB
<missing>      6 weeks ago   /bin/sh -c #(nop)  CMD ["/bin/sh"]              0B
<missing>      6 weeks ago   /bin/sh -c #(nop) ADD file:aad4290d27580cc1a…   5.59MB

Docker Hub manifest:
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
   "config": {
      "mediaType": "application/vnd.docker.container.image.v1+json",
      "size": 5965,
      "digest": "sha256:25f7cc6fa4d475b8c47baa69dfa94e12524c2c12b9f62187a30390e8eac13a98"
   },
   "layers": [
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 2814446,
         "digest": "sha256:a0d0a0d46f8b52473982a3c466318f479767577551a53ffc9074c9fa7035982e"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 1935099,
         "digest": "sha256:14df950e5a796f46eb6615169002a1c428bd908141de49fb35ec026c206e77aa"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 154,
         "digest": "sha256:86a31cc9e913427e8959328b7d290bdcc639a9f84c11956c33c0ce112788cf19"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 61283898,
         "digest": "sha256:f7a4137012260e097fc6b4bf6d75ba3b193acb399fb1276687303dea63ba519c"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 544,
         "digest": "sha256:53d92eaf14165f5a5883286b050c77b9c7022efbde954c3b7e96e92565515f0a"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 1018,
         "digest": "sha256:e701314a31132c239baf0de9d4922559fc419c445e13c9ce7ffd8b4518b4f98e"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 150,
         "digest": "sha256:5bea1be2ff281d99199cd048ef3bf1464615aec1ca9abfc20e73838913432dc0"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 8781498,
         "digest": "sha256:422f08ef0f6f67fcbd20597827d3f3375edb785cebd724a931fb7c0c383d66c1"
      },
      {
         "mediaType": "application/vnd.docker.image.rootfs.diff.tar.gzip",
         "size": 11203594,
         "digest": "sha256:7c540caa425da99de7975be1006840038e33a5f5b8ed715b9394ef0298dda777"
      }
   ]
}

After the error message, there is a stack trace or the usage from cli is showed?

In the report I can see that is using version v2.6.2

After the error message there is any stack trace as you can see:

I don't know if it can help, but I run the command this way. The GetStartHorusecCMD function is the one that I showed you here

I'm a bit confused now. How the output file was generated if there is an error?  On the message above you show a Github workflow configuration, the error does it occur in it? These error showed on last message (2) occurs on Windows or Linux?

Sorry, my bad. I did not tell you that I show you images of two different runs.
The scanner analyzes the code successfully if I do not include the --config-file-path option in the command. But, it does not read the  horusec-config.json file from the root. (In this comment I show where I put the file). That is why I can see the version in a report.
The error related to the /tmp directory occurs when I add the --config-file-path option to the command. When I do this the execution fails and any report is generated.
The REPORT_NAME env is empty because it will be generated dynamically in the previous step of the pipeline called Run GenerateReportName script. As you can see in this image where I am showing to you the Run Python script step, the REPORT_NAME has a value, I set the --config-file-path option, and the error occurred

If I do not include the --config-file-path to the command the scanner works, but it did not read the  horusec-config.json file from the root:

I have two different behaviors:

Using the --config-file-path option: when I use this option I move the config.json to the Horusec folder because there is where I want this file. When I do this I receive the error related to the /tmp directory.
Without the --config-file-path option: I leave the config.json in the root. I do not receive any error, but Horusec is not reading my config.json.

I tried  with the --log-file-path as you said and I got the same error message

If changing the path continue generating an error, can you try install the cli on workflow using the docs? Just to check if the problem is with the binary ou running inside Docker.

Did you try this?

This is great!!
I'm still confusing why this error is happening. Here is where we set the default log file path, I don't understand why in this scenario only os.TempDir() is used. But I think that its better to not fail the analysis if we get error on creating the log file anyway. I'will open a new issue to discover this bug.
Thank you very much for your help and patience, we really appreciate it.
We will release this patch very soon, on the next days.


Fix/declaration sejour  prestations

:tada: This PR is included in version 0.10.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


beef up FAI detection related parameter explanations – #110

This PR will resolve #110
@martinfleis If the language in the additions to simplify_network() are accurate & make sense, I'll cascade them into internal functions prior to merging.

@jGaboardi thanks for the deciphering!! i did a second pass on the parameter documentation - but now I think it needs a third 😅 as in: it is factually correct now but potentially too detailed / verbose

I'm fine with @anastassiavybornova version.

Do not merge. Still reviewing.

Won't, also due to

I'll cascade them into internal functions prior to merging.

@anastassiavybornova Would you like to review my suggestions or shall I commit them myself? (still need to update the other docstrings after that).

@jGaboardi reviewing them now!

@jGaboardi done

I'll merge this once CI is green.


[Bug Report] SHOW RETENTION POLICIES returns invalid formated duration

Bug report
System info:

Ubuntu 16.04.3 LTS
influxdb 1.3.5

Steps to reproduce:
> ALTER RETENTION POLICY test1 ON test DURATION 336h14ms

> SHOW RETENTION POLICIES ON test

name    duration     shardGroupDuration replicaN default
----    --------     ------------------ -------- -------
test1   336h0m0.014s 24h0m0s            1        true

> ALTER RETENTION POLICY test1 ON test DURATION 336h0m0.014s
ERR: error parsing query: invalid duration at line 1, char 47

Expected behavior: The duration returned by SHOW RETENTION POLICIES should be a valid formated duration, which can be used in a ALTER RETENTION POLICY query
Actual behavior: The duration returned by SHOW RETENTION POLICIES is not in all cases a valid formated duration

I think I can take this.


Icons Disappear After A Coded Selected Index Switch

I have a screen that hides the tab bar controller. The issue is that as a result the way we return to the original view controller is by calling self.tabBarController?.selectedIndex = 0 which works fine except that the icons for the screen we were on and the screen we swapped to completely disappear.
Here is what that looks like:

And The Way It Is Supposed To Look:

The issue is on this repository.
I may be doing something else that is causing the issue.

@askopin It looks like you were the last one to actually maintain this project, but I realize you may have moved on from Cuberto, but I figured this was still worth a shot. Any suggestions?

@EKKOING have you find solution for this problem

@mbhanen I don't think I did ever figure this one out. I ended up going with another tab bar for the final product.

@EKKOING  thanks, you used the same animation? if yes can you give me the api

Same issue

I have the same issue too. Did you find any solution ?


feat: Reading environment variables from forge test

Component
Forge
Describe the feature you would like
In certain circumstances, it would be very helpful if Forge tests could read pre-configured variables (either from foundry.toml or sourced from the bash environment) for conditional/context-specific logic, without the need to use the potentially unsafe vm.ffi cheatcode.
Additional context
The Seaport test suite uses vm.ffi with what is essentially a no-op to conditionally compile+deploy a set of contracts normally in order to surface stack traces and source code in the debugger when a specific Foundry profile is active.
We have included a warning about the dangers of using ffi, but it would be even better if we did not have to use it at all.

how about env_{string, uint,int}("string") -> {string, uint,int} cheatcodes?

Cheatcodes would be great!


MBM3.0.0 [Blood Magic]

[Blood Altar]  Unable to build third floor

Translate:The Altar of Blood on the next floor is missing a glowstone block.

You need to use Primal Voidstone Eye for the tier 3 caps

Thank you .


Parse unknown attributes as "custom" attributes.

Parse custom attributes with the grammar:
'@' type-identifier expr-paren?

We currently don't do anything with the custom attributes other than parse them, and diagnose them as unknown attributes. However, this is the basis for handling custom attributes of various forms.

@swift-ci please smoke test and merge


The plugin seem totally broken

I run on NodeBB 1.4.5 and the plugin seem broken.
The current configuration doesn't work and i have no more access to the plugin settings.
Can you follow the real NodeBB compatibility instead of using ^1.x in package.json?

By semver, every minor or patch version should be backward compatible. Technically plugin should not work with NodeBB 2.x.x.
The plugin was Ok with 1.4.4 where 1.4.5 just a patch version.

What error do you have in NodeBB logs?

I haven't log, but the route to admin/plugins/twitch-monitor is broken and i haven't the plugin in ACP menu.

Oh, in the console i have a warning:
Error has occurred, can not update initial cache for twitch monitor, error: [[error:invalid-event]]
(anonymous) @ nodebb.min.js:23

Without any reason, the plugin display channels now, but i have some REDIS error.
node_redis: Deprecated: The HMSET command contains a "null" argument.
This is converted to a "null" string now and will return an error from v.3.0 on.
Please handle this in your code to make sure everything works as you intended it to.

If you disable Twitch plugin, do you still see redis error?

No, the errors desapear when i turn it off.

The plugin uses internal NodeBB wrappers for work with Database (Mongo or Redis).
I'm not sure how actionable an issue from the plugin perspective.


Download eventLogFile feature

Add a popup menu on eventlogfile path to let users download Event Log file with one click.

Hi @Annubis45,
Thanks for this PR 🙏
Could you fill the CHANGES.md file and follow current convention for describing the new feature implementation ?
Also it could be nice to describe it with a gif in the 'how-to' page (I can do it if you want).
Two remarks regarding the feature:

could you add a cursor pointer to indicate the user the link is clickable ?
Remove "Copy Id" option or rename it to "Copy Path" if you think this can be useful

Thanks a lot !

Hi @Annubis45, Thanks for this PR 🙏
Could you fill the CHANGES.md file and follow current convention for describing the new feature implementation ? Also it could be nice to describe it with a gif in the 'how-to' page (I can do it if you want).
Two remarks regarding the feature:

could you add a cursor pointer to indicate the user the link is clickable ?
Remove "Copy Id" option or rename it to "Copy Path" if you think this can be useful

Thanks a lot !

I've implemented your remarks and done the gif in the how to.
I didn't know which url to put in the src of the img tag. Hope I used the right way.

@Annubis45  That's great  👏  thanks for the updates 🙏
You're right at the beginning the images were uploaded like that but now I'm pasting the image when editing the page directly from github, it saves some storage.
One last remark, it could be great to name the downloaded file by the eventLog id, it could be easier to make the distinction when downloading multiple files, what do you think ?

@tprouvot  I've implemented your suggestion. The default name file id  : 0ATxxxxxxxxxx_LogFile.csv.


App Launcher

We'll need an app that lists available apps and lets users launch them. Maybe we'll also need a standard way to exit a foregrounded app and/or launch the launcher?

Done


Stop burnt cNFTs from displaying in Assets page

Added an if statement to ensure that assets displayed on the Assets page are not burnt cNFTs

Circling back on this, any chance we could review?


access: access control problems

You cannot access Holding Pen as superadmin currently. Also, I've noticed a few problems in the access control module.

CFG_SUPERADMINROLE_ID  is not set properly due to application context issue, but exception is masked by a classic try..except: pass.
There is a quote too much in a SQL query.

I am submitting a PR shortly. Done

@jalavik thanks


feat: use accounts indexer for posts feed

Relates to #855

[x] add relationship.json file

Ultimately the AccountProfile widget receives a profile property. Maybe the Feed code can be cleaned up so the account relationship (which could be renamed profile) gets passed all the way down and post/item doesn't have profile_image, etc fields?

@gabehamilton may I ask you to verify that relationship.json file correctly updated

The relationship looks good

@calebjacob I'd like you to take a look at this changes


It's not obvious what a "Timer" is

Splitty seems to differentiate between the Timer Name and the Game Name and it's far from obvious what the difference is. Most other Timers simply either use a single field to describe the splits or split it into Game Name and Category Name. It doesn't look like the "Timer Name" is the Category Name though, so it's pretty confusing what this is supposed to mean. I'd suggest changing that or making it clear to the user what you are meaning with that.

You're right, I will add a mention for both I think. It allows someone to have multiple timers for the same run.

I added a tooltip feature in commit d3d0cb8. It will surely be expanded later.


Unable to read SQL Table with _date array: thread '' panicked at 'not implemented: _date',

What language are you using?
Python
What version are you using?
(connectorx:          0.3.2)
What database are you using?
PostgresSQL
What dataframe are you using?
Polars
Can you describe your bug?
I would like to query an SQL (Postgres) table that contains a _date columns (array of dates).
I use polars for the query  read_database
What are the steps to reproduce the behavior?
Create exemplary data in SQL (postgres)
create table test_polars (
		arr_date _date
);

insert into test_polars
values
		(array ['2023-01-01'::date,'2023-03-01'::date])
;

select * from test_polars;

Try to read data with read_database
import polars as pl

pl.read_database("select * FROM test_polars",url)

# Teseted with connectorx directly aswell
import connectorx as cx
cx.read_sql(url, query)

What is the error?
thread '<unnamed>' panicked at 'not implemented: _date', /__w/connector-x/connector-x/connectorx/src/sources/postgres/typesystem.rs:108:22
stack backtrace:
   0: rust_begin_unwind
             at /rustc/eb26296b556cef10fb713a38f3d16b9886080f26/library/std/src/panicking.rs:593:5
   1: core::panicking::panic_fmt
             at /rustc/eb26296b556cef10fb713a38f3d16b9886080f26/library/core/src/panicking.rs:67:14
   2: <connectorx::sources::postgres::typesystem::PostgresTypeSystem as core::convert::From<&postgres_types::Type>>::from
   3: <alloc::vec::Vec<T> as alloc::vec::spec_from_iter::SpecFromIter<T,I>>::from_iter
   4: <connectorx::sources::postgres::PostgresSource<P,C> as connectorx::sources::Source>::fetch_metadata
   5: connectorx::dispatcher::Dispatcher<S,D,TP>::run
   6: connectorx::get_arrow2::get_arrow2
   7: connectorx::arrow2::write_arrow
   8: connectorx::read_sql::read_sql
   9: std::panicking::try
  10: connectorx::__pyo3_raw_read_sql
  11: <unknown>
  12: _PyEval_EvalFrameDefault
  13: _PyFunction_Vectorcall
  14: _PyEval_EvalFrameDefault
  15: _PyFunction_Vectorcall
  16: _PyEval_EvalFrameDefault
  17: _PyFunction_Vectorcall
  18: PyObject_Call
  19: _PyEval_EvalFrameDefault
  20: _PyFunction_Vectorcall
  21: _PyEval_EvalFrameDefault
  22: _PyFunction_Vectorcall
  23: _PyEval_EvalFrameDefault
  24: <unknown>
  25: PyEval_EvalCode
  26: <unknown>
  27: <unknown>
  28: <unknown>
  29: _PyRun_SimpleFileObject
  30: _PyRun_AnyFileObject
  31: Py_RunMain
  32: Py_BytesMain
  33: <unknown>
  34: __libc_start_main
  35: _start

Hey @Buedenbender. I solved a similar issue awhile back with this PR. It was for implementing varchar arrays but i think the strategy would work for date arrays too if you're interested in making a PR. Otherwise I'm happy to take a crack at this.

Hi @Jordan-M-Young unfortunately I will not be able to create PR.
I would be more than happy to buy you a coffee if you could create one and implement it. I know a few other folks who are waiting for this.


Postal worker keeps sending request to http endpoint

Describe the bug
Hi, I'm new on Postal. And I wanna try to receive email from http endpoint.
I found weird behavior with receiving emails from HTTP endpoint. I already setup HTTP endpoint and its route. Then I send email from my personal email to postal routes address.
It is successful and I got the mail to my endpoint. BUT, it keeps sending me the message. I checked the worker logs, and it said something like this:

It's like it started to scheduler to send it again or something.
To Reproduce

Create Http endpoint
Create routes using http endpoint that you created before
Send email to the routes address

Expected behaviour
Get message on http endpoint every 5 minutes, event tho http endpoint already received it before.
Screenshots
And this is my setup:

This is log on my http endpoint:

Environment details

OS: Installed postal on ubuntu 20
Browser chrome
Version 2.1.0

So you sent an email message to an address handled by Postal and received several requests to your ngrok?

So you sent an email message to an address handled by Postal and received several requests to your ngrok?

Yes, that's what exactly happened to me. I already followed the documentation to give 200 OK to the response if I got the message.
I checked on Incoming Message and I have multiple identical messages received, 1 message / 5-10 minutes. But those multiple messages weren't sent from my personal email, I checked and it just sent one.
What makes it happen? I was thought maybe it because of this:

But I already give 200 OK as a response.

that should only be if it fails though, you should see your message logged in the messages tab in Postal and then see what happened to it on the right hand side?

that should only be if it fails though, you should see your message logged in the messages tab in Postal and then see what happened to it on the right hand side?

Do you mean this? These messages are all the same

you should be able to click on those messages for more details

you should be able to click on those messages for more details

Yes, and they are exactly the same. It becomes weirder today, the postal couldn't read the message as success, because it tried to send me Mail Delivery Failed multiple times today.

Is this have something to do with misconfiguration DNS?

I almost forgot I found misplaced words on http endpoint format field. When I choose "Delivered as raw message", instead of raw message I got the hashed one and vice versa

Anyway, I will close this issue since I solved this. I guess it was because of misconfiguration. I have google mail MX configuration on domain A, and I was moved to domain B which there is no MX configuration before, and it worked fine now.


Allow installing CLI in custom dir without using sudo

Current dependencies on/for this PR:

main

PR #113   👈

This stack of pull requests is managed by Graphite.

This PR still needs to be thoroughly tested & update PowerShell appropriately.

LGTM, but I do want to try giving it a run first

Please do! I'm leaving this a draft until we can make sure both install scripts work for Godot.
Only potential problem I see is if for some reason you can't write to the BIN_DIR, it will hang on sudo indefinitely.

@jog1t @AngelOnFira  Let me know if this works for you & is ready to merge

Merge activity

Dec 24, 12:12 AM: @@NathanFlurry started a stack merge that includes this pull request via Graphite.


Custom event "grounded" now "ground"?

Hey guys!
After installing kaboom@next the "grounded" custom events didn't work anymore.
Just took a look at the codebase to see that the custom event being triggered from body is now 'ground'.
player.on('grounded', () => ...) // doesn't work
player.on('ground', () => ...) // works

Docs say it should be 'grounded'..

Hey! Sorry the docs is a bit desync now, the doc / website is being reworked (the new one is 100% generated) and will be shipped next week with a kaboom stable release. Before that please clone the repl and npm run setup npm run dev to see the latest API on @next, or use this temp link I just setup: https://kaboom2000.slmjkdbtl.repl.co/


onSSR causes injection error when container top-element is identical to content

I have a function that post-processes markdown text to inject images. It will only run correctly on the client, so I use placeholders on the server. This function is called htmlImageIdReplacementHack.
let post =
;
return <NoSSR key={_id} onSSR={post}>{post}</NoSSR>

This code throws the following warning:
Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server:
 (client) ta-reactid="56">

<div style="width

If I use onSSR={Loading...} instead everything is fine.

I found the cause of the issue:
Apparently the onSSR block is evaluated on the client too and it only works if the onSSR block yields the same result on the server and on the client. I added a weird flag to my htmlImageIdReplacementHack function and then use Meteor.isServer || simulateSSR in there, but that sounds far from ideal to me.

To resolve this in a generic way, how about requiring that component props (onSSR), be wrapped in a callback so they aren't evaluated unless it's needed?


Create Haruhue.json

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

@eddiejaoude @Pradumnasaraf

Please do not tag maintainers like that, we already get the notification, adding more notifications does not help. It was only a few minutes since you raised the PR, we all live in different timezones, please be patient, we will get to your PR soon.
Please read the contributing guide https://github.com/EddieHubCommunity/BioDrop/blob/main/CONTRIBUTING.md

Please do not tag maintainers like that, we already get the notification, adding more notifications does not help. It was only a few minutes since you raised the PR, we all live in different timezones, please be patient, we will get to your PR soon.
Please read the contributing guide https://github.com/EddieHubCommunity/BioDrop/blob/main/CONTRIBUTING.md

Sorry about that

Please remove the changes to the file TobySolutions/testimonials - this does not relate to your Profile or a testimonial given by you or to you.

I already did that

I already did that

You deleted the file from someone else's profile, for your PR to be accepted please remove your changes to the file (not delete the file) from your Pull Request, there should be no changes over than your json file in the "files changed" tab, please check again
Here is a screenshot to help

Tried undoing it but it was not working and frustrating, I made a new one:
https://github.com/EddieHubCommunity/BioDrop/pull/10171


fix(date-time): align props date time and introduce default-value

Describe pull-request
Removed the slots for label/helper and created props for them instead, also introduces the prop
default-value to allow the user to select a default time to be displayed.
Solving issue
Fixes: AB#2837
How to test

Go to storybook link below.
Check in Components -> Date-time
Check that the controls regarding label/helper works as inteded.
Try out the new custom/now value for default-value.

Screenshots
Additional context

Question: Is it better to use the value prop to set the default value?

Props format and defaultValue - are they dependent on each other and if how?
format: prop looks like it is not used - but maybe you wanted to discuss it more in the group?
defaultValue: Do we need to specify the format that is expected in the comment of the prop so users know in which format they need to pass the value?


Add Swift 4 env var to Travis

Description

Motivation and Context

How Has This Been Tested?

Checklist:

[ ] I have submitted a CLA form
[ ] If applicable, I have updated the documentation accordingly.
[ ] If applicable, I have added tests to cover my changes.

Codecov Report

Merging #53 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #53   +/-   ##
=======================================
  Coverage   62.54%   62.54%
=======================================
  Files           5        5
  Lines         259      259
=======================================
  Hits          162      162
  Misses         97       97

Flag
Coverage Δ

#Credentials
62.54% <ø> (ø)
: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 2b17345...620274a. Read the comment docs.


no matching function for call to 'LiquidCrystal_PCF8574::createChar(int, byte [8])'

I defined the character as a byte
byte cM[8] = {B01100, B10000, B10000, B01100, B10001, B01010, B00100, B00100};
initialise in setup with
lcd.createChar(0, cM);
When I compile I get this error
no matching function for call to 'LiquidCrystal_PCF8574::createChar(int, byte [8])'

The createChar() function in the latest published version had the problem to use a int[8] instead of a byte[8] parameter.
In the current master this has been fixed already.
Will be fixed in the next version. You can use the master from github, change the array to int[8] for now..

The createChar() function in the latest published version had the problem to use a int[8] instead of a byte[8] parameter.
In the current master this has been fixed already.
Will be fixed in the next version. You can use the master from github, change the array to int[8] for now..

Next version is 2.0.0 and has this interface change as requested.
A PROGMEM version will be available vor AVR processors as well #22


Alternate links in Online Learning page

Fixes for @Jaqster 's #6749.

[x] Links for "Streaming" header
[x] Alternate individual stream links
[x] Make stream titles into links - someone needs to check that change.

Still need an on hover CSS class for the stream and resource text links.

@shakao fixed this in #6754


Provide a method to wait until remote configuration is loaded

Provide a method to wait until remote configuration is loaded

Added
IWorkbenchConfigurationService.whenRemoteConfigurationLoaded()


Passing a version_id to generate_blob_sas creates a SAS

It should be made clear in the documentation that when using generate_blob_sas to fetch specific versions of a document, the returned SAS is not valid unless the version id is appended to the resulting query string in the format:
sas_that_works = f'{returned_sas}&versionid={versionid}'
where versionid exactly matches the created date/time of the blob in YYYY-MM-DDTHH:MM:SS.NNNNNNNZ format.

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

ID: bc13eca7-8c35-456c-cb38-016d2fa40df5
Version Independent ID: d89dc470-199e-fe2a-e8ba-ec35c73e1bc4
Content: azure.storage.blob package
Content Source: docs-ref-autogen/azure-storage-blob/azure.storage.blob.yml
Service: storage
GitHub Login: @lmazuel
Microsoft Alias: lmazuel

Thanks for the feedback @piercsi . We will investigate and get back to you asap.

Hi @piercsi Simon, thanks for the request. While it is true that a SAS generated with a version_id can only be used on that specific version of the blob, I'm not sure documenting this on the result of the generate_blob_sas is the right thing to do. The resulting SAS token is intended to be used with an API in the SDK where you would already have to specify the version_id as an argument to that operation. For example:
blob_client = BlobClient(..., credential=<sas_token>)
props = blob_client.get_blob_properties(version_id='YYYY-MM-DDTHH:MM:SS.NNNNNNNZ')

In this case, you would not want to add the versionid query param to your SAS token as get_blob_properties will be adding it to the API call for you and you'd actually end up with two versionid which would be invalid. So ideally, when using the SDK, you should never have to add the versionid query parameter yourself even if you have a SAS for a version.

I don't disagree with the rationale for how it works; my suggestion is that it could be explained better in the documentation somewhere.
The confusion (in opinion) is that when using a SAS, generate_blob_sas creates all the query string parameters for you, except the versionid, even when you supply a version_id parameter. It feels counterintuitive.

Hi @piercsi Simon, sorry for the delay but we've taken your feedback and merged #29802 to update the documentation to include:

Note that the 'versionid' query parameter is not included in the output SAS. Therefore, please provide the 'version_id' parameter to any APIs when using the output SAS to operate on a specific version.

The online documentation is auto-generated from the code and will update within the next couple of weeks. Thanks!


Wrong Values with 1.6.13

After updating from 1.6.12 to 1.6.13 the production values are way too high, gui_inverter_power showed like 14000w, even the device has a maximum output of 10000w... after reverting back to 1.6.12, everything is fine again.
Hardware: SENEC HOME V2.1 with 10kw Storage (with external Kostal inverter)

should be fixed within the hour. Sorry.

Fixed with v1.6.14.
Checks and autodeplyment in progress. Once completed you can either wait for NPM to supply the version or update via iobroker using Github.


[BUG] Pod is removed from catalyst builds without adding it to catalyst_configuration

Describe the bug
Hey, we're using a local pod that is always removed from the catalyst build even if we don't specify it in catalyst_configuration. The pod has StoreKit in its name and we suspect an over-eager name matching causes this unnecessary removal.
In a previous version of this script, this line was the main offender in the uninstall function:
lines_to_replace = snippet.filter_lines do |line| line.include? "#{key}" end.to_set.to_a
which we remedied locally by requiring an exact match:
lines_to_replace = snippet.filter_lines do |line| line.match "\/#{key}" end.to_set.to_a
I didn't find the relevant part in the new codebase.
We fixed the issue by renaming the local pod but maybe this is something you'd like to take a look at. Thanks in advance!
Podfile
Relevant part:
pod 'MKStoreKit', :path => '../MKStoreKit'
Environment

cocoapods-catalyst-support => 0.1.2
Ruby version [e.g 2.6.0] => 2.7.2
Cocoapods version [e.g 1.10.0] => 1.10.1
Xcode version [e.g 12.2] => 12.4

Hi @tamasjager , the line you mention should be in native_target.rb but this is something that should definitely be solved.
So rather than checking if Foo is included in the bash file your fix tries to match /Foo to avoid fake matches like MKFoo, for instance. Is that right?

Yes. In the meantime my colleague made a PR with the same fix https://github.com/fermoya/cocoapods-catalyst-support/pull/23.

Thanks @tamasjager . I'll release a version shortly, thanks for the fix

version 0.1.3 released 🚀


Break out / duplicate apm rebuild here

For projects using Atom Shell that are not Atom, using the "Atom Package Manager" to build native modules is a bit strange. It might be useful to have a core component of Atom Shell be a tool to build native modules that is not so deeply connected to the Atom project to make packaging easier for other framework users, perhaps allowing for building a dist of atom-shell (e.g. from a branch) and rebuilding specified modules to match it in one go. I'm curious to hear thoughts on this from @atom/core as well as other people trying to build on this framework.
cc @paulcbetts who brought this up in conversation yesterday

We already have electron-rebuild, and there is no mention of apm in the docs, so I think we are done here.


[Bug]: Switching databases within session management may result in errors

ODC version
odc422
OB version
not have
What happened?

What did you expect to happen?
Switching databases without reporting errors
How can we reproduce it (as minimally and precisely as possible)?
Switching databases within session management
Anything else we need to know?
No response
Cloud
No response

Fixed In Commit 80ec85e98864e0a0b2b12da022170ee2433d0e0a
------
晓康
Fri Oct 20 17:13:08 2023 +0800

pass


Logitech Powerplay LED breathing and cycle are broken

The only modes that work are solid color and off. The breathing mode will not return any error, but will turn the led off, the cycle mode will return an error.
ratbag raw: hidpp write:  11 07 0b 38 00 0a 26 a2 69 13 88 00 00 00 00 00 01 00 00 00
ratbag raw: hidpp read:   11 07 ff 0b 38 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00
ratbag error:     HID++ error from the device (7): ERR_INVALID_ARGUMENT (02

I am not sure about the firmware in this device, perhaps it is broken, I'll try to update when I get a chance.

It's not a firmware issue.

It's not a firmware issue.

I can confirm this issue as well

I can confirm this issue as well

Okay, maybe they are not broken. It works for me when the no device is connected. The profile allows an alternative effect to be configured, perhaps the powerplay is using that when something is connected.

Any resolution to this? I can confirm the same issue for me. I don't get an error when putting it in any mode but the LED just turns off. Solid is the only working mode. Any idea how can I get this working for cycle?


wire/udata: Remove ttl field from UData

TTL field is removed in favor of other caching methods as research has
shown that there are better alternative caching methods than ttl based
caching.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 18 (44.44%)  changed or added relevant lines in 4 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.01%) to 54.444%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

blockchain/indexers/flatutreexoproofindex.go
1
3
33.33%

blockchain/utreexoviewpoint.go
0
4
0.0%

wire/udata.go
6
10
60.0%

Files with Coverage Reduction
New Missed Lines
%

database/ffldb/blockio.go
4
93.68%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
26192

Relevant Lines:
48108

💛  - Coveralls


getting could not load the system's DNS configuration, using synchronous, blocking fallback error

I am getting the following error when error reporting is turned on, irrespective of whether the db query is insert/update/select/delete, even though the expected operation is happening,
Warning: Could not load the system's DNS configuration, using synchronous, blocking fallback in /home/chat2/webapps/app-chat2/public_html/easeampmysqlredis/vendor/amphp/dns/lib/Rfc1035StubResolver.php on line 252
The php code is being run on ubuntu linux server and with php 7.4. Do we need to explicitly define dns resolver ip addresses (either google or opendns etc...), to fix this error? if yes, I would request you to please suggest with a code sample.
thank you

@raghuveer I've transferred your issue to the correct repository. The systems configuration is usually automatically detected and used. The warning appears if loading the configuration fails, but TBH doesn't currently indicate the reason for that. The fallback is using the native resolver, but it can't resolve DNS names non-blocking in that state, so it issues a warning.
Could you have a look at the exception caught and provide that information here? https://github.com/amphp/dns/blob/299511d7e6458d14e2881eccd23caca204b8e750/lib/Rfc1035StubResolver.php#L249
A new release improving the warning seems appropriate.

Please try with dev-master, I've pushed https://github.com/amphp/dns/commit/659bad6bba93aa20548f8fc797d108114ff722e4.

Thanks @kelunik, tried running amphp/dns package from dev-master as you suggested,
my server setup:
Ubuntu 18.04
PHP v7.4.14 with PHP-FPM and Nginx before Apache web server
ran sample code from https://github.com/amphp/dns,
`require 'vendor/autoload.php';
ini_set('display_errors', 1);
ini_set('display_startup_errors', 1);
error_reporting(E_ALL);
use Amp\Dns;
use Amp\Loop;
Loop::run(function () {
$githubIpv4 = yield Dns\resolve("github.com", Dns\Record::A);
pretty_print_records("github.com", $githubIpv4);
$googleIpv4 = Amp\Dns\resolve("google.com", Dns\Record::A);
$googleIpv6 = Amp\Dns\resolve("google.com", Dns\Record::AAAA);

$firstGoogleResult = yield Amp\Promise\first([$googleIpv4, $googleIpv6]);
pretty_print_records("google.com", $firstGoogleResult);

$combinedGoogleResult = yield Amp\Dns\resolve("google.com");
pretty_print_records("google.com", $combinedGoogleResult);

$googleMx = yield Amp\Dns\query("google.com", Amp\Dns\Record::MX);
pretty_print_records("google.com", $googleMx);

});
`
got the following error,
Warning: Could not load the system's DNS configuration; falling back to synchronous, blocking resolver; Amp\Dns\ConfigException: Could not read configuration file '/etc/resolv.conf' (2) file_get_contents(): open_basedir restriction in effect. File(/etc/resolv.conf) is not within the allowed path(s): (/home/chat2/webapps/app-chat2:/var/lib/php/session:/tmp) in /home/chat2/webapps/app-chat2/public_html/amphp-dns/vendor/amphp/dns/lib/Rfc1035StubResolver.php on line 260
Fatal error: Uncaught Error: Call to undefined function pretty_print_records() in /home/chat2/webapps/app-chat2/public_html/amphp-dns/index.php:13 Stack trace: #0 [internal function]: {closure}() #1 /home/chat2/webapps/app-chat2/public_html/amphp-dns/vendor/amphp/amp/lib/Coroutine.php(118): Generator->send() #2 /home/chat2/webapps/app-chat2/public_html/amphp-dns/vendor/amphp/amp/lib/Success.php(41): Amp\Coroutine->Amp{closure}() #3 /home/chat2/webapps/app-chat2/public_html/amphp-dns/vendor/amphp/amp/lib/Internal/Placeholder.php(40): Amp\Success->onResolve() #4 /home/chat2/webapps/app-chat2/public_html/amphp-dns/vendor/amphp/amp/lib/Coroutine.php(151): Amp\Coroutine->onResolve() #5 /home/chat2/webapps/app-chat2/public_html/amphp-dns/vendor/amphp/amp/lib/Loop/Driver.php(126): Amp\Coroutine->__construct() #6 /home/chat2/webapps/app-chat2/public_html/amphp-dns/vendor/amphp/amp/lib/Loop/Driver.php(72): Amp\Loop\Driver->tick() #7 /home/chat2/webapps/app-chat2/public_html/amphp-dns/vendor/amphp/amp/lib/Loop.php(95): Amp\Loop\Dr in /home/chat2/webapps/app-chat2/public_html/amphp-dns/index.php on line 13

@kelunik is there any alternative solution for amphp/dns to access /etc/resolv.conf without disabling open_basedir restrictions?
What are other options?
your support will be really helpful,
thank you

@kelunik
is there any alternative solution for amphp/dns to access /etc/resolv.conf without disabling open_basedir restrictions?
I did try the example at https://github.com/amphp/dns/blob/master/examples/custom-config.php, by providing a numeric array of hostnames,
$argv = ["microsoft.com","google.com","yahoo.com"];
With google offered recursive dns servers being used in the custom config, I see available list of IPv4 and IPv6 addresses in the result, for whichever domain name is given in the input, I would like to know about how this custom config be consumed by all dependencies of amphp/mysql library like amphp/socket, that inturn uses amphp/dns library?
your inputs and support will be really helpful,
thank you

@raghuveer You've found the correct example. Dns\resolver(new Dns\Rfc1035StubResolver(null, $customConfigLoader)); sets the given configuration globally, so it's automatically used by all packages like amphp/socket and amphp/mysql.

Thanks a lot @kelunik it worked, I will try including this in my application :)

What are the suggested number of attempts? the number in the sample code is 3.
I did try adding more recursive DNS Servers (like 2 IPv4 Addresses of opendns.com), to the existing Google Recursive DNS Server IPv4 Address (<IP_ADDRESS>) and some IPv6 Address
`$customConfigLoader = new class implements Dns\ConfigLoader {
public function loadConfig(): Promise
{
return Amp\call(function () {
$hosts = yield (new Dns\HostLoader)->loadHosts();
        return new Dns\Config([
            "<IP_ADDRESS>:53", "<IP_ADDRESS>:53","<IP_ADDRESS>:53","[2001:4860:4860::8888]:53"
        ], $hosts, $timeout = 5000, $attempts = 3);
    });
}

};
Dns\resolver(new Dns\Rfc1035StubResolver(null, $customConfigLoader));
`
is this ok? please share your inputs,
thank you

That depends on your needs on speed and reliability. I think 2 or 3 are the default. The total timeout will be attempt * timeout I think.

I am using the defaults as per your example, thank you @kelunik


Increase Consistency in Navbar

To make the color more interactive in Navbar UI . The font sizes could be adjusted assign it to me for Hacktober . @anjalit03

Sure!! please make sure the changes align with the current website design and style :)


Tried to follow iOS steps, app just crashes on start

Hi! I tried to follow all the steps in this repo, because I wanted to try codegen with typescript (which is supported since react-native-codegen 0.0.13). I managed to get the app compiling, but now when it starts it just immediately crashes.
The only difference so far I could spot is the react-native version, on this repo it is pointing to a nightly that I could not find and I had to replace with 0.0.0-20220309-2009-538636440 (instead of 20220309-2009-538636440).
Here is a repo with all my work so far:
https://github.com/ospfranco/awesome_turbo_module
Any idea what might be wrong?

A couple other questions:

Can this work on a non-nightly version? I tried 0.68 and got compilation/pod install errors
The non-nightly version also seems to contain some default functions to handle app initialization (such as initializing RCTImage and RCTNetwork), but I'm not sure how they are supposed to work with the code in the repo

I just noticed on the run.md file there a some notice of incompatibility with Hermes and that it needs to be built from source. I added the changes but the app still crashes (at least with a different error)
Is there a way to make this work on 0.68 release? and how?

I just tried the the version officially published in the documentation 0.0.0-20220201-2008-79975d146 and it compiles. However my module was not being properly loaded, and as is turns out, it was because Xcode was not referencing the folder correctly, so it was not picking up my class. I had to delete and "Add files to [project]" again for Xcode to pick up my files.


Remove src_addr from EXT-ROUTER

We've found that this attribute contains a very wide range IPs, which doesn't seem to be what you'd expect for a router.  E.g. we're seeing the entire space of IPs in various ranges, like <IP_ADDRESS>/24 and others for the same entity.  Our suspicion is that this value is the src_addr of TCP flows / devices that the router may be talking to / have entries in its MAC table, etc.
This is problematic for us as the tag will have a lot of churn (e.g. we're seeing millions of changes per minute for an account with just 250 routers) and cause excessive writes to the entity store (which works under the assumption of storing objects that don't change that often).
We're removing this for now so that we can re-enable the entity type.
Relevant information
Describe what you have done and any details that you think are relevant or that you might want to discuss with us.
Checklist

[ ] I've read the guidelines and understand the acceptance criteria.
[ ] The value of the attribute marked as identifier will be unique and valid.
[ ] I've confirmed that my entity type wasn't already defined. If it is I'm providing an
explanation above.

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

Merging as the CLA bot seems to be acting up again.


Check for FabricSynchronization condition on Aggregator device

Simple test script to verify FabricSynchronization condition on the Bridged Node device type.
Spec [bits under the in-progress,matter-fabric-synchronization condition]: https://github.com/CHIP-Specifications/connectedhomeip-spec/blob/master/src/device_types/BridgedNode.adoc
Currently this test script does not pass, because the fabric-bridge-app lacks some features.

Currently this test script does not pass, because the fabric-bridge-app lacks some features.

I would split this up into yaml and all the CI test stuff separately so that you don't block getting the yaml test in

@tehampson I have created a separate PR #34626. Unfortunately @arkq is on holiday and I'm not able to update this PR.


dvizz fails to start if no service is running

Starting dvizz on a docker swarm w/o any running service will result in a panic:
$ docker run -v /var/run/docker.sock:/var/run/docker.sock -p 6969:6969 -it --rm liske/dvizz
Starting WebSocket server at port 6969
Starting WebSocket server
Starting event sender goroutine...
panic: interface conversion: interface {} is nil, not []main.DService

goroutine 8 [running]:
main.convServices(0xa98588, 0x0, 0x0, 0x0, 0xa98588, 0x0)
        /dvizz/converters.go:67 +0xe0
main.publishServices(0xc420114090)
        /dvizz/main.go:108 +0x80
created by main.main
        /dvizz/main.go:50 +0x14e

@eriklupander I'm not a go developer - maybe you could give it a look?

@liske I'm on it.

I've added some nil and empty-slice checks as well as some unit tests.


Fix incorrect JID resource with Websockets

This commit makes the connect function check the provided JID for a resource. Without this, Candy connects with the default resource of “Candy”, then causes a stream error when sending the first stanza with a from containing the full JID.

Changes Unknown when pulling f4b6c6f595ffefe67add99931d47ad050f430cd6 on bklang:dev into ** on candy-chat:dev**.

I think you need to strip the resource from the ChatUser too, no?


Add immutable ID header to Get requests

This allows using immutable IDs for Exchange objects. It does not add this header to put requests as we don't record the IDs of restored objects anywhere.
May slightly increase performance of events backups as
it now sets the delta query page size to 200 like with
other requests

Does this PR need a docs update or release note?

[ ] :white_check_mark: Yes, it's included
[ ] :clock1: Yes, but in a later PR
[x] :no_entry: No

Type of change

[x] :sunflower: Feature
[ ] :bug: Bugfix
[ ] :world_map: Documentation
[ ] :robot: Supportability/Tests
[ ] :computer: CI/Deployment
[ ] :broom: Tech Debt/Cleanup

Issue(s)

closes #2861

Test Plan

[x] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

still need a way to force a full backup with this change (see linked issue comments for why we need a full backup or extra work)

still need a way to force a full backup with this change (see linked issue comments for why we need a full backup or extra work)

Can we enable this only for newer repositories? Is there a mechanism for us to detect a repository created after this change was introduced? If not - we should add that.

still need a way to force a full backup with this change (see linked issue comments for why we need a full backup or extra work)

Can we enable this only for newer repositories? Is there a mechanism for us to detect a repository created after this change was introduced? If not - we should add that.

@ashmrtn @ryanfkeepers - here's what I was thinking - https://github.com/alcionai/corso/pull/3161

@vkamra @ryanfkeepers this should be ready for review.
I'v added a non-user-facing feature flag that can be used to fetch immutable IDs. Note that right now it's only safe to enable this flag if either of the following are true

this will be a full backup
this will be an incremental backup and the base backup also used immutable IDs

Manual testing showed we got mutable IDs for a backup and an incremental on top of it with the flag set to false (no changes beyond this PR). Forcing the flag to true (by setting in the Default() options c'tor) caused immutable IDs to be used for a backup and an incremental on top of it


Home page refactoring

I'm not a big fan of the current home page.
I quickly designed a prototype: the whole idea is to make obvious what the app is here for.
Tell me what you think.

Hi @monsieurtanuki
That's a very good time to discuss this, as we are trying to restart the discussions about what the app is for, how it's different from the existing OFF apps etc. We had a lot of discussions with @PrimaelQuemerais last year, but a lot of things have changed (e.g. all the Personal Search with the attributes etc.). So it would be great to revisite this again. :)
The initial ideas and plan are on: https://wiki.openfoodfacts.org/Project_Smoothie
Something we would like to do is to put personalization, and personal uses of the product data, at the core of the app. Our idea is to have different "modes" that users can switch to:

a "Choose" mode, where the goal is to find / select the products that corresponds the best to the user.
a "Organize" mode, where users can create lists of products they need to buy or have already bought
a "Track" mode so that users can see how much they eat, how good the Nutri-Score etc. of the food they eat evolves over time
a "Contribute" mode, for users who are more interested in adding new product data and photos on OFF.

The core functions of the app are the same in the different modes: you can scan products, search products, put them in lists etc. but they way we present the data is very different.
For instance when an user scan a product in "Choose" mode, we show the user in the scan card how well the product matches the food preferences he selected.
When the user scan in "Organize" mode, what we show instead is whether the user already has this product in his inventory or not (and where it is, how many there is, when is the expiration date etc.). And the actions we offer are to indicate if we are adding the product or removing it.
When the user is in "Contribute" mode, we can show instead whether we need fresh pictures for this product or not.
So each mode functions in the same way: scanning, product cards, product pages, lists of products, but with different information shown and actions proposed.
The app would remember the last mode used by the user, and when it opens, it would go straight to that mode.
What you are proposing would work very well for the Choose mode I think.

@stephanegigandet Very interesting indeed, as my point was to make things easy to understand. I know that as an end-user, I would be tempted to click on each item of the home page I prototyped. And you're right, I'm closer to the "Choose" mode - which may be very similar to the current Android app.
As for your 4 modes, I think this is very ambitious to presume that the end-user won't get confused. Perhaps 4 different apps with the same core would make more sense, and would be easier to "sell". Working on the UX (with personas?) seems very important right now.

We should definitely start with Choose. We can release a first app with it. And we can add the other use cases after, and try to find the best way to organize / surface them.

@stephanegigandet

We should definitely start with Choose. We can release a first app with it.

Can I interpret that as a GO! to merge my prototype into smoothie and change its home page?

I think it's very good when we revise the "homepage".
But how is the one proposed by @monsieurtanuki planned?  As a stand-alone page from which all navigation starts. Or just an overview, so instead of the choosepage.

@M123-dev In my mind my prototype was the home page. The current "choosepage" has no sense anymore, and would be recycled into a "categorysearchpage", or something like that. And from there, with a back button, you go back to the homepage.

I have a suggestion.Something like a kind of personalized greeting. What do you think of it

In terms of routing structure, it sounds very good to me: @monsieurtanuki 's prototype leads to all the useful pages / features of the app, it would make sense to have them on the home page. How exactly to display those things etc. could be discussed and adjusted later. (or we could have a first discussion now)
One thing I like a lot is that the different buttons are personalized with my history: the last products I saw, searches I made, lists I used. It makes the page a bit crowded though (lots of text). Maybe some of those buttons could be done a bit differently (like showing product images for the food product history instead of their names).
As I'm typing this comment, I just saw @M123-dev 's proposal. I like the "Good Morning, Marvin". :) Making the app personal is definitely a good idea, that would make the app different of the existing OFF apps.

@stephanegigandet @M123-dev As long as we agree on the structure, we can move on and I can start developing, can't I?
I like my prototype display because it is homogenous (and it took me 30 minutes to build it), but of course the target is to be less verbose and include more pictures, obviously for the "food ranking parameters" and the products history.
Regarding personalization, that really deserves a specific new github issue regarding different aspects like onboarding, mandatory login or not, and endless translation questions (except in English which is rather gender-neutral and politeness-neutral) (as opposed to French's vous/tu and German's Sie/du).

As long as we agree on the structure, we can move on and I can start developing, can't I?

I think so. :)

Done in #143


Overwriting custom plugin

I use a forked version of one of the plugins that is in the alcatraz list (with the same name). It seems that whenever I open xcode, the copy of the plugin I installed gets overwritten by the one alcatraz wants to use.

Hmm yes, you could maybe try renaming the manually installed plugin folder?

Ah. That works. I had tried that yesterday, but was trying a bunch of other things at the same time, and so it must have conflicted with something else I was doing so it didn't seem to help.


Fix wrong Y axis scale in Aim UI when metric has infinity values

The Aim UI knows how to deal with such values but we were not mapping them correctly in the encoded result, as MLFlow's database storage uses MaxFloat64 instead of infinity. This PR adds a mapping back from MaxFloat64 to proper infinity.
Fixes #489

I wish I could ask for a unit test here, but this whole thing looks like its up for refactor soon.

indeed it is 😄


Enhance common module code documentation

Issue link

https://issues.redhat.com/browse/RHOAIENG-13958
What changes have been made

Enhanced common module code documentation
Verification steps

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[x] Testing is not required for this change

I'm making a few changes in this repo's settings:

We are dropping the merge queue feature as it seems it's not properly maintained with major issues found unresolved for over a year.
One benefit seen from merge queue is that it ensures PRs are tested against the target branch. Since we won't be using this feature, I've enabled "Require branches to be up to date before merging" GitHub feature in this repo. By enabling this, all PRs will require to rebase before they can be merged and this way ensure code stability and integration.

Great work!
Just to confirm, do we want to cover code documentation on only the public functions in the common module?

It could cover the private ones as well, but I don't see any private functions appear in the sphinx documentation.

@Ygnas Yeah that's what I thought as well. Perhaps, the private functions can continue to have simple comments while the public functions include the enhanced code documentation for sphynx.


Int max limit, can't prefetch more than<PHONE_NUMBER> files

[ ] Define int type, fast swap all int bigger include big_int.h

[ ] Runtime type https://stackoverflow.com/a/20526163

Assume most user don't have more than<PHONE_NUMBER> to prefetch. Reply to this issue if you did meet this situation.


Make healthcheck dependent on models loaded

Good morning,
I'm using the MMS server to host a single model in AWS Sagemaker.  The model is loaded on MMS startup with sagemaker_inference.model_server.start_model_server with a custom handler_service.
The problem is that loading the model can take significant amount of time (up to 20 minutes). In the time that model is being loaded MMS server /ping endpoint returns 200 OK responses, causing sagemaker endpoint to assume the model is already loaded.
Furthermore, I tested MMS locally to see how the server behaves in the model loading stage and it looks like the model details endpoint returns model worker status as READY before the worker is finished loading the model.
In the logs below you can see that workers start and immediately there's:
2024-04-23T11:01:33,313 [DEBUG] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - W-9000-test State change null -> WORKER_MODEL_LOADED

after that there's
2024-04-23T11:01:33,317 [DEBUG] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - W-9000-test State change null -> WORKER_STARTED
...
2024-04-23T11:01:33,322 [DEBUG] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - W-9000-test State change null -> WORKER_STARTED

and only finally:
2024-04-23T11:03:33,657 [DEBUG] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - W-9000-test State change WORKER_STARTED -> WORKER_MODEL_LOADED
...
2024-04-23T11:03:33,657 [DEBUG] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - W-9000-test State change WORKER_STARTED -> WORKER_MODEL_LOADED

In the meantime /ping returns 200 OK and localhost:8081/models/test returns:
{
  "modelName": "test",
  "modelUrl": "test.mar",
  "runtime": "python3",
  "minWorkers": 2,
  "maxWorkers": 2,
  "batchSize": 1,
  "maxBatchDelay": 100,
  "loadedAtStartup": true,
  "workers": [
    {
      "id": "9000-57e7cf49",
      "startTime": "2024-04-23T11:01:33.316Z",
      "status": "READY",
      "gpu": false,
      "memoryUsage": 13099008
    },
    {
      "id": "9000-be19b2af",
      "startTime": "2024-04-23T11:01:33.317Z",
      "status": "READY",
      "gpu": false,
      "memoryUsage": 13434880
    }
  ]
}

All logs:

Removing orphan pid file.
WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.
2024-04-23T11:01:33,126 [INFO ] main com.amazonaws.ml.mms.ModelServer -
MMS Home: /home/ec2-user/SageMaker/notebooks/environment/user/user-env-base-3-10/user-env-base-3-10/pex_venv/lib/python3.10/site-packages
Current directory: /tmp/models/test
Temp directory: /tmp
Number of GPUs: 0
Number of CPUs: 2
Max heap size: 978 M
Python executable: /home/ec2-user/SageMaker/notebooks/environment/user/user-env-base-3-10/user-env-base-3-10/pex_venv/bin/python3.10
Config file: config.properties
Inference address: http://<IP_ADDRESS>:8080
Management address: http://<IP_ADDRESS>:8081
Model Store: /tmp/models/test/export
Initial Models: test.mar
Log dir: null
Metrics dir: null
Netty threads: 0
Netty client threads: 0
Default workers per model: 2
Blacklist Regex: N/A
Maximum Response Size: 6553500
Maximum Request Size: 6553500
Preload model: false
Prefer direct buffer: false
2024-04-23T11:01:33,133 [INFO ] main com.amazonaws.ml.mms.ModelServer - Loading initial models: test.mar preload_model: false
2024-04-23T11:01:33,189 [INFO ] main com.amazonaws.ml.mms.archive.ModelArchive - model folder already exists: f05f8ac8472b74dad6310273915eb6a5de447740
2024-04-23T11:01:33,217 [WARN ] W-9000-test com.amazonaws.ml.mms.wlm.WorkerLifeCycle - attachIOStreams() threadName=W-9000-test
2024-04-23T11:01:33,309 [INFO ] W-9000-test-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - model_service_worker started with args: --sock-type unix --sock-name /tmp/.mms.sock.9000 --handler /tmp/models/test/model_handler.py:handle --model-path /tmp/models/f05f8ac8472b74dad6310273915eb6a5de447740 --model-name test --preload-model false --tmp-dir /tmp
2024-04-23T11:01:33,311 [INFO ] W-9000-test-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - Listening on port: /tmp/.mms.sock.9000
2024-04-23T11:01:33,311 [INFO ] W-9000-test-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - [PID] 30549
2024-04-23T11:01:33,312 [INFO ] W-9000-test-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - MMS worker started.
2024-04-23T11:01:33,313 [INFO ] W-9000-test-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - Python runtime: 3.10.12
2024-04-23T11:01:33,313 [DEBUG] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - W-9000-test State change null -> WORKER_MODEL_LOADED
2024-04-23T11:01:33,314 [INFO ] W-9000-test MMS_METRICS - W-9000-test.ms:106|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870093
2024-04-23T11:01:33,314 [INFO ] main com.amazonaws.ml.mms.wlm.ModelManager - Model test loaded.
2024-04-23T11:01:33,315 [DEBUG] main com.amazonaws.ml.mms.wlm.ModelManager - updateModel: test, count: 2
2024-04-23T11:01:33,317 [DEBUG] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - W-9000-test State change null -> WORKER_STARTED
2024-04-23T11:01:33,320 [INFO ] main com.amazonaws.ml.mms.ModelServer - Initialize Inference server with: EpollServerSocketChannel.
2024-04-23T11:01:33,322 [DEBUG] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - W-9000-test State change null -> WORKER_STARTED
2024-04-23T11:01:33,334 [INFO ] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - Connecting to: /tmp/.mms.sock.9000
2024-04-23T11:01:33,333 [INFO ] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - Connecting to: /tmp/.mms.sock.9000
2024-04-23T11:01:33,415 [INFO ] main com.amazonaws.ml.mms.ModelServer - Inference API bind to: http://<IP_ADDRESS>:8080
2024-04-23T11:01:33,416 [INFO ] main com.amazonaws.ml.mms.ModelServer - Initialize Management server with: EpollServerSocketChannel.
2024-04-23T11:01:33,426 [INFO ] W-9000-test-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - Connection accepted: /tmp/.mms.sock.9000.
2024-04-23T11:01:33,429 [INFO ] W-9000-test-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - Connection accepted: /tmp/.mms.sock.9000.
2024-04-23T11:01:33,441 [INFO ] main com.amazonaws.ml.mms.ModelServer - Management API bind to: http://<IP_ADDRESS>:8081
Model server started.
2024-04-23T11:01:33,480 [WARN ] pool-3-thread-1 com.amazonaws.ml.mms.metrics.MetricCollector - worker pid is not available yet.
2024-04-23T11:01:33,553 [INFO ] W-9000-test-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - model initialising, waiting for 2 minutes
2024-04-23T11:01:33,554 [INFO ] W-9000-test-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - model initialising, waiting for 2 minutes
2024-04-23T11:01:33,592 [INFO ] pool-3-thread-1 MMS_METRICS - CPUUtilization.Percent:0.0|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870093
2024-04-23T11:01:33,598 [INFO ] pool-3-thread-1 MMS_METRICS - DiskAvailable.Gigabytes:48.51470947265625|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870093
2024-04-23T11:01:33,599 [INFO ] pool-3-thread-1 MMS_METRICS - DiskUsage.Gigabytes:86.47355270385742|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870093
2024-04-23T11:01:33,600 [INFO ] pool-3-thread-1 MMS_METRICS - DiskUtilization.Percent:64.1|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870093
2024-04-23T11:01:33,600 [INFO ] pool-3-thread-1 MMS_METRICS - MemoryAvailable.Megabytes:2041.51171875|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870093
2024-04-23T11:01:33,600 [INFO ] pool-3-thread-1 MMS_METRICS - MemoryUsed.Megabytes:1586.08984375|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870093
2024-04-23T11:01:33,602 [INFO ] pool-3-thread-1 MMS_METRICS - MemoryUtilization.Percent:47.8|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870093
2024-04-23T11:02:33,459 [WARN ] pool-3-thread-1 com.amazonaws.ml.mms.metrics.MetricCollector - worker pid is not available yet.
2024-04-23T11:02:33,528 [INFO ] pool-3-thread-1 MMS_METRICS - CPUUtilization.Percent:0.0|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870153
2024-04-23T11:02:33,529 [INFO ] pool-3-thread-1 MMS_METRICS - DiskAvailable.Gigabytes:48.51460266113281|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870153
2024-04-23T11:02:33,529 [INFO ] pool-3-thread-1 MMS_METRICS - DiskUsage.Gigabytes:86.47365951538086|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870153
2024-04-23T11:02:33,530 [INFO ] pool-3-thread-1 MMS_METRICS - DiskUtilization.Percent:64.1|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870153
2024-04-23T11:02:33,530 [INFO ] pool-3-thread-1 MMS_METRICS - MemoryAvailable.Megabytes:2014.546875|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870153
2024-04-23T11:02:33,530 [INFO ] pool-3-thread-1 MMS_METRICS - MemoryUsed.Megabytes:1613.0546875|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870153
2024-04-23T11:02:33,531 [INFO ] pool-3-thread-1 MMS_METRICS - MemoryUtilization.Percent:48.5|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870153
2024-04-23T11:03:33,445 [WARN ] pool-3-thread-2 com.amazonaws.ml.mms.metrics.MetricCollector - worker pid is not available yet.
2024-04-23T11:03:33,515 [INFO ] pool-3-thread-2 MMS_METRICS - CPUUtilization.Percent:0.0|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870213
2024-04-23T11:03:33,518 [INFO ] pool-3-thread-2 MMS_METRICS - DiskAvailable.Gigabytes:48.51456069946289|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870213
2024-04-23T11:03:33,519 [INFO ] pool-3-thread-2 MMS_METRICS - DiskUsage.Gigabytes:86.47370147705078|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870213
2024-04-23T11:03:33,520 [INFO ] pool-3-thread-2 MMS_METRICS - DiskUtilization.Percent:64.1|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870213
2024-04-23T11:03:33,521 [INFO ] pool-3-thread-2 MMS_METRICS - MemoryAvailable.Megabytes:2015.05078125|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870213
2024-04-23T11:03:33,523 [INFO ] pool-3-thread-2 MMS_METRICS - MemoryUsed.Megabytes:1612.55078125|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870213
2024-04-23T11:03:33,523 [INFO ] pool-3-thread-2 MMS_METRICS - MemoryUtilization.Percent:48.4|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870213
2024-04-23T11:03:33,653 [INFO ] W-9000-test-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - model finished waiting
2024-04-23T11:03:33,655 [INFO ] W-9000-test-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - Model test loaded io_fd=0242b6fffe39090c-00007712-00000001-85c1e7725a6e3c25-be19b2af
2024-04-23T11:03:33,656 [INFO ] W-9000-test-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - model finished waiting
2024-04-23T11:03:33,655 [INFO ] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - Backend response time: 120099
2024-04-23T11:03:33,656 [INFO ] W-9000-test-stdout com.amazonaws.ml.mms.wlm.WorkerLifeCycle - Model test loaded io_fd=0242b6fffe39090c-00007712-00000002-b0c9e7725a6e3c25-57e7cf49
2024-04-23T11:03:33,655 [INFO ] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - Backend response time: 120104
2024-04-23T11:03:33,657 [DEBUG] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - W-9000-test State change WORKER_STARTED -> WORKER_MODEL_LOADED
2024-04-23T11:03:33,658 [INFO ] W-9000-test MMS_METRICS - W-9000-test.ms:120341|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870213
2024-04-23T11:03:33,658 [WARN ] W-9000-test com.amazonaws.ml.mms.wlm.WorkerLifeCycle - attachIOStreams() threadName=W-test-2
2024-04-23T11:03:33,657 [DEBUG] W-9000-test com.amazonaws.ml.mms.wlm.WorkerThread - W-9000-test State change WORKER_STARTED -> WORKER_MODEL_LOADED
2024-04-23T11:03:33,659 [INFO ] W-9000-test MMS_METRICS - W-9000-test.ms:120343|#Level:Host|#hostname:ip-10-10-24-132.eu-west-1.compute.internal,timestamp:1713870213

Questions:

Is that the intended behaviour?
Is it possible for /ping endpoint to return something else than 200 OK when workers are still loading the models?

thank you! :)

I was just looking into this to understand what how ping and Sagemaker UpdateEndpoint would work together with MMS. As far as I can tell, the ping handler can already return non-200 (a 503 to be exact). The problem is how the running check is determined here. If you trace the code, you'd see that the check is essentially equivalent to to the first WorkerThread.getState() == WorkerState.WORKER_MODEL_LOADED.
The problem is that BOTH the server thread (the main thread/process running model_service_worker.py) and worker threads are implemented as WorkerThread. For the server thread's WorkerThread, it's state is set to WORKER_MODEL_LOADED right when the WorkerThread starts and remains that way. This corresponds with the first log line you showed
Since the model is thought to be loaded when the first WorkerThread is running instead of all of them, the ping handler quickly responds with 200, even if your model hasn't actually been loaded
I think the quickest fix on your end without a code change on MMS is to preload the model, in which case the model will attempt to be loaded when the Python backend, model_service_worker.py, is initially started
Note: if you're using this in Sagemaker, Sagemaker docs says that /ping should return a 200 within 8 minutes after container startup


Use Thumbnail with Translatable Collection

Laravel Version: 5.5
Voyager Version: 1.0
PHP Version: 7.2

Description:
I can not use the "thumbnail" function in a photo from the collection which is translated.
My Code
Controller
 $posts = App\Post::orderBy('created_at')->limit(3)->get()->translate(App::getLocale());

Template
@foreach($posts as $post)
...
   thumbnail('small'))}}">
...
@endforeach

ErrorException
Call to undefined method TCG\Voyager\Translator::thumbnail()

Did you try something like
 $posts = App\Post::orderBy('created_at')->limit(3)->withTranslations(App::getLocale())->get();
?

Thank you ! It works.

Terixer sorry and what your solution?

@imronmaulana007, the snippet posted by @emptynick was the solution.

For the next one that follows, how to avoid having to continually use getTranslatedAttribute() ...
The problem is that the original Model gets wrapped in a Translator model. So, in the template of the original in the OP's code:
getModel()->thumbnail('small') ) }}">


Update reactivity coefficient parameters

What is the change?
Update the parameter definition for some reactivity coefficient parameters to get the correct uniform mesh mapping behavior (change from ParamLocation.AVERAGE to ParamLocation.VOLUME_INTEGRATED).
Also changed some parameter defaults (None for list/array-like, 0.0 for scalar floats).
Simplified the logic for getting parameter values to be mapped in the uniform mesh converter.
Why is the change being made?
Certain parameters were not being mapped correctly because they were listed with the wrong ParamLocation tag.

Checklist

[x] This PR has only one purpose or idea.
[x] Tests have been added/updated to verify that the new/changed code works.

[x] The code style follows good practices.
[x] The commit message(s) follow good practices.

[x] The release notes (location doc/release/0.X.rst) are up-to-date with any important changes.
[x] The documentation is still up-to-date in the doc folder.
[x] The dependencies are still up-to-date in setup.py.

So, quick question.
These parameters need to be in ARMI and not a downstream reactivity coeffs plugin/repo?

And one the great debates (well, to me lol) rages on!
I'm of the opinion that these (amongst, many many others) should be moved downstream. I recognize the other arguments for keeping these sorts of things on ARMI, but I currently think they should be moved downstream.
Just my two cents.

Yeah, these parameters could definitely be moved to a downstream plugin, but I was just trying to tread lightly here. The PR was mostly about fixing minor issues with default values or locations for a few parameters. I only added one new reactivity coefficients parameter, which can be migrated downstream with the others if/when that happens.


symlink(): No such file or directory. Fixed!!

This is how I solved this issue, note that the "Fix it" notification still shows after this fix.
Make the following changes to you live app(that is your app online), I am using cPanel incase you want to know.
Add this in your web.php
Route::get('/link', function () {
$target = '/home/username/app_foler_name/storage/app/public';
$shortcut = '/home/username/public_html/storage';
symlink($target, $shortcut);
});
Now open a new tab and put in yourwebsitename.yourdomain/link
Incase you get the error below after doing the above steps:
Error: Call to undefined function Illuminate\Filesystem\finfo_file()
Go to Cpanel, go to "PHP selector"  and check the "fileinfo" option.
I also replaced my symbolic link in config/filesystem.php with the code below.
'links' => [
public_path('/home/username/public_html/storage') =>
storage_path('/home/username/app_folder_name/storage/app/public'),
],

https://github.com/the-control-group/voyager/pull/5367


Add emails to README

A small suggestion for our README file is to add our academic email addresses to the table at the top. @EvitaChasioti can you take care of that?

[x] Add email addresses to README.md

I added our email addresses to the info table.