text:
make install also installs the tests

Describe the bug
make DESTDIR="/wherever/" install also copies tests
To Reproduce
./configure --prefix=/usr
make
make DESTDIR="/wherever/" install
this creates the $PWD directory tree and tests, like /home/zoe/Downloads/mptcpdpkg/pkg/mptcpd/home/zoe/Downloads/mptcpdpkg/src/mptcpd-0.4/tests in my case. (here DESTDIR was "/home/zoe/Downloads/mptcpdpkg/pkg/mptcpd/"
Expected behavior
tests should not be installed, and especially not under /prefix/$build_pwd
Desktop:

Linux Kernel: 5.6.14-arch1-1
Compiler: gcc version 10.1.0

Additional context
an arch PKGBUILD:
pkgname=mptcpd
pkgver=0.4
pkgrel=1
pkgdesc="Multipath TCP daemon"
url="https://github.com/intel/mptcpd"
arch=('x86_64')
license=('GPL2' 'BSD')
depends=('ell')
source=("https://github.com/intel/mptcpd/releases/download/v$pkgver/$pkgname-$pkgver.tar.gz")
sha512sums=('1db9fa7182b167d45c44e16dcec051f426039eeeb84dc5b7352819f5b5048e5f5cdc22c567b32054b72bed444869cad36b24c3354e63d671a807010d0b9aab68')

#prepare() {
#       cd "$pkgname-$pkgver"
#    #./bootstrap # only required when building a git clone
#}

build() {
        cd "$pkgname-$pkgver"
    ./configure --prefix=/usr
    make
}

package() {
        cd "$pkgname-$pkgver"
    make DESTDIR="$pkgdir/" install
    echo "$PWD"
}

Nice catch!
This looks like an artifact of my attempt to force test plugins to be built and installed in the mptcpd/tests directory.  In tests/Makefile.am:
## Build a test mptcpd plugin.
##
## "check_LTLIBRARIES" can't be used here since a dynamically loadable
## module will not be built.  A Libtool convenience library would be
## built instead.
##
## Absolute path needed by Libtool during installation.
plugin_adir    = $(abs_builddir)/plugins_a
...
plugin_a_LTLIBRARIES = plugin_three.la plugin_four.la
...

The generated tests/Makefile ends up prepending $(DESTDIR) to the test plugin installation directories, which then causes them to be potentially installed outside of the mptcpd/tests directory when DESTDIR is set.  Ideally, the test plugins would only be built when running make check, but then we run into the problem described in the above Makefile.am snippet.  I'll see what I can do about this problem.  Thanks for the bug report!

thanks. I also had issues when trying to build from a dedicated build directory. simply mkdir build; cd build; configure ..; make will fail
I should open up a new issue for that, I guess

The dedicated build directory problem (VPATH build) was fixed by pull request #73 that was recently merged to the master branch.  Please give it a try if you get a chance.
I'm still reworking the plugin test infrastructure to address the original problem you reported.

mptcpd 0.5 was just released.  It fixes this problem.

repo: intel/mptcpd


text:
README.md: mention certificate installation in setup section

https://github.com/intel/pmem-csi#setup must mention that certificates must be created and installed.

if no-one yet working on this, I can create a PR based on recent email msgs on topic

source: gharchive/issue

authors: okartau pohly

repo: intel/pmem-CSI

license_type: permissive

license_source: github-api


text:
Deploying operator and the driver in non-default namespace

Deployment changes to run the operator and the driver in the non-default namespace. By default, the manifests deploy in 'pmem-csi' namespace. Also had to fix tests to support this change.
FIXES #785

"make test" failed. Please, remember to run that before submitting a change.

"make test" failed. Please, remember to run that before submitting a change.

I did run the make test and other operator tests quite enough times. But it didn't occur on my setup. It is only visible on a clean clone :(. Hopefully, I fixed it now.

It is only visible on a clean clone :(

Why was that? That sounds like an issue in our testing process that we may want to fix.

Something broke consistently in "switch device mode lvm-to-direct delete volume – fedora-1_17.operator.API": https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/organizations/jenkins/pmem-csi/detail/PR-829/2/tests
Dec 8 22:47:12.557: Giving up waiting for PMEM-CSI to start up, check the previous warnings and log output. Last error: get port for service lvm-to-direct-delete-volume-metrics in namespace default: services "lvm-to-direct-delete-volume-metrics" not found

Do we still get our pod output dumped when running E2E tests? Probably not, because https://github.com/intel/pmem-csi/blob/3e5744b93675b0b7aed231de8eb8b57bc1ca2454/test/e2e/e2e.go#L111-L121 is only watching the "default" namespace.
That should be changed, ideally so that it works for all test scenarios. We were missing the operator output already before when deployed in kube-system (a special case). That couldn't be avoided because watching everything in "kube-system" was too verbose (I tried), but at least "pmem-csi" and whatever other PMEM-CSI specific namespaces are used now should be doable.

Something broke consistently in "switch device mode lvm-to-direct delete volume – fedora-1_17.operator.API": https://cloudnative-k8sci.southcentralus.cloudapp.azure.com/blue/organizations/jenkins/pmem-csi/detail/PR-829/2/tests
Dec 8 22:47:12.557: Giving up waiting for PMEM-CSI to start up, check the previous warnings and log output. Last error: get port for service lvm-to-direct-delete-volume-metrics in namespace default: services "lvm-to-direct-delete-volume-metrics" not found

The issue is with the test itself it was waiting for the driver pods in the default namespace whereas the operator deployed in operator-test namespace.

I'm wondering whether version skew tests still work with this change. Have you tested that manually? Those tests don't run in pre-submit jobs.

is only watching the "default" namespace.
That should be changed, ideally so that it works for all test scenarios. We were missing the operator output already before when deployed in kube-system (a special case). That couldn't be avoided because watching everything in "kube-system" was too verbose (I tried), but at least "pmem-csi" and whatever other PMEM-CSI specific namespaces are used now should be doable.

Added the "operator-test" namespace to the watchlist, this is the namespace used by the operator tests.

I'm wondering whether version skew tests still work with this change. Have you tested that manually? Those tests don't run in pre-submit jobs.

@pohly How I can run them locally?

How I can run them locally?

make test_e2e TEST_E2E_FOCUS=skew

I'm wondering whether version skew tests still work with this change. Have you tested that manually? Those tests don't run in pre-submit jobs.

I tested version skew tests with this change locally. There was one issue discover about the driver certificates. In this change by default certificates are generated for the 'pmem-csi' namespace which are not usable for the driver running in default namespace.  I fixed this.
Except that I couldn't figure out any other issues.

source: gharchive/pull-request

authors: avalluri pohly

repo: intel/pmem-csi


text:
harmoni_bot roslaunch wants test args

roslaunch harmoni_bot harmoni_service.launch -- launching the service requires a test args which we no longer set/use

I should have fixed it in the testing-framework branch

repo: interaction-lab/HARMONI

license: MIT


text:
refactor!: rename interbtc to ibtc

Signed-off-by: Gregory Hill gregorydhill@outlook.com

Was the decision to rename to iBTC finalized?

repo: interlay/interbtc


text:
938/mk/create receiver

Changes proposed in this pull request

Adding CreateReceiver mutation to GraphQL admin API, which allows creating a remote (or local) incoming payment

Context

Fixes #938

Checklist

[x] Related issues linked using fixes #number
[x] Tests added/updated
[ ] Documentation added
[ ] Make sure that all checks pass

Will also update the Postman collection once this is merged in

repo: interledger/rafiki


text:
fix(style): video timecode hover

Breakdown
Let's break down this PR into 2 pieces, for react and twig. This separation is necessary because video components have drastically different implementations.
Twig
Twig component uses video.js for display, which has its own makeup for controls.

When we hover the button, duration is also styled because we are using the sibling(~) selector
&:hover,
&:focus {
  background-color: $color-ux-video-controls-hover-background;
  @include iconbutton(
    "play",
    $spacing-ux-video-bigplaybutton-height,
    $spacing-ux-video-bigplaybutton-width,
    $color-ux-video-controls-hover-icon
  );

  & ~ .vjs-duration,
  & ~ .ilo--video--controls--duration {
    background-color: $color-ux-video-controls-hover-background;
    color: $color-ux-video-controls-hover-icon;
  }

but when we want to invert the behavior we can't use the sibling selector because the button is on top of duration  and sibling selectors can't select items above it

The subsequent-sibling combinator (~) separates two selectors and matches all instances of the second element that follow the first element (not necessarily immediately) and share the same parent element.

Because of that we have Javascript implementation that listens to mouseover and mouseout on duration element and attaches hovered class to the button.
Demo
https://github.com/international-labour-organization/designsystem/assets/36326203/48eb65b1-f4dd-470a-a3c4-13b1e06421f0
For implementation details, the Video class has the function cacheDomReferences but the current implementation is using cacheVideoReferences because of this chain
init() {
  this.cacheDomReferences()
    .start()
    .cacheVideoReferences()
    .setupHandlers()
    .enable();

  return this;
}

We can't find dom references for video.js until it's instantiated.
a11y
Since button element is first and it's tab indexed there is no problem for keyboard a11y
https://github.com/international-labour-organization/designsystem/assets/36326203/80f05f67-d728-4afd-905c-c7a7740874a2

React
The current react implementation has no implementation for this feature at all, so I included that one too.
Current
https://github.com/international-labour-organization/designsystem/assets/36326203/1ed2dd8f-1319-4f7e-a87c-0addc5625b87
Fixed
https://github.com/international-labour-organization/designsystem/assets/36326203/60fa0434-78f0-43f4-9ff6-94fa42a93a5f
but on the react side everything is upside down compared to Twig, I mean that controls are reversed
<>
  <label
    className={`${controlsClasses}--duration ${showposter ? "show" : ""}`}
  >
    {duration}
  </label>
  <button
    className={`${controlsClasses}--${!playing ? "play" : "pause"}`}
    onClick={togglePlay}
  >
    <span>
      {!playing ? controls && controls.play : controls && controls.pause}
    </span>
  </button>
</>

so without breaking an old implementation, the initial flow was done by a sibling selector but reversed, and the problematic part was done with the same behavior as the Twig one.
For implementation details, I'm handling mouseover and mouseout directly on the button without controlling the hover effect with state, because there is no need to bring extra rerenders for the hover effect, since the application logic does not need it
a11y
Since the button element is the second one we also handling onFocus and onBlur for keyboard navigation
https://github.com/international-labour-organization/designsystem/assets/36326203/18f4885d-bf54-4e6c-b2d8-2fbed58f8758
Closing #521

Great work on this @GGKapanadze , I see that it was really tricky given the different implementations across twig and react. I don't like that we have to resort to JS to mend this, it adds a lot of complexity to the component.
Just an idea, but what if we add a custom hover class to each of these elements (e.g. .hover-group) and then handle the hover on the parent element to apply styles to this hover class? (e.g. .parent:hover > .hover-group)

Before the JS solution, I tried the grouping strategy as you mentioned, but there were sizing problems.
React

On a smaller screen the video wrapper is spanned at full width so hovering will behave unexpectedly

https://github.com/international-labour-organization/designsystem/assets/36326203/89fee314-6e3e-4c11-a700-fee477338dd9
But it can be fixed by either reworking the markup a bit or managing the width with CSS
Twig

Default size wrapper is higher than necessary elements

https://github.com/international-labour-organization/designsystem/assets/36326203/0ed18f47-22c2-4e5d-8d5f-c84c08fa397b

The Responsive version behaves the es same way as the react

https://github.com/international-labour-organization/designsystem/assets/36326203/7fd38ff1-e1cb-47c5-b8f9-aaa190e69c82
These issues are fixable without JS but it will be a bit clanky because the wrapper contains not only duration and play a button and we have to size them properly, so I decided to go with a bit future-proof solution but I agree about complexity concerns.

Do you want me to go with the CSS approach and then discuss which one fits our needs @bashlk ?

Hey @bashlk, I think @GGKapanadze's solution is fine. Like the description says, the Video component is one of just a few that have completely different JS implementations in React and Twig, as long as they're still using the same CSS classes I'm ok with it.

authors: GGKapanadze bashlk justintemps


text:
ICM: Enable dynamic environment keyvault secret exchange for customer projects

E.g.:
environmentsFromProjectSecrets:
- datadogLabel
- ebayKey

and
{{- range .Values.environmentsFromProjectSecrets }}
- name: {{.}}
  valueFrom:
    secretKeyRef:
      name: project-secrets
      key: {{.}}
{{- end -}}

This issue is connected to our internal infrastructure deployment (see #93578).

Closed this ticket as it's possible with #550

repo: intershop/helm-charts


text:
Order history enhancements

Order history is missing the following features:

order list: search/filtering by date range, orderno, status, productno
order details: add2cart button
currently order history is visible for the current user only. Optional configuration in backoffice to display order history for all users of the current customer

AB#89758

order list: search/filtering by date range, orderno, status, productno - implemented with #1571

order details: add2cart button - implemented with #1592

order history for all users of the current customer - the REST API for this feature will be available with ICM 12.1.0 and the functionality will be implemented in the PWA, the feature will be available based on a certain permission of the currently logged in user

authors: shauke ximmw

repo: intershop/intershop-pwa


text:
🛑 Bonnefanten is down

In a1ecde4, Bonnefanten (https://www.bonnefanten.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bonnefanten is back up in d3c3cc0 after 7 minutes.

repo: intk/intk-upptime


text:
Whole numbers in initial step size

For variable step sizes, if you set an initial step that's a whole number, the COE dies with initsize is not a double. This happens even if you use say 1.0. Is this restriction legitimate or an error? Seems like an error.
In any case, the simulation just hangs at 50%. It should switch to failed.
ERROR [NanoHttpd Request Processor (#1)] (RequestProcessors.java:201) - initsize is not a double
Oct 05, 2016 4:10:32 PM fi.iki.elonen.NanoHTTPD$DefaultTempFileManager clear
WARNING: could not delete file
java.lang.Exception: could not delete temporary file
        at fi.iki.elonen.NanoHTTPD$DefaultTempFile.delete(NanoHTTPD.java:403)
        at fi.iki.elonen.NanoHTTPD$DefaultTempFileManager.clear(NanoHTTPD.java:446)
        at fi.iki.elonen.NanoHTTPD$HTTPSession.execute(NanoHTTPD.java:964)
        at fi.iki.elonen.NanoHTTPD$ClientHandler.run(NanoHTTPD.java:192)
        at java.lang.Thread.run(Unknown Source)

fixed in release contained in 0.0.9

authors: lausdahl ldcouto

repo: into-cps/intocps-ui

license: mit

license_source: bigquery


text:
Add support for sharing karate variables across gatling scenarios as is.

Description
Currently, while using karate-gatling, there is no way to pass variables from one karate feature to another.
This implies that today, a new feature would have to be written for performance tests and the power of gatling cannot be fully utilised.
In this PR, by introducing __karate as temporary key in gatling session to carry over the variables post result of one karateFeature execution onto another.

Relevant Issues : https://github.com/intuit/karate/issues/1612
Type of change :

[x] New feature
[ ] Bug fix for existing feature
[ ] Code quality improvement
[ ] Addition or Improvement of tests
[ ] Addition or Improvement of documentation

@abhi-rao this is good stuff, thanks !
in case @theathlete3141 and @douglas-six are listening, can you take a look once, thanks !

authors: abhi-rao ptrthomas

repo: intuit/karate


text:
🛑 Console Web is down

In 98822c6, Console Web (https://console.inu-cafeteria.app) was down:

HTTP code: 500
Response time: 3103 ms

Resolved: Console Web is back up in b3ff957.

repo: inu-appcenter/cafeteria-status


text:
custom fields: ensure mapping compatibility with OpenSearch

The mapping property of the CF classes is returning a dictionary with the ES configuration. However, the backend can change in the future (e.g. to OpenSearch). Adding a layer of abstration would provide transparent compatibility.
This layer would mean having e.g. Keyword, Text classes. This could be hosted in invenio-search provided they don't exist in elasticsearch-dsl, elasticsearch-py or the corresponding amazon forks.

PR https://github.com/inveniosoftware/invenio-records-resources/pull/372

Regarding the TextCF:

why not always adding the keyword by default?
There is also this ignore_above which might be useful...

See https://github.com/inveniosoftware/invenio-records-resources/pull/377#discussion_r949996829

This was implemented.


text:
global: v3.3 final release

Make the final v3.3 release

closed by #4013

authors: lnielsen ppanero

repo: inveniosoftware/invenio


text:
Bug: i18next scanner

i18next scanner - has some issue while extracting messages only if the strings are marked with Trans component.
the issue is that it passes the key to values for other languages rather than only to eng language.
Originally posted by @mb-wali in https://github.com/inveniosoftware/react-invenio-deposit/issues/345#issuecomment-882636917

Related issue https://github.com/i18next/i18next-scanner/issues/187

see https://github.com/inveniosoftware/react-invenio-deposit/issues/591

authors: mb-wali rekt-hard zzacharo

repo: inveniosoftware/react-invenio-deposit


text:
invoke update failing with error

Please verify that this bug has NOT been raised before.

[X] I checked and didn't find a similar issue

Describe the bug*
I'm running a version that is a few weeks old. Did a sync to github and trying to invoke update and getting a error:
inventree@inventree:~/src$ invoke update
Traceback (most recent call last):
  File "/usr/bin/invoke", line 11, in <module>
    load_entry_point('invoke==1.4.1', 'console_scripts', 'invoke')()
  File "/usr/lib/python3/dist-packages/invoke/program.py", line 373, in run
    self.parse_collection()
  File "/usr/lib/python3/dist-packages/invoke/program.py", line 465, in parse_collection
    self.load_collection()
  File "/usr/lib/python3/dist-packages/invoke/program.py", line 696, in load_collection
    module, parent = loader.load(coll_name)
  File "/usr/lib/python3/dist-packages/invoke/loader.py", line 76, in load
    module = imp.load_module(name, fd, path, desc)
  File "/usr/lib/python3.10/imp.py", line 235, in load_module
    return load_source(name, filename, file)
  File "/usr/lib/python3.10/imp.py", line 172, in load_source
    module = _load(spec)
  File "<frozen importlib._bootstrap>", line 719, in _load
  File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
  File "<frozen importlib._bootstrap_external>", line 883, in exec_module
  File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
  File "/home/inventree/src/tasks.py", line 326, in <module>
    def update(c, skip_backup=False, no_frontend: bool = False, frontend: bool = False):
  File "/usr/lib/python3/dist-packages/invoke/tasks.py", line 338, in inner
    obj = klass(
  File "/usr/lib/python3/dist-packages/invoke/tasks.py", line 76, in __init__
    self.positional = self.fill_implicit_positionals(positional)
  File "/usr/lib/python3/dist-packages/invoke/tasks.py", line 167, in fill_implicit_positionals
    args, spec_dict = self.argspec(self.body)
  File "/usr/lib/python3/dist-packages/invoke/tasks.py", line 153, in argspec
    spec = inspect.getargspec(func)
  File "/usr/lib/python3.10/inspect.py", line 1245, in getargspec
    raise ValueError("Function has keyword-only parameters or annotations"
ValueError: Function has keyword-only parameters or annotations, use inspect.signature() API which can support them

Steps to Reproduce

git pull origin master

inventree@inventree:~/src$ git log -1
commit 4e0f22aa00d92638ef69372d4afe4b9ad661301a (HEAD -> master, origin/master, origin/HEAD)
Run invoke update
Expected behaviour
invoke update should upgrade the version.
Deployment Method

[ ] Docker
[X] Bare metal

Version Information
Version Information:
InvenTree-Version: 0.13.0 dev
Django Version: 3.2.20
Commit Hash: 370021b
Commit Date: 15/07/2023
Commit Branch: master
Database: mysql
Debug-Mode: True
Deployed using Docker: False
Platform: Linux-5.15.0-76-generic-x86_64-with-glibc2.35
Installer: GIT
Active plugins: False
Please verify if you can reproduce this bug on the demo site.

[ ] I can reproduce this bug on the demo site.

Relevant log output
No response

Hello @StormTrooper ,
which version of invoke do you have installed? You could check that via pip freeze | grep invoke. Maybe this is related: https://github.com/pyinvoke/invoke/issues/357

inventree@inventree:~/src$ pip freeze | grep invoke
invoke==1.4.1

Thanks, will look into the link

Looks like invoke 1.4.1 is the latest on Ubuntu 23.04
Downloaded 2.2.0 from source and manually installed. This has fixed the issue.

I've run into the same issue and I can confirm that
pip install --upgrade invoke
solved the issue for me.

authors: Kedarius StormTrooper wolflu05

repo: inventree/InvenTree


text:
fix: make protected setting again changeable through admin ui

#5229 hides the settings completely from admin ui and also disables the button to change it. This PR adds the change button back, but still hides the settings value.

Nice work thanks


text:
[bug]: Can't access webui from iPhone

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
cuda
VRAM
24GB
What version did you experience this issue on?
latest
What happened?
I can run the webui just fine on my Windows11 machine, but after editing the yaml file and changeing to host 0.0.0.0 and port forwarding allowing 9090.
But still the page in my phone wont load.
In automatic1111 for example it does work.
What more can be done?
Screenshots
No response
Additional context
No response
Contact Details
No response

Anyone? :O

Have you tried asking in the Discord? There's multiple folks who have it setup successfully

Are the PC and the iphone in the same network. (Not all Router let the wifi devices talk to cable devices)
allow_origins needs to be set right (IP or *)

authors: Millu Pfannkuchensack iChristGit

repo: invoke-ai/InvokeAI


text:
WIP Seamless Implementation

What type of PR is this? (check all applicable)

[ ] Refactor
[ X ] Feature
[ ] Bug Fix
[ ] Optimization
[ ] Documentation Update
[ ] Community Node Submission

Have you discussed this change with the InvokeAI team?

[ X ] Yes
[ ] No, because:

Have you updated all relevant documentation?

[ ] Yes
[ X ] No

Description
Adds Seamless back into the options for Denoising.
Related Tickets & Documents

Related Issue #3975

QA Instructions, Screenshots, Recordings

Should test X, Y, and XY seamless tiling for all model architectures.

Added/updated tests?

[ ] Yes
[ X ] No : Will need some guidance on automating this.

Huge thanks to @StAlKeR7779 for helping me with porting some of the tricky stuff into a LoRA compatible post Torch 2.0 update.
Tested and working in both a SD 1.5 + LoRA and SDXL + LoRA graph. Have not tested with Refiner.


text:
🛑 SharePic is down

In 7c741e6, SharePic (https://sharepic.eu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SharePic is back up in b07e4ea after 32 minutes.

repo: involve-gmbh/upptime


text:
🛑 Bitwage API (Sandbox) is down

In 8662437, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 265 ms

Resolved: Bitwage API (Sandbox) is back up in e2be6c7 after 13 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In 5bb7292, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 268 ms

Resolved: Bitwage API (Sandbox) is back up in a0587a4 after 31 minutes.


text:
🛑 Bitwage API (Sandbox) is down

In 108498b, Bitwage API (Sandbox) (https://api.sandbox.bitwage.com) was down:

HTTP code: 403
Response time: 247 ms

Resolved: Bitwage API (Sandbox) is back up in 537a067 after 20 minutes.


text:
Provide a shared ESLint config

Separate for JS/TS
https://eslint.org/docs/developer-guide/shareable-configs

When implementing, please have a look at ioBroker/create-adapter#569, so we don't forget anything.

Looks like this isn't necessary anymore as there is "@iobroker/eslint-config"

right

authors: AlCalzone Apollon77 UncleSamSwiss hombach

repo: ioBroker/adapter-dev


text:
Improved validation of fontsize keys

This PR addresses an issue raised in #291.
There it was pointed out that there is no warning when an invalid fontsize key is supplied and such a warning could help users discover which keys are valid.

I think this is ready for merging now.

repo: ioam/holoviews


text:
Adapter funktioniert nach kurzer Zeit nicht mehr.

Hallo!
Ich habe folgendes Problem: Wenn ich den Adapter neu Starte dann scheint alles zu funktionieren, aber nach ein paar Stunden werden die states nicht mehr aktualisiert (Adapter Zeigt weiterhin grün), als würde keine Verbindung zum AVR mehr bestehen. Der AVR hat aber dauerhaft Verbindung zum Netzwerk (habe einen Ping über mehrere Stunden laufen lassen).
Die Verwendete Adapterversion ist: 0.5.3
Yamaha AVR: RX-V1071
Node.js Version: 14.21.3
js-controller: 4.0.24
Falls weitere Infos benötigt werden lasst es mich bitte Wissen (ist mein erster Issue den ich erstelle :-)).
Würde mich sehr freuen wenn das Problem behoben werden könnte :-)
mfg Markus

Bitte Loglevel auf Debug stellen, mitlaufen lassen und ab da wo es nicht mehr geht mal log posten (und vllt bissl davor)

Abend!
Hier jetzt also das Log, hat nicht all zu lange gedauert bis es nicht mehr Funktioniert hat. bei Zeile 14 hat es trotz das da etwas von Connection Closed steht noch funktioniert, dann habe ich eine weile gewartet und dann ging es wieder nicht.
https://pastebin.com/8Nk06iVy
Mfg Markus

Was passiert, wenn du versuchst etwas an den AVR zu senden (also irgendwas schalten), wenn states nicht mehr aktualisiert werden?

Senden scheint momentan zu funktionieren, allerdings meine ich das ging auch mal nicht, da bin ich mir aber nicht zu 100% sicher! Jedenfalls kann ich den AVR, aktuell, per ioBroker einschalten, aber die states das er auch an ist, oder sich sonst was ändert, werden nicht aktualisiert.

gibts auch ein Log von so einem szenario? Und was heisst (zum log oben "nach einiger zeit"? Wäre geil mit Uhr zeiten aus dem log zu kombinieren :-)


text:
IE11 Alert Prompt not working

Ionic version:  (check one with "x")
[ ] 1.x (For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

Any alerts with prompt do not open on IE11.
Expected behavior:

Prompts open on IE11
Steps to reproduce:

Open the official doc under http://ionicframework.com/docs/components/#alert-prompt in IE11. Click then the "Show Prompt Alert" button.

I found out, if you provide the type, the error is gone in IE11:
            inputs: [
                {
                    type: 'text',
                    name: 'description',
                    value: attachment.meta.description,
                    placeholder: ''
                },
            ],

Hello! Thanks for using Ionic! At this time we do not officially support IE11.

repo: ionic-team/ionic


text:
[4.0.0-beta.13] ion-reorder-group/ion-reorder: buggy list after item is dropped

Bug Report
Ionic Info
Ionic:

   ionic (Ionic CLI)             : 4.2.1 (/usr/local/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 4.0.0-beta.13
   @angular-devkit/build-angular : 0.10.2
   @angular-devkit/schematics    : 7.0.2
   @angular/cli                  : 7.0.2
   @ionic/angular-toolkit        : 1.0.0

Cordova:

   cordova (Cordova CLI) : 8.0.0
   Cordova Platforms     : ios 4.5.5
   Cordova Plugins       : cordova-plugin-ionic 5.2.5, cordova-plugin-ionic-keyboard 2.1.3, cordova-plugin-ionic-webview 2.2.0, (and 11 other plugins)

System:

   ios-deploy : 2.0.0
   ios-sim    : 7.0.0
   NodeJS     : v10.12.0 (/usr/local/Cellar/node/9.11.1/bin/node)
   npm        : 6.4.1
   OS         : macOS
   Xcode      : Xcode 10.0 Build version 10A255

Describe the Bug
When I drag an  element and drop it (within the ) the  view gets messed up/buggy.
Before interaction:

After (drag &) dropping an item:

Steps to Reproduce
Steps to reproduce the behavior:

make basic re-ordable list
drag & drop an item
See messed up list view

NO ERRORS ARE THROWN DURING THESE ACTIONS
Related Code
html code:
<ion-content>
  <ion-list>
        <ion-list-header>
            <ion-label>INCLUDE</ion-label>
        </ion-list-header>
        <ion-reorder-group (ionItemReorder)="reorder($event)" [disabled]="false">
            <ion-item *ngFor="let accessory of accessories">
                <ion-label>{{accessory}}</ion-label>
                <ion-reorder></ion-reorder>
            </ion-item>
        </ion-reorder-group>
   </ion-list>
</ion-content>

typescript code:
 accessories = ['test', 'test1', 'test2'];

reorder(event) {
        const itemToMove = this.accessories.splice(event.detail.from, 1)[0];
        this.accessories.splice(event.detail.to, 0, itemToMove);
    }

Expected Behavior
no messed up view

i face the same issue with use broswer to test the feature.

after i drag & drop

and the items can't dragged anymore

@gentleen @GillesMontyne You have to complete reordering by calling complete on ReorderGroup instance. Read the docs:
https://github.com/ionic-team/ionic/tree/master/core/src/components/reorder-group
Once the data structure has been updated to reflect the reorder change, the complete() method must be called. This method finishes the reorder operation and resets all the CSS transforms applied by the ion-reorder-group component.

thx, this solved my issue!

@gentleen @GillesMontyne You have to complete reordering by calling complete on ReorderGroup instance. Read the docs:
https://github.com/ionic-team/ionic/tree/master/core/src/components/reorder-group
Once the data structure has been updated to reflect the reorder change, the complete() method must be called. This method finishes the reorder operation and resets all the CSS transforms applied by the ion-reorder-group component.

Should this not moved to the ionic Doku beta page?

@TrayserCassa It should and I guess that it will be... but can't tell why it is not present in docs website. @brandyscarney ?

We will have the API documentation updated soon. It hasn't been deployed since beta.11 so it is out of sync with the current API reference. I created an issue for the description being cut off: https://github.com/ionic-team/ionic-docs/issues/160
In the future if you see any issues with documentation (outdated, incomplete, etc.) please create an issue on the ionic-docs repository. Thank you!

Hi @brandyscarney!
The example in the doc is freezing when the element is dropped. The page says 4.0.0-beta.15.

Same here.  I get an error:  reorder node not found and it freezes

Resolved.   Add  implements OnInit to my page component.  Then added the reorder event listener.  All good now.

@yuricamara

Zitat:
In the future if you see any issues with documentation (outdated, incomplete, etc.) please create an issue on the ionic-docs repository. Thank you!

This is the wrong issue tracker for doc errors ...

@TrayserCassa , thank you for your advice but this was NOT about doc. I was talking about an official example by chance in the doc.

Thanks, @brandyscarney

authors: GillesMontyne TrayserCassa brandyscarney emgould gentleen mmlleevvyy yuricamara


text:
docs: contributing for v4 - Fixes #16672

Short description of what this resolves:
contributing for ionic v4 changed a lot of things, so I tried my best. Someone should check it or should make changes to it if everything is explained wrong
Ionic Version:
Fixes: #16672

@brandyscarney nice, I have nothing to add :)


text:
fix(buttons): use theme toolbar colors for default iOS buttons

Pull request checklist
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been reviewed and added / updated if needed (for bug fixes / features)
[x] Build (npm run build) was run locally and any changes were pushed
[x] Lint (npm run lint) has passed locally and any fixes were made for failures

Pull request type

Please check the type of change your PR introduces:

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Codepen reproducing the problem: https://codepen.io/brandyscarney/pen/VNoPNj?editors=0110
Issue Number: #18184 and #17840
What is the new behavior?

Updates the iOS buttons in a toolbar to use the proper global theming variables
Fixes the iOS segment to use the correct background variable when checked
Fixes the iOS back button to use the proper color in a toolbar

Does this introduce a breaking change?

[ ] Yes
[x] No

Other information
Fixes #18184, fixes #17840
The iOS buttons were not using the global theme variables that the material design buttons did use. So in the conference app, for example, if you applied the same global theme variables as md is using, it wouldn't work in iOS. Here's a before & after of this with the following custom variables:
:root {
  /* Custom Toolbar CSS (optional) */
  --ion-toolbar-background: #000;
  --ion-toolbar-border-color: #333;
  --ion-toolbar-color: limegreen;
  --ion-toolbar-color-activated: rgb(35, 156, 35);
}

/* Customize the Toolbar Segment by Mode */
.ios {
  --ion-toolbar-color-unchecked: limegreen;
  --ion-toolbar-color-checked: limegreen;
}

.md {
  --ion-toolbar-color-unchecked: rgba(255, 255, 255, .6);
  --ion-toolbar-color-checked: #fff;
}

Note that this also has a ton of other custom variables above it for the background/texts.
master:

branch:

I found some issues with the toolbar colors that exist on master that I am looking into.

This should be good to go now!


text:
fix(input): add ng-touched to valid highlights

Short description of what this resolves:
Prevents valid highlights from showing until inputs are touched.
Changes proposed in this pull request:

add .ng-touched to $text-input-{PLATFORM}-show-valid-highlight

Ionic Version: 2.x
Fixes: #8826

Hello and thank you for contributing to Ionic! We have been working on porting all of the Ionic components to web components and have recently updated master to reflect this. This significant change has caused this pull request to break. While we really appreciate the time and effort you put into creating this, we are not able to merge it because of the newly introduced conflicts. We are extremely sorry about this. We will not be merging any more features in to v3. If this is a feature and you have the time, please resubmit this PR against the master branch. If this is a critical security issue in v3, we would greatly appreciate it if you would resubmit the PR against the new v3 branch. Thanks so much for your time!

authors: Ionitron patrickmcd


text:
when conf & unconf same tx cant blind outputs

How to replicate
yarn test ./test/e2e/syntheticAsset.test.ts

It fails with TypeError: key must be a Buffer of 32 bytes
basically what happens is that inside maybeUnblindInUtxos triggered by blindOutputs when an input is uncofidential the asset being pushed is 33 bytes instead of 32 (ie. prefix still on),
Any reason why we do not strip the prefix? @louisinger @altafan
From https://github.com/vulpemventures/liquidjs-lib/blob/master/ts_src/psetv2/zkp.ts#L536-L554
if (this.ownedInputs && this.ownedInputs.length > 0) {
      return pset.inputs.map((input, i) => {
        const ownedInput = this.ownedInputs.find(({ index }) => index === i);
        if (ownedInput) {
          console.log('ownedInput at index ' + i, ownedInput);
          return {
            value: '',
            valueBlindingFactor: Buffer.from([]),
            asset: ownedInput.asset,
            assetBlindingFactor: ownedInput.assetBlindingFactor,
          };
        }
        console.log('non blinded input at index ' + i, input.getUtxo().asset.length)
        return {
          value: '',
          valueBlindingFactor: Buffer.from([]),
          asset: input.getUtxo().asset,
          assetBlindingFactor: transaction_1.ZERO,
        };
      });
    }

@tiero I'm not able to replicate,everything looks good to me (unchanged yarn.lock and node v16).

now Error: Invalid output asset surjection proof cc/ @louisinger @altafan

authors: louisinger tiero

repo: ionio-lang/ionio


text:
After graduation

Μετά το Πτυχίο
Πάτρικ Βάις
Π2014090

excerpt?

authors: PatrykWajs epidrome


text:
[Task]: Line at the bottom does not match the box

Task description
The bottom line on the landing page doesn't match the box width. They should be of the same size.

Requirements
The width of line should match the box width.
Acceptance criteria
N/A
Creation checklist

[ ] I have assigned this task to the correct people
[X] I have added the most appropriate labels
[X] I have linked the correct milestone and/or project

Couldn't be reproduced on latest build.

authors: laumair msarcev

repo: iotaledger/explorer


text:
Remove dependency on identity_core default features

Description of change
identity_did and identity_document depend on identity_core but do not turn off default features. This means that these crates cannot be compiled for wasm32-unknown-unknown without a dependency on js-sys.
Given the default features are not required, removing them makes these crates compatible across a wider range of compilation targets.
Type of change
Add an x to the boxes that are relevant to your changes.

[ ] Bug fix (a non-breaking change which fixes an issue)
[x] Enhancement (a non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Fix

How the change has been tested
Existing test suite.
Change checklist
Add an x to the boxes that are relevant to your changes.

[x] I have followed the contribution guidelines for this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

@itsyaasir: There are other features that we need (e.g. #1406) but in terms of compiling the library (at least the crates that we currently use) such that it works on the ICP platform, I can confirm that it works.
Thanks.

@itsyaasir: Could this be merged?


text:
Add vByteFactorDelegation to RentStructure

https://github.com/iotaledger/tips-draft/pull/24/files/51c445ef58ae9610de2d8c38c7f68380405ff5e1..93227c50259fdc413b1beaec56c35360a14a3efb

Closed by https://github.com/iotaledger/iota-sdk/pull/1195

repo: iotaledger/iota-sdk


text:
Add alias transition examples

Description of change
Add alias transition examples
Links to any relevant issues
Closes #1084
Type of change

Documentation enhancement

How the change has been tested
Running the examples

Why would we? It's only examples


text:
🛑 备用KMS激活服务器 01 is down

In 5aa485c, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in 8e7883e after 43 minutes.

repo: iougemini/ikms-uptime


text:
🛑 备用KMS激活服务器 01 is down

In e6898ee, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in 61bea4a after 9 minutes.


text:
🛑 备用KMS激活服务器 01 is down

In 8ce9faf, 备用KMS激活服务器 01 (s11.ikms.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: 备用KMS激活服务器 01 is back up in 1cd76b5 after 18 minutes.


text:
Save Multiple Connections

As @diasdavid suggested, we should support having a list of connection options where we can just switch from one to another.

Is this about switching between different IPFS backends (eg. local go-ipfs, embedded js-ipfs, remote HTTP API, etc) ?
If so,  we plan to add similar feature to Companion (https://github.com/ipfs-shipyard/ipfs-companion/issues/491).
cc @fsdiogo  to keep everyone in the loop so our UIs do not drift too far apart :)

Yup @lidel

also look at https://github.com/RHazDev/IPFS-Manager/releases .
His manager allows for creating multiple peerIDs on the fly,
adding files and easily publishing to any peerID

authors: hacdias lidel roscoevanderboom

repo: ipfs-shipyard/ipfs-desktop


text:
Interface for files.add

Builds on top of https://github.com/ipfs/interface-ipfs-core/pull/20
Adds

[x] Fix aegir setup (rename test->src so that it is buildable
[x] Stop using require(raw! (the right module was not being loaded, broke all browser tests, we don't need it anyway)
[x] Stop requiring fs on demand per test, breaks webpack too

Thanks for taking this the last mile, @diasdavid.
:horse: LGTM, other than my one comment.

authors: diasdavid noffle

repo: ipfs/interface-ipfs-core


text:
Include all repos (not just 100)

Load all repos (at max 100 per page), recursively loading until no more pages.
Fixes #59.
I tried this with 100 per page and 10 per page, and in both cases we get 108 repos.  (Manual sanity check passes.)
Diff will make more sense after #78 is merged.

This looks good to me. Merge?

authors: RichardLitt harlantwood

repo: ipfs/project-repos


text:
bug

提个不定性bug   有时单击返回时，界面退出不了，怎么解决，这个情况不是每次都出现 ，还有的时候 ，图片有很多时，比如到第四张图片，单击返回，直接返回到第一张，不退出界面，有时候连图都不显示，全黑

@77521  加我QQ 备注:#66

你QQ多少啊

499491531


text:
[feature] Command to show quota. (possible using the /me endpoint)

Sometime ago, I used the /me EP to validate the token during auth. The /me EP actually returns usefull quota information, but at this point it is not used.
I propose a command that displays the quota information.
$ ipinfo quota

Requests
Day: 0,
Month: 9,
Limit: 50000,
Remaining: 49991

"features": {
    "core": {
      "daily": 2147483647,
      "monthly": 50000
    },
    "hostio": {
      "daily": 2147483647,
      "monthly": 1000,
      "result_limit": 5
    }
  }

Or something similar. The design is pending.

Yeah a quota subcommand would be nice. But we probably need a different endpoint for this as the existing one gives potentially confusing data, like when it says limit/remaining, what does that mean - is that for core, asn, or what?
I'll figure smth out for this later, thanks for the suggestion!

@UmanShahzad  I have this proposal:
Either allow parameters in the quoata command to let the user choose WHAT to use, or default to core

Solved in #131

authors: UmanShahzad eacp rm-Umar

repo: ipinfo/cli


text:
🛑 NowBoarding (tokyo) is down

In e2ef5ab, NowBoarding (tokyo) (https://tokyo.nowboarding.club/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NowBoarding (tokyo) is back up in bb7ae78 after 25 minutes.

repo: iplanwebsites/up


text:
🛑 NowBoarding (tokyo) is down

In 70f438d, NowBoarding (tokyo) (https://tokyo.nowboarding.club/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NowBoarding (tokyo) is back up in 7b61924 after 15 minutes.


text:
Support for Git and Bitcoin

Currently, the js implementation is missing git and Bitcoin support to match the go-ipfs implementation

http://ipld.io/implementations/
We will get to this at some point, however, if there is someone in the community that would like to take on that task right now, it would be really appreciated! Let me know if you need help getting started :)

Supporting Git isn't that easy, there is quite a bit of delicate parsing there. @magik6k who implemented Go's support for git might be of help.

@magik6k would you like to tackle this one?

Sure, might have a look at that

@magik6k awesome work adding support for Git in JS land <3

[x] Git thanks to @magik6k 👏🏽 ✅
[ ] Missing Bitcoin

authors: Kubuxu diasdavid magik6k

repo: ipld/js-ipld-resolver


text:
Edit: Russian night HD

Channel ID (required)
RussiannightHD.ru
Channel Name
No response
Alternative Names
No response
Network
No response
Owners
No response
Country
No response
Subdivision
No response
City
No response
Broadcast Area
No response
Languages
No response
Categories
No response
NSFW
None
Launched
No response
Closed
No response
Replaced By
No response
Website
No response
Logo
No response
Notes
No response

__

03446725753

03446725753

03446725753

repo: iptv-org/database

license: Unlicense


text:
Add CableGO EPG

This EPG service is for peruvian channels.
Source:
https://cablego.com.pe/epg
(for some peruvian channels only see: https://cablego.com.pe/epg?category=NACIONALREGIONA)
Channels:

BHTV.pe
PBO.pe
Conecta2TV.pe
ExitosaTV.pe
USMPTV.pe
Nativa.pe
CongresoTV.pe
Karibena.pe
OvacionTV.pe

Added.

authors: freearhey sguinetti

repo: iptv-org/epg


text:
🛑 iTa'LeEM Cloud is down

In 8e6d975, iTa'LeEM Cloud (https://italeemc.iium.edu.my) was down:

HTTP code: 502
Response time: 612 ms

Resolved: iTa'LeEM Cloud is back up in a4b2619 after 27 minutes.

repo: iqfareez/iium-services-status


text:
build subcommand verbose print topdir arg should a quote

current verbose print is

Running rpmbuild -ba SPECS/a.spec -D _topdir /home/w/repos/temp/a/target/release/rpmbuild -D _tmppath /home/w/repos/temp/a/target/release/rpmbuild/tmp

when I copy this command run again get error: Macro %_topdir has empty body
the arg should print to -D '_topdir /home/w/repos/temp/a/target/release/rpmbuild' with quote to include whitespace
https://github.com/iqlusioninc/cargo-rpm/blob/ca2f28d012529914c59a1cc93edfd059bf294e21/src/builder.rs#L357
current code use join to concat args can improve?

cargo-rpm is unmaintained: #96

authors: pymongo tony-iqlusion

repo: iqlusioninc/cargo-rpm


text:
Add curve graph and graph image in README.md

Add new graph

CurvePlotItem

Update README.md

Add new graph images
Split issues for windows, macOS
Some decoration

Revise some grammar and words.
Add /img dir for graph images.

Looks good!

repo: irahorecka/visuaudio


text:
Compute workgroup count based on pack op input shape, not result shape.

This is part 4/9 of https://github.com/iree-org/iree/issues/11755: Finish the transition to --iree-flow-enable-data-tiling.
The workgroup count computation should not care about the inner (register-level) tile sizes. But the result shape outer dims of a pack op depend on tile sizes (they are the quotient of the input shape by tile shape).
With the newly added possibility of dynamic tile sizes, this code had gotten complicated as the workgroup count computation had to call the query_tile_sizes ukernel.
Finally the last straw was that we realized that since that is host-side not device-side work, that was the one place introducing a host-side dependency on the VMVX module providing the query_tile_size ukernel, so that was why we suddenly needed either #11643 or #11644.
So this PR not only removes the need for #11643 and #11644, it removes an unnessary tangling of device details into host code and removes > 50 lines of nontrivial code from TileAndDistributeToWorkgroupsPass.
The only downside is that since the input shape is larger than the outer dims of result shape that were being used, this is increasing the number of workgroups, so we may want to adjust that in a follow-up?  But was the current workgroup count determination any optimized anyway?

But was the current workgroup count determination any optimized anyway?

given that I still see lots of cases of 2000x 1us workgroups for some things and 4x 1ms workgroups for others makes me think that there hasn't been much optimization done there, so I'm ok with this change - it'll at least have the right order of magnitude :)

Superseded by #11819 .  Followup discussion in #11818 .

But was the current workgroup count determination any optimized anyway?

It was done to the best of the abilities of people involved were, for the cases that were looked at. It is optimized for some cases, but it doesnt work all the time. More help on what this should be would be very welcome.

authors: MaheshRavishankar benvanik bjacob

repo: iree-org/iree


text:
[CPU][ArmSME] Update tiling to use all SME accumulators

Previously, we only tiled for a single SME accumulator. This patch updates the lowering_config to make use of all SME accumulators.
This is done by increasing the tile size to [8]x[8] for f32 and to [4]x[8] for f64. This lowers to four [4]x[4] 32-bit accumulators and eight [2]x[2] 64-bit accumulators respectively.
Signed-off-by: Benjamin Maxwell benjamin.maxwell@arm.com
ci-extra: build_test_all_arm64

cc @c-rhodes

Note: This patch now needs a fix upstream due to #16350 (we need to legalize arith.constants), should be a simple fix but I'll have to wait until the next LLVM integration.

@hanhanW, @MaheshRavishankar if this looks okay, could we land this today? :pray:
P.s. I don't have write access.


text:
ms_readtracelist doest not populate datasamples

The program:
#include <errno.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <time.h>

#include <libmseed.h>

int main (int argc, char **argv) {

    int retcode;

    int32_t trace_number;
    int32_t segment_number;
    int64_t sample_number;

    MSTraceList *mstl = NULL;
    MSTraceID *cur_tid;
    MSTraceSeg *cur_segment;

    char seg_time[32];

    retcode = ms_readtracelist (&mstl, argv[1], 0, -1., -1., 0, 1, 0, 1);
    if(retcode != MS_NOERROR) {
        printf("error reading traces");
        printf("\t%s", ms_errorstr(retcode));
        return 1;
    }

    mstl_printtracelist (mstl, 0, 1, 0);

    // iterate of the traces
    cur_tid = mstl->traces;
    for(trace_number=0; trace_number<mstl->numtraces; ++trace_number) {

        // iterate over the segments
        cur_segment = cur_tid->first;
        for(segment_number=0; segment_number<cur_tid->numsegments; ++segment_number) {

            printf("%s\n", ms_hptime2isotimestr(cur_segment->starttime, seg_time, 1));

            // iterate over the samples
            for(sample_number=0; sample_number<cur_segment->numsamples; ++sample_number) {
                printf("%ld, ", sample_number);
            }

            cur_segment = cur_segment->next;
        }

        cur_tid = cur_tid->next;
    }

    return 1;

} /* End of main() */

produces
   Source                Start sample             End sample        Hz  Samples
IU_COLA_00_LHZ    2010,058,06:50:00.069539 2010,058,07:59:59.069538 1   4200
Total: 1 trace(s) with 1 segment(s)
2010-02-27T06:50:00.069539

When compiled against branch master (c23cc3d8036ef5).
This is because mstl->traces->first->datasamples is NULL.
when run against ./example/test.mseed. I was expecting I'd see 4200 numbers rapidly scroll down my screen. Am I doing something wrong?

Thank you for the quick response. For some reason when I read the man page I assumed that if they were not 'unpacked', they would still be available but would be stored 'packed'. I wondered why one would want that and rapidly concluded that that this must be some sort of trade off between memory and access speed.

repo: iris-edu/libmseed


text:
(fix) Allow compilation using latest Rust

This basically fixes static. This blocks however on iron/iron#270.

Merged iron/iron#270, rerunning travis.

I'll push the changes once gcc etc. are building again.

Any updates on this? Or is this effectively superseded by #24 ?

@AnthIste, this has already become outdated and #24 seems to superseed it.

authors: AnthIste ProtectedMode reem

repo: iron/static


text:
Syntax highlighting broken with newline in method definition

If the method is defined all on one line, highlighting for the method name works fine but things like primitive types (string, map, etc) are not highlighted correctly:

If there is a newline in the method definition, the name is not highlighted correctly, but the primitive types are:

Moved to #59

repo: ironcladlou/GoTools


text:
Method Coverage

Feature Request
It would also be useful to have Method coverage reported by the tool.
Expected Behaviour
There would be an additional column that reports Method coverage
Additional Context
Similar to what is printed out by dotnet test:
Calculating coverage result...
Generating report './bin/test-results/coverage.cobertura.xml'
+------------------+--------+--------+--------+
| Module           | Line   | Branch | Method |
+------------------+--------+--------+--------+
| RCS.Libs.ArgUtil | 93.82% | 95.83% | 92.3%  |
+------------------+--------+--------+--------+
+---------+--------+--------+--------+
|         | Line   | Branch | Method |
+---------+--------+--------+--------+
| Total   | 93.82% | 95.83% | 92.3%  |
+---------+--------+--------+--------+
| Average | 93.82% | 95.83% | 92.3%  |
+---------+--------+--------+--------+

Optional would be fine.

repo: irongut/CodeCoverageSummary


text:
【自荐项目】-🔥中文 prompt 精选🔥

https://github.com/yzfly/wonderful-prompts
🔥中文 prompt 精选🔥，ChatGPT 使用指南，提升 ChatGPT 可玩性和可用性！🚀

good job！，收到，已同步添加到参考项目列表

authors: isLinXu yzfly

repo: isLinXu/prompt-engineering-note


text:
feat(client): added suspended protobuf and event handle

See: https://github.com/zerodytrash/TikTok-Live-Connector
Source: https://github.com/zerodytrash/TikTok-Live-Connector/blob/3277f0707dd4702650e682eed0bcd06b936de7e3/src/index.js#L531
    if (actionId === 3) {
        console.log('Stream ended by user');
    }
    if (actionId === 4) {
        console.log('Stream ended by platform moderator (ban)');
    }
})```

i don't even wanna know how anyone figured this out

@isaackogan doesn't there need to be a regenerated file somewhere here or it will cause an issue when referencing the enum type in the python code?

there absolutely does and i will do it at a later date

@isaackogan doesn't there need to be a regenerated file somewhere here or it will cause an issue when referencing the enum type in the python code?

I have no idea about that. Can you explain to me what you mean exactly, Sir?

I may have misspoken, it looks like the library uses the .proto file directly, I didn't know it could do that! So maybe this is fine.

authors: int3debug isaackogan steampoweredtaco

repo: isaackogan/TikTokLive


text:
Add exam board filtering to search results

Moves filterOnExamBoard to examBoard service from the topics service.
Filters search results based on user specified exam board
Provides Anon user choice like topics in the filter section

Implemented suggested changes

repo: isaacphysics/isaac-cs-app


text:
Rust code loses all syntax highlighting if there is a trait declaration in there

Moved from https://github.com/jashkenas/docco/issues/338

An entire block of Rust code (between two comments) will lose all its syntax highlighting if there is a single trait block with a "supertrait" declaration in there. That is, even the part of the code that's correctly highlighted usually will be broken once more code is added to the end of the file. Yeah, that doesn't make much sense, but what can I say^^

The following two files demonstrate the issue:

hljs.highlight('rs', 'fn sqr(i: i32) { i * i }');
> Object {r: 3, value: "<span class="hljs-keyw… i32) { i * i }", language: "rs", top: Object}

hljs.highlight('rs', 'fn sqr(i: i32) { i * i }\ntrait Minimum : Copy {}');
> Object {r: 0, value: "fn sqr(i: i32) { i * i }↵trait Minimum : Copy {}"}

When running docco, I would expect both of these files to get rendered with syntax highlighting. The first file works as expected. The second one lacks any form of syntax highlighting, even for its first line. If I remove the " : Copy", it's all working.

Thanks for reporting this!

authors: Sannis keithamus


text:
The database is full.

Steps to Reproduce
When the database file size reaches ~2G (2097152000 bytes), the database is full
Unhandled exception:
IsarError: The database is full.

Code sample
import 'dart:io';
import 'package:isar/isar.dart';
part 'test_isar.g.dart';

@collection
class User {
  Id id = Isar.autoIncrement; // you can also use id = null to auto increment
  String? name1;
  String? name2;
  String? name3;
  String? name4;
}

const bigText = """
Features💙 Made for Flutter. Easy to use, no config, no boilerplate🚀 Highly scalable The sky is the limit (pun intended)🍭 Feature rich. Composite & multi-entry indexes, query modifiers, JSON support etc.⏱ Asynchronous. Parallel query operations & multi-isolate support by default🦄 Open source. Everything is open source and free forever!Isar database can do much more (and we are just getting started🕵 Full-text search. Make searching fast and fun📱 Multiplatform. iOS, Android, Desktop and FULL WEB SUPPORT!🧪 ACID semantics. Rely on database consistency💃 Static typing. Compile-time checked and autocompleted queries✨ Beautiful documentation. Readable, easy to understand and ever-improvingJoin the Telegram group for discussion and sneak peaks of new versions of the db.If you want to say thank you, star us on GitHub and like us on pub.dev 🙌💙
""";

void main() async {
  await Isar.initializeIsarCore(download: true);
  final isar = await Isar.open([UserSchema],
      inspector: true, directory: Directory.current.path, name: "full-test");

  while (true) {
    await isar.writeTxn(() async {
      isar.users.putAll(List.generate(
          100,
          (index) => User()
            ..name1 = bigText
            ..name2 = bigText
            ..name3 = bigText
            ..name4 = bigText));
    });
  }
}

Waiting for fill to 2.1G

Details

Platform: Windows 11
Dart SDK version: 2.19.0-255.0.dev
Isar version: 3.0.2

[x] I searched for similar issues already
[x] I filled the details section with the exact device model and version
[x] I am able to provide a reproducible example

How much memory have you allocated? I believe the database size is limited by the available virtual memory.

Thank you for your advice.
I don't know how to allocate memory.
I checked dart --help --verbose
old_gen_heap_size: 30720 MB
Dart VM appears to have plenty of memory.

2GB is the maximum supported size currently. I'll add an option to increase the allowed size

There is a new property to customise the max database size (maxSizeMib) a new version will be released soon

I seem to be getting instances where I get this message even though I am nowhere near past the limit, I've even increased my size to 10GB (the size of user data/cache is only around 1GB) and I set the above parameter to 10240.
I'm trying to import 700K objects in one single transaction and get "The database is full", while the message does not show if I import 1K objects 700K times instead.
I also have feedback from users on slower devices where importing too many objects crashes their device but if I do the alternative 1K per transaction limit, no crash occurs. I'll probably make a new issue for this with the proper information, I'm on the latest Isar version.

authors: leisim lrorpilla xioxin

repo: isar/isar


text:
ezmsg-zmq: hotfix -- best practices for packaging, consistency

Same logic as #15

Merged in 3.3.0

repo: iscoe/ezmsg


text:
the fancyimpute needs tensorflow?

My unix has tensorflow-cpu and tensorflow-gpu. When I use the fancyimpute, it calls error about "importerror tensorflow"
ImportError: libcublas.so.9.0: cannot open shared object file: No such file or directory
it means the tensorflow-gpu version is error. But I can't update this GPU version. I only use this CPU version.
So how can I solve this question? thanks!

Sorry we can't help. This is a Tensorflow question. Try their GitHub.

repo: iskandr/fancyimpute


text:
🛑 ApiSyncfusionApp02.isolucion.co is down

In 427c5c8, ApiSyncfusionApp02.isolucion.co (https://ApiSyncfusionApp02.isolucion.co) was down:

HTTP code: 500
Response time: 588 ms

ok

repo: isolucionco/EstadoIsolucionHosting


text:
🛑 SanGabrielCajica.isolucion.co is down

In 744d875, SanGabrielCajica.isolucion.co (https://SanGabrielCajica.isolucion.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: SanGabrielCajica.isolucion.co is back up in 14f5777 after 569 days, 20 hours, 16 minutes.


text:
🛑 dane.isolucion.co is down

In 9deeeeb, dane.isolucion.co (https://dane.isolucion.co) was down:

HTTP code: 0
Response time: 0 ms

Resolved: dane.isolucion.co is back up in 35bc6c2.


text:
Bug in the plugin

The following program crashes the plugin:
{-# LANGUAGE TemplateHaskell #-}

module Polysemy.KVStore where

import Polysemy

data KVStore k v m a where
  LookupKV :: k -> KVStore k v m (Maybe v)
  UpdateKV :: k -> Maybe v -> KVStore k v m ()

makeSem ''KVStore

foo :: Member (KVStore k v) r => Sem r (Maybe Bool)
foo = do
  lookupKV "hello"

instead, it should be rejected saying couldnt prove k ~ String or v  ~ Bool

This won't be too hard, just need to keep track of which constraint is wanted and which is given. The wanted must be more polymorphic than the given in order to be substituted.

Closed in c3e13cadc70b41344b72be3c940209d7257c5330

repo: isovector/polysemy


text:
new implementation of the linked list queue buffer

Hi Ian,
this is the new implementation of the linked list queue buffer, that we started using in the Notification Framework. Maybe you want to add it to OpenRate as well.

Alright, but why use ConcurrentLinkedDeque?

authors: RonnySoak skymania

repo: isparkes/OpenRate


text:
Bug: max-height property doesn't seem to work in IE

In IE the max-height property of multi-select does not work. when a huge no of items are bound to multiselect dropdown it overflows the IE page  and to view more items we have to use arrow key but in that case the main multi-select control runs out of the view.
Also selecting a item in multi-select on IE browser , when the focus is on the selected item item content is not displayed

You also need to add the overflow-y: scroll; to the inline style in the line mentioned above by isteven.
Just so that I would have to manipulate the directive I added the following css and added the multi-div class to the div where the multi select is created. This way you can specify which multi select has the max-height and scrolling. If you add the style directly to the directive it will be applied to all multiselects in the app.
.multi-div .checkBoxContainer {
max-height: 220px;
overflow-y: scroll;
}
I tried changing the style in the directive to ng-style and I couldn't get it to work but with ng-style at least the setHeight() function was being called. The setHeight() method doesn't get called in the style attribute with IE.

@broguyman
Thanks for the update, much appreciated :)

Hi @isteven,
In which version is this fix available ? I am at v2.0.2 and issue is still available on IE 11.

@NalinSajwan
Try to download the latest version (v4.0.0). If it doesn't work, set it manually by following these 2 steps:  https://github.com/isteven/angular-multi-select/issues/153#issuecomment-67101299 and https://github.com/isteven/angular-multi-select/issues/153#issuecomment-68712377

authors: NalinSajwan aartiD broguyman isteven

repo: isteven/angular-multi-select


text:
Cherry-pick doc commits to release-0.1

Add useful commits to the release-0.1 (cf. #199 )

This should have been a rebase merge :/

authors: bmangoen dgn

repo: istio-ecosystem/sail-operator


text:
Use https instead of http

Avoids security error on https://istio.io/

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

#287 will cleanup to copy pasta/duplication in those 3 files

authors: istio-testing ldemailly

repo: istio/fortio


text:
Translation:k8s health checks

/assign @rootsongjc @fleeto

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: gyliu513
If they are not already assigned, you can assign the PR to them by writing /assign @gyliu513 in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content_zh/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Hi @pigletfly. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: fleeto
If they are not already assigned, you can assign the PR to them by writing /assign @fleeto in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content_zh/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/lgtm

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: rootsongjc
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content_zh/OWNERS [rootsongjc]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

authors: istio-testing pigletfly rootsongjc


text:
Pilot is using a static generated cacert to fetch JWT public key

Describe the bug
When JWT policy is used, Pilot is responsible to fetch the public key and distribute to Envoy. When fetching the public key, the public key is usually fetched from a HTTPS endpoint which means Pilot needs to verify the certificate of this HTTPS endpoint.
Currently Pilot is using a manually generated static CA bundle to do the verification:
https://github.com/istio/istio/blob/392be6637545b7df6c8a6c04ac29685c7aba615d/pilot/pkg/model/jwks_resolver.go#L65
https://github.com/istio/istio/blob/35ec73eff13fcc93decee31fabe80a7f5aacd743/tests/testdata/certs/cacert.pem#L2
Expected behavior
I'm not sure what's the best option here, but we should avoid using a static CA bundle as it doesn't scale well:

It doesn't handle well if a root certificate is revoked, or if there is a new root certificate added
The cacert.perm is placed under the testdata which seems indicating it's only for test purpose, but actually it's used in production

Version
1.1
/cc @quanjielin @liminw @diemtvu @kyessenov I'm wondering is it a temporary workaround to use the static ca bundle? or is it something standard to follow? Thank you.

today we baked Ubuntu CA bundle into pilot docker image, ideally we should put something below in pilot docker file get fetch it dynamically(see nodeagent example)
RUN apt-get update && apt-get install -y ca-certificates

@quanjielin Are there any problems blocking us to do it now?

No, should be a small change.

Sounds fine, but put the docker command into the daily base image. apt-get will cause build flakiness if you run it on every PR.

authors: kyessenov quanjielin yangminzhu

repo: istio/istio


text:
mixer TestCheck_Deny and TestMixer_Report_Direct flake

Example: https://circleci.com/gh/istio/istio/366445?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link
In the same PR the tests passed on prow, and I think I have seen this before, so I believe it is a flake.

Seems like a failure of the test framework to deploy the policy backend:
2019-03-27T07:16:50.383051Z	info	grpc: addrConn.createTransport failed to connect to {127.0.0.1:37479 0  }. Err :connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:37479: connect: connection refused". Reconnecting...
2019-03-27T07:16:50.383095Z	info	pickfirstBalancer: HandleSubConnStateChange: 0xc4208ea410, CONNECTING
2019-03-27T07:16:50.383103Z	info	pickfirstBalancer: HandleSubConnStateChange: 0xc4208ea410, TRANSIENT_FAILURE
2019-03-27T07:17:01.243341Z	info	grpc: addrConn.createTransport failed to connect to {127.0.0.1:37479 0  }. Err :connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:37479: connect: connection refused". Reconnecting...
2019-03-27T07:17:01.243384Z	info	pickfirstBalancer: HandleSubConnStateChange: 0xc4208ea410, CONNECTING
2019-03-27T07:17:01.243393Z	info	pickfirstBalancer: HandleSubConnStateChange: 0xc4208ea410, TRANSIENT_FAILURE
2019-03-27T07:17:18.304776Z	info	pickfirstBalancer: HandleSubConnStateChange: 0xc4208ea410, CONNECTING
2019-03-27T07:17:18.304858Z	info	grpc: addrConn.createTransport failed to connect to {127.0.0.1:37479 0  }. Err :connection error: desc = "transport: Error while dialing dial tcp 127.0.0.1:37479: connect: connection refused". Reconnecting...
2019-03-27T07:17:18.304878Z	info	pickfirstBalancer: HandleSubConnStateChange: 0xc4208ea410, TRANSIENT_FAILURE

This is for the test-integration-kubernetes suite?
Did your PR include: https://github.com/istio/istio/pull/12848 ?
I think the conversion over to the new framework wasn't/isn't complete or stable.

Is this a dupe of https://github.com/istio/istio/issues/12750 ?

PR must not have included that change since it looks like they were skipped. Thanks!

authors: douglas-reid howardjohn kyessenov


text:
Virtualservices/Destination rules not working after 1.2.5 upgrade

Bug description
I’ve recently upgraded my istio setup from 1.0.5 to 1.2.5, basically running a fresh setup.
After that my set of VirtualServices / Destination rules seems to be totally ignored.
I’ve a Kong Api gw with istio sidecar acting as a ingress and a couple of nginx labelled “version: green” and “version: blue” I want to access via a given header “nginx” (green is the live one, blue the “dark” alternative)
here is my destinationRule
kind: DestinationRule
apiVersion: networking.istio.io/v1alpha3
metadata:
  name: nginx-service-destination
  namespace: staging
  labels:
    app: nginx-service
    profile: staging
spec:
  host: nginx
  subsets:
    - labels:
        version: blue
      name: blue-nginx
    - labels:
        version: green
      name: green-nginx

and my virtual service
kind: VirtualService
apiVersion: networking.istio.io/v1alpha3
metadata:
  name: nginx-service-vservice
  namespace: staging

  labels:
    app: nginx-service
    profile: staging
spec:
  hosts:
    - nginx
  http:
    - match:
        - headers:
            nginx:
              exact: green
      name: green
      route:
        - destination:
            host: nginx
            port:
              number: 80
            subset: green-nginx
    - match:
        - headers:
            nginx:
              exact: blue
      name: blue
      route:
        - destination:
            host: nginx
            subset: blue-nginx
    - name: default
      route:
        - destination:
            host: nginx
            subset: green-nginx

Such configuration was working perfectly on old 1.0.5 and I could drive my browser from green to blue simply adding http header “nginx: blue”.
I’ve checked 1.2.5 documentation several time but could’n find any significant change and validation webhook and Kiali says everything is fine.
Nevertheless my requests are simply doing a roundRobin between green and blue as they where totally ignored by istio.

Affected product area (please put an X in all that apply)
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ X ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Expected behavior
Request should be routed to proper pod according to header presence/value
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version)
istio 1.2.5
kiali 1.4.2
kubernetes 1.12.6 (local installation)
How was Istio installed?
helm template + kubectl apply
values.yaml
# Top level istio values file has the following sections.
#
# global: This file is the authoritative and exhaustive source for the global section.
#
# chart sections: Every subdirectory inside the charts/ directory has a top level
#       configuration key in this file. This file overrides the values specified
#       by the charts/${chartname}/values.yaml.
#       Check the chart level values file for exhaustive list of configuration options.

#
# Gateways Configuration, refer to the charts/gateways/values.yaml
# for detailed configuration
#
gateways:
  enabled: false

#
# sidecar-injector webhook configuration, refer to the
# charts/sidecarInjectorWebhook/values.yaml for detailed configuration
#
sidecarInjectorWebhook:
  enabled: true
  enableNamespacesByDefault: false

#
# galley configuration, refer to charts/galley/values.yaml
# for detailed configuration
#
galley:
  enabled: true

#
# mixer configuration
#
# @see charts/mixer/values.yaml, it takes precedence
mixer:
  policy:
    # if policy is enabled the global.disablePolicyChecks has affect.
    enabled: false

  telemetry:
    enabled: true
#
# pilot configuration
#
# @see charts/pilot/values.yaml
pilot:
  enabled: true
  traceSampling: 100.0

#
# security configuration
#
# DO NOT TURN OFF OR YOU WILL GET MISSING SECRETS FOR OTHER COMPONENTS
security:
  enabled: true

#
# nodeagent configuration
#
nodeagent:
  enabled: false

#
# addon grafana configuration
#
grafana:
  enabled: false

#
# addon prometheus configuration
#
prometheus:
  enabled: false

#
# addon jaeger tracing configuration
#
tracing:
  enabled: false
  jaeger:
    tag: 1.13.1

#
# addon kiali tracing configuration
#
kiali:
  enabled: true
  #tag: v0.21
  tag: v1.4.2
  dashboard:
    # You must create a secret with this name - one is not provided out-of-box.
    secretName: kiali
    # Bind the service account to a role with only read access
    viewOnlyMode: false
    # If you have Grafana installed and it is accessible to client browsers, then set this to its external URL.
    # Kiali will redirect users to this URL when Grafana metrics are to be shown.
    grafanaURL:  https://monitor.test.k8.mydomain.int/
    # If you have Jaeger installed and it is accessible to client browsers, then set this property to its external URL.
    # Kiali will redirect users to this URL when Jaeger tracing is to be shown.
    jaegerURL:  https://jaeger.test.k8.mydomain.int/
  prometheusAddr: http://prometheus-server.kube-system:80

#
# addon certmanager configuration
#
certmanager:
  enabled: false

#
# Istio CNI plugin enabled
#   This must be enabled to use the CNI plugin in Istio.  The CNI plugin is installed separately.
#   If true, the privileged initContainer istio-init is not needed to perform the traffic redirect
#   settings for the istio-proxy.
#
istio_cni:
  enabled: false

# addon Istio CoreDNS configuration
#
istiocoredns:
  enabled: false

# Common settings used among istio subcharts.
global:
  # Default hub for Istio images.
  # Releases are published to docker hub under 'istio' project.
  # Daily builds from prow are on gcr.io, and nightly builds from circle on docker.io/istionightly
  hub: docker.io/istio

  # Default tag for Istio images.
  tag: 1.2.5

  # Comma-separated minimum per-scope logging level of messages to output, in the form of <scope>:<level>,<scope>:<level>
  # The control plane has different scopes depending on component, but can configure default log level across all components
  # If empty, default scope and level will be used as configured in code
  logging:
    level: "default:warn"

  # monitoring port used by mixer, pilot, galley
  monitoringPort: 15014

  k8sIngress:
    enabled: false
    # Gateway used for k8s Ingress resources. By default it is
    # using 'istio:ingressgateway' that will be installed by setting
    # 'gateways.enabled' and 'gateways.istio-ingressgateway.enabled'
    # flags to true.
    gatewayName: ingressgateway
    # enableHttps will add port 443 on the ingress.
    # It REQUIRES that the certificates are installed  in the
    # expected secrets - enabling this option without certificates
    # will result in LDS rejection and the ingress will not work.
    enableHttps: false

  proxy:
    image: proxyv2

    # cluster domain. Default value is "cluster.local".
    clusterDomain: "cluster.local"

    # Resources for the sidecar.
    resources:
      requests:
        cpu: 100m
        memory: 128Mi
      limits:
        cpu: 2000m
        memory: 1024Mi

    # Controls number of Proxy worker threads.
    # If set to 0 (default), then start worker thread for each CPU thread/core.
    concurrency: 2

    # Configures the access log for each sidecar.
    # Options:
    #   "" - disables access log
    #   "/dev/stdout" - enables access log
    accessLogFile: ""

    # Configure how and what fields are displayed in sidecar access log. Setting to
    # empty string will result in default log format
    accessLogFormat: ""

    # Configure the access log for sidecar to JSON or TEXT.
    accessLogEncoding: JSON

    # Log level for proxy, applies to gateways and sidecars.  If left empty, "warning" is used.
    # Expected values are: trace|debug|info|warning|error|critical|off
    logLevel: "warning"

    # Per Component log level for proxy, applies to gateways and sidecars. If a component level is
    # not set, then the global "logLevel" will be used. If left empty, "misc:error" is used.
    componentLogLevel: ""

    # Configure the DNS refresh rate for Envoy cluster of type STRICT_DNS
    # This must be given it terms of seconds. For example, 300s is valid but 5m is invalid.
    dnsRefreshRate: 300s

    #If set to true, istio-proxy container will have privileged securityContext
    privileged: false

    # If set, newly injected sidecars will have core dumps enabled.
    enableCoreDump: false

    # Default port for Pilot agent health checks. A value of 0 will disable health checking.
    statusPort: 15020

    # The initial delay for readiness probes in seconds.
    readinessInitialDelaySeconds: 1

    # The period between readiness probes.
    readinessPeriodSeconds: 2

    # The number of successive failed probes before indicating readiness failure.
    readinessFailureThreshold: 30

    # istio egress capture whitelist
    # https://istio.io/docs/tasks/traffic-management/egress.html#calling-external-services-directly
    # example: includeIPRanges: "172.30.0.0/16,172.20.0.0/16"
    # would only capture egress traffic on those two IP Ranges, all other outbound traffic would
    # be allowed by the sidecar
    includeIPRanges: "*"
    excludeIPRanges: "{{ansible_default_ipv4.network}}/24"
    excludeOutboundPorts: ""

    # pod internal interfaces
    kubevirtInterfaces: ""

    # istio ingress capture whitelist
    # examples:
    #     Redirect no inbound traffic to Envoy:    --includeInboundPorts=""
    #     Redirect all inbound traffic to Envoy:   --includeInboundPorts="*"
    #     Redirect only selected ports:            --includeInboundPorts="80,8080"
    includeInboundPorts: "*"
    excludeInboundPorts: ""

    # This controls the 'policy' in the sidecar injector.
    autoInject: disabled

    # Sets the destination Statsd in envoy (the value of the "--statsdUdpAddress" proxy argument
    # would be <host>:<port>).
    # Disabled by default.
    # The istio-statsd-prom-bridge is deprecated and should not be used moving forward.
    envoyStatsd:
      # If enabled is set to true, host and port must also be provided. Istio no longer provides a statsd collector.
      enabled: false
      host: # example: statsd-svc.istio-system
      port: # example: 9125

    # Sets the Envoy Metrics Service address, used to push Envoy metrics to an external collector
    # via the Metrics Service gRPC API. This contains detailed stats information emitted directly
    # by Envoy and should not be confused with the the Istio telemetry. The Envoy stats are also
    # available to scrape via the Envoy admin port at either /stats or /stats/prometheus.
    #
    # See https://www.envoyproxy.io/docs/envoy/latest/api-v2/config/metrics/v2/metrics_service.proto
    # for details about Envoy's Metrics Service API.
    #
    # Disabled by default.
    envoyMetricsService:
      enabled: false
      host: # example: metrics-service.istio-system
      port: # example: 15000

    # Specify which tracer to use. One of: lightstep, zipkin, datadog
    tracer: "zipkin"

  proxy_init:
    # Base name for the proxy_init container, used to configure iptables.
    image: proxy_init

  # imagePullPolicy is applied to istio control plane components.
  # local tests require IfNotPresent, to avoid uploading to dockerhub.
  # TODO: Switch to Always as default, and override in the local tests.
  imagePullPolicy: IfNotPresent

  # controlPlaneSecurityEnabled enabled. Will result in delays starting the pods while secrets are
  # propagated, not recommended for tests.
  controlPlaneSecurityEnabled: false

  # disablePolicyChecks disables mixer policy checks.
  # if mixer.policy.enabled==true then disablePolicyChecks has affect.
  # Will set the value with same name in istio config map - pilot needs to be restarted to take effect.
  disablePolicyChecks: true

  # policyCheckFailOpen allows traffic in cases when the mixer policy service cannot be reached.
  # Default is false which means the traffic is denied when the client is unable to connect to Mixer.
  policyCheckFailOpen: false

  # EnableTracing sets the value with same name in istio config map, requires pilot restart to take effect.
  enableTracing: true

  # Configuration for each of the supported tracers
  tracer:
    # Configuration for envoy to send trace data to LightStep.
    # Disabled by default.
    # address: the <host>:<port> of the satellite pool
    # accessToken: required for sending data to the pool
    # secure: specifies whether data should be sent with TLS
    # cacertPath: the path to the file containing the cacert to use when verifying TLS. If secure is true, this is
    #   required. If a value is specified then a secret called "lightstep.cacert" must be created in the destination
    #   namespace with the key matching the base of the provided cacertPath and the value being the cacert itself.
    #
    lightstep:
      address: ""                # example: lightstep-satellite:443
      accessToken: ""            # example: abcdefg1234567
      secure: true               # example: true|false
      cacertPath: ""             # example: /etc/lightstep/cacert.pem
    zipkin:
      # Host:Port for reporting trace data in zipkin format. If not specified, will default to
      # zipkin service (port 9411) in the same namespace as the other istio components.
      address: "{{jaeger_deploy_name}}-collector.{{istio_namespace}}:9411"
    datadog:
      # Host:Port for submitting traces to the Datadog agent.
      address: "$(HOST_IP):8126"

  # Default mtls policy. If true, mtls between services will be enabled by default.
  mtls:
    # Default setting for service-to-service mtls. Can be set explicitly using
    # destination rules or service annotations.
    enabled: false

  # ImagePullSecrets for all ServiceAccount, list of secrets in the same namespace
  # to use for pulling any images in pods that reference this ServiceAccount.
  # For components that don't use ServiceAccounts (i.e. grafana, servicegraph, tracing)
  # ImagePullSecrets will be added to the corresponding Deployment(StatefulSet) objects.
  # Must be set for any cluster configured with private docker registry.
  imagePullSecrets:
    # - private-registry-key

  # Specify pod scheduling arch(amd64, ppc64le, s390x) and weight as follows:
  #   0 - Never scheduled
  #   1 - Least preferred
  #   2 - No preference
  #   3 - Most preferred
  arch:
    amd64: 2
    s390x: 2
    ppc64le: 2

  # Whether to restrict the applications namespace the controller manages;
  # If not set, controller watches all namespaces
  oneNamespace: false

  # Default node selector to be applied to all deployments so that all pods can be
  # constrained to run a particular nodes. Each component can overwrite these default
  # values by adding its node selector block in the relevant section below and setting
  # the desired values.
  defaultNodeSelector:
    devops: test

  # Default node tolerations to be applied to all deployments so that all pods can be
  # scheduled to a particular nodes with matching taints. Each component can overwrite
  # these default values by adding its tolerations block in the relevant section below
  # and setting the desired values.
  # Configure this field in case that all pods of Istio control plane are expected to
  # be scheduled to particular nodes with specified taints.
  defaultTolerations: []

  # Whether to perform server-side validation of configuration.
  configValidation: true

  # Custom DNS config for the pod to resolve names of services in other
  # clusters. Use this to add additional search domains, and other settings.
  # see
  # https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#dns-config
  # This does not apply to gateway pods as they typically need a different
  # set of DNS settings than the normal application pods (e.g., in
  # multicluster scenarios).
  # NOTE: If using templates, follow the pattern in the commented example below.
  #podDNSSearchNamespaces:
  #- global
  #- "[[ valueOrDefault .DeploymentMeta.Namespace \"default\" ]].global"

  # If set to true, the pilot and citadel mtls will be exposed on the
  # ingress gateway
  meshExpansion:
    enabled: false
    # If set to true, the pilot and citadel mtls and the plain text pilot ports
    # will be exposed on an internal gateway
    useILB: false

  multiCluster:
    # Set to true to connect two kubernetes clusters via their respective
    # ingressgateway services when pods in each cluster cannot directly
    # talk to one another. All clusters should be using Istio mTLS and must
    # have a shared root CA for this model to work.
    enabled: false

  # A minimal set of requested resources to applied to all deployments so that
  # Horizontal Pod Autoscaler will be able to function (if set).
  # Each component can overwrite these default values by adding its own resources
  # block in the relevant section below and setting the desired resources values.
  defaultResources:
    requests:
      cpu: 10m
    #   memory: 128Mi
    # limits:
    #   cpu: 100m
    #   memory: 128Mi

  # enable pod distruption budget for the control plane, which is used to
  # ensure Istio control plane components are gradually upgraded or recovered.
  defaultPodDisruptionBudget:
    enabled: true
    # The values aren't mutable due to a current PodDisruptionBudget limitation
    # minAvailable: 1

  # Kubernetes >=v1.11.0 will create two PriorityClass, including system-cluster-critical and
  # system-node-critical, it is better to configure this in order to make sure your Istio pods
  # will not be killed because of low priority class.
  # Refer to https://kubernetes.io/docs/concepts/configuration/pod-priority-preemption/#priorityclass
  # for more detail.
  priorityClassName: ""

  # Use the Mesh Control Protocol (MCP) for configuring Mixer and
  # Pilot. Requires galley (`--set galley.enabled=true`).
  useMCP: true

  # The trust domain corresponds to the trust root of a system
  # Refer to https://github.com/spiffe/spiffe/blob/master/standards/SPIFFE-ID.md#21-trust-domain
  # Indicate the domain used in SPIFFE identity URL
  # The default depends on the environment.
  #   kubernetes: cluster.local
  #   else:  default dns domain
  trustDomain: ""

  # Set the default behavior of the sidecar for handling outbound traffic from the application:
  # ALLOW_ANY - outbound traffic to unknown destinations will be allowed, in case there are no
  #   services or ServiceEntries for the destination port
  # REGISTRY_ONLY - restrict outbound traffic to services defined in the service registry as well
  #   as those defined through ServiceEntries
  # ALLOW_ANY is the default in 1.1.  This means each pod will be able to make outbound requests
  # to services outside of the mesh without any ServiceEntry.
  # REGISTRY_ONLY was the default in 1.0.  If this behavior is desired, set the value below to REGISTRY_ONLY.
  outboundTrafficPolicy:
    mode: REGISTRY_ONLY

  # The namespace where globally shared configurations should be present.
  # DestinationRules that apply to the entire mesh (e.g., enabling mTLS),
  # default Sidecar configs, etc. should be added to this namespace.
  # configRootNamespace: istio-config

  # set the default set of namespaces to which services, service entries, virtual services, destination
  # rules should be exported to. Currently only one value can be provided in this list. This value
  # should be one of the following two options:
  # * implies these objects are visible to all namespaces, enabling any sidecar to talk to any other sidecar.
  # . implies these objects are visible to only to sidecars in the same namespace, or if imported as a Sidecar.egress.host
  #defaultConfigVisibilitySettings:
  #- '*'

  sds:
    # SDS enabled. IF set to true, mTLS certificates for the sidecars will be
    # distributed through the SecretDiscoveryService instead of using K8S secrets to mount the certificates.
    enabled: false
    udsPath: ""
    useTrustworthyJwt: false
    useNormalJwt: false

  # Configure the mesh networks to be used by the Split Horizon EDS.
  #
  # The following example defines two networks with different endpoints association methods.
  # For `network1` all endpoints that their IP belongs to the provided CIDR range will be
  # mapped to network1. The gateway for this network example is specified by its public IP
  # address and port.
  # The second network, `network2`, in this example is defined differently with all endpoints
  # retrieved through the specified Multi-Cluster registry being mapped to network2. The
  # gateway is also defined differently with the name of the gateway service on the remote
  # cluster. The public IP for the gateway will be determined from that remote service (only
  # LoadBalancer gateway service type is currently supported, for a NodePort type gateway service,
  # it still need to be configured manually).
  #
  # meshNetworks:
  #   network1:
  #     endpoints:
  #     - fromCidr: "192.168.0.1/24"
  #     gateways:
  #     - address: 1.1.1.1
  #       port: 80
  #   network2:
  #     endpoints:
  #     - fromRegistry: reg1
  #     gateways:
  #     - registryServiceName: istio-ingressgateway.istio-system.svc.cluster.local
  #       port: 443
  #
  meshNetworks: {}

  # Specifies the global locality load balancing settings.
  # Locality-weighted load balancing allows administrators to control the distribution of traffic to
  # endpoints based on the localities of where the traffic originates and where it will terminate.
  # Please set either failover or distribute configuration but not both.
  #
  # localityLbSetting:
  #   distribute:
  #   - from: "us-central1/*"
  #     to:
  #       "us-central1/*": 80
  #       "us-central2/*": 20
  #
  # localityLbSetting:
  #   failover:
  #   - from: us-east
  #     to: eu-west
  #   - from: us-west
  #     to: us-east
  localityLbSetting: {}

  # Specifies whether helm test is enabled or not.
  # This field is set to false by default, so 'helm template ...'
  # will ignore the helm test yaml files when generating the template
  enableHelmTest: false

Environment where bug was observed (cloud vendor, OS, etc)
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.

can anybody provide me any hint?
This is blocking me from upgrading to latest version.

have you tried to use istioctl proxy-config to check if the VS and DR configuration in your gateway or pod?

@aroundthecode  Are you using kong ingress controller?  and is it working as expected in the current istio version ?

in the end this resulted in some configuration/conflict errors which where note reported by Istio validation webook / pilot nor Kiali causing the whole destination rule to be dropped and ignored.
The only point where the error was reported was the policy pod, but if you miss such log all the rest of the mesh is report to be working properly with given configuration when in fact it's not.
I think such errors should be propagated with much more evidence mainly because the "entry check" performed by the validation webook doesn't seem to perform the same checks.
is there any prometheus metrics which can be used to detect such "dropped" configurations?

I suspect your issue is similar to this one https://github.com/istio/istio/issues/19835
Try changing your service port to 8080 and check if that works

authors: aroundthecode hobbytp ravibagri5 sekhrivijay