Cannot create entities or devices for IoT-Agent JSON v1.19.0 with FiLiP v0.2.5

Describe the bug
In our current cluster setup, which is running the following versions

iotagent-json:1.19.0
mongodb:6.0.9-debian-11-r5
orion:3.7.0

we are able to create service group, entities and devices using API requests via Postman, however, we are unable to create any of these using the FiLiP library. The only thing possible is reading the version.
Going through the logs, we identified the following two errors in this process:
time=2023-10-19T14:51:04.356Z | lvl=DEBUG | corr=9b6f9b8d-a609-4253-bc0d-6cf208c887fc | trans=9b6f9b8d-a609-4253-bc0d-6cf208c887fc | op=IoTAgentNGSI.RestUtils | srv=PerformanceTestsDebuggingTest | subsrv=/PerformanceTestsDebuggingTest | msg=Errors found validating request: {"valid":false,"errors":[{"attribute":"additionalProperties","property":"devices.0.attributes.1.metadata","actual":{},"message":"must not exist"},{"attribute":"additionalProperties","property":"devices.0.attributes.0.metadata","actual":{},"message":"must not exist"}]} | comp=IoTAgent
time=2023-10-19T14:51:04.356Z | lvl=DEBUG | corr=9b6f9b8d-a609-4253-bc0d-6cf208c887fc | trans=9b6f9b8d-a609-4253-bc0d-6cf208c887fc | op=IoTAgentNGSI.GenericMiddlewares | srv=PerformanceTestsDebuggingTest | subsrv=/PerformanceTestsDebuggingTest | msg=Error [WRONG_SYNTAX] handling request: Wrong syntax in request: Errors found validating request. | comp=IoTAgent
To Reproduce
You can find a script for the device creation including the current configuration for our cluster in our internal git repository https://git-ce.rwth-aachen.de/ebc/projects/EBC0391_BMWi_PL-Reg_GES/communication/datamodelsforsemanticnetworking/-/tree/BoosterDatamodelsStresstests/datamodels/BES?ref_type=heads. The main.py will try to create service group, entities, devices, subscriptions and grafana dashboards to cover a full check of the FIWARE setup. For checking if the process was successful, you can either request the created objects or check within the cluster components directly. However, for the latter, you will require the credentials.
Expected behavior
We expect the entity and device creation etc. via FiLiP to behave the same as via API request from Postman. So, after the creation, they should appear as stored objects in the mongodb.
Environment (please complete the following information):

OS [Windows 10 Education]
pydantic: [1.8.2]
filip [0.2.5]

@msc-d1s7fa1eza can you search for 9b6f9b8d-a609-4253-bc0d-6cf208c887fc in logs? Then, you can see which device caused the problem. Please try to provision this device via Filip. And it not works, please post your code below

@djs0109 Please excuse the delayed reply. We already discussed the background to this issue in person. For the record and history, I would like to share the insights here:
In fact, the issue was caused with the version 1.14.0 of the IoT Agent. This version seems to not be compatible with the current FiLiP version any more, which resulted in not being able to create any devices or service groups etc. As we are using Kubernetes for the FIWARE deployment, there are currently only HELM charts available for the version 1.14.0 of the IoT Agent json, for reference, see our issue here. Due to a change of the mountPath from /opt/iotajson/config.js to /opt/iotagent-json/config.js, when switching the image version to 1.19.0, the IoT Agent was not able to connect to the mongoDB correctly, consequently, again resulting in not being able to use the IoTA API. Fixing the mountPath allows for installing the latest IoTA version, which is working just fine with the current FiLiP version so far. Therefore, if you could add a hint that version 1.14.0 is no longer supported, this would probably help in finding potential incompatibilities in the setup. We also have tested the 1.19.0 version of the IoT Agent, which seemed also to be working just fine, so I would close the issue now.


Clarification on how the function calculate_ic works

I wonder if you can explain the job of the function calculate_ic? https://github.com/bio-ontology-research-group/deepgoplus/blob/e031def1f0fb1921e8ae57d7b3ef1cbb2fc2e5fe/utils.py#L48

Hi,
This function computes information content (IC) of the classes based on
the annotations. You can find detailed explanation for this specific IC measure here https://www.ncbi.nlm.nih.gov/pubmed/23813009.

Thanks a lot. This helps.


ClientModel: Add Distributed Tracing policy

Duplicate of https://github.com/Azure/azure-sdk-for-net/issues/42115


ValidationError when using Generic constructor for subfield

Initial Checks

[X] I confirm that I'm using Pydantic V2

Description
Encountered ValidationError while migrating a codebase from Pydantic v1 to v2. Identified the problem to be from a generic BaseModel constructor, which works on v1 but not v2.
Example code below is a simplified version of the problematic use case in the current codebase.
Wondering if there are any solutions or workarounds with minimal changes, ideally without having to define additional classes, as that will cause large amounts of code redundancy in the codebase.
Example Code
from typing import Generic, TypeVar
from pydantic import BaseModel

A = TypeVar("A")

class Box(BaseModel, Generic[A]):
    value: A | None = None

class Storage(BaseModel):
    int_box: Box[int]

class BoxMaker(Generic[A]):
    @staticmethod
    def make_box() -> Box[A]:
        return Box[A]()

int_box = BoxMaker[int].make_box()
store = Storage(int_box=int_box)

print(store.dict())

Python, Pydantic & OS Version
pydantic version: 2.7.1
        pydantic-core version: 2.18.2
          pydantic-core build: profile=release pgo=false
               python version: 3.10.11 (v3.10.11:7d4cc5aa85, Apr  4 2023, 19:05:19) [Clang 13.0.0 (clang-13<IP_ADDRESS>)]
                     platform: macOS-14.4.1-x86_64-i386-64bit

@FizzyAgent,
Thanks for reporting this. I know this issue has been reported before, but I'm still digging around to find it.
In the meantime, here's a similar issue: https://github.com/pydantic/pydantic/issues/8071.

Other related issues:

https://github.com/pydantic/pydantic/issues/9295
https://github.com/pydantic/pydantic/issues/7096#issuecomment-1678031081
https://github.com/pydantic/pydantic/issues/9414

Going to mark this as a duplicate and closer for now, but definitely something we'll want to revisit for V3. Great articulation of the issue!


Getting exception Cannot call start() again on a started server inspite of stop() being called before start()

Actual behavior (the bug)
I get the exception java.lang.IllegalStateException: Cannot call start() again on a started server. even though app.stop() was called when the second test runs.
Expected behavior
app.start(9001) should work if called after app.stop()
To Reproduce
In beforeEach section of your test suite add the following lines of code
    app.stop()
    app.start(9001)

where app refers to the instance that was created using Javalin.create() at the top level
Additional context
The language being used is Scala and the testing framework being used is munit

@ashwinbhaskar The server is not intended to be "re-started" once it has been started. You should make a new instance :)

@tipsy are you sure about that? These set of tests had passed for me earlier here
https://github.com/ashwinbhaskar/hydra-java/blob/master/src/test/java/HydraClientImplTest.java
But I had written this in Java and with org.junit

I'm sure about the intention. I never planned on having "restarts" for a server, so when you do stop() the server is not supposed to be used anymore. It might still work, my recommendation is that you create a new instance.

@tipsy got it:)

