Removes deprecated configurations and tables in preparation for 1.7.0 release

Deprecated web.stat.chart.version configuration removed
AgentStat and Traces tables removed from hbase scripts

Codecov Report

Merging #3587 into master will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           master   #3587   +/-   ##
======================================
  Coverage    40.1%   40.1%
======================================
  Files        2186    2186
  Lines       71519   71519
  Branches     9831    9831
======================================
  Hits        28681   28681
  Misses      40098   40098
  Partials     2740    2740

Impacted Files
Coverage Δ

...p/pinpoint/profiler/sender/AbstractDataSender.java
97.05% <0%> (-2.95%)
:arrow_down:

...m/navercorp/pinpoint/test/OrderedSpanRecorder.java
72.11% <0%> (-1.93%)
:arrow_down:

...orp/pinpoint/rpc/server/DefaultPinpointServer.java
79.02% <0%> (-0.35%)
:arrow_down:

...inpoint/profiler/sender/AsyncQueueingExecutor.java
77.17% <0%> (+1.08%)
:arrow_up:

...tor/metric/datasource/DefaultDataSourceMetric.java
78.78% <0%> (+3.03%)
:arrow_up:

...npoint/rpc/server/SimpleServerMessageListener.java
100% <0%> (+20%)
:arrow_up:

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 00287d2...deebc5d. Read the comment docs.


Minor article update

Please use this template to ensure easier processing of your pull request
Category

[ ] Content fix
[ ] New article
[x] Example checked item (delete this line)

For the above list, an empty checkbox is [ ] as in [SPACE]. A checked checkbox is [x] with no space between the brackets. Use the PREVIEW tab at the top right to preview the rendering before submitting your issue.
(DELETE THIS PARAGRAPH AFTER READING)

Related issues:

fixes #issuenumber
partially #issuenumber
mentioned in #issuenumber

If this fixes (aka: closes) or references an issue, please reference it here. This helps maintaining the issue list as it will (1) link the PR to the issue & (2) automatically close the issue when this PR is merged in.
(DELETE THIS PARAGRAPH AFTER READING)

What's in this Pull Request?

Please describe the changes in this PR. Sample description or details around bugs which are being fixed.
(DELETE THIS PARAGRAPH AFTER READING)

Guidance

Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.
Please target your PR to 'master' branch. Released documents are in live branch.
(DELETE THIS PARAGRAPH AFTER READING)

Docs Build status updates of commit 9e3b021:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Community/managing-external-guest-in-SharePoint-vs-Teams.md
:warning:Warning
View
Details

Community/managing-external-guest-in-SharePoint-vs-Teams.md

Line 118: [Warning] Link 'https://docs.microsoft.com/nb-no/microsoft-365/admin/create-groups/manage-guest-access-in-groups?view=o365-worldwide#block-guest-users-from-a-specific-group' contains locale code 'nb-no'. For localizability, remove 'nb-no' from links to most Microsoft sites.

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


Atom Version 0.198.0 (0.198.0) is failing to load fixmyjs

what sort of error are you getting?

@goatslacker Error snapshot attached herewith.

i dont have much knowledge of how the atom editor works, is there a step you need to take to install the fixmyjs module before you can use it?

@goatslacker  Steps are same as other IDEs: Go to settings -> Package - Search Package -> Install


calculate pending changefeed in gc

Changefeed in pending state should block gc safepoint.

/label affects-6.5
/label affects-7.1


chore: update version of canbench

Updates the version of canbench to release it with the change in #47.

cc @jasonz-dfinity


Replicaset

The MongoDB Replica Set installation and creation works consistently.
Both the Replica Set and the MongoDB Server have application templates so they can be deployed from the UI, and are completely configurable.
The next pull request will contain a few tests for the replica set as well as sensors for the replica set as a whole.
And a third will add in simplistic auto scaling.

The Java/src directory should be removed.

The install phase of first-node fails.
These are the only env values defined when viewed in the console:
REPLSETNAME="ReplicaSetName" OPLOGSIZE="4096" SECINDPRE="all" ENAMAJREADCONCERN="false" PID_FILE="/home/users/Mike/brooklyn-managed-processes/apps/EPeDvLBa/entities/VanillaSoftwareProcess_nRBO5698/pid.txt"
However, many more variables are actually needed in this phase.  It looks like they are not getting passed down.

I cannot reproduce the port variable working incorrectly.
All I get is this:
MONGOPORT="27017"
I am testing on the most recent snapshot of Brooklyn.

LGTM -- tested and works on latest Brooklyn snapshot.

Looks good and well done on doing it all in YAML.
How will you handle a change of primary? With the implementation here PRIMARY_NODE is always assumed to be $brooklyn:component("first-node"). We can't assume that this will always be the case. Perhaps we can publish the value MongoDB thinks is the primary as a sensor on the cluster (see rs.status() and replSetGetStatus) and refer to that instead when adding new members to the cluster.
Secondly, we need to reconfigure the cluster when members are removed. I'm not sure how to do that from YAML.

@sjcorbett The value ofPRIMARY_NODE is retrieved from a sensor on $brooklyn:component("first-node") in this manner: $brooklyn:component("first-node").attributeWhenReady("mongodb.rs.primaryNode").  That sensor is actually doing a lookup of the primary node, not just returning the first-node that we've designated.
@d-qoi can this be published on the cluster itself?  IIRC it needs to be on one of the actual nodes so we can run a command to perform a lookup.
We'll need to think more about the reconfig issue.  Does that work need to be in this PR @sjcorbett?

Thanks. In that case, what happens if the entity that was the first node is removed from the cluster?

Reconfiguration doesn't need to be handled in this pr but not sure we can consider replica sets complete until we've thought about it more.

@sjcorbett First node removal and reconfiguration are tasks that are next up for implementing and will be in subsequent PRs. Thanks!


upload fails and wipes bootloader on Trinket 5v 8Mhz

Hi,
I am encountering a problem using PlatformIO to upload a firmware on an Adafruit Trinket 5v 8Mhz.
Compilation ends ok, but upload fails and wipes out the bootloader of the Trinket. Using the Arduino IDE to compile and upload works fine.
Here is the log of the upload using PlatformIO:
BeforeUpload(["upload"], [".pioenvs/trinket5/firmware.hex"])
"/Users/marcpoppleton/.platformio/packages/tool-avrdude/avrdude" -v -p attiny85 -C "/Users/marcpoppleton/.platformio/packages/tool-avrdude/avrdude.conf" -c usbtiny -D -U flash:w:.pioenvs/trinket5/firmware.hex:i

avrdude: Version 6.0.1, compiled on Dec 16 2013 at 17:26:24
Copyright (c) 2000-2005 Brian Dean, http://www.bdmicro.com/
Copyright (c) 2007-2009 Joerg Wunsch

System wide configuration file is "/Users/marcpoppleton/.platformio/packages/tool-avrdude/avrdude.conf"
User configuration file is "/Users/marcpoppleton/.avrduderc"
User configuration file does not exist or is not a regular file, skipping

Using Port                    : usb
Using Programmer              : usbtiny
avrdude: usbdev_open(): Found USBtinyISP, bus:device: 001:016-1781-0c9f-ff-00
AVR Part                      : ATtiny85
Chip Erase delay              : 900000 us
PAGEL                         : P00
BS2                           : P00
RESET disposition             : possible i/o
RETRY pulse                   : SCK
serial program mode           : yes
parallel program mode         : yes
Timeout                       : 200
StabDelay                     : 100
CmdexeDelay                   : 25
SyncLoops                     : 32
ByteDelay                     : 0
PollIndex                     : 3
PollValue                     : 0x53
Memory Detail                 :

Block Poll               Page                       Polled
Memory Type Mode Delay Size  Indx Paged  Size   Size #Pages MinW  MaxW   ReadBack
----------- ---- ----- ----- ---- ------ ------ ---- ------ ----- ----- ---------
eeprom        65    12     4    0 no        512    4      0  4000  4500 0xff 0xff
flash         65     6    32    0 yes      8192   64    128 30000 30000 0xff 0xff
signature      0     0     0    0 no          3    0      0     0     0 0x00 0x00
lock           0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
lfuse          0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
hfuse          0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
efuse          0     0     0    0 no          1    0      0  9000  9000 0x00 0x00
calibration    0     0     0    0 no          2    0      0     0     0 0x00 0x00

Programmer Type : USBtiny
Description     : USBtiny simple USB programmer, http://www.ladyada.net/make/usbtinyisp/
avrdude: programmer operation not supported

avrdude: Using SCK period of 10 usec
avrdude: AVR device initialized and ready to accept instructions

Reading | ################################################## | 100% 0.00s

avrdude: Device signature = 0x1e930b
avrdude: safemode: lfuse reads as 0
avrdude: safemode: hfuse reads as 0
avrdude: safemode: efuse reads as 0
avrdude: reading input file ".pioenvs/trinket5/firmware.hex"
avrdude: writing flash (816 bytes):

Writing | ###avrdude: 4 retries during SPI command
####avrdude: 4 retries during SPI command
####avrdude: 4 retries during SPI command
####avrdude: 4 retries during SPI command
####avrdude: 4 retries during SPI command
####avrdude: 4 retries during SPI command
###avrdude: 4 retries during SPI command
####avrdude: 4 retries during SPI command
####avrdude: 4 retries during SPI command
####avrdude: 4 retries during SPI command
####avrdude: 3 retries during SPI command
####avrdude: 3 retries during SPI command
#### | 100% 0.51s

avrdude: 816 bytes of flash written
avrdude: verifying flash memory against .pioenvs/trinket5/firmware.hex:
avrdude: load data flash data from input file .pioenvs/trinket5/firmware.hex:
avrdude: input file .pioenvs/trinket5/firmware.hex contains 816 bytes
avrdude: reading on-chip flash data:

Reading | ################################################## | 100% 0.07s

avrdude: verifying ...
avrdude: verification error, first mismatch at byte 0x0040
0x01 != 0xcf
avrdude: verification error; content mismatch

avrdude: safemode: lfuse reads as 0
avrdude: safemode: hfuse reads as 0
avrdude: safemode: efuse reads as 0
avrdude: safemode: Fuses OK (H:00, E:00, L:00)

avrdude done.  Thank you.

scons: *** [upload] Error 1
========================================= [ ERROR ] Took 8.36 seconds =========================================

Any idea of what I'm doing wrong?
PlatformIO, version 2.7.1.
Thanks,

Have you tried Upload using Programmer?

Yeay, problem solved!
Thanks! (for the answer and the very short deplay to provide it!)

Please give us a star :star: https://github.com/platformio/platformio/stargazers
Have you tried PlatformIO IDE ?

I use IntelliJ IDEA with Ant scripts calling PlatformIO, I'll give PlatformIO IDE a try. (star given)

Thanks a lot!
Happy coding!


View rule help box clips off the screen

Currently, if the watch window is on the right side of the screen, hovering over the question-mark icon to show the view rule hover-help results in a window that is mostly off-screen and cannot be read. It would be nice if there was a default mechanism for ensuring hover-help always stays within the window so it can be read.
- Casey

