Progressive auto-complete

(Copying from https://github.com/adieyal/sd-dynamic-prompting/issues/20#issue-1424307123)
When writing a prompt, I can use the tab key to autocomplete wildcards. This is very useful, except it will auto-complete whichever one is the top one, rather than filling in only what is "common" to the current possibilities. This means I have to type out a considerable amount before I can auto-complete usefully.
For example, if the three files are "foofoo", "foobar" and "foobaz". I would expect the following:

f<TAB> becomes "foo"
foob<TAB> becomes "fooba"

Currently, f<TAB> would just autocomplete whichever happens to be first in the list of possibilities.
Additionally, this happens when auto-completing tags, not just wildcards, I just hadn't used tag autocomplete enough to notice it.

The issue is that this script currently doesn't do any sorting, it just filters by your typed string. This is not a big problem for tags, since those are ordered by count in the CSV. So generally more used tags will be higher in the list, which is similar enough to what the booru sites themselves do.
But I totally understand that it can be a problem for wildcards or other unordered tag lists. I tried a solution based on edit distance in the past, but that wasn't working well at least on its own.
The progressive completion is an interesting idea, however it might be more tricky with general tags. For example, if you type "hair" it will both filter "long_hair" and other hair lengths, but also "hair_bun" or even "chair" somewhere further down the list. We know the common part is what was typed, but we don't know in which direction the user wants to complete (or even both at once if the word is in the middle of the tag).
If we always assume forward completion, that makes it pretty useless for many common tags or wildcards where the common part is at the end and your want suggestions for the beginning.
So it would definitely have to be some kind of hybrid solution. Currently my only idea in that regard is putting perfect matches at the top. But that wouldn't help in your foo example. Edit distance and its related algorithms would work better in that case, but be worse generally since for example typing just "f" would prefer other single letter tags over words that start with f. And even if we first filter and then sort based on edit distance so we only choose from words containing an f, it often preferred very niche tags over common ones just because they're one letter shorter, so it was slower for common tags.
So I'm kind of stuck regarding this problem, other than implementing one of those and leaving it off by default. But I'm open to suggestions if you have an idea.

With the current completion system and code, I don't see this happening, but since the completion behavior has also improved a bit since then I also think it's not needed anymore.

@DominikDoom What improvements are you referring to that help with this?
Solution wise, the wildcard system from dynamic prompts uses this type of structure for nested folders: /character/body/hair.txt. Currently, typing "ch" and then pressing tab would autocomplete /character/body/hair.txt in it's entirety assuming it's the at the top of the autocomplete results
Instead though, could tab completition be made to only complete one level of wildcard path at a time? So typing "ch" and then tabbing would autocomplete the first result of "/character/" assuming it's at the top alphabetically. Then "b" and tab would append "body" so you end up with "/character/body/" and so on and so forth.
If nothing else, do you have advice for which file to edit for color coding different levels of nested wildcard folders for easier skimming? I don't know much coding, but I could probably make that adjustment for myself using chatGPT and share it on here if I'm successful.

@PaperOrb The improvements I was referring to were mainly related to the normal tags.
Since quite a while it filters based on word beginnings by default, so if you type "hair" you will not get "chair" anymore but preferably tags that actually start with hair in one of its parts. If you would also want chair, you'd have to instead use "*hair".
So it is much rarer now for it to misunderstand what tag family you mean.
As for the rest of your suggestions, that would require a custom solution for wildcards.
Both can be done, but it is not trivial since the code only ever assumes the tag to be one whole piece when it comes to insertion and coloring. So I would rather try to implement it myself. I'll move the issue to #190, please do any further discussion there as this issue is really old and largely unrelated to how the new feature would work.


Can't install Hyper .deb on Ubuntu 20.04

[x] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

Ubuntu 20.04 Beta:
Current .deb 3.0.2:

Issue

When I download the available .deb from the website it won't install in Ubuntu's Software application as in the past. An error occurs saying "Failed to Install: not supported".
I haven't done much investigating other than knowing GitHub's Atom editor also seems to be experiencing the same issue here

Nevermind, this is Ubuntu related. See Here

you can try the appImage or snap also from https://github.com/zeit/hyper/actions/runs/71249146


ANNOUNCE: Asyncio is now supported natively in the 'Elasticsearch' package

Starting in version 7.8.0 of the elasticsearch package Asyncio is now supported natively with async/await on Python 3.6+.
Due to this, this library is now deprecated and will not be adding new features or receiving updates beyond impactful bug fixes for Elasticsearch 6.x.
You can install async support via:
$ python -m pip install elasticsearch[async]

NOTE: If you're still targetting Elasticsearch 6.x you should continue to use this library until you've upgraded to Elasticsearch 7.x or later

GitHub Project: https://github.com/elastic/elasticsearch-py
Documentation: https://elasticsearch-py.readthedocs.io
Issue Tracker: https://github.com/elastic/elasticsearch-py/issues

Hi, I've tried to run the simple async bulk request example and got the following error message:
File "sample_async.py", line 28, in <module>     loop.run_until_complete(main())   File "/usr/local/Cellar/python/3.7.3/Frameworks/Python.framework/Versions/3.7/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete     return future.result()   File "sample_async.py", line 25, in main     await async_bulk(es, gendata())   File "/usr/local/lib/python3.7/site-packages/elasticsearch/_async/helpers.py", line 241, in async_bulk     async for ok, item in async_streaming_bulk(client, actions, *args, **kwargs):   File "/usr/local/lib/python3.7/site-packages/elasticsearch/_async/helpers.py", line 171, in async_streaming_bulk     **kwargs   File "/usr/local/lib/python3.7/site-packages/elasticsearch/_async/helpers.py", line 92, in azip     yield tuple([await x.__anext__() for x in aiters])   File "/usr/local/lib/python3.7/site-packages/elasticsearch/_async/helpers.py", line 92, in <listcomp>     yield tuple([await x.__anext__() for x in aiters])   File "/usr/local/lib/python3.7/site-packages/elasticsearch/_async/helpers.py", line 55, in _process_bulk_chunk     resp = await client.bulk("\n".join(bulk_actions) + "\n", *args, **kwargs)   File "/usr/local/lib/python3.7/site-packages/elasticsearch/_async/client/__init__.py", line 435, in bulk     body=body,   File "/usr/local/lib/python3.7/site-packages/elasticsearch/_async/transport.py", line 286, in perform_request     timeout=timeout, TypeError: object tuple can't be used in 'await' expression
using the following code snipped:
`import asyncio
from aws_requests_auth.boto_utils import BotoAWSRequestsAuth
from elasticsearch import AsyncElasticsearch, RequestsHttpConnection
from elasticsearch.helpers import async_bulk
es_host = 'exampleurldoesnotexist.eu-west-1.es.amazonaws.com'
auth = BotoAWSRequestsAuth(aws_host=es_host,
aws_region='eu-west-1',
aws_service='es')
es = AsyncElasticsearch(host=es_host,
port=80,
connection_class=RequestsHttpConnection,
http_auth=auth,
timeout=60)
async def gendata():
mywords = ['foo', 'bar', 'baz']
for word in mywords:
yield {
"_index": "mywords",
"doc": {"word": word},
}
async def main():
await async_bulk(es, gendata())
loop = asyncio.get_event_loop()
loop.run_until_complete(main())
`

@aockel This isn't the appropriate place to raise this issue, I'm going to migrate it to the main repository and tag you.


Cargo.lock: update dependencies

Updates all dependencies except for backtrace, which appears to be exhibiting segmentation faults / NPE on macOS:
https://github.com/rust-lang/backtrace-rs/issues/310

Codecov Report

Merging #25 into develop will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #25   +/-   ##
========================================
  Coverage    54.30%   54.30%
========================================
  Files          140      140
  Lines         3957     3957
========================================
  Hits          2149     2149
  Misses        1808     1808

Continue to review full report at Codecov.

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


Danger failing test - Do NOT ACCEPT

          1 Error

:no_entry_sign:
Please include a CHANGELOG entry.
You can find it at CHANGELOG.md.

          1 Message

:book:
Thanks! :tada:

  Generated by :no_entry_sign: Danger

You can close this; just wanted to show you what it looked like when one of the Danger rules failed. BlueprintBot will comment with what the issue is.


Fixed gimbal target location

The Gimbal class is not targeting absolute gps coordinates. This fixes the issue.

I submitted a PR for this in November, which fixes this among other bugs with the gimbal class, but the package maintainers don't seem to be working on dronekit anymore

this project is basically abandoned at this point. this is unfortunate.


Question about ai2thor version for offline data

Hi,
I just found the script in the #3, but it seems that would be asserted at line 384 in offline_controller_with_small_rotation.py.
Meanwhile, I could not understand the visible_object_map.json, some node in that file seems to be further than 1 meter from the target.
Thanks

Sorry, I do not understand the first part of your question, do you mind explaining in more detail?
The visible_object_map.json contains a dictionary of items and lists of locations where those items are visible according to ai2thor.
We create it with this script:
for scene in scenes:
    try:
        with open('{}/{}/metadata.json'.format(data_dir, scene), 'r') as f:
            metadata_list = json.load(f)

        visible_map = {}
        for k in metadata_list:
            metadata = metadata_list[k]
            for obj in metadata['objects']:
                if obj['visible']:
                    objId = obj['objectId']
                    if objId not in visible_map:
                        visible_map[objId] = []
                    visible_map[objId].append(k)

        with open('{}/{}/visible_object_map.json'.format(data_dir, scene), 'w') as f:
            json.dump(visible_map, f)
    except Exception as e:
        print(scene, e)

Thanks for your reply!
It is my problem for the misunderstanding questions, sorry for that.

When I run the script from #3 :

def search_and_save(in_queue):
    while not in_queue.empty():
        try:
            scene_name = in_queue.get(timeout=3)
        except:
            return
        c = None
        try:
            out_dir = os.path.join(<path-to-where-you-want-data-to-go>, scene_name)
            if not os.path.exists(out_dir):
                os.mkdir(out_dir)

            print('starting:', scene_name)
            c = ExhaustiveBFSController(
                grid_size=0.25,
                fov=90.0,
                grid_file=os.path.join(out_dir, 'grid.json'),
                graph_file=os.path.join(out_dir, 'graph.json'),
                metadata_file=os.path.join(out_dir, 'metadata.json'),
                images_file=os.path.join(out_dir, 'images.hdf5'),
                depth_file=os.path.join(out_dir, 'depth.hdf5'),
                grid_assumption=False)
            c.start()
            c.search_all_closed(scene_name)
            c.stop()
        except AssertionError as e:
            print('Error is', e)
            print('Error in scene {}'.format(scene_name))
            if c is not None:
                c.stop()
            continue

It always be asserted at line 384 in offline_controller_with_small_rotation.py
assert next_state == next_state_guess
It seems that the agent is tricked in front of the fridge, cause the assertion error.

I thought the visible attribute of the object might be 1.5 meters according to the https://ai2thor.allenai.org/documentation/concepts. In this case, should we modify the environment variable to the same as the paper?

Thanks

Unfortunately the documentation and error are for the new AI2-THOR and I am not sure what the bug is -- are you able to use the scraped data? We tried to scrape it so that this would be easier, as we also had issues when initially scraping. Also feel free to raise an issue on the AI2-THOR repo if you are noticing strange behavior (e.g. the agent thinks it is moving forward but the fridge or something like it is confusing the agent).
One fix that you can try is calling GetReachablePositions() and make sure the agent is always in one of those positions.

Thanks for that, I have fixed this problem with your suggestions!

Hello, when I call your search_and_save function, what is the cause of the following error? After the error occurs, the process becomes a zombie process, and the program cannot continue.
Traceback (most recent call last):
File "/home/ubuntu/miniconda3/envs/VT_Depth/lib/python3.6/multiprocessing/process.py", line 258, in _bootstrap
self.run()
File "/home/ubuntu/miniconda3/envs/VT_Depth/lib/python3.6/multiprocessing/process.py", line 93, in run
self._target(*self._args, **self._kwargs)
File "gen_ground_truth.py", line 39, in search_and_save
c.start()
File "/home/ubuntu/miniconda3/envs/VT_Depth/lib/python3.6/site-packages/ai2thor/controller.py", line 804, in start
self.download_binary()
File "/home/ubuntu/miniconda3/envs/VT_Depth/lib/python3.6/site-packages/ai2thor/controller.py", line 742, in download_binary
os.rename(extract_dir, os.path.join(self.releases_dir(), self.build_name()))
OSError: [Errno 39] Directory not empty: '/home/ubuntu/.ai2thor/tmp/thor-201903131714-Linux64' -> '/home/ubuntu/.ai2thor/releases/thor-201903131714-Linux64'


Remote debugger stops working after importing a library

Description
After importing a js library (https://github.com/orhan/react-native-openpgp) if you turn on the remote debugger, the app keeps crashing.
04-05 11:01:41.784  2775  2868 E AndroidRuntime: FATAL EXCEPTION: OkHttp Dispatcher 04-05 11:01:41.784  2775  2868 E AndroidRuntime: Process: com.lemonmobileapp, PID: 2775 04-05 11:01:41.784  2775  2868 E AndroidRuntime: java.lang.IllegalStateException: Expected a name but was NUMBER 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at android.util.JsonReader.nextName(JsonReader.java:390) 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at com.facebook.react.devsupport.JSDebuggerWebSocketClient.onMessage(JSDebuggerWebSocketClient.java:196) 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at okhttp3.internal.ws.RealWebSocket$1.onMessage(RealWebSocket.java:62) 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:242) 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:108) 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at okhttp3.internal.ws.RealWebSocket.readMessage(RealWebSocket.java:97) 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at okhttp3.ws.WebSocketCall.createWebSocket(WebSocketCall.java:152) 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at okhttp3.ws.WebSocketCall.access$000(WebSocketCall.java:41) 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at okhttp3.ws.WebSocketCall$1.onResponse(WebSocketCall.java:97) 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at okhttp3.RealCall$AsyncCall.execute(RealCall.java:126) 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32) 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) 04-05 11:01:41.784  2775  2868 E AndroidRuntime:        at java.lang.Thread.run(Thread.java:761)
This is the stacktrace that is dumped when the app crashes.
Reproduction Steps
react-native init test
npm install --save react-native-openpgp
react-native link react-native-openpgp
//index.android.js
import * as openpgp from 'react-native-openpgp';

