Lapce freezes when trying to edit this Markdown README file

Lapce Version
Replicated bug in both v.0.2.6 and v0.2.7 both installed from the DMG on the main website
System information
macOS Monterey 12.6, M1 Max (Apple Silicon)
Describe the bug
I attempt to edit a README file (attached) by adding an opening bracket before the text on line 77, then I added a closing bracket on the same line after the text. I then went to enter an open parentheses (Markdown link/href format) and then the program froze. I can reliably reproduce this error.
I originally had another folder open for another project, and the application logs appear to indicate the error is related to those, but I did not have any files open from that project when I was editing the README file from this other folder.
I closed the other folder so that the only folder open is the one in my project I am actively editing and the bug still occurred, so the bug does not appear to be related to having multiple folders open.
The application logs appear to consistently indicate an unhandled exception occurred related to osc_dispatch and alacritty_terminal::ansi at line 963.
Additional information
See attached Apple error reporting info after force-quitting the app.
lapce_prob_details_sysconfig.txt
See attached latest application logs:
20230504-151051.log
20230504-151738.log
The "twitch bot" stuff in the error is the other folder that was open in the left sidebar but no files from it were open in the editor tabs. The "ntdsextract" README file is what I was editing when the crash occurred. I also closed the other folder in a subsequent attempt to replicate this bug so that the only folder open was the one I was actively editing, and the bug still happened so it does not appear related to having multiple folders open.
The consistent error in the logs appears to be:
[2023-05-04][15:17:48][alacritty_terminal::ansi][DEBUG] [unhandled osc_dispatch]: [['1'],['.''.''e''v''/''n''t''d''s''x''t''r''a''c''t'],] at line 963

The actual text in each error changes based on what folder(s) are opened, but [alacritty_terminal::ansi][DEBUG] [unhandled osc_dispatch] and line 963 are consistently in the error messages.
The README.md file I was attempting to edit when it crashed:
README.md

[2023-05-04][15:17:48][alacritty_terminal::ansi][DEBUG] [unhandled osc_dispatch]: [['1'],['.''.''e''v''/''n''t''d''s''x''t''r''a''c''t'],] at line 963

Is an unrelated issue. It appears to be a bad recursion in find_matching_pair? Namely this function here: https://github.com/tree-sitter/tree-sitter/blob/master/lib/src/node.c#L187
Does anyone know of a tree-splitter developer that I can contact for help?


20.1 changed dhcpv6 staticmapping value domain into domainsearchlist --> auto-DNS-registration fails

