Continuing LLM response parsing problems after 250

System Info
ubuntu
v0.0.250
Who can help?
@hwchase17 @agola11 @hwchase17
Information

[X] The official example notebooks/scripts
[ ] My own modified scripts

Related Components

[X] LLMs/Chat Models
[ ] Embedding Models
[X] Prompts / Prompt Templates / Prompt Selectors
[ ] Output Parsers
[ ] Document Loaders
[ ] Vector Stores / Retrievers
[ ] Memory
[X] Agents / Agent Executors
[ ] Tools / Toolkits
[ ] Chains
[X] Callbacks/Tracing
[ ] Async

Reproduction

implement multi input structured tool
enter user input to trigger the tool
check parsing

have had a chance to read and review earlier related regex and other parsing issues filed earlier some of which were marked as solved with 249 and 250 but continuing to have parsing issues
for example
https://github.com/langchain-ai/langchain/pull/7511
which is merged
when invoking a multi input structured tool
LLM returns
> Entering new AgentExecutor chain...
Could not parse LLM output: Action:
```json
{
  "action": "image_generate",
  "action_input": {
    "prompt": "Draw a cat"
  }

with extra 'json' before the valid json which is then cannot parse

have tried to handle this in the system prompt with (one example but tried multiple):

  _SUFFIX = ("Don't ask the user to confirm if you are pretty sure what you need to do in order to fulfill the request. "
           "For example, don't ask the user 'I can DO X. Would you like me to do that?', just do it. "
           "Make sure that any JSON you return is fully valid, does not include any extra 'json' text before the JSON object. "
           "For example, If you see you are generating a JSON that looks like this"
           "```json"
           "{{\"action\": \"edit_image\",\"action_input\": {{\"image_path\": \"sandbox:/images/edited_from_image_a1bc6dbb-1127-49d5-898a-d35c3bb1564d.png\",\"prompt\": \"Make the drawing even more basic\"}}}}"
           "``` and has the text 'json' before the valid JSON object, remove the extra 'json' text at the start so that your final output is ```"
           "{{\"action\": \"edit_image\",\"action_input\": {{\"image_path\": \"sandbox:/images/edited_from_image_a1bc6dbb-1127-49d5-898a-d35c3bb1564d.png\",\"prompt\": \"Make the drawing even more basic\"}}}}"
           "``` without the json"
           "Chat history:\n{chat_history}\n\n") + _SUFFIX

any help in trying to either parse better or instruct the LLM to provide a better answer would be appreciated.
thank in advance.
Expected behavior
either

works out of the box with another version of the
https://github.com/langchain-ai/langchain/pull/7511
resolution

works with additional LLM system prompt SUFFIX instructions if need be.
have tried a bunch of variations can't get it to work,

if anyone is facing the same issue I am currently handing it with a handle_parsing_errors flag in initialize agent
handle_parsing_errors="Check your output and make sure the complete output is a valid JSON! Sometimes there is a 'json' extra chacters at the beginning of the output before the JSON Object and that should be removed.",
this does delay things a bit but seems to work itself out
> Entering new AgentExecutor chain...
Could not parse LLM output: Action:
```json
{
  "action": "search_wikipedia",
  "action_input": {
    "query": "Michelle Obama"
  }
}

Observation: Check your output and make sure the complete output is a valid JSON! Sometimes there is a 'json' extra chacters at the beginning of the output before the JSON Object and that should be removed.
Thought:I apologize for the confusion. Let me search for information about Michelle Obama on Wikipedia without asking for permission.
Action:
{
  "action": "search_wikipedia",
  "action_input": {
    "query": "Michelle Obama"
  }
}
```Searching wikipedia for : Michelle Obama

Observation: Page: Michelle Obama
Summary: Michelle LaVaughn Robinson Obama (born January 17, 1964) is an American attorney and author who served as the first lady of the United States from 2009 to 2017, being married to former president Barack Obama.
Raised on the South Side of Chicago, Obama is a graduate of Princeton University and Harvard Law School. In her early legal career, she worked at the law firm Sidley Austin where she met Barack Obama.

interestingly trying to explain this in the system prompt is not working, perhaps I was too verbose in trying to explain this in the system prompt with the SUFFIX above

for now the best method I have found is to edit the structured chat prompt
at libs/langchain/langchain/agents/structured_chat/prompt.py
specifically I added
Make sure that there is nothing inside ``` to  ``` which would create a parsing error, such as text like "json" or "python".
to the FORMAT_INSTRUCTIONS

Actually in the responses we reviewed it is discussed your preferred direction was a pull request to programmatically remove “json” but the OP observed, same as we did, that a prompt change would be more effective.
Since the prompts are tied to the code you all should take the lead.  Or do you suggest that we propose prompt changes pull requests when they work for us?
The prompt change is above.

continues to happen in 251
Could not parse LLM output: Action:
{
  "action": "Final Answer",
  "action_input": "Here are the estimates for SABR in a table:\n\n| Year | Revenue (Million) | Dividend | Dividend Yield | EPS | P/E Ratio | EBIT (Million) | EBITDA (Million) | Net Profit (Million) |\n|------|------------------|----------|----------------|-----|-----------|----------------|-----------------|---------------------|\n| 2023 | $2,902           | $0.02    | 0.55%          | -   | -6.68     | $184            | $320             | -$188                |\n| 2024 | $3,221           | $0.02    | 0.55%          | -   | 16.33     | $499            | $621             | $83                  |\n| 2025 | $3,489           | $0.04    | 0.82%          | $0.79 | 5.71      | $738            | $837             | $285                 |\n| 2026 | $3,596           | $0.00    | 11.73%         | $0.93 | 4.84      | $811            | $903             | $328                 |\n| 2027 | $3,501           | -        | -              | $0.48 | 9.38      | $770            | $840             | $215                 |"
}

This is happening because it is using that json format + the tricky split/regex by backsticks. I have experienced the same issue asking for code. It is not able to actually manage proper escaping inside the JSON format. Doing some tests - out of langchain - I got very nice results using YAML format to communicate LLMs, less tokens and you dont need to worry about escaping if you specify the value as multiline value and give the requirement to manage properly multiline values - redudant I know, but you need to specify all this details to get a right machine format. At least GPT3.5 have a lot of issues formatting properly this kind of things. In adition, the chain should require the json/yaml clean, without surrond with markdown stuff not needed.
action: my_actions
action_input: |
   my awesome
   multileline
   ```with markdown```
  and
  <code>

Still seeing this issue in langchain 350 when using bedrock claude 2.1. Have identified the problem is the parse method in MRKLOutputParser. The final answer returned by the LLM must be structured as 'Final Answer: answer' or OutputParserException is raised. This is currently hardcoded. It is sometimes possible to use extra instructions in the prompt to force the correct output, but this is not reliable and as the prompt grows too long, issue #13647 often arrises.


Fullscreen option

It would be nice to add a fullscreen option.

Hi! I belive there is a way to do this without my lib, I want to give only crucial functionalities to not overload it and keep the small size, thanks!


Why use np.array to create add_count

I notice here the replay buffer initialize add_count as a numpy array. But it used as int.
And in the test script here and other agent test scripts like this initialize add_count as int.
So why use np.array in the first place?

Hi, this is to simplify serialization.


QCL turnup add profile options based of linked earth

See #2287

@consideRatio could you share the script as I can't quite follow the rounding and math you are using  in #2338

@pnasrat I put it here https://gist.github.com/consideRatio/071110916cb58220657398c61c14af7c.
Its based on having kubectl get node report information under allocatable for each node type as summarized in https://github.com/2i2c-org/infrastructure/issues/2121#issuecomment-1465277039.
I've done some manual transformations from KiB units to GiB and GB units as well, so the source for the logic is k8s reported allocatable memory for a node of each type in X KiB.

@consideRatio re your point about changing pull policy that sounds like something that should be done outside of the single cluster and in basehub, is that correct?

About singleuser.image.pullPolicy. Its not needed for any image that uses a immutable tag, but most hubs doesn't do that but instead has a specific image pinned. What would the downside be of using Always? More requests to the container registry, but if the container registry lists hashes for all the image's layers and those layer hashes are already around on the node - its not being downloaded again.
I have seen a binderhubf or example run into rate limitations by hub.docker.com for example though, so it can be relevant to not have Always as a imagePullPolicy by default unless its known to be needed for a mutable tag.
Here is an existing exception for carbonplan:
https://github.com/2i2c-org/infrastructure/blob/de1b067c83edadc99faebdfaf9c6e4b74f06dc82/config/clusters/carbonplan/common.values.yaml#L36-L41
I think it makes sense to opt-in for this rather than rely on a default value change in the basehub helm chart. Ideally in my mind, this should not be set at all in kubespawner, and then the k8s default behavior of acting as if its "Always" if the tag is latest specifically, and acting as if its "IfNotPresent" if the image tag is something else. Many helm charts, for example the boilerplate generated when using helm create <new chart name> comes with explicit configuration of the imagePullPolicy for some reason though.

Not a downside I am merely ensuring that I would be addressing in the correct place!

Ah great reading https://cloud.google.com/kubernetes-engine/docs/concepts/plan-node-sizes makes this clearer.

I read that too!! Then i calculated based on that and couldt observe that the allocatable memory from the described 128GB memory for the n2-highmem-16 node for example. At that point i gave up and looked at the actually allocatable memory as reported by k8s for pods on the node.

@consideRatio please take another look. I've done most things but will double check the allocatable once the profile list is up to both validate my understanding and understand the process you used to get the numbers

Btw if you get multiple code suggestions you want to commit, you have the choice to combine them into one via the GitHub UI, but only from the "Files changed" tab!

Thanks for the review/approval. I will likely do this with the  manual staging deploy first thing my time tomorrow!

Manual deploy to QC: staging
Running helm upgrade --install --create-namespace --wait --namespace=staging staging /home/pnasrat/workspace/src/github.com/2i2c-org/infrastructure/helm-charts/basehub --values=/tmp/tmp8yyyv0vu --values=/home/pnasrat/workspace/src/github.com/2i2c-org/infrastructure/config/clusters/qcl/common.values.yaml --values=/home/pnasrat/workspace/src/github.com/2i2c-org/infrastructure/config/clusters/qcl/staging.values.yaml --values=/tmp/tmptogaic_g
Release "staging" has been upgraded. Happy Helming!
NAME: staging
LAST DEPLOYED: Tue Mar 14 09:54:56 2023
NAMESPACE: staging
STATUS: deployed
REVISION: 15
TEST SUITE: None

kubectl get node gke-qcl-cluster-nb-huge-highcpu-56ceaf12-5fnb   -o json | jq '.["status"]["allocatable"]'
{
  "attachable-volumes-gce-pd": "127",
  "cpu": "95690m",
  "ephemeral-storage": "47060071478",
  "hugepages-1Gi": "0",
  "hugepages-2Mi": "0",
  "memory": "91143984Ki",
  "pods": "110"
}

allocatable memory 93.33GB

kubectl get node gke-qcl-cluster-nb-large-highcpu-9a199cd3-75db    -o json | jq '.["status"]["allocatable"]'
{
  "attachable-volumes-gce-pd": "127",
  "cpu": "31850m",
  "ephemeral-storage": "47060071478",
  "hugepages-1Gi": "0",
  "hugepages-2Mi": "0",
  "memory": "29130868Ki",
  "pods": "110"
}


