templates not working on actions

Checklist:

[x] I updated to the latest version available
[x] I cleared the cache of my browser

Release with the issue:
3.8.1
Last working release (if known):
Browser and Operating System:
Windows - Chrome
Android - Native App
Description of problem:
Templates seem to be working fine when changing styles etc. but they don't work when defining actions.
in the example below "spotify" works fine, but both "plex" and "youtube" generate a "none" action.
Javascript errors shown in the web inspector (if applicable):
when clicking the button the value of "d.action" is "none":
                    if (d && this.handleConfirmation(d))
                        try {
                            switch (d.action) {

Your Full Remote Config
type: custom:android-tv-card
rows:
  - - plex
    - youtube
    - spotify
custom_actions:
  myselectsource:
    tap_action:
      action: call-service
      service: media_player.select_source
      target:
        entity_id: media_player.roku_ultra
  myselectsource2:
    service: media_player.select_source
    service_data:
      entity_id: media_player.roku_ultra
  plex:
    style:
      color: orange
    template: myselectsource
    tap_action:
      data:
        source: Plex - Free Movies & TV
  youtube:
    style:
      color: red
    template: myselectsource2
    service_data:
      source: YouTube
  spotify:
    style:
      color: green
    service: media_player.select_source
    service_data:
      entity_id: media_player.roku_ultra
      source: Spotify Music

Additional information:

that worked, thank you for the quick response!

Fixed in 3.8.2.


Change wording on ADOT Section

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #369 (67b880a) into master (2f467e5) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #369   +/-   ##
=========================================
  Coverage     58.41%   58.41%
  Complexity     1229     1229
=========================================
  Files           133      133
  Lines          5011     5011
  Branches        589      589
=========================================
  Hits           2927     2927
  Misses         1814     1814
  Partials        270      270

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

@atshaw43 @carolabadeer PTAL


HttpTrigger & Logging samples

@cecilphillip,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:warning: Validation status: warnings

File
Status
Preview URL
Details

sandbox/snippets/101functions/logging/logging-ilogger.md
:warning:Warning
View
Details

sandbox/snippets/101functions/logging/logging-tracewriter.md
:warning:Warning
View
Details

sandbox/snippets/101functions/logging/using-third-party-logger.md
:warning:Warning
View
Details

sandbox/snippets/101functions/etc/accessing-settings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/accessing-querystrings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/accessing-request-body.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/restricting-http-verbs.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/security-keys.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/logging-ilogger.md

[Warning] Failed to find Git account for the committer<EMAIL_ADDRESS>Solution: 1) File creator to associate email address<EMAIL_ADDRESS>with his or her Git account, or 2) Anyone to explicitly add "author: <Git account>" into markdown YAML header.

sandbox/snippets/101functions/logging/logging-tracewriter.md

[Warning] Failed to find Git account for the committer<EMAIL_ADDRESS>Solution: 1) File creator to associate email address<EMAIL_ADDRESS>with his or her Git account, or 2) Anyone to explicitly add "author: <Git account>" into markdown YAML header.

sandbox/snippets/101functions/logging/using-third-party-logger.md

[Warning] Failed to find Git account for the committer<EMAIL_ADDRESS>Solution: 1) File creator to associate email address<EMAIL_ADDRESS>with his or her Git account, or 2) Anyone to explicitly add "author: <Git account>" into markdown YAML header.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

sandbox/snippets/101functions/logging/logging-ilogger.md
:warning:Warning
View
Details

sandbox/snippets/101functions/logging/logging-tracewriter.md
:warning:Warning
View
Details

sandbox/snippets/101functions/logging/using-third-party-logger.md
:warning:Warning
View
Details

sandbox/snippets/101functions/etc/accessing-settings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/accessing-querystrings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/accessing-request-body.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/restricting-http-verbs.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/security-keys.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/logging-ilogger.md

[Warning] Failed to find Git account for the committer<EMAIL_ADDRESS>Solution: 1) File creator to associate email address<EMAIL_ADDRESS>with his or her Git account, or 2) Anyone to explicitly add "author: <Git account>" into markdown YAML header.

sandbox/snippets/101functions/logging/logging-tracewriter.md

[Warning] Failed to find Git account for the committer<EMAIL_ADDRESS>Solution: 1) File creator to associate email address<EMAIL_ADDRESS>with his or her Git account, or 2) Anyone to explicitly add "author: <Git account>" into markdown YAML header.

sandbox/snippets/101functions/logging/using-third-party-logger.md

[Warning] Failed to find Git account for the committer<EMAIL_ADDRESS>Solution: 1) File creator to associate email address<EMAIL_ADDRESS>with his or her Git account, or 2) Anyone to explicitly add "author: <Git account>" into markdown YAML header.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sandbox/snippets/101functions/etc/accessing-settings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/accessing-querystrings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/accessing-request-body.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/restricting-http-verbs.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/security-keys.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/logging-ilogger.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/logging-tracewriter.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/using-third-party-logger.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sandbox/snippets/101functions/etc/accessing-settings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/accessing-querystrings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/accessing-request-body.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/restricting-http-verbs.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/httpTriggers/security-keys.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/logging-ilogger.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/logging-tracewriter.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/using-third-party-logger.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sandbox/snippets/101functions/etc/accessing-settings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/http-triggers/accessing-querystrings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/http-triggers/accessing-request-body.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/http-triggers/restricting-http-verbs.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/http-triggers/security-keys.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/logging-ilogger.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/logging-tracewriter.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/using-third-party-logger.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sandbox/snippets/101functions/etc/accessing-settings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/http-triggers/accessing-querystrings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/http-triggers/accessing-request-body.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/http-triggers/restricting-http-verbs.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/http-triggers/security-keys.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/logging-ilogger.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/logging-tracewriter.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/using-third-party-logger.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/table-storage/azure-table-storage.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/table-storage/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

sandbox/snippets/101functions/etc/accessing-settings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/http-triggers/accessing-querystrings.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/http-triggers/accessing-request-body.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/http-triggers/index.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/http-triggers/restricting-http-verbs.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/http-triggers/security-keys.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/index.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/logging-ilogger.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/logging-tracewriter.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/logging/using-third-party-logger.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/table-storage/azure-table-storage.md
:white_check_mark:Succeeded
View

sandbox/snippets/101functions/table-storage/index.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


saving and opening a drawing

Hi,
I am not sure is this is a bug or not, but when I save a drawing, I cannot open it with the default image viewer of windows (Windows 10). However  I can open it with MS paint and others. Therefore I wonder if there is something wrong with the generated image.
I get the image using the toimage() method and then I use python to save the generated image as:
with open("imageToSave2.png", "wb") as f:
    f.write(image_string[22:].decode('base64'))

I have followed this method to save the images generated by other JS drawing libraries, and I can open them with the windows image viewer.

hey, so the toImage method simply wraps the toDataURL method of the canvas. Not to say that this is not a valid issue, but I wonder if this has something to do with the browser implementation of the canvas method.

I see, the other library that I tested is https://github.com/Leimi/drawingboard.js. For some reason theirs seem to work with the windows image viewer, but it seems they are just also wrapping toDataURL.


javax.ws.rs-api 2.1.1

Type: Missing
Summary:
javax.ws.rs-api 2.1.1
Details:
Maven license field and links indicate EPL-2.0
POM indicates EPL-2.0
Resolution:
EPL-2.0
Affected definitions:

javax.ws.rs-api 2.1.1

@LandOfBliss This component is dual-licensed. See POM file:
SPDX-License-Identifier: EPL-2.0 OR GPL-2.0 WITH Classpath-exception-2.0
I think we would Declare as "EPL-2.0 OR GPL-2.0-only WITH Classpath-exception-2.0". @ariel11 Do you agree?

@AE49 I agree.


Optimize TupleHashTable for aggregates

fixes https://github.com/uwescience/myria/issues/876

Coverage decreased (-0.05%) to 26.862% when pulling 6886abdfcd7dee946a32cd824a19f0999b3dbc37 on optimize_aggregates into 60ad02e34545dfe619576212414ce241c2dfeff4 on master.

Coverage increased (+0.01%) to 26.921% when pulling cbf7747e391dbfb56cecddb887a2a1b61e8c2f77 on optimize_aggregates into 60ad02e34545dfe619576212414ce241c2dfeff4 on master.

As I mentioned in comments, I agree that it might be useful to reuse the implementation for grouping keys with multiple result entries (although the current implementation does assume unique grouping keys and would need to be changed accordingly), but I think the interface should explicitly reflect the assumptions made about uniqueness of grouping keys (i.e., getIndex() vs. getIndices()). If we decide to reuse this implementation for cases in which uniqueness of grouping keys is not guaranteed (like joins in the absence of functional dependency information), we should change the interface accordingly.

What do you think about a version of DupElim which uses 128-bit hash codes (so no collisions are expected until the number of tuples approaches 2^64, which will never happen)? That should save a lot of space since no results ever need to be retained!

Coverage increased (+0.004%) to 26.914% when pulling 09256cdda33b2416caf50774fc666d8781500b70 on optimize_aggregates into 60ad02e34545dfe619576212414ce241c2dfeff4 on master.

I think 64-bit is large enough since 2^32 is ~4G and 4G*(8+4)bytes = 48G already. Also even if it's 128-bit I guess we still need the logic for handling collisions.
I like the idea of making it simple, UniqueTupleHashTable is good.

Coverage increased (+0.04%) to 26.937% when pulling a05586a40e35237dc1a4d145b535eb39beb5e2d4 on optimize_aggregates into 5b992a04ef11093ffa1c26137fc578c2baad9f55 on master.

Actually my point was that with 128-bit hash values, we don't need logic for handling collisions, if we can trust our hash function (and we can always use a cryptographic hash function if we don't trust a heuristic hash function like MurmurHash). Using the approximation p = n^2/2m (where n = number of items and m = number of bins), which works well when p << 0.5, we can conclude that the chance of a collision with say n = 2^40 (a trillion items) is about 2^-72, which is completely negligible. Any content-addressable storage system (e.g. git) makes the assumption that random collisions are statistically impossible, as do many cryptography schemes (like digital signatures).
64-bit hashes are inadequate for realistic data sizes since by the above formula, even for say 128M items (2^27) the probability of a collision is about 2^-11, which is far from negligible.