[X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[X] I have searched the existing issues and I'm convinced that mine is new.
Describe the bug
In previous versions before 20.1 you could add static dhcpv6 leases and activate the option 'Register DHCP static mappings' in unbound. No need to add an extra DNS record.
In 20.1 the dhcpv6 static-leases changed the domain entry to domain-searchlist. Thus no DNS entries are created. Entries created with 19.X and migrated by upgrade to 20.1. still have the correct domain value in configuration and get registered.
ATM I manually have to download configuration, add the  XML entry and restore DHCP configuration.
Previously:
<staticmap>
        <duid>00:01:23:45:67:89:01:12:34:56:78:90:aa:bb</duid>
        <ipaddrv6>2002:db::1</ipaddrv6>
        <hostname>www</hostname>
        <descr>Webserver</descr>
        <domain>dmz.domain.tld</domain>
/staticmap>

created an AAAA record with www.dmz.domain.tld IN AAAA 2002:db::1
In 20.1:
 <staticmap>
        <duid>00:01:23:45:67:89:01:12:34:56:78:90:aa:bb</duid>
        <ipaddrv6>2002:db::1</ipaddrv6>
        <hostname>www</hostname>
        <descr>Webserver</descr>
        <domainsearchlist>dmz.domain.tld;domain.tld</domainsearchlist>
</staticmap>

To Reproduce
Create static dhcpv6 lease and activate option to register DHCP leases in unbound.
Expected behavior
Possibility to add a domain in static lease configuration and get correct DNS records auto-created by unbound.
Additional context
If really needs to set an extra domainsearch-list per host, then at least reactivate the domain option in lease configuration.
Environment
OPNsense 20.1.1-amd64
FreeBSD 11.2-RELEASE-p16-HBSD
OpenSSL 1.1.1d 10 Sep 2019

Seems to be introduced with https://github.com/opnsense/core/issues/2336, maybe better ask @maurice-w how this was intended to work. I'm not a huge fan of these application dependancies, since they always have a higher risk of breakage.
We have a couple of options available in my opinion:

Register the dns domain with the entry, which would re-add both fields as extra
Traverse the domainsearchlist items and register them all, if that makes sense.
Ditch the feature and remove the code in unbound, change description that this feature only applies to ipv4 .

Right, I didn't consider the unbound dependencies. I'll take a look.

I can't reproduce that no DNS entries are created for new static mappings. However, the system domain is used for these DNS entries, not the 'Domain search list' domain(s). @Kimotu, can you confirm?
@AdSchellevis, I suggest we re-introduce the <domain> option in the <staticmap> section of the XML and add same code to services_dhcpv6_edit.php which sets it to the first domain in the domain search list. This would avoid changes to the unbound code and maintain some backward compatibility.

@maurice-w I'm ok with that, as long as the help text explains the use-case

@maurice-w Sorry for late reply. Registering all domains in search path does not make much sense. But registering the first one is ok. But if a <domain> option exists, use it preferably for backward compatibility. I added most static leases with 19.7 and all entries have <domain> option, but no <domainsearchlist>, since it did not exist prior 20.1.
Else the upgrade process would have to rewrite the mappings, but for 20.1 this is too late.

@Kimotu, using the first domain in the domainsearchlist or the domain as a legacy fallback is exactly what #3946 does. See the discussion there. It also migrates domain to domainsearchlist if you edit a static mapping created in pre-20.1. No bulk migration though.


for suppressing warning when checked props on radio-button is missing.

trivial fix.
EnhancedSwitch requires switched property, but RadioButton may not have it, so put default value.
[Warning] Warning: Failed propType: Required prop `switched` was not specified in `EnhancedSwitch`. Check the render method of `RadioButton`.

Thanks @n-miyo


Feature

See last page user on

Adding more. Ability to see as an admin what page a user was last on. Example payment or specific product


Implement rpc annotations

This should be merged after #78 .
These are the RPCMode annotations a user can use instead of the RPCMode enum argument inside the @RegisterProperty and the @RegisterFunction annotations.
Resolves #70 .

Why do we need two ways to specify the rpc mode? I would prefer to just have one, less thing we have to support.

True. The idea was that the user can do what he prefers. Consider this case:
@IntRange(0, 100, 2)
@RegisterProperty(true, RPCMode.Master)
var foo: Int = 2

vs:
@Master
@IntRange(0, 100, 2)
@RegisterProperty(true)
var foo: Int = 2

If even more annotations wpould be added in the future we would have even more lines

I think we should only support one, I personally prefer the enums as it clearly shows the relationship of RpcMode and RegisterMethod/RegisterFunction. In my experience with maintaining libraries having a single way to do things is beneficial in the long run for maintainers. It also simplifies the entry generator as it only needs to check a single thing.

Ok I'm fine with this. I'll then close this PR and the corresponding issue. We can still add them if we decide to do this way later on.


Add new docker host connection - Server URL must be a valid URL

When I add new docker host connection , if I set the Server URL to https://<IP_ADDRESS>:2376 I get a docker error on the release  ( same as http).

2018-05-31T20:26:47.6344996Z [command]"C:\Program Files\Docker\docker.exe" -H https://<IP_ADDRESS>:2376 --tls --tlscacert='.dockercerts\ca.pem' --tlscert='.dockercerts\cert.pem' --tlskey='.dockercerts\key.pem' run -d --restart no harbor.eyalcomp.local/$(build.repository.name):$(build.buildid)
2018-05-31T20:26:47.6842294Z invalid argument "https://<IP_ADDRESS>:2376" for H: Invalid bind address format: https://<IP_ADDRESS>:2376
2018-05-31T20:26:47.6899432Z ##[error]C:\Program Files\Docker\docker.exe failed with return code: 1

The docker H option  need to by only IP and not http/s .
but i can't add only address i get "Server URL must be a valid URL

is need to be TCP://<IP_ADDRESS>:2376  not http.


[Bug] doris自动分析问题

Search before asking

[X] I had searched in the issues and found no similar issues.

Version
2.0.3-rc03
What's Wrong?
创建表后，执行insert进行数据插入，自动分析生效。
执行SHOW AUTO ANALYZE；state为FAILED，message里的内容为：Failed to execute internal SQL. org.apache.doris.common.AnalysisException: errCode = 2, detailMessage = Syntax error, Failed to execute internal SQL. org.apache.doris.common.AnalysisException: errCode = 2, detailMessage = Syntax error, Failed to execute internal SQL. org.apache.doris.common.AnalysisException: errCode = 2, detailMessage = Syntax error, Failed to execute internal SQL. org.apache.doris.common.AnalysisException: errCode = 2, detailMessage = Syntax error, Failed to execute internal SQL. org.apache.doris.common.AnalysisException: errCode = 2, detailMessage = Syntax error, Failed to execute internal SQL. org.apache.doris.common.AnalysisException: errCode = 2, detailMessage = Syntax error, Failed to execute internal SQL. org.apache.doris.common.AnalysisException: errCode = 2, detailMessage = Syntax error, Job has been cancelled: Failed to execute internal SQL. org.apache.doris.common.AnalysisException: errCode = 2, detailMessage = Syntax error, Job has been cancelled: Failed to execute internal SQL. org.apache.doris.common.AnalysisException: errCode = 2, detailMessage = Syntax error, Job has been cancelled: Failed to execute internal SQL. org.apache.doris.common.AnalysisException: errCode = 2, detailMessage = Syntax error。
SHOW  ANALYZE；show  analyze jobid;SHOW  ANALYZE TASK STATUS jobid;无法查看自动分析任务的信息
show column stats tablename(id);统计信息已经生成，但是这个sql没数据
What You Expected?
正常执行
How to Reproduce?
No response
Anything Else?
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

日志里发现一条关于统计信息一直执行的sql，SELECT CONCAT(10061,
'-',
-1,
'-',
'key') AS id,
0 AScatalog_id,
10059 ASdb_id,
10061 AStbl_id,
-1 ASidx_id,
'key' AS col_id,
NULL ASpart_id,
COUNT(1) AS row_count,
NDV(key) AS ndv,
COUNT(1)-COUNT(key) AS null_count,
CAST(MIN(key)ASSTRING) AS min,
CAST(MAX(key)ASSTRING) AS max,
SUM(LENGTH(key)) AS data_size,
NOW() AS update_time
FROM tablename;
key没有加反引号，导致无法执行

https://github.com/apache/doris/pull/27321

#27321

#27321

doris2.1.1 FE警告日志中一直在执行 这样的SQL
SELECT SUBSTRING(CAST(MIN(key) AS STRING), 1, 1024) as min,
SUBSTRING(CAST(MAX(key) AS STRING), 1, 1024) as max
FROM DB.Table index null
然后每次执行都不成功
错误为
Encountered: INDEX
Expected: COMMA, INDEX is keyword, maybe INDEX


 It seems like that's not a part of the spec. It would be nice if we could define which members are required and also some default values for members that are not provided.
A good example of this being useful is for the created_at and updated_at fields that Laravel uses by default.

I just ran into this very thing. I know I POSTed to the controller and created properly, but now it is failing with "status": 422,       "code": "unprocessable_entity",       "title": "Missing Attribute",       "detail": "Attribute created_at is missing.",       "source": {         "pointer": "/data/attributes/created_at"       }
very confused.

This is a bug.
This can be fixed at https://github.com/nilportugues/serializer-eloquent-driver for sure by checking if public $timestamps = false; field is true, and force them there.
Problem comes from the Serializer's Eloquent adapter doing all the magic for you.

Not sure if I was totally clear. I think it would be helpful to be able to specify which members are required. Maybe a getRequiredAttributes() function on the transformer would do the trick.  I'd propose the following functionality:
Default: Require all attributes.
If getRequiredAttributes() returns an array: Only require the specified attributes.
The database schema would be responsible for the default values of whatever is not required. Is there any reason this wouldn't be a good idea? It doesn't change existing default functionality, it just provides a way to configure the environment for something that's not in the spec.

@jeremymlane I like the idea.

As for now, added fix for $timestamps https://github.com/nilportugues/laravel5-jsonapi/releases/tag/2.4.2

@jeremymlane @nilportugues Are you working on something about this ? Indeed, I ran into a similar problem, and it could be great to have optional fields others than timestamps.

@nilportugues Submitted several pull requests for this one. I left it out of the interface so it can be backwards compatible with the transformers everyone has already implemented.

@jeremymlane  Only thing missing is making sure aliased properties work... and I'll close this issue


Fix flake8 invocation in .travis.yml

flake8 was invoked with '*.py tests' which was only checking
setup.py and Python files in tests/, and not checking any of
the nested_dict modules.
Use tox.ini to specify the files to be excluded, which allows
flake8 to include all other Python files found.
Fix whitespace related errors.
Ignore code E265 due to several #print.. lines.
Also simplify the invocation of the sphinx docs command in .travis.yml

I'm happy to remove the #print lines, but I suspect that some of them would be better converted into logging calls.
The remaining flakes are fixed with #5 and #6.

Thanks for all the bug fixes! The print calls were for debugging during development and are not used normally. I think logging is probably over kill.


[Bug]: The hovering display of the log is inconsistent with the design draft

ODC version
odc431
OB version

What happened?

What did you expect to happen?

How can we reproduce it (as minimally and precisely as possible)?

Execute SQL
view log

Anything else we need to know?
No response

Fixed In Commit b8310dbf525090e447de8ab108fba352e21af1e0
------
畅晚
Mon Jul 8 09:36:58 2024 +0800

pass


dataset

Can I download your datset?

This is a course project so the dataset is actually not so large. The lab dataset is available on the course website, and the baseline model's dataset (such as TOTB and Trans_10kv2 dataset) can be downloaded on their websites.

好的，谢谢，另外请问您有尝试减少识别的玻璃种类吗？

913838102
@.***

------------------ 原始邮件 ------------------
发件人: "Jiarui @.>;
发送时间: 2023年2月14日(星期二) 上午10:55
收件人: @.>;
抄送: @.>; @.>;
主题: Re: [LiJiarui111/Trans2Seg-AutoBio-Challenge] dataset (Issue #1)
This is a course project so the dataset is actually not so large. The lab dataset is available on the course website, and the baseline model's dataset (such as TOTB and Trans_10kv2 dataset) can be downloaded on their websites.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


new intel ultra cpu's NPU

Hi, Does Ktrain can use new intel ultra CPU's NPU?

Hi:  I'm not familiar with the device, but it really depends on whether TensorFlow (PyTorch) can support it.  You might checkout this reddit thread on the topic.

I read. My labtops NPU stranger than GPU as Geekbench AI benchmark.


Can't resize the height of the editor

Hi,
I'm running 0.11.8 of hover editor and whenever I try to resize the height of the editor it won't go beyond the initial size set in the settings.  It's as though it's now using the initial size as the maximum size.
Thanks,
David

Good points.  I should have checked that first.  I will check now.

My apologies.  With default theme and all other plugins disabled the issue goes away.  I will now start the hunt for the guilty party.  Sorry to bother you.

Okay, the guilty party is the Things theme (in case you were wondering).

You should let them know.  They have a max-height of 40vh set, and it's at a priority where it's overriding Hover Editor's unset max height.  So you can't make it any bigger than 40% of the screen height.


mssql-tools is not pinned in the image

mssql-tools should be pinned to the same version as the MS SQL driver.

Fixed


Hello, Any workable solution to this problem. I am trying to run it on MAC which does not have GPU and I get the errors related to GPU

Hello, Any workable solution to this problem. I am trying to run it on MAC which does not have GPU and I get the errors related to GPU
Originally posted by @csv610 in https://github.com/IDEA-Research/GroundingDINO/issues/71#issuecomment-1542293997

We support CPU mode for inference your demo with Grounded-SAM

Hello
Can we use mps on Mac m1/m2?
Thanks
Sent from Yahoo Mail for iPhone
On Tuesday, July 25, 2023, 6:56 AM, Ren Tianhe @.***> wrote:
We support CPU mode for inference your demo with Grounded-SAM
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Hello  Can we use mps on Mac m1/m2? Thanks Sent from Yahoo Mail for iPhone On Tuesday, July 25, 2023, 6:56 AM, Ren Tianhe @.> wrote: We support CPU mode for inference your demo with Grounded-SAM — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID: @.>

We did not test this situation before, maybe you can try to inference on your device to see if Grounded-SAM can work on it


Out-of-memory error for training on 80GB A100 GPUs

When I try to train the model on 80GB A100 GPUs, I still receive out-of-memory errors. Im suspecting that it has to do with differences in the package versions of my environment. Could you please run the following command on your conda environment and report the result for better reproducibility:
conda env export -n fastcomposer > environment.yml
Thank you very much!

found a solution in https://github.com/mit-han-lab/fastcomposer/issues/26#issue-2007095881

@malteprinzler Hi, do you have some insights about when will the model converge? I found it taking quite long with A100 and I wonder if lowering the train_step can offer similar performance?


Transactional outbox in scope?

For reliable domain event emission synchronized with database transactions, the transactional outbox pattern is a common solution. In https://github.com/eclipse/microprofile-reactive-messaging/issues/117 I was directed towards this proposal, which might be a candidate for describing the required interfaces to realize such an outbox. So far, I can't find any explicit references to this pattern in the specification. Do you assume that implementations handle this internally or is reliable event transmission completely out of scope for this proposal?

@languitar For version 1.0 which is going to be released in the following month we are staying with only the application level REST calls. This doesn't prohibit database interactions but they are expected to be handled by the user code.
The transactional outbox pattern integration is definitely an area that we can investigate. The integration with reactive messaging and events will be also investigated. We need to define what the relations between them should be and where the transactional outbox pattern would live.

Hey, Gunnar here from the Debezium team; I'm working on a PoC for implementing the Saga pattern based on top of the outbox pattern: https://github.com/debezium/debezium-examples/pull/140/. Perhaps it can serve as inspiration for this work here? Happy to exchange and discuss any details, if you're interested.

Hey, Gunnar here from the Debezium team; I'm working on a PoC for implementing the Saga pattern based on top of the outbox pattern: https://github.com/debezium/debezium-examples/pull/140/. Perhaps it can serve as inspiration for this work here? Happy to exchange and discuss any details, if you're interested.

Thanks Gunnar, we are interested and will be keen to discuss it with you and leverage your knowledge when we have finalised 1.0.

Thanks Gunnar, we are interested and will be keen to discuss it with you and leverage your knowledge when we have finalised 1.0.


Horovod doesn't use all GPUs

🐛 Bug
When I use horovod as an accelerator, it detects all 4 GPUs, but only uses 1 GPU instead of 4
  trainer = pl.Trainer(
      strategy="horovod",
      accelerator="gpu",
      devices=4,
      max_epochs=3,
      logger=neptune_logger,
      accumulate_grad_batches=4,
      callbacks=[checkpoint_callback],
      num_sanity_val_steps=0,
  )

To Reproduce
  trainer = pl.Trainer(
      strategy="horovod",
      accelerator="gpu",
      devices=4,
      max_epochs=3,
      logger=neptune_logger,
      accumulate_grad_batches=4,
      callbacks=[checkpoint_callback],
      num_sanity_val_steps=0,
  )

Expected behavior
All four gpus should have high utilization
Thu Aug 11 11:20:25 2022
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 510.47.03    Driver Version: 510.47.03    CUDA Version: 11.6     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  Tesla T4            On   | 00000000:00:1B.0 Off |                    0 |
| N/A   51C    P0    72W /  70W |   8081MiB / 15360MiB |    100%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  Tesla T4            On   | 00000000:00:1C.0 Off |                    0 |
| N/A   29C    P8    13W /  70W |      2MiB / 15360MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   2  Tesla T4            On   | 00000000:00:1D.0 Off |                    0 |
| N/A   30C    P8    14W /  70W |      2MiB / 15360MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   3  Tesla T4            On   | 00000000:00:1E.0 Off |                    0 |
| N/A   29C    P8    13W /  70W |      2MiB / 15360MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A     35574      C   python                           8077MiB |
+-----------------------------------------------------------------------------+

Environment

Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
PyTorch Lightning Version (e.g., 1.5.0): 1.7.1
Lightning App Version (e.g., 0.5.2):
PyTorch Version (e.g., 1.10): 1.12.1
Python version (e.g., 3.9): 3.9
OS (e.g., Linux): Amazon Linux
CUDA/cuDNN version: 10.2
GPU models and configuration:
How you installed PyTorch (conda, pip, source): pip
If compiling from source, the output of torch.__config__.show():
Running environment of LightningApp (e.g. local, cloud):
Any other relevant information:

Additional context

cc @awaelchli

@arunpatro-meesho When using Horovod with Lightning, you need to launch it with the horovodrun command. Did you do that? And devices needs to be set to 1, because horovodrun will isolate each process to one GPU only.

@arunpatro-meesho Were you able to make it work?

No it didn't work :/
On Sun, 21 Aug, 2022, 3:09 am Adrian Wälchli, @.***>
wrote:

@arunpatro-meesho https://github.com/arunpatro-meesho Were you able to
make it work?
—
Reply to this email directly, view it on GitHub
https://github.com/Lightning-AI/lightning/issues/14164#issuecomment-1221413838,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AWKAKZR3NMWCADIFER2NFLDV2FGBZANCNFSM56HZL5BA
.
You are receiving this because you were mentioned.Message ID:
@.***>

--

This communication is confidential, may be privileged, and is meant
only for the intended recipient and purpose. No part of this email or any
files transmitted with it can be shared, copied, forwarded, published
online or offline, or used in any unauthorised manner. If you are not the
intended recipient, please preserve the confidentiality of the contents,
delete the e-mail and attachments (if any) from your system, and inform the
sender immediately.

But how do I use it via code and not use horovodrun? I am building a library which would internally call Trainer api.

But how do I use it via code and not use horovodrun?

You can take a look here how we run horovodrun programatically in our tests:
https://github.com/Lightning-AI/lightning/blob/52a4457ae3f4aef81ce81d6e19cca14855c64c05/tests/tests_pytorch/models/test_horovod.py#L55-L76


Create project page: add Skills and Info Url

You can now add skills/projectRoles to a project when creating one!
Support for adding a info link.
Also toasts

Codecov Report

Merging #395 (3db3f9a) into develop (46c4245) will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop        #395   +/-   ##
=============================================
  Coverage   96.60334%   96.60334%
=============================================
  Files             79          79
  Lines           1737        1737
=============================================
  Hits            1678        1678
  Misses            59          59

Merge conflicts :o


Sudan (SD) missing address data

no data is found for Sudan (territory code SD):
https://i18napis.appspot.com/address/data/SD

Looking into this.
32446329. ai/md

Address format here: http://www.upu.int/fileadmin/documentsFiles/activities/addressingUnit/sdnEn.pdf

Seems to have been added: https://chromium-i18n.appspot.com/ssl-address/data/SD
Still missing administrative areas.

Note that SD has not moved to the gstatic pages yet:

https://chromium-i18n.appspot.com/ssl-address/data/SD - OK
https://www.gstatic.com/chrome/autofill/libaddressinput/chromium-i18n/ssl-address/data/SD - 404 error

Thanks for pointing this out, @mimckenna. Sudan was added to gstatic, but I would insist that people still use URLs like https://chromium-i18n.appspot.com/ssl-address/data/SD and not point to gstatic directly, as this case illustrates


Why are contract creators not allowed to have a nonce of 0?

Hi There,
What is wrong?
I'm trying to create a contract with an account that has a nonce of 0 and it's failing due to the address generation. I can see here that the 1 is subtracted from the sender nonce: https://github.com/ethereum/py-evm/blob/44e0ee4cb1756522ffe294a379d4735a25701003/eth/vm/forks/frontier/state.py#L68.
How can it be fixed
Is this intentional? If so, are there ways around it?

Nevermind, just realised there is an increment nonce operation before that on line 60.


Typescript tools for Visual Studio 2015 - requires restart.

Expected behavior:
I've just installed TypeScript for Visual Studio 2015.  On completion it tells me it needs to restart the entire system.  What ever for?!
Actual behavior:

Can you upload all the *typescript* log files in %temp%

This is the beta correct? Try 2.0.3.

dd_TypeScript_Dev14_20161020095157_000_TypeScript_Dev14.msi.zip
So the Beta restarted my machine.  I found the release 2.0.3 version about 10 minutes later and that didn't require a restart but I don't know if that was just because my machine had been restarted 10 minutes earlier.

Thanks, looking at the logs it looks like there was still an instance of either VS or MSBuild running, which required the reboot. (This could be an orphaned instance due to a crash). We try to kill them, but that doesn't always work.
If we don't reboot in that case you could end-up with a mix of TypeScript versions, which would be a bad experience.


Compiled with Default Target(LLVM) and Built with USE_MRVL=ON

Please review the fix:
It is a unique use-case to check the default target(LLVM), though TVM is built with BYOC(MRVL-ON)
The config of Codegen(BYOC) contains default values for configuration/optons, it is extracted
during _generate_codegen_args. In command line processing, validate_target_args checks if there are add-on options and it expects that particular target to be given explicitly in command line.  Here, it is test for default (LLVM) path only, hence validate_target_args need to ignore the codegen's configuration

@Hzfengsy @lhutton1
Could you please review this patch ?
Thanks

cc TVMC maintainer @leandron

@leandron
Please review my updated patch which has generic fix.,
The purpose of this fix is not to extract any options of codegen(BYOC) when only default target is specified by the user.
Eg:
python3 -m tvm.driver.tvmc compile  --target="llvm" model.onnx
Thanks

@leandron
Could you please merge this PR?
Thanks

@leandron
Could you please merge this PR?
Thanks

Yes, I just forgot this step after the review. This is merged now - thanks for your PR.

@leandron
Thanks a lot for your quick review feedback and response.


Fix send2cgeo script

Fix var after GC change and step up version number.
This fix must also commit to website.

This cannot be merged. Commit only send2 script.


Error: 0x80040305

Your Windows build number: 10.0.17604.1000

What you're doing and what's happening: I noticed that my default user had changed to root (I don't remember if I had done that or if I had just never noticed it before. I ran cut -d: -f1 /etc/passwd to get a list of all users and saw "bryce" at the bottom. I wanted my user to be "bthedestroyer" so I ran usermod -l bthedestroyer bryce and checked /etc/passwd again to find it changed. I then closed ubuntu and ran ubuntu config --default-user bthedestroyer from the command line and got a confirmation message, but when I went back in I was still root. I then restarted my computer and when I tried to run ubuntu this time, I get the error 0x80040305 and it instantly closes. I tried changing the default user back to root hoping that'd fix the issue but now I get Failed to set default user to: root

What's wrong / what should be happening instead: I should be able to open Ubuntu or at least change the user back to root.

lxcore_kernel.zip

@BtheDestroyer - When you attempted to change the default UID back to root was there an error?

I agree. The only error I got was Failed to set default user to: root

I think we should relax this error path

That or add a --userspec commandline parameter. Which get you another step closer.

@BtheDestroyer - I'm not sure where that error message is coming from, I guess ubuntu.exe's code.

My solution to get Ubuntu back running again was to copy out the files I needed from C:\Users\%USERNAME%\AppData\Local\Packages\CanonicalGroupLimited.UbuntuonWindows_79rhkp1fndgsc\LocalState\rootfs, uninstall Ubuntu, reinstall it, and copy the files back in. Works, but this probably shouldn't be something that happens in the first place.

Agreed. I submitted a mitigation for this yesterday which will fall back to root if there is a problem with parsing the /etc/passwd file.

Can bash run without /etc/passwd?

Yes, but the way WSL sets up environment uses /etc/passwd similar to the login binary. After my change a missing passwd file won't prevent launching.

Can you share what do you change? Or close-source 🤐

The change is in our init daemon which is closed-source, maybe someday we can open it up.  I can describe the change at a high level though:
1. Call getpwuid for default UID, if success goto 4
2. Call getpwuid for root UID, if success goto 4
3. Initialize a default passwd structure with some sane defaults (root, /bin/sh, etc).
4. Launch shell from passwd structure

This change is now available in the Skip-ahead 17627 build.

wsl.exe can't open without passwd but bash.exe can. Is it normal?

I had a similar issue. I set it to root to reset my Kali password, then I went to set it back. I ran cat /etc/passwd to get my user ID, then I went to the registry editor and changed the default UID to 1000. Of course, it didn't work, and I got error 0x80040305. So I went back, switched it to decimal, not hexadecimal 1000, and it worked. I know hex 0 and decimal 0 are the same but that might fix it.


Remove the ability to add an empty field

Change the comment in submission. Now comments are added even if there are no comments in the corresponding field

I fixed it


Bug fix ResNet-50

Reverted sequence of to_hls transformations to get rid of all Transpose nodes.

Verified that all layers are converting successfully to HLS layers once again. Thanks @mmrahorovic !


Impossible to json_encode Subclass of Primitive Types

Checks

[x] I added a descriptive title to this issue
[x] I have searched (google, github) for similar issues and couldn't find anything
[x] I have read and followed the docs and still think this is a bug

Bug
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.8.1
            pydantic compiled: True
                 install path: /home/cwu/.cache/pypoetry/virtualenvs/magic-nixJrDdi-py3.9/lib/python3.9/site-packages/pydantic
               python version: 3.9.4 (default, Apr  4 2021, 19:38:44)  [GCC 10.2.1 20210401]
                     platform: Linux-5.11.0-13-generic-x86_64-with-glibc2.33
     optional deps. installed: ['devtools', 'email-validator', 'typing-extensions']

As of the following code, I would expect json-encoded values "str" and "my_str", but got "" instead.
from pydantic import BaseModel as PydanticBaseModel

class MyStr(str):
    ...

class BaseModel(PydanticBaseModel):
    class Config:
        # XXX: json_dumps does not work, either
        json_encoders = {
            str: lambda _: 'str',
            MyStr: lambda _: 'my_str',
        }

class WithCustomEncoders(BaseModel):
    a: str
    b: MyStr

m = WithCustomEncoders(a='', b='')
print(m.json())
# {"a": "", "b": ""}

print(type(m.b))
<class 'str'>

The root cause is an instance of a subclass of a primitive type degenerates into the primitive type.

Actually a duplicate of https://github.com/samuelcolvin/pydantic/issues/1245


feat: Add pre-commit & CONTRIBUTING.md

What this PR does:
Add pre-commit & CONTRIBUTING.md
Which issue(s) this PR fixes:

Fixes #289
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

[pre-commit hooks]
- imports-formatter
- license-eye
- golangci-lint

Codecov Report

Merging #353 (89047d7) into master (4db8eda) will increase coverage by 0.00%.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #353   +/-   ##
=======================================
  Coverage   39.46%   39.46%
=======================================
  Files         111      111
  Lines       14764    14764
=======================================
+ Hits         5826     5827    +1
+ Misses       8223     8222    -1
  Partials      715      715

Impacted Files
Coverage Δ

pkg/dataset/priority_queue.go
66.66% <0.00%> (+1.11%)
:arrow_up:

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


Update eventing examples with Knative service sinks

Currently, eventing samples use Kubernetes deployment as sinks. We should also show Knative service as sinks.

Fixed in the latest commit


LiveFyre comment on Dependency Versions

https://docs.microsoft.com/en-us/nuget/create-packages/dependency-versions#comments-container
April 4 2017
Sometimes we have alpha/beta package version like 2.0-beta. It would be great for the doc to clarify whether [1.0,2.0) will resolve as 2.0-beta if 2.0-beta is the latest version. Thanks.

There's a Note callout on the page that explains how pre-release versions are applied with ranges (not) and wildcards (yes). Plus the comment itself disappeared when the topic got renamed.


Add [GBI7SAXJOO2VLMQ5AGKYKN5KQ4E2KBWUGCYM5TPPZF7HXPYJWZ] #wallet GBI7SA…BETMQO

Address: GBI7SAXJOO2VLMQ5AGKYKN5KQ4E2KBWUGCYM5TPPZF7HXPYJWZBETMQO
Tags: wallet
Title: GBI7SAXJOO2VLMQ5AGKYKN5KQ4E2KBWUGCYM5TPPZF7HXPYJWZ
Requested by @jesse6484

GBI7SAXJOO2VLMQ5AGKYKN5KQ4E2KBWUGCYM5TPPZF7HXPYJWZBETMQO

Hello @jesse6484,
I'm not sure what you are reporting or requesting. It sounds like you are asking for a personal wallet to be labelled on our stellar.expert database but with over 7 million wallets on the Stellar blockchain we are not actually able to do that. I am sure you understand.
Looking Towards The Future With You,
Rob TheCryptoHobbyist


Add migration script

Purpose
Fix database inconsistency that prevents some users from logging in. Update the data for users who have non-null values of date_last_login and null values of date_confirmed such that date_confirmed = date_last_login and is_registered = True iff it's not already set to True.
Closes https://github.com/CenterForOpenScience/osf.io/issues/1462
Changes
Migration script added
Side Effects
date_confirmed will almost certainly not be the exact time that they confirmed via email.

Can you also log out the count of migrated records (in both dry and non-dry mode)?

The logged output should be the same between dry and non-dry mode. The only difference is that dry run mode should not perform any database changes and not log to a file.

1st pass finished. :football:

Also, can you please resend this as a hotfix?

Done. See https://github.com/CenterForOpenScience/osf.io/pull/1513


ApiController attribute - Enforcing 415 Unsupported Media Type with bad Content-Type

From @YouvalLabade on August 4, 2018 20:32
With the attribute [ApiController] how to return a 415 Unsupported Media Type if the Content-Type is incorrect or unsupported?
Should we do something like this ?
services.Configure<ApiBehaviorOptions>(config =>
{
	config.InvalidModelStateResponseFactory = (actionContext) =>
	{
		var errors = actionContext.ModelState.Values.SelectMany(modelState => modelState.Errors);

		if(errors.Any(modelError => modelError?.Exception?.GetType() == typeof(UnsupportedContentTypeException)))
		{
			return new StatusCodeResult(StatusCodes.Status415UnsupportedMediaType);
		}

		return new BadRequestResult();
	};
});

Copied from original issue: aspnet/Home#3387

@Youuuuuuuuuuu that's a reasonable workaround for now. However it does seem like a bug that the framework does not correctly handle this for you. I'll try bringing this up for patch consideration.

cc @YouvalLabade

cc @rynowak \ @dougbu.
The current instance of UnsupportedContentTypeFilter isn't ordered and is consequently has an implicit order of 0, Scope = Global. ModelStateInvalidFilter that ApiBehaviorApplicationModelProvider adds to actions is Order = -2000, Scope = Action. It runs prior to UnsupportedContentTypeFilter and ends up producing a BadResult instead of a UnsupportedMediaTypeResult.
We could
a) make UnsupportedContentTypeFilter ordered and give it a default order that is earlier than ModelStateInvalidFilter. Users could change it they are broken by it.
b) make UnsupportedContentTypeFilter ordered. Leave the global one as is (so it continues to have an order of 0). Add a second one in ApiBehaviorApplicationModelProvider if we're also adding ModelStateInvalidFilter. Limits the order change to ApiController instances that are the ones primarily affected by this issue.
c) Make UnsupportedContentTypeFilter a resource filter (in addition to being an IActionFilter)? Checking for a formatting failure seems like a resource filter concern. <-- Least patch-worthy solution.

