Responsive graphs (question)

What would be the preferred/best practice way to make the graphs dynamic in width/height for a responsive design?

Hey @bytewiz
This is a pretty complex question! On the ostensible top layer (how to make a visualization that simply scales well with size changes), i tend to prefer making a stateful wrapper around my chart which measures itself on window size change and then update my visualization as appropriate. I am going to work on adding an example of this technique to one of the examples.
Beyond that there are some interesting ledgibility questions about how to make a visualization that scales well with pixel and data density. Check out this demo http://nrabinowitz.github.io/rdv/, for some cool thoughts on the matter. (also, I am in the process of re-producing that example in react-vis, checkout this PR https://github.com/uber/react-vis/pull/253).
If this isn't enough, can you tell me more about your use case? Maybe I can point you in the right direction?

@mcnuttandrew looks like what I need :) I have currently done it somewhat the same way as you proposed by programmatically calculate screensize and then "shrink" or "scale up" the graph by that calculation.
though I thought there might be a better way, and true I see that it becomes a problem when scaling down and still display the data points.
Thanks 👍

Another option is svg's viewBox attribute, which allows your entire graphic to scale independently of the coordinate system. This is easy to use and works great for many things but has the downside of scaling any <text> elements in addition to scaling the graphic, which is usually not what you want.
CSS-Tricks has a good article discussing the pros and cons of several different solutions, but as @mcnuttandrew pointed out the easiest solution in React is often just to wrap a higher-order component and treat any corner-cases of your design as responsive breakpoints in JS.

All good stuff, I'll throw another recipe into the mix - I've had success with wrapping my XYPlot's in a react-dimensions component. It's an HOC that simply provides width / height as it changes. If you then use flexbox for your container layout, you'll get fluid width and height which react-dimensions picks up on, and you can simply pass it to react-vis.

there's also the makeWidthFlexible function.
import {
  makeWidthFlexible,
  XYPlot
} from 'react-vis';

const FlexibleXYPlot = makeWidthFlexible(XYPlot);

in the above FlexibleXYPlot behaves exactly like XYPlot but no width needs be passed. Instead, it uses the size of its containing component.
makeWidthFlexible works with width, as the name implies - in our use cases it made more sense to change the width of a chart and keep height fixed.

I've just implemented the makeWidthFlexible HOC, and it took me a little while to work out how to use it correctly. For anybody else wondering, the trick is to have your plot component accept a prop named width and pass this on to the XYPlot. You also need to explicitly declare width as a propType on your base component, otherwise propTypes validation will fail (see https://github.com/uber/react-vis/blob/master/src/make-vis-flexible.js#L97).
Example:
render () {
  const Plot = ({ width }) =>
    <XYPlot
      height={180}
      width={width}>
      <VerticalGridLines />
      <HorizontalGridLines />
      <XAxis />
      <YAxis />
      <LineSeries data={measurements} />
    </XYPlot>

  Plot.propTypes = { width: React.PropTypes.number }
  Plot.displayName = 'TimeSeriesLineChartPlot'
  const FlexibleXYPlot = makeWidthFlexible(Plot)

  return (
    <FlexibleXYPlot />
  )
}

Is there a plan to also expose "makeHeightFlexible" too? I'm try to use a HorizontalBarSeries chart to function as a vertical indexing sidebar, and found it would be useful to auto-determine its height.

This is great!  When you resize the screen, the experience is a little choppy/bouncy...making it nice/smooth would be excellent..thank you!

Hey @julesbond007 can you say more about what you are seeing? Also, would you mind opening a new ticket about it?

