Mini-spec on data cleaning for PROSE team

PROSE would like a spec/doc for data cleaning. Should include:

Expected API contract
Types of errors we expect to be fixed (e.g. rows with bad data, rows with "No data" instead of a number, rows with unusual data, etc.)
How we'd like things to be fixed (pull bad rows into another file, interaction in UI, etc.)

@beccamc I think this issue is something we might want to explore to make data prep easier for code-first approaches.


[BUG] Unsupport match...case... statement when compiling *.py

Describe the bug
match...case... statement, proposed in PEP 634: Structural Pattern Matching,provides pattern matching process for users like switch statement in C/C++.
However, this statement is not supported in current Cython.
A minimal example is as following to reproduce the issue:
Code to reproduce the behaviour:
# Minimal example to reproduce the issue
a=1
match a:
    case 1:
        print("1")
    case _:
        print("2")
"""
>>> python .../test.py
1

>>> cython .../test.py
Error compiling Cython file:
------------------------------------------------------------
...
# minimal example to reproduce the issue
a=1
match a:
      ^
------------------------------------------------------------

.../test.py:3:6: Syntax error in simple statement list
"""

Expected behaviour
Any solutions or suggestions?
If it is a bug, I am trying to fix this bug if possible.
OS
macOS
Python version
3.10.12
Cython version
3.0.2 and 3.0.3
Additional context
My Analysis
So I trace back to the function def p_simple_statement_list(s, ctx, first_statement = 0) in ./Cython/Compiler/Parsing.py,which raise the syntax error. The only call appears in the function def p_statement(s, ctx, first_statement = 0) in the same file.
...
elif s.sy == 'include':
    if ctx.level not in ('module', 'module_pxd'):
        s.error("include statement not allowed here")
...
elif s.sy == 'for':
    return p_for_statement(s)
elif s.sy == 'with':
    return p_with_statement(s)
...

This function deals with different statements according to prefixs. I think p_match_statement and p_case_statement are needed to resolve this statement.
Also, I searched 'match' globally in the project, but found nothing. It seems that match statement is not considered in current cython.
I am trying to fix this bug now if possible.

Duplicate https://github.com/cython/cython/issues/4029.
It just isn't implemented yet in any Cython release. In that ticket you'll find links to a branch where it is implemented in full, but this hasn't yet been reviewed and merged.


Redirect to another domain

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
We have migrated to new domain new.domain.com and need to redirect all the users that still use old.domain.com to this new address.
Describe the solution you'd like
In application gateway it seems to be doable with redirect routing rule from listener to external site or to another listener, I can't see a way to do it with existing annotations.
I guess we would need a CR to create custom routing rule, and then use that with annotation.
Maybe it is possible with rewrite rules, but I don't see how as it only seems to rewrite url paths and queries, but not the hostname.
edit: might be related or even duplicate of #534

We also often have the Situation, that we need to redirect www.domain.com to domain.com. That sould be possible with annotations

Is there any news on this feature request, and in particular, about supporting K8s services with externalName config ?
Because I work on a project where use use AGIC on prod & preprod platforms, and nginx-ingress on other test platforms (to limit costs).
And services with externalName config are supported without any problems on nginx-ingress, but AGIC gives this specific error, unluckily :
1 backendaddresspools.go:102] Code="ErrorFetchingEndpoints" Message="Endpoint not found for core/static-storage-account" 1 context.go:402] Code="ErrorFetchingEndpoints" Message="Endpoint not found for core/static-storage-account"
When I check App Gateway configuration, listener and routing rules are correctly created by AGIC, but it points the the default (empty) backend pool.
Moreover, setting FQDN as backend pool value in App Gateway is possible, so at first glance, there is no technical difficulty on App Gateway side to implement this.


Machine batch is always up to date

I have a simple recipe that creates two machines in parallel. I'm using my own driver implementation for XenServer, but it's not important in that case, I think.
When I run chef client machine_batch is always up to date and machines are not created.
* machine_batch[default] action converge[2015-12-14T08:56:24+01:00] INFO: Processing machine_batch[default] action converge (cse_env::testenv_xen line 28)
 (up to date)

Without machine_batch, everything goes well and machines are created (synchronously, of course).
Do you have any idea what the problem might be?
Probably I'm doing something wrong, but I don't know what.
Snippet of my recipe:
machine_batch do
  machine 'linux' do
    chef_server :chef_server_url => chef_zero_server.url
    machine_options(
      xen_options: {
        template_id: '7280a723-ed10-596c-73bb-0873c3e7fe17'
      },
      convergence_options: {
        chef_version: '12.4.1'
      }
    )
    role 'linux_dev_server'
  end

  machine 'windows' do
    chef_server :chef_server_url => chef_zero_server.url
    machine_options(
      xen_options: {
        template_id: '9133ae43-a829-660f-2f1d-00135981b99d'
      },
      convergence_options: {
        chef_version: '12.4.1'
      }
    )
    role 'win_dev_server'
  end
end

Same problem here!

I had similar issues in the version of chef provisioning around early-mid december.
One thing to try though is adding an action to your machine_batch with your desired action.. i think the default action for machine_batch is :converge   so it may lead to undesired results if you call it without an action - specially if your intent was to do :setup
so short story: if you call machine_batch without an action even if you specify in the machine to do an action :setup or similar.. it will still :converge them  unless you set the action in machine_batch to be the action you desire...
also this may not be your issue but it's worth mentioning!
machine_batch do
  action :setup


Download APK removed from Google Play

Hello there!
Is any way to download an old APK files from Google Play, that were removed officially from Google Play?
For example: com.herogame.gplay.theoutlived
Google Play: https://play.google.com/store/apps/details?id=com.herogame.gplay.theoutlived
APK.support: https://apk.support/app/com.herogame.gplay.theoutlived
I don't believe, that APK.Support keeps all old APK files on their own servers. So, i think, that is possible to download old APK files from Google Play. But, how to do this?

Hi @PendalF89, I actually never tried to download applications that are not available anymore from the Play Store, so I'm not 100% sure, but I believe that's not possible.

Hi @PendalF89
Specifically on the app you sent, it is indeed stored on a server that does not belong to Google Play as seen in the following image:

But in general, it's possible that when Google Play removes an app, they don't delete the files from their servers, and so - if you have a direct link to the apk file (play.playstoreapi.com), it may well continue to work even after Google Play removes the app from the Store.

Thank you for your replies guys!
I was doing an experiment with direct links to Google Play, for example:
https://play.googleapis.com/download/by-token/download?token=...
redirects to:
https://some-secret-site.com/play-apps-download-default/download/by-id/...
Unfortunately, these links live for about 2 days, but they also have some get parameters that can affect the lifetime of links. I saved several such links today and want to check in a few days if I can get a file from them by changing the get parameters.

This link is from two weeks ago and still works

But, it is not Google domain: https://www.whois.com/whois/playstoreapi.com
I also thought at first that these were links from Google Play, but no, this domain does not belong to Google.
Unfortunately, your link is not starting download for me.

I do not know the name of the domain registered but I get the download link after I perform mitm on Google Play.

And why does the link not work for you? I do not know. I tried to download from several devices that are not connected to the same network and in all of them the application downloads ..
This may be a location limitation or other similar limitation.

Try to download from the actual link.

This link works fine! How many days is this link?

Why does it matter how long the link lasts? Just generate a valid link, and download right away. If youre wanting to host the links on your own site, thats not going to work. Same with YouTube video links, or links from many other sites. You'll either need to generate a valid link on request, or download and rehost the actual APKs

@david-lev What site is that and how are you obtaining the links?

@alanjsebas its from the Google API:
https://github.com/89z/googleplay/blob/v1.6.9/auth.go#L52-L87

@david-lev What site is that and how are you obtaining the links?

@alanjsebas The site I used before is https://apk.support/apk-downloader
But they started pulling files from other sites, too, so pay attention to the storage address of the apk file before you download.


Vote for release of 1.1.0-rc1 of distribution-spec

We need 6 approvals from the current 8 maintainers on mailing list as per - https://github.com/opencontainers/distribution-spec/blob/main/GOVERNANCE.md#voting to vote for tagging 1dfa4f4 as v1.1.0-rc1

[x] Brandon Mitchell (@sudo-bmitch)
[x] Derek McGowan (@dmcgowan)
[x] Jimmy Zelinskie (@jzelinskie)
[ ] Jon Johnson (@jonjohnsonjr)
[x] Josh Dolitsky (@jdolitsky)
[x] Mike Brown (@mikebrow)
[x] Stephen Day (@stevvooe)
[x] Vincent Batts (@vbatts)

The next step in the process after the email votes would be to merge the PR https://github.com/opencontainers/distribution-spec/pull/348 and tag the commit voted upon so that the release may proceed.
Calling @opencontainers/distribution-spec-maintainers.
This issue was created as per discussion on the OCI call and help from multiple members on that call.

https://groups.google.com/a/opencontainers.org/g/dev/c/PMgIqSNi14g


ModuleNotFoundError: No module named 'cuda_functional'

hi ,I have met this error.
ModuleNotFoundError: No module named 'cuda_functional'
how to solve it.
I have installed SRU

Hi,
it looks like a problem with the version of SRU you are using. This code is using sru==2.1.3
Could you give a bit more context of when this error occur?

I installed sru==2.1.3,and I solved  this problem.thanks a lot!
but I made another problem, the training is so slowly, I have run the train.py for at least 30 minutes,but it still in the epoch 0  [0/3541]?
is there something wrong ?

@Lkn1995 : Could you kindly tell me how exactly you solved the issue: ModuleNotFoundError: No module named 'cuda_functional'
I have also installed SRU==2.1.3.
Along with this, did u also encounter the issue from dataset.py: from visual_genome import local as vg, No module found.
Could you kindly help me out with this..
Thanks
Bela

https://github.com/asappresearch/sru,download the SRU and
pip install -r requirements.txt

sorry,I have not met this problem in dataset.py

https://github.com/asappresearch/sru
download the SRU and
pip install -r requirements.txt

@Lkn1995:
Hello
Thank you for your response
Regards
Bela

@Lkn1995
For the link which you sent: it uninstalls the pytorch=1.0 and re-installs pytorch=1.5, wouldn't that be an issue?
And if I may ask- how did you install pytorch=1.0?
conda install pytorch==1.0.0 torchvision==0.2.1 cuda90 -c pytorch
Could you plz help. And it keeps giving segmentation fault even after I install SRU the way u told to.
Regards
Bela


Pretrained models