Fixed: f808e8ae2987158ae1404b66251a34ac506c4b52


Failed to generate track2 sdk of azure-mgmt-mixedreality

When I generated mixedreality, I got a confusing error. But I checked it actually has this ref.
My config
Errro log:
VERBOSE [2.81 s]: Reading OpenAPI 2.0 file file:///_/azure-rest-api-specs/specification/mixedreality/resource-manager/Microsoft.MixedReality/stable/2020-05-01/proxy.json
VERBOSE [2.84 s]: Reading OpenAPI 2.0 file file:///_/azure-rest-api-specs/specification/mixedreality/resource-manager/Microsoft.MixedReality/stable/2020-05-01/spatial-anchors.json
VERBOSE [2.87 s]: Reading OpenAPI 2.0 file file:///_/azure-rest-api-specs/specification/mixedreality/resource-manager/Microsoft.MixedReality/preview/2020-04-06-preview/remote-rendering.json
VERBOSE [2.92 s]: Reading $ref'd file file:///_/azure-rest-api-specs/specification/mixedreality/resource-manager/Microsoft.MixedReality/stable/2020-05-01/common.json
VERBOSE [2.96 s]: Reading $ref'd file file:///_/azure-rest-api-specs/specification/common-types/resource-management/v1/types.json
VERBOSE [2.96 s]: Reading $ref'd file file:///_/azure-rest-api-specs/specification/mixedreality/resource-manager/Microsoft.MixedReality/preview/2020-04-06-preview/common.json
  Error: $ref to original location 'file:///_/azure-rest-api-specs/specification/mixedreality/resource-manager/Microsoft.MixedReality/stable/2020-05-01/common.json#/components/parameters/accountKeyRegenerateParameter' is not found in the new refs collection

This isn't an autorest.python issue, it looks like it might be an issue further up in core. I'll re-open this in autorest core for you


Fix typo

Hi. There was a trivial JSON tailing comma problem in edition-2, post-02, zh-CN(only). So I fixed that for consistency across languages.

Thanks!

Thanks!


Improve the README.md file

fixes #86
fixes #64

I think some of these sections could be moved to the wiki to keep the README simpler. I could make those page in the wiki and make a separate PR to delete the corresponding sections in the README, if that's okay?

Sure. In that case, nothing is left to do for the current PR. After this is merged, you can go ahead with the follow-ups.


COR-92: Rewrite e2e test with page object pattern [WIP]

Looking good so far!
You may want to merge main into this branch so that you can test the latest version; the CaseType and Case flows have changed a bit.
Feel free to delete the old create-edit-*.spec.js files I created once you have a working analog with the page object pattern.

Looking good :)
Just a couple more things:

Adapt the Case tests to the new template system. Bear in mind, the built-in Cases are currently broken. Perhaps the best solution would be to make sure the Case test always runs right after the CaseType test so that we can ensure the Case form displays the proper fields.
Add a test for the "search and add member" feature on a Team's page

Visit a Team's page
Type a valid name in the search box: ex: "Diddley"
Add it and verify it's been added

Add "edit" tests for Individual, Attribute, Party, CaseType and Relationship
After every "create" or "edit" a checks to make sure the given data was properly saved
Remove the main-pages.spec.js we don't need it anymore

made a couple changes; see latest commits. You may want to double check your tests as some of them aren't passing with the latest changes.
If you're sick of this ticket though, go ahead and merge 😅  we can open tickets to update the tests


Grid docs: Overview page

Acceptance Criteria
REF https://www.figma.com/file/mtARocDBevZmtgEMjb1cJs/2x-grid-overview-updates?node-id=0-1&t=3lBAl6bvJUXpW7K4-0
To do (see spec file above):

