pantheon.elementary-iconbrowser: init at unstable-2022-09-24

Description of changes
https://github.com/elementary/iconbrowser
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

To be clear I don't plan to merge this before this has a tag in the elementary repo.

:confused: I rebased this to both #182618 and nixos-unstable and this is what I saw on start up (without starting to select some items from the sidebar):
Probably the same thing that happens in e-calendar?

#182618
nixos-unstable

@ofborg eval
@ofborg build pantheon.elementary-iconbrowser


Timer events

Currently, the screen is only redrawn when an event happens. This is either input or resize.
We most likely also want periodic updates. Enter timer events! ;)

Added in 7af8e1263bbe1aed3c43e40159c543abecb18e20.


Update MD file on new branch 2017-28-30_21-11-10

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix: Update news article paragraph date to div element

Please always provide the GitHub issue(s) your PR is for, as well as test URLs where your change can be observed (before and after):
Fix
Test URLs:

Before: https://main--accenture-newsroom--hlxsites.hlx.page/news/2023/accenture-to-acquire-solnet-to-expand-cloud-first-capabilities-in-aotearoa-new-zealand
After: https://abstract-date--accenture-newsroom--hlxsites.hlx.page/news/2023/accenture-to-acquire-solnet-to-expand-cloud-first-capabilities-in-aotearoa-new-zealand

@raymond-h-dev I created a draft PR for the implementation of article date p tag to div element


zsh: command not found: dotnet

Problem encountered on https://dotnet.microsoft.com/en-us/learn/aspnet/blazor-tutorial/install
Operating System: macos
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

Your dotnet SDK installation might not have finished successfully. Please download the SDK by clicking on the Download .NET SDK button appropriate for your CPU architecture at https://dotnet.microsoft.com/en-us/download (on the macOS tab) and then run/install it on your machine.
If this step was successful you might need to restart your terminal, close and reopen the terminal and run the dotnet command again, please let us know if that helps.


network: Use "one shot" protocol handler.

Add two new NetworkBehaviours, one handling remote block requests and another one to handle light client requests (both local and from remote). The change is motivated by the desire to use multiple substreams of a single connection for different protocols. To achieve this, libp2p's OneShotHandler is used as a protocol handler in each behaviour. It will open a fresh substream for the duration of the request and close it afterwards. For block requests, we currently only handle incoming requests from remote and tests are missing. For light client handling we support incoming requests from remote and also ported a substantial amount of functionality over from light_dispatch.rs (including several tests). However the result lacks in at least two aspects:

We require external updates w.r.t. the best block per peer and currently nothing updates this information.
We carry a lot of peer-related state around.

Both aspects could be simplified by externalising peer selection and just requiring a specific peer ID where the request should be sent to. We still have to maintain some peer related state due to the way libp2p's swarm and network behaviour work (e.g. we must make sure to always issue NetworkBehaviourAction::SendEvents to peers we are connected to, otherwise the actions die a silent death).
Another change implemented here is the use of protocol buffers as the encoding for network messages. Certain individual fields of messages are still SCALE encoded. There has been some discussion about this in another PR (https://github.com/paritytech/substrate/pull/3452), so far without resolution.

Is there any round-trip involved for opening a substream?
Does it increase network traffic?

Is there any round-trip involved for opening a substream?

Opening a new substream involves the use of multistream-select to negotiate the protocol to use with the stream. I think this involves at least 1 roundtrip currently. Version 2 of multistream-select will eventually improve on this.

Does it increase network traffic?

Depending on the multiplexer there might be an increase in control data. For example with Yamux there are WindowUpdate frames to implement flow control and those are sent per stream.

The change is motivated by the desire to use multiple substreams of a single connection for different protocols.

So what motivates this desire then? Extra roundtrips for each request does not sound like a good idea to me.

So what motivates this desire then? Extra roundtrips for each request does not sound like a good idea to me.

The main motivation is de-coupling the gossiping from block requests, so that:

Light clients and nodes in general can make requests without occupying a gossiping slot (which is the case right now). In other words, you wouldn't occupy a gossiping slot anymore while major syncing for example.
Nodes can close their gossiping channel without interrupting all on-going requests.
We can open multiple gossiping channels (for example one only within validators, one for the relay chain, and one for each parachain) without having the problem of which channel to send the request to.

Note that, theoretically, if multistream-select 2 happens, and a better multiplexing such as QUIC happens, then that new system will be very slightly more efficient than what we currently have, as we would no longer transmit the type of message nor the request ID.

I don't see how adding extra network latency can be more efficient.
What exactly is "gossiping slot"?
The current protocol was designed in such a way that parallel requests are possible.
In general I'm OK with using a separate substream for gossiping, but not with opening a new substream for each request/response. One of our major goals is to minimize network latency and data propagation time.

What exactly is "gossiping slot"?

The slots whose number is controlled with the --in-peers and --out-peers options. What the peerset manager decides.

I don't see how adding extra network latency can be more efficient.

Theoretically, there shouldn't be any additional round-trip compared to what we have right now.
Opening a substream is a very cheap operation. A substream is basically equivalent to a request ID.
The problem is that, due to the way the multistream-select protocol is designed, we have to wait for the remote to acknowledge that it supports the protocol we want (eg. "requesting a block").
There is an optimization in place in the code of multistream-select that allows skipping this round-trip, but it unfortunately can't apply here.
As a work-around, we could add a few hacks to the code of multistream-select to remove this round-trip.

sadly, i think we will need to retain a compatibility model since there are at least three other languages (JS, Go, C++) creating a polkadot implementation and thus who we will need to talk to.

sadly, i think we will need to retain a compatibility mode since there are at least three other languages (JS, Go, C++) creating a polkadot implementation and thus who we will need to talk to.

I see. It may still be an option though to convince all these parties to adopt some additional assumptions around the use of multistream-select v1 that are necessary to make the use of it safe with "lazy" negotiation and thus 0-RTT negotiation on substreams, because I don't think it strictly requires any changes to the protocol itself (on the wire), just some additional assumptions on how it is implemented and knowledge of the (fixed set of) protocols being used. See https://github.com/libp2p/rust-libp2p/pull/1212 and https://github.com/libp2p/rust-libp2p/pull/1245 for further detail.

The choice would have to be static, of course, since 0-RTT is only really possible when the "dialer" only supports a single protocol at each level of the protocol stack (i.e. for each upgrade, including the initial multistream protocol)

This I don't quite understand. Is there no way to do a few round-trips in the beginning of a connection to negotiate on what kinds of substreams you could do 0-RTT negotiation for?

@twittner Could you please update to the master branch? We might merge this soon.

Updated and rebased. Ready for review again.

For the sake of not leaving this PR open for a couple more months, I'm going to merge it.
As discussed above, these code paths aren't used by default yet.


SC4S official support for Rubrik

Hello SC4S team. My company uses Rubrik and we need to stream the logs it emits through SC4S into Splunk. Can you please add Rubrik as a supported vendor. I have attached the raw text (obfuscated) from a tcpdump we just did. Please contact me via email if you need anything else.
RubrikRawDataObfuscated.zip
Thanks,
Frank

@fpunzohig,
Could you please answer following questions:

What is the source (what TA is associated to this sample)?
What is the sourcetype and index of the message?
Is there any documentation to refer to this sample to validate the RFC compliance?

@bparmar-splunk. Apologies, as it turns out this data is not specific to Rubrick, these are just Linux OS logs. We are going to get them ingested through SC4S using the nix_syslog key. Before I close this issue though, can I bother you for some instruction on how to ingest data into the nix_syslog key but have the data arrive on a non default port. We would like to have the data arrive via TCP rather then UDP 514 due to the added resiliency of TCP protocol. I have read through all the documentation but can't find anything telling me how to do that.
Thanks in advance,
Frank

@fpunzohig,
You can copy below env variable to env_file.
SC4S_LISTEN_DEFAULT_TCP_PORT=${SC4S_LISTEN_TCP_PORT}
You can also make use of below parser to route your messages:
block parser app-syslog-rubrik() {
    channel {
        rewrite {
            r_set_splunk_dest_default(
                index("netops")
                sourcetype('rubrik:syslog')
                vendor("rubrik")
                product("syslog")
            )
        };
    };
};
application app-syslog-rubrik[sc4s-syslog-pgm] {
    filter {
        program('sudo'  type(string)  flags(prefix)) or
        match('rubrik' value('MESSAGE'));
    };
    parser { app-syslog-rubrik(); };
};

Please validate your usecase and let us know in case of any queries.


fix: use different MContext for every Result

Codecov Report

Merging #228 (e0d0a48) into main (01be522) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

:exclamation: Current head e0d0a48 differs from pull request most recent head b5a9a00. Consider uploading reports for the commit b5a9a00 to get more accurate results

@@            Coverage Diff             @@
##             main     #228      +/-   ##
==========================================
- Coverage   89.90%   89.90%   -0.01%
==========================================
  Files         116      116
  Lines        7490     7488       -2
==========================================
- Hits         6734     6732       -2
  Misses        756      756

Flag
Coverage Δ

e2e.cbl
89.52% <100.00%> (-0.01%)
:arrow_down:

unit.cbl
2.92% <0.00%> (+<0.01%)
:arrow_up:

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

Impacted Files
Coverage Δ

packages/cbl/lib/src/query/ffi_query.dart
96.03% <100.00%> (-0.12%)
:arrow_down:

packages/cbl/lib/src/query/proxy_query.dart
97.18% <100.00%> (-0.04%)
:arrow_down:

packages/cbl/lib/src/query/result.dart
95.79% <100.00%> (+0.07%)
:arrow_up:

Continue to review full report at Codecov.

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


add a parameter to support "interactive constraints"

The upstream dmlc xgboost has a feature called interaction constraints.
This feature is useful to train highly explainable models for high-risk applications like lending. It would be wonderful if TFDF boosting supported a similar option.

Per offline chat, for others interested, this is a simple and almost equivalent approach, by ensembling multiple individual trees, each trained with a subset of features (only one feature in the example):
https://colab.research.google.com/drive/17LEDCwsf1-x2cBKz0J43SES8EDeiy-AB?usp=sharing
Maybe this will be helpful for others, while we don't implement the feature.


Support for Centos7 AMI in China

Environment:

AWS ParallelCluster / CfnCluster version : 2.5
OS: centos7
Scheduler: SGE
Master instance type:t3.xlarge
Compute instance type: c5.large

Bug description and how to reproduce:
As in cn-northwest-1 region there is no centos AMI available, pcluster create command will fail  when i set base_os=centos7. The detailed error message is as following:
Template error: Unable to get mapping for AWSRegionOS2AMI::cn-northwest-1::centos7
I try to make a custom AMI of centos7, but it didn't work either.
Is there any workaround method?
thanks!
Additional context:
Any other context about the problem. E.g.:

configuration file without any credentials or personal data.
pre/post-install scripts, if any
screenshots, if useful
if the cluster fails creation, please re-execute create action using --norollback option and attach /var/log/cfn-init.log, /var/log/cloud-init.log and /var/log/cloud-init-output.log files from the Master node
if a compute node was terminated due to failure, there will be a directory /home/logs/compute. Attach one of the instance-id.tar.gz from that directory
if you encounter scaling problems please attach /var/log/nodewatcher from the Compute node and /var/log/jobwatcher and /var/log/sqswatcher from the Master node

Unfortunately Centos 7 official AMI is not available in China regions and that is the reason why ParallelCluster is not supporting it at the moment.
A workaround can be to import a Centos 7 AMI in cn-northwest-1 and then use the pcluster createami command as described here to create a ParallelCluster AMI that can be then specified as custom_ami in the cluster config.
Just be aware that because of Chinese gov firewalls you might face connectivity issues while trying to build the custom AMI.

I'm going to mark this as a feature enhancement so that we can evaluate native support for Centos 7 AMI in China.
Here is also another request: https://github.com/aws/aws-parallelcluster/issues/1505

Got it! Thanks for you kindly help!

Hi @demartinofra
Do you have any progress for "Support for Centos7 AMI in China"?
Have already CentOS6/7 official AMI in China region (ZHY & BJS) long time ago.
https://awsmarketplace.amazonaws.cn/marketplace/seller-profile?id=d86d613e-d4e3-4746-8dff-baec467169e7&ref=dtl_prodview-xhibnjn5u6kjmz

Adding support for CentOS in China is part of our product roadmap. Unfortunately, we do not have an ETA for this item. While there are some CentOS AMIs available in China, these are not compatible for use with ParallelCluster due to limitations on their reuse and republication. We are working with the CentOS community to make compatible AMIs available in China and will then be able to include support for them inside ParallelCluster.
Originally posted by @nstornetta in https://github.com/aws/aws-parallelcluster/issues/2192#issuecomment-722463000

Hi,
I have copied the image I built in Singapore region to China region as suggested in this. While trying to build the cluster, I got the following error.
Template error: Unable to get mapping for AWSRegionOS2AMI::cn-northwest-1::centos7

Is this specific to parallelcluster compatibility with Centos7 in China region?

Hi @SivaKanishka,
are you setting the parameter custom_ami in the PCluster configuration as described previously here?
The value for custom_ami must be the new AMI id that you got as part of the copy process into the region cn-northwest-1.

Hi @lukeseawalker
Yes, I have set the new AMI id that we created in China region.
Also, I have tried changing the base_os parameter in config file to alinux2 after I got the error I have mentioned in my previous comment. Compute fleet creation is successful and master node creation is initialising, but status check for it is failing with the following error,
Instance reachability check failed

Sorry for the late reply @SivaKanishka,
let's do a step back:
once you have copied the AMI into one of the two China regions, are you able to start an Instance from it and SSH into the instance? Can you please do this test without involving PCluster first?

We are marking this item as closed for the time being.
As indicated earlier in this issue thread, publishing AMIs in a given region requires our team to have a base, official AMI that is eligible for reuse and republication in that region.
To date, this is not the case for CentOS 7 in the China regions. If we are able to make progress with partner teams in having official AMIs eligible for ParallelCluster use, then we will reopen and update this issue.


ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed.

System information

OS Platform and Distribution: Windows 10
TensorFlow installed from: binary
TensorFlow version: 2.2.0
Python version: 3.8.6
Installed using: pip
CUDA/cuDNN version: 10.1/ 7.6.5
GPU model and memory: Nvidia Geforce GTX 1050i TI

Describe the problem
When i import tensorflow like normal it throw an error, i have done the same thing on my laptop and there it all works fine, ik have the exact same code and followed the exact same steps, but on my computer it just fails.
Provide the exact sequence of commands / steps that you executed before running into the problem

open a python file;
import tensorflow as tf
error occurs

Traceback (most recent call last):
File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 29, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 25, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\imp.py", line 242, in load_module
return load_dynamic(name, filename, file)
File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\imp.py", line 342, in load_dynamic
return _load(spec)
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "model_main_tf2.py", line 31, in
import tensorflow.compat.v2 as tf
File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow_init_.py", line 41, in
from tensorflow.python.tools import module_util as module_util
File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python_init.py", line 52, in
from tensorflow.python import pywrap_tensorflow
File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 69, in
raise ImportError(msg)
ImportError: Traceback (most recent call last):
File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in
from tensorflow.python.pywrap_tensorflow_internal import *
File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 29, in
_pywrap_tensorflow_internal = swig_import_helper()
File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 25, in swig_import_helper
_mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description)
File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\imp.py", line 242, in load_module
return load_dynamic(name, filename, file)
File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\imp.py", line 342, in load_dynamic
return _load(spec)
ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed.
Failed to load the native TensorFlow runtime.