Possible Solution
So far the only solution I see could be in the JSDebuggerWebSocketClient.java, specifically the onMessage method, It could be that the JsonReader doesn't skip some values properly. But that's only a guess.
Additional Information

React Native version: [0.41.0]
Platform: [Android (Possibly both)]
Development Operating System: [Windows]
Dev tools: [PhpStorm, Android SDK 23]

I have a similar issue with
https://github.com/layerhq/layer-websdk/issues/160

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

@hrEven I'm facing the same problem, please re-open this issue.


Add automatic management of snapshots (deletion and load)

This branch adds two new feature to snapshot system of Chainer. The
first feature is automatic deletion of old snapshot files during the
training. This is done by adding a post-save hook interface to
snapshot writers and if the number of snapshots to retain is set as
positive integers, the snapshot writers automatically lists all files
in Trainer output directory and matches the filename format.  One
limitation is that the automatic matching is only for integers but
does not work for arbitrary formatting of objects or string. For
example, if the filename format is defined as
snapshot_iter_{.updater.iteration} , the automatic matching system
picks files named as snapshot_iter_10, snapshot_iter_12000 and so
on.
Another feature is automatic loading of snapshot target at extension
initialization. If autoload option is set as True it scans the
Trainer output directory and finds matches the filename format. For
example, if files named as snapshot_iter_10 and
snapshot_iter_12000 are found at startup, it chooses the latter
as the latest snapshot and loads the data to target.
Note: this depends on #6762 to prevent conflict. Also this is more better version of  #6531 .

Note: find_latest_snapshot and find_stale_snapshots are exposed for future extension of swapping writer and lister that access HDFS (and other storage systems).

It looks the two features are independent.
Could you separate PRs to make review process simpler?

My intention to mark this as 6.0.0 milestone after feature fix is because this has high priority in our internal cluster system; It is important 1) to help Chainer users to casually get prepared for job preemption by our internal job scheduler system (along with automatic start), and 2) to save our storage spaces by automatically deleting stale snapshots, which is anticipated to increase and to occupy more space if we encourage taking snapshots more by (1).
The reason I didn't split the PR was both new features stem from one core internal function _find_snapshot_files. It defines behaviours of both autocleanup and autoload so we should discuss their spec at the same context. If I split this into two PRs then the scope and place of discussion might be confused.
I want to discuss several points such as:

It only matches integers but not string defined by the format, do we need more smart matching?
The newly exposed function names are a bit long, can they be named more cooler?
How's the idea itself?

We agreed to backport this PR.

Jenkins, test this please.

Jenkins CI test (for commit d9da82a01c832e059dfd38f44cd53d77ba6a66b4, target branch master) succeeded!

Sorry for delay.
To me, the collection part (i.e. regex part) looks a bit too adhoc.
It also does not always work (as you stated), which is confusing.
I think this inverse problem is simply too difficult and we should find another way round.
I don't have a good alternative idea, though.
Maybe the problem is that the original spec of snapshot is too general... We should have limited to some specific directory.

Discussed with the team:

We don't want to add another interface with shrunk specification (e.g. limit the directory of snapshot files) as that would affect many users and their environment (e.g. their auxiliary scripts handling snapshot files).
As the regexp method is too complicated, one alternative idea is to recognize only the prefix and the suffix of the format (it's easily done by detecting { and } respectively).
Users may request more sophiscated parser (like the current regexp method). In that case we may make the listing functionality pluggable, but not necessarily in this PR.

@kuenishi  How do you think?

@niboshi that'd be fine. Let me have time to work on it.

@niboshi I pushed new implementation that only uses prefix and suffix matching by detected {} . Please check it out.

@niboshi I removed listdir and get_ts abstraction, but still want to hear thoughts on prefix and suffix matchinng, hook and loadfun .

@niboshi ping?

@kuenishi
Sorry for being late. I commented on the last thread https://github.com/chainer/chainer/pull/6856#discussion_r298432858.
Could you proceed with that?

I think it's ready for review again :)

@niboshi Thanks for sole and careful review, I was happy to fix all of them. I hope now they're all fixed.

Note: find_latest_snapshot and find_stale_snapshots are exposed for future extension of swapping writer and lister that access HDFS (and other storage systems).

Could you elaborate this point? I feel they cannot be reused as they currently are in HDFS etc., partly because _find_snapshot_files is internal.

Could you elaborate this point? I feel they cannot be reused as they currently are in HDFS etc., partly because _find_snapshot_files is internal.

At the first aim I wanted to include new feature addition on pluggable writers to transparently switch backend storage from POSIX to HDFS, but IIRC we agreed at offline chat that those feature addition should be another PR. My original comment was before that chat, if I really remember correctly.
Anyhow I updated the PR onto the comments, thanks again @niboshi

@kuenishi Thank you for explanation. So I think find_latest_snapshot and find_stale_snapshots can be made internal.

yes, indeed. I should have done it

Thanks!
Jenkins, test this please

Jenkins CI test (for commit 1241c3fbe86608b824c55430ccaef329587b1a54, target branch master) failed with status FAILURE.

Could you check the failure in Travis CI?

Sure. Test failures in Jenkins were all from ChainerX so IMO they're flaky tests (not sure). I'll dig in test failure from Travis.

@niboshi it was a new bug in the test code made during the review process. Now fixed.

/test

Jenkins, test this please.

Jenkins CI test (for commit a3cbcd3d3869624b568745ef2d0419fe9764e4eb, target branch master) failed with status FAILURE.

It looks 10e-3 is enough as an interval and I think it's good to go.

Another approach for better determinacy would be to set file timestamps manually.
How do you think?

I didn't know os.utime and it'd be awesome! I pushed the change and carefully updated the test code, putting utime call to the place where it's really needed.

Jenkins, test this please.
@niboshi I finally got the Travis test pass. Hopefully it also passes other CIs..

mmmm... sorry about my test code being flaky. Now I hope it fixed.

Jenkins CI test (for commit 9eb18b6ed13c2322f6f29d9d295bdd32ec6654af, target branch master) failed with status FAILURE.

/test
Now this time around it should work

@niboshi Thanks for patient review, this time all tests seem passing to me.

Jenkins, test this please

Jenkins CI test (for commit c3506fc686ecc6ea4350ac88efc3d8bd0a3c09b7, target branch master) failed with status FAILURE.

LGTM!

Thanks again for working with long review rounds :)


Optimize - 16 Apr 2019

Pull Request Test Coverage Report for Build 191

10 of 11 (90.91%)  changed or added relevant lines in 4 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.09%) to 92.429%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/chess/core/internal/_applyEnPassant.js
5
6
83.33%

Totals

Change from base Build 190:
-0.09%

Covered Lines:
408

Relevant Lines:
429

💛  - Coveralls


Any possible way of getting multiple sensors working?

Been using the library with a single sensor, but now have the requirement of multiple kinects.
Thanks

Microsoft SDK for Kinect V2 only supports one device per PC.
So it's impossible w/ Microsoft SDK.


Correct cents to pence for GBP

GBP are broken up into 100 pence (or p) but not cents.

Hi @snood1205,
Did you test your changes? Each corpus file tests the behavior of its corresponding ruleset.
For this example though, internally Duckling represents money subdivisions as cents (for example, in Croatian 100 lipa make 1 kuna, and the relevant rule parses kuna as Cent).
So here I would suggest to update the ruleCent to also account for pence.

Triggering travis run.


Output 'tensorflow/core/kernels/_objs/broadcast_to_op_gpu/broadcast_to_op_gpu.cu.pic.o' was not created

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 16.04.5
TensorFlow installed from (source or binary): source
TensorFlow version: r1.11
Python version: 3.6.6
Installed using virtualenv? pip? conda?: None
Bazel version (if compiling from source): 0.18.0
GCC/Compiler version (if compiling from source): 5.4.0
CUDA/cuDNN version: 8.0 / 7.0.1
GPU model and memory: GeForce GT 740M; 2004MiB

