error: undefined - MacOS Ollama

Describe the bug
I'm not able to search running Perplexica as a docker container locally and Ollama.
To Reproduce
Ollama installation
$ brew install ollama
$ brew services start ollama
$ ollama pull llama3:latest

confirm the service is working
$ curl  http://<IP_ADDRESS>:11434

Ollama is running%

config file:
[API_ENDPOINTS]
SEARXNG = "http://localhost:32768" # SearxNG API URL
OLLAMA = "http://host.docker.internal:11434"

open http://localhost:3000 and do any search ...
Expected behavior
Perplexica be able to return answers for any query with no errors
Additional context
Anytime I try to search for something I see error: undefined in the log entries:
docker logs perplexica-perplexica-backend-1 -f
yarn run v1.22.19
$ node dist/app.js
info: WebSocket server started on port 3001
info: Server is running on port 3001

error: undefined
error: undefined

I'll try to reproduce

I run Perplexica on a Mac. Ollam is running on the Mac app because I see that Ollama has a pending update with the icon.
if you follow the Perplexica compse installation, and you put OLLAMA = "http://host.docker.internal:11434" on the Config.toml file you should have Perplexica running.
By default Perplexica frontend is on localhost:3000, see if you have anything listening there

Getting the same bug

When I try to run it for first time.

 When I try to run it for first time.

What are the logs from the backend container

2024-06-29 15:08:06 yarn run v1.22.19
2024-06-29 15:08:06 $ node dist/app.js
2024-06-29 15:08:06 info: WebSocket server started on port 3001
2024-06-29 15:08:06 info: Server is running on port 3001
2024-06-29 15:08:15 error: undefined
2024-06-29 15:08:16 error: undefined
2024-06-29 15:08:25 node:internal/process/promises:289
2024-06-29 15:08:25             triggerUncaughtException(err, true /* fromPromise */);
2024-06-29 15:08:25             ^
2024-06-29 15:08:25
2024-06-29 15:08:25 TypeError: Invalid URL
2024-06-29 15:08:25     at new URL (node:internal/url:775:36)
2024-06-29 15:08:25     at OpenAI.buildURL (/home/perplexica/node_modules/openai/core.js:318:15)
2024-06-29 15:08:25     at OpenAI.buildRequest (/home/perplexica/node_modules/openai/core.js:199:26)
2024-06-29 15:08:25     at OpenAI.makeRequest (/home/perplexica/node_modules/openai/core.js:274:44)
2024-06-29 15:08:25     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2024-06-29 15:08:25     at async /home/perplexica/node_modules/@langchain/openai/dist/chat_models.cjs:684:29
2024-06-29 15:08:25     at async RetryOperation._fn (/home/perplexica/node_modules/p-retry/index.js:50:12) {
2024-06-29 15:08:25   code: 'ERR_INVALID_URL',
2024-06-29 15:08:25   input: 'null/chat/completions'
2024-06-29 15:08:25 }
2024-06-29 15:08:25
2024-06-29 15:08:25 Node.js v20.8.1
2024-06-29 15:08:25 error Command failed with exit code 1.
2024-06-29 15:08:25 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2024-06-29 15:08:25 yarn run v1.22.19
2024-06-29 15:08:25 $ node dist/app.js
2024-06-29 15:08:25 info: WebSocket server started on port 3001
2024-06-29 15:08:25 info: Server is running on port 3001

2024-06-29 15:08:06 yarn run v1.22.19
2024-06-29 15:08:06 $ node dist/app.js
2024-06-29 15:08:06 info: WebSocket server started on port 3001
2024-06-29 15:08:06 info: Server is running on port 3001
2024-06-29 15:08:15 error: undefined
2024-06-29 15:08:16 error: undefined
2024-06-29 15:08:25 node:internal/process/promises:289
2024-06-29 15:08:25             triggerUncaughtException(err, true /* fromPromise */);
2024-06-29 15:08:25             ^
2024-06-29 15:08:25
2024-06-29 15:08:25 TypeError: Invalid URL
2024-06-29 15:08:25     at new URL (node:internal/url:775:36)
2024-06-29 15:08:25     at OpenAI.buildURL (/home/perplexica/node_modules/openai/core.js:318:15)
2024-06-29 15:08:25     at OpenAI.buildRequest (/home/perplexica/node_modules/openai/core.js:199:26)
2024-06-29 15:08:25     at OpenAI.makeRequest (/home/perplexica/node_modules/openai/core.js:274:44)
2024-06-29 15:08:25     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2024-06-29 15:08:25     at async /home/perplexica/node_modules/@langchain/openai/dist/chat_models.cjs:684:29
2024-06-29 15:08:25     at async RetryOperation._fn (/home/perplexica/node_modules/p-retry/index.js:50:12) {
2024-06-29 15:08:25   code: 'ERR_INVALID_URL',
2024-06-29 15:08:25   input: 'null/chat/completions'
2024-06-29 15:08:25 }
2024-06-29 15:08:25
2024-06-29 15:08:25 Node.js v20.8.1
2024-06-29 15:08:25 error Command failed with exit code 1.
2024-06-29 15:08:25 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2024-06-29 15:08:25 yarn run v1.22.19
2024-06-29 15:08:25 $ node dist/app.js
2024-06-29 15:08:25 info: WebSocket server started on port 3001
2024-06-29 15:08:25 info: Server is running on port 3001

Have you configured the OpenAI API key or the Groq API key or the Ollama address? Once of them is required for Perplexica to work.

Sorry for late reply. Yes I gave Ollama docker port address, which was successfully running in my local but it still did not work

[GENERAL]
PORT = 3001 # Port to run the server on
SIMILARITY_MEASURE = "cosine" # "cosine" or "dot"
[API_KEYS]
OPENAI = "" # OpenAI API key - sk-1234567890abcdef1234567890abcdef
GROQ = "" # Groq API key - gsk_1234567890abcdef1234567890abcdef
[API_ENDPOINTS]
SEARXNG = "http://localhost:32768" # SearxNG API URL
OLLAMA = "http://host.docker.internal:11434" # Ollama API URL - http://host.docker.internal:11434

What OS are you on?

[GENERAL] PORT = 3001 # Port to run the server on SIMILARITY_MEASURE = "cosine" # "cosine" or "dot"
[API_KEYS] OPENAI = "" # OpenAI API key - sk-1234567890abcdef1234567890abcdef GROQ = "" # Groq API key - gsk_1234567890abcdef1234567890abcdef
[API_ENDPOINTS] SEARXNG = "http://localhost:32768" # SearxNG API URL OLLAMA = "http://host.docker.internal:11434" # Ollama API URL - http://host.docker.internal:11434

+1 - Getting the same issue. I'm running Ollama on Ubuntu Server. IP address and port set in the Perplexica config works on all other apps. Inference seems to be triggered, but after about 30 seconds Perplexica throws the following error:

Failed to connect to the server. Please try again later.

+1 - Getting the same issue. I'm running Ollama on Ubuntu Server. IP address and port set in the Perplexica config works on all other apps. Inference seems to be triggered, but after about 3 seconds Perplexica throws the following error:

Failed to connect to the server. Please try again later.

What are the logs from the backend container?

What OS are you on?

[GENERAL] PORT = 3001 # Port to run the server on SIMILARITY_MEASURE = "cosine" # "cosine" or "dot"
[API_KEYS] OPENAI = "" # OpenAI API key - sk-1234567890abcdef1234567890abcdef GROQ = "" # Groq API key - gsk_1234567890abcdef1234567890abcdef
[API_ENDPOINTS] SEARXNG = "http://localhost:32768" # SearxNG API URL OLLAMA = "http://host.docker.internal:11434" # Ollama API URL - http://host.docker.internal:11434

Version 14.3 (23D56) MacOS Sonoma

@Arun-chaitanya @ItzCrazyKns - Got this working. The service expects a fake GROQ API key for this to work. Using sk-proj-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx gets the service to run with Ollama.

2024-06-29 15:08:06 yarn run v1.22.19
2024-06-29 15:08:06 $ node dist/app.js
2024-06-29 15:08:06 info: WebSocket server started on port 3001
2024-06-29 15:08:06 info: Server is running on port 3001
2024-06-29 15:08:15 error: undefined
2024-06-29 15:08:16 error: undefined
2024-06-29 15:08:25 node:internal/process/promises:289
2024-06-29 15:08:25             triggerUncaughtException(err, true /* fromPromise */);
2024-06-29 15:08:25             ^
2024-06-29 15:08:25
2024-06-29 15:08:25 TypeError: Invalid URL
2024-06-29 15:08:25     at new URL (node:internal/url:775:36)
2024-06-29 15:08:25     at OpenAI.buildURL (/home/perplexica/node_modules/openai/core.js:318:15)
2024-06-29 15:08:25     at OpenAI.buildRequest (/home/perplexica/node_modules/openai/core.js:199:26)
2024-06-29 15:08:25     at OpenAI.makeRequest (/home/perplexica/node_modules/openai/core.js:274:44)
2024-06-29 15:08:25     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
2024-06-29 15:08:25     at async /home/perplexica/node_modules/@langchain/openai/dist/chat_models.cjs:684:29
2024-06-29 15:08:25     at async RetryOperation._fn (/home/perplexica/node_modules/p-retry/index.js:50:12) {
2024-06-29 15:08:25   code: 'ERR_INVALID_URL',
2024-06-29 15:08:25   input: 'null/chat/completions'
2024-06-29 15:08:25 }
2024-06-29 15:08:25
2024-06-29 15:08:25 Node.js v20.8.1
2024-06-29 15:08:25 error Command failed with exit code 1.
2024-06-29 15:08:25 info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
2024-06-29 15:08:25 yarn run v1.22.19
2024-06-29 15:08:25 $ node dist/app.js
2024-06-29 15:08:25 info: WebSocket server started on port 3001
2024-06-29 15:08:25 info: Server is running on port 3001

Have you configured the OpenAI API key or the Groq API key or the Ollama address? Once of them is required for Perplexica to work.

I have an OpenAI API key configured as well as the Ollama server URI, but switching to Ollama seems to require a fake GROQ API key in order to work. Using sk-proj-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx gets it working for me. Just FYI, the error showing in the backend container logs was:

error: Error loading Groq models: Error: OpenAI or Azure OpenAI API key not found

This issue is now resolved with https://github.com/ItzCrazyKns/Perplexica/commit/8539ce82ad4b289956fc9c57bd1fb505aa26451d. I'd recommend everyone to re-install Perplexica.
docker compose up -d --build

Note: Run this only after re-cloning the repository.

This issue is now resolved with 8539ce8. I'd recommend everyone to re-install Perplexica.
docker compose up -d --build

Note: Run this only after re-cloning the repository.

Did this but now nothing works. Do I need to change or do anything else?

Also experiencing the same wit Ollama