I have seen this auto response on other issues, I think it has to do with the CPU bot being compatible, why is that? because I have a gpu shouldn't it just run on my CPU?

@aradox
What is make/model of your cpu?
I suspect your cpu model does not support AVX instructions sets.See hardware requirements
Make sure to download the latest microsoft visual c++ redistributable from here.
.Also, please follow the instructions from to install from Tensorflow website.
Please, check Your CPU/Python is on 32 bits?
Please, refer duplicate issue #43130
Thanks!

Vendor ID         : GenuineIntel
CPU name          : Intel(R) Core(TM) i5 CPU         660  @ 3.33GHz
Microarchitecture : westmere
Vector instructions supported:
SSE       : Yes
SSE2      : Yes
SSE3      : Yes
SSSE3     : Yes
SSE4.1    : Yes
SSE4.2    : Yes
SSE4a     : --
AVX       : --
AVX2      : --
BMI1      : --
BMI2      : --
The system is a 64bit system.
I see that my CPU does not allow for AVX instructions. so what can i do now? I already tried to compile from source but this failed after 67 minutes of compiling.

@aradox
TensorFlow release binaries version 1.6 and higher are prebuilt with AVX instruction sets.
Therefore on any CPU that does not have these instruction sets, either CPU or GPU version of TF will fail to load.
Apparently, your CPU model does not support AVX instruction sets. You can still use TensorFlow with the alternatives given below:
Try Google Colab to use TensorFlow.
The easiest way to use TF will be to switch to google colab. You get pre-installed latest stable TF version. Also you can use pip install to install any other preferred TF version.
It has an added advantage since you can you easily switch to different hardware accelerators
(cpu, gpu, tpu) as per the task.
All you need is a good internet connection and you are all set.
or else try to build TF from sources by changing CPU optimization flags.
Thanks!

System information

OS Platform and Distribution: Windows 10
TensorFlow installed from: binary
TensorFlow version: 2.2.0
Python version: 3.8.6
Installed using: pip
CUDA/cuDNN version: 10.1/ 7.6.5
GPU model and memory: Nvidia Geforce GTX 1050i TI

Describe the problem When i import tensorflow like normal it throw an error, i have done the same thing on my laptop and there it all works fine, ik have the exact same code and followed the exact same steps, but on my computer it just fails.
Provide the exact sequence of commands / steps that you executed before running into the problem

open a python file;
import tensorflow as tf
error occurs

Traceback (most recent call last): File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in from tensorflow.python.pywrap_tensorflow_internal import * File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 29, in _pywrap_tensorflow_internal = swig_import_helper() File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 25, in swig_import_helper _mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description) File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\imp.py", line 242, in load_module return load_dynamic(name, filename, file) File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\imp.py", line 342, in load_dynamic return _load(spec) ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed.
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "model_main_tf2.py", line 31, in import tensorflow.compat.v2 as tf File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow__init__.py", line 41, in from tensorflow.python.tools import module_util as module_util File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python__init_.py", line 52, in from tensorflow.python import pywrap_tensorflow File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 69, in raise ImportError(msg) ImportError: Traceback (most recent call last): File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in from tensorflow.python.pywrap_tensorflow_internal import * File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 29, in _pywrap_tensorflow_internal = swig_import_helper() File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 25, in swig_import_helper _mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description) File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\imp.py", line 242, in load_module return load_dynamic(name, filename, file) File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\imp.py", line 342, in load_dynamic return _load(spec) ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed.
Failed to load the native TensorFlow runtime.

only need for !pip install tensorflow==2.7.0  tensorflow-gpu==2.7.0 --upgrade
to solve hole problem

System information

