Geode 4722

Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?

[x] Has your PR been rebased against the latest commit within the target branch (typically develop)?

[ ] Is your initial contribution a single, squashed commit?

[x] Does gradlew build run cleanly?

[ ] Have you written or updated unit tests to verify your changes?

[n/a] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to<EMAIL_ADDRESS>

Intentionally left unsquashed for now -- The first commit just groups methods by general type: Cache and member utility, byte stream utility, etc.  Actual code changes are limited to the second commit.

Precheckin green.


sass-resource-loader: Zone already loaded error

Hi Mark,
I'm using bootstrap 4 and trying to include some scss mixins with sass-resource-loader. The problem is when I try to specify the path to include I get "Zone already loded error". I replaced scss loader with this in webpack.common.js:
{
  test: /\.scss$/,
  use: [
    'to-string-loader',
    'css-loader',
    'sass-loader',
    {
      loader: 'sass-resources-loader',
      options: {
        // Provide path to the file with resources
        resources: root('./node_modules/bootstrap/scss/mixins/mixin.scss'),
      },
    },
  ],
},

Do you have any idea to solve this?
Thanks

I haven't ran into that one, is this using the latest updates from the repo as well?
Also does the error come up during the server or browser render?

Actually, it happened (during server side prerendering) because the loader is not working, and I used a mixin inside an scss file. The funny thing is if I load the whole bootstrap like you did in app.component.scss I still cant use mixins..

Does it work now what did you need to do?

Sorry, but it wasnt your awesome template's but it was my fault. The problem was that the order is matters when you load your assets in your resoures section.


[Bug]: Type custom did not generate @font-face

Demo URL
No response
What happened?
I can not find anywhere the following @font-face-code in the generated files:
https://github.com/cssninjaStudio/unplugin-fonts/blob/941d0196992fc7fd0dc6515cea1d15d068f9c66b/src/loaders/custom.ts#L210-L218
vite-config is in a subdir (config/vite.config.ts)
The assets are in assets/common but will be copied in production to dist/-root folder, that is why i use transform() to correct the path.
unplugin-fonts config:
//...
      custom: {
        families: [
          {
            name: 'Pacifico',
            local: 'Pacifico',
            src: '../assets/common/fonts/pacifico/*.ttf',
            transform(font) {
              // correct frontend path
              font.files.forEach((file) => {
                file.path = file.path.replace('assets/common/', '')
              })
console.log(JSON.stringify(font, null, 2))
              return font
            },
          },
        ],
        display: 'auto',
        preload: true,
        prefetch: false,
        injectTo: 'head-prepend',
      },

Output from console.log above
{
  "source": "../assets/common/fonts/pacifico/*.ttf",
  "name": "Pacifico",
  "basename": "Pacifico-Regular",
  "weight": 400,
  "style": "normal",
  "local": "Pacifico",
  "display": "auto",
  "files": [
    {
      "src": "/myapp/assets/common/fonts/pacifico/Pacifico-Regular.ttf",
      "path": "/fonts/pacifico/Pacifico-Regular.ttf",
      "format": "truetype",
      "ext": ".ttf"
    }
  ]
}

index.html contains
  <head>
    <script type="module" src="/@vite/client"></script>
    <link rel="preload" as="font" type="font/ttf" href="/fonts/pacifico/Pacifico-Regular.ttf" crossorigin>

The font is loaded, but it can't be displayed, cause there is no css code for @font-face.
Reproduction steps
Usa a custom font.

Relevant log output
No response
What browsers are you seeing the problem on?
No response
What is your operating system?
No response