[x] Remove resource section (there are currently no relevant Resource links
[x] Update copy under Columns and rows > Fixed grid (it's highlighted)
[x] Update caption under Vertical Rhythm Don't caption (it used to refer to Sketch)

We removed the Max Plus breakpoint from this issue; it needs it's own work stream

Figma file:
https://www.figma.com/file/mtARocDBevZmtgEMjb1cJs/2x-grid-overview-updates?node-id=0%3A1&t=YQEMZfO7e6XLD4I5-1
The three updates are highlighted in magenta.
Text for the second update (fixed grid)

Fixed grid
A fixed grid starts with a fixed unit size from the sizing scale, then tiles and wraps as needed, like text. To employ the 2x concept, once you’ve determined the original box size that you want to use, you can multiply it by two and so forth to create a layout.

Text for the third update (Don't caption)

In Figma, always use “Auto width” in the Text panel to ensure the text box is fitting with the content. Spacer snaps to the text box.


Python wheels fail to build, yet build succeeds?

Step 6/9 : RUN pip install -r requirements.txt
 ---> Running in 369cc7c6b7fb
Collecting biopython==1.66 (from -r requirements.txt (line 1))
  Downloading biopython-1.66.tar.gz (13.7MB)
Collecting numpy==1.14.2 (from -r requirements.txt (line 2))
  Downloading numpy-1.14.2-cp27-cp27mu-manylinux1_x86_64.whl (12.1MB)
Collecting seqmagick==0.6.2 (from -r requirements.txt (line 3))
  Downloading seqmagick-0.6.2.tar.gz (40kB)
Building wheels for collected packages: biopython, seqmagick
  Running setup.py bdist_wheel for biopython: started
  Running setup.py bdist_wheel for biopython: finished with status 'error'
  Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-28ZYgs/biopython/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /tmp/tmp_qrRWDpip-wheel- --python-tag cp27:
  usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
     or: -c --help [cmd1 cmd2 ...]
     or: -c --help-commands
     or: -c cmd --help

  error: invalid command 'bdist_wheel'

  ----------------------------------------
  Failed building wheel for biopython
  Running setup.py clean for biopython
  Running setup.py bdist_wheel for seqmagick: started
  Running setup.py bdist_wheel for seqmagick: finished with status 'error'
  Complete output from command /usr/bin/python -u -c "import setuptools, tokenize;__file__='/tmp/pip-build-28ZYgs/seqmagick/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" bdist_wheel -d /tmp/tmpHc0LqTpip-wheel- --python-tag cp27:
  usage: -c [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
     or: -c --help [cmd1 cmd2 ...]
     or: -c --help-commands
     or: -c cmd --help

  error: invalid command 'bdist_wheel'

  ----------------------------------------
  Failed building wheel for seqmagick
  Running setup.py clean for seqmagick
Failed to build biopython seqmagick
Installing collected packages: biopython, numpy, seqmagick
  Running setup.py install for biopython: started
    Running setup.py install for biopython: finished with status 'done'
  Running setup.py install for seqmagick: started
    Running setup.py install for seqmagick: finished with status 'done'
Successfully installed biopython-1.66 numpy-1.14.2 seqmagick-0.6.2
Removing intermediate container 369cc7c6b7fb
 ---> 40b622df2f9f

From my reading, it seems like this might be due to a dumbly out-of-date version of pip being installed by Debian. (Big surprise.)

The wheels are Python's binary distribution format. I'd rather find the appropriate setup.py flag to just disable their generation entirely?

Would this be suitable to try to accomplish when we migrate to multi-stage builds?

It would replace #85

So… should we do this part first, and then fix it later?

I didn't find any references to not building bdist_wheel in the setuptools documentation, so let's just go with #85's solution


Interact::on_input in async mode doesn't take Session as an argument

The issue is we can't Send+Clone &mut Self for future which will be spawned in handler.
We need to use some kind of mutex but we can't use the one in std because its blocking.
We could chose a tokio implemetnation or async-std or something else and provide an argument as Arc<Mutex<Session>>.
But in such case we bind the user with our chose which is sort of bad.
The possible solution is to ask user to provide an implementation of Mutex via given Fn() -> impl future::Future<Output=&mut Self> .
And I tried to follow this approach but... it didn't worked out.
So I open an issue as a reminder and just in case someone holds some thoughts.
issue #15

wait for #![feature(impl_trait_in_fn_trait_return)]


Form Modification

Hello @danielo515,
Firstly I must say thank you so much for this plugin that you made, it ease my data storing. I don't have any experience in coding either a simplest programming language and I'm not really have lot knowledge in Obsidian but I figured it out how to make it work by try and error. This is my first time to write an issues in GitHub, so if any mistake that I made in the writing I'm sorry.
I'm writing this to ask you about 2 things:

Toggle: true > textArea
Editing the current metadata using form that has been used in creating the metadata

Before that I need to mention that I'm not a native English speaker, excuse my grammar if there's any confusion. If any of my requests below has been pointed before I apologise for overlooked.
Toggle: true > textArea
When creating a form I noticed that the Toggle option didn't have any additional option like when you toggle it on a text area will pop-up for you to fill in. I'm hoping that if you could add (if toggle is true, you can add option under it). For instance I just add under the toggle like this:

Editing the current metadata using form that has been used in creating the metadata
It's like fill in the form but I can edit the form back in the note itself rather overwrite option in QuickAdd or edit the metadata in the note. I'm hoping this feature because sometimes I need to look back in the form for me to add new property in the metadata, I tried overwrite option in QuickAdd but when I add new little data in the form it replace all of the metadata.

Outcome
Thanks to you again @danielo515 for this incredible plugin and you did a great, powerful and easy-to-understand plugin for a person like me. Below is my final test and it worked to create what I want
https://github.com/danielo515/obsidian-modal-form/assets/154692251/12c6fa4b-7e59-4e9a-bb94-4b3aa0f8d58e
Best regards,
Mel

Hello @danielo515 and @melmennn.
I find it super practical to be able to edit the form again. And in the same way, I thank you very much for the modal forms plugin, it is wonderful. Thank you.

Your first request looks a lot like dependent inputs. It means that, based on the value of one input another input is made available or not. I think that is already requested in #225, right? I think you don't mean to only do it for text-areas but for any other input.
Regarding your other requirement, I think it should be doable if you only want to edit the metadata as I already requested (yes, I do feature requests myself) in #165 .
If a more advanced  "edit" is required, I think that is out of the scope of this plugin.
I think the latter is already currently doable if you are willing to write some code, but that may be out of reach of many people.


Electron Cash 3.3 Portable for Windows no longer works with Trezor One

Seems that the Trezor library is missing from the build. Opening a wallet created with a Trezor One now just pops up the error message "Cannot find python library for 'trezor'. Make sure you install it with python3".
Attempting to sign a transaction pops up the error "Handler not found for trezor. A library is probably missing."
Attempting to view an address on the Trezor makes Electron Cash crash with the traceback:
File "C:[...]\electroncash_plugins\trezor\qt_generic.py", line 196, in show_address
keystore.thread.add(partial(self.show_address, wallet, addrs[0]))
AttributeError: 'TrezorKeyStore' object has no attribute 'thread'
Reverting the executable to 3.1.6 makes it work fine again.

This has been fixed by @jhoenicke in a recent PR.  Look for it to be addressed in 3.3.1 release -- or if impatient -- run from github sources today!

PS: Thanks so much for reporting this and sorry it broke!


Update CI config

Run coverage only after successful first job (TRAVIS_JOB_NUMBER=X.1)
Test on rbx-3
Update codeclimate (https://github.com/codeclimate/ruby-test-reporter#upgrading-from-pre-10-versions)

Travis tells that CODECLIMATE_REPO_TOKEN must be set at https://travis-ci.org/dry-rb/dry-logic/jobs/176718501#L211:

Cannot post results: environment variable CODECLIMATE_REPO_TOKEN must be set.

Welp!

thanks @splattael - I'll follow up in master with more tweaks


How to enable streaming output in OpenAIAssistantRunnable?

Checklist

[X] I added a very descriptive title to this issue.
[X] I included a link to the documentation page I am referring to (if applicable).

Issue with current documentation:
How to enable streaming output in OpenAIAssistantRunnable?
Idea or request for content:
No response

Hi @chizm, have you been able to resolve this? Would love to hear if you managed to stream with the OpenAIAssistantRunnable.

Interested. After struggling for some time I've come to the conclusion that currently OpenAIAssistantRunnable only handles polling queries


bower search should make use of specified keywords

Moved from https://github.com/bower/bower/issues/48
Ref: https://github.com/twitter/bower/issues/17#issuecomment-8548167
Like bower search slider would return components with slider in title or keywords.

Query results were improved and bower search slider actually returns useful entries.

It seems that searching in the registry still makes no use of keywords.
The package slider declares image as one of its keywords:
$ bower info slider
bower slider#*                  cached https://github.com/AlanGuo/slider.git#1.0.1
bower slider#*                validate 1.0.1 against https://github.com/AlanGuo/slider.git#*

{
  name: 'slider',
  version: '1.0.1',
  description: '一个前卫，时尚的图片轮播库，提供数种炫酷的轮播效果，适用于时尚的大图轮播网站，使用html5使性能体验达到最佳，支持移动端，而且本库不依赖任何第三方库，轻便易用。',
  main: 'slider.js',
  ignore: [
    '*.jshintrc',
    '**/*.txt',
    'Gruntfile.js',
    'demo/',
    'lib/',
    'dist/fordoc/',
    'README.md'
  ],
  keywords: [
    'slide',
    'image'
  ],
  authors: [
    'alan'
  ],
  license: 'MIT',
  homepage: 'https://github.com/AlanGuo/slider'
}

Available versions:
  - 1.0.1

You can request info for a specific version with 'bower info slider#<version>'

Still bower does not list slider when searching for image:
$ bower search image
Search results:

    is-image https://github.com/sindresorhus/is-image.git
    mn-image https://github.com/minimalist-components/mn-image.git
    mr-image https://github.com/maxiruani/mr-image.git
    uf-image https://github.com/urban/uf-image.git
    imagey https://github.com/fullscreeninc/imagey-filter.git
    p15-image https://github.com/paralelo15/p15-image.git
    imgur-image https://github.com/basicelements/imgur-image.git
    image.php https://github.com/paulbunyannet/image.php.git
    iron-image https://github.com/PolymerElements/iron-image.git
    image-map https://github.com/clarketm/image-map.git
    imagery https://github.com/mach3/imagery.git
    image-swap https://github.com/benjamindean/image-swap.git
    zoom-image https://github.com/osternaudClem/zoom-image.git
    image-mask https://github.com/hejty/image-mask.git
    input-image https://github.com/marcus7777/input-image.git
    escr-image https://github.com/eat-sleep-code-repeat/escr-image.git
    epic-image https://github.com/AnkushD/epic-image.git
    image-card https://github.com/herschel666/image-card.git
    image-type https://github.com/sindresorhus/image-type.git
    blur-image https://github.com/Erichain/blur-image.git
    fill-image https://github.com/arvindr21/fill-image.git
    image-wall https://github.com/vedsmith92/image-wall.git
    silk-image https://github.com/woutervroege/silk-image.git
    image-zoom https://github.com/EllipticalElements/image-zoom.git
    image-crop https://github.com/alexk111/ngImgCrop.git
    psudo-image https://github.com/psudocode/image-zoom.git
    image-razor https://github.com/postalPain/ImageRazor.git
    paste-image https://github.com/redgeoff/paste-image.git
    ImageBox https://github.com/eiweiss/ImageBox.git
    mygod-image https://github.com/Mygod/mygod-image.git

When searching for both keywords (slide and image, I'm not even sure about how to search with two criteria), the search ends up with no result at all:
$ bower search slide image
No results.


PowerShell Command Explorer extension module filter/search

Summary of the new feature / enhancement
With the PowerShell Command Explorer extension in the sidebar, I would Like to see a way to search/filter, similar to how it is in the PowerShell integrated scripting environment. To filter by the module, instead of all the modules being all combined with each other.
Proposed technical implementation details (optional)
No response

It sounds like you're talking about a Visual Code Extension, perhaps PowerShell Commander?
You'll need to file issues in the relevant repository instead (e.g., https://github.com/DocNougat/PowerShell-Commander) - this repo is only for issues with PowerShell (Core) itself.


pactPublish error when I am on step13

yu@ubuntu:~/pact-workshop-jvm$ ./gradlew consumer:pactPublish
:consumer:pactPublish
Publishing Our Little Consumer-Our Provider.json ... FAILED! 401 Unauthorized - Unknown error
:consumer:pactPublish FAILED
FAILURE: Build failed with an exception.

What went wrong:
One or more of the pact files were rejected by the pact broker

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED
Total time: 6.734 secs

need I do this in file gradle.properties :
actBrokerUser=pactBrokerUser
pactBrokerPassword=pactBrokerPassword

after do this , there is still an error like :
yu@ubuntu:~/pact-workshop-jvm$ ./gradlew consumer:pactPublish
FAILURE: Build failed with an exception.

Where:
Build file '/home/yu/pact-workshop-jvm/providers/springboot-provider/build.gradle' line: 46

What went wrong:
A problem occurred evaluating project ':providers:springboot-provider'.

Unauthorized

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED
Total time: 6.391 secs

i know i must sign up on website : https://pact.dius.com.au/register
can I deploy my own service as a broker like this ?

You can use your own broker, you don't need to signup for one. You can run one using docker, just search on docker hub.
You will have to setup the appropriate values in https://github.com/DiUS/pact-workshop-jvm/blob/master/providers/springboot-provider/build.gradle#L46 and https://github.com/DiUS/pact-workshop-jvm/blob/master/providers/dropwizard-provider/src/test/groovy/au/com/dius/pactworkshop/dropwizardprovider/PactVerificationTest.groovy#L19 to match the pact broker you are running

i know , thank you very much


Release 0.4.6

@JuliaRegistrator register(branch=release)

Registration pull request created: JuliaRegistries/General/6735
After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.
This will be done automatically if Julia TagBot is installed, or can be done manually through the github interface, or via:
git tag -a v0.4.6 -m "<description of version>" da89cc3ca62309da4cf3f23f29d670e67e7be14c
git push origin v0.4.6


Console should be shown, if hidden and not docked to a tab, when errors are logged

See this comment for relevance.
I believe this may have been the default behavior at one time.

@kenny-evitt thanks for opening this ticket :)
Just one clarification: I am not sure what you mean by errors, but in my previous comment I was referring to normal output with println rather than Closure errors.
I think that the console should be shown in both cases.

I really really don't want the console to be shown by default for println and friends. (much like I don't want the console in my browser to be shown by default).

Not sure that the comparison between the console of an IDE and the console of your browser makes much sense...
Here we are talking about an environment where developers want to have visibility of what's going on.
In any other IDE I have used before when I press RUN the console is always visible or become so.

@Muffo You should be able to keep the console open in a tab and move the tab to a separate tab group. Then you can see the console output with other tabs open. You should be able setup this as a default by editing your user.behaviors file.
But, more in the LT 'spirit' would be to just eval code in your source files, or open a REPL tab and run or test code as you write it.
But I don't think opening the console if any output is logged to the console – or opening it if it's closed and any output is logged – make sense for most users. If that's what you want, you should create a plugin to implement that functionality.
And I'm sure that LT never opened the console automatically if a non-error is logged.

OK I am happy to open a console in a separate tab, but my point here is that if it is the first time ever you use Clojure and LT and you simply copy and paste this Hello World:
; Clojure
(defn hello [name]
  (println "Hello," name))

You type this and won't see anything happening.
What about an icon somewhere in the GUI at least to highlight that there is something in the console?

@Muffo There is an icon that indicates that something's been logged to the console. In the screenshot below, the "1" highlighted in red indicates that an error has been logged:

In this screenshot, the "2" highlighted in lighter-gray-blue indicates that two non-errors have been logged:

Actually that's perfect!!
I did not notice this before, thanks @kenny-evitt for the clarification :)


Sortable table

Hello,
Please can you help with an information :)
How can i make something like this
http://www.mccran.co.uk/index.cfm/2011/5/15/Combining-JQuery-Datatable-with-drag-and-drop-functions
It about jquery sortable with drag and drop.
Thank's a lot

I resolve this isue with sortable by jquery ui.
Thank a lot

@butoibogdan, glad you sorted this out. Don't have time yet to test this so I can't give much help. :beers:


Fix mix between bold and bright

There is a (common) misbehavior in the color handling process for terminals (both ncurses and ansi).
In effect, one mix bold with brighter, so for terminal that handle bold font correctly (like Kitty for one, but many other do), asking for a brighter font results in a bold font instead.
In reality, a bright font should use an escape code of \e[90+color m; and not \e[30+color;1m` since the latter is for bold attribute (see here).
So this PR fixes this for ANSI driver.
For ncurses, since it's an arcane library, there is no A_BRIGHT attribute (yet?) but a A_DIM attribute instead. However, it does not seem to work (why???)
So in order to fix it for ncurses, I've taken a different approach, and I'm using the facility to reconfigure the color palette instead for a color index. So, it's better since the code is now able to load the theme set in MP and assign a color index of the terminal palette to the exact RGB value in the theme (so no more brighter requirement here).
If the terminal does not support 256 colors (or more), then the default behavior is kept even if it's ugly.

I've found several issues with this patch under OpenBSD:
. In the console, the ANSI driver is severely broken (only a small set of colors are shown, the rest is B/W)
. The curses driver does not compile because A_ITALIC is not defined.
Regards,
Claire

What is the version of ncurses you have ?
Since version 3.7, A_ITALIC was added and it was released in 2013.
Maybe you should upgrade the library to a more recent version.
Concerning the small set of colors in ANSI, I wonder if your terminal supports the brighter color code [90m. This is supported by VT500 series (released in 1993), see here search for Ps = 9 0.
I guess I'll have to add a configure switch/macro to disable "advanced" feature for very antique terminal and/or console, but, on the other side, recent terminal implements these code correctly.
And using bold code instead of bright gives a very ugly output (since everything is in dark color, only the font weight if changing, and it's not very obvious).
So, I don't know what to do, the current code (without this patch) is not usable for me in the terminal I've used (Terminology, Kitty, Konsole), and with this patch it's not usable with your old console and ncurses version.
Can you assert if you can upgrade ncurses version and if you can test in a more recent terminal ?

See PR #17 for a fix for your issue and please comment if it worked for you. Thanks!


Refactor: Use exvcr to record eth/rootchain network requests

:clipboard:  #709
TODO

[ ] Fix skip test for has_token/2 due to ald contract function change
[ ] Fix skip test for get_deposits due to invalid output encoding
[ ] Fix CircleCI where passing in --umbrella breaks the exvcr usage.

Overview
This PR introduces exvcr to record the response we get from  the Ethereum client for testing with OMG.Eth, OMG.Eth.RootChain and the rest of its ilk. This will record our tests and allows us to turn down the service and test against those responses instead of spinning up, and tearing down the geth process each time for each test case.
It also introduces another way for us to run our tests against an ethereum client by setting up a docker service to bring up the client instead of using DevHelpers to bring up and teardown the geth process.
Recording VCR Cassettes with Docker + ExVCR
Spin up the docker instance for ganache/plasma-contracts:
docker-compose -f docker-compose-fixtures.yml up ganache plasma-contracts

This will spin up ganache in a deterministic mode and deploy the ALD contracts from plasma_framework see here
In your test cases, you can specify the pre-determined addresses (see ganache output in docker) in the setup block. Then just wrap your network calls in use_cassette:
test "get_height/1 returns me a number", %{contract: contract} do
  use_cassette "get_height" do
    OMG.Eth.get_height(contract)
  end
end

Changes

introduce exvcr and record geth responses 9e6148fa
Breaks out tests into separate files for each module, e.g eth_test.exs and root_chain_test.exs 9e6148fa
reset Ethereuemex into request counter so that we can have a consistent recording. This changes the DevHelpers and test setup block to explicitly reset the counter to 0. 5d9d9f15 8e38bb97
adds a docker-compose-fixtures.yml to spin up ganache and plasma-contracts. Note, currently dumped the service here and can consolidate it after. 14d009f5

Testing
mix test --only common test/omg_eth/eth_test.exs
mix test --only common test/omg_eth/root_chain_test.exs
# or do it all
mix test --only common

I think the --umbrella flag in the common_coveralls_and_integration_tests is breaking the exvcr usage. 🤔

also on this:

Fix CircleCI where passing in --umbrella breaks the exvcr usage.

I don't have any hints yet, why this would hurt coveralls. Are you able to run CircleCI's invocation locally (or in whichever setup where you have the mix test invocations pass)? That would be more or less these (note the different paths):
mix coveralls --umbrella --only common apps/omg_eth/test/omg_eth/eth_test.exs
mix coveralls --umbrella --only common apps/omg_eth/test/omg_eth/root_chain_test.exs
# or do it all
mix coveralls --umbrella --only common

Also to troubleshoot a bit more, can you run
mix coveralls --umbrella --only common apps/omg_eth/test/omg_eth/eth_test.exs

for elixir-omg/master and see what happens?
Ping me if you get stuck, I'll try to reproduce the problem on my end.

Ha, actually I played around with this and got something.
If you run the coveralls invocations, you'll see that exvcr attempts generate new cassettes under a parent dir (outside apps/omg_eth). This is because coveralls runs in the root dir, not in the app subdir :(.
Hence the econnrefused are coming from attempts to talk to ganache and record the cassettes. Not sure how to make exvcr choose the correct root path.

THIS IS MAJOR 👏 👏 👏  <3 <3 <3

Coverage decreased (-24.9%) to 60.777% when pulling f9435faf87a881c8a3a9f83de76b411ce8c569a2 on achiurizo/exvcr into 3b26fc072fa553992277e1b9c4bad37b3d61ec6a on master.

@pdobacz

how do I actually record the cassettes from scratch? There is a section in the PR description, but I'm not sure if this is complete. I'd assume one would need to bypass exvcr replaying of cassettes and instead have it record them? How are the json files updated in practice

Wrapping the code executing the network request will update the json.  Depending on your matching preference, it will automatically re-record if it does not have an existing record.

related but a bit separate: how do I just run those tests with exvcr entirely bypassed, using geth, parity (or ganache, since it's supported now)?

Haven't tried this but seems like the approach is to pass in another option like:
use ExVCR.Mock, adapter: ExVCR.Adapter.Hackney, options: [clear_mock: true]


v1.5.0 does not compile with 2.4.20

I only replaced /modules/http2 in the httpd 2.4.20 sources. Part of the buildlog:
.\h2_util.c(1524) : error C2373: 'h2_casecmpstr' : redefinition; different type modifiers .\h2_util.h(387) : see declaration of 'h2_casecmpstr'
.\h2_util.c(1524) : error C2491: 'h2_casecmpstr' : definition of dllimport function not allowed
.\h2_util.c(1538) : error C2373: 'h2_casecmpstrn' : redefinition; different type modifiers .\h2_util.h(388) : see declaration of 'h2_casecmpstrn'
.\h2_util.c(1538) : error C2491: 'h2_casecmpstrn' : definition of dllimport function not allowed

And, besides that, the *.dsp has to be adjusted to reflect the removal of h2_task_output.c, h2_task_input.c & h2_int_queue.c. But that is Windows only.

See the PR: https://github.com/icing/mod_h2/pulls
And note that the *.dsp has to have references to h2_bucket_beam.c/obj.

Thanks for the PR, merged.
The dsp is not in this project and the subversion httpd/trunk should have it.

Fixed in current master.


Update Zendesk theme based on designs

We have a design for the Zendesk support center. It can be found here I've included a screenshot below.
The support center in progress can be found here: https://mitxonline.zendesk.com/hc/en-us
Please update the theme to match the proposed design with a few notes

Proposed design

Acceptance Criteria

[x] Match the designs to the InVision mock up
[x] Submit a request link (upper right) will open a page to submit a new support request (xPRO example)
[ ] There are only two buttons. Use the design of the top row of buttons from Invision, but with two buttons rather than three:

[x] The Invision design uses the wrong font. Use fonts that match the rest of the MITx Online site (primarily Montserrat)
[x] The title of page should be Support Center rather than Help & FAQs
[x] Add a Can't find what you're looking for? section, similar to xPRO. Just above the footer.

[x] The horizontal rule should have a background-color of  #c2c2c2
[x] The section background-color should be  #f5f5f5
[x] Clicking Contact Us will open a page to submit a new support request (xPRO example)

@briangrossman There are a few comments:

The Support Center link mentioned in the ticket is restricted and we would need to make it publically accessible. (We probably need to make it public in case we need to access it, I tried with my Kerberos but wasn't successful as well)
(Update) There is an open PR https://github.com/mitodl/mitxonline-zendesk-theme/pull/2 that should resolve most of the footer part.

@briangrossman There are a few comments:

The Support Center link mentioned in the ticket is restricted and we would need to make it publically accessible. (We probably need to make it public in case we need to access it, I tried with my Kerberos but wasn't successful as well)

I believe you are now set up as a Light Agent (your edly address) and should be able to view this. Let me know if you're not.

(Update) There is an open PR style: match the theme footer with MITxOnline App #2 that should resolve most of the footer part.

Great. Yes... that PR should take care of the footer.

Could you try and export the hero background behind search bar, which is added as bitmaps in the Invision, I tried but wasn't able to export that.

I was also unable to do so. I'll work on getting it for you.

@briangrossman Since this PR has been merged. You should be able to deploy the theme from main branch now. Let me know if you see any issues.

Closed when https://github.com/mitodl/mitxonline-zendesk-theme/pull/4 completed.


Suggestion to improve the readme description

The description of openapi-cli talks about "bundling" and that the "startingPoint" is the "root document," but it doesn't say anywhere how the multiple files are at all related. I assume that the root file is supposed to have $ref references to other files, but the readme doesn't say that and there is no example shown. An example and just a little more explanation would go a long way on this.

Hello, @StephenNay. Thank you for your attention and involvement. We will definitely update the README. It was not finalized yet, as before the v1 release the API can change quite substantially. However, now that should not be a case anymore, so it's the right time to get better docs.

I think we'll add these examples primarily by linking to the generator repo (once we release it with the new format).


ut_control: building issues from testing suite

make[2]: Entering directory '/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/ut-core/framework/ut-control'
-e TARGET_LIB [libut_control.so]
find: ‘/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/framework/libfyaml-master/src/lib’: No such file or directory
find: ‘/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/framework/libfyaml-master/src/thread’: No such file or directory
find: ‘/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/framework/libfyaml-master/src/util’: No such file or directory
find: ‘/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/framework/libfyaml-master/src/xxhash’: No such file or directory
find: ‘/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/framework/asprintf/asprintf.c-master/’: No such file or directory
find: ‘/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/framework/libfyaml-master/src/lib’: No such file or directory
find: ‘/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/framework/libfyaml-master/src/thread’: No such file or directory
find: ‘/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/framework/libfyaml-master/src/util’: No such file or directory
find: ‘/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/framework/libfyaml-master/src/xxhash’: No such file or directory
find: ‘/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/framework/asprintf/asprintf.c-master/’: No such file or directory
TARGET [linux]
make[2]: *** No rule to make target '/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/obj/src/test_l2_plat_power.o', needed by 'lib'. Stop.
make[2]: Leaving directory '/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/ut-core/framework/ut-control'
make[1]: *** [Makefile:106: framework] Error 2
make[1]: Leaving directory '/home/xx/git/fast/comcast/code/opensource/rdkv/rdk-halif-power_manager/ut/ut-core'
make: *** [Makefile:73: build] Error 2

Merged as part of https://github.com/rdkcentral/ut-control/pull/13


The base model has the same results when add a peft model?

System Info
My code is:
base_model =[]
peft_model = []
new model = PeftModel.from_pretrained(base_model, peft_model)
However, if I want to use the base model after these, it has the same results with the new_model unless I restart it.
The only method I use to do is create a zero peft_model.
Who can help?
No response
Information

[ ] The official example scripts
[X] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder
[X] My own task or dataset (give details below)

Reproduction
base_model =[]
peft_model = []
new_model = PeftModel.from_pretrained(base_model, peft_model)
res1 = new_model(**input)
res2 = base_model(**input)
Expected behavior
res1 is the same as res2 but I don't want it

PEFT will modify the base model in-place to add the adapters, therefore, the base model will output different results from before applying PEFT. If you need the original output at the same time, you may have to load a separate copy of the base model.

I agree that it can be confusing. The solution you suggested would also be confusing, though, because the base_model and the (peft_)model are not identical. The former is the base model with some in-place modification, the latter is an instance of PeftModel that wraps the base_model and adds some stuff on top. If there was a way to implement PEFT without modifying the base model, that would be ideal, but there are a bunch of technical reasons that make it impossible, or at least extremely hard.

So what I meant was that we just have a function convert_to_peft_model which doesn't return anything. Then it will be less confusing.
However I am getting another problem. I do a deepcopy of the base_model before applying get_peft_model to it. But I get the exact same forward pass result. Here is the code :
config = peft.LoraConfig(
    r=8,
    target_modules=["seq.0", "seq.2"],
    modules_to_save=["seq.4"],
)

base_model = MLP()
orig_model = copy.deepcopy(base_model)
peft_model = peft.get_peft_model(base_model, config)

X = torch.rand((100, 20))
y = (X.sum(1) > 10).long()
criterion = nn.CrossEntropyLoss()

def step(model,xb,yb):
    outputs = model(xb)
    loss = criterion(outputs, yb)
    return loss

step(peft_model,X,y) == step(orig_model,X,y)

MLP() is from https://github.com/huggingface/peft/blob/main/examples/multilayer_perceptron/multilayer_perceptron_lora.ipynb

So what I meant was that we just have a function convert_to_peft_model which doesn't return anything. Then it will be less confusing.

There is such a function, inject_adapter_in_model.

However I am getting another problem. I do a deepcopy of the base_model before applying get_peft_model to it. But I get the exact same forward pass result. Here is the code :

The issue with that code is that by default, applying LoRA does not change the output (some weights are initialized as 0's). If you pass init_lora_weights=False to the config, the results will differ.
Also, in some very rare circumstances, copy and PyTorch tensors may have strange interactions. To be 110% certain, I would actually initialize the original model (with the same seed) instead of creating a deepcopy.

Thank you for the clarification. I hope this discussion will be useful for anyone who faces similar issues.

@iopwsy If this answers your initial question, feel free to close the issue.

Thanks a lot. I got it


Yocto update fixes

Yocto update required two different changes:
Adding support to 64 arm architecture, which required
-- Adding aarm64 macro to gperftools stacktrace.cc
-- Using SYSEVENTFD2 instead of SYSEVENTFD

Building libuv with autogen instead of gyp.

Merging this allows removing 0001-aarch64-arm.patch, 0002-eventfd2.patch, 0003-build-with-autoconf.patch under each target from meta-pelion-edge. These files were introduced in follwoing PR:
PelionIoT/meta-pelion-edge#180

Refer to this link for build results (access rights to CI server needed):
https://edge-jenkins.isgtesting.com/job/test_team-build-maestro/182/

Refer to this link for build results (access rights to CI server needed):
https://edge-jenkins.isgtesting.com/job/test_team-build-maestro/183/

@costanic @mray190 @cmonr I moved this maestro-patch PR to this branch, since it seems that the CI wasn't able to build it from the fork. It still fails, but I'm unable to discern the reason. I also removed the hard-coded host-value for now from this PR. Please check this when you a moment suitable for it, no worries if it takes some more time now.

Refer to this link for build results (access rights to CI server needed):
https://edge-jenkins.isgtesting.com/job/test_team-build-maestro/185/

Refer to this link for build results (access rights to CI server needed):
https://edge-jenkins.isgtesting.com/job/test_team-build-maestro/197/


Release Google.Cloud.BigQuery.AnalyticsHub.V1 version 1.7.0

Changes in this release:
New features

Support public directory self service for Listings/Exchanges (commit b8e1836)
Support Direct Table Access Toggle (Egress GA) (commit b8e1836)

Documentation improvements

A comment for message Listing is changed (commit b8e1836)
A comment for message DataExchange is changed (commit b8e1836)

Created release for Google.Cloud.BigQuery.AnalyticsHub.V1-1.7.0


Allow Flatcar Linux os_channel on AWS

Change AWS optional os_channel variable to represent an AMI channel for a Container Linux derivative
Allow the Flatcar Linux Container Linux derivative os_channel on AWS with flatcar-stable, flatcar-beta, flatcar-alpha
Require values stable, beta, alpha be changed to coreos-stable (default), coreos-beta, coreos-alpha if they were set

Possibly rename the variable to os_image to have a really nice alignment with Google Cloud and Digital Ocean which already support os_image values coreos-stable, coreos-beta, etc.` (though no Flatcar yet). Just a uniform way to pick the flavor and channel, no fuss.

rel: #209

Targeting this for the weekend.


Implement new Concept Exercise: Async/Await

Goal
The goal here is to create a new concept exercise and a new concept from scratch.
Getting started
Here you can read about what Concept Exercises are and how they are structured:

What are Concept Exercises?
Concept Exercises
Concepts

If you have not done so yet, it is probably also helpful to do a couple of "Learning Exercises" (this is how they are called on the site) yourself. You can also look at the code of an existing concept exercise like bird-watcher (concept for-loops) for reference.
Concepts
The following concept needs to be created. You can use the introduction.md file of the concept also as introduction.md file of the exercise. No need to create different content at this point. Additionally, if you want to save some time it is ok to not have an extensive about.md at this point. It can also be mainly the instruction.md content, maybe with some additions you would like to make.

async-await

Learning Objectives
In the concepts the student should learn about the following topics and then practice them in the concept exercise.

Async functions
Await
Relation to promises
Error handling with try/catch/finally
Top level await (incl. a note that it might not yet be available in all environments)

Out of Scope

Repeating details about promises

Prerequisites
The following concepts should be assumed and defined as prerequisites for the new exercise:

promises
errors

Resources
Here some links that might be helpful as a starting point:

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/async_function
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/await
https://javascript.info/async-await

Help
You can choose to do this solo-style, or collaborate with multiple people on this. The suggested approach is to

First accept this issue by saying "I'd like to work on this" (no need to wait for a response, just go with it) and optionally request that someone works with you (and wait for a second person to accept your request).
Use this issue to discuss any questions you have, what should be included in the content and what not and to collect reference material.
Create a PR and set "exercism/javascript" as reviewers. Additionally you can write in #maintaining-javascript that your PR is ready for review. Once you incorporated any critical feedback that the reviewer might give you and the PR is approved, it will be merged by a maintainer.

Is somebody working on it or I could pick it up

@shubhsk88 It's yours if you want it. 🙂

Thanks will start working on it this weekend

@shubhsk88, how is it going on the concept? I would like to pitch in if you are willing? Let me know if I can help. Thanks

Sorry Got stuck with life but will be finishing this up sooner, I will let you know @pertrai1  if I need help.Thanks for the help😅

@shubhsk88 Can you give a short update on the status here? Feel free to create a draft PR in case you want some early feedback on something. Also let us know in case you can't continue working on this for some reason.

@shubhsk88 Since I didn't hear back from you for some month, I will unassign you from the issue so it can be picked up by someone else.

@junedev, I'm free, have other person working in this concept?

I want to work on this.

@SalahuddinAhammed Great that you want to help. I'll assign you to the issue. Please let us know in case you have any questions or decide you don't want to continue working on this.

That's great. I am working on this issue.

Sorry to say, but I will not work on this issue anymore for personal reasons. Please unassign me from this issue.

@rockysingh3 I did not see any commits being added to your PR I a while. Are you still planning to work on this?

Hi, I would like to take this on

@derin-art if you'd still like to work on this, please create a forum post with an outline of your proposed implementation before doing "all the work", to prevent you from having to scrap a lot.


Adding artifacts and logs generated by e2e tool to gitignore

Description of changes:
Adding a gitignore on files downloaded by e2e tool.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Doc links (3x) broken on Deploying ALZ ZTNetwork wiki page

Describe the bug
The three links on this doc page https://github.com/Azure/Enterprise-Scale/wiki/Deploying-ALZ-ZTNetwork#azure-landing-zone-portal-accelerator-deployment-with-zero-trust-network-principles  are broken
Steps to reproduce
1.Check URL above
Screenshots

@JefferyMitchell or @brsteph would you mind taking a look at this and submitting a PR to fix it?

PR #1525 has been submitted to address


Skip entries done > x days/months ago

The API appears to include tasks from all time, even archived ones. Confirm this, and if so, add an option to skip tasks/projects/categories completed more than X days ago.

Checked with the folks at Amazing Marvin to ask how to replicate the filtering in the app, that seems ideal, so hopefully I get guidance.


pull request for e2e test at 02/05/2017 02:45:06

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


Updates Workbox strategies guide to include section on custom strategies

What's changed, or what was fixed?

Updates Workbox strategies guide to include section on custom strategies

Target Live Date: TBD (when Workbox v6 is released(

[ ] This has been reviewed and approved by (NAME)
[X] I have run npm test locally and all tests pass.
[X] I have added the appropriate type-something label.
[X] I've staged the site and manually verified that my content displays correctly.

CC: @jeffposnick @philipwalton

Whoops!
There were 13 warnings that will prevent this PR from being merged. Please take a look, and either fix, or provide a justification for why they can't be fixed.
WARNINGS
src/content/en/tools/workbox/modules/workbox-strategies.md#L319 - Consider adding a "was this page helpful?" widget to your page: https://developers.google.com/web/resources/widgets#helpful
src/content/en/tools/workbox/modules/workbox-strategies.md#L45 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/tools/workbox/modules/workbox-strategies.md#L69 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/tools/workbox/modules/workbox-strategies.md#L90 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/tools/workbox/modules/workbox-strategies.md#L108 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/tools/workbox/modules/workbox-strategies.md#L126 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/tools/workbox/modules/workbox-strategies.md#L150 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/tools/workbox/modules/workbox-strategies.md#L175 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/tools/workbox/modules/workbox-strategies.md#L201 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/tools/workbox/modules/workbox-strategies.md#L230 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/tools/workbox/modules/workbox-strategies.md#L275 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/tools/workbox/modules/workbox-strategies.md#L307 - Common typo found: 'javascript' Should it be 'JavaScript'?
src/content/en/tools/workbox/modules/workbox-strategies.md#L113 - Common typo found: 'admin' Should it be 'administrator'? See: https://developers.google.com/style/word-list#administrator

@jeffposnick - can you take a peek at this and LGTM/merge

This and the other recent PRs from Houssein are on hold until Workbox v6 is released. (The URLs are unversioned, and we try to have the documentation reflect the latest production release.)


Inconsistency between search and reduce

Hello,
I am writing a tool that uses either search or reduce to get a list of documents. The two work differently. search returns an AsyncIterator alright, but reduce returns an AsyncGeneratorContextManager, for which I have to use an async with clause before being able to loop over the results:
if args.path:
    dociter = paperless.documents.reduce(id__in=docids)

else:
    dociter = paperless.documents.search(args.search)

async for item in dociter:
    print(item.title)

This won't work when I provide args.path, but rather dies with
TypeError: 'async for' requires an object with __aiter__ method, got _AsyncGeneratorContextManager

I don't quite understand why reduce can't just be an iterator itself, but I think it would be better to have a consistent way to iterate over result sets returned by the API, rather than having to use context managers at times, and not at others.

Technically, document.search("foo") is a shortcut for
async with p.documents.reduce(query="foo") as docs:
  async for item in docs:
    # ...

I made reduce a context manager as it magically applies to the http-GET methods __aiter__, all and pages, and later built search as a shortcut on top of that. I cannot turn reduce into an iterator for that reason, as it is meant to apply temporarily and to be used with one of the above mentioned methods, which are iterators theirselves in some cases.
Gonna check if creating another iterator class makes sense here, but it has to wait until I am back from holidays. :)

I am not sure I follow, but I've now stopped using search altogether and that's fine.

Back again. Okay, I will close this issue for now. :)


make topic metadata available to functions

Is this a BUG REPORT or FEATURE REQUEST?:
Feature request
What happened:
We have a use case for certain parameters like partitions, offset, keys that are not available in the events object for consumption by functions
What you expected to happen:
Make those parameters available to the functions since they are already present in the controller
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
I have a working fork that we use internally and would be happy to contribute this if it is a desired feature.
Environment:

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"19", GoVersion:"go1.15.2"
Server Version: version.Info{Major:"1", Minor:"15+" GoVersion:"go1.12.17"}
Kubeless version (use kubeless version):
Kubeless version: v1.0.7-dirty
Cloud provider or physical cluster:
AWS eks cluster

I also think this is valuable information, especially for cases where a function cannot handle the message for some reason.
How do you suggest making this information available to the handler? What I had in mind is using the request headers, like in here.

I also think this is valuable information, especially for cases where a function cannot handle the message for some reason.
How do you suggest making this information available to the handler? What I had in mind is using the request headers, like in here.

This is exactly what I have done. Here is a PR


Fully port GatesInBasis to Rust.

Summary
Ports GatesInBasis to Rust. The implementation avoids the prior conversion to DAGCircuit for each control flow block, which should help with performance.
Details and comments
Additional changes:

Adds a PyInstruction::blocks() for passes which need to get the blocks of a control flow operation as native CircuitData.
Adds NodeType::unwrap_operation() for callers who know that a DAG node is an operation.
Makes Target interface public for use in other crates (needed to accept a &Target in a pyfunction).
Fixes some mutability / visibility concerns in DAGCircuit, naming making dag, qubits, and clbits private again.

Includes some changes from #13013 and #13006 which ought to merge first.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

175 of 199 (87.94%)  changed or added relevant lines in 8 files are covered.
4 unchanged lines in 3 files lost coverage.
Overall coverage increased (+0.03%) to 89.207%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

crates/circuit/src/dot_utils.rs
0
3
0.0%

crates/circuit/src/circuit_data.rs
5
14
35.71%

crates/circuit/src/dag_circuit.rs
53
65
81.54%

Files with Coverage Reduction
New Missed Lines
%

crates/circuit/src/dot_utils.rs
1
0.0%

crates/accelerate/src/two_qubit_decompose.rs
1
90.82%

crates/qasm2/src/lex.rs
2
92.23%

Totals

Change from base Build<PHONE_NUMBER>9:
0.03%

Covered Lines:
71641

Relevant Lines:
80309

💛  - Coveralls


[release/6.1] Update to newer Windows build images

Manual backport of #2345 to release/6.1

/azp run dotnet-monitor-ci


Update master to version 1.x

similar thoughts as in the other PR... sorry for the long comment :)
the files install-dev.yaml and install.yaml are not being updated? is that on purpose?
regarding the {OPERATOR_IMAGE} placeholder in deploy/operator.yaml I think it could be nice to get rid of that placeholder and put there the appropiate operator image. I know the placeholder is handy when you are testing your local changes (to use your own image) but the placeholder make the deployment manifests "incomplete" and it's easy for new users to just go ahead and try to do kubectl apply -f deploy/ and find that the deployment manifests don't work out of the box. I know we have the install.yaml for those purposes... but actually the install.yaml is not a perfect solution, I may even vote for remove it in the future, because it can lead to errors because of having the deployment manifests duplicated in the repository... anyway, my point is to remove the OPERATOR_IMAGE placeholder with the appropiate image, in this case quay.io/apicurio/apicurio-registry-operator:1.0.0-dev and whenever we do a release we change it to 1.0.0. wdyt?
about the changes to the OLM files I don't know if it's ok or not, I guess we will see in the future :)

similar thoughts as in the other PR... sorry for the long comment :)
the files install-dev.yaml and install.yaml are not being updated? is that on purpose?
regarding the {OPERATOR_IMAGE} placeholder in deploy/operator.yaml I think it could be nice to get rid of that placeholder and put there the appropiate operator image. I know the placeholder is handy when you are testing your local changes (to use your own image) but the placeholder make the deployment manifests "incomplete" and it's easy for new users to just go ahead and try to do kubectl apply -f deploy/ and find that the deployment manifests don't work out of the box. I know we have the install.yaml for those purposes... but actually the install.yaml is not a perfect solution, I may even vote for remove it in the future, because it can lead to errors because of having the deployment manifests duplicated in the repository... anyway, my point is to remove the OPERATOR_IMAGE placeholder with the appropiate image, in this case quay.io/apicurio/apicurio-registry-operator:1.0.0-dev and whenever we do a release we change it to 1.0.0. wdyt?
about the changes to the OLM files I don't know if it's ok or not, I guess we will see in the future :)

