Installation fails

My environment

OS version/details: SLES15-SP1
Node version: v17.4.0
npm version: 8.4.1
Version of yo : -bash: yo: command not found

Expected behavior
I'm using npm install -g yo to install Yeoman, as expected it should be installed successfully.
Current behavior
Installation failed with errors.
Steps to reproduce the behavior
npm install -g yo
Command line output
npm ERR! path /root/.nvm/versions/node/v17.4.0/lib/node_modules/yo
npm ERR! command failed
npm ERR! command sh -c yodoctor
npm ERR! sh: yodoctor: command not found

npm ERR!
I mean: sudo npm install -g yo

I had similar problem on Ubuntu 22.04 using node v18.18.0 provided by snap. I installed yarn first and then installed yeoman by using the command sudo yarn global add yo. The installation completes successfully after that. No clue why the npm not able to complete the installation.

Hi everyone,
Same issue:

Installing as root, so no doubt, it does not depend on that.
Any thoughts?
Thanks.

Hi @swahpy, please ensure your PATH is setup correctly. It must include path to your global npm installation where the tools are.
echo "$(npm prefix -g)/bin"

See https://docs.npmjs.com/cli/v11/commands/npm-prefix
This is not issue with the yo tool and you must ensure your machine is configured correctly.


MDX?

HI,leptos rendering Markdown with embdedded dynamic leptos components

There’s no support for this at this time. It would be possible to create a library to do it in user-land without additional support from the framework, I think.
I’ll leave the issue open in case others are interested in the idea, but I don’t have any plans for MDX support.

While not mdx, a couple of us are compiling regular markdown with femark. Perhaps that could work as a substitute or might help you create your own MDX compiler


Manage tracked token issue

The tokens used in Vigor protocol are missing in traked token list and it is not possible to add all of  them manually.
FYI  I was able to add only one manually
the required token are PBTC, IQ, VIG, VIGOR, USDT

The Vigor team is free to add all of these tokens to the smart contract which powers Anchor's token list:
https://github.com/greymass/customtokens
We can add them as well to the contract, we would just need to know the token contract name, token symbol, and token precision for each one to be added. I'm not familiar with some of these tokens and not sure where to find the information myself.


GPS AR ok in Android Firefox , coordinates not passing in anywhere else in Android and iOS browsers

Do you want to request a feature or report a bug? -> bug, I hope.
 https://gitter.im/AR-js returns http404

What is the current behavior?
https://panoramapalace.com/preview/mindar/quiztest.html works on firefox android , shows the ARcontent but camera is white in firefox iOS , camera works but does not show AR contente at all
If the current behavior is a bug, please provide the steps to reproduce.
added simulateLatitude and simulateLongitude to help.
just open the link with some browser. It asks for permitions and then nothing happens.
all the code is there in quiztest.html , I did not add server side yet till i get this stable

Please mention other relevant information such as the browser version, Operating System and Device Name
Android and iOS devices
What is the expected behavior?
i'd like this to work cross browser.
screenshots of some browsers and a screencast of firefox android working here -> https://drive.google.com/drive/folders/1_g7ZKaiuxYsGdOLzM_ZU21IXgeZ3PMDL?usp=sharing
Thank you for your help and work.
If this is a feature request, what is motivation or use case for changing the behavior?

just opened quiztest.html (it has simulateLatitude and simulateLongitude) in chrome with GPS off and my "Ar boxes" show.

further testing in iOS reveals that if simulateLatitude and simulateLongitude is present all works in all browsers.
Same for Android
thank you

spent the whole day thinking about this and the presence of "simulate" so I added a

and it showed above me (because of position 10) in android Chorme (s22ultra)
I (or the lib) must be missing something to pass the gps data to the framework
thanks

Have you looked at this bug?. If that doesn't help, try logging and changing bits and pieces in aframe/src/new-location-based/gps-new-camera.js

I'v ran the samples with js code from internet and from the samples and always without sucess in android chrome, for example
the only way to work in all browsers is with simulated coordinates
Thank you for your insight

Tried project wizard from AR-js
overcome the warning of "don't get gps coordinates before user interaction" but... this just won't work
Does anyone have a combination of versions that work for location AR in chrome?
Thank you

@nickw1
hi nick, this is my bug, i just tested the other solution you gave on the other one but then all my comments there would be unrelated and highjacking the other issue
about the links you provided
https://github.com/AR-js-org/AR.js/tree/master/aframe/examples/new-location-based/poi
works great in firefox and shows nothing in chrome
https://github.com/AR-js-org/AR.js/tree/master/aframe/examples/new-location-based/basic-js
removed the alert about gps and i open the page with gps enabled

when i open in ffox i get an imediate warning about "got first GPS position -> " and it adds the cubes and i do not need to touch anywhere. it just works.
when i open in chrome nothing happens. Then i click on the Go and it adds the coordinates i gave to the simulateLatitude and simulateLongitude, it shows the warning about the "got first GPS position -> " but it never goes to my real location as ffox does

Android chrome is now working as it should and always did
I ended up by coding some javascript for debugging and foud out the coordinates of my device were way of and found accuracy was 2km
There is a setting in my android phone the makes high accuracy available for each app and it was disabled for chrome and enabled for firefox.
That's why nothing was showing to me

Still.. "brave" browser is not working yet but may be it just takes some time... didn't go and check "can i use" things for him
Thank you @Platform-Group and @nickw1 .
Hope this thread helps someone.

@herrpedro glad you got it working! Thanks for sharing your experiences.


Can it implement custom width segments instead of fixed widths?

I have seen segment controls in apps having custom widths and underline bars animate according to their size. Where custom widths are determined by the contents in them. Here the height is fixed for the maximum width segment item or else the font size is reduced to fit in.
Hoping this could be implemented or have done already.

@GocePetrovski https://github.com/GocePetrovski/ScrollableSegmentedControl/pull/17 will fix this.

Done. See v1.4


Fitting for white noise

In general, approxposterior won't just work on simulated data, it needs to handle real data, obviously! Need to implement ability to supply, fit for white noise.

Users can construct and supply arbitrary mixtures of GPs.  For usage of GP mixtures, see this example from the official george docs.


Mrr prequalify remove participants#2891

https://github.com/edenlabllc/ehealth.api/issues/2891

Coverage decreased (-0.06%) to 91.117% when pulling b4d814900eafc2c77bccb22cc928e838a5102c52 on mrr_prequalify_remove_participants#2891 into e7b3081b3193392c03dfe42fe7f47327affe680c on develop.


typo in test_string.cpp

it seems that BABYLON_USE_PROTOUF at https://github.com/baidu/babylon/blob/5db6b619a0fac8df960f3aacce18e27575436699/test/serialization/test_string.cpp#L3 is a typo, which I think should be BABYLON_USE_PROTOBUF.

thanks. will fix in next release


Create User instance in SQL

User attributes: ID, Name, Surname, DateOfBirth, Phone, Mail

Belongs to:

#2


Possibly avoid modifying circuit.data

https://github.com/Qiskit/qiskit/pull/10827, which moves QuantumCircuit._data to a data structure in Rust, is due to be merged before the next Qiskit release.  This may impact our ability to modify circuit.data, which we do in a few places in the current code.  We should start by testing CKT against that branch and noting where the test failures occur.

Let's keep this issue open until Qiskit/qiskit#10827 is merged. If all tests still pass then, we can close this.

Closing, as https://github.com/Qiskit/qiskit/pull/10827 is now merged.


Add method to download the image/video