Agree with @senderista -- if the crypto folks don't have to worry about collisions at this size, we don't either. Assuming that Murmur is approximately cryptographically secure, which I think it is.

I don't think Murmur is cryptographically secure in the rigorous sense, but it has been empirically shown to have excellent distribution properties, which is probably enough for our purposes. If we're paranoid enough about collisions to use a real crypto hash function, MD5 should be sufficient, or SipHash if we care about performance.

My concern of using 128-bit is memory consumption. It's 64 bits more per key comparing to 64-bit, and let's say the chance of a collision is 1/10. The cost of each collision is the size of the Java array that stores indices, let's say it takes 50 bytes. Then 64-bit still uses less memory than 128-bit. (Note that we can't avoid storing tuples even for 128-bit because it's a hash table for keeping states.)


Launch program with elevated privileges from non-elevated VS Code

I have a program that needs to run elevated. Currently, the only possible way to do this it to run VS Code itself elevated. This has some unfortunate side effects like not being able to drag and drop files onto the editor to open them any more.
Using compile settings to change UAC Execution Level highestAvailable or requireAdministrator both fail with Unknown Error: 0x800702e4. (In the case of highestAvailable this seems like a bug.) The same error occurs when setting the exe Compatibility properties to Run this program as an administrator.
Can we get an option to request elevation on a launch task without required VS Code itself to be elevated? This appears to possible on Windows.

What type of program do you want to launch elevated?
What debugger are you using?

C++ executable and cpptools vs debbugger, though I'd assume this applies to any executable on Windows and any debugger.

VS Code has no builtin support for elevation. Please file this request against the C++ extension.


BQ Quests not advancing on their own

The Quests in the BetterQuesting book do not progress on their own, each step that has a detection piece needs to have the detect/submit button in the quest book pressed.
Not a huge issue for most quests as you can click the button to move things along, but it breaks all the hidden quests.  Only after clicking on the detect/submit button in creative mode does the quest auto-complete.
EG :  Launching a new game world and starting from the initial spawn location, moving to the map location for the "Welcome to Middle Earth" quest.  Opening the quest book and looking at the quest it shows as undiscovered in the quest book.  This does not change until clicking on the detect button.  After which the location goes to found, and roughly 1 second later the quest auto-completes ( claim button grey's out ).
Base information

Minecraft version: 1.10.2
Minecraft Forge version: <IP_ADDRESS>1
TolkienCraft II version: 0.10.1

java version :  1.8.0_121"
running on Linux MultiMC

Talk to the NPC in rivendell (the record keeper) book is in edit mode and he has an option to turn it off

Spoke with Darage the record keeper, the option to reload BQ Quests did
not have any affect, there were a couple placeholder items in his
dialogs that may have been the option you were speaking of.
I did find the command to switch edit mode off from the betterquesting
wiki and once getting the quest book out of edit mode { /bq_admin edit
}  It did indeed correct the quest issues and they progress as
expected.
On Thu, 2017-05-11 at 12:42 -0700, GreatOrator wrote:

Talk to the NPC in rivendell (the record keeper) book is in edit mode
and he has an option to turn it off

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c5
5493e4bb","name":"GitHub"},"entity":{"external_key":"github/GreatOrat
or/TolkienCraft-3-Map","title":"GreatOrator/TolkienCraft-3-
Map","subtitle":"GitHub repository","main_image_url":"https://cloud.g
ithubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-
7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent
.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-
b52498112777.png","action":{"name":"Open in
GitHub","url":"https://github.com/GreatOrator/TolkienCraft-3-
Map"}},"updates":{"snippets":[{"icon":"PERSON","message":"@GreatOrato
r in #16: Talk to the NPC in rivendell (the record keeper) book is in
edit mode and he has an option to turn it
off\r\n"}],"action":{"name":"View
Issue","url":"https://github.com/GreatOrator/TolkienCraft-3-
Map/issues/16#issuecomment-300896182"}}}


feat(theme): use the config from Material Kit for the theme of Material UI

Currently, there is a mix in the configuration of the Material UI theme. We use a part of the configuration from Material Kit and a part of the old CSS configuration from the old theme.
To avoid to have to fix it at each new integration of component from Material Kit or Material UI, I do the following actions:

Removed the configuration of the old theme in the Material UI theme,
Uses the theme configuration from Material Kit for the existing configuration of Material UI.

ℹ Based on our team's decision, we no longer require approval of the refactoring pull request. Instead, we will review and approve the refactoring once all changes related to a specific component have been completed.

BeforeNow


gh-2180 Skipping making graph from cache on exception.

Codecov Report

Merging #2181 into develop will increase coverage by 1.45%.
The diff coverage is n/a.

@@              Coverage Diff              @@
##             develop    #2181      +/-   ##
=============================================
+ Coverage      63.72%   65.18%   +1.45%
- Complexity      2401     2402       +1
=============================================
  Files            781      853      +72
  Lines          25533    28813    +3280
  Branches        3062     3579     +517
=============================================
+ Hits           16272    18782    +2510
- Misses          7938     8509     +571
- Partials        1323     1522     +199

Impacted Files
Coverage Δ
Complexity Δ

...chq/gaffer/parquetstore/query/ParquetEdgeSeed.java
64.28% <0%> (ø)
0% <0%> (?)

...ion/handler/utilities/ParquetElementRetriever.java
69.73% <0%> (ø)
0% <0%> (?)

...serialisation/impl/TypeValueParquetSerialiser.java
37.5% <0%> (ø)
0% <0%> (?)

...on/handler/utilities/RetrieveElementsFromFile.java
74.35% <0%> (ø)
0% <0%> (?)

...ration/handler/utilities/AggregateAndSortData.java
100% <0%> (ø)
0% <0%> (?)

.../gaffer/parquetstore/partitioner/PartitionKey.java
83.33% <0%> (ø)
0% <0%> (?)

...parquetstore/utils/GafferGroupObjectConverter.java
82.19% <0%> (ø)
0% <0%> (?)

...chq/gaffer/parquetstore/SingleUseParquetStore.java
100% <0%> (ø)
0% <0%> (?)

...q/gaffer/parquetstore/io/writer/ElementWriter.java
79.61% <0%> (ø)
0% <0%> (?)

...titioner/serialisation/PartitionKeySerialiser.java
84.26% <0%> (ø)
0% <0%> (?)

... and 63 more

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 cf55440...6e4d86d. Read the comment docs.


implement skip_notification for sharing Google Cloud Print printer

Currently, if I share a Google Cloud Printer (gam printer id add USER ...) they do not receive a notification that the printer was shared with them.
This is controlled by the skip_notification field as described in the JSON for GCP /share at https://developers.google.com/cloud-print/docs/shareApi#share.
Please implement at your convenience. :)

It looks like doPrinterAddACL has the field defined with a default of True.
The field just needs to be added as an optional arg.

chaplina,
As you have the source, the following gets you what you want.
def doPrinterAddACL():
  cp = buildGAPIObject(u'cloudprint')
  printer = sys.argv[2]
  role = sys.argv[4].upper()
  scope = sys.argv[5]
  notify = True if len(sys.argv) > 6 and sys.argv[6].lower() == u'notify' else False
  public = None
  skip_notification = True
  if scope.lower() == u'public':
    public = True
    scope = None
    role = None
    skip_notification = None
  elif scope.find(u'@') == -1:
    scope = u'/hd/domain/%s' % scope
  else:
    skip_notification = not notify
  result = callGAPI(cp.printers(), u'share', printerid=printer, role=role, scope=scope, public=public, skip_notification=skip_notification)
  checkCloudPrintResult(result)
  who = scope
  if who is None:
    who = u'public'
    role = u'user'
  print u'Added %s %s' % (role, who)

Ross

this is in 4.31


CNP0000325, GSE134355: Construction of a human cell landscape at single-cell level (HCA Publication)

Primary Wrangler:
Ami
Secondary Wrangler:

Associated files:
Google Drive: https://docs.google.com/spreadsheets/d/1PEpUcm0C8xWTKv_DIrXhwPluuxC6KjuW/edit#gid=37156403
Published study links
Paper: https://www.nature.com/articles/s41586-020-2157-4#data-availability
Accessioned data:  https://www.ncbi.nlm.nih.gov/geo/query/acc.cgi?acc=GSE134355
https://db.cngb.org/search/project/CNP0000325/
Key Events

[x] convert published metadata to HCA spreadsheet
[x] manually curate dataset to meet HCA metadata standard
[ ] Upload sheet to validate metadata
[ ] Check linking using ingest graph validator
[ ] Transfer files to ingest to validate data files
[ ] Ask the Secondary Wrangler for an end-to-end review of the project. Ask the Expertise Wrangler to review specific tabs if needed
[ ] Submit dataset to Production

This is a UCSC dataset so I am closing this ticket.

This is a UCSC dataset so I am closing this ticket.

@ami-day It would be good to know more about why UCSC decided to leave it, what were the issues they found? We should record this reason in the data tracker so we can report if required

@ami-day It would be good to know more about why UCSC decided to leave it, what were the issues they found? We should record this reason in the data tracker so we can report if required

Hi @lauraclarke I'm not sure that they did decide to leave it? It looks like a pretty good dataset. There were no issues found. Microwell technology was used which cannot be processed by pipelines but we can still curate the metadata.

Hi @lauraclarke I'm not sure that they did decide to leave it? It looks like a pretty good dataset. There were no issues found. Microwell technology was used which cannot be processed by pipelines but we can still curate the metadata.

@ami-day did you ever follow up on this?

Need to follow up on details with UCSC on this

Followed up with UCSC, they identified it as not adequate quality due to raw data. Agreed I would look into the data, see if we find any problems, and if not, will curate it on our side.

I don't see an issue currently with this dataset, and in the publication they state it is an HCA paper and that the PI is part of the HCA project, so I've started curating it

The author got back and I have asked them additional questions, so I am waiting to hear back again. The new ontology term request is in progress.

The new ontology term for Microwell-Seq as a scRNA-Seq library construction method in HCAO is expected to be available from Tuesday 18th May