Describe the problem
Every time I  use the bazel command to build tensorflow, this error appears:
ERROR: /home/rosgori/Python/tengpu/tensorflow/tensorflow/core/kernels/BUILD:673:1: output 'tensorflow/core/kernels/_objs/broadcast_to_op_gpu/broadcast_to_op_gpu.cu.pic.o' was not created
I have used gcc version 5.4 and 4.9 and every time a new error appears, some examples:
ERROR: /home/rosgori/Python/tengpu/tensorflow/tensorflow/core/kernels/BUILD:2250:1: output 'tensorflow/core/kernels/_objs/resize_nearest_neighbor_op_gpu/resize_nearest_neighbor_op_gpu.cu.pic.o' was not created

ERROR: /home/rosgori/Python/tengpu/tensorflow/tensorflow/contrib/image/BUILD:115:1: output 'tensorflow/contrib/image/_objs/python/ops/_distort_image_ops_gpu/adjust_hsv_in_yiq_op_gpu.cu.pic.o' was not created

ERROR: /home/rosgori/Python/tengpu/tensorflow/tensorflow/core/kernels/BUILD:3360:1: output 'tensorflow/core/kernels/_objs/conv_ops_gpu/conv_ops_gpu_3.cu.pic.o' was not created

ERROR: /home/rosgori/Python/tengpu/tensorflow/tensorflow/core/kernels/BUILD:2178:1: output 'tensorflow/core/kernels/_objs/crop_and_resize_op_gpu/crop_and_resize_op_gpu.cu.pic.o' was not created

ERROR: /home/rosgori/Python/tengpu/tensorflow/tensorflow/core/kernels/BUILD:4355:1: output 'tensorflow/core/kernels/_objs/scatter_op_gpu/scatter_op_gpu.cu.pic.o' was not created

ERROR: /home/rosgori/Python/tengpu/tensorflow/tensorflow/core/kernels/BUILD:3782:1: output 'tensorflow/core/kernels/_objs/batch_space_ops_gpu/spacetobatch_functor_gpu.cu.pic.o' was not created

ERROR: /home/rosgori/Python/tengpu/tensorflow/tensorflow/core/kernels/BUILD:673:1: output 'tensorflow/core/kernels/_objs/broadcast_to_op_gpu/broadcast_to_op_gpu.cu.pic.o' was not created

They have something in common, the extension .cu.pic.o is in every error. So my questions are: What is the meaning of this error? Can it be fixed?
I even tried r1.12 today (2018-10-28) with no success. I think it is strange that the build was successful when I tried r1.10, so... I don't know what happened there.
Provide the exact sequence of commands / steps that you executed before running into the problem
bazel build --verbose_failures -c opt --copt=-mavx --copt=-mavx2 --copt=-mfma --copt=-msse4.1 --copt=-msse4.2 --config=opt --config=cuda --cxxopt="-D_GLIBCXX_USE_CXX11_ABI=0" //tensorflow/tools/pip_package:build_pip_package
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

As I read other issues, the problem might be CUDA, it should be 9 instead of 8

@rosgori  - Yes you are right. CUDA 9  cuDNN 7 should be used. Please save this for reference.
Thanks !


support uploading kbld built images to tags

For convenience, it may be helpful to allow the destination.newImage field of an ImageDestination document to contain a tag. Currently it errors when trying to auto-generate the upload tag

i think it's probably better to have a separate tags field that will be an array. since a lot of times you may want to add multiple tags at once (e.g. tags: ["1-latest", "1.0.1"])

Would you accept a PR? When yes could you make a configuration example?

I think the easiest solution would be to pass additional tags to https://github.com/k14s/kbld/blob/5baf1d5fefa9a76ce8d46556c376ec9d8662e0f9/pkg/kbld/image/docker.go#L95

included in https://github.com/k14s/kbld/releases/tag/v0.26.0

Nice, thanks!


[Schema] cvParameter definition is referencing itself for a member definition (unit)

Should we really do this? Maybe a cvTerm accession would do.
	"cvParameter": {
		"description": "Base element containing a reference to a controlled vocabulary.",
		"type": "object",
		"properties": {
			"cvRef": {
				"description": "Reference to the CV that contains the parameter definition.",
				"type": "string",
				"pattern": "^[A-Z]+$"
			},
			"accession": {
				"description": "Accession number identifying the parameter within its CV.",
				"type": "string",
				"pattern": "^[A-Z]+:[0-9]{7}$"
			},
			"name": {
				"description": "Name of the CV element describing the parameter.",
				"type": "string"
			},
			"description": {
				"description": "Description of the parameter.",
				"type": "string"
			},
			"value": {
				"description": "Value of the parameter."
			},
			"unit": {
				"description": "A CV element describing the unit of the parameter value.",
				"anyOf": [
					{
						"$ref": "#/definitions/cvParameter"
					},
					{
						"type": "array",
						"minItems": 1,
						"items": {
							"$ref": "#/definitions/cvParameter"
						}
					}
				]
			}
		},
		"required": ["cvRef", "accession", "name"]
	},

cvParameter is used as base element for a few other elements. However, it seems like only qualityParameter would actually have a unit. (TODO: Verify this.)
So I'd propose to remove unit from cvParameter and move it to qualityParameter to extend cvParameter instead.
That shouldn't invalidate any of our existing mzQC files I think.

@mwalzer What do you think about this now? Move unit to qualityMetric as this is the only cvParameter that actually has a unit, or just keep it as is?
That schema change wouldn't make a difference for the actual mzQC files.

Yep, I think a move into qualityMetric would be appropriate. Do you want to include that in #106 ?


last device doesn't get added - doesn't have "model" attribute, skipped

Issue description
Plugin doesn't pick last added device, reporting "doesn't have "model" attribute, skipped"
Additional information
Zigbee2MQTT version: 1.14.1
Python version: 3.7.5
Domoticz version: 4.11786
Plugin version: 0.2.0
It seems that plugin is interviewing Zigbee2MQTT too fast after pairing a device, while zigbee2MQTT doesn't have the model information yet. Device addition is skipped. It is added only when pairing the next device, while the next one is not added with the same "doesn't have "model" attribute, skipped".
Following the logs - plugin questioning with "zigbee2mqtt/bridge/config/devices" same second after receiving "device_connected" on "zigbee2mqtt/bridge/log", while "interview_successful" with model information appears only after 30 sec. Question about device discovery time frame and procedure?
Same problem  encountered  in #301, #255, #217.
Logs
Domoticz:

2020-07-01 23:30:40.617 (z2mqtt) MQTT message: zigbee2mqtt/bridge/config/devices
2020-07-01 23:30:40.617 (z2mqtt) MQTT message: zigbee2mqtt/bridge/log {'type': 'devices', 'message': [{'ieeeAddr': '0x00124b00014d275a', 'type': 'Coordinator', 'networkAddress': 0, 'friendly_name': 'Coordinator', 'softwareBuildID': 'zStack12', 'dateCode': '20190608', 'lastSeen':<PHONE_NUMBER>603}]}
2020-07-01 23:30:40.617 (z2mqtt) Received available devices list from bridge
2020-07-01 23:30:40.618 (z2mqtt) Coordinator address is 0x00124b00014d275a
2020-07-01 23:30:40.718 (z2mqtt) MqttClient::ping
2020-07-01 23:30:42.191 (z2mqtt) MQTT message: zigbee2mqtt/bridge/log {'type': 'device_connected', 'message': {'friendly_name': '0x00158d0002703bbf'}}
2020-07-01 23:30:42.191 (z2mqtt) MqttClient::publish zigbee2mqtt/bridge/config/devices ()
2020-07-01 23:30:42.191 (z2mqtt) MQTT message: zigbee2mqtt/bridge/log {'type': 'pairing', 'message': 'interview_started', 'meta': {'friendly_name': '0x00158d0002703bbf'}}
2020-07-01 23:30:42.191 (z2mqtt) MQTT message: zigbee2mqtt/bridge/log {'type': 'device_announced', 'message': 'announce', 'meta': {'friendly_name': '0x00158d0002703bbf'}}
2020-07-01 23:30:42.243 (z2mqtt) MQTT message: zigbee2mqtt/bridge/config/devices
2020-07-01 23:30:42.244 (z2mqtt) MQTT message: zigbee2mqtt/bridge/log {'type': 'devices', 'message': [{'ieeeAddr': '0x00124b00014d275a', 'type': 'Coordinator', 'networkAddress': 0, 'friendly_name': 'Coordinator', 'softwareBuildID': 'zStack12', 'dateCode': '20190608', 'lastSeen':<PHONE_NUMBER>196}, {'ieeeAddr': '0x00158d0002703bbf', 'networkAddress': 7021, 'vendor': '-', 'description': '-', 'friendly_name': '0x00158d0002703bbf', 'lastSeen':<PHONE_NUMBER>179}]}
2020-07-01 23:30:42.245 (z2mqtt) Received available devices list from bridge
2020-07-01 23:30:42.245 (z2mqtt) Coordinator address is 0x00124b00014d275a
2020-07-01 23:30:42.245 (z2mqtt) Device 0x00158d0002703bbf (0x00158d0002703bbf) doesn't have "model" attribute, skipped
2020-07-01 23:30:43.104 (z2mqtt) MQTT message: zigbee2mqtt/0x00158d0002703bbf {'battery': 100, 'voltage': 3005, 'linkquality': 110}
2020-07-01 23:30:50.732 (z2mqtt) MqttClient::ping
2020-07-01 23:31:00.745 (z2mqtt) MqttClient::ping
2020-07-01 23:31:10.724 (z2mqtt) MqttClient::ping
2020-07-01 23:31:12.810 (z2mqtt) MQTT message: zigbee2mqtt/bridge/log {'type': 'pairing', 'message': 'interview_successful', 'meta': {'friendly_name': '0x00158d0002703bbf', 'model': 'SJCGQ11LM', 'vendor': 'Xiaomi', 'description': 'Aqara water leak sensor', 'supported': True}}
2020-07-01 23:31:20.766 (z2mqtt) MqttClient::ping

Zigbee2MQTT:

zigbee2mqtt:info  2020-07-01 20:28:37: MQTT publish: topic 'zigbee2mqtt/bridge/state', payload 'online'
zigbee2mqtt:info  2020-07-01 20:28:37: MQTT publish: topic 'zigbee2mqtt/bridge/config', payload '{"version":"1.14.1","commit":"7e46435","coordinator":{"type":"zStack12","meta":{"transportrev":2,"product":0,"majorrel":2,"minorrel":6,"maintrel":3,"revision":20190608}},"log_level":"debug","permit_join":true}'
zigbee2mqtt:warn  2020-07-01 20:30:40: Device '0x00158d0002703bbf' left the network
zigbee2mqtt:info  2020-07-01 20:30:40: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_removed","message":"left_network","meta":{"friendly_name":"0x00158d0002703bbf"}}'
zigbee2mqtt:debug 2020-07-01 20:30:40: Received MQTT message on 'zigbee2mqtt/bridge/config/devices' with data ''
zigbee2mqtt:info  2020-07-01 20:30:40: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"devices","message":[{"ieeeAddr":"0x00124b00014d275a","type":"Coordinator","networkAddress":0,"friendly_name":"Coordinator","softwareBuildID":"zStack12","dateCode":"20190608","lastSeen":1593635440603}]}'
zigbee2mqtt:info  2020-07-01 20:30:42: Device '0x00158d0002703bbf' joined
zigbee2mqtt:info  2020-07-01 20:30:42: Starting interview of '0x00158d0002703bbf'
zigbee2mqtt:info  2020-07-01 20:30:42: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_connected","message":{"friendly_name":"0x00158d0002703bbf"}}'
zigbee2mqtt:info  2020-07-01 20:30:42: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_started","meta":{"friendly_name":"0x00158d0002703bbf"}}'
zigbee2mqtt:debug 2020-07-01 20:30:42: Device '0x00158d0002703bbf' announced itself
zigbee2mqtt:info  2020-07-01 20:30:42: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"device_announced","message":"announce","meta":{"friendly_name":"0x00158d0002703bbf"}}'
zigbee2mqtt:debug 2020-07-01 20:30:42: Received MQTT message on 'zigbee2mqtt/bridge/config/devices' with data ''
zigbee2mqtt:info  2020-07-01 20:30:42: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"devices","message":[{"ieeeAddr":"0x00124b00014d275a","type":"Coordinator","networkAddress":0,"friendly_name":"Coordinator","softwareBuildID":"zStack12","dateCode":"20190608","lastSeen":1593635442196},{"ieeeAddr":"0x00158d0002703bbf","networkAddress":7021,"vendor":"-","description":"-","friendly_name":"0x00158d0002703bbf","lastSeen":1593635442179}]}'
zigbee2mqtt:debug 2020-07-01 20:30:42: Received Zigbee message from '0x00158d0002703bbf', type 'attributeReport', cluster 'genBasic', data '{"modelId":"lumi.sensor_wleak.aq1","appVersion":4}' from endpoint 1 with groupID 0
zigbee2mqtt:debug 2020-07-01 20:30:43: Received Zigbee message from '0x00158d0002703bbf', type 'attributeReport', cluster 'genBasic', data '{"65281":{"1":3005,"3":30,"4":424,"5":83,"6":[0,1],"8":516,"10":0,"100":0}}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2020-07-01 20:30:43: MQTT publish: topic 'zigbee2mqtt/0x00158d0002703bbf', payload '{"battery":100,"voltage":3005,"linkquality":110}'
zigbee2mqtt:debug 2020-07-01 20:30:53: Received Zigbee message from '0x00158d0002703bbf', type 'readResponse', cluster 'genBasic', data '{"manufacturerName":"LUMI"}' from endpoint 1 with groupID 0
zigbee2mqtt:debug 2020-07-01 20:30:56: Received Zigbee message from '0x00158d0002703bbf', type 'readResponse', cluster 'genBasic', data '{"powerSource":3}' from endpoint 1 with groupID 0
zigbee2mqtt:debug 2020-07-01 20:30:59: Received Zigbee message from '0x00158d0002703bbf', type 'readResponse', cluster 'genBasic', data '{"zclVersion":1}' from endpoint 1 with groupID 0
zigbee2mqtt:debug 2020-07-01 20:31:03: Received Zigbee message from '0x00158d0002703bbf', type 'readResponse', cluster 'genBasic', data '{"stackVersion":2}' from endpoint 1 with groupID 0
zigbee2mqtt:debug 2020-07-01 20:31:06: Received Zigbee message from '0x00158d0002703bbf', type 'readResponse', cluster 'genBasic', data '{"hwVersion":2}' from endpoint 1 with groupID 0
zigbee2mqtt:debug 2020-07-01 20:31:09: Received Zigbee message from '0x00158d0002703bbf', type 'readResponse', cluster 'genBasic', data '{"dateCode":"20170721"}' from endpoint 1 with groupID 0
zigbee2mqtt:debug 2020-07-01 20:31:12: Received Zigbee message from '0x00158d0002703bbf', type 'readResponse', cluster 'genBasic', data '{"swBuildId":"3000-0001"}' from endpoint 1 with groupID 0
zigbee2mqtt:info  2020-07-01 20:31:12: Successfully interviewed '0x00158d0002703bbf', device has successfully been paired
zigbee2mqtt:info  2020-07-01 20:31:12: Device '0x00158d0002703bbf' is supported, identified as: Xiaomi Aqara water leak sensor (SJCGQ11LM)
zigbee2mqtt:info  2020-07-01 20:31:12: MQTT publish: topic 'zigbee2mqtt/bridge/log', payload '{"type":"pairing","message":"interview_successful","meta":{"friendly_name":"0x00158d0002703bbf","model":"SJCGQ11LM","vendor":"Xiaomi","description":"Aqara water leak sensor","supported":true}}'
zigbee2mqtt:debug 2020-07-01 20:33:34: Saving state to file /app/data/state.json
```

Same problem encountered in #301, #255, #217.

Yes, you are right, this issue is well known and isn't related to plugin. You need to repair your device

Repairing doesn't help as leads to same situation. On the contrary, issuing a message to "zigbee2mqtt/bridge/config/devices" topic just after Zigbee2MQTT reports that device is paired - voila, device is discovered properly.

Also, you probably noticed (I did, with my devices, and searched all over), that device with "doesn't have model attribute, skipped" error is ALWAYS at the end of devices list. Isn't it strange? Not for me.
https://github.com/stas-demydiuk/domoticz-zigbee2mqtt-plugin/blob/16cc31bf2ffa96199c2aa5cda416a59ca31a40a1/plugin.py#L165-L166
Devices list is requested on message type "device_connected" or "device_removed" (and also on Zigbee2mqtt state "online", that's why restarting Zigbee2mqtt helps with last device discovery), however when a new device is connecting to zigbee network - it takes time to find the model. Wouldn't it be better to watch for the message type "pairing", with payload "interview_successful"?

Yes, makes sense, updated plugin with that change

Very good, as I already made a fork and implemented that change. Thanks for the plugin, keep up the good work.


Rework ordering of linear models module

Fixes #697. Fixes #641.
This PR addresses al the point in #697 except for the point:

rename "Beyond linear separation in classification"

This will be addressed in a different PR as I would like to fit the narrative to the new placing of this notebook.
Furthermore, we can consider moving Q2 from M4.05

The decision boundaries of a logistic regression:
a) uses only one of the input features
b) uses a combination of the input features
c) separates a single class

out of the regularization lesson and into the Quiz M4.02, i.e. in the lesson on intuitions.

Merged main to see the render with the synchronized quizzes from #708.

Thank you @ArturoAmorQ. @glemaitre and I will now work on some follow-up PRs for feature engineering for linear classification and regularization for linear classification.


Enhancement of Terraform modules for App Service - Enable free plan

Content
This PR contains the changes necessary for a user to use the Azure App Service with a free plan. This plan is special as it comes with limitation concerning some settings, namely the always_on and the support of 64 bit workers.
The PR therefore exposes these configurations as variables and propagates the variables to the core modules.
The Terraform variables are defaulted and consequently optional.  They contain the default values of the current setup. Introduction of the variables is therefore not a breaking change.
Reason
This setup might be useful for azd templates that serve as quickstarter or for demos/lessons at schools/universities to keep the cost of the setup at a minimum.
Additional information
The .bicep modules already contain the  necessary parameters. So this PR synchronizes the options available for the supported IaC variants.

related: https://github.com/Azure/azure-dev/issues/1460

Should we default to free?

Should we default to free?

From what I have seen in our quickstarter repository, I would stick to the plan B1 for the azd templates, as the experience is better (due to the always_on setting). As with this PR you can reconfigure things for the free and shared plans I think this is okay.

Can we do the same for bicep templates?

@jongio The bicep template was already in perfect shape for adding the free plan. No adoptions needed there.

/azp run azure-dev repoman

/azp run azure-dev - template - tests

/azp run azure-dev - repoman

/azp run azure-dev - repoman

Repoman Generation Results
Repoman pushed changes to remotes for the following projects:
Project: todo-nodejs-mongo-terraform
Remote: azure-samples-staging
Branch: pr/1496
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-terraform -b pr/1496

View Changes | Compare Changes

Project: todo-python-mongo-terraform
Remote: azure-samples-staging
Branch: pr/1496
You can initialize this project with:
azd init -t Azure-Samples/todo-python-mongo-terraform -b pr/1496

View Changes | Compare Changes

@lechnerc77 , please see the error messages from Terraform:

╵

╷
│ Error: Unclosed configuration block
│
│ On modules/appservicepython/appservicepython_variables.tf line 59: There is
│ no closing brace for this block before the end of the file. This may be
│ caused by incorrect brace nesting elsewhere in this file.
╵

╷
│ Error: Unclosed configuration block
│
│ On modules/appservicepython/appservicepython_variables.tf line 59: There is
│ no closing brace for this block before the end of the file. This may be
│ caused by incorrect brace nesting elsewhere in this file.
╵

╷
│ Error: Unclosed configuration block
│
│ On modules/appservicepython/appservicepython_variables.tf line 59: There is
│ no closing brace for this block before the end of the file. This may be
│ caused by incorrect brace nesting elsewhere in this file.
╵

╷
│ Error: Unclosed configuration block
│
│ On modules/appservicenode/appservicenode_variables.tf line 59: There is no
│ closing brace for this block before the end of the file. This may be caused
│ by incorrect brace nesting elsewhere in this file.
╵

ERROR: planning deployment: planning infrastructure provisioning: terraform init failed:  , err: failed running terraform init:  (exit status 1)

### ERROR: Dev container exec failed (exit code: 1)

Trying closing missing bracket as simple fix

/azp run azure-dev - repoman

Repoman Generation Results
Repoman pushed changes to remotes for the following projects:
Project: todo-nodejs-mongo-terraform
Remote: azure-samples-staging
Branch: pr/1496
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-terraform -b pr/1496

View Changes | Compare Changes

Project: todo-python-mongo-terraform
Remote: azure-samples-staging
Branch: pr/1496
You can initialize this project with:
azd init -t Azure-Samples/todo-python-mongo-terraform -b pr/1496

View Changes | Compare Changes

/azp run azure-dev - repoman

Repoman Generation Results
Repoman pushed changes to remotes for the following projects:
Project: todo-nodejs-mongo-terraform
Remote: azure-samples-staging
Branch: pr/1496
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-terraform -b pr/1496

View Changes | Compare Changes

Project: todo-python-mongo-terraform
Remote: azure-samples-staging
Branch: pr/1496
You can initialize this project with:
azd init -t Azure-Samples/todo-python-mongo-terraform -b pr/1496

View Changes | Compare Changes

Trying closing missing bracket as simple fix

Seems to have worked, right? Sorry for that glitch!

blocked by: https://github.com/Azure/azure-dev/pull/1764

/azp run azure-dev - repoman

Repoman Generation Results
Repoman pushed changes to remotes for the following projects:
Project: todo-nodejs-mongo-terraform
Remote: azure-samples-staging
Branch: pr/1496
You can initialize this project with:
azd init -t Azure-Samples/todo-nodejs-mongo-terraform -b pr/1496

View Changes | Compare Changes

Project: todo-python-mongo-terraform
Remote: azure-samples-staging
Branch: pr/1496
You can initialize this project with:
azd init -t Azure-Samples/todo-python-mongo-terraform -b pr/1496

View Changes | Compare Changes


Track items to synchronize

[x] Update kind tests and kube version (WLO PR)
[x] Fix e2e tests to non-OpenShift (WLO PR)

Delivered by https://github.com/application-stacks/runtime-component-operator/pull/495


Update yeoman dependencies

Similar to https://github.com/jhipster/generator-jhipster/pull/9267 this PR updates the yeoman dependencies as follows:

yeoman-generator: 3.2.0
yeoman-environment: 2.3.4
yeoman-test: 1.9.1

I have tested these for the main generator and the Kotlin and VueJS blueprints for https://github.com/jhipster/generator-jhipster/pull/9266

Please make sure the below checklist is followed for Pull Requests.

[ ] Travis tests are green

[x] Tests are added where necessary

[x] Documentation is added/updated where necessary

[x] Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

Thanks @pvliss
I put on hold label, as I need to check if it is compatible with generator-jhipster 5.8.1, master or both.
It is because we plan to do a release next week and I don't want something broken because of different dependencies between this blueprint and generator-jhipster

@pascalgrimaud  Yes, I understand. By release you mean final? If so I did not realize and I was under the impression you were building against current master(6.x) but I did not check. I can change it if you want to match the ones in v5.8.1(which seem to be the same with 5.x maintenance as well). BTW, is there a plan to release a 5.8.2 as well? I could do a PR to update the dependencies over there as well and see if npm test and CI builds pass which I guess is enough? The biggest change I see is moving from yeoman-generator 2.0.5 to 3.x.x and JHipster 5.8.1 is already at 3.0.0, so that should not be a big problem.

Forgot to mention that running npm install generates a lot of security warnings mainly related to lodash and there are 2-3 more dependencies that could be updated as well. Again if you are targeting 5.8.1 I guess these can wait but should be checked nonetheless

The biggest change I see is moving from yeoman-generator 2.0.5 to 3.x.x and JHipster 5.8.1 is already at 3.0.0

in that case, let's merge this !!!

Wow, that was fast!!!

Thanks @pascalgrimaud

Would you like me to check the other dependencies as well by using npm audit fix or will you take care of it instead?

No computer this weekend for me (only my phone), so if you have the bandwidth, yes, it will help us a lot.

Oh, OK. Yes, I will check and create PRs as needed. Thanks

You contribute a lot, to the organization JHipster, the last weeks / months.
Maybe you would be interested to join us ?

@pascalgrimaud Sure, I would be honored!!!

Give me few days and I'll speak to Julien :-)

Thanks @pascalgrimaud. I really appreciate this


Merge master into live

Please don't squash-merge this PR.

closing / reopening for a fresh build


feat!: bump remark dependencies and support ESM only

<EMAIL_ADDRESS>supports only ESM.

https://github.com/ybiquitous/remark-preset-ybiquitous/pull/23/checks?check_run_id=3328187750#step:6:26
remark-gfm seems to have a problem... 🤔
README.md
  1:1  error  TypeError: Cannot read property '2' of undefined
    at lineStart (file:///Users/masafumi.koba/git/ybiquitous/remark-preset-ybiquitous/node_modules/micromark-extension-gfm-table/lib/syntax.js:563:30)
    at go (/Users/masafumi.koba/git/ybiquitous/remark-preset-ybiquitous/node_modules/micromark/dist/util/create-tokenizer.js:136:13)
    at main (/Users/masafumi.koba/git/ybiquitous/remark-preset-ybiquitous/node_modules/micromark/dist/util/create-tokenizer.js:130:9)
    at Object.write (/Users/masafumi.koba/git/ybiquitous/remark-preset-ybiquitous/node_modules/micromark/dist/util/create-tokenizer.js:70:5)
    at continueFlow (/Users/masafumi.koba/git/ybiquitous/remark-preset-ybiquitous/node_modules/micromark/dist/initialize/document.js:119:15)
    at flowContinue (/Users/masafumi.koba/git/ybiquitous/remark-preset-ybiquitous/node_modules/micromark/dist/initialize/document.js:97:7)
    at flowStart (/Users/masafumi.koba/git/ybiquitous/remark-preset-ybiquitous/node_modules/micromark/dist/initialize/document.js:86:12)
    at go (/Users/masafumi.koba/git/ybiquitous/remark-preset-ybiquitous/node_modules/micromark/dist/util/create-tokenizer.js:136:13)
    at main (/Users/masafumi.koba/git/ybiquitous/remark-preset-ybiquitous/node_modules/micromark/dist/util/create-tokenizer.js:130:9)
    at Object.write (/Users/masafumi.koba/git/ybiquitous/remark-preset-ybiquitous/node_modules/micromark/dist/util/create-tokenizer.js:70:5)

The error of (https://github.com/ybiquitous/remark-preset-ybiquitous/pull/23#issuecomment-898860933) is caused by<EMAIL_ADDRESS>as a ybiq's dependency.
The commit 1e392a3 can fix it by installing<EMAIL_ADDRESS>explicitly.
$ npm ls remark
<EMAIL_ADDRESS>/Users/masafumi.koba/git/ybiquitous/remark-preset-ybiquitous
├─┬<EMAIL_ADDRESS>│ └──<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>


It seems that wherever I send #learn or #sleep, I will be muted at the QQ group 769885907. Can you fix it?

It seems that wherever I send #learn or #sleep, I will be muted at the QQ group 769885907. Can you fix it?
@xinyunaha

This bug has been fixed


Create nuxt project use  create-nuxt-app(3.2.0 select typescript) runing error

I build nuxt project use create-nuxt-app(3.2.0 select typescript), runing error.
The cli install @nuxt/typescript-runtime version 1.0.0 in dependencies, I think it's should install version 2.0.0 in devDependencies

Duplicate of https://github.com/nuxt/create-nuxt-app/issues/602
Fixed in https://github.com/nuxt/create-nuxt-app/pull/599
Release pending (cc @pi0)


MudDatePicker DisplayMonths issue #6270

Description

MudBlazor.Docs: Added DatePickerMultipleMonthsExample.razor on DatePickerPage.razor.
MudBlazor: DatePicker: Changed DatePicker behavior, when DisplayMonths is greater than 1. Now months/years view opens not in first calendar, but in one which header was clicked (#6270)

Closes #6270
I'm new to open-source project development. Hope i didn't miss anything and this helps.
How Has This Been Tested?

I've tested it visually on local server.
Types of changes

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

Checklist:

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[x] I've added relevant tests.

Hi.
Why was this PR closed? Because no one responded or there is another reason?


Media Ext - Fix and additions

Updates to readme

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 10

See the complete overview on Codacy


Unexpected end of JSON input on Task Inputs and Outputs example

Expected Behavior
Run the tutorial to have a build image.
Actual Behavior
kubectl logs build-docker-image-from-git-source-task-run-pod-acf4c7 -c step-build-and-push
INFO[0000] Downloading base image golang:1.12.6-alpine3.9
2019/08/16 18:21:46 No matching credentials were found, falling back on anonymous
INFO[0000] Unpacking rootfs as cmd RUN go build -o /web . requires it.
INFO[0006] Taking snapshot of full filesystem...
INFO[0007] Skipping paths under /kaniko, as it is a whitelisted directory
INFO[0007] Skipping paths under /proc, as it is a whitelisted directory
INFO[0007] Skipping paths under /var/run, as it is a whitelisted directory
INFO[0007] Skipping paths under /sys, as it is a whitelisted directory
INFO[0007] Skipping paths under /dev, as it is a whitelisted directory
INFO[0007] Skipping paths under /builder/home, as it is a whitelisted directory
INFO[0007] Skipping paths under /builder/tools, as it is a whitelisted directory
INFO[0007] Skipping paths under /workspace, as it is a whitelisted directory
INFO[0009] Using files from context: [/workspace/docker-source/examples/microservices/leeroy-web/web.go]
INFO[0009] COPY web.go .
INFO[0009] Taking snapshot of files...
INFO[0009] RUN go build -o /web .
INFO[0009] cmd: /bin/sh
INFO[0009] args: [-c go build -o /web .]
INFO[0010] Taking snapshot of full filesystem...
INFO[0011] Skipping paths under /kaniko, as it is a whitelisted directory
INFO[0011] Skipping paths under /proc, as it is a whitelisted directory
INFO[0011] Skipping paths under /var/run, as it is a whitelisted directory
INFO[0011] Skipping paths under /sys, as it is a whitelisted directory
INFO[0011] Skipping paths under /dev, as it is a whitelisted directory
INFO[0011] Skipping paths under /builder/home, as it is a whitelisted directory
INFO[0011] Skipping paths under /builder/tools, as it is a whitelisted directory
INFO[0011] Skipping paths under /workspace, as it is a whitelisted directory
INFO[0011] Adding whiteout for /root/.cache/go-build/e3/e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855-d
INFO[0011] Adding whiteout for /root/.cache/go-build/31/311571a11a5934d4f63ba6daaa1b0a1e578ee13a1a373547131af1d9d157dbb4-d
INFO[0011] Adding whiteout for /root/.cache/go-build/98/9816bb371bccde8cb7bf5a44febdb32bbc327a0a5c2e940d9b8b3a402f62e4f0-d
INFO[0011] Adding whiteout for /root/.cache/go-build/77/77a522d1008cfd60284c5bd5cc6fc283abe7ef012d61d06d0fd6b1ff03becc68-a
INFO[0011] Adding whiteout for /root/.cache/go-build/c4/c483d510e0608431902a9e3aa9e162e4b88f745b790a07a1a4b45f22ef9013f4-a
INFO[0011] Adding whiteout for /root/.cache/go-build/e0/e0d9637a42516f6aa3defff56cc9a4d3deaf96b2ade546448835c41bd63d82bc-a
INFO[0011] Adding whiteout for /root/.cache/go-build/b5/b5cb5076dbba489139e99e802f57979f0f7f4f96806267201ca4e383513a312b-a
INFO[0011] Adding whiteout for /root/.cache/go-build/5e/5eddca62332aaa6cb767cf6e8b4ce6b00d97ee63b3f549ac9586becdaea0f26c-d
INFO[0013] Storing source image from stage 0 at path /kaniko/stages/0
INFO[0020] Deleting filesystem...
INFO[0023] Downloading base image alpine:3.9
2019/08/16 18:22:09 No matching credentials were found, falling back on anonymous
INFO[0023] Taking snapshot of full filesystem...
INFO[0024] Skipping paths under /kaniko, as it is a whitelisted directory
INFO[0024] Skipping paths under /proc, as it is a whitelisted directory
INFO[0024] Skipping paths under /var/run, as it is a whitelisted directory
INFO[0024] Skipping paths under /sys, as it is a whitelisted directory
INFO[0024] Skipping paths under /dev, as it is a whitelisted directory
INFO[0024] Skipping paths under /builder/home, as it is a whitelisted directory
INFO[0024] Skipping paths under /builder/tools, as it is a whitelisted directory
INFO[0024] Skipping paths under /workspace, as it is a whitelisted directory
INFO[0024] CMD ["./web"]
INFO[0024] COPY --from=builder /web .
INFO[0024] Taking snapshot of files...
error pushing image: failed to push to destination us.icr.io/moficodes/leeroy-web:latest: unexpected end of JSON input

I think two lines to notice is
2019/08/16 18:21:46 No matching credentials were found, falling back on anonymous

and
error pushing image: failed to push to destination us.icr.io/moficodes/leeroy-web:latest: unexpected end of JSON input

If this is a secret issue, maybe we can see little better error messages.
But I should have the right credentials set. In this namespace I can pull image from the same source.
Might be missing something.
Steps to Reproduce the Problem

Run through the Task Inputs and Outputs tutorial.

Additional Info
Run on a vanilla k8s on IKS 1.15

Hi again! :D
@moficodes looking at the output:
error pushing image: failed to push to destination us.icr.io/moficodes/leeroy-web:latest: unexpected end of JSON input

I think maybe  us.icr.io should be us.gcr.io?

Hey @bobcatfish no its the ibm cloud container registry. 😬
I will try testing with some other container registry next and see if thats why its failing.

Hey @bobcatfish no its the ibm cloud container registry. 😬

hahaha sorry about that! I tried to go to us.icr.io in my browser with no luck and thought that was the end of it XD
This probably has something to do with how kaniko is doing the auth then - https://github.com/GoogleContainerTools/kaniko/issues/425 looks like a related issue tho i dont think it points at a clear answer 🤔

If this is a secret issue, maybe we can see little better error messages.

Unfortunately that error is coming from kaniko so you might be able to find more on how to get thi to work at  https://github.com/GoogleContainerTools/kaniko
Also our docs on our kaniko catalog task might help: https://github.com/tektoncd/catalog/tree/master/kaniko#serviceaccount

The service account secret was the culprit.
More specifically
  annotations:
    tekton.dev/docker-0: https://gcr.io # Described below

Adding this annotation and pointing it to the right base.
Its a bit weird. But the image is created and pushed to the cloud. 🤘🏽
Thank you @bobcatfish for your help.
Closing.

Glad you were able to get it working @moficodes !!! Seems a bit odd that you have to use an annotation with gcr.io when you're actually using icr.io :sweat_smile:  Feel free to open another issue if it's something you feel we should look into further :pray:


Failed at the<EMAIL_ADDRESS>install script

Hello all, starting to pull my hair out. I've tried to install home bridge but keep hitting the road block of node and npm versions. Any help would be appreciated. I have also tried to remove and reinstall node and npm but it just won't update to the newer versions.
npm ERR! Linux 4.4.26+
npm ERR! argv "node" "/usr/local/bin/npm" "install" "-g" "homebridge"
npm ERR! node v0.10.29
npm ERR! npm  v3.10.9
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>install: node-pre-gyp install --fallback-to-build
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the bignum package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node-pre-gyp install --fallback-to-build
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs bignum
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls bignum
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/npm-debug.log

npm ERR! node v0.10.29

You are still using node 0.10.29... Try install node v6.x using the following command
curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -
sudo apt-get install -y nodejs

Thank you for the quick reply. I ran that command. Here is the outcome.
`pi@raspberrypi:~ $ curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash -
Installing the NodeSource Node.js v6.x repo...
You appear to be running on ARMv6 hardware. Unfortunately this is not currently supported by the NodeSource Linux distributions. Please use the 'linux-armv6l' binary tarballs available directly from nodejs.org for Node.js v4 and later.
pi@raspberrypi:~ $ sudo apt-get install -y nodejs
Reading package lists... Done
Building dependency tree
Reading state information... Done
nodejs is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.`

Ah, you are running on the old raspberry pi. Have you tried using n to switch version? https://www.npmjs.com/package/n

I just followed this tut.
https://blog.wia.io/installing-node-js-v4-0-0-on-a-raspberry-pinode -v
now shows V4.0.0

I'd afraid you need at least 4.5 or higher... you can try to follow the same article and replace 4.0.0 with 6.9.1

Ya,
looks like its wanting at least 4.3.2
engine<EMAIL_ADDRESS>wanted: {"node":">=4.3.2"} (current: {"node":"4.0.0","npm":"2.14.2"})

I followed the same tut but went with v5. so far so good.

Ran into some snags. Looks npm is also outdated.
I will try again when I get home later today. Thanks.

edit package.json and bignum 0.13.0


Update repo references from baseobject to skbase

Reference Issues/PRs
Fixes #72 by updating references to old repo name (renaming was handled outside PR in github).

@fkiraly this should be ready for you to review. From my readings, it looks like Github rename of repo, will update refs from old repo to new one, so our App integrations are still working. We can separately make sure those are all authorized on the new repo name.


upgrades to django2.1

Coverage remained the same at 38.889% when pulling 9698a20801e647564199afcc786f69e84b9d91ad on feature/django2.1 into cc213cd42e76bdaf960514e3b296fffb28b1dd90 on master.


Hsp 27 binding, Hsp 27 regulator

Hello,
I have a gene product that specifically interacts with
the heat shock protein 27 - hsp 27 - and exerts an
inhibitory effect upon its functioning.
PMID: 11546764 and references therein
Heat shock protein 27 participates in an number of
processes; its activity is modulated via interactions with
a range of proteins
Proposed terms
GO:0005515 - protein binding
GO:new - Hsp 27 binding
Def: Interacting selectively with Hsp 27, a member of
the light weight heat shock proteins.
GO:0030188 - chaperone regulator activity
GO:new - Hsp 27 regulator activity
Def: Modulates the activity of light weight chaperone
proteins.
GO:0030190 - chaperone inhibitor activity
GO_new - Hsp 27 inhibitor activity
Def: Stops, prevents or reduces the activity of light
weight chaperone proteins.
Thank you,
Victoria
Reported by: vpetri
Original Ticket: "geneontology/ontology-requests/1541":https://sourceforge.net/p/geneontology/ontology-requests/1541

thanks www.movied.org


Master

Hey,
Here's an implementation of Muller's Method (and a subtle change in Racket's folder since I wasn't able to clone it).
Let me know if I did anything wrong.
Gabriel

Thanks 👍🏼


Too many SQL queries getting executed in tenant creation

There are around 12500 SQL queries getting executed when we create a tenant in IS-5.3.0 default pack. But in IS-5.2.0, it was around 1660 SQLs.
Almost all additional queries has been done against following tables.
IDN_CLAIM_MAPPING
IDN_CLAIM_MAPPED_ATTRIBUTE
IDN_CLAIM_DIALECT
IDN_CLAIM_PROPERTY
IDN_CLAIM

This issue occurs as below happens whenever a claim gets added in order to load claims back to the cache.

Add claim, attribute mappings and attribute properties to the database
Get all claims from the database
For each claim a database call is initiated to retrieve attribute mappings and another call is initiated to retrieve metadata properties

Above gets significant in tenant creation flow as all claims get added to the database upon tenant initialization.

Added https://github.com/wso2/product-is/issues/3081 to identify and improve the flow when adding a claim.
With this respective issue we will focus only on improving the flow while adding all claims in bulk mode with tenant creation.


Device model: philips.light.ceiling.

Why is only MiCloud connection used instead of local connection? It is very slow and does not work without internet connection. Here is plugin with a local connection and very fast response from the device:
https://github.com/CorsairCat/homebridge-mi-philips-light

Not sure how many times I should explain this😅
This plugin is for devices which support the miot protocol! Your device is an older device which does not support the miot protocol but instead uses the miio protocol. For convenience xiaomi offers miot protocol emulation for older device but that only works over the MiCloud! This is something I cannot change, so if you are using older devices with this plugin you will have a slight delay, depending on what server you have your devices.

Thank you for your comment. Now I know a lot more about my celling light


Follow Microsoft 365 on Social Media needs some updates

Article issue
The article Follow Microsoft 365 on Social Media needs some updates and improvements:

the highlighted tip to have a Power Automate template to monitor certain hashtags is not linked to a template and not described how to do that
noone is using the in the tip highlighted # "PowerHelp" - I ran a query on twitter and there are only 5 tweets in the last two years using that hashtag, seems to be irrelevant
same for # pnphelp, last time it was used was in 2018
the hashtags # m365pnp # Microsoft365 are missing
the list of notable twitter accounts of Microsoft people and community people should be longer.

Happy to fix that :-)

@PathToSharePoint - This is your article; just want to keep you in the loop. I say go for it, @LuiseFreese - open source!

@PathToSharePoint - This is your article; just want to keep you in the loop. I say go for it, @LuiseFreese - open source!

Thanks for the list of suggestions @LuiseFreese ! And thx for pinging me @sympmarc , this is a timely topic as it'll be the subject of my presentation tomorrow at the Cal conference.
Certainly the most important point is to turn the list into action, with an actual template. Love the idea! For the record as part of my presentation I'll share a Power BI template and that could be linked too. Click here for the demo.
Sounds good to remove the unused hashtags, I think those were not in my original piece and were added later (maybe more people to ping).
As for #M365PnP and other M365 tags, I ran a poll at the time (Marc was also involved), and the general feedback was that Microsoft365 should be spelled out. Maybe something to revisit... on Twitter! #Microsoft365 is there, actually one of the first on the list.
The list of notable accounts is a tough one, and I think you already called me a nerd on that one ;-) My initial idea was to list all accounts with more than 20,000 followers.

Thanks for the list of suggestions @LuiseFreese ! And thx for pinging me @sympmarc , this is a timely topic as it'll be the subject of my presentation tomorrow at the Cal conference.
Certainly the most important point is to turn the list into action, with an actual template. Love the idea! For the record as part of my presentation I'll share a Power BI template and that could be linked too. Click here for the demo.
Sounds good to remove the unused hashtags, I think those were not in my original piece and were added later (maybe more people to ping).
As for #M365PnP and other M365 tags, I ran a poll at the time (Marc was also involved), and the general feedback was that Microsoft365 should be spelled out. Maybe something to revisit... on Twitter! #Microsoft365 is there, actually one of the first on the list.
The list of notable accounts is a tough one, and I think you already called me a nerd on that one ;-) My initial idea was to list all accounts with more than 20,000 followers.

@LuiseFreese follow up on the templates. After doing some work on my Power BI template this week, it's clear that it will require its own repository and page(s) for  instructions. Not something that would just fit in the current page. I am open to ideas and suggestions, and to hear what you have in mind for the automate sample. For now my plan is to use my own blog and github repository. Also, click here for the latest sample, feedback welcome :-)
I also started looking into the Power Platform Twitter connector. In particular I see that GCC has a specific entry point.
Another path I am exploring is LinkedIn. It is not as popular as Twitter, but being a Microsoft company it certainly deserves a mention in a page dedicated to social media. I could imagine that eventually each hashtag gets two links, one for Twitter and one for LinkedIn (hopefully the hashtags are the same!).

@LuiseFreese follow up on the templates. After doing some work on my Power BI template this week, it's clear that it will require its own repository and page(s) for  instructions. Not something that would just fit in the current page. I am open to ideas and suggestions, and to hear what you have in mind for the automate sample. For now my plan is to use my own blog and github repository. Also, click here for the latest sample, feedback welcome :-)
I also started looking into the Power Platform Twitter connector. In particular I see that GCC has a specific entry point.
Another path I am exploring is LinkedIn. It is not as popular as Twitter, but being a Microsoft company it certainly deserves a mention in a page dedicated to social media. I could imagine that eventually each hashtag gets two links, one for Twitter and one for LinkedIn (hopefully the hashtags are the same!).

Just making a note that Viva needs to be added too. There seems to be a twitter account https://twitter.com/MicrosoftViva but it is currently protected. As for the hashtags, there is no clear favorite yet between #MicrosoftViva and #MSFTViva.

@PathToSharePoint - @jeffteper made it official on Twitter.

@sympmarc so #MSFTViva it is, I'd love to hear the rationale here. It seems to me that the rule so far was to NOT abbreviate Microsoft.
I have published my Power BI report for Twitter. I don't want to force it on everybody, so I'll wait to hear if it's worth including in the article. For the record, I'll use it in March to track MS Ignite news. This is also the topic of my upcoming speaking engagement at the Scottish Summit, so hopefully I'll get some more feedback soon.
Next, I'll try to put together a Power Automate template. I guess we actually need two as the GCC connector is different.

Hey, if Jeff says it's #MSFTViva, then that's what it is!
I'm not sure about your Power BI report. It seems that using lists or steams in something like HootSuite give people a way to customize their own Twitter feeds.

@sympmarc good call, and maybe a third party tool like HootSuite is what we could recommend instead of - or in addition to - Power BI or Power Automate.
I am not using HootSuite myself so I'll need to give it a try (or try the Twitter homegrown tool some people have mentioned). The idea with a BI report is to answer questions such as:

what was the most popular tweet in the past week
what was the most popular tweet for the hashtag #MSFTViva
who are the top users tweeting about #MSFTViva
etc.

At least one benefit I see with the Power Platform is that it doesn't require to login to Twitter. It means that it might be more suitable to an enterprise environment, especially if different groups track different topics.
If you'd like to take a quick look at the Power BI report, I posted the one from last week. Maybe you would be able to tell quickly if HootSuite gives you similar information.

I worked with Twitter Connector in Power Apps and in Power Automate, but both Connections required a twitter user as -connection. What do you mean by "doesn't require to login to Twitter" ?

Sorry, my comment was about the Power BI report specifically. It uses a "developer token" to authenticate to the Twitter API, which is different from having a Twitter user account. I have posted more details with the template instructions.

💡💡💡 - thank you!

@sympmarc after reviewing the HootSuite offer, the analytics plan doesn't come cheap. So I wouldn't feed comfortable recommending it. On the other hand, a Power BI desktop template is free, and it's a good learning experience when you work with MSFT365
Thoughts? I'll keep looking for other Twitter apps.

@LuiseFreese @sympmarc I just posted a pull request that addresses some of the issues:

changed help example to replace PowerHelp
added MSFTViva
removed pnphelp

@PathToSharePoint - I hadn't looked at the contents of your PowerBI report when I made my comment above. You're right: third party tools which offer stats like that cost money. But isn't PowerBI itself costly?
Plus, in my mind, the use case for most people is to follow the hashtags on Twitter or LinkedIn or whatever so they can read what's going on. I don't think the "most popular hashtags" type of stats serve that purpose. Or am I missing something in your intent?
It does seem useful to check out the most popular tweets in retrospect. I wonder if focusing on that and making something available in the context of the docs is even possible.

@sympmarc thanks for the feedback! That's why I said I didn't want to force the tool on everybody, I want it to make sense.
To address some of your points:

Power BI Desktop is free, and some features of Power BI Service come for free with Microsoft 365. That's actually how I use it in this scenario. The twitter API is free for occasional use.
One of the features I advertise in my talk is that the report is actionable. When you find an interesting tweet you can click on the link which takes you to twitter. The report is meant to surface fresh tweets from the past week. Typical example: during Microsoft conferences, I run it at the end of the day to surface the main announcements. I posted about the last MS Ignite here. btw in the post, I mention a similar report from John White, but AFAIK the source for his is not available.

@sympmarc @LuiseFreese now that the immediate issues have been addressed, would it make sense to move this thread - or at least the part that is still relevant - to discussions?

yes good idea!

There hasn't been much progress on this thread in the past months.
To wrap this up, I would suggest to remove the reference to Power Automate from the article. I am not sure where it came from (could be me...). Personally I am not a fan of promoting Power Automate as copy/paste tool.
As for the notable twitter accounts, maybe that section should be removed too, rather than opening a can of worms. The official accounts listed in the post are already a good reference.

If you think there should be changes, feel free to do a PR.

I'll definitely do a PR. I just wanted to make sure we, and the OP in particular, are on the same  page. It's a community endeavor!

I'll definitely do a PR. I just wanted to make sure we, and the OP in particular, are on the same page. It's a community endeavor!

I'm fine with that, as already expressed here: https://github.com/MicrosoftDocs/microsoft-365-community/issues/399#issuecomment-785284583
:-)


It's unclear how to start spotifywebplayer

➜ pwd
/usr/bin/spotifywebplayer
➜ ls
get_prerequisites.sh  icons  js  libs  LICENSE  main.js  node_modules  node_modules_x64.zip  package.json  plugins  spotifywebplayer
➜ ./spotifywebplayer
./spotifywebplayer: 2: ./spotifywebplayer: Bad substitution
./spotifywebplayer: 5: ./spotifywebplayer: /usr/bin/spotifywebplayer: Permission denied
➜ cat spotifywebplayer
#!/bin/sh
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
OLDDIR=$(pwd)
cd $DIR
$DIR/libs/electron/spotifywebplayer $DIR/.
cd $OLDDIR%
➜ spotifywebplayer
zsh: permission denied: spotifywebplayer

It seems to me that nothing is installed into a default PATH for linux. Regardless, the script that appears to be the launcher (spotifywebplayer) fails to work. It apparently needs additional parameters. I'm not sure what those should be.
This was after installing via the 1.0.0 deb file.

run it as a bash script . /usr/bin/spotifywebplayer/spotifywebplayer or launch it with a gtk-launch gtk-launch spotifywebplayer.


bugfix: DeleteExecutor. buildBeforeImageSQL keyword checker by db type

Ⅰ. Describe what this PR did
keyword checker not distinguish db type
Ⅱ. Does this pull request fix one issue?

fixes #1754
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #1777 into develop will increase coverage by <.01%.
The diff coverage is 0%.

@@              Coverage Diff              @@
##             develop    #1777      +/-   ##
=============================================
+ Coverage      50.56%   50.57%   +<.01%
  Complexity      2166     2166
=============================================
  Files            414      414
  Lines          14196    14196
  Branches        1709     1709
=============================================
+ Hits            7178     7179       +1
  Misses          6328     6328
+ Partials         690      689       -1

Impacted Files
Coverage Δ
Complexity Δ

...va/io/seata/rm/datasource/exec/DeleteExecutor.java
0% <0%> (ø)
0 <0> (ø)
:arrow_down:

...server/store/file/FileTransactionStoreManager.java
53.94% <0%> (+0.32%)
27% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


[Contributions] Complete redesign of the application

I can create a new design for the application. I can even try to implement it. (But i'm not particularly good at programming)
will it be included in the application?

There's already one in #87, but feel free to create your own concept.

Yeah, as @itsWindows11 said, that's already being worked on, feel free to read the thread and provide suggestions :)


DStability input files with NaN values cannot be parsed

Originally reported by Thijs Damsma
Somehow DStability files created with the desktop application can have NaN values for certain fields (I didn’t create them and don’t know exactly how this happened, but I do need to parse them). If one tries to load these in geolib these then the input is rejected as NaN is not a valid value for those fields. I’m guessing NaN should be interpreted as “not set”, so this can easily be solved by ignoring all fields with nan values when parsing the input.

This should be fixed now in v0.1.9 by #26


Fix bug: IntegrityError cc_address violates not-null constraint

What's this Pull Request do?
Fix bug IntegrityError on field 'cc_address'
What has been changed?

[x] Change 'cc_address' to be nullable (null=True)

This code, fix bug #98.

Closing, explanation given in #98


SSHD needs network-online target when listenAddress is configured

Describe the bug
When your sshd configuration has a listenAddresses statement, the default target of network.target is no longer enough since there is a possible race when the ip address is not yet available, but sshd is already starting.
Excerpt from logging:
Dec 01 04:44:54 vb sshd[29345]: error: Bind to port 22 on x.x.x.250 failed: Cannot assign requested address.
Dec 01 04:44:55 vb network-addresses-eth0-start[29343]: adding address x.x.x.250/24... done

To Reproduce
Steps to reproduce the behavior:
Configure listenAddresses and reboot. Since this is a race, it is not always apparent.
I have only noticed this race personally during (automatic) system updates.
Expected behavior
SSHD should wait for the addresses to be available before trying to listen.
Additional context
Apparently SSHD refused to implement IP_FREEBIND (https://bugzilla.mindrot.org/show_bug.cgi?id=2512) which could have made this problem none-existent.
I believe this could be fixed by including:
systemd.services.sshd.wants = [ "network-online.target" ];
systemd.services.sshd.after = [ "network-online.target" ];

automatically, if (and only if) listenAddresses is used since this will not affect people binding to the default wildcard * address (but it brings other dependencies in the boot sequence and slows down the boot).
(Information taken from man 7 systemd.special

Looks like proposed change did not help, since last nights' auto-upgrade process failed again to start SSHD because ip was not available:
Dec 09 04:46:02 vb network-addresses-eth0-start[15292]: adding address x.x.x.252/24... done
Dec 09 04:46:02 vb network-addresses-eth0-start[15292]: adding address x.x.x.251/24... done
Dec 09 04:46:02 vb network-addresses-eth0-start[15292]: adding address x.x.x.250/24... done
Dec 09 04:46:02 vb network-addresses-eth0-start[15292]: adding address x.x.x.249/24... done
Dec 09 04:46:02 vb sshd[15288]: error: Bind to port 22 on x.x.x.250 failed: Cannot assign requested address.

@edolstra @aneeshusa

same issue here. Any workaround ?


Scratch image generation

What type of PR is this?

/kind feature
What this PR does / why we need it:
Adds a script to generate scratch images with different image IDs. These images can then be preloaded onto the kubemark nodes. Details in https://github.com/kubernetes/kubernetes/issues/90833.
Which issue(s) this PR fixes:

Part of https://github.com/kubernetes/kubernetes/issues/90833
Special notes for your reviewer:
Build and push to gcr after merging.
Does this PR introduce a user-facing change?:

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

/cc @mm4tt

/ok-to-test

Nice!
/lgtm
/approve

I pushed 20 scratch images to k8s-testimages


add run_constrained to avoid build

Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Noted in:

https://github.com/conda-forge/staged-recipes/pull/21501

Thanks!


Update https://github.com/allenjzhang/typespec-e2e-demo/blob/main/tsptemplate.json to add JS client settings

Update https://github.com/allenjzhang/typespec-e2e-demo/blob/main/tsptemplate.json to add JS client settings
Repro step:

Use the @next version of tsp compiler
tsp init https://raw.githubusercontent.com/allenjzhang/typespec-e2e-demo/refs/heads/main/tsptemplate.json

Expect:  JS client configs exist in tspconfig.
Actual:  There is no JS client settings.

Resolved by https://github.com/allenjzhang/typespec-e2e-demo/pull/62.   Thanks @qiaozha


Error on non-existing arguments/parameters

This patch adds __slots__ to all API classes that use setattr magic and kwargs for function parameters. Besides reducing memory and speeding up access, the main point of this change is that a typo when calling a function will result in an error, rather than silently setting non-existing properties.
In [1]: import ev3dev.ev3 as ev3
In [2]: m = ev3.MediumMotor()
In [3]: m.run_to_abs_pos(position_sp=72*20, speed_sd=500, stop_action='coast')
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-4-08bcba75fb47> in <module>()
----> 1 m.run_to_abs_pos(position_sp=72*20, speed_sd=500, stop_action='coast')

/home/robot/ev3dev-lang-python/ev3dev/core.py in run_to_abs_pos(self, **kwargs)
    799         """
    800         for key in kwargs:
--> 801             setattr(self, key, kwargs[key])
    802         self.command = self.COMMAND_RUN_TO_ABS_POS
    803

AttributeError: 'MediumMotor' object has no attribute 'speed_sd'

Currently the last line would just set the speed_sd property on the object, without doing anything, leaving it up to you to figure out why your motor went berserk or did nothing at all.

What is _bin_data_size, what is it used for, and what is that piece of code trying to do? Obviously a class with __slots__ has no __dict__, but it seems adding it to __slots__ and checking for None would have the same effect? The property is not used anywhere else in the project, so maybe it could also just be a local variable?

What is _bin_data_size, what is it used for, and what is that piece of code trying to do?

_bin_data_size stores the size of raw binary data to read from the sensor (see bin_data here).
In the code the field is used as a cache to store the value (and save an access to bin_data_format attribute). Initializing it with None should work as well.

If this makes property access faster it would be nice to see some timeit before and after. Could be a worthy addition to the release notes, since speed improvements help to cut latency on control loops.

yep I will give it a try

I'm not sure what a good test is to test performance of this change, TBH probably most time is spend talking to the kernel, compared to one dictionary lookup.
I fixed the data size, which was rather straightforward.
The helper classes require a bit more thought. __slots__ don't mix well with multiple inheritance. The internet consensus seems to be that if you run into this you're using __slots__ wrong. It is suggested that they are a memory optimisation, not a means to "freeze" classes. The "Pythonic" way that is suggested is to overwrite __setattr__, which would make things slower, if anything, though the impact is probably manageable.
As it stands now, using the helper classes would add an internal dict, allowing undefined attributes as before.

I think this one needs some more testing. I cannot pinpoint what is wrong but when using this patch my robot failed to solve the rubiks cube three times in a row, without this patch it can solve it everytime.  All motors look like they are rotating the correct amount (the cube would get jammed up otherwise) but I suspect one is turning in the wrong direction in some scenario.

Weird. No errors? (or things that swallow errors) If the robot is deterministic, I suppose you could use the same scramble and see where it goes wrong. Or just plain old printf debugging.Ik might be able to do some more testing, but simple things seemed to work and without knowing more it's hard to know where to look.Is this robot of yours one I can reproduce with my own ev3 (software and instructions available), or a custom monster with tons of extra parts?

Is this robot of yours one I can reproduce with my own ev3 (software and instructions available), or a custom monster with tons of extra parts?

This is not my robot, but I believe its built according to these instructions: http://mindcuber.com/mindcub3r/mindcub3r.html.
And the program is here: https://github.com/rhempel/ev3dev-lang-python/tree/develop/demo/MINDCUB3R

MINDCUBER is a good way to test, a lot of things have to be perfect for it to solve the cube.  I'm actually using my own cube solver now, if you have a 42009 (the big crane) then you can build it.  I need to put together instructions though.
Let me do this, I can put the cube back in the same scrambled state and record a video of it being solved with and without your patch.  Then I can compare the two videos side by side and see where it is behaving differently. That should help narrow it down a bit.

Ignore what I said, I suspect I have an error on my end.

A simple performance test shows there is a bit of improvement, or at least it is definitely not worse:
Before
>>> import timeit
>>> timeit.repeat('s.proximity', 'from ev3dev.ev3 import InfraredSensor; s = InfraredSensor()', number=100)
[4.144548124999972, 3.950399667000056, 4.128440291999993]
>>> timeit.repeat('s.proximity', 'from ev3dev.ev3 import InfraredSensor; s = InfraredSensor()', number=100)
[3.9438115419999917, 4.096679416999962, 3.8801820420000013]
>>>

After
>>> import timeit
>>> timeit.repeat('s.proximity', 'from ev3dev.ev3 import InfraredSensor; s = InfraredSensor()', number=100)
[3.8830312090000234, 4.003896959000031, 3.78919083400001]
>>> timeit.repeat('s.proximity', 'from ev3dev.ev3 import InfraredSensor; s = InfraredSensor()', number=100)
[3.8567800419999685, 3.932827876000033, 3.8972169590000476]
>>>

But I think the main idea here was to help users by catching semantic errors early.

Thanks!

Awesome. Still curious what happened on @dwalton76 's end though.

I have a bug where I sometimes assign the wrong color to a cube square based on the RGB values. In a nutshell you have 54 RGB tuples and from that you have to assign each square to be one of the six colors of the Rubik's cube. I had this fairly rock solid but have been working on this code to make it support 4x4x4, 5x5x5, etc cubes and must have introduced a bug because when I took a video of it solving with your patch in place I noticed that it got some of the color assignments wrong.

In another run I was able to solve a cube with your patch applied so the motor movements seem to be fine.


[Enhancement] Compatible with  GlueCatalog  table that without StorageDescriptor for iceberg table

What type of PR is this：

[ ] BugFix
[ ] Feature
[x] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[ ] 2.4
[ ] 2.3

[FE PR Coverage Check]
:disappointed: fail : 0 / 10 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/connector/hive/glue/util/HiveTableValidator.java
0
7
00.00%
[43, 44, 45, 46, 47, 49, 50]

:large_blue_circle:
com/starrocks/connector/hive/glue/converters/CatalogToHiveConverter.java
0
3
00.00%
[160, 161, 162]

[FE PR Coverage Check]
:disappointed: fail : 0 / 10 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/connector/hive/glue/util/HiveTableValidator.java
0
8
00.00%
[43, 44, 45, 47, 48, 60, 61, 62]

:large_blue_circle:
com/starrocks/connector/hive/glue/converters/CatalogToHiveConverter.java
0
2
00.00%
[159, 160]

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


Add "Hello world" in io programming language.

I would love to take up this issue, can you pleas assign to this me

helloworld.io has been already created with proper code and added to readme file. What can I do? Please let me know.


typescriptlang.org redirects (no www) generally do not go to the appropriate page

Note: This repo requests issues be reserved for critical issues and PRs be entered for non-critical issues. For reasons explained below, this problem cannot be addressed with a PR.
Page URL: https://typescriptlang.org/docs/handbook/intro.html
Issue: Earlier tonight I filed an issue about some problems me and some friends found with redirects on typescriptlang.org. Our attempts to figure out what was happening were made more difficult by the fact that typescriptlang.org, as opposed to www.typescriptlang.org, does not have full redirects set up to the correct site (www.typescriptlang.org). For example, consider the URL https://typescriptlang.org/docs/handbook/intro.html. This redirects to the www.typescriptlang.org front page. The single address https://typescriptlang.org/docs appears to have been special-cased to correctly redirect to its corresponding www version, but no other page on the site does this; all other pages, in my testing, send to the typescriptlang.org front page.
This problem is exacerbated by an unfortunate decision on the part of Chrome (and so possibly some Chrome derivatives— I haven't checked) to start hiding the www. trailer on URLs. So for example if you look at https://typescriptlang.org/docs/handbook/intro.html in Chrome, your URL bar will say typescriptlang.org/docs/handbook/2/everyday-types.html, a URL which does not work (redirects to front page). While attempting to navigate the typescriptlang site, I found myself repeatedly typing URLs from my desktop (running Chrome) to my laptop (running Firefox), and being mysteriously redirected to the typescriptlang.org front page instead. It took me some time to figure out why this was happening. :(
Expected behavior: URLs on the typescriptlang.org domain should redirect to their exact counterparts on www.typescriptlang.org, not to the front page.
Could this have been a PR? Although as an external dev I am not in a good position to fix this particular type of problem as a PR, I did poke at this repo this evening and found there is in fact a file handling redirects in the TypeScript-Website source. However it makes no mention of the www/no-www split at all. This makes me strongly suspect that no-www->www redirect is in some piece of configuration housed outside this repo, and a PR cannot be attempted.

👍 it works!


Add the possibility of translations by default

Hi!
I think it would be valuable to add default translations. Maybe just start with one language in english, but then the user will have an easier job including more locales themselves.
Other than that; great template!

@Voldemorten Thanks for the suggestion and kind comment!
Localization/i18n is definitely something I'd eventually want to incorporate into the template. As I have not worked with any Sanity plugins or have tried to implement myself, I'd ideally want to try a solution first before adding to the template.
With that, my current stance is: Localization is left to the adopter to implement, as there are a number of community plugins available


[BigDecimal] to_s should be encoded as US-ASCII

Ruby ticket: https://bugs.ruby-lang.org/issues/17011
BigDecimal change: https://github.com/ruby/bigdecimal/pull/160
The spec is mostly taken from Integer and Float specs.
That BigDecimal wasn't pulled in ruby/ruby yet, so I'm unsure what the process should be.

Thanks for the specs!
I'll ask how to apply/cherry-pick that fix in CRuby's master.
We should wait until that fix is in CRuby (so that the spec will pass when synchronized in CRuby).

Ah, I missed that https://github.com/ruby/bigdecimal/pull/160 is already in ruby/ruby master since it was merged in 2019 (I thought it was a recent PR).

Yes. But surprisingly it didn't make it to 2.7

Commit in ruby/ruby is https://github.com/ruby/ruby/commit/6a826eb4b08484cb3b6279da905f5b9e03e0df5f

Full details that we don't see on GitHub:
$ git log -p --format=fuller ext/bigdecimal
...
commit 6a826eb4b08484cb3b6279da905f5b9e03e0df5f
Author:     Kenta Murata<EMAIL_ADDRESS>AuthorDate: Mon Dec 23 11:07:23 2019 +0900
Commit:     Nobuyoshi Nakada<EMAIL_ADDRESS>CommitDate: Mon Jul 6 01:15:47 2020 +0900

Oh good catch. I was starting to think I was getting crazy as I was certain the fix wasn't pulled last time I checked.