chore: package updated

Initial checklist

[x] I read the support docs
[x] I read the contributing guide
[x] I agree to follow the code of conduct
[x] I searched issues and couldn’t find anything (or linked relevant results below)
[x] If applicable, I’ve added docs and tests

Description of changes
TODO

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

Comparison is base (704ce56) 67.61% compared to head (28c2c42) 61.15%.

Files
Patch %
Lines

packages/cli/src/index.ts
0.00%
2 Missing :warning:

packages/logger/src/index.ts
66.66%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #178      +/-   ##
==========================================
- Coverage   67.61%   61.15%   -6.46%
==========================================
  Files          11       13       +2
  Lines         315      345      +30
  Branches       27       29       +2
==========================================
- Hits          213      211       -2
- Misses        102      134      +32

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


wemos reset itselt

Dear Maarteen,
Thank you very much for sharing this project.
I am trying to configure a single channel gateway using your version 4 code, but something is not working properly.
First I tried with WifiManager enabled without success.
Now I have disabled WifiManager and hardcoded the ssid and password of the wifi AP, but the wemos resets itself (see image).
https://s02.justpaste.it/files/justpaste/d475/a17167248/file1.png
Please, could you help me to solve this problem?
Kind regards from Madrid

Ok, I have managed to solve this.
The problem is that the pins definition inloraModem.h is for Hallard's board, not for the instruction I found at http://things4u.github.io/HardwareGuide/Single-Channel-Gway/ESP-gateway-v4.html
// Definition of the GPIO pins used by the Gateway
//struct pins {
uint8_t dio0=15;	// GPIO15 / D8. For the Hallard board shared between DIO0/DIO1/DIO2
uint8_t dio1=15;	// GPIO15 / D8. Used for CAD, may or not be shared with DIO0
uint8_t dio2=15;	// GPIO15 / D8. Used for frequency hopping, don't care
uint8_t ss=16;		// GPIO16 / D0. Select pin connected to SPIO16 / D0
uint8_t rst=0;		// GPIO0 / D3. Reset pin not used
// MISO 12 / D6
// MOSI 13 / D7
// CLK 14 / D5
// SS 16 / D0
//} pins;
// For ComResult gateway use the following settings
struct pins {
uint8_t dio0=5;		// GPIO5 / D1. For the Hallard board shared betweenDio0/DIO1/DIO2
uint8_t dio1=4;		// GPIO4 / D2. Used for CAD, may or not be shared with DIO0
uint8_t dio2=0;		// GPIO0 / D3. Used for frequency hopping, don't care
uint8_t ss=15;		// GPIO15 / D8. Select pin connected to SPIO16
uint8_t rst=0;		// Reset pin not used
} pins;

Sorry for not responding sooner. Ny now you will have discovered that the pin definitions are in loraModem.h file, You should enable the standard pin setting setting by commenting the Hallard section and uncommenting the Comresult setting.
I'm thinking how to make the gateway autodiscover but I do not think this is possible.
I have updated the Read.me file to document how to get started with teh single channel gateway, which should in any case mean that you have to set the pins in loraModem.h, set the SSID and password for  your network in ESP-sc-gway.h and from that moment on cofnigure the gateway further.


Specify and populate config defaults using schema

As a user,
I would like config defaults to be documented in schemas,
So that I don't have to look through code logic to determine which key/values can be omitted.
This is mostly prompted by looking at vCloud Edge Gateway. There is lots of useful information in the README about defaults.
These are otherwise buried within Vcloud::EdgeGateway::ConfigurationGenerator::*, e.g. https://github.com/alphagov/vcloud-edge_gateway/blob/v0.5.0/lib/vcloud/edge_gateway/configuration_generator/firewall_service.rb
It feels like the schema might be the right place to centralise this information. Albeit changing the behaviour of Core::ConfigValidator quite drastically. Kwalify has something similar: http://www.kuwata-lab.com/kwalify/ruby/users-guide.01.html#schema-rules

Thank you for your interest in this project but we now consider it
both feature complete for our own usage and in maintenance mode.
While we will not be investing any more development time in this
project we may still include pull requests.


Jersey async client not actually using NIO

Make Spring Template the default NIO client

Changes on master - renamed both clients


protocol: implement peering links

This is an attempt to address Issue #4093
Since the feature branch referenced by the original PR #4249 wasn't correctly rebased, we'll start over with a clean slate as suggested by @oncilla .

This change is

Running bin/end2end_integration succeeds with the included peering-test.topo.
However, some of the traceroute tests run via bin/scion_integration fail. Here is a ping via one of the peering links that succeeds:
echo 0 | ./bin/scion ping -c 1 --sciond $(./scion.sh sciond-addr 113) -i 2-ff00:0:213,<IP_ADDRESS>
[...]
Using path:
  Hops: [1-ff00:0:113 3>3 1-ff00:0:112 42>23 2-ff00:0:212 3>3 2-ff00:0:213] MTU: 1472 NextHop: <IP_ADDRESS>:31022
[...]
1 packets transmitted, 1 received, 0% packet loss, time 2.015ms

Doing the same with a traceroute:
echo 0 | ./bin/scion traceroute --sciond $(./scion.sh sciond-addr 113) -i 2-ff00:0:213,<IP_ADDRESS>
[...]
Using path:
  Hops: [1-ff00:0:113 3>3 1-ff00:0:112 42>23 2-ff00:0:212 3>3 2-ff00:0:213] MTU: 1472 NextHop: <IP_ADDRESS>:31022

0 1-ff00:0:113,<IP_ADDRESS>:0 IfID=3 387µs 230µs 206µs
1 ?? * * *
2 ?? * * *
3 2-ff00:0:213,<IP_ADDRESS>:0 IfID=3 1.811ms 1.48ms 1.331ms
Error: packets were lost

Inspecting br1-ff00_0_112-3.log:
DEBUG          router/dataplane.go:483  SCMP    {"err": "scmp {cause=MAC verification failed {actual=fa5182d6f01c; cons_dir=true; curr_hf=2; curr_inf=1; expected=eb0cb3becbbc; if_id=0; seg_id=45995}; typecode=ParameterProblem(InvalidHopFieldMAC)}", "dst_addr": "<IP_ADDRESS>:31016"}

So MAC verification for SCMP is still an issue on peering links, at least in traceroute scenarios. Any pointers what I need to look at to make this work?

An odd bug keeps triggering on integration test. I've changed peering-test.topo to also trigger it when running ./bin/scion_integration. Here is what I've found so far:

MAC validation can fail when an AS has more than one peering link.
SCMP Errors are only reported by the border router(s) of the AS with the multiple peering links.
In some SCMP Errors, curr_hf, curr_inf and if_id are reported as 0.

I think I need a bit more information.
* What changes to the topology did you do?

My latest commit changed the following:
diff --git a/topology/peering-test.topo b/topology/peering-test.topo
index 40aed961f..b32873948 100644
--- a/topology/peering-test.topo
+++ b/topology/peering-test.topo
@@ -33,6 +33,7 @@ links:
   - {a: "1-ff00:0:110#2", b: "1-ff00:0:112#1", linkAtoB: CHILD, bw: 500}
   - {a: "1-ff00:0:112#3", b: "1-ff00:0:113#3", linkAtoB: CHILD, bw: 500}
   - {a: "1-ff00:0:113#4", b: "1-ff00:0:114#4", linkAtoB: CHILD, bw: 500}
+  - {a: "1-ff00:0:112#47", b: "1-ff00:0:114#11", linkAtoB: PEER}
   - {a: "1-ff00:0:110#3", b: "2-ff00:0:210#3", linkAtoB: CORE}
   - {a: "2-ff00:0:210#1", b: "2-ff00:0:211#3", linkAtoB: CHILD, mtu: 1280}
   - {a: "2-ff00:0:210#2", b: "2-ff00:0:212#7", linkAtoB: CHILD, bw: 500}
   - {a: "2-ff00:0:212#3", b: "2-ff00:0:213#3", linkAtoB: CHILD, bw: 500}
   - {a: "1-ff00:0:112#42", b: "2-ff00:0:212#23", linkAtoB: PEER}

* What tool fails: ping vs traceroute vs showpaths?

Ping as well as traceroute fail. It's easiest to verify when running bin/end2end_integration and/or bin/scion_integration.

* Between which hosts is the failure

Between any hosts that select a path via one of the two peering links offered by AS -112. Example:
echo "0" | ./bin/scion ping -c 1 --sciond "$(./scion.sh sciond-addr 213)" -i 1-ff00:0:114,<IP_ADDRESS>
Available paths to 1-ff00:0:114:
5 Hops:
[ 0] Hops: [2-ff00:0:213 3>3 2-ff00:0:212 23>42 1-ff00:0:112 3>3 1-ff00:0:113 4>4 1-ff00:0:114] MTU: 1472 NextHop: <IP_ADDRESS>:31056
7 Hops:
[ 1] Hops: [2-ff00:0:213 3>3 2-ff00:0:212 7>2 2-ff00:0:210 3>3 1-ff00:0:110 2>1 1-ff00:0:112 3>3 1-ff00:0:113 4>4 1-ff00:0:114] MTU: 1400 NextHop: <IP_ADDRESS>:31056
Choose path: Resolved local address:
  <IP_ADDRESS>
Using path:
  Hops: [2-ff00:0:213 3>3 2-ff00:0:212 23>42 1-ff00:0:112 3>3 1-ff00:0:113 4>4 1-ff00:0:114] MTU: 1472 NextHop: <IP_ADDRESS>:31056

PING 1-ff00:0:114,<IP_ADDRESS>:0 pld=0B scion_pkt=124B
ERROR: not SCMPEchoReply {type=snet.SCMPParameterProblem}

--- 1-ff00:0:114,<IP_ADDRESS> statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 1.869ms
Error: no reply packet received

Unrelated question: should I rebase or merge from master at this point or would just complicated matters?

Unrelated question: should I rebase or merge from master at this point or would that just complicated matters?

