Migrate to React 18

Have you read the Contributing Guidelines on issues?

[X] I have read the Contributing Guidelines on issues.

For site maintainers
Upgrading to React 18 is optional—it won't break anything, but it won't do anything either. Until Docusaurus uses the new createRoot API, the site's behavior will still be the same as that in React 17. However, you may be able to use a few React 18 niceties like useId() (which I'm personally excited about for accessibility reasons).
If your dependency management bot wants to upgrade to React 18 for you, and it doesn't cause any problems (around peer dependencies), feel free to accept it.
Motivation
Unlike React 17, React 18 contains actual API changes that may not be backward-compatible (i.e. you can't take a React 18 program and expect it to run in a project installed with React 17). Therefore, migration to React 18 can only happen along two paths:

We migrate to React 18 by using the new createRoot API, and throw an early error for anyone still installed with react@17, telling them to update their package.json.

Problem: breaks virtually every site, some sites already having a version of React in their monorepo may end up having duplicate copies, which opens a can of worms.

We detect the version of React installed, and selectively uses ReactDOM.render or createRoot based on the version.

Problem: hacky code, slightly increases bundle size, and harder to maintain in the long run (refactoring hazards)

It is not good to move forward with either solution.
We have some preliminary work done in #7102, but it's far from being complete, and gets stalled in multiple places. The resolution is that as the 2.0 release is approaching, we'll likely stay on React 17 because the truth is, even many libraries are not fully prepared for React 18 yet! React 18 will be considered a breaking change and will come in v3.
The most urgent blocking issue is that MDX v1 doesn't declare React v18 in its peer dependencies range. Because the v1 line is effectively frozen, I believe there's no plan to fix this. Certain package managers (namely, npm v7 and pnpm) are strict about peer dependencies and will refuse to install properly if @mdx-js/react is installed alongside react@18. This will be confusing for the users, so it's another strong point why we'll delay it to v3: we'll only migrate to MDX v2 in Docusaurus v3 (#4029).
Since I don't think React 18 actually removed any API, there's not much we need to do on the code side. It's only about dependencies. Still, it would be nice if we can remove react-loadable (#3841), because it uses the deprecated componentWillMount lifecycle and prevents us from opting into StrictMode. Also, React 18 will bring support for new SSG APIs (including server-rendering Suspense), and we'll want to take the opportunity of prolonged migration time window to look into that as well.
Self-service

[ ] I'd be willing to do some initial work on this proposal myself.

@sanjaiyan-dev That falls under the realm of

Problem: hacky code, slightly increases bundle size, and harder to maintain in the long run (refactoring hazards)

I'm not really willing to maintain that code, but it's a nice path nevertheless. Let's wait till v3 is actually on the roadmap to decide what is best for us.

so react 18 would never be supported on V2? only on the future version, Docusaurus V3?
There are some really nice features in react-18.
For example, ReactDOMServer (which is used on production build) 18 allows lazy loading of React components, which in turn allows write and use of custom components that show a live preview of a component and its code.

We hope to release Docusaurus v3 very quickly. According to our release doc, it should be within a few months, so you should not worry about it too much. React 18 will be a major change, so no, it will not be backported. Also, we have abstracted all the build pipeline, so we hope you could develop without caring about the underlying plumbing infra.

When can we expect the first canary release that uses React 18? Saw that you have 3.0.0-alpha.0 but it's still on React 17?

Hi! I have a problem that I think is related to this issue. I have a monorepo (turborepo) and I can't have multiple versions of react in it. (otherwise react breaks) I'm trying to change the docusaurus project's react dependency to 18, but npm install fails with:
peer<EMAIL_ADDRESS>|| ^17.0.0" from<EMAIL_ADDRESS>
I noticed that next-auth has a similar project structure and is successfully using react 18 in the docusaurus project.
I tried to replicate it on my project, but wasn't successful. Does someone understand how they did it? Is there anyway I can work around this problem?
Thank you in advance.

Just disable strict peer dependencies. If you're on pnpm, create a .npmrc and put strict-peer-dependencies=false in it

@juliusmarminge thanks for the guidance!
I was able to make it work with the command npm i --legacy-peer-deps now that the lock file has the structure, I'm able to instal with only npm i.

Would also love to know if there's an updated timeline somewhere for support. Wasn't able to come up with branches / tags to look at. Would be happy to play the guinea pig here! (we're actually "dependent" on React 18, because we'd love to integrate https://github.com/pacocoursey/cmdk with our docs)

Is a contribution needed here to keep this item moving forward? I'd be happy to commit to this, as the peer deps poses problems for monorepos in particular.

@Sonic12040 React 18 and MDX2 are aimed at being supported with V3: https://github.com/facebook/docusaurus/discussions/8469

Thanks for that. I'll see what's open to contribute to 3.0!


Add transferwise variant of tap-mysql

Migrated from GitLab: https://gitlab.com/meltano/meltano/-/issues/2411
Originally created by @DouweM on 2020-11-05 23:14:08

https://github.com/transferwise/pipelinewise-tap-mysql
https://transferwise.github.io/pipelinewise/connectors/taps/mysql.html

View 7 previous comments from the original issue on GitLab


Bad indentation when using elementary.generate_schema_baseline_test

Describe the bug
The output of dbt run-operation elementary.generate_schema_baseline_test has bad indentation.
Currently, the resulting data is structured as:
Generating schema changes from baseline test for source 'mytable':

sources:
  - name: the_schema
    tables:
  - name: mytable
    columns:
        - ...

While it should be formatted as
Generating schema changes from baseline test for source 'mytable':

sources:
  - name: myschema
    tables:
      - name: mytable
        columns:
          - ...

Additionally, there are two very usefull nice to have's for this call:

Output in lowercase: It is very common to describe all fields and data-types exclusively in lowercase, the output of the command, however, is currently always fully-uppercase. A flag to change this would be great
Automatically add it to existing .yml files. It would be fairly doable to scan the existing yml files for the correct sources and appen the tests and column definitions to them for even more ease of use.

Environment:

edr Version: 0.7.7
dbt package Version: 0.7.5

Hi @Luttik ,
Thank you for reporting!
Unfortunately, your second suggestion isn't trivial, as the operation is a dbt operation and through dbt you don't get write access to the .yml files...
But the good news are that fixing the formatting and adding a flag to default to lowercase should be very easy to do.
Would you be interested in contributing this change?

This is the relevant file - https://github.com/elementary-data/dbt-data-reliability/blob/master/macros/commands/generate_schema_baseline_test.sql
In the macro generate_schema_baseline_test_for_node I suggest taking the code under this comment:   {# Common yaml for sources and models #} and separating it to a macro that creates the model yaml and another one that creates the source one.


Update EKS-D for 1.20 - 1.23

Issue #, if available:
Description of changes:

Updates EKS-D for 1.20 - 1.23, which includes Kubernetes patch version updates for 1.22 and 1.23

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve

/test flux-tooling-presubmit


Collaboration service - envvar issues

While adding the collaboration service to the admin docs which was a neccessity to get an error free build, I stumbled over some envvar related things that need a change. As reference how it is currently rendered, see the admin docs:

The sort order of items is not inline with other serices.
We have for example in all other services logging, tracing or debugging on top but here it is at the bottom.
COLLABORATION_JWT_SECRET (OCIS_JWT_SECRET)
This envvar has a string defined, normally we have this empty, see all other services using OCIS_JWT_SECRET. If a value must be populated, we need to reflect this in the description and in the requirements of the readme.
The default for COLLABORATION_APP_LOCKNAME --> com.github.owncloud.collaboration looks strange.
I doubt for the COLLABORATION_APP_ICON that both the default image-edit and the description Icon for the app are correct. Imho the default should be empty and the description adapted to define a path to an icon using $OCIS_BASE_DATA_PATH/path as we have in many other services. For an example see the PROXY_TRANSPORT_TLS_CERT envvar.
Should'nt we add OCIS_GATEWAY_GRPC_ADDR to the COLLABORATION_GRPC_ADDR and use the default of the global envvar?
Many envvars need a much better and clearer description to make them also inline with other services..

@jvillafanez @micbar @dragonchaser

The sort order of items is not inline with other serices.

I think the items that need to be changed should be at the top, and items that are unlikely to be changed should be bottom. I'm quite convinced that people in general will look at the first 5-10 options before assuming that the rest are optional and don't need to be touched for an initial approach.
Anyway, consistency is also important.

COLLABORATION_JWT_SECRET (OCIS_JWT_SECRET)

I'm not sure if we can use an empty secret. The idea was to ensure that at least there is a secret available that can be overwritten if needed, so a random-generated secret is populated there early.
I need to check how other services are doing this, but I suppose we'll just need to move the generation of the secret to a different place.

The default for COLLABORATION_APP_LOCKNAME

This was copied from the original repo so I'm not sure if it needs a specific format or not. Maybe @wkloucek knows.

I doubt for the COLLABORATION_APP_ICON

Same

Should'nt we add OCIS_GATEWAY_GRPC_ADDR to the COLLABORATION_GRPC_ADDR and use the default of the global envvar?

The collaboration service starts a GRPC server that is connected to reva, so the address is for that service. It's also a bind address, so other services, in particular reva, can access to the collaboration service via GRPC.
I'm not sure how much ocis-related is that address because is linked to reva.
Side note, I'm not sure if we have a reference service. Except for the specific options for the service, most of the options have been copied from other services.

COLLABORATION_JWT_SECRET (OCIS_JWT_SECRET)

I think we need to use the global OCIS_JWT_SECRET together with the local variable

I'm not sure if we can use an empty secret. The idea was to ensure that at least there is a secret available that can be overwritten if needed, so a random-generated secret is populated there early.
I need to check how other services are doing this, but I suppose we'll just need to move the generation of the secret to a different place.

The jwt secret is randomized during ocis init.

Should'nt we add OCIS_GATEWAY_GRPC_ADDR to the COLLABORATION_GRPC_ADDR and use the default of the global envvar?

The collaboration service starts a GRPC server that is connected to reva, so the address is for that service. It's also a bind address, so other services, in particular reva, can access to the collaboration service via GRPC.
I'm not sure how much ocis-related is that address because is linked to reva.

Side note, I'm not sure if we have a reference service. Except for the specific options for the service, most of the options have been copied from other services.

We should add  OCIS_GATEWAY_GRPC_ADDR to the COLLABORATION_GRPC_ADDR

We should add OCIS_GATEWAY_GRPC_ADDR to the COLLABORATION_GRPC_ADDR

This was wrong. The COLLABORATION_GRPC_ADDR has nothing to do with the Gateway.
All issues in this ticket are fixed.


Yarn is trying to unpack in the same destination

When Running
Yarn install
Error -  _Pattern ["@injectivelabs/token-metadata@next"] is trying to unpack in the same destination "/home/codespace/.cache/yarn/v6/npm-@injectivelabs-token-metadata-1.11.0-beta.16-01c375e3396812733f15caa5b11976c592cdf1bc-integrity/node_modules/@injectivelabs/token-metadata" as pattern ["@injectivelabs/token-metadata@^1.11.0-beta.16","<EMAIL_ADDRESS>This could result in non-deterministic behavior, skipping
To Reproduce
``yarn install Expected behavior
expect it to install the dependencies properly
Using Github codespaces, as work space.

Can you try removing node_modules and installing again?

Yes, will do thank you.


Build scan publishes results even if licenseAgree is set to no

Expected Behavior

Build scan publishes scan results to central server if following configuration is applied in your build.gradle
// Adds build scan functionality
plugins {
id 'com.gradle.build-scan' version '1.13.1'
}
buildScan {
licenseAgreementUrl = 'https://gradle.com/terms-of-service'
licenseAgree = 'yes'
}
// End build scan functionality
Current Behavior

Even if build scan is configured as without url or licenseAgree='no' it still publishes the results
// Adds build scan functionality
plugins {
id 'com.gradle.build-scan' version '1.13.1'
}
buildScan {
licenseAgreementUrl = 'https://gradle.com/terms-of-service'
licenseAgree = 'no'
}
// End build scan functionality
$ gradle build --scan
BUILD SUCCESSFUL in 0s
4 actionable tasks: 4 up-to-date
Publishing build scan...
https://gradle.com/s/y.......
OR
// Adds build scan functionality
plugins {
id 'com.gradle.build-scan' version '1.13.1'
}
buildScan {
licenseAgreementUrl = ''
licenseAgree = 'no'
}
// End build scan functionality
$ gradle build --scan
BUILD SUCCESSFUL in 0s
4 actionable tasks: 4 up-to-date
Publishing build scan...
https://gradle.com/s/b.......
Context

Steps to Reproduce (for bugs)

Create a simple java project and run the build as follows:
gradle build --scan
NOTE: Add plugin configuration for build scan with licenseAgree='no' with or without Url as shown above.
Your Environment

Build scan URL:

I cannot reproduce it now, looks like there may have been something else that was overriding settings.


Add new pipeline: MB'n'B

This PR adds the pipeline Freedberg and @mollysrour were talking about yesterday, which runs two tree generation steps.
The first tree generation generates the consensus tree through MrBayes, which we feed into Ent and get out the initial list of non-monophyletic individuals.
The second tree generation removes those individuals from the data, then runs BEAST and JML on the reduced dataset.
We then present the JML distributions, probabilities, and results tables nicely in the UI, and we highlight any results with P<0.05 in the table in yellow.
Thoughts on the approach or the implementation welcome. I'll go over it at tomorrow's meeting, too.
(PS: this PR is actually only +314, if you discount the new tests.)

At Hawken's behest, I will merge this and make another release and inform the bio team yet again

(once I get up to my room that is)


[Bug] [Regression] GeneratePage does not work

Description
Generate Page from datasource does not work
Steps to reproduce the behaviour:

Important Details

Version: [Cloud / Self-Hosted vx.x]
OS: [e.g.MacOSX]
Browser [e.g. chrome, safari]
Environment [production, release, deploy preview]

@nidhi-nair here generate a page from Datasource API response are different hence the problem. Can you please checkout if you need to update the backend with the latest release or something?

@yatinappsmith I'm not able to reproduce this issue. It could be as Apeksha mentions, and that a recent build has resolved the issue. Could you please confirm this?

verified on latest DP


Split for Installation and Configuration Plays

[x] Moved services variables from hard coded includes to vars, so we can skip remove services we do not want, IE kafka-rest. Added 2 new vars for this kafka_services and zookeeper_services, defaults work as before
[x] Added state value to the services, this way we can do an installation and not start the services, this is needed for building a vm
[x] Added enabled value to services, so we can install a service but not enable it, this is needed for building VMS
[x] Added installation and configuration tags across the board
[x] Fixed some typos, renamed tasks

Nice idea of moving the services variables. Looks way better


Errbit: Set bigdecimal gem version

The stats role isn't booting on Fedora 32 (which includes a more recent version of ruby, 2.7). After some googling, it turns out we need to pick a version of the bigdecimal gem that is compatible with errbit.
See: https://github.com/ruby/bigdecimal#which-version-should-you-select
I've tested this out, and it get us past asset compilation stage that was failing.
qa_req 0
Ref: https://github.com/iFixit/server-templates/issues/2748
CC @danielbeardsley @addison-grant @iFixit/devops

CR :barber:

CR 👍

CR 👍


Investigate abc9

Description
Yosys has support for a new command, abc9, which appears to be a new version of abc.
This new version seems to support a number of interesting functions:
This script pass performs a sequence of commands to facilitate the use of the
ABC tool [1] for technology mapping of the current design to a target FPGA
architecture. Only fully-selected modules are supported.

    -run <from_label>:<to_label>
        only run the commands between the labels (see below). an empty
        from label is synonymous to 'begin', and empty to label is
        synonymous to the end of the command list.

    -exe <command>
        use the specified command instead of "/nix/store/zfnc6mbakfrh7nlri48i3x7yxgj2d3ql-yosys-abc/bin/abc" to execute ABC.
        This can e.g. be used to call a specific version of ABC or a wrapper.

    -script <file>
        use the specified ABC script file instead of the default script.

        if <file> starts with a plus sign (+), then the rest of the filename
        string is interpreted as the command string to be passed to ABC. The
        leading plus sign is removed and all commas (,) in the string are
        replaced with blanks before the string is passed to ABC.

        if no -script parameter is given, the following scripts are used:
          &scorr; &sweep; &dc2; &dch -f; &ps; &if {C} {W} {D} {R} -v; &mfs

    -fast
        use different default scripts that are slightly faster (at the cost
        of output quality):
          &if {C} {W} {D} {R} -v

    -D <picoseconds>
        set delay target. the string {D} in the default scripts above is
        replaced by this option when used, and an empty string otherwise
        (indicating best possible delay).

    -lut <width>
        generate netlist using luts of (max) the specified width.

    -lut <w1>:<w2>
        generate netlist using luts of (max) the specified width <w2>. All
        luts with width <= <w1> have constant cost. for luts larger than <w1>
        the area cost doubles with each additional input bit. the delay cost
        is still constant for all lut widths.

    -lut <file>
        pass this file with lut library to ABC.

    -luts <cost1>,<cost2>,<cost3>,<sizeN>:<cost4-N>,..
        generate netlist using luts. Use the specified costs for luts with 1,
        2, 3, .. inputs.

    -maxlut <width>
        when auto-generating the lut library, discard all luts equal to or
        greater than this size (applicable when neither -lut nor -luts is
        specified).

    -dff
        also pass $_DFF_[NP]_ cells through to ABC. modules with many clock
        domains are supported and automatically partitioned by ABC.

    -nocleanup
        when this option is used, the temporary files created by this pass
        are not removed. this is useful for debugging.

    -showtmp
        print the temp dir name in log. usually this is suppressed so that the
        command output is identical across runs.

    -box <file>
        pass this file with box library to ABC.

Note that this is a logic optimization pass within Yosys that is calling ABC
internally. This is not going to "run ABC on your design". It will instead run
ABC on logic snippets extracted from your design. You will not get any useful
output when passing an ABC script that writes a file. Instead write your full
design as an XAIGER file with `write_xaiger' and then load that into ABC
externally if you want to use ABC to convert your design into another format.

[1] http://www.eecs.berkeley.edu/~alanmi/abc/

    check:
        abc9_ops -check [-dff]    (option if -dff)

    map:
        abc9_ops -prep_hier [-dff]    (option if -dff)
        scc -specify -set_attr abc9_scc_id {}
        abc9_ops -prep_bypass [-prep_dff]    (option if -dff)
        design -stash $abc9
        design -load $abc9_map
        proc
        wbflip
        techmap -wb -map %$abc9 -map +/techmap.v A:abc9_flop
        opt -nodffe -nosdff
        abc9_ops -prep_dff_submod                                                     (only if -dff)
        setattr -set submod "$abc9_flop" t:$_DFF_?_ %ci* %co* t:$_DFF_?_ %d           (only if -dff)
        submod                                                                        (only if -dff)
        setattr -mod -set whitebox 1 -set abc9_flop 1 -set abc9_box 1 *_$abc9_flop    (only if -dff)
        foreach module in design
            rename <module-name>_$abc9_flop _TECHMAP_REPLACE_                         (only if -dff)
        abc9_ops -prep_dff_unmap                                                      (only if -dff)
        design -copy-to $abc9 =*_$abc9_flop                                           (only if -dff)
        delete =*_$abc9_flop                                                          (only if -dff)
        design -stash $abc9_map
        design -load $abc9
        design -delete $abc9
        techmap -wb -max_iter 1 -map %$abc9_map -map +/abc9_map.v [-D DFF]    (option if -dff)
        design -delete $abc9_map

    pre:
        read_verilog -icells -lib -specify +/abc9_model.v
        abc9_ops -break_scc -prep_delays -prep_xaiger [-dff]    (option for -dff)
        abc9_ops -prep_lut <maxlut>    (skip if -lut or -luts)
        abc9_ops -prep_box    (skip if -box)
        design -stash $abc9
        design -load $abc9_holes
        techmap -wb -map %$abc9 -map +/techmap.v
        opt -purge
        aigmap
        design -stash $abc9_holes
        design -load $abc9
        design -delete $abc9

    exe:
        aigmap
        foreach module in selection
            abc9_ops -write_lut <abc-temp-dir>/input.lut    (skip if '-lut' or '-luts')
            abc9_ops -write_box <abc-temp-dir>/input.box    (skip if '-box')
            write_xaiger -map <abc-temp-dir>/input.sym [-dff] <abc-temp-dir>/input.xaig
            abc9_exe [options] -cwd <abc-temp-dir> -lut [<abc-temp-dir>/input.lut] -box [<abc-temp-dir>/input.box]
            read_aiger -xaiger -wideports -module_name <module-name>$abc9 -map <abc-temp-dir>/input.sym <abc-temp-dir>/output.aig
            abc9_ops -reintegrate [-dff]

    unmap:
        techmap -wb -map %$abc9_unmap -map +/abc9_unmap.v
        design -delete $abc9_unmap
        design -delete $abc9_holes
        delete =*_$abc9_byp
        setattr -mod -unset abc9_box_id

Proposal
We should investigate uses for abc9 within our synthesis scripts.

Appears to be primarily FPGA-geared.


[Bug] parallel output may be error in no flashattention case

描述该错误

parallel output may be error in no flashattention case
环境信息
no flashattention case
其他信息
No response

here is a hard-code

completed in pr #103


Add copy tooltips to address avatar + name

@holygits  We should have put a css development guide somewhere but did not get a time.
Anyway, generally we implemented theming & colour definition in styled-theming, which was similar with that in runanode.
The detailed documents can be viewed at centrality-react-components-demo.netlify.app for now.
Upcoming review comments may find some references from the above links.
cc @alexsednz  @KarishmaBothara

changes looks good to me on UI.. except for on safari the copy icon is not completely visible, but it works well on chrome/firefox

It would be easier to get dev/designer reviews with gif image showcases attached in ui PRs.
Otherwise, please check with the design team to have a design review before PR merging.

lgtm


Add module files

I've added the most important module files. Note that the files 'visualize' and 'utils' should be empty right now because I'll be moving some functions there (but the structure will remain the same).

Failures to load ADIOS2_jll should have been fixed by https://github.com/JuliaRegistries/General/pull/91100 (and https://github.com/JuliaRegistries/General/pull/91101)

Windows CI keeps failing due to a ADIOS2.jl issue:
https://github.com/eschnett/ADIOS2.jl/issues/15


How to extract sentence features (vectors) from a custom transformer language model?

What is your question?
I have trained a simple custom transformer language model following the exact instructions and parameters from your readme (https://github.com/pytorch/fairseq/blob/master/examples/language_model/README.md), and now I would like to extract features for new sentences (a vector for each sentence). Is that possible?
After loading the model, I can encode new sentences and get token tensors in return, but I don't see any functions to get the features (like the extract_features function in roBERTa) in the form of tensors/vectors for each new sentence. Is there any way to do that?
Thanks in advance.

You can access the underlying models from the hub interface.  The following should do what you're looking for:
import torch

en_lm = torch.hub.load('pytorch/fairseq', 'transformer_lm.wmt19.en', tokenizer='moses', bpe='fastbpe')
tokens = en_lm.encode('This is a test')
batch_tokens = tokens.unsqueeze(0)  # extract_features expects a batch of tokens
x, extra = en_lm.models[0](tokens)  # [0] specifies the first model in the ensemble
extracted_features = extra["inner_states"][-1]  # -1 will give you the last layer's features

Thanks for the code, however it seems that it's not working. This is what I have when I try it:
`>>> en_lm = torch.hub.load('pytorch/fairseq', 'transformer_lm.wmt19.en', tokenizer='moses', bpe='fastbpe')
Downloading: "https://github.com/pytorch/fairseq/archive/master.zip" to /Users/pikusmi1/.cache/torch/hub/master.zip
100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████|<PHONE_NUMBER>/3617096500 [05:12<00:00, 11587188.41B/s]
Loading codes from /Users/pikusmi1/.cache/torch/pytorch_fairseq/0cabe4a3e5ef7de13b205be3ab7feaf000768c332991cab28503a5464cbd5133.1194dafe66fa251b0e81fb532efac27216c501bfb0573c5d7e77e04dd6d88b15/bpecodes ...
Read 30000 codes from the codes file.

tokens = en_lm.encode('This is a test')
batch_tokens = tokens.unsqueeze(0)
x, extra = en_lm.models0
Traceback (most recent call last):
File "", line 1, in
File "/Users/pikusmi1/miniconda3/envs/sig2cpd/lib/python3.6/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
result = self.forward(*input, **kwargs)
File "/Users/pikusmi1/miniconda3/envs/sig2cpd/lib/python3.6/site-packages/fairseq/models/fairseq_model.py", line 481, in forward
return self.decoder(src_tokens, **kwargs)
File "/Users/pikusmi1/miniconda3/envs/sig2cpd/lib/python3.6/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
result = self.forward(*input, **kwargs)
File "/Users/pikusmi1/miniconda3/envs/sig2cpd/lib/python3.6/site-packages/fairseq/models/transformer.py", line 691, in forward
alignment_heads=alignment_heads,
File "/Users/pikusmi1/miniconda3/envs/sig2cpd/lib/python3.6/site-packages/fairseq/models/transformer.py", line 712, in extract_features
alignment_heads,
File "/Users/pikusmi1/miniconda3/envs/sig2cpd/lib/python3.6/site-packages/fairseq/models/transformer.py", line 757, in extract_features_scriptable
if self.embed_positions is not None
File "/Users/pikusmi1/miniconda3/envs/sig2cpd/lib/python3.6/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
result = self.forward(*input, **kwargs)
File "/Users/pikusmi1/miniconda3/envs/sig2cpd/lib/python3.6/site-packages/fairseq/modules/sinusoidal_positional_embedding.py", line 69, in forward
bsz, seq_len = bspair[0], bspair[1]
IndexError: index 1 is out of bounds for dimension 0 with size 1`

Any suggestions what could be causing that error?
Thanks!

I figured it out. There was a typo, as in the code you pasted you passed tokens instead of batch_tokens to the model.
Now it works correctly:
>>> x, extra = en_lm.models[0](batch_tokens)
>>> extracted_features = extra["inner_states"][-1]
>>> extracted_features
tensor([[[-3.5917, -1.8685, -9.1815,  ..., -4.9372,  8.9840,  7.8096]],

        [[ 0.5874, -4.2458, -6.0061,  ..., -5.2102,  4.8120, 10.1918]],

        [[ 5.3164, -3.1789, -2.2152,  ..., -7.4375,  5.0749,  7.6545]],

        [[ 7.2160, -2.4256, -2.2334,  ..., -6.8708, 11.5427,  0.9657]],

        [[-1.7110,  0.8291,  0.3438,  ..., -4.2493,  3.7655,  2.7240]]],
       grad_fn=<AddBackward0>)

Thanks a lot for your help!


Problems with SQL Server deadlocks

Bug description
If a connection triggers a deadlock on SQL Server, the following queries in that connection throw an exception on a transaction descriptor.
Additionally, if connection gets to a deadlock, it gets rolled back automatically. In core, if the transaction fails, we try to trigger another rollback. This one throws an error, but we should just not quietly skip that one.

@pimeys Hey do you have more information you could add here, specifically on how to reproduce this?

@eviefp as for now, this is fixed, tests added for both client and engine. Sorry for outdated ticket, closing this now.


SmoothPath fails for ADA

SmoothPath appears to fail for Ada: Specifically, ADA keeps moving back and forth when RRTConnect is called, indicating a possible issue with shortcutting. It also appears not to respect collision constraints. @hjzh4

It seems, when we use ompl RRTConnect, we need to set planner range by calling ::ompl::geometric::RRTConnect::setRange(double distance) otherwise the planner range will be inf by default and the distance between adjacent nodes of random exploration tree will be very  large which results in a jerky path with a few waypoints (3~4).

That's right. When you call an OMPL planner, you will need to set the planner parameters as per your choosing. A few questions before I solve the issue:

@Stefanos19, is the robot moving back and forth along the same motion? Or is it that it moves along a windy path (which would be the expected behavior if the range is high)?

@hjzh4, are you using planner/ompl/OMPLConfigurationToConfigurationPlanner to set up the planner or are you calling the function utility function provided in robot/util/planToConfiguration()?

Hi Aditya, I directly called util/planToConfiguration()

Hi Aditya, Thanks for the prompt response!  Sounds like the issue is then in setting up the planner parameters.
AIKIDO now allows defining Problems and Planners for planning. If you have a planner/ConfigurationToConfiguration problem, you could use a planner/ompl/OMPLConfigurationToConfigurationPlanner, a wrapper for OMPL planners. It exposes the underlying planner to allow setting planner specific parameters. You could instantiate an RRTConnect as follows:
auto mPlanner = std::make_shared<OMPLConfigurationToConfigurationPlanner<RRTConnect>>(adaArmSpace);
auto omplPlanner = mPlanner->getOMPLPlanner()->as<RRTConnect>();
omplPlanner->setRange(range);
omplPlanner->setAnyPlannerParam(value);

Your own method planToConfiguration() could then just be mPlanner->plan(problem).
Two more points:

We generally set the RRTConnect range to be equal to the collision checking resolution without loss in performance.
I would recommend checking out planner/SequenceMetaPlanner if you are setting up multiple planners to solve the problem.

Setting the planner parameters did the trick. Closing the issue.


trouble defining grid when axis doesnt have direction attributes

Reported by ansley b manke on 17 Oct 2012 20:46 UTC
Kevin ran into this dataset,
http://www.ncdc.noaa.gov/thredds/dodsC/OISST-V2-AVHRR_agg
whose netCDF header looks like this:

netcdf OISST-V2-AVHRR_agg {
dimensions:
        lat = 720 ;
        lon = 1440 ;
        time = 11369 ;
        zlev = 1 ;
variables:
        float zlev(zlev) ;
                zlev:long_name = "Sea surface height" ;
                zlev:units = "meters" ;
                zlev:actual_range = "0, 0" ;
                zlev:_CoordinateAxisType = "Height" ;
        float lat(lat) ;
                lat:long_name = "Latitude" ;
                lat:units = "degrees_north" ;
                lat:grids = "Uniform grid from -89.875 to 89.875 by 0.25" ;
        float lon(lon) ;
                lon:long_name = "Longitude" ;
                lon:units = "degrees_east" ;
                lon:grids = "Uniform grid from 0.125 to 359.875 by 0.25" ;
        float time(time) ;
                time:long_name = "Center time of the day" ;
                time:units = "days since 1978-01-01 00:00:00" ;
        short sst(time, zlev, lat, lon) ;
                sst:long_name = "Daily sea surface temperature" ;
                sst:units = "degrees_C" ;
                sst:_FillValue = -999s ;
                sst:add_offset = 0.f ;
                sst:scale_factor = 0.01f ;
                sst:valid_min = -300s ;
                sst:valid_max = 4500s ;
                sst:standard_name = "daily_sea_surface_temperature" ;

The axis zlev doesn't have CF attributes that identify it as a Z axis, so Ferret needs to decide where to put it. But Ferret does have enough info to create a correct grid.  Instead it creates this grid with ZLEV on the E axis:
aborted
yes? sh grid sst
    GRID GND1
 name       axis              # pts   start                end
 LON       LONGITUDE         1440mr   0.125E               0.125W
 LAT       LATITUDE           720 r   89.875S              89.875N
 normal    Z
 TIME      TIME             11369 r   01-SEP-1981 00:00    16-OCT-2012 00:00
 ZLEV      E (meters)           1 r   0                    0
 normal    F

I created a small file xsz.nc which has axes XAX, SAX, and ZAX where the X and Z axis have attributes, but SAX, in the position of a Y axis, does not have such identifiers.
yes? use xsz.nc
yes? sh dat
     currently SET data sets:
    1> ./xsz.nc  (default)
 name     title        I     J     K     L     M     N
 TEMP     TEMPERATURE  1:5   ...   1:3   1:7   ...   ...

but with previous 4D Ferret, the grid is xyz.
Looks like the trouble is in tm_axis_order.F, after
*     Is there a dimension before the x dimension?
*     If so create a permutation.

where a flag saying a permutation is needed was set in cases where it is not needed.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1975

Comment by steven.c.hankin on 17 Oct 2012 21:23 UTC
I'm a little surprised that "z" at the start of the axis name, zlev, wasn't used by Ferret as a last ditch heuristic to infer axis orientation.  Aren't there routines like axis_orient to draw conclusions from heuristics like this?  Can we tweak these routines to draw a last ditch conclusion from a leading "Z" in the axis name.
A second issue is the attribute  "_CoordinateAxisType", which is on the Z axis.  It is defined in John Caron's Common Data Model -- a close cousin of CF.  Ferret might as well be made to understand this attribute and its relatives.  I cannot see a down side to doing so.

Comment by steven.c.hankin on 17 Oct 2012 21:30 UTC
Have added Kevin as a cc.
Note that the satellite community has defined a netCDF standard which borrows from both CF and CDM ... which is where the _CoordinateAxisType attribute comes from.  (And why we should probably support this attribute in Ferret.)
Kevin:  I assume that the UAF crawler found this dataset acceptable, as it is build from Java netCDF code, and therefore based upon CDM, rather than CF.

Comment by ansley.b.manke on 17 Oct 2012 21:34 UTC
If _CoordinateAxisType is in a commonly used data standard, then by all means we should use it and any other attributes from that standard that make sense to use.
We used to use axis names to get directions, but with recent versions of Ferret we had decided that Ferret would NOT use axis names to determine directions but would adhere to conventions and attributes.
See item 7 of these release notes:
http://ferret.pmel.noaa.gov/Ferret/documentation/release-notes/version-6-7-release-notes
Frankly, it's been something of a headache.

Comment by steven.c.hankin on 17 Oct 2012 21:59 UTC
My recommendation:  Since supporting _CoordinateAxisType would have addressed this particular problem, lets support it, and not re-open the door about axis name-based heuristics at this time.
It would be worth a pass through http://www.unidata.ucar.edu/software/netcdf-java/reference/CoordinateAttributes.html to see if there are other readily usable coordinate attributes from CDM.  A lot of them appear to support GIS by-name coordinate coordinate transform types (e.g. LambertConformal), and it may be (much) more effort than we want to invest at this time to support them.  A few, like _CoordinateZisPositive, seem straightforward, though.

Comment by ansley.b.manke on 17 Oct 2012 22:47 UTC
The heuristics were getting us into trouble when we wanted to make sure an axis gets just one direction in all the grids it's a member of. Something like TSTATION being put onto a T axis, when it should really be on an abstract X axis. So there was good reason behind making that change.
There's a table of _CoordinateAxisType values which we can make use of; including one for "Ensemble" and one called "RunTime" that looks to be Forecast time.
http://www.unidata.ucar.edu/software/netcdf-java/reference/CoordinateAttributes.html#CoordinateAttributes
There's also a _CoordinateZisPositive attribute mentioned, which would be an analog for positive=up or down. Other than that I don't see anything that corresponds to Ferret's handling of axes and grids.

Comment by ansley.b.manke on 18 Oct 2012 00:03 UTC
I've added a check for the attribute _CoordinateAxisType when determining axis direction, and if that's there and it's Height or Pressure, look for _CoordinateZisPositive
Otherwise I have fixed the bug in tm_axis_order.F so that if there is no clue about the direction we'll use the default Ferret ordering as before.

Attachment from ansley.b.manke on 17 Oct 2012 20:47 UTC
file with an axis in the"y" direction but with no direction clues
REPLACE THIS TEXT WITH UPLOADED FILE ./attachments/TRAC_1975_GIT_1247/xsz.nc


Upgrade packages and React Rough renderer

Travis should pass now that I've clear the cache in the CI 🤞

Lezz go live!


DEMO Do not merge: add metric reader with oTel exporter

DEMO: DO NOT MERGE
Description
This PR is a part of the SPIKE ticket to investigate the filtering and aggregation of Otel traces and metrics. It is for demonstration purpose only.
Changes
When a metric endpoint (e.g. http://localhost:4318/v1/metrics) is provided in OPENTELEMETRY_METRICS_ENDPOINT, it adds a metric reader with oTel exporter to the oTel SDK, so the app can send metrics to the endpoint.
Note
Although it is planned that Amazon Managed Service for Prometheus will be used as the backend of metric storage, it would be better to output the metrics in oTel format and convert the format to Prometheus in oTel collector, rather than directly using Prometheus exporter in the metric reader.

Hi @ytcleon, thanks for doing this, it's been useful as a learning exercise 🙂 I'm going to close this PR as we now have a finished implementation in #1089. Fingers crossed we'll ship it soon!


Build Awesome Books using ES6 and Modules (rm3)

In this project, I restructured my Awesome Books app and make it more organized by using modules and ES6 syntax.
Project Requirements:

Setup project:

Create a new directory and initialize it with git
Use the npm init -y command to create a package.json file
Create the entry point for your JavaScript code called index.js
Create an index.css file for styles
Create the main index.html file and link index.js and index.css files
Create a directory called modules

Re-create the Awesome books app following these rules:

Use ES6 syntax
Divide my code into modules. Save each module in a separate file in the modules dir. Import modules in the index.js file (the more modules the better)
Keep all functionalities of the app without errors
Refactor my methods and functions to arrow functions
Use let and const in a correct way

Display the current date below the navigation bar:

Use a library Luxon
Download the script and save it to the project
Import it as a module
Use this tool with little externally curated support

General Requirements:

Check linter errors
Use the correct GitHub flow
Document my work in a professional way
Follow best practices for HTML, CSS & JavaScript
Open a pull request and ask for a review

@muneebulrehman, @mikethreels


First pass at modified LRO to include metadata

This is a simple approach, but the name of the returned type ends up
being very long.
(Ready for review in terms of general approach; more testing work required.)

Pushed change for the callback.

@evildour: Any general thoughts about this approach? Other alternatives would involve generating a new type for each long-running call, so we'd have LongRunningRecognizeOperation - there are various options for exactly how to do that, but they're all quite involved.

That was my first thought when skimming this, but I could go either way. It's kind of borderline-ugly at this point and since var is an option in many cases, it might not matter.
Would each new type contain an Operation<...> or derive from it? I would lean toward the latter so  callers would not need to do instance.Operation.Whatever. But given that the class needs to create new instances of itself, Operation<...> would need abstract Create... methods or it would have to be parameterized with a 3rd type argument: the derived type, which always seems a bit hacky to me.

@evildour: That was basically my thought process, experimenting for a while. I started off with composition - generally favouring composition over inheritance - then tried inheritance, and in every case it got really complicated.
The downsides of the proposal are only:

It avoids long return types (which we already have for pagination, mind you)
If we knew that some services didn't support cancellation or deletion, we could not generate those methods
If we ever wanted to add extra methods to the generated code, we could do so

I'm leaning more and more to this being the solution.

You mean you're leaning towards inheritance being the solution? I guess abstract/virtual creation methods are the cleanest way to do this if that's the way to go.

No, I'm leaning to this PR being the solution. I tried both composition and inheritance, and both were messy. We could easily end up with a type system which is fine so long users only use Intellisense - but which is really confusing (for very little benefit) as soon as they start looking at the documentation.

I see, got a little confused there. Ok, this make sense. Yeah, I didn't consider the documentation, but that's a good point.

This is now our plan of record, modulo objections.


Update notebook markdown descriptions

This PR adds some context to our Synapse notebooks. Two things:

I changed MCI (master case index) to MII (master incident index) because that's what it is called in Synapse
Datastore vs Data store vs DataStore? I personally don't have a preference but went with camel casing because that seemed to appear the most

I ended up going with datastore because I realized that's how it is formatted in Synapse, e.g., the datastore is called the ecr-datastore.


Deprecation warnings on ReflectionClass conctructor while generating Meta

Versions:

ide-helper Version: 2.12.3
Laravel Version: 9.27.0
PHP Version: 8.1.2

Description:
[2022-08-31 10:50:54] local.WARNING:
ReflectionClass::__construct(): Passing null to parameter #1 ($objectOrClass) of type object|string is deprecated in /path/to/project/vendor/barryvdh/laravel-ide-helper/src/Console/MetaCommand.php on line 98

[2022-08-31 10:50:54] local.WARNING:
ReflectionClass::__construct(): Passing null to parameter #1 ($objectOrClass) of type object|string is deprecated in /path/to/project/vendor/barryvdh/laravel-ide-helper/src/Console/MetaCommand.php on line 98

ReflectionClass::__construct signature from PHPStorm stubs:
/**
 * Constructs a ReflectionClass
 *
 * @link https://php.net/manual/en/reflectionclass.construct.php
 * @param class-string<T>|T $objectOrClass Either a string containing the name of
 * the class to reflect, or an object.
 * @throws ReflectionException if the class does not exist.
 */
public function __construct(#[LanguageLevelTypeAware(['8.0' => 'object|string'], default: '')] $objectOrClass) {}

Steps To Reproduce:

Enable Laravel deprecation logging
Run php artisan ide-helper:meta

Seems that is's already resolved in master branch...
Duplicates: https://github.com/barryvdh/laravel-ide-helper/pull/1279


Refactored to add premium features to ag-grid

Included premium state to ag-grid features and used regex to find premium keyword

Not sure where to find fillRight feature and I assumed it was also premium because fillDown is premium here.
I also made a this Set filtering is premium, the rest is free statement with filtering since Set Filtering is the only premium while the rest is free. Worth checking out if its capture the intent.
My main source of checking is here: https://www.ag-grid.com/javascript-data-grid/ but you could also check this if this suits you: https://github.com/ag-grid/ag-grid/tree/latest/enterprise-modules.


Cleaned up the if then statements

Set all the if-then statements to use the bash [[ (test command) by surrounding them with [[ and ]]
Removed all the -eq, replaced with ==
Fixes https://github.com/selfire1/BibleGateway-to-Obsidian/issues/23 and https://github.com/selfire1/BibleGateway-to-Obsidian/issues/21.

Hi! Thanks for contributing, sorry it took some time to come back to you.
I have added the commits for newlines and if statements. Super helpful stuff, thanks again!


UMD Wrapper

Fix for https://github.com/rackt/react-router/issues/787

There was also a small mistake in package.json: it pointed to wrong index.js.

Can you please squash into a single commit?

What is wrong with two commits? I can do that, but please provide justification, since it would be some amount of manual copy-paste...

@kirill-konshin - lookup git rebase -i to squash your commits without having to do any copying or pasting:
https://ariejan.net/2011/07/05/git-squash-your-latests-commits-into-one/

Created new PR https://github.com/rackt/react-router/pull/807


Polymer bouded property not updating - or getting reset (sometimes)

I have the following html in a polymer element
        <iron-selector attr-for-selected="step-number" selected="{{stepNumber}}">
            <page-1 id="page1"></page-1>

            <page-2 id="page2"></page-2>

            <page-3 id="page3"></page-3>

page 1 fires an event - event1, page-2 fires event2. Here's my javascript for the polymer element
function () {
  Polymer({
    is: 'workflow',
    ready: function() {
      this.stepNumber = 1;
      var firstStep = this.$.page1;
      var secondStep = this.$.page2;
      var thirdStep = this.$.page3;
      var that = this;
      firstStep.addEventListener('event1', function(e) {
        that.stepNumber = 2;                       // WORKING
      });
      secondStep.addEventListener('event2', function(e) {
        that.stepNumber = 3;                      // NOT WORKING
        that.somethingElse = 'works';                     // WORKING - persists
      });
    }
  });

This polymer element is like a workflow, every page is like a workflow step. The events are fired when the workflow step completes. For example, page-1 is a searching page. When the user clicks on search button, event1 is fired. Page-2 is a search result listing page. When one of the items in the list is clicked event2 is fired.
Here's the interesting part:
Both events get fired, the value for stepNumber gets updated inside event1 handler but not inside event2 handler. I also debugged this and inside the event2 handler the value of stepNumber DOES get updated (page-3 element gets the tag "iron-selected") but it doesn't persist. After a bunch of polymer code executes the value is back to 2.
Some info from the debugger -
polymer code that's executing after the event method is basically the code that executes the event handler, followed by a "gesture recognition" code (which i guess is the on-click), where the tag iron-selector is added to page-2 section
   var recognizers = Gestures.recognizers;

   for (var i = 0, r; i < recognizers.length; i++)
  { r = recognizers[i];
  if (gs[r.name] && !handled[r.name]) {
   handled[r.name] = true;           // in here for r.name = "tap"
  r [ type ] ( ev );                              // type = click. ev = MouseEvent. ev.target = iron-selector
   }
   }

Digging deeper -
this creates an event handler
  _createEventHandler: function(node, eventName, methodName) {
  var host = this;
  return function(e) {
  if (host [ methodName ]) {
  host[methodName](e, e.detail);
  } else {
  host._warn(host._logf("_createEventHandler", "listener method `" + methodName + "` not defined"));
  }
  };

host is iron-selector. methodName is _activateHandler where _itemActivate is called for section of page-2
_activateHandler: function(e) {
      // TODO: remove this when https://github.com/Polymer/polymer/issues/1639 is fixed so we
      // can just remove the old event listener.
      if (e.type !== this.activateEvent) {
        return;
      }
      var t = e.target;
      var items = this.items;
      while (t && t != this) {
        var i = items.indexOf(t);
        if (i >= 0) {
          var value = this._indexToValue(i);
          this._itemActivate(value, t);
          return;
        }
        t = t.parentNode;
      }
    },
_itemActivate: function(value, item) {
      if (!this.fire('iron-activate',
          {selected: value, item: item}, {cancelable: true}).defaultPrevented) {
        this.select(value);
      }

_itemActivate is where the value of stepNumber changes back to 2

Raised an issue with iron-selector/


undefined ls-remote -h -t<EMAIL_ADDRESS>

Hi
Although I don't think this is a direct issue with vue-html2pdf, unfortunately at the moment I can't install via npm as I'm getting the above error.  vue-html2pdf looks awesome, I'd love to be able to install it and use it in my application.  I am simply trying to run: npm i vue-html2pdf .
2021-01-31T07_16_15_734Z-debug.log

Can you try this solution?
Install jspdf 1.5.2: npm i<EMAIL_ADDRESS>install this plugin: npm i vue-html2pdf

Can you try this solution?
Install jspdf 1.5.2: npm i<EMAIL_ADDRESS>install this plugin: npm i vue-html2pdf

Thank you Steven! That worked !
Sent from my iPhone

On 31/01/2021, at 21:58, Kemp Steven<EMAIL_ADDRESS>wrote:

Can you try this solution?
Install jspdf 1.5.2: npm i<EMAIL_ADDRESS>install this plugin: npm i vue-html2pdf
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Support for table prefix

Use --with-prefix=prefix_ to install all voyager tables with a prefix. (Need to add documentation)
Running the whole test suite with prefix gives no error but I can't guaranty that everything works so I would tag the functionality as experimental.

Change all voyager tables with the use of helper get_prefix_table
Left unchanged slugs because that will affect also templates
Prefixable Trait applies prefix to table name
Added a test to verify install with prefix works

Closes #1014

This is a nice feature. What's the status of this? Can we use it on new projects?

Closing as this will be implemented in Voyager 2

Closing as this will be implemented in Voyager 2

Hi @emptynick , is there an expected release date for V2? thanks

Why would such a feature sit on a shelf for almost 2 years ?


personal/download.cmd

          personal/download.cmd

Originally posted by @HIGDAWGG in https://github.com/iam-py-test/my_filters_001/pull/123#discussion_r1720800317

Please refrain from spamming and other disruptive behavior.
Your pull request does not appear to solve a problem or improve the script; adding random hexadecimal digits to files is not constructive. If I am incorrect, and they do serve a purpose, please correct me.
In any case, this issue is not constructive. Please continue any discussion on the original pull request.
Thank you


menuentryswapper: enable shift withdraw/deposit for seed vault

Makes your bank withdraw/deposit options in MES work in the seed vault. Doesn't support withdraw-all-but-1 because that isn't an option for the vault so withdraw-all's in that case. Tested the options swapped for all relevant values.

@Nightfirecat Please review


Old festivals removed from search

Can you allow old festivals to be viewed in search please...I can't clone old festivals, so I need to be able to find those festivals to make that short cut.
I'm going to have to add some festivals and keep the site ticking over to some extent for the summer given this job I'm doing for Feidhlim. It's fairly urgent, so if you could look at it whenever you get a chance that would be appreciated.

I'd rather not add finished to be included in the search results because this will reintroduce the problem that removing them solved.
In case you don't remember what this problem is: as time goes on, the number of finished festivals increases steadily while the number of future festivals remains fairly constant. If finished festivals are included in the search results, they dominate future festivals, but in general users are only interested in the latter. So if finished festivals are included in the search results indefinitely, the data becomes dominated by irrelevant data. So the current approach is to remove festivals from the search results once the festival is 6 months old.
However, you can still access these festivals from the festival list page once you uncheck the "Future Festivals Only" box. So you could load a list of all Irish/UK/European festivals, and then use the browser's search feature (Ctrl + F) to search for the festival by name. Is this an acceptable compromise?

Closing this due to non-response.


IndexError: list index out of range

Hi All,
I see many errors in my log:
I use add-on 0.0.4 on HA 2020.12.2
2021-01-05 18:35:26 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 119, in _handle_refresh_interval
    await self.async_refresh()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 193, in async_refresh
    update_callback()
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 245, in _handle_coordinator_update
    self.async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 296, in async_write_ha_state
    self._async_write_ha_state()
  File "/usr/src/homeassistant/homeassistant/helpers/entity.py", line 320, in _async_write_ha_state
    sstate = self.state
  File "/usr/src/homeassistant/homeassistant/components/binary_sensor/__init__.py", line 158, in state
    return STATE_ON if self.is_on else STATE_OFF
  File "/config/custom_components/satellitetracker/binary_sensor.py", line 116, in is_on
    next_pass = self.coordinator.data["visual_passes"][0]
IndexError: list index out of range

I'm assuming you have no upcoming visual passes showing. Will update and put in a new release to check for that condition shortly.

I'm assuming you have no upcoming visual passes showing. Will update and put in a new release to check for that condition shortly.

Fixed in 0.0.5

Fixed in 0.0.5


Closing system Popups

Hi Everyone, thanks for this amazing tool that I have enjoyed a lot automating some stuff around.
I have a case where the customer website shows everything on popups and have manage to grab all the files required for each iteration. The problem resides that I need to close all the previous pop-up to start a new iteration. How can this be done? The only option I found was to perform a close, but that means then to log again into the system which is not very efficient
Thanks in advance for any ideas

Hi @boeschl, how would you normally do the process of closing popups? Maybe you can try to automate in the same way.
If by popup you mean is a new tab, you can try using r.keyboard('[ctrl]w') or something to that effect to close it. But be sure to do something like r.click('image.png') to make sure the Chrome browser is made to be in the foreground to 'receive' the keystrokes to close.

Thanks @kensoh it work perfectly!! Well initially closed the program itself then actually moved the focus correctly


getService errback fix

Changes the DfpUser.prototype.getService api to accept a node-style callback to make error handling possible.
This is a breaking change for existing users. If you're concerned about this, I can tweak this to support single-argument callbacks as well. If you're ok with the breaking change, not sure if you want to increment the major version or not since you're not yet 1.0.
Addresses issue https://github.com/ShinyAds/node-google-dfp/issues/17.

@ahaurw01 Thanks for the commit. I think it would be better to allow single-argument callback -because of the breaking change. I'd really like to merge and publish, think it's a good change.

Cool, thanks for the quick feedback @ajsouza. I'll adjust to be backwards-compatible to see what you think of the approach. What do you think of keeping the README and examples showcasing the errback style?

@ajsouza Updated. Tested locally - seems to be working as expected.

Ok. I merged it in, will test then publish to NPM. Thanks a lot @ahaurw01 .

Sweet, thanks!!


[FLINK-20650][k8s] Remove "native-k8s" command and add bash wrapper for JobManager and TaskManager container args

What is the purpose of the change
native-k8s command has been removed in https://github.com/apache/flink-docker/pull/49. So when the Flink client create the JobManager deployment and TaskManager pod, the arguments needs to be changed accordingly.
A typical container spec looks like following.
Containers:
  flink-job-manager:
    Container ID:  docker://e3d57ca68e90c2efcbccff5ddf109c3008e292636cca8b9355b7dd2f73c56ae2
    Image:         registry.cn-beijing.aliyuncs.com/streamcompute/flink:1.12.0-debug
    Image ID:      docker-pullable://registry.cn-beijing.aliyuncs.com/streamcompute/flink@sha256:dfed8ea21ae56607286688629211cb29d5aee65fca26402904590383ee968331
    Ports:         8081/TCP, 6123/TCP, 6124/TCP
    Host Ports:    0/TCP, 0/TCP, 0/TCP
    Command:
      /docker-entrypoint.sh
    Args:
      bash
      -c
      $JAVA_HOME/bin/java -classpath $FLINK_CLASSPATH -Xmx654311424 -Xms654311424 -XX:MaxMetaspaceSize=268435456 -Dlog.file=/opt/flink/log/jobmanager.log -Dlogback.configurationFile=file:/opt/flink/conf/logback-console.xml -Dlog4j.configuration=file:/opt/flink/conf/log4j-console.properties -Dlog4j.configurationFile=file:/opt/flink/conf/log4j-console.properties org.apache.flink.kubernetes.entrypoint.KubernetesApplicationClusterEntrypoint -D jobmanager.memory.off-heap.size=134217728b -D jobmanager.memory.jvm-overhead.min=201326592b -D jobmanager.memory.jvm-metaspace.size=268435456b -D jobmanager.memory.heap.size=654311424b -D jobmanager.memory.jvm-overhead.max=201326592b
    State:          Running
      Started:      Fri, 18 Dec 2020 15:10:00 +0800
    Ready:          True
    Restart Count:  0
    Limits:
      cpu:     1
      memory:  1200Mi
    Requests:
      cpu:     1
      memory:  1200Mi
    Environment:
      ENABLE_BUILT_IN_PLUGINS:  flink-oss-fs-hadoop-1.12.0.jar
      _POD_IP_ADDRESS:           (v1:status.podIP)
    Mounts:
      /opt/flink/conf from flink-config-volume (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-t8nfg (ro)

Brief change log

Remove "native-k8s" command and add bash wrapper for JobManager and TaskManager container args

Verifying this change

The unit tests have been updated to make them pass
All the K8s e2e tests should work without any change
Manually test in minikube

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@xintongsong Thanks for the review. I have integrated the comments and force pushed.

LGTM. I'll merge this after AZP gives green light.


Update GOV.UK Frontend to 2.8.0

You can preview this change here:
Built with commit 21e3bc8146eefe5da450f21c86031d4cbcc030ab
https://deploy-preview-819--govuk-design-system-preview.netlify.com


Write a GO program to check vowel

Description
Write a GO program to check vowel
Vowel check is a simple program to check whether a character is a vowel or not.
Input  : a
Output : Vowel

How to contribute

Save the solution in check_vowel.go file
Add check_vowel.go file in check-vowel folder

!assign

!assign


[SPARK-30302][SQL] Complete info for show create table for views

What changes were proposed in this pull request?

Add table/column comments and table properties to the result of show create table of views.
Does this PR introduce any user-facing change?

When show create table for views, after this patch, the result can contain table/column comments and table properties if they exist.
How was this patch tested?

add new tests

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/20340/
Test PASSed.

Test build #115539 has started for PR 26944 at commit b48eaa6.

Test build #115539 has finished for PR 26944 at commit b48eaa6.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/115539/
Test FAILed.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/20372/
Test PASSed.

Test build #115574 has started for PR 26944 at commit b48eaa6.

Test build #115574 has finished for PR 26944 at commit b48eaa6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/115574/
Test PASSed.

Test build #115592 has started for PR 26944 at commit 1519413.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/20391/
Test PASSed.

Test build #115592 has finished for PR 26944 at commit 1519413.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/115592/
Test PASSed.

@dongjoon-hyun @HyukjinKwon do you have time to take a look? Sorry to disturb you on Holiday :)

ping @dongjoon-hyun @HyukjinKwon. Could you spare some time to review this?

Test build #116091 has started for PR 26944 at commit c054672.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/20884/
Test PASSed.

Test build #116091 has finished for PR 26944 at commit c054672.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/116091/
Test PASSed.

Thanks for the check, @HyukjinKwon! Merged to master.

@wzhfy  do you have time to make a pr for https://github.com/apache/spark/pull/26944#discussion_r360193294?

Sorry for missing pings here, @maropu and @wzhfy. I was sway since Dec. 20th~

nvm, happy new year, @dongjoon-hyun ~

@wzhfy do you have time to make a pr for #26944 (comment)?

@maropu Yes, I will submit a pr in several days.

Thanks~

Happy new year, @maropu . 😄


Java Home setting wants an URI, but it's actually supposed to be a path

Whether in the settings panel:

or in the file:

the setting wants the path to be an URI, but only works when I provide a filesystem path. Prefixing with file:// actually causes the TLC not to run at all, and the error to appear:

The fix is available in v1.5.3-alpha.1

The fix is available in v1.5.3-alpha.1

@kubukoz, thanks for the report and for the fix!

@kubukoz, thanks for the report and for the fix!


Add International Institute of Information Technology (I²IT).

International Institute of Information Technology (I²IT) is a college in Pune, Maharashtra, India affiliated with Savitribai Phule Pune University. The college offers Bachelor of Engineering courses in Electronics and Telecommunication, Computer Engineering, and Information Technology.
Website: https://www.isquareit.edu.in/
Programmes Offered: https://www.isquareit.edu.in/programmes-offered/

@suvijo First stage of verification passed, official domain is isquareit.edu.in as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@suvijo Pull request merged. Thank you.


Issue with MFA

Hi,
I enabled MFA on my account and since then I am unable to do anything.  According to Okta, the login was successful.  What I assume I should be getting is the list of accounts and roles to select.  We have multiple linked accounts and roles.  Could it a race issue of some sort?
$ awscli help
Username: xxxxxxx
Password:
Multi-Factor authentication is required. Please select a factor to use.
Factors:
[ 1 ] : push
[ 2 ] : Okta Verify
Selection: 1
Push Factor Authentication
Waiting for you to approve the Okta push notification on your device...
Waiting for you to approve the Okta push notification on your device...
Waiting for you to approve the Okta push notification on your device...
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Exception in thread "main" java.lang.RuntimeException: You do not have access to AWS through Okta.
Please contact your administrator.
at com.okta.tools.saml.OktaSaml.getSamlResponseForAws(OktaSaml.java:54)
at com.okta.tools.saml.OktaSaml.getSamlResponse(OktaSaml.java:44)
at com.okta.tools.OktaAwsCliAssumeRole.run(OktaAwsCliAssumeRole.java:88)
at com.okta.tools.awscli.main(awscli.java:33)

App-level MFA policies are not supported. For details see #25

I see.  So just to recap: setting up MFA "Sign On Policy" in individual applications isn't supported.  Thank you.


Add device_id to EventHubEvent

Please add a property device_id to EventHubData similar to EventHub reader implementation (https://github.com/Azure/azure-event-hubs-python/blob/master/azure/eventhub/common.py).

Duplicate of https://github.com/Azure/azure-webjobs-sdk/issues/2068

Reopening as there will be Python specific tasks once the linked issue is fixed.

@elprans quick update - the issue is now unblocked for you to make the language worker changes.

Issue https://github.com/Azure/azure-webjobs-sdk/issues/2068 is fixed. Next runtime release will include the fix.

@elprans do you have an update on this?

Unfortunately, runtime release got delayed. ETA for complete roll out is end of this week.


Add Castle Safe App

Revision checks

[x] Your Safe App include a manifest.json file at the root with the required data
[x] The app can be loaded as a custom Safe App in the Apps section of https://gnosis-safe.io/app
[x] The app auto-connects to the Safe
[x] You are able to trigger and execute one transaction with a Safe
[x] RPC requests are optimized (not triggering many requests in a very short time period)

Name/Description

Name: 0xNFTs by Castle
Description: NFT Marketplace Aggregator: Buy, list and transfer NFTs across OpenSea and all major markets.

Type

New addition

Compatible Networks
- Mainnet

Code for review
Code repository for Castle's Safe App
IPFS hash/App URL
Link to Castle's Safe App
Desired date
We are looking to get Castle's Safe App on the Gnosis Safe UI as soon as possible.

Complete initial review & testing: Aug 19th
Target deployment & launch: Aug 29th - Sept 5th

Hi guys! I can see that the safe app connects to my safe as expected but could we get rid of this connection pop up?

It it pops up every time the app is opened, I navigate to /marketplace or try to send or create a new listing.
Cheers!

Hi there! Thanks for flagging - you may need to connect your EOA / signing wallet to Gnosis UI to hide that popup.
Will also review our code to ensure that the popup isn't triggered unnessarily!

Anytime! Can confirm that the pop up is there when my wallet is connected to the safe interface. Here is a lil video:
https://user-images.githubusercontent.com/92332710/191517403-15d5b9e8-7733-4c84-beae-7d2c86f1aebd.mp4
Cheers!

Still can see the pop up unfortunately. I even asked a couple of my teammates to give it a quick check to be completely sure and we were all able to reproduce it from the shared link :(

Morning! I was doing some debugging yesterday and the connection pop up is present for us because we don't have the app connected to Metamask. Connecting to it does the trick of not showing it anymore (which would explain why you don't see it) but in the context of safe apps this metamask (& WC) connection should be ignored.
Removing the Castle connection on metamask is prompting the metamask connection everytime I open the app too. I think that if you do so it should pop up for you as well. Cheers!

Hi there! I think I was able to remove the Castle connection to MM - can you try it out now! Seems to work for me fine.

Much better, thanks! I am able to see it in only one place now:
https://user-images.githubusercontent.com/92332710/193754106-b3a6098b-2970-4ca2-bd29-1ff63cd8755d.mp4

App was published


108 icons for id links

This PR adds icons to Wikidata labels in corpora indices. Fixes #108

Well done. Thanks!


[SPARK-22370][SQL][PYSPARK] Config values should be captured in Driver.

What changes were proposed in this pull request?
ArrowEvalPythonExec and FlatMapGroupsInPandasExec are refering config values of SQLConf in function for mapPartitions/mapPartitionsInternal, but we should capture them in Driver.
How was this patch tested?
Added a test and existing tests.

Test build #83118 has started for PR 19587 at commit 0918872.

cc @BryanCutler @icexelloss @cloud-fan @gatorsmile

Test build #83118 has finished for PR 19587 at commit 0918872.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83118/
Test PASSed.

LGTM. +1

Test build #83130 has started for PR 19587 at commit b47f55b.

Test build #83130 has finished for PR 19587 at commit b47f55b.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83130/
Test PASSed.

LGTM, good catch!

LGTM

Could you add a comment in abstract class QueryPlan's conf? Hopefully, the others will read the comment before using it.

Test build #83154 has started for PR 19587 at commit ea20b03.

Test build #83154 has finished for PR 19587 at commit ea20b03.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83154/
Test FAILed.

Test build #83160 has started for PR 19587 at commit 624736e.

LGTM too

Test build #83160 has finished for PR 19587 at commit 624736e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/83160/
Test PASSed.

LGTM, merging to master!


Lucas newbee!!!

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Joao Gavazzi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Fixes: #9686.

Merged, thanks @shubhamdhama!


Whether the workload needs to follow the job changes

The current workload design is that if the configuration of workload and job is found to be inconsistent, the current workload will be deleted and re-created.
If there are some special scenarios where I need to change the job configuration, it will cause my job to be re-queued, which is not very reasonable from a product perspective, the expectation is that the workload will not be re-created but will change as the job changes.

Yes, I'll modify it when the job is queued or suspended

That sounds feasible.
@trasc, could you investigate if it's possible?

Yes, it should be doable.
/assign

/assign