Cannot read property 'headerText' of undefined

I'm getting this error when I add search to my table.
TypeError: Cannot read property 'headerText' of undefined     at http://localhost:3000/static/js/bundle.js:102201:27     at Array.map (native)     at BootstrapTable.renderToolBar (http://localhost:3000/static/js/bundle.js:102197:31)     at BootstrapTable.render (http://localhost:3000/static/js/bundle.js:101417:27)     at http://localhost:3000/static/js/bundle.js:26822:22     at measureLifeCyclePerf (http://localhost:3000/static/js/bundle.js:26101:13)     at ReactCompositeComponentWrapper._renderValidatedComponentWithoutOwnerOrContext (http://localhost:3000/static/js/bundle.js:26821:26)     at ReactCompositeComponentWrapper._renderValidatedComponent (http://localhost:3000/static/js/bundle.js:26848:33)

could you please show me your code and keep it minimal and simple, and what's version you used?
thanks

Hey i am getting same issue

"Uncaught (in promise) TypeError: Cannot read property 'headerText' of undefined"

i am doing remote sorting, remote pagination and remote searching..
remote sorting and remote pagination works well whenever i place

search={ true }

on options it gives me this error.. if i removed this from options then my table is working pretty cool..

when i do something like this it works perfectly (just an example)-->
<BootstrapTable data={ products } search={ true } options={ options }>
          <TableHeaderColumn dataField='id' isKey dataSort={true}>Product ID</TableHeaderColumn>
          <TableHeaderColumn dataField='name' dataSort={true}>Fruit Name</TableHeaderColumn>
          <TableHeaderColumn dataField='price' dataSort={true}>Product Price</TableHeaderColumn>
      </BootstrapTable>

but when i use map function to populate TableHeaderColumn it gives me that error
render(){
             const TableBody = this.props.data.map(function (data) {
             return (<TableHeaderColumn key={data.key} dataField={data.key}
                         filter={ {type: 'TextFilter'} } dataSort={true} >{data.title}
                         </TableHeaderColumn>)
		});
return(
               <BootstrapTable data={ products } search={ true } options={ options }>
                     <TableHeaderColumn dataField='id' isKey dataSort={true}>Product ID</TableHeaderColumn>
                     {TableBody}
              </BootstrapTable>
);
}

removing search={true} sorting and fliter is working perfectly over map function too..

but when i use map function to populate TableHeaderColumn it gives me that error

I think this is maybe the root cause, I dont think the search is the problems here, if true, there're must have same issue at before.
@salahcoffye, could you please show me your case? thanks

Same issue here. I can't use exportCSV while using map to render TableHeaderColumn

@shyjal, did you enable search?

ok, I got the problem, if you use map for creating the TableHeaderColumn, please do not doing this
<BootstrapTable data={ products } search={ true } options={ options }>
   <TableHeaderColumn dataField='id' isKey dataSort={true}>Product ID</TableHeaderColumn>
   { columns }
</BootstrapTable>

Please use following, if you feel isKey is noisy, you can use keyFile on BootstrapTable instead.
<BootstrapTable data={ products } search={ true } options={ options } keyField='id'>
   { columns }
</BootstrapTable>

Let me know if the problem still remain, thanks

@AllenFang I enabled exportCSV and got this issue. Moved all TableHeaderColumn components inside map like you mentioned,now the issue is solved. Thank you.

What if I would like to to this (this is a pseudo code):

{mapped TableHeaderColumns}
Product ID

So basically I would like to map my data to header columns, but also have a custom column (in my case, a column containing delete buttons, one for each row). This is not working, Any suggestions?

@genau7, use keyField on BootstrapTable instead of isKey on TableHeaderColumn
Also, even if you have different custom children for TableHeaderColumn, I think you still can use in a map function,
some pseudo code like this:
headers.map(header => {
    return (
        <TableHeaderColumn key={header.key} dataField={header.key}>
            {   isFunction? header.title() : header.title  }
         </TableHeaderColumn>
    );
});

// header title if is a function, you can return a custom JSX or react component


Yolov5s Edge TPU Compilation - Operation is otherwise supported, but not mapped due to some unspecified limitation

Description
Hello,
The work at https://github.com/zldrobit/yolov5/tree/tf-edgetpu has progressed and compilation with edge tpu compiler v16 maps nearly all operations onto edge tpu but it reports a couple of operations where 'Operation is otherwise supported, but not mapped due to some unspecified limitation'. Is this a bug/limitation in the compiler? It seems it is very close to being able to compile everything onto edge tpu!
Here is a colab notebook for exporting the yolov5s-int8_edgetpu.tflite model.
# Install the Compiler
! curl https://packages.cloud.google.com/apt/doc/apt-key.gpg | sudo apt-key add -
! echo "deb https://packages.cloud.google.com/apt coral-edgetpu-stable main" | sudo tee /etc/apt/sources.list.d/coral-edgetpu.list
! sudo apt-get update
! sudo apt-get install edgetpu-compiler

# Install Branch https://github.com/zldrobit/yolov5/tree/tf-edgetpu
!git clone https://github.com/zldrobit/yolov5.git
%cd yolov5
!git checkout tf-edgetpu
%pip install -qr requirements.txt
from yolov5 import utils
display = utils.notebook_init()  # checks

# Export file Compiled for Coral Edge TPU
%pip install --upgrade flatbuffers==1.12 # downgrade from v2 to v1.12
!python export.py --weights yolov5s.pt --include edgetpu --img 320 --data data/coco128.yaml

This results in an export, with below information.

Edge TPU: starting export with Edge TPU compiler 16.0.384591198...
Edge TPU Compiler version 16.0.384591198
Started a compilation timeout timer of 180 seconds.
Model compiled successfully in 2499 ms.
Input model: yolov5s-int8.tflite
Input size: 7.31MiB
Output model: yolov5s-int8_edgetpu.tflite
Output size: 7.78MiB
On-chip memory used for caching model parameters: 7.02MiB
On-chip memory remaining for caching model parameters: 512.00B
Off-chip memory used for streaming uncached model parameters: 434.62KiB
Number of Edge TPU subgraphs: 1
Total number of operations: 229
Operation log: yolov5s-int8_edgetpu.log
Model successfully compiled but not all operations are supported by the Edge TPU. A percentage of the model will instead run on the CPU, which is slower. If possible, consider updating your model to use only operations supported by the Edge TPU. For details, visit g.co/coral/model-reqs.
Number of operations that will run on Edge TPU: 225
Number of operations that will run on CPU: 4
Operator Count Status
MAX_POOL_2D 3 Mapped to Edge TPU
RESHAPE 3 Mapped to Edge TPU
ADD 7 Mapped to Edge TPU
LOGISTIC 57 Mapped to Edge TPU
CONV_2D 60 Mapped to Edge TPU
QUANTIZE 15 Mapped to Edge TPU
QUANTIZE 2 Operation is otherwise supported, but not mapped due to some unspecified limitation
MUL 57 Mapped to Edge TPU
RESIZE_NEAREST_NEIGHBOR 2 Mapped to Edge TPU
TRANSPOSE 2 Operation is otherwise supported, but not mapped due to some unspecified limitation
TRANSPOSE 1 Mapped to Edge TPU
CONCATENATION 13 Mapped to Edge TPU
PAD 7 Mapped to Edge TPU
Compilation child process completed within timeout period.
Compilation succeeded!
Edge TPU: export success, saved as yolov5s-int8_edgetpu.tflite (8.2 MB)

There are only 4 operations that will not be loaded on the tpu, even though they would be supported. The model, as rendered via netron.app, shown below.

Is this an issue with the complier?
Click to expand!
Issue Type
Bug
Operating System
Linux
Coral Device
USB Accelerator
Other Devices
No response
Programming Language
No response
Relevant Log Output
No response

Here is the exported yolov5s-int8_edgetpu.tflite if that is useful.
yolov5s-int8_edgetpu.tflite.gz

@phodgers It is due to transpose operations size they won't be able to map to edgetpu. Please try with the reduced model input size. Also, please share the uncompiled tflite model. Thanks!

@hjonnala thanks for the reply. The img size is set to 320, so not that large. When I try different img sizes I get different results, sometimes 2 operations not mapped and also the operation differs, it can be transpose, or quantize or reshape. I have also tried the smaller yolov5n (compiles to 2.5 MB, but also the same results in terms of 4 operations not mapped at 320 image size). So it leads me to think there is something else going on with the compiler, it doesn't seem to be a consistent issue. I attach the TFLITE file also generated from a 320 image size. Hopefully it help further.
yolov5s-int8.tflite.gz

Hmm..For yolo5s-int8.tflite transpose operations [(1, 400, 3, 85),(1, 1600, 3, 85)] are too big for edgetpu. I hope reducing the input size would reduce the transpose operations size so that they can be mapped to edge TPU. Can you please share the tflite file, which reshape operation is not mapped. Thanks!

Here are some selected results, I'll post each .tflite and its log output in following posts for reference.
img 224 - 2 operations not mapped due to some unspecified limitation
img 256 - 4 operations not mapped due to some unspecified limitation
img 352 - Compilation failed: Compilation failed due to large activation tensors in model.
img 384 - 5 operations (including RESHAPE) not mapped due to some unspecified limitation.
img 480 - Compilation failed: Compilation failed due to large activation tensors in model.
img 512- 7 operations (including RESHAPE) not mapped due to some unspecified limitation.

img 224
yolov5s-int8.zip

