About dataset txt file and training

Hello! I realized that the txt files of the datasets are not provided in your code, especially the test datasets (e.g. CASIA, NIST), which makes it impossible for me to run the training and test code, and I am not clear about the specific data division, can you provide the relevant txt files please?
btw, I would like to know exactly which parts of the dataset you used for model training?

@kerryhhh
For the inference, please follow this sec. Five inference datasets and the corresponding lists can be download in tar_data
The txt file for the training can be found in https://drive.google.com/drive/folders/1OIUv7OGxfAyerMnmKvrNnN_5CmIDcNxo

I also have the same confusion. In the code for loading the training set, I noticed that the file was read from a series of txt files, but I did not find the file named 'copy_move.txt' in the download link.And the files corresponding to the splice randmask and painting were not found either。

I also have the same confusion. In the code for loading the training set, I noticed that the file was read from a series of txt files, but I did not find the file named 'copy_move.txt' in the download link.And the files corresponding to the splice randmask and painting were not found either。

I had the same question, did you solve it?


Datastore.select - does it work with column names that have solely integers?

Hey dev team, we have a Datastore table like this:

As you can see, the column names are integers, i.e. IDs mapping to individual rows within another namespace > path.
Using the code found in this issue, I am able to select a column with a name like date, but not a column with a name like<PHONE_NUMBER>066624.
transaction.select(['date']); // this works :)
transaction.select(['date','4820477751066624']); // this does not work :(

Is it generally assumed that column names are strings with at least one letter as the starting character? Or can there be solely integer column names?
Here is my Datastore response:
{
    error: {
        code: 412,
        message: 'no matching index found.'
    }
}

I have double-triple checked to make sure I run the query using an integer that is definitely a column name for the table pictured above.
Thanks in advance for your help!

// @pcostell

Projection queries in Datastore are a little different compared to a traditional SQL projection. In particular, the projection only works if it is being run on an index (in fact, this is why we offer projection queries, so that the query only needs to perform an index scan and not the accompanied entity lookup).
In the case of transaction.select(['date','4820477751066624']);, you would need to have an index on (Date,<PHONE_NUMBER>066624) to perform the query. However, given the automatic indexes transaction.select(['4820477751066624']); should work.

Taking your advice and using GCloud v.0.18, here is the query:
Datastore.query({
    namespace: 'accounts',
    path: [ pathmap[ req.query.metric ] ],
    select: [n],
    filter: {
        "date >=": req.query.ds || m.startOf('month').unix(),
        "date <=": req.query.de || m.endOf('month').unix()
    }
}, function (error, stats) {
    console.dir(error);
});

Here is the transaction object before it is sent to the Datastore servers:
{
    namespace: 'accounts',
    kinds: [ 'analytics' ],
    filters:
    [ { name: 'date', op: '>=', val:<PHONE_NUMBER> }, { name: 'date', op: '<=', val:<PHONE_NUMBER> } ] ]
    orders: [],
    groupByVal: [],
    selectVal: [ '5666823336886272' ],
    autoPaginateVal: true,
    startVal: null,
    endVal: null,
    limitVal: -1,
    offsetVal: -1,
    ... [fns]
}

And here is the response:
{
    error: {
        code: 412,
        message: 'Precondition Failed'
    }
}

Using the same code I can make a query and select the date column. And yes I have noticed that everything is auto-indexed, so that is why I was hoping we could query by account number.

You can query by date in this case because it is already part of the index you are using (due to the inequality).
In order to answer this query, you would need an index on (date,<PHONE_NUMBER>886272).

Okay, I get it, thank you.


Add a shortcut or a button to restart extension host.

Right now if the extension host crashes we have to restart the editor , it would be awesome if we could add a button or shortcut for the same.

If the extension host crashes, there is a popup that contains a button to restart it. Have you seen that @siddhant1 ?

Yup , I have seen that , but sometimes u close that accidentally by removing all notifications and then I notice that my extensions are crashed! The only solution is restart the editor.

This crashes for me a lot. I think it would be nice to have information on why it crashes and for a way to restart to be easily done. I'm assuming CPU load is the issue for me as my computer's bottleneck is the CPU.

It will be more helpful if we put a button to the workspace bar below that will only appear when extension host crashes.

If the extension host crashes, there is a popup that contains a button to restart it. Have you seen that @siddhant1 ?

I’ve never seen that popup, so I’m guessing the extension host has never actually crashed on me.
It very frequently (as in, at least once an hour during normal work) becomes unresponsive, making extensions stop working. Or at least that’s what the output tab says (“UNRESPONSIVE extension host, [extension] took XX% of XXXXms, saved PROFILE here…”).
The only way to get the extension back then is to restart the entire editor, as far as I can tell. :-/

I have found the command palette 'Developer: Reload Window' works well for cases where the extension host crashes and you want to reload it without fully exiting and re-opening vscode. See https://stackoverflow.com/a/42002990/805031 for more info.

Even better, could you please restart the extension host automatically? Reporting that it has crashed, and then waiting for me to recognize that my editor is not working because I have to click an OK button is a bad experience. Rather, only notify me if the extension host is crashing repeatedly, and then provide some context as to what was happening when it crashed. Then I could actually do something to fix it (either disable an extension or restart my editor).

It is crazy that it happens, and that it happens so often.

First, why do you inform me about it in a first place instead of relaunching it immediately after this problem?
Secondly, why is this information for only few seconds and then disappears? If I go for a minute away from computer, VS Code does its amazing every-5-minutes-crash, and unless I remember to check, my extensions are not working.
At third, why there is no information what cause the problem? Exactly which extension is broken? What should I do to avoid in the future? Anything?
And at last, how to solve it? Restarting VS Code sounds for me the same nice as restarting the computer - so yeah... not so fancy way of solving software problem
Sorry Microsoft, but such mistakes  would be explainable for some small IT company who has no idea about UI and UX. Microsoft seems to not be such a company, so what's the problem?

When the extension host crashes, I typically hit ESCAPE to close any notifications. However, there is no option in the VSCode Command Palette for me to force the extension host to reload. The only option is to use the [slower] Reload Window option.
I would also like to see the ability to restart the extension host, from the Command Palette.


Speed up Travis by using bundle caching and container architecture

Why is the passenger commit included in the PR?

Or is this a bogus branch now?  I don't see bundler caching in the travis config anymore.

Btw, the failure above is actually a lie.  Click the link for proof.  Ready to merge?
Build finished in just a little over 10m!

Weird. Why is it showing failed in the first place?

It failed on the first run four weeks ago. :)  Then I re-ran the build when I saw this PR waiting here and presto.  Dunno why GitHub didn't update this page.


GeneratorApp Update [dataDictionary.MD]

See Improvement ticket #527
This ticket aims to create the dataDictionary.MD file which is based on dataStructure.yml. The dataDictionary.MD file will be used for the implementation guide.

See ticket #524 for issue with current app to be resolved in this version.


Mattcs create dev env

FYI the failing check above seems to have gotten conflated with PR #35 which was a test of the check. It doesn't actually apply to this PR.


Make node resolution environment aware

Is your feature request related to a problem? Please describe.
Hi folks,
Thanks for the great work, I wonder is it possible to make node resolution process to be environment (target) aware?
So in our use case lower environments (targets) like dev, ci are using one set of Snowflake tables for defer and we can put it in the manifest, but for higher environments (target) like prod the same model should be resolved to a different fully qualified name. If I rephrase the question can we hack generate_schema_name and generate_database_name macros to node resolution?
Describe alternatives you've considered
Not quite sure if there is a solution other than maintain N different manifests one for each environment, which doesn't look like an optimal and potentially error prone method.
Additional context
I'm ready to contribute to the solution with enough guidance provided.

Hi @zendesk-sova 👋🏻 Thanks for submitting this feature request. I think I understand the request, but I want to make sure that I have a complete mental model before I start digging in too deep. Can you please describe in a little more details precisely what the project and environment configuration looks like for your set-up? It sounds like there are two separate environments with separate snowflake objects attempting to share a manifest, and I'm not quite sure what this looks like in practice.
Thanks!

Hi @nicholasyager ,
Yes, we have multi-project multi-environment setup with complex database resolution logic. If I understand correctly plugin just takes fully qualified name from the manifest and uses it in models, and I'm asking if it's possible to dynamically resolve what database/schema would've been if we applied custom generate macros at the moment of execution.
The other moment with fixed prebuilt manifests, how to work with multiple targets locally as $DBT_TARGET environment variable is not synchronized with --target <target_name> and such kind of operations become extremely error prone.

Hello everybody!
Thanks for the contributions to [dbt-loom].
Is looks like a scenario for an alternative resolution is what [dbt-mesh] is doing, I am thinking about how that could be implemented in [dbt-loom] as well:
https://docs.getdbt.com/docs/collaborate/govern/project-dependencies#how-to-write-cross-project-ref
Safeguarding production data with staging environments
When working in a Development environment, cross-project refs normally resolve to the Production environment of the project. However, to protect production data, set up a Staging deployment environment within your projects. With a staging environment integrated into the project, any references from external projects during development workflows resolve to the Staging environment. This adds a layer of security between your Deployment and Production environments by limiting access to production data.