the files install-dev.yaml and install.yaml are not being updated? is that on purpose?

install-dev.yaml has been updated in the Update generated files commits. Is there something I missed? The reason why install.yaml is not updated is because it has to deploy the latest release, so it's only updated during a release process.

regarding the {OPERATOR_IMAGE} placeholder in deploy/operator.yaml I think it could be nice to get rid of that placeholder and put there the appropiate operator image. I know the placeholder is handy when you are testing your local changes (to use your own image) but the placeholder make the deployment manifests "incomplete" and it's easy for new users to just go ahead and try to do kubectl apply -f deploy/ and find that the deployment manifests don't work out of the box.

Is the new approach by using "yq" OK?

I know we have the install.yaml for those purposes... but actually the install.yaml is not a perfect solution, I may even vote for remove it in the future, because it can lead to errors because of having the deployment manifests duplicated in the repository...

I see what you mean, but it allows a nice one-line-command deployment without cloning the repo.

about the changes to the OLM files I don't know if it's ok or not, I guess we will see in the future :)

I'll do a few more changes in the ApicurioRegistry CSV.

the files install-dev.yaml and install.yaml are not being updated? is that on purpose?

install-dev.yaml has been updated in the Update generated files commits. Is there something I missed? The reason why install.yaml is not updated is because it has to deploy the latest release, so it's only updated during a release process.

