[Enhancement] Revise the num_classes logic in basic conditional gan

Codecov Report

Merging #69 (3b21656) into master (24dfdc6) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #69      +/-   ##
==========================================
+ Coverage   75.97%   76.00%   +0.02%
==========================================
  Files         117      117
  Lines        7675     7675
  Branches     1409     1409
==========================================
+ Hits         5831     5833       +2
+ Misses       1468     1467       -1
+ Partials      376      375       -1

Flag
Coverage Δ

unittests
76.00% <100.00%> (+0.02%)
:arrow_up:

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

Impacted Files
Coverage Δ

mmgen/models/gans/basic_conditional_gan.py
52.51% <100.00%> (ø)

...chitectures/stylegan/generator_discriminator_v1.py
89.83% <0.00%> (ø)

...chitectures/stylegan/generator_discriminator_v2.py
87.77% <0.00%> (+1.11%)
:arrow_up:

Continue to review full report at Codecov.

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


Inability to type next to or past custom Embed blot (with contenteditable=false)

I am trying to create a custom Embed blot that will allow our users to mention other users (a la GitHub), however treat the entire username as a single entity (hence why I am using Embed and not Inline) so that if a user backspaces in front of it, it deletes the entire user name and not just a single character of it.
While I am able to correctly create the UserMention embed in a Quill document, it causes a multitude of problems with cursor positioning, selection states, and the ability to type, especially if the UserMention embed is at the end of a document.
Steps for Reproduction

Visit http://codepen.io/anon/pen/dOKqEN
Try to move cursor past UserMention embed by using both arrow keys and clicking past it (two different errors occur)

Expected behavior:
User should be able to type content before or after UserMention embed blot
Actual behavior:
If moving cursor by touching arrow keys, cursor will get stuck when trying to move next to or past UserMention blot. Cursor will also sometimes disappear. Rarely, it's possible to actually have two cursors visible at once.
Additionally on<EMAIL_ADDRESS>Try to move the cursor past the UserMention blot will cause the editor window to scroll jump well past the content
Platforms:
Latest Chrome OSX
Version:
1.1.6 (also occurs on 1.1.5)

Its not a quilljs bug, its browsers failure. All current browsers having different issues handling contenteditable="false" nodes inside in contenteditable="true" container.
In our project we developed similar functionality (custom blocks and nodes which users cannot edit inside of quilljs) and those cursor and selection problems driven me nuts.
Some kind of solution we used - tracking of cursor position. If cursor found in bugged area (in general: before first non-editable in line, after last non-editable in line, between two non-editables) insert there quilljs cursor blot or another zero-width filler node.

@cutteroid thanks for pointing me in the right direction. Good to know that I may have to solve these issues myself and then back port them into Quill.
Any chance you have an example of how you've handled issues like the one i'm describing? Still wrapping my head around the beast that is contenteditable and any examples would be much appreciated.

@danielschwartz
example
Beware! It is a big pile of shitcode written with "it's only a prototype. will rewrite it later" in mind :)

@cutteroid good to know :). I'm sure it will be useful either way. Really appreciate you helping shed some light on all these selection issues!

@danielschwartz I've encountered the same issue, hopefully, there's a workaround :)
Basically, the problem is that when you add text right after (and sometimes right before) a blot, you are not editing the block next to the blot but the blot itself (which you marked as readonly).
e.g.
Where "it seems" the cursor is:

Here is my read only blot|

Where the cursor actually is:

Here is my read only blot|

I couldn't get the contenteditable=false approach working, it turned out to be a bit difficult to handle in some cases, and, most important for my use case, it produces different behaviors on different platforms.
What I had to do to workaround this problem is to leverage the update function of the blot and handle prepends (typing right before the blot), appends (typing right after the blot), and text replacements (like using spell suggestions on the phone or Ctrl+Backspace deleting words) with different code.
Basically, instead of using a non-editable Blot I created a sort of immutable one.
Here you have a working example: http://codepen.io/ivanalejandro0/pen/LbyNYW , it is a big portion of the code I'm using which includes handling of several edge cases. I hope this is useful for you.

@cutteroid I have also ran into the issue. In the past (with CKEditor) I have just inserted a zero width space after the blob () to fix the issues. This actually worked quite well!
Do you think it would be possible to insert a zero width space  if the cursor is exactly after or before the blob?

@Wattos how were you able to insert a zero width space after a blob?

This has been fixed in 1.3.0.

@jhchen Are you sure this is fixed? I updated the example to Quill 1.3.0 and it still exhibits the same behaviour. I can't use the arrow keys to move past the EmbedBlot and then start typing.
https://codepen.io/anon/pen/MoMrva

I too am using 1.3.0 and am still experiencing this issue.
I don't know if this is of use to anyone but the workaround that I am using is adding an additional space after the embed and then setting the current selection to be after that space.
const range = editor.getSelection();
editor.insertEmbed(range.index, 'shortcode', `{{ $${val} }}`);
editor.insertText(range.index + 1, ' ');
editor.setSelection(range.index + 2, Quill.sources.SILENT);

It is fixed with a new InlineEmbed blot but the default export is still Embed: https://github.com/quilljs/quill/blob/develop/blots/embed.js. I'll switch this over but in the meantime if you build Quill you can import InlineEmbed instead.
To observe the fixed behavior take a look at formula on the homepage of https://quilljs.com. It used to use the space workaround like @BrockReece suggested but should not be necessary anymore.

Is there a way to use InlineEmbed with the npm module now?

InlineEmbed will be converted to the default Embed as soon as 1.3.1 is released (commit is already in develop).

Hey, @jhchen I'm facing a similar problem here in 1.3.2. I tried running the example code that @danielschwartz provided running the latest version of Quill and I noticed that it's also showing the same issue as described in the ticket. Would you have any words of wisdom of how the example could be fixed?
Here's my fork running on 1.3.2
https://codepen.io/brianbest/pen/mBEGQV

The setting contenteditable to false needs to be removed in create(). The native embed already has sets the contents to be contenteditable to false and this additional call is defeating the cursor workaround the fix added.

Boom! That's great thank you @jhchen !

@ivanalejandro0 I appreciate the example. Any idea how you would go about replicating your example for ^1.3.5, it doesn't seem to work with the latest version.

@petahbred yeah, I've forked my previous example into a new one that works with the current latest quill version (1.3.6 as today).
https://codepen.io/ivanalejandro0/pen/GdOBjQ
Some caveats:

it works differently than the previous one, there's no blot to text conversion since that was part of the workaround of the blot not being immutable previously.
the code is much shorter since there's no longer need to handle blot mutations thanks to the new non editable blot and the "guards" around it that handles changes.
there's a workaround on the update() function to handle an android bug using gboard (I think it could be #1985)

@danielschwartz
example
Beware! It is a big pile of shitcode written with "it's only a prototype. will rewrite it later" in mind :)

@cutteroid Excuse me? What is zEditor.fixCaret()?

@ivanalejandro0 thank you very much for sharing!

Why is this issue closed? It is not resolved, besides workaround created by @ivanalejandro0

需要在 create() 中删除将 contenteditable 设置为 false。本机嵌入已将 contenteditable 的内容设置为 false，并且此额外调用使修复程序添加的修复方法无效。

Hi,@jhchen I followed what you said and made modifications based on the code of @Brianbest. Indeed, the cursor displayed normally and could be entered, but when I entered a word after Blots, the first letter would appear twice, for example:
Didn't anyone else encounter this problem？

https://github.com/slab/quill/issues/1904

#1094

#1904 same issue


Training Code

Hi,
Congratulations for the great work! Can you provide the google colab python notebook file as well which you used for training the model?
Thanks

Thanks, but unfortunately I don't have access to it anymore (the student graduated)


Add latest RALI changes

@LokeshBonta can you sync this with TOT master. This PR is removing the changes which we have made.

@LokeshBonta can you also check on LGTM Warnings

@LokeshBonta this PR fails build test. check Travis
[ 98%] Building CXX object rali/CMakeFiles/rali.dir/source/reader_factory.cpp.o
1430In file included from /MIVisionX/rali/./include/tf_record_reader.h:11:0,
1431                 from /MIVisionX/rali/source/reader_factory.cpp:4:
1432/MIVisionX/rali/./tf/example.pb.h:10:10: fatal error: google/protobuf/port_def.inc: No such file or directory
1433 #include <google/protobuf/port_def.inc>
1434          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1435compilation terminated.
1436rali/CMakeFiles/rali.dir/build.make:1694: recipe for target 'rali/CMakeFiles/rali.dir/source/reader_factory.cpp.o' failed
1437make[2]: *** [rali/CMakeFiles/rali.dir/source/reader_factory.cpp.o] Error 1
1438CMakeFiles/Makefile2:844: recipe for target 'rali/CMakeFiles/rali.dir/all' failed
1439make[1]: *** [rali/CMakeFiles/rali.dir/all] Error 2
1440Makefile:151: recipe for target 'all' failed
1441make: *** [all] Error 2

@kiritigowda
The pb files we use from tensorflow requires protobuf version 3.11.4
That is why we have included that in the Readme.md

LGTM warning have been resolved now with the latest commit

@kiritigowda
The pb files we use from tensorflow requires protobuf version 3.11.4
That is why we have included that in the Readme.md
Can we change the default installation to 3.11.4?

@LakshmiKumar23 can we check if the protobuf version is set to 3.11.4 MIVisionX can still build? @LokeshBonta

@kiritigowda MIVisionX builds with libprotoc 3.11.4.

 I just saw that your master is 19 commits behind the TOT master.

Hi
@kiritigowda @rrawther
I will create another pull request with some other modifications which we talked about in the call
Please let me know if it is okay to close the pull request.

@LokeshBonta yes, we can close this PR. I will close this PR and you can open another with the changes.


[Data] Create csv of daily reports across countries

Have a list that can be updated daily with updated cases.

Useful for visualisation
Useful for situational awareness.

You can use the WHO situational reports (linked in /data/) to assist. How do we automatically extract from situational reports pdfs?

Do you mean extracting the data from the WHO situational reports (pdf) and saving it in CSV format? I think I can help with this issue.

How do you want us to proceed to add the data for the countries we've assigned to ourselves? Do we duplicate the line-list-africa.csv file in the repo and rename it to the country of our choosing, for e.g., line-list-ghana.csv? I'm not sure the instructions are clear.

