gPTP sync issue fixes

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f248345). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #12070   +/-   ##
=========================================
  Coverage          ?   48.05%
=========================================
  Files             ?      281
  Lines             ?    43416
  Branches          ?    10406
=========================================
  Hits              ?    20864
  Misses            ?    18403
  Partials          ?     4149

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 f248345...72f236b. Read the comment docs.


Added ability to set expiration on Redis keys

Added the ability to specify KeyExpiry on RedisManager, this can also be set on the passed in config file. KeyExpiry is a TimeSpan and will let Redis automatically remove old keys once the expiry is breached.


Bot

A bot always joins whenever I load up the extension, and it keeps spamming Izarus is king or whatever, and it just got annoying.

um how to use the bot

@itsLegndzz ... that sounds unrelated to this bot, because nowhere in the code does it ever send messages called "lazarus is king"...
I'd suggest looking through your extensions, and removing any that look suspicious


ERROR extracting IXI HH Data from t1.tar

System : Ubuntu Server 18.04
Python : 2.7
All of prerequisites installed.

While running /data/download_IXI_HH.py, the script throws
Extracting IXI HH data from t2.tar.
Extracting IXI HH data from mra.tar.
Extracting IXI HH data from pd.tar.
Extracting IXI HH data from t1.tar.
[u'Table', u'Ethnicity', u'Marital Status', u'Occupation', u'Qualification', u'Study Date']
download_IXI_HH.py:139: FutureWarning: Method .as_matrix will be removed in a future version. Use .values instead.
  na_values=[]).as_matrix()
Resampling IXI012
Traceback (most recent call last):
  File "download_IXI_HH.py", line 150, in <module>
    t1 = sitk.ReadImage(t1_fn)
  File "/home/bijayregmi/.local/lib/python2.7/site-packages/SimpleITK/SimpleITK.py", line 8876, in ReadImage
    return _SimpleITK.ReadImage(*args)
NotImplementedError: Wrong number or type of arguments for overloaded function 'ReadImage'.
  Possible C/C++ prototypes are:
    itk::simple::ReadImage(std::vector< std::string,std::allocator< std::string > > const &,itk::simple::PixelIDValueEnum,std::string const &)
    itk::simple::ReadImage(std::string const &,itk::simple::PixelIDValueEnum,std::string const &)

Please read the note in the README file. In accordance with scipy and numpy, we are not supporting python 2.x anymore. I am pretty certain this is due to some issue with string parsing. Could you run this in a python3 environment and confirm this problem?

Script runs fine on python3. Indeed a problem in python 2.x environment.

Thanks for confirming!


The Style/SpecialGlobalVars cop does not always auto-correct the code properly

The Style/SpecialGlobalVars cop does not always auto-correct the code properly, for example, it replaces the $/ global by the $INPUT_RECORD_SEPARATOR one but it does not includes the English module, so it basically breaks the code (rubocop version 0.35.1).
To reproduce:
$ echo 'p $/' > test.rb

$ ruby test.rb
"\n"

$ rubocop --auto-correct --only="Style/SpecialGlobalVars" --format=simple test.rb
== test.rb ==
C:  1:  3: [Corrected] Prefer $INPUT_RECORD_SEPARATOR or $RS from the stdlib 'English' module over $/.

1 file inspected, 1 offense detected, 1 offense corrected

$ cat test.rb
p $INPUT_RECORD_SEPARATOR

$ ruby test.rb
nil

this has been discussed recently: https://github.com/bbatsov/rubocop/issues/2496#issuecomment-164114650

This is regrettable, but there is not much we can do, for reasons already discussed. Maintainers, please close this issue.

Erm, I'm not really sure to follow ...
If this cop is known to produce broken auto-corrected code, why not disable the auto-correction (by default) ?


"dvara" set up for my mongoDB help needed i am begging for help

Sorry for posting here i am in deep trouble. and i don't have your email ID
I want your help in "dvara" set up for my mongoDB instance.  as per the git and google i can't find tutorial for dvara as this is not popular. can you please provide some steps to set up dvara on AWS (i am not able to run). i am new to go and my app is falling and not wokring at all. i am begging you for help as i am paying for server more then i am earning.
I am running Parse server open source for my app. and i have lot of request in mongo DB as my app is like instaragaram to lot of images video and Mongo DB request is making my app slow even my app is not wokring as its taking so much merory. I tried mongodb sharding but its not wokring for me and my app is not responding for almost all query.
Right now I am runing my mongo DB on R4.2xlarge server with replica set (as sharding not helpfull for me app). total cost of AWS i am paying more then 1200$ which i can't effort.
Please please help i only have hope from you to help it will not take 10-15 min for you. please help !!!!!!!
Please provide your email ID
My email ID is :-<EMAIL_ADDRESS>

Hey, sorry to hear you're not having success with dvara. As it says in the readme Facebook isn't using it anymore either. Additionally I no longer work there anymore either.
If your application is suffering from Mongo DB slowness then dvara isn't going to fix that. It simply serves as a connection pooling proxy. I would suggest trying to optimize your mongo use rather than try to use dvara to fix it.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/263 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit bf8aa51:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/index.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/sql-database-engine.png
:white_check_mark:Succeeded

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Offline availability

Goal is to know if this is possible or not.
If yes: how?
If not: why not?
To document.
If not possible, what are alternative solutions?
I.e. create free WiFi points.

Actually, after the refactoring of #200, everything works offline.
Visitors have to open a specific Region-page at least once.
After the visit all sheet-data is stored locally per region, so multiple regions can be stored for offline use. (Up to max 8 regions? Depends on use of Q&As. Can be configured differently.)
After 7 days the data is considered 'too old'; This can be configured differently too.
Images/icons are not all (pre-)loaded, so some 'holes' will show during offline use.


Invalid format: Missing XING header and insufficient MPEG frames

While uploading my collection with:
gms up -u somename -v --debug /srv/library/music
I encounter with the following error, while I used the
Traceback (most recent call last):
   File "/usr/local/lib/venv.google-music-script/bin/gms", line 10, in <module>
      sys.exit(run())
  File "/usr/local/lib/venv.google-music-script/lib/python3.7/site-packages/google_music_scripts/cli.py", line 920, in run
    DISPATCH[command](args)
  File "/usr/local/lib/venv.google-music-script/lib/python3.7/site-packages/google_music_scripts/commands.py", line 364, in do_upload
    if generate_client_id(song) not in google_client_ids:
  File "/usr/local/lib/venv.google-music-script/lib/python3.7/site-packages/google_music_proto/musicmanager/utils.py", line 18, in generate_client_id
    song = audio_metadata.load(song)
  File "/usr/local/lib/venv.google-music-script/lib/python3.7/site-packages/audio_metadata/api.py", line 82, in load
    return parser_cls.load(fileobj)
  File "/usr/local/lib/venv.google-music-script/lib/python3.7/site-packages/audio_metadata/formats/mp3.py", line 519, in load
    self.streaminfo = MP3StreamInfo.load(self._obj)
  File "/usr/local/lib/venv.google-music-script/lib/python3.7/site-packages/audio_metadata/formats/mp3.py", line 406, in load
    raise InvalidFormat("Missing XING header and insufficient MPEG frames.")
audio_metadata.exceptions.InvalidFormat: Missing XING header and insufficient MPEG frames

Although "verbose" and "debug" gms options have been activated, not much additional info is reported ...
Here is my config in a Python 3.7 with a virtualenv:
Package                Version
---------------------- -----------
ansimarkup             1.4.0
appdirs                1.4.3
attrs                  18.2.0
audio-metadata         0.4.0
better-exceptions-fork 0.2.1.post6
bidict                 0.17.5
bitstruct              6.0.0
certifi                2019.3.9
chardet                3.0.4
colorama               0.4.1
google-music           3.0.1
google-music-proto     2.4.0
google-music-scripts   4.0.1
google-music-utils     2.1.0
idna                   2.8
loguru                 0.2.5
marshmallow            2.19.2
more-itertools         4.3.0
multidict              4.5.2
natsort                6.0.0
oauthlib               3.0.1
pendulum               2.0.4
pip                    19.0.3
pprintpp               0.4.0
protobuf               3.7.1
Pygments               2.4.0
python-dateutil        2.8.0
pytzdata               2019.1
requests               2.21.0
requests-oauthlib      1.2.0
setuptools             40.8.0
six                    1.12.0
tenacity               5.0.4
tomlkit                0.5.3
urllib3                1.24.3
wrapt                  1.11.1

Unable to find so far to find the file generating this error ...

Transferred to audio-metadata repo.
Yeah, I got sidetracked by an injury before I got to release some logging changes/additions to the dependency stack that would help identify the file. I'm back to developing, just having gotten to releasing those changes yet.
For now, you can run this script in a directory to recursively check for audio files that fail to load with audio-metadata.
Feel free to post link/files here or by email so I can check them out.

Seems the issue is on my side, one of my file appears to be broken, the file size is nearly null (4k) ...
I've altered google_music_scripts/commands.py in such way to ignore failing files:
...
20          import audio_metadata
...

362         existing_songs = []
363         google_client_ids = {song.get('clientId', '') for song in get_google_songs(mc)}
364         for song in local_songs:
365             try:
366                 if generate_client_id(song) not in google_client_ids:
367                     missing_songs.append(song)
368                 else:
369                     existing_songs.append(song)
370             except audio_metadata.exceptions.InvalidFormat:
371                 logger.info("%s is not a valid file" %  song)

362         existing_songs = []
363         google_client_ids = {song.get('clientId', '') for song in get_google_songs(mc)}
364         for song in local_songs:
365             try:
366                 if generate_client_id(song) not in google_client_ids:
367                     missing_songs.append(song)
368                 else:
369                     existing_songs.append(song)
370             except audio_metadata.exceptions.InvalidFormat:
371                 logger.info("%s is not a valid file" %  song)

....
....

Well, that doesn't necessarily mean it's broken. I'd like to take a look at it anyway just to check it out.

Here is the file...
Mar 14 mai 2019, à 11:11, thebigmunch a écrit :

Well, that doesn't necessarily mean it's broken. I'd like to take a look at it anyway just to check it out.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/thebigmunch/audio-metadata/issues/5?email_source=notifications&email_token=ACAYTLN6T7LGMNHGU4TNTP3PVJ65DA5CNFSM4HMQSGYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVK3ETY#issuecomment-492155471, or mute the thread https://github.com/notifications/unsubscribe-auth/ACAYTLOHRSMI26W6SSC2GPTPVJ65DANCNFSM4HMQSGYA.