regarding the {OPERATOR_IMAGE} placeholder in deploy/operator.yaml I think it could be nice to get rid of that placeholder and put there the appropiate operator image. I know the placeholder is handy when you are testing your local changes (to use your own image) but the placeholder make the deployment manifests "incomplete" and it's easy for new users to just go ahead and try to do kubectl apply -f deploy/ and find that the deployment manifests don't work out of the box.

Is the new approach by using "yq" OK?

I know we have the install.yaml for those purposes... but actually the install.yaml is not a perfect solution, I may even vote for remove it in the future, because it can lead to errors because of having the deployment manifests duplicated in the repository...

I see what you mean, but it allows a nice one-line-command deployment without cloning the repo.

about the changes to the OLM files I don't know if it's ok or not, I guess we will see in the future :)

I'll do a few more changes in the ApicurioRegistry CSV.

The install-dev.yaml is now perfect, I forgot the install.yaml had to point to latest release
The removal of the operator image placeholder and your approach using yq is perfect, thank you
and about the rest is ok
Thank you! you are free to merge the PR

The install-dev.yaml is now perfect, I forgot the install.yaml had to point to latest release
The removal of the operator image placeholder and your approach using yq is perfect, thank you
and about the rest is ok
Thank you! you are free to merge the PR


Multi dimensional indexing goes wrong for ListOffsetArray with numpy array content that is in fortran order