Is your feature request related to a problem? Please describe.
Currently the library only gives the users an URL and tell them if it's an image or a video and leave the downloading up to the user.
Describe the feature you'd like
It would be nice to provide a DownloadMedia method on the ApodClient that downloads the content and returns it (maybe as byte[]? I'm not sure what format would be preferred for users).

Known video sources:
youtube.com (example: 2019-02-05)
vimeo.com (example: 2019-01-20)
ustream.tv (example: 2019-06-02)
Youtube is most common by far.
Videos would probably not be downloadable


Create Testing Workflow and Utils

Changes

Automated testing infrastructure including a Jest configuration in the server/functions directory.
Utils for managing firebase state
Adds a CI workflow and makes changes where necessary.

Requirements
Requires yarn install in functions directory to get testing dependencies.
PR Dependencies
Depends on: #24.
Merged Branches and Other Dependencies
Merged branch(es): None
Other dependencies: None
Subtasks / Progress
N/A
Preview
N/A
Testing
Automated
List of added tests:

Example test

@rlnsy this looks great thank you! Can we update the README? Also, is there a page on Notion for devs to know how to add test stubs, etc?

@wynnset I added some example tests and all the required infrastructure. Will add a testing document on notion soon.

@wynnset ready to merge once docker PR is merged.

@rlnsy could you please fix the merge conflicts when you get a chance?

@rlnsy could you please fix the merge conflicts when you get a chance?

Done.


Support UEFI runtime services in addition to boot services

Currently the IDA plugin does a very good job in finding calls to several selected UEFI boot services, but so far the runtime services were neglected. Since runtime services are a key part of the UEFI specification, supporting them will greatly aid the reverse engineering of virtually any UEFI module.

This plugin is partially rewritten in C++ (https://github.com/binarly-io/efiXplorer) and has a primitive search for runtime services via gRT. This does not work for all drivers, but we are working on a more advanced search. Any ideas, problems and pull requests are welcome.


Adds Apache License to the repository

It's important to have a license for the dataset [DUT Anti-UAV] distributed via this repository.

@zj5559 @wangdongdut
I'm currently doing some research with Anti UAV datasets and can work only with datasets that contain a license. In my opinions, your dataset is quite good and should be made available to the research community in a broader way. Hence, I would like to know if it's possible to add the Apache License to it. Since your dataset is distributed via Google Drive and Baidu, with links in this repository, adding the license here should suffice.
Thanks in advance.

Thank you very much on behalf of the whole community, @zj5559. I will close this PR as the license is already available.


nextcloud-reloaded branch + Buster issues

Hi,
There are couple of issues with nextcloud-reloaded on latestDebian buster.

Fixable - firewalld sections must be removed or commented out in order to playbook to run.
Not fixed yrt - playbook throws error "collabora : set allow domain cloud1.myserver.com - 'missing parameter(s) required by ''attribute'': value'". Resulting system displays "FIle not found" on startup page.
nextcloud error log:

2021/02/22 16:46:11 [error] 9999#9999: *2 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: <IP_ADDRESS>, server: cloud1.myserver.com, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/run/php/php7.4-fpm.sock:", host: "cloud1.myserver.com"
Playbook errors:
2021/02/22 16:46:11 [error] 9999#9999: *2 FastCGI sent in stderr: "Primary script unknown" while reading response header from upstream, client: <IP_ADDRESS>, server: cloud1.myserver.com, request: "GET / HTTP/2.0", upstream: "fastcgi://unix:/run/php/php7.4-fpm.sock:", host: "cloud1.myserver.com"

[DEPRECATION WARNING]: ALLOW_WORLD_READABLE_TMPFILES option, moved to a per plugin approach that is more flexible, use mostly the same config will work, but
now controlled from the plugin itself and not using the general constant. instead. This feature will be removed from ansible-base in version 2.14. Deprecation
 warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
ERROR! couldn't resolve module/action 'firewalld'. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in '/home/andrei/Downloads/nextcloud/roles/onlyoffice/tasks/main.yml': line 38, column 3, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

- name: open firewall ports {{ nextcloud_web_port }}/{{ nextcloud_ssl_port }}

# ----------------------------------

ERROR! couldn't resolve module/action 'firewalld'. This often indicates a misspelling, missing collection, or incorrect module path.

The error appears to be in '/home/andrei/Downloads/nextcloud/roles/talk/tasks/main.yml': line 27, column 5, but may
be elsewhere in the file depending on the exact syntax problem.

The offending line appears to be:

  block:
  - name: open firewall ports 3478/tcp/udp
    ^ here

# -------------------------------------

fatal: [localhost]: FAILED! =>
  reason: |-
    couldn't resolve module/action 'firewalld'. This often indicates a misspelling, missing collection, or incorrect module path.

    The error appears to be in '/home/andrei/Downloads/nextcloud/roles/webserver/tasks/firewall_config.yml': line 39, column 5, but may
    be elsewhere in the file depending on the exact syntax problem.

    The offending line appears to be:

      block:
      - name: open firewall ports {{ nextcloud_web_port }}/{{ nextcloud_ssl_port }}
        ^ here
    We could be wrong, but this one looks like it might be an issue with
    missing quotes. Always quote template expression brackets when they
    start a value. For instance:

        with_items:
          - {{ foo }}

    Should be written as:

        with_items:
          - "{{ foo }}"

# -------------------------------------

TASK [collabora : set allow domain cloud1.myserver.com] ********************************************************************************************************
Monday 22 February 2021  16:43:39 +0200 (0:13:38.679)       0:16:45.726 *******
fatal: [localhost]: FAILED! => changed=false
  msg: 'missing parameter(s) required by ''attribute'': value'

Ansible starts to rename all modul names. Starting with firewalld (which is used only for RedHat based distrios.)
Should be fixed with 68ec322

I have merged 68ec322 with my fork and tried building with an Ubuntu 20.04 AMI with no luck.
Ansible
TASK [check install status] **************************************************** Thursday 04 March 2021  23:01:47 +0000 (0:00:01.810)       0:06:11.590 ********  fatal: [localhost]: FAILED! => changed=false    connection: close   content: ''   content_type: text/html; charset=UTF-8   date: Thu, 04 Mar 2021 23:01:48 GMT   elapsed: 0   msg: 'Status code was 500 and not [200]: HTTP Error 500: Internal Server Error'   redirected: false   referrer_policy: no-referrer   server: nginx   status: 500   transfer_encoding: chunked   url: https://test2247.example.com/status.php   x_content_type_options: nosniff   x_download_options: noopen   x_frame_options: SAMEORIGIN   x_permitted_cross_domain_policies: none   x_robots_tag: none   x_xss_protection: 1; mode=block
Nginx
Could not boot files_versionsCould not resolve OCA\\Files_Versions\\Versions\\IVersionManager! Class can not be instantiated"},"userAgent":"--","version":"<IP_ADDRESS>"}

I managed to fix this by setting the inventory file to use PHP8 and using fixes 0b99e726700ebcb4c52671439d2703d6b8bbaf08 and 2fcb3f953045d47a72ddbcf5999f145ac3b5b1d6.
Redis was actually the underlying issue because it is now using PHP8 and Nextcloud was using PHP7.

I made some changes to code so it's working also with php 8.0 right now.
I also disabled the setting of the default loglevel to 1. That crashed any occ command executed later.


Brainstorm list of howtos (maybe in job story form)

Create a list (e.g. 5-20) potential howtos we could write re FD. Preferred form would be a job story. Example:

When I have a data package I want to import it into pandas as a data frame so that I can analyze in pandas my favourite tool

@lwinfree @roll I've booted this issue for you guys following on from chat the other day. Feel free to amend / update.
Acceptance

[ ] A list in spreadsheet or e.g. here or hackmd of 5-20 potential howtos

if we can, add example of someone who had this
Bonus: value + cost estimates

Tasks

[ ] Brainstorm the list
[ ] Review ...

Hey @rufuspollock, thanks for getting this started. We can document our work in this issue. However, I also want to note that we had all agreed that I was going to do this task (start this issue), and I just want to make sure that we are all still on the same page and sticking to our project plan 😃

@lwinfree yes, you are doing the issue. I just booted just b/c i had not seen anything in last 48h and did not want it to overflow from (my) stack.

I think this brings up a good point that it would be helpful to put project management guidelines on the agenda for the next call. I want to make sure that we all have the same expectations and agree to a plan of action to optimally work together. I'm starting the list in the existing spreadsheet here & then Evgeny & I will go from there!

I think we can use some generalized approach for integration specific tutorials. We have a matrix of source/targets and actions/stories:
Source/target

SQL
BigQuery
Pandas
ElasticSearch
SPSS
CKAN

Stories

Export data and metadata from {source} to FD
Import data and metadata from FD to {target}

Writing or adopting a first tutorial could cost a day or so but generating the next 11 will be much faster.

FIXED. We now have a list of 10 howtos. We will keep adding no doubt but done for now. Will be follow up issues to actually do howtos.


Rule Targets should allow for custom data categories

Today in Fides, you cannot create or modify rule targets to use custom data categories, which will limit the ability of customers to configure DSR rules based on their own customizations to the Fideslang taxonomy. The rule targets currently only support data categories from the default taxonomy.
Steps to reproduce

Create a custom data category - this can be done either via a YAML file extension of the taxonomy or via the UI at /taxonomy.
Try a PATCH request to: "/api/v1/dsr/policy/{policy_key}/rule/{rule_key}/target"
You can use the policy key default_access_policy and the rule key default_access_policy_rule
You should get an error that lists the valid enumeration members as the default data categories only.

AC

Update the rule target data category validation to allow any data category from the instance of Fides. I should be able to extend the taxonomy and create custom data categories, then create a rule target for a policy that uses my newly created data category.
The validation should not allow any data category, just those defined in that Fides' instances taxonomy - findable at /api/v1/data_category

Re-implemented with this PR.


Can't set custom colors!

How to set custom color for the tag? The themes are not enough. Thank you.

$ npm i<EMAIL_ADDRESS> <ion-tags-input
    [color]="'#999'">
 </ion-tags-input>


Update freeorion-test.json

Like the official installer, I have added a full-screen shortcut.
It was mentioned in the official wiki, so I decided it was necessary.
The bin was removed because it could not be executed normally outside of the installation folder.

This needs a rebase before it can be merged.


Feature request: add CI checks and run on PRs

We could use GitHub Actions to run some tests on PR branches, and require these checks to pass before merging.
Some things to test:

Everything compiles, runs, and exits cleanly (return 0)
Check program output and test if existing features work correctly.

GitHub Actions docs: https://docs.github.com/en/actions/learn-github-actions


Sorting of pac lists

Describe actual behavior
Symbols (such as - and .) are ignored when using the command sort, such as addWhite.sh.
What is your expected behavior
Symbols will not be ignored when sorting the lists.
Specifications like the version of the project, operating system, or hardware
Only white list were resorted in https://github.com/txthinking/pac/commit/5944ef79051cd0f0ce8c04947a4e098e97da2950. Before this commit, symbols in all the lists are not ignored when sorting.
Steps to reproduce the problem
The following are merely examples, not real websites.

Add a website in white list addWhite.sh abc.com
Add another website addWhite.sh abcb.com
abc.com will stand behind abcb.com because the dot is ignored.

Possible solution
Since it is more practical to treat all characters equal, a solution has been provided in https://stackoverflow.com/questions/5982531/behaviour-of-gnu-sort-command-with-non-letter-ascii-characters-such-as-dot-or. We can add LC_COLLATE=C before sort in all .sh files starting with add. In my opinion, a better choice is to revert last two commits before modifying .sh files.

Yes. Set LC_COLLATE=C can get traditional sort order that uses native byte values. This is not a functional defect.  I think we don't need to care the old commits. Just modifying scripts, running scripts is enough.

https://github.com/txthinking/pac/pull/13


[feature request] CLI should allow for setting of retention policy

In the current CLI it's not possible to do something like SHOW MEASUREMENTS against anything but the default retention policy.

closing as dupe of https://github.com/influxdb/influxdb/issues/3188


Doesn't scroll when big one cell alone

Hello, found that problem, what is this? my mistake? Scrolling just stop, if there big one cell without 2 small, but i can see it while bouncing collectionview
I like your job, and want to implement in my project, but does it work only with even counts of items?

It should work with any number of items without affecting the scrolling. The only thing it does affect is the layout. I'm not sure what the issue is, you're saying it doesn't scroll but it does bounce so I'm just a bit confused

content of scroll = small one, not big one

Could you make a gif of this in action, it's hard to tell through still images

http://im.ezgif.com/tmp/ezgif-366586186.gif

The way to fix this issue is to go into the TRMosaicColumns and change the following line:
import UIKit
struct TRMosaicColumns {
var columns:[TRMosaicColumn]

var smallestColumn:TRMosaicColumn {

   // return columns.sort().first! <---------------------------------------------! CHANGE THIS

    return columns.sort().last! <---------------------------------------------! TO THIS

}

init() {

    columns = [TRMosaicColumn](count: 3, repeatedValue: TRMosaicColumn())

}

subscript(index: Int) -> TRMosaicColumn {

    get {

        return columns[index]

    }

    set(newColumn) {

        columns[index] = newColumn

    }

}

}

Från: pluckq<EMAIL_ADDRESS>Skickat: den 19 juli 2016 12:54
Till: vinnyoodles/TRMosaicLayout
Ämne: [vinnyoodles/TRMosaicLayout] Doesn't scroll when big one cell alone (#4)
Hello, found that problem, what is this? my mistake? Scrolling just stop, if there big one cell without 2 small, but i can see it while bouncing collectionview
I like your job, and want to implement in my project, but does it work only with even counts of items?

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/vinnyoodles/TRMosaicLayout/issues/4, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AOmtnmmKIWJxDFVy310k_n94PHHJusbCks5qXKzdgaJpZM4JPmyu.

But doesn't the sort() return the array in ascending order? So the first element would ideally be the smallest?

Hi, having the same issue to solve should I use Nathan solution or are you working on a fix ?

Use @Nathan961207 's solution, I haven't been able to recreate the issue so I can't offer a better solution

Fix is working fine thanks

Please release this in cocoapod, Until then we ended up with
  pod 'TRMosaicLayout', :git => 'https://github.com/vinnyoodles/mosaic-layout.git', :branch => 'master'


Vagrantified LibreNMS setup plus other fixes

I'll merge this as it has been proven to work by two different people.


@types/es6-promise  deprecated

Category

[x] Bug

Describe the bug
please remove adding a reference in package.json to @types/es6-promise since it is deprecated "This is a stub types definition for es6-promise (https://github.com/jakearchibald/ES6-Promise). es6-promise provides its own type definitions, so you don't need @types/es6-promise installed!"
Steps to reproduce

generate new project in yo generator
go to package.json
in dependecies is "@types/es6-promise": "0.0.33",
on npm page for this package "This is a stub types definition for es6-promise (https://github.com/jakearchibald/ES6-Promise). es6-promise provides its own type definitions, so you don't need @types/es6-promise installed!"

Expected behavior
this dependency absence probably should be checked the presence of es6-promise explicitly.

It seems to be duplicate - https://github.com/SharePoint/sp-dev-docs/issues/2249#issuecomment-580044282
@johnguy0 your views please

@PrasadKasireddy is correct, this is a dupe and as stated in the referenced issue, will be resolved in the next SPFx version.


HTML

#HTML
##User Story
As a boot camp student
I want a prework to be structured on a webpage
so that I can easily find and read information
##Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git, and JavaScript with associated notes listed

#CSS
##User Story
As a boot camp student
I want a prework to be structured on a webpage
so that I can easily find and read information
##Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I see a dark blue header and footer, and four boxes with a shadow

#JavaScript
##User Story
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
##Acceptence Criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I can see the four topics I learned listed along with a suggestion on what I should study first

#README
##User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
##Acceptance Criteria
GIVEN the prework project repository,
WHEN I view the README for the repository,
THEN I can see a professional README that provides information on the project and how to use it

#Deployment
##User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
##Acceptance Criteria
GIVEN a Prework Study Guide website,
WHEN I visit the website using the URL,
THEN I can access my website from any browser


Fix README links

Now that the project has shifted the README links no longer work.
PRs welcome!

I am checking and doing this.
NP :)

PR done-
https://github.com/MarkPieszak/aspnetcore-angular2-universal/pull/116


Clarify how parameter wait works on ApplicationHost

Currently it is not documented:
interface ApplicationHost {
    val environment: ApplicationHostEnvironment

    fun start(wait: Boolean = false): ApplicationHost
    fun stop(gracePeriod: Long, timeout: Long, timeUnit: TimeUnit)
}

It is not clear whether it will block until the JVM shuts down or will only block until the server managed to start up. Please add kdoc to clarify this.

Added kdoc


server: check overlaps for new region

What problem does this PR solve?
When a region is merged, and then PD receives a stale heartbeat of it for some kind of reasons. It may overlap with some regions and update region tree improperly.
What is changed and how it works?
When inserting a new region, check are there any overlapped regions and compare the version to decide whether the heartbeat is stale or not.
Check List

Unit test

Related changes

Need to be included in the release notes

Fix https://github.com/tikv/tikv/issues/3868

/run-unit-test


refresh is required after removing child (in context menu)

After removing a child there was no update in my screen,
I guess I have to add refresh() at below code :
remove_child.onclick = e => {
if (isRoot) return
mind.removeNode()
mind.refresh();
menuContainer.hidden = true
}

Ah, I've checked it again accoring to your metion and found that
this issue can be reproduced at only Firefox browser (93.x in my case) !

I should use Chrome :)