Waiting to hear back from author - they sent me an email but forgot to attach the mentioned files.

-Waiting to hear back again this time about technology barcode specifics.
-Error downloading fastq from ENA even though they are available. Discussing with Eugene in ENA team.

the data is transferring a to hca-util area

To ask:

what is the model organ for iPSC differentiation
cord and blood samples: clarify from which samples CD34+ cells were enriched

@ami-day quick question, I know on slack we were talking about urine as the source of cells, that isn't the model organ though, that is the organ the cells came from (I guess bladder in that case), where they differentiated? in which case what into as that is the model organ?

I have cleared the milestone as we are waiting to hear back about some required metadata to be able to move forward.

@ami-day quick question, I know on slack we were talking about urine as the source of cells, that isn't the model organ though, that is the organ the cells came from (I guess bladder in that case), where they differentiated? in which case what into as that is the model organ?

Hi @lauraclarke I already put the model organ as pancreas for iPSCs or Embryoid Body for the hESCs. The organ I entered in the "specimen from organism" tab is uterus (iPSC) and embryo (hESC) as this is from where they were derived, and so the specimen_from_organism in this case is linked to the cell lines in the cell line tab as the specimen id.

Barcode information from authors:

Microwell-Seq is a 3' end tag/bias method.

Cell barcode in Microwell-Seq bead is 18bp(3X6bp).

UMI barcode in Microwell-Seq bead is 6bp.

Cell barcode offset in Microwell-Seq sequencing read1

BASE_RANGE=1-6:22-27:43-48

UMI offset in Microwell-Seq sequencing read1

BASE_RANGE=49-54

The cell barcode and umi barcode are on read1, they are on the same read

bead-conjugated oligo:
5-TTTAGGGATAACAGGGTAATAAGCAGTGGTATCAACGCAGAGTACGT[6bp cell barcode part1]CGACTCACTACAGGG[6bp cell barcode part2]TCGGTGACACGATCG[6bp cell barcode part3] [6bp UMI] (T)30VN-3’

Now I have asked them about the model organ and which are the CD34+ enriched samples. They are probably starting to think I am very annoying...

Other answers:

We cultured the Embryoid Body for random, it didn't have any specific target organs. Besides, EB9, EB18 and EB20 are embryoid body derived from hiPSCs instead of hESC.
In the method, it states" CD34 + cord blood and CD34 + mPB were enriched using a human CD34 selection kit (StemCell Technologies)." We just enrich CD34+ for umbilical cord blood in two batches:Cord Blood1 (CD34+) and Cord Blood1 (CD34+). And CD34+ mPB is just for CD34 + mobilized peripheral blood and the data is from another paper in our lab: “Comparative transcriptomic analysis of hematopoietic system between human and mouse by Microwell-seq”. No fluorescence-activated cell sorting (FACS) step was used in other HCL experiments.

Updated the metadata based on the author's response. However I need to update the HCA metadata schema to allow for multiple barcode offset ranges to reflect the above oligo structure.

Blocked as waiting to be able to make additional metadata schema updates. I need to be able to change the allowed barcode length and offset format.

The latest library_preparation_protocol schema is here: https://schema.humancellatlas.org/module/process/sequencing/5.2.6/barcode The umi and cell barcode offset and length value types have not yet been updated to enable a range in values.

I have added details in Ingest, and Ami had already linked the ticket. So closing this ticket for now


How to build latest version?

Hi,
Latest release is over a year old but i see code has been updated since then. How do I build the latest version pls?

Hi, @xT4Z1N4TRx,
You can download the code with latest changes, and then load the plugin by following steps:

Enable developer mode in chrome
Click on "load unpacked extension" button
Navigate and select the unzipped folder of extension(which contains manifest file)

If you face any problem, you can comment here and I'll try to resolve it, closing the issue


feat(transformer): support exponentiation operator plugin

The implementation copy from the original implementation which removed in https://github.com/oxc-project/oxc/pull/2865.

#4876  👈
main

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

Join @Dunqing and the rest of your teammates on  Graphite

As discussed earlier, I wasn't planning to review these new transform PRs at this stage. I proposed that we merge them and then I do a second pass to review/tidy them later on. I only looked into this one because it informed #4880.

As discussed earlier, I wasn't planning to review these new transform PRs at this stage. I proposed that we merge them and then I do a second pass to review/tidy them later on. I only looked into this one because it informed #4880.

Let's merge all this stack of PRs first. We can make many improvements later

As discussed earlier, I wasn't planning to review these new transform PRs at this stage. I proposed that we merge them and then I do a second pass to review/tidy them later on. I only looked into this one because it informed #4880.

Thank you for your review, Let's merge all this stack of PRs first. We can make many improvements later


Driver License scanning - Barcode scanning for PDF417 is no longer working for some states

Hi,
We are using Google Mobile vision library in our app to scan PDF417 scanning for driver licenses. It used to work for most of the states which are adhere to AAMVA standard. Even if the parser failed to decode to non-compliant with AAMVA standard we used to see that scanning was working fine. However recently we received issues from production app saying some the states licenses scanning stops working.
When I verified my NJ licenses it used to work, however one of my colleagues NJ licenses was not scanning using neither our app nor the visionSamples for barcode scanning. Also we got the image for LA state license which is also failed to scan as well. I will send the licenses as PM upon request as this real DL and I do not want attach it on public forum.
My question, are you aware of any issue on barcode scanning lately? I could able to provide some real licenses to repro the issue on your end upon request. Let me know if you need more details or have any questions.

The PDF417 reader and the AAMVA parser have not changed in any way since the Play Services 10.0 release (November 2016). If you are only seeing a regression now, then it's probably not related to the Barcode API.

@pchx Thanks for the response. The issue I am facing is different. Looks like NJ state license barcode type is changed (There is a visible difference in rendered barcode). I used the Google Vision sample app and camera is not able to detect the barcode itself. If needed I could send you the DL license in a private message, otherwise let me know what sort of logs you want to debug the issue from your end.

@pchx I have attached the LA license which is not scanning. The behavior is same for NJ license as well. Please let me know if you have any questions.

I will take a look, but in the meantime I strongly suggest that you remove that image since it is readable (by means other than our Barcode API) and appears to contain some personal information. Sorry, I couldn't find any means to directly contact you.

The example you provided a valid PDF417 barcode, but you can see gaps in what should be solid black regions in the upper half of the code. This seems to be enough damage that our reader can't decode the image.

@pchx I see this might be the reason for the reader fail to decode image for NJ state license as well. One of my colleague recently renewed his NJ state license and scanning stopped working with the new one. Old one is still working though. I have the scan copy of the DL if needed I could send you that as well. I can be reached at<EMAIL_ADDRESS>I could share the DL directly to you. Are you saying the generated barcode for these non working states is wrong?

They're (probably) perfectly valid barcodes, but when printed at low quality it can be hard to read them except under perfect conditions.

@pchx I understand that image quality might be the reason, however I used the real NJ license and the scanning was not working. We have actually received the issue from production as some of the state licenses were not scanning. Do you aware of any decoding issue with some of the states?

Like I said, my guess (without seeing these licenses) is that they're perfectly valid barcodes that were printed at low quality by the state DMV or otherwise damaged. The PDF417 reader in our Barcode API does not handle these well.

@pchx I understand that the quality of image might be the reason why the decoder fails to process the image. I have attached the video from my QA engineer who used his latest NJ license to scan using the Barcode API sample app from Github. He used both his latest license and his old expired license. It is evident that the old license was working and the newly issued one is not. I am not sure what might be causing the scanning failure and need your help to look into the issue.

It's hard to tell from the video, but that card does not appear to have a valid PDF417 stop pattern on its right side.

@pchx I see your point. This looks more like an error in printing the barcode. If possible could you let me know what circumstances could make the image decoding to fail?

Invalid PDF417 barcode pattern
Poor resolution
Anything else?
Also even if the image decode works fine the parser might fail if the decoded string do not follow the AAMVA standard. Am I Correct?

Right.

I got the same issue, I'm using the same plugin "phonegap-plugin-barcodescanner": "^7.0.3", for iOS and android platform, but it doesn't work for android when I'm trying to scan my Florida Driver License, however for iOS it works.

@kkamaraj  This issue is fixed or you got any solution?

I am no longer looking into this issue.
On Tue, May 21, 2019 at 2:22 AM nagendra789<EMAIL_ADDRESS>wrote:

@kkamaraj https://github.com/kkamaraj This issue is fixed or you got
any solution?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/googlesamples/android-vision/issues/231?email_source=notifications&email_token=AB4PLUAIJZ2RO46LHEMJAT3PWOII5A5CNFSM4DNR3362YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV236BA#issuecomment-494255876,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB4PLUC4HS56VE4OXTUNNODPWOII5ANCNFSM4DNR336Q
.


Help PHP :)

Hi there,
I may be missing a thing. I just dont't get how to launch a an example script? I have everything properly installed: Wamp server, Composer, downloaded the project files. When I run in cmd php path/example_file.php I have an error saying it's impossible to find some files from the require line. It shows a messy path string with / and at some point \ between folders names.
Well. How does the script work? How do you launch it? Thanks for some help :)

Hi, @ymongo
Try to use
require __DIR__ . '/../vendor/autoload.php';
instead of
require __DIR__ . '/vendor/autoload.php';


raftstore: tiny tuning

broadcast heartbeat more frequently to make the cluster more stable
set a smaller tick interval to make raft base tick more accurate
add some logs

@siddontang @hhkbp2 @ngaut PTAL

what's the heartbeat network pressure for 3w+ regions with 500ms interval?

I reset the heartbeat frequency, the accurate base tick should make the cluster stable enough.

Rest LGTM

@siddontang @hhkbp2 PTAL

LGTM
PTAL @hhkbp2

LGTM

LGTM


File Menu opening a new file (Like Ctrl + N) instead of expanding the Menu

VSCode Version: 1.28.2 (user setup)
OS Version: Windows 10

Steps to Reproduce:

Open Code
Click on "File" Menu
Expected - Expand File Menu
Actual - Open a new untitled file

Does this issue occur when all extensions are disabled?: YES