OS Platform and Distribution: Windows 10
TensorFlow installed from: binary
TensorFlow version: 2.2.0
Python version: 3.8.6
Installed using: pip
CUDA/cuDNN version: 10.1/ 7.6.5
GPU model and memory: Nvidia Geforce GTX 1050i TI

Describe the problem When i import tensorflow like normal it throw an error, i have done the same thing on my laptop and there it all works fine, ik have the exact same code and followed the exact same steps, but on my computer it just fails.
Provide the exact sequence of commands / steps that you executed before running into the problem

open a python file;
import tensorflow as tf
error occurs

Traceback (most recent call last): File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in from tensorflow.python.pywrap_tensorflow_internal import * File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 29, in _pywrap_tensorflow_internal = swig_import_helper() File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 25, in swig_import_helper _mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description) File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\imp.py", line 242, in load_module return load_dynamic(name, filename, file) File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\imp.py", line 342, in load_dynamic return _load(spec) ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed.
During handling of the above exception, another exception occurred:
Traceback (most recent call last): File "model_main_tf2.py", line 31, in import tensorflow.compat.v2 as tf File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow__init__.py", line 41, in from tensorflow.python.tools import module_util as module_util File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python__init_.py", line 52, in from tensorflow.python import pywrap_tensorflow File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 69, in raise ImportError(msg) ImportError: Traceback (most recent call last): File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow.py", line 58, in from tensorflow.python.pywrap_tensorflow_internal import * File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 29, in _pywrap_tensorflow_internal = swig_import_helper() File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\site-packages\tensorflow\python\pywrap_tensorflow_internal.py", line 25, in swig_import_helper _mod = imp.load_module('_pywrap_tensorflow_internal', fp, pathname, description) File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\imp.py", line 242, in load_module return load_dynamic(name, filename, file) File "C:\Users\TastDesktop\AppData\Local\Programs\Python\Python38\lib\imp.py", line 342, in load_dynamic return _load(spec) ImportError: DLL load failed while importing _pywrap_tensorflow_internal: A dynamic link library (DLL) initialization routine failed.
Failed to load the native TensorFlow runtime.

I have a similar architecture as you, and running into the same problem.

@sac-ux It's 2024 and that line gives:
"ERROR: Could not find a version that satisfies the requirement tensorflow==2.7.0 (from versions: 2.16.0rc0, 2.16.1)
ERROR: No matching distribution found for tensorflow==2.7.0"

dll load failed while importing _pywrap_tf2:

@sac-ux It's 2024 and that line gives: "ERROR: Could not find a version that satisfies the requirement tensorflow==2.7.0 (from versions: 2.16.0rc0, 2.16.1) ERROR: No matching distribution found for tensorflow==2.7.0"

same here,,, still looking, please reply to me if you managed to make it work :(


Submissions scarletbright

Node Id: 042cb7d587e12a63
Addresses:
4rov1pw3RbYukW2eRtWp4pY9GADu86dLexMpEm146meAgT7x5Y
3HVNZ5FxukbT1pc5EsuaAGdnKBKRkUbvz2yMsnLjyv9egrADHK
Device: iPhone 6s, MKR42LL/A
Software: iOS 14.0.1

pending:ID1
account1:screenshot-TBC
account2:screenshot-TBC
We cannot fully verify this submission. Please assist us in typing out the account addresses for ID1 in full as text in a comment on this PR. Thank you!
@scarletbright

confirmed:EI1

confirmed:EI5

confirmed:EI5

confirmed:B2

confirmed:B2

confirmed:B3

confirmed:B3

confirmed:B6

confirmed:B6

pending:ID2
We cannot fully verify this submission. Please assist us in typing out the account addresses for ID2 in full as text in a comment on this PR. Thank you!
@scarletbright

pending:ID2
We cannot fully verify this submission. Please assist us in typing out the account addresses for ID2 in full as text in a comment on this PR. Thank you!
@scarletbright

rejected:ID3
reason:We cannot fully verify this submission. It looks like you are trying to submit ID3, however, it seems there is no supporting details.

confirmed:ID4
AccountAddress:4rov1pw3RbYukW2eRtWp4pY9GADu86dLexMpEm146meAgT7x5Y
DeviceDetails:verified

confirmed:ID4
AccountAddress:4rov1pw3RbYukW2eRtWp4pY9GADu86dLexMpEm146meAgT7x5Y
DeviceDetails:verified

rejected:T1
reason:We cannot fully verify this submission. It looks like you are trying to submit T1, however, it seems like there are no supporting details(screenshots).

rejected:T1
reason:We cannot fully verify this submission. It looks like you are trying to submit T1, however, it seems like there are no supporting details(screenshots).

rejected:T1
reason:We cannot fully verify this submission. It looks like you are trying to submit T1, however, it seems like there are no supporting details(screenshots).

but the Submission for T1 says:
submit account addresses for A and B
submit device make and model and OS version

rejected:T1
reason:We cannot fully verify this submission. It looks like you are trying to submit T1, however, it seems like there are no supporting details(screenshots).

but the Submission for T1 says:
submit account addresses for A and B
submit device make and model and OS version

pending:ID2
account1:missing-TBC
account2:missing-TBC
We cannot fully verify this submission. Please assist us in typing out the account addresses for ID2 in full as text in a comment on this PR. Thank you!
@scarletbright

pending:ID2
account1:missing-TBC
account2:missing-TBC
We cannot fully verify this submission. Please assist us in typing out the account addresses for ID2 in full as text in a comment on this PR. Thank you!
@scarletbright

I'm afraid I don't have access to that info anymore, as the app is not working currently

pending:ID2
account1:missing-TBC
account2:missing-TBC
We cannot fully verify this submission. Please assist us in typing out the account addresses for ID2 in full as text in a comment on this PR. Thank you!
@scarletbright

pending:ID2
account1:missing-TBC
account2:missing-TBC
We cannot fully verify this submission. Please assist us in typing out the account addresses for ID2 in full as text in a comment on this PR. Thank you!
@scarletbright

I'm afraid I don't have access to that info anymore, as the app is not working currently

confirmed:B4
address:4rov1pw3RbYukW2eRtWp4pY9GADu86dLexMpEm146meAgT7x5Y
baker:51

confirmed:B4
address:4rov1pw3RbYukW2eRtWp4pY9GADu86dLexMpEm146meAgT7x5Y
baker:51

confirmed:B4
address:4rov1pw3RbYukW2eRtWp4pY9GADu86dLexMpEm146meAgT7x5Y
baker:51

confirmed:B4
address:4rov1pw3RbYukW2eRtWp4pY9GADu86dLexMpEm146meAgT7x5Y
baker:51

rejected:ID1
reason:We cannot fully verify this submission. It looks like you are trying to submit ID1, however, it seems like we cannot find the address1 and address2

rejected:ID1
reason:We cannot fully verify this submission. It looks like you are trying to submit ID1, however, it seems like we cannot find the address1 and address2

confirmed:T2
account1:4rov1pw3RbYukW2eRtWp4pY9GADu86dLexMpEm146meAgT7x5Y
account2:3HVNZ5FxukbT1pc5EsuaAGdnKBKRkUbvz2yMsnLjyv9egrADHK

confirmed:T2
account1:4rov1pw3RbYukW2eRtWp4pY9GADu86dLexMpEm146meAgT7x5Y
account2:3HVNZ5FxukbT1pc5EsuaAGdnKBKRkUbvz2yMsnLjyv9egrADHK

rejected:ID2
reason:We cannot fully verify this submission. It looks like you are trying to submit ID2, however, it seems like we cannot find address1 and address2

rejected:ID2
reason:We cannot fully verify this submission. It looks like you are trying to submit ID2, however, it seems like we cannot find address1 and address2

rejected:ID1
reason:We cannot fully verify this submission. It looks like you are trying to submit ID1, however, it seems like we cannot find address1 and address2

rejected:ID1
reason:We cannot fully verify this submission. It looks like you are trying to submit ID1, however, it seems like we cannot find address1 and address2

confirmed:T3
address:3HVNZ5FxukbT1pc5EsuaAGdnKBKRkUbvz2yMsnLjyv9egrADHK

confirmed:T3
address:3HVNZ5FxukbT1pc5EsuaAGdnKBKRkUbvz2yMsnLjyv9egrADHK

confirmed:T4
address:3HVNZ5FxukbT1pc5EsuaAGdnKBKRkUbvz2yMsnLjyv9egrADHK

confirmed:T4
address:3HVNZ5FxukbT1pc5EsuaAGdnKBKRkUbvz2yMsnLjyv9egrADHK

confirmed:B5
address:4rov1pw3RbYukW2eRtWp4pY9GADu86dLexMpEm146meAgT7x5Y

confirmed:B5
address:4rov1pw3RbYukW2eRtWp4pY9GADu86dLexMpEm146meAgT7x5Y

Form submitted yesterday, April 23rd, in the evening, CET (sorry, I didn't notice the remark about this comment, so can't say the exact time)


Audio and Video Calling

This isn't much an 'issue' as it is a general question but I am a little confused.  The app supports audio and video calls but I do not see anywhere in the app where to do this. I want to test it out with the demo provided but I don't see any buttons to start any calls in the app.

Once you have a contact connected, you should see a call icon in the contact list if your server has setup a STUN/TURN server.
The account from the demo server has the STUN/TURN server configured, so from that contact list, you should be able to call any connected contact.
Let me know if that makes sense, I'm still working on a user guide which would be helpful right about now....

Makes sense! Thanks so much. I've been meaning to check this app out for weeks and had some free time today to get it up and running! So far it's great!

Awesome, please let me know of any issues or features you would like. Thanks again!


Add middle click paste support on linux

Would be great if one can paste by middle clicking.

Maybe xclip shoud be use the PRIMARY section.
This package use the CLIPBOARD section.
http://unix.stackexchange.com/questions/69111/how-to-target-multiple-selections-with-xclip
umm, any idea?

Maybe use both?

nucular has a better implementation, which uses xgb: https://github.com/aarzilli/nucular/blob/master/clipboard/clipboard_linux.go


Input debugger tool

Currently, the only easy way to test your input maps is with the demo scene. I'd like to add an editor window that can be brought up while in play mode in any scene that shows the status of each TButt virtual action.

Done in beta branch.


Dockerize validator and relayer for simple testing purposes

This adds a docker and docker-compose that runs the validator and relayer together with non-secret private keys that are expected to be used only for local testing or for a public-facing testnet intended for developer testing only.
There will be a follow up PR that adds README and Makefile commands for instructions on how to build and deploy this to AWS.
It is currently blocked on https://github.com/cosmos/peggy/pull/63, and contains all important commits from that branch. We can deprecate that branch if desired, or merge that branch first and then this one second.

Note: Have retargeted this to cosmos:feat/tag-chain-and-contract and it is also blocked on https://github.com/cosmos/peggy/pull/68

@musnit resolved a merge conflict. As #63 and #68 have been merged, let's change the base branch back to master and resolve any conflicts so that we can merge this PR.

@denalimarsh @fedekunze have rebased this onto master.

@fedekunze have fixed args/flag and rebased to master. should be ready for merge!


os.path.join compatibility

In python 3, os.path.join(pathlib.Path('my/path'), 'my.file') returns a string, my/path/my.file.
However, os.path.join(pathlib2.Path('my/path'), 'my.file') raises an AttributeError:
     68         if b.startswith('/'):
     69             path = b
---> 70         elif path == '' or path.endswith('/'):
     71             path +=  b
     72         else:

AttributeError: 'PosixPath' object has no attribute 'endswith'

This is an issue for someone trying to gradually port a large codebase over to using Paths
While strictly speaking, this may be due to py2's implementation of os.path.join rather than pathlib2's implementation of PurePath, it may be useful to reverse engineer compatibility for such a common path operation.
Usually, this would require implementing startswith, endswith, and __iadd__ on PurePath. However, giving pathlib2.PurePath a significant amount of behaviour not seen in the 'real' PurePath doesn't seem like a good idea. Is there another way round it? Is it possible for importing pathlib2 to insert a shim into os.path?

This incompatibility also affects something as basic as open, drastically reducing the utility of pathlib2 - I suppose nothing can be done about that.

Closing due to inactivity (as with the related pull request).


"step-run" fails during long benchmark run

This is caused by using "successCondition" in the Argo step to track the status of the created kubeflow resources (tfjob), which causes the step to timeout in a few minutes if the "successCondition" is not met. However the kubeflow resources running benchmarks might take longer time than the step can wait.
We need a more proper way to track the status of the created kubeflow resources.

/priority p2

is this still an open issue and is this being handled?


Convert representation of sex to use OntologyTerm rather than have

remove a special case enum that is different than all other metadata.

+1, this leaves us free to use whatever the right ontology actually is here, since "genetic sex" is such a slippery notion.

+1
On Sun, Mar 8, 2015 at 3:01 PM, adamnovak<EMAIL_ADDRESS>wrote:

+1, this leaves us free to use whatever the right ontology actually is
here, since "genetic sex" is such a slippery notion.
—
Reply to this email directly or view it on GitHub
https://github.com/ga4gh/schemas/pull/251#issuecomment-77777273.

+1 :-)

