bug: Creating autocmd based on LazyNvim's User Events generates unexpected event error

Did you check docs and existing issues?

[X] I have read all the lazy.nvim docs
[X] I have searched the existing issues of lazy.nvim
[X] I have searched the existing issues of plugins related to this issue

Neovim version (nvim -v)
NVIM v0.10.0-dev-c88bb65
Operating system/version
<IP_ADDRESS>-microsoft-standard-WSL2
Describe the bug
Creating autocmd based on LazyNvim's User Events generates unexpected event error.
I already tried with standard events like BufReadPre and it works.
Steps To Reproduce
nvim -u repro.lua
Expected Behavior
There shouldn't be any error
Repro
local lazypath = vim.fn.stdpath('data') .. '/lazy/lazy.nvim'
if not vim.loop.fs_stat(lazypath) then
    vim.fn.system({
        'git',
        'clone',
        '--filter=blob:none',
        '--single-branch',
        'https://github.com/folke/lazy.nvim.git',
        lazypath,
    })
end
vim.opt.runtimepath:prepend(lazypath)

require('lazy').setup({}, {
    root = vim.fn.stdpath('data') .. '/lazy', -- directory where plugins will be installed
    defaults = {
        lazy = false, -- should plugins be lazy-loaded?
        version = nil,
        -- version = "*", -- enable this to try installing the latest stable versions of plugins
    },
    lockfile = vim.fn.stdpath('config') .. '/lazy-lock.json', -- lockfile generated after running update.
    concurrency = nil, ---@type number limit the maximum amount of concurrent tasks
    git = {
        -- defaults for the `Lazy log` command
        -- log = { "-10" }, -- show the last 10 commits
        log = { '--since=3 days ago' }, -- show commits from the last 3 days
        timeout = 120, -- kill processes that take more than 2 minutes
        url_format = 'https://github.com/%s.git',
    },
    dev = {
        -- directory where you store your local plugin projects
        path = '~/projects',
        ---@type string[] plugins that match these patterns will use your local versions instead of being fetched from GitHub
        patterns = {}, -- For example {"folke"}
    },
    install = {
        -- install missing plugins on startup. This doesn't increase startup time.
        missing = false,
        -- try to load one of these colorschemes when starting an installation during startup
        colorscheme = { 'kanagawa' },
    },
    ui = {
        -- a number <1 is a percentage., >1 is a fixed size
        size = { width = 0.8, height = 0.8 },
        -- The border to use for the UI window. Accepts same border values as |nvim_open_win()|.
        border = 'none',
        icons = {
            cmd = ' ',
            config = '',
            event = '',
            ft = ' ',
            init = ' ',
            keys = ' ',
            plugin = ' ',
            runtime = ' ',
            source = ' ',
            start = '',
            task = '✔ ',
        },
        throttle = 20, -- how frequently should the ui process render events
    },
    checker = {
        -- automatically check for plugin updates
        enabled = false,
        concurrency = nil, ---@type number? set to 1 to check for updates very slowly
        notify = true, -- get a notification when new updates are found
        frequency = 3600, -- check for updates every hour
    },
    change_detection = {
        -- automatically check for config file changes and reload the ui
        enabled = true,
        notify = true, -- get a notification when changes are found
    },
    performance = {
        cache = {
            enabled = true,
            path = vim.fn.stdpath('state') .. '/lazy/cache',
            -- Once one of the following events triggers, caching will be disabled.
            -- To cache all modules, set this to `{}`, but that is not recommended.
            -- The default is to disable on:
            --  * VimEnter: not useful to cache anything else beyond startup
            --  * BufReadPre: this will be triggered early when opening a file from the command line directly
            disable_events = { 'VimEnter', 'BufReadPre' },
        },
        reset_packpath = true, -- reset the package path to improve startup time
        rtp = {
            reset = true, -- reset the runtime path to $VIMRUNTIME and your config directory
            ---@type string[]
            paths = {}, -- add any custom paths here that you want to indluce in the rtp
            ---@type string[] list any plugins you want to disable here
            disabled_plugins = {
                'gzip',
                'matchit',
                'matchparen',
                'tarPlugin',
                'tohtml',
                'tutor',
                'zipPlugin',
            },
        },
    },
    -- lazy can generate helptags from the headings in markdown readme files,
    -- so :help works even for plugins that don't have vim docs.
    -- when the readme opens with :help it will be correctly displayed as markdown
    readme = {
        root = vim.fn.stdpath('state') .. '/lazy/readme',
        files = { 'README.md' },
        -- only generate markdown helptags for plugins that dont have docs
        skip_if_doc_exists = true,
    },
})

vim.api.nvim_create_autocmd({ 'LazyInstall', 'LazyUpdate' }, {
    group = vim.api.nvim_create_augroup('BumpNeoVim', {
        clear = true,
    }),
    callback = function(args)
        print('hi')
        local version = vim.version()
        local build = version.build
        local config = vim.fn.stdpath('config')
        local version_file = config .. '/version'
        vim.fn.writefile({ build }, version_file, 's')
    end,
})

Hello @c3n21,
This discussion could provide useful information.
Best regards!

Hello @c3n21,
This discussion could provide useful information.
The type of the event should be User.
Best regards!

I missed that discussion. Thanks!


ffmpeg won't build with vulkan present

This is admittedly a problem that won't affect 99% of users since Vulkan isn't something widely packaged on KISS, but it is available via sewn's gkiss-multilib repo.
I found a thread here that describes the issue where they link this patch which deletes the offending lines. In the thread, they clarify that these features aren't yet used within ffmpeg (as of 25 Dec 2022) and that doing a patch to change the names to the proper ones seems like a bad idea from their POV.
I've tried the patch myself and can confirm it works; if you'd be interested in me adding it here then I'd be happy to make a PR (and if not, I understand why). It's probably the case that some future version of ffmpeg will start to depend on these lines and get the identifiers' names right, at which point the patch could be removed.
Another much simpler option would be to just disable Vulkan support outright by just adding --disable-vulkan to the build config, which is what it seems sewn did. Then, likewise, we could just remove this flag when ffmpeg's Vulkan support is more mature.

Vulkan is not handled by kiss-xorg, and neither is there any Vulkan support on most applications. Why is the issue being made here? The only time i expected Vulkan working is when i was trying to run SuperTuxKart, as it ran with the more inferior OpenGL.
Who knows, maybe Vulkan will one time be pushed here and maintained by me???

Why is the issue being made here?

Because it's an issue with ffmpeg, not with any other package. I mean, doing an override is possible (and is what I am doing, evidently, so this isn't a showstopper by any means) but it seems "nicer" to just have one package maintained that works for everyone. If practically no-one uses vulkan, and those who do use vulkan need it disabled on ffmpeg, then I think adding the --disable-vulkan option has no potential downsides.
OTOH because it's such a minor issue it's also perfectly fair to say it's not worth fixing and just drop the issue. I don't mind either way but just thought I'd bring this to light to attempt to reduce duplication of work.

I'll close this, as a solution through #128 will work in the future (somewhere in April, most likely)


bug/image processing issues

What does this implement/fix? Explain your changes.
Fix image processing issues reported by @Piasy
Any relevant logs, error output, etc?
...
Any other comments?
...
Where has this been tested?

Devices/Simulators:
Google Pixel 4

OS Version:
Android 11

@Piasy could you check if your reported issues here are finally solved with this PR?
If so, please review the code.

After a quick test, seems only this one is fixed:

when take 2 pictures, rotate the second picture 4 times, which makes it to the original orientation, then crop it, the picture isn't shown in crop screen

this one has a new issue:

when take a picture, rotate it, then crop it, the preview isn't rotated in crop screen

I can't adjust the left/right edge of the crop area.
Please check it when you have time @Gnzlt .

in crop screen, user can set a non-rectangle crop area, but the result image is rectangle, which will stretch the content, is it designed behavior?
The cropping implies a perspective correction based on OpenCV so it will make adjustments every time you decide a new area, it's expected.
the picture isn't displayed in center when discard one picture, please check this screen recording,
This should not happen anymore
it always scroll from the first picture to the last one after taking new picture, please check this screen recording,

in crop screen, user can set a non-rectangle crop area, but the result image is rectangle, which will stretch the content, is it designed behavior?

The cropping implies a perspective correction based on OpenCV so it will make adjustments every time you decide a new area, it's expected.

the picture isn't displayed in center when discard one picture, please check this screen recording,

This should not happen anymore

it always scroll from the first picture to the last one after taking new picture, please check this screen recording,

This is the expected behavior

when take a picture, rotate it, then crop it, the preview isn't rotated in crop screen

This should not happen anymore

I can't adjust the left/right edge of the crop area.
Working on it

@Gnzlt told me the changes are ready. @Piasy please could you finish your review? Thanks.

Hi I test with com.github.meganz:AndroidDocumentScanner:35f38e2, and this issue is still there, please check them when you have time.

the picture isn't displayed in center when discard one picture, please check this screen recording, https://mega.nz/file/H94GBCxZ#uRjfEmrvWy074ETaWl8Sj5oX-KOcFS5px2n0qclUvdU

All other issues are resolved, except https://jira.developers.mega.co.nz/browse/AND-12535, which shouldn't block this PR now.
Code changes look good, but I just find out it still use Glide, could you please replace it with Fresco? I don't agree with Javier on this issue:

I suppose that @Gnzlt uses Glide because is the one originally used in the library (maybe also because could be better for this scenario). As this is a separate project from the app, in principle I don't see a problem to use Glide instead Fresco here, the only one thing we have to take into account is use only one library for image processing in the project.

At first, the original library doesn't use Glide, secondly, if we use Glide at this project, then Glide will also be included into our final MEGA app, which will increase APK size.
But if you plan to replace Glide with Fresco in another separate PR, I think it's fine.

You are right @Piasy , we should try to use Fresco here as well like in whole app project to use only one image procesing library and don't increase the APK size much more.

As mentioned on the original review, my first plan was to use Fresco but I ran into some issues that I needed to spend more time on. Do you guys think I should tackle those issues now? Or instead doing the migration afterwards to unblock this feature?

Initially I planned to use Fresco, and I actually migrated the calls to Fresco because of that same reason, trying to avoid having multiple libraries for the same purpose. But while I was getting into more complex tasks where it required bitmap rotation or grayscale conversion, I ended up having some OOMs. At that point I decided to migrate back to Glide since I didn't have those issues. In any case this could be change in the future since I didn't spend that much time trying to solve those issues with Fresco.

Please make a new try to see if you achieve migrate to Fresco avoiding those issues you mentioned. It is also important don't increase the APK size much more than strictly needed.
You can create a new branch from this for that try, so if it is finally unsuccesfull we could easy discard it.

Fresco migration has been merged and page offset has been fixed. This is ready for review @Piasy

the picture isn't displayed in center when discard one picture, please check this screen recording, https://mega.nz/file/H94GBCxZ#uRjfEmrvWy074ETaWl8Sj5oX-KOcFS5px2n0qclUvdU