What other StatusCode-setting filters do we have? Don't want ModelStateInvalidFilter interfering with an AuthorizeFilter (for example) either. (Might imply this issue is better handled together with #7125.)
Another alternative would be to make StatusCode-setting filters more aware of each other. They could no-op when a "more specific" StatusCode may be set later or even invoke later setters before doing their own work. Throwing this out but likely this is too fragile and complicated to be worthwhile; it also introduces an implicit ordering that confusingly overrides the usual Order.
Whatever the case, I agree a filter that sets StatusCode to something fairly generic like BadRequest should not supercede one that sets StatusCode to UnsupportedContentType, MethodNotAllowed or ImATeaPot.

I'm not sure that c) is even valid. A resource filter would run before model binding, so we wouldn't be able to see the error.
I'm in favor of a) because it's the simplest to reason about.


Feature request

Hey, everyone. thank you for this github action.
Is there a way to pass a parameter to the Azure Pipeline we want to call??
I want to call an Azure Pipeline only after the semantic release is generated here on github so when calling the Azure Pipeline, I want to tell it to use an specific variable value containing the latest github release generated to put a footer information on my website.(eg.: v1.5.12)
Again, thank you for this.

+1. I have a similar request. The pipeline I'm triggering has a variable I want to set when triggering it.

+1 also looking to be able to set a variable in the pipeline build since we want to use this for triggering releases from the GH Deployments.