Any opinions on one the "right" ontology is for this?

This is actually a big problem that needs addressing, apologies that I didn't try earlier when this came up and I argued for genetic sex ;-).
If you search ontobee for 'sex',  you get no results. Bioportal isn't a whole lot better.
http://purl.obolibrary.org/obo/PATO_0000047 'biological sex' isn't consistent with what the metadata group agreed on in that it is not genotypic.
PATO has a subclass 'mating type' but the subclasses don't apply to humans.
If you search ontobee for 'male' and you don't find much either. there is this: http://www.ebi.ac.uk/efo/EFO_0001266 but it isn't genotypic sex either. After that, you get into NCI, MeSH, etc. NCI has 'sex', it has gender as a synonym. MeSH 'sex' is defined as "The totality of characteristics of reproductive structure, functions, PHENOTYPE, and GENOTYPE, differentiating the MALE from the FEMALE organism."
Then you move on to CDEs.
PhenX has 'gender': Question asking the respondent for his/her self-conception of being male or female.
but not much else.
The NIH CDE here is probably the closest: http://1.usa.gov/1EoB3lr
but its a CDE and therefore not terribly web compliant or interoperable (though we as a community should try to do better here).
We suggest we add some classes to PATO and work on this some more. I have put in a few stawmen here: https://github.com/obophenotype/pato/commit/3dcabfef5592fbfc560309fcbc269796696dafc6
Note these are not released yet. We need to think more about how we deal with differences in different organisms. I've kept these terms generic, but with specific examples from human. Ideally you'd be able to be more specific about what chromosomal complement you had.

Hi Melissa,
Thanks!  The sole purpose of this PR was to do away with the one-off enum that
create a different programming model for just one field.  Note that the field
was named simply sex' before, with the type GeneticSex.  The field name could easily be changed to geneticSex'.
I think we need to explore making ontology references easier to use
in the APIs.  I am not quite sure how to do it yet, but we don't want it
to be too cumbersome.
Cheers,
Mark
Melissa Haendel<EMAIL_ADDRESS>writes:

This is actually a big problem that needs addressing, apologies that I didn't
try earlier when this came up and I argued for genetic sex ;-).
If you search ontobee for 'sex', you get no results. Bioportal isn't a whole
lot better.
http://purl.obolibrary.org/obo/PATO_0000047 'biological sex' isn't consistent
with what the metadata group agreed on in that it is not genotypic.
PATO has a subclass 'mating type' but the subclasses don't apply to humans.
If you search ontobee for 'male' and you don't find much either. there is this:
http://www.ebi.ac.uk/efo/EFO_0001266 but it isn't genotypic sex either. After
that, you get into NCI, MeSH, etc. NCI has 'sex', it has gender as a synonym.
MeSH 'sex' is defined as "The totality of characteristics of reproductive
structure, functions, PHENOTYPE, and GENOTYPE, differentiating the MALE from
the FEMALE organism."
Then you move on to CDEs.
PhenX has 'gender': Question asking the respondent for his/her self-conception
of being male or female.
but not much else.
The NIH CDE here is probably the closest: http://1.usa.gov/1EoB3lr
but its a CDE and therefore not terribly web compliant or interoperable (though
we as a community should try to do better here).
We suggest we add some classes to PATO and work on this some more. I have put
in a few stawmen here: obophenotype/pato@3dcabfe
Note these are not released yet. We need to think more about how we deal with
differences in different organisms. I've kept these terms generic, but with
specific examples from human. Ideally you'd be able to be more specific about
what chromosomal complement you had.
—
Reply to this email directly or view it on GitHub.*

Great, well you have the ontology class available now http://purl.obolibrary.org/obo/PATO_0020000
(its released but not yet resolving in Ontobee). This is a parent node for several classes.
see https://github.com/obophenotype/pato/releases
I agree we should document how to apply ontologies for use in the APIs a bit better. I would anticipate that you'd want to define behavior for any references- for example, reference of a single class, any logical entailments, property domain and range restrictions. @cmungall and I can work on this.

And I had wanted to discuss this as a case for an "ontology-with-fallback" model ...
Which I still support, since there may be many generic but usable attribute/value uses, which one cannot map easily but doesn't want to discard (see sex until now).
I would be absolutely delighted if you could do the implementation side of the ontology term, for the general metadata scheme, while keeping in close contact/discussion with some involved MTT people (e.g. Mark Diekhans, Suzy Lewis, myself ...).

On 25 Mar 2015, at 18:34, Melissa Haendel<EMAIL_ADDRESS>wrote:
Great, well you have the ontology class available now http://purl.obolibrary.org/obo/PATO_0020000 http://purl.obolibrary.org/obo/PATO_0020000
(its released but not yet resolving in Ontobee). This is a parent node for several classes.
see https://github.com/obophenotype/pato/releases https://github.com/obophenotype/pato/releases
I agree we should document how to apply ontologies for use in the APIs a bit better. I would anticipate that you'd want to define behavior for any references- for example, reference of a single class, any logical entailments, property domain and range restrictions. @cmungall https://github.com/cmungall and I can work on this.
—
Reply to this email directly or view it on GitHub https://github.com/ga4gh/schemas/pull/251#issuecomment-86134590.

