feat(icons): added line-squiggle icon

What is the purpose of this pull request?

[x] New Icon

Description
Added new wavy-line icon.
Icon use case

gestures for touchscreen devices
denoting snakes or serpent
doodles
denoting curves

Alternative icon designs

Icon Design Checklist
Concept

[x] I have provided valid use cases for each icon.
[x] I have not added any a brand or logo icon.
[x] I have not used any hate symbols.
[x] I have not included any religious or political imagery.

Author, credits & license

[x] The icons are solely my own creation.
[x] The icons were originally created in # by @chessurisme
[x] I've based them on the following Lucide icons: wavy-line
[x] I've based them on the following design: Gestures in Streamline

Naming

[x] I've read and followed the naming conventions
[x] I've named icons by what they are rather than their use case.
[x] I've provided meta JSON files in icons/[iconName].json.

Design

[x] I've read and followed the icon design guidelines
[x] I've made sure that the icons look sharp on low DPI displays.
[x] I've made sure that the icons look consistent with the icon set in size, optical volume and density.
[x] I've made sure that the icons are visually centered.
[x] I've correctly optimized all icons to three points of precision.

Before Submitting

[x] I've read the Contribution Guidelines.
[x] I've checked if there was an existing PR that solves the same issue.

Hmmm, I propose my icon as an alternative design. 😁

Feels more swirly than curvy.

@jguddas agreed.

I try to rename it to line-squiggle because I think this one suit to itself.

See the update icon:

I'll try to modify it again.

How was it?

What about making the loop more circular?
Open lucide studio

Open lucide studio

Good idea.

Ready to go?


Memory Metrics are doubled Grafana

I have installed this grafana plugin, and installed prometheus and the associated scrape configs, but now my metrics are doubled, see these screenshots.
How can i troubleshoot this?

I have noticed the same thing. It is because there are more than one time series for one pod name and the result is summed up. There is one for every container and one for the pod (total).
Kubernetes cluster monitoring (via Prometheus) This Dashboard for example adds the following instant vector selectors to the query image!="",name=~"^k8s_.*". This will filter out the pod total time series.
If I add that to the Dashboard from this plugin, the data is still incorrect, but I don't have a clue why. Although it is getting closer.


Backport #5320

Original #5320: remove usage of obsolete _dataAsRows flag
https://github.com/Itseez/opencv_contrib/issues/429

:+1:


refactor(nav): reorder menu options

Codecov Report

Merging #349 (6944aec) into master (8b81d5e) will decrease coverage by 0.10%.
The diff coverage is n/a.

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

@@            Coverage Diff             @@
##           master     #349      +/-   ##
==========================================
- Coverage   55.83%   55.72%   -0.11%
==========================================
  Files          39       39
  Lines         969      969
  Branches       88       88
==========================================
- Hits          541      540       -1
- Misses        395      396       +1
  Partials       33       33

Impacted Files
Coverage Δ

src/app/shared/add-device/add-device.component.ts
86.36% <0.00%> (-2.28%)
:arrow_down:

Continue to review full report at Codecov.

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


Roku Card Editor

Can't seem to locate this file to add to my www.
because of this when I add the custom card to my UI i get this :
TypeError: Failed to fetch dynamically imported module: https://secret.duckdns.org:8123/local/roku-card-editor.js

Readme should be updated, there is no longer an editor included

When was this updated? I'm new to HA and Github

https://github.com/custom-cards/roku-card/releases/tag/1.0.0
I've updated the readme file to not reference the editor anymore. Just don't include the resource line about importing the editor and you'll be fine.

Make sure you're downloading from the dist folder

That did it, thanks!


Is this support UWP?

If not, When it will come?

Yes, UWP is very important for quick-cycle code/run/test on Windows.


Blank screen when switching to a new tab

I loaded a spreadsheet with many tabs. After working on one tab, I tried to switch to a new tab and the screen when blank. I quit t2wml and started fresh. When I visit the same project I get the same blank screen. Project, logs attached. I am running 2.95-pre.1
Hovy.zip
2021-05-31_13-35-17_t2wml.log.zip
To recover from this problem II need to delete t2wmlproj.user.json

pretty sure this has been fixed in 10.0-rc, please confirm

@szeke can this be closed?


Bills pages

Designs: https://www.figma.com/file/MWzmEAYQC1NYZiD4BG0FlI/V2-Fast-Follows?type=design&node-id=29-1394&mode=design

This work should also include adding a link to the bill page when we see a DTSI stance referencing a bill

We'll also want to replace the bills list on this page with the API

@travisbloom-cb to ship API that supports this page before @eduardopicolo-cb starts work


PerfectScrollbar not working with sidebar mini on Windows/Chrome + Firefox

Customer details:
"I'm checking http://demos.creative-tim.com/paper-dashboard-pro/examples/dashboard/overview.html on Windows (Chome & Firefox)
During minifying the sidebar, the UI scroll is defaulting to browser one instead of the one that comes with the theme. Could you please check this and fix?
Thanks"

Solved in the version 2.0.1


Definition missing for Integer#to_d

Input
https://devdocs.io/ruby~2.5/integer#method-i-to_d
→ View on sorbet.run
# typed: strong

require 'bigdecimal'
require 'bigdecimal/util'

42.to_d   # => 0.42e2

Observed output
editor.rb:6: Method to_d does not exist on Integer component of Integer(42) https://srb.help/7003
     6 |42.to_d   # => 0.42e2
        ^^^^^^^

Expected behavior
It should typecheck

Integer#to_d is provided by a monkey-patch from bigdecimal/utils. It's not entirely clear how we should treat monkey-patches in sorbet: currently all rbis for the stdlib are loaded at startup, so making this change would put the monkey-patch in scope even if bigdecimal/utils was not required.

https://sorbet.org/docs/faq#it-looks-like-sorbet-s-types-for-the-stdlib-are-wrong
It's the same for to_set on Array. I think as long as the monkey patch is defined by requiring something in the standard library, it's fine to have it.

this was resolved in https://github.com/sorbet/sorbet/pull/3027


Threads parameter is not working on Apple Silicon

Obs.: I'm opening a ticket for an issue I noticed while the support for M1 was not yet official. I noticed that this still seem to be happening. Back then, I wrote the following report:
    I know support is not official yet, but sharing my experience in the hope it will eventually be useful for when there is an official release.

One thing I noticed is that the build for ARM doesn't seem to respect the mvnd.threads setting or the -T flag. Using -T 0.5C here, still causes it to use all cores.

Originally posted by @orpiske in https://github.com/apache/maven-mvnd/issues/337#issuecomment-1087450339

Can you reproduce the issue ?
Are you sure you don't have the mvnd.threads property set in one of the configuration file ?
It seems to work correctly for me...

@gnodet my [USER_HOME]/.m2/mvnd.properties has mvnd.threads=0.5C. My understanding is that it would use half of the available cores by default. Is there something else I should look at that could be affecting this?

I've set my [USER_HOME]/.m2/mvnd.properties to add mvnd.threads=0.5C and it works fine for me.
Can you check your environment maybe using set | grep MAVEN ?
mvnd also checks the [PROJECT_HOME]/.mvn/mvnd.properties and [MVND_HOME]/conf/mvnd.properties...

@gnodet thanks. This is what I have:
MAVEN_OPTS=-Xms2048m -Xmx3584m
MAVEN_HOME=/Users/opiske/.sdkman/candidates/maven/current

My mvnd.properties from MVND_HOME seems to use the default values:
cat $MVND_HOME/conf/mvnd.properties | grep -i thread
# MVND_MIN_THREADS
# The minimum number of threads to use when constructing the default {@code -T} parameter for the daemon.
# This value is ignored if @{@code -T}, @{@code --threads} or {@code -Dmvnd.threads} is specified on the command
# line, or if {@code mvnd.threads} is specified in {@code ~/.m2/mvnd.properties}.
# mvnd.minThreads = 1
# MVND_THREADS
# The number of threads to pass to the daemon; same syntax as Maven's {@code -T}/{@code --threads} option. Ignored
# if the user passes @{@code -T}, @{@code --threads} or {@code -Dmvnd.threads} on the command
# mvnd.threads =
# MVND_THREAD_STACK_SIZE
# JVM options for the daemon to specify the thread stack size
# mvnd.threadStackSize = 1M

And looking at one of my projects, this is what I have:
ls ~/code/java/camel/.mvn
extensions.xml  jvm.config      wrapper/

I think I know where the problem may be: the log message correctly displays the scaled down number of threads as I adjust the setting, however the CPU load pattern on both htop and on Activity Monitor seems to imply that the load is happening on all Cores.
I am not sure if the problem is indeed w/ Maven Daemon. Maybe it's something specific about how the scheduler distributes the load on this OS/platform.
So, I think we can close this @gnodet.


container: Add cgroup mount for introspection

Signed-off-by: Mrunal Patel<EMAIL_ADDRESS>

This will help us test that cgroups setting such as pids limit is properly set up.

I think I'll fold this with the pids limit PR.


Did you train the tf Deit models from scratch?

Hi Sayak,
Thanks a lot for sharing this tensorflow version of Deit models.
I was wondering if you trained these tf Deit models from scratch to obtain the same level of accs as the original Pytorch Deit models?
Have you tried to convert the original Pytorch model weights into tf format, and load them into your tf Deit model? Were you able to get the same level of acc as the pytorch model in this way?
If you need to train these tf Deit models from scratch or fine tuning from the original pytorch weights, can you share your training or finetuning recipe as well?
Thanks a lot for your help again.

I converted the models. This is written in the README.

Ok nice that you can get the same level of acc by converting the pytorch weights. I actually met some troubles achieving that, I will check details of your convert.py.
Also Deit pytorch has a lot data augmentations, any plan to integrate those as well in here?
Cheers

I don't.


Exporting ehCache metrics to Elasticsearch causes NaN error