👋  @N-Usha - any word on when eg. https://github.com/Azure/pipelines/pull/18 or https://github.com/Azure/pipelines/pull/11 could get merged? We've had to maintain a fork of this action for several months now, and speaking frankly I went from being very happy to find this action which demonstrates willingness to integration Github and DevOps Pipelines, to now being quite disappointed to see two seperate contributions of a rather small and valuable feature go stale :(

+1 We would also find this useful.

+1
Looking a way to run Azure DevOps pipeline when there is a new pull request in GitHub, or a change in any of the feature branches.

+1
Looking a way to run Azure DevOps pipeline when there is a new pull request in GitHub, or a change in any of the feature branches.

@N-Usha could you take a look?


Train fail. Error occurred when executing InitFluxLoRATraining:  Cannot copy out of meta tensor; no data!

The first time train lora only because comfyUI is easy to use. Copy dataset to ComfyUI folder.

Got the following errors.
>  !!! Exception during processing!!! Cannot copy out of meta     execution.py:180
>                              tensor; no data! Please use torch.nn.Module.to_empty() instead
>                              of torch.nn.Module.to() when moving module from meta to a
>                              different device.
>                     ERROR    Traceback (most recent call last):                             execution.py:181
>                                File "F:\ComfyUI_flus\ComfyUI\execution.py", line 152, in
>                              recursive_execute
>                                  output_data, output_ui = get_output_data(obj,
>                              input_data_all)

I'm getting the same error (Comfy and all extension are updated)
Error occurred when executing InitFluxLoRATraining:
Cannot copy out of meta tensor; no data! Please use torch.nn.Module.to_empty() instead of torch.nn.Module.to() when moving module from meta to a different device.
File "D:\ANEWCOMFY\ComfyUI_windows_portable\ComfyUI\execution.py", line 317, in execute
output_data, output_ui, has_subgraph = get_output_data(obj, input_data_all, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\ANEWCOMFY\ComfyUI_windows_portable\ComfyUI\execution.py", line 192, in get_output_data
return_values = _map_node_over_list(obj, input_data_all, obj.FUNCTION, allow_interrupt=True, execution_block_cb=execution_block_cb, pre_execute_cb=pre_execute_cb)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\ANEWCOMFY\ComfyUI_windows_portable\ComfyUI\execution.py", line 169, in _map_node_over_list
process_inputs(input_dict, i)
File "D:\ANEWCOMFY\ComfyUI_windows_portable\ComfyUI\execution.py", line 158, in process_inputs
results.append(getattr(obj, func)(**inputs))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\ANEWCOMFY\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-FluxTrainer\nodes.py", line 336, in init_training
training_loop = network_trainer.init_train(args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "D:\ANEWCOMFY\ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-FluxTrainer\train_network.py", line 377, in init_train
vae.to(accelerator.device, dtype=vae_dtype)
File "D:\ANEWCOMFY\ComfyUI_windows_portable\python_embeded\Lib\site-packages\torch\nn\modules\module.py", line 1173, in to
return self._apply(convert)
^^^^^^^^^^^^^^^^^^^^
File "D:\ANEWCOMFY\ComfyUI_windows_portable\python_embeded\Lib\site-packages\torch\nn\modules\module.py", line 779, in _apply
module._apply(fn)
File "D:\ANEWCOMFY\ComfyUI_windows_portable\python_embeded\Lib\site-packages\torch\nn\modules\module.py", line 779, in _apply
module._apply(fn)
File "D:\ANEWCOMFY\ComfyUI_windows_portable\python_embeded\Lib\site-packages\torch\nn\modules\module.py", line 779, in _apply
module._apply(fn)
[Previous line repeated 3 more times]
File "D:\ANEWCOMFY\ComfyUI_windows_portable\python_embeded\Lib\site-packages\torch\nn\modules\module.py", line 804, in _apply
param_applied = fn(param)
^^^^^^^^^
File "D:\ANEWCOMFY\ComfyUI_windows_portable\python_embeded\Lib\site-packages\torch\nn\modules\module.py", line 1166, in convert
raise NotImplementedError(

This was because we were using the diffusers version of the VAE , switch to this VAE https://huggingface.co/black-forest-labs/FLUX.1-dev/blob/main/ae.safetensors thanks Kijai for solving the issue :)

This was because we were using the diffusers version of the VAE , switch to this VAE https://huggingface.co/black-forest-labs/FLUX.1-dev/blob/main/ae.safetensors thanks Kijai for solving the issue :)

I get the same error regardless even after downloading the VAE from that link.

This was because we were using the diffusers version of the VAE , switch to this VAE https://huggingface.co/black-forest-labs/FLUX.1-dev/blob/main/ae.safetensors thanks Kijai for solving the issue :)

I get the same error regardless even after downloading the VAE from that link.

Similarly check that the other models are correct, the error definitely is related to them. Which ones are you trying to use?

This was because we were using the diffusers version of the VAE , switch to this VAE https://huggingface.co/black-forest-labs/FLUX.1-dev/blob/main/ae.safetensors thanks Kijai for solving the issue :)

I get the same error regardless even after downloading the VAE from that link.

Similarly check that the other models are correct, the error definitely is related to them. Which ones are you trying to use?

Yeah, you're right. I tried a different one and it worked (fp16). I don't remember which is which to be honest because I downloaded a few, but I first tried with the fp8 version and it didn't work. But that might've been one downloaded from civitai. Where should I download the fp8 version from?

This was because we were using the diffusers version of the VAE , switch to this VAE https://huggingface.co/black-forest-labs/FLUX.1-dev/blob/main/ae.safetensors thanks Kijai for solving the issue :)

I get the same error regardless even after downloading the VAE from that link.

Similarly check that the other models are correct, the error definitely is related to them. Which ones are you trying to use?

Yeah, you're right. I tried a different one and it worked (fp16). I don't remember which is which to be honest because I downloaded a few, but I first tried with the fp8 version and it didn't work. But that might've been one downloaded from civitai. Where should I download the fp8 version from?

https://huggingface.co/Kijai/flux-fp8/blob/main/flux1-dev-fp8.safetensors

This was because we were using the diffusers version of the VAE , switch to this VAE https://huggingface.co/black-forest-labs/FLUX.1-dev/blob/main/ae.safetensors thanks Kijai for solving the issue :)

I get the same error regardless even after downloading the VAE from that link.

Similarly check that the other models are correct, the error definitely is related to them. Which ones are you trying to use?

Yeah, you're right. I tried a different one and it worked (fp16). I don't remember which is which to be honest because I downloaded a few, but I first tried with the fp8 version and it didn't work. But that might've been one downloaded from civitai. Where should I download the fp8 version from?

https://huggingface.co/Kijai/flux-fp8/blob/main/flux1-dev-fp8.safetensors

Thank a lot. It works after using model you suggested.
But too much VRAM! Anyway to reducing it?

This was because we were using the diffusers version of the VAE , switch to this VAE https://huggingface.co/black-forest-labs/FLUX.1-dev/blob/main/ae.safetensors thanks Kijai for solving the issue :)

I get the same error regardless even after downloading the VAE from that link.

Similarly check that the other models are correct, the error definitely is related to them. Which ones are you trying to use?

Yeah, you're right. I tried a different one and it worked (fp16). I don't remember which is which to be honest because I downloaded a few, but I first tried with the fp8 version and it didn't work. But that might've been one downloaded from civitai. Where should I download the fp8 version from?

https://huggingface.co/Kijai/flux-fp8/blob/main/flux1-dev-fp8.safetensors

Thank a lot. It works after using model you suggested. But too much VRAM! Anyway to reducing it?

If you are using the default settings it shouldn't use that much. Some people have said it helps to upgrade pytorch to 2.4.0 minimum, so if you are on 2.3.x then that could be the issue.

Up torch to 2.4. The VRAM usage downgrade to 17G.


Convert @EntityListeners annotation to attribute

Somehow there is a bug in AnnotationToAttributeRector that causes it not to work. No idea what it is.

please rebase.

@samsonasik Done, please approve workflow

This repository is only using rule from rector-src repository.
The right place for this test is in https://github.com/rectorphp/rector-src in AnnotationToAttributeRectorTest

Thanks :+1:


Custom queryAttribute - missing options labels

This is  a bug.

Prerequisites

[x] Are you running the latest version?
[x] Are you reporting to the correct repository?
[x] Did you check the documentation?
[x] Did you perform a cursory search?

Description
Problem:
Select options are missing names(labels).
I'm trying to create a simple form where 1-n relations are set.
I have a "Group" model, where a FK "permission_group_id" can be set.
For this I tried using a select field with the options from the "PermissionGroup" controller
/app/Http/Controllers/Models/Permissiongroups/Options.php
`
class Options extends Controller
{
use OptionsBuilder;
protected $model = PermissionGroup::class;

protected $queryAttributes = ['permission_group_name'];

public function query(Request $request)
{
    return PermissionGroup::query();
}

}
/app/Forms/Templates/Models/group.json
{
"routePrefix": "models.groups",
"sections": [
{
"columns": 2,
"fields": [
{
"label": "Permission Group Id",
"name": "permission_group_id",
"value": null,
"meta": {
"type": "select",
"multiple": false,
"options": [],
"source": "models.permissiongroups.options"
}
},
{
"label": "Group Name",
"name": "group_name",
"value": null,
"meta": {
"custom": false,
"type": "input",
"content": "text",
"disabled": false
}
}
]
}
]
}
`
/app/Tables/Builders/Models/GroupTable.php
`
class GroupTable extends Table
{
protected $templatePath = DIR.'/../../Templates/Models/groups.json';
public function query()
{
    return Group::selectRaw('
        groups.id as "dtRowId",
        groups.permission_group_id as "dtRowPermissionGroupId",
        groups.group_name as "dtRowGroupName"
    ');
}

}
`
I think the problem is the deviation from the default "name" queryAttribute which is expected, and in my situation the "name" which should be used as select option label is called "permission_group_name"
Ajax call is returning a valid JSON ;

Steps to Reproduce
Create a Select field which uses the options of a different model which has no "name" column.
Expected behavior
To see the options generated in the options
Actual behavior
Options are generated but without a name

docs

label - string, optional, default name - the attribute that is to be used as label from the result/options list

the front end component needs this attribute. If you're using enso-form / vue-form you should add  "label": "permission_group_name" to the field's meta object

docs

label - string, optional, default name - the attribute that is to be used as label from the result/options list

the front end component needs this attribute. If you're using enso-form / vue-form you should add "label": "permission_group_name" to the field's meta object

Nice! Thank you. I'm still getting familiar to things, had thought that the select documentation should have contained this detail, although makes perfect sense to be a front-end thing... duuh..
Now I know! Have a good weekend.

The link is from the select documentation, but the FE part :)

The link is from the select documentation, but the FE part :)

<synapses firing>


refactor example sources task to use DataSourceAPI

fix GEARPUMP-192Refactor example sources task to use DataSourceAPI.

please modify the commit comment to the format "[GEARPUMP-XXX] xyz"

also, please fix the UT failure

Current coverage is 69.63% (diff: 100%)

Merging #78 into master will increase coverage by 1.02%

@@             master        #78   diff @@
==========================================
  Files           177        177
  Lines          5927       5927
  Methods        5604       5606     +2
  Messages          0          0
  Branches        323        321     -2
==========================================
+ Hits           4066       4127    +61
+ Misses         1861       1800    -61
  Partials          0          0

Powered by Codecov. Last update 529799c...d8f0838

+1


Sources overview should not be limited to 4 sources

At this moment max 4 sources are shown in the overview of the consulted sources.
The right amount of sources is still shown in the summary, but we cannot get any details of the 5th, 6th ... source.

This is not true, my mistake


fix(semantic): generic passed to typeof not counted as a reference

close: #4495

#4499  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @Dunqing and the rest of your teammates on  Graphite


[GalacticScale 2.1.9] Unable to land on a planet

Unable to land on a planet Kusomonmon - XV - I (an Ice planet satellite of an Ice Giant) - Mecha just slips through it even at a small speed.
The cluster is the same as in this issue.

Same issue here, cannot land on a moon. It seems like its too close to its Ice Giant, when I'm about to land my minimap indicates that I'm on the ice giant and the moon surfaces does not load.
I attached my config and the save file right before landing.
Preferences.zip
Planet won't load - before landing.zip

Should be fixed in 2.1.13 :)