Generally, feel free to merge or rebase at any point. The Reviewable tool is very robust and does not easily get confused. The rebase-and-squash merge workflow that we use in this repository means that you don't need to worry about a clean commit history in your branch.
The merge conflicts that currently come up only come from moving the function calls for validateHopExpiry and validateIngressID out from parsePath (see #4157). This should be straight forward to resolve.
Btw. I've looked at the problem that show up with the changed peering topology, but haven't been able to figure out what is going on yet. I'll try to look into this again and get back to you by next week.

I reverted peering-test.topo to the simple topology with the single, "working" peering link and created peering-test-multi.topo with multiple peering links that demonstrates the above-mentioned problems.
Not sure if rebasing at this point wasn't a mistake. Some chaos couldn't be avoided, plus I had to make a few validation exceptions for peering (marked with XXX(benthor) in the code).
Even with the simple topology, bin/end2end_integration now fails with "no path found" across certain endpoint combinations, although bin/scion_integration succeeds and manually testing peering links (via, e.g., echo "0" | ./bin/scion ping -c 1 --sciond "$(./scion.sh sciond-addr 213)" -i 1-ff00:0:114,<IP_ADDRESS>) also yields 0% packet loss.
Some pointers about where to go from here would be appreciated.

I had to make a few validation exceptions for peering (marked with XXX(benthor) in the code).

Yep, the checks in validateEgressID look right to. Shouldn't we also accept the case ingress == topology.Peer && egress == topology.Unset: though?
I think we shouldn't need  the blanket exception for peering hops in validateTransitUnderlaySrc, but perhaps the logic to determine the ingressInterface() needs to be adapted for peer hops.
Sorry that I've not managed to give a more detailed feedback on your issues. I'm on leave until mid next week, but I will try to look into it after I return. Maybe someone else can already have a look in the meantime.

The latest commit contains a patch by @matzf for a tricky regression that apparently got introduced by changing a PeerEntry struct field from pointer to value and thereby breaking the semantics of a critical for loop body. See also go discussion #56010.
With this fix, the issues that plagued this PR for the last two months finally seem resolved. Peering links work again (also in more complex topologies).
In other words, we should be back on track. :tada:

Would you have capacity work on this?

Well-worded question. As much as I would like to work on this I will probably not find the time before end of next month, unfortunately.

Ok, I've added the "help wanted" label for the meantime. The current status here is: works, but missing tests.
Whoever starts working on this, please coordinate in this PR.


Overview app code cleanup and mobile improvements

Description
Overview app code cleanup and mobile improvements
Validation
To Validate

Make sure all merge request checks have passed (CI/CD).
Pull and run overview using 'npm run start-overview-dev' from the overview repo.
Navigate to the overview home page http://localhost:8082/.
View page in different mobile views and verify page looks good.
Navigate to the overview home page http://localhost:8082/getting_started.
View page in different mobile views and verify page looks good.
Navigate to the overview home page http://localhost:8082/data_publication_guidelines.
View page in different mobile views and verify page looks good.

Change Log
Overview app code cleanup and mobile improvements (0c7b26cc56386d8ba136a89e7e829701867316b0)

The not-in-use is there for a reason.  The svg icons are icons that the info team have used in the past, so they could want to use them in the future. The previous jsons are there so a developer can know how to build the json file and use those icons and other custom components like the infoBubble.  The other pictures are in case we need to create a new version of that image (whats in the hero).


Add a loading spinner

...so the user knows that something is going on. :grin:

@coltaemanuela Would you like to do this?


[Bug]: Waiting for load-balancer to get an IP... loop

Description
terraform apply
is stuck:
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization: Still creating... [1m30s elapsed]
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization: Still creating... [1m40s elapsed]
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...
module.kube-hetzner.null_resource.kustomization (remote-exec): Waiting for load-balancer to get an IP...

The LoadBalancer service is created in Kubernetes and is healthy in Hetzner.
I saw another issue with the same issue. https://github.com/kube-hetzner/terraform-hcloud-kube-hetzner/issues/539
I commented on there because I have the opposite situation my service name is ngx-ingress-nginx-controller instead of nginx-ingress-nginx-controller
Kube.tf file
locals {
  # Fill first and foremost your Hetzner API token, found in your project, Security, API Token, of type Read & Write.
  hcloud_token = var.hcloud_token

}

module "kube-hetzner" {
  providers = {
    hcloud = hcloud
  }
  hcloud_token = local.hcloud_token

  source = "kube-hetzner/kube-hetzner/hcloud"

  version = "2.1.5"

  ssh_public_key = file("/Users/user/.ssh/id_ed25519.pub")

  ssh_private_key = file("/Users/user/.ssh/id_ed25519")

  ssh_hcloud_key_label = "role=admin"

  network_region = "eu-central" # change to `us-east` if location is ash

  control_plane_nodepools = [
    {
      name        = "captain-nbg1",
      server_type = "cx21",
      location    = "nbg1",
      labels      = [],
      taints      = [],
      count       = 3
    },
  ]

  agent_nodepools = [
    {
      name        = "ship-small",
      server_type = "cx21",
      location    = "nbg1",
      labels      = [],
      taints      = [],
      count       = 0
    },
    {
      name        = "ship-large",
      server_type = "cx31",
      location    = "nbg1",
      labels      = [],
      taints      = [],
      count       = 8
    }
  ]

  load_balancer_type     = "lb11"
  load_balancer_location = "nbg1"

  etcd_s3_backup = {
    etcd-s3-access-key = var.aws_key
    etcd-s3-secret-key = var.aws_secret_key
    etcd-s3-bucket     = "k3s-etcd-snapshots"
    etcd-s3-region     = "eu-central-1"
  }

  ingress_controller = "nginx"

  cluster_name = "galaxy"

  extra_firewall_rules = [
    {
      description     = "To allow acces to resources via SSH"
      direction       = "out"
      protocol        = "tcp"
      port            = "22"
      source_ips      = [] # Won't be used for this rule
      destination_ips = ["<IP_ADDRESS>/0", "::/0"]
    }
  ]

  cni_plugin = "cilium"

  enable_cert_manager = true

  use_control_plane_lb = true

  lb_hostname = "cluster.io"

  enable_rancher = false

  rancher_hostname = "rancher.cluster.io"

  rancher_values = <<EOT
ingress:
  tls:
    source: "letsEncrypt"
hostname: "rancher.cluster.io"
letsEncrypt:
  email<EMAIL_ADDRESS>replicas: 3
bootstrapPassword: "password"
  EOT

}

provider "hcloud" {
  token = local.hcloud_token
}

terraform {
  required_version = ">= 1.3.3"
  required_providers {
    hcloud = {
      source  = "hetznercloud/hcloud"
      version = ">= 1.38.2"
    }
  }
}

output "kubeconfig" {
  value     = module.kube-hetzner.kubeconfig
  sensitive = true
}

Screenshots
No response
Platform
Mac

I just had a look into the init.tf. It tries to search for the service in the nginx namespace but my service is located in kube-system.

I deployed everything with the terraform module.

i just setup a new cluster, maybe hetzner is the culprit

Thanks for confirming @aDingil!
@Keyruu Everything looks fine on my end too, just tried a test cluster with nginx and I get the LB just fine. Please note that there is an issue with your kube.tf file that could be indirectly causing this.
Rancher is not yet compatible with the latest version of Kubenetes, please check on their site (and read the explanation well around the rancher variables in kube.tf, there are also links in there). A safe bet would be to set initial_k3s_channel to v1.24 or v1.25.


New GitHub organization

@n-rodriguez, I would like to create a new GitHub organization to host all projects related to redmine_git_hosting. Because right now it's a bit of a mess to maintain with dependencies scarreted left and right and quite a few of them looks only half maintained.
My hope is that with a proper organization, to which I would add at least yourself and @alexandermeindl, we can better keep everything maintained together.
So my question is, if I create said organization, would you be willing to transfer the ownership of the following repo ?

https://github.com/jbox-web/gitolite-rugged
https://github.com/jbox-web/grack
https://github.com/jbox-web/redmine_git_hosting

PS: Additionally, I would also include https://github.com/ogom/redmine_sidekiq in that org.

Why not :) how would you name it?

I created https://github.com/redmine-git-hosting and invited both of you as owners. And I threw in a logo made in 5 seconds.
I'd appreciate if you could transfer ownership of the 3 others projects.

Done! I also transfered https://github.com/jbox-web/gitolite which is the previous version of https://github.com/jbox-web/gitolite-rugged

Thank you !


Key concepts - Inconsistent with Lock and UnlockAndRelock

Hello,
The Key Concepts page says:

All WOPI operations that modify files, such as PutFile, will include a lock ID as a parameter in their
request. Usually the ID will be passed in the X-WOPI-Lock request header (but not always;
UnlockAndRelock is an exception).

However, when we check UnlockAndRelock, we can see that this is not true.

X-WOPI-Lock:
A string provided by the WOPI client that the host must use to identify the new lock on
the file. The maximum length of a lock ID is 1024 ASCII characters. Required.

Do you think opening a PR to fix this is a good idea?

Howdy drupol,
I think the confusion is that the X-Wopi-Lock header on the UnlockAndRelock request is the new lock not the old lock.
On most requests the X-Wopi-Lock header contains the existing lock string that the host is expected to enforce alongside the request.  The UnlockAndRelock request uses the X-WOPI-OldLock header for that string.
Best regards,
Rob Rolnick

Ok ok fair enough :)
Maybe this should be copy-pasted into the documentation.
Thanks for the responsiveness.
Regards.

Howdy drupol,
That's reasonable.  See the new Pull Request.
Best regards,
Rob Rolnick

Thanks !


Broken formatting in the linting-vale-cli page

Broken content in https://redhat-documentation.github.io/vale-at-red-hat/docs/user-guide/linting-vale-cli/:

The code block is misaligned
Erroneous + before "Where", and this block is misaligned
The space after the double dashes for the option is misleading.

https://redhat-documentation.github.io/vale-at-red-hat/docs/user-guide/using-vale-cli/


corrected DNS record referrence

#590

nenonix @JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@MSFTTracyP - PR has been copy edited and is ready for final review. This is based on issue
Thank you.
cc: @kenwith


build(deps): upgrade angular 11

Nice work @damingerdai . Can you please update the README.md as well?

Would fix https://github.com/ngx-translate/core/issues/1270

@lulzzz please review my pr

@ocombe any news on this ?

@ocombe any news on this ?

As explained in https://github.com/ngx-translate/core/issues/1270 we don't need to change the peer dependencies, the lib works just fine as it is...

As explained in https://github.com/ngx-translate/core/issues/1270 we don't need to change the peer dependencies, the lib works just fine as it is...


[stable/mongodb-replica-set] Fix metrics livenessProbe and regression in securityContext

What this PR does / why we need it:

Fix indentation in metrics container's livenessProbe settings, preventing the manifests to be applied with metrics enabled
Re-enable securityContext which was enabled by default before #10682

@unguiculus @steven-sheehy
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped

Thanks, I wish we wouldn't have merged that last PR. Besides accidentally disabling securityContext, it also limits people from customizing other keys within securityContext like capabilities, etc.
/assign
/assign @unguiculus
/ok-to-test

Good points @steven-sheehy. I agree we shouldn't have merged it. Should we revert it?

/lgtm

@unguiculus Yes, we should probably revert it.


*.S file suggest support

coc-clangd not support some assembly language file jump to define (this type file often exist in linux kernel source code, suce as: arch/arm/kernel/head.S), if use coc-settings.json like :
"languageserver": {
    "clangd": {
        "command": "clangd",
        "filetypes": ["c", "cc", "cpp", "c++", "objc", "objcpp", "asm"],
        "args": ["--background-index"],
        "rootPatterns": ["compile_commands.json",  ".git/", ".svn/"]
    }
}

it will work for *.S file (vim set ), so suggest add support for assembly language file.

Clangd doesn't support assembly files. Some preprocessor features may happen to work, but I wouldn't expect other features to, and I'd expect to see a lot of suprious errors.


Fail with default heroku-18 stack

2018-09-15T07:40:54.868060+00:00 app[web.1]: stderr: (node:17) UnhandledPromiseRejectionWarning: Error: Failed to launch chrome!