@bhosale-ajay when you click on the file menu, do you see any animation of the menu appearing at all?

No, On further observation, this happens with screen zoomed (+4) and when double clicked on File.

@bhosale-ajay even under these circumstances I do not see the behavior you describe. Would you be able to provide a gif of your whole window while reproing the behavior?

Please check

@bhosale-ajay can you verify with the latest version of VS Code?

Verified, and looks like it is fixed


Crash on load-chat: attempt to index global 'bit32' (a nil value)

Hello and thank you for this awesome project. However, on my system, upon attempting to load-chat, the script crashes with the following error:
[mpv_youtube_chat]
[mpv_youtube_chat] stack traceback:
[mpv_youtube_chat]      /home/<name>/.config/mpv/scripts/mpv-youtube-chat/main.lua:330: in function 'load_live_chat'
[mpv_youtube_chat]      /home/<name>/.config/mpv/scripts/mpv-youtube-chat/main.lua:388: in function 'handler'
[mpv_youtube_chat]      mp.defaults:380: in function 'handler'
[mpv_youtube_chat]      mp.defaults:510: in function 'call_event_handlers'
[mpv_youtube_chat]      mp.defaults:552: in function 'dispatch_events'
[mpv_youtube_chat]      mp.defaults:503: in function <mp.defaults:502>
[mpv_youtube_chat]      [C]: at 0x5623556aa5e0
[mpv_youtube_chat]      [C]: at 0x5623556aaaa0
[mpv_youtube_chat] Lua error: /home/<name>/.config/mpv/scripts/mpv-youtube-chat/main.lua:242: attempt to index global 'bit32' (a nil value)

I have the following in input.conf and the error occurs when pressing ctrl+shift+c:
CTRL+Shift+c script-message load-chat
Alt+CTRL+Shift+c script-message unload-chat

mpv --version:
mpv 0.35.1-dirty Copyright © 2000-2023 mpv/MPlayer/mplayer2 projects
 built on Fri Apr 21 07:11:25 2023
FFmpeg library versions:
   libavutil       58.2.100
   libavcodec      60.3.100
   libavformat     60.3.100
   libswscale      7.1.100
   libavfilter     9.3.100
   libswresample   4.10.100
FFmpeg version: n6.0

Arch Linux, lua verison 5.4.6, latest git master of mpv-youtube-chat, other scripts installed are mpvacious and autosubsync-mpv.
Any ideas how to troubleshoot this problem?

The script was written with lua 5.2 in mind, which doesn't operators for bitwise operations like 5.4. I'm unsure if there's a simple way to support both, I don't really feel like looking into it right now but maybe I'll get to it soon, otherwise if somebody wants to PR a fix I can merge that.

Closed by #3


[ToolRunner] Enhanced 'shell' execution option

Enhancement for #637
Required to fix issue #12848.
Required for PR #13099
Applied enhancement for shell option to wrap a tool path and arguments with double quotes to ensure that command is handled correctly if it is executed inside shell. The path and arguments are wrapped only if shell property of IExecOptions object set to true.
Added tests.

@damccorm Thank you very much for the review! I've applied changes in accordance with your review points so could you please take a look?


With latest identity server I get 404 on authorize endpoint

[x] I read and understood how to enable logging

I am not sure what I am doing wrong (but obviously I am missing something). Everything works (in the Identity Server host and connected API), except for the authorize endpoint. Any assistance would be appreciated.
Issue / Steps to reproduce the problem
Startup.cs contains the following
services.AddIdentityServer(options =>
{
options.Events.RaiseSuccessEvents = true;
options.Events.RaiseFailureEvents = true;
options.Events.RaiseErrorEvents = true;
options.Endpoints.EnableAuthorizeEndpoint = true;
})
.AddDefaultEndpoints()
.AddRequiredPlatformServices()
.AddResourceStore()
.AddDeveloperSigningCredential()
.AddPersistedGrants()
.AddClientStore()
.AddAspNetIdentity();
Relevant parts of the log file
[06:55:28 Information] IdentityServer4.Hosting.IdentityServerMiddleware
Invoking IdentityServer endpoint: "IdentityServer4.Endpoints.AuthorizeEndpoint" for "/connect/authorize/login"
[06:55:28 Information] Microsoft.AspNetCore.Hosting.Internal.WebHost
Request finished in 27.7207ms 404

Just to make this 100% clear - this is using IdSrv 4 prerelease for .net core 2.

Not enough info.

Closing this issue. Bug was on my side. Once I had the Id Server code running on my machine where I could step through it, the issue was easy to spot and resolve.

hi @ashtonkj , what was the root cause? thanks!


replace github.com/lxc/lxd with github.com/canonical/lxd

The Go LXD import path has changed.  See

github.com/lxc/lxd has been renamed to github.com/canonical/lxd

Done.


Scala case class fields shuffling

Hi, I just created #224 to highlight a weird behavior when using scalapb encoders with "classic" scala case class.
Given a case class with two fields with same type (AddressLike(street: Option[String], city: Option[String])) I save a dataset using the first field (street) as the partitionning column.
Then when loading the dataset, spark create a dataframe with columns city and street.
Finally, when collecting this dataframe to an Array[AddressLike], the value of the field street is in the city field and vice-versa.
This seems to happen because the dataframe schema has the street field at the end (while it is the first field of the case class):
root
 |-- city: string (nullable = true)
 |-- street: string (nullable = true)

Providing the schema before calling .load does not modify this actual schema.
Finally, when deserializing to scala case class, mapping seems to be done by position instead of name, leading to city values mapped to the street field and vice-versa.
This index-based mapping can be problematic too, if you have a dataframe with "useless" columns and try to "cast" it to a case class with fewer fields.I will add a test to highlight this too.
Maybe this is more related to frameless encoder than scalapb ones. I can forward this issue there if required.

This seems to be a frameless issue.
I reproduce the errors on their repo: https://github.com/typelevel/frameless/compare/master...AlexisBRENON:case_class_support#diff-dd83f3b1d1a249804b5620473177ce6034efbc5f36b45a9b1ef01283cafd50f9R540
And it seems that others already report it: typelevel/frameless#411

I suggest to keep tracking it upstream. My understanding from the above is that it is not actionable by ScalaPB.


Castle event wiring facility and dynamic parameters throw EventWiringException

When trying to link an event with a handler using Castle.EventWiringFacility when the target service has a dynamic dependency, I get the EventWiringException with following description: Publisher tried to start subscriber 'xxx' that is waiting for a dependency.
I have traced the code down to the facility and I have found the assertion:
private static void AssertValidHandler(IHandler handler, string subscriberKey)
{
  if (handler == null)
	throw new EventWiringException("Publisher tried to start subscriber " + subscriberKey + " that was not found");
  if (handler.CurrentState == HandlerState.WaitingDependency)
	throw new EventWiringException("Publisher tried to start subscriber " + subscriberKey + " that is waiting for a dependency");
}

The problem is that the component with dynamic dependency is always in HandlerState.WaitingDependency state.
Is there a way how to tell the Castle that it should consider the dynamic dependency as Valid instead of WaitingDependency?
If not, I think that the state should be changed or may be the assertion in EventWiringFacility.AssertValidHandler could be skipped. If I skip the assertion in debugger, everything is working fine, i.e. the service gets resolved and the event gets fired and handled.
Using a factory method instead of dynamic parameter solves the issue but is not a convenient way how to fix the problem in my application.
Please find the code below to reproduce the behavior:
using System;
using Castle.Facilities.EventWiring;
using Castle.Facilities.Startable;
using Castle.MicroKernel.Registration;
using Castle.Windsor;

namespace SmallTests
{
	public interface IA
	{
		string DynDep { get; }
		void EventHandler(object sender, EventArgs args);
	}

	public class A : IA
	{
		private readonly string _dynDep;

		public A(string dynDep)
		{
			_dynDep = dynDep;
		}

		public string DynDep
		{
			get { return _dynDep; }
		}

		public void EventHandler(object sender, EventArgs args)
		{
			Console.WriteLine("Event Handled");
		}
	}

	public interface IB
	{
		event EventHandler MyEvent;
		void RaiseEvent();
	}

	public class B : IB
	{
		public event EventHandler MyEvent;

		public virtual void RaiseEvent()
		{
			var handler = MyEvent;
			if (handler != null) handler(this, EventArgs.Empty);
		}
	}

	public class CastleTest
	{
		public static void CastleDynamicDependency()
		{
			var c = new WindsorContainer();
			c.AddFacility<EventWiringFacility>();
			c.AddFacility<StartableFacility>(f => f.DeferredStart());

			c.Register(Component.For<IA>().ImplementedBy<A>()
				.DynamicParameters((kernel, parameters) => parameters["dynDep"] = DateTime.Now.ToShortTimeString())
				.Named("A"));

			//This works fine, but I cannot use it in my project
			//c.Register(Component.For<IA>()
			//    .UsingFactoryMethod(kernel => new A(DateTime.Now.ToShortTimeString()))
			//    .Named("A"));

			c.Register(Component.For<IB>().ImplementedBy<B>()
				.PublishEvent(x => x.MyEvent += null,
					y => y.To<IA>("A", s => s.EventHandler(null, null))));

			var r = c.Kernel.GetHandler("A");
			Console.WriteLine(r.CurrentState);

			var a = c.Resolve<IA>();
			Console.WriteLine(a.DynDep);

			var b = c.Resolve<IB>();
			b.RaiseEvent();

			Console.ReadLine();
		}
	}
}

I have also posted the question on stackowerflow.

Hi @pecanw
Event Wiring facility is no longer supported so I'd say it's quite unlikely this is going to be fixed unfortunately.
I know it's not ideal but I'd recommend migrating away from using EventWiringFacility if that's an option

Can you point me to another (supported) way to wire-up events and handlers in Windsor Castle?

Hi @pecanw  -- were you able to find another method to wire events?

We are using Castle.Facilities.EventWiring, Version=<IP_ADDRESS>, but we got rid of the dynamic dependencies.

The source code is still easily accessible, still Apache 2.0 licensed and isn't very big, so if you do want to continue using the facility it would be pretty trivial to copy the code into your own project. That way you could also make any needed changes.
https://github.com/castleproject-deprecated/Castle.Windsor.Facilities/tree/master/src/Castle.Facilities.EventWiring