Hey all,
Now that flexible plots are exposed at the top level of the library (http://uber.github.io/react-vis/#/documentation/api-reference/flexible-plots) I think we can close this issue. Discussion can continue under fold, or issue can be re-opened if folks disagree.

How about responsive Stankey Diagram?

I think it's also pending the radial chart:
https://github.com/uber/react-vis/issues/620

I've also tried with "ranking" chart (XYPlot with HorizontalBarSeries) and it doesn't seems to work. I've used makeVisFlexible, makeWidthFlexible and same result.
Before  class declaration:
const FlexibleXYPlot = makeVisFlexible(XYPlot);

Render method:
render() {
        let data = this.props.data ? _.orderBy(this.props.data, 'x', ['asc']) : this.props.data;

        data = (this.sort === 'desc') ? data.slice(0 - this.top) : data.slice(0, this.top);

        const ppp = responsiveUtilsService.getPPP(this.innerWidth, this.innerHeight, data, 'HEIGHT');
        this.featuresToRender = responsiveUtilsService.filterFeatures(BARCHART_FEATURES, ppp);
        this.xRange = [0, this.innerWidth];
        this.yRange = this.sort === 'asc' ? [0, this.innerHeight] : [this.innerHeight, 0];

        return (
            <FlexibleXYPlot
                yType="ordinal"
                xType="linear"
                margin={this.margin}
                width={this.width}
                height={this.height}
            >
                {this.featuresToRender.xaxis && <XAxis orientation="top"/>}
                {this.featuresToRender.yaxis && <YAxis />}
                {this.featuresToRender.bars && (
                    <HorizontalBarSeries
                        colorType="literal"
                        xRange={this.xRange}
                        yRange={this.yRange}
                        data={data} />
                )}
            </FlexibleXYPlot>
        );
    }

Hey all,
Now that flexible plots are exposed at the top level of the library (http://uber.github.io/react-vis/#/documentation/api-reference/flexible-plots) I think we can close this issue. Discussion can continue under fold, or issue can be re-opened if folks disagree.

I think the link quoted has been updated since then, the new link is a great help: https://uber.github.io/react-vis/documentation/api-reference/flexible-plots

@wzup
to make a react-vis sankey responsive (horizontally and vertically) use the makeVisFlexible() helper as explained here: https://uber.github.io/react-vis/documentation/api-reference/flexible-plots
little code example:
   const FlexibleSankey = makeVisFlexible(Sankey);    return (         <FlexibleSankey           nodes={nodes}           links={links}           nodePadding={20}           align='left'           layout={500}         />   )

Where is the documentation for this?
I don't understand the reason to pass width props into the width property to make flexible.
I just use
  const FlexibleGraph = makeVisFlexible(XYPlot);
  return (
    <FlexibleGraph height={300}>
      <VerticalGridLines />
      <HorizontalGridLines />
      <XAxis />
      <YAxis />
      <AreaSeries
        className="area-series-example"
        curve="curveNatural"
        data={data}
      />
    </FlexibleGraph>
  );

I'm doing this:
  componentDidMount() { //add listener to do thing
    this.updateWindowDimensions();
    window.addEventListener('resize', this.updateWindowDimensions);
  }

  componentWillUnmount() { //remove event listener after done doing thing
    window.removeEventListener('resize', this.updateWindowDimensions);
  }

  updateWindowDimensions = () => {
    this.setState({ width: window.innerWidth });
  };

// then in render() (I'm using Sunburst from react-vis):
<Sunburst
          height={this.state.width / 4}
          width={this.state.width / 4}
/>
// using width for both dimensions because this component is a circle.

hope it helps.

It looks like FlexibleWidthXYPlot, FlexibleHeightXYPlot, and FlexibleXYPlot have been added (probably since this issue was active) in case this is useful for anyone else! https://uber.github.io/react-vis/documentation/api-reference/flexible-plots


Android Logs storage

Hi,
I'm quite new with Android app, how can I see/store android.util.Log logs?
Thank you

You can use Logcat for that


Added profile card

I have created a profile card with HTML and CSS.

@shital-09
you done changes properly??, because i am not able to find your folder.

@shital-09
you not add your name into CONTRIBUTIN.md file


Better obs-fold handling in parser

Currently the rfc7230 utilities like ext_list use an internally allocated std::string to handle the case where an HTTP field value contains an obsolete line continuation. We can eliminate the need for this allocation if the parser itself handles the line continuation simply by replacing the CRLF with spaces, or optionally deleting the CRLF and extraneous spaces.
This would also require a memory allocation. The parser already allocates memory for the case where the input buffer sequence is discontiguous, we could use the same buffer.  To satisfy some user desires for a non-allocating implementation, a new parser option can be added which makes any received obs-fold illegal, generating an error.
Finally the rfc7230 field value adapters can be modified to no longer need an additional std::string.

Hmm I was mistaken, the rfc7230 adapters use std::string to remove escaped characters from quoted strings. This will require more thought.


Annotate API calls via wrapper/thunk functions

I tried to run the MSDN Annotations plugin but it turns out that it does not work well with IDA 7.1 Pro.
It creates a Segment .msdn with content but it does not change the Symbols as expected.

Does it fail to annotate all calls or just this one?
It appears that the plugin fails to identify the function call. Is there a cross-reference from the import table to the CreateFileA call?

It fails to annotate everything. But, I can see the additional segment called .msdn.

Is there a cross-reference from the import table to the CreateFileA call?
What do you mean by that?

I attached to files I checked.
reverseMe.exe.zip

Here is the IDA output I get

@mr-tz Do you have any idea how to solve this?

The sample calls the functions from the import address table via an intermediate thunk function. For example the call to CreateFileA is made via the function at offset 0x401283. The plugin does not currently support the annotation of function arguments for such calls.

Could you please add this to the plugin?

It shouldn't be too hard, but I cannot promise a solution soon. We will keep this issue open to track it.

@mr-tz Could you give me some hint where to start, then I will try to add it and push a change?

Thanks, that would be great! One solution would be to add the respective call offsets to the library_calls dictionary.

Well, then you have to give some more details on what to do.

you need to update the implementation of the get_imports function called here: https://github.com/fireeye/flare-ida/blob/master/python/flare/IDB_MSDN_Annotator/init.py#L527
you should enumerate functions and detect when they are thunks to other imports, mark them as such, and find a way to update the library_calls dictionary, as @mr-tz suggested. if you have trouble following the information flow, try adding some calls to logging.debug(…) so you can see the data formats.

Any more hint which APIs are relevant here?

I would probably look at the following functions first:

idc.get_func_flags() using idc.FUNC_THUNK
idc.get_func_name()
idautils.Functions() might help as well


Precompilation staleness check with docker still not working in 0.4.1?

I've started to use 0.4.1 to get this change, about issues with modification time checks for staleness with precompilation:  https://github.com/JuliaLang/julia/pull/13613.
However, it still doesn't work for me - curious if anyone else seeing anything different.
Note that I'm forcing precompilation by adding a "using" statement right after the Pkg.add() in include_packages here:
https://github.com/JuliaLang/JuliaBox/blob/master/container/interactive/setup_julia.sh

Staleness check doesn't seem to be an issue anymore.
JuliaBox package bundles now contain precompiled packages after https://github.com/JuliaLang/JuliaBox/commit/0b70e6e70f626a987aa70adc59289d923be117e3


Case sensitivity of property names in query is compromised when the property has an index

Hi, I faced this issue while executing a query. The case sensitivity of property name is compromised when there is an index for that property.
e.g.
Assume there is a property "rolename" in class Role.
SELECT FROM ROLE WHERE ROLENAME='USER'
and
SELECT FROM ROLE WHERE rolename='USER'
works when there is an index for ROLE.rolename.
But
SELECT FROM ROLE WHERE ROLENAME='USER'
does not work when there is no index for ROLE.rolename.
So the case sensitivity validation seems to be not working when there is an index for the property.
Please let me know if any more information is needed.
Stack Overflow Discussion

Hi @sachintaksande
It seems to be a bug, I'll take a look at this asap and I'll let you know
Thanks
Luigi

Hi @sachintaksande
the problem does not seem to be on the index, but on the schema.
We are investigating it
Thanks
Luigi

The problem is on how the schema is implemented indeed. We fixed this problem in v 3.0, but we cannot backport the fix to 2.2 without breaking backward compatibility
Closing
Thanks
Luigi


Default testnet denom metadata

Resolves #229
Default values in testnet setup as a template in genesis:
{
  "metadatas": [
    {
      "description": "The native staking token of test chain",
      "denom_units": [
        {
          "denom": "utgd",
          "aliases": [
            "microtgd"
          ]
        },
        {
          "denom": "tgd",
          "exponent": 6
        }
      ],
      "base": "utgd",
      "display": "tgd"
    }
  ],
  "pagination": {
    "total": "1"
  }
}

Thanks for the link here: https://github.com/confio/tgrade/issues/229#issuecomment-1033505511 which helps put in context


Revert "Integration tests for @OnTouch, @OnItemClick and @OnItemLongClick"

Reverts JakeWharton/butterknife#1477

Why?


Installation error from source code with cuda7.5

For bugs or installation issues, please provide the following information.
The more information you provide, the more easily we will be able to offer
help and advice.
Environment info
Operating System:
Ubuntu 14.04
Installed version of CUDA and cuDNN:
(please attach the output of ls -l /path/to/cuda/lib/libcud*):
~$ ls -l /usr/local/cuda/lib64/libcud*
-rw-r--r-- 1 root root 322936  8月 16  2015 /usr/local/cuda/lib64/libcudadevrt.a
lrwxrwxrwx 1 root root     16  8月 15  2015 /usr/local/cuda/lib64/libcudart.so -> libcudart.so.7.5
lrwxrwxrwx 1 root root     19  8月 15  2015 /usr/local/cuda/lib64/libcudart.so.7.5 -> libcudart.so.7.5.18
-rwxr-xr-x 1 root root 383336  8月 15  2015 /usr/local/cuda/lib64/libcudart.so.7.5.18
-rw-r--r-- 1 root root 720192  8月 16  2015 /usr/local/cuda/lib64/libcudart_static.a
【cudnn】:
/usr/local/include/cudnn.h
/usr/local/lib/libcudnn.so.5
/usr/local/lib/libcudnn.so.5.0.5
/home/guorui/soft/cudnn_v5/cuda/include/cudnn.h
/home/guorui/soft/cudnn_v5/cuda/lib64/libcudnn.so
/home/guorui/soft/cudnn_v5/cuda/lib64/libcudnn.so.5
/home/guorui/soft/cudnn_v5/cuda/lib64/libcudnn.so.5.0.5
If installed from source, provide

The commit hash (git rev-parse HEAD)
tensorflow version: download 2017.1.12
The output of bazel version
bazel-0.4.3-installer-linux-x86_64.sh

Logs or other output that would be helpful
(If logs are large, please upload as attachment or provide link).
$ ./configure
Please specify the location of python. [Default is /usr/bin/python]:
Do you wish to build TensorFlow with Google Cloud Platform support? [y/N] N
No Google Cloud Platform support will be enabled for TensorFlow
Do you wish to build TensorFlow with Hadoop File System support? [y/N] N
No Hadoop File System support will be enabled for TensorFlow
Do you wish to build TensorFlow with the XLA just-in-time compiler (experimental)? [y/N] N
No XLA JIT support will be enabled for TensorFlow
Found possible Python library paths:
/usr/local/lib/python2.7/dist-packages
/usr/lib/python2.7/dist-packages
Please input the desired Python library path to use.  Default is [/usr/local/lib/python2.7/dist-packages]
Using python library path: /usr/local/lib/python2.7/dist-packages
Do you wish to build TensorFlow with OpenCL support? [y/N] N
No OpenCL support will be enabled for TensorFlow
Do you wish to build TensorFlow with CUDA support? [y/N] y
CUDA support will be enabled for TensorFlow
Please specify which gcc should be used by nvcc as the host compiler. [Default is /usr/bin/gcc]:
Please specify the CUDA SDK version you want to use, e.g. 7.0. [Leave empty to use system default]:
Please specify the location where CUDA  toolkit is installed. Refer to README.md for more details. [Default is /usr/local/cuda]:
Please specify the Cudnn version you want to use. [Leave empty to use system default]:
Please specify the location where cuDNN  library is installed. Refer to README.md for more details. [Default is /usr/local/cuda]: /home/guorui/soft/cudnn_v5/cuda
libcudnn.so resolves to libcudnn.5
Please specify a list of comma-separated Cuda compute capabilities you want to build with.
You can find the compute capability of your device at: https://developer.nvidia.com/cuda-gpus.
Please note that each additional compute capability significantly increases your build time and binary size.
[Default is: "3.5,5.2"]: 5.2
#Create the pip package and install
bazel build -c opt --config=cuda --local_resources 2048,.5,1.0 //tensorflow/tools/pip_package:build_pip_package
【error message】:
INFO: From Compiling tensorflow/core/kernels/cwise_op_gpu_mul.cu.cc:
Killed
ERROR: /home/guorui/soft/code/tensorflow/tensorflow/tensorflow/core/kernels/BUILD:2081:1: output 'tensorflow/core/kernels/_objs/cwise_op_gpu/tensorflow/core/kernels/cwise_op_gpu_mul.cu.pic.o' was not created.
ERROR: /home/guorui/soft/code/tensorflow/tensorflow/tensorflow/core/kernels/BUILD:2081:1: not all outputs were created or valid.
Target //tensorflow/tools/pip_package:build_pip_package failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 1555.053s, Critical Path: 1466.64s
Thank you very much.

I have found the problem.
Just add: --local_resources 2048,.5,1.0


fix(assets): rebuild assets for new developement

The merged pull requests for i18n (#353), user settings saving (#380)
and dependencies update (#381) require to rebuild the assets.

I think the dist/ should not be in sources but it needs #385 to be solved first.
So, I did a rebuild for now to make it possible to install directly from git without the need of npm & co.


Should I make consensus sequence before using Clipkit or after ClipKit

Dear Clipkit Developer
I am interested using Clipkit before running IQTree. But I also need to generate Consensus sequences for primer designing. Should I used Clipkit trimmed alignment for Consensus Sequence generation or not?
Also, you autodetect, detects my Nucleotide sequence as protein sequence:
Determining smart-gap threshold...

-------------
| Arguments |
-------------
Input file: ../05_postOutlierDetection/halign3.aln (format: fasta)
Output file: ../05_postOutlierDetection/halign3.aln.clipkit (format: fasta)
Sequence type: Protein
Gaps threshold: 0.9986
Trimming mode: kpic-smart-gap
Create complementary output: False
Create log file: True

------------------------
| Processing Alignment |
------------------------

Hi Rohit,
Thank you for using ClipKIT!
I would not recommend trimming the alignment before consensus sequence generation.
Also, can you please share your file here so I can investigate the autodetect error? Alternatively, please feel free to email me.
best,
Jacob

Thanks for your input @JLSteenwyk. Here is the file. I used Halign3 for aligning the sequences.
halign3.zip

Hi Rohit,
ClipKIT detects Amino Acids because your sequences have a lot of non-canonical characters. All unique characters include: -, A, C, G, K, M, N, R, S, T, W, Y.
Although these are acceptable nucleotide characters, in my experience, it is relatively uncommon to see all of these in an alignment file. If I am mistaken, please let me know. As a result, I recommend specifying that your alignments are of nucleotide characters.
best,
Jacob


KAFKA-14197: use raft error RaftBatchTooLargeException instead of exi…

…sting API error
When writeEvent failed, we'll try to renounce the controller state. But if the error is an ApiException, we'll just throw exception. The problem happened when trying to allocate buffer for the batch, we might encounter RecordBatchTooLargeException. The RecordBatchTooLargeException thrown from BatchAccumulator#append is one of ApiException, and that will enter here without renounce.
Fix it by creating new RaftBatchTooLargeException since this exception thrown by BatchAccumulator should be part of RaftException, not ApiException.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Not sure if this change makes sense. Please help comment. Thanks.
@dengziming @hachikuji @jsancio

I think this can fix the problem, but I'm also wondering why not call renounce when we throw anApiException.

This is already fixed, we can close it.

Agree. Closed


Referenced Sniff: <my_custom_sniff_name> doesn't exist

I am trying to exclude my custom sniff in the phpcs configuration xml file, i get the referenced sniff doesn't exist error.
I understand that the error is due to the fact that i haven't installed my sniff yet, but i have a specific usecase that requires this. I want to able to check if that sniff is installed, if yes then it needs to be excluded from phpcs via the configuration xml file. Is it possible to acheive this? I am using the latest version 3.9.0.
Thank you

@naveen17797 As far as I can think of, that's not possible at this time.
Can you expand a bit on your usecase ?

@jrfnl  Thanks, i will look for alternatives


Everytime I win a match, it disconnects me

The title is the question. Everytime I win a match, I win, but I get an internal server error.

Same it happen on me:(

Send the error!!!


[ENH] Add a way to set Py_mod_gil slot for modules defined in cython

The free-threaded python build requires that modules explicitly declare whether or not they support running without the GIL using either PyUnstable_Module_SetGIL for single-phase init or the Py_mod_gil slot for multi-phase init.
If the slot isn't set, python warns at runtime about this and re-enables the GIL, unless you force the interpreter to disable the GIL:
In [1]: from numpy import *
<frozen importlib._bootstrap>:488: RuntimeWarning: The global interpreter lock (GIL) has been enabled to
load module 'numpy.random.bit_generator', which has not declared that it can run safely without the GIL.
To override this behavior and keep the GIL disabled (at your own risk), run with PYTHON_GIL=0 or -Xgil=0.

I tried looking at doing that from inside the definition of a cython module in the cython language, and I came to the conclusion that cython needs to handle this in the compiler, since the changes we need to do to the module need to be in the module definition in C or C++.
I don't think cython can just automatically say that modules rely on the GIL or not, since code may implicitly be locking around the GIL. It makes sense to me to let users explicitly opt-in with a global or module-local compiler directive.

That makes sense to me.

I can get started on implementing this.

I assume this would need both a source-level directive and a front-end flag for cython/cythonize?
For NumPy and SciPy I'd expect we would want to use it as cython --free-threaded-safe (or whatever the flag ends up being called).

Souce-level directives are automatically command line arguments to the cython command via -X so I don't think anything special needs doing there. (I can't remember about cythonize off the top of my head).
I'm not quite sure why you'd want to use the command-line argument as most of the time though? It seems more like something the source code should know rather than the the build system. (It would be a no-op for non-free-threaded Python builds so wouldn't break anything to set it universally once you'd decided that an individual file was good).

Ah yes, good point about -X. Nice and easy then:)
CLI arguments: because (a) easier to audit since we have way more .pyx files than build config files, and (b) a cleaner end state (a single flag somewhere, right next to -3) rather than an annotation in every single source file. The source file annotations are also easy to forget when a contributor adds a new .pyx file.

Minor logistical request: could this issue and the linked PR please be labelled with nogil CPython?


0x3a support

The tgt code is under GPL, but the tcmu-runner is under Apache. So we cannot integrate the tgt code.
Please see: https://github.com/open-iscsi/tcmu-runner/pull/73

Thanks for the patch @zjcmszh  and thanks for catching that @lxbsz.

Thanks a lot for your suggestion which is very practical,and I will take it. @lxbsz  @mikechristie .

Sorry I missed you re-pushing this PR! Will look at it this week.
In the future, just add a comment to the PR if you do a "push -f" to update the patches, because I do not get notifications when you do a forced push.

Updated patches, please refer to it.
Thanks @mikechristie

Please remove the noise file:
<EMAIL_ADDRESS>
And the noise in commit comment:
Conflicts:
tcmur_cmd_handler.c

Thank you very much for your detailed suggestions@lxbsz.  Updated patches.@mikechristie

Did you test these patches? Do they work with sg utils's sg_opcodes command?

Patches updated @mikechristie
test result：
[root@zj-client ~]# sg_opcodes /dev/sdc --opcode=0x42
Opcode=0x42
Command_name: Unmap
Command supported [conforming to SCSI standard]
Usage data: 42 01 00 00 00 00 00 ff ff 07
[root@zj-client ~]# sg_opcodes /dev/sdc --opcode=0x83
Opcode=0x83
Command_name: Extended copy(LID1)
Command supported [conforming to SCSI standard]
Usage data: 83 00 00 00 00 00 00 00 00 00 ff ff ff ff 00 07

Patches updated, please refer to it, thanks.@mikechristie

@mikechristie  Patches updated, please refer to it. Thanks.


refactor: Remove unused code

Cleans up the code and removes unused code

This extracts parts of https://github.com/stuebingerb/KGraphQL/pull/119 that are IMHO completely risk-free to simplify later changes.


Nyaa api don't working

Hi, https://github.com/popcorn-official/popcorn-api/blob/development/src/providers/anime/Nyaa.js
this don't working, because nyaa-api-pt can't connect to nyaa.se - site not found, so
I wrote https://github.com/xdk78/pantsu-api working nyaa api using nyaa.pantsu.cat, it might be helpful

https://github.com/ChrisAlderson/nyaa-api-pt/tree/2.0.0-alpha.0

Ok


Upgrading to another version is possible ?

Hi,
I want to know if is it possible to upgrade/downgrade between filebeat's versions without having to establish a new clean server ?
When I tried to update the main.yml file from version 1.2.3 to 5.4.0 I got this error message:
FAILED! => {"changed": false, "dest": "C:/ProgramData/chocolatey/lib/filebeat/tools/filebeat-5.4.0-windows/filebeat.yml", "failed": true, "msg": "Failed to copy file Could not find a part of the path 'C:\\ProgramData\\chocolatey\\lib\\filebeat\\tools\\filebeat-5.4.0-windows\\filebeat.yml'.", "src": "C:\\Users\\Administrator\\AppData\\Local\\Temp\\ansible-tmp-1494915143.51-85430862209816\\source"}
Can you assist please ?

Some other older versions of filebeat should work. 5.4.0 may not be supported by chocolatey. I have plans to a look into 5.4.0 support.

Hi @dohque,
Filebeat version 5.2.2 also failed.
As you can see Chocolatey support filebeat 5.4.0 :-)

Looks like it is.

filebeat 5.4.0 from chocolatey package was deployed to
C:\ProgramData\chocolatey\lib\filebeat\tools\filebeat-5.4.0-windows**-x86_64**

while I expect it to be deployed to
C:/ProgramData/chocolatey/lib/filebeat/tools/filebeat-{{filebeat_version}}-windows

Hey @dohque, it seems that the intent here is to make sure that the template is pushed to the config dir. Would it make sense to just use {{filebeat_config_dir}}/filebeat.yml for the path?

@jhuggart there was some deeper issue and some major update I wanted to implement in all my ELK roles to support 5+ versions. But I crazily busy at work. ( Hope I will return to roles soon.


Default to develop branch

Work from develop as per our Git Flow workflow in other 3.0 repositories.

should be all set


Can RocketMQ use centralized storage to ensure syncflush?

version:4.9.1
In the discussion of pull request#3382, areyouok mentioned that this.mappedByteBuffer.force() has the following
limitations:
"If the file does not reside on a local device then no such guarantee is made"
Does this mean that
RocketMQ can only use local hard drives to ensure syncflush?Can I use centralized storage, such as HDS, EMC, etc.
I understand that the meaning of this sentence should be that if centralized storage is used, the storage
guarantees the reliability of flush. If centralized storage cannot be used, RocketMQ's architecture choices will
be very limited.

@iamqq23ue I agree with you that if you can strengthen the synchronization flush process, RocketMQ can run on a variety of centralized storage in a single replica mode. While reducing costs, also makes RocketMQ easier to operate and maintain. Looking forward to you more the opinion of this issue.

In fact, I don't quite understand, what does "If the file does not reside on a local device then no such guarantee is made" mentioned in the description of mappedByteBuffer.force() mean?
Have you studied this method?
------------------ 原始邮件 ------------------
发件人:                                                                                "apache/rocketmq"                                                                                @.>;
发送时间: 2021年11月29日(星期一) 晚上8:41
@.>;
<EMAIL_ADDRESS>主题: Re: [apache/rocketmq] Can RocketMQ use centralized storage to ensure syncflush? (Issue #3536)
@iamqq23ue I agree with you that if you can strengthen the synchronization flush process, RocketMQ can run on a variety of centralized storage in a single replica mode. While reducing costs, also makes RocketMQ easier to operate and maintain. Looking forward to you more the opinion of this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

If I use SAN storage instead of local disks, will I get OK before the data is placed on the disk?
------------------ 原始邮件 ------------------
发件人:                                                                                "apache/rocketmq"                                                                                @.>;
发送时间: 2021年11月29日(星期一) 晚上8:41
@.>;
<EMAIL_ADDRESS>主题: Re: [apache/rocketmq] Can RocketMQ use centralized storage to ensure syncflush? (Issue #3536)
@iamqq23ue I agree with you that if you can strengthen the synchronization flush process, RocketMQ can run on a variety of centralized storage in a single replica mode. While reducing costs, also makes RocketMQ easier to operate and maintain. Looking forward to you more the opinion of this issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.

As far as I know, storage methods such as cloud disks provide reliability guarantees. Of course, there is no need to "force"

This is equivalent to the separation of storage and calculation. Of course, the computing node will be well maintained, but in essence it just transfers the maintenance work to the storage node. But the structure of separation of storage and computing is of course also beneficial, at least it is more decoupled and flexible, and overall maintenance will reduce the problems caused by coupling.

If I remember correctly, rocketmq5.0 will provide a separate storage and computing deployment method, which may be similar to the centralized storage you mentioned.


Added support for Cordova 4.x

Added support for Cordova 4.x

Thanks @FRD49! Nice to see some contribution!
I tested it and it seems to be working fine, so it's good to go. :+1:


Pin docker version in CI to v0.27.2

Codecov Report

Merging #199 (2b521ae) into main (2e0727f) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main      #199   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          687       687
=========================================
  Hits           687       687

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 2e0727f...2b521ae. Read the comment docs.


Release apimangement 2022-08 01

ARM API Information (Control Plane)
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[x] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[x] I commit to follow the Breaking Change Policy of "no breaking changes"
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

@solankisamir, could you fix all the tool check errors?  For breaking change, please follow the below process:
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.

/azp run

@lirenhe This PR is just a group of PRs which were reviewed before already and have all the validation and Breaking change approvals
https://github.com/Azure/azure-rest-api-specs/pull/21352
https://github.com/Azure/azure-rest-api-specs/pull/21595

Hi @solankisamir  I see
https://github.com/Azure/azure-rest-api-specs/pull/21352
https://github.com/Azure/azure-rest-api-specs/pull/21595
But they are part of this PR. So I want to make sure are all breaking changes and Lint diff errors are reviewed. Thanks

Another thing, as ApiReadinessCheck failed, Is service release date confirmed? can you provide? Thanks

@zzvswxy the ApiReadiness date is 2/10/2023

It seems all the commits in the PR has already been reviewed before? What is new on this PR?
Please also check the lintDiff errors.
Thanks

Hi @qiaozha @tadelesh  , can you help me to review the js and go SDK breaking changes? Thanks

It seems all the commits in the PR has already been reviewed before? What is new on this PR?
Please also check the lintDiff errors.
Thanks

Synced offline, all changes are already reviewed and released. Please track these lint errors in a workitem, when the next API version in introduced, you should fix them.

@solankisamir Please resolve the duplicate schema problem of ProxyResource.

Hi @solankisamir   For duplicated-schema, here is the doc how to fix it: https://github.com/Azure/azure-rest-api-specs/wiki/Common-CI-Error#duplicated-schema

About Lint diff,
LroLocationHeader: https://github.com/Azure/azure-openapi-validator/blob/main/docs/lro-location-header.md

@solankisamir  please pay attention to these errors.

@zzvswxy arm team also signed off

Hi @solankisamir  I talk with SDK owners and LintDiff check maintainer. Their requirement are list in the comment above. They both consider the issues need to be fixed. So can you fix it? Thanks

What is the problem with ProxyResource, I could not find any error logs
@zzvswxy  I have created another PR for just Linter Errors
https://github.com/Azure/azure-rest-api-specs/pull/22537

What is the problem with ProxyResource, I could not find any error logs

ProxyResource error shows in SDK generation pipeline. You can find more error info by this way:
For example, python SDK:

Then you can see

Click View more details on Swagger Pipeline you can find the full log.

About how to fix:
SDK owner give a wiki https://github.com/Azure/azure-rest-api-specs/wiki/Common-CI-Error#duplicated-schema
This error cause both .NET/Go/Python SDK generation failed. So the SDK owners think it's necessary to fix the ProxyResource error.

What is the problem with ProxyResource, I could not find any error logs

ProxyResource error shows in SDK generation pipeline. You can find more error info by this way: For example, python SDK:  Then you can see  Click View more details on Swagger Pipeline you can find the full log.
About how to fix: SDK owner give a wiki https://github.com/Azure/azure-rest-api-specs/wiki/Common-CI-Error#duplicated-schema
This error cause both .NET/Go/Python SDK generation failed. So the SDK owners think it's necessary to fix the ProxyResource error.

Ok found the issue with duplicate schema and fixed that error in the pr https://github.com/Azure/azure-rest-api-specs/pull/22537

/azp run

Hi @msyyc  @qiaozha  can you help me to review the Python and JS SDK breaking changes? Thanks

@zzvswxy how does it look after the merge? Can we merge to main branch?


chore(stdlib)!: remove unnecessary merkle functions from stdlib

Description
Problem*
Related to #1258 and https://github.com/noir-lang/acvm/issues/295
Summary*

This PR removes the unnecessary functions from the merkle module in the stdlib (check_membership and compute_root_from_leaf).
We no longer use the black box version of compute_merkle_root in preparation for the opcode being removed and just use the noir implementation (which has been shown to be more efficient anyway). compute_root_from_leaf is then removed/renamed to compute_merkle_root
Documentation

[ ] This PR requires documentation updates when merged.

[ ] I will submit a noir-lang/docs PR.

[ ] I will request for and support Dev Rel's help in documenting this PR.

Additional Context

PR Checklist*

[x] I have tested the changes locally.
[x] I have formatted the changes with Prettier and/or cargo fmt on default settings.

Has check_membership been removed in favor of just computing the root and comparing to a given root. If they match, then it's a member?

Yes, that's correct. We expect user code to use assert(expected_root == compute_merkle_root(...)) instead of wrapping it in an extra function.


Add basic telemetry about the python version being used

What does this PR do?
Add basic telemetry about the python version being used

@olivielpeau thanks for the review, updated the PR following your input.


[WIP] Add support for syncing local packages with the IPFS registry

Proposed changes

adds aea packages group
Implements PackageManager class
Implements aea packages sync to sync local packages directory with remote
Implements aea packages init to initialze packages.json file in a local packages directory

Types of changes
What types of changes does your code introduce to agents-aea?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist
Put an x in the boxes that apply.

[x] I have read the CONTRIBUTING doc
[x] I am making a pull request against the develop branch (left side). Also you should start your branch off our develop.
[x] Lint and unit tests pass locally with my changes and CI passes too
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have checked that code coverage does not decrease.
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

The command implementation works as intended, but there's an issue. When I remove packages/valory and run the command it does the job, but the binary files shows modified permissions, in this case the files are
        modified:   packages/valory/connections/p2p_libp2p/libp2p_node/libp2p_node
        modified:   packages/valory/connections/p2p_libp2p/libp2p_node/link

We need to include this into the readme of the package or this may cause some issues

The command implementation works as intended, but there's an issue. When I remove packages/valory and run the command it does the job, but the binary files shows modified permissions, in this case the files are
        modified:   packages/valory/connections/p2p_libp2p/libp2p_node/libp2p_node
        modified:   packages/valory/connections/p2p_libp2p/libp2p_node/link

We need to include this into the readme of the package or this may cause some issues

Ok

Codecov Report

Merging #310 (fcb7778) into main (2f7323f) will decrease coverage by 0.29%.
The diff coverage is 44.03%.

@@            Coverage Diff             @@
##             main     #310      +/-   ##
==========================================
- Coverage   93.96%   93.67%   -0.30%
==========================================
  Files         216      217       +1
  Lines       18619    18728     +109
==========================================
+ Hits        17495    17543      +48
- Misses       1124     1185      +61

Flag
Coverage Δ

unittests
93.67% <44.03%> (-0.30%)
:arrow_down:

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

Impacted Files
Coverage Δ

aea/cli/packages.py
42.71% <42.71%> (ø)

aea/configurations/data_types.py
99.12% <50.00%> (-0.58%)
:arrow_down:

aea/cli/core.py
100.00% <100.00%> (ø)

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


URLs Missing

Hi,
There are two URLs missing for the identity role. Based on your Microsoft AzureStack Readiness script it needs to also connect to the two endpoints below during deployments (from the Public Infrastructure Network):
ManagementServiceUri = "https://management.core.windows.net/"
ARMUri                          = "https://management.azure.com/"
I've encountered this issue when deploying the solution for a customer blocking the outgoing traffic allowing only the list above.
Thanks,
Q

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

ID: 34d02f93-1ae9-eb2d-9c0f-0af012653885
Version Independent ID: 18f15ad2-ef9b-f883-c49b-09289a2e6fb8
Content: Publish Azure Stack services in your datacenter
Content Source: azure-stack/operator/azure-stack-integrate-endpoints.md
Service: azure-stack
GitHub Login: @mattbriggs
Microsoft Alias: justinha

@justinha Thanks for bringing this to our attention. We are looking into this and will get back to you shortly.

@QFiaux Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@QFiaux Thanks for your feedback. I have a question out and will update shortly.
#in-progress

@QFiaux The topic has been updated. Thanks again for your feedback.
#please-close


cannot import name 'FeatureLoader' from 'sae_auto_interp.features'

while trying to run this https://github.com/EleutherAI/sae-auto-interp/blob/main/demo/simulate.py  script got this error ImportError: cannot import name 'FeatureLoader' from 'sae_auto_interp.features'.i also check that there is no class named FeatureLoader in features.py.
checkout this colab notebook for more details https://colab.research.google.com/drive/1qX2USmeCPyFksARj0ipWVk-aYScr1uCn?usp=sharing

Hi. I updated the script with the required changes for it to run, but as the header of the script said, this script had still not updated to the most recent changes we made to the library and might not be completely functional. Is there a reason you want to start with simulation instead of using the basic.py script?

@SrGonao I've trained a sparse autoencoder and have a bunch of weights for this. I'd like to run this through the Eleuther auto-interp

The basic.py demo is the best place to start.

okay that's great


NOx set state

Hi,
I'm just wrapping my head around how setVocTuningParameters and setVocAlgorithmState work and differ.
Does the algorithm state store historical data such as 12hour history, and so it differs from just storing setting parameters for VocTuningParameters - such as offsets?
Is there a reason there is a setNoxTuningParameters but no setNoxAlgoirthmState, whilst VOC has this? I'm looking at the SGP41 repo, and it seems this can exist and can be made available? I'm trying to understand if this is possible on the SEN51. Is there more documentation on this?
Thanks!!

There was something mentioned about tuning in this ticket on the gas-algorithm repo, https://github.com/Sensirion/gas-index-algorithm/issues/1
I've been experiencing a 1.0 returned float for over 24hrs. There were two minor deviations to 0.83 and 0.7 but possibly at init for one of them. I've been seeing the same in arduino sketch. Having stuck my prototype under a saucepan and using a yellow-flamed kitchen lighter for about 3seconds up under one edge and closing the pan down caused the NOx to wake up, and now all seems more realistically as described in the datasheets where an index of 100 is expected for both VOC and NOx.
It would be lovely to have a more thorough getting your design correct guide, as the temperature compensation guide is a huge part of that, presumably the voc/nox tuning is too, rather than being a fire and forget event sensing index. Or maybe I'm being overly harsh, as with the saucepan I've seen it does at least react when submitted to enough of a NOx event.

the algorithm tuning parameters setVocTuningParameters can be used to specify the behavior of the gas index algorithm. E.g. the index_offset parameter specifies what VOC index is used under average condition (the environment condition the sensor sees most often)
Please check to full documentation in the gas index algorithm header file:
https://github.com/Sensirion/gas-index-algorithm/blob/master/sensirion_gas_index_algorithm/sensirion_gas_index_algorithm.h#L220
The state setVocAlgorithmState can be used to faster recover from device restarts. After at least 3 hours of operation the state can be used for short (max 10min) interruptions. The state has to be saved regular (e.g. once per minute) and set on startup after init or reset. The algorithm will then skip the initial learning phase and be much faster fully usable again.
the algorithm state and some of the tuning parameters are only available for VOC and not for Nox. The algorithm state does not work for the Nox signal and is therefore only available for VOC.
Please find all available documentation on the SGP41 product page:
https://developer.sensirion.com/sensirion-products/sgp41-voc-nox-sensor/

Thank you!


Crash DIGraph_SdkConfigStore_singleton_access

SDK version: 1.2.4
Environment:  Production
Are logs available?
No, because we can not reproduce a crash in a debug area
Describe the bug
In our crashlytics we can see a lot of crashes from the customer io library.
Crash:
Crashed: DIGraph_SdkConfigStore_singleton_access
EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000000

Now the app crashes on any screen, any user flow, we can see it in the crashlytics.
To Reproduce
Can not reproduce from our side
Expected behavior
An app should not crash.
Screenshots

issue_ca7686a2dbc4478891e440a0b082755c_crash_session_4192f76bfb2e45a8be413c7800cba7e2_DNE_0_v2_stacktrace.txt

Hi @alpha-khambir @Arideno
Thank you for flagging this issue. Can you confirm if you are using custom or creating own instances of CustomerIO iOS SDK in your app ? We have deprecated creating own instances of the SDK and using it could be a possible reason behind this issue.

Hi @ami-aman
We are using shared CustomerIO and shared MessagingPush.
And also initialize CustomerIO via initialize method.
CustomerIO.initialize(
   siteId: BuildConfiguration.customerIOSiteID,
   apiKey: BuildConfiguration.customerIOAPIKey
)

Thanks again for reporting this issue to us. The details you sent were very helpful (especially the stacktrace screenshot) to help us help you faster.
Looking at the stacktrace, I have an idea for what the problem may be. Luckily, we just released a new version of the SDK that should hopefully fix this issue for you.
The release is in alpha currently as we work to finish the final steps to get it into beta. We would love for you to try out this new release and report issues to us that you encounter.
There are some small steps you will need to take to migrate to the new version 2 of the SDK. We plan to release those documents when we release v2 to beta.
In the mean time, I will share this draft of the migration docs with you so you can get started with your migration and test out the release if you decide to.

Draft of migration docs

Upgrade from 1.x to 2.x
Singleton API is now enforced
In version 1.x of the Customer.io iOS SDK, could use the SDK in 2 ways:

Singleton API:

CustomerIO.initialize(...) // initialize the singleton SDK instance
Customer.shared.track(...) // use the singleton SDK instance

Non-singleton API:

let cio = CustomerIO(...) // initialize the non-singleton SDK instance
cio.track(...)            // use the non-singleton SDK instance

In version 2.x, we removed the non-singleton API. To successfully migrate, you need to replace any code using a non-singleton with the singleton instance:
// Replace the non-singleton instance:
cio.track(...)
messagingPush.application(...)
// With `CustomerIO.shared` or `MessagingPush.shared`:
CustomerIO.shared.track(...)
MessagingPush.shared.application(...)

If your app uses a technique like dependency injection, you can keep your code base as-is and simply replace code where you create new instances of the SDK:
// For example, if you have code that accepts a CustomerIO dependency in the constructor (to easily allow mocking the Customer.io SDK):
class Repository {
    let customerIO: CustomerIO

    init(customerIO: CustomerIO) {
        self.customerIO = customerIO
    }

    func acceptFriendRequest() {
        ...
        self.customerIO.track(...)
        ...
    }
}

// You can keep your Repository as-is, but you need to change where you create instances from:
let repository = Repository(customerIO: CustomerIO(...))
repository.acceptFriendRequest()
// To:
let repository = Repository(customerIO: CustomerIO.shared) // Don't forget to initialize the SDK 😉
repository.acceptFriendRequest()

Configuration of the SDK happens during SDK initialization
In version 1.x of the Customer.io iOS SDK, you configured the SDK through a .config function:
CustomerIO.config {
  $0.autoTrackScreenViews = true
}

In version 2.x of the Customer.io iOS SDK, we moved the .config function into CustomerIO.initialize. You'll need to move your configuration into the SDK initialization process to migrate:
CustomerIO.initialize(siteId: "YOUR SITE ID", apiKey: "YOUR API KEY", region: Region.EU) { config in
  config.autoTrackScreenViews = true
}

Visit the getting started doc to learn more about SDK configuration.
SDK initialization required parameters
In version 1.x of the Customer.io SDK, the function CustomerIO.initialize contained optional parameters. We had to remove those and make all parameters required.
To migrate to 2.x of the SDK, fill in the rest of the parameters in your initialize function:
// v1.x
CustomerIO.initialize(siteId: "YOUR SITE ID", apiKey: "YOUR API KEY")

// v2.x
CustomerIO.initialize(siteId: "YOUR SITE ID", apiKey: "YOUR API KEY", region: Region.US) {}
// Optionally, if you want to configure settings of the SDK, do so in initialization.
CustomerIO.initialize(siteId: "YOUR SITE ID", apiKey: "YOUR API KEY", region: Region.EU) { config in
  config.autoTrackScreenViews = true
}

Visit the getting started doc to learn more about SDK configuration.
Rich push initialization
If you have followed our docs to setup rich push in your app, you should have a Notification Service Extension file in your code base.
Because of the behavior of Notification Service Extensions in iOS, you need to initialize the Customer.io SDK in your host app and in your Notification Service.
class NotificationService: UNNotificationServiceExtension {

    override func didReceive(
        _ request: UNNotificationRequest,
        withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void
    ) {
        // Make sure to initialize the SDK at the top of this function.
        CustomerIO.initialize(siteId: "YOUR SITE ID", apiKey: "YOUR API KEY", region: Region.US) { config in
            config.autoTrackPushEvents = true
        }
        ...
    }
}

See our docs for rich push to learn more about rich push setup, SDK initialization, and SDK configuration.
Cocoapods users, make sure you have installed Firebase dependencies yourself
The CustomerIO/MessagingPushFCM Cocoapod has removed all Firebase SDKs as dependencies. This means that you need to install the Firebase Cloud Messaging (FCM) dependencies in your Podfile on your own.
If you installed the Customer.io SDK using Swift Package Manager, this change does not effect you.

@levibostian thanks! When the new version will be released? Any estimates?

@alpha-khambir No estimates at this time but hope within the next week or two.
We upgrade alpha releases to beta once we have completed full internal testing of a release and finish documentation. Both of these tasks are underway at this moment meaning beta is dependent mostly on how internal testing goes.

@levibostian sounds good, I will wait for your release. I hope that the new version will fix this issue 🙏


How to maintain the connection?

Each time I relaunch my application, I have to authorize!

How to prevent this?
Is there a way to keep using the same rsa key fingerprint?

You need to initialize KadbCert in ApplicationInit, generate a new KadbCert by KadbCert.get(), and save it in your ways like File or SharedPreferences etc, then set the KadbCert by KadbCert.set(cert.toByteArray(), key.toByteArray()).
Here's the sample code to generate a new KadbCert and save it by SharedPreferences in Application:
// Try to get cert and key from SharedPreferences
val sp = applicationContext.getSharedPreferences("kadb", Context.MODE_PRIVATE)
val cert = sp.getString("cert", null)
val key = sp.getString("key", null)
if (cert.isNullOrEmpty() || key.isNullOrEmpty()) {
    // If KadbCert haven't been saved in SharedPreferences, generate a new one
    val pair = KadbCert.get()
    sp.edit()
        .putString("cert", pair.first.decodeToString())
        .putString("key", pair.second.decodeToString()).apply()
    return
}
try {
    KadbCert.set(cert.toByteArray(), key.toByteArray())
} catch (e: Exception) {
    if (e is CertificateExpiredException || e is CertificateNotYetValidException) {
    val pair = KadbCert.get()
    sp.edit().putString("cert", pair.first.decodeToString())
        .putString("key", pair.second.decodeToString()).apply()
    }
    throw e
}

https://github.com/flyfishxu/Kadb/blob/main/docs/kadbcert.md


add binary deb support for xpack

Is your feature request related to a problem? Please describe.
xpack current support only source deb format, i want to submit a pr for binary deb format.
Describe the solution you'd like
how can i distinguish pack deb from source or pack deb from binary for deb format of xpack?
maybe we can use the api xpack:inputkind?
inputkind
Describe alternatives you've considered
No response
Additional context
No response

right, you can open a pr.

we can distinguish source deb and binary deb using the api xpack:inputkind.
but we can't change the behavior of xpack using command line.
for example, we can't do this:
xmake pack -f deb -k binary

maybe we can add a new comman option or add a new format name for binary deb format

you can use different package names. xpack("mysrcdeb"), mybindeb ...
https://github.com/xmake-io/xmake/blob/2f1213a70b2ea1be2097c7f2bd7b4fc85a861b80/xmake/plugins/pack/xmake.lua#L38


Allow nested selectors

@garronej this seems to work, by calling emotion css function twice - but it breaks the types.

Actually if I change:
            getCssObjectOrCssObject:
                | ((
                      theme: Theme,
                      params: Params,
                      classes: Record<Key, string>,    // <-- here
                  ) => Record<Key, CSSObject>)
                | Record<Key, CSSObject>,

to:
            getCssObjectOrCssObject:
                | ((
                      theme: Theme,
                      params: Params,
                      classes: any,
                  ) => Record<Key, CSSObject>)
                | Record<Key, CSSObject>,

But I am not totally sure why that happens. Also any seems like not the right choice here but it does get it working.

Damn,
I though it was the runtime that would be hard to get working but it's actually the typings that turn out to be a problem.
I got the classes parameter to be inferred as Record<string, string> but I am still failing to to get it as Record<"el1" | "el2", string>...
Good job on the implementation though.

I am very disappointed 😞
I think it's a no go with the current state of typescript.
Trying to think of another API...

I am very disappointed 😞
I think it's a no go with the current state of typescript.
Trying to think of another API...

Calling css function twice isn't really ideal either. I'm not sure if there is a performance hit, but it seems hacky.
I am going to run this in the meantime, until a better API emerges.

@garronej also, I pushed up the change from any to Record<string, string> since it's at least a slight improvement. Even without the typings on the classes that come back in useStyles the work might still be useful to some 🤷🏻♂
You might still consider a merge and then a minor version bump later in the case of a better API.

Hold on a minute, I want to know what you think about this

What do you think of that:

It's less sexy but also less voodooish and type safe...

Seems fine to me if it gets the job done!

I test it and release it in the next hour.
Thank you very much for your involvement, it helps a lot

I will merge even if I override it. This way you'll appear in the contributor list.


HIVE-26065: fix incorrect metric active_calls_alter_partitions and active_calls_alter_partition

In our production environment, we found that the value of the metric "active_calls_alter_partition" was negative. This is very confusing.
After checking the HMSHandler.class, we found that the method alter_partitions_with_environment_context called()
startTableFunction("alter_partitions", catName, db_name, tbl_name);
...
endFunction("alter_partition", oldParts != null, ex, tbl_name);
So the metric "active_calls_alter_partition" will be decremented by one after the "alter_partitions" function execution ends, causing the value become a negative number

@maheshk114 Can you please help review this patch? Thanks

+1 (unstable tests)

@Tuan8888
Can you please rebase the patch.

@maheshk114 thanks. Already Finished


Show NotFoundPage if report does not exist in sub report views

Details

Show NotFoundPage if report does not exist in sub report views
Renamed HOC withReportOrNavigateHome to withReportOrNotFound

$ https://github.com/Expensify/App/issues/14513
PROPOSAL: https://github.com/Expensify/App/issues/14513#issuecomment-1418199977
Tests

Login to any account
Open any report
Edit the URL by appending any random number
Verify that you see "Hmm... it's not here" message
Edit the URL again (keep the random added number) by appending /details
Verify that you see "Hmm... it's not here" message

[ ] Verify that no errors appear in the JS console

Offline tests
n/a
QA Steps

Login to any account
Open any report
Edit the URL by appending any random number
Verify that you see "Hmm... it's not here" message
Edit the URL again (keep the random added number) by appending /details
Verify that you see "Hmm... it's not here" message

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[X] I linked the correct issue in the ### Fixed Issues section above
[X] I wrote clear testing steps that cover the changes made in this PR

[X] I added steps for local testing in the Tests section
[X] I added steps for the expected offline behavior in the Offline steps section
[X] I added steps for Staging and/or Production testing in the QA steps section
[X] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[X] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[X] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[X] I included screenshots or videos for tests on all platforms
[X] I ran the tests on all platforms & verified they passed on:

[X] Android / native
[X] Android / Chrome
[X] iOS / native
[X] iOS / Safari
[X] MacOS / Chrome / Safari
[X] MacOS / Desktop

[X] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[X] I followed proper code patterns (see Reviewing the code)

[X] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[X] I verified that comments were added to code that is not self explanatory
[X] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[X] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[X] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[X] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[X] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[X] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[X] I verified the JSDocs style guidelines (in STYLE.md) were followed

[X] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[X] I followed the guidelines as stated in the Review Guidelines
[X] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[X] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[X] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[X] I verified that if a function's arguments changed that all usages have also been updated correctly
[X] If a new component is created I verified that:

[X] A similar component doesn't exist in the codebase
[X] All props are defined accurately and each prop has a /** comment above it */
[X] The file is named correctly
[X] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[X] The only data being stored in the state is data necessary for rendering and nothing else
[X] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[X] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[X] All JSX used for rendering exists in the render method
[X] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[X] If any new file was added I verified that:

[X] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[X] If a new CSS style is added I verified that:

[X] A similar style doesn't already exist
[X] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[X] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[X] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[X] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[X] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[X] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome
https://user-images.githubusercontent.com/16493223/221321115-dd32bbc2-d982-4d38-bdb3-ea723e0b0d99.mp4

Mobile Web - Safari
https://user-images.githubusercontent.com/16493223/221321131-1364cc63-0593-4238-8ea9-26d9889991d1.mp4

Desktop
https://user-images.githubusercontent.com/16493223/221539587-870af232-b319-4390-8600-f79feb1456cc.mp4

iOS

Android

@neil-marcellini Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

cc @AndrewGable @0xmiroslav Tagging you here, not sure why puller bear didn't assign you.

@0xmiroslav

let's fix these kinds of warnings in all 3 pages

How are those errors related to this PR? They are reproducible in main. Please report on Slack.

@0xmiroslav

you can also test deep link on desktop app locally and add video by disabling this

Do I have to build a production release for desktop? Will deep link work with just npm run desktop?

Updated

@s77rt please make sure to not change the PR template. Keep the Fixed issues section as its in the PR template so the correct people are assigned for a review. Thanks 🙇

@mountiny Add @0xmiroslav as a reviwer too.
Actually I was looking into what went wrong with the template, I see it now, I accidentally deleted the ### Fixed Issues header 😅

Updated :D

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/AndrewGable in version: 1.2.78-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.2.78-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Show number of volunteers on activity page?

Should the activity page show the number of volunteer positions needed and how many are filled? And if there are two or more skills needed should that be broken down into how many of each needed?

@schuback - Pinging for your thoughts. I'm not 100% sure what is meant by activity page though.

I'll have to review this.
On Thu, Mar 16, 2017 at 1:23 PM, Steve Gordon<EMAIL_ADDRESS>wrote:

@schuback https://github.com/schuback - Pinging for your thoughts. I'm
not 100% sure what is meant by activity page though.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/HTBox/allReady/issues/553#issuecomment-287180036, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAyqVI04xJkSDezAOAKnql5THxvNon9Eks5rmZpZgaJpZM4HevBf
.

--
Pascal Schuback
<EMAIL_ADDRESS>206.414.8799
@schuback


Update cats-helper to 2.7.5

Updates com.evolutiongaming:cats-helper from 2.7.0 to 2.7.5.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.evolutiongaming", artifactId = "cats-helper" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #307.


node scripts/build-tries.js fails on Ubuntu 16.04.5 LTS (GNU/Linux 4.4.0-131-generic x86_64)

I receive this message trying to install parse-domain.  I have installed the latest versions of node.js and npm.

<EMAIL_ADDRESS>postinstall /usr/local/bin/auspice/node_modules/parse-domain
node scripts/build-tries.js

sh: 1: node: not found
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm WARN optional Skipping failed optional dependency /watchpack/chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>< 16.4.0 but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>< 16.4.0 but none was installed.
npm WARN<EMAIL_ADDRESS>No repository field.
npm WARN<EMAIL_ADDRESS>license should be a valid SPDX license expression
npm ERR! Linux 4.4.0-131-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "parse-domain"
npm ERR! node v4.2.6
npm ERR! npm  v3.5.2
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR<EMAIL_ADDRESS>postinstall: node scripts/build-tries.js
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script 'node scripts/build-tries.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the parse-domain package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     node scripts/build-tries.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs parse-domain
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls parse-domain
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /usr/local/bin/auspice/npm-debug.log

Looks like node is not in your $PATH

Fixed with v3.0.0 🚀


Add \rerun <ID> command for failed jobs in workflows

Description
This adds a command which allows rerunning of just the failed jobs on an existing workflow run ID.
This can help with reducing unnecessary workflow runs. It also allows trusted community members who are not approvers to perform this action (the same people who can run /ok-to-test).
Usage:
\rerun <ID>, where the ID is obtained from URL of a given workflow run

There is a 5% chance this will actually work given my Javascript skills, but it won't break anything. Testing in production :) - Let's see.


Keeps marker widths on autostyle

Notice that this applies to turbo-carto and static marker size rules, like the following:
marker-width: ramp([col],10, 30, 'jenks');

or
marker-width: 10;

Except for my comment, the rest is 👍


Update HTTPoison, ExVCR

Updates HTTPoison to 1.3.0 (since 1.4.0+ requires some work to be done on HTTPoison itself)
Updates ExVCR to 0.10.3 - required moving of VCR configuration to the Mix config file (solves the issue encountered here)

That's awesome! Sorry for the super delay xD


Remove LiLaC and remove unnecessary configs

LiLaC is an unused dependency, so it is removed.
Removed unnecessary modernfix config that are already set by default.
Fix "use_entity_culling": false not applying on 1.16.5
Simulation distance, always_defer_chunk_updates, and cpu_render_ahead_limit doesn't exist in 1.16.5, so they're removed from the config.
always_defer_chunk_updates is already on by default on 1.20.1-1.20.4. So they're removed from the config.
Closes
#49 and #50

Wait a minute, I forgot about quilt.

As of the latest additive version, this pr is unnecessary except for the "Removed unnecessary modernfix config that are already set by default." part


Pool error formatter (with EthConfig)

Depends on #736
Updated port of #510 :
Introduce a new associated type in EthConfig to customize pool error format to better match other implementations such as Geth. Further PRs could add support to other implementations format, or include formatting of errors of other RPC endpoints by adding new functions to the Formatter trait.
Adds an additional check in transaction validation for when the user don't have enough funds for a transfer (is currently covered by the transfer + gas check, but geth return 2 distinct errors)

Can you rebase this without https://github.com/paritytech/frontier/pull/736?

@sorpaas Rebased without the EthConfig trait.


Disable batch transfer in DP mode

What does this PR do?

There is no need to transfer the batch to the device in DP mode since it's handled internally. Else what's happening now is let say a batch with batch_size 32 is there. Then first it's transferred to gpu:0, passed to the model wrapped around DataParallel and again transferred to separate devices after splitting. So the first transfer is unnecessary.
Before submitting

[ ] Was this discussed/approved via a GitHub issue? (not for typos and docs)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure your PR does only one thing, instead of bundling different changes together?
[x] Did you make sure to update the documentation with your changes? (if necessary)
[x] Did you write any new necessary tests? (not for typos and docs)
[x] Did you verify new and existing tests pass locally with your changes?
[x] Did you update the CHANGELOG? (not for typos, docs, test updates, or internal minor changes/refactorings)

PR review
Anyone in the community is free to review the PR once the tests have passed.
Before you start reviewing make sure you have read Review guidelines. In short, see the following bullet-list:

[x] Is this pull request ready for review? (if not, please submit in draft mode)
[x] Check that all items from Before submitting are resolved
[x] Make sure the title is self-explanatory and the description concisely explains the PR
[x] Add labels and milestones (and optionally projects) to the PR so it can be classified

Did you have fun?
Make sure you had fun coding 🙃

Hello @rohitgr7! Thanks for updating this PR.

In the file tests/accelerators/test_dp.py:

Line 197:23: W292 no newline at end of file


Apply fixes from StyleCI

This pull request applies code style fixes from an analysis carried out by StyleCI.

For more information, click here.

Pull Request Test Coverage Report for Build 627

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.0%

Totals

Change from base Build 625:
0.0%

Covered Lines:
0

Relevant Lines:
218

💛  - Coveralls

Codecov Report

Merging #130 into commands will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             commands   #130   +/-   ##
=========================================
  Coverage           0%     0%
  Complexity         72     72
=========================================
  Files               9      9
  Lines             231    231
=========================================
  Misses            231    231

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 3a48d76...93317f3. Read the comment docs.


Why is foreground prediction necessary?

Hello,
First of all, good job with the paper! Nicely written and explains a lot of concepts pretty well.
However, I am still a little puzzled about why is predicting foreground (or foreground residual in this case) necessary in the pipeline.
Consider this example from the demo:

For the composition (the final step) - why do we use the pixels from upsampled foreground and not from the original image? They are supposed to be identical anyway, because we explicitly train the coarse foreground prediction to replicate the pixels from the original image (in the alpha mask region) (formula 2):

A possible answer is mentioned in Issue#19, but it's unclear to me what the "background color spill onto partial-opacity hairs and edges" looks like and how does foreground prediction branch mitigate this issue.
I would greatly appreciate an explanation and/or just a side-by-side comparison of 2 images (original vs predicted foreground).
Thank you in advance!

https://github.com/PeterL1n/RobustVideoMatting/issues/42

Foreground is only equal to the source on region where alpha = 1. But for semitransparent regions, it is not, because part of the background will leak through. These regions are usually hair, silhouette, and motion blur.

But the foreground will be learned to be the same as the original pixels for all alpha > 0, not just alpha = 1, no?

No, it won't. The dataset provides ground truth foreground F and alpha a. We composite them to a background to synthesize a synthetic source input I = aF + (1-a)B. The model predicts foreground F' and alpha a'. The loss on F' is from ground truth F.

Oh, so we use the properly-extracted foregrounds from the datasets and the model directly learns to remove the background in those situations you described (hair strands, motion blur, etc.). I missed that, sorry.
Thanks for the explanation!


#patch fix panic for GET cmd w table output

TL;DR
Suggested fix for https://github.com/flyteorg/flyte/issues/1396.
nil checks exists for ExpectedOutput container but not on the Variables map pointer itself prior to calling, and nil argument causes a panic.
Added nil check on map argument to FormatVariableDescriptions at pkg/printer/printer.go:173 prior to calling in all places found.
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[ ] Code completed
[ ] Smoke tested
[ ] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
As described in https://github.com/flyteorg/flyte/issues/1396 flytectl panics for get resource command if resource is missing ExpectedOutput.Variables
Prior to fix
$ go run ./main.go get launchplans -p demo-1 -d production --latest demo-1.no-output

panic: assignment to entry in nil map

goroutine 1 [running]:
github.com/flyteorg/flytectl/pkg/printer.FormatVariableDescriptions(0x0)
	/workspace/flyteorg/flytectl/pkg/printer/printer.go:202 +0x307
github.com/flyteorg/flytectl/cmd/get.LaunchplanToTableProtoMessages({0xc000a30938, 0x1, 0x7ffeefbff977})
	/workspace/flyteorg/flytectl/cmd/get/launch_plan.go:136 +0xee
github.com/flyteorg/flytectl/cmd/get.getLaunchPlanFunc({0x2dfbf98, 0xc0000580b8}, {0xc0002fb8c0, 0x1, 0x11519b4}, {{0x2e55850, 0xc000a30120}, {0x2e472c0, 0xc0009a3110}, {0x2ddff60, ...}, ...})
	/workspace/flyteorg/flytectl/cmd/get/launch_plan.go:158 +0x307
github.com/flyteorg/flytectl/cmd/core.generateCommandFunc.func1(0xc000481680, {0xc0002fb8c0, 0x1, 0x6})
	/workspace/flyteorg/flytectl/cmd/core/cmd.go:69 +0x47d
github.com/spf13/cobra.(*Command).execute(0xc000481680, {0xc0002fb860, 0x6, 0x6})
	/workspace/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:852 +0x60e
github.com/spf13/cobra.(*Command).ExecuteC(0xc000480000)
	/workspace/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:960 +0x3ad
github.com/spf13/cobra.(*Command).Execute(...)
	/workspace/go/pkg/mod/github.com/spf13/cobra@v1.1.3/command.go:897
github.com/flyteorg/flytectl/cmd.ExecuteCmd()
	/workspace/flyteorg/flytectl/cmd/root.go:135 +0x1e
main.main()
	/workspace/flyteorg/flytectl/main.go:12 +0x1d
exit status 2

With this fix I get expected output, a table style output with empty value for output.
Tracking Issue
https://github.com/flyteorg/flyte/issues/1396
Signed-off-by: Viktor Gerdin<EMAIL_ADDRESS>

Interesting....Upgrade unit test got failed. I will check and let you know the issue.


[Storage][STG71] Rename BlobContainerProperties.DenyEncryptionScopeOverride

https://github.com/Azure/azure-sdk-for-net/pull/9190
Pending email discussion.

@seanmcc-msft
Please add "Client" label for dataplane SDK. (As agreement before, we use "Client" label to differ dataplane SDK issue and SRP SDK issue)
We have a system to collect SRP SDK issues, the issues without "Client" label will be collect as SRP SDK issues.
Thanks!

@blueww, sorry about that!


[WIP] Turn transform definition into configuration style

Definitions now must be parseable using Properties.load() after the semicolons have been replaced with new lines.

@gpang

The names for these configurations are kept from the old options configurations which means that they are not very good at the moment.

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/Alluxio-Pull-Request-Builder/8662/
Test FAILed.

Merged build finished. Test FAILed.

@gpang: I have done some basic testing and testing results look good. The only thing that's left are:

Making all tests pass
Figuring out good names.

renamed hive.file.count.max -> name.count.max
and renamed hive.file.size.min -> file.size.min

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/8699/
Test FAILed.

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/Alluxio-Pull-Request-Builder/8704/
Test FAILed.

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/Alluxio-Pull-Request-Builder/8726/
Test FAILed.

Tests in error:
GetBlockInfoCommandIntegrationTest.alluxio.client.cli.fsadmin.command.GetBlockInfoCommandIntegrationTest » Runtime

alluxio-bot, test this please.

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/Alluxio-Pull-Request-Builder/8727/
Test FAILed.

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/Alluxio-Pull-Request-Builder/8728/
Test FAILed.

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/Alluxio-Pull-Request-Builder/8729/
Test FAILed.

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/Alluxio-Pull-Request-Builder/8730/
Test FAILed.

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/Alluxio-Pull-Request-Builder/8732/
Test FAILed.

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/Alluxio-Pull-Request-Builder/8734/
Test PASSed.

@gpang: ready for review.

@gpang Ping?

Addressed Feedback. Note that definition normalization is not very good right now and will probably work on that later since it previously was also not very good.

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/Alluxio-Pull-Request-Builder/8776/
Test FAILed.

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/Alluxio-Pull-Request-Builder/8783/
Test PASSed.

Feedback addressed.

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/Alluxio-Pull-Request-Builder/8787/
Test FAILed.

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/Alluxio-Pull-Request-Builder/8788/
Test FAILed.

Tests in error:
FileSystemAclIntegrationTest.alluxio.client.hadoop.FileSystemAclIntegrationTest » Runtime
Flaked tests:
alluxio.server.ft.journal.ufs.UfsJournalIntegrationTest.loadMetadata(alluxio.server.ft.journal.ufs.UfsJournalIntegrationTest)
Run 1: UfsJournalIntegrationTest.loadMetadata:172->loadMetadataTestUtil:176->createFsMasterFromJournal:603 » Runtime
Run 2: PASS

alluxio-bot, test this please.

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/Alluxio-Pull-Request-Builder/8789/
Test FAILed.

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/Alluxio-Pull-Request-Builder/8790/
Test FAILed.

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/Alluxio-Pull-Request-Builder/8791/
Test PASSed.

Lets merge this @gpang

alluxio-bot, merge this please


Add x86 / 32bits support

Some users are locked to legacy x86 platforms. Let's support them!

closed 50250bed7a02404b4cf3e5b1118ab2d7170d9334


Custom request works but reports error

Dear all
I've setup a device to command a roller blind via a Fibaro HCL.
When I test the command, the blind opens/closes but the ha-bridge reports an error
Error on calling url to change device state
The command is
http://usr:pwd@<IP_ADDRESS>/api/callAction?deviceID=118&name=setValue&arg1=0
When I try it from safari by entering it directly in the adress bar it returns
{"id":0,"jsonrpc":"2.0","result":{"result":0}}
I've set GET, no content in the manual add interface
Ideas?
Thanks for your help
Anthony

@bwssytems I had a user report on my how-to blog post the same problem,

"...when I try to use the Test On or Test Off buttons, I get this error message: Error on calling url to change device state..."

It was for a custom url, I've asked for their devices json, I'll post when I get it.

I have the same problem. I'm using: http://user:password@192.168.x.x/api/callAction?deviceID=149&name=turnOn with GET. It does work by the way, I can switch this light on and off, but Alexa (and the test buttons) return an error message.

This should work, I'll look at the url handling.

I found the problem. Fibaro is sending a back 202 not a 200

Ahh, I see. And that is a valid code. I'll update the handling to be more cognizant of the other success codes.

Ahh, I see. And that is a valid code. I'll update the handling to be more cognizant of the other success codes.

I had this working on an old server, I have re-installed a new server a few weeks later and my old settings no longer working. the difference being there has been a recent Home Center 2 update and not sure if this maybe part of the issue. I am getting the issue that you have described above whereby even though I specify the username and password in the http content. On my browser it still askes me to login using my username and password and then works there after. I am running a Ubuntu server with command prompt only so I have no way of authorizing the output message like I do in the browser any ideas? Any help would be appreciated.

curl -v http://UserName:Password@192.168.xxx.xxx/api/callAction?deviceID=21&name=turnOn
[6] 6057
[5]   Done                    curl -v http://Username:Password@192.168.xxx.xxx/api/callAction?deviceID=21
usr@HomeServer:/usr/bin/habridge/data$ *   Trying 192.168.xxx.xxx...

Connected to 192.168.x.xx (192.168.xxx.xxx) port 80 (#0)
Server auth using Basic with user 'Username'

GET /api/callAction?deviceID=21 HTTP/1.1
Host: 192.168.xxx.xxx
Authorization: Basic BBJlem3yOlRvc3Nlcjcc
User-Agent: curl/7.47.0
Accept: /

< HTTP/1.1 400 Bad Request
< Date: Sat, 24 Dec 2016 14:28:24 GMT
< Server: 0.9
< Cache-Control: no-cache, no-store, must-revalidate, max-age=0, max-age:0
< Content-Type: application/json;charset=UTF-8
< Pragma: no-cache
< Expires: Fri, 01 Jan 2010 00:00:00 GMT
< Connection: close
< Transfer-Encoding: chunked
<

Closing connection 0
{"type":"ERROR","reason":"MISSING_PARAMETER","message":"name: missing required parameter"}^C
[6]+  Done                    curl -v http://Username:Password@192.168.xxx.xxx/api/callAction?deviceID=21
usr@HomeServer:/usr/bin/habridge/data$

Not an ha-bridge issue as I can see. You will need to work out the http call with curl and then get that into the ha-bridge.


Only count text characters towards length

Fixes #26 and  #27

Nice, great catch! Thanks @Huluk 💟


RoundTrip renderer not working?, breaking changes in output.

Tests done with 0.33.0
I have complex markdown that Itry to process and I find the simpple issue that at least links are not properly processed at all.
The following is a simple code snippet that I use to debug this:
void MarkdownTreeRework(string original)
{
    var document = Markdig.Markdown.Parse(original)!;
    var writer = new StringWriter();
    var renderer = new Markdig.Renderers.Roundtrip.RoundtripRenderer(writer);
    renderer.Render(document);
    var updatedMarkdown = writer.ToString();
    Console.WriteLine(updatedMarkdown);

}
Doing really nothing, it takes a text as input, generates the parsed document, turns it out through the RoundtripRenderer. This is as simple as it gets, essentially.
Here are some (not so nice) findings I find:

There is a loss of empty lines:

This:
# Universal Basic Income: Pros, Cons, and its Feasibility in a World Dominated by AI

## Overview

### What is Universal Basic Income?

Universal Basic Income (UBI) is a policy that guarantees every individual a regular,

turns into:
#Universal Basic Income: Pros, Cons, and its Feasibility in a World Dominated by AI
##Overview
###What is Universal Basic Income?
Universal Basic Income (UBI) is a policy that guarantees every individual a regular,

In some parts, it is breaking:
while ensuring a fair and equitable distribution of resources.

## Impact on Employment

![](https://contenu.nyc3.digitaloceanspaces.com/journalist/d69a68ba-5f1a-4ddf-801e-f4fdb4b8be06/thumbnail.jpeg)

### Promoting Entrepreneurship and Innovation

To:
 while ensuring a fair and equitable distribution of resources.##Impact on Employment
![]()###Promoting Entrepreneurship and Innovation

2x the new line was skipped, putting the image link right into text and destroying the header information, as it must be on a new line. On top, this snippet shows another round trip bug:

Links are removed

As you can see in the last comparison up - the https link was removed and the output has no URL. It does keep the text associated:
`Artificial intelligence (AI) is [revolutionizing the financial markets](https://unescap.org/cgi-bin/koha/tracklinks.pl?uri=http://yfv8j11nou46.%D0%B0%D0%BB%D1%8C%D0%B4%D0%BE%D0%B3%D0%B0.%D1%80%D1%84) and the economy as a whole.`

To
`Artificial intelligence (AI) is [revolutionizing the financial markets]() and the economy as a whole. With its ability to analyse vast amounts of data and make predictions,`

but the links get removed.
it COULD bea configuration error on my side, but the code as shown is trivial enough I do not think so and follows the roundtrip documentation.
Not round trippy.

You have to pass the trackTrivia flag to Markdown.Parse
-var document = Markdig.Markdown.Parse(original)!;
+var document = Markdig.Markdown.Parse(original, trackTrivia: true);

This smells like a bug still to me. Let me be clear here - I can understand that for things that re non breaking (like removing SURPLUS empty lines).... but if this parsing removes functional elements.... something is broken. trackTrivial should not leave to links becoming totlly useless or new lines that are essential to be removed.

This smells like a bug still to me. Let me be clear here - I can understand that for things that re non breaking (like removing SURPLUS empty lines).... but if this parsing removes functional elements.... something is broken. trackTrivial should not leave to links becoming totlly useless or new lines that are essential to be removed.

Markdig was initially developed for generating HTML. Not for doing roundtrip to Markdown which came later, came partially and was not ideal to bring because it is on its own, already quite complex to manage, but even more complicated to bring as an afterthought.
trackTrivia was introduced after, by someone outside of myself and @MihaZupan. Tracktrivia is not free, it makes the parsing slower, generates more GC and as I said, the primary usage of Markdig is for generating HTML. That's why it's not on by default.
So, it's not a bug, but a complexity/legacy that we need to deal with.


Set region awareness envvar to true in Cassandra when region is specified

@gabrielhartmann just to save a step, since the one implies the other, and otherwise the user would have to specify some config.allow_region_awareness in addition to specifying a remote region if they wanted to run in one.