TensorFlow Lite: export success, saved as yolov5s-int8.tflite (7.7 MB)
Edge TPU: starting export with Edge TPU compiler 16.0.384591198...
Edge TPU Compiler version 16.0.384591198
Started a compilation timeout timer of 180 seconds.
Model compiled successfully in 2653 ms.
Input model: yolov5s-int8.tflite
Input size: 7.31MiB
Output model: yolov5s-int8_edgetpu.tflite
Output size: 8.14MiB
On-chip memory used for caching model parameters: 7.41MiB
On-chip memory remaining for caching model parameters: 512.00B
Off-chip memory used for streaming uncached model parameters: 289.12KiB
Number of Edge TPU subgraphs: 1
Total number of operations: 230
Operation log: yolov5s-int8_edgetpu.log
Model successfully compiled but not all operations are supported by the Edge TPU. A percentage of the model will instead run on the CPU, which is slower. If possible, consider updating your model to use only operations supported by the Edge TPU. For details, visit g.co/coral/model-reqs.
Number of operations that will run on Edge TPU: 228
Number of operations that will run on CPU: 2
Operator                       Count      Status
ADD                            7          Mapped to Edge TPU
MAX_POOL_2D                    3          Mapped to Edge TPU
PAD                            7          Mapped to Edge TPU
CONCATENATION                  13         Mapped to Edge TPU
RESHAPE                        3          Mapped to Edge TPU
TRANSPOSE                      1          Operation is otherwise supported, but not mapped due to some unspecified limitation
TRANSPOSE                      2          Mapped to Edge TPU
LOGISTIC                       57         Mapped to Edge TPU
RESIZE_NEAREST_NEIGHBOR        2          Mapped to Edge TPU
MUL                            57         Mapped to Edge TPU
QUANTIZE                       1          Operation is otherwise supported, but not mapped due to some unspecified limitation
QUANTIZE                       17         Mapped to Edge TPU
CONV_2D                        60         Mapped to Edge TPU
Compilation child process completed within timeout period.
Compilation succeeded!
Edge TPU: export success, saved as yolov5s-int8_edgetpu.tflite (8.5 MB)

img 256
yolov5s-int8.zip

TensorFlow Lite: export success, saved as yolov5s-int8.tflite (7.7 MB)
Edge TPU: starting export with Edge TPU compiler 16.0.384591198...
Edge TPU Compiler version 16.0.384591198
Started a compilation timeout timer of 180 seconds.
Model compiled successfully in 2469 ms.
Input model: yolov5s-int8.tflite
Input size: 7.31MiB
Output model: yolov5s-int8_edgetpu.tflite
Output size: 7.69MiB
On-chip memory used for caching model parameters: 7.16MiB
On-chip memory remaining for caching model parameters: 0.00B
Off-chip memory used for streaming uncached model parameters: 293.12KiB
Number of Edge TPU subgraphs: 1
Total number of operations: 229
Operation log: yolov5s-int8_edgetpu.log
Model successfully compiled but not all operations are supported by the Edge TPU. A percentage of the model will instead run on the CPU, which is slower. If possible, consider updating your model to use only operations supported by the Edge TPU. For details, visit g.co/coral/model-reqs.
Number of operations that will run on Edge TPU: 225
Number of operations that will run on CPU: 4
Operator                       Count      Status
QUANTIZE                       2          Operation is otherwise supported, but not mapped due to some unspecified limitation
QUANTIZE                       15         Mapped to Edge TPU
MUL                            57         Mapped to Edge TPU
CONV_2D                        60         Mapped to Edge TPU
RESIZE_NEAREST_NEIGHBOR        2          Mapped to Edge TPU
RESHAPE                        3          Mapped to Edge TPU
TRANSPOSE                      1          Mapped to Edge TPU
TRANSPOSE                      2          Operation is otherwise supported, but not mapped due to some unspecified limitation
CONCATENATION                  13         Mapped to Edge TPU
PAD                            7          Mapped to Edge TPU
LOGISTIC                       57         Mapped to Edge TPU
ADD                            7          Mapped to Edge TPU
MAX_POOL_2D                    3          Mapped to Edge TPU
Compilation child process completed within timeout period.
Compilation succeeded!
Edge TPU: export success, saved as yolov5s-int8_edgetpu.tflite (8.1 MB)

img 352
yolov5s-int8.zip

TensorFlow Lite: export success, saved as yolov5s-int8.tflite (7.7 MB)
Edge TPU: starting export with Edge TPU compiler 16.0.384591198...
Edge TPU Compiler version 16.0.384591198
Started a compilation timeout timer of 180 seconds.
ERROR: Restored original execution plan after delegate application failure.
Compilation failed: Compilation failed due to large activation tensors in model.
Compilation child process completed within timeout period.
Compilation failed!
Edge TPU: export failure: Command 'edgetpu_compiler -s -a yolov5s-int8.tflite' returned non-zero exit status 1.

img 384
yolov5s-int8.zip

TensorFlow Lite: export success, saved as yolov5s-int8.tflite (7.7 MB)
Edge TPU: starting export with Edge TPU compiler 16.0.384591198...
Edge TPU Compiler version 16.0.384591198
Started a compilation timeout timer of 180 seconds.
Model compiled successfully in 2876 ms.
Input model: yolov5s-int8.tflite
Input size: 7.31MiB
Output model: yolov5s-int8_edgetpu.tflite
Output size: 7.75MiB
On-chip memory used for caching model parameters: 7.11MiB
On-chip memory remaining for caching model parameters: 256.00B
Off-chip memory used for streaming uncached model parameters: 342.75KiB
Number of Edge TPU subgraphs: 1
Total number of operations: 229
Operation log: yolov5s-int8_edgetpu.log
Model successfully compiled but not all operations are supported by the Edge TPU. A percentage of the model will instead run on the CPU, which is slower. If possible, consider updating your model to use only operations supported by the Edge TPU. For details, visit g.co/coral/model-reqs.
Number of operations that will run on Edge TPU: 224
Number of operations that will run on CPU: 5
Operator                       Count      Status
TRANSPOSE                      1          Mapped to Edge TPU
TRANSPOSE                      2          Operation is otherwise supported, but not mapped due to some unspecified limitation
CONCATENATION                  13         Mapped to Edge TPU
PAD                            7          Mapped to Edge TPU
RESIZE_NEAREST_NEIGHBOR        2          Mapped to Edge TPU
QUANTIZE                       2          Operation is otherwise supported, but not mapped due to some unspecified limitation
QUANTIZE                       15         Mapped to Edge TPU
MUL                            57         Mapped to Edge TPU
CONV_2D                        60         Mapped to Edge TPU
LOGISTIC                       57         Mapped to Edge TPU
ADD                            7          Mapped to Edge TPU
MAX_POOL_2D                    3          Mapped to Edge TPU
RESHAPE                        1          Operation is otherwise supported, but not mapped due to some unspecified limitation
RESHAPE                        2          Mapped to Edge TPU
Compilation child process completed within timeout period.
Compilation succeeded!
Edge TPU: export success, saved as yolov5s-int8_edgetpu.tflite (8.1 MB)

img 512
yolov5s-int8.zip

TensorFlow Lite: export success, saved as yolov5s-int8.tflite (7.7 MB)
Edge TPU: starting export with Edge TPU compiler 16.0.384591198...
Edge TPU Compiler version 16.0.384591198
Started a compilation timeout timer of 180 seconds.
Model compiled successfully in 3438 ms.
Input model: yolov5s-int8.tflite
Input size: 7.31MiB
Output model: yolov5s-int8_edgetpu.tflite
Output size: 7.52MiB
On-chip memory used for caching model parameters: 6.89MiB
On-chip memory remaining for caching model parameters: 1.00KiB
Off-chip memory used for streaming uncached model parameters: 175.00KiB
Number of Edge TPU subgraphs: 1
Total number of operations: 229
Operation log: yolov5s-int8_edgetpu.log
Model successfully compiled but not all operations are supported by the Edge TPU. A percentage of the model will instead run on the CPU, which is slower. If possible, consider updating your model to use only operations supported by the Edge TPU. For details, visit g.co/coral/model-reqs.
Number of operations that will run on Edge TPU: 222
Number of operations that will run on CPU: 7
Operator                       Count      Status
CONCATENATION                  13         Mapped to Edge TPU
PAD                            7          Mapped to Edge TPU
TRANSPOSE                      3          Operation is otherwise supported, but not mapped due to some unspecified limitation
ADD                            7          Mapped to Edge TPU
MAX_POOL_2D                    3          Mapped to Edge TPU
MUL                            57         Mapped to Edge TPU
QUANTIZE                       14         Mapped to Edge TPU
QUANTIZE                       3          Operation is otherwise supported, but not mapped due to some unspecified limitation
LOGISTIC                       57         Mapped to Edge TPU
CONV_2D                        60         Mapped to Edge TPU
RESIZE_NEAREST_NEIGHBOR        2          Mapped to Edge TPU
RESHAPE                        2          Mapped to Edge TPU
RESHAPE                        1          Operation is otherwise supported, but not mapped due to some unspecified limitation
Compilation child process completed within timeout period.
Compilation succeeded!
Edge TPU: export success, saved as yolov5s-int8_edgetpu.tflite (7.9 MB)

img 480
yolov5s-int8.zip

please try the command below for this model (image 480):
!edgetpu_compiler -s  -i "model/tf_detect/Reshape_2/shape_1"  yolov5s-int8_480.tflite
and for (image 352):
edgetpu_compiler -s  -i "model/tf_detect/Reshape/shape_1"  yolov5s-int8_352.tflite
In all  cases operations are not mapped due to edge TPU compiler limitations with the operation sizes.. Thanks!

@hjonnala Yes I can see using above options, that the 352 and 420 can now both also compile, with some more unsupported operations.
Do you have a feeling for whether the TPU compiler limitations are something that could be overcome with future release of compiler, or is it an issue that is unlikely to be possible for technical reasons?
Thanks,

I am not sure, most likely it is not possible map the large size operations especially  transpose and reshape operations.


framework7-icons npm package is not working in this webpack template