If you tried to attach it to the issue comment through email, I don't believe that works. You'd have to attach it through the web interface or email it to me directly at<EMAIL_ADDRESS>

The file may be broken in that the song the metadata points to is supposed to be over 3 minutes long, not a fraction of a second, but it's actually a valid MP3 file. It only has 2 MPEG frames, though, which is below the threshold I've set for when an MP3 doesn't have a Xing header. But this file really should be supported by audio-metadata, so I'm going to work on changing up the code a bit to cover this kind of case. So, it should just work in a future release.


Docker meet Firewall comments

2017-08-15-docker-firewall.md
Wow! What a great post! I'm new to Docker, so I wondered why a docker install broke my ethernet bridge on my Debian Jesse server. This explained it all and helped me solve it.
I would suggest a couple of edits for clarity:

You say "Don’t change the FORWARD chain to ACCEPT from DROP. There is no need any more."
and I agree. But in /etc/iptables.conf, you begin with this:*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]  # <== This should be DROP, no?
:OUTPUT ACCEPT [0:0]
:FILTERS - [0:0]
:DOCKER-USER - [0:0]

This may be distribution / OS dependent, but I don't find any --now option for this command:And enable it:
$ sudo systemctl enable --now iptables

The systemd man page (what I find) says to run start as a separate command:$ sudo systemctl enable iptables
$ sudo systemctl start iptables    # start it now

I'm familiar with iptables, but maybe not an expert ;-) - I don't understand why the <IP_ADDRESS> rule
has no target? My understanding is that the rule would be ignored (but my understanding of the
masquerading and extension stuff is limited ...)-A FILTERS -m state --state ESTABLISHED,RELATED -j ACCEPT
-A FILTERS -m state --state NEW -s <IP_ADDRESS>/32
-A FILTERS -m state --state NEW -m tcp -p tcp --dport 22 -j ACCEPT

Thanks again for a great post :-)

Thank you for the feedback! And double thanks for being so polite about my silly mistakes, its a rare treat these days.
Hopefully I've fixed the errors in the examples now. I guess --now is newer than Jessie and older than Xenial. I think it's in Stretch. I have got both ways of doing it now.
Thanks again!


Not working with cordova IOS app

I just tested the library with the cordova based IOS app and it is not working for me, it is going to the error section and when I am trying to check the error by running  alert(JSON.stringify(err)) then I am getting blank object like this {}
my code is as follow
 blobUtil.imgSrcToBlob(imageUrl, "image/jpg" ,  'Anonymous').then(function (image) {
                                        alert("success")
                                    }).catch(function (err) {
                                    alert(JSON.stringify(err))
                                    });

Hi, you actually can’t stringify an error object; you need to just console.log(err) and that’s the easiest way to see what the error is. Then you can connect to it using Safari Dev Tools and see what exactly the error is.
Based on your code, it’s hard to say what’s wrong; it could be literally anything, but most likely its that the image doesn’t exist or the server doesn’t support CORS.

+1
Trying with file:///

its an FB profile image where "https://static.xx.fbcdn.net/rsrc.php/v2/yo/r/UlIqmHJn-SK.gif" where the response headers already obey the CORS, it was working in android app and normal web but not in IOS hybrid app

Can you provide a test case to reproduce? I think the issue may be that the URL is file:// and Safari UIWebView has some strange bugs when you serve things over file:// but it's hard to tell from the code and description provided.


[Bug]: GoogleDemo.ipynb notebook seems to be requiring OpenAI API key

Bug Description
Hi,
I'm following the demo: https://github.com/run-llama/llama_index/blob/2f2d5a4735dd82f8acd2f630c745758e92202be2/docs/docs/examples/managed/GoogleDemo.ipynb
I have configured service account auth, enabled the Google API, downloaded the paul graham doc, but when I get to the basic querying section I get the following error:
ValueError:

Could not load OpenAI model. If you intended to use OpenAI, please check your OPENAI_API_KEY.
Original error:
No API key found for OpenAI.
Please set either the OPENAI_API_KEY environment variable or openai.api_key prior to initialization.
API keys can be found or created at https://platform.openai.com/account/api-keys
To disable the LLM entirely, set llm=None.

I was under the impression that the LLM in this case would be Google's Gemini and the necessary credentials were already set by passing the Service Account details to set_google_config(auth_credentials=credentials)
Version
llama_index-0.10.28
Steps to Reproduce
Follow the instructions on the notebook
Relevant Logs/Tracbacks
---------------------------------------------------------------------------
ValueError                                Traceback (most recent call last)
/usr/local/lib/python3.10/dist-packages/llama_index/core/llms/utils.py in resolve_llm(llm, callback_manager)
     40             llm = OpenAI()
---> 41             validate_openai_api_key(llm.api_key)
     42         except ImportError:

6 frames
ValueError: No API key found for OpenAI.
Please set either the OPENAI_API_KEY environment variable or openai.api_key prior to initialization.
API keys can be found or created at https://platform.openai.com/account/api-keys

During handling of the above exception, another exception occurred:

ValueError                                Traceback (most recent call last)
/usr/local/lib/python3.10/dist-packages/llama_index/core/llms/utils.py in resolve_llm(llm, callback_manager)
     46             )
     47         except ValueError as e:
---> 48             raise ValueError(
     49                 "\n******\n"
     50                 "Could not load OpenAI model. "

ValueError:
******
Could not load OpenAI model. If you intended to use OpenAI, please check your OPENAI_API_KEY.
Original error:
No API key found for OpenAI.
Please set either the OPENAI_API_KEY environment variable or openai.api_key prior to initialization.
API keys can be found or created at https://platform.openai.com/account/api-keys

To disable the LLM entirely, set llm=None.
******

It still needs an LLM to do response synthesis. It doesn't do that for you, and instead defaults to the global settings
You should define an LLM, and either change the global defaults
from llama_index.core import Settings
Settings.llm = llm

Or pass it in (I'm assuming its this line of code, although you didn't specify)
query_engine = index.as_query_engine(llm=llm)

Seems like an issue with the response coming from googles API 😞


Line Forward Model

[x] Implement a wrapper for Mike Line's forward model generator.

[x] Exposing basic least squares fitting of forward models to data

[ ] Documentation  and Example notebook

Fixes #4 and does some work on #1
Will address docs content and example notebook in another PR.


Feat/access denied error

was this attempted to be upstreamed? would be nice to not use the replace tag

Hi @tac0turtle , you mean upstreamed to github.com/cosmos/keyring, right ?

no 99designs

ok, we'll do the PR but doesn't seem to be a very active repo

PR made https://github.com/99designs/keyring/pull/119


Date field i18n issue in nested attributes

class Object < ActiveRecord::Base
has_many :things, :as => :thingable, :dependent => :destroy
accepts_nested_attributes_for :things
end
class Thing < ActiveRecord::Base
belongs_to :thingable, :polymorphic => true
validate _presence_of :date_of_thing
end
In Object edit nested form ... date_of_thing won't save !
But in Thing edit it will

it has something to do with format... I use french format
30 decembre 2012 is not saving
while 01 decembre 2012 is saving
30 12 2012 not ok
01 12 2012 ok
Maybe it's my fault with the i18n of date format ???

actually it does not read french...FM People
If I enter "25 Février 2012" it does not save, If I enter "February,25 2012" it does
BUT only in nested ressources...no problem when using it directly !

JS issue?
Do you have errors in the console?

I clearly identified the problem : french (as usual)
Not kidding, it's an utf8 problem I think. février, décembre, août won't save when all others yes. Of course when entering XX/XX/XX it's YYYY/MM/DD format that is taken

again strange thing is :
accent is not a problem when creatin object directly but in nested form as has_many polymorphic object

Got it.
Fields::DateTime#parse_input middleman isn't called for nested forms before sending to ActiveRecord.
And AR doesn't know about août at all, since it simply relies on ruby's DateTime#parse

Great ! you're good !
But what's middleman (I though it was for static website) ? Do I have something to do , or will you add the call within RA and commit soon ?

function acting as a man in the middle.
It's not that simple. It's a design failure.
2 ways to solve it:

recursively go down every nested attributes and treat them with #parse_input (ugly)
remove the #parse_input pattern and refactor datetime widgets (lot of work)

parse_input is only used for dates.
I can't see the easy way.

how about configuring datepicker ?
http://stackoverflow.com/questions/7181220/rails-3-jquery-date-picker-date-not-saving-to-database

Ok, it's fixed.
I'll push to master tmrw (I removed a correlated hack for serialized attributes that I need to replace)
I pushed it to the fix-1013 branch if you need it now on your fork.
About your idea, do you mean filling an hidden field with the real input name?
You'll need to refresh this field each time a manual change is done in the input field (not through calendar)

That was just the most intersting post I found to try to help you a little...I can't really help myself. You and your team are doing a great job with rails admin. Bravo !


First Experimental Version

Finally got something useful done.
@amiralies I'd like to merge this and have a quick chat with you regarding how we should continue with the vim integration

Nice work! I've tested this with cristiano's fork of reason-language-server and everything seemed to be fine, I'm going to merge this into master. and feel free to send me a DM on discourse or whatever platform you like.


model events only are trigged in single execution

I am making tests for my laravel app and, I used to run file per file my features, and it work's.
the problem hapens when I execute all the feature files for a general review of mi app
and this looks like:
Feature: Create materials

    In order to manage the Warehouse
    As a Warehouse admin
    I want to create new materials to the warehouse

  Scenario:                                                # features/CreateMaterialsFeature.feature:7
    And I have a group "Accesorios" with code 'ACC'        # FeatureContext::iHaveAGroupWithCode()
    And I am on "warehouse/materials/create"               # FeatureContext::visit()
    ...
    Then I should be on "warehouse/materials"              # FeatureContext::assertPageAddress()
    And I should see "Aislador Flow System 00-00"          # FeatureContext::assertPageContainsText()
    And I should see "ACC-0001"                            # FeatureContext::assertPageContainsText()
      The text "ACC-0001" was not found anywhere in the text of the current page. (Behat\Mink\Exception\ResponseTextException)

when I go to my file for replicate the error and review them, mi test is ok.
this happen because I use a model trigger to designate the code ACC-0001 and this is only triggered in the single file environment of behat

I'm sorry Behat has nothing to do with Laravel. You probably should point your question to:
https://github.com/laracasts/Behat-Laravel-Extension


HDDS-6540. Add a Cache for per-disk DB handles.

What changes were proposed in this pull request?
A new Cache for per-disk db handles after rocksdb-merge.
Originally we have the ContainerCache for per-container db handles.
And we should have a new DatanodeStoreCache for per-disk db handles which should be relatively small.
We could choose whether to use the  DatanodeStoreCache or the ContainerCache according to the schema version in BlockUtils.getDB().
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-6540
How was this patch tested?
A new UT.

Hi @ChenSammi @nandakumar131 PTAL~

The patch LGTM, + 1.
Thanks @guihecheng for the contribution.


fmt.doc: formatting functions will round the number according to the specified precision

Close the PR because factors like system architecture, etc can impact the behavior outside of the control of the  fmt package:
more details on system's architecture:
On x86 processors, the default rounding mode is typically "round to nearest, ties to even."
On some ARM processors, the default rounding mode may be "round towards zero,"
...


First Run Issue

I created a project of blazor wasm using visual studio 2022 and found issues. The logs of the console are added in the log file attached to this issue.
Looking forward to knowing how can I fix this issue
LOG FILE

Is this the code straight from the github repository, or did you use the template?
You sure you didn't change/add anything?
Looking at the log, it seems like you must have a "System" namespace defined somewhere that's conflicting with the global system namespace...

@fretje thanks for having looked at the issue. I created straight away from the template of visual studio.

#170 issue fixed.


GetPictureCells returns an empty result

Description

Steps to reproduce the issue:
	f, _ := excelize.OpenFile("2.xlsx")
	defer f.Close()
	cell, err := f.GetPictureCells("sheet")
	fmt.Println(cell, err)
	pics, err := f.GetPictures("sheet", "A2")
	fmt.Println(pics, err)

Describe the results you received:
The function GetPictureCells returns an empty result.
Describe the results you expected:
There is a picture at cell A2.
Output of go version:
GOVERSION='go1.22.2'

Excelize version or commit ID:
github.com/xuri/excelize/v2 v2.8.1

Environment details (OS, Microsoft Excel™ version, physical, etc.):
xlsx:
2.xlsx

Thanks for your issue. I have fixed this issue. Please upgrade to the master branch code by go get github.com/xuri/excelize/v2@master. This patch will be released in the next version.

Thanks for your issue. I have fixed this issue. Please upgrade to the master branch code by go get -u github.com/xuri/excelize/v2@master. This patch will be released in the next version.

Thanks for your issue. I have fixed this issue. Please upgrade to the master branch code by go get -u github.com/xuri/excelize/v2@master. This patch will be released in the next version.


Autocomplete: when option is too large crop the chip's text

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have read the contributing guidelines

Describe the issue
when there is an autocomplete option that is too large, the chip can end up being larger than the autocomplete itself.
To fix this, there should be a maximum character limit to crop the chip's text, adding ... to the end.

Reduced test cases
No response
What operating system(s) are you seeing the problem on?
No response
What browser(s) are you seeing the problem on?
No response
What is the issue regarding ?
@trimble-oss/modus-web-components
What version of npm package are you using ?
No response
Priority
Medium
What product/project are you using Modus Components for ?
Trimble Inspections
What is your team/division name ?
Camaleão/Transportation
Are you willing to contribute ?
Maybe
Are you using Modus Web Components in production ?
No response

@mitch-trimble could you please review this issue and provide your recommendations?
https://modus-web-components.trimble.com/?path=/docs/components-chip--default
https://modus-web-components.trimble.com/?path=/docs/user-inputs-autocomplete--multiple-selection


Missing new materials in the classification

@stefanpauliuk I am not sure if the classification master on Dropbox is the one you used for producing the latest set of results, but we noted that there is a mismatch for some new materials.
Glass and Insulation are listed in Material_Production_i2, but not in Engineering_Materials_m2.
We have already collected data in 4_PE_ProcessExtensions_Materials and in 4_EI_ProcessEnergyIntensity, and linked materials to processes in 4_SHA_MaterialsTechnologyShare, so they would be ready to be used.
On the contrary, Bricks are listed in Engineering_Materials_m2, but not in Material_Production_i2, so they are in the stock but do not have any production impact. Data in 4_PE_ProcessExtensions_Materials, 4_EI_ProcessEnergyIntensity and 4_SHA_MaterialsTechnologyShare are also missing.
New non-residential archetypes have non-zero brick intensity, so their contribution is missing.
Also, if I remember correctly, residential archetypes (and maybe non-res too) had some glass and insulation, which were aggregated to Other materials. There is room for refinement here, assigning them in BuildME to their corresponding material class.

Hi @CarrerF Indeed, these materials haven't been considered so far.
I propose to add the following (see curent Master Classification file):
add to Engineering_Materials_m2:
glass
insulation material
add to Material_Production_i2:
production of bricks from clay
So these can now be selected in the config file and existing data can be used!
Different type of insulation material (fibre-based, plastic-based, rock wool) can be implemented via their different impacts (MF, GHG, energy consumption in production).
still to be done:

Add energy requirements and footprints of bricks --> I propose that I do this over the weekend!

Check the "Other materials" group of the building archetypes. Here, I have an email from Niko that sais that it can be done in principle, and that Kamila knows how to operate the code.
The material aggregation settings are listed here:
https://github.com/nheeren/BuildME/blob/0e218b5a66d721da1e1e6b3b2d35d67e1fb15c5f/BuildME/settings.py#L553
Glass and insulation are crucial for the buildings energy balance and should be included I think. I'll forward you the email (in German though), and I propose that you take a closer look at it if you wantto focus on these materials!

Brick production energy use and material footprint is now included in
\Dropbox\RECC_v2_5_v2_6\data\CURRENT_V2_5
4_EI_ProcessEnergyIntensity_V3.2
4_PE_ProcessExtensions_Materials_V1.2
See also the updated master classification as described above:
RECC_Classifications_Master_V2.0

Thanks Stefan!
@LolaRousseau might be useful for you as well

Great, thanks @stefanpauliuk and @CarrerF! I plan to include the materials in the version of ODYM-RECC that I have, very nice to have the updated files to look at :)


Remove ignition

🎉 New feature
Removes ignition
Checklist

[ ] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

the ignition_physics-ci-pr_any-ubuntu_auto-amd64 build is using 20.04 and should be ignored

the windows test failure are pre-existing on the main branch:

https://build.osrfoundation.org/job/ign_physics-ci-win/189/


[MINOR] Fix typo,'intance' corrected to 'instance'

Tips

Thank you very much for contributing to Apache Hudi.
Please review https://hudi.apache.org/contribute/how-to-contribute before opening a pull request.

What is the purpose of the pull request
Fix typo,'intance' corrected to 'instance'
Brief change log
(for example:)

Fix typo,'intance' corrected to 'instance'

Verify this pull request
(Please pick either of the following options)
This pull request is a trivial rework / code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end.
Added HoodieClientWriteTest to verify the change.
Manually verified the change by running a job locally.

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

@hudi-bot run azure

@hudi-bot run azure


Order doesn't quite work for > 10 bubbles

Hi Dave, great work btw.
Trying to use the Bubbles viz. If I have 10 parent bubbles (each with nested bubbles), I can order the parent bubbles from large to small (vice versa). But once I hit 11 and up, they do not order as desired. Any idea why?
Thanks.

Interesting, can you post a code snippit? Maybe a jsfiddle?

Hmm...I can't seem to replicate that. :(
But the issue now exists for less than 10.
`  var view3 = [
{"count":19, "name":"f", "group":"A"},
{"count":1, "name":"c", "group":"B"},
{"count":10, "name":"b", "group":"B"},
{"count":67, "name":"f", "group":"B"},
{"count":8, "name":"a", "group":"B"},
{"count":5, "name":"f", "group":"C"},
{"count":4, "name":"f", "group":"D"},
{"count":1, "name":"a", "group":"D"},
{"count":1, "name":"a", "group":"E"}]
var visualization = d3plus.viz()
    .container("#viz")     // container DIV to hold the visualization
    .data(view3)     // data to use with the visualization
    .type("bubbles")       // visualization type
    .id(["group","name"]) // nesting keys
    .depth(1)              // 0-based depth
    .size("count") // key name to size bubbles
	.order({"sort":"desc"})
    .color("name") // color by each group
    .draw()                // finally, draw the visualization!`

I want to sort the biggest bubble to smallest. But the order doesn't work.

Ok, here's why.
When I set the nesting ids  as ["group","name"] and use .order later on, I am defining the order based on "group", in this case, it is alphabetical.
I want to be able to sort based on the aggregated counts.
So what I did was create this array:
var view3 = [ {"total":"19","count":19, "name":"f", "group":"A"}, {"total": "86","count":1, "name":"c", "group":"B"}, {"total":"86","count":10, "name":"b", "group":"B"}, {"total":"86","count":67, "name":"f", "group":"B"}, {"total":"86","count":8, "name":"a", "group":"B"}, {"total":"5","count":5, "name":"f", "group":"C"}, {"total":"5","count":4, "name":"f", "group":"D"}, {"total":"5","count":1, "name":"a", "group":"D"}, {"total":"5","count":1, "name":"a", "group":"E"}];
`	var visualization = d3plus.viz()
.container("#viz")     // container DIV to hold the visualization
.data(view3)     // data to use with the visualization
.type("bubbles")       // visualization type
.id(["total","name"]) // nesting keys
.depth(1)              // 0-based depth
.size("count") // key name to size bubbles
.order({"sort":"asc"})
.color("name") // color by each group
.draw()                // finally, draw the visualization!
`
The above works for sorting the aggregated bubbles from large to small. However...it breaks down beyond 10 bubbles.  Hope this makes sense.

Thanks for posting your code. I was able to hunt down the problem and it the fix will be part of the next release.

Nice! Thank you Dave.


Optional Success and fail widgets

Looks very nice and smooth however, there should be an optional success and fail state of the widget after the waiting progress animation finishes for these buttons to be more useful.
Just like how the button transforms from
Its default state to the busy state(network call) after we get the response we should be able to show the user what hos/her action resulted in with a green tick or a red exclamation mark for instance