2018-09-15T07:40:54.868085+00:00 app[web.1]: /app/node_modules/puppeteer/.local-chromium/linux-588429/chrome-linux/chrome: error while loading shared libraries: libpangoft2-1.0.so.0: cannot open shared object file: No such file or directory

The libpangoft2 package is needed.

@paulcarroty I tested this buildpack from the person who upvoted you and it seemed to work with heroku-18. It would be nice if we can upstream the changes here.

2018-09-16T12:46:18.149982+00:00 app[web.1]: /app/node_modules/puppeteer/.local-chromium/linux-579032/chrome-linux/chrome: error while loading shared libraries: libthai.so.0: cannot open shared object file

I  forked the repo and added the "libpangoft2-1.0-0" package, however I get a new dependency error, which is the "libthai.so.0" package which I couldn't find a way to add. And of course, there might be more broken dependencies. I also got this error with both my app and the "https://github.com/timleland/headless-chrome" guide.
Also, the nguyenkaos buildpack referenced above gave me the same dependency error.

Thanks, @nguyenkaos, you should make the pull request.
I got it working with latest node, puppeter and ['--no-sandbox', '--disable-setuid-sandbox' ] flags.

I tried latest node, puppeteer and the flags. + cleaned cache and still getting the the "libthai.so.0" dependency error. If anyone has any tips how to solve it that'd be very appreciated!

The libthai.so.0 library is a part from libthai0 package which available in nguyenkaos buildpack.
Connect to your instance via heroku run bash and verify this library.

Thanks a lot @paulcarroty, it's now up and running!

Hey all. Thanks very much for bringing this to my attention and then getting it resolved amongst yourselves!
I did some digging and found that in the heroku-16 stack, those two dependencies listed were available at run time, but on the heroku-18 stack, they moved those two dependencies to build time only. The full list is here: https://devcenter.heroku.com/articles/stack-packages
So I added those in and made a new release for the updates: https://github.com/jontewks/puppeteer-heroku-buildpack/releases/tag/1.1.4
@hilmerx if you would be able to try that release and just confirm its working for you that would be very helpful. I also tested it on heroku-18 just now and all seemed well.
Thanks again for letting me know!

@hilmerx thanks a lot for double checking and letting me know!


feat(extension): remove dapp beta pill

Remove DApp Beta pill from Lace DApp connector and any related code

Allure Report
allure-report-publisher generated test report!

processReports: ✅ test report for 05bfc5f9

passed
failed
skipped
flaky
total
result

Total
32
0
4
0
36
✅


postgresqlPackages.pg_partman: 4.4.1 -> 4.5.1

Motivation for this change
https://nvd.nist.gov/vuln/detail/CVE-2021-33204 #124662
I don't know how to easily test this, will probably need a hand from a maintainer.
Things done

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

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

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Added a release notes entry if the change is major or breaking
[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 125007 at 29b52648 run on x86_64-linux 1

1 package built successfully:

postgresqlPackages.pg_partman (postgresql11Packages.pg_partman)

1 suggestion:

warning: missing-phase-hooks
installPhase should probably contain runHook preInstall and runHook postInstall.
Near pkgs/servers/sql/postgresql/ext/pg_partman.nix:16:3:
   |
16 |   installPhase = ''
   |   ^


⚠ Spryr has degraded performance

In c48aba4, Spryr (https://spryr.com) experienced degraded performance:

HTTP code: 200
Response time: 4006 ms

Resolved: Spryr performance has improved in 9dbcdc5 after 11 minutes.


Recaptcha V3

Description
it not a issue tbh, i just wanna know, how exacly i can make a "bypass" for the recaptchav3? i tried everything and could make it work, if someone has a example that would be great for me.
Full steps to reproduce the issue
(not a issue just a question)
Issue Type
Support
Operating System
Windows 10
Do you use Docker?
I don't use Docker

you better move this to the discussion section, it will fit better there

you better move this to the discussion section, it will fit better there

Sorry

there was already a discussion about Recaptcha V3 anyway #187

https://github.com/ZFC-Digital/puppeteer-real-browser?tab=readme-ov-file#why-cant-i-pass-recaptcha-v3


Fixed CyclicLearningRate and its tests' errors

Fixes #1203 .
What was causing the errors?

The derived classes of CyclicLearningRate doesn't have attribute scale_fn which was returned by mistake in get_config() through **super().get_config().
The tests were poorly written and that's why y_true and y_pred were calculated from two different functions. That's why it was failing.

I have resolved all the errors related to it. Also added one more test which was overlooked in previous implementation.
@gabrieldemarmiesse and @seanpmorgan - Please review it.

@raphaelmeudec
You are owner of some files modified in this pull request.
Would you kindly review the changes whenever you have the time to?
Thank you very much.

@gabrieldemarmiesse - Build is again cancelled. Is there any bug in the workflow? If there is, I want work on that issue.

@gabrieldemarmiesse - Build is again cancelled. Is there any bug in the workflow? If there is, I want work on that issue.

https://github.community/t5/GitHub-Actions/Macos-job-sometimes-get-canceled-without-any-reason/m-p/52875#M8654
Is as far as we got with troubleshooting that. We've turned on debug logs so you can download the log for any failing action that does this. They're not exactly user friendly though (at least with our setup), but it certainly desverves some attention:

@seanpmorgan - Done changes. Please review.


It works just not in a docker container

The current implementation works 99% of the time in the dev container or on a bare metal setup. But when built in a docker container it doesn't work at all. At this point, I've run out of ideas to find a solution.
Some observations:

The browser loads the pages but when the username is submitted it returns to the login page asking for the username again. It would also do this for the password field at some point in the testing. My guess here is some javascript is not loading the correct value in the form being submitted, but I could be totally off base.
I've tried messing with the shm_size and other things, but my knowledge of docker is limited.

Hey, I've been tooling with another script filling a similar purpose which was having a similar issue; the user name would get put into the input, the submit button clicked, the page would submit, but then it would come back to the initial login page. While the approach is different (that script makes use of Selenium rather than using chromium's api), the root issue may be the same: Xfinity is blocking automated access to their login page. There are likely some things which can be done with the headers or something which can work around these blockers; indeed I've found a python selenium replacement for chromium which does exactly this and has made jantman's script functional again.
The python lib is called undetected_chromedriver in case you're interested in poking around at it to see what may be special about it. I know that Selenium adds some fingerprints which websites can pick up on, but maybe there are other things there which may be helpful.
Any rate, I'll poke around at the script as well, see if there's any learnings I got from the Selenium/python side of things which may be relevant. I don't have high hopes tbh, but I want this to work too :-)

@XerxesDGreat I've been running the current script for over 3 weeks on a standalone VM with no docker and it completes the data retrieval 99% of the time. If I dockerize the same script with the same version of Chromium it fails after entering a valid username and password and then returning to the login screen.
So it's not the script or Chromium but something when you add them all to docker.

Yeah, I got that; I'm just trying to eliminate variables, one of which is Xfinity being aggressive with their automation blocking

How can we run this standalone to work? Trying Docker version, not working yet. But really interested in this integration!

@XerxesDGreat
Finally, found some time and motivation to look into undetected_chromedriver which then lead me to playwright-extra. Got it working with my setup yesterday and seems pretty reliable. Been running for a little over 24 hours on a 20-minute interval and has only missed one login.
Thanks.

thanks for the hard working. It finally worked in my docker.

Making progress but the sensor is unknown. Dunno if I got the username or password wrong but seems correct. It's a username and not an email, right?

Awesome, thank you! You succeeded where I failed 😅


#60: Specialized endpoints

-
-

Issue
https://github.com/ripe-tech/ripe-twitch/issues/60

Dependencies
--

Decisions
--

Closing and will re-open later as ripe-twitch API will yet have some changes regarding this routes


fix: add transformer to header params for proxy-rewrite and response-…

fix: https://github.com/apache/apisix/issues/2082
fix: https://github.com/apache/apisix/issues/2087
Solution: https://github.com/apache/apisix/issues/2082#issuecomment-716364969

 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.

@liuxiran pls sign the CLA

@liuxiran pls sign the CLA

thanks for your reminding, already done 😊

@liuxiran 嗨，请更新对应插件的 package.json 中的版本号。

@liuxiran 嗨，请更新对应插件的 package.json 中的版本号。

ok, already done :)

Just published


Last.fm 502 Bad Gateway

Hello!
Thank you for your hard work!
An error occurs when connecting the service. (502 Bad Gateway)

Hello!
I did notice this a couple weeks ago too. There is nothing wrong with your setup or last.fm account as far as I know. I believe something changed on the last.fm side, as this exact flow used to work. I wasn't able to find any kind of public changelog from them either.
I do have some bad news regardless, which is that last.fm integration will be discontinued in the next major Polaris release. I know this is annoying, and I didn't make this decision lightly (I am also using this integration!). The reasons are that:

The Rust library to interface with last.fm is abandoned (ignoring my basic maintenance PRs)
I don't want to spend time and energy supporting for-profit closed platforms anymore (still supporting Windows/Android due to ubiquity 😥)
It's borked (as you discovered)

(closing the ticket since I am not planning to action on it, but happy to continue the conversation)

(closing the ticket since I am not planning to action on it, but happy to continue the conversation)

Yes, I also have not used Lastfm for a long time. I'm more interested in maloja.

(closing the ticket since I am not planning to action on it, but happy to continue the conversation)

Yes, I also have not used Lastfm for a long time. I'm more interested in maloja.

in the next major Polaris release

Can we find out what changes and improvements await us?

I keep this board up to date as I'm working on it: https://github.com/users/agersant/projects/2/views/1
Maloja looks neat. I haven't explored the OSS ecosystem for scrobbling but I would be interested in (re)adding something to Polaris to fill this niche eventually.


Provide an option to only allow /back command to go back to death position

Related discussion: https://discord.com/channels/818135932103557162/1107340350898585630
Currently you can control whether players are able to use /back to return where they died, however, it's not possible to only allow /back command to go back to death position but not allow to return their previous position.
I'd like to have a new permission to control whether a player can go back to their previous position, for example:
huskhomes.command.back.previous
So overall the new permissions can be organized this way:

huskhomes.command.back - Get access to /back command (it's just used to allow the access, not the usage of actual features)
huskhomes.command.back.previous - Use /bcak to return your previous position
huskhomes.command.back.death - Use /back to return to where you died

An extra suggestion, you can take it or not :) to avoid confusion & hassle caused by the permission changes, huskhomes.command.back.previous can be given out as a default permission. So it'd be just a drag-and-drop update process.

Closed in #422


allow actorlifecyclemanager to accept stop msg when already stopped

Codecov Report

Merging #52 (bea3653) into main (c16e582) will increase coverage by 0.92%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##             main      #52      +/-   ##
==========================================
+ Coverage   76.02%   76.94%   +0.92%
==========================================
  Files         165      165
  Lines        3011     3006       -5
  Branches       69       67       -2
==========================================
+ Hits         2289     2313      +24
+ Misses        722      693      -29

Impacted Files
Coverage Δ

...ternal/akka/actor/ActorLifecycleManagerActor.scala
90.47% <50.00%> (+1.00%)
:arrow_up:

...health/windows/actor/HealthSignalWindowActor.scala
93.10% <0.00%> (-1.15%)
:arrow_down:

...a/surge/kafka/KafkaPartitionShardRouterActor.scala
62.58% <0.00%> (-1.11%)
:arrow_down:

.../surge/internal/kafka/KafkaProducerActorImpl.scala
86.58% <0.00%> (-0.44%)
:arrow_down:

...alth/matchers/SignalPatternMatcherDefinition.scala
93.54% <0.00%> (+3.22%)
:arrow_up:

.../scala/surge/internal/health/HealthSignalBus.scala
75.53% <0.00%> (+4.25%)
:arrow_up:

...afka/streams/AggregateStateStoreKafkaStreams.scala
83.33% <0.00%> (+4.76%)
:arrow_up:

...kafka/streams/KafkaStreamLifeCycleManagement.scala
74.15% <0.00%> (+5.61%)
:arrow_up:

...rnal/health/supervisor/HealthSupervisorActor.scala
78.51% <0.00%> (+6.66%)
:arrow_up:

... and 3 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 c16e582...bea3653. Read the comment docs.


Update PublishPushDataset.cs

Allow to set the RetentionPolicy to 'basicFIFO' via a cmdlet parameter. Replaces hardcoded 'None'.

Thanks for the contribution. Do you have a cmdlet compiled you can use, or do you need the one in the gallery? I'm not able to publish an update soon, for this reason I'm asking!

Thanks for the feedback! I have compiled the cmdlet locally so I can survive until a next version. Maybe it would be good to return the retention policy of the new dataset as well, as apparently there's no way to read it after creation.

I just released an updated version of the NuGet package and of the PowerShell cmdlet yesterday.
Good point about the retention policy, thanks for the suggestion!


Add 'Array Detector (non-EPICS)'

Adapted from https://gist.github.com/danielballan/84484f940aea836ac997d3873c88d762

I'll go ahead and merge this so it's in main; we can edit as needed from there.


Plan for resource hosting

We need to determine where and how audio and visual resources for the VIM will be hosted.

@zhannaklimanova @lucasmarchd01 Feel free to weigh in on this.

Started the discussion here: https://github.com/DDMAL/VIM/discussions/15

Per here (https://github.com/DDMAL/VIM/discussions/11#discussioncomment-6848283), we will use either Internet Archive or an Alliance hosting mechanism.


feat(GCS+gRPC): implement standard parameters

The REST API has a small number of "standard" query parameters which are
not part of the gRPC requests. They are implemented using special
x-goog-* "metadata" via the grpc::ClientContext. These are
documented at:
https://cloud.google.com/apis/docs/system-parameters
With this change the GCS+gRPC plugin fills out those headers from the
*Request object.
Fixes #4215 and fixes #6982

This change is

/FYI: @tritone @noahdietz I am not sure if you implemented the quotaUser, userIp, or the fields query parameters for REST, but here is how I implemented them for gRPC.


New #include guard sanity check + fixes to current guards

@ctiller

Sanity seems to be failing

Given the presence of an automatic fixer - can we postpone this a week?

Sure.

This PR needs and LGTM and rebasing.

Done. PTAL. Reasigned to @sreecha

OMG GREEN

Thanks for a really thorough review @sreecha !

LGTM. Did you run this tool one more time ?

Now I have :)

green enough

LGTM!


Update websites-dotnet-webjobs-sdk-get-started.md

Hi @davidau, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no contribution license agreement is required at this point. Real humans will now evaluate your PR.

TTYL, AZPRBOT;

@tdykstra - Could you review this public repo contribution from @davidau?

@tysonn Looks good -- Thanks, @davidau  for the correction!


refactor: replace bossy with duct

closes https://github.com/tauri-apps/tauri/issues/6718

I saw several PR about replacing bossy with duct. Could you tell me why bossy has problems?
And why this could resolve cross compile of openssl?

I saw several PR about replacing bossy with duct. Could you tell me why bossy has problems?

They seem to be doing something with the children process handles that introduced several bugs.

And why this could resolve cross compile of openssl?

bossy had two ways to create commands, impure and pure. The impure version would inherit env vars while the pure one doesn't inherit it. In this PR, all child processes inherit env vars which the linked issue wants to, in order to fix openssl compilation.

Pushed some fixes (most important one is removing the SDKROOT env var - swift build fails with that one).

We'll need to watch out for bugs though, I'm sure there's a reason cargo-mobile were doing the pure/impure thing.


Run examples on windows too

The history is a bit bleah, so please squash-merge.

Examples have a tendency to rot easily. Also, this makes sure they work on all platforms even though I locally test them only on Linux.

Examples have a tendency to rot easily. Also, this makes sure they work on all platforms even though I locally test them only on Linux.


Improve Live Game Scanner

Live Game Scanner is too slow and unreliable at times. Procmon is not only way faster in getting file paths but can also get the obscure ones. The only issue is that It might also grab stuff unrelated to a map as well. You just need to filter the results given from the program.
Link to tool: https://learn.microsoft.com/en-us/sysinternals/downloads/procmon
How it can be used: https://web.archive.org/web/20231201201948/https://www.hiveworkshop.com/threads/poc-reforged-mpq-name-scanner.351760/

I believe this is exactly what I'm doing except instead of using ProcMon as an external app, I re-coded it directly inside WC3MapDeprotector.
I'm using WC3's "Allow local files" registry setting. I'm using this API from Microsoft for monitoring hard drive access: Microsoft.Diagnostics.Tracing.Session.TraceEventSession
I'd love to improve it if it's not working correctly or if there's a better way.
Can you give me an example of a map & unknown file that can be discovered via procmon & https://web.archive.org/web/20231201201948/https://www.hiveworkshop.com/threads/poc-reforged-mpq-name-scanner.351760
which is not found by "Live Game Scanner" of WC3MapDeprotector?
Also, tell me if there's something specific I need to click inside the map to get the unknown file to load from disk. (Select a unit, enter a dungeon, etc)
Having this example would help me troubleshoot why WC3MapDeprotector is failing to discover the unknown file.

It is not really an issue with certain maps. It is just that Live Game Scanner is incredibly slow in general. I could be playing around for hours on end just to get the path for a file. With ProcMon, you just need to run the map in game, and it will fetch the paths for a whole bunch of files. You don't even need to play the game really.

I understand exactly what you're saying. however, i need proof so i can fix it. Live game scanner in my app does use procmon., it's a different version, but it should produce the same result.
The reason live game scanner is slow & rarely finds files is because it's the last step & most files have already been discovered.
can you give me proof of 1 unknown file that is found by procmon but is unknown by my tool? i need this proof so i can research how to fix the bug bexause they should be the same.

