text:
UHSAS variables

These are essentially histograms with 99 bins that need to be transformed into C3 timeseries.

@hgordo I included the UHSASdNdlogd variables to the ObservationOutout type in a straightforward manner and ran a batch job (which now runs in parallel!) to upsert them. It seems to be working well!
I played a little bit with the metrics (see this notebook) to see if results are consistent and they look alright to me, but I think it would be nice if you can check it, as you are the expert on the science. Here's a plot:


text:
feat(cli) Add repl command

I think it can be a good addition.

hello @c4spar thanks as well for the cool deno projects you have!

source: gharchive/pull-request

license: MIT

license_type: permissive

license_source: github-api


text:
Simplify wrapping_diff code

wrapping_diff can be simplified to b.wrapping_sub(a) as i16
I wrote a test to compare the two implementations so a reviewer can convince themselves that they are identical.
The test can be run with:
cargo test --release -- test_wrapping_diff_equivalence --ignored

--release is required because it tests all $2^{32}$ inputs.
The wrapping_diff_old can be removed before merge.

@cBournhonesque ready to merge :)

Thanks that is much better! I don't know why I didn't go for this, I guess I must have had a good reason at the time

authors: Nul-led ambiso cBournhonesque

repo: cBournhonesque/lightyear


text:
Custom User-Agent

I am experimenting with grabbing some channels from various providers and some rely on having a browser user agent to work.
Is there an option I am missing or some sort of configuration parameter I can adjust to customise the user agent string that Cabernet sends when grabbing the stream?
Thanks

Currently the User-Agent sends the Firefox Browser text.  It is not available to adjust in the settings, but if you want to try other browsers, you can set it by editing the utils.py at cabernet/lib/common/ to see if other strings will work.  I just updated it in RC2 to Firefox version 111.0

source: gharchive/issue

repo: cabernetwork/cabernet


text:
iaas_launch.py fails when attempting to locate the image ubuntu-source-fluentd

Please see the attached stdout/stderr.https://app.zenhub.com/files/104253320/4a687249-58df-4335-bdaf-280920f166e5/download

This is the first command to fail.
TASK [run start-registry command] ****************************************************************************************************************************************************************************************
fatal: [10.1.0.11]: FAILED! => {"changed": true, "cmd": ["docker", "run", "-d", "-p", "4000:5000", "--restart=always", "--name", "registry", "registry:2"], "delta": "0:00:00.033931", "end": "2018-02-05 16:34:10.836958", "failed": true, "rc": 125, "start": "2018-02-05 16:34:10.803027", "stderr": "docker: Error response from daemon: Conflict. The container name "/registry" is already in use by container "686117e0ed5e0d5143288fc757a2081ce42c28d0a49c7c608d0523978a9bc80a". You have to remove (or rename) that container to be able to reuse that name.\nSee 'docker run --help'.", "stderr_lines": ["docker: Error response from daemon: Conflict. The container name "/registry" is already in use by container "686117e0ed5e0d5143288fc757a2081ce42c28d0a49c7c608d0523978a9bc80a". You have to remove (or rename) that container to be able to reuse that name.", "See 'docker run --help'."], "stdout": "", "stdout_lines": []}

deploy3.txt is from the second attempt. Attaching deploy.txt is from the initial attempt.
deploy.txt

Hi,
Can you please provide us the output of the following commands:
docker images (On target node)
curl -X GET <DOCKER_REGISTRY IP:PORT>/v2/_catalog (On target node)
Regards,
Chirag

Hi Chirag,
Here's the stdout:
root@build-os-vm-test-launcher:~# curl -X GET 10.1.0.11:4000/v2/_catalog
{"repositories":[]}
I will leave this environment up in case you would like to take a closer look. You can access the build server with:
ssh ubuntu@10.197.113.57
password: "Pa$$w0rd"
The full stdout can be found in /root/deploy.out and the rest in /tmp: deployment.yaml and snaps-openstack source.
Cheers,
Steve
P.S. This is a virtual environment deployed to lab3

authors: RandyLevensalor chiraggupta06 spisarski

repo: cablelabs/snaps-openstack


text:
Current Investments for an authenticated user

To my knowledge there is currently no way to find out all the current investments for an authenticated user. Need to contact BTCJam and see if I am missing something or if it is on their roadmap.

When accessing BTCJam via the web the following call is made:
https://btcjam.com/listing_investments.json?for_user=true
I tried using a client_id and client_secret with this URL as well via the API URL; although, it doesn't appear that this route is accessible either way.

repo: cacciatc/btcjammer

license: mit

license_source: bigquery


text:
🛑 cache.bi Portal Data Service is down

In 614a3b3, cache.bi Portal Data Service (https://data.api.cache.bi/_health) was down:

HTTP code: 0
Response time: 0 ms

Resolved: cache.bi Portal Data Service is back up in 42601fe.

repo: cachetech/service-status


text:
🛑 CBTB Coffee House Shop is down

In 2be2f57, CBTB Coffee House Shop (https://shop.cbtb.coffee/) was down:

HTTP code: 403
Response time: 1327 ms

Resolved: CBTB Coffee House Shop is back up in 777a489.


text:
🛑 CBTB Coffee House Shop is down

In 5a3e22d, CBTB Coffee House Shop (https://shop.cbtb.coffee/) was down:

HTTP code: 403
Response time: 1199 ms

Resolved: CBTB Coffee House Shop is back up in b0d6ec1 after 20 minutes.


text:
Components API doesn't behave as documented

The documentation for the components API endpoint doesn't match the current code.
Here's the sample from the doc:
{
    "data":{
        "id":1,
        "name":"API",
        "description":"This is the Cachet API.",
        "status_id":1,
        "status":"Operational",
        "incident_count":0,
        "created_at":1425630835,
        "updated_at":1425719658
    }
}

And what you're actually getting with the current master:
{
    "data":
    {
        "id": "2",
        "name": "API",
        "description": "This is the Cachet API.",
        "link": "link",
        "status": "1",
        "order": "2",
        "group_id": "0",
        "created_at": "2015-07-22 16:47:20",
        "updated_at": "2015-07-28 17:46:15",
        "deleted_at": null
    }
}

status is a numeric ID and there's no textual representation of the status. It would be really useful to have a human readable message, for example to announce a partial outage on a site.

The documentation is out of date here. I'll update it as soon as I can. Sorry for this.

Thanks.
Are we supposed to parse the list of incidents to find the ones for a component instead of getting the status?

Are we supposed to parse the list of incidents to find the ones for a component instead of getting the status?

Sorry, do you mean that you want to find incidents for a certain status?

I would like to get the status (human readable) for a component from the API. As far as I understand I can only get that from the incidents API, not the components API (you only get a numeric status ID)

Docs are being updated.

Docs are done :) We've now added status_name.

authors: gregkare jbrooksuk

repo: cachethq/Cachet


text:
Update button in tab

Hi,
Thanks for a great product.
I have added a button to the tab via TabButton.
However, I wish to change the color of the Icon when it is clicked. Is this possible please?
Many Thanks
Garth

Unfortunately, the only way is to remove the tab and insert a new one. It's not good. I'm looking at how to make it easier ok?

I'm thinking of adding an optional id to the tab class. In addition, it also makes the attributes editable and notifiable. So, the button onPressed could get a tab from the controller using the id and change any attribute from it. What do you think?

Thank you so much for your quick response.
That idea sounds perfect - Thank you.
Another request please.
Is it possible to delimit the values on the hierarchy method in
docking_layout.dart?
Something like:
String hierarchy(
{bool indexInfo = false,
bool levelInfo = false,
bool hasParentInfo = false,
bool nameInfo = false}) {
String str = typeAcronym;
if (indexInfo) {
str += index.toString() + '|';
}
if (levelInfo) {
str += level.toString();
}
if (hasParentInfo) {
if (_parent == null) {
str += 'F';
} else {
str += 'T';
}
}
return str;
}
}
You will see the values are delimited by a '|'.
I use this a lot to serialize the panes to Json.
Many Thanks
Garth
On 2022-03-18 15:38, Carlos Eduardo Leite de Andrade wrote:

I'm thinking of adding an optional id to the tab class. In addition, it also makes the attributes editable and notifiable. So, the button onPressed could get a tab from the controller using the id and change any attribute from it. What do you think?
--
Reply to this email directly, view it on GitHub [1], or unsubscribe [2].
Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].
You are receiving this because you authored the thread.Message ID: @.***>

Links:
[1]
https://github.com/caduandrade/tabbed_view/issues/9#issuecomment-1072419717
[2]
https://github.com/notifications/unsubscribe-auth/AYJIKZ627IO6RER4KOU4SIDVASBMVANCNFSM5RBZ47XQ
[3]
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
[4]
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

DockingLayout is my other package. I can see it as well but first, let me change the TabbedView ok?

@garthawaters ,
Example of a State changing the color by recreating the buttons:
  late TabbedViewController _controller;

  TabButton _buildTabButton(Color color) {
    return TabButton(
        icon: IconProvider.data(Icons.star),
        color: color,
        hoverColor: color,
        onPressed: _onTabButtonPressed);
  }

  void _onTabButtonPressed() {
    TabData tab = _controller.getTabByIndex(0);
    tab.text = 'hello';
    tab.closable = false;
    tab.buttons = [_buildTabButton(Colors.red)];
  }

  @override
  void initState() {
    super.initState();
    _controller = TabbedViewController([
      TabData(
          buttons: [_buildTabButton(Colors.black)],
          text: 'Tab 1',
          content: Padding(child: Text('Hello'), padding: EdgeInsets.all(8)))
    ]);
  }

This works for you, right? Can I release a version?

Perfect, thank you
On 2022-03-18 16:04, Carlos Eduardo Leite de Andrade wrote:

DockingLayout is my other package. I can see it as well but first, let me change the TabbedView ok?
--
Reply to this email directly, view it on GitHub [1], or unsubscribe [2].
Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].
You are receiving this because you authored the thread.Message ID: @.***>

Links:
[1]
https://github.com/caduandrade/tabbed_view/issues/9#issuecomment-1072443018
[2]
https://github.com/notifications/unsubscribe-auth/AYJIKZ7NQFDVNXHUXZF6S43VASENPANCNFSM5RBZ47XQ
[3]
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
[4]
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

That certainly works for me - Thank you
On 2022-03-18 16:47, Carlos Eduardo Leite de Andrade wrote:

@garthawaters [1] ,
Example of a State changing the color by recreating the buttons:
late TabbedViewController _controller;
TabButton _buildTabButton(Color color) {
return TabButton(
icon: IconProvider.data(Icons.star),
color: color,
hoverColor: color,
onPressed: _onTabButtonPressed);
}
void _onTabButtonPressed() {
TabData tab = _controller.getTabByIndex(0);
tab.text = 'hello';
tab.closable = false;
tab.buttons = [_buildTabButton(Colors.red)];
}
@override
void initState() {
super.initState();
_controller = TabbedViewController([
TabData(
buttons: [_buildTabButton(Colors.black)],
text: 'Tab 1',
content: Padding(child: Text('Hello'), padding: EdgeInsets.all(8)))
]);
}
This works for you, right? Can I release a version?
--
Reply to this email directly, view it on GitHub [2], or unsubscribe [3].
Triage notifications on the go with GitHub Mobile for iOS [4] or Android [5].
You are receiving this because you were mentioned.Message ID: @.***>

Links:
[1] https://github.com/garthawaters
[2]
https://github.com/caduandrade/tabbed_view/issues/9#issuecomment-1072481797
[3]
https://github.com/notifications/unsubscribe-auth/AYJIKZ6OBMVEGTGT4HS7UTDVASJPLANCNFSM5RBZ47XQ
[4]
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
[5]
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

Done. 1.12.0 released. If anything else is missing, let me know.
If you can register a :thumbsup: on pub.dev or a :star: here on Github, I'd appreciate it!
About the docking issue, can you open a new issue on https://github.com/caduandrade/docking_flutter/issues ?
Thanks