Yes sure go ahead with it.

dear @iamyogik, I've read your Code. I think I should add a new ButtonState to this enum. and before showing the Idle state, the button should go into the error or success state.
if u have any other idea please let me know.

should I change the onTap event?
should I take any other constructor parameter?

thanks


Umlauts in filenames

Hi! Unfortunately all umlauts from the german language (ÄÖÜäöüß) gets "normalized" (=erased). Many of the lecture titles are harder to read because of this. Would it be possible to add umlauts to the allowed characters?
I tried this for a quick workaround: changing the unicodedata.normalize method in _sanitize.py from 'NFKC' to 'NFKD'. At least this gives me U instead of Ü or o instead of ö. But not an ideal result. Adding the umlauts to the SLUG_OK variable did not help at all.
Best regards

@NoMoreUsernamesAvailable currently i 'm working on new release i will look into that in next release.


nytimes.com submitting search does not work

If I record going to http://nytimes.com, clicking on the search button in the top left corner, and submit a search term, I get following result
const {open, click, type, submit} = require('@pptr/recorder');
open('http://nytimes.com', async () => {
  await click('#app > div:nth-child(2) > div > header > section.css-ui9rw0.e1suatyy2 > div.css-11hrj97.er09x8g0 > div.css-10488qs > button > svg');
  await click('ariaName/SEARCH');
  await type('ariaName/SEARCH', 'coronavirus');
  await submit('#app > div:nth-child(2) > div > header > section.css-ui9rw0.e1suatyy2 > div.css-11hrj97.er09x8g0 > div.css-10488qs > div > form');
  await click('ariaName/Coronavirus Live Updates: U.S. Daily Cases Surpass 59,000');
})

This does not replay correctly though.

Thanks for reporting this. I'll take a look at what's going wrong there!

There are multiple elements with the same aria name. I'll look into how to distinguish them.


Why is element.clone() used?

My page is running very slow with vertilize and i can only assume its the element.clone() duplicating loads of inputs. Why do you use this? I've seen the comment but I still don't quite understand why you can't just take the height.

I guess this is also related to #15. I had the same issue and for me the workaround is simply:
 var getMyRealHeight = function(){ 	 return element.clientHeight;  };


fix: modify synapse test config, modify isolation forest notebook for testing

Related Issues/PRs

#xxx
What changes are proposed in this pull request?
Briefly describe the changes included in this Pull Request.
How is this patch tested?

[ ] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[ ] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[ ] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

/azp run

Codecov Report

Merging #1833 (ba9a663) into master (a7e20ce) will decrease coverage by 40.65%.
The diff coverage is n/a.

 Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

/azp run

/azp run

/azp run

/azp run

Summary for changes made here:
package install on synapse test: need to replace magic with subprocess for testing pipeline.
avro: logging isolation forest requires avro, change the configuration and adding the package.
logging model:

reload package: preinstalled package typing_extensions need to be update and reload on Synapse 3.2 pool
setup connection with AML

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

website/docs/getting_started/installation.md
97
100
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

website/docs/getting_started/installation.md
97
100
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

/azp run

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

website/docs/getting_started/installation.md
97
100
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

website/docs/getting_started/installation.md
97
100
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

website/docs/getting_started/installation.md
97
100
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

/azp run

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

website/docs/getting_started/installation.md
88
100
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

website/docs/getting_started/installation.md
88
100
100
link
:white_check_mark:

website/docs/mlflow/installation.md
85
100
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

Acrolinx Scorecards
A minimum Acrolinx score of 80 is required.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology.

Article
Acrolinxscore
Word andPhrases Score
CorrectnessScore
Scorecard
Processed

website/docs/getting_started/installation.md
88
100
100
link
:white_check_mark:

website/docs/mlflow/installation.md
100
100
100
link
:white_check_mark:

More information about Acrolinx

Install Acrolinx locally for VSCode
False positives or issues
Troubleshooting issues with Acrolinx

/azp run


Feature Request - More Hex-Friendly Modern/Sci-Fi Options

There's a bit of visual dissonance from a square-oriented object (circles with four points, elements broken up into quarters, etc.) spinning around hex-shaped icons. The module includes some very nice round+hex shaped turn markers, but they're very fantasy flavored. I would love to see more options that are circular in nature (a pattern that repeats more than four times) but also more hi-tech.

Any additions are very welcome, however I am not an artist. If you can source artwork with licencing I would be more than happy to add more options. That being said, you can freely choose any image in your data folder to use instead, you are not limited to the seleection provided


Goaccess Not Working behind Nginx Reverse Proxy

I know this is a common issue and I have spent the last 2 days just going through the solutions but still not being able to fix it.
Okay, so here is the scenario. I am running an Express Backend on AWS EC2 and using Nginx as reverse proxy (SSL certificates are provisioned by letsencrypt). Here is my config:
server {
    server_name my.domain;
    location / {
      proxy_pass http://localhost:5000;
    }

    location /report {
        alias /var/www/html;
        index report.html;
        types {
            text/html html htm;
        }
        add_header Content-Type text/html;
    }

    location /ws {
        proxy_pass http://localhost:7890;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        proxy_buffering off;
        proxy_cache off;
        proxy_connect_timeout 60s;
        proxy_send_timeout 300s;
        proxy_read_timeout 300s;
    }

   listen 443 ssl;
   ssl_certificate /etc/letsencrypt/live/my.domain/fullchain.pem;
   ssl_certificate_key /etc/letsencrypt/live/my.domain/privkey.pem;
   include /etc/letsencrypt/options-ssl-nginx.conf;
   ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem;
}
server {
  if ($host = my.domain) {
    return 301 https://$host$request_uri;
  } # managed by Certbot

  listen 80;
  server_name my.domain;
    return 404;
}

The command that I am running is:
sudo goaccess /var/log/nginx/access.log -o /var/www/html/report.html \
 --real-time-html \
 --ws-url=wss://my.domain/ws \
 --log-format=COMBINED \
 --port=7890 \
 --ssl-cert=/etc/letsencrypt/live/my.domain/fullchain.pem \
 --ssl-key=/etc/letsencrypt/live/my.domain/privkey.pem

Now, When I try to go to wss://my.domain/ws, it says Connection Refused.
➜  ~ websocat wss://my.domain/ws

websocat: WebSocketError: WebSocketError: Received unexpected status code (502 Bad Gateway)
websocat: error running

Upon Inspecting Nginx Logs, I get this:
ubuntu@ip-<IP_ADDRESS>:~$ sudo tail -f /var/log/nginx/error.log

2024/10/28 10:18:49 [error] 80757#80757: *469 upstream prematurely closed connection while reading response header from upstream, client: <IP_ADDRESS>, server: my.domain, request: "GET /ws HTTP/1.1", upstream: "http://<IP_ADDRESS>:7890/ws", host: "my.domain"

GoAccess Logs are empty though. (Still waiting for websocket connections)
ubuntu@ip-<IP_ADDRESS>:~$ sudo goaccess /var/log/nginx/access.log -o /var/www/html/report.html --real-time-html --ws-url=wss://my.domain/ws --port=7890 --log-format=COMBINED -d
 [SETTING UP STORAGE /var/log/nginx/access.log] {0} @ {0/s}
WebSocket server ready to accept new client connections

Additional:
When I run goaccess as a background process and try to access the websocket from the machine itself (without using nginx), it fails to connect as well.
ubuntu@ip-<IP_ADDRESS>:~$ curl -v -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Host: localhost:7890" -H "Origin: http://localhost" http://localhost:7890/ws
* Host localhost:7890 was resolved.
* IPv6: ::1
* IPv4: <IP_ADDRESS>
*   Trying [::1]:7890...
* connect to ::1 port 7890 from ::1 port 50438 failed: Connection refused
*   Trying <IP_ADDRESS>:7890...
* Connected to localhost (<IP_ADDRESS>) port 7890
> GET /ws HTTP/1.1
> Host: localhost:7890
> User-Agent: curl/8.5.0
> Accept: */*
> Connection: Upgrade
> Upgrade: websocket
> Origin: http://localhost
>
* Empty reply from server
* Closing connection
curl: (52) Empty reply from server

I am also using Cloudflare for managing DNS and I have enabled Websockets as well as set SSL/TLS to Strict(Full).

Okay, After countless hours of mindless debugging, here is what fixed it. In Cloudflare, disabling "Proxy through Cloudflare" in DNS Panel


Remove vendor directory

If/when #1043 is fixed, can we remove the vendor directory requirement? go mod vendor is fast.

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

To be honest, I think we could keep vendor directory, so Docker builds are faster and you don't hit issues with outages of dependencies hosting etc.

+1 remove vendor
Just because my IDE (JetBrains goland) supports symlinks in vendor dir no very well... It doesn't treat things in the original path and symlinked path as the same one, which makes functionalities like find usage only return a partial result set, really annoying when reading codes.
I have to write a script to delete all symlinks when I need to read codes and regen them when I need to compile  :joy:

/remove-lifecycle rotten

/remove-lifecycle stale

This project is being archives, for more information see this issue:
https://github.com/kubernetes/org/issues/2824
/close


Entire material-ui library stubbed out and mostly implemented

I'm not at 100% coverage yet, but the definition file is already over 1,900 lines.
Every component except for the ./svg-icons/**/* tree is at least stubbed out, if not implemented.
Modules can be required()ed at the top level (require("material-ui")) or at the component level (require("material-ui/lib/flat-button")).  Both work; to use for variable typing, it's better to pull from the top level.
The tests are written in a .TSX file using the documentation examples and then back-ported to .TS.
This pull request implements #5619, a request for material-ui definitions.
It is significantly more complete than pull request #5736, which only had FlatButton implemented.
This implementation requires and includes #5915, minor updates to react.d.ts.

material-ui/material-ui.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/material-ui
http://bower.io/search/?q=material-ui
others?

[X] has a test file? (material-ui/material-ui-tests.ts or others)
[ ] pass the Travis-CI test?

@pspeter3 @vsiao @jbrantly could you review react.d.ts changes?

blocked by https://github.com/DefinitelyTyped/definition-tester/issues/11

Did some definitions as well last week but I see you are already onto something here. Mine covers all components exported from material-ui's index.js, but I have no tests and I'm not 100% sure of its correctness.
Some remarks that might help:

There are some required properties, denoted by PropTypes.*.isRequired.
You can extend props interface based on the component itself, no need to redefine "ref":

interface MenuProps extends React.Props<Menu> {
//...
}
class Menu extends React.Component<MenuProps, {}> {
}

No circular reference problem here.

Some components delegate some props to inner components, like this <Button {...this.props}>.... For some components I extended Props from React.HTMLAttributes, but this is not always possible, nor is it always 100% correct, since only a subset or the properties may be passed to the inner component. Another example is RaisedButton, which uses an EnhancedButton and so "extends" its properties.

Some props defined in HTMLAttributes are redefined (e.g. style, icon), but sometimes with different types, making it impossible to extend from the HTMLAttributes interface.

Will post my d.ts later tomorrow, for cross-checking.

@use-strict:

You can extend props interface based on the component itself, no need to redefine "ref":

I'm currently blocked by #5915 when the component extends HTMLAttributes and also has methods on the instance, which many do.  Those are still there to ensure that the underlying React library also gets changed or generate an error if it hasn't.  I was planning on removing them later.

For some components I extended Props from React.HTMLAttributes, but this is not always possible, nor is it always 100% correct, since only a subset or the properties may be passed to the inner component. Another example is RaisedButton, which uses an EnhancedButton and so "extends" its properties.

I think it is ok to extend the React.HTMLAttributes in most cases because it is always going to add new properties.  I did implement RaisedButtonProp based on SharedEnhancedButtonProp<T>, based on React.HTMLAttributesBase<T>, so please take a look at it.

You can use the same name for both exported variable and its type (I think there are similar examples in lib.d.ts)

I did this in many cases, for example, Transitions (see line), but in the case of Typography, the module exports an instance of a class, so I modeled it as such, and I can't share names between a class and a variable (see line)
I don't have every component in there, and I haven't gone through them all and checked if there is an underlying HTML element (thus needing HTMLAttributes) yet, but I am fairly confident in what I have so far because I not only have the tests, I am using these components in a real project.
I welcome a collaboration to get this fleshed out.  I've probably spend 20 hours on the definitions so far, and they aren't complete yet.  I would like to see this merged soon so everyone has a common base to build from.

@ngbrown , I implemented my changes here: https://github.com/ngbrown/DefinitelyTyped/pull/1 . Please review them and let's discuss if there is anything questionable in there.

@use-strict thanks a lot for helping.  I cleaned up some stuff, but your contributions really made this more complete.

@pspeter3 @vsiao @jbrantly could you review this pull request about react.d.ts?

@vvakame I am in #5915 which is the react.d.ts changes here

oh, same changes? thanks!
@ngbrown please merge master/HEAD into this PR.

@vvakame done..

thanks mate!

Hi @vvakame, I'm waiting patiently for the Material-UI definitions :)
Can you give an approximate time when it will be generally available?

@huwman Sorry, I should have been more clear. This is the merged PR that implemented the material UI definitions. You can get them from here: https://github.com/borisyankov/DefinitelyTyped/tree/master/material-ui

@jbrantly That is very cool. Thanks to all that worked on it!

@ngbrown Do you have a project hidden somewhere that you used to test this?

@huwman normally a UI toolkit would be just one of many packages used in a project, so an option would be to find a TypeScript based React starter project.  I built my project manually so I haven't looked into this and have no recommendations.
See the files in the https://github.com/borisyankov/DefinitelyTyped/tree/master/material-ui directory for the DefinitelyTyped test.
Personally, I manage all the JS libraries through NPM, TSD for TypeScript definitions, and WebPack for hot-reload and bundling, but there really is no one way.  Experiment and find what works best for you and your project.

@ngbrown , I just found an obscure behavior that allows to export the types as well via export = .
declare namespace "material-ui/lib/dialog" {
    import Dialog = __MaterialUI.Dialog;
    export = Dialog;
}

The only difference is not exporting __MaterialUI.Dialog directly, but first importing it first as an alias, then re-exporting it.
Could be a subject for another PR :)


Broken

I have my flow and qna maker set up correctly and it was working. It has since stopped responding. You ask a question in Yammer and it doesn't give an answer.

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

ID: 32446a8e-a16c-8017-290e-d414e6d9a242
Version Independent ID: e4f45a16-0deb-2eb4-eca2-31bec804dc51
Content: Create a knowledge-based commnity in Yammer by using QnA Maker and Flow
Content Source: yammer/integrate-yammer-with-other-apps/knowledge-base-community-flow-qna-maker.md
Service: yammer
GitHub Login: @IrenePasternack
Microsoft Alias: v-irpast

@hpfaff88  - thank you for submitting feedback.
I think the best way forward is if you can open a service ticket in your tenant so this can get resolved ASAP. Based on outcome let me know if it is something that can be called out in the docs.
Please follow this link contact support for business products: https://docs.microsoft.com/office365/admin/contact-support-for-business-products
If you don't mind please keep us posted here on the resolution and I really want to get this information you are discovering back into the docs.
NOTE:  We used to use this link to a video explaining how to open a support ticket.
Here is a quick video on opening a ticket: https://www.youtube.com/watch?v=puuOy0sEg1Y


what the .mlab file used for?

Hi, i'm new to medical image process and happen to known mevislab.There are two .mlab files in your repository but no related description mentioned,could you please share sth about this? I have opened the file but the result of the process pipeline seemed meaningless as below, is there something i misunderstood ?

Hi shartoo,
The image you are looking at is a segmented lung, not the orginal CT scan volume. It's a method for segmenting lungs, but it's quite slow and not recommended.

It's not used for anything in the LUNA competition by the way, as the organizers already supply segmentations which are mostly fine. It was created for a sub-assignment in the university course.

Ah,i see,thank you! There are various way to do lung segmentation,have you ever tried to step further on after lung  segmentation? Like generating nodule candidates by Mevislab network using traditional method such as region growing,connected component computation,or context feature of nodules. Some paper show great capability of Mevislab and fine candidates instead of whole lung before CNN may compensate for the lack of labeled positive sample of data ,what's your opinion? Here is some basic work i have done

An example paper using Mevislab is below,published in 2014 and reached a sensitivity of 80% at an average of only 1.0 false positive detections per scan.
Automatic detection of subsolid pulmonary nodules in thoracic
computed tomography images

That is very neat, most candidate extraction methods trade off precision for recall. Recall is much more important, as the false positives can be filtered very well (see FPRED track in the LUNA16 competition).
I have been experimenting with a 3D CNN approach without any segmentation steps. The network is quite simple in architecture, but I haven't had time to explore it well or tune the hyperparameters. I haven't calculated the amount of parameters, but a save of the network structure + weights is around 440KB. Inference is also fast at a few seconds per scan.
I am using a different annotation set than the one used in the LUNA16 competition, it has 1406 nodules annotated (by at least 2 radiologists), it excludes nodules which are probably benign.  I hit around 1322 of these, so a recall of 0.94, with 59804 candidates. Precision would then be (1322/59804=)0.022. This is much better than the systems used for the FPRED candidate set. Although big note should be taken that this was trained on a subset of the same dataset (no proper cross-validation splits), so real world performance is probably worse!
Maybe if I find the time I can do the proper splits and make another submission..

A solely 3DCNN can achieve a recall of 0.94, that's amazing 👍 ! A 3DCNN example  is a fusion of mutli-level framework from Qi Dou whose kernel achieved the highest competition performance metric (CPM) score in the false positive reduction track in LUNA16 challenge.His network framework is rather simple as below:

the result

I have implemented this network by tensorflow but get a performance just so so,which may be caused by bad data preprocess or lacke of enough training data.There is an idea using multi-view 2DCNN came from paper Pulmonary nodule detection in CT images: false
positive reduction using multi-view convolutional
networks and got a nice result,its framework is:

too complex to implement 😸 . Thank you for your sharing and look forward to your better kernel on kaggle!

@gzuidhof could you share the link to download LUNA16 segmentation data (original_lung_masks). I can only download the original lung data and csv files (including: annotations.csv, candidates.csv, sampleSubmission.csv)

@huythach you can find them here (link from the competition website downloads page).

@gzuidhof Thank you for your shared link.
Now I can run you program, but another error happens
"IOError: [Errno 2] No such file or directory: 'data\1_1_1mm_slices_lung\subset0\<IP_ADDRESS>.4.1.145<IP_ADDRESS>.6279.6001.108197895896446896160048741492_slice80.pkl.gz'"
Do you know how to fix it? Thanks.

I see the problem that gzip.open does not automatically create a folder to save file, so that error occurs. By writing a simple check and create folder as follows, I can handle the problem. Thanks.
def create_folder_if_not_exist(filePath):
if not os.path.exists(os.path.dirname(filePath)):
try:
os.makedirs(os.path.dirname(filePath))
except OSError as exc: # Guard against race condition
if exc.errno != errno.EEXIST:
raise

@shartoo  3DCNN mentioned above, the title of this paper? Does he have a shared code?

@mjiansun no,he does't.But the framefork is rather simple,you can build it with tensorflow(or Keras) by few code.

@shartoo OK, thank you very much!

@shartoo How did you get the training set?How do you preprocess the data？

@mjiansun  As described in the paper,the training data comes from LUNA16 which can be download from their website.A good model largely depend on suitable data preprocessing  ,some data enhancement should be done .

@shartoo Ok. I will try.

@mjiansun 你是南信工的？我是南财的。

@shartoo 是的。


Fix markdown files for proper markdown formatting.