After npm install framework7-icons --save, the icons are not available in both dev and build env.
Only default icons (e.g. <f7-link icon="icon-bars" open-panel="left"></f7-link>) works properly.
<f7-icon f7="refresh"></f7-icon> fails to show up. (display blank only)
I am wondering whether it is related to the webpack font copying process. I need some advices to fix this. Meanwhile I manually copy the framework7-icons source to my app source to make things work.

Run into the same issue.
Adding this line in main.js file fixed it
import Framework7Icons from 'framework7-icons/css/framework7-icons.css'

@maurodaprotis not work for me.

I am having the same problem

why it closed? it's still not working

I have the same problem, there is some icons not appears. ex. logo_facebook, logo_github, etc.


[Bug] Using deprecated APIs

Hi there, your plugin was denied with reason:

The plugin is using all the deprecated APIs, please see the docs and update to the newer versions. After that please resubmit, the plugin looks great otherwise!

Please take a look at the documentation for the API and make sure you are using the current methods instead of the old ones. (i.e. use BdApi.Webpack over BdApi.findModuleByProps or BdApi.Data over BdApi.loadData).
Here is the plugin guide: https://docs.betterdiscord.app/plugins/
Here is the api reference: https://docs.betterdiscord.app/api/bdapi
Other than that, the plugin looks great! I'd love to see this updated and resubmitted. Feel free to ping me (Zerebos) once you do and I'll be sure to give it a priority review.

New update looks good, only thing I would say is to remove these:
    getName() { return "ChannelsBadges"; }
    getDescription() { return "Add Voice | Forum | Nsfw | Rule | Ads badges to channels."; }
    getVersion() { return "1.1.0"; }
    getAuthor() { return "Sheiylanie"; }

Those are long deprecated and it's just a duplication of the information in the meta comment. BTW the info in the meta comment is passed to the constructor of the plugin so you can still access the information programmatically.
class MyPlugin {
    constructor(meta) {
        this.meta = meta;
    }

    someOtherFunc() {
        console.log(this.meta.version);
    }
}

I'll still be approving the plugin, but just something to note!


Update dataset with congresspeople social media account

What is the purpose of this Pull Request?
The purpose is to update the dataset with congresspeople Twitter accounts, as we have two reports of new accounts (here and here).
What was done to achieve this purpose?
I updated the Google Spreadsheet and generated a new .xz version of the CSV. The file is already in S3.
How to test if it really works?
Try to download the latest datasets (as in the README.md) and check if a file with today's date and the Twitter account data is downloaded within the bunch. The fle name is 2018-02-05-congresspeople-social-accounts.xz.
Who can help reviewing it?
@anaschwendler @jtemporal @Irio

The fle name is 2017-06-11-congresspeople-social-accounts.xz.

The correct file name is: 2018-02-05-congresspeople-social-accounts.xz
Did exactly what @cuducos said on the How to test if it really works?  section (plus the file name correctio). It works =)

The correct file name is: 2018-02-05-congresspeople-social-accounts.xz

True story 🥂


Fixes dev server "ArgumentError" crashes by updating ruby, rails, other dependencies.

Spent a few hours debugging #70 and got to a state where it no longer crashes with this error by updating several dependencies (and fixing the issues that arose from doing that). This is based on #58.

Thanks @vimota! I was able to get this running locally using your fixes branch. I hope it gets merged soon.


Add shorthands for fixed width integer types

Added shorthands for fixed-width integer types, as they tend to get noisy without type deduction.

[x] I've read [CONTRIBUTING.md]
[ ] I've added new test cases to verify my change
[ ] I've updated any affected documentation
[x] I've rebuilt and run the tests with at least one of:

[ ] Clang 9 or higher
[ ] GCC 9 or higher
[x] Visual Studio 2022

Hmmn, what is the value of this? Personally I prefer the aliases in  since they're idiomatic C++.

@marzer done :)

Hmmn, what is the value of this? Personally I prefer the aliases in <cstdint> since they're idiomatic C++.

Syntactic suggestion to be more inline with the literals suffix really, matter of personal preference more than any real value. I was using it with Muu so I thought I might as well PR back to remote

Syntactic suggestion to be more inline with the literals suffix really

Ah yeah, that's a good point. Then there's a nice symmetry, e.g.:
i64 value = 6_i64;

Oh, whoops. Looks like you inherited my typo 😅


Signup page keeps saying admin registration is still open

https://github.com/rickbergfalk/sqlpad/blob/v2.5.4/client-js/SignUp.js#L44
The || true override seems to have been included since v2.5.0.

Thanks for reporting this! I must have forgot that when testing the style changes. This will be fixed in next release


always get this issue. Why?

Product and Version [VS/VSCode]:
OS Version [macOS/Windows/Linux]:
Live Share Extension Version:
Target Platform or Language [e.g. Node.js]:
What were you doing when you encountered the desync?
How often have you encountered desyncs?

I'm closing this issue as a duplicate of #3197. Please upload your logs there so we can diagnose the problem.


panic from subtraction overflow during merge, multi-valued fastfield

Describe the bug

What did you do?

Ran indexing process, which periodically indexes a batch of documents and commits.

What happened?

The application panicked (crashed).
Message:  attempt to subtract with overflow
Location: /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/tantivy-0.16.0/src/fastfield/multivalued/reader.rs:71

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
                                ⋮ 12 frames hidden ⋮
  13: core::panicking::panic::hbb13bbcfbaa2890b
      at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/core/src/panicking.rs:50
  14: tantivy::fastfield::multivalued::reader::MultiValuedFastFieldReader<Item>::num_vals::heaf368d0a6f14b43
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/tantivy-0.16.0/src/fastfield/multivalued/reader.rs:71
        69 │     pub fn num_vals(&self, doc: DocId) -> usize {
        70 │         let range = self.range(doc);
        71 >         (range.end - range.start) as usize
        72 │     }
        73 │
  15: <tantivy::fastfield::multivalued::reader::MultiValuedFastFieldReader<Item> as tantivy::fastfield::MultiValueLength>::get_len::h231cf36bdce28e4d
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/tantivy-0.16.0/src/fastfield/multivalued/reader.rs:83
        81 │ impl<Item: FastValue> MultiValueLength for MultiValuedFastFieldReader<Item> {
        82 │     fn get_len(&self, doc_id: DocId) -> u64 {
        83 >         self.num_vals(doc_id) as u64
        84 │     }
        85 │
  16: tantivy::indexer::merger::IndexMerger::write_1_n_fast_field_idx_generic::h7b089a49f7c55428
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/tantivy-0.16.0/src/indexer/merger.rs:510
       508 │                 for doc in 0u32..reader.max_doc() {
       509 │                     if delete_bitset.is_alive(doc) {
       510 >                         let num_vals = u64s_reader.get_len(doc) as u64;
       511 │                         total_num_vals += num_vals;
       512 │                     }
  17: tantivy::indexer::merger::IndexMerger::write_multi_value_fast_field_idx::hff15ed17f4f18c09
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/tantivy-0.16.0/src/indexer/merger.rs:565
       563 │         }).collect::<Vec<_>>();
       564 │
       565 >         Self::write_1_n_fast_field_idx_generic(
       566 │             field,
       567 │             fast_field_serializer,
  18: tantivy::indexer::merger::IndexMerger::write_multi_fast_field::h8a8cf09448a3fc71
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/tantivy-0.16.0/src/indexer/merger.rs:657
       655 │         // First we merge the idx fast field.
       656 │         let offsets =
       657 >             self.write_multi_value_fast_field_idx(field, fast_field_serializer, doc_id_mapping)?;
       658 │
       659 │         let mut min_value = u64::max_value();
  19: tantivy::indexer::merger::IndexMerger::write_fast_fields::h6be8ac9b0cab83c0
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/tantivy-0.16.0/src/indexer/merger.rs:298
       296 │                     }
       297 │                     Some(Cardinality::MultiValues) => {
       298 >                         self.write_multi_fast_field(field, fast_field_serializer, doc_id_mapping)?;
       299 │                     }
       300 │                     None => {}
  20: tantivy::indexer::merger::IndexMerger::write::h08cf0320d357591c
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/tantivy-0.16.0/src/indexer/merger.rs:1099
      1097 │             &doc_id_mapping,
      1098 │         )?;
      1099 >         self.write_fast_fields(
      1100 │             serializer.get_fast_field_serializer(),
      1101 │             term_ord_mappings,
  21: tantivy::indexer::segment_updater::merge::hdc3230d728afdd61
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/tantivy-0.16.0/src/indexer/segment_updater.rs:142
       140 │     let segment_serializer = SegmentSerializer::for_segment(merged_segment.clone(), true)?;
       141 │
       142 >     let num_docs = merger.write(segment_serializer)?;
       143 │
       144 │     let merged_segment_id = merged_segment.id();
  22: tantivy::indexer::segment_updater::SegmentUpdater::start_merge::{{closure}}::h92bac4c09cef47c4
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/tantivy-0.16.0/src/indexer/segment_updater.rs:498
       496 │             // as well as which segment is currently in merge and therefore should not be
       497 │             // candidate for another merge.
       498 >             match merge(
       499 │                 &segment_updater.index,
       500 │                 segment_entries,
  23: <core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll::h0b9ec7c8a2a6a500
      at /rustc/a178d0322ce20e33eac124758e837cbd80a6f633/library/core/src/future/mod.rs:80
  24: <futures_task::future_obj::LocalFutureObj<T> as core::future::future::Future>::poll::h82b8c2584ca1d3c0
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-task-0.3.17/src/future_obj.rs:84
        82 │     #[inline]
        83 │     fn poll(mut self: Pin<&mut Self>, cx: &mut Context<'_>) -> Poll<T> {
        84 >         unsafe { Pin::new_unchecked(&mut *self.future).poll(cx) }
        85 │     }
        86 │ }
  25: <futures_task::future_obj::FutureObj<T> as core::future::future::Future>::poll::ha493c3e4cc50bed8
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-task-0.3.17/src/future_obj.rs:127
       125 │     #[inline]
       126 │     fn poll(mut self: Pin<&mut Self>, cx: &mut Context<'_>) -> Poll<T> {
       127 >         Pin::new(&mut self.0).poll(cx)
       128 │     }
       129 │ }
  26: futures_util::future::future::FutureExt::poll_unpin::h2db2c56d1c89396f
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-util-0.3.17/src/future/future/mod.rs:562
       560 │         Self: Unpin,
       561 │     {
       562 >         Pin::new(self).poll(cx)
       563 │     }
       564 │
  27: futures_executor::thread_pool::Task::run::h469ec9cc1fc5fa80
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-executor-0.3.17/src/thread_pool.rs:322
       320 │
       321 │             loop {
       322 >                 let res = future.poll_unpin(&mut cx);
       323 │                 match res {
       324 │                     Poll::Pending => {}
  28: futures_executor::thread_pool::PoolState::work::haf842fd80f3d5b25
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-executor-0.3.17/src/thread_pool.rs:154
       152 │             let msg = self.rx.lock().unwrap().recv().unwrap();
       153 │             match msg {
       154 >                 Message::Run(task) => task.run(),
       155 │                 Message::Close => break,
       156 │             }
  29: futures_executor::thread_pool::ThreadPoolBuilder::create::{{closure}}::h4de4015d663fd980
      at /Users/sbhushan/.cargo/registry/src/github.com-1ecc6299db9ec823/futures-executor-0.3.17/src/thread_pool.rs:284
       282 │                 thread_builder = thread_builder.stack_size(self.stack_size);
       283 │             }
       284 >             thread_builder.spawn(move || state.work(counter, after_start, before_stop))?;
       285 │         }
       286 │         Ok(pool)
                                ⋮ 13 frames hidden ⋮