Not sure if this is supported, but if i manually construct a ListOffsetArray that uses a numpy array in fortran order as content (happened to me accidentally since the output of some np operations return fortran ordered arrays) then things go wrong when i try multidimensional indexing:
>>> import awkward1 as ak
>>> import numpy as np
>>> offsets = ak.layout.Index64(np.arange(0, 1010, 10))
>>> np_content = np.asfortranarray(np.arange(0, 3000).reshape(-1, 3))
>>> content = ak.layout.NumpyArray(np_content)
>>> loa = ak.Array(ak.layout.ListOffsetArray64(offsets, content))
>>> loa[0][0] # this is fine
<Array [0, 1, 2] type='3 * int64'>
>>> np_content[0]
array([0, 1, 2])
>>> loa[0, 0] # this goes wrong
<Array [0, 0,<PHONE_NUMBER>06304] type='3 * int64'>

The underlying NumpyArray seems to be aware of the fortran order strides and indexing it works as expected:
>>> content
<NumpyArray format="l" shape="1000 3" strides="8, 8000" data="0x 00000000 00000000 03000000 00000000 ... b20b0000 00000000 b50b0000 00000000" at="0x56001c85b610"/>
>>> content[0]
<NumpyArray format="l" shape="3" strides="8000" data="0 1 2" at="0x56001c85b610"/>
>>> content[0][1]
1
>>> content[0, 1]
1

Thanks for catching this! Fortran-order NumpyArrays are supported, since they come for free with NumPy's shape, strides mechanism, which is needed for any sliced NumPy arrays. (This shape, strides thing is very clever! Worth reading about if you don't already know about it.)
As seen in PR #420, there were two errors: the calculation of NumpyArray::bytelength
@@ -422,7 +422,11 @@ namespace awkward {
       return itemsize_;
     }
     else {
-      return shape_[0]*strides_[0];
+      ssize_t out = itemsize_;
+      for (size_t i = 0;  i < shape_.size();  i++) {
+        out += (shape_[i] - 1)*strides_[i];
+      }
+      return out;
     }
   }