Exactly.  Rather than fallback I would describe these as local ontologies.  Nothing special case
... Sent from my computer phone
-----Original Message-----
From: Michael Baudis<EMAIL_ADDRESS>To: ga4gh/schemas<EMAIL_ADDRESS>Cc: Mark Diekhans<EMAIL_ADDRESS>Sent: Wed, 25 Mar 2015 3:34 PM
Subject: Re: [schemas] Convert representation of sex to use OntologyTerm rather than have (#251)
And I had wanted to discuss this as a case for an "ontology-with-fallback" model ...
Which I still support, since there may be many generic but usable attribute/value uses, which one cannot map easily but doesn't want to discard (see sex until now).
I would be absolutely delighted if you could do the implementation side of the ontology term, for the general metadata scheme, while keeping in close contact/discussion with some involved MTT people (e.g. Mark Diekhans, Suzy Lewis, myself ...).

On 25 Mar 2015, at 18:34, Melissa Haendel<EMAIL_ADDRESS>wrote:
Great, well you have the ontology class available now http://purl.obolibrary.org/obo/PATO_0020000 http://purl.obolibrary.org/obo/PATO_0020000
(its released but not yet resolving in Ontobee). This is a parent node for several classes.
see https://github.com/obophenotype/pato/releases https://github.com/obophenotype/pato/releases
I agree we should document how to apply ontologies for use in the APIs a bit better. I would anticipate that you'd want to define behavior for any references- for example, reference of a single class, any logical entailments, property domain and range restrictions. @cmungall https://github.com/cmungall and I can work on this.
—
Reply to this email directly or view it on GitHub https://github.com/ga4gh/schemas/pull/251#issuecomment-86134590.

Reply to this email directly or view it on GitHub:
https://github.com/ga4gh/schemas/pull/251#issuecomment-86185540


d2l-list and d2l-scroll-wrapper: Dragging to the last spot adds padding causing the scroll wrapper to start vertical scrolling

This is likely only a problem with the padding-type="none" option. Dragging to the last spot causes the size of the last element to increase slightly and the scroll wrapper to start vertical scrolling creating a stuttering effect.
Known Workaround
Adding 6px of padding to the last list item can mitigate the issue.

We've had a bit of conversation on this.  Currently the marker end-caps are 12px high and it requires some whitespace below the last item to display correctly.  We never really expected the list component to be used in this way.  Nevertheless, we are considering some alternate solutions for the end caps and probably moving the marker up further.  For the moment though, I think the app needs to reserve some space for it until we can get a few other list changes done.


sync_all_commands appears to block discord.py heartbeats

Use Case
Enable slash commands for any bot that loads extensions and then later manually adds a cog (after on_ready) using add_cog.
Expected Solution
Currently enabling this:
slash = SlashCommand(bot, sync_commands=True, sync_on_cog_reload=True, override_type=True)

Issue
Enabling the above does not cause cogs manually added after on_ready to get recognized. I understand this is already a known issue.
Attempted Solution
self.bot.add_cog(MyCustomCog(self.bot))

# Call sync_all_commands directly to force detection of cogs.
print("Before sync_all_commands()")
await self.bot.slash.sync_all_commands(delete_from_unused_guilds=False)
print("After sync_all_commands")

In addition to verify that the client sent the cog's new commands I added prints into the command_request method as well. https://github.com/eunwoo1104/discord-py-slash-command/blob/d5cba045a60aa5f9e3e16d16e7a4520fbdd31e3c/discord_slash/client.py#L341
This doesn't work as seen in this debug log:
DEBUG:discord.gateway:Keeping shard ID None websocket alive with sequence 4.
DEBUG:discord.client:Dispatching event socket_raw_receive
DEBUG:discord.gateway:For Shard ID None: WebSocket Event: {'t': None, 's': None, 'op': 11, 'd': None}
DEBUG:discord.client:Dispatching event socket_response
Before sync_all_commands()
Syncing commands...
INFO:discord_slash:Syncing commands...
Called command_request with GET
DEBUG:discord.gateway:Keeping shard ID None websocket alive with sequence 4.
WARNING:discord.gateway:Shard ID None heartbeat blocked for more than 10 seconds.
Loop thread traceback (most recent call last):
  File "C:\Users\taven\AppData\Local\Programs\Python\Python39\lib\runpy.py", line 197, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "C:\Users\taven\AppData\Local\Programs\Python\Python39\lib\runpy.py", line 87, in _run_code
    exec(code, run_globals)
  File "C:\Users\taven\PycharmProjects\OpenDebates\venv\lib\site-packages\erin\__main__.py", line 72, in <module>
    main()
  File "C:\Users\taven\PycharmProjects\OpenDebates\venv\lib\site-packages\erin\__main__.py", line 62, in main
    args.action(args)
  File "C:\Users\taven\PycharmProjects\OpenDebates\venv\lib\site-packages\erin\cli\start.py", line 42, in run
    app.start(**passed_args)
  File "C:\Users\taven\PycharmProjects\OpenDebates\venv\lib\site-packages\erin\app.py", line 105, in start
    bot.run(config["bot"]["token"], bot=True, reconnect=True)
  File "C:\Users\taven\PycharmProjects\OpenDebates\venv\lib\site-packages\discord\client.py", line 713, in run
    loop.run_forever()
  File "C:\Users\taven\AppData\Local\Programs\Python\Python39\lib\asyncio\windows_events.py", line 316, in run_forever
    super().run_forever()
  File "C:\Users\taven\AppData\Local\Programs\Python\Python39\lib\asyncio\base_events.py", line 596, in run_forever
    self._run_once()
  File "C:\Users\taven\AppData\Local\Programs\Python\Python39\lib\asyncio\base_events.py", line 1890, in _run_once
    handle._run()
  File "C:\Users\taven\AppData\Local\Programs\Python\Python39\lib\asyncio\events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "C:\Users\taven\PycharmProjects\OpenDebates\plugins\debate\rooms\interface.py", line 679, in voice_channel_update
    empty_invisible_room = self.empty_invisible_rooms.get()
  File "C:\Users\taven\AppData\Local\Programs\Python\Python39\lib\queue.py", line 171, in get
    self.not_empty.wait()
  File "C:\Users\taven\AppData\Local\Programs\Python\Python39\lib\threading.py", line 312, in wait
    waiter.acquire()

As seen above GET is called, but PUT is never called. In addition while the function is being called the heartbeat is blocked until the bot goes offline.

PUT is only called if there is a reason to push a change to discord, so unless its not detecting changes, im not overly concerend about that.
As for blocking heartbeat, thats a touch more concerning, how many slash commands do you have?

@LordOfPolls I only have one slash command. It looks like this:
     @cog_ext.cog_slash(
        name="topic",
        guild_ids=[769148380156133416],
        description="Set a topic in a debate room.",
        options=[
            create_option(
                name="Topic",
                description="The topic or proposition you want to set.",
                option_type=SlashCommandOptionType.STRING,
                required=True
            )
        ]
    )
    async def topic_slash(self, ctx, topic):
        await self.topic(ctx, message=topic)

This shouldn't be possible then... Nor can i replicate
Do have any sort of network restriction? Are you using a free hosting provider like repl.it?

@LordOfPolls No. No network restriction. Regular cogs are working without slash commands. Plus I'm on a local machine.

Interesting, ill look into it later on today

@LordOfPolls Any progress on this?

Closing as per conversation on discord -- unable to replicate
will reopen if that changes


[Bug]: FAQs section can be made better

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
FAQ section is very dull and also taking very much space , i can organise faq section neatly , providing styling and smooth transition
Add Screenshots

What browsers are you seeing the problem on?
Chrome
Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC contributor
[X] I want to work on this issue
[X] I'm willing to provide further clarification or assistance if needed.

like how? can you give the outlook design, how you made look better

@mansiruhil13 firstly neumorphic effect is not so visually appealing and also transition when clicked is not so smooth and questions are arranged one by one vertically which requires scolling , ican make it in grid format so scrolling is not required and also add some text color matching with theme because black n white is not the right call.
i hope u understand now and thanku for assigning me this issue


Kotlin implementation of the Acey Ducey game

Excellent thank you! 🙌

You can submit a pr moving the file by deleting it and moving it to the
proper location, that would be easiest.. thank you!
On Wed, Jan 19, 2022 at 6:19 AM Claus Volko @.***>
wrote:

Hi Jeff,
Just a quick note: I am fairly new to GitHub and have made the mistake of
putting the Kotlin file into the main directory where also the Basic file
is located. Perhaps you could create a subdirectory "kotlin" and move
aceyducey.kt into this subdirectory?
When I send you a Kotlin implementation of another game, I'll try to put it
into the correct subdirectory.
Best Regards
Claus Volko
Am Mo., 17. Jan. 2022 um 18:30 Uhr schrieb Jeff Atwood <
@.***>:

Merged #521
https://github.com/coding-horror/basic-computer-games/pull/521 into
main.
—
Reply to this email directly, view it on GitHub
<
https://github.com/coding-horror/basic-computer-games/pull/521#event-5905969972
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ALYK4YHZIXU2MAO2KM3BJVLUWRG4LANCNFSM5MFC4GCA
.
Triage notifications on the go with GitHub Mobile for iOS
<
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
<
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
.
You are receiving this because you authored the thread.Message ID:
@.***
.com>

--
Dipl.-Ing. Dr. Claus Volko
http://www.cdvolko.net/
—
Reply to this email directly, view it on GitHub
https://github.com/coding-horror/basic-computer-games/pull/521#issuecomment-1016510645,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALTWVK5ZCILYBCOXR6NJP3UW3B75ANCNFSM5MFC4GCA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you modified the open/close state.Message
ID: @.***>


Fix GitHub capitalize on Docs and Code comments

About
s/Github/GitHub/ig

Codecov Report

Merging #3623 into dev will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##              dev    #3623   +/-   ##
=======================================
  Coverage   99.19%   99.19%
=======================================
  Files          18       18
  Lines        1123     1123
  Branches      303      303
=======================================
  Hits         1114     1114
  Misses          9        9

Impacted Files
Coverage Δ

lib/builder/generator.js
94.23% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Update PR template

FYI @saeedbashir @danialzahid94
Related to https://github.com/edx/edx-app-android/pull/855

Current coverage is 23.03% (diff: 100%)

Merging #817 into master will not change coverage

@@             master       #817   diff @@
==========================================
  Files           677        677
  Lines         56430      56430
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
  Hits          13001      13001
  Misses        43429      43429
  Partials          0          0

Powered by Codecov. Last update 0c03923...d9c5f5f


capture dynamic values from events

Hi - is there a way to capture dynamic values generated inside smart contract fns that are emitted via events rather than returned?  technically I think #515's proposed soln would solve this as well, but felt like a distinct enough issue (might be another workaround I missed in the docs) that I thought it was worth opening a separate ticket. Thank you
(my specific use case is similar to those mentioned in other tickets e.g. #529 : calling a fn from a ~FactoryContract and then needing to get the address of the new contract for testing purposes)

pulling event value from receipt for now, e.g.
      const receipt = await (await createSplitTx).wait()
      splitAddress =
        receipt.events?.[0]?.args?.split &&
        ethers.utils.getAddress(receipt.events[0]?.args?.split)


Add basic CI support

This adds a very basic CI support to the repo. This should help to avoid to break main after a not so thoroughly tested merges.
Of course the configuration can be expanded and tuned, but it should be a good starting point 🤞 .
A sample run can be found here.

@lechuckcaptain Good job!

Is this okay to merge, or are there more commits to come?

Okay, well let's find out 😅


Build verification tests fails on Open Power Firestone Hardware

I am executing the BVT tests targeted for a Open Power Firestone Hardware as below.
[root@lop827 bvt]# ./run-op-bvt --bmcip <IP_ADDRESS> --bmcuser sysadmin --bmcpwd superuser --usernameipmi ADMIN --passwordipmi admin --cfgfiledir ../ci/source/ --imagedir /tmp/ --imagename firestone_update.pnor --fverbose /tmp/new_firestone ./op-ci-basic-bvt.xml
ipmitool -H <IP_ADDRESS> -I lanplus -U ADMIN -P admin sdr elist |grep 'OCC Active'
ipmitool -H <IP_ADDRESS> -I lanplus -U ADMIN -P admin sdr elist |grep 'OCC Active'
ipmitool -H <IP_ADDRESS> -I lanplus -U ADMIN -P admin sdr elist |grep 'OCC Active'
ipmitool -H <IP_ADDRESS> -I lanplus -U ADMIN -P admin sdr elist |grep 'OCC Active'
IPL timeout
00:26:29 :: op-ci-basic: ERROR: command failed with exit code 256
00:26:29 :: op-ci-basic: Finished Test:
00:26:29 :: op-ci-basic: Starting Test:
00:26:29 :: op-ci-basic: Running command: op-ci-bmc-run  "op_ci_bmc.ipmi_sel_check()"
ipmitool -H <IP_ADDRESS> -I lanplus -U ADMIN -P admin sel elist
00:26:45 :: op-ci-basic: OK: command finished successfully
00:26:45 :: op-ci-basic: Finished Test:
00:26:45 :: op-ci-basic: ERROR: Finished tests on 2015-November-04 with one or more testcase errors.
00:26:45 :: ERROR: "OP CI Basic BVT" (op-ci-basic.xml) finished with one or more errors
00:26:45 :: ERROR: Finished BVT tests on 2015-November-04 with 1 testcase failures.
All logs and FFDC saved under /tmp/root/bvt/2015-11-04-89279
As can be seen the tests fail because of the failure of the command:
ipmitool -H <IP_ADDRESS> -I lanplus -U ADMIN -P admin sdr elist |grep 'OCC Active'
As per my analysis, I have found out that the above command is failing because the
grep 'OCC Active' is failing to fetch the correct output from the sdr elist of the Firestone Hardware.
However, on a Habanero Hardware the output looks as follows:
[root@lop826 src]# ./ipmitool -H <IP_ADDRESS> -I lanplus -U ADMIN -P admin sdr elist |grep 'OCC Active'
OCC Active       | 08h | ok  | 210.0 | Device Enabled
There are 2 OCC chips on Firestone and 1 OCC chip on Habanero.
In the sdr elist entries there will be OCC 1 Active and OCC 2 Active mentioned for Firestones.
So, the correct fix for the above command to work for both Habanero and Firestone Hardware's are:
[root@lop826 src]# ./ipmitool -H <IP_ADDRESS> -I lanplus -U ADMIN -P admin sdr elist |grep '^OCC'
OCC 1 Active     | 08h | ok  | 210.0 | Device Enabled
OCC 2 Active     | 09h | ok  | 210.1 | Device Enabled
[root@lop826 src]# ./ipmitool -H <IP_ADDRESS> -I lanplus -U ADMIN -P admin sdr elist |grep '^OCC'
OCC Active       | 08h | ok  | 210.0 | Device Enabled
Please suggest me if I can submit a patch with the changes mentioned above to the source file op-test-framework/common/OpTestIPMI.py which has the code mentioned in the function ipl_wait_for_working_state().
Or else should we enable the commented line
#    cmd = 'sdr elist |grep 'Host Status''
instead of the existing line
cmd = 'sdr elist |grep 'OCC Active''
Either way, we need to submit a patch and fix the same in-order to make the Build Verification Tests work on Firestone Hardware.

Hey Pavaman, thanks for the detailed info.  I've never been real happy with this portion of the code (we should have a better way to detect a successful boot) but I think what you propose is good for now in that it at least gets the tests working on both systems.  Please fork and submit pull request with this change and I'll merge it in.

I have forked and submitted the pull request with the changes as suggested above.

This issue can be closed since we have merged the pull request with the uncommenting of the original source code lines in the common/OpTestIPMI.py for Host Status sensor checking.


Connect the email from webapp to mailgun api to get delivery confirmation or error for all emails sent out (and make the status visible on app pages)

Mailgun should be sending notification back to the app now.
I have set ANYMAIL_WEBHOOK_SECRET and configured web hooks in Mailgun for Delivered Messages, Permanent Failure and Temporary Failure.
What actually happens to these in Django is something @todd-dembrey can explain I think.

		Nov 07 14:28:39 live-opentech-fund heroku/router: at=info method=POST path="/activity/anymail/mailgun/tracking/" host=apply.opentech.fund request_id=9876e12d-268d-43d8-9361-58d39d475b27 fwd="<IP_ADDRESS>,<IP_ADDRESS>" dyno=web.1 connect=1ms service=82ms status=500 bytes=1142 protocol=https

Nov 07 14:28:39 live-opentech-fund app/web.1: [2018-11-07 13:28:38,781] exception: ERROR - Internal Server Error: /activity/anymail/mailgun/tracking/

Nov 07 14:28:39 live-opentech-fund app/web.1: <IP_ADDRESS> - r4IRLZj4sbpa4IEs [07/Nov/2018:13:28:38 +0000] "POST /activity/anymail/mailgun/tracking/ HTTP/1.1" 500 808


Q&A- Tec: Credential Revocation

Another topic that we want to share with you is regarding the revocation of a credential. We share evidence with you (images 4 and 5).
Image 4

Image 5

This error is always triggered when trying to revoke the credential.

@MyriamLara What is running on running on port 4008? Could you please show us an error log from the relevant microservice?

@alexfigtree
el contenedor de status en el puerto 4008 esta corriendo pero desde payload no lo alcanza a servidor por fetch:
y no alcanzamos a hacer ninguna solicitud

Por lo tanto nuestra propuesta es que mejor usen axios en lugar de fetch
https://www.npmjs.com/package/axios

@MyriamLara
Could you show us your docker compose file and any .env files?  Taking out the secret parts of course.
In particular, we want to see what your GitHub configuration for the status list looks like. If you'd rather not post it here in this issue, feel free to email me.
Thanks!

I attach the versions and environment variables that we use to test the application and we cannot revoke the credential. Can't find the container. I know there is another URL that works, but we don't want to depend on the external service. Solo status of the container. I tried it directly on postaman and the service works. In the payload backend it cannot be linked. You must see some problem with the IP of the containers or ports. Check it. Greetings
dcc_admin_dashboard.zip

@jchartrand - would you look into this issue? Could it be related to the version of the software being used?

@AngelOCrz94 I'm not sure if you meant to include the .env files in the zip? I just see the docker compose file. You could email them to me if that's easier/better.

@jchartrand  in a moment send you to email this files .env

I not have shared configuration is own tec. Because no found the revocation.

@MyriamLara @AngelOCrz94
Could you try changing the env variable called STATUS_URL to: http://status:4008 (you had it set to http://localhost:4008) and then try revoking a credential again?
Thanks!

@MyriamLara
It is still using the local status container service.
http://status:4008 is the address for the service within the docker compose network. It is one of the very cool features of docker compose. The docker compose network knows to resolve that name 'status' to the running local service.

@AngelOCrz94 confirms that this issue is resolved during a team meeting on 6/14/24. Closing this issue.


build validate on Linux failed in lack of test   spaces/hsc2hs

Cannot find hsc2hs: /tmp/tmpRClrGx/ghc/inplace/test   spaces/hsc2hs.  Stop.

stderr log: http://hadrian-status-dev.zhenzhang.me:3000/logs/2017-07-16T12%3A04%3A49.765572%25validate%252139.31077409%25failure.err.log
The weird thing is that the validation works fine on my Mac.

So, presumably this has something to do with paths containing spaces. One possible test is install GHC into a directory whose name contains spaces. I'll try to do on Windows, as part of #345.

this is fixed I think


Update Style/SuperArguments to handle super with a block

Register an offense for super with a block or numblock when all the positional arguments match, for instance:
def foo(a, b)
  super(a, b) { x }
end

Also register an offense for super with a chained block, for instance:
def foo(a)
  super(a).bar { x }
end

Fixes #13601.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Blocks and super are certainly something. I think there's nothing wrong with the resulting code, but saying that the arguments are the same seems a bit of a stretch?
Blocks are passed implicitly to super so I would say the arguments are not the same if there is an explicit block. I think, instead it would make more sense to detect an offense for this:
def bar(a, b, &)
  super(a, b)
end

since the block is actually passed along as is. Still, it relies on some weird behavior and may cause a bit of confusion since arguments don't look the same.

@Earlopain I'm not sure if your example should be changed to an offense, or if we should have another cop to indicate that the block is passed in these cases anyways. In any event, for the time being I added a test for that example to document the behaviour.

Blocks and super are certainly something. I think there's nothing wrong with the resulting code, but saying that the arguments are the same seems a bit of a stretch?

I'm not sure I understand, are you saying the offense message should be changed?

I'm not sure if your example should be changed to an offense, or if we should have another cop to indicate that the block is passed in these cases anyways. In any event, for the time being I added a test for that example to document the behaviour.

Sure, seems fine.

I'm not sure I understand, are you saying the offense message should be changed?
It's true that the arguments are not the same, but the positional arguments can still be skipped in this case, if they all match. The behaviour is the same either way.

It's technically correct but I think its pretty confusing. I would leave it alone but I guess it's ok to do since its just how Ruby works.
Maybe you could add something to the docs about block handling + super?


Getting Started Guide Issue

I have realized that the very beginning of the getting started guide has two connected mistakes that make the process confusing.
In step 2. of the guide, it says: "Add references to ngGrid's javascript and css files." This includes a hyperlink to https://github.com/angular-ui/ng-grid . But there are no javascript and css files in this repo that correspond to the files that appear in the demo code, "ng-grid.css" and "ng-grid-1.3.2.js", or to anything similar to that.
I found these files here: https://github.com/angular-ui/ng-grid/tree/2.x, instead. Note the different version.
Later, in step 3, it goes on: Where you declare your app module, add ui.grid:
angular.module('myApp',['ui.grid']);
But it only works if you add 'ngGrid' instead. (Maybe with version 1.3.2 what you needed was "ui.grid", but I don't know which way this should go)

I think you're stuck between 2.x and 3.0.  Most of our documentation now relates to 3.0, which means ui-grid and using the ui-grid files.
Where exactly is the getting started guide that you are referring to?

Yes, I realize the version change....
I am using this guide here:
http://angular-ui.github.io/ng-grid/

Closing as ng-grid is no longer being supported.


Incorrect destination IP in L7 ingress flows with L7 egress and ingress policy configured for same port

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
When configuring both ingress and egress L7 HTTP policies that target the same port, the destination IP is the cilium node IP, causing the pod_name in the destination to be missing. The L7 egress flows seem to still have the correct source/destination IPs for the pods.
I suspect this is related to the fact that the packet is going through envoy which will appear as the cilium node.
I've been able to reliably produce this on a single node KIND setup locally. If I disable the egress policy, the destination IP is correct, similarly, if I disable the ingress policy, the IPs remain correct, it's only an issue when both egress and ingress policies are enabled for the same port. I also tried variations of enabling the ingress policy first, then the egress policy, as well as the opposite: enabling the egress policy first, then enabling the ingress policy. Ordering does not seem to matter, and it still only effects the ingress flows destination IP, and only when both L7 ingress/egress policies are enabled.
Cilium Version
Client: 1.12.1 4c9a630 2022-08-15T16:29:39-07:00 go version go1.18.5 linux/arm64

Kernel Version
Linux lima-docker 5.15.0-46-generic #49-Ubuntu SMP Thu Aug 4 18:08:11 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux
Kubernetes Version
Client Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.1", GitCommit:"3ddd0f45aa91e2f30c70734b175631bec5b5825a", GitTreeState:"clean", BuildDate:"2022-05-24T12:26:19Z", GoVersion:"go1.18.2", Compiler:"gc", Platform:"darwin/arm64"}
Kustomize Version: v4.5.4
Server Version: version.Info{Major:"1", Minor:"24", GitVersion:"v1.24.0", GitCommit:"4ce5a8954017644c5420bae81d72b09b735c21f0", GitTreeState:"clean", BuildDate:"2022-05-19T15:42:59Z", GoVersion:"go1.18.1", Compiler:"gc", Platform:"linux/arm64"}

Sysdump
cilium-sysdump-20220826-165646.zip
Relevant log output
# <IP_ADDRESS> is the cilium node IP, <IP_ADDRESS> is the client app (crawler) and <IP_ADDRESS> is the server app (loader)
# notice how ingress flows have the destination as the cilium node IP, but egress flows have the correct values.
(⎈|kind-kind:default) ~/p/w/kind-cilium-ce-helm-install ❯❯❯ hubble observe -t l7 -n tenant-jobs --protocol http -o jsonpb  | grep EGRESS | jq '.flow | {ip: .IP, source_pod: .source.pod_name, dest_pod: .destination.pod_name}' -rc                                             main ⬆ ✭ ✱ ◼
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"loader-597c4c8b54-8vn84","dest_pod":"crawler-86b7cbc87-fbqzc"}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"crawler-86b7cbc87-fbqzc","dest_pod":"loader-597c4c8b54-8vn84"}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"crawler-86b7cbc87-fbqzc","dest_pod":"loader-597c4c8b54-8vn84"}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"loader-597c4c8b54-8vn84","dest_pod":"crawler-86b7cbc87-fbqzc"}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"loader-597c4c8b54-8vn84","dest_pod":"crawler-86b7cbc87-fbqzc"}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"crawler-86b7cbc87-fbqzc","dest_pod":"loader-597c4c8b54-8vn84"}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"loader-597c4c8b54-8vn84","dest_pod":"crawler-86b7cbc87-fbqzc"}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"crawler-86b7cbc87-fbqzc","dest_pod":"loader-597c4c8b54-8vn84"}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"loader-597c4c8b54-8vn84","dest_pod":"crawler-86b7cbc87-fbqzc"}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"crawler-86b7cbc87-fbqzc","dest_pod":"loader-597c4c8b54-8vn84"}
(⎈|kind-kind:default) ~/p/w/kind-cilium-ce-helm-install ❯❯❯ hubble observe -t l7 -n tenant-jobs --protocol http -o jsonpb  | grep INGRESS | jq '.flow | {ip: .IP, source_pod: .source.pod_name, dest_pod: .destination.pod_name}' -rc                                            main ⬆ ✭ ✱ ◼
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"loader-597c4c8b54-8vn84","dest_pod":null}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":null,"dest_pod":"loader-597c4c8b54-8vn84"}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"loader-597c4c8b54-8vn84","dest_pod":null}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":null,"dest_pod":"loader-597c4c8b54-8vn84"}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"loader-597c4c8b54-8vn84","dest_pod":null}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":null,"dest_pod":"loader-597c4c8b54-8vn84"}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"loader-597c4c8b54-8vn84","dest_pod":null}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":null,"dest_pod":"loader-597c4c8b54-8vn84"}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":"loader-597c4c8b54-8vn84","dest_pod":null}
{"ip":{"source":"<IP_ADDRESS>","destination":"<IP_ADDRESS>","ipVersion":"IPv4"},"source_pod":null,"dest_pod":"loader-597c4c8b54-8vn84"}