What was expected?

No panic in merge.

Some bugs are not deterministic. Can you describe with precision in which context it happened?

Not deterministic, once the index is in this state it reproduces but not sure what caused it to get into such a state. Rebuilding the index fixes the problem. If I see a pattern to when the index is entering such a state, I will note here. It has happened twice so far.

If this is possible, can you share your code?

Afraid not, for now. Full disclosure: this is happening when using a custom Directory implementation, there is a chance that could be implicated. I will try to reproduce with a regular MMapDirectory, but wanted to report the issue in case a bug if apparent to tantivy devs based on the stacktrace.

Hi Shikar,
thank you for the bug report.
The multivalued fast field is in fact two fast fields, one fast field to get the range of the multi values (internally idx_reader) for a document and one fastfield with a flat list of all values (internally vals_reader).

The issue here is coming from the idx_reader. They need to be monotonically increasing to get the range, which they are not.
Since tantivy 0.16 we have 3 different codecs, which are automatically detected depending on the data in the fast field. In the index usually linearinterpolation or multilinear interpolation is used.
Do you still have the broken index e.g. to get the detected codec or some other information about the broken state? That would be helpful.
I'll try to reproduce something in our tests.

@shikhar
Thank you for the report! Are you sorting your index by a specific field?

@shikhar thanks again for the report. I could find the issue. It was a off by one error in the stats, which were only relevant in some cases. #1151

Do you still have the broken index e.g. to get the detected codec or some other information about the broken state? That would be helpful.

Yes, I do currently! There is only one multi-valued fast field. I don't think I can share the index with you but happy to help in remote diagnosing e.g. figure out codec.

Are you sorting your index by a specific field?

no

Can you confirm the bug happen on an index created by 0.16 and used by 0.16?

yes

It was a off by one error in the stats, which were only relevant in some cases. #1151

Awesome, I can try to run with that patch! The index is ending up in this state sooner or later so if it runs fine for a few hours I think that should be good confidence about this being the bug.

@PSeitz 2h in looking good, I'm pretty confidence this fixes it!

published in 0.16.1. Apologies for the terrible bug :-S


Is there any function calling model for tinyllama?

tinyllama which finetuning by function calling

There def may be ways to improve on what I'm trying, but it's pretty hard to get such small models to work well. You can see this vid.


Add support for setting Global ID for Overviews from outside.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.4 out of 6 committers have signed the CLA.:white_check_mark: enizhou:white_check_mark: npomaroli:white_check_mark: deckdom:white_check_mark: guggi:x: Serhii Plyhun:x: GenticsDevSerhii Plyhun seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

No single idea how this

turned on push into 16 commits and 79 edits.

plyhun@plyhun-kubuntu:~/gtx-cms-workspace/cms-oss$ git checkout hotfix-6.0.x
Switched to branch 'hotfix-6.0.x'
plyhun@plyhun-kubuntu:~/gtx-cms-workspace/cms-oss$ git pull
Enter passphrase for key '/home/plyhun/.ssh/id_rsa':
Current branch hotfix-6.0.x is up to date.


Improve display of freelook/zoom speed indicator bars in the 3D editor

Use a different color for freelook and zoom speed bars.
Use an outline for the text to make it readable on any background.

Preview
Before
https://user-images.githubusercontent.com/180032/158072728-9eab0b7d-3427-4bd0-9b0b-8dd00d961cda.mp4
After
https://user-images.githubusercontent.com/180032/158072732-b7ef94e5-bc54-407c-b88a-ab58ea283108.mp4

Thanks!


Missing #include throws an exception

If you include a nonexistent file it should output an error, but it currently throws.

Fixed by 28a83dfed7e64d66f7bc71a2326dacc4897c640f.


[WIP] Replace the etcdctl proc call with etcd client.

What do these changes do?
As titled
Related issue number
Fixes https://github.com/v6d-io/v6d/issues/1945

The e2e-tests-five-etcd-nodes-failover always failed, wait for debugging.


ackee: init at 3.3.0

Motivation for this change
Ackee is a self-hosted, Node.js based analytics tool for those who care about privacy: electerious/Ackee
I previously tried in #122822, but the web interface didn’t work there (only the api). Now finally got the web interface working too.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[x] (Module addition) Added a release notes entry if adding a new NixOS module
[x] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Rebased to fix merge conflicts

Rebased to fix merge conflicts in the release notes.

I switched away from ackee because building mongodb from source took so long (and I hit some build errors).


build(styles): modify build configs

:tada: This PR is included in version 1.3.1 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Running two python versions concurrently

since creating the privateGPT instance in the localhost 8001requires python 3.11 (and not 3.12)
and importing PrivateGPTApi in the python code requires python 3.12
the way im running it in WSL2 is opening 2 ubuntu command lines interfaces each with a corresponding conda enviorment one to run the instance and one to run the code.
is this the intended way? or did i miss something obvious.
(side note) how do i change the system prompt from my code
and if i change it from the GUI through additional inputs. does that change apply to the code?

We just released v0.1.2 which lowers the python required version to 3.11 to align it with PrivateGPT


Fix null issue in lastMessageText

Details
It fixes https://expensify.slack.com/archives/C049HHMV9SM/p1681445959245769 and https://expensify.slack.com/archives/C049HHMV9SM/p1681452005073379
Fixed Issues

$ https://github.com/Expensify/App/issues/15131
PROPOSAL: GH_LINK_ISSUE(COMMENT)
Tests

Go offline
Click on + button > New Chat
Start new chat with an email address with whom you don’t have a chat history
Check the LHN
Verify that LHN shows "This is the beginning of your…" instead of null.

[x] Verify that no errors appear in the JS console

Offline tests

Go offline
Click on + button > New Chat
Start new chat with an email address with whom you don’t have a chat history
Check the LHN
Verify that LHN shows "This is the beginning of your…" instead of null.

QA Steps

Go offline
Click on + button > New Chat
Start new chat with an email address with whom you don’t have a chat history
Check the LHN
Verify that LHN shows "This is the beginning of your…" instead of null.

[ ] 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 grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is 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 code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[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
https://user-images.githubusercontent.com/25876548/231976550-d8c2027d-b3bf-4ce9-96d8-4e3e5a2cb269.mov

Mobile Web - Chrome
https://user-images.githubusercontent.com/25876548/231987068-9523afbd-6b0b-4097-bd13-ee61dcc069e9.mov

Mobile Web - Safari
https://user-images.githubusercontent.com/25876548/231987088-28c4f185-2c41-48f9-8b62-9fdf67c95917.mov

Desktop
https://user-images.githubusercontent.com/25876548/231985480-f4de878d-51e3-43ba-80bb-be9d7d1f72c0.mov

iOS
https://user-images.githubusercontent.com/25876548/231988082-04a19845-4f95-4aea-b26f-a8b4a24d0023.mov

Android
https://user-images.githubusercontent.com/25876548/231989601-6d980a44-43ce-4a6b-84d1-98df28fc7c96.mov

@jayeshmangwani I was unable to reproduce the issue on IOS. Can you please help me test this PR on IOS. Please let me know if it does not fix the issue on IOS.

@sobitneupane I'm on it

@sobitneupane Yes your changes solve the crash, attaching a video of the before after crash
https://drive.google.com/file/d/1uhHWwv6EPN9fx_OQ2BXInQVoZA5SX7yv/view?usp=sharing

@pecanoro @s77rt One of you needs to 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]

This PR is created to solve the regression caused by https://github.com/Expensify/App/pull/16957

@sobitneupane Your changes look good to me and I tested it works well

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] 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)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

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

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] 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).
[ ] I verified that comments were added to code that is not self explanatory
[ ] 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.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] 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.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] 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
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] 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)
[ ] 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)
[ ] All JSX used for rendering exists in the render method
[ ] 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

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

[ ] 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

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

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

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] 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)
[ ] 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.
[ ] 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.
[ ] 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.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

Testing on iOS