I've added a feature to automatically load the deprotected map in the world editor at the end of processing. I'm going to attempt to do live scanning on it the same as in game (not sure if it uses the "Local Files" setting, I'll have to test).
In addition, I had an idea that I can search all other maps that use the same file by searching with the asset scanner tool from hive workshop
https://www.hiveworkshop.com/asset-scanner
It searches based on the binary data in the file, rather than the filename, so it should find all references to it (assuming the map has been uploaded to hive).
If other map makers kept the same filename, we could deprotect the other map in hopes to discover the name. The manual process would be to deprotect the other maps in hopes the filename is found & added to the global list file, then deprotecting the 1st map again. I may be able to find a way to automate this a bit more.

Test with this tool to see if it finds additional listfile names
http://<IP_ADDRESS>:9999/export

Read all file names from all native blizzard MPQ files and add to global listfile. This is because custom maps can override base skins by re-using same filename as native, but no reference will be found by searching .mdx/.blp/etc of custom map because reference is in base game files. (will probably need a casc loader and if they're missing a listfile will need to run scanner against native game files)


Parse escaped characters in strings

There is support for some escaped characters in strings which will involve a little bit of Cow magic to involve potentially manipulating the strings.

Finished with cceb207913a5e1544a831158f7df4acf0c20e1ea - f14baa658c613d28da372675cff918f3d2213606


polymer.js:11079 Uncaught ReferenceError: PolymerExpressions is not defined

This is one of those errors that only comes about when I compile my own version of polymer with browserify or similar module loaders.
polymer.js:11079 Uncaught ReferenceError: PolymerExpressions is not defined

I'm unclear why you're using browserify. Innm, browserify is for using node modules in a browser. Polymer already targets the browser, so it isn't appropriate to use browserify - you just use a  element in your index.html or other html file.

Hey @davidmaxwaterman, thanks for your comments (including https://github.com/Polymer/polymer/issues/1236#issuecomment-76690902)!
I think that my goal or what I'd like to see is an easier way to build components with dependencies. You're absolutely right, you mentioned in your other comment it doesn't require a compile step. I have a working demo here of two components using the same dependency moment. And your right In these examples, I'm not importing polymer using the link tag or relying on Polymer being a global variable. All I can really share is my desire to make things like this, and if the community disagrees then so be it.  I just feel like the polymer project is a little lacking when it comes to minifying, packaging, and dependencies, which are all real-world issues.
var Polymer = require("polymer")
var moment = require("moment")

Polymer("moment-time", {
  ready: function() {
    var $this = this
    setInterval(function(){
      $this.time = moment().format($this.format)
    }, 1000);
  }
});

OK, I see what you're getting at. I'm not sure about that objective, so I'll leave it to others to answer, and be interested in reading what is said too :)

Sorry to come back to such an old thread, but I thought I'd mention a method of loading dependencies in a require.js fashion - though actually with System.js. I't's not quite as succinct as Require.js, but it does the job. If you can use ES2015 destructuring, then it might be a lot more like Require.js does it.
We implemented it here (a 0.5 app) :
https://github.com/solettaproject/soletta-visual-editor/blob/master/app/elements/slv-editor.html#L178
  window.slvEditorReady = Promise.all(
  [
    System.import('Component'),
    System.import('FactoryDecorator'),
    System.import('GraphQuery'),
    System.import('ComponentSimilarGrouper'),
    System.import('NodePlacer'),
    System.import('lodash'),
    System.import('js-signals'),
    window.slvComponentSelectPopupReady
  ])
  .then(function (imports) {
    'use strict';
    var Component = imports.shift();
    var FactoryDecorator = imports.shift();
    var GraphQuery = imports.shift();
    var ComponentSimilarGrouper = imports.shift();
    var NodePlacer = imports.shift();
    var _ = imports.shift();
    var signals = imports.shift();

Having said this, I had a discussion with @sjmiles who knows infinitely more about this sort of thing than I do, and he said it really isn't needed - I never did understand what he was saying though.
I suppose there are two questions I'd like to know the answer to :

The encapsulation of the Polymer() call inside an asynchronous callback function, meaning that, by the time the JavaScript in that imported file has finished running, the Polymer() call may not have been run (it's dependencies are loaded first, often meaning delays due to disk and/or network), so elements that import it, can't rely on the element having been registered/etc. How to solve that problem?

How to 'rename' a dependency? This is done by changing the name of the parameter in the require() callback. I'm not sure how you would do this with an html import.

I've seen some mention of things that might be relevant to the above at the Polymer Summit....yes, from @ebidel 's talk, he mentioned a beforeRegister method which sounded like it might fit into this somewhere, but exactly I'm not sure where or how.
@robdodson said he'd also come up with some similar solution to the promise based one above, but I hope Scott or Eric can elaborate on the issues, and detail their recommended solutions.


Cannot write to ‘master.tar.gz’

The Travis test on our Flavor fails without any real modification (README.md).
https://travis-ci.org/workflow4metabolomics/w4m-vm/builds/164635858#L741
$ make install
cd /home/galaxy && sudo su galaxy -c 'wget https://github.com/bgruening/bioblend/archive/master.tar.gz'
--2016-10-05 13:18:40--  https://github.com/bgruening/bioblend/archive/master.tar.gz
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://codeload.github.com/bgruening/bioblend/tar.gz/master [following]
--2016-10-05 13:18:41--  https://codeload.github.com/bgruening/bioblend/tar.gz/master
Resolving codeload.github.com (codeload.github.com)... <IP_ADDRESS>
Connecting to codeload.github.com (codeload.github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-gzip]
Saving to: ‘master.tar.gz’
    [ <=>                                   ] 0           --.-K/s   in 0s
Cannot write to ‘master.tar.gz’ (Success).
make: *** [install] Error 3
The command "make install" failed and exited with 2 during .
Your build has been stopped.

Any idea?
Thanks

Mh its working for me: https://travis-ci.org/bgruening/docker-galaxy-ngs-preprocessing
Can you rerun the test? Maybe this was a network error?

I've got the same error on another branch of your project. I've re-run the build, and got the same error again.

@pierrickrogermele @lecorguille oh great - so we have the same travis.yaml and it crashes randomly?
I will trigger a few times for a build and see if I can reproduce it.
It worked for you at some point isn't it?

https://github.com/bgruening/docker-galaxy-epigenetics/pull/1 also working, I don't get it.

2 guys but the same repo.
So maybe, there is something with our project?
Is there some disk usage limitation in Travis?

Mh, afaik the disc quota can vary between different VMs, sometime you can even get one which runs in a ramdisc. How many GB are you using approximately?

Our Docker images is rather big: 3.968 GB
We can try a du -sh . somewhere in the .travis.yml ?

@lecorguille and maybe you can remove some tools in a branch and see what happens.
I will try to make the base image smaller for the next release if I find some time.

I've run some commands.
The build is run inside /home/travis/build/workflow4metabolomics/w4m-vm, and the / point is as following:
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        30G   17G   13G  57%   /

First time I have seen this: https://travis-ci.org/bgruening/docker-galaxy-exome-seq/jobs/165581712#L639 but there seems to be a limit in space on travis. I was able to run out of discspace.

It is indeed because of disc-space. https://travis-ci.org/bgruening/galaxy-rna-seq/builds/165854108#L696
Now I need to find a way to fix this :(

All green now 👍
Thanks

Perfect!


New contributors

@asmacdo as part of the DataLad and container-based execution alternatives, you have made some contributions to this. Could you send me your ORCID? Wasn't able to find it.

0000-0002-8124-807X

Added you to the record https://zenodo.org/record/8214739


Support UPPER_CASE keys for all settings

In the AppSettings, all settings use upper case names other than AzureWebJobsStorage.
This causes an issue when using Doppler or other secret/env managers, as they only support upper case keys for cross-environment support.
My request is that AzureWebJobsStorage is updated to use upper case for the setting lookup, or to make the comparisons case-insensitive.
https://github.com/Azure/functions-action/blob/master/src/handlers/resourceValidator.ts#L200

Fixing this needs more changes than just updating the logic in this repo. Correct fix is to make sure the appsettings are created with the right case to begin with.


test failed on Windows

'should respect line-ending config' failed because parameters were out of order on expected result. CRLF version of the tests was out of sync with LF version.
Fixes #1849

Thanks for reporting and fixing this for us!
This one was my fault, those tests get skipped both for me and on our CI environment. ^-^'
Later I'll evaluate if we can include a Windows runner in our pipeline to catch this in future.


CompilerSkSL should be able to handle UBOs and push constants

SkSL does not support UBOs (possible in GL or Vulkan) or push constants (Vulkan only).
We could make impellerc generate compliant SkSL from GLSL that has UBOs or push constants either by using emit_uniform_buffer_as_plain_uniforms (I think) from SPIRV-Cross or just by manually manipulating the UBOs into flattened uniforms (should work for sure).

The update in the last Impeller Weekly was that we are not going to go out of our way to support additional features in fragment program shaders at this time. Closing this as wont-fix.


can I send file by this Lib?

can I send file by this Lib?
such as .mp3 media data.
what function I can use ?
thanks!!

Every file can be converted to array of byte. You can send byte array with this lib.


Jurisdictions -> Divisions

In OCD the areas are called divisions. Jurisdictions things like school board or legislature that operate in a given division.

Cool. looks like we're good now.


Add ability for an external party (like the eWallet) to sync with the OmiseGO Network

The eWallet is currently able to sync with Ethereum by going through each block, parsing the transactions and extracting all transactions of interest. This allows the eWallet to listen for incoming transactions to its hot wallets and deposit wallets.
We need something similar from the OmiseGO Network. In order to sync, we need to get all the transactions since the beginning. The problem is that block numbers don't follow each other (1000, 1001, 2000`, etc.) so we need a way to retrieve the list of all blocks, in order to then query the transactions for each one of those blocks.
Note that we don't necessarily need the blocks, what we care about are the transactions, so we may be able to rely only on /transaction.all if that endpoint was updated to allow sorting via parameter.
Here are a few options we came up with that meet our needs:

Getting the list of blocks with some endpoint (/block.all), and for each block getting the transactions and parsing them (/transaction.all with blk_num as filter).
Using /transaction.all to go through all transactions since the beginning of time - would require to specify the sorting order.
Listening to transactions on Ethereum going to the childchain smart contract (committing new blocks), getting the block hash from it, and querying the block/transactions from the Watcher with that hash (if supported, and if the hash is the same :sweat_smile: ).
Can't we just get the list of all blocks from the smart contract directly? If that's the case, we can just query that, parse it and get the transactions from the Watcher for each block. This bypasses the Watcher / Childchain for block retrieval (and doesn't require much work).

/discuss

Thank you for taking the time to write this down :pray:
To reiterate, you want to pre-preocess the contents of the child chain (the transactions to date) to extract useful information, concerning some addresses of your choice (or other criteria, like currency).
That is, you don't want to rely on being able to call transaction.all at the moment you need this information. Is this correct?
Now onto the details:

The problem is that block numbers don't follow each other (1000, 1001, 2000`, etc.)

1001 are deposit blocks, which kinda follow their own special rules. Also the ordering of a particular deposit isn't defined till after the ethereum events related gain finality. E.g. 1000 1001 2000 can easily become 1000 2000 2001 due to a reorg.
I think currently the Watcher doesn't treat (on the outside APIs) deposits as txs nor deposit blocks as blocks. They're just "deposits", UTXOs that appear out of thin air.

able to rely only on /transaction.all if that endpoint was updated to allow sorting via parameter.
...
2. Using /transaction.all to go through all transactions since the beginning of time - would require to specify the sorting order.

I think transaction.all sorts by [desc: :blknum, desc: :txindex] meaning that you should have the order. As noted above, it doesn't include the deposits, for other reasons.
Oh wait, what you're saying is that you'd like to specify the order as "ascending" is that it?

Getting the list of blocks with some endpoint (/block.all), and for each block getting the transactions and parsing them (/transaction.all with blk_num as filter).

Hm, similarly, if you treat deposits independently, then the list of all blocks (all blknums) is just 1000 through last_validated_blknum, increasing in 1000. The last_validated_blknum you can get from status.get

Listening to transactions on Ethereum going to the childchain smart contract (committing new blocks), getting the block hash from it,

I think this is an option. As soon as the block is successfully validated by the watcher, you should be able to get the contents. I'd then vote to do transaction.all+filter by block hash and leave block.get to allow Watcher2Watcher proxying (mimic block.get on the childchain). But not 100% sure if the last part makes sense

Can't we just get the list of all blocks from the smart contract directly? If that's the case, we can just query that, parse it and get the transactions from the Watcher for each block

An option as well:

you can get the top child blknum from the contract
you can iterate from 1000 to that by 1000 to get all the blknums

It is an alternative of (1/) where you would use status.get, the difference being, you might run into a not-yet-validated blknum, so I think (1/) is better

I think the choice here boils down to keeping the proper separation of concerns and the question how you want to handle deposits (or - do you necessarily need to handle them as blocks and transactions).
Another question from me is how would you like to discover that a new block has been validated and there's more txs to look at - push event from the Watcher? poll?
Also let me tag @Pongch for some wider product perspective here.

I think this is tackled by many sub-issues already. Closing this in favor of those. Re-open if you think I've missed the point! Ktnx <3


No matching distribution found for yaml

ERROR: Could not find a version that satisfies the requirement yaml (from versions: none)
ERROR: No matching distribution found for yaml

Is it "PyYAML" that needs to be installed?

Yes, my bad, changed it already.


RetryMiddleware shared examples tests not running.

Something async or with how Jest wants the structure is causing tests in  /spec/browser/middleware/retry/shared-examples.js not to run.

I think you can't run the tests directly with jest; you have to use the yarn commands.
yarn
test:browser
test:browser:integration
test:browser:watch
test:node
test:node:integration
test:node:watch
-- this command runs all the tests (integration + unit)
test

I am passing yarn test:node && yarn test:browser locally and I think the pipeline passes with this line:
https://github.com/jbeuckm/mappersmith/commit/9e22ac350b5c51aebe5c991a196e331776359cf1#diff-31c89a1400440944e8819670912e0907R23

Updating jest per Tulios recommendation... https://github.com/jbeuckm/mappersmith/tree/bump-jest-version


Please ignore. This is for testing.

Commit IDs
https://github.com/iancha1992/bazel/commit/79a0dc276cc81717ac2951d575e19f6a54d71e43
Category
team-Core, team-Bazel
Reviewers
@iancha1992

The following commits were cherry-picked in https://github.com/bazelbuild/bazel/pull/19706: https://github.com/iancha1992/bazel/commit/79a0dc276cc81717ac2951d575e19f6a54d71e43.


[CoreWM] Resizable panels

Just an idea for the panel.

I made a note of this in #49 and will re-open this issue when I start working on this functionality, Stay tuned and thanks for the suggestion :)

I made a note of this in #49 and will re-open this issue when I start working on this functionality, Stay tuned and thanks for the suggestion :)


Facing issue in deploying twilio cli for programmable video

After running npm run deploy:twilio-cli, optimized production build compiles successfully, chunk.js file gets created. However after this starts giving network connectivity error, although there isn't any internet issue.

Environment (please complete the following information):

OS: Ubuntu 18.04
Browser: Chrome
Node.js version:15.0.1

Additional context
Twilio login command asks for account sid and auth token,after being added cannot find any profiles using command twilio profiles:list.So have added account sid, api key and api secret in .env file.

Thanks for the issue @rakeshkk16!
We have an article that has resources that can help you diagnose the issue: https://support.twilio.com/hc/en-us/articles/360007199494-Resources-for-Diagnosing-Connection-Issues-to-the-Twilio-REST-API
Let's double check and make sure that your machine can access Twilio's APIs. Can you please run the dig and curl commands as specified in that article and let me know what the output is? Thanks.

Thanks for the info @rakeshkk16!
Everything looks good there.
What if you run another twilio-cli command just to test that it is working properly. For instance:
twilio phone-numbers:list
This will display any twilio phone numbers you have purchased (if any).

This command givind me error as could not find profile (scrrenshot for your reference). Although I can see TWILIO_ACCOUNT_SID when I runs echo $TWILIO_ACCOUNT_SID command as I already have set these values in environment variables.

Thanks for the screenshot @rakeshkk16!
I think I see the issue. You are using sudo. When you use sudo, commands are executed as another user, specifically the root user.
I think this is why the Twilio CLI cannot access the environment variables you set. You're setting them as your user, but it's the root user that's running the CLI commands.
A test:
-Run env. You should see your Twilio environment variables.
-Run sudo env. You should not see your Twilio environment variables.
This could also explain why twilio login isn't working for you.
I would recommend using npm without sudo. There are a number of articles online about ways to achieve this. You may need to uninstall node and npm, and then install node with a tool like nvm. Let me know how this works for you!

Thanks for your support @timmydoza I got the issue. My nodu_module folder was assigned under root permission also was facing proxy issue due to which these all errors were coming. Now things are working fine. :+1:

Great to hear @rakeshkk16!!


Update features.md

I am the Product Manager for AWS Deep Learning Containers (https://www.linkedin.com/in/ongjinghan/)
We want to change the hyperlink for DLCs from a general overview page to the one specifically on DLCs for EKS. We think this will be better for customers

Hi @jingong2105, thank you for the contribution. The documentation has been updated since this PR and the link you are trying to change is specific to jupyter notebook server. Lets find a better place for the content you are trying to talk about i.e. training, inference etc on EKS using DLC. Please reach out to @judyheflin.
Closing this PR for now, please reopen with updated changes
/close


[VMAlert] cr.spec.Notifier, cr.spec.notifierConfigRef and discovered alertmanager are empty prevent using flag notifier.blackhole

I am currently using the VictoriaMetrics Operator version: victoria-metrics-k8s-stack-0.18.6.
I want to deploy VMAlert just for using recording rule so I don't need to configure the spec.notifier and I used spec.extraArgs to enable flag notifier.blackhole: "true".
The configuration file looks like this:
apiVersion: operator.victoriametrics.com/v1beta1
kind: VMAlert
metadata:
  name: vmalert-vm-k8s
  namespace: monitoring
spec:
  datasource:
    url: "http://vmselect-vm-k8s-victoria-metrics-k8s-stack.monitoring:8481/select/0/prometheus"
  remoteWrite:
    url: "http://vminsert-vm-k8s-victoria-metrics-k8s-stack.monitoring:8480/insert/0/prometheus"
  remoteRead:
    url: "http://vmselect-vm-k8s-victoria-metrics-k8s-stack.monitoring:8481/select/0/prometheus"
  evaluationInterval: "30s"
  ruleSelector:
    matchLabels:
     metric: "true"
  ruleNamespaceSelector:
    matchLabels:
      kubernetes.io/metadata.name: monitoring
  # for accessing to vmalert via vmauth with path prefix
  extraArgs:
    http.pathPrefix: /vmalert
    notifier.blackhole: "true"

It seems like we have a bug here.
We can not left the cr.spec.Notifier, cr.spec.notifierConfigRef empty If we do the operator can not create VMAlert pod.
But when you enter a random URL just like in the configuration file above, the VMAlert pod shows error:
2023-11-22T08:42:55.943Z	fatal	VictoriaMetrics/app/vmalert/main.go:170	failed to init: failed to init notifier: only one of -notifier.blackhole, -notifier.url and -notifier.config flags must be specified

We should allow notifier and notifiers both to be empty at the first space, since vmalert only needs -notifier.url  when there is alerting rules and operator can't check that.

Should be fixed since 0.39.4, close as completed.

Thank @Haleygo for your support!

I have the same problem. After updating to chart version 0.19.4 with app version v1.99.0 get error message on vmalert
2024-03-08T05:32:06.703Z fatal VictoriaMetrics/app/vmalert/main.go:162 failed to init: failed to init notifier: only one of -notifier.blackhole, -notifier.url and -notifier.config flags must be specified
and I see in pods args
-datasource.url=http://vmsingle-vm-victoria-metrics-k8s-stack.vm.svc:8429/
-evaluationInterval=30s
-external.label=cloud=npe
-external.label=cluster=k8s-pcidss-dev
-httpListenAddr=:8080
-notifier.blackhole=true
-notifier.url=
-remoteRead.url=http://vmsingle-vm-victoria-metrics-k8s-stack.vm.svc:8429/
-remoteWrite.disablePathAppend=true
-remoteWrite.url=http://vmagent-vm-victoria-metrics-k8s-stack.vm.svc:8429/api/v1/write
-rule="/etc/vmalert/config/vm-vm-victoria-metrics-k8s-stack-rulefiles-0/*.yaml"

but in chart I don't write notifier.url arg
my values
vmalert:
  annotations: {}
  enabled: true

  # Controls whether VMAlert should use VMAgent or VMInsert as a target for remotewrite
  remoteWriteVMAgent: true
  # spec for VMAlert crd
  # https://docs.victoriametrics.com/operator/api.html#vmalertspec
  spec:
    selectAllByDefault: true
    image:
      tag: v1.99.0
    evaluationInterval: 30s
    resources:
      limits:
        cpu: "1"
      requests:
        cpu: "600m"
    nodeSelector:
      node-role: victoria-metrics
    tolerations:
      - key: "node-role"
        operator: "Equal"
        value: "victoria-metrics"
        effect: "NoSchedule"
    extraArgs:
      notifier.blackhole: "true"

Hi @iPapanya!
Could you check again the version of the victoriametrics-operator and make sure it's equal 0.39.4 or higher than that?
It's seem like here docker.io/victoriametrics/operator:v0.39.1

@tantm3 @iPapanya Seems like this issue is the same as https://github.com/VictoriaMetrics/operator/issues/894#issuecomment-1984095730. It was fixed in https://github.com/VictoriaMetrics/operator/pull/895 and will be released as a part of the next release.

Hi @iPapanya! Could you check again the version of the victoriametrics-operator and make sure it's equal 0.39.4 or higher than that? It's seem like here docker.io/victoriametrics/operator:v0.39.1

victoriametrics/operator:v0.41.2


feat: UnknownABI that is catch-all for unknown ABIs

What I did

fixes: #
How I did it
How to verify it
Checklist

[ ] Passes all linting checks (pre-commit and CI jobs)
[ ] New test cases have been added and are passing
[ ] Documentation has been updated
[ ] PR title follows Conventional Commit standard (will be automatically included in the changelog)

@fubuloubu  This makes things just work; I am wondering your thoughts


Harden crypto 'key' option: turn off cmdline completion, disable set-=

"set-=" can be used maliciously with a crypto key, as it allows an attacker (who either has access to the computer or a plugin author) to guess a substring by observing the modified state. Simply turn off set+=/-=/^= for this option as there is no good reason for them to be used.
Update docs to make that clear as well.
Also, don't allow cmdline completion for 'key' as it just shows ***** which is not useful and confusing to the user what it means (if the user accidentally hits enter they will have replaced their key with "*****" instead).

Noticed this issue when working on https://github.com/vim/vim/pull/13182

Hm, this throws this error in CI:
In file included from vim.h:1941,
                 from option.c:39:
option.h:21:25: error: unsigned conversion from ‘long long int’ to ‘long unsigned int’ changes value from ‘4294968844’ to ‘1548’ [-Werror=overflow]
   21 | #define P_STRING        0x04    // the option is a string
      |                         ^~~~
optiondefs.h:1470:29: note: in expansion of macro ‘P_STRING’
 1470 |     {"key",         NULL,   P_STRING|P_ALLOCED|P_VI_DEF|P_NO_MKRC|P_NO_CMD_EXPAND,
      |                             ^~~~~~~~
gcc -c -I.       -Iproto -DHAVE_CONFIG_H     -O2 -fno-strength-reduce -Wall -Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -Wall -Wextra -Wshadow -Werror -Wno-deprecated-declarations -Wno-error=maybe-uninitialized   -DEXITFREE      -Wno-error=unused-function -Wno-shadow   -Wno-error=unused-parameter  -o objects/optionstr.o optionstr.c
gcc -c -I. -Iproto -DHAVE_CONFIG_H     -O2 -fno-strength-reduce -Wall -Wno-deprecated-declarations -D_REENTRANT -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -Wall -Wextra -Wshadow -Werror -Wno-deprecated-declarations -Wno-error=maybe-uninitialized   -DEXITFREE     -o objects/os_unix.o os_unix.c

Maybe P_NO_CMD_EXPAND can be set to 0x20, which doesn't have a flag?

I tried the following on top of your patch and it seems to work:
diff --git a/src/option.c b/src/option.c
index e25ef5a9a..fe7f52149 100644
--- a/src/option.c
+++ b/src/option.c
@@ -2968,7 +2968,7 @@ insecure_flag(int opt_idx, int opt_flags)
        }

     // Nothing special, return global flags field.
-    return &options[opt_idx].flags;
+    return (unsigned long int *) &options[opt_idx].flags;
 }
 #endif

diff --git a/src/optiondefs.h b/src/optiondefs.h
index f850d19b1..12370817e 100644
--- a/src/optiondefs.h
+++ b/src/optiondefs.h
@@ -263,7 +263,7 @@ struct vimoption
 {
     char       *fullname;      // full option name
     char       *shortname;     // permissible abbreviation
-    long_u     flags;          // see in option.h
+    long_u8    flags;          // see in option.h
     char_u     *var;           // global option: pointer to variable;
                                // window-local option: VAR_WIN;
                                // buffer-local option: global value
diff --git a/src/vim.h b/src/vim.h
index c78b12b16..342c4c001 100644
--- a/src/vim.h
+++ b/src/vim.h
@@ -364,12 +364,21 @@ typedef unsigned int      int_u;
 // On Win64, longs are 32 bits and pointers are 64 bits.
 // For printf() and scanf(), we need to take care of long_u specifically.
 #ifdef _WIN64
+typedef unsigned __int64       long_u8;
 typedef unsigned __int64       long_u;
 typedef                 __int64        long_i;
 # define SCANF_HEX_LONG_U       "%llx"
 # define SCANF_DECIMAL_LONG_U   "%llu"
 # define PRINTF_HEX_LONG_U      "0x%llx"
+#elif defined(i386) || defined(__i386__) || defined(__i386) || defined(_M_IX86)
+typedef unsigned long          long_u;
+typedef long long int          long_u8;
+typedef                 long           long_i;
+# define SCANF_HEX_LONG_U       "%lx"
+# define SCANF_DECIMAL_LONG_U   "%lu"
+# define PRINTF_HEX_LONG_U      "0x%lx"
 #else
+typedef unsigned long          long_u8;
 typedef unsigned long          long_u;
 typedef                 long           long_i;
 # define SCANF_HEX_LONG_U       "%lx"

not sure if this is the best way to do and keep compatible with i386

Maybe P_NO_CMD_EXPAND can be set to 0x20, which doesn't have a flag?

I could do that. I looked at code history and seems like 0x20 has been missing since Vim 7, so maybe it's some really early flag that got removed and remains unused (didn't feel like digging through older code history since they aren't in the main git repo). We still have to address this problem when we want to add new flags though. I can at least leave a comment there indicating that we need to fix this.
We can either fix this by using a 64-bit int, or two separate flags (e.g. a flag and flag2 variable).

I tried the following on top of your patch and it seems to work:

I'm not a huge fan of declaring a new typedef personally because we may end up running into more compatibility issues on platforms that are not tested in CI, and I find the name confusing (most people think in how many bits a number has, not bytes, so it should be "64", not "8").
Now, since we technically moved to C99 (see #11157 for more discussions), we should technically have access to <stdint.h> which defines the convenient uint64_t for us which seems like what we should use instead (incidentally long_u probably could have been uintptr_t but Vim obviously predates the popularity of C99.
One issue is that I'm not 100% sure if C99 support is fully rolled out. The only real problematic place I see is OpenVMS support, where os_vms_conf.h seems to suggest that the max value of long long under VAX is only 32-bit. Also, the platform undefines HAVE_STDINT_H so we may not have access to the header. Looking around (https://github.com/vim/vim/issues/11157#issuecomment-1327813832 and https://groups.google.com/g/comp.os.vms/c/Bnh3tIOc7bo) I guess only the latest VMS has support for stdint.h and C99. Either way the VMS version of Vim linked to from vim.org (http://www.polarhome.com/vim/) is still on Vim 8.2 so I'm not sure if this is even still technically "supported" or not as Vim only started migrating to C99 in Vim 9 and I didn't see too much discussion about OpenVMS in that discussion.
On this topic, I feel like I don't fully know what the full list of "supported" platforms for Vim are. Maybe that's because it's been a little opportunistic in a "fix it as much as possible" and Vim is used in so many places across different versions that it's hard to have a complete count compared to newer / more controlled editors.

So my suggestion is I just use 0x20 and punt this down the line for the tomorrow version of us 😅.
To properly fix this I would rather just use uint64_t and polyfill it with long long if that's not defined. I would rather use existing C-standard names that is well understood (for flags, it's good to have explicit bitness guarantees).
The docs does say we should have guaranteed long long, but I don't know if that sentence was written with OpenVMS or other obscure platforms in mind:
https://github.com/vim/vim/blob/e379e21ddc2dc12abea9dcfd0708e27788bb568c/runtime/doc/develop.txt#L213-L216

I can find the removal of 0x20 here: https://github.com/vim/vim-history/commit/c3cba9278b34e6ff131e99d5ef39e346176957de

Ok I pushed a new commit to just use the unused 0x20 since I don't want to fix this now :)
Speaking of which, I find some of the flags kind of… suspect. P_DEF_ALLOCED, P_WAS_SET, and P_INSECURE are actually runtime properties on an option, rather than a specification of an option. P_INSECURE also needs to work on window-specific options which is why each window has members like w_p_stl_flags whose existence is just to hold those flags. Personally, if we need more flags in the future, I would refactor those away to a "runtime_flags" first, as it makes a lot more sense to me to separate specification flags and runtime values. It only gives a grand total of 3 additional flags for us to use but I think that's a little clearer anyway.

thanks, looks good now


Fix sealed-secrets-operator base url

Kustomize fails to build the manifest as the folder within the catalog git repo is sealed-secrets-operator and not sealed-secrets
That commit changed the folder name: https://github.com/redhat-canada-gitops/catalog/commit/74ab574caf82562ba64bec1e886012f1e593b97f
Error
Error: accumulating resources: accumulation err='accumulating resources from 'github.com/redhat-canada-gitops/catalog/sealed-secrets/overlays/default?ref=master': evalsymlink failure on '/Users/adetalhouet/tmp/ocp-gitops/apps/00-sealed-secrets/github.com/redhat-canada-gitops/catalog/sealed-secrets/overlays/default?ref=master' : lstat /Users/adetalhouet/tmp/ocp-gitops/apps/00-sealed-secrets/github.com: no such file or directory': evalsymlink failure on '/private/var/folders/p0/7r6t73s915536ksg4s9l_kwr0000gn/T/kustomize-914914193/sealed-secrets/overlays/default' : lstat /private/var/folders/p0/7r6t73s915536ksg4s9l_kwr0000gn/T/kustomize-914914193/sealed-secrets: no such file or directory

Thanks for the fix!


Long-running processes fail with Error: ENOENT: no such file or directory

First off, thanks for this great library!
When setting it up for an existing cypress project, I've noticed that some files that take a while to preprocess will throw an error in the Cypress runner output window:
Error: ENOENT: no such file or directory, stat '/Users/<user>/Library/Application Support/Cypress/cy/production/projects/<project-hash>/bundles/cypress/e2e/<spec>.cy.ts'

After a few minutes of waiting, it seems that Vite builds the file and emits an event for Cypress to rerun, which then it succeeds. I'm wondering if there are some improvements that can be made to the watcher for the preprocessor, but I'm not super familiar with Cypress file preprocessors.
Here is a rough diff for the final return of the process here. I was able to working locally that checks if the ouputFile is ready or otherwise will throw an error. Ideally it would be nice to have Cypress wait longer before outputting anything but I couldn't figure that out:
-    cache[filePath] = outputPath
-    debug("Bundle for file %s cached at %s", filePath, outputPath)
-    return outputPath
+
+    if (fs.existsSync(outputPath)) {
+      cache[filePath] = outputPath
+      debug("Bundle for file %s cached at %s", filePath, outputPath)
+      return outputPath
+    }
+
+    if (shouldWatch) {
+      debug("Bundle not ready while compiling original file %s", filePath)
+      throw Error("Bundle not ready while compiling original file")
+    } else {
+      return filePath
+    }

System info:
  Binaries:
    Node: 16.15.0
    Yarn: 1.22.18
    npm: 8.8.0
    typescript: 4.7.2
  Browsers:
    Chrome: 108.0.5359.124

Hi @jordanandree, thanks for reaching out.
Recently, I experienced the same delay on the first run in one of my projects and it was because of a not-optimized dependency in the app. Obviously, in my case, it wasn't the tests that caused the problem. I'm not sure, but maybe in your case, there is a test utility or some third party that is causing the issue. Can you check to see whether this is true? Or maybe a Vite plugin is causing the issue?
I don't think throwing error is the right way to solve this. I'll try to figure out some way for triggering a rerun when the bundle is ready. And btw, more information about the tests, configuration, etc., or perhaps a reproduction can help me through this.

Hi, thanks for great library like this ! :)
I got same error.
Execute npx cypress open and run e2e test, then Cypress Studio shows the following error.
Error: ENOENT: no such file or directory, stat '/Users/<user>/Library/Application Support/Cypress/cy/production/projects/front-7a0bead4da052e7d0236bfff078df7a5/bundles/cypress/e2e/xxx/xxx.cy.ts

This file exists surely but has extention .ts.js not .ts.
/Users/<user>/Library/Application Support/Cypress/cy/production/projects/front-7a0bead4da052e7d0236bfff078df7a5/bundles/cypress/e2e/xxx/xxx.cy.ts.js

Why and how to fix it ?

cypress.config.ts

import { defineConfig } from 'cypress'
import vitePreprocessor from 'cypress-vite'
import path from 'path'

export default defineConfig({
  viewportWidth: 1000,
  viewportHeight: 1200,
  video: false,
  screenshotOnRunFailure: false,
  e2e: {
    // We've imported your old cypress plugins here.
    // You may want to clean this up later by importing these.
    setupNodeEvents(on) {
      on('file:preprocessor', vitePreprocessor(path.resolve(__dirname, './vite.config.ts')))
    },
    baseUrl: 'http://localhost:8082',
  },
})

Versions

Node: 16.17.0
Cypress: 12.13.0
TypeScript: 4.9.4
vite: 4.0.4
cypress-vite: 1.3.0

snagasawa I am experiencing the exact same problem! I think there is an actual issue with this library but I can't seem to fix it. If anyone knows how to fix this please say

@jordanandree @snagasawa Cypress version 10.11 seems to solve this (with Node 17).

@jordanandree @snagasawa do you confirm that<EMAIL_ADDRESS>solves this?

@oren-legit @mammadataei
Cypress version 10.11 solve this error, although different issue occurred. Thanks. :)
v11.2 still got error.

@snagasawa same error on v11.2?! If so, could you please send me the debug output?
Feel free to open a new issue if you are facing a new error; I'll do my best to resolve it.

I had same error, no output from debug then i matched versions, tsconfigs and vite configs to this example repo. Then i got error RollupError: Invalid value for option "output.manualChunks" - this option is not supported for "output.inlineDynamicImports". and after removing this piece of config from my vite.config.ts it started working.

@MartinN3 Can you clarify in what file and what code you removed to get this working?


Multi-AZ DB cluster parameter?

Hello,
I don't know ACK RDS Controller supports Multi-AZ DB cluster or not. It looks like ACK pretends support multi-AZ DB cluster but I couldn't have found any installation parameters. I would like to install a multi-AZ DB cluster but have been looking for the necessary parameter in documentation. It would be nice if you can put cpl of sentence explain this.
Thanks & Regars

Hi @tirelibirefe currently Multi-Az DB Cluster is not supported due to https://github.com/aws-controllers-k8s/community/issues/1376 - please subscribe to this issue to know get notified when the bug is fixed.

Hello again,
If I install single-zone DBCluster by using ACK, will I be able to convert to multi-AZ DBCluster later after the problem is fixed ?
Thanks & Regards

Hello again,
If I install single-zone DBCluster by using ACK, will I be able to convert to multi-AZ DBCluster later after the problem is fixed ?
Thanks & Regards


to_datetime conversion inconsistency in 0.15.0

to_datetime is not converting input consistently between a pandas series or a python list of either strings or datetime objects.  for example:
import pandas as pd
s = pd.Series(['102214','102314'])
df = pd.Series({'dates':['102214','102314']})
lst = ['102214','102314']
pd.to_datetime(s,format='%m%d%y') and pd.to_datetime(df['dates'],format='%m%d%y') return a numpy.datetime64 ndarray, while pd.to_datetime(lst,format='%m%d%y') returns a pandas.DateTimeIndex object.  Is this behavior an expected result in 0.15.0?

This was closed by #8921


Send from to Defi Bridge failed, can not complete this transaction

Hi,
I have sent defi from my defi address with the
Transaction ID:
dce136b6f26ce201cd9f906eb04363566efd6bb6128b905367456972cb94db1c
To defi bridge address:
8dkpbNfFiaHPSQGKBLa8dBZS8uqFvYHoGk
sent.
That was<PHONE_NUMBER>1 DFI which should be sent to Binance. I sent these over the DefiChain network.
This is the address these should be sent to.
0x7CEE45497fF04A7613D5EB86470A4367087D3Bcf
However, I am unable to complete the transaction.

How can the transaction be completed or I got my DFI back.
Thank you very much.
BR, Henning

Hi,
please on Feedback.
Many thanks.
BR, Henning

Hi, please use the Recovery funtion to receive the DFI on BSC. Below the Button NEXT click on Click here to recover an incomplete transaction. Enter your TXID from Defichain and your BSC-Address and then "Recover".
Please close this Issue when it worked for you.