Anything else?
L7 policies in question: https://gist.github.com/chancez/d717d68e329c4997fbdf896cdddf15ce
This is using the jobs-app for cilium enterprise demos (note, the demo app has these policies but without the egress L7 policy on the ports, so you'll need to apply the manifest from the gist after installing):
helm install jobs-app isovalent/jobs-app --version v0.2.0 --namespace tenant-jobs

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I recall we had trouble with overlapping 5-tuples at least in the case where both egress and ingress policies are in place and both source and destination are on the same node. For this reason, IIRC:
Ingress proxy always uses the node IP as the source address when forwarding to the destination pod. This does not affect the exported (hubble) flow information, as that is based on the incoming 5-tuple.
Egress proxy uses the node IP as the source if the destination is on the same node. This does not affect the exported flow entry exported by the egress proxy as the 5-tuple is from the incoming connection. L7 LB takes the destination address from the upstream connection, but keeps the original source address from the incoming (downstream) connection. This WILL affect the flow exported at ingress, both at L3 and L7 levels, as the incoming source address is the node IP. Source security ID is always carried through within the node, so that is not affected.
We have NOTRACK rules from proxy redirection connections, so that connection tracking is not the issue here, but the host networking namespace would not be able to differentiate between the connections to the egress and ingress listeners if they both had the same 5-tuple.
Since this happens only for connections on the same node, we could probably paper over this in Cilium agent, if so desired. It could be a bit confusing if hubble flows report 5-tuples that don’t really match the network traffic (or the L3/4 flow entries), but this already happens with L7 LB flows as described above.

But it is actually weird that the destination IP is the node IP, unless that is for a return packet for a connection for which the source address was the node IP. We always preserve the original destination IP address/port when forwarding traffic through Envoy, as otherwise the destination node would not know to which pod the traffic should go to. Having port numbers visible with the IP addresses would reveal the direction (original/reply) of the flows.

So I was doing some more testing, and it does seem like this is actually not limited to destination IP as I thought. And it's actually not consistently broken either it seems. I applied the following policy: https://gist.github.com/chancez/d6e08d2f0ae8e513f3f28144958bd9ea
And discovered some ingress flows with incorrect source, and some missing dest. In this output, my cilium node IP is <IP_ADDRESS>. I also included source/dest ports in case that helps.
(⎈|kind-kind:default) ~/p/w/kind-cilium-ce-helm-install ❮❮❮ hubble observe -t l7 -n tenant-jobs --protocol http -o jsonpb  | grep INGRESS | jq '.flow | {source_pod: .source.pod_name, dest_pod: .destination.pod_name, source: "\(.IP.source):\(.l4.TCP.source_port)", dest: "\(.IP.destination):\(.l4.TCP.destination_port)"}' -rc
{"source_pod":"coreapi-546797cd76-8m28l","dest_pod":"elasticsearch-master-0","source":"<IP_ADDRESS>:42420","dest":"<IP_ADDRESS>:9200"}
{"source_pod":"elasticsearch-master-0","dest_pod":"coreapi-546797cd76-8m28l","source":"<IP_ADDRESS>:9200","dest":"<IP_ADDRESS>:42420"}
{"source_pod":"coreapi-546797cd76-8m28l","dest_pod":null,"source":"<IP_ADDRESS>:9080","dest":"<IP_ADDRESS>:57580"}
{"source_pod":"crawler-86b7cbc87-p27dk","dest_pod":"loader-597c4c8b54-8mv9s","source":"<IP_ADDRESS>:48382","dest":"<IP_ADDRESS>:50051"}
{"source_pod":"loader-597c4c8b54-8mv9s","dest_pod":"crawler-86b7cbc87-p27dk","source":"<IP_ADDRESS>:50051","dest":"<IP_ADDRESS>:48382"}
{"source_pod":null,"dest_pod":"coreapi-546797cd76-8m28l","source":"<IP_ADDRESS>:57582","dest":"<IP_ADDRESS>:9080"}
{"source_pod":"coreapi-546797cd76-8m28l","dest_pod":"elasticsearch-master-0","source":"<IP_ADDRESS>:42420","dest":"<IP_ADDRESS>:9200"}
{"source_pod":"elasticsearch-master-0","dest_pod":"coreapi-546797cd76-8m28l","source":"<IP_ADDRESS>:9200","dest":"<IP_ADDRESS>:42420"}
{"source_pod":"coreapi-546797cd76-8m28l","dest_pod":null,"source":"<IP_ADDRESS>:9080","dest":"<IP_ADDRESS>:57582"}
{"source_pod":"crawler-86b7cbc87-p27dk","dest_pod":"loader-597c4c8b54-8mv9s","source":"<IP_ADDRESS>:48382","dest":"<IP_ADDRESS>:50051"}
{"source_pod":"loader-597c4c8b54-8mv9s","dest_pod":"crawler-86b7cbc87-p27dk","source":"<IP_ADDRESS>:50051","dest":"<IP_ADDRESS>:48382"}
{"source_pod":null,"dest_pod":"coreapi-546797cd76-8m28l","source":"<IP_ADDRESS>:57584","dest":"<IP_ADDRESS>:9080"}
{"source_pod":"coreapi-546797cd76-8m28l","dest_pod":"elasticsearch-master-0","source":"<IP_ADDRESS>:42420","dest":"<IP_ADDRESS>:9200"}
{"source_pod":"elasticsearch-master-0","dest_pod":"coreapi-546797cd76-8m28l","source":"<IP_ADDRESS>:9200","dest":"<IP_ADDRESS>:42420"}
{"source_pod":"coreapi-546797cd76-8m28l","dest_pod":null,"source":"<IP_ADDRESS>:9080","dest":"<IP_ADDRESS>:57584"}

In the above logs destination IP is only ever the node IP for (ingress) response packets, which makes sense since the egress visibility policy redirects to Envoy, and uses the node IP as the source due to the destination being in the same node and 5-tuples arriving to egress and ingress proxies need to be different.

Policy enforcement is not affected as in this case we can always carry the source security ID to the destination.

The reason behind this behavior makes sense, though it breaks the metrics labels like source/destination pod because the pod name is missing, and obviously the IP being "wrong" can be confusing. At least it's limited to a specific circumstance.

@chancez based on the discussion above do you there's a good solution that we can implement/

I don't know enough about how packets traverse cilium to have any suggestions on solutions, I think that's something @jrajahalme might be able to answer better.

Policy enforcement is not affected as in this case we can always carry the source security ID to the destination.

Also, this is correct, but it does break filtering for hubble flows since the IP is not what the user would expect.


Tool to generate functions.go based on rules descriptor

Current behavior:
User has to write down functions.go with condition evaluators and action functions as defined in the rules descriptor json.
Expected behavior:
Add a cli tool or flogo cli plugin to generate functions.go boilerplate code based on supplied rules descriptor json.
What is the motivation / use case for changing the behavior?

Improves turn around time to create and run a new rule application.
Eliminates human errors caused due to mismatch function names (usually spelling mistakes)  between descriptor json and functions.go

Additional information you deem important (e.g. I need this tomorrow):

Hmmm - I guess? Honestly I'd prefer this to be done:

Conditions utilize the flogo expression language with bindings to the Tuple store
Action functions - same thing (or wrap it in an activity if used within a flogo flow)

Doing a code generator isn't really moving the needle.

I think all this is asking is for stubs to be generated and save some typing/and errors. (unlike the elaborate codegen in BE) So it would be a good little nifty utility to have.. #2 that Matt mentioned above would be really cool.. When a rule fires, execute a Flogo-flow.. That would be a nice ER. And of course #1 above, which was done but broke when Flogo-core changed their APIs. That needs to be redone.

I echo @balamg, points 1 & 2 mentioned by @tibmatt are really cool !!
Not sure about the complexity involved in point 1 & 2 realization, until then this kind of tool saves some time/errors.

Closing this issue as this kind of tool may not be required as issues #22 & #69 effectively handles the problem statement.


Missed an amazonka version.

They should all be version ranges rather than a hardcoded version.
There can be issues with the lenses amazonka exports and what P exposes, care needs to be taken to ensure you have the right hiding on import.

:+1:


how to extract a image from PPT

what i have are many PPT , and what i want to do is  extract those image with as many features as possible and put them into database , but i don't know how to do it

Closing as not an issue. You might have better luck with support questions like this on Stack Overflow, marking it with the python-pptx tag.


feat(footer): optimize node counts

Related Ticket(s)
Resolves #10656
Description
Reduces the usage of hidden DOM elements by replacing them with conditionally rendered markup based on the viewport width.
Analysis
Fortunately, the <dds-footer> family of components was pretty well optimized aside from the locale modal (which is being handled in #10657). The <dds-footer-nav-group> switches between accordion and list displays for mobile and desktop, respectively, but it was already leveraging browser APIs to render just one version of the markup at a time. I did switch this to use our new MediaQueryMixin for consistency's sake and reducing the amount of code necessary for the component to function.
The only opportunities for actual node reductions I found were in the <dds-footer-composite>'s rendering of language selectors, which appear in Stories such as Default language only.
Mobile

-
Before
After
% Reduction

Nodes
2521
1840
27%

Comments
726
528
27%

Inters
1086
802
26%

Desktop

-
Before
After
% Reduction

Nodes
2476
1891
24%

Comments
711
560
21%

Inters
1071
827
23%

Changelog
Changed

Use MediaQueryMixin for DDSFooterNavGroup headers' conditional rendering as accordion label or static heading.
Conditionally render DDSFooterComposite's language selector based on viewport size.
Make mock MediaQueryList reusable and update related unit tests.

looking great!
one thing i did notice was the language only footer dropdown has a height of 40px vs 48px:
deploy-preview:

latest:

Nice catch, @ariellalgilmore! Should be fixed now.


Incorrect SP ID

SP Should be "b46c3ac5-9da6-418f-a849-0a07a10b3c6c"
You are missing a 0
b46c3ac5-9da6-418f-a849-0a7a10b3c6c
[Enter feedback here]

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

ID: 1b2bd8cc-1bb7-2056-5fc0-0d1e55912770
Version Independent ID: f09fcaa5-0c6e-2adc-4965-bf72ce2a391c
Content: Enable CloudKnox Permissions Management in your organization
Content Source: articles/active-directory/cloud-infrastructure-entitlement-management/cloudknox-onboard-enable-tenant.md
Service: active-directory
Sub-service: ciem
GitHub Login: @Yvonne-deQ
Microsoft Alias: v-ydequadros

@WhippsP Thank you for catching this. We will review and get this updated.

@WhippsP You are correct . I tested this in the lab and we can see the following screenshot provides clear instructions that the service principal ID is b46c3ac5-9da6-418f-a849-0a07a10b3c6c  and the command should be as following.
az ad sp create --id b46c3ac5-9da6-418f-a849-0a07a10b3c6c

We have initiated a change request for the same. and once the content team approves it , this change will be live.
Thank you.


Create a GitHub action for Build Image and push against main branch

Issue link

https://github.com/project-codeflare/multi-cluster-app-dispatcher/issues/559
What changes have been made

Added Github action for image build and push
Removed travis.yml file to skip travis CI build trigger and adjusted Makefile
Updated latest to dev for tag to align with release process

Verification steps

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[ ] Unit tests
[ ] Manual tests
[ ] Testing is not required for this change

Tested the workflow changes in fork repository https://github.com/Srihari1192/multi-cluster-app-dispatcher/actions/runs/5820949721

/lgtm

/approve


Unspecified USER in Dockerfile causes checkouts with 'Permission Denied'

Hi, I'm trying to use this to build a package with pyinstaller on a self-hosted runner but am running into some issues.
Since the Dockerfile doesn't specify a USER, the commands in entrypoint.sh are run as root, causing the built artifacts to be owned by root:root (See this discussion post).
This is likely not much of an issue on Github hosted runners since the environment is re-provisioned, but on a self hosted runner after the first run of this action the checkout step fails with:
   warning: failed to remove [REPO]/dist/windows: Permission denied
Warning: Unable to clean or reset the repository. The repository will be recreated instead.
Deleting the contents of '/home/jenkins/gha/w1/w/[REPO]
Error: File was unable to be removed Error: EACCES: permission denied, rmdir '/home/jenkins/gha/w1/w/[REPO]/dist/windows'

Because the built artifacts are in the repo directory, this also causes linux builds of the same source to fail. Specifying a USER in the Dockerfile would be greatly appreciated.

Please feel free to open a PR with the needed change 🙂