@tipsy was there a specific reason for not allowing it to restart? Also, can the error message in the exception be changed to reflect this intention (I can raise a PR for that if you'd like)?

was there a specific reason for not allowing it to restart?

No reason particular, there are just a lot more things to consider if you allow restarts.

also, can the error message in the exception be changed to reflect this intention (I can raise a PR for that if you'd like)?

That would be great!

@tipsy Have raised this pull request - https://github.com/tipsy/javalin/pull/942


affected/package:

What version of Go are you using (go version)?

$ go version 1.19.3

Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
C:\Users\goran>go env
set GO111MODULE=
set GOARCH=amd64
set GOBIN=D:\goworkspace\bin
set GOCACHE=C:\Users\goran\AppData\Local\go-build
set GOENV=C:\Users\goran\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=D:\goworkspace\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=D:\goworkspace
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Program Files\Go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLDIR=C:\Program Files\Go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=go1.19.3
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=NUL
set GOWORK=
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=C:\Users\goran\AppData\Local\Temp\go-build3586402992=/tmp/go-build -gno-record-gcc-switches

What did you do?

package main
import "fmt"
func main() {
fmt.Println("Hello from GO")
}
What did you expect to see?
Hello from GO
after 1-2s of compiling
What did you see instead?
Hello from GO
after 19 s of compiling

The build time related to your PC's performance.
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions

I have hp elitebook g 840 with 32gb of memory. I have tried to compile
under wsl2 Ubuntu on the same machine and compilation is 1.5 sec.
On Wed, Dec 7, 2022, 12:42 Meng Zhuo @.***> wrote:

Closed #57137 https://github.com/golang/go/issues/57137 as not planned.
—
Reply to this email directly, view it on GitHub
https://github.com/golang/go/issues/57137#event-7976900937, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACXQ4EKHE4TFQDSHE24K26LWMBZ2JANCNFSM6AAAAAASWT6DLE
.
You are receiving this because you authored the thread.Message ID:
@.***>

Then it's your antivirus.


Verilator linter with -match

As suggested by @imphil we are adding a wildcard match for lint_off rules in Verilator. This avoids adopting lines in the linter configuration file.
It is still under development in Verilator and hopefully makes one of the next two releases. Clone https://github.com/verilator/verilator/tree/issue-1649 to test it.
Upstream issue: https://github.com/verilator/verilator/issues/1649

Feature upstream, next release (4.026) scheduled for mid February.

It is in Verilator 4.028 now!

This needs two things:

A rebase to pick up recent changes to the waiver. Can you do that @wallento?
A fix for https://github.com/lowRISC/ibex/issues/603 to ensure we inform our users that they need to update Verilator. I'll look into that.

Tom or Stefan, could one of you do the rebase and also update the minimum Verilator version in our Config

Thanks @wallento, @tomroberts-lowrisc, and @rswarbrick!


added read me for two tests:office-addin-test-helpers and office-addi…

This addresses https://github.com/OfficeDev/Office-Addin-Scripts/issues/137

I'm still reviewing this.

@julflore000 I noticed the summary text for each package is also copied into the package's readme. Can you please be sure the text is the same wherever the text is copy pasted into a package readme?

@julflore000 @TCourtneyOwen Please work to update this so we can complete the pull request.


added predicate for Xsline

#48

@yegor256 FYI

@MikhailLipanin I believe, a more elegant way would be to create a new Shift called StSequence:
final Train<Shift> train = new TrDefault<>().with(
  new StSequence(
    xml -> xml.nodes("/x[text()='{{{hello}}}']").isEmpty(),
    new TrClasspath<>(new TrDefault<>())
      .with("add-brackets.xsl")
      .with("add-brackets.xsl")
      .with("add-brackets.xsl")
      .back()
  )
)
final XML output = new Xsline(train).pass(new XMLDocument("<x>hello</x>"));
MatcherAssert.assertThat(
  output,
  XhtmlMatchers.hasXPaths("/x[.='{{{hello}}}']")
);

@yegor256 done

I think, with this new shift, we can refuse to use StOfTrain

@MikhailLipanin yes, indeed... we can delete StOfTrain and introduce a new ctor: StSequence(Iterable<Shift>). WDYT?

@yegor256 Yes, done.
Now, when releasing, we need to update the minor version of the library, because StOfTrain functionality is no longer available.

@MikhailLipanin yes, indeed, we have to. But it would be great to not, because of ZeroVer philosophy. I think it would be great if w put StOfTrain back to repository and annotate it with @Deprecated, and make it use StSequence.

@yegor256 done. Also added a  Ctor with uid in StSequence, same as was at StOfTrain

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 9min)


Add netgear_exporter to exporters list

Just released this since it's something I've been wanting for a few months. Hopefully others find it useful.

Something went waaaay wrong here... just scrapping and restarting


⚠ Bofrost.es has degraded performance

In f8da534, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1637 ms

Resolved: Bofrost.es performance has improved in 91754bf after 9 minutes.


have plan to support android home widget?

have plan to support android home widget?

Hey @saviourdog
Currently not planned but is definitely an interesting feature for the future.


ARM assembly pack: translate bit-sliced AES implementation to AArch64

This addresses a performance issue on the Raspberry Pi 4, when running in AArch64 mode. This device feature a Cortex-A72 CPU, without the cryptography extensions. OpenSSL includes a bit-sliced AES implementation for Arm cores which is used by the Raspberry Pi 4 in AArch32 mode, but this has not been usable in AArch64 mode until now. In fact, it runs a little faster on AArch64 than AArch32 because there are more registers available (so less spilling of variables to the stack is required) and I have been able to schedule the instructions to better suit modern CPUs that are superscalar for SIMD instructions.
The AArch32 version featured a build variant which was used at one point in the past when the same source file was built into the Linux kernel. Linux has since replaced this with a dedicated implementation, so this build variant is not carried across to the AArch64 version.
Here are some benchmarks for a 1.5 GHz Raspberry Pi 4, using openssl speed -evp <type> first with and then without -decrypt:
Before

type
16 bytes
64 bytes
256 bytes
1024 bytes
8192 bytes
16384 bytes

aes-256-cbc
20985.17k
40250.30k
41440.43k
41834.15k
41945.77k
41899.35k

aes-256-cbc
27709.77k
29490.15k
30024.11k
30124.03k
30203.90k
30206.63k

aes-256-ctr
25902.21k
28224.73k
29000.96k
29195.26k
29253.63k
29261.82k

aes-256-ctr
26052.76k
28445.89k
29051.39k
29178.88k
29253.63k
29256.36k

aes-256-xts
12040.37k
18575.40k
21351.51k
22141.61k
22421.50k
22435.16k

aes-256-xts
13714.33k
23058.97k
27679.66k
29090.82k
29521.24k
29545.81k

After

type
16 bytes
64 bytes
256 bytes
1024 bytes
8192 bytes
16384 bytes

aes-256-cbc
46384.37k
54493.12k
64383.74k
69976.41k
71789.23k
71931.22k

aes-256-cbc
26784.13k
29198.31k
29956.35k
30095.29k
30198.44k
30190.25k

aes-256-ctr
44068.21k
53480.06k
74281.22k
82495.83k
85330.60k
85475.33k

aes-256-ctr
43571.85k
53088.87k
74143.91k
82298.88k
85502.63k
85535.40k

aes-256-xts
15152.73k
25001.58k
58084.27k
66503.34k
70372.01k
70533.12k

aes-256-xts
16100.20k
29117.95k
68045.31k
78810.11k
82823.85k
83077.80k

This demonstrates a significant speed-up in all cases except CBC encryption (which by its nature is impossible to parallellise across multiple crypto blocks in the manner performed by bit-slicing).
The make test suite passes.
A separate PR #14592 has been raised to apply the equivalent change to master.
One thing that I noticed during debugging is that the make test suite occasionally calls the functions with identical input and output pointers. The C prototypes are defined by the types cbc128_f and ctr128_f in modes.h and struct EVP_AES_XTS_CTX member stream in e_aes.c. In all these cases, the in and out arguments to the function pointers do not feature a restrict qualifier, so this is a valid way to call them as far as a C compiler is concerned.
However, I'm aware that the AArch32 implementations (and doubtless many others) do not honour calls with pointers that alias in any other manner than strict equality - in other words, if the input and output buffers only partially overlap. At least for now, this is also the case with my AArch64 implementation. Since the input and output data are of identical size, this could be handled by memmoveing the source to the destination, then performing in-place de/encryption at the destination address. Since this would be a fix required in many places, I wonder whether it would be better implemented as a generic wrapper in some way?
The other course of action, of course, is to leave things as they are. But in that case, may I suggest that it's documented somewhere that identical in and out pointers are permitted, but that is the only form of pointer aliasing that is?

We will need a version of this that goes into master, we put changes into master and then other branches.
OTC: should this be merged to 1.1.1?
I've added the help wanted tag in the hope that somebody who understands ARM64 assembler can help review this.

Not sure this can be treated as pure bug fix (for the 1.1.1 merge).

It would seem to be like some of the other performance enhancements we back ported: isolated to a specific architecture that's not well supported.  It's not quite the same, I'll put an OTC decision on this.
Regardless, we need this on master first.

This PR is in a state where it requires action by @openssl/otc but the last update was 30 days ago

The OTC has made the decision that this should not be included in 1.1.1


How to override apache_vhosts and mysql_databases with dynamic values?

I've got Drupal VM up and running but now I'm getting greedy and hoping to extend it to create a complete environment by restoring database backups. These tasks will require additional config info beyond what is provided for in config.yml and I was hoping to keep all the config info in one place, so I thought I could create my own settings file, create some tasks in pre-provision.yml to set some variables, and then use those variables in config.yml. Then, in post-provision.yml, I could use some more of the variables for tasks such as restoring the databases and creating settings.php from a template. I'm new to both Ansible and YAML so I'm not sure if this is even possible. If it is, I'm struggling with the syntax to make it work.
The standard config.yml defines apache_vhosts and mysql_databases like this:
apache_vhosts:
  - servername: "intranet.dev"
    documentroot: "/var/www/intranet.dev/httpdocs"
    extra_parameters: "{{ apache_vhost_php_fpm_parameters }}"
  - servername: "extranet.dev"
    documentroot: "/var/www/extranet.dev/httpdocs"
    extra_parameters: "{{ apache_vhost_php_fpm_parameters }}"

mysql_databases:
  - name: "intranet_db"
    encoding: utf8
    collation: utf8_general_ci
  - name: "extranet_db"
    encoding: utf8
    collation: utf8_general_ci

I have a my-settings.yml that contains this:
my_sites:
  - name: "My Intranet"
    env: intranet
    alias: intranet.dev
    docroot: "/var/www/intranet_files/httpdocs"
    db_name: intranet_db
    db_dump: /srv/dumps/intranet_dump.sql.gz

  - name: "My Extranet"
    env: extranet
    alias: extranet.dev
    docroot: "/var/www/extranet_files/httpdocs"
    db_name: extranet_db
    db_dump: /srv/dumps/extranet_dump.sql.gz

And in my pre-provision.yml file I'm doing this:
- name: "Include my site-specific info"
  include_vars:
    file: "my-settings.yml"

- name: "Set my_vhosts_entries variable"
  set_fact:
    my_vhost_entries: "{{ my_vhost_entries | default([]) +XXX }}"
    with_items: "{{ my_sites }}"

- name: "Set my_db_entries variable"
  set_fact:
    my_db_entries: "{{ my_db_entries | default([]) + YYY }}"
    with_items: "{{ my_sites }}"

This is working to the point where my settings file is being read and the my_sites list is available, but I don't know how to use its values to create the my_vhost_entries and my_db_entries variables. I have fiddled around with all sorts of permutations for XXX and YYY but I'm clutching at straws and really don't know what to put in. What I'm hoping to end up with is two variables, my_vhost_entries and my_db_entries, that I can use in config.yml, like this:
apache_vhosts: {{ my_vhost_entries }}
mysql_databases: {{ my_db_entries }}

Is this even possible, and if so, what should I use instead of XXX and YYY in the pre-provision file above?
Finally, I don't want to push my luck but if someone could suggest the code for a task to restore the databases in post-provision.yml that would be greatly appreciated :-)

Wouldn't the easiest way be to add db_dump or any new "important" fields to each of mysql_databasesitems and create a playbook that can be run independently.  Not only during provision.
With a task , note following is a pseudo code more or less.
- name: "import database"
  command: >
      "drush @[site].[env] ah-db-import --db={{ item.name }} --drop  --force {{ item. db_dump }}"
    with_items: "{{ mysql_databases }}"

Just add new keys to the mysql_databases or apache_vhosts so that they don't conflict with roles existing parameters.
I personally use capistrano or shipit js tasks that can be called like bundle exec cap db:pull that do various things like, connects to the remote and dumps the database, gets it locally, replaces production urls to development urls, change admin pw to something easier, put payment methods to development mode etc.

Thanks, such a simple and good idea. It works great except for one tiny problem. It's not possible to keep all of the info in the mysql_databases list. Some values -- server name, alias, and document root -- must be specified in the apache_vhosts list.

If you absolutely want to use your own custom list to set the values, then why use the set fact in your set fact to set the.
Afaik, i mean that I haven't double checked, you can't do this:
apache_vhosts: {{ my_vhost_entries }}
mysql_databases: {{ my_db_entries }}

as the config.yml is read quite early, but what you could do in your pre task is to set the fact 'mysql_databases':
- name: "Add my db values to the mysql_databases"
  set_fact:
    mysql_databases: "{{ mysql_databases|default([]) + [ {'db_name': item.name} ] }}"
    with_items: "{{ my_sites }}"

previous is totally untested.

That's it exactly! The variables defined in config.yml are available in pre-provision.yml, not the other way round. Blindingly obvious now that you mention it - thanks :-)


Clarify/Evaluate role of corelibc and MUSL: DO NOT EDIT!!!

What is LIBC ?
For this discussion, libc is defined as an implementation of a C library as seen in various Linux, Unix, Android, OS-X platforms.
A libc provides the following functionality

fully compatible implementation of ISO C standards (89/99 etc)
mostly compatible implementation of POSIX standards
OS specific functionality and extensions

libc does not require that there exist a single binary/library that contains the entire implementations.For example posix threads exist in a separate library pthreads.
For OE, we are dealing with a subset of libc functionality since not all functionality makes sense in an enclave and not all functionality is immediately relevant.
Some popular OS (e.g Mac OS X) are posix certified, whereas other popular OSes (Linux, Android) are mostly POSIX compliant. What this means is that the libc for these mostly POSIX compliant platforms are heavily based on POSIX, but may have known and important differences from POSIX.
System Call ABI
The mostly POSIX like functionality implemented by Linux and its derivatives are called system calls.
Often each kernel syscall function (e.g. Sys_open) provides an almost compatible implementation of a POSIX function (e.g. open) and is wrapped by the user space GLIBC function that has the POSIX name (e.g. open).
The behavior of a Linux system call can be obtained via man 2:
$ man 2 open | less
OPEN(2)                                                                          Linux Programmer's Manual                                                                         OPEN(2)

NAME
       open, openat, creat - open and possibly create a file

...
DESCRIPTION
       The open() system call opens the file specified by pathname.  If the specified file does not exist, it may optionally (if O_CREAT is specified in flags) be created by open().

The POSIX behavior for the same function can be looked up via an online reference http://pubs.opengroup.org/onlinepubs/9699919799/
syscall instruction
Various processors provide instructions to transfer control to and invoke functions in the kernel.
In x64, this is the syscall instruction, in ARM64 it is the svc #0 instruction.
http://man7.org/linux/man-pages/man2/syscall.2.html lists the "syscall" instructions used on various processors.
The syscall instruction in various processors invokes a OS handler that implements a specific (mostly) posix functionality at kernel privilege. The instruction also provides various guarantees about registers, flags e.t.c.
For example, the syscall instruction on x64 provides the following behavior and guarantees:

SYSCALL invokes an OS system-call handler at privilege level 0. It does so by loading RIP from the IA32_LSTAR MSR (after saving the address of the instruction following SYSCALL into RCX). (The WRMSR instruction ensures that the IA32_LSTAR MSR always contain a canonical address.) SYSCALL also saves RFLAGS into R11 and then masks RFLAGS using the IA32_FMASK MSR (MSR address C0000084H); specifically, the processor clears in RFLAGS every bit corresponding to a bit that is set in the IA32_FMASK MSR.

LIBC syscall function
The syscall instruction is generally wrapped by the platform's LIBC via a syscall function/intrinsic.
       #define _GNU_SOURCE         /* See feature_test_macros(7) */
       #include <unistd.h>
       #include <sys/syscall.h>   /* For SYS_xxx definitions */

       long syscall(long number, ...);

The syscall function itself provides various guarantees:

syscall() saves CPU registers before making the system call, restores
the registers upon return from the system call, and stores any error
code returned by the system call in errno(3) if an error occurs.

LIBC POSIX functions
LIBC generally provides thin wrappers of the kernel system calls by using the LIBC system call function.
http://man7.org/linux/man-pages/man2/syscalls.2.html

Often the glibc wrapper function is quite thin, doing little work
other than copying arguments to the right registers before invoking
the system call, and then setting errno appropriately after the
system call has returned.

There are also exceptions where the LIBC function is more than a thin wrapper

Sometimes, however, the wrapper function does some extra work before
invoking the system call.  For example, nowadays there are (for
reasons described below) two related system calls, truncate(2) and
truncate64(2), and the glibc truncate() wrapper function checks which
of those system calls are provided by the kernel and determines which
should be employed.

or cases where the LIBC function does not call the corresponding system call
$ man 2 signal | grep sigaction
By default, in glibc 2 and later, the signal() wrapper function does not invoke the kernel system call.  Instead, it calls sigaction(2) using flags that  supply  BSD  semantics

Call chain for LIBC functions
In general calling a LIBC function (mostly posix) leads to the following chain of call:
LIBC open  ->  LIBC syscall function  -> processor syscall instruction  -> kernel Sys_open system call
Note that the kernel syscall implementations are guarded by both the syscall instruction as well as the LIBC syscall function, both of which provide register preservation and other guarantees across the user space to kernel transfer of control.
What is MUSL?
From MUSL faq

musl is a “libc”, an implementation of the standard library functionality described in the ISO C and POSIX standards, plus common extensions, intended for use on Linux-based systems.
... musl is a new general-purpose implementation of the C library. It is lightweight, fast, simple, free, and aims to be correct in the sense of standards-conformance and safety.

For our purpose, MUSL is a replacement of Linux GLIBC. However it may not be 100% behaviorally equivalent of GLIBC. Additionally MUSL claims to be lightweight, fast, simple, free, and aims to be correct in the sense of standards-conformance and safety.
Using MUSL would lead to the following call chain where MUSL becomes the LIBC:
MUSL open  ->  LIBC syscall function  -> processor syscall instruction  -> kernel Sys_open system call
Enclave syscall function hook/
Since syscall instruction is not supported within SGX enclaves, OE provides an implementation of the LIBC syscall function that instead of executing the syscall instruction, dispatches to the OE syscall implementations
https://github.com/microsoft/openenclave/blob/eac946aaec2a71e7d48283bd025ee84aed10f9f5/posix/syscall.c#L37-L54
and
https://github.com/microsoft/openenclave/blob/eac946aaec2a71e7d48283bd025ee84aed10f9f5/libc/sgx/syscalls.c#L226-L251
Note: Currently the OE syscall function does not provide the same guarantees (e.g register save restore as described by http://man7.org/linux/man-pages/man2/syscall.2.html

Be careful to not assume that the term "syscall" means Linux.  Other OS's use the same term as well, so it would be incorrect to use the term "syscall" by itself in a way that is Linux-specific.  It's safer to say "Linux syscall" if you mean Linux specific behavior.

@dthaler Good point. Will rephrase. Am capturing my thoughts/understanding for now in this issue.
Can you point me to TrustZone documentation? I would like to know what kind of library functions the enclave has access to - is it POSIX or some custom flavor of LIBC.

Your question is really about OP-TEE not TrustZone per se.  https://wiki.linaro.org/WorkingGroups/Security/OP-TEE#What_API.27s_has_been_implemented_in_OP-TEE.3F and https://optee.readthedocs.io/ explain that it implements the GlobalPlatform (not POSIX) APIs.  That said, OP-TEE also includes native support for a limited number of POSIX APIs which you can see in the headers in this directory: https://github.com/ms-iot/optee_os/tree/ms-iot/lib/libutils/isoc/include

@Thanks! Very useful.

@dthaler Thanks! Very useful.


runtime: recognize .busted files as lua filetype

Are these file literally called ".busted"?  So you can only have one per directory, and they are hidden files?

Are these file literally called ".busted"? So you can only have one per directory, and they are hidden files?

From what I understand in the usage section, the config files are literally .busted, I'm presuming they are hidden (with leading '.'), and it seems you create one in the root (doesn't say whether it supports more than one per directory).

Are these file literally called ".busted"? So you can only have one
per directory, and they are hidden files?

From what I understand in the
usage section, the config
files are literally .busted, I'm presuming they are hidden (with
leading '.'), and it seems you create one in the root (doesn't say
whether it supports more than one per directory).