I set up ehCache metrics collection with the Dropwizard metrics in my Spring Boot app. I set up a vanilla elasticsearch server and set up a Scheduled job to use ElasticsearchReporter. Looks like the timestamp data from the ehcache metrics is causing elasticsearch to stumble:
[2015-02-24 18:07:28,426][DEBUG][action.bulk              ] [Bora] [metrics-2015-02][4] failed to execute bulk item (index) index {[metrics-2015-02][gauge][szcN3Lg4QcCm7aZP3UyOhA], source[{"name":"net.sf.ehcache.Cache.com.xxx.xxx.xxx.CustomerPromotion.mean-search-time","@timestamp":"2015-02-24T18:07:26.000+0000","value":"NaN"}]}
org.elasticsearch.index.mapper.MapperParsingException: failed to parse [value]
at org.elasticsearch.index.mapper.core.AbstractFieldMapper.parse(AbstractFieldMapper.java:418)
at org.elasticsearch.index.mapper.object.ObjectMapper.serializeValue(ObjectMapper.java:616)
at org.elasticsearch.index.mapper.object.ObjectMapper.parse(ObjectMapper.java:469)
at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:515)
at org.elasticsearch.index.mapper.DocumentMapper.parse(DocumentMapper.java:462)
at org.elasticsearch.index.shard.service.InternalIndexShard.prepareCreate(InternalIndexShard.java:363)
at org.elasticsearch.action.bulk.TransportShardBulkAction.shardIndexOperation(TransportShardBulkAction.java:406)
at org.elasticsearch.action.bulk.TransportShardBulkAction.shardOperationOnPrimary(TransportShardBulkAction.java:157)
at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction.performOnPrimary(TransportShardReplicationOperationAction.java:556)
at org.elasticsearch.action.support.replication.TransportShardReplicationOperationAction$AsyncShardOperationAction$1.run(TransportShardReplicationOperationAction.java:426)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.NumberFormatException: For input string: "NaN"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Long.parseLong(Long.java:441)
at java.lang.Long.parseLong(Long.java:483)
at org.elasticsearch.common.xcontent.support.AbstractXContentParser.longValue(AbstractXContentParser.java:145)
at org.elasticsearch.index.mapper.core.LongFieldMapper.innerParseCreateField(LongFieldMapper.java:297)
at org.elasticsearch.index.mapper.core.NumberFieldMapper.parseCreateField(NumberFieldMapper.java:215)
at org.elasticsearch.index.mapper.core.AbstractFieldMapper.parse(AbstractFieldMapper.java:408)

@kmandeville  Are you sure your problem is related to the Dropwizard project?
From the log you provided, I don't see anything that links it with the io.dropwizard package, under which the project is distributed.
If you believe that the problem is with Dropwizard Metrics - it's a separate project under Dropwizard organization. You can open an issue there.

Additionally the Elasticsearch metrics reporter is maintained by Elasticsearch: https://github.com/elasticsearch/elasticsearch-metrics-reporter-java


Make a big mental shift

This is it, the mental shift we need to make to get out of our own heads and into our customer's.
"Pay for open source" is about our problems and motivations.
"Invest in open source" is about their problems and motivations.

@JessaWitzel Merge? 😄

Okay stopping. slack 🐭


Introduce the Dumpable (empty) module.

This module serves as an interface to indicate that instances of types that include it
will respond to the .dump method, as a way to convert their internal substructure to primitive Ruby objects.
This makes other tools able to further invoke the dump method of the object (or not), when rendering nested structures.

fixes #157
Signed-off-by: Josep M. Blanquer<EMAIL_ADDRESS>

You might want to include the dumpable.rb file too. Just a thought. :smile:

woops...haha. yup, added it.

LGTM


persistent enumeration failures

Describe the issue
Following these instructions plus the workaround in #2610, I'm attempting to boot macOS x86 on a macOS M1 host. Without the workaround, the machine crashes with the reported failure. After applying the workaround, it no longer crashes, but repeatedly emits a few messages while consuming the bulk of the host CPU.
AppleUSB20HubPort004810000: AppleUSBHostPort::createDevice: failed to create device (0xe00002ba:)
AppleUSB20HubPort004810000: AppleUSB20HubPort::resetAndCreateDevice: failed to create device, disabling port
AppleUSB20HubPort004810000: AppleUSBHostPort::disconnect: persistent enumeration failures.

Those messages are re-typed from what I could read from the machine thumbnail after terminating it. There might be typos or characters I couldn't read accurately due to resolution.
Even if terminating the VM very quickly (by human standards), UTM becomes mostly unresponsive and killing it difficult (sometimes requires force-quitting the app or some bash processes).
I tried switching to USB 2.0, but that prevented booting altogether.
Configuration

UTM Version: 4.1.4
macOS Version: 13.1
Mac Chip (Intel, M1, ...): M1

Debug log
I was able to capture a debug.log, even though it's supposed to be unavailable for macOS-on-macOS VMs (perhaps because this is a custom x86 vm). The file is small, so probably doesn't provide a lot of insight.
Upload VM
Here is the VM.
Any advice is appreciated.

Did you ever figure out a solution to this issue? stuck on the same thing.

Nope.


Add Swift 2.0 / Xcode 7.0 support

This pull request will remain open to track Xcode 7 and Swift 2.0 support. If you're doing work with Swift 2.0, feel free to pull the xcode-7.0 branch.
The changes were all primarily done by Xcode 7 automatically.

One note regarding an outstanding issue I'm running into - I've updated my Cartfile.private to point to the Swift 2.0 versions of Quick and Nimble, but when I run carthage update, the build fails. If I go into the Carthage/Checkouts directory and run xcodebuild there, it works just fine, though.
I'll keep trying to track that issue down.

With the next seed Chris Lattner hinted support for recursive enums. This could probably be relevant for type safe XML parsing. Not sure yet, just thought I needed to deposit this info ;)

Whoa, I hadn't heard that yet - other than checking out the keynote and headlines, I haven't really had a chance to dig in on much of the news this week. That sounds very interesting. I'm not even sure what that would look like.

I'm no longer seeing the issue with Carthage - I updated to the latest Quick/Nimble releases as well as fixed an issue with no simulator being found for the playground.

@drmohundro
Error at places where 'joinWithSeparator' API is used. I am using xcode 7 beta 4

@imran20487 this branch is up to date with the latest Xcode 7.0 beta which is beta 6 - between beta 5 and beta 6, the joinWithSeparator method was added (and the prior " ".join was removed). Hope this helps.

Looks like Xcode 7.0 is out now... I'll hopefully get this branch merged soon.

As far as semver goes, this is a breaking change so this release will be labeled 2.0.0, primarily because this release requires Xcode 7.0 and Swift 2.0. There are some minor breaking changes in the API, too, though they're only related to error handling.
Error Handling Changes/Additions in 2.0
@leoMehlig added support for Swift 2.0's new error handling (exception handling in other languages) in #35. As part of that, the previous .Error case is now named .XMLError and the new XMLIndexer.Error is the ErrorType that is thrown when there is a problem parsing.
There is also new byIndex and byKey methods if you want to explicitly catch parsing errors. There isn't throws support on subscript methods which is why they've been added; however, you can still get the ErrorType response by handling the .XMLError case.
Other Contributions to 2.0
@fluffyemily and @jpsim helped make changes to support Swift 2.0's new joinWithSeparator method (#42).
In addition, thanks to everyone for reporting issues and offering feedback!


Removes hb-articles directory from appearing in breadcrumb

Filters hb-articles out of breadcrumbs

:shipit:


Exception when processing ECL request

Describe the bug
When searching a concept by ECL expression that includes a wildcard *, the server throws exceptions and response with 500. After looking a bit into this it seems like the root cause of the issue is the ElasticSearch cluster size - there are network limits, different for the different cluster sizes https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/aes-limits.html. Ours in dev has limit 10MB, but even in prod where the limit is 100MB some of the queries fail.
Even though the root cause is the max size of HTTP request payload allowed as per the ES limitations it seems unreasonable to have to send a request of over 100MB, so maybe this bit can be either optimised or maybe use scrolling to mitigate that on a request level in SnowOwl.
To Reproduce
Here are couple of random examples of ECL to use:

" << * :  *  =  *"    - this doesn't worn in both cluster sizes
"<< * :  246090004  =  *"   - this works in the larger size

Expected behavior
I would have expected limit in the request to snowowl to play a role in the request to ES as well or maybe have different param or config to control the ES requests. However, the expected behaviour is just a proper returned response. Currently the response is 500 with message Something went wrong during the processing of your request.
Version

Snow Owl Version:  v7.9.1
Elasticsearch Version (external): 7.7.0

Additional context
Parts of the stacktrace include

 ERROR index.snomedstore - Couldn't execute query

followed by

.    Suppressed: org.elasticsearch.common.ParsingException: Failed to parse object: expecting field with name [error] but found [Message]

where the response seems to be :

{"Message":"Request size exceeded 10485760 bytes"}

Hi @ivelina-yordanova,
Thank you for reporting the issue.
Yes, this is something that has been reported from other sources, where AWS is being used.
We will take the time to limit the size of the requests Snow Owl sends to an ES cluster, but at the current state this is not supported.
As a possible workaround, in some cases limiting the ECL query or splitting up the ECL query manually on the input side could work, but I see this is not an ideal solution to the problem.
Once we have the fixes, I'll get back to you.
Regards,
Mark

Hi @cmark,
Thank you for replying so quickly. I am suspecting the size limit is also the main issue we cannot save the results of the classification job (see this issue), which is quite important for us at the moment, so I was wondering if you have an approximate timeline or estimation when/ in what release do you expect to have a fix for this, otherwise we'll have to look for workarounds for that as well.
Thanks,
Ivelilna

Hi @ivelina-yordanova,
Not 100% sure that the two issues are actually connected or one is the reason of the other, but if yes, then handling large filters and request body sizes in our Elasticsearch client layer will definitely solve the issue. I'd like to fix these issues as soon as possible and it will happen eventually, but I cannot guarantee any specific release version or any release date.
I hope you understand.
Contributions are always welcome, feel free to play with the low-level parts of our ES client layer and submit your changes.
Regards,
Mark

Hi @cmark,
Completely understand.
Just wanted to share another observation in case that's useful - we did an experiment with a larger cluster, where the payload limit is 10x more and this worked for the classification issue and given the logs from the issue I assume they are for sure related.
Regards,
Ivelina

Thank you!
Mark

Hi @ivelina-yordanova,
Do you have any updates on this? Did you encounter the occasional failures of ECL evaluation either in your dev or prod environments?
We have made several improvements to proper Elasticsearch request sizing in recent releases, but some of the areas might need extra care.
Any update on this is greatly appreciated.
Thank you,
Mark

Hi @ivelina-yordanova,
Multiple improvements have been introduced in the ECL processing and evaluation of the latest 8.0.0 release that hopefully help with the failures you have experienced in this ticket. Feel free to check them out.
As always, if you have any further questions or experience any other issues, raise them here.
Cheers,
Mark


Fix double instantiation of Uri in IsHttps()

Uri instance is created two times from the address.

@kosta-arnorsky please rebase the change against dev branch. This is what @brentschmaltz asked for in https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/issues/1659#issuecomment-889456490

Created https://github.com/AzureAD/azure-activedirectory-identitymodel-extensions-for-dotnet/pull/1676


Data quality in Resource Registry

Description of the bug
Currently there's some issues with the data quality in RRR.

API-delegation:

Steps To Reproduce
Go to API-delegation on: https://am.ui.tt02.altinn.no/accessmanagement/ui/offered-api-delegations/choose-api
or go to: Single rights to see what's on the pictures
Additional Information
No response