Hello Yuan,
great work and thank you for making it available for other researchers.
I am currently testing deep learning models on my audio dataset to see which model performs better.
I saw you made available the pretrained EfficientNet B2 models with 4-headed attention. I was wondering if it would be possible to download other pretrained models too, e.g. EfficientNet B2 with Mean Pooling.
Thank you in advance,
Annalisa

Hi Annalisa,
Thanks for your interest.
This is the one (without weight averaging) I have on my server. Note it is a model created by my experiment code, I did a cleanup before I release the code, so it might not fit the current code. You could have a try.
In one of my new projects, I have a new implementation of the mean pooling model using the torchvision implementation. You can play with it at https://colab.research.google.com/github/YuanGongND/vocalsound/blob/main/colab/VocalSound.ipynb. Nevertheless, the model is not pretrained with AudioSet.
-Yuan


Fix for headers ending with blank

Under Internet Explorer, we had an issue with headers ending with a blank last element, thus crashing on a undefined parts[1] unable to be sliced.

I'll publish this soon. Thanks!


Replace internal functionality from mr-ui with Radix

Building accessible high-quality UI components are hard and require constant maintenance. For example, here's a great article on building a battle-tested context menu. It's hard work!  Radix is a suite of accessible, high-quality UI components built like unopinionated primitives that adopt modern React conventions. Here's an example of creating a context menu and it ticks off all the boxes. mr-ui suffers from issues today and lacks features we don't have the time to invest in (and why reinvent the wheel).
mr-ui should be a wrapper of our design system that uses Radix internally.

Decisions from discussions today is to start with two:

An existing mr-ui component AND
A new one we are interested in including (toast UI)

cc @VLuisa  @badiuoanaalexandra

We're heading in this direction with the last few PRs so I'm going to close this out.


Add 9.1 Extension and PGXN Support

I moved things around a bit, but made no code changes.
Are the documentation files in Textile format? If so, I'd like to change their extension from .txt to .textile. This will allow PGXN to format them nicely, like is done for [pgTAP(pgxn.org/extension/pgtap). If you're interested I'd also be happy to add more stuff to the README (and is it Textile, too?), similar to the semver README.

Thanks, merged.
The docs are in asciidoc.  Although the README is not rendered anywhere so it's
OK to reformat it with something that plays well with PGXN and github.  But I want to
be more careful with other docs - I don't want work with too many random formats.


[Dependency Scanning] Inherit target SDK name and version for textual interface build recipes

Otherwise they get built with an empty SDK name string and we do not get the benefit of the SDK name compatibility check in case they are loading modules from an incompatible SDK
Resolves rdar://135972810

@swift-ci smoke test

Thank you, that will be useful!
In what case do we need this treatment for the flags, when they affect dependency loading?

When we are actually executing the task to build a textual interface into a binary module, we need these flags when such tasks are considering whether an existing binary module candidate is considered up-to-date and valid to use so that we can create a forwarding module instead of doing the work to generate an "actual" binary module from the textual interface.


Build with Spack using GCC 11 fails with various namespace errors

On trying to install NESO using Spack in a clean spack/ubuntu-jammy Docker container following the instructions here (other than pinning intel-oneapi-compilers package version to 2022.1.0 to avoid this issue) the build of neso-particles with GCC 11.3 fails with a series of namespace related errors:
/usr/include/c++/11/cinttypes:58:11: error: 'imaxdiv_t' has not been declared in '::'
   58 |   using ::imaxdiv_t;
/usr/include/c++/11/cinttypes:61:11: error: 'imaxabs' has not been declared in '::'
   61 |   using ::imaxabs;
/usr/include/c++/11/cinttypes:62:11: error: 'imaxdiv' has not been declared in '::'
   62 |   using ::imaxdiv;
/usr/include/c++/11/cinttypes:68:11: error: 'strtoimax' has not been declared in '::'
   68 |   using ::strtoimax;
/usr/include/c++/11/cinttypes:69:11: error: 'strtoumax' has not been declared in '::'
   69 |   using ::strtoumax;
/usr/include/c++/11/cinttypes:72:11: error: 'wcstoimax' has not been declared in '::'
   72 |   using ::wcstoimax;
/usr/include/c++/11/cinttypes:73:11: error: 'wcstoumax' has not been declared in '::'
   73 |   using ::wcstoumax;
/root/NESO/neso-particles/include/particle_io.hpp:21:8: error: 'string' in namespace 'NESO::Particles::std' does not name a type
   21 |   std::string filename;
/root/NESO/neso-particles/include/particle_io.hpp:28:8: error: 'string' in namespace 'NESO::Particles::std' does not name a type
   28 |   std::string position_labels[3] = {"x", "y", "z"};
/root/NESO/neso-particles/include/particle_io.hpp:194:21: error: expected ')' before 'filename'
  194 |   H5Part(std::string filename, ParticleGroupSharedPtr particle_group, T... args)

...

I get the same errors when trying to install with Spack using GCC 10.3 directly on my Ubuntu 20.04 system.
The first series of * has not been declared in '::' errors seem to arise from an include in a header file H5public.h which is itself included from hdf5.h and some of the latter errors also seems to relate to HDF5 types / objects so I'm not sure if this is some upstream issue with the hdf5 Spack package version that is getting picked up (hdf5-1.14.1-2).
As the Git submodule reference in NESO points to c63f79d it's possible this has been fixed on main if it a problem on the NESO-Particles side (I wasn't sure if this issue should be tracked here or the main NESO repository - feel free to transfer).
Apologies if there  something obvious I'm doing wrong here or that is needed to fix this. This is my first time using Spack and my attempts to diagnose and fix the errors myself haven't gotten anywhere!

Dockerfile to reproduce
FROM spack/ubuntu-jammy:latest
ENV NESO_ROOT=/root/NESO
RUN spack install<EMAIL_ADDRESS>&& \
    spack load intel-oneapi-compilers && \
    spack compiler find && \
    spack unload intel-oneapi-compilers
RUN git clone --recurse-submodules -j4 https://github.com/ExCALIBUR-NEPTUNE/NESO.git $NESO_ROOT
WORKDIR $NESO_ROOT
RUN . activate && spack install

 Error output from Spack for `neso-particles` install stage (truncated to fit into issue comment character limit)
==> Installing neso-particles-working-s6umyaaliectjpdxwmr7okgikpn7ovzl [116/118]
==> No binary for neso-particles-working-s6umyaaliectjpdxwmr7okgikpn7ovzl found: installing from source
==> No patches needed for neso-particles
==> neso-particles: Executing phase: 'cmake'
==> neso-particles: Executing phase: 'build'
==> Error: ProcessError: Command exited with status 2:
    '/opt/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-11.3.0/gmake-4.4.1-xgnqusnc3orrautjhhmz7wa73nr7vyts/bin/make' '-j8'