OK, the section "Predefined Busted Tasks" explains it.
The test fails, since ".busted" gets filetype "lua", but the test
expects the filetype "busted".  So should the filetype detection be
adjusted or the test?
A quick look at the docs suggest that this .busted file has Lua syntax,
but follows test specs with a certain format.  What we often do in such
cases is use a specific filetype, and have the indent/syntax/filetype
plugin files load the more generic file type plugins.  That allows for
tuning to this specific filetype when needed.
--
My Go, this amn keyboar oesn't have a .
/// Bram Moolenaar -- @.*** -- http://www.Moolenaar.net   \
///                                                                      \
\\        sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ ///
\\            help me help AIDS victims -- http://ICCF-Holland.org    ///

@brammool I've changed it now to just put .busted in the correct spot in the test file, sorry about that, it's completely lua, no extra need for distinct indent/syntax/ftplugin rules.


I have a question regarding data preprocessing.

Hello,
I raise the issue because I have a question during data preprocessing.
fisrt.
How should I run the matlab file? Should I run it using octave-cli in ubuntu?
second.
There is a parameter called dir_ref_in in the prepare_data_for_wav2vec.m file, but I don't know which one to put in here. Should I insert a file path in txt format like wavListFile?

Hi, thanks for taking an interest.
We only used MATLAB. But I've just gone through the code and checked it in Octave too. It needed a few tweaks (some unsupported functions, etc.), but it should work now, at least in Octave 6.4.0 on Ubuntu (that's the version currently available in the Ubuntu 22.04 package repository). However, I cannot guarantee that everything will work 100% the same as in MATLAB - I only tested it on a few short audio files.

How should I run the matlab file? Should I run it using octave-cli in ubuntu?

To run prepare_data_for_wav2vec in Octave, either use Octave in interactive mode, like this:
$ octave
octave:1> prepare_data_for_wav2vec('/some/path/wav_list_CALLHOME.txt', '/some/path/audio_out', '/some/path/CALLHOME/RTTM', '/some/path/w2v2_ref_VAD_out', 'VAD', 'dataset', 'CALLHOME', 'refFileSuffix', '_RTTM.txt')

Or if you need to call it from another script, this should work:
octave --eval "prepare_data_for_wav2vec('/some/path/wav_list_CALLHOME.txt', '/some/path/audio_out', '/some/path/CALLHOME/RTTM', '/some/path/w2v2_ref_VAD', 'VAD', 'dataset', 'CALLHOME', 'refFileSuffix', '_RTTM.txt')"

There may be other ways to do it, but like I said, we use MATLAB, so I'm not too familiar with Octave.

There is a parameter called dir_ref_in in the prepare_data_for_wav2vec.m file, but I don't know which one to put in here. Should I insert a file path in txt format like wavListFile?