@ItzCrazyKns - After your last commit, it seems that having any Ollama settings in place stop Perplexica from working at all. Removing the Ollama URI and GROQ API key, and OpenAI settings work. As another using mentioned, Ollama is no longer an option in the "Chat Model Provider" list - just OpenAI and "Custom_OpenAI"

@ItzCrazyKns - After your last commit, it seems that having any Ollama settings in place stop Perplexica from working at all. Removing the Ollama URI and GROQ API key, and OpenAI settings work. As another using mentioned, Ollama is no longer an option in the "Chat Model Provider" list - just OpenAI and "Custom_OpenAI"

Just did another commit, https://github.com/ItzCrazyKns/Perplexica/commit/27e6f5b9e1adeda5aeb5665a366d21d03cb07f30, that should help

Just did another commit, 27e6f5b, that should help

How should Ollama work now? The option is still not in the drop down. There's "Custom_OpenAI" and then the Ollama URI parameter separately to that. Earlier there was a separate option for Ollama in the model provider list...

I've re-cloned and re-set up everything, and now it works to me. Also had to clear cache and cookies, at the first attempt it was showing the same error

I've re-cloned and re-set up everything, and now it works to me. Also had to clear cache and cookies, at the first attempt it was showing the same error

Are you able to get Ollama working?

Are you able to get Ollama working?

Yes, it's working fine for me now!

Just did another commit, 27e6f5b, that should help

How should Ollama work now? The option is still not in the drop down. There's "Custom_OpenAI" and then the Ollama URI parameter separately to that. Earlier there was a separate option for Ollama in the model provider list...

the same error

Are you able to get Ollama working?

Yes, it works for me with Ollama, after re setting up everything, and clearing cache and cookies of the webpage from my browser

@nicolas-g   I have two environments, and currently my Mac can use ollama to call it normally,

Then I entered my Mac API interface into the Linux server, but it didn't seem to be correct and directly returned the message 'unable to connect'

I want to separate the backend from SEARXNG. Normally, only SEARXNG needs to open a proxy, right? The programs on the frontend and backend do not need a proxy, right

I was facing the same 'Invalid URL' error on my mac.
I tried some solution from this thread. Then I figured out, that config.toml is backed right in the backends docker image. So every time you do a change, you have to rebuild the docker images by doing
docker compose up -d --build

After that I got it running.
There is still another problem with the searxng container (Cannot load engine “gentoo”), but since I am using my already existing instance that does not matter for me.
see https://github.com/ItzCrazyKns/Perplexica/issues/257

The problem re-appeared. Deleting the cookies solved it.


Add reordering functionality for custom rules

This is an adaption of #229 which implements #71 for the fix of #226

Some testing with theses rules:
"rules": [
      {
        "rule": "sandbox",
        "icon": "FarFolder",
        "for": "folders",
        "filepath": true,
        "useFilePath": true,
        "order": 0
      },
      {
        "rule": "subfolder",
        "icon": "BoBxsBolt",
        "for": "files",
        "order": 1,
        "useFilePath": true
      },
      {
        "rule": "\\.md$",
        "icon": "LiFile",
        "for": "files",
        "order": 2
      }
]

Tree:
sandbox/
├─ subfolder/
│  ├─ fix/
│  │  ├─ eroerj er/
│  │  │  ├─ test
│  │  │  ├─ truc

Renamed file :
Renaming a file add the default icon (.md), not the subfolder icon
Creating file
No issue found, but as renaming change the icon to the default one…

[!NOTE]
Reloading Obsidian fix the icons problem, so each time:

We rename a file
We move a file
We edit the custom rules (order or type)
We need to reload Obsidian.

Some testing with theses rules:
"rules": [
      {
        "rule": "sandbox",
        "icon": "FarFolder",
        "for": "folders",
        "filepath": true,
        "useFilePath": true,
        "order": 0
      },
      {
        "rule": "subfolder",
        "icon": "BoBxsBolt",
        "for": "files",
        "order": 1,
        "useFilePath": true
      },
      {
        "rule": "\\.md$",
        "icon": "LiFile",
        "for": "files",
        "order": 2
      }
]

Tree:
sandbox/
├─ subfolder/
│  ├─ fix/
│  │  ├─ eroerj er/
│  │  │  ├─ test.md
│  │  │  ├─ truc.md

Renamed file :
Renaming a file add the default icon (.md), not the subfolder icon
Creating file
No issue found, but as renaming change the icon to the default one…
Note Reloading Obsidian fix the icons problem, so each time:

We rename a file
We move a file
We edit the custom rules (order or type)

We need to reload Obsidian.

Thank you for the detailed explanation. These issues should be fixed now.

Fixed! Ty :>


Cannot import SVG as a component: Invalid tag

🐛 Bug report
Current Behavior
When you try to import a SVG file as a react component following error occurs:
Invalid tag http://localhost:3001/static/media/logo.935ec323.svg
Expected behavior
SVG should be rendered as an embedded component
Steps to reproduce
yarn add @svgr/webpack
// razzle.config.js
module.exports = {
  modifyWebpackConfig(opts) {
    const config = opts.webpackConfig;
    config.module.rules.push({
      test: /\.svg$/,
      use: ["@svgr/webpack"],
    });
    return config;
  }
};

// app.js
import Logo from "logo.svg";

export default class App extends React.Component {
  render() {
    return (

          <Logo/>

    );
  }
}

Your environment

Software
Version(s)

Razzle
4.0.4

Razzle Plugins
razzle-plugin-scss

Node
v14.16.0

Browser
Chrome 89.0.4389.90 (64-bit)

npm/Yarn
Yarn 1.22.10

Operating System
Ubuntu 20.04 64Bit

TypeScript
No

React
17.0.2

@jaredpalmer FYI

Can confirm this is happening on a fresh create-razzle-app application with your configuration applied.
I think this is caused by the default configuration. There is already a file-loader configured for .svg. One solution could be this:
  modifyWebpackOptions({ options: { webpackOptions } }) {
    webpackOptions.fileLoaderExclude = [
      /\.svg$/,
      ...webpackOptions.fileLoaderExclude,
    ];
    return webpackOptions;
  },

However, that prevents you to refer to SVGs as external assets, e.g. in CSS files. If you follow https://react-svgr.com/docs/webpack/#using-with-url-loader-or-file-loader it works.
  modifyWebpackConfig(opts) {
    const config = opts.webpackConfig;
    config.module.rules.push({
      test: /\.svg$/,
      use: ["@svgr/webpack", "url-loader"],
    });
    return config;
  },

Usage:
import React from "react";
import logoUrl, { ReactComponent as Logo } from "./react.svg";

class Home extends React.Component {
  render() {
    return (
      <>

        <Logo />
      </>
    );
  }
}

export default Home;

Not sure if this is a bug. I also encountered a similar issue when I introduced specific loaders for SVGs. Maybe this is more of a gotcha that could be documented?

Use a resourceQuery and add the rule at the top, just use unshift instead of push, so you can do
import Logo from "logo.svg?component";


Creating maintainers entry for the new sort library

Thanks for your other fixes to import the sort library.  Do I need to do something, or will this file automatically include sort in the future?


Feature request: Support Consul Connect

Consul Connect is a new open source feature of consul that enables secure communications with TLS for services connected to consul.
https://www.hashicorp.com/blog/consul-1-2-service-mesh

Can you explain more about what this is? We already support TLS connections for Consul SD.

Consul Connect is a new feature of Consul (currently beta) that enables transparent TLS connection between services configured by Consul. It means that prometheus could transparently scrape metrics using https.

See also: https://www.consul.io/intro/getting-started/connect.html

I've read the docs, but they're not very illuminating. How does this work under the covers?
We don't support bespoke auth mechanisms as that would be a maintenance nightmare, so unless this is a standard http proxy (which we already support) it's unlikely this will be supported. Prometheus would also continue to need access to individual instances, which I'm not sure if this provides. If there's new metadata (which I presume there is) we can expose it via SD.

@roidelapluie - off topic - please see my email regarding promcon. We could then publish our schedule.

@RichiH Hi, I see no email from you.

@RichiH found the mail and ti is OK for me.

(JFTR, the short off-topic chat is over, we have confirmation :)

Here it is, a small POC.
in consul.d, add prometheus.json
{
   "service": {
      "connect": {
         "proxy": {
            "config": {
               "upstreams": [
                  {
                     "destination_name": "prometheus",
                     "local_bind_port": 1234
                  }
               ]
            }
         }
      },
      "name": "prometheus",
      "port": 9090
   }
}

Run:
consul agent -dev -config-dir=consul.d

Run prometheus.
Then, you can connect to http://<IP_ADDRESS>:1234 (not https); that will use tls behind the scene.
Multiple questions remain:

How can we fetch metrics of all the services? Because port 1234 currently will redirect you to one of the sane services.
how can we get the extra metadata to know which port to connect to?

So my assumption for the two answers before is that we would need to implement connect client directly inside prometheus. While that should not be that much work that would still be work.
Maybe we can also take this outside of prometheus and try to make a consul-connect file_sd provider but because there are so many prometheus users using consul that would be sad.

So my assumption for the two answers before is that we would need to implement connect client directly inside prometheus. While that should not be that much work that would still be work.

I don't think it's appropriate to start implementing service mesh support inside Prometheus (we can't maintain SDs as-is, we don't need a whole new category of thing to maintain). If someone needs this they can always use the existing proxy_url.

Maybe we can also take this outside of prometheus and try to make a consul-connect file_sd provider but because there are so many prometheus users using consul that would be sad.

Presuming you can solve 1., this would likely be possible with consul_sd, some new metadata, and relabelling. You'd probably still need a connect-aware proxy though.

there are so many prometheus users using consul that would be sad.

That's kinda like saying that Prometheus supports EC2 SD, so why doesn't it support using RDS as a backing store. Discovery and scraping are different layers of the stack.

I have opened https://github.com/hashicorp/consul/issues/4298
If it gets implemented, I will write some documentation about that (& blog posts).
In the meantime let's keep this issue open ; maybe I will get other ideas.