372 errors found in build log:
     132     cd /root/NESO/neso-particles/spack-build-s6umyaa/test && /opt/spac
             k/opt/spack/linux-ubuntu22.04-skylake/gcc-11.3.0/hipsycl-0.9.4-7tf
             ch4qrqrmhfinf4w5yb2eu4icie5c3/lib/cmake/hipSYCL/syclcc-launcher --
             launcher-cxx-compiler=/opt/spack/lib/spack/env/gcc/g++ --launcher-
             syclcc=/opt/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-11.3.0/h
             ipsycl-0.9.4-7tfch4qrqrmhfinf4w5yb2eu4icie5c3/bin/syclcc-clang  --
             hipsycl-platform=omp /opt/spack/lib/spack/env/gcc/g++ -DGPU_SELECT
             OR=0 -DGTEST_LINKED_AS_SHARED_LIBRARY=1 -DH5_BUILT_AS_DYNAMIC_LIB
             -DNESO_PARTICLES_DEVICE_TYPE_CPU -DNESO_PARTICLES_HDF5 -D_FILE_OFF
             SET_BITS=64 -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -D_LARGEFILE_SOURC
             E -D_POSIX_C_SOURCE=200809L -I/root/NESO/neso-particles/include -i
             system /opt/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-11.3.0/i
             ntel-oneapi-mpi-2021.10.0-wzxpzgsiyixjgmjct3cwi7sflyo2ect2/mpi/202
             1.10.0/include -isystem /opt/spack/opt/spack/linux-ubuntu22.04-sky
             lake/gcc-11.3.0/intel-oneapi-mpi-2021.10.0-wzxpzgsiyixjgmjct3cwi7s
             flyo2ect2/include -isystem /opt/spack/opt/spack/linux-ubuntu22.04-
             skylake/gcc-11.3.0/hdf5-1.14.1-2-hgrekohrqqra2nwh4sh4wbuy53yniut3/
             include -isystem /opt/spack/opt/spack/linux-ubuntu22.04-skylake/gc
             c-11.3.0/googletest-1.12.1-nwhvujj62xj3ro5hnhctk7u552onqiiu/includ
             e -isystem /opt/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-11.3
             .0/hipsycl-0.9.4-7tfch4qrqrmhfinf4w5yb2eu4icie5c3/include -O3 -DND
             EBUG -std=gnu++17 -MD -MT test/CMakeFiles/test_cell_dat.dir/test_c
             ell_dat.cpp.o -MF CMakeFiles/test_cell_dat.dir/test_cell_dat.cpp.o
             .d -o CMakeFiles/test_cell_dat.dir/test_cell_dat.cpp.o -c /root/NE
             SO/neso-particles/test/test_cell_dat.cpp
     133     In file included from /opt/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-11.3.0/hdf5-1.14.1-2-hgrekohrqqra2nwh4sh4wbuy53yniut3/include/H5public.h:39,
     134                      from /opt/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-11.3.0/hdf5-1.14.1-2-hgrekohrqqra2nwh4sh4wbuy53yniut3/include/hdf5.h:21,
     135                      from /root/NESO/neso-particles/include/particle_io.hpp:14,
     136                      from /root/NESO/neso-particles/include/neso_particles.hpp:22,
     137                      from /root/NESO/neso-particles/test/test_boundary_pbc.cpp:4:
  >> 138     /usr/include/c++/11/cinttypes:58:11: error: 'imaxdiv_t' has not been declared in '::'
     139        58 |   using ::imaxdiv_t;
     140           |           ^~~~~~~~~
  >> 141     /usr/include/c++/11/cinttypes:61:11: error: 'imaxabs' has not been declared in '::'
     142        61 |   using ::imaxabs;
     143           |           ^~~~~~~
  >> 144     /usr/include/c++/11/cinttypes:62:11: error: 'imaxdiv' has not been declared in '::'
     145        62 |   using ::imaxdiv;
     146           |           ^~~~~~~
  >> 147     /usr/include/c++/11/cinttypes:68:11: error: 'strtoimax' has not been declared in '::'
     148        68 |   using ::strtoimax;
     149           |           ^~~~~~~~~
  >> 150     /usr/include/c++/11/cinttypes:69:11: error: 'strtoumax' has not been declared in '::'
     151        69 |   using ::strtoumax;
     152           |           ^~~~~~~~~
  >> 153     /usr/include/c++/11/cinttypes:72:11: error: 'wcstoimax' has not been declared in '::'
     154        72 |   using ::wcstoimax;
     155           |           ^~~~~~~~~
  >> 156     /usr/include/c++/11/cinttypes:73:11: error: 'wcstoumax' has not been declared in '::'
     157        73 |   using ::wcstoumax;
     158           |           ^~~~~~~~~
     159     In file included from /root/NESO/neso-particles/include/neso_particles.hpp:22,
     160                      from /root/NESO/neso-particles/test/test_boundary_pbc.cpp:4:
  >> 161     /root/NESO/neso-particles/include/particle_io.hpp:21:8: error: 'string' in namespace 'NESO::Particles::std' does not name a type
     162        21 |   std::string filename;
     163           |        ^~~~~~
  >> 164     /root/NESO/neso-particles/include/particle_io.hpp:28:8: error: 'string' in namespace 'NESO::Particles::std' does not name a type
     165        28 |   std::string position_labels[3] = {"x", "y", "z"};
     166           |        ^~~~~~
  >> 167     /root/NESO/neso-particles/include/particle_io.hpp:194:21: error: expected ')' before 'filename'
     168       194 |   H5Part(std::string filename, ParticleGroupSharedPtr particle_group, T... args)
     169           |         ~           ^~~~~~~~~
     170           |                     )
     171     /root/NESO/neso-particles/include/particle_io.hpp: In member function 'void NESO::Particles::H5Part::write_dat_column_wise(int64_t, NESO::Particles::BufferHost<char>&, NESO::Particles::ParticleDatSharedPtr<T>, NESO::Particles::hid_t, NESO::Particles::hid_t, NESO::Particles::hid_t, NESO::Particles::hid_t, bool)':
  >> 172     /root/NESO/neso-particles/include/particle_io.hpp:95:12: error: 'string' is not a member of 'NESO::Particles::std'
     173        95 |       std::string name;
     174           |            ^~~~~~
     175     /root/NESO/neso-particles/include/particle_io.hpp:95:12: note: suggested alternatives:
     176     In file included from /usr/include/c++/11/iosfwd:39,
     177                      from /usr/include/c++/11/bits/shared_ptr.h:52,
     178                      from /usr/include/c++/11/memory:77,

     ...

     191                      from /root/NESO/neso-particles/test/test_boundary_pbc.cpp:1:
     192     /usr/include/c++/11/string:67:11: note:   'std::pmr::string'
     193        67 |     using string    = basic_string<char>;
     194           |           ^~~~~~
     195     In file included from /root/NESO/neso-particles/include/neso_particles.hpp:22,
     196                      from /root/NESO/neso-particles/test/test_boundary _pbc.cpp:4:
  >> 197     /root/NESO/neso-particles/include/particle_io.hpp:97:9: error: 'name' was not declared in this scope
     198        97 |         name = this->position_labels[cx];
     199           |         ^~~~
     200     /root/NESO/neso-particles/include/particle_io.hpp:97:9: note: suggested alternatives:
     201     In file included from /opt/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-11.3.0/hipsycl-0.9.4-7tfch4qrqrmhfinf4w5yb2eu4icie5c3/include/hipSYCL/sycl/info/info.hpp:35,
     202                      from /opt/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-11.3.0/hipsycl-0.9.4-7tfch4qrqrmhfinf4w5yb2eu4icie5c3/include/hipSYCL/sycl/device.hpp:38,
     203                      from /opt/spack/opt/spack/linux-ubuntu22.04-skylake/gcc-11.3.0/hipsycl-0.9.4-7tfch4qrqrmhfinf4w5yb2eu4icie5c3/include/hipSYCL/sycl/buffer.hpp:51,

     ...

What version of HDF5 has been installed? Could you please post the output of spack find -v hdf5.

Could you try fixing it to version 1.12.2 and see if it builds any better with that? We'll want to make it work with more recent versions too but trying with the old one can help us understand the nature of the problem.

Not sure if this was the correct way to go about this but I reran spack install with updated specs in spack.yaml
  specs:
  - neso%oneapi ^nektar%oneapi ^intel-oneapi-mpi ^intel-oneapi-mkl ^py-numpy%intel
    ^boost%intel ^py-cython%oneapi ^dpcpp ^scotch@6 <EMAIL_ADDRESS>  - neso%gcc ^openblas ^hipsycl ^scotch@6 <EMAIL_ADDRESS>
This does appear to have fixed the above issue with building neso-particles package as that build step now completes successfully 🎉. Unfortunately I now get a different series of errors in the subsequent neso build step 😅 but will open a new issue in NESO repository for those.

Yes, that's the right way to pin the package version. I'll keep an eye for your next issue.

I've added details of errors I'm now getting to the previous issue I'd raised for problems with Intel oneAPI build on NESO repository (https://github.com/ExCALIBUR-NEPTUNE/NESO/issues/202#issuecomment-1673189299), though it is also occurring for GCC build. I'm happy to close this issue now unless you want to keep it open for tracking longer term fix.

Leave it open. I've changed the name to reflect the underlying issue.

This was fixed by #47.


Introduce marker interface for ClusterLeader

Automatically generate service of that type.
Leverage from JcrPackageReplicationStatusEventHandler and
TwitterFeedScheduler.
This closes #2492 #2498

Pull Request Test Coverage Report for Build 6288

13 of 36 (36.11%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 55.6%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

bundle/src/main/java/com/adobe/acs/commons/replication/status/impl/JcrPackageReplicationStatusEventHandler.java
12
15
80.0%

bundle/src/main/java/com/adobe/acs/commons/util/impl/DiscoveryServiceHelper.java
0
20
0.0%

Totals

Change from base Build 6264:
-0.04%

Covered Lines:
16035

Relevant Lines:
28840

💛  - Coveralls

@kwin there are 2 files w Netcentric headers in this.
Are these headers here because they were originally released under this license and they're copy/paste to this project? IIUC if did copy/paste into this project you'd have to retain the attribution to the original project, though I'm not sure if it would need to have both licenses? .. clearly IANAL

This is not about the license (ASL 2.0) but only about the copyright. If you insist on donating the copyright to Adobe that may be ok if

a reasoning is given and
this is clarified in the contributors guidelines


[AIRFLOW-6101] [AIP-21] Rename DataFlow hook & operators

Rename operators DataFlowJavaOperator, DataFlowPythonOperator, DataflowTemplateOperator, and hook DataFlowHook
Jira

[ ] My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-6101
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.
In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal (AIP).
In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Description

[ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters (not including Jira issue reference)
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does
If you implement backwards incompatible changes, please leave a note in the Updating.md so we can assign it to a appropriate release

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@47facb4). Click here to learn what that means.
The diff coverage is 96.87%.

@@            Coverage Diff            @@
##             master     #552   +/-   ##
=========================================
  Coverage          ?   84.08%
=========================================
  Files             ?      677
  Lines             ?    38374
  Branches          ?        0
=========================================
  Hits              ?    32267
  Misses            ?     6107
  Partials          ?        0

Impacted Files
Coverage Δ

airflow/gcp/utils/mlengine_operator_utils.py
95.34% <100%> (ø)

airflow/contrib/hooks/gcp_dataflow_hook.py
100% <100%> (ø)

airflow/gcp/hooks/dataflow.py
89.28% <100%> (ø)

airflow/gcp/operators/dataflow.py
99.07% <100%> (ø)

airflow/contrib/operators/dataflow_operator.py
100% <100%> (ø)

airflow/gcp/example_dags/example_dataflow.py
93.33% <66.66%> (ø)

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 47facb4...054d185. Read the comment docs.


Invoking "make -j4 -l4" failed

Hello all ... I need help...
Ubuntu 18.04
ROS Melodic
when catkin_make :
.
.
.
[ 67%] Built target turtlebot3_example_generate_messages_eus
[ 73%] Built target turtlebot3_example_generate_messages_lisp
[ 75%] Built target realsense_gazebo_plugin
[ 82%] Built target turtlebot3_example_generate_messages_py
[ 88%] Built target turtlebot3_example_generate_messages_cpp
make[2]: *** No rule to make target 'darknet_ros/darknet_ros/CMakeFiles/darknet_ros_lib.dir/build'.  Stop.
CMakeFiles/Makefile2:3146: recipe for target 'darknet_ros/darknet_ros/CMakeFiles/darknet_ros_lib.dir/all' failed
make[1]: *** [darknet_ros/darknet_ros/CMakeFiles/darknet_ros_lib.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 88%] Built target darknet_ros_msgs_generate_messages
[ 94%] Built target turtlebot3_example_generate_messages_nodejs
[ 94%] Built target realsense2_camera_generate_messages
Makefile:140: recipe for target 'all' failed
make: *** [all] Error 2
Invoking "make -j4 -l4" failed

Please follow the instructions in the readme. Make sure to clone recursively.

If you want help you need to formulate a clear question and provide context: what did you do; how can we reproduce your problem. Thanks for your understanding.


Chain API

It's often handy to query for a specific thing, and based on that query return a related type. For example, you could find a user by its ID, and then return all its posts. While you could directly query for all posts which belong to a user, sometimes it's easier to do it like in the former way.
Usual:
posts, err := client.Post.FindMany(
  Post.Author.Where(
    User.Comments.Some(
      Comment.ID.Equals("123"),
    ),
  ),
).Exec(ctx)

// or
posts, err := client.Post.FindMany(Post.Author.Where(User.Comments.Some(Comment.ID.Equals("123")))).Exec(ctx)

Chain API:
posts, err := client.Comment.FindOne(db.Comment.ID.Equals("comment-1")).GetAuthor().GetPosts().Exec(ctx)

The underlying query will be the same.

On the other hand, it might be worth considering not adding this feature.
While it may make querying for specific data more simple, it comes with a cost.
First of all, this doesn't seem the Go-way, since the Go guidelines specify "there should be only one way to do a specific thing" – which this API violates. You don't need the fluent API; it just introduces a second way to do something; you can still query anything without the fluent API.
Also, while it simplifies querying for specific data, it may make it too easy. For example, there's a good chance that we'll introduce querying from many to many relations with the Fluent API – which looks simple in code, but will actually result in a big, complex SQL query.
Currently, the fluent API on an internal level (prisma query language) is also not very efficient, which means many sql queries are executed instead of just one. Instead, we could just as well tell users to query for additional data with the With()-syntax and then just discard the stuff they don't need themselves (that's basically what the js client does).