Having some trouble since I am getting "New Expensify quit unexpectedly" when trying to run it on iOS. I am looking into it but it's pretty odd

It does work on iOS!

: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/pecanoro in version: 1.3.1-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to staging by https://github.com/pecanoro in version: 1.3.1-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
failure ❌

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/mountiny in version: 1.3.1-3 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Backporting action links to non-existing CONTRIBUTING section

Describe the bug
The backporting action links to:
https://github.com/NixOS/nixpkgs/blob/master/CONTRIBUTING.md#criteria-for-backporting-changes

but this section does not exist in the CONTRIBUTING.md file.
Pinging both accounts that were involved in the backporting action and the contributing file:
@mweinelt @Mic92 @AndersonTorres @infinisil

Thanks for the report! I did miss this one, but it was also later reported after which I fixed it here: https://github.com/NixOS/nixpkgs/pull/253621


Update documentation to reflect required Node version

With the release of v2.5, we changed from istanbuljs (nyc) to using c8 as our test coverage tool.
This change now means that we no longer support older versions of Node when contributing to the CLI, we now require v12 or higher.
We should update our documentation to reflect this change.

package.json is not the right place to do it, because it would indicate that you need Node@12 to use the CLI. We require Node@12 only when contributing to it to run tests using c8. You should be be able to use the CLI with older Node versions as well though.

Good spot @waldekmastykarz 👍🏻
I have updated the issue description.

Coming back to this, the c8 docs state that the version of node required is >= 10.12.0 not 12 so will update our docs based on this.
https://github.com/bcoe/c8#supported-nodejs-versions

v10 is the minimum, but some of our tests fail if you don't run them on v12 😊

Updated 👍🏻


Updating APEX default version to v2.6.3

Updating APEX default version to v2.6.3
Proposed Changes

see changelist here: https://github.com/UO-OACISS/apex/releases/tag/v2.6.3

Any background context you want to provide?
Checklist
Not all points below apply to all pull requests.

[ ] I have added a new feature and have added tests to go along with it.
[ ] I have fixed a bug and have added a regression test.
[ ] I have added a test using random numbers; I have made sure it uses a seed, and that random numbers generated are valid inputs for the tests.
[x]  I tested the change :)

bors merge


Add IsGroup to PlayerInfo

I did not test this because I haven't gone through the process of building it before. It looks like the one above it so it probably works fine.

Oh also this could and probably should be a property rather than a method

Sorry, not familiar enough with the syntax. Would that be something like this?
		public bool IsGroup { get; set; } = GroupMembers != null && GroupMembers.Length > 0;

public bool IsGroup => GroupMembers != null && GroupMembers.Length > 0;

Above would be the best way to go, read-only property with an expression body syntax

For educational purposes yours would allow the outside world to set it, and additionally it would be set when the instance is created instead of evaluated on request.
The most verbose correct way would be like this with a number of more concise intermediate options.
public bool IsGroup
{
    get
    {
        return GroupMembers != null && GroupMembers.Length > 0;
    }
}


Disable social logins when the associated provider is not available

Overview
Login with Google, Discord, Twitch only work if the associated social login provider is available.  This typically requires access to an API key and, therefore, does not work for the opensource local deployment build (i.e. ./b data-snapshot run). However, on http://localhost:3000 (the splash page for the local build) the social logins are still listed, and do nothing or crash the web server when clicked.
Desired solution
Conditionally render the social logins based on whether the social login provider is available. A brute-force approach would be to not show the social logins if using the data-snapshot build.

was that issue solved??

You should disable Discord web hooks by adding:
discordHooksEnabled: false


Importing select with 2018 edition

(Caution: I'm not sure if this may be a language issue still in the works.)
When I try to do use crossbeam_channel::select to import the macro on Rust 2018, since select! uses two helper macros I have to import these as well, ending up with
use crossbeam_channel::{select, __crossbeam_channel_parse, __crossbeam_channel_codegen};

Yes, this is an annoying one. I can't wait for the new macro system to get over the finish line. :)
For now, I'll just merge the two helper macros with the main one so that we don't have to deal with these kinds of issues.

Thanks!


Doing azd up on the todo-csharp-sql creates SQL resources but doesn't list them in the output

Output from azd version
azd version 0.4.0-beta.1 (commit 2bf7a529914d86d8e9f5d7b6f95a4f20a2351e01)
Output from az version
{
  "azure-cli": "2.42.0",
  "azure-cli-core": "2.42.0",
  "azure-cli-telemetry": "1.0.8",
  "extensions": {}
}

Describe the bug
I did azd up on a todo-csharp-sql app, and it did deploy the SQL resources, but did not list them in the output log:

To Reproduce

azd init, choose todo-csharp-sql
azd up

Expected behavior
The SQL resources would be included in the output
Environment
Information on your environment:
* .NET 7.0 installed
* VSCode 1.74.1

dupe: https://github.com/Azure/azure-dev/issues/857


Add power_off to group control types

Description:
Adds power_off to group control types. Behaviour: home-assistant/home-assistant-polymer#383
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#3169
Example entry for configuration.yaml (if applicable):
group:
  kitchen:
    name: Kitchen
    control: power_off
    entities:
      - switch.kitchen_pin_3
      - switch.kitchen_pin_3

Checklist:
If user exposed functionality or configuration variables are added/changed:

[x] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] New dependencies have been added to the REQUIREMENTS variable (example).
[x] New dependencies are only imported inside functions that use them (example).
[x] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[x] New files were added to .coveragerc.

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[x] Tests have been added to verify that the new code works.

See https://github.com/home-assistant/home-assistant-polymer/pull/383#issuecomment-321949113


How to download this mod?

Hi, can you explain how to install this mod to Minecraft?

Do you already have fabric and use litematica?

Do you already have fabric and use litematica?

Yea, understood how it works. Thanks for mod!

Yea, understood how it works. Thanks for mod!


JBPM-4646 - Case management - support for reopening the case

depends on https://github.com/droolsjbpm/jbpm/pull/629
@sutaakar as we talked about it the other day :) can you take a look?

Looks good :)
Just had one minor question.

jenkins retest this


More warnings

Warnings

refs-must-have-owner
invalid-aria-prop
dont-call-proptypes

Relates to: https://github.com/reactjs/es.reactjs.org/issues/79

@alejandronanez done with the changes 👍


Use dual-mode packages (.js & .mjs)

An ESM build is output with the .mjs extension, while a CommonJS build is output with the .js extension. In package.json, the "main" field has no extension, which allows the system to choose which module to resolve with.
UMD builds now have the extension .umd.js because the CommonJS builds needed to be just .js.
.mjs files exist in a bit of an odd place right now. In order to use them with node, the --experimental-modules flag has to be used. Webpack and Rollup support them, although I am unsure to what extent.

I had initially removed pkg.module fields, but was having an issue with Rollup only resolving the CJS build when bundling @curi/react-universal into @curi/react-dom's UMD build. I restored pkg.module, but the issue was really that I was using an old version of rollup-plugin-node-resolve that didn't know to look for .mjs files.
At this point in time, I'm not certain whether or not to keeppkg.module, but I do not believe that it is hurting anything, so it will stay for now.


Switched from _app_ctx_stack to flask.g

This PR addresses the incompatibilities mentioned in #1068 by using the flask.g object instead of _app_ctx_stack.top.

Hey @davidism would you be able to look at this sometime soonish? It's the source of a ton of warnings since the update to Flask 2.2.2

Some minor nitpick things that might be a slight bit better. Disclaimer is that I am an outsider.
Hopefully this gets the attention to get merged soon, for me it's responsible for around 10,000 new warnings since upgrading Flask.

Yeah - we are currently sitting on 43,000 warnings

Fixed in https://github.com/pallets-eco/flask-sqlalchemy/pull/1087. Using db.session or db.engine now always requires an active Flask application context. The session is scoped to the current context, which ensures it is always cleaned up.


[PIRK-30]: Pirk compile no longer fails with RAT checks

Travis is failing the PR with the following error:
[ERROR] Failed to execute goal org.apache.rat:apache-rat-plugin:0.11:check (default) on project pirk: Too many files with unapproved license: 1 See RAT report in: /home/travis/build/apache/incubator-pirk/target/rat.txt -> [Help 1]
Does anyone know how to check/access the report /home/travis/build/apache/incubator-pirk/target/rat.txt? I've had this happen some and it just required a bit of cleaning...

After long debugging and messing with Travis, here's the culprit

This issue is fixed now, and the PR is good to merge.

+1 -- will merge now. Thanks for fixing this issue!


How to dynamically define mimeType when uploading a file

Hello,
In the code below (from google documentation v3), the mimeType has a value of "application/vnd.google-apps.spreadsheet" because the actual file is a csv file.
But what if we don't know what type of file the user will upload, what should be the value of mimeType?
$fileMetadata = new Google_Service_Drive_DriveFile(array(
    'name' => 'My Report',
    'mimeType' => 'application/vnd.google-apps.spreadsheet'));

$content = file_get_contents('files/report.csv');

$file = $driveService->files->create($fileMetadata, array(
    'data' => $content,
    'mimeType' => 'text/csv',
    'uploadType' => 'multipart',
    'fields' => 'id'));
printf("File ID: %s\n", $file->id);

Drive will attempt to automatically detect an appropriate value from uploaded content if no value is provided. The value cannot be changed unless a new revision is uploaded.
If a file is created with a Google Doc MIME type, the uploaded content will be imported if possible. The supported import formats are published in the About resource.

Hi Matt,
It gives me funny characters when i try to upload a file


Targeting Control Systems Perk - Incorrect Values

According to the description in the menu, the Targeting Control Systems perk should decrease target lock-on time by 15% at rank 2, 30% at rank 3, and 60% at rank 4.
What it actually does is decrease the lock-on time by 15% at rank 2, 15% at rank 3, and 30% at rank 4.