Renamed since RRR is Resource Rights Registry

#1  Empty name on resource should not be possible. Updated so it at least require 1 character
For emtpy service owner name we will update list method to get the offical name if not set
#2 We will allow override of name. So we just have to live with it
#3 We just need to keep training the service owners to set good name. Not possible to create validation that make sure the name makes sense


[BULK] - DocuTune remediation - Sensitive terms with GUIDs (part 41)

Applying sensitive terms with GUID changes as part of Content SFI and outlined in Overview - Writing content securely - Platform Manual. Changes are part of the Microsoft-wide SFI effort. Point of contact: @CelesteDG
DocuTune v<IP_ADDRESS>
CorrelationId: ac15aa43-4e2b-437f-ab1c-fdd7e79cd4db
#docutune

#docutune-review

LGTM


raise TypeError('iteration over a 0-d tensor') TypeError: iteration over a 0-d tensor

I am using  Console to run .py file. It has pre-installed tf2.3_py3.6 kernel installed in it. It has 2 GPUS in it.

PyTorch Lightning Version (e.g., 1.3.0): '1.4.6'
PyTorch Version (e.g., 1.8): '1.6.0+cu101'
Python version: 3.6
OS (e.g., Linux): system='Linux'
CUDA/cuDNN version: 11.2
GPU models and configuration: Mentioned below
How you installed PyTorch (conda, pip, source): pip

Additional context
NVIDIA-SMI 460.91.03    Driver Version: 460.91.03    CUDA Version: 11.2     |
|-------------------------------+----------------------+----------------------+
| 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 V100-SXM2...  Off  | 00000000:62:00.0 Off |                    0 |
| N/A   36C    P0    57W / 300W |   2842MiB / 32510MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  Tesla V100-SXM2...  Off  | 00000000:89:00.0 Off |                    0 |
| N/A   32C    P0    43W / 300W |      3MiB / 32510MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
+-----------------------------------------------------------------------------+

Code:
model = SRTagger(
  n_classes=100,
  n_warmup_steps=warmup_steps,
  n_training_steps=total_training_steps
)

criterion = nn.BCELoss()

checkpoint_callback = ModelCheckpoint(
  dirpath="checkpoints_sample_2",
  filename="best-checkpoint",
  save_top_k=1,
  verbose=True,
  monitor="val_loss",
  mode="min"
)

logger = TensorBoardLogger("lightning_logs_2", name="SmartReply2")

early_stopping_callback = EarlyStopping(monitor='val_loss', patience=2)

trainer = pl.Trainer(
  logger=logger,
  callbacks=[early_stopping_callback,checkpoint_callback],
  max_epochs=N_EPOCHS,
  gpus=[0,1],
  progress_bar_refresh_rate=50,
  amp_level='O3',
  accelerator="dp"
  )

print("here")

trainer.fit(model, data_module)

Error:
File "/home/pc/.local/lib/python3.6/site-packages/pytorch_lightning/loops/epoch/training_epoch_loop.py", line 224, in on_run_end
    training_epoch_end_output = model.training_epoch_end(processed_outputs)
  File "20210923_passDis_model_pc1.py", line 255, in training_epoch_end
    for out_labels in output["labels"].detach().cpu():
  File "/home/pc/.local/lib/python3.6/site-packages/torch/_tensor.py", line 607, in __iter__
    raise TypeError('iteration over a 0-d tensor')
TypeError: iteration over a 0-d tensor

Is it related to criterion = nn.BCELoss(). I am solving multi-label classification problem. How can I avoid this error ?

Hi
The error happens in your training_epoch_end, the error message is telling you where the error occurs:
for out_labels in output["labels"].detach().cpu():
here you are iterating over a 0-dim tensor, so output["labels"] must be a 0-dim tensor. Please double check your code that this is the intended behavior.

Hi
The error happens in your training_epoch_end, the error message is telling you where the error occurs:
for out_labels in output["labels"].detach().cpu():
here you are iterating over a 0-dim tensor, so output["labels"] must be a 0-dim tensor. Please double check your code that this is the intended behavior.

I guess this has to do with accelartor=dp and nn.BCE() loss.  Because same code run without accelartor.
Here is the link.  https://stackoverflow.com/questions/62109287/why-does-nn-crossentropyloss-throw-typeerror-iteration-over-a-0-d-tensor-when
My question to you is how can we overcome this error?


Unify prompt config for user and system

a couple of things is done in this PR:

user can setup user and system prompt with the --prompt or environment variable. For more detail, you can check the readme file or comments in the cli.py
set a convention for all bilingual_book_maker (BMM) environment variables, so they all start with BBM_ prefix as a namespace. I didn't remove the previous supported environment variables, for backward compatibility purpose. I think they should be considered deprecated, we can remove them soon if the project maintainer Mr. @yihong0618 agrees :)
minor fix for the readme number list
minor fix for the kwargs invocation
added test for json case

LGTM after a quick look
will test tonight（+8 timezone) thank you very much

agree about 2


Features not documented

Anti-malware policies have two features that are undocumented by this page:

Common Attachment Types Filter
Malware Zero-hour Auto Purge
It's possible to find these features mentioned elsewhere in Docs, but they should be documented here in the "Use the EAC to create anti-malware policies" section, since this is a walkthrough of creating an anti-malware policy, and these features appear on-screen when creating an anti-malware policy.

To see what I'm talking about, set up a Microsoft 365 test tenant (using https://demos.microsoft.com) and try to follow the steps in "Use the EAC to create anti-malware policies." There are two sections in the dialog that are not documented on this page.
The Common Attachment Types Filter subsection should be after the Malware Detection Response section. The Malware Zero-hour Auto Purge section should be after the Common Attachment Types Filter section.
The Notifications section (already documented on this page) should be after the Malware Zero-Hour Auto Purge section.

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

ID: db041b73-f7c9-db6c-070b-a7c974de640c
Version Independent ID: dffb7045-3ba8-a014-d1be-462ca1d609b5
Content: Configure anti-malware policies
Content Source: microsoft-365/security/office-365-security/configure-anti-malware-policies.md
Service: o365-seccomp
GitHub Login: @MSFTTracyP
Microsoft Alias: tracyp

@robmacf  - Thank you for submitting feedback.
I will get this issue over to the Microsoft 365 writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@robmacf Thank you so much for the feedback. I have modified the doc accordingly via PR# https://github.com/MicrosoftDocs/microsoft-365-docs/pull/831
Thanks
Sri

@robmacf - From our understanding, the issue has been resolved based on this merged commit https://github.com/MicrosoftDocs/microsoft-365-docs/commit/9407a98db94bf61a9cf79e6d4d183df55d08cfcc.
Thank you for your contribution to make the docs better! Much appreciated!


Feature - Transaction contribution details

Feature
View the percentage contribution of a transaction with respect to the total budget (income or expense).
Proposed Changes

Create a transaction detail view page.
Create a link to the transaction detail page from the budget list page.
Have a back navigation button to return to previous router.
Transaction detail page should display the description / title, percentage contribution with a + [plus] sign for inflow and - [minus] sign for outflow and a pie/donut chart showing the percentage contribution in overall budget.

Screenshot

Checklist

[x] Feature developed
[x] Created/updated unit tests
[x] Comments in some parts of code
[x] Tested for desktop and mobile compatibility

Coverage decreased (-0.005%) to 77.925% when pulling cf14a9e0d841ca56db854651d390bba2154a3b56 on jeffreyroshan:master into ddf7c8e1ee591036dbf2f6285e5ae412423f4f6e on ModusCreateOrg:master.


URL sometimes not saved to yaml

Hey @katydecorah, thanks for an awesome project.
For some reason I have found that this website: https://thefullstackdev.net/article/create-beautiful-website-while-sucking-at-design/ doesn't appear to download correctly.
It generated the following yaml
- title: You can create a great looking website while sucking at design
  site: ''
  date: '2022-08-03'
  description: How to create great looking websites while having little design skill.
  image: ''
  type: ''
  notes: "blah blah blah"

As you can see it didn't grab the URL correctly for some reason.
Thought I would just report this to you :)
Thanks for a great project!

Thank you for this use case! Fix happening in #63 🌻


Syntax highlighting

There are numerous syntax highlighters on the web. I had to migrate a large documentation from Confluence to GitHub wiki. One of requirements was to preserve language specific highlighting. I hacked the code to get what I needed before bumping into similar implementation done by Benjamin-Dobell/reverse_markdown@73a1da89940c92b757605de06cc44ad35596c939. Then I figured out that more generic solution is needed: Solution that would make adding support for converting various syntax highlighting implementations easier.
The only difference to upstream implementation is that I add a new line before code block based on recommendation in GitHub Flavoured Markdown article.
I couldn't find out upon which syntax highlighter Benjamin based his implementation. Therefore I named highlighter after his last name. I will be happy to refactor once Benjamin provides name of syntax highlighter upon which he based his implementation.
Base highlighter class has unimplemented method validate. The idea is to validate languages based on GitHub supported languages
Defining which syntax highlighter is used in HTML to be converted aligns with upstream logic:
ReverseMarkdown.config do |config|
  config.unknown_tags     = :bypass
  config.github_flavored  = true
  config.syntax_highlight = 'confluence'
end

or
ReverseMarkdown.convert(input, unknown_tags: :bypass, github_flavored: true, syntax_highlight: 'confluence')

Hello @schkovich, thanks for your PR. I'll take a look at it and get back to you.

@schkovich could you provide some examples for the confluence highlighting mechanism? Where is it used at? Is https://confluence.atlassian.com/display/DOC/Code+Block+Macro the right one?

Given macro is about Confluence internal rendering mechanism.
I find that export tools are more relevant in migration use case. Exporting Confluence Pages and Spaces to HTML
I have no access to the latest Confluence. Bellow is a code block example generated using confluence 3.5.
<pre class="theme: Confluence; brush: php; gutter: false">
    class ArticlesModel extends Model
    {
        public function getBlog($id)
        {
            $sql = "SELECT id, title, body
             FROM blogs
            WHERE id = " . (int)$id;

            $blog = Db::instance()->getFirst($sql);

            $blog['body'] = BBParser::parse($blog['body']);

            return $blog;
        }
    }
</pre>

Hello @schkovich, thanks for your answer. Please take a look at #44 and let me know how you feel about that approach.

I just release version 0.7.0 that includes this feature. Thanks for your help and patience, I think we have a clean solution now. Please close the PR if nothing stands in the way.

Thank you @xijo! I hope that we will have a chance to work together again. :)


Refactor ros2_ws image and scripts

Add sshd_config file to Dockerfile

Streamline build.sh script and support MacOS

Add server.sh script with arg parsing to spinup
a built image as a background SSH server.