Wow, your response is amazing, much appreciated
I will install and try the new version - Thanks again
On 2022-03-18 21:13, Carlos Eduardo Leite de Andrade wrote:

Done. 1.12.0 released. If anything else is missing, let me know.
If you can register a 👍 on pub.dev or a ⭐ here on Github, I'd appreciate it!
About the docking issue, can you open a new issue on https://github.com/caduandrade/docking_flutter/issues ?
Thanks
--
Reply to this email directly, view it on GitHub [1], or unsubscribe [2].
Triage notifications on the go with GitHub Mobile for iOS [3] or Android [4].
You are receiving this because you were mentioned.Message ID: @.***>

Links:
[1]
https://github.com/caduandrade/tabbed_view/issues/9#issuecomment-1072727285
[2]
https://github.com/notifications/unsubscribe-auth/AYJIKZ7B6KZJDHXIO25ENPDVATIULANCNFSM5RBZ47XQ
[3]
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
[4]
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub

authors: caduandrade garthawaters


text:
[Bug] Zipper Initiative leaves additional enemies at the bottom

So while zipper initiative works perfectly most of the time, when there are many enemies then they are all put at the bottom of the initiative after being put one after another.
For example, currently when you have 4 players and 10 enemies, the initiative might look like P1, E1, P2, E2, P3, E3, P4, E4, E5, E6, E7, E8, E9, E10.
However, this goes against the entire point of the zipper initiative system. Would it be possible to make it go down and up the initiative order?
So in an ideal situation, the above initiative order would instead be P1, E1, E8, E9, P2, E2, E7, E10, P3, E3, E6, P4, E4, E5.
I'm not sure if I'm clear, so feel free to ask me on Discord if what I'm asking isn't apparent.
Thank you very much 🙂

I think I understand what you mean. I added an "interleave" setting in v0.2.1 that does this.
It is not a bug to leave all the remaining enemies at the bottom, but rather intended behavior as described by at least some versions of the zipper initiative. But I get why that is not always desirable, thus the new setting!

authors: GhostwheelX caewok

repo: caewok/fvtt-zipper-initiative


text:
Error

سلام
وقتی روی هر ایتم کلیک میکنم
از سمت بازار پیغام این ایتم وجود ندارد میده
ممنون میشم راهنمایی کنید

سلام
لطفا چک کنید شناسه ای که وارد کردید تو پنل توسعه دهندگان بازار وجود داشته باشه و مطمئن بشیم که مقداری که تو ستون "شناسه‌ی کالا" هست رو تو فانکشن purchase وارد کرده باشیم .

از نمونه اپ داخل منبع استفاده کنید در صورتی که بدون مشکل خرید انجام می‌شود یا در پیشخان محصول خود را معرفی نکرده‌اید یا packagename اپ اشتباه است.

آیا بدون هیچ تغییر پروژه نمونه کار می کند؟

packagename  اپ کجا باید تعریف کرد؟

من طبق مستندات خود سایت پولکی پیش رفتم اما به خطا خورده

آیا بدون هیچ تغییر پروژه نمونه کار می کند؟

یاسخ این سوال رو هنوز دریافت نکردم

ببینید موارد دقیق انجام شده اما بازم وقتی رو ایتم کلیک میشه میگه محصولی وجود ندارد

  ببینید موارد دقیق انجام شده اما بازم وقتی رو ایتم کلیک میشه میگه محصولی وجود ندارد

هنوز پاسخ سوال قبل دریافت نشده است

packagename اپ کجا باید تعریف کرد؟
این مسئله در مورد تکنولوژی فلاتر بوده و ارتباطی به این پروژه ندارد.

الان این ارور بخاطر همین پکیج نیم هست؟

Reference in ne

بله کار میکنه

منتهی من سعی کردم از کد همون سورس منبع استفاده کنم اما اوکی نمیشد و محصول رو شناسایی نمیکرد

پکیج نیم این اپ درحال حاضر اینه
صرفا یک اپ تست برای اتصال به بازاره که همچنان تو خطاست

این به این معنی هست که پلاگین مشکلی نداره و شما در تغییراتی که در پروژه ایجاد می‌کنید احتمالا اشتباهی رخ داده. سه نوع تغییرات بایست داشته باشید در انجام مراحل دقت فرمایید.
packagename
base64RSAkey
productIds

ببینید من متوجه نشدم تغیرات
packagename
base64RSAkey
کجا هستند اخه تو مستندات ذکر نشده
میشه یک توضیح بدید؟

authors: AliZahmatkesh manjav msmoradi


text:
Mask R-CNN Model