Ah, I've checked it again accoring to your metion and found that this issue can be reproduced at only Firefox browser (93.x in my case) !

do you have any error information using firefox?


Bot.AvatarURL

How can i get the bot avatar URL?

You need to retrieve user with id being @me or use s.State.User.
After that you use user.AvatarURL("") to get the url ("" - means no size constraint is set).

You need to get bot user. You can either fetch it - s.User("@me") or get it from the Ready payload (it's stored in the State), so s.State.User
After that you use user.AvatarURL("") to get the url ("" here indicates that there no size constraint).

Yup! got it here. Thank you very much


Multiple parts in Response Header

What is the feature you are proposing?
While implementing #3461, I couldn't find a way to set multiple parts in response header.
For partial contents response, a Response may contain multiple parts for partial contents like this:
HTTP/1.1 206 Partial Content
Date: Wed, 15 Nov 2015 06:25:24 GMT
Last-Modified: Wed, 15 Nov 2015 04:58:08 GMT
Content-Length: 1741
Content-Type: multipart/byteranges; boundary=BOUNDARY
ETag: "abc123"
Accept-Ranges: bytes

--BOUNDARY
Content-Type: application/pdf
Content-Range: bytes 234-639/8000

# content of first range (406 bytes)
--BOUNDARY
Content-Type: application/pdf
Content-Range: bytes 4590-7999/8000

# content of second range (3410 bytes)
--BOUNDARY--

Another example of multiple parts is multipartform data.

Hi @exoego
We may use FormData for a body of Response? Response can accept an instance of FormData: https://developer.mozilla.org/en-US/docs/Web/API/Response/Response
And FromData will add proper boundaries.
app.get('/', (c) => {
  const data = new FormData()
  data.append('foo', 'bar')
  return new Response(data)
})

Thanks.
I was able to use ReadableStream to set multiple parts in response body, in https://github.com/honojs/hono/pull/3461 for future reference


Modify involve_yishuv_name to accident_yishuv_name in widgets filters

@ziv17 can you please review?

@ziv17 merging in order to fix bugs but waiting for your review (and will fix later if needed)


Automate AUR package release

When a new release is tagged, automate the process of updating the PKGBUILD version and also version it inside this repository.
Reference:

https://github.com/tectonic-typesetting/tectonic/issues/54
https://docs.travis-ci.com/user/deployment/releases/

I created this issue to track work and discussion on this matter, will work on it when possible.

Thanks for tracking this, @badosu (and all your help on Arch) ! The approach tectonic is using looks pretty legit. Let me know if you need anything from me, or if you need any of the travis build settings tweaked.

@bryphe I noticed that the release tag for 0.2.10 has an -recovery appended. If we are going to automate this we'll have to use consistent names for the release tags. Noticed because I had to change the PKGBUILD manually for this.

Sorry about that @badosu , I keep making your life difficult with the AUR repo... I'll switch to using a consistent release tag, and avoid using a -recovery tag in the future (I'll just bump the version).
I'll release a 0.2.11 build shortly with proper naming convention, that we can stick with moving forward.

Don't worry, this is not only for AUR but for any automation done by other actors.

Right, it actually made it a pain updating the README.md with download links too 😞

FYI, I just published v0.2.11 which has a consistent naming schema.

Thanks @bryphe, I was able to make the upgrade package to v0.2.10 anyway, next release I'll use the new schema

Sounds great, thanks @badosu !

@bryphe First step should be to include the code for packaging it, then automating it later, where do you think would be a good place to put it?
I thought of dist/arch or something like that any ideas?

Sweet! If there are scripts or code to run, maybe those could live in build/aur? Alternatively, there's a scripts folder. Would either of those work?
Today the stuff in the dist folder is solely built files (output from the various packaging strategies). I do a lot of rimraf dist so it might throw off my workflow if we have checked-in files there 😄

@badosu I'm on Arch and I'd be willing to help out with this task, but I've never deployed to AUR before. You linked Tectonic and I was checking out their deploy script. And obviously we'd need to update the travis.yml. What else?

From #2089, it looks like the AUR package hasn't been updated for the latest release, is it worth waiting for the PR, up manually updating for now?

Oh, I updated on the same day locally but forgot to push, fixed now. Thanks!


Improve Design and Layout

(This is intended to be an introductory issue, teaching new people how to use the build system)
Some options for making improvements are:

Improve the display of information on the help page.
Improve the organization of the options page on the Chrome extension.
Improve the metadata section.
Anything you don't like!

I am intentionally being vague in what can be improved since you are new to the project and will have better ideas of what needs improvement than someone who has already contributed. If you want to fix something specific, then I suggest you move the information block so it snaps to the footer of the page instead of floating up to meet the content. You can see this on the "New Message" page, when you make the window tall.
You may need to read about Twitter Bootstrap to make changes. Bootstrap is a "responsive" library, meaning it helps change the layout of the page in response to many different screen resolutions.

Redesign of Options page.

Reasons to change:

Felt there were only 4 options and people mostly browse on 15" inch to 17" and they shouldn't scroll just for 4 simple options.
Symmetry influenced by homepage (the icons).

Some more suggestions:

Use of Switch or Toggle button for changing state of Privly button. http://www.bootstrap-switch.org/examples.html

Hi @prastut! I think this is an improvement, so long as you implemented it with Bootstrap's responsive columns. Want to open a PR?

@smcgregor I would love to but I am facing a little difficulty in understanding the workflow. I will elaborate the steps, correct me where I am wrong.

I first forked and cloned the privly-chrome repo because I wanted to work on chrome development for Privly. Got the local extension setup and working.
Later I realized the issues I intended to work upon where in privly-applications repo. So I forked and cloned it and started working on it.
I realized that privly-applications alone can't build the full chrome extension. Nevertheless started working using the following procedure

Edited the particular subtemplate and not the HTML (as mentioned in the privly dev pages).
Run python build for chrome to see the changes.

I think I have some misunderstanding since the dev pages say to clone the platform related repo (in my case chrome) recursively.

You should clone one of the projects that incorporate privly-applications as a submodule. When you use the --recursive flag, privly-applications will automatically be cloned into a folder within the repo (privly-applications is the name of the folder within privly-chrome). At this point you will want to change the remote of the privly-application module to be the remote of your fork on github of privly-applications. Now you can commit to your local copy of privly-applications and push it to your fork so you can make a pull request. Does this make sense?

