example to implement CustomAttributes under Cognito User Pool

Hi all
Any ideia how to add some custom attributes to a particular auth.userPoolId / auth.cognitoIdentityPoolId?
example customType, customCLass, customXField
I look around aws cognito but I could understand how to be implemented under sst.dev.
thanks for your sharing

We are transition this repo to https://github.com/sst/v2 and are closing this issue for now. If it is still relevant please reopen it there - sorry for the trouble


What‘s the meaning of "summary_label" in Data file?

Thanks for your excellent work! It's highly appreciated. I have two questions regarding the code:
Q1: I noticed that the meaning of "summary_label" was forgotten to be mentioned in the readme. Could you tell me about that?
Q2: Could you kindly offer more information about "rel_sent_positions" (List of source sentence indexes)? Was it annotated by a human? Does it align with the "label" in "annotations" (which I observed it does not)? I'm a bit confused about this and would greatly appreciate some clarification.
Thank you for your time！

Hi @sswingHUA,
Thank you for your interest and for the questions! I'm so sorry for the delayed response. Somehow, I completely overlooked this issue.

Q1: I noticed that the meaning of "summary_label" was forgotten to be mentioned in the readme. Could you tell me about that?

It's reconstructibility label. More specifically, it's a list of manual judgments. Added the following information to README.md

summary_label: List[int]: Reconstructibility label (1: Yes, 0: No) (whether the system/reference summary can be reconstructed from the source document)

Q2: Could you kindly offer more information about "rel_sent_positions" (List of source sentence indexes)? Was it annotated by a human? Does it align with the "label" in "annotations" (which I observed it does not)? I'm a bit confused about this and would greatly appreciate some clarification.

Yes, your understanding is correct. It can be reconstructed from lists of labels in annotations. However, I wanted to keep this field to handle the information easily for convenience.
I hope the information is still helpful for you. Please let me know if you have any questions!


#114 | Ziyang | Add .devcontainer folder

Closes #114.

Codecov Report

Merging #115 (08049ba) into main (90fb491) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #115   +/-   ##
=======================================
  Coverage   97.65%   97.65%
=======================================
  Files           5        5
  Lines         299      299
=======================================
  Hits          292      292
  Misses          7        7

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 90fb491...08049ba. Read the comment docs.


New: Check whether someone has been rescued !

Provide a feature to check on people whether they have been rescued or not !
Kind of people register books.
It will help to avoid duplicate request.

And if possible add status to the request, whether its already been taken care of.
eg: Resolved, Under Process, Yet to taken care of

Feature available https://keralarescue.in/find_people/
How the user can post the rescued people details.


Support for CUDA capability sm_90

Hello,
I am training the equivariant transformer and running dynamics using it on some Nvidia H100 GPUs. Overall, the workflow is going fine. However, I do get the following warning at the start of every training session:
/home/frankhu/mambaforge/envs/torchmd-net/lib/python3.10/site-packages/torch/cuda/__init__.py:173: UserWarning:
NVIDIA H100 PCIe with CUDA capability sm_90 is not compatible with the current PyTorch installation.
The current PyTorch install supports CUDA capabilities sm_35 sm_50 sm_60 sm_61 sm_70 sm_75 sm_80 sm_86 compute_86.
If you want to use the NVIDIA H100 PCIe GPU with PyTorch, please check the instructions at https://pytorch.org/get-started/locally/

  warnings.warn(incompatible_device_warn.format(device_name, capability, " ".join(arch_list), device_name))

The CUDA version I am using currently is 12.1, and from the PyTorch website, CUDA 12.1 is only supported with the nightly version of PyTorch, not the stable 2.0.* versions indicated in the environment.yml file. Has torchmd-net been tested with this newer version of PyTorch that supports CUDA 12.1 capability? If so, would it be safe to upgrade to the nightly version of PyTorch without breaking the code?
Thank you!

Most functionality I have successfully tested with pytorch nightly, i.e most tests run and all that run pass.
Depending on what exactly you need though you might run into dependency issues, since releases for some dependencies are not prepared to live outside conda-forge (e.g NNPOps, but you can install it from source and it is compatible with CUDA 12/torch-nightly AFAIK).
I have gotten away with running most tests by installing all dependencies that allow so with pip and compiling NNPOps manually.

This environment works for me at the moment of writing:
name: torchmd-net
channels:
  - nvidia
  - pytorch-nightly
  - conda-forge
dependencies:
  - python<=3.11
  - pip
  - cmake
  - pytorch-cuda=12.1
  - cuda-toolkit=12.1
  - cuda-compiler=12.1
  - gxx<12
  - pytorch
  - torchvision
  - torchaudio
  - ninja
  - pip:
       - torch-cluster==1.6.1
       - torch-geometric==2.3.1
       - torch-scatter==2.1.1
       - torch-sparse==0.6.17
       - pytorch-lightning==1.6.3
       - torchmetrics==0.11.4
       - tqdm
       - pytest
       - psutil
       - matplotlib
       - h5py
       - torchani==2.2.3

$ mamba create -f environment.yml

This contains everything required to compile NNPOps too:
$ mamba activate torchmd-net
$ git clone https://github.com/openmm/NNPOps
$ cd NNPOps
$ mkdir build && cd build
$ sed 's+14+17+g' ../CMakeLists.txt # Pytorch nightly requires C++17
$ Torch_DIR=$(python -c 'import torch;print(torch.utils.cmake_prefix_path)')  cmake -DCMAKE_BUILD_TYPE=Release ..
$ make -j5 all install

After this you can go back to torchmd-net/tests and try:
$ pytest test*py

All tests pass on our systems

Torchmd-net and pytorch are now built for CUDA 12 in conda forge and include sm_90. Closing this.


Question: How to connect by javascript to the server via sockets

Hello, I am trying to make a client server connection via sockets, the server being in reatchphp with the following code.
`<?php
require 'vendor/autoload.php';
$colours = ['red', 'green', 'yellow', 'blue', 'purple', 'cyan'];
$loop = React\EventLoop\Factory::create();
$socket = new React\Socket\Server($loop);
// This event triggers every time a new connection comes in
$socket->on('connection', function ($conn) use ($colours) {
$colour = array_pop($colours); // Only doing this as an example, you will run out of colours.
// Event listener for incoming data
$conn->on('data', function ($data, $conn) use ($colour) {

    // Write data back to the connection

    $conn->write("a");
    $address = $conn->getRemoteAddress();
    echo 'Connection with ' . $address . PHP_EOL;
    // Echo the data into our terminal window
    echo (new \Malenki\Ansi($data))->fg($colour);
});

});
// Listen on port 1337
$socket->listen(1337);
$loop->run();
`
And the client in javascript with the following code
`var conn = new WebSocket('ws://localhost:1337');
conn.onopen = function(e) {
console.log("Connection established!");
};
conn.onmessage = function(e) {
console.log(e.data);
};`
The question is that I managed to connect listening from the console with telnet but with javascript I could not give me the following error
Firefox can not establish a connection to the server at ws: // localhost: 1337 /.

It looks like you're running a plaintext TCP/IP socket server and are trying to use the WebSocket protocol to connect to this server?
You can use any plaintext TCP/IP client to connect to your server, such as telnet or any other TCP/IP library.
If you want to use a WebSocket client, such as the one provided by your browser, you will have to use a WebSocket server. Ratchet is a WebSocket server that builds on top of this project.
I hope this helps :+1:

Hi, I ended up using ratchet and found the solution to my problem, thanks :)


look into reference

I need to look into this.
I think I know what the issue is.

@manulera  somewhere in your code for gene structure updates, when a gene structure changes, it is assumed that any reference added during that period describes the feature coordinates. This is likely trui in 99% of cases, but we also added globally a db_xref:
/db_xref="SPD:19/19F02" which actually provides a link to the orfeome collection
which sometimes gets pulled in.
Could these references be "blocked" at some point?
@kimrutherford

Could these references be "blocked" at some point?

Would it be OK just remove all the db_xrefs that aren't PubMed IDs?

Hi both, sorry about the late reply. Yes, that's a possibility, otherwise we could make a list of refs we want to exclude from the list in a separate text file and have the script remove those?
I can implement the change.

PMID:16823372 SPD:19/19F02
is the only one I am aware of. Most of the. others. should be correct.

Hi @ValWood now those two references are excluded if they are picked up from the changes in contig files (this commit: 87605c9fd7aba0b1cdee9c4ff944fb9e86c21aa4). However, in the manual changelog (the one you used to maintain manually), the reference PMID:16823372 is included several times (list below). Should I remove it from there as well?
systematic_id	comments	reference	date
SPAC3H1.04c             PMID:16823372   2010-10-21
SPCC1442.04c    frameshifted    PMID:16823372   2009-02-02
SPAC1F8.07c     frameshifted    PMID:16823372   2009-02-02
SPAC22F3.11c    frameshifted    PMID:16823372   2009-02-02
SPBC1A4.06c     frameshifted; C term exon changed from 1987076..1987675 to 1987044..1987675     PMID:16823372   2009-02-02
SPBC29A3.08     frameshifted; truncated to 2048336..2049892, 2049894..2049896   PMID:16823372   2009-02-02
SPBC13E7.01     frameshifted    PMID:16823372   2009-02-02
SPBC23G7.06c    frameshifted; now a single exon PMID:16823372   2009-02-02
SPBC14C8.09c    merged with SPBC14C8.08c; frameshifted  PMID:16823372   2009-02-02

Also, I noticed that SPD:19/19F02 is only associated with SPCC1442.04c. Did you mean to get rid of all the refs that started with SPD*?

The SPD:19/19F02 type links need to stay. Those are used  to create the orfeome links
in the external resources section of the gene page https://www2.riken.jp/SPD/19/19F02.html
(usually there are images associated but not for this one for some reason).
They predate PomBAse, but we never migrated over to the current system. @kimrutherford  should we do that?

Hi @ValWood I am not sure I follow here. From your comment "@manulera somewhere in your code for gene [...]" it seemed that you wanted those references not to appear in the gene structure history. What references did you want not to appear?

AH sorry, yes they should not appear in the gene structure history.
When you  asked:
Also, I noticed that SPD:19/19F02 is only associated with SPCC1442.04c. Did you mean to get rid of all the refs that started with SPD*?
I thought you were asking that we no longer needed them in the contig file at all
PMID:16823372 should not be in the manual log either, I have no idea which paper I meant   here...

Yes!

Should be fixed now


M68000: Overriding signature doesn't work

So, this problem makes my heart bleeding...
ROM: http://www.technopop.net/images/zerotole.zip
At the address 0xc5b38 there is a function that uses stack to pass arguments into the FUN_000c5d2a:

Then, to get passed arguments, M68k calls link a6, 0x0, so the A6 register becomes equal to the SP where arguments where stored:

Problem:
000c5d36  70 ff                  moveq        #-0x1,D0
000c5d38  2f 00                  move.l       D0,-(SP)=>local_8
000c5d3a  4e ba ff c2            jsr          FUN_000c5cfe

In disassembly it looks ok, and decompiler also shows -1 passed as function's argument. But, if we go into FUN_000c5cfe function, we will see that this function doesn't accept any argument:

Ok, then I'm trying to use Override signature feature:

But after going into that function again, I'm taking the same result: FUN_000c5cfe doesn't accept any argument.
So, how to specify that argument? How to tell Ghidra to use it without specifying it for every possible function?
Seems, that the next FUN_000c5c9c also uses this argument.

A workaround would be to edit the signature with the option given from the list.
If it isn't working, maybe it should be removed and people should be enforced to click "Edit function signature" instead. If it is supposed to work there should be a key-binding to it.

Override signature is used only to override a signature such as printf, generally varags, where there are different number of parameters throughout the program and the arguments aren't detected correctly.
@nihilus is correct you should be using Edit Function signature to specify it takes a parameter, then it will show up that way everywhere it is used.
Also the fact that the function has a void suggests that one of the called functions in Fun_c5fce takes a parameter.
You can go into the leaf-functions in the decompiler and commit params/return.  There is also a paramID analyzer you can turn on, but that can also spread problems if there are issues in the code you haven't taken care of.

Problem is not editing function signature manually, but why Ghidra knows that function accepts one argument, and doesn't know that at the same time.

And any one found an explanation for this ?


Slide disappear when using loop and centeredSlides

Hi,
I'm having a problem when using swiper with centeredSlides and loop. I have a slider with 3 slides. I click the next button twice to go to the third slide and then click the previous button to go back to the second slide, and the previous slide (the first one) from the actual active slide disappears, is like the loop brokes for some reason and the duplicated slide is not visible since in the html the duplicated slides exists
Here is my code:
mainSliderSwiper = new Swiper('.main-slider .swiper-container',{
      slidesPerView: 'auto',
      centeredSlides: true,
      speed: 600,
      loop: true,
      loopedSlides: 2,
      pagination: '.pagination',
      paginationClickable: true,
      cssWidthAndHeight: true,
      initialSlide: 0
    });
    $('.main-slider .swiper-controls .swiper-prev-area').on('click',function(){
      mainSliderSwiper.swipePrev();
    });
    $('.main-slider .swiper-controls .swiper-next-area').on('click',function(){
      mainSliderSwiper.swipeNext();
    });
  }

The captures from firbug of the html:
Initial State

After clicking next once (second slide centered):

After clicking next twice (third slide centered):

After clicking previous once to return to second slide ( second slide centered  and first slide disappears):

thank you :+1:


Updating CI files

This commit updates all CI scripts to the latest version

@dignifiedquire @diasdavid crypto.createHash is not a function is now breaking all the CIs, any ideas of what's going on?

@VictorBjelkholm let's merge this one and open a issue with that bug. (multihashing needs some love)


feat: error if parameter name in impurity reason is invalid

Closes #741
Summary of Changes
A parameterName in an ImpurityReason must be the name of a parameter in the annotated function. This PR adds validation for this.

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

npm package (@latest dist-tag)
npm package (@latest dist-tag)
v0.4.0
GitHub release

Your semantic-release bot :package::rocket:


Mac Input just does not work (mostly for modern distributions)

I'm combining these issues into one because it's becoming a significant problem and there needs to be a single place to refer to for all of the individual cases.
#1241 - input not working solved by adding the Etterna exec (not .app) to Input Monitoring in settings
#1047 - input not working macos 11.4, no response
#829 - right clicking never works

See: https://gist.github.com/bluebandit21/d34d7b0b4f9137c34c167e607db63c03 for the most complete compilation of things to try to fix "Input not working due to lack of permissions" suite of problems.
Unfortunately this is right in the intersection of horribly annoying things to work around -- problems relating to us using a horribly old (and honestly horribly insecure! We basically get to act as a system-wide keylogger!!) API for input and problems relating to us being an unsigned/unnotarized app causing us to take an unpleasant alternate path through LaunchServices...


Issue with ROS noetic

build.make.005.log
Attaching the build log file. The create_random_forest.cpp file generates a boost library error. There are a lot of issues with noetic, boost, and Ubuntu 20.04. Is there a way to remove these dependencies?

Hi @Mahathi1992!
I don't have ROS noetic/Ubuntu 20.04 right now, but could you try to git pull the last commit of this repo, then do the wstool merge and wstool update commands as explained in the Readme, and then try to compile again?
I changed some things in the CMakelist.txt of acl_gazebo
Let me know if this solves the issue!

Hi @jtorde,
I tried your fix and some more steps but Ubuntu 20.04 is not budging. For now I have reverted back to 18.04 and ROS melodic. FASTER should work with this combination right?

Hi @Mahathi1992,
Yes, Ubuntu 18.04/ROS melodic works


Android Support?

It would be awesome if it has android support.

This should already work for Android?

Its not working on Android, any idea why?

@KalebPortillo there is no platform specific code afaik. Can you be more specific than "it does not work"?

the swipes are not detected in android... I was using the same code for both platforms

@KalebPortillo oh that's weird. It is very much possible that things have changed between now and when I wrote this proof of concept. I haven't been using RN much recently because my day job does not permit it, so I couldn't really tell right off the bat. If you feel like investigating, that would be welcome!

When I swipe my finger left at a decent swiping speed, I get following log ->
' vx : ', 1.9513594000461165e-8, ' dy : ', -1.333343505859375, ' initialVelocityThreshold : ', 0.7, ' verticalThreshold = ', 10
As you see the velocity magnitude is waaayyyyy too small to be compared with threshold
and validHorizontal always turns out to be false.
Trying to get to the bottom of it .

looks like fix should land in rn 0.34
as per
https://github.com/facebook/react-native/pull/8199


Confusing design about reorder and memory

Example first:
I want to use reorder to transpose two memory
src: format: io dims: {2, 3}
dst: format: oi dims: {3, 2}.
However when I use reorder(src, dst), the dims need to be exactly the same. (This is also hard to understand, why not the dim follow the format chaning?)
Then got a question, choose {2,3} or {3,2} ?
This is a bit confusing for me. What's the rule users should follow?
As far as I can see now, this dims always followed oi format no matter it's src or dst memory.
Why like this? Am I wrong?
By the way, I thought if I want to reorder nChw8c to nhwc the dims should be {n, c/8, h, w, 8} to {n, h, w, c} corresponding, then it's simply to me to understand. Otherwise I should use the dim of {n, c, h, w} of format nchw to deal with this case, which should be confusing for user.
Another issue,

This is also hard to understand, why not the dim follow the format chaning?

After reorder, the data buffer actually transposed indeed.
But it did not change the format, that's weird as well.
For example, user reorder src({2, 3}, oi) to io format, the result he got should be dst({2,3}, io) (the {2,3} not changing). Then he want to use the dst memory following the dims to read the data, then should be a error, since the correct dim should be {3,2} now!

Hi @tensor-tang, we have decided that order of values in dims is always fixed and represents the 'logical' dimensions of the tensor. The memory format is 'physical' and is a separate matter. This actually makes things easier because the format is not always known beforehand and yet you still need to be able to describe tensor dimensions. Hope this helps...

Thanks @rsdubtso, Yeah, I can understand your point.
But,

that order of values in dims is always fixed and represents the 'logical' dimensions of the tensor.
But like the case io to oi, how users can understand which dim to choose, {2, 3} or {3, 2}, to init the two memory?
Most likely user would init memory follow the format in dims, then they would got error when reorder here.

And another case, if we train on BDW, then want to inference on other platform like KNL or FPGA.
Then we should at least save the weight format and dims on BWD like OIhw8i8o, but when reorder the weight to another platform the dims saved would not be correct then.

like the case io to oi, how users can understand which dim to choose, {2, 3} or {3, 2}, to init the two memory?
Most likely user would init memory follow the format in dims, then they would got error when reorder here.

Well, of course when you are initializing data explicitly you have to know the layout, there's no getting around that. But that init happens outside of MKL-DNN, right? Typically, the data is read in nchw or nhwc formats and then converted using MKL-DNN primitives. I am probably missing something here...

And another case, if we train on BDW, then want to inference on other platform like KNL or FPGA.
Then we should at least save the weight format and dims on BWD like OIhw8i8o, but when reorder the weight to another platform the dims saved would not be correct then.

This is a very good point. I do not think we have a solution for this rather than converting to a known 'stable' format like nchw every time you write a data to be used later. I think this is what IntelCaffe does.

But that init happens outside of MKL-DNN, right?

In common use I thought the memory can be used outside MKL-DNN.
User can directly init a memory like this:
auto src = memory(memory::primitive_desc({{2, 3}, f32, io}, engine), src_data);
auto dst = memory(memory::primitive_desc({{3, 2}, f32, oi}, engine), dst_data);

This makes perfect sense to me. The src_data and dst_data buffer has been created outside.
And the src is input and filled with some useful data, then he want to convert src to dst of which memory has also been created.
And use reorder(src, dst) to implement this convert. Then he may get an error, since the dims size do not equal.
What he need to do is to create another memory like this:
auto src_tmp = memory(memory::primitive_desc({{**3, 2**}, f32, io}, engine), src_data);
Then reorder(src_tmp, dst), which is weird and confusing for user, right?

I think this is what IntelCaffe does.

Yeah, Thanks. I confirmed with that, IntelCaffe only save cpu_data.

What he need to do is to create another memory like this:
auto src_tmp = memory(memory::primitive_desc({{**3, 2**}, f32, io}, engine), src_data);
Then reorder(src_tmp, dst), which is weird and confusing for user, right?

Okay, now I get your point. And I understand that this is confusing. However, I believe this is a reasonable tradeoff compared to what might have happened if we tried matching the order in tensor dims to format. For example: MKL-DNN supports blocked formats and it would have to map those to some canonical ones before validating the dims. But the choice of canonical formats is not trivial. For example, I see two options for nChw16c -- nchw and nhwc, and either would be causing some confusion...

Yeah, for the blocked formats, like I said:

I thought if I want to reorder nChw8c to nhwc the dims should be{n, c/8, h, w, 8} to {n, h, w, c} corresponding, then it's simply to me to understand

Because I thought for those who know when to use nChw8c should have this knowledge what does it mean, and should also be acquired to know.
Anyway, this is just my own view and concern, thanks @rsdubtso

Okay. Closing then. Thanks for the discussion.


"Casper Imaging could not locate any drives for imaging"

I'm hoping this is the right place to post an issue that @MarkPetersonURMC reported on JAMF Nation:
https://jamfnation.jamfsoftware.com/discussion.html?id=11044
Just getting around to testing this (thanks for updating!).
I'm getting the same Casper Imaging could not locate any drives for imaging error when I boot into the NBI.
If I manually mount Yadayada.nbi/Install.dmg.sparseimage it shows up as Volumes/Install instead of /Volumes/Macintosh\ HD.
We are using Casper NetInstall Creator 4.0 (14062401) which we downloaded today (7/1/2014).
Do I get a t-shirt for being the first to post an issue here? :)
Don