Encountering the same issue in <IP_ADDRESS> with DSP <IP_ADDRESS>89. Any body that is the satellite of a gas or ice giant simply cannot be landed on. I tried to land on half a dozen of these types of moons all over the cluster and simply fly right through them at any speed. The game seed was 72736089-64-A10, although when I put this seed in again to regenerate I got a different cluster configuration with different planet names for some reason.

<IP_ADDRESS> should fix this


[4.x] Customize the response factory class in the slim http psr17 factory

Hi there
In order to be able to set the Response Factory Class (which defaults to Slim\Http\Factory\DecoratedResponseFactory) in \Slim\Factory\Psr17\SlimHttpPsr17Factory, we should add a new static method setResponseFactory(string $responseFactoryClass).
See also https://github.com/slimphp/Slim-Http/issues/95.

The possibility to customize the response factory class in the slim http psr17 factory (i.e. to customize the http decorator) should be mentioned in the docs. Where would it make sense?


@floating-ui/react 0.18.0 and up missing @floating-ui/dom dependency causing issues with Yarn PnP

Change introduced here: https://github.com/floating-ui/floating-ui/compare/%40floating-ui/react%400.17.0...%40floating-ui/react%400.18.0#diff-1cee8646d2cfba37d6ce6a6e9a8d16f8caba0b99fc3a1ad0cb997ed8c7384d2e
@floating-ui/dom needs to be added as a dependency to @floating-ui/react.

Importing them from react-dom instead of dom should work the same, PR is welcome if you want


Narrowing on assignment does not remove weak types

Filing an issue to track the regression from #26143 described in https://github.com/Microsoft/TypeScript/pull/26143#issuecomment-412156267.

TypeScript Version:  master (fe387cc7f0739256337771e62398a565fbcf82c1)

Search Terms: narrow assignment weak type assignable comparable
Code
type AOrArrA<T> = T | T[];
const arr: AOrArrA<{x?: "ok"}> = [{ x: "ok" }]; // weak type
arr.push({ x: "ok" });  // Error: Property 'push' does not exist on type 'AOrArrA<{ x?: "ok"; }>'.

Expected behavior: No error.
Actual behavior: Error as indicated above.
Playground Link: N/A, playground is not affected
Related Issues: #26143

@ahejlsberg tentatively tagging Bug but we'll figure out what we really want to do

Continuing the work toward a solution from https://github.com/Microsoft/TypeScript/pull/26143#issuecomment-412198200:
I tried:

Narrowed type = intersection of declared and assigned types: Fails with let foo: Foo[] = [], where the narrowed type is never[] even after a push.
Narrowed type = minimal sub-union of declared type to which assigned type is assignable: Picks an arbitrary union constituent when the assigned type is any.  Even if we fixed that somehow, let foo: {a: number} | {b: number} = {a: 1, b: 2} would arbitrarily pick one of the two union constituents, an undesirable loss of symmetry.

So I think it's most practical to just fix weak types.  To recap, we want to (1) decompose unions on the source side, (2) consider the constraints of indexed access types on the source side and decompose unions again after doing so, and (3) check for weak types.  The old implementation did (1) and (3) but not (2); the one from #26143 does (1) and (2) but not (3).  ISTM it's going to be awkward to get (2) without building on the existing checkTypeRelatedTo code.  Thus, I think the best way we can get (1), (2), and (3) is to add a new relation that is the same as the comparable relation but checks for weak types; I propose to name it the "narrowable" relation.  I'll submit a PR to do this.  I hesitate to add a new relation, but it's just a matter of replacing each of the ~10 occurrences of relation === comparableRelation with relation === comparableRelation || relation === narrowableRelation except for the one for weak types.

Proposed fix is at #26425.

Per #26518, we'll revert the changes in #26143

Wait, I have another idea: use the old algorithm but if it messes up and produces a narrowed type to which the assigned type is not assignable (as in #26130), then skip narrowing and use the declared type.  I updated #26405.
By the way, another example that confuses the old algorithm (playground):
// Enable strictNullChecks
function test<T extends number | string>(arg: null | T) {
  let x: null | number | string = arg;
  if (x == null)
    return;
  x;  // never
}


List Bevy at wgpu-rs website under their showcase section

Would be nice to list Bevy on their showcase: https://wgpu.rs

Done!


fix(helm): allows extra top-level properties

SUMMARY
When our Helm Chart is used in composition additional properties might be added extra properties than defined by us eg. global, enabled. In #18161 we restricted available properties with comment:

I can see that overwhelmingly required fields may appear now. Removing these requirements requires very careful verification in multiple parameters that the Helm Chart is prepared to render without the parameter, which I intend to do when we work on the rendering tests. (...)
I think it's better to agree on the structure and notation of the schema and then relax & extend when working with Helm Chart is less fragile (more tests added).

To avoid scenario like that in future we should add that scenario to tests in #18127 .

Example error:
▶ helm install superset-v2 . -f values.yaml --dry-run > deploy-logs.yaml
coalesce.go:162: warning: skipped value for extraEnv: Not a table.
Error: INSTALLATION FAILED: values don't meet the specifications of the schema(s) in the following chart(s):
superset:
- (root): Additional property global is not allowed
- (root): Additional property enabled is not allowed

values.yaml content:
superset:
  enabled: true
  #image:
  #  repository: apache/superset
  #  tag: 1.4.0
  postgresql:
    # Create postgres locally for development purposes only.
    enabled: true

Chart.yaml content:
apiVersion: v2
name: superset
description: A Helm chart for Superset

type: application
version: 0.0.1
appVersion: 1.14.0

dependencies:
- name: superset
  repository: https://apache.github.io/superset
  version: 0.5.5
  condition: superset.enabled

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

N/A
TESTING INSTRUCTIONS

We need tests deploy with Chart.yaml and values.yaml provided above.
ADDITIONAL INFORMATION

[ ] Has associated issue: no, reported by Slack
[ ] Required feature flags: no
[ ] Changes UI: no
[ ] Includes DB Migration (follow approval process in SIP-59): N/A

[ ] Migration is atomic, supports rollback & is backwards-compatible: N/A
[ ] Confirm DB migration upgrade and downgrade tested: N/A
[ ] Runtime estimates and downtime expectations provided: N/A

[ ] Introduces new feature or API: no
[ ] Removes existing feature or API: no

I had just hit this issue, the suggested changes allow for correct configuration of helm charts as a dependency on other charts.
Thank you for fixing this Adam!


ipv6 support

Hello!
I can not connect to database using ipv6 address (which is requirement of Apple now).

Duplicate of #37. Use the format XXXX:XXXX:X:X::X:XXXX

Hello, Thank you for answer!
Ipv6 is now working correctly.
Looking forward for further development of SQLClient :)
Alexey