@jamesmbaazam for the line lists, yes.


How to Explide domain from operation??

Let's say I have multiple sub domains an I have this rule:
pagespeed Domain *.example.org;
But the problem is that one of the subdomains I would like to exclude for example images.example.org (this domain is on external CDN, like Amazon)
Is there something like:
pagespeed DomainExlude *.example.org;
?

There's https://developers.google.com/speed/pagespeed/module/restricting_urls
For example, you could configure:
pagespeed Disallow "http://images.example.com*"

Note that in general you don't need to set Domain manually.  If you're running a site on www.example.com then PageSpeed will assume it has permission to modify anything on www.example.com.  You only need Domain if you want www.example.com to be willing to rewrite a.example.com, b.example.com etc.

But I am running a website with lots of sub domains and sub-sub domains so this is something that is important to me.

Let's say you want to allow pagespeed to optimize resources on all subdomains of example.org except images.example.org and scripts.example.org.  Then you can use Otto's suggestion:
pagespeed Domain *.example.org;
pagespeed Disallow "http://images.example.org*";
pagespeed Disallow "http:/sscripts.example.org*";

But will this work for sub-subdomains?
For example:
I have domains:
en.example.com
a.en.example.com
b.en.example.com
c.en.example.com
And I would like to exclude images.en.example.com
Will this work?

Yes, that should work for subdomans:
pagespeed Domain *.example.com;
pagespeed Disallow "http://images.en.example.com*";


ARM/ARM64 split - part 1

Some important points:

To have this passing on CI we need to have https://github.com/zephyrproject-rtos/sdk-ng/pull/325 merged and actively used by CI
This is going to fail on checkpatch because it is going to recheck all the moved code so we are catching all the past warnings, etc...
This is going to conflict often
This PR is only for the AArch64 part. When this is merged I will post another PR taking care of the AArch32 part.
It was a bit more painful than expected but I also think this is necessary

Closes #32741

Is the aarch32 removal needed in this PR? Agree it should be done, but wondering about splitting it out into its own PR?

Not strictly needed (this is why I have it in a separate commit). But I can split the PRs for the sake of simplicity.

Not strictly needed (this is why I have it in a separate commit). But I can split the PRs for the sake of simplicity.

Just thinking to get arm64 split merged to limit this PR as much as possible, and than have followup cleanup PRs would make it quicker to get merged.

Just thinking to get arm64 split merged to limit this PR as much as possible, and than have followup cleanup PRs would make it quicker to get merged.

No objections. I'll use this PR only for the AArch64 part and once this is merged I can push the remaining part.

No objections. I'll use this PR only for the AArch64 part and once this is merged I can push the remaining part.

+1

Alright, I split the PRs. This PR is now only concerning the AArch64 separation.

It feels like the broadcom SoC/board stuff might be useful to have in its own commit since I feel like the split going on there between arm64/arm isn't a straight forward move.

It feels like the broadcom SoC/board stuff might be useful to have in its own commit since I feel like the split going on there between arm64/arm isn't a straight forward move.

That is going to break bisectability for the Broadcom board though.

That is going to break bisectability for the Broadcom board though.

At least maybe call out what's happening in the commit message for the broadcom board/soc.

@Abhishek-brcm @sandeepbrcm about the bcm_vk/viper split it would be nice to have your review as well.

@galak there is a way to use zephyrproject-rtos/sdk-ng#325 for CI already?

The compliance test is failing as usual on the typedefs, so that's bogus as usual.


Use PTY for test output redirect.

Scope & Purpose
This allows us to have colored output in CircleCI.

[x] :pizza: New feature

Does this change affect Jenkins at all? should a jenkins run be done to make sure that nothing breaks?

No, Jenkins is completely unaffected by this change.


[bounty] $100 make it possible to update remotely installed pipe

use case annoying i faced:

install pipe from an URL
i updated the pipe in the repo
couldn't find a way to update to new version

this works well with local code pipe which shows reload button
/bounty 100
plz suggest the UX first before implementing so i confirm it's what we want

i'll take a look!

@louis030195 what about a update button here?

implementation:
update button, will reinstall the pipe

this function is able to update remote pipe
https://github.com/mediar-ai/screenpipe/blob/6b9a1083c0389ee5bdc92ed4ec2bc408650726e8/screenpipe-app-tauri/components/pipe-store.tsx#L660
https://github.com/user-attachments/assets/0bb5b06e-d4a5-4f6e-a1d3-73e512e4d10f

when pipe installation fails it creates a .temp folder, fixing it

@louis030195
updating a pipe is just reinstalling, also most of pipes are now next js and reinstalling a pipe will not override the pipe.json file. so this function seems okay for this
https://github.com/mediar-ai/screenpipe/blob/1249de1a5078cde642c7d3609f42e113e2d35c79/screenpipe-app-tauri/components/pipe-store.tsx#L949
what do you think?

i wonder how obsidian store does it, their versionning

i wonder how obsidian store does it, their versionning

https://github.com/obsidianmd/obsidian-sample-plugin.git
https://github.com/elias-sundqvist/obsidian-annotator.git
most of obsidian plugins are git repo, i guess they handle versioning by adding these files

manifest.json which is equivalent to pipe.json
versions.json a fallback of manifest.json

also versioning can be handle from github releases if pipes are git repo.
while in screenpipe, right the now all the plugins are as a directory in git repo, if you'd create separate repo for all plugins the it'd be easier for installing and maintaining the pipe version

so i think we can pull version from package.json or commit
related
#1006
for now i'll just add a button that do delete+redownload but we could have a button check for update + update if any in the future like obsidian does


Port BadgeOverlay from Storefront

Component Name
BadgeOverlay
Overview / Summary
Summary description of UI component
BadgeOverlay renders a div with a primary and secondary badge for the given product. Used for displaying whether the product is low inventory, a best-seller, sold out, etc.
Rationale for why this component is necessary
Needed for the porting of the storefront product grid to the component lib.
Expected use cases

Rendering badges in product grid
Rendering badge in PDP variant list

Images / Designs of UI component in context
Example of BadgeOverlay with a simple <img /> tag as the only child:

Data
Props
propTypes = {
    /**
     * The contents wrapped in the overlay, such as text, icons, or any combination of React and HTML components
     */
    children: PropTypes.node,
    /**
     * Only show badge if status is of a certain type
     * Types: BACKORDER, BESTSELLER, LOW_QUANTITY, SALE, SOLD_OUT
     */
    filterOnly: PropTypes.string,
    /**
     * The product, whose properties determine which badge(s) to display
     */
    product: PropTypes.shape({
      isSoldOut: PropTypes.bool,
      isBackorder: PropTypes.bool,
      isOnSale: PropTypes.bool,
      isLowQuantity: PropTypes.bool,
      isBestseller: PropTypes.bool
    }),
    /**
     * Whether to only display the primary badge
     */
    shouldShowPrimaryOnly: PropTypes.bool
  }

Data Fetching
None - all data comes from props
State Store
None
Routing / Query String
None
Breakpoints
Desktop, Tablet, Mobile
Renders full-width with a primary badge floated left, and a secondary badge floated right
UI States
Normal
Renders primary and secondary badge as mentioned above.
Sold out
Fades out div to 50% opacity if product is sold out

:tada: This issue has been resolved in version 0.20.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Set level: 3 in phpstan.neon.dist

NOTE: This repository is no longer supported or updated by @gomzyakov . If you wish to continue to develop this code yourself, we recommend you fork it.


Add the ability to add the -race flag to the local operator builder

Description of the change:
Add a command line option to enable building the local version of the operator with the -raceflag.
Motivation for the change:
When running the operator locally, I wanted to compile it with the -race flag to enable the runtime race detection.

@levigross I'm hesitant to add more go plumbing flags (see https://github.com/operator-framework/operator-sdk/pull/1600#issuecomment-506730405 for some background).
Would it be reasonable to just always include the -race flag in operator-sdk up local?

@joelanford Thank you for highlighting that issue and I hope that this PR doesn't exacerbate it.
I don't think we should always include -race when building the operator as there is a significant performance penalty when it is enabled.

I am in agreement that we shouldn't be adding more flags to wrapped go invocations. Moreover wouldn't -race be more amenable to being used with go test instead?

Hi @levigross,
Really thank you for your contribution.
Based on the following comments added by @estroz shows that we can be closing this one. However, please feel free to re-open if you think that it still required.

An extra flag is not needed. -race can be appended directly to GoCmdOptions.Args in the caller.

I am in agreement that we shouldn't be adding more flags to wrapped go invocations. Moreover wouldn't -race be more amenable to being used with go test instead?


feat: add dynamic theming

This adds the ability to change animation colors in runtime using lottie dynamic properties.

Closing this as theming is supposed to be handled natively in lottie-ios and lottie-android

