text:
OKD & Proxmox : 4.11.0 console and authentication not working after bootstrap

Describe the bug
Hi ! I have a problem when boostrap complete : Console and authentication not Ready. I have 503 call :
"APIServicesAvailable: "oauth.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request..."
I have six server proxmox with one "okd-services" contains : DNS server, haproxy, pxe server. And 3 master / 3 worker. Domains calls between nodes / master works (ping test). When i try to access to console : I access on cluster but with the not available screen (same as route not exist in cluster).
Note : I have a home lab proxmox with one server (with 6 VM : 3 master / 3 worker) and it works.
Install configuration :
apiVersion: v1
baseDomain: {{ dns.domain }}
metadata:
  name: {{ dns.clusterid }}
compute:
- hyperthreading: Enabled
  name: worker
  replicas: 3
controlPlane:
  hyperthreading: Enabled
  name: master
  replicas: 3
networking:
  clusterNetwork:
  - cidr: 10.128.0.0/14
    hostPrefix: 23
  networkType: OpenShiftSDN
  serviceNetwork:
  - 172.30.0.0/16
platform:
  none: {}
fips: false
pullSecret: '{{ pull_secret }}'
sshKey: "{{ ssh_pub_key }}"

[root@okd-services ~]# oc get nodes
NAME           STATUS   ROLES    AGE   VERSION
okd-master-1   Ready    master   52m   v1.24.6+5658434
okd-master-2   Ready    master   52m   v1.24.6+5658434
okd-master-3   Ready    master   52m   v1.24.6+5658434
okd-worker-1   Ready    worker   39m   v1.24.6+5658434
okd-worker-2   Ready    worker   39m   v1.24.6+5658434
okd-worker-3   Ready    worker   39m   v1.24.6+5658434

Version
4.11.0-0.okd-2022-12-02-145640
UPI / Platform none
How reproducible
100%
Log bundle
[root@okd-services ~]# oc get clusteroperators
NAME                                       VERSION                          AVAILABLE   PROGRESSING   DEGRADED   SINCE   MESSAGE
authentication                             4.11.0-0.okd-2022-12-02-145640   False       False         True       45m     APIServicesAvailable: "oauth.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request...
baremetal                                  4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
cloud-controller-manager                   4.11.0-0.okd-2022-12-02-145640   True        False         False      46m
cloud-credential                           4.11.0-0.okd-2022-12-02-145640   True        False         False      46m
cluster-autoscaler                         4.11.0-0.okd-2022-12-02-145640   True        False         False      43m
config-operator                            4.11.0-0.okd-2022-12-02-145640   True        False         False      45m
console                                    4.11.0-0.okd-2022-12-02-145640   False       False         True       37m     RouteHealthAvailable: console route is not admitted
csi-snapshot-controller                    4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
dns                                        4.11.0-0.okd-2022-12-02-145640   True        False         False      43m
etcd                                       4.11.0-0.okd-2022-12-02-145640   True        False         False      42m
image-registry                             4.11.0-0.okd-2022-12-02-145640   False       True          True       30m     NodeCADaemonAvailable: The daemon set node-ca has available replicas...
ingress                                    4.11.0-0.okd-2022-12-02-145640   True        False         False      4m11s
insights                                   4.11.0-0.okd-2022-12-02-145640   True        False         False      38m
kube-apiserver                             4.11.0-0.okd-2022-12-02-145640   True        True          False      40m     NodeInstallerProgressing: 2 nodes are at revision 8; 1 nodes are at revision 9
kube-controller-manager                    4.11.0-0.okd-2022-12-02-145640   True        False         True       42m     GarbageCollectorDegraded: error fetching rules: Get "https://thanos-querier.openshift-monitoring.svc:9091/api/v1/rules": dial tcp 172.30.42.204:9091: connect: connection refused
kube-scheduler                             4.11.0-0.okd-2022-12-02-145640   True        True          False      41m     NodeInstallerProgressing: 1 nodes are at revision 7; 2 nodes are at revision 8
kube-storage-version-migrator              4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
machine-api                                4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
machine-approver                           4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
machine-config                             4.11.0-0.okd-2022-12-02-145640   True        False         False      43m
marketplace                                4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
monitoring                                                                  False       True          True       31m     Rollout of the monitoring stack failed and is degraded. Please investigate the degraded status error.
network                                    4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
node-tuning                                4.11.0-0.okd-2022-12-02-145640   True        False         False      43m
openshift-apiserver                        4.11.0-0.okd-2022-12-02-145640   False       False         False      29m     APIServicesAvailable: "apps.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request...
openshift-controller-manager               4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
openshift-samples                          4.11.0-0.okd-2022-12-02-145640   True        False         False      34m
operator-lifecycle-manager                 4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
operator-lifecycle-manager-catalog         4.11.0-0.okd-2022-12-02-145640   True        False         False      43m
operator-lifecycle-manager-packageserver   4.11.0-0.okd-2022-12-02-145640   True        False         False      6m7s
service-ca                                 4.11.0-0.okd-2022-12-02-145640   True        False         False      44m
storage                                    4.11.0-0.okd-2022-12-02-145640   True        False         False      45m

must-gather-okd-20221212.txt

We're gonna need an archive produced by must-gather tool, not its output

@titou10titou10 Thanks.
Yes i check many times. After each bootstrap complete, comment bootstrap on haproxy and stop bootstrap VM. My home lab works fine with one proxmox server.
I have 6 proxmox servers with private mesh VPN (Wireguard). Each server on 192.168.1X.1/24 network.
Server 1 : 192.168.11.1
Server 2 : 192.168.12.1
Server X : 192.168.1X.1
Each server have dnsmasq (config pxe server & attribute VM IP by mac address & configure DNS server).
Example dnsmasq config :
dhcp-range=192.168.11.10,192.168.11.250,12h
dhcp-lease-max=25
dhcp-host=D2:8E:FF:B3:01:73,192.168.11.11,okd-master-1
dhcp-host=12:8E:DE:B3:01:60,192.168.11.100,okd-services
dhcp-option=option:dns-server,192.168.11.100,1.1.1.1
dhcp-boot=pxelinux.0,,192.168.11.100

okd-services (bastion) :
public (enp6s18) : PUBLIC_IP
private (enp6s19) : 192.168.11.100

haproxy
pxe server
dns server (bind)

okd-master-1 : 192.168.11.11
okd-master-2 : 192.168.12.12
okd-master-3 : 192.168.13.13
okd-worker-1 : 192.168.14.21
okd-worker-2 : 192.168.15.22
okd-worker-3 : 192.168.16.23

I have a problem on authentication operators (503) and console not contact oauth (timeout). Very similar : https://github.com/okd-project/okd/issues/430
My bad. The archive :
must-gather.local.1194632374733407674.tar.gz

Try with networkType: OVNKubernetes. Same result.
must-gather archive :
must-gather.local.7911081472470111102.tar.gz

Get \"https://oauth-openshift.apps.cloud.soyouweb.fr/healthz\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)\nOAuthServerServiceEndpointAccessibleControllerDegraded: Get \"https://172.30.138.239:443/healthz\": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

and
"WellKnownReadyControllerProgressing: kube-apiserver oauth endpoint https://192.168.12.12:6443/.well-known/oauth-authorization-server is not yet served and authentication operator keeps waiting (check kube-apiserver operator, and check that instances roll out successfully, which can take several minutes per instance)"

in authentication operator, as kube-apiserver never rolled out:
"NodeInstallerProgressing: 1 nodes are at revision 0; 1 nodes are at revision 3; 1 nodes are at revision 8"

installer pods cannot be created:
"Failed to create pod sandbox: rpc error: code = Unknown desc = failed to create pod network sandbox k8s_installer-8-okd-master-1_openshift-kube-apiserver_62b703a9-0b89-4801-92dc-a6af80a6b611_0(c09814543ff0b731abf40775238958a55b55b10d5c1059d5b47b070163b5d453): error adding pod openshift-kube-apiserver_installer-8-okd-master-1 to CNI network \"multus-cni-network\": plugin type=\"multus\" name=\"multus-cni-network\" failed (add): [openshift-kube-apiserver/installer-8-okd-master-1/62b703a9-0b89-4801-92dc-a6af80a6b611:openshift-sdn]: error adding container to network \"openshift-sdn\": CNI request failed with status 400: 'the server was unable to return a response in the time allotted, but may still be processing the request (get pods installer-8-okd-master-1)\n'"

That looks like a weird networking issue.
Also, must-gather is incomplete, seems its using some user cert and didn't fetch a lot of data from openshift-* namespaces. Could you check if that works using installer-generated kubeconfig? Also try via export KUBECONFIG=/etc/kubernetes/static-pod-resources/kube-apiserver-certs/secrets/node-kubeconfigs/localhost.kubeconfig on masters

Thanks. I think too but i found not the problem.
The must-gather could be complete : https://drive.google.com/file/d/1LMTX6oV4Mz7n5h1rQ5RSIog8G4ccNP_Q/view?usp=share_link

I have 6 proxmox servers with private mesh VPN (Wireguard). Each server on 192.168.1X.1/24 network.

Are you sure the private mesh VPN between the hypervisors isn't interfering here? I'm not 100% sure, but the must-gather does indicate to me some kind of peculiar networking issue outside of the cluster.

I installed new cluster in single proxmox server and it works. I abandon installation on multiple proxmox with private mesh networks. Thanks for your help.

authors: KvnOnWeb melledouwsma vrutkovs

repo: okd-project/okd


text:
Melhorias na Documentação da Toolbox