$ mdl docs/
docs//how-to-use-paperclip-with-minio.md:9: MD009 Trailing spaces
docs//how-to-use-paperclip-with-minio.md:11: MD009 Trailing spaces
docs//how-to-use-paperclip-with-minio.md:12: MD009 Trailing spaces
docs//how-to-use-paperclip-with-minio.md:22: MD009 Trailing spaces
docs//how-to-use-paperclip-with-minio.md:24: MD009 Trailing spaces
docs//how-to-use-paperclip-with-minio.md:26: MD009 Trailing spaces
docs//how-to-use-paperclip-with-minio.md:30: MD009 Trailing spaces
docs//how-to-use-paperclip-with-minio.md:31: MD009 Trailing spaces
docs//how-to-use-paperclip-with-minio.md:38: MD009 Trailing spaces
docs//how-to-use-paperclip-with-minio.md:3: MD013 Line length
docs//how-to-use-paperclip-with-minio.md:7: MD013 Line length
docs//how-to-use-paperclip-with-minio.md:9: MD013 Line length
docs//how-to-use-paperclip-with-minio.md:11: MD022 Headers should be surrounded by blank lines
docs//how-to-use-paperclip-with-minio.md:36: MD031 Fenced code blocks should be surrounded by blank lines
docs//how-to-use-paperclip-with-minio.md:38: MD032 Lists should be surrounded by blank lines
docs//how-to-use-paperclip-with-minio.md:9: MD034 Bare URL used
docs//how-to-use-cloudberry-drive-with-minio.md:27: MD012 Multiple consecutive blank lines
docs//how-to-use-cloudberry-drive-with-minio.md:3: MD013 Line length
docs//how-to-use-cloudberry-drive-with-minio.md:9: MD013 Line length
docs//how-to-use-cloudberry-drive-with-minio.md:11: MD013 Line length
docs//how-to-use-cloudberry-drive-with-minio.md:17: MD013 Line length
docs//how-to-use-cloudberry-drive-with-minio.md:23: MD013 Line length
docs//how-to-use-cloudberry-drive-with-minio.md:25: MD034 Bare URL used
docs//aws-cli-with-minio.md:3: MD009 Trailing spaces
docs//aws-cli-with-minio.md:11: MD009 Trailing spaces
docs//aws-cli-with-minio.md:12: MD009 Trailing spaces
docs//aws-cli-with-minio.md:41: MD009 Trailing spaces
docs//aws-cli-with-minio.md:3: MD013 Line length
docs//aws-cli-with-minio.md:5: MD013 Line length
docs//aws-cli-with-minio.md:20: MD013 Line length
docs//aws-cli-with-minio.md:11: MD022 Headers should be surrounded by blank lines
docs//aws-cli-with-minio.md:40: MD022 Headers should be surrounded by blank lines
docs//aws-cli-with-minio.md:42: MD022 Headers should be surrounded by blank lines
docs//aws-cli-with-minio.md:13: MD034 Bare URL used
docs//aws-cli-with-minio.md:19: MD034 Bare URL used
docs//store-postgresql-backups-in-minio.md:10: MD009 Trailing spaces
docs//store-postgresql-backups-in-minio.md:25: MD009 Trailing spaces
docs//store-postgresql-backups-in-minio.md:13: MD013 Line length
docs//store-postgresql-backups-in-minio.md:25: MD013 Line length
docs//store-postgresql-backups-in-minio.md:27: MD014 Dollar signs used before commands without showing output
docs//store-postgresql-backups-in-minio.md:11: MD022 Headers should be surrounded by blank lines
docs//store-postgresql-backups-in-minio.md:15: MD026 Trailing punctuation in header
docs//store-postgresql-backups-in-minio.md:23: MD026 Trailing punctuation in header
docs//store-mysql-backups-in-minio.md:5: MD009 Trailing spaces
docs//store-mysql-backups-in-minio.md:26: MD009 Trailing spaces
docs//store-mysql-backups-in-minio.md:5: MD012 Multiple consecutive blank lines
docs//store-mysql-backups-in-minio.md:16: MD012 Multiple consecutive blank lines
docs//store-mysql-backups-in-minio.md:14: MD013 Line length
docs//store-mysql-backups-in-minio.md:26: MD013 Line length
docs//store-mysql-backups-in-minio.md:28: MD014 Dollar signs used before commands without showing output
docs//store-mysql-backups-in-minio.md:6: MD022 Headers should be surrounded by blank lines
docs//store-mysql-backups-in-minio.md:17: MD026 Trailing punctuation in header
docs//store-mysql-backups-in-minio.md:24: MD026 Trailing punctuation in header
docs//how-to-install-golang.md:9: MD001 Header levels should only increment by one level at a time
docs//how-to-install-golang.md:53: MD001 Header levels should only increment by one level at a time
docs//how-to-install-golang.md:12: MD009 Trailing spaces
docs//how-to-install-golang.md:60: MD009 Trailing spaces
docs//how-to-install-golang.md:26: MD013 Line length
docs//how-to-install-golang.md:74: MD013 Line length
docs//how-to-install-golang.md:11: MD014 Dollar signs used before commands without showing output
docs//how-to-install-golang.md:19: MD014 Dollar signs used before commands without showing output
docs//how-to-install-golang.md:36: MD014 Dollar signs used before commands without showing output
docs//how-to-install-golang.md:42: MD014 Dollar signs used before commands without showing output
docs//how-to-install-golang.md:59: MD014 Dollar signs used before commands without showing output
docs//how-to-install-golang.md:67: MD014 Dollar signs used before commands without showing output
docs//how-to-install-golang.md:86: MD014 Dollar signs used before commands without showing output
docs//how-to-install-golang.md:92: MD014 Dollar signs used before commands without showing output
docs//how-to-install-golang.md:49: MD024 Multiple headers with the same content
docs//how-to-install-golang.md:57: MD024 Multiple headers with the same content
docs//how-to-install-golang.md:63: MD024 Multiple headers with the same content
docs//how-to-install-golang.md:72: MD024 Multiple headers with the same content
docs//how-to-install-golang.md:90: MD024 Multiple headers with the same content
docs//how-to-install-golang.md:33: MD031 Fenced code blocks should be surrounded by blank lines
docs//aws-sdk-for-javascript-with-minio.md:3: MD009 Trailing spaces
docs//aws-sdk-for-javascript-with-minio.md:8: MD009 Trailing spaces
docs//aws-sdk-for-javascript-with-minio.md:11: MD009 Trailing spaces
docs//aws-sdk-for-javascript-with-minio.md:37: MD009 Trailing spaces
docs//aws-sdk-for-javascript-with-minio.md:3: MD013 Line length
docs//aws-sdk-for-javascript-with-minio.md:11: MD013 Line length
docs//aws-sdk-for-javascript-with-minio.md:15: MD013 Line length
docs//aws-sdk-for-javascript-with-minio.md:17: MD013 Line length
docs//aws-sdk-for-javascript-with-minio.md:9: MD022 Headers should be surrounded by blank lines
docs//aws-sdk-for-javascript-with-minio.md:59: MD031 Fenced code blocks should be surrounded by blank lines
docs//aws-sdk-for-javascript-with-minio.md:17: MD038 Spaces inside code span elements
docs//setup-nginx-proxy-with-minio.md:3: MD009 Trailing spaces
docs//setup-nginx-proxy-with-minio.md:5: MD009 Trailing spaces
docs//setup-nginx-proxy-with-minio.md:13: MD009 Trailing spaces
docs//setup-nginx-proxy-with-minio.md:32: MD009 Trailing spaces
docs//setup-nginx-proxy-with-minio.md:39: MD009 Trailing spaces
docs//setup-nginx-proxy-with-minio.md:17: MD013 Line length
docs//setup-nginx-proxy-with-minio.md:39: MD026 Trailing punctuation in header
docs//setup-nginx-proxy-with-minio.md:47: MD026 Trailing punctuation in header
docs//store-mongodb-backups-in-minio.md:10: MD009 Trailing spaces
docs//store-mongodb-backups-in-minio.md:11: MD009 Trailing spaces
docs//store-mongodb-backups-in-minio.md:26: MD009 Trailing spaces
docs//store-mongodb-backups-in-minio.md:5: MD012 Multiple consecutive blank lines
docs//store-mongodb-backups-in-minio.md:12: MD012 Multiple consecutive blank lines
docs//store-mongodb-backups-in-minio.md:15: MD013 Line length
docs//store-mongodb-backups-in-minio.md:26: MD013 Line length
docs//store-mongodb-backups-in-minio.md:28: MD014 Dollar signs used before commands without showing output
docs//store-mongodb-backups-in-minio.md:17: MD026 Trailing punctuation in header
docs//store-mongodb-backups-in-minio.md:24: MD026 Trailing punctuation in header
docs//rclone-with-minio.md:54: MD009 Trailing spaces
docs//rclone-with-minio.md:57: MD009 Trailing spaces
docs//rclone-with-minio.md:72: MD009 Trailing spaces
docs//rclone-with-minio.md:73: MD009 Trailing spaces
docs//setup-apache-http-proxy-with-minio.md:3: MD009 Trailing spaces
docs//setup-apache-http-proxy-with-minio.md:43: MD009 Trailing spaces
docs//setup-apache-http-proxy-with-minio.md:49: MD009 Trailing spaces
docs//setup-apache-http-proxy-with-minio.md:48: MD012 Multiple consecutive blank lines
docs//setup-apache-http-proxy-with-minio.md:5: MD013 Line length
docs//setup-apache-http-proxy-with-minio.md:9: MD013 Line length
docs//setup-apache-http-proxy-with-minio.md:13: MD013 Line length
docs//setup-apache-http-proxy-with-minio.md:51: MD014 Dollar signs used before commands without showing output
docs//setup-apache-http-proxy-with-minio.md:57: MD014 Dollar signs used before commands without showing output
docs//setup-apache-http-proxy-with-minio.md:18: MD026 Trailing punctuation in header
docs//setup-apache-http-proxy-with-minio.md:49: MD026 Trailing punctuation in header
docs//setup-apache-http-proxy-with-minio.md:55: MD026 Trailing punctuation in header
docs//s3cmd-with-minio.md:57: MD009 Trailing spaces
docs//s3cmd-with-minio.md:3: MD013 Line length
docs//s3cmd-with-minio.md:5: MD013 Line length
docs//s3cmd-with-minio.md:20: MD013 Line length
docs//s3cmd-with-minio.md:13: MD034 Bare URL used
docs//s3cmd-with-minio.md:17: MD034 Bare URL used
docs//s3cmd-with-minio.md:19: MD034 Bare URL used
docs//aws-sdk-for-php-with-minio.md:8: MD009 Trailing spaces
docs//aws-sdk-for-php-with-minio.md:11: MD009 Trailing spaces
docs//aws-sdk-for-php-with-minio.md:3: MD013 Line length
docs//aws-sdk-for-php-with-minio.md:11: MD013 Line length
docs//aws-sdk-for-php-with-minio.md:15: MD013 Line length
docs//aws-sdk-for-php-with-minio.md:9: MD022 Headers should be surrounded by blank lines
docs//aws-sdk-for-go-with-minio.md:8: MD009 Trailing spaces
docs//aws-sdk-for-go-with-minio.md:37: MD009 Trailing spaces
docs//aws-sdk-for-go-with-minio.md:81: MD009 Trailing spaces
docs//aws-sdk-for-go-with-minio.md:23: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:24: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:25: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:27: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:28: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:29: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:30: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:31: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:35: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:36: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:37: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:38: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:39: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:40: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:41: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:42: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:43: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:44: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:45: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:46: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:48: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:50: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:51: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:52: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:54: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:55: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:56: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:57: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:58: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:59: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:60: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:62: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:63: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:64: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:65: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:66: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:67: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:68: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:69: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:70: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:71: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:72: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:74: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:75: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:76: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:77: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:78: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:79: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:80: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:81: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:82: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:83: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:84: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:85: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:86: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:87: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:88: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:89: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:90: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:91: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:92: MD010 Hard tabs
docs//aws-sdk-for-go-with-minio.md:3: MD013 Line length
docs//aws-sdk-for-go-with-minio.md:15: MD013 Line length
docs//aws-sdk-for-go-with-minio.md:40: MD013 Line length
docs//aws-sdk-for-go-with-minio.md:72: MD013 Line length
docs//aws-sdk-for-go-with-minio.md:9: MD022 Headers should be surrounded by blank lines
docs//multiple-minio-servers-with-traefik.md:83: MD010 Hard tabs
docs//multiple-minio-servers-with-traefik.md:85: MD010 Hard tabs
docs//multiple-minio-servers-with-traefik.md:86: MD010 Hard tabs
docs//multiple-minio-servers-with-traefik.md:87: MD010 Hard tabs
docs//multiple-minio-servers-with-traefik.md:88: MD010 Hard tabs
docs//multiple-minio-servers-with-traefik.md:89: MD010 Hard tabs
docs//multiple-minio-servers-with-traefik.md:90: MD010 Hard tabs
docs//multiple-minio-servers-with-traefik.md:131: MD013 Line length
docs//multiple-minio-servers-with-traefik.md:132: MD013 Line length
docs//multiple-minio-servers-with-traefik.md:133: MD013 Line length
docs//aws-sdk-for-java-with-minio.md:8: MD009 Trailing spaces
docs//aws-sdk-for-java-with-minio.md:15: MD009 Trailing spaces
docs//aws-sdk-for-java-with-minio.md:106: MD009 Trailing spaces
docs//aws-sdk-for-java-with-minio.md:120: MD009 Trailing spaces
docs//aws-sdk-for-java-with-minio.md:124: MD009 Trailing spaces
docs//aws-sdk-for-java-with-minio.md:129: MD009 Trailing spaces
docs//aws-sdk-for-java-with-minio.md:3: MD013 Line length
docs//aws-sdk-for-java-with-minio.md:11: MD013 Line length
docs//aws-sdk-for-java-with-minio.md:15: MD013 Line length
docs//aws-sdk-for-java-with-minio.md:76: MD013 Line length
docs//aws-sdk-for-java-with-minio.md:9: MD022 Headers should be surrounded by blank lines
docs//aws-sdk-for-java-with-minio.md:134: MD031 Fenced code blocks should be surrounded by blank lines
docs//aws-sdk-for-python-with-minio.md:8: MD009 Trailing spaces
docs//aws-sdk-for-python-with-minio.md:11: MD009 Trailing spaces
docs//aws-sdk-for-python-with-minio.md:3: MD013 Line length
docs//aws-sdk-for-python-with-minio.md:11: MD013 Line length
docs//aws-sdk-for-python-with-minio.md:15: MD013 Line length
docs//aws-sdk-for-python-with-minio.md:36: MD013 Line length
docs//aws-sdk-for-python-with-minio.md:39: MD013 Line length
docs//aws-sdk-for-python-with-minio.md:9: MD022 Headers should be surrounded by blank lines
docs//aws-sdk-for-python-with-minio.md:51: MD031 Fenced code blocks should be surrounded by blank lines
docs//aws-sdk-for-ruby-with-minio.md:8: MD009 Trailing spaces
docs//aws-sdk-for-ruby-with-minio.md:11: MD009 Trailing spaces
docs//aws-sdk-for-ruby-with-minio.md:3: MD013 Line length
docs//aws-sdk-for-ruby-with-minio.md:11: MD013 Line length
docs//aws-sdk-for-ruby-with-minio.md:15: MD013 Line length
docs//aws-sdk-for-ruby-with-minio.md:17: MD013 Line length
docs//aws-sdk-for-ruby-with-minio.md:9: MD022 Headers should be surrounded by blank lines
docs//aws-sdk-for-ruby-with-minio.md:58: MD031 Fenced code blocks should be surrounded by blank lines
docs//aggregate-apache-logs-with-fluentd-and-minio.md:61: MD009 Trailing spaces
docs//aggregate-apache-logs-with-fluentd-and-minio.md:15: MD012 Multiple consecutive blank lines
docs//aggregate-apache-logs-with-fluentd-and-minio.md:72: MD012 Multiple consecutive blank lines
docs//aggregate-apache-logs-with-fluentd-and-minio.md:93: MD012 Multiple consecutive blank lines
docs//aggregate-apache-logs-with-fluentd-and-minio.md:3: MD013 Line length
docs//aggregate-apache-logs-with-fluentd-and-minio.md:29: MD022 Headers should be surrounded by blank lines
docs//aggregate-apache-logs-with-fluentd-and-minio.md:18: MD026 Trailing punctuation in header
docs//aggregate-apache-logs-with-fluentd-and-minio.md:29: MD026 Trailing punctuation in header
docs//aggregate-apache-logs-with-fluentd-and-minio.md:61: MD026 Trailing punctuation in header
docs//aggregate-apache-logs-with-fluentd-and-minio.md:70: MD026 Trailing punctuation in header
docs//aggregate-apache-logs-with-fluentd-and-minio.md:89: MD026 Trailing punctuation in header
docs//aggregate-apache-logs-with-fluentd-and-minio.md:100: MD026 Trailing punctuation in header
docs//how-to-use-mountainduck-with-minio.md:3: MD009 Trailing spaces
docs//how-to-use-mountainduck-with-minio.md:9: MD009 Trailing spaces
docs//how-to-use-mountainduck-with-minio.md:11: MD009 Trailing spaces
docs//how-to-use-mountainduck-with-minio.md:21: MD009 Trailing spaces
docs//how-to-use-mountainduck-with-minio.md:30: MD009 Trailing spaces
docs//how-to-use-mountainduck-with-minio.md:27: MD012 Multiple consecutive blank lines
docs//how-to-use-mountainduck-with-minio.md:3: MD013 Line length
docs//how-to-use-mountainduck-with-minio.md:7: MD013 Line length
docs//how-to-use-mountainduck-with-minio.md:9: MD013 Line length
docs//how-to-use-mountainduck-with-minio.md:11: MD013 Line length
docs//how-to-use-mountainduck-with-minio.md:17: MD013 Line length
docs//how-to-use-mountainduck-with-minio.md:30: MD013 Line length
docs//how-to-use-mountainduck-with-minio.md:28: MD026 Trailing punctuation in header
docs//running-minio-in-freenas.md:3: MD009 Trailing spaces
docs//running-minio-in-freenas.md:13: MD013 Line length
docs//running-minio-in-freenas.md:21: MD013 Line length
docs//running-minio-in-freenas.md:24: MD013 Line length
docs//running-minio-in-freenas.md:29: MD013 Line length
docs//running-minio-in-freenas.md:88: MD013 Line length
docs//running-minio-in-freenas.md:115: MD013 Line length
docs//running-minio-in-freenas.md:123: MD013 Line length
docs//running-minio-in-freenas.md:12: MD022 Headers should be surrounded by blank lines
docs//running-minio-in-freenas.md:23: MD022 Headers should be surrounded by blank lines
docs//running-minio-in-freenas.md:34: MD022 Headers should be surrounded by blank lines
docs//running-minio-in-freenas.md:42: MD022 Headers should be surrounded by blank lines
docs//running-minio-in-freenas.md:93: MD022 Headers should be surrounded by blank lines
docs//running-minio-in-freenas.md:122: MD022 Headers should be surrounded by blank lines
docs//running-minio-in-freenas.md:125: MD022 Headers should be surrounded by blank lines
docs//running-deis-workflow-with-minio.md:3: MD013 Line length
docs//running-deis-workflow-with-minio.md:5: MD013 Line length
docs//running-deis-workflow-with-minio.md:11: MD013 Line length
docs//running-deis-workflow-with-minio.md:15: MD013 Line length
docs//running-deis-workflow-with-minio.md:16: MD013 Line length
docs//running-deis-workflow-with-minio.md:3: MD034 Bare URL used
docs//running-deis-workflow-with-minio.md:5: MD034 Bare URL used
docs//setup-caddy-proxy-with-minio.md:21: MD009 Trailing spaces
docs//setup-caddy-proxy-with-minio.md:35: MD012 Multiple consecutive blank lines
docs//setup-caddy-proxy-with-minio.md:3: MD013 Line length
docs//setup-caddy-proxy-with-minio.md:17: MD013 Line length
docs//setup-caddy-proxy-with-minio.md:33: MD026 Trailing punctuation in header
docs//setup-caddy-proxy-with-minio.md:42: MD026 Trailing punctuation in header
docs//presigned-get-download-from-browser.md:11: MD001 Header levels should only increment by one level at a time
docs//presigned-get-download-from-browser.md:68: MD010 Hard tabs
docs//presigned-get-download-from-browser.md:69: MD010 Hard tabs
docs//presigned-get-download-from-browser.md:56: MD022 Headers should be surrounded by blank lines
docs//presigned-put-upload-via-browser.md:7: MD001 Header levels should only increment by one level at a time
docs//running-minio-in-docker.md:12: MD013 Line length
docs//running-minio-in-docker.md:74: MD013 Line length
docs//running-minio-in-docker.md:75: MD013 Line length
docs//running-minio-in-docker.md:132: MD013 Line length
docs//running-minio-in-docker.md:20: MD026 Trailing punctuation in header
docs//how-to-use-cyberduck-with-minio.md:3: MD009 Trailing spaces
docs//how-to-use-cyberduck-with-minio.md:9: MD009 Trailing spaces
docs//how-to-use-cyberduck-with-minio.md:11: MD009 Trailing spaces
docs//how-to-use-cyberduck-with-minio.md:3: MD013 Line length
docs//how-to-use-cyberduck-with-minio.md:7: MD013 Line length
docs//how-to-use-cyberduck-with-minio.md:9: MD013 Line length
docs//how-to-use-cyberduck-with-minio.md:11: MD013 Line length
docs//how-to-use-cyberduck-with-minio.md:27: MD013 Line length
docs//how-to-use-cyberduck-with-minio.md:15: MD019 Multiple spaces after hash on atx style header
docs//restic-with-minio.md:36: MD009 Trailing spaces
docs//restic-with-minio.md:3: MD013 Line length
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:33: MD012 Multiple consecutive blank lines
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:3: MD013 Line length
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:5: MD013 Line length
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:7: MD013 Line length
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:17: MD013 Line length
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:18: MD013 Line length
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:37: MD013 Line length
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:57: MD013 Line length
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:22: MD026 Trailing punctuation in header
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:31: MD026 Trailing punctuation in header
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:41: MD026 Trailing punctuation in header
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:55: MD026 Trailing punctuation in header
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:66: MD026 Trailing punctuation in header
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:75: MD026 Trailing punctuation in header
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:85: MD026 Trailing punctuation in header
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:85: MD034 Bare URL used
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:3: MD039 Spaces inside link text
docs//generate-lets-encypt-certificate-using-concert-for-minio.md:5: MD039 Spaces inside link text