dir_ref_in is the path to a directory where you have the reference annotation files, in the RTTM format,
(like for speaker diarization). There should be a separate reference file for each WAV file, with a matching name. By default, the script looks for files with a .rttm extension, but you can change it to anything else, like in the example above ('refFileSuffix', '_RTTM.txt'  will look for files named <something>_RTTM.txt")

Thank you for your reply @mkunes!

Thank you for your reply @mkunes!
I have an additional question.
This is a question that occurred when I first encountered speaker diarization like VAD.
{"path":"/path/CMA01_all.16kHz_t0-30.wav","label": [...]}
{"path":"/path/CMA01_all.16kHz_t30-60.wav","label": [...]}

If you look at the file name in the path item here, it says "~t0-30.wav", "~t30-60.wav".  Looking at most of the data, there are a lot of voices that go over 20 to 30 minutes, but if you put that voice at once, it takes a lot of load, so are you cutting the voice on purpose? If you cut it, is there a standard for cutting it?


Publishing to crates.io

GitHub and some other tree-sitter consumers (the Lapce editor comes to mind) consume tree-sitter parsers through Rust crates.
@patrickt would be happy to set up the crate but would like to add us as maintainers of the package. What do you think @jonatanklosko? (And I imagine you would like to be a crate maintainer as well? And maybe @josevalim?)

Sounds good, please go ahead! I've just signed into crates, so feel free to add :)

Along these same lines it would be nice to publish the generate JavaScript package to NPM for easy consumption by JS projects.

Published v0.1.0.


Add support for Yiddish (yi) language

https://trello.com/c/cDsKUvYY/2652-new-translation-option-yiddish
⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠

Looks like there's a failing test.  Is there something else that needs adding to specify this is a right-to-left language?

Looks like there's a failing test. Is there something else that needs adding to specify this is a right-to-left language?

Yes, there was one more test that needed updating 👍


Update PopoverLink component

This pull request addresses #30.
It also extracts some functionality into a PopoverTrigger component that can be used to display a popover using a different triggering mechanism.

Two things I found:

The popover title doesn't appear to be working now.
The regular popover without the focus trap doesn't close when clicking anywhere outside the popover anymore, only by clicking the link.

@Darrken Good catch. those two issues should be fixed now.


DSA : Next Greater Element

Question : Given an array. Find the next Greater Element for every element in the array and return the new arrary

/assign


Failed test with harness returns Instance of 'TestResponseBody instead of meaningful data

Aqueduct Version: 3.0.0-alpha.1
Expected Behavior: Failing a test returns the body of the failed content rather than just Instance of 'TestReponseBody'. Specifically, sending an empty JSON array also causes the test to not return why it differs if it contains a contains matcher.
Actual Behavior:
package:test                             expect
test/search_controller_test.dart 177:5   main.<fn>
===== asynchronous gap ===========================
dart:async                               _Completer.completeError
test/search_controller_test.dart         main.<fn>
===== asynchronous gap ===========================
dart:async                               _asyncThenWrapperHelper
test/search_controller_test.dart 176:38  main.<fn>

Expected: --- HTTP Response ---
          - Status code must be 200
          - Headers can be anything
          - Body after decoding must be:

            contains 'tags'
          ---------------------
  Actual: TestResponse:<-----------
          - Status code is 200
          - Headers are the following:
            - content-encoding: gzip
            - content-length: 22
            - x-frame-options: SAMEORIGIN
            - content-type: application/json; charset=utf-8
            - x-xss-protection: 1; mode=block
            - x-content-type-options: nosniff
            - server: aqueduct/1
          Instance of 'TestResponseBody'
          -------------------------
          >
   Which: the body differs for the following reasons:

Note that the extra whitespace at the end is part of the data it returns, not my formatting.
Steps to reproduce:

Have an route that returns JSON data:

router.route('/').linkFunction((req) async => new Response(200, null, []));

Create a test that the return JSON data fails on.

test('GET root of website', () async {
  expect(
      await harness.publicAgent.get('/'),
      hasResponse(200, body: contains("tags")));
});

Thanks for filing. Adding reference information here for the forthcoming fix.
TestResponseBody must implement its toString method to return the decoded body. Previous to this regression, TestResponse.toString accessed the decoded body, but now directly references the body's toString. There is no test coverage to ensure that the decoded body are included in the failure. This coverage needs to be added.

The decoded body will now be part of the output. I'm leaving this open w.r.t. the empty list not showing the 'differing reasons'. This may be something in package:matcher, but it needs to be investigated further.

OK, the remaining issue is that package:matcher does not have output for a contains matcher that does not meet the criteria. Prob makes sense to file at https://github.com/dart-lang/matcher/issues


Fix portal behavior

So apparently Material.isSolid returns true for lava and water? Interesting. To fix that portal spawning will now respect the same material ignore list as random spawning. Additionally portal spawning will now create a valid spawning location on bedrock if there is none. If there is no bedrock, a piece of stone to stand on will be spawned

Also adresses https://github.com/Civcraft/BetterShards/issues/92 and the same issue with pistons

@Maxopoly I rebased and forced this push so it'll be out of sync with your local, but clean merge against current master.
Anything missing from here? Is this tested?

Oh I thought this was already online. Havent gotten a chance to test it, but it's fairly straight forward, so it should be fine

lmao I was telling everyone that the spawning issues were fixed, but we never merged this


[FEA] Replace RowEncoder with ExpressionEncoder for Delta Lake

Is your feature request related to a problem? Please describe.
In Spark 3.5.0 RowEncoder's apply method has been moved to ExpressionEncoder
Describe the solution you'd like
We use this method in the Delta Lake module and we should switch to the new method in versions of Databricks greater than 13.3
Additional context
https://github.com/apache/spark/commit/071feabbd4#diff-bcb03e1769f63da7a6ca53a3bb9c9d9f648d860520fa8de95b680c67d8c89fd9

This will be fixed with compiler failures when supporting Delta Lake on Spark 3.5 which needs Delta Lake 3.0.


Built Executables close straightaway

Windows 10 Enterprise Version	10.0.17134 Build 17134
VS2017 15.8.8
Latest version of bgfx/bx/bimg
I tried to run the build of my project outside VS and it opened up the window but kept being black for some time and then closed. I've moved the project configuration to a property sheet(.props) so I thought I might have missed something. But then I ran the builds in bgfx's debug folder and only the following ran successfully:
HelloWorld, Metaballs, drawStress, nanosvg, C99, DebugDraw.
All the others had the same behavior as mine.
One thing I noticed is that I don't see an ilk file in my Debug folder. But in bgfx, all examples do have it and they fail anyway.
Am I missing something? Have you come across this before?

Looking through some of the .cpps of those that work and those that don't, one thing I can see that looks like a common point is that the examples that work use bgfx::createProgram to load shaders, while the ones that don't use loadProgram from bgfx_utils.

The working directory should be examples/runtime. Those particular examples worked because they don't load any assets.

You're right. As soon as I copied the shader assets to the debug folder I got it working.

Embedded shaders are more for apps that don't have too many of them, or you want to guarantee functionality exist even if file system doesn't.

Yeah it's up to you how to setup that. If you just use a few shaders all the time, it's ok to embed them all. For example I did that in texturev tool. Since it would be silly to require loading shaders before displaying image.


Realm: Kokkos Processors

It's become clear recently that we need explicit Kokkos processors for the FleCSI level one milestone next year as the majority of the GPU code for FleCSI is going to be written using Kokkos. This significantly deprioritizes #570 as VPSC is not going to be used for the FleCSI level one milestone.

We definitely need to do something here.  However, I'm beginning to lean away from having so many processor types.  It leads to trouble when an application mixes different programming models for its leaf asks.  For example, an app with both native OpenMP and Kokkos leaf tasks would be forced to decide up front which CPU cores do OpenMP work and which do Kokkos work, when really the same cores could do either (just not at the same precise moment in time).

I agree with you. I would prefer that Kokkos run unmodified on top of our existing OpenMP and GPU processors. If it were a proper header-only library like Thrust or Agency then it wouldn't have any problems. Mainly we just need to use this issue to make sure that Kokkos works and doesn't trip over itself like it has been with the restrictions that we enforce upon it.

The kokkos branch (https://gitlab.com/StanfordLegion/legion/tree/kokkos) has the beginnings of support for this.  I made an attempt at writing idiomatic Kokkos code here:
https://gitlab.com/StanfordLegion/legion/blob/kokkos/examples/kokkos_saxpy/kokkos_saxpy.cc
and have successfully built and run it with Kokkos' Serial, OpenMP, and Cuda devices.  To get a little confidence that this matches the way real people use Kokkos, I've rigged this example to use the BLAS routines from kokkos-kernels if you build with KOKKOS_KERNELS set to that package's installation location.
The build only works with the Makefile flow so far (no cmake yet), and requires the app's Makefile to set USE_KOKKOS=1 and KOKKOS_DIR to the Kokkos install directory (no support for building Kokkos as part of Legion).  There are a number of limitations with the current version:

Realm's OpenMP support is insufficient for Kokkos's needs, so use the Kokkos OpenMP device without USE_OPENMP=1 and then only use -ll:cpu 1 to avoid angering the external OpenMP runtime.  (On the plus side, it looks like Kokkos might actually be fine with Realm's multiple OpenMP runtime instances once all the right entry points are added to Realm.)
Kokkos's Cuda device support is fundamentally limited to a single GPU, so you must build Realm with USE_CUDA=1 and then use -ll:gpu 1.  You also can't use a CUDA-enabled Kokkos without a GPU.
A Kokkos built with both OpenMP and Cuda devices cannot be initialized properly right now (Kokkos needs all the initialization and the launch of the OpenMP work to happen from the same thread, which doesn't work with Realm's threading model.)

All that said, I think this is far enough along that if folks want to try building Kokkos-using apps against this, it's worth giving it a go.  Now is also the time for folks to look things over and make comments/suggestions about how the interop looks.

What parts of OpenMP are not supported by Realm that Kokkos needs?
Also @ipdemes and @gshipman told me that they don't plan to use Kokkos external views with FleCSI, but instead pass in their own iterator types from FleCSI. They have tested this and apparently it works, but you will have to ask them for more details.

@streichler : should I use https://gitlab.com/StanfordLegion/legion/tree/kokkos branch for our further work with Kokkos?
@lightsighter : Yes, we don't use Kokkos::Views in FleCSI and pass our own iterator types that were adapted for Kokkos.

@ipdemes yes, please give it a try and let me know how it goes...  if you need these changes applied on top of some other branch (e.g. control_replication), that can be arranged
regarding flecsi's custom iterators, do you construct those directly from legion accessors, or convert the legion accessors to raw pointers and then into flecsi iterators?

Also, @ipdemes do custom iterators work on GPUs too?

@streichler : Yes, we need this to be applied to the Control-replication branch before I can try this.

regarding flecsi's custom iterators, do you construct those directly from legion accessors, or convert the legion accessors to raw pointers and then into flecsi iterators?
We get a raw pointer from legion and use it in our custom iterators.

@lightsighter : yes, we made them work for GPU as well. At least a simple unit test that uses them on GPU pass. I am working on making the test more complex

@ipdemes I've rebased the kokkos branch to sit on top of control_replication.  I'll back-port things as needed to master later.

Status update: We're able to build against the latest Kokkos develop branch with any combination of OpenMP and CUDA support.  Remaining work before it can be merged into master is to do a cleanup pass of the build flow.  (Kokkos has completely changed their makefile-based flow, and the cmake flow has probably more warts than it needs.)

@streichler : thank you for an update.

Kokkos support has been merged into the master branch with commit 61cf62e.  Note that it is only available through the cmake build, as Kokkos no longer supports building against an installed version via a Makefile.


PR: Generate widgets' toolbars from the actions in their context menu & make toolbars toggleable

the below description has been updated several times...
This is one of the things discussed in issue #2353.
Also relevant is: pending pull #2288 and merged pull #2426.
TODO:

[x] basic class/factory methods to make the context-menu => togglable-toolbar possible
[x] refactor File Explorer widget with new system
[x] refactor Outline Explorer widget with new system
[x] refactor Help (previously known as "Object Inspector") widget with new system - requires support for multiple toolbar "modes" (qtstacked) and combo boxes (custom ComboAction, subclassed from QWidgetAction)...there are a few bugs still with the OI.
[ ] refactor Variable Explorer widget with new system - a more difficult job, lets leave it for now
apply to other widgets?

I have created a helper widget called WidgetInnerToolbar and a utility function for constructing instances of that widget from a context menu - context_menu_to_toolbar.  For the Object Inspector I had to add some more features, such as support for switching between multiple toolbar "modes" and supporting arbitrary subclasses of QWidgetAction, such as the custom made ComboAction.
The idea is that WidgetInnerToolbar can be registered as a nearly-proper toolbar using the new register_toolbar method of SpyderPluginMixin.  It then takes part in the global toggling on/off of toolbars.  It also seems a lot neater to collect together all the actions in one place (the context-menu) and then use that to populate other places (the toolbar).  I decided to do it this way round because in all cases the widgets seemed to have a "main child" widget that already had its own context-menu, so it seemed easier to add to that and then build the toolbar from the amalgamated context-menu.
This is what the file explorer's context-menu and toolbar look like (note the name|size|type bit is not actually part of the toolbar  -I should probably have cropped it out here):

This is what the outline explorer looks like (with toolbar hidden/showing):

And this is the help widget's toolbar and context menu. Note there are two modes: source/plain-text and rich-text.

@goanpeca, would you mind to review this one?

Since this PR is already touching quite a few files I'd prefer to stop here if possible and leave the other widgets for later - both the variable explorer and object inspector are more messy to deal with, but should be reasonably self-contained projects.

I will, but on the weeken!

I got a bit carried away and decided to tackle the object inspector.  It basically works now, with a few minor bugs in the history-combo interations.  I have updated the original post with a new description and more screenshots to explain the state of this PR.
In terms of fixing the remaining OI bugs, I guess I will aim to do that in the near future, but I should say that I never quite understood all the expected behaviors of the original widget...both the code itself and the UX were a bit all-over-the-place...which is to say that maybe a more general refactor of the OI is merited (but not something I want to do here if possible).
@goanpeca, @ccordoba12 - if you have a chance to try this out and give me some feedback that would be good...As I said before, this PR touches quite a lot of files (11 currently), a few in fairly major ways (the three widgets) so it would be a great to get it processed quickly-ish..although that never ends up being easy I guess.

@d1manson, tests are failing for this one, please review the Travis log :-)

@ccordoba12 travis is happier now, although fix was a bit hacky.
Note that I'm not expecting you guys to be 100% happy with the code as it is, there are a couple of hacky aspects to it (e.g. import statements within functions, where global import wasn't working..not a big deal performance-wise because the functions should only be called a handful of times at startup, but still rather ugly code).
Mostly I was hoping for feedback on the functionality and possibly some suggestions on improving the way I've structured the code.

@d1manson can you rebase this?

@goanpeca  I've rebased.
Travis is passing but AppVeyor is giving a meaningless Command exited with code 1 error.

Thanks, @ccordoba12 can you take a look?

The error is real (I rebuilt the PR to verify that! :-)
The error code means that codeeditor just crashes when running its test. So you need to run the test locally to see what's happening.

@ccordoba12  I've installed 64 bit conda and setup a python 3.5 environment. When I run the command:
python "spyderlib\widgets\sourcecode\codeeditor.py"
It just launches a standalone instance of an editor widget.  This is the same whether I am on master branch or my PR branch. Other tests (such as ...\base.py) run and terminate within a second or two (without complaint).
What am I doing wrong?
P.S. I'm a bit of a noob when it comes to CI testing.

I dunno what was wrong, but following the latest rebase it's now working again.

@d1manson again can you merge with master (or rebase..) there seem to be some conflicts...
Also what is the status of this PR?

Closing because (although interesting) we don't plan to go for this.


bookmark feature

Will require db migrations

Hey @hkirat Your is is responding with 404 here, please checkout.

Hello @hkirat, the screenshot image is not visible.

Hey @hkirat can I please work on this???

Hey guys I am really new to this thing and i have a feeling that i can contribute somewhere and make my first contribution can u guys help me in making my first merge @devsargam & @AbdullahKhan08

Updated image

@Vivek-1102 learn and then contribute.

@shivamhwp I think i can do some of the stuffs but ur right i need to practise more than contributing i have still not manage to run the codebase locally can u help me to just to setup locally

are you on 100xdevs discord. if not, join & i'll help you setup it locally.

Two things can be done here:

Allowing the user to set startTimestamp and endTimestamp for the video segment and having them listed in a bookmarks tab. Here, the video is played from the startTimestamp till endTimestamp.

Allowing the user to set startTimestamp and endTimestamp for the video segment and create a whole new video segment and place it in the bookmarks tab. In this case, the video can be downloaded by the user.

How can we proceed on this?
Any more ideas are appreciated for this issue.

@hkirat, is this issue still open? If so, I’d be happy to take it on.

Issue is still open

@Antiarin i'm working on it

@siinghd I have already started man!

@siinghd I have already started man!

i have also, its quite simple but you continue, i will do it quickly and probably ur will be better or if u need help let me know

Had started on working on this feature, but then the repo went AWOL for a while, and got stuck into work. Have completed the basic version of it, willl be completing the full feature if this looks good enough #237


panic: runtime error with enable-health-check-nodeport: "false" and kube-proxy-replacement: probe

Bug report
General Information

Cilium version v1.8.3
Kernel version Linux test-node6 5.7.0-0.bpo.2-amd64 #1 SMP Debian 5.7.10-1~bpo10+1 (2020-07-30) x86_64 GNU/Linux
Kubernetes v1.18.9

How to reproduce the issue
Hello, I got this error:
level=info msg="Enabling k8s event listener" subsys=k8s-watcher
level=info msg="Removing stale endpoint interfaces" subsys=daemon
level=info msg="Waiting until all pre-existing resources related to policy have been received" subsys=k8s-watcher
level=info msg="Initializing node addressing" subsys=daemon
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x1d3aa37]