13 июня 2017 г., в 18:22, Martin Rybak<EMAIL_ADDRESS>написал(а):
Duplicate of #37. Use the format XXXX:XXXX:X:X::X:XXXX
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I appreciate it! When you have a chance, please test out the types branch. Lots of changes in there, including proper data type conversions.

I tried updates branch, had exceptions which I can't understand yet.
Will try types soon.

13 июня 2017 г., в 18:36, Martin Rybak<EMAIL_ADDRESS>написал(а):
I appreciate it! When you have a chance, please test out the types branch. Lots of changes in there, including proper data type conversions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


[5.9][Macros] Suppress the conformance macro diagnostic in swiftinterfaces.

(cherry picked from commit e461c25fa5e677b1fc1869cd49428ef7b52ef3cc)

@swift-ci please test


Document Frequency Project directory structure

Document the purpose of main directories and files, so it's easier for developers to understand what code goes where, thus keeping the structure cleaner and easier to maintain.
I will capture the structure in the Wiki section first https://github.com/LibertyDSNP/frequency/wiki/Directory-Structure, but it can be later moved to the Frequency documentation site, if more appropriate.

@demisx It likely needs to mention the Polkadot JS API library as it doesn't really do anything without that.

That works. Perhaps a link to the Readme as well?


Re-add rebar3_hank once it gets OTP 27 -ready