Details
I have simply changed the abFortifyTargetLockTime magnitude to 0.3 in abTargetingControlSystems_TargetLockTime_02 [SPEL: 002CCF94], and changed it to 0.6 in abTargetingControlSystems_TargetLockTime_03 [SPEL: 002CCF95]. These spells are only ever referenced by this perk, so changing these values does nothing except fix this issue.
Game Version
<IP_ADDRESS>
Language
English (EN)
New Game
Yes
Reproduction Steps
Take rank 2 of the targeting control systems perk. Select your ship in the command console, and use getav spaceshiptargetlocktime. The value should return 2.55, representing a 15% decrease from the base 3.00 value.
Then, take rank 3 of the perk. It will still return 2.55, instead of the expected 30% decrease to 2.1.
Then take rank 4, and you will now see 2.1 instead of the expected 1.2.

Fix here: https://1drv.ms/u/s!AhuMaF-FsKU-lEKXXcglJymrItIk?e=hvR9rk


Be able to select from multiple theme in the demo app

We could take inspiration from Google's material catalog:
https://play.google.com/store/apps/details?id=androidx.compose.material.catalog&hl=en&gl=US
They already have a nice UI to configure the displayed theme and colors

Yep I was going to propose it 😋


Extend kustomize controller health assessment to support HelmReleases

If the kustomize controller health assessment was extended to support HelmReleases the kustomize-controller could be used to deploy helmreleases custom resources and detect execution outcome based on HR status. This would enable users to define kustomization custom resources linked by the dependsOn field and sequence deployment of HelmReleases with other object creations.

Could also consider integrating the kstatus library to get coverage for all the resource types it supports, which includes HelmRelease v2, since it supports the Ready condition

@seaneagan if kstatus waits for a resource to be created before trying to fetch the ready status then we can replace the current implementation.

I ran some quick tests to see how kstatus behaves in different scenarios with deployments.
I quickly wrote some code that would poll the status of a deployment. I started the polling before the deployment existed, allowed it to reconcile and be ready, then deleted it again.
Id: default_dep_apps_Deployment
Status: NotFound
Message: Resource not found
EventType: ResourceUpdateEvent

Id: default_dep_apps_Deployment
Status: InProgress
Message: Available: 0/1
EventType: ResourceUpdateEvent

Id: default_dep_apps_Deployment
Status: Current
Message: Deployment is available. Replicas: 1
EventType: ResourceUpdateEvent

Id: default_dep_apps_Deployment
Status: Current
Message: Deployment is available. Replicas: 1
EventType: ResourceUpdateEvent

Id: default_dep_apps_Deployment
Status: NotFound
Message: Resource not found
EventType: ResourceUpdateEvent

It looks like kstatus does what it advertises, as long as the CRD implements the status it expects. Just need to check how it behaves with HelmReleases, but if it has a similar status I guess it should be fine. Using kstatus would be preferable as we would not have to verify if every single CRD works with the health check.
For reference if you want to try this yourself.
package main

import (
	"context"
	"fmt"

	"k8s.io/apimachinery/pkg/runtime/schema"
	"k8s.io/client-go/discovery"
	"k8s.io/client-go/discovery/cached/memory"
	"k8s.io/client-go/restmapper"
	"sigs.k8s.io/cli-utils/pkg/kstatus/polling"
	"sigs.k8s.io/cli-utils/pkg/object"
	"sigs.k8s.io/controller-runtime/pkg/client"
	"sigs.k8s.io/controller-runtime/pkg/client/config"
)

func main() {
	cfg := config.GetConfigOrDie()
	reader, err := client.New(cfg, client.Options{})
	if err != nil {
		panic(err)
	}

	identifiers := []object.ObjMetadata{
		{
			GroupKind: schema.GroupKind{
				Group: "apps",
				Kind:  "Deployment",
			},
			Name:      "dep",
			Namespace: "default",
		},
	}

	dc, err := discovery.NewDiscoveryClientForConfig(cfg)
	if err != nil {
		panic(err)
	}
	mapper := restmapper.NewDeferredDiscoveryRESTMapper(memory.NewMemCacheClient(dc))

	poller := polling.NewStatusPoller(reader, mapper)
	opt := polling.Options{
		PollInterval: 2,
	}
	eventsChan := poller.Poll(context.Background(), identifiers, opt)
	for e := range eventsChan {
		fmt.Printf("Id: %v\n", e.Resource.Identifier.String())
		fmt.Printf("Status: %v\n", e.Resource.Status.String())
		fmt.Printf("Message: %v\n", e.Resource.Message)
		fmt.Printf("EventType: %v\n", e.EventType.String())
		fmt.Println()
	}
}


Should we rename this action scala-dependency-submission

It seems the pattern *-dependency-submission is more common for such Github actions that push dependency snapshot to the Github Dependency Submission API:

https://github.com/actions/go-dependency-submission
https://github.com/mikepenz/gradle-dependency-submission
https://github.com/marketplace/actions/elm-dependency-submission
https://github.com/marketplace/actions/sbom-submission-action

@ckipp01 @julienrf @sjrd any opinion on this?

Probably sbt-dependency-submission, no?

“dependency-submission” is not very explicit to me, but if that’s the de facto standard, let’s use that!

@adpi2 @julienrf maybe scala-github-dependency-submission? The format is specific to github, right?
Also flagging for scala-cli folks - cc @romanowski @alexarchambault

Thanks @kubukoz for the suggestion. We also thought of sbt-dependency-submission-action, to state clearly that this is a Github action.
But ***-dependency-submission has become a standard in other ecosystems (go, gradle, elm, sbom). So I will stick to it. That's not really self-explanatory but a quick look at the Readme should cFor those who don't know, larify that this is a Github action and nothing more.

Also flagging for scala-cli folks - cc @romanowski @alexarchambault

Here is another thread where we discuss the possibility of a build-tool agnostic version of this action using BSP. It is not yet possible to extract a dependency graph using BSP but we could add this feature. It's not a niche feature, as it could be reused in many languages, not only scala, and in other BSP servers: would be cool to view the dependency graph in Metals for instance.


Add 3 pbjs callbacks to the adapter

I did a few tests and I'm a little confused about the ask...
Before I implement any of the required functions (onBidWon(), onSetTargeting(), onTimeout()):

pbjs.getAllPrebidWinningBids() already returns sharethrough winning bids, tied to the sharethrough bidder code
pbjs.getAdServerTargeting() does return an empty object for each placement
...making me confused about the ticket description that states that some other bidders would show up as winners. So I'm not sure if I'm just missing something.

I have been able to confirm that adding an empty onSetTargeting() function changes the result of pbjs.getAdServerTargeting() returning some targeting data instead of empty objects. I cannot tell if the other 2 (onBidWon(),  onTimeout()) bring anything, I even haven't been able to see onBidWon() being called even though sharethrough had winning bids. I added them to the PR nonetheless.
https://www.pivotaltracker.com/story/show/165641393

@maphe apologies for the confusion. Looking at the story, support and I misunderstood the behavior of pbjs.getAllPrebidWinningBids -- this function will only return winning bids that did not render on the page. There is a related function pbjs.getAllWinningBids that returns all winning bids that did render. Given this, we must have misinterpreted seeing STR ads render on the page but not appearing in the return value for pbjs.getAllPrebidWinningBids as an error.
However, the return value for pbjs.getAdServerTargeting previously did not populate with STR data. I think your implementation of onSetTargeting has solved this. I don't think onBidWon and onTimeout are being invoked, but I don't see the harm in including them -- if anything, the empty functions can be placeholders for future implementations if we decide we need them.
I will test your branch locally and review by my EOD.

@maphe apologies for the confusion. Looking at the story, support and I misunderstood the behavior of pbjs.getAllPrebidWinningBids -- this function will only return winning bids that did not render on the page. There is a related function pbjs.getAllWinningBids that returns all winning bids that did render. Given this, we must have misinterpreted seeing STR ads render on the page but not appearing in the return value for pbjs.getAllPrebidWinningBids as an error.
However, the return value for pbjs.getAdServerTargeting previously did not populate with STR data. I think your implementation of onSetTargeting has solved this. I don't think onBidWon and onTimeout are being invoked, but I don't see the harm in including them -- if anything, the empty functions can be placeholders for future implementations if we decide we need them.
I will test your branch locally and review by my EOD.

Tested locally, but wasn't able to get pbjs.getAdServerTargeting to return a populated object. Going to test again on Monday.
Also, here are the Prebid docs explaining pbjs.getAllWinningBids and pbjs.getAllPrebidWinningBids: http://prebid.org/dev-docs/publisher-api-reference.html#module_pbjs.getAllWinningBids


cant follow chain tutorial in releases since 9.5

Hi @mfused just following up! Are you still experiencing an issue with this tutorial?

All good, thanx.
Sent from my iPad

On 11 Nov 2019, at 18:37, Ellen Nickles<EMAIL_ADDRESS>wrote:
Hi @mfused just following up! Are you still experiencing an issue with this tutorial?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


Unable to register shipyard-agent

Hi,
I'm trying to register shipyard agent and I get the following error:
"Error parsing JSON from Shipyard register: json: cannot unmarshal number into Go value of type main.AgentData"
root@shipyard-server:~# shipyard-agent -url http://<IP_ADDRESS>:8080 -register
2015/02/15 13:47:20 Using <IP_ADDRESS> for the Docker Host IP for Shipyard
2015/02/15 13:47:20 If this is not correct or you want to use a different IP, please update the host in Shipyard
2015/02/15 13:47:20 Registering at http://<IP_ADDRESS>:8080
2015/02/15 13:47:21 Error parsing JSON from Shipyard register: json: cannot unmarshal number into Go value of type main.AgentData
My Shipyard version is:
shipyard cli> shipyard info
Controller Version: 2.0.8
Cpus: 8.00
Memory: 16384.00 MB
Containers: 2
Images: 2
Engines: 2
Reserved Cpus: 25.00% (2.00)
Reserved Memory: 6.25% (1024.00 MB)
root@shipyard-server:~#  docker version
Client version: 1.4.1
Client API version: 1.16
Go version (client): go1.3.3
Git commit (client): 5bc2ff8
OS/Arch (client): linux/amd64
Server version: 1.4.1
Server API version: 1.16
Go version (server): go1.3.3
Git commit (server): 5bc2ff8
root@shipyard-server:~# shipyard-agent --version
0.3.2
Have you had the same issue?
Thanks