[SuperEditor][iOS] Fix exception when moving floating cursor between paragraphs (Resolves #1449)

[SuperEditor][iOS] Fix exception when moving floating cursor between paragraphs. Resolves #1449
Moving the floating cursor between paragraphs causes an exception when the selection sits at an offset bigger than the newly selected paragraph length.
The cause is that the IME generates non-text deltas while the floating cursor is moving. After the selection already changed to the other paragraph, we receive a non-text delta for the previously selected paragraph. This causes an IME mapping error.
This PR changes DocumentImeInputClient to ignore deltas while the floating cursor is being displayed.
Related flutter ticket: https://github.com/flutter/flutter/issues/134989

This PR changes DocumentImeInputClient to ignore deltas while the floating cursor is being displayed.

This sounds like a problem waiting to happen. What if content actually changes while the floating cursor is moving? For example, what would happen in a multi-user experience when another user is adding or deleting text while the primary user happens to be moving a floating cursor?

But in a multi user experience, changes from other users won't generate IME deltas, right?
We could also be cautious and only ignore if the delta list contains only non-text deltas

Ok, let's try ignoring non-text deltas in that case. But, I think we still need to be careful about which ones we ignore. For example, it's possible that a non-text delta is used in the middle of editing deltas:
Set selection
Delete
Insert
Set selection
Insert
Even if we're moving the floating cursor, we can't ignore those non-text selection deltas, because those selection changes are being used to facilitate the editing.
I think we probably only want to ignore non-text deltas when the delta batch ONLY has non-text deltas.
What do you think?

I think we probably only want to ignore non-text deltas when the delta batch ONLY has non-text deltas.
What do you think?

I agree. In fact, I pushed a commit yesterday with that change. With this change we will only ignore the batch if it contains only non-text deltas.


Connect UART direct to Raspi GPIO

Hi, I connected the UART connector from BMS directly to my Raspi GPIO ports , and can read the data via /dev/ttyS0 .
But no luck to use your script to send the data via mqtt to my mqtt iobroker on my windows server.
I would apriciate for some help.
Best wishes
Ralf

Sorry but I've only used it through USB. No idea how it would work through gpio pins

Do you have an idea ?
ralle@raspi-ahoy:~/dalybms $ ./run.sh
Starting BMS monitor...
Traceback (most recent call last):
File "/home/ralle/.local/lib/python3.9/site-packages/serial/serialposix.py", line 322, in open
self.fd = os.open(self.portstr, os.O_RDWR | os.O_NOCTTY | os.O_NONBLOCK)
FileNotFoundError: [Errno 2] No such file or directory: 'null'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/ralle/dalybms/./monitor.py", line 15, in
ser = serial.Serial(os.environ['DEVICE'])  # open serial port
File "/home/ralle/.local/lib/python3.9/site-packages/serial/serialutil.py", line 244, in init
self.open()
File "/home/ralle/.local/lib/python3.9/site-packages/serial/serialposix.py", line 325, in open
raise SerialException(msg.errno, "could not open port {}: {}".format(self._port, msg))
serial.serialutil.SerialException: [Errno 2] could not open port null: [Errno 2] No such file or directory: 'null'


python312Packages.pycontrol4: 1.1.2 -> 1.2.0

Description of changes
Diff: https://github.com/lawtancool/pyControl4/compare/refs/tags/v1.1.2...v1.2.0
Changelog: https://github.com/lawtancool/pyControl4/releases/tag/v1.2.0
Home Assistant PR: https://github.com/home-assistant/core/pull/124750

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 337965 run on x86_64-linux 1

13 packages built:

home-assistant-component-tests.control4
python311Packages.pycontrol4
python311Packages.pycontrol4.dist
python311Packages.python-engineio-v3
python311Packages.python-engineio-v3.dist
python311Packages.python-socketio-v4
python311Packages.python-socketio-v4.dist
python312Packages.pycontrol4
python312Packages.pycontrol4.dist
python312Packages.python-engineio-v3
python312Packages.python-engineio-v3.dist
python312Packages.python-socketio-v4
python312Packages.python-socketio-v4.dist

How very cool that they're forking socketio and engineio :shrug:


Variable adds final modifier

If these variables do not add final modifiers, there will be ambiguity and security risks.

Potential security vulnerabilities should be reported privately to<EMAIL_ADDRESS>Not in a  PR or any other public forum.
That said, there are no valid security risks here so - fortunately - no harm is done.
The additional of final here (and the many, many other places tools such as UCDetector will identify automatically) is more a matter of style than anything else.
Making invalid claims of 'security risks' is not helpful. It undermines the credibility of the PR and makes it more likely it will be rejected.
We generally do not make changes purely for stylistic reasons. There is a code quality case that could be made for this change but it isn't a particularly strong one.
I am -1 on the PR as currently submitted due to the incorrect statement regarding security risks in the commit comment.

That's a very useful reminder for me, if a PR is pulled, it also needs to have a decent description as well, otherwise misleading information gets into the commit info [and for sure it is the sort that would bring us trouble]. So -1 as well for this reason.

I am very sorry, this is the first time I submit the code, because I am Chinese, my English is a little poor, there are errors in the description. Thank you very much for your guidance. I will continue to work hard.


Can't create resource oneview_server_profile_template

Hi,
i can't create a oneview_server_profile_template resource.
First of all, we don't use enclosure groups at all, but the key is required in terraform. Via the webinterface we actually can create Server Profile Templates without an enclosure group.
So i tried to create an empty enclosure group named "empty". But that does not work. The plugin crashes.
Any ideas?
Resource:
resource "oneview_server_profile_template" "DL360_Gen9_1_legacy" {
  name = "DL360 Gen9 1 legacy"
  enclosure_group = "empty"
  server_hardware_type = "DL360 Gen9 1"
}

With empty enclosure group:
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # oneview_server_profile_template.DL360_Gen9_1_legacy will be created
  + resource "oneview_server_profile_template" "DL360_Gen9_1_legacy" {
      + affinity              = "Bay"
      + enclosure_group       = "empty"
      + etag                  = (known after apply)
      + hide_unused_flex_nics = true
      + id                    = (known after apply)
      + mac_type              = "Virtual"
      + name                  = "DL360 Gen9 1 legacy"
      + serial_number_type    = "Virtual"
      + server_hardware_type  = "DL360 Gen9 1"
      + type                  = "ServerProfileTemplateV1"
      + uri                   = (known after apply)
      + wwn_type              = "Virtual"
    }

Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

oneview_server_profile_template.DL360_Gen9_1_legacy: Creating...
╷
│ Error: Plugin did not respond
│
│   with oneview_server_profile_template.DL360_Gen9_1_legacy,
│   on server_profile_template.tf line 1, in resource "oneview_server_profile_template" "DL360_Gen9_1_legacy":
│    1: resource "oneview_server_profile_template" "DL360_Gen9_1_legacy" {
│
│ The plugin encountered an error, and failed to respond to the
│ plugin.(*GRPCProvider).ApplyResourceChange call. The plugin logs may
│ contain more details.
╵

Stack trace from the terraform-provider-oneview_6.0.0-13.exe plugin:

panic: interface conversion: interface {} is []interface {}, not *schema.Set

goroutine 55 [running]:
github.com/HewlettPackard/terraform-provider-oneview/oneview.resourceServerProfileTemplateCreate(0xc000428690, 0x12eb6c0, 0xc00044e200, 0x2, 0x1c1e9e0)
	github.com/HewlettPackard/terraform-provider-oneview/oneview/resource_server_profile_template.go:1007 +0x7ad9
github.com/hashicorp/terraform-plugin-sdk/helper/schema.(*Resource).Apply(0xc000541b80, 0xc000840280, 0xc000488720, 0x12eb6c0, 0xc00044e200, 0x12d9901, 0xc0000b6828, 0xc0006a1320)
	github.com/hashicorp/terraform-plugin-sdk@v1.7.0/helper/schema/resource.go:305 +0x375
github.com/hashicorp/terraform-plugin-sdk/helper/schema.(*Provider).Apply(0xc00017af00, 0xc0005afa10, 0xc000840280, 0xc000488720, 0xc000685ee8, 0xc00059a5d8, 0x12db5c0)
	github.com/hashicorp/terraform-plugin-sdk@v1.7.0/helper/schema/provider.go:294 +0xa5
github.com/hashicorp/terraform-plugin-sdk/internal/helper/plugin.(*GRPCProviderServer).ApplyResourceChange(0xc00059a0b0, 0x15fec80, 0xc00087e000, 0xc00081c060, 0xc00059a0b0, 0xc00087e000, 0xc000301b78)
	github.com/hashicorp/terraform-plugin-sdk@v1.7.0/internal/helper/plugin/grpc_provider.go:885 +0x8ab
github.com/hashicorp/terraform-plugin-sdk/internal/tfplugin5._Provider_ApplyResourceChange_Handler(0x13ebd80, 0xc00059a0b0, 0x15fec80, 0xc00087e000, 0xc00081c000, 0x0, 0x15fec80, 0xc00087e000, 0xc00087c000, 0x321)
	github.com/hashicorp/terraform-plugin-sdk@v1.7.0/internal/tfplugin5/tfplugin5.pb.go:3189 +0x214
google.golang.org/grpc.(*Server).processUnaryRPC(0xc000584600, 0x1608660, 0xc000585200, 0xc0007f2100, 0xc000704510, 0x1bdba40, 0x0, 0x0, 0x0)
	google.golang.org/grpc@v1.27.1/server.go:1024 +0x522
google.golang.org/grpc.(*Server).handleStream(0xc000584600, 0x1608660, 0xc000585200, 0xc0007f2100, 0x0)
	google.golang.org/grpc@v1.27.1/server.go:1313 +0xd54
google.golang.org/grpc.(*Server).serveStreams.func1.1(0xc0000941e0, 0xc000584600, 0x1608660, 0xc000585200, 0xc0007f2100)
	google.golang.org/grpc@v1.27.1/server.go:722 +0xa8
created by google.golang.org/grpc.(*Server).serveStreams.func1
	google.golang.org/grpc@v1.27.1/server.go:720 +0xa8

Error: The terraform-provider-oneview_6.0.0-13.exe plugin crashed!

This is always indicative of a bug within the plugin. It would be immensely
helpful if you could report the crash with the plugin's maintainers so that it
can be fixed. The output above should help diagnose the issue.

Using terraform 0.15.1 and OneView 6.00.00.

@Schluggi Hello Lukas, Thank you for raising this issue, as of now enclosure_group is a required attribute in the provider, and hence the terraform crashes. We will take the necessary actions to address this in our upcoming release.

By the way, thank you @AsisBagga for your quick attention to all the issues.   I will say that server profile/templates are probably the area of most concern for anyone using Oneview.  Most of the other configuration falls into the initial install-time configuration pieces so, whilst important they are not the "moving" pieces you would need to ongoing manage with a config management tool.
If we can get terraform to do the right thing against all the CRUD for server profiles this tool will be far better than managing with ansible, powershell, or any of the others, since folks will be able to declare the state of the infrastructure in a easily composable manner, which I think is a core goal of Synergy.  This will be better than imperatively managing the inf.
Just wanted to lend my gratitude for all the hard work.

@rismoney Thank you, we are continuously thriving to make this provider as efficient as possible for our users, thank you for raising issues for getting them to our attention.

Since this issue is fixed. Proceeding with closing it.


Interface to allow migration assemblies to load database drivers

This patch provides an interface (IDbFactoryLoader) to allow loading database drivers.
It enables user to load assemblies/drivers in the migration assembly, without modifying the app.config (or Migrator.exe.config provided with the nuget package).

I think I am missing somthing here.  So anyones else please help me see.
But from looking at the code you have changed a nice clean call to CreateAndUnwrap whih loads a type from the current appdomain or Loads the named assembly into the current appdomain and then loads the type.
Into a mass of code that scanning the assemblies in the current appdomain to see if the type exists and then calls CreateAndUnwrap at the end if you can find the type to let the framework do the same thing.
What issue were you trying to solve?  Sorry if I completely wrong.  It is quite late.

Sorry for the lack of details.
The patch allows user to load drivers that are not in GAC and potentially outside the AppBase directory relative to Migrator.exe. Since modifying Migrator.exe.config isn't a good option where the directory is maintained/updated by NuGet; allowing drivers to be loaded programmatically seems to be a good option. Patch can also provide support for driver wrappers.
Reason to use Activator.CreateInstance() rather than CreateAndUnwrap() is that CreateAndUnwrap() triggers an Assembly.Load() variant, which fails even if the assembly is loaded in AppDomain.
Here is our case for a concrete example:
We have a large web application, that consists of multiple projects, including a Migration project. External dependencies (like Mysql.Data, or FluentMigrator) are maintained by nuget. MySql.Data isn't installed on GAC (either on development PCs, or production servers). To be able to maintain integrity, Migration project has a dependency on the MySql.Data pacakge as well, and mysql.data.dll is copied to the output directory of the migration project.
Example execution:
..\packages\FluentMigrator.<IP_ADDRESS>\tools\Migrate.exe --verbose=true --assembly ..\XXXX.Data.Migrations\bin\XXXX.Data.Migrations.dll --provider mysql --connectionString "Server=localhost;Database=XXXXService;Uid=XXXXUser;Pwd=XXXX" --task migrate --profile "develop"

Without the patch, Migrator.exe fails to locate mysql.data.dll.
Example implementation:
	public class MySqlDbFactoryLoader : IDbFactoryLoader
	{
		public void LoadDbFactory()
		{
			var driverUri = new Uri(new Uri(Assembly.GetExecutingAssembly().CodeBase), "MySql.Data.dll");
			Assembly.LoadFile(driverUri.LocalPath);
		}
	}

I hope that I'm not missing something obvious.
Thanks

Please ignore last 2 commits. They were supposed to be on a separate branch.


⚠ Cioos National CKAN has degraded performance

In 58c8cd8, Cioos National CKAN (https://catalogue.cioos.ca/) experienced degraded performance:

HTTP code: 200
Response time: 17047 ms

Resolved: Cioos National CKAN performance has improved in 2ecf84c after 31 minutes.


1.4.0 regression: infinite loop with COPY . .

/kind bug
Steps to reproduce the issue:

git clone https://github.com/openshift/machine-config-operator/

podman build -t localhost/machine-config-server:latest -f Dockerfile.machine-config-server --no-cache

Describe the results you received:
Indefinite hang at STEP 3: COPY . .
Describe the results you expected:
Successful build.
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
root@orion ~# rpm -q podman
podman-1.4.0-1.fc30.x86_64
root@orion ~# podman version
Version:            1.4.0
RemoteAPI Version:  1
Go Version:         go1.12.5
OS/Arch:            linux/amd64
root@orion ~# rpm-ostree status -b
State: idle
AutomaticUpdates: stage; rpm-ostreed-automatic.timer: last run 22h ago
BootedDeployment:
● ostree://fedora-silverblue:fedora/30/x86_64/silverblue
                   Version: 30.20190610.0 (2019-06-10T00:41:42Z)
                BaseCommit: 79ea01d81ad1c6d3be6f7d699ff94326b8f04deb82d88b5ebec4326a89b23e81
              GPGSignature: Valid signature by F1D8EC98F241AAF20DF69420EF3C111FCFC659B9
      ReplacedBasePackages: containernetworking-plugins 0.7.4-2.fc30 -> 0.7.5-1.fc30, podman 2:1.3.1-1.git7210727.fc30 -> 2:1.4.0-1.fc30
           LayeredPackages: firefox-wayland fish fuse-sshfs git-evtag gnome-tweak-tool gstreamer1-plugin-openh264 gstreamer1-plugins-ugly-free keepassx krb5-workstation libva-vdpau-driver libvirt-client libvirt-daemon-driver-qemu mozilla-openh264 opensc
                            pcsc-lite-ccid qemu-kvm strace sway tilix tmux virt-manager xsel ykclient ykpers
root@orion ~#

Output of podman info --debug:
podman info --debug
debug:
  compiler: gc
  git commit: ""
  go version: go1.12.5
  podman version: 1.4.0
host:
  BuildahVersion: 1.8.3
  Conmon:
    package: podman-1.4.0-1.fc30.x86_64
    path: /usr/libexec/podman/conmon
    version: 'conmon version 0.2.0, commit: f111af8a1cf9563213ee49df9cf1de79a0dd6e6f'
  Distribution:
    distribution: fedora
    version: "30"
  MemFree:<PHONE_NUMBER>8
  MemTotal:<PHONE_NUMBER>2
  OCIRuntime:
    package: runc-1.0.0-93.dev.gitb9b6cc6.fc30.x86_64
    path: /usr/bin/runc
    version: |-
      runc version 1.0.0-rc8+dev
      commit: e3b4c1108f7d1bf0d09ab612ea09927d9b59b4e3
      spec: 1.0.1-dev
  SwapFree: 0
  SwapTotal: 0
  arch: amd64
  cpus: 8
  hostname: orion
  kernel: 5.1.7-300.fc30.x86_64
  os: linux
  rootless: false
  uptime: 24h 56m 28.01s (Approximately 1.00 days)
registries:
  blocked: null
  insecure: null
  search: null
store:
  ConfigFile: /etc/containers/storage.conf
  ContainerStore:
    number: 29
  GraphDriverName: overlay
  GraphOptions:
  - overlay.mountopt=nodev,metacopy=on
  GraphRoot: /var/lib/containers/storage
  GraphStatus:
    Backing Filesystem: xfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "true"
  ImageStore:
    number: 458
  RunRoot: /var/run/containers/storage
  VolumePath: /var/lib/containers/storage/volumes

Additional environment details (AWS, VirtualBox, physical, etc.):
physical

@TomSweeneyRedHat PTAL

I've a strong suspicion that this is the same issue as: https://github.com/containers/buildah/issues/1578

@TomSweeneyRedHat if you replicate this, just connect to the pid with dlv and you will know right away whats going on ... if you need help with this one, let me know.

@baude given the other irons in the fire that I have atm and my suspicion that @nalind has a fix in flight, I'll most likely wait until early next week to check in with him when he returns.

This is definitely a regression, works fine with podman-1.3.1-1.git7210727.fc30.x86_64.

@TomSweeneyRedHat We're not expecting a fix for this in the Buildah revendor tomorrow, right?

@mheon, unless the Buildah Fix Fairy swings by, I'm not suspecting this will be fixed for 1.8.4

Alright, Podman 1.5.0 it is, then.

The first of the two dots in the Copy command seem to be the issue.  If I change that first dot to a file or even an '*' (asterisk), it seems to work.   Smaller reproducer:
# cat ~/Dockerfile.copyhang
FROM alpine
WORKDIR /tmp
COPY .  .

# buildah bud --layers -t tom -f Dockerfile.copyhang .

@cgwalters if you have a chance, can you try running your build command with --log-level debug added?  podman --log-level debug build ...?  Adding that seems to make things work for me and I'm not quite understanding why ATM.

@cgwalters @TomSweeneyRedHat any updates fellas?

Lets say this is fixed in podman 1.5, and reopen if I am mistaken.

Did a test with rootless and
$ rpm -q podman
podman-1.5.1-3.fc30.x86_64

and yeah, seems to work now.


Fix typo in Kubernetes Sysdig page heading

Kubernetes was typoed as "Kubenrnetes".

Hi @itowlson, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Ivan Towlson). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

@itowlson : Thanks for your contribution to the Azure documentation! The author, @bburns, has been notified to review your proposed change.

#please-close
Sorry for the delay on this, the initial owner has not responded. I've checked and this has already been updated.


Update Backend for Additional Modes

This PR is created for #912 to complete backend.
@JonasVautherin thanks, especially kindly helping and responding.
Sorry for a lot of commits, I'm not good at git :) But I'm keeping my eyes open to learn.

@bozkurthan: I made the update myself, so that you can see what files were modified. All I did was updating the proto/ submodule, and running generate_from_protos.sh :blush:.

Thank you for all :+1:


Add azure static website component

thank YOU for making the component! :tada: I am realizing now, I think we need to add a docs folder with the index.md and installation-configuration.md files to the azure-static-website repo before merging this. I think there is a job that runs that tries to keep those files in sync with these that are in the registry. I'll get those added.


sciCAR Fragment file

Hello,
I wonder of is have tried your code over sciCAR data as well or not ?
and If so, what is the optimal parameters that i have to use in order to avoid the pitfalls of generating the fragment file for the sciCAR dataset.
I'm Currently working on the Mouse Kidney sample of sciCAR .
Thanks

I have not, but I'm sure you could follow a similar workflow to the one in this repo to process sciCAR data also.

Hello,
May I ask why I have been stuck in the first step？
Collecting package metadata (repodata.json): failed
CondaHTTPError: HTTP 000 CONNECTION FAILED for url https://conda.anaconda.org/bioconda/linux-64/repodata.json
Elapsed: -
An HTTP error occurred when trying to retrieve this URL.
HTTP errors are often intermittent, and a simple retry will get you on your way.
'https://conda.anaconda.org/bioconda/linux-64'

Sounds like a conda issue https://github.com/conda/conda/issues/9555


Victory Area Cuts at the max and min values

You can see above,
All my charts are cutted-off at the max and min values.
If I remove "interpolation" graph stops cutting-off.
But I want to make it cardinal.
I'm sharing code below.
What could be solve?
         ```

<VictoryArea
style={{
data: { fill: '#ffe2e5', stroke: '#f64e60', strokeWidth: 2 },
}}
height={250}
interpolation="cardinal"
data={dashboard}
padding={{ left: 10, right: 10 }}
animate={{
duration: 2000,
onLoad: { duration: 1000 },
}}
/>

@tcagkansokmen VictroyArea uses a clipped groupComponent which is what allows the curtaining effect for animations, but is also what is clipping off the tops and bottoms of your path. You have a couple options.

If you're not using animations, you can replace your groupComponent with a standard  tag from rn-svg like groupComponent={<G />}
you can add a bit of domain padding to give your area component more space. Here's some more information about the domainPadding prop: https://formidable.com/open-source/victory/docs/common-props/#domainpadding


"Fix" syntax in vocabulary.rb that Ruby versions < 2.2.5

don't parse properly. Set Travis to test on 2.2.2, not just 2.2, which defaulted to 2.2.7 at the time of this fix.
Fixes #386.

Coverage decreased (-0.01%) to 92.261% when pulling 97d81a7a40188913421ec7f2c4e39cd8f6e3fdb7 on feature/2.2.2-compat into d42c565cb80465a7f2c725b77a94605f9a807672 on develop.


It seems the trinity process doesn't respect the specified number of cpus

When I ran the test it was using around 4 cpus instead of the specified 2.

Hopefully fixed in ce610e72b218fd9c7fde804df18c0da07f18b25c.


Improve compatibillity with CardanoSharp-Wallet

CardanoSharp-Wallet and blockfrost-dotnet combined will be a great tool to develop on the cardano blockchain. However, there's quite some room for improvements.
I wanted to create a Transaction that I previously serialized with CardanoSharp-Wallet. However, the data types of the two libraries do not match.
...
// Create serialized transaction using CardanoSharp.Wallet.Models.Transactions.Transaction
var signedTx = transaction.Serialize();

// Use blockfrost-dotnet to submit the transaction
transactionService.SubmitAsync(signedTx); // doesn't work because signedTxSerialized is byte[] but a string is expected

What also seems to be wrong is the way the data is transmitted. In ABlockfrostService.SendPostRequestAsync(), which is used for the above call to transactionService.SubmitAsync(signedTx), the following code is present:
// line 345, pretty sure the StringContent doesn't work for binary data.
request_.Content = new StringContent(content, System.Text.Encoding.UTF8, "application/cbor");

POST will be in the next release... '0.0.5`
As we move to 0.1.x there will be an extensions for CS-Wallet to support their types before we have a major update of the API to improve DevExp with much cleaner namespaces and method names...

I tried to use the .ToStringHex() extension method of CS-Wallet, but this also doesn't seem to be correct.
transactionService.SubmitAsync(signedTxSerialized.ToStringHex())

The error message I get is simply 400: Bad request. So I don't know what exactly I did wrong..
Is there an example on how the Tx has to be formatted for the blockfrost API to accept it?

This is what I am going to do to test (and fix) it
sh```
Assuming tx.signed is signed transaction constructed by cardano-cli
xxd -r -p <<< $(jq .cborHex tx.signed) > tx.submit-api.raw
curl "https://cardano-mainnet.blockfrost.io/api/v0/tx/submit"
-X POST
-H "Content-Type: application/cbor"
-H "project_id: $PROJECT_ID"
--data-binary @./tx.submit-api.raw

I tried to use the .ToStringHex() extension method of CS-Wallet, but this also doesn't seem to be correct.

There was a bug with a control character at the end of the CBOR a while ago with the ToStringHex method.. i think it got fixed (not sure tough). I would use cardano-cli for now to sign the transaction

As you pointed out the StringContent is probably the issue ... you could try this and hope for the best 😅
var hex = signedTxSerialized.ToStringHex():
var raw = hex.HexToByteArray();
using MemoryStream stream = new MemoryStream(raw);
await transactionService.SubmitAsync(raw)

Ok there are a couple of issues here:

Add predefined test vectors known to work on cardano-cli
Create sender and receiver wallets for tests
Submit transaction via stream
Submit transaction via string
Verify transaction submit

We will keep this open until we release v0.1

Continued here https://github.com/blockfrost/blockfrost-dotnet/pull/30#pullrequestreview-735612348

...nope. this is not done


Rhel9

@arjuhe I opened a new PR because pushing to your branch proved a pain.

@arjuhe Could you take a look at this again :)


Enforce that no PASE sessions that aren't commissioning are possible

For v1, we do not support operational PASE, so PASE is only permissible during commissioning.
In access control, for v1 we grant any PASE session the administer privilege, since it's appropriate given commissioning can be taken for granted.
Therefore, we need to enforce in the SDK that in v1 it is not possible to create a non-commissioning PASE session. This may already be the case but we need to double check.

PASE session establishment is only allowed once the commissioning window manager calls WaitForPairing. We already expire PASE pairings on commissioning complete, but we should also expire them when the commissioning window closes so that other nodes can't establish a long-running PASE connection and send commands after the commissioning window is closed.

Issue Scrub: We believe in the current implementation of the SDK, PASE can't be easily, or at all used. Closing.


For this purpose, add MRB_PROC_NOARG to struct RProc::flags.

This PR has been merged as commit 668b12e7566282f6c0165252e2b2f5432964020a.


applyCss warning in Angular 9.1

In my code I am using
<svg-icon *ngIf="gameDate" class="arrow-icon" src="{{ environment.iconPath }}chevron-left.svg" [applyCss]="true" (click)="selectPrevDate()"></svg-icon>
But just today I tried to upgrade my project into Angular 9. I think it was successful except there are lots of warning that appeared in my Chrome console saying applyCss deprecated since 9.1.0, will be removed in 10.0.0 and use applyClass instead. Of course I tried applyClass but its not supported by angular-svg-icon. Im using version 9.2.0

Are you absolutely certain you're using 9.2.0? Because [applyClass]="true" is working in this stackblitz I just made.


Session token lifetime

Hi , this document mentions that refresh token lifetimes need to be set via Conditional Access whereas Access token lifetimes can be set via token lifetime policy . There are 2 other token lifetimes Single-Factor Session Token Max Age and Multi-Factor Session Token Max Age. Will this also be handled via Condtional Access Policies.

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

ID: 02ff3d62-dc0e-ad0c-f5ae-418337cf31e4
Version Independent ID: d50952b5-6b98-c40d-d3a3-f9cbec58dd28
Content: Configurable token lifetimes in Azure Active Directory
Content Source: articles/active-directory/develop/active-directory-configurable-token-lifetimes.md
Service: active-directory
Sub-service: develop
GitHub Login: @rwike77
Microsoft Alias: ryanwi

@prashantkarkera  , Thank you for your feedback. We will investigate and get back to you shortly.

@prashantkarkera
The later parts in the article indicate that token lifetime policies are used for these session tokens, but since configurable token lifetimes are being discontinued I believe that conditional access will handle this and per my understanding it is the recommended approach
@rwike77 can you pleases confirm and consider adding a note to the article?

@prashantkarkera  I believe that conditional access will be used to configure lifetimes for refresh tokens, only.  Session tokens (and the max age property) will continue to be configured using Configurable Token Lifetime policy.  @hpsin, could you please confirm?  Thanks

Forwarded thread internally to the owner for lifetimes, thanks Ryan.

@hpsin, any updates?  Thanks.

Only access token lifetimes will be supported in the future.  Session and refresh tokens will not be changeable once the deprecation occurs.

Thanks @hpsin, I'll update the article to make this clear.

@prashantkarkera I updated the note at the top of the article to state that session and refresh token lifetimes will not be changeable after the deprecation.  Updates to the article should post live this afternoon.  Thanks for bringing this up.  #please-close

No, it means they cannot be impacted any longer by policy.

@hpsin . By policy are you referring to conditional access or token lifetime policy ( via powershell) .

Token lifetime policy, my apologies, I missed a key word in your question.  I don't have details on the CA based management.

@hpsin No worries, so session tokens can no longer be configured via token lifetime policy. The only other thing that is not clear is whether session tokens are also configured via Conditional Access (similar to refresh tokens)


Trường ĐH Mở Tp.Hồ Chí Minh

@phuong-ntn9 I am closing this as a duplicate to already merged #7819. Thank you.


Problem updating to 0.7.0

Hi,
I started the upgrade on my virtual dev system and while the stories seem to display fine (besides the DOM changes for which I need to update our theme) the admin panel cannot be opened:

Please be so kind to help me in getting round this. Not sure where I made a mistake. Is there anything more you need to understand the issue?
Thanks a lot in advance!
Cheers,

Hi,
is it possible that you are using Rails 4.1 and Formtastic 2.3.0.rc2? I had to update Formtastic to 2.3.0. Rails 4.1 appears to have changed some interfaces of form builder methods which older Formtastic version rely on. If that's not it, please provide the full stack trace of the exception.
Cheers

hi tf,
Switched to:
Using rails 4.0.2 (was 4.1.9)
Using formtastic 2.3.0 (was 2.3.0.rc2)
Works now. Thanks for the pointers. BTW, when using older rails but formtastic rc2 it spits out deprectaion warnings. Looks like extra .css in the scss files (active admin) is no longer necessary.
Thanks again!
Cheers,

I'd recommend sticking with 4.1. Rails 4.0 no longer receives security fixes. So you'll need to update sooner or later anyway. See the Gemfile fragment in the README for a working set of gems for Rails 4.1.
Regarding the deprecation warnings: We'll remove the extra file suffix eventually, but for now it does not hurt far es I can tell.
Cheers

thanks for the hint. Using rails 4.1.9 works fine when the state_machine is added as per the README.


QT static build misses dependecies - windows binaries

By building windows binaries, not all required dependencies were built into the binary.

L900
On Jul 29, 2017 5:25 PM, "Cevap Master"<EMAIL_ADDRESS>wrote:

By building windows binaries, not all required dependencies were built
into the binary.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cevap/ion/issues/62, or mute the thread
https://github.com/notifications/unsubscribe-auth/AK2jS6w0W7t8oRnkVcEMs74Csyk0qPi6ks5sS7FrgaJpZM4Onerx
.

I'm pl0
On Jul 29, 2017 6:58 PM, "Adam Matlack"<EMAIL_ADDRESS>wrote:
L900
On Jul 29, 2017 5:25 PM, "Cevap Master"<EMAIL_ADDRESS>wrote:

By building windows binaries, not all required dependencies were built
into the binary.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cevap/ion/issues/62, or mute the thread
https://github.com/notifications/unsubscribe-auth/AK2jS6w0W7t8oRnkVcEMs74Csyk0qPi6ks5sS7FrgaJpZM4Onerx
.


APR does not reflect external incentives

Seems like the UI only shows APR for OSMO incentives and not external ones.
https://app.osmosis.zone/pool/604
https://app.osmosis.zone/pool/611
vs
https://api-osmosis.imperator.co/apr/v1/604
https://api-osmosis.imperator.co/apr/v1/611

As of today, I noticed the APR seems to reflect external incentives!

wip as part of refactor #163

@Thunnini adding this to in progress in the project

This API will return everything mashed into one, so you'll want to separate them out, e.g.
// calling imperator, e.g. https://api-osmosis.imperator.co/apr/v1/604
const [{ apr_list }] = await validator.getPoolApr(poolIds[p]);

const osmoIncentives = apr_list
  .filter((i) => new Date(i.start_date) <= new Date() && i.symbol == 'OSMO');

const externalIncentives = apr_list
  .filter((i) => new Date(i.start_date) <= new Date() && i.symbol != 'OSMO');

const futureIncentives = apr_list
  .filter((i) => new Date(i.start_date) > new Date());

@pyramation:
For fetching Imperator data, we may want to take the approach delivan took with the pool fees API for the refactored pools page. His mobx store object extends @keplr-wallet/stores/ObservableQuery which will manage the Axios instance for us. It also uses computedFn from mobx-utils which memoizes query results/references -- it works well with React's frequent re-rendering without having to write error-prone useMemo logic ourselves.

For fetching Imperator data, we may want to take the approach delivan took with the pool fees API for the refactored pools page.

100% — after digging more into the code today, I think internal, external, and future incentives would be memoized, computed functions. Now I'm seeing the light!


the weired structure of double strand DNA

i ran a prediction for the case where protein dimer recognize a 32bp dsDNA,but the prediction structure has met the double strand spliting far away from each other.This is not a normal phenomenon and is there any training issue or any problem of my input?

i give the two protein fasta and the dna fasta as the input

I am also running into these types of issues.


feat: Upgrade Az.* dependent modules

Closes https://github.com/arcus-azure/arcus.scripting/issues/436

Are these changes too big to be in a minor release? Meaning: would releasing this as the next minor release break any scripts on existing DevOps piprlines that use it?
Wondering if we should play it safe and see this as a breaking change. 🤔

Are these changes too big to be in a minor release? Meaning: would releasing this as the next minor release break any scripts on existing DevOps piprlines that use it? Wondering if we should play it safe and see this as a breaking change. 🤔

I don't think so, all the unit and integration tests still work.


Only report last week's PRs in weekly stats

This fixes https://github.com/AnalyticalGraphicsInc/cesium-concierge/issues/135 and adds a test to ensure that it works.

Thanks for the pull request @OmarShehata!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:sparkles: :sparkles: :sparkles:I'm the Cesium Concierge and I'm here to test things. :sparkles: :sparkles: :sparkles:

@ggetz

@ggetz actually let me see if I can also filter out prs that were closed instead of merged and I'll ping you again

I've fixed the issue with it reporting PRs that were closed instead of merged. I've updated the PR description @ggetz .

@ggetz this should be good to merge.

Thanks again for your contribution @OmarShehata!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

:sparkles: :sparkles: :sparkles:I'm the Cesium Concierge and I'm here to test things. :sparkles: :sparkles: :sparkles:

Thanks again for your contribution @OmarShehata!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

:sparkles: :sparkles: :sparkles:I'm the Cesium Concierge and I'm here to test things. :sparkles: :sparkles: :sparkles:

Oh no, please don't close this @cesium-concierge !  It's for your own good.

Thanks again for your contribution @OmarShehata!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

:sparkles: :sparkles: :sparkles:I'm the Cesium Concierge and I'm here to test things. :sparkles: :sparkles: :sparkles:

Thanks again for your contribution @OmarShehata!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

:sparkles: :sparkles: :sparkles:I'm the Cesium Concierge and I'm here to test things. :sparkles: :sparkles: :sparkles:

Thanks again for your contribution @OmarShehata!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

:sparkles: :sparkles: :sparkles:I'm the Cesium Concierge and I'm here to test things. :sparkles: :sparkles: :sparkles:

Thanks again for your contribution @OmarShehata!
No one has commented on this pull request in 30 days. Maintainers, can you review, merge or close to keep things tidy?
I'm going to re-bump this in 30 days. If you'd like me to stop, just comment with @cesium-concierge stop. If you want me to start again, just delete the comment.

:sparkles: :sparkles: :sparkles:I'm the Cesium Concierge and I'm here to test things. :sparkles: :sparkles: :sparkles:

I've opted to remove the check for first time contributors. There's no straightforward way that I can see to check for this once the PR is merged without some kind of database I can write to when the PR is first opened.
When you merge a PR and get the webhook, you can't check the branch they're merging into for CONTRIBUTORS.md because the webhook runs after the PR is merged, so their name will already be in there. You could try to go through the history of the contributors file to see if it was there at the time the PR was opened, but it seemed too much to orchestrate here so I punted on it for now.


foo_midi internal version string reported to Foobar2000, not updated to beta version #.

The current release is v<IP_ADDRESS>
and the new beta is of course v<IP_ADDRESS>_beta01
but Foobar2000 is showing v<IP_ADDRESS> in the components list.
so this is just a minor issue...
lol ;-)

Fixed in beta 2

ty


Manifest output file not created

Describe the bug
When I run through the steps identified in issue #274 after I get the "Error: Duplicate Service Name detected: [Service A]", the output manifest file is not generated.
To Reproduce
Use the steps in #274
Expected behavior
If the manifest file was generated I could at least modify it and then re-submit the file.
Additional context
See is #274

is that still valid since the removal of the slo management commands @gtfisher @daidokoro  ?
correct if I'm wrong but now the user's choice is to overwrite or quit if a manifest already exists

@dmartin35 @gtfisher
The current behavior has now been simplfied. So the init command can only:

create/overwrite a manifest yaml
check for duplicate service names at a form level
checks for an existing manifest in the default manifest path ie. ./reliably.yaml, it does not read it

Looks like this was resolved by https://github.com/reliablyhq/cli/pull/285


Use style loader directly to support css/sass livereload in development

I was immediately annoyed with having to manually refresh for style changes, when everything else was being live-reloaded.
This small change to the webpack config should allow this, while still using the text extractor for production builds.

Totally agree, thanks for this. Will check it out tomorrow.

Thanks a lot for this! I have merged with some changes.

And thank you, its a great seed project!


Remove PHPStan

Why? :(

No specific reason in particular, lately I find Psalm's configuration easier and one tool should be enough for these packages - it makes maintenance a bit easier. Still will ship both PHPStan and Psalm with main repositories - Sylius/Sylius, Sylius/Sylius-Standard and Sylius/PluginSkeleton. Thanks for your work on PHPStan 🥇

Alright, thanks :)


Add dependencies to package.json and bower.json

In order to let people npm or bower install bootstrap, we should make sure that the package files are updated with the necessary dependencies.
I see two deps (could be that a missed one):

jQuery
tether

Once the package files are updated we should also remove jQuery and tether from the vendor dir and link to the bower or npm version in the tests.
In order to get completely rid of the vendor folder, we could also add qunit as a dev dependency to the package.json.
X-ref #17201

jQuery is already listed as a dependency. Tether isn't though, and we should fix that.

we should also remove jQuery and tether from the vendor dir and link to the bower or npm version in the tests.

Meh. We don't currently use npm for client-side dependencies. And we definitely don't want to hook into Bower, since it kinda sucks isn't too actively developed these days.

jQuery is already listed as a dependency. Tether isn't though, and we should fix that.

jQuery is indeed listed in the bower file, but it's still missing in the package file ... I only see jQuery listed under the jspm deps in the package file.

but it's still missing in the package file

Like I said:

We don't currently use npm for client-side dependencies.

@cvrebert If you list npm as one of the possible ways to install bootstrap (which you're doing in the v4 docs) you should make sure all deps can be resolved correctly, no?

Actually we already list npm in the v3 docs (since last year), and nobody seems to have complained about jQuery not being in package.json's dependencies until now...
I can't think of a particular reason not to include it though, so I guess I'm not opposed adding it.
CC: @twbs/team

Probably not a lot of people were using npm to install bootstrap since it wasn't exporting any useful js modules. With the js rewrite of v4 and combined with the rise of tools like browserify and webpack that may change ... Also, like you said I don't think it would do any harm if we add deps to the package file.

X-Ref: #17273
I'm :+1: on this one for the same reasons @vejersele listed.

Absolutely :+1: it would also be very useful to use Bootstrap's JS components with ECMAScript 6 import syntax, e.g.
import {Popover, Modal} from 'bootstrap'

and use them without even knowing they depends on jQuery or Tether.

:+1: for supporting the import syntax.
I am currently trying to include Collapse plugin only and despite being able to load the plugin itself, I have no idea how to satisfy it's requirement for jQuery (despite jQuery being imported right above it) in an ES6 (Babelified) project.

+1 Same issue here since alpha 2

Why is tether a dependency if the user doesn't plan on using tooltips? Will this be solved in the final release / compiled version?

I started doing the initial legwork on proper (/better) modularization (and dependency management) of the v4 Bootstrap modules today and should have an PR up for review / thoughts some time next week.
Meanwhile @reustle you could mock window.Tether with window.Tether = function (){} to get past the dependency.

@petetnt I imported the library so it is satisfied for now, I was more curious if the dependency was going to be required in the final release. It seems weird that Bootstrap would need a hard dependency on another library (besides jQuery), especially if it is for a feature you aren't using (tooltips).

I just stumbled on another problem. The check of the Tether object being on the global window context
if (window.Tether === undefined)
will fail if Tether is used within a module loader context.
Tethers distributed version uses the universal module approach (see https://github.com/HubSpot/tether/blob/master/dist/js/tether.js#L3), so there won't be any global if it detects a module environment.

It also seems as though other files may need to be changed. Even when jQuery and tether are installed via npm manually, util.js throws an error because it can't find jQuery in the global scope on line 169.

Fixed by #18575 & #19427.
Going to say that #19017 covers the module system problems.

For those currently using bootstrap v4.0.0-alpha.2 through npm you could require Tether as a global instead of a module:
global.Tether = require('tether');
I know it's not perfect, but it's better than placing an empty function on a global Tether variable.

The error persists using CDN version.
Not installing via npm or bower.

@hougasian You want #19017.


rust: remove ruby from rustPlatform

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Probably staging?

/rebase staging

Added @andir as a reviewer, I am not sure what the expectations are wrt. the available git functionality.

The difference between git and gitMinimal is that the manuals, python and pcre2 support are not included. This removes the need ruby from the uutilsStdenv which saves me quite a bit of time while testing. Most other fetchers/builders use gitMinimal too so I think it should be save to swap them.

I would think so too.


Add static_url variable in index.j2 templates

Hello,
I need to add the static_url variable because I dont have the same URL to serve static file and render a jinja template.

Is this project abandoned ?

Hey @Maillol
Thanks for your PR - It's not something I'd like to pull in at this time.
If you're using this in connexion, it's straightforward to serve whatever files you like - these are meant to just be a sane default.


Does not work with TailwindCSS anymore

Is your feature request related to a problem? Please describe.
We're using TailwindCSS to style our website. Just upgraded this component for security reasons and found that lineNumberContainerProps and lineNumberProps were removed. Also, lineProps is not allowing us to pass custom classNames. That makes it impossible for us to use both Tailwind and this component.
You can see more here: https://github.com/asyncapi/website/blob/master/components/editor/CodeBlock.js#L61-L77.
Describe the solution you'd like
For lineNumberProps and lineNumberContainerProps either bring them back or maybe create something like lineNumberClassNames and lineNumberContainerClassNames. Happy to discuss what's better.
For lineProps, it seems the offending line is this one. Maybe this can be changed to:
properties.className = properties.className ? `${className} ${properties.className}` : className;

Describe alternatives you've considered
I've considered requiring the Tailwind configuration file from the component but that would couple the component to the config file, making it less reusable. Also considered hard-coding the values I want as inline styles but we'd get duplicated values in the config file and in this component.

Happy to help implementing the solution to this. Thanks for the great work! 🙌

Good catch! Looks like there was a PR to get rid of lineNumberContainerStyle and lineNumberStyle and replace them with   lineNumberContainerProps and lineNumberProps: https://github.com/react-syntax-highlighter/react-syntax-highlighter/pull/229 ... but somehow it was regressed with the 13.0.0 update.
If you've got a bit of time to implement a solution, we'd be grateful.

Absolutely. Do you want me to cherry pick the changes on #229?

Go for it!

@simmerer I'm having problems with it too.


Exit delay not bypassing sensors

Alarmo Version
v1.9.7
HA Version
2023.1.7
Bug description
When trying to arm, the exit delay starts, but as soon as I open the door, it stops and disables (does not arm, "bypass required"). Only way i can arm then walk out is to:

open the door
override the 'open door' sensor
walk out and close the door.

am I missing something? shouldn't the exit delay bypass any sensors for the 'exit delay' period?

Steps to reproduce

Ensure all sensors are cleared
Type in alarm code, then ARM AWAY
Delay starts "exit delay"
Open door; soon as the door opens, keypad says "bypass required" & arming is canceled.

Relevant log output
No response

Yes, you’re missing something.
In the sensors page you can click on a sensor to change its settings.
There’s a setting ‘use exit delay’ which needs to be turned on for a sensor that is allowed to be active during the exit delay.

ah thank you so much. the door sensor was set to "tamper', not 'door', and those options were not there.
much appreciate it!


Environment variables

I compiled from source and used envinronment variables in service unit file - it works OK. I mentioned the version is marked as development so I wanted to switch to stable. When i downloaded compiled 0.3.7 and replaced binary file with it, the environment variables are not noticed.
[Unit]
Description=WireGuard UI                                                                                Documentation=https://github.com/ngoduykhanh/wireguard-ui
After=network.target network-online.target
Requires=network-online.target                                                                                AssertFileIsExecutable=/usr/local/bin/wireguard-ui
[Service]
Type=simple
ExecStart=/usr/local/bin/wireguard-ui
Restart=on-failure
SyslogIdentifier=wireguard-ui                                                                                Environment="WGUI_DEFAULT_CLIENT_ALLOWED_IPS=<IP_ADDRESS>/24"                                                               Environment="SMTP_HOSTNAME=mail.fy.cz"
Environment="SMTP_PORT=587"
Environment="SMTP_AUTH_TYPE=none"<EMAIL_ADDRESS>                                                                 Environment="EMAIL_FROM_NAME=WireguardVPN"

Same for me, environment variables are not taken into account

I'm running mine using Docker Compose and noticed if you make changes to env variables it will not take it into account. The solution I found is to delete the db folder or modify the files inside if you already setup the instance.


NavigationCommand lambda with receiver

simplify callsites by using a lambda with receiver in NavigationCommand

@Zhuinden any thoughts?

I was thinking about this one, on second read it's a good idea, but I'm not sure if it'll actually make the intent of the code clearer to understand for those who see it for the first time.

I think people will still need to look at examples or the documentation to know how to use this either way.
I think the approach you had is nice in that people who know how to ask for the IDE to autocomplete a lambda with parameter names filled in would automatically see everything, but they could still get the gist by looking at a kdoc @sample or by looking at other callsites.
In all the places your sample calls this lambda, the context is not used which i think will be the majority case for most apps so things are quite short and elegant with the receiver syntax.

Sold, thank you for the contribution :+1:


Semantic-UI Menu always shows the same content - help please

I attempted to post this issue on the Semantic-UI github, but there was no obvious way to create a new issue. Considering that there are currently over 7000 issues (and again, no obvious way to search the issues) I decided to post here, as I am working with Meteor/Semantic-UI...
I am attempting to use the Sematic-UI Menu, and see no indication on how to change the content based on menu selection - or even the javascript that should make it all work (seems to be a recurring theme with Semantic-UI; scant documentation and incongrous examples).
Specifically, the example html code for the tabular menu (left side tabs/stretched grid column) shows how to create four tabs, all of which display the same content:

        Bio

        Pics

        Companies

        Links

      This is an stretched grid column. This segment will always match the tab height

How do I indicate unique content for each tab?
Is there any javascript associated with this example that makes the menu work that is, for whatever reason, buried somewhere else?
If anyone has sample code they can post, it would be greatly appreciated!

Anyone have insights into this issue? Code examples?

Is this supported at all? No examples?

afaik there is no javascript for the menu. You'll have to do the logic yourself. The "interactivity" on the semantic-ui page is just for illustration. You will have to set the classes of the items to change how they look.
If you want to use Blaze you might want to take a look at Meteor/Session+Blaze/Templates examples first. Once you understand how those work together, this and lots of other problems solve them self.
In Blaze you use an event to set a Session value which you use to set/add the active class. Then you might use a custom Template for the content.
something in the means of this..

  Links

UI.registerHelper('isActive', function(name){
  return Session.equals('activeMenu',name) ? 'active' : ''
})

Template.menutemplate.events({
  'click .menu-links':function(){
    Session.set('activeMenu','links')
  }
})

But let me add, there are >9000 ways of doing things in meteor and i don't want to put you on a path that might bite you in the foot later on in the project.

Thanks for the response.
I was not able to get you example code working; every attempt resulted in not being able to even select a menu item (make active), but it did help me advance in anther area, somewhat.
I can select the menu tabs via javascript now, and can change the content via session.get/set. The problem now is that the accordion stops working when switching tabs...
I'll start a new topic for that.

wdwf


State values sould not be in the Device map

The state values are currently in the device map. This should be changed (temporary fix)! States have their own API calls.

No longer relevant


Fix missing 'const' modifier for BorderRadius.circular factory

BorderRadius.circular factory is missing const modifier (unlike .all, .vertical, etc)

@daniilguit when you created this PR you were asked to fill out a form in the PR description. Can you please do that. Thanks!

I'm really sorry, could you please cancen this request? It's wrong :(


[enhancement request] Annotation for fluent setter

example:
Class Foo has:

@Setter(Style.FLUENT)
public String name;

Will creates a setter:
public Foo setName(String name){
     this.name = name;
     return this;
}

+1, Would be great to have this added.

check this https://github.com/rzwitserloot/lombok/blob/master/src/core/lombok/experimental/Accessors.java

@kamkie Awesome!  Did not see the experimental page.  After my OP, I also thought why even need the prefix.


Feature request: add a link to the explorer on transaction details view

#62 :

When a transaction is inspected in the mobile wallet, it should be one-click to pass through to the web explorer for that txid..


Choose the quality ?

Hi,
Very nice script.
Do you think it's possible to add parameter to choose the quality ?
Actualy the "toDataURL()" don't take parameter so the output is saved as .png file. And the uploaded file is bigger than the input file.
Do you think it's possible to add parameter to select the mime type and quality ? like :
toDataURL("image:jpeg", "0.7")
Thank you.

I'm unclear on what you're wanting to happen with the quality.  Croppie isn't changing the image's resolution.
Maybe you're referring to the result method's size argument.  You can pass in size: 'original' and it returns the image at it's native size, but cropped.

I use the script with the "canvas" option.
When I choose to upload an .jpg filen the saved cropped picture, got the right size, but it's no more an jpeg file but a png file.
In your script the function "toDataURL" (line 173 in your .js file) is used to return the content of the canvas area.
But if there is no parameter for this function, the data return is automaticly converted to "png" at 96dpi.
=> https://developer.mozilla.org/en-US/docs/Web/API/HTMLCanvasElement/toDataURL
In my case i choose an input file .jpg at 160kb, but the output file is cropped but with the conversion to .png I got a size of 833 kb :(

I see what you're saying now - that seems like a useful feature.  We'll see if we can get to it soon.

nice. thank you :) keep up the good work.

#75

This is in https://github.com/Foliotek/Croppie/releases/tag/v2.0.0

I'm unclear on what you're wanting to happen with the quality. Croppie isn't changing the image's resolution.
Maybe you're referring to the result method's size argument. You can pass in size: 'original' and it returns the image at it's native size, but cropped.

It is not taking this value :( I am trying to not resize image at all, but only to crop. Am I missing anything?


Checking out a new branch in git does not change the prompt

Hello,
I've installed zim and everything is running great with one exception: when I make changes to a git repo that should be reflected in the prompt (change branches, add/rm a file, etc.), it doesn't update until I either move out of the repo and back in or manually run git_prompt_info. I've attached every uncommented line of my .zimrc below. Thanks for taking a look!
zmodules=(directory environment git ssh history input utility custom spectrum pacman
      syntax-highlighting history-substring-search prompt completion)

zprompt_theme='steeef'

highlighting/blob/master/docs/highlighters.md
zhighlighters=(main brackets cursor)

zssh_ids=(id_rsa)

zpacman_frontend='yaourt'
zpacman_helper=(aur)

Actually, it looks like this bug only shows up when using the steeef theme. I'll poke around and see if I can figure out what the difference is.

The steef theme only changes the prompt upon making a call to git/svn.

Interesting. Checking out a different branch doesn't qualify?

It doesn't have any magic that runs in the background like some of the other themes do. It is more conservative. Typing anything starting with git will cause it to change, but using aliases will not. I can change this if it bothers you; it's not a big deal to change.

No, I mean if it's working as intended then no harm, no foul. I migrated from from prezto and noticed the difference and thought it might be a bug. I'll let it ride for a while and see what I think.
Great work by the way! I look forward to using zim.

No problem. Glad you like it!


Fix 'override' and 'override default' functionality

COUCHDB-2788

+1 after squash

PR is squashed.

@iilyak then merge? :)

Yes it is good to merge.


Add access modifiers for type, function and operation declarations

Resolves #259.
TODO:

[x] Name mangling for imported internal declarations (#370)
[x] Support for re-using internal names in more than one reference (#376)

Two minor comments, but other than that looks good! Well done, @marshallsa!


Scroll to last option is required

I have a usecase wherein I need to move to the last of the ref initially and then call several prev()s to move back in the list.
Somthing like
scrollRef.scroll.last(25);
Is this possible?

Sounds like a great addition. PRs welcome.

Thanks!
I tried it with the following code and failed miserably, will really appreciate your help here.  :
Scroll.prototype.last = function(lastNumRecords, totalRecords) {
  if( this.hasNext() ) {
    this.end = totalRecords;
    this.start = totalRecords - lastNumRecords;
    this.cache.moveTo(this.start, this.end - this.start);
  }
};

I wanted to determine totalRecords on the fly once this code started working. :(

Sorry, I assumed this was related to Paginate. That's the only context where this makes sense.
Infinite scroll, by definition, should be able to handle an infinite number of records, and thus it won't be able to go to the end of the list or count the number of records. The solution here would be to store an attribute on the records that puts them in descending order, and then use that as the sort field.

I have a timestamp field which is added to records as they get added. There is no way to sort records in descending order. Only best thing is to use setWithPriority. Is that right approach?

Change your timestamp field to a negative value, so they are ordered descending.

Yupe, found that solution. Thanks @katowulf

PS: I am using negative timestamp in the $priority field.

Any reason to not simply store it in a invertedTimestamp field? That way
you won't depend on a hidden property.
On Wed, Dec 16, 2015 at 8:31 AM vikasprogrammer<EMAIL_ADDRESS>wrote:

PS: I am using negative timestamp in the $priority field.
—
Reply to this email directly or view it on GitHub
https://github.com/firebase/firebase-util/issues/79#issuecomment-165165470
.

No reason, I am just exploring various options. I think your suggestion has a valid point.
PS: @puf This question for the app https://instantchat.io, you liked in the Firebase's Google group.

I use this function to set priority for decending order.
function priority(){     var now = new Date().getTime();     return -1 * now; }


Non-blocking submit for Task Scheduler

Coverage decreased (-0.4%) to 67.239% when pulling b50a01c6b7d044532f560dcc9d902deba6bba40c on yycptt:non-blocking-submit into a20e0b412825dfdfe36af172e2238127fe32ff40 on uber:master.


Add fetch improvements for app extensions.

Details at go/frc-appext-fetch-improvements
Please refer to the following commits for changes: https://github.com/firebase/firebase-ios-sdk/pull/3831/commits/8f7f9f0c8fe1e1250ed73f6da7cdc0d35de64224
https://github.com/firebase/firebase-ios-sdk/pull/3831/commits/98fb02137d23c2d7ed8c7964436ae4b015ea6cd7

Do we also handle and test the situation where the extension updates more recently than the app, or what should we do in that situation?

This should be handled. The main app and all app extensions (only for the default namespace), all overwrite the same lastETag and fetch time fields. Any RC instance (app or extension), if otherwise hitting the cache, will check to see if the cached config has a different ETag than the latest available in sharedUserDefaults. If different, and if the last fetch time is greater than the one for the cached config, the RC instance is allowed to fetch from Remote.
Note that all of the above logic only comes into existence if the developer has set the groupID in FIROptions.

Closing since this would need to be reimagined anyway.


Completion not being styled

We created a basic example (you can see it at  http://vigna.di.unimi.it/test.html )  . We are very confused, as after scanning for hours the documentation it appears that CSS are inlined and typeahead should work out of the box. However, we see a very ugly result:

Typeahead also perturbed significantly the CSS property of the FuelUX repeater search box, that we had to fix manually.
Is there any basic CSS file we should use? If so, please discuss it in the documentation.
Note that the example does not show that, for instance, the completion list is transparent. Here's a picture from the complete page using FuelUX:

The situation is actually worse—attaching typeahead to the Search box of a FuelUX repeater makes the repeater ignore the Search box at all. We wonder if you have any suggestion on how to proceed.

As far as I know typeahead only inlines the basic css to make it work.
I used the styles from this stackoverflow question and they work well:
http://stackoverflow.com/questions/20198247/twitters-typeahead-js-suggestions-are-not-styled-have-no-border-transparent-b


need use static_cast to be more compatible

node = malloc(sizeof(*node) + level * sizeof(struct sk_link));
the right hand returned is void ＊. many compliers may give you an error that void ＊ can not be assigned to a variable of type skipnode＊. so, please use this instead:
node = (struct skipnode ＊)malloc(sizeof(＊node) + level ＊ sizeof(struct sk_link));
likewise, you should
list = (struct skiplist ＊)malloc(sizeof(*list));

Which kind of compiler or under which version? Less code is better for readability thank to the support of the modern compiler such as C99 -- After all, I am lazy not providing the Makefile:)


Fixing tests 17 and 18

These changes allow tests 17 and 18 to execute correctly on Ubuntu 14.04 with Apache 2.4

looks good except that filter-ORIGINAL.perl should not be deleted.  i'll document that in the wiki.

Re-added the filter-ORIGINAL.perl and requested David document how it is to be used.


Fix fullscreen pseudo CSS class name

Change from :full-screen to :fullscreen.
See https://fullscreen.spec.whatwg.org/#:fullscreen-pseudo-class

Yep, good catch. Please merge.i


ConvertTo-JSONDate sets wrong minutes value

use $InputObject.Minute value

That makes perfect sense, thanks for the fixing the issue!


add scenario button

Adds a button to trigger an invalid okta attribute scenario.

Are we just deploying this to staging?

I tested this against production and it worked fine, I'm happy to just ship to staging but confident it will work in production.


'Mismatched version in @salesforce/plugin-generator plugin manifest' error with version 7.63.0

Summary
Whenever we run any 'sfdx' command we get the following error:
(node:222) Warning: Mismatched version in @salesforce/plugin-generator plugin manifest. Expected: 1.1.4 Received: 1.1.3
This usually means you have an oclif.manifest.json file that should be deleted in development. This file should be
automatically generated when publishing.
This does not seem to affect the operation of the commands.
We are using version 7.63.0 of the CLI due to open issue 470 (https://github.com/forcedotcom/cli/issues/470).
Steps To Reproduce:
Repository to reproduce: dreamhouse-lwc
NOTE: If your issue is not reproducable by dreamhouse-lwc, i.e. requires specific metadata or files, we require a link to a simple Salesforce project repository with a script to setup a scratch org that reproduces your problem.

Install sfdx CLI v7.63 using npm: # sudo npm install<EMAIL_ADDRESS>--global
Run sfdx any sfdx command, including with no arguments: # sfdx
Get the @salesforce/plugin-generator warning/error message

Expected result
sfdx command should complete without the @salesforce/plugin-generator error/warning message
Actual result
sfdx command gives the following error/warning message:
(node:222) Warning: Mismatched version in @salesforce/plugin-generator plugin manifest. Expected: 1.1.4 Received: 1.1.3
This usually means you have an oclif.manifest.json file that should be deleted in development. This file should be
automatically generated when publishing.
Additional information
This only seems to affect new installs of the CLI.  For example I've had it installed on my laptop for a few months and I don't get the error.
My (error-free) version gives:
CLI Version: sfdx-cli/7.63.0 darwin-x64 node-v14.15.1
Plugin versions:
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.2.3 (core)
@oclif/plugin-help 3.0.1 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.7.10 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.0.7 (core)
analytics 1.9.1 (core)
generator 1.1.3 (core)
salesforcedx 48.19.0 (core)
├─ salesforcedx-templates 48.18.0 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.5 (core)
├─ salesforce-alm 48.20.0 (core)
└─ custom-metadata 1.0.10 (core)
sfdx-cli 7.63.0 (core)
Feel free to attach a screenshot.
SFDX CLI Version(to find the version of the CLI engine run sfdx --version):
7.63.0
SFDX plugin Version(to find the version of the CLI plugin run sfdx plugins --core)
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.2.3 (core)
@oclif/plugin-help 3.0.1 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.7.10 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.0.7 (core)
analytics 1.9.1 (core)
generator 1.1.4 (core)
salesforcedx 48.19.0 (core)
├─ salesforcedx-templates 48.18.0 (core)
├─ @salesforce/sfdx-plugin-lwc-test 0.1.5 (core)
├─ custom-metadata 1.0.11 (core)
└─ salesforce-alm 48.20.0 (core)
sfdx-cli 7.63.0 (core)
OS and version:
MacOs 10.15.7 (19H114)
Ubuntu 18.04.3 LTS (Bionic Beaver)

I am experiencing the same issue with both the latest and latest-rc versions of the cli installed via npm globally. I only started seeing the warning after upgrading to the latest cli version today.

I am experiencing the same issue with both the latest and latest-rc versions of the cli installed via npm globally. I only started seeing the warning after upgrading to the latest cli version today.

This will only happen with npm. There was a new version of the plugin-generator that was published while testing the build. That warning should have no impact on actual CLI usage though. I'll reset latest to 1.1.3.

This will only happen with npm. There was a new version of the plugin-generator that was published while testing the build. That warning should have no impact on actual CLI usage though. I'll reset latest to 1.1.3.


Installation instructions for windows is wrong

From the article, this is the installation instructions for winows:
curl -fsSL https://raw.githubusercontent.com/databricks/setup-cli/main/install.sh | sh
Fails in cmd.exe with this error message:
'sh' is not recognized as an internal or external command,
operable program or batch file.

Fails in pwsh with this error message:
sh: The term 'sh' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

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

ID: 7a2adc38-e976-8819-1c8c-5a4e385d287b
Version Independent ID: 7a2adc38-e976-8819-1c8c-5a4e385d287b
Content: Databricks CLI tutorial - Azure Databricks
Content Source: databricks/dev-tools/cli/tutorial.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@johanrex
Thanks for your feedback! We will investigate and update as appropriate.

@kateglee-db
Could you please review add comments on this, update as appropriate.

@johanrex
Thank you for bringing this to our attention.
I've delegated this to content author @mssaperla, who will review it and offer their insightful opinions.

Thanks for providing feedback that helps improve our documentation. We've created an internal work item (DOC-12182) to address your feedback. The timeline for resolution varies based on resourcing.

#please-close


Remove outdated templates

Those files are outdated and haven't been used in a long time, let's simply remove them

I believe we no longer mention them anywhere, do we?

No we don't and those pages have changed significantly. If we ever add a new language my suggestion is to copy from another language and work from there.


remove dependency to puppet/staging

This module has a dependency to https://forge.puppet.com/puppet/staging
but this module is deprecated.
We should move to https://forge.puppet.com/puppet/archive instead.

We've just merge a PR that made the tests all green again. Would you be able to come up with a patch?


[System] Fix binary path location when dlls run from an unexpected executable

PR Details
A user had an issue running tests from Rider, the folder returned from that function pointed next to the test runner executable instead of the dlls. Pinging @tebjan since this is his area.
Related Issue
None logged
Types of changes

[ ] Docs change / refactoring / dependency upgrade
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

[ ] My change requires a change to the documentation.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

This change assumes that the exe and the binaries are in the same folder, the code you deleted made it possible to provide a clean output directory.
/MessyBinaryFolder
Entry.exe

We use that in vvvv to have everything in a different folder. Stride.Core.dll is one level up from the exe, and also the asset database and so on...

This change assumes that the exe and the binaries are in the same folder

I think it's the exact opposite, the previous version assumes the binaries are next to or one level deeper than the executable, my change doesn't assume anything, it will return the directory wherever those binaries may be ?
Unless we're talking about android here, in which case, nothing changed, it already returned the directory where the executable was.

You are right, it takes the folder of Stride.Core.dll because that type is in that dll, didn't grasp that on first look. Looks good to me.


Quasiquote template stats

How I would write without quasiquotes
case t: internal.ast.Template if t.stats.isDefined =>
  ???

How the docs say I can write with quasiquote:
case template"{ ..$stats } with ..$ctorcalls { $param => ..$stats }" =>
  ???

Why are there two stats, which one should I use?

The first one is early initializers. The second one is regular statements in the body of the template. You should use both.


Swipe inside another swipeable component

Hello,
In my case I used this inside a material top tab navigator of react navigation v5.
Which is also a swipeable component.  And when i swipe in the carousel it swipes in the top tab navigator's screens not in the carousel images.
Is there any way to prevent this somehow?

@Bayramito Hey, have you solved this problem?