Hi @Gnzlt , this issue still happens on my Huawei Honor V30 Android 10 and Nexus 5X Android 8.1, does it work as expected on your device? BTW, I test it inside MEGA application, do you test it in the demo app or this repo?

I test it inside MEGA application, do you test it in the demo app or this repo?
This should be fixed, and works on my Moto G5S too. If you test it inside MEGA, keep in mind that Gradle might be building it with a cached version of the repo. I would recommend you to test it on this repo. Once this is merged, I will merge develop changes and request a review on MEGA PR.

@Piasy please approve again and merge this PR.


How to escape dollar sign in replacements?

It looks like it's treated as a capture group, any way to escape it? \$ doesn't work. Sorry if I missed something from the readme.

Ok the solution was to to use $$, a ripgrep thing.


Extension not showing in sidebar

I've installed the plugin but its not showing up in my sidebar.

Extension version:
VSCode Version: 1.69.1
OS:  OSX M1

Steps to Reproduce:

Can you share the output of "GitHub Pull Requests"?

Closing - I did not realize I needed to setup the GitHub extension first


Add support for implementing different ethernet boards for esp32

Cherry pick from PR : https://github.com/project-chip/connectedhomeip/pull/26687
This PR includes changes for enabling someone to implement any type of ethernet board they want
One can override ESP32Ethernet Driver's methods to set up their own configuration of ethernet board

@PSONALl this had conflicts.


MRG: Fix epochs type in reference

3 lines!!

travis is not happy :(

@agramfort Merge or should I add a test?

thanks @jona-sassenhagen

There are three or so other cases like isinstance(inst, Epochs). I can make a PR for that later.

Coverage decreased (-3.0%) to 87.59% when pulling a0db06c4fb36629e312e03d5547046d51c8cc32b on jona-sassenhagen:patch-2 into 281a645a9db171bd6904047ba462f39a024844f0 on mne-tools:master.


all: Update credentials format

Update credentials format to match upstream KBC URI change

I tested the patch to pull image from authenticated registry and can confirm that this works successfully.
Thanks @stevenhorsman


chore(main): release 1.237.0

When this PR is merged, a new tagged release will be created with the notes below.
1.237.0 (2023-07-28)
Features

Add warning for large payloads (#620) (d616f64)
reduce jserrors wrapping and remove onerror use (#614) (e393c96)
Stop reporting ajax events going to same beacon (#609) (ca43edf)

Bug Fixes

Defining agent api methods for ts types (#613) (14d4294)
Fix potential property of undefined errors (#610) (389b5ad)
prevent invalid error stack traces (#617) (3d9f2c0)
Remove fetch keep-alive unhandled rejection (#625) (dc4fb1b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/newrelic/newrelic-browser-agent/releases/tag/v1.237.0 :sunflower:


Source generator fails under Live Unit Testing

While developing a msgpack serializer sample for this repo, I tried running Live Unit Testing under Visual Studio. It failed. The build log showed this:
15:58:32.349     3>TypeShape.Tests.FSharp -> C:\Users\andarno\source\lut\typeshape-csharp\v2\0\b\tests\TypeShape.Tests.FSharp\bin\Debug\net8.0\TypeShape.Tests.FSharp.dll
15:58:32.772     2>TypeShape -> C:\Users\andarno\source\lut\typeshape-csharp\v2\0\b\src\TypeShape\bin\Debug\net8.0\TypeShape.dll
15:58:33.416     4>TypeShape.Examples -> C:\Users\andarno\source\lut\typeshape-csharp\v2\0\b\src\TypeShape.Examples\bin\Debug\net8.0\TypeShape.Examples.dll
15:58:34.010     5>TypeShape.SourceGenerator -> C:\Users\andarno\source\lut\typeshape-csharp\v2\0\b\src\TypeShape.SourceGenerator\bin\Debug\netstandard2.0\TypeShape.SourceGenerator.dll
CSC : error CS8032: An instance of analyzer TypeShape.SourceGenerator.TypeShapeIncrementalGenerator cannot be created from C:\Users\andarno\source\lut\typeshape-csharp\v2\0\b\src\TypeShape.SourceGenerator\bin\Debug\netstandard2.0\TypeShape.SourceGenerator.dll : Exception has been thrown by the target of an invocation..

Build FAILED.

CSC : error CS8032: An instance of analyzer TypeShape.SourceGenerator.TypeShapeIncrementalGenerator cannot be created from C:\Users\andarno\source\lut\typeshape-csharp\v2\0\b\src\TypeShape.SourceGenerator\bin\Debug\netstandard2.0\TypeShape.SourceGenerator.dll : Exception has been thrown by the target of an invocation..
    0 Warning(s)
    1 Error(s)

Time Elapsed 00:00:02.42

But ordinary builds are fine.

I haven't used this feature. Is this a bug with the generator itself or an infrastructural issue with the solution?

To know that we'd actually have to see the exception that's being thrown, but unfortunately the target invocation exception is hiding it. We need to find a way to see more of the exception.

Could this have been caused by https://github.com/eiriktsarpalis/typeshape-csharp/issues/18?

No. It still repros after the fix for #18.
I can see that the csc.exe process can successfully execute your source generator. So it must be some subsequent load in another process that fails.

https://developercommunity.visualstudio.com/t/Live-Unit-Testing-fails-logs-only-an-op/10777151


Exception: Password required for user xxx when drop partition of ReplicatedMergeTree table

I hereby agree to the terms of the CLA available at: https://yandex.ru/legal/cla/?lang=en
In our cluster, we have set password for the default user name. When we use default username to drop a partition of ReplicatedMergeTree table, sometimes we got the following exception:
Code: 194. DB::Exception: Received from localhost:9000, <IP_ADDRESS>. DB::Exception: Received from host:9000, ip. DB::Exception: Password required for user default.

0. /home/clickhouse/clickhouse-current/bin/clickhouse-server(StackTrace::StackTrace()+0x16) [0x5c1e746]
1. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::readException(DB::Exception&, DB::ReadBuffer&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)+0x337) [0x5c448a7]
2. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::Connection::receiveException()+0x6f) [0x57580ef]
3. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::Connection::receiveHello()+0x153) [0x57585d3]
4. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::Connection::connect()+0x20b) [0x575ad7b]
5. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::Connection::getServerRevision()+0x1a) [0x575b4fa]
6. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::MultiplexedConnections::sendQuery(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, unsigned long, DB::ClientInfo const*, bool)+0xd5b) [0x576c57b]
7. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::RemoteBlockInputStream::sendQuery()+0x2fb) [0x49d6a3b]
8. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::copyData(DB::IBlockInputStream&, DB::IBlockOutputStream&, std::atomic<bool>*)+0x24) [0x49dce24]
9. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::StorageReplicatedMergeTree::sendRequestToLeaderReplica(std::shared_ptr<DB::IAST> const&, DB::Settings const&)+0xaad) [0x562e80d]
10. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::StorageReplicatedMergeTree::dropPartition(std::shared_ptr<DB::IAST> const&, std::shared_ptr<DB::IAST> const&, bool, DB::Context const&)+0x55) [0x562fb45]
11. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::InterpreterAlterQuery::execute()+0xeae) [0x598f45e]
12. /home/clickhouse/clickhouse-current/bin/clickhouse-server() [0x550f425]
13. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::executeQuery(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, DB::Context&, bool, DB::QueryProcessingStage::Enum)+0x73) [0x55112c3]
14. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::TCPHandler::runImpl()+0x499) [0x29b5c69]
15. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::TCPHandler::run()+0x1c) [0x29b6eac]
16. /home/clickhouse/clickhouse-current/bin/clickhouse-server(Poco::Net::TCPServerConnection::start()+0xf) [0x5d92dbf]
17. /home/clickhouse/clickhouse-current/bin/clickhouse-server(Poco::Net::TCPServerDispatcher::run()+0x166) [0x5d93186]

The same exception will occur when truncate table of ReplicatedMergeTree.
According to the exception stack, we found that the context used in method StorageReplicatedMergeTree::sendRequestToLeaderReplica  does not contain the client_info, so we can not get current_user and current_password from the context :
Connection connection(
        leader_address.host,
        leader_address.queries_port,
        leader_address.database,
        context.getClientInfo().current_user, context.getClientInfo().current_password, timeouts, "ClickHouse replica");

But the client_info actually is stored in the variable context outside the method StorageReplicatedMergeTree::sendRequestToLeaderReplica, so our solution is replacing the second parameter (called settings) with the context outside. And we test that is work.

https://github.com/yandex/ClickHouse/pull/3598
Maybe replica is different from the current server username and password.

@nicelulu
The following log is printed on the leader node:
0. /home/clickhouse/clickhouse-current/bin/clickhouse-server(StackTrace::StackTrace()+0x16) [0x5c1e746]
1. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::Exception::Exception(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, int)+0x1f) [0x29a8a1f]
2. /home/clickhouse/clickhouse-current/bin/clickhouse-server() [0x298e1e1]
3. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::SecurityManager::authorizeAndGetUser(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, Poco::Net::IPAddress const&) const+0xb6) [0x54b01b6]
4. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::Context::setUser(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, Poco::Net::SocketAddress const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)+0x66) [0x5411e66]
5. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::TCPHandler::receiveHello()+0x5c3) [0x29b3313]
6. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::TCPHandler::runImpl()+0x1af) [0x29b597f]
7. /home/clickhouse/clickhouse-current/bin/clickhouse-server(DB::TCPHandler::run()+0x1c) [0x29b6eac]
8. /home/clickhouse/clickhouse-current/bin/clickhouse-server(Poco::Net::TCPServerConnection::start()+0xf) [0x5d92dbf]
9. /home/clickhouse/clickhouse-current/bin/clickhouse-server(Poco::Net::TCPServerDispatcher::run()+0x166) [0x5d93186]
10. /home/clickhouse/clickhouse-current/bin/clickhouse-server(Poco::PooledThread::run()+0x77) [0x5ea20a7]
11. /home/clickhouse/clickhouse-current/bin/clickhouse-server(Poco::ThreadImpl::runnableEntry(void*)+0x38) [0x5e9e068]
12. /home/clickhouse/clickhouse-current/bin/clickhouse-server() [0x652acef]
13. /lib64/libpthread.so.0(+0x7dc5) [0x7fcc50703dc5]
14. /lib64/libc.so.6(clone+0x6d) [0x7fcc4ff2873d]

The leader node will use the username and password configured on the machine to check those received from the connection.
If the username and password in the connection sent by follower node are both null, we still get the the same exception.
So I think it is the follower side problem.
Maybe better solusion is needed!

This is my first submission, I wonder why the test didn't run？Is there anything wrong？

Closed in favor of https://github.com/yandex/ClickHouse/pull/3598.


Express example

Do you have an example of how you are using the Express controller in an application?
Thanks in advance.

I improved a documentation


events not firing