Add connect.sh script as a shortcut for 'exec'
attaching an interactive shell to a running
container, with platform specific environment
variables and volumes for display configuration.

Add apt-key file downloaded from
http://repo.ros2.org/repos.key
to ros2_ws/config directory to add with apt-key in
the Dockerfile. Note: curl is not used because
it is not yet installed in the base ros image,
and cannot be installed with apt without the key!

Consolidate contents of ros2_ws config directory into
Dockerfile directly (99_aptget and update_bashrc),
both to reduce clutter and to allow passing the USER
variable instead of hardcoding ros2

Reduce the amount of setup sourcing done in the various
bashrc and entrypoint scripts in the Dockerfile, simply
sourcing the core ros and ros2_ws setup scripts at the top
of bashrc

Before I forget what I did, here are the changes I mainly made to enable CLion development. At the same time, I've tried to make the docker image namespace more consistent with the conventions I set out a while ago, and also found a convenient solution to the whole UID and GID thing on linux.
The idea for the workflow is to instantiate a given ros2 container only once, and have it run as a background process with an SSH server. This runs non-interactively as root, so on instantiation, it can copy the RSA authentication as well as change the UID and GID of a specified user (ros2) to match that of the host user. Then, subsequent sessions can use docker exec to attach to the existing container (rather than creating a new one each time).

How does this enable the CLion workflow? Because the ros2 sourcing happens at the top of the bashrc file, it is now evaluated even for non-interactive sessions (e.g. the CLion client ssh process). Add to this the ability to keep the ros2 user passwordless like before and you have a happy situation on your hands. There's some extra CMake magic to really get the full IDE experience with ros2 going, but at least in its current form you can load a source project and the colcon generated cmakelist and it will happily index it.

This looks super interesting and promising. It builds like a charm, the server.sh script correctly create the container, however on connect.sh I got:
access control disabled, clients can connect from any host
unknown shorthand flag: 'v' in -v
See 'docker container exec --help'.

The volume option does not appear to be an option for docker exec but for docker run


Make Pass enum non-exhaustive.

This enum will change over time and shouldn't be exhaustively matched.

Use #[non_exhaustive] attribute.

done


can I use Angular2 with Typings?

Hi - Today is my first entree into the Typescript world and I got a message saying to use Typings over TSD.
My question is I was following an example using angular2 with TSD.
I used
 typings install rx-lite --ambient --save

Which didn't work:
  typings install rx-lite --ambient --save

Which is fair enough, it isn't there.
The issue is really -- must I use TSD to use Angular2?  I saw several issues mentioning "Angular" (angular 1 I guess, since my error says there isn't an Angular2 registered.)
If "Yes.." Can/will TSD and Typings play nice together?  Or do I need to just use one of them?

Angular2 already has it's typings in node_modules, all you have to do is have the reference in your main file, as in: https://github.com/ericmdantas/angular2-typescript-todo/blob/master/index.ts#L1

@aplatypus Yes, TSD and Typings can play together, but it's not recommended since they both output to the same directory (but won't conflict). And no, you don't need Typings or TSD to use TypeScript - it's only needed for the typings of libraries not in TypeScript. For Angular 2, it already comes with type definitions as @ericmdantas has mentioned. Did you manage to get things working?
Feel free to continue the discussion if you have more issues!

I think I asked the wrong question.  The thing we will do is to use a definition manager with our projects.  The examples we have show a line like this:
 tsd query angular2 --action install

My question was about using Typings to manager Anguar2 definitions.  We have little interest i the work-around alternatives because we have a lot to do.  It sounds like there's no definition for Angular2 at this stage.  So the answer would be "No."
That means we need to stick with the TSD approach because Angular2 is a show stopper.

As mentioned above, Angular 2 includes it's Typings in the node module. Using TSD or Typings makes no difference there. Your comments will aren't entirely clear. If you're trying to decide on which to use, I'd use Typings - I deprecated TSD and left a giant note about this on the homepage.


Method to refresh compiled  global css from scss like livereload/browsersync

Bug Report or Feature Request (mark with an x)
- [ ] bug report -> please search issues before submitting
- [x ] feature request

Versions.

@angular/cli: 1.4.2
node: 6.11.2
os: darwin x64
US-ST016LO-MLT:des
Desired functionality.
Our projects use a global scss file.  We need to have source maps to debug sass as we work, so currently we run ng serve --sourcemap --extractCss -o --hmr -e=hmr.  When editing a scss file, the css is compiled but the browser is not refreshed with the changes.
So, sometimes I will run the app without HMR just to force a reload on every save: ng serve --sourcemap --extractCss -o.
However, it would be preferable to have the CSS changes injected like the JS is with HMR.  In older projects we used Gulp and Browsersync, which would inject css changes without reloading the browser.
I have searched and searched on this, and many issues request this for SCSS in components which, while nice, is more than we require; just getting this for global scss/css file would be huge.
I don't see this on any roadmaps anywhere.  Is something like this being worked on?

I ran into this one today... well..., not so cool since we are transitioning from global styles to component styles right now and need to check changes in a HMR-way on both sides including source maps support.

+1 @Brocco would appreciate your thoughts on this.

Global style injection seems to work if you omit the --extractCss flag

@SystemR But then source maps don't work


Struct typedef in class fails with wrong struct size

Input C/C++ Header
class Foo {
    public:
    typedef struct {
        int abc;
    } Bar;

    Bar bar;
};

Bindgen Invokation
$ bindgen input.h -- -x c++

Actual Results
ERROR:bindgen::codegen::struct_layout: Calculated wrong layout for Foo, too more 4 bytes

/* automatically generated by rust-bindgen */

#[repr(C)]
#[derive(Debug, Copy)]
pub struct Foo {
    pub __bindgen_anon_1: Foo_Bar,
    pub bar: Foo_Bar,
}
#[repr(C)]
#[derive(Debug, Copy)]
pub struct Foo_Bar {
    pub abc: ::std::os::raw::c_int,
}
#[test]
fn bindgen_test_layout_Foo_Bar() {
    assert_eq!(::std::mem::size_of::<Foo_Bar>() , 4usize , concat ! (
               "Size of: " , stringify ! ( Foo_Bar ) ));
    assert_eq! (::std::mem::align_of::<Foo_Bar>() , 4usize , concat ! (
                "Alignment of " , stringify ! ( Foo_Bar ) ));
    assert_eq! (unsafe {
                & ( * ( 0 as * const Foo_Bar ) ) . abc as * const _ as usize }
                , 0usize , concat ! (
                "Alignment of field: " , stringify ! ( Foo_Bar ) , "::" ,
                stringify ! ( abc ) ));
}
impl Clone for Foo_Bar {
    fn clone(&self) -> Self { *self }
}
#[test]
fn bindgen_test_layout_Foo() {
    assert_eq!(::std::mem::size_of::<Foo>() , 4usize , concat ! (
               "Size of: " , stringify ! ( Foo ) ));
    assert_eq! (::std::mem::align_of::<Foo>() , 4usize , concat ! (
                "Alignment of " , stringify ! ( Foo ) ));
    assert_eq! (unsafe {
                & ( * ( 0 as * const Foo ) ) . bar as * const _ as usize } ,
                0usize , concat ! (
                "Alignment of field: " , stringify ! ( Foo ) , "::" ,
                stringify ! ( bar ) ));
}
impl Clone for Foo {
    fn clone(&self) -> Self { *self }
}

Expected Results
The struct typedef shouldn't be a member of the Foo struct.

Thanks for the bug report!
Looks like our anonymous field code is getting tripped up, and we're ending up with two Bar members:
pub struct Foo {
    pub __bindgen_anon_1: Foo_Bar,
    pub bar: Foo_Bar,
}


Fixes the thumbnail loading for animated stickers and emojis.

An error occurs during the channel thumbnail loading if an animated sticker or emoji is set as the cover:
Traceback (most recent call last):
  File "/app/telegram/channels.py", line 145, in get_channel_photo
    local_file = await client.download_profile_photo(chat, '/tmp/%s' % hash, download_big=is_large)
  File "/usr/local/lib/python3.7/site-packages/telethon/client/downloads.py", line 265, in download_profile_photo
    thumb=thumb, progress_callback=None
  File "/usr/local/lib/python3.7/site-packages/telethon/client/downloads.py", line 832, in _download_photo
    file_size = size.size
AttributeError: 'VideoSizeStickerMarkup' object has no attribute 'size'

These types should be ignored during the thumbnail search.

Example of a channel with a sticker as a cover: https://t.me/onboarding_ru


Typescript TSLinting issues

Typescript generation has code with the following issues.

Shadowed variables (no-shadowed-variable)
Use of var when it should be let or const (prefer-const, no-var keyword)

Closing this, TSLint has been replaced with ESLint


docs/podman-pod-create.1.md: add example with port mapping

Given that you can't change ports in a pod after creation[1], I thought it might be nice to include an example of how to set up the port mapping in the manpage.
Should the manpage mention you can't change ports after creation?
[1] https://developers.redhat.com/blog/2019/01/15/podman-managing-containers-pods/
"Most of the attributes that make up the Pod are actually assigned to the “infra” container.  Port bindings, cgroup-parent values, and kernel namespaces are all assigned to the “infra” container. This is critical to understand, because once the pod is created these attributes are assigned to the “infra” container and cannot be changed. For example, if you create a pod and then later decide you want to add a container that binds new ports, Podman will not be able to do this.  You would need to recreate the pod with the additional port bindings before adding the new container."

Sure, LGTM
/approve

bot, add author to whitelist

@jcpunk You need to add a signoff to your commit - git commit --amend -s and re-push

/ok-to-test

@jcpunk Thanks for the PR.
But you need to sign it.
git commit -a --amend -s
git push --force

Added sign off.

bot, retest this please

Test failures look like network flakes

Thanks @jcpunk
/lgtm


Add hook to enable horizon

This PR adds hooks to enable horizon service which is not enabled by default in a crc deploy . This is needed as we are trying to extend test-operator zuul gating job to include horizon testing .

/approve


Github actions for more connectivity!

We can implement github workflows for the following things:

Auto comment on issue Closed and Opened (already implemented in you'r repo)!!
Auto comment on PR mergs (already implemented in you'r repo)!!
Auto comment on PR raises ( i can work on this)?

Using this workflows makes you'r repo more interactive ! @Anuj3553
i'm expecting a level2 (or) level3 with gssoc-ext and hacktoberfest-accepted label

Hyy @smog-root, I'm assigning this issue to you.


Error parsing iconPath of registered providers

Start ADS
Register a new provider (easiest way is to install the PGSQL extension)

This error appears in the console :
ERR The "path" argument must be of type string. Received type object: Error: The "path" argument must be of type string. Received type object
    at validateString (file:///D:/src/azuredatastudio/out/vs/base/common/path.js:37:19)
    at Object.join (file:///D:/src/azuredatastudio/out/vs/base/common/path.js:435:17)
    at Object.joinPath (file:///D:/src/azuredatastudio/out/vs/base/common/resources.js:101:47)
    at toAbsolutePath (file:///D:/src/azuredatastudio/out/sql/workbench/parts/connection/common/connectionProviderExtension.js:163:42)
    at resolveIconPath (file:///D:/src/azuredatastudio/out/sql/workbench/parts/connection/common/connectionProviderExtension.js:195:13)

The issue is here : https://github.com/microsoft/azuredatastudio/blob/89c1c4897a4508a9562a9de0e483f29275655676/src/sql/workbench/parts/connection/common/connectionProviderExtension.ts#L187-L188
We're assuming that light and dark are string values - but that's not the case in the above scenario. They're URIs.
The issue seems to be that when we register a new provider we go through and resolve the icon paths for ALL extensions even if they've already been registered/resolved.
https://github.com/microsoft/azuredatastudio/blob/89c1c4897a4508a9562a9de0e483f29275655676/src/sql/workbench/parts/connection/common/connectionProviderExtension.ts#L168
So on startup the MSSQL provider is registered and the paths are resolved to full URIs. Then when this is called again for a new provider being registered we get the error.

Closing this as it was fixed by #7738 - @smartguest FYI you can have GitHub auto-close issues associated with a PR by using certain keywords such as Fixes, e.g.
Fixes #7471
https://help.github.com/en/articles/closing-issues-using-keywords


Render to regex syntax

I'm making a new form library like formlets, and considering the ability to embed a regex as a validator/parser which would run on the server side with regex-applicative upon submission, but also, as a UX optimization, compile the same regex to a [a-z]{2}+-style regex to be used as the pattern=".." attribute for html5 (avoiding a roundtrip just to do a simple text format check). This would enable a developer to build forms with client and server-side validation composed using the same regex-applicative recipe.
So the question is: is there already a library or module that would convert an RE s a to Text? E.g.
render (many (sym 'a')) => "a*"

I assume I could write my own, but perhaps it already exists.
Thanks!

Unfortunately, this is not possible because sym 'a' is translated to psym (== 'a'), and you cannot extract 'a' out of (== 'a').

@feuerbach Ah, ok. So it was worth asking. Thanks.
I suppose then I would need to wrap up the API with an interface which doesn't expose psym. E.g.
data Regex a

with a Regex a -> RE Char a conversion function. Whipping up a simple GADT that is the same as the RE one but without this capability should be trivial, and I can re-use the rest of the library.
If you're interested, I could send it as a PR against this package as e.g. Text.Regex.Applicative.Renderable or w/e, otherwise package it as regex-applicative-renderable or something. I'm sure I'll find other uses than just this form package, and the work is probably trivial.

Yeah, or maybe have a class containing sym and perhaps some other functions, and make both types instances of that class.
The other constructors it should probably support are:

Recognizing a set (as in Data.Set.Set) of characters — can be simulated by summing individual syms, but could be implemented more efficiently.
Recognizing a class (as in a POSIX regex class — alpha, alnum etc.) of characters — can in theory be implemented via individual syms, but in practice would be prohibitive.

This new module/representation might also support more efficient compilation, i.e. it's potential utility won't be restricted just to rendering. Let's call it Text.Regex.Applicative.Char?

OK, great then. When I get to this part of my lib I'll circle back to this issue. Thanks, Roman.

A Set of characters will perform considerably worse, for almost all
operations, than an IntMap of their equivalents.
On Sat, Sep 14, 2019, 4:23 PM Roman Cheplyaka<EMAIL_ADDRESS>wrote:

Yeah, or maybe have a class containing sym and perhaps some other
functions, and make both types instances of that class.
The other constructors it should probably support are:

Recognizing a set (as in Data.Set.Set) of characters — can be
simulated by summing individual syms, but could be implemented more
efficiently.
Recognizing a class (as in a POSIX regex class — alpha, alnum etc.)
of characters — can in theory be implemented via individual syms, but in
practice would be prohibitive.

This new module/representation might also support more efficient
compilation, i.e. it's potential utility won't be restricted just to
rendering. Let's call it Text.Regex.Applicative.Char?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/feuerbach/regex-applicative/issues/36?email_source=notifications&email_token=AAOOF7LLQYO3GZSCCMMTNE3QJVB3NA5CNFSM4IWRCSDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6XDKUQ#issuecomment-531510610,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAOOF7NXIJDAAYRNRC5ZRMTQJVB3NANCNFSM4IWRCSDA
.

@treeowl do you have benchmarks for that?

I stumbled upon this discussion today. I had written a Scala regex library that a while ago I rewrote to more or less be a port of regex-applicative. The way I handled this in my library is that the the equivalent of the Symbol constructor (I call it Elem) has a separate metadata field of an abstract type m (which ends up needing to be another type parameter on RE).
For character (and any other discrete type) regexes, the m type ends up being a type that looks something like:
data Match a = Literal a | Wildcard | Allow (Diet a) | Forbid (Diet a)

where Diet is a discrete interval tree. This represents the notion of character classes in traditional regular expressions, supporting unions and intersections. You can then write helper methods that implement the a -> maybe b function based on the Match.
In addition to being able to get a string representation of the regex, a nice benefit of having this metadata around is that you can then convert a regular expression to a Quickcheck generator that generates values that match that regex. I have a demo page here that I think is kind of fun.
Now is probably a good time to say thanks for creating this library, @feuerbach! As soon as I saw it I knew that I wanted to rewrite my Scala library :)

Thanks @ceedubs, those are some nice ideas.


❓ Is reanimated v3 supported yet?

Question
I tried using reanimated v3 with react-native-vision-camera v2.11.2.
It generally works but frame processors in particular do not work on Android. (It works on iOS.)
Specifically, I am trying to use vision-camera-code-scanner v0.2.0, which relies on frame processors.
The device logs I'm seeing in Flipper are:
Setting new Frame Processor...
Found CameraView!
Adapting Shareable value from function (conversion to worklet)...
Successfully created worklet!
Called Frame Processor callback, but `frameProcessor` is null!
Called Frame Processor callback, but `frameProcessor` is null!
Called Frame Processor callback, but `frameProcessor` is null!
...
Removing Frame Processor...
Frame Processor removed!

Nothing crashes, but the frameProcessor is null warnings get logged very often (equal to my frameProcessorFps value of 5). Did reanimated v3 at HEAD break the frame processor code in this library? Thanks!
What I tried
No response
VisionCamera Version
2.11.2
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

Hey! That's interesting, I didn't try REA 3 yet. Let me know if you find anything that might be the cause of this issue!

Are there any logs or specifically areas of the codebase I should be looking at? I'm not too familiar with how to debug why frameProcessor is null. Thanks!

Vision camera fails to be build on rn 69. few issues. react-native directory used to have only react-native aar, but now it has hermes aar too. This leads finding rnAAR to fail.
If that is fixed the next error comes due to REA no longer containing pre-built aar, this leads extractJNI to fail

Can you share the folder structure on RN <0.68 and RN 0.69 for comparison?

This is 69

This is 68

similarly, REA doesn't have AAR anymore with 3.0.0

I was able to get the react native and android AAR paths to work. Couldn't get REA to work. Couldn't find the jni headers you were requiring earlier anymore in REA 3.

Hey - yep REA 3 is supported now! Both in V3 and V2 of VisionCamera


Migrate the Material Date pickers to M3 Reprise

This PR is entirely the work of @darrenaustin - https://github.com/flutter/flutter/pull/118603.
Part of: https://github.com/flutter/flutter/issues/91605
Updated the Date Pickers  with support for Material Design 3.

In order to use the date pickers with the new Material 3 defaults, turn on the useMaterial3 flag in the ThemeData:
  return MaterialApp(
    theme: ThemeData(useMaterial3: true),
    // ...
  );

This PR includes a new DatePickerTheme that can be used to configure the look of the components used in the date picker widgets (i.e. showDatePicker, showDateRangePicker, DatePickerDialog, DateRangePickerDialog, CalendarDatePicker, and InputDatePickerTextField.
Fixes: #101481
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is [test-exempt].
[x] All existing and new tests are passing.

Also, see this https://github.com/flutter/flutter/pull/118603#discussion_r1086018643

An example is a good idea; plan to address that in a separate PR: https://github.com/flutter/flutter/pull/118603#discussion_r1086009128


Better ajax requests

According to #17, ajax() should be improved. I think the ideal would be something like nanoajax but a bit more prescriptive:
var options = {
  method: 'POST',   // or 'post'
  action: '/wherever',
  data: { name: 'value' },   // or 'body'?
  headers: { name: 'value' }
};
ajax(options, function(err, data){
  // data is an object parsed from a returned JSON
});

Or maybe the data could still be passed as a parameter since it'll be normally present:
ajax({}, { name: 'value' }, function(){});

Of course we'll also need documentation and tests.

Required parameters are passed as parameters. Optional parameters as an optional array. The only really required parameter is the URL, since the method can be defaulted to POST and the data can be defaulted to {} (however I still like it to be a default parameter). Example:
var data = {};
var options = {
  method: 'POST',
  headers: {}
};
ajax('/update', data, options, after, before);


Created projects don't load - infinite loop

Hi,
just finished install of codiad on UBUNTU18.04, PHP7.2, NGINX1.14.0
All went well.
Up to the creation of a new project where the system goes in an infinite loop.
I can see the projects folder is created in codiad/workspace  and in the case of a project from github the files are successfully downloaded in the folder.
So in the back all seems to be working...but the ide is not able to load the project. All I see is an infinite looping sign in the Codiad Explorer
What can be the solution?
Grts
Mario

I'm having the same issue on a freshly installed Ubuntu 18;04, PHP 7.2 with Apache 2.4.29.
The project loading icon in the left top corner just keeps turning in circles and nothing else happens.
Apache access.log:
<IP_ADDRESS> - - [15/Aug/2018:15:57:18 +0200] "GET /editor/components/user/controller.php?action=verify HTTP/1.1" 200 486 "https://domain.com/editor/" "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0"
Apache error.log:
[Wed Aug 15 15:28:19.525360 2018] [php7:error] [pid 23294] [client <IP_ADDRESS>:39942] PHP Fatal error:  Cannot redeclare mb_ord() in /var/www/html/editor/lib/diff_match_patch.php on line 2079, referer: https://domain.com/editor/
I edited /var/www/html/editor/lib/diff_match_patch.php and put comments around the offending code and then Codiad started working again.  Seems those functions are already available in PHP 7.2, so no need to redeclare them (like the message in error.log says). I'm sure there is a more elegant way to fix this, but this works for me for now.
/*
function mb_ord($v) {
$k = mb_convert_encoding($v, 'UCS-2LE', 'UTF-8');
$k1 = ord(substr($k, 0, 1));
$k2 = ord(substr($k, 1, 1));
return $k2 * 256 + $k1;
}
function mb_chr($num){
return mb_convert_encoding('&#'.intval($num).';', 'UTF-8', 'HTML-ENTITIES');
}
*/
PS: After I commented out just the function mb_ord(), I got a same error about mb_chr(), that's why I commented them both out.
Hope it helps.
Kind regards, Elko

Super!!
Had the exact same errors in the nginx error logs.
Commented both functions....problem seems solved!
Finally some coding again!!
Thx a lot!
Mario

Glad you confirmed the issue and the "fix".  Though on second thought, I cannot determine if PHP's implementation of the functions mb_ord() and mb_chr() are the same as intended by the Codiad project. (I did a configure&&make of the PHP 7.2.7 source and was not sure if the output of those functions is the same).
To avoid any problems with php-mbstring multi-byte encoded files in Codiad, I did the following.
First, I decided to check the PHP version when these mb_ord() and mb_chr() functions were first implemented, then looked at the PHP source of them, to no avail.  Guess the Codiad developers have to look into this (if those functions have the same result).
My version check was this:
$php_check_version = (float)PHP_VERSION;
if ($php_check_version < 7.2) {
       function mb_ord($v) { ... function code here ... }
       function mb_chr($num) { ... function code here ... }
}

But since I don't have a clue if the PHP implementation of these functions is the same as those provided by Codiad, I decided a safer approach.
For now, I've grepped around in the Codiad-master source a bit and come to this fix, renaming the Codiad mb_ord() and mb_chr() functions, so their intended purpose would not be undone by just commenting those functions out.  It's only a couple of instances in the "diff_match_patch.php" file.
#> sed -i 's!\(mb_ord\)!codiad_\1!g;s!\(mb_chr\)!codiad_\1!g' diff_match_patch.php
It changes the Codiad mb_ord() function to codiad_mb_ord() and the same for the mb_chr() function.
For me, this works.  Guess we have to wait until this gets fixed in Codiad-master.
Kind regards, Elko

Just some notes (don't know if the results of the functions are the same either):
  // PHP version checking
if (version_compare(PHP_VERSION, '7.2.0') >= 0) {
  // at least version 7.2.0
}

  // Safer to just wrap:
if (!function_exists('mb_ord'} {
  function mb_ord($v) { ... }
}
if (!function_exists('mb_chr') {
  function mb_chr($num) { ... }
}

Welcome to the wonderfull world of PhP 7.2 and his drop of mb_string(). Of course, Ubuntu 18.04 LTS forced update to PhP 7.2, so...

I had fixed it .

Thanks for the solution, I simply renamed mb_ord to mb_ord1 and same for mb_chr that way Incase the PHP defines versions are different from codiad's it'll isebthe codiad definitions to be safe, thank you!

Glad you confirmed the issue and the "fix". Though on second thought, I cannot determine if PHP's implementation of the functions mb_ord() and mb_chr() are the same as intended by the Codiad project. (I did a configure&&make of the PHP 7.2.7 source and was not sure if the output of those functions is the same).
To avoid any problems with php-mbstring multi-byte encoded files in Codiad, I did the following.
First, I decided to check the PHP version when these mb_ord() and mb_chr() functions were first implemented, then looked at the PHP source of them, to no avail. Guess the Codiad developers have to look into this (if those functions have the same result).
My version check was this:
$php_check_version = (float)PHP_VERSION;
if ($php_check_version < 7.2) {
       function mb_ord($v) { ... function code here ... }
       function mb_chr($num) { ... function code here ... }
}

But since I don't have a clue if the PHP implementation of these functions is the same as those provided by Codiad, I decided a safer approach.
For now, I've grepped around in the Codiad-master source a bit and come to this fix, renaming the Codiad mb_ord() and mb_chr() functions, so their intended purpose would not be undone by just commenting those functions out. It's only a couple of instances in the "diff_match_patch.php" file.
#> sed -i 's!\(mb_ord\)!codiad_\1!g;s!\(mb_chr\)!codiad_\1!g' diff_match_patch.php
It changes the Codiad mb_ord() function to codiad_mb_ord() and the same for the mb_chr() function.
For me, this works. Guess we have to wait until this gets fixed in Codiad-master.
Kind regards, Elko

Solved

you all are the excellent person , i fixed it already and do my jobs done.

Bonjour jai la meme erreur mai j'ai toujour invalid path

Hey i'm having a similar but slightly different issue - php 8.1 on ubuntu 22.04 spinning wheel at project root in the explore window when trying to load projects php error log shows me "[Fri Jul 01 20:26:15.328201 2022] [php:error] [pid 732] [client <IP_ADDRESS>:52246] PHP Fatal error:  Uncaught TypeError: Cannot access offset of type string on string in /var/www/html/components/filemanager/controller.php:57\nStack trace:\n#0 {main}\n  thrown in /var/www/html/components/filemanager/controller.php on line 57, referer: http://<IP_ADDRESS>/"
any ideas?

found a solution - tested it and submitted a pull request #1138


keyboardDidHide doesn't get fired on some devices

Description
I see this magic number in native code for Keyboard on android:
mMinKeyboardHeightDetected = (int) PixelUtil.toPixelFromDIP(60);

In my app, when I setup a listener for keyboardDidHide event, the handler doesn't get fired. Instead, keyboardDidShow handler gets fired with endCoordinates.height value of around 73. I propose to up that magic number to 80 value or to add top notch value on top of 60, since this commit changed the logic for keyboardDidHide event.
I was able to fix the bug by adding these lines on top of my keyboardDidShow handler:
  _keyboardDidShow = (e) => {
    if (e.endCoordinates.height < 100) {
      this._keyboardDidHide();
      return;
    }
    /* other code */
  }

The device I used was Samsung Galaxy S20FE. It has a big notch at the top and it also has irregular bigger than usual height of bottom buttons (the bug is only there when using 3-button navigation. When using gesture navigation the bug does not occur).
Version
0.67.1
Output of npx react-native info
System:
OS: macOS 12.2
CPU: (8) x64 Apple M1
Memory: 29.16 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.2.0 - ~/.nvm/versions/node/v16.2.0/bin/node
Yarn: 1.22.17 - ~/dev/emma-master/node_modules/.bin/yarn
npm: 7.13.0 - ~/.nvm/versions/node/v16.2.0/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.11.2 - /Users/pistonsky/.rvm/rubies/ruby-2.7.4/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
Android SDK:
API Levels: 23, 28, 29, 30, 31
Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.2, 30.0.3
System Images: android-29 | Google APIs ARM 64 v8a, android-30 | Google APIs ARM 64 v8a, android-30 | Google APIs Intel x86 Atom, android-31 | Google APIs ARM 64 v8a, android-31 | Google Play ARM 64 v8a, android-32 | Google Play ARM 64 v8a, android-32 | Google Play Intel x86 Atom_64, android-S | Google APIs ARM 64 v8a, android-Sv2 | Google APIs ARM 64 v8a
Android NDK: 22.1.7171670
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7621141
Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_275 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: 0.67.1 => 0.67.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
Unfortunately, I was not able to reproduce this bug on 0.67.1 clean install, even using the same device that had that bug on my project. But still, that 60 magic value in combination with those changes 4 months ago seems to be the cause of it.
Snack, code example, screenshot, or link to a repository
No response

Your issue is in this lines of code. You say that keyboardDidShow is triggered when it should not, caused by a certain combination of keyboardHeight and notchHeight.
If I correctly understand you experience this when you navigate backwards with this button.
https://github.com/facebook/react-native/blob/cfa42605989eee5a9de42bdb1259fb7f4d9451fb/ReactAndroid/src/main/java/com/facebook/react/ReactRootView.java#L667-L679
But I would prefer to reproduce this problem or at least have a video of the problem before writing a fix.
Thanks a lot :pray:

The same problem occurs on Xiaomi devices, if virtual navigation keys are enabled, the keyboardDidShow event is still sent even if the keyboard does not pop up,
But after only needing to rotate the screen orientation once, this event will return to working normally

I recorded a video demonstrating it:
https://user-images.githubusercontent.com/20365169/158751241-0391a29e-bac7-4987-bdaa-6bbcfc53f52f.mp4
The code for the application to listen for keyboard events is as follows:
Keyboard.addListener('keyboardDidShow', (e) => {
  Alert.alert('keyboardDid --> Show', 'keyboard height: ' + e.endCoordinates.height, [
    {
      text: 'Cancel',
    },
  ])
})
Keyboard.addListener('keyboardDidHide', (e) => {
  Alert.alert('keyboardDid --> Hide', 'keyboard height: ' + e.endCoordinates.height, [
    {
      text: 'Cancel',
    },
  ])
})

@lyswhut Can you provide the source code of the complete app that you used to record the demo please?

I found the cause of this issue in my project. The reason was usage of react-native-extra-dimensions-android package.
When you have a style in your project like so:
const styles = StyleSheet.create({
  container: {
    height: ExtraDimensions.get('REAL_WINDOW_HEIGHT'),
  },
});

all keyboard events will be broken. When app starts, you will receive keyboardDidShow event right away, with some random relatively small value (for example, Samsung S20 has 81.52381134033203 value). However, no keyboard is shown, so this event should not even be dispatched. This can potentially break bottom tab bar if you set it to auto-hide on keyboard. Be aware!
Also, when you actually do focus some text input, the height of keyboard within the event will be wrong - it will be more than it actually is, by the value that comes when you hide the keyboard. And when you hide the keyboard, no keyboardDidHide event will be dispatched. Instead, you will receive keyboardDidShow.
This behavior occurs on some devices, not all of them. For example, I've seen it on Samsung S20 when navigation is setup to use 3-button navigation (soft navigation bar at the bottom).
How to reproduce
Start a new react native project, then install this package, and add code above. I've setup a repo for convenience

I found the cause of this issue in my project. The reason was usage of react-native-extra-dimensions-android package.

I also use this package, as long as any method of this package is called, this problem occurs, for example:
// index.js
import ExtraDimensions from 'react-native-extra-dimensions-android'
import { Keyboard, Alert } from 'react-native'

ExtraDimensions.getRealWindowWidth()

Keyboard.addListener('keyboardDidShow', (e) => {
  Alert.alert('keyboardDid --> Show', 'keyboard height: ' + e.endCoordinates.height, [
    {
      text: 'Cancel',
    },
  ])
})
Keyboard.addListener('keyboardDidHide', (e) => {
  Alert.alert('keyboardDid --> Hide', 'keyboard height: ' + e.endCoordinates.height, [
    {
      text: 'Cancel',
    },
  ])
})


[ENG-5367] Dep-group: datetime

Purpose
Update python-dateutil
Changes
replaced datetime.utcfromtimestamp
QA Notes
Please make verification statements inspired by your code and what your code touches.

Verify
Verify

What are the areas of risk?
Any concerns/considerations/questions that development raised?
Documentation

Side Effects

Ticket
https://openscience.atlassian.net/browse/ENG-5367

Looks good!  Merged.


VPC Gen 2

I saw on the overview page

Service Name
Package name

VPC
vpcv1

VPC Gen 1
vpcclassicv1

When will VPC Gen 2 be supported?
Some features like block storage for Gen 2 can't use BYOK because its depended on this SDK being updated"
https://github.com/IBM-Cloud/terraform-provider-ibm/issues/1673#issuecomment-670401620

hi. vpcv1 is Gen2

Thank you for that clarification. @astha-jain I meant VPC Gen 2 BYOK feature update.
"We are waiting for the SDK to update the BYOK feature for Gen2
https://github.com/IBM/vpc-go-sdk/
Once we have the SDK rolled out with this feature we will support for Gen2 also"

https://github.com/IBM/vpc-go-sdk/releases/tag/v0.0.3 supports BYOK for gen 2.

The terraform team is waiting for the SDK to update, any idea when this will be?


ls: Reduce binary size of ls by removing regex crate

Became interested in reducing the size of the ls binary after reading this: https://www.reddit.com/r/rust/comments/riqolp/whats_in_a_rust_binary/
Via 'cargo bloat', I found that the regex crate was the main culprit, and was a sub-dependency of the globset package.  I was able to replace with the glob crate, as there is no need for full regex implementation in ls.
This change reduces the release binary size of ls by over 1/2.

terrific. would it be possible to include that in the ci ?

terrific. would it be possible to include that in the ci ?

I don't have much experience with different types of CI, but I suppose you could warn on including bloat-y crates and suggest using 'cargo bloat, tree.'  Here is a sample output of 'cargo bloat --crates -p uu_ls'  before I made any changes:
File  .text     Size Crate
14.2%  27.6% 385.6KiB std
11.2%  21.7% 303.8KiB clap
7.2%  14.0% 196.0KiB regex_syntax
6.5%  12.7% 177.1KiB regex
3.8%   7.3% 102.4KiB uu_ls
2.9%   5.7%  79.4KiB globset
2.8%   5.4%  75.1KiB aho_corasick
0.7%   1.4%  19.3KiB chrono
0.6%   1.2%  16.3KiB [Unknown]
0.5%   1.1%  14.7KiB memchr
0.5%   0.9%  12.8KiB uucore
0.4%   0.8%  11.7KiB lscolors
0.2%   0.5%   6.3KiB ansi_term
0.2%   0.3%   4.3KiB term_grid
0.1%   0.3%   3.9KiB os_display
0.1%   0.2%   2.8KiB strsim
0.1%   0.1%   1.7KiB textwrap
0.0%   0.1%   1.0KiB once_cell
0.0%   0.0%     304B number_prefix
0.0%   0.0%     256B log
0.0%   0.0%     704B And 6 more crates. Use -n N to show more.
51.3% 100.0%   1.4MiB .text section size, the file size is 2.7MiB


Games not correctly restored after saving.

Every time I've tried to restore a modded game from a save, the game has come back only partially modded. We've now  had a report from Solracd saying that they've experienced the same thing.
Not sure if it's an issue we can fix, but I've been forgetting to mention it for the last few weeks, so though I'd raise it as an issue here.

FWIW, activating HR from a save wasn't explicitly part of core.  My thinking was that (at least without some amount of work), we couldn't determine whether a save was modded in the first place.
But thinking about this for the first time in a long time, perhaps it's not our responsibility to verify/keep the integrity of a save.  If a player wants to load mods for a save, why not let them.  I'll work on this and see what we think.


A couple of yup features that would be nice to have

I'm really impressed with this project and its ease of use.  There are a couple of features from yup that would be really useful.
#1. yup.object().noUnknown() - This feature causes yup to throw an error on validation if there's a property on the object that doesn't match the schema
#2. ValidationError.path - When yup throws a validation error, it specifies where in the schema that error occurred which can be very helpful for large schemas

Thanks! I created separate dedicated issues for each of these (#16 and #17). Should get around to implementing both of these relatively soon.

@JohnDavisSDS<EMAIL_ADDRESS>includes vastly improved error handling, check out the Errors section of the Readme for details 🤙

@JohnDavisSDS Zod also now supports the equivalent of .noUnknown.
Or more specifically, I clarified in the docs that "no unknown keys" is the default behavior, since this hews more closely to how TypeScript works. You're now able to all unknown keys by calling .nonstrict() on any object schema 👍


Test s390x fix for ocaml-git.

ocaml-ci doesn't support pin-depends in vendored libraries, but I tested this manually (by removing the version constraints on these packages from the generated Dockerfile) and the tests passed.

Thanks, I will try to do a release next week.


Issue with weird readings from bluetooth on JKB2A20S20P

Hi,
I wonder if anyone can help - my ESP32 home and Home Assistant have been working perfectly on my bluetooth link to my JKB2A20S20P (via my ESP32 )- and then collecting that info into Home Assistant. It's been running for about a year, some time outs and usually ESP issues but nothing a simple restart wouldn't fix.
I don't know what happened, something broke - I thought it might be the ESP32 so I replaced it, still the same readings.
I get perfect readings on bluetooth with the BMS app (so I know the BMS device is sending out ok readings)
When I connect the ESP Home - it connects to the bluetooth and the readings are spurious for example here's some of my logs (ignore the names, I never bothered to rename them but it all works fine) - Cell voltages appear to be reading but total voltage, temperature etc but others are just either zero or some weird number like this 'capacity remaining': Sending state 14286.84863 Ah' (max Ah normally is 272 so that number should be anything below that.)
here's a brief log capture from the ESP
Like I say, everything was working perfectly a couple of days ago, rebooted the ESP and then this ... replaced and still the same.
Any ideas what's broken and where - I've rebuilt the code and now updated Home Assistant as I was a few versions out of date - no difference, still the same.
0:51:27][I][jk_bms_ble:467]: Cell info frame (version 2, 300 bytes) received
[10:51:27][D][sensor:094]: '${name} cell voltage 1': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 2': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 3': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 4': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 5': Sending state 3.31100 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 6': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 7': Sending state 3.31300 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 8': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 9': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 10': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 11': Sending state 3.31800 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 12': Sending state 3.31800 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 13': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 14': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 15': Sending state 3.31400 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} cell voltage 16': Sending state 3.31100 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} min cell voltage': Sending state 3.31100 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} max cell voltage': Sending state 3.31800 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} average cell voltage': Sending state 0.00000 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} delta cell voltage': Sending state 0.00000 V with 3 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} max voltage cell': Sending state 1.00000  with 0 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} min voltage cell': Sending state 1.00000  with 0 decimals of accuracy
[10:51:27][D][jk_bms_ble:557]: Unknown112: 0x00 0x00
[10:51:27][D][jk_bms_ble:562]: Wire resistance warning bitmask: 0x00 0x00 0x00 0x00
[10:51:27][D][sensor:094]: '${name} total voltage': Sending state 0.00000 V with 2 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} current': Sending state 0.00000 A with 2 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} power': Sending state 0.00000 W with 2 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} charging power': Sending state 0.00000 W with 2 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} discharging power': Sending state 0.00000 W with 2 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} temperature sensor 1': Sending state 0.00000 °C with 1 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} temperature sensor 2': Sending state 0.00000 °C with 1 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} power tube temperature': Sending state 0.00000 °C with 1 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} errors bitmask': Sending state 0.00000  with 0 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} balancing current': Sending state 0.00000 A with 2 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} state of charge': Sending state 0.00000 % with 0 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} capacity remaining': Sending state 14286.84863 Ah with 0 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} total battery capacity setting': Sending state 0.00000 Ah with 0 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} charging cycles': Sending state 53038.00000  with 0 decimals of accuracy
[10:51:27][D][sensor:094]: '${name} total charging cycle capacity': Sending state 308.41501 Ah with 3 decimals of accuracy
[10:51:28][D][jk_bms_ble:647]: Unknown158: 0x49 0xE9 (always 0x64 0x00?)
[10:51:28][D][jk_bms_ble:650]: Unknown160: 0xFF 0xFF (always 0xC5 0x09?)
[10:51:28][D][sensor:094]: '${name} total runtime': Sending state 8913059.00000 s with 0 decimals of accuracy
[10:51:28][D][jk_bms_ble:663]: Unknown168: 00.00.A8.F<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>E.00.00.00.C<IP_ADDRESS>.<IP_ADDRESS>.D0.7A.6F.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.00 (46)
[10:51:28][D][jk_bms_ble:677]: Unknown189: 0x01 0x64
[10:51:28][D][jk_bms_ble:681]: Unknown192: 0x00
[10:51:28][D][jk_bms_ble:683]: Unknown193: 0x00 0xD0 (0x00 0x8D)
[10:51:28][D][jk_bms_ble:685]: Unknown195: 0x7A 0x6F (0x21 0x40)
[10:51:28][W][component:214]: Component esp32_ble took a long time for an operation (0.46 s).
[10:51:28][W][component:215]: Components should block for at most 20-30ms.
[10:51:37][I][jk_bms_ble:467]: Cell info frame (version 2, 300 bytes) received
[10:51:37][D][sensor:094]: '${name} cell voltage 1': Sending state 3.31400 V with 3 decimals of accuracy
[10:51:37][D][sensor:094]: '${name} cell voltage 2': Sending state 3.31400 V with 3 decimals of accuracy
[10:51:37][D][sensor:094]: '${name} cell voltage 3': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:37][D][sensor:094]: '${name} cell voltage 4': Sending state 3.31800 V with 3 decimals of accuracy
[10:51:37][D][sensor:094]: '${name} cell voltage 5': Sending state 3.31800 V with 3 decimals of accuracy
[10:51:37][D][sensor:094]: '${name} cell voltage 6': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} cell voltage 7': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} cell voltage 8': Sending state 3.31400 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} cell voltage 9': Sending state 3.31300 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} cell voltage 10': Sending state 3.30300 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} cell voltage 11': Sending state 3.31400 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} cell voltage 12': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} cell voltage 13': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} cell voltage 14': Sending state 3.31300 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} cell voltage 15': Sending state 3.31300 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} cell voltage 16': Sending state 3.31300 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} min cell voltage': Sending state 3.30300 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} max cell voltage': Sending state 3.31800 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} average cell voltage': Sending state 0.00000 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} delta cell voltage': Sending state 0.00000 V with 3 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} max voltage cell': Sending state 1.00000  with 0 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} min voltage cell': Sending state 1.00000  with 0 decimals of accuracy
[10:51:38][D][jk_bms_ble:557]: Unknown112: 0x00 0x00
[10:51:38][D][jk_bms_ble:562]: Wire resistance warning bitmask: 0x00 0x00 0x00 0x00
[10:51:38][D][sensor:094]: '${name} total voltage': Sending state 0.00000 V with 2 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} current': Sending state 0.00000 A with 2 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} power': Sending state 0.00000 W with 2 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} charging power': Sending state 0.00000 W with 2 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} discharging power': Sending state 0.00000 W with 2 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} temperature sensor 1': Sending state 0.00000 °C with 1 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} temperature sensor 2': Sending state 0.00000 °C with 1 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} power tube temperature': Sending state 0.00000 °C with 1 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} errors bitmask': Sending state 0.00000  with 0 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} balancing current': Sending state 0.00000 A with 2 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} state of charge': Sending state 0.00000 % with 0 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} capacity remaining': Sending state 14286.84863 Ah with 0 decimals of accuracy
[10:51:38][D][sensor:094]: '${name} total battery capacity setting': Sending state 0.00000 Ah with 0 decimals of accuracy
[10:51:48][I][jk_bms_ble:467]: Cell info frame (version 2, 300 bytes) received
[10:51:48][D][sensor:094]: '${name} cell voltage 1': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:48][D][sensor:094]: '${name} cell voltage 2': Sending state 3.31200 V with 3 decimals of accuracy
[10:51:48][D][sensor:094]: '${name} cell voltage 3': Sending state 3.31300 V with 3 decimals of accuracy
[10:51:48][D][sensor:094]: '${name} cell voltage 4': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:48][D][sensor:094]: '${name} cell voltage 5': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:48][D][sensor:094]: '${name} cell voltage 6': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:48][D][sensor:094]: '${name} cell voltage 7': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:48][D][sensor:094]: '${name} cell voltage 8': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:48][D][sensor:094]: '${name} cell voltage 9': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:48][D][sensor:094]: '${name} cell voltage 10': Sending state 3.30800 V with 3 decimals of accuracy
[10:51:48][D][sensor:094]: '${name} cell voltage 11': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:48][D][sensor:094]: '${name} cell voltage 12': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:48][D][sensor:094]: '${name} cell voltage 13': Sending state 3.31800 V with 3 decimals of accuracy
[10:51:48][D][sensor:094]: '${name} cell voltage 14': Sending state 3.31800 V with 3 decimals of accuracy
[10:51:49][D][sensor:094]: '${name} cell voltage 15': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:58][I][jk_bms_ble:467]: Cell info frame (version 2, 300 bytes) received
[10:51:58][D][sensor:094]: '${name} cell voltage 1': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:58][D][sensor:094]: '${name} cell voltage 2': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:58][D][sensor:094]: '${name} cell voltage 3': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:58][D][sensor:094]: '${name} cell voltage 4': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:58][D][sensor:094]: '${name} cell voltage 5': Sending state 3.31800 V with 3 decimals of accuracy
[10:51:58][D][sensor:094]: '${name} cell voltage 6': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:58][D][sensor:094]: '${name} cell voltage 7': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:58][D][sensor:094]: '${name} cell voltage 8': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:58][D][sensor:094]: '${name} cell voltage 9': Sending state 3.31500 V with 3 decimals of accuracy
[10:51:58][D][sensor:094]: '${name} cell voltage 13': Sending state 3.31700 V with 3 decimals of accuracy
[10:51:58][D][sensor:094]: '${name} current': Sending state 0.00000 A with 2 decimals of accuracy
[10:51:58][D][sensor:094]: '${name} capacity remaining': Sending state 14286.84863 Ah with 0 decimals of accuracy
[10:51:58][D][sensor:094]: '${name} total battery capacity setting': Sending state 0.00000 Ah with 0 decimals of accuracy
[10:51:59][D][sensor:094]: '${name} charging cycles': Sending state 53047.00000  with 0 decimals of accuracy
[10:51:59][D][sensor:094]: '${name} total charging cycle capacity': Sending state 285.65601 Ah with 3 decimals of accuracy
[10:51:59][D][jk_bms_ble:647]: Unknown158: 0xF7 0xEA (always 0x64 0x00?)
[10:51:59][D][jk_bms_ble:650]: Unknown160: 0xFF 0xFF (always 0xC5 0x09?)
[10:51:59][D][sensor:094]: '${name} total runtime': Sending state 8913059.00000 s with 0 decimals of accuracy
[10:51:59][D][jk_bms_ble:663]: Unknown168: 00.00.83.F<IP_ADDRESS>F.<IP_ADDRESS>.<IP_ADDRESS>E.00.00.00.F<IP_ADDRESS>.<IP_ADDRESS>.EF.7A.6F.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.<IP_ADDRESS>.00 (46)
[10:51:59][D][jk_bms_ble:677]: Unknown189: 0x01 0x64
[10:51:59][D][jk_bms_ble:681]: Unknown192: 0x00
[10:51:59][D][jk_bms_ble:683]: Unknown193: 0x00 0xEF (0x00 0x8D)
[10:51:59][D][jk_bms_ble:685]: Unknown195: 0x7A 0x6F (0x21 0x40)
[10:51:59][W][component:214]: Component esp32_ble took a long time for an operation (0.43 s).