goroutine 61 [running]:
github.com/cilium/cilium/pkg/service.(*Service).UpsertService(0xc0001a67e0, 0xc0006f9980, 0x0, 0x0, 0x0)
        /go/src/github.com/cilium/cilium/pkg/service/service.go:289 +0xdf7
github.com/cilium/cilium/pkg/k8s/watchers.(*K8sWatcher).addK8sSVCs(0xc00091c160, 0xc000dafb50, 0xc, 0xc000dafb60, 0xc, 0x0, 0xc000605580, 0xc000d98098, 0x0, 0x2)
        /go/src/github.com/cilium/cilium/pkg/k8s/watchers/watcher.go:810 +0x46a
github.com/cilium/cilium/pkg/k8s/watchers.(*K8sWatcher).k8sServiceHandler.func1(0x0, 0xc000dafb50, 0xc, 0xc000dafb60, 0xc, 0xc000605580, 0x0, 0xc000d98098, 0xc0006abce0)
        /go/src/github.com/cilium/cilium/pkg/k8s/watchers/watcher.go:502 +0xa4e
github.com/cilium/cilium/pkg/k8s/watchers.(*K8sWatcher).k8sServiceHandler(0xc00091c160)
        /go/src/github.com/cilium/cilium/pkg/k8s/watchers/watcher.go:545 +0x95
created by github.com/cilium/cilium/pkg/k8s/watchers.(*K8sWatcher).RunK8sServiceHandler
        /go/src/github.com/cilium/cilium/pkg/k8s/watchers/watcher.go:550 +0x3f

My config:
  auto-direct-node-routes: "false"
  bpf-map-dynamic-size-ratio: "0.0025"
  bpf-policy-map-max: "16384"
  cluster-name: default
  cluster-pool-ipv4-cidr: <IP_ADDRESS>/8
  cluster-pool-ipv4-mask-size: "24"
  debug: "false"
  disable-cnp-status-updates: "true"
  enable-auto-protect-node-port-range: "true"
  enable-bpf-clock-probe: "true"
  enable-bpf-masquerade: "true"
  enable-endpoint-health-checking: "true"
  enable-health-check-nodeport: "false"
  enable-ipv4: "true"
  enable-ipv6: "false"
  enable-metrics: "true"
  enable-remote-node-identity: "true"
  enable-session-affinity: "true"
  enable-well-known-identities: "false"
  enable-xt-socket-fallback: "true"
  etcd-config: |-
    ---
    endpoints:
      - https://...
      - https://...
      - https://...
    ca-file: "/etc/cilium/certs/ca_cert.crt"
    key-file: "/etc/cilium/certs/key.pem"
    cert-file: "/etc/cilium/certs/cert.crt"
  identity-allocation-mode: kvstore
  install-iptables-rules: "true"
  ipam: cluster-pool
  k8s-require-ipv4-pod-cidr: "true"
  k8s-require-ipv6-pod-cidr: "false"
  kube-proxy-replacement: probe
  kvstore: etcd
  kvstore-opt: '{"etcd.config": "/var/lib/etcd-config/etcd.config"}'
  masquerade: "true"
  monitor-aggregation: medium
  monitor-aggregation-flags: all
  monitor-aggregation-interval: 5s
  node-port-bind-protection: "true"
  operator-api-serve-addr: <IP_ADDRESS>:9234
  operator-prometheus-serve-addr: :6942
  preallocate-bpf-maps: "false"
  prometheus-serve-addr: :9090
  sidecar-istio-proxy-image: cilium/istio_proxy
  tunnel: vxlan
  wait-bpf-mount: "false"

@gandalfmagic thank you for filling the GH issue, this is already fixed on master and it's going to be fixed once we release 1.8.4 which will happen in the following days.
The PR that fixed this https://github.com/cilium/cilium/pull/13190


Created functionality that allows a user to customize manifest.json

Created functionality that allows a user to customize manifest.json
Description:
This will allow users to customize the display, start_url and short_name (name displayed on andoird ios shortcut) in the manifest.json file.
Documentation updates in PR https://github.com/home-assistant/home-assistant.io/pull/8759
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): home-assistant/home-assistant.io#<home-assistant.io PR number goes here>
Example entry for configuration.yaml (if applicable):
frontend:
  manifest_json:
    display: fullscreen
    short_name: "Home Assistant"
    start_url: /

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass
[x] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Tests have been added to verify that the new code works.