Wow I totally didn't get an alert when you responded! :) We have been trying to get this to work with Casper NetInstall Creator 5.0 and Casper Imaging 9.65 which is supposed to be able to deal with corestorage enabled drives (all Yosemite Macs ship with this), and hopefully with FV2 encrypted drives as well. Not having luck. Tried 10.10, 10.10.1, and 10.10.2 on an iMac 5K Retina.
https://jamfnation.jamfsoftware.com/discussion.html?id=13351

FYI:
https://jamfnation.jamfsoftware.com/article.html?id=228#responseChild824

Don,
Thanks for the note.
FYI - the bug we're dealing with is actually a Casper Imaging bug, and not
a Casper NetInstall Image Creator bug.  Casper Imaging doesn't recognize a
drive that's encrypted with FileVault.  Defect number is D-008217.  I'm
hounding engineering about it, and I will continue to do so until it is
fixed :)
Nick
On Tue, Mar 10, 2015 at 8:46 AM, Don Montalvo<EMAIL_ADDRESS>wrote:

Wow I totally didn't get an alert when you responded! :) We have been
trying to get this to work with Casper NetInstall Creator 5.0 and Casper
Imaging 9.65 which is supposed to be able to deal with corestorage enabled
drives (all Yosemite Macs ship with this), and hopefully with FV2 encrypted
drives as well. Not having luck. Tried 10.10, 10.10.1, and 10.10.2 on an
iMac 5K Retina.
https://jamfnation.jamfsoftware.com/discussion.html?id=13351
—
Reply to this email directly or view it on GitHub
https://github.com/jamf/CasperNetInstallCreator/issues/1#issuecomment-78055323
.

Closing since this was resolved with Casper Imaging 9.7


Default --directory parameter overrides directory in .checkov.yml

.checkov.yml:
directory:
  - infra
evaluate-variables: true
framework: all
output: cli
quiet: true
download-external-modules: false

Action config:
      - name: Run Checkov
        uses: bridgecrewio/checkov-action@master
        with:
          config_file: .checkov.yml

Expected outcome:
$ checkov --output sarif   --config-file .checkov.yml

Current outcome:
$ checkov -d .  --output sarif   --config-file .checkov.yml