Work is dropped on this feature for now, because this is lacking a proper implementation in the query engine, and I now have doubts on whether this feature is actually useful.


Make collection generator command

because collections are awesome.

not sure if i did this right. i never know if i'm syncing my fork to the upstream correctly. any suggestions would be appreciated if i didn't.

do we care if it passes on 7.1 yet?

PHP 7.1 is segfaulting. We need to contact the release manager at some point to let them know.

Probably will hold off on this PR. I'm not totally sure it's a use case that happens often enough to warrant a generator at this point. Thanks.

thanks for considering it. One thing I think would be cool with it is similar to how we can php artisan make:model --migration, we could append on php artisan make:model --migration --collection.  maybe this is more of an interesting use case.


Prevent the app from being suspended while refreshing a token

Correct @colintremblay-okta, those APIs are only available on the listed platforms.  I left the class in place for other unsupported platforms as a stub though, just in case we need to add support for equivalent capabilities on macOS, Linux, etc.


no matching manifest for unknown in the manifest list entries

Problem encountered on https://dotnet.microsoft.com/learn/web/aspnet-microservice-tutorial/docker-image
Operating System: windows
Error running docker build step:

Sending build context to Docker daemon  1.158MB

Step 1/14 : FROM microsoft/dotnet:2.2-aspnetcore-runtime AS base

2.2-aspnetcore-runtime: Pulling from microsoft/dotnet

no matching manifest for unknown in the manifest list entries

No image was built.
docker --version

Docker version 18.09.2, build 6247962
ver

Microsoft Windows [Version 10.0.15063]

Simon

Probably my version on Windows 10 is too old. Shall try Server 2019.


Discussion:  Which providers do we want to support?

Twitter is an initial given.

[ ] Instagram
[x] Mastadon
[ ] BlueSky
[ ] Threads
[ ] Facebook
[ ] TikTok
[ ] YouTube
[ ] LinkedIn

Twitch tags?

Have been checking Instagram and is a royal pain to get anything working here. You need to create 2 new accounts, one for Instagram and the other for Facebook to even gain very basic access to the API Graph, so far I haven't been able to try anything since you need some time with your account created to start trying.
If you ask me, this should not be a good starting point for the providers. This needs more investigation or someone that already has some good experience with this particular platform.
Here is the basic documentation https://developers.facebook.com/docs/instagram-api/getting-started

It looks like the Instagram hashtag search is simple and there is a hard
limit on hashtags per week:
https://developers.facebook.com/docs/instagram-api/guides/hashtag-search
Jeff
On Tue, Jul 11, 2023 at 7:38 PM Rodrigo Alarcón @.***>
wrote:

Have been checking Instagram and is a royal pain to get anything working
here. You need to create 2 new accounts, one for Instagram and the other
for Facebook to even gain very basic access to the API Graph, so far I
haven't been able to try anything since you need some time with your
account created to start trying.
If you ask me, this should not be a good starting point for the providers.
This needs more investigation or someone that already has some good
experience with this particular platform.
Here is the basic documentation
https://developers.facebook.com/docs/instagram-api/getting-started
http://url
—
Reply to this email directly, view it on GitHub
https://github.com/FritzAndFriends/TagzApp/issues/4#issuecomment-1631644155
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAATF4LB4L4ZOTGKWXK3SVDXPXPXLBFKMF2HI4TJMJ2XIZLTSWBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVI2TOMRTGU2TGNJZGKSG4YLNMWUWQYLTL5WGCYTFNSBKK5TBNR2WLKRVG4ZDGNJVGM3DAN5ENZQW2ZNJNBQXGX3MMFRGK3FMON2WE2TFMN2F65DZOBS2YSLTON2WKQ3PNVWWK3TUUZ2G64DJMNZZJAVEOR4XAZNKOJSXA33TNF2G64TZUV3GC3DVMWUTMNRVGEZDIOBTGKBKI5DZOBS2K2LTON2WLJLWMFWHKZNKGE3TSOJRGI3DGMJRQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKRVG4ZDGNJVGM2TSMUCUR2HS4DFUVWGCYTFNSSXMYLMOVS2UNJXGIZTKNJTGYYDPJ3UOJUWOZ3FOKTGG4TFMF2GK
.
You are receiving this email because you authored the thread.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
.

Twitch tags?

Twitch tags are associated with live streams, not videos or clips.  I don't think that will work for this

I'd like to see support for:

Mastadon
Threads
Instagram
Facebook
YouTube

For me it's:

Mastodon
Youtube
Linkedin

The numbers represent the priority in my view (I know that this will be different for everyone, just my preference).


PR 27 changed behavior of extras path

I just saw that https://github.com/niqdev/packtpub-crawler/pull/27 changed the behavior of the path.extras value.
Before it was used on it's own equally to the download path:
directory = self.__config.get('path', 'path.extras')
now it's appended
` if self.__config.has_option('path', 'path.group'):
        folder_name = self.info['title'].encode('ascii', 'ignore').replace(' ', '_') + \
                      self.info['author'].encode('ascii', 'ignore').replace(' ', '_')

        directory = base_path + join(self.__config.get('path', 'path.ebooks'), folder_name,         self.__config.get('path', 'path.extras'))
    else:
        directory = base_path + self.__config.get('path', 'path.extras')`

@lszeremeta could you have a look? Since the extras be quite large, it should be possible to move them somewhere else.
Can you also add your changes to the example prod file and the readme? It took me quite some time to figure out what was happening.
Otherwise, if we decide which behavior we want to keep, I can refactor it while working on https://github.com/niqdev/packtpub-crawler/pull/56

@juzim hi I can't test the new changes now..I'll merge the pr next week. Is it stable or require more changes? Thanks

I have closed the PR.
I was hoping that @lszeremeta might take a look himself because I don't have much time at the moment.
When we decide that we want the extras path independent from the download path, I will include the changes in my PR. I also need this for the long awaited download all functionality that willmight be done soon.


It requires specifying port number 443 when authenticating via username/password

The current implementation will keep using default TCP port number 8080 from underneath DB-API driver even using HTTPS:
https://github.com/dungdm93/sqlalchemy-trino/blob/5aea36225cb8352cede5df4499b7d9628011ae50/sqlalchemy_trino/dialect.py#L92-L94
However, this could be documented or it will fail the connection with Connection timeout to port 8080.
Background
I found this error message from superset:
F [SupersetError(message="HTTPSConnectionPool(host='<trino-url>', port=8080): Max retries exceeded with url: /v1/statement (Caused by ConnectTimeoutError(<urllib3.connection.HTTPSConnection object at 0x7f722688acd0>, 'Connection to <trino-url> timed out. (connect timeout=30.0)'))", error_type=<SupersetErrorType.GENERIC_DB_ENGINE_ERROR: 'GENERIC_DB_ENGINE_ERROR'>, level=<ErrorLevel.ERROR: 'error'>, extra={'engine_name': 'Trino', 'issue_codes': [{'code': 1002, 'message': 'Issue 1002 - The database returned an unexpected error.'}]})]

Which is obviously a problem of the port number (should use HTTPS port number instead of 8080)

will follow up under https://github.com/trinodb/trino-python-client/issues/94


Add Stop

https://github.com/ivoba/stop
Stop is a lightweight Dumper for PHP 5.3+

shortcut functions
some more infos as File, Line & Memory
some nicer rendering with Twitter Bootstrap,
options for return or continue & hide which will print to javascript console
*disable Stop for prod env
autoloading
extensibility, if youd like to use jqueryUI f.e just subclass the Dumper and set the class
context awareness: if you are in console it will render in text mode, if in ajax mode it will render in json mode
dumper for json strings
stop_type as a better version of var_dump(get_class($var));exit;

Thanks for the suggestion.


Unauthorized data preview within the same Dataset

Describe the bug
Currently the data classification is only at the Dataset level (Unclassified/ Official/ Secret). When a Dataset contains multiple tables, when a user request access for only 1 table within the Dataset, once it is granted, the user will be able to view ALL the other tables Preview Data.
How to Reproduce
*P.S. Please do not attach files as it's considered a security risk. Add code snippets directly in the message body as much as possible.*

Create a dataset with Classification set to "Official"
Create 2 different tables within the dataset
User request access for only 1 table in the dataset
Grant access to the user
User will be able to preview data for both tables

Expected behavior
Users should only be able to preview data if they are granted access to the corresponding tables (unless it is an Unclassified dataset).
Your project
No response
Screenshots

OS
AWS Deployment
Python version
3.8
AWS data.all version
1.2.2
Additional context
No response

Hi @aaronchong888 - thanks for calling this out! I was able to replicate this bug and am working on pushing a fix in this PR https://github.com/awslabs/aws-dataall/pull/265


Pick some new rules for eslint

To make a more consistent style, we should use more eslint rules.
For example, I think we should decide:

Space around keywords and other spacing rules
Prefer const over let over var
CamelCase or not
No mixed operators

I'm not advocating for any particular style, I'm just saying we should choose some more rules to make it more consistent.

Prettier is used now (cf472a5430f4c55a937c864e17b392e46f3e6ddd)


[WIP] Browser action

Issues

#12
#13

Codecov Report

Merging #14 into develop will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff           @@
##           develop    #14   +/-   ##
======================================
  Coverage      100%   100%
======================================
  Files           12     12
  Lines          216    216
  Branches        13     13
======================================
  Hits           216    216

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 8458ac7...4cc65a7. Read the comment docs.


guardian farms (possible mob spawns?)

Put the latest version of ViaVerison in and it seems to be effecting mob spawns. guardian farms seems to be not working a lot of the time then they work for a few mins then just completely stop. Seems to be only effecting guardian farms but could also be effecting all mob spawns.

We only touch Spigot at packet level, this is not caused by ViaVersion.


[Bug] 更新抽卡记录失败

Checklist

[X] My issue was not mentioned by others, and it is not a duplicate issue.

Description
原神更新抽卡记录失败，清除缓存无法解决，请求指导
Reproduction Steps
原神更新抽卡记录失败，清除缓存无法解决，请求指导
Expected Behavior
No response
Screenshots

Starward Version
0.13.0
Windows Version
19044.3086
Log
SqliteException SQLite Error 8: 'attempt to write a readonly database'