From my understanding, the Mask R-CNN model (https://arxiv.org/abs/1703.06870) was implemented using Caffe2. Could the code be released as part of Caffe2 or as a tutorial? It would be great if the ROIAlign layer and other necessary components were included in Caffe2. I think it would help Caffe2 gain more traction.
Is there anything that the community can do to help make this happen (like with assisting the tutorial)?
In case @KaimingHe, @gkioxari, or other co-authors read this, is there an expected release time of the Mask R-CNN code?

I am also interested in this. Is anybody working on it?

hope to see more example code with caffe2

authors: MartinPlantinga jiangnanhugo williford


text:
Compilation error in gloo

I am building the framework on Ubuntu 14.04, and i get a compilation error with gloo. When i disable gloo in the CMakeLists, everything works well.
Here is the error:

[ 14%] Building NVCC (Device) object third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/nccl/./gloo_cuda_generated_nccl.cu.o
/home/sherif/caffe2/third_party/gloo/gloo/nccl/nccl.cu(36): error: argument of type "const int *" is incompatible with parameter of type "int *"

1 error detected in the compilation of "/tmp/tmpxft_00006488_00000000-7_nccl.cpp1.ii".
CMake Error at gloo_cuda_generated_nccl.cu.o.cmake:260 (message):
Error generating file
/home/sherif/caffe2/build/third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/nccl/./gloo_cuda_generated_nccl.cu.o

Thanks for the bug report. I've not seen this before. Do you happen to have some version of NCCL installed on your machine? Could you paste the CMake summary (including dependency versions) that the C2 CMake process displays? Maybe there is a clue in there...

-- Found Git: /usr/bin/git (found version "1.9.1")
-- Build type not set - defaulting to Release
-- Looking for include file pthread.h
-- Looking for include file pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Found PROTOBUF: /usr/lib/x86_64-linux-gnu/libprotobuf.so
-- The BLAS backend of choice:Eigen
-- Could NOT find NNPACK (missing:  NNPACK_INCLUDE_DIR NNPACK_LIBRARY)
-- Will try to build NNPACK from source. If anything fails, follow the NNPACK prerequisite installation steps.
CMake Warning at cmake/External/nnpack.cmake:157 (message):
NNPACK is chosen to be installed, but confu and ninja that are needed by it
are not installed.  As a result we won't build with NNPACK.
Call Stack (most recent call first):
cmake/Dependencies.cmake:52 (include)
CMakeLists.txt:85 (include)
CMake Warning at cmake/Dependencies.cmake:57 (message):
Not compiling with NNPACK.  Suppress this warning with -DUSE_NNPACK=OFF
Call Stack (most recent call first):
CMakeLists.txt:85 (include)
-- Found GFlags: /usr/include
-- Found gflags  (include: /usr/include, library: /usr/lib/x86_64-linux-gnu/libgflags.so)
-- Found system gflags install.
-- Found Glog: /usr/include
-- Found glog    (include: /usr/include, library: /usr/lib/x86_64-linux-gnu/libglog.so)
-- Found system glog install.
-- Found PythonInterp: /usr/bin/python (found version "2.7.6")
-- git Version: v0.0.0
-- Version: 0.0.0
-- Performing Test HAVE_CXX_FLAG_STD_CXX11
-- Performing Test HAVE_CXX_FLAG_STD_CXX11 - Success
-- Performing Test HAVE_CXX_FLAG_WALL
-- Performing Test HAVE_CXX_FLAG_WALL - Success
-- Performing Test HAVE_CXX_FLAG_WEXTRA
-- Performing Test HAVE_CXX_FLAG_WEXTRA - Success
-- Performing Test HAVE_CXX_FLAG_WSHADOW
-- Performing Test HAVE_CXX_FLAG_WSHADOW - Success
-- Performing Test HAVE_CXX_FLAG_WERROR
-- Performing Test HAVE_CXX_FLAG_WERROR - Success
-- Performing Test HAVE_CXX_FLAG_PEDANTIC
-- Performing Test HAVE_CXX_FLAG_PEDANTIC - Success
-- Performing Test HAVE_CXX_FLAG_PEDANTIC_ERRORS
-- Performing Test HAVE_CXX_FLAG_PEDANTIC_ERRORS - Success
-- Performing Test HAVE_CXX_FLAG_WSHORTEN_64_TO_32
-- Performing Test HAVE_CXX_FLAG_WSHORTEN_64_TO_32 - Failed
-- Performing Test HAVE_CXX_FLAG_WFLOAT_EQUAL
-- Performing Test HAVE_CXX_FLAG_WFLOAT_EQUAL - Success
-- Performing Test HAVE_CXX_FLAG_FSTRICT_ALIASING
-- Performing Test HAVE_CXX_FLAG_FSTRICT_ALIASING - Success
-- Performing Test HAVE_CXX_FLAG_WZERO_AS_NULL_POINTER_CONSTANT
-- Performing Test HAVE_CXX_FLAG_WZERO_AS_NULL_POINTER_CONSTANT - Success
-- Performing Test HAVE_CXX_FLAG_WSTRICT_ALIASING
-- Performing Test HAVE_CXX_FLAG_WSTRICT_ALIASING - Success
-- Performing Test HAVE_CXX_FLAG_WTHREAD_SAFETY
-- Performing Test HAVE_CXX_FLAG_WTHREAD_SAFETY - Failed
-- Performing Test HAVE_CXX_FLAG_COVERAGE
-- Performing Test HAVE_CXX_FLAG_COVERAGE - Success
-- Performing Test HAVE_STD_REGEX
-- Performing Test HAVE_STD_REGEX -- compiled but failed to run
-- Performing Test HAVE_GNU_POSIX_REGEX
-- Performing Test HAVE_GNU_POSIX_REGEX -- failed to compile
-- Performing Test HAVE_POSIX_REGEX
-- Performing Test HAVE_POSIX_REGEX -- success
-- Performing Test HAVE_STEADY_CLOCK
-- Performing Test HAVE_STEADY_CLOCK -- success
-- Performing Test BENCHMARK_HAS_CXX03_FLAG
-- Performing Test BENCHMARK_HAS_CXX03_FLAG - Success
-- Found LMDB: /usr/include
-- Found lmdb    (include: /usr/include, library: /usr/lib/x86_64-linux-gnu/liblmdb.so)
-- Found LevelDB: /usr/include
-- Found LevelDB (include: /usr/include, library: /usr/lib/x86_64-linux-gnu/libleveldb.so)
-- Found Snappy: /usr/include
-- Found Snappy  (include: /usr/include, library: /usr/lib/libsnappy.so)
-- Could NOT find RocksDB (missing:  RocksDB_INCLUDE_DIR RocksDB_LIBRARIES)
CMake Warning at cmake/Dependencies.cmake:131 (message):
Not compiling with RocksDB.  Suppress this warning with -DUSE_ROCKSDB=OFF
Call Stack (most recent call first):
CMakeLists.txt:85 (include)
-- OpenCV found (/usr/share/OpenCV)
-- Found PythonInterp: /usr/bin/python (found suitable version "2.7.6", minimum required is "2.7")
-- Found PythonLibs: /usr/lib/x86_64-linux-gnu/libpython2.7.so (found suitable version "2.7.6", minimum required is "2.7")
-- Found NumPy: /usr/local/lib/python2.7/dist-packages/numpy/core/include (found version "1.11.0")
-- NumPy ver. 1.11.0 found (include: /usr/local/lib/python2.7/dist-packages/numpy/core/include)
-- Found MPI_C: /usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so
-- Found MPI_CXX: /usr/lib/libmpi_cxx.so;/usr/lib/libmpi.so;/usr/lib/x86_64-linux-gnu/libdl.so;/usr/lib/x86_64-linux-gnu/libhwloc.so
-- MPI support found
-- MPI compile flags:
-- MPI include path: /usr/lib/openmpi/include/usr/lib/openmpi/include/openmpi
-- MPI LINK flags path:
-- MPI libraries: /usr/lib/libmpi_cxx.so/usr/lib/libmpi.so/usr/lib/x86_64-linux-gnu/libdl.so/usr/lib/x86_64-linux-gnu/libhwloc.so
CMake Warning at cmake/Dependencies.cmake:222 (message):
OpenMPI found, but it is not built with CUDA support.
Call Stack (most recent call first):
CMakeLists.txt:85 (include)
-- Try OpenMP C flag = [-fopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Success
-- Try OpenMP CXX flag = [-fopenmp]
-- Performing Test OpenMP_FLAG_DETECTED
-- Performing Test OpenMP_FLAG_DETECTED - Success
-- Found OpenMP: -fopenmp
-- Adding -fopenmp
-- CUDA detected: 7.5
-- Added CUDA NVCC flags for: sm_52
-- Found libcuda: /usr/lib/x86_64-linux-gnu/libcuda.so
-- Found libnvrtc: /usr/local/cuda/lib64/libnvrtc.so
-- Found CUDNN: /usr/local/cuda/include
-- Found cuDNN: v5.1.3  (include: /usr/local/cuda/include, library: /usr/local/cuda/lib64/libcudnn.so)
-- Found NCCL: /usr/include
-- Found NCCL    (include: /usr/include, library: /usr/lib/x86_64-linux-gnu/libnccl.so)
-- NCCL: /usr/lib/x86_64-linux-gnu/libnccl.so
-- MPI include path: /usr/lib/openmpi/include/usr/lib/openmpi/include/openmpi
-- MPI libraries: /usr/lib/libmpi_cxx.so/usr/lib/libmpi.so/usr/lib/x86_64-linux-gnu/libdl.so/usr/lib/x86_64-linux-gnu/libhwloc.so
-- Found CUDA: /usr/local/cuda (found suitable version "7.5", minimum required is "7.0")
-- CUDA detected: 7.5
-- Found libcuda: /usr/lib/x86_64-linux-gnu/libcuda.so
-- Found libnvrtc: /usr/local/cuda/lib64/libnvrtc.so
-- Performing Test CAFFE2_LONG_IS_INT32_OR_64
-- Performing Test CAFFE2_LONG_IS_INT32_OR_64 - Success
-- Does not need to define long separately.
-- Performing Test HAS_BUILTIN_CPU_SUPPORTS
-- Performing Test HAS_BUILTIN_CPU_SUPPORTS - Success
-- This compiler has builtin_cpu_supports feature.
-- Performing Test CAFFE2_NEED_TO_TURN_OFF_DEPRECATION_WARNING
-- Performing Test CAFFE2_NEED_TO_TURN_OFF_DEPRECATION_WARNING - Failed
-- Turning off deprecation warning due to glog.
-- GCC 4.8.4: Adding gcc and gcc_s libs to link line
-- Including MPI binaries
-- Including OPENCV binaries
-- Include NCCL operators
-- Including image processing operators
-- Excluding mkl operators as we are not using mkl
-- Automatically generating missing init.py files.
-- ******** Summary ********
-- General:
--   Git version           : v0.7.0-122-g6a9906e
--   System                : Linux
--   C++ compiler          : /usr/bin/c++
--   Protobuf compiler     : /usr/bin/protoc
--   CXX flags             :  -fopenmp -Wno-deprecated -std=c++11 -fPIC -Wno-narrowing
--   Build type            : Release
--   Compile definitions   : CAFFE2_USE_EIGEN_FOR_BLAS;CAFFE2_USE_GOOGLE_GLOG;CAFFE2_USE_GFLAGS;EIGEN_MPL2_ONLY;CAFFE2_FORCE_FALLBACK_CUDA_MPI
--   BUILD_SHARED_LIBS     : ON
--   BUILD_PYTHON          : ON
--     Python version      : 2.7.6
--     Python library      : /usr/lib/x86_64-linux-gnu/libpython2.7.so
--   USE_CUDA              : ON
--     CUDA version        : 7.5
--   USE_CNMEM             : OFF
--   USE_NERVANA_GPU       : OFF
--   USE_GLOG              : ON
--   USE_GFLAGS            : ON
--   USE_LMDB              : ON
--     LMDB version        : 0.9.10
--   USE_LEVELDB           : ON
--     LevelDB version     : 1.15
--     Snappy version      : 1.1.0
--   USE_OPENCV            : ON
--     OpenCV version      : 2.4.8
--   USE_ZMQ               : OFF
--   USE_ROCKSDB           : OFF
--   USE_MPI               : ON
--   USE_NCCL              : ON
--   USE_NNPACK            : OFF
--   USE_OPENMP            : ON
--   USE_REDIS             : OFF
--   USE_GLOO              : ON
-- Configuring done
-- Generating done
-- Build files have been written to: /home/sherif/caffe2/build

@sherifshehata Thanks for the paste. Your build is picking up the system NCCL version, which likely is older than the one we're expecting. Can you try using the vendored version instead? I don't think we have an option to explicitly opt out of the system version, so you may have to uninstall it for this to work...

which NCCL version is needed?

NCCL 1.3.1 or higher. This is the bundled version. We don't have a version check in place but looking at your issue this is worth considering.

I'm not sure if older versions will work. We only use it with 1.3.1 or higher.

ok, thank you.

authors: pietern sherifshehata


text:
fix right click crashes

Describe the bug
When Cario is open, right clicking causes most apps, or Cario to crash.
Steps to reproduce

Have my windows-related issues (Additional context)
open any app (it happens on Cario too) besides notepad++ and browsers
keep right clicking anywhere on that app until it crashes (about 3x)
I know for a fact that this is a Cario (+my issue, excuse me) related issue because  my apps don't crash when I right click when the desktop is empty (no shell is running)
Expected behavior
Apps don't crash.

System information:
Cario 0.4.1588.53003 pr on Windows 11 1H2 Build 2000.318 (shell disabled)
Additional context
Post I made for some reason on MS-Docs

based off of the thread you linked in, it sounds like the Windows Explorer shell isn't properly initializing on login. given that, I think you may want to try the following:

open Cairo Settings, and under Advanced, note which shell is currently set as "your shell" (usually either Cairo or Windows Explorer).
if Cairo's set as the shell, click "Set Windows Explorer as Shell" and then log out/log in when prompted to have it take effect.
if Windows Explorer is set as the shell, click "Set Cairo as Shell", log out/in, and then reopen Cairo Settings to reset it to Windows Explorer via step 2.

hope this helps.

Thank you for trying, but I've already reset my pc.
I had to reset twice for the same issue, but it turns out that explorer decided to stop working, just once more. but, fortunately, resetting my pc fixed part of the issue. right clicking is fixed, and thanks to the new update, I can now access notifications and the other little menu containing connections, and (I'm guessing a windows update, when explorer decides it wants to start up successfully, it simply shown a black screen before. I had no access to touchpad gestures) when I use a gesture, the shortcut activates. and I missed the volume bar in the top left.
but settings still refuse to start. so...........

repo: cairoshell/cairoshell


text:
A question about experiment setup

Hi,
Thanks for your amazing work.
I would like to ask a step concerning the "3.1 Experiment step" in the paper.
In the paper, you stated that "G uses clean images from DIV2K [59], Flickr2K [60], BSD68 [61], Kodak24 [62], and Urban100 [63] to generate realistic noisy-clean image pairs". I assume this step is in the (b) training phrase and the generated (fake) noisy images and corresponding real noisy images will be inputted into two discriminator to train them.
However, some of the datasets (Flickr2K, Kodak24, Urban100) you used in this phase don't contain noisy images. I don't know how could the training of the two discriminator be done in the phase. Or you just add gaussian noise to these three dataset and regard them as real noisy images.
Thanks in advance for the clarification.

Correct


text:
Wrong language variable

# i18n/en.php
'editor.blocks.gallery.settings.imageAlt.label' => 'Gallery Alt Name',

I realised I've actually not used this setting as it's difficult to set alt text on gallery of images. Any thoughts on what this could be?
Options are some sort of gallery caption, or to remove this setting.

Actually I just realised I've missed a few more items in the translations, let me add those too. :) @medienbaecker Hope you'd be able to help me with the German translations for those

Thanks for adding the missing items! ❤
One thing that's still untranslated is the "or" between "Upload images" and "Select images".

Ah yes, great point! I'll reopen this until all the fixes are in. :)

authors: cajames medienbaecker

repo: cajames/kirby-editor-gallery-block


text:
(GH-30) added icons for Cake files

I switched from using the png file to using the svg file, as providing
different icon sizes is much easier here.
fixes #30

@nils-a your changes have been merged, thanks for your contribution 👍

@nils-a your changes have been merged, thanks for your contribution 👍

repo: cake-build/cake-rider


text:
Add descriptions and enum values to vscode cake settings on package.json

Add descriptions and default values to subsections on package.json configuration without breaking changes.
Affected sections:

cake.taskRunner
cake.bootstrappers
cake.configuration

@jrgcubano this sounds like a good idea to me!

repo: cake-build/cake-vscode


text:
XmlPeek not working correctly for element nodes

What You Are Seeing?
I have the following XML document:
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
  <PropertyGroup>
    <WebPublishMethod>FileSystem</WebPublishMethod>
    <LastUsedBuildConfiguration>DeploymentTemplate</LastUsedBuildConfiguration>
    <LastUsedPlatform>Any CPU</LastUsedPlatform>
    <SiteUrlToLaunchAfterPublish />
    <LaunchSiteAfterPublish>True</LaunchSiteAfterPublish>
    <ExcludeApp_Data>False</ExcludeApp_Data>
    <publishUrl>C:\Deployment\DeploymentTemplate\WebApi</publishUrl>
    <DeleteExistingFiles>False</DeleteExistingFiles>
  </PropertyGroup>
</Project>

The following code does not yield the publishUrl element (instead null ist returned and a warning is logged):
var xmlPeekSettings = new XmlPeekSettings
{
  Namespaces = new Dictionary<string, string>{
    { "msbuild", "http://schemas.microsoft.com/developer/msbuild/2003" }
  }
};

var xmlElementContents = XmlPeek(pubXmlFile,
  "/msbuild:Project/msbuild:PropertyGroup/msbuild:publishUrl", xmlPeekSettings);

Running the same code using the standard .NET XPathDocument works okay.
What is Expected?
XmlPeek should return the contents of the publishUrl element, i.e. C:\Deployment\DeploymentTemplate\WebApi.
When using XPathDocument everything works okay:
using (var stream = new System.IO.FileStream(pubXmlFile.ToString(), FileMode.Open))
{
  var xPathDocument = new System.Xml.XPath.XPathDocument(stream);
  var navigator = xPathDocument.CreateNavigator();

  System.Xml.XmlNamespaceManager ns = null;

  if (navigator.NameTable != null)
  {
    ns = new System.Xml.XmlNamespaceManager(navigator.NameTable);
    ns.AddNamespace("msbuild", "http://schemas.microsoft.com/developer/msbuild/2003");
  }

  var node = navigator.SelectSingleNode(
    "/msbuild:Project/msbuild:PropertyGroup/msbuild:publishUrl", ns);
}

Here node contains the selected node.
What version of Cake are you using?
Version 0.17.0
Are you running on a 32 or 64 bit system?
64bit
What environment are you running on?  Windows? Linux? Mac?
Windows
How Did You Get This To Happen? (Steps to Reproduce)
See code above.

[Proposal for a Bugfix]
After some investigation I found the bug. Have a look at line https://github.com/cake-build/cake/blob/303b1d092864ae119cbcfb9d3430b99cb8d3bd4f/src/Cake.Common/Xml/XmlPeekAliases.cs#L141:
When calling method SelectSingleNode(...) on an instance of XmlDocument, an XmlNode is returned. Then in turn when reading the Value property, null is returned for nodes of type XmlNodeType.Element (so say the docs from Microsoft).
This does not happen if you are using an XPathNavigator - yes, this is really weird, but it works.
Here the corrected code:
/// <summary>
/// Gets the value of a target node.
/// </summary>
/// <returns>The value found at the given XPath query (or the first, if multiple eligible nodes are found).</returns>
/// <param name="source">The source xml to transform.</param>
/// <param name="xpath">The xpath of the nodes to set.</param>
/// <param name="settings">Additional settings to tweak Xml Peek behavior.</param>
private static string XmlPeek(XmlReader source, string xpath, XmlPeekSettings settings)
{
    if (source == null)
    {
        throw new ArgumentNullException(nameof(source));
    }

    if (string.IsNullOrWhiteSpace(xpath))
    {
        throw new ArgumentNullException(nameof(xpath));
    }

    if (settings == null)
    {
        throw new ArgumentNullException(nameof(settings));
    }

    var document = new XmlDocument();
    document.PreserveWhitespace = settings.PreserveWhitespace;
    document.Load(source);

    var navigator = document.CreateNavigator();
    XmlNamespaceManager namespaceManager = null;

    if (navigator.NameTable != null)
    {
        namespaceManager = new XmlNamespaceManager(navigator.NameTable);
        foreach (var xmlNamespace in settings.Namespaces)
        {
            namespaceManager.AddNamespace(xmlNamespace.Key /* Prefix */, xmlNamespace.Value /* URI */);
        }
    }

    var node = navigator.SelectSingleNode(xpath, namespaceManager);

    return node?.Value;
}

I have just updated to Cake version 0.21.1 and it is still happening.
Any estimation about when this will be fixed?
Thanks!

Currently I have not the time to drop a pull request, but the code I posted above fixes the issue. Maybe some of the Cake guys can take the code snippet and fix that bug. ;-)

fixed by #1701

authors: alvaromongon devlead peter-perot

repo: cake-build/cake


text:
GH3878: Adds support for case sensitive OpenCover filters

Currently, if you try to apply multiple (case-sensitive) filters (with same-ish values) in your cake script like this:
var coverageInclusionFilters = new List<string>
{
   "+[ModuleName*]*",
   "+[moduleName*]*"
};

var openCoverSettings = new OpenCoverSettings();
//rest of the code omitted for clarity

for(var inclusionFilter in coverageInclusionFilters)
{
   openCoverSettings.WithFilter(inclusionFilter);
}

It produces this kind of a filter argument value:
-filter:"+[ModuleName*]*"

containing only the first one from the coverageInclusionFilters list from the code above.
As per https://github.com/opencover/opencover/wiki/Usage#understanding-filters
OpenCover filters are case-sensitive.
This change enables you to apply those kind of filter values.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: lynkx sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

cc @DNikolina

@lynkx your changes have been merged, thanks for your contribution 👍

authors: devlead dnfadmin lynkx


text:
Recommended changes resulting from automated audit

We performed an automated audit of your Cake addin and found that it does not follow all the best practices.
We encourage you to make the following modifications:

[ ] You are currently referencing Cake.Core 0.31.0. Please upgrade to 0.33.0
[ ] The Cake.Core reference should be private. Specifically, your addin's .csproj should have a line similar to this: <PackageReference Include="Cake.Core" Version="0.33.0" PrivateAssets="All" />
[ ] The nuget package for your addin should use the cake-contrib icon. Specifically, your addin's .csproj should have a line like this: <PackageIconUrl>https://cdn.jsdelivr.net/gh/cake-contrib/graphics/png/cake-contrib-medium.png</PackageIconUrl>.

Apologies if this is already being worked on, or if there are existing open issues, this issue was created based on what is currently published for this package on NuGet.
This issue was created by a tool: Cake.AddinDiscoverer version 3.12.1

We performed a follow up automated audit of your Cake addin and found that some (or all) issues previously identified have not been resolved.
We strongly encourage you to make the modifications previously highlighted.
Apologies if this is already being worked on, or if there are existing open issues, this issue was created based on what is currently published for this package on NuGet.
This comment was created by a tool: Cake.AddinDiscoverer version 3.12.1


text:
🛑 xmr-node.cakewallet.com:18081 is down

In 83abb93, xmr-node.cakewallet.com:18081 (xmr-node.cakewallet.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: xmr-node.cakewallet.com:18081 is back up in ec3e2c2 after 19 minutes.

repo: cake-tech/upptime-cakewallet


text:
🛑 node.moneroworld.com:18089 is down

In abb1dba, node.moneroworld.com:18089 (node.moneroworld.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: node.moneroworld.com:18089 is back up in b9c129e after 7 minutes.

repo: cake-tech/upptime-monerocom


text:
Same link for historical snapshot and documentation div (box #2 and #3)

Both divs link to http://calaccess.californiacivicdata.org/files/.

Thanks. If we ironed out the bugs, what do you think of the boxes as lead promo art on the page? Are they big and bold enough?

I think they stand out and would do well. But, in my opinion, a description of what CAL-ACCESS is should precede the boxes, just to complement what the boxes offer. Right now, the lead is California Civic Data Coalition, when the website is about CAL-ACCESS. What do you think?

authors: palewire ssdatar


text:
List Item radio button

Checkox available, but no radio button available

The hierarchy is a little off, but it's there: http://material-ui.com/#/components/switches
See the tabs. Checkbox, RadioButtons, and Toggle.
This can be marked as resolved.

ListItem have properties such as leftCheckbox and rightToggle.
I want to have something like leftRadio

This make me think that the ListItem component should be composable instead of having an long list of property.

Agree.

Radio is available, the other topic is irrelevant to this issue. If you have trouble composing components please open another issue. Thank you

I feel like that answer is pretty unsatisfactory. If anyone is trying to find a solution to this, this looks like an option http://stackoverflow.com/questions/37150254/radiobuttongroup-within-nested-list

authors: danwoods luckyraul matthewoates oliviertassinari subjectix

repo: callemall/material-ui


text:
[Tabs] TabIndicator width is being calculated before fonts are loaded

Hello!
I believe I've found a small bug. I'm happy to take a look at fixing this, but I could use some direction on what would be the best approach.
Problem description
The width of TabIndicators seem to be calculated before fonts are loaded. Here's an example of what I'm seeing:

Notice the indicator is wider than the radial background. Here is an example of the background on Tabs using Helvetica:

Both changing tabs and resizing the window fires events that cause the indicator to resize itself correctly.

Link to minimal working code that reproduces the issue
https://github.com/zachwolf/tab-spacing-demo

Versions

Material-UI: 1.0.0-alpha.19
React: 15.6.0
Browser: Chrome 59.0.3071.86

Thanks!

I have noticed that issue too many times. Any idea how to fix it? I thought that if that was going to be a real issue, I were going to make so that the default font (not the one loaded) would match the spacing of the loaded one as much as possible.

For the Tabs, there's two possible solutions that I can think of.

Restructure the html. It would be possible (although maybe difficult) to give each Tab an indicator and wait until it's interacted with to create another indicator to handle the animation.

Blindly call the getTabsMeta.

An idea for fixing this globally would be to create a component that listens for a font to be loaded. It could broadcast a global event which other components could listen to.
What are your thoughts on these?

Blindly call the getTabsMeta.

Yeah, we could try calling it a few time right after the first mount hoping for the better (the font to be loaded). This is a naive and poorly performant solution. Let's see if we can do better.

An idea for fixing this globally would be to create a component that listens for a font to be loaded.

I'm not sure we can find something that works across our supported browsers. Oh yes, there is fontfaceobserver.
This issue makes me think that we need a strong story around font loading. This article is a must-read on the topic. This tool is interesting regarding reducing width jump. It can be used to make is imperceptible while still present.
Terminology:

FOUT: (Flash of Unstyled Text) browsers display a fallback font in the font stack until the custom one loaded.
FOIT: (Flash of Invisible Text) browsers detect if the text was set in a custom font that hasn't loaded yet, and made it invisible until the font did load.

I've thought about this problem for a bit, and upon weighing my options, I decided that implementing an 'initial' indicator (for the first render) on the tab itself, and then using an absolutely positioned indicator on subsequent renders (once the tab index changes). The two indicators are mutually exclusive: once the tab index changes, you transition from using the 'initial' indicator to the one absolutely positioned with respect to all the tabs.
By relying on the width of the tab, the 'initial' indicator automatically reflows when content changes -- so the timing FOUT issue fizzles out.
The strongest upside to this approach is that you don't have to watch fonts or add in some external library that handles watching resize events on DOM elements. You do need to keep an internal boolean in the tab component state to keep track of if you have a changed tab index or not.
Before:

After:

Here's my implementation but it'd be pretty easy to adapt to concepts:
Initially shown tab:
https://github.com/collegepulse/material-react-components/blob/master/src/Tabs/Tab.js#L22-L27
New state to keep track of:
https://github.com/collegepulse/material-react-components/blob/master/src/Tabs/Tabs.js#L21-L25

@petermikitsh Thanks for sharing your approach but I don't think that we want to go into that direction. We need to address the root of the issue. It's not ok to have the font "jump" that way. Once we solve it, the tab issue is solved to for free.

@oliviertassinari To my understanding (and please correct if I'm wrong here) the indicator width is calculated before the custom font is loaded. So suppose this is how you have your DOM configured, with respect to getting your fonts initialized:
<html>
  <head>
    <link href="https://fonts.googleapis.com/css?family=Roboto:300,400,500" rel="stylesheet">
    <style type="text/css">
      html, body {
        font-family: 'Roboto', sans-serif;
      }
    </style>
  </head>
  <body>
    ...
  </body>
</html>

The browser will first render with sans-serif, and once Roboto is downloaded (presuming here that it's not installed locally on the machine), Roboto loads and then the browser reflows.
But since you calculated in width of the indicator when sans-serif was used, you end up with the incorrect indicator width. The browser reflowed, and the width of the tab changed, but the width of the indicator didn't.
I think it ultimately comes down to being a limitation of the browser. The browser asynchronously reflowing when a font loads is something you cannot control. But you can control when and how you calculate the indicator width.
I think you'd have to be watching for when the font is loaded, and then recalculate the indicator styles. That would probably mean having an interface for consumers to tell you what custom font they use in their Tabs as well. Fontfaceobserver appears to be a solid cross-browser solution, but on a slow network connection, you be waiting up to 3 seconds (fontfaceobserver's default timeout) before calculating the indicator width.

the indicator width is calculated before the custom font is loaded.

Yes, that's what is happening.

The browser asynchronously reflowing when a font loads is something you cannot control.

I don't agree, following my previous link regarding how to handle font loading: https://github.com/callemall/material-ui/issues/7187#issuecomment-309911023
There is a variety of solutions, basicaly, you either 1. make the font loading before rendering the React tree or 2. you make is so you minimize the font "jump" by tweaking the default font size dimensions.

One can already be implemented on userland, 2. Two can now be implemented with https://github.com/callemall/material-ui/pull/7461 by updating the theme font once the Roboto font is loaded.

I need to implement one of these solutions at work to be sure but I believe we can close the issue with: fix the font loading, no need for extra code complexity on the tabs component (that have a cost, like extra payload)

We went with changing the implementing to work server side using a width: 100% under the active tab.

authors: oliviertassinari petermikitsh zachwolf


text:
Way icons are imported

Each icon needs to be imported separetely. E.g.:
import CallIcon from 'material-ui-icons/Call';
import CallEndIcon from 'material-ui-icons/CallEnd';
import ExitToAppIcon from 'material-ui-icons/ExitToApp';
import LanguageIcon from 'material-ui-icons/Language';
import RefreshIcon from 'material-ui-icons/Refresh';

<CallIcon />
<CallEndIcon />
<ExitToAppIcon />
<LanguageIcon />
<RefreshIcon />

Wouldn't it be better if all icons could be in signle alias and then used:
import * as i from 'material-ui-icons';

<i.Call />
<i.CallEnd />
<i.ExitToApp />
<i.Language />
<i.Refresh />

Or if somebody doesn't like aliases, they could still list all imports like:
import {
    Call as CallIcon,
    CallEnd as CallEndIcon,
    ExitToApp as ExitToAppIcon,
    Language as LanguageIcon,
    Refresh as RefreshIcon,
} from 'material-ui-icons';

<CallIcon />
<CallEndIcon />
<ExitToAppIcon />
<LanguageIcon />
<RefreshIcon />

?
In order to do that, typings would have to be written like
declare module 'material-ui-icons' {
    import SvgIcon from 'material-ui/SvgIcon';
    export class Call extends SvgIcon {}
}

instead of:
declare module 'material-ui-icons/Call' {
    import SvgIcon from 'material-ui/SvgIcon';
    export default class Call extends SvgIcon {}
}

Wouldn't this greatly increase the bundle size and not take advantage of tree shaking?

Wouldn't it be better if all icons could be in signle alias and then used:

As far as I know, you can already do the described pattern.

@oliviertassinari  then you know it wrong :)
import * as i from 'material-ui-icons';

$ ./node_modules/.bin/webpack
...
ERROR in [at-loader] ./src/browser/components/component/view.tsx:14:20
    TS2306: File '/var/www/html/project/node_modules/material-ui-icons/index.d.ts' is not a module.
...

some versions:
material-ui@1.0.0-beta.6
material-ui-icons@1.0.0-beta.5
typescript@2.5.1

@sebald Is this a typescript issue?

Current release has no "index export" (#7820). Was added in #7874, if I didn't mess up.
So import all the icons should be possible with the next release, I guess.

ok, thanks.

authors: nenadalm oliviertassinari sebald the-simian


text:
[Dialog] Add style prop to some propTypes

The style props is used to override the main style, it's useful to have. might as well document it in a way.

:+1: Sounds good. I would suggest using https://github.com/nkt/babel-plugin-react-remove-prop-types for those how don't want to suffer from useless propTypes in production

Thanks. It seems like there are more like this. I'm gonna fix them before merging.

I'll squash to one commit and open a new one.

authors: oliviertassinari subjectix


text:
Fixed GridList style broken in Safari

Flex require -webkit- prefix to work in Safari.
Fixed GridTile height: it was NaN if you set cellHeight using a 'px' value.

Looks fine to me. @shaurya947 ?

:+1:

Oups (https://github.com/callemall/material-ui/pull/1686#issuecomment-149927077)

Haha no worries. Feel free to merge #1686 too

authors: oliviertassinari shaurya947 vinzscam


text:
feature: チャットAPI関連の仕様を定義

やったこと

チャットルーム作成・一覧取得エンドポイントの仕様定義
チャットメッセージの送信エンドポイントの仕様定義

レビュー時のポイント

@sea-kai が実装中のチャット機能で必要なものが記載されてるか確認してほしい

残タスク

Firestoreの設計図の作成

備考

下記4つのエンドポイントについての仕様書を作成しました
リクエスト/レスポンス値については、 Gifted Chat の型定義を参考にしてます

@hamachans
レビューありがとう!!指摘してもらった箇所、修正しました!!

repo: calmato/gran-book


text:
How to find MAC address

Hello! This isn't really an issue per se but wanted to add this in case it helps anyone else. The iOS app at least (not sure about Android) doesn't tell you the MAC address so here's how I found it.
From a terminal on the Pi where I'm running homebridge I ran hcitool lescan. and look for a line that looks something like "41:55:55:93:3A:79 FELLOW". That will be the MAC address you want to put into api.py.
With that setup the homebridge plugin is working, so thanks!

Thanks for the feedback! I'll try to remember to update the documentation with this information.
I'm glad to hear it is working for you!

authors: calvinmclean keithnorm

repo: calvinmclean/stagg-ekg-plus


text:
Release version 0.1.0

I would like to cut 0.0.0 release, so my gateway installation script [1] could download the latest gateway fat jar from Maven central.
FYI Gateway is a Spring Boot based fat jar that can be used as a "default" application installed on Rasbian to collect the messages from the sensors and send them to the data center.
[1] https://github.com/camel-labs/camel-labs/blob/master/iot/initd/rasbian/get-camel-labs-iot-gateway-rasbian.sh

Let's try to focus on closing the task we have assigned to 0.0.0 milestone.

The Tinkerforge component is ready, so I think we're good for the 0.1 release.

Great. I will cut the release soon.

Done.

authors: geertschuring hekonsek

repo: camel-labs/camel-labs


text:
remove hardcode CAS_USERNAME

remove hardcode CAS_USERNAME
add code to gen new session when login successful

Looks good. The problem is I am not set up to test this. I need access to a CAS Server, any suggestions?

Looks good. The problem is I am not set up to test this. I need access to a CAS Server, any suggestions?

You can try https://casserver.herokuapp.com/cas/login

repo: cameronbwhite/Flask-CAS


text:
kubelet Kubernetes node labels are missing

Hi
I encounter the same issue as described here
https://github.com/prometheus/prometheus/issues/3294
when deploying Prometheus
Earlier (before the Prometheus operator implementation) metrics like
container_memory_working_set_bytes{id='/'}
provided all the node labels

But unfortunately now most of the useful labels are missing.

Hi @paalkr, sorry for the late reply. I did try to fix it but unfortunately wasn't able to do it. Tested also with TargetLables and still not working. I think I'll need more time to understand exactly how this work.
Here is the example I tried:
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: kubelet
  labels:
    k8s-app: kubelet
spec:
  jobLabel: k8s-app
  endpoints:
  - port: http-metrics
    path: /metrics/cadvisor
    interval: 30s
    honorLabels: true
  selector:
    matchLabels:
      k8s-app: kubelet
  targetLabels:
    - app
    - prometheus
    - beta.kubernetes.io/instance-type
    - kops.k8s.io/instancegroup
    - failure-domain.beta.kubernetes.io/zone
    - name
    - address
  namespaceSelector:
    matchNames:
    - kube-system

Hi, thanks  for looking into this, I appreciate your effort and help.

May this be of any help?
https://github.com/coreos/prometheus-operator/blob/master/example/prometheus-operator-crd/servicemonitor.crd.yaml

Hi, id did notice a big commit yesterday. Did you have any success to get the labels applied?

No luck yet

Ah, I see. Thanks for the feedback. anything I can do to help?

Some more interesting information
https://github.com/coreos/prometheus-operator/issues/1166
https://github.com/coreos/prometheus-operator/issues/1548#issuecomment-402045553

I managed to sort out this issue. There are several things worth mentioning.
The Prometheus Operator ServiceMonitor object/kind/crd does not provide access to the kubernetes_sd_config role=node
  kubernetes_sd_configs:
  - api_server: null
    role: node

And therefor non of the __meta_kubernetes_node_* labels are available. This can be worked around using additionalScrapeConfigs in the PrometheusSpec (https://github.com/coreos/prometheus-operator/blob/master/Documentation/api.md#prometheusspec).
Trying to use targetLabels in the service monitor will fail, becasue they will translate into
__meta_kubernetes_service_label_<labelname> as the role of targets created by the automated processes in the operator always are service.
  kubernetes_sd_configs:
  - api_server: null
    role: service

So I ended up removing the kubelet ServiceMonitor (prometheus-k8s-service-monitor-kubelet.yaml), and replacing this with a custom scarping config. To get this to work you have to do several things.

Alter the rbac config to allow node access a the cluster scope

apiVersion: rbac.authorization.k8s.io/v1beta1
kind: Role
metadata:
  name: prometheus-k8s
  namespace: default
rules:
- apiGroups: [""]
  resources:
  - nodes/metrics
  - nodes
  - services
  - endpoints
  - pods
  verbs: ["get", "list", "watch"]
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRole
metadata:
  name: prometheus-k8s
rules:
- apiGroups: [""]
  resources:
  - nodes/metrics
  - nodes
  - endpoints
  - pods
  - services
  verbs: ["get", "list", "watch"]
- nonResourceURLs: ["/metrics"]
  verbs: ["get"]

Create a yaml file with your custom scraping configs
kubelet.yaml

- job_name: 'kubernetes-nodes'
  scheme: https
  metrics_path: /metrics
  tls_config:
    insecure_skip_verify: true
  bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
  kubernetes_sd_configs:
  - role: node
  relabel_configs:
  - action: labelmap
    regex: __meta_kubernetes_node_label_(.+)
  - source_labels: [__meta_kubernetes_node_address_InternalIP]
    target_label: __address__
    regex: (.+)
    replacement: ${1}:10250

- job_name: 'kubernetes-cadvisor'
  scheme: https
  metrics_path: /metrics/cadvisor
  tls_config:
    insecure_skip_verify: true
  bearer_token_file: /var/run/secrets/kubernetes.io/serviceaccount/token
  kubernetes_sd_configs:
  - role: node
  relabel_configs:
  - action: labelmap
    regex: __meta_kubernetes_node_label_(.+)
  - source_labels: [__meta_kubernetes_node_address_InternalIP]
    target_label: __address__
    regex: (.+)
    replacement: ${1}:10250

Create a secret with content from the custom scraping config yaml
kubectl create secret generic additional-scrape-configs --from-file=kubelet.yaml=.\kubelet.yaml

Modify the Prometheus config to include the customs scraping configs

apiVersion: monitoring.coreos.com/v1
kind: Prometheus
metadata:
  labels:
    prometheus: k8s
  name: k8s
  namespace: monitoring
spec:
  alerting:
    alertmanagers:
    - name: alertmanager-main
      namespace: monitoring
      port: web
  externalUrl: xxx
  replicas: 2
  ruleSelector:
    matchLabels:
      prometheus: k8s
      role: prometheus-rulefiles
  serviceAccountName: prometheus-k8s
  additionalScrapeConfigs:
    name: additional-scrape-configs
    key: kubelet.yaml
  serviceMonitorSelector:
    matchExpressions:
    - key: k8s-app
      operator: Exists
  version: v2.2.1

All node labels are then propagated to metrics like container_memory_working_set_bytes, machine_memory_bytes etc.

Hi @paalkr, thanks for this fix. I'll try to integrate it in the next update.

@camilb I'm facing the same issue with the node-exporter.

Do we have any work around for now to get the node name label in the metrics without additionalScrape config ?

with respect to node-exporter o we have any work around for now to get the node name label in the metrics without additionalScrape config ?

bumppppp there has to be a better way to do this

please help me understand that. I am really looking for prometheus operator use name labels on nodes.
PUNEET
On Wednesday, 1 July 2020, 10:57:42 PM IST, Blaumer <notifications@github.com> wrote:

with respect to node-exporter o we have any work around for now to get the node name label in the metrics without additionalScrape config ?
bumppppp there has to be a better way to do this
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

I'll take a look on it later today

thanks a lot.. just let me know when you check.. I will try that immediately.
PUNEET
On Thursday, 2 July 2020, 07:49:56 AM IST, Camil Blanaru <notifications@github.com> wrote:

I'll take a look on it later today
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

Hi guys.
I have faced with the same issue.
Do we have any updates regarding the solution?

I have solved it by used group_left in query.
sum by(label_node_type, node) (kube_node_status_allocatable_cpu_cores * on(node) group_left(label_node_type) kube_node_labels)

Hi guys, probably this is a more cleaner way to do this (on the serviceMonitor object)
prometheus-node-exporter:
  prometheus:
    monitor:
      enabled: true
      relabelings:
        - sourceLabels: [__meta_kubernetes_endpoint_node_name]
          targetLabel: node

These values are for kube-prometheus-stack helm chart. Check service discovery on prometheus for more labels. most of the useful ones are available.

Hi. Thanks a lot for your reply. Will check it.

Hello, I'm trying to add a custom label to the node.
       - job_name: 'kubernetes-nodes'           scheme: https           metrics_path: /metrics           kubernetes_sd_configs:           - role: node           relabel_configs:           - action: labelmap             regex: __meta_kubernetes_node_label_(.+)           - source_labels: [__meta_kubernetes_node_failure_domain_beta_kubernetes_io_zone]                   target_label: __failure_domain_beta_kubernetes_io_zone__             regex: (.+)             replacement:  $1
But it is not working. Please ow can I have this label in my cluster failure-domain.beta.kubernetes.io/zone  The label is at the node level.
I using kube-Prometheus-stack helm chart

authors: Blaumer HariomSaini Ngougniheguens camilb estahn izavadynskyi paalkr puneetmathur-87

repo: camilb/prometheus-kubernetes


text:
react: upgrade to use myitcv.io/react

A placeholder for the the move from the old github.com/myitcv/gopherjs/react to myitcv.io/react

@mpl currently seeing test errors like https://github.com/camlistore/camlistore/issues/680 locally
Am I missing something obvious on how to make the tests with the equivalent of -parallel 1 (which I guess would cause things to run in serial, maybe fixing the issue?)

you mean you're getting the text file busy errors?
I think I've fixed these in https://camlistore-review.googlesource.com/9326
My first patch was pretty much what you guessed, but Brad didn't like it I think. So the subsequent patchsets are a different approach.

you mean you're getting the text file busy errors?

Yes.

I think I've fixed these in https://camlistore-review.googlesource.com/9326

Ok cool.

My first patch was pretty much what you guessed, but Brad didn't like it I think.

I spent literally no time thinking about it so there's almost certainly more complexity that I'm missing :)

https://camlistore-review.googlesource.com/c/camlistore/+/10367

authors: mpl myitcv

repo: camlistore/camlistore


text:
通常の開館日ではないがイベントがある日のサポート

通常の開館日ではないがイベントがある日に, 単純に閉館ツイートを流すのではなく, イベント情報をツイートしたりする機能を追加する.

#7 を先に実装した方が良さそう.

動作例:
$ schedule-notifier -n --now 2017-02-12
#1
「第6回 プログラミング大相談会」を13:00〜17:00に開催します!
みなさんのお越しをお待ちしています!!
https://camphor.connpass.com/event/49917/

ツイート内容が変わるのでレビューをお願いします.

@shiba6v もレビューよろしく

repo: camphor-/schedule-notifier


text:
Allow to manage inet_protocols parameter

It would be nice to be able to manage the inet_protocols parameter.

we do this via postfix::config

@igalic so this can be done without a new feature, correct?

@raphink correct.

I'll consider this a question and close then. Thank you @igalic.

authors: gothicx igalic raphink

repo: camptocamp/puppet-postfix


text:
Updated all dependencies and fixed the Keyberon dep inside Cargo.toml

All dependencies have been updated to their latest versions and the path to Keyberon was fixed inside Cargo.toml so it points to the github repo (which is necessary to build it because the stable release doesn't have chording yet).  In order to do that I had to make a few trivial changes to the code since it didn't quite match how the new chording feature wants you to define things and there were some minor changes to rp2040-boot2 in 0.2.0 which changed how you're supposed to use it (slightly).
I tested that these changes compile and flash to an rp2040 board (an ItsyBitsy which is basically just a smaller version of the main Pico board) but I did not test using it as an actual keyboard.  It should work just fine though 👍

Wow thanks! I should have updated the chording once it got merged into keyberon.
PR looks good and I can update a couple things after it merges. Just curious, what made you submit the PR if you don't have the hardware?

Haha I know you must've been like, "WTF‽ LOL! Who is this guy‽"  Here's how it happened:  I was looking for an example of using an RP2040 to emulate a keyboard in Rust and this project came up.  I cloned it and tried to build it...  It failed (because of the hard-coded local Keyberon path).  So I had a look and quickly realized it only needed trivial changes to fix it so I made them.
Then I was like, "well, I did all this work I might as well put it to good use" and submitted a PR 👍
HO HO HO Merry Christmas! :grin:

Awesome! Thanks!
I've also got these floating out there as rp2040 examples:
https://github.com/camrbuss/lily58-rp2040-keyberon
https://github.com/camrbuss/crkbd-rp2040-keyberon

authors: camrbuss riskable

repo: camrbuss/pinci


text:
Support for initContainers to wait for database startup

On first installing my resources I get sometimes the following exception in my camunda pod:
06-Oct-2021 14:21:56.462 SEVERE [main] org.postgresql.Driver.connect Connection error:
	org.postgresql.util.PSQLException: FATAL: the database system is starting up

or even:
7-Oct-2021 09:58:29.075 SEVERE [main] org.postgresql.Driver.connect Connection error:
	org.postgresql.util.PSQLException: Connection to db-cluster:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
		at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:265)
		at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49)

To avoid this I want to use initcontainers, which wait until the service and database are started.
initContainers:
  - name: check-db-service-available
    image: busybox:1.34.0
    command: ['sh', '-c',
      'until nslookup db-cluster;
      do echo waiting for db-cluster; sleep 2; done;
      echo db service found;']
  - name: check-db-ready
    image: postgres:13.4
    command: ['sh', '-c',
    'until pg_isready -h db-cluster -d processEngine -p 5432;
      do echo waiting for database; sleep 2; done;
      echo database is ready']

Does this make sense for you? I tried it directly with the yaml files without using the helm chart and it worked quite well. But of cause I want rather to use your helm charts.
Perhaps it could be an option to include something like this in the development yaml:
{{- if .Values.initContainers }}
  {{- toYaml .Values.initContainers | nindent 6 }}
{{- end }}

So that I will be able to define my initContainers in the values file

Thanks, works fine.

repo: camunda-community-hub/camunda-helm


text:
Preserve newline character for narratives

Many narratives entered by users are quite long. Unfortunately, paragraphs entered in the input get rendered as a single line in the output, making it more difficult to read. This is to request that newlines entered in the multi-line free-text fields be preserved in the output (results page and PDF).
E.g. of input:

And how it currently gets rendered, with newlines removed.

@MrDeshaies Results page preserve newline and space has been fixed. However the pdf still not show the newline, I will investigate more. The branch is 777-preserve-newline if you want to see it.

@MrDeshaies PDF fixed too.

authors: Ancentury MrDeshaies

repo: canada-ca/aia-eia-js


text:
🛑 kubeflow-news.com is down

In bcc88e4, kubeflow-news.com (https://kubeflow-news.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: kubeflow-news.com is back up in 76641b5.

repo: canonical-web-and-design/upptime


text:
Fix cgroup-limit test on Ubuntu 24.10 Oracular Oriole

I noticed that dotnet8 autopkgtests on Oracular have been failing consistently on all architectures, always on the test cgroup-limit (see example). It was fairly easy to reproduce the behavior on an Oracular VM:
# dotnet /home/ubuntu/dotnet-test-runner/Turkey/bin/Debug/net6.0/Turkey.dll --test-name cgroup-limit
Testing everything under /home/ubuntu/dotnet-regular-tests
Current platform is: linux, linux-x64, ubuntu, ubuntu-x64, ubuntu24.10, ubuntu.24.10, ubuntu.24.10-x64
Tests matching these traits will be skipped: arch=x64, os=linux, os=ubuntu, os=ubuntu.24.10, rid=linux, rid=linux-x64, rid=ubuntu, rid=ubuntu-x64, rid=ubuntu.24.10, rid=ubuntu.24.10-x64, rid=ubuntu24.10, runtime=coreclr, version=8, version=8.0.
Running tests:
cgroup-limit                                                [FAIL]      (2s)

The following tests failed:
cgroup-limit                  (2s)

Total: 1 Passed: 0 Failed: 1

This test executes the script cgroup-limit/test.sh, which launches a systemd.scope unit that executes a .NET program within a memory-limited cgroup. So, running the systemd-run command directly makes the error a little more obvious:
# systemd-run --scope -p CPUQuota=100% -p MemoryLimit=100M bin/Release/net8.0/cgroup-limit
Running as unit: run-r9a06bd833e06411e9f979ab12692be60.scope; invocation ID: 55874dd982974640b0fe1e4dfd43eebb
Killed

Examining the unit status a little more closely, shows that it was killed by the OOM Killer:
# systemctl status run-r9a06bd833e06411e9f979ab12692be60.scope
× run-r9a06bd833e06411e9f979ab12692be60.scope - /home/ubuntu/dotnet-regular-tests/cgroup-limit/bin/Release/net8.0/cgroup-limit
     Loaded: loaded (/run/systemd/transient/run-r9a06bd833e06411e9f979ab12692be60.scope; transient)
  Transient: yes
     Active: failed (Result: oom-kill) since Fri 2024-08-16 10:22:28 -03; 46s ago
   Duration: 31ms
 Invocation: 55874dd982974640b0fe1e4dfd43eebb

Aug 16 10:22:28 oracular systemd[1]: Started run-r9a06bd833e06411e9f979ab12692be60.scope - /home/ubuntu/dotnet-regular-tests/cgroup-limit/bin/Release/net8.0/cgroup-limit.
Aug 16 10:22:28 oracular systemd[1]: run-r9a06bd833e06411e9f979ab12692be60.scope: A process of this unit has been killed by the OOM killer.
Aug 16 10:22:28 oracular systemd[1]: run-r9a06bd833e06411e9f979ab12692be60.scope: Failed with result 'oom-kill'.

Interestingly enough, running the same command on a Noble VM does execute to the end succesfully:
# systemd-run --scope -p CPUQuota=100% -p MemoryLimit=100M bin/Release/net8.0/cgroup-limit
Running as unit: run-rb48982bf5e4f4deebb40efde4e9a4ff0.scope; invocation ID: cda5ac4363e7436f97e266376a3db079
Limits:
1
78643200

It is not 100% clear to me why this is the case, maybe something changed in the OOM Killer in between kernels, but bumping the memory limit property on the systemd-run command should fix the problem for Oracular without negatively impacting the test's accuracy:
# systemd-run --scope -p CPUQuota=100% -p MemoryLimit=200M cgroup-limit/bin/Release/net8.0/cgroup-limit
Running as unit: run-raafabb5488044c1ca1ef20425759bc72.scope; invocation ID: f73de50077d34ad389087d65e6ed0bf0
Limits:
1
157286400

# dotnet /home/ubuntu/dotnet-test-runner/Turkey/bin/Debug/net6.0/Turkey.dll --test-name cgroup-limit
Testing everything under /home/ubuntu/dotnet-regular-tests
Current platform is: linux, linux-x64, ubuntu, ubuntu-x64, ubuntu24.10, ubuntu.24.10, ubuntu.24.10-x64
Tests matching these traits will be skipped: arch=x64, os=linux, os=ubuntu, os=ubuntu.24.10, rid=linux, rid=linux-x64, rid=ubuntu, rid=ubuntu-x64, rid=ubuntu.24.10, rid=ubuntu.24.10-x64, rid=ubuntu24.10, runtime=coreclr, version=8, version=8.0.
Running tests:
cgroup-limit                                                [PASS]      (4s)

The following tests failed:

Total: 1 Passed: 1 Failed: 0

Verification:
PPA upload: https://launchpad.net/~mateus-morais/+archive/ubuntu/dotnet8-cgroup-limit
Autopkgtest Results:

amd64 [PASS ✅]: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-mateus-morais-dotnet8-cgroup-limit/oracular/amd64/d/dotnet8/20240816_175410_bd5a3@/log.gz
arm64 [PASS ✅]: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-mateus-morais-dotnet8-cgroup-limit/oracular/arm64/d/dotnet8/20240816_190722_3fc51@/log.gz
ppc64el [PASS ✅]: https://autopkgtest.ubuntu.com/results/autopkgtest-oracular-mateus-morais-dotnet8-cgroup-limit/oracular/ppc64el/d/dotnet8/20240816_204430_51ec2@/log.gz
s390x [❓]: networking issues in runners are currently preventing test runs, but not expecting issues here.

repo: canonical/dotnet-regular-tests


text:
how to configure istio-core manifests with a namespace defined at runtime

To enabling deploying istio to the kubernetes namespace that corresponds to its Juju model, we need to render manifests at runtime that refer to the desired namespace.  The manifests for istio's control plane reference the control plane namespace about 45 times (example manifest - search istio-systemmm:

~3/4 are the namespace field in other objects (eg: the namespace a ServiceAccount or Deployment is put into)
~6 are the roleRef and subjects of 3 ClusterRoleBindings
~3 are settings in Validating and Mutating webhook configurations
~5 spread inside the data of a few ConfigMaps
2 are in a Deployments configuration

Our plan is to mostly render these manifests at compile time, then modify those during runtime.  How should we tackle this modification part of the work?  I don't think we want to do this by hand for every istio version, so maybe we need some scripting to search for these?
One spot that worries me is if a new istio release adds a new setting that uses namespace - how do we confidently find this new setting?  With ~45 usages of namespace in the manifests, I don't think we can rely on a human noticing when they change.  Sounds like we'd need something robust and automated there as well

Another fun complication I've hit today - some of the configmaps istio creates include jinja (or very jinja-like) templates.  I haven't tried much debugging, but on the first pass if I tried to render the manifests istioctl generated through jinja, jinja raised errors.  Might be a way I can suppress these though

Closed by #4 because we used istioctl to do this dynamically

repo: canonical/istio-core-operator


text:
use chisme pebble update_layer

Update dashboard-operator to use the update_layer function in chisme, updated tests to match
CI would fail until this pr is merged and published. Tested locally with git+https://github.com/canonical/charmed-kubeflow-chisme@KF-605/update-layer-handler in requirements.txt

Thanks @agathanatasha, this charm has been refactored and the changes do not apply anymore. Closing the PR.

authors: DnPlas agathanatasha

repo: canonical/kubeflow-dashboard-operator


text:
microk8s doesn't seem to work on raspberry pi 3 or 4 devices

Hey there,
I've spent the day trying to get microk8s running on a variety of Raspberry Pi following the tutorial here, with a variety of different and interesting failures. I apologise if some of these are duplicated, I am in no way familiar with k8s and flailing wildly.
Running raspbian aarch64 from here. Tested with microk8s stable and edge, both showing the same symptoms / collection of issues. uname -a shows:
Linux pi-k8s-01 5.10.17-v8+ #1414 SMP PREEMPT Fri Apr 30 13:23:25 BST 2021 aarch64 GNU/Linux

inspection-report-20210721_030553.tar.gz
Firstly, installing microk8s appears to work, and after a reboot microk8s status shows things are okay. Commands vary between completing instantly and taking tens of seconds, which may be related to #2280 though moving journald to volatile storage has not made a notable difference (it seems maybe related to the container restarting later).
pi@pi-k8s-01:~ $ microk8s status
microk8s is running
high-availability: no
  datastore master nodes: 127.0.0.1:19001
  datastore standby nodes: none
addons:
  enabled:
    ha-cluster           # Configure high availability on the current node
  disabled:
    dashboard            # The Kubernetes dashboard
    dns                  # CoreDNS
    helm                 # Helm 2 - the package manager for Kubernetes
    helm3                # Helm 3 - Kubernetes package manager
    host-access          # Allow Pods connecting to Host services smoothly
    ingress              # Ingress controller for external access
    linkerd              # Linkerd is a service mesh for Kubernetes and other frameworks
    metallb              # Loadbalancer for your Kubernetes cluster
    metrics-server       # K8s Metrics Server for API access to service metrics
    openebs              # OpenEBS is the open-source storage solution for Kubernetes
    portainer            # Portainer UI for your Kubernetes cluster
    prometheus           # Prometheus operator for monitoring and logging
    rbac                 # Role-Based Access Control for authorisation
    registry             # Private image registry exposed on localhost:32000
    storage              # Storage class; allocates storage from host directory
    traefik              # traefik Ingress controller for external access

Checking what's running under k8s it looks like a lot of tasks are not ready, maybe related to #2367:
pi@pi-k8s-01:~ $ microk8s kubectl get all --all-namespaces
NAMESPACE     NAME                                          READY   STATUS    RESTARTS   AGE
kube-system   pod/calico-kube-controllers-f7868dd95-bf2st   0/1     Pending   0          101m
kube-system   pod/calico-node-nzjzw                         1/1     Running   39         101m

NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
default       service/kubernetes                  ClusterIP   10.152.183.1     <none>        443/TCP    101m
kube-system   service/metrics-server              ClusterIP   10.152.183.23    <none>        443/TCP    96m
kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.185   <none>        443/TCP    35m
kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.179   <none>        8000/TCP   35m

NAMESPACE     NAME                         DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR            AGE
kube-system   daemonset.apps/calico-node   1         1         0       1            0           kubernetes.io/os=linux   101m

NAMESPACE     NAME                                        READY   UP-TO-DATE   AVAILABLE   AGE
kube-system   deployment.apps/calico-kube-controllers     0/1     1            0           101m
kube-system   deployment.apps/metrics-server              0/1     0            0           96m
kube-system   deployment.apps/kubernetes-dashboard        0/1     0            0           35m
kube-system   deployment.apps/dashboard-metrics-scraper   0/1     0            0           35m

NAMESPACE     NAME                                                DESIRED   CURRENT   READY   AGE
kube-system   replicaset.apps/calico-kube-controllers-f7868dd95   1         1         0       101m

Running commands has a 50/50 chance of failure, presumably related to #1916 (and maybe #2280), though this node is not joined to a cluster nor does anything appear to be getting OOM killed. This usually returns one of a few errors:
The connection to the server 127.0.0.1:16443 was refused - did you specify the right host or port?

Attempting to install the dashoard with microk8s enable dashboard sometimes seems to work, and in other cases appears to kill the snap.microk8s.daemon-kubelite, seemingly requiring a restart to recover. When it does claim to succeed the containers never seem to run (as you can see above), nor does microk8s status report that the dashboard is enabled.
Attempting to forward a port to the dashboard machine (via microk8s kubectl port-forward -n kube-system service/kubernetes-dashboard 10443:443) first results in:
error: watch closed before UntilWithoutRetry timeout

which is probably to be expected if the container isn't up. Then if retried:
The connection to the server 127.0.0.1:16443 was refused - did you specify the right host or port?

which appears to also crash something that takes a while to recover.
A few errors do end up in the logs, but I haven't had much luck resolving them. A sampling of unique entries via  sudo journalctl -u snap.microk8s.daemon-* --all | grep error | tail -500:
Jul 21 03:23:33 pi-k8s-01 microk8s.daemon-containerd[29649]: time="2021-07-21T03:23:33.486142810+01:00" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.aufs\"..." error="aufs is not supported (modprobe aufs failed: exit status 1 \"modprobe: FATAL: Module aufs not found in directory /lib/modules/5.10.17-v8+\\n\"): skip plugin" type=io.containerd.snapshotter.v1
Jul 21 03:23:33 pi-k8s-01 microk8s.daemon-containerd[29649]: time="2021-07-21T03:23:33.486893901+01:00" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.btrfs\"..." error="path /var/snap/microk8s/common/var/lib/containerd/io.containerd.snapshotter.v1.btrfs (ext4) must be a btrfs filesystem to be used with the btrfs snapshotter: skip plugin" type=io.containerd.snapshotter.v1
Jul 21 03:23:33 pi-k8s-01 microk8s.daemon-containerd[29649]: time="2021-07-21T03:23:33.487056063+01:00" level=warning msg="failed to load plugin io.containerd.snapshotter.v1.devmapper" error="devmapper not configured"
Jul 21 03:23:33 pi-k8s-01 microk8s.daemon-containerd[29649]: time="2021-07-21T03:23:33.488229827+01:00" level=info msg="skip loading plugin \"io.containerd.snapshotter.v1.zfs\"..." error="path /var/snap/microk8s/common/var/lib/containerd/io.containerd.snapshotter.v1.zfs must be a zfs filesystem to be used with the zfs snapshotter: skip plugin" type=io.containerd.snapshotter.v1
Jul 21 03:24:25 pi-k8s-01 microk8s.daemon-containerd[29921]: time="2021-07-21T03:24:25.694509662+01:00" level=error msg="failed to delete" cmd="/snap/microk8s/2343/bin/containerd-shim-runc-v1 -namespace k8s.io -address /var/snap/microk8s/common/run/containerd.sock -publish-binary /snap/microk8s/2343/bin/containerd -id e9fed7097d0b2493e8483a08e43e42d19145bd881e064b181ec11d8a7831e7d3 -bundle /var/snap/microk8s/common/run/containerd/io.containerd.runtime.v2.task/k8s.io/e9fed7097d0b2493e8483a08e43e42d19145bd881e064b181ec11d8a7831e7d3 delete" error="exit status 1"
...
Jul 21 03:24:15 pi-k8s-01 microk8s.daemon-kubelite[29977]: E0721 03:24:15.068578   29977 controller.go:116] loading OpenAPI spec for "v1beta1.metrics.k8s.io" failed with: failed to retrieve openAPI spec, http error: ResponseCode: 503, Body: service unavailable
Jul 21 03:24:25 pi-k8s-01 microk8s.daemon-containerd[29921]: time="2021-07-21T03:24:25.694509662+01:00" level=error msg="failed to delete" cmd="/snap/microk8s/2343/bin/containerd-shim-runc-v1 -namespace k8s.io -address /var/snap/microk8s/common/run/containerd.sock -publish-binary /snap/microk8s/2343/bin/containerd -id e9fed7097d0b2493e8483a08e43e42d19145bd881e064b181ec11d8a7831e7d3 -bundle /var/snap/microk8s/common/run/containerd/io.containerd.runtime.v2.task/k8s.io/e9fed7097d0b2493e8483a08e43e42d19145bd881e064b181ec11d8a7831e7d3 delete" error="exit status 1"
Jul 21 03:24:25 pi-k8s-01 microk8s.daemon-containerd[29921]: time="2021-07-21T03:24:25.695113389+01:00" level=warning msg="failed to clean up after shim disconnected" error="io.containerd.runc.v1: remove /run/containerd/s/bf95c1279ce968440d9923564b9437c60297e8f859ed59ea05f45fe7462c2cc7: no such file or directory\n: exit status 1" id=e9fed7097d0b2493e8483a08e43e42d19145bd881e064b181ec11d8a7831e7d3 namespace=k8s.io
Jul 21 03:24:28 pi-k8s-01 microk8s.daemon-containerd[29921]: time="2021-07-21T03:24:28.685861940+01:00" level=error msg="failed to reload cni configuration after receiving fs change event(\"/var/snap/microk8s/2343/args/cni-network/10-calico.conflist\": REMOVE)" error="cni config load failed: no network config found in /var/snap/microk8s/2343/args/cni-network: cni plugin not initialized: failed to load cni config"
Jul 21 03:24:33 pi-k8s-01 microk8s.daemon-containerd[29921]: time="2021-07-21T03:24:33.723080957+01:00" level=error msg="collecting metrics for 053fcd20e91ca8cc84f8b3dbfe64cb59d09b77d13efbd16efe35c277156d3399" error="cgroups: cgroup deleted: unknown"
...
Jul 21 03:32:18 pi-k8s-01 microk8s.daemon-kubelite[7740]: E0721 03:32:18.774730    7740 status.go:71] apiserver received an error that is not an metav1.Status: &url.Error{Op:"Get", URL:"https://pi-k8s-01:10250/containerLogs/kube-system/calico-node-nzjzw/upgrade-ipam", Err:(*net.OpError)(0x40013f3db0)}: Get "https://pi-k8s-01:10250/containerLogs/kube-system/calico-node-nzjzw/upgrade-ipam": dial tcp 127.0.0.1:10250: connect: connection refused

Most of these errors are repeated constantly, the "exit status 1" seems to suggest containerd is restarting but, there doesn't seem to be any super obvious indication of a fresh start in the logs.
I hope some part of this is useful, I'd hoped for it to be a quick morning setup but seem to have bitten off more than I can chew ^_^

Hi @ryankurte,
I see that the CNI (calico-node) is not healthy, it has restarted 39 times in 101 minutes. As the CNI is not healthy there is no networking for the Kubernetes pods so it is expected for the rest of the services to not work.
This machine has 2GB of RAM and you have added 100MB of swap. With this amount of swap is as if there is none.
Here is a suggestion: microk8s disable ha-cluster , this will switch you to a setup with etcd instead of dqlite and flannel instead of calico.

thanks for the response! after running docker it didn't even occur to me that the runtime would need > 2GB of ram, is this too low to be worthwhile? (i actually didn't intend the swap to be there at all, the rpi seems to have automatically done it on file system expand, i may have missed recommendations about this?).
after disabling ha-cluster it's idling around ~500MB memory used (on a base of ~200MB without it running) which seems like it should be workable, and after microk8s enable dashboard it goes up to 600MB...
microk8s status however still reports:
microk8s is not running. Use microk8s inspect for a deeper inspection.

and the services don't seem to be running (or, ready, anyway).
$ microk8s kubectl get all --all-namespaces
NAMESPACE     NAME                                  READY   STATUS    RESTARTS   AGE
kube-system   pod/metrics-server-698f47cc84-nzwks   0/1     Running   6          13m

NAMESPACE     NAME                                TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)    AGE
default       service/kubernetes                  ClusterIP   10.152.183.1     <none>        443/TCP    16m
kube-system   service/dashboard-metrics-scraper   ClusterIP   10.152.183.20    <none>        8000/TCP   13m
kube-system   service/kubernetes-dashboard        ClusterIP   10.152.183.200   <none>        443/TCP    13m
kube-system   service/metrics-server              ClusterIP   10.152.183.169   <none>        443/TCP    13m

while microk8s inspect seems to suggest everything is okay:
Inspecting Certificates
Inspecting services
  Service snap.microk8s.daemon-cluster-agent is running
  Service snap.microk8s.daemon-containerd is running
  Service snap.microk8s.daemon-apiserver-kicker is running
  Service snap.microk8s.daemon-kubelite is running
  Service snap.microk8s.daemon-flanneld is running
  Service snap.microk8s.daemon-etcd is running
  Copy service arguments to the final report tarball
Inspecting AppArmor configuration
Gathering system information
  Copy processes list to the final report tarball
  Copy snap list to the final report tarball
  Copy VM name (or none) to the final report tarball
  Copy disk usage information to the final report tarball
  Copy memory usage information to the final report tarball
  Copy server uptime to the final report tarball
  Copy current linux distribution to the final report tarball
  Copy openSSL information to the final report tarball
  Copy network configuration to the final report tarball
Inspecting kubernetes cluster
  Inspect kubernetes cluster
Inspecting juju
  Inspect Juju
Inspecting kubeflow
  Inspect Kubeflow

inspection-report-20210722_021452.tar.gz
ram use is bouncing around a lot so i guess something is still failing / restarting, and it sorta looks like systemd is stopping and starting microk8s.daemon-containerd every few seconds or so:
Jul 22 02:22:09 pi-k8s-01 systemd[1]: Started Service for snap application microk8s.daemon-containerd.
Jul 22 02:22:09 pi-k8s-01 microk8s.daemon-containerd[30603]: time="2021-07-22T02:22:09.748621182+01:00" level=info msg="Start event monitor"
Jul 22 02:22:09 pi-k8s-01 microk8s.daemon-containerd[30603]: time="2021-07-22T02:22:09.748726828+01:00" level=info msg="Start snapshots syncer"
Jul 22 02:22:09 pi-k8s-01 microk8s.daemon-containerd[30603]: time="2021-07-22T02:22:09.748766124+01:00" level=info msg="Start cni network conf syncer"
Jul 22 02:22:09 pi-k8s-01 microk8s.daemon-containerd[30603]: time="2021-07-22T02:22:09.748795271+01:00" level=info msg="Start streaming server"
Jul 22 02:22:25 pi-k8s-01 microk8s.daemon-containerd[30603]: time="2021-07-22T02:22:25.330933873+01:00" level=info msg="Stop CRI service"
Jul 22 02:22:25 pi-k8s-01 systemd[1]: Stopping Service for snap application microk8s.daemon-containerd...
Jul 22 02:22:25 pi-k8s-01 microk8s.daemon-containerd[30603]: time="2021-07-22T02:22:25.345294578+01:00" level=info msg="Stop CRI service"
Jul 22 02:22:25 pi-k8s-01 microk8s.daemon-containerd[30603]: time="2021-07-22T02:22:25.345431743+01:00" level=info msg="Event monitor stopped"
Jul 22 02:22:25 pi-k8s-01 microk8s.daemon-containerd[30603]: time="2021-07-22T02:22:25.345469353+01:00" level=info msg="Stream server stopped"
Jul 22 02:22:25 pi-k8s-01 systemd[1]: snap.microk8s.daemon-containerd.service: Succeeded.
Jul 22 02:22:25 pi-k8s-01 systemd[1]: Stopped Service for snap application microk8s.daemon-containerd.
Jul 22 02:22:25 pi-k8s-01 systemd[1]: Starting Service for snap application microk8s.daemon-containerd...

dmesg also shows the virtual network adaptor bouncing around but, not much else:
[84269.623924] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[84269.625245] cni0: port 1(vetha72a21b7) entered blocking state
[84269.625268] cni0: port 1(vetha72a21b7) entered disabled state
[84269.625561] device vetha72a21b7 entered promiscuous mode
[84269.625662] cni0: port 1(vetha72a21b7) entered blocking state
[84269.625668] cni0: port 1(vetha72a21b7) entered forwarding state
[84320.885230] cni0: port 1(vetha72a21b7) entered disabled state

systemd reports that etcd is up, flanneld is failing with:
failed to ensure address of interface flannel.1: link has incompatible addresses. Remove additional addresses and try again

so i'm just looking into that now, fingers crossed ^_^
expanded log (via sudo journalctl -u snap.microk8s.daemon-flanneld.service --all -n 500):

Here
Jul 22 02:31:33 pi-k8s-01 microk8s.daemon-flanneld[14053]: I0722 02:31:33.516644   14053 main.go:514] Determining IP address of default interface
Jul 22 02:31:33 pi-k8s-01 microk8s.daemon-flanneld[14053]: I0722 02:31:33.517697   14053 main.go:527] Using interface with name eth0 and address 192.168.1.54
Jul 22 02:31:33 pi-k8s-01 microk8s.daemon-flanneld[14053]: I0722 02:31:33.517760   14053 main.go:544] Defaulting external address to interface address (192.168.1.54)
Jul 22 02:31:33 pi-k8s-01 flanneld[14053]: warning: ignoring ServerName for user-provided CA for backwards compatibility is deprecated
Jul 22 02:31:33 pi-k8s-01 microk8s.daemon-flanneld[14053]: I0722 02:31:33.519699   14053 main.go:244] Created subnet manager: Etcd Local Manager with Previous Subnet: 10.1.43.0/24
Jul 22 02:31:33 pi-k8s-01 microk8s.daemon-flanneld[14053]: I0722 02:31:33.519734   14053 main.go:247] Installing signal handlers
Jul 22 02:31:33 pi-k8s-01 microk8s.daemon-flanneld[14053]: I0722 02:31:33.599360   14053 main.go:386] Found network config - Backend type: vxlan
Jul 22 02:31:33 pi-k8s-01 microk8s.daemon-flanneld[14053]: I0722 02:31:33.599538   14053 vxlan.go:120] VXLAN config: VNI=1 Port=0 GBP=false DirectRouting=false
Jul 22 02:31:33 pi-k8s-01 microk8s.daemon-flanneld[14053]: I0722 02:31:33.607213   14053 local_manager.go:147] Found lease (10.1.43.0/24) for current IP (192.168.1.54), reusing
Jul 22 02:31:33 pi-k8s-01 microk8s.daemon-flanneld[14053]: E0722 02:31:33.614657   14053 main.go:289] Error registering network: failed to configure interface flannel.1: failed to ensure addr
Jul 22 02:31:33 pi-k8s-01 microk8s.daemon-flanneld[14053]: I0722 02:31:33.615088   14053 main.go:366] Stopping shutdownHandler...
Jul 22 02:31:33 pi-k8s-01 systemd[1]: snap.microk8s.daemon-flanneld.service: Main process exited, code=exited, status=1/FAILURE
Jul 22 02:31:33 pi-k8s-01 systemd[1]: snap.microk8s.daemon-flanneld.service: Failed with result 'exit-code'.