Try to double check the path to your fonts in assets (is the assets library under src/ and your config isn't?)

Hi @Farnsi, I think I have run into the same problem. The font <link> items all have urls that point to fonts, but again the @font-face is not being generated.

Try to declareunfonts.css in client.d.ts and import it in main.ts
client.d.ts
declare module 'unfonts.css' {
  const content: string;
  export default content;
}

main.ts
import 'unfonts.css';


Support PerformAction event in composed tasks

This PR aims to introduce support for PerformAction event. Changes

JSON schema for PerformAction event description
FleetUpdateHandle::add_performable_action(const std::string& category) API: Set the category of actions that robots in this fleet can perform.
RobotUpdateHandle::set_action_executor(ActionExecutor action_executor) API: Set the executor which can be used by the fleet adapter to request a robot to perform an action and RobotUpdateHandle::update_action_remaining_time(rmf_traffic::Duration duration) to update the estimate of the time remaining for the action.
Standby and Active definitions for PerformAction

This PR requires https://github.com/open-rmf/rmf_task/pull/49

This is shaping up very nicely. I just left a few more small remarks to address and then I'll be happy to approve :ok_hand:


Enable ARM(SVE) CPU support with reference backend

Proposed changes in this PR

Enabled support for build on ARM CPUs (SVE).
Arm build supports DAL Interface (daal) and oneAPI C++ interface (oneapi_c).
ci/env/tbb.sh helps to build tbb for ARM (SVE) cpu and installs it in the right folder structure for use during compile time.
Make command for arm(sve):
make -f makefile daal oneapi_c BACKEND_CONFIG=ref PLAT=lnxarm -j$(nproc)

Open Issues/Limitations:

oneAPI DPC++ interface (oneapi) is not supported since Intel's DPC++ compiler is not supported on arm.
oneAPI examples build fail on arm.
Bazel build is yet not supported.

For the most part, the structure looks good, and a change for building on a generic (non vendor-specific) CPU looks very similar to what is here. One of the most common comments I have (I didn't put all of them in), is that it's probably good to have x86 branches first, as this is the most likely code path at the moment.
There are a few things to discuss still, which can be quite big in themselves:

Do we target building with Bazel for new architectures? I don't have an opinion yet, as I'm not familiar with Bazel
How do we structure the code for new architectures? At the moment, there are multiple #ifdef in the files, where if this is done for each (micro-)architecture, the files can become cluttered. I would advocate for having target-specific sub-directories, and put target specific code in those, keeping as much common code in the files they are currently in.

@keeranroth we din't really change any structure and stuck to what x86 follows so we just added arm compatibility on top of it. My thoughts on further points:

@napetrov prefers the new architectures to support bazel, however x86 itself isn't fully ready yet so we chose to support the make file approach. We are now actively working towards supporting bazel on arm. Bazel is new for us as well and might take time to support it.
This would require a massive code re-architecture since only external APIs are isolated (BLAS/LAPACK etc.), ideally we would need to replicate similar methods for other parts of the algorithms as well. I agree with you on this to isolate the micro-architecture components.

/intelci: run

The approach above involves too many mk files like CMPLR.BACKEND.ARCH.mk. Having "n" backends and "m" archs, it will give [nxm] matrix. For every new arch it will be necessary to add all backends and vise versa and repeat it for all supported compilers. My suggestion is to separate backend and arch definitions to have a single file at least for every backend. For instance, defs.ref.mk for "ref" backend could contain COMPILER.defs += -DDAAL_REF -DONEDAL_REF -DONEAPI_DAAL_NO_MKL_GPU_FUNC while cmplr.clang.x86.mk could use COMPILER.defs above (both are included in main makefile): ### COMPILER.mac.clang = clang++ -m64 -fgnu-runtime -stdlib=libc++ -mmacosx-version-min=10.15 -fwrapv
-Werror -Wreturn-type $(COMPILER.defs)
COMPILER.lnx.clang = clang++ -m64
-Werror -Wreturn-type
$(COMPILER.defs)

/intelci: run

/intelci: run

on top of clang format, there are some other internal checks that should eb fixed
+---+---+---+---+---+---+---+---+------
|NLS|TAB|CHR|TAL|EOF|150|EXT|CRT| NAME
+---+---+---+---+---+---+---+---+------
| U | X | o | X | o | o | o | o | /lnx32e/src/cpp/daal/include/services/daal_defines.h
| U | o | o | o | X | o | o | X | /lnx32e/src/cpp/daal/include/services/internal/aarch64/aarch64_kernel_defines.h
| U | o | o | o | X | o | o | X | /lnx32e/src/cpp/daal/include/services/internal/x86_64/x86_64_kernel_defines.h
+---+---+---+---+---+---+---+---+------
Files tested:           3506
|NLS|TAB|CHR|TAL|EOF|150|EXT|CRT| NAME
+---+---+---+---+---+---+---+---+------
Files with errors:      3
Fixes applied:          0
Non-fixed errors found: 6
Warnings found:         1361
[legend] NLS ==> mixed dos-unix new line styles
[legend] TAB ==> tabs in files
[legend] CHR ==> chars outside of ASCII 127
[legend] TAL ==> tail spaces
[legend] EOF ==> not exactly one newline before EOF
[legend] 150 ==> more than 150 symbols in a line
[legend] EXT ==> exit label found
[legend] CRT ==> wrong name of file before copyright notice
[legend] YER ==> wrong year in copyright line

Internal build passing, but attempts to build daal4py on top of it failing with
__release_lnx/daal/latest/include/oneapi/dal/detail/policy.hpp:20:10: fatal error: daal/include/services/daal_defines.h: No such file or directory
So seems first public build should be fixed + there are bazel build failures

on top of clang format, there are some other internal checks that should eb fixed +---+---+---+---+---+---+---+---+------ |NLS|TAB|CHR|TAL|EOF|150|EXT|CRT| NAME +---+---+---+---+---+---+---+---+------ | U | X | o | X | o | o | o | o | /lnx32e/src/cpp/daal/include/services/daal_defines.h | U | o | o | o | X | o | o | X | /lnx32e/src/cpp/daal/include/services/internal/aarch64/aarch64_kernel_defines.h | U | o | o | o | X | o | o | X | /lnx32e/src/cpp/daal/include/services/internal/x86_64/x86_64_kernel_defines.h +---+---+---+---+---+---+---+---+------ Files tested: 3506 |NLS|TAB|CHR|TAL|EOF|150|EXT|CRT| NAME +---+---+---+---+---+---+---+---+------ Files with errors: 3 Fixes applied: 0 Non-fixed errors found: 6 Warnings found: 1361 [legend] NLS ==> mixed dos-unix new line styles [legend] TAB ==> tabs in files [legend] CHR ==> chars outside of ASCII 127 [legend] TAL ==> tail spaces [legend] EOF ==> not exactly one newline before EOF [legend] 150 ==> more than 150 symbols in a line [legend] EXT ==> exit label found [legend] CRT ==> wrong name of file before copyright notice [legend] YER ==> wrong year in copyright line

Thank you @napetrov for running checks.
Few Questions -

What does U mean in the table? X - means fail and o mean pass, is our understanding correct?
Erros and warnings are with respect to clang code format only? Do we need to fix warnings also? Currently we run .ci/scripts/clang-format.sh to do code formatting.

on top of clang format, there are some other internal checks that should eb fixed +---+---+---+---+---+---+---+---+------ |NLS|TAB|CHR|TAL|EOF|150|EXT|CRT| NAME +---+---+---+---+---+---+---+---+------ | U | X | o | X | o | o | o | o | /lnx32e/src/cpp/daal/include/services/daal_defines.h | U | o | o | o | X | o | o | X | /lnx32e/src/cpp/daal/include/services/internal/aarch64/aarch64_kernel_defines.h | U | o | o | o | X | o | o | X | /lnx32e/src/cpp/daal/include/services/internal/x86_64/x86_64_kernel_defines.h +---+---+---+---+---+---+---+---+------ Files tested: 3506 |NLS|TAB|CHR|TAL|EOF|150|EXT|CRT| NAME +---+---+---+---+---+---+---+---+------ Files with errors: 3 Fixes applied: 0 Non-fixed errors found: 6 Warnings found: 1361 [legend] NLS ==> mixed dos-unix new line styles [legend] TAB ==> tabs in files [legend] CHR ==> chars outside of ASCII 127 [legend] TAL ==> tail spaces [legend] EOF ==> not exactly one newline before EOF [legend] 150 ==> more than 150 symbols in a line [legend] EXT ==> exit label found [legend] CRT ==> wrong name of file before copyright notice [legend] YER ==> wrong year in copyright line

Thank you @napetrov for running checks. Few Questions -

What does U mean in the table? X - means fail and o mean pass, is our understanding correct?
Erros and warnings are with respect to clang code format only? Do we need to fix warnings also? Currently we run .ci/scripts/clang-format.sh to do code formatting.

Yes, correct.  U - unix. This one just checks for new line symbols.
We heve set of internal source code checks and some of them can be moved to opensource. Although they are not ideal. This is old script that was used back in the days for SVN. But it's still relevant in terms of keeping some of code consistency.

Errors - i mean that clang format check was failing previously. thanks for fixing

/intelci: run

env/lnxx86_64.sh: No such file or directory
Failures in internal CI. Not sure what line is causing this. but expectation should be that env files would remain the same

env/lnxx86_64.sh: No such file or directory

Hi @napetrov,

This is screenshot of oneDAL's main branch directory tree. I don't see lnxx86_64.sh file there.
Are you referring to some other path?

/intelci: run

env/lnxx86_64.sh: No such file or directory
Failures in internal CI. Not sure what line is causing this. but expectation should be that env files would remain the same

Seems like somewhere ARCH is being set to x86_64 (instead of 32e)

env/lnxx86_64.sh: No such file or directory
Failures in internal CI. Not sure what line is causing this. but expectation should be that env files would remain the same

Seems like somewhere ARCH is being set to x86_64 (instead of 32e)

Is it possible to provide more information about the error like from which command this error is generated? Which file is throwing this error? These things will help us investigate issue further.

Looks like 1 new CI fail based on updates:
In file included from cpp/daal/include/algorithms/algorithm_container_base.h:28,                  from cpp/daal/include/algorithms/algorithm_container_base_common.h:30,                  from cpp/daal/include/algorithms/algorithm_base.h:28,                  from cpp/daal/include/algorithms/algorithm.h:34,                  from cpp/daal/include/algorithms/sorting/sorting_batch.h:28,                  from cpp/daal/src/algorithms/sorting/sorting_batch_container.h:27,                  from cpp/daal/src/algorithms/sorting/sorting_dense_default_batch_fpt_dispatcher.cpp:24: bazel-out/k8-opt/bin/cpp/daal/include/services/internal/daal_kernel_defines.h:42:14: fatal error: x86_64/x86_64_kernel_defines.h: No such file or directory    42 |     #include "x86_64/x86_64_kernel_defines.h
Also clang formatting check failed.

/intelci: run

Please sync branch to main, as there is a change which will fix a problem with internal CI build.

/intelci: run

/intelci: run

Please sync to main again - getting build error with deprecated abs that should be corrected by rebasing branch

/intelci: run

Looks like bazel tests are running better now. @homksei could you check those example fails? looks like may require updating path in infra. http://intel-ci.intel.com/eec4ff3c-da06-f16f-b641-a4bf010d0e2e

/intelci: run

/intelci: run

The internal CI failure with our examples are still unresolved - anyone else on the intel side able to take a peek at the fails?

The internal CI failure with our examples are still unresolved - anyone else on the intel side able to take a peek at the fails?

@ethanglaser @napetrov  can you please help to check if the CI is still failing with the recent rebase! Thanks

/intelci: run

Hi @rageshhajela16!
I have checked the last commit. Unfortunately, the red ci steps still exist. After the investigation of internal ci issues, I found the issue.
The true issue log in examples is

I doublecheck how __release_lnx/daal/latest/lib/cmake/oneDAL/oneDALConfig.cmake looks like and it looks

So instead of lib/"arch_name" it uses just lib, and I would like to say that its incorrectly.
In comparison with master(it has green ci) it looks like

I also doublechecked your changes and these changes looks good for me https://github.com/oneapi-src/oneDAL/pull/2614/files#diff-a711276942a2647ec3ee01db428047af7e0efcd9ed25a93f600bc9bf53b70c2dR212
But may be its possible to replace it with ${ARCH_DIR_ONEDAL}, what do you think?

Hi @rageshhajela16! I have checked the last commit. Unfortunately, the red ci steps still exist. After the investigation of internal ci issues, I found the issue. The true issue log in examples is
I doublecheck how __release_lnx/daal/latest/lib/cmake/oneDAL/oneDALConfig.cmake looks like and it looks

So instead of lib/"arch_name" it uses just lib, and I would like to say that its incorrectly. In comparison with master(it has green ci) it looks like

I also doublechecked your changes and these changes looks good for me https://github.com/oneapi-src/oneDAL/pull/2614/files#diff-a711276942a2647ec3ee01db428047af7e0efcd9ed25a93f600bc9bf53b70c2dR212 But may be its possible to replace it with ${ARCH_DIR_ONEDAL}, what do you think? Or may be you have some more ideas about what could be the reason. I checked env variables and ARCH_DIR_ONEDAL is set correctly. I also will work on the investigation

From the build directory name it looks like, onedal is built using icc compiler (now depracated in version 2024.0, please confirm!).
We have run tried building onedal and examples using below commands -
make -f makefile onedal_c -j32
.ci/scripts/test.sh --test-kind examples --build-dir__release_lnx --compiler gnu --interface daal/cpp --build_system cmake
.ci/scripts/test.sh --test-kind examples --build-dir__release_lnx --compiler gnu --interface oneapi/cpp --build_system cmake
Everything works fine. All test examples building and passing successfully.
here compiler is automatically taken as icc (/opt/intel/oneapi/compiler/2023.2.1/linux/bin/intel64/icc) (noticed from logs).
icc installed via sudo apt install intel-oneapi-compiler-dpcpp-cpp-and-cpp-classic
oneDALConfig.cmake contain correct prefix -

Just to cross verify, is it possible to share configuration used to generate binaries? More precisely build command.
Thanks!

Hi @rageshhajela16! I have checked the last commit. Unfortunately, the red ci steps still exist. After the investigation of internal ci issues, I found the issue. The true issue log in examples is
I doublecheck how __release_lnx/daal/latest/lib/cmake/oneDAL/oneDALConfig.cmake looks like and it looks

So instead of lib/"arch_name" it uses just lib, and I would like to say that its incorrectly. In comparison with master(it has green ci) it looks like

I also doublechecked your changes and these changes looks good for me https://github.com/oneapi-src/oneDAL/pull/2614/files#diff-a711276942a2647ec3ee01db428047af7e0efcd9ed25a93f600bc9bf53b70c2dR212 But may be its possible to replace it with ${ARCH_DIR_ONEDAL}, what do you think? Or may be you have some more ideas about what could be the reason. I checked env variables and ARCH_DIR_ONEDAL is set correctly. I also will work on the investigation

From the build directory name it looks like, onedal is built using icc compiler (now depracated in version 2024.0, please confirm!). We have run tried building onedal and examples using below commands - make -f makefile onedal_c -j32 .ci/scripts/test.sh --test-kind examples --build-dir__release_lnx --compiler gnu --interface daal/cpp --build_system cmake .ci/scripts/test.sh --test-kind examples --build-dir__release_lnx --compiler gnu --interface oneapi/cpp --build_system cmake
Everything works fine. All test examples building and passing successfully.
here compiler is automatically taken as icc (/opt/intel/oneapi/compiler/2023.2.1/linux/bin/intel64/icc) (noticed from logs). icc installed via sudo apt install intel-oneapi-compiler-dpcpp-cpp-and-cpp-classic
oneDALConfig.cmake contain correct prefix -
Just to cross verify, is it possible to share configuration used to generate binaries? More precisely build command. Thanks!

on icc usage question - yes, we use it for build currently with plan for migration to icx.
But for icc it's public build, one of latest versions.

@ethanglaser  here the job with infra fixes https://intel-ci.intel.com/eecfd78a-97b3-f181-afe8-a4bf010d0e2e

@ethanglaser here the job with infra fixes https://intel-ci.intel.com/eecfd78a-97b3-f181-afe8-a4bf010d0e2e Examples look good now.

would suggest running nightly validation to check on broader scope, but so far things looks good and ready for integration

@ethanglaser here the job with infra fixes https://intel-ci.intel.com/eecfd78a-97b3-f181-afe8-a4bf010d0e2e Examples look good now.

would suggest running nightly validation to check on broader scope, but so far things looks good and ready for integration

Previous regular job has successfully finished!
Nightly job with this pr:  https://intel-ci.intel.com/eecfef9e-97dc-f1b8-9360-a4bf010d0e2e

/intelci: run

/intelci: run

Thanks everyone for working on this PR!

Thanks everyone for working on this PR!

Thanks everyone contributing to this PR!


Application terminated unexpectedly

When I chose the 'Chose from Library...' button ,my app terminated unexpectedly.How can i deal with?

Can you show us some stackTrace, code ?

Make sure the app don't crush by her self (run the library out of your app)

Oh,I validate the package in the ipad,Xcode crash.
but I run in iphone,it run normally.
doesn't  the package support Ipad?

@marcshilling any idea ?

Please upgrade to the latest version v0.18.15 and confirm its still happening. If so, please post some of your code that's using the Image Picker.

@peace201105
Perhaps adding this code in AppDelegate.m would solve the issue.
#if __IPHONE_OS_VERSION_MAX_ALLOWED < 90000
- (NSUInteger)application:(UIApplication *)application supportedInterfaceOrientationsForWindow:(UIWindow *)window
#else
- (UIInterfaceOrientationMask)application:(UIApplication *)application supportedInterfaceOrientationsForWindow:(UIWindow *)window
#endif
{
  if (UI_USER_INTERFACE_IDIOM() == UIUserInterfaceIdiomPad)
    return UIInterfaceOrientationMaskAll;
  else
    return UIInterfaceOrientationMaskAllButUpsideDown;
}


missing config.cd file

OrientDB Version: 3.0.22
Java Version: 11
OS: Win 10, Ubuntu 20.04, MacOs BigSur
Expected behavior
Database should not be corrupt
Actual behavior
From time to time I get my database throwing this:
com.orientechnologies.orient.core.exception.OStorageException: File with name config.cd does not exist in storage default
at com.orientechnologies.orient.core.storage.cache.local.OWOWCache.loadFile(OWOWCache.java:732) ~[orientdb-core-3.0.22.jar:3.0.22]
at com.orientechnologies.orient.core.storage.impl.local.paginated.base.ODurableComponent.openFile(ODurableComponent.java:188) ~[orientdb-core-3.0.22.jar:3.0.22]
at com.orientechnologies.orient.core.storage.cluster.v1.OPaginatedClusterV1.open(OPaginatedClusterV1.java:204) ~[orientdb-core-3.0.22.jar:3.0.22]
at com.orientechnologies.orient.core.storage.config.OClusterBasedStorageConfiguration.load(OClusterBasedStorageConfiguration.java:192) ~[orientdb-core-3.0.22.jar:3.0.22]
at com.orientechnologies.orient.core.storage.disk.OLocalPaginatedStorage.initConfiguration(OLocalPaginatedStorage.java:455) ~[orientdb-core-3.0.22.jar:3.0.22]
at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.open(OAbstractPaginatedStorage.java:385) ~[orientdb-core-3.0.22.jar:3.0.22]
at com.orientechnologies.orient.core.db.OrientDBEmbedded.open(OrientDBEmbedded.java:281) ~[orientdb-core-3.0.22.jar:3.0.22]
at com.orientechnologies.orient.core.db.OrientDB.open(OrientDB.java:205) ~[orientdb-core-3.0.22.jar:3.0.22]
at com.orientechnologies.orient.core.db.OrientDB.open(OrientDB.java:190) ~[orientdb-core-3.0.22.jar:3.0.22]
at org.apache.tinkerpop.gremlin.orientdb.OrientGraphFactory.getDatabase(OrientGraphFactory.java:153) ~[orientdb-gremlin-3.0.22.jar:3.0.22]
Steps to reproduce
Did not find any reproduction paths...I don't know why this happens...
My real question is how can I recover my database if it's at this point?

It seems that there is also an old report of more of the same issue https://github.com/orientechnologies/orientdb/issues/9391 with no attention/solution...is this in any way on any radar?

Hi @florian-stoica-tlabs , your data are not lost, But unfortunately, all team is busy with issues from commercial clients. Once we deal with them we will work on issues from the OS version.

@florian-stoica-tlabs do you see this file inside of the database folder?

That could be one of the issues which we already fixed, did you try to update to the 3.0.37 version and check?

Hi @laa Sorry for the long wait until I responded. I do have the following files inside:
config_13174512.bd
config_1983382051.nd
config_2061034952.cd
config_1506633995.ccm
Also updating to 3.0.37 did not help the same error is thrown.

@laa is there anything else I can try to recover the database?

Hi! I had the same problem using orient 3.1.5. Any news about this?
DWL:database: block size = 4096 bytes, maximum segment size = 347 MB [DoubleWriteLogGL]Exception `18748728` in storage `plocal:/path/to/database`: 3.1.5 - Veloce (build 846eeb77dcb175a9fbd7ed534e039424322f44a7, branch 3.1.x)
com.orientechnologies.orient.core.exception.OStorageException: Exception during execution of atomic operation inside of storage database
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideAtomicOperation(OAtomicOperationsManager.java:195)
at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.open(OAbstractPaginatedStorage.java:422)
at com.orientechnologies.orient.core.db.OrientDBEmbedded.open(OrientDBEmbedded.java:483)
at com.orientechnologies.orient.core.db.OrientDBEmbedded.open(OrientDBEmbedded.java:418)
at com.orientechnologies.orient.server.OServer.openDatabase(OServer.java:979)
at com.orientechnologies.orient.server.OServer.openDatabase(OServer.java:947)
at com.orientechnologies.orient.server.OConnectionBinaryExecutor.executeDatabaseOpen37(OConnectionBinaryExecutor.java:1369)
at com.orientechnologies.orient.client.remote.message.OOpen37Request.execute(OOpen37Request.java:75)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.sessionRequest(ONetworkProtocolBinary.java:355)
at com.orientechnologies.orient.server.network.protocol.binary.ONetworkProtocolBinary.execute(ONetworkProtocolBinary.java:239)
at com.orientechnologies.common.thread.OSoftThread.run(OSoftThread.java:67)
Caused by: com.orientechnologies.orient.core.exception.OStorageException: Exception during execution of component operation inside component config.cd in storage database
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideComponentOperation(OAtomicOperationsManager.java:221)
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideComponentOperation(OAtomicOperationsManager.java:206)
at com.orientechnologies.orient.core.storage.impl.local.paginated.base.ODurableComponent.executeInsideComponentOperation(ODurableComponent.java:102)
at com.orientechnologies.orient.core.storage.cluster.v2.OPaginatedClusterV2.open(OPaginatedClusterV2.java:211)
at com.orientechnologies.orient.core.storage.config.OClusterBasedStorageConfiguration.load(OClusterBasedStorageConfiguration.java:250)
at com.orientechnologies.orient.core.storage.disk.OLocalPaginatedStorage.initConfiguration(OLocalPaginatedStorage.java:558)
at com.orientechnologies.orient.core.storage.impl.local.OAbstractPaginatedStorage.lambda$open$1(OAbstractPaginatedStorage.java:433)
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideAtomicOperation(OAtomicOperationsManager.java:189)
... 10 more
Caused by: com.orientechnologies.orient.core.exception.OStorageException: File with name config.cd does not exist in storage database
at com.orientechnologies.orient.core.storage.cache.local.OWOWCache.loadFile(OWOWCache.java:760)
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationBinaryTracking.loadFile(OAtomicOperationBinaryTracking.java:372)
at com.orientechnologies.orient.core.storage.impl.local.paginated.base.ODurableComponent.openFile(ODurableComponent.java:193)
at com.orientechnologies.orient.core.storage.cluster.v2.OPaginatedClusterV2.lambda$open$1(OPaginatedClusterV2.java:216)
at com.orientechnologies.orient.core.storage.impl.local.paginated.atomicoperations.OAtomicOperationsManager.executeInsideComponentOperation(OAtomicOperationsManager.java:214)
... 17 more

I am seeing this issue with 3.2.0.  I have no idea what trigger this. Is there any update on this?
orientdb> connect plocal:/data/databases/dbname abc 123
Connecting to database [plocal:/data/databases/dbname] with user 'abc'...
Error: com.orientechnologies.orient.core.exception.ODatabaseException: Cannot open database 'dbname'
Error: com.orientechnologies.orient.core.exception.OStorageException: Exception during execution of atomic operation inside of storage dbname
Error: com.orientechnologies.orient.core.exception.OStorageException: Exception during execution of component operation inside component config.cd in storage dbname
Error: com.orientechnologies.orient.core.exception.OStorageException: File with name config.cd does not exist in storage dbname
In the database directories, I am assuming these are correct:
root@uat-db-001:/opt/orientdb/log# ls -la /data/databases/dbname/config_*
-rw-r--r-- 1 orientdb orientdb 132096 Aug 16 19:50 /data/databases/dbname/config_1863402051.cd
-rw-r--r-- 1 orientdb orientdb 132096 Aug 16 19:50 /data/databases/dbname/config_2029091032.ccm
-rw-r--r-- 1 orientdb orientdb 132096 Aug 16 19:50 /data/databases/dbname/config_27966618.bd
-rw-r--r-- 1 orientdb orientdb  66560 Jun 24 06:15 /data/databases/dbname/config_415755639.nd
-rw-r--r-- 1 orientdb orientdb 132096 Aug 16 19:50 /data/databases/dbname/config_671038889.fcm

Hi @pa-chris , could you send me your database to check?

How would you like me to send it?

On Aug 17, 2021, at 8:16 AM, Andrey Lomakin @.***> wrote:
Hi @pa-chris https://github.com/pa-chris , could you send me your database to check?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/orientechnologies/orientdb/issues/9562#issuecomment-900338024, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKZEQEJYR4WPWKAS5JGFOCDT5JVM5ANCNFSM4ZF6CAMQ.

I need a link to the database data on my email<EMAIL_ADDRESS>.

@pa-chris Just to clarify, did you work only with 3.2.0 version and then experienced this problem? I mean did you create a database and work with it using the same version of the distribution, did not you?

Yes, that is correct.  This particular one was only every on 3.2.0.

On Aug 17, 2021, at 8:38 AM, Andrey Lomakin @.***> wrote:
@pa-chris https://github.com/pa-chris Just to clarify, did you work only with 3.2.0 version and then experienced this problem? I mean did you create a database and work with it using the same version of the distribution, did not you?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/orientechnologies/orientdb/issues/9562#issuecomment-900356243, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKZEQEJIZTBQC6MCXEWS4XTT5JX6BANCNFSM4ZF6CAMQ.

Hi @pa-chris , thank you.
It was very informative. I have found a durability issue in the procedure of storing the registry of files of the database during close.
I will provide a fix ASAP.

Thank you very much

On Aug 18, 2021, at 8:57 AM, Andrey Lomakin @.***> wrote:
Hi @pa-chris https://github.com/pa-chris , thank you.
It was very informative. I have found a durability issue in the procedure of storing the registry of files of the database during close.
I will provide a fix ASAP.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/orientechnologies/orientdb/issues/9562#issuecomment-901185682, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKZEQEKRYXJSR7Y64J7FMWTT5PC4VANCNFSM4ZF6CAMQ.

@pa-chris data are not touched, but unfortunately, that is quite a time-consuming procedure, so only for commercial customers. I am sorry for that. It implies manual repair of data. I am running tests now to be sure that changes do not break anything and will commit.

@laa , If you can point me to how to do the manual repair, that is no problem at all. That would be kindly appreciated

Fixed by PR above.


Hangs forever in refresh after 5 minutes when 2ary unreachable

tl;dr setsockopt(SO_RCVTIMEO) doesn't work for us in Ruby 2.[01] MRI, infinite hangs result
We're having trouble in our Mongo cluster when a secondary becomes unreachable (due to e.g. crashed instance or network partition): the symptom is that after five minutes all attempts to contact the primary seem to hang indefinitely (or until Unicorn kills our worker process).  Note that our mongoid.yml has options: {read: primary}
Attempting to replicate the problem in a test environment gets us a call stack something like this (some frames omitted for brevity)
     # /home./.bundler/ruby/2.1.0/moped-4c2a0a29122e/lib/moped/connection/socket/connectable.rb:47:in `read'
     # /home./.bundler/ruby/2.1.0/moped-4c2a0a29122e/lib/moped/connection/socket/connectable.rb:47:in `block in read'
     # /home./.bundler/ruby/2.1.0/moped-4c2a0a29122e/lib/moped/connection/socket/connectable.rb:119:in `handle_socket_errors'
     # /home./.bundler/ruby/2.1.0/moped-4c2a0a29122e/lib/moped/connection/socket/connectable.rb:47:in `read'
     # /home./.bundler/ruby/2.1.0/moped-4c2a0a29122e/lib/moped/connection.rb:221:in `with_connection'
     # /home./.bundler/ruby/2.1.0/moped-4c2a0a29122e/lib/moped/connection.rb:114:in `read'
     # /home./.bundler/ruby/2.1.0/moped-4c2a0a29122e/lib/moped/protocol/query.rb:213:in `receive_replies'
     # /home./.bundler/ruby/2.1.0/moped-4c2a0a29122e/lib/moped/node.rb:180:in `block in ensure_connected'
     # /home./.bundler/ruby/2.1.0/moped-4c2a0a29122e/lib/moped/node.rb:432:in `refresh'
     # /home./.bundler/ruby/2.1.0/moped-4c2a0a29122e/lib/moped/cluster.rb:182:in `block in refresh'
     # /home./.bundler/ruby/2.1.0/moped-4c2a0a29122e/lib/moped/cluster.rb:151:in `nodes'
     # /home./.bundler/ruby/2.1.0/moped-4c2a0a29122e/lib/moped/cluster.rb:240:in `with_primary'
     # /home./.bundler/ruby/2.1.0/moped-4c2a0a29122e/lib/moped/read_preference/primary.rb:55:in `block in with_node'

and after some digging the problem seems to be that implementing timeouts using socket options doesn't work in Ruby MRI.  Looking at it with strace I see a call to read that returns after five seconds with EAGAIN followed by a call to ppoll  - the EAGAIN doesn't ever get as far as interpreted code.
getsockname(7, {sa_family=AF_INET, sin_port=htons(44829), sin_addr=inet_addr("<IP_ADDRESS>")}, [16]) = 0
setsockopt(7, SOL_SOCKET, SO_SNDTIMEO, "\5\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 16) = 0
futex(0x7f24117f6654, FUTEX_WAIT_PRIVATE, 1, NULL) = 0
futex(0x7f24117f66d0, FUTEX_WAKE_PRIVATE, 1) = 0
select(8, [7], NULL, [7], {0, 0})       = 0 (Timeout)
read(7, 0x7f2413130f00, 100)            = -1 EAGAIN (Resource temporarily unavailable)
ppoll([{fd=7, events=POLLIN}], 1, NULL, NULL, 8  <hang indefinitely>

See also http://stackoverflow.com/questions/9853516/set-socket-timeout-in-ruby-via-so-rcvtimeo-socket-option
The attached patch has a spec that demonstrates the problem (try running it under strace) and a fix which implements read timeouts "by hand" using select() instead of relying on socket options.  A more full solution would probably address the write() case and be tested on SSL connections as well as plaintext ones, but I thought I'd push this early diagnosis up to you for comment first to see if I'm on the right track
/cc @dawid-sklodowski @cpoo22 just fyi

We experience this issue as well. Would love to see it merged.

@telent, have you been running this in production? I tested this out on production and had some really strange errors (moped cursor returning empty documents) that were sporadic and hard to reproduce. I reverted the change for now but will do some more investigation later.

Though to be clear, I had done it by copying the code into a fork of Moped 1.5. I didn't try with Moped 2 yet.

I tried testing this again by issuing a scatter-gather query on a massive collection with hundreds of millions of documents. This wreaked havoc on the database, as it appears that the query continually kept getting retried but the cursor wasn't closed. As such, before I CTRL+C'd it, we had 19 identical queries running which caused massive queued reads and blocking. I'm not sure this is safe. Though, I had retrofitted it to 1.5, so it may work in 2.0 but I am bearish on this right now given what happened to us.

@durran have you thought about this problem at all in the new ruby driver? As @telent points out, SO_RCVTIMEO simply does not work in MRI anymore. We experience this issue when we have a bad networking event or a physical host which has multiple mongoDs freezes or crashes; our processes completely hang and must be kill -9'd. We have an identical stack trace to what @telent describes in the issue. Reviewing the code for the new driver, I think that we'll have the same issue as long as IO.select is not used before the socket read. This pull as it is is problematic for us, my guess is because if a query takes longer than @timeout to return, then the ConnectionFailure causes it to be re-issued (as I mentioned above, we wreaked havoc on a database with this pull and a 10 second timeout), but this is a real operational issue that causes really bad problems for us.

@jonhyman I have a branch up on the new driver that actually does an IO.select before selecting a server to use in an operation... (https://github.com/mongodb/mongo-ruby-driver/pull/670/files#diff-ea2082a78a5d9b36b80ce79b7705943dR86) The server.connectable? call is eventually calling a select before returning it, and the operation would execute immediately after.

I may be wrong, but I don't think that that's going to help. Going back to Moped and this issue for a second, the Moped code already has a check_if_alive! immediately before the read, but one issue is that alive? is defined as this (in both Moped and the new driver)
def alive?
  if Kernel::select([ self ], nil, [ self ], 0)
    !eof? rescue false
  else
    true
  end
rescue IOError
  false
end

so if select returns nil, alive? still returns true. The alive? check has a 0 second timeout, so all you know is that the socket is not dead, but if it returns nil then it does not have data on it right now and is not ready for reading. Because the current Moped code does this:
check_for_alive!
handle_socket_errors { super }

you don't know if the socket is ready for reading when you go to read, and the super call hangs indefinitely as @telent's stack trace shows (and we have that exact stack trace when it happens to us).
In your pull, connectable? simply does an alive? check, which, if select returns nil signifying that the socket is not ready for reading, connectable? will still return true. Then you'll end up calling @socket.read in https://github.com/mongodb/mongo-ruby-driver/blob/master/lib/mongo/socket.rb#L172 and I think this code will be vulnerable to hanging again (I have not yet tested, your pull is the last one I'm waiting on before we perform failover testing scenarios with the new driver :grin:).
From all my testing locally, I can't figure out how to solve this hanging case in Ruby that does not involve using select to set a "maximum read time" by making read_from_socket look something like this:
def read_from_socket(length)
  begin
    @socket.read_nonblock(length) || String.new
  rescue IO::WaitReadable, OpenSSL::SSL::SSLErrorWaitReadable
    ready = IO.select([@socket], nil, [@socket], 300)
    if ready
      retry
    else
      raise StandardError.new("Maximum query time exceeded, no data from socket returned in 300 seconds.")
    end
  end
end


Please Add BinaryFormatter (a fast and secure one)

It seems that the release of .Net 5 would need a fast and secure BinaryFormatter
https://github.com/dotnet/corefx/issues/38760#issuecomment-504539915
This repo look like the perfect one

I believe this should be closed. @benaadams already added all the secure aspects of BinaryFormatter to this code base.

@dotnet-bot please close this issue.

@terrajobst
Serializer ! I meant Serializer
that would need a review from @blowdart

it seems i cannot type properly ...


bump version to 1.14.0-dev

from now on, every change related to the 1.13 release should me merged in https://github.com/docker/docker/tree/1.13.x

ping @mlaventure @tonistiigi @tiborvass

LGTM

LGTM


fix: Replace fuzzywuzzy with thefuzz

The fuzzywuzzy library has been renamed to thefuzz (see: https://github.com/seatgeek/fuzzywuzzy?tab=readme-ov-file#this-project-has-been-renamed-and-moved-to-httpsgithubcomseatgeekthefuzz).
There doesn't seem to be anything broken with fuzzywuzzy but thefuzz actually receives updates.
This commit just updates the requirements and import to use thefuzz.
Didn't find any issue or PR talking about this before, so if there is any reason why lolstaticdata needs to use fuzzywuzzy instead just let me know.

Thanks! We need to update to rapidfuzz instead going forward.


Adding an extra option to suppress rate metrics if so desired

Please take a look. This will save consumers $$. We are trying to weed away with rate metrics as well - since there's ways in librato to do this without client side data.
Basic idea is to allow the users to use a new factory function to pass in specific rate metrics they want instead of giving them no option. A little more democratic :)

@mihasya Would love for you to take a look and let me know if this is something we can integrate.

Hey that certainly sounds useful.. I have had this thought before.
High level feedback - this patch is pretty hard to read; it is not very clear exactly what's happening and why the code achieves the end. Specifically:

Need better-named methods. handleDefaultRateOptions and handleRateOption seem like they should do nearly identical things, but they're completely different methods. handle as a "catch-all" verb is hurting readability.
I'm not sure I understand the RateOptions data structure. It seems like the values are always nil. Are you just using the "map as a set" pattern here? Perhaps naming could make this better as well - EnabledRates or EnabledRateSet perhaps.
I don't like the use of reflect inside the reporter loop. I understand what you're trying to do in using a DRY method for both the cases, but reflection has a cost, both in terms of processing and readability. I believe Timer implements Meter so you could achieve the same end by just type asserting Timer as Meter and making your DRY method work with an instance of Meter.

Let me know if these make sense. Thanks!

Hi, to answer your comments:

Yes - the naming of the methods could be clearer, I'm fixing that.
The rate data structure holds specifically which options I want to turn on say, Rate1 for Timer but Rate15 for Meter. And yes, this is a Hash Set so to speak - because I didn't want the client to repeat the values. I can name this differently as well.
Your thoughts on reflection are well taken, but my understanding of this piece of code was that it would get invoked every X seconds lowest being 5 - I wouldn't imagine those reflect calls having a big overhead there.

I'm fairly new to Golang - so keep those comments coming. I'll make the changes and update this PR this morning at some point.

@mihasya I've updated some names and code a little bit. On the comment about reflection - I generally agree with you - but this piece of code will be called a maximum of 6 times per run - which at the lowest resolution will be around every 5 seconds in it own goroutine. If you still feel strongly about it - I can refactor the code - however, I don't believe my DRY philosophy is actually affecting performance in any significant manner. I added some more tests, and fixed a glaring bug with the rate method not being invoked.
I can also add a map of functions to their types - but that's probably over engineering it. Point is that the original code was a little too repetitive, whichever way we choose to go, we should move forward with something more compact. Thanks. Looking forward to your comments.

(on my plate to review this weekend, so sorry for the long wait. have had my hands full)

No problems. I do have a small update for this - I will update the PR shortly.


doc improvements for saga vs thunk, handling simple cases

This seems like some low hanging fruit that would aid newcomers.
When reading the docs it's not immediately clear to me how to use a saga in "the simplest case". By simplest case I mean there is a view button that triggers a callback, and that callback has async behavior. In a redux-thunk implementation, that callback would be a bound action creator with some middleware to handle the async nature of the callback:
<button onClick={this.props.login} />

...

mapDispatchToProps(dispatch) {
    return bindActionCreators(actionCreators, dispatch)
}

...

let actionCreators = {
    login() {
        return (dispatch, getState) => {
            dispatch({
                type: LOGIN_REQUEST
            })

            return xhr({
                method: 'POST'
                , url: api.login
            })
            .then((res) => {
                if (res.statusCode === 200) {
                    dispatch({
                        type: LOGIN_SUCCESS
                    })
                }
            })
        }
    }
}

The docs say redux-saga is a replacement/alternative for redux-thunk or other middlewares, and neatly explains how sagas are a much more powerful construct, especially when dealing with longer running sequences of events. However, it's not immediately clear whether the use case of "one event, one action" also falls under a saga's domain, or how we might implement that case. This is how I would do it, but I'm open to suggestions:
let actionCreators = {
    login({ username, password }) {
        return {
            username
            , password
            , type: LOGIN
        }
    }
    , loginRequest() {
        return {
            type: actions.DO_LOGIN_REQUEST
        }
    }
    , loginError() {
        return {
            type: actions.DO_LOGIN_ERROR
        }
    }
    , loginFailure() {
        return {
            type: actions.DO_LOGIN_FAilURE
        }
    }
    , loginSuccess(response) {
        return {
            response
            , type: actions.DO_LOGIN_SUCCESS
        }
    }
}

function* watchForLogin() {
    while (true) {
        const { username, password } = yield take(actions.LOGIN)
        yield call(login, { username, password })
    }
}

function* login({ username, password }) {
    yield put(actionCreators.loginRequest())
    let { statusCode, body } = yield call(doLogin, { username, password })

    if (statusCode > 499) {
        yield put(actionCreators.loginError())
        return
    }

    if (statusCode > 399) {
        yield put(actionCreators.loginFailure())
        return
    }

    yield put(actionCreators.loginSuccess(body))
}

function* doLogin({ username, password }) {
    const b64 = btoa(`${username}:${password}`)
    return xhr({
        method: 'POST'
        , url: api.login
        , headers: {
            'authorization': `Basic ${b64}`
        }
    })
}

First, is this the "right way" to make a one-to-one, or is there a cleaner approach than having an explicit "start this saga" action creator callback? Second, do you think this is something that should appear in the docs?

@aft-luke I like the one-to-one comparison. Using a login example highlights the differences between redux-thunk and redux-saga quite well.
I'm just starting out with redux-saga and getting familiar with it so I can't answer your first question.
Should it appear in the docs? As a new user I think it would help to have a one-to-one example from redux-thunk considering most people using redux will be familiar with it.
If it would be a welcome addition, I wouldn't mind working on a PR to use gitbook for documentation. The cost would be harder upkeep of the docs (e.g. making sure these types of examples still work, etc). There is a certain beauty about keeping all the documentation in a single README.md, but by using something like gitbook these additional examples can be added in without worrying about bloat.

Sagas that milmics the thunk callbacks are generally wrapped inside a while(true). the examples dir re-implement some of the original redux/thunk examples so I don't think there is a lack on this side. although I agree there is a lack on the docs side: step by step tutorials; showcase of complex flow implementations; handling common concurrency concerns...)
@trevorsenior

If it would be a welcome addition, I wouldn't mind working on a PR to use gitbook for documentation

Didn't work with gitbook before; but from the site docs, it seems like publishing gitbooks isn't done in the Github repo but instead on the gitbook site https://github.com/GitbookIO/gitbook#publish-your-book.
Of course any contribution is welcome

Didn't work with gitbook before; but from the site docs, it seems like publishing gitbooks isn't done in the Github repo but instead on the gitbook site https://github.com/GitbookIO/gitbook#publish-your-book.

The site is optional, you can totally make it work with Github Pages. You can check out docs:publish in package.json of Redux to get an idea.

I'm new to redux-saga and checking out the Readme with no prior knowledge.  The one thing I'm really puzzled by is the difference between take, put, etc.  Even a bulleted list of the API methods with one-liners would be very helpful.

@danscan yeap; API docs is a serious lack; hope to do it soon.

opened #70 to centralize feedback

also will close this; feel free to add your suggestions to #70

@danscan there is a new section for API docs
http://yelouafi.github.io/redux-saga/docs/api/index.html
Will be adding more content later


Event Calendar functionality for public events organized by Svet Media Group.

With Angular Material Grid List

https://angular-ui.github.io/

http://angular-ui.github.io/ui-calendar/


bump version and create release note stubs for 1.1.0

Thanks. It looks like I needed to do more proofreading!


Idea: iPXE

Would you be opposed to adding iPXE to allow the file transfer to go over http(s) instead of tftp?

Not opposed, but...
iPXE doesn't work for everyone (myself included) due to the bootlooping issue iPXE has. And while there are workarounds, I opted for the "simplest" route since I don't care how long a node takes to reboot/rejoin.
I think there's probably a way to tackle this so it's an option for those who want to use iPXE. :) So I'm +1

Done and confirmed on my homelab!
Currently works off ghcr.io/jeefy/booty:main but will be in the next release once I finish the other idea I'm knocking out. :)
Was fun seeing a node boot in about thirty seconds instead of like ten minutes.


Issue #1487 - Fix issue with Node FQDN required parameters

Problem: SDK requires address parameter with Node, but the REST API
does not require it for fqdn type nodes
Solution: This PR looks for a set of required parameters that exclusively
permits the fqdn or the address for the create method.
Files Changed:

f5/bigip/tm/ltm/node.py (changed)
f5/bigip/tm/ltm/test/functional/test_node.py (changed)

@caphrim007 ready for review


Keeps cycling in iso update

Bug
Click update on iso install ok looks good but refresh iso update and your app comes back wanting to update stoped trying after third time
<EMAIL_ADDRESS>if you want me to poke stuff for you
if you already know all this just ignore me hate to waste your time
Screenshots
If applicable, add screenshots to help explain your problem
Steps to reproduce

Error is thrown

Hello,
I have the same problem. I am currently on 22.4.xxx and trying to update to 23.0 seems to fail. Once the update is supposed to be done, the update button is back and the version check confirm that no update was done.
Any way to get some trace of what's happening ?

Behavior has changed. Appstore app no longer propose the update but a  open button as if the upgrade has been done.
After control, the installed app is still 22.4.x where the appstore shows 23.0

Perhaps an App Store issue?
Are you using the App Store or TestFlight?

I just have retried now (regular upgrade using appstore) and this time the upgrade was quick and fine. I am now on 23.0.1145
May be as you said an appstore issue ! Sorry for the inconvenience
By the way, MANY THANKS for giving us the ability to manage manually display/hide of the keyboard, I found it was switching frequently in undesired way. Nice usability improvement ! 😄

Thank you so much @philippelt for your feedback 🙏
Glad to hear that the App Store issue is over 😅
If you think that more improvements could be done about the keyboard doesn't hesitate to tell me.
Have a nice day ☀


Update dependency spatie/laravel-ignition to v2

This PR contains the following updates:

Package
Type
Update
Change

spatie/laravel-ignition (source)
require-dev
major
^1.0 -> ^2.0

Release Notes

spatie/laravel-ignition (spatie/laravel-ignition)
v2.4.2
Compare Source
What's Changed

Bump actions/cache from 3 to 4 by @dependabot in https://github.com/spatie/laravel-ignition/pull/178
Add some sensible defaults for headers that should be sensored. by @timvandijck in https://github.com/spatie/laravel-ignition/pull/180

New Contributors

@timvandijck made their first contribution in https://github.com/spatie/laravel-ignition/pull/180

Full Changelog: https://github.com/spatie/laravel-ignition/compare/2.4.1...2.4.2
v2.4.1
Compare Source
What's Changed

[2.x] Fixes dump header on different symfony versions by @nunomaduro in https://github.com/spatie/laravel-ignition/pull/177

Full Changelog: https://github.com/spatie/laravel-ignition/compare/2.4.0...2.4.1
v2.4.0
Compare Source
What's Changed

[2.x] Adds L11 support by @nunomaduro in https://github.com/spatie/laravel-ignition/pull/167

New Contributors

@nunomaduro made their first contribution in https://github.com/spatie/laravel-ignition/pull/167

Full Changelog: https://github.com/spatie/laravel-ignition/compare/2.3.3...2.4.0
v2.3.3
Compare Source

decode job payload data if it is a string

v2.3.2
Compare Source

Fix issue where sending Flare reports from tinker was impossible (especially logging)

v2.3.1
Compare Source

fix config description

v2.3.0
Compare Source
What's Changed

Bump dependabot/fetch-metadata from 1.5.1 to 1.6.0 by @dependabot in https://github.com/spatie/laravel-ignition/pull/154
Help Sail users when they forget to run an Artisan command using sail by @jessarcher in https://github.com/spatie/laravel-ignition/pull/156

Full Changelog: https://github.com/spatie/laravel-ignition/compare/2.2.0...2.3.0
v2.2.0
Compare Source

Add support arguments and argument reducers

v2.1.3
Compare Source
What's Changed

Better support for custom context and exception context by @rubenvanassche in https://github.com/spatie/laravel-ignition/pull/146
Support for PhpStorm Remote editor

Full Changelog: https://github.com/spatie/laravel-ignition/compare/2.1.2...2.1.3
v2.1.2
Compare Source

fix regex pattern in MissingImportSolutionProvider

Full Changelog: https://github.com/spatie/laravel-ignition/compare/2.1.1...2.1.2
v2.1.1
Compare Source
v2.1.0
Compare Source
What's Changed

Bump dependabot/fetch-metadata from 1.3.5 to 1.3.6 by @dependabot in https://github.com/spatie/laravel-ignition/pull/135
Update run-tests.yml by @tvbeek in https://github.com/spatie/laravel-ignition/pull/136
Add AI solutions by @freekmurze in https://github.com/spatie/laravel-ignition/pull/142

New Contributors

@tvbeek made their first contribution in https://github.com/spatie/laravel-ignition/pull/136

Full Changelog: https://github.com/spatie/laravel-ignition/compare/2.0.0...2.1.0
v2.0.0
Compare Source
What's Changed

[10.x] Laravel v10 development by @driesvints in https://github.com/spatie/laravel-ignition/pull/38
Update composer.json by @driesvints in https://github.com/spatie/laravel-ignition/pull/39
Update composer.json by @driesvints in https://github.com/spatie/laravel-ignition/pull/40
Update to Monolog v3 by @driesvints in https://github.com/spatie/laravel-ignition/pull/91
Support Laravel 10 by @freekmurze in https://github.com/spatie/laravel-ignition/pull/134

Full Changelog: https://github.com/spatie/laravel-ignition/compare/1.6.4...2.0.0

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: src/composer.lock
Command failed: composer update spatie/laravel-ignition:2.4.2 --with-dependencies --ignore-platform-req='ext-*' --ignore-platform-req='lib-*' --no-ansi --no-interaction --no-scripts --no-autoloader --no-plugins
Loading composer repositories with package information
Dependency laravel/framework is also a root requirement. Package has not been listed as an update argument, so keeping locked at old version. Use --with-all-dependencies (-W) to include root dependencies.
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires spatie/laravel-ignition ^2.0 -> satisfiable by spatie/laravel-ignition[2.4.2].
    - spatie/laravel-ignition 2.4.2 requires illuminate/support ^10.0|^11.0 -> found illuminate/support[v10.0.0, ..., v10.46.0] but these were not loaded, likely because it conflicts with another require.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.


[BUG] Repeated error HTTPError (for a null.jpg)

I am getting this 403 Error.
It is strange, which I am getting "Forbidden for url: https://static.cdninstagram.com/rsrc.php/null.jpg"
This is what I dont expected. If I got blocked by instagram, the log show show I am requesting a url for a media that have HTTP Error.
However, in this case, the script is requesting a "null.jpg"

I dont think it is instagram block issue
the same script running for downloading another account's media works like charm.

this and the other issues that pop up the abort/ignore/retry/forever question that require manual input should always be answered ignore automatically by the script if possible. i usually leave this running because its very slow and then notice later that it has stopped and its asking this.. its usually for expired stories that cause it tho and it says gone instead of denied but now also this. theres nothing the user can do to these so they should always be ignored automatically if possible so it does not stop the scraper.

expiring this issue too

Agree - running into the same issues - one suggestion would be for the library to handle these and return the data that was collected to that point.

Can you share a username on which this null.jpg file was gathered instead of a photo url?

Did bug disappear, why no one reported a way to reproduce it?

no it didn't:
instagram-scraper lindseypelas

The bug is caused by this media https://www.instagram.com/p/BqNrxivlWju/ and it shouldn't be just ignored, it is possible to obtain the video from there https://scontent-arn2-1.cdninstagram.com/vp/79014d4897be9578130672f402e23670/5D502B9B/t50.2886-16/46381814_273146856675109_1025908209014977424_n.mp4?_nc_ht=scontent-arn2-1.cdninstagram.com we just need to process it differently. Ignoring errors lead to masking bugs and data losses.

I have same problem:
2019-09-16 12:32:12,547 - instagram_scraper.app - WARNING - Retry after exception HTTPError('403 Client Error: Forbidden for url: https://static.cdninstagram.com/rsrc.php/null.jpg',) on https://static.cdninstagram.com/rsrc.php/null.jpg from https://www.instagram.com/p/B2XFiekH3UN
I downloading 100k posts now and after 60k it's happened. It's runned by:
--tag --media-metadata --comments --include-location --retry-forever
So.. probably need to stop downloading because even when all 100k will be downloaded process will be looped and I can't get .json file?


Terrain overshadows 3D Tiles model

Hello,
parts of my 3D Tiles city model gets overshadowed by terrain when displayed with it. Is there a way to ensure the model is always visible over the terrain?
Sandcastle example
Browser: Chromium 72.0
Operating System: Ubuntu 16.04
Thanks,
Ladislav

Hello @ladislavhorky, you can use a modelMatrix transform to adjust the height of the tileset to line it up with terrain.  See this example: https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/?src=3D Tiles Adjust Height.html&label=3D Tiles
In the future, if you have questions like this, please ask them on the forum: https://groups.google.com/forum/?hl=en#!forum/cesium-dev
We use GitHub exclusively for tracking bugs and planning new features.  Thanks!


test_io.test_ImageRecordIter_seed_augmentation has fixed seed that can mask flakiness

The unit test in title have been using fixed seed to mask flakiness. Suggested action:

Evaluate whether the test is flaky without fixed seed. If not, remove seed. Else move to 2
If test is flaky, determine whether it's an actual uncaught edge case. If so, fix the operator. Else move to 3
If numerical instability is inevitable, adjust tolerance level appropriately.

Thanks for filing this issue. We will investigate this Flaky test

This is a duplicate of #11359.


[Snyk] Security upgrade ubuntu from 16.04 to xenial-20210114

Snyk has created this PR to fix 2 vulnerabilities in the dockerfile dependencies of this project.
Keeping your Docker base image up-to-date means you’ll benefit from security fixes in the latest version of your chosen image.
Snyk changed the following file(s):

samples/contrib/nvidia-resnet/components/inference_server_launcher/Dockerfile

We recommend upgrading to ubuntu:xenial-20210114, as this image has only 92 known vulnerabilities. To do this, merge this pull request, then verify your application still works as expected.
Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Allocation of Resources Without Limits or Throttling SNYK-UBUNTU1604-SYSTEMD-1320131
  614

Allocation of Resources Without Limits or Throttling SNYK-UBUNTU1604-SYSTEMD-1320131
  614

Allocation of Resources Without Limits or Throttling SNYK-UBUNTU1604-SYSTEMD-1320131
  614

Allocation of Resources Without Limits or Throttling SNYK-UBUNTU1604-SYSTEMD-1320131
  614

Improper Check for Dropped Privileges SNYK-UBUNTU1604-BASH-542609
  536

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Allocation of Resources Without Limits or Throttling

Commit Checker results:
**NOTE**: These are the results of the commit checker scans.
If these are not commits from upstream kfp, then please ensure
you adhere to the commit checker formatting

commitchecker verson unknown
Validating 1 commits between e27b68731776c35efe5e363295c3cc4a782cec4f...fba1fa9a41a00a551abdb3580b1c88601f42a34e

UPSTREAM commit fba1fa9 has invalid summary fix: samples/contrib/nvidia-resnet/components/inference_server_launcher/Dockerfile to reduce vulnerabilities.

The Data Science Pipelines team recommends testing this using the Data Science Pipelines Operator.  Check here for more information on using the DSPO.
To use and deploy a DSP stack with these images (assuming the DSPO is deployed), first save the following YAML to a file named dspa.pr-117.yaml:
apiVersion: datasciencepipelinesapplications.opendatahub.io/v1alpha1
kind: DataSciencePipelinesApplication
metadata:
  name: pr-117
spec:
  dspVersion: v2
  apiServer:
    image: "quay.io/opendatahub/ds-pipelines-api-server:pr-117"
    argoDriverImage: "quay.io/opendatahub/ds-pipelines-driver:pr-117"
    argoLauncherImage: "quay.io/opendatahub/ds-pipelines-launcher:pr-117"
  persistenceAgent:
    image: "quay.io/opendatahub/ds-pipelines-persistenceagent:pr-117"
  scheduledWorkflow:
    image: "quay.io/opendatahub/ds-pipelines-scheduledworkflow:pr-117"
  mlmd:
    deploy: true  # Optional component
    grpc:
      image: "quay.io/opendatahub/mlmd-grpc-server:latest"
    envoy:
      image: "registry.redhat.io/openshift-service-mesh/proxyv2-rhel8:2.3.9-2"
  mlpipelineUI:
    deploy: true  # Optional component
    image: "quay.io/opendatahub/ds-pipelines-frontend:pr-117"
  objectStorage:
    minio:
      deploy: true
      image: 'quay.io/opendatahub/minio:RELEASE.2019-08-14T20-37-41Z-license-compliance'

Then run the following:
cd $(mktemp -d)
git clone git@github.com:opendatahub-io/data-science-pipelines.git
cd data-science-pipelines/
git fetch origin pull/117/head
git checkout -b pullrequest fba1fa9a41a00a551abdb3580b1c88601f42a34e
oc apply -f dspa.pr-117.yaml

More instructions here on how to deploy and test a Data Science Pipelines Application.


VI Description unreadable in "Build Message with Arguments(Auto Check)"

@drjdpowell I moved this issue to the CSM core repository, as it seems more appropriate there. it will be fixed in the upcoming December release.
As a heavy user of your SQLite/JSONText/CycleTableProbe library, I am delighted to see your interest in CSM. Please feel free to leave your suggestion and feedback. It will be valuable for me. :)

add a testcase for checking documentation.


Need to add md5sum to the bam_to_cram_ step

We will wan't an md5sum for both the cram and the index cram.crai in the "bam_to_cram_" task.
This will enable more efficient transfer and sharing of data between TGen and collaborators.

@bryce-turner Also will need the logic to create the md5sum for the bams if bam to cram is not enabled.


TrimSqlNode bug

MyBatis version
3.4.4
Database vendor and version
mysql
Test case or example project
<select id="select" parameterType="string" resultType="map">
    select * from table_name
    <trim prefix="WHERE" prefixOverrides="AND |OR ">
        <if test="id !='' and id !=null">
            and `id` = #{id}
        </if>
        <if test="username !='' and username !=null">
            and `username` = #{username}
        </if>
    </trim>
</select>

Steps to reproduce
I set prefixOverrides value is "AND  |OR " (AND followed by 2 blank space)。it will not remove remove prefix "and"
Expected result
set prefixOverrides value "  AND   |   OR"，prefix "and" or "or" will be remove
Actual result

source code is

i think if condition change to
" trimmedUppercaseSql.startsWith(toRemove) || trimmedUppercaseSql.startsWith(toRemove.trim()) " will fix this bug

Hello @mnisummer ,
I'm sorry, but that is a misconfiguration.
It's clearly documented.

The prefixOverrides attribute takes a pipe delimited list of text to override, where whitespace is relevant.

The proposed change will create a new more serious bug.
<trim prefix="WHERE" prefixOverrides="AND |OR ">
  organization = #{organization}
</trim>

will become
where ganization = #{organization}

For WHERE clause, you should use <where /> tag.


IoT needs several more concepts

Work with BacNet and the Heathrow projects suggests we need: Controller and System to round it out.

Done at latest in 9.1.0.


Fix typo in docstring

Add example in assign source method
Close #2811

FYI: I've added comments in PyAEDT PR #2813 for refactoring EDB to explain how to resolve the Vale warnings.


Set up the basic structure for the bitmasking-dp-algorithm

A new file needs to be added to the dp-folder.

@AmandaStromdahl I already added it !

I noticed your file and I added some content to it.


Release crate

Waiting for @desplesda's answer on whether we can become the official Rust port of Yarn Spinner.

If yes - release as yarnspinner

Thank you @tinaun for freeing the crate name!
Rename everything
Change links to issue creation
Remove all instances of "git" from the code

if no - release as yarn_slinger

Then write a post on reddit, mastodon, discord, ferdi, etc.

Done 🎉


Blur+ renders Cobblemon Battle GUI Blurry -- way to exclude it? (v3.1.0 - Fabric)

I attempted to look for a .config file, but the only one available is a CLASS document which I'd have to decompile and seems to be quite a bit of work overall.

you have to go to the blur config (that much should be obvious) and to the list of blurExclusions add: "com.cobblemon.mod.common.client.gui.battle"
after having the same issue and finding no solutions online i ended up just searching the entirety of the cobblemon sourcecode for "gui" and found BatleGUI.kt which mentioned the above id right at the top
so similar issues should be able to be solved in a similar way


Ability to open a SQLite database by "uploading" it

Not actually uploading it to the server, but opening it through the browser file open UI - like https://squoosh.app/

In this general space (getting content into a browser based app), you could also add file system access.
Elsewhere, JupyterLite was the prompt for the jupyterlab-contrib/jupyterlab-filesystem-access extension, I think.

Related: It looks like you can't sue a file:/// URL to load a local sqlite db into datasette lite, which I imagine is a common use case. If someone sends you a .db file to use, you need to find a "real URL" to host it at, which may not always be easy/desirable, esp. if it's sensitive data. Wonder how much work it would be to support file:/// URLs, whether or not it comes with a "nice file picker UI" to figure out the URL (which of course would be even nicer).


Fixed typo

Thanks!

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


expected update syntax can be too aggressive

Not a bug report, more of a question.
Because the docs don't provide examples of UPDATE queries, I experimented with what seemed to make the most sense from the SQLA docs. I found that performing an .update() on (what I thought was) a single record turned out to update every row in database. See code sample.
Is there a preferred way of performing an update on a single record where you change multiple attributes at once? Or better yet, use a dict to specify all the attributes to change, and the new values?
from flask import Flask
from flask_sqlalchemy import SQLAlchemy

app = Flask(__name__)
app.config['SQLALCHEMY_DATABASE_URI'] = 'sqlite:///e:\\foo.db'
db = SQLAlchemy(app)

class User(db.Model):
    id = db.Column(db.Integer, primary_key=True)
    username = db.Column(db.String(80))
    email = db.Column(db.String(120))

    def __repr__(self):
        return '<User %r>' % self.username

db.create_all()
john = User(username='jlennon'<EMAIL_ADDRESS>paul = User(username='pmac'<EMAIL_ADDRESS>george = User(username='ghar'<EMAIL_ADDRESS>ringo = User(username='rstarr'<EMAIL_ADDRESS>
db.session.add_all([john, paul, george, ringo])
db.session.commit()

user_four = User.query.get(4)
# UNSAFE!! Will change EVERY row!!
user_four.query.update({<EMAIL_ADDRESS>})
db.session.commit()

# SAFE. But how to change multiple attributes? or load from a dict?
user_three = User.query.get(3)
user_three.username = 'georgeh'
db.session.commit()

the docs don't provide examples of UPDATE queries

Because Flask-SQLAlchemy doesn't do anything about those, it's just a thin wrapper around SQLAlchemy. Refer to those docs, you'll see the same behavior.
The query property is a class property, not an instance property. It's still accessible from instances, but it's not filtered to just that instance, it represents a new unfiltered query.

Please use Stack Overflow for questions about your own code. This tracker is for issues related to the project itself. Be sure to include a minimal, complete, and verifiable example.

If I add the following lines to my first example, the entire table is wiped out. Are you saying this is what would be expected, or desired? Come on.
# WHOOPS!!
user_three.query.delete()
db.session.commit()
# now I have an empty table

But making the query property available to a single record, rather than the full model/table, IS possible in Flask-SqlAlchemy and NOT possible in the base API. Similar syntax is not documented over there because it is invalid and throws an error, as I've shown above.
My issue isn't with the documentation, it is with the functionality. Do you really want single_row.query.delete() to delete all the rows? Because that's what it does.

Oh got it. You want the returned row object to have it's query BaseQuery class helper property removed when the row is instantiated and no longer a model class. We could override create_row_processor to unset self.query when the row object is instantiated, or maybe also orm.reconstructor to unset query?
Both User.query and User.query.first().query are actually the same, but you're right the latter isn't needed and I've never seen anyone using it so probably ok to unset on init.

when the row is instantiated and no longer a model class

Right. Attaching .query to a single row (single instance of the Model class), should not make it possible to affect the entire model.
I would like to see a syntax so that single_row.query.delete() deleted just a single row. But SQLAlchemy doesn't work that way (https://github.com/mitsuhiko/flask-sqlalchemy/issues/575), which is fine. What isn't fine, in my opinion, is to allow the syntax but have it do something unexpected and potentially dangerous.
To expand on your example...
User.query.delete()  # clearly, deleting every row in the model User

and
joe = User.query.filter_by(username='joe').first()
joe.query.delete()  # appears that we are only deleting 'joe', but not true

both do the same thing, despite syntax that suggests otherwise.

Maybe we should raise an exception or warning when accessing query on an instance instead of a class?

i believe a waning should do fine there - it should hint that the use of instance.query is discouraged as the query object is always for the type and if the type is not well known ahead at least using type(instance).query will be documentation of the ownership relations of the objects to avoid missunderstandings

Raising an exception with #650.

In the base SQLAlchemy, update() cannot be called on an instance.

Those aren't the docs I was referring to. SQLAlchemy implements its own version of query_property, and that does the exact same thing as what we do: the property returns a query against the class whether it's accessed from a class or instance.

when the row is instantiated and no longer a model class

Right. Attaching .query to a single row (single instance of the Model class), should not make it possible to affect the entire model.
I would like to see a syntax so that single_row.query.delete() deleted just a single row. But SQLAlchemy doesn't work that way (#575), which is fine. What isn't fine, in my opinion, is to allow the syntax but have it do something unexpected and potentially dangerous.
To expand on your example...
User.query.delete()  # clearly, deleting every row in the model User

and
joe = User.query.filter_by(username='joe').first()
joe.query.delete()  # appears that we are only deleting 'joe', but not true

both do the same thing, despite syntax that suggests otherwise.

How to delete two tables data combine using flask-sqlalchemy query???

Closing based on SQLAlchemy behavior described in the comment above.


[evaluation fix] remove obsolete linuxPackages_5_12 alias

Motivation for this change
Things done

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

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Should be merged rather quick because it breaks nixpkgs-review on staging.

The linux_5_12 alias needs to be removed as well, no?
I wasn't aware of this PR and attempted the same in  #134594

Subsumed.


Error when trying to compile

Whenever I try to compile a test program I get this error:
emojicodec: error while loading shared libraries: libtinfo.so.5: cannot open shared object file: No such file or directory
Not quite sure what it means but if someone could help that would be greatly appreciated!

Just fixed it by running it in docker instead.

Please see this comment https://github.com/emojicode/emojicode/issues/166#issuecomment-654672307


Fairies mark the mine

When a fairy reveals a mine, we should mark the mine directly on the field. We should use a new special mine symbol. Something like a fairy wand.

Has been implemented.


ASCII depiction of graph

Is there a way to display the graph in ASCII art? Similar to what binarytree does?
Or what would you suggest is the best way to visualize the graph?

I haven't seen any tool to display a graph in ASCII art.
Maybe for planar graphs it is possible to create something
but it will be difficult.
--
dr hab. Andrzej Kapanowski
Sekretarz Wydziałowego Zespołu Rekrutacyjnego
Uniwersytet Jagielloński, Instytut Fizyki
30-384 Kraków, Łojasiewicza 11
tel. +48 12 664 4628
email<EMAIL_ADDRESS>
Od: Ashok Bakthavathsalam<EMAIL_ADDRESS>Wysłane: poniedziałek, 10 lutego 2020 17:31
Do: ufkapano/graphs-dict<EMAIL_ADDRESS>DW: Subscribed<EMAIL_ADDRESS>Temat: [ufkapano/graphs-dict] ASCII depiction of graph (#5)
Is there a way to display the graph in ASCII art? Similar to what binarytreehttps://github.com/joowani/binarytree/blob/master/README.rst#getting-started does?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/ufkapano/graphs-dict/issues/5?email_source=notifications&email_token=ABPAP5IGU3RTNX2WSOPSR6LRCF6NPA5CNFSM4KSRMMLKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IMJZQPA, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPAP5OEMZ7JKMND5QWEY2LRCF6NPANCNFSM4KSRMMLA.

The graph structure can be described by a tree decomposition (a tree with bags) but finding a TD is a hard problem in general. I am going to add some heuristic algorithms for finding TD (or a chordal completion). You can check the ToTo website http://treedecompositions.com/


TCK scenarios for list slices

Acceptance tests for list slice
Covers valid and invalid ranges
Ported from Cypher for Gremlin

 Review PR #329 TCK scenarios for list slices


Feat/argocd repo/add template repos

what

allow argocd-repo component to skip creating the repo
allow argocd-repo component to manage secrets in a repo

why

It's difficult to set up argocd repos correctly
make it easier to rotate a secret such as a PAT on a set of applications

Will work on separate component rather than modifying argocd-repo

re-opening for discussion/refresh

re-closing since this should still be a separate module at this point


Root pass for PHP container

I'm getting this error when I try and upload a 21MB site backup.
The input file exceeds the servers upload_max_filesize or post_max_size limit.
I tried logging into the Vanilla drupal container and changing /usr/local/etc/php/conf.d/docker-php.ini and adding
upload_max_filesize = 10M post_max_size = 10M
but the docker-php.ini keeps getting reset when I restart the container.
How can I avoid the upload_max_filesize error?

I think we should be able to edit all configs in php.ini.


CIT-573: Delete Opportunity

Issue:
Currently, user cannot delete an opportunity when the name of the opportunity is empty.
Fix:
Removed text input requesting for the name of the opportunity to allow soft deletion of the opportunity.
Removed authorization check in backend. Users will not have their IDIR registered to Keycloak to handle permissions, the application is public.
Reference: https://connectivitydivision.atlassian.net/browse/CIT-573

Removed isAuthenticated because we are not going to add the users with IDIR privileges. The isAuthenticated function is checking if the user has IDIR, but this is going to be never in OpenShift, so it would fail always.


Crash during GIF handling

There is nothing much more to add. Problematic images attached.
GIFs.zip

A final remark: Updating GifLib wouldn't help here as this is GIF-handling code outside GifLib. Might be a good idea to upgrade anyway, of course.


[tensor] customized op returns ColoTensor

We have to make the output of Op a ColoTensor.
Therefore we can assign the spec for them.
For example, the output of 1Drow Linear should be a shard of the global tensor. We can better represent it using ColoTensor than a Torch Tensor.


fix(deps): update terraform github.com/terraform-ibm-modules/terraform-ibm-landing-zone to v6.2.1

This PR contains the following updates:

Package
Type
Update
Change

github.com/terraform-ibm-modules/terraform-ibm-landing-zone
module
minor
v6.1.2 -> v6.2.1

Release Notes

terraform-ibm-modules/terraform-ibm-landing-zone (github.com/terraform-ibm-modules/terraform-ibm-landing-zone)
v6.2.1
Compare Source
Bug Fixes

if consuming root level module, the clusters input now also requires operating_system input to be set. Its no longer optional. Updates also made to the example override json files to reflect this. (#908) (3003ac4)

v6.2.0
Compare Source
Features

The operating_system input is now a required variable for OCP related DAs. Valid values are REDHAT_8_64 or RHCOS. Anyone who is using the override json will now also need to explicitly set this value. (#905) (e2390eb)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.

/run pipeline

/run pipeline

:tada: This PR is included in version 2.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Executing all tests on build agent

Description
This PR ensures we run all tests on the build agent (unit and integration tests).

Extends the TestCommon library with SqlServerDatabaseManager to support testing using a local SQL express instead of using Squadron and linux docker image (which is not supported on windows runners).
Refactored TestCommon library to use the latest Azure.Messaging.ServiceBus SDK
Refactored other database dependent tests to use the ChargesDatabaseFixture and removed all dependencies to Squadron with regards to SQL server.
Updated the build pipeline to use a windows runner instead of linux, and install necessary tools. Changed bash shell to PowerShell.

References
https://app.zenhub.com/workspaces/mighty-ducks-60ae1565be2dfe0017ff66b2/issues/energinet-datahub/mightyducks/209

I rebased the branch with master to get the fix for the client CI build.


GNOME: 40 → 41

https://discourse.gnome.org/t/gnome-41-released/7603/1
cc @NixOS/gnome
https://github.com/NixOS/nixpkgs/projects/41
https://hydra.nixos.org/jobset/nixpkgs/gnome
Changelogs reviewed up to gnome.zenity: 3.32.0 → 3.41.0  by @jtojnar

libvirt-glib doesn't build with glib > 2.69 on the latest release. Reading through commits doesn't look like it's been addressed yet, and after a quick search through the mailing list I didn't see any patches either (not that I was super thorough).

Some probably off-topic note: We just pinned Vala to 0.52 for Pantheon packages that cannot build with 0.54 in this PR.

libvirt-glib doesn't build with glib > 2.69 on the latest release.

A newbie question: I tried building libvirt-glib on this PR and it failed with G_TYPE_IS_FINAL not available before 2.70 (full log). Will mesonFlags = [ "-Dc_args=-DGLIB_DISABLE_DEPRECATION_WARNINGS" ]; work in this case (it does successfully compile for me)?
Not sure if these are related: (1) GLIB_VERSION_MAX_ALLOWED set in libvirt-glib (2) Fedora Rawhide is building this with glib 2.69.2 +  gobject-introspection 1.68.0 (3) Add "final" class attribute merge request in gobject-introspection (4) Add "final" type flag merge request in glib.

All packages under gnome attribute have been bumped and possible problems noticed in changelogs were added to the board. Probably not ready to test on real systems yet. Feel free to lend a hand in triaging them or submitting fixes. Helping with red jobs on Hydra also appreciated.

Weird, that does not look like something that should fail:
https://gitlab.gnome.org/GNOME/tracker/-/blob/255c935754ca6c0b6a0e05fd411c21c7364ea5cd/tests/libtracker-sparql/tracker-resource-test.c#L61
I was not able to reproduce it so probably something transient.

All GNOME apps seem to work, the portal too, failing Hydra packages are pretty low (only few leaf Vala packages) so the only remaining thing is extensions but those can be updated separately when they are released.
Unfortunately, it turns out the tests no longer pass. Likely because the shell api we used is now private: https://gitlab.gnome.org/GNOME/gnome-shell/-/merge_requests/1970

Shouldn't this merge request target staging instead of the main branch?
Thanks for working on this. Enjoying GNOME 41 so far and nothing seems to be broken after a whole day of usage(other than some extensions missing upstream GNOME 41 support unu)

Since we build the packages on Hydra, merging to master will not cause a mass rebuild.

I somehow still can't figure out a way to rebase this to master and not trigger a huge rebuild, so I'm mildly cautious about that claim.
Running it for 3 days already, still can't find much to complain about
(which kinda undermines my whole reason for trying it: dispelling boredom)
Brightness icon is occasionally volume icon and vice versa when I adjust them, but I seriously doubt this is a packaging issue.
Got any testing guidelines or something?

pkgsi686Linux.tracker fails same as https://github.com/NixOS/nixpkgs/pull/139144#issuecomment-937302301.

nixos-unstable is now broken for me, too.
running tests
ninja: Entering directory `/build/tracker-3.2.0/build'
ninja: no work to do.
 1/33 tracker:functional / fts-functions                      OK               0.89s
 2/33 tracker:functional / sparql-bugs                        OK               0.92s
 3/33 tracker:functional / query                              OK               1.32s
 4/33 tracker:functional / group-concat                       OK               0.68s
 5/33 tracker:functional / coalesce                           OK               0.77s
 6/33 tracker:functional / insertion                          OK               1.84s
 7/33 tracker:functional / distance                           OK               0.73s
 8/33 tracker:functional / graph                              OK               0.92s
 9/33 tracker:functional / collation                          OK               0.70s
10/33 tracker:functional / notifier                           OK               1.02s
11/33 tracker:functional / concurrent-query                   OK               1.49s
12/33 tracker:functional / ontology-rollback                  OK               0.47s
13/33 tracker:functional+ipc / bus-query-cancellation         OK               0.40s
14/33 tracker:gvdb / gvdb                                     OK               0.01s
15/33 tracker:common / file-utils                             OK               0.01s
16/33 tracker:common / utils                                  OK               0.01s
17/33 tracker:data / crc32                                    OK               0.02s
18/33 tracker:data / ontology-change                          OK               0.58s
19/33 tracker:data / ontology-error                           OK               0.03s
20/33 tracker:data / sparql-blank                             OK               0.07s
21/33 tracker:functional / cli                                OK               1.74s
22/33 tracker:data / insert-or-replace                        OK               0.37s
23/33 tracker:functional / ontology-changes                   OK               2.60s
24/33 tracker:functional / portal                             OK               2.89s
25/33 tracker:fts / fts                                       OK               0.39s
26/33 tracker:resource / resource                             FAIL             0.12s   killed by signal 6 SIGABRT
>>> MALLOC_PERTURB_=186 LANG=en_US.UTF8 TRACKER_LANGUAGE_STOP_WORDS_DIR=/build/tracker-3.2.0/src/libtracker-common/stop-words /build/tracker-3.2.0/build/tests/libtracker-sparql/tracker-resource-test
 ✀
stdout:
# random seed: R02S9bb64c7f3a28fd1d4cbc9738781ee4e8
# Testing Tracker resource abstraction
1..6
# Start of libtracker-sparql tests
# Start of tracker-resource tests
ok 1 /libtracker-sparql/tracker-resource/get_empty
Bail out! Tracker:ERROR:../tests/libtracker-sparql/tracker-resource-test.c:61:test_resource_get_set_simple: 'tracker_resource_get_first_double (resource, "http://example.com/1") == 0.6' should be TRUE
stderr:
**
Tracker:ERROR:../tests/libtracker-sparql/tracker-resource-test.c:61:test_resource_get_set_simple: 'tracker_resource_get_first_double (resource, "http://example.com/1") == 0.6' should be TRUE

27/33 tracker:data+slow / ontology                            OK               3.64s
28/33 tracker:data / service                                  OK               5.40s
29/33 tracker:data+slow / sparql                              OK               6.75s
30/33 tracker:sparql / sparql                                 OK               0.44s
31/33 tracker:sparql / statement                              OK               0.57s
32/33 tracker:examples / endpoint                             OK               0.59s
33/33 tracker:sparql / fd                                     OK               0.91s

Summary of Failures:

26/33 tracker:resource / resource                     FAIL             0.12s   killed by signal 6 SIGABRT

Ok:                 32
Expected Fail:      0
Fail:               1
Unexpected Pass:    0
Skipped:            0
Timeout:            0

Full log written to /build/tracker-3.2.0/build/meson-logs/testlog.txt
builder for '/nix/store/d67j41d88js80c6rvk7d6fpap7ilmczd-tracker-3.2.0.drv' failed with exit code 1
cannot build derivation '/nix/store/yw942n07506d9gfkcxc2j0mz83i15j39-gtk+3-3.24.30.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/vh65pnvg2h1rv5gcm6kbrk0y4cwbvv77-steam-usr-multi.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/xv3xrn6fs6w2pyds8dh9hvwcp8vs2sg2-steam-fhs.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/1ivxvf5svrz2k27bgcrz0a5k1hfiwm3d-steam.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/2g1vib9a53hlx3vn5qkgnlpm8c9mpvp5-steam.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/5qyk5w68qbq5cl0adgp05pzwr0ynxgh7-system-path.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/r911pdavjdg67sfpi19cqkab2nkc34qp-nixos-system-venus-21.11.git.7366ad6608f.drv': 1 dependencies couldn't be built
error: build of '/nix/store/r911pdavjdg67sfpi19cqkab2nkc34qp-nixos-system-venus-21.11.git.7366ad6608f.drv' failed


Persist user specific stats like games played and total enemies killed

in a local sqlite. Along the way, we refactored arcade+db functionality into separate crates/compilation units to assist platform-specific feature development+conditional compilation.

Some help with layout and styling would be appreciated.

The problem is that sqlite (in C) uses stdio.h and we don't have that in the browser. turns out this isnt so easy since sqlite is all about synchronous IO which doesnt go so well in the browser, especially since we also need to compile audio stuff to JS. so ill conditionally compile out the db stuff and the current game metrics are all we get in the browser for now.
I also tried with wasm32-wasi and wasm32-emscripten targets.

First time I ran Thetawave on Windows with the "storage" feature. I had this error appear. Reporting to you as directed in the message 👍

The "Games Lost" stat seems off.

The "Games Lost" stat seems off.

The next game I played it was in the 20000's.

Both of those errors were caused by me setting the wrong schedule for the system that increments those counters. Fixed 4aa65dd

After running my branch a few times (using the storage feature) after pulling your changes, it looks like the "games lost" isn't being properly saved in the database. It resets every time I re-run the game.

There seems to be a typo in some of the SQL

code.


Headless Renderer crashes if it encounters a GeometryGroup

If a GeometryGroup is used, the Headless renderer will crash with following exception, while being used in integration tests as example:
System.NotImplementedException The method or operation is not implemented.    at Avalonia.Headless.HeadlessPlatformRenderInterface.CreateGeometryGroup(FillRule fillRule, IReadOnlyList1 children)    at Avalonia.Media.GeometryGroup.CreateDefiningGeometry()    at Avalonia.Media.Geometry.get_PlatformImpl()    at Avalonia.Visual.SynchronizeCompositionProperties()    at Avalonia.Rendering.Composition.CompositingRenderer.UpdateCore()    at Avalonia.Rendering.Composition.CompositingRenderer.Update()    at Avalonia.Rendering.Composition.Compositor.CommitCore()    at Avalonia.Rendering.Composition.Compositor.Commit()    at Avalonia.Media.MediaContext.CommitCompositor(Compositor compositor)    at Avalonia.Media.MediaContext.CommitCompositorsWithThrottling()    at Avalonia.Media.MediaContext.RenderCore()    at Avalonia.Media.MediaContext.Render()    at Avalonia.Threading.DispatcherOperation.InvokeCore()    at Avalonia.Threading.DispatcherOperation.Execute()    at Avalonia.Threading.Dispatcher.ExecuteJob(DispatcherOperation job)    at Avalonia.Threading.Dispatcher.ExecuteJobsCore(Boolean fromExplicitBackgroundProcessingCallback)    at Avalonia.Threading.Dispatcher.Signaled()    at Avalonia.Controls.Platform.ManagedDispatcherImpl.RunLoop(CancellationToken token)    at Avalonia.Threading.DispatcherFrame.Run(IControlledDispatcherImpl impl)    at Avalonia.Threading.Dispatcher.PushFrame(DispatcherFrame frame)    at Avalonia.Headless.HeadlessUnitTestSession.<>c__DisplayClass9_01.<Dispatch>b__0()
Here is a quick example to reproduce this:
https://github.com/yankun/AvaloniaHeadlessCrash
To Reproduce
Create a view containing a geometry group and try to use it in a headless test session.
Expected behavior
The headless test session should not be affected by the use of geometry groups.

Sorry to bring this up, bus as 11.0.10 has been released my changes are still not included, so our IntegrationTests keep failing. Has the issue been forgotten?

@yankun should be in 11.1 beta


(PUP-6917) Enable app management keywords as attribute names

Prior to this commit, the parser would treat 'produces' and 'application'
as keywords (with app-management enabled) but not 'consumes' and 'site'.
This commit adds them to the list of keywords, which enables them to be
used as names of attributes.

CLA signed by all contributors.


Could not establish trust relationship for the SSL/TLS secure channel

Just to let everyone know that the following must be added to the script so that it works correctly
if ("TrustAllCertsPolicy" -as [type]) {} else {
        Add-Type "using System.Net;using System.Security.Cryptography.X509Certificates;public class TrustAllCertsPolicy : ICertificatePolicy {public bool CheckValidationResult(ServicePoint srvPoint, X509Certificate certificate, WebRequest request, int certificateProblem) {return true;}}"
        [System.Net.ServicePointManager]::CertificatePolicy = New-Object TrustAllCertsPolicy
}

Hey @marco-vaz ,
Thanks for your contribution! I did not have the opportunity to test it. I keep this issue open until I can test it and validate it.
Thanks again, I hope this script helped you!