As-is, it's crashing with stuff like
===> exit analyzing files: badrpc
Stack: [{rpc,check,2,[{file,"rpc.erl"},{line,1131}]},
        {timer,tc,2,[{file,"timer.erl"},{line,590}]},
        {hank,analyze,5,
              [{file,"..."},
               {line,32}]},

This'll most likely fix it for us: https://github.com/inaka/katana-code/pull/83. A local test showed it did. So we'll wait for review+merged+tag+release+publish.


Feature request: merging YAML lists

For example, I encountered the following situation:
_exe-ghc-options: &exe-ghc-options
  - -O2
  - -threaded
  - -rtsopts
  - -with-rtsopts=-N

executables:
  mypackage:
    ghc-options: *exe-ghc-options
    ghc-prof-options:
      *exe-ghc-options
      - -with-rtsopts="-N -p"

Since the exe-ghc-options approach produces a nested list, this cause a parse error at ghc-prof-options. I guess that hpack have been using YAML for removing redundancies. But It's seems that the YAML specification do not allow us to merge lists.
(https://stackoverflow.com/questions/24090177/how-to-merge-yaml-arrays)
The finer grained the project is, the more helpful it is. So could we implement merging lists in some way?
Thank you for your time and effort!

Alternatively, we could allow every list to be a hash instead. Related: https://github.com/sol/hpack/issues/186

Seriously though, supporting hashes for GHC options might be nice. It could help with problems like #182 too.
ghc-options:
  -with-rtsopts: -N

https://github.com/sol/hpack/issues/194#issuecomment-329560341 seems good.  But, we should think about some cases and make the translating semantics more clearly.
In a easy case, it translates from
ghc-options: &base-ghc-options
  -Wall: true
  -rtsopts: true
  -threaded: true
  -with-rtsopts: -N

ghc-prof-options:
  <<: *base-ghc-options
  -Wall: false
  -with-rtsopts: -N -p

to
ghc-options: "-Wall" "-rtsopts" "-threaded" "-with-rtsopts=-N"
ghc-prof-options: "-rtsopts" "-threaded" "-with-rtsopts=-N -p"

This semantics is simple:

<option>: true => "<option>"
<option>: false =>
<option>: <parameter> => "<option>=<parameter>"

However, if we use -O2 and -O0 options, how to behave for merging?
ghc-options: &base-ghc-options
  -O2: true

ghc-prof-options:
  <<: *base-ghc-options
  -O0: true
  # Should we write `-O2: false` ?

P.S. if there's no idea for the several cases, I will write a PR to support hash options with above simple translation.

Alternatively, we could allow every list to be a hash instead.

Before considering this I want to see if #211 will help the situation.

Before considering this I want to see if #211 will help the situation.

I think that's an entirely different usecase. Mine was using yaml anchors/aliases as macros for things like test suites, groups of dependencies, etc. Unfortunately I no longer use Haskell at work so I haven't had a chance to use these macros for long enough to have any sort of insight into how it ought to work. :-(

I think that's an entirely different usecase.

I think so, too.
And, hash styles have affinity with YAML.  Because my custom options tend to be complex, I agree with hash supports for option fields.  (About me, that's enough.)

I just started using hpack, so I'm not sure if my question is related to this issue.
I'd like to merge include, global and subsection field (dependencies in particular).
Something like this:

include.yaml

- &def-deps
  dependencies:
    - bytestring

package.yaml

_default-opts: !include "../include.yaml"

<<: *def-deps
dependencies:
   - text
...
library:
  dependencies:
    - containers

So the library stanza in generated app.cabal would look like this:
library:
  dependencies:
    - bytestring
    - containers
    - text

Is it even possible to do something like this now (with some special syntax), or not and related to this issue?

@vlatkoB This can be achieved with defaults, see https://github.com/sol/hpack#defaults.
Example:
# include.yaml
dependencies:
- bytestring

# package.yaml
name: foo

defaults:
  local: include.yaml

dependencies:
- text

library:
  dependencies:
  - containers

@sol Thanks, that worked. Obviously, I wasn't reading carefully enough because I somehow understood defaults is some kind of new include. :-(
Lots of word "defaults" in reference. However, now that I read it again, all seems clear.

The original feature request can be achieved today, without any modifications to hpack:
_exe-ghc-options: &exe-ghc-options
  - -O2
  - -threaded
  - -rtsopts

executables:
  mypackage:
    main: Main.hs
    ghc-options: *exe-ghc-options
    ghc-prof-options: *exe-ghc-options
    when:
      condition: true
      ghc-options: -with-rtsopts=-N
      ghc-prof-options: -with-rtsopts="-N -p"

This will produce:
executable mypackage
  main-is: Main.hs
  other-modules:
      Paths_foo
  ghc-options: -O2 -threaded -rtsopts
  ghc-prof-options: -O2 -threaded -rtsopts
  if true
    ghc-options: -with-rtsopts=-N
    ghc-prof-options: -with-rtsopts="-N -p"
  default-language: Haskell2010

As a side note, it's best not to assume any ordering guarantees until we figured out how to deal with https://github.com/sol/hpack/issues/255.  This is why I moved -with-rtsopts=-N into the conditional.


How to install this plugin in a docker container

Hi,
I do have a node-red docker container.
How can I install this in a docker container? I did not find a how to in the wiki or via Google.
Have you guys any tips?
my docker-compose.yml looks like this:
---
services:
  nodered:
    image: nodered/node-red
    container_name: nodered
    user: "1004"
    restart: unless-stopped
    ports:
      - 'LOCAL_IP:1180:1880'
    volumes:
      - /docker/nodered/container_data/:/data

I would offer 3 different ways to achieve this:

Install it from the UI by using the Node-RED manage palette

Execute the installation within the docker container using:
docker-compose exec nodered bash
Then navigate to data directory and run:
npm install node-red-contrib-amazon-echo

Use an init container which will install the module before starting the Node-RED service.

version: '3'
services:
  nodered:
    image: "nodered/node-red:latest"
    environment: {}
    ports:
      - "1880:1880"
    volumes:
      - type: bind
        source: ./data
        target: /data/
    restart: unless-stopped
    depends_on:
      nodered-init:
        condition: service_completed_successfully

  nodered-init:
    image: "nodered/node-red:latest"
    volumes:
      - type: bind
        source: ./data
        target: /data/
    entrypoint:
      - "/bin/sh"
      - "-c"
      - "cd /data && npm install node-red-contrib-amazon-echo"

Thanks for the fully automated option nr 3.
Although the other options will achive the same result I highly prefer the option 3 as it is fully automatic .
I do have some issues with this option however.  I hope you can give me a hint to a solution.
This is my compose file:
services:
  nodered:
    image: "nodered/node-red:latest"
    #environment: {}
    user: "1004"
    ports:
      - 'LOCALIP:1180:1880'
    volumes:
      - type: bind
        source: /docker/nodered/container_data/
        target: /data/
    restart: unless-stopped
    depends_on:
      nodered-init:
        condition: service_completed_successfully

  nodered-init:
    image: "nodered/node-red:latest"
    volumes:
      - type: bind
        source: /docker/nodered/container_data/
        target: /data/
    entrypoint:
      - "/bin/sh"
      - "-c"
      - "cd /data && npm install node-red-contrib-amazon-echo"

running /usr/bin/docker-compose --verbose -p docker-nodered -f /docker/nodered/compose_files/compose.yml up --force-recreate I get this error:
...
compose.cli.verbose_proxy.proxy_callable: docker attach <- ('a004fe4a07005c31d53fa585fa74e277b08f3a15fe22b3739b82b1225e485a77', stdout=True, stderr=True, stream=True)
compose.parallel.feed_queue: Pending: {<Service: nodered>}
compose.cli.verbose_proxy.proxy_callable: docker attach -> <docker.types.daemon.CancellableStream object at 0x7f74338e4b90>
compose.cli.verbose_proxy.proxy_callable: docker disconnect_container_from_network <- ('a004fe4a07005c31d53fa585fa74e277b08f3a15fe22b3739b82b1225e485a77', 'docker-nodered_default')
compose.parallel.feed_queue: Pending: set()
compose.cli.verbose_proxy.proxy_callable: docker disconnect_container_from_network -> None
compose.cli.verbose_proxy.proxy_callable: docker connect_container_to_network <- ('a004fe4a07005c31d53fa585fa74e277b08f3a15fe22b3739b82b1225e485a77', 'docker-nodered_default', aliases=['a004fe4a0700', 'nodered-init'], ipv4_address=None, ipv6_address=None, links=[], link_local_ips=None)
compose.cli.verbose_proxy.proxy_callable: docker connect_container_to_network -> None
compose.cli.verbose_proxy.proxy_callable: docker start <- ('a004fe4a07005c31d53fa585fa74e277b08f3a15fe22b3739b82b1225e485a77')
compose.parallel.feed_queue: Pending: {<Service: nodered>}
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: {<Service: nodered>}
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: {<Service: nodered>}
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: {<Service: nodered>}
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: {<Service: nodered>}
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: {<Service: nodered>}
compose.parallel.feed_queue: Pending: set()
compose.parallel.feed_queue: Pending: {<Service: nodered>}
compose.parallel.feed_queue: Pending: set()
compose.cli.verbose_proxy.proxy_callable: docker start -> None
compose.cli.verbose_proxy.proxy_callable: docker remove_container <- ('174a68b0eea4badbf025cb8a78548e972d5b782a42cfc6ec1aed21e8fc67e49e')
compose.cli.verbose_proxy.proxy_callable: docker remove_container -> None
Recreating docker-nodered_nodered-init_1 ... done
compose.parallel.feed_queue: Pending: set()
compose.parallel.parallel_execute_iter: Finished processing: <Service: nodered-init>
compose.parallel.feed_queue: Pending: {<Service: nodered>}
compose.cli.verbose_proxy.proxy_callable: docker containers <- (all=True, filters={'label': ['com.docker.compose.project=docker-nodered', 'com.docker.compose.service=nodered-init', 'com.docker.compose.oneoff=False']})
compose.cli.verbose_proxy.proxy_callable: docker containers -> (list with 1 items)
compose.cli.verbose_proxy.proxy_callable: docker inspect_container <- ('a004fe4a07005c31d53fa585fa74e277b08f3a15fe22b3739b82b1225e485a77')
compose.cli.verbose_proxy.proxy_callable: docker inspect_container -> {'AppArmorProfile': 'docker-default',
 'Args': ['-c', 'cd /data && npm install node-red-contrib-amazon-echo'],
 'Config': {'AttachStderr': False,
            'AttachStdin': False,
            'AttachStdout': False,
            'Cmd': None,
            'Domainname': '',
            'Entrypoint': ['/bin/sh',
                           '-c',
                           'cd /data && npm install '
...
compose.parallel.feed_queue: Service(s) upstream of <Service: nodered> did not completed successfully - not processing
compose.parallel.parallel_execute_iter: Failed: <Service: nodered>
compose.parallel.feed_queue: Pending: set()

ERROR: for nodered  Container "a004fe4a0700" exited with code 2.
ERROR: compose.cli.main.exit_with_metrics: Encountered errors while bringing up the project.

Do I see it correctly that the "Args" looks fine:  'Args': ['-c', 'cd /data && npm install node-red-contrib-amazon-echo'],
But in the Entrypoint there  is the "node-red-contrib-amazon-echo" missing?: 'Entrypoint': ['/bin/sh','-c','cd /data && npm install '
or is that cut by the docker engine/output?
I understand the logic what is done by the init container/service, but I do not know why it does not function :/

You can use the following steps to debug the nodered-init container, as it appears to have exited with code 2:
docker-compose down
docker-compose up
docker-compose logs nodered-init

thanks a lot :)
as long as the urls http://IP/api/description.xml and http://IP/description.xml are accessable though Port 80 and the nodered and the amazon echo are on the same network, it should do right?
Is there something special I need to take care of when I am switching the nodered installation from one host/IP to another? Other than deleting the devices in alexa? It should discover them, right?

That's correct. The Node-RED Docker container needs to use the host network for the SSDP discovery process to work correctly. Echo devices and the Docker host must be on the same broadcast domain, and Echo devices will try to access the hub on port 80


[FRON-2027] Hotfix cleave's "rawValue" variable

As per FRON-2027, this patch fixes cleave.js for our use cases.

ok, i closed this earlier, then forgot why and re-opened it, but now i remember why I closed it. leaving a note so i don't forget again.

probably don't want to merge this into master, since (depending on how long we need to keep this fork open), it would be nice to be able to pull cleanly into master

we can just point our package installation at this branch anyway


ignore_class_list was a breaking addition

@Andarist adding the ignore_class_list to the exports means that var hoc = require('react-onclickoutside') no longer works, as that require call now yields an object
{ __esModule: true,
  IGNORE_CLASS_NAME: 'ignore-react-onclickoutside',
  default: [Function: onClickOutsideHOC]
}

so all the code in the readme that explains how to use this library is now wrong. I am backing out the ignore class commit, and if we want to reintroduce, that will be a breaking change warranting a v7

I thought we'd fixed the repo so that it would run an ES conversion for people using node "the old way", but I see node requiring in the ES6+ version when doing a normal require vs using import statements.
I'd like to know what is going on here.

TL;DR
v6 broke this and not that merge. When using bare require it indeed now needs to access default property like this require('react-onclickoutside').default. If docs use bare require in its examples they need to be:

refactored to es6 modules
refactored to .default

Full explanation
Aint sure how did u check this - plain node.js? If so, please also check previous version as generally it should yield the same result.
When importing through babel it wraps required modules like this:
function _interopRequireDefault(obj) { return obj && obj.__esModule ? obj : { default: obj }; }
var _reactOnclickoutside = require('react-onclickoutside');
var _reactOnclickoutside2 = _interopRequireDefault(_reactOnclickoutside);

So it is able to unwrap properly what got exported after transpilation.
Please take a look at what is exported now (and before IGNORE_CLASS_NAME merge).
exports.__esModule = true;
exports.default = onClickOutsideHOC;

And what is exported with IGNORE_CLASS_NAME merged in:
Object.defineProperty(exports, "__esModule", {
  value: true
});
exports.IGNORE_CLASS_NAME = undefined;
exports.default = onClickOutsideHOC;
var IGNORE_CLASS_NAME = exports.IGNORE_CLASS_NAME = 'ignore-react-onclickoutside';

So what u should notice, structure is basically the same and shouldnt matter.

Secondary note: https://github.com/Pomax/react-onclickoutside/issues/210 is not directly related, but seems to have been caused by the deps cleanup

Closing this, gonna rerelease discussed code in following days.


Question about update Az Module related to #5

I have an automation account I am going to only use Az module.  From Azure doc https://docs.microsoft.com/en-us/azure/automation/az-modules, AzureRM modules are still installed when create automation account and there is no way to remove the AzureRM modules.  The doc says "When a new Automation Account is created the existing AzureRM modules will still be installed and the tutorial runbooks will still be authored with AzureRM cmdlets."  This means both AzureRM and Az modules are installed for my automation account.  The ReadMe of this "Update-AutomationAzureModulesForAccount" says "Avoid starting this runbook on Automation accounts that contain both AzureRM and Az modules."
I am confused.  My question is, can this runbook be used to update Az Modules on the automation account?  Because every automation account will have AzureRM modules installed by default.  I haven't found an option to remove AzureRM modules (the delete button is not available).
Thanks for your help in advance.

This advice is outdated, it should be removed:

Avoid starting this runbook on Automation accounts that contain both AzureRM and Az modules

Thank you for noticing this. Older versions of this runbook were not designed to handle Az modules well, so this advice was relevant. The latest version does not have this restriction, you just need to pass a correct value to the AzureModuleClass parameter.

README is fixed.


Missing word "with" in sentence

Missing word, either "in" or "with" after "Let's walk through it...."
Let's walk through it this example.
topics - One-way binding, under first subheading "But how precisely does that work?"

Fixed in 15346145e2b87a75c63543da5472901a73ebd572


#33 adapted README; bumped docker base image

adapted README
bumped docker base image

Current coverage is 95.94% (diff: 100%)

Merging #35 into master will not change coverage

@@             master        #35   diff @@
==========================================
  Files            19         19
  Lines           222        222
  Methods           0          0
  Messages          0          0
  Branches          2          2
==========================================
  Hits            213        213
  Misses            9          9
  Partials          0          0

Powered by Codecov. Last update d8633c3...c7ca08d

:+1:

:+1:


user docs: Create Settings macro

Automated message from Dropbox CLA bot
@synicalsyntax, it looks like you've already signed the Dropbox CLA. Thanks!

This looks great, merged thanks @synicalsyntax!!
I'm really excited to have all this duplicated content cleaned up :)


Enable ANGLE for Windows 7 and below

Godot compiles with ANGLE for UWP builds (winrt), so #3634 is no more actual (there is choice to use Godot on Windows). However, it only works for Windows 8 and above.
It would be nice to backport support for ANGLE backend to non-UWP platforms, such as Windows 7 and below. ANGLE may also be used to run Godot on systems with Vulkan (#3729) drivers, but without OpenGL support (which sounds kind of strange).

there is zero gain on running Godot on Vulkan using Angle
On Thu, Oct 6, 2016 at 12:14 PM, anatoly techtonik<EMAIL_ADDRESS>
wrote:

Godot compiles with ANGLE
https://github.com/godotengine/godot/commits/master/platform/winrt/include/angle_gl.h
for UWP builds (winrt), so #3634
https://github.com/godotengine/godot/issues/3634 is no more actual
(there is choice to use Godot on Windows). However, it only works for
Windows 8 and above.
It would be nice to backport support for ANGLE backend to Windows 7 and
below as well, which may also be handy for running Godot on Vulkan (#3729
https://github.com/godotengine/godot/issues/3729) as soon as ANGLE
https://chromium.googlesource.com/angle/angle/+/master/README.md
implements this renderer.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/godotengine/godot/issues/6726, or mute the thread
https://github.com/notifications/unsubscribe-auth/AF-Z2x-BlsAohgZznVxhSYr-YxMDYXckks5qxRBjgaJpZM4KQED8
.

How about incremental porting from GLES to Vulkan? Or just reusing ANGLE optimizations for Vulkan without inventing own?

@reduz does the change to roadmap regarding vulkan affect this request? https://godotengine.org/article/abandoning-gles3-vulkan-and-gles2

Yes, we won't start using ANGLE on desktop now (apart from UWP which needs it). ANGLE is bad enough in web browsers not to be worth investigating as a workaround for bad OpenGL support.


gridApi.core.scrollTo error

Hi,
I use your core.scrollTo() function to scroll to the desired cell. But each time i call the function, i get the below error message.
This is the caller code =>
$scope.gridApi.core.scrollTo( $scope.model.gridData[valRet.rowIndx], $scope.columnDefs[valRet.colIndx] ). then(function(){ /This part has not called by the promise yet/ })
Error:
asked to listen on core.on.scrollEnd but scope wasn't passed in the input parameters, you probably forgot to provide it, not registering
(anonymous function) @ angular.js:265
module.service.s.logError @ ui-grid.js:10015
GridApi.registerEvent.feature.on.(anonymous function) @ ui-grid.js:5618
Grid.scrollToIfNecessary @ ui-grid.js:5297
Grid.scrollTo @ ui-grid.js:5329
(anonymous function) @ ui-grid.js:3245
module.service.s.createBoundedWrapper @ ui-grid.js:9473
(anonymous function) @ sfsGrid.js:69
(anonymous function) @ angular.js:265
it @ angular.js:265
(anonymous function) @ angular.js:265

gridApi.cellNav.scrollToFocus() function also produces the same error message
$scope.gridApi.cellNav.scrollToFocus( $scope.model.gridData[rowIndx], $scope.columnDefs[colIndx] );

What version are you on?  This was a defect in earlier versions, I thought it had been resolved.

My version is ui-grid - v3.0.0-rc.20-3cbe79f - 2015-04-17
I'll try with the latest version.

As you said, it had been resolved :)


white spase in the grid if no records

$('#grid').w2grid({
    name: 'grid',
    show: {
        lineNumbers: false,
        toolbar: true,
        toolbarReload: false,
        toolbarColumns: false,
        columnHeaders: true,
        selectColumn: true
    },
    multiSelect: true,
    columns: [
        {
            "field": "FechaAlbaran",
            "caption": "Mes",
            "sortable": true,
        }
    ],
    records: []
});

Column size is not defined, therefor it shows like that. I made the change if column size is not defined, it will set it to '100%'. Will push in a bit.


workflows/contributors: rm PR config

[x] read the CONTRIBUTING guidelines
[x] raised a GitHub issue or discussed it on the projects chat beforehand
[] added unit tests
[] added integration tests
[] updated documentation if needed
[] updated CHANGELOG.md

Fixup to #335

obsolete with creation of branch "update-contributors"


Login Page

Description
Make the frontend as well as the backend for the login page with email id and password as parameters and proper validation of every field in frontend as well as in the backend API
IMP - Write or send a photo of the table schema in the comments of this issue and once verified, go ahead to work on that.
Deadline
15th October, 9 PM

@irsayvid  Also, write code for check login and logout.

Admin:

admin_id  (int)
name (tiny text)
email (varchar 100)
password (tiny text)
event_name (varchar 255)
event_description (long text)
event_date (varchar 150)
event_organiser (medium text)

User:

user_id (int)
user_name (tiny text)
email (varchar 100)
rating (long text)
comments_abt_event (long text)
suggestions (long_text)
admin_fk (foreign key admin_id)

Template_preview:

id (int)
font_size (smallcint)
font_color (varchar 50)
x_coordinate (int)
y_coordinate (int)
font_type (varchar 50)
admin_fk (foreign key admin_id)


Notifications (Toast)

Laravel Mix Version<EMAIL_ADDRESS>Node Version v7.7.2:
NPM Version 4.1.2:
OS: macOS Sierra 10.12.3
LaraDock 4.19.0

On a fresh install of Laravel 5.4 and LaraDock, I'm not getting any notifications when Laravel Mix finishes. I'm not sure if this is a feature request or a bug. I'd like to see it working though.

Growl notifications do support using TCP messages, but I don't think the native toasts do.
Additionally looking at the upstream that does notifications in mix, just at a glance doesn't look to have remote notification support even if the underlying provider has it (growl is the only one I'm aware of).
https://github.com/mikaelbr/node-notifier is what's doing the notifications in mix, for the record.


Icons don't show up in Chrome

The icons are not showing up in Chrome. I am using grunt to start app locally. When I switch to font awesome, which does show up, the icons are not centered.

icons are pulled in from a cdn in the demo, so you should import them on your index.html <head>. Never tried with Font awesome so there might be some css to be tweaked in that particular case.

Got it. I will stick with your fonts. Works now.


Issue with k8s.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/

This is a...

[x] Feature Request
[ ] Bug Report

Problem:
I am a newcomer for k8s. I want to know the kubectl's configuration, so I googled it and found the docs easily:
=> https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/
here, I know some basic config of kubectl. Its good.
BUT, there is one thing I have to googled a lot and spent much time on it, its about the base64 encode data of cert file content (such as certificate-authority-data) instead of put the file path there in the configuration.
here, also the doc in your website I found the certificate-authority-data configuration. So I wandered why you don't mention it in the previous doc - configure-access-multiple-clusters?
Proposed Solution:
add the information of the configuration below to https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/

certificate-authority-data
client-certificate-data
client-key-data

@xiaotuanyu120 Thanks for filing this issue. Do you mind propose a PR to fix it?

okay, I will do a PR tonight


Security predicates tags.

Add sydr-security tag for inputs generated by Sydr security predicates.

Tested on the freeimage project by myself, it works.


Upgrade Issue - TW is 5.1.9 ?

Installing the TW5-auto-publish2gh-pages uses TW 5.1.9 and even rebuilding the project does not upgrade the TW.
The Job log in Travis shows the TW 5.1.16 is installed but the TW in GH pages tells it is 5.1.9 (Note: I cross checked this by creating new tiddler with <> content)

second this. How do you upgrade to latest version?


yarn install fails when run locally

Bug Report?

node version: v7.4.0
npm: 4.0.5
yarn version: 0.19.1

After locally cloning this repository. I ran yarn install --verbose
Following was the output I received
$ yarn install --verbose
yarn install v0.19.1
[1/4] Resolving packages...
[2/4] Fetching packages...
verbose Performing "GET" request to<EMAIL_ADDRESS>verbose Performing "GET" request to "https://https//registry.yarnpkg.com/tslint/-/tslint-4.4.0.tgz".
verbose Performing "GET" request to "https://registry.yarnpkg.com/typescript/-/typescript-2.1.4.tgz".
warning There appears to be trouble with your network connection. Retrying...
verbose Performing "GET" request to "https://https//registry.yarnpkg.com/tslint/-/tslint-4.4.0.tgz".
verbose Performing "GET" request to<EMAIL_ADDRESS>warning There appears to be trouble with your network connection. Retrying...
verbose Performing "GET" request to<EMAIL_ADDRESS>verbose Performing "GET" request to "https://https//registry.yarnpkg.com/tslint/-/tslint-4.4.0.tgz".
warning There appears to be trouble with your network connection. Retrying...
verbose Performing "GET" request to<EMAIL_ADDRESS>verbose Performing "GET" request to "https://https//registry.yarnpkg.com/tslint/-/tslint-4.4.0.tgz".
warning There appears to be trouble with your network connection. Retrying...
verbose Performing "GET" request to "https://https//registry.yarnpkg.com/tslint/-/tslint-4.4.0.tgz".
verbose Performing "GET" request to<EMAIL_ADDRESS>warning There appears to be trouble with your network connection. Retrying...
verbose Performing "GET" request to "https://https//registry.yarnpkg.com/tslint/-/tslint-4.4.0.tgz".
verbose Performing "GET" request to<EMAIL_ADDRESS>verbose Error: read ECONNRESET
    at exports._errnoException (util.js:1022:11)
    at TLSWrap.onread (net.js:572:26)
error An unexpected error occurred<EMAIL_ADDRESS>read ECONNRESET".
info If you think this is a bug, please open a bug report with the information provided in "/abcd/abcd/abcd/tslint/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

This is probably because of yarn.lock.

Another reason to remove update-notifier in favor of simple check? (#2151)

It was easy to bypass this issue by editing yarn.lock file.  Surprising that we don't use yarn install in ci builds.

Surprising that we don't use yarn install in ci builds.

agreed, I think we just missed that step when switching to Yarn. @nchen63 can you set that up today?


TypeError when changing dropdown before data is given

On first load, we pass in an empty array. Once we load the data (with the click of a button), it then gets a populated array. This works fine. However, if you change the items-per-page dropdown, and then load the data in, we get a type error. I briefly stepped through the code and saw that the error is being thrown here, where data is undefined. on line 55, this.props.data is an array of undefined items
Many thanks.

sorry for lately reply, bust on this month, you got the error if you change size per page firstly and then load data?

Yes, that's right. I will try to get a minimal example that reproduces the issue for you.

thanks, I'll also try to reproduce it, but need some time, there're a lots of issue was queued

jsfiddle here (fullscreen). Working on some source code for you to clone

I forked your repo and reproduced the bug in the basic pagination example. Hope this helps

ok, I can reproduce it and it absolutely is a bug, thanks

Fixed on v3.1.3, check it out 👍

Awesome, that was quick! Thanks so much, will try it out tomorrow


NO GPS in QGC

why is this?

analyze have data .but showwing NO GPS

Hi,
It seems that for some reason the position estimator did not initialize.
Can you please share the log file?

I solve that. Because the fix_type is not receive.


[Question] Is using PreviousTailAffinity in a single node cluster valid syntax?

Hey there. I tried to apply to following CR with podDistribution type set to PreviousTailAffinity and the reconciliation failed. I'm wondering if this is a semantic issue or a bug in operator. In case you want to see more details, I also attach the log of operator below.
Thanks.
apiVersion: clickhouse.altinity.com/v1
kind: ClickHouseInstallation
metadata:
  name: test-cluster
spec:
  configuration:
    clusters:
    - layout:
        replicasCount: 2
        shardsCount: 2
      name: replicated
    zookeeper:
      nodes:
      - host: zookeeper.zoo3.ns
  defaults:
    templates:
      dataVolumeClaimTemplate: default
      podTemplate: clickhouse:19.6
  templates:
    podTemplates:
    - name: clickhouse:19.6
      podDistribution:
      - type: PreviousTailAffinity
      spec:
        containers:
        - image: clickhouse/clickhouse-server:22.3
          name: clickhouse-pod
    volumeClaimTemplates:
    - name: default
      spec:
        accessModes:
        - ReadWriteOnce
        resources:
          requests:
            storage: 500Mi

affinity.log

Could you share
kubectl get pod -n acto-clickhouse | grep chi-test-cluster-replicated-0-0-0
kubectl logs -n acto-clickhouse chi-test-cluster-replicated-0-0-0 --since=48h


change domain in build workflow

Is the domain actually specified there? Or is it just the /toborrights path that needs to be fixed

yeah you're right, whoops. i was just thinking about the domain name so i wrote that.

fixed by 8bbdfacb2fe8156315fb6ac24898d19279bd915e


Black hole for 2x rate limit

The TChannel protocol specifies that clients should retry if they receive a busy frame. The rate limiter produces busy frames. There are two kinds of busy: ephemeral business, where a node is temporarily busy but other peers are available; and systemic business, where all peers are backlogged. The rate limiter indicates the latter but induces the behavior for the former.
We could alternately drop requests if a service receives 2x the rate limit. In practice, the normal rate limiter induces 5x the normal volume, by causing some number of retires and different retry policies. A 2x black hole rate limiter would mitigate retry storms caused by the 1x rate limit. This effectively would encourage folks to use a "retry once policy" to keep under the 2x rate limit, and thus getting notified immediately if they hit the rate limiter.

I think we already do this:
https://github.com/uber/hyperbahn/blob/master/rate_limiter.js#L33
https://github.com/uber/hyperbahn/blob/master/service-proxy.js#L549
Maybe the feature isn't implemented properly.

We do kill switch; that works.
The issue is probably the current "total rate limit". 4k * 2 === 8k;
There probably are all kinds of bad things that happen between 4k QPS & 8k QPS before the black hole kicks in... The black hole may never kick in if it cannot even get to 8k QPS.
You should probably look at a rate limiter not based on QPS but based on say "event loop lag" or some other symptom of being 100% CPU.
Aka rate limit at X event loop & black hole at 2X event loop will most likely kick in properly as 2X event loop is "garantueed" to happen but 8k QPS may never happen.

The total kill switch isn't a multiplier; it's just totalRpsLimit + 200. So currently 4296.
I propose lowering the service kill switch factor to 1.5 but this is something we could determine experimentally with the staging ring.

We should just make the kill switch factor a configurable, then we can
#seewhatworks, and have the ability to drop the boom if needed
On Mon, Jul 25, 2016 at 3:47 PM Russ Frank<EMAIL_ADDRESS>wrote:

The total kill switch isn't a multiplier; it's just totalRpsLimit + 200.
So currently 4296.
I propose lowering the service kill switch factor to 1.5 but this is
something we could determine experimentally with the staging ring.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/uber/hyperbahn/issues/291#issuecomment-235109713, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AADCM4HCub4puY09EtQJh8EBh0imhxQdks5qZTz9gaJpZM4JUZbv
.

Fixed in #295