@harshavardhana This is how config.json looks like to linter
{
  "name": "cookbook",
  "version": "1.0.0",
  "description": "Minio Cookbook",
  "directories": {
    "doc": "docs"
  },
  "repository": {
    "type": "git",
    "url": "git+https://github.com/minio/cookbook.git"
  },
  "author": "Minio, Inc.",
  "license": "Apache-2.0",
  "bugs": {
    "url": "https://github.com/minio/cookbook/issues"
  },
  "homepage": "https://github.com/minio/cookbook",
  "scripts": {
    "lint": "remark ."
  },
  "remarkConfig": {
    "presets": ["lint-recommended"]
  },
  "dependencies": {
    "remark-cli": "^2.1.0",
    "remark-lint": "^5.2.0",
    "remark-preset-lint-recommended": "^1.0.0"
  }
}

And this is the output of entire cookbook content.
$ npm run lint

><EMAIL_ADDRESS>lint /Users/koolhead17/minio-work/docs/cookbook
> remark .

docs/multiple-minio-servers-with-traefik.md
         8:7  warning  Remove 3 spaces before this heading’s content  no-heading-content-indent  remark-lint
        12:7  warning  Remove 3 spaces before this heading’s content  no-heading-content-indent  remark-lint
        14:7  warning  Remove 2 spaces before this heading’s content  no-heading-content-indent  remark-lint