Hi, events are not firing for me.  Any tips on debugging this?  I tried configuring the nemLogging module to debug, but not seeing debugging, either.
I'm using ui-leaflet 1.0.0 2015-10-29
I've put a console.log on line 3364 and can see that the moveend event is getting detected.
here's what my code/markup looks like
angular.extend($scope, {
        center: {
            lat: 33.7677129,
            lng: -84.420604,
            zoom: 15
        },
        events: {
            map: {
                enable: ['layeradd','zoomstart','zoomend','drag', 'click', 'mousemove','moveend','mouseover'],
                logic: 'emit'
            }
        },
        layers: {
            baselayers: {
                osm: $scope.definedLayers.osm
            },
            overlays: {
                shapes: {
                    name: 'Shapes',
                    type: 'group',
                    visible: true
                }
            },
            paths:$scope.paths
        },
        defaults: {
            scrollWheelZoom: false
        }
    });

        var mapEvents = leafletMapEvents.getAvailableMapEvents();
        for (var k in mapEvents){
            var eventName = 'leafletDirectiveMap' + mapEvents[k];
            console.log("available event : " + eventName);
            $scope.$on(eventName, function(event){
                console.log("ok");
                $scope.eventDetected = event.name;
            });
        }

<leaflet
        id="map"
        defaults="defaults"
        class="lg_map"
        layers="layers"
        paths="paths"
        center="center"
        event-broadcast="events"
        events="events"
        height="445px" width="100%">
</leaflet>

this was resolved by adding the id of the map to the event registration.
e.g. leafletDirectiveMap.lg_map.movend
also, per the logging, I found that I had to include leafletLogger in my controller and manually set the log level.

This doesn't work for me.  I copied the code exactly and it didn't work.  Is there a better explanation on how to do this?

If your map does not have an id then you do not need it. Therefore no id would use leafletDirectiveMap.movend

https://github.com/angular-ui/ui-leaflet/blob/master/examples/0501-markers-events-add-example.html#L24
https://github.com/angular-ui/ui-leaflet/blob/master/examples/0513-markers-events-example-with-id.html#L39-L44

I'm currently having the same problem. My JS code is like this:
$scope.map = {
    events: {
        map: {
            enable: ['click'],
            logic: 'emit'
        }
    }
};
leafletLogger.currentLevel =  leafletLogger.LEVELS.debug;

console.log('leafletMapEvents', leafletMapEvents, 'available map events', leafletMapEvents.getAvailableMapEvents());
$scope.$on('leafletDirectiveMap.click', function(event, args){
    console.log(event, args);
});

And HTML:
<leaflet width="100%" height="280px" event-broadcast="map.events"></leaflet>

Checking console, I see the available map events, and when I click on the map I see leafletLogger debug log, but not the console.log of the event.
Any help is appreciated.


Arduino DUE and Serial1,2,3

Hi, thanks for super library.
I have problem with using different serial other then serial 0. On UNO si code fast and without problems. On DUE works slowly (but works). Serial1(2,3) on DUE didn't work at all. It sends nothing. I tried:
ModbusMaster node(Serial1,1);
ModbusMaster node(1,1);
Comunication not working.
I using library version 0.11.0, arduino IDE 1.6.8
Only corrections I made, is adding lines for TX enable and
MBSerial->begin(u16BaudRate, SERIAL_8E1)
Code works on UNO without any problems.

Hy, can you show me the code of the modifications of TX enable and SERIAL_8E1 ?

I found the problem. Below line:
MBSerial->begin(u16BaudRate);
i add
Serial1.begin(9600, SERIAL_8E1);
Then serial prot works with parity.
I don't understand how it works, but i'm happy.
For TX enable I just add digital write high function above line:
MBSerial->flush();

Glad it's working. Thanks. Closing issue.


More examples

I need to interpolate a SDF of say 128 x 128 x 128, as well as calculate normals (gradients).
Link to interpolate in scipy.
Could you please provide an easy-to-use example?

Hi,
The first thing is that the functions in this repo only work if the data to interpolate are defined on a regular grid (like scipy.interpolate.interpn, but not like scipy.interpolate.griddata).
If that's what you're interested in, I've just added a demo notebook. Let me know if that's the type of example you're looking for, or if you had something else in mind.
One last thing, I am not fully confident that the backward pass of grid_grad is correct. If you plan to backpropagate through it, maybe be careful, and please let me know if you get weird results.
Cheers
Yael

Hello, do you know how to pad texture like: https://www.youtube.com/watch?v=r9l8RfTvqyI , another question here: https://blender.stackexchange.com/questions/264966/inpainting-for-atlas-texture-map , I think it is related to interpolation, but I don't know how to implement it.


Test: manual launching of multiple debug processes

[ ] OS X  @jrieken
[ ] Windows @roblourens

complexity: 4
As requested in https://github.com/Microsoft/vscode/issues/14338 we now support starting multiple debug sessions by clicking on the debug start action multiple times. Have a workspace with mutiple launch configurations and verify:

You can start multiple debug sessions via debug start action (you can only do this if you try to launch different configurations)
Once you are debugging two processes a dropdown appears in the floating debug actions widget
Switching processes via this dropdown opens the appropriate stack frame in the editor and all debug actions get scoped for that process
Clicking on the stack frames in the call stack view opens those stack frames in the editor and all actions get scoped for the process of that stack frame
Each Process and Thread show their status in the call stack view

I am not really able to test this because of #16596

@jrieken makes sense, we should first fix that issue. Sorry about that

That issue is now fixed, builds should be out of the oven soon so this can be tested


Add generic issue template

@tayloramurphy @pnadolny13 We didn't have a generic bug report issue template so I figured it would be good to make one so that we can collect the right info from folks. Will this work?
@rwfeather @cjohnhanson Would love to get your thoughts on this to make sure this captures info you might need as well.
See https://meltano.slack.com/archives/C01UGBSJNG5/p1668779438979179 for context on this proposal.

@afolson to get this to work like the others, I think it needs to be a YAML file so it can render like this https://github.com/meltano/hub/blob/main/.github/ISSUE_TEMPLATE/new_tap.yml content-wise I think it looks good though!


Closing Files

First of all just wanted to say thanks for making this great library, its so helpful.
So I am using the library to zip files where the paths are passed via the URL. I have my own handler function that gets the data from the URL string, makes the template and then calls archive.ServeHTTP(w, r). But after its finished the files aren't closed, and the ServeHTTP isn't blocking so it seems there is no way to know when the request is finished. Any ideas on this would be great!

Hi @nerdbaggy ,
archive.ServeHTTP uses http.ServeContent internally, so it is blocking (it returns after the request has been handled). So if you create the template in the request handler, you should be able to close the file(s) yourself after the call to archive.ServeHTTP in your handler returns.
This example works for me https://gist.github.com/martin-sucha/b1ba6416cfbf948b1ce499aaa44c8b7f
Please let me know whether the above information was helpful.
In case archive.ServeHTTP isn't blocking then it's a bug and please let me know steps how to reproduce it, ideally with some Go source code demonstrating the issue.

This is super helpful and exactly what I needed thanks! And you are right http.ServeContent is a block call. After doing some pcaps I realized then on Firefox when the download popup appears it is still downloading the content in the background. So in my testing I just put a fmt.Println() after the ServeHTTP and noticed that before I clicked save on the download popup the Println printed, so I assumed it wasn't a blocking call. Thanks again for the help!


switch to donttest so CRAN checks don't fail when SB is down.

sbtools_1.1.8.tar.gz
Fixes #250 tar.gz is attached to be uploaded to cran. 🤞 that does the trick.

ignoring travis on this since that error is unrelated

The travis.yml over in nhdplusTools should have an example that will get rgdal working... should I port that over here?

if you are up for it, that would be great. Ideally, we'd have working CI on this repo 👍

OK -- I se a couple other easy issues in here I could pick off -- it's on my list.


Fix Aspire launch settings structure

The extra closing bracket didn't allow launch settings to be properly used for startup

Thanks for the PR!


InvalidTemplateDeployments | openai & appserviceplan | need SKU options or model modification options please

Please provide us with the following information:

This issue is for a: (mark with an x)
- [X] bug report -> please search issues before submitting
- [ ] feature request
- [ ] documentation issue or request
- [ ] regression (a behavior that used to work and stopped in a new release)

Minimal steps to reproduce

Using Github codespaces
azd auth login --use-device-code --> logged in with azure subscription, not the free one
azd env new --> "azuresearchopenaidemo"
setting .env variables in the .azure folder: (AZURE_AUTH_TENANT_ID, AZURE_CLIENT_APP_ID, AZURE_CLIENT_APP_SECRET, AZURE_ENV_NAME="azuresearchopenaidemo", AZURE_LOCATION="eastus", AZURE_SERVER_APP_ID, AZURE_SERVER_APP_SECRET, AZURE_SUBSCRIPTION_ID, AZURE_USE_AUTHENTICATION="true")
azd up

Any log messages given by the failure

ERROR: error executing step command 'provision': deployment failed: error deploying infrastructure: deploying to subscription:
Deployment Error Details:
InvalidTemplateDeployment: The template deployment 'openai' is not valid according to the validation procedure. The tracking id is 'c5aeeea6-7822-472a-a60d-1fa7fa726271'. See inner errors for details.
InsufficientQuota: This operation require 30 new capacity in quota Tokens Per Minute (thousands) - GPT-35-Turbo, which is bigger than the current available capacity 0. The current quota usage is 30 and the quota limit is 30 for quota Tokens Per Minute (thousands) - GPT-35-Turbo.
InvalidTemplateDeployment: The template deployment 'appserviceplan' is not valid according to the validation procedure. The tracking id is '3e04040e-327a-4718-9812-67262d68883a'. See inner errors for details.
ValidationForResourceFailed: Validation failed for a resource. Check 'Error.Details[0]' for more information.
SubscriptionIsOverQuotaForSku: This region has quota of 0 instances for your subscription. Try selecting different region or SKU.
TraceID: 1c1febac791efa7bf63f8a0911f913d7
Expected/desired behavior

Successful first time deployment.
I haven't been able to successfully launch the azd up command.

OS and Version?

Version used: Windows 11 Pro

Versions

azd version 1.10.3 (commit 0595f33fe948ee6df3da492567e3e7943cb9a733)
{
"azure-cli": "2.65.0",
"azure-cli-core": "2.65.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {}
}

Mention any other details that might be useful