Hi @brezuicabogdan,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!

⚠ I was unable to find a documentation PR (matching this code change) in our documentation repository.
Please, update the documentation and open a PR for it (be sure to create a documentation PR against the next branch) and link 🔗 this PR and the new documentation PR by mentioning the link to the PR's in both openings posts/descriptions.
🏷 I am adding the docs-missing label until this has been resolved.

⚠ I was unable to find a documentation PR (matching this code change) in our documentation repository.
Please, update the documentation and open a PR for it (be sure to create a documentation PR against the next branch) and link 🔗 this PR and the new documentation PR by mentioning the link to the PR's in both openings posts/descriptions.
🏷 I am adding the docs-missing label until this has been resolved.

Updated docummentation in PR https://github.com/home-assistant/home-assistant.io/pull/8759
Also signed the CLA but I see the CLA check still shows failed.

Should we close this PR?

There was no activity for a long time. So I guess close it.


Great template - few newbie questions.

Is there a example for Twitter social icon?
Is it possible to change the font?
Is it possible to change the width, so the left side is reduced a bit? it looks like profile takes a lot of space?

Thanks,
Raj

@rajganeshp

yes that's possible:

[[params.socialIcons]]
icon = "fa-twitter"
title = "twitter"
url = "https://www.twitter.com/username"

yes, you could change that using css. Simply include a custom CSS.
yes, you could change that easily using css too.

@rajganeshp you can change the font like this:
@import url(//fonts.googleapis.com/css?family=Open+Sans);
body{
    font-family: 'Open Sans', sans-serif;
}

Place that snippet in a css file within the assets/css folder and include it as described in the README.md

Thank you so much.
On Fri, Sep 25, 2020 at 2:11 PM Alexander Bilz<EMAIL_ADDRESS>wrote:

@rajganeshp https://github.com/rajganeshp you can change the font like
this:
@import url(//fonts.googleapis.com/css?family=Open+Sans);body{
font-family: 'Open Sans', sans-serif;
}
Place that snippet in a css file within the assets/css folder and include
it as described in the README.md
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lxndrblz/anatole/issues/77#issuecomment-699105340,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACR3WBWVLN3G33YCQCF25QTSHTTNVANCNFSM4RZ4PHFA
.

Is the above snippet changing the blog post font size. I see the date only in the location where it show the "date" in the blog post. Is there a way to change blog posts font. i would like it little bit bigger if possible.

It's changing the font but not necessarily the size. if you want to adjust the font size, then go like this:
.post-content p {
font-size: 14px;
}

You can easily see the results by using the inspector in your browser.

it actually changes some parts of the post like bullets and post.

Which part do you want to increase? Just your date or the whole content?

the whole content will be good. the default font is little bit small.
On Fri, Sep 25, 2020 at 2:48 PM Alexander Bilz<EMAIL_ADDRESS>wrote:

Which part do you want to increase? Just your date or the whole content?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/lxndrblz/anatole/issues/77#issuecomment-699121870,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACR3WBUGRJNAF7TWCBMYXZTSHTXZVANCNFSM4RZ4PHFA
.

if you need, take a loot at my site, https://www.connectthoughts.com. I like the font of the post to be little bigger. I'm not sure which font offers the best readability. Again, you helped a lot, but this is something will be better to have. Thanks again.

Like I said earlier, this can all be done using a custom css script.

However, I won't be providing you with a snippet, as this is outside of the scope of these GitHub issues. Please see the available resources online and tinker a bit around yourself, and you'll should be able to achieve satisfying results.


Add Debugging for the generated api

Description
Hello, i would like to suggest to be able to see the generated api by mswjs/source so i know what to expect and know what's wrong if thing goes wrong. maybe the api will look something like this
import recording from './recording.har'
import traffic from "./recording.har"

const handlers = fromTraffic(traffic)

handlers.debug()

export default handlers

where it will be outputting an array of object containing details of what are the specified api like
[
    { "url": "example.com/hello", "method": "GET", "queryParams": { ... } },
    { "url": "example.com/test", "method": "POST", "payload": { ... } }
]

Alternatives

Hi, @ahmad-reza619. Thanks for proposing this.
The API you are describing actually already exists! It's not a part of handlers but rather the setupWorker/setupServer functions, and it's called .listHanders().
Here's how you use it:
import recording from './recording.har'
import traffic from "./recording.har"

const handlers = fromTraffic(traffic)

export default handlers

import { setupServer } from 'msw/node'
import handlers from './handlers.js'

export const server = setupServer(...handlers)

// This will console log the list of handlers.
// In this case, those handlers will show you what
// MSW generates out of your network archive.
console.log(server.listHandlers())

Relates resources

https://mswjs.io/docs/integrations/browser
https://mswjs.io/docs/integrations/node

ah okay, thanks for the info


Add new Exclusion path for MSBuild in Visual Studio Speedup

I've added the new MSBuild file paths in Visual Studio Speedup.

Your welcome :D


Fix kubernetes client's release job's template

@rohanKanojia subject seems does not match PR changes

@riuvshin : This change is done as per https://gitlab.cee.redhat.com/dtsd/housekeeping/issues/2341 .


Replace mentions of Perl 6 with Raku

https://docs.raku.org/ did not work when I first created this commit, and it looks like there's a string in there I've missed, so I'll tack on another commit to adjust these.


Can you help me in changing the module path directory

Hi,
There is one request for you.
Currently as per your module you have added the adminModule and frontendModule.
I want the dir structure like
app/modules/core/admin
app/modules/core/frontend
Thanks

Hi, new release ar here, try to use the new release maybe it will help you resolve your problems.
Old release just work with phalcon < 2 this new works with phalcon 2.0.

Structure of your file you can set in configuration file.


Simple test with Link component return Cannot update a component (withI18nextTranslation(NextStaticProvider)) while rendering a different component (withI18nextSSR(MyApp))

Describe the bug
1.) When using the own component Link generates an error in the following landing page.
2.) When refresh routed "localhost:3000/es/test" entire page with F5, shows 404 error.
3.) i18n.languages were undefined or empty undefined
Occurs in next-i18next version
Last version.
Steps to reproduce
It is a very basic example that I have not uploaded to any repository. You can look at the code here.
https://www.dropbox.com/s/dy4bco6a25laebu/test-i18n.zip?dl=0
"npm install" and "npm run dev".
Expected behaviour
You must provide a clear and concise description of what you expected to happen.
Screenshots

OS (please complete the following information)

Device: MBP 2020 16
Browser: Firefox 75.0

Additional context
Add any other context about the problem here.

Well, you haven't followed the documentation. You need to either use a custom server, or try out the beta/serverless release.


'Open .' does not work in terminal

Issue Type: Bug
"Open ." does not work in terminal
VS Code version: Code 1.24.1 (24f62626b222e9a8313213fb64b10d741a326288, 2018-06-13T17:41:50.128Z)
OS version: Darwin x64 17.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-2435M CPU @ 2.40GHz (4 x 2400)

GPU Status
2d_canvas: unavailable_softwareflash_3d: unavailable_softwareflash_stage3d: unavailable_softwareflash_stage3d_baseline: unavailable_softwaregpu_compositing: unavailable_softwaremultiple_raster_threads: unavailable_offnative_gpu_memory_buffers: unavailable_softwarerasterization: unavailable_softwarevideo_decode: unavailable_softwarevideo_encode: unavailable_softwarevpx_decode: unavailable_softwarewebgl: unavailable_offwebgl2: unavailable_off

Load (avg)
2, 2, 2

Memory (System)
4.00GB (0.03GB free)

Process Argv
/private/var/folders/yk/1ts81gtx76n2ylr67t095kw80000gn/T/AppTranslocation/49A6D8C2-8101-404F-8EC2-C9AF3155EB38/d/Visual Studio Code.app/Contents/MacOS/Electron

Screen Reader
no

VM
0%

Extensions (11)

Extension
Author (truncated)
Version

html-snippets
abu
0.2.1

vscode-postgres
cko
1.0.13

bracket-pair-colorizer
Coe
1.0.59

vscode-npm-script
eg2
0.3.5

auto-close-tag
for
0.5.6

auto-rename-tag
for
0.0.15

beautify
Hoo
1.3.2

mssql
ms-
1.4.0

material-icon-theme
PKi
3.5.2

Ruby
reb
0.18.0

JavaScriptSnippets
xab
1.7.0

(3 theme extensions excluded)

It opens finder for me at that folder, what's happening for you?

Same, I thought it used to open the folder within the editor so you can
begin writing code. If not, is there a way to do this ?
On Fri, Jul 27, 2018 at 2:49 PM, Daniel Imms<EMAIL_ADDRESS>wrote:

It opens finder for me at that folder, what's happening for you?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vscode/issues/55261#issuecomment-408507279,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Ac5JkqHOuEfT94GRJkI-xPyvJjHZfA3Wks5uK2CvgaJpZM4VkgTp
.

--
Kelechi Agwunobi
Candidate for B.S., Finance
University of Rhode Island | Class of 2016
(401) 602-3171 |<EMAIL_ADDRESS>[image: View my profile on LinkedIn]
http://www.linkedin.com/pub/kelechi-agwunobi/58/385/193/
https://www.linkedin.com/profile/view?id=203968191&trk=nav_responsive_tab_profile_pic

open . is calling finder, you're after code . or code -r .


Remotes/origin/add tailwind and tailwind UI

thanks for the PR!
btw. we use yarn. so we should not commit the package-lock.json file afaik .


Idk how to run locally your website

Hello, I am a junior backend developer and I want to help you to code your website.
As you don't explain how to run your website, I just can't test what I am doing.
Can you explain how to run it ? Tysm for your great work :)

Here is a small commit, what do you think ?
https://github.com/Kienlabadao/COC-Damage-Calculator/compare/main...SNEAXIII:COC-Damage-Calculator:basic-refactor

I'm using vscode with live server extension, so I can run the website locally (while live update every time I make change to the file). Another way is you can host it on github, but you probably will have to update some of the redirect link in order for it to work.

Thanks buddy :)

Look at my PR ^^


How to handle "invisible to Shoes" display properties?

Certain properties aren't easily visible to Shoes. Let's say you set a style for red text in a para. You can easily verify that the style is what you set it to. But how do you make sure it's actually red, short of taking a screenshot or analysing the HTML? Neither of those are within the portable Shoes interface, so it's not clear how Shoes-Spec would check that.
You can check some amount of the layout using display properties (e.g. top, left, width, height) that "feed back" the real values to be visible to Shoes. But those properties are less common than the other kind.