README.md
         7:4  warning  Incorrect list-item indent: add 1 space        list-item-indent           remark-lint
         8:4  warning  Incorrect list-item indent: add 1 space        list-item-indent           remark-lint
         9:4  warning  Incorrect list-item indent: add 1 space        list-item-indent           remark-lint
        14:4  warning  Incorrect list-item indent: add 1 space        list-item-indent           remark-lint
        15:4  warning  Incorrect list-item indent: add 1 space        list-item-indent           remark-lint
        19:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        20:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        21:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        22:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        23:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        24:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        25:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        26:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        27:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        28:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        29:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        30:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        31:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        32:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        33:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        34:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        35:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        36:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        37:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        38:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
  38:3-38:87  warning  Don’t pad `link` with inner spaces             no-inline-padding          remark-lint
        39:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        40:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        41:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        42:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        43:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint
        44:3  warning  Incorrect list-item indent: add 2 spaces       list-item-indent           remark-lint

docs/presigned-get-download-from-browser.md: no issues found
docs/aws-cli-with-minio.md: no issues found
docs/aggregate-apache-logs-with-fluentd-and-minio.md: no issues found
docs/presigned-put-upload-via-browser.md: no issues found
docs/aws-sdk-for-javascript-with-minio.md: no issues found
docs/aws-sdk-for-go-with-minio.md: no issues found
docs/aws-sdk-for-java-with-minio.md: no issues found
docs/restic-with-minio.md: no issues found
docs/how-to-install-golang.md: no issues found
docs/generate-lets-encypt-certificate-using-concert-for-minio.md: no issues found
docs/aws-sdk-for-php-with-minio.md: no issues found
docs/aws-sdk-for-python-with-minio.md: no issues found
docs/aws-sdk-for-ruby-with-minio.md: no issues found
docs/s3cmd-with-minio.md: no issues found
docs/how-to-use-paperclip-with-minio.md: no issues found
docs/how-to-use-cyberduck-with-minio.md: no issues found
docs/how-to-use-mountainduck-with-minio.md: no issues found
docs/how-to-use-cloudberry-drive-with-minio.md: no issues found
docs/rclone-with-minio.md: no issues found
docs/running-deis-workflow-with-minio.md: no issues found
docs/running-minio-in-docker.md: no issues found
docs/running-minio-in-freenas.md: no issues found
docs/setup-apache-http-proxy-with-minio.md: no issues found
docs/setup-caddy-proxy-with-minio.md: no issues found
docs/setup-nginx-proxy-with-minio.md: no issues found
docs/store-mongodb-backups-in-minio.md: no issues found
docs/store-mysql-backups-in-minio.md: no issues found
docs/store-postgresql-backups-in-minio.md: no issues found

⚠ 35 warnings

Linter ignores code block indentation.

This is fixed with remark linter..


Upgrade to vue2

  "dependencies": {
    "vue": "^2.0.0",
    "vue-router": "^2.0.0",
    "vuex": "^2.0.0",
    "vuex-router-sync": "^3.0.0"
  },

Also latest webpack is now: "webpack": "2.1.0-beta.25"

webpack has breaking changes since version 22, and I will not update it for a while.

Oh!? I had no idea. Thanks ;)

Trying to use a similar approach in a vue component created using a generator:
Getting this error:
Can not load "webpack"!
  WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration has an unknown property 'vue'. These properties are valid:
   object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
   For typos: please correct them.
   For loader options: webpack 2 no longer allows custom properties in configuration.
     Loaders should be updated to allow passing options via loader options in module.rules.
     Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader:
     plugins: {
       new webpack.LoaderOptionsPlugin({
         // test: /\.xxx$/, // may apply this only for some modules
         options: {
           vue: ...
         }
       })
     }

You seen this before? Is this the webpack issue you are talking about? I see you are also using the vue config option in webpack.base.config.js
module.exports = {
    module: {
        loaders: [{
            test: /\.js$/,
            loader: 'babel',
            exclude: /node_modules/
        }, {
            test: /\.vue$/,
            loaders: ['vue']
        }]
    },
    vue: {
        loaders: {},
    }
};

https://github.com/kristianmandrup/circle-menu
    "vue-loader": "^9.5.1",
    "vue-style-loader": "^1.0.0",
    "webpack": "2.1.0-beta.21",
    "webpack-dev-middleware": "^1.8.1",
    "webpack-hot-middleware": "^2.12.2",
    "webpack-dashboard": "^0.1.8",
    "webpack-dev-server": "^1.15.0",
    "webpack-merge": "^0.14.1"

Related to this issue: https://github.com/webpack/webpack/issues/3018
But I don't see your vue loader config having any real effect unless I'd want to use postcss.

PR welcome for webpack 2 beta 23+ :)

Looks like I have beta25 installed and it works just fine...

no @kristianmandrup  i try in my i got error
throw new WebpackOptionsValidationError(webpackOptionsValidationErrors);
^
WebpackOptionsValidationError: Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.

configuration has an unknown property 'vue'. These properties are valid:
object { amd?, bail?, cache?, context?, dependencies?, devServer?, devtool?, entry, externals?, loader?, module?, name?, node?, output?, plugins?, profile?, recordsInputPath?, recordsOutputPath?, recordsPath?, resolve?, resolveLoader?, stats?, target?, watch?, watchOptions? }
For typos: please correct them.
For loader options: webpack 2 no longer allows custom properties in configuration.
Loaders should be updated to allow passing options via loader options in module.rules.
Until loaders are updated one can use the LoaderOptionsPlugin to pass these options to the loader:
plugins: {
new webpack.LoaderOptionsPlugin({
// test: /.xxx$/, // may apply this only for some modules
options: {
vue: ...
}
})
}
configuration.resolve.extensions[0] should not be empty.
at webpack (/usr/share/nginx/html/yokadev/node_modules/webpack/lib/webpack.js:16:9)
at Object. (/usr/share/nginx/html/yokadev/build/server.js:17:18)
at Module._compile (module.js:413:34)
at Object.Module._extensions..js (module.js:422:10)
at Module.load (module.js:357:32)
at Function.Module._load (module.js:314:12)
at Function.Module.runMain (module.js:447:10)
at startup (node.js:148:18)
at node.js:405:3

Remove the part vue config part:
    vue: {
        loaders: {},
    }

Se my circle-menu config

I will update webpack when its docs are ready.

I changed version in package.json to "webpack": "^1.12.2" and webpack worked well. The newer versions didn't work, i don't know why.

Could be conflicts in node_modules folder.  Good idea to make sure it's clean.
Try:
rm -rf node_modules && npm install


fix for issue #10

fix for the issue I opened a minute or so ago

Looks good, but the thing in self._default_nonassigned should be removed. Merging.


ClassHierarchy: When I move file from one package(dir) to another, it shows alert box with "Unimplemented" message

ClassHierarchy: When I move file from one package(dir) to another, it shows alert box with "Unimplemented" message, instead it should update references(like it used to work before).
TIR: STB-7312

@sganapavarapu1, did you fix this today when you fixed the move test?

@sganapavarapu1 Sorry, you didn't fix that, Boyan did.
@as3boyan Did this bug get fixed when you fixed the 'move' unit test?

Only testMovePackage was fixed. I need to test it.

It was pleasure to work with IDEA and git bisect 858ef3adfd04a3bfb6cc8ec9e08e78b3b8e06cc6 is the first bad commit, my bad

Hopefully fixed in https://github.com/TiVo/intellij-haxe/pull/272

Fixed.  Merged.