Sorry, as I see the agent is no used in Shipper v2 .
https://github.com/shipyard/shipyard-agent#docker


Unable to convert Lyon or Rotterdam CityGML models to OBJ (possibly others too)

I've been trying to convert the CityGML models listed by yourselves on the CityGML wiki but have had no luck to date. I assumed it was because they are using version 1.0 of CityGML, but even when changing the schema to 2.0 the converter crashes.
Here's an example crash (the others fail at the same point when changed to a 2.0 schema):
CityGML2OBJ. Searching for CityGML files...
1-10-STADSDRIEHOEK
	There are 848 cityObject(s) in this CityGML file.
	Analysing buildings and extracting the geometry...
Traceback (most recent call last):
  File "CityGML2OBJs.py", line 378, in <module>
    poly_to_obj(poly, 'All')
  File "CityGML2OBJs.py", line 149, in poly_to_obj
    t = polygon3dmodule.triangulation(epoints, irings)
  File "./CityGML2OBJs/polygon3dmodule.py", line 455, in triangulation
    tris = t['triangles']
KeyError: 'triangles'

I don't know much about CityGML but the geometry seems ok and the fact that this occurs for all the real cities I've tried makes me think that it's either some part of the 1.0 schema that I've missed, or there's an issue converting these files at the moment. For the record, the converter works fine for the random CityGML data generator you created.
Can you enlighten me on whether this is indeed an issue because of 1.0 (and what specifically might be causing it), or whether there is something else going wrong? I'd be happy to try and fix it but I don't know what I'm looking for right now (I'm new to CityGML).

Thanks for this report and for trying the code. I intend to work on improving the converter to support CityGML 1.0, and also to improve the detection of the invalid geometries to avoid such crashes. The error that you have experienced has likely been caused by invalid geometry in the dataset, which is not surprising considering that public datasets are usually full of invalid geometries. The built-in geometry validator is a basic one, and in some public datasets I have encountered nastier errors that cause the embedded triangulator to crash (sometimes also with a C error that cannot be excepted in Python). However, that's not an excuse not to improve this converter to detect them better and skip them. I will come back to you in a few weeks.

Thanks for the update Filip! This is a great tool and it will be very useful for myself and the people who use ViziCities and other services that I work on that utilise CityGML models.
If it helps, the same CityGML models that fail converting using CityGML2OBJs actually import into 3DCityDB ok and can be exported out as collada models. Perhaps 3DCityDB fixes broken geometry as I noticed it had detected polygons without an endpoint and used the start point to create a new one. I suppose in this case, it's more useful to fix the geometry if we can than it is to just detect and ignore it (especially if the errors are common and known).

Same issue here with data from http://suche.transparenz.hamburg.de/dataset/3d-stadtmodell-hamburg  using a re-written header.
Here is an example file (with the header for 2.0, hopefully correct): http://pastebin.com/FPMpgrga (https://www.govdata.de/dl-de/by-2-0)

Noted, thanks for the report. It seems that the demand for solving this shortcoming is increasing, so I'll investigate and work on it as soon as I'll have time.

Hello,
Sorry for the long break, busy times. I've worked on solving the errors which you have encountered. Probably you've already managed to convert the data with some other utility (I also know that Rob has been developing his tool). If you are interested, I've updated the code, and while it still has some hiccups and it returns errors in some files, many data sets that previously didn't work are now supported. The code now works with CityGML 1.0. I tried it with Rotterdam, Lyon, and Hamburg (see the picture below).
Let me know of data sets that do not work, so I'll take a look.


the dssnet.py

I don't understand what's the means about this:
extra = {'dss': .....}
Could you tell me what's this and how to do with it.Thank you very much.

I don't understand what's the means about this:
extra = {'dss': .....}
Could you tell me what's this and how to do with it.Thank you very much.

I don't understand the '[8, 16, 32, 64]' and '[4, 8, 16, 32]', could you tell me why they are different?

I don't understand what's the means about this:
extra = {'dss': .....}
Could you tell me what's this and how to do with it.Thank you very much.

I got it


Change login endpoint from GET to POST

Overview of the problem

Spark module
Description

Steps to Reproduce

Expected behavior

Actual behavior

done by @rootux


Random posts are not being send out for Bluesky

The random posts were not sent out to Bluesky. Could be related to #129

Implemented with https://github.com/jguadagno/jjgnet-broadcast/commit/ce55e51095d9174378a3d4dfc0caf8515ba794a0


move js to js file

Same javascript is reused on all pages so a separate Js file would make sense.

fixed in ed08dc1 (bad wip) and eecb3d1 (bugs fixed and reformatted too).


Add Result.combine

The function corresponds to http://package.elm-lang.org/packages/Apanatshka/elm-signal-extra/5.4.1/Signal-Extra#combine (or to http://hackage.haskell.org/package/base-<IP_ADDRESS>/docs/Data-Traversable.html#v:sequenceA).
An example use is here.

There's a PR for adding sequence to Maybe. Seems like combine versus sequence convention needs to be resolved: Would you mind commenting on https://github.com/circuithub/elm-maybe-extra/pull/5 ?

I've commented over there why I think combine would be the better name in the case of Result. In particular in the case of only Ok inputs the "effective" outcome is not sensitive to the order of inputs coming in, so there is no concept of "sequentiality".

Evan's blessing is good enough for me.
Published to 1.3.0


Comments on event page should have the option of delete and report

Right now registered user can just add comments to any event but cannot delete it and the event organiser should also have authority to do that and other registered users should can report the comment too which notifies event organiser so he/she could delete it .

I think it's level 2 issue

Please assign this to me


Avoid Benchmarking Allocs

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences

[trickle] No significant performance differences

[microbenchmarks] No significant performance differences


shipyard-ready-registry-v2 ,Can not add registry2.

When I add registry2,
the registry response :
level=warning msg="error authorizing context: authorization token required" go.version=go1.5.3 http.request.host=registry.com http.request.id=8faa30ab-0562-4fb0-abb7-78220d34a32d http.request.method=GET http.request.remoteaddr=<IP_ADDRESS> http.request.uri="/v2/" http.request.useragent="Go-http-client/1.1" instance.id=1570ed8c-8495-49ec-be24-526b598e3e1e version=v2.3.1
<IP_ADDRESS> - - [23/Aug/2016:10:15:59 +0800] "GET /v2/ HTTP/1.0" 401 87 "" "Go-http-client/1.1"

@yeruisen It seems that you are trying to set up an registry and you are not able to log in to it. Please try to check it using docker login [SERVER].
The --insecure-registry needs to be set in the /etc/default docker. In case you have ubuntu version 16.04 you need to configure it for systemd.
Keep in mind that is not possible to use insecure registry with basic authentication.

@AndreeaDora
Yes, I agree with you. but it didn't work.
because my registry2.0 was controlled by Portus. So I don't know what to do.

@yeruisen It sounds that it is a problem with the registry deployed in Portus and not with ILM. I suggest you try to make the registry work using docker login [SERVER], and then add it to the shipyard registries.