Como o objetivo do Read the Docs é ser a documentação técnica, dos recursos do Querido Diário, seu conteúdo deve ser enxuto, expondo o suficiente para busca rápidas e localização das respostas facilmente. A referência é a documentação de Python que lista e descreve muito objetivamente para que tal comando serve (exemplo: https://docs.python.org/3/library/string.html?highlight=string#module-string)
Assim, a melhoria na página da Toolbox seria adequá-a nesse modelo de documentação técnica "tradicional", por exemplo:
class Gazette
gazette.extract_content()
explica o que faz
gazette.load_content()
explica o que faz
Para conhecê-los, basta verificar em https://github.com/okfn-brasil/querido-diario-toolbox/tree/main/querido_diario_toolbox as classes que a toolbox oferece e seus métodos. Por enquanto, os módulos em etl não precisam ser incluídos.
Da página já em exibição, o tópico de instalação pode ser mantido, enquanto o tópico de "Exemplos de uso" que deve ser substituido pela listagem das classes/métodos

Adicionalmente: alguns links estão quebrados na página da toolbox

source: gharchive/issue

repo: okfn-brasil/querido-diario-comunidade

license: MIT

license_type: permissive

license_source: github-api


text:
events pages could be easier to navigate

From https://okfn.org/get-involved/ -> "find an event near you" -> https://okfn.org/get-involved/events/ which has a nice listing of international events but nothing near me. This phrasing should link direct to : http://www.meetup.com/OpenKnowledgeFoundation/  (I think).
Also it was hard to find the meetup list at all, i read the main body of https://okfn.org/get-involved/events/ and assumed there was no local events, but then i found a tiny link in the sidebar!  We should have the same content linked from the explanatory text on a page as in the sidebar, here.

WONTFIX

authors: LaurieJ morchickit

repo: okfn/foundation

license: mit

license_source: bigquery


text:
Check contrast and colors

Is this a BUG REPORT or FEATURE REQUEST?:
bug
What happened:
Our button fragment has some color issues.
What you expected to happen:
Everything readable and contrast is ok.
How to reproduce it (as minimally and precisely as possible):
Check the various color testing pages.
Anything else we need to know?:
Can we auto check color contrast/readability on our dev color pages?

We can  run axe using Cypress to test different pages but axe tests the entire accessibility checklist. Do we only want the contract checks?

authors: mpourismaiel stp-ip

repo: okkur/syna


text:
Getting error while committing the code as - Skipped because of errors from tasks

I have configured husky, git hook, and lint-staged together.
It seems it Huskey and Git hooks are configured correctly.
It seems Either I haven't configured the .lintstagerc file correctly.
I have tried reusing either npm command or direct command in the rc file as below
but both have given the same type of error while git commit.
What am I really missing here?
pre-comit-hook-file
#!/usr/bin/env sh
. "$(dirname -- "$0")/_/husky.sh"

npx lint-staged

.lintstagerc
{
    "**/*.{js,jsx}": [
        "npm run prettier --write"
    ]
}

OR
{
    "*.js": "npm run fix:lint",
    "*.scss": "npm run css-fix"
}

✔ Reverting to original state because of errors...
✔ Cleaning up temporary files...
prettier --write [FAILED]
  ❯ ABC/src/XYZ/.lintstagedrc — 25 files (chunk 2/7).…
    ❯ **/*.{js,jsx} — 25 files
      ✖ npm run prettier --write [FAILED]
  ❯ ABC/src/XYZ/.lintstagedrc — 25 files (chunk 3/7).…
    ❯ **/*.{js,jsx} — 24 files
      ✖ npm run prettier --write [FAILED]
  ❯ ABC/src/XYZ/.lintstagedrc — 24 files (chunk 6/7).…
    ❯ **/*.{js,jsx} — 24 files
      ✖ npm run prettier --write [FAILED]
  ❯ ABC/src/XYZ/.lintstagedrc — 24 files (chunk 7/7).…
    ❯ **/*.{js,jsx} — 22 files
      ✖ npm run prettier --write [FAILED]
↓ Skipped because of errors from tasks. [SKIPPED]
✔ Reverting to original state because of errors...
✔ Cleaning up temporary files...
husky - pre-commit hook exited with code 1 (error)

Steps to reproduce
I have configuration files below.
.huskyrc
{
    "hooks": {
        "pre-commit": "lint-staged"
    }
}

package.json
"scripts": {
     "start": "react-scripts start",
     "build": "react-scripts build",
     "test": "react-scripts test",
     "eject": "react-scripts eject",
     "lint": "eslint ./ --ignore-path .eslintignore",
     "fix:lint": "eslint --fix --ext=js --ext=jsx ./src",
     "test:watch": "jest --watchAll",
     "coverage": "npm run test -- --coverage --watchAll=false",
     "preCommit": "npm run coverage && npm run fix:lint && npm run lint",
     "csslint": "stylelint **/*.{css,sass,scss}",
     "css-fix": "stylelint src/**/*.{css,sass,scss} --fix",
     "stylelint-check": "stylelint-config-prettier-check",
     "stylelint-find-rules": "stylelint-find-new-rules -c",
     "prepare": "cd ../../../ && husky install consumer-income-frontend/.husky",
     "lint-staged": "lint-staged",
     "eslint": "eslint --fix ."
 },
"devDependencies": {
     "@isnotdefined/stylelint-plugin": "^1.2.0",
     "@testing-library/jest-dom": "^5.16.2",
     "@testing-library/react": "^12.1.4",
     "@testing-library/react-hooks": "^7.0.2",
     "babel-plugin-module-resolver": "^4.1.0",
     "eslint": "^8.16.0",
     "eslint-config-prettier": "^8.5.0",
     "eslint-plugin-import": "^2.26.0",
     "eslint-plugin-jsx-a11y": "^6.5.1",
     "eslint-plugin-prefer-arrow": "^1.2.3",
     "eslint-plugin-prettier": "^4.0.0",
     "eslint-plugin-react": "^7.30.0",
     "eslint-plugin-react-hooks": "^4.5.0",
     "eslint-plugin-unused-imports": "^2.0.0",
     "husky": "^8.0.1",
     "jest-environment-jsdom-sixteen": "^2.0.0",
     "jest-junit-reporter": "^1.1.0",
     "lint-staged": "^13.0.3"
}

When I run git commit
gives this error log
✔ Reverting to original state because of errors...
✔ Cleaning up temporary files...
prettier --write [FAILED]
  ❯ ABC/src/XYZ/.lintstagedrc — 25 files (chunk 2/7).…
    ❯ **/*.{js,jsx} — 25 files
      ✖ npm run prettier --write [FAILED]
  ❯ ABC/src/XYZ/.lintstagedrc — 25 files (chunk 3/7).…
    ❯ **/*.{js,jsx} — 24 files
      ✖ npm run prettier --write [FAILED]
  ❯ ABC/src/XYZ/.lintstagedrc — 24 files (chunk 6/7).…
    ❯ **/*.{js,jsx} — 24 files
      ✖ npm run prettier --write [FAILED]
  ❯ ABC/src/XYZ/.lintstagedrc — 24 files (chunk 7/7).…
    ❯ **/*.{js,jsx} — 22 files
      ✖ npm run prettier --write [FAILED]
↓ Skipped because of errors from tasks. [SKIPPED]
✔ Reverting to original state because of errors...
✔ Cleaning up temporary files...
husky - pre-commit hook exited with code 1 (error)

development environment

OS:  Windows 11
Node.js: 14.19.0
lint-staged: ^13.0.3

You shouldn't invoke an npm script through lint-staged that runs linters for the entire src directory:
"fix:lint": "eslint --fix --ext=js --ext=jsx ./src",

The point of lint-staged is to supply the list of staged files to your linters:
"*.js": "eslint --fix",

will become for example eslint --fix staged1.js staged2.js

@iiroj  Can you please mention what should be the change in the rc and package.json? I have made this change but not worked.
.lintstagerc
{     "*.js": "eslint --fix" }
and        "*.js": "eslint --fix"      in package.json

repo: okonet/lint-staged


text:
Clarify okteto test --no-cache option

Basically provide some more info to why one might want to disable the caching.

@viddo could you also update this file? that way, the change also apply to current docs version: https://github.com/okteto/docs/blob/main/versioned_docs/version-1.22/reference/okteto-cli.mdx

Ah my bad! Didn't realize we just published the new version. Also noticed we have okteto test docs back to v1.21 so applied for both v1.21 + v1.22, considering the docs clarification is independent from the chart/CLI version.

source: gharchive/pull-request

repo: okteto/docs


text:
Error parsing comment before DDL statement

Very small issue:
In a script if I add a comment before DDL statement, it throws SQL script execution.
(without the comment the script executes fine)

Fixed in 0.20. Comments in DDL-statements will no longer be sent to Cloud Spanner, as Cloud Spanner itself does not accept these as a part of a DDL-statement.

Great! Thanks

authors: olavloite shlomiw

repo: olavloite/spanner-jdbc


text:
[BSO] add =monster for all custom bosses

🚀 Feature Proposal
there is a =monster mally & =monster treebeard, but none of the other custom bosses.

This has been fixed with show_info

Still doesnt apply to some custom bso monsters

authors: LuxrayElite imTURBObro nwjgit

repo: oldschoolgg/oldschoolbot


text:
Cleanup Navigation

This PR Resolves #1364 and #1365
This PR has following changes:

Unnecessary stylings in the navigation.scss removed
Tob Bar and Menus Variables in the settings.scss changed to defaults
Changing Mobile menu Toggle to toggle the Top-Bar instead of the mobile nav inside the top-bar-right

If we are getting rid of the dark-nav-color from the navigation, should it be removed from the off-canvas too?

authors: derweili nitrokevin

repo: olefredrik/FoundationPress


text:
[Bug]: Misleading text about shared references

Your minimal.lua config
irrelevant
Error messages
No response
Log output
irrelevant
Health check output
No response
Describe the bug
It's not really a breaking bug, but more like how the plugin displays shared variables.
> Sharing: ... is added to the next message, but in it does not actually adds any variables to the second message.
Expected behavior is probably - display variables only on the original message.

## Me ─

> Sharing:
> - /tmp/test.txt

#buffer

I'm testing how sharing context works. Display me received file. Short answer, no suggestions on next steps.

## copilot ─

```text
Version 1
```

## Me ─

> Sharing:
> - /tmp/test.txt

How about now?

## copilot ─

```text
Version 1
```

Json log from gd:
--Settings
adapter = "copilot"
n = 1
model = "claude-3.5-sonnet"
max_tokens = 4096
temperature = 0
top_p = 1

--Messages
{ {
    content = "You are an AI programming assistant named \"CodeCompanion\".\nYou are currently plugged in to the Neovim text editor on a user's machine.\n\nYour core tasks include:\n- Answering general programming questions.\n- Explaining how the code in a Neovim buffer works.\n- Reviewing the selected code in a Neovim buffer.\n- Generating unit tests for the selected code.\n- Proposing fixes for problems in the selected code.\n- Scaffolding code for a new workspace.\n- Finding relevant code to the user's query.\n- Proposing fixes for test failures.\n- Answering questions about Neovim.\n- Running tools.\n\nYou must:\n- Follow the user's requirements carefully and to the letter.\n- Keep your answers short and impersonal, especially if the user responds with context outside of your tasks.\n- Minimize other prose.\n- Use Markdown formatting in your answers.\n- Include the programming language name at the start of the Markdown code blocks.\n- Avoid line numbers in code blocks.\n- Avoid wrapping the whole response in triple backticks.\n- Only return code that's relevant to the task at hand. You may not need to return all of the code that the user has shared.\n- Use actual line breaks instead of '\\n' in your response to begin new lines.\n- Use '\\n' only when you want a literal backslash followed by a character 'n'.\n- All non-code responses must use English.\n\nWhen given a task:\n1. Think step-by-step and describe your plan for what to build in pseudocode, written out in great detail, unless asked not to do so.\n2. Output the code in a single code block, being careful to only return relevant code.\n3. You should always generate short suggestions for the next user turns that are relevant to the conversation.\n4. You can only give one reply for each conversation turn.",
    id = 1947269257,
    opts = {
      visible = false
    },
    role = "system"
  }, {
    content = "I'm testing how sharing context works. Display me received file. Short answer, no suggestions on next steps.",
    id = -546777357,
    opts = {
      visible = true
    },
    role = "user"
  }, {
    content = "Buffer ID: 1\nName: test.txt\nPath: /tmp/test.txt\nFiletype: text\nContent:\n```text\n1:  Version 1\n```\n",
    id = -454189760,
    opts = {
      reference = "/tmp/test.txt",
      tag = "variable",
      visible = false
    },
    role = "user"
  }, {
    content = "```text\nVersion 1\n```",
    id = 1226543241,
    opts = {
      visible = true
    },
    role = "llm"
  }, {
    content = "How about now?",
    id = 419434627,
    opts = {
      visible = true
    },
    role = "user"
  }, {
    content = "```text\nVersion 1\n```",
    id = 1226543241,
    opts = {
      visible = true
    },
    role = "llm"
  } }

Reproduce the bug

Share a #buffer with agent
Look as "> Sharing" in second message (unexpected)

Final checks

[X] I have made sure this issue exists in the latest version of the plugin
[X] I have tested with the minimal.lua file from above and have shared this
[X] I have shared the contents of the log file

I love the fact that it does not re-share all the buffer content over and over each message (to keep the context size "leaner"). But I agree there needs to be a way to "update" the content when you want to after changing the buffer. What if a timestamp gets added to the reference for the buffer so you can see when it was shared (and thus the time of content being used from that buffer) and if you include again in a message later the #buffer tag then that means you would like to update the content so it would add an updated copy of the buffer and then would update the timestamp of the buffer in the references list.
thoughts?

So maybe the references say something like:

Sharing:

/tmp/test.txt (as of 10:15 AM)

> Sharing: ... is added to the next message, but in it does not actually adds any variables to the second message.

My logic for this is that once you add a reference (i.e. a buffer or a file) to the chat buffer, it becomes part of the payload which is sent with every request to your LLM. I chose the verb "sharing" because that's exactly what's happening with every message you send. If I'd have used  > Added ... then I think that could be interpreted to mean the reference was added with that message.
There's a fine line to tread in the chat buffer between useful information and visual bloat. This was a feature I hadn't intended to add but acknowledged that for some users it was really useful.
I'm also planning a lot of features related to this e.g. sticky/updateable references on every request and the ability to modify references on the fly.
Closing this as it's not a bug but will transfer to a discussion.

authors: GitMurf last-partizan olimorris


text:
Add trailing commas to multi-line objects and arrays

Enable the comma-dangle eslint rule.
Add yarn format to fix eslint issues.
Fix a handful of comma-dangle issues.
Note: a couple of concessions are made, in order to prevent a large number of changes that woud likely cause merge conflicts with outstanding branches:

comma-dangle is a warning, not an error
files in src aren't fixed

Required
Changes must conform to these requirements:

[x] yarn test passes.  All new and existing tests pass.
[x] yarn lint passes. All new code follows the code style of this project.

Aspirational
We don't yet require these, but they are nice to have:

[x] New code is covered by new or existing tests.
[x] Changed code is covered by new or existing tests.

I experimented with adopting all of AirBnB style, but it required either a large number of exceptions (work in progress here), or a large number of code changes (log here — note that that's with all the exceptions in the previous link). Later we might want to adopt at least semi and quotes, when there's not as much work in branches.

repo: olinlibrary/abe-web


text:
Update NON_MECHANIZABLE_COST and INSURANCE_PERCENTUAL_COST

Os Correios realizarão duas alterações a partir do dia 10/09:

O valor da cobrança adicional de manuseio especial por formato e dimensão passará para R$ 79,00 (setenta e nove reais - o valor hoje é 20,00) a partir de 10/09/2018.

Os percentuais de Ad Valorem do serviço adicional de Valor Declarado, relativos aos serviços de encomendas, serão reajustados de 0,7% para 1% nas postagens a faturar

Este PR visa ajustar os dois pontos citados

Good point @lamenezes. We intended to release Monday morning. I will label as do-not-merge

repo: olist/correios


text:
Checking for clearing chat history

Resolves #149. Also did some quick Tailwind cleanup by moving individual self-center to group items-center.

LGTM, Thanks!

repo: ollama-webui/ollama-webui


text:
404 on /api/chat

Hi,
I started ollama serve w/o issue
Then I tried ollama.list() which returned the 3 models I have pulled with a 200 code on /api/tags. One of these models is 'mistral:latest'
Then I tried ollama.show('mistral') and it returned an object with a license, a modelfile, ... and a code 200 on /api/show
Up to now, everything fine...
Then I tried the chat example code:
response = ollama.chat(model='mistral', messages=[
  {
    'role': 'user',
    'content': 'Why is the sky blue?',
  },
])
print(response['message']['content'])

and here I get a 404 code on /api/chat
$ python ollama-test.py
Traceback (most recent call last):
  File "/home/olivi/devt/ollama/ollama-test.py", line 9, in <module>
    response = ollama.chat(model='mistral', messages=[
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/olivi/miniconda3/envs/ollama/lib/python3.11/site-packages/ollama/_client.py", line 158, in chat
    return self._request_stream(
           ^^^^^^^^^^^^^^^^^^^^^
  File "/home/olivi/miniconda3/envs/ollama/lib/python3.11/site-packages/ollama/_client.py", line 81, in _request_stream
    return self._stream(*args, **kwargs) if stream else self._request(*args, **kwargs).json()
                                                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/olivi/miniconda3/envs/ollama/lib/python3.11/site-packages/ollama/_client.py", line 57, in _request
    raise ResponseError(e.response.text, e.response.status_code) from None
ollama._types.ResponseError: 404 page not found

In the ollama server terminal:
[GIN] 2024/01/28 - 09:49:50 | 200 |       281.8µs |       127.0.0.1 | GET      "/api/tags"
[GIN] 2024/01/28 - 09:49:50 | 200 |         405µs |       127.0.0.1 | POST     "/api/show"
[GIN] 2024/01/28 - 09:56:49 | 404 |        24.4µs |       127.0.0.1 | POST     "/api/chat"

Than I tried:
response = generate('mistral', 'Why is the sky blue?')
print(response['response'])

which worked fine (code 200 on /api/generate')
So why a 404 on /api/chat? Is it because of an error in the lib or because mistral does provide a chat API?

Update: I was running ollama 0.1.9. After updating to 0.1.22, it started working...

repo: ollama/ollama-python


text:
Install NPM

Hello guys, not sure if here is the right place to ask questions. I am new to GitHub.
In the readme file, I cant move forward at the step 'npm install'. The git interface says it doesnt know the command.
Any suggestion on how to fix this issue, pls?
Cheers.

ok all sorted.

repo: ollelauribostrom/rebus


text:
Button Remap doesnt work

Hello,
I have tried to remap button TRAFFIC to APP but no success. Unit 5Q0035874C and display unit 5E0919605J.
Car is Skoda Octavia MK3.
Backup is attached including photo.
configurationmanager_Backup.zip

Try this one https://github.com/olli991/mib-std2-pq-zr-toolbox/archive/refs/heads/master.zip


text:
Please add LG AeroTower Air Purifying Fan

It has Air Purifying and Heating.
Please, i need your help. Thank you.

You must attach integration diagnostics.

You must attach integration diagnostics.

config_entry-smartthinq_sensors-ac04b66f03530b973951ca337b690a44.json (1).txt
Here it is!
I appreciate your help very much.


text:
Link do Discord Expirou

Descrição do Bug:
Ao ir nas configurações (menu no canto superior direito) e ir na opção "Discord", o aplicativo redireciona o usuário, porém ao ir para o discord o discord avisa que o link foi expirado
Passos Reproduzidos:

Abra o app
Entre no menu no canto superior direito
Clique na opção "Discord"

Resultado Esperado:
Redirecionar o usuário ao discord com uma tela de convite ao suposto servidor.
Resultado Obtido:
Tela de "convite expirou"
Screenshots:
https://user-images.githubusercontent.com/71888091/126051986-89c81478-2462-46ed-9dbb-6ff2f3f68b2b.mp4
Versão do app:
Versão 0.1.0

I confirm that the bug is still present 🐛

Subi um PR fixando o link do discord para um link permanente sem limite de usos, muito obrigado pelas contribuições @ludovicobesana @IgorVini25

authors: IgorVini25 ludovicobesana matuella

repo: olmps/memo


text:
Implement file storage with an item pipeline

This commit introduces a change in a general Crawly Data Storage Worker.
Now the worker is not responsible for storing the item itself. And
this work is expected to be done by a pipeline.
Also file_storage_pipeline is added.

Todo:

[ ] Fix coverage tests (FilesPipeline is not covered yet)
[ ] Update docsify documentation (deprecated settings)
[ ] Write a comment why we're not doing the File.close in the pipeline, so it's clear to readers

I've renamed the pipeline to WriteToFile, updated relevant docs sections. I've also written a simplified unit test with file assertions.

👍 Still need to do something with coveralls. Maybe we should decrease the required coverage a bit. I think we could try to aim 85% for example?

i agree, coverage != good code

@Ziinc now the build is passing. So if it's ok with you lets merge it?

The use of global configs for pipelines makes me a little uncomfortable, but i think that's for another issue/PR.
I fixed a typo; looks good to merge

authors: Ziinc oltarasenko

repo: oltarasenko/crawly


text:
select is undefined

Why get select is undefined ??
<select id="ddlCaja01" runat="server" name="ddlCaja01"                              data-role="select" data-add-empty-value="true" data-clear-button="true"                             data-on-item-select="onItemSelect"                             style="width:100px"  />
function onItemSelect(el) {                 var select = $(el).data('select');         console.log(select.val());     }

https://metroui.org.ua/components-api.html

select is undefined
usign your example https://github.com/olton/Metro4-Docs/blob/master/public_html/examples/ajax/select.html
tks for your time

And..? Example work fine https://metroui.org.ua/examples/ajax/select.html without errors

repo: olton/Metro-UI-CSS


text:
Icon Name

Minimal: There is an icon named as "spoon-knife" but the icon shows spoon and fork

fixed, thanks

authors: olton renielcanlas


text:
🛑 UoD SLS OMERO (4063) is down

In 04c2e11, UoD SLS OMERO (4063) (nightshade.openmicroscopy.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UoD SLS OMERO (4063) is back up in 3dc0dcc after 1 day, 23 minutes.

repo: ome/upptime


text:
🛑 UoD SLS OMERO (image 3925540 - render_thumbnail) is down

In 03202da, UoD SLS OMERO (image 3925540 - render_thumbnail) (https://omero.lifesci.dundee.ac.uk/webgateway/render_thumbnail/3925540/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: UoD SLS OMERO (image 3925540 - render_thumbnail) is back up in 1fb1811 after 634 days, 11 hours, 40 minutes.


text:
Add checking for rights before start on Azure pipeline

It can save us a lot of time. We need to add checking for all needable rights before start of the application on pipeline. So pipeline should be stopped without running of tests in case of absence of rights. We need the rights to write on an external storage and an internal one.

Discussed and decided not to implement


text:
Random failed test on integration test

    merge utxos
Faucet sent 0.1 ETH on root chain to 0x9cf61985fe593ee0454accf532173e3a40eccf62
Waiting for ETH balance...  (1)
Waiting for childchain balance...  (1)
Waiting for childchain balance...  (2)
Waiting for childchain balance...  (3)
Waiting for childchain balance...  (4)
Waiting for childchain balance...  (1)
Waiting for childchain balance...  (2)
Waiting for childchain balance...  (3)
      1) should merge utxos to a single utxo

  20 passing (17m)
  1 failing

  1) mergeUtxoTest.js
       merge utxos
         should merge utxos to a single utxo:
     Error: submit:client_error, submit:utxo_not_found
      at parseResponse (/home/circleci/project/packages/omg-js-childchain/src/rpc/rpcApi.js:84:9)
      at Object.post (/home/circleci/project/packages/omg-js-childchain/src/rpc/rpcApi.js:64:12)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      at async Context.<anonymous> (/home/circleci/project/packages/integration-tests/test/mergeUtxoTest.js:107:7)

😢😢😢😢😢 I am seeing this too

This is resolved with https://github.com/omgnetwork/omg-js/pull/330. was due to test ordering.

authors: boolafish jarindr nicholasmueller

repo: omgnetwork/omg-js


text:
Integration specifications

In order for other implementation teams to use plasma-contracts correctly and successfully we need to provide an integration document.
Issue Type
[ ] bug report
[x] feature request

Current Behavior
Not aware of any existing technical specs.
Expected Behavior
Similar to
https://stripe.com/docs/payments
https://www.emvco.com/emv-technologies/src/ (scroll to specifications)
Steps to Reproduce
/
Suggested Fix
/
Motivation for Change
System Specs
/

This should specifically address the ALD implementation.

[NOTE]
sigh, I wasn't able to find a way to use the following two tools to automatically generate the doc but worth note it here: (and hopefully some smart people can find out some way to do this clever XDD)

https://github.com/OpenZeppelin/solidity-docgen
https://github.com/DigixGlobal/doxity

I think current issue is that truffle uses solc-js and the tool uses solc. We have code importing external libraries (eg. from openzeppling) and solc would fail on compilation.

Hey, let's continue conversation on this GH issue here @kevsul . I believe it was @paulperegud who worked on the integration spec prior to this. Could you help take a look at what we have thus far and what is necessary to have a) brief walkthrough of all flows and b) details on the expected API call req and response ?

GOOOD NEWS!!!!! Finally find one tool that does not need to do the stupid compilation :p
https://github.com/CYBRToken/solidoc
I tried it locally and it was able to auto generate the doc files from code documentation!!

Very nice @boolafish.
I think we can use this for all kinds higher level documentation to reference to. Can we get this merged?

authors: InoMurko Pongch boolafish thec00n

repo: omisego/plasma-contracts


text:
PAID ACCOUNT!!

Description
The program fails when attempting to scrape data using Google Maps Scraper Pro. The issue arises during the execution of a Python script, where it attempts to download and use ChromeDriver for Chrome version 119. The script fails to find or move the ChromeDriver file, resulting in a FileNotFoundError.
Steps to Reproduce

Activate the Anaconda environment using source /opt/homebrew/anaconda3/bin/activate /opt/homebrew/anaconda3.
Navigate to the directory containing the google-maps-scraper-pro-master.
Run the script using python main.py.
Observe the script attempting to download ChromeDriver for Chrome version 119.
Encounter the error indicating that the ChromeDriver for the installed Chrome version cannot be found, followed by a FileNotFoundError.

Expected behavior: The script should download the appropriate version of ChromeDriver, move it to the specified directory, and proceed with the scraping task without errors.
Actual behavior: The script fails to find or move the ChromeDriver file, resulting in a FileNotFoundError, and halts the scraping process.
Reproduces how often: This issue occurs consistently whenever the script is run.
Additional context

Chrome Version: Ensure that the Google Chrome version installed matches the ChromeDriver version the script attempts to download. This can be checked in Google Chrome at chrome://version.
Manual Installation of ChromeDriver: If automatic downloading of ChromeDriver fails, manually download the appropriate version from the ChromeDriver downloads page and ensure it's accessible to the script.
Python and Library Versions: Verify that the Python version (Python 3.9 in this case) is compatible with all used libraries and frameworks.
Script Review: Examine the script for any hardcoded paths or version numbers that might cause issues.
Environment and Permissions: Check for any environment issues or file permission problems that might prevent the script from downloading or moving files.
Dependencies: Ensure all dependencies are correctly installed and up-to-date in the Python environment.
Documentation and Support: Consult the documentation or support forums for the tool or libraries being used for additional guidance or known issues.
Debugging Approach: Consider adding debug statements in the script to trace the execution flow and identify where exactly it fails.

Avoid relying on screenshots for sharing code or error messages; instead, use text format, possibly formatted with GitHub Flavored Markdown for clarity.

Fixed using https://github.com/omkarcloud/google-maps-scraper/issues/68

repo: omkarcloud/google-maps-scraper


text:
The current build fails to pick up PGDG PostgreSQL server include files on Ubuntu Noble

The build doesn't account for the fact that, on some systems (E.G. Ubuntu Noble LTS), server development files are packaged separately from client development files.

Resolved in #633

authors: dysinger yrashk

repo: omnigres/omnigres


text:
Add timeout parameter to omni_txn.retry procedure

Problem:
The current implementation of the omni_txn.retry function uses a max_attempts parameter to control how many times a transaction should be retried. However, this approach does not allow specifying how long the system should continue retrying, which makes it difficult to control the overall retry duration. As a result, transactions may attempt retries beyond a practical time limit, potentially leading to longer-than-desired delays or system timeouts.
Solution:
The omni_txn.retry function has been updated to introduce a timeout parameter, which specifies the maximum duration (in milliseconds) for which retry attempts should be made. This allows for more fine-grained control over retry behavior by setting a time limit for retry attempts, rather than relying solely on the number of attempts.
Additionally, the following updates have been made:
-Test cases in retry.yml have been updated to include scenarios that validate the timeout functionality.
-The function implementation has been refactored to ensure the new parameter integrates smoothly with the existing logic while maintaining readability.
This solution provides a more flexible way to handle transaction retries by focusing on time-based limits instead of only retry counts, thus improving the practical applicability of the retry mechanism.

hey @yrashk please this PR

Thank you for sending the PR. It doesn't look like it compiles at the moment, though.

Hi @yrashk ,
Thank you for reviewing my pull request and for bringing the compilation issue to my attention. I appreciate your feedback.
I will investigate the compilation errors and make the necessary adjustments to ensure that the code compiles successfully. Specifically, I will look into the conflicting function signature for TimestampDifferenceExceeds and any other issues that may arise.
Once I have resolved the compilation issues, I will update the PR accordingly. Thank you for your patience, and I will keep you posted on my progress.

hey @yrashk why i am getting this error ??

hey @yrashk why i am getting this error ??

Chances are this is because you are not dropping the latest version of retry (this is masked by if exists in droppage) and then when you're commenting on it, Postgres can't choose a specific version to comment on because there's more than one.


text:
Problem with Relation/Way polygon mapping during import (a.k.a. New Zealand is shrinking)

Context
I am trying to import polygons corresponding to regions of interest.  In general, it is working really well, so thanks for some great software.
Expected Behavior
I am importing admin_level=2 for New Zealand, and would expect to find a row with osm_id=556706 and name=New Zealand/Aotearoa
https://www.openstreetmap.org/relation/556706
Actual Behavior
Instead, I get a row with osm_id=196244129, which corresponds to a (random?) way that is just one part of the overall New Zealand relation.
https://www.openstreetmap.org/way/196244129
Steps to Reproduce
In the attached file, there are a few shell scripts that will reproduce nicely.
issue.zip

Run setup.sh (will download the dataset and create a subset with just the admin_level=2 items).  Note that this also runs 'osmium check-refs' to make sure the datasets are OK.
Run import.admin_2.sh.  This will import the full new-zealand-latest dataset, but use an imposm3 filter to only bring in admin_level=2 items.  It then does a query showing the unexpected result.
Run import.subset.sh.  This will import the small new-zealand-latest.subset dataset, but uses the reference 'example-mapping.json' file.  Again, a query is performed that shows the unexpected result.
Run import.all.sh.  This will import the full new-zealand-latest dataset, using example-mapping.json.  Again, a query is performed showing that the sole admin_level=2 item is not what was expected.

Context
Something is wrong here.  It could be:

My understanding of OpenStreetMap data relationships
A fault in the source OpenStreetMap dataset
My incorrect usage of the imposm3 tool - in particular maybe I need to use relation_member, however I cannot get this to work correctly (and the current docs indicate this should not be necessary - https://imposm.org/docs/imposm3/latest/mapping.html - see the section on relation_types)
A bug/feature in imposm3 related to the handling of multipolygon import

Either way, if someone who knows a bit more about this can take a look and give me some suggestions/workarounds, that would be greatly appreciated.
Your Environment
PostgreSQL 9.5.6 on x86_64-pc-linux-gnu, compiled by gcc (Alpine 6.2.1) 6.2.1 20160822, 64-bit
imposm3-0.4.0dev-20170519-3f00374-linux-x86-64.tar.gz
Regards,
Glen.

@glenharris :

Something is wrong here. It could be:
2. A fault in the source OpenStreetMap dataset

see  osmium check-refs -r  result:   Ways      in relations missing: 140
$ osmium check-refs -r -i new-zealand-latest.subset.osm.pbf
w195461062 in r556706
w195461053 in r556706
w195461065 in r556706
w195461046 in r556706
w195461066 in r556706
w195461067 in r556706
w195461072 in r556706
w195461074 in r556706
w195461071 in r556706
w195461057 in r556706
w195461069 in r556706
w195461059 in r556706
w195461055 in r556706
w195461050 in r556706
w195461058 in r556706
w195461045 in r556706
w195461056 in r556706
w196197784 in r556706
w196197761 in r556706
w196197795 in r556706
w196197778 in r556706
w196197777 in r556706
w196197790 in r556706
w196197788 in r556706
w196197764 in r556706
w196197789 in r556706
w196197780 in r556706
w196197769 in r556706
w196197767 in r556706
w196197770 in r556706
w196197773 in r556706
w196197792 in r556706
w196197763 in r556706
w196197786 in r556706
w196197768 in r556706
w196197776 in r556706
w196197762 in r556706
w196197794 in r556706
w196197775 in r556706
w196197793 in r556706
w196197782 in r556706
w196197779 in r556706
w196197783 in r556706
w196197771 in r556706
w196197766 in r556706
w196197781 in r556706
w196197787 in r556706
w196197785 in r556706
w196197765 in r556706
w196197774 in r556706
w196197772 in r556706
w196215225 in r556706
w196215211 in r556706
w196215216 in r556706
w196215223 in r556706
w196215212 in r556706
w196215221 in r556706
w196215214 in r556706
w196215226 in r556706
w196215224 in r556706
w196215220 in r556706
w196215217 in r556706
w196215215 in r556706
w196215219 in r556706
w196215222 in r556706
w196215213 in r556706
w196215218 in r556706
w197085365 in r556706
w197085367 in r556706
w197085390 in r556706
w197085415 in r556706
w197085348 in r556706
w197085398 in r556706
w197085360 in r556706
w197085437 in r556706
w197085372 in r556706
w197085382 in r556706
w197085418 in r556706
w197085358 in r556706
w197085445 in r556706
w197085412 in r556706
w197085428 in r556706
w197085425 in r556706
w197085403 in r556706
w197085387 in r556706
w197085400 in r556706
w197085379 in r556706
w197085406 in r556706
w197085461 in r556706
w197085476 in r556706
w197085430 in r556706
w197085464 in r556706
w197085480 in r556706
w197085384 in r556706
w197085377 in r556706
w197085422 in r556706
w197085434 in r556706
w197085440 in r556706
w197085369 in r556706
w197085374 in r556706
w197085451 in r556706
w197085362 in r556706
w197085458 in r556706
w197085466 in r556706
w197085488 in r556706
w197085393 in r556706
w197085395 in r556706
w197085409 in r556706
w197085353 in r556706
w197085467 in r556706
w197085481 in r556706
w197085472 in r556706
w197091406 in r556706
w197091385 in r556706
w197091431 in r556706
w197091420 in r556706
w197091364 in r556706
w197091315 in r556706
w197091434 in r556706
w197091331 in r556706
w197091368 in r556706
w197091324 in r556706
w197091350 in r556706
w197091425 in r556706
w197091339 in r556706
w197091366 in r556706
w197091328 in r556706
w197091375 in r556706
w197091416 in r556706
w197091393 in r556706
w197091361 in r556706
w197091371 in r556706
w197091342 in r556706
w197091383 in r556706
w197091402 in r556706
w197091380 in r556706
w197091318 in r556706
w197091389 in r556706
w197091399 in r556706
w197091411 in r556706
[======================================================================] 100%
There are 13792 nodes, 687 ways, and 1 relations in this file.
Nodes     in ways      missing: 0
Nodes     in relations missing: 0
Ways      in relations missing: 140
Relations in relations missing: 0

Ah, thanks for that.  For anyone browsing this thread, I ran
'osmium check-refs .osm.pbf', which gave no errors.  However, it appears as though this command does not check the relations (just the ways), and so the correct command should have been
'osmium check-refs --check-relations .osm.pf' (or osmium check-refs -r .osm.pbf).
I am just about to go through the process again using the planet dataset, so I will update this issue once that has completed.

authors: ImreSamu glenharris


text:
[WIP] Omnirepo

Please provide description of the purpose of this pull request, as well as its
motivation and context.
Use omnivector PPA for installing slurm on Ubuntu.
Bundle to use for testing:
name: Omnivector Slurm Distribution
description: OSD

applications:
  slurmctld:
    charm: slurmctld
    num_units: 1
    use-osd-stable-repo: false
  slurmd:
    charm: slurmd
    num_units: 1
    options:
      custom-slurm-repo: "ppa:srcc/slurm-wlm"
  slurmdbd:
    charm: slurmdbd
    num_units: 1
  slurmrestd:
    charm: slurmrestd
    num_units: 1
  percona-cluster:
    charm: cs:percona-cluster-293
    series: bionic
    num_units: 1
relations:
  - [slurmdbd:db, percona-cluster:db]
  - [slurmctld:slurmdbd, slurmdbd:slurmdbd]
  - [slurmctld:slurmd, slurmd:slurmd]
  - [slurmctld:slurmrestd, slurmrestd:slurmrestd]

Depends on https://github.com/omnivector-solutions/slurm-ops-manager/pull/67
How was the code tested?
make tests passed locally :)
Final checklist

[ ] I am the author of these changes, or I have the rights to submit them.
[ ] I added the relevant changed to the README and/or documentation.
[ ] I self reviewed my own code.
[ ] I updated the CHANGELOG according to the contributing
guide

Nice work 👍

authors: heitorPB jamesbeedy

repo: omnivector-solutions/slurm-charms


text:
Send current value of the slider + level meter

Hi,
I want to use rotary encoder + led ring like https://modwiggler.com/forum/viewtopic.php?t=217920
Do you thing it's possible to send the current value of the slider with it's level ?
Thanks !

Hi there @fensoft, thanks for writing!
It's definitely possible to make deej work with rotary encoders, but it's not inherently supported in the main version of deej which is aimed only for use with potentiometers.
I recommend you to check out a fork with encoder support such as Orotavia/deej, or to ask around in the #coding-help channel on our community Discord server to help you set something similar up for yourself.
Good luck :)

I'm speaking about the go windows client, not the arduino software.
I just want some kind of feedback from the serial port.
Thanks !

Ah, you would need two-way communication for that. This is outside my scope, but you can try to look for a fork which does this or ask around in the Discord :)

authors: fensoft omriharel

repo: omriharel/deej


text:
144 remove inventory modals

https://github.com/on-site/StockAid/issues/144

:sheep: :dash:

authors: slinkeOSM yazfaz

repo: on-site/StockAid


text:
add excerise details page

add excerise details page and amend css slightly

I had error in so please ignore this push I am going to push a new branch that's is working


text:
The figures in "oneAPI GPU Optimization Guide" are broken

oneAPI GPU Optimization Guide: https://www.intel.com/content/www/us/en/docs/oneapi/optimization-guide-gpu/2023-2/intel-xe-gpu-architecture.html

@GHGmc2 The figures seem to be working for me now. Are you still having this issue?
If not, I will close out this issue.

https://www.intel.com/content/www/us/en/docs/oneapi/optimization-guide-gpu/2023-2/intel-xe-gpu-architecture.html

It works now, thanks!

repo: oneapi-src/oneAPI-samples


text:
How can I add login_hint as a parameter in Auth.login method

https://github.com/onelogin/java-saml/blob/master/toolkit/src/main/java/com/onelogin/saml2/Auth.java#L332
I don't see a way, how to add custom parameter, is that possible?

There is no way to add a custom parameter to the method, but not hard to support it at all:
You can call login with stay=true, then you will get an URL string from the login method.
Concat to the string the login_hint=xxx and then execute a redirection to the result URL string.

Hi @hamusi,
I added an easy way to add extra parameters to the login and login method
A new HashMap parameter that could contain the extra GET parameters you wanted to sent.
See https://github.com/onelogin/java-saml/commit/ec3af78bd6836fc98b27bac79099cb27a817a0f5

authors: hamusi pitbulk

repo: onelogin/java-saml


text:
Certificate empty variable

Use an array with the settings data, in the array I declare  'x509cert' => 'xxxxx' and 'privateKey' > 'nnn'.
That works without any problem until I change authnRequestsSigned = true in the security array. When I set that to true it throws an error:
[2017-10-09 18:03:05] WEB.ERROR: SP Private key not found. Exception Type: OneLogin_Saml2_Error [] {"uid":"8a93698","method":"GET","route":"/saml/metadata","userId":null}
That error are thrown from https://github.com/onelogin/php-saml/blob/6ab8488da916744d6816589ab2d0330a17c060d8/lib/Saml2/Settings.php#L604-L613
Because the cert and key are not found from the SP array in settings.php
https://github.com/onelogin/php-saml/blob/6ab8488da916744d6816589ab2d0330a17c060d8/lib/Saml2/Settings.php#L691-L701
It works if I create sp.srt and sp.key and put them in the /certs folder. Is there a way of using array instead? Could it be a problem with $this->_sp['x509cert']?

https://github.com/onelogin/php-saml/blob/master/settings_example.php#L66
Explained here

Thanks @pitbulk for looking in to this. I think I understand the documentation regarding how to handle certificate and key for SP.
Thought I could choose to provide the SP crt and key via array OR file. The array method doesn't work using security.
Just close the ticket if it is irrelevant or don't hesitate to get back and I can try to reproduce step by step.
Brgd
Fredrik

Maybe you are not defined the value on the array properly.
When you set the value on the array, the data is loaded by _loadSettingsFromArray
        if (isset($settings['sp'])) {
            $this->_sp = $settings['sp'];
        }

so when the getSPcert method is called, that method should read and return the
$this->_sp['x509cert'] value, and checkSPCerts should return true if also a privateKey was defined.
Can you debug your app and at php-saml/lib/Saml2/Settings.php try print  values of:

$sp['x509cert']
$sp['privateKey'].

My skills how php-saml are implemented into the xibo are limited. But i works perfect expect the SP certificates in the array. Sorry I can't provide you with more detailed debug but here are some :-(
Implementation in xibo $authentication = new \Xibo\Middleware\SAMLAuthentication(); and then the array SAML as its authentication provider.
I have it up and running with the sp.crt and sp.key  in vendor/onelogin/php-saml/certs/. No problem at all!
If I remove/rename sp.crt and sp.key from vendor/onelogin/php-saml/certs/ and put the values into the array 'sp' => array 'x509cert' => 'my cert' and 'privateKey' > 'my key with bits=4096' both are in one line and comments are removed.
The error when truying to login again is ~100 lines:
[2017-10-19 12:44:53] WEB.ERROR: Invalid array settings: sp_certs_not_found_and_required Exception Type: OneLogin_Saml2_Error [] {"uid":"ebd2658","method":"GET","route":"/login","userId":null} [2017-10-19 12:44:53] WEB.ERROR: Invalid array settings: sp_certs_not_found_and_required Exception Type: OneLogin_Saml2_Error [] {"uid":"81b1acd","method":"GET","route":"/login","userId":null} ... ...
Thanks for taking time.
Brgd
Fredrik

Hi @flysen,
What version of php-saml are you using?
I noticed that xibo at Xibo is set the 2.10 version. Can you try and install the latest?
The SAML Auth object is initailized as follows:
$auth = new \OneLogin_Saml2_Auth($this->app->configService->samlSettings);

and that $samlSettings is initalized here.
You should add there a
print_r($samlSettings);

to see if the 'x509cert' and 'privateKey' is there... if is there means that something is wrong with the php-saml module. If is not there means that something removes its values, that you had set on the saml settings file..
P.S I created the first SAML attempt on  Xibo, but it changed a lot :)

Morning @pitbulk thanks for taking time.
I've added the print_r and can confirm that the privateKey are missing in the array:
settings.php (key and crt are truncated by me)
... 'sp' => array (         'entityId' => 'https://diskus-demo.ub.uu.se/saml/metadata',         'assertionConsumerService' => array (             'url' => 'https://diskus-demo.ub.uu.se/saml/acs',         ),         'singleLogoutService' => array (             'url' => 'https://diskus-demo.ub.uu.se/saml/sls',         ),         'NameIDFormat' => 'urn:oasis:names:tc:SAML:2.0:nameid-format:transient',         'x509cert' => 'MIIFAzCCAuugAwIBAgIJAONjaHZu0gBEMA0GCSqGSIb3DQEBCwUAMB8xHTAbBgNVBAMTFGRpc2t1cy1kZW1vLnViLnV1LnNlMB4XDTE3MTAwNTE0MTgwNVoXDTI3MTAwMzE0MTgwNVowHzEdMBsGA1UEAxMUZGlza3VzLWRlbW8udWIudXUuc2UwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQC7TVocn7onWp4lnTIBFETrHkW3FWi78t/vqaRu/FodUpJFXCSjvYUKNcsX0krwA8s...',         'privateKey' > 'MIIJQQIBADANBgkqhkiG9w0BAQEFAASCCSswggknAgEAAoICAQC7TVocn7onWp4lnTIBFETrHkW3FWi78t/vqaRu/FodUpJFXCSjvYUKNcsX0krwA8sDsZxOxQnlbyY2BE0byA/fe9bz43BDhJ30FJPFQlC+1oNJbTchYIEtr84GzxThZJ4EAh0AE7X+4NjJOsLmjUeDU5cQhVZwmvNEFA9R4LBoJaGksXYGSGIpEVu0sUmDBVjz+1Z1HL1Kyogim4mDDhIdDYIvAT5TzQyNCfRtrk+hr/L38/8mvlkEIRpipBVveQR+PaQxK1/3NGNoLaxJ4IbJvUP+iQifeL1/yR/UwBeEHRhyO+QFEvgGArFidGvlhI5XgO6O1v2tzwd5T9biIbnP1uQL...', 	'security' => array (         	'nameIdEncrypted' => false,        		'authnRequestsSigned' => true,         	'logoutRequestSigned' => true,         	'logoutResponseSigned' => true,         	'signMetadata' => true,         	'wantMessagesSigned' => false,         	'wantAssertionsSigned' => false,         	'wantAssertionsEncrypted' => false,         	'wantNameIdEncrypted' => false,     ),     'contactPerson' => array ( ...
Output from the array:
`
[sp] => Array
(
[entityId] => https://diskus-demo.ub.uu.se/saml/metadata
[assertionConsumerService] => Array
(
[url] => https://diskus-demo.ub.uu.se/saml/acs
)
        [singleLogoutService] => Array
            (
                [url] => https://diskus-demo.ub.uu.se/saml/sls
            )

        [NameIDFormat] => urn:oasis:names:tc:SAML:2.0:nameid-format:transient
        [x509cert] => MIIFAzCCAuugAwIBAgIJAONjaHZu0gBEMA0GCSqGSIb3DQEB...
        [0] => 1
    )

[security] => Array
    (
        [nameIdEncrypted] =>
        [authnRequestsSigned] => 1
        [logoutRequestSigned] => 1
        [logoutResponseSigned] => 1
        [signMetadata] => 1
        [wantMessagesSigned] =>
        [wantAssertionsSigned] =>
        [wantAssertionsEncrypted] =>
        [wantNameIdEncrypted] =>
    )

[contactPerson] => Array

`
The privateKey are missing.
I'll try to upgrade to latest php-saml-2.11.0, xibo using v.2.10.2 today. I'm not sure how to upgrade but I give it a try.
Regards
Fredrik

Upgraded to latest php-saml-2.11.0 (copy the directory). The result is the same as above.
/Fredrik

Since the PrivateKey is not there, it seems there is some issue on the Xibo implementation, is not related to the php-saml toolkit.
If you defined the PrivateKey properly on the settings and is not there when you use it to build the Auth object, that means that Xibo made something to it..

Thanks, moving the question to xibo.
cheers
Fredrik

@pitbulk sorry for this, but here is the problem:
'privateKey' > 'MIIJQQIBADANBgkq should be 'privateKey' => 'MIIJQQIBADANBgkq
Feel really bad for taking your time. Thanks for all support!
Fredrik

authors: flysen pitbulk

repo: onelogin/php-saml


text:
[C1.0] failed to stage contract (flow-cli crash)

Instructions
flow-cli crashed when staging https://github.com/fixes-world/token-list/blob/cadence1.0/cadence/contracts/TokenList.cdc
Problem

runtime error: invalid memory address or nil pointer dereference
[] []
map[device:map[arch:arm64 num_cpu:10] os:map[name:darwin] runtime:map[go_maxprocs:10 go_numcgocalls:13 go_numroutines:21 name:go version:go1.20]]
goroutine 1 [running]:
runtime/debug.Stack()
        /usr/local/go/src/runtime/debug/stack.go:24 +0x64
github.com/onflow/flow-cli/internal/command.initCrashReporting.func1(0x14000bf4580, 0x1400071a660)
        /go/src/github.com/onflow/flow-cli/internal/command/command.go:388 +0x1c8
github.com/getsentry/sentry-go.(*Client).processEvent(0x1400014fa40, 0x14000bf4580?, 0x1400071a660, {0x104bd5880, 0x140001e79e0})
        /root/go/pkg/mod/github.com/getsentry/sentry-go@v0.27.0/client.go:631 +0x24c
github.com/getsentry/sentry-go.(*Client).CaptureEvent(...)
        /root/go/pkg/mod/github.com/getsentry/sentry-go@v0.27.0/client.go:447
github.com/getsentry/sentry-go.(*Client).RecoverWithContext(0x60?, {0x0?, 0x0}, {0x1047fd440?, 0x105ff0020?}, 0x102d47118?, {0x104bd5880, 0x140001e79e0})
        /root/go/pkg/mod/github.com/getsentry/sentry-go@v0.27.0/client.go:498 +0x1e4
github.com/getsentry/sentry-go.(*Client).Recover(0x14000a523a8?, {0x1047fd440?, 0x105ff0020?}, 0x1024cd920?, {0x104bd5880?, 0x140001e79e0?})
        /root/go/pkg/mod/github.com/getsentry/sentry-go@v0.27.0/client.go:462 +0x80
github.com/getsentry/sentry-go.(*Hub).Recover(0x14000a52388?, {0x1047fd440?, 0x105ff0020?})
        /root/go/pkg/mod/github.com/getsentry/sentry-go@v0.27.0/hub.go:330 +0xc0
github.com/getsentry/sentry-go.Recover()
        /root/go/pkg/mod/github.com/getsentry/sentry-go@v0.27.0/sentry.go:68 +0x40
panic({0x1047fd440, 0x105ff0020})
        /usr/local/go/src/runtime/panic.go:884 +0x1f4
github.com/onflow/cadence/runtime/sema.(*InterfaceType).EffectiveInterfaceConformances(0x14001238000?)
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/sema/type.go:5967 +0x18
github.com/onflow/cadence/runtime/sema.(*IntersectionType).initializeEffectiveIntersectionSet.func1()
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/sema/type.go:8217 +0xb0
sync.(*Once).doSlow(0x18?, 0x10497c060?)
        /usr/local/go/src/sync/once.go:74 +0x100
sync.(*Once).Do(...)
        /usr/local/go/src/sync/once.go:65
github.com/onflow/cadence/runtime/sema.(*IntersectionType).initializeEffectiveIntersectionSet(0x14000a52688?)
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/sema/type.go:8211 +0x48
github.com/onflow/cadence/runtime/sema.(*IntersectionType).EffectiveIntersectionSet(...)
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/sema/type.go:8206
github.com/onflow/cadence/runtime/sema.(*IntersectionType).SupportedEntitlements.func1()
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/sema/type.go:8437 +0x38
sync.(*Once).doSlow(0x10?, 0x140014d43c0?)
        /usr/local/go/src/sync/once.go:74 +0x100
sync.(*Once).Do(...)
        /usr/local/go/src/sync/once.go:65
github.com/onflow/cadence/runtime/sema.(*IntersectionType).SupportedEntitlements(0x14001609180?)
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/sema/type.go:8434 +0x50
github.com/onflow/cadence/runtime/stdlib.(*CadenceV042ToV1ContractUpdateValidator).expectedAuthorizationOfIntersection(0x14000543148?, {0x140006c2f80, 0x3, 0x14001bb24c0?})
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/stdlib/cadence_v0.42_to_v1_contract_upgrade_validator.go:294 +0x114
github.com/onflow/cadence/runtime/stdlib.(*CadenceV042ToV1ContractUpdateValidator).expectedAuthorizationOfComposite(0x104bde100?, 0x104bebd60?)
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/stdlib/cadence_v0.42_to_v1_contract_upgrade_validator.go:270 +0x68
github.com/onflow/cadence/runtime/stdlib.(*CadenceV042ToV1ContractUpdateValidator).checkEntitlementsUpgrade(0x14001bb24c0?, 0x14001c20980)
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/stdlib/cadence_v0.42_to_v1_contract_upgrade_validator.go:338 +0x8c
github.com/onflow/cadence/runtime/stdlib.(*CadenceV042ToV1ContractUpdateValidator).checkTypeUpgradability(0x14001bb24c0, {0x104bf8ea0?, 0x14001bc20c0}, {0x104bf8ea0?, 0x14001c20980}, 0x1)
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/stdlib/cadence_v0.42_to_v1_contract_upgrade_validator.go:421 +0x1dc
github.com/onflow/cadence/runtime/stdlib.(*CadenceV042ToV1ContractUpdateValidator).checkTypeUpgradability(0x14001bb24c0, {0x104bf8d80?, 0x14001bc0a80}, {0x104bf8d80?, 0x14001c22540}, 0x0)
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/stdlib/cadence_v0.42_to_v1_contract_upgrade_validator.go:534 +0x8dc
github.com/onflow/cadence/runtime/stdlib.(*CadenceV042ToV1ContractUpdateValidator).checkField(0x14001bb24c0, 0x14001236720?, 0x14001c26120)
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/stdlib/cadence_v0.42_to_v1_contract_upgrade_validator.go:661 +0x78
github.com/onflow/cadence/runtime/stdlib.checkFields({0x104c0cf00, 0x14001bb24c0}, {0x104c06c20?, 0x14001654320?}, {0x104c06c20, 0x14001655040})
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/stdlib/contract_update_validation.go:272 +0x108
github.com/onflow/cadence/runtime/stdlib.checkDeclarationUpdatability({0x104c0cf00, 0x14001bb24c0}, {0x104c06c20?, 0x14001654320}, {0x104c06c20?, 0x14001655040}, 0x14000a53298)
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/stdlib/contract_update_validation.go:235 +0xf4
github.com/onflow/cadence/runtime/stdlib.checkNestedDeclarations({0x104c0cf00, 0x14001bb24c0}, {0x104c06c20, 0x140016545a0}, {0x104c06c20, 0x140016552c0}, 0x8e79a71f8a926fb8?)
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/stdlib/contract_update_validation.go:355 +0xf4
github.com/onflow/cadence/runtime/stdlib.checkDeclarationUpdatability({0x104c0cf00, 0x14001bb24c0}, {0x104c06c20?, 0x140016545a0}, {0x104c06c20?, 0x140016552c0}, 0x14000a53298)
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/stdlib/contract_update_validation.go:237 +0x114
github.com/onflow/cadence/runtime/stdlib.(*CadenceV042ToV1ContractUpdateValidator).Validate(0x14001bb24c0)
        /root/go/pkg/mod/github.com/onflow/cadence@v1.0.0-preview.25/runtime/stdlib/cadence_v0.42_to_v1_contract_upgrade_validator.go:110 +0x208
github.com/onflow/flow-cli/internal/migrate.(*stagingValidator).ValidateContractUpdate(0x14000abe310, {{0x16d94a747, 0x9}, {0xb8, 0x6f, 0x92, 0x8a, 0x1f, 0xa7, 0x79, ...}}, ...)
        /go/src/github.com/onflow/flow-cli/internal/migrate/staging_validator.go:172 +0x514
github.com/onflow/flow-cli/internal/migrate.stageContract({0x140003509e0, 0x1, 0x0?}, {{0x0, 0x0}, {0x103ea13c2, 0x4}, {0x0, 0x0}, {0x0, ...}, ...}, ...)
        /go/src/github.com/onflow/flow-cli/internal/migrate/stage_contract.go:102 +0x4b8
github.com/onflow/flow-cli/internal/command.Command.AddToParent.func1(0x1060277c0?, {0x140003509e0, 0x1, 0x2})
        /go/src/github.com/onflow/flow-cli/internal/command/command.go:142 +0x4f0
github.com/spf13/cobra.(*Command).execute(0x1060277c0, {0x1400004e120, 0x2, 0x2})
        /root/go/pkg/mod/github.com/spf13/cobra@v1.8.0/command.go:987 +0x798
github.com/spf13/cobra.(*Command).ExecuteC(0x1400069af00)
        /root/go/pkg/mod/github.com/spf13/cobra@v1.8.0/command.go:1115 +0x364
github.com/spf13/cobra.(*Command).Execute(...)
        /root/go/pkg/mod/github.com/spf13/cobra@v1.8.0/command.go:1039
main.main()
        /go/src/github.com/onflow/flow-cli/cmd/flow/main.go:168 +0xd68

Steps to Reproduce
run
flow-c1 migrate stage-contract TokenList --network=testnet

Acceptance Criteria
Not to crash, tell me what happened.
Context
flow-cli: v1.18.0-cadence-v1.0.0-preview.23

Thanks for adding this issue. @jribbink any chance this is solved in #1582 ? I know you're making a lot of changes there.

authors: btspoony chasefleming

repo: onflow/flow-cli


text:
Add testnet/mainnet to EVM gateway

Closes #???
Description
Add EVM Gateway options for testnet & mainnet

For contributor use:

[ ] Targeted PR against master branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[ ] Code follows the standards mentioned here
[ ] Updated relevant documentation
[ ] Re-reviewed Files changed in the Github PR explorer
[ ] Added appropriate labels

Codecov Report
Attention: Patch coverage is 0% with 5 lines in your changes missing coverage. Please review.

Project coverage is 29.48%. Comparing base (46f37b0) to head (7e5371f).

Files with missing lines
Patch %
Lines

internal/evm/gateway.go
0.00%
5 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1727      +/-   ##
==========================================
- Coverage   29.50%   29.48%   -0.03%
==========================================
  Files          88       88
  Lines        5162     5166       +4
==========================================
  Hits         1523     1523
- Misses       3452     3456       +4
  Partials      187      187

Flag
Coverage Δ

unittests
29.48% <0.00%> (-0.03%)
:arrow_down:

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

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

authors: codecov-commenter jribbink


text:
Update error-codes.mdx

remove --> since it looks to be causing an error in converting to html
Description
error in converting markdown causing page to crash in dev portal

For contributor use:

[x] Targeted PR against master branch
[ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
[ ] Code follows the standards mentioned here.
[ ] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[ ] Added appropriate labels

Codecov Report

Merging #349 (bfb443a) into master (54ba363) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #349   +/-   ##
=======================================
  Coverage   62.99%   62.99%
=======================================
  Files          23       23
  Lines        2113     2113
=======================================
  Hits         1331     1331
  Misses        657      657
  Partials      125      125

Flag
Coverage Δ

unittests
62.99% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

authors: bthaile codecov-commenter

repo: onflow/flow-go-sdk


text:
Password authentication failed for user "kittyuser"

Hi there,
Thanks so much for the excellent framework!
After deploying the contracts and following the API steps here:
https://github.com/onflow/kitty-items/tree/master/api#readme
There seems be an error with regard to password authentication failed for user "kittyuser". Please see the error below:

npm run start:dev

kitty-items-api@0.0.1 start:dev
tsnd --respawn src/index.ts

[INFO] 20:09:41 ts-nhttps://github.com/onflow/kitty-items/tree/master/api#readmeode-dev ver. 1.1.1 (using ts-node ver. 9.1.1, typescript ver. 4.1.2)
error: password authentication failed for user "kittyuser"
at Parser.parseErrorMessage (kitty-items/api/node_modules/pg-protocol/src/parser.ts:357:11)
at Parser.handlePacket (kitty-items/api/node_modules/pg-protocol/src/parser.ts:186:21)
at Parser.parse (kitty-items/api/node_modules/pg-protocol/src/parser.ts:101:30)
at Socket. (kitty-items/api/node_modules/pg-protocol/src/index.ts:7:48)
at Socket.emit (node:events:378:20)
at addChunk (node:internal/streams/readable:313:12)
at readableAddChunk (node:internal/streams/readable:288:9)
at Socket.Readable.push (node:internal/streams/readable:227:10)
at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
length: 105,
severity: 'FATAL',
code: '28P01',
detail: undefined,
hint: undefined,
position: undefined,
internalPosition: undefined,
internalQuery: undefined,
where: undefined,
schema: undefined,
table: undefined,
column: undefined,
dataType: undefined,
constraint: undefined,
file: 'auth.c',
line: '329',
routine: 'auth_failed'
}

Can you kindly advise how to fix it?
Thanks!

Fixed it by re-opening the port. Thanks!

repo: onflow/kitty-items


text:
[WIP] Tabs show modified state.

Some early work on getting tabs to show the modified state.
Current issue is that I'm using the buffer.modified value to check if a buffer has been modified, which is what the buffer mode tabs use.
However, this seems to not be set when swapping between splits or between tabs. This also seems to be an issue for me if I use "tabs.mode": "buffer" as well though, so is this a regression or was it just not wired up like that in the first place?
To test this I'm doing as follows :

Open Oni
Open file
Open new file with :vsplit FILE2
Edit file 2
Click on original file, and modified status will go away in the Oni visualised tabs. Neovim returns 1 as expected when using :echo &modified.

This happens in both modes, and on the latest release, so I don't think its me, but if someone could confirm its not any of my settings that would be useful.
Regardless, to do:

[ ] Check where I am calling tabpagebuflist makes sense.
[x] Fix the modified status turning off when swapping.
[ ] Add Unit tests for Tab modified status function
[x] Add CI test for Tab modified (and Buffer if needed)

@bryphe, it looks like the current CI test way of pulling in the config.js settings didn't work for strings. I think I've fixed that here since I needed to use it, but am just pointing out the change since it isn't directly related to the title of the PR!

Ah thanks for the heads up @CrossR ! Shoot, I hit the same issue in #1354  -
https://github.com/onivim/oni/blob/6ac8763a8e127e78dce96642429444883361791a/test/common/runInProcTest.ts#L63
Sorry to duplicate that work, but your fix for it looks great. Thanks for checking, I agree it makes sense to bring it in with this change 👍  Really appreciate you writing the test for it too!

This should be in a working state now, with passing Unit + CI tests.
I want to do a little more testing to make sure there is no odd edge cases I'm missing, but otherwise its done.

Done some more testing with this and didn't hit any hiccups, so I'll bring this in now!

authors: CrossR bryphe

repo: onivim/oni


text:
added get_nearby_locations function

Added function to extract nearby locations using Openstreetmaps api from trajectories numpy array.

I don't understand why it says that great_circle_dist has too many arguments, since it takes 4 and I provide it 4 in great_circle_dist(*row[1:3], lat[i], lon[i]).

Could you write a test for great_circle_dist(*row[1:3], lat[i], lon[i]) to confirm the actual number of values passed in?

This also may be a limitation of mypy since great_circle_dist(lat[i], lon[i], *row[1:3]) produces no error. So, perhaps the best (and potentially more readable) solution is to unpack row[1:3] before passing the values to the function.

authors: GeorgeEfstathiadis hackdna

repo: onnela-lab/forest


text:
AssertionError: retinanet-bbox/classification_submodel/pyramid_classification/Bi asAdd/ReadVariableOp/resource:0 is disconnected,

i got this error why this is occured
outputs = keras.layers.Conv2D(
filters=num_classes * num_anchors,
kernel_initializer=keras.initializers.RandomNormal(mean=0.0, stddev=0.01, seed=None),
#bias_initializer='zeros',
bias_initializer=initializers.PriorProbability(probability=prior_probability),
name='pyramid_classification',
**options
)(outputs)
this is pyramid_classfication layer
AssertionError: retinanet-bbox/classification_submodel/pyramid_classification/Bi asAdd/ReadVariableOp/resource:0 is disconnected,
i think it's no problems in this layer
but i got this error ....
i am wondering

Retinanet conversion is not supported right now.

thanks to answer ..... but i need to find another way ...

repo: onnx/keras-onnx


text:
refer function on webRTC question

These are typically directed to the google group.
Hi,
Currently I'm working with 0.17.1.
when i using logLevel: "debug" and i make outbound out-of-dialog REFER requests. Status code only send me status 100 trying
and not auto hangup in spite of target refer accepted, after accepted 30s code send status code 408 request time out, still not hangup and make noise between caller and refer target and when i reject the call, it remains the same . Until i must hangup middle call manually.
Can someone please give me the solution (a simple code example would be very much appreciated).
Thanks!

How are you sending the refer?

How are you sending the refer?
First i receive call then using session to refer like this:

    const transferTarget = SIP.UserAgent.makeURI(`sip:${toNumber}@${TestSipjs.domain}`);

    window.SimpleUser.session.refer(transferTarget,{
      onNotify(e){
        console.log(e);
      },
      requestDelegate: {
        onAccept(){
          window.SimpleUser.session.bye();
          console.log("ok");
        },
        onReject(){
          self.setupInCall();
        }
      }
    }

);

Creating a transfer (REFER) with SimpleUser is not supported. You need to use the full API.
Out of dialog refer is not supported at all with SIP.js at the moment. Your hack is an in dialog refer.
This is definitely not a SIP.js bug but a question about implementation. Please direct this towards the Google Group


text:
how can i create a new route ?

hi, i just discover and fork this repo. i think "astrowind" is the best solution for landing and blog post static website.
i want to create a new routes "/organisations"
│   ├── pages/
│   |   ├── [...blog]/
|   |   ├── [...page].astro
|   |   └── [slug].astro
│   |   ├── [...organisations]/
|   |   ├── [...page].astro
|    |   └── [slug].astro
when i created these files and trying to check the route . i have a error .
" getstaticPaths route pattern matched but no matching static path found (/organisations)
thank for your anwser .

Hi @houmedfa
It's good to know that you find AstroWind useful. It is still a work in progress, any suggestion or idea you have, contact us.
The error that is shown to you is because you are defining the route like this [...organizations]. According to the Astro documentation, routes defined with [] are dynamic and require you to implement the getStaticPaths function.
My doubt is that I don't know if you need to create only one page with /organizations, or a list of dynamic pages inside the organizations folder

To create the '/organizations' url, if you only want to create that route with a simple page you can do either of the two variants:

A
/
│   ├── pages/
│   |   ├── ...
│   |   ├── [...blog]/
|   |   |   ├── [...page].astro
|   |   |   └── [slug].astro
+   |   ├── organizations/
+   |   |   └── index.astro
│   |   ├── index.astro
|   |   ├── 404.astro
|   |   └-- rss.xml.js
└── ...

B
/
│   ├── pages/
│   |   ├── ...
│   |   ├── [...blog]/
|   |   |   ├── [...page].astro
|   |   |   └── [slug].astro
+   |   ├── organizations.astro
│   |   ├── index.astro
|   |   ├── 404.astro
|   |   └-- rss.xml.js
└── ...

2. On the other hand, if you want to create a list of pages inside /organizations route, then the folder structure for the paths should be different.
/
│   ├── pages/
│   |   ├── ...
│   |   ├── [...blog]/
|   |   |   ├── [...page].astro
|   |   |   └── [slug].astro
+   |   ├── organizations/
+   |   |   ├── organization1.astro
+   |   |   ├── organization2.astro
+   |   |   └── index.astro
│   |   ├── index.astro
|   |   ├── 404.astro
|   |   └-- rss.xml.js
└── ...

3. And if you want to create a list of **dynamic pages** inside /organizations route, then the folder structure for the paths should be different.
/
│   ├── pages/
│   |   ├── ...
│   |   ├── [...blog]/
|   |   |   ├── [...page].astro
|   |   |   └── [slug].astro
+   |   ├── organizations/
+   |   |   ├── [...pages].astro
+   |   |   └──[slug].astro
│   |   ├── index.astro
|   |   ├── 404.astro
|   |   └-- rss.xml.js
└── ...

And you should also implement a getStaticPaths function inside each of those dynamic paths [slug].astro, [...page].astro
https://docs.astro.build/en/core-concepts/routing/#dynamic-routes

thank you for your clean and helpful anwser.

authors: houmedfa prototypa

repo: onwidget/astrowind


text:
collector archival script: prevent race conditions

The archival script might be moving reports to /srv/collector/renamed before fastpath had time to read the files. Investigate ways to prevent races. Ideally provide a long backlog based on available disk space. Add metrics where possible.
Related to #265

As we determined in the end the root cause of the incident to be the backlog of the collector and the pipeline stalling. I will am reverting the change which made the cronjob run hourly and instead do it on a daily basis as it did before: https://github.com/ooni/sysadmin/commit/2e71a4c3f6434a75a96b2a086837f591a3c69a5f.
The race is still there, but I don't think this is as urgent anymore to address.

authors: FedericoCeratto hellais

repo: ooni/pipeline


text:
Element id wont accept "mixed" types when inferring type

Checks

[x] I added a descriptive title to this issue
[x] I have searched (Google, GitHub) for similar issues and couldn't find anything
[x] I have read and followed the docs and still think this is a bug

Bug Description
When the id of an element starts with a number and there is a - in the name, there seems to be an error when mapping the value as Float. As id's in EPANET are regarded as strings, this behaviour will break if an element has an id such as 1-p. This seems to be related to the reportfile_reader.lst2xray, that is trying to parse the element id's while reading the file.

Steps to Reproduce
Importing the following model will trigger an error
Named_id_model.txt
import oopnet as on

# Load the EPANET model
fname = "Named_id_model.txt"
net = on.Network.read(fname)

Expected Behavior
It is expected that the id's are not parsed, as they are supposed to be strings.

I had the same problem with a similar name structure ("123456-A") fixed that in my fork by adding a condition to reportfile_reader.lst2xray that excludes the first entry in each lst entry:

# check for invalid values
    for entry_index, entry in enumerate(lst):
        new_entry = []
        for index, item in enumerate(entry):
            c = Counter(item)
            if (
                    "+" in c
                    and "-" in c
                    or "+" in c
                    and c["+"] > 1
                    or "-" in c
                    and (c["-"] > 1 or item[0] != "-" and item[0].isnumeric())
            ) and (
                    index > 1 #this will exclude the first entry (=node/link name) so it is not split and misinterpreted
            )

Report is now being generated for my own network and your example.
Not opening a PR for this since I do not have the capacity to test this with all networks that are provided in testing and do it cleanly. There might be a reason the node name as not exluded from the if clause!

Indeed, it is not clear to me either.
I patched the issue in my own fork as well, but let's wait for some comments from the maintainers to see if this is indeed a bug or a feature.
Thanks!

authors: j-chacon jokwb

repo: oopnet/oopnet


text:
Fix sanitizing data bug.

Filter Params were not working when set as symbols.
Filter was not applied properly in http error_messages.
Filter was only applied to String values.

This should fix Issue#39

This is great, @simitt ! Thank you.
❤💜💙💛💚

authors: mikker simitt

repo: opbeat/opbeat-ruby


text:
Visualization for taxonomy cover.

Add visualisation for taxonomy cover.
# Using result store
ADRIA.viz.taxonomy(result_set)

# Using scenario spec and YAXArray
ADRIA.viz.taxonomy(scens, relative_taxa_cover)

@DanTanAtAims I like that visualization! In addition to that, it would be nice to see one plot per species showing counterfactual/guided/unguided.

The new target is main and this PR only contains commits related to taxonomy visualisation.

authors: DanTanAtAims Zapiano


text:
Sometimes non-responsive DNS resolvers are configured in instances

An example from the demo server: hpc-client was adding 10.0.38.2 to /etc/resolv.conf, but there was no server listening on this address. This caused long pauses when configuring the instance using ansible due to DNS timeouts.
One fix was to force the problematic network to return 8.8.8.8:
neutron subnet-update 04bacdd6-e3c1-4a8b-9ee9-61e20afd4111 --dns-nameservers list=true 8.8.8.8
Ultimately, it would may be best for private networks to not offer DNS services, and only public networks that provide Internet connectivity, such as nat-net, should offer DNS services.

Added "dns_nameservers=8.8.8.8" to sync_controller_networks.yaml. Applied change to Portal. Waiting on portal keystone issues in order to test.

Resolved.

repo: open-cloud/xos


text:
New service account for some application pods

https://github.com/stolostron/backlog/issues/22006
Signed-off-by: Philip Wu phwu@redhat.com

/lgtm


text:
:bug:  fix token-secret format

Summary
Related issue(s)
Fixes #

/assign @qiujian16

/approve
/lgtm

repo: open-cluster-management-io/ocm


text:
Add client cert condition when cert is rotated

Signed-off-by: Jian Qiu jqiu@redhat.com

/assign @yue9944882
/assign @elgnay

/lgtm

repo: open-cluster-management-io/registration


text:
ChartQA augmented & CMMMU

It would be nice if VLMEvalKit can support evaluation on ChartQA augmented set and CMMMU, since it has supported ChartQA human set and MMMU

Hi, @KosumosuL ,
ChartQA augmented is now incorporated. However, there is no news from the developers of CMMMU.

VLMEvalkit has supported ChartQA.

authors: KosumosuL junming-yang kennymckormick

repo: open-compass/VLMEvalKit


text:
🛑 Search v1 is down

In 5ce040b, Search v1 (https://search.open.canada.ca/en/od) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Search v1 is back up in 5bbd5f0.

repo: open-data/status-statut


text:
Foot Contact Switch connection

Hi, how does Foot Contact Switch v1 connect to Micro Driver ?
As I understand it connects to ADC to one of the Micro Driver MCU via U$12 contact.

Hi,
each Micro Driver has 2 ADC ports which are evaluated and transmitted at 1kHz.
You want to supply the foot sensor with 3.3V - that's the maximum voltage of the ADCs.
In this schematic the ADC ports are labeled with ADC-A6 and ADC-B6.

that is, I can connect 2 sensors to one board udriver?

Yes - that's possible.
In that case the sensors will have to share the 3.3V and GND connection.
It might be less convenient for assembly and repairs to have both sensors on a single Hirose connector.
It might make sense to connect one sensor per Micro Driver board and use a individual 3pin Hirose connector for each one.

Thanks!

Welcome!


text:
Feature front end

This PR Fixes #issue_number
Proposed Changes
Please review

[ ] @libremente

Can you please rebase @EugenioCorso ?

authors: EugenioCorso libremente

repo: open-education-polito/fare-platform


text:
Metric for evaluations by reason (including errors)

We should create a new metric which buckets evaluations by reason, which would include evaluations that failed because they were not found flags, or evaluations which had un-parsable context, or other error conditions, as well as flags that evaluated some way due to targeting vs static assignment, etc.
Created based on this (cc @beeme1mr @thisthat )

To continue the discussion based on the PR, I agree to have this information, but I don't know if a whole new metric makes sense. We could add the reason in a new dimension feature_flag_reason without the need to set up a whole new metric pipeline. With the concern about metric explosion due to the use of invalid flag keys, we could bucket these faulty evaluations under the dimension feature_flag_key=flagd_error.
WDYT @toddbaert, @beeme1mr ?

I think that impressions should only be captured for valid feature flags. Creating a hard-coded error dimension would likely work but seems like a magic string. What would happen if someone named their feature flagd_error 🤣.
What's the disadvantage of adding a new metric? Perhaps the metric could be focused entirely on error conditions instead of capturing all reasons. Being able to chart errors like "flag not found" over time would be very valuable.

Perhaps the metric could be focused entirely on error conditions instead of capturing all reasons.

Isn't seeing reasons also really valuable though STATIC (cachable) vs TARGET_MATCH vs ERROR (and error details). I see only upsides to all this info.

@thisthat and I spoke about this and I think we agree that a new metric that contains reasons (including ERROR) as well as data about the error (FLAG_NOT_FOUND) makes sense.
Use cases this supports:

understanding performance (eg: lots of STATIC evaluation means more caching may be possible)
understanding configuration errors (eg: a sudden spike in ERRORs of type FLAG_NOT_FOUND means a new evaluation has been deployed ahead of its definition)
finding bugs (a client is sending an invalid context)

authors: beeme1mr thisthat toddbaert

repo: open-feature/flagd


text:
feat!: Move all files from pkg/openfeature to openfeature.

This PR

Move the package from being
github.com/open-feature/go-sdk/pkg/openfeature, which has an unnecessary pkg in the import path, to github.com/open-feature/go-sdk/openfeature, without the unnecessary "pkg" in the import path.
The existing github.com/open-feature/go-sdk/pkg/openfeature package is now a compatibility shell; exported types, constants, variables, and functions are now aliased to the new
github.com/open-feature/go-sdk/openfeature equivalents in a way that will pass equality checks, and types are interchangeable between both packages. No logic or tests live in the package anymore, only the exported identifiers, which call through to the new package for behavior.
The memprovider package, similarly, has moved.
Related Issues

Fixes #227
How to test

Any consumers of the package that already exist should be able to transparently use this version (go mod edit -replace github.com/open-feature/go-sdk=github.com/paddycarver/open-feature@no-pkg) with no code changes or changes in behavior.

@paddycarver thank you for the contribution and I like the approach proposed through this PR (compared to #233 with root level content)
Could you please sign off your commit ? This guide should help you - https://github.com/open-feature/go-sdk/pull/232/checks?check_run_id=18694944964

Should be done. :)

@Kavindu-Dodan @paddycarver thanks so much for this change. I agreed very much with @craigpastro that the imports were not ideal, and I had already accepted that this would be a breaking change, so this was a welcome surprise!
There's a ! in the title. This implies this is breaking, which I believe it is not (I don't consider deprecations breaking). Since everything should work transparently with the exception of compiler warnings around deprecations, I guess we can remove the !? Otherwise our release automation will try to increment the package version to v2.0.0.

What problem does this solve? It's good practice to use pkg in golang

@AlexsJones, the reasoning was discussed in the linked issue. @paddycarver was able to introduce this change in a nonbreaking way.

If we can make the change without breaking things 👍

authors: AlexsJones Kavindu-Dodan beeme1mr paddycarver toddbaert

repo: open-feature/go-sdk


text:
fix: protobuf-java version for CVE-2024-7254

Fixes a vuln.
Issue to revert in future: https://github.com/open-feature/java-sdk-contrib/issues/1031

Is there a ticket we can follow in gRPC java?

Kinda - it's mentioned here.

repo: open-feature/java-sdk-contrib


text:
Cover deploy frameworks (Asgard, Spinnaker, etc)

At least mention major ones and who uses them, etc.
https://github.com/Netflix/asgard
http://www.spinnaker.io/

@jlevy Where do you see this fitting into the README file? I might start a branch outlining candidate entries, but I want to put it where you see fit.
cc @ThanosBaskous

Closing and including with #317

authors: jlevy rjhintz

repo: open-guides/og-aws


text:
Show Manage Tab only if User has access to perform any action underneath

Right now we show Manage tab for all the users even if they do not have access to perform any actions under that tab
To avoid confusion, instead of blocking user, we should not show Manage tab if user does not have any permission to perform the actions there

CC: @harshach @vivekratnavel @devyani-kaushik

Closing this as we have removed the manage tab.

repo: open-metadata/OpenMetadata


text:
Permissions for Feed Resource

Currently, edit conversation, edit task, or edit announcement permissions are not handled by the authorizer. We should add edit operations to Feed resource to bring it under the authorizer.

@vivekratnavel assigning it to you for 0.12.1

authors: harshach vivekratnavel


text:
Issue-3234: Rename default in role_entity to defaultRole

Describe your changes :
see #3234

Type of change :

[x] Improvement

Frontend Preview (Screenshots) :
For frontend related change, please link screenshots of your changes preview! Optional for backend related changes.

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have performed a self-review of my own.
[ ] I have tagged my reviewers below.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] My changes generate no new warnings.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers

@harshach  This parameter is also used in UI codebase, we need to change that too.
Besides that these changes look good from backend

@Sachin-chaurasiya check if we need to make any changes on the UI side

https://github.com/open-metadata/OpenMetadata/blob/main/openmetadata-ui/src/main/resources/ui/src/pages/RolesPage/RolesPage.component.tsx#L172

@Sachin-chaurasiya check if we need to make any changes on the UI side

@harshach, Changes for UI is done.

authors: Sachin-chaurasiya harshach mithmatt


text:
[Enhancement] Add version update

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
When the current version of openmim is lower than the latest version, it will print a warning message to remind user of upgrading openmim.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the back-compatibility of the downstream repos?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects, like MMDet or MMCls.
The documentation has been modified accordingly, like docstring or example tutorials.

Codecov Report

:exclamation: No coverage uploaded for pull request base (main@1bb17cd). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #54   +/-   ##
=======================================
  Coverage        ?   63.50%
=======================================
  Files           ?       21
  Lines           ?     1488
  Branches        ?      331
=======================================
  Hits            ?      945
  Misses          ?      418
  Partials        ?      125

Flag
Coverage Δ

unittests
63.50% <0.00%> (?)

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

Continue to review full report at Codecov.

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

authors: codecov-commenter zhouzaida

repo: open-mmlab/mim