This looks great (haven't tried it though). I don't understand why this isn't merged if it's working? If it's working it's better to have this possibility than to not have it (even though I guess @emilioicai means there's an even better solution).

@robertherber read the discussion linked above:
https://github.com/bradmartin/nativescript-lottie/pull/40
The notion of a theme does not exist in the parent libraries and should not have public api changes imposed upon them as the behaviour may change. Typically if you feel a need for the notion of a theme you would implement this in your own internal provider.


What is the purpose of the Getting started section in README?

In the README, the Getting started section only covers the Tests. Shouldn't we include a link to the tutorials?

It's a good idea to put a link to the tutorials. We also have the examples/ folder, which is messy, but I wanted to make the examples in google colab, and put links in the README to the most interesting examples/notebooks. What do you think?

The getting started section is still under construction

@omardrwch  I agree: we should have colab notebooks rather than python scripts, and redirect to them (in a structured way) in the getting started section of the doc.


Bug stomach

Currently, bugs instantly get the energy they need from food. In order to make some types of food more/less efficient than others, we need to introduce the concept of a stomach.

Input neuron, fullness.
Output neuron, digest.

Attributes include:

Food preference.
Base stomach size.

Digestion efficiency of plants and meat should each have their own curves.
Digestion efficiency should also depend on how active the neuron is. Constantly putting digest to 1 should have disadvantages.
Huge credit to the Bibites on this one: https://www.youtube.com/watch?v=kNWb7e8FZDo&t=927s

Stomach struct has digestion intensity, total plant matter, total meat matter, and max amount of matter. A stomach of size x should be able to hold more meat energy than plant energy as meat matter is more energy dense.
Adding more food of either type requires checking whether there is space.
Digestion intensity it set from the output neuron.
The digestion system draws energy from both types of matter. The amount will depend on the: intensity, fullness and food preference.
Some amount of the energy will be wasted and passed to the BurntEnergy struct.


There is a way to change the icon at the corner?

I want to eliminate that icon, i rather to don't have it

set showDismissButton=NO;


[BUG] compile error on alpine with raspberrypi 5

Describe the bug
Error installing alpine linux and building rpicam-apps on Raspberry Pi 5.
Bug report
The following commands are dependent on the installation of the builds:
apk add ffmpeg-dev boost-dev gnutls-dev tiff-dev meson cmake py3-yaml yaml-dev py3-ply glib-dev py3-pybind11-dev g++ python3-dev coreutils py3-pip py3-jinja2 libexif-dev libdrm-dev libpng-dev lttng-ust-dev libunwind-dev libudev-zero-dev elfutils-dev
git clone https://github.com/raspberrypi/rpicam-apps.git
cd rpicam-apps
CFLAGS="-mcpu=cortex-a76" CPPFLAGS="-mcpu=cortex-a76 -Wno-unused-parameter" meson setup build \
        --buildtype=release \
        -Denable_libav=enabled \
        -Denable_drm=enabled \
        -Denable_egl=disabled \
        -Denable_qt=disabled \
        -Denable_opencv=disabled \
        -Denable_tflite=disabled \
        -Db_lto=true && meson compile -C build

The error occurs :
ninja: job failed: c++ -Irpicam_app.so.1.5.1.p -I. -I.. -Icore -I/usr/local/include/libcamera -I/usr/include -I/usr/include/webp -I/usr/include/libpng16 -I/usr/include/libdrm -flto=auto -fdiagnostics-color=always -D_GLIBCXX_ASSERTIONS=1 -Wall -Winvalid-pch -Wextra -Wpedantic -Werror -std=c++17 -O3 -pedantic -Wno-unused-parameter -faligned-new -D_FILE_OFFSET_BITS=64 -Wno-psabi -ftree-vectorize -DLIBAV_PRESENT=1 -DLIBDRM_PRESENT=1 -mcpu=cortex-a76 -Wno-unused-parameter -fPIC -pthread -DBOOST_ALL_NO_LIB -MD -MQ rpicam_app.so.1.5.1.p/core_dma_heaps.cpp.o -MF rpicam_app.so.1.5.1.p/core_dma_heaps.cpp.o.d -o rpicam_app.so.1.5.1.p/core_dma_heaps.cpp.o -c ../core/dma_heaps.cpp
../core/dma_heaps.cpp: In member function 'libcamera::UniqueFD DmaHeap::alloc(const char*, std::size_t) const':
../core/dma_heaps.cpp:68:45: error: overflow in conversion from 'long unsigned int' to 'int' changes value from '3222816768' to '-1072150528' [-Werror=overflow]
   68 |         ret = ::ioctl(dmaHeapHandle_.get(), DMA_HEAP_IOCTL_ALLOC, &alloc);
      |                                             ^~~~~~~~~~~~~~~~~~~~

After adding -Wno-error=overflow to CPPFLAGS, the following error occurs:
ninja: job failed: c++  -o post_processing_stages/core-postproc.so post_processing_stages/core-postproc.so.p/hdr_stage.cpp.o post_processing_stages/core-postproc.so.p/motion_detect_stage.cpp.o post_processing_stages/core-postproc.so.p/negate_stage.cpp.o -Werror -flto -Wl,--as-needed -Wl,--allow-shlib-undefined -Wl,-O1 -shared -fPIC -mcpu=cortex-a76 -Wno-error=overflow -Wno-unused-parameter -Wl,-rpath,/usr/local/lib -Wl,-rpath-link,/usr/local/lib -Wl,--start-group /usr/local/lib/libcamera.so /usr/local/lib/libcamera-base.so -Wl,--end-group
In function 'copy',
    inlined from '__ct ' at /usr/include/c++/13.2.1/bits/basic_string.h:683:23,
    inlined from 'operator+' at /usr/include/c++/13.2.1/bits/basic_string.h:3690:43,
    inlined from 'get_value' at /usr/include/boost/property_tree/detail/ptree_implementation.hpp:671:9,
    inlined from 'get_value' at /usr/include/boost/property_tree/detail/ptree_implementation.hpp:680:31,
    inlined from 'get' at /usr/include/boost/property_tree/detail/ptree_implementation.hpp:752:69,
    inlined from 'Read' at ../post_processing_stages/hdr_stage.cpp:410:47:
/usr/include/c++/13.2.1/bits/char_traits.h:435:56: error: '__builtin_memcpy' writing 45 bytes into a region of size 16 overflows the destination [-Werror=stringop-overflow=]
  435 |         return static_cast<char_type*>(__builtin_memcpy(__s1, __s2, __n));
      |                                                        ^
/usr/include/boost/property_tree/detail/ptree_implementation.hpp: In member function 'Read':
/usr/include/boost/property_tree/detail/ptree_implementation.hpp:671:9: note: at offset 16 into destination object '<anonymous>' of size 32
  671 |         BOOST_PROPERTY_TREE_THROW(ptree_bad_data(
      |         ^
lto1: all warnings being treated as errors
lto-wrapper: fatal error: c++ returned 1 exit status
compilation terminated.
/usr/lib/gcc/aarch64-alpine-linux-musl/13.2.1/../../../../aarch64-alpine-linux-musl/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
lto-wrapper: warning: using serial compilation of 9 LTRANS jobs
lto-wrapper: note: see the '-flto' option documentation for more information

But adding -fno-inline to the CFLAGS and CPPFLAGS envs will not cause this error.
Alpine version: Linux localhost 6.6.41-0-rpi Alpine SMP PREEMPT Thu Jul 18 19:40:13 UTC 2024 aarch64 GNU/Linux

This looks to be an error in the Boost JSON parser, so not much we can do with the code there.  I suggest you keep the -fno-inline argument in your builds.  We will not be able to add it to our meson buildfiles due to possible performance impact.


Add methods for Application API

[x] def get_applications
[x] def get_application
[x] def create_application
[x] def update_application
[x] def delete_application

Added in 45f946d


question on infotype in send/recv function

Hi, I wonder if infotype in sendv() and recvv() must match?
For example, if I use SCTP_SEND_SNDINFO in sendv(), do I have to use SCTP_RECVV_RCVINFO in recvv()?  What if I use other infotype?
Does socket do memory copy in terms of *info?

These questions should be covered by the SCTP API Documentation [RFC6458].

What if I use other infotype?

It can fail (with an error return code), produce undefined behaviour or provoke a crash.

Does socket do memory copy in terms of *info?

If the question means whether you need to provide the memory for the info struct, then yes. Usually you'd just pass a reference from the stack as it doesn't require dynamic allocation.


Error in rake task for graphQL client in Ruby app: "rake aborted! Don't know how to build task"

Issue summary
I am a newbie to Ruby, so perhaps the fix is deadly simple. I am building a private Shopify app for my company which requires graphQL calls to the Admin API.
I am following this documentation (https://github.com/Shopify/shopify_api/blob/master/docs/graphql.md) to set up a graphQL client for the app. As per the documentation, I have made a Rakefile called Rakefile, as well as a shopify_graphql_schemas folder, in my root project folder.
When I run the private app rake command (with my api_key, password, and shop name, and current API version), I run into an error.
Expected behavior
When I run the private app rake command from the command line, a file called 2021-04.json should be created in /shopify_graphql_schemas, and I should be able to use the graphQL client to query the Admin API.
Actual behavior
I get the following error message, with trace:
rake aborted!
Don't know how to build task 'shopify_api:graphql:dump' (See the list of available tasks with rake --tasks)
C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/task_manager.rb:59:in []' C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:159:in invoke_task'
C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:116:in block (2 levels) in top_level' C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:116:in each'
C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:116:in block in top_level' C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:125:in run_with_threads'
C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:110:in top_level' C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:83:in block in run'
C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:186:in standard_exception_handling' C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/rake-13.0.3/lib/rake/application.rb:80:in run'
C:/Ruby27-x64/lib/ruby/gems/2.7.0/gems/rake-13.0.3/exe/rake:27:in <top (required)>' C:/Ruby27-x64/bin/rake:23:in load'
C:/Ruby27-x64/bin/rake:23:in `'
Steps to reproduce the problem

create a project folder with a simple app.rb which requires shopify_api and rake
add a Rakefile and a folder called shopify_graphql_schemas
from the command line, run:
rake shopify_api:graphql:dump<EMAIL_ADDRESS>API_VERSION=2021-04

Specifications

shopify_api version: 9.4.1
activeresource version: N/A
Shopify API version used: 2021-04

Can you share the output of bundle exec rake --tasks

Hi, thank you for your prompt response.
When I run that from my project folder, no response

Also no response when I run rake shopify_api:graphql:dump


After exporting, creature plugin for godot can't read .json data without copying files from res:// to user://

Godot version: 3.2.1-stable and 3.2.2-beta
OS/device including version: Windows
Issue description:
Everything works fine on editor, but after exporting it seems that the .json and .mdata can't be read. (Tested on windows .exe and web .html exports)
The only way to read them is to copy dir from res:// to user:// and then reference the files in user:// instead.
More detailed explanation:
https://github.com/kestrelm/Creature_Godot/issues/16#issuecomment-559658886
TLDR:

Did you specify *.json in the non-resource export filters in the Export dialog?

@MelimeliDev Please fill in the issue template when reporting bugs instead of replacing it.
Also, it would be appreciated if you could make a minimal reproduction project. Did you add *.json, *.mdata to the non-resource export filter? If so, maybe this is a bug in Godot (but I'm still not sure, as many people have gotten JSON exports to work).

Did you specify *.json in the non-resource export filters in the Export dialog?

Yes, that part is working fine because the .json files has been successfully copied from res:// to user://, they just can't be read/referenced from res://
Godot version has been added, and I don't have problems with reading .json files outside of this plugin. However, it seems that it's also a godot issue because the plugin works fine if files are read from user://

Also, it would be appreciated if you could upload a minimal reproduction project.

The godot that needs to be used is different (compiled with the plugin module) so I'm not sure how helpful it'd be, but any of the demo from the plugin github would do:
https://github.com/kestrelm/Creature_Godot/tree/master/creaturegodot3/Godot3Demo

Since it's C++ plugin it's probably using system file access API to read "*.json" (and globalize_path() to get full path).
If it is, it won't be able to do so, exported files do not exist in the host file system, but stored in the PCK archive.
Unless plugin is using GDNative FileAccess API to access files there's no straightforward way to mitigate this, in any other way than extracting file.

And looks like it is the case, plugin is using std::ifstream: https://github.com/kestrelm/Creature_Godot/blob/master/creaturegodot/CreatureModule.cpp#L657-L661
To read files from the PCK it should use something like (it's probably is not the only place in the plugin that should be changed):
#include <File.hpp>
...
	Ref<File> file;
	file.instance();
	if (file->open(filename.c_str(), File::READ) == Error::OK) {
		String data = file->get_as_text();
		std::string text(data.utf8().get_data());

		LoadCreatureJSONDataFromString(text, load_data);

		file.close();
	}

instead of:
	std::ifstream read_file;
        read_file.open(filename_in.c_str());
        std::stringstream str_stream;
        str_stream << read_file.rdbuf();
        read_file.close();

        LoadCreatureJSONDataFromString(str_stream.str(), load_data);

Thank you! I'll see if the plugin owner can fix this bug.

Related issue: #36781 and PR #37252.

It's solved! Thanks for the help!

It's solved! Thanks for the help!

Can you point the solution?


fix: prompt for update logic

With current version multiple clients get auto updated once the service worker receives the first update: with logic included on PR https://github.com/vite-pwa/vite-plugin-pwa/pull/394
With current changes, it is working properly, also tested on Firefox.
There are a few combinations using isUpdate and isExternal: these 2 flags from workbox-window are defined as boolean | undefined, when installed|activated events fired, undefined values have special meaning.
As an example, with only one client:

on first visit we receive isExternal: false with no isUpdate
on update, we receive isExternal: false and isUpdate: true and showSkipWaitingPrompt  being called from waiting event.

Problems comes when we have a few clients, for example, 2 tabs in first browser instance and another browser instance:
On first visit we receive isExternal: false with no isUpdate only in the first one client visiting the app, other clients will not receive the event
On update it is more complex, since we can have a few combinations, here the tests I've made with previous setup (building between tests):
Test 1:
Reloading app in tab1:

tab 1 receives isExternal: false and isUpdate: true
tab 2 receives isExternal: false with no isUpdate
second instance receives isExternal: false with no isUpdate

Click prompt reload button from tab1, all clients being updated, then build again.
Test 2:
Reloading browser instance 2:

tab 1 receives isExternal: false and isUpdate: true
tab 2 receives isExternal: false and isUpdate: true
second instance receives isExternal: false and isUpdate: true

Click prompt reload button from browser instance 2, all clients being updated, then build again.
Test 3:
Reloading browser instance 2:

tab 1 receives  isExternal: false with no isUpdate
tab 2 receives  isExternal: false with no isUpdate
second instance receives isExternal: false and isUpdate: true

Click prompt reload button from tab2 in browser instance 1, all clients being updated.
It seem on next update isExternal depends on the client that fires the update.

do not merge, I'm checking if we can switch event listener from installed to activated.

Master @antfu can you please review this PR? <3


chore: remove version from archive name

What kind of change does this PR introduce?
allows github release redirect
What is the new behavior?
eg. https://github.com/supabase/cli/releases/latest/download/supabase_1.27.10_checksums.txt
Additional context
Add any other context or screenshots.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3423

Relevant Lines:
5529

💛  - Coveralls


Migrate admission webhooks to v2 api

Why are we making this change?
Migrating admission webhooks to the new and improved v2 api!
What's changing?
Added config to allow consumers to trust the new v2 api

@dspigarelli good call. I think we should hop on a huddle and coordinate the release of these changes! @dylan-moradpour and I also have client changes that go along with this.


wrangler: command not found

Followed these installation steps on my mac:
npm i @cloudflare/wrangler -g
wrangler --help
wrangler: command not found

check if npm bin is added to PATH yet maybe?

Maybe related to #240

Hey thanks for reporting, are you still experiencing this problem?
How do you have node and npm installed?
Can you post the response from npm install -g @cloudflare/wrangler
Thanks!

the issue seems to be resolved by itself already.
i didnt do anything. it just works fine now
On Tue, Jul 9, 2019 at 8:41 PM Matt<EMAIL_ADDRESS>wrote:

Hey thanks for reporting, are you still experiencing this problem?
How do you have node and npm installed?
Can you post the response from npm install -g @cloudflare/wrangler
Thanks!
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/cloudflare/wrangler/issues/266?email_source=notifications&email_token=AAEZETQN6PBNKWHB7XH2GBLP6SIO3A5CNFSM4H2Z5ZQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZQJQYA#issuecomment-509646944,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEZETR6FHTTZCULM3XGMMDP6SIO3ANCNFSM4H2Z5ZQQ
.

If anyone is still experiencing this issue like I was, if you are using npm 5.2 or higher, try npx to run packages globally . I ran the following command, and it worked.
npx wrangler --help
Hope that helps!

For Mac users and for future reference: I've found that when installing npm packages globally, it takes a restart to register them so they're available for use.

This is still happening for me. Here is the entire log:
abhinab@abhinab-PC:~/git/os$ node -v
v14.13.1
abhinab@abhinab-PC:~/git/os$ npm -v
6.14.8
abhinab@abhinab-PC:~/git/os$ npx -v
6.14.8
abhinab@abhinab-PC:~/git/os$ npm install --save-dev @cloudflare/wrangler

><EMAIL_ADDRESS>postinstall /home/abhinab/git/mabsisa-os/node_modules/@cloudflare/wrangler
> node ./install-wrangler.js

Downloading release https://workers.cloudflare.com/get-npm-wrangler-binary/1.12.0/x86_64-unknown-linux-musl
wrangler has been installed!
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| >= 3.2.0-dev || >= 3.3.0-dev || >= 3.4.0-dev || >= 3.5.0-dev || >= 3.6.0-dev || >= 3.6.0-beta || >= 3.7.0-dev || >= 3.7.0-beta but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/chokidar/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/react-scripts/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})

+<EMAIL_ADDRESS>updated 1 package and audited 1942 packages in 30.481s

83 packages are looking for funding
  run `npm fund` for details

found 1 high severity vulnerability
  run `npm audit fix` to fix them, or `npm audit` for details
abhinab@abhinab-PC:~/git/os$ wrangler config
wrangler: command not found

I'm on Ubuntu 18. Can anyone let me kno what needs to be done in order to make it working?


ngclient: Don't use target path as local path

Doing so is not always safe and has various other issues
(like target paths "a/../b" and "b" ending up as the same
local path).
Instead URL-encode the target path to make it a plain filename. This
removes any opportunity for path trickery and removes the need to create
the required sub directories (which we were not doing currently, leading
to failed downloads). URL-encoding encodes much more than we really need
but doing so should not hurt: the important thing is that it encodes
all path separators.
Return the actual filepath as return value. I would like to modify the
arguments so caller could decide the filename if they want to. But I
won't do it now because updated_targets() (the caching mechanism)
relies on filenames being chosen by TUF. The plan is to make it
possible for caller to choose the filename though.
This is clearly a "filesystem API break" for anyone depending on the
actual target file names, and does not make sense if we do not plan to
go forward with other updated_targets()/download_target() changes
listed in #1580.
This is part of bigger plan in #1580
Fixes #1571
Signed-off-by: Jussi Kukkonen<EMAIL_ADDRESS>

[x] The code follows the Code Style Guidelines
[x] Tests have been added for the bug fix or new feature
[x] Docs have been added for the bug fix or new feature

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.02%) to 97.269%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
3956

Relevant Lines:
4044

💛  - Coveralls

A bit annoying that the tests do not include the case it is supposed to fix (targetpath includes subdirectories) because of #1576 but ok.

yes and I should have pointed that out in the PR message, sorry about that... we can either merge this with the pinky promise that the real tests with "directories" are going to be added, or alternatively we combine this PR and 1756 and merge the result to develop.
@MVrachev 1756 is yours, any opinions? I'd maybe lean towards merging this as is, and then you rebasing your work -- is that ok?

ok, let's try this: if it doesn't end up working we can always admit defeat and bring back the old API -- we have not promised ngclient is stable yet


.env.local not respected on install

Description
I tried to install shopware via composer with shopware/production <IP_ADDRESS> and created an .env.local file with required information to run bin/console system:setup
Installation failed due to missing _ENV variables.
In EnvVarProcessor.php line 171:

  Environment variable not found: "APP_URL".

I renamed the file to .env and it worked.
Possible Solution
Verify the presence of .env.{APP_ENV} and .env.local before running the installation.

Personally I think the issue is actually the template as if you check here https://github.com/shopware/production/blob/6.3/public/index.php
and the same goes for the corresponding console file, they use  (new Dotenv(true))->load($envFile); intead of the new (new Dotenv())->bootEnv(dirname(__DIR__).'/.env'); or (new Dotenv(false))->loadEnv(dirname(__DIR__).'/.env'); (this one defintily exists in 4.4, the other one migh be new in 5.x)
If you have to use it, you could change the corresponding methods yourself in those files.
However, the issue is that the newer Symfony.env loading standard will not work correctly with their storefront and admin build scripts and probably also not with the install command and install web page which is probably why it is not used yet.

Personally I think the issue is actually the template as if you check here https://github.com/shopware/production/blob/6.3/public/index.php
and the same goes for the corresponding console file, they use  (new Dotenv(true))->load($envFile); intead of the new (new Dotenv())->bootEnv(dirname(__DIR__).'/.env'); or (new Dotenv(false))->loadEnv(dirname(__DIR__).'/.env'); (this one defintily exists in 4.4, the other one migh be new in 5.x)
If you have to use it, you could change the corresponding methods yourself in those files.
However, the issue is that the newer Symfony.env loading standard will not work correctly with their storefront and admin build scripts and probably also not with the install command and install web page which is probably why it is not used yet.

Hello,
Within our company roadmap and work capacity, we try to address each bug or improvement request but admit that not each one will be resolved. To continue our culture of honesty and openness, we are closing this issue to focus on our roadmap on behalf of all Shopware users.
If you feel like this issue is still impacting you, please create a new issue and let us know.
Thank you again for your valuable feedback.


Prepare the GitHub Actions release workflows for the release

[ ] Set the event type to push
[ ] Refactor the workflows and clean up

Addressed via various pull requests.


I don't get notifications when the app is closed on macOS.

Any ideas for troubleshooting this?

NetNewsWire uses local notifications (and not push notifications). Therefore it needs to be running on macOS to receive notifications.

@stuartbreckenridge Is there a way to keep running in the background and not have the icon show in my dock?

Not to my knowledge.

I just opened an FR for this: https://github.com/Ranchero-Software/NetNewsWire/issues/4261


Feature request: recover_reduce to support single bit coarse gates $and, ...

Hello,
coarse gate designs have this same need. Currently I have 60.000 single bit $and and 60.000 single bit $or cells in some design. Majority of those form long reduce chains. It is important to reduce those chains because it might reduce cell count dramatically in some cases. Like in mine. There are some simulation situations where reduced cell count will affect to simulation speed. Chains might be very long so option to limit width of reduce cell will help to get a bit more realistic cell count in coarse level.

Here is test unit for this feature request. Now it will make three single bit $and. One 4bit wide $reduce_and would be nice.
module and_reduce (a, b, x);
input [3:0] a, b;
output [3:0] x;
    assign x = (a[3] & a[2] & a[1] & a[0]);
endmodule

There's the extract_reduce pass for transforming $_AND_, $_OR_, $_XOR_ chains into reduce cells as you describe, but at the moment it doesn't consider single-bit $and cells and similar.


feat: switch to RsaPssParams::new()

Switch to using RsaPssParams::new() from pkcs1 crate. This fixes the issue reported by zlint for x509-cert, where SHA* digest algorithms had empty parameters instead of NULL parameters (as required by Mozilla policy and permitted by RFC4055).

cc @baloo @dignifiedquire

@tarcieri thank you! Could you please cut another prerelease?


Version Discrepancy Issue

Hi All,
Is there a reason that under Releases 1.3.0 is marked latest, but https://www.npmjs.com/package/angulartics says 1.4.0 is?
Thanks,
-Brian Eriksen

Just wasn't showing because it wasn't published. thanks!


plugin needs a func running schedule.

Documentation Scope
plugin
Describe the Change
We should describe how plugin running. Such as this:

This is: https://hackmd.io/OM6QW34lSMGn15ez0u0blA?view#Step-3-Create-a-sub-task-for-data-collection


How can I add a plugin?

I'm looking for sending notifications to Slack when errors are handled. I found a lot of documentation about setting it up but that's with X-Pack and the operator doesn't seem to manage it (required > 6.3 according to the official website).
A backup would be to use directly the plugin "watcher" as described in this article:
http://uldissturms.github.io/2016/02/08/configure-elasticsearch-error-watcher-to-send-slack-notifications/
But I'm not sure how to proceed to add a plugin and link it to ElasticSearch since I'm using the operator and its Custom Resource Definitions... Could you provide me some help please?
Thank you 😀

Anyone could help please?
cc @stevesloka

Hey @sneko, plugin's today are installed and baked into the image, I'm not a fan of installing deps on the fly in a production cluster. You can see those base images here: https://github.com/upmc-enterprises/docker-elasticsearch-kubernetes

@stevesloka oh ok I understand 👍
I saw that 6.3 was released yesterday (https://www.elastic.co/blog/elasticsearch-6-3-0-released). How much time the operator usually takes to support new version? (It's just by curiosity, will wait the time it needs 😀  )


Paging Implementation: Add support for huge pages in translate function

This seems to be much simpler than I thought: https://github.com/phil-opp/blog_os/issues/570#issuecomment-680972559

from post 09, OffsetPageTable: "The implementation already supports huge pages [...], so we will use it in the following instead of adding huge page support to our own implementation."
So, does this issue refer to the blog implementation or is this done? :)


ARM state bag constants.

Hi @boumenot, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

What do you think, should we split the non-shared constants to the separate builder packages?

I think it makes sense, but lets wait for the dust settle to figure out what's shared and what isn't.  If we namespace them I would be leaving it as is too.


Set kafka.partition-limit-enforced to true

Setting the kafka.partition-limit-enforced property to true for work on MGDSTRM-8672

Hello @k-wall, @MikeEdgar, @shawkins, would you mind reviewing, please? Thanks :)

lgtm


About the ground-truth labels

This is a good job, but i'm very Interested in that how to make the ground-truth labels. I found your macth pair results similar to the SP+SG, you used the SuperPoint labels?

This is a very good question. And we didn't use any detector labels. As stated in the paper (3.5), mutual nearest neighbors of 1/8-resolution grids are selected as coarse-level labels, and sub-pixel correspondences are the fine-level labels.

按你文中所示用了[Qianqian Wang, Xiaowei Zhou, Bharath Hariharan, and Noah Snavely. Learning feature descriptors using camera pose supervision. In ECCV, 2020. 5]该方法，通过有relative pose利用极线约束来进行学习描述子。

We didn't apply epipolar loss proposed in CAPS to learn descriptors. 我们没有使用CAPS提出的极线损失函数来学习描述子。

Of course, you constructed a loss to  find the match pairs.

Oh, @atztao  I'm sorry I think finally understand your question based on your edited description.
We use dense depth maps and camera parameters to compute ground-truth correspondences. The depth maps are provided by depth sensor (ScanNet) and MVS system (MegaDepth).

Ok,  good answer.


fix rxdeep results, add rxjs-hooks

follow up to this PR, fixing RxDeep results (in README) and adding rxjs-hooks for reference.

Thanks. Merging this. I need to investigate why check 7 doesn't fail with some of rxjs libs.

I would love to help, though I would need to read the code more closely to understand what is each check actually checking. The tearing bits are more understandable, but I have no idea what the "EXCEED" error is showing.

I know the code for check 7 is not easy for reading.
Let's start with some basics.
For state branching, https://reactjs.org/docs/concurrent-mode-intro.html is must read.
Suppose the initial count is 0 and we dispatch the increment action in a transition.
The state is branched and in the first branch it's 0 and in the second branch it's 1.
While components render with the second branch, we still have the first branch and displayed.
Once the render phase is finished, we show the new tree (rendered with the second branch).
Now, if we dispatch another action outside transition within the pending state, the expected behavior is to apply it to the second branch and do not change the first branch. So, users would see 0 and "Pending..." and then 1. When they see 2, no "Pending..."
However, if a global state does not support branching, the second action is applied even if it's in a transition. In this case, users would see 2 with "Pending..."
This is what the current tool does for checking branching. That is EXCEEDED. I'm happy to take any other approaches to check branching.
Finally, please note that all of this is what I learned from the doc and the behavior in many experiments. However, there can be some mistakes or React will change the behavior in the future.

thanks for the explanation. intuitively makes sense, I'll have to take a deeper look once I got some more free time on my hand.


Summer Start System

Have one command to commence summer:

delete course-text channels

I'm still deciding what to do about advisements... I don't know whether to remove them now or closer to next year.

Also remove advisement roles and maybe add Class of [Year] to all students and use it to sort the sidebar


Minitest

Hey Colin, thanks again for the help yesterday! A few things came up as I was going through the rest of the call controller. It looks like we had been saving calls without statuses in our first test. Now I am validating by status in the call model so the test needed updated. There’s also one test that doesn’t make much sense the way I’m approaching it, but I’ve included inline comments to explain the problem. Feel free to come back with lots of comments! This isn't quite ready to merge, but I'm just assuming that a PR is still the easiest way to give/get feedback.

Thanks a ton for your hard work on this, Alexis! I should be able to review
this today or tmrw.
On Tue, Feb 16, 2016 at 10:36 AM Alexis Johnson<EMAIL_ADDRESS>wrote:

Hey Colin, thanks again for the help yesterday! A few things came up as I
was going through the rest of the call controller. It looks like we had
been saving calls without statuses in our first test. Now I am validating
by status in the call model so the test needed updated. There’s also one
test that doesn’t make much sense the way I’m approaching it, but I’ve
included inline comments to explain the problem. Feel free to come back
with lots of comments! This isn't quite ready to merge, but I'm just
assuming that a PR is still the easiest way to give/get feedback.
You can view, comment on, or merge this pull request online at:
https://github.com/colinxfleming/dcaf_case_management/pull/83
Commit Summary

generate calls_controller_test.rb
calls, cases, patients factories
should create and save a new call
fix call count
extract attributes_for :call
test calls#create should redirect to the root path
validates_presence_of status for call
another attempt at testing association between call and case
call should reject other attributes besides status
Merge branch 'master' of github.com:colinxfleming/dcaf_case_management
into minitest

File Changes

A app/assets/javascripts/calls.coffee
https://github.com/colinxfleming/dcaf_case_management/pull/83/files#diff-0
(3)
A app/assets/stylesheets/calls.scss
https://github.com/colinxfleming/dcaf_case_management/pull/83/files#diff-1
(3)
M app/controllers/calls_controller.rb
https://github.com/colinxfleming/dcaf_case_management/pull/83/files#diff-2
(3)
M app/controllers/patients_controller.rb
https://github.com/colinxfleming/dcaf_case_management/pull/83/files#diff-3
(2)
A app/helpers/calls_helper.rb
https://github.com/colinxfleming/dcaf_case_management/pull/83/files#diff-4
(2)
M app/models/call.rb
https://github.com/colinxfleming/dcaf_case_management/pull/83/files#diff-5
(2)
A test/controllers/calls_controller_test.rb
https://github.com/colinxfleming/dcaf_case_management/pull/83/files#diff-6
(51)
A test/factories/call.rb
https://github.com/colinxfleming/dcaf_case_management/pull/83/files#diff-7
(5)
A test/factories/case.rb
https://github.com/colinxfleming/dcaf_case_management/pull/83/files#diff-8
(7)
A test/factories/patient.rb
https://github.com/colinxfleming/dcaf_case_management/pull/83/files#diff-9
(6)

Patch Links:

https://github.com/colinxfleming/dcaf_case_management/pull/83.patch
https://github.com/colinxfleming/dcaf_case_management/pull/83.diff

—
Reply to this email directly or view it on GitHub
https://github.com/colinxfleming/dcaf_case_management/pull/83.

This is really great work, @ajohnson052 . Nice job!
I'll do a little wrenching on it tomorrow night to make sure things are behaving right, and I had a few comments and suggestions if you've got the opportunity this week, but these are great. (If you don't have the time I'm happy to merge this and knock the rest of them out this weekend.)

@ajohnson052 :clap:


test script hard-codes 8001 and does not take an argument

In the youtube video you say that the script test-k8sdemo.sh takes an argument but it seems only to access the host at port 8001. This is an issue as you suggest to use port 8080 throughout the tutorial.
When you run the script it prints:
curl: (7) Failed to connect to localhost port 8001: Connection refused
If you change 8001 in the script to $1 then it prints:

Greetings from the DEMO! *

(BTW Thanks for the education. )

Hey @turkeylurkey. Sorry about that. I forgot to commit the change that makes the script argument work.
Please grab the latest, and try again. Thanks for reporting this!
--jsp


How to Migrating from Python 3.6 to Python 2.7 or multiple use for both version

Since pysumma is just starting its development, I would strongly advise NOT supporting Python 2 at all. Pysumma dependencies such as Pandas and Xarray are dropping Python 2 support later this year so any advantage you get from supporting both will be short lived.

@jhamman Thank you for your opinion.


NormalizeSeparators with pipe separators silently fails with param sections=comments

Trying to fine tune the run of just NormalizeSeparators on resource file with large comments.  The doc on Ignored Sections shows that the only the sections listed in the 'sections' param will get transformed.
If I list all sections but comments all lines are transformed.  This might be because I do not understand what is considered a comment section.  If I am correct than this usage of  'sections' param is broken too.
But if sections param only has 'comments' no output is produced and return code is 0 (zero)
Orig file:
*** Settings ***
| Documentation
| ... | Provides access to all Keywords needed for interaction with Toucan GUI.
| ... | For more details on what must be set to use this library, see documentation
| ...
| Library   | String
| Library   | Collections
| Library   | SensorSwitchRig
| ... | gmswRig | 001
| Resource  | vertiv_lol_sensor_rig.robot
| Variables | geist_toucan_constants.py

*** Keywords ***

#------------------------------------------------------------------#
# A LARGE COMMENT SECTION                                          #
#                                                                  #
# Used to do a complete set and verify of a Toucan param           #
#------------------------------------------------------------------#

#
# Text Fields
#
Test Toucan Text Field
| | [Documentation] | Sets and verifies Toucan GUI text fields against expected value.
| | ... | \nExample:
| | ... | \| \| Test Toucan Text Field  \| webserver \| httpport  \| ${value} \| ${expected}
| | [Arguments] | ${page name} | ${field name} | ${value} | ${expected}=${G_NOT_DEFINED}
| | Set And Save Toucan Field Type | text | ${page name} | ${field name} | ${value}
| | Verify Param Without Login | ${page name} | ${field name} | ${value} | ${expected}

With all sections but comments.  Expectation is all pipes removed with 4 spaces but large block comment is not changed.
robotidy  --output out.robot  --transform NormalizeSeparators:sections=settings,variables,keywords,testcases in.robot

cat out.robot

*** Settings ***
Documentation
...    Provides access to all Keywords needed for interaction with Toucan GUI.
...    For more details on what must be set to use this library, see documentation
...
Library    String
Library    Collections
Library    SensorSwitchRig
...    gmswRig    001
Resource    vertiv_lol_sensor_rig.robot
Variables    geist_toucan_constants.py

*** Keywords ***

#------------------------------------------------------------------#
# A LARGE COMMENT SECTION    #
#    #
# Used to do a complete set and verify of a Toucan param    #
#------------------------------------------------------------------#

#
# Text Fields
#
Test Toucan Text Field
    [Documentation]    Sets and verifies Toucan GUI text fields against expected value.
    ...    \nExample:
    ...    \| \| Test Toucan Text Field  \| webserver \| httpport  \| ${value} \| ${expected}
    [Arguments]    ${page name}    ${field name}    ${value}    ${expected}=${G_NOT_DEFINED}
    Set And Save Toucan Field Type    text    ${page name}    ${field name}    ${value}
    Verify Param Without Login    ${page name}    ${field name}    ${value}    ${expected}

With only comments given there is no output and RC=0
robotidy  --output out.robot  --transform NormalizeSeparators:sections=comments in.robot

echo $?
0

cat out.robot
cat: out.robot: No such file or directory

I tried the same using a configure file and the results are the same:
PRODUCES NO OUTPUT

cat comments.toml

[tool.robotidy]
separator = "space"
spacecount = 4

transform = [
    "NormalizeSeparators:sections=comments"
]

PRODUCES OUTPUT AS GIVEN ABOVE:

cat nocomments.toml

[tool.robotidy]
separator = "space"
spacecount = 4

transform = [
    "NormalizeSeparators:sections=settings,variables,keywords,testcases"
]

I have added in 3.0 release skip_* parameters. I think - when you mention this transformer and behavior of the section - I should replace it with skip_section in the future. I will open issue for it. But that's for the next major release.
For the issue itself - the comments is *** Comments *** section. Every line before first section in the file is considered as part of the comment section - and it can optionally have header *** Comments ***. When I will be near PC I can check if the transformer skip it properly and section parameter is honored.
If you want to skip comments (the ones with #) in NormalizeSeparator we would need to add new skip_* parameter. It could be either skip_comment skipping all comments or skip_standalone_comments - bit verbose but a way to skip lines containing only comments.

Sounds good.  I will test the *** Comments *** section tomorrow and let you know.  Expect it should work.

Opened separated issue to track mentioned future changes, closing this issue for now (reopen if needed).


Use context.Background in tests instead of context.TODO

As discussed in #162.

This change is

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

thank you!

Review status: :shipit: all files reviewed at latest revision, all discussions resolved, all commit checks successful.

Comments from Reviewable


[Feature Request] "Zigbee Direct" support for ESP32-H2 and ESP32-C6 in ESP-Zigbee-SDK? (TZ-716)

Is your feature request related to a problem?
Requesting support for the new "Zigbee Direct" feature for ESP32-H2 and ESP32-C6 in ESP-Zigbee-SDK, can that be possible?
https://csa-iot.org/all-solutions/zigbee/zigbee-direct/
"Zigbee Direct" allow users to directly interact with Zigbee devices over BLE (Bluetooth Low Energy) using a smart phone / tablet.
https://csa-iot.org/all-solutions/zigbee/zigbee-direct-faq/
https://www.youtube.com/watch?v=py2O0OJwick
Real-world examples of Zigbee Direct are products from Ubisys which list some of the use cases as well as show some demos:
https://www.ubisys.de/en/technology/zigbee-direct/
The latest version/revision of DSR’s ZBOSS stack does support Zigbee Direct Device (ZDD) but believe the device needs support for concurrent Zigbee and BLE communication at the same time, however, I understand that ESP32-H2 does have concurrent support for IEEE 802.15.4 and Bluetooth LE as that is needed for Thread based Matter devices, but is it possible to use Zigbee and BLE simultaneous on ESP32-H2 and  ESP32-C2?
Anyway, DRS claim that ZOI and ZBOSS SDK 4.1.0 supports Zigbee Pro 2023 (R23) where support for the Zigbee Virtual Device (ZVD) is included.
https://dsr-zoi.com/updates/dsr-zigbee-direct/
https://dsr-iot.com/solutions/zigbee-direct/
https://dsr-iot.com/downloads/zigbee-direct/
https://dsr-zboss.com/#!/updates
https://dsr-zboss.com/#!/updates/dsr-zigbee-direct-solutions
https://dsr-zboss.com/#!/updates/zoi-r23-update
https://dsr-zboss.com/#!/updates/dsr-zigbee-direct
"DSR’s market-proven ZBOSS stack with Zigbee Direct Device (ZDD) empowers silicon vendors to integrate the ZDD, enabling the product companies who utilize their chipsets to fully support Zigbee Direct."
"Product companies and app developers can integrate the Zigbee Virtual Device into their offerings through our ZBOSS ZVD SDK, which is used to build user-facing applications with Zigbee Direct functionalities onto your smart device, allowing it to interact with the Zigbee Direct Device in the network"
"Utilize DSR's zRemote application to commission and maintain Zigbee devices from a smart device. Installers can use the “batch-commissioning” feature to add groups of devices to the network simultaneously, instead of having to manually commission devices one-by-one."
Zigbee Direct - What it is and How to Use it in Your Products
https://www.youtube.com/watch?v=b7jqB8m0s-I
https://www.silabs.com/support/training/zgb-201-what-is-zigbee-direct
A ZVD (Zigbee Virtual Device) establishes a secure Bluetooth® Low Energy connection with a Zigbee Direct Device. Once connection is established, the ZVD can send commands to the Zigbee Direct Device and other Zigbee Devices on that same network.

I understand that there is also another Zigbee Direct feature to help with initial commission of a Zigbee device over BLE.
https://www.youtube.com/watch?v=TlCX95jTrWQ

Describe the solution you'd like.
Support for both Zigbee Direct Device (ZDD) and Zigbee Virtual Device (ZVD) in ESP Zigbee SDK.
BLE control of ESP32-H2 and ESP32-C6 Zigbee device without a Zigbee gateway/bridge/hub.
Support for BLE commissioning to a Zigbee network using Zigbee Direct to join a new device to an existing Zigbee network.
Describe alternatives you've considered.
No response
Additional context.
No response

'Zigbee Direct' is indeed in our roadmap, but not a high priority at this moment. Feel free to contact us if any clear customer product requirement.


Enhance tmt.utils.retry_session with timeout support

retry_session is now usable as a context manager, and accepts a
timeout to honor for each HTTP request.
Current retry_session was overlapping with similar functionality in
artemis plugin, so merged both together and threw context manager in
too, because retry_session was used in that manner exclusively.

@lukaszachy BTW this and https://github.com/teemtee/tmt/pull/1280 would be prime candidates for the "refactoring" label you suggested, they do exactly that.


Add PCI-DSS Policy to OCP on GCP deployment

Feature Request
Add PCI-DSS as per SAA
Description of Problem:
To meet SAA requirement PCI-DSS policy needs to be added to OCP C
...please resist the temptation to describe your request in terms of a solution.  Job Story form ("When [triggering condition], I want to [motivation/goal], so I can [outcome].") can help ensure you're expressing a problem statement.
Potential Solutions:
Add PCI to Compliance operator policy

merge changes for this issue into Dev - now waiting on issue #25 to update main. Closing this issue.


python312Packages.txamqp: normalize pname

Description of changes
part of #245383
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 297038 run on x86_64-linux 1

6 packages failed to build:

python311Packages.graphite-web
python311Packages.graphite-web.dist
python312Packages.carbon
python312Packages.carbon.dist
python312Packages.graphite-web
python312Packages.graphite-web.dist

6 packages built:

python311Packages.carbon
python311Packages.carbon.dist
python311Packages.txamqp
python311Packages.txamqp.dist
python312Packages.txamqp
python312Packages.txamqp.dist


Runtime cache of found view files.

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
no

Tests pass?
yes

Fixed issues

Runtime cache of found view files.
This reduce count of calls to disk and manipulations with strings when calculation the result path.
Caching increase speed when findViewFile() calls many times.
For example, we calls $this->renderPartial() for one view file more than 500 times.

It looks interesting. Have you benchmarked it?

It's a clear yii2-basic application.
1 000 iterations
cache:    float 0.0070009231567383
no-cache: float 0.012001037597656

10 000 iterations
cache:    float 0.070007085800171
no-cache: float 0.12501192092896

Caching give more performance when using and extends theme component.
For example we have view files of default theme and extends some of files in advance theme.
In this case we have more operations with disk and concatenitions.
Each file checking as this (as example):
$files = [
    '/themes/advance/view.php',
    '/themes/default/view.php',
];

foreach ($files as $file) {
    if (file_exists($file)) return $file;
}

return false;

Sorry, but we can not accept this PR for the reasons I've posted in my review


Deleting Party Relation

Deleting a party relation deletes more than the two representative records.

Currently, we delete a contact from an Opportunity by deleting the PartyRelationship record. This isn't correct, as there are two PartyRelationship records. Perhaps we should instead, use EndRelationship?

Also, we need to improve the UI to more clearly indicate a relationship that has ended.

The original issue that deleting one PartyRelation was not just deleting the reverse relationship record, but also was deleting additional records not associated with the relationship.
I reopened this so I can get clarity on the discussion comments, because I think multiple issues might have been addressed in this bug report:

We currently don't have an OpportunityParty entity, so there shouldn't be a way to remove a party from an Opportunity, as it would be confusing to the user. If we decide to support that feature, it would require its own feature request.
In the interest of preserving the integrity of temporal data, ending a relationship is preferred over deleting the records. That said, this would be a new feature request since there are many factors to consider (e.g., updating/adding API, updating UI to show active vs. historical).

I have confirmed that deleting one PartyRelation record deletes more than just its reverse. It deletes all partyrelation records that PartyFromId.

I've removed the allow delete in data file in the relationship between PartyRelation#To -> PartyRelation#To_PartyRelation#From and updated the Delete PartyRelation API.


python3Packages.pyopencl: fix build

Motivation for this change
Fix the recently broken build by adding pybind11 and pkgs.pybind11
to the build. Also set $HOME to a temporary directory during the build
to avoid "Permission denied" errors in the build script.
This also unbreaks sasview and pybitmessage.
See also https://hydra.nixos.org/build/89037506
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Why are both needed? That seems a bit weird.

WIthout pkgs.pybind11 as build input the compilation fails with the following errors, so I'm not sure if the Python version will work:
gcc -Wno-unused-result -Wsign-compare -fwrapv -Wall -O3 -DNDEBUG -fPIC -DPYGPU_PACKAGE=pyopencl -DPYGPU_PYOPENCL=1 -Ipybind11/include -I/nix/store/6la3fblc497pacyy0vxhnjq1l1wlb5w7-python3-3.7.2/include/python3.7m -I/build/tmp.aabYVn0RAS/.local/include/python3.7m -I/nix/store/rirgscxdd9r8kgady8ilgpv6r7yvk388-python3.7-numpy-1.16.0/lib/python3.7/site-packages/numpy/core/include -I/nix/store/rirgscxdd9r8kgady8ilgpv6r7yvk388-python3.7-numpy-1.16.0/lib/python3.7/site-packages/numpy/core/include -I/nix/store/6la3fblc497pacyy0vxhnjq1l1wlb5w7-python3-3.7.2/include/python3.7m -c src/wrap_constants.cpp -o build/temp.linux-x86_64-3.7/src/wrap_constants.o -fvisibility=hidden -DVERSION_INFO="2018.2.2" -std=c++14 -fvisibility=hidden
In file included from src/wrap_cl.hpp:86:0,
                 from src/wrap_constants.cpp:27:
src/wrap_helpers.hpp:31:10: fatal error: pybind11/pybind11.h: No such file or directory
 #include <pybind11/pybind11.h>
          ^~~~~~~~~~~~~~~~~~~~~
compilation terminated.
error: command 'gcc' failed with exit status 1
builder for '/nix/store/289qbw2j1a2n2a7b4cpbfl2r4hxln6y8-python3.7-pyopencl-2018.2.2.drv' failed with exit code 1

If I get this right, we want to patch the pybind11 reference away from setup_requires and only use pkgs.pybind11 for compilation?

If I get this right, we want to patch the pybind11 reference away from setup_requires and only use pkgs.pybind11 for compilation?

Correct.

Hmm I'm afraid that this isn't that easy: we need pkgs.pybind11 as build input (otherwise the compilation will fail as posted above), however we need pythonPackages.pybind11 as well, otherwise the build will break with the following error:
...
File "setup.py", line 51, in __str__
    import pybind11
ModuleNotFoundError: No module named 'pybind11'

Admittedly I'm not that experienced with the pybind11 integration, so I'm not 100% sure what else to do (instead of using the current approach from this PR).

...
File "setup.py", line 51, in __str__
    import pybind11
ModuleNotFoundError: No module named 'pybind11'

That probably comes from https://github.com/inducer/pyopencl/blob/0faf48a10edd086c783f794a6decdf85e8dc625b/aksetup_helper.py#L894. We'd need to patch that function to return "${pkgs.pybind11}/include".

I see. If @FRidh prefers the latter solution you proposed, I'd implement this, otherwise I'd vote for merging this :)

pybind11/__init.py:get_include needs to be fixed because it returns the path to the headers folder of ${python3} instead of ${python3.pkgs.pybind11}.

Cross-referencing #56826 (the build is broken on the new release as well).

See also https://github.com/pybind/pybind11/pull/1426 for a requests to fix get_include.

@Ma27 we might use that PR as a patch.

@FRidh applied the pybind11 patch and updated.

@dotlambda anything else to do? :)

cherry picked in 2d8b128fff9ee11eb853a01a3bbd97abd6b3575e and 68c73b977fb6be3ab5ff187d12bfa786f6489119


Added comment about target padding.

Edited  comment about target padding.
@vdauwera Can you review this simple update to the workflow prerequisites in the README?  Does it need to be included in later material?  At some point, contents of this README will be in the forum (broken up into separate posts).  However, I am having an issue with the forum now (see email).
Closes #206

Done with my review -- would be good to have a bit more clarity, see in line comments.

@vdauwera This pull request can be closed without merging.  Previous pull request obviates it.  I updated the forum post, so everything should be fine.

Here was the added content...
Before running the workflows, we recommend padding the target file by 250 bases with the PadTargets tool.  Example:  java -jar gatk-protected.jar PadTargets --targets initial_target_file.bed --output initial_target_file.padded.bed --padding 250
This allows some off-target reads to be factored into the copy ratio estimates.  Our internal evaluations have shown that this improves results.
If you are using the premade Queue scripts (see below), you can specify the padding there and the workflow will generate the padded targets automatically (i.e. there is no reason to run PadTargets explicitly if you are using the premade Queue scripts).

Forum post:  http://gatkforums.broadinstitute.org/gatk/discussion/6791/description-and-examples-of-the-steps-in-the-cnv-case-and-cnv-pon-creation-workflows


Allow cmsg_space! to be used in unit tests

Fixes https://github.com/nix-rust/nix/issues/1405

Looks good, but you need to rebase on master to fix the test failures.

Looks good, but you need to rebase on master to fix the test failures.

Rebased.


[4.0] Avoid call parseRender when render attribute is null.

Actual Behavior.
Currently, when the action column is added in the Builder, the render attribute is set to null, and the parseRender method is called in the Column class constructor. This commit adds a little validation to avoid calling parseRender and all the methods called inside this method.

Released on v4.3.2, thanks! 🚀


Merge Main > Live

Docs Build status updates of commit b80f3cf:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit ed67430:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

TerminalDocs/images/oh-my-posh-winget.png
:white_check_mark:Succeeded
View

TerminalDocs/tutorials/custom-prompt-setup.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Added PHP Redis Extension for PHP 7

@g0ld3lux Thanks!

i have an updated pull request with readme please merge it
https://github.com/laradock/laradock/pull/548


docs(installation): add documentation for intellisense on SFC objects

Added documentation and examples for enabling tailwind IntelliSense on objects in a vue SFC using a /*tw*/ prefix.
Sometimes when overriding too many ui props, a single line can get cluttered.
This would allow you to define your ui overrides in the script portion of the VUE SFC with IntelliSense.

You would define the RegExp in settings.json with:
"tailwindCSS.experimental.classRegex": [["/\\*tw\\*/\\s*{([^}]*)}", "'([^']*)'"]]
This can be appended to the ui config regexp that is already defined in the installation documentation.
How it works is it looks for JS objects prefixed with a /*tw*/ comment.
You could enable IntelliSense for the entire SFC but I figured /*tw*/ would be better to avoid over-saturating editor suggestions.
Here is an example:
<template>
    <UCard :ui="ui" />
</template>
<script setup>
     const ui = /*tw*/ {
         "background": "bg-blue-500"
     }
</script>

You can also make it reactive with:
<template>
    <UCard :ui="ui" />
</template>
<script setup>
     const ui = ref(/*tw*/ {
         "background": "bg-blue-500"
     })
</script>

Hope this is useful!

UI would make sense too.
You are the expert! I'm open to whatever, just an idea that helped me tremendously keep my templates organized.
Would it make sense for tailwind intellisense on all SFC globally without syntactic sugar?
Let me know and I can change the prefix to /*ui*/ or make it global for every .vue that has a <script> tag.

You can change to /*ui*/, I don't think it would make sense globally as you only define those classes in either app.config.ts, :ui prop directly in the template or through a ui variable like you mentioned and the first two cases are already documented.

Awesome. I changed to /*ui*/ and updated the regexp to support all characters that enclose a string aswell as fixed nested objects. It only applies intellisense on strings that are values and not keys. Thanks for the regexp! I adopted it from whoever wrote app.config.ts regexp.
"tailwindCSS.experimental.classRegex": [["/\\*ui\\*/\\s*{([^;]*)}", ":\\s*[\"'`]([^\"'`]*).*?[\"'`]"]]
An example:
<script setup>
const ui = /*ui*/ {
    "base": "flex",
    "background": `bg-gray-900`,
    "heading": {
        "background": 'bg-gray-700'
    },
    "footer": {
        "background": 'bg-gray-700'
    }
}
</script>

Hello does it work if the hint is on top of the statement? this is the normal way of declaring annotations and would be nice if this is supported as otherwise maybe a bit counter intuitive
<script setup>
  // Will this work?

  /*ui*/
  const ui = {
    "background": "bg-blue-500"
  }
</script>

Hello does it work if the hint is on top of the statement? this is the normal way of declaring annotations and would be nice if this is supported as otherwise maybe a bit counter intuitive
<script setup>
  // Will this work?

  /*ui*/
  const ui = {
    "background": "bg-blue-500"
  }
</script>

Would this way interfere with JSDoc annotations?
Ive never used JSDoc so my intuition says that you wouldnt use JSDoc on something like this but dont want intellisense to be a hinderance.
Im open to whatever though!

"tailwindCSS.experimental.classRegex": [["/\\*ui\\*/[^{};]*{([^;]*)}", ":\\s*[\"'`]([^\"'`]*).*?[\"'`]"]]
This works for declaring your annotation on top of the object declaration. It relies on a ; delimiter at the end of the object to avoid intellisense applying on the next object, however.
Let me know what you guys think!

@MadDog4533 JSDoc syntax starts with a slash followed by two stars to be unique so that shouldn't be a problem
// JSDoc starts with a '/**'
/**
 * Represents a book.
 * @constructor
 */
function Book(title, author) {
}

// Your descrimniator starts with '/*', we should be good!
/*ui*/
const ui = {
  "background": "bg-blue-500"
}


To exclude code of WebAudio in Blink

I believe we've lost this part during the rebase of last time.
This patch bring 332K szie-reduction back.
With this patch (and the one for Plugins) the newest size of Crosswalk-LIte is:
10548   XWalkCoreShell.apk
10204   XWalkRuntimeClientEmbeddedShell.apk
We're very close to 10M!

@heke123 @halton

LGTM

What a great news, we're close to 10M again.


Toml sub-section quotes

Test Code
TomlTable expectedNode = new TomlTable
{
    ["section"] = new TomlTable
    {
        ["sub.section"] = new TomlTable
        {
            ["foo"] = "foo",
            ["bar"] = "bar"
        }
    }
};

using (var sw = new StringWriter())
{
    expectedNode.WriteTo(sw);

    string result = sw.ToString();
}

Expected Result:
[section."sub.section"]
foo = "foo"
bar = "bar"

Actual Result:
[section.sub.section]
foo = "foo"
bar = "bar"

Additional notes:

This problem really only happens if a . dot exists in the key.
Deserialization works fine if the quotes are supplied in the section.  Only serialization has a problem.

Suggested Change:
https://github.com/dezhidki/Tommy/blob/e5fa93e3fa9ca2595886ef58a1038cdb2912904f/Tommy/Tommy.cs#L569
string childKey = child.Key.Contains(".") ? $"\"{child.Key}\"" : child.Key;
child.Value.WriteTo(tw, $"{namePrefix}{childKey}", first);


Problems with latest version

Currently, the latest version does not compile on XCode 7 because of #42.
The solution was to use :head but the problem is that it doesn't compile anymore because PodSpec file has not been updated properly and some files are not added correctly.
Is it possible to update ASAP, I posted a PR #65 to fix the problems I believe

Merged #65. A new release is under development, but still very experimental. I will spend a whole week to polish that new release during the national holiday of China (Oct/1 - Oct/7), should be enough to finish it.

Perfect, I'll be in holiday too, let me know if you need any help.

+1

+1


Koa deprecated Support for generators

Hey guys!
I'm a paid user for the Google cloud platform and love it.
Could you guys please update the driver for koajs? I start to get the following warning:
Mon, 05 Feb 2018 11:47:29 GMT koa deprecated Support for generators will be removed in v3. See the documentation for examples of how to convert old middleware https://github.com/koajs/koa/blob/master/docs/migration.md at node_modules/@google-cloud/trace-agent/build/src/plugins/plugin-koa.js:99:24
You guys can follow the update instructions here, I think it will be pretty straightforward:
https://github.com/koajs/koa/blob/master/docs/migration.md
Thank you for your awesome job in this library!
Henry

The Trace Agent doesn't prepend generator functions for Koa 2. I think what's happening is that the warning message shows the top line of the stack trace when Koa#use is being called. Because the Trace Agent wraps this function, it altered the stack trace to add an extra frame to the top as you've observed.
I would expect that when turning off the Trace Agent (by removing the call to start), the warning message will show a line in your application where a generator is still being used.

Hi @kjin thanks for your explanation, really appreciate that! But, could you be a little bit more detailed? How could I start the monitor in my Koa2 application without getting this warning? Any code example would be very helpful.
Below is how I currently call the monitor in my application:
// Stackdriver
const trace = require('@google-cloud/trace-agent').start({
    projectId: 'polen--project',
    serviceContext: {
        service: 'glasstone-travel-channel',
        version: '1.0.0'
    }
});

Getting the message:
koa deprecated Support for generators will be removed in v3. See the documentation for examples of how to convert old middleware https://github.com/koajs/koa/blob/master/docs/migration.md node_modules/@google-cloud/trace-agent/build/src/plugins/plugin-koa.js:99:24
Thanks!

Sure, what I mean is that I suspect you will get a warning even if you comment out the code above. Here's a code example: https://gist.github.com/kjin/e1b9ddcf4360adbdef2e11b939d6a6f2

Can I use the agent without a generator function, since I'm using Koa2? Thanks

Yes, you can! The example shown was just for the sake of showing how the warning changes depending on whether the Trace Agent is started or not.

@henryoliver Were you able to verify whether the warning message comes from use of generators external to the Trace Agent?

@henryoliver Closing this for now. Please comment if this doesn't work for you.


[WIP][Nova] Added draft calling GHA workflow for building linux wheels

As part of Project Nova, we are consolidating CI/CD workflows and infra, making them reusable across PyTorch ecosystem libraries. https://github.com/pytorch/test-infra/pull/460 introduces a general-purpose reusable workflow to build linux wheels for python libraries. This PR introduces a caller workflow that triggers the reusable workflow. Details around modular env setup, passing input args across workflows, etc. are still being worked out.

Shall we merge what we have so far (after removing the on: PR trigger in the calling workflow)? That way we can unblock Wei to work on completing the build matrix without stepping on the other in-progress changes. Also so everybody owns their own PR's :)

@mehtanirav is testing py37 and py38 wheels, once it is done, I will add the remaining ~22 test cases.

Shall we merge what we have so far (after removing the on: PR trigger in the calling workflow)? That way we can unblock Wei to work on completing the build matrix without stepping on the other in-progress changes. Also so everybody owns their own PR's :)

Good point. I will try to close this PR today, and unblock Wei from his testing.


CartItems: Minimal UI issues that don't manifest outside the Component Library site

Type: minor
Describe the bug
There are a few small UI issues with the CartItems component. However, as far as I can see via testing, I think these issues are due to the new sidebar / design of the Component Library causing issues with responsive sizes, and actually don't occur when we use this component inside the starterkit. I'm creating this ticket as a "come back and check this later to make sure it looks good once we officially use this component in the starterkit."
To Reproduce
Steps to reproduce the behavior:

Go to the `CartItems component docs
Change the size of the viewport
See that the prices aren't aligned as they should be

Expected behavior
Prices should always remain inside their container
Screenshots

Desktop (please complete the following information):

OS: macOs
Browser: all

Smartphone (please complete the following information):

Device: iPhoneX
OS: 11.2
Browser safari

Additional context
I think this is just a temporary issue inside the component library due to the overall design of the library, not this particular component.

@mikemurray let's close this if we can't reproduce.

This is only an issue in the documentation at a certain breakpoint due to the sidebar not collapsing when nearing mobile sizes. In the starter kit and mobile view of the documentation, everything is fine.
Closing this issue.


Fixed add_root_of_trust call+ Added bank zip files download functionality

Fixed add_root_of_trust call+ Added bank zip files download functionality

Everything looks good to me. I have tested the changes locally with docker and the remote scripts, and everything works as expected.


Add json schema to validation to backend

Proposed solution
Validate JSON submissions POSTed to /objects/{schema} against json schemas. Let's use https://github.com/dchaplinsky/aiohttp_validate
DoD (Definition of Done)
Json is validated in the same manner as XMLs, invalid submissions are reported.
Testing
Unit tests and integration tests

that package does not contain that many things, I would do it in a simple decorator and have more control over the checks and the raised errors.


:sparkles: Make separate folder in Android storage for downloads

Closes #93
This also solves the permission issue on Android Q.

Orientation has been fixed to portrait (prevent auto-rotation) in this PR.


Fix typo (groups)

croups -> groups

What changes did you make? (Give an overview)
Fixed a typo.
Is there anything you'd like reviewers to focus on?
No.
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[x] No need to

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings (e.g. Sonar is happy)
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged

A picture of a cute animal (not mandatory but encouraged)

@yardenshoham thanks!