@yeruisen in the host where you have deployed eedevops/shipyard (ILM) check the docker daemon configuration. I suggest you take a look at the following docker docs. Basically, you need to configure your host's docker daemon so that it overrides the requirement from the client to verify TLS. This is done with the flag --insecure-registry=[] (from the documentation before).
Another option, if you are using an ubuntu host, you may also configure the daemon in the /etc/default/docker file by adding the above flag to the DOCKER_OPTS environment variable. After that you need to restart your docker daemon by restarting the service (e.g. sudo service docker restart.
I hope that helps!

Referencing https://github.com/eedevops/shipyard/issues/77 which is an open, known issue. @soninob @edagan you might want to come up with an automated way to send this configuration to the docker daemon upon registry addition.

@AndreeaDora
@rqc
Yes， the problem  due to the registry deployed in Portus and not ILM.  So I plan to solve this problem from Portus.

Closing, @yeruisen if there is still a need for this issue, please reopen.


Declared but undefined copy assignment operator for iox::expected

Required information
Operating system:
Ubuntu 20.04.6 LTS
Compiler version:
Clang 11
Eclipse iceoryx version:
master
Observed result or behaviour:
iox::expected has a copy and a move assignment operator defined here:
https://github.com/eclipse-iceoryx/iceoryx/blob/4739ffdc35c611197ab7bf2d9aa2db8e7cbd11df/iceoryx_hoofs/vocabulary/include/iox/expected.hpp#L166-L174
however, only the move assignment operator is defined
https://github.com/eclipse-iceoryx/iceoryx/blob/4739ffdc35c611197ab7bf2d9aa2db8e7cbd11df/iceoryx_hoofs/vocabulary/include/iox/detail/expected.inl#L111-L121
As a result, a linker error is generated when attempting to run the following snippet ...
TEST_CASE("Test")
{
  iox::expected<void, int> a = iox::ok();
  iox::expected<void, int> b = iox::err(1);
  a = b;
}

ld.lld: error: undefined symbol: iox::expected<void, int>::operator=(iox::expected<void, int> const&)
>>> referenced by estimator_lib_test.cc
>>>               <REDACTED PATH>test.o:(C_A_T_C_H_T_E_S_T_2())
clang-11: error: linker command failed with exit code 1 (use -v to see invocation)

Expected result or behaviour:
No compiler error
Conditions where it occurred / Performed steps:
See above

@pbarone-latai Whoopsie. How did that happen.
Thanks for the finding, I will take care of this.


[Bug][Manager] Unknown method isNoneBlank

What happened

What you expected to happen
no error
How to reproduce
run manager
Environment
No response
InLong version
master
InLong Component
InLong Manager
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@woofyzhao, let me see it


[world rebuild][vcpkg scripts] Test, fix, extend vcpkg_execute_required_process

Fixes OUTPUT_VARIABLE, ERROR_VARIABLE. vcpkg always wants logfiles. execute_process doesn't send stdout/stderr to files and variables at the same time. So simultaneous output has to be handled in vcpkg_execute_required_process.
At this occasion, port the arguments for stripping trailing whitespace.
tensorflow-common implicitly relied on the broken behavior. I chose the minimal fix: drop the pointless calls, just set the empty value.

tensorflow, tensorflow-cc:
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/tensorflow/runtime/archive/6ca793b5d862ef6c50f242d77a811f06cce9b60a.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
...
WARNING: Download from https://storage.googleapis.com/mirror.tensorflow.org/github.com/llvm/llvm-project/archive/0538e5431afdb1fa05bdcedf70ee502ccfcd112a.tar.gz failed: class java.io.FileNotFoundException GET returned 404 Not Found
...
ERROR: An error occurred during the fetch of repository 'local_config_python':
   Traceback (most recent call last):
	File "/mnt/vcpkg-ci/b/tensorflow/x64-linux-dbg/third_party/py/python_configure.bzl", line 271, column 40, in _python_autoconf_impl
		_create_local_python_repository(repository_ctx)
	File "/mnt/vcpkg-ci/b/tensorflow/x64-linux-dbg/third_party/py/python_configure.bzl", line 214, column 22, in _create_local_python_repository
		_check_python_lib(repository_ctx, python_lib)
	File "/mnt/vcpkg-ci/b/tensorflow/x64-linux-dbg/third_party/py/python_configure.bzl", line 138, column 25, in _check_python_lib
		auto_config_fail("Invalid python library path: %s" % python_lib)
	File "/mnt/vcpkg-ci/b/tensorflow/x64-linux-dbg/third_party/remote_config/common.bzl", line 12, column 9, in auto_config_fail
		fail("%sConfiguration Error:%s %s\n" % (red, no_color, msg))
Error in fail: Configuration Error: Invalid python library path: /home/cloudtest/.local/lib/python3.10/site-packages
ERROR: /mnt/vcpkg-ci/b/tensorflow/x64-linux-dbg/WORKSPACE:15:14: fetching python_configure rule //external:local_config_python: Traceback (most recent call last):
	File "/mnt/vcpkg-ci/b/tensorflow/x64-linux-dbg/third_party/py/python_configure.bzl", line 271, column 40, in _python_autoconf_impl
		_create_local_python_repository(repository_ctx)
	File "/mnt/vcpkg-ci/b/tensorflow/x64-linux-dbg/third_party/py/python_configure.bzl", line 214, column 22, in _create_local_python_repository
		_check_python_lib(repository_ctx, python_lib)
	File "/mnt/vcpkg-ci/b/tensorflow/x64-linux-dbg/third_party/py/python_configure.bzl", line 138, column 25, in _check_python_lib
		auto_config_fail("Invalid python library path: %s" % python_lib)
	File "/mnt/vcpkg-ci/b/tensorflow/x64-linux-dbg/third_party/remote_config/common.bzl", line 12, column 9, in auto_config_fail
		fail("%sConfiguration Error:%s %s\n" % (red, no_color, msg))
Error in fail: Configuration Error: Invalid python library path: /home/cloudtest/.local/lib/python3.10/site-packages

Maybe from tensorflow-common:
	vcpkg_execute_required_process(COMMAND ${PYTHON3} -c "import site; print(site.getusersitepackages())" WORKING_DIRECTORY ${CURRENT_BUILDTREES_DIR} LOGNAME prerequisites-pypath-${TARGET_TRIPLET} OUTPUT_VARIABLE PYTHON_LIB_PATH)

now actually setting PYTHON_LIB_PATH.

execute-required-process feature passed with following triplet:
x64-windows

Tagging team review because it's technically a backwards incompatible change to scripts but I think we should take it anyway.

@AugP
@ras0219-msft
@data-queue
@JavierMatosD
and I discussed this today.
@AugP This means it would break people who upgrade vcpkg but don't update their baseline?
@ras0219-msft Yes that is the concern. But we didn't document this as being broken like that. It's borderline but I think it's OK.
@data-queue Could it be made into a script port?
@BillyONeal I think execute_required_process is too 'fundamental' to do that.
@AugP will mention this in the blog post for July as a known breaking change.
I'll push the merge button just before Friday's build at 9pm pacific.

Thanks for the fix!


Taskbar Icon not showing after Windows Update

After updating to the latest windows feature update 1909 vscode taskbar icon turned into a white file icon. The insiders build has no issues.

VSCode Version: 1.41.1 (user setup)
OS Version: Windows_NT x64 10.0.18363

Things I have tried:

Reinstalling vscode
Clearing icon cache

Does this issue occur when all extensions are disabled?: Yes
Screenshot:

The bug was fixed after some vscode launches. We can close this issue 😄


feat(cdc): share a changelog stream for multiple cdc tables

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.
What's changed and what's your intention?
Part of https://github.com/risingwavelabs/risingwave/issues/11079, related: https://github.com/risingwavelabs/risingwave/issues/11545
Interface

create a CDC Source job

create source mysql_mydb with (
 connector = 'mysql-cdc',
 hostname = '<IP_ADDRESS>',
 port = '8306',
 username = 'root',
 password = '123456',
 database.name = 'mydb',
 server.id = 5888
);

The parallelism is set to 1
The format is fixed to FORMAT PLAIN ENCODE JSON so it can be eliminated.

create CDC Tables based on the above source

CREATE TABLE t1_rw (
    v1 int,
    v2 int,
    PRIMARY KEY(v1)
) FROM mysql_mydb TABLE 'mydb.t1';

CREATE TABLE t3_rw (
  v1 INTEGER,
  v2 timestamptz,
  PRIMARY KEY (v1)
) FROM mysql_mydb TABLE 'mydb.t3';

The parallelism of these table jobs is set to 1
The table name behind the second TABLE keyword should be qualified with the database name in the MySQL.

Implementation

Add a new Source type streaming job to support the cdc source job
The output schema of the cdc source job is fixed to (payload jsonb, _rw_offset varchar, _rw_table_name varchar, _row_id ).
The dispatcher of the cdc source job will dispatch cdc event chunks to downstream table jobs based on the _rw_table_name column
The CdcBackfillExecutor will transform the upstream chunk to the specific schema of a table job (e.g. (v1 int, v2 int)) before doing backfill
Right now the backfill state doesn't persist in this case, so it will trigger the backfill again upon recovery
Here is a figure to demonstrate the workflow:

Checklist

[x] I have written necessary rustdoc comments
[x] I have added necessary unit tests and integration tests
[ ] I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features #7934).
[ ] My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
[x] All checks passed in ./risedev check (or alias, ./risedev c)
[ ] My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

[ ] My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

[ ] My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note
If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

@yezizp2012 Could you please also help review the meta and catalog part of this PR? I would really appreciate it.

@yezizp2012 Could you please also help review the meta and catalog part of this PR? I would really appreciate it.

Yes sure. ❤  I'll take a look later.


Feature activate / deactivate ?

Hello, I love this app so much, but since I use bluetooth keyboard and trackpad, it, obviously, prevents my MacBook to get off out sleep with it. Is there a way to exclude some bluetooth devices from Bluesnoow or have a menu-bar option to deactivate / reactivate blue snooze ?

+1
Disconnecting from specific devices would be favored over fully disabling bluetooth for me.

Sorry not looking to add per-device toggling - it'd be a complete re-write. Feel free to fork & experiment as you like ✌
https://github.com/odlp/bluesnooze#can-you-add-support-for-selectively-disconnecting-certain-devices


MIAD-267 start plan

Codecov Report
Attention: Patch coverage is 98.93617% with 1 line in your changes missing coverage. Please review.

Project coverage is 90.73%. Comparing base (f77e0fa) to head (18bbc10).

Files with missing lines
Patch %
Lines

...ital/hmpps/hmppsalertsapi/service/PlanBulkAlert.kt
98.46%
0 Missing and 1 partial :warning:

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #255      +/-   ##
============================================
+ Coverage     90.35%   90.73%   +0.38%
- Complexity      513      522       +9
============================================
  Files            92       92
  Lines          1783     1868      +85
  Branches        119      123       +4
============================================
+ Hits           1611     1695      +84
  Misses          126      126
- Partials         46       47       +1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[new feature] support run pluginin with local plugin

support run pluginin with local plugin

added in #14


Add handling for non-space delimiters for equal predicate. Fixes #30.

I would appreciate any feedback here. I don't know that this would be the cleanest implementation, but testing locally, it worked for me.

Is this meant to fix this issue - https://github.com/NodeSquarespace/node-squarespace-jsont/issues/30 ?

Yes, it is. Sorry, don't know why I put 100 in the pull request and branch names.


Reward ads do not show

Hi,
We are experiencing some weird behavior regarding the reward ads. The problems started to get worse after the latest update 0.3.1 . When running with testMode=true in the emulator we can see that reward ads are loaded but we cannot get them to show.
In production we need to restart the app between successfully shown reward ads to show them again.
We used to have problems with this only on iOS but now it seems to be equally broken.

Closing this since it started working for us and we cannot seem to reproduce it anymore.