RuntimeError: mat1 and mat2 shapes cannot be multiplied (2x1024 and 512x1024)

To reproduce run codes/models/clip/clvp.py

i want to test solo model by random inputs

Correct, the Tortoise CLVP model is text_voice_clip.


Scope list could be an enum

Hello, would be great if the available scopes came in the form of an enum, and also, if they were listed on the README file (I'll make a pull request with it soon).

All pr's welcomed
On 24 Jul 2017 9:44 p.m., "Junior Damacena"<EMAIL_ADDRESS>wrote:

Hello, would be great if the available scopes came in the form of an enum,
and also, if they were listed on the README file (I'll make a pull request
with it soon).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/geniushkg/github-oauth/issues/5, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFDjJcWb6Uv80jAIdLJfBxP5KWB38zS3ks5sRML2gaJpZM4OhaRz
.


Performance - Reject instanced geometry which is smaller than a specific screen-space threshold in shader

Spike inconclusive; culling smaller objects did not benefit the framerate


Add counters to measure append attempts during scrapes

Adds 2 new counters, aiming to monitor append success ratio during scrapes.
Fix #12585

@TheSpiritXIII, just to let you know that there was a brief discussion in slack and maybe a metric in scrape-manager might not be the best solution here...
cc @roidelapluie


Added linear gradients to the background

Description
Made the site's background more attractive. Fixed low contrast problem on the main theme.
Type of Change:
deleted unnecessary images that are no longer required because in place of them now it is gradient colors.

Code
Quality Assurance
User Interface

Screenshots
Screenshots of the proposed changes compared with the current version of the project.
main theme

dark theme

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests/screenshots(If any) that prove my fix is effective or that my feature works

you code has conflicts , please review the code.

Done!

you code has conflicts , please review the code.

Done!


Is there any way to sort by weight(score) for full text search fields?

Is your feature request related to a problem? Please describe.
As I know right now we have only .Sort() method which accept 2 arguments: field name and sort by ASC, DESC but it would be nice to have a method to sort by score(weight) for full text search fields. The query might be something like:
db.table.find({$text:{$search:"Test"}},{score:{$meta:"textScore"}}).sort({score:{$meta:"textScore"}})
Describe the solution you'd like
It would be nice to have a method like .sortByScore()

Is your feature request related to a problem? Please describe.
As I know right now we have only .Sort() method which accept 2 arguments: field name and sort by ASC, DESC but it would be nice to have a method to sort by score(weight) for full text search fields. The query might be something like:
db.table.find({$text:{$search:"Test"}},{score:{$meta:"textScore"}}).sort({score:{$meta:"textScore"}})
Describe the solution you'd like
It would be nice to have a method like .sortByScore()

In branch sort_feature_change I've changed Sort 2nd argument to type interface can you checkout on that branch and test the solution.
sortValue := bson.M{
		"$meta" : "textScore",
	}
aggPaginatedData, err := paginate.New(collection).Context(ctx).Limit(limit).Page(page).Sort("score", sortValue)...

I've tested it but still, I want to make sure the solution works for you then we can merge it on the main branch.

@gobeam Works Perfect now! Thank you so much for your quick turnaround. Great Library and implementation!

@gobeam Works Perfect now! Thank you so much for your quick turnaround. Great Library and implementation!

You're welcome. Happy to know you liked it. I'm closing this issue now.


@ash => Initial work on an ORM from Transition -> Show

Allows for a similar Network -> ORM chain that we have in Eidolon, I'm not massively sold on Gloss' Everything is Optional policy, but maybe its better that we understand what is actually option in the data.
All inlined ATM so I could iterate faster

Nice! Very idiomatically Swift 2 :100:


Docs: Healthcheck Endpoint

Description of the Change
Added small description of the endpoint to the configuration page
Issue
closes #1834

Benefits
more docs
Possible Drawbacks
none

Sara lost to Git. New PR is https://github.com/hyperledger/iroha/pull/1870


Make a CupertinoSearchBar

See https://developer.apple.com/design/human-interface-guidelines/search-fields
Android sister request #9783.
cc @sethladd

This is in our list of immediate next things to do

Looking forward to this!

@xster Any progress? Would you be potentially accepting PRs for this?

Sure, we'd be happy to take PRs for it.

Does CupertinoSearchBar exist in flutter release now?

Does CupertinoSearchBar exist in flutter release now?

Nope :(

Does this include the fact that it should work with the Cupertino (sliver) AppBar ? Like for example in the contacts app

is it possible to use this search bar atm? how? it was removed from "goals" what that means exactly? TIA

should we use cupertion_controllers package? will be this included into flutter sdk?

It seems like there is a Cupertino Search Bar in https://pub.dev/packages/native_widgets, but I literally cannot tell you how it works because it seems like it just doesn't...

@xster Will this get an updated milestone?

This is in our list of immediate next things to do

What's the status of this? Is there any point waiting around for it or should we opt for other solutions?

No 1 location as said
Sent from my iPhone

On 17 Sep 2020, at 23:23, Alex Meuer<EMAIL_ADDRESS>wrote:

This is in our list of immediate next things to do
What's the status of this? Is there any point waiting around for it or should we opt for other solutions?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Also looking forward to this. Any updates?

I've been tasked with taking care of this. I'll assume the earliest this will be available is in 1 month. @AlexMeuer
Just getting started haha. Will update you guys!

Fantastic. Let me know if you need/want any input.

Ok, progress update: Got something that looks kinda like the UISearchTextField
https://youtu.be/ZoTgPsaMu6U
Some UI necessities going forward:

[ ] Icons should increase/decrease with system font. Currently, this is not supported and I've only hard-coded the size of the search and x icons. Tracking here: https://github.com/flutter/flutter/issues/67792#issuecomment-707240962
[ ]  UIKit's UITextField has differing content insets for both placeholders/text and cursor position. This isn't necessary for the search control to work, but it should be dealt with. Tracking here: https://github.com/flutter/flutter/issues/67951 The default font is also slightly narrower than what's seen in Flutter. Tracking here: https://github.com/flutter/flutter/issues/67953
[ ] Add bookmark button option
[ ] Make a search bar and add the search field to it
[ ] Add a cancel button to the search field's trailing

Will keep you updated.

That comparison tool is sooooo useful :D
Solid!

Are you also working on a Sliver version of it?

CupertinoSearchTextField is now available for use.
This doesn't yet support a sliver version. Working on that part soon.

CupertinoSearchTextField is now available for use.
This doesn't yet support a sliver version. Working on that part soon.

It seems the link is broken.
I also tried going through the official documentation, but it also returns the default firebase page not found
An updated link would be appreciated.

@adeolaex Its in the Cupertino folder on GitHub.
https://github.com/flutter/flutter/blob/dev/packages/flutter/lib/src/cupertino/search_field.dart
Currently only in the dev channel/branch.  What is a channel in flutter?

@Alleckz Thanks for clarification.
For a second there, the link you provided was opening up the issues page of flutter.

@adeolaex No problems. Ye, missed copying the link in the actual url filed inside the brackets. Fixed it directly.

The api.flutter.dev site reflects the stable branch (where CupertinoSearchTextField isn't present on yet). See https://master-api.flutter.dev/flutter/cupertino/CupertinoSearchTextField-class.html for the doc on master/dev channels.

The recently added atomic header slivers can achieve the scrolling effect of the search bar in the settings app, so we might not need a brand new scrolling version of https://master-api.flutter.dev/flutter/cupertino/CupertinoSearchTextField-class.html.
There is some sample code that shows how to achieve the Settings app revealing search bar here:
https://github.com/flutter/flutter/blob/master/examples/api/lib/widgets/sliver/pinned_header_sliver.1.dart
CupertinoSearchTextField might just need an update, or a new widget could wrap it with the new slivers we have for the effect.
Updated HIG is in: https://developer.apple.com/design/human-interface-guidelines/search-fields
There is a SearchBar widget in the material library now, would be worth looking to see if/where there are opportunities to align the two (with either the existing cupertino one or a new one - which might also help us decide what to do here).

@Piinks should this issue be closed to focus on the sliver requirements in https://github.com/flutter/flutter/issues/18103? Looks like this should have been closed by https://github.com/flutter/flutter/pull/68074.


Disable starting an instance with default yaml if existing-instance f…

Hi. Today if we start a VM with limactl in a workflow with tty=false without specifing template or yaml, it will create a new instance with default yaml if we start an instance that doesn't exist. For example "limactl start newInstance --tty=false" will create a new instance with name "newInstance" from default.yaml file. We want to provide a way for users to start only existing instances without creating a new instance from default.yaml file unintentionlly. For backward capability, we added new flag --existing-instance to start command so that when user specifies the flag to be true, lima will throw an error instead of creating a new instance if the instance doesn't exist.

I'm not sure that this works well; if you forget to specify the new --existing-instance option (which is hard to type), then you will still create a new instance.
I would have preferred if we had separate create and start commands (with create auto-starting by default, and a --no-start option to prevent it), but that ship has sailed, as they say.
Assuming you are wrapping the start command with a script anyways, you could just add a check to the script to make sure the instance exists, e.g.
if [ -z "$(limactl ls -f '{{.Status}}' $INSTANCE 2>/dev/null)" ]; then
    echo Instance $INSTANCE does not exist
    exit 1
fi

@AkihiroSuda I wonder why limactl ls $INSTANCE just shows a warning and still has an exit code of 0 when the instance doesn't exist; that feels wrong to me. Should we change that?

Thanks for the feedback @jandubois. I'm using a cobra application to wrap the limactl command, is it possible to do something like the shell script you have mentioned in the cobra app?

I'm using a cobra application to wrap the limactl command, is it possible to do something like the shell script you have mentioned in the cobra app?

I'm not sure what "cobra app" means; to me cobra is just a Go library to parsing commandline arguments.
If this is a Go program, then yes, you can do this; either by running limactl ls as a subprocess, or just by checking if the directory $LIMA_HOME/$INSTANCE exists (defaults to $HOME/.lima/$INSTANCE when LIMA_HOME is not set).

I wonder why limactl ls $INSTANCE just shows a warning and still has an exit code of 0 when the instance doesn't exist; that feels wrong to me. Should we change that?

Yes


Strip trailing /index.html from seo_url

Fixes #2
This replace technique is the same as what is used by jekyll-sitemap
What happens if the post is actually just in a subdirectory called /index.html/? Every thing falls apart, I guess :egg:

LGTM. Thanks, once again, @pathawks! :turtle: :cactus: :hamster:

What happens if the post is actually just in a subdirectory called /index.html/? Every thing falls apart, I guess

Yeah. Don't do that. I'm fine calling that a crazy edge case not worth supporting.


Replace x-forwarded support with Airlift version

Replace manual handling of forwarded headers with request rewriting in Airlift

Maybe say "Jetty" instead


Possibility of annotating whole text data at once

Problem
Right now, there is a possibility of labeling the NER of a text data by uploading it. But it only works, when the "treat as TSV" is chosen. So, the problem arises, when i have  large text data, where i need to annotate everything at once, this is tedious, since some of the line will be empty, and there will be thousands of sentneces that requires annotation.
Solution
Possibility of annotating entire doumets at once like in docanno would be great.

Could you describe step by step what you are doing and what is wrong, because right now it's not clear.
You can import a big txt files as a whole task and label it, what is your concern?

I am trying to annotate like NER in many Text datas.
For this, i created a new project, and chose the Labelling as "NLP NER" template.

Then i imported the text file through "Data Import". Then, there is a choise of either choosing it as "List of tasks" or as "Time Series or Whole Text File"

Now, at first i chose the second part, "Whole Text File". Then, after chossing this, i see following : Only one file is there to be annotated, and the name of Text file is shown at the column text. But, i think there should be the content of the Text File.

Now, the problem is, when i try to annotate it, you can see that there is actually the name of the file as content to annotate, which i dont think should be the case.

.
And the second option, if i chose the List of tasks and save it, then i see that the tasks are broken it into multiple tasks containing a single line of the text only.

I want all the text file, to be annotated at a single time, rather than annotataing many sentences, since i am trying to extract whole annotated data from the entire text, which is what i need in my case.
I installed label studio using pip, and i am using windows 11, if it helps.
Thanks for your kind interest.

Same problem, I only see undefined$ word, instead of my text to be annotated.

I understand, and fixed my problem by using

in Settings->Labeling interface->Code
note, if you chooese "list of tasks" when importing, then use that setting:

I think documentation is vague

@zakcali It worked. Thank you for your answer.


Please add your planning poker estimate with Zenhub @jsartisan @KelvinOm


Use jbuilder utop <dir>

jbuilder utop src doesn't fully work.
Error occurring if project is built with make before running jbuilder utop src:
...
  #thread;;                 to enable threads

Cannot load required shared library dllcamlstr.
Reason: /home/martin/.opam/4.05.0/lib/ocaml/stublibs/dllcamlstr.so: /home/martin/.opam/4.05.0/lib/ocaml/stublibs/dllcamlstr.so: undefined symbol: caml_stat_free.

Error occurring when starting jbuilder utop src after a make clean:
...
#thread;;                 to enable threads

No such package: sample-lib

See also
https://discuss.ocaml.org/t/jbuilder-templates/958/9?u=mjambon

I removed the utop target from the makefile, so this is no longer an issue.


V2

Adds unit test & TravisCI config (xplat)
Remove globby dependency (no deps! :tada:)
Adds async version
Adds TypeScript defs

Closes #3
Closes #5
Might close #2
Fixes issue in barsh/UniversitySite
https://travis-ci.org/caseyWebb/true-case-path
Breaking Changes

Named exports (was module.exports = trueCasePathSync, now module.exports = { trueCasePath, trueCasePathSync }
Anything relying on (undocumented) glob matching no longer works
Drop Node 6

How does it work
First, make the path absolute if not already. Then, split on the delimiter (\ on Windows, / everywhere else). Then, starting at the fs root, get the contents, and try matching each against a case insensitive regex constructed with the segment. When found, append the real dir/file name. Continue.

:wave: @caseyWebb,
In regards to #9, I've tested this with the bug I've found and your version indeed fixes this. Couldn't test it on old HFS devices tho.
Have you published this version somewhere in the meanwhile? If so, I'd look into replacing the existing dep at Gatsby with your version.
Thanks for your work!
Btw. I've added a test to your branch, but can't figure out how to PR onto this branch, so here's the diff: https://gist.github.com/rmehner/f6b92c2cc00dae7ba7a666a988cb03c1

@rmehner, I haven't published this, but @barsh is actually my boss. He's out of town right now, but I'll give him a ping to publish this when he's back.

Forked to https://github.com/Profiscience/true-case-path, published on npm as 2.0.0


Pattern: Link list visual design & design specs provided by Reboot designers

Notes

The Reboot team is responsible for creating the visual designs and design specs for most of the patterns included in the Solutions page.  This issue is to track the transition of the Reboot design work to the DDS design & engineering team members.

Additional Information

Visual Designs & Design Specs Box folder
Links to the visual designs and design specs will be updated once received and reviewed by the Reboot designers.
Airtable
Link list [storybook] [code] [directory]
CTA [storybook] [code] [directory]

Basically right now the link list only allows for a card style vertical list of links. We're thinking we can add multiple styles of links (See CTA component) like link with icon. This update will allow us to use this consistently accross some of the newer designs coming from the solution page work. Things like table of contents is an example that would leverage this update.

Horizontal layout
Style: text link
optional heading

Need to finalize an optional eyebrow to the card style

Acceptance Criteria

[ ] Visual designs and specs received from Reboot designers
[ ]  A pdf file is created and placed in the Box folder with the updated Sketch file
[ ] Meetings conducted with DDS team members to review the designs

@RobertaJHahn Visual design specs (sketch and PDF) are now posted:
https://ibm.ent.box.com/folder/101876058407

5/5/2020:  Visual designs reviewed with the DDS designers and engineers.


feature: HTTP In: support other methods such as Options

Description
We currently only support the main four methods - need to broaded that out

@knolleary
Looking at this and doing some tests.
The methods listed on MDN are...

GET
The GET method requests a representation of the specified resource. Requests using GET should only retrieve data.
HEAD
The HEAD method asks for a response identical to a GET request, but without the response body.
POST
The POST method submits an entity to the specified resource, often causing a change in state or side effects on the server.
PUT
The PUT method replaces all current representations of the target resource with the request payload.
DELETE
The DELETE method deletes the specified resource.
CONNECT
The CONNECT method establishes a tunnel to the server identified by the target resource.
OPTIONS
The OPTIONS method describes the communication options for the target resource.
TRACE
The TRACE method performs a message loop-back test along the path to the target resource.
PATCH
The PATCH method applies partial modifications to a resource.

Q1: Should we add the missing items to the dropdown list?
Q2: Should we updated httpNodeCors in settings.js to permit "GET,PUT,POST,DELETE,PATCH,OPTIONS,HEAD,TRACE,CONNECT"
NOTES

OPTIONS: options is already handled for server (in code) and seems to take all routes (i.e. the HTTP In is bypassed) We would need to modify this to permit the OPTIONS method to reach the flow
HEAD: Should we delete the body (payload) on a HEAD request (in the HTTP Response node) - OR - expect the user setting up a HEAD method to do this?
Any pointers or opinions you have an the addition of these methods would be greatly appreciated.

I have very little opinion on the matter - other than 'do the right thing'. Happy to take your judgement on it.

HEAD: Should we delete the body (payload) on a HEAD request (in the HTTP Response node) - OR - expect the user setting up a HEAD method to do this?

Okay.. one small opinion - given the head response should not have a body, then we should ignore whatever the user passes in. Saves them having to delete it.


input font: inherit also pulls in line height

I have a search form where the parent element sets a line height to vertically centre the text in the form. The following rule brings that line height to the text inside the input in the form:
button,
input,
optgroup,
select,
textarea {
font: inherit; /* 1 */
}
Perhaps this was overlooked? I don't think it's a great 'normalisation' as I don't think anyone would expect this particular aspect of the font style to come through. Perhaps we could be more specific and inherit just the font-face?

I’m not a fan of styling inputs beyond what’s necessary. However, inheriting all font styles may be an expectation of normalize.css. I’m not sure if this particular choice is “the exception that proves the rule” (which is why body { margin: 0 } happens), and that it must stay in future releases, but I would need a lot more input from the community, particularly from the bootstrap community.

@battaglr, @patrickhlauke, I would very much be interested in your input here, no pun intended. :)

@jonathantneal, @brendon, sadly this is the trade-off of using inherit. In the past using it in other properties has proven to be problematic, as in #502.
Pondering some options I can think of three possible actions:

Leave it as it is, accepting the trade-offs of inherit.

Remove the normalization altogether —not a good idea IMO.

Declare explicit values instead of inherit, using the default values of most browsers, and our own opinionated defaults:

font: small/normal sans-serif;

Or if we want to be even more explicit, and avoid some quirks of the font property we could use:
font-family: sans-serif;
font-size: small;
line-height: normal;

Notes:

According to the MDN the default value for font-family is medium —although in my tests is usually closer to small— and for line-height is normal. Also, in this code-base the body has a font-family of sans-serif —since its value depends on the user agent.
By doing this the optgroup declaration will no longer make sense.
Finally, these values of course should be reviewed.

I would like to hear other opinions. :smiley:

Hum, apparently I missed a fairly obvious fourth option, that is a middle ground:
font-family: inherit;
font-size: inherit;
line-height: inherit;

If we do this we still have to deal with potential problems of inherit, but by being explicit we don't take anyone by surprise while using the font property that may be a bit confusing for some. Also we avoid inheriting things like font-style, font-weight, etc.
Like a bonus point, we could remove the the optgroup declaration.

I don't like the idea to use inherit with shorthand syntax because that affects every single property:

font-style (normal per spec)
font-variant (normal per spec)
font-stretch (normal per spec)
font-weight (normal per spec)
font-size (medium per spec)
line-height (normal per spec)
font-family (depends on user agents per spec)

Being explicit seems more reasonable to me. Also because a new property could be added; as it happened with font-stretch that was not part of the original properties to include in font.

I agree, that's a great compromise :)

@thierryk, we totally agree on this (thank you for the spec links).
What would you suggest as possible solution for this?

@battaglr using inherit with a limited set of properties is definitely an improvement but I don't see how your suggestion solves the problem. From my understanding, @brendon does not want this:
line-height: inherit;

Or am I missing something? Because his comment ("great compromise") seems to say otherwise...

@thierryk, sorry you're right, I didn't notice the line-height inclusion. I don't think line-height should be inherited by any of those elements. Most tend to have their own 'surroundings' that look weird when a line-height is applied.
My comment should be: It's a great compromise, provided you're inheriting logical aspects of the font. What is 'logical' is probably a matter of opinion.

The specs say that the initial value for line-height is normal. Do we know the discrepancies between browsers and controls regarding the initial value of that property? Because if we need to set a line-height value then it may be better to go with normal rather than inherit as this should lead to more "predictable" results, no?

I’m with @thierryk on this, because line-height: normal would be a spec normalization, and the current style is opinionated, anyway. However, a lot of people might be expecting this with normalize.css, line-height and all, so I hope for more feedback.

I'm happy with normal.

@jonathantneal, @thierryk, @brendon, I may have expressed myself wrong, since I was not necessarily advocating for a particular solution, but hopping to open an interesting discussion (like this one) by presenting some options.
I think that line-height: normal would be a good replacement for inherit —as I mentioned in a previous comment—, but I'll ask the same question than @thierryk:

Do we know the discrepancies between browsers and controls regarding the initial value of that property?

If I'm understanding right, we all agree that would be a good idea to stop using font and just normalize only the 3 properties that —apparently— differ in browsers. Having something like this:
font-family: inherit || sans-serif;
font-size: inherit || ??;
line-height: normal;

Generally I would prefer an explicit value over inherit for these properties, but I'm not sure about font-size.

To be honest, I don't like inherit. If normalize.css is about:

Preserving useful defaults, unlike many CSS resets.
Normalizing styles for a wide range of elements.
Correcting bugs and common browser inconsistencies.

Then I think we should avoid using inherit because this value relates to styles set by authors instead of styles set by UAs. In other words, I think normalizes.css should style elements the same regardless of projects and inherit does not help to achieve that.
I understand that most authors expect to have these values inherited but I don't think this is the job of normalizes.css. In my opinion, people should use custom rules targeting form controls for this. normalizes.css should not become a "base"/opinionated style sheet.
I don't know. May be there should be a companion file, containing rules that do not belong to normalize.css but that are pretty much meant to be included in every project.

I would also agree that setting the normalization to line-height: normal would be good, as well as making font-family and font-size match up more (opinionatedly) with the main content/body styles.

@patrickhlauke but how do we draw the line? Don't you think opinionated styles belong to a library?
I know we already have exceptions (i.e. margin:0 on body) but that does not mean there is a good rational for it.
This is a recent comment from @jonathantneal:

This would be much more useful in something like sanitize.css,. normalize.css should not get into overriding OS styling.

I think making font-family and font-size opinionated is the goal of other libraries.
For what it's worth, this is one of the reasons I didn't want to include normalize.css as a dependency on yahoo.com, because I feared we could end up on-boarding things we could not have expected—and this issue is the perfect example of that.

Probably related.

Basically, I would be happy with the original posters "problem", i.e. inheriting line-height on all elements. My problem is IE is not behaving like the other browsers, see https://jsfiddle.net/8ppqodc4/9/
I could not find a way to make IE (11 and below, don't know about EDGE) behave like the others, so the most unobtrusive way to normalize all browsers seems to be adding
input, button {   line-height: normal; }
which was (without button) removed in the commit I commented on. And after the removal, my buttons and inputs were out of line in IE.
So, in my comment, I moaned about the removal of said line. I would like to see it back, except there's a better way to make IE expand the height of the whole input by inheriting line-height.

@jovilog It is not a problem with inheritance per se because the computed value shows the expected line-height value (i.e. 45px), it is just that Internet Explorer ignores that value (line-height has no effect on the layout of the box). Note that this was also the case in Firefox for a very long time.

[line-height:normal + padding]  seems the only "elegant" way to achieve same-height inputs and buttons across all browsers

Actually, I think you'd have a better chance to achieve same height across browsers by relying on the height property instead of using line-height + vertical padding (give it a try).

@thierryk

It is not a problem with inheritance per se because the computed value shows the expected line-height value (i.e. 45px), it is just that Internet Explorer ignores that value (line-height has no effect on the layout of the box).

Right, that's true. But is normalize.css about normalizing computed values or what's actually on screen? In most cases, the two are the same, but here?
Keeping elements as flexible as possible is a core concept of modern best practices in (responsive) web design. Using a fix height to somewhat reset appearance seems so against this. Where's my thinking wrong here?

@jovilog

Keeping elements as flexible as possible is a core concept of modern best practices in (responsive) web design. Using a fix height to somewhat reset appearance seems so against this. Where's my thinking wrong here?

You said you were using padding to fix the issue in Internet Explorer, I simply suggested you should give height a try. None of these solutions are "flexible", it is just that height may be a better one.
I was not suggesting to normalize input by styling them with an explicit height.

@thierryk
I'm using padding (and a unitless line-height on the body element) as basics in the author stylesheet to get the basic look I want, which is not unusual, I believe.
I'm not using it to fix the issue with IE. IE applies padding on inputs just like any other browser.
Until the recent removal of input { line-height: normal; }, this worked great.

but what we're suggesting here is to include that style

Yes, yes, please!
@battaglr wrote:

line-height: normal; /* If indeed requires normalization */

I was just substantiating the progress of this issue with a related issue (in my opinion) and example, i.e. inputs do require this normalization (except there's a better way to make IE inherit line-height like the other browsers).
So, ideally, IE would expand the box of inputs with growing (inherited) line-height. Since I don't know how this could possibly be done, I am all for line-height: normal coming back, because this makes inputs look quite consistent across browsers.
[offtopic]
I was not looking for an alternative to padding, which works just fine and is much more flexible than height:

padding is ignored by checkboxes and radio buttons, height is not
therefore padding can be applied to one low specific selector as a base style, selectors for height need to be unnecessarily specific
padding can impossibly clip the text, an explicit height could

[/offtopic]

I think a PR will do now. :)

Since no PR has been made, I’ll be making the PR for this.

Remove inherit from the shorthand font, and avoid shorthands in general.
Restore inherit to font-family and font-size as another exception to the rule.
Possibly add normal or a computed value to line-height if normalization is necessary.

@jonathantneal, I was waiting to have some time to tackle this, but needed to iron some things first. My thoughts so far:

Totally agree on removing font in favor of more specific properties. But I differ in the values you're proposing.

Totally agree with @thierryk here regarding inherit:

Then I think we should avoid using inherit because this value relates to styles set by authors instead of styles set by UAs. In other words, I think normalizes.css should style elements the same regardless of projects and inherit does not help to achieve that.

Also notice that inherit has been the reason of many opened issues and unexpected behaviours —that's why we removed color from input, among others.
Regarding the implementation, I would:

Use font-family: sans-serif since we already do this on the html.
Use line-height: 1.15 since we already do this on the html.
User font-size: 100% since this was the original normalization for this property.

I would really like to have the time to test all this.

@battaglr, wonderful! I think we very much agree. Effectively, you are suggesting we use something closer to the computed values than inherit, which in this case I also prefer. We need to make a CodePen test for line-height: normal that I can apply across all of the browsers we support. That will be a goal for this week, if you have not already made it and will not have the time. Thanks a bunch for your notes.

@jonathantneal, awesome!

I create 3 test inputs; one using line-height: normal, another using line-height: 1.15, and the last not setting the line height at all.
I expect that line-height: normal equates line-height: 1.15, so I set the element’s font size as 40px and measure the offsetHeight of the element, expecting to see 46 because 40 * 1.15 = 46.

Test Results

In most browsers, all 3 tests return 46.

In Chrome 50 for Windows (and 48 for Nexus 9), line-height: 1.15 normalizes the line height, which is otherwise 45.
In Firefox 45 for Mac, line-height: 1.15 really normalizes the line height, which is otherwise 41.
In Safari for iOS 9, the result is always 48 unless you explicitly set the height to a non-auto length. I don’t know what this is due to; shadow elements?

https://app.crossbrowsertesting.com/public/i76b092cd2b52b86/screenshots/z8f9760e01ee5fdbef3e

I met the problem just now, However use line-height: normal works

Thank you @jonathantneal, @battaglr, and all the rest of you who chipped in to fix this one up :)

The font-family should stay inherit IMO, as it overrides the font-family set on html or body in an author stylesheet. I have to set it again on form controls now.
The separation of line-height has the same effect, but is very welcome as I tried to point out in a former comment.

I just updated to v5.0.0 and noticed, that all my buttons are broken. But all the other elements (like span) that use same classes and look like buttons - they are fine. I've read this thread and understood why this happened.
Dudes, you're totally wrong. I'll explain.
Everything has started with @brendon and his huge line-height (e.g. line-height:100px), which is used to center the content of a search form vertically:

But Brendon is now complaining that the input inherits this huge line-height:100px and everything looks awful, like this:

So, Brendon, guess what? line-height:100px is a hack. It's not the general purpose of line-height to center objects vertically. Thus you have at least 2 options:

Stop using this hack in this place. Use a more appropriate technique of vertical centering instead.
Or simply define height for your inputs. height+border-box is one of best ways to make inputs look exacly the same in all the browsers.

Okay, what's going on now?

Now normalize.css sets font-family:sans-serif to all the form elements. That means that buttons look differently from the other elements on the site:

font-family:sans-serif is totally useless. All the modern sites use the same font for the buttons as for all other elements. So almost every developer would be glad to have the inheritance here (see #642).
Quote from issue #642:

As a user of this library, the most common thing I do is set a base font for a project. Usually on body. I then appreciate that font being (weakly) inherited by every element automatically. (Weakly, meaning very easy to override in special cases). This is a simple technique to achieve consistent site appearance.
<...>
If my site uses Open Sans as its base font I will probably want my form elements to use Open Sans.

Yes, I understand that normalize.css is about normalization, not convenience. But font-family:inherit makes buttons look exacly the same in all the browsers, so IT IS about normalization.

line-height:1.15 is another terrible idea.
Many methodologies say that in most of the cases we shouldn't stylish tags. We should use classes instead. Thus many developers have classes like .btn .btn_green .btn_big, which are used to stylish any tags as buttons. No matter is it button or span, they'll be looking exacly the same:

<button class="btn btn_green">Button</button>
Span

But if we remove the inheritance the perfection is broken:

So, for font anything but inherit is a terrible idea.
If you think the opposite, then you're probably doing something wrong. For example, using line-height to center a complex scene vertically.

Hi @olegcherr, thanks for bringing this to everyones attention. Perhaps the original PR would end up being more appropriate?: https://github.com/necolas/normalize.css/issues/591#issuecomment-230505380
@olegcherr, I know it's a hack. Still, one who sets a large line height on text for aesthetic reasons would probably not want their form inputs inheriting that line height either. Perhaps line-height should be left untouched by normalize. Or perhaps we can be more specific and inherit only for button and not other inputs?

I agree with @olegcherr that setting font-family: sans-serif; on the input elements is not such a great idea. @battaglr mentiones this is done because the font-family is also set for the html, but this is no longer the case since 7.0.0. I would expect that all browsers use the same font for body text and inputs, so using font-family: inherit; is the logical option for me.

I’m still here. :) Feel free to read the related threads to understand how I cannot help. I agree that inherit, while not a normalization, would provide a less opinionated default.

@TimVevida, considering the current direction of the project, I agree that going back to inherit would be the best thing to do.

At 2017-10-31 04:14:10, "Luciano Battagliero"<EMAIL_ADDRESS>wrote:
@TimVevida, considering the current direction of the project, I agree that going back to inherit would be the best thing to do.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Not working properly with devtools

Describe the bug
Using the latest 2.0.0-beta.51, the integration with Nuxt DevTools doesn't seem to work as expected.
I'm using defineOgImage in App.vue to apply a static og image to all pages. It gets added correctly but the devtools doesn't pick it up.
OpenGraph (built in Devtools)
The image doesn't get picked up in preview or details. It says it's missing og:image and other metatags although it's present in the website .

OG Image (Nuxt Seo OG Image module)
It says there isn't a defineOGImage used in the app. Even if I use another defineOGImage in pages/index as instructed the message stays the same.

Reproduction
I've created a minimal reproduction repo (Devtools doesn't work in Stackblitz / Codeflow).

 It says image og tags are missing but if you inspect the DOM you'll find them.
Go to OG Image option. It says defineOGImage is not used while it's there in App.vue. Uncomment the defineOGImage in pages/index.vue and the message stays the same.

Reproduction
https://github.com/MuhammadM1998/nuxt-seo-reproduction
System / Nuxt Info
- Operating System: Windows_NT
- Node Version:     v20.10.0
- Nuxt Version:     3.8.2
- CLI Version:      3.9.1
- Nitro Version:    2.8.1
- Package Manager<EMAIL_ADDRESS>- Builder:          -
- User Config:      devtools, modules
- Runtime Modules<EMAIL_ADDRESS>- Build Modules:    -

OpenGraph (built in Devtools)

There is a bug in the Nuxt DevTools OpenGraph tab that it's not showing it, the module itself is working correctly.

OG Image (Nuxt Seo OG Image module)

This is because you're trying to use the previewer for a pre-existing image, this is not currently supported. I've made an issue here to track: https://github.com/harlan-zw/nuxt-og-image/issues/129.

Thanks for clarifying. I'll post update If I found a solution to the OpenGraph module

Will close this for now as there are already upstream issues for them.
DevTools: https://github.com/nuxt/devtools/issues/580, https://github.com/nuxt/devtools/issues/274
OG Image: https://github.com/nuxt-modules/og-image/issues/129


Add Docker build/push

Use the original SLATE Catalog's Incubator version of basic-auth to devise a way to incorporate building and pushing any related Dockerfile material to Harbor.

Not going to do this.


Update models.py - fixing error message for azure --model issue

[!NOTE]
IF YOU SEE A LOT OF FORMATTING RELATED MERGE CONFLICTS
PLEASE MAKE SURE THAT YOU ARE USING OUR CODE FORMATTER.
Please see our development guide.

Reference Issues/PRs

What does this implement/fix? Explain your changes.

@klieret please correct this if i'm wrong

Thanks! :)


added breast cancer data set

Description

Issue Ticket Number
Fixes #(issue_number)

Checklist:

[ ] I have followed the contributing guidelines of this project as mentioned in CONTRIBUTING.md
[ ] I have cross-checked that the dataset I'm uploading is not present in the project
[ ] I have cross-checked that the dataset is present in the correct folder

The breast cancer dataset is already there and yes @Mahakal0123, don't spam. Uploading different dataset doesn't sounds good right? Also it is unfair to others.


Create LICENSE

Merge activity

Oct 20, 6:36 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.


[Usage question] Using Pact JVM with JUnit 5 in a CDI application

I'm working on a prototype how to use Pact for contract testing in our application. While the basic setup, either with JUnit 5 or the Maven plugin, is working fine, I do have some trouble when it comes to seting up provider states.
Following the documentation I'm aware of the @State annotation. So, a state setup method could look like this:
@State("user already exists")
public void createUser() {
  // ...
}

The problem I'm facing is this. Our application uses CDI, it is kind of heavyweight and so is its data model. Even for only creating a user, at minimum I would have to somehow inject the DAO for database access. For more complex provider states I would have to insert data across several tables in a consistent way. All of this would get kind of complex.
Are there any recommendations how to handle this? Some of my first ideas...

Injecting the services, or at least the DAO, into the Pact provider state methods. This seems to create a new layer of complexity with something like Weld JUnit or Arquillan?
Using Mockito to mock services. As there are functional tests for the services themselves, I'd go with that approach but I've only found examples for Spring Boot applications, none for CDI.
Implementing a REST endpoint in the application dedicated to insert data. This would solve the dependency issues but the complex data model is still there, so I wouldn't gain much.

From what I know so far, I'd favor #2 though it contradicts the idea to "use as much production code as possible".

I would go with a mock-based solution if you can. The provider state callbacks are there so you can put your provider in a valid state so it can generate a valid response. The actual data it uses is not as important.


miss contract file

I did not find the KeysWithPlonkVerifier.sol contract file document

It's in .gitignore as it's auto-generated:

https://github.com/matter-labs/zksync/blob/1387e44b22f794910867132b361ac12222691268/infrastructure/zk/src/run/verify-keys.ts#L13-L32


We only report buckets so don't track summaries

We stopped using the summaries a while back this just updates the default to not double track.
@jhaber @stevegutz

lgtm


Does this example support other vehicles?

look this title

Or must Lincoln MKZ be used?

https://github.com/ApolloAuto/apollo/blob/master/docs/howto/how_to_add_a_new_vehicle.md

thanks a lot


Better Performance PLS

I think the system is really impressive!
It has great features, is easy to use and has a beautiful design.
The only negative...
The performance is not the best...
It sometimes loads a bit longer and has micro jerks...
My PC:
CPU: AMD Ryzen 9 5950X
GPU: 24GB ASUS ROG Strix 3090 OC
RAM: 64 GB DDR4 3600
Main SSD: Samsung Pro 980 1 TB
Secondary SSD: Samsung QVO 870 4 TB

Merging with #4180

We're excited to share that startup performance will be significantly improved in the upcoming release of version 3. You can download the preview version from our website https://files.community/download.


Android Devices

Is there an option to enabled the "Status fade" effect only when running it on iOS?
See bellow issue with Android:

Greetings @ghpabs!
I've closed this issue because my sensors indicated it was old and inactive, and may have already been fixed in recent versions of Ionic. However, if you are still experiencing this issue, please feel free to reopen this issue by creating a new one, and include any examples and other necessary information, so that we can look into it further.
Thank you for allowing me to assist you.


feat: resolve schema via adbc

This PR adds server side schema evaluation for a single parquet file.
TODO:

Support for multiple files
Supports for any adbc backend
Support for merging schemas

The code looks like it should work. Do we want to add some code that exercises the new path (perhaps remove the hard-coded schema from client_demo.get_customer_database?

updated.


Improve Blending Soft Shadow Logic

Prevents Distant Shadow Splits from getting absurdly blurry with Blending Splits when using High Blur Values
Before (blur 10):

After (blur 10):

Do note that the Peter Panning is caused by https://github.com/godotengine/godot/pull/68339 and also appears with this level of blur with blending splits off on master, as the Bias modifier used doesn't take into account the Soft Shadow Blur Factor that is doing the softness modifications.

100 was just arbitrary as it should never even cross 20 (ultra soft * 10)
What the PR does is it enables the blur factor for blending splits but it prevents it from going below 1.0 as that tends to look quite a bit worse when it's allowed to go down to 0 on longer distance directional shadows (beyond the default 100 units) and blending splits is best used when you have such longer distance directional shadows in the first place as it hides the split transitions that aren't all that intrusive at default distance.
TBH I'm not very happy with this solution, but the only real solution would be to allow the user to set their own blur value for each split but from a UX perspective I'm not sure how I'd do that for advanced users while keeping the auto behavior working for less advanced users.
One thing I'm unclear on however is how Shader Templates play into this, and would it be possible for advanced users to just hack in their desired blur values for a given split, and how difficult that'd be, as if it isn't a ton of work with them, I'm actually in favor of scrapping this PR and just documenting how to do such somewhat common modifications to the Templates, as then people who don't use it wouldn't be dealing with the slight potential performance costs while advanced users would just have much more control that this isn't able to provide anyhow.


Do not showcase KokkosExt::ArithmeticTraits in our examples

Related to the discussion in https://github.com/arborx/ArborX/pull/986#issuecomment-1866563100
Without going into a debate of what to do with our KokkosExt::ArithmeticTraits, we should not have it in our examples and use the experimental numeric traits from Kokkos directly.

Not worrying about the not started builds.