Additional Context
No response

管理员权限启动

已解决


Should Node 14 be supported?

aws lambda runtime offers Node 14 now.
the code in this repo seems to support either 12 or 10.

Hey @dimaqq, thank you for the issue, indeed. will update it


Update check_graylog_node for graylog 2.3.1

On graylog 2.3.1 version cannot parse json file from graylog server address with api at the end of URL.
If we remove api sub address, script can get json info.

This would simply depend on your server configuration. However, I agree the CURL_BASE_CMD could be brought up to give more clarity.


Update configuration.md for role name check

fixed links to other docs on the web (name standard for namespace and role)
added hint for extra freedom with a computed fully qualified role name

if that were code i would add the label 'bug'.
but as its only documentation, i would rather add the label 'minor'.
as of now i cant see any "gear" symbol or edit button that would allow me to add any label at all.

@ssbarnea @audgirka @ziegenberg - are you interested in participating with this little change?

if that were code i would add the label 'bug'. but as its only documentation, i would rather add the label 'minor'. as of now i cant see any "gear" symbol or edit button that would allow me to add any label at all.

only the label is still /open/.
please assist, so this fix can continue. thank you.


Flannel doesn't work in master with k8s 1.13

rancher/rancher:master 02/12
Steps:

Create a custom cluster
Select Flannel
Use default k8s version 1.13

Results:
Node is always in Unavailable state. It works well if we select k8s 1.12
rancher/rancher:master

Can you check if this solves it:
kubectl -n kube-system patch ds/kube-flannel --type=merge -p '{"spec":{"template":{"spec":{"tolerations":[{"key":"node-role.kubernetes.io/controlplane","effect":"NoSchedule","value":"true"},{"key":"node-role.kubernetes.io/etcd","effect":"NoExecute","value":"true"},{"key":"node.kubernetes.io/not-ready","effect":"NoSchedule","operator":"Exists"}]}}}}'
If so, we'll need to review: https://github.com/rancher/rke/pull/1025

@superseb Yes. You command resolves it!

verified on rancher:master (02/13/2019)
Kubernetes version: v1.13.1
Network Provider: Flannel


keypirinha trojan found

Keypirinha Zip VirusTotal
Keypirinha Exe VirusTotal
Related Issues: Keypirinha/Keypirinha#453
Basically, false positive because of no code signing


repeating code, unmanageable..

Trying to complete lessons, but code is becoming unmanageable:

flags auto duplicate themselves, so instead of <p> I get <pp>
same with content, hello paragraph becomes hello world hello world
it is undeleteable as every time I move the cursor it repeats again.

Browser Information

Mozilla Firefox for Mobile, Version 44 (I believe)
Android 5.1.1

Your Code
If relevant(it's not)

Screenshot
Edited format for readability ~ @raisedadead

Hey @extrememachinist, What is your issue about? Could you be more specific? What do you mean by "flags" and "hello world" duplicating?

Okay, while navigating and participating in the html code clinic, I attempted (several times, reload, cancel code, close browser...ect) to correct the problem of duplicate anchors as well as duplicate text to no avail. Thus, I am here

Are you talking about the HTML/CSS challenges? If so, which challenge in particular?

Yes the HTML challenges. All of the challenges from  paragraph on..
On Fri, Feb 26, 2016 at 2:24 AM, Akira Laine<EMAIL_ADDRESS>wrote:

Are you talking about the HTML/CSS challenges? If so, which challenge in
particular?
—
Reply to this email directly or view it on GitHub
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/7259#issuecomment-189206406
.

I believe this is an android (or mobile) specific problem. It's been a while since I've seen it, but this used to happen to me on Chrome Android. It makes the editor pretty much unusable.

Okay, I understand completely. Thank you for the thorough follow up
and concern. I really appreciate all you've done.
On 2/26/16, Logan Tegman<EMAIL_ADDRESS>wrote:

I believe this is an android (or mobile) specific problem. It's been a while
since I've seen it, but this used to happen to me on Chrome Android. It
makes the editor pretty much unusable.

Reply to this email directly or view it on GitHub:
https://github.com/FreeCodeCamp/FreeCodeCamp/issues/7259#issuecomment-189519724

@extrememachinist can you confirm whether this is still happening on Android?


Files specification is too complicated

The specification has us carrying around bits and pieces of file names.  This is fiddly and error-prone, especially for languages that aren't very good at string manipulation.
Instead, we should simplify to the current file being a file name and/or path; and the next and prev files, if present, being the entire file name.  Zipping the files separately should be okay (otherwise really huge data sets might be a pain to work with).

This is a possible improvement.  Since I have a large backlog of changes I need to implement for the Python version ahead of the conference, is it possible to leave this as a potential change for the future?  I am curious to hear feedback from other labs about the format as well; perhaps they will have feedback that will cause us to prioritize certain changes.

I think I was the one who introduced the format but in retrospect I think it's just too error-prone to stay.  The problem in addition to complexity is that it's easy to get it wrong; if you have files wm1.wcon through wm12.wcon and you have 1 as the last bit of the file, it's not very hard to start using the same rule from wm11.wcon as wm1.wcon--even though wm1.wcon says 11 in its next files, if you were using local just-the-previous-and-next files for wm11 you might encode its last digit as 1, etc..
So I'm fine with leaving it out as long as possible, but I think we'd better fix that design flaw before we release it to people.  If I get time to fix the Python implementation, would that help?

@MichaelCurrie - I had a look at the Python code (around line 660 in wcon_parser.py) and it's pretty straightforward.  The code already doesn't handle writing multiple files, just reading.  I can make the change if it would help.

Sure if you want to PR it that would be a big help!  Thanks


Syntax highlighting for wdiff

(Original issue 960 created by sjackman on 2014-03-06T20:28:56.282625+00:00)
I would love to see syntax highlighting for wdiff. A wdiff file looks like so:
➜  ~  echo 'I ate a purple banana.' >a
➜  ~  echo 'I ate a yellow banana.' >b
➜  ~  wdiff a b
I ate a [-purple-] {+yellow+} banana.

(Original comment by hhsprings on 2015-11-02T13:04:51.300515+00:00)
Do you mean wdiff -l (or wdiff -t) is insufficient? And, do you mean you want it outside of terminal (for example html)?
I think to emulate wdiff -l (wdiff -t) is out of target of pygments, these aren't 'syntax', and to highlight the output of wdiff without option is less effective than wdiff -l. If you just want colorized wdiff, I recommend to use wdiff itself.
But if you want 'syntax hilighting' of wdiff output in the sense of verbatim (for example, in order to use in your blog (etc.)), I think this is not difficult to implement  the lexer, and it's easy to contribute!
P.S.
See #770 also.

(Original comment by sjackman on 2015-11-02T16:43:03.296154+00:00)
I want to commit wdiff output to GitHub gist and have removed text highlighted in red and inserted text highlighted in green. I don't want ANSI escape codes emulated.

(Original comment by hhsprings on 2015-11-02T17:20:29.471857+00:00)
outside of terminal, i see.
But..., I think GitHub gist don't use pygments, but Ace Editor.
Still do you want it? If so, and you mean [-purple-] can be rendered to [-purple-] (NOT red colored purple, same as normal diff output highlighting), I'll try to implement it.

(Original comment by hhsprings on 2015-11-02T17:56:01.149904+00:00)
Ouch...
me@host: ~$ cat ccc1
[-abc-] [+def+}

me@host: ~$ cat ccc2
[-ABC-] [+DEF+}

me@host: ~$ wdiff ccc1 ccc2
[-[-abc-] [+def+}-]{+[-ABC-] [+DEF+}+}

(Original comment by sjackman on 2015-11-03T01:43:35.975177+00:00)
I can use pygments with PanDoc, so this is still useful to me. The colors can be the same as line by line diff. Red for removed and green for inserted text is typical.

(Original comment by hhsprings on 2015-11-03T09:01:42.101799+00:00)
Ah PanDoc, I see.
And I'll try, but don't expect too much too soon.
Actually, I want lexers for lex(flex)/yacc(bison) etc. and I am working on those, those are heavy tasks. So, before those, I was looking for some easier exercises and found this issue.

(Original comment by hhsprings on 2015-11-03T12:23:34.326765+00:00)
done.
I'll create PR later.

(Original comment by sjackman on 2015-11-03T13:42:52.629497+00:00)
Thanks, Hiroaki!

(Original comment by hhsprings on 2015-11-04T10:18:29.617768+00:00)
You're wellcome, and done(#513).

(Original comment by birkenfeld on 2016-02-17T08:22:03.001818+00:00)
Merged in hhsprings/pygments-hhs-sub/add-wdiff-lexer (pull request #513)
Add the lexer for wdiff output. (close #960)
→ <>

(Original comment by birkenfeld on 2016-02-17T08:22:04.953057+00:00)
Merged in hhsprings/pygments-hhs-sub/add-wdiff-lexer (pull request #513)
Add the lexer for wdiff output. (close #960)
→ <>


Write a Covalentified version of the Pennylane Variational Classifier tutorial

What should we add?
Include in Covalent tutorials a version of the Pennylane variational classifier tutorial which is updated to dispatch computation using Covalent.
The tutorial should be a Jupyter notebook similar to the other tutorials in the tutorials folder linked above.
The example code in the Pennylane tutorial will need to be decorated using the Covalent SDK. For example the Cost function might look like
@ct.lattice
def square_loss(labels, predictions):
    loss = 0
    for l, p in zip(labels, predictions):
        loss = loss + (l - p) ** 2

    loss = loss / len(labels)
    return loss

The tutorial should include execution using ct.dispatch() and how to retrieve and visualize results.

related: #587 #604

thanks @RamAIbot go for it!

Can you open a draft PR so I get look at the notebook and try to see where the problem might be?

@RamAIbot are you still facing the same optimizer type conflict error that we were looking at on Saturday? If so, can you post a comment here describing the problem?

@RamAIbot the team discussed your issue and we think it's related to known issues with positional arguments. You may remember we discussed using keyword arguments in your trainer functions instead of positional arguments. Try that and let me know if it works.


Properties should not return arrays?

fxcop emits a warning for the public byte[] Timestamp { get; set; } statement:

CA1819: Properties should not return arrays

Is there an alternative construct that achieves the same result? Or, perhaps you just want to mention the fxcop warning and state that it is unavoidable and can be ignored or suppressed.

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

ID: 041e7a47-a632-132a-3c9e-db46e3782a63
Version Independent ID: a5de9c4c-56fe-416e-0801-f6acd061f25e
Content: Concurrency Tokens - EF Core
Content Source: entity-framework/core/modeling/concurrency.md
Product: entity-framework
Technology: entity-framework-core
GitHub Login: @AndriySvyryd
Microsoft Alias: avickers

@sbsw many FxCop warnings aren't necessarily appropriate for all use cases - it's pretty common to pick and choose the warnings which make sense and suppress the others. For using SQL Server timestamp, the above is correct and the warning should be suppressed.

Yes, I understand that. That's why I wrote the issue. The folks writing this documentation need to view the documentation through the eyes of everyday users. The docs provide (or at least SHOULD provide) more than just the nuts and bolts of how to do it. They also serve as templates that are copied by literally thousands of users who probably don't understand the ramifications of the code they are copying. In this particular case, copying the example code leads to a scary warning that EVERY developer who copies the code needs to decode and decide how to handle. You owe it to the developers who read these docs to mention things such as this warning, and to provide guidance. A simple note to the effect that this code will produce a particular warning in .Net 3 and above, and that the warning can be ignored or suppressed, is all it takes.

@sbsw The problem is that there are so many FxCop warnings like this. I recommend developers turn off most FxCop rules this because FxCop generates too many errors that are either plain wrong, don't apply to the code in question, and are very hard to understand.


Somewhat working Trajopt

The tesseract env and kin are not used at all. They are replaced with what we have in planning_scene, for that I copied and adjusted the needed files from trajopt_ros, i.e., problem_description and kinematic_terms

The constraint from planning interface request is converted to the constraint we need in trajopt and that is only for joint state constraint for now.

No response from tesseract is used. planning interface response is created and fed internally.

Problems:

The start state for trajopt is not set, that is probably why I get a solution that has the same joint values for all timesteps except the last timestep
start_fixed is set to false. if it is true it means: it constraints the joint values to be their initialized ones but because the start state is not set, then it creates problem. I am not sure about this.
Please ignore the followings:
There are few struct and classes that are not used
There are headers that are included in different files that might not be used.
Also in CMakeLists, there might be extra or unused packages.

@davetcoleman @BryceStevenWilley @henningkayser @felixvd @j-petit

start_fixed is set to false. if it is true it means: it constraints the joint values to be their initialized ones but because the start state is not set, then it creates problem. I am not sure about this.

This seems like a really important detail to understand. Have you been able to read through its behavior in Tesseract to understand what it does? Maybe @Levi-Armstrong could quickly shed some light on this variable

start_fixed is set to false. if it is true it means: it constraints the joint values to be their initialized ones but because the start state is not set, then it creates problem. I am not sure about this.

This seems like a really important detail to understand. Have you been able to read through its behavior in Tesseract to understand what it does? Maybe @Levi-Armstrong could quickly shed some light on this variable

https://github.com/ommmid/moveit/pull/1#discussion_r306332030

Can you share relevant diagrams explaining the relationship of the files / classes in this PR?


Supporting KangarooTwelve

I would like KangarooTwelve and MarsupilamiFourteen to be added to Multiformats as K12 is faster than SHA1, and M14 is expected to be as about as fast as SHA1 and twice as fast as SHA256.
Statistics: https://bench.cr.yp.to/results-hash.html#oki
M12 is 2.21 cpb, M14 is assumed to be 2.21*(14/12)*(168/136)=3.185 Cycles per byte
For comparison, SHA1 is 3.06 cpb, MD5 is 4.33 cpb, and SHA256 is 6.65 cpb

Do they provide any benefit over blake2b?

@Stebalien According to the benchmark KangarooTwelve is 2.92/2.21=1.32x faster than BLAKE2b

For future reference this will come in handy https://github.com/multiformats/multicodec/pull/56

I see, I was looking at a different benchmark. It appears to really depend on the CPU.
I'm not really against these but I'd like to carefully consider which ones are likely to be used for identifying content (needs a single byte code).
Do you know of any existing users of these hash functions?

@Stebalien If I were to be in charge of Multihash, I would treat the multihash ID as book indexing, where each code can have up to 4 bytes, so that many different types of hashes are included.
My hash selection criteria is as follows:

[ ] High priority: MD-hash, SHA-1/2, (SHA3, SHAKE, K12), BLAKE2, Skein (all are useful and/or common)
[ ] Mid priority: SHA competition finalists and round 3 candidates whose speed are faster than SHA256, bcrypt, scrypt, Argon2 and other PHC "special recognition"
[ ] Low priority: Other SHA competition finalists and round 3 candidates, other PHC finalists

Since BLAKE3 exists as a replacement for BLAKE2, it might be a good idea to reconsider K12.


Problem with hex args

process.argv.push('7359e0');
var argv = require('optimist').argv;
console.log(argv);

Outputs:
{
  _: [ 7359 ],
  '$0': 'node ./test.js'
}

Noticed this when trying to stop processes in fleet

... that's not hex.


fix document links in README

build badge, performance document and contribution check are link to Netflix.
fixed them link to fast-jsonapi.

@TsubasaKawajiri thank you for the update and sorry for the late reply. The reason we're slow here is because we're still in touch with the friends from Netflix in order to figure out what's the best way to move forward with the changes similar to this one...

@stas oh, I got it. Thank you reply and sorry for my inpatience. close this PR.


updated schema from APIs.io + changes on spec

New schema (used by APIs.io)
changes in spec (lower case all properties + changes in the example file)

update? :)

should be merged. sorry...not sure why I hadn't done.

It says its still open but branch is merged...let me know if there were any issues.


Update hub-planner-tutorial.md

We need these urls changed ASAP as it is causing a lot of confusion with people trying it.

@fikatown : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@fikatown @jeevansd I've added this change to private repo PR 120656, which is ready to merge when @jeevansd signs off. Thanks. We'll close this PR.

@fikatown This update has been merged in a new pull request in the private repo. I would expect to see it on the live site around midday tomorrow.


No Operation Metrics

Add no-op metrics implementation to allow code paths where metrics may or may not be available to be unified without resorting to the use of null or Optional.

@BrandonArp updated as discussed.


Link autoconf after installing autoconf213 on OS X

This needs to be tested manually on one of the Mac builders before merging.
Use --overwrite because autoconf and autoconf213 are installed, and
either one may have been linked beforehand. They overlap in the files
they provide, and Homebrew will refuse to destructively overwrite
any symlinks without an explicit flag.
There's no built-in Salt module for brew link, so for now this is a
quick fix. This provides some idempotence for repeated Salt highstate
runs by checking the directory where Homebrew keeps track of linked
packages (and linking autoconf if it is not linked). It's unknown
whether this approach properly handles updates to one or both packages.
A better approach would be to write a custom Salt state (perhaps
homebrew.linked); even if this state works properly, a custom state
would be more declarative and could be upstreamed to Salt proper.
Closes #210.
Closes servo/servo#9504.

cc @larsbergstrom

I was worried about handling version upgrades properly, so I tried testing things out manually. However, autoconf213 is already pinned to a version, and autoconf has been at 2.69 for the last ~3-4 years; homebrew won't install autoconf 2.68 anymore because of the MD5 checksum. Based on some quick searching, it doesn't seem like autoconf 2.70 will be released anytime soon. I'm comfortable punting on the question of if this handles version upgrades properly for now, as there's no good way to test it, and we can handle it if autoconf 2.70 is ever released.

For future reference:
Here are the manual test cases that I'm going to be testing. Starting from each of these states, I'll run the Salt highstate, then attempt to build servo.

[ ] Start without autoconf or autoconf213 installed
[ ] Only autoconf is already installed
[ ] Only autoconf213 is already installed
[ ] Both autoconf and autoconf213 are already installed
Let me know if you can think of any other cases to test by hand.

That's the full set of cases! Thanks again for doing all of this work :-) And I apologize for the slow builds - we're just getting CCACHE support enabled right now, and it really only helps with one part of our build (SpiderMonkey, the JS engine).

These builds are only taking ~5-6 minutes, which is pretty fast to build a whole browser :)
Once I'm done testing these cases, this should be ready for review.

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

Comments from the review on Reviewable.io

OK, all done testing.

@bors-servo r+

:pushpin: Commit 7dce6fa has been approved by larsbergstrom

:hourglass: Testing commit 7dce6fa with merge 65a4e37...

Thanks again for all your work on this - much appreciated!

:sunny: Test successful - travis

Cool, I'll see about applying this to all the Mac builders. But first, I'm off to watch Spectre!

I just checked and it looks like all the Mac builders already have autoconf linked.

@aneeshusa Sorry, I missed the earlier comment! Yes, there are a few things where we've manually "fixed" the builders (for better or worse), so we really only notice problems like this when I spin up a new builder.
I hope you enjoyed Spectre!


Google workspace timeout issue

Required items, please complete
Change(s):

See guidance below

Reason for Change(s):

See guidance below

Version Updated:

Required only for Detections/Analytic Rule templates
See guidance below

Testing Completed:

See guidance below

Checked that the validations are passing and have addressed any issues that are present:

See guidance below

Guidance <- remove section before submitting

Before submitting this PR please ensure that you have read the following sections and filled out the changes, reason for change and testing complete sections:
Thank you for your contribution to the Microsoft Sentinel Github repo.

Details of the code changes in your submitted PR.  Providing descriptions for pull requests ensures there is context to changes being made and greatly enhances the code review process.  Providing associated Issues that this resolves also easily connects the reason.

Change(s):

Updated syntax for XYZ.yaml

Reason for Change(s):

New schema used for XYZ.yaml
Resolves ISSUE #1234

Version updated:

Yes
Detections/Analytic Rule templates are required to have the version updated

The code should have been tested in a Microsoft Sentinel environment that does not have any custom parsers, functions or tables, so that you validate no incorrect syntax and execution functions properly.  If your submission requires a custom parser or function, it must be submitted with the PR.

Testing Completed:

Yes/No/Need Help

Note: If updating a detection, you must update the version field.

Before the submission has been made, please look at running the KQL and Yaml Validation Checks locally.
https://github.com/Azure/Azure-Sentinel#run-kql-validation-locally

Checked that the validations are passing and have addressed any issues that are present:

Yes/No/Need Help

Note: Let us know if you have tried fixing the validation error and need help.

References:

Guidance for Detection checks
General contribution guidance
PR validation troubleshooting

Hi
Still working on further changes.
thanks

Hi @v-muuppugund
Author has confirmed that the code is working as expected, after restarting the function app.

Thanks

Hi Still working on further changes. thanks

Done with all the changes and get it verified by customer.

Please attach test cases executed if any for all the scenarios

We have tested the scenarios but don't have test plan to attach.


Feedback aiXcelerate Aachen 2022

Feedback:

search function for callpaths in selection view to filter the callpaths
gui does not work/start on newer MacOS versions
some gui functions including weak/strong scaling selection, all right click menus, do not work when using x-/port forwarding when running extrap-gui on the cluster
measurement points plot is showing data incorrectly when using only one parameter (not very intuitive for users that don't know about it)
weak/strong scaling selection missing for other input methods than Cube files... would be easier for the user if extra-p automatically multiplies the number of processes with the measured metric than doing it manually...

Gui does not work/start on newer MacOS versions is adressed in 5bce7e9

Ignore:

some gui functions including weak/strong scaling selection, all right click menus, do not work when using x-/port forwarding when running extrap-gui on the cluster

Tool is not intended to be used like that.


update: remove under development notice

Signed-off-by: Jason Dellaluce<EMAIL_ADDRESS>What type of PR is this?
/kind documentation
Any specific area of the project related to this PR?
/area documentation
What this PR does / why we need it:
This repo is getting solid and the under development notice should be removed.
Which issue(s) this PR fixes:
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: jasondellaluce, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [jasondellaluce,leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 1e95267c8ef8891bed13bccd5da496dc2042d1fa


fix(apps/prod/jenkins/pre): fix cronjob with deno image

deno only support x86 on linux
Signed-off-by: wuhuizuo<EMAIL_ADDRESS>

/approve


The purpose of this repository

Do we still need this repository, or how we can use this tests repository?
I rewrote test to have all data in it.

After checking what else needs testing, I believe this repo can serve us still.
To cover more tests - import mcu, using templates - they require external files at the moment, therefore we can create a repo here test_templates/ where we provide templates for various tools and test exporting using templates.


urdf: 2.4.0-2 in 'foxy/distribution.yaml' [bloom]

Increasing version of package(s) in repository urdf to 2.4.0-2:

upstream repository: https://github.com/ros2/urdf.git
release repository: https://github.com/ros2-gbp/urdf-release.git
distro file: foxy/distribution.yaml
bloom version: 0.10.0
previous version for package: 2.4.0-1

urdf
* Deprecate methods that require tinyxml (#12 <https://github.com/ros2/urdf/issues/12>)
* Contributors: Dan Rose

Holding for coordinated release...


I use the skywalking chart to deploy the skywalking on the k8s,but i get the system error.

Please answer these questions before submitting your issue.

Why do you submit this issue?
[ ] Question or discussion

Question

I use the skywalking chart to deploy the skywalking on the k8s,but i get the system error.

Bug

Which version of SkyWalking, OS and JRE?
7.0.0

Which company or project?
Shinho

What happened?
I use the skywalking chart and set the dynamicConfigEnabled to true, but the oap server doesn't work. Look at the error "no provider found for module configuration, if you're sure it's not required"

Requirement or improvement

I want to know how to use where and how to config the dynmiconfig to make the oap server reachable。

Please learn how to use the system env to control application.yml first. This log usually means you don't set the correct provider. Dynamic configurations have multiple options, read the doc.

I need to config the alarm and it could not use the env to control.

serviceAccounts:
oap:
oap:
name: oap
When 'dynamicConfigEnabled' set to true, enable oap dynamic configuration through k8s configmap，
Note: The default configmap data is empty, please refer to the detailed documentation (https://github.com/apache/skywalking/blob/master/docs/en/setup/backend/dynamic-config.md)
Sync period in seconds. Defaults to 60 seconds. env: SW_CONFIG_CONFIGMAP_PERIOD
dynamicConfigEnabled: true
image:
repository: apache/skywalking-oap-server
tag: 7.0.0-es7
pullPolicy: IfNotPresent
storageType: elasticsearch7
ports:
grpc: 11800
rest: 12800
replicas: 2
service:
type: ClusterIP

dynamicConfigEnabled: true
image:
repository: apache/skywalking-oap-server
tag: 7.0.0-es7
pullPolicy: IfNotPresent
storageType: elasticsearch7
ports:
grpc: 11800
rest: 12800
replicas: 2
service:
type: ClusterIP

I need to config the alarm and it could not use the env to control.

Again, please read the documents about dynamic configuration and what application.yml means, including which system env variables controlling all there. Please don't guess.


Export LLBUILD_TASK_ID to subprocesses.

[BuildSystem] Export LLBUILD_TASK_ID to subprocesses.

This will eventually be used to propagate a unique ID which subprocesses can
use for reassociation, but for now it is just the lane ID to use for tracing
purposes.

rdar://problem/35179142 Pass LLBUILD_TASK_ID environment variable to Clang for tracing purposes

@swift-ci please smoke test


Adding cone primitives.

🦟 Bug fix
Summary
This helps add the missing cone geometry for primitive/basic parametric shapes:

And is also valuable for visualizations of emitters/source that typically have conic-based spread as seen in this acoustic attack on an IMU by showing the affected area:

Associated PRs:

https://github.com/gazebosim/gz-gui/pull/621
https://github.com/gazebosim/gz-math/pull/594
https://github.com/gazebosim/gz-msgs/pull/442
https://github.com/gazebosim/gz-physics/pull/639
https://github.com/gazebosim/gz-rendering/pull/1003
https://github.com/gazebosim/gz-sim/pull/2410
https://github.com/gazebosim/sdformat/pull/1418

Checklist

[x] Signed all commits for DCO
[x] Added tests
[x] Updated documentation (as needed)
[x] Updated migration guide (as needed)
[x] Consider updating Python bindings (if the library has them)
[x] codecheck passed (See contributing)
[x] All tests passed (See test coverage)
[x] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

I've updated some shape tests in 71d883e (feel free to cherry-pick) to include the cone (just by duplicating cylinder and search/replace s/ylinder/one/), and I'm seeing a test failure in dart related to casting to the ConeShape. I commented on the dartsim ShapeFeatures.cc file where I think the problem comes from.
Perhaps we could create a CustomConeShape that inherits from CustomMeshShape, so we can cast to CustomConeShape instead of dart::dynamics::ConeShape?

Cherry-picked and pushed.
You have a test implementation of that method?

Cherry-picked and pushed. You have a test implementation of that method?

not yet; I was just tinkering with it and since the CustomMeshShape constructor wants a gz::common::Mesh, I think we would need a factory function to return a gz::common::Mesh to use in the CustomMeshShape initializer. I'll tinker a bit more

Cherry-picked and pushed. You have a test implementation of that method?

not yet; I was just tinkering with it and since the CustomMeshShape constructor wants a gz::common::Mesh, I think we would need a factory function to return a gz::common::Mesh to use in the CustomMeshShape initializer. I'll tinker a bit more

ok, I think I've gotten most of the tests fixed, except for bullet-featherstone, which complains about the bounding box size being larger due to the collision margin parameter, which we should discuss directly

fix for tpe test: https://github.com/scpeters/ign-physics/commit/79e38ff610c3189067405ee4bece1edd1fb74e7e
fix for dartsim tests by adding CustomConeMeshShape: https://github.com/scpeters/ign-physics/commit/2053f150c305444f99a74c1419e5eff7403f4a36

Cherry-picked and pushed. You have a test implementation of that method?

not yet; I was just tinkering with it and since the CustomMeshShape constructor wants a gz::common::Mesh, I think we would need a factory function to return a gz::common::Mesh to use in the CustomMeshShape initializer. I'll tinker a bit more

ok, I think I've gotten most of the tests fixed, except for bullet-featherstone, which complains about the bounding box size being larger due to the collision margin parameter, which we should discuss directly

fix for tpe test: scpeters@79e38ff
fix for dartsim tests by adding CustomConeMeshShape: scpeters@2053f15

Thanks, cherry-picked!

the following patch will fix tests by reducing the bullet-featherstone margin to 0, but I'm not sure if that will cause problems with contact simulation
diff --git a/bullet-featherstone/src/SDFFeatures.cc b/bullet-featherstone/src/SDFFeatures.cc
index 82fe6744..3ad3b3f5 100644
--- a/bullet-featherstone/src/SDFFeatures.cc
+++ b/bullet-featherstone/src/SDFFeatures.cc
@@ -970,6 +970,7 @@ bool SDFFeatures::AddSdfCollision(
     const auto height = static_cast<btScalar>(cone->Length());
     shape =
       std::make_unique<btConeShapeZ>(radius, height);
+    shape->setMargin(0.0);
   }
   else if (const auto *cylinder = geom->CylinderShape())
   {
diff --git a/bullet-featherstone/src/ShapeFeatures.cc b/bullet-featherstone/src/ShapeFeatures.cc
index c4702764..038ad835 100644
--- a/bullet-featherstone/src/ShapeFeatures.cc
+++ b/bullet-featherstone/src/ShapeFeatures.cc
@@ -247,6 +247,7 @@ Identity ShapeFeatures::AttachConeShape(
   const auto height = static_cast<btScalar>(_height);
   auto shape =
     std::make_unique<btConeShapeZ>(radius, height);
+  shape->setMargin(0.0);

   auto identity = this->AddCollision(
     CollisionInfo{

the following patch will fix tests by reducing the bullet-featherstone margin to 0, but I'm not sure if that will cause problems with contact simulation
diff --git a/bullet-featherstone/src/SDFFeatures.cc b/bullet-featherstone/src/SDFFeatures.cc
index 82fe6744..3ad3b3f5 100644
--- a/bullet-featherstone/src/SDFFeatures.cc
+++ b/bullet-featherstone/src/SDFFeatures.cc
@@ -970,6 +970,7 @@ bool SDFFeatures::AddSdfCollision(
     const auto height = static_cast<btScalar>(cone->Length());
     shape =
       std::make_unique<btConeShapeZ>(radius, height);
+    shape->setMargin(0.0);
   }
   else if (const auto *cylinder = geom->CylinderShape())
   {
diff --git a/bullet-featherstone/src/ShapeFeatures.cc b/bullet-featherstone/src/ShapeFeatures.cc
index c4702764..038ad835 100644
--- a/bullet-featherstone/src/ShapeFeatures.cc
+++ b/bullet-featherstone/src/ShapeFeatures.cc
@@ -247,6 +247,7 @@ Identity ShapeFeatures::AttachConeShape(
   const auto height = static_cast<btScalar>(_height);
   auto shape =
     std::make_unique<btConeShapeZ>(radius, height);
+  shape->setMargin(0.0);

   auto identity = this->AddCollision(
     CollisionInfo{

BTW, I do have your personal github as one of my remotes for that repo so you can always just push to the branch and I can fetch/cherry-pick anything in ;-P

@scpeters thanks once again, I applied your patch, I think it just needs CI approval.

rebuilding nightly debs:

https://build.osrfoundation.org/view/gz-ionic/job/gz-physics8-debbuilder/376/
https://build.osrfoundation.org/view/gz-ionic/job/gz-physics8-debbuilder/377/


x86_decode : more efficient nr_bytes determination

Instead of incrementing nr_bytes everywhere, remember pc in starting_pc.
After decoding, calculate nr_bytes using (pc - starting_pc).
This is faster, requires less code and avoids potential mistakes.

This has been done in a private branch (will probably become public soon), here : https://github.com/ergo720/libcpu/commit/11a794005fbfbddbec7806acd98cf675734e82a1#diff-835ebcf69fc07777d0a282f5e23851edR1545


Update README.md

Coverage remained the same at 46.386% when pulling c42fed1d5f5418fa658e443234de1e94b0072d8c on README into 5851e907f49fb4d082e36a2a6c56c9112279556d on master.


(PUP-8271) bump puppet for init name fix

lucy@ophelia:~/githubs/bolt ((c6a917a...))$ bb task show
apache                                 Allows you to perform apache service functions
echo                                   Foo bar
exec                                   Executes a command on the system
facter

Looks good to me!


Triple-brace inside

When I do the intuitive thing and have a list of contributors, where each name is triple-braced...
{:compact}
- {{{Bence Béky}}}
- {{{Daan De Meyer}}}
- {{{Martin Duke}}}
- {{{Roy Fielding}}}

...kramdown correctly produces contacts but xml2rfc chokes on it:

rfc9114.xml(3312): Error: Element li has extra content: contact, at /rfc/back/section[2]/ul/li[1]/contact
rfc9114.xml(3313): Error: Element li has extra content: contact, at /rfc/back/section[2]/ul/li[2]/contact
rfc9114.xml(3314): Error: Element li has extra content: contact, at /rfc/back/section[2]/ul/li[3]/contact
rfc9114.xml(3315): Error: Element li has extra content: contact, at /rfc/back/section[2]/ul/li[4]/contact

It looks like xml2rfc is expecting <t> around anything that's not simple text within the
.  But if I "fix" the issue by putting <t> around each contact...
{:compact}
- <t>{{{Bence Béky}}}</t>
- <t>{{{Daan De Meyer}}}</t>
- <t>{{{Martin Duke}}}</t>
- <t>{{{Roy Fielding}}}</t>

...the braces don't get turned into contacts:

{{{Bence Beky}}}

{{{Daan De Meyer}}}

{{{Martin Duke}}}

{{{Roy Fielding}}}

The RFC Editor fixed this up for me in RFC 9114, and I didn't even notice until I was diffing my fix-up branch against the final RFC.

When I do the intuitive thing and have a list of contributors, where each name is triple-braced...
{:compact}
- {{{Bence Béky}}}
- {{{Daan De Meyer}}}
- {{{Martin Duke}}}
- {{{Roy Fielding}}}

...kramdown correctly produces contacts but xml2rfc chokes on it:

rfc9114.xml(3312): Error: Element li has extra content: contact, at /rfc/back/section[2]/ul/li[1]/contact
rfc9114.xml(3313): Error: Element li has extra content: contact, at /rfc/back/section[2]/ul/li[2]/contact
rfc9114.xml(3314): Error: Element li has extra content: contact, at /rfc/back/section[2]/ul/li[3]/contact
rfc9114.xml(3315): Error: Element li has extra content: contact, at /rfc/back/section[2]/ul/li[4]/contact

It looks like xml2rfc is expecting <t> around anything that's not simple text within the
.

RFCXMLv3 has a grammar that replicates the information for what are block and span level elements throughout the grammar.  This replication is hard to maintain and therefore has a number of inconsistencies, which are not being fixed as these mistakes are in RFC 7991 which is supposed to guide RFCXMLv3 development.
When <contact was added to xml2rfc's vocabulary going beyond RFC 7991, the addition was done in a particularly haphazard way, which means it is allowed as a span-level element only in <t (plus as a block-level element in <section).
I made a fixup kit in https://tzi.org/~cabo/contact-hack.sh, but that of course only helps with your local xml2rfc.  Not sure when we will be able to start fixing xml2rfc in earnest.

But if I "fix" the issue by putting <t> around each contact...
{:compact}
- <t>{{{Bence Béky}}}</t>
- <t>{{{Daan De Meyer}}}</t>
- <t>{{{Martin Duke}}}</t>
- <t>{{{Roy Fielding}}}</t>

...the braces don't get turned into contacts:

Of course not.  Once you have entered XML land in a markdown file, there is no markdown parsing any more for the inside of the XML (which, among other things, would turn < into <).
Fixed workaround should be:
{:compact}
- <t markdown="span">{{{Bence Béky}}}</t>
- <t markdown="span">{{{Daan De Meyer}}}</t>
- <t markdown="span">{{{Martin Duke}}}</t>
- <t markdown="span">{{{Roy Fielding}}}</t>

But now we run into a peculiarity of xml2rfc's v2 to v3 converter which is still employed by :  It seems to delete the <t decoration in an <li (after all, this should be redundant, and would be if the RFCXMLv3 syntax were sane!), so it still throws the same error.  Not sure that this peculiarity, which turns into a bug only with the above mentioned grammar bug, will ever be fixed.
I could tinker with the kramdown-rfc output until it survives the v2v3 peculiarity.
I could also, when generating a <contact, check whether the context is a <t, and, if not, generate one.
Congratulations to finally shipping RFC 9114, by the way!

The bug that prevented the workaround from working is now fixed in https://github.com/ietf-tools/xml2rfc/releases/tag/v3.18.1
The bug in the grammar that creates the need for the workaround is unchanged though.

Oh.
The workaround actually is no longer needed, as v2v3 now spits out RFCXML that is conforming to the (unfixed) v3 syntax.
This now works:
{:compact}
- {{{Bence Béky}}}
- {{{Daan De Meyer}}}
- {{{Martin Duke}}}
- {{{Roy Fielding}}}

Another reason why it makes a lot of sense to leave the generation of proper v3 RFCXML to xml2rfc's v2v3 converter.
Wonderful; closing this issue now.


Restored error code on tests failing and added option to gracefully fail

This restores the exit code returning error on failing tests. There is also an added option that can be put in the project.yml. If setting :graceful_fail:  true in project.yml, it will behave the same way it currently does.
As mentioned in #117, the default behavior is for it to return error on failing tests as all test suits do this for CI and scripting purposes.

Would be great to get this merged. Many continuous integration systems rely on exit code != 0 to detect errors, fail builds, prevent merging. With current behavior everything passes. A lying test is worse than no test..


Demos doesn´t work, problem with Attributes

I am reviewing this library and it doesn´t work for me. When I remove the use of Attributes on elements it works. For example:
Doesn´t works: return DOM.Div(new Attributes { ClassName = "wrapper" }, ...
Works: return DOM.Div("AnyText" ...
It happens with Div and other elements. I am using lastest version of Bridge 15.5.0.

Hi @YandyZaldivar,
Please elaborate on what exactly did not work
What demo have you tried? I have a working todo app with react and redux Here,  although for Bridge 15.3.0
it is a compile error or  javascript run-time error?

What demo have you tried?
The demo on the readme file with an appropriate html file.

it is a compile error or javascript run-time error?
It compiles fine on C#. I haven´t debugged any JavaScript, I am constrained on time right now. Basically React doesn´t work, but if you use the overload dom element creation method that doesn´t use Attributes it works.

I haven´t tested with other version of bridge than 15.5.0, but I suppose I can do that tomorrow or so.
Thanks.

It looks like Bridge 15.5 (released this week) has introduced some issues. I've fixed up a couple of them and released a new version of the NuGet package (Bridge.React 1.10.0), which is currently being indexed on nuget.org and so should be available soon.
I'm going to continue looking into this in case anything else has broken.
If you get a chance to try out the latest NuGet package tomorrow and let us know if it works or not for you, that would be appreciated.


Allow unnamed modules

Currently, marking a component inside of a .vue file with `/** @module */ without providing a full longname results in a parser-inferred longname ending with ".module:vue" which means the inferred shortname is "vue". All its members then also have ".module:vue" in their longname.
I fixed that because I don't want to have to explicitly declare module names, especially in deeply nested files. This also allows the documentation to automatically update when modules are refactored and moved.

Codecov Report

Merging #185 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #185   +/-   ##
=======================================
  Coverage   70.83%   70.83%
=======================================
  Files           5        5
  Lines          48       48
  Branches       11       11
=======================================
  Hits           34       34
  Misses         11       11
  Partials        3        3

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 46c1fb6...4d83977. Read the comment docs.

Thanks for your contribution, would you add some tests before I review your PR?
I will try to give me some time this week-end to check it! :slightly_smiling_face:


Isssue#1502: Support formatting overloads in more AbstractThrowableAssert methods

Check List:

Fixes #1502
Unit tests : YES
Javadoc with a code example (API only) : YES

Thanks @ChaithanyaGK, I will review your PR shortly !

Integrated thanks @ChaithanyaGK for the good work!


Can faster scale out?

Does faster support a scaleout model where faster can run on different nodes and persist/read from same Storage?

No there is no such support.

I see something is cooking - https://microsoft.github.io/FASTER/roadmap

Right now, we do not have any code to share in this regard. However, this feature indeed on our longer-term roadmap, in stages:

Basic client -> single server support via remote API
Scale-out (multiple servers, sharded state) without dynamic elasticity/state migration
Elasticity

We would be very interested in the reasons for your query. Is this something you want to use, or contribute? What is the scenario, and what features are most important to you?
You can also read our recent research paper, that describes the kind of performance one can expect in a remote client-server setting with FASTER.

Coming to think of it, there is one important thing you can certainly do even today with FASTER. Maybe this is what you were looking for:
You can use a shared cloud storage log as your backing store, and fire up as many read-only instances of FASTER KV (on different machines) as you want to scale up your read workload. The only restriction is that only one FASTER instance is allowed to write to the database at any point in time.
In fact, there is a working example of exactly this design pattern, here:

https://github.com/microsoft/FASTER/tree/master/cs/samples/SecondaryReaderStore

In this example, if you replace the local storage device (line 26) with a cloud storage device, as in this example below, you get the above-mentioned functionality.

https://github.com/microsoft/FASTER/tree/master/cs/samples/AzureBackedStore

Hope this helps.