which showed up in print-outs of the NumpyArray layout, and NumpyArray::carry, which is used to propagate slices down in __getitem__. Handling the full non-contiguous case in carry would be complicated; I decided to punt for now and just ensure that the array is C-contiguous.
There are quite a few spots like that, in which non-contiguous arrays are allowed as inputs, but they aren't handled efficiently: they're first converted to contiguous and then the operation proceeds. The plan is to get everything working first and optimize hotspots later (i.e. not this year, unless they're particularly egregious). Therefore, if you're using Fortran-order arrays for efficiency, that's not a good strategy with Awkward Array.

Before:
>>> import awkward1 as ak
>>> import numpy as np
>>> np_content = np.asfortranarray(np.arange(15).reshape(3, 5))
>>> np_content
array([[ 0,  1,  2,  3,  4],
       [ 5,  6,  7,  8,  9],
       [10, 11, 12, 13, 14]])
>>> ak_content = ak.layout.NumpyArray(np_content)
>>> ak_content
<NumpyArray format="l" shape="3 5" strides="8 24" data="0x 00000000 00000000 05000000 00000000 0a000000 00000000" at="0x55ff9abd35b0"/>
>>> offsets = ak.layout.Index64(np.array([0, 0, 1, 1, 2, 2, 3, 3]))
>>> listoffsetarray = ak.layout.ListOffsetArray64(offsets, ak_content)
>>> listoffsetarray[1, 0]
<NumpyArray format="l" shape="5" strides="24" data="0 33<PHONE_NUMBER>1488<PHONE_NUMBER>7728 3" at="0x55ff9aeb1e90"/>
>>> ak.to_list(listoffsetarray[1, 0])
[0, 33,<PHONE_NUMBER>3392,<PHONE_NUMBER>7728,<PHONE_NUMBER>3088]

After:
>>> import awkward1 as ak
>>> import numpy as np
>>> np_content = np.asfortranarray(np.arange(15).reshape(3, 5))
>>> np_content
array([[ 0,  1,  2,  3,  4],
       [ 5,  6,  7,  8,  9],
       [10, 11, 12, 13, 14]])
>>> ak_content = ak.layout.NumpyArray(np_content)
>>> ak_content
<NumpyArray format="l" shape="3 5" strides="8 24" data="0x 00000000 00000000 05000000 00000000 ... 09000000 00000000 0e000000 00000000" at="0x55570d3eab20"/>
>>> offsets = ak.layout.Index64(np.array([0, 0, 1, 1, 2, 2, 3, 3]))
>>> listoffsetarray = ak.layout.ListOffsetArray64(offsets, ak_content)
>>> listoffsetarray[1, 0]
<NumpyArray format="l" shape="5" data="0 1 2 3 4" at="0x55570d401e50"/>
>>> ak.to_list(listoffsetarray[1, 0])
[0, 1, 2, 3, 4]
>>> listoffsetarray[3, 0]
<NumpyArray format="l" shape="5" data="5 6 7 8 9" at="0x55570d3fe2f0"/>
>>> ak.to_list(listoffsetarray[3, 0])
[5, 6, 7, 8, 9]

Interestingly, I noticed along the way that NumPy's nbytes doesn't really describe how many bytes a sliced array covers, either:
>>> import numpy as np
>>> import ctypes
>>> a = np.arange(15, dtype="i2").reshape(3, 5)
>>> a
array([[ 0,  1,  2,  3,  4],
       [ 5,  6,  7,  8,  9],
       [10, 11, 12, 13, 14]], dtype=int16)
>>> b = a[:, :-1]
>>> b
array([[ 0,  1,  2,  3],
       [ 5,  6,  7,  8],
       [10, 11, 12, 13]], dtype=int16)
>>> b.shape
(3, 4)
>>> b.strides
(10, 2)
>>> b.itemsize
2

Using the algorithm I implemented for NumpyArray::bytelength, the length of the buffer is (shape[0] - 1)*strides[0] + (shape[1] - 1)*strides[1] + itemsize:
>>> (3 - 1)*10 + (4 - 1)*2 + 2
28

but ndarray.nbytes says
>>> b.nbytes
24

(which is shape[0]*shape[1]*itemsize). If you look at 28 bytes in memory, starting at the data pointer,
>>> np.ctypeslib.as_array((ctypes.c_int16 * int(28/2)).from_address(b.ctypes.data))
array([ 0,  1,  2,  3,  4,  5,  6,  7,  8,  9, 10, 11, 12, 13],
      dtype=int16)

you do need to go 28 bytes out to see everything in b. Internally, NumPy must be calculating the right length in order to copy array slices, but the nbytes they provide is rather naive. (It's the size the array would be if you copied it into a contiguous buffer, not the size that it is currently occupying in memory.)

Thanks a lot for the quick fix! I didn't have a use case in mind where fortran ordering would be used for efficiency - i just didn't notice that i was using fortran ordered arrays as they came out of a numpy operation (np.argwhere). So returning a C-contiguous copy after __getitem__  is perfectly fine.
Indeed the strides, shape logic is quite interesting!


Added font-face

Added font-face to import custom fonts

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

Hi
As there has been no response from your end for a while, we are closing this PR.
Feel free to request this PR to be reopened, if you still wish to make the changes you originally added.  Also, remember to update your fork, so you have the latest version of master in case it has changed significantly.
Happy Coding! ✈


Feature labels disappear sometimes in Firefox

I've noticed labels behave strangely in iD 2.16.0 on Firefox 70. One consistent bug is that all feature labels disappear upon selecting a feature and only reappear upon a redraw, triggered for example by panning the map or resizing the window. Could not reproduce this in Safari.

This can be reproduced in Firefox Nightly 82

This is happening before the click, because when setting a breakpoint on the click, all labels have already disappeared.  Once the selection is made a zoom in/zoom out  or moving the map makes the label reappears while keeping the item selected. Also without clicking a hover a specific label makes it disappear.
the pointer not on top of the label.
<text class="pointlabel-halo point tag-tourism n6630299764" x="705.0164586752653" y="619.2783916816115" style="text-anchor: start;">The Quaker</text>

The pointer on top of the label
<text class="pointlabel-halo point tag-tourism n6630299764 nolabel" x="705.0164586752653" y="619.2783916816115" style="text-anchor: start;">The Quaker</text>

but when selecting a specific item it doesn't add nolabel to all items in the map. So that looks like more a painting issue with SVG?
When selecting it seems to reassign all the labels by rewriting them in the DOM.
This is calling
  function textFunction(t) {
    return function () {
      var e = t.apply(this, arguments);
      this.textContent = null == e ? '' : e
    }
  }

and it is going through each of them… and remove them
  function selection_each(e) {
    for (var t = this._groups, n = 0, r = t.length; n < r; ++n) for (var i, o = t[n], a = 0, s = o.length; a < s; ++a) (i = o[a]) && e.call(i, i.__data__, a, o);
    return this
  }

which is strange because the value is really the text for example e == The Quaker

ah I wonder if it's related to https://bugzilla.mozilla.org/show_bug.cgi?id=725221
@quincylvania maybe just checking if textContent already exists with the same content, and if it does do not overwrite. Maybe that would work.

I can't reproduce this issue using Firefox version 96. Seems like it was either fixed in Firefox or by some other change in iD.


Student Setup: Hide Enroll / Unenroll buttons when not applicable

It's confusing

Courses completed now have button that just says "Mark Course as Not Complete"
Courses that are not completed now have button that just says "Mark Course as Complete"


python2.7下怎么运行例程

莫烦老师您好！
我是初学者，看了您的视频收获很大，讲行特别好，非常感谢您 的分享！
我用python2.7运行您的例程tutorials/tensorflowTUT/tf14_tensorboard/
会报错，不知道该怎么改。报错如下：
Traceback (most recent call last):
File "/home/py/文档/practice/tensorflow_Visualization2.py", line 46, in
writer = tf.train.SummaryWriter('logs/', sess.graph)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/summary_io.py", line 82, in init
self.add_graph(graph_def)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/training/summary_io.py", line 128, in add_graph
event = event_pb2.Event(wall_time=time.time(), graph_def=graph_def)
File "/usr/local/lib/python2.7/dist-packages/google/protobuf/internal/python_message.py", line 519, in init
_ReraiseTypeErrorWithFieldName(message_descriptor.name, field_name)
File "/usr/local/lib/python2.7/dist-packages/google/protobuf/internal/python_message.py", line 450, in _ReraiseTypeErrorWithFieldName
six.reraise(type(exc), exc, sys.exc_info()[2])
File "/usr/local/lib/python2.7/dist-packages/google/protobuf/internal/python_message.py", line 517, in init
copy.MergeFrom(new_val)
File "/usr/local/lib/python2.7/dist-packages/google/protobuf/internal/python_message.py", line 1208, in MergeFrom
"expected %s got %s." % (cls.name, type(msg).name))
TypeError: Parameter to MergeFrom() must be instance of same class: expected GraphDef got Graph. for field Event.graph_def

请问你的 Tensorflow 的版本是哪个? 因为新版本的和老版本的语法有点不同.
On 5 February 2017 at 12:58, py060301045<EMAIL_ADDRESS>wrote:

莫烦老师您好！
我是初学者，看了您的视频收获很大，讲行特别好，非常感谢您 的分享！
我用python2.7运行您的例程tutorials/tensorflowTUT/tf14_tensorboard/
会报错，不知道该怎么改。报错如下：
Traceback (most recent call last):
File "/home/py/文档/practice/tensorflow_Visualization2.py", line 46, in
writer = tf.train.SummaryWriter('logs/', sess.graph)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/
python/training/summary_io.py", line 82, in init
self.add_graph(graph_def)
File "/usr/local/lib/python2.7/dist-packages/tensorflow/
python/training/summary_io.py", line 128, in add_graph
event = event_pb2.Event(wall_time=time.time(), graph_def=graph_def)
File "/usr/local/lib/python2.7/dist-packages/google/protobuf/internal/python_message.py",
line 519, in init
_ReraiseTypeErrorWithFieldName(message_descriptor.name, field_name)
File "/usr/local/lib/python2.7/dist-packages/google/protobuf/internal/python_message.py",
line 450, in _ReraiseTypeErrorWithFieldName
six.reraise(type(exc), exc, sys.exc_info()[2])
File "/usr/local/lib/python2.7/dist-packages/google/protobuf/internal/python_message.py",
line 517, in init
copy.MergeFrom(new_val)
File "/usr/local/lib/python2.7/dist-packages/google/protobuf/internal/python_message.py",
line 1208, in MergeFrom
"expected %s got %s." % (cls.name, type(msg).name))
TypeError: Parameter to MergeFrom() must be instance of same class:
expected GraphDef got Graph. for field Event.graph_def
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MorvanZhou/tutorials/issues/31, or mute the thread
https://github.com/notifications/unsubscribe-auth/ASgmNN9Z2h0xncyWPToVzdx2Sep7mJjzks5rZVbxgaJpZM4L3Y-r
.

我用的是这个下的： https://storage.googleapis.com/tensorflow/linux/cpu/tensorflow-0.8.0-cp27-none-linux_x86_64.whl

建议使用python3.x，我看莫凡老师使用的是python3.x @py060301045


Convention annotation for Property values in Extensions?

Expected Behavior
Thank you for gradle and lazy properties!
I just had the thought that maybe a new "Convention" annotation would help reduce duplicated code and may make it clearer for plugin developers what default values are.
I guess what somewhat bugs me is that a plugin developers the actual defaults (convention) can be far away from the property in the extension.
Consider for example an interface extension where the convention is only set by the plugin:
interface HelloWorldPluginExtension {
    Property<String> getGreeting();
}

public class HelloWorldPlugin implements Plugin<Project> {
    public void apply(Project project) {
        var extension = project.getExtensions().create(
                "helloWorld", HelloWorldPluginExtension.class);
        extension.getGreeting().convention("Hello World");
    }
}

one certainly can bring this a bit closer, by passing on the project to the extension:
public class HelloWorldPluginExtension {
    Property<String> greeting;

    public HelloWorldPluginExtension(Project project) {
        greeting = project.getObjects().property(String.class).convention("Hello World");
    }
}

public class HelloWorldPlugin implements Plugin<Project> {
    public void apply(Project project) {
        var extension = project.getExtensions().create(
                "helloWorld", HelloWorldPluginExtension.class, project);
    }
}