I was just reading through a few issues - discovered that this part had changed (didn't realise)
'I assume you are using the wrong protocol_version (JK02 vs JK02_32S).' from @syssi
https://github.com/syssi/esphome-jk-bms/discussions/329#discussioncomment-5926542
Updated and all works (love it when a plan comes together) - hopefully if anyone else has this.
Thanks for this


Internet Explorer 11 gives Promise error without polyfill

Without a Promise polyfill Axios won't work in Internet Explorer.

The first line of the project description on Github reads: "Promise based HTTP client for the browser and node.js"
So it's safe to say the library won't work if the environment doesn't support promises. I think not including the polyfill in the library is a great decision, as many developers have a strong preference when it comes to that.

@Etheryte It also states that the plugin works with IE8+ If you know Promise is not supported in IE11 and the like you are save. However not everyone is aware of this. I feel like this should be noted near the IE8+ supported icon.

It's covered in the readme, but if you don't know to look for it, then yes, you'll run into the issue.


Ability to run lxd recover as noninteractive

Could you make ability to run lxd recover as noninteractive.
It needs to run lxd recover in bash scripts.
I think would be great something like this:
lxd recover ctname --backend=dir --source=/var/lib/lxd/storage-pools/default
ctname may be optional, if empty - try to recover all finded ct's

We have a use-case I believe applicable for exposing "lxd recover" as an API endpoint or accepting input flags.
If a host loses an OS drive (common at our scale), we run ansible playbooks against a freshly imaged machine that detects the scenario and imports the zpool. I'd like to automate the remainder of the process so that we can issue an API command to automatically run the lxd recover from an ansible playbook. The input parameters for the recovery process are the same every time, as the zfs pools and storage pools are all deployed the same.
Example... the json will never deviate from this in our recovery process:
{ "pools": [ { "config": { "source": "<name>", "zfs.pool_name": "<name>" }, "description": "", "name": "<name>", "driver": "zfs" } ] }
If you have a better suggestion for recovering pools in an automated fashion, or if you can provide pointers for hitting the /internal API as a workaround/temporary alternative, I'm open to it!

You can hit the /internal/recover API for this if you really need to, but it's an internal API so subject to change.
We're not likely to be adding this kind of feature to the stable user facing API any time soon though.


Eigenflow hangs if error is thrown during EigenflowBootstrap initialization

Motivation
If an error is thrown during eigenflow initialization the actor system doesn't get shutdown properly and the entire application remains stuck. No error is logged to the main job log, but a stracktrace can be found in the stderr log (see https://issues.ypg.com/browse/MPN-2889).
This causes several problems:

The job does not restart automatically as scheduled the next day. So manual intervention is required to get the job running again.
Because the failure happens so early no useful information is logged in the main job logs. We have to dig around to find the stderr logs to see the stacktrace.
Also because the failure happens so early, no notifications are generated.

Input
Error thrown during EigenflowBootstrap initialization for example, see stacktrace in MPN-2889
Output
Application shuts down.
Test
Throw an error during EigenflowBootstrap initialization.
Check ps to verify that application should no longer be running.

Fixed in eigenflow v 0.3.2


fix: prevent scientific notation in large balances

Resolves #613
This prevents large balances from being returned in scientific notation.
An example Safe on the Transaction Service should no longer return the fiatTotal or individual fiatBalance/fiatConversion with exponents, but the full number as a string: /v1/chains/137/safes/0x828d55AaF0fE916879C7dCf0E3278D1E8dbEDDd3/balances/usd.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.05%) to 92.499%