@smcgregor Makes sense! Thanks :D
I cleaned my branch but had a doubt. If I build the system, there are a lot changes shown amidst the ones I actually did. Is this normal?

@prastut That is normal.  Do not commit any built html files, just the templates.

Please review PR #357

You can make more templating changes if you like, but it is generally good to move on to the higher levels if you understand what is happening with the lower ones.


:vimgrep can run slowly when ALE is enabled

Information
VIM version
NVIM v0.2.2
Build type: Release
Operating System: Mac
:ALEInfo
Current Filetype:
Available Linters: []
Enabled Linters: []
Linter Variables:
Global Variables:
let g:ale_cache_executable_check_failures = 0
let g:ale_change_sign_column_color = 0
let g:ale_command_wrapper = ''
let g:ale_completion_delay = 100
let g:ale_completion_enabled = 0
let g:ale_completion_max_suggestions = 50
let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%code: %%s'
let g:ale_echo_msg_info_str = 'Info'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_history_enabled = 1
let g:ale_history_log_output = 1
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_filetype_changed = 1
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'always'
let g:ale_lint_on_insert_leave = 0
let g:ale_linter_aliases = {}
let g:ale_linters = {'javascript': ['eslint']}
let g:ale_linters_explicit = 0
let g:ale_list_window_size = 10
let g:ale_loclist_msg_format = '%code: %%s'
let g:ale_max_buffer_history_size = 20
let g:ale_max_signs = -1
let g:ale_maximum_file_size = 0
let g:ale_open_list = 0
let g:ale_pattern_options = {}
let g:ale_pattern_options_enabled = 0
let g:ale_set_balloons = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 1
let g:ale_sign_error = '⦿'
let g:ale_sign_info = '⦿'
let g:ale_sign_offset = 1000000
let g:ale_sign_style_error = '⦿'
let g:ale_sign_style_warning = '⦿'
let g:ale_sign_warning = '⦿'
let g:ale_statusline_format = ['%d error(s)', '%d warning(s)', 'OK']
let g:ale_type_map = {}
let g:ale_warn_about_trailing_blank_lines = 1
let g:ale_warn_about_trailing_whitespace = 1
Command History:
What went wrong
when ale is loaded, vimgrep searched text so so so slowly, and there's another tmp window in current window, this is my snapshot.

when i remove ale from init.vim, vimgrep searched fastly, and without tmp window.
Reproducing the bug
Steps for repeating the bug:

open vi in a project folder
:vimgrep /some text/ **

Any clues on this problem? It is extremely slow compared to having ALE disabled.
I assume it is linting every file that is being searched. I noticed that setting 'ale_lint_on_enter=0' seems to have no effect, ALE always lints every buffer on open. Perhaps it is related to the problem.

I think this could be fixed by the fix proposed under https://github.com/w0rp/ale/issues/1619

I'll fix setting the option after ALE is loaded, as mentioned in the other issue. You can disable linting on enter today by setting the option before ALE is loaded, which is how it's intended to work. I recommend using denite.vim instead of :vimgrep, which runs in the background.


Raise bug

integrate with Zen Desk to allow users to report issues.

Can one of the admins verify this patch?


New package: OptEinsum v0.0.1

Registering package: OptEinsum
Repository: https://github.com/mofeing/OptEinsum.jl
Created by: @mofeing
Version: v0.0.1
Commit: 2d79313f1391a2c11b8e6aba0d7c24d36507738a
Git reference: HEAD
Description: Julia bindings to opt_einsum package

Please, close this PR as I changed the package name as suggested to OptimizedEinsum.
Continue in #65494.


[RFC] Add --check option

I've made a --check option that ensures that prettyprint(file) === prettyprint(prettyprint(file)). The code is not good for commit but it detects some good things to fix :)

nuclide: https://gist.github.com/vjeux/5b8516202113918de051a0a085ba52e6
react: https://gist.github.com/vjeux/2eeac7e9890c3c3a232bbe366d33523e
react-native: https://gist.github.com/vjeux/e1bfd5b8aef9f2196d8a7c28e672953c

Cool, thanks! I was thinking of using --check as the option for checking if all files are formatted, and exiting with a non-zero status code if not. That would be used in CI and such.
This command is essentially just for us developers, no? I wouldn't want to encourage users to use it because it's going to be a lot slower than pp(parse(file)) === file. If so, maybe we should rename this and make it an undocumented option?

Oh yeah, this is only for developers of prettier to ensure that we are doing correct thing. Having a different name and making it undocumented is fine with me :)

What do you think about making a separate command entirely? I don't love that this adds a bunch of code the the official CLI that's just for us, and complicates maintenance of the CLI. I don't care too much about this code, but I do care about the code around it that all users use. There's not much code for extracting out the files to run and running them through the printer, so we could duplicate that in another command that only we use. What do you think?

I'll just keep it in my branch. Good news is that in the next few days we won't need it anymore since everything passes :p

Sounds good. Something like this is most useful in the Jest testing, and have the AST diffing there, but we could probably switch to pretty-print compare and dump in a bunch more test suites. Then it's automated too.


Add a test for GC.compact for Ruby 3.0

This helps flag global pointers that have moved via the compacting
garbage collector in Ruby 2.7 and up.

Hi @stanhu,
[...]

This helps flag global pointers that have moved via the compacting
garbage collector in Ruby 2.7 and up.

Nice!
Do we actually have this problem? Well, I suppose, we are going to find out!

After having a look at what the test does a question: would a short-lived run during testing be enough to trigger a potential issue? I suppose, the "failure" of this test would be a dangling reference and therefore a Ruby crash. I am just wondering whether there is enough time to trigger any issue. :)
Perhaps finding a way to manually trigger a problem, like what @tenderlove did in few other projects, would be something we could also try.
Krzysztof


Is possible skip requested element?

For example, if loaded or requested element has some class, dont append it, just skip and go next. Is it possible?