Thanks for the link, @sergey-vdovin! Based on the docs provided, it sounds like dbt Mesh is tracking state for both staging and production environments. I have a hunch that their proprietary systems are simply tracking manifests for all environments. This hunch is based on the requirement that one has a completed staging environment run prior to attempting to use cross-project refs.
In our case, dbt-loom is very simplistic. It has no concept of an environment. Rather, it assumes that the manifests being piped into it are exactly what we want. For this feature to be realistically implemented, we'd also need to have a concept of environment external to the concept of project. This is doable, but require more forethought and design around how we want to configure and implement. Maybe it can be rolled in with #61?
In any case, I'm open to suggestions!


EntryNotFound when using Arm Device-Manager to get svdPath

Type: Bug Report
Describe the bug

OS and Version: Ubuntu 22.04.6 LTS
VS Code Version: 1.83.1
Extension Version: Cortex Debug v1.12.1
Target Device: Silicon Labs EFR32MG24BXXXF1536
Other extensions you installed (and if the issue persists after disabling them): Arm Device Manager (yes), C/C++ (yes)

Issue
When starting a debug session via Cortex-Debug, in the XPERIPHERAL view, I get the following error message instead of a peripheral list:

To Reproduce
Steps to reproduce the behavior:

Setup my peripheral with the following settings:

        "version": "0.2.0",
        "configurations": [
            {
                "name": "JLink - Launch",
                "cwd": "${workspaceFolder}",
                "executable": "./build/debug/project.out",
                "request": "launch",
                "type": "cortex-debug",
                "interface": "swd",
                "svdPath": "${command:device-manager.getDevicePack}",
                "device": "${command:device-manager.getDeviceName}",
                "runToEntryPoint": "main",
                "gdbPath": "arm-none-eabi-gdb",
                "servertype": "jlink",
                "swoConfig": {
                    "source": "probe",
                    "enabled": true,
                    "swoFrequency": 875000,
                    "decoders": [
                        {
                            "port": 0,
                            "type": "console",
                        }
                    ]
                }
            }
         ]
      }

Start a debug session with the JLink - Launch configuration.
Check the XPERIPHERAL view.
See error

Expected behavior
A list of my device's peripheral in the view.
Code sample and logs
Cortex-Debug: VSCode debugger extension version 1.12.1 git(652d042). Usage info: https://github.com/Marus/cortex-debug#usage
Reading symbols from arm-none-eabi-objdump --syms -C -h -w <path to my project>/build/debug/project.out
Reading symbols from arm-none-eabi-nm --defined-only -S -l -C -p <path to my project>/build/debug/project.out
Launching GDB: arm-none-eabi-gdb -q --interpreter=mi2
    IMPORTANT: Set "showDevDebugOutput": "raw" in "launch.json" to see verbose GDB transactions here. Very helpful to debug issues or report problems
Launching gdb-server: JLinkGDBServer -singlerun -nogui -if swd -port 50000 -swoport 50001 -telnetport 50002 -device EFR32MG24BXXXF1536
    Please check TERMINAL tab (gdb-server) for output from JLinkGDBServer
Finished reading symbols from objdump: Time: 46 ms
Finished reading symbols from nm: Time: 59 ms
Output radix now set to decimal 10, hex a, octal 12.
Input radix now set to decimal 10, hex a, octal 12.
<my entry point> () at <path to my source file>

Program stopped, probably due to a reset and/or halt issued by debugger
2
Resetting target
SWO enabled successfully.

Additional context
As you can tell from my settings.json file, I'm using the ARM Device-Manager to resolve which SVD file I need for my device. It correctly identifies it and I can see that it's trying to fetch the correct SVD pack for it, but for some reason, cortex-debug is not able to use it. The SVD part of the configuration was done according to the official extension documentation, by leveraging the ARM Device Manager extension.
EDIT:
Since this is an issue related to the SVD viewer, I opened it under this repo, but let me know if the issue should be moved elsewhere.

Thanks for the bug report. I suspect the issue is in a different extension, but I'll investigate...

I can see there is an issue with the space in the vendor name silicon labs.
While we investigate further, you should be able to use this as a workaround:
    ...
    "cmsisPack"<EMAIL_ADDRESS>    ...

Also, I notice you have an entry in your config called device. I think this should be deviceName.

Ah-ha! That whitespace was indeed my issue. However, on my end the device field is indeed correct, changing it to deviceName results in a Property is not allowed prompt in my settings.json.

I'll report this in the ARM device manager extension, as it seems to be the culprit. Cheers!

I've fixed this in the latest device manager release, v1.9.7


Wait for listening socket to close in shutdown callbacks test

This resolves a failure of the subsequent test with the error
"listen tcp :9654: bind: address already in use".
Fix #60

Fantastic! Thank you!


Remove containerContext.id deprecation

Need to remove id again after FFX side removes their usages of continerContext.id
Originally posted by @heliocliu in https://github.com/microsoft/FluidFramework/pull/9156#discussion_r808552719

no longer need to remove, we can undeprecate this


Pin length inconsistency between view and password count

I had this issue in some projects where setting pin length to another length rather than the default value would update the view but the password count is still 5 leading to either crashes when the pin length is greater than the default value or not triggering didFinishCallback if less than 5.
I fixed this issue by moving the password array initialization to the collection view delegate method numberOfItemsInSection rather than in loadView that gets called in init method.
SVPin version : 1.0.6
Deployment Target : iOS 11
it doesn't appear in iOS 12.1 projects though.

Yes. Its too annoying to me. I am getting same error. My configuration in below,
      mobileOtp.pinLength = 4
       mobileOtp.didFinishCallback = didFinishEnteringPin(pin:)
       mobileOtp.didChangeCallback = { pin in
           print("The mobileOtp pin is \(pin)")
       }

func didFinishEnteringPin(pin: String) {
       print("mobileOtp entered is \(pin)")
       self.showAlertWithTitle(title: "", message: pin)
   }

My console output is,

Therefore my **mobileOtp.didFinishCallback** could not called when I reach 4 digit password.

My deployment target is **11.0**
iOS : 12.1.4

Please share the solution to get rid of this issue. Thanks in advance.

@Mostafa3la2 @ssowri1 Apologies for the delay, have fixed the issue and made a release (1.0.7). Do let me know in case of any further issues.
Thanks.

@xornorik: Thank you for your support.


Can I reuse

Can I reuse my viewcontroller?

Hi,
Currently not, might be something I'll add in the future.

I think reuse the controllers may cause a lot problems happen such as a  confused viewController life cycle. Maybe, cache the viewControllers as many as possible and dealloc some controllers when receive memoryWarning is a better way? @MerrickSapsford @wenzhaot


Testing issues on ARM

Hello there.
I'm having some issues running tests of version 4.2.3 on a Cavium ThunderX2 node running centos 7.7.

About the first one: can you try again by replacing this line:
https://github.com/devitocodes/devito/blob/master/devito/compiler.py#L557
with
obj = super().__new__(cls)

?
if it works, could you open a PR applying this simple patch? Guidelines available here

About the other set of issues. The key thing to notice is:
E           OSError: /tmp/devito-jitcache-uid927800007/d7c6f77c0044b47f33dd888e61168861bcb53547.so: undefined symbol: omp_get_thread_num

It appears to be unable to compile OpenMP.
I think the actual issue is that the system you're running on has some preset CC, CFLAGS, CXX or LDFLAGS environment variables, so Devito won't use its own preset flags to compile the generated code, which may or may not include OpenMP (those tests do). You could either unset those flags in your environment, or tell Devito to use a very specific compiler. Assuming you're on bash, you could
export DEVITO_ARCH=gcc-9.2.0

which hopefully should make the trick

And if you got that far, I'd assume you didn't encounter the ARM related issues reported here. Right?