Totals

Change from base Build<PHONE_NUMBER>:
0.05%

Covered Lines:
4356

Relevant Lines:
4609

💛  - Coveralls


Improved website to Responsive

What is the change?
All hard code is changed into responsive code.
Related issue?
issue: #177
How was it tested?
I have tested it in my local system.
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelines while contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Have you made corresponding changes to the documentation?
[x] Your submission doesn't break any existing feature.
[x] Have you tested the code before submission?

Screenshots or Video:
https://user-images.githubusercontent.com/59636849/108155011-13260a00-7104-11eb-88a1-3a8765fbab68.mp4

@pankajkumarbij still working on this or can I close this PR?

@pankajkumarbij still working on this or can I close this PR?

I will do required changes by end of the today.
Actually I was busy in collage exams.

I have close this PR and Make a new updated PR.


Webview Service Worker Error in registration due to invalid document state

I cannot open a single Jupyter notebook and some extensions stopped working

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.
Happy Coding!

The solution was to remove Cache
rm -rf ~/.config/Code/Cache


upstream

Changes
API changes

Type changes that you did here (ignore if you didn't do any changes related to this category)

Types/JSDoc changes

Type changes that you did here (ignore if you didn't do any changes related to this category)

Behavior changes

Type changes that you did here (ignore if you didn't do any changes related to this category)

Other changes

Type changes that you did here (ignore if you didn't do any changes related to this category)

u should merge this


Ridiculous request

I know this is a bit small, but can you make parrots dance when around a radio just like they do when nearby a jukebox?
Thanks in advance!

sadly cant be done at the moment as minecraft checks if its a jukebox block.
leaving this as note for a forge PR
1. make the actual tag json
2. in Forge's Tags.Block class, add a field for the tag similar to all the other ones there
3. at the vanilla code site, replace the check with net.minecraftforge.<dontremember>.Tags.Block.PARTY_BLOCKS.contains(block)
``` thanks to williewillus :)

Oh sad. Thanks for the reply anyway!