One solution is to add a specific class to items that should be displayed, and use this in append
append: '.post.addable'`

Another solution is to write you're own load event handler that selects and adds the desired content.


fix d2J_dX2_temp(0,5) element

Hello and thank you very much for the covariance of the ICP.
I need this covariance  for a SLAM system and I study this code and your paper.
I notice that element d2J_dX2_temp(0,5) reuses d2J_dzdx instead of d2J_dcdx.
It seems like a minor mistake.
Tavoularis Nikolaos
University of Crete, Forth

Thanks tavu.
I was having negative elements in my diagonal elements and that was the cause.


package is a reserved word

Did something recently change to make this crash? We use jade, which uses with, which uses acorn. Without updating anything, our code started breaking in our test environments, where we do a fresh install every time. Or local dev environments were fine. Finally I tried deleting jade and doing a fresh install and then I was able to see the error on my local. The world of subdependencies can be very hard to debug.
SyntaxError: The keyword 'package' is reserved (740:10)
    at Parser.pp.raise (/app/node/app/node_modules/jade/node_modules/with/node_modules/acorn/dist/acorn.js:1021:13)
    at Parser.pp.parseIdent (/app/node/app/node_modules/jade/node_modules/with/node_modules/acorn/dist/acorn.js:732:240)
    at Parser.pp.parseBindingAtom (/app/node/app/node_modules/jade/node_modules/with/node_modules/acorn/dist/acorn.js:1136:19)
    at Parser.pp.parseVar (/app/node/app/node_modules/jade/node_modules/with/node_modules/acorn/dist/acorn.js:1987:20)
    at Parser.pp.parseVarStatement (/app/node/app/node_modules/jade/node_modules/with/node_modules/acorn/dist/acorn.js:1883:8)
    at Parser.pp.parseStatement (/app/node/app/node_modules/jade/node_modules/with/node_modules/acorn/dist/acorn.js:1683:19)
    at Parser.pp.parseBlock (/app/node/app/node_modules/jade/node_modules/with/node_modules/acorn/dist/acorn.js:1938:21)
    at Parser.pp.parseStatement (/app/node/app/node_modules/jade/node_modules/with/node_modules/acorn/dist/acorn.js:1689:19)
    at Parser.pp.parseFor (/app/node/app/node_modules/jade/node_modules/with/node_modules/acorn/dist/acorn.js:1961:20)
    at Parser.pp.parseForStatement (/app/node/app/node_modules/jade/node_modules/with/node_modules/acorn/dist/acorn.js:1770:17)

In both ES3 and in ES5+ strict mode, package is indeed a reserved word. How are you invoking acorn.parse and which language version are you trying to parse? And what value are you passing the allowReserved option?

Yeah the obvious fix is to change package to pkg, which we did.
We are using jade, which is using with (https://github.com/ForbesLindesay/with), which is using acorn. My guess is one of the sub-dependencies got updated on a fresh install, even though we didn't change the primary dependency versions. Either Jade got a newer version of with, or with got a newer version of acorn.

Yeah the obvious fix is to change package to pkg, which we did.
We are using jade, which is using with (https://github.com/ForbesLindesay/with), which is using acorn. I see from the link above that this is from with using the latest version of acorn.

@jackspaniel It was because of this commit - https://github.com/ForbesLindesay/with/commit/0ef234b62e9a6a674e129122efd896a0824e0a44 - where @ForbesLindesay sets sourceType: module so that code is treated as ES6 Module Code which is always strict.
Closing this as not issue of Acorn.


Fixes and improvements related to Linux Kernel header mounts on other Linux distros

Those are various improvements related to Linux Kernel header mounts on other Linux distros, specially getting sysbox to work on Arch:

Commit 1: Fix: longestCommonPath should not truncate a path component

This is just a fix for a very very low impact issue I found while manually testing various scenarios for Linux Kernel header mounts, as far as I know it does not have any impact on any supported configuration, but it's better to leave it fixed to avoid future issues with other distros.

Commit 2: Create intermediate paths when symlinking Linux kernel headers

This fixes an issue launching containers which only happens on very obscure scenarios on supported/typical configurations, but which happens on Arch (after merging "Add Linux Kernel header path for Arch Linux" from sysbox-libs) when launching Alpine-based containers.

Commit 3: Don't fail launching the containers on host kernel headers not found

This is a functional change to facilitate people getting basic Sysbox functionality to work on other distributions, if the kernel headers on the host can not be found, it is a warning instead of an error which prevents launching the containers.
I ran the test-mgr tests and they all passed.

I agree, the code and messages are more readable with the changes you comment. Changed and changed.


ensurepath should ensure pipx's binary path is in PATH

Describe the bug

Our install directions in the absence of Homebrew direct the user to install pipx using pip to the python user install directory.  But this directory's bin/ or Scripts/ subdirectory may not already be in a user's path.
We should use python3 -m pipx ensurepath to also ensure that the path to the pipx script itself is in the user's path.
Ref: https://github.com/pipxproject/pipx/issues/421#issuecomment-646243397

Duplicate of #371


Split up utilities into smaller modules

The only way I've found to sanely, and safely, be able to selectively turn colors on/off is with a custom Exception type per error type. That means adding quite a few classes, which I'd rather not have in Config, as it would diminish the visibility of the most important parts.

Codecov Report

Merging #10 (8e07fe3) into v1.x.x (0cc888d) will not change coverage.
The diff coverage is 36.00%.

@@           Coverage Diff           @@
##           v1.x.x      #10   +/-   ##
=======================================
  Coverage   55.69%   55.69%
=======================================
  Files           2        4    +2
  Lines         158      158
=======================================
  Hits           88       88
  Misses         70       70

Flag
Coverage Δ

unittests
55.69% <36.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

source/agora/config/Config.d
58.46% <ø> (+3.62%)
:arrow_up:

source/agora/config/Exceptions.d
26.31% <26.31%> (ø)

source/agora/config/Utils.d
66.66% <66.66%> (ø)

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 0cc888d...8e07fe3. Read the comment docs.


Add remove export command.

Add editorconfig file.
Add remove export command.
 I think editorconfig change the indent behavior.

ah yeah.. can you remove the editorconfig then? it conflicts with how go is formatted, so we shouldn't be using it.

@nlf I removed .editorconfig. Could I ask why it conflicts with how go is formatted? It just update your editor config settings. Github will load the config and change display format of files.

because go fmt formats your code with tabs, and the .editorconfig was telling editors to format the code with 2 spaces instead

@nlf You missing some point. I set golang files using tab with default 2 indent size not 2 spaces instead.
https://github.com/appleboy/dlite/commit/31028b635851fb16c136bb58b73740f3efe10426#diff-1e70daafb475c0ce3fef7d2728279182R41


linux: mounts: document bind mounts

We have no examples of how a bind mind from the host works, we need to fix this.

This is done and pushed to master now


Wave file audio compression

Currently wave files (.wav) aren't detected or processed. LZMA filters can help for 16-bit or 16-bit stereo audio files, but this doesn't work for embedded files. The lossless audio compressor wavpack can be used to compress audio data in this case and achieves much better ratios.

So, this issue involves two parts, right? (a). Detection of .wav files, and then (b). Compression of .wav files. It sounds like wavpack can be used for (b), but does it help us with (a)?
Also, if I am understanding this correctly, that means that the output stream will be partially compressed with LZMA, and partially compressed with wavpack. Is that okay? Does the .pcf format have support for that?

Luckily, part (a) is not very complicated as RIFF WAVE is easy to parse (although there's some ambiguousness, e.g. in the order of chunks). My current plan is to do the default first (WAVE-PCM), a bit of additional verification and to check additional nice-to-haves in later versions. I already have a proof-of-concept project for (b), so the implementation of this isn't as far away as it might seem.
The output stream situation is similar for JPG streams (packJPG) and zLib streams (preflate) - these both use an arithmetic coder, so their output is compressed. LZMA receives everything as one big output stream without knowing these details. That's not optimal since the compressed output will most likely get a bit larger. On the other hand, this gives LZMA the chance to de-duplicate in case of identical compressed output.

@schnaader Any news on this?

I'll start a branch where I will integrate my proof-of-concept in March.

Thanks! Looking forward to it


Support (Discord) reply context in IRC

Is your feature request related to a problem? Please describe.
Discord replies have no context in IRC (even that they ARE a reply), leading to confusion.
Describe the solution you'd like
Discord replies -> IRC should include some level of context: that it's a reply at all, reply to a particular user, reply to a message at a particular timestamp, or the beginning of the parent message.
Additional context
Quick and dirty pseudocode if there's interest in merging a tested PR:
In https://github.com/42wim/matterbridge/blob/master/bridge/discord/handlers.go#L85
In
    // Add our parent id if it exists, and if it's not referring to a message in another channel
    if ref := m.MessageReference; ref != nil && ref.ChannelID == m.ChannelID {
        rmsg.ParentID = ref.MessageID
    }

(MessageReference is just an id, ReferencedMessage has the actual content)
I would do something along the lines of this (but better typed :p)
DESIRED_SNIPPET_LENGTH := 25
DISCORD_PARENT_CONTENT := "discord_parent_content"
    // Add our parent id if it exists, and if it's not referring to a message in another channel.
        // Also, include a snippet of the parent to let bridges include it when the id is unusable.
    if ref := m.MessageReference; ref != nil && ref.ChannelID == m.ChannelID {
        rmsg.ParentID = ref.MessageID
                // Proper null safety here for best practice

                rmsg.Extra[DISCORD_PARENT_CONTENT] = ref.ReferencedMessage.content[:DESIRED_SNIPPET_LENGTH-1]
    }

Then in IRC https://github.com/42wim/matterbridge/blob/master/bridge/irc/irc.go#L140
if msg.Extra[DISCORD_PARENT_CONTENT] != "" (or w.e) {
    msg.Text = msg.Extra[DISCORD_PARENT_CONTENT].prettyFormatOrWhatever() + msg.Text
}

Yes please, would be perfect if they looked just like telegram!


Sonarqube resolve aknowledge issue with csrf

We have a problem in the backend_admin, sonarqube has reported a security hotspot.
I just disabled csrf as we were not using it previously. And enable it means that we have to change the CI to bypass the security password for karate testing, but also that we need to change the way to make a request to the API in the front admin in UAT to use the password set.
Once everything is setup we will be able to restrict the URL access to only certains roles and with an authentification required

duplicate with #553


Open Text or OpenText?

I notice both are used in the doco - which should be used and when?

I would assume OpenText always and never Open Text.
Use the reference on OpenText about us page: https://www.opentext.com/about


Allow custom keywords that are not valid JS identifiers (fixes issue #389)

What issue does this pull request resolve?
Custom keywords were required to be valid JS identifiers due to the way they were being used in the generated code.  This prevented the use of keywords with the x- prefix that is required by the swagger API definition spec.
See issue #389 for discussion.
What changes did you make?
This change fixes that by updating the only place that was using them directly as an identifier to use brackets notation rather than dot notation.  This brings the definition of $schemaPath in definitions.def in line with the way the keyword definition is accessed from RULES.custom at the top of custom.jst.
Is there anything that requires more attention while reviewing?
The validation of the keyword name has been changed to allow any name in this change, but this should be updated to either just remove the test or update it to a similar but more relaxed rule to the previous one
before this change is included in the project.
Tests
This updates a number of the tests in custom.spec.js to use non-valid identifiers for the names of some of the custom keywords being tested (primarily by adding x- to the front of the name).
Test Plan:

Run npm test and ensure all tests run and pass

Also docs needs to be updated here: https://github.com/epoberezkin/ajv#addkeywordstring-keyword-object-definition

Thank you!

in 4.10.4


Content: Broken Link in Chapter 18

A user reported that this link is not accessible atm: https://commons.oceanprotocol.com/
Update or remove it.

This was fixed long ago, time to close


⚠ gorzdrav.org has degraded performance

In f87a74d, gorzdrav.org (https://gorzdrav.org) experienced degraded performance:

HTTP code: 200
Response time: 17542 ms

Resolved: gorzdrav.org performance has improved in f15b6cb.


Discussion: Re-design for Plugins

👋  - Here's a general direction for where we can take the GraphiQL. It takes design cues from Storybook JS and VSCode. It aims to have quite a few UI chrome entry points for plugins to be able to work from. This ranges from adding a sidebar button which can either control a sidebar or the whole UI, to toolbar items and tabs on request/reponse.

This is roughly how I see each section:

Notes

This top bar (current query description) is questioned every time I show the design. Its goal is to provide scanability and to give an official "title" to every query. The title is basically either the name of the query + up to 3 vars. If there's no name, we try infer it from the root query/mutation fields. This has 2 main advantages: when you have many tabs with you can know what the page is, when we show summaries of tabs there is a consistent naming.

I've built out a consistent way to show the different types in GraphQL:

I've tried to always use one highlight colour which is used in different shades: which means that can be customized by a consumer. Artsy might have used the purple from it's logo. The default value is the turquoise colour from the GrpahQL logo.

Docs currently lives in the sidebar, as a sub navigation which is pushed on top of whatever is  on the left, in a similar stack metaphor to how iOS does navigation. There's a back button and that pops the stack. I'm open to this changing, it can cover useful UI by doing this. The trade-off is that there needs to be a special section just for introspection of the code

Things missing from design spec:

Run button
Sure button
Error tab?
Explorer style query generation

Things I'm not sold on and can change:

The sidebar reference to a query, feels like it needs to be tighter somehow

Example plugins
Ideally most of the chrome in GraphiQL comes from the plugin infra, that means we can be sure to build a scalable plugin API which works with massive schemas.
Schema
The default sidebar tab: provides an entry point into your schema and allows for deeper introspection of your current query. It probably doesn't need to interact with requests or responses. It provides a way to dig into the documentation of the schema.

History
It would listen to every request made, check to see if it was different from the last one and keep track of the diffs. It would add a toolbar item, which when clicked showed a list of the requests and you can click to set the query string to be one you hit in the past

Stored Queries
It can add a tab to the request toolbar to save queries, as well as having a consistent way to access queries at runtime.
For example Artsy keeps all its stored queries in a JSON file, so the configuration for this plugin could have a function to index or search these queries. The same could be done against the Apollo server automatic persisted queries

Playground
Provides a toolbar icon to the requests section of graphiql which shows a tab which  lets you eval JavaScript against the response. Extra kudos points if that has type completion for that JSON ;)

Sketch file

Awesome work @orta! I support the general direction so will limit my feedback to design for now:
Icons
Icons for technical products can sometimes be tough to understand because they boil down an abstraction to a 14x14 symbol. I wonder if a simpler shape with the first letter inside might be simpler to comprehend at a glance.
Layout
I think there's a visual disconnect between the query panel and the response panel. If they were conjoined (e.g., remove the margin between them) it might make the relationship between them clearer. Same for the query title header and the query/response panel.
Run button It's pretty useful for new users that might be unfamiliar with the UI. I used it in the past and still do.

I love this feedback ❤ - will give that a look

I love the idea of adding tabs to each of the three default panes. we will need to make it so that the default tab is overrideable. do you remember my idea of a diagnostics/console area that slides up from the bottom? similar to vscode or codesandbox? gives a nice birds eye view when you're linting large queries, etc. might be nice for things like response headers, though we can just make that a secondary tab on the right pane.
Also for that legend, i like the icons, and the look and feel is close to the official look and feel which is great. For the legend labels, we need to use spec language - for example i think primitive is scalar?
Plugin notes: The side icon bar and panel region will itself be provided via a plugin. Also, I'd like to encapsulate the default layout in a simple layout component that doesn't need to pass any props, because some people want to override the default three pane layout, or we can just encourage them to compose the existing components however they want. We need to make this capability first order, in documentation/etc because it's where a lot of people get stuck very quickly.

This looks incredible, @orta; thanks for sharing your progress!
Here's a couple of questions/notes I have that I couldn't see the answers to in your designs:
One of the popular things in GraphQL Playground was the ability to browse through the docs and keep the previous layer and a bit open for context - effectively keeping a couple of the previous states of the navigation stack that you mention visible. I think we would like to enable this via a plugin; how do you see that fitting into the design?
Another thing that's commonly requested is a header and URL editor. I'm not sure if this would comfortably fit in the sidebar due to lack of width (URL bar especially). Maybe we could address this with plugin hooks to the "Current Query Description" area; I'm thinking a plugin could do something like adding an icon to the left/right that would open a header editing popover/modal. I'm not sure what this means for usage on mobile though. And perhaps that popover/modal should be baked into GraphiQL for all plugins to use rather than having each reinvent the wheel?
How do you see this mapping to mobile? Storybook is surprisingly good on mobile I discovered a few days ago, so perhaps we could take some inspiration from there.
Just want to say again - absolutely incredible work! :raised_hands:

im thinking the query tab itself could have a network tab and thus the url, verb, headers, etc
the notes about the navigation trail are critical, agreed thanks @benjie

There's some great explorer ideas here: https://github.com/OneGraph/graphiql-explorer/issues/10

There's some great explorer ideas here: OneGraph/graphiql-explorer#10

The explorer seems like it would fit really well as a plugin in the leftmost column.
We also have a code exporter plugin that would fit well in the rightmost column.

Definitely something we’re planning on!
On Thu, Oct 24, 2019 at 12:27 PM Daniel Woelfel<EMAIL_ADDRESS>wrote:

There's some great explorer ideas here: OneGraph/graphiql-explorer#10
https://github.com/OneGraph/graphiql-explorer/issues/10
The explorer seems like it would fit really well as a plugin in the
leftmost column.
We also have a code exporter plugin
https://github.com/OneGraph/graphiql-code-exporter that would fit well
in the rightmost column.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/graphql/graphiql/issues/978?email_source=notifications&email_token=AAKOFFZK3G3B5CUE2CQ4KHDQQHEIHA5CNFSM4I6T4TKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOECFUG4A#issuecomment-545997680,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKOFFYB3CIXSDDM7JAKWDLQQHEIHANCNFSM4I6T4TKA
.

Do peeps have opinions on these sort of type signifiers?

There's some great explorer ideas here: OneGraph/graphiql-explorer#10

The explorer seems like it would fit really well as a plugin in the leftmost column. I think we've implemented most of the feedback from that issue.
We also have a code exporter plugin that would fit well in the rightmost column.

I plan on introducing this pretty early on actually. I'd like to make the doc explorer and query histories into plugins, as ways of defining what the initial plugin interface should be. the idea is to abstract CM and monaco details enough that addCommand() will translate over fluidly into a transformed experience for 1.0.0

Do peeps have opinions on these sort of type signifiers?

I feel like the middle ones with the square border box are easier to identify than the ones on the right without a square, but there could be a11y issues I'm not aware of. Thanks for digging in on this today @orta! Happy Birthday!

Dark mode please.

In my opinion, The dark mode should be supported. Latest version of Safari, Chrome, Firfox support the CSS media query below:
@media (prefers-color-scheme: dark) {

}

By writing some CSS codes, we can make it support dark mode easily, however, design picture for dark mode is needed.

I'm going to make dark-mode request comment as off-topic, there is plans to support theming and dark mode is effectively a theme

nice, theme-ui has some handy stuff for this

We can actually provide a feature to preview the response in the form of tree like structure for better visualization.
We can actually provide a visual programming tool for writing queries, so that user won't actually have to remember the query attributes

https://github.com/graphql/graphiql/blob/master/working-group/agendas/2020-03-10.md
heres the agenda for the working group tomorrow! we will be discussing this and other topics please open a pr to add yourself to the agenda!

We can add tabs option to Graphiql. This will help help a lot.  When we have to switch between different queries multiple times, it becomes a little complicated to use history or commenting. I did a little changes in @orta proposed UI.

thanks for that! @orta has a design that includes tabs somewhere, and we are working towards tabs support

We can actually provide a feature to preview the response in the form of tree like structure for better visualization.
We can actually provide a visual programming tool for writing queries, so that user won't actually have to remember the query attributes

@Chhekur dont you think treeview structure is already implemented. Look this image

But i think it would be a better approach if we move expand/collapse button with the nodes. But we have to make this feature optional for users through plugins or extensions
I have a code that implements a relatively better treeview. Im looking for a container to view it. Graphiql is using CodeMirror to show response and we cant render html in CodeMirror.
I will make a pr soon

graphql explorer plugin is a great “visual programming tool”. @Chhekur may be referring to a tree view using nodes/edges for json results? we will be providing plugins for handling different result formats , such as json, mdx, xml or yaml (all have been requested), and tabs for displaying reaults visually. any such proposal we can come up with sounds great.
working on the plugin proposal template today!

graphql explorer plugin is a great “visual programming tool”. @Chhekur may be referring to a tree view using nodes/edges for json results? we will be providing plugins for handling different result formats , such as json, mdx, xml or yaml (all have been requested), and tabs for displaying reaults visually. any such proposal we can come up with sounds great.
working on the plugin proposal template today!

Yes I was talking about representation of data in the form of node/edges, it'll be very easy to understand for user


feat(policies): support namespaced affected dataplanes

The policy detail page now looks like this:

There are two tabs [Affected policies] and [YAML].  Affected policies are now in a table instead of a list.
I also removed the search, I understand that this list is likely to be small enough to not warrant a search (previously it didn't even have paging implemented, but it does now). If we do need ?name= search I can implement that in a separate PR.
Support for https://github.com/kumahq/kuma/pull/10428

I switched to a table layout here 👍


Make union value trees lazily generated.

I wanted to put this up to get some early opinions. Note that there's the one API change that happens: the
type param for UnionValueTree is no longer the tree -- it's the strategy. I don't think this should
affect any actual code, but wanted to flag this just in case.
I'll do lazy tuples as well if this looks good.
Closes #143.

This is ready for review now! Some notes:

The overall PR consists of several commits that build on top of each other. The commits are all self-consistent (and should compile at each step) so it may be easier to review each commit separately.
I've included benchmarks and tests. The benchmarks show an 80-97% improvement in perf for large enums.
I believe this doesn't have any API breakages so can be published as a minor update, but I think that's somewhat debatable. Please let me know if you disagree :)
I'm not totally sure if I've gotten the non-std stuff correct or even what the constraints are, so feedback about that would be greatly appreciated!

Thanks again for proptest.

Ah, looks like the doctests are failing because of the std_facade stuff -- did I get it wrong? https://travis-ci.org/AltSysrq/proptest/jobs/529058312#L2058

It looks like the macros currently just assume that std is available and somehow none of the no_std users have complained.
We could probably make std_facade #[doc(hidden)] pub, but I'd say for now you should just use std directly and I'll fix the macros later.
As for the more general case of std vs no_std, my usual approach when developing locally is:

cargo test succeeds on stable
cargo build --no-default-features --features 'alloc unstable' succeeds on nightly

The Travis build tests a number of other permutations for certain edge cases but I wouldn't expect you to run into any of those here.

Huh, I had forgotten that proptest actually uses the macros internally now. I guess you can go ahead and make std_facade accessible.
I generally prefer to do the actual version bumps right before publishing so that the version in the repo matches what's in crates.io, so I'd appreciate it if you removed the version number changes for now. In the changelogs, just change the explicit version to "Unreleased".

Should proptest-derive also use the std facade?

The generated code from proptest-derive probably should use the std facade. But currently we don't have anything testing that the generated code works with no-std so I wouldn't worry about it too much here.

Thanks! I won't make any changes then. Anything else I can do to help with the review?

Hey, just wanted to check in on this :) is there any way I can help?

Sorry about the delay. I was going to take care of this last Saturday but (and I know this'll sound like a "dog ate my  homework" level of excuse) but a lightning strike took out my main dev machine and a bunch of other stuff. I should have things mostly back up tomorrow so I should be able to take care of this then.

Thanks so much! :)

These changes have been published in version 0.9.4 and proptest-derive version 0.1.2.

Thanks again :heart:


Make --fast and --columns mutually exclusives

This works as expected...
net11 # lxc list --columns=nsp --format=csv
clients,RUNNING,2557
jasites,RUNNING,4114
ubuntu-template-zesty,RUNNING,5017

Adding --fast quietly ignores --columns directive.
net11 # lxc list --fast --columns=nsp --format=csv
clients,RUNNING,x86_64,2017/06/30 23:05 UTC,default,PERSISTENT
jasites,RUNNING,x86_64,2017/06/25 22:26 UTC,default,PERSISTENT
ubuntu-template-zesty,RUNNING,x86_64,2017/06/25 15:23 UTC,default,PERSISTENT

I've scripted around this for now + likely best if --fast + --columns work together or an error is thrown saying, they're mutually exclusive.

Yeah, I guess we should throw an error. The help does say that it's just an alias for "-c nsacPt" already.

Apologies. I completely missed the alias not.


cannot resolve module 'fs'

Added lokijs to dependency for my project, and when attempting to build I get "Module not found: Error: Cannot resolve module 'fs'". This is related to the setup by this template as it worked in my old setup...

Adding
node: {
console: 'empty',
fs: 'empty',
net: 'empty',
tls: 'empty'
}
to the webpack.base.conf.js fixes the problem

@runarhk Thanks for sharing this! Can you explain a little more about the implications of a change like this? I understand it's creating an empty mock of these node modules, but after looking at the docs, I'm still unsure why or when this is necessary. I'm also not sure what potential problems mocking these modules could cause (I imagine there's probably a reason it's not default behavior).

Sorry, but I am still learning the loops in webpack. I had a problem, googled it and found a solution that worked for me. I am not able to explain more about the implications, but it would be nice if you guys had a look at it.

@runarhk Thanks for the follow-up! I'm a Webpack power user, but by no means a complete Webpack expert, so I'll leave this open with the help wanted tag until someone can enlighten us. 😃

Since this issue has been stale for a while and no one else has reported it, I'm closing for now. Happy to reopen pending new information or others indicating that it's a problem for them as well.

Still getting this problem as well. I can not use fs !!
Might be on to something:
Actually when npm install after a clean new vue init webpack my-fs-test, I get warnings:
 npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
 npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>

Im my case, I found the solution here:
https://github.com/webpack-contrib/css-loader/issues/447


Update README.md

Fix LinkedIn setting description.

Already fixed it in https://github.com/Arasthel/Ghostly/pull/5


new(vx-responsive): add leading option to resize debounce

:rocket: Enhancements

add leading calls to debounced resize function in all @vx/responsive HOCs and components. This prevents the initial render from blocking, increasing perceived page load speed.

Fixes #753
The gifs below represent a page refresh. I set the debounceTime to 1000ms for demonstration purposes. The Before image shows a 1 second delay before the chart gets rendered on reload. The After image immediately renders the component on reload.
Before:

After:

@Pringels after discussing more with @hshoff, and looking at the rendering implications (this will add an additional render which is likely fine), we think this probably should be configurable via props, could you make that change?
You can test the difference in behavior in this sandbox

@williaster I added the additionial key to props. I set the default value to true, as I suspect this would be the desired behaviour in most cases, but if someone really needs to fine-tune performance they can always opt out.

Awesome, thanks @Pringels 🙏 This should be out in the 0.0.198 release 🔜 .

(marking this as breaking for the release since it will add new behavior, still below 1.0.0 so will be 0.0.198 as mentioned above)


[docs] Extend language tutorial to demonstrate invoke statements

We should extend the language tutorial to show people how to use a multiplier using an invoke statement.

Good idea!


Added the ability for ldapserver and/or krb5kadmin to be arrays.

Thanks in advance and thanks again for the contribution,


aggregate_trade_iter(): fixed empty resulting set problem

Fixes #341.
When starting from startStr, if the first hour doesn't contain any trades, it will now not crash, but move forward hour by hour until it at least one trade is found or present moment is reached.

Coverage decreased (-0.4%) to 38.301% when pulling 8761faf85402ed09b695ae0467ab44efec0fbac1 on sapph1re:master into 78a64a67cad02ca6397b0b95486b2bc830ae5ef0 on sammchardy:master.

As far as I understand it says that the code is not covered by tests. But this particular part of behaviour has no easy way to cover by a test, as it depends on the data from Binance. So I'll leave it as it is.


Add note about RoutablePageMixin not calling get_context et al

Fixes #6346. The relationship between RoutablePageMixin and the standard Wagtail page serving chain-of-command is a frequent point of confusion (see #6062 for example) - hopefully this clears things up a bit.

@gasman Crazy idea: How about moving the following code out of Page.serve() into a new Page.render() method, then updating the example to show that being used?
    return TemplateResponse(
            request,
            self.get_template(request, *args, **kwargs),
            self.get_context(request, *args, **kwargs)
        )

@ababic Given that the whole point of RoutablePage is to do different things for different URL endpoints, I think the usefulness of funnelling those different functions into a shared render / get_context method is a bit debatable - if we steer people towards that as best practice, they'll end up wanting to know how to pass in extra variables (or use an alternative template) for this one view.
Any abstractions / helpers that we demonstrate in the docs will tend to lead to people using those things unquestioningly, whether or not it actually makes sense for their use-case. I think it's more helpful to tell (and show) people that these view methods work just like Django views, and then they can build their own abstractions on top of that if they feel that's appropriate.

@gasman Okay, I see your point, but perhaps the example help there by also showing a custom route doing something completely different?

@ababic If you can think of something, feel free to open a PR :-)

Superseded by #6370


Add style for blockquotes

Adds a CSS style for rendering blockquotes. The style can be adjusted
using SASS variables.
Fixes codeandmedia/zola_easydocs_theme#9

excellent, many thanks!


Keybinds is not working

The package keybindings is not working in Atom 1.23.3 on Ubuntu 16.04.
Package version is 1.0.2

I will check the atom doc later.


acrostiche in a show rule

it would be neat if you could define a show rule instead of calling #accr functions.
show rules cannot support the following syntax yet but let it be food for thoughts :
show: x if x in accronym_list.map(get_short_version) => {
          if already been used {
                     use short version
          } else { use long version }
}

@Grisely

Originally the acronym call was in a reference (@BIOS for example), which made it much closer to natural writing. I agree that a show rule would be even nicer, but both approaches share the same issue, in my opinion, to try to be smarter than you.
I am not sure I was a show rule to try and guess which word I want to be expanded because there might be a reason why I specifically want the acronym to be in the short version.
I might also want the plural version, and I find it weird to not have a similar syntax for the singular and plural versions.
Finally, one of the main hurdles I had to overcome with the package was how the variables were shared between the main document and the package. I suspect show rules would not play nicely in that regard.
I agree that the syntax could be even lighter, but for now, I did not find a solution that does not compromise on features and predictability of the results. I am, of course, open to suggestions and on the lookout for ways to improve the package.

show rules cannot support the following syntax yet but let it be food for thoughts

This actually works:
#let x = "abc"
#show x: "xyz"
Test abc 123

So it should be possible to define a show rule for each acronym this way.

I might also want the plural version, and I find it weird to not have a similar syntax for the singular and plural versions.

I just want to mention that you can also use the supplement in reference show rules. So that you could have @NN[s] expand to Neural Networks.

Finally, one of the main hurdles I had to overcome with the package was how the variables were shared between the main document and the package. I suspect show rules would not play nicely in that regard.

There should not be much issue in that. You can just return a  "show rule" (ie a function content -> content) that the user has to apply. All global package variables should then still be accessible in that function. Although I haven't tried this out, so maybe I'm missing something.

There's probably no good alternative here because acrostiche has no repository key in its manifest, but in general I would prefer to keep issues on this repository only related to the package management itself and not the packages.

There's probably no good alternative here because acrostiche has no repository key in its manifest, but in general I would prefer to keep issues on this repository only related to the package management itself and not the packages.

A bit off-topic but: Should the repository key maybe become mandatory for future packages/versions? Otherwise, people will probably always create issues here due to the lack of a better alternative.

Not everybody necessarily develops their stuff in a repository though.

Thank you for your ideas. I am adding a final point to better explain my view, and then we can move that to the fork repo: https://github.com/Grisely/packages.
My point is not that it would not be possible but that it could introduce unwanted behaviour to have a show rule trigger on every instance of a work it recognizes.
In the case where the show rule triggers a regex of an acronym and lookup the definition, I am almost sure I can find counter-examples to every possible regex definition of an acronym. So I don't trust a regex to catch my acronyms.
In the case where you define one show rule per acronym, this seems like a burden to put on the user, and that would make the package heavier to use.
Even if it works, what about the case where the first instance is in a table that automatically locates at the top of the page, but you want to keep the acronym short? Do you have to manually escape each instance of the acronym that you want to keep short (kinda defeats the purpose of an automatic acronym management system IMHO).
Finally, for the "s" at the end of the reference, it is indeed possible but the whole purpose of having a plural version of the definition is to be able to have something different than just an "s" at the end (more important in languages other than English where the noun could be at the beginning, like French).
All in all the current solution is, in my opinion, the best compromise between features, practicality, and determinism of the behaviour.


Develop test fixture for single motor pivot demo

The goal of the v0.1 milestone is to develop a demo that combines the motor control with sensor feedback from the mpu-9250.
In order to accomplish this goal we need a fixture to hold the motor at the end of a pivot as well as a pivot joint that can be affixed to the bench.

#29

https://cad.onshape.com/documents/092c9ad021a8f9693cfda00a/w/540c3cb33ba7e44cbc012b26/e/5458e5c9358795ed5e9bfd87

Constructed arm fixture out of cardboard and a dowel rod.

The cardboard was actually too heavy. Once I determine the length of each arm of our airframe and cut them, I'll use one of the arms (carbon fiber tube) to test the single motor pivot.


Error compiling

Hi
I have an error when i try to compile your code.
I'm ussing Arduino Ide 1.8.1
ESP Library 2.3.0
Here the error:
C:\Users\Angel\AppData\Local\Temp\arduino_build_805687\sketch\PZEM004T.cpp: In member function 'bool PZEM004T::recieve(uint8_t, uint8_t*)':
C:\Users\Angel\AppData\Local\Temp\arduino_build_805687\sketch\PZEM004T.cpp:137:37: error: 'class SoftwareSerial' has no member named 'listen'
     ((SoftwareSerial *)serial)->listen();

What version of software serial are you using?

see #14


remove lerna bootstrap

Please makes sure these boxes are checked before submitting your PR, thank you!

[ ] Make sure you follow Element's Contributing Guide.
[ ] Rebase before creating a PR to keep commit history clear.
[ ] Add some descriptions and refer relative issues for you PR.

ci 挂了 还要把 theme default 的依赖拿进来

Done


NaiveDate Field Error

When I add a field of type NaiveDate it shows me the following error
 the trait bound NaiveDate: InputType is not satisfied
what would be the correct way to implement it?
#[derive(InputObject, Clone, Debug)]
pub struct DateFiltering {
    pub eq: Option<NaiveDate>,
    pub gt: Option<NaiveDate>,
    pub lt: Option<NaiveDate>,
}

    |
    | #[derive(InputObject, Clone)]
    |          ^^^^^^^^^^^ the trait `InputType` is not implemented for `NaiveDate`
    |
    = note: required by `federation_fields`
    = note: this error originates in a derive macro (in Nightly builds, run with -Z macro-backtrace for more info)

did you enable the chrono feature?

Yes
use async_graphql::*;
use chrono::{NaiveDate, NaiveTime};

#[derive(InputObject, Clone, Debug)]
pub struct DateFiltering {
    pub eq: Option<NaiveDate>,
    pub gt: Option<NaiveDate>,
    pub lt: Option<NaiveDate>,
}

add chrono feature to Cargo.toml
async-graphic = { version = "...", features = ["chrono"] }


On EDGE browser the function return "true"

Hi,
the module return TRUE for EDGE browser, which in its turn creates bug in airbnb/react-dates.
This issue exist even in https://www.airbnb.com/ when browsing with Edge.
https://www.screencast.com/t/bDGA6Czw

Many windows laptops these days have touch screens. Are you using Edge on a device that has a touch screen?
Also, I'm unable to view your video because it requires Flash. Can you share it in some other way?

Actually I came here because of airbnb/react-dates. I was using the module, and then found out that it is not working correctly in Edge browser on Windows 10. You can go to https://www.airbnb.com/ and just pick a date range, but first try it on Chrome/Mozilla/IE11 then on Edge to compare them. And here is the related issue on react-dates https://github.com/airbnb/react-dates/issues/697.
Thanks.

@arshKhachatryan can you confirm that your device doesn't actually have a touch screen?

Yes, 100% , I am using Lenovo T470, if my laptop has had touch screen, I would have the same problem in other browsers.

@arshKhachatryan I'm unable to reproduce this; can you open up your browser console and provide the results for this code:
[
  'ontouchstart' in window,
  window.DocumentTouch,
  document instanceof window.DocumentTouch,
  navigator.maxTouchPoints,
  navigator.msMaxTouchPoints
]

Thanks!

const chrome = {
            'ontouchstart' in window: false,
            window.DocumentTouch: undefined,
            document instanceof window.DocumentTouch: Uncaught TypeError: Right-hand side of 'instanceof' is not an object,
            navigator.maxTouchPoints: 0,
            navigator.msMaxTouchPoints: undefined
        }
const Edge = {
            'ontouchstart' in window: false,
            window.DocumentTouch: undefined,
            document instanceof window.DocumentTouch: Invalid operand to 'instanceof': Function expected,
            navigator.maxTouchPoints: 2,
            navigator.msMaxTouchPoints: undefined
        }
const EdgeOnPC = {
            navigator.maxTouchPoints: 0
        }

@ljharb I made a little research, and it turned out, that on pc, navigator.maxTouchPoints returns 0, though in my laptop is returns 2, but on laptop my other browsers return 0 for navigator.maxTouchPoints.
I think depending on laptop model, browsers may give different values which I assume is related to the touch-pads that specific laptop, notebook uses.
If navigator.maxTouchPoints equals 2 for not all touch devices, only for those that are not not touch devices like my laptop, I think navigator.maxTouchPoints: 2 case can be put in the code as an exception.

That seems premature; given that the spec says that any touchPoints value > 1 indicates touch support. Is there a chance that your laptop's trackpad has multitouch?

(Also, what's the value of window.PointerEvent in those browsers?)

I'm particularly looking at https://patrickhlauke.github.io/touch/touchscreen-detection/ as an alternative.

Yes my laptop's trackpad has multitouch.
Is there any specific value you want from this window.PointerEvent?

And unfortunately this https://patrickhlauke.github.io/touch/touchscreen-detection/ also detected touchscreen in my EDGE

If it's got multitouch, it's a touch device - I'm not sure there's an issue here (altho it's surprising that Chrome doesn't report it as one)

The confusion from my part is that only the EDGE treats it as an touch device, others do not,

Right - i'm not clear on whether that's an Edge bug, or a bug in those other browsers.

I had the same problem, and we had to fallback to Modernizr's version:
https://github.com/Modernizr/Modernizr/blob/master/feature-detects/touchevents.js

A bit late to the party but there is a confirmed bug in Edge. Not sure if this was the current Edge version when the issue was initially raised.
https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/20417074/

Just updated MS Edge to latest version and the bug is gone. Edge v79+ uses chromium-based engine which works as expected.


CLOUDP-120446: Telemetry - Track Events for All Errors

Proposed changes
Telemetry - Track Events for All Errors

Jira ticket: CLOUDP-120446

Closes #[issue number]
Checklist

[x] I have signed the MongoDB CLA
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have added any necessary documentation in document requirements section listed in CONTRIBUTING.md (if appropriate)
[x] I have addressed the @mongodb/docs-cloud-team comments (if appropriate)
[x] I have updated e2e/E2E-TESTS.md (if an e2e test has been added)
[x] I have run make fmt and formatted my code

Further comments

Filipe, what happens if the error message is very long, or spans multiple lines?
We may want to trim error messages if they are excessive.
I'll experiment to come up with examples...

ready for another look @johansteyn

Felipe, I've been trying different edge cases to verify if errors are being tracked as expected.
If I run "atlas config describe" without an argument, or with an invalid argument the errors are tracked as expected.
But if I delete my config file and run those same commands, the errors are still displayed in stdout but they are not tracked.

Felipe, I've been trying different edge cases to verify if errors are being tracked as expected.
If I run "atlas config describe" without an argument, or with an invalid argument the errors are tracked as expected.
But if I delete my config file and run those same commands, the errors are still displayed in stdout but they are not tracked.

Are they stored in the cache until a new config is created or fully not tracked (lost)?

At the moment all tracking is to the cache (file), and the error is not written to the cache at all (ie. it's lost).
I am wondering if the absence of a config file means it's not able to determine whether or not telemetry is enabled...

Telemetry should be enabled despite the lack of a config file, because I have the environment variable set:
MONGODB_ATLAS_TELEMETRY_FEATURE_FLAG=true

@johansteyn I've just tested and I agree, telemetry is not tracking because our default state is false currently. In other words when config file is not present we haven't saved telemetry_enabled = true at least once so when the system reads it, it returns false. I think this bug requires a Jira of it's own.

I have submitted a separate ticket: CLOUDP-122243


feat: updated route order values

https://lifi.atlassian.net/browse/LF-6497

Isn't that a breaking change? Partner integrations that use those values will break

I think it will be more like a breaking change from the API side. But we can also make it a breaking change in the types, so the users will be aware 🙂


Allow extensions to register their own functions

I am working on a sprite project and want to be able to register extensions that can add their own custom functions. In addition I've changed Env so that a person can override it with their own class and have that class created everywhere (because of CreateChildEnv).
If you like it I will add support for registering extensions into the web.config etc.

Done.


Non-cached mode

Hi!
How I can implement volatile with computed decorator?
Code from Api docs.
value: Ember.computed(function() {
    return OutsideService.getValue();
  }).volatile()

Thanks.

We don't plan to support this here, as the plan is for volatile to merely be a raw es5 getter

@stefanpenner Ok. It's rightly. Thanks.

Maybe some mode with memorize decorator?
What do you think of it? Discussed?

@stefanpenner I just tried to use a raw es5 getter to make what's effectively a volatile CP within a component but found that when the getter code is run this is the raw JS object for the component definition, rather than the run-time instance of the component, thus this.get and this.getProperties are not defined.
The old style syntax of Ember.computed(function() {}).volatile() as per the example above works OK.  Given the syntax of how a component is currently made (using Ember.Component.extend(...)) it makes sense that an es5 getter won't work, and an old style volatile CP will, but it feels a bit icky to have to use old-style computed syntax alongside decorators.
Feels like it would be nice to have a @volatile, at least in the short term

Kind of annoying, but you cannot use the ES6 shorthand for defining getters/setters at .extend time right now.
// does not work
export default Ember.Component.extend({
  get foo() {
    return 'hi';
  }
});

// Works, but definitely not as pretty:
const Thing = Ember.Component.extend({});

Object.defineProperty(Thing.prototype, 'foo', {
  get() {
    return 'hi';
  }
});

export default Thing;


Compute Pseudotime & find terminal states

A CellRank follow up:

Compute pseudotime
Run pseudotime kernel
Find terminal states with GPCCA estimator
Calulate fate probabilities & find features which correlate with fate probabilities

Done. Just need to add this properly to the MIMIC-II vignette.


Ability to query all collections at once & some minor fixes in webhooks

Hi there,
I made some enhancements that I needed.

There was an issue with the webhook url had an empty character in front. Fixed it with trimming the url
If the webhook was a SSL-URL the curl call failed, fixed it
If the webhook fails for some reason - trigger an error
Added the ability to query all collections at once with the API. So Instead of calling /api/collections/get/?field=value you now can also do /api/collections/get?field=value and the api returns all entries that matches field=value in any collection

Best,
Markus

Thanks for the contribution! I'll merge the webhook fixes, but need to think about the query all collections code.

I close this one. to query multiple collections I would recommend using the following addon: https://github.com/agentejo/CockpitQL


Support for the updated Figma embed

Affected design types

[X] figma
[X] figspec
[ ] link
[ ] image
[ ] iframe

Describe the bug
I don't know if this is a very recent change or not. I've just now starting using the figma integration with storybook. I know figma has been going through lots of changes regarding developer mode, making it an additional cost and all... Maybe this is new URL is part of those recent changes.
Right-clicking on a figma variant, select Copy as > Copy link to selection, it gives you a URL that starts with
https://www.figma.com/design/...
Entering this into the figma or figspec parameters, the design panel then displays an error with the URL and is not a valid Figma URL
It appears figma is still supporting the file path, it just forwards you to a design path in the end. So my workaround so far has been to use the Copy link to selection and simply swap out design with file.
Would be nice to update the regex figmaURLPattern in packages/storybook-addon-designs/src/manager/components/Figma.tsx to include design
How to reproduce the bug?

Right-clicking on a figma variant, select Copy as > Copy link to selection. Note, the copied URL starts with
https://www.figma.com/design/...
Entering this URL into a figma or figspec parameters:url definition of a story
The design panel then displays an error with the URL and is not a valid Figma URL

Expected behaviour
Should display figma without an error for a valid url
Environment

[X] Chrome / Chromium / Chromium based browsers
[ ] Firefox
[ ] macOS Safari
[ ] iOS Safari
[ ] Samsung Internet
[ ] Other

Affected versions
8.0.1
Storybook versions
8.0.4

I ran into this today while using FireFox. According to this thread on the Figma Discord server,, it was an intentional change to url structure slated for April 1st.
There's also a Figma community thread where someone reported the same kind of issue a few days ago, which leads me to believe something changed more recently than April 1st, or that the change is being progressively rolled out.

Thanks for hopping on this. Unexpected change is always around the corner...

Is there an estimation till this new link issue is solved?
I tried to change the figma link from 'design' to 'file' but it only works in type 'figma' and i wanted 'figspec'.

As workaround you can use the iframe embed url.
{
    type: 'figma',
    url: 'https://www.figma.com/embed?embed_host=share&url=https://www.figma.com/design/....'
}