I've been happily running K8s on a cluster of RPi 2s and 3s for years. But as of (roughly) 1.17 it seems that Kubernetes just can't run on these machines anymore. I have similar results with microk8s and k3s. 1.17 kind of runs, but the master just dies after a while, once you've deployed one or more actual apps (like cert-manager and ArgoCD). With 1.21 I can't even get to k get nodes, it never really start up fully, with either k3s or microk8s.
Guess I'm going to have to find something else to do with my RPis, I don't want to upgrade to RPi 4s as they run too hot, I have the cluster in my office and I don't want a rack of fans running next to me all day.

@teq0 i've subsequently got k3s via k3sup running on a cluster of Pi 3s without any issue (though the leader is a Pi 4) on raspbian aarch64, not heavily loaded but it seems to be running alright.

I was about to try that option myself. Given that microk8s is multi-master (if I'm reading the docs correctly) I don't think it will work with a mix of 3s and 4s, but single-master k3s should probably work.

Having similar issues as well. I'll switch to k3s to see if that works better.

@copiltembel @teq0 if you do not want to have HA (multi-master) you can microk8s disable ha-cluster on your nodes before joining them. In this setup only the first node will run the control plane.

@ktsakalozos I've disabled ha-cluster and will give it another go.
I have a mixed setup with two nodes running on rpi4 (arm64) and a single amd64 machine. From what I read HA was enabled as soon as there were 3 nodes in the cluster. But my amd64 was mostly off, maybe that caused microk8s to fail.

@ktsakalozos Unfortunately I ran into a different problem, even without HA: https://github.com/ubuntu/microk8s/issues/1598
I have 2 nodes now (both rpi4 8gb), one of them seems to work fine for now, the other is experiencing the issues described in https://github.com/ubuntu/microk8s/issues/1598 :(

I have spent 2 days to figure out why my Raspberry Pi 4 - 4Gb memory is refusing connection. I have put exactly same commands on x64 and aarch64. Tried almost everything what i could found on the internet. After executing microk8s disable ha-cluster i was able to run microk8s.status <= and it informed me that it is lunched and after "microk8s.kubectl get cs" I have got healthy status of components. It is strange that i had no such problems on x64 :octocat:

So next day i had to reinstall again, because it started again showing "connection refuse" - so problem still exists

authors: bohatermateusz copiltembel ktsakalozos ryankurte teq0


text:
Adds code to configure MySQL instances and create cluster

WIP

@DnPlas @shayancanonical, should we close this PR then?

Since there are significant differences between @paulomach's implementation and this PR, I am going to close this PR. Thanks @DnPlas - we really benefited from using this PR as a reference

authors: DnPlas shayancanonical simskij