It would be possible for some display services to have optional methods that allow checking. For instance, you could have an optional "can render to HTML" interface that can be queried. But that only helps for HTML-capable libraries, so that's not perfect. And having separate major features in Shoes-Spec (e.g. HTML-only libs) splits the spec in a not-great way.  But to some extent you can divide it into "completely implements Shoes" features like multiple windows or clipboard support, versus features that may be mutually exclusive with each other, such as display-service-specific output parsing (HTML vs native output.)


Async Compute Executors

What
This PR modifies the executor interface to include the following additions:
Start(ctx context.Context, request *RunCommandRequest) error
Wait(ctx context.Context, executionID string) (<-chan *models.RunCommandResult, error)

It then updates the Noop, Wasm and Docker executors to satisfy the new interface requirements. Each of these executor changes needs some review as the changes are more than pure mechanical changes. A handler pattern has been implemented to manage each executors active executions.
This PR updates the BaseExecutor to also include a Start and Wait method, however these methods are not used outside of the BaseExecutor, and are instead called via the BaseExecutors Run method. This allows the ExecutorBuffer to continue using the BaseExecutor as it did before this change.
Call outs

Previously when a docker container was passed an invalid entrypoint/command it would return an error rather than start the execution. There were some tests that made assertions on this. Since starting the docker container is the same as running the job, and we want to run jobs async, it is no longer the case that these errors are returned immediately. They are instead shown when describing the failed executions state. I have modified the required tests to account for this change in behavior.
The ExecutorBuffer triggers job timeouts via context cancellation by passing the Run method a context with a timeout. I am dubious this will continue to work as intended when operating against pluggable executors and suspect it will instead end the client connection to the plugin server. For the time being I have worked around this here and added a TODO comment. IMO we should instead explicitly call the Cancel method on an executor to cancel its operation instead of relying on the passed context. As mentioned in the TODO comment there is more context on canceled job states here
As Ross has already brought attention to here PrepareRunArguments now returns a function that may be called to trigger cleanup of input volumes. We should continue discussion in the linked thread regarding further changes to this design. I believe this is related to some work @simonwo is landing regarding restarts.
WriteJobResults function signature has been modified to no longer return an error, instead the error is embedded (as it already was) in the returned RunCommandResult structure. This change was made to simplify logic around checking errors returned by the method.

It'll also be necessary to update the protobufs with the new interface otherwise the plugins fail to load (as the GRPCClient that is dispensed can't be cast to an executor.Executor impl. This manifests currently as a crash at startup with running devstack with --pluggable-executors.

I don't think I get this just yet. I thought the reason we were making them async was so that we could pick them up and resume them if the compute node goes down. I can't see a way to do that just with Start and Wait, doesn't Start need to be idempotent or we need some way to detect executions already in progress so we can selectively start them?

It'll also be necessary to update the protobufs with the new interface otherwise the plugins fail to load (as the GRPCClient that is dispensed can't be cast to an executor.Executor impl. This manifests currently as a crash at startup with running devstack with --pluggable-executors.

@rossjones this has been done in: 2e1b46d

@rossjones the BaseExecutor.Run method has been made idempotent for duplicate calls to Start here: https://github.com/bacalhau-project/bacalhau/pull/2778/commits/ed60b77ff773b55e276f603885d6b6ebeb821076

Unblocking so you can marge when you're ready in my PM.


Feat/populate company requests

Description
Added a starting point company requests accordion content(not finished yet) component and populated with data.
Related Issue(s)

#49 #46

Verification

[ ] Your code builds clean without any errors or warnings
[ ] Manual testing done (required)
[ ] Relevant automated test added (if you find this hard, leave it and we'll help out)
[ ] All tests run green

Documentation

[ ] User documentation is updated with a separate linked PR in altinn-studio-docs. (if applicable)

Don't need this anymore


Add ManhattanWordDistance meta example

Changes to be committed:
new file:   examples/meta/src/distance/manhattan_word.sg.in
deleted:    examples/undocumented/python/distance_manhattanword.py

#3555
Hi,
This is my first time writing a meta example.
Can anyone review this PR and provide me with feedback?

Hi @braceletboy, thanks for your pr, could you also add the data files please?

@LiuYuHui I used data files that were already present in the shogun-data repository. You can find them here: train and test

Hi @braceletboy, when you port a new meta example, it will produce a new data file, please check this link, if you are porting a new example, please also add the produced datafile so that we can do integration tests automatically, thanks.

@LiuYuHui When I tested and ran the examples locally, it didn't produce a new data file. I did refer to the link you pointed out while I was writing the new example file. I even ran tests on the examples that I created using ctest -R manhattan_word* and all the tests passed.

@braceletboy you can the produced data file in build/examples/meta/cpp/distance.

Okay. Thanks @LiuYuHui
Found the datafile. I have a question though. It seems that latest commit in shogun-data is not being tracked by the shogun repository. Is it alright to just commit and push changes to shogun-data or should I make a commit in shogun as well (so that it tracks the latest changes)? Following is a screenshot of git diff data/ (after did a git checkout master inside the data folder)

you should first make pr to shogun-data, and then updata the commit to shogun.

Hi @braceletboy, it seems like that you didn't update your commit to shogun-data, please follow those steps:
cd shogun/data && git remote add mydata <your data repo>
git fetch mydata

then push this commit to shogun.

@LiuYuHui  I added the commit I made to shogun-data and all checks are failing. I am not entirely sure what is happening. I am a bit new to using submodules - so please bear with me (thanks).

Hi @braceletboy, after
cd shogun/data && git remote add mydata <your data repo>
git fetch mydata

you should checkout your branch in shogun/data
git checkout add_meta_examples

@LiuYuHui  I have done as you have suggested. Also, is there a reason for the swig interface related shogun-ci failing?

@LiuYuHui I have done as you have suggested. Also, is there a reason for the swig interface related shogun-ci failing?

Hi, there is an issue with the building of the interfaces atm. The issues you are seeing here are probably related to that.

@LiuYuHui I have done as you have suggested. Also, is there a reason for the swig interface related shogun-ci failing?

Hi, there is an issue with the building of the interfaces atm. The issues you are seeing here are probably related to that.


[Activation] Fix test sending_from_fifty_addresses_to_one_address

The problem appears to have been that no block was getting mined between node1_sends_funds_to_node2_TO_fifty_addresses and node2_receives_the_funds, so the wait loop in the latter would generally time out without the transaction appearing in the wallet.

This needs further investigation, the underlying problem seems to be that node 2 occasionally does not sync from node 1, so the unconfirmed transaction never appears in the wallet. Mining another block tends to kickstart the syncing process and causes the test to pass, but we should probably fix the sync problem instead.


Fix server side errors and season health check

Resolves #545
Resolves #544

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 10 (100.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.002%) to 96.157%

Totals

Change from base Build<PHONE_NUMBER>:
0.002%

Covered Lines:
7501

Relevant Lines:
7571

💛  - Coveralls


Fixed glitch filter by un-initializing a variable

#299
On line 109 GlitchFilter initialized the this._direction variable to zero.
This variable is the internal version of a setter direction that also writes the uniform cosDir and sinDir values as long as the new direction value is different to the one in _direction
Initializing _direction to zero makes the filter ignore when the direction is set to zero again thus never setting the cosDir and sinDir variable in the shader.
This PR un-initializes the this._direction as it will be initialized in the constructor via the setter direction anyway.

@miltoncandelero could you fix the lint for line length?

did it work?


React Navigation web not compatible with react-app-rewired

"dependencies": {
    "@react-navigation/core": "3.0.0-alpha.19",
    "@react-navigation/web": "^1.0.0-alpha",
    "react": "^16.8.4",
    "react-art": "^16.8.4",
    "react-dom": "^16.8.4",
    "react-native-web": "0.10.0",
    "react-scripts": "2.1.8"
  },
  "devDependencies": {
    "@babel/plugin-proposal-class-properties": "7.3.4",
    "@babel/plugin-proposal-export-default-from": "7.2.0",
    "customize-cra": "0.2.12",
    "react-app-rewired": "2.1.0"
  },

React Navigation works when run with react-scripts start but fails when scripts is replaced with react-app-rewired start
This is config-overrides.js file

Output

I'm not sure that react-app-rewired had ever been working with react-native...it was designed for react (create-react-app), and there are a lot of differences between create-react-app and create-react-native-app.

@dawnmist I didn't mention react-native anywhere.
The project I tried was as per the installation procedure mentioned in create-react-app

This React Navigation: Routing and navigation for your React Native apps?
The library you specifically mentioned is designed for React Native, the screenshot you added for config-overrides.js contains a ton of react-native paths including an alias for react-native to react-native-web, so my understanding was that you were trying to get things working with the web version of react-native.
You've given very little information about the error itself - it looks like an issue somewhere in babel because the stuff it is complaining about is compiled code. Running with react-scripts on its own won't be including all the babelInclude/addBabelPlugins changes you're adding in your config-overrides.js file, so I'd start looking into whether it is one of the babel includes/plugins that you're adding in config-overrides.js that is causing your issue.

When I exclude react-navigation/web from project and run with react-app-rewired, it works fine with config-overrides.js

Closing this.
As this isn't a bug.


Storytelling With Data - Meirav Ben Izhak | PyData Global 2021

Storytelling With Data - Meirav Ben Izhak | PyData Global 2021
https://www.youtube.com/watch?v=dLnUmbUcsN4&t=857s
00:00 Welcome
01:00 About Meirav Ben Izhak
01:30 Data analysis in a Nutshell
03:13 Choosing the right dataset
04:58 Pre-processing the data
05:48 Brainstorming for data analysis
07:18 Prettifying data exploration
08:33 Exploring new ways to visualize
10:05 Going beyond the numbers
12:31 Publish your data analysis work
13:56 QnA session
14:55 QnA-Question 1
16:22 QnA-Question 2
17:05 QnA-Question 3
17:36 QnA-Question 4

Hey! Can you update this to show what the questions actually are?

I struggle with communicating results concisely to business audiences. Any tips on that in clarity and conciseness?

What are the Python packages used for making these visualizations?

(Question not clear. Something related to storing datasets.)

How do you balance time and need for exploratory analysis with stakeholders who are very interested in results right away and how do you emphasize for these results are exploratory rather than precise and actionable results?


[master] Bump KIE 7.55.0.Final

The (build) Optaplanner check is successful.

The (build) Apps check is successful.

The (build) Runtimes check is successful.

The (build) Examples check has failed. Please check the logs.


Compute instances missing?

Did the source pages get changed? I don't see any c3 instances in the lists anymore.

c4 instances are also missing.

Working on a fix for this now. I broke it with the push this morning adding the new P3 instances.


data.js updated and HTML, JS files formatting using Prettier

@NisooJadhav can you mix the conflicts

@aditeyaS conflict resolved


v3.3.0 unable to load map files?

I'm straight up confused. Things were working fine right before I updated, if I downgrade back to v3.2.3 things work fine again.

That is definitely not good. Could you send the whole stacktrace please?

TiledCS.TiledException
  HResult=0x80131500
  Message=An error occurred while trying to parse the Tiled map file
  Source=TiledCS
  StackTrace:
   at TiledCS.TiledMap.ParseXml(String xml)
   at Static.Utilities.InGame.Initialize() in C:\Users\nicol\Desktop\Static\Game\Static\Static\Utilities\Menu.cs:line 49
   at Static.Utilities.Menu..ctor() in C:\Users\nicol\Desktop\Static\Game\Static\Static\Utilities\Menu.cs:line 19
   at Static.Utilities.InGame..ctor()
   at Static.Static.Initialize() in C:\Users\nicol\Desktop\Static\Game\Static\Static\Static.cs:line 48
   at Microsoft.Xna.Framework.Game.DoInitialize()
   at Microsoft.Xna.Framework.Game.Run(GameRunBehavior runBehavior)
   at Static.Program.Main() in C:\Users\nicol\Desktop\Static\Game\Static\Static\Program.cs:line 11

  This exception was originally thrown at this call stack:
    [External Code]

Inner Exception 1:
NullReferenceException: Object reference not set to an instance of an object.

Thanks! Does the inner exception have a stacktrace by any chance?

Hey @pacoo2454
Thanks for the heads up about the object layer. I didn't had one in my test map anymore so I just added one and it went kaboom for me too. So I patched it up and a new version should be on its way in a couple of minutes. :)
With kind regards,
TheBoneJarmer

I've updated to 3.3.1 things seem to be working flawlessly ( so far ) 👍

No problem. That also fixed it for me too! Thanks for the quick update.

Awesome! Glad it works for the both of you. :D


Issue with merge-pdfs while using sort by name and date

Whenever I add the files, if I click on sort by name or date it is duplicating the file instead of sorting.
https://github.com/Stirling-Tools/Stirling-PDF/assets/101550345/4e9d8ae8-4f1c-4ccc-8e9e-6a5073c1de08

@Frooodle here what exactly is the intension behind sort by date functionality.

@Frooodle here what exactly is the intension behind sort by date functionality.

That it would order the existing selected files by their date


Feature request: add bash auto-complete file

Add bash auto-complete file for bash auto completion when TAB is used.

Anyone good with bash auto or tab-completion is willing to contribute a PR?
Any contributions are welcome :heart:


While using markLine autoscale does not work.

Version
4.6.5
Link to Minimal Reproduction
https://stackblitz.com/edit/angular-9-ngx-echarts-yceciu?file=src/app/app.component.ts
Steps to Reproduce

Add data
Try to add markLine to chart,
turn on autoscale
if markLine is greater than max value from data, it is not visable in chart / if You set max value to value of markLine it will cut the chart in not scaled parts

Current Behavior
If I want to scale my chart to equal areas using scale = true with markLine

NO MAX VALUE , MARKLINE SET TO VALUE GREATER THAN MAX VALUE FROM DATA ===> markLine not visable
MAX VALUE SET TO VALUE OF MARKLINE ===> markLine is visable, but chart is not scale properly

Expected Behavior
markLine value is visable and chart is scaled
Environment
- OS:
- Browser:
- Framework:

Any additional comments?
No response

Cannot understand and/or reproduce the problem.
Demo Code based on your example, but without framework (Angular). Looks ok to me....


Add a "Created" column to the pod view.

Also update godeps.
@ghodss @jlowdermilk @bgrant0607

I'm supportive of this change, but:

Doesn't build (hah!)
It's basically impossible to review a gigantic change due to importing a new version of something. Mixing another change with such an update isn't a good idea, in general. Please don't do that.

Ah, it does compile locally, but I think that the godeps update breaks @ head because I wasn't fully sync'd to head.
As for reviewing.  That's why there are two different commits, you can review the first commit for the actual changes, and then basically skip the commit that adds the dependencies.
I could separate that into two different PRs if you really want me to, but that hasn't been the pattern.

merged to head.  it builds clean on my box.  (though godeps is unintuitive at times)

Here's the link to the commit with just my changes, fwiw:
https://github.com/GoogleCloudPlatform/kubernetes/commit/037962093f6d71ee27c473057010cc5900479dc7

hrmph, godep is still wanting to remove something.  It turns out we have a different docker provider human readable duration library already checked in.  Migrated to that.
--brendan

Comments on individual commits get blown away when changes are pushed, so that's not great, either.
LGTM.

LGTM as well. Merging.


Gateway and virtual service in different namespaces not working

Describe the bug
One of our users report that he has to put gateway resource and virtual service that bound to the gateway in the same namespace to get it working.  Is this a limitation (or a bug) we have?  I don't find it documented as a limitation in istio.io (https://istio.io/docs/concepts/traffic-management/#gateways) or api (https://github.com/istio/api/blob/master/networking/v1alpha3/gateway.proto)
This is not desired because he expect infra admin to control gateway resource definition and each team in its own namespace to control its own virtual services.
Version
1.0.x
Environment
k8s IKS

Did this work for you in the end ?

I just tried on istio 1.1.3 to put the bookinfo gateway into the istio-system namespace and kept the virtual service in default with istio-system/ in front of the gateway name. It works fine, but Kiali does report an error. Kiali doesn't seem to have been updated to understand the namespace/ syntax.

Add area/policies and telemetry label since it's a Kiali bug.

cc @lucasponce

@jmazzitelli I'm closing this issue, as the final comment is that this is a Kiali issue. It should be tracked on the Kiali repo.

It sounds a bug in the Kiali validation editor.
@frankbu thanks for reporting this.
Could you confirm which version of Kiali are you using ? Just to confirm that is not already addressed in upstream.

@lucasponce I used the version of Kiali in the Istio 1.1.3 release.

@lucasponce I used the version of Kiali in the Istio 1.1.3 release.

There is an "About" box in Kiali that can retrieve a bunch of version strings to ensure you know what you really are running... but the Kiali that is in 1.1.3 is v0.14. I'm still waiting for the PR to be merged that gets the next 1.1.x release up to a more recent version of v0.16 - see https://github.com/istio/istio/pull/13312

Hello @frankbu,
I think this issue is addressed in upstream as gateway validations support multiple namespaces
https://github.com/kiali/kiali/blob/master/business/checkers/gateway_checker.go#L18
This commit is included from Kiali version v0.16.
I think that should cover the scenario you propose.

This commit is included from Kiali version v0.16.

istio will get this version of kiali as soon as someone merges this PR: https://github.com/istio/istio/pull/13312
it is hit-or-miss when these PRs get merged... I don't know what the criteria is to get things merged into the 1.1 branch. I just create the PRs, I don't merge them :)

