Project Generator not compatible with SDK version 1.5 on Windows?

Hi
I installed the C/C++ SDK by running "pico-setup-windows-x64-standalone.exe" and then downloaded the Pico Project Generator. The Project Generator did not run because tkinter is missing (I posted this as a separate issue on github.com/raspberrypi/pico-setup-windows/issues/12).
I then installed a new version of Python manually and changed the python path in "pico-env.cmd" to point to that newly installed python.exe. With this trick, tkinter was present and I was able to run the Project Generator in GUI mode.
However, when trying to create a new project, the error message appears:
_CMake Error at CMakeLists.txt:21 (project):
Running
'nmake' '-?'
failed with:
Das System kann die angegebene Datei nicht finden  (=file not found)._
As far as I understand, the SDK installer for Windows sets up CMake to use ninja and not nmake (anymore). Is there a possibility to make the Project Generator compatible with the latest version of the SDK installer for Windows?
Thx.

Hi, thanks for the report, I'll try and find the time to look in to this.

@kilograham Hi Graham, do you know the runes for a ninja build on windows to replicate the current "cmake -DCMAKE_BUILD_TYPE=Debug -G "NMake Makefiles" .."

I suspect it is as simple as :
cmake -DCMAKE_BUILD_TYPE=Debug -G Ninja ..
then
ninja in the build folder?

yes (assuming the installer puts ninja in the path)

Modified pico_project.py starting from line 1341:
if isWindows:
    # Had a special case report, when using MinGW, need to check if using nmake or mingw32-make.
    if shutil.which("mingw32-make"):
        # Assume MinGW environment
        cmakeCmd = 'cmake -DCMAKE_BUILD_TYPE=Debug -G "MinGW Makefiles" ..'
        makeCmd = 'mingw32-make '
    elif shutil.which("ninja"):
        # When installing SDK version 1.5.0 on windows with installer pico-setup-windows-x64-standalone.exe, ninja is used
        cmakeCmd = 'cmake -DCMAKE_BUILD_TYPE=Debug -G Ninja ..'
        makeCmd = 'ninja '
    else:
        # Everything else assume nmake
        cmakeCmd = 'cmake -DCMAKE_BUILD_TYPE=Debug -G "NMake Makefiles" ..'
        makeCmd = 'nmake '

seems to work fine.
Many Thanks!

With the modifications described above, compiling was possible, but I ran into problems when trying to debug using VSCode. It turned out that the JSON files generated in the .vscode directory do not match the settings needed for the SDK installed using "pico-setup-windows-x64-standalone.exe". I modified the python script to add a function that generates the JSON files of the .vscode direcory in the examples folder. I am by far not an expert on these settings, so if someone with knowledge could have a look at it and maybe this code could be added in a future version of the pico project generator.
Here is the function:
# Generates the requested project files for Windows SDK 1.5.0
def generateProjectFiles_Win(projectPath, projectName, sdkPath, projects, debugger):

oldCWD = os.getcwd()

os.chdir(projectPath)

deb = debugger_config_list[debugger]

for p in projects :
    if p == 'vscode':
        # launch.json
        v1 = (  '{\n'
                '  "version": "0.2.0",\n'
                '  "configurations": [\n'
                '    {\n'
                '      "name": "Pico Debug (Cortex-Debug)",\n'
                '      "cwd": "${workspaceFolder}",\n'
                '      "executable": "${command:cmake.launchTargetPath}",\n'
                '      "request": "launch",\n'
                '      "type": "cortex-debug",\n'
                '      "servertype": "openocd",\n'
                '      "gdbPath": "arm-none-eabi-gdb",\n'
                '      "device": "RP2040",\n'
                '      "configFiles": [\n'
                '        "interface/cmsis-dap.cfg",\n'
                '        "target/rp2040.cfg"\n'
                '      ],\n'
                '      "svdFile": "${env:PICO_SDK_PATH}/src/rp2040/hardware_regs/rp2040.svd",\n'
                '      "runToEntryPoint": "main",\n'
                '      "openOCDLaunchCommands": [\n'
                '        "adapter speed 1000"\n'
                '      ]\n'
                '    },\n'
                '    {\n'
                '      "name": "Pico Debug (Cortex-Debug with external OpenOCD)",\n'
                '      "cwd": "${workspaceFolder}",\n'
                '      "executable": "${command:cmake.launchTargetPath}",\n'
                '      "request": "launch",\n'
                '      "type": "cortex-debug",\n'
                '      "servertype": "external",\n'
                '      "gdbTarget": "localhost:3333",\n'
                '      "gdbPath": "arm-none-eabi-gdb",\n'
                '      "device": "RP2040",\n'
                '      "svdFile": "${env:PICO_SDK_PATH}/src/rp2040/hardware_regs/rp2040.svd",\n'
                '      "runToEntryPoint": "main"\n'
                '    },\n'
                '    {\n'
                '      "name": "Pico Debug (C++ Debugger)",\n'
                '      "type": "cppdbg",\n'
                '      "request": "launch",\n'
                '      "cwd": "${workspaceFolder}",\n'
                '      "program": "${command:cmake.launchTargetPath}",\n'
                '      "MIMode": "gdb",\n'
                '      "miDebuggerPath": "arm-none-eabi-gdb",\n'
                '      "miDebuggerServerAddress": "localhost:3333",\n'
                '      "debugServerPath": "openocd",\n'
                '      "debugServerArgs": "-f interface/cmsis-dap.cfg -f target/rp2040.cfg -c \\"adapter speed 1000\\"",\n'
                '      "serverStarted": "Listening on port .* for gdb connections",\n'
                '      "filterStderr": true,\n'
                '      "stopAtEntry": true,\n'
                '      "hardwareBreakpoints": {\n'
                '        "require": true,\n'
                '        "limit": 4\n'
                '      },\n'
                '      "preLaunchTask": "Flash",\n'
                '      "svdPath": "${env:PICO_SDK_PATH}/src/rp2040/hardware_regs/rp2040.svd"\n'
                '    }\n'
                '  ]\n'
                '}\n')

        # c_cpp_properties.json
        c1 = (  '{\n'
                '  "configurations": [\n'
                '    {\n'
                '      "name": "Pico",\n'
                '      "includePath": [\n'
                '        "${workspaceFolder}/**",\n'
                '        "${env:PICO_SDK_PATH}/**"\n'
                '      ],\n'
                '      "defines": [],\n'
                '      "compilerPath": "${env:PICO_INSTALL_PATH}/gcc-arm-none-eabi/bin/arm-none-eabi-gcc.exe",\n'
                '      "cStandard": "c11",\n'
                '      "cppStandard": "c++11",\n'
                '      "intelliSenseMode": "linux-gcc-arm",\n'
                '      "configurationProvider": "ms-vscode.cmake-tools"\n'
                '    }\n'
                '  ],\n'
                '  "version": 4\n'
                '}\n')

        #settings.json
        s1 = (  '{\n'
                '    // These settings tweaks to the cmake plugin will ensure\n'
                '    // that you debug using cortex-debug instead of trying to launch\n'
                '    // a Pico binary on the host\n'
                '    "cmake.statusbar.advanced": {\n'
                '        "debug": {\n'
                '            "visibility": "hidden"\n'
                '        },\n'
                '        "launch": {\n'
                '            "visibility": "hidden"\n'
                '        },\n'
                '        "build": {\n'
                '            "visibility": "hidden"\n'
                '        },\n'
                '        "buildTarget": {\n'
                '            "visibility": "hidden"\n'
                '        }\n'
                '    },\n'
                '    "cmake.buildBeforeRun": true,\n'
                '    "cmake.configureOnOpen": true,\n'
                '    "cmake.configureSettings": {\n'
                '      "CMAKE_MODULE_PATH": "${env:PICO_INSTALL_PATH}/pico-sdk-tools"\n'
                '    },\n'
                '    "cmake.generator": "Ninja",\n'
                '    "C_Cpp.default.configurationProvider": "ms-vscode.cmake-tools"\n'
                '}\n')

        #extensions.json
        e1 = (  '{\n'
                '  "recommendations": [\n'
                '    "marus25.cortex-debug",\n'
                '    "ms-vscode.cmake-tools",\n'
                '    "ms-vscode.cpptools",\n'
                '    "ms-vscode.cpptools-extension-pack",\n'
                '    "ms-vscode.vscode-serial-monitor"\n'
                '  ]\n'
                '}\n')

        #cmake-kits.json
        k1 = (  '[\n'
                '  {\n'
                '    "name": "Pico ARM GCC",\n'
                '    "description": "Pico SDK Toolchain with GCC arm-none-eabi",\n'
                '    "toolchainFile": "${env:PICO_SDK_PATH}/cmake/preload/toolchains/pico_arm_gcc.cmake"\n'
                '  }\n'
                ']\n')

        #tasks.json
        t1 = (  '{\n'
                '  "version": "2.0.0",\n'
                '  "tasks": [\n'
                '    {\n'
                '      "label": "Flash",\n'
                '      "type": "shell",\n'
                '      "command": "openocd",\n'
                '      "args": [\n'
                '        "-f",\n'
                '        "interface/cmsis-dap.cfg",\n'
                '        "-f",\n'
                '        "target/rp2040.cfg",\n'
                '        "-c",\n'
                '        "adapter speed 1000; program {${command:cmake.launchTargetPath}} verify reset exit"\n'
                '      ],\n'
                '      "problemMatcher": []\n'
                '    },\n'
                '    {\n'
                '      "label": "Build",\n'
                '      "type": "cmake",\n'
                '      "command": "build",\n'
                '      "problemMatcher": "$gcc",\n'
                '      "group": {\n'
                '        "kind": "build",\n'
                '        "isDefault": true\n'
                '      }\n'
                '    }\n'
                '  ]\n'
                '}\n')

        # Create a build folder, and run our cmake project build from it
        if not os.path.exists(VSCODE_FOLDER):
            os.mkdir(VSCODE_FOLDER)

        os.chdir(VSCODE_FOLDER)

        filename = VSCODE_LAUNCH_FILENAME
        file = open(filename, 'w')
        file.write(v1)
        file.close()

        file = open(VSCODE_C_PROPERTIES_FILENAME, 'w')
        file.write(c1)
        file.close()

        file = open(VSCODE_SETTINGS_FILENAME, 'w')
        file.write(s1)
        file.close()

        file = open(VSCODE_EXTENSIONS_FILENAME, 'w')
        file.write(e1)
        file.close()

        file = open(VSCODE_CMAKEKITS_FILENAME, 'w')
        file.write(k1)
        file.close()

        file = open(VSCODE_TASKS_FILENAME, 'w')
        file.write(t1)
        file.close()

    else :
        print('Unknown project type requested')

os.chdir(oldCWD)

And further down in the code, an if-clause to choose these files if on Windows:
if params['projects']:
        if isWindows:
            generateProjectFiles_Win(projectPath, params['projectName'], params['sdkPath'], params['projects'], params['debugger'])
        else:
            generateProjectFiles(projectPath, params['projectName'], params['sdkPath'], params['projects'], params['debugger'])

Hi, I just pushed a possible fix for all this to
https://github.com/raspberrypi/pico-project-generator/tree/update_vscode_json_to_sdk1_5
Testing would be appreciated.

Tested. Test environment:
Windows Sandbox, freshly installed https://github.com/raspberrypi/pico-setup-windows
Because tkinter is (for no obvious reasons) still missing in this packet, installed latest Python for Windows:
https://www.python.org/downloads/release/python-3113/
and edited "....\Pico SDK v1.5.0\pico-env.cmd" to change the path to the new python.exe:
rem call :AddToPath "%PICO_INSTALL_PATH%\python"
call :AddToPath "(something like: ....\AppData\Local\Programs\Python\Python311\)"

Started project generator in GUI mode, made a test project, opened VSCode, opened the directory of the test project and VSCode started working.
Error message appeared:
Failed to parse "c:\pico\Test\Testproject1.vscode\c_cpp_properties.json": Unexpected token p in JSON at position 4
I can find no obvious errors in this JSON file, but I am not an expert on VSCode settings...
Klicked on CMake icon on the tool button and built the projekt. Everything ran smoothly with no error message.
Project compiled and all the output files were generated.

Looks to be a backslash/forward slash parsing issue on path names. Will take a look

OK, this was actually a backslash escape issue, I think Windows paths need a double backslash in JSON files. So have added this and pushed to this branch for testing.


Chore: remove unused font to fix CI build warning

See #2298

seems like Link Checker job failed same on some fews prev merged PR too.
https://github.com/near/docs/actions/runs/11606881487/job/32319538828?pr=2283
https://github.com/near/docs/actions/runs/11792833691/job/32847173936?pr=2296


override tagname for all elements

I want to override all the tagNames for creating an expandable table, so I need to override the panel body, the root element's tagname too, etc. Is it possible?

This addon should not support doing that because a table is not an element that is eligible for interactivity (please see the HTML spec for more details).
I'm closing this as a stale issue, please re-open if you feel as though it was closed in error. 👍


ApiAuth.authentic? always return false

I have set up the client side as the following:
  	access_id = "1"
    secret_key = 'hello'

    headers = { 'Content-MD5' => Digest::MD5.hexdigest('go_to_space!'),
        'Content-Type' => "text/plain",
        'Date' => Time.zone.now }
    request = RestClient::Request.new(:url => "http://localhost:4000/",
        :headers => headers,
        :method => :get)

    @signed_request = ApiAuth.sign!(request, access_id, secret_key)
    @headers = ApiAuth::Headers.new(@signed_request)
    @response = @signed_request.execute

And the server side as the following:
    access_id = ApiAuth.access_id(request)
    api_client = ApiClient.where(:id => access_id.to_i).last
    if api_client then
      result = ApiAuth.authentic?(request, api_client.secret)
    end

But ApiAuth.authentic? result is always false. Any clue.
I am using api-auth 1.3.1
Thank you

I'm also encountering this problem.

@moustafasallam, It looks like a Content-MD5 is being set, but then the request is a GET request. A GET request doesn't typically have any content. My guess is that the server is not seeing any content and thus the Content-MD5 is not matching.
Another possible gotcha to watch out for is to make sure the client and servers are both set to the correct time.

@kjg, Thank you. It is time stamp issue indeed. I removed adding the date to the client request http header and it works now just fine.

@moustafasallam Glad to hear it. You should really consider syncing the time, though. It prevents replay attacks by ensuring packets can't get re-sent.


[Task]: Fix BIC negative when transition many accounts

I think this can be because we are not estimating the mana cost with enough buffer and if the mana cost changes, then the bic can go negative. We can try adding 1 extra slot (instead of the 3 we had originally) and see if it still happens, I feel like it hsouldntshouldnt 🤞🏼

Fixed by the SDK


fix: ensure that latest transactions are correct for the network

fixes #2692

It could have "broken" view from time to time, when switching between networks:
https://github.com/superhero-com/superhero-wallet/assets/69896204/c471a0e8-20ed-4c62-bc0f-ad588567bee1

It could have "broken" view from time to time, when switching between networks:

The behaviour is very strange, turned out that from time to time the watcher of the networks in the latestTransactions composable, stops it's work. This is happening (mostly) if you will try to send eth on the /account page.
https://github.com/superhero-com/superhero-wallet/blob/feat/eth-support/src/composables/latestTransactionList.ts#L178
@peronczyk What do you think about this issue?

It could have "broken" view from time to time, when switching between networks:

The behaviour is very strange, turned out that from time to time the watcher of the networks in the latestTransactions composable, stops. This is happening (mostly) if you will try to send eth on the /account page. https://github.com/superhero-com/superhero-wallet/blob/feat/eth-support/src/composables/latestTransactionList.ts#L178 @peronczyk What do you think about this issue?

I feel that regular watch within the composable is not always the best idea. I think this PR will fix this issue: https://github.com/superhero-com/superhero-wallet/pull/2598
@Liubov-crypto maybe you can confirm this?

It could have "broken" view from time to time, when switching between networks:

The behaviour is very strange, turned out that from time to time the watcher of the networks in the latestTransactions composable, stops. This is happening (mostly) if you will try to send eth on the /account page. https://github.com/superhero-com/superhero-wallet/blob/feat/eth-support/src/composables/latestTransactionList.ts#L178 @peronczyk What do you think about this issue?

I feel that regular watch within the composable is not always the best idea. I think this PR will fix this issue: #2598
@Liubov-crypto maybe you can confirm this?

I'm afraid not, Txs from testnet could be visible in mainet from time to time, I found API error in console

https://github.com/superhero-com/superhero-wallet/assets/69896204/8fc805fe-6a45-4c25-8675-fecf7a27ab99

It could happen from time to time, when switching between networks, I think it's related to API issue:
https://github.com/superhero-com/superhero-wallet/assets/69896204/4692c217-f2b8-4910-9ce3-d2a395d6afe9

lgtm


How to simulate flaky/slow connections with HikariCP?

Hi.
I have a bug in my program that occurs when the MySQL suddenly stops working for a few seconds. This makes the issue a bit difficult to reproduce, so I would like to make a test that simulates the flaky connections to trigger the bug on in a unit test.
The bug occurs when Connection#isValid returns false
I have a mock Connection that returns false for that method call, but the issue is getting this connection inside the connection pool.
How would I go about placing the connection inside the pool?
Is there some other way to simulate flaky connections?

This is a good starting point: https://gist.github.com/brettwooldridge/7564827e45d67e1dc8dd

This is a good starting point: https://gist.github.com/brettwooldridge/7564827e45d67e1dc8dd


Rotate marker on bench view

Some photos have an EXIF tag showing which direction the camera was facing when the photo was taken.
True North
https://openbenches.org/image/fc37ce8a6b4811d8f9ac6a6d816aea76b456c97d/exif
    'GPSImgDirectionRef' => 'T',
    'GPSImgDirection' => '38266/593',

Magnetic North
https://openbenches.org/image/37fc2548dcb4e9e67bae12d53d5549c5f1926467/exif
    'GPSImgDirectionRef' => 'M',
    'GPSImgDirection' => '23607/100',

The direction is found by dividing the two numbers. 38266/593 = 64.5 degrees from North.
Use...
https://github.com/bbecquet/Leaflet.RotatedMarker

As per https://github.com/bbecquet/Leaflet.RotatedMarker/issues/18
The plugin is for True North.  Should we correct Magnet North ones?


[Enhancement] User, createdBy

I'll use feedback only for registered users, therefor I don't want them to input their mail, instead It'd be nice to have a createdBy feature out of the box.

Is this enough for you?
https://github.com/okulbilisim/FeedbackBundle/blob/master/src/Okulbilisim/FeedbackBundle/Entity/Feedback.php#L199

Yes :) Thanks a lot!


Added a prop to reveal the menu from the right side

rightSide = {true} will make the menu appear from the right side, in the offcanvas3D and offcanvasReveal

@shoumma  any thoughts about this?


bug: Small issue of loading position

Describe the bug
The Loading was on the left until the refresh database shows up.
To Reproduce
Steps to reproduce the behavior:

Just go to app.100xdevs.com and refresh.
You will see the loading is positioned on left.

Expected behavior
If the refresh database button is on center the loading must be on the center.
While loading

After loading

Info (please complete the following information):

Brave
v1.66.115

@siinghd Can you look at this?


Avoid new mode

Web mode-solid web

I don't think it works well enough - especially on the servers that I could test this on.


AscentCore - Job titles missing

ENVIRONMENT: production
URL: https://peviitor.ro
Browser: Safari
Device: Laptop
OS: macOS 14 Sonoma
STEPS TO REPRODUCE:

Open URL in browser
Type "AscentCore" in the search bar
Click on "Cauta"
Right-click and select "Inspect"
Copy the Request cURL: https://api.peviitor.ro/v3/search/?q=ascentcore&country=România&page=1
Open Postman and create a new entry with GET request
Click on "Send"

EXPECTED RESULT:
The GET request should return a response with a status of 200 OK and information related to job openings retrieved from the API response should match the information related to job openings listed on the official website of AscentCore and on the peviitor.ro website.
ACTUAL RESULT:
Job titles are missing.

issue fixed


Skipped single-digt numbers

Thank you for this handy tool!
When I try to use TesserOCR to convert the following table from a PDF file, all the single-digit numbers are skipped.

The resulting table is:

| 0 | 1 | 2 |
-- | -- | -- | --
Example\nnumber | FGFR1 Binding\nICso (nM) | FGFR2 Binding\nICso (nM) | FGFR3 Binding\nICso (nM)
None | 44 | ND | None
None | 42 | ND | None
None | 47 | ND | None
None | 157 | ND | 18
None | 52 | ND | None
None | 73 | ND | None
None | 56 | ND | None
10 | 56 | ND | None
11 | 210 | ND | 25
12 | 214 | ND | 32
13 | 245 | ND | 39

Any idea why would this happen? Is there any configuration that can save this issue?

I have had similar experience. It gets some of the single digits. The quality of the scanned pdf I'm attempting process is pretty good to so there must be something else going on. Unsure if the bug is oce language model dependent. I was thinking it was an issue with Tessaract.

This is because of Tesseract character detection as it works fine when I try using other OCR solutions on your image.
Messing with the PSM configuration can be an option as digits are detected when using ocr = TesseractOCR(lang='eng', psm=1)

I tried easyOCR and it gets much better now. Thanks!


Move to API v3 password reset endpoints

Update the password reset flow to use the v3 endpoints.

Ready for review @heroku/api

Thanks!

Thank you again!


do not make an unwrap on the type parameter split

after playing to reproduce the behavior of #4360 I discovered a panic. Here is the quick fix.

Oh it seems you also already catch it https://github.com/rust-analyzer/rust-analyzer/commit/43cedecf68a6686b61fbd244b76c592726d1f211 Sorry I wasn't rebased

Yes, I discovered filing #4360 was exactly how I discovered the issue D:


Whitelist TLDs

I'd like to use Wakatime for tracking only my dev enviroments. Currently the extension doesn't seem to support http://*.test in whitelist. Is this possible in the future?

V3 already supports wildcards on whitelist 👍


UI error

My first install of this plugin.
Steps taken:
-deinstall -> game restart -> re install -> same result as in picture
-Dalamud UI scaling on 2.0 ->  visible part gets smaller, but still only part of it visible as in picture
-changing to window mode with 1920 x 1080 instead of 4k borderless window -> did nothing -> full window -> did nothing
-UI scaling of game itself did nothing as well

looks like there is some weirdness with your Dalamud UI settings. Did you change any of the defaults?

Copied your settings and clicked "save" on the dalamud window.
Bellow you see another plugin which works fine without any squashed bits.


Write-Information results in InformationRecord being added to the Information stream unexpectedly in some cases

Steps to reproduce
First run this in a new PowerShell session with -noprofile:
Write-Information 'Information'
Write-Verbose 'Verbose'
Write-Debug 'Debug'

Note how none of those produce any output, because each of their corresponding $*Preference variables is set to [System.Management.Automation.ActionPreference]::SilentlyContinue by default.
Now run this in the same session:
$ps = [powershell]::Create()
$ps.AddScript(@'
Write-Information 'Information'
Write-Verbose 'Verbose'
Write-Debug 'Debug'
'@).Invoke()
$ps.Streams.Verbose # Empty, as expected
$ps.Streams.Debug # Empty, as expected
$ps.Streams.Information # Not empty, and outputs "Information"...why?

Expected behavior
Both blocks of code would not output anything.
Actual behavior
The second block outputs the following text:
Information

Environment data

Name                           Value
----                           -----
PSVersion                      7.0.3
PSEdition                      Core
GitCommitId                    7.0.3
OS                             Microsoft Windows 10.0.18363
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Some general comments on this: I have a C# project that runs PowerShell. I want to control the streams. When I put logic in place to allow the streams to be controlled, whether or not I have turned the Information stream "on", I get output from that stream, with no metadata to let me know if that output should show up or not. This seems like a bug, because InformationPreference is SilentlyContinue, just like it is for VerbosePreference and DebugPreference.
I have found a workaround for this, but it shouldn't be necessary, and I want to make sure it isn't doing something that I don't want to do. If I set InformationPreference to Ignore, the logic works as expected, and I can turn on Information stream output on demand within my script by using InformationAction on commands where I want that output. That workaround seems to be the only way that I can make the Information stream behave like it does in native PowerShell, but it shouldn't be necessary. Here is the above snippet with the workaround where I get the results that I expected in the first place:
$ps = [powershell]::Create()
$ps.AddScript(@'
$InformationPreference = [System.Management.Automation.ActionPreference]::Ignore
Write-Information 'Information'
Write-Verbose 'Verbose'
Write-Debug 'Debug'
'@).Invoke()
$ps.Streams.Verbose # Empty, as expected
$ps.Streams.Debug # Empty, as expected
$ps.Streams.Information # Not empty, and outputs "Information"...why?

After discussing this in Discord, I bet this is probably due to the desire for Write-Host output to be capturable in the transcript, but if that is the desired result, the implementation is wrong because there is no use of Write-Host here.

Write-Information is by default also capturable in a transcript, even if it never appears on screen. I always assumed that was intentional.

It is not for Write-Host and not for a transcript. The code explicitly is if (preference != ActionPreference.Ignore) - write if not "Ignore". I believe it is by design and changing this would be huge breaking change since events are triggered there for other threads.

I suppose, why be consistent, right? Just because the error, warning, verbose, debug and progress streams can be silenced using System.Management.Automation.ActionPreference.SilentlyContinue, why should the information stream work the same way? That would make too much sense. 🙄

The code is so simple that I can only say it is definitely by design and I don't know why. Perhaps someone from MSFT team knows this history.

@vexx32, the transcript behavior with respect to Write-Information has been fixed (after all, a transcript should not show different output than the console), though I'm not sure in what version exactly, and I'm aware of an associated bug report (still affects Windows PowerShell; see also: #4645).
Let me try to summarize the troubling inconsistency (derived from observation, not source-code analysis):

Unlike with all other streams, SilentlyContinue for stream 6 (Write-Information) does not suppress writing to the stream at the source.

Seemingly, it is unexpectedly left to the host to enforce the silence for display.

This is easy to demonstrate: a redirection of stream 6 succeeds even with -InformationAction SilentlyContinue:
PS> Write-Information info -Infa SilentlyContinue 6>&1 | % { "[$_]" }
[info]  # !! stream output was still produced and redirected to the success stream.

To contrast this with the behavior of the Write-* cmdlets for the other streams:
'Write-Error', 'Write-Warning', 'Write-Verbose', 'Write-Debug', 'Write-Information' | % {
  $stream = ($_ -split '-')[-1]
  $htArgs = if ($stream -in 'Debug', 'Verbose') { # Boolean common parameters
    @{
      $stream = $false
    }
  } else { # enum-based common parameters
    @{
      ($stream + 'Action') = 'SilentlyContinue'
    }
  }
  $out = & $_ @htArgs $stream *>&1
  "redirected $stream`: [$out]"
}

redirected Error: []
redirected Warning: []
redirected Verbose: []
redirected Debug: []
redirected Information: [Information]


Fix pushback

This issue tracks problem described here:
https://github.com/popravich/minihttp/commit/f849057ac0bee661e1d64374334850acc6bf640a#commitcomment-19486411

see @3ea08748b8156e2fe05313e3b8d13add3ffe5132

No, we don't need to buffer data in. The whole point of backpressure is not to read data in.
Solution would be to try read after polling if we haven't done reading before.

Furthermore, it doesn't fix the problem :) I.e. the data is in input buffer, but nobody would trigger the future to actually parse request from there.

It's not an issue any more since tk-bufstream is used. The real issue is #5


linked by target "opencv_flann" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/flann
linked by target "opencv_flann" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/flann
linked by target "opencv_imgproc" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/imgproc
linked by target "opencv_imgproc" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/imgproc
linked by target "opencv_ml" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/ml
linked by target "opencv_ml" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/ml
linked by target "opencv_objdetect" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/objdetect
linked by target "opencv_objdetect" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/objdetect
linked by target "opencv_video" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/video
linked by target "opencv_video" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/video
linked by target "opencv_cudabgsegm" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudabgsegm
linked by target "opencv_cudabgsegm" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudabgsegm
linked by target "opencv_cudafilters" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudafilters
linked by target "opencv_cudafilters" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudafilters
linked by target "opencv_cudaimgproc" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudaimgproc
linked by target "opencv_cudaimgproc" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudaimgproc
linked by target "opencv_cudawarping" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudawarping
linked by target "opencv_cudawarping" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudawarping
linked by target "opencv_imgcodecs" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/imgcodecs
linked by target "opencv_imgcodecs" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/imgcodecs
linked by target "opencv_photo" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/photo
linked by target "opencv_photo" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/photo
linked by target "opencv_shape" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/shape
linked by target "opencv_shape" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/shape
linked by target "opencv_videoio" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/videoio
linked by target "opencv_videoio" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/videoio
linked by target "opencv_cudacodec" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudacodec
linked by target "opencv_cudacodec" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudacodec
linked by target "opencv_highgui" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/highgui
linked by target "opencv_highgui" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/highgui
linked by target "opencv_features2d" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/features2d
linked by target "opencv_features2d" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/features2d
linked by target "opencv_calib3d" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/calib3d
linked by target "opencv_calib3d" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/calib3d
linked by target "opencv_cudafeatures2d" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudafeatures2d
linked by target "opencv_cudafeatures2d" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudafeatures2d
linked by target "opencv_cudalegacy" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudalegacy
linked by target "opencv_cudalegacy" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudalegacy
linked by target "opencv_cudaobjdetect" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudaobjdetect
linked by target "opencv_cudaobjdetect" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudaobjdetect
linked by target "opencv_cudaoptflow" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudaoptflow
linked by target "opencv_cudaoptflow" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudaoptflow
linked by target "opencv_cudastereo" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudastereo
linked by target "opencv_cudastereo" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudastereo
linked by target "opencv_stitching" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/stitching
linked by target "opencv_stitching" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/stitching
linked by target "opencv_superres" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/superres
linked by target "opencv_superres" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/superres
linked by target "opencv_videostab" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/videostab
linked by target "opencv_videostab" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/videostab
CUDA_nppif_LIBRARY (ADVANCED)
linked by target "opencv_cudev" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudev
linked by target "opencv_cudev" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudev
linked by target "opencv_core" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/core
linked by target "opencv_core" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/core
linked by target "opencv_cudaarithm" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudaarithm
linked by target "opencv_cudaarithm" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6d/modules/cudaarithm
linked by target "opencv_flann" in directory D:/vcpkg2/buildtrees/opencv/src/3.4.1-273ea13f6

I have CMake 3.11.2 and reinstalled CUDA 9.2 as you suggested.  It did not make any difference.  I have Windows 10 with latest updates and VS 2017 Pro with latest updates.  I think the CUDA installation is fine because it works with other packages, just not opencv.  I'm kind of bummed I can not figure this one out.

The only difference between your setup and mine is I am using VS 2017
Community. Sorry about not being able to help.
On Wed, May 23, 2018 at 4:28 PM, carmangary<EMAIL_ADDRESS>wrote:

I have CMake 3.11.2 and reinstalled CUDA 9.2 as you suggested. It did not
make any difference. I have Windows 10 with latest updates and VS 2017 Pro
with latest updates. I think the CUDA installation is fine because it works
with other packages, just not opencv. I'm kind of bummed I can not figure
this one out.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vcpkg/issues/2749#issuecomment-391533961,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALNuYMovwcyEDOVlQaDPsSUu6nvSV6h8ks5t1fCigaJpZM4R-N7V
.

Thank you for trying.
From: Jason Juang<EMAIL_ADDRESS>Sent: Thursday, May 24, 2018 1:08 AM
To: Microsoft/vcpkg
Cc: carmangary; Comment
Subject: Re: [Microsoft/vcpkg] OpenCV build with CUDA fails (#2749)
The only difference between your setup and mine is I am using VS 2017
Community. Sorry about not being able to help.
On Wed, May 23, 2018 at 4:28 PM, carmangary<EMAIL_ADDRESS>wrote:

I have CMake 3.11.2 and reinstalled CUDA 9.2 as you suggested. It did not
make any difference. I have Windows 10 with latest updates and VS 2017 Pro
with latest updates. I think the CUDA installation is fine because it works
with other packages, just not opencv. I'm kind of bummed I can not figure
this one out.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/vcpkg/issues/2749#issuecomment-391533961,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALNuYMovwcyEDOVlQaDPsSUu6nvSV6h8ks5t1fCigaJpZM4R-N7V
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vcpkg/issues/2749#issuecomment-391589707, or mute the threadhttps://github.com/notifications/unsubscribe-auth/APt48wb6kvIQkWOT9XG6q99Ul0RTdVf4ks5t1kAlgaJpZM4R-N7V.

Seems like the x64-windows build works if done with 140 toolkit.  x86 does not seem to work at all.  Guess I will just use opencv without cuda until someone can fix it.

I was having a similar issue with OpenCV and Cuda 9.2. In the case of Cuda 9.2, it is only compatible with "Microsoft (R) C/C++ Optimizing Compiler Version 19.13.XXXXX.X for x64" and maybe earlier. For me 19.15.XXXXX.X and newer produced he same error. This, however, is not an issue of opencv, but an issue of cuda. To install a specific version of the VS toolset, do:

vs_installer.exe --quiet --norestart --remove Microsoft.VisualStudio.Component.VC.CMake.Project --add Microsoft.VisualStudio.Component.VC.Tools.14.13

You might want to create your own triplet file like this:

set(VCPKG_TARGET_ARCHITECTURE x64)
set(VCPKG_CRT_LINKAGE dynamic)
set(VCPKG_LIBRARY_LINKAGE dynamic)
set(VCPKG_BUILD_TYPE release)
set(VCPKG_PLATFORM_TOOLSET "v141")
set(VCPKG_PLATFORM_TOOLSET_VERSION "14.13")

Info on Cuda 10. I don't know whether this applies to x86 as well, but I assume it does.

Seems like the x64-windows build works if done with 140 toolkit. x86 does not seem to work at all. Guess I will just use opencv without cuda until someone can fix it.

NVIDIA  does not support 32-but builds for a number of compilers and support libraries. Please see the following documentation:
https://docs.nvidia.com/cuda/cuda-installation-guide-microsoft-windows/index.html#abstract

Similar issue here:
config-x86-windows-out.log

OpenCV [CUDA] option only builds on x64, as some cuda libraries are only available for x64.

From: cagnulein<EMAIL_ADDRESS>Sent: Monday, March 11, 2019 6:45:32 AM
To: Microsoft/vcpkg
Cc: David Cloutier; Comment
Subject: Re: [Microsoft/vcpkg] OpenCV build with CUDA fails (#2749)
Similar issue here:
config-x86-windows-out.loghttps://github.com/Microsoft/vcpkg/files/2951802/config-x86-windows-out.log
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://github.com/Microsoft/vcpkg/issues/2749#issuecomment-471490255, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQKKBjkb9GrEh3ImFBW1c1TUwvllVs_pks5vVjPMgaJpZM4R-N7V.

OpenCV [CUDA] option only builds on x64, as some cuda libraries are only available for x64.
…
________________________________ From: cagnulein<EMAIL_ADDRESS>Sent: Monday, March 11, 2019 6:45:32 AM To: Microsoft/vcpkg Cc: David Cloutier; Comment Subject: Re: [Microsoft/vcpkg] OpenCV build with CUDA fails (#2749) Similar issue here: config-x86-windows-out.loghttps://github.com/Microsoft/vcpkg/files/2951802/config-x86-windows-out.log — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#2749 (comment)>, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AQKKBjkb9GrEh3ImFBW1c1TUwvllVs_pks5vVjPMgaJpZM4R-N7V.

That could be a vcpkg bug/enhancement then.  If some option is not supported for the specified architecture then there should be an "unsupported configuration" error generated instead of just failing.


⚠ Hartman Foundation has degraded performance

In 4dd8ea8, Hartman Foundation (https://gordonhartman.com/) experienced degraded performance:

HTTP code: 200
Response time: 2591 ms

Resolved: Hartman Foundation performance has improved in f97e616.


[Bug]: XSS Vulnerability

What happened?
If you provide the editor with img and the tag contains onerror  attribute it executes JavaScript when the src attribute is invalid.
Sample img input:
<img src="notfound" onerror="alert('Vulnerable!')" />
Version
15.3.0
Angular Version
15.1.0
What browsers are you seeing the problem on?
Chrome
Link to reproduce
stackblitz
Relevant log output
No response
Willing to submit a PR?
None

Hi, Sorry for the delay in response.
The editor itself neither allows pasting javascript directly to be executed nor sanitizes the input, it is the responsibility of the developer to sanitize the input before providing it to the editor.
Or Maybe you could write a pluing to sanitize html before the editor renders it. I am sure that there should be a prosemirror handle to preprocess html before inseted.
Let me know if you have more questions.


governance_action.description content format change request

OS
Your OS: Linux
Versions
The db-sync version (eg cardano-db-sync --version): 2.2.0
Build/Install Method
The method you use to build or install cardano-db-sync: Docker image
Run method
The method you used to run cardano-db-sync (eg Nix/Docker/systemd/none): Docker
Additional context
In governance_action schema documentation is stated that the content of the column in subject is in a readable format.
Problem Report
Looking at some some example records it seems the content of the column is concatenation of a string describing the Governance Action with the serialization of a complex data.
Speaking with @Cmdv I learned that a new specific table for Governance Action description may be added in the future, in that case this could probably be ignored.
Otherwise I would suggest to change the content of the given column in a single JSON somethin like:
{
  "governane_action_description": ${complex_data},
  "any_other_interesting_attribute_1": ${value_1},
  "any_other_interesting_attribute_2": ${value_2},
  ...
}

Thank you

going to close this issue as there seems to already be a discussion on this matter here -> https://github.com/input-output-hk/cardano-db-sync/issues/1553


linux-imx: Enable popular CAN-USB dongles

In order to use CAN on Charge Control C the support for those popular USB dongles must be enabled.

Currently await feedback from customer


bumb to 0.2.2 and CHANGELOG

Following up on the move of Base.adjoint -- we can merge this just before the QuantumOpticsBase deletion of that method. I am marking it as non-breaking because at worst it would just show some warnings about redefined methods.

Let's merge this.


HttpError: Validation Failed on trying to update branch protection

Bug Report
Current Behavior
Trying to update branch protection through context.github fails with validation failed error message.
 try  {
      await context.github.repos.updateBranchProtection({
        owner,
        repo,
        branch,
        required_status_checks,
        enforce_admins,
        required_pull_request_reviews,
        restrictions,
        headers
      })
    } catch (e) {
        context.log.warn(e, `Failed to update branch protection rule on ${branch}`)
    }
}

const headers = {
    "accept": 'application/vnd.github.hellcat-preview+json,application/vnd.github.luke-cage-preview+json,application/vnd.github.zzzax-preview+json'
  }

I am using the above preview header in the request
Expected behavior/code
Branch protection rule to be updated appropriately
Environment

Probot version(s): 9.3.2
Node/npm version: Node 10.16.0 npm 6.9.0
OS: OSX 10.14.5

Forgot to add my permissions for the app:
repository metadata: read
repository administration: read/write
repository contents: read

Can you paste the full error? Can you make sure you are using the latest probot and @octokit/rest version?
WIth the latest version, you can set preview headers more easily:
    mediaType: { previews: ['hellcat', 'luke-cage', 'zzzax'] }

@gr2m I tried running my app with latest probot (v9.3.3) and octokit/rest (16.28.9) but it still fails. Here is the error.

is there more information on the error? The error has a .request property, that's what we need to better understand the cause of your problem

@gr2m
17:37:29.072Z  WARN event: Failed to update branch protection rule on master (id=75cd9270-d328-11e9-8411-4994023d34d1, method=PUT)
  url: https://api.github.com/repos/denang1/mergemate-test/branches/master/protection
  --
  headers: {
    "accept": "application/vnd.github.luke-cage-preview+json",
    "user-agent": "octokit.js/16.28.9 Node.js/10.16.0 (macOS Mojave; x64)",
    "authorization": "token [REDACTED]",
    "content-type": "application/json; charset=utf-8"
  }
  --
  body: {"required_status_checks":{"strict":true,"contexts":["ci/circleci: build"]},"enforce_admins":true,"required_pull_request_reviews":{"required_approving_review_count":1,"dismiss_stale_reviews":true,"require_code_owner_reviews":true,"dismissal_restrictions":{"users":[],"teams":[]}},"restrictions":{"users":[],"teams":[]}}
  --
  request: {
    "validate": {
      "branch": {
        "required": true,
        "type": "string"
      },
      "enforce_admins": {
        "allowNull": true,
        "required": true,
        "type": "boolean"
      },
      "owner": {
        "required": true,
        "type": "string"
      },
      "repo": {
        "required": true,
        "type": "string"
      },
      "required_pull_request_reviews": {
        "allowNull": true,
        "required": true,
        "type": "object"
      },
      "required_pull_request_reviews.dismiss_stale_reviews": {
        "type": "boolean"
      },
      "required_pull_request_reviews.dismissal_restrictions": {
        "type": "object"
      },
      "required_pull_request_reviews.dismissal_restrictions.teams": {
        "type": "string[]"
      },
      "required_pull_request_reviews.dismissal_restrictions.users": {
        "type": "string[]"
      },
      "required_pull_request_reviews.require_code_owner_reviews": {
        "type": "boolean"
      },
      "required_pull_request_reviews.required_approving_review_count": {
        "type": "integer"
      },
      "required_status_checks": {
        "allowNull": true,
        "required": true,
        "type": "object"
      },
      "required_status_checks.contexts": {
        "required": true,
        "type": "string[]"
      },
      "required_status_checks.strict": {
        "required": true,
        "type": "boolean"
      },
      "restrictions": {
        "allowNull": true,
        "required": true,
        "type": "object"
      },
      "restrictions.teams": {
        "type": "string[]"
      },
      "restrictions.users": {
        "type": "string[]"
      }
    }
  }

Thanks, that might in fact be a bug with https://github.com/octokit/request.js/
For the time being, you should be able to do this
octokit.request('/repos/:owner/:repo/branches/:branch/protection', {
        owner,
        repo,
        branch,
        required_status_checks,
        enforce_admins,
        required_pull_request_reviews,
        restrictions,
        mediaType: {
                previews: ['luke-cage']
        }
})

Could you please check if that works for you?

@gr2m Yep that works! Thanks so much for the help!

@gr2m I got the create branch protection working but when I do an update I get a 200 response with no changes to the repo. Do you have any suggestions? Thanks!

Can you share your code? I had a typo in my code above, I missed the PUT

I tried to reproduce the problem here: https://runkit.com/gr2m/probot-probot-1007
I indeed got an error, but I had to log error.errors to understand what the problem was:

Only organization repositories can have users and team restrictions

Is it possible that you run into the same restriction yourself?
Something I'll definitely look into is to set error.message to something more helpful than just Validation Failed 👍


WPF: Zoom is laggy after MapControl is re-created

https://github.com/Mapsui/Mapsui/assets/93271991/bf2cadb8-1851-4e36-b0f9-f45a054f604b
Mapsui Version
4.1.7
Mapsui Platform
WPF
Device
Windows
Describe the bug
I discovered a weird behavior where the zoom is laggy if the MapControl is in a TabItem of a TabConrol and the tabs are dynamically created. This was no problem in Mapsui version 3.
The reason is the re-creation of the MapControl if the tab is re-selected (dynamic creation of tabs). Its the normal behavior of the internal virtualization of TabControl. In addition the state of the Map property is saved and is always assigned as the Map of the MapControl as soon as it gets re-created. If the Map property is always initialized new, the zoom is smooth. The map only is re-created, if a tab with another content (ex TextBlock) also exists.
To Reproduce
To see the effect, switch the tab to the TextBlock and back to MapControl. Sometimes it needs a couple of switches. It seems, that the lag gets worse with each switch/re-creation of the MapControl. Don’t know why.
I attached a sample project
MapsuiTab.zip
https://github.com/Mapsui/Mapsui/assets/93271991/67cb06a7-4b9d-4f07-86ee-f545df222fe0

Thanks for your excellent bug report. I can reproduce the behavior with your sample. The problem also exists in 5.0.0-beta.1.

Inspecting the code I see there is a CustomMap derived from MapControl which is IDisposable, so CustomMap must be disposed. How should that work in this setup where a standard TabControl is used with content defined in xaml?

You are correct, the MapControl is not disposed. Do you think the laggy zoom is related to this?

Indeed, i managed to dispose MapControl via an AttachedProperty as soon as it is released from the TabControl and this seems to solve the issue.
I dont really understand why, do you have an explanation? As i mentioned above, this was no Issue in v3.


Don't call stream.end() on Watch ended by server

This is part of https://github.com/googleapis/nodejs-firestore/pull/564
The changes in #564 to make formattedName() async changed a lot of the timing in the Watch code and uncovered an issue with the way we close streams. We should only call stream.end() if the SDK closes the stream. If the server closes the stream we don't call end() - if we do, we get an exception (that was previously swallowed).
This PR also introduces subclasses for Watch that provide the Target Proto and the Comaprator. This makes it possible to construct these after initialization time and to return a Promise.

I'm gonna leave this unmerged for a bit to give @mikelehen a chance to comment.


Set connection attributes before connection is made

Environment
UPDATE: replaced Latest with master ~mloskot

nanodbc version: Latest master
DBMS name/version: SQL Server 2014
ODBC connection string:
OS and Compiler: MSVC 2017 ( v 15.3)
CMake settings:

Actual behavior
In order to enable bulk copy ( really fast data loads ) using the Microsoft odbc driver you have to enable bcp in the connection attributes.
My attempt was
auto const connection_string = L"Driver={ODBC Driver 13 for SQL Server}; Server=myServer;Database=myDB;Trusted_Connection=Yes";
nanodbc::connection conn(connection_string);
SQLRETURN rc = SQLSetConnectAttr(conn.native_dbc_handle, SQL_COPT_SS_BCP, (SQLPOINTER)SQL_BCP_ON, SQL_IS_INTEGER);

Expected behavior
This does not work. You have to be in bcp mode before you establish the connection.
Here is the documentation and  sample code
https://docs.microsoft.com/en-us/sql/relational-databases/native-client-odbc-extensions-bulk-copy-functions/bcp-init
 // Allocate ODBC connection handle, set BCP mode, and connect.
   retcode = SQLAllocHandle(SQL_HANDLE_DBC, henv, &hdbc1);
   if ( (retcode != SQL_SUCCESS_WITH_INFO) && (retcode != SQL_SUCCESS)) {
      printf("SQLAllocHandle(hdbc1) Failed\n\n");
      Cleanup();
      return(9);
   }

   retcode = SQLSetConnectAttr(hdbc1, SQL_COPT_SS_BCP, (void *)SQL_BCP_ON, SQL_IS_INTEGER);
   if ( (retcode != SQL_SUCCESS_WITH_INFO) && (retcode != SQL_SUCCESS)) {
      printf("SQLSetConnectAttr(hdbc1) Failed\n\n");
      Cleanup();
      return(9);
   }

   // Sample uses Integrated Security. Create SQL Server DSN using Windows NT authentication.
   retcode = SQLConnect(hdbc1, (UCHAR*)"Test", SQL_NTS, (UCHAR*)"", SQL_NTS, (UCHAR*)"", SQL_NTS);
   if ( (retcode != SQL_SUCCESS) && (retcode != SQL_SUCCESS_WITH_INFO) ) {
      printf("SQLConnect() Failed\n\n");
      Cleanup();
      return(9);
   }

   // Initialize the bulk copy.
   retcode = bcp_init(hdbc1, "BCPDate", "BCPODBC.bcp", NULL, DB_IN);
   if ( (retcode != SUCCEED) ) {
      printf("bcp_init(hdbc1) Failed\n\n");
      Cleanup();
      return(9);

Currently, it is not possible. The connection constructor and connect() method allocate and open connection in one go.
New operation will need to be extracted, eg. connection::allocate() to allow flow along these lines:
connection c1;
SQLSetConnectAttr(c1.native_dbc_handle(), ...);
c1.open(...);

I've changed this issue to feature request/suggestion.

This issue was moved to nanodbc/nanodbc#2


Replacement for #1017

This implementation is aware for functions and methods when checking argument counts.
Fixes #1051

@astrelsky Please verify this corrects your issue.
@Christopher-Chianelli Please look over this and review to see if it is a reasonable replacement.

@astrelsky Please verify this corrects your issue. @Christopher-Chianelli Please look over this and review to see if it is a reasonable replacement.

Seems to work.

@marscher  This one should be ready for review.  I likely should add a note about it in the changelog.

Thanks for the provided fix and testing @Thrameos and @Christopher-Chianelli, @astrelsky


bug: icons not appearing in windows terminal

Did you check the docs and existing issues?

[X] I have read the docs
[X] I have searched the existing issues

Neovim version (nvim -v)
0.10.0
Operating system/version
Win11
Describe the bug
Icons looks weird (mini.icons)

What is the severity of this bug?
minor (annoyance)
Steps To Reproduce
I have following lua file included by Lazy
oil-nvim.txt
Expected Behavior
I expect to see real icons. Currently it looks like icons have very low width
Directory structure
Anything
Repro
-- save as repro.lua
-- run with nvim -u repro.lua
-- DO NOT change the paths
local root = vim.fn.fnamemodify("./.repro", ":p")

-- set stdpaths to use .repro
for _, name in ipairs({ "config", "data", "state", "runtime", "cache" }) do
  vim.env[("XDG_%s_HOME"):format(name:upper())] = root .. "/" .. name
end

-- bootstrap lazy
local lazypath = root .. "/plugins/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)

-- install plugins
local plugins = {
  "folke/tokyonight.nvim",
  {
        "stevearc/oil.nvim",
        config = function()
            require("oil").setup({
                dependencies = { 'echasnovski/mini.icons' },
                -- dependencies = { 'nvim-tree/nvim-web-devicons' },
                opts = {
                  default_file_explorer = true,
                  delete_to_trash = true,
                  watch_for_changes = true,  -- Set to true to watch the filesystem for changes and reload oil

                  columns = {
                    "icon",
                    -- "permissions",
                    -- "size",
                    -- "mtime",
                  },

                  keymaps = {
                    ["<CR>"] = "actions.select",
                    ["<C-t>"] = { "actions.select", opts = { tab = true }, desc = "Open the entry in new tab" },
                    ["<C-p>"] = "actions.preview",
                    ["<C-c>"] = "actions.close",
                    ["<C-l>"] = "actions.refresh",
                    ["-"] = "actions.parent",
                    ["_"] = "actions.open_cwd",
                    ["`"] = "actions.cd",
                    ["~"] = { "actions.cd", opts = { scope = "tab" }, desc = ":tcd to the current oil directory" },
                    ["gs"] = "actions.change_sort",
                    ["gx"] = "actions.open_external",
                    ["g."] = "actions.toggle_hidden",

                    --["<C-h>"] = { "actions.select", opts = { horizontal = true }, desc = "Open the entry in a horizontal split" },
                    --["<C-s>"] = { "actions.select", opts = { vertical = true }, desc = "Open the entry in a vertical split" },
                    --["g?"] = "actions.show_help",
                    --["g\\"] = "actions.toggle_trash",
                  },
                  -- Set to false to disable all of the above keymaps
                  use_default_keymaps = true,
                },
            })
        end,
  },
  {
    'echasnovski/mini.nvim',
    config = function()
      -- Better Around/Inside textobjects
      --
      -- Examples:
      --  - va)  - [V]isually select [A]round [)]paren
      --  - yinq - [Y]ank [I]nside [N]ext [']quote
      --  - ci'  - [C]hange [I]nside [']quote
      require('mini.ai').setup { n_lines = 500 }

      -- Add/delete/replace surroundings (brackets, quotes, etc.)
      --
      -- - saiw) - [S]urround [A]dd [I]nner [W]ord [)]Paren
      -- - sd'   - [S]urround [D]elete [']quotes
      -- - sr)'  - [S]urround [R]eplace [)] [']
      require('mini.surround').setup()
      require('mini.icons').setup()

      -- Simple and easy statusline.
      --  You could remove this setup call if you don't like it,
      --  and try some other statusline plugin
      local statusline = require 'mini.statusline'
      -- set use_icons to true if you have a Nerd Font
      statusline.setup { use_icons = vim.g.have_nerd_font }

      -- You can configure sections in the statusline by overriding their
      -- default behavior. For example, here we set the section for
      -- cursor location to LINE:COLUMN
      ---@diagnostic disable-next-line: duplicate-set-field
      statusline.section_location = function()
        return '%2l:%-2v'
      end

      -- ... and there is more!
      --  Check out: https://github.com/echasnovski/mini.nvim
    end,
  }
  -- add any other plugins here
}
require("lazy").setup(plugins, {
  root = root .. "/plugins",
})

vim.cmd.colorscheme("tokyonight")
-- add anything else here

Did you check the bug with a clean config?

[X] I have confirmed that the bug reproduces with nvim -u repro.lua using the repro.lua file above.

Sorry to ask, but do you have any of the Nerd Fonts installed?

@keyclicker Well I have some installed on system, but nowhere in neovim config I specified any. So it shouldn't effect things, right?
Or is it a requirement? I didn't see it in the readme

You should install one of this fonts as your terminal emulator font.
(I guess it's Windows Terminal in your case.)

I installed this one, but still same result

As previously commented, this looks like you haven't set up your terminal to use a patched font. I can't speak to how you would do this on Windows, but here's how you can verify if it's working: copy the glyph below and paste it into your terminal (in the prompt is fine, doesn't have to be in neovim). If you see a circle with a check, your font is working. If not, your font is not set up properly.


It should look like this:

Well, it looks fine

Iiiinteresting. In neovim, what do you see if you run this command
:=require("mini.icons").get("file", "test.lua")

Here:

Well, that is strange that it appears to work in your terminal but doesn't work in Neovim. I don't have any other debugging ideas, but at this point it is also very clearly nothing to do with oil.nvim. You could try posting an issue on mini.nvim about the problem, including the debugging steps you've already taken with pasting the icon in the terminal and the output of :=require("mini.icons").get("file", "test.lua")

It turns out that specific font has something to do with the issue (MesloLGS NF)
After installing another one (FiraCodeNerdFont), issue seems to be resolved.
Thanks for your help :)


Pull hub contents from database, have editing UI

It's currently a config file which isn't ideal.

Hub registration is automatic now.


When I switch the project / language, the current decision is still visible

When I change the language / project in the drop down menu on top, the current edit remains from the previous selection. Only when going to the next edit, it changes to an edit from the newly selected language / project.
Expected behavior: when I change the language / project, an edit from the newly selected language / project should be shown.

The duplicate #134 is fixed. It's currently live


Power Automate Visual in Power BI - run with user's connections

Kindly provide some information in the documentation that describes how we can set up this visual so that it runs with the logged in Power BI user's credentials and connections and not the credentials and connections of the Power Automate flow author.

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

ID: de472a84-f62c-d01c-a8b2-e6ea168a222d
Version Independent ID: da8c0056-7e3d-fc14-c5a4-1bd3bab573de
Content: Create a Power Automate visual for Power BI (preview) - Power BI
Content Source: powerbi-docs/create-reports/power-bi-automate-visual.md
Service: powerbi
Sub-service: pbi-reports-dashboards
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Good question! I'll look into it and get back to you. Might not be immediate. I suggest asking the community, https://community.powerbi.com/

Hi, @salilathalye -- you are correct, this is not possible today, the flow runs in the owner's context currently. There's a backlog item to allow manually run flows from the PowerBI visual which would allow running the flow in the users credential context, but no exact timeline for this. Hope that helps!


Generated extension functions are weakly typed

Consider the README example:
[pyfn(m, "sum_as_string")]
fn sum_as_string_py(a:i64, b:i64) -> PyResult<String>

Here is what happens when this function is called with non-int arguments:
>>> from rust2py import sum_as_string
>>> sum_as_string(1, 2)  # good
'3'

>>> sum_as_string(10**100, 2)  # good
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OverflowError: int too big to convert

>>> sum_as_string([], [])  # good
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: int() argument must be a string, a bytes-like object or a number, not 'list'

>>> sum_as_string('1', 2)  # bad
'3'

>>> sum_as_string(1.9, 2.9)  # bad
'3'

Generally Python functions that expect int argument raise TypeError when fed strings or floats. This helps to catch some programming errors.
>>> range('42')  # good
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: 'str' object cannot be interpreted as an integer

>>> range(42.9)  # good
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: 'float' object cannot be interpreted as an integer

I think it would be more consistent if generated extension functions behaved the same way.

thanks! this is definitely bug.

So it seems relevant that I'm running this example on Windows (target_pointer_width="64", target_os="windows"), and that the argument type is i64 and not, say, i32.
The problem appears to be here: https://github.com/PyO3/pyo3/blob/63a2066a39a6389f24ed1d5acda322425ade0937/src/objects/num3.rs#L121-L130
PyLong_Check(x) is roughly equivalent to isinstance(x, int), and PyNumber_Long(x) is analagous to int(x), hence the frivolous conversion.
This code was there since it was written in https://github.com/dgrunwald/rust-cpython/commit/55ea6cc85b53566494ae550020b3dcea03de1fc0#diff-2eab662fc2799e2bdab71b4844e11090R155
I wonder if this whole else branch should just return TypeError instead.

but ffi::PyLong_Check(ptr) should fail for string, I guess

PyLong_Check() returns 0 on a string, and then PyNumber_Long() attempts to parse it.

Unexpected :)

Found another similar instance of weak-typedness that happens for a different reason:
#[pyfn(m, "take_i32")]
fn take_i32(a: i32) -> PyResult<()> {
    println!("my arg is {}", a);
    Ok(())
}

>>> take_i32(42)  # good
my arg is 42

>>> take_i32('42')  # good
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
TypeError: an integer is required (got type str)

>>> take_i32(42.9)  # bad
my arg is 42

This happens because in https://github.com/PyO3/pyo3/blob/63a2066a39a6389f24ed1d5acda322425ade0937/src/objects/num3.rs#L48-L57
, the call to PyLong_AsLong() is equivalent to calling __int__() method on an object. Strings don't have it but floats do.

@Vlad-Shcherbina i think this should be fixed now?

Yes, it's fixed for Python 3.


check if data already Binary

Hi , I have added the necessary code that checks if data , if it is already in binary , then return it in same format.

Hey @UtkarshMish ,
Thank you very much for this PR. I implemented it the same way, but a little in another place here https://github.com/roman-right/beanie/pull/168


one test depend on the network

I am trying to enable the tests in nixpkgs for this package (cf https://github.com/NixOS/nixpkgs/issues/169293).
I am almost done but current tests fail with:
Success ||      sqlite.db :delete delete multiple keys with dict for each conditions. V2
Fail    ||      sqlite.db :select .... pre
            ...-lua5.1-plenary.nvim-scm-1/share/lua/5.1/plenary/job.lua:106: curl: Executable not found
            stack traceback:
                ...-lua5.1-plenary.nvim-scm-1/share/lua/5.1/plenary/job.lua:106: in function 'new'
                ...lua5.1-plenary.nvim-scm-1/share/lua/5.1/plenary/curl.lua:254: in function 'get'
                /build/sqlite.lua-ade5bc2/test/auto/db_spec.lua:554: in function </build/sqlite.lua-ade5bc2/test/auto/db_spec.lua:552>
                [C]: in function 'xpcall'
                ...a5.1-plenary.nvim-scm-1/share/lua/5.1/plenary/busted.lua:74: in function 'call_inner'
                ...a5.1-plenary.nvim-scm-1/share/lua/5.1/plenary/busted.lua:175: in function 'it'
                /build/sqlite.lua-ade5bc2/test/auto/db_spec.lua:552: in function </build/sqlite.lua-ade5bc2/test/auto/db_spec.lua:548>
                [C]: in function 'xpcall'
                ...a5.1-plenary.nvim-scm-1/share/lua/5.1/plenary/busted.lua:74: in function 'call_inner'
                ...a5.1-plenary.nvim-scm-1/share/lua/5.1/plenary/busted.lua:132: in function 'describe'
                /build/sqlite.lua-ade5bc2/test/auto/db_spec.lua:548: in function </build/sqlite.lua-ade5bc2/test/auto/db_spec.lua:8>
                [C]: in function 'xpcall'
                ...a5.1-plenary.nvim-scm-1/share/lua/5.1/plenary/busted.lua:74: in function 'call_inner'
                ...a5.1-plenary.nvim-scm-1/share/lua/5.1/plenary/busted.lua:120: in function 'describe'
                /build/sqlite.lua-ade5bc2/test/auto/db_spec.lua:8: in main chunk
                [builtin#25]: at 0x7ffff7dd7ad0
                [C]: in function 'pcall'
                ...a5.1-plenary.nvim-scm-1/share/lua/5.1/plenary/busted.lua:221: in function 'run'
                [string ":lua"]:1: in main chunk

            stack traceback:
                /build/sqlite.lua-ade5bc2/test/auto/db_spec.lua:554: in function </build/sqlite.lua-ade5bc2/test/auto/db_spec.lua:552>

Fail    ||      sqlite.db :select return everything with no params
            ./lua/sqlite/assert.lua:28: sqlite.lua: can not execute select, posts doesn't exists.

indeed curl is not available because we dont want network access when building/testing from the nix sandbox. Is there a way to skip this test or just add these files to the repository ? It's not the download that is tested but the decoding capability if I understand correctly.
    it(".... pre", function()
      if luv.fs_stat "/tmp/posts" == nil then
        curl.get("https://jsonplaceholder.typicode.com/posts", { output = "/tmp/posts" })
        curl.get("https://jsonplaceholder.typicode.com/users", { output = "/tmp/users" })
      end

Once I get the test passing in nixpkgs, maybe I can port it to the flake if that's of interest

🤔 perhaps you could check if curl exists and then if so do this test else skip.

fixed in https://github.com/tami5/sqlite.lua/pull/141

also note that I added it to https://github.com/NixOS/nixpkgs/issues/169293 . The package seems to fail on darwin but I haven't looked why. Maybe because I hardcoded the .so extension


Add tariffID in OCPI Settings

As spoken, we need to continue splitting the Validators schemas for Setting.
Many are still to be collected. Let me know if I must continue this migration or continue with the tariffID in the other UIs.

Continue with the tariff ID.
Thanks!


Reload page and switching tab causes crash

I noticed that if you reload the page and try to navigate to another tab, the browser crashes and leaves us with the following bokeh error:
RuntimeError: Models must be owned by only a single document,
ImportedStyleSheet(id='p1388', ...) is already in a doc

Yes this has always been the case, we suspect it is a problem with how rye serves the app


when run todo.go,get error msgs like below:

thx for your porject, but when i clone your project and follow the installions,at the last  got this error msg:
➜  go-vue-todos git:(master) go run todo.go
todo.go:8:2: cannot find package "github.com/labstack/echo/engine/standard" in any of:
/usr/local/go/src/github.com/labstack/echo/engine/standard (from $GOROOT)
/Users/allenwu/GoProjects/src/github.com/labstack/echo/engine/standard (from $GOPATH)
I had checked issues and pr,but nothing about the error.

It seems that echo has changed something.
I commented this:
//"github.com/labstack/echo/engine/standard"
and changed
e.Run(standard.New(":8080"))
to
e.Start(":8080")

I left a pull request and I made changes @nowilike mentioned.

This has since been updated.


Various UI improvements and a bug fix.

Bug fixes:

fix the amount and fee values not correctly updating in send page when pressing onSubmit

UI improvements:

Show addresses in this format now  "txch1fz...agzfzg" which is responsive to the width
Added masked inputs for fee or amount inputs which prevent inputing a smaller decimal then decimals or default of 12.
Added a warning to confirmation dialog if the users fee is very high

Went over the comments, removed and reverted not needed changes. Fixed the fee is to high warning to use mojo's now as well after the merge. Also fixed the copybox to have a value and dispValue, otherwise the copy will use the short format address.


add missing .swcrc for typescript example

@LyhourChhen the typescript example is working at the moment without this file. This package detects a .tsconfig file at the root so understand that the typescript loader is used.


Node graph

Closes #1402
Closes #1403

Coverage decreased (-0.2%) to 82.201% when pulling f661359ed428b5e6d734141599e10f6c8e013c16 on na3d:node-graph into d2f166b38c1d01c2f8263f155334e7735eab6d22 on linode:master.

Coverage decreased (-0.2%) to 82.201% when pulling 8263c4bc3d6558291b50fb0e91d546831bd50b1d on na3d:node-graph into d2f166b38c1d01c2f8263f155334e7735eab6d22 on linode:master.


disabling rules that are set inside of a preset?

Hi,
I have a .jscsrc in my project root structured like so:
{
  "preset": "airbnb"
}

I'm using this preset because most of the rules apply to me, however I wish to override a particular rule, validateIndentation.
Per the JSCS docs, there's no "disable"/false/etc. value for this rule. Since it's set in the preset, it seems there's no way for me to "unset" it.
Is there a way to override this value as set in the preset? I'd like to simply disable it.

Hey @tconroy, there's always the ability to set null or false for any rule. It's not the doc for each individual rule since you can do it for all of them.
See http://jscs.info/overview#presets

interesting, not sure why setting false is not working for me, but setting null works.
Thanks for your help, apologies for not reading the docs at a higher level. :)
Cheers! :+1:

false should work too (added in later, so maybe update your version)


Make sure the hostname does not get superseeded by the transient one

We are setting the hostnane via ignition by editing /etc/hostname, that set the static hostname correctly, but it gets superseded by the transient one.
I tried forcing the transient one with DHCP_HOSTNAME=hostname in ifcfg files, but to no avail.

However hostnamectl set-hostname <hostname> seems to persist, so will try with that.

Fixed in the last pushed to staging, thanks to the command being applied.

With the above command, it survives reboots, but not updates, the static transient name comes back!

@mysticaltech  I had not looked into this before, but if read hostnamectl(1) correctly, your command only sets the "pretty" hostname, right?
Does hostnamectl --static set-hostname <hostname> survive upgrades? I don't have a long-running cluster to test atm :D

Am not sure if I have tested the above with --static. But without it, it survived reboots, but not upgrades!
However have found this resource just yesterday, it could have the solution for this, basically including the hostname in /etc/hosts and adding preserve_hostname: true to /etc/cloud/cloud.cfg.

Interesting... https://man7.org/linux/man-pages/man1/hostnamectl.1.html

However have found this resource just yesterday, it could have the solution for this, basically including the hostname in /etc/hosts and adding preserve_hostname: true to /etc/cloud/cloud.cfg, on top hostnamectl.

Ah yes, that sounds about right! Don't know anything about microos implementation, but I did need preserve_hostname with cloud-init on another platform for the same behavior (Debian VMs with Proxmox VEs cloud-init implementation)

Yeah, me too. MicroOS does do cloud-init, so maybe that is what resets the hostname on upgrades?! No idea, but worth a shot hehe.

Just tried with hostnamectl set-hostname --static let's see in a few days!
About the rest, the system does not have an etc/cloud directory. Was also not able to find cloud.cfg on the filesystem.

Otherwise, we can run that command at boot time and that's it.

I can confirm that the image we use doesn't include cloud-init. It is only available in the OpenStack flavor.

This is what happen, it did it again, at some point the $HOST global variable takes the name of the transient hostname that shows up out of the blue.

Basically, by doing that, we would force the value of the static hostname and the HOST global variable, the rest, we do not care. Personally, I believe that to be good enough.

As soon as I can, will also try editing the /etc/hosts file too, which is something we have not tried before.

Will try adding <IP_ADDRESS> <name> at the top of the hosts file on top of issuing hostname set-hostname, maybe that would solve it for us once and for all.

Should be fixed now, turns out we needed to set NETCONFIG_NIS_SETDOMAINNAME to "no" in /etc/sysconfig/network/config.


CSS is broken after update

I am opening new issue related to css.
main.scss
// Base
@import '../node_modules/bootstrap/dist/css/bootstrap.css';
@import "../node_modules/uikit/dist/css/uikit.css";
@import "../node_modules/element-ui/lib/theme-chalk/index.css";
@import "base/fonts";
@import "base/variables";
@import "base/mixins";
// Components
@import "components/login";
@import "components/navbar";
@import "components/index";
@import "components/custom_uikit";
@import "components/custom_elementui";
@import "components/images";
@import '~vuejs-noty/dist/vuejs-noty.css';
@import '../node_modules/vue2-dropzone/dist/vue2Dropzone.min.css';
@import '../node_modules/highlight.js/styles/vs.css';
@import '../node_modules/codemirror/lib/codemirror.css';
@import '../node_modules/summernote/dist/summernote-bs4.css';

app.vue
<template>

    <vue-dropzone ref="myVueDropzone" id="dropzone" :options="dropzoneOptions" @vdropzone-file-added="processFile"></vue-dropzone>

</template>

dropzoneOptions: {
          url: 'https://httpbin.org/post',
          maxFilesize: 5,
          thumbnailWidth: 150,
          headers: { "My-Awesome-Header": "header value" }
}

HTML output:

66.3 KB

c-294-milk-thistle.jpg

    <svg width="54px" height="54px" viewBox="0 0 54 54" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:sketch="http://www.bohemiancoding.com/sketch/ns">      <title>Check</title>      <defs></defs>      <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" sketch:type="MSPage">        <path d="M23.5,31.8431458 L17.5852419,25.9283877 C16.0248253,24.3679711 13.4910294,24.366835 11.9289322,25.9289322 C10.3700136,27.4878508 10.3665912,30.0234455 11.9283877,31.5852419 L20.4147581,40.0716123 C20.5133999,40.1702541 20.6159315,40.2626649 20.7218615,40.3488435 C22.2835669,41.8725651 24.794234,41.8626202 26.3461564,40.3106978 L43.3106978,23.3461564 C44.8771021,21.7797521 44.8758057,19.2483887 43.3137085,17.6862915 C41.7547899,16.1273729 39.2176035,16.1255422 37.6538436,17.6893022 L23.5,31.8431458 Z M27,53 C41.3594035,53 53,41.3594035 53,27 C53,12.6405965 41.3594035,1 27,1 C12.6405965,1 1,12.6405965 1,27 C1,41.3594035 12.6405965,53 27,53 Z" id="Oval-2" stroke-opacity="0.198794158" stroke="#747474" fill-opacity="0.816519475" fill="#FFFFFF" sketch:type="MSShapeGroup"></path>      </g>    </svg>

    <svg width="54px" height="54px" viewBox="0 0 54 54" version="1.1" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:sketch="http://www.bohemiancoding.com/sketch/ns">      <title>Error</title>      <defs></defs>      <g id="Page-1" stroke="none" stroke-width="1" fill="none" fill-rule="evenodd" sketch:type="MSPage">        <g id="Check-+-Oval-2" sketch:type="MSLayerGroup" stroke="#747474" stroke-opacity="0.198794158" fill="#FFFFFF" fill-opacity="0.816519475">          <path d="M32.6568542,29 L38.3106978,23.3461564 C39.8771021,21.7797521 39.8758057,19.2483887 38.3137085,17.6862915 C36.7547899,16.1273729 34.2176035,16.1255422 32.6538436,17.6893022 L27,23.3431458 L21.3461564,17.6893022 C19.7823965,16.1255422 17.2452101,16.1273729 15.6862915,17.6862915 C14.1241943,19.2483887 14.1228979,21.7797521 15.6893022,23.3461564 L21.3431458,29 L15.6893022,34.6538436 C14.1228979,36.2202479 14.1241943,38.7516113 15.6862915,40.3137085 C17.2452101,41.8726271 19.7823965,41.8744578 21.3461564,40.3106978 L27,34.6568542 L32.6538436,40.3106978 C34.2176035,41.8744578 36.7547899,41.8726271 38.3137085,40.3137085 C39.8758057,38.7516113 39.8771021,36.2202479 38.3106978,34.6538436 L32.6568542,29 Z M27,53 C41.3594035,53 53,41.3594035 53,27 C53,12.6405965 41.3594035,1 27,1 C12.6405965,1 1,12.6405965 1,27 C1,41.3594035 12.6405965,53 27,53 Z" id="Oval-2" sketch:type="MSShapeGroup"></path>        </g>      </g>    </svg>

Screening:

#430

Can you show me your options and how you're importing the css? Are you applying any css overrides? Do you always experience the incorrect behaviour?

Can you try adding import 'vue2-dropzone/dist/vue2Dropzone.min.css' after the initial import?

Can you try adding import 'vue2-dropzone/dist/vue2Dropzone.min.css' after the initial import?

updated the issue.

can confirm that this stopped working with 3.5.5
import DropZone from 'vue2-dropzone'
import 'vue2-dropzone/dist/vue2Dropzone.css'

and using the .min version messes up the styling

It looks like dropzone/dist/dropzone.css doesn't get included anymore. Adding import 'dropzone/dist/dropzone.css', or in the example above, @import '../node_modules/dist/dropzone.css'; seems to fix it.

Ok here goes 3.5.6-alpha.0
Had to shuffle around my importing of the dropzone.css having moved from less to plain ol' css to fit with how rollup-plugin-css-only wants to work

fixed now. thank you @rowanwins

FYI vue2-dropzone/dist/vue2Dropzone.css is still missing in 3.5.6 so only the .min version is available, also the styling seems a bit different using the minified version compared to 3.5.2

In case if anyone has the same issue, you need to give your element .dropzone and .vue-dropzone classes.


Mistake when skipping images.

Hi @fredzzhang,
We have a tricky problem.
            if len(x_keep) == 0:
                ho_queries.append(torch.zeros(0, self.repr_size, device=device))
                paired_indices.append(torch.zeros(0, 2, device=device, dtype=torch.int64))
                prior_scores.append(torch.zeros(0, 2, self.num_verbs, device=device))
                object_types.append(torch.zeros(0, device=device, dtype=torch.int64))
                positional_embeds.append({})
                continue

The absence of human is dealt with here. （x_keep==0）
https://github.com/fredzzhang/pvic/blob/b02d77ee08dd24a875ba1db2e9ca7eb8b15a6252/transformers.py#L179
        k_p = self.q_attn_kpos_proj(q_pos["box"])

When x_keep==0 is an empty dictionary, it results in:
    cc = self.clipdecoder(
  File "/root/miniconda3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
  File "/root/autodl-tmp/pvicx/transformers.py", line 905, in forward
    pair = q_pos["pair_spatial"]
KeyError: 'pair_spatial'

Here "pair_spatial" denotes the features formed by the concatenation of human and object (from DETR). The feature encounters x_keep==0 and reports an error. We have found that your positional_embeds will also have x_keep==0, but your code works fine.
We try to rewrite positional_embeds.append({}) as a tensor type for positional_embeds.append(torch.zeros(0, 1, self.repr_size, device=device)), but this null tensor causes subsequent code to continue to report errors. How should I modify this part of the code to work correctly?

Hi @yaoyaosanqi,
The zero-size queries are handled here in the TransformerDecoder class, and should not proceed into the TransformerDecoderLayer class.
Fred.

Thanks, our model works fine.


Fix vulnerability in org.eclipse.parsson:parsson

org.eclipse.parsson:parsson:jar:1.1.1 in test

CVE-2023-4043, severity CWE-20: Improper Input Validation (7.5)

Vulnerability is typically introduced via transitive test dependency exasol-test-containers:
\- com.exasol:exasol-testcontainers:jar:6.6.2:test
   \- com.exasol:bucketfs-java:jar:3.1.0:test
      \- org.eclipse.parsson:parsson:jar:1.1.1:test

Was fixed with #42.
Uses https://central.sonatype.com/artifact/org.eclipse.parsson/parsson/1.1.4 which does not have the vulnerability anymore.


Move from mcstats.org to bstats.org for Metrics

The frontend of the former is always down.

Closed by 87ad8701857bf2cdc3d2d2cd9e3ec79ea46421b1.


Chart tab switching to scroll

when opening time frame dropdown

without dropdown

It seems only appears on Windows OS

It seems only appears on Windows OS

On OSX I've got horrizontal scrollbar poping

:wave:


starting of clone work item type

For issue #13

Hi,
I was googling and came across this.  Thanks for adding this feature.  How do I use azure-devops-process-cli?

it's just a dotnet core command line app. Just install and run it :)
if you have any questions let me know

Thanks I will :)

thanks for the awesome feature! is there an official eta for this to rollout?


Google Cloud functions framework not working when upgrading Nx from 17.0.3 -> 17.1.3

Running a cloud function used to work with v17.0.x
npx @google-cloud/functions-framework --source=dist/apps/cloud-functions --target=CloudFunctions

Function 'CloudFunctions' is not defined in the provided module.
Did you specify the correct target function to execute?
Could not load the function, shutting down.

From what I realized: the build in the dist is different between the two versions:
Nx Report (17.0.3):
 Node   : 20.9.0
   OS     : darwin-arm64
   npm    : 10.2.4

   nx (global)        : 17.0.3
   nx                 : 17.0.3
   @nx/js             : 17.0.3
   @nx/jest           : 17.0.3
   @nx/linter         : 17.0.3
   @nx/eslint         : 17.0.3
   @nx/workspace      : 17.0.3
   @nx/angular        : 17.0.3
   @nx/cypress        : 17.0.3
   @nx/devkit         : 17.0.3
   @nx/esbuild        : 17.0.3
   @nx/eslint-plugin  : 17.0.3
   @nx/nest           : 17.0.3
   @nx/node           : 17.0.3
   @nrwl/tao          : 17.0.3
   @nx/web            : 17.0.3
   @nx/webpack        : 17.0.3
   typescript         : 5.1.6
   ---------------------------------------
   Community plugins:
   @nx-extend/gcp-functions : 10.0.1

Compiled version before update (17.0.3):
/******/ (() => { // webpackBootstrap
/******/ 	"use strict";
var __webpack_exports__ = {};
// This entry need to be wrapped in an IIFE because it uses a non-standard name for the exports (exports).
(() => {
var exports = __webpack_exports__;

Object.defineProperty(exports, "__esModule", ({ value: true }));
exports.CloudFunctions = void 0;
const { foo = 'testBar' } = process.env;
const CloudFunctions = async (req, res) => {
    res.status(200).send(foo);
};
exports.CloudFunctions = CloudFunctions;

})();

var __webpack_export_target__ = exports;
for(var i in __webpack_exports__) __webpack_export_target__[i] = __webpack_exports__[i];
if(__webpack_exports__.__esModule) Object.defineProperty(__webpack_export_target__, "__esModule", { value: true });
/******/ })()
;
//# sourceMappingURL=main.js.map

Nx Report (17.1.3):
 Node   : 20.9.0
   OS     : darwin-arm64
   npm    : 10.2.4

   nx (global)        : 17.1.3
   nx                 : 17.1.3
   @nx/js             : 17.1.3
   @nx/jest           : 17.1.3
   @nx/linter         : 17.1.3
   @nx/eslint         : 17.1.3
   @nx/workspace      : 17.1.3
   @nx/angular        : 17.1.3
   @nx/cypress        : 17.1.3
   @nx/devkit         : 17.1.3
   @nx/esbuild        : 17.1.3
   @nx/eslint-plugin  : 17.1.3
   @nx/nest           : 17.1.3
   @nx/node           : 17.1.3
   @nrwl/tao          : 17.1.3
   @nx/web            : 17.1.3
   @nx/webpack        : 17.1.3
   nx-cloud           : 16.5.2
   typescript         : 5.2.2
   ---------------------------------------
   Community plugins:
   @nx-extend/gcp-functions : 10.0.1

Compiled version after update (17.1.3):
/******/ (() => { // webpackBootstrap
/******/ 	"use strict";
var __webpack_exports__ = {};
// This entry need to be wrapped in an IIFE because it uses a non-standard name for the exports (exports).
(() => {
var exports = __webpack_exports__;

Object.defineProperty(exports, "__esModule", ({ value: true }));
const { foo = 'testBar' } = process.env;
const CloudFunctions = async (req, res) => {
    res.status(200).send(foo);
};
exports.CloudFunctions = CloudFunctions;

})();

/******/ })()
;
//# sourceMappingURL=main.js.map

Could you elaborate a bit more? What are the differences, what version of nx-extend (run nx report).
PS: There is also a runner inside the nx-extend package that can run all your functions instead of only one at a time,

@TriPSs Updated my original answer.
Will check the runner out thanks! is it part of the same package or a different one?

It is, you can generate the runner project with nx g @nx-extend/gcp-functions:init-runner, this will generate a project with an main.ts file where you can import all your functions, note: the runner uses the deploy target of the project to set it up correctly (for pub/sub, bucket event or http, see the code here).
Regarding your issue: could it be that something within your tsconfig.json changed that caused the difference in ouput or is everything the same but only the nx version difference? Will check what Nx did with the webpack package as the build of gcp-functions uses that one to build.

Createing a completely brand new project - same error.
Will give your runner a try, thank you!

Could you also give it a try typescript: 5.1.6 (same version when the build was still ok)

Also wondering if it works if you do the following:
const functions = require('@google-cloud/functions-framework');

functions.http('helloWorld', (req, res) => {
  res.send('Hello, World');
});

Could you also give it a try typescript: 5.1.6 (same version when the build was still ok)

This one works.

Also wondering if it works if you do the following:
const functions = require('@google-cloud/functions-framework');

functions.http('helloWorld', (req, res) => {
  res.send('Hello, World');
});

this does not

Could you also give it a try typescript: 5.1.6 (same version when the build was still ok)

This one works. The new angular however forces us to use to use >=5.2

Interesting, not sure if we can do something about it here.

Hey @TriPSs,
I think until google updates their typescript package to the latest typescript, you're right there isn't much we can do.
I tried running your runner, I'm encountering this error:
The "@nx/node" package does not support Nx executors.
Error: Unable to resolve @nx/node:execute.
The "@nx/node" package does not support Nx executors.

Here's my main.ts:
import { bootstrapRunner } from '@nx-extend/gcp-functions/runner';

/* eslint-disable @nx/enforce-module-boundaries */
bootstrapRunner(
  new Map([['cloud-runner', import('../../cloud-functions/src/main')]]),
);

Is there something I've missed? Thanks!

Sorry for that, just now noticed that when updating the code to the latest runner I did not update the generating of the runner, can you change your json to the following:
{
  "name": "cloud-functions-runner",
  "$schema": "../../node_modules/nx/schemas/project-schema.json",
  "projectType": "application",
  "sourceRoot": "apps/cloud-functions-runner/src",
  "targets": {
    "_build": {
      "executor": "@nx/webpack:webpack",
      "outputs": ["{options.outputPath}"],
      "options": {
        "outputPath": "dist/apps/cloud-functions-runner",
        "main": "apps/cloud-functions-runner/src/main.ts",
        "tsConfig": "apps/cloud-functions-runner/tsconfig.app.json",
        "compiler": "tsc",
        "target": "node",
        "namedChunks": true
      }
    },
    "serve": {
      "executor": "@nx/js:node",
      "options": {
        "buildTarget": "cloud-functions-runner:_build"
      }
    }
  },
  "tags": []
}

Let me know if it works or if you get other issues.

Amazing, and how does it register the routes and call the functions? Do we need to set up explicitely the endpoints names?

Based on the info inside the projects deploy info it will build an endpoint, the runner should also log all the endpoints it registeres.
They can than be called like localhost:9000/

[Nest] 31115  - 29/11/2023, 09:56:28   DEBUG [Runner] Register http -> "/cloud-functions"
[Nest] 31115  - 29/11/2023, 09:56:28   DEBUG [Runner] Register http -> "/_check/health"

/_check/health calls fine and returns empty.
/cloud-functions returns this error:
[Nest] 31115  - 29/11/2023, 10:04:38   ERROR [ExceptionsHandler] endpoint.func is not a function

Could you share the project.json of that cloud function?

It's the same one you provided above

This is the of the runner, I mean the one of the actual function, since the runner uses the project.json of the imported projects inside the map and than uses the target where the executor is @nx-extend/gcp-functions:deploy, based on that it builds the endpoint.
For example, it uses the required entryPoint option of deploy to determine what code to use from the main.ts

{
  "name": "cloud-functions",
  "$schema": "../../node_modules/nx/schemas/project-schema.json",
  "projectType": "application",
  "sourceRoot": "apps/cloud-functions/src",
  "targets": {
    "lint": {
      "executor": "@nrwl/linter:eslint",
      "options": {}
    },
    "test": {
      "executor": "@nx/jest:jest",
      "options": {
        "jestConfig": "apps/cloud-functions/jest.config.ts",
        "passWithNoTests": true
      }
    },
    "build": {
      "executor": "@nx-extend/gcp-functions:build",
      "options": {
        "generateLockFile": true,
        "outputPath": "dist/apps/cloud-functions",
        "main": "apps/cloud-functions/src/main.ts",
        "tsConfig": "apps/cloud-functions/tsconfig.app.json",
        "assets": []
      },
      "configurations": {
        "production": {
          "optimization": true,
          "extractLicenses": false,
          "inspect": false
        }
      }
    },
    "deploy": {
      "executor": "@nx-extend/gcp-functions:deploy",
      "options": {
        "functionName": "cloud-functions",
        "envVarsFile": "apps/cloud-functions/src/environments/production.yaml"
      }
    }
  },
  "tags": []
}

There's no entryPoint defined here. By the way, this is generated by @nx-extend/gcp-functions:init without any modification

Sorry for all the issues here, I really need to invest some time and finish + update docs (#152).
The issues we encountered here I updated.

No worries mate, you're doing great work - your library saved me a ton of time.
I'll also find some time to contribute in the upcoming weeks, this is a great project and a great time saver. Thank you

When attempting to deploy, I'm getting the following:
The user-provided container failed to start and listen on the port defined provided by the PORT=8080 environment variable. Logs for this revision might contain more information

Logs state that the healthcheck is failing. Container Healthcheck failed and revision is failing.
This wasn't a problem before, did you face this at any point?

just to make sure, you are deploying the function right? Not the runner?
Double checking: entry point is correct?

Yes the function, and entry point is correct

There is no other error in the logs that could point out why it failed to start?

FYI: I have created an slack for an other opensource project I maintain, if you want you can also join there and maybe share a bit more info on your code.

Downgrading to  "@nx/webpack": "17.0.3" temporarely solves the issue.
Reference: https://github.com/nrwl/nx/issues/20349

Nx released the fix (17.2.0)

Good to know: also update to the latest nx-extend version, Nx introduced a couple more issues which are now temporarily solved by the package.

Yea realized that, thanks!