I'm trying to deploy this demo with my enterprise's azure subscription.
I've been battling with this issue for a couple of days now, and I'd like to know if theres a way to change the "openai" model from GPT-35-Turbo to GPT-4, or if possible I'd like to know the SKU options for the openai and appservice resources.
I've found :
"appServiceSkuName": {
"value": "${AZURE_APP_SERVICE_SKU=B1}"
and
"chatGptModelName":{
"value": "${AZURE_OPENAI_CHATGPT_MODEL}"
},
"chatGptDeploymentName": {
"value": "${AZURE_OPENAI_CHATGPT_DEPLOYMENT}"
},
"chatGptDeploymentVersion":{
"value": "${AZURE_OPENAI_CHATGPT_DEPLOYMENT_VERSION}"
},
"chatGptDeploymentSkuName":{
"value": "${AZURE_OPENAI_CHATGPT_DEPLOYMENT_SKU}"
and
"gpt4vDeploymentSkuName":{
"value": "${AZURE_OPENAI_GPT4V_DEPLOYMENT_SKU}"
and
"openAiSkuName": {
"value": "S0"

But I'm unsure as to which one to set in the .env file for the errors to go away.
PLEASE HELP, I'M BEGINNING TO LOSE IT :)

Thanks! We'll be in touch soon.

I've been able to solve the 'openai' TemplateDeployment issue by setting the .env variables: AZURE_OPENAI_CHATGPT_DEPLOYMENT_VERSION="0914"
AZURE_OPENAI_CHATGPT_MODEL="gpt-35-turbo-instruct"
What I haven't been able to solve is the issue with the 'appserviceplan'. If I could get some help with this issue I'd really appreciate it.
The resources that were successfully created are these:

Thank you in advance for any insight you can provide.

Update on the appserviceplan error:
Turns out my AZURE_LOCATION had to be changed to 'eastus2' instead of 'eastus', that's it.
For some reason that's weird to me 'eastus' has more restrictions than 'eastus2'.
Hope it helps anyone out there with the same issue as me.


Add Pico4 support.

Fix #666

Thank you for the pull request!  One thing -- this change should go into the dev branch instead of master.  On dev I added the XR_BD_controller_interaction OpenXR extension, which is needed for these action paths.  It should be possible to change the base branch for the pull request here if you click "edit", hopefully there are no merge conflicts.

OK，I will close this pr and open another one.


Cannot discover tests anymore

Type: Bug

Behaviour
Expected vs. Actual
Expected: Clicking the tests icon should discover tests.
Actual: No tests have been found in this workspace yet.
Steps to reproduce:

Load a project previously having tests discovered.
Click the Tests icon.

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.11.6
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Venv
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

python /Users/johan/.vscode/extensions/ms-python.python-2023.22.0/pythonFiles/unittestadapter/discovery.py --udiscovery -v -s ./src -p test_*.py

and if I run that myself in the terminal, I get:

Error[vscode-unittest]: TEST_PORT is not set.  TEST_UUID =  None
Error: no uuid provided or parsed.
Error sending response: [Errno 61] Connection refused
Request data: Content-Length: 42
Content-Type: application/json
Request-uuid:

{"command_type": "discovery", "eot": true}

User Settings

languageServer: "Pylance"

testing
• pytestArgs: "<placeholder>"
• unittestArgs: "<placeholder>"
• unittestEnabled: true

Extension version: 2023.22.0
VS Code version: Code 1.85.0 (Universal) (af28b32d7e553898b2a91af498b1fb666fdebe0c, 2023-12-06T18:18:04.614Z)
OS version: Darwin arm64 23.1.0
Modes:

System Info

Item
Value

CPUs
Apple M1 Max (10 x 24)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
5, 5, 6

Memory (System)
64.00GB (0.05GB free)

Process Argv
. --crash-reporter-id f7b7518c-4fd8-4a0b-b95d-1c10ff2f756b

Screen Reader
no

VM
0%

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263:30899288
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
2e4cg342:30602488
89544117:30613380
2i9eh265:30646982
showlangstatbar:30737416
962ge761:30917236
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
welcomedialogc:30910334
pythonnosmt12:30797651
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixt:30902429
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
accentitlementsc:30887149
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
aa_t_chat:30882232
dsvsc019:30917259

I don't know if this is the same issue, but I get this output:
2023-12-11 09:28:38.822 [error] Error discovering pytest tests:
 Error: spawn /Users/kristiandupont/repositories/[redacted]/venv EACCES
    at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:476:16)
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -13,
  code: 'EACCES',
  syscall: 'spawn /Users/kristiandupont/repositories/[redacted]/venv',
  path: '/Users/kristiandupont/repositories/[redacted]/venv',
  spawnargs: [
    '/Users/kristiandupont/.vscode/extensions/ms-python.python-2023.22.0/pythonFiles/testing_tools/run_adapter.py',
    'discover',
    'pytest',
    '--',
    '--rootdir',
    '/Users/kristiandupont/repositories/[redacted]',
    '-s',
    '--cache-clear',
    'api/tests/'
  ]
}

This started happening right after I upgraded VSCode today. I wonder if it introduced stricter roles for subprocesses?

My issue does not seem to be related to access rights.
Some updates. I rebooted my computer, because why not, and the issue changed a bit. Now at least it tries to scan for tests, but finds 0. However, now the tests can be run individually from the editor (the run test arrow pops up at the test definition code). By the way, from the terminal I can still run the test suite using python -m unittest.

I don't know if this is the same issue, but I get this output:
2023-12-11 09:28:38.822 [error] Error discovering pytest tests:
 Error: spawn /Users/kristiandupont/repositories/[redacted]/venv EACCES
    at Process.ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:476:16)
    at processTicksAndRejections (node:internal/process/task_queues:82:21) {
  errno: -13,
  code: 'EACCES',
  syscall: 'spawn /Users/kristiandupont/repositories/[redacted]/venv',
  path: '/Users/kristiandupont/repositories/[redacted]/venv',
  spawnargs: [
    '/Users/kristiandupont/.vscode/extensions/ms-python.python-2023.22.0/pythonFiles/testing_tools/run_adapter.py',
    'discover',
    'pytest',
    '--',
    '--rootdir',
    '/Users/kristiandupont/repositories/[redacted]',
    '-s',
    '--cache-clear',
    'api/tests/'
  ]
}

This started happening right after I upgraded VSCode today. I wonder if it introduced stricter roles for subprocesses?

Have encountered the same exact issue after the latest update of vscode. It looks like the discovery command that vscode is executing is wrong. From the terminal I can see it is executing
~/source/[redacted]/.venv ~/.vscode/extensions/ms-python.python-2023.22.0/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir ~/source/[redacted] -s --cache-clear tests

However it works if I change that to the following and run it manually in my terminal:
~/source/[redacted]/.venv/bin/python ~/.vscode/extensions/ms-python.python-2023.22.0/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir ~/source/[redacted] -s --cache-clear tests

Can confirm the same behaviour that @eff917 mentions. Downgrading is the easiest way to mitigate, it seems.

I had a similar problem today. No errors in the Output console though. It just said this:
[info] Discover tests for workspace name: [...]
[info] Running discovery for pytest using the new test adapter.

But nothing happened.
To work around it, I disabled the new test adapter experiment by adding this to my VSCode user settings:
"python.experiments.optOutFrom": ["pythonTestAdapter"]

After adding this (and restarting VSCode), Python tests were discovered correctly. And, I can't explain why, but I went back and removed that setting and test discovery is now working with the new test adapter. :shrug:
vscode-python info
Version: 2023.22.0

VSCode info
Version: 1.84.2
Commit: 1a5daa3a0231a0fbba4f14db7ec463cf99d7768e
Date: 2023-11-09T10:50:47.800Z
Browser: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Code/1.84.2 Chrome/114.0.5735.289 Electron/25.9.2 Safari/537.36

This is also happening for me on Sonoma 14.2. Downgrading the Extension to 2023.20 fixed the issue

Editing python.experiments.optOutFrom doesn't work as suggested (Ubuntu 20.04 LTS, Python 3.8.13, /ms-python.python-2023.22.0) but produces the output
2023-12-12 07:37:58.774 [info] Starting Pylance language server.
2023-12-12 07:38:03.589 [info] Discover tests for workspace name: ulb-it-migration - uri: /home/hartwig/Projekte/ulb-it-migration
2023-12-12 07:38:03.633 [info] > . ./venv/bin/activate && echo 'e8b39361-0157-4923-80e1-22d70d46dee6' && python ~/.vscode/extensions/ms-python.python-2023.22.0/pythonFiles/printEnvVariables.py
2023-12-12 07:38:03.633 [info] shell: bash
2023-12-12 07:38:03.682 [info] > ./venv ~/.vscode/extensions/ms-python.python-2023.22.0/pythonFiles/testing_tools/run_adapter.py discover pytest -- --rootdir . -s --cache-clear tests
2023-12-12 07:38:03.682 [info] cwd: .
2023-12-12 07:38:03.693 [error] Error discovering pytest tests:
 [Error: spawn /home/hartwig/Projekte/ulb-it-migration/venv EACCES
	at ChildProcess._handle.onexit (node:internal/child_process:283:19)
	at onErrorNT (node:internal/child_process:476:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)] {
  errno: -13,
  code: 'EACCES',
  syscall: 'spawn /home/hartwig/Projekte/ulb-it-migration/venv',
  path: '/home/hartwig/Projekte/ulb-it-migration/venv',
  spawnargs: [
    '/home/hartwig/.vscode/extensions/ms-python.python-2023.22.0/pythonFiles/testing_tools/run_adapter.py',
    'discover',
    'pytest',
    '--',
    '--rootdir',
    '/home/hartwig/Projekte/ulb-it-migration',
    '-s',
    '--cache-clear',
    'tests'
  ]
}

Same problem as @kristiandupont here

Hello everyone, sorry for the delay and lets figure out the problem here. It seems that "python.experiments.optOutFrom": ["pythonTestAdapter"] this was a fix for some but not all so given this we have two different issues, one which is impacted by the experiment being on and one which does not depend on the experiment.
@johansmolinski with Error[vscode-unittest]: TEST_PORT is not set.  TEST_UUID =  None Error: no uuid provided or parsed. What happens is we set an env var to store the value of the UUID and PORT for testing and spin up a subprocess with these env vars to pass this information. Can you check to see if you override or clear environment variables during testing?
@kristiandupont, it seems you are running the old discovery, can you please try and run the new testing experiment. Your logs reference /pythonFiles/testing_tools/run_adapter.py which is a file only used in the old code. You could try opting into the experiment explicitly ("python.experiments.optInto": ["pythonTestAdapter"]) but everyone should have the experiment so I am not sure why you are still seeing the old code. I would check to see if you are opted out from all experiments in your workspace or user settings.
@johansmolinski, can you include logs from this run "Now at least it tries to scan for tests, but finds 0". Please set log level to trace via the command palette.
@AndreasHaure and @M3ssman same as @kristiandupont, try to switch to new experiment.
@eff917, @nmost, and @danibishop if you could provide logs that would be great, if you could also set log level to trace via the command palette.
@bricker, interesting a re-start worked, let me know if you see this behavior pop up again.
Thanks everyone for engaging on this issue!

I reproduce the same symptom and I found what mades a difference for me is how I open vscode for my project. If I open VSCode first, and then select the pre-existing virtualenv, I can make test discovery to work. However, my typical using the /usr/local/bin/code (already in my path, so i just code .) code ., the test discovery will consistent not work.
Like others, if i revert to earlier vscode python extension 2023.20.0, test discovery works normally.

Hello everyone, I am able to repro the issue and am in the process of narrowing down what commit in release 2023.22.0 is causing the issue. I will send updates in this issue.
The issue is the wrong path is put for the python executable:
expected ./.venv/bin/python -m pytest -p vscode_pytest --collect-only . (which works)
actual ./.venv -m pytest -p vscode_pytest --collect-only . (which doesn't work)

I am only able to repro with @smoy steps using code .. What are other environment configurations that people have which are leading to this bug? I am interested in where your executable you are trying to use is and how you loaded vscode to then start work on your project that might have caused the executable to not be selected correctly. Looking for an additional repro and will continue to explore the problem.

So glad I found this thread! Been struggling with this for the last few hours. As others have commented, if I launch VS Code from the terminal using code . it is unable to discover tests. But if I manually select the Python interpreter (actually, "reselect" is the correct term since it appears that VS Code is already using the correct interpreter), then test discovery works fine. Also, if I launch a new instance of VS Code, then open the project folder from the File menu, then test discovery works as expected first time. Hope that helps.

Hi everyone, we've deployed a fix to the pre-release version. Please give it a try and let us know if it helps.

@karrtikr I can confirm switching to pre-release version resolve the test discovery issue.

I am only able to repro with @smoy steps using code .. What are other environment configurations that people have which are leading to this bug? I am interested in where your executable you are trying to use is and how you loaded vscode to then start work on your project that might have caused the executable to not be selected correctly. Looking for an additional repro and will continue to explore the problem.

@eleanorjboyd I have the issues described here and I am doing what you say.  cd into my project directory, activate my virtual environment and then type code . on the command line, but the same thing happens if I start VS code from the Applications folder and pick the project directory.  In the latter case when I hit F1 and "Select Python Interpreter" I can see that it has automatically selected "./venv" rather than "./venv/bin/python" and when I update it to the latter it seems to be working.  This is with 2023.22.0.

Hi everyone, we've deployed a fix to the pre-release version. Please give it a try and let us know if it helps.

This update solved my problem.

Hi everyone, we've deployed a fix to the pre-release version. Please give it a try and let us know if it helps.

This fixed the issue for me. thanks.

@stuartmaxwell - works for me. The "Testing" explorer was first still at the "No tests were found..." at first, so I thought it didn't work but after a few seconds it loaded the tests.
thanks!

Hi everyone, we've deployed a fix to the pre-release version. Please give it a try and let us know if it helps.

this worked for me as well.
thanks.

Also confirmed, ms-python.python-2023.23.13471011 solved discovery problems.

closing as the point release contains the fix to this issue. Please comment if you are still experiencing problems even on the point release. Thanks


New version: Tar v1.9.1

Registering package: Tar
Repository: https://github.com/JuliaIO/Tar.jl
Created by: @StefanKarpinski
Version: v1.9.1
Commit: 86825ecf1e8b6f57105bf0632e93c532cee200a4
Reviewed by: @StefanKarpinski
Reference: https://github.com/JuliaIO/Tar.jl/commit/86825ecf1e8b6f57105bf0632e93c532cee200a4#commitcomment-49328000

Guess we can't make releases of new stdlibs anymore 😬

Yeah, automerge can't install them


demo: change objc true to YES

Per Apple best practices.
Risk Level: Low
Testing: CI
Docs Changes: No

Didn't see a rule for it here 🤷♂


Is there a way to make it work by searching terms in news websites?

Hi,
First. I LOVE this API :)
I have a couple of questions:

Is it possible to scrape a site based on search term?
I am trying to scrape news articles based on a a search term on a news website (e.g. CNN). Right now, I am scraping URLs using kimono and then passing those URLs to newspaper. I think it would be great to have a way to scrape search results in addition to active content.
Can it bulk process a list of URLs using pooling? I am building my own thread pools using joblib now.

Thanks.

Closing this because at the moment newspaper is more interested in improving core functionality and fixing bugs over extending features


Bump version to 5.1.0

See https://github.com/conda-forge/libignition-gazebo-feedstock/pull/11#issuecomment-871713489 .
Checklist

[x] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin, please rerender

@conda-forge-admin, please rerender

Needs libign-common 4.1


Create AndroGari.json

My portfolio

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

@AndroGari do you need any help with the changes suggested by the reviewers?

Closing Issue due to no response, @AndroGari  Please feel free to create a new PR if you wish to add your profile, Thank you!


Update extensions.py

When the uploaded file is all in chinese, such as "图片png", the extension function in this file flask uploads\extensions.py. will return empty.

https://github.com/jugmac00/flask-reuploaded/issues/169
I am lazy , so it happend again, so I am not lazy again.

https://github.com/jugmac00/flask-reuploaded/issues/169
I am lazy , so it happend again, so I am not lazy again.


define valid initial Shelley ledger states

We should explicitly define the valid initial Shelley ledger states. In particular, for what Byron states B does toShelley B give a valid initial state?

This will allow us to ensure a smooth migration since the Shelley ledger will not be starting from absolute zero.  The state that we start in should ideally be one that can be reached by following valid state transitions from absolute zero, but must certainly meet any conditions that are necessary to ensure invariants for future transitions (including e.g. consistency/preservation of ada).


Program crashes when output container uses input container properties as output container as template after input container is closed

Overview
Program crashes when output container uses input container properties as output container as template after input container is closed
Expected behavior
The corresponding exception should be thrown instead of crashing the program.
Actual behavior
root@941f5896c51c:/tmp# python3 test.py
<av.VideoStream #0 h264, yuv420p 1920x1080 at 0x7f409f81c130>
Check duration:
Segmentation fault (core dumped)
root@941f5896c51c:/tmp#
Investigation
This error is similar to the 1137 issue fixed in version 11.0.0
Reproduction
import time
import av
import numpy as np

def make_sample_video(save_path, in_video_stream):
    duration = 4
    fps = 24
    total_frames = duration * fps
    vid_w = 256
    vid_h = 128

    container = av.open(save_path, mode="w")
    stream = container.add_stream(template=in_video_stream)
    stream.width = vid_w
    stream.height = vid_h
    stream.pix_fmt = "yuv420p"

    # Write random frames
    for frame_i in range(total_frames):
        img = np.random.randint(0, 255, (vid_h, vid_w, 3), dtype=np.uint8)
        frame = av.VideoFrame.from_ndarray(img, format="rgb24")
        for packet in stream.encode(frame):
            container.mux(packet)

    # Flush stream
    for packet in stream.encode():
        container.mux(packet)

    container.close()

sample_file_path = "rainbow_noise.mp4"
container = av.open(sample_file_path, mode="r")
in_video_stream = container.streams.video[0]

make_sample_video(sample_file_path, in_video_stream)
print(in_video_stream)

time.sleep(3)
container.close()

print("Check duration:", in_video_stream)
print("Finished!")

OS: Ubuntu 20.04.6
PyAV v11.0.0
Additional context
https://github.com/PyAV-Org/PyAV/issues/1137

This doesn't happen anymore.
In v12.0.0, you get an exception:
  File "av/frame.pyx", line 44, in av.frame.Frame._rebase_time
ValueError: Cannot rebase to zero time.


Long search time

Describe the bug
Meili searches 1.6M documents in 2.5 seconds when search phrase is something like 'what to do in life'. It is fast when search is one-two words of containing less used words.
Elastic search does it in <50ms.
To Reproduce
Expected behavior
Screenshots
Meilisearch version: [e.g. v0.20.0]
0.26.1
Additional context
I started noticing this after upgrade to 0.26.1, not sure if it is related to it.

Hello @vprelovac
Thanks for this report and testing Meilisearch!
Could you send us more information so that we can reproduce the issue? We already tested on datasets with several millions of documents and we did not get this issue yet.
We would need:

the settings you applied
and most of all, the dataset, otherwise it's complicated to reproduce. We would understand you cannot share it publically, however, you can send it privately by email. Be sure we will delete it right after our tests. This is something we have already done with some of our users.
the exact query you sent. With filter? With highlight?

Thanks in advance and sorry for the inconvenience 🙂

Unfortunately I decided to give up on meilie and continue using typsense.
There were just too many problems like:

database incompatibility between releases
slow indexing
poor quality of results
slow responses like this one

Wish you the best for the project and I will check it when you are at v1.0

Thank you for your feedback, too bad that you can't provide us with more information that would help us understand the issue. Good luck with your project!

Hi @vprelovac
Sorry to hear that. Indeed, we are doing a lot to solve indexing speed and reduce breaking changes in the future. We are stabilizing the APIs as we go along.
Can you share with us details about the poor quality of results? Would love to have some materials to think about.
Thanks!


refactor: make Scene Activation CC -> Scene ID stateless

@zwave-js-bot pack this

@zwave-js-bot pack this


Create functional test for generated bulk exports

That's strange. It works on nightly and beta, but not stable.
I don't know of any macro-related features in the upcoming beta... I will have to look into this.

Okay, it seems that expr and ident have different behavior in 1.45. Since it's better in 1.46, I won't dig into it further.
Now let's see if it passes the rest of CI.

This has now passed CI, and is ready for review.
What do you think, @schungx? Is this an acceptable way to do all of your bulk exports of "bulit-in" operations? I am not sure you can "meta macro" this much further, so you would probably have to write these two macros for each one.

Good news: I made it as generic as your original intentions. The actual generated Rust is probably uglier than you were thinking, but it should be no less efficient.
If you think it's acceptable, click the merge button!

This looks really close to what I need!
However, it seems to be a lot of boilerplate, since the core function may need to vary.  For example, it may have different number of arguments, of different types etc.
Is it possible to extract the wrapping boilerplate from the macro and make it more general?  Such as:

macro_rules! generate_ops {
    ($op_name:ident, $op_fn:ident, $($type_names:ident),+) => {
        pub mod $op_name {
            $(
                pub mod $type_names {
                    use rhai::plugin::*;
                    use super::super::$op_fn;
                    #[export_fn]
                                    <<< Paste in code here >>>
                }
            )*
        }
    }
}```

Is it possible to extract the wrapping boilerplate from the macro and make it more general?

After trying a couple of things, my current impression is: I don't think so.
When macros accept an entire block of paste code here, it is literal. It cannot be expanded or modified by the macro itself.
For example, based on your question, I tried to create a macro you invoke like this:
generate_ops! {
    name: add,
    types: i8, i16, i32, i64,
    op: pub fn add_generic<T: std::ops::Add<Output = T>>(x: T, y: T) -> T {
        x + y
    }
}

That is possible to write. I could generate a bunch of fn add_i32() which would redirect to the generic form with T = i32. The problem is, that doesn't really solve anything. It would still have the same "hard coding" of return type T and argument count of 2.
Even if you started to parameterize pieces, you still couldn't do everything. Consider:
generate_ops! {
    name: add,
    types: i8, i16, i32, i64,
    args: x, y,
    op: pub fn add_generic<T: std::ops::Add<Output = T>>(x: T, y: T) -> T {
        x + y
    }
}

That parameterizes the number of arguments, but not their types. If you added the return type as an input, it would be fixed, but could not be the types you expand to. And so on, and so on.
 They are designed after patterns of functions -- two inputs, one output, this pattern of types -- to let you copy and paste operations for types over and over again. If there is a new pattern of call, you wrote a new macro.
All the same limitations apply here, I'm sorry to say.

Yes actually I don't think I mind writing different macros for different cases, just wanted to see if it is possible to reduce the amount of boilerplate.
Your example is interesting:
generate_ops! {
    name: add,
    types: i8, i16, i32, i64, u8, u16, u32, u64, f32, f64,
    op: pub fn add_generic<T: std::ops::Add<Output = T>>(x: T, y: T) -> T {
        x + y
    }
}

Can I also run another one like this:
generate_ops! {
    name: neg,
    types: i8, i16, i32, i64,f32, f64,
    op: pub fn neg_generic<T: std::ops::Neg<Output = T>>(x: T) -> T {
        x.neg()
    }
}

And another one:
generate_ops! {
    name: is_neg,
    types: i8, i16, i32, i64,f32, f64,
    op: pub fn is_neg_generic<T: Zero + PartialOrd>(x: T) -> bool {
        ...
    }
}

If I can, then you have already solved  my problem.

Can I also run another one like this:

If you wrote a second macro, perhaps called generate_unary_op. The current PR should really be thought of as generate_binary_op, i.e. the signature must be: fn(T, T) -> T.
If you prefer that "struct style" syntax, and having the op embedded -- even though it is limited -- I could do that instead...

Now I understand you.  The signature form of the function is hard coded in the macro, it seems.
I was hoping maybe you can write a proc macro that can be more flexible...  but it doesn't really matter.  Your earlier macros will do the job just fine.  Your trick is creating multi-levels of modules to differentiate the functions by namespace instead of by name.
This I suppose is fine enough. I'll play around with it some more.

Thanks.
Also:

I was hoping maybe you can write a proc macro that can be more flexible

In fairness, I will expand a little bit more on why I am reluctant to do that.
Basically, procedural macros are more powerful in behavior, but see the input the same way as basic macros do: as giant token trees. This means:

Structuring and highlighting all the cases where the user should get an error instead of error: macro panicked is a manual process. Did you notice that the "simple" change to add the return_raw attribute was 200 lines, 50% of which were tests? That's because I had to add a number of new error cases and messages to the core parsing of attributes. That's just simple things like, "you need to have a string here" and "you need to delete a string here".

There is no type inference. You can tell what seems like a "type token", but anything you want to understand about what that type is? That is something you must know ahead of time, assume, or calculate from a blank sheet of paper.

The idea of having the user pass in a specifically-formed list of types, and then applying them to a format string in order to generate the output? That is waaaaay more complicated than it sounds given those limitations.

Ah!  Makes sense!
BTW, I've tried a number of combinations of your two macros.  They seem to work well for built-in types.  However, whenever it involves a type that is imported via use, it always come back with cannot find type X in this scope or something like that.
Try it out with type X = i64 and then put X as one o the types.
I guess it has something to do with macro hygene but don't know enough to be able to fix it...

They seem to work well for built-in types. However, whenever it involves a type that is imported via use, it always come back with cannot find type X in this scope or something like that.

The key is, you must include an  import at the site of use. Remember, you are creating a module, and in Rust, modules don't inherit use statements from the outside.
use rhai::Engine; // <-- this will do it for the generic form, but not the macro
pub fn run_thru_engine_generic<T: std::ops::Add<Output = T>>(x: T, y: Engine) -> T {
    /* magic occurs here */
    x
}

macro_rules! generate_ops {
    ($op_name:ident, $op_fn:ident, $($type_names:ident),+) => {
        pub mod $op_name {
            $(
                pub mod $type_names {
                    use rhai::plugin::*;
                    use super::super::$op_fn;
                    use rhai::Engine; // <-- this is the extra one you need for resolution within the module
                    #[export_fn]
                    pub fn op(x: $type_names, y: Engine) -> $type_names {
                        $op_fn(x, y)
                    }
                }
            )*
        }
    }
}

Doing that code and cleaning things up in my macro_unroll.rs test case will give an error about Clone not being implemented -- which means it was able to resolve the type Engine.

But that doesn't help if type_names is the type in question...  If one of the type_names needs to be use-ed, and others doesn't...
For example, say if type_names is i64, bool, MyType.  The first two requires no use statements, while the third one needs use super::super::$type_names;.

EDIT: OK. I can put in use {i64, bool}; to import them to the root.

And if necessary, you can use the ultimate sledgehammer I used in my macros! use super::super::*; :smile:


Fix double path rewrite routing failures

Case is, target service on the remote side is a tunnel.
If the path gets rewritten once remotely, it can throw off finding the right service in the local server.
Solution: a second linkup header linkup-destination set on every hop. If the destination has been calculated once, we reuse it on later hops.

This doesn't work. Destinations become permanent rather than temporary so persist across sub-requests..


traverson-hal support?

Is there an easy way to pull traverson-hal into traverson-angular?

Never mind. Turns out there's a lovely example in https://github.com/basti1302/traverson-angular/blob/master/browser/example/hal.js

Since you are the second person asking this question, I added docs for this and a link to the example.
https://github.com/basti1302/traverson-angular/#traverson-angular-with-media-type-plug-ins
Had planned to do this already, thanks for the ping.


[#112] Enable GPG checks of channel artifacts

Fixes #112

Initial SignatureValidator API
Pass GPG setting to dependant channels
Update validator signatur
Add SignatureValidator implementation
Use return status instead of exceptions
Report validation errors
Add keyserver support to the validator
Create channel version 2.1.0

@jmesnil could you review this please? It's a large one, if it makes it easy I can split it up into spec/API changes and implementation PRs.

@jmesnil this should be ready for re-review, sorry about the delay. Again if it's easier I can break this down into smaller PRs (e.g. API/Spec changes vs implementation)

@jmesnil would you be able to re-review the changes? I think it'd be good to get at least the channel part of this merged for WF35 so we don't have the problem with potential schema changes

@jmesnil I addressed the review notes apart from the class name as it's part of bouncycastle library


Hyperlink circular reference

The "how to manually configure device registration" link in the "Select your scenario" section links back to this same page (i.e. a circular reference).  There is no information on this page about manually configuring device registration.  The link target should be updated, or the link should be removed if that content does not exist.

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

ID: 72cdc251-618a-e84e-f40d-960b0ac69f99
Version Independent ID: 8cbaba3c-e883-2c71-28fb-f88db3fcaf7d
Content: How to plan hybrid Azure Active Directory join implementation in Azure Active Directory (Azure AD)
Content Source: articles/active-directory/devices/hybrid-azuread-join-plan.md
Service: active-directory
GitHub Login: @MarkusVi
Microsoft Alias: markvi

Hi @jholl016 , I tested the link and it properly links to the section in the article. The scenario in this case refers to Managed Domains vs. Federated Domains. https://docs.microsoft.com/en-us/azure/active-directory/devices/hybrid-azuread-join-plan#select-your-scenario

@jholl016 good catch - looks like the link got moved to here: https://docs.microsoft.com/en-us/azure/active-directory/devices/hybrid-azuread-join-manual
I made a pull request for review by @MarkusVi
https://github.com/MicrosoftDocs/azure-docs-pr/pull/65045

We will now proceed to close this thread. Changes generally go live in ~24 hours.


failed to build Project1.sln

Error when building project1.sln with Visual Studio 2019.
Seems caused by the path "project..\binaries"
Other projects get built just fine, except for project 1.
_Severity	Code	Description	Project	File	Line	Suppression State
Error	MSB3073	The command "copy /Y F:\Mastering-Graphics-Programming-with-Vulkan\project..\binaries\SDL2-2.0.18\lib\x64\SDL2.dll F:\Mastering-Graphics-Programming-with-Vulkan\project..\binaries
copy /Y F:\Mastering-Graphics-Programming-with-Vulkan\project..\binaries\assimp\windows\bin\assimp-vc142-mt.dll F:\Mastering-Graphics-Programming-with-Vulkan\project..\binaries
:VCEnd" exited with code 1.	RaptorEngine_Chapter1	C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\MSBuild\Microsoft\VC\v160\Microsoft.CppCommon.targets	155

Thanks for reporting this. Unfortunately I am not able to reproduce this issue. I am opening the solution project\RaptorEngine.sln and compiling RaptorEngine_Chapter1. I also double checked that the copy path is resolved correctly in the post build step:

Could you double check that this is what you're seeing as well? Which version of Visual Studio are you using?

I ran into this problem on Debian LInux this morning. It looks like the pull includes only Windows binaries. If anyone else has this issue, it is a simple fix to add these from apt.
sudo apt install libsdl2-2.0-0
sudo apt install libsdl2-dev
sudo apt install libassimp5
sudo apt install libassimp-dev

@theWatchmen, maybe add this to the Linux section?

Thanks lettings us know! We do provide the assimp library for Linux (https://github.com/PacktPublishing/Mastering-Graphics-Programming-with-Vulkan/tree/main/binaries/assimp/linux/lib) and CMake should reference that. I'll double check that we didn't forget to upload the SDL binaries for Linux.

@theWatchmen, my bad. You do indeed! I was apt getting SDL, so I just got them both. ;^)

No worries :) I added the instructions to install the SDL2 library to the README as that library is not provided with the repo.

Closing this because of no recent activity.


Support for nvim-treesitter-textobjects

First, thanks for your work on supporting R in treesitter.
I wonder if support for text objects (https://github.com/nvim-treesitter/nvim-treesitter-textobjects) is currently possible. The required files to extend a language with textobjects are located in queries/[language], e.g. https://github.com/nvim-treesitter/nvim-treesitter-textobjects/blob/master/queries/c/textobjects.scm for C.
In particular, @parameter.inner and @parameter.outer would be interesting for me, but I think most objects have their raison d'être. I had a quick look in the code, but I didn't find a named node for it.

Sure it is possible, someone would need to write the queries like you linked to.
@parameter.inner would likely be variations on this
(formal_parameters
  (identifier) @parameter.inner)

@mllg, https://github.com/nvim-treesitter/nvim-treesitter-textobjects/pull/173 added support for r

Great, thanks @aspeddro!

Thanks!
AFAICT @parameter.inner and @parameter.outer only work in the function definition (| is cursor position):
# works here
f = function(x|, y, ...) {
  x^2
}

# does not work here
f(x|, y)

Is this working as intended or am I mixing things up?

@mllg, https://github.com/nvim-treesitter/nvim-treesitter-textobjects/pull/181 add support to call functions.


Issue 310: Generated GPX file contains both  and  tags

Launch a popup window in JS where the user can select which GPX data parts shall be exported.
Additionally add the possibility for exporting of GPX waypoints.
Please note that it was necessary to update the jquery-ui version, as otherwise the popup diolog did not show up. I somewhere found the suggestion to update the version on stackoverflow and the updated version works.
Fixes #310

:+1: nice!

In the console it says to me: $(...).sortable is not a function and the web UI is scrambled a bit
Is the a js module missing?

Yes, I'm sorry, one file was missing. Now its added and the change in update-translations.sh reverted.

Thanks! This is now merged, let me know if this is okay for you!
Note that I've changed the css IDs to avoid collision in the future and also the URL parameters have now a gpx. prefix. Furthermore additionally to FIXME in the source you should add it to the issue text. See the default change for 'route' via #437

deployed, need to document the new parameters


Xdotnetcore.yml

javascript-client-generated.zip
android-client-generated.zip
Access everythinh to find a place

 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: alfian8787 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


[feature-request] Create auditing process on pRest

It would be nice to have an auditing feature on pRest that records who does what on the system. Basically it would log everything it does with more metadata in another table (possibly another data base) in order to allow one to see who has done what on the system.

I think that is a bad idea. I don't like of pREST be responsible by a feature of "database team".
Could be a nice idea to create a new middleware (by pREST user) or use notify feature from postgresql.

@kemelzaidan there are a PostgreSQL extension called PGAudit for this purpose. See: https://www.pgaudit.org/


Rotate orchestrator.log

I am wondering what the proper procedure for rotating the /var/log/orchestrator.log file is?
I tried setting up a logrotate rule, but orchestrator doesn't write to the new log once it's rotated. The only way I can find to force this is to issue service orchestrator restart, which seems a little extreme.
I see that you can set it up to write to syslog, but I prefer having the separate log file.

This is our logrotate config which works well:
# cat /etc/logrotate.d/orchestrator
/var/log/orchestrator.log {
  daily
  rotate 7
  missingok
  ifempty
  compress
  nodelaycompress
  copytruncate
}

Ah, copytruncate is the key here. Should have looked for more options in log rotate's settings.
I can confirm this is working for me as well now. Thanks!


Token StartAttribute in state Element Content would result in an invalid XML document.

When an element contains both an attribute and an element the exception Token StartAttribute in state Element Content would result in an invalid XML document. is thrown. This seems to have something to do with EnableMemberExceptionHandling().
For this sample I have the following classes:
public class RootElement
{
    public Bar Bar { get; set; }
    public string Version { get; set; }
}

public class Bar
{
    public string Name { get; set; }
}

Tests
Test 1

Without EnableMemberExceptionHandling()
RootElement has an attribute named Version, which is set.
RootElement has an element Bar, which is set.

var c = new ConfigurationContainer()
    .ConfigureType<RootElement>()
        .Name("Root")
        .Member(re => re.Version)
            .Attribute()

    .ConfigureType<Bar>()

    .Create();

var r = new RootElement
{
    Version = "1",
    Bar = new Bar { Name = "bar" },
};

r.SerializeToFile();

c.Cycle(r).Should().BeEquivalentTo(r);

This gives the following result:
<?xml version="1.0" encoding="utf-8"?>
<Root UniformsVersion="1" xmlns="clr-namespace:Unittests.Serialization;assembly=Unittests">
  <Bar>
    <Name>bar</Name>
  </Bar>
</Root>

Test 2

With EnableMemberExceptionHandling()
RootElement has an attribute named Version, which is set.
RootElement has an element Bar, which is set.

var c = new ConfigurationContainer()
    .EnableMemberExceptionHandling()
    .ConfigureType<RootElement>()
        .Name("Root")
        .Member(re => re.Version)
            .Attribute()

    .ConfigureType<Bar>()

    .Create();

var r = new RootElement
{
    Version = "1",
    Bar = new Bar { Name = "bar" },
};

r.SerializeToFile();

c.Cycle(r).Should().BeEquivalentTo(r);

Which throws the following stacktrace:
Test Name:	Unittests.Serialization.SerializeAttributesSpec.SerializeAttributes
Test FullName:	Unittests.Serialization.SerializeAttributesSpec.SerializeAttributes
Test Source:	C:\Workspace\Unittests\Serialization\SerializeAttributes.cs : line 78
Test Outcome:	Failed
Test Duration:	0:00:00,602

Result StackTrace:
bij ExtendedXmlSerializer.ExtensionModel.Content.Members.MemberExceptionHandlingExtension.MemberSerializer.Write(IFormatWriter writer, Object instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ExtensionModel\Content\Members\MemberExceptionHandlingExtension.cs:regel 94
   bij ExtendedXmlSerializer.ContentModel.Members.MemberListWriter.Write(IFormatWriter writer, Object instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\Members\MemberListWriter.cs:regel 36
   bij ExtendedXmlSerializer.ContentModel.Serializer`1.Write(IFormatWriter writer, T instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\Serializer.cs:regel 47
   bij ExtendedXmlSerializer.ContentModel.Content.Enclosure`1.Write(IFormatWriter writer, T instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\Content\Enclosure.cs:regel 51
   bij ExtendedXmlSerializer.ContentModel.SerializerAdapter`1.Write(IFormatWriter writer, T instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\SerializerAdapter.cs:regel 66
   bij ExtendedXmlSerializer.Write`1.Execute(Writing`1 parameter) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\Write.cs:regel 43
   bij ExtendedXmlSerializer.Serializer`2.Serialize(TWrite writer, Object instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\Serializer.cs:regel 41
   bij ExtendedXmlSerializer.ExtensionModel.Xml.ExtendedXmlSerializer.Serialize(XmlWriter writer, Object instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ExtensionModel\Xml\ExtendedXmlSerializer.cs:regel 40
   bij Unittests.Serialization.Support.Extensions.SerializeToFile(Object object, IExtendedXmlSerializer serializer, String fileName) in C:\Workspace\Unittests\Serialization\Support\Extensions.cs:regel 40
   bij Unittests.Serialization.SerializeAttributesSpec.SerializeAttributes() in C:\Workspace\Unittests\Serialization\SerializeAttributes.cs:regel 119
----- Inner Stack Trace -----
   bij System.Xml.XmlWellFormedWriter.ThrowInvalidStateTransition(Token token, State currentState)
   bij System.Xml.XmlWellFormedWriter.AdvanceState(Token token)
   bij System.Xml.XmlWellFormedWriter.WriteStartAttribute(String prefix, String localName, String namespaceName)
   bij System.Xml.XmlWriter.WriteAttributeString(String localName, String value)
   bij ExtendedXmlSerializer.ExtensionModel.Xml.XmlWriter.Content(IIdentity property, String content) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ExtensionModel\Xml\XmlWriter.cs:regel 120
   bij ExtendedXmlSerializer.ContentModel.Format.ContextualWriter`1.Write(IFormatWriter writer, T instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\Format\ContextualWriter.cs:regel 40
   bij ExtendedXmlSerializer.ContentModel.DecoratedWriter`1.Write(IFormatWriter writer, T instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\DecoratedWriter.cs:regel 43
   bij ExtendedXmlSerializer.ContentModel.DecoratedWriter`1.Write(IFormatWriter writer, T instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\DecoratedWriter.cs:regel 43
   bij ExtendedXmlSerializer.ContentModel.Serializer`1.Write(IFormatWriter writer, T instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\Serializer.cs:regel 47
   bij ExtendedXmlSerializer.ContentModel.Properties.Property`1.Write(IFormatWriter writer, T instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\Properties\Property.cs:regel 47
   bij ExtendedXmlSerializer.ContentModel.Properties.ConverterProperty`1.Write(IFormatWriter writer, T instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\Properties\ConverterProperty.cs:regel 41
   bij ExtendedXmlSerializer.ContentModel.GenericSerializerAdapter`1.Write(IFormatWriter writer, Object instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\GenericSerializerAdapter.cs:regel 36
   bij ExtendedXmlSerializer.ContentModel.Members.MemberSerializers.Writer.Write(IFormatWriter writer, Object instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\Members\MemberSerializers.cs:regel 107
   bij ExtendedXmlSerializer.ContentModel.Members.MemberSerializer.Write(IFormatWriter writer, Object instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\Members\MemberSerializer.cs:regel 46
   bij ExtendedXmlSerializer.ContentModel.Members.PropertyMemberSerializer.Write(IFormatWriter writer, Object instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ContentModel\Members\PropertyMemberSerializer.cs:regel 36
   bij ExtendedXmlSerializer.ExtensionModel.Content.Members.MemberExceptionHandlingExtension.MemberSerializer.Write(IFormatWriter writer, Object instance) in C:\projects\extendedxmlserializer\src\ExtendedXmlSerializer\ExtensionModel\Content\Members\MemberExceptionHandlingExtension.cs:regel 90
Result Message:
System.InvalidOperationException : An exception was encountered while serializing member 'Unittests.Serialization.RootElement.Version'.  Provided instance is 'Unittests.Serialization.RootElement'.
---- System.InvalidOperationException : Token StartAttribute in state Element Content would result in an invalid XML document..

Test 3

With EnableMemberExceptionHandling()
RootElement has an attribute named Version, which is NOT set.
RootElement has an element Bar, which is set.

var c = new ConfigurationContainer()
    .EnableMemberExceptionHandling()
    .ConfigureType<RootElement>()
        .Name("Root")
        .Member(re => re.Version)
            .Attribute()

    .ConfigureType<Bar>()

    .Create();

var r = new RootElement
{
    //Version = "1",
    Bar = new Bar { Name = "bar" },
};

r.SerializeToFile();

c.Cycle(r).Should().BeEquivalentTo(r);

which has this result:
<?xml version="1.0" encoding="utf-8"?>
<Root xmlns="clr-namespace:Unittests.Serialization;assembly=Common.Unittests">
  <Bar>
    <Name>bar</Name>
  </Bar>
</Root>

Test 4

With EnableMemberExceptionHandling()
RootElement has an attribute named Version, which is set.
RootElement has an element Bar, which is NOT set.

var c = new ConfigurationContainer()
    .EnableMemberExceptionHandling()
    .ConfigureType<RootElement>()
        .Name("Root")
        .Member(re => re.Version)
            .Attribute()

    .ConfigureType<Bar>()

    .Create();

var r = new RootElement
{
    Version = "1",
    //Bar = new Bar { Name = "bar" },
};

r.SerializeToFile(c, @"C:\Users\johan.SERVER-PARLANDO\AppData\Local\Temp\xml.xml");

c.Cycle(r).Should().BeEquivalentTo(r);

<?xml version="1.0" encoding="utf-8"?>
<Root Version="1" xmlns="clr-namespace:Common.Unittests.Serialization;assembly=Common.Unittests" />

Nice catch @johanvergeer and thank you for the thorough description and test scenarios.  It made it easier to track down.  I have committed a fix into the preview feed.  Please give it a try and let me know if you run into any further issues around this.
https://www.myget.org/F/wojtpl2/api/v3/index.json
(Note: If you do run into issues, it may be a caching problem with Nuget and how we version our assemblies.  Please try deleting all versions of ExtendedXmlSerializer from your nuget cache and see if that fixes it.)

Hi @Mike-EEE ,
I just downloaded the latest 2.1.21 version (after deleting the cache), but the error still shows.

Boh.  Are you by chance able to successfully duplicate on your end the following test that was committed as part of the fix?
https://github.com/wojtpl2/ExtendedXmlSerializer/blob/bf198270a37e400139014ba31db1b525fbd1df8a/test/ExtendedXmlSerializer.Tests/ReportedIssues/Issue257Tests.cs#L13-L34
If that test fails for you then we can be sure it's a caching issue.
If I recall correctly, you had a caching issue previously that went away with a reboot.  Perhaps try also restarting Visual Studio first before rebooting.
If that test does pass and your code still fails, then we have another bug I will have to trace down.

Oh, I know.  Perhaps try cleaning your solution as well in addition to clearing your nuget cache.  It's probably doing a comparison on version and not copying it over because the version is the same and it's already in your bin folder.
@wojtpl2 we really need to have the continuous deployment on myget kick off a new version with each commit. 😁

This seems to be fixed.
Thanks

@wojtpl2 we really need to have the continuous deployment on myget kick off a new version with each commit. 😁

That would be awesome

Cool!  Glad we got that one.  I will circle deploying .21 next Tuesday to account for any other issues that might pop up during that time. 👍

This has been deployed to 2.1.21: https://www.nuget.org/packages/ExtendedXmlSerializer/
Please let us know if you encounter any further issues/questions/concerns around this and we will do our best to assist you.
Closing for now. 👍


Few questions

Question 1: How this the algorithm behave in a scenario with two tracks of two persons, where the detector fails to detect one person in one frame but manage to detect the person in the next frame. Will it recover the track or simple assign it a new trackid?
Question 2: Any plans to make an online version of this algorithm (like SORT) ?

Answer  1: If there is a "missing detection" the track will be terminated. If one or more frames later a detection is received which could belong to the first track, a new track with a new ID is started. Currently there is no option to recover a track. Obviously this can cause a lot of ID switches that seem unnecessary but can also prevent some other failure cases. Anyway, here is of course a lot of room for improvement, but for the sake of simplicity (to prove the point in the paper) no strategy for track recovery was included in the current work.
Answer 2: If the time allows, i may implement and evaluate an online version of the tracker. The most straightforward approach would be to remove the filtering for sigma_h and t_min, but then the performance will degrade (probably a lot).

Thanks for your answer! @bochinski


Make querystring.stringify params optional, rather than using maybe types.

From the Query String docs:

Serialize an object to a query string. Optionally override the default separator ('&') and assignment ('=') characters.

Test file:
#!/usr/bin/env node
/* @flow */
import querystring from 'querystring';
var output = querystring.stringify({ 'key': 'value' });
console.log(output);

flow without this PR:  call of method stringify Too few arguments (expected default/rest parameters in function) Found 1 error
flow with this PR: No errors!

Nice! Looks correct to me.

Great! Thanks for fixing this!


OpenRPC support

Not sure really where this ticket belongs, but this project and the surrounding ones are awesome.
http://open-rpc.org/ is an OpenAPI-like specification for JSON-RPC based architectures.
I think it would benefit from having OpenRPC support, on many levels, as your core architecture is JSON-RPC, but also you could support OpenRPC as inputs as an alternative to OpenAPI.

@shanejonas Thanks for the suggestion. Yeah I've seen Open RPC, and I like the concept.
Currently just trying to get the Rust, Python, Kotlin, TypeScript, Java, Swift, C, C++ languages working smoothly with my CDD approach, then there should be huge opportunity to expand (and actually get community interest + involvement).
Yeah yeah, the perfect is the enemy of the good and I should probably limit it to a smaller number of languages… but wouldn't it be so much more expansive if we just kept developing until this point? 🥇
Would welcome your input =)
PS: Sorry I only saw this now, must've gotten lost in the huge number of notifications from March 2020. For future—if replied aren't speedy—my email is<EMAIL_ADDRESS>

@shanejonas Thanks for the suggestion. Yeah I've seen Open RPC, and I like the concept.
Currently just trying to get the Rust, Python, Kotlin, TypeScript, Java, Swift, C, C++ languages working smoothly with my CDD approach, then there should be huge opportunity to expand (and actually get community interest + involvement).
Yeah yeah, the perfect is the enemy of the good and I should probably limit it to a smaller number of languages… but wouldn't it be so much more expansive if we just kept developing until this point? 🥇
Would welcome your input =)
PS: Sorry I only saw this now, must've gotten lost in the huge number of notifications from March 2020. For future—if replies aren't speedy—my email is<EMAIL_ADDRESS>

@shanejonas Thanks for the suggestion. Yeah I've seen OpenRPC, and I like the concept.
Currently just trying to get the Rust, Python, Kotlin, TypeScript, Java, Swift, C, C++ languages working smoothly with my CDD approach, then there should be huge opportunity to expand (and actually get community interest + involvement).
Yeah yeah, the perfect is the enemy of the good and I should probably limit it to a smaller number of languages… but wouldn't it be so much more expansive if we just kept developing until this point? 🥇
Would welcome your input =)
PS: Sorry I only saw this now, must've gotten lost in the huge number of notifications from March 2020. For future—if replies aren't speedy—my email is<EMAIL_ADDRESS>

@shanejonas Thanks for the suggestion. Yeah I've seen OpenRPC, and I like the concept.
Currently just trying to get the Rust, Python, Kotlin, TypeScript, Java, Swift, C, C++ languages working smoothly with my CDD approach, then there should be huge opportunity to expand (and actually get community interest + involvement).
Yeah yeah, the perfect is the enemy of the good and I should probably limit it to a smaller number of languages… but wouldn't it be so much more expansive if we just kept developing until this point? 🥇
Would welcome your input =)

PS: Beyond RPC there's also FFI and cross language binary compatible formats like Arvo, Thrift and Protobuf. That's also planned for the future.
PS: Sorry I only saw this now, must've gotten lost in the huge number of notifications from March 2020. For future—if replies aren't speedy—my email is<EMAIL_ADDRESS>


Restructure unittests

I changed a couple of imports such that the tests can now be executed all at once from the root directory with python -m unittest discover. We can now add this to the setup.py script in order to always run all tests before packaging.
Signed-off-by: Eva Charlotte Mayer<EMAIL_ADDRESS>

I added an entry point. Tests are now executable via python setup.py test


Keep getting IndentationError from the ground truth answers for HUMANEVAL_PLUS_VERSION = "v0.1.9", but works when set to 0.1.8

Kept getting this error on all machines I tested, regardless of installation method:
Traceback (most recent call last):
  File "/mnt/data/FastEval/.venv/bin/evalplus.evaluate", line 8, in <module>
    sys.exit(main())
  File "/mnt/data/FastEval/.venv/src/evalplus/evalplus/evaluate.py", line 275, in main
    evaluate_humaneval(args)
  File "/mnt/data/FastEval/.venv/src/evalplus/evalplus/evaluate.py", line 136, in evaluate_humaneval
    expected_output = get_groundtruth(problems, dataset_hash)
  File "/mnt/data/FastEval/.venv/src/evalplus/evalplus/evaluate.py", line 48, in get_groundtruth
    oracle["base"], oracle["base_time"] = trusted_exec(
  File "/mnt/data/FastEval/.venv/src/evalplus/evalplus/gen/util/__init__.py", line 7, in trusted_exec
    exec(code, exec_globals)
  File "<string>", line 39
    ans = 0
               ^
IndentationError: unindent does not match any outer indentation level

Was only able to fix it by changing HUMANEVAL_PLUS_VERSION = "v0.1.9" to  "v0.1.8"

@alpayariyak Thanks for the report. Can you delete your cache at ~/.cache/evalplus and retry? It should be fixed now.

Thank you very much @ganler!


Auto deselect.

Hi, Thanks a lot for your code.
I have a little suggest.
imagePickerController.allowsMultipleSelection = YES;
imagePickerController.minimumNumberOfSelection = 1;
imagePickerController.maximumNumberOfSelection = 1;

In this kind of case, when selecting a new picture can you make it deselect the old one automatically?
Then the user can select the new one without deselecting the old one before.
Because before tap the done button, user maybe change mind when scrolling.

Implemented in 2.5.0.

👍


OpenApi Code Generation

Use an OpenApi specification to generate the client instead of it all being handwritten.
For endpoints, would then be able to use the examples for testing purpose.

Model generation

Enums => StringEnum
Identifier => Value class
Identifiable => implement Identifiable interface
Schema formats:

byte (for Ranger int id and specialization id)
short (for skill int id)
arrayOfArray (for skills_by_palette which is an array of arrays instead of key mapped to object)
duration-seconds: Amount of time in seconds.
duration-milliseconds: Amount of time in milliseconds
dimension-2d: Array of doubles indicating length/width.
point-2d
point-3d
texturebound-topleft: Rectangle by using two array of two doubles.
texturebound-bottomleft
textureposition

Resource generation

Multiple files which include the models/endpoints, each one representing an individual resource

Tag management to include resource when merging the files

Client generation

Ability to provide scope validation

Permissions

account, builds, characters, guilds, inventories, progression, pvp, tradingpost, unlocks, wallet

Guild ranking

leader, member

Profession

necromancer, mesmer, elementalist ...

Paging

Through link header

Example: </v2/account/buildstorage?page=1&page_size=1>; rel=next, </v2/account/buildstorage?page=0&page_size=1>; rel=self, </v2/account/buildstorage?page=0&page_size=1>; rel=first, </v2/account/buildstorage?page=5&page_size=1>; rel=last

https://github.com/Woody230/KotlinExtensions/issues/39


add support for kubebuilder v2 kubebuilder:object:root comment

The kubebuilder V2 adds +kubebuilder:object:root comment instead of +genclient comment to public types.
BTW, the +kubebuilder:object:root is in ListTypes, while +genclient don't appear in ListTypes, this PR will filter out listTypes if only +kubebuilder:object:root presents.

@fawadkhaliq  @M00nF1sh I tried your branch on my kuberbuilder api but it's not working

Thank you. We also need to make sure this doesn't break compat for existing projects (listed in readme).

@fawadkhaliq @M00nF1sh I tried your branch on my kuberbuilder api but it's not working

@evalsocket, u still need to create a doc.go contain same content(without import and var) of your groupversion_info.go.
the 'doc.go' requirement is from the k8s library this gen-crd-api-reference relies on.

@M00nF1sh Thanks....You made my day

@evalsocket Can you also please validate this with one of the projects listed in README.md?
Sadly, I can't just merge this because "it works for you". Removing //+genclient most likely will have consequences.
Right now to me, my priorities aren't at Kubebuilder v2 or Operator SDK. This project has existing users and keeping those working is my top priority.