Hey @nayoa, if the in-line --directory argument is overriding the config file, that behavior is by design. See the note at the bottom of checkov --help
Args that start with '--' (eg. -v) can also be set in a config file
(/Users/kpande/Downloads/.checkov.yaml or /Users/kpande/Downloads/.checkov.yml
or /Users/kpande/.checkov.yaml or /Users/kpande/.checkov.yml or specified via
--config-file). The config file uses YAML syntax and must represent a YAML
'mapping' (for details, see http://learn.getgrav.org/advanced/yaml). If an arg
is specified in more than one place, then commandline values override
environment variables which override config file values which override
defaults.

Let me know if that is not what you meant.

@kartikp10 : The action is still on . directory instead of the directory mentioned in config.yaml
..
running checkov on directory: .
checkov -d .     --output sarif   --config-file .github/workflows/checkov_config.yaml
..

Although I experience the same problem and it is driving me nuts, I think the subject/title of this issue should more accurately reflect the problem. This is not about the --directory parameter but about the directory setting in .checkov.yaml being ignored (completely). It makes it impossible to use the checkov-action for larger repos or monorepos. As an example, I need to check Kubernetes manifests created with kustomize. However, if Checkov traverses all directories from . then Checkov will fail with a stacktrace due to how kustomize directory structure is and you can overwrite values. At the moment, the Checkov Action is unusable with kustomize repositories I think.


KAFKA-12324: Upgrade jetty to fix CVE-2020-27218

Here is the fix. The reason of CVE-2020-27218 was Incorrect recycling of HttpInput and patched in 9.4.35.v20201120.
This PR updates Jetty dependency into the following version, 9.4.36.v20210114.
Committer Checklist (excluded from commit message)

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

@ijuma @chia7712 Could you have a look?

Let's cherry-pick this to 2.8, 2.7 and 2.6.


Inconsistent handling of identical peptides between indexed and classic searches

When ambiguity is turned off, a single theoretical is assigned to a spectra.
In the case where a peptide is present in both target and decoy search spaces (something that shouldn't occur in the first place), there is inconsistency in that:
For Classic, the peptide assigned is a always a decoy
For indexed searches, the peptide assigned is always a target.
To satisfy a TDA, there should be a random coin toss to determine which ID is assigned in both cases.

As an update, it doesn't appear that turning off ambiguity does anything to output of classic search, so that should be fixed, too.

Is this fixed now?


Update key spanish commemoration_of_all_the_faithful_departed

commemoration_of_all_the_faithful_departed to oficial CEE translate.

Hi @tukusejssirs, good practice to add the source. I've just added your suggested change, that is according the Spanish CCE.


Refused to evaluate a string as JavaScript because 'unsafe-eval'

Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' http://www.google-analytics.com https://www.google-analytics.com http://cdn.mxpnl.com https://cdn.mxpnl.com".

I take it you've added the browser-policy package to your app and have set BrowserPolicy.content.disallowInlineScripts(), is that right?
I don't think that will work, I think most of the analytics service scripts inject inline scripts. I haven't confirmed this, let me know if that fixes your issue.

Nope, we did not use browser-policy, .meteor/packages:
meteor-platform
insecure
ian:bootstrap-3
ian:accounts-ui-bootstrap-3
accounts-password
accounts-facebook
accounts-google
aldeed:autoform
aldeed:collection2
yogiben:autoform-modals
iron:router
mrt:twit
mrt:moment
meteorhacks:npm
npm-container
meteorhacks:async
autopublish
workman:meteor-editable
pahans:reactive-modal
dburles:collection-helpers
fortawesome:fontawesome
percolate:synced-cron
stevezhu:lodash
reywood:iron-router-ga
meteorhacks:kadira
meteorhacks:zones

Can you check which version of the analytics package you're using? Check .meteor/versions. If it's not 0.1.1 can you do meteor update okgrow:analytics? There was a previous version that pulled in browser-policy as a dependency rather than a weak dependency, and sometimes Meteor's version solver defaults to the oldest package rather than the newest (although that's only when adding indirect dependencies, so that's actually probably not the issue).

Can you check which version of the analytics package you're using? Check .meteor/versions. If it's not 0.1.1 can you do meteor update okgrow:analytics? There was a previous version that pulled in browser-policy as a dependency rather than a weak dependency, and sometimes Meteor's version solver defaults to the oldest package rather than the newest (although that's only when adding indirect dependencies, so that's actually probably not the issue).

Thanks, the problem was solved

Just curious, was that the solution? It was an old version? I'm not sure how that would happen unless it was a dependency of another package (or unless you actually installed it during the one day window that it had that bug).

It was an old version


Add a docker-compose.yml file for development purposes

Hi!
I though that it could be convenient to allow contributors the option to work with a docker-compose.yml file. Doing so ensures the developer works with the same node version as the one used in production.
No more yarn needed on the developer machine, just docker exec -ti noether sh to get a shell access and easily run tests, etc...
I also updated the .dockerignore file to ignore the docker-compose.yml that will not be needed in the Docker image, as well as other files and dirs that could also be added.
Regarding the compose file, we could also name it docker-compose.dev.yml or docker-compose-dev.yml if you think the current name could lead to confusion for standard users, but it would mean a more verbose command to bootstrap the contributor environment:
docker-compose -f docker-compose.dev.yml up -d instead of the simple docker-compose up -d.
Please tell me if you have any question or you would like to see more improvement to the work I've done. Thanks!

Looks good. Personally I'd prefer forcing a more verbose invocation but add -dev or something alike to the docker compose file, but the default name works too.


Scale up components on Loki write path

Scale up components on Loki write path
do not allow changing mla NS in the deploy script

/lgtm


api change: introduce KABPFMapElement interface

This introduces KABPFMapElement and make changes to LookupElement(), UpdateElement() and DeleteElement().
Now the consumer needs to satisfy this interface to make use of element management methods.

I'll leave this open for a couple of days, waiting for a possible discussion.


Update extension-based-hybrid-runbook-worker-install.md

Missing dash for argument TypeHandlerVersion

Due to the upcoming conference, all merging and publishing are on hold until the morning of 5/23.
This PR is ready for merge on 5/23.
#label: "event-triaged-to-10AM"
#label: "missed-content-complete"

#sign-off


Starboards don't work inside threads

Describe the bug
Stars on messages in threads don't get posted to the starboard.
To Reproduce
Steps to reproduce the behavior:

Make a thread
Post a message
Add star/etc reactions until the threshold

Expected behavior
I'd expect the message to get posted in the starboard like any other message, but right now it doesn't.
Screenshots

Additional context
You'd likely need to update to a discord.py version that supports api v9, and then the bot should receive events as normal.

This will not be supported until at least starboard 2.0, and definitely not until @CircuitSacul gets back, as nobody else has permission to restart the bot to apply updates.

This will be fixed when the next release of Starboard comes out.


[QUERY/ Feature Req] EventHubConsumerAsyncClient doesnt support checkpoint feature as Sync client does.

We are developing a reactive application and using EventHub for our event processing. Currently we are using EventProcessorClient for consuming the messages asynchronously like below.
Sinks.Many<CustomMessage> unicastSink; = Sinks.many().unicast().onBackpressureBuffer()
EventProcessorClientBuilder eventProcessorClientBuilder = new EventProcessorClientBuilder()
.connectionString("connStr","ehname")
.consumerGroup(EventHubClientBuilder.DEFAULT_CONSUMER_GROUP_NAME)
.processEvent(PARTITION_PROCESSOR).processError(ERROR_HANDLER)
.checkpointStore(new BlobCheckpointStore(blobContainerAsyncClient));

public Consumer<EventContext> PARTITION_PROCESSOR = eventContext -> {
    PartitionContext partitionContext = eventContext.getPartitionContext();
    EventData eventData = eventContext.getEventData();

    System.out.printf("Processing event from partition %s with sequence number %d with body: %s%n",
        partitionContext.getPartitionId(), eventData.getSequenceNumber(), eventData.getBodyAsString());

    unicastSink.tryEmitNext(new CustomMessage(eventData.getCorrelationId(), eventData.getBodyAsString()));

    if (eventData.getSequenceNumber() % 10 == 0) {
        eventContext.updateCheckpoint();
    }
};

Here in the consumer function, we are emitting the messages to the sink as we consume which is working fine in a normal scenario.  If the consumer(Operator) of these messages are processing slowly, then i have to slow down the consumption of messages from EventHub. How to achieve it ? I see there are reactive consumption in EventHubConsumerAsyncClient but they dont support Checkpoint feature.

Thanks for reaching out to us via this GitHub issue, @anandsugumaran.  @conniey can you please follow up?
/cc @Azure/azsdk-sb-java

EventHubConsumerAsyncClient is our lower-level client, we do not support checkpointing because there is no concept of "load-balancing" between multiple instances that EventProcessorClient has.  You would have to manage your own checkpointing locally and results to a persistent storage. Additionally, EventProcessorClient recovers indefinitely when there is an error, EventHubConsumerAsyncClient will attempt to reconnect until the retryOptions elapse, after that, you'd have to own the recreation/reconnection of the client.


MavericksLauncherMockActivity crashes if there's no App.Theme or if fragments are Hilt fragments

From testing w/ a small Compose test app where there's no App theme, this activity can crash with this error:
UnsupportedOperationException: Failed to resolve attribute at index 1: TypedValue{t=0x2/d=0x7f030003 a=-1}, theme={InheritanceMap=[id=0x103013fandroid:style/Theme.DeviceDefault.Light.DarkActionBar,

Fix is to add an app theme but probably should be documented.
Also, when launching a Hilt Fragment MockableMavericksView from MavericksLauncherMockActivity, this happens:
java.lang.IllegalStateException: Hilt Fragments must be attached to an @AndroidEntryPoint Activity. Found: class com.airbnb.mvrx.launcher.MavericksLauncherMockActivity

Wrapping the MavericksLauncherMockActivity like this had the same error:
@AndroidEntryPoint
class HiltMavericksLauncherMockActivity : MavericksLauncherActivity() {

    companion object {
        private inline fun <reified T> Context.buildIntent(initializer: Intent.() -> Unit = {}): Intent {
            return Intent(this, T::class.java).apply(initializer)
        }

        fun show(context: Context) {
            context.startActivity(context.buildIntent<HiltMavericksLauncherMockActivity>())
        }
    }
}

even when launching with "HiltMavericksLauncherMockActivity.show(this)"

This looks like just a docs issue...doing this works fine and probably should be part of the mavericks-hilt module?
@AndroidEntryPoint
class HiltMavericksLauncherMockActivity : MavericksBaseLauncherActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)

        if (savedInstanceState == null) {
            MavericksLauncherMockActivity.showNextMockFromActivity(
                activity = this,
                showView = { mavericksView ->
                    // Use whatever custom code you want to show your Mavericks View
                    setFragment(mavericksView as Fragment, commitNow = true)
                },
            )
        }
    }
}


Unable to pass cloudflare challenge

Hey,
I just started using your tool and it is truly amazing!
However, I have some trouble to bypass some cloudflare protections.
from botasaurus import *

@browser()
def scrape_heading_task(driver: AntiDetectDriver, data):
    driver.google_get("https://vulbis.com")
    driver.prompt()
    heading = driver.text('html')
    return heading

if __name__ == "__main__":
    # Initiate the web scraping task
    scrape_heading_task()

Issue: it keeps refreshing the page, not able to solve the challenge

How did you go about solving this mate @WarKaa
I am really stuck and need help too

@WarKaa Could you tell, how did you solve this? would be really helpful.


FIX: Verify proc file exists before reading

Changes proposed in this pull request
Check that /proc/1/cgroup exists before attempting to read it.
Fixes #1453.
Documentation that should be reviewed

Has this change been pushed to docker hub? I cannot seem to build docker images directly from the github repository.

You should be able to use poldracklab/fmriprep:unstable to use the latest master. But we have not yet made a release that includes this PR.

Ugh, I ran into another error with poldracklab/fmriprep:unstable. Here it is: No module named 'fmriprep.interfaces.images. Any ideas?

Yeah, there's been a reorganization, and apparently we haven't caught all the vestiges of the old organization. Thanks for testing before we hit the release button... Could you share your command line?

Got it.
Here is the snippet from an executable that runs fmriprep:
subj_id=A01
#ses_id=SESSIONID
data_dir=/home/umii/hendr522/scratch.global.data/BIDS/Ann_Van_de_Winckel_Stroke
singularity run -B ${data_dir}/BIDS_output:/bids_dir -B ${data_dir}/fmriprep_output_new:/output_dir  /home/umii/hendr522/singularity_images/poldracklab_fmriprep_unstable-2018-12-20-a7b8e494e
dad.simg /bids_dir /output_dir participant --participant_label ${subj_id} --fs-license-file /output_dir/license.txt --use-aroma --medial-surface-nan --nthreads 3 --mem_mb 90000 --longitudinal

I'm dealing with some time sensitive processing, is there a version that I could use that is guaranteed to be stable?

It looks like 1.2.2 is the last version that predates the cgroup check. We can try to get master to a state that works for you by tomorrow, if you have time for some back-and-forth, but I'm hesitant to push a new release just before the holidays.

Also, can you provide any more context for the No module named 'fmriprep.interfaces.images' error? Was there a traceback? I'm not able to find a place that attempts to use it.


DFI and BTC Wallets Missing

Preflight Checklist

[x ] I have searched DeFiChain’s Github Issue Page and none matches my issue
[x ] I have read through How To Submit Issues for DeFi App

Issue Details

Current DeFi App Version:
2.1.4
Previous DeFi App Version:
None
Operating System (OS):
Windows 10

Screenshot(s) / screen recording(s) of issue
Cake DFI Withdrawal Jan 25 2021.zip
Actual Behavior
DeFi App crashed when I was sending funds from Cake to my DFI wallet in the DeFi app. I'm worried that my funds might be lost. Neither my DFI wallet nor my BTC wallet appear in the DeFi app.
Please provide steps on how to reproduce the issue:
1. Open the app
2. Go to wallet page
3. Click on DFI
4. Send DFI
5. Unable to send DFI
6. Error: Insufficient UTXOs

-->
Expected Behavior
Open app. See my DFI wallet and my BTC wallet. See funds deposited from Cake to DFI wallet in the app.
App log / binary log / app config

app_log.log

take a look:

Clarke Quay upgrade transition is successful and live on mainnet.
App users, please ensure that you are running app version 2.1.9 and up.
If you run a node, ensure that it is version 1.4.x and up.

(https://t.me/defichain_announcements)
did upgrading solve your issue @OreoDave71 ?

take a look:

Clarke Quay upgrade transition is successful and live on mainnet.
App users, please ensure that you are running app version 2.1.9 and up.
If you run a node, ensure that it is version 1.4.x and up.

(https://t.me/defichain_announcements)
did upgrading solve your issue @OreoDave71 ?

Hi Adrian. Yes, upgrading to the newest version of the software did help
quite a bit. We can call the issue resolve. That said, I won't be
using even the newest version of the software on a regular basis until some
improvements are made. The software is "buggy" and takes quite a long time
to sync even when run on a new computer with lots of RAM and a good
graphics card.
OreoDave
On Tue, Jan 26, 2021 at 9:35 AM Adrian Schnell<EMAIL_ADDRESS>wrote:

take a look:
Clarke Quay upgrade transition is successful and live on mainnet.
App users, please ensure that you are running app version 2.1.9 and up.
If you run a node, ensure that it is version 1.4.x and up.
(https://t.me/defichain_announcements)
did upgrading solve your issue @OreoDave71 https://github.com/OreoDave71
?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DeFiCh/app/issues/383#issuecomment-767625171, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASI7GZYPQWWFNDNQYFYGFZDS33OLJANCNFSM4WSNB2CQ
.

Hi Adrian. Yes, upgrading to the newest version of the software did help
quite a bit. We can call the issue resolve. That said, I won't be
using even the newest version of the software on a regular basis until some
improvements are made. The software is "buggy" and takes quite a long time
to sync even when run on a new computer with lots of RAM and a good
graphics card.
OreoDave
On Tue, Jan 26, 2021 at 9:35 AM Adrian Schnell<EMAIL_ADDRESS>wrote:

take a look:
Clarke Quay upgrade transition is successful and live on mainnet.
App users, please ensure that you are running app version 2.1.9 and up.
If you run a node, ensure that it is version 1.4.x and up.
(https://t.me/defichain_announcements)
did upgrading solve your issue @OreoDave71 https://github.com/OreoDave71
?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/DeFiCh/app/issues/383#issuecomment-767625171, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ASI7GZYPQWWFNDNQYFYGFZDS33OLJANCNFSM4WSNB2CQ
.

Hi @OreoDave71 , thanks for your feedback, I understand your hesitation, our team is constantly working on improving the app and solving its issues. We regularly do releases, so if you are not in a big hurry I would suggest staying on the latest version and wait for a fix.  Thank you for your understanding.
Hi @adrian-schnell thank you for the help!

Hi @OreoDave71 , thanks for your feedback, I understand your hesitation, our team is constantly working on improving the app and solving its issues. We regularly do releases, so if you are not in a big hurry I would suggest staying on the latest version and wait for a fix.  Thank you for your understanding.
Hi @adrian-schnell thank you for the help!


Rewrite CONTRIBUTING

Consider moving it to a wiki

[ ] Finish WIP sections
[ ] Add section on Git workflow


Added Oxford IIIT Pets Dataset

The current implementation only supports image segmentation but the code can be further adapted for image classification.
I need some help for a few sections.

Hey @BradLarson just a gentle reminder in case you missed this.

I am working on adding some tests and should be done soon.

Looks like the OxfordIIITPets.swift file might be missing from the CMakeLists for Datasets, leading to a test failure:

OxfordIIITPets/OxfordIIITPetsTests.swift /swift-models/Tests/DatasetsTests/XCTestManifests.swift    && :
/swift-models/Tests/DatasetsTests/OxfordIIITPets/OxfordIIITPetsTests.swift:7:19: error: cannot find 'OxfordIIITPets' in scope
let dataset = OxfordIIITPets(batchSize: 64)

The conflicts are because of WordSeg's entry in CMakeList. Just adding the file entries for CMake would result in a build failure hence it would be cleaner to just start a new pull request and close this one.
The new PR is at #548


Background monitoring is killed and never restarted

Hi! Recently started using Estimote SDK, and I had a few questions regarding a bug we've been having when developing our indoor map application.
First of all, some information:
Device: Samsung Galaxy S7
OS Version: 6.0.1
Estimote SDK version: 0.16.0
My app does the following: Monitors beacons and sends beacon data to a web server for real-time positioning (by closest beacon).
The problem: Beacon background monitoring stops working after a time period (varies, but usually one or a few days). During this time period I usually have time to charge my phone etc, but never restart it. I enter/exit different regions every weekday, many times a day (beacons at the office).
Some code (removed the application-specific code):
public class BeaconApplication extends Application implements BeaconManager.MonitoringListener {

    private BeaconManager beaconManager;

    @Override
    public void onCreate() {
        super.onCreate();

        beaconManager = initBeaconManager(new BeaconManager(getApplicationContext()));
    }

    public BeaconManager initBeaconManager(BeaconManager beaconManager) {
        monitoredRegions = new ArrayList<>();

        beaconManager.connect(() -> {
            beaconManagerIsConnected = true;
            fetchRegionsAndStartMonitoring(); // Fetches regions from a database and monitors each region.
        });

        beaconManager.setMonitoringListener(this);
        return beaconManager;
    }

    @Override
    public void onEnteredRegion(Region region, List<Beacon> list) {
        updateUserLocation(region);
    }

    @Override
    public void onExitedRegion(Region region) {
        // Do nothing
    }
}

I have verified that the BeaconService is no longer in my apps running in background.
So, since this is not working, I am having a hard time figuring out the issue. Should I declare com.estimote.sdk.BeaconService in my manifest? Should I use my own background Service for handling the monitoring? Or is it maybe recommended to use a foreground Service for handling beacons to make sure the app remains alive, and letting users know that we are monitoring beacons? Also, would this affect the beacon scan period (which currently adjusts to doze nicely)?
On another note: Do I need to do EstimoteSDK.initialize(...) in my Application onCreate method? It's mentioned at the github page, but not at the get started page.
Thanks in advance!

I have now verified that this does not work for Nougat either.
But using a Foreground Service to keep the app alive works, and the beacon monitoring still properly adjusts to doze.
So I moved the start/stop monitoring calls to a ForegroundService onCreate/onDestroy to resolve this issue, and simply toggling beacon monitoring by starting/stopping the service.

Hello @magnusgudmandsen !
Thanks for reporting that. Android system might kill our beacon service whenever it wants - especially after one/two day constant scan. We can do nothing about it. Your idea with launching service in the foreground is pretty neat - the only downside is that user is constantly aware of this process via notification bar. Not all our developers wan't that behaviour, so we decided to use background service. Let me know how this solution works in the long run!

@pawelDylag Wouldn't using START_STICKY as a return value to the Service's onStartCommand solve this issue by letting the Android system know that we want this service to run whenever we can? This should signal to the Android OS that this service should restart again once we have enough memory to run it again (or for whatever reason it was killed).
Also, even if all developers might not want that behaviour, it would be really convenient to allow us to set it to the BeaconManager instead of implementing it ourselves (as many might want this behaviour for continuous scanning).
Such a method could have something like the following signature, demanding that we supply the notification that should be showed:
public void startForegroundNotification(@NonNull Notification notification) {
    startForeground(ONGOING_NOTIFICATION_CONSTANT, notification);
}

public void stopForegroundNotification(boolean removeNotification) {
    stopForeground(removeNotification);
}

When started, this should allow the beacon monitoring to be run in the background indefinitely, and conform to the demands from Android that the user is aware of this.
My current solution is a very simple background service that just calls my extended BeaconApplication class to do all the dirty work. When the service is created, I start it in foreground with a notification and start monitoring, and when the service is destroyed I stop monitoring (and the notification is automatically removed when service is destroyed).
The BeaconManager callbacks are handled in the BeaconApplication class, which also contains the BeaconManager. This works since the Application object is always alive while the service is alive.

I encourage you to try our new ProximitySDK 🚀 - it is dedicated for creating proximity interactions with our beacons - its main focus is to deliver the reliable enter/exit experience according to a different zones of beacons, based on our own data-science, and Estimote Monitoring packet.
It works extremely well with Android 5.0-8.0 devices (full support for Nougat, and Oreo included), and also allows you to configure it to keep scanning in the background.
Here is the official repository page ->  https://github.com/Estimote/Android-Proximity-SDK
Also, we keep posting updates about the progress of our development on this thread at our forums.
I encourage you to track it in order to be super up-to-date :)
Please, check the mentioned new SDK - the current SDK will soon be deprecated, and we will support only critical issues for some time.


Version 2.13.6 pulls in scala3 dependencies

It's quite inconvenient that com.lihaoyi:ammonite_2.13.6 pulls in scala 3.0. Is this intentional?
See the generated pom file:
https://search.maven.org/artifact/com.lihaoyi/ammonite-cross-23-util_2.13/2.4.0-19-f4790b61/jar
Without modification, when attempting to compile a REPL line, I get this obscure runtime error:
fansi.Attrs does not take parameters

If I explicitly exclude the scala3 dependencies and grab the 2.13 versions, then I can again use the REPL.

To be extra clear, these are the dependencies that I exclude and include back into the project:
    implementation('com.lihaoyi:ammonite_2.13.6:2.4.0-19-f4790b61') {
        exclude group: 'com.lihaoyi', module: 'pprint_3'
        exclude group: 'com.lihaoyi', module: 'fansi_3'
        exclude group: 'org.scala-lang', module: 'scala3-library_3'
    }
    implementation 'com.lihaoyi:pprint_2.13:0.6.6'
    implementation 'com.lihaoyi:fansi_2.13:0.2.14'


Email Authentication to another Login form project

Issue Type:

[x] Feature Request

Describe the bug

there is one more project related to Signup and login form. I want to setup email Auth for that one too

@VidhiBhatt01 @DEEPALI-SUK Can I get assign to this task?


Updates to state migration wiki page

I have made some updates to the state migration wiki page.

A few general comment. Can you please really make sure that the steps are possible and exact? For example, in step 2 constants.js does not exist. In step 6 can you please explain more how the contributors should write the draft migrations?

Ah! Forgot to remove the 2 point, done now. I have also taken a quick pass and have updated the page. Let me know if you think any thing else need change.
Thanks
@vojtechjelinek PTAL

@vojtechjelinek note that we don't have Oppiabot on this repository, so you have to manage the assignments manually

Hey @vojtechjelinek, I have made the necessary changes PTAL.
Thanks

@lkbhitesh07 are you stuck anywhere?

@lkbhitesh07 Lets try to merge this PR soon

Sorry for the delay, I accidentally missed out on this. Done with the changes.
Hey @vojtechjelinek PTAL.

Done with the changes @vojtechjelinek. PTAL
Thanks

@lkbhitesh07 Does @DubeySandeep and @iamprayush also have to review this PR?

@lkbhitesh07 Does @DubeySandeep and @iamprayush also have to review this PR?

Not really, I think @vojtechjelinek has approved the PR and that would be enough. I'm fine either way, if it is mandatory we can have reviews from them too.
Thanks

Also please add a Table to contents to be beginning of the file.

Done with the changes @gp201.
Thanks


nm, ovs: Fix report crash when OVS has dup iface names

In case of an existing OVS deployment which uses an identical name for
the bridge, port and interface, libnmstate.show() exploded.
It is now possible to report such deployments.

Please, let me prepare a full solution for this. Thanks!

Please, let me prepare a full solution for this. Thanks!

A more comprehensive solution can still be added as a follow-up. IMHO it is important to ensure this is fixed on base before merging the PRs on the other branches.

Please, let me prepare a full solution for this. Thanks!

A more comprehensive solution can still be added as a follow-up. IMHO it is important to ensure this is fixed on base before merging the PRs on the other branches.

I am not sure this is possible, the changes needed here are much different and the fixes I used on previous version are not enough, on base another layer fails. So there are two points that need caring here beyond what I just posted:

Handle the new error seen here (coming from register_async).
Support reporting duplicate names.

If we manage to fix the 1st now, great. If we cannot do it in a few days, I prefer the fixes on older branched to get in and work on this in parallel.

This PR does not works when ovs internal interface holding the same name with ovs bridge.
The upper level fix has been working at https://github.com/nmstate/nmstate/pull/1370

Closed as dup of #1370


Remove torchvision and torchtext

Description

Remove torchvision and torchtext from the base requirements.

Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] Refactor (non-breaking change which refactors the code base)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist

[ ] My code follows the pre-commit style and check guidelines of this project.
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing tests pass locally with my changes
[ ] I have added a summary of my changes to the CHANGELOG (not for minor changes, docs and tests).

nstalled? If I remember correctly, SC docker files contain additi

We don't have a check for torch, but do have for these. Actually this would be even more problematic

nstalled? If I remember correctly, SC docker files contain additi

We don't have a check for torch, but do have for these. Actually this would be even more problematic

Alright. Let's roll with this then

@ashwinvaidya17, I also feel that we should also have anomalib install option that comes with the CLI. I think that would be the safest bet


StopLaunch&StartLaunch endpoint

StopLaunch endpoint should do

Stop selected launch. (Replica count 0)
Change workload_status flag --> false

StartLaunchendpoint should do

Stop selected launch. (Replica count 1)
Change workload_status flag --> true

Both of them gets "Launch" return error and "Launch".

Too much code reusing  stop & start endpoint can be merged on same endpoint as a toggle endpoint or operations can be merged under kubeclient pkg.


changelog clean - [merged]

Merges changelog -> master

In GitLab by @wtbarnes on Oct 29, 2021, 07:33
mentioned in commit f1a4e2fd4e74e4327bd2f898e5c89fce2934be96

In GitLab by @codecov on Oct 29, 2021, 07:17
Codecov Report

Merging #122 (52151e1) into master (a248c7a) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #122   +/-   ##
=======================================
  Coverage   97.43%   97.43%
=======================================
  Files          16       16
  Lines         545      545
=======================================
  Hits          531      531
  Misses         14       14

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a248c7a...52151e1. Read the comment docs.

In GitLab by @wtbarnes on Oct 29, 2021, 07:32
approved this merge request

In GitLab by @wtbarnes on Oct 29, 2021, 07:33
picked the changes into the branch cherry-pick-f1a4e2fd with commit 33689d48df295c08206ca0a3fef7b246f13be5c4

In GitLab by @wtbarnes on Oct 29, 2021, 07:36
mentioned in commit 97c3be18fb54d6b237264e2b5cc4ec486d9434a3

picked the changes into the branch cherry-pick-f1a4e2fd-2 with commit 97c3be18fb54d6b237264e2b5cc4ec486d9434a3

mentioned in commit 68113f877f8e8cd95e9fcc07899fb57a19775077

In GitLab by @wtbarnes on Oct 29, 2021, 07:33
mentioned in commit 33689d48df295c08206ca0a3fef7b246f13be5c4


Texas bays disappear at zoom 9

TO REPRODUCE THE ISSUE, FOLLOW THESE STEPS:

In all each Tangram style (and in our own Map Maker) we're losing Matagorda Bay just northeast of Corpus Christi, Texas.
Zooming from level 8 to 9 causes the bay to turn into earth (I can't see a way to fix it in the yaml styles)

RESULT:
Bay disappears.

EXPECTED RESULT:
The bay should remain (and get probably more detailed as the data switches to OSM).
ENVIRONMENT:
Happening in Mac OS Chrome Version 61.0.3163.91 (Official Build) (64-bit)

@nvkelso likely a data issue (though could be a style thing) :)

Data problem in OSM, overzealous data editor there.
Sent from my handsful device.

On Sep 19, 2017, at 15:02, Brett Camper<EMAIL_ADDRESS>wrote:
Assigned #596 to @nvkelso.
―
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

Bah! Should they be natural=bay or something else?

On Sep 19, 2017, at 3:07 PM, Nathaniel V. KELSO<EMAIL_ADDRESS>wrote:
Data problem in OSM, overzealous data editor there.
Sent from my handsful device.

On Sep 19, 2017, at 15:02, Brett Camper<EMAIL_ADDRESS>wrote:
Assigned #596 to @nvkelso.
―
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Technically the editor is re-tagging to valid tag. It just breaks most maps as it's an annual data update instead of a minutely diff config. Next mapzen build will update, but esp 6-8 weeks.
I'll relate vector tile issue here when I'm back at computer. Should be tracked there instead of here.

On Sep 19, 2017, at 15:09, Jon Schleuss<EMAIL_ADDRESS>wrote:
Bah! Should they be natural=bay or something else?

On Sep 19, 2017, at 3:07 PM, Nathaniel V. KELSO<EMAIL_ADDRESS>wrote:
Data problem in OSM, overzealous data editor there.
Sent from my handsful device.

On Sep 19, 2017, at 15:02, Brett Camper<EMAIL_ADDRESS>wrote:
Assigned #596 to @nvkelso.
―
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.

―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@nvkelso 10-4 that makes sense. thank you!

It's this https://github.com/tilezen/vector-datasource/issues/1383.


support inlay hints

For neovim, this can be accomplished temporary by using https://github.com/phenax/nvim-extra-codelens. It simply uses treesitter and definition to produce inlay type hints. I used with typescript and so far it works very well.
Not sure would incorporating a similar solution to xbase core is good idea or to wait to sourcekit-lsp to be supported.


Add SEOwl.co under Keywords section

SEOwl is a cool rank tracker providing both free and paid plans, I think this would be a nice addition to the tools list

@Sadikk
Thanks for your contribution 👍


Deepseek-coder actually uses deepseek-chat?

Issue
So I've been using the deepseek model for a few days and wanted to check its usage, strange, but it shows that only deepseek-chat was used all the time

And this is the command I'm using for running aider
aider --deepseek

or
aider --model deepseek/deepseek-coder

Wha't im getting is this

And even I've run test couple minutes ago, and also only deepseek-chat shows usage, am I missing something or this is really an issue?
Thanks!
Version and model info
Aider v0.60.0

Deepseek models have been merged: https://api-docs.deepseek.com/ and deepseek-coder and deepseek-chat are supposed to be the same.

Ah, thank you for your reply, I didn't know that this is how it works at the moment, their dashboard is a bit confusing, thank you for your reply.


Foreground colors in About window don't work with light mode

This is 11.2 (Big Sur). Only logo is problematic, text OK.

Looks like templated images are not working as expected for big sur, The image is correctly adjusted in light mode for catalina 10.15.7, have to test out all the other images also if they are working as expected.
Screenshot from catalina

@jsliacan Still haven't updated to big sur, but i updated Xcode and it now has the big sur sdks, which i think should fix this issue, can you please try out this build (https://54-241065687-gh.circle-artifacts.com/0/crc-tray-macos.tar.gz) and check if the color issue is fixed now.

Sorry, still seems the same with Light theme on OS level.

Same issue with 10.14

Fixed by https://github.com/code-ready/tray-macos/commit/7e484035b911c3313507edcd1f053e3167fe5ed6


[Bazel] batch 9, of 12 files (s)

Files starting with s, except for those starting with 'snark' and a few others, which have already been PRed.

!ci-build-me


Reconnect to a previous device causes strange behavior

As a central, I'm seeing a weird behavior, as if either binc (or more likely bluetoothctl) is "remembering" something about a previous device.
A device will disconnect, but the scanner is still running, and so as soon as the device comes back into range, it will connect again.  However, when this happens, before I've done any configuring of the device, I will get a few notifications (two from the battery, two from one of my custom characteristics).  I can see from btmon that these get produced from bluetooth, but I also see that these die NOT come from my device.  Separate logging on my device shows no activity there.
Then, when I go to configure my newly connected device, I go to turn on the battery level characteristic to send notifications, but (1) the library is telling me this characteristic already has notifications enabled (binc_characteristic_is_notifying saying true), and then when I try to enable it anyway via binc_characteristic_start_notify, the command goes out, but there is no log saying it returned (no notifying true <uuid>) probably because it's already true so it didn't "change"?

My workaround for this at the moment is that I check to see the state before I do an action.  If I want to turn notifications on, but it's already on, I say "hey that's weird" (because I know in my application I never want to turn it off).    It's a hack because there is the possibility I could get into a loop here maybe, but it suffices.
But I'm curious if you are keeping objects around in your library based upon the UUID of the characteristic, and they are staying even if a device disconnects?  And then the internal state of that is "notifications were enabled".  Or, as I said, most likely it's a bluetoothctl thing

This is probably expected behavior. Bluez retains notification state for as long as the object is on the DBus. For paired devices this is the correct behavior and in line with the bluetooth standard. But for non-paired devices this should not be done. What I do in my apps is to remove non-paired devices from Dbus upon disconnecting. That way Bluez will 'forget' the notification state...

Got it.  This is a non-paired device (BINC_BOND_NONE when discovered, and no pairing request made).  Is there some way to "force" something off the DBUS when it's disconnected?
My workaround is fine.  If you think about it, I can't think of a reason why I would have notifications enabled and would want to turn it off, so if I were to ever see it on when I think I want to turn it on, it's easy enough to assume that maybe the data is stale and to force it off, and then back on.

Boom!  That did the trick.
I'm wondering... since this is DBUS related, would there be any benefit to also "hiding" this?  i.e. if we sense a device is disconnected, and it isn't a paired device, could adapter/device just internally call the remove?
Totally get why you might be reluctant to do that.

Well, if you remove it always, then you always need to discover it again before you can connect again. This might not be desirable in all use cases...e.g. if you want to connect to known devices quickly

So, how do I connect to already paired devices? I'm a newbie and I can't see the paired devices in discovery and I'm not getting any connection change event when the paired device is powered on.


Serialization

I was not merging this because I was looking into cereal as alternative for boost serialization.
By just reading the documentation I don't see much benefit in using cereal instead of boost, even though the documentation is much better.

Have a look here :
https://github.com/thekvs/cpp-serializers
Cereal outperforms boost

So the main benefit is that is twice as fast, which is definitely a plus. The biggest drawback is maybe the problem we can get by mixing up different versions of cereal or using boost serialization in the mix. Cereal does not save it's version in the archives.
But anyway I need to do some tests to see if we really can use it in the current setup. There are no polymorphic archives in cereal, on which we currently relay in the SerializationHandle class.


Remove dependency on a custom engine fork

Obviously I'd like to not make every user rely on downloading some guy's fork of Godot to use this extension. However, this is not feasible right now. This issue is blocked by:
https://github.com/godotengine/godot-proposals/issues/8609
https://github.com/godotengine/godot/pull/86539 (or another pull request that does this in a better way)

this can close i think

As far as I can tell all the godot-steam-audio documentation says it requires a godot fork.

this pr was merged https://github.com/godotengine/godot/pull/86539

Cheers

Yeah! Closing this.

Wait, so a custom fork is no longer required?

It is not required provided you get the release on the PR, and you are using Godot 4.4. When there is a stable release for 4.4 I’ll merge the PR and release a new version of the extension.


Second Child Window Placement possible?

Hey guys,
Is there a way (or is it planned) to enable window_placement = second child like in yabai or many tiling window managers for linux?
To explain for those that don't know what I mean: You start a new window. When you open another one, it splits horizontally, of course. If you open a third one, it will split this half vertically, where you had the focus while opening the third window - and so on.

I think once you have three you have to make the choice to join windows together in a container and each container would occupy their respective estate and would have the effects that you are seeking but there is no automatic configuration for this.

@hwamil the fact that you "have" to make the choice is probably the reason that @RobinRuf created the ticket, which is totally understandable.
Coming from Yabai or other tiling managers, this automatic management of the children is something that aerospace should also possibly do.
So currently if you have two windows side by side like this:
h_tiles
├── window 1
└── window 2

When opening a third window, the current behaviour is opening it in the same container, 3 windows side by side like this:
h_tiles
├── window 1
├── window 2
└── window 3

And this is acceptable and might actually be the preferred option if its being used in a ultrawide monitor.
But for the regular monitors like the built-in display, splitting the second and third window vertically would make more sense (OR having to accordion those two) but ideally in that monitor we could have something like this:
h_tiles
├── window 1
└── v_tiles
    ├── window 2
    └── window 3

This is possible by joining the window 2 and window 3 after opening the window 3, but there could be an option to automatically join that new window.

@danfbfern Yeah, I was just answering his question. I'm a layman so that's all I can do :(


Reordering does not work when drop is disabled

First of all, thanks for this library, it's great!
I am struggling to figure out how to get the following DnD behaviour to work properly with the following tree:

Root1
Root2
Root3

Child1
Child2

Root4

Child3
Child4

Roots should not be allowed to be dragged into each other
Reordering roots at the same level should still be allowed

If I provide the disableDrop handler with something like:
  if (parentNode.level >= dragNodes[0].level) {
    return true;
  }
  return false;

Then the roots are no longer allowed to be dragged into each other but also reordering is no longer working properly - it seems that I can only reorder in between roots with children (for example drag Root1 in between Root3 and Root4) or drag a root all the way to the top or bottom.
Am I using this correctly?

Hi! Thanks for using the library. I believe it is possible with the disableDrop prop.
((args: {
        parentNode: NodeApi<T>;
        dragNodes: NodeApi<T>[];
        index: number;

The parent node is the "folder" your dragging over.
The index is the place within the folder you will drop.
And the dragNodes are the nodes you are dragging.
So you maybe need to check if the dragNode.parentId === parentId. Then allow drop only if that is true?
Checkout the Node api. Those are all the methods you can call on the dragNodes.
Please report back if that works for you.

Thanks for the reply @jameskerr. I haven't been able to figure it out yet completely, but I am unsure if I've found a bug. The following code almost works (also brings the behavior I want for folders further down the tree):
  const dragNode = dragNodes[0];
  if (dragNode.isInternal) {
    if (parentNode.level < dragNode.level) return false;
    return true;
  }
  return false;

This works most of the way but once again, only works if I drag Root1 in between Root3 and Root4. In this scenario parentNode.level becomes -1 with an id of __REACT_ARBORIST_INTERNAL_ROOT__ which allows the root to be dropped in between. But if I drag Root1 in between Root2 and Root3, parentNode.level stays 0 and the drop is disallowed. It seems this is dependent on whether or not the internal node has any children or not - if the children array contains any objects, the level becomes -1 and if the array is empty it stays 0.


always missing on the Alphabetical Index

What is always missing on the Alphabetical Index? XD
It appears everything in Functional and Core is missing from the Aplahbetical Index as well.

hana::always :).

Duplicate of #238.


Addresses show obscure names instead of of towns/cities

When reverse-resolving addresses with OpenStreetMap, TeslaMate gives hamlets higher rank than cities, so most of my drives show some obscure names instead of well-known ones.
For example, this shows on TeslaMate as 'IKEA, Pioneer Homes' instead of 'IKEA, Elizabeth': https://nominatim.openstreetmap.org/details.php?osmtype=W&osmid=29416243&class=shop
Pioneer Homes is a neighborhood 2 miles away which just happens to be the closest hamlet point.
OSM returns these closest hamlet points even if they are not related to the address at all. Cities and towns are enclosing polygons and should be much more relevant.
geocoder.ex module pulls the first available tag from OSM in this order:
  @city_aliases [
    "village",
    "hamlet",
    "locality",
    "croft",
    "city",
    "town",
    "municipality"
  ]

Would it make more sense to move town/city/municipality before village/hamlet, so hamlet names will be used only if there is no city/town name available?

That definitely makes sense 👍


Add mapping strategy to global configuration options

We often have to map on field-level instead of property/method level and need to have a common configuration option to define the mapping strategy. To avoid explicit field mappings like this
        <field>
            color
            color
        </field>

we want to configure field mapping globally:
    <configuration>
            <mapping-type>FIELD</mapping-type>
    </configuration>

We do although not want to send unnecessary accessors (getter/setters) to our domain objects just to satisfy Dozer.

+1

@openwms , do you know if someone has started working on it? Or has it been at least approved? I'm keen on looking into it myself.

@yuranos87 I did only a few investigations in the code to find out how it can be realizied. It shouldn't be hard to get it realized. The more tricky part is to find all occurrences where this configuration parameter needs to be considered.
@garethahealy Whats your opinion? Do you give your approval for this feature?

If one of you is happy to do the work, i am happy to review/merge.

Any roadmap for implementing this?


This query is not working

{
	"message": {
		"query_graph": {
			"nodes": {
				"n0": {
					"id": "MONDO:0005132",
					"category":"biolink:Disease"
				},
				"n1": {
					"category": "biolink:ChemicalSubstance"
				},
				"n2": {
					"id": "UMLS:C0032961",
					"category":"biolink:Disease"
				}
			},
			"edges": {
				"e01": {
					"subject": "n1",
					"object": "n0",
					"predicate":"biolink:treats"
				},
				"e02": {
					"subject": "n1",
					"object": "n2",
					"predicate": "biolink:contraindicated_for"
				}
			}
		}
	}
}

Seems the reverse edge is not working.
biothings-explorer-trapi:qedge2btedge Filter criteria is: {"input_type":"Disease","output_type":"ChemicalSubstance","predicate":"treats"} +0ms
biothings-explorer-trapi:qedge2btedge Filter criteria is: {"input_type":"Disease","output_type":"ChemicalSubstance","predicate":"contraindicated_for"} +44ms

contraindicated_by => contraindicated_for: currently fixed in MyChem.info SmartAPI

The real problem is that we don't reverse the predicate.
it should be Disease => treated_by => ChemicalSubstance.
Need to implement edge reversal in BTE.

#33 look for symmetric predicate from biolink model
#29 look for reverse predicate from biolink model

Fixed in: https://github.com/biothings/BioThings_Explorer_TRAPI/pull/37/commits/a1673454c396b196c1d6970a65fe67468802e057 for #33
Fixed in: https://github.com/biothings/BioThings_Explorer_TRAPI/pull/30/commits/862560daa9da0005dd85fdd5612e72ce5364e0f4 for #29


Add markdown styling

Description of the feature

Added all the required options & tools that's present in Markdown Styling so that any non-tech user's can write blogs with ease.
Added extra plugin for uploading any image at any position of the Blog.
Added extra plugin for the category of Coding Blog-Posts with syntax highlighting feature.

Additional Changes[Fixes]

Fixed the position and spacing of the buttons of Pagination.
Fixed a minor error which caused while updating any particular Posts.
Fixed the position issue of the View Count & Read Time which was not being displayed inline.

Fixes: #136
GIF

Hello @Kajol-Kumari , Can you review this, and let me know the changes, if any I have to make for this PR to get merged.

One additional note @ManishShah120 Please avoid doing changes other than required for resolving the assigned issue in a single PR. Kike I can see many changes including comment modification, pagination count change etc. It's good practice to open up a new PR for such enhacements or changes other than those required by the related issue.

@Kajol-Kumari , I have removed the jpg's, which could be removed.

One additional note @ManishShah120 Please avoid doing changes other than required for resolving the assigned issue in a single PR. Like I can see many changes including comment modification, pagination count change etc. It's good practice to open up a new PR for such enhacements or changes other than those required by the related issue.

Okay, I will definitely take care of these from next time.

@ManishShah120 I can still see gifs and jpg files in the PR. Ifthey are not require, please remove them.

_icons.png, icons_hidpi.png, dialog_sides.gif, dialog_sides.png, dialog_sides_rtl.png, mini.gif, spinner.gif, sprites.png, sprites_ie6.png, toolbar_start.gif_
Hey @Kajol-Kumari, If you are requesting to remove the above files, then this files can't be removed because these are the icons, of the ckeditor toolbar, Though If I refresh the page after deleting all these files then the positions of these icons blanks out. Except these files, I am not able to figure out any other images/gif's that you are requesting me to remove.

Hey @Kajol-Kumari, some of the present changes from the upstream repo are creating an issue in the home page UI beacuase of  some of the repetitive line of codes, due to which the home page is not loading. Can I solve that problem, because without solving these issue I will not be able to resolve the conflicts, or should I wait for this #151  PR to get merged.

@ManishShah120 please wait for the PR #151 to be merged.

@ManishShah120 please resolve the conflicts now so that It can be merged.

@Kajol-Kumari, Done please have a look.


Fix #511: Only execute completion requests if LS supports it

Issue: We always ask for completions.. even if the language server doesn't support it. This causes unnecessary errors.
Fix: Use the completion provider capability to check before executing the request.

Fixes #511


feat: add vim-like keymaps and other ideas

Hello again,
I have a suggestion to add. Add vim-like keymaps to be able to delete clipboards contents.
For example :

hjkl for navigation between clipboards contents instead of fuzzy find ( h for left, l for right, k for up and j for down)
/{cmd} to fuzzy-find through the clipboards contents, accept regex expressions too
d will delete the line (without copying it like in vim) of the clipboard content the cursor is in
keymap to delete the whole clipboard history with a confirm popup like
y will copy the clipboard content the cursor is in to use it outside the clipboard manager
clipboard contents are read-only to avoid conflicts
ability to configure a color-background to determine the actual line we are in ( where the cursor is in )

you can get some inspiration from a neovim / vim plugin where we can adopt some similarities for a completely fully functionnal clipboard manager, here's the link
Hope it helps,
Thanks,
Yushi

Thanks for the issue. Since clapboard doesn't have it's own interface, but instead instead it use's the launcher of your choice, I do not see how this can ever be implemented (unless we create a Clapboard-specific launcher, which seems like an overkill).

Hello, maybe the commands used to store clapboard contents can be used to wipe clapboard etc

Closing this issue as it seems out of scope of Clapboard.


Build failed for iOS

What happened?
[17/389] Generating llvm-cpu_command_buffer_dispatch_test.bin from command_buffer_dispatch_test.mlir
FAILED: runtime/src/iree/hal/drivers/local_task/cts/llvm-cpu_command_buffer_dispatch_test.bin /Users/y/w/iree-ios/iree-runtime-build/ios-sim/runtime/src/iree/hal/drivers/local_task/cts/llvm-cpu_command_buffer_dispatch_test.bin
cd /Users/y/w/iree-ios/iree-runtime-build/ios-sim/runtime/src/iree/hal/drivers/local_task/cts && /Users/y/w/iree-ios/iree-build/install/bin/iree-compile --output-format=vm-bytecode --compile-mode=hal-executable --iree-hal-target-backends=llvm-cpu /Users/y/w/iree-ios/iree/runtime/src/iree/hal/cts/testdata/command_buffer_dispatch_test.mlir -o llvm-cpu_command_buffer_dispatch_test.bin --iree-hal-executable-object-search-path=\"/Users/y/w/iree-ios/iree-runtime-build/ios-sim\"
/Users/y/w/iree-ios/iree/runtime/src/iree/hal/cts/testdata/command_buffer_dispatch_test.mlir:25:94: error: expected ':'
      %0 = hal.interface.binding.subspan set(0) binding(0) type(storage_buffer) alignment(32) offset(%c0) : !flow.dispatch.tensor<readonly:f32>
                                                                                ^

Steps to reproduce your issue

git pull upstream main && git submodule update
Follow steps in https://iree-org.github.io/iree/building-from-source/ios

The above error appears at the building of the IREE runtime for the iOS Simulator.
What component(s) does this issue relate to?
Runtime
Version information
9242287e7cca1eab8ab08f4f9f9a52c4cbf91c66
Additional context
macOS: 13.1 (22C65)
Xcode: Version 14.2 (14C18)

The errored code snippet is
https://github.com/iree-org/iree/blob/c170ca3d2396eaa7e68e5a8b7a0f33dbef37d21b/runtime/src/iree/hal/cts/testdata/command_buffer_dispatch_test.mlir#L25-L26

Looks like you'll need to rebuild the compiler tools (in your host build). If you've already rebuilt the compiler tools and still see that error, clean your build directory (https://github.com/iree-org/iree/issues/11331 might be affecting you too)


Integrating Translation-helps, bible reference and workspace rcl inside Autographa

Integrating Translation-helps, bible reference and workspace RCL inside Autographa with necessary UI/UX changes.

above mentioned things are visible in the editor page(3page), hence moving this to done.
attaching the screenshot for the same.


Phone Number Validation

Check that the number is valid before accepting new user (acceptable dialing code, no plus, sufficient number of digits, etc).  Maybe there is some library that already provides this

Like this https://github.com/stefanfoulis/django-phonenumber-field


Export a data map using fides resources

Closes #324
Code Changes

[x] Use the provided example to generate output for the Organization resource as a csv
[x] Create a new CLI command to export a data map
[x] Use the provided example to build the "walk-state" output of a data map formatted for Excel
[x] Ensure all components of the datamap can be separately exported as csv

Steps to Confirm

[x] Data output aligns with vision laid out in example data map / RoPA
[x] Change to upsert functionality aligns with expectations of existing cli commands

Pre-Merge Checklist

[x] All CI Pipelines Succeeded
[x] Documentation Updated

Description Of Changes
This PR is focused on exporting the combined resources as a data map.
To test out the functionality, you should be able to do the following:
make cli
fidesctl apply demo_resources
fidesctl export datamap demo_resources

Additionally, the following flags can be applied to not use the excel format:
fidesctl export datamap demo_resources --csv
fidesctl export datamap demo_resources --dry
As well as having a separate command to output the organization resource separately as csv (all in support of those that do not want the formatted .xlsx)
fidesctl export organization demo_resources
The exported datamap is currently sent to the same directory housing the resource manifests where it can be viewed. This will likely need to be changed (or have a flag added) when ready to have this available for download from a fides UI.
Due to the output formatting, an Excel output was chosen (.xlsx) and uses a static copy of the form we were provided.
Attributes that are either yet to be modeled (or still to be exported properly as of writing) are either left blank or marked as N/A
Do we want to add another guide to the docs for exporting resources? I could go either way here, I think so but I also think it might be a bit light at this point and could possibly wait for the next release on the run state 🤷🏽

@iamkelllly I am still going to be cleaning up a few things and sorting through docs but would love to get your thoughts on how this is working so far 🙌🏽

@iamkelllly I am still going to be cleaning up a few things and sorting through docs but would love to get your thoughts on how this is working so far 🙌🏽

Feedback captured via slack and addressed in here (fix issues with xlsx template, third country support). Joint controller only remaining gap, thinking about deferring until run state until we get more information

LGTM! Had a suggestion as a small nit and would also recommend breaking out the export.py file, running up on 500 lines starts to get a bit unwieldy but these are non-blocking nits :)

Thanks for the review @ThomasLaPiana ! all updates made, split out the extras into an export_helpers.py (unsure on name but easy to change if we want)

@SteveDMurphy LGTM, merge when ready!


Get firebase database versionCode

Need to use at validating JSON versions and app update notifications

Need to have additional support for official releases and beta releases

extended from the issue #172

oh yeah? #175


CLI Hand Off

Repo Here
build pipeline Here

[x] Migrate source  to machinelearning-tools repo and solution
[x] Migrate build to MicroBuild
[ ] Pull out CodeGen into shared library
[ ] Update ModelBuilder to use CodeGen Library
[ ] Consider: Creating extensible command line In MLNet repo
[ ] Rename new command to AutoTrain
[ ] Try to get rid of hard coded catalog (cross team effort with ML.NET and AutoML.NET)
[ ] Transfer issues from CLI repo to this repo

Going to work on "Migrate source to machinelearning-tools repo and solution" and "Migrate build to MicroBuild"

on task 3, maybe a better way is to create public interface to code generator and add reference to mlnet in model builder, due to the fact that code generator is so cohesive with cli.
any suggestion? @JakeRadMSFT @tbombach

Going to work on task 3 and 4 now

Please hold off until we discuss where CLI and ModelBuilder lives going forward.


Show display name instead of first name

Was there any context for this request?

Iirc there is a displayName attribute provided from our idp, which can be used by people who don't go by their legal first name.


broken pipeline error in distributed mode

OrientDB Version: 3.0.0-SNAPSHOT
Java Version: 1.8
OS: CentOS
I run a distributed ODB cluster. After a while, I find below message on node0 and I can't insert any data
+----------+------+----------------------+-----+---------+-----------------+-----------------+------------------------+
|Name      |Status|Databases             |Conns|StartedOn|Binary           |HTTP             |UsedMemory              |
+----------+------+----------------------+-----+---------+-----------------+-----------------+------------------------+
|odb0(*)(@)|ONLINE|poc_zy=ONLINE (MASTER)|89   |18:20:23 |<IP_ADDRESS>:2424|<IP_ADDRESS>:2480|807.59MB/3.98GB (19.84%)|
|          |      |demodb=ONLINE (MASTER)|     |         |                 |                 |                        |
|odb4      |ONLINE|poc_zy=ONLINE (MASTER)|8    |18:22:58 |<IP_ADDRESS>:2424|<IP_ADDRESS>:2480|628.61MB/4.00GB (15.35%)|
|          |      |demodb=ONLINE (MASTER)|     |         |                 |                 |                        |
|odb3      |ONLINE|poc_zy=ONLINE (MASTER)|8    |18:22:30 |<IP_ADDRESS>:2424|<IP_ADDRESS>:2480|1.16GB/3.99GB (29.05%)  |
|          |      |demodb=ONLINE (MASTER)|     |         |                 |                 |                        |
|odb2      |ONLINE|poc_zy=ONLINE (MASTER)|8    |18:21:57 |<IP_ADDRESS>:2424|<IP_ADDRESS>:2480|739.24MB/3.99GB (18.11%)|
|          |      |demodb=ONLINE (MASTER)|     |         |                 |                 |                        |
|odb1      |ONLINE|poc_zy=ONLINE (MASTER)|8    |18:20:41 |<IP_ADDRESS>:2424|<IP_ADDRESS>:2480|921.18MB/3.99GB (22.57%)|
|          |      |demodb=ONLINE (MASTER)|     |         |                 |                 |                        |
+----------+------+----------------------+-----+---------+-----------------+-----------------+------------------------+

2018-01-10 19:20:53:523 WARNI I/O Error on distributed channel  clientId=5 reqType=120
2018-01-10 19:21:33:533 WARNI [odb0]->[odb1] Error on sending message to distributed node (java.net.SocketException: Broken Pipeline (Write failed)) retrying (1/3)
2018-01-10 19:22:13:515 WARNI I/O Error on distributed channel  clientId=7 reqType=120
2018-01-10 19:22:43:425 WARNI I/O Error on distributed channel  clientId=9 reqType=120
2018-01-10 19:22:53:531 WARNI [odb0]->[odb2] Error on sending message to distributed node (java.net.SocketException: Broken Pipeline (Write failed)) retrying (1/3)
2018-01-10 19:23:08:465 WARNI I/O Error on distributed channel  clientId=11 reqType=120
2018-01-10 19:23:23:441 WARNI [odb0]->[odb3] Error on sending message to distributed node (java.net.SocketException: Broken Pipeline (Write failed)) retrying (1/3)
2018-01-10 19:23:48:489 WARNI [odb0]->[odb4] Error on sending message to distributed node (java.net.SocketException: Broken Pipeline (Write failed)) retrying (1/3)
2018-01-10 20:06:29:042 WARNI [odb0]->[odb1] Error on sending message to distributed node (java.net.SocketException: Broken Pipeline (Write failed)) retrying (1/3)
2018-01-10 20:06:29:044 WARNI [odb0]->[odb2] Error on sending message to distributed node (java.net.SocketException: Broken Pipeline (Write failed)) retrying (1/3)
2018-01-10 20:06:29:045 WARNI [odb0]->[odb3] Error on sending message to distributed node (java.net.SocketException: Broken Pipeline (Write failed)) retrying (1/3)
2018-01-10 20:06:29:141 WARNI I/O Error on distributed channel  clientId=6 reqType=121
2018-01-10 20:06:29:141 WARNI I/O Error on distributed channel  clientId=8 reqType=121
2018-01-10 20:06:29:142 WARNI I/O Error on distributed channel  clientId=10 reqType=121

The same messages can be found on other nodes, below messages are found on node1:
2018-01-10 19:21:03:519 WARNI [odb1]->[odb0] Server 'odb0' did not respond to the gossip message (db=poc_zy, timeout=10000ms), but cannot be set OFFLINE by configuration
2018-01-10 19:21:13:520 WARNI [odb1]->[odb0] Server 'odb0' did not respond to the gossip message (db=demodb, timeout=10000ms), but cannot be set OFFLINE by configuration
2018-01-10 19:21:13:522 WARNI [odb1]->[odb0] Error on sending message to distributed node (java.net.SocketException: broken pipline (Write failed)) retrying (1/3)
2018-01-10 19:21:13:525 WARNI I/O Error on distributed channel  clientId=4 reqType=121
2018-01-10 19:21:23:525 WARNI [odb1]->[odb0] Server 'odb0' did not respond to the gossip message (db=poc_zy, timeout=10000ms), but cannot be set OFFLINE by configuration
2018-01-10 19:21:33:526 WARNI [odb1]->[odb0] Server 'odb0' did not respond to the gossip message (db=demodb, timeout=10000ms), but cannot be set OFFLINE by configuration
2018-01-10 19:22:13:511 WARNI I/O Error on distributed channel  clientId=5 reqType=120
2018-01-10 19:22:23:529 WARNI [odb1]->[odb2] Server 'odb2' did not respond to the gossip message (db=poc_zy, timeout=10000ms), but cannot be set OFFLINE by configuration
2018-01-10 19:22:33:529 WARNI [odb1]->[odb2] Server 'odb2' did not respond to the gossip message (db=demodb, timeout=10000ms), but cannot be set OFFLINE by configuration
2018-01-10 19:22:33:531 WARNI [odb1]->[odb2] Error on sending message to distributed node (java.net.SocketException: broken pipline (Write failed)) retrying (1/3)
2018-01-10 19:22:33:534 WARNI I/O Error on distributed channel  clientId=6 reqType=121
2018-01-10 19:22:43:422 WARNI I/O Error on distributed channel  clientId=7 reqType=120
2018-01-10 19:22:43:533 WARNI [odb1]->[odb2] Server 'odb2' did not respond to the gossip message (db=poc_zy, timeout=10000ms), but cannot be set OFFLINE by configuration
2018-01-10 19:22:53:528 WARNI [odb1]->[odb2] Error on sending message to distributed node (java.net.SocketException: broken pipline (Write failed)) retrying (1/3)
2018-01-10 19:22:53:536 WARNI [odb1]->[odb3] Server 'odb3' did not respond to the gossip message (db=demodb, timeout=10000ms), but cannot be set OFFLINE by configuration
2018-01-10 19:22:53:536 WARNI [odb1]->[odb2] Server 'odb2' did not respond to the gossip message (db=demodb, timeout=10000ms), but cannot be set OFFLINE by configuration
2018-01-10 19:23:03:540 WARNI [odb1]->[odb3] Server 'odb3' did not respond to the gossip message (db=poc_zy, timeout=10000ms), but cannot be set OFFLINE by configuration
2018-01-10 19:23:03:541 WARNI [odb1]->[odb3] Error on sending message to distributed node (java.net.SocketException: broken pipline (Write failed)) retrying (1/3)
2018-01-10 19:23:03:543 WARNI I/O Error on distributed channel  clientId=8 reqType=121
2018-01-10 19:23:08:461 WARNI I/O Error on distributed channel  clientId=9 reqType=120

But I can create a new Class and insert data to this new Class.

Hi @weickdev
Do you have all the shards in the all of your servers?

The same issue.


pin the SDK version in global.json

I'll update the tag as well when this merges. I verified that this fixes the issue on my local build. I wanted to get this one done and in before blasting something out to all the other repos.
/cc @pranavkm @Eilon

Note: This is intentionally targeted at master

Once appveyor and Travis-linux builds pass (Travis-mac is stuck on ye olde OpenSSL issue), to verify the KoreBuild change was picked up. I'll merge this and update the tag