@lucasponce @frankbu @douglas-reid This information about gateways needing to have /my-gateway should be updated in this doc here: https://istio.io/docs/reference/config/networking/v1alpha3/virtual-service/#HTTPMatchRequest

Hello @linsun @frankbu I am able to get the bookinfo application to work if the pods, gateways and virtualservices aree deployed in the same namespace as that of istio-ingressgateway.
But If I move bookinfo resources to another namespace, it doesn't work. I've even tried the approach suggested by @frankbu where I create the gateway of bookinfo in the same namespace as istio-ingressgateway and have the virtualservice point to the bookinfo-gateway through istio-system/bookinfo in the gateways field of the bookinfo virtualservice.
Requesting some pointers in debugging this.

By "getting it to work", I mean access the productpage from external traffic through the istio-ingressgateway load balancer.

@tariq1890 Maybe this will help you: https://istio.io/docs/ops/best-practices/traffic-management/#cross-namespace-configuration

@frankbu Thanks for your response. That did not help unfortunately. I have raised the issue here. Requesting your inputs on that:
https://github.com/istio/istio/issues/23347


lazy initialisation of kafka_consumer client

Solves https://github.com/DataDog/integrations-core/issues/7238
User wants to be able to start the check while the broker is down.

Let's remove the release related files but the code looks good


Grafana metrics dashboard in progress request count is negative

Description:
I recently tried out metrics monitoring with prometheus and grafana as mentioned ballerina website. When I import and view the grafana dashboard, In progress request count was always negative and the negative value kept on increasing as I send more requests to the underlying ballerina service.

This needs to be fixed soon since this is the most visible metric in the grafana dashboard.
Affected Product Version:
SL Beta 4
Steps to reproduce:
See description

This issue is specific to the ballerina/http module itself.
Background
We have a method called stopObservationWithContext which allows ballerina/http module to stop an observation manually (without relying on the compiler instrumentation). This was done to allow support to record the status code and then close the observation manually after a resource method had ended when the user wants to use a return instead of caller-respond() call.
Cause
The ObserveUtils.stopObservationWithContext method provided for manually stopping an observation is being called twice. This causes the observability to receive one start observation (in progress requests count + 1) call and two stop observation calls (in progress requests count - 2). This results in the in progress decrement by 1 for each http resource call.
Possible Actions

Investigate in ballerina/http module to figure out why this is being called twice.
Add a guard from ObserveUtils.stopObservationWithContext method to prevent closing an observation twice.


Stop installing setuptools in python 3.12+

This fixes the intent that was meant to happen in #833 of no longer including setuptools (or wheel).
Fixes #952.
If you are using Python 3.12+ and you have build or runtime dependencies on setuptools or wheel, a simple addition to your Dockerfile is all that is needed. (I think longer term, they might make sense as additions to your requirements.txt)
FROM python:3.12
WORKDIR /usr/src/app

### ⬇ this line ⬇ ##########################
RUN pip install --no-cache-dir setuptools wheel
###############################################

# continue your regular installation
COPY requirements.txt ./
RUN pip install --no-cache-dir -r requirements.txt

# ...

I think it might also be worth updating the PR description to give an example of how to restore the previous behaviour, for the small subset of users who are running broken dependencies (that don't correctly list an explicit dependency on setuptools/wheel) or are running pip with build isolation disabled.
For example:
FROM python:3

WORKDIR /usr/src/app

RUN pip install --no-cache-dir setuptools wheel
COPY requirements.txt ./
RUN pip install --no-cache-dir -r requirements.txt

# ...

(this is an adapted version of the Dockerfile usage example listed at https://hub.docker.com/_/python/)

https://github.com/docker-library/official-images/pull/17446 :eyes: (I've verified that works with this PR's images, and fails on the current images)

(Close and reopen to force trigger new CI so it includes our updated test. :bow:  I've also got https://github.com/docker-library/python/actions/runs/10623880671 running fresh on master so we can see the failing baseline.)

Hilariously, thanks to https://github.com/pypa/get-pip/pull/218, my "baseline" test on master is succeeding because now get-pip.py has the same behavior as this PR. :joy:

Now we're being really explicit about it both directions, which feels right. :smile: