Add various exports.

Adds various missing exports.

Sorry, I realized there was a commit that I had meant to push this morning, and it did some of the stuff you have in your PR, but also moved some exports around.  Just pushed it now so that's the cause of the conflict here.

Cool then I close this one, wasn't to much work. Have you also exposed the: distribution, distribution builder and the sanitize functions? I have not seen those yet. Would like to be able to use those in my project. An other question, when are you planning to release those changes?

It doesn't expose anything related to the Prometheus exporter, so feel free to reopen this: I have a few thoughts on how I'd want the exports structured.
I'm happy to cut a new release of metrics-util whenever but if you also want some new exports in metrics-exporter-prometheus, then I'd rather get this/whatever PR merged in first so I can do the releases all at once.

Just updated the PR.
Would be really nice if there is a new release within this week. As im working on some project and hope to open a PR for it this week. Otherwise I will have to copy logic which feels a bit bad.

Looks like this needs cargo fmt run on it, and the test failures need to be addressed.

Pushed to fix some of the compile errors. Locally it works now, CI is waiting for your approval.

For now, I did not expose:
invalid_label_key_character,
invalid_label_key_start_character,
invalid_metric_name_character,
invalid_metric_name_start_character,
sanitize_label_value_or_descpiption

Since they did not seem very relevant and were mostly used by the relevant functions:
sanitize_description
sanitize_label_value
sanitize_label_key
sanitize_metric_name
write_metric_line
write_type_line
write_help_line
key_to_parts

This is released in<EMAIL_ADDRESS>Thanks again for your contribution!

Awesome @tobz !


fix: replace / in nested gitlab repos with - to fix slack issues

Signed-off-by: ankitm123<EMAIL_ADDRESS>

/cc @msvticket @tomhobson @babadofar

Related to https://github.com/jenkins-x/jx/issues/8303
Tested and verified by @svilenvul

/lgtm


fixes #385

Changes
Correctly pass the version information.
Actually such important utility functions needed to be tested.
Related Issues
Closes # (add issue numbers)
Checks

[ ] updated CHANGELOG.md
[ ] updated tests
[ ] updated doc/
[ ] update example/tutorial notebooks

I suppose we do not need a changelog entry for a implementation detail, which has net been released either (luckily).

good catch, did this cause any bugs in code we currently have? (wondering since version handling so far is pretty rudimentary)

Nah it didn't cause any trouble (presumably because we do not have anything beyond version 1.0.0), I just stumble upon it.


Reduce Possible Side Effects in Style API

Not feasable due to the inherently mutable nature of Swing components :/
(The component is exposed to the style API lambdas to allow for customizable component styling)


change minimill description

should read "Design agency for brand, web, and mobile."

Bump

FWIW, our description is now "A design agency for branding and web."

Got it, I will update to "A design agency that no longer exists."

Done


Add colorcet to conda recipe

colorcet is not in conda-forge. Need to add it in installation:
conda install acme_diags -c acme -c conda-forge -c uvcdat -c bokeh

Done in 34a6843, need to remember to add this to the install instructions.


added check in index.js to check for /opt/openshfit /usr/bin/oc

added check in index.js to check for /opt/openshfit /usr/bin/oc

fix for https://github.com/austincunningham/change_oc/issues/18


VSCode get a net::ERR_PROXY_CONNECTION_FAILED

Kindly suggest.

Could you install the Network Proxy Test extension (https://marketplace.visualstudio.com/items?itemName=chrmarti.network-proxy-test) and check the output of F1 > Network Proxy Test: Test Connection?

not showing the "Network Proxy'' . Kindly assist me through the snapshot.
On Wed, Apr 5, 2023 at 12:22 PM Christof Marti @.***>
wrote:

Could you install the Network Proxy Test extension (
https://marketplace.visualstudio.com/items?itemName=chrmarti.network-proxy-test)
and check the output of F1 > Network Proxy Test: Test Connection?
—
Reply to this email directly, view it on GitHub
https://github.com/microsoft/vscode/issues/179227#issuecomment-1497005191,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZ6SZVM3FS56IBMXUYUUVR3W7UJEPANCNFSM6AAAAAAWTSB7B4
.
You are receiving this because you authored the thread.Message ID:
@.***>

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


[APM] Use map lookups instead of string slice

What does this PR do?
Replace the string slice with known span kinds with a map, in order to have more efficient looksup.
Motivation
Describe how to test/QA your changes
N/A
Possible Drawbacks / Trade-offs
Additional Notes

/merge


[WIP] perf: common neural network workloads benchmarks

currently add CPU versions. should be easy to extend to GPU once SciMLBenchmarks has GPU runners available.
TODOs

[ ] Restore Manifest to use the released versions of packages
[ ] Boilerplate

[x] Inference
[x] Inference Plots
[ ] Training
[ ] Training Plots

[ ] Models

[ ] Simple MLP

[x] Inference
[ ] Training

[ ] Simple MLP with BN -- wait on https://github.com/LuxDL/LuxLib.jl/pull/126

[ ] Inference
[ ] Training

[ ] LeNet

[x] Inference
[ ] Training

[ ] ResNet

[ ] Inference
[ ] Training

[ ] Add Reactant Inference Code

Training code will have to wait till the compile PR lands in Lux

@thazhemadam @staticfloat what's the easiest way to set this up so that benchmarks can choose a separate runner for GPUs?

Allowing different runners based on the jmd metadata. Something like
---
title: Simple Neural Networks
author: Avik Pal
backend: CUDA <--- If nothing present then use CPU. In future we can allow AMDGPU/Metal/etc with the same syntax
---

Lux now matches SimpleChains in inference timings :sweat_smile:. The ones where we fall behind are because Octavian is somewhat slow on EPYC machines so it is turned off


compute-vm module does not support 'disk_encryption_key' property for compute instance templates

Add disk_encryption_key field to google_compute_instance_template resource in compute-vm module
(Supported when compute instance is made individually but not the instance template)

Ref: https://registry.terraform.io/providers/hashicorp/google/latest/docs/resources/compute_instance_template#disk_encryption_key

PR #830


Fixed Maven build

Maven build was broken when using mvn compile goal, but not for the rest of the goals.
Maven dependencies are now fixed and Maven lifecycle was checked.

Current coverage is 18.18% (diff: 100%)

No coverage report found for devel at 3faada0.

Powered by Codecov. Last update 3faada0...c046a62


DCATFederalProfile vs DCATAPprofil

Looks like the DCATFederalProfile.md is an older copy of DCATAPprofil.fr.md.
So the DCATFederalProfile should probably be deleted, and/or a language selection page should be created instead (similar to README.md and README.fr.md / README.nl.md)

DCATFederalProfile is indeed an older copy of DCATAPprofil.fr.md. The file is now deleted.


Type aliases requires go1.9 or later

I've run mingo against my program (initially set to go 1.22) which has a few type aliases, eg:
type Timestamp = uint64

mingo suggests go1.0:
$ mingo
0
$ mingo -check
Error scanning directory: go.mod declares version 1.22 but computed minimum is 1.0 [0]

But after changing the go.mod to go 1.0, the program becomes invalid:
$ mingo -check
Error scanning directory: loading package(s): loading package github.com/XXX: -: # github.com/XXX
XXX:20:6: type aliases requires go1.9 or later (-lang was set to go1; check go.mod)
loading package github.com/XXX: XXX:20:16: type aliases requires go1.9 or later
loading package github.com/XXX: XXX:33:13: type aliases requires go1.9 or later
loading package github.com/XXX: XXX:3:13: type aliases requires go1.9 or later

Thank you for this report! I can't reproduce this behavior using the latest version of mingo, which is v0.10.0. Is that the version you're using? (Run go version -m /path/to/mingo to find out, and look for the mod github.com/bobg/mingo line.) If it isn't, please go install github.com/bobg/mingo/cmd/mingo@latest and try again.
If this does reproduce for you with the latest mingo, can you supply some input here that demonstrates the bug? (My test case was a simple .go file containing exactly the type alias you mentioned.)


Improve resiliency of iframe CSS loading

Test Puck's iframe behaviour across multiple CSS frameworks and improve resiliency:

Tailwind
Mantine
...

Related: #409

@xaviemirmon

I've been investigating this issue using the Mantine library and have found two problems that prevent it from rendering all of the styles correctly.

The AutoFrame component only mirrors the styles from the document head. Mantine is also injecting styles into the body, and these styles aren't getting mirrored.
Mantine is also relying on data attributes in the html tag for theme/color mode selection, but this isn't getting copied across.

PR #544 is ready for review.

Mantine now working. @xaviemirmon to review further Tailwind setups before closing.

Hello @chrisvxd,
we really appreciate your work and love the puck editor. As we would like to work with serverless infrastructure we started a new project with the remix recipe and added Chakra UI and eventually realized that stylings from the Iframe are not generated and rendered in the editor route. The published site will be rendered as expected.
We tried to enforce client rendering and some other hacks, but did not manage to solve it from the outside. We think this issue is connected with the iframe.
I created a minimal sample for this: https://github.com/henning-f/puck-remix-chakra-issue
I followed the instructions of the Chakra UI documentation for Remix.
Are these issues connected?
I am looking forward to your response.

Hello.
In our project we are using styled-components library for React to style our components. With iframe enabled , those styles are not being picked up by editor. However inline stylings works as expected. Sharing some code example so maybe You can try to reproduce that issue.
Editor Config :
import BlockQuote from './BlockQuote
const config = {
  components: {
    Quote:{
      fields: {
        quote: {
          type: 'text',
        },
      },
      defaultProps: {
        quote: 'Hello, quote',
      },
      render: ({ quote }) => {
        return
;
      },
    }
  },
};

Component Code
import styled from 'styled-components';

export default function BlockQuote(props) {
  const { quote } = props;
  return (
    <QuoteWrapper>
      <LineDiv />

        {quote}

    </QuoteWrapper>
  );
}

const LineDiv = styled.div`
  width: 0.25rem;
  background-color: ${({ theme }) => theme.colors.blue[60]};
  align-self: stretch;
  margin-right: 1rem;
`;

const QuoteWrapper = styled.div`
  padding-bottom: 3rem;
  padding-top: 2rem;
  display: flex;
  align-items: center;

  .quote-text {
    font-size: 1.75rem;
    line-height: 2.25rem;
    color: ${({ theme }) => theme.colors.blue[60]};
  }
`;

Hey @chrisvxd,
Just wanted to confirm that disabling iframes (iframe={{enabled:false}}) fixed the issue with the remix recipe, too.
I thought it wouldn't work, but I guess I had a configuration error last time.

@MiniMarPaz which version of Puck are you using? Have you tried the canary which has some iFrame enhancements?

@xaviemirmon I'm using latest available version of Puck. 0.15.0 . I did not tried canary version but I will try and let You know if canary version fix issue

@henning-f I have been looking at your issue and have narrowed it down to how Emotion Cache is interacting with the iFrame.  My current theory is that Emotion Cache isn't able to interact with the style tags in the iFrame.

@MiniMarPaz amazing thanks!

@MiniMarPaz I tried replicating your issue in the demo app using your code, and was unable to

Can you provide a codesandbox that replicates the issue?

Okay, I was able to reproduce the Chakra/Remix issue and have released some new APIs and tools to help in (available in 0.16.0-canary.607a585).
Here's an example chakra + remix example using the new APIs: https://github.com/chrisvxd/puck-chakra-remix-example/commit/baf0863fe0fa4ea1a20c4011320c37a8d489ca32
New APIs
iframe override API
Receives the iframe document as a prop. This enables you to inject your styles and manipulate the iframe document however you need. This example injects a custom emotion cache with the cha key for Chakra:
    <Puck overrides={{
      iframe: ({ children, document }) => {
        const [cache, setCache] = useState<EmotionCache | null>(null);

        // eslint-disable-next-line react-hooks/rules-of-hooks
        useEffect(() => {
          if (document) {
            setCache(
              createCache({
                key: "cha",
                container: document.head,
              })
            );
          }
        }, [document, key]);

        if (cache) {
          return <CacheProvider value={cache}>{children}</CacheProvider>;
        }

        return <>{children}</>;
      },
    }} />

emotion-cache plugin
This captures the above as a plugin, since it's likely a common use-case. We could consider adding one for style-components, if necessary.
import { Puck } from "@measured/puck";
import createEmotionCache from "@measured/puck-plugin-emotion-cache";

// Create your emotion cache plugin. This example configures it for Chakra.
const chakraEmotionCache = createEmotionCache("cha");

// Render Puck
export function Page() {
  return <Puck config={config} data={data} plugins={[chakraEmotionCache]} />;
}

I'm going to close this out as I'm pretty sure this will cover any remaining use-cases, but shout if there are still issues and I'll


Fix name conversion

Thanks for adding the RELEASE.md file!

Here's a preview of the changelog:

This release fix the return value of enums when using a custom
name converter for them.

Here's the preview release card for twitter:

Here's the tweet text:
🆕 Release (next) is out! Thanks to @patrick91 for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)


crowdsec-firewall-bouncer-iptables upgrade problem

What happened?
I manage 8 machines with crowdsec running, and on 5 out of 8 I got this problem:
sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
crowdsec-firewall-bouncer-iptables
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 3,656 kB of archives.
After this operation, 143 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://packagecloud.io/crowdsec/crowdsec/debian bullseye/main amd64 crowdsec-firewall-bouncer-iptables amd64 0.0.26 [3,656 kB]
Fetched 3,656 kB in 1s (4,881 kB/s)
(Reading database ... 97834 files and directories currently installed.)
Preparing to unpack .../crowdsec-firewall-bouncer-iptables_0.0.26_amd64.deb ...
Removed /etc/systemd/system/multi-user.target.wants/crowdsec-firewall-bouncer.service.
Unpacking crowdsec-firewall-bouncer-iptables (0.0.26) over (0.0.25) ...
Setting up crowdsec-firewall-bouncer-iptables (0.0.26) ...
Configuration file '/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml'
==> Modified (by you or by a script) since installation.
==> Package distributor has shipped an updated version.
What would you like to do about it ?  Your options are:
Y or I  : install the package maintainer's version
N or O  : keep your currently-installed version
D     : show the differences between the versions
Z     : start a shell to examine the situation
The default action is to keep your current version.
*** crowdsec-firewall-bouncer.yaml (Y/I/N/O/D/Z) [default=N] ? Y
Installing new version of config file /etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml ...
Installing new version of config file /etc/systemd/system/crowdsec-firewall-bouncer.service ...
cscli/crowdsec is present, generating API key
API Key successfully created
Created symlink /etc/systemd/system/multi-user.target.wants/crowdsec-firewall-bouncer.service → /etc/systemd/system/crowdsec-firewall-bouncer.service.
Job for crowdsec-firewall-bouncer.service failed because the control process exited with error code.
See "systemctl status crowdsec-firewall-bouncer.service" and "journalctl -xe" for details.
dpkg: error processing package crowdsec-firewall-bouncer-iptables (--configure):
installed crowdsec-firewall-bouncer-iptables package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
crowdsec-firewall-bouncer-iptables
E: Sub-process /usr/bin/dpkg returned an error code (1)
What did you expect to happen?
full upgrade
How can we reproduce it (as minimally and precisely as possible)?
it was a simple apt upgrade
Anything else we need to know?
No response
Crowdsec version

```console
$cscli version
2023/05/08 17:33:42 version: v1.4.6-debian-pragmatic-5f71037b40c498045e1b59923504469e2b8d0140
2023/05/08 17:33:42 Codename: alphaga
2023/05/08 17:33:42 BuildDate: 2023-02-09_14:34:10
2023/05/08 17:33:42 GoVersion: 1.19.2
2023/05/08 17:33:42 Platform: linux
2023/05/08 17:33:42 Constraint_parser: >= 1.0, <= 2.0
2023/05/08 17:33:42 Constraint_scenario: >= 1.0, < 3.0
2023/05/08 17:33:42 Constraint_api: v1
2023/05/08 17:33:42 Constraint_acquis: >= 1.0, < 2.0
```

OS version

$cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

$ uname -a
Linux srv11222 5.15.102-1-pve crowdsecurity/crowdsec#1 SMP PVE 5.15.102-1 (2023-03-14T13:48Z) x86_64 GNU/Linux

Enabled collections and parsers

$ cscli hub list -o raw
# paste output here

Acquisition config

```console
# On Linux:
$ cat /etc/crowdsec/acquis.yaml /etc/crowdsec/acquis.d/*
# paste output here
On Windows:
C:> Get-Content C:\ProgramData\CrowdSec\config\acquis.yaml
paste output here

Config show

$ cscli config show
Global:
   - Configuration Folder   : /etc/crowdsec
   - Data Folder            : /var/lib/crowdsec/data
   - Hub Folder             : /etc/crowdsec/hub
   - Simulation File        : /etc/crowdsec/simulation.yaml
   - Log Folder             : /var/log/
   - Log level              : info
   - Log Media              : file
Crowdsec:
  - Acquisition File        : /etc/crowdsec/acquis.yaml
  - Parsers routines        : 1
  - Acquisition Folder      : /etc/crowdsec/acquis.d
cscli:
  - Output                  : human
  - Hub Branch              :
  - Hub Folder              : /etc/crowdsec/hub
Local API Server:
  - Listen URL              : <IP_ADDRESS>:8080
  - Profile File            : /etc/crowdsec/profiles.yaml
  - Trusted IPs:
      - <IP_ADDRESS>
      - ::1
  - Database:
      - Type                : sqlite
      - Path                : /var/lib/crowdsec/data/crowdsec.db
      - Flush age           : 7d
      - Flush size          : 5000

Prometheus metrics

$ cscli metrics
FATA[08-05-2023 17:36:22] failed to fetch prometheus metrics : executing GET request for URL "http://<IP_ADDRESS>:6060/metrics" failed: Get "http://<IP_ADDRESS>:6060/metrics": dial tcp <IP_ADDRESS>:6060: connect: connection refused

Related custom configs versions (if applicable) : notification plugins, custom scenarios, parsers etc.

Hi @merkleID, thanks for the report
Could you run these and see what it says?
See "systemctl status crowdsec-firewall-bouncer.service" and "journalctl -xe" for details.

Hi, same issue here.
On my side the issue was that I have disabled LAPI.
The upgrade process want at all cost to generate an API Key on LAPI...
Once I have reactivate the LAPI on crowdsec I was able to finish the upgrade for the bouncer...
But I need to activate LAPI, upgrade the bouncer, deactivate again the LAPI...
Here are some logs of the upgrade process :
Setting up crowdsec-firewall-bouncer-iptables (0.0.26) ...
cscli/crowdsec is present, generating API key
INFO[09-05-2023 10:01:48] Patching yaml: '/etc/crowdsec/config.yaml' with '/etc/crowdsec/config.yaml.local'
FATA[09-05-2023 10:01:48] Local API is disabled, please run this command on the local API machine
failed to create API key
ERR: missing required variable value
dpkg: error processing package crowdsec-firewall-bouncer-iptables (--configure):
 installed crowdsec-firewall-bouncer-iptables package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 crowdsec-firewall-bouncer-iptables
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)

Note : the bouncer work fine if I do a systemctl restart crowdsec-firewall-bouncer...
But the upgrade process want to register on LAPI, even if I have the API key and API url configured in the bouncer config file (or in the .local file)...

Thanks @LtSich for the detailed explanation.
We are preparing a new release to deal with these cases, the .yaml.id file is used later when the package is uninstalled, it would unregister the bouncer if the configuration is removed too (i.e. apt purge) otherwise it's harmless. I can ping you to test a pre-release if you want.
By the way you said that when upgrading the package, if you already have an API_KEY it would generate a new one. I guess you accepted the new configuration file which reverts the generated key to ${API_KEY}. In this case the bouncer is registered a second time but it should work correctly.

The configuration file don't have any API key, but I have a .local file with everything needed.
I have try to manually add the api key and api url directly in the config file, but same result, the upgrade process want to register a local bouncer.
Note : I don't want that the upgrade process register a new bouncer... I have close to 50 bouncers registered on a "central" LAPI... Each one with a "real" name, I don't want to manage random name in my bouncers list :)

Of course we must take .yaml.local into account: if BACKEND or API_KEY are there, we won't touch the config.
Another thing: you said an issue was that LAPI was not running, but LAPI is not used to create an api key, because cscli writes it directly in the database.

As I say, the -no-api in the systemd file is not a problem.
But commenting (#) the server part in config.yaml break the upgrade process.

@merkleID: Thanks for opening an issue, it is currently awaiting triage.
In the meantime, you can:

Check Crowdsec Documentation to see if your issue can be self resolved.
You can also join our Discord.
Check Releases to make sure your agent is on the latest version.

Details

Hi,
here's the log
root@srv21934:/home/luca# journalctl -xe -u crowdsec-firewall-bouncer.service
May 10 15:19:50 srv21934 systemd[1]: crowdsec-firewall-bouncer.service: Scheduled restart job, restart counter is at 13340.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit crowdsec-firewall-bouncer.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
May 10 15:19:50 srv21934 systemd[1]: Stopped The firewall bouncer for CrowdSec.
░░ Subject: A stop job for unit crowdsec-firewall-bouncer.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit crowdsec-firewall-bouncer.service has finished.
░░
░░ The job identifier is 1699431 and the job result is done.
May 10 15:19:50 srv21934 systemd[1]: Starting The firewall bouncer for CrowdSec...
░░ Subject: A start job for unit crowdsec-firewall-bouncer.service has begun execution
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit crowdsec-firewall-bouncer.service has begun execution.
░░
░░ The job identifier is 1699431.
May 10 15:19:50 srv21934 crowdsec-firewall-bouncer[883631]: time="2023-05-10T15:19:50+02:00" level=info msg="crowdsec-firewall-bouncer v0.0.26-debian-pragmatic-fa0e7d25b886aea927c1c3323ba854b5751fc3d1"
May 10 15:19:50 srv21934 crowdsec-firewall-bouncer[883637]: time="2023-05-10T15:19:50+02:00" level=info msg="crowdsec-firewall-bouncer v0.0.26-debian-pragmatic-fa0e7d25b886aea927c1c3323ba854b5751fc3d1"
May 10 15:19:52 srv21934 crowdsec-firewall-bouncer[883637]: time="10-05-2023 15:19:52" level=fatal msg="process terminated with error: stream api init failed"
May 10 15:19:52 srv21934 systemd[1]: crowdsec-firewall-bouncer.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit crowdsec-firewall-bouncer.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
May 10 15:19:52 srv21934 systemd[1]: crowdsec-firewall-bouncer.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit crowdsec-firewall-bouncer.service has entered the 'failed' state with result 'exit-code'.
May 10 15:19:52 srv21934 systemd[1]: Failed to start The firewall bouncer for CrowdSec.
░░ Subject: A start job for unit crowdsec-firewall-bouncer.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit crowdsec-firewall-bouncer.service has finished with a failure.
░░
░░ The job identifier is 1699431 and the job result is failed.

Thanks. In the linked PR the install script will avoid touching the config file if api_key is defined in .yaml.local. That should be ok for this case

0.0.27-rc1 is out, should fix that
https://packagecloud.io/crowdsec/crowdsec-testing

Just updated Crowdsec, got this:
Setting up crowdsec-firewall-bouncer-iptables (0.0.28) ...

Configuration file '/etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** crowdsec-firewall-bouncer.yaml (Y/I/N/O/D/Z) [default=N] ? d
--- /etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml       2023-06-05 14:23:03.504134248 +0000
+++ /etc/crowdsec/bouncers/crowdsec-firewall-bouncer.yaml.dpkg-new      2023-10-02 11:36:23.000000000 +0000
@@ -1,7 +1,5 @@
 mode: iptables
-pid_dir: /var/run/
 update_frequency: 10s
-daemonize: true
 log_mode: file
 log_dir: /var/log/
 log_level: info
@@ -10,7 +8,7 @@
 log_max_backups: 3
 log_max_age: 30
 api_url: http://<IP_ADDRESS>:8080/
-api_key: <my_current_api_key_here>
+api_key: ${API_KEY}
 insecure_skip_verify: false
 disable_ipv6: false
 deny_action: DROP
@@ -55,6 +53,6 @@
   anchor_name: ""

 prometheus:
-  enabled: true
+  enabled: false
   listen_addr: <IP_ADDRESS>
   listen_port: 60601

Is this intended behavior? Can I safely let the system overwrite my current config file or should I keep it?

You can keep the old file, or replace it -- it will just create a new api_key when the service is run.
We had to disable metrics by default because on some systems they have a performance impact.
Note: we should find a clean way to move api_key to its own file.


BUG: array.asarray does not respect dtype arg

Describe the issue:
dask.array.asarray does not respect the dtype argument.
Minimal Complete Verifiable Example:
>>> import numpy as np
>>> import dask.array as da
>>> Zm = da.asarray([[1, 2, 3]])
>>> Zm
dask.array<array, shape=(1, 3), dtype=int64, chunksize=(1, 3), chunktype=numpy.ndarray>
>>> Z = da.asarray(Zm, dtype=da.float64)
>>> Z
dask.array<array, shape=(1, 3), dtype=int64, chunksize=(1, 3), chunktype=numpy.ndarray>
>>> Z.compute().dtype
dtype('int64')
# same issue is present with `np` dtypes directly
>>> Z = da.asarray(Zm, dtype=np.float64)
>>> Z
dask.array<array, shape=(1, 3), dtype=int64, chunksize=(1, 3), chunktype=numpy.ndarray>
>>> Z.compute().dtype
dtype('int64')

Anything else we need to know?:
Environment:

Dask version: 2024.8.0+3.g65270980
Python version: 3.12.4
Operating System: Ubuntu
Install method (conda, pip, source): python -m pip install git+https://github.com/dask/dask.git

It looks like the logic does in incorrect early return:
https://github.com/dask/dask/blob/ed5f68897b3a097f7c5ec1a9ec13ce49c112a544/dask/array/core.py#L4577-L4579
It should only be returning the same object if like is None and dtype is None and order is None.


Rolling 4 dependencies

Roll third_party/shaderc/ dd6b19ec3..0d10afabc (1 commit)
https://github.com/google/shaderc/compare/dd6b19ec37f3...0d10afabcf7a
$ git log dd6b19ec3..0d10afabc --date=short --no-merges --format='%ad %ae %s'
2019-11-18 9856269+sarahM0 Add spvc parser support for control flow instructions (#894)
Roll third_party/spirv-tools/ c3f22f7cb..0391d0823 (3 commits)
https://github.com/KhronosGroup/SPIRV-Tools/compare/c3f22f7cba60...0391d0823ebf
$ git log c3f22f7cb..0391d0823 --date=short --no-merges --format='%ad %ae %s'
2019-11-19 stevenperron Handle OpPhi with no in operands in value numbering (#3056)
2019-11-19 stevenperron Kill the id-to-func map after wrap-opkill (#3055)
2019-11-18 rharrison Convert stderr and stdout in status to strings on assignment (#3049)
Roll third_party/vulkan-loader/ d24b204e0..c3a266436 (1 commit)
https://github.com/KhronosGroup/Vulkan-Loader/compare/d24b204e0f31...c3a2664367d2
$ git log d24b204e0..c3a266436 --date=short --no-merges --format='%ad %ae %s'
2019-11-18 shannon build: Update known-good for 1.1.128 header
Roll third_party/vulkan-validationlayers/ e2441190b..c2bd11586 (2 commits)
https://github.com/KhronosGroup/Vulkan-ValidationLayers/compare/e2441190bb0c...c2bd11586919
$ git log e2441190b..c2bd11586 --date=short --no-merges --format='%ad %ae %s'
2019-11-13 petr_kraus tests: Test swapchain acquire for sync param
2019-11-13 petr_kraus layers: Migrate swapchain acquire check to stateless
Created with:
roll-dep third_party/effcee third_party/glm third_party/glslang third_party/googletest third_party/re2 third_party/shaderc third_party/spirv-cross third_party/spirv-headers third_party/spirv-tools third_party/tinyxml2 third_party/vulkan-docs third_party/vulkan-guide third_party/vulkan-headers third_party/vulkan-hpp third_party/vulkan-loader third_party/vulkan-validationlayers

Known shaderc nose test failure.


[Feature Request] Monsters attack Masked

Title. Has always irked me that giants will have tea parties with Mimic's but be line it for real players.

Great idea for sure will add in another update


Feature - add robots "noindex, nofollow" meta tag on legacy docs

The logic here pulls the project name (influxdb, influxdb_enterprise, chronograf, etc.) out of the url and checks it agains the project's semver defined data/default_versions.toml. If the projects semver doesn't exist in the page's URL, the robots tag is set to noindex, nofollow. If it does exist in the URL or the current page is the home page, it sets it to index, follow.
This should help to prevent users being led to old docs from Google search results.

when this is checked in, someone should log into our google search console and request a recrawl of the docs.

This will tell Google to index only the latest versions of our products. The Docsearch will still index all pages for all versions, so customers on earlier versions can use the docsite's search to find earlier docs if needed.


Two new options: security fixes

Description
Two new options: security fixes
Fixes #196
Type of change

Configuration update

Testing steps
N/A
Checklist

[ ] make before_commit passes
[ ] updated documentation wherever necessary
[ ] added or modified tests if necessary
[ ] updated schemas and validators in insights-data-schemas in case of input/output change

Codecov Report
Base: 25.64% // Head: 25.64% // No change to project coverage :thumbsup:

Coverage data is based on head (3dfcedc) compared to base (c107029).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #198   +/-   ##
=======================================
  Coverage   25.64%   25.64%
=======================================
  Files           3        3
  Lines         468      468
=======================================
  Hits          120      120
  Misses        339      339
  Partials        9        9

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Switch channels via Siri

Hello, will it be possible to switch channels via Siri in a future version? I already have such a plug-in for my Sony TV and it is then implemented using scenes. Greetings Michel

Can you please let us know the plugin name so we can see their source code as a reference implementation

@neilpatel121 Thank you for your prompt reply!
With pleasure, Homebridge Bravia Tvos - https://github.com/SeydX/homebridge-bravia-tvos#readme
greetings michel
P.S: skyq-tvremote - great job !!!

Thanks, what Siri command do you use to change the channel, can you type the command pls

@neilpatel121 I've set up a scene for each channel.
And then I say over my homepod, Hey Siri activate RTL as an example. Everyone can determine that themselves when setting up the scene :-)

@neilpatel121 In my case, of course, in German. But the Sony plug-in works in all languages, as I understand it.

Ok I think I understand how you got it work, there is an alternative way you can do this, which I use all ready, I expose channels as switches in the home app, then you can use Siri to control the switch,

Take a look at this https://github.com/AdamSwinden/homebridge-sky-q#readme

This is what I use to use Siri to change sky channels

I've added the feature to switch channels.
Could you test v1.2.0-beta.1 please?

@EpicKris Very happy but how do I find the beta and how do I install it?

@EpicKris Very happy but how do I find the beta and how do I install it?

Are you using Hombridge Config UI X?

@EpicKris Very happy but how do I find the beta and how do I install it?

Are you using Hombridge Config UI X?

yes,  v4.41.0

yes, v4.41.0

Go to the Plugins tab, select the tool (right of Settings), select Install Previous Version, select the latest beta, then select select Install.
You'll need to revert to the latest version manually after testing.

yes, v4.41.0

Go to the Plugins tab, select the tool (right of Settings), select Install Previous Version, select the latest beta, then select select Install.
You'll need to revert to the latest version manually after testing.

Okay, so I installed and added it to HomeKit like the stable version. But unfortunately I get the message "No answer" But it looks good ;-)

Could you test 1.2.0-beta.3?

Hi, I installed the last beta and I can now turn Sky Q on and off again. So the connection is there. But there are no channels to be seen. greetings michel

Could you test 1.2.0-beta.5 please?

Could you test 1.2.0-beta.5 please?

Tested but unfortunately the same problem. There is a connection, it is possible to switch us on, but no station list. What is also wrong with the input sources, there is a station name that I can change, which doesn't make any sense at the moment.

Could you include your Homebridge logs please?

Could you include your Homebridge logs please?

ok. Please delete it after viewing ;-)
homebridge.log.txt

Have you tried removing and re-adding the TV since using the latest beta?

Have you tried removing and re-adding the TV since using the latest beta?

the TV? no why? It has nothing to do with the Sky Q Box, does it? But I deleted the Sky Q Box and added it again to test it. The Sky Q receiver is connected via HDMI 3 and the type of reception is cable

Could you include your Homebridge config.json please?

Could you include your Homebridge config.json please?

ok.
config.json.txt

The logging is a lot less chatty now thanks.
The issue with the inputs not appearing after a restart and requiring the home app to be killed and reopened persists. There is also an error thrown if you select the input:
[25/04/2021, 12:20:22] [skyq-tvremote] [Sky Q Mini] Set Input: 101
[25/04/2021, 12:20:22] [homebridge-skyq-tvremote] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside write handler for characteristic: input.split is not a function or its return value is not iterable. See https://git.io/JtMGR for more info.

Originally posted by @benfysh in https://github.com/neilpatel121/homebridge-skyq-tvremote/issues/19#issuecomment-826308203

The logging is a lot less chatty now thanks.
The issue with the inputs not appearing after a restart and requiring the home app to be killed and reopened persists. There is also an error thrown if you select the input:
[25/04/2021, 12:20:22] [skyq-tvremote] [Sky Q Mini] Set Input: 101
[25/04/2021, 12:20:22] [homebridge-skyq-tvremote] This plugin threw an error from the characteristic 'Active Identifier': Unhandled error thrown inside write handler for characteristic: input.split is not a function or its return value is not iterable. See https://git.io/JtMGR for more info.

Originally posted by @benfysh in #19 (comment)

okay and that means what now? Can the problem be solved?

@michel0271 Could you visit http://<IP_ADDRESS>:9006/as/services and include the data here please?

@benfysh Could you test 1.2.0-beta.6 please?

@michel0271 Could you visit http://<IP_ADDRESS>:9006/as/services and include the data here please?

ok.
service.txt

@benfysh Could you test 1.2.0-beta.6 please?

testet... the same... no Channels, on/ off Works

Could you test 1.2.0-beta.7 please?

Could you test 1.2.0-beta.7 please?

tested, now we can no longer find the Sky Q Box on Homebridge and in the HomeApp

Could you include your Homebridge logs please? Please truncate them to only the latest run.

Could you include your Homebridge logs please? Please truncate them to only the latest run.

ok.
homebridge.log.txt
config.json.txt

I'm not seeing any errors.
@benfysh Could you confirm this please?

I installed Beta 7 again. Sky Q can now be seen in HomeBridge, but it does not appear in the HomeApp

I'm not seeing any errors.
@benfysh Could you confirm this please?

Now I have installed the normal version again and I can no longer add this to the Home App either. IP address has stayed the same from Sky Q. Could it be that Apple blocks it after too many attempts? Or that there are problems at Apple?

Now I have installed the normal version again and I can no longer add this to the Home App either. IP address has stayed the same from Sky Q. Could it be that Apple blocks it after too many attempts? Or that there are problems at Apple?

Remember that TVs are external accessories, you may need to re-add it.

Remember that TVs are external accessories, you may need to re-add it.

nothing to be done, I installed the normal version 1.2.0 now. Sky Q Box can also be seen in Homebridge. But I can no longer add the box to the Home app.

@EpicKris  Before it went without any problems. What's broken now?

Try Homebridge Settings > Remove Single Cached Accessory.

Try Homebridge Settings > Remove Single Cached Accessory.

Okay ... the box is back in the Home App ... :-) Beta 7 reinstalled. When setting up the input sources it said Sky One HD, I left it that way. The Home App (see screenshot) says Sky One HD, if I press it, my box switches to channel 1100 (E! Enteraiment). All other channels are not available.

Basic plugin functionality is working as expected (Beta 7). This issue still persists https://github.com/neilpatel121/homebridge-skyq-tvremote/issues/19#issuecomment-826276471
With regards to the channels as input. When you select ''BBC One Yorks' it seems to send 101 twice and sometimes ends up on 110 as opposed to 101. The input then gets stuck on ''BBC One Yorks' and requires a restart in order to reset.
Logs shown when selecting input are displayed below:
[25/04/2021, 14:15:16] [skyq-tvremote] [Sky Q Mini] Set Input: 101
[25/04/2021, 14:15:16] [skyq-tvremote] [Sky Q Mini] Set Input: 101
[25/04/2021, 14:15:16] [skyq-tvremote] Error: This callback function has already been called by someone else; it can only be called one time.
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:6:13
    at /usr/local/lib/node_modules/homebridge-skyq-tvremote/src/platform.ts:146:95
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:4069) UnhandledPromiseRejectionWarning: Error: This callback function has already been called by someone else; it can only be called one time.
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/src/lib/util/once.ts:6:13
    at /usr/local/lib/node_modules/homebridge-skyq-tvremote/src/platform.ts:148:17
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:4069) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)

@EpicKris At least the channel is switched even if it is wrong. However, switching only worked once.

Could you test 1.2.0-beta.8 please?

Could you test 1.2.0-beta.8 please?

Tested, unfortunately the same again. When setting up in the Home App, Sky One HD was suggested which I left that way. This time the one-time switching does not work either. On / off works. I have a real guilty conscience, you are trying so hard for me ... sorry. You're great!

Please, don't apologise, it would be a great feature for this plugin.
Could you include your logs please?

Beta 8 working here will change to 101 reliably now with no error in the logs. However it is still getting 'stuck' on ''BBC One Yorks' as the selected input showing on the tile after changing channels / power cycling the box and this remains even if you kill and reopen the home app requiring a homebridge restart in order to reset to blank.
I am not sure what the expected behaviour is or if you can get the currently tuned channel in order to correctly set the input if the channel is changed? Some way to reset the input selector after choosing a channel may work?

Please, don't apologise, it would be a great feature for this plugin.
Could you include your logs please?

Thank you, then we will continue to work on the matter :-)
config.json.txt
homebridge.log.txt

Somehow we have to manage that the channel list can be read out by the plug-in of the Sky Q receiver. At least that's how it works with the Sony TV OS plug-in. But maybe that's not even possible with the Sky Q Receiver?

Somehow we have to manage that the channel list can be read out by the plug-in of the Sky Q receiver. At least that's how it works with the Sony TV OS plug-in. But maybe that's not even possible with the Sky Q Receiver?

I've grabbed the channel list from the Sky Q receiver, which is why you're seeing Sky One HD which s channel 100 for you.
Could you test 1.2.0-beta.9 please?

Somehow we have to manage that the channel list can be read out by the plug-in of the Sky Q receiver. At least that's how it works with the Sony TV OS plug-in. But maybe that's not even possible with the Sky Q Receiver?

I've grabbed the channel list from the Sky Q receiver, which is why you're seeing Sky One HD which s channel 100 for you.
Could you test 1.2.0-beta.9 please?

Tested, Sky One HD set up as relaxed as suggested. It was switched once and even on the correct channel! :-) The whole thing did not work once, then unfortunately no longer. However, the other channels are not displayed. On / off works.

@EpicKris is the intention to show all the channels from /as/services as inputs? (I am only seeing the first currently) I think there is a limit to the number of inputs to be displayed
From https://github.com/jsiegenthaler/homebridge-eosstb#readme
Input service. The input (TV channels) utilises one service per input.
The maximum possible channels (inputs) are thus 100 - 3 = 97

An option may be to grab the favourites from a box via /as/services/favourites if they exist and use those?

@EpicKris is the intention to show all the channels from /as/services as inputs? (I am only seeing the first currently) I think there is a limit to the number of inputs to be displayed

Yes, this exactly what we're trying to achieve, thank you for pointing out the limit as I'd forgotten about that.

An option may be to grab the favourites from a box via /as/services/favourites if they exist and use those?

Could you provide me with data for the /as/services/favourites please?

Could you also test 1.2.0-beta.10 please?

Could you provide me with data for the /as/services/favourites please?

This is from the one box I have them set on:
{
   "favourites" : [
      {
         "lcn" : 1,
         "sid" : "1044"
      },
      {
         "lcn" : 2,
         "sid" : "4081"
      },
      {
         "lcn" : 3,
         "sid" : "2076"
      },
      {
         "lcn" : 4,
         "sid" : "4075"
      },
      {
         "lcn" : 5,
         "sid" : "4010"
      },
      {
         "lcn" : 6,
         "sid" : "2075"
      },
      {
         "lcn" : 7,
         "sid" : "4002"
      },
      {
         "lcn" : 8,
         "sid" : "2104"
      },
      {
         "lcn" : 9,
         "sid" : "4077"
      }
   ]
}

Could you also test 1.2.0-beta.10 please?

Wooooooow ... it seems to be working! I am so happy! Even if switching is very slow. Each channel number appears on the TV individually ... first as an example the 1 ... then the 2 ... then the 3. But it works! : :)

Could you also test 1.2.0-beta.10 please?

Wooooooow ... it seems to be working! I am so happy! Even if switching is very slow. Each channel number appears on the TV individually ... first as an example the 1 ... then the 2 ... then the 3. But it works! : :)

1.2.0-beta.10 is now showing the first 97 channels as inputs on all boxes (after killing and opening the home app after restarting homebridge. and you can change channels by selecting the inputs.
It still has the same behaviour in that the previously selected input persists even if the channel is changed or the box is power cycled.

Good job! Many Thanks! I am very happy! I would like to continue to support you with the beta. Maybe we will get it to switch faster. The on-off function is also fast?

It still has the same behaviour in that the previously selected input persists even if the channel is changed or the box is power cycled.

Is there an endpoint to get the current channel that you're aware of?

https://user-images.githubusercontent.com/39130531/115998894-d259de00-a5e9-11eb-8378-b6fb19b9b28d.mov
👍🏼

It still has the same behaviour in that the previously selected input persists even if the channel is changed or the box is power cycled.

Is there an endpoint to get the current channel that you're aware of?

not that I am aware of

Is there an endpoint to get the current channel that you're aware of?

not that I am aware of

Not that I could find either, I don't think there's a way around this issue without being able to grab that information.

been having a look around, this like the HA community have managed to do this,
https://github.com/RogerSelwyn/Home_Assistant_SkyQ_MediaPlayer

can't find now typescript or js implementations, seems quite involved, with soap request, better reference implantation here..
https://github.com/4n0nD3v3l0p3r/Home_Assistant_SkyQ_MediaPlayer/blob/master/skyq/sky_remote.py

@neilpatel121 Great find, I'm going to create a separate library so we can utilise this, it even has device discovery.

I have no idea what you're doing, but I'll be there ... First Beta Tester 😂👍🏼

So I can't test the Soap requests because I don't have access to a Sky Q yet.

So I can't test the Soap requests because I don't have access to a Sky Q yet.

Let me know if I can help in any way.

For now I've released this as is. #19 has been fixed and this feature is almost done. And will re-visit this again soon.
I have started developing a library at https://github.com/EpicKris/node-sky-q, you're welcome to test that as is if you'd like, however the Soap part hasn't been fully built out yet.

Will you continue to work on the plugin? E.g. faster switching times? greetings michel

Will you continue to work on the plugin? E.g. faster switching times? greetings michel

The actual speed of switching cannot be increased, it currently works by "backing up" and then entering the channel number as if it were a remote. I'm not aware of any other way of changing the channel currently.

ok

Can we have an option to not have channels listed? It shows as 97 off on my favourites page which means you cannot easily power cycle from the control centre. The LG web OS plug in for example has an option for channel control/volume control etc

Could you test v1.3.0-beta.0?

Could you test v1.3.0-beta.0?

Favourites are now being loaded as 'Inputs' on the box where I have them set instead of the first 100 channels. On boxes without favourites no 'Inputs' are being loaded. Not sure if this is what you are expecting?
The input is also not synced with the actual channel on the box assume you are not getting the state yet?
The issue persists that on the first open of the home all inputs are shown as switches as opposed to selectable inputs. Killing and reopening the home app resolves this.

So I'm trying to use the favourites from the Sky box for the input list instead of the first 100 channels.
Could you send me a full screenshot please?

Sure:
After restarting homebridge only on first load of the home app:

After killing and reopening the home app.

The latest screenshot appears to be expected behaviour?

Yes, it just requires you to kill and reopen the home app (even if wasn't running previously) in order to get the expected behaviour. Minor in the scheme of things and may be on the iOS as opposed to the plugin side.

Oh yes, I experienced the same issue, but does seem to be an iOS issue, tried with a couple of different devices.

Hi Both,
Was this resolved - i can't see the inputs when i load this plugin into Home?
Thanks

This is what I use to use Siri to change sky channels

Does this still work, if so how?
Could you let me see the code?

@simon3163 Please open a new issue.


Use Height in sizing as well as Width

Feature request:
Allow height to be defined in the sizes, that will fit an image into the given dimensions heightXwidth as in the first example on imagemagick's docs. To make it simpler, you could make it only respect height if width is already defined, and fail otherwise.
  sizes:
    - width: 180
      height: 120
      quality: 80

Apologies for the (very) late reply on this. It sounds like the intention here is to automatically crop images, which goes beyond the scope of this plugin. The focus of this plugin is to take the burden out of implementing responsive images. Given that responsive images deal with device width, I won't be adding any functionality around height in the foreseeable future.


Support microk8s containerdRegistryConfigPath

Hi, I've got things setup on my local 5-node microk8s setup, and things seem to be working really well.
One catch is that I'd like to use a containerdRegistryConfigPath like /var/snap/microk8s/current/args/certs.d so that I don't have to update the config whenever I update my microk8s snap (otherwise the path looks like /var/snap/microk8s/6872/args/certs.d ).
However -
https://github.com/spegel-org/spegel/blob/77de00d660d35011c0237e613c02801a2bc7d8cd/pkg/oci/containerd.go#L129
this section doesn't like it if I don't use /var/snap/microk8s/6872/args/certs.d
the path with 'current' in it is a symlink to the currently installed snap version's path:
$ ls -l /var/snap/microk8s/current
lrwxrwxrwx 1 root root 4 Jun  3 00:02 /var/snap/microk8s/current -> 6872

Otherwise, I just did a helm install with these values:
spegel:
  containerdSock: "/var/snap/microk8s/common/run/containerd.sock"
  containerdRegistryConfigPath: "/var/snap/microk8s/6872/args/certs.d"
  containerdContentPath: "/var/snap/microk8s/common/var/lib/containerd/io.containerd.content.v1.content"

and edited /var/snap/microk8s/current/args/containerd-template.toml to include 'discard_unpacked_layers = false'

I am not familiar with how snap works with the dynamic directory paths, but I understand why you would want to use symlinks to get a static path. Adding a secondary check with symlinks is easy enough, and there are probably others out there who would want this in the future.


WIP: Metadata cache optimization

Currently, Blueflood stores the following metadata for numeric and string metrics:

Type
Unit
RollupType

However for numeric metrics, which is our most common use case, we do not want to store metadata information in the metadata cache and infer it automatically ie if type and rollup type are null, we assume a numeric type, Basic rollup type respectively. Units will be obtained from ElasticSearch.

@tilogaat Can you clean up the extra spaces and new lines introduced before making the ready?

Changes Unknown when pulling 4918ba8c41d25e4d7cfe1f678d3ec1d6a855d4f1 on tilogaat:meta_cache_optimization into ** on rackerlabs:master**.

@tilogaat  I'm not so sure about using ES this way. What's the pro argument?

Closing in favor of #428 and #432


Office location and capacity - phase 1

Enhancement suggested by
@P4NK4J
Parent Issue
https://github.com/ColoredCow/portal/issues/2382
Is your feature request related to a problem? Please describe.
In ColoredCow we have a culture to freely move to different locations and work from there. As ColoredCow is growing and now we have multiple offices at different locations so we need to manage the capacity of an office so that is not overpopulated at a particular time.
To manage these kinds of things, we need an operation Module where we will create functionalities related to operations.
Additional context
On this module is set up in the portal, then we can start managing our operations-related tasks from the Portal, which will help us to easily manage our infrastructure, capacity, etc
Point of Contact for guidance
@GauravGusain98

Action Items
Basics - 1 pointer

[ ] Read about Models in Laravel. Share your understanding of why we use them in the task comment in your own language
[ ] Read about Views in Laravel. Share your understanding of why we use them in the task comment in your own language
[ ] Read about Routes in Laravel. Share your understanding of why we use them in the task comment in your own language
[ ] Read about Controller in Laravel. Share your understanding of why we use them in the task comment in your own language
[ ] Read about Services files in Laravel. Share your understanding of why we use them in the task comment in your own language
[ ] Read how we can print a value in Laravel using dd()
[ ] Try printing hello world using the dd function

Laravel Modules - 1 pointer

[ ] Read about the Laravel module and what is benefit of it. Share your understanding in your own language in the task comment.
[ ] Create a new module in Portal with the name Operations

Add Home page - 1 Pointer

[ ] Add Operations option in Menu bar as shown in below image

[ ]  When Clicking on the Office Location link, then a page should open, in which the header and its center should have Coming Soon written.

Laravel modules
-A Laravel module is a larvael package
-It has controller, model ,views or routes
-It  helps to make projects
create module in larvel
-got go xampp-htdocs-larevel project file
-start the command and write the command line >php artisan module: make module_name

The menu bar is not present in the images you shared above

Please use the existing menu bar. you don't need to create a new menu bar for every page

This UI doesn't look as per the one shown in action items. Please make it correct

Looks fine. Have you created PR for this?


Utils not code covered

Since the utilities have been split out into separate files they are no longer covered by the Istanbul code coverage. On line 173 in the Gruntfile.js we need to add 'shared/gh/js/utils/*.js' and then proceed to bring coverage back up to 100%

Assigning to @bp323 for review

Coverage remained the same at 100.0% when pulling feae95dea16d6598b6ea9f3e0fd6f7814c0bbbc4 on Coenego:issue-265-coverage into 439cafdcc77761e44096b93765b1ff2c062252ef on CUL-DigitalServices:master.

Coverage remained the same at 100.0% when pulling f6c7c5c85af7902ae7d07ccf5c0dfc86e01b3e25 on Coenego:issue-265-coverage into 439cafdcc77761e44096b93765b1ff2c062252ef on CUL-DigitalServices:master.

Verified and merged, thanks for looking into this!


Exception: jetson.utils -- function wasn't passed a valid cudaImage or cudaMemory object

Hi.
Jetson Nano 2Gb+JetPack 4.6.1 (clean installation)+CSI RPi cam v2
also tried
Jetson Nano 2Gb+JetPack 4.5 (clean installation)+CSI RPi cam v2
Camera streaming is fine on both.
There is an issue with detection networks from the examples folder, for example my_detection.py with SSD-Mobilenet-v2.
log.txt
Commenting out the detection part and adding print(img.format) gives "rgb8". In addition there are a lot of "[gstreamer] gstCamera::Capture() -- a timeout occurred waiting for the next image buffer" during this test run.

Hi @Boris7Britva, can you try rebuilding with -DENABLE_NVMM=off cmake option?
cd jetson-inference/build
cmake -DENABLE_NVMM=off ../
make
sudo make install

Hi @dusty-nv , thank you for fast reply.
Rebuild done per your input - still same issue:
log1.txt

oh okay, after inspecting the logs again, that may not have been necessary.
Are you able to run video-viewer.py or detectnet.py okay?    I may need to update my-detection.py for something

@dusty-nv is there anything else I can try?

@Boris7Britva I'm not sure why your camera freezes only when running detectnet, sorry about that.  To further debug it, are you able to process a video file with detectnet okay?    https://github.com/dusty-nv/jetson-inference/blob/master/docs/detectnet-console-2.md#processing-video-files
Also, have you tried running the jetson-inference docker container to see if you get different results?   https://github.com/dusty-nv/jetson-inference/blob/master/docs/aux-docker.md

@Boris7Britva thanks, unfortunately I'm unable to reproduce this - can you try commenting out these two lines from detectnet.py:
https://github.com/dusty-nv/jetson-inference/blob/56604b07da34bdf32c02e1201ab99c413b47bc85/python/examples/detectnet.py#L90
then make sure you run the detectnet.py that has your changed modifications (or rename it to something else)

@dusty-nv, please see the log:
log_detectnet_edited.txt

@Boris7Britva everything looks normal in that log except the video seems to stop early.   I wonder if the video is corrupted?
Can you try running this example?  https://github.com/dusty-nv/jetson-inference/blob/master/docs/imagenet-console-2.md#processing-a-video

@Boris7Britva I still see a lot of errors in your logs about nvbuf utils - are you sure that you re-build/re-installed with -DENABLE_NVMM=off?
cd jetson-inference/build
cmake -DENABLE_NVMM=off ../
make
sudo make install

(this should be done outside of container and you shouldn't use container)

@dusty-nv Sorry, I reinstalled the image yesterday and didn't apply that option.
Attached log after disabling NVMM
log_jellyfish_nvmm_off.txt

OK, I believe the issue now is that you are trying to save the video to a directory that doesn't exist in your current path:
~/Downloads/AI/jetson-inference/python/examples$ ./imagenet.py --network=resnet-18 jellyfish.mkv images/test/jellyfish_resnet18.mkv

(there is no images/test directory under jetson-inference/python/examples to save to)
Instead, just save jellyfish_resnet18.mkv to the current directory - try just running it as:
~/Downloads/AI/jetson-inference/python/examples$ ./imagenet.py --network=resnet-18 jellyfish.mkv jellyfish_resnet18.mkv

Ok. This one worked.
I've bought a new Rpi cam v2.1 to make sure it's not camera issue.
Can you please explain what's wrong for this simple script?
log_jetson_csi.txt
jetson_csi.py.txt

Hi@Boris7Britva @dusty-nv . I am a beginner that met the same problem on jetson.inference.detectNet().
I was running these lines,and the csi camera was running just fine:
import jetson.utils
input = jetson.utils.videoSource("csi://0")
output = jetson.utils.videoOutput("display://0")
while output.IsStreaming():
img = input.Capture()
output.Render(img)
But after I put detectNet in to the lines, it showed the same problem that @Boris7Britva got:
import jetson.utils
input = jetson.utils.videoSource("csi://0")
output = jetson.utils.videoOutput("display://0")
import jetson.inference
net = jetson.inference.detectNet("ssd-mobilenet-v2",threshold=0.5)
while output.IsStreaming():
img = input.Capture()
detections = net.Detect(img)
output.Render(img)
output.SetStatus("Performance:{:.0}FPS".format(net.GetNetworkFPS()))
Exception: jetson.utils -- function wasn't passed a valid cudaImage or cudaMemory object
log.txt
I have already tried  re-build/re-installed with -DENABLE_NVMM=off and it still showed the same exception.
I am using Jetson Nano 2Gb+ JetPack 4.6.3 with L4T 32.7.3 and IMX219 CSI camera.
Can you help me to fix this please? Thank you so much.

I tried to use another TF card to reinstall the image and run  the script again. Still had the same exception, but the log looked differently.
log.txt

Thank you @dusty-nv . Firstly, I checked Line 65 in detectnet.py and add that if img is None: like this:
`while True:
# capture the next image
img_input = input.Capture()
if img_input is None: # timeout
    continue

img = input.Capture()

if img is None: # timeout
    continue  `

And  I noticed that we got  if img_input is None: as well.
Secondly, I ran nvgstcapture-1.0 on terminal and the first time the video stream or window didn't show up. And then I turned off Jetson nano and check the connection of my CSI camera and ran nvgstcapture-1.0 again. Then I saw the video is streaming. But when I ran my Script:
`import jetson_utils
input = jetson_utils.videoSource("csi://0")
output = jetson_utils.videoOutput("display://0")
import jetson_inference
net = jetson_inference.detectNet("ssd-mobilenet-v2",threshold=0.5)
while output.IsStreaming():
img = input.Capture()
detections = net.Detect(img)
output.Render(img)It still showsgstCamera::Capture() -- a timeout occurred waiting for the next image bufferand File "1.py", line 10, in
detections = net.Detect(img)
Exception: jetson.utils -- function wasn't passed a valid cudaImage or cudaMemory object
`
log.txt
Thanks for your help@dusty-nv

If I try usb camera instead of csi camera, the script ran well. I wonder which part went wrong.

It still shows
gstCamera::Capture() -- a timeout occurred waiting for the next image buffer and
 File "1.py", line 10, in <module> detections = net.Detect(img) Exception: jetson.utils -- function wasn't passed a valid cudaImage or cudaMemory object

@mmhzlrj modify your script to be like this:
while output.IsStreaming():
	img = input.Capture()
	if img is None:
		continue
	detections = net.Detect(img)
	output.Render(img)

gstCamera::Capture() -- a timeout occurred waiting for the next image buffer and
 File "1.py", line 10, in <module> detections = net.Detect(img) Exception: jetson.utils -- function wasn't passed a valid cudaImage or cudaMemory object

Problem solved. Thank you so much @dusty-nv

Hi @dusty-nv ,
I am also currently having this problem whilst trying to run a modified version of my-detection.py I have made. I am currently using a CLI therefore, I removed all instances of the display object.
Heres the Code and Log:
`from jetson_inference import detectNet
from jetson_utils import videoSource
net = detectNet("ssd-mobilenet-v2", threshold=0.5)
camera = videoSource("csi://0")      # '/dev/video0' for V4L2
while True:
img = camera.Capture()
detections = net.Detect(img)

print(detections)`

log.txt
Note: I have denabled NVMM using the following commands:
cd jetson-inference/build
cmake -DENABLE_NVMM=off ../
make
sudo make install
Any help would be appreciated,
Thanks,
Mathias


Open new Code Lens PR

I haven't had enough time yet (or hung up on a different very interesting task) to open a new PR yet.
With this I'm tracking the task to open the PR and post if here if I'm running into a particular problem.

sorry that I didn't take care of this yet :(

@realvictorprm
can you get us a pr labelling it as experimental, and with an off by default switch.
Thanks
Kevin

@KevinRansom this time for master?

Master is the branch now, yes.

Thanks
Phillip Carter<EMAIL_ADDRESS>schrieb am So., 13. Mai 2018,
17:50:

Master is the branch now, yes.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/visualfsharp/issues/4868#issuecomment-388636579,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AYPM8Eo1CpP43I2zLhD2GBMu4VvSl_WHks5tyFZegaJpZM4T4wW2
.

Closing old issue, as CodeLens is now in for 15.8


added super inside constructor

we need to call the super to initialize Component states.

Already merged same fix, sorry :)

I guess I wasn't fast enough. Next time :P. Good job!

Thank you for helping me maintain this :+1:


UI: Add notice when "too many scrape pools"

Proposal
Hello!
Something that quite confused me, until I read the source code, was this snippet:
https://github.com/prometheus/prometheus/blob/d6e1b1acdb1231f5bb694bc482b568ccea2b40af/web/ui/react-app/src/pages/targets/ScrapePoolList.tsx#L235-L241
Would be really nice with a small notification in the UI stating why the first option was picked, instead of just silently picking the first item. Such as:

There's a lot of targets. To not stress your browser, we're only showing the first target.
Click here to show all targets

Also, would be great if this was configurable. We don't have that many targets. In fact, we just have 21 targets. Having the limit at 20 seems a bit arbitrarily low. Is it possible to set configs specifically for the UI?
Kind regards

cc @juliusv


Is a significant difference of the DesignMatrix of the PLD exist between the latest lightkurve and the version 1.10.0 ?

Hi everyone,
I found a significant difference in building the DesignMatrix of the PLD between the latest pldcorrector.py and the old one in lightkurve 1.10.0.   During creating the DesignMatrix of each PLD orde,  the for loop seems to start from the first order of PLD in the latest version while that from the second order in the old version.  Is my understanding right?  Should we correct the first index of the for loop from 2 to 1 in lightkurve 1.10.0?  Please see the following parts for the details.
I prefer the PLD implementation in lightkurve 1.10.0 because of the GPs model for the stellar variability. Thanks.
######################################## The Latest version.
# Background-subtracted, flux-normalized pixel time series
regressors = self.tpf.flux[:, pld_aperture_mask].reshape(len(self.tpf.flux), -1)
regressors = regressors - bkg.flux.reshape(-1,1) * pld_aperture_mask.sum() * u.pixel
regressors = np.array([r[np.isfinite(r)] for r in regressors])
regressors = np.array([r / f for r,f in zip(regressors, self.lc.flux.value)])
    # Use the DesignMatrix infrastructure to apply PCA to the regressors.
    with warnings.catch_warnings():
        warnings.filterwarnings('ignore', message='.*low rank.*')
        regressors_dm = DesignMatrix(regressors)
    if isinstance(pca_components, (tuple, list)):
        ncomp = pca_components[0]
    else:
        ncomp = pca_components
    if ncomp > 0:
        regressors_dm = regressors_dm.pca(ncomp)
    regressors_pld = regressors_dm.values

    # Create a DesignMatrix for each PLD order
    all_pld = []
    **for order in range(1, pld_order+1):
        reg_n = np.product(list(multichoose(regressors_pld.T, order)), axis=1).T**
        with warnings.catch_warnings():
            warnings.filterwarnings('ignore', message='.*low rank.*')
            pld_n = DesignMatrix(reg_n)
        # Apply PCA. Check if pca_components has an entry for each order,
        # otherwise use pca_components for PCA of higher order matrices.

#################################
################################# The old version
# first order PLD design matrix
pld_flux = flux_crop[:, aperture_crop]
f1 = np.reshape(pld_flux, (len(pld_flux), -1))
X1 = f1 / np.nansum(pld_flux, axis=-1)[:, None]
# No NaN pixels
X1 = X1[:, np.isfinite(X1).all(axis=0)]
    # higher order PLD design matrices
    **X_sections = [np.ones((len(flux_crop), 1)), X1]
    for i in range(2, pld_order+1):
        f2 = np.product(list(multichoose(X1.T, pld_order)), axis=1).T**
        try:
            # We use an optional dependency for very fast PCA (fbpca).
            # If the import fails we will fall back on using the slower `np.linalg.svd`
            from fbpca import pca
            components, _, _ = pca(f2, n_pca_terms)
        except ImportError:
            log.error("PLD uses the `fbpca` package. You can pip install "
                      "with `pip install fbpca`. Using `np.linalg.svd` "
                      "instead.")
            components, _, _ = np.linalg.svd(f2)
        X_n = components[:, :n_pca_terms]
        X_sections.append(X_n)

    # Create the design matrix X by stacking X1 and higher order components, and
    # adding a column vector of 1s for numerical stability (see Luger et al.).
    # X has shape (n_components_first + n_components_higher_order + 1, n_cadences)
    X = np.concatenate(X_sections, axis=1)

##################################
Best wishes,
Sun

@exo-hunter Thank you for opening an issue!
There have indeed been significant changes to PLDCorrector as part of PR #746.
The biggest change is the removal of Gaussian Processes (GPs) in favor of using splines to fit long-term trends.  We decided to start using splines because they are much faster and easier to fit.  We think splines should work equally well, but perhaps the default parameters have not been set correctly yet.  Would you be willing to post example code for a target that worked much better with GPs than splines?  That would help us figure out how to do better!
Changing the first index in the pld_order for loop should not make a different. In the past, the first PLD order was created separately, above the for loop, on lines 200-205.  We simplified the code to make these lines part of the for loop, but it should not make a big difference:
https://github.com/KeplerGO/lightkurve/blob/6d602ebf227f2f7398f0b3268c74e1272dd259ef/lightkurve/correctors/pldcorrector.py#L200-L222

@barentsen  Thank you for your quick reply.
You are right. The first-order regressor of PLD  was built separately in the old version.  But I guess that "f2 = np.product(list(multichoose(X1.T, pld_order)), axis=1).T" should be replaced with "f2 = np.product(list(multichoose(X1.T, i)), axis=1).T".   When someone want to employ 3 order PLD instand of the default order (e.g. default pld_order=2) in the old version , the former expression will make a mistake.
I am a big fan of GPs.  And the nonparametric form and flexibility of GPs are actually suitable for unknown stellar variability.  The celerite Matern-3/2 kernel was implemented in lightkurve 1.10.0, which could be optimized with better hyperparameter estimation by using non-linear optimization algorithms (like L-BFGS-B of scipy.optimize).
Later, I will try to compare the PLD correction results in some specific cases.
Thanks,
Sun

in the old version , the former expression will make a mistake.

You're right, it looks like the old version contained a bug when using pld_order > 2!

I am a big fan of GPs.

So are we, but we struggled to make the GPs fast and robust enough.  We are hoping that splines can offer the same flexibility at a fraction of the speed, albeit without the uncertainty propagation with makes GPs particularly nice.
I'd be very interested to look at specific examples where GPs work and splines don't!

@exo-hunter I'm going to close this issue because there hasn't been any activity for 2 weeks, but feel free to re-open if you come across a good example that we can debug/investigate to make PLDCorrector work better.  I'd be very interested in that any time!  :+1:


Adds Events for "data" and "labels" to VictoryLegend

I couldn't figure out how to get "parent" events working then realized that parent events probably aren't very useful for this component. If it seems worth adding, I'll look into adding them back in.
Fixes https://github.com/FormidableLabs/victory/issues/477
cc @boygirl

@zachhale VictoryLegend is going to need a getBaseProps static method in order to work with shared events (i.e. be controlled by other components like VIctoryChart)
Here's an example of getBaseProps https://github.com/FormidableLabs/victory-chart/blob/master/src/components/victory-bar/victory-bar.js#L137
https://github.com/FormidableLabs/victory-chart/blob/master/src/components/victory-bar/helper-methods.js#L96
It should also have an expectedComponents static so that it can pick up defaultEvents from any of its sub components.
like this:
https://github.com/FormidableLabs/victory-chart/blob/master/src/components/victory-bar/victory-bar.js#L138


Revert to using jcenter for dokka

This PR reverts to using jcenter for now for Dokka to work correctly.

Does Dokka have a planned alternative to jcenter?

@weisers Yep! The latest versions of Dokka are already on mavenCentral, but some dependencies are not yet: https://github.com/Kotlin/dokka/issues/1725
I've created a tracking issue here: #47

Thanks @weisers and @dperez37 !


WIP: Added support for debugging external test processes

Description
Added support for debugging external test processes.
Related issue
https://github.com/microsoft/vstest-docs/blob/ec090fe5dc2b47948c7b771ea0ecf25d978f164b/RFCs/0029-Debugging-External-Test-Processes.md

@cvpoienaru Marked this as WIP so I have easier time reviewing the list of PRs. Please unmark it when it's ready to merge.

I agree, that sounds like something we could benefit from here. This did come up earlier too but I'm not sure why we couldn't move. Is anything blocking vstest from moving to C# 8?

In reply to: 364763134 [](ancestors = 364763134)

I agree, that sounds like something we could benefit from here. This did come up earlier too but I'm not sure why we couldn't move. Is anything blocking vstest from moving to C# 8?
In reply to: 364763134 [](ancestors = 364763134)

I got really excited when this was first proposed. It would've saved us a lot of headaches down the road, but unfortunately won't work on today's implementation and that's kind of a bummer :(
Quoting @shyamnamboodiripad reply: (https://github.com/microsoft/vstest/pull/2325#discussion_r390082079) "Unfortunately, default interface implementation depends on CLR features that are not available when targeting net472 (requires netcoreapp3.0). Since VS and many test adapters still run atop net472 I don't believe we can use default interface implementation yet."

public interface ITestRequestHandler : IDisposable

So this interface could be made internal too?

Refers to: src/Microsoft.TestPlatform.CommunicationUtilities/Interfaces/ITestRequestHandler.cs:17 in 234a53c. [](commit_id = 234a53cc5859800f1a993a8ae3038d9603b5dbdc, deletion_comment = False)

public interface IDesignModeClient : IDisposable

can be made internal

Refers to: src/Microsoft.TestPlatform.Client/DesignMode/IDesignModeClient.cs:15 in 234a53c. [](commit_id = 234a53cc5859800f1a993a8ae3038d9603b5dbdc, deletion_comment = False)

How are we tracking the documentation update and filling in the test matrix we discussed?

ITestRequestHandler and IDesignModeClient cannot be made internal without significant work outside the scope of this PR. I already opened an issue here to track this change: https://github.com/microsoft/vstest/issues/2362


Minor APIView improvements for Java

Three fixes to the Java APIView processor:

Remove unnecessary newline on the maven dependencies list
Remove all anonymous inner class code from appearing in public static field declarations, as it was just adding a lot of noise.
Remove duplicate "missing JavaDoc" error messages

Can you please update the parser version if this change needs to update existing reviews? Please also update the parser version in JavaLanguageService.cs and APIView.csproj file.

Can you please update the parser version if this change needs to update existing reviews? Please also update the parser version in JavaLanguageService.cs and APIView.csproj file.

@praveenkuttappan Will do - although I'm curious if we could make this simpler? I always wish there was just one file to update, and it's now even worse because I have to update the XmlLanguageService too! :-) And I always need to hunt around for the right files (e.g. it isn't APIView.csproj, it's APIViewWeb.csproj, but I only realised that after I opened the wrong one) :-)

@praveenkuttappan Please let me know if the version string updates are correct (I'm never entirely sure when I should update the json-output versionString value)

Ping @praveenkuttappan - thanks!

This is failing for reasons unrelated to the PR - can you get it merged and deployed sometime please @praveenkuttappan?

/azp run azure-sdk-tools - APIView

/check-enforcer override


istio.io setup/install/multicluster/primary-remote/test.sh test fails on main branch

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
Bug description
This may be a duplicate of #29388 as the east west-gateway isn't found.
setup/install/multicluster/primary-remote_multi-network/test.sh also fails with the same message.
Trying to move the istio.io tests from the release-1.8 branch to main and the test now fails. The tail end of the log (https://storage.googleapis.com/istio-prow/pr-logs/pull/istio_istio.io/8562/doc.test.multicluster_istio.io/1334602913783222272/artifacts/tests-setup-multicluster-42277d/TestDocs/setup/install/multicluster/primary-remote/test.sh/test.sh/_test_context/test.sh_output.txt):
Installing Istio on Primary cluster: kind-doc-cluster1
This will install the Istio 1.9.0 default profile with ["Istio core" "Istiod" "Ingress gateways"] components into the cluster. Proceed? (y/N)
- Processing resources for Istio core.
✔ Istio core installed
- Processing resources for Istiod.
- Processing resources for Istiod. Waiting for Deployment/istio-system/istiod
✔ Istiod installed
- Processing resources for Ingress gateways.
- Processing resources for Ingress gateways. Waiting for Deployment/istio-system/istio-ingressgat...
✔ Ingress gateways installed
- Pruning removed resources
✔ Installation completeCreating the east-west gateway

- Processing resources for Istio core.
✔ Istio core installed
- Processing resources for Istiod.
- Processing resources for Istiod. Waiting for Deployment/istio-system/istiod
✔ Istiod installed
- Processing resources for Ingress gateways.
- Processing resources for Ingress gateways. Waiting for Deployment/istio-system/istio-ingressgat...
✔ Ingress gateways installed
- Pruning removed resources
✔ Installation completeWaiting for the east-west gateway to have an external IP
VERIFY FAILED snip_install_the_eastwest_gateway_in_cluster1_2 (timeout after 120s):
received:
"Error from server (NotFound): services "istio-eastwestgateway" not found"
expected:
"NAME                    TYPE           CLUSTER-IP    EXTERNAL-IP    PORT(S)   AGE
istio-eastwestgateway   LoadBalancer   <IP_ADDRESS>   <IP_ADDRESS>   ...       51s"

Expected behavior
Steps to reproduce the bug
Run the istio.io test or try and follow the instructions on the content/en/docs/setup/install/multicluster/pimary-remote/index.md page.
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you used Helm)
main branch
How was Istio installed?
via test framework
Environment where the bug was observed (cloud vendor, OS, etc)
pipeline
Additionally, please consider running istioctl bug-report and attach the generated cluster-state tarball to this issue.
Refer cluster state archive for more details.

@nmittler @stevenctl could one of you look at this?  This is preventing us from testing istio.io on master.

@nmittler @stevenctl could one of you look at this?  This is preventing us from testing istio.io on master.

@linsun I am able to reproduce with this script (basically a copy & paste of the snippets from istio.io.
One thing I noticed was that the discovery address in the sidecar is istiod.istio-system rather than istiod-remote.istio-system. Is it possible that some of the central istiod work has broken this?

@linsun I am able to reproduce with this script (basically a copy & paste of the snippets from istio.io.
One thing I noticed was that the discovery address in the sidecar is istiod.istio-system rather than istiod-remote.istio-system. Is it possible that some of the central istiod work has broken this?

I also see a lot of recent activity to https://github.com/istio/istio/commits/master/manifests/charts/istiod-remote
@linsun re-assigning to you since I believe this is related to recent work related to istiod-less remotes.

I also see a lot of recent activity to https://github.com/istio/istio/commits/master/manifests/charts/istiod-remote
@linsun re-assigning to you since I believe this is related to recent work related to istiod-less remotes.

Thanks @nmittler for the investigation!  It looks like we never updated the docs to be istiodless on the remote cluster.  I can take a stab at updating it.
I think the discovery addr is supposed to be istiod.istio-system as there is no other istiod on the remote cluster thus no need to use a different name like istiod-remote.istio-system
@irisdingbj pls correct me if I'm wrong here.

Thanks @nmittler for the investigation!  It looks like we never updated the docs to be istiodless on the remote cluster.  I can take a stab at updating it.
I think the discovery addr is supposed to be istiod.istio-system as there is no other istiod on the remote cluster thus no need to use a different name like istiod-remote.istio-system
@irisdingbj pls correct me if I'm wrong here.

@linsun ok sounds good. One concern I have is that if we're making the leap to istiod-less, we need to make sure that we're not breaking upgrade. Have you tested upgrade of remotes from legacy to istiod-less?

@linsun ok sounds good. One concern I have is that if we're making the leap to istiod-less, we need to make sure that we're not breaking upgrade. Have you tested upgrade of remotes from legacy to istiod-less?

Update. A change was merged, https://github.com/istio/istio/pull/30377 and it's cherry-pick, which allows the install to happen in both the PrimaryRemote and PrimaryRemote-MultiNetwork tests, but they are now failing when trying to verify cross cluster traffic.
An example failure is here: https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio.io/8854/doc.test.multicluster_istio.io/1354427767550119936
The failure is now:
Verifying load balancing from kind-doc-cluster2
VERIFY FAILED snip_verifying_crosscluster_traffic_3 (timeout after 120s):
received:
"Hello version: v2, instance: helloworld-v2-7855866d4f-qnplj"
expected:
"Hello version: v1, instance:"

It seems no traffic is flowing from cluster 2 to cluster 1.

Update. A change was merged, https://github.com/istio/istio/pull/30377 and it's cherry-pick, which allows the install to happen in both the PrimaryRemote and PrimaryRemote-MultiNetwork tests, but they are now failing when trying to verify cross cluster traffic.
An example failure is here: https://prow.istio.io/view/gs/istio-prow/pr-logs/pull/istio_istio.io/8854/doc.test.multicluster_istio.io/1354427767550119936
The failure is now:
Verifying load balancing from kind-doc-cluster2
VERIFY FAILED snip_verifying_crosscluster_traffic_3 (timeout after 120s):
received:
"Hello version: v2, instance: helloworld-v2-7855866d4f-qnplj"
expected:
"Hello version: v1, instance:"

It seems no traffic is flowing from cluster 2 to cluster 1.

@nmittler sounds like the pods in cluster 2 are using cluster 2's control plane

@nmittler sounds like the pods in cluster 2 are using cluster 2's control plane

@linsun this is an actual bug and a regression for multi-cluster. I don't have the feeling that istiod-less remotes are in a state where they're ready to be made a default. For example, I'm not sure we've thought through the upgrade story. For 1.9, I think the safe move is to go back to the legacy istiod-based remotes by default. This includes reverting our tests as well.
This seems like a release blocker to me. Can you take a look?
FYI @smawson @stevenctl @duderino @ericvn

@linsun this is an actual bug and a regression for multi-cluster. I don't have the feeling that istiod-less remotes are in a state where they're ready to be made a default. For example, I'm not sure we've thought through the upgrade story. For 1.9, I think the safe move is to go back to the legacy istiod-based remotes by default. This includes reverting our tests as well.
This seems like a release blocker to me. Can you take a look?
FYI @smawson @stevenctl @duderino @ericvn

I had previously marked this as a release-blocker.

I had previously marked this as a release-blocker.

@linsun Yes, there is an istiod in the cluster, however istio.io tests fail due to the fact that installation appears to be using the remote's istiod for discovery. In other words, the installation is broken for remote clusters in 1.9. The problem isn't the docs, it's the installation itself. The reason it wasn't discovered by integration tests was that we moved all of the integ tests over to using istiod-less remotes in anticipation that istiod-less remotes would be beta for 1.9. That didn't happen, however, so we now need to revert that.

@linsun Yes, there is an istiod in the cluster, however istio.io tests fail due to the fact that installation appears to be using the remote's istiod for discovery. In other words, the installation is broken for remote clusters in 1.9. The problem isn't the docs, it's the installation itself. The reason it wasn't discovered by integration tests was that we moved all of the integ tests over to using istiod-less remotes in anticipation that istiod-less remotes would be beta for 1.9. That didn't happen, however, so we now need to revert that.

I ran the istio.io tests against the 1.9 branch commit which contains the cherry pick for fix discoveryAddress in configmap template (https://github.com/istio/istio/pull/30524). The multicluster tests did pass.

I ran the istio.io tests against the 1.9 branch commit which contains the cherry pick for fix discoveryAddress in configmap template (https://github.com/istio/istio/pull/30524). The multicluster tests did pass.


[Idea]: Please add spawn to the aliases for mvs to the plugin.yml inside the jar. It takes seconds, but would solve the problem of players used to typing /spawn receiving a command not found error when they do.

Describe the feature
Make the following change to the plugin.yml file inside the .jar   Add spawn as an alias along with mvs.
mvspawn:
description: Teleport to the spawn area
aliases: [mvs, spawn]    <<---------<<<<<
usage: / [player] -- Teleports you to the spawn area of your current world.
How is the feature useful to all Multiverse users?
Players will be able to use the command they are most used to, without getting an error, and without having to be reminded to use /mvs.
This is not so much a feature as a convenience. It takes me about ten seconds to do this myself, and once done it is permanent. Just do it now for everyone and problem solved.
Agreements

[X] I have searched for and ensured there isn't already an open issue regarding this.

Aliases can be configured.
https://www.spigotmc.org/wiki/command-alias/
aliases:
    spawn:
    - "mvspawn $1-"

Should do it.

Did you even read what I wrote? Do you really want to be responding to
people to tell them things they already know, when you can make a change
inside the jar that will be forever that you never have to think of again?
In other words, you could have done this in the time it took you to respond
to me. I already told you I was capable of making the change and had
already. Now it's your turn. If you so choose.
On Thu, Jan 6, 2022, 3:18 PM Ryan Leach @.***> wrote:

Aliases can be configured.
https://www.spigotmc.org/wiki/command-alias/
aliases:
spawn:
- "mvspawn $1-"
Should do it.
—
Reply to this email directly, view it on GitHub
https://github.com/Multiverse/Multiverse-Core/issues/2750#issuecomment-1006906247,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARGFQQXD52DOHQGWY5VMX6LUUX2KDANCNFSM5LMZTMDQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

You said you could do it yourself. You didn't provide enough context on how. For all I know you may have thought it was difficult.
Personally, I much rather MV stays in it's lane, so I don't need to prevent conflicts with other plugins that use /spawn.

@Dave-Redisfa Commands.yml is not changing the mv's jar in any way. And I agree with @ryantheleach, mv does not want to override any vanilla commands.

@Dave-Redisfa There's 2 Commands.yml if you wern't aware. One in each jar and one in the root directory of bukkit. I was talking about the one in the root directory of bukkit.


Support Alibaba-NLP/gte-multilingual-base & Alibaba-NLP/gte-multilingual-reranker-base

Model description
The GTE model family has consistent support on Hugging Face TEI, but the newly introduced gte-multilingual-base fails to be supported at this moment.
2024-08-03T08:44:51.913133Z  INFO download_pool_config: text_embeddings_core::download: core/src/download.rs:38: Downloading `1_Pooling/config.json`
2024-08-03T08:44:52.701241Z  INFO download_new_st_config: text_embeddings_core::download: core/src/download.rs:62: Downloading `config_sentence_transformers.json`
2024-08-03T08:44:52.885881Z  INFO download_artifacts: text_embeddings_core::download: core/src/download.rs:21: Starting download
2024-08-03T08:44:52.885905Z  INFO download_artifacts: text_embeddings_core::download: core/src/download.rs:23: Downloading `config.json`
2024-08-03T08:44:53.270526Z  INFO download_artifacts: text_embeddings_core::download: core/src/download.rs:26: Downloading `tokenizer.json`
2024-08-03T08:44:53.749799Z  INFO download_artifacts: text_embeddings_backend: backends/src/lib.rs:331: Downloading `model.safetensors`
2024-08-03T08:44:57.772619Z  INFO download_artifacts: text_embeddings_core::download: core/src/download.rs:32: Model artifacts downloaded in 4.886736258s
Error: `config.json` does not contain `id2label`

The same error happens for both biencoder and reranker.
Open source status

[X] The model implementation is available
[X] The model weights are available

Provide useful links for the implementation
https://huggingface.co/Alibaba-NLP/gte-multilingual-base
https://huggingface.co/Alibaba-NLP/gte-multilingual-reranker-base

TEI determines the type of backend model by the architectures in config.json code.
However, gte-multilingual-base architectures in config.json are NewModel and NewForTokenClassification. I guess it'd be good to change the config (e.g. removing NewForTokenClassification from the architectures)
the reranker has a correct architecture name, but the config does not contain id2label. So, I assume adding id2label seems good (or loading as a reranker model if there's no id2label key in the config.json).
In short, opening a PR to remove/add the config can solve the issues.

@kozistr nice guidance. will look into it

https://huggingface.co/Alibaba-NLP/gte-multilingual-base/discussions/7#66bfb82ea03b764ca92a2221

@nbroad1881 yup, I've found that renaming weight keys to remove prefixes like "new" and ensuring they follow the standard model naming pattern (e.g., "encoder.layer.0.attention.self.query.weight") improves compatibility for my own,


type savety and Elixir

So?

Embedded Elixir is a bad word use, because the first thing that comes to mind is the embedded Elixir

Oh. I changed this :slightly_smiling_face:

Changed it a little to avoid words that might be unnecessarily confusing for less experienced visitors


Problems when extracting chains from PDB files

Hi,
I was using "input_output.extractPDB" to extract PDB chains for my work and two problems popped up. Essentially the code can end up missing a few residues depending on the following:
1:
class NotDisordered(Select):
    def accept_atom(self, atom):
        return not atom.is_disordered() or atom.get_altloc() == "A"

According to the comment on this class, it is supposed to exclude disordered atoms. However, this class actually is used to save disordered atoms. It appears to be a result of an error in the validation of the X-ray-derived structure (link), whereby two different configurations are given for a set of atoms. What this code is supposed to do is to choose one out of those two configurations ().
Typically the two configurations are labelled 'A' and 'B', however I have noticed that they can be labelled as '1' or '2'. When they are labelled '1' or '2', the class returns False -- the disordered residues are ignored. For my own work, I have used the following function to ensure that the residues are not ignored, even if they are labelled '1' or '2'.
class NotDisordered(Select):
    def accept_atom(self, atom):
        return not atom.is_disordered() or atom.get_altloc() == "A" or atom.get_altloc() == "1"

2:
Modified / non-canonical amino acids are designated HETATM in the PDB, even though they are clearly amino acids. I added a function which reads the names of modified / non-canonical amino acids from the PDB SEQRES section, and notes the non-standard codes.
from Bio.SeqUtils import IUPACData
PROTEIN_LETTERS = [x.upper() for x in IUPACData.protein_letters_3to1.keys()]

def find_modified_amino_acids(path):
    res_set = set()
    for line in open(path, 'r'):
        if line[:6] == 'SEQRES':
            for res in line.split()[4:]:
                res_set.add(res)
    for res in list(res_set):
        if res in PROTEIN_LETTERS:
            res_set.remove(res)
    return res_set

def extractPDB(
    infilename, outfilename, chain_ids=None, includeWaters=False, invert=False
):
    # extract the chain_ids from infilename and save in outfilename.
    # includeWaters: deprecated parameter, include the crystallographic waters (should not be used).
    # invert: Select all chains EXCEPT those in chain_ids.
    parser = PDBParser(QUIET=True)
    struct = parser.get_structure(infilename, infilename)
    model = Selection.unfold_entities(struct, "M")[0]
    chains = Selection.unfold_entities(struct, "C")

    # Select residues to extract and build new structure
    structBuild = StructureBuilder.StructureBuilder()
    structBuild.init_structure("output")
    structBuild.init_seg(" ")
    structBuild.init_model(0)
    outputStruct = structBuild.get_structure()

    # Load a list of non-standard amino acid names -- these are
    # typically listed under HETATM, so they would be typically
    # ignored by the orginal algorithm
    modified_amino_acids = find_modified_amino_acids(infilename)

    for chain in model:
        if (
            chain_ids == None
            or (chain.get_id() in chain_ids and not invert)
            or invert == True
        ):
            structBuild.init_chain(chain.get_id())
            for residue in chain:
                het = residue.get_id()
                if not invert:
                    if het[0] == " " or (het[0] == "W" and includeWaters):
                        outputStruct[0][chain.get_id()].add(residue)
                    elif het[0][-3:] in modified_amino_acids:
                        print(het[0])
                        outputStruct[0][chain.get_id()].add(residue)
                else:
                    if (het[0] == "W" and includeWaters) or (
                        chain.get_id() not in chain_ids
                    ):
                        outputStruct[0][chain.get_id()].add(residue)
                    elif het[0][-3:] in modified_amino_acids:
                        outputStruct[0][chain.get_id()].add(residue)
                                                                                63,0-1

    # Output the selected residues
    pdbio = PDBIO()
    pdbio.set_structure(outputStruct)
    pdbio.save(outfilename, select=NotDisordered())

Thank you jomimc!!! These are very useful fixes! I have uploaded them with proper credit. I'm excited to use this.