With a large set of configuration options this can become messy really quickly. Especially when a project has various types of configurations (String, int, long, bool, ...) repeating the project.getObjects().property(SomeObject.class) feels painful.
Instead I'd propose a new Convention-Annotation that would work similar to the second example.
Roughtly I'd image that the second example could also be expressed as:
public class HelloWorldPluginExtension {
    @Convention("Hello World")
    Property<String> greeting;

    // Is a constructor even needed? Why not make the extension an interface again? Open for suggestions and interpretation!
}

public class HelloWorldPlugin implements Plugin<Project> {
    public void apply(Project project) {
        var extension = project.getExtensions().create(
                "helloWorld", HelloWorldPluginExtension.class, project);
    }
}

if types are needed I guess it also would be ok to supply types @Convention(String.class, "Hello World!"), but this could get tricky for lists and files/directories. Ideally the project would be accessible in the convention since for directory properties one might often need the project (e.g. project.getLayout().getProjectDirectory()....).
Thank you for your time and consideration.
Current Behavior (optional)
No response
Context
see above.

Thank you for your interest in Gradle!
This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

@TheSnoozer Thanks for the suggestion.
I think your first example (with the conventions in the plugin) is what we want to recommend for most use cases.
The annotation idea has come up before, but it has some issues:

The mental model we use is that conventions belong to the plugin. If there's an extension Foo, there can be multiple plugins with different conventions for the same property. Putting conventions directly into the extension would introduce another path for conventions that might be hard to explain.
The annotation is only convenient for things that can be known statically. Accessing project state is awkward and makes it easier to depend on unexpected things or invoke expensive calculations.
We want to encourage plugin authors to structure their plugins into reusable chunks. If the extension also has conventions, there isn't a way for another plugin to reuse the "unconfigured" extension.

In your second example, you could write:
public abstract class HelloWorldPluginExtension {
    public abstract Property<String> getGreeting();

    @Inject
    public HelloWorldPluginExtension() {
        getGreeting().convention("Hello World");
    }
}

This has some of the same problems as the annotation approach, but it avoids the need for injecting a Project.

Thank you for tacking the time to explain this in great detail! Also great thanks for your example where one would avoid the project.getObjects().property(SomeObject.class). I'm not really sure if I can avoid a somewhat very long list of configurations. In the end I'm working on a project that has grown over years in the maven world and now finally have time to make it a thing under gradle...certainly I can keep multiple Extensions and your snippet in mind.
Since I read between the lines that you (or gradle) would rather avoid the extra complexity (which is what I somewhat expected) I'm going ahead and close this request since I don't think you want to add such annotations.
Thanks again for taking the time and thank you for the consideration.
Closing as "Won't fix / Won't do".

Thanks again for the suggestion!
Works great.
Perhaps if anyone else bumps over this:
The suggestion requires at least gradle 5.3.
A 5.1 fails with
* What went wrong:
A problem occurred evaluating root project
> Failed to apply plugin
   > Cannot create a proxy class for abstract class 'Extension'.

and a 5.2 and 5.2.1 fail with
* What went wrong:
A problem occurred evaluating root project
> Failed to apply plugin
   > Could not create an instance of type Extension.
      > Receiver class Extension_Decorated does not define or inherit an implementation of the resolved method 'abstract org.gradle.api.provider.Property getMessage()' of abstract class Extension.

Since the above also gets rid of the project one needs to find a replacement.
In my case all was available through the ProjectLayout which can be injected in the extension.
E.g.
public abstract class HelloWorldPluginExtension {
    public abstract RegularFileProperty getHelloFile();

    @Inject
    public ProjectLayout getProjectLayout() {
        throw new IllegalStateException("Should have been injected!");
    }

    @Inject
    public HelloWorldPluginExtension() {
        getGenerateGitPropertiesFilename().convention(
            getProjectLayout().getBuildDirectory().file("hello.file"));
    }
}


[WIP] Handle 1-4TiB provider config and upscaling

Resolves Faas-44, Faas-45:

Adds support for UsableCapacityInTiB config knob with values 1-4TiB
Performs up-scaling and prevents down-scaling when updated value is smaller than current

TODOs:

[ ] Check regarding optimal perf of different setups of {capacity, OSD size} combos
[x] Check use case of non-integer UsableCapacityInTiB is handled correctly
[x] Test manually

Can we merge all the commits to be a single commit?
Also, could you remove WIP from the PR title?


Revive code coverage usage in neon repo

### Tasks
- [ ] Add coverage comment to the top of PR (based on the current solution or use  https://github.com/apps/barecheck )
- [ ] Coverage upload to some TTL-based storage (S3/..) https://github.com/neondatabase/neon/pull/4256
- [ ] Add to review template to ensure the reviewer tends to coverage as well
- [ ] Enforcement of some level if needed (minimal threshold)

The report isn't pretty (I like them colorized) but that's a separate issue :)
I think it would be helpful to include the report link in the 'allure' comment. That way, it's in front of dev eyes => people will look at it.
If it can't be in the same comment, then post a separate comment for coverage, that is auto-updated just like the allure report.
Once we get the 'coverage change by this PR' reporting that @shanyp asked for above, we can get rid of that comment again.

From https://github.com/neondatabase/neon/pull/4256#pullrequestreview-1430207402


Add collapse option

Add collapse option
✍  Description
This PR cherry-picks the commits made here and extends the functionality of adding a collapse action to compose.
📷 Demo
ltr.webm
rtl.webm
⚠ I have tested all scenarios, but it might be wise to double check that everything works properly

@giangpham96 I just found a bug with my implementation. The last line gets cut incorrectly with a collapse action. I will submit a fix soon. Do not merge!


AVD optimization

the URL is broken https://github.com/Azure/avdaccelerator/blob/main/workload/scripts/Optimize_OS_for_AVD.ps1#L20

Thanks @jamasten closing this issue


Can noise reduction be set to be intermediate to the fixed noise_level settings?

I have images where noise_level set at 0 is not enough, but when set at 1 it is too much filtering.  Is it possible to have an intermediate amount of noise reduction between noise_level 0 and 1?
Thanks!

No. Each noise_level uses a different pre-trained model.

Ok, thanks for the speedy response.

A person who never made a mistake never tried anything new. -- Albert Einstein
Well done is better than well said. -- Benjamin Franklin
The essence of faith is fewness of words and abundance of deeds. -- Bahá´u´lláh

On Aug 1, 2019, at 4:09 PM, nagadomi<EMAIL_ADDRESS>wrote:
No. Each noise_level uses a different pre-trained model.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


feat(collapse): add possibility to collapse horizontally

New attribute to collapse horizontally or vertically : put 'horizontal' to collapse horizontally or put nothing to do it vertically
Plunkr : http://plnkr.co/edit/EXr6cBJ58wfRRDlvCl5i?p=preview

This mostly looks good, just needs some code cleanup to avoid unnecessary repetition.

Sorry for two of my commit but i made a lot of code cleanup.
Pluckr updated : http://plnkr.co/edit/EXr6cBJ58wfRRDlvCl5i?p=preview

We have an open issue for this.  I'll try and find to link it in.  Thank you for taking the initiative to do this...

A lot of minor issues, clean those up and this should be good to go

@icfantv I needed this feature so i made it and i send it here :)

I think this is good for merge - what do you think @icfantv?

Yep, doooo eeeeeet.


[x] website builds and runs in production - for information on how to test locally go here.

Description

Added /tutorials
Added the tutorialLink component
Added tutorials to the navbar
Additional Information
Reviewers, please see the abstract property for each TutorialLink. I have brought in a paragraph from each blog but this was just to get content in place.
fixes: https://github.com/appsody/website/issues/80

Closing as we could link straight to medium for now


Allow Strategy template trading_logic! implementations to behave differently with respect to the format of the data received

It would be nice if the strategy templates may be compatible with more than one format of data, and it would also be nice if it didn't take much effort to do it.
Design comments:
Julia has Typing on datatypes for example 2USD can have the type Money{:USD}
and we can have a function
function x(m::Money{S}) where {S}
  if S==:USD
   # Do this
  end
end

Even more you can have multiple dispatch depending on the value of S. This can be a nice computational advantage if implemented correctly

Not sure which milestone this would correspond to, nor how it prioritize against other stories. Will leave in the parking lot in the meantime


Jsx renderer uses rouge jsx lexer (from 2.0.6 onwards)

Signed-off-by: Tom Chen<EMAIL_ADDRESS>See: https://github.com/jneen/rouge/issues/275

Is CI in general just broken right now?


SW-6274 Added std dev calculations

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2720  👈 (View in Graphite)
#2719
#2716
main

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

Merge activity

Dec 30, 11:04 PM EST: A user started a stack merge that includes this pull request via Graphite.


SO MANY FILES ARE BEING SHRUNKEN IT'S NOT EVEN FUNNY

(also brazdan paras gets its (or rather its kantonian counterpart's) cry)

Conflicted with LFS reversion, gonna attempt to discard these commits and try again


Focus method used by various events should unfocus what is focused already

Heard a comment on the Ember Weekend show, http://emberweekend.com/episodes/actual-newsy-things at 01:10 about focus and how we could also check the DOM and focusout on any currently focused element.
Perhaps in the focus method we could use document.activeElement to check if an element has focus and fire blur or focusout

See https://developer.mozilla.org/en-US/docs/Web/API/Document/activeElement

@code0100fun @rondale-sc Can you comment here, please :) I think you had some feedback from on the podcast, would be great to capture that here as well.

I also heard the podcast and I was surprised by that. At least if the browser window has the focus, I'd expect el.focus(); on this line to also cause a blur on whatever else if focused before.
Perhaps that effect only happens on the branch before, the one were we fake a focus.

In CI the browser is not in focus as it's driven by a machine. So yeah the branch of manually firing focus could also check for document.activeElement but again how could that be necessary as the browser it is not in focus. Well I guess if the tests fires focus somehow it could be true that we'd need to unfocus. So that begs the question should we have a focus helper too?

the problem is that (I think) if the browser doesn't has the focus, you cannot obtain document.activeElement, so we can't know what to blur. Can we?

From Slack, thanks @code0100fun …

Chase… I'm not sure if Twiddle supports addons fully. I can't import the click function. Here is my use case: https://ember-twiddle.com/58027e0abcdbda5ee6001ce01245eac5?openFiles=tests.integration.components.my-component-test.js%2Ctemplates.components.my-component.hbs If you disable tests you can see it working. The test should pass but does not without manaully bluring/focusing

@cibernox yeah document.focus() will trigger blur event on the document.activeElement. I added a test in the PR to show that working. The caveat is that that part of the test can only work if the browser window has focus, so skips in CI. Also Chrome, Firefox and Safari pass with the new test in PR #36. However PhantomJS fails so it may be time to abandon PhantomJS.

@code0100fun @rondale-sc Please see the PR which adds a test to show that blur does fire as long as the browser window has focus.