@FabioLuporini The first one worked just fine, thank you. Now all test_operator.py tests are passing.
The second issue remains, however. When runing with DEVITO_ARCH=gcc, the error message now is the following (for all the same tests).
self = <test_dse.TestAliases object at 0x400041992898>
def test_full_shape(self):
"""
Check the shape of the Array used to store an aliasing expression.
 Right?

@FabioLuporini Regarding #1043 , I've only tested the 2nd edit and it worked.

Could you open Pull Requests to address these small issues?

I can see that in your logs:

  op2 = Operator(Eq(u, u + 1), platform='nvidiaX')

Please try setting DEVITO_PLATFORM=arm
We are working on a patch to solve issues ASAP.

@fcannini this PR: https://github.com/devitocodes/devito/pull/1515
is supposed to fix the issues with ARM, and is tested on ThunderX2.
as shown here:
https://github.com/devitocodes/devito/wiki/[Manual]-Installing-Devito-on-ARM.-Tested-on-GW4-Isambard
Can you try it?
Your compilation issue logged as:
/tmp/devito-jitcache-uid927800007/e20a23bf10888f2e802213becebab45f3cf8d1a5.c: In function ‘bf0’:
/tmp/devito-jitcache-uid927800007/e20a23bf10888f2e802213becebab45f3cf8d1a5.c:78:43: error: expected iteration declaration or initialization before ‘x’
78 |         for (int x = x0_blk0 - 1, xs = 0; x <= x0_blk0 + x0_blk0_size; x += 1, xs += 1)
|                                           ^
/tmp/devito-jitcache-uid927800007/e20a23bf10888f2e802213becebab45f3cf8d1a5.c:80:45: error: expected iteration declaration or initialization before ‘y’
80 |           for (int y = y0_blk0 - 1, ys = 0; y <= y0_blk0 + y0_blk0_size; y += 1, ys += 1)
|                                             ^
/tmp/devito-jitcache-uid927800007/e20a23bf10888f2e802213becebab45f3cf8d1a5.c:90:39: error: expected iteration declaration or initialization before ‘x’
90 |         for (int x = x0_blk0, xs = 0; x <= x0_blk0 + x0_blk0_size - 1; x += 1, xs += 1)
|                                       ^
/tmp/devito-jitcache-uid927800007/e20a23bf10888f2e802213becebab45f3cf8d1a5.c:92:41: error: expected iteration declaration or initialization before ‘y’
92 |           for (int y = y0_blk0, ys = 0; y <= y0_blk0 + y0_blk0_size - 1; y += 1, ys += 1)
|                                         ^
FAILED compiler invocation:gcc -O3 -g -fPIC -Wall -std=c99 -Wno-unused-result -Wno-unused-variable -Wno-unused-but-set-variable -ffast-math -shared -fopenmp /tmp/devito-jitcache-uid927800007/e20a23bf10888f2e802213becebab45f3cf8d1a5.c -lm -o /tmp/devito-jitcache-uid927800007/e20a23bf10888f2e802213becebab45f3cf8d1a5.so

is probably happening due to faulty core autodetection. (It happened to me as well.)
The PR mentioned above is supposed to fix it.
Let us know if this works for you.

@georgebisbas  When running with DEVITO_PLATFORM=arm the error messages are the same as my first message.

PR #1515 is not supposed to fix all tests, as code generation is kinda different for AMR kernels (no denormals flushing etc...)
but you should be able to run al operators and most of the tests. Could you have a look at it?
--George

@georgebisbas I've applied #1515 as a patch but still the same tests are failing.
test_dse.py::TestAliases::test_full_shape
test_dse.py::TestAliases::test_contracted_shape
test_dse.py::TestAliases::test_uncontracted_shape
test_dse.py::TestAliases::test_full_shape_w_subdims
test_dse.py::TestAliases::test_mixed_shapes

Hi again @fcannini , may I ask how you run these tests? (reproducibility instructions?).
I am using a ThunderX2 as well.
So, just to note that at this moment we are not expecting all the tests to pass cause we do not have yet an ARM-CI and the code-generation is kinda different from the typical CPU code generation.
However, the above tests pass for me! :
brx-gbisbas@xcimom2:~/pbs.77294.xci00.x8z/devito> python3 -m pytest tests/test_dse.py::TestAliases::test_full_shape
======================================================= test session starts =======================================================
platform linux -- Python 3.6.5, pytest-6.1.2, py-1.9.0, pluggy-0.13.0
rootdir: /lustre/home/brx-gbisbas/pbs.77294.xci00.x8z/devito, configfile: setup.cfg
plugins: forked-1.3.0, nbval-0.9.3, xdist-2.1.0, cov-2.8.1
collected 2 items

tests/test_dse.py ..                                                                                [100%]

======================================================== warnings summary =========================================================
../../../../../opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219
../../../../../opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219
  /opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 216, got 192
    return f(*args, **kwds)

../../../../../opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219
  /opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 192 from C header, got 216 from PyObject
    return f(*args, **kwds)

-- Docs: https://docs.pytest.org/en/stable/warnings.html
====================================================== slowest 20 durations =======================================================
2.53s call     tests/test_dse.py::TestAliases::test_full_shape[False]
1.99s call     tests/test_dse.py::TestAliases::test_full_shape[True]

(4 durations < 0.005s hidden.  Use -vv to show these durations.)
================================================== 2 passed, 3 warnings in 8.81s ==================================================
brx-gbisbas@xcimom2:~/pbs.77294.xci00.x8z/devito> python3 -m pytest tests/test_dse.py::TestAliases::test_contracted_shape
======================================================= test session starts =======================================================
platform linux -- Python 3.6.5, pytest-6.1.2, py-1.9.0, pluggy-0.13.0
rootdir: /lustre/home/brx-gbisbas/pbs.77294.xci00.x8z/devito, configfile: setup.cfg
plugins: forked-1.3.0, nbval-0.9.3, xdist-2.1.0, cov-2.8.1
collected 2 items

tests/test_dse.py ..                                                                                [100%]

======================================================== warnings summary =========================================================
../../../../../opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219
../../../../../opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219
  /opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 216, got 192
    return f(*args, **kwds)

../../../../../opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219
  /opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 192 from C header, got 216 from PyObject
    return f(*args, **kwds)

-- Docs: https://docs.pytest.org/en/stable/warnings.html
====================================================== slowest 20 durations =======================================================
2.16s call     tests/test_dse.py::TestAliases::test_contracted_shape[False]
1.93s call     tests/test_dse.py::TestAliases::test_contracted_shape[True]

(4 durations < 0.005s hidden.  Use -vv to show these durations.)
================================================== 2 passed, 3 warnings in 5.26s ==================================================
brx-gbisbas@xcimom2:~/pbs.77294.xci00.x8z/devito> python3 -m pytest tests/test_dse.py::TestAliases::test_mixed_shapes
======================================================= test session starts =======================================================
platform linux -- Python 3.6.5, pytest-6.1.2, py-1.9.0, pluggy-0.13.0
rootdir: /lustre/home/brx-gbisbas/pbs.77294.xci00.x8z/devito, configfile: setup.cfg
plugins: forked-1.3.0, nbval-0.9.3, xdist-2.1.0, cov-2.8.1
collected 2 items

tests/test_dse.py ..                                                                                [100%]

======================================================== warnings summary =========================================================
../../../../../opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219
../../../../../opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219
  /opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 216, got 192
    return f(*args, **kwds)

../../../../../opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219
  /opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 192 from C header, got 216 from PyObject
    return f(*args, **kwds)

-- Docs: https://docs.pytest.org/en/stable/warnings.html
====================================================== slowest 20 durations =======================================================
2.72s call     tests/test_dse.py::TestAliases::test_mixed_shapes[False]
2.59s call     tests/test_dse.py::TestAliases::test_mixed_shapes[True]

(4 durations < 0.005s hidden.  Use -vv to show these durations.)
================================================== 2 passed, 3 warnings in 6.61s ==================================================
brx-gbisbas@xcimom2:~/pbs.77294.xci00.x8z/devito> python3 -m pytest tests/test_dse.py::TestAliases::test_full_shape_w_subdims
======================================================= test session starts =======================================================
platform linux -- Python 3.6.5, pytest-6.1.2, py-1.9.0, pluggy-0.13.0
rootdir: /lustre/home/brx-gbisbas/pbs.77294.xci00.x8z/devito, configfile: setup.cfg
plugins: forked-1.3.0, nbval-0.9.3, xdist-2.1.0, cov-2.8.1
collected 2 items

tests/test_dse.py ..                                                                                [100%]

======================================================== warnings summary =========================================================
../../../../../opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219
../../../../../opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219
  /opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 216, got 192
    return f(*args, **kwds)

../../../../../opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219
  /opt/python/<IP_ADDRESS>/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 192 from C header, got 216 from PyObject
    return f(*args, **kwds)

-- Docs: https://docs.pytest.org/en/stable/warnings.html
====================================================== slowest 20 durations =======================================================
2.53s call     tests/test_dse.py::TestAliases::test_full_shape_w_subdims[False]
2.40s call     tests/test_dse.py::TestAliases::test_full_shape_w_subdims[True]

(4 durations < 0.005s hidden.  Use -vv to show these durations.)
================================================== 2 passed, 3 warnings in 6.00s ==================================================

Nevertheless there are quite a few failing tests with this patch. In order to see all tests failing and not just 5 (default maxfail value) try running with pytest --maxfail 100
(100 can be a whatever big value....)
Those tests are affected by the code generation procedure followed and are mostly expected to fail.
May I ask what is your main purpose for this?
Cause I guess, if you would like to run Devito operators you should be just fine to continue your work as that aspect seems to be just fine.
Let me know about reproducibility instructions and how you test please. Thanks a lot.

Those tests are affected by the code generation procedure followed and are mostly expected to fail.
May I ask what is your main purpose for this?

I'm not an user of devito, I'm "the IT guy" tasked to install it on behalf of a client. I'm using the tests as a sort of checklist to see if everything is okay so I can deliver it to the users.

Cause I guess, if you would like to run Devito operators you should be just fine to continue your work as that aspect seems to be just fine.

Am I correct in understanding that these failures aren't that big of a deal?

Let me know about reproducibility instructions and how you test please. Thanks a lot.

HI again,
Not all Devito tests are expected to run on ARM. As far as I can tell, Devito is installed correctly and should work fine. Should your users bump into any issues, please tell them to get in touch with us directly (e.g., on our Slack workspace) .
You should be able to run wave-propagators in Devito without problems.
e.g. on ARM Thunder X2 I see that wave-propagator operators are running.

@georgebisbas I don't think it merits a PR, but this gist should be helpful (somehow)
https://gist.github.com/fcannini/70b66c0bea604d7f62ab9e83ba7b9b0f

HI @fcannini, my apologies for the delay here. This PR : https://github.com/devitocodes/devito/pull/1515/files
should have solved quite a few issues and has been useful for us in the last months.
Though Devito still doesn't have ARM CI, so support is not guaranteed.
I am closing this issue now, let us know if you need any help, either by reopening this issue or by posting in our Slack, and specifically in the #arm channel. Thanks.


Add maildev package

Good Node alternative to Mailcatcher Gem
http://djfarrelly.github.io/MailDev/

Can add it in your own after scripts.


added space on build.gradle

added space on build.gradle file

@Chimakurthi7788 Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.


LiveQuery failed on android because of mapblock

Hi guys
When using couchbase with nativescript, livequeries failed because of this class:
com.couchbase.lite.store.SQLiteViewStore$AbstractMapEmitBlock
Emit must document must be done from Nativescript (JS) so it is calling AbstractMapEmitBlock.emit using Java Reflection. It causes : ClassNotFoundException
It fails because AbstractMapEmitBlock is an private inner class. Is it possible to make it a public (non inner) class?
Thanks

Hi @nabil-mansouri,
I don't know why you have faced ClassNotFoundException. Do you include couchbase-lite-java-javascript.jar in your project?

@nabil-mansouri
Do you know how react-native manage Java ClassLoader? Based on your comment, it seems the thread has own ClassLoader and it is different from main. You might need to set class path to ClassLoader of non-main thread (this is just my guess).

Hi @hideki  thank you for your advice! Since i have tried to find the cause of this exception and i tried to play with Classloader but no result. I opened an issue on Nativescript Runtime it seems that it can't find classes when we are using Java thread (they use a cache class...). So i think that "ClassNotFoundException" is not a couchbase issue i am waiting their replies!
However i implement iOS part of my plugin and i have the same issue as android: livequery failed, it never send changes to listeners.
Do i need in my unit test to create documents from another database instance to see it in live query listener? Because now i am creating and listening query rows in the same database instance? Do i need to call some method (like waitRows?) before listening changes?
I did it here ("should live query"):
https://github.com/nabil-mansouri/nativescript-couchbaselite/blob/master/tests/app/tests/couchbase.ts

Hi @jamiltz
As I am not familiar with how CBL for react-native works, can you help @nabil-mansouri ?

That's related to Nativescript which is in @nraboy's department ;)

@nabil-mansouri,
LiveQuery was not added to the NativeScript plugin, so I'm assuming you've made your own implementation of it?  Mind sharing your forked repository or pasting the plugin function?


Update README.md to include necessary step

Include a step that is necessary to use the task in the build.gradle file.

Could you please clarify why is this step necessary?

Without this I get a Unresolved reference: tasks error when I run ./gradlew build.
Since the buildscript itself needs the dependency com.github.Orangesoft-Development:lokalise-loader:<version> to resolve the new task tasks.LokaliseUpdateTask the classpath keyword is used.
Loading a dependency with classpath loads it in such a way that it can be used in the same buildscript.


msys2's mingw-w64-x86_64: attached gdb causes multithreaded test to crash on thread termination

Description
May be distantly related to #401
Steps to reproduce

Install msys2 and pacman -S mingw-w64-x86_64-gcc mingw-w64-x86_64-gdb
Create a directory with the latest doctest.h (I've used both 2.4.6 and 2.4.1) and the following code in test.cpp:

#define DOCTEST_CONFIG_IMPLEMENT_WITH_MAIN
#include "doctest.h"
#include <thread>

TEST_CASE("Test thread") {
    std::thread([&]() {
        CHECK(2 * 2 == 4);
    }).join();
}

Compile it with g++ test.cpp -o test.exe (IIRC, no optimizations by default).
Run test.exe, test with a single assertion passes.
Now run gdb -ex run -ex where -ex "set confirm off" -ex q test.exe (same as running gdb test.exe and typing run, where, q and confirming)

Expected result: program runs, and the test with a single assertion passes.
Actual result:
GNU gdb (GDB) 10.1
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-w64-mingw32".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<https://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from test.exe...
Starting program: F:\_0_MAIN\Teach\2020\cpp\drafts\210427\test.exe
warning: [doctest] doctest version is "2.4.6"
[doctest] run with "--help" for options
[New Thread 11008.0x2070]
warning: Critical error detected c0000374

Thread 2 received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 11008.0x2070]
0x00000000774cf680 in ntdll!RtlUnhandledExceptionFilter ()
   from C:\Windows\SYSTEM32\ntdll.dll
#0  0x00000000774cf680 in ntdll!RtlUnhandledExceptionFilter ()
   from C:\Windows\SYSTEM32\ntdll.dll
#1  0x00000000774cfc86 in ntdll!EtwEnumerateProcessRegGuids ()
   from C:\Windows\SYSTEM32\ntdll.dll
#2  0x00000000774d08a2 in ntdll!RtlQueryProcessLockInformation ()
   from C:\Windows\SYSTEM32\ntdll.dll
#3  0x00000000774d29b4 in ntdll!RtlLogStackBackTrace ()
   from C:\Windows\SYSTEM32\ntdll.dll
#4  0x000000007743a0b0 in ntdll!RtlFreeHeap ()
   from C:\Windows\SYSTEM32\ntdll.dll
#5  0x000007feff0310c8 in msvcrt!free () from C:\Windows\system32\msvcrt.dll
#6  0x000007fecca29827 in ?? ()
   from C:\Software\msys64\mingw64\bin\libstdc++-6.dll
#7  0x000000013fc299a6 in run_dtor_list (ptr=<synthetic pointer>)
    at C:/_/M/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/tls_atexit.c:59
#8  tls_callback (hDllHandle=<optimized out>, dwReason=<optimized out>,
    lpReserved=<optimized out>)
    at C:/_/M/mingw-w64-crt-git/src/mingw-w64/mingw-w64-crt/crt/tls_atexit.c:155
#9  0x0000000077455088 in ntdll!RtlpUnWaitCriticalSection ()
   from C:\Windows\SYSTEM32\ntdll.dll
#10 0x000000007744868f in ntdll!LdrShutdownThread ()
   from C:\Windows\SYSTEM32\ntdll.dll
#11 0x0000000077453ee8 in ntdll!RtlExitUserThread ()
   from C:\Windows\SYSTEM32\ntdll.dll
#12 0x000007feff034213 in msvcrt!_endthreadex ()
   from C:\Windows\system32\msvcrt.dll
#13 0x000007fef1394f6e in ?? ()
   from C:\Software\msys64\mingw64\bin\libwinpthread-1.dll
#14 0x000007feff03415f in srand () from C:\Windows\system32\msvcrt.dll
#15 0x000007feff036ebd in msvcrt!_ftime64_s ()
   from C:\Windows\system32\msvcrt.dll
#16 0x00000000772059cd in KERNEL32!BaseThreadInitThunk ()
   from C:\Windows\system32\kernel32.dll
#17 0x000000007746383d in ntdll!RtlUserThreadStart ()
   from C:\Windows\SYSTEM32\ntdll.dll
#18 0x0000000000000000 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

How to make the issue go away

Comment out CHECK inside the second thread.

Extra information

doctest version: v2.4.6
Operating System: Windows 7 Pro x64 En
Compiler+version: g++ (Rev10, Built by MSYS2 project) 10.2.0 (64-bit)

Looks like a tooling bug, not doctest's bug. The following code exhibits the same behavior (works ok, but crashes under gdb):
#include <sstream>
#include <thread>

int main() {
  std::thread([&]() {
    thread_local std::ostringstream oss;
    oss.clear();
  }).join();
}

I will now try reporting it to msys2.

Looks like mingw-w64 issue, not msys2-specific, so I filed it under https://sourceforge.net/p/mingw-w64/bugs/893/

Ok, so it's a very old mingw issue: non-trivial destructors of thread_local variables may be called in a wrong order, including being called after the underlying memory is free (which is what happens here), see https://github.com/msys2/MINGW-packages/issues/2519 , https://github.com/msys2/MINGW-packages/issues/7096 and https://sourceforge.net/p/mingw-w64/bugs/527/#9a0c
No remedy or workarounds are available at the time except not using thread_local, as far as I understood.

You can avoid the use of thread_local by simply defining DOCTEST_THREAD_LOCAL (without a value) before including doctest.h

Kinda works, but I'd prefer to avoid calling CHECKs in other threads at all.
It looks to me like a direct way to race conditions on DOCTEST_THREAD_LOCAL std::ostringstream g_oss and similar namespace-scoped variables. Also, INFO blocks get messed up because of g_infoContexts, e.g. in
#define DOCTEST_THREAD_LOCAL
#define DOCTEST_CONFIG_IMPLEMENT_WITH_MAIN
#include "doctest.h"
#include <thread>

TEST_CASE("Test thread") {
    std::thread t([&]() {
        INFO("second thread");
        CHECK(2 * 2 == 5);
    });
    INFO("first thread");
    CHECK(2 * 2 == 6);
    t.join();
}

both CHECKs log both first thread and second thread, at least on my machine.
Actually, not sure how to work around that: one really need that g_infoContexts to be thread-local and it cannot be passed around.

Kinda works, but I'd prefer to avoid calling CHECKs in other threads at all.

Well if you'll be avoiding asserts in multiple threads from a single test case then you can indeed simply define DOCTEST_THREAD_LOCAL to nothing and not have to worry about the globals.

Ah, yes, sorry, it makes perfect sense in this case to avoid other unknown complications with thread_local (if any).

When compiling with mingw32-w64, this issue affects normal runs, not just when attached to the debugger.
I'm using mingw-w64, i686-8.1.0-release-posix-dwarf-rt_v6-rev0.
The exit code is a non-zero value and the exit takes longer because Windows is collecting a crash report:
[doctest] doctest version is "2.4.6"
[doctest] run with "--help" for options
===============================================================================
[doctest] test cases: 18 | 18 passed | 0 failed | 0 skipped
[doctest] assertions: 70 | 70 passed | 0 failed |
[doctest] Status: SUCCESS!

Process finished with exit code -1073741819 (0xC0000005)

I added this to my CMakeLists.txt and the process now exits with 0 like expected and is much quicker.
if (WIN32 AND (CMAKE_CXX_COMPILER_ID STREQUAL GNU))
    set(DOCTEST_THREAD_LOCAL "")
endif()

If I understand correctly this is not a doctest bug.
I suggest the issue + the workaround to be added to the docs.


TE Crash when clearing out of bounds

Rect clearing off the right side of the level In tile editor causes a crash, doesn't happen in other editors or with the left side

fixed, posting new patch


Encoding Parameter for Tee-Object

PR Summary
Adds an Encoding parameter to the Tee-Object cmdlet (See issue #11104)
PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[x] Documentation needed

[x] Issue filed: MicrosoftDocs/PowerShell-Docs#5612

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Peter-Schneider sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Ha, you beat me to it. 😁

@vexx32 Thank you anyway.. ;-) What does the "Waiting on Author" label mean?

@Peter-Schneider Please add tests.

@Peter-Schneider Please open new issue in PowerShell-Docs repo for the new parameter and add reference in the PR description.

@SteveL-MSFT @TravisEz13 Could you please look CI failures? It seems it is not the PR related.

@iSazonov The windows failure definitely seem related to this branch.  Perhaps a rebase is needed.

@Peter-Schneider Please rebase. You will switched to new .Net version - 5.0 Preview1, so you should install it.

@vexx32 Please review again (new commits).

@iSazonov Thank you for your patience!

@SteveL-MSFT @TravisEz13 The PR is waiting MSFT team review.

@Peter-Schneider Please resolve merge conflicts.

@Peter-Schneider Please address CI failures.

@TravisEz13 @SteveL-MSFT Could you please review the PR.

Reopen to update CIs.

@SteveL-MSFT Can we merge?

@SteveL-MSFT Can we merge?

@iSazonov I think this is good to go.  thanks.

@Peter-Schneider Thanks for your contribution!

Thanks for merging! :partying_face:


Redo process requeust/response in backends

Request -> response logic is hacky - clean up.

This issue was moved to StackHut/stackhut-toolkit#24


fluxcd updated even if fluxcd terraform provider version stays the same

the fluxcd terraform providers behaviour is a bit unpredictable.
if i run the same terraform definition after a week for example, a lot of changes regarding docker image version and so are introduced sometimes, changing the deployment in the cluster even if nothing in the terraform files has changed.
imho this should not happen.
updates to the k8s resources should only happen, if the terraform provider was updated too.

The terraform provided downloads the manifests from GitHub, so if you don’t set a flux version in tf, you’ll endup with the latest stable release.

Hmmm... Any chance you'll add a fixed version by default to the next flux provider releases?
Feels a bit like using latest as docker image tag at the moment 😁

The question is what should the version default to in this case? We would need to update the flux version when we update the provider in that case. I can add a note about setting the version but the provider should behave in the same way as the CLI, which today uses the latest version when run, if nothing else is specified.

So the CLI with version 0.7.0 would install flux version 0.8.0 too, if available?

Yes I would expect that to happen, as the Terraform provider and CLI uses the same code in its core. The default value for the version parameter in the provider is derived from here in fluxv2. Which has the value latest.
https://github.com/fluxcd/flux2/blob/a2887f5776f48797ae77820192ad6d0d60743e21/pkg/manifestgen/install/options.go#L43
Looking at the CLI code the same default value is used. It can be verified if you run flux bootstrap --help which will return.
 -v, --version string             toolkit version (default "latest")

Ok, i will add it manually.
Nevertheless I think it should be documented that the config is not idempotent.


[Bug]: Why is the React documentation in German only for the landing page and not the whole docs?

Summary
When I try to open the German version of the docs, only the landing page in de.react.dev is in German, but the rest of the app is still in English.

Is it still in development?
I look forward to an answer from the community, otherwise I could go ahead, and contribute myself.
Page
de.react.dev
Details
Is it still in development?
I look forward to an answer from the community, otherwise I could go ahead, and contribute myself.

Hello @bcostaaa01, translations for every language are done on separate repositories. For german, you should check the progress on de.react.dev.

Thanks for the reply, and information @rammba! So, I should open an issue there then?


dotnet: Build for .NET 8, the current LTS version

Simply update the .NET client project to build for net8.0 alongside the previous version, 7.0 and change the GitHub Workflow to use dotnet tool version 8.0.x instead ofo 7.0.x
.NET 7 is already out of support and .NET 8 is the current LTS version
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core#lifecycle

Thanks so much for the heads-up @woksin, we missed the .net 7.0 EOS notice in May 14th!
I think we can abandon .net7.0, so I also updated the related projects, docs and CI scripts.

Thanks so much for the heads-up @woksin, we missed the .net 7.0 EOS notice in May 14th!
I think we can abandon .net7.0, so I also updated the related projects, docs and CI scripts.

Thanks for cleaning up my cleanup, @batiati. I could also help with making the .net client more idiomatic .NET, at least in terms of setup and configuration, if you would want and appreciate that 😃


Configuration for Evaluators

Strategize uses evaluators to define how a collection of rules or policies should be evaluated and returned to the system. The RuleEvaluator and PolicyEvaluator classes are provided as the default evaluators.
Implement a configuration block for Strategize that would allow developers to easily define their own evaluators and plug them into Strategize.
Strategize.configure do |config|
  config.rule_evaluator = Custom::RuleEvaluator
  config.policy_evaluator = Custom::PolicyEvaluator
end

This would also help to ease the current requirement that when you using Strategize with the default evaluators, you the developer must still define each evaluator. A global config object would remove this need and ease getting started with Strategize.

This feature is available in version 0.0.4


How do you resample upscale an image using wasm-vips?

Loading the image like this works fine.
const vips = await Vips();
let im = vips.Image.newFromFile('in.jpg');
What I do not know is the syntax for resampling and upscaling an image using lanzcos3.
It looks like I need to use vips.affine as shown in the vips docs.  What would my javascript statement be in order to resample upscale my image.
Thanks,
Dan

Thank you for the suggestion.  I mistakenly put .jpg but I am actually resampling a png heightmap file so I need the quality.  Example in GIMP I can open my 512x512 in.png choose Image > Scale to 2017x2017 set Interpolation to NoHalo click resample and then export the png using the defaults and get the expected results of attached out.png.  Attached are my input and output files from GIMP if this helps.  Thank you very much for your help.
in.png 512x512 heightmap png

out.png 2017x2017
I have also tested the same process with Affinity Photo and selecting Lanzcos3 and I get the expected results as well.


Set re-tiling id in sub-block metadata

In order to avoid unnecessary(and erroneous) stitching of the files created by warpaffine, I propose to add the re-tiling metadata to the created sub-blocks. This metadata allows to handle blocks with the same id as one contiguous area.

just thinking loud... If I get this right, then (in the file dowarp.cpp) in DoWarp::InputBrick (line 305) we are given one "source brick", and everything that derives from this "source brick" needs to have the same slice_id. So, I wonder - wouldn't this be the right place to assign a slice_id? I mean - by simply incrementing a counter, as opposed to reading the slice_id from the destination_brick_info  (line 322). If so... I wouldn't see necessity to add slice_id to the BrickInfo-struct at all. We could pass the slice_id as an additional argument to DoWarp::ProcessBrickCommon2 (line 336), and from there we could pass it to DoWarp::ProcessOutputSlice (line 391), where it then is put into the ICziSlicesWriter::AddSliceInfo and passed to the writer.
Sidenote: maybe slice_id is not the best name, at least I'd associate a particular z-slice with it (and that's not what I understand its purpose is). It is in order to mark "bricks origination from the same source-brick", right? So - what about source_brick_id? And, it should be documented that no particular order is implied here, the guarantee is only "it is a unique number for all bricks originating from the same source-brick".
Getting rid of the addition of slice_id to BrickInfo I would see as a good thing - I'd argue that BrickInfo is meant to describe a brick at its lowest level, or just the bitmap-representation of it. It does not feel right to add "metadata" (or: information associated with a particular brick) to this structure, this should be the business of "upper layers". Yeah, if it fits the bill and makes things easier (= no requiring a larger refactoring), I would be fine with it, but if we can avoid it as I sketched above, I'd go for it.

Would it be asked too much to follow the existing code's brace style :-) ?

What would need to be done in addition (besides functional changes):

Bump the version number https://github.com/ZEISS/warpaffine/blob/31b2f65b49281cc2a935c61005f160948d251500/CMakeLists.txt#L22C19-L22C24 . According to semver, I'd think this would be an increment of MINOR version, so 0.4.0.
add to version-history - which, btw, was forgotton with this PR  also...
best case... update usage.md with the latest synopsis and a short explanation whtat the new command-line argument does.

Can you do me a favor and add a line to version-history.md, something like
0.3.2              |  3     | bugfix for a deadlock in rare case


Allow filtering by metadata entities that have caused graph validation errors

Story
As a wrangler, I want to be able to see a summary of metadata entities that have caused graph validation errors and filter by them.
Background
After #546, submission states for graph validation have been added. Before #546, the graph validator was setting the validation state of metadata documents to INVALID, which, in turn, sets the submission state to INVALID. This meant the user could just filter by metadata entities that were invalid because of graph validation errors or metadata validation errors. Now that the graph validation state is included in the overall submission state, setting the overall submission state to INVALID after graph validation is not possible due to complications with state transitions. The submission state now transitions to a new GRAPH_INVALID state.
Technical task
We don't need a graphValidationState on metadata documents as it can only be VALID or INVALID, hence, the presence of graphValidationErrors should suffice. graphValidationErrors are removed whenever graph validation is requested.

[x] Allow filtering by metadata entities that have graphValidationErrors.length > 0 (core)
[x] Include a count of entities with graphValidationErrors in the submission summary (core)
[x] Display the new count in the summary (UI)
[x] Display option to filter by entities with graph validation errors (UI)

PRS:

https://github.com/ebi-ait/ingest-ui/pull/145
https://github.com/ebi-ait/ingest-core/pull/103

Testing this

Tested (see comment on #546), works fine!
I noticed that seems slower than usual to show non-filtered entities, is that normal though?


Can you help me: what am I doing wrong?

Hi there,
I am new to this and trying to get oauth2 installed. Here's what I get. Thanks for your help!
%run /Users/stephanesantos/Desktop/Project_Albuquerque/python-oauth2-master/setup.py
An exception has occurred, use %tb to see the full traceback.
SystemExit: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: no commands supplied
%tb
SystemExit                                Traceback (most recent call last)
/Applications/Canopy.app/appdata/canopy-<IP_ADDRESS>0.macosx-x86/Canopy.app/Contents/lib/python2.7/site-packages/IPython/utils/py3compat.pyc in execfile(fname, *where)
181             else:
182                 filename = fname
--> 183             builtin.execfile(filename, *where)
/Users/stephanesantos/Desktop/Project_Albuquerque/python-oauth2-master/setup.py in ()
38       zip_safe = True,
39       test_suite="tests",
---> 40       tests_require=['coverage', 'mock'])
/Applications/Canopy.app/appdata/canopy-<IP_ADDRESS>0.macosx-x86/Canopy.app/Contents/lib/python2.7/distutils/core.pyc in setup(**attrs)
138         ok = dist.parse_command_line()
139     except DistutilsArgError, msg:
--> 140         raise SystemExit, gen_usage(dist.script_name) + "\nerror: %s" % msg
141
142     if DEBUG:
SystemExit: usage: setup.py [global_opts] cmd1 [cmd1_opts] [cmd2 [cmd2_opts] ...]
or: setup.py --help [cmd1 cmd2 ...]
or: setup.py --help-commands
or: setup.py cmd --help
error: no commands supplied

Can you try doing this using easy_setup?


TypeError: server.closeAllConnections is not a function after authorization.

Describe The Bug:
Now that the applications issue on Daikin is resolved,
it is still not working to authorize.
To Reproduce:
Create an app on Daikin, provide info in the plugin.
The authorization URL will work.
After approving, you're redirected to the local Thank you page. (Authorization complete).
But in the logs, the plugin crashes and restarts.
Logs:
Daikin Cloud BridgeErrorTypeError: server.closeAllConnections is not a function
at cleanup (/var/lib/hoobs/daikincloudbridge/node_modules/daikin-controller-cloud/src/onecta/oidc-callback-server.ts:80:24)
at onAuthCode (/var/lib/hoobs/daikincloudbridge/node_modules/daikin-controller-cloud/src/onecta/oidc-callback-server.ts:92:17)
at ServerResponse. (/var/lib/hoobs/daikincloudbridge/node_modules/daikin-controller-cloud/src/onecta/oidc-callback-server.ts:102:46)
at Object.onceWrapper (node:events:627:28)
at ServerResponse.emit (node:events:525:35)
at onFinish (node:_http_outgoing:950:10)
at callback (node:internal/streams/writable:554:21)
at afterWrite (node:internal/streams/writable:499:5)
at onwrite (node:internal/streams/writable:479:7)
at WriteWrap.onWriteComplete [as oncomplete] (node:internal/stream_base_commons:106:10)

What version of node are you using @Tangheta? You must use at least 18.15.0 or up. It looks like you are using a lower version that doesn't yet support closeAllConnections .


Fediverse compatibility, object resolution, inbox forwarding

Combined a few items in this PR that would otherwise have generated merge conflicts:
authentication requirements for compatibility with mastodon >=3.2.1

add & sign digest header on POST
optionally sign GETs

Pleroma compatibility

remove unnecessary Accept header on POSTs

fixes #5
Recursive object resolution

follows links in incoming activities to ensure the full conversation thread is available

Forwarding from inbox

https://www.w3.org/TR/activitypub/#inbox-forwarding
Helps ensure complete threads are available on different servers

@quinn-madson gonna merge this in to avoid more conflicts with current work


XmlComments fail to generate comments when models used from external class library

just got swagger generated and i'm pumped! love this project! but i noticed an issue that i'm hoping to find the answer to but the more i search for it there's no luck, so if anyone has any insight on this i'd love to know what i'm lacking right now.
i'm keeping the models in a business layer and just including them in the controller through a using reference. the main issue is that the summary xmlcomments aren't being recognized in the generated swagger.
so here's the commented code:

and the generated swagger:

this confused me. looking into it i recognized that swashbuckle was included in the api project within the solution, but the business project layer does not have it included (this is my prime suspicion for this issue however adding swashbuckle to business layer is an issue as that would create xml file conflictions) so i went to the models folder of api: models->add->existing item->and navigated to the models from my isbnbusiness project: (sorry for long verticle picture)

once i did so i changed the namespace and set this up within the controller:

so its not the prettiest (possibly a buggy patch waiting to burst) solution but when i did this the swagger generated this:

so a fix? maybe. but i'd really rather only be using isbnbusiness' and not the api's models
how can i fix this so that swashbuckle will recognize the comments of the models of the business layer project and generate the
comments i need in swagger?

There is a very simple solution this.
You need to generate the xmldocumentation for the project where the models reside
in project properties/Build

Then in swagger.config create a static string that returns the xml file location
protected static string GetXmlCommentsForDTO()
        {
            return<EMAIL_ADDRESS>System.AppDomain.CurrentDomain.BaseDirectory);
        }

And then in the swaggerconfiguration c.IncludeXmlComments(GetXmlCommentsForDTO()); and you are all set :)

I think this can be closed

@domaindrivendev thank you, I just want to add that we can get comments from multiple files in swashbuckle
c.IncludeXmlComments(GetXmlCommentsPath());
c.IncludeXmlComments(GetXmlCommentsPathCommon());'

private static string GetXmlCommentsPath()
{
   return AppDomain.CurrentDomain.BaseDirectory + @"bin\ReportingAPI.xml";
}

private static string GetXmlCommentsPathCommon()
{
	return AppDomain.CurrentDomain.BaseDirectory + @"bin\ReportingAPI.Common.xml";
}


Add support for GKE Workload Identity

Signed-off-by: Joshua Wong<EMAIL_ADDRESS>This closes #1657
Instead of solely relying on the private key for creating new GCP API clients, gcp/object_store.go and gcp/volume_snapshotter.go were changed to use the GCP Default Credentials, since that automatically uses the compute engine tokens if the GCP Service Account key file isn't available.
In order to continue using signed urls, the GCP ObjectStore uses the SignBlob API with the service account name passed in via the config.
Also, I added an install option to specify specific ServiceAccount annotations, since the Kubernetes Service Account needs a certain annotation in order to masquerade as the GCP Service Account.
Steps to test this:

Create a cluster with workload identity enabled
Create the GSA with the permissions that velero needs in order to function
Grant the GSA iam.serviceAccountTokenCreator role to itself
Add the IAM policy binding: gcloud iam service-accounts add-iam-policy-binding
--role roles/iam.workloadIdentityUser
--member "serviceAccount:[PROJECT_ID].svc.id.goog[velero/velero]"
<EMAIL_ADDRESS>Note: You can still add the policy binding before the KSA is created
Install velero: velero install --provider gcp --no-secret --sa-annotations<EMAIL_ADDRESS>--backup-location-config<EMAIL_ADDRESS>

thanks for the PR @JWong101 and apologies for the delay, we're a little backed up at the moment. Will review soon!

@victortrac @salrashid123 would love to have some additional eyes on this if you've got time!

just a comment on the IAM permissions..if you grant roles/iam.serviceAccountTokenCreator that gives the service account that the WI Identity runs as a number of overlapping capabilities.   For example, the WI enabled system can now execute the capabilities below (the getAccessToken() is redundant since you already have it for the service account to even start the flow (as provided by roles/iam.workloadIdentityUser).   If what you just want is to signBlob() an IAM role with just htat permission should work
unfortunately the GCP only has one canned IAM role that covers all of it
roles/iam.serviceAccountTokenCreator
    iam.serviceAccounts.get
    iam.serviceAccounts.getAccessToken
    iam.serviceAccounts.implicitDelegation
    iam.serviceAccounts.list
    iam.serviceAccounts.signBlob
    iam.serviceAccounts.signJwt
    resourcemanager.projects.get
    resourcemanager.projects.list

so for customer who whated to very tightly limit its access, they'd currently need to define a custom role with just iam.serviceAccounts.signBlob permission
for reference,
roles/iam.workloadIdentityUser
    iam.serviceAccounts.get
    iam.serviceAccounts.getAccessToken
    iam.serviceAccounts.list

Added a couple more comments from testing, but this is looking almost ready! It would be great to  add some documentation about this as well -- site/docs/master/gcp-config.md and site/docs/master/api-types/backupstoragelocation.md would be good places to start.
You can take a look at https://velero.io/docs/v1.1.0/aws-config/ and the bottom section on installing using kube2iam as a reference for how alternate installation methods are documented.

ref. https://github.com/heptio/velero/pull/1810#issuecomment-528553593 -- I tested by just adding iam.serviceAccounts.signBlob to the custom Velero server role defined here, and that seemed to do the trick.

@JWong101 just checking to see if you wanted to continue moving this forward - if not, I can take it over and give you credit for the commits made.

Yeah, sorry, I've just been busy w/ schoolwork + interviews. I should be able to finish the changes by Friday or Saturday.

Great, thanks for the updates @JWong101!


Implement GPU cluster support

Checked in the first executable multi-lusters GPU simulation. Currently inter-clusters spikes are not supported. Here is a preliminary results:

Run simulations of 10,000 neurons, 10s * 2 epochs.
Master - 76s
1 cluster - 89s
2 clusters - 75s
4 clusters - 78s

Run simulations of 1000 izh neurons, 1s.

As number of synapses/neuron increases, summation kernel occupies higher ratio of execution time.
As number of clusters increases, overhead also increases.
Initialization/setup time is almost constant.

Implemented performance improvement code where eliminating inter-clusters data transfer during synaptic delay period (level 1). This way also could eliminate barrier-synchronization during the period.
In addition implemented parallel reduction method in summation kernel (level 2).
Run simulations of 1,000 neurons, 999 synapses/neuron, 1s * 1 epoch.

Version
1 cluster
2 clusters
4 clusters

master
33
N/A
N/A

No optimization
36
37
38

Optimized inter-clusters data transfer (Level 1)
35
34
33

Level 1 + parallel reduction (level 2)
37
29
25

Run simulations of 10,000 neurons, 46.3 synapses/neuron, 100s * 2 epochs.

Version
1 cluster
2 clusters
4 clusters

master
519
N/A
N/A

No optimization
958
1020
1082

Optimized inter-clusters data transfer (Level 1)
619
455
377

Level 1 + parallel reduction (level 2)
961
668
525

These are very interesting results. Clearly, a big win for "synapse bound" simulations, like the first one, while it introduces extra overhead in the second case. Maybe we need to have two versions of the summation kernel and choose which one to use (each epoch?) based on the (presumably average) number of synapses per neuron...
Since this is likely to be an extensive discussion, and since this is closed and we have a "performance tuning" issue ( #185 ), let's move further discussion there (and I'll put a comment in there linking back to this issue).

Also, link to issue #204


Cannot start 2 different Dev sessions on Podman due to conflicting host ports

/kind bug
What versions of software are you using?

In one terminal:
$ mkdir /tmp/nodejs1 && cd /tmp/nodejs1
$ odo init --name my-nodejs --devfile nodejs --starter nodejs-starter
$ ODO_EXPERIMENTAL_MODE=t odo dev --debug --platform=podman

Wait until the Dev session is started.
In a separate terminal:
$ mkdir /tmp/nodejs2 && cd /tmp/nodejs2
$ odo init --name my-nodejs-2 --devfile nodejs --starter nodejs-starter
$ ODO_EXPERIMENTAL_MODE=t odo dev --debug --platform=podman

Actual behavior
The dev session for my-nodejs-2 (second terminal) wouldn't start, because we are trying to bind to port 20001, which is already used by the dev session started by my-nodejs (first terminal).
The error is explicit: [... rootlessport listen tcp <IP_ADDRESS>:20001: bind: address already in use]
$ ODO_EXPERIMENTAL_MODE=t odo dev --debug --platform=podman
============================================================================
⚠ Experimental mode enabled. Use at your own risk.
More details on https://odo.dev/docs/user-guides/advanced/experimental-mode
============================================================================

  __
 /  \__     Developing using the "my-nodejs-2" Devfile
 \__/  \    Platform: podman
 /  \__/    odo version: v3.7.0
 \__/

↪ Running on podman in Dev mode
 ✗  Deploying pod [6s]
Cleaning up resources
 ✗  exit status 125:
Complete Podman output:
Trying to pull registry.access.redhat.com/ubi8/nodejs-16:latest...
Getting image source signatures
Checking if image destination supports signatures
Copying blob sha256:f6020ef1f0c813cb6e68b95ffe2ba1eb76a61b5083e624cb8a72a51626191bf7
Copying blob sha256:1eb1cc491a1bd8e2827ef1c90d2253d5aca4348cc5642ec2206c85dfd20a22e1
Copying blob sha256:ea0a20a2c44861ba5e4cd80a32868b6f8265cd3ee81310d4d493a1b50d1c0d8c
Copying config sha256:bfc987a83b9e6ffa90480235b015d1eb969bb78adec0e78714140787b091efaf
Writing manifest to image destination
Storing signatures
[starting container c2b8f4c5cef80875ea6e4987bbb81e21cdceaf3894a382c5f1178a1fc2c0c337: rootlessport listen tcp <IP_ADDRESS>:20001: bind: address already in use]
[starting container c2b8f4c5cef80875ea6e4987bbb81e21cdceaf3894a382c5f1178a1fc2c0c337: rootlessport listen tcp <IP_ADDRESS>:20001: bind: address already in use starting container 5c71090911cb59380f68223bf1ef033b5edbff0543d53b5c4a736e3c86465810: a dependency of container 5c71090911cb59380f68223bf1ef033b5edbff0543d53b5c4a736e3c86465810 failed to start: container state improper]
Pod:
f673cb2681aa98a0f976f50f4acb6e08f89342f698004654d45bda5742270f84
Container:
5c71090911cb59380f68223bf1ef033b5edbff0543d53b5c4a736e3c86465810

starting container c2b8f4c5cef80875ea6e4987bbb81e21cdceaf3894a382c5f1178a1fc2c0c337: rootlessport listen tcp <IP_ADDRESS>:20001: bind: address already in use
starting container 5c71090911cb59380f68223bf1ef033b5edbff0543d53b5c4a736e3c86465810: a dependency of container 5c71090911cb59380f68223bf1ef033b5edbff0543d53b5c4a736e3c86465810 failed to start: container state improper

Error: failed to start 2 containers

Expected behavior
The dev session started in the second tab should listen on different ports not being used. So it looks like there is an issue with the way we detect if a port is used or not (util.IsPortFree(int)).
Any logs, error output, etc?
Initially, I suspected the kernel issue we already hit a few weeks ago. But running https://go.dev/play/p/ijrIFcB3ayo?v=goprev works as expected. And this is reportedly fixed in recent kernels. So this is not a kernel issue to me.

NOTE: I quickly checked if it works with Kubernetes, since both Kubernetes and Podman implementations of odo dev use the same util.IsPortFree(int) function to determine if a port is available. And port-forwarding on Kubernetes works as expected by binding to non-conflicting ports. So maybe there is something different in how Podman handles hostPort?

This works on podman 3.4.7 and Kernel version 6.0.12-100.
$ uname -a
Linux fedora 6.0.12-100.fc35.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Dec 8 16:53:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

If a port is open by podman, it is not detected (by either odo dev on podman or cluster)

Need research

I reported this issue to the Podman folks: https://github.com/containers/podman/issues/17719
And the conclusion is that this issue is (again) a regression in the kernel that allows binding twice on the same port under some circumstances.
It has been reported to the kernel [1], and a patch [2] is underway.
Meanwhile, I think a workaround for us could be to explicitly set hostIP in the Pod spec to <IP_ADDRESS>, or, better, try to detect used ports bound to <IP_ADDRESS> (and not only <IP_ADDRESS>).
[1]<EMAIL_ADDRESS>[2]<EMAIL_ADDRESS>


WIP: updated robot implementation

I updated the interface definition for the device type "Robot", adressing #24. My goal was to implement all of the device unspecific behaviour in one place i.e. in functions that are defined on the abstract Robot type ("interface functions"), while all device specific details are "hidden" from the user in unexported, raw functions (corresponding names, prefixed with underscore, "device functions"). These functions do not have the security and argument checks, which the user-functions have and should only be called directly if there is no other way. This has the advantage that any convenience functions (default units, default speeds, Varargs instead of vector etc.) as well as all checks for the safety of coordinates just need to be implemented once for all robots. The device functions can then assume that their arguments are all valid and safe.
The core of the robot interface is a state machine that defines different states with functions to procede between the states. The different states are shown schematically in this graphic. The interface functions check for the state of the robot and will error if the function can not be called in the current state (e.g. moveAbs in state DISABLED). The interface functions will also handle the state transitions so that the device functions do not need to interact with the state of the robot.
As this is still WIP, some points that are still on my list to implement are:

[x] implement new interface for the Isel robot
[ ] test new interface for the Isel robot
[ ] implement new interface for the Bruker robot
[ ] clean up or reimplement robot safety checks
[ ] improve the error handling (currently mix of @error, error() and custom exceptions)
[ ] implement device tests on hardware

Some additional features that could be implemented

[ ] option to include positions with names (equivalent to moveParkPos() and moveCenterPos() of old interface)
[ ] convenience functions with default units (e.g. mm)
[ ] implement a forced/emergency movement stop (might not be necessary, if it is done in hardware)

I am open to discuss the design of the interface and am happy to take hints on how to improve it. Also please tell me if I forgot any potential use cases or features that would be nice to have.

I am currently moving performTour! into the protocol setup and noticed that there is currently no way to check, whether the robot has a brake which can be set with setBrake. Should we have a function hasBrake that must be implemented by all robots?

Actually, I don't think that we really use that. So, I would be ok to first leave that out and look later if we miss it. For the system function calibration, we seem to not use setBrake.


Using react magic's htmltojsx to do the heavy lifting of svg -> jsx.

A few notes:

separated out a few function files. This should make adding testing easier
separated out a language file. This should make it easier to add multiple languages (if thats a thing), also keeps all "content"-ish stuff in one spot
swapped minimist for yargs as better support for dashed booleans
generateComponent - the split/join line is to keep indenting consistent when using template strings
removeStyle function - htmltojsx comes with jsdom, so using jsdom to manipulate attributes (instead of manually parsing the DOM - which would have been tricky, esp with single v double quotes, etc)
jsDOM is also used to add width/height attributes back in (if not already present). The only catch, as noted by the comments is jsdom and htmltojsx will attempt to quote any attributes - so a minimal amount of regex is used to strip the quotes (this is the only direct DOM manipulation done now, which means easier to maintain (imo)).

Tested on n4.6.

At a glance, this looks great. Will go over the code and manually test tonight.


Allow for browserslist environment variables

Browserslist allows for setting browserslist config using environment variables, but CRA still prompts for setting browserslist config when it is already configured for the environment.
For example, running this currently results in CRA improperly detecting that browserslist is not configured, even though it is.
BROWSERSLIST="> 5%" npm run build

It looks like the build is now passing for other MRs, can someone please re-run CI on this MR?

It looks like the build is now passing for other MRs, can someone please re-run CI on this MR?

Never mind, I just pushed an amended commit.

@GreenGremlin We've had some problems with out CR, sorry that you had to push to get your PR to pass ;)

This looks good, can you share the documentation on this? I couldn't find it on their repo.

Unfortunately, just like findConfig there doesn't appear to be documentation on loadConfig. You can see from the loadConfig implementation that, unlike findConfig which just returns the path to the config, it returns the actual config. The primary difference here being that it also checks process.env.BROWSERSLIST and process.env.BROWSERSLIST_CONFIG, which findConfig doesn't account for.

It's interesting that we're setting this in our e2e tests. I imagine it must not be doing anything?
https://github.com/facebook/create-react-app/blob/ac93f310bf73461684dc1351eacca62533470b7c/tasks/e2e-kitchensink.sh#L107

It's interesting that we're setting this in our e2e tests. I imagine it must not be doing anything?
https://github.com/facebook/create-react-app/blob/ac93f310bf73461684dc1351eacca62533470b7c/tasks/e2e-kitchensink.sh#L107

The environment variables work for everything but the check for browserslist config that determines wether we should prompt to add it. Also, if the e2e tests are not run interactively, we may just skip the prompt entirely.

Thanks @GreenGremlin!


2.19.0 is very slow

paket install is about 10 times slower than 2.17.0

Second run was as fast as 2.17. Wierd.

Mhm.
You can't share your dependencies file, can you?
/cc @mrinaldi

Sounds like caching

But nothing was changed.

redirects: on
framework: net45, net451, net452, net46
source https://www.nuget.org/api/v2

nuget AlphaFS
nuget Antlr
nuget Argu
nuget axmlprinter
nuget bootstrap 3.3.1
nuget bootstrap.TypeScript.DefinitelyTyped
nuget BouncyCastle 1.7.0
nuget Castle.Core
nuget Castle.FactorySupportFacility
nuget Castle.Windsor
nuget Common.Logging
nuget Common.Logging.Core
nuget DogStatsD-CSharp-Client 2.1.0
nuget DotNetZip 1.9.3
nuget EasyNetQ.Management.Client
nuget Elasticsearch.Net
nuget ExtCore
nuget FAKE
nuget Fizzler
nuget Fizzler.Systems.HtmlAgilityPack
nuget FontAwesome
nuget Foq
nuget FParsec
nuget FsCheck
nuget FsCheck.NUnit
nuget FSharp.Core <IP_ADDRESS>
nuget FSharp.Collections.ParallelSeq
nuget FSharp.Configuration
nuget FSharp.Control.AsyncSeq
nuget FSharp.Data
nuget FSharp.Data.SqlClient
nuget FSharp.Management
nuget FSharp.Text.RegexProvider
nuget FSharpx.Async
nuget FSharpx.Collections
nuget FSharpx.Extras
nuget FsPickler 1.2.21
nuget FsPickler.Json 1.2.21
nuget FsUnit
nuget FsWebAddRegistryEntries <IP_ADDRESS>
nuget fszmq
nuget Hopac
nuget Hopac.Extras
nuget HtmlAgilityPack 1.4.6
nuget Http.fs
nuget jquery.TypeScript.DefinitelyTyped 1.6.0
nuget knockout.TypeScript.DefinitelyTyped 0.6.7
nuget knockoutjs 3.2.0
nuget Microsoft.AspNet.Mvc 5.2.2
nuget Microsoft.AspNet.Web.Optimization 1.1.3
nuget Microsoft.AspNet.WebApi 5.0.0
nuget Microsoft.Data.OData 5.6.3
nuget Microsoft.SqlServer.Types
nuget Moment.js 2.8.4
nuget moment.TypeScript.DefinitelyTyped 0.9.7
nuget mongocsharpdriver
nuget Moq
nuget MSBuild.Extension.Pack 1.3.0
nuget MSDN.FSharpChart.dll
nuget NEST
nuget Newtonsoft.Json 7.0.1
nuget NHibernate
nuget NLog 4.0.1
nuget NuGet.CommandLine 2.8.5
nuget NUnit 2.6.3
nuget NUnit.Runners 2.6.3
nuget Paket
nuget PowerShellTypeProvider
nuget protobuf-net <IP_ADDRESS>0
nuget Quartz
nuget RabbitMQ.Client 3.4.3
nuget RhinoMocks
nuget rickshaw 1.4.6
nuget rickshaw.TypeScript.DefinitelyTyped 0.0.2
nuget Selenium.WebDriver
nuget SevenZipSharp
nuget SQLProvider
nuget StackExchange.Redis
nuget Strathweb.CacheOutput.WebApi2 0.6
nuget Suave 0.32
nuget TFS.Client 11.0.0
nuget underscore.js 1.7.0
nuget underscore.TypeScript.DefinitelyTyped 0.4.9
nuget Unquote
nuget WindowsAzure.Storage
nuget ZetaLongPaths
http http://hg.mozilla.org/mozilla-central/raw-file/default/security/certverifier/ExtendedValidation.cpp

yeah. i guess the following happened:

in 2.17 everything was cached ==> relative fast updates
in 2.18/2.19 we changed the evaluation strategy a bit. Now paket looks at different versions than before to find the resolution. That means it looks at different part of the search tree. Now it needs to ask nuget about details for these versions.


[BUG] dbv cannot use mysql driver 8

Steps to reproduce the behavior (Required)

dbv version:10.0.27  use mysql jdbc dirver version: 8.0.33 8.0.11 8.0.22 8.0.19
SELECT  xxx from xxx

Expected behavior (Required)
Normal return results
Real behavior (Required)

StarRocks version (Required)
3.2-rc1

I simply tested it, and it seems that it is due to a long period of non-connection or fe restart and the connection failed. As long as the user clicks reconnect again, it can be used normally.
Are you still unable to connect after clicking reconnect?

@Astralidea Yes, I still can’t connect after clicking Reconnect.

Execute sql once and a reconnection window pops up.

Is it convenient to add WeChat to view remotely?

WeChat ID has been sent to your email（163）。

hi，@nmgliangwei I used a new driver to reproduce your problem. It was because I used the default driver version 5 that it did not reproduce. Let me see the reason first.

@Astralidea  Okay, 5.1.x In some environments, it may be impossible to return for a long time. Manually adding limit can return normally.   if necessary, we can reproduce remotely via weichat.

We have found out the reason for this problem, which is caused by the substandard support of COM_STMT_PREPARE. We will submit a PR later to fix this problem.


Update mamba pin

mamba pin is >=0.19,<0.20, but mamba is now at 0.21.
@wolfv, is there a new release on the way that supports mamba 0.21?

yes